.1.0,LLDP-MIB::std,,,,,,
.1.0.8802,LLDP-MIB::iso8802,,,,,,
.1.0.8802.1,LLDP-MIB::ieee802dot1,,,,,,
.1.0.8802.1.1,LLDP-MIB::ieee802dot1mibs,,,,,,
.1.0.8802.1.1.1,IEEE8021-PAE-MIB::ieee8021paeMIB,,,,,,The Port Access Entity module for managing IEEE 802.1X.
.1.0.8802.1.1.1.1,IEEE8021-PAE-MIB::paeMIBObjects,,,,,,
.1.0.8802.1.1.1.1.1,IEEE8021-PAE-MIB::dot1xPaeSystem,,,,,,
.1.0.8802.1.1.1.1.1.1,IEEE8021-PAE-MIB::dot1xPaeSystemAuthControl,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative enable/disable state for Port Access Control in a System.
.1.0.8802.1.1.1.1.1.2,IEEE8021-PAE-MIB::dot1xPaePortTable,,not-accessible,,current,,A table of system level information for each port supported by the Port Access Entity. An entry appears in this table for each port of this system.
.1.0.8802.1.1.1.1.1.2.1,IEEE8021-PAE-MIB::dot1xPaePortEntry,,not-accessible,dot1xPaePortNumber,current,,The Port number, protocol version, and initialization control for a Port.
.1.0.8802.1.1.1.1.1.2.1.1,IEEE8021-PAE-MIB::dot1xPaePortNumber,Integer32,not-accessible,,current,,The Port number associated with this Port.
.1.0.8802.1.1.1.1.1.2.1.2,IEEE8021-PAE-MIB::dot1xPaePortProtocolVersion,Unsigned32,read-only,,current,,The protocol version associated with this Port.
.1.0.8802.1.1.1.1.1.2.1.3,IEEE8021-PAE-MIB::dot1xPaePortCapabilities,BITS,read-only,,current,dot1xPaePortAuthCapable(0):dot1xPaePortSuppCapable(1),Indicates the PAE functionality that this Port supports and that may be managed through this MIB.
.1.0.8802.1.1.1.1.1.2.1.4,IEEE8021-PAE-MIB::dot1xPaePortInitialize,INTEGER,read-write,,current,true(1):false(2),The initialization control for this Port. Setting this attribute TRUE causes the Port to be initialized. The attribute value reverts to FALSE once initialization has completed.
.1.0.8802.1.1.1.1.1.2.1.5,IEEE8021-PAE-MIB::dot1xPaePortReauthenticate,INTEGER,read-write,,current,true(1):false(2),The reauthentication control for this port. Setting this attribute TRUE causes the Authenticator PAE state machine for the Port to reauthenticate the Supplicant. Setting this attribute FALSE has no effect. This attribute always returns FALSE when it is read.
.1.0.8802.1.1.1.1.2,IEEE8021-PAE-MIB::dot1xPaeAuthenticator,,,,,,
.1.0.8802.1.1.1.1.2.1,IEEE8021-PAE-MIB::dot1xAuthConfigTable,,not-accessible,,current,,A table that contains the configuration objects for the Authenticator PAE associated with each port. An entry appears in this table for each port that may authenticate access to itself.
.1.0.8802.1.1.1.1.2.1.1,IEEE8021-PAE-MIB::dot1xAuthConfigEntry,,not-accessible,dot1xPaePortNumber,current,,The configuration information for an Authenticator PAE.
.1.0.8802.1.1.1.1.2.1.1.1,IEEE8021-PAE-MIB::dot1xAuthPaeState,INTEGER,read-only,,current,initialize(1):disconnected(2):connecting(3):authenticating(4):authenticated(5):aborting(6):held(7):forceAuth(8):forceUnauth(9):restart(10),The current value of the Authenticator PAE state machine.
.1.0.8802.1.1.1.1.2.1.1.2,IEEE8021-PAE-MIB::dot1xAuthBackendAuthState,INTEGER,read-only,,current,request(1):response(2):success(3):fail(4):timeout(5):idle(6):initialize(7):ignore(8),The current state of the Backend Authentication state machine.
.1.0.8802.1.1.1.1.2.1.1.3,IEEE8021-PAE-MIB::dot1xAuthAdminControlledDirections,INTEGER,read-write,,current,both(0):in(1),The current value of the administrative controlled directions parameter for the Port.
.1.0.8802.1.1.1.1.2.1.1.4,IEEE8021-PAE-MIB::dot1xAuthOperControlledDirections,INTEGER,read-only,,current,both(0):in(1),The current value of the operational controlled directions parameter for the Port.
.1.0.8802.1.1.1.1.2.1.1.5,IEEE8021-PAE-MIB::dot1xAuthAuthControlledPortStatus,INTEGER,read-only,,current,authorized(1):unauthorized(2),The current value of the controlled Port status parameter for the Port.
.1.0.8802.1.1.1.1.2.1.1.6,IEEE8021-PAE-MIB::dot1xAuthAuthControlledPortControl,INTEGER,read-write,,current,forceUnauthorized(1):auto(2):forceAuthorized(3),The current value of the controlled Port control parameter for the Port.
.1.0.8802.1.1.1.1.2.1.1.7,IEEE8021-PAE-MIB::dot1xAuthQuietPeriod,Unsigned32,read-write,,current,,The value, in seconds, of the quietPeriod constant currently in use by the Authenticator PAE state machine.
.1.0.8802.1.1.1.1.2.1.1.8,IEEE8021-PAE-MIB::dot1xAuthTxPeriod,Unsigned32,read-write,,deprecated,,The value, in seconds, of the txPeriod constant currently in use by the Authenticator PAE state machine.
.1.0.8802.1.1.1.1.2.1.1.9,IEEE8021-PAE-MIB::dot1xAuthSuppTimeout,Unsigned32,read-write,,deprecated,,The value, in seconds, of the suppTimeout constant currently in use by the Backend Authentication state machine.
.1.0.8802.1.1.1.1.2.1.1.10,IEEE8021-PAE-MIB::dot1xAuthServerTimeout,Unsigned32,read-write,,current,,The value, in seconds, of the serverTimeout constant currently in use by the Backend Authentication state machine.
.1.0.8802.1.1.1.1.2.1.1.11,IEEE8021-PAE-MIB::dot1xAuthMaxReq,Unsigned32,read-write,,deprecated,,The value of the maxReq constant currently in use by the Backend Authentication state machine.
.1.0.8802.1.1.1.1.2.1.1.12,IEEE8021-PAE-MIB::dot1xAuthReAuthPeriod,Unsigned32,read-write,,current,,The value, in seconds, of the reAuthPeriod constant currently in use by the Reauthentication Timer state machine.
.1.0.8802.1.1.1.1.2.1.1.13,IEEE8021-PAE-MIB::dot1xAuthReAuthEnabled,INTEGER,read-write,,current,true(1):false(2),The enable/disable control used by the Reauthentication Timer state machine (8.5.5.1).
.1.0.8802.1.1.1.1.2.1.1.14,IEEE8021-PAE-MIB::dot1xAuthKeyTxEnabled,INTEGER,read-write,,current,true(1):false(2),The value of the keyTransmissionEnabled constant currently in use by the Authenticator PAE state machine.
.1.0.8802.1.1.1.1.2.2,IEEE8021-PAE-MIB::dot1xAuthStatsTable,,not-accessible,,current,,A table that contains the statistics objects for the Authenticator PAE associated with each Port. An entry appears in this table for each port that may authenticate access to itself.
.1.0.8802.1.1.1.1.2.2.1,IEEE8021-PAE-MIB::dot1xAuthStatsEntry,,not-accessible,dot1xPaePortNumber,current,,The statistics information for an Authenticator PAE.
.1.0.8802.1.1.1.1.2.2.1.1,IEEE8021-PAE-MIB::dot1xAuthEapolFramesRx,Counter32,read-only,,current,,The number of valid EAPOL frames of any type that have been received by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.2,IEEE8021-PAE-MIB::dot1xAuthEapolFramesTx,Counter32,read-only,,current,,The number of EAPOL frames of any type that have been transmitted by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.3,IEEE8021-PAE-MIB::dot1xAuthEapolStartFramesRx,Counter32,read-only,,current,,The number of EAPOL Start frames that have been received by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.4,IEEE8021-PAE-MIB::dot1xAuthEapolLogoffFramesRx,Counter32,read-only,,current,,The number of EAPOL Logoff frames that have been received by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.5,IEEE8021-PAE-MIB::dot1xAuthEapolRespIdFramesRx,Counter32,read-only,,current,,The number of EAP Resp/Id frames that have been received by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.6,IEEE8021-PAE-MIB::dot1xAuthEapolRespFramesRx,Counter32,read-only,,current,,The number of valid EAP Response frames (other than Resp/Id frames) that have been received by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.7,IEEE8021-PAE-MIB::dot1xAuthEapolReqIdFramesTx,Counter32,read-only,,current,,The number of EAP Req/Id frames that have been transmitted by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.8,IEEE8021-PAE-MIB::dot1xAuthEapolReqFramesTx,Counter32,read-only,,current,,The number of EAP Request frames (other than Rq/Id frames) that have been transmitted by this Authenticator.
.1.0.8802.1.1.1.1.2.2.1.9,IEEE8021-PAE-MIB::dot1xAuthInvalidEapolFramesRx,Counter32,read-only,,current,,The number of EAPOL frames that have been received by this Authenticator in which the frame type is not recognized.
.1.0.8802.1.1.1.1.2.2.1.10,IEEE8021-PAE-MIB::dot1xAuthEapLengthErrorFramesRx,Counter32,read-only,,current,,The number of EAPOL frames that have been received by this Authenticator in which the Packet Body Length field is invalid.
.1.0.8802.1.1.1.1.2.2.1.11,IEEE8021-PAE-MIB::dot1xAuthLastEapolFrameVersion,Unsigned32,read-only,,current,,The protocol version number carried in the most recently received EAPOL frame.
.1.0.8802.1.1.1.1.2.2.1.12,IEEE8021-PAE-MIB::dot1xAuthLastEapolFrameSource,OCTET,read-only,,current,,The source MAC address carried in the most recently received EAPOL frame.
.1.0.8802.1.1.1.1.2.3,IEEE8021-PAE-MIB::dot1xAuthDiagTable,,not-accessible,,deprecated,,A table that contains the diagnostics objects for the Authenticator PAE associated with each Port. An entry appears in this table for each port that may authenticate access to itself.
.1.0.8802.1.1.1.1.2.3.1,IEEE8021-PAE-MIB::dot1xAuthDiagEntry,,not-accessible,dot1xPaePortNumber,deprecated,,The diagnostics information for an Authenticator PAE.
.1.0.8802.1.1.1.1.2.3.1.1,IEEE8021-PAE-MIB::dot1xAuthEntersConnecting,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions to the CONNECTING state from any other state.
.1.0.8802.1.1.1.1.2.3.1.2,IEEE8021-PAE-MIB::dot1xAuthEapLogoffsWhileConnecting,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from CONNECTING to DISCONNECTED as a result of receiving an EAPOL-Logoff message.
.1.0.8802.1.1.1.1.2.3.1.3,IEEE8021-PAE-MIB::dot1xAuthEntersAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from CONNECTING to AUTHENTICATING, as a result of an EAP-Response/Identity message being received from the Supplicant.
.1.0.8802.1.1.1.1.2.3.1.4,IEEE8021-PAE-MIB::dot1xAuthAuthSuccessWhileAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATING to AUTHENTICATED, as a result of the Backend Authentication state machine indicating successful authentication of the Supplicant (authSuccess = TRUE).
.1.0.8802.1.1.1.1.2.3.1.5,IEEE8021-PAE-MIB::dot1xAuthAuthTimeoutsWhileAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATING to ABORTING, as a result of the Backend Authentication state machine indicating authentication timeout (authTimeout = TRUE).
.1.0.8802.1.1.1.1.2.3.1.6,IEEE8021-PAE-MIB::dot1xAuthAuthFailWhileAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATING to HELD, as a result of the Backend Authentication state machine indicating authentication failure (authFail = TRUE).
.1.0.8802.1.1.1.1.2.3.1.7,IEEE8021-PAE-MIB::dot1xAuthAuthReauthsWhileAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATING to ABORTING, as a result of a reauthentication request (reAuthenticate = TRUE).
.1.0.8802.1.1.1.1.2.3.1.8,IEEE8021-PAE-MIB::dot1xAuthAuthEapStartsWhileAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATING to ABORTING, as a result of an EAPOL-Start message being received from the Supplicant.
.1.0.8802.1.1.1.1.2.3.1.9,IEEE8021-PAE-MIB::dot1xAuthAuthEapLogoffWhileAuthenticating,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATING to ABORTING, as a result of an EAPOL-Logoff message being received from the Supplicant.
.1.0.8802.1.1.1.1.2.3.1.10,IEEE8021-PAE-MIB::dot1xAuthAuthReauthsWhileAuthenticated,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATED to CONNECTING, as a result of a reauthentication request (reAuthenticate = TRUE).
.1.0.8802.1.1.1.1.2.3.1.11,IEEE8021-PAE-MIB::dot1xAuthAuthEapStartsWhileAuthenticated,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATED to CONNECTING, as a result of an EAPOL-Start message being received from the Supplicant.
.1.0.8802.1.1.1.1.2.3.1.12,IEEE8021-PAE-MIB::dot1xAuthAuthEapLogoffWhileAuthenticated,Counter32,read-only,,deprecated,,Counts the number of times that the state machine transitions from AUTHENTICATED to DISCONNECTED, as a result of an EAPOL-Logoff message being received from the Supplicant.
.1.0.8802.1.1.1.1.2.3.1.13,IEEE8021-PAE-MIB::dot1xAuthBackendResponses,Counter32,read-only,,deprecated,,Counts the number of times that the state machine sends an initial Access-Request packet to the Authentication server (i.e., executes sendRespToServer on entry to the RESPONSE state). Indicates that the Authenticator attempted communication with the Authentication Server.
.1.0.8802.1.1.1.1.2.3.1.14,IEEE8021-PAE-MIB::dot1xAuthBackendAccessChallenges,Counter32,read-only,,deprecated,,Counts the number of times that the state machine receives an initial Access-Challenge packet from the Authentication server (i.e., aReq becomes TRUE, causing exit from the RESPONSE state). Indicates that the Authentication Server has communication with the Authenticator.
.1.0.8802.1.1.1.1.2.3.1.15,IEEE8021-PAE-MIB::dot1xAuthBackendOtherRequestsToSupplicant,Counter32,read-only,,deprecated,,Counts the number of times that the state machine sends an EAP-Request packet (other than an Identity, Notification, Failure or Success message) to the Supplicant (i.e., executes txReq on entry to the REQUEST state). Indicates that the Authenticator chose an EAP-method.
.1.0.8802.1.1.1.1.2.3.1.16,IEEE8021-PAE-MIB::dot1xAuthBackendNonNakResponsesFromSupplicant,Counter32,read-only,,deprecated,,Counts the number of times that the state machine receives a response from the Supplicant to an initial EAP-Request, and the response is something other than EAP-NAK (i.e., rxResp becomes TRUE, causing the state machine to transition from REQUEST to RESPONSE, and the response is not an EAP-NAK). Indicates that the Supplicant can respond to the Authenticators chosen EAP-method.
.1.0.8802.1.1.1.1.2.3.1.17,IEEE8021-PAE-MIB::dot1xAuthBackendAuthSuccesses,Counter32,read-only,,deprecated,,Counts the number of times that the state machine receives an EAP-Success message from the Authentication Server (i.e., aSuccess becomes TRUE, causing a transition from RESPONSE to SUCCESS). Indicates that the Supplicant has successfully authenticated to the Authentication Server.
.1.0.8802.1.1.1.1.2.3.1.18,IEEE8021-PAE-MIB::dot1xAuthBackendAuthFails,Counter32,read-only,,deprecated,,Counts the number of times that the state machine receives an EAP-Failure message from the Authentication Server (i.e., aFail becomes TRUE, causing a transition from RESPONSE to FAIL). Indicates that the Supplicant has not authenticated to the Authentication Server.
.1.0.8802.1.1.1.1.2.4,IEEE8021-PAE-MIB::dot1xAuthSessionStatsTable,,not-accessible,,current,,A table that contains the session statistics objects for the Authenticator PAE associated with each Port. An entry appears in this table for each port that may authenticate access to itself.
.1.0.8802.1.1.1.1.2.4.1,IEEE8021-PAE-MIB::dot1xAuthSessionStatsEntry,,not-accessible,dot1xPaePortNumber,current,,The session statistics information for an Authenticator PAE. This shows the current values being collected for each session that is still in progress, or the final values for the last valid session on each port where there is no session currently active.
.1.0.8802.1.1.1.1.2.4.1.1,IEEE8021-PAE-MIB::dot1xAuthSessionOctetsRx,Counter64,read-only,,current,,The number of octets received in user data frames on this Port during the session.
.1.0.8802.1.1.1.1.2.4.1.2,IEEE8021-PAE-MIB::dot1xAuthSessionOctetsTx,Counter64,read-only,,current,,The number of octets transmitted in user data frames on this Port during the session.
.1.0.8802.1.1.1.1.2.4.1.3,IEEE8021-PAE-MIB::dot1xAuthSessionFramesRx,Counter32,read-only,,current,,The number of user data frames received on this Port during the session.
.1.0.8802.1.1.1.1.2.4.1.4,IEEE8021-PAE-MIB::dot1xAuthSessionFramesTx,Counter32,read-only,,current,,The number of user data frames transmitted on this Port during the session.
.1.0.8802.1.1.1.1.2.4.1.5,IEEE8021-PAE-MIB::dot1xAuthSessionId,OCTET,read-only,,current,,A unique identifier for the session, in the form of a printable ASCII string of at least three characters.
.1.0.8802.1.1.1.1.2.4.1.6,IEEE8021-PAE-MIB::dot1xAuthSessionAuthenticMethod,INTEGER,read-only,,current,remoteAuthServer(1):localAuthServer(2),The authentication method used to establish the session.
.1.0.8802.1.1.1.1.2.4.1.7,IEEE8021-PAE-MIB::dot1xAuthSessionTime,TimeTicks,read-only,,current,,The duration of the session in seconds.
.1.0.8802.1.1.1.1.2.4.1.8,IEEE8021-PAE-MIB::dot1xAuthSessionTerminateCause,INTEGER,read-only,,current,supplicantLogoff(1):portFailure(2):supplicantRestart(3):reauthFailed(4):authControlForceUnauth(5):portReInit(6):portAdminDisabled(7):notTerminatedYet(999),The reason for the session termination.
.1.0.8802.1.1.1.1.2.4.1.9,IEEE8021-PAE-MIB::dot1xAuthSessionUserName,OCTET,read-only,,current,,The User-Name representing the identity of the Supplicant PAE.
.1.0.8802.1.1.1.1.3,IEEE8021-PAE-MIB::dot1xPaeSupplicant,,,,,,
.1.0.8802.1.1.1.1.3.1,IEEE8021-PAE-MIB::dot1xSuppConfigTable,,not-accessible,,current,,A table that contains the configuration objects for the Supplicant PAE associated with each port. An entry appears in this table for each port that may authenticate itself when challenged by a remote system.
.1.0.8802.1.1.1.1.3.1.1,IEEE8021-PAE-MIB::dot1xSuppConfigEntry,,not-accessible,dot1xPaePortNumber,current,,The configuration information for a Supplicant PAE.
.1.0.8802.1.1.1.1.3.1.1.1,IEEE8021-PAE-MIB::dot1xSuppPaeState,INTEGER,read-only,,current,disconnected(1):logoff(2):connecting(3):authenticating(4):authenticated(5):acquired(6):held(7):restart(8):sForceAuth(9):sForceUnauth(10),The current state of the Supplicant PAE state machine (8.5.8).
.1.0.8802.1.1.1.1.3.1.1.2,IEEE8021-PAE-MIB::dot1xSuppHeldPeriod,Unsigned32,read-write,,current,,The value, in seconds, of the heldPeriod constant currently in use by the Supplicant PAE state machine (8.5.8.1.2).
.1.0.8802.1.1.1.1.3.1.1.3,IEEE8021-PAE-MIB::dot1xSuppAuthPeriod,Unsigned32,read-write,,current,,The value, in seconds, of the authPeriod constant currently in use by the Supplicant PAE state machine (8.5.8.1.2).
.1.0.8802.1.1.1.1.3.1.1.4,IEEE8021-PAE-MIB::dot1xSuppStartPeriod,Unsigned32,read-write,,current,,The value, in seconds, of the startPeriod constant currently in use by the Supplicant PAE state machine (8.5.8.1.2).
.1.0.8802.1.1.1.1.3.1.1.5,IEEE8021-PAE-MIB::dot1xSuppMaxStart,Unsigned32,read-write,,current,,The value of the maxStart constant currently in use by the Supplicant PAE state machine (8.5.8.1.2).
.1.0.8802.1.1.1.1.3.1.1.6,IEEE8021-PAE-MIB::dot1xSuppControlledPortStatus,INTEGER,read-only,,current,authorized(1):unauthorized(2),The current state of the Supplicant PAE state machine (8.5.8).
.1.0.8802.1.1.1.1.3.1.1.7,IEEE8021-PAE-MIB::dot1xSuppAccessCtrlWithAuth,INTEGER,read-write,,current,inactive(1):active(2),The setting for the application of the Supplicant authorization state when the port is operating as both a Supplicant and an Authenticator. inactive indicates the port will not apply the the Supplicant authorization state, using only the Authenticator authorization  state to restrict access to the port. active indicates the port will apply the the Supplicant authorization state, as well as the Authenticator authorization state.
.1.0.8802.1.1.1.1.3.1.1.8,IEEE8021-PAE-MIB::dot1xSuppBackendState,INTEGER,read-only,,current,initialize(1):idle(2):request(3):response(4):receive(5):fail(6):success(7):timeout(8),The current state of the Supplicant Backend state
.1.0.8802.1.1.1.1.3.2,IEEE8021-PAE-MIB::dot1xSuppStatsTable,,not-accessible,,current,,A table that contains the statistics objects for the Supplicant PAE associated with each port. An entry appears in this table for each port that may authenticate itself when challenged by a remote system.
.1.0.8802.1.1.1.1.3.2.1,IEEE8021-PAE-MIB::dot1xSuppStatsEntry,,not-accessible,dot1xPaePortNumber,current,,The statistics information for a Supplicant PAE.
.1.0.8802.1.1.1.1.3.2.1.1,IEEE8021-PAE-MIB::dot1xSuppEapolFramesRx,Counter32,read-only,,current,,The number of EAPOL frames of any type that have been received by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.2,IEEE8021-PAE-MIB::dot1xSuppEapolFramesTx,Counter32,read-only,,current,,The number of EAPOL frames of any type that have been transmitted by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.3,IEEE8021-PAE-MIB::dot1xSuppEapolStartFramesTx,Counter32,read-only,,current,,The number of EAPOL Start frames that have been transmitted by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.4,IEEE8021-PAE-MIB::dot1xSuppEapolLogoffFramesTx,Counter32,read-only,,current,,The number of EAPOL Logoff frames that have been transmitted by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.5,IEEE8021-PAE-MIB::dot1xSuppEapolRespIdFramesTx,Counter32,read-only,,deprecated,,The number of EAP Resp/Id frames that have been transmitted by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.6,IEEE8021-PAE-MIB::dot1xSuppEapolRespFramesTx,Counter32,read-only,,deprecated,,The number of valid EAP Response frames (other than Resp/Id frames) that have been transmitted by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.7,IEEE8021-PAE-MIB::dot1xSuppEapolReqIdFramesRx,Counter32,read-only,,deprecated,,The number of EAP Req/Id frames that have been received by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.8,IEEE8021-PAE-MIB::dot1xSuppEapolReqFramesRx,Counter32,read-only,,deprecated,,The number of EAP Request frames (other than Rq/Id frames) that have been received by this Supplicant.
.1.0.8802.1.1.1.1.3.2.1.9,IEEE8021-PAE-MIB::dot1xSuppInvalidEapolFramesRx,Counter32,read-only,,current,,The number of EAPOL frames that have been received by this Supplicant in which the frame type is not recognized.
.1.0.8802.1.1.1.1.3.2.1.10,IEEE8021-PAE-MIB::dot1xSuppEapLengthErrorFramesRx,Counter32,read-only,,current,,The number of EAPOL frames that have been received by this Supplicant in which the Packet Body Length field (7.5.5) is invalid.
.1.0.8802.1.1.1.1.3.2.1.11,IEEE8021-PAE-MIB::dot1xSuppLastEapolFrameVersion,Unsigned32,read-only,,current,,The protocol version number carried in the most recently received EAPOL frame.
.1.0.8802.1.1.1.1.3.2.1.12,IEEE8021-PAE-MIB::dot1xSuppLastEapolFrameSource,OCTET,read-only,,current,,The source MAC address carried in the most recently received EAPOL frame.
.1.0.8802.1.1.1.2,IEEE8021-PAE-MIB::dot1xPaeConformance,,,,,,
.1.0.8802.1.1.1.2.1,IEEE8021-PAE-MIB::dot1xPaeGroups,,,,,,
.1.0.8802.1.1.1.2.1.1,IEEE8021-PAE-MIB::dot1xPaeSystemGroup,,,,,,A collection of objects providing system information about, and control over, a PAE.
.1.0.8802.1.1.1.2.1.2,IEEE8021-PAE-MIB::dot1xPaeAuthConfigGroup,,,,,,A collection of objects providing configuration information about an Authenticator PAE.
.1.0.8802.1.1.1.2.1.3,IEEE8021-PAE-MIB::dot1xPaeAuthStatsGroup,,,,,,A collection of objects providing statistics about an Authenticator PAE.
.1.0.8802.1.1.1.2.1.4,IEEE8021-PAE-MIB::dot1xPaeAuthDiagGroup,,,,,,A collection of objects providing diagnostic statistics about an Authenticator PAE.
.1.0.8802.1.1.1.2.1.5,IEEE8021-PAE-MIB::dot1xPaeAuthSessionStatsGroup,,,,,,A collection of objects providing statistics about the current, or last session for an Authenticator PAE.
.1.0.8802.1.1.1.2.1.6,IEEE8021-PAE-MIB::dot1xPaeSuppConfigGroup,,,,,,A collection of objects providing configuration information about a Supplicant PAE.
.1.0.8802.1.1.1.2.1.7,IEEE8021-PAE-MIB::dot1xPaeSuppStatsGroup,,,,,,A collection of objects providing statistics about a Supplicant PAE.
.1.0.8802.1.1.1.2.1.8,IEEE8021-PAE-MIB::dot1xPaeAuthConfigGroup2,,,,,,A collection of objects providing configuration information about an Authenticator PAE.
.1.0.8802.1.1.1.2.1.9,IEEE8021-PAE-MIB::dot1xPaeSuppConfigGroup2,,,,,,A collection of objects providing configuration information about a Supplicant PAE.
.1.0.8802.1.1.1.2.1.10,IEEE8021-PAE-MIB::dot1xPaeSuppStatsGroup2,,,,,,A collection of objects providing statistics about a Supplicant PAE.
.1.0.8802.1.1.1.2.2,IEEE8021-PAE-MIB::dot1xPaeCompliances,,,,,,
.1.0.8802.1.1.1.2.2.1,IEEE8021-PAE-MIB::dot1xPaeCompliance,,,,,,The compliance statement for device support of Port Access Control.
.1.0.8802.1.1.1.2.2.2,IEEE8021-PAE-MIB::dot1xPaeCompliance2,,,,,,The compliance statement for device support of Port Access Control.
.1.0.8802.1.1.2,LLDP-MIB::lldpMIB,,,,,,Management Information Base module for LLDP configuration, statistics, local system data and remote systems data components. Copyright (C) IEEE (2005). This version of this MIB module is published as subclause 12.1 of IEEE Std 802.1AB-2005; see the standard itself for full legal notices.
.1.0.8802.1.1.2.0,LLDP-MIB::lldpNotifications,,,,,,
.1.0.8802.1.1.2.0.0,LLDP-MIB::lldpNotificationPrefix,,,,,,
.1.0.8802.1.1.2.0.0.1,LLDP-MIB::lldpRemTablesChange,,,,,,A lldpRemTablesChange notification is sent when the value of lldpStatsRemTableLastChangeTime changes. It can be utilized by an NMS to trigger LLDP remote systems table maintenance polls. Note that transmission of lldpRemTablesChange notifications are throttled by the agent, as specified by the 'lldpNotificationInterval' object.
.1.0.8802.1.1.2.1,LLDP-MIB::lldpObjects,,,,,,
.1.0.8802.1.1.2.1.1,LLDP-MIB::lldpConfiguration,,,,,,
.1.0.8802.1.1.2.1.1.1,LLDP-MIB::lldpMessageTxInterval,Integer32,read-write,,current,,The interval at which LLDP frames are transmitted on behalf of this LLDP agent. The default value for lldpMessageTxInterval object is 30 seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.2,LLDP-MIB::lldpMessageTxHoldMultiplier,Integer32,read-write,,current,,The time-to-live value expressed as a multiple of the lldpMessageTxInterval object. The actual time-to-live value used in LLDP frames, transmitted on behalf of this LLDP agent, can be expressed by the following formula: TTL = min(65535, (lldpMessageTxInterval * lldpMessageTxHoldMultiplier)) For example, if the value of lldpMessageTxInterval is '30', and the value of lldpMessageTxHoldMultiplier is '4', then the value '120' is encoded in the TTL field in the LLDP header. The default value for lldpMessageTxHoldMultiplier object is 4. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.3,LLDP-MIB::lldpReinitDelay,Integer32,read-write,,current,,The lldpReinitDelay indicates the delay (in units of seconds) from when lldpPortConfigAdminStatus object of a particular port becomes 'disabled' until re-initialization will be attempted. The default value for lldpReintDelay object is two seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.4,LLDP-MIB::lldpTxDelay,Integer32,read-write,,current,,The lldpTxDelay indicates the delay (in units of seconds) between successive LLDP frame transmissions  initiated by value/status changes in the LLDP local systems MIB. The recommended value for the lldpTxDelay is set by the following formula: 1 <= lldpTxDelay <= (0.25 * lldpMessageTxInterval) The default value for lldpTxDelay object is two seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.5,LLDP-MIB::lldpNotificationInterval,Integer32,read-write,,current,,This object controls the transmission of LLDP notifications. the agent must not generate more than one lldpRemTablesChange notification-event in the indicated period, where a 'notification-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional changes in lldpRemoteSystemsData object groups occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of lldpStatsRemTableLastChangeTime to detect any missed lldpRemTablesChange notification-events, e.g. due to throttling or transmission loss. If notification transmission is enabled for particular ports, the suggested default throttling period is 5 seconds. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.6,LLDP-MIB::lldpPortConfigTable,,not-accessible,,current,,The table that controls LLDP frame transmission on individual ports.
.1.0.8802.1.1.2.1.1.6.1,LLDP-MIB::lldpPortConfigEntry,,not-accessible,lldpPortConfigPortNum,current,,LLDP configuration information for a particular port. This configuration parameter controls the transmission and the reception of LLDP frames on those ports whose rows are created in this table.
.1.0.8802.1.1.2.1.1.6.1.1,LLDP-MIB::lldpPortConfigPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpPortConfigTable.
.1.0.8802.1.1.2.1.1.6.1.2,LLDP-MIB::lldpPortConfigAdminStatus,INTEGER,read-write,,current,txOnly(1):rxOnly(2):txAndRx(3):disabled(4),The administratively desired status of the local LLDP agent. If the associated lldpPortConfigAdminStatus object has a value of 'txOnly(1)', then LLDP agent will transmit LLDP frames on this port and it will not store any information about the remote systems connected.  If the associated lldpPortConfigAdminStatus object has a value of 'rxOnly(2)', then the LLDP agent will receive, but it will not transmit LLDP frames on this port. If the associated lldpPortConfigAdminStatus object has a value of 'txAndRx(3)', then the LLDP agent will transmit and receive LLDP frames on this port. If the associated lldpPortConfigAdminStatus object has a value of 'disabled(4)', then LLDP agent will not transmit or receive LLDP frames on this port. If there is remote systems information which is received on this port and stored in other tables, before the port's lldpPortConfigAdminStatus becomes disabled, then the information will naturally age out.
.1.0.8802.1.1.2.1.1.6.1.3,LLDP-MIB::lldpPortConfigNotificationEnable,INTEGER,read-write,,current,true(1):false(2),The lldpPortConfigNotificationEnable controls, on a per port basis, whether or not notifications from the agent are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
.1.0.8802.1.1.2.1.1.6.1.4,LLDP-MIB::lldpPortConfigTLVsTxEnable,BITS,read-write,,current,portDesc(0):sysName(1):sysDesc(2):sysCap(3),The lldpPortConfigTLVsTxEnable, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. It should be noted that the organizationally-specific TLVs are excluded from the lldpTLVsTxEnable bitmap.  LLDP Organization Specific Information Extension MIBs should have similar configuration object to control transmission of their organizationally defined TLVs. The bit 'portDesc(0)' indicates that LLDP agent should transmit 'Port Description TLV'. The bit 'sysName(1)' indicates that LLDP agent should transmit 'System Name TLV'. The bit 'sysDesc(2)' indicates that LLDP agent should transmit 'System Description TLV'. The bit 'sysCap(3)' indicates that LLDP agent should transmit 'System Capabilities TLV'. There is no bit reserved for the management address TLV type since transmission of management address TLVs are controlled by another object, lldpConfigManAddrTable. The default value for lldpPortConfigTLVsTxEnable object is empty set, which means no enumerated values are set. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.7,LLDP-MIB::lldpConfigManAddrTable,,not-accessible,,current,,The table that controls selection of LLDP management address TLV instances to be transmitted on individual ports.
.1.0.8802.1.1.2.1.1.7.1,LLDP-MIB::lldpConfigManAddrEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the local system management address instance will be transmitted. This configuration object augments the lldpLocManAddrEntry, therefore it is only present along with the management address instance contained in the associated lldpLocManAddrEntry entry. Each active lldpConfigManAddrEntry must be restored from non-volatile and re-created (along with the corresponding lldpLocManAddrEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.1.7.1.1,LLDP-MIB::lldpConfigManAddrPortsTxEnable,OCTET,read-write,,current,,A set of ports that are identified by a PortList, in which each port is represented as a bit. The corresponding local system management address instance will be transmitted on the member ports of the lldpManAddrPortsTxEnable.  The default value for lldpConfigManAddrPortsTxEnable object is empty binary string, which means no ports are specified for advertising indicated management address instance.
.1.0.8802.1.1.2.1.2,LLDP-MIB::lldpStatistics,,,,,,
.1.0.8802.1.1.2.1.2.1,LLDP-MIB::lldpStatsRemTablesLastChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime object (defined in IETF RFC 3418) at the time an entry is created, modified, or deleted in the in tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems. An NMS can use this object to reduce polling of the lldpRemoteSystemsData objects.
.1.0.8802.1.1.2.1.2.2,LLDP-MIB::lldpStatsRemTablesInserts,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
.1.0.8802.1.1.2.1.2.3,LLDP-MIB::lldpStatsRemTablesDeletes,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects. This counter should be incremented only once when the complete set of information is completely deleted from all related tables. Partial deletions, such as deletion of rows associated with a particular MSAP from some tables, but not from all tables are not allowed, thus should not change the value of this counter.
.1.0.8802.1.1.2.1.2.4,LLDP-MIB::lldpStatsRemTablesDrops,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP could not be entered into tables contained in lldpRemoteSystemsData and lldpExtensions objects because of insufficient resources.
.1.0.8802.1.1.2.1.2.5,LLDP-MIB::lldpStatsRemTablesAgeouts,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired. This counter should be incremented only once when the complete set of information is completely invalidated (aged out) from all related tables. Partial aging, similar to deletion case, is not allowed, and thus, should not change the value of this counter.
.1.0.8802.1.1.2.1.2.6,LLDP-MIB::lldpStatsTxPortTable,,not-accessible,,current,,A table containing LLDP transmission statistics for individual ports. Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
.1.0.8802.1.1.2.1.2.6.1,LLDP-MIB::lldpStatsTxPortEntry,,not-accessible,lldpStatsTxPortNum,current,,LLDP frame transmission statistics for a particular port.  The port must be contained in the same chassis as the LLDP agent.  All counter values in a particular entry shall be maintained on a continuing basis and shall not be deleted upon expiration of rxInfoTTL timing counters in the LLDP remote systems MIB of the receipt of a shutdown frame from a remote LLDP agent. All statistical counters associated with a particular port on the local LLDP agent become frozen whenever the adminStatus is disabled for the same port.
.1.0.8802.1.1.2.1.2.6.1.1,LLDP-MIB::lldpStatsTxPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpStatsTable.
.1.0.8802.1.1.2.1.2.6.1.2,LLDP-MIB::lldpStatsTxPortFramesTotal,Counter32,read-only,,current,,The number of LLDP frames transmitted by this LLDP agent on the indicated port.
.1.0.8802.1.1.2.1.2.7,LLDP-MIB::lldpStatsRxPortTable,,not-accessible,,current,,A table containing LLDP reception statistics for individual ports. Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
.1.0.8802.1.1.2.1.2.7.1,LLDP-MIB::lldpStatsRxPortEntry,,not-accessible,lldpStatsRxPortNum,current,,LLDP frame reception statistics for a particular port. The port must be contained in the same chassis as the LLDP agent.  All counter values in a particular entry shall be maintained on a continuing basis and shall not be deleted upon expiration of rxInfoTTL timing counters in the LLDP remote systems MIB of the receipt of a shutdown frame from a remote LLDP agent. All statistical counters associated with a particular port on the local LLDP agent become frozen whenever the adminStatus is disabled for the same port.
.1.0.8802.1.1.2.1.2.7.1.1,LLDP-MIB::lldpStatsRxPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The value of this object is used as a port index to the lldpStatsTable.
.1.0.8802.1.1.2.1.2.7.1.2,LLDP-MIB::lldpStatsRxPortFramesDiscardedTotal,Counter32,read-only,,current,,The number of LLDP frames received by this LLDP agent on the indicated port, and then discarded for any reason. This counter can provide an indication that LLDP header formating problems may exist with the local LLDP agent in the sending system or that LLDPDU validation problems may exist with the local LLDP agent in the receiving system.
.1.0.8802.1.1.2.1.2.7.1.3,LLDP-MIB::lldpStatsRxPortFramesErrors,Counter32,read-only,,current,,The number of invalid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled.
.1.0.8802.1.1.2.1.2.7.1.4,LLDP-MIB::lldpStatsRxPortFramesTotal,Counter32,read-only,,current,,The number of valid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled.
.1.0.8802.1.1.2.1.2.7.1.5,LLDP-MIB::lldpStatsRxPortTLVsDiscardedTotal,Counter32,read-only,,current,,The number of LLDP TLVs discarded for any reason by this LLDP agent on the indicated port.
.1.0.8802.1.1.2.1.2.7.1.6,LLDP-MIB::lldpStatsRxPortTLVsUnrecognizedTotal,Counter32,read-only,,current,,The number of LLDP TLVs received on the given port that are not recognized by this LLDP agent on the indicated port.  An unrecognized TLV is referred to as the TLV whose type value is in the range of reserved TLV types (000 1001 - 111 1110) in Table 9.1 of IEEE Std 802.1AB-2005. An unrecognized TLV may be a basic management TLV from a later LLDP version.
.1.0.8802.1.1.2.1.2.7.1.7,LLDP-MIB::lldpStatsRxPortAgeoutsTotal,Gauge32,read-only,,current,,The counter that represents the number of age-outs that occurred on a given port. An age-out is the number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired. This counter is similar to lldpStatsRemTablesAgeouts, except that the counter is on a per port basis. This enables NMS to poll tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems on the indicated port only. This counter should be set to zero during agent initialization and its value should not be saved in non-volatile storage. When a port's admin status changes from 'disabled' to 'rxOnly', 'txOnly' or 'txAndRx', the counter associated with the same port should reset to 0. The agent should also flush all remote system information associated with the same port. This counter should be incremented only once when the complete set of information is invalidated (aged out) from all related tables on a particular port. Partial aging is not allowed, and thus, should not change the value of this counter.
.1.0.8802.1.1.2.1.3,LLDP-MIB::lldpLocalSystemData,,,,,,
.1.0.8802.1.1.2.1.3.1,LLDP-MIB::lldpLocChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),The type of encoding used to identify the chassis associated with the local system.
.1.0.8802.1.1.2.1.3.2,LLDP-MIB::lldpLocChassisId,OCTET,read-only,,current,,The string value used to identify the chassis component associated with the local system.
.1.0.8802.1.1.2.1.3.3,LLDP-MIB::lldpLocSysName,OCTET,read-only,,current,,The string value used to identify the system name of the local system. If the local agent supports IETF RFC 3418, lldpLocSysName object should have the same value of sysName object.
.1.0.8802.1.1.2.1.3.4,LLDP-MIB::lldpLocSysDesc,OCTET,read-only,,current,,The string value used to identify the system description of the local system. If the local agent supports IETF RFC 3418, lldpLocSysDesc object should have the same value of sysDesc object.
.1.0.8802.1.1.2.1.3.5,LLDP-MIB::lldpLocSysCapSupported,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are supported on the local system.
.1.0.8802.1.1.2.1.3.6,LLDP-MIB::lldpLocSysCapEnabled,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are enabled on the local system.
.1.0.8802.1.1.2.1.3.7,LLDP-MIB::lldpLocPortTable,,not-accessible,,current,,This table contains one or more rows per port information associated with the local system known to this agent.
.1.0.8802.1.1.2.1.3.7.1,LLDP-MIB::lldpLocPortEntry,,not-accessible,lldpLocPortNum,current,,Information about a particular port component. Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.3.7.1.1,LLDP-MIB::lldpLocPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry.  The value of this object is used as a port index to the lldpLocPortTable.
.1.0.8802.1.1.2.1.3.7.1.2,LLDP-MIB::lldpLocPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),The type of port identifier encoding used in the associated 'lldpLocPortId' object.
.1.0.8802.1.1.2.1.3.7.1.3,LLDP-MIB::lldpLocPortId,OCTET,read-only,,current,,The string value used to identify the port component associated with a given port in the local system.
.1.0.8802.1.1.2.1.3.7.1.4,LLDP-MIB::lldpLocPortDesc,OCTET,read-only,,current,,The string value used to identify the 802 LAN station's port description associated with the local system. If the local agent supports IETF RFC 2863, lldpLocPortDesc object should have the same value of ifDescr object.
.1.0.8802.1.1.2.1.3.8,LLDP-MIB::lldpLocManAddrTable,,not-accessible,,current,,This table contains management address information on the local system known to this agent.
.1.0.8802.1.1.2.1.3.8.1,LLDP-MIB::lldpLocManAddrEntry,,not-accessible,lldpLocManAddrSubtype:lldpLocManAddr,current,,Management address information about a particular chassis component. There may be multiple management addresses configured on the system identified by a particular lldpLocChassisId. Each management address should have distinct 'management address type' (lldpLocManAddrSubtype) and 'management address' (lldpLocManAddr.) Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.3.8.1.1,LLDP-MIB::lldpLocManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpLocManagmentAddr' object.
.1.0.8802.1.1.2.1.3.8.1.2,LLDP-MIB::lldpLocManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the local system. The purpose of this address is to contact the management entity.
.1.0.8802.1.1.2.1.3.8.1.3,LLDP-MIB::lldpLocManAddrLen,Integer32,read-only,,current,,The total length of the management address subtype and the management address fields in LLDPDUs transmitted by the local LLDP agent. The management address length field is needed so that the receiving systems that do not implement SNMP will not be required to implement an iana family numbers/address length equivalency table in order to decode the management adress.
.1.0.8802.1.1.2.1.3.8.1.4,LLDP-MIB::lldpLocManAddrIfSubtype,INTEGER,read-only,,current,unknown(1):ifIndex(2):systemPortNumber(3),The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the local system.
.1.0.8802.1.1.2.1.3.8.1.5,LLDP-MIB::lldpLocManAddrIfId,Integer32,read-only,,current,,The integer value used to identify the interface number regarding the management address component associated with the local system.
.1.0.8802.1.1.2.1.3.8.1.6,LLDP-MIB::lldpLocManAddrOID,OBJECT,read-only,,current,,The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the local system agent.
.1.0.8802.1.1.2.1.4,LLDP-MIB::lldpRemoteSystemsData,,,,,,
.1.0.8802.1.1.2.1.4.1,LLDP-MIB::lldpRemTable,,not-accessible,,current,,This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port. The following procedure may be used to retrieve remote systems information updates from an LLDP agent: 1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpStatsRemTablesInserts b. lldpStatsRemTablesDeletes c. lldpStatsRemTablesDrops d. lldpStatsRemTablesAgeouts e. lldpStatsRxPortAgeoutsTotal for all ports. 2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations. 3. NMS receives the notifications and compares the new values of objects listed in step 1.  Periodically, NMS should poll the object lldpStatsRemTablesLastChangeTime to find out if anything has changed since the last poll. if something has changed, NMS will poll the objects listed in step 1 to figure out what kind of changes occurred in the tables. if value of lldpStatsRemTablesInserts has changed, then NMS will walk all tables by employing TimeFilter with the last-polled time value. This request will return new objects or objects whose values are updated since the last poll. if value of lldpStatsRemTablesAgeouts has changed, then NMS will walk the lldpStatsRxPortAgeoutsTotal and compare the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS will have to retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter.) lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops objects are provided for informational purposes.
.1.0.8802.1.1.2.1.4.1.1,LLDP-MIB::lldpRemEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about a particular physical network connection. Entries may be created and deleted in this table by the agent, if a physical topology discovery process is active.
.1.0.8802.1.1.2.1.4.1.1.1,LLDP-MIB::lldpRemTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention in IETF RFC 2021 and  http://www.ietf.org/IESG/Implementations/RFC2021-Implementation.txt to see how TimeFilter works.
.1.0.8802.1.1.2.1.4.1.1.2,LLDP-MIB::lldpRemLocalPortNum,Integer32,not-accessible,,current,,The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The lldpRemLocalPortNum identifies the port on which the remote system information is received. The value of this object is used as a port index to the lldpRemTable.
.1.0.8802.1.1.2.1.4.1.1.3,LLDP-MIB::lldpRemIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemIndex will wrap between reboots.
.1.0.8802.1.1.2.1.4.1.1.4,LLDP-MIB::lldpRemChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),The type of encoding used to identify the chassis associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.5,LLDP-MIB::lldpRemChassisId,OCTET,read-only,,current,,The string value used to identify the chassis component associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.6,LLDP-MIB::lldpRemPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),The type of port identifier encoding used in the associated 'lldpRemPortId' object.
.1.0.8802.1.1.2.1.4.1.1.7,LLDP-MIB::lldpRemPortId,OCTET,read-only,,current,,The string value used to identify the port component associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.8,LLDP-MIB::lldpRemPortDesc,OCTET,read-only,,current,,The string value used to identify the description of the given port associated with the remote system.
.1.0.8802.1.1.2.1.4.1.1.9,LLDP-MIB::lldpRemSysName,OCTET,read-only,,current,,The string value used to identify the system name of the remote system.
.1.0.8802.1.1.2.1.4.1.1.10,LLDP-MIB::lldpRemSysDesc,OCTET,read-only,,current,,The string value used to identify the system description of the remote system.
.1.0.8802.1.1.2.1.4.1.1.11,LLDP-MIB::lldpRemSysCapSupported,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are supported on the remote system.
.1.0.8802.1.1.2.1.4.1.1.12,LLDP-MIB::lldpRemSysCapEnabled,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7),The bitmap value used to identify which system capabilities are enabled on the remote system.
.1.0.8802.1.1.2.1.4.2,LLDP-MIB::lldpRemManAddrTable,,not-accessible,,current,,This table contains one or more rows per management address information on the remote system learned on a particular port contained in the local chassis known to this agent.
.1.0.8802.1.1.2.1.4.2.1,LLDP-MIB::lldpRemManAddrEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpRemManAddrSubtype:lldpRemManAddr,current,,Management address information about a particular chassis component. There may be multiple management addresses configured on the remote system identified by a particular lldpRemIndex whose information is received on lldpRemLocalPortNum of the local system. Each management address should have distinct 'management address type' (lldpRemManAddrSubtype) and 'management address' (lldpRemManAddr.) Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.4.2.1.1,LLDP-MIB::lldpRemManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpRemManagmentAddr' object.
.1.0.8802.1.1.2.1.4.2.1.2,LLDP-MIB::lldpRemManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the remote system. The purpose of this address is to contact the management entity.
.1.0.8802.1.1.2.1.4.2.1.3,LLDP-MIB::lldpRemManAddrIfSubtype,INTEGER,read-only,,current,unknown(1):ifIndex(2):systemPortNumber(3),The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the remote system.
.1.0.8802.1.1.2.1.4.2.1.4,LLDP-MIB::lldpRemManAddrIfId,Integer32,read-only,,current,,The integer value used to identify the interface number regarding the management address component associated with the remote system.
.1.0.8802.1.1.2.1.4.2.1.5,LLDP-MIB::lldpRemManAddrOID,OBJECT,read-only,,current,,The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the remote system agent.
.1.0.8802.1.1.2.1.4.3,LLDP-MIB::lldpRemUnknownTLVTable,,not-accessible,,current,,This table contains information about an incoming TLV which is not recognized by the receiving LLDP agent. The TLV may be from a later version of the basic management set. This table should only contain TLVs that are found in a single LLDP frame. Entries in this table, associated with an MAC service access point (MSAP, the access point for MAC services provided to the LCC sublayer, defined in IEEE 100, which is also identified with a particular lldpRemLocalPortNum, lldpRemIndex pair) are overwritten with most recently received unrecognized TLV from the same MSAP, or they will naturally age out when the rxInfoTTL timer (associated with the MSAP) expires.
.1.0.8802.1.1.2.1.4.3.1,LLDP-MIB::lldpRemUnknownTLVEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpRemUnknownTLVType,current,,Information about an unrecognized TLV received from a physical network connection. Entries may be created and deleted in this table by the agent, if a physical topology discovery process is active.
.1.0.8802.1.1.2.1.4.3.1.1,LLDP-MIB::lldpRemUnknownTLVType,Integer32,not-accessible,,current,,This object represents the value extracted from the type field of the TLV.
.1.0.8802.1.1.2.1.4.3.1.2,LLDP-MIB::lldpRemUnknownTLVInfo,OCTET,read-only,,current,,This object represents the value extracted from the value field of the TLV.
.1.0.8802.1.1.2.1.4.4,LLDP-MIB::lldpRemOrgDefInfoTable,,not-accessible,,current,,This table contains one or more rows per physical network connection which advertises the organizationally defined information. Note that this table contains one or more rows of organizationally defined information that is not recognized by the local agent. If the local system is capable of recognizing any organizationally defined information, appropriate extension MIBs from the organization should be used for information retrieval.
.1.0.8802.1.1.2.1.4.4.1,LLDP-MIB::lldpRemOrgDefInfoEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpRemOrgDefInfoOUI:lldpRemOrgDefInfoSubtype:lldpRemOrgDefInfoIndex,current,,Information about the unrecognized organizationally defined information advertised by the remote system. The lldpRemTimeMark, lldpRemLocalPortNum, lldpRemIndex, lldpRemOrgDefInfoOUI, lldpRemOrgDefInfoSubtype, and lldpRemOrgDefInfoIndex are indexes to this table. If there is an lldpRemOrgDefInfoEntry associated with a particular remote system identified by the lldpRemLocalPortNum and lldpRemIndex, there must be an lldpRemEntry associated with the same instance (i.e, using same indexes.) When the lldpRemEntry for the same index is removed from the lldpRemTable, the associated lldpRemOrgDefInfoEntry should be removed from the lldpRemOrgDefInfoTable. Entries may be created and deleted in this table by the agent.
.1.0.8802.1.1.2.1.4.4.1.1,LLDP-MIB::lldpRemOrgDefInfoOUI,OCTET,not-accessible,,current,,The Organizationally Unique Identifier (OUI), as defined in IEEE std 802-2001, is a 24 bit (three octets) globally unique assigned number referenced by various standards, of the information received from the remote system.
.1.0.8802.1.1.2.1.4.4.1.2,LLDP-MIB::lldpRemOrgDefInfoSubtype,Integer32,not-accessible,,current,,The integer value used to identify the subtype of the organizationally defined information received from the remote system. The subtype value is required to identify different instances of organizationally defined information that could not be retrieved without a unique identifier that indicates the particular type of information contained in the information string.
.1.0.8802.1.1.2.1.4.4.1.3,LLDP-MIB::lldpRemOrgDefInfoIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular unrecognized organizationally defined information instance, unique only for the lldpRemOrgDefInfoOUI and lldpRemOrgDefInfoSubtype from the same remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemOrgDefInfoIndex will wrap between reboots.
.1.0.8802.1.1.2.1.4.4.1.4,LLDP-MIB::lldpRemOrgDefInfo,OCTET,read-only,,current,,The string value used to identify the organizationally defined information of the remote system. The encoding for this object should be as defined for SnmpAdminString TC.
.1.0.8802.1.1.2.1.5,LLDP-MIB::lldpExtensions,,,,,,
.1.0.8802.1.1.2.1.5.4623,LLDP-EXT-DOT3-MIB::lldpXdot3MIB,,,,,,The LLDP Management Information Base extension module for IEEE 802.3 organizationally defined discovery information. In order to assure the uniqueness of the LLDP-MIB, lldpXdot3MIB is branched from lldpExtensions using OUI value as the node. An OUI/'company_id' is a 24 bit globally unique assigned number referenced by various standards. Copyright (C) IEEE (2005). This version of this MIB module is published as Annex G.6.1 of IEEE Std 802.1AB-2005; see the standard itself for full legal notices.
.1.0.8802.1.1.2.1.5.4623.1,LLDP-EXT-DOT3-MIB::lldpXdot3Objects,,,,,,
.1.0.8802.1.1.2.1.5.4623.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3Config,,,,,,
.1.0.8802.1.1.2.1.5.4623.1.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3PortConfigTable,,not-accessible,,current,,A table that controls selection of LLDP TLVs to be transmitted  on individual ports.
.1.0.8802.1.1.2.1.5.4623.1.1.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3PortConfigEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.3 organizationally defined TLVs on LLDP transmission capable ports. This configuration object augments the lldpPortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpPortConfigEntry entry. Each active lldpXdot3PortConfigEntry must be from non-volatile storage (along with the corresponding lldpPortConfigEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.4623.1.1.1.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3PortConfigTLVsTxEnable,BITS,read-write,,current,macPhyConfigStatus(0):powerViaMDI(1):linkAggregation(2):maxFrameSize(3),The lldpXdot3PortConfigTLVsTxEnable, defined as a bitmap, includes the IEEE 802.3 organizationally defined set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to an IEEE 802.3 subtype associated with a specific IEEE 802.3 optional TLV. The bit 0 is not used since there is no corresponding subtype. The bit 'macPhyConfigStatus(0)' indicates that LLDP agent should transmit 'MAC/PHY configuration/status TLV'. The bit 'powerViaMDI(1)' indicates that LLDP agent should transmit 'Power via MDI TLV'. The bit 'linkAggregation(2)' indicates that LLDP agent should transmit 'Link Aggregation TLV'. The bit 'maxFrameSize(3)' indicates that LLDP agent should transmit 'Maximum-frame-size TLV'. The default value for lldpXdot3PortConfigTLVsTxEnable object is an empty set, which means no enumerated values are set. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.4623.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3LocalData,,,,,,
.1.0.8802.1.1.2.1.5.4623.1.2.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocPortTable,,not-accessible,,current,,This table contains one row per port of Ethernet port information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.0.8802.1.1.2.1.5.4623.1.2.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocPortEntry,,not-accessible,lldpLocPortNum,current,,Information about a particular port component.
.1.0.8802.1.1.2.1.5.4623.1.2.1.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocPortAutoNegSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with the local system) supports Auto-negotiation.
.1.0.8802.1.1.2.1.5.4623.1.2.1.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3LocPortAutoNegEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether port Auto-negotiation is enabled on the given port associated with the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.1.1.3,LLDP-EXT-DOT3-MIB::lldpXdot3LocPortAutoNegAdvertisedCap,OCTET,read-only,,current,,This object contains the value (bitmap) of the ifMauAutoNegCapAdvertisedBits object (defined in IETF RFC 3636) which is associated with the given port on the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.1.1.4,LLDP-EXT-DOT3-MIB::lldpXdot3LocPortOperMauType,Integer32,read-only,,current,,An integer value that indicates the operational MAU type of the given port on the local system. This object contains the integer value derived from the list position of the corresponding dot3MauType as listed  in IETF RFC 3636 (or subsequent revisions) and is equal to the last number in the respective dot3MauType OID.  For example, if the ifMauType object is dot3MauType1000BaseTHD which corresponds to {dot3MauType 29}, the numerical value of this field will be 29. For MAU types not listed in RFC 3636 (or subsequent revisions), the value of this field shall be set to zero.
.1.0.8802.1.1.2.1.5.4623.1.2.2,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerTable,,not-accessible,,current,,This table contains one row per port of power ethernet  information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerEntry,,not-accessible,lldpLocPortNum,current,,Information about a particular port component.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerPortClass,INTEGER,read-only,,current,pClassPSE(1):pClassPD(2),The value that identifies the port Class of the given port associated with the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerMDISupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is supported on the given port associated with the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1.3,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerMDIEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to identify whether MDI power is enabled on the given port associated with the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1.4,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerPairControlable,INTEGER,read-only,,current,true(1):false(2),The truth value is derived from the value of pethPsePortPowerPairsControlAbility object (defined in IETF RFC 3621) and is used to indicate whether the pair selection can be controlled on the given port associated with the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1.5,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerPairs,Integer32,read-only,,current,,This object contains the value of the pethPsePortPowerPairs object (defined in IETF RFC 3621) which is associated with the given port on the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.2.1.6,LLDP-EXT-DOT3-MIB::lldpXdot3LocPowerClass,Integer32,read-only,,current,,This object contains the value of the pethPsePortPowerClassifications object (defined in IETF RFC 3621) which is associated with the given port on the local system.
.1.0.8802.1.1.2.1.5.4623.1.2.3,LLDP-EXT-DOT3-MIB::lldpXdot3LocLinkAggTable,,not-accessible,,current,,This table contains one row per port of link aggregation  information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.0.8802.1.1.2.1.5.4623.1.2.3.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocLinkAggEntry,,not-accessible,lldpLocPortNum,current,,Link Aggregation information about a particular port component.
.1.0.8802.1.1.2.1.5.4623.1.2.3.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocLinkAggStatus,BITS,read-only,,current,aggCapable(0):aggEnabled(1),The bitmap value contains the link aggregation capabilities and the current aggregation status of the link.
.1.0.8802.1.1.2.1.5.4623.1.2.3.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3LocLinkAggPortId,Integer32,read-only,,current,,This object contains the IEEE 802.3 aggregated port identifier, aAggPortID (IEEE 802.3-2002, 30.7.2.1.1), derived from the ifNumber of the ifIndex for the port component in link aggregation. If the port is not in link aggregation state and/or it does not support link aggregation, this value should be set to zero.
.1.0.8802.1.1.2.1.5.4623.1.2.4,LLDP-EXT-DOT3-MIB::lldpXdot3LocMaxFrameSizeTable,,not-accessible,,current,,This table contains one row per port of maximum frame  size information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.0.8802.1.1.2.1.5.4623.1.2.4.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocMaxFrameSizeEntry,,not-accessible,lldpLocPortNum,current,,Maximum Frame Size information about a particular port component.
.1.0.8802.1.1.2.1.5.4623.1.2.4.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3LocMaxFrameSize,Integer32,read-only,,current,,An integer value indicating the maximum supported frame  size in octets on the given port of the local system.
.1.0.8802.1.1.2.1.5.4623.1.3,LLDP-EXT-DOT3-MIB::lldpXdot3RemoteData,,,,,,
.1.0.8802.1.1.2.1.5.4623.1.3.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemPortTable,,not-accessible,,current,,This table contains Ethernet port information (as a part of the LLDP 802.3 organizational extension) of the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemPortEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about a particular physical network connection.
.1.0.8802.1.1.2.1.5.4623.1.3.1.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemPortAutoNegSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with remote system) supports Auto-negotiation.
.1.0.8802.1.1.2.1.5.4623.1.3.1.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3RemPortAutoNegEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether port Auto-negotiation is enabled on the given port associated with the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.1.1.3,LLDP-EXT-DOT3-MIB::lldpXdot3RemPortAutoNegAdvertisedCap,OCTET,read-only,,current,,This object contains the value (bitmap) of the ifMauAutoNegCapAdvertisedBits object (defined in IETF RFC 3636) which is associated with the given port on the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.1.1.4,LLDP-EXT-DOT3-MIB::lldpXdot3RemPortOperMauType,Integer32,read-only,,current,,An integer value that indicates the operational MAU type of the sending device. This object contains the integer value derived from the list position of the corresponding dot3MauType as listed in in IETF RFC 3636 (or subsequent revisions) and is equal to the last number in the respective dot3MauType OID.  For example, if the ifMauType object is dot3MauType1000BaseTHD which corresponds to {dot3MauType 29}, the numerical value of this field will be 29. For MAU types not listed in RFC 3636 (or subsequent revisions), the value of this field shall be set to zero.
.1.0.8802.1.1.2.1.5.4623.1.3.2,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerTable,,not-accessible,,current,,This table contains Ethernet power information (as a part of the LLDP 802.3 organizational extension) of the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about a particular physical network connection.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerPortClass,INTEGER,read-only,,current,pClassPSE(1):pClassPD(2),The value that identifies the port Class of the given port associated with the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerMDISupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is supported on the given port associated with the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1.3,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerMDIEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to identify whether MDI power is enabled on the given port associated with the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1.4,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerPairControlable,INTEGER,read-only,,current,true(1):false(2),The truth value is derived from the value of pethPsePortPowerPairsControlAbility object (defined in IETF RFC 3621) and is used to indicate whether the pair selection can be controlled on the given port associated with the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1.5,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerPairs,Integer32,read-only,,current,,This object contains the value of the pethPsePortPowerPairs object (defined in IETF RFC 3621) which is associated with the given port on the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.2.1.6,LLDP-EXT-DOT3-MIB::lldpXdot3RemPowerClass,Integer32,read-only,,current,,This object contains the value of the pethPsePortPowerClassifications object (defined in IETF RFC 3621) which is associated with the given port on the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.3,LLDP-EXT-DOT3-MIB::lldpXdot3RemLinkAggTable,,not-accessible,,current,,This table contains port link aggregation information (as a part of the LLDP 802.3 organizational extension) of the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.3.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemLinkAggEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Link Aggregation information about remote system's port component.
.1.0.8802.1.1.2.1.5.4623.1.3.3.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemLinkAggStatus,BITS,read-only,,current,aggCapable(0):aggEnabled(1),The bitmap value contains the link aggregation capabilities and the current aggregation status of the link.
.1.0.8802.1.1.2.1.5.4623.1.3.3.1.2,LLDP-EXT-DOT3-MIB::lldpXdot3RemLinkAggPortId,Integer32,read-only,,current,,This object contains the IEEE 802.3 aggregated port identifier, aAggPortID (IEEE 802.3-2002, 30.7.2.1.1), derived from the ifNumber of the ifIndex for the port component associated with the remote system. If the remote port is not in link aggregation state and/or it does not support link aggregation, this value should be zero.
.1.0.8802.1.1.2.1.5.4623.1.3.4,LLDP-EXT-DOT3-MIB::lldpXdot3RemMaxFrameSizeTable,,not-accessible,,current,,This table contains one row per port of maximum frame  size information (as a part of the LLDP 802.3 organizational extension) of the remote system.
.1.0.8802.1.1.2.1.5.4623.1.3.4.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemMaxFrameSizeEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Maximum Frame Size information about a particular port component.
.1.0.8802.1.1.2.1.5.4623.1.3.4.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3RemMaxFrameSize,Integer32,read-only,,current,,An integer value indicating the maximum supported frame  size in octets on the port component associated with the  remote system.
.1.0.8802.1.1.2.1.5.4623.2,LLDP-EXT-DOT3-MIB::lldpXdot3Conformance,,,,,,
.1.0.8802.1.1.2.1.5.4623.2.1,LLDP-EXT-DOT3-MIB::lldpXdot3Compliances,,,,,,
.1.0.8802.1.1.2.1.5.4623.2.1.1,LLDP-EXT-DOT3-MIB::lldpXdot3Compliance,,,,,,The compliance statement for SNMP entities which implement the LLDP 802.3 organizational extension MIB.
.1.0.8802.1.1.2.1.5.4623.2.2,LLDP-EXT-DOT3-MIB::lldpXdot3Groups,,,,,,
.1.0.8802.1.1.2.1.5.4623.2.2.1,LLDP-EXT-DOT3-MIB::lldpXdot3ConfigGroup,,,,,,The collection of objects which are used to configure the LLDP 802.3 organizational extension implementation behavior. This group is mandatory for agents which implement the  LLDP 802.3 organizational extension.
.1.0.8802.1.1.2.1.5.4623.2.2.2,LLDP-EXT-DOT3-MIB::lldpXdot3LocSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.3 organizational extension Local Device Information.  This group is mandatory for agents which implement the  LLDP 802.3 organizational extension in the TX mode.
.1.0.8802.1.1.2.1.5.4623.2.2.3,LLDP-EXT-DOT3-MIB::lldpXdot3RemSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.3 organizational extension Local Device Information.  This group is mandatory for agents which implement the  LLDP 802.3 organizational extension in the RX mode.
.1.0.8802.1.1.2.1.5.4795,LLDP-EXT-MED-MIB::lldpXMedMIB,,,,,,The LLDP Management Information Base extension module for TIA-TR41.4 Media Endpoint Discovery information. In order to assure the uniqueness of the LLDP-MIB, lldpXMedMIB is branched from lldpExtensions using the TIA OUI value as the node. An OUI/'company_id' is a 24 bit globally unique assigned number referenced by various standards. Copyright (C) TIA (2005). This version of this MIB module is published as Section 13.3 of ANSI/TIA-1057. See the standard itself for full legal notices.
.1.0.8802.1.1.2.1.5.4795.0,LLDP-EXT-MED-MIB::lldpXMedNotifications,,,,,,
.1.0.8802.1.1.2.1.5.4795.0.1,LLDP-EXT-MED-MIB::lldpXMedTopologyChangeDetected,,,,,,A notification generated by the local device sensing a change in the topology that indicates that a new remote device attached to a local port, or a remote device disconnected or moved from one port to another.
.1.0.8802.1.1.2.1.5.4795.1,LLDP-EXT-MED-MIB::lldpXMedObjects,,,,,,
.1.0.8802.1.1.2.1.5.4795.1.1,LLDP-EXT-MED-MIB::lldpXMedConfig,,,,,,
.1.0.8802.1.1.2.1.5.4795.1.1.1,LLDP-EXT-MED-MIB::lldpXMedLocDeviceClass,INTEGER,read-only,,current,notDefined(0):endpointClass1(1):endpointClass2(2):endpointClass3(3):networkConnectivity(4),Local Device Class.
.1.0.8802.1.1.2.1.5.4795.1.1.2,LLDP-EXT-MED-MIB::lldpXMedPortConfigTable,,not-accessible,,current,,A table that controls selection of LLDP TLVs to be transmitted on individual ports.
.1.0.8802.1.1.2.1.5.4795.1.1.2.1,LLDP-EXT-MED-MIB::lldpXMedPortConfigEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of the MED organizationally defined TLVs on LLDP transmission capable ports. This configuration object augments the lldpPortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpPortConfigEntry entry. Each active lldpXMedPortConfigEntry must be stored and retrieved from non-volatile storage (along with the corresponding lldpPortConfigEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.4795.1.1.2.1.1,LLDP-EXT-MED-MIB::lldpXMedPortCapSupported,BITS,read-only,,current,capabilities(0):networkPolicy(1):location(2):extendedPSE(3):extendedPD(4):inventory(5),The bitmap includes the MED organizationally defined set of LLDP TLVs whose transmission is possible for the respective port on the LLDP agent of the device. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent supports the corresponding TLV.
.1.0.8802.1.1.2.1.5.4795.1.1.2.1.2,LLDP-EXT-MED-MIB::lldpXMedPortConfigTLVsTxEnable,BITS,read-write,,current,capabilities(0):networkPolicy(1):location(2):extendedPSE(3):extendedPD(4):inventory(5),The lldpXMedPortConfigTLVsTxEnable, defined as a bitmap, includes the MED organizationally defined set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent will send the corresponding TLV if the respective capability is supported per port. Setting a bit with in this object for a non-supported capability shall have no functional effect and will result in an inconsistent value error returned to the management application. There are other rules and restrictions that prevent arbitrary combinations of TLVs to be enabled on LLDP-MED devices according to the device classes. These rules are defined in Section 10.2.1, Tables 5 - 9 of ANSI/TIA-1057. In case a management application attempts to set this object to a value that does not follow the rules, the set operation shall have and will result in an inconsistent value error returned to the management application. Setting this object to an empty set is valid and effectively disables LLDP-MED on a per-port basis by disabling transmission of all MED organizational TLVs. In this case the remote tables objects in the LLDP-MED MIB corresponding to the respective port will not be populated. The default value for lldpXMedPortConfigTLVsTxEnable object is an empty set, which means no enumerated values are set. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.4795.1.1.2.1.3,LLDP-EXT-MED-MIB::lldpXMedPortConfigNotifEnable,INTEGER,read-write,,current,true(1):false(2),A value of 'true(1)' enables sending the topology change traps on this port. A value of 'false(2)' disables sending the topology change traps on this port.
.1.0.8802.1.1.2.1.5.4795.1.1.3,LLDP-EXT-MED-MIB::lldpXMedFastStartRepeatCount,Unsigned32,read-write,,current,,The number of times the fast start LLDPDU are being sent during the activation of the fast start mechanism defined by LLDP-MED.
.1.0.8802.1.1.2.1.5.4795.1.2,LLDP-EXT-MED-MIB::lldpXMedLocalData,,,,,,
.1.0.8802.1.1.2.1.5.4795.1.2.1,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyTable,,not-accessible,,current,,This table contains one row per policy type per port of media policy information (as a part of the MED organizational extension) on the local system known to this agent.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyEntry,,not-accessible,lldpLocPortNum:lldpXMedLocMediaPolicyAppType,current,,Information about a particular policy on a specific port component.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1.1,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyAppType,BITS,not-accessible,,current,unknown(0):voice(1):voiceSignaling(2):guestVoice(3):guestVoiceSignaling(4):softPhoneVoice(5):videoconferencing(6):streamingVideo(7):videoSignaling(8),The media type that defines the primary function of the application for the policy advertised by an endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1.2,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyVlanID,Integer32,read-only,,current,,An extension of the VLAN Identifier for the port, as defined in IEEE 802.1P-1998. A value of 1 through 4094 is used to define a valid PVID. A value of 0 shall be used if the device is using priority tagged frames, meaning that only the 802.1p priority level is significant and the default VID of the ingress port is being used instead. A value of 4095 is reserved for implementation use.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1.3,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyPriority,Integer32,read-only,,current,,This object contains the value of the 802.1p priority which is associated with the given port on the local system.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1.4,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyDscp,Integer32,read-only,,current,,This object contains the value of the Differentiated Service Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475 which is associated with the given port on the local system.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1.5,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyUnknown,INTEGER,read-only,,current,true(1):false(2),A value of 'true' indicates that the network policy for the specified application type is currently unknown. In this case, the VLAN ID, the layer 2 priority and the DSCP value fields are ignored. A value of 'false' indicates that this network policy is defined.
.1.0.8802.1.1.2.1.5.4795.1.2.1.1.6,LLDP-EXT-MED-MIB::lldpXMedLocMediaPolicyTagged,INTEGER,read-only,,current,true(1):false(2),A value of 'true' indicates that the application is using a tagged VLAN. A value of 'false' indicates that for the specific application the device either is using an untagged VLAN or does not support port based VLAN operation. In this case, both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP value has relevance.
.1.0.8802.1.1.2.1.5.4795.1.2.2,LLDP-EXT-MED-MIB::lldpXMedLocHardwareRev,OCTET,read-only,,current,,The vendor-specific hardware revision string as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.3,LLDP-EXT-MED-MIB::lldpXMedLocFirmwareRev,OCTET,read-only,,current,,The vendor-specific firmware revision string as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.4,LLDP-EXT-MED-MIB::lldpXMedLocSoftwareRev,OCTET,read-only,,current,,The vendor-specific software revision string as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.5,LLDP-EXT-MED-MIB::lldpXMedLocSerialNum,OCTET,read-only,,current,,The vendor-specific serial number as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.6,LLDP-EXT-MED-MIB::lldpXMedLocMfgName,OCTET,read-only,,current,,The vendor-specific manufacturer name as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.7,LLDP-EXT-MED-MIB::lldpXMedLocModelName,OCTET,read-only,,current,,The vendor-specific model name as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.8,LLDP-EXT-MED-MIB::lldpXMedLocAssetID,OCTET,read-only,,current,,The vendor-specific asset tracking identifier as advertised by the endpoint.
.1.0.8802.1.1.2.1.5.4795.1.2.9,LLDP-EXT-MED-MIB::lldpXMedLocLocationTable,,not-accessible,,current,,This table contains Location information as advertised by the local system. The information may be configured per port by a Location Information Server (LIS) or other management application. Multiple Location TLVs of different subtypes may be transmitted in the same PDU. The information in this table MUST be stored in non-volatile-memory and persist over restart/reboot sequences.
.1.0.8802.1.1.2.1.5.4795.1.2.9.1,LLDP-EXT-MED-MIB::lldpXMedLocLocationEntry,,not-accessible,lldpLocPortNum:lldpXMedLocLocationSubtype,current,,Information about Location information for the local device.
.1.0.8802.1.1.2.1.5.4795.1.2.9.1.1,LLDP-EXT-MED-MIB::lldpXMedLocLocationSubtype,INTEGER,not-accessible,,current,unknown(1):coordinateBased(2):civicAddress(3):elin(4),The location subtype advertised by the local device.
.1.0.8802.1.1.2.1.5.4795.1.2.9.1.2,LLDP-EXT-MED-MIB::lldpXMedLocLocationInfo,OCTET,read-write,,current,,The location information. Parsing of this information is dependent upon the location subtype, as defined by the value of the lldpXMedLocLocationSubtype object.
.1.0.8802.1.1.2.1.5.4795.1.2.10,LLDP-EXT-MED-MIB::lldpXMedLocXPoEDeviceType,INTEGER,read-only,,current,unknown(1):pseDevice(2):pdDevice(3):none(4),Defines the type of Power-via-MDI (Power over Ethernet) advertised by the local device. A value pseDevice(2) indicates that the device is advertised as a Power Sourcing Entity (PSE). A value pdDevice(3) indicates that the device is advertised as a Powered Device (PD). A value of none(4) indicates that the device does not support PoE.
.1.0.8802.1.1.2.1.5.4795.1.2.11,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPSEPortTable,,not-accessible,,current,,This table contains one row per port of PSE PoE information on the local system known to this agent.
.1.0.8802.1.1.2.1.5.4795.1.2.11.1,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPSEPortEntry,,not-accessible,lldpLocPortNum,current,,Information about a particular port PoE information.
.1.0.8802.1.1.2.1.5.4795.1.2.11.1.1,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPSEPortPowerAv,Gauge32,read-only,,current,,This object contains the value of the power available from the PSE via this port expressed in units of 0.1 watts.
.1.0.8802.1.1.2.1.5.4795.1.2.11.1.2,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPSEPortPDPriority,INTEGER,read-only,,current,unknown(1):critical(2):high(3):low(4),Reflects the PD power priority that is being advertised on this PSE port. If both locally configure priority and ldpXMedRemXPoEPDPowerPriority are available on this port, it is a matter of local policy which one takes precedence. This object reflects the active value on this port. If the priority is not configured or known by the PD, the value unknown(1) will be returned. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621.
.1.0.8802.1.1.2.1.5.4795.1.2.12,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPSEPowerSource,INTEGER,read-only,,current,unknown(1):primary(2):backup(3),Defines the type of PSE Power Source advertised by the local device. A value primary(2) indicates that the device advertises its power source as primary. A value backup(3) indicates that the device advertises its power Source as backup.
.1.0.8802.1.1.2.1.5.4795.1.2.13,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPDPowerReq,Gauge32,read-only,,current,,This object contains the value of the power required by a PD expressed in units of 0.1 watts.
.1.0.8802.1.1.2.1.5.4795.1.2.14,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPDPowerSource,INTEGER,read-only,,current,unknown(1):fromPSE(2):local(3):localAndPSE(4),Defines the type of Power Source advertised as being used by the local device. A value fromPSE(2) indicates that the device advertises its power source as received from a PSE. A value local(3) indicates that the device advertises its power source as local. A value localAndPSE(4) indicates that the device advertises its power source as using both local and PSE power.
.1.0.8802.1.1.2.1.5.4795.1.2.15,LLDP-EXT-MED-MIB::lldpXMedLocXPoEPDPowerPriority,INTEGER,read-only,,current,unknown(1):critical(2):high(3):low(4),Defines the priority advertised as being required by this PD. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621.
.1.0.8802.1.1.2.1.5.4795.1.3,LLDP-EXT-MED-MIB::lldpXMedRemoteData,,,,,,
.1.0.8802.1.1.2.1.5.4795.1.3.1,LLDP-EXT-MED-MIB::lldpXMedRemCapabilitiesTable,,not-accessible,,current,,A table that displays LLDP-MED capabilities of remote devices connected to individual ports.
.1.0.8802.1.1.2.1.5.4795.1.3.1.1,LLDP-EXT-MED-MIB::lldpXMedRemCapabilitiesEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,LLDP-MED capabilities of remote devices connected to the device ports and communicating via LLDP-MED. The remote tables in the LLDP-MED MIB excepting this table may be sparsely populate. An entry in one of these table is meaningful and shall be populated by the agent only if the corresponding bits for the respective function are set in the objects in this table.
.1.0.8802.1.1.2.1.5.4795.1.3.1.1.1,LLDP-EXT-MED-MIB::lldpXMedRemCapSupported,BITS,read-only,,current,capabilities(0):networkPolicy(1):location(2):extendedPSE(3):extendedPD(4):inventory(5),The bitmap includes the MED organizationally defined set of LLDP TLVs whose transmission is possible on the LLDP agent of the remote device connected to this port. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent has the capability to support the corresponding TLV.
.1.0.8802.1.1.2.1.5.4795.1.3.1.1.2,LLDP-EXT-MED-MIB::lldpXMedRemCapCurrent,BITS,read-only,,current,capabilities(0):networkPolicy(1):location(2):extendedPSE(3):extendedPD(4):inventory(5),The bitmap includes the MED organizationally defined set of LLDP TLVs whose transmission is possible on the LLDP agent of the remote device connected to this port. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent currently supports the corresponding TLV.
.1.0.8802.1.1.2.1.5.4795.1.3.1.1.3,LLDP-EXT-MED-MIB::lldpXMedRemDeviceClass,INTEGER,read-only,,current,notDefined(0):endpointClass1(1):endpointClass2(2):endpointClass3(3):networkConnectivity(4),Device Class as advertised by the device remotely connected to the port.
.1.0.8802.1.1.2.1.5.4795.1.3.2,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyTable,,not-accessible,,current,,This table contains media policy information as advertised by the remote system. This table may be sparsely populated. Entries in this table are relevant only if the networkPolicy(0) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpXMedRemMediaPolicyAppType,current,,Information about the per port per policy type policy information for a particular physical network connection.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1.1,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyAppType,BITS,not-accessible,,current,unknown(0):voice(1):voiceSignaling(2):guestVoice(3):guestVoiceSignaling(4):softPhoneVoice(5):videoconferencing(6):streamingVideo(7):videoSignaling(8),The media type that defines the primary function of the application for the policy advertised by the endpoint connected remotely to this port.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1.2,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyVlanID,Integer32,read-only,,current,,An extension of the VLAN Identifier for the remote system connected to this port, as defined in IEEE 802.1P-1998. A value of 1 through 4094 is used to define a valid PVID. A value of 0 shall be used if the device is using priority tagged frames, meaning that only the 802.1p priority level is significant and the default VID of the ingress port is being used instead. A value of 4095 is reserved for implementation use.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1.3,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyPriority,Integer32,read-only,,current,,This object contains the value of the 802.1p priority which is associated with the remote system connected at given port.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1.4,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyDscp,Integer32,read-only,,current,,This object contains the value of the Differentiated Service Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475 which is associated with remote system connected at the port.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1.5,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyUnknown,INTEGER,read-only,,current,true(1):false(2),A value of 'true' indicates that the network policy for the specified application type is currently unknown. In this case, the VLAN ID, the layer 2 priority and the DSCP value fields are ignored. A value of 'false' indicates that this network policy is defined.
.1.0.8802.1.1.2.1.5.4795.1.3.2.1.6,LLDP-EXT-MED-MIB::lldpXMedRemMediaPolicyTagged,INTEGER,read-only,,current,true(1):false(2),A value of 'true' indicates that the application is using a tagged VLAN. A value of 'false' indicates that for the specific application the device either is using an untagged VLAN or does not support port based VLAN operation. In this case, both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP value has relevance.
.1.0.8802.1.1.2.1.5.4795.1.3.3,LLDP-EXT-MED-MIB::lldpXMedRemInventoryTable,,not-accessible,,current,,This table contains inventory information as advertised by the remote system. This table may be sparsely populated. Entries in this table are relevant only if the inventory(2) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1,LLDP-EXT-MED-MIB::lldpXMedRemInventoryEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about inventory information for the remote devices connected to the ports.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.1,LLDP-EXT-MED-MIB::lldpXMedRemHardwareRev,OCTET,read-only,,current,,The vendor-specific hardware revision string as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.2,LLDP-EXT-MED-MIB::lldpXMedRemFirmwareRev,OCTET,read-only,,current,,The vendor-specific firmware revision string as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.3,LLDP-EXT-MED-MIB::lldpXMedRemSoftwareRev,OCTET,read-only,,current,,The vendor-specific software revision string as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.4,LLDP-EXT-MED-MIB::lldpXMedRemSerialNum,OCTET,read-only,,current,,The vendor-specific serial number as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.5,LLDP-EXT-MED-MIB::lldpXMedRemMfgName,OCTET,read-only,,current,,The vendor-specific manufacturer name as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.6,LLDP-EXT-MED-MIB::lldpXMedRemModelName,OCTET,read-only,,current,,The vendor-specific model name as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.3.1.7,LLDP-EXT-MED-MIB::lldpXMedRemAssetID,OCTET,read-only,,current,,The vendor-specific asset tracking identifier as advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.4,LLDP-EXT-MED-MIB::lldpXMedRemLocationTable,,not-accessible,,current,,This table contains Location information as advertised by the remote system. This table may be sparsely populated. Entries in this table are relevant only if the Location(3) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set.
.1.0.8802.1.1.2.1.5.4795.1.3.4.1,LLDP-EXT-MED-MIB::lldpXMedRemLocationEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpXMedRemLocationSubtype,current,,Information about Location information for the remote devices connected to the ports.
.1.0.8802.1.1.2.1.5.4795.1.3.4.1.1,LLDP-EXT-MED-MIB::lldpXMedRemLocationSubtype,INTEGER,not-accessible,,current,unknown(1):coordinateBased(2):civicAddress(3):elin(4),The location subtype advertised by the remote endpoint.
.1.0.8802.1.1.2.1.5.4795.1.3.4.1.2,LLDP-EXT-MED-MIB::lldpXMedRemLocationInfo,OCTET,read-only,,current,,The location information advertised by the remote endpoint. Parsing of this information is dependent upon the location subtype, as defined by the value of the corresponding lldpXMedRemLocationSubType object. 
.1.0.8802.1.1.2.1.5.4795.1.3.5,LLDP-EXT-MED-MIB::lldpXMedRemXPoETable,,not-accessible,,current,,This table contains information about the PoE device type as advertised by the remote system. This table is densely populated.
.1.0.8802.1.1.2.1.5.4795.1.3.5.1,LLDP-EXT-MED-MIB::lldpXMedRemXPoEEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about PoE type of the remote devices connected to the ports.
.1.0.8802.1.1.2.1.5.4795.1.3.5.1.1,LLDP-EXT-MED-MIB::lldpXMedRemXPoEDeviceType,INTEGER,read-only,,current,unknown(1):pseDevice(2):pdDevice(3):none(4),Defines the type of Power-via-MDI (Power over Ethernet) advertised by the remote device. A value pseDevice(2) indicates that the device is advertised as a Power Sourcing Entity (PSE). A value pdDevice(3) indicates that the device is advertised as a Powered Device (PD). A value none(4) indicates that the device does not support PoE.
.1.0.8802.1.1.2.1.5.4795.1.3.6,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPSETable,,not-accessible,,current,,This table contains extended PoE information as advertised by the remote devices of PSE type. This table may be sparsely populated. Entries in this table are relevant only if the extendedPSE(4) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set.
.1.0.8802.1.1.2.1.5.4795.1.3.6.1,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPSEEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about Extended PoE PSE information for the remote devices connected to the ports.
.1.0.8802.1.1.2.1.5.4795.1.3.6.1.1,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPSEPowerAv,Gauge32,read-only,,current,,This object contains the value of the power available from the PSE via this port expressed in units of 0.1 watts on the remote device.
.1.0.8802.1.1.2.1.5.4795.1.3.6.1.2,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPSEPowerSource,INTEGER,read-only,,current,unknown(1):primary(2):backup(3),Defines the type of PSE Power Source advertised by the remote device. A value primary(2) indicates that the device advertises its power source as primary. A value backup(3) indicates that the device advertises its power Source as backup.
.1.0.8802.1.1.2.1.5.4795.1.3.6.1.3,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPSEPowerPriority,INTEGER,read-only,,current,unknown(1):critical(2):high(3):low(4),This object contains the value of the PSE power priority advertised by the remote device. A value critical(2) indicates that the device advertises its power priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power priority as low, as per RFC 3621.
.1.0.8802.1.1.2.1.5.4795.1.3.7,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPDTable,,not-accessible,,current,,This table contains extended PoE information as advertised by the remote devices of PD type. This table may be sparsely populated. Entries in this table are relevant only if the extendedPD(5) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set.
.1.0.8802.1.1.2.1.5.4795.1.3.7.1,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPDEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about XPoEPD information for the remote devices connected to the ports.
.1.0.8802.1.1.2.1.5.4795.1.3.7.1.1,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPDPowerReq,Gauge32,read-only,,current,,This object contains the value of the power required by a PD connected remotely to the port expressed in units of 0.1 watts.
.1.0.8802.1.1.2.1.5.4795.1.3.7.1.2,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPDPowerSource,INTEGER,read-only,,current,unknown(1):fromPSE(2):local(3):localAndPSE(4),Defines the type of Power Source advertised as being used by the device connected remotely to the port. A value fromPSE(2) indicates that the device advertises its power source as received from a PSE. A value local(3) indicates that the device advertises its power source as local. A value localAndPSE(4) indicates that the device advertises its power source as using both local and PSE power.
.1.0.8802.1.1.2.1.5.4795.1.3.7.1.3,LLDP-EXT-MED-MIB::lldpXMedRemXPoEPDPowerPriority,INTEGER,read-only,,current,unknown(1):critical(2):high(3):low(4),Defines the priority advertised as being required by the PD connected remotely to the port. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621.
.1.0.8802.1.1.2.1.5.4795.2,LLDP-EXT-MED-MIB::lldpXMedConformance,,,,,,
.1.0.8802.1.1.2.1.5.4795.2.1,LLDP-EXT-MED-MIB::lldpXMedCompliances,,,,,,
.1.0.8802.1.1.2.1.5.4795.2.1.1,LLDP-EXT-MED-MIB::lldpXMedCompliance,,,,,,The compliance statement for SNMP entities which implement the LLDP MED extension MIB.
.1.0.8802.1.1.2.1.5.4795.2.2,LLDP-EXT-MED-MIB::lldpXMedGroups,,,,,,
.1.0.8802.1.1.2.1.5.4795.2.2.1,LLDP-EXT-MED-MIB::lldpXMedConfigGroup,,,,,,The collection of objects which are used to configure or describe the configuration or behavior of the LLDP-MED organizational extension implementation.
.1.0.8802.1.1.2.1.5.4795.2.2.2,LLDP-EXT-MED-MIB::lldpXMedOptMediaPolicyGroup,,,,,,The collection of objects which are used to represent LLDP MED organizational extensions for Media Policy Information.
.1.0.8802.1.1.2.1.5.4795.2.2.3,LLDP-EXT-MED-MIB::lldpXMedOptInventoryGroup,,,,,,The collection of objects which are used to represent LLDP MED organizational extension for inventory Information.
.1.0.8802.1.1.2.1.5.4795.2.2.4,LLDP-EXT-MED-MIB::lldpXMedOptLocationGroup,,,,,,The collection of objects which are used to represent LLDP MED organizational extension for Location Information.
.1.0.8802.1.1.2.1.5.4795.2.2.5,LLDP-EXT-MED-MIB::lldpXMedOptPoEPSEGroup,,,,,,The collection of objects which are used to represent LLDP MED organizational extensions for PoE PSE Information.
.1.0.8802.1.1.2.1.5.4795.2.2.6,LLDP-EXT-MED-MIB::lldpXMedOptPoEPDGroup,,,,,,The collection of objects which are used to represent LLDP MED organizational extensions for PoE PD Information.
.1.0.8802.1.1.2.1.5.4795.2.2.7,LLDP-EXT-MED-MIB::lldpXMedRemSysGroup,,,,,,The collection of objects which are used to represent LLDP- MED organizational extension Remote Device Information.
.1.0.8802.1.1.2.1.5.4795.2.2.8,LLDP-EXT-MED-MIB::lldpXMedNotificationsGroup,,,,,,Notifications sent by an LLDP-MED agent.
.1.0.8802.1.1.2.1.5.32962,LLDP-EXT-DOT1-MIB::lldpXdot1MIB,,,,,,The LLDP Management Information Base extension module for IEEE 802.1 organizationally defined discovery information. In order to assure the uniqueness of the LLDP-MIB, lldpXdot1MIB is branched from lldpExtensions using OUI value as the node. An OUI/'company_id' is a 24 bit globally unique assigned number referenced by various standards. Copyright (C) IEEE (2005). This version of this MIB module is published as Annex F.7.1 of IEEE Std 802.1AB-2005; see the standard itself for full legal notices.
.1.0.8802.1.1.2.1.5.32962.1,LLDP-EXT-DOT1-MIB::lldpXdot1Objects,,,,,,
.1.0.8802.1.1.2.1.5.32962.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1Config,,,,,,
.1.0.8802.1.1.2.1.5.32962.1.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigPortVlanTable,,not-accessible,,current,,A table that controls selection of LLDP Port VLAN-ID TLVs to be transmitted on individual ports.
.1.0.8802.1.1.2.1.5.32962.1.1.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigPortVlanEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined Port VLAN-ID TLV on LLDP transmission capable ports. This configuration object augments the lldpPortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpPortConfigEntry entry. Each active lldpConfigEntry must be restored from non-volatile storage (along with the corresponding lldpPortConfigEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.1.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigPortVlanTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1ConfigPortVlanTxEnable, which is defined as a truth value and configured by the network management, determines whether the IEEE 802.1 organizationally defined port VLAN TLV transmission is allowed on a given LLDP transmission capable port. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigVlanNameTable,,not-accessible,,current,,The table that controls selection of LLDP VLAN name TLV instances to be transmitted on individual ports.
.1.0.8802.1.1.2.1.5.32962.1.1.2.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigVlanNameEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the Local System VLAN name instance will be transmitted. This configuration object augments the lldpLocVlanEntry, therefore it is only present along with the VLAN Name instance contained in the associated lldpLocVlanNameEntry entry. Each active lldpXdot1ConfigVlanNameEntry must be restored from non-volatile storage (along with the corresponding lldpXdot1LocVlanNameEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.2.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigVlanNameTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding Local System VLAN name instance will be transmitted on the port defined by the given lldpXdot1LocVlanNameEntry. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.3,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigProtoVlanTable,,not-accessible,,current,,The table that controls selection of LLDP Port and Protocol VLAN ID TLV instances to be transmitted on individual ports.
.1.0.8802.1.1.2.1.5.32962.1.1.3.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigProtoVlanEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the Local System Protocol VLAN instance will be transmitted. This configuration object augments the lldpXdot1LocVlanEntry, therefore it is only present along with the Port and Protocol VLAN ID instance contained in the associated lldpXdot1LocVlanEntry entry. Each active lldpXdot1ConfigProtoVlanEntry must be restored from non-volatile storage (along with the corresponding lldpXdot1LocProtoVlanEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.3.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigProtoVlanTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding Local System Port and Protocol VLAN instance will be transmitted on the port defined by the given lldpXdot1LocProtoVlanEntry. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.4,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigProtocolTable,,not-accessible,,current,,The table that controls selection of LLDP Protocol  TLV instances to be transmitted on individual ports.
.1.0.8802.1.1.2.1.5.32962.1.1.4.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigProtocolEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the Local System Protocol instance will be transmitted. This configuration object augments the lldpXdot1LocProtoEntry, therefore it is only present along with the Protocol instance contained in the associated lldpXdot1LocProtoEntry entry. Each active lldpXdot1ConfigProtocolEntry must be restored from non-volatile storage (along with the corresponding lldpXdot1LocProtocolEntry) after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.1.4.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigProtocolTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding Local System Protocol Identity instance will be transmitted on the port defined by the given lldpXdot1LocProtocolEntry. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
.1.0.8802.1.1.2.1.5.32962.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1LocalData,,,,,,
.1.0.8802.1.1.2.1.5.32962.1.2.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocTable,,not-accessible,,current,,This table contains one row per port for IEEE 802.1 organizationally defined LLDP extension on the local system known to this agent.
.1.0.8802.1.1.2.1.5.32962.1.2.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocEntry,,not-accessible,lldpLocPortNum,current,,Information about IEEE 802.1 organizationally defined LLDP extension.
.1.0.8802.1.1.2.1.5.32962.1.2.1.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocPortVlanId,Integer32,read-only,,current,,The integer value used to identify the port's VLAN identifier associated with the local system. A value of zero shall be used if the system either does not know the PVID or does not support port-based VLAN operation.
.1.0.8802.1.1.2.1.5.32962.1.2.2,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtoVlanTable,,not-accessible,,current,,This table contains one or more rows per Port and Protocol VLAN information about the local system.
.1.0.8802.1.1.2.1.5.32962.1.2.2.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtoVlanEntry,,not-accessible,lldpLocPortNum:lldpXdot1LocProtoVlanId,current,,Port and protocol VLAN ID Information about a particular port component. There may be multiple port and protocol VLANs, identified by a particular lldpXdot1LocProtoVlanId, configured on the given port.
.1.0.8802.1.1.2.1.5.32962.1.2.2.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtoVlanId,Integer32,not-accessible,,current,,The integer value used to identify the port and protocol VLANs associated with the given port associated with the local system. A value of zero shall be used if the system either does not know the protocol VLAN ID (PPVID) or does not support port and protocol VLAN operation.
.1.0.8802.1.1.2.1.5.32962.1.2.2.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtoVlanSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with the local system) supports port and protocol VLANs.
.1.0.8802.1.1.2.1.5.32962.1.2.2.1.3,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtoVlanEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the port and protocol VLANs are enabled on the given port associated with the local system.
.1.0.8802.1.1.2.1.5.32962.1.2.3,LLDP-EXT-DOT1-MIB::lldpXdot1LocVlanNameTable,,not-accessible,,current,,This table contains one or more rows per IEEE 802.1Q VLAN name information on the local system known to this agent.
.1.0.8802.1.1.2.1.5.32962.1.2.3.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocVlanNameEntry,,not-accessible,lldpLocPortNum:lldpXdot1LocVlanId,current,,VLAN name Information about a particular port component. There may be multiple VLANs, identified by a particular lldpXdot1LocVlanId, configured on the given port.
.1.0.8802.1.1.2.1.5.32962.1.2.3.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocVlanId,Integer32,not-accessible,,current,,The integer value used to identify the IEEE 802.1Q  VLAN IDs with which the given port is compatible.
.1.0.8802.1.1.2.1.5.32962.1.2.3.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1LocVlanName,OCTET,read-only,,current,,The string value used to identify VLAN name identified by the Vlan Id associated with the given port on the local system. This object should contain the value of the dot1QVLANStaticName object (defined in IETF RFC 2674) identified with the given lldpXdot1LocVlanId.
.1.0.8802.1.1.2.1.5.32962.1.2.4,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtocolTable,,not-accessible,,current,,This table contains one or more rows per protocol identity information on the local system known to this agent.
.1.0.8802.1.1.2.1.5.32962.1.2.4.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtocolEntry,,not-accessible,lldpLocPortNum:lldpXdot1LocProtocolIndex,current,,Information about particular protocols that are accessible through the given port component. There may be multiple protocols, identified by particular lldpXdot1ProtocolIndex, and lldpLocPortNum.
.1.0.8802.1.1.2.1.5.32962.1.2.4.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtocolIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular protocol identity.
.1.0.8802.1.1.2.1.5.32962.1.2.4.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1LocProtocolId,OCTET,read-only,,current,,The octet string value used to identify the protocols associated with the given port of the local system.
.1.0.8802.1.1.2.1.5.32962.1.3,LLDP-EXT-DOT1-MIB::lldpXdot1RemoteData,,,,,,
.1.0.8802.1.1.2.1.5.32962.1.3.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemTable,,not-accessible,,current,,This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpXdot1RemEntry is present for each local port, or it may choose to maintain multiple lldpXdot1RemEntries for the same local port.
.1.0.8802.1.1.2.1.5.32962.1.3.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex,current,,Information about a particular port component.
.1.0.8802.1.1.2.1.5.32962.1.3.1.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemPortVlanId,Integer32,read-only,,current,,The integer value used to identify the port's VLAN identifier associated with the remote system. if the remote system either does not know the PVID or does not support port-based VLAN operation, the value of lldpXdot1RemPortVlanId should be zero.
.1.0.8802.1.1.2.1.5.32962.1.3.2,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtoVlanTable,,not-accessible,,current,,This table contains one or more rows per Port and Protocol VLAN information about the remote system, received on the given port.
.1.0.8802.1.1.2.1.5.32962.1.3.2.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtoVlanEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpXdot1RemProtoVlanId,current,,Port and protocol VLAN name Information about a particular port component. There may be multiple protocol VLANs, identified by a particular lldpXdot1RemProtoVlanId, configured on the remote system.
.1.0.8802.1.1.2.1.5.32962.1.3.2.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtoVlanId,Integer32,not-accessible,,current,,The integer value used to identify the port and protocol VLANs associated with the given port associated with the remote system. If port and protocol VLANs are not supported on the given port associated with the remote system, or if the port is not enabled with any port and protocol VLAN, the value of lldpXdot1RemProtoVlanId should be zero.
.1.0.8802.1.1.2.1.5.32962.1.3.2.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtoVlanSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with the remote system) is capable of supporting port and protocol VLANs.
.1.0.8802.1.1.2.1.5.32962.1.3.2.1.3,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtoVlanEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the port and protocol VLANs are enabled on the given port associated with the remote system.
.1.0.8802.1.1.2.1.5.32962.1.3.3,LLDP-EXT-DOT1-MIB::lldpXdot1RemVlanNameTable,,not-accessible,,current,,This table contains one or more rows per IEEE 802.1Q VLAN name information about the remote system, received on the given port.
.1.0.8802.1.1.2.1.5.32962.1.3.3.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemVlanNameEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpXdot1RemVlanId,current,,VLAN name Information about a particular port component. There may be multiple VLANs, identified by a particular lldpXdot1RemVlanId, received on the given port.
.1.0.8802.1.1.2.1.5.32962.1.3.3.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemVlanId,Integer32,not-accessible,,current,,The integer value used to identify the IEEE 802.1Q  VLAN IDs with which the given port of the remote system is compatible.
.1.0.8802.1.1.2.1.5.32962.1.3.3.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1RemVlanName,OCTET,read-only,,current,,The string value used to identify VLAN name identified by the  VLAN Id associated with the remote system.
.1.0.8802.1.1.2.1.5.32962.1.3.4,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtocolTable,,not-accessible,,current,,This table contains one or more rows per protocol information about the remote system, received on the given port.
.1.0.8802.1.1.2.1.5.32962.1.3.4.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtocolEntry,,not-accessible,lldpRemTimeMark:lldpRemLocalPortNum:lldpRemIndex:lldpXdot1RemProtocolIndex,current,,Protocol information about a particular port component. There may be multiple protocols, identified by a particular lldpXdot1ProtocolIndex, received on the given port.
.1.0.8802.1.1.2.1.5.32962.1.3.4.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtocolIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular protocol identity.
.1.0.8802.1.1.2.1.5.32962.1.3.4.1.2,LLDP-EXT-DOT1-MIB::lldpXdot1RemProtocolId,OCTET,read-only,,current,,The octet string value used to identify the protocols associated with the given port of remote system.
.1.0.8802.1.1.2.1.5.32962.2,LLDP-EXT-DOT1-MIB::lldpXdot1Conformance,,,,,,
.1.0.8802.1.1.2.1.5.32962.2.1,LLDP-EXT-DOT1-MIB::lldpXdot1Compliances,,,,,,
.1.0.8802.1.1.2.1.5.32962.2.1.1,LLDP-EXT-DOT1-MIB::lldpXdot1Compliance,,,,,,The compliance statement for SNMP entities which implement the IEEE 802.1 organizationally defined LLDP extension MIB.
.1.0.8802.1.1.2.1.5.32962.2.2,LLDP-EXT-DOT1-MIB::lldpXdot1Groups,,,,,,
.1.0.8802.1.1.2.1.5.32962.2.2.1,LLDP-EXT-DOT1-MIB::lldpXdot1ConfigGroup,,,,,,The collection of objects which are used to configure the IEEE 802.1 organizationally defined LLDP extension implementation behavior. This group is mandatory for agents which implement the  IEEE 802.1 organizationally defined LLDP extension.
.1.0.8802.1.1.2.1.5.32962.2.2.2,LLDP-EXT-DOT1-MIB::lldpXdot1LocSysGroup,,,,,,The collection of objects which are used to represent  IEEE 802.1 organizationally defined LLDP extension associated with the Local Device Information.  This group is mandatory for agents which implement the  IEEE 802.1 organizationally defined LLDP extension in the TX mode.
.1.0.8802.1.1.2.1.5.32962.2.2.3,LLDP-EXT-DOT1-MIB::lldpXdot1RemSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.1 organizational extension Local Device Information.  This group is mandatory for agents which implement the  LLDP 802.1 organizational extension in the RX mode.
.1.0.8802.1.1.2.2,LLDP-MIB::lldpConformance,,,,,,
.1.0.8802.1.1.2.2.1,LLDP-MIB::lldpCompliances,,,,,,
.1.0.8802.1.1.2.2.1.1,LLDP-MIB::lldpCompliance,,,,,,The compliance statement for SNMP entities which implement the LLDP MIB.
.1.0.8802.1.1.2.2.2,LLDP-MIB::lldpGroups,,,,,,
.1.0.8802.1.1.2.2.2.1,LLDP-MIB::lldpConfigGroup,,,,,,The collection of objects which are used to configure the LLDP implementation behavior. This group is mandatory for agents which implement the LLDP.
.1.0.8802.1.1.2.2.2.2,LLDP-MIB::lldpConfigRxGroup,,,,,,The collection of objects which are used to configure the LLDP implementation behavior. This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.2.2.2.3,LLDP-MIB::lldpConfigTxGroup,,,,,,The collection of objects which are used to configure the LLDP implementation behavior. This group is mandatory for agents which implement the LLDP and have the capability of transmitting LLDP frames.
.1.0.8802.1.1.2.2.2.4,LLDP-MIB::lldpStatsRxGroup,,,,,,The collection of objects which are used to represent LLDP reception statistics. This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.2.2.2.5,LLDP-MIB::lldpStatsTxGroup,,,,,,The collection of objects which are used to represent LLDP transmission statistics. This group is mandatory for agents which implement the LLDP and have the capability of transmitting LLDP frames.
.1.0.8802.1.1.2.2.2.6,LLDP-MIB::lldpLocSysGroup,,,,,,The collection of objects which are used to represent LLDP Local System Information.   This group is mandatory for agents which implement the LLDP and have the capability of transmitting LLDP frames.
.1.0.8802.1.1.2.2.2.7,LLDP-MIB::lldpRemSysGroup,,,,,,The collection of objects which are used to represent LLDP Remote Systems Information. The objects represent the information associated with the basic TLV set. Please note that even the agent doesn't implement some of the optional TLVs, it shall recognize all the optional TLV information that the remote system may advertise.  This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.2.2.2.8,LLDP-MIB::lldpNotificationsGroup,,,,,,The collection of notifications used to indicate LLDP MIB data consistency and general status information. This group is mandatory for agents which implement the LLDP and have the capability of receiving LLDP frames.
.1.0.8802.1.1.3,IEEE8021-SECY-MIB::ieee8021SecyMIB,,,,,,The MAC security entity (SecY) MIB module. A SecY is a protocol shim providing MAC Security (MACsec) in an interface stack. Each SecY transmits MACsec protected frames on one or more Secure Channels (SCs) to each of the other SecYs attached to the  same LAN and participating in the same Secure Connectivity Association (CA). The CA is a security relationship, that is established and maintained by key agreement protocols and supported  by MACsec to provide full connectivity between its participants. Each SC provides unidirectional point to multipoint connectivity  from one participant to all the others and is supported by a  succession of similarly point to multipoint Secure Associations  (SAs). The Secure Association Key (SAK) used to protect frames is  changed as an SA is replaced by its (overlapping) successor so fresh keys can be used without disrupting a long lived SC and CA. Two different upper interfaces, a Controlled Port (for frames protected by MACsec, providing an instance of the secure MAC service) and an Uncontrolled Port (for frames not requiring  protection, like the key agreement frames used to establish the  CA and distribute keys) are associated with a SecY shim. For each instance of a SecY two ifTable rows (one for each interface) run on  top of an ifTable row representing the 'Common Port' interface, such as a row with ifType ='ethernetCsmacd(6)'. ___________________________________________________________________ | | | | Controlled Port Interface | Uncontrolled Port Interface | | (ifEntry = j,ifType = | (ifEntry = k, ifType = | | macSecControlledIF(231)) | macSecUncontrolledIF(232)) | |________________________________________________________________| | | | Physical Interface | | (ifEntry = i) | | (ifType = ethernetCsmacd(6)) | |________________________________________________________________| Example MACsec Interface Stack. i, j, k are ifIndexes each indicating a row in the ifTable. 
.1.0.8802.1.1.3.0,IEEE8021-SECY-MIB::secyMIBNotifications,,,,,,
.1.0.8802.1.1.3.0.1,IEEE802171-CFM-MIB::dot1agCfmFaultAlarm,,,,,,A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification. 
.1.0.8802.1.1.3.1,IEEE8021-SECY-MIB::secyMIBObjects,,,,,,
.1.0.8802.1.1.3.1.1,IEEE8021-SECY-MIB::secyMgmtMIBObjects,,,,,,
.1.0.8802.1.1.3.1.1.1,IEEE8021-SECY-MIB::secyIfTable,,not-accessible,,current,,A table with an entry for each service interface in this system with MAC Security capability, i.e. for each SecY. The configured value of writable objects in each table entry shall be stored in persistent memory and remain unchanged across a re-initialization of the system's management entity.
.1.0.8802.1.1.3.1.1.1.1,IEEE8021-SECY-MIB::secyIfEntry,,not-accessible,secyIfInterfaceIndex,current,,A table entry with service information for a particular SecY.
.1.0.8802.1.1.3.1.1.1.1.1,IEEE8021-SECY-MIB::secyIfInterfaceIndex,Integer32,not-accessible,,current,,An interface index, aligned with ifIndex in the ifTable, pointing to the SecY's Controlled Port.
.1.0.8802.1.1.3.1.1.1.1.2,IEEE8021-SECY-MIB::secyIfMaxPeerSCs,Unsigned32,read-only,,current,,The maximum number of peer SCs for this SecY.
.1.0.8802.1.1.3.1.1.1.1.3,IEEE8021-SECY-MIB::secyIfRxMaxKeys,Unsigned32,read-only,,current,,The maximum number of keys in simultaneous use for reception for this SecY.
.1.0.8802.1.1.3.1.1.1.1.4,IEEE8021-SECY-MIB::secyIfTxMaxKeys,Unsigned32,read-only,,current,,The maximum number of keys in simultaneous use for transmission for this SecY.
.1.0.8802.1.1.3.1.1.1.1.5,IEEE8021-SECY-MIB::secyIfProtectFramesEnable,INTEGER,read-write,,current,true(1):false(2),Enables or disables protection of transmitted frames.
.1.0.8802.1.1.3.1.1.1.1.6,IEEE8021-SECY-MIB::secyIfValidateFrames,INTEGER,read-write,,current,disabled(1):check(2):strict(3):null(4),Controls validation of received frames. disabled(1) : disable validation, remove SecTAGs and ICVs (if  present) from received frames. check(2) : enable validation, do not discard invalid frames. strict(3) : enable validation and discard invalid frames. null(4) : no processing, do not remove SecTAGs or ICVs.
.1.0.8802.1.1.3.1.1.1.1.7,IEEE8021-SECY-MIB::secyIfReplayProtectEnable,INTEGER,read-write,,current,true(1):false(2),Enables or disables replay protection.
.1.0.8802.1.1.3.1.1.1.1.8,IEEE8021-SECY-MIB::secyIfReplayProtectWindow,Unsigned32,read-write,,current,,The replay protection window size.
.1.0.8802.1.1.3.1.1.1.1.9,IEEE8021-SECY-MIB::secyIfCurrentCipherSuite,Unsigned32,read-write,,current,,The Cipher Suite currently used by this SecY, identified by the secyCipherSuiteTable entry index. Should be read-only if secyIfCipherTable implemented.
.1.0.8802.1.1.3.1.1.1.1.10,IEEE8021-SECY-MIB::secyIfAdminPt2PtMAC,INTEGER,read-write,,current,forceTrue(1):forceFalse(2):auto(3),Controls the value of operPointToPointMAC (secyOperPt2PtMAC) reported to the user(s) of this SecY's Controlled Port.  forceTrue(1) : operPointToPointMAC is True, regardless of the configuration and status of the SecY. forceFalse(2) : operPointToPointMAC is False, regardless of the configuration and status of the SecY. auto(3) : OperPointMAC is True if secyIfvalidateFrames is  strict and reception is from at most one peer SecY, or if secyIfvalidateFrames is not strict and  operPointToPointMAC is True for the Common Port, and is False otherwise.
.1.0.8802.1.1.3.1.1.1.1.11,IEEE8021-SECY-MIB::secyIfOperPt2PtMAC,INTEGER,read-only,,current,true(1):false(2),Reflects the current service connectivity to be assumed by the  user(s) of the SecY's Controlled Port. true(1) : connectivity is to at most one other system. false(2) : connectivity is to one or more other systems.
.1.0.8802.1.1.3.1.1.1.1.12,IEEE8021-SECY-MIB::secyIfIncludeSCIEnable,INTEGER,read-write,,current,true(1):false(2),Mandates inclusion of an explicit SCI in the SecTAG when transmitting protected frames.
.1.0.8802.1.1.3.1.1.1.1.13,IEEE8021-SECY-MIB::secyIfUseESEnable,INTEGER,read-write,,current,true(1):false(2),Enables use of the ES bit in the SecTAG when transmitting protected frames.
.1.0.8802.1.1.3.1.1.1.1.14,IEEE8021-SECY-MIB::secyIfUseSCBEnable,INTEGER,read-write,,current,true(1):false(2),Enables use of the SCB bit in the SecTAG when transmitting protected frames.
.1.0.8802.1.1.3.1.1.1.1.15,IEEE8021-SECY-MIB::secyIfSCI,OCTET,read-only,,current,,The SCI for the SecY's default traffic class.
.1.0.8802.1.1.3.1.1.1.1.16,IEEE8021-SECY-MIB::secyIfIncludingSCI,INTEGER,read-only,,current,true(1):false(2),True if an explicit SCI is included in the SecTAG when transmitting protected frames.
.1.0.8802.1.1.3.1.1.1.1.17,IEEE8021-SECY-MIB::secyIfMaxTSCs,Unsigned32,read-only,,current,,The maximum number of transmit SCs for this SecY.
.1.0.8802.1.1.3.1.1.2,IEEE8021-SECY-MIB::secyTxSCTable,,not-accessible,,current,,A table with an entry for each SecY's transmit SC.
.1.0.8802.1.1.3.1.1.2.1,IEEE8021-SECY-MIB::secyTxSCEntry,,not-accessible,secyIfInterfaceIndex,current,,An entry with transmit SC information for a SecY.
.1.0.8802.1.1.3.1.1.2.1.1,IEEE8021-SECY-MIB::secyTxSCI,OCTET,read-only,,current,,The SCI for the SecY's transmit SC.
.1.0.8802.1.1.3.1.1.2.1.2,IEEE8021-SECY-MIB::secyTxSCState,INTEGER,read-only,,current,inUse(1):notInUse(2),The transmitting state of the SecY's transmit SC. inUse(1) : one or more SAs are in use. notInUse(2) : no SAs are in use.
.1.0.8802.1.1.3.1.1.2.1.3,IEEE8021-SECY-MIB::secyTxSCEncodingSA,OBJECT,read-only,,current,,The SA currently used to encode the SecTAG for frames awaiting  transmission. The row pointer will point to an entry in the  secyTxSATable. If no such information is available, the value shall  be the OBJECT IDENTIFIER { 0 0 }.
.1.0.8802.1.1.3.1.1.2.1.4,IEEE8021-SECY-MIB::secyTxSCEncipheringSA,OBJECT,read-only,,deprecated,,The SA currently used to encipher frames for transmission. The row pointer will point to an entry in the secyTxSATable.  If no such information is available, the value shall be the OBJECT IDENTIFIER { 0 0 }.
.1.0.8802.1.1.3.1.1.2.1.5,IEEE8021-SECY-MIB::secyTxSCCreatedTime,TimeTicks,read-only,,current,,The system time when this transmitting SC was created.
.1.0.8802.1.1.3.1.1.2.1.6,IEEE8021-SECY-MIB::secyTxSCStartedTime,TimeTicks,read-only,,current,,The system time when this transmitting SC last started transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.2.1.7,IEEE8021-SECY-MIB::secyTxSCStoppedTime,TimeTicks,read-only,,current,,The system time when this transmitting SC last stopped transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.3,IEEE8021-SECY-MIB::secyTxSATable,,not-accessible,,current,,A table with an entry for each transmit SA for each of  the system's SecYs.
.1.0.8802.1.1.3.1.1.3.1,IEEE8021-SECY-MIB::secyTxSAEntry,,not-accessible,secyIfInterfaceIndex:secyTxSA,current,,An entry for a transmit SA.
.1.0.8802.1.1.3.1.1.3.1.1,IEEE8021-SECY-MIB::secyTxSA,Unsigned32,not-accessible,,current,,The association number (AN) for this transmit SA.
.1.0.8802.1.1.3.1.1.3.1.2,IEEE8021-SECY-MIB::secyTxSAState,INTEGER,read-only,,current,inUse(1):notInUse(2),The current status of the transmitting SA. inUse(1) : this SA is in use. notInUse(2) : this SA is not in use.
.1.0.8802.1.1.3.1.1.3.1.3,IEEE8021-SECY-MIB::secyTxSANextPN,Unsigned32,read-only,,current,,The next packet number (PN) for this SA.
.1.0.8802.1.1.3.1.1.3.1.4,IEEE8021-SECY-MIB::secyTxSAConfidentiality,INTEGER,read-only,,current,true(1):false(2),True if the SA provides confidentiality as well as integrity for transmitted frames.
.1.0.8802.1.1.3.1.1.3.1.5,IEEE8021-SECY-MIB::secyTxSASAKUnchanged,INTEGER,read-only,,deprecated,true(1):false(2),A reference to an SAK that is unchanged for the life of the transmitting SA.
.1.0.8802.1.1.3.1.1.3.1.6,IEEE8021-SECY-MIB::secyTxSACreatedTime,TimeTicks,read-only,,current,,The system time when this transmit SA was created.
.1.0.8802.1.1.3.1.1.3.1.7,IEEE8021-SECY-MIB::secyTxSAStartedTime,TimeTicks,read-only,,current,,The system time when this transmit SA last started transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.3.1.8,IEEE8021-SECY-MIB::secyTxSAStoppedTime,TimeTicks,read-only,,current,,The system time when this transmit SA last stopped transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.4,IEEE8021-SECY-MIB::secyRxSCTable,,not-accessible,,current,,A table for the system's SecY's receive SCs.
.1.0.8802.1.1.3.1.1.4.1,IEEE8021-SECY-MIB::secyRxSCEntry,,not-accessible,secyIfInterfaceIndex:secyRxSCI,current,,An entry for one of the SCs used by one of the system's SecY's to receive protected frames.
.1.0.8802.1.1.3.1.1.4.1.1,IEEE8021-SECY-MIB::secyRxSCI,OCTET,not-accessible,,current,,The SCI for the receive SC.
.1.0.8802.1.1.3.1.1.4.1.2,IEEE8021-SECY-MIB::secyRxSCState,INTEGER,read-only,,current,inUse(1):notInUse(2),The state of the receive SC. inUse(1) : one or more SAs for this SC are in use. notInUse(2) : no SAs for this SC is in use.
.1.0.8802.1.1.3.1.1.4.1.3,IEEE8021-SECY-MIB::secyRxSCCurrentSA,OBJECT,read-only,,deprecated,,The current receiving association number of the SC in use. The row pointer will point to an entry in the secyRxSATable. If no  such information can be identified, the value of this object shall  be the OBJECT IDENTIFIER { 0 0 }.
.1.0.8802.1.1.3.1.1.4.1.4,IEEE8021-SECY-MIB::secyRxSCCreatedTime,TimeTicks,read-only,,current,,The system time when this receiving SC was created.
.1.0.8802.1.1.3.1.1.4.1.5,IEEE8021-SECY-MIB::secyRxSCStartedTime,TimeTicks,read-only,,current,,The system time when this receiving SC last started receiving MACsec frames.
.1.0.8802.1.1.3.1.1.4.1.6,IEEE8021-SECY-MIB::secyRxSCStoppedTime,TimeTicks,read-only,,current,,The system time when this receiving SC last stopped receiving MACsec frames.
.1.0.8802.1.1.3.1.1.5,IEEE8021-SECY-MIB::secyRxSATable,,not-accessible,,current,,A table with entries for the system's receive SAs.
.1.0.8802.1.1.3.1.1.5.1,IEEE8021-SECY-MIB::secyRxSAEntry,,not-accessible,secyIfInterfaceIndex:secyRxSCI:secyRxSA,current,,An entry for one of the SAs used by one of the system's SecY's to receive protected frames.
.1.0.8802.1.1.3.1.1.5.1.1,IEEE8021-SECY-MIB::secyRxSA,Unsigned32,not-accessible,,current,,The association number (AN) for this receive SA.
.1.0.8802.1.1.3.1.1.5.1.2,IEEE8021-SECY-MIB::secyRxSAState,INTEGER,read-only,,current,inUse(1):notInUse(2),The current state for this receive SA.
.1.0.8802.1.1.3.1.1.5.1.3,IEEE8021-SECY-MIB::secyRxSANextPN,Unsigned32,read-write,,deprecated,,One more than the highest PN conveyed in the SecTAG of a frame  received on this SA that has been successfully validated (if  validateFrames has not been disabled). Deprecated: use  secyRxSANextXPN for both 32-bit PN and 64-bit XPN PN values. If  this object is implemented and an XPN Cipher Suite is used, it  contains the lowest 32-bits of the XPN.
.1.0.8802.1.1.3.1.1.5.1.4,IEEE8021-SECY-MIB::secyRxSASAKUnchanged,INTEGER,read-only,,deprecated,true(1):false(2),A reference to an SAK that is unchanged for the life of the receiving SA.
.1.0.8802.1.1.3.1.1.5.1.5,IEEE8021-SECY-MIB::secyRxSACreatedTime,TimeTicks,read-only,,current,,The system time when this receiving SA was created.
.1.0.8802.1.1.3.1.1.5.1.6,IEEE8021-SECY-MIB::secyRxSAStartedTime,TimeTicks,read-only,,current,,The system time when this receiving SA last started receiving MACsec frames.
.1.0.8802.1.1.3.1.1.5.1.7,IEEE8021-SECY-MIB::secyRxSAStoppedTime,TimeTicks,read-only,,current,,The system time when this receiving SA last stopped receiving MACsec frames.
.1.0.8802.1.1.3.1.1.5.1.8,IEEE8021-SECY-MIB::secyRxSANextXPN,Counter64,read-only,,current,,One more than the highest PN conveyed in the SecTAG of successfully validates frames received on this SA.
.1.0.8802.1.1.3.1.1.5.1.9,IEEE8021-SECY-MIB::secyRxSALowestXPN,Counter64,read-only,,current,,The lowest acceptable packet number. A received frame  with a lower PN is discarded if  secyIfReplayProtectEnable is enabled.
.1.0.8802.1.1.3.1.1.5.1.10,IEEE8021-SECY-MIB::secyRxSAKeyIdentifier,OCTET,read-only,,current,,The Key Identifier (KI) for the SAK for this SA.
.1.0.8802.1.1.3.1.1.5.1.11,IEEE8021-SECY-MIB::secyRxSASSCI,Integer32,read-only,,current,,The SSCI for this SA, 0 if an XPN Cipher Suite is not being used.
.1.0.8802.1.1.3.1.1.6,IEEE8021-SECY-MIB::secyCipherSuiteTable,,not-accessible,,current,,A table of the system's Cipher Suite capabilities, which can differ by Cipher Suite implementation, so there can be more than one entry  with the same secyCipherSuiteId. The secyIfCipherTable lists  available entries by SecY, avoiding the need for remote network  management to write objects or create rows in this table. Any  configured values shall be stored in persistent memory and remain  unchanged across a re-initialization of the management system.
.1.0.8802.1.1.3.1.1.6.1,IEEE8021-SECY-MIB::secyCipherSuiteEntry,,not-accessible,secyCipherSuiteIndex,current,,An entry for a Cipher Suite implementation.
.1.0.8802.1.1.3.1.1.6.1.1,IEEE8021-SECY-MIB::secyCipherSuiteIndex,Unsigned32,not-accessible,,current,,The CipherSuiteTable entry index.
.1.0.8802.1.1.3.1.1.6.1.2,IEEE8021-SECY-MIB::secyCipherSuiteId,OCTET,read-create,,current,,A unique 64-bit (EUI-64) identifier for the Cipher  Suite.
.1.0.8802.1.1.3.1.1.6.1.3,IEEE8021-SECY-MIB::secyCipherSuiteName,OCTET,read-create,,current,,The Cipher Suite Name, 128 octets or fewer.
.1.0.8802.1.1.3.1.1.6.1.4,IEEE8021-SECY-MIB::secyCipherSuiteCapability,BITS,read-create,,current,integrity(0):confidentiality(1):offsetConfidentiality(2),Cipher Suite implementation capability information. integrity(0) : integrity protection. confidentiality(1) : confidentiality protection. offsetConfidentiality(2) : offset confidentiality  protection.
.1.0.8802.1.1.3.1.1.6.1.5,IEEE8021-SECY-MIB::secyCipherSuiteProtection,BITS,read-create,,deprecated,integrity(0):confidentiality(1):offsetConfidentiality(2),The secyIfCipherSuite table should be used instead of this object  to allow per SecY Cipher Suite configuration.  The options provided by this control are a subset of those defined by the object secyCipherSuiteCapability.  If secyCipherSuiteCapability has the integrity bit on,the integrity  bit can be turned on for this object. If secyCipherSuiteCapability has the integrity and confidentiality  bits on, the confidentiality bit of this object can be turned on  and the integrity bit must be on. If secyCipherSuiteCapability has the integrity and offsetConfidentiality bits on, the offsetConfidentiality bit can be  turned on and the integrity bit must be on. integrity(0) : on or off the function of supporting integrity protection for this cipher suite. confidentiality(1) : on or off the function of supporting confidentiality for this cipher suite. offsetConfidentiality(2) : on or off the function of supporting  offset confidentiality for this cipher suite.
.1.0.8802.1.1.3.1.1.6.1.6,IEEE8021-SECY-MIB::secyCipherSuiteProtectionOffset,Integer32,read-create,,deprecated,,The confidentiality protection offset options of this cipher suite.  Options should depend on the choice of secyCipherSuiteProtection. If the value of secyCipherSuiteProtection only turns on integrity  bit, users can only choose 0 byte for this object. If the value of secyCipherSuiteProtection only turns on integrity  and confidentiality bits, users can only choose 0 byte for this  object. If the value of secyCipherSuiteProtection only turns on integrity  and offsetConfidentiality bits, users can choose 30 or 50 bytes for  this object. If the value of secyCipherSuiteProtection turns on integrity and  confidentiality and offsetConfidentiality bits, users can choose 0  or 30 or 50 bytes for this object.
.1.0.8802.1.1.3.1.1.6.1.7,IEEE8021-SECY-MIB::secyCipherSuiteDataLengthChange,INTEGER,read-create,,current,true(1):false(2),True if cipher suite changes the length of the data.
.1.0.8802.1.1.3.1.1.6.1.8,IEEE8021-SECY-MIB::secyCipherSuiteICVLength,Unsigned32,read-create,,current,,The length of the integrity check value (ICV) field.
.1.0.8802.1.1.3.1.1.6.1.9,IEEE8021-SECY-MIB::secyCipherSuiteRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The secyIfCipherTable (if implemented) avoids the need for network manager creation of entries in the secyCipherSuiteTable,  and RowStatus should always be valid(1), with any per SecY unavailability indicated by an absence of a corresponding secyIfCipherTable entry or one with secyCipherSuiteAvailable false (the latter can indicate temporay unavailability).
.1.0.8802.1.1.3.1.1.7,IEEE8021-SECY-MIB::secyIfCipherTable,,not-accessible,,current,,A table with an entry for the Cipher Suite capabilities implemented for each SecY in this system, providing per SecY control of Cipher Suite use. The configured value of writable objects in each table entry shall be stored in persistent memory and remain unchanged across a re-initialization of the system's management entity.
.1.0.8802.1.1.3.1.1.7.1,IEEE8021-SECY-MIB::secyIfCipherEntry,,not-accessible,secyIfInterfaceIndex:secyCipherSuiteIndex,current,,A table entry with Cipher Suite control for a SecY.
.1.0.8802.1.1.3.1.1.7.1.1,IEEE8021-SECY-MIB::secyIfCipherImplemented,INTEGER,read-only,,current,true(1):false(2),True if the Cipher Suite implementation can be used by this SecY (if secIfCipherEnablUse is true).
.1.0.8802.1.1.3.1.1.7.1.2,IEEE8021-SECY-MIB::secyIfCipherEnableUse,INTEGER,read-write,,current,true(1):false(2),Enables use of the Cipher Suite by this SecY.
.1.0.8802.1.1.3.1.1.7.1.3,IEEE8021-SECY-MIB::secyIfCipherRqConfidentiality,INTEGER,read-write,,current,true(1):false(2),True if confidentiality protection (without an offset) is required if this Cipher Suite is used.
.1.0.8802.1.1.3.1.1.8,IEEE8021-SECY-MIB::secyIfTCTable,,not-accessible,,current,,The Traffic Class Table for each SecY in this system. The configured value of writable objects in each table entry shall be stored in persistent memory and remain unchanged across a re-initialization of the system's management entity.
.1.0.8802.1.1.3.1.1.8.1,IEEE8021-SECY-MIB::secyIfTCEntry,,not-accessible,secyIfInterfaceIndex:secyIfTCUserPriority,current,,A table entry providing Traffic Class selection for a given SecY and User Priority.
.1.0.8802.1.1.3.1.1.8.1.1,IEEE8021-SECY-MIB::secyIfTCUserPriority,Integer32,not-accessible,,current,,One of the possible User Priority values for a frame.
.1.0.8802.1.1.3.1.1.8.1.2,IEEE8021-SECY-MIB::secyIfTCTrafficClass,Integer32,read-write,,current,,The Traffic Class for this SecY and User Priority, as  transmitted in the four most significant bits of the Port Identifier component of the SCI of protected frames.
.1.0.8802.1.1.3.1.1.9,IEEE8021-SECY-MIB::secyIfAPTable,,not-accessible,,current,,The Access Priority Table for each SecY in this system. The configured value of writable objects in each table entry shall be stored in persistent memory and remain unchanged across a re-initialization of the system's management entity.
.1.0.8802.1.1.3.1.1.9.1,IEEE8021-SECY-MIB::secyIfAPEntry,,not-accessible,secyIfInterfaceIndex:secyIfAPUserPCP,current,,A table entry selecting the Access Priority Code Point for a given SecY and User Priority Code Point.
.1.0.8802.1.1.3.1.1.9.1.1,IEEE8021-SECY-MIB::secyIfAPUserPCP,Integer32,not-accessible,,current,,A User Priority Code Point.
.1.0.8802.1.1.3.1.1.9.1.2,IEEE8021-SECY-MIB::secyIfAPAccessPCP,Integer32,read-write,,current,,The Access Priority Code Point for this SecY and User PCP. Defaults to the User PCP value. 
.1.0.8802.1.1.3.1.1.10,IEEE8021-SECY-MIB::secyTSCTable,,not-accessible,,current,,A table of entries for each SecY's traffic class SCs.
.1.0.8802.1.1.3.1.1.10.1,IEEE8021-SECY-MIB::secyTSCEntry,,not-accessible,secyIfInterfaceIndex:secyTSCI,current,,An entry with transmit SC information for one of the system's SecYs and one of its traffic classes.
.1.0.8802.1.1.3.1.1.10.1.1,IEEE8021-SECY-MIB::secyTSCI,OCTET,not-accessible,,current,,The SCI for the transmit SC for this SecY and  traffic class.
.1.0.8802.1.1.3.1.1.10.1.2,IEEE8021-SECY-MIB::secyTSCState,INTEGER,read-only,,current,inUse(1):notInUse(2),The state of the transmit SC for this SecY and traffic class. inUse(1) : one or more SAs for the traffic class SC are in use. notInUse(2) : no SAs for the traffic class SC are in use.
.1.0.8802.1.1.3.1.1.10.1.3,IEEE8021-SECY-MIB::secyTSCEncodingSA,OBJECT,read-only,,current,,The SA currently used to encode the SecTAG for frames awaiting  transmission. The row pointer will point to an entry in the  secyTxSATable. If no such information is available, the value shall  be the OBJECT IDENTIFIER { 0 0 }.
.1.0.8802.1.1.3.1.1.10.1.4,IEEE8021-SECY-MIB::secyTSCCreatedTime,TimeTicks,read-only,,current,,The system time when this transmitting SC was created.
.1.0.8802.1.1.3.1.1.10.1.5,IEEE8021-SECY-MIB::secyTSCStartedTime,TimeTicks,read-only,,current,,The system time when this transmitting SC last started transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.10.1.6,IEEE8021-SECY-MIB::secyTSCStoppedTime,TimeTicks,read-only,,current,,The system time when this transmitting SC last stopped transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.11,IEEE8021-SECY-MIB::secyTSATable,,not-accessible,,current,,A table with an entry for each transmit SA for each of  the system's SecYs.
.1.0.8802.1.1.3.1.1.11.1,IEEE8021-SECY-MIB::secyTSAEntry,,not-accessible,secyIfInterfaceIndex:secyTSCI:secyTSA,current,,An entry for a transmit SA.
.1.0.8802.1.1.3.1.1.11.1.1,IEEE8021-SECY-MIB::secyTSA,Unsigned32,not-accessible,,current,,The association number (AN) for this transmit SA.
.1.0.8802.1.1.3.1.1.11.1.2,IEEE8021-SECY-MIB::secyTSAState,INTEGER,read-only,,current,inUse(1):notInUse(2),The current status of the transmit SA. inUse(1) : this SA is in use. notInUse(2) : this SA is not in use.
.1.0.8802.1.1.3.1.1.11.1.3,IEEE8021-SECY-MIB::secyTSANextXPN,Counter64,read-only,,current,,The next packet number (PN) for this SA.
.1.0.8802.1.1.3.1.1.11.1.4,IEEE8021-SECY-MIB::secyTSAConfidentiality,INTEGER,read-only,,current,true(1):false(2),True if the SA provides confidentiality as well as integrity for transmitted frames.
.1.0.8802.1.1.3.1.1.11.1.5,IEEE8021-SECY-MIB::secyTSAKeyIdentifier,OCTET,read-only,,current,,The Key Identifier (KI) for the SAK for this SA.
.1.0.8802.1.1.3.1.1.11.1.6,IEEE8021-SECY-MIB::secyTSASSCI,Integer32,read-only,,current,,The SSCI for this SA, 0 if an XPN Cipher Suite is not being used.
.1.0.8802.1.1.3.1.1.11.1.7,IEEE8021-SECY-MIB::secyTSACreatedTime,TimeTicks,read-only,,current,,The system time when this transmit SA was created.
.1.0.8802.1.1.3.1.1.11.1.8,IEEE8021-SECY-MIB::secyTSAStartedTime,TimeTicks,read-only,,current,,The system time when this transmit SA last started transmitting MACsec frames.
.1.0.8802.1.1.3.1.1.11.1.9,IEEE8021-SECY-MIB::secyTSAStoppedTime,TimeTicks,read-only,,current,,The system time when this transmit SA last stopped transmitting MACsec frames.
.1.0.8802.1.1.3.1.2,IEEE8021-SECY-MIB::secyStatsMIBObjects,,,,,,
.1.0.8802.1.1.3.1.2.1,IEEE8021-SECY-MIB::secyTxSAStatsTable,,not-accessible,,deprecated,,A table of statistics for each transmit SA for each of  the system's SecYs.
.1.0.8802.1.1.3.1.2.1.1,IEEE8021-SECY-MIB::secyTxSAStatsEntry,,not-accessible,,deprecated,,An entry with statistics for a transmit SA. The AN that  identifies an SA (for a given SC) and this corresponding entry can be reused. When creating the SA and before (re)using the entry, the SA counters are (re)set to 0. When the SA is stopped (secyTxSA notInuse) the counters will be stop incrementing. The secyTxSATable timestamps SA creation, start, and stop.
.1.0.8802.1.1.3.1.2.1.1.1,IEEE8021-SECY-MIB::secyTxSAStatsProtectedPkts,Counter32,read-only,,deprecated,,The number of integrity protected but not encrypted  packets for this transmit SA. Zero if secyTxSAConfidentiality is True, and one less than  secyTxSANextPN otherwise.
.1.0.8802.1.1.3.1.2.1.1.2,IEEE8021-SECY-MIB::secyTxSAStatsEncryptedPkts,Counter32,read-only,,deprecated,,The number of integrity protected and encrypted packets  for this transmit SA. Zero if secyTxSAConfidentiality  is False, and one less than secyTxSANextPN otherwise.
.1.0.8802.1.1.3.1.2.1.1.3,IEEE802171-CFM-MIB::dot1agCfmDefaultMdLevelMhfCreation,INTEGER,read-write,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3),A value indicating if the Management entity can create MHFs (MIP Half Function) for this VID. 
.1.0.8802.1.1.3.1.2.1.1.4,IEEE802171-CFM-MIB::dot1agCfmDefaultMdLevelLevel,Integer32,read-write,,current,,The MD Level at which MHFs are to be created, or -1 if defMHFnone. 
.1.0.8802.1.1.3.1.2.2,IEEE8021-SECY-MIB::secyTxSCStatsTable,,not-accessible,,current,,A table of statistics for each SecY's transmit SC.
.1.0.8802.1.1.3.1.2.2.1,IEEE8021-SECY-MIB::secyTxSCStatsEntry,,not-accessible,,current,,An entry containing counts for a transmit SC. SA counters are  reset when the SA's AN is reused, so these SC counts are a summation for all current and prior SAs belonging to the SC.
.1.0.8802.1.1.3.1.2.2.1.1,IEEE8021-SECY-MIB::secyTxSCStatsProtectedPkts,Counter64,read-only,,current,,The number of integrity protected but not encrypted packets for this transmit SC.
.1.0.8802.1.1.3.1.2.2.1.4,IEEE8021-SECY-MIB::secyTxSCStatsEncryptedPkts,Counter64,read-only,,current,,The number of integrity protected and encrypted packets  for this transmit SC.
.1.0.8802.1.1.3.1.2.2.1.10,IEEE8021-SECY-MIB::secyTxSCStatsOctetsProtected,Counter64,read-only,,deprecated,,The number of plain text octets that are integrity  protected but not encrypted for this transmit SC.
.1.0.8802.1.1.3.1.2.2.1.11,IEEE8021-SECY-MIB::secyTxSCStatsOctetsEncrypted,Counter64,read-only,,deprecated,,The number of plain text octets that are integrity protected and encrypted on the transmit SC.
.1.0.8802.1.1.3.1.2.3,IEEE8021-SECY-MIB::secyRxSAStatsTable,,not-accessible,,deprecated,,A table that contains the statistics objects for each receiving SA in the MAC security entity.
.1.0.8802.1.1.3.1.2.3.1,IEEE8021-SECY-MIB::secyRxSAStatsEntry,,not-accessible,,deprecated,,An entry with statistics for a receive SA. The AN that  identifies an SA (for a given SC) and this corresponding entry can be reused. When creating the SA and before (re)using the entry, the SA counters are (re)set to 0. When the SA is stopped (secyRxSA notInuse) the counters will be stop incrementing. The secyRxSATable timestamps SA creation, start, and stop.
.1.0.8802.1.1.3.1.2.3.1.1,IEEE8021-SECY-MIB::secyRxSAStatsUnusedSAPkts,Counter32,read-only,,deprecated,,For this SA which is not currently in use, the number of received, unencrypted, packets with secyValidateFrames not in the strict mode.
.1.0.8802.1.1.3.1.2.3.1.4,IEEE8021-SECY-MIB::secyRxSAStatsNoUsingSAPkts,Counter32,read-only,,deprecated,,For this SA which is not currently in use, the number of received packets that have been discarded, and have either the packets encrypted or secyValidateFrames set to strict mode.
.1.0.8802.1.1.3.1.2.3.1.13,IEEE8021-SECY-MIB::secyRxSAStatsNotValidPkts,Counter32,read-only,,deprecated,,For this SA, the number discarded packets with the condition that the packets are not valid and one of the following conditions are true: either secyValidateFrames in strict mode or the packets encrypted.
.1.0.8802.1.1.3.1.2.3.1.16,IEEE8021-SECY-MIB::secyRxSAStatsInvalidPkts,Counter32,read-only,,deprecated,,For this SA, the number of packets with the condition that the packets are not valid and secyValidateFrames is in check mode.
.1.0.8802.1.1.3.1.2.3.1.25,IEEE8021-SECY-MIB::secyRxSAStatsOKPkts,Counter32,read-only,,deprecated,,For this SA, the number of validated packets.
.1.0.8802.1.1.3.1.2.4,IEEE8021-SECY-MIB::secyRxSCStatsTable,,not-accessible,,current,,A table of statistics for each receive SC for each of the system's SecYs.
.1.0.8802.1.1.3.1.2.4.1,IEEE8021-SECY-MIB::secyRxSCStatsEntry,,not-accessible,,current,,An entry containing counts for a receive SC. SA counters are  reset when the SA's AN is reused, so these SC counts are a  summation for all current and prior SAs belonging to the SC.
.1.0.8802.1.1.3.1.2.4.1.1,IEEE8021-SECY-MIB::secyRxSCStatsUnusedSAPkts,Counter64,read-only,,deprecated,,The sum of secyRxSAStatsUnusedSAPkts counts for all current and prior SAs belonging to this SC.
.1.0.8802.1.1.3.1.2.4.1.2,IEEE8021-SECY-MIB::secyRxSCStatsNoUsingSAPkts,Counter64,read-only,,deprecated,,The sum of secyRxSAStatsNoUsingSAPkts counts for all current and prior SAs belonging to this SC.
.1.0.8802.1.1.3.1.2.4.1.3,IEEE8021-SECY-MIB::secyRxSCStatsLatePkts,Counter64,read-only,,current,,The number of packets discarded, for this SC, because the  the received PN was lower than the lowest acceptable PN (secyRxSALowestXPN) and secyIfReplayProtectEnable was true.
.1.0.8802.1.1.3.1.2.4.1.4,IEEE8021-SECY-MIB::secyRxSCStatsNotValidPkts,Counter64,read-only,,current,,The number of packets discarded, for this SC, because validation failed and secyIfvalidateFrames was 'strict' or the data was encrypted (so the original frame could not be recovered).
.1.0.8802.1.1.3.1.2.4.1.5,IEEE8021-SECY-MIB::secyRxSCStatsInvalidPkts,Counter64,read-only,,current,,The number of packets, for this SC, that failed validation but  could be received because secyIfvalidateFrames was 'check' and the data was not encrypted (so the original frame could be  recovered).
.1.0.8802.1.1.3.1.2.4.1.6,IEEE8021-SECY-MIB::secyRxSCStatsDelayedPkts,Counter64,read-only,,current,,The number of received packets, for this SC, with PN lower than the lowest acceptable PN (secyRxSALowestXPN) and  secyIfReplayProtectEnable false.
.1.0.8802.1.1.3.1.2.4.1.7,IEEE8021-SECY-MIB::secyRxSCStatsUncheckedPkts,Counter64,read-only,,current,,The number of packets received for this SC, while  secyValidateFrames was 'disabled'.
.1.0.8802.1.1.3.1.2.4.1.8,IEEE8021-SECY-MIB::secyRxSCStatsOKPkts,Counter64,read-only,,current,,The number of packets received for this SC successfully validated and within the replay window.
.1.0.8802.1.1.3.1.2.4.1.9,IEEE8021-SECY-MIB::secyRxSCStatsOctetsValidated,Counter64,read-only,,deprecated,,The number of plaintext octets recovered from packets  that were integrity protected but not encrypted.
.1.0.8802.1.1.3.1.2.4.1.10,IEEE8021-SECY-MIB::secyRxSCStatsOctetsDecrypted,Counter64,read-only,,deprecated,,The number of plaintext octets recovered from packets  that were integrity protected and encrypted.
.1.0.8802.1.1.3.1.2.5,IEEE8021-SECY-MIB::secyStatsTable,,not-accessible,,current,,A table of statistics for each of the system's SecYs.
.1.0.8802.1.1.3.1.2.5.1,IEEE8021-SECY-MIB::secyStatsEntry,,not-accessible,,current,,An entry containing counts for a SecY.
.1.0.8802.1.1.3.1.2.5.1.1,IEEE8021-SECY-MIB::secyStatsTxUntaggedPkts,Counter64,read-only,,current,,The number of packets transmitted without a SecTAG because secyProtectFramesEnable is configured false.
.1.0.8802.1.1.3.1.2.5.1.2,IEEE8021-SECY-MIB::secyStatsTxTooLongPkts,Counter64,read-only,,current,,The number of transmit packets discarded because their length is greater than the ifMtu of the Common Port.
.1.0.8802.1.1.3.1.2.5.1.3,IEEE8021-SECY-MIB::secyStatsRxUntaggedPkts,Counter64,read-only,,current,,The number of packets without the MACsec tag (SecTAG)  received while secyValidateFrames was not 'strict'.
.1.0.8802.1.1.3.1.2.5.1.4,IEEE8021-SECY-MIB::secyStatsRxNoTagPkts,Counter64,read-only,,current,,The number of received packets without a SecTAG discarded because secyValidateFrames was 'strict'.
.1.0.8802.1.1.3.1.2.5.1.5,IEEE8021-SECY-MIB::secyStatsRxBadTagPkts,Counter64,read-only,,current,,The number of received packets discarded with an  invalid SecTAG, zero value PN, or invalid ICV.
.1.0.8802.1.1.3.1.2.5.1.6,IEEE8021-SECY-MIB::secyStatsRxUnknownSCIPkts,Counter64,read-only,,deprecated,,The number of received packets with an unknown SCI.
.1.0.8802.1.1.3.1.2.5.1.7,IEEE8021-SECY-MIB::secyStatsRxNoSCIPkts,Counter64,read-only,,deprecated,,The number of discarded packets with an unknown SCI.
.1.0.8802.1.1.3.1.2.5.1.8,IEEE8021-SECY-MIB::secyStatsRxOverrunPkts,Counter64,read-only,,current,,The number of packets discarded because they exceeded  cryptographic performance capabilities.
.1.0.8802.1.1.3.1.2.5.1.9,IEEE8021-SECY-MIB::secyStatsRxNoSAPkts,Counter64,read-only,,current,,The number of received packets with an unknown SCI  or for an unused SA.
.1.0.8802.1.1.3.1.2.5.1.10,IEEE8021-SECY-MIB::secyStatsRxNoSAErrorPkts,Counter64,read-only,,current,,The number of packets discarded because the received SCI is unknown or the SA is not in use.
.1.0.8802.1.1.3.1.2.5.1.11,IEEE8021-SECY-MIB::secyStatsTxOctetsProtected,Counter64,read-only,,current,,The number of plain text octets integrity protected  but not encrypted in transmitted frames.
.1.0.8802.1.1.3.1.2.5.1.12,IEEE8021-SECY-MIB::secyStatsTxOctetsEncrypted,Counter64,read-only,,current,,The number of plain text octets integrity protected  and encrypted in transmitted frames.
.1.0.8802.1.1.3.1.2.5.1.13,IEEE8021-SECY-MIB::secyStatsRxOctetsValidated,Counter64,read-only,,current,,The number of plaintext octets recovered from packets  that were integrity protected but not encrypted.
.1.0.8802.1.1.3.1.2.5.1.14,IEEE8021-SECY-MIB::secyStatsRxOctetsDecrypted,Counter64,read-only,,current,,The number of plaintext octets recovered from packets  that were integrity protected and encrypted.
.1.0.8802.1.1.3.1.2.12,IEEE8021-SECY-MIB::secyTSCStatsTable,,not-accessible,,current,,A table of statistics for each SecY's transmit SCs.
.1.0.8802.1.1.3.1.2.12.1,IEEE8021-SECY-MIB::secyTSCStatsEntry,,not-accessible,,current,,A entry containing counts for a transmit SC, since SA counters  are reset when the SA's AN is reused these are a summation for all current and prior SAs belonging to the SC.
.1.0.8802.1.1.3.1.2.12.1.1,IEEE8021-SECY-MIB::secyTSCStatsProtectedPkts,Counter64,read-only,,current,,The number of integrity protected but not encrypted packets for this transmit SC.
.1.0.8802.1.1.3.1.2.12.1.2,IEEE8021-SECY-MIB::secyTSCStatsEncryptedPkts,Counter64,read-only,,current,,The number of integrity protected and encrypted packets for this transmit SC.
.1.0.8802.1.1.3.1.3,IEEE802171-CFM-MIB::dot1agCfmConfigErrorList,,,,,,
.1.0.8802.1.1.3.1.3.1,IEEE802171-CFM-MIB::dot1agCfmConfigErrorListTable,,not-accessible,,current,,The CFM Configuration Error List table provides a list of Interfaces and VIDs that are incorrectly configured. 
.1.0.8802.1.1.3.1.3.1.1,IEEE802171-CFM-MIB::dot1agCfmConfigErrorListEntry,,not-accessible,dot1agCfmConfigErrorListVid:dot1agCfmConfigErrorListIfIndex,current,,The Config Error List Table entry
.1.0.8802.1.1.3.1.3.1.1.1,IEEE802171-CFM-MIB::dot1agCfmConfigErrorListVid,Integer32,not-accessible,,current,,The vlan ID of the vlan with errored interfaces.
.1.0.8802.1.1.3.1.3.1.1.2,IEEE802171-CFM-MIB::dot1agCfmConfigErrorListIfIndex,Integer32,not-accessible,,current,,This object is the IfIndex of the interface.
.1.0.8802.1.1.3.1.3.1.1.3,IEEE802171-CFM-MIB::dot1agCfmConfigErrorListErrorType,BITS,read-only,,current,cfmLeak(0):conflictingVids(1):excessiveLevels(2):overlappedLevels(3),A vector of Boolean error conditions from 22.2.4, any of which may be true: 1) CFMleak; 2) ConflictingVids; 3) ExcessiveLevels; 4) OverlappedLevels. 
.1.0.8802.1.1.3.1.4,IEEE802171-CFM-MIB::dot1agCfmMd,,,,,,
.1.0.8802.1.1.3.1.4.1,IEEE802171-CFM-MIB::dot1agCfmMdTableNextIndex,Unsigned32,read-only,,current,,This object contains an unused value for dot1agCfmMdIndex in the dot1agCfmMdTable, or a zero to indicate that none exist. 
.1.0.8802.1.1.3.1.4.2,IEEE802171-CFM-MIB::dot1agCfmMdTable,,not-accessible,,current,,The MaintenanceDomain table. Each row in the table represents a different maintenance domain. A Maintenace domain is described in 802.1ag (3.22) as the network or the part of the network for which faults in connectivity are to be managed. The boundary of a Maintenance Domain is defined by a set of DSAPs, each of which can become a point of connectivity to a service instance. 
.1.0.8802.1.1.3.1.4.2.1,IEEE802171-CFM-MIB::dot1agCfmMdEntry,,not-accessible,dot1agCfmMdIndex,current,,The Maintenance Domain table entry. This entry is not lost upon reboot. It is backed up by stable storage. 
.1.0.8802.1.1.3.1.4.2.1.1,IEEE802171-CFM-MIB::dot1agCfmMdIndex,Unsigned32,not-accessible,,current,,The index to the maintenance domain table. dot1agCfmMdTableNextIndex needs to be inspected to find an available index for row-creation. Referential integrity is required i.e. the index needs to be persistent upon a reboot or restart of a device. The index can never be reused for other maintenance domain. The index value should keep increasing up to the time that they wrap around. This is to facilitate access control based on OID. 
.1.0.8802.1.1.3.1.4.2.1.2,IEEE802171-CFM-MIB::dot1agCfmMdFormat,INTEGER,read-create,,current,none(1):dnsLikeName(2):macAddressAndUint(3):charString(4),The type (and thereby format) of the Maintenance Domain Name.
.1.0.8802.1.1.3.1.4.2.1.3,IEEE802171-CFM-MIB::dot1agCfmMdName,OCTET,read-create,,current,,The Maintenance Domain name. The type/format of this object is determined by the value of the dot1agCfmMdNameType object.  Each Maintenance Domain has unique name amongst all those used or available to a service provider or operator. It facilitates easy identification of administrative responsibility for each Maintenance Domain. Clause 3.24 defines a Maintenance Domain name as the identifier, unique over the domain for which CFM is to protect against accidental concatenation of Service Instances, of a particular Maintenance Domain. 
.1.0.8802.1.1.3.1.4.2.1.4,IEEE802171-CFM-MIB::dot1agCfmMdLevel,Integer32,read-create,,current,,The Maintenance Domain Level.
.1.0.8802.1.1.3.1.4.2.1.5,IEEE802171-CFM-MIB::dot1agCfmMdMhfCreation,INTEGER,read-create,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3),Enumerated value indicating whether the management entity can create MHFs (MIP Half Function) for this Maintenance Domain. 
.1.0.8802.1.1.3.1.4.2.1.6,IEEE802171-CFM-MIB::dot1agCfmMdFaultAlarmDestDomain,OBJECT,read-create,,current,,The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB) The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX TransportAddress must have a zero-length OCTET STRING as a value. 
.1.0.8802.1.1.3.1.4.2.1.7,IEEE802171-CFM-MIB::dot1agCfmMdFaulAlarmDestAddress,OCTET,read-create,,current,,The transportAddress to which Fault Alarms are to be transmitted to. The type/format of this object is determined by the value of the dot1agCfmMdFaultAlarmDestDomain. If the dot1agCfmMdFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not to be transmitted') then this object should have a value of a zero-length OCTET STRING.  
.1.0.8802.1.1.3.1.4.2.1.8,IEEE802171-CFM-MIB::dot1agCfmMdRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated. 
.1.0.8802.1.1.3.1.5,IEEE802171-CFM-MIB::dot1agCfmMa,,,,,,
.1.0.8802.1.1.3.1.5.1,IEEE802171-CFM-MIB::dot1agCfmMaTableNextIndex,Unsigned32,read-only,,current,,Value to be used as the index of the MA table when the management entity wants to create a new row in the table. 
.1.0.8802.1.1.3.1.5.3,IEEE802171-CFM-MIB::dot1agCfmMaTable,,not-accessible,,current,,The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. Creation of a Service Instance establishes a connectionless association among the selected DSAPs. Configuring a Maintenance association End Point (MEP) at each of the DSAPs creates a Maintenance Association (MA) to monitor that connectionless connectivity. The MA is identified by a Short MA Name that is unique within the Maintenance Domain and chosen to facilitate easy identification of the Service Instance. Together, the Maintenance Domain Name and the Short MA Name form the Maintenance Association Identifier (MAID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance association End Point Identifier (MEPID), identifies each MEP among those configured on a single MA (802.1ag clauses 3.17 and 18.2). This table uses two indices, first index is the index of the Maintenance Domain table. The writable objects in this table need to be persistent upon reboot or restart of a device. 
.1.0.8802.1.1.3.1.5.3.1,IEEE802171-CFM-MIB::dot1agCfmMaEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex,current,,The MA table entry.
.1.0.8802.1.1.3.1.5.3.1.1,IEEE802171-CFM-MIB::dot1agCfmMaIndex,Unsigned32,not-accessible,,current,,Index of the MA table dot1agCfmMaTableNextIndex needs to be inspected to find an available index for row-creation 1..4094 -> describes an MA entry associated with a VID 16777217..4294967295 -> describes an MA entry not associated with any VID 
.1.0.8802.1.1.3.1.5.3.1.2,IEEE802171-CFM-MIB::dot1agCfmMaFormat,INTEGER,read-create,,current,primaryVid(1):charString(2):unsignedInt16(3):rfc2865VpnId(4),The type (and thereby format) of the Maintenance Association Name. 
.1.0.8802.1.1.3.1.5.3.1.3,IEEE802171-CFM-MIB::dot1agCfmMaName,OCTET,read-create,,current,,The Short Maintenance Association name. The type/format of this object is determined by the value of the dot1agCfmMaNameType object. 
.1.0.8802.1.1.3.1.5.3.1.4,IEEE802171-CFM-MIB::dot1agCfmMaMhfCreation,INTEGER,read-create,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3),Indicates if the Management entity can create MHFs (MIP Half Function) for this MA. 
.1.0.8802.1.1.3.1.5.3.1.5,IEEE802171-CFM-MIB::dot1agCfmMaCcmInterval,INTEGER,read-create,,current,intervalInvalid(0):interval300Hz(1):interval10ms(2):interval100ms(3):interval1s(4):interval10s(5):interval1min(6):interval10min(7),Interval between CCM transmissions to be used by all MEPs in the MA. 
.1.0.8802.1.1.3.1.5.3.1.6,IEEE802171-CFM-MIB::dot1agCfmMaFaultAlarmDestDomain,OBJECT,read-create,,current,,The transportDomain for the address to which Fault Alarms are to be transmitted. Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB)  The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX  transportAddress must have a zero-length OCTET STRING as a value. 
.1.0.8802.1.1.3.1.5.3.1.7,IEEE802171-CFM-MIB::dot1agCfmMaFaulAlarmDestAddress,OCTET,read-create,,current,,The transportAddress to which Fault Alarms are to be transmitted to. The type/format of this object is determined by the value of the dot1agCfmMaFaultAlarmDestDomain. If the dot1agCfmMaFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not to be transmitted') then this object should have a value of a zero-length OCTET STRING.  
.1.0.8802.1.1.3.1.5.3.1.8,IEEE802171-CFM-MIB::dot1agCfmMaMoreThanOneVid,INTEGER,read-create,,current,true(1):false(2),True indicate that the MA is associated with more that one VID. False indicates that the MA is associated with only one VID or no VID. This value should be false for MAs with an index greater than 16777216. 
.1.0.8802.1.1.3.1.5.3.1.9,IEEE802171-CFM-MIB::dot1agCfmMaRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated. 
.1.0.8802.1.1.3.1.5.4,IEEE802171-CFM-MIB::dot1agCfmMaVlanTable,,not-accessible,,current,,If an MA is associated with multiple VIDs, then this table contains all the VIDs associated with the MA other than the primary VID. The writable objects in this table need to be persistent upon reboot or restart of a device. 
.1.0.8802.1.1.3.1.5.4.1,IEEE802171-CFM-MIB::dot1agCfmMaVlanEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMaVlanVid,current,,The Maintenance Association VLAN table entry.
.1.0.8802.1.1.3.1.5.4.1.1,IEEE802171-CFM-MIB::dot1agCfmMaVlanVid,Integer32,not-accessible,,current,,This is a VLAN ID of the vlan monitored by the MA. VID 0 means that the MA is not associated with any VLAN. 
.1.0.8802.1.1.3.1.5.4.1.2,IEEE802171-CFM-MIB::dot1agCfmMaVlanRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated. 
.1.0.8802.1.1.3.1.5.8,IEEE802171-CFM-MIB::dot1agCfmMaMepListTable,,not-accessible,,current,,List of MEPIDs (in any bridge) that belong to the same MA. Clause 12.14.6.1.3 specifies that a list of MEPIDs in all bridges in that MA, but since SNMP SMI does not allow to state in a MIB that an object in a table is an array, the  information has to be stored in another table with two indices, being the first index, the index of the table that  contains the list or array. 
.1.0.8802.1.1.3.1.5.8.1,IEEE802171-CFM-MIB::dot1agCfmMaMepListEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMaMepListIdentifier,current,,The known MEPS table entry.
.1.0.8802.1.1.3.1.5.8.1.1,IEEE802171-CFM-MIB::dot1agCfmMaMepListIdentifier,Unsigned32,not-accessible,,current,,MEPID
.1.0.8802.1.1.3.1.5.8.1.2,IEEE802171-CFM-MIB::dot1agCfmMaMepListRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. Read SNMPv2-TC (RFC1903) for an explanation of the possible values this object can take. 
.1.0.8802.1.1.3.1.6,IEEE802171-CFM-MIB::dot1agCfmMep,,,,,,
.1.0.8802.1.1.3.1.6.1,IEEE802171-CFM-MIB::dot1agCfmMepTable,,not-accessible,,current,,The Maintenance Association End Point (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an end point of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (802.1ag clause 3.18). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain. The Transmit Loopback table. Entries in this table are created/removed at the same time than entries in the MEP table are created/removed. The MEP table also stores all the managed objects for sending LBM and LTM. *LBM Managed objects LBM Managed objects in the MEP table  enables the management entity to initiate transmission of Loopback messages. It will signal the MEP that it should transmit some number of Loopback messages and detect the detection (or lack thereof) of the corresponding Loopback messages. Steps to use entries in this table: 1) Wait for dot1agCfmMepTransmitLbmStatus value to be 'ready'. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and dot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for dot1agCfmMepTransmitLbmStatus is 'ready' - if not, wait x seconds, goto step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change dot1agCfmMepTransmitLbmStatus value from 'ready' to 'notReady' to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo  and dot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. 3) Setup the different data to be sent (number of messages, optional TLVs,...). 4) Record the current values of dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu. 6) Change dot1agCfmMepTransmitLbmStatus value from 'notReady' to 'transmit' to initiate transmission of Loopback messages. 7) Check the value of dot1agCfmMepTransmitLbmResultOK to find out if the operation was sucessfully initiated or not. 8) Monitor the value of dot1agCfmMepTransmitLbmMessages. When it reaches 0, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) Compare dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. 10) Change the dot1agCfmMepTransmitLbmStatus value back to 'ready' to allow other management entities to use the table. *LTM Managed objects The LTM Managed objects in the MEP table are used in a manner similar to that described for LBM transmission, above. Upon successfully initiating the transmission, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the results of the LTM from the dot1agCfmLtrTable. 
.1.0.8802.1.1.3.1.6.1.1,IEEE802171-CFM-MIB::dot1agCfmMepEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier,current,,The MEP table entry
.1.0.8802.1.1.3.1.6.1.1.1,IEEE802171-CFM-MIB::dot1agCfmMepIdentifier,Unsigned32,not-accessible,,current,,Integer that is unique among all the MEPs in the same MA. Other definition is: a small integer, unique over a given Maintenance Association, identifying a specific Maintenance association End Point (3.19). MEP Identifier is also known as the MEPID. 
.1.0.8802.1.1.3.1.6.1.1.2,IEEE802171-CFM-MIB::dot1agCfmMepIfIndex,Integer32,read-create,,current,,This object is the interface index of the interface eiter a bridge port, or an aggregated IEEE 802.1 link within a bridge port, to which the MEP is attached. 
.1.0.8802.1.1.3.1.6.1.1.3,IEEE802171-CFM-MIB::dot1agCfmMepDirection,INTEGER,read-create,,current,down(1):up(2),The direction in which the MEP faces on the Bridge port.
.1.0.8802.1.1.3.1.6.1.1.4,IEEE802171-CFM-MIB::dot1agCfmMepPrimaryVid,Unsigned32,read-create,,current,,An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MEP's MA. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID.
.1.0.8802.1.1.3.1.6.1.1.5,IEEE802171-CFM-MIB::dot1agCfmMepActive,INTEGER,read-create,,current,true(1):false(2),Administrative state of the MEP A Boolean indicating the administrative state of the MEP. True indicates that the MEP is to function normally, and false that it is to cease functioning.
.1.0.8802.1.1.3.1.6.1.1.6,IEEE802171-CFM-MIB::dot1agCfmMepFngState,INTEGER,read-only,,current,fngReset(1):fngDefect(2):fngReportDefect(3):fngDefectReported(4):fngDefectClearing(5),Current state of the MEP Fault Notification Generator State Machine. 
.1.0.8802.1.1.3.1.6.1.1.7,IEEE802171-CFM-MIB::dot1agCfmMepCciEnabled,INTEGER,read-create,,current,true(1):false(2),If set to true, the MEP will generate CCM messages.
.1.0.8802.1.1.3.1.6.1.1.8,IEEE802171-CFM-MIB::dot1agCfmMepCcmLtmPriority,Unsigned32,read-create,,current,,The priority value for CCMs and LTMs transmitted by the MEP. Default Value in the highest priority value allowed to pass through the bridge port for any of this MEPs VIDs. The management entity can obtain the default valuefor this  variable from the priority regeneration table by extracting the  highest priority value in this table on this MEPs bridge port. (1 is lowest, then 2, then 0, then 3-7). 
.1.0.8802.1.1.3.1.6.1.1.9,IEEE802171-CFM-MIB::dot1agCfmMepMacAddress,OCTET,read-only,,current,,MAC address of the MEP.
.1.0.8802.1.1.3.1.6.1.1.10,IEEE802171-CFM-MIB::dot1agCfmMepFaultAlarmDestDomain,OBJECT,read-create,,current,,The transportDomain for the address to which Fault Alarms are to be transmitted.  Typical values will be one of (not all inclusive) list: transportDomainUdpIpv4 (from TRANSPORT-ADDRESS-MIB) transportDomainUdpIpv6 (from TRANSPORT-ADDRESS-MIB) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB)  The value 'zeroDotZero' indicates 'Fault Alarms are not to be transmitted', in which case the related object of SYNTAX  transportAddress must have a zero-length OCTET STRING as a value. 
.1.0.8802.1.1.3.1.6.1.1.11,IEEE802171-CFM-MIB::dot1agCfmMepFaulAlarmDestAddress,OCTET,read-create,,current,,The transportAddress to which Fault Alarms (12.14.7.7) are to be transmitted to. The type/format of this object is determined by the value of dot1agCfmMepFaultAlarmDestDomain. If the dot1agCfmMepFaultAlarmDestDomain object has a value of 'zeroDotZero' (indicating 'Fault Alarms are not specified') then this object should have a value of a zero-length OCTET STRING. If 'Fault Alarms are not specified', the address used is that from the Maintenance Association managed object (12.14.6.1.3:e). 
.1.0.8802.1.1.3.1.6.1.1.12,IEEE802171-CFM-MIB::dot1agCfmMepLowPrDef,INTEGER,read-create,,current,allDef(1):macRemErrXcon(2):remErrXcon(3):errXcon(4):xcon(5):noDef(6),An integer value specifying the lowest priority defect  that is allowed to generate fault alarm. 
.1.0.8802.1.1.3.1.6.1.1.13,IEEE802171-CFM-MIB::dot1agCfmMepFngAlarmTime,INTEGER,read-create,,current,,The time that defects must be present before a Fault Alarm is issued (fngAlarmTime. 20.33.3) (default 2.5s). 
.1.0.8802.1.1.3.1.6.1.1.14,IEEE802171-CFM-MIB::dot1agCfmMepFngResetTime,INTEGER,read-create,,current,,The time that defects must be absent before re-enabling a Fault Alarm (fngResetTime, 20.33.4) (default 10s). 
.1.0.8802.1.1.3.1.6.1.1.15,IEEE802171-CFM-MIB::dot1agCfmMepHighestPrDefect,INTEGER,read-only,,current,none(1):defRDICCM(2):defMACstatus(3):defRemoteCCM(4):defErrorCCM(5):defXconCCM(6),The highest priority defect that has been present since the MEPs Fault Notification Generator State Machine was last in the FNG_RESET state. 
.1.0.8802.1.1.3.1.6.1.1.16,IEEE802171-CFM-MIB::dot1agCfmMepSomeRdiDefect,INTEGER,read-only,,current,true(1):false(2),A Boolean flag indicating that some other MEP in this MEP's MA is transmitting the RDI bit. 
.1.0.8802.1.1.3.1.6.1.1.17,IEEE802171-CFM-MIB::dot1agCfmMepErrMacStatus,INTEGER,read-only,,current,true(1):false(2),A Boolean flag (someMACstatusDefect, 20.33.6) indicating that a Port Status TLV (21.5.4) or Interface Status TLV (21.5.5) is indicating an error condition (can trigger DefMACstatus). 
.1.0.8802.1.1.3.1.6.1.1.18,IEEE802171-CFM-MIB::dot1agCfmMepSomeRMepCcmDefect,INTEGER,read-only,,current,true(1):false(2),A Boolean flag indicating that CCMs are not being received from at least one of the configured remote MEPs. 
.1.0.8802.1.1.3.1.6.1.1.19,IEEE802171-CFM-MIB::dot1agCfmMepErrorCcmDefect,INTEGER,read-only,,current,true(1):false(2),A Boolean flag indicating that a stream of erroneous CCMs is being received from some MEP in this MEP's MA. 
.1.0.8802.1.1.3.1.6.1.1.20,IEEE802171-CFM-MIB::dot1agCfmMepXconCcmDefect,INTEGER,read-only,,current,true(1):false(2),A Boolean flag indicating that a stream of CCMs is being received from a MEP that may be in some other MA. 
.1.0.8802.1.1.3.1.6.1.1.21,IEEE802171-CFM-MIB::dot1agCfmMepErrorCcmLastFailure,OCTET,read-only,,current,,The last-received CCM that triggered an DefErrorCCM fault.
.1.0.8802.1.1.3.1.6.1.1.22,IEEE802171-CFM-MIB::dot1agCfmMepXconCcmLastFailure,OCTET,read-only,,current,,The last-received CCM that triggered a DefXconCCM fault.
.1.0.8802.1.1.3.1.6.1.1.23,IEEE802171-CFM-MIB::dot1agCfmMepRCcmSequenceErrors,Counter32,read-only,,current,,The total number of out-of-sequence CCMs received from all remote MEPs. 
.1.0.8802.1.1.3.1.6.1.1.24,IEEE802171-CFM-MIB::dot1agCfmMepCciSentCcms,Counter32,read-only,,current,,Total number of Continuity Check messages transmitted.
.1.0.8802.1.1.3.1.6.1.1.25,IEEE802171-CFM-MIB::dot1agCfmMepNextLbmTransId,Unsigned32,read-only,,current,,Next sequence number/transaction identifier to be sent in a Loopback message. This sequence number can be zero because it wraps around. 
.1.0.8802.1.1.3.1.6.1.1.26,IEEE802171-CFM-MIB::dot1agCfmMepLbrIn,Counter32,read-only,,current,,Total number of valid, in-order Loopback Replies received.
.1.0.8802.1.1.3.1.6.1.1.27,IEEE802171-CFM-MIB::dot1agCfmMepLbrInOutOfOrder,Counter32,read-only,,current,,The total number of valid, out-of-order Loopback Replies received. 
.1.0.8802.1.1.3.1.6.1.1.28,IEEE802171-CFM-MIB::dot1agCfmMepLbrBadMsdu,Counter32,read-only,,current,,(optional) The total number of LBRs received whose mac_service_data_unit did not match (except for the OpCode) that of the corresponding LBM (20.2.3). 
.1.0.8802.1.1.3.1.6.1.1.29,IEEE802171-CFM-MIB::dot1agCfmMepLtmNextSeqNumber,Unsigned32,read-only,,current,,Next transaction identifier/sequence number to be sent in a Linktrace message. This sequence number can be zero because it wraps around. 
.1.0.8802.1.1.3.1.6.1.1.30,IEEE802171-CFM-MIB::dot1agCfmMepUnexpLtrIn,Counter32,read-only,,current,,The total number of unexpected LTRs received (20.39.1). 
.1.0.8802.1.1.3.1.6.1.1.31,IEEE802171-CFM-MIB::dot1agCfmMepLbrOut,Counter32,read-only,,current,,Total number of Loopback Replies transmitted.
.1.0.8802.1.1.3.1.6.1.1.32,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmStatus,INTEGER,read-write,,current,true(1):false(2),A Boolean flag set to true by the bridge port to indicate that another LBM may be transmitted.  Reset to false by the MEP Loopback Initiator State Machine.
.1.0.8802.1.1.3.1.6.1.1.33,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmDestMacAddress,OCTET,read-create,,current,,The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is 'false'. 
.1.0.8802.1.1.3.1.6.1.1.34,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmDestMepId,Unsigned32,read-create,,current,,The Maintenance association End Point Identifier of another MEP in the same Maintenance Association to which the LBM is to be sent. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is 'true'. 
.1.0.8802.1.1.3.1.6.1.1.35,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmDestIsMepId,INTEGER,read-create,,current,true(1):false(2),True indicates that MepID of the target MEP is used for Loopback transmission. False indicates that unicast destination MAC address of the target MEP is used for Loopback transmission. 
.1.0.8802.1.1.3.1.6.1.1.36,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmMessages,Integer32,read-create,,current,,The number of Loopback messages to be transmitted.
.1.0.8802.1.1.3.1.6.1.1.37,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmDataTlv,OCTET,read-create,,current,,An arbitrary amount of data to be included in the Data TLV, if the Data TLV is selected to be sent. 
.1.0.8802.1.1.3.1.6.1.1.38,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmVlanPriority,Integer32,read-create,,current,,Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted frame. The default value is CCM priority. 
.1.0.8802.1.1.3.1.6.1.1.39,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmVlanDropEnable,INTEGER,read-create,,current,true(1):false(2),Drop Enable bit value to be used in the VLAN tag, if present in the transmitted frame. For more information about VLAN Drop Enable, please check IEEE 802.1ad. 
.1.0.8802.1.1.3.1.6.1.1.40,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmResultOK,INTEGER,read-only,,current,true(1):false(2),Indicates the result of the operation: - true The Loopback Message(s) will be (or hasbeen) sent. - false The Loopback Message(s) will not be sent. 
.1.0.8802.1.1.3.1.6.1.1.41,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLbmSeqNumber,Unsigned32,read-only,,current,,The Loopback Transaction Identifier (dot1agCfmMepNextLbmTransId) of the first LBM (to be) sent. The value returned is undefined if dot1agCfmMepTransmitLbmResultOK is false. 
.1.0.8802.1.1.3.1.6.1.1.42,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmStatus,INTEGER,read-write,,current,true(1):false(2),A Boolean flag set to true by the bridge port to indicate that another LTM may be transmitted.  Reset to false by the MEP Linktrace Initiator State Machine.
.1.0.8802.1.1.3.1.6.1.1.43,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmFlags,BITS,read-create,,current,useFDBonly(0),The flags field for LTMs transmitted by the MEP.
.1.0.8802.1.1.3.1.6.1.1.44,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmTargetMacAddress,OCTET,read-create,,current,,The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is 'false'. 
.1.0.8802.1.1.3.1.6.1.1.45,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmTargetMepId,Unsigned32,read-create,,current,,An indication of the Target MAC Address Field to be transmitted: The Maintenance association End Point Identifier of another MEP in the same Maintenance Association This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is 'true'. 
.1.0.8802.1.1.3.1.6.1.1.46,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmTargetIsMepId,INTEGER,read-create,,current,true(1):false(2),True indicates that MepID of the target MEP is used for Linktrace transmission. False indicates that unicast destination MAC address of the target MEP is used for Loopback transmission. 
.1.0.8802.1.1.3.1.6.1.1.47,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmTtl,Unsigned32,read-create,,current,,The LTM TTL field. Default value, if not specified, is 64. The TTL field indicates the number of hops remaining to the LTM. Decremented by 1 by each Linktrace Responder that handles the LTM. The decremented value is returned in the LTR. If 0 on input, the LTM is discarded. If 0 on output, the LTM is not transmitted to the next hop. 
.1.0.8802.1.1.3.1.6.1.1.48,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmResult,INTEGER,read-only,,current,true(1):false(2),Indicates the result of the operation: - true The Linktrace Message will be (or has been) sent. - false The Linktrace Message will not be sent
.1.0.8802.1.1.3.1.6.1.1.49,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmSeqNumber,Unsigned32,read-only,,current,,The LTM Transaction Identifier (dot1agCfmMepLtmNextSeqNumber) of the LTM sent. The value returned is undefined if dot1agCfmMepTransmitLtmResult is false. 
.1.0.8802.1.1.3.1.6.1.1.50,IEEE802171-CFM-MIB::dot1agCfmMepTransmitLtmEgressIdentifier,OCTET,read-create,,current,,Identifies the MEP Linktrace Initiator that is originating, or the Linktrace Responder that is forwarding, this LTM. The low-order six octets contain a 48-bit IEEE MAC address unique to the system in which the MEP Linktrace Initiator or Linktrace Responder resides. The high-order two octets contain a value sufficient to uniquely identify the MEP Linktrace Initiator or Linktrace Responder within that system. For most Bridges, the address of any MAC attached to the Bridge will suffice for the low-order six octets, and 0 for the high-order octets. In some situations, e.g. if multiple virtual Bridges utilizing emulated LANs are implemented in a single physical system, the high-order two octets can be used to differentiate among the transmitting entities. The value returned is undefined if dot1agCfmMepTransmitLtmResult is false. 
.1.0.8802.1.1.3.1.6.1.1.51,IEEE802171-CFM-MIB::dot1agCfmMepRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row can not be changed if the row is active. All columns must have a valid value before a row can be activated. 
.1.0.8802.1.1.3.1.6.2,IEEE802171-CFM-MIB::dot1agCfmLtrTable,,not-accessible,,current,,This table extends the MEP table and contains a list of Linktrace replies received by a specific MEP in response to a linktrace message. SNMP SMI does not allow to state in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices. 
.1.0.8802.1.1.3.1.6.2.1,IEEE802171-CFM-MIB::dot1agCfmLtrEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:dot1agCfmLtrSeqNumber:dot1agCfmLtrReceiveOrder,current,,The LinktraceReply table entry.
.1.0.8802.1.1.3.1.6.2.1.1,IEEE802171-CFM-MIB::dot1agCfmLtrSeqNumber,Unsigned32,not-accessible,,current,,Transaction identifier/Sequence number returned by a previous transmit linktrace message command, indicating which LTM's response is going to be returned. 
.1.0.8802.1.1.3.1.6.2.1.2,IEEE802171-CFM-MIB::dot1agCfmLtrReceiveOrder,Unsigned32,not-accessible,,current,,An index to distinguish among multiple LTRs with the same LTR Transaction Identifier field value. dot1agCfmLtrReceiveOrder are assigned sequentially from 1, in the order that the Linktrace Initiator received the LTRs. 
.1.0.8802.1.1.3.1.6.2.1.3,IEEE802171-CFM-MIB::dot1agCfmLtrTtl,Unsigned32,read-only,,current,,TTL field value for a returned LTR.
.1.0.8802.1.1.3.1.6.2.1.4,IEEE802171-CFM-MIB::dot1agCfmLtrForwarded,INTEGER,read-only,,current,true(1):false(2),Indicates if a LTM was forwarded by the repsonding MP, as returned ind the 'FwdYes' flag of the flags field. 
.1.0.8802.1.1.3.1.6.2.1.5,IEEE802171-CFM-MIB::dot1agCfmLtrTerminalMep,INTEGER,read-only,,current,true(1):false(2),A boolean value stating whether the forwarded LTM reached a MEP enclosing its MA, as returned in the Terminal MEP flag of the Flags field. 
.1.0.8802.1.1.3.1.6.2.1.6,IEEE802171-CFM-MIB::dot1agCfmLtrLastEgressIdentifier,OCTET,read-only,,current,,An octet field holding the Last Egress Identifier returned in the LTR. The Last Egress Identifier identifies the MEP Linktrace  Initiator that originated, or the Linktrace Responder that  forwarded, the LTM to which this LTR is the response. This is the same value as the Egress Identifier field of that LTM. 
.1.0.8802.1.1.3.1.6.2.1.7,IEEE802171-CFM-MIB::dot1agCfmLtrNextEgressIdentifier,OCTET,read-only,,current,,An octet field holding the Next Egress Identifier returned in the LTR. The Next Egress Identifier Identifies the Linktrace Responder that transmitted this LTR, and can forward the LTM to the next hop. This is the same value as the Egress Identifier of the  forwarded LTM, if any. If the FwdYes bit of the Flags field is false, the contents of this field are undefined, i.e. any value can be transmitted, and the field is ignored by the receiver. 
.1.0.8802.1.1.3.1.6.2.1.8,IEEE802171-CFM-MIB::dot1agCfmLtrRelay,INTEGER,read-only,,current,rlyHit(1):rlyFdb(2):rlyMpdb(3),Value returned in the Relay Action field.
.1.0.8802.1.1.3.1.6.2.1.9,IEEE802171-CFM-MIB::dot1agCfmLtrChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),This object specifies the format of the Chassis ID returned in the Sender ID TLV of the LTR, if any. This value is meaningless if the dot1agCfmLtrChassisId has a length of 0.
.1.0.8802.1.1.3.1.6.2.1.10,IEEE802171-CFM-MIB::dot1agCfmLtrChassisId,OCTET,read-only,,current,,The Chassis ID returned in the Sender ID TLV of the LTR, if any. The format of this object is determined by the value of the dot1agCfmLtrChassisIdSubtype object. 
.1.0.8802.1.1.3.1.6.2.1.11,IEEE802171-CFM-MIB::dot1agCfmLtrManAddressType,INTEGER,read-only,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),Management Address subtype of the bridge transmitting the LTR, if returned in a Sender ID TLV. The value is meaningless if the dot1agCfmLtrManAddress has a length of 0. 
.1.0.8802.1.1.3.1.6.2.1.12,IEEE802171-CFM-MIB::dot1agCfmLtrManAddress,OCTET,read-only,,current,,Management Address information of the bridge transmitting the LTR, if returned in the Sender ID TLV. Some limitation to the size of the TLVs carrying a Manaement Address is needed, as there is no bound on the lengths of AddressFamilyNumbers. 31 octets, the maximum length of LldpManAddress, is long enough for currently deployed systems. This MIB module assumes that SNMP (IETF STD 62) is used along with the Management Address to access the management database. 
.1.0.8802.1.1.3.1.6.2.1.13,IEEE802171-CFM-MIB::dot1agCfmLtrIngress,INTEGER,read-only,,current,ingOk(1):ingDown(2):ingBlocked(3):ingVid(4),The value returned in the Ingress Action Field of the LTM.
.1.0.8802.1.1.3.1.6.2.1.14,IEEE802171-CFM-MIB::dot1agCfmLtrIngressMac,OCTET,read-only,,current,,MAC address returned in the ingress MAC address field.
.1.0.8802.1.1.3.1.6.2.1.15,IEEE802171-CFM-MIB::dot1agCfmLtrIngressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Format of the Ingress Port ID.
.1.0.8802.1.1.3.1.6.2.1.16,IEEE802171-CFM-MIB::dot1agCfmLtrIngressPortId,OCTET,read-only,,current,,Ingress Port ID. The format of this object is determined by the value of the dot1agCfmLtrIngressPortIdSubtype object. 
.1.0.8802.1.1.3.1.6.2.1.17,IEEE802171-CFM-MIB::dot1agCfmLtrEgress,INTEGER,read-only,,current,egrOK(1):egrDown(2):egrBlocked(3):egrVid(4),The value returned in the Egress Action Field of the LTM.
.1.0.8802.1.1.3.1.6.2.1.18,IEEE802171-CFM-MIB::dot1agCfmLtrEgressMac,OCTET,read-only,,current,,MAC address returned in the egress MAC address field.
.1.0.8802.1.1.3.1.6.2.1.19,IEEE802171-CFM-MIB::dot1agCfmLtrEgressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Format of the egress Port ID.
.1.0.8802.1.1.3.1.6.2.1.20,IEEE802171-CFM-MIB::dot1agCfmLtrEgressPortId,OCTET,read-only,,current,,Egress Port ID. The format of this object is determined by the value of the dot1agCfmLtrEgressPortIdSubtype object. 
.1.0.8802.1.1.3.1.6.2.1.21,IEEE802171-CFM-MIB::dot1agCfmLtrOrganizationSpecificTlv,OCTET,read-only,,current,,All Organization specific TLVs returned in the LTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.
.1.0.8802.1.1.3.1.6.3,IEEE802171-CFM-MIB::dot1agCfmMepDbTable,,not-accessible,,current,,The MEP Database. A database, maintained by every MEP, that maintains received information about other MEPs in the Maintenance Domain. SNMP SMI does not allow to stat in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices. 
.1.0.8802.1.1.3.1.6.3.1,IEEE802171-CFM-MIB::dot1agCfmMepDbEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:dot1agCfmMepDbRMepIdentifier,current,,The MEP Database table entry.
.1.0.8802.1.1.3.1.6.3.1.1,IEEE802171-CFM-MIB::dot1agCfmMepDbRMepIdentifier,Unsigned32,not-accessible,,current,,Maintenance association End Point Identifier of a remote MEP whose information from the MEP Database is to be returned. 
.1.0.8802.1.1.3.1.6.3.1.2,IEEE802171-CFM-MIB::dot1agCfmMepDbRMepState,INTEGER,read-only,,current,rMepIdle(1):rMepStart(2):rMepFailed(3):rMepOk(4),The operational state of the remote MEP IFF State machines.
.1.0.8802.1.1.3.1.6.3.1.3,IEEE802171-CFM-MIB::dot1agCfmMepDbRMepFailedOkTime,TimeTicks,read-only,,current,,The time (SysUpTime) at which the IFF Remote MEP state machine last entered either the RMEP_FAILED or RMEP_OK state. 
.1.0.8802.1.1.3.1.6.3.1.4,IEEE802171-CFM-MIB::dot1agCfmMepDbMacAddress,OCTET,read-only,,current,,The MAC address of the remote MEP.
.1.0.8802.1.1.3.1.6.3.1.5,IEEE802171-CFM-MIB::dot1agCfmMepDbRdi,INTEGER,read-only,,current,true(1):false(2),State of the RDI bit in the last received CCM (true for RDI=1), or false if none has been received. 
.1.0.8802.1.1.3.1.6.3.1.6,IEEE802171-CFM-MIB::dot1agCfmMepDbPortStatusTlv,INTEGER,read-only,,current,psNoPortStateTLV(0):psBlocked(1):psUp(2),An enumerated value of the Port status TLV received in the last CCM from the remote MEP or the default value psNoPortStateTLV indicating either no CCM has been received, or that nor port status TLV was received in the last CCM. 
.1.0.8802.1.1.3.1.6.3.1.7,IEEE802171-CFM-MIB::dot1agCfmMepDbInterfaceStatusTlv,INTEGER,read-only,,current,isNoInterfaceSatatusTLV(0):isUp(1):isDown(2):isTesting(3):isUnknown(4):isDormant(5):isNotPresent(6):isLowerLayerDown(7),An enumerated value of the Interface status TLV received in the last CCM from the remote MEP or the default value isNoInterfaceStatus TLV indicating either no CCM has been received, or that no interface status TLV was received in the last CCM. 
.1.0.8802.1.1.3.1.6.3.1.8,IEEE802171-CFM-MIB::dot1agCfmMepDbChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),This object specifies the format of the Chassis ID received in the last CCM.
.1.0.8802.1.1.3.1.6.3.1.9,IEEE802171-CFM-MIB::dot1agCfmMepDbChassisId,OCTET,read-only,,current,,The Chassis ID. The format of this object is determined by the value of the dot1agCfmLtrChassisIdSubtype object. 
.1.0.8802.1.1.3.1.6.3.1.10,IEEE802171-CFM-MIB::dot1agCfmMepDbManAddressType,INTEGER,read-only,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),Management Address subtype of the bridge transmitting the CCM. 
.1.0.8802.1.1.3.1.6.3.1.11,IEEE802171-CFM-MIB::dot1agCfmMepDbManAddress,OCTET,read-only,,current,,Management Address information of the bridge transmitting the CCM. Some limitation to the size of the TLVs carrying a Manaement Address is needed, as there is no bound on the lengths of AddressFamilyNumbers. 31 octets, the maximum length of LldpManAddress, is long enough for currently deployed systems. This MIB module assumes that SNMP (IETF STD 62) is used along with the Management Address to access the management database. 
.1.0.8802.1.1.3.2,IEEE8021-SECY-MIB::secyMIBConformance,,,,,,
.1.0.8802.1.1.3.2.1,IEEE8021-SECY-MIB::secyMIBCompliances,,,,,,
.1.0.8802.1.1.3.2.1.1,IEEE8021-SECY-MIB::secyMIBCompliance,,,,,,The compliance statement for the IEEE8021-SECY-MIB as specified in IEEE Std 802.1AE-2006.
.1.0.8802.1.1.3.2.1.2,IEEE8021-SECY-MIB::secyMIBTcCompliance,,,,,,The compliance statement for an IEEE8021-SECY-MIB supporting traffic class transmit SCs, added by IEEE 802.1AEcg.
.1.0.8802.1.1.3.2.2,IEEE8021-SECY-MIB::secyMIBGroups,,,,,,
.1.0.8802.1.1.3.2.2.1,IEEE8021-SECY-MIB::secyIfCtrlGroup,,,,,,SecY service management (secyIfTable) objects.
.1.0.8802.1.1.3.2.2.2,IEEE8021-SECY-MIB::secyTxSCGroup,,,,,,Transmit SC management objects (for systems without traffic class SC capabilities).
.1.0.8802.1.1.3.2.2.3,IEEE8021-SECY-MIB::secyTxSAGroup,,,,,,Transmit SA management objects (for systems without traffic class SC capabilities).
.1.0.8802.1.1.3.2.2.4,IEEE8021-SECY-MIB::secyRxSCGroup,,,,,,Receive SC management objects.
.1.0.8802.1.1.3.2.2.5,IEEE8021-SECY-MIB::secyRxSAGroup,,,,,,Receive SA management objects.
.1.0.8802.1.1.3.2.2.6,IEEE8021-SECY-MIB::secyCipherSuiteGroup,,,,,,Cipher Suite information objects.
.1.0.8802.1.1.3.2.2.7,IEEE8021-SECY-MIB::secyTxSAStatsGroup,,,,,,Transmit SA statistics objects.
.1.0.8802.1.1.3.2.2.8,IEEE8021-SECY-MIB::secyRxSAStatsGroup,,,,,,Receive SA statistics objects.
.1.0.8802.1.1.3.2.2.9,IEEE8021-SECY-MIB::secyTxSCStatsGroup,,,,,,Transmit SC statistics objects.
.1.0.8802.1.1.3.2.2.10,IEEE8021-SECY-MIB::secyRxSCStatsGroup,,,,,,Receive SC statistics objects.
.1.0.8802.1.1.3.2.2.11,IEEE8021-SECY-MIB::secyStatsGroup,,,,,,SecY statistics objects.
.1.0.8802.1.1.3.2.2.12,IEEE8021-SECY-MIB::secyIfGroup,,,,,,SecY service management (secyIfTable objects) for  systems supporting traffic class SCs.
.1.0.8802.1.1.3.2.2.13,IEEE8021-SECY-MIB::secyIfCipherGroup,,,,,,Cipher Suite use control (secyIfCipherTable objects).
.1.0.8802.1.1.3.2.2.14,IEEE8021-SECY-MIB::secyIfTCGroup,,,,,,Traffic class control (secyIfTCTable).
.1.0.8802.1.1.3.2.2.15,IEEE8021-SECY-MIB::secyIfAPGroup,,,,,,Access Priority Code Point control (secyIfAPTable).
.1.0.8802.1.1.3.2.2.16,IEEE8021-SECY-MIB::secyTSCGroup,,,,,,Transmit SC management (secyTSCTable objects) for systems supporting traffic class SCs.
.1.0.8802.1.1.3.2.2.17,IEEE8021-SECY-MIB::secyTSAGroup,,,,,,Transmit SA management (secyTSATable objects) for systems supporting traffic class SCs.
.1.0.8802.1.1.3.2.2.18,IEEE8021-SECY-MIB::secyRSCGroup,,,,,,Receive SC management (secyRxSCTable objects).
.1.0.8802.1.1.3.2.2.19,IEEE8021-SECY-MIB::secyRSAGroup,,,,,,Receive SA (secyRxSATable objects).
.1.0.8802.1.1.3.2.2.20,IEEE8021-SECY-MIB::secyIfStatsGroup,,,,,,SecY statistics (secyStatsTable objects).
.1.0.8802.1.1.3.2.2.21,IEEE8021-SECY-MIB::secyCipherInfoGroup,,,,,,Cipher Suite implementation information  (secyCipherSuiteTable objects).
.1.0.8802.1.1.3.2.2.22,IEEE8021-SECY-MIB::secyTSCStatsGroup,,,,,,Transmit SC statistics (secyTSCStatsTable objects).
.1.0.8802.1.1.3.2.2.23,IEEE8021-SECY-MIB::secyRSCStatsGroup,,,,,,Receive SC statistics (secyRxSCStatsTable objects).
.1.0.8802.1.1.3.2.2.24,IEEE8021-SECY-MIB::secyCipherStatsGroup,,,,,,Cipher Suite performance statistics (from secyStatsTable).
.1.2,IEEE8023-LAG-MIB::member-body,,,,,,
.1.2.840,IEEE8023-LAG-MIB::us,,,,,,
.1.2.840.10006,IEEE8023-LAG-MIB::ieee802dot3,,,,,,
.1.2.840.10006.300,IEEE8023-LAG-MIB::snmpmibs,,,,,,
.1.2.840.10006.300.43,IEEE8023-LAG-MIB::lagMIB,,,,,,The Link Aggregation module for managing IEEE 802.1AX-2014 as updated by 802.1AX-2014-Cor1.
.1.2.840.10006.300.43.0,IEEE8023-LAG-MIB::lagMIBNotifications,,,,,,
.1.2.840.10006.300.43.0.1,IEEE8023-LAG-MIB::dot3adAggLinkUpNotification,,,,,,When aAggLinkUpDownNotificationEnable is set to 'enabled,' a Link Up notification is generated when the Operational State of the Aggregator changes from 'down' to 'up.' When aAggLinkUpDownNotificationEnable is set to 'disabled,' no Link Up notifications are generated. The notification carries the identifier of the Aggregator whose state has changed.
.1.2.840.10006.300.43.0.2,IEEE8023-LAG-MIB::dot3adAggLinkDownNotification,,,,,,When aAggLinkUpDownNotificationEnable is set to 'enabled,' a Link Down notification is generated when the Operational State of the Aggregator changes from 'up' to 'down.' When aAggLinkUpDownNotificationEnable is set to 'disabled,' no Link Down notifications are generated. The notification carries the identifier of the Aggregator whose state has changed.
.1.2.840.10006.300.43.1,IEEE8023-LAG-MIB::lagMIBObjects,,,,,,
.1.2.840.10006.300.43.1.1,IEEE8023-LAG-MIB::dot3adAgg,,,,,,
.1.2.840.10006.300.43.1.1.1,IEEE8023-LAG-MIB::dot3adAggTable,,not-accessible,,current,,A table that contains information about every Aggregator that is associated with this System.
.1.2.840.10006.300.43.1.1.1.1,IEEE8023-LAG-MIB::dot3adAggEntry,,not-accessible,dot3adAggIndex,current,,A list of the Aggregator parameters. This is indexed by the ifIndex of the Aggregator.
.1.2.840.10006.300.43.1.1.1.1.1,IEEE8023-LAG-MIB::dot3adAggIndex,Integer32,not-accessible,,current,,The unique identifier allocated to this Aggregator by the local System. This attribute identifies an Aggregator instance among the subordinate managed objects of the containing object. This value is read-only. NOTE-The aAggID is represented in the SMIv2 MIB as an ifIndex-see D.4.1.
.1.2.840.10006.300.43.1.1.1.1.2,IEEE8023-LAG-MIB::dot3adAggMACAddress,OCTET,read-only,,current,,A 6-octet read-only value carrying the individual MAC address assigned to the Aggregator.
.1.2.840.10006.300.43.1.1.1.1.3,IEEE8023-LAG-MIB::dot3adAggActorSystemPriority,Integer32,read-write,,current,,A 2-octet read-write value indicating the priority value associated with the Actor's System ID.
.1.2.840.10006.300.43.1.1.1.1.4,IEEE8023-LAG-MIB::dot3adAggActorSystemID,OCTET,read-write,,current,,A 6-octet read-write MAC address value used as a unique identifier for the System that contains this Aggregator. NOTE-From the perspective of the Link Aggregation mechanisms described in Clause 6, only a single combination of Actor's System ID and System Priority are considered, and no distinction is made between the values of these parameters for an Aggregator and the port(s) that are associated with it; i.e., the protocol is described in terms of the operation of aggregation within a single System. However, the managed objects provided for the Aggregator and the port both allow management of these parameters. The result of this is to permit a single piece of equipment to be configured by management to contain more than one System from the point of view of the operation of Link Aggregation. This may be of particular use in the configuration of equipment that has limited aggregation capability (see 6.7).
.1.2.840.10006.300.43.1.1.1.1.5,IEEE8023-LAG-MIB::dot3adAggAggregateOrIndividual,INTEGER,read-only,,current,true(1):false(2),A read-only Boolean value indicating whether the Aggregator represents an Aggregate ('TRUE') or an Individual link ('FALSE').
.1.2.840.10006.300.43.1.1.1.1.6,IEEE8023-LAG-MIB::dot3adAggActorAdminKey,Integer32,read-write,,current,,The current administrative value of the Key for the Aggregator. The administrative Key value may differ from the operational Key value for the reasons discussed in 6.7.2. This is a 16-bit read-write value. The meaning of particular Key values is of local significance. For an Aggregator that is associated with a Portal, the aAggActorAdminKey has to be different for each Portal System. Specifically the two most significant bits are set to aDrniPortalSystemNumber (7.4.1.1.7). The lower 14 bits may be any value, have  to be the same in each Portal System within the same Portal,
.1.2.840.10006.300.43.1.1.1.1.7,IEEE8023-LAG-MIB::dot3adAggActorOperKey,Integer32,read-only,,current,,The current operational value of the Key for the Aggregator. The administrative Key value may differ from the operational Key value for the reasons discussed in 6.7.2. This is a 16-bit read-only value. The meaning of particular Key values is of local significance.
.1.2.840.10006.300.43.1.1.1.1.8,IEEE8023-LAG-MIB::dot3adAggPartnerSystemID,OCTET,read-only,,current,,A 6-octet read-only MAC address value consisting of the unique identifier for the current protocol Partner of this Aggregator. A value of zero indicates that there is no known Partner. If the aggregation is manually configured, this  System ID value will be a value assigned by the local System.
.1.2.840.10006.300.43.1.1.1.1.9,IEEE8023-LAG-MIB::dot3adAggPartnerSystemPriority,Integer32,read-only,,current,,A 2-octet read-only value that indicates the priority value associated with the Partner's System ID. If the aggregation is manually configured, this System Priority value will be a value assigned by the local System.
.1.2.840.10006.300.43.1.1.1.1.10,IEEE8023-LAG-MIB::dot3adAggPartnerOperKey,Integer32,read-only,,current,,The current operational value of the Key for the Aggregator's current protocol Partner. This is a 16-bit read-only value. If the aggregation is manually configured, this Key value will be a value assigned by the local System.
.1.2.840.10006.300.43.1.1.1.1.11,IEEE8023-LAG-MIB::dot3adAggCollectorMaxDelay,Integer32,read-write,,current,,The value of this 16-bit read-write attribute defines the maximum delay, in tens of microseconds, that may be imposed by the Frame Collector between receiving a frame from an Aggregator Parser, and either delivering the frame to its Aggregator Client or discarding the frame (see 6.2.3.1.1).
.1.2.840.10006.300.43.1.1.2,IEEE8023-LAG-MIB::dot3adAggPortListTable,,not-accessible,,current,,A table that contains a list of all the ports associated with each Aggregator.
.1.2.840.10006.300.43.1.1.2.1,IEEE8023-LAG-MIB::dot3adAggPortListEntry,,not-accessible,dot3adAggIndex,current,,A list of the ports associated with a given Aggregator. This is indexed by the ifIndex of the Aggregator.
.1.2.840.10006.300.43.1.1.2.1.1,IEEE8023-LAG-MIB::dot3adAggPortListPorts,OCTET,read-only,,current,,The complete set of ports currently associated with this Aggregator. Each bit set in this list represents an Actor Port member of this Link Aggregation.
.1.2.840.10006.300.43.1.1.3,IEEE8023-LAG-MIB::dot3adAggXTable,,not-accessible,,current,,A table that extends dot3adAggTable.
.1.2.840.10006.300.43.1.1.3.1,IEEE8023-LAG-MIB::dot3adAggXEntry,,not-accessible,,current,,A list of extension parameters for the Aggregator Configuration Table
.1.2.840.10006.300.43.1.1.3.1.1,IEEE8023-LAG-MIB::dot3adAggDescription,OCTET,read-only,,current,,A human-readable text string containing information about the Aggregator. This string could include information about the distribution algorithm in use on this Aggregator; for example, 'Aggregator 1, Dist Alg=Dest MAC address.' This string is read-only. The contents are vendor specific.
.1.2.840.10006.300.43.1.1.3.1.2,IEEE8023-LAG-MIB::dot3adAggName,OCTET,read-write,,current,,A human-readable text string containing a locally significant name for the Aggregator. This string is read-write.
.1.2.840.10006.300.43.1.1.3.1.3,IEEE8023-LAG-MIB::dot3adAggAdminState,INTEGER,read-write,,current,up(1):down(2),This read-write value defines the administrative state of the Aggregator. A value of 'up' indicates that the operational state of the Aggregator (aAggOperState) is permitted to be either up or down. A value of 'down' forces the operational state of the Aggregator to be down. Changes to the administrative state affect the operational state of the Aggregator only, not the operational state of the Aggregation Ports that are attached to the Aggregator. A GET operation returns the current administrative state. A SET operation changes the administrative state to a new value.
.1.2.840.10006.300.43.1.1.3.1.4,IEEE8023-LAG-MIB::dot3adAggOperState,INTEGER,read-only,,current,up(1):down(2),This read-only value defines the operational state of the Aggregator. An operational state of 'up' indicates that the Aggregator is available for use by the Aggregator Client; a value of 'down' indicates that the Aggregator is not available for use by the Aggregator Client.
.1.2.840.10006.300.43.1.1.3.1.5,IEEE8023-LAG-MIB::dot3adAggTimeOfLastOperChange,Integer32,read-only,,current,,The time at which the interface entered its current operational state, in terms of centiseconds since the system was last reset. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a value of zero. The ifLastChange object in the Interfaces MIB defined in IETF RFC 2863 is a suitable object for supplying a value for aAggTimeOfLastOperChange. This value is read-only. the aTimeSinceSystemReset variable of IEEE Std 802.3-2008, F.2.1, in earlier versions of this standard. aTimeSinceSystemReset and ifLastChange have the same meaning.
.1.2.840.10006.300.43.1.1.3.1.6,IEEE8023-LAG-MIB::dot3adAggDataRate,Integer32,read-only,,current,,The current data rate, in bits per second, of the aggregate link. The value is calculated as the sum of the data rate of each link in the aggregation. This attribute is read-only.
.1.2.840.10006.300.43.1.1.3.1.7,IEEE8023-LAG-MIB::dot3adAggOctetsTxOK,Counter64,read-only,,current,,A count of the data and padding octets transmitted by this Aggregator on all Aggregation Ports that are (or have been) members of the aggregation. The count does not include octets transmitted by the Aggregator in frames that carry LACPDUs or Marker PDUs (7.3.3.1.7, 7.3.3.1.8, 7.3.3.1.9). However, it includes frames discarded by the Frame Distribution function of the Aggregator (7.3.1.1.25). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.8,IEEE8023-LAG-MIB::dot3adAggOctetsRxOK,Counter64,read-only,,current,,A count of the data and padding octets received by this Aggregator, from the Aggregation Ports that are (or have been) members of the aggregation. The count does not include octets received in frames that carry LACP or Marker PDUs (7.3.3.1.2, 7.3.3.1.3, 7.3.3.1.4), or frames discarded by the Frame Collection function of the Aggregator (7.3.1.1.26). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.9,IEEE8023-LAG-MIB::dot3adAggFramesTxOK,Counter64,read-only,,current,,A count of the data frames transmitted by this Aggregator on all Aggregation Ports that are (or have been) members of the aggregation. The count does not include frames transmitted by the Aggregator that carry LACP or Marker PDUs (7.3.3.1.7, 7.3.3.1.8, 7.3.3.1.9). However, it includes frames discarded by the Frame Distribution function of the Aggregator (7.3.1.1.25). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.10,IEEE8023-LAG-MIB::dot3adAggFramesRxOK,Counter64,read-only,,current,,A count of the data frames received by this Aggregator, from the Aggregation Ports that are (or have been) members of the aggregation. The count does not include frames that carry LACP or Marker PDUs (7.3.3.1.2, 7.3.3.1.3, 7.3.3.1.4), or frames discarded by the Frame Collection function of the Aggregator (7.3.1.1.26). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.11,IEEE8023-LAG-MIB::dot3adAggMulticastFramesTxOK,Counter64,read-only,,current,,A count of the data frames transmitted by this Aggregator on all Aggregation Ports that are (or have been) members of the aggregation, to a group DA other than the broadcast address. The count does not include frames transmitted by the Aggregator that carry LACP or Marker PDUs (7.3.3.1.7, 7.3.3.1.8, 7.3.3.1.9). However, it includes frames discarded by the Frame Distribution function of the Aggregator (7.3.1.1.25). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.12,IEEE8023-LAG-MIB::dot3adAggMulticastFramesRxOK,Counter64,read-only,,current,,A count of the data frames received by this Aggregator, from the Aggregation Ports that are (or have been) members of the aggregation, that were addressed to an active group address other than the broadcast address. The count does not include frames that carry LACP or Marker PDUs (7.3.3.1.2, 7.3.3.1.3, 7.3.3.1.4), or frames discarded by the Frame Collection function of the Aggregator (7.3.1.1.26). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.13,IEEE8023-LAG-MIB::dot3adAggBroadcastFramesTxOK,Counter64,read-only,,current,,A count of the broadcast data frames transmitted by this Aggregator on all Aggregation Ports that are (or have been) members of the aggregation. The count does not include frames transmitted by the Aggregator that carry LACP or Marker PDUs (7.3.3.1.7, 7.3.3.1.8, 7.3.3.1.9). However, it includes frames discarded by the Frame Distribution function of the Aggregator (7.3.1.1.25). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.14,IEEE8023-LAG-MIB::dot3adAggBroadcastFramesRxOK,Counter64,read-only,,current,,A count of the broadcast data frames received by this Aggregator, from the Aggregation Ports that are (or have been) members of the aggregation. The count does not include frames that carry LACP or Marker PDUs (7.3.3.1.2, 7.3.3.1.3, 7.3.3.1.4), illegal or unknown protocol frames (7.3.3.1.5, 7.3.3.1.6), or frames discarded by the Frame Collection function of the Aggregator (7.3.1.1.26). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.15,IEEE8023-LAG-MIB::dot3adAggFramesDiscardedOnTx,Counter64,read-only,,current,,A count of data frames requested to be transmitted by this Aggregator that were discarded by the Frame Distribution function of the Aggregator when conversations are reallocated to different Aggregation Ports, due to the requirement to ensure that the conversations are flushed on the old Aggregation Ports in order to maintain proper frame ordering (B.3), or discarded as a result of excessive collisions by Aggregation Ports that are (or have been) members of the aggregation. This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.16,IEEE8023-LAG-MIB::dot3adAggFramesDiscardedOnRx,Counter64,read-only,,current,,A count of data frames, received on all Aggregation Ports that are (or have been) members of the aggregation, that were discarded by the Frame Collection function of the Aggregator as they were received on Aggregation Ports whose Frame Collection function was disabled. This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.17,IEEE8023-LAG-MIB::dot3adAggFramesWithTxErrors,Counter64,read-only,,current,,A count of data frames requested to be transmitted by this Aggregator that experienced transmission errors on Aggregation Ports that are (or have been) members of the aggregation. This count does not include frames discarded due to excess collisions. This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.18,IEEE8023-LAG-MIB::dot3adAggFramesWithRxErrors,Counter64,read-only,,current,,A count of data frames discarded on reception by all Aggregation Ports that are (or have been) members of the aggregation, or that were discarded by the Frame Collection function of the Aggregator, or that were discarded by the Aggregator due to the detection of an illegal Slow Protocols PDU (7.3.3.1.6). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.19,IEEE8023-LAG-MIB::dot3adAggUnknownProtocolFrames,Counter64,read-only,,current,,A count of data frames discarded on reception by all Aggregation Ports that are (or have been) members of the aggregation, due to the detection of an unknown Slow Protocols PDU (7.3.3.1.5). This value is read-only.
.1.2.840.10006.300.43.1.1.3.1.20,IEEE8023-LAG-MIB::dot3adAggLinkUpDownNotificationEnable,INTEGER,read-write,,current,enabled(1):disabled(2),When set to 'enabled', Link Up and Link Down notifications are enabled for this Aggregator. When set to 'disabled', Link Up and Link Down notifications are disabled for this Aggregator. This value is read-write.
.1.2.840.10006.300.43.1.1.3.1.21,IEEE8023-LAG-MIB::dot3adAggPortAlgorithm,OCTET,read-write,,current,,This object identifies the algorithm used by the Aggregator to assign frames to a Port Conversation ID. Table 6-4 provides the IEEE 802.1 OUI (00-80-C2) Port Algorithm encodings. A SEQUENCE following octet.
.1.2.840.10006.300.43.1.1.3.1.22,IEEE8023-LAG-MIB::dot3adAggPartnerAdminPortAlgorithm,OCTET,read-write,,current,,This object identifies the value for the algorithm of the Partner System, assigned by administrator or System policy for use when the Partner's information is unknown. Table 6-4 provides the IEEE 802.1 OUI (00-80-C2) Port Algorithm encodings. Its default value is set to the 'Unspecified' value 
.1.2.840.10006.300.43.1.1.3.1.23,IEEE8023-LAG-MIB::dot3adAggPartnerAdminPortConversationListDigest,OCTET,read-write,,current,,The value for the digest of the prioritized Port Conversation ID-to-Link Number ID assignments of the Partner System, assigned by administrator or System policy for use when the Partner's information is unknown. Its default value is set to NULL.
.1.2.840.10006.300.43.1.1.3.1.24,IEEE8023-LAG-MIB::dot3adAggAdminDiscardWrongConversation,INTEGER,read-write,,deprecated,true(1):false(2),The administrative value that determines what the Aggregator Collection_Conversation_Mask. The value 'TRUE' indicates that
.1.2.840.10006.300.43.1.1.3.1.25,IEEE8023-LAG-MIB::dot3adAggPartnerAdminConvServiceMappingDigest,OCTET,read-write,,current,,The value for the digest of the Port Conversation ID-to-Service ID assignments of the Partner System, assigned by administrator or System policy for use when the Partner's information is unknown. Its default value is set to NULL.
.1.2.840.10006.300.43.1.1.3.1.26,IEEE8023-LAG-MIB::dot3adAggAdminDiscardWrongConversation2,INTEGER,read-write,,current,forceTrue(1):forceFalse(2):auto(3),The administrative value that determines whether an Aggregator Collection_Conversation_Mask. The value 'forceTrue' 
.1.2.840.10006.300.43.1.1.4,IEEE8023-LAG-MIB::dot3adAggConversationAdminLinkTable,,not-accessible,,current,,There are 4096 aAggConversationAdminPort[] variables, aAggConversationAdminLink[0] through aAggConversationAdminLink[4095], indexed by Port Conversation ID. Each contains administrative values of the link selection priority list for the referenced Port Conversation ID. This selection priority list is a sequence of Link-Number IDs for each Port Conversation ID, in the order of preference, highest to lowest, for the corresponding link to carry that Port Conversation ID. A 16-bit zero value is used to indicate that no link is assigned to carry the associated Port Conversation ID. NOTE - This mapping of Port Conversation IDs to Link Number IDs is the fundamental administrative input. An equivalent mapping of Port Conversation IDs to Port  IDs [Conversation_PortList[]] is derived from this and  used internally. NOTE - When a network administrator  issues a command for selection rules, provided by aAggConversationAdminLink[], the ChangeActorOperDist is set as  specified in 6.6.2.2.
.1.2.840.10006.300.43.1.1.4.1,IEEE8023-LAG-MIB::dot3adAggConversationAdminLinkEntry,,not-accessible,dot3adAggConversationAdminLinkId:dot3adAggIndex,current,,An entry contains administrative values of the link selection priority list for the referenced Port Conversation ID. This selection priority list is a sequence of Link-Number IDs for each Port Conversation ID, in the order of preference, highest to lowest, for the corresponding link to carry that Port Conversation ID. A 16 bit zero value is used to indicate that no link is assigned to carry the associated Port Conversation ID.
.1.2.840.10006.300.43.1.1.4.1.1,IEEE8023-LAG-MIB::dot3adAggConversationAdminLinkId,Integer32,not-accessible,,current,,An identifier for Port Conversation.
.1.2.840.10006.300.43.1.1.4.1.2,IEEE8023-LAG-MIB::dot3adAggConversationAdminLinkList,OCTET,read-write,,current,,Each two octets of the octet string represent the agreed Link Number ID that is assigned to an Aggregation Port (7.3.2.1.27). The list is in the order of preference, highest to lowest, for corresponding preferred link to carry that Port Conversation ID.
.1.2.840.10006.300.43.1.1.5,IEEE8023-LAG-MIB::dot3adAggAdminServiceConversationMapTable,,not-accessible,,current,,There are 4096 aAggAdminServiceConversationMap[] variables, aAggAdminServiceConversationMap[0] through aAggAdminServiceConversationMap[4095], indexed by Port Conversation ID. Each contains, in general, a set of Service IDs (8.2.2), unique within the array. If the Service IDs are representing VIDs, only a single VID is used, while in the case that Service IDs are representing I-SIDs, more than one I-SIDs are possible. Service IDs not contained in the map are not mapped to any Port Conversation ID and will be discarded.
.1.2.840.10006.300.43.1.1.5.1,IEEE8023-LAG-MIB::dot3adAggAdminServiceConversationMapEntry,,not-accessible,dot3adAggAdminServiceConversationMapId:dot3adAggIndex,current,,An entry contains, in general, a set of Service IDs (8.2.2), unique within the array. If the Service IDs are representing VIDs, only a single VID is applicable, while in the case that Service IDs are representing I-SIDs, more than one I-SIDs are possible.
.1.2.840.10006.300.43.1.1.5.1.1,IEEE8023-LAG-MIB::dot3adAggAdminServiceConversationMapId,Integer32,not-accessible,,current,,The Port Conversation ID used to index Conversation Map entries.
.1.2.840.10006.300.43.1.1.5.1.2,IEEE8023-LAG-MIB::dot3adAggAdminServiceConversationServiceIDList,OCTET,read-write,,current,,A list contains, in general, a set of Service IDs (8.2.2), unique within the array.
.1.2.840.10006.300.43.1.2,IEEE8023-LAG-MIB::dot3adAggPort,,,,,,
.1.2.840.10006.300.43.1.2.1,IEEE8023-LAG-MIB::dot3adAggPortTable,,not-accessible,,current,,A table that contains Link Aggregation Control configuration information about every Aggregation Port associated with this device. A row appears in this table for each physical port.
.1.2.840.10006.300.43.1.2.1.1,IEEE8023-LAG-MIB::dot3adAggPortEntry,,not-accessible,dot3adAggPortIndex,current,,A list of Link Aggregation Control configuration parameters for each Aggregation Port on this device.
.1.2.840.10006.300.43.1.2.1.1.1,IEEE8023-LAG-MIB::dot3adAggPortIndex,Integer32,not-accessible,,current,,The unique identifier allocated to this Aggregation Port by the local System. This attribute identifies an Aggregation Port instance among the subordinate managed objects of the containing object. This value is read-only. NOTE-The aAggPortID is represented in the SMIv2 MIB as an ifIndex-see D.4.1.
.1.2.840.10006.300.43.1.2.1.1.2,IEEE8023-LAG-MIB::dot3adAggPortActorSystemPriority,Integer32,read-write,,current,,A 2-octet read-write value used to define the priority value associated with the Actor's System ID.
.1.2.840.10006.300.43.1.2.1.1.3,IEEE8023-LAG-MIB::dot3adAggPortActorSystemID,OCTET,read-only,,current,,A 6-octet read-only MAC address value that defines the value of the System ID for the System that contains this  Aggregation Port.
.1.2.840.10006.300.43.1.2.1.1.4,IEEE8023-LAG-MIB::dot3adAggPortActorAdminKey,Integer32,read-write,,current,,The current administrative value of the Key for the Aggregation Port. This is a 16-bit read-write value. The meaning of particular Key values is of local significance.
.1.2.840.10006.300.43.1.2.1.1.5,IEEE8023-LAG-MIB::dot3adAggPortActorOperKey,Integer32,read-only,,current,,The current operational value of the Key for the Aggregation Port. This is a 16-bit read-only value. The meaning of particular Key values is of local significance.
.1.2.840.10006.300.43.1.2.1.1.6,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminSystemPriority,Integer32,read-write,,current,,A 2-octet read-write value used to define the administrative value of priority associated with the Partner's System ID. The assigned value is used, along with the value of aAggPortPartnerAdminSystemID, aAggPortPartnerAdminKey, aAggPortPartnerAdminPort, and aAggPortPartnerAdminPortPriority, in order to achieve manually configured aggregation.
.1.2.840.10006.300.43.1.2.1.1.7,IEEE8023-LAG-MIB::dot3adAggPortPartnerOperSystemPriority,Integer32,read-only,,current,,A 2-octet read-only value indicating the operational value of priority associated with the Partner's System ID. The value of this attribute may contain the manually configured value carried in aAggPortPartnerAdminSystemPriority if there is no protocol Partner.
.1.2.840.10006.300.43.1.2.1.1.8,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminSystemID,OCTET,read-write,,current,,A 6-octet read-write MACAddress value representing the administrative value of the Aggregation Port's protocol Partner's System ID. The assigned value is used, along with the value of aAggPortPartnerAdminSystemPriority, aAggPortPartnerAdminKey, aAggPortPartnerAdminPort, and aAggPortPartnerAdminPortPriority, in order to achieve manually configured aggregation.
.1.2.840.10006.300.43.1.2.1.1.9,IEEE8023-LAG-MIB::dot3adAggPortPartnerOperSystemID,OCTET,read-only,,current,,A 6-octet read-only MACAddress value representing the current value of the Aggregation Port's protocol Partner's System ID. A value of zero indicates that there is no known protocol Partner. The value of this attribute may contain the manually configured value carried in aAggPortPartnerAdminSystemID if there is no protocol Partner.
.1.2.840.10006.300.43.1.2.1.1.10,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminKey,Integer32,read-write,,current,,The current administrative value of the Key for the protocol Partner. This is a 16-bit read-write value. The assigned value is used, along with the value of aAggPortPartnerAdminSystemPriority, aAggPortPartnerAdminSystemID, aAggPortPartnerAdminPort, and aAggPortPartnerAdminPortPriority, in order to achieve manually configured aggregation.
.1.2.840.10006.300.43.1.2.1.1.11,IEEE8023-LAG-MIB::dot3adAggPortPartnerOperKey,Integer32,read-only,,current,,The current operational value of the Key for the protocol Partner. The value of this attribute may contain the manually configured value carried in aAggPortPartnerAdminKey if there is no protocol Partner. This is a 16-bit read-only value.
.1.2.840.10006.300.43.1.2.1.1.12,IEEE8023-LAG-MIB::dot3adAggPortSelectedAggID,Integer32,read-only,,current,,The identifier value of the Aggregator that this Aggregation Port has currently selected. Zero indicates that the Aggregation Port has not selected an Aggregator, either because it is in the process of detaching from an Aggregator or because there is no suitable Aggregator available for it to select. This value is read-only.
.1.2.840.10006.300.43.1.2.1.1.13,IEEE8023-LAG-MIB::dot3adAggPortAttachedAggID,Integer32,read-only,,current,,The identifier value of the Aggregator that this Aggregation Port is currently attached to. Zero indicates that the Aggregation Port is not currently attached to an Aggregator. This value is read-only.
.1.2.840.10006.300.43.1.2.1.1.14,IEEE8023-LAG-MIB::dot3adAggPortActorPort,Integer32,read-only,,current,,The port number locally assigned to the Aggregation Port. The port number is communicated in LACPDUs as the Actor_Port. This value is read-only.
.1.2.840.10006.300.43.1.2.1.1.15,IEEE8023-LAG-MIB::dot3adAggPortActorPortPriority,Integer32,read-write,,current,,The priority value assigned to this Aggregation Port. This 16-bit value is read-write. NOTE-In the case of DRNI (Clause 9), the two least significant bits of the priority for each Aggregation Port in a Distributed Relay's Aggregator Port will be ignored because these bits are used to encode the Portal System Number [item e) in 9.3.3].
.1.2.840.10006.300.43.1.2.1.1.16,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminPort,Integer32,read-write,,current,,The current administrative value of the port number for the protocol Partner. This is a 16-bit read-write value. The assigned value is used, along with the value of aAggPortPartnerAdminSystemPriority, aAggPortPartnerAdminSystemID, aAggPortPartnerAdminKey, and aAggPortPartnerAdminPortPriority, in order to achieve manually configured aggregation.
.1.2.840.10006.300.43.1.2.1.1.17,IEEE8023-LAG-MIB::dot3adAggPortPartnerOperPort,Integer32,read-only,,current,,The operational port number assigned to this Aggregation Port by the Aggregation Port's protocol Partner. The value of this attribute may contain the manually configured value carried in aAggPortPartnerAdminPort if there is no protocol Partner. This 16-bit value is read-only.
.1.2.840.10006.300.43.1.2.1.1.18,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminPortPriority,Integer32,read-write,,current,,The current administrative value of the port priority for the protocol Partner. This is a 16-bit read-write value. The assigned value is used, along with the value of aAggPortPartnerAdminSystemPriority, aAggPortPartnerAdminSystemID, aAggPortPartnerAdminKey, and aAggPortPartnerAdminPort, in order to achieve manually configured aggregation.
.1.2.840.10006.300.43.1.2.1.1.19,IEEE8023-LAG-MIB::dot3adAggPortPartnerOperPortPriority,Integer32,read-only,,current,,The priority value assigned to this Aggregation Port by the Partner. The value of this attribute may contain the manually configured value carried in aAggPortPartnerAdminPortPriority if there is no protocol Partner. This 16-bit value is read-only.
.1.2.840.10006.300.43.1.2.1.1.20,IEEE8023-LAG-MIB::dot3adAggPortActorAdminState,BITS,read-write,,current,lacpActivity(0):lacpTimeout(1):aggregation(2):synchronization(3):collecting(4):distributing(5):defaulted(6):expired(7),A string of 8 bits, corresponding to the administrative values of Actor_State (5.4.2) as transmitted by the Actor in LACPDUs. The first bit corresponds to bit 0 of Actor_State (LACP_Activity), the second bit corresponds to bit 1 (LACP_Timeout), the third bit corresponds to bit 2 (Aggregation), the fourth bit corresponds to bit 3 (Synchronization), the fifth bit corresponds to bit 4 (Collecting), the sixth bit corresponds to bit 5 (Distributing), the seventh bit corresponds to bit 6 (Defaulted), and the eighth bit corresponds to bit 7 (Expired). These values allow administrative control over the values of LACP_Activity, LACP_Timeout and Aggregation. This attribute value is read-write.
.1.2.840.10006.300.43.1.2.1.1.21,IEEE8023-LAG-MIB::dot3adAggPortActorOperState,BITS,read-only,,current,lacpActivity(0):lacpTimeout(1):aggregation(2):synchronization(3):collecting(4):distributing(5):defaulted(6):expired(7),A string of 8 bits, corresponding to the current operational values of Actor_State as transmitted by the Actor in LACPDUs. The bit allocations are as defined in 7.3.2.1.20. This attribute value is read-only.
.1.2.840.10006.300.43.1.2.1.1.22,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminState,BITS,read-write,,current,lacpActivity(0):lacpTimeout(1):aggregation(2):synchronization(3):collecting(4):distributing(5):defaulted(6):expired(7),A string of 8 bits, corresponding to the current administrative value of Actor_State for the protocol Partner. The bit allocations are as defined in 7.3.2.1.20. This attribute value is read-write. The assigned value is used in order to achieve manually configured aggregation.
.1.2.840.10006.300.43.1.2.1.1.23,IEEE8023-LAG-MIB::dot3adAggPortPartnerOperState,BITS,read-only,,current,lacpActivity(0):lacpTimeout(1):aggregation(2):synchronization(3):collecting(4):distributing(5):defaulted(6):expired(7),A string of 8 bits, corresponding to the current values of Actor_State in the most recently received LACPDU transmitted by the protocol Partner. The bit allocations are as defined in 7.3.2.1.20. In the absence of an active protocol Partner, this value may reflect the manually configured value aAggPortPartnerAdminState. This attribute value is read-only.
.1.2.840.10006.300.43.1.2.1.1.24,IEEE8023-LAG-MIB::dot3adAggPortAggregateOrIndividual,INTEGER,read-only,,current,true(1):false(2),A read-only Boolean value indicating whether the Aggregation Port is able to Aggregate ('TRUE') or is only able to operate as an Individual link ('FALSE').
.1.2.840.10006.300.43.1.2.2,IEEE8023-LAG-MIB::dot3adAggPortStatsTable,,not-accessible,,current,,A table that contains Link Aggregation information about every port that is associated with this device. A row appears in this table for each physical port.
.1.2.840.10006.300.43.1.2.2.1,IEEE8023-LAG-MIB::dot3adAggPortStatsEntry,,not-accessible,dot3adAggPortIndex,current,,A list of Link Aggregation Control Protocol statistics for each port on this device.
.1.2.840.10006.300.43.1.2.2.1.1,IEEE8023-LAG-MIB::dot3adAggPortStatsLACPDUsRx,Counter32,read-only,,current,,The number of valid LACPDUs received on this Aggregation Port. This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.2,IEEE8023-LAG-MIB::dot3adAggPortStatsMarkerPDUsRx,Counter32,read-only,,current,,The number of valid Marker PDUs received on this Aggregation Port. This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.3,IEEE8023-LAG-MIB::dot3adAggPortStatsMarkerResponsePDUsRx,Counter32,read-only,,current,,The number of valid Marker Response PDUs received on this Aggregation Port. This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.4,IEEE8023-LAG-MIB::dot3adAggPortStatsUnknownRx,Counter32,read-only,,current,,The number of frames received that either: - carry the Slow Protocols Ethernet Type value (IEEE Std 802.3-2008, Annex 57A.4), but contain an unknown PDU, or: - are addressed to the Slow Protocols group MAC Address (IEEE Std 802.3-2008, Annex 57A.3), but do not carry the Slow Protocols Ethernet Type. This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.5,IEEE8023-LAG-MIB::dot3adAggPortStatsIllegalRx,Counter32,read-only,,current,,The number of frames received that carry the Slow Protocols Ethernet Type value (IEEE Std 802.3-2008, Annex 57A.4), but contain a badly formed PDU or an illegal value of Protocol Subtype (IEEE Std 802.3-2008, Annex 57A.3). This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.6,IEEE8023-LAG-MIB::dot3adAggPortStatsLACPDUsTx,Counter32,read-only,,current,,The number of LACPDUs transmitted on this Aggregation Port. This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.7,IEEE8023-LAG-MIB::dot3adAggPortStatsMarkerPDUsTx,Counter32,read-only,,current,,The number of Marker PDUs transmitted on this Aggregation Port. This value is read-only.
.1.2.840.10006.300.43.1.2.2.1.8,IEEE8023-LAG-MIB::dot3adAggPortStatsMarkerResponsePDUsTx,Counter32,read-only,,current,,The number of Marker Response PDUs transmitted on this Aggregation Port. This value is read-only.
.1.2.840.10006.300.43.1.2.3,IEEE8023-LAG-MIB::dot3adAggPortDebugTable,,not-accessible,,current,,A table that contains Link Aggregation debug information about every port that is associated with this device. A row appears in this table for each physical port.
.1.2.840.10006.300.43.1.2.3.1,IEEE8023-LAG-MIB::dot3adAggPortDebugEntry,,not-accessible,dot3adAggPortIndex,current,,A list of the debug parameters for a port.
.1.2.840.10006.300.43.1.2.3.1.1,IEEE8023-LAG-MIB::dot3adAggPortDebugRxState,INTEGER,read-only,,current,currentRx(1):expired(2):defaulted(3):initialize(4):lacpDisabled(5):portDisabled(6),This attribute holds the value 'currentRx' if the Receive state machine for the Aggregation Port is in the  CURRENT state, 'expired' if the Receive state machine is in the EXPIRED state, 'defaulted' if the Receive state machine is in the DEFAULTED state, 'initialize' if the Receive state machine is in the INITIALIZE state, 'lacpDisabled' if the Receive state machine is in the LACP_DISABLED state, or 'portDisabled' if the Receive state machine is in the PORT_DISABLED state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.2,IEEE8023-LAG-MIB::dot3adAggPortDebugLastRxTime,TimeTicks,read-only,,current,,The time at which the last LACPDU was received by this Aggregation Port, in terms of centiseconds since the system was last reset. The ifLastChange object in the Interfaces MIB defined in IETF RFC 2863 is a suitable object for supplying a value for aAggPortDebugLastRxTime. This value is read-only. NOTE - aAggPortDebugLastRxTime was defined in terms of the aTimeSinceSystemReset variable of IEEE Std 802.3-2008, Annex F, F.2.1, in earlier versions of this standard. aTimeSinceSystemReset and ifLastChange have the same meaning.
.1.2.840.10006.300.43.1.2.3.1.3,IEEE8023-LAG-MIB::dot3adAggPortDebugMuxState,INTEGER,read-only,,current,detached(1):waiting(2):attached(3):collecting(4):distributing(5):collectingDistributing(6),This attribute holds the value 'detached' if the Mux state machine (5.4.14) for the Aggregation Port is in the DETACHED state, 'waiting' if the Mux state machine is in the WAITING state, 'attached' if the Mux state machine for the Aggregation Port is in the ATTACHED state, 'collecting' if the Mux state machine for the Aggregation Port is in the COLLECTING state, 'distributing' if the Mux state machine for the Aggregation Port is in the DISTRIBUTING state, and 'collectingDistributing' if the Mux state machine for the Aggregation Port is in the COLLECTING_DISTRIBUTING state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.4,IEEE8023-LAG-MIB::dot3adAggPortDebugMuxReason,OCTET,read-only,,current,,A human-readable text string indicating the reason for the most recent change of Mux machine state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.5,IEEE8023-LAG-MIB::dot3adAggPortDebugActorChurnState,INTEGER,read-only,,current,noChurn(1):churn(2):churnMonitor(3),The state of the Actor Churn Detection machine (6.4.17) for the Aggregation Port. A value of 'noChurn' indicates that the state machine is in either the NO_ACTOR_CHURN or the ACTOR_CHURN_MONITOR state, and 'churn' indicates that the state machine is in the ACTOR_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.6,IEEE8023-LAG-MIB::dot3adAggPortDebugPartnerChurnState,INTEGER,read-only,,current,noChurn(1):churn(2):churnMonitor(3),The state of the Partner Churn Detection machine (6.4.17) for the Aggregation Port. A value of 'noChurn' indicates that the state machine is in either the NO_PARTNER_CHURN or the PARTNER_CHURN_MONITOR state, and 'churn' indicates that the state machine is in the PARTNER_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.7,IEEE8023-LAG-MIB::dot3adAggPortDebugActorChurnCount,Counter32,read-only,,current,,Count of the number of times the Actor Churn state machine has entered the ACTOR_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.8,IEEE8023-LAG-MIB::dot3adAggPortDebugPartnerChurnCount,Counter32,read-only,,current,,Count of the number of times the Partner Churn state machine has entered the PARTNER_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.9,IEEE8023-LAG-MIB::dot3adAggPortDebugActorSyncTransitionCount,Counter32,read-only,,current,,Count of the number of times the Actor's Mux state machine (6.4.15) has entered the IN_SYNC state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.10,IEEE8023-LAG-MIB::dot3adAggPortDebugPartnerSyncTransitionCount,Counter32,read-only,,current,,Count of the number of times the Partner's Mux state machine (6.4.15) has entered the IN_SYNC state. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.11,IEEE8023-LAG-MIB::dot3adAggPortDebugActorChangeCount,Counter32,read-only,,current,,Count of the number of times the Actor's perception of the LAG ID for this Aggregation Port has changed. This value is read-only.
.1.2.840.10006.300.43.1.2.3.1.12,IEEE8023-LAG-MIB::dot3adAggPortDebugPartnerChangeCount,Counter32,read-only,,current,,Count of the number of times the Partner's perception of the LAG ID (see 6.3.6.1) for this Aggregation Port has changed. This value is read-only.
.1.2.840.10006.300.43.1.2.4,IEEE8023-LAG-MIB::dot3adAggPortXTable,,not-accessible,,current,,A table that extends dot3adAggPortTable.
.1.2.840.10006.300.43.1.2.4.1,IEEE8023-LAG-MIB::dot3adAggPortXEntry,,not-accessible,,current,,A list of extension parameters for Aggregation Port.
.1.2.840.10006.300.43.1.2.4.1.1,IEEE8023-LAG-MIB::dot3adAggPortProtocolDA,OCTET,read-write,,current,,A 6-octet read-write MACAddress value specifying the DA to be used when sending Link Aggregation Control and Marker PDUs on this Aggregation Port, corresponding to the value of Protocol_DA in 6.2.8.1.2, 6.2.10.1.3 and 6.5.4.2.1. The default value shall be the IEEE 802.3 Slow_Protocols_Multicast address.
.1.2.840.10006.300.43.1.2.5,IEEE8023-LAG-MIB::dot3adAggPortSecondXTable,,not-accessible,,current,,A table that extends dot3adAggPortTable.
.1.2.840.10006.300.43.1.2.5.1,IEEE8023-LAG-MIB::dot3adAggPortSecondXEntry,,not-accessible,,current,,A list of extension parameters for Aggregation Port.
.1.2.840.10006.300.43.1.2.5.1.1,IEEE8023-LAG-MIB::dot3adAggPortOperConversationPasses,OCTET,read-only,,current,,A read-only current operational vector of Boolean values, with one value for each possible Port Conversation ID. A 1 indicates that the Port Conversation ID is distributed through this Aggregation Port, and a 0 indicates that it cannot. aAggPortOperConversationPasses is referencing the current value of Port_Oper_Conversation_Mask (6.6.2.2).
.1.2.840.10006.300.43.1.2.5.1.2,IEEE8023-LAG-MIB::dot3adAggPortOperConversationCollected,OCTET,read-only,,current,,A read-only current operational vector of Boolean values, with one value for each possible Port Conversation ID. A 1 indicates that the Port Conversation ID is collected through this Aggregation Port, and a 0 indicates that it cannot. aAggPortOperConversationPasses is referencing the current value of Collection_Conversation_Mask (6.6.1.1.2).
.1.2.840.10006.300.43.1.2.5.1.3,IEEE8023-LAG-MIB::dot3adAggPortLinkNumberId,Integer32,read-write,,current,,The Link Number ID value configured for this Aggregation Port by the System's administrator. When the Link Number ID value matches one of the non zero values in the selection prioritized lists in aAggConversationAdminLink[] (7.3.1.1.35), then this Aggregation Port must be configured to have an aAggPortActorAdminKey value that matches the aAggActorAdminKey of the Aggregator used by the LAG of the links specified in aAggConversationAdminLink[]. Its default value is set to the match of the aAggActorAdminKey to aAggPortActorAdminKey values excludes the first two bits identifying the individual Portal System in the Portal. If the network administrator fails to configure the proper values for the aAggPortActorAdminKey variables in all of the Aggregators Ports attached to a Portal, the DRCP (9.4) and the variable Port_Oper_Conversation_Mask (6.6.2.2) prevent looping and/or duplicate delivery, if necessary, by discarding frames belonging to misconfigured Conversations.
.1.2.840.10006.300.43.1.2.5.1.4,IEEE8023-LAG-MIB::dot3adAggPortPartnerAdminLinkNumberId,Integer32,read-write,,deprecated,,The value for the Link Number ID of the Partner System for this Aggregation Port, assigned by administrator or System policy for use when the Partner's information is unknown. Its default value is set to 0.
.1.2.840.10006.300.43.1.2.5.1.5,IEEE8023-LAG-MIB::dot3adAggPortWTRTime,Integer32,read-write,,current,,The wait-to-restore (WTR) period accompanying selection
.1.2.840.10006.300.43.1.2.5.1.6,IEEE8023-LAG-MIB::dot3adAggPortEnableLongPDUXmit,INTEGER,read-write,,current,true(1):false(2),A read-write Boolean value indicating whether the Aggregation Port
.1.2.840.10006.300.43.1.2.6,IEEE8023-LAG-MIB::dot3adAggPortDebugXTable,,not-accessible,,current,,A table that extends dot3adAggPortDebugTable.
.1.2.840.10006.300.43.1.2.6.1,IEEE8023-LAG-MIB::dot3adAggPortDebugXEntry,,not-accessible,,current,,A list of extension parameters for the LACP Port Debug table.
.1.2.840.10006.300.43.1.2.6.1.1,IEEE8023-LAG-MIB::dot3adAggPortDebugActorCDSChurnState,INTEGER,read-only,,current,noChurn(1):churn(2):churnMonitor(3),This managed object is applicable only when Conversation-sensitive frame collection and distribution as specified in 6.6 is supported. The state of the Actor CDS Churn Detection machine (6.6.2.7) for the Aggregation Port. A value of 'noChurn' indicates that the state machine is in either the NO_ACTOR_CDS_CHURN or the ACTOR_CHURN_CDS_MONITOR state, and 'churn' indicates that the state machine is in the ACTOR_CDS_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.6.1.2,IEEE8023-LAG-MIB::dot3adAggPortDebugPartnerCDSChurnState,INTEGER,read-only,,current,noChurn(1):churn(2):churnMonitor(3),This managed object is applicable only when Conversation-sensitive frame collection and distribution as specified in 6.6 is supported. The state of the Partner CDS Churn Detection machine (6.6.2.7) for the Aggregation Port. A value of 'noChurn' indicates that the state machine is in either the NO_PARTNER_CDS_CHURN or the PARTNER_CDS_CHURN_MONITOR state, and 'churn' indicates that the state machine is in the PARTNER_CDSCHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.6.1.3,IEEE8023-LAG-MIB::dot3adAggPortDebugActorCDSChurnCount,Counter64,read-only,,current,,This managed object is applicable only when Conversation-sensitive frame collection and distribution as specified in 6.6 is supported. Count of the number of times the Actor CDS Churn state machine has entered the ACTOR_CDS_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.2.6.1.4,IEEE8023-LAG-MIB::dot3adAggPortDebugPartnerCDSChurnCount,Counter64,read-only,,current,,This managed object is applicable only when Conversation-sensitive frame collection and distribution as specified in 6.6 is supported. Count of the number of times the Partner CDS Churn state machine has entered the PARTNER_CDS_CHURN state. This value is read-only.
.1.2.840.10006.300.43.1.3,IEEE8023-LAG-MIB::dot3adTablesLastChanged,TimeTicks,read-only,,current,,This object indicates the time of the most recent change to the dot3adAggTable, dot3adAggPortTable, dot3adDrniTable and dot3adIPPAttributeTable.
.1.2.840.10006.300.43.1.4,IEEE8023-LAG-MIB::dot3adDrni,,,,,,
.1.2.840.10006.300.43.1.4.1,IEEE8023-LAG-MIB::dot3adDrniTable,,not-accessible,,current,,A table that contains information about every DRNI that is associated with this System.
.1.2.840.10006.300.43.1.4.1.1,IEEE8023-LAG-MIB::dot3adDrniEntry,,not-accessible,dot3adDrniIndex,current,,A list of the DRNI parameters. This is indexed by the DRNI Portal ID.
.1.2.840.10006.300.43.1.4.1.1.1,IEEE8023-LAG-MIB::dot3adDrniIndex,Integer32,not-accessible,,current,,The unique identifier allocated to this Distributed Relay by the local System. This attribute identifies a Distributed Relay instance among the subordinate managed objects of the containing object. This value is read-only. NOTE - The aDrniID is represented in the SMIv2 MIB as an ifIndex-see D.5.
.1.2.840.10006.300.43.1.4.1.1.2,IEEE8023-LAG-MIB::dot3adDrniDescription,OCTET,read-only,,current,,A human-readable text string containing information about the Distribute Relay. This string is read-only. The contents are vendor specific.
.1.2.840.10006.300.43.1.4.1.1.3,IEEE8023-LAG-MIB::dot3adDrniName,OCTET,read-write,,current,,A human-readable text string containing a locally significant name for the Distributed Relay. This string is read-write.
.1.2.840.10006.300.43.1.4.1.1.4,IEEE8023-LAG-MIB::dot3adDrniPortalAddr,OCTET,read-write,,current,,A read-write identifier of a particular Portal. aDrniPortalAddr has to be unique among at least all of the potential Portal Systems to which a given Portal System might be attached via an IPL Intra-Portal Link. Also used as the Actor's System ID (6.3.2) for the emulated system.
.1.2.840.10006.300.43.1.4.1.1.5,IEEE8023-LAG-MIB::dot3adDrniPortalPriority,Integer32,read-write,,current,,A 2-octet read-write value indicating the priority value associated with the Portal's System ID. Also used as the Actor's System Priority (6.3.2) for the emulated system.
.1.2.840.10006.300.43.1.4.1.1.6,IEEE8023-LAG-MIB::dot3adDrniThreePortalSystem,INTEGER,read-write,,current,true(1):false(2),A read-write Boolean value indicating whether this Portal System is part of a Portal consisting of three Portal Systems or not. Value 1 stands for a Portal of three Portal Systems, value 0 stands for a Portal of two Portal Systems. The default value is 0.
.1.2.840.10006.300.43.1.4.1.1.7,IEEE8023-LAG-MIB::dot3adDrniPortalSystemNumber,Integer32,read-write,,current,,A read-write identifier of this particular Portal System within a Portal. It is the responsibility of the network administrator to ensure that these numbers are unique among the Portal Systems with the same aDrniPortalAddr (7.4.1.1.4).
.1.2.840.10006.300.43.1.4.1.1.8,IEEE8023-LAG-MIB::dot3adDrniIntraPortalLinkList,OCTET,read-write,,current,,Read-write list of the Interface Identifiers of the Ports to the Intra-Portal Links assigned to this Distributed Relay. Each Interface Identifier, a Port ID (6.3.4), has the two least significant bits of its Port Priority (7.3.2.1.15) configured to match the Portal System Number of the attached Portal System. The number of IPLs in the list depends on the Portal topology. For a Portal of three Portal Systems two or three IPLs can be used, for a Portal of two Portal Systems a single IPL is required and for a single Portal System no IPL is required.
.1.2.840.10006.300.43.1.4.1.1.9,IEEE8023-LAG-MIB::dot3adDrniAggregator,Integer32,read-write,,current,,An INTEGER that matches the syntax of an Interface Identifier. Read-write Interface Identifier of the Aggregator Port assigned to this Distributed Relay.
.1.2.840.10006.300.43.1.4.1.1.10,IEEE8023-LAG-MIB::dot3adDrniNeighborAdminConvGatewayListDigest,OCTET,read-write,,current,,The value for the digest of the prioritized Gateway Conversation ID-to-Gateway assignments of the Neighbor Portal System, assigned by administrator or System policy for use when the Neighbor Portal System's information is unknown. Its default value is set to NULL.
.1.2.840.10006.300.43.1.4.1.1.11,IEEE8023-LAG-MIB::dot3adDrniNeighborAdminConvPortListDigest,OCTET,read-write,,current,,The value for the digest of the prioritized Port Conversation ID-to-Aggregation Port assignments of the Neighbor Portal System, assigned by administrator or System policy for use when the Neighbor Portal System's information is unknown. Its default value is set to NULL.
.1.2.840.10006.300.43.1.4.1.1.12,IEEE8023-LAG-MIB::dot3adDrniGatewayAlgorithm,OCTET,read-write,,current,,This object identifies the algorithm used by the DR Function to assign frames to a Gateway Conversation ID. Table 9-7 provides the IEEE 802.1 OUI (00-80-C2) Gateway Algorithm encodings. A SEQUENCE OF OCTETS consisting of an OUI or CID and one following octet.
.1.2.840.10006.300.43.1.4.1.1.13,IEEE8023-LAG-MIB::dot3adDrniNeighborAdminGatewayAlgorithm,OCTET,read-write,,current,,This object identifies the value for the Gateway algorithm of the Neighbor Portal System, assigned by administrator or System policy for use when the Neighbor Portal System's information is unknown. Table 9-7 provides the IEEE 802.1 OUI (00-80-C2) Gateway Algorithm encodings. Its default value is set to NULL. A SEQUENCE OF OCTETS consisting of a 3-octet OUI or CID and one following octet.
.1.2.840.10006.300.43.1.4.1.1.14,IEEE8023-LAG-MIB::dot3adDrniNeighborAdminPortAlgorithm,OCTET,read-write,,current,,This object identifies the value for the Port Algorithm of the Neighbor Portal System, assigned by administrator or System policy for use when the Neighbor Portal System's information is unknown. Table 6-4 provides the IEEE 802.1 OUI (00-80-C2) Port Algorithm encodings. Its default value is set to NULL. A SEQUENCE OF OCTETS consisting of a 3-octet OUI or CID and one following octet.
.1.2.840.10006.300.43.1.4.1.1.15,IEEE8023-LAG-MIB::dot3adDrniNeighborAdminDRCPState,BITS,read-write,,current,homeGateway(0):neighborGateway(1):otherGateway(2):ippActivity(3):timeout(4):gatewaySync(5):portSync(6):expired(7),A string of 8 bits, corresponding to the administrative values of DRCP_State [item s) in 9.4.3.2] as transmitted by this Portal System in DRCPDUs. The first bit corresponds to bit 0 of DRCP_State (HomeGateway), the second bit corresponds to bit 1 (NeighborGateway), the third bit corresponds to bit 2 (OtherGateway), the fourth bit corresponds to bit 3 (IppActivity), the fifth bit corresponds to bit 4 (Timeout), the sixth bit corresponds to bit 5 (GatewaySync), the seventh bit corresponds to bit 6 (PortSync), and the eighth bit  corresponds to bit 7 (Expired). These values allow administrative control over the values of HomeGateway, NeighborGateway, OtherGateway, IppActivity, and Timeout. Their values are by default set to FALSE. This attribute value is read-write.
.1.2.840.10006.300.43.1.4.1.1.16,IEEE8023-LAG-MIB::dot3adDrniEncapsulationMethod,OCTET,read-write,,current,,This managed object is applicable only when Network / IPL sharing by time (9.3.2.1) or Network / IPL sharing by tag (9.3.2.2) or Network / IPL sharing by encapsulation (9.3.2.3) is supported. The object identifies the value representing the encapsulation method that is used to transport IPL frames to the Neighbor Portal System when the IPL and network link are sharing the same physical link. It consists of the 3-octet OUI or CID identifying the organization that is responsible for this encapsulation and one following octet used to identify the encapsulation method defined by that organization. Table 9-11 provides the IEEE 802.1 OUI (00-80-C2) encapsulation method encodings. A Default value of 0x00-80-C2-00 indicates that the IPL is using a separate physical or Aggregation link. A value of 1 indicates that Network / IPL sharing by time (9.3.2.1) is used. A value of 2 indicates that the encapsulation method used is the same as the one used by network frames and that Network / IPL sharing by tag (9.3.2.2) is used.
.1.2.840.10006.300.43.1.4.1.1.17,IEEE8023-LAG-MIB::dot3adDrniDRPortConversationPasses,OCTET,read-only,,current,,A read-only current operational vector of Boolean values, with one value for each possible Port Conversation ID. A 1 indicates that the Port Conversation ID is allowed to be distributed through this DR Function's Aggregator, and a 0 indicates that it cannot. aDrniDRPortConversationPasses is referencing the current value of Drni_Portal_System_Port_Conversation (9.3.4.2).
.1.2.840.10006.300.43.1.4.1.1.18,IEEE8023-LAG-MIB::dot3adDrniDRGatewayConversationPasses,OCTET,read-only,,current,,A read-only current operational vector of Boolean values, with one value for each possible Gateway Conversation ID. A 1 indicates that the Gateway Conversation ID is allowed to pass through this DR Function's Gateway, and a 0 indicates that it cannot. aDrniDRGatewayConversationPasses is referencing the current value of Drni_Portal_System_Gateway_Conversation (9.3.4.2).
.1.2.840.10006.300.43.1.4.1.1.19,IEEE8023-LAG-MIB::dot3adDrniPSI,INTEGER,read-only,,current,true(1):false(2),A read-only Boolean value providing the value of PSI, which ('FALSE').
.1.2.840.10006.300.43.1.4.1.1.20,IEEE8023-LAG-MIB::dot3adDrniPortConversationControl,INTEGER,read-write,,current,true(1):false(2),A read-write Boolean value that controls the operation of the algorithm and the Port algorithm use the same distributions methods. The default is 'FALSE', indicating that the Home Gateway Vector is controlled by the network control protocol.
.1.2.840.10006.300.43.1.4.1.1.21,IEEE8023-LAG-MIB::dot3adDrniIntraPortalPortProtocolDA,OCTET,read-write,,current,,A 6-octet read-write MAC Address value specifying the destination address to be used when sending DRCPDUs, corresponding to the value of DRCP_Protocol_DA in 9.4.4.1.3. Its values is one of the addresses selected from Table 9-4 and its default shall be the IEEE 802.1 Nearest non-TPMR Bridge group address (01-80-C2-00-00-03).
.1.2.840.10006.300.43.1.4.2,IEEE8023-LAG-MIB::dot3adDrniConvAdminGatewayTable,,not-accessible,,current,,There are 4096 aDrniConvAdminGateway[] variables, aDrniConvAdminGateway[0] through aDrniConvAdminGateway[4095], indexed by Gateway Conversation ID. Each contains administrative values of the Gateway selection priority list for the Distributed Relay for the referenced Gateway Conversation ID. This selection priority list, a sequence of integers for each Gateway Conversation ID, is a list of Portal System Numbers in the order of preference, highest to lowest, for the corresponding preferred Portal System's Gateway to carry that Conversation. NOTE - To the extent that the network administrator fails to configure the same values for the aDrniConvAdminGateway[] variables in all of the DR Functions of a Portal, frames can be misdirected. The DRCP (9.4) detects such misconfiguration.
.1.2.840.10006.300.43.1.4.2.1,IEEE8023-LAG-MIB::dot3adDrniConvAdminGatewayEntry,,not-accessible,dot3adDrniGatewayConversationID:dot3adDrniIndex,current,,A Gateway selection priority list for the Distributed Relay for the referenced Gateway Conversation ID. This selection priority list, a sequence of integers for each Gateway Conversation ID, is a list of Portal System Numbers in the order of preference, highest to lowest, for the corresponding preferred Portal System's Gateway to carry that Conversation.
.1.2.840.10006.300.43.1.4.2.1.1,IEEE8023-LAG-MIB::dot3adDrniGatewayConversationID,Integer32,not-accessible,,current,,An identifer for a Gateway Conversation.
.1.2.840.10006.300.43.1.4.2.1.2,IEEE8023-LAG-MIB::dot3adDrniConvAdminGatewayList,OCTET,read-write,,current,,Priority list of Portal System Numbers in order of preference from highest to lowest.
.1.2.840.10006.300.43.1.4.3,IEEE8023-LAG-MIB::dot3adDrniIPLEncapMapTable,,not-accessible,,current,,This managed object is applicable only when Network / IPL sharing by tag (9.3.2.2) or Network / IPL sharing by encapsulation (9.3.2.3) is supported. Each entry represents the value of the identifier used for an IPL frame associated with that Gateway Conversation ID for the encapsulation method specified in 7.4.1.1.17.
.1.2.840.10006.300.43.1.4.3.1,IEEE8023-LAG-MIB::dot3adDrniIPLEncapMapEntry,,not-accessible,dot3adDrniGatewayConversationID:dot3adDrniIndex,current,,An entry represents the value of the identifier used for an IPL frame associated with that Gateway Conversation ID for the encapsulation method specified in 7.4.1.1.17.
.1.2.840.10006.300.43.1.4.3.1.2,IEEE8023-LAG-MIB::dot3adDrniIPLFrameIdValue,Integer32,read-write,,current,,The value of the identifier used for an IPL frame associated with that Gateway Conversation ID for the encapsulation method.
.1.2.840.10006.300.43.1.4.4,IEEE8023-LAG-MIB::dot3adDrniNetEncapMapTable,,not-accessible,,current,,This managed object is applicable only when Network / IPL sharing by tag (9.3.2.2) is supported. Each entry represents the translated value of the identifier used for a network frame associated with that Gateway Conversation ID when the method specified in 7.4.1.1.17 is the Network / IPL sharing by tag method specified in 9.3.2.2 and the network frames need to share the tag space used by IPL frames.
.1.2.840.10006.300.43.1.4.4.1,IEEE8023-LAG-MIB::dot3adDrniNetEncapMapEntry,,not-accessible,dot3adDrniGatewayConversationID:dot3adDrniIndex,current,,An entry represents the translated value of the identifier used for a network frame associated with that Gateway Conversation ID when the method specified in 7.4.1.1.12 is the Network / IPL sharing by tag method specified in 9.3.2.2 and the network frames need to share the tag space used by IPL frames.
.1.2.840.10006.300.43.1.4.4.1.1,IEEE8023-LAG-MIB::dot3adDrniNetFrameIdValue,Integer32,read-write,,current,,The translated value of the identifier used for a network frame associated that Gateway Conversation ID.
.1.2.840.10006.300.43.1.5,IEEE8023-LAG-MIB::dot3adIPP,,,,,,
.1.2.840.10006.300.43.1.5.1,IEEE8023-LAG-MIB::dot3adIPPAttributeTable,,not-accessible,,current,,A table that contains information about every IPP that is associated with this System.
.1.2.840.10006.300.43.1.5.1.1,IEEE8023-LAG-MIB::dot3adIPPAttributeEntry,,not-accessible,dot3adIPPIndex,current,,An entry containing Attributes for an IPP.
.1.2.840.10006.300.43.1.5.1.1.1,IEEE8023-LAG-MIB::dot3adIPPIndex,Integer32,not-accessible,,current,,The unique identifier allocated to this IPP by the local Portal System. This attribute identifies an IPP instance among the subordinate managed objects of the containing object. This value is read-only. NOTE-The aIPPID is represented in the SMIv2 MIB as an ifIndex-see D.5.
.1.2.840.10006.300.43.1.5.1.1.2,IEEE8023-LAG-MIB::dot3adIPPPortConversationPasses,OCTET,read-only,,current,,A read-only current operational vector of Boolean values, with one value for each possible Port Conversation ID. A 1 indicates that the Port Conversation ID is allowed to be transmitted through this IPP Intra-Portal Port, and a 0 indicates that it cannot. aDrniIPPPortConversationPasses is referencing the current value of Ipp_Port_Conversation_Passes (9.3.4.3).
.1.2.840.10006.300.43.1.5.1.1.3,IEEE8023-LAG-MIB::Ipp_Gateway_Conversation_Direction,OCTET,read-only,,current,,A read-only current operational vector of Boolean values, with one value for each possible Gateway Conversation ID. A 1 indicates that the Gateway Conversation ID is assigned to Gateways reachable through this IPP Intra-Portal Port, and a 0 indicates that the Gateway for the indexed Gateway Conversation ID is not reachable through this IPP Intra-Portal Port. aIPPGatewayConversationDirection is referencing the current value of
.1.2.840.10006.300.43.1.5.1.1.4,IEEE8023-LAG-MIB::dot3adIPPAdminState,INTEGER,read-write,,current,up(1):down(2),This read-write value defines the administrative state of the IPP. A value of 'up' indicates that the operational state of the IPP (aIPPOperState) is permitted to be either up or down. A value of 'down' forces the operational state of the IPP to be down. A GET operation returns the current administrative state. A SET operation changes the administrative state to a new value.
.1.2.840.10006.300.43.1.5.1.1.5,IEEE8023-LAG-MIB::dot3adIPPOperState,INTEGER,read-only,,current,up(1):down(2),This read-only value defines the operational state of the IPP. The operational state is 'up' if the IPL is operational, and if the value of aIPPAdminState for the IPP is also 'up'. If the IPL is not operational, or if the administrative state of the IPP (aIPPAdminState) is 'down', then the operational state is 'down.' An operational state of 'up' indicates that the IPP is available for use by the DR Function; a value of 'down' indicates that the IPP is not available for use by the DR Function.
.1.2.840.10006.300.43.1.5.1.1.6,IEEE8023-LAG-MIB::dot3adIPPTimeOfLastOperChange,Integer32,read-only,,current,,The time at which the interface entered its current operational state, in terms of centiseconds since the system was last reset. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a value of zero. The ifLastChange object in the Interfaces MIB defined in IETF RFC 2863 is a suitable object for supplying a value for aIPPTimeOfLastOperChange. This value is read-only.
.1.2.840.10006.300.43.1.5.2,IEEE8023-LAG-MIB::dot3adIPPStatsTable,,not-accessible,,current,,A table that contains information for IPP statistics. A row appears in this table for each IPP in the system.
.1.2.840.10006.300.43.1.5.2.1,IEEE8023-LAG-MIB::dot3adIPPStatsEntry,,not-accessible,dot3adIPPIndex,current,,An entry containing Statistics for an IPP.
.1.2.840.10006.300.43.1.5.2.1.1,IEEE8023-LAG-MIB::dot3adIPPStatsDRCPDUsRx,Counter64,read-only,,current,,The number of valid DRCPDUs received on this IPP. This value is read-only.
.1.2.840.10006.300.43.1.5.2.1.2,IEEE8023-LAG-MIB::dot3adIPPStatsIllegalRx,Counter64,read-only,,current,,The number of frames received that carry the DRCP Ethernet Type value (9.4.2.4), but contain a badly formed PDU. This value is read-only.
.1.2.840.10006.300.43.1.5.2.1.3,IEEE8023-LAG-MIB::dot3adIPPStatsDRCPDUsTx,Counter64,read-only,,current,,The number of DRCPDUs transmitted on this IPP. This value is read-only.
.1.2.840.10006.300.43.1.5.3,IEEE8023-LAG-MIB::dot3adIPPDebugTable,,not-accessible,,current,,A table that contains IPP debug information. A row appears in this table for each IPP in the system.
.1.2.840.10006.300.43.1.5.3.1,IEEE8023-LAG-MIB::dot3adIPPDebugEntry,,not-accessible,dot3adIPPIndex,current,,An entry containing Debug Information for an IPP.
.1.2.840.10006.300.43.1.5.3.1.1,IEEE8023-LAG-MIB::dot3adIPPDebugDRCPRxState,INTEGER,read-only,,current,expired(2):defaulted(3):initialize(4):reportToManagement(5),This attribute holds the value 'current' if the DRCPDU Receive state machine for the IPP is in the CURRENT state, 'expired' if the DRCPDU Receive state machine is in the EXPIRED state, 'defaulted' if the DRCPDU Receive state machine is in the DEFAULTED state, 'initialize' if the DRCPDU Receive state machine is in the INITIALIZE state, or 'reportToManagement' if the Receive state machine is in the REPORT_TO_MANAGEMENT state. This value is read-only.
.1.2.840.10006.300.43.1.5.3.1.2,IEEE8023-LAG-MIB::dot3adIPPDebugLastRxTime,TimeTicks,read-only,,current,,The time at which the last DRCPDU was received by this IPP, in terms of centiseconds since the system was last reset. The ifLastChange object in the Interfaces MIB defined in IETF RFC 2863 is a suitable object for supplying a value for aDrniIPPDebugLastRxTime. This value is read-only.
.1.2.840.10006.300.43.1.5.3.1.3,IEEE8023-LAG-MIB::dot3adIPPDebugDifferPortalReason,OCTET,read-only,,current,,A human-readable text string indicating the most recent set of variables that are responsible for setting the variable Differ_Portal or Differ_Conf_Portal (9.4.8) on this IPP to TRUE. This value is read-only.
.1.2.840.10006.300.43.2,IEEE8023-LAG-MIB::dot3adAggConformance,,,,,,
.1.2.840.10006.300.43.2.1,IEEE8023-LAG-MIB::dot3adAggGroups,,,,,,
.1.2.840.10006.300.43.2.1.1,IEEE8023-LAG-MIB::dot3adAggGroup,,,,,,A collection of objects providing information about an aggregation.
.1.2.840.10006.300.43.2.1.2,IEEE8023-LAG-MIB::dot3adAggPortListGroup,,,,,,A collection of objects providing information about every port in an aggregation.
.1.2.840.10006.300.43.2.1.3,IEEE8023-LAG-MIB::dot3adAggPortGroup,,,,,,A collection of objects providing information about every port in an aggregation.
.1.2.840.10006.300.43.2.1.4,IEEE8023-LAG-MIB::dot3adAggPortStatsGroup,,,,,,A collection of objects providing information about every port in an aggregation.
.1.2.840.10006.300.43.2.1.5,IEEE8023-LAG-MIB::dot3adAggPortDebugGroup,,,,,,A collection of objects providing debug information about  every aggregated port.
.1.2.840.10006.300.43.2.1.6,IEEE8023-LAG-MIB::dot3adTablesLastChangedGroup,,,,,,A collection of objects providing information about the time of changes to the configuration of aggregations and their ports.
.1.2.840.10006.300.43.2.1.7,IEEE8023-LAG-MIB::dot3adAggPortProtocolDAGroup,,,,,,A collection of objects providing information about the protocol destination address in use for ports in an aggregation.
.1.2.840.10006.300.43.2.1.8,IEEE8023-LAG-MIB::dot3adAggNotificationGroup,,,,,,A collection of notifications providing information about  the aggregation.
.1.2.840.10006.300.43.2.1.9,IEEE8023-LAG-MIB::dot3adAggXGroup,,,,,,A collection of extension entries providing information on an aggregation.
.1.2.840.10006.300.43.2.1.10,IEEE8023-LAG-MIB::dot3adAggRecommendedGroup,,,,,,A collection of recommended objects providing information about an aggregation.
.1.2.840.10006.300.43.2.1.11,IEEE8023-LAG-MIB::dot3adAggOptionalGroup,,,,,,A collection of optional objects providing information about an aggregation.
.1.2.840.10006.300.43.2.1.12,IEEE8023-LAG-MIB::dot3adPerServiceFrameDistGroup,,,,,,A collection of objects providing information about Per-Service Frame Distribution.
.1.2.840.10006.300.43.2.1.13,IEEE8023-LAG-MIB::dot3adAggPortDebugXGroup,,,,,,A collection of objects extending aggregator port debug.
.1.2.840.10006.300.43.2.1.14,IEEE8023-LAG-MIB::dot3adDrniGroup,,,,,,A collection of objects providing information about DRNI.
.1.2.840.10006.300.43.2.1.15,IEEE8023-LAG-MIB::dot3adIPPGroup,,,,,,A collection of objects providing IPP information.
.1.2.840.10006.300.43.2.1.16,IEEE8023-LAG-MIB::dot3adIPPStatsGroup,,,,,,A collection of objects providing IPP statistics information.
.1.2.840.10006.300.43.2.1.17,IEEE8023-LAG-MIB::dot3adIPPDebugGroup,,,,,,A collection of objects providing IPP debug information.
.1.2.840.10006.300.43.2.1.18,IEEE8023-LAG-MIB::dot3adPerServiceFrameDistGroup2,,,,,,A collection of objects providing information about Per-Service Frame Distribution.
.1.2.840.10006.300.43.2.2,IEEE8023-LAG-MIB::dot3adAggCompliances,,,,,,
.1.2.840.10006.300.43.2.2.1,IEEE8023-LAG-MIB::dot3adAggCompliance,,,,,,The compliance statement for device support of Link Aggregation.
.1.2.840.10006.300.43.2.2.2,IEEE8023-LAG-MIB::dot3adAggCompliance2,,,,,,The compliance statement for device support of Link Aggregation.
.1.2.840.10036,IEEE802dot11-MIB::ieee802dot11,,,,,,The MIB module for IEEE 802.11 entities. iso(1).member-body(2).us(840).ieee802dot11(10036)
.1.2.840.10036.1,IEEE802dot11-MIB::dot11smt,,,,,,
.1.2.840.10036.1.1,IEEE802dot11-MIB::dot11StationConfigTable,,not-accessible,,current,,Station Configuration attributes. In tablular form to allow for multiple instances on an agent.
.1.2.840.10036.1.1.1,IEEE802dot11-MIB::dot11StationConfigEntry,,not-accessible,ifIndex,current,,An entry in the dot11StationConfigTable. It is possible for there to be multiple IEEE 802.11 interfaces on one agent, each with its unique MAC address. The relationship between an IEEE 802.11 interface and an interface in the context of the Internet-standard MIB is one-to-one. As such, the value of an ifIndex object instance can be directly used to identify corresponding instances of the objects defined herein.  ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.1.1.1,IEEE802dot11-MIB::dot11StationID,OCTET,read-write,,deprecated,,The purpose of dot11StationID is to allow a manager to  identify a station for its own purposes. This attribute provides for that eventuality while keeping the true MAC address independent. Its syntax is MAC address, and the default value is the station's assigned, unique  MAC address.
.1.2.840.10036.1.1.1.2,IEEE802dot11-MIB::dot11MediumOccupancyLimit,INTEGER,read-write,,current,,This attribute shall indicate the maximum amount of time, in TU, that a point coordinator (PC) may control the usage  of the wireless medium (WM) without relinquishing control  for long enough to allow at least one instance of DCF access  to the medium. The default value of this attribute shall  be 100, and the maximum value shall be 1000.
.1.2.840.10036.1.1.1.3,IEEE802dot11-MIB::dot11CFPollable,INTEGER,read-only,,current,true(1):false(2),When this attribute is true, it shall indicate that 
.1.2.840.10036.1.1.1.4,IEEE802dot11-MIB::dot11CFPPeriod,INTEGER,read-write,,current,,The attribute shall describe the number of DTIM intervals between the start of CFPs. It is modified by MLME-START.request primitive.
.1.2.840.10036.1.1.1.5,IEEE802dot11-MIB::dot11CFPMaxDuration,INTEGER,read-write,,current,,The attribute shall describe the maximum duration of 
.1.2.840.10036.1.1.1.6,IEEE802dot11-MIB::dot11AuthenticationResponseTimeOut,Unsigned32,read-write,,current,,This attribute shall specify the number of time units (TUs) that a responding STA should wait for the next frame in the authentication sequence.
.1.2.840.10036.1.1.1.7,IEEE802dot11-MIB::dot11PrivacyOptionImplemented,INTEGER,read-only,,current,true(1):false(2),This attribute, when true, shall indicate that the IEEE 802.11 WEP option is implemented. The default value of this attribute shall be false.
.1.2.840.10036.1.1.1.8,IEEE802dot11-MIB::dot11PowerManagementMode,INTEGER,read-write,,current,active(1):powersave(2),This attribute shall specify the power management
.1.2.840.10036.1.1.1.9,IEEE802dot11-MIB::dot11DesiredSSID,OCTET,read-write,,current,,This attribute reflects the Service Set ID (SSID)
.1.2.840.10036.1.1.1.10,IEEE802dot11-MIB::dot11DesiredBSSType,INTEGER,read-write,,current,infrastructure(1):independent(2):any(3),This attribute shall specify the type of BSS the
.1.2.840.10036.1.1.1.11,IEEE802dot11-MIB::dot11OperationalRateSet,OCTET,read-write,,current,,This attribute shall specify the set of data 
.1.2.840.10036.1.1.1.12,IEEE802dot11-MIB::dot11BeaconPeriod,INTEGER,read-write,,current,,This attribute shall specify the number of TUs that 
.1.2.840.10036.1.1.1.13,IEEE802dot11-MIB::dot11DTIMPeriod,INTEGER,read-write,,current,,This attribute shall specify the number of beacon
.1.2.840.10036.1.1.1.14,IEEE802dot11-MIB::dot11AssociationResponseTimeOut,Unsigned32,read-write,,current,,This attribute shall specify the number of TU that a
.1.2.840.10036.1.1.1.15,IEEE802dot11-MIB::dot11DisassociateReason,INTEGER,read-only,,current,,This attribute holds the most recently
.1.2.840.10036.1.1.1.16,IEEE802dot11-MIB::dot11DisassociateStation,OCTET,read-only,,current,,This attribute holds the MAC address from the
.1.2.840.10036.1.1.1.17,IEEE802dot11-MIB::dot11DeauthenticateReason,INTEGER,read-only,,current,,This attribute holds the most recently
.1.2.840.10036.1.1.1.18,IEEE802dot11-MIB::dot11DeauthenticateStation,OCTET,read-only,,current,,This attribute holds the MAC address from the
.1.2.840.10036.1.1.1.19,IEEE802dot11-MIB::dot11AuthenticateFailStatus,INTEGER,read-only,,current,,This attribute holds the most recently
.1.2.840.10036.1.1.1.20,IEEE802dot11-MIB::dot11AuthenticateFailStation,OCTET,read-only,,current,,This attribute holds the MAC address from the
.1.2.840.10036.1.1.1.21,IEEE802dot11-MIB::dot11MultiDomainCapabilityImplemented,INTEGER,read-write,,current,true(1):false(2),This attribute, when TRUE, indicates that the 
.1.2.840.10036.1.1.1.22,IEEE802dot11-MIB::dot11MultiDomainCapabilityEnabled,INTEGER,read-write,,current,true(1):false(2),This attribute, when TRUE, indicates that the 
.1.2.840.10036.1.1.1.23,IEEE802dot11-MIB::dot11CountryString,OCTET,read-only,,current,,This attribute identifies the country in which the 
.1.2.840.10036.1.2,IEEE802dot11-MIB::dot11AuthenticationAlgorithmsTable,,not-accessible,,current,,This (conceptual) table of attributes shall be a set of all the authentication algorithms supported by the stations. The following are the default values and the associated algorithm: Value = 1: Open System Value = 2: Shared Key
.1.2.840.10036.1.2.1,IEEE802dot11-MIB::dot11AuthenticationAlgorithmsEntry,,not-accessible,ifIndex:dot11AuthenticationAlgorithmsIndex,current,,An Entry (conceptual row) in the Authentication Algorithms Table.  ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.2.1.1,IEEE802dot11-MIB::dot11AuthenticationAlgorithmsIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the Authentication Algorithms Table.
.1.2.840.10036.1.2.1.2,IEEE802dot11-MIB::dot11AuthenticationAlgorithm,INTEGER,read-only,,current,openSystem(1):sharedKey(2),This attribute shall be a set of all the authentication
.1.2.840.10036.1.2.1.3,IEEE802dot11-MIB::dot11AuthenticationAlgorithmsEnable,INTEGER,read-write,,current,true(1):false(2),This attribute, when true at a station, shall enable the acceptance 
.1.2.840.10036.1.3,IEEE802dot11-MIB::dot11WEPDefaultKeysTable,,not-accessible,,current,,Conceptual table for WEP default keys. This table shall contain the four WEP default secret key values corresponding to the four possible KeyID values. The WEP default secret keys are logically WRITE-ONLY. Attempts to read the entries in this table shall return unsuccessful status and values of null or zero. The default value of each WEP default key shall be null.
.1.2.840.10036.1.3.1,IEEE802dot11-MIB::dot11WEPDefaultKeysEntry,,not-accessible,ifIndex:dot11WEPDefaultKeyIndex,current,,An Entry (conceptual row) in the WEP Default Keys Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.3.1.1,IEEE802dot11-MIB::dot11WEPDefaultKeyIndex,INTEGER,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the WEP Default Keys Table. The value of this variable is equal to the WEPDefaultKeyID + 1
.1.2.840.10036.1.3.1.2,IEEE802dot11-MIB::dot11WEPDefaultKeyValue,OCTET,read-write,,current,,A WEP default secret key value.
.1.2.840.10036.1.4,IEEE802dot11-MIB::dot11WEPKeyMappingsTable,,not-accessible,,current,,Conceptual table for WEP Key Mappings. The MIB supports the ability to share a separate WEP key for each RA/TA pair. The Key Mappings Table contains zero or one entry for each MAC address and contains two fields for each entry: WEPOn and the corresponding WEP key. The WEP key mappings are logically WRITE-ONLY. Attempts to read the entries in this table shall return unsuccessful status and values of null or zero. The default value for all WEPOn fields is false.
.1.2.840.10036.1.4.1,IEEE802dot11-MIB::dot11WEPKeyMappingsEntry,,not-accessible,ifIndex:dot11WEPKeyMappingIndex,current,,An Entry (conceptual row) in the WEP Key Mappings Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.4.1.1,IEEE802dot11-MIB::dot11WEPKeyMappingIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the WEP Key Mappings Table.
.1.2.840.10036.1.4.1.2,IEEE802dot11-MIB::dot11WEPKeyMappingAddress,OCTET,read-create,,current,,The MAC address of the STA for which the values from this key mapping entry are to be used.
.1.2.840.10036.1.4.1.3,IEEE802dot11-MIB::dot11WEPKeyMappingWEPOn,INTEGER,read-create,,current,true(1):false(2),Boolean as to whether WEP is to be used when communicating with the dot11WEPKeyMappingAddress STA.
.1.2.840.10036.1.4.1.4,IEEE802dot11-MIB::dot11WEPKeyMappingValue,OCTET,read-create,,current,,A WEP secret key value.
.1.2.840.10036.1.4.1.5,IEEE802dot11-MIB::dot11WEPKeyMappingStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status column used for creating, modifying, and deleting instances of the columnar objects in the WEP key mapping Table.
.1.2.840.10036.1.5,IEEE802dot11-MIB::dot11PrivacyTable,,not-accessible,,current,,Group containing attributes concerned with IEEE 802.11 Privacy. Created as a table to allow multiple instantiations on an agent.
.1.2.840.10036.1.5.1,IEEE802dot11-MIB::dot11PrivacyEntry,,not-accessible,ifIndex,current,,An entry in the dot11PrivacyTable Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.5.1.1,IEEE802dot11-MIB::dot11PrivacyInvoked,INTEGER,read-write,,current,true(1):false(2),When this attribute is true, it shall indicate that the IEEE
.1.2.840.10036.1.5.1.2,IEEE802dot11-MIB::dot11WEPDefaultKeyID,INTEGER,read-write,,current,,This attribute shall indicate the use of the first, second, third, or fourth element of the WEPDefaultKeys array when set to values of zero, one, two, or three. The default value of this attribute shall be 0.
.1.2.840.10036.1.5.1.3,IEEE802dot11-MIB::dot11WEPKeyMappingLength,Unsigned32,read-write,,current,,The maximum number of tuples that dot11WEPKeyMappings can hold.
.1.2.840.10036.1.5.1.4,IEEE802dot11-MIB::dot11ExcludeUnencrypted,INTEGER,read-write,,current,true(1):false(2),When this attribute is true, the STA shall not indicate at
.1.2.840.10036.1.5.1.5,IEEE802dot11-MIB::dot11WEPICVErrorCount,Counter32,read-only,,current,,This counter shall increment when a frame is received with the WEP subfield of the Frame Control field set to one and the value of the ICV as received in the frame does not match the ICV value that is calculated for the contents of the received frame.
.1.2.840.10036.1.5.1.6,IEEE802dot11-MIB::dot11WEPExcludedCount,Counter32,read-only,,current,,This counter shall increment when a frame is received with the WEP subfield of the Frame Control field set to zero and the value of dot11ExcludeUnencrypted causes that frame to be discarded.
.1.2.840.10036.1.6,IEEE802dot11-MIB::dot11SMTnotification,,,,,,
.1.2.840.10036.1.6.0,IEEE802dot11-MIB::anonymous#2,,,,,,
.1.2.840.10036.1.6.0.1,IEEE802dot11-MIB::dot11Disassociate,,,,,,The disassociate notification shall be sent when the STA ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.6.0.2,IEEE802dot11-MIB::dot11Deauthenticate,,,,,,The deauthenticate notification shall be sent when the STA ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.6.0.3,IEEE802dot11-MIB::dot11AuthenticateFail,,,,,,The authenticate failure notification shall be sent when the STA ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.1.7,IEEE802dot11-MIB::dot11MultiDomainCapabilityTable,,not-accessible,,current,,This (conceptual) table of attributes for 
.1.2.840.10036.1.7.1,IEEE802dot11-MIB::dot11MultiDomainCapabilityEntry,,not-accessible,ifIndex:dot11MultiDomainCapabilityIndex,current,,An entry (conceptual row) in the Multiple Domain  Capability Table.
.1.2.840.10036.1.7.1.1,IEEE802dot11-MIB::dot11MultiDomainCapabilityIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of 
.1.2.840.10036.1.7.1.2,IEEE802dot11-MIB::dot11FirstChannelNumber,Integer32,read-write,,current,,This attribute shall indicate the value of the lowest 
.1.2.840.10036.1.7.1.3,IEEE802dot11-MIB::dot11NumberofChannels,Integer32,read-write,,current,,This attribute shall indicate the value of the total 
.1.2.840.10036.1.7.1.4,IEEE802dot11-MIB::dot11MaximumTransmitPowerLevel,Integer32,read-write,,current,,This attribute shall indicate the maximum transmit power, 
.1.2.840.10036.2,IEEE802dot11-MIB::dot11mac,,,,,,
.1.2.840.10036.2.1,IEEE802dot11-MIB::dot11OperationTable,,not-accessible,,current,,Group contains MAC attributes pertaining to the operation of the MAC. This has been implemented as a table in order to allow for multiple instantiations on an agent.
.1.2.840.10036.2.1.1,IEEE802dot11-MIB::dot11OperationEntry,,not-accessible,ifIndex,current,,An entry in the dot11OperationEntry Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.2.1.1.1,IEEE802dot11-MIB::dot11MACAddress,OCTET,read-only,,current,,Unique MAC Address assigned to the STA.
.1.2.840.10036.2.1.1.2,IEEE802dot11-MIB::dot11RTSThreshold,INTEGER,read-write,,current,,This attribute shall indicate the number of octets in an MPDU,
.1.2.840.10036.2.1.1.3,IEEE802dot11-MIB::dot11ShortRetryLimit,INTEGER,read-write,,current,,This attribute shall indicate the maximum number of
.1.2.840.10036.2.1.1.4,IEEE802dot11-MIB::dot11LongRetryLimit,INTEGER,read-write,,current,,This attribute shall indicate the maximum number of
.1.2.840.10036.2.1.1.5,IEEE802dot11-MIB::dot11FragmentationThreshold,INTEGER,read-write,,current,,This attribute shall specify the current maximum size, in
.1.2.840.10036.2.1.1.6,IEEE802dot11-MIB::dot11MaxTransmitMSDULifetime,Unsigned32,read-write,,current,,The MaxTransmitMSDULifetime shall be the elapsed time in TU,
.1.2.840.10036.2.1.1.7,IEEE802dot11-MIB::dot11MaxReceiveLifetime,Unsigned32,read-write,,current,,The MaxReceiveLifetime shall be the elapsed time in TU, after the initial reception of a fragmented MMPDU or MSDU, after which further attempts to reassemble the MMPDU or MSDU shall be terminated. The default value shall be 512.
.1.2.840.10036.2.1.1.8,IEEE802dot11-MIB::dot11ManufacturerID,OCTET,read-only,,current,,The ManufacturerID shall include, at a minimum, the name of the manufacturer. It may include additional information at the manufacturer's discretion. The default value of this attribute shall be null.
.1.2.840.10036.2.1.1.9,IEEE802dot11-MIB::dot11ProductID,OCTET,read-only,,current,,The ProductID shall include, at a minimum, an identifier that is unique to the manufacturer. It may include additional information at the manufacturer's discretion. The default value of this attribute shall be null.
.1.2.840.10036.2.2,IEEE802dot11-MIB::dot11CountersTable,,not-accessible,,current,,Group containing attributes that are MAC counters. Implemented as a table to allow for multiple instantiations on an agent.
.1.2.840.10036.2.2.1,IEEE802dot11-MIB::dot11CountersEntry,,not-accessible,ifIndex,current,,An entry in the dot11CountersEntry Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.2.2.1.1,IEEE802dot11-MIB::dot11TransmittedFragmentCount,Counter32,read-only,,current,,This counter shall be incremented for an acknowledged MPDU with an individual address in the address 1 field or an MPDU with a multicast address in the address 1 field of type Data or Management.
.1.2.840.10036.2.2.1.2,IEEE802dot11-MIB::dot11MulticastTransmittedFrameCount,Counter32,read-only,,current,,This counter shall increment only when the multicast bit is set in the destination MAC address of a successfully transmitted MSDU. When operating as a STA in an ESS, where these frames are directed to the AP, this implies having received an acknowledgment to all associated MPDUs.
.1.2.840.10036.2.2.1.3,IEEE802dot11-MIB::dot11FailedCount,Counter32,read-only,,current,,This counter shall increment when an MSDU is not transmitted
.1.2.840.10036.2.2.1.4,IEEE802dot11-MIB::dot11RetryCount,Counter32,read-only,,current,,This counter shall increment when an MSDU is successfully transmitted after one or more retransmissions.
.1.2.840.10036.2.2.1.5,IEEE802dot11-MIB::dot11MultipleRetryCount,Counter32,read-only,,current,,This counter shall increment when an MSDU is successfully transmitted after more than one retransmission.
.1.2.840.10036.2.2.1.6,IEEE802dot11-MIB::dot11FrameDuplicateCount,Counter32,read-only,,current,,This counter shall increment when a frame is received that the Sequence Control field indicates is a duplicate.
.1.2.840.10036.2.2.1.7,IEEE802dot11-MIB::dot11RTSSuccessCount,Counter32,read-only,,current,,This counter shall increment when a CTS is received in response to an RTS.
.1.2.840.10036.2.2.1.8,IEEE802dot11-MIB::dot11RTSFailureCount,Counter32,read-only,,current,,This counter shall increment when a CTS is not received in
.1.2.840.10036.2.2.1.9,IEEE802dot11-MIB::dot11ACKFailureCount,Counter32,read-only,,current,,This counter shall increment when an ACK is not received when expected.
.1.2.840.10036.2.2.1.10,IEEE802dot11-MIB::dot11ReceivedFragmentCount,Counter32,read-only,,current,,This counter shall be incremented for each successfully received MPDU of type Data or Management.
.1.2.840.10036.2.2.1.11,IEEE802dot11-MIB::dot11MulticastReceivedFrameCount,Counter32,read-only,,current,,This counter shall increment when a MSDU is received with the multicast bit set in the destination MAC address.
.1.2.840.10036.2.2.1.12,IEEE802dot11-MIB::dot11FCSErrorCount,Counter32,read-only,,current,,This counter shall increment when an FCS error is detected in a received MPDU.
.1.2.840.10036.2.2.1.13,IEEE802dot11-MIB::dot11TransmittedFrameCount,Counter32,read-only,,current,,This counter shall increment for each successfully transmitted MSDU.
.1.2.840.10036.2.2.1.14,IEEE802dot11-MIB::dot11WEPUndecryptableCount,Counter32,read-only,,current,,This counter shall increment when a frame is received with
.1.2.840.10036.2.3,IEEE802dot11-MIB::dot11GroupAddressesTable,,not-accessible,,current,,A conceptual table containing a set of MAC addresses identifying the multicast addresses for which this STA will receive frames. The default value of this attribute shall be null.
.1.2.840.10036.2.3.1,IEEE802dot11-MIB::dot11GroupAddressesEntry,,not-accessible,ifIndex:dot11GroupAddressesIndex,current,,An Entry (conceptual row) in the Group Addresses Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.2.3.1.1,IEEE802dot11-MIB::dot11GroupAddressesIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the Group Addresses Table.
.1.2.840.10036.2.3.1.2,IEEE802dot11-MIB::dot11Address,OCTET,read-create,,current,,MAC address identifying a multicast addresses from which this STA will receive frames.
.1.2.840.10036.2.3.1.3,IEEE802dot11-MIB::dot11GroupAddressesStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status column used for creating, modifying, and deleting instances of the columnar objects in the Group Addresses Table.
.1.2.840.10036.3,IEEE802dot11-MIB::dot11res,,,,,,
.1.2.840.10036.3.1,IEEE802dot11-MIB::dot11resAttribute,,,,,,
.1.2.840.10036.3.1.1,IEEE802dot11-MIB::dot11ResourceTypeIDName,OCTET,read-only,,current,,Contains the name of the Resource Type ID managed object. The attribute is read-only and always contains the value RTID. This attribute value shall not be used as a naming attribute for any other managed object class.
.1.2.840.10036.3.1.2,IEEE802dot11-MIB::dot11ResourceInfoTable,,not-accessible,,current,,Provides a means of indicating, in data readable from a managed object, information that identifies the source of the implementation.
.1.2.840.10036.3.1.2.1,IEEE802dot11-MIB::dot11ResourceInfoEntry,,not-accessible,ifIndex,current,,An entry in the dot11ResourceInfo Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.3.1.2.1.1,IEEE802dot11-MIB::dot11manufacturerOUI,OCTET,read-only,,current,,Takes the value of an organizationally unique identifier.
.1.2.840.10036.3.1.2.1.2,IEEE802dot11-MIB::dot11manufacturerName,OCTET,read-only,,current,,A printable string used to identify the manufacturer of the resource. Maximum string length is 128 octets.
.1.2.840.10036.3.1.2.1.3,IEEE802dot11-MIB::dot11manufacturerProductName,OCTET,read-only,,current,,A printable string used to identify the manufacturer's product name of the resource. Maximum string length is 128 octets.
.1.2.840.10036.3.1.2.1.4,IEEE802dot11-MIB::dot11manufacturerProductVersion,OCTET,read-only,,current,,Printable string used to identify the manufacturer's product version of the resource. Maximum string length is 128 octets.
.1.2.840.10036.4,IEEE802dot11-MIB::dot11phy,,,,,,
.1.2.840.10036.4.1,IEEE802dot11-MIB::dot11PhyOperationTable,,not-accessible,,current,,PHY level attributes concerned with
.1.2.840.10036.4.1.1,IEEE802dot11-MIB::dot11PhyOperationEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyOperation Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.1.1.1,IEEE802dot11-MIB::dot11PHYType,INTEGER,read-only,,current,fhss(1):dsss(2):irbaseband(3):ofdm(4):hrdsss(5),This is an 8-bit integer value that identifies the PHY type
.1.2.840.10036.4.1.1.2,IEEE802dot11-MIB::dot11CurrentRegDomain,Integer32,read-write,,current,,The current regulatory domain this instance of the PMD is supporting. This object corresponds to one of the RegDomains listed in dot11RegDomainsSupported.
.1.2.840.10036.4.1.1.3,IEEE802dot11-MIB::dot11TempType,INTEGER,read-only,,current,tempType1(1):tempType2(2),There are different operating temperature requirements
.1.2.840.10036.4.2,IEEE802dot11-MIB::dot11PhyAntennaTable,,not-accessible,,current,,Group of attributes for PhyAntenna. Implemented as a table indexed on ifIndex to allow for multiple instances on an agent.
.1.2.840.10036.4.2.1,IEEE802dot11-MIB::dot11PhyAntennaEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyAntenna Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.2.1.1,IEEE802dot11-MIB::dot11CurrentTxAntenna,Integer32,read-write,,current,,The current antenna being used to transmit. This value
.1.2.840.10036.4.2.1.2,IEEE802dot11-MIB::dot11DiversitySupport,INTEGER,read-only,,current,fixedlist(1):notsupported(2):dynamic(3),This implementation's support for diversity, encoded as:
.1.2.840.10036.4.2.1.3,IEEE802dot11-MIB::dot11CurrentRxAntenna,Integer32,read-write,,current,,The current antenna being used to receive, if the dot11 
.1.2.840.10036.4.3,IEEE802dot11-MIB::dot11PhyTxPowerTable,,not-accessible,,current,,Group of attributes for dot11PhyTxPowerTable. Implemented as a table indexed on STA ID to allow for multiple instances on an Agent.
.1.2.840.10036.4.3.1,IEEE802dot11-MIB::dot11PhyTxPowerEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyTxPower Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.3.1.1,IEEE802dot11-MIB::dot11NumberSupportedPowerLevels,INTEGER,read-only,,current,,The number of power levels supported by the PMD. This attribute can have a value of 1 to 8.
.1.2.840.10036.4.3.1.2,IEEE802dot11-MIB::dot11TxPowerLevel1,INTEGER,read-only,,current,,The transmit output power for LEVEL1 in mW. This is also the default power level.
.1.2.840.10036.4.3.1.3,IEEE802dot11-MIB::dot11TxPowerLevel2,INTEGER,read-only,,current,,The transmit output power for LEVEL2 in mW.
.1.2.840.10036.4.3.1.4,IEEE802dot11-MIB::dot11TxPowerLevel3,INTEGER,read-only,,current,,The transmit output power for LEVEL3 in mW.
.1.2.840.10036.4.3.1.5,IEEE802dot11-MIB::dot11TxPowerLevel4,INTEGER,read-only,,current,,The transmit output power for LEVEL4 in mW.
.1.2.840.10036.4.3.1.6,IEEE802dot11-MIB::dot11TxPowerLevel5,INTEGER,read-only,,current,,The transmit output power for LEVEL5 in mW.
.1.2.840.10036.4.3.1.7,IEEE802dot11-MIB::dot11TxPowerLevel6,INTEGER,read-only,,current,,The transmit output power for LEVEL6 in mW.
.1.2.840.10036.4.3.1.8,IEEE802dot11-MIB::dot11TxPowerLevel7,INTEGER,read-only,,current,,The transmit output power for LEVEL7 in mW.
.1.2.840.10036.4.3.1.9,IEEE802dot11-MIB::dot11TxPowerLevel8,INTEGER,read-only,,current,,The transmit output power for LEVEL8 in mW.
.1.2.840.10036.4.3.1.10,IEEE802dot11-MIB::dot11CurrentTxPowerLevel,INTEGER,read-write,,current,,The TxPowerLevel N currently being used to transmit data. Some PHYs also use this value to determine the receiver sensitivity requirements for CCA.
.1.2.840.10036.4.4,IEEE802dot11-MIB::dot11PhyFHSSTable,,not-accessible,,current,,Group of attributes for dot11PhyFHSSTable. Implemented as a table indexed on STA ID to allow for multiple instances on an Agent.
.1.2.840.10036.4.4.1,IEEE802dot11-MIB::dot11PhyFHSSEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyFHSS Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.4.1.1,IEEE802dot11-MIB::dot11HopTime,INTEGER,read-only,,current,,The time in microseconds for the PMD to change from channel 2 to channel 80.
.1.2.840.10036.4.4.1.2,IEEE802dot11-MIB::dot11CurrentChannelNumber,INTEGER,read-write,,current,,The current channel number of the frequency output by the RF synthesizer.
.1.2.840.10036.4.4.1.3,IEEE802dot11-MIB::dot11MaxDwellTime,INTEGER,read-only,,current,,The maximum time in TU that the transmitter is permitted to operate on a single channel.
.1.2.840.10036.4.4.1.4,IEEE802dot11-MIB::dot11CurrentDwellTime,INTEGER,read-write,,current,,The current time in TU that the transmitter shall operate on a single channel, as set by the MAC. Default is 19 TU.
.1.2.840.10036.4.4.1.5,IEEE802dot11-MIB::dot11CurrentSet,INTEGER,read-write,,current,,The current set of patterns the PLME 
.1.2.840.10036.4.4.1.6,IEEE802dot11-MIB::dot11CurrentPattern,INTEGER,read-write,,current,,The current pattern the PLME is using to determine the hop sequence.
.1.2.840.10036.4.4.1.7,IEEE802dot11-MIB::dot11CurrentIndex,INTEGER,read-write,,current,,The current index value the PLME is using to determine the CurrentChannelNumber.
.1.2.840.10036.4.4.1.8,IEEE802dot11-MIB::dot11EHCCPrimeRadix,Integer32,read-write,,current,,This attribute indicates the value to be 
.1.2.840.10036.4.4.1.9,IEEE802dot11-MIB::dot11EHCCNumberofChannelsFamilyIndex,Integer32,read-write,,current,,This attribute indicates the value to be 
.1.2.840.10036.4.4.1.10,IEEE802dot11-MIB::dot11EHCCCapabilityImplemented,INTEGER,read-write,,current,true(1):false(2),This attribute, when TRUE, indicates that the 
.1.2.840.10036.4.4.1.11,IEEE802dot11-MIB::dot11EHCCCapabilityEnabled,INTEGER,read-write,,current,true(1):false(2),This attribute, when TRUE, indicates that the 
.1.2.840.10036.4.4.1.12,IEEE802dot11-MIB::dot11HopAlgorithmAdopted,INTEGER,read-write,,current,crnt(1):hopindex(2):hcc(3),This attribute, indicates which of the algorithms 
.1.2.840.10036.4.4.1.13,IEEE802dot11-MIB::dot11RandomTableFlag,INTEGER,read-write,,current,true(1):false(2),This attribute, indicates that a Random Table is 
.1.2.840.10036.4.4.1.14,IEEE802dot11-MIB::dot11NumberofHoppingSets,Integer32,read-only,,current,,The Number of Sets field indicates the total 
.1.2.840.10036.4.4.1.15,IEEE802dot11-MIB::dot11HopModulus,Integer32,read-only,,current,,The number of allowed channels for the hopping 
.1.2.840.10036.4.4.1.16,IEEE802dot11-MIB::dot11HopOffset,Integer32,read-write,,current,,The next position in the hopping set.
.1.2.840.10036.4.5,IEEE802dot11-MIB::dot11PhyDSSSTable,,not-accessible,,current,,Entry of attributes for dot11PhyDSSSEntry. Implemented as a table indexed on ifIndex allow for multiple instances on an Agent.
.1.2.840.10036.4.5.1,IEEE802dot11-MIB::dot11PhyDSSSEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyDSSSEntry Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.5.1.1,IEEE802dot11-MIB::dot11CurrentChannel,INTEGER,read-write,,current,,The current operating frequency channel of the DSSS PHY. Valid channel numbers are as defined in 15.4.6.2
.1.2.840.10036.4.5.1.2,IEEE802dot11-MIB::dot11CCAModeSupported,INTEGER,read-only,,current,,dot11CCAModeSupported is a bit-significant value, energy detect only (ED_ONLY) = 01,
.1.2.840.10036.4.5.1.3,IEEE802dot11-MIB::dot11CurrentCCAMode,INTEGER,read-write,,current,edonly(1):csonly(2):edandcs(4):cswithtimer(8):hrcsanded(16),The current CCA method in operation. Valid values are: energy detect only (edonly) = 01, carrier sense only (csonly) = 02, carrier sense and energy detect (edandcs)= 04 carrier sense with timer (cswithtimer)= 08 high rate carrier sense and energy detect (hrcsanded)=16.
.1.2.840.10036.4.5.1.4,IEEE802dot11-MIB::dot11EDThreshold,Integer32,read-write,,current,,The current Energy Detect Threshold being used by the DSSS PHY.
.1.2.840.10036.4.6,IEEE802dot11-MIB::dot11PhyIRTable,,not-accessible,,current,,Group of attributes for dot11PhyIRTable. Implemented as a table indexed on ifIndex to allow for multiple instances on an Agent.
.1.2.840.10036.4.6.1,IEEE802dot11-MIB::dot11PhyIREntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyIR Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.6.1.1,IEEE802dot11-MIB::dot11CCAWatchdogTimerMax,Integer32,read-write,,current,,This parameter, together with CCAWatchdogCountMax, determines when energy detected in the channel can be ignored.
.1.2.840.10036.4.6.1.2,IEEE802dot11-MIB::dot11CCAWatchdogCountMax,Integer32,read-write,,current,,This parameter, together with CCAWatchdogTimerMax, determines when energy detected in the channel can be ignored.
.1.2.840.10036.4.6.1.3,IEEE802dot11-MIB::dot11CCAWatchdogTimerMin,Integer32,read-write,,current,,The minimum value to which CCAWatchdogTimerMax can be set.
.1.2.840.10036.4.6.1.4,IEEE802dot11-MIB::dot11CCAWatchdogCountMin,Integer32,read-write,,current,,The minimum value to which CCAWatchdogCount can be set.
.1.2.840.10036.4.7,IEEE802dot11-MIB::dot11RegDomainsSupportedTable,,not-accessible,,current,,There are different operational requirements dependent on the regulatory domain. This attribute list describes the regulatory domains the PLCP and PMD support in this implementation. Currently defined values and their corresponding Regulatory Domains are: FCC (USA) = X'10', DOC (Canada) = X'20', ETSI (most of Europe) = X'30', Spain = X'31', France = X'32', MKK (Japan) = X'40', Others = X'00' 
.1.2.840.10036.4.7.1,IEEE802dot11-MIB::dot11RegDomainsSupportedEntry,,not-accessible,ifIndex:dot11RegDomainsSupportedIndex,current,,An entry in the dot11RegDomainsSupportedTable. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.7.1.1,IEEE802dot11-MIB::dot11RegDomainsSupportedIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the RegDomainsSupport Table.
.1.2.840.10036.4.7.1.2,IEEE802dot11-MIB::dot11RegDomainsSupportedValue,INTEGER,read-only,,current,fcc(16):doc(32):etsi(48):spain(49):france(50):mkk(64),There are different operational requirements dependent on the regulatory domain. This attribute list describes the regulatory domains the PLCP and PMD support in this implementation. Currently defined values and their corresponding Regulatory Domains are: FCC (USA) = X'10', DOC (Canada) = X'20', ETSI (most of Europe) = X'30', Spain = X'31', France = X'32', MKK (Japan) = X'40' 
.1.2.840.10036.4.8,IEEE802dot11-MIB::dot11AntennasListTable,,not-accessible,,current,,This table represents the list of antennae. An antenna can be 
.1.2.840.10036.4.8.1,IEEE802dot11-MIB::dot11AntennasListEntry,,not-accessible,ifIndex:dot11AntennaListIndex,current,,An entry in the dot11AntennasListTable, representing the properties  of a single antenna. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.8.1.1,IEEE802dot11-MIB::dot11AntennaListIndex,Integer32,not-accessible,,current,,The unique index of an antenna which is used to identify the columnar  objects in the dot11AntennasList Table.
.1.2.840.10036.4.8.1.2,IEEE802dot11-MIB::dot11SupportedTxAntenna,INTEGER,read-write,,current,true(1):false(2),When true, this object indicates that the antenna represented by  dot11AntennaIndex can be used as a transmit antenna.
.1.2.840.10036.4.8.1.3,IEEE802dot11-MIB::dot11SupportedRxAntenna,INTEGER,read-write,,current,true(1):false(2),When true, this object indicates that the antenna represented by the  dot11AntennaIndex xan be used as a receive antenna.
.1.2.840.10036.4.8.1.4,IEEE802dot11-MIB::dot11DiversitySelectionRx,INTEGER,read-write,,current,true(1):false(2),When true, this object indicates that the antenna represented by  dot11AntennaIndex can be used for receive diversity. This object  may only be true if the antenna can be used as a receive antenna,  as indicated by dot11SupportedRxAntenna.
.1.2.840.10036.4.9,IEEE802dot11-MIB::dot11SupportedDataRatesTxTable,,not-accessible,,current,,The Transmit bit rates supported by the PLCP and PMD, represented by a count from X'02-X'7f, corresponding to data rates in increments of 500kbit/s from 1 Mbit/s to 63.5 Mbit/s subject to limitations of each individual PHY.
.1.2.840.10036.4.9.1,IEEE802dot11-MIB::dot11SupportedDataRatesTxEntry,,not-accessible,ifIndex:dot11SupportedDataRatesTxIndex,current,,An Entry (conceptual row) in the dot11SupportedDataRatesTx Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.9.1.1,IEEE802dot11-MIB::dot11SupportedDataRatesTxIndex,Integer32,not-accessible,,current,,Index object which identifies which data rate to access. Range is 1..8.
.1.2.840.10036.4.9.1.2,IEEE802dot11-MIB::dot11SupportedDataRatesTxValue,Integer32,read-only,,current,,The Transmit bit rates supported by the PLCP and PMD, represented by a count from X'02-X'7f, corresponding to data rates in increments of 500kbit/s from 1 Mbit/s to 63.5 Mbit/s subject to limitations of each individual PHY.
.1.2.840.10036.4.10,IEEE802dot11-MIB::dot11SupportedDataRatesRxTable,,not-accessible,,current,,The receive bit rates supported by the PLCP and PMD, represented by a count from X'002-X'7f, corresponding to data rates in increments of 500kbit/s from 1 Mbit/s to 63.5 Mbit/s.
.1.2.840.10036.4.10.1,IEEE802dot11-MIB::dot11SupportedDataRatesRxEntry,,not-accessible,ifIndex:dot11SupportedDataRatesRxIndex,current,,An Entry (conceptual row) in the dot11SupportedDataRatesRx Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.10.1.1,IEEE802dot11-MIB::dot11SupportedDataRatesRxIndex,Integer32,not-accessible,,current,,Index object which identifies which data rate to access. Range is 1..8.
.1.2.840.10036.4.10.1.2,IEEE802dot11-MIB::dot11SupportedDataRatesRxValue,Integer32,read-only,,current,,The receive bit rates supported by the PLCP and PMD, represented by a count from X'02-X'7f, corresponding to data rates in increments of 500kbit/s from 1 Mbit/s to 63.5 Mbit/s.
.1.2.840.10036.4.11,IEEE802dot11-MIB::dot11PhyOFDMTable,,not-accessible,,current,,Group of attributes for dot11PhyOFDMTable. Implemented as a table indexed on ifindex to allow for multiple instances on an Agent.
.1.2.840.10036.4.11.1,IEEE802dot11-MIB::dot11PhyOFDMEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyOFDM Table. ifIndex - Each IEEE 802.11 interface is represented by an ifEntry. Interface tables in this MIB module are indexed by ifIndex.
.1.2.840.10036.4.11.1.1,IEEE802dot11-MIB::dot11CurrentFrequency,INTEGER,read-write,,current,,The number of the current operating frequency channel of the OFDM PHY.
.1.2.840.10036.4.11.1.2,IEEE802dot11-MIB::dot11TIThreshold,Integer32,read-write,,current,,The Threshold being used to detect a busy medium (frequency). CCA shall report a busy medium upon detecting the RSSI above 
.1.2.840.10036.4.11.1.3,IEEE802dot11-MIB::dot11FrequencyBandsSupported,INTEGER,read-only,,current,,The capability of the OFDM PHY implementation to operate in  bit 0 .. capable of operating in the lower (5.15-5.25 GHz) bit 1 .. capable of operating in the middle (5.25-5.35 GHz)  bit 2 .. capable of operating in the upper (5.725-5.825 GHz)  For example, for an implementation capable of operating in the 
.1.2.840.10036.4.12,IEEE802dot11-MIB::dot11PhyHRDSSSTable,,not-accessible,,current,,Entry of attributes for dot11PhyHRDSSSEntry.
.1.2.840.10036.4.12.1,IEEE802dot11-MIB::dot11PhyHRDSSSEntry,,not-accessible,ifIndex,current,,An entry in the dot11PhyHRDSSSEntry Table.
.1.2.840.10036.4.12.1.1,IEEE802dot11-MIB::dot11ShortPreambleOptionImplemented,INTEGER,read-only,,current,true(1):false(2),This attribute, when true, shall indicate that the
.1.2.840.10036.4.12.1.2,IEEE802dot11-MIB::dot11PBCCOptionImplemented,INTEGER,read-only,,current,true(1):false(2),This attribute, when true, shall indicate that the PBCC
.1.2.840.10036.4.12.1.3,IEEE802dot11-MIB::dot11ChannelAgilityPresent,INTEGER,read-only,,current,true(1):false(2),This attribute indicates that the PHY is capable of
.1.2.840.10036.4.12.1.4,IEEE802dot11-MIB::dot11ChannelAgilityEnabled,INTEGER,read-only,,current,true(1):false(2),This attribute indicates that the PHY channel agility
.1.2.840.10036.4.12.1.5,IEEE802dot11-MIB::dot11HRCCAModeSupported,INTEGER,read-only,,current,,dot11HRCCAModeSupported is a bit-significant value,
.1.2.840.10036.4.13,IEEE802dot11-MIB::dot11HoppingPatternTable,,not-accessible,,current,,The (conceptual) table of attributes necessary for 
.1.2.840.10036.4.13.1,IEEE802dot11-MIB::dot11HoppingPatternEntry,,not-accessible,ifIndex:dot11HoppingPatternIndex,current,,An entry (conceptual row) in the Hopping Pattern Table 
.1.2.840.10036.4.13.1.1,IEEE802dot11-MIB::dot11HoppingPatternIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of 
.1.2.840.10036.4.13.1.2,IEEE802dot11-MIB::dot11RandomTableFieldNumber,Integer32,read-write,,current,,This attribute shall indicate the value of the 
.1.2.840.10036.5,IEEE802dot11-MIB::dot11Conformance,,,,,,
.1.2.840.10036.5.1,IEEE802dot11-MIB::dot11Groups,,,,,,
.1.2.840.10036.5.1.1,IEEE802dot11-MIB::dot11SMTbase,,,,,,The SMT object class provides the necessary support at the STA to manage the processes in the STA such that the STA may work cooperatively as a part of an IEEE 802.11 network.
.1.2.840.10036.5.1.2,IEEE802dot11-MIB::dot11SMTprivacy,,,,,,The SMTPrivacy package is a set of attributes that shall be present if WEP is implemented in the STA.
.1.2.840.10036.5.1.3,IEEE802dot11-MIB::dot11MACbase,,,,,,The MAC object class provides the necessary support for the access control, generation, and verification of frame check sequences (FCSs), and proper delivery of valid data to upper layers.
.1.2.840.10036.5.1.4,IEEE802dot11-MIB::dot11MACStatistics,,,,,,The MACStatistics package provides extended statistical information on the operation of the MAC. This  package is completely optional.
.1.2.840.10036.5.1.5,IEEE802dot11-MIB::dot11ResourceTypeID,,,,,,Attributes used to identify a STA, its manufacturer, and various product names and versions.
.1.2.840.10036.5.1.6,IEEE802dot11-MIB::dot11SmtAuthenticationAlgorithms,,,,,,Authentication Algorithm Table.
.1.2.840.10036.5.1.7,IEEE802dot11-MIB::dot11PhyOperationComplianceGroup,,,,,,PHY layer operations attributes.
.1.2.840.10036.5.1.8,IEEE802dot11-MIB::dot11PhyAntennaComplianceGroup,,,,,,Attributes for Data Rates for IEEE 802.11.
.1.2.840.10036.5.1.9,IEEE802dot11-MIB::dot11PhyTxPowerComplianceGroup,,,,,,Attributes for Control and Management of transmit power.
.1.2.840.10036.5.1.10,IEEE802dot11-MIB::dot11PhyFHSSComplianceGroup,,,,,,Attributes that configure the Frequency Hopping for IEEE 802.11.
.1.2.840.10036.5.1.11,IEEE802dot11-MIB::dot11PhyDSSSComplianceGroup,,,,,,Attributes that configure the DSSS for IEEE 802.11.
.1.2.840.10036.5.1.12,IEEE802dot11-MIB::dot11PhyIRComplianceGroup,,,,,,Attributes that configure the baseband IR for IEEE 802.11.
.1.2.840.10036.5.1.13,IEEE802dot11-MIB::dot11PhyRegDomainsSupportGroup,,,,,,Attributes that specify the supported Regulation Domains.
.1.2.840.10036.5.1.14,IEEE802dot11-MIB::dot11PhyAntennasListGroup,,,,,,Attributes that specify the supported Regulation Domains.
.1.2.840.10036.5.1.15,IEEE802dot11-MIB::dot11PhyRateGroup,,,,,,Attributes for Data Rates for IEEE 802.11.
.1.2.840.10036.5.1.16,IEEE802dot11-MIB::dot11CountersGroup,,,,,,Attributes from the dot11CountersGroup that are not described in the dot11MACStatistics group. These objects are mandatory.
.1.2.840.10036.5.1.17,IEEE802dot11-MIB::dot11NotificationGroup,,,,,,IEEE 802.11 notifications
.1.2.840.10036.5.1.18,IEEE802dot11-MIB::dot11SMTbase2,,,,,,The SMTbase2 object class provides the necessary support at the STA to manage the processes in the STA such that the STA may work cooperatively as a part of an IEEE 802.11 network.
.1.2.840.10036.5.1.19,IEEE802dot11-MIB::dot11PhyOFDMComplianceGroup,,,,,,Attributes that configure the OFDM for IEEE 802.11.
.1.2.840.10036.5.1.20,IEEE802dot11-MIB::dot11SMTbase3,,,,,,The SMTbase3 object class provides the necessary support at the
.1.2.840.10036.5.1.21,IEEE802dot11-MIB::dot11MultiDomainCapabilityGroup,,,,,,The dot11MultiDomainCapabilityGroup object class provides 
.1.2.840.10036.5.1.22,IEEE802dot11-MIB::dot11PhyFHSSComplianceGroup2,,,,,,Attributes that configure the Frequency Hopping for IEEE 802.11 when multi-domain capability option is implemented.
.1.2.840.10036.5.1.23,IEEE802dot11-MIB::dot11PhyHRDSSSComplianceGroup,,,,,,Attributes that configure the HRDSSS for IEEE 802.11.
.1.2.840.10036.5.2,IEEE802dot11-MIB::dot11Compliances,,,,,,
.1.2.840.10036.5.2.1,IEEE802dot11-MIB::dot11Compliance,,,,,,The compliance statement for SNMPv2 entities that implement the IEEE 802.11 MIB.
.1.3,SNMPv2-SMI::org,,,,,,
.1.3.6,SNMPv2-SMI::dod,,,,,,
.1.3.6.1,SNMPv2-SMI::internet,,,,,,
.1.3.6.1.1,SNMPv2-SMI::directory,,,,,,
.1.3.6.1.2,SNMPv2-SMI::mgmt,,,,,,
.1.3.6.1.2.1,SNMPv2-SMI::mib-2,,,,,,
.1.3.6.1.2.1.1,SNMPv2-MIB::system,,,,,,
.1.3.6.1.2.1.1.1,SNMPv2-MIB::sysDescr,OCTET,read-only,,current,,A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software.
.1.3.6.1.2.1.1.2,SNMPv2-MIB::sysObjectID,OBJECT,read-only,,current,,The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.424242, it could assign the identifier 1.3.6.1.4.1.424242.1.1 to its `Fred Router'.
.1.3.6.1.2.1.1.3,SNMPv2-MIB::sysUpTime,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the network management portion of the system was last re-initialized.
.1.3.6.1.2.1.1.3.0,DISMAN-EVENT-MIB::sysUpTimeInstance,,,,,,
.1.3.6.1.2.1.1.4,SNMPv2-MIB::sysContact,OCTET,read-write,,current,,The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.
.1.3.6.1.2.1.1.5,SNMPv2-MIB::sysName,OCTET,read-write,,current,,An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.
.1.3.6.1.2.1.1.6,SNMPv2-MIB::sysLocation,OCTET,read-write,,current,,The physical location of this node (e.g., 'telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.
.1.3.6.1.2.1.1.7,SNMPv2-MIB::sysServices,INTEGER,read-only,,current,,A value which indicates the set of services that this entity may potentially offer. The value is a sum. This sum initially takes the value zero. Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs only routing functions would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly: layer functionality 1 physical (e.g., repeaters) 2 datalink/subnetwork (e.g., bridges) 3 internet (e.g., supports the IP) 4 end-to-end (e.g., supports the TCP) 7 applications (e.g., supports the SMTP) For systems including OSI protocols, layers 5 and 6 may also be counted.
.1.3.6.1.2.1.1.8,SNMPv2-MIB::sysORLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the most recent change in state or value of any instance of sysORID.
.1.3.6.1.2.1.1.9,SNMPv2-MIB::sysORTable,,not-accessible,,current,,The (conceptual) table listing the capabilities of the local SNMP application acting as a command responder with respect to various MIB modules. SNMP entities having dynamically-configurable support of MIB modules will have a dynamically-varying number of conceptual rows.
.1.3.6.1.2.1.1.9.1,SNMPv2-MIB::sysOREntry,,not-accessible,sysORIndex,current,,An entry (conceptual row) in the sysORTable.
.1.3.6.1.2.1.1.9.1.1,SNMPv2-MIB::sysORIndex,INTEGER,not-accessible,,current,,The auxiliary variable used for identifying instances of the columnar objects in the sysORTable.
.1.3.6.1.2.1.1.9.1.2,SNMPv2-MIB::sysORID,OBJECT,read-only,,current,,An authoritative identification of a capabilities statement with respect to various MIB modules supported by the local SNMP application acting as a command responder.
.1.3.6.1.2.1.1.9.1.3,SNMPv2-MIB::sysORDescr,OCTET,read-only,,current,,A textual description of the capabilities identified by the corresponding instance of sysORID.
.1.3.6.1.2.1.1.9.1.4,SNMPv2-MIB::sysORUpTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time this conceptual row was last instantiated.
.1.3.6.1.2.1.2,IF-MIB::interfaces,,,,,,
.1.3.6.1.2.1.2.1,IF-MIB::ifNumber,Integer32,read-only,,current,,The number of network interfaces (regardless of their current state) present on this system.
.1.3.6.1.2.1.2.2,IF-MIB::ifTable,,not-accessible,,current,,A list of interface entries. The number of entries is given by the value of ifNumber.
.1.3.6.1.2.1.2.2.1,IF-MIB::ifEntry,,not-accessible,ifIndex,current,,An entry containing management information applicable to a particular interface.
.1.3.6.1.2.1.2.2.1.1,IF-MIB::ifIndex,Integer32,read-only,,current,,A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
.1.3.6.1.2.1.2.2.1.2,IF-MIB::ifDescr,OCTET,read-only,,current,,A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.
.1.3.6.1.2.1.2.2.1.3,IF-MIB::ifType,INTEGER,read-only,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention.
.1.3.6.1.2.1.2.2.1.4,IF-MIB::ifMtu,Integer32,read-only,,current,,The size of the largest packet which can be sent/received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.
.1.3.6.1.2.1.2.2.1.5,IF-MIB::ifSpeed,Gauge32,read-only,,current,,An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable by this object then this object should report its maximum value (4,294,967,295) and ifHighSpeed must be used to report the interace's speed. For a sub-layer which has no concept of bandwidth, this object should be zero.
.1.3.6.1.2.1.2.2.1.6,IF-MIB::ifPhysAddress,OCTET,read-only,,current,,The interface's address at its protocol sub-layer. For example, for an 802.x interface, this object normally contains a MAC address. The interface's media-specific MIB must define the bit and byte ordering and the format of the value of this object. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length.
.1.3.6.1.2.1.2.2.1.7,IF-MIB::ifAdminStatus,INTEGER,read-write,,current,up(1):down(2):testing(3),The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
.1.3.6.1.2.1.2.2.1.8,IF-MIB::ifOperStatus,INTEGER,read-only,,current,up(1):down(2):testing(3):unknown(4):dormant(5):notPresent(6):lowerLayerDown(7),The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components.
.1.3.6.1.2.1.2.2.1.9,IF-MIB::ifLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.2.2.1.10,IF-MIB::ifInOctets,Counter32,read-only,,current,,The total number of octets received on the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.11,IF-MIB::ifInUcastPkts,Counter32,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.12,IF-MIB::ifInNUcastPkts,Counter32,read-only,,deprecated,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast or broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. This object is deprecated in favour of ifInMulticastPkts and ifInBroadcastPkts.
.1.3.6.1.2.1.2.2.1.13,IF-MIB::ifInDiscards,Counter32,read-only,,current,,The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.14,IF-MIB::ifInErrors,Counter32,read-only,,current,,For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character- oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.15,IF-MIB::ifInUnknownProtos,Counter32,read-only,,current,,For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing the number of transmission units received via the interface which were discarded because of an unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter will always be 0. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.16,IF-MIB::ifOutOctets,Counter32,read-only,,current,,The total number of octets transmitted out of the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.17,IF-MIB::ifOutUcastPkts,Counter32,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.18,IF-MIB::ifOutNUcastPkts,Counter32,read-only,,deprecated,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. This object is deprecated in favour of ifOutMulticastPkts and ifOutBroadcastPkts.
.1.3.6.1.2.1.2.2.1.19,IF-MIB::ifOutDiscards,Counter32,read-only,,current,,The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.20,IF-MIB::ifOutErrors,Counter32,read-only,,current,,For packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted because of errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.2.2.1.21,IF-MIB::ifOutQLen,Gauge32,read-only,,deprecated,,The length of the output packet queue (in packets).
.1.3.6.1.2.1.2.2.1.22,IF-MIB::ifSpecific,OBJECT,read-only,,deprecated,,A reference to MIB definitions specific to the particular media being used to realize the interface. It is recommended that this value point to an instance of a MIB object in the media-specific MIB, i.e., that this object have the semantics associated with the InstancePointer textual convention defined in RFC 2579. In fact, it is recommended that the media-specific MIB specify what value ifSpecific should/can take for values of ifType. If no MIB definitions specific to the particular media are available, the value should be set to the OBJECT IDENTIFIER { 0 0 }.
.1.3.6.1.2.1.3,RFC1213-MIB::at,,,,,,
.1.3.6.1.2.1.3.1,RFC1213-MIB::atTable,,not-accessible,,deprecated,,The Address Translation tables contain the NetworkAddress to `physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries.
.1.3.6.1.2.1.3.1.1,RFC1213-MIB::atEntry,,not-accessible,atIfIndex:atNetAddress,deprecated,,Each entry contains one NetworkAddress to `physical' address equivalence.
.1.3.6.1.2.1.3.1.1.1,RFC1213-MIB::atIfIndex,INTEGER,read-write,,deprecated,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.3.1.1.2,RFC1213-MIB::atPhysAddress,OCTET,read-write,,deprecated,,The media-dependent `physical' address. Setting this object to a null string (one of zero length) has the effect of invaliding the corresponding entry in the atTable object. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atPhysAddress object.
.1.3.6.1.2.1.3.1.1.3,RFC1213-MIB::atNetAddress,NetworkAddress,read-write,,deprecated,,The NetworkAddress (e.g., the IP address) corresponding to the media-dependent `physical' address.
.1.3.6.1.2.1.4,RFC1213-MIB::ip,,,,,,
.1.3.6.1.2.1.4.1,RFC1213-MIB::ipForwarding,INTEGER,read-write,,mandatory,forwarding(1):not-forwarding(2),The indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host). Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to change this object to an inappropriate value.
.1.3.6.1.2.1.4.2,RFC1213-MIB::ipDefaultTTL,INTEGER,read-write,,mandatory,,The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
.1.3.6.1.2.1.4.3,RFC1213-MIB::ipInReceives,Counter32,read-only,,mandatory,,The total number of input datagrams received from interfaces, including those received in error.
.1.3.6.1.2.1.4.4,RFC1213-MIB::ipInHdrErrors,Counter32,read-only,,mandatory,,The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
.1.3.6.1.2.1.4.5,RFC1213-MIB::ipInAddrErrors,Counter32,read-only,,mandatory,,The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
.1.3.6.1.2.1.4.6,RFC1213-MIB::ipForwDatagrams,Counter32,read-only,,mandatory,,The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful.
.1.3.6.1.2.1.4.7,RFC1213-MIB::ipInUnknownProtos,Counter32,read-only,,mandatory,,The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
.1.3.6.1.2.1.4.8,RFC1213-MIB::ipInDiscards,Counter32,read-only,,mandatory,,The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
.1.3.6.1.2.1.4.9,RFC1213-MIB::ipInDelivers,Counter32,read-only,,mandatory,,The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
.1.3.6.1.2.1.4.10,RFC1213-MIB::ipOutRequests,Counter32,read-only,,mandatory,,The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
.1.3.6.1.2.1.4.11,RFC1213-MIB::ipOutDiscards,Counter32,read-only,,mandatory,,The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
.1.3.6.1.2.1.4.12,RFC1213-MIB::ipOutNoRoutes,Counter32,read-only,,mandatory,,The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagarms which a host cannot route because all of its default gateways are down.
.1.3.6.1.2.1.4.13,RFC1213-MIB::ipReasmTimeout,INTEGER,read-only,,mandatory,,The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
.1.3.6.1.2.1.4.14,RFC1213-MIB::ipReasmReqds,Counter32,read-only,,mandatory,,The number of IP fragments received which needed to be reassembled at this entity.
.1.3.6.1.2.1.4.15,RFC1213-MIB::ipReasmOKs,Counter32,read-only,,mandatory,,The number of IP datagrams successfully re- assembled.
.1.3.6.1.2.1.4.16,RFC1213-MIB::ipReasmFails,Counter32,read-only,,mandatory,,The number of failures detected by the IP re- assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
.1.3.6.1.2.1.4.17,RFC1213-MIB::ipFragOKs,Counter32,read-only,,mandatory,,The number of IP datagrams that have been successfully fragmented at this entity.
.1.3.6.1.2.1.4.18,RFC1213-MIB::ipFragFails,Counter32,read-only,,mandatory,,The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
.1.3.6.1.2.1.4.19,RFC1213-MIB::ipFragCreates,Counter32,read-only,,mandatory,,The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
.1.3.6.1.2.1.4.20,RFC1213-MIB::ipAddrTable,,not-accessible,,mandatory,,The table of addressing information relevant to this entity's IP addresses.
.1.3.6.1.2.1.4.20.1,RFC1213-MIB::ipAddrEntry,,not-accessible,ipAdEntAddr,mandatory,,The addressing information for one of this entity's IP addresses.
.1.3.6.1.2.1.4.20.1.1,RFC1213-MIB::ipAdEntAddr,IpAddress,read-only,,mandatory,,The IP address to which this entry's addressing information pertains.
.1.3.6.1.2.1.4.20.1.2,RFC1213-MIB::ipAdEntIfIndex,INTEGER,read-only,,mandatory,,The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.4.20.1.3,RFC1213-MIB::ipAdEntNetMask,IpAddress,read-only,,mandatory,,The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.
.1.3.6.1.2.1.4.20.1.4,RFC1213-MIB::ipAdEntBcastAddr,INTEGER,read-only,,mandatory,,The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this (logical) interface.
.1.3.6.1.2.1.4.20.1.5,RFC1213-MIB::ipAdEntReasmMaxSize,INTEGER,read-only,,mandatory,,The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.
.1.3.6.1.2.1.4.21,RFC1213-MIB::ipRouteTable,,not-accessible,,mandatory,,This entity's IP Routing table.
.1.3.6.1.2.1.4.21.1,RFC1213-MIB::ipRouteEntry,,not-accessible,ipRouteDest,mandatory,,A route to a particular destination.
.1.3.6.1.2.1.4.21.1.1,RFC1213-MIB::ipRouteDest,IpAddress,read-write,,mandatory,,The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. Multiple routes to a single destination can appear in the table, but access to such multiple entries is dependent on the table- access mechanisms defined by the network management protocol in use.
.1.3.6.1.2.1.4.21.1.2,RFC1213-MIB::ipRouteIfIndex,INTEGER,read-write,,mandatory,,The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.4.21.1.3,RFC1213-MIB::ipRouteMetric1,INTEGER,read-write,,mandatory,,The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.4,RFC1213-MIB::ipRouteMetric2,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.5,RFC1213-MIB::ipRouteMetric3,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.6,RFC1213-MIB::ipRouteMetric4,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.7,RFC1213-MIB::ipRouteNextHop,IpAddress,read-write,,mandatory,,The IP address of the next hop of this route. (In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that interface.)
.1.3.6.1.2.1.4.21.1.8,RFC1213-MIB::ipRouteType,INTEGER,read-write,,mandatory,other(1):invalid(2):direct(3):indirect(4),The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP architecture. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipRouteType object.
.1.3.6.1.2.1.4.21.1.9,RFC1213-MIB::ipRouteProto,INTEGER,read-only,,mandatory,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):is-is(9):es-is(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.2.1.4.21.1.10,RFC1213-MIB::ipRouteAge,INTEGER,read-write,,mandatory,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.2.1.4.21.1.11,RFC1213-MIB::ipRouteMask,IpAddress,read-write,,mandatory,,Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of: mask network 255.0.0.0 class-A 255.255.0.0 class-B 255.255.255.0 class-C If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. It should be noted that all IP routing subsystems implicitly use this mechanism.
.1.3.6.1.2.1.4.21.1.12,RFC1213-MIB::ipRouteMetric5,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.21.1.13,RFC1213-MIB::ipRouteInfo,OBJECT,read-only,,mandatory,,A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntatically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
.1.3.6.1.2.1.4.22,RFC1213-MIB::ipNetToMediaTable,,not-accessible,,mandatory,,The IP Address Translation table used for mapping from IP addresses to physical addresses.
.1.3.6.1.2.1.4.22.1,RFC1213-MIB::ipNetToMediaEntry,,not-accessible,ipNetToMediaIfIndex:ipNetToMediaNetAddress,mandatory,,Each entry contains one IpAddress to `physical' address equivalence.
.1.3.6.1.2.1.4.22.1.1,RFC1213-MIB::ipNetToMediaIfIndex,INTEGER,read-write,,mandatory,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.4.22.1.2,RFC1213-MIB::ipNetToMediaPhysAddress,OCTET,read-write,,mandatory,,The media-dependent `physical' address.
.1.3.6.1.2.1.4.22.1.3,RFC1213-MIB::ipNetToMediaNetAddress,IpAddress,read-write,,mandatory,,The IpAddress corresponding to the media- dependent `physical' address.
.1.3.6.1.2.1.4.22.1.4,RFC1213-MIB::ipNetToMediaType,INTEGER,read-write,,mandatory,other(1):invalid(2):dynamic(3):static(4),The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToMediaType object.
.1.3.6.1.2.1.4.23,RFC1213-MIB::ipRoutingDiscards,Counter32,read-only,,mandatory,,The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
.1.3.6.1.2.1.4.24,IP-FORWARD-MIB::ipForward,,,,,,The MIB module for the management of CIDR multipath IP Routes. Copyright (C) The Internet Society (2006). This version of this MIB module is a part of RFC 4292; see the RFC itself for full legal notices.
.1.3.6.1.2.1.4.24.1,IP-FORWARD-MIB::ipForwardNumber,Gauge32,read-only,,obsolete,,The number of current ipForwardTable entries that are not invalid.
.1.3.6.1.2.1.4.24.2,IP-FORWARD-MIB::ipForwardTable,,not-accessible,,obsolete,,This entity's IP Routing table.
.1.3.6.1.2.1.4.24.2.1,IP-FORWARD-MIB::ipForwardEntry,,not-accessible,ipForwardDest:ipForwardProto:ipForwardPolicy:ipForwardNextHop,obsolete,,A particular route to a particular destination, under a particular policy.
.1.3.6.1.2.1.4.24.2.1.1,IP-FORWARD-MIB::ipForwardDest,IpAddress,read-only,,obsolete,,The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. This object may not take a Multicast (Class D) address value. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipForwardMask object is not equal to x.
.1.3.6.1.2.1.4.24.2.1.2,IP-FORWARD-MIB::ipForwardMask,IpAddress,read-create,,obsolete,,Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipForwardDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipForwardMask by reference to the IP Address Class. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipForwardDest object is not equal to ipForwardDest.
.1.3.6.1.2.1.4.24.2.1.3,IP-FORWARD-MIB::ipForwardPolicy,Integer32,read-only,,obsolete,,The general set of conditions that would cause the selection of one multipath route (set of next hops for a given destination) is referred to as 'policy'. Unless the mechanism indicated by ipForwardProto specifies otherwise, the policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30 Protocols defining 'policy' otherwise must either define a set of values that are valid for this object or must implement an integer-instanced policy table for which this object's value acts as an index.
.1.3.6.1.2.1.4.24.2.1.4,IP-FORWARD-MIB::ipForwardNextHop,IpAddress,read-only,,obsolete,,On remote routes, the address of the next system en route; otherwise, 0.0.0.0.
.1.3.6.1.2.1.4.24.2.1.5,IP-FORWARD-MIB::ipForwardIfIndex,Integer32,read-create,,obsolete,,The ifIndex value that identifies the local interface through which the next hop of this route should be reached.
.1.3.6.1.2.1.4.24.2.1.6,IP-FORWARD-MIB::ipForwardType,INTEGER,read-create,,obsolete,other(1):invalid(2):local(3):remote(4),The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destination. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipForwardTable object. That is, it effectively disassociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipForwardType object.
.1.3.6.1.2.1.4.24.2.1.7,IP-FORWARD-MIB::ipForwardProto,INTEGER,read-only,,obsolete,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):is-is(9):es-is(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.2.1.4.24.2.1.8,IP-FORWARD-MIB::ipForwardAge,Integer32,read-only,,obsolete,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.2.1.4.24.2.1.9,IP-FORWARD-MIB::ipForwardInfo,OBJECT,read-create,,obsolete,,A reference to MIB definitions specific to the particular routing protocol that is responsible for this route, as determined by the value specified in the route's ipForwardProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any implementation conforming to ASN.1 and the Basic Encoding Rules must be able to generate and recognize this value.
.1.3.6.1.2.1.4.24.2.1.10,IP-FORWARD-MIB::ipForwardNextHopAS,Integer32,read-create,,obsolete,,The Autonomous System Number of the Next Hop. When this is unknown or not relevant to the protocol indicated by ipForwardProto, zero.
.1.3.6.1.2.1.4.24.2.1.11,IP-FORWARD-MIB::ipForwardMetric1,Integer32,read-create,,obsolete,,The primary routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.2.1.12,IP-FORWARD-MIB::ipForwardMetric2,Integer32,read-create,,obsolete,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.2.1.13,IP-FORWARD-MIB::ipForwardMetric3,Integer32,read-create,,obsolete,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.2.1.14,IP-FORWARD-MIB::ipForwardMetric4,Integer32,read-create,,obsolete,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.2.1.15,IP-FORWARD-MIB::ipForwardMetric5,Integer32,read-create,,obsolete,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.3,IP-FORWARD-MIB::ipCidrRouteNumber,Gauge32,read-only,,deprecated,,The number of current ipCidrRouteTable entries that are not invalid. This object is deprecated in favor of inetCidrRouteNumber and the inetCidrRouteTable.
.1.3.6.1.2.1.4.24.4,IP-FORWARD-MIB::ipCidrRouteTable,,not-accessible,,deprecated,,This entity's IP Routing table. This table has been deprecated in favor of the IP version neutral inetCidrRouteTable.
.1.3.6.1.2.1.4.24.4.1,IP-FORWARD-MIB::ipCidrRouteEntry,,not-accessible,ipCidrRouteDest:ipCidrRouteMask:ipCidrRouteTos:ipCidrRouteNextHop,deprecated,,A particular route to a particular destination, under a particular policy.
.1.3.6.1.2.1.4.24.4.1.1,IP-FORWARD-MIB::ipCidrRouteDest,IpAddress,read-only,,deprecated,,The destination IP address of this route. This object may not take a Multicast (Class D) address value. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipCidrRouteMask object is not equal to x.
.1.3.6.1.2.1.4.24.4.1.2,IP-FORWARD-MIB::ipCidrRouteMask,IpAddress,read-only,,deprecated,,Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipCidrRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipCidrRouteMask by reference to the IP Address Class. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipCidrRouteDest object is not equal to ipCidrRouteDest.
.1.3.6.1.2.1.4.24.4.1.3,IP-FORWARD-MIB::ipCidrRouteTos,Integer32,read-only,,deprecated,,The policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 0 0 1 0 ==> 4 0 0 1 1 ==> 6 0 1 0 0 ==> 8 0 1 0 1 ==> 10 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1 1 1 0 ==> 28 1 1 1 1 ==> 30
.1.3.6.1.2.1.4.24.4.1.4,IP-FORWARD-MIB::ipCidrRouteNextHop,IpAddress,read-only,,deprecated,,On remote routes, the address of the next system en route; Otherwise, 0.0.0.0.
.1.3.6.1.2.1.4.24.4.1.5,IP-FORWARD-MIB::ipCidrRouteIfIndex,Integer32,read-create,,deprecated,,The ifIndex value that identifies the local interface through which the next hop of this route should be reached.
.1.3.6.1.2.1.4.24.4.1.6,IP-FORWARD-MIB::ipCidrRouteType,INTEGER,read-create,,deprecated,other(1):reject(2):local(3):remote(4),The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destination. Routes that do not result in traffic forwarding or rejection should not be displayed, even if the implementation keeps them stored internally. reject (2) refers to a route that, if matched, discards the message as unreachable. This is used in some protocols as a means of correctly aggregating routes.
.1.3.6.1.2.1.4.24.4.1.7,IP-FORWARD-MIB::ipCidrRouteProto,INTEGER,read-only,,deprecated,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.2.1.4.24.4.1.8,IP-FORWARD-MIB::ipCidrRouteAge,Integer32,read-only,,deprecated,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied, except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.2.1.4.24.4.1.9,IP-FORWARD-MIB::ipCidrRouteInfo,OBJECT,read-create,,deprecated,,A reference to MIB definitions specific to the particular routing protocol that is responsible for this route, as determined by the value specified in the route's ipCidrRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntactically valid object identifier, and any implementation conforming to ASN.1 and the Basic Encoding Rules must be able to generate and recognize this value.
.1.3.6.1.2.1.4.24.4.1.10,IP-FORWARD-MIB::ipCidrRouteNextHopAS,Integer32,read-create,,deprecated,,The Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing- protocol specified in the route's ipCidrRouteProto value. When this object is unknown or not relevant, its value should be set to zero.
.1.3.6.1.2.1.4.24.4.1.11,IP-FORWARD-MIB::ipCidrRouteMetric1,Integer32,read-create,,deprecated,,The primary routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.4.1.12,IP-FORWARD-MIB::ipCidrRouteMetric2,Integer32,read-create,,deprecated,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.4.1.13,IP-FORWARD-MIB::ipCidrRouteMetric3,Integer32,read-create,,deprecated,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.4.1.14,IP-FORWARD-MIB::ipCidrRouteMetric4,Integer32,read-create,,deprecated,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.4.1.15,IP-FORWARD-MIB::ipCidrRouteMetric5,Integer32,read-create,,deprecated,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.4.1.16,IP-FORWARD-MIB::ipCidrRouteStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to row installation and removal conventions.
.1.3.6.1.2.1.4.24.5,IP-FORWARD-MIB::ipForwardConformance,,,,,,
.1.3.6.1.2.1.4.24.5.1,IP-FORWARD-MIB::ipForwardGroups,,,,,,
.1.3.6.1.2.1.4.24.5.1.2,IP-FORWARD-MIB::ipForwardMultiPathGroup,,,,,,IP Multipath Route Table.
.1.3.6.1.2.1.4.24.5.1.3,IP-FORWARD-MIB::ipForwardCidrRouteGroup,,,,,,The CIDR Route Table. This group has been deprecated and replaced with inetForwardCidrRouteGroup.
.1.3.6.1.2.1.4.24.5.1.4,IP-FORWARD-MIB::inetForwardCidrRouteGroup,,,,,,The IP version-independent CIDR Route Table.
.1.3.6.1.2.1.4.24.5.2,IP-FORWARD-MIB::ipForwardCompliances,,,,,,
.1.3.6.1.2.1.4.24.5.2.1,IP-FORWARD-MIB::ipForwardCompliance,,,,,,The compliance statement for SNMPv2 entities that implement the ipForward MIB. This compliance statement has been deprecated and replaced with ipForwardFullCompliance and ipForwardReadOnlyCompliance.
.1.3.6.1.2.1.4.24.5.2.2,IP-FORWARD-MIB::ipForwardOldCompliance,,,,,,The compliance statement for SNMP entities that implement the ipForward MIB.
.1.3.6.1.2.1.4.24.5.2.3,IP-FORWARD-MIB::ipForwardFullCompliance,,,,,,When this MIB is implemented for read-create, the implementation can claim full compliance. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT inetCidrRouteDestType -- SYNTAX InetAddressType (ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)) -- DESCRIPTION -- This MIB requires support for global and -- non-global ipv4 and ipv6 addresses. -- -- OBJECT inetCidrRouteDest -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for global and -- non-global IPv4 and IPv6 addresses. -- -- OBJECT inetCidrRouteNextHopType -- SYNTAX InetAddressType (unknown(0), ipv4(1), -- ipv6(2), ipv4z(3) -- ipv6z(4)) -- DESCRIPTION -- This MIB requires support for global and -- non-global ipv4 and ipv6 addresses. -- -- OBJECT inetCidrRouteNextHop -- SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for global and -- non-global IPv4 and IPv6 addresses. 
.1.3.6.1.2.1.4.24.5.2.4,IP-FORWARD-MIB::ipForwardReadOnlyCompliance,,,,,,When this MIB is implemented without support for read- create (i.e., in read-only mode), the implementation can claim read-only compliance.
.1.3.6.1.2.1.4.24.6,IP-FORWARD-MIB::inetCidrRouteNumber,Gauge32,read-only,,current,,The number of current inetCidrRouteTable entries that are not invalid.
.1.3.6.1.2.1.4.24.7,IP-FORWARD-MIB::inetCidrRouteTable,,not-accessible,,current,,This entity's IP Routing table.
.1.3.6.1.2.1.4.24.7.1,IP-FORWARD-MIB::inetCidrRouteEntry,,not-accessible,inetCidrRouteDestType:inetCidrRouteDest:inetCidrRoutePfxLen:inetCidrRoutePolicy:inetCidrRouteNextHopType:inetCidrRouteNextHop,current,,A particular route to a particular destination, under a particular policy (as reflected in the inetCidrRoutePolicy object). Dynamically created rows will survive an agent reboot. Implementers need to be aware that if the total number of elements (octets or sub-identifiers) in inetCidrRouteDest, inetCidrRoutePolicy, and inetCidrRouteNextHop exceeds 111, then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.4.24.7.1.1,IP-FORWARD-MIB::inetCidrRouteDestType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the inetCidrRouteDest address, as defined in the InetAddress MIB. Only those address types that may appear in an actual routing table are allowed as values of this object.
.1.3.6.1.2.1.4.24.7.1.2,IP-FORWARD-MIB::inetCidrRouteDest,OCTET,not-accessible,,current,,The destination IP address of this route. The type of this address is determined by the value of the inetCidrRouteDestType object. The values for the index objects inetCidrRouteDest and inetCidrRoutePfxLen must be consistent. When the value of inetCidrRouteDest (excluding the zone index, if one is present) is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object inetCidrRoutePfxLen MUST be equal to x. If not, then the index pair is not consistent and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.4.24.7.1.3,IP-FORWARD-MIB::inetCidrRoutePfxLen,Unsigned32,not-accessible,,current,,Indicates the number of leading one bits that form the mask to be logical-ANDed with the destination address before being compared to the value in the inetCidrRouteDest field. The values for the index objects inetCidrRouteDest and inetCidrRoutePfxLen must be consistent. When the value of inetCidrRouteDest (excluding the zone index, if one is present) is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object inetCidrRoutePfxLen MUST be equal to x. If not, then the index pair is not consistent and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.4.24.7.1.4,IP-FORWARD-MIB::inetCidrRoutePolicy,OBJECT,not-accessible,,current,,This object is an opaque object without any defined semantics. Its purpose is to serve as an additional index that may delineate between multiple entries to the same destination. The value { 0 0 } shall be used as the default value for this object.
.1.3.6.1.2.1.4.24.7.1.5,IP-FORWARD-MIB::inetCidrRouteNextHopType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the inetCidrRouteNextHop address, as defined in the InetAddress MIB. Value should be set to unknown(0) for non-remote routes. Only those address types that may appear in an actual routing table are allowed as values of this object.
.1.3.6.1.2.1.4.24.7.1.6,IP-FORWARD-MIB::inetCidrRouteNextHop,OCTET,not-accessible,,current,,On remote routes, the address of the next system en route. For non-remote routes, a zero length string. The type of this address is determined by the value of the inetCidrRouteNextHopType object.
.1.3.6.1.2.1.4.24.7.1.7,IP-FORWARD-MIB::inetCidrRouteIfIndex,Integer32,read-create,,current,,The ifIndex value that identifies the local interface through which the next hop of this route should be reached. A value of 0 is valid and represents the scenario where no interface is specified.
.1.3.6.1.2.1.4.24.7.1.8,IP-FORWARD-MIB::inetCidrRouteType,INTEGER,read-create,,current,other(1):reject(2):local(3):remote(4):blackhole(5),The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destination. Routes that do not result in traffic forwarding or rejection should not be displayed, even if the implementation keeps them stored internally. reject(2) refers to a route that, if matched, discards the message as unreachable and returns a notification (e.g., ICMP error) to the message sender. This is used in some protocols as a means of correctly aggregating routes. blackhole(5) refers to a route that, if matched, discards the message silently.
.1.3.6.1.2.1.4.24.7.1.9,IP-FORWARD-MIB::inetCidrRouteProto,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.2.1.4.24.7.1.10,IP-FORWARD-MIB::inetCidrRouteAge,Gauge32,read-only,,current,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of 'too old' can be implied, except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.2.1.4.24.7.1.11,IP-FORWARD-MIB::inetCidrRouteNextHopAS,Unsigned32,read-create,,current,,The Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing- protocol specified in the route's inetCidrRouteProto value. When this object is unknown or not relevant, its value should be set to zero.
.1.3.6.1.2.1.4.24.7.1.12,IP-FORWARD-MIB::inetCidrRouteMetric1,Integer32,read-create,,current,,The primary routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.7.1.13,IP-FORWARD-MIB::inetCidrRouteMetric2,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.7.1.14,IP-FORWARD-MIB::inetCidrRouteMetric3,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.7.1.15,IP-FORWARD-MIB::inetCidrRouteMetric4,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.7.1.16,IP-FORWARD-MIB::inetCidrRouteMetric5,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.4.24.7.1.17,IP-FORWARD-MIB::inetCidrRouteStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to row installation and removal conventions. A row entry cannot be modified when the status is marked as active(1).
.1.3.6.1.2.1.4.24.8,IP-FORWARD-MIB::inetCidrRouteDiscards,Counter32,read-only,,current,,The number of valid route entries discarded from the inetCidrRouteTable. Discarded route entries do not appear in the inetCidrRouteTable. One possible reason for discarding an entry would be to free-up buffer space for other route table entries.
.1.3.6.1.2.1.4.25,IP-MIB::ipv6IpForwarding,INTEGER,read-write,,current,forwarding(1):notForwarding(2),The indication of whether this entity is acting as an IPv6 router on any interface in respect to the forwarding of datagrams received by, but not addressed to, this entity. IPv6 routers forward datagrams. IPv6 hosts do not (except those source-routed via the host). When this object is written, the entity SHOULD save the change to non-volatile storage and restore the object from non-volatile storage upon re-initialization of the system.
.1.3.6.1.2.1.4.26,IP-MIB::ipv6IpDefaultHopLimit,Integer32,read-write,,current,,The default value inserted into the Hop Limit field of the IPv6 header of datagrams originated at this entity whenever a Hop Limit value is not supplied by the transport layer protocol. When this object is written, the entity SHOULD save the change to non-volatile storage and restore the object from non-volatile storage upon re-initialization of the system.
.1.3.6.1.2.1.4.27,IP-MIB::ipv4InterfaceTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which a row in the ipv4InterfaceTable was added or deleted, or when an ipv4InterfaceReasmMaxSize or an ipv4InterfaceEnableStatus object was modified. If new objects are added to the ipv4InterfaceTable that require the ipv4InterfaceTableLastChange to be updated when they are modified, they must specify that requirement in their description clause.
.1.3.6.1.2.1.4.28,IP-MIB::ipv4InterfaceTable,,not-accessible,,current,,The table containing per-interface IPv4-specific information.
.1.3.6.1.2.1.4.28.1,IP-MIB::ipv4InterfaceEntry,,not-accessible,ipv4InterfaceIfIndex,current,,An entry containing IPv4-specific information for a specific interface.
.1.3.6.1.2.1.4.28.1.1,IP-MIB::ipv4InterfaceIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.28.1.2,IP-MIB::ipv4InterfaceReasmMaxSize,Integer32,read-only,,current,,The size of the largest IPv4 datagram that this entity can re-assemble from incoming IPv4 fragmented datagrams received on this interface.
.1.3.6.1.2.1.4.28.1.3,IP-MIB::ipv4InterfaceEnableStatus,INTEGER,read-write,,current,up(1):down(2),The indication of whether IPv4 is enabled (up) or disabled (down) on this interface. This object does not affect the state of the interface itself, only its connection to an IPv4 stack. The IF-MIB should be used to control the state of the interface.
.1.3.6.1.2.1.4.28.1.4,IP-MIB::ipv4InterfaceRetransmitTime,Unsigned32,read-only,,current,,The time between retransmissions of ARP requests to a neighbor when resolving the address or when probing the reachability of a neighbor.
.1.3.6.1.2.1.4.29,IP-MIB::ipv6InterfaceTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which a row in the ipv6InterfaceTable was added or deleted or when an ipv6InterfaceReasmMaxSize, ipv6InterfaceIdentifier, ipv6InterfaceEnableStatus, ipv6InterfaceReachableTime, ipv6InterfaceRetransmitTime, or ipv6InterfaceForwarding object was modified. If new objects are added to the ipv6InterfaceTable that require the ipv6InterfaceTableLastChange to be updated when they are modified, they must specify that requirement in their description clause.
.1.3.6.1.2.1.4.30,IP-MIB::ipv6InterfaceTable,,not-accessible,,current,,The table containing per-interface IPv6-specific information.
.1.3.6.1.2.1.4.30.1,IP-MIB::ipv6InterfaceEntry,,not-accessible,ipv6InterfaceIfIndex,current,,An entry containing IPv6-specific information for a given interface.
.1.3.6.1.2.1.4.30.1.1,IP-MIB::ipv6InterfaceIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.30.1.2,IP-MIB::ipv6InterfaceReasmMaxSize,Unsigned32,read-only,,current,,The size of the largest IPv6 datagram that this entity can re-assemble from incoming IPv6 fragmented datagrams received on this interface.
.1.3.6.1.2.1.4.30.1.3,IP-MIB::ipv6InterfaceIdentifier,OCTET,read-only,,current,,The Interface Identifier for this interface. The Interface Identifier is combined with an address prefix to form an interface address. By default, the Interface Identifier is auto-configured according to the rules of the link type to which this interface is attached. A zero length identifier may be used where appropriate. One possible example is a loopback interface.
.1.3.6.1.2.1.4.30.1.5,IP-MIB::ipv6InterfaceEnableStatus,INTEGER,read-write,,current,up(1):down(2),The indication of whether IPv6 is enabled (up) or disabled (down) on this interface. This object does not affect the state of the interface itself, only its connection to an IPv6 stack. The IF-MIB should be used to control the state of the interface. When this object is written, the entity SHOULD save the change to non-volatile storage and restore the object from non-volatile storage upon re-initialization of the system.
.1.3.6.1.2.1.4.30.1.6,IP-MIB::ipv6InterfaceReachableTime,Unsigned32,read-only,,current,,The time a neighbor is considered reachable after receiving a reachability confirmation.
.1.3.6.1.2.1.4.30.1.7,IP-MIB::ipv6InterfaceRetransmitTime,Unsigned32,read-only,,current,,The time between retransmissions of Neighbor Solicitation messages to a neighbor when resolving the address or when probing the reachability of a neighbor.
.1.3.6.1.2.1.4.30.1.8,IP-MIB::ipv6InterfaceForwarding,INTEGER,read-write,,current,forwarding(1):notForwarding(2),The indication of whether this entity is acting as an IPv6 router on this interface with respect to the forwarding of datagrams received by, but not addressed to, this entity. IPv6 routers forward datagrams. IPv6 hosts do not (except those source-routed via the host). This object is constrained by ipv6IpForwarding and is ignored if ipv6IpForwarding is set to notForwarding. Those systems that do not provide per-interface control of the forwarding function should set this object to forwarding for all interfaces and allow the ipv6IpForwarding object to control the forwarding capability. When this object is written, the entity SHOULD save the change to non-volatile storage and restore the object from non-volatile storage upon re-initialization of the system.
.1.3.6.1.2.1.4.31,IP-MIB::ipTrafficStats,,,,,,
.1.3.6.1.2.1.4.31.1,IP-MIB::ipSystemStatsTable,,not-accessible,,current,,The table containing system wide, IP version specific traffic statistics. This table and the ipIfStatsTable contain similar objects whose difference is in their granularity. Where this table contains system wide traffic statistics, the ipIfStatsTable contains the same statistics but counted on a per-interface basis.
.1.3.6.1.2.1.4.31.1.1,IP-MIB::ipSystemStatsEntry,,not-accessible,ipSystemStatsIPVersion,current,,A statistics entry containing system-wide objects for a particular IP version.
.1.3.6.1.2.1.4.31.1.1.1,IP-MIB::ipSystemStatsIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version of this row.
.1.3.6.1.2.1.4.31.1.1.3,IP-MIB::ipSystemStatsInReceives,Counter32,read-only,,current,,The total number of input IP datagrams received, including those received in error. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.4,IP-MIB::ipSystemStatsHCInReceives,Counter64,read-only,,current,,The total number of input IP datagrams received, including those received in error. This object counts the same datagrams as ipSystemStatsInReceives, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.5,IP-MIB::ipSystemStatsInOctets,Counter32,read-only,,current,,The total number of octets received in input IP datagrams, including those received in error. Octets from datagrams counted in ipSystemStatsInReceives MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.6,IP-MIB::ipSystemStatsHCInOctets,Counter64,read-only,,current,,The total number of octets received in input IP datagrams, including those received in error. This object counts the same octets as ipSystemStatsInOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.7,IP-MIB::ipSystemStatsInHdrErrors,Counter32,read-only,,current,,The number of input IP datagrams discarded due to errors in their IP headers, including version number mismatch, other format errors, hop count exceeded, errors discovered in processing their IP options, etc. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.8,IP-MIB::ipSystemStatsInNoRoutes,Counter32,read-only,,current,,The number of input IP datagrams discarded because no route could be found to transmit them to their destination. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.9,IP-MIB::ipSystemStatsInAddrErrors,Counter32,read-only,,current,,The number of input IP datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., ::0). For entities that are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.10,IP-MIB::ipSystemStatsInUnknownProtos,Counter32,read-only,,current,,The number of locally-addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol. When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.11,IP-MIB::ipSystemStatsInTruncatedPkts,Counter32,read-only,,current,,The number of input IP datagrams discarded because the datagram frame didn't carry enough data. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.12,IP-MIB::ipSystemStatsInForwDatagrams,Counter32,read-only,,current,,The number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to forward them to that final destination. In entities that do not act as IP routers, this counter will include only those datagrams that were Source-Routed via this entity, and the Source-Route processing was successful. When tracking interface statistics, the counter of the incoming interface is incremented for each datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.13,IP-MIB::ipSystemStatsHCInForwDatagrams,Counter64,read-only,,current,,The number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to forward them to that final destination. This object counts the same packets as ipSystemStatsInForwDatagrams, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.14,IP-MIB::ipSystemStatsReasmReqds,Counter32,read-only,,current,,The number of IP fragments received that needed to be reassembled at this interface. When tracking interface statistics, the counter of the interface to which these fragments were addressed is incremented. This interface might not be the same as the input interface for some of the fragments. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.15,IP-MIB::ipSystemStatsReasmOKs,Counter32,read-only,,current,,The number of IP datagrams successfully reassembled. When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.16,IP-MIB::ipSystemStatsReasmFails,Counter32,read-only,,current,,The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. When tracking interface statistics, the counter of the interface to which these fragments were addressed is incremented. This interface might not be the same as the input interface for some of the fragments. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.17,IP-MIB::ipSystemStatsInDiscards,Counter32,read-only,,current,,The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.18,IP-MIB::ipSystemStatsInDelivers,Counter32,read-only,,current,,The total number of datagrams successfully delivered to IP user-protocols (including ICMP). When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.19,IP-MIB::ipSystemStatsHCInDelivers,Counter64,read-only,,current,,The total number of datagrams successfully delivered to IP user-protocols (including ICMP). This object counts the same packets as ipSystemStatsInDelivers, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.20,IP-MIB::ipSystemStatsOutRequests,Counter32,read-only,,current,,The total number of IP datagrams that local IP user- protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipSystemStatsOutForwDatagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.21,IP-MIB::ipSystemStatsHCOutRequests,Counter64,read-only,,current,,The total number of IP datagrams that local IP user- protocols (including ICMP) supplied to IP in requests for transmission. This object counts the same packets as ipSystemStatsOutRequests, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.22,IP-MIB::ipSystemStatsOutNoRoutes,Counter32,read-only,,current,,The number of locally generated IP datagrams discarded because no route could be found to transmit them to their destination. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.23,IP-MIB::ipSystemStatsOutForwDatagrams,Counter32,read-only,,current,,The number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path to their final destination. In entities that do not act as IP routers, this counter will include only those datagrams that were Source-Routed via this entity, and the Source-Route processing was successful. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully forwarded datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.24,IP-MIB::ipSystemStatsHCOutForwDatagrams,Counter64,read-only,,current,,The number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path to their final destination. This object counts the same packets as ipSystemStatsOutForwDatagrams, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.25,IP-MIB::ipSystemStatsOutDiscards,Counter32,read-only,,current,,The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipSystemStatsOutForwDatagrams if any such datagrams met this (discretionary) discard criterion. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.26,IP-MIB::ipSystemStatsOutFragReqds,Counter32,read-only,,current,,The number of IP datagrams that would require fragmentation in order to be transmitted. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.27,IP-MIB::ipSystemStatsOutFragOKs,Counter32,read-only,,current,,The number of IP datagrams that have been successfully fragmented. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.28,IP-MIB::ipSystemStatsOutFragFails,Counter32,read-only,,current,,The number of IP datagrams that have been discarded because they needed to be fragmented but could not be. This includes IPv4 packets that have the DF bit set and IPv6 packets that are being forwarded and exceed the outgoing link MTU. When tracking interface statistics, the counter of the outgoing interface is incremented for an unsuccessfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.29,IP-MIB::ipSystemStatsOutFragCreates,Counter32,read-only,,current,,The number of output datagram fragments that have been generated as a result of IP fragmentation. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.30,IP-MIB::ipSystemStatsOutTransmits,Counter32,read-only,,current,,The total number of IP datagrams that this entity supplied to the lower layers for transmission. This includes datagrams generated locally and those forwarded by this entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.31,IP-MIB::ipSystemStatsHCOutTransmits,Counter64,read-only,,current,,The total number of IP datagrams that this entity supplied to the lower layers for transmission. This object counts the same datagrams as ipSystemStatsOutTransmits, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.32,IP-MIB::ipSystemStatsOutOctets,Counter32,read-only,,current,,The total number of octets in IP datagrams delivered to the lower layers for transmission. Octets from datagrams counted in ipSystemStatsOutTransmits MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.33,IP-MIB::ipSystemStatsHCOutOctets,Counter64,read-only,,current,,The total number of octets in IP datagrams delivered to the lower layers for transmission. This objects counts the same octets as ipSystemStatsOutOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.34,IP-MIB::ipSystemStatsInMcastPkts,Counter32,read-only,,current,,The number of IP multicast datagrams received. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.35,IP-MIB::ipSystemStatsHCInMcastPkts,Counter64,read-only,,current,,The number of IP multicast datagrams received. This object counts the same datagrams as ipSystemStatsInMcastPkts but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.36,IP-MIB::ipSystemStatsInMcastOctets,Counter32,read-only,,current,,The total number of octets received in IP multicast datagrams. Octets from datagrams counted in ipSystemStatsInMcastPkts MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.37,IP-MIB::ipSystemStatsHCInMcastOctets,Counter64,read-only,,current,,The total number of octets received in IP multicast datagrams. This object counts the same octets as ipSystemStatsInMcastOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.38,IP-MIB::ipSystemStatsOutMcastPkts,Counter32,read-only,,current,,The number of IP multicast datagrams transmitted. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.39,IP-MIB::ipSystemStatsHCOutMcastPkts,Counter64,read-only,,current,,The number of IP multicast datagrams transmitted. This object counts the same datagrams as ipSystemStatsOutMcastPkts, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.40,IP-MIB::ipSystemStatsOutMcastOctets,Counter32,read-only,,current,,The total number of octets transmitted in IP multicast datagrams. Octets from datagrams counted in ipSystemStatsOutMcastPkts MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.41,IP-MIB::ipSystemStatsHCOutMcastOctets,Counter64,read-only,,current,,The total number of octets transmitted in IP multicast datagrams. This object counts the same octets as ipSystemStatsOutMcastOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.42,IP-MIB::ipSystemStatsInBcastPkts,Counter32,read-only,,current,,The number of IP broadcast datagrams received. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.43,IP-MIB::ipSystemStatsHCInBcastPkts,Counter64,read-only,,current,,The number of IP broadcast datagrams received. This object counts the same datagrams as ipSystemStatsInBcastPkts but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.44,IP-MIB::ipSystemStatsOutBcastPkts,Counter32,read-only,,current,,The number of IP broadcast datagrams transmitted. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.45,IP-MIB::ipSystemStatsHCOutBcastPkts,Counter64,read-only,,current,,The number of IP broadcast datagrams transmitted. This object counts the same datagrams as ipSystemStatsOutBcastPkts, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipSystemStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.1.1.46,IP-MIB::ipSystemStatsDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.4.31.1.1.47,IP-MIB::ipSystemStatsRefreshRate,Unsigned32,read-only,,current,,The minimum reasonable polling interval for this entry. This object provides an indication of the minimum amount of time required to update the counters in this entry.
.1.3.6.1.2.1.4.31.2,IP-MIB::ipIfStatsTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which a row in the ipIfStatsTable was added or deleted. If new objects are added to the ipIfStatsTable that require the ipIfStatsTableLastChange to be updated when they are modified, they must specify that requirement in their description clause.
.1.3.6.1.2.1.4.31.3,IP-MIB::ipIfStatsTable,,not-accessible,,current,,The table containing per-interface traffic statistics. This table and the ipSystemStatsTable contain similar objects whose difference is in their granularity. Where this table contains per-interface statistics, the ipSystemStatsTable contains the same statistics, but counted on a system wide basis.
.1.3.6.1.2.1.4.31.3.1,IP-MIB::ipIfStatsEntry,,not-accessible,ipIfStatsIPVersion:ipIfStatsIfIndex,current,,An interface statistics entry containing objects for a particular interface and version of IP.
.1.3.6.1.2.1.4.31.3.1.1,IP-MIB::ipIfStatsIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version of this row.
.1.3.6.1.2.1.4.31.3.1.2,IP-MIB::ipIfStatsIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.31.3.1.3,IP-MIB::ipIfStatsInReceives,Counter32,read-only,,current,,The total number of input IP datagrams received, including those received in error. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.4,IP-MIB::ipIfStatsHCInReceives,Counter64,read-only,,current,,The total number of input IP datagrams received, including those received in error. This object counts the same datagrams as ipIfStatsInReceives, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.5,IP-MIB::ipIfStatsInOctets,Counter32,read-only,,current,,The total number of octets received in input IP datagrams, including those received in error. Octets from datagrams counted in ipIfStatsInReceives MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.6,IP-MIB::ipIfStatsHCInOctets,Counter64,read-only,,current,,The total number of octets received in input IP datagrams, including those received in error. This object counts the same octets as ipIfStatsInOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.7,IP-MIB::ipIfStatsInHdrErrors,Counter32,read-only,,current,,The number of input IP datagrams discarded due to errors in their IP headers, including version number mismatch, other format errors, hop count exceeded, errors discovered in processing their IP options, etc. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.8,IP-MIB::ipIfStatsInNoRoutes,Counter32,read-only,,current,,The number of input IP datagrams discarded because no route could be found to transmit them to their destination. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.9,IP-MIB::ipIfStatsInAddrErrors,Counter32,read-only,,current,,The number of input IP datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., ::0). For entities that are not IP routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.10,IP-MIB::ipIfStatsInUnknownProtos,Counter32,read-only,,current,,The number of locally-addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol. When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.11,IP-MIB::ipIfStatsInTruncatedPkts,Counter32,read-only,,current,,The number of input IP datagrams discarded because the datagram frame didn't carry enough data. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.12,IP-MIB::ipIfStatsInForwDatagrams,Counter32,read-only,,current,,The number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to forward them to that final destination. In entities that do not act as IP routers, this counter will include only those datagrams that were Source-Routed via this entity, and the Source-Route processing was successful. When tracking interface statistics, the counter of the incoming interface is incremented for each datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.13,IP-MIB::ipIfStatsHCInForwDatagrams,Counter64,read-only,,current,,The number of input datagrams for which this entity was not their final IP destination and for which this entity attempted to find a route to forward them to that final destination. This object counts the same packets as ipIfStatsInForwDatagrams, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.14,IP-MIB::ipIfStatsReasmReqds,Counter32,read-only,,current,,The number of IP fragments received that needed to be reassembled at this interface. When tracking interface statistics, the counter of the interface to which these fragments were addressed is incremented. This interface might not be the same as the input interface for some of the fragments. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.15,IP-MIB::ipIfStatsReasmOKs,Counter32,read-only,,current,,The number of IP datagrams successfully reassembled. When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.16,IP-MIB::ipIfStatsReasmFails,Counter32,read-only,,current,,The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. When tracking interface statistics, the counter of the interface to which these fragments were addressed is incremented. This interface might not be the same as the input interface for some of the fragments. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.17,IP-MIB::ipIfStatsInDiscards,Counter32,read-only,,current,,The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.18,IP-MIB::ipIfStatsInDelivers,Counter32,read-only,,current,,The total number of datagrams successfully delivered to IP user-protocols (including ICMP). When tracking interface statistics, the counter of the interface to which these datagrams were addressed is incremented. This interface might not be the same as the input interface for some of the datagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.19,IP-MIB::ipIfStatsHCInDelivers,Counter64,read-only,,current,,The total number of datagrams successfully delivered to IP user-protocols (including ICMP). This object counts the same packets as ipIfStatsInDelivers, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.20,IP-MIB::ipIfStatsOutRequests,Counter32,read-only,,current,,The total number of IP datagrams that local IP user- protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipIfStatsOutForwDatagrams. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.21,IP-MIB::ipIfStatsHCOutRequests,Counter64,read-only,,current,,The total number of IP datagrams that local IP user- protocols (including ICMP) supplied to IP in requests for transmission. This object counts the same packets as ipIfStatsOutRequests, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.23,IP-MIB::ipIfStatsOutForwDatagrams,Counter32,read-only,,current,,The number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path to their final destination. In entities that do not act as IP routers, this counter will include only those datagrams that were Source-Routed via this entity, and the Source-Route processing was successful. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully forwarded datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.24,IP-MIB::ipIfStatsHCOutForwDatagrams,Counter64,read-only,,current,,The number of datagrams for which this entity was not their final IP destination and for which it was successful in finding a path to their final destination. This object counts the same packets as ipIfStatsOutForwDatagrams, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.25,IP-MIB::ipIfStatsOutDiscards,Counter32,read-only,,current,,The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipIfStatsOutForwDatagrams if any such datagrams met this (discretionary) discard criterion. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.26,IP-MIB::ipIfStatsOutFragReqds,Counter32,read-only,,current,,The number of IP datagrams that would require fragmentation in order to be transmitted. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.27,IP-MIB::ipIfStatsOutFragOKs,Counter32,read-only,,current,,The number of IP datagrams that have been successfully fragmented. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.28,IP-MIB::ipIfStatsOutFragFails,Counter32,read-only,,current,,The number of IP datagrams that have been discarded because they needed to be fragmented but could not be. This includes IPv4 packets that have the DF bit set and IPv6 packets that are being forwarded and exceed the outgoing link MTU. When tracking interface statistics, the counter of the outgoing interface is incremented for an unsuccessfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.29,IP-MIB::ipIfStatsOutFragCreates,Counter32,read-only,,current,,The number of output datagram fragments that have been generated as a result of IP fragmentation. When tracking interface statistics, the counter of the outgoing interface is incremented for a successfully fragmented datagram. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.30,IP-MIB::ipIfStatsOutTransmits,Counter32,read-only,,current,,The total number of IP datagrams that this entity supplied to the lower layers for transmission. This includes datagrams generated locally and those forwarded by this entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.31,IP-MIB::ipIfStatsHCOutTransmits,Counter64,read-only,,current,,The total number of IP datagrams that this entity supplied to the lower layers for transmission. This object counts the same datagrams as ipIfStatsOutTransmits, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.32,IP-MIB::ipIfStatsOutOctets,Counter32,read-only,,current,,The total number of octets in IP datagrams delivered to the lower layers for transmission. Octets from datagrams counted in ipIfStatsOutTransmits MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.33,IP-MIB::ipIfStatsHCOutOctets,Counter64,read-only,,current,,The total number of octets in IP datagrams delivered to the lower layers for transmission. This objects counts the same octets as ipIfStatsOutOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.34,IP-MIB::ipIfStatsInMcastPkts,Counter32,read-only,,current,,The number of IP multicast datagrams received. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.35,IP-MIB::ipIfStatsHCInMcastPkts,Counter64,read-only,,current,,The number of IP multicast datagrams received. This object counts the same datagrams as ipIfStatsInMcastPkts, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.36,IP-MIB::ipIfStatsInMcastOctets,Counter32,read-only,,current,,The total number of octets received in IP multicast datagrams. Octets from datagrams counted in ipIfStatsInMcastPkts MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.37,IP-MIB::ipIfStatsHCInMcastOctets,Counter64,read-only,,current,,The total number of octets received in IP multicast datagrams. This object counts the same octets as ipIfStatsInMcastOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.38,IP-MIB::ipIfStatsOutMcastPkts,Counter32,read-only,,current,,The number of IP multicast datagrams transmitted. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.39,IP-MIB::ipIfStatsHCOutMcastPkts,Counter64,read-only,,current,,The number of IP multicast datagrams transmitted. This object counts the same datagrams as ipIfStatsOutMcastPkts, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.40,IP-MIB::ipIfStatsOutMcastOctets,Counter32,read-only,,current,,The total number of octets transmitted in IP multicast datagrams. Octets from datagrams counted in ipIfStatsOutMcastPkts MUST be counted here. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.41,IP-MIB::ipIfStatsHCOutMcastOctets,Counter64,read-only,,current,,The total number of octets transmitted in IP multicast datagrams. This object counts the same octets as ipIfStatsOutMcastOctets, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.42,IP-MIB::ipIfStatsInBcastPkts,Counter32,read-only,,current,,The number of IP broadcast datagrams received. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.43,IP-MIB::ipIfStatsHCInBcastPkts,Counter64,read-only,,current,,The number of IP broadcast datagrams received. This object counts the same datagrams as ipIfStatsInBcastPkts, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.44,IP-MIB::ipIfStatsOutBcastPkts,Counter32,read-only,,current,,The number of IP broadcast datagrams transmitted. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.45,IP-MIB::ipIfStatsHCOutBcastPkts,Counter64,read-only,,current,,The number of IP broadcast datagrams transmitted. This object counts the same datagrams as ipIfStatsOutBcastPkts, but allows for larger values. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ipIfStatsDiscontinuityTime.
.1.3.6.1.2.1.4.31.3.1.46,IP-MIB::ipIfStatsDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.4.31.3.1.47,IP-MIB::ipIfStatsRefreshRate,Unsigned32,read-only,,current,,The minimum reasonable polling interval for this entry. This object provides an indication of the minimum amount of time required to update the counters in this entry.
.1.3.6.1.2.1.4.32,IP-MIB::ipAddressPrefixTable,,not-accessible,,current,,This table allows the user to determine the source of an IP address or set of IP addresses, and allows other tables to share the information via pointer rather than by copying. For example, when the node configures both a unicast and anycast address for a prefix, the ipAddressPrefix objects for those addresses will point to a single row in this table. This table primarily provides support for IPv6 prefixes, and several of the objects are less meaningful for IPv4. The table continues to allow IPv4 addresses to allow future flexibility. In order to promote a common configuration, this document includes suggestions for default values for IPv4 prefixes. Each of these values may be overridden if an object is meaningful to the node. All prefixes used by this entity should be included in this table independent of how the entity learned the prefix. (This table isn't limited to prefixes learned from router advertisements.)
.1.3.6.1.2.1.4.32.1,IP-MIB::ipAddressPrefixEntry,,not-accessible,ipAddressPrefixIfIndex:ipAddressPrefixType:ipAddressPrefixPrefix:ipAddressPrefixLength,current,,An entry in the ipAddressPrefixTable.
.1.3.6.1.2.1.4.32.1.1,IP-MIB::ipAddressPrefixIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface on which this prefix is configured. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.32.1.2,IP-MIB::ipAddressPrefixType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of ipAddressPrefix.
.1.3.6.1.2.1.4.32.1.3,IP-MIB::ipAddressPrefixPrefix,OCTET,not-accessible,,current,,The address prefix. The address type of this object is specified in ipAddressPrefixType. The length of this object is the standard length for objects of that type (4 or 16 bytes). Any bits after ipAddressPrefixLength must be zero. Implementors need to be aware that, if the size of ipAddressPrefixPrefix exceeds 114 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.4.32.1.4,IP-MIB::ipAddressPrefixLength,Unsigned32,not-accessible,,current,,The prefix length associated with this prefix. The value 0 has no special meaning for this object. It simply refers to address '::/0'.
.1.3.6.1.2.1.4.32.1.5,IP-MIB::ipAddressPrefixOrigin,INTEGER,read-only,,current,other(1):manual(2):wellknown(3):dhcp(4):routeradv(5),The origin of this prefix.
.1.3.6.1.2.1.4.32.1.6,IP-MIB::ipAddressPrefixOnLinkFlag,INTEGER,read-only,,current,true(1):false(2),This object has the value 'true(1)', if this prefix can be used for on-link determination; otherwise, the value is 'false(2)'. The default for IPv4 prefixes is 'true(1)'.
.1.3.6.1.2.1.4.32.1.7,IP-MIB::ipAddressPrefixAutonomousFlag,INTEGER,read-only,,current,true(1):false(2),Autonomous address configuration flag. When true(1), indicates that this prefix can be used for autonomous address configuration (i.e., can be used to form a local interface address). If false(2), it is not used to auto- configure a local interface address. The default for IPv4 prefixes is 'false(2)'.
.1.3.6.1.2.1.4.32.1.8,IP-MIB::ipAddressPrefixAdvPreferredLifetime,Unsigned32,read-only,,current,,The remaining length of time, in seconds, that this prefix will continue to be preferred, i.e., time until deprecation. A value of 4,294,967,295 represents infinity. The address generated from a deprecated prefix should no longer be used as a source address in new communications, but packets received on such an interface are processed as expected. The default for IPv4 prefixes is 4,294,967,295 (infinity).
.1.3.6.1.2.1.4.32.1.9,IP-MIB::ipAddressPrefixAdvValidLifetime,Unsigned32,read-only,,current,,The remaining length of time, in seconds, that this prefix will continue to be valid, i.e., time until invalidation. A value of 4,294,967,295 represents infinity. The address generated from an invalidated prefix should not appear as the destination or source address of a packet. The default for IPv4 prefixes is 4,294,967,295 (infinity).
.1.3.6.1.2.1.4.33,IP-MIB::ipAddressSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow cooperating SNMP managers to coordinate their use of the set operation in creating or modifying rows within this table. In order to use this lock to coordinate the use of set operations, managers should first retrieve ipAddressTableSpinLock. They should then determine the appropriate row to create or modify. Finally, they should issue the appropriate set command, including the retrieved value of ipAddressSpinLock. If another manager has altered the table in the meantime, then the value of ipAddressSpinLock will have changed, and the creation will fail as it will be specifying an incorrect value for ipAddressSpinLock. It is suggested, but not required, that the ipAddressSpinLock be the first var bind for each set of objects representing a 'row' in a PDU.
.1.3.6.1.2.1.4.34,IP-MIB::ipAddressTable,,not-accessible,,current,,This table contains addressing information relevant to the entity's interfaces. This table does not contain multicast address information. Tables for such information should be contained in multicast specific MIBs, such as RFC 3019. While this table is writable, the user will note that several objects, such as ipAddressOrigin, are not. The intention in allowing a user to write to this table is to allow them to add or remove any entry that isn't permanent. The user should be allowed to modify objects and entries when that would not cause inconsistencies within the table. Allowing write access to objects, such as ipAddressOrigin, could allow a user to insert an entry and then label it incorrectly. Note well: When including IPv6 link-local addresses in this table, the entry must use an InetAddressType of 'ipv6z' in order to differentiate between the possible interfaces.
.1.3.6.1.2.1.4.34.1,IP-MIB::ipAddressEntry,,not-accessible,ipAddressAddrType:ipAddressAddr,current,,An address mapping for a particular interface.
.1.3.6.1.2.1.4.34.1.1,IP-MIB::ipAddressAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of ipAddressAddr.
.1.3.6.1.2.1.4.34.1.2,IP-MIB::ipAddressAddr,OCTET,not-accessible,,current,,The IP address to which this entry's addressing information pertains. The address type of this object is specified in ipAddressAddrType. Implementors need to be aware that if the size of ipAddressAddr exceeds 116 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.4.34.1.3,IP-MIB::ipAddressIfIndex,Integer32,read-create,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.34.1.4,IP-MIB::ipAddressType,INTEGER,read-create,,current,unicast(1):anycast(2):broadcast(3),The type of address. broadcast(3) is not a valid value for IPv6 addresses (RFC 3513).
.1.3.6.1.2.1.4.34.1.5,IP-MIB::ipAddressPrefix,OBJECT,read-only,,current,,A pointer to the row in the prefix table to which this address belongs. May be { 0 0 } if there is no such row.
.1.3.6.1.2.1.4.34.1.6,IP-MIB::ipAddressOrigin,INTEGER,read-only,,current,other(1):manual(2):dhcp(4):linklayer(5):random(6),The origin of the address.
.1.3.6.1.2.1.4.34.1.7,IP-MIB::ipAddressStatus,INTEGER,read-create,,current,preferred(1):deprecated(2):invalid(3):inaccessible(4):unknown(5):tentative(6):duplicate(7):optimistic(8),The status of the address, describing if the address can be used for communication. In the absence of other information, an IPv4 address is always preferred(1).
.1.3.6.1.2.1.4.34.1.8,IP-MIB::ipAddressCreated,TimeTicks,read-only,,current,,The value of sysUpTime at the time this entry was created. If this entry was created prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.4.34.1.9,IP-MIB::ipAddressLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.4.34.1.10,IP-MIB::ipAddressRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The RowStatus TC requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified. The value of this object has no effect on whether other objects in this conceptual row can be modified. A conceptual row can not be made active until the ipAddressIfIndex has been set to a valid index.
.1.3.6.1.2.1.4.34.1.11,IP-MIB::ipAddressStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. If this object has a value of 'permanent', then no other objects are required to be able to be modified.
.1.3.6.1.2.1.4.35,IP-MIB::ipNetToPhysicalTable,,not-accessible,,current,,The IP Address Translation table used for mapping from IP addresses to physical addresses. The Address Translation tables contain the IP address to 'physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. While many protocols may be used to populate this table, ARP and Neighbor Discovery are the most likely options.
.1.3.6.1.2.1.4.35.1,IP-MIB::ipNetToPhysicalEntry,,not-accessible,ipNetToPhysicalIfIndex:ipNetToPhysicalNetAddressType:ipNetToPhysicalNetAddress,current,,Each entry contains one IP address to `physical' address equivalence.
.1.3.6.1.2.1.4.35.1.1,IP-MIB::ipNetToPhysicalIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.35.1.2,IP-MIB::ipNetToPhysicalNetAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of ipNetToPhysicalNetAddress.
.1.3.6.1.2.1.4.35.1.3,IP-MIB::ipNetToPhysicalNetAddress,OCTET,not-accessible,,current,,The IP Address corresponding to the media-dependent `physical' address. The address type of this object is specified in ipNetToPhysicalAddressType. Implementors need to be aware that if the size of ipNetToPhysicalNetAddress exceeds 115 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.4.35.1.4,IP-MIB::ipNetToPhysicalPhysAddress,OCTET,read-create,,current,,The media-dependent `physical' address. As the entries in this table are typically not persistent when this object is written the entity SHOULD NOT save the change to non-volatile storage.
.1.3.6.1.2.1.4.35.1.5,IP-MIB::ipNetToPhysicalLastUpdated,TimeTicks,read-only,,current,,The value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re- initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.4.35.1.6,IP-MIB::ipNetToPhysicalType,INTEGER,read-create,,current,other(1):invalid(2):dynamic(3):static(4):local(5),The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToPhysicalTable. That is, it effectively dis- associates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToPhysicalType object. The 'dynamic(3)' type indicates that the IP address to physical addresses mapping has been dynamically resolved using e.g., IPv4 ARP or the IPv6 Neighbor Discovery protocol. The 'static(4)' type indicates that the mapping has been statically configured. Both of these refer to entries that provide mappings for other entities addresses. The 'local(5)' type indicates that the mapping is provided for an entity's own interface address. As the entries in this table are typically not persistent when this object is written the entity SHOULD NOT save the change to non-volatile storage.
.1.3.6.1.2.1.4.35.1.7,IP-MIB::ipNetToPhysicalState,INTEGER,read-only,,current,reachable(1):stale(2):delay(3):probe(4):invalid(5):unknown(6):incomplete(7),The Neighbor Unreachability Detection state for the interface when the address mapping in this entry is used. If Neighbor Unreachability Detection is not in use (e.g. for IPv4), this object is always unknown(6).
.1.3.6.1.2.1.4.35.1.8,IP-MIB::ipNetToPhysicalRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The RowStatus TC requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified. The value of this object has no effect on whether other objects in this conceptual row can be modified. A conceptual row can not be made active until the ipNetToPhysicalPhysAddress object has been set. Note that if the ipNetToPhysicalType is set to 'invalid', the managed node may delete the entry independent of the state of this object.
.1.3.6.1.2.1.4.36,IP-MIB::ipv6ScopeZoneIndexTable,,not-accessible,,current,,The table used to describe IPv6 unicast and multicast scope zones. For those objects that have names rather than numbers, the names were chosen to coincide with the names used in the IPv6 address architecture document. 
.1.3.6.1.2.1.4.36.1,IP-MIB::ipv6ScopeZoneIndexEntry,,not-accessible,ipv6ScopeZoneIndexIfIndex,current,,Each entry contains the list of scope identifiers on a given interface.
.1.3.6.1.2.1.4.36.1.1,IP-MIB::ipv6ScopeZoneIndexIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which these scopes belong. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.36.1.2,IP-MIB::ipv6ScopeZoneIndexLinkLocal,Unsigned32,read-only,,current,,The zone index for the link-local scope on this interface.
.1.3.6.1.2.1.4.36.1.3,IP-MIB::ipv6ScopeZoneIndex3,Unsigned32,read-only,,current,,The zone index for scope 3 on this interface.
.1.3.6.1.2.1.4.36.1.4,IP-MIB::ipv6ScopeZoneIndexAdminLocal,Unsigned32,read-only,,current,,The zone index for the admin-local scope on this interface.
.1.3.6.1.2.1.4.36.1.5,IP-MIB::ipv6ScopeZoneIndexSiteLocal,Unsigned32,read-only,,current,,The zone index for the site-local scope on this interface.
.1.3.6.1.2.1.4.36.1.6,IP-MIB::ipv6ScopeZoneIndex6,Unsigned32,read-only,,current,,The zone index for scope 6 on this interface.
.1.3.6.1.2.1.4.36.1.7,IP-MIB::ipv6ScopeZoneIndex7,Unsigned32,read-only,,current,,The zone index for scope 7 on this interface.
.1.3.6.1.2.1.4.36.1.8,IP-MIB::ipv6ScopeZoneIndexOrganizationLocal,Unsigned32,read-only,,current,,The zone index for the organization-local scope on this interface.
.1.3.6.1.2.1.4.36.1.9,IP-MIB::ipv6ScopeZoneIndex9,Unsigned32,read-only,,current,,The zone index for scope 9 on this interface.
.1.3.6.1.2.1.4.36.1.10,IP-MIB::ipv6ScopeZoneIndexA,Unsigned32,read-only,,current,,The zone index for scope A on this interface.
.1.3.6.1.2.1.4.36.1.11,IP-MIB::ipv6ScopeZoneIndexB,Unsigned32,read-only,,current,,The zone index for scope B on this interface.
.1.3.6.1.2.1.4.36.1.12,IP-MIB::ipv6ScopeZoneIndexC,Unsigned32,read-only,,current,,The zone index for scope C on this interface.
.1.3.6.1.2.1.4.36.1.13,IP-MIB::ipv6ScopeZoneIndexD,Unsigned32,read-only,,current,,The zone index for scope D on this interface.
.1.3.6.1.2.1.4.37,IP-MIB::ipDefaultRouterTable,,not-accessible,,current,,The table used to describe the default routers known to this entity.
.1.3.6.1.2.1.4.37.1,IP-MIB::ipDefaultRouterEntry,,not-accessible,ipDefaultRouterAddressType:ipDefaultRouterAddress:ipDefaultRouterIfIndex,current,,Each entry contains information about a default router known to this entity.
.1.3.6.1.2.1.4.37.1.1,IP-MIB::ipDefaultRouterAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type for this row.
.1.3.6.1.2.1.4.37.1.2,IP-MIB::ipDefaultRouterAddress,OCTET,not-accessible,,current,,The IP address of the default router represented by this row. The address type of this object is specified in ipDefaultRouterAddressType. Implementers need to be aware that if the size of ipDefaultRouterAddress exceeds 115 octets, then OIDS of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.4.37.1.3,IP-MIB::ipDefaultRouterIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface by which the router can be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.37.1.4,IP-MIB::ipDefaultRouterLifetime,Unsigned32,read-only,,current,,The remaining length of time, in seconds, that this router will continue to be useful as a default router. A value of zero indicates that it is no longer useful as a default router. It is left to the implementer of the MIB as to whether a router with a lifetime of zero is removed from the list. For IPv6, this value should be extracted from the router advertisement messages.
.1.3.6.1.2.1.4.37.1.5,IP-MIB::ipDefaultRouterPreference,INTEGER,read-only,,current,reserved(-2):low(-1):medium(0):high(1),An indication of preference given to this router as a default router as described in he Default Router Preferences document. Treating the value as a 2 bit signed integer allows for simple arithmetic comparisons. For IPv4 routers or IPv6 routers that are not using the updated router advertisement format, this object is set to medium (0).
.1.3.6.1.2.1.4.38,IP-MIB::ipv6RouterAdvertSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow cooperating SNMP managers to coordinate their use of the set operation in creating or modifying rows within this table. In order to use this lock to coordinate the use of set operations, managers should first retrieve ipv6RouterAdvertSpinLock. They should then determine the appropriate row to create or modify. Finally, they should issue the appropriate set command including the retrieved value of ipv6RouterAdvertSpinLock. If another manager has altered the table in the meantime, then the value of ipv6RouterAdvertSpinLock will have changed and the creation will fail as it will be specifying an incorrect value for ipv6RouterAdvertSpinLock. It is suggested, but not required, that the ipv6RouterAdvertSpinLock be the first var bind for each set of objects representing a 'row' in a PDU.
.1.3.6.1.2.1.4.39,IP-MIB::ipv6RouterAdvertTable,,not-accessible,,current,,The table containing information used to construct router advertisements.
.1.3.6.1.2.1.4.39.1,IP-MIB::ipv6RouterAdvertEntry,,not-accessible,ipv6RouterAdvertIfIndex,current,,An entry containing information used to construct router advertisements. Information in this table is persistent, and when this object is written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.4.39.1.1,IP-MIB::ipv6RouterAdvertIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface on which router advertisements constructed with this information will be transmitted. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.39.1.2,IP-MIB::ipv6RouterAdvertSendAdverts,INTEGER,read-create,,current,true(1):false(2),A flag indicating whether the router sends periodic router advertisements and responds to router solicitations on this interface.
.1.3.6.1.2.1.4.39.1.3,IP-MIB::ipv6RouterAdvertMaxInterval,Unsigned32,read-create,,current,,The maximum time allowed between sending unsolicited router advertisements from this interface.
.1.3.6.1.2.1.4.39.1.4,IP-MIB::ipv6RouterAdvertMinInterval,Unsigned32,read-create,,current,,The minimum time allowed between sending unsolicited router advertisements from this interface. The default is 0.33 * ipv6RouterAdvertMaxInterval, however, in the case of a low value for ipv6RouterAdvertMaxInterval, the minimum value for this object is restricted to 3.
.1.3.6.1.2.1.4.39.1.5,IP-MIB::ipv6RouterAdvertManagedFlag,INTEGER,read-create,,current,true(1):false(2),The true/false value to be placed into the 'managed address configuration' flag field in router advertisements sent from this interface.
.1.3.6.1.2.1.4.39.1.6,IP-MIB::ipv6RouterAdvertOtherConfigFlag,INTEGER,read-create,,current,true(1):false(2),The true/false value to be placed into the 'other stateful configuration' flag field in router advertisements sent from this interface.
.1.3.6.1.2.1.4.39.1.7,IP-MIB::ipv6RouterAdvertLinkMTU,Unsigned32,read-create,,current,,The value to be placed in MTU options sent by the router on this interface. A value of zero indicates that no MTU options are sent.
.1.3.6.1.2.1.4.39.1.8,IP-MIB::ipv6RouterAdvertReachableTime,Unsigned32,read-create,,current,,The value to be placed in the reachable time field in router advertisement messages sent from this interface. A value of zero in the router advertisement indicates that the advertisement isn't specifying a value for reachable time.
.1.3.6.1.2.1.4.39.1.9,IP-MIB::ipv6RouterAdvertRetransmitTime,Unsigned32,read-create,,current,,The value to be placed in the retransmit timer field in router advertisements sent from this interface. A value of zero in the router advertisement indicates that the advertisement isn't specifying a value for retrans time.
.1.3.6.1.2.1.4.39.1.10,IP-MIB::ipv6RouterAdvertCurHopLimit,Unsigned32,read-create,,current,,The default value to be placed in the current hop limit field in router advertisements sent from this interface. The value should be set to the current diameter of the Internet. A value of zero in the router advertisement indicates that the advertisement isn't specifying a value for curHopLimit. The default should be set to the value specified in the IANA web pages (www.iana.org) at the time of implementation.
.1.3.6.1.2.1.4.39.1.11,IP-MIB::ipv6RouterAdvertDefaultLifetime,Unsigned32,read-create,,current,,The value to be placed in the router lifetime field of router advertisements sent from this interface. This value MUST be either 0 or between ipv6RouterAdvertMaxInterval and 9000 seconds. A value of zero indicates that the router is not to be used as a default router. The default is 3 * ipv6RouterAdvertMaxInterval.
.1.3.6.1.2.1.4.39.1.12,IP-MIB::ipv6RouterAdvertRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. As all objects in this conceptual row have default values, a row can be created and made active by setting this object appropriately. The RowStatus TC requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.4.40,SAVI-MIB::saviMIB,,,,,,The MIB Module for managing SAVI implementations.
.1.3.6.1.2.1.4.40.1,SAVI-MIB::saviObjects,,,,,,
.1.3.6.1.2.1.4.40.1.1,SAVI-MIB::saviObjectsSystemTable,,not-accessible,,current,,The table containing savi system-wide parameters.
.1.3.6.1.2.1.4.40.1.1.1,SAVI-MIB::saviObjectsSystemEntry,,not-accessible,saviObjectsSystemIPVersion,current,,Each entry containing savi system-wide parameters for a particular IP version.
.1.3.6.1.2.1.4.40.1.1.1.1,SAVI-MIB::saviObjectsSystemIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version 
.1.3.6.1.2.1.4.40.1.1.1.2,SAVI-MIB::saviObjectsSystemMode,INTEGER,read-write,,current,savi-disable(1):savi-default(2):savi-dhcp-only(3):savi-slaac-only(4):savi-dhcp-slaac-mix(5),IP Address Assignment Methods. 
.1.3.6.1.2.1.4.40.1.1.1.3,SAVI-MIB::saviObjectsSystemMaxDadDelay,INTEGER,read-write,,current,,A constant. When A gratuitous ARP Request or Duplicate  Address Detection Neighbor Solicitation is received  from anchor, the lifetime of the BST(Binding State Table) entry MUST be set to be MAX_ARP_DELAY or MAX_DAD_DELAY  respectively.
.1.3.6.1.2.1.4.40.1.1.1.4,SAVI-MIB::saviObjectsSystemMaxDadPrepareDelay,INTEGER,read-write,,current,,A constant. When a DHCPv4 DHCPACK or DHCPv6 REPLY message is received, the lifetime of the BST(Binding State Table) entry MUST be set to be MAX_ARP_PREPARE_DELAY or  MAX_DAD_PREPARE_DELAY respectively.
.1.3.6.1.2.1.4.40.1.2,SAVI-MIB::saviObjectsIfTable,,not-accessible,,current,,The table containing SAVI running parameters of each anchor.
.1.3.6.1.2.1.4.40.1.2.1,SAVI-MIB::saviObjectsIfEntry,,not-accessible,saviObjectsIfIPVersion:saviObjectsIfIfIndex,current,,An entry containing SAVI running parameters of an anchor.
.1.3.6.1.2.1.4.40.1.2.1.1,SAVI-MIB::saviObjectsIfIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version 
.1.3.6.1.2.1.4.40.1.2.1.2,SAVI-MIB::saviObjectsIfIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.40.1.2.1.3,SAVI-MIB::saviObjectsIfValidationStatus,INTEGER,read-write,,current,enable(1):disable(2),The validation status of the interface.  enable(1), check source address. disable(2), don't check source address.  
.1.3.6.1.2.1.4.40.1.2.1.4,SAVI-MIB::saviObjectsIfTrustStatus,INTEGER,read-write,,current,no-trust(1):dhcp-trust(2):ra-trust(3):dhcp-ra-trust(4),The trust status of the interface.  no-trust(1), discard dhcp adv/reply and ra packet, dhcp-trust(2), permit dhcp adv/reply packet and discard ra packet, ra-trust(3), permit ra packet and discard dhcp adv/reply packet, dhcp-ra-trust(4), permit dhcp adv/reply and ra packet. 
.1.3.6.1.2.1.4.40.1.2.1.5,SAVI-MIB::saviObjectsIfFilteringNum,Unsigned32,read-write,,current,,The max filtering number of the Interface
.1.3.6.1.2.1.4.40.1.3,SAVI-MIB::saviObjectsBindingTable,,not-accessible,,current,,The Binding State Table containing the state of binding  between source address and anchor.
.1.3.6.1.2.1.4.40.1.3.1,SAVI-MIB::saviObjectsBindingEntry,,not-accessible,saviObjectsBindingIpAddressType:saviObjectsBindingType:saviObjectsBindingIfIndex:saviObjectsBindingIpAddress,current,,An entry containing the state of binding between source  address and anchor. Entries are keyed on the anchor,  binding type, source IP address version, and source IP  address.
.1.3.6.1.2.1.4.40.1.3.1.1,SAVI-MIB::saviObjectsBindingIpAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),IP address type of the binding source IP
.1.3.6.1.2.1.4.40.1.3.1.2,SAVI-MIB::saviObjectsBindingType,INTEGER,not-accessible,,current,static(1):slaac(2):dhcp(3),IP address assignment methods.
.1.3.6.1.2.1.4.40.1.3.1.3,SAVI-MIB::saviObjectsBindingIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.40.1.3.1.4,SAVI-MIB::saviObjectsBindingIpAddress,OCTET,not-accessible,,current,,The binding source IP address
.1.3.6.1.2.1.4.40.1.3.1.5,SAVI-MIB::saviObjectsBindingMacAddr,OCTET,read-create,,current,,The binding source mac address.
.1.3.6.1.2.1.4.40.1.3.1.6,SAVI-MIB::saviObjectsBindingState,INTEGER,read-create,,current,start(1):live(2):detection(3):query(4):bound(5),The state of the binding entry. 
.1.3.6.1.2.1.4.40.1.3.1.7,SAVI-MIB::saviObjectsBindingLifetime,INTEGER,read-create,,current,,The remaining lifetime of the entry.  If saviObjectsBindingType=static, a value of 2147483647  represents infinity.
.1.3.6.1.2.1.4.40.1.3.1.8,SAVI-MIB::saviObjectsBindingRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.  An Entry can be created or deleted only when  saviObjectsBindingType=static.
.1.3.6.1.2.1.4.40.1.4,SAVI-MIB::saviObjectsFilteringTable,,not-accessible,,current,,The Filtering Table is used to filter packets.
.1.3.6.1.2.1.4.40.1.4.1,SAVI-MIB::saviObjectsFilteringEntry,,not-accessible,saviObjectsFilteringIpAddressType:saviObjectsFilteringIfIndex:saviObjectsFilteringIpAddress,current,,An entry containing the filtering parameters. Entries are keyed on the anchor.
.1.3.6.1.2.1.4.40.1.4.1.1,SAVI-MIB::saviObjectsFilteringIpAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),IP address type of the filtering source IP
.1.3.6.1.2.1.4.40.1.4.1.2,SAVI-MIB::saviObjectsFilteringIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.4.40.1.4.1.3,SAVI-MIB::saviObjectsFilteringIpAddress,OCTET,not-accessible,,current,,The filtering source IP address
.1.3.6.1.2.1.4.40.1.4.1.4,SAVI-MIB::saviObjectsFilteringMacAddr,OCTET,read-only,,current,,The filtering source mac address.
.1.3.6.1.2.1.4.40.2,SAVI-MIB::saviConformance,,,,,,
.1.3.6.1.2.1.4.40.2.1,SAVI-MIB::saviCompliances,,,,,,
.1.3.6.1.2.1.4.40.2.1.1,SAVI-MIB::saviCompliance,,,,,,The compliance statement for entities which implement SAVI.
.1.3.6.1.2.1.4.40.2.2,SAVI-MIB::saviGroups,,,,,,
.1.3.6.1.2.1.4.40.2.2.1,SAVI-MIB::systemGroup,,,,,,The system group of objects containing savi system parameter.
.1.3.6.1.2.1.4.40.2.2.2,SAVI-MIB::ifGroup,,,,,,The if group of objects containing the savi running parameters of each anchor.
.1.3.6.1.2.1.4.40.2.2.3,SAVI-MIB::bindingGroup,,,,,,The binding group of objects containing the binding information  of anchor and soure ip address. 
.1.3.6.1.2.1.4.40.2.2.4,SAVI-MIB::filteringGroup,,,,,,The filtering group of objects containing the filtering information  of anchor and soure ip address. 
.1.3.6.1.2.1.5,RFC1213-MIB::icmp,,,,,,
.1.3.6.1.2.1.5.1,RFC1213-MIB::icmpInMsgs,Counter32,read-only,,mandatory,,The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
.1.3.6.1.2.1.5.2,RFC1213-MIB::icmpInErrors,Counter32,read-only,,mandatory,,The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
.1.3.6.1.2.1.5.3,RFC1213-MIB::icmpInDestUnreachs,Counter32,read-only,,mandatory,,The number of ICMP Destination Unreachable messages received.
.1.3.6.1.2.1.5.4,RFC1213-MIB::icmpInTimeExcds,Counter32,read-only,,mandatory,,The number of ICMP Time Exceeded messages received.
.1.3.6.1.2.1.5.5,RFC1213-MIB::icmpInParmProbs,Counter32,read-only,,mandatory,,The number of ICMP Parameter Problem messages received.
.1.3.6.1.2.1.5.6,RFC1213-MIB::icmpInSrcQuenchs,Counter32,read-only,,mandatory,,The number of ICMP Source Quench messages received.
.1.3.6.1.2.1.5.7,RFC1213-MIB::icmpInRedirects,Counter32,read-only,,mandatory,,The number of ICMP Redirect messages received.
.1.3.6.1.2.1.5.8,RFC1213-MIB::icmpInEchos,Counter32,read-only,,mandatory,,The number of ICMP Echo (request) messages received.
.1.3.6.1.2.1.5.9,RFC1213-MIB::icmpInEchoReps,Counter32,read-only,,mandatory,,The number of ICMP Echo Reply messages received.
.1.3.6.1.2.1.5.10,RFC1213-MIB::icmpInTimestamps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp (request) messages received.
.1.3.6.1.2.1.5.11,RFC1213-MIB::icmpInTimestampReps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp Reply messages received.
.1.3.6.1.2.1.5.12,RFC1213-MIB::icmpInAddrMasks,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Request messages received.
.1.3.6.1.2.1.5.13,RFC1213-MIB::icmpInAddrMaskReps,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Reply messages received.
.1.3.6.1.2.1.5.14,RFC1213-MIB::icmpOutMsgs,Counter32,read-only,,mandatory,,The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
.1.3.6.1.2.1.5.15,RFC1213-MIB::icmpOutErrors,Counter32,read-only,,mandatory,,The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.
.1.3.6.1.2.1.5.16,RFC1213-MIB::icmpOutDestUnreachs,Counter32,read-only,,mandatory,,The number of ICMP Destination Unreachable messages sent.
.1.3.6.1.2.1.5.17,RFC1213-MIB::icmpOutTimeExcds,Counter32,read-only,,mandatory,,The number of ICMP Time Exceeded messages sent.
.1.3.6.1.2.1.5.18,RFC1213-MIB::icmpOutParmProbs,Counter32,read-only,,mandatory,,The number of ICMP Parameter Problem messages sent.
.1.3.6.1.2.1.5.19,RFC1213-MIB::icmpOutSrcQuenchs,Counter32,read-only,,mandatory,,The number of ICMP Source Quench messages sent.
.1.3.6.1.2.1.5.20,RFC1213-MIB::icmpOutRedirects,Counter32,read-only,,mandatory,,The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.
.1.3.6.1.2.1.5.21,RFC1213-MIB::icmpOutEchos,Counter32,read-only,,mandatory,,The number of ICMP Echo (request) messages sent.
.1.3.6.1.2.1.5.22,RFC1213-MIB::icmpOutEchoReps,Counter32,read-only,,mandatory,,The number of ICMP Echo Reply messages sent.
.1.3.6.1.2.1.5.23,RFC1213-MIB::icmpOutTimestamps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp (request) messages sent.
.1.3.6.1.2.1.5.24,RFC1213-MIB::icmpOutTimestampReps,Counter32,read-only,,mandatory,,The number of ICMP Timestamp Reply messages sent.
.1.3.6.1.2.1.5.25,RFC1213-MIB::icmpOutAddrMasks,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Request messages sent.
.1.3.6.1.2.1.5.26,RFC1213-MIB::icmpOutAddrMaskReps,Counter32,read-only,,mandatory,,The number of ICMP Address Mask Reply messages sent.
.1.3.6.1.2.1.5.29,IP-MIB::icmpStatsTable,,not-accessible,,current,,The table of generic system-wide ICMP counters.
.1.3.6.1.2.1.5.29.1,IP-MIB::icmpStatsEntry,,not-accessible,icmpStatsIPVersion,current,,A conceptual row in the icmpStatsTable.
.1.3.6.1.2.1.5.29.1.1,IP-MIB::icmpStatsIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version of the statistics.
.1.3.6.1.2.1.5.29.1.2,IP-MIB::icmpStatsInMsgs,Counter32,read-only,,current,,The total number of ICMP messages that the entity received. Note that this counter includes all those counted by icmpStatsInErrors.
.1.3.6.1.2.1.5.29.1.3,IP-MIB::icmpStatsInErrors,Counter32,read-only,,current,,The number of ICMP messages that the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
.1.3.6.1.2.1.5.29.1.4,IP-MIB::icmpStatsOutMsgs,Counter32,read-only,,current,,The total number of ICMP messages that the entity attempted to send. Note that this counter includes all those counted by icmpStatsOutErrors.
.1.3.6.1.2.1.5.29.1.5,IP-MIB::icmpStatsOutErrors,Counter32,read-only,,current,,The number of ICMP messages that this entity did not send due to problems discovered within ICMP, such as a lack of buffers. This value should not include errors discovered outside the ICMP layer, such as the inability of IP to route the resultant datagram. In some implementations, there may be no types of error that contribute to this counter's value.
.1.3.6.1.2.1.5.30,IP-MIB::icmpMsgStatsTable,,not-accessible,,current,,The table of system-wide per-version, per-message type ICMP counters.
.1.3.6.1.2.1.5.30.1,IP-MIB::icmpMsgStatsEntry,,not-accessible,icmpMsgStatsIPVersion:icmpMsgStatsType,current,,A conceptual row in the icmpMsgStatsTable. The system should track each ICMP type value, even if that ICMP type is not supported by the system. However, a given row need not be instantiated unless a message of that type has been processed, i.e., the row for icmpMsgStatsType=X MAY be instantiated before but MUST be instantiated after the first message with Type=X is received or transmitted. After receiving or transmitting any succeeding messages with Type=X, the relevant counter must be incremented.
.1.3.6.1.2.1.5.30.1.1,IP-MIB::icmpMsgStatsIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version of the statistics.
.1.3.6.1.2.1.5.30.1.2,IP-MIB::icmpMsgStatsType,Integer32,not-accessible,,current,,The ICMP type field of the message type being counted by this row. Note that ICMP message types are scoped by the address type in use.
.1.3.6.1.2.1.5.30.1.3,IP-MIB::icmpMsgStatsInPkts,Counter32,read-only,,current,,The number of input packets for this AF and type.
.1.3.6.1.2.1.5.30.1.4,IP-MIB::icmpMsgStatsOutPkts,Counter32,read-only,,current,,The number of output packets for this AF and type.
.1.3.6.1.2.1.6,RFC1213-MIB::tcp,,,,,,
.1.3.6.1.2.1.6.1,RFC1213-MIB::tcpRtoAlgorithm,INTEGER,read-only,,mandatory,other(1):constant(2):rsre(3):vanj(4),The algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
.1.3.6.1.2.1.6.2,RFC1213-MIB::tcpRtoMin,INTEGER,read-only,,mandatory,,The minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
.1.3.6.1.2.1.6.3,RFC1213-MIB::tcpRtoMax,INTEGER,read-only,,mandatory,,The maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793.
.1.3.6.1.2.1.6.4,RFC1213-MIB::tcpMaxConn,INTEGER,read-only,,mandatory,,The limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
.1.3.6.1.2.1.6.5,RFC1213-MIB::tcpActiveOpens,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
.1.3.6.1.2.1.6.6,RFC1213-MIB::tcpPassiveOpens,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
.1.3.6.1.2.1.6.7,RFC1213-MIB::tcpAttemptFails,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
.1.3.6.1.2.1.6.8,RFC1213-MIB::tcpEstabResets,Counter32,read-only,,mandatory,,The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
.1.3.6.1.2.1.6.9,RFC1213-MIB::tcpCurrEstab,Gauge32,read-only,,mandatory,,The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
.1.3.6.1.2.1.6.10,RFC1213-MIB::tcpInSegs,Counter32,read-only,,mandatory,,The total number of segments received, including those received in error. This count includes segments received on currently established connections.
.1.3.6.1.2.1.6.11,RFC1213-MIB::tcpOutSegs,Counter32,read-only,,mandatory,,The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
.1.3.6.1.2.1.6.12,RFC1213-MIB::tcpRetransSegs,Counter32,read-only,,mandatory,,The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
.1.3.6.1.2.1.6.13,RFC1213-MIB::tcpConnTable,,not-accessible,,mandatory,,A table containing TCP connection-specific information.
.1.3.6.1.2.1.6.13.1,RFC1213-MIB::tcpConnEntry,,not-accessible,tcpConnLocalAddress:tcpConnLocalPort:tcpConnRemAddress:tcpConnRemPort,mandatory,,Information about a particular current TCP connection. An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
.1.3.6.1.2.1.6.13.1.1,RFC1213-MIB::tcpConnState,INTEGER,read-write,,mandatory,closed(1):listen(2):synSent(3):synReceived(4):established(5):finWait1(6):finWait2(7):closeWait(8):lastAck(9):closing(10):timeWait(11):deleteTCB(12),The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
.1.3.6.1.2.1.6.13.1.2,RFC1213-MIB::tcpConnLocalAddress,IpAddress,read-only,,mandatory,,The local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.
.1.3.6.1.2.1.6.13.1.3,RFC1213-MIB::tcpConnLocalPort,INTEGER,read-only,,mandatory,,The local port number for this TCP connection.
.1.3.6.1.2.1.6.13.1.4,RFC1213-MIB::tcpConnRemAddress,IpAddress,read-only,,mandatory,,The remote IP address for this TCP connection.
.1.3.6.1.2.1.6.13.1.5,RFC1213-MIB::tcpConnRemPort,INTEGER,read-only,,mandatory,,The remote port number for this TCP connection.
.1.3.6.1.2.1.6.14,RFC1213-MIB::tcpInErrs,Counter32,read-only,,mandatory,,The total number of segments received in error (e.g., bad TCP checksums).
.1.3.6.1.2.1.6.15,RFC1213-MIB::tcpOutRsts,Counter32,read-only,,mandatory,,The number of TCP segments sent containing the RST flag.
.1.3.6.1.2.1.6.16,IPV6-TCP-MIB::ipv6TcpConnTable,,not-accessible,,obsolete,,A table containing TCP connection-specific information, for only those connections whose endpoints are IPv6 addresses. This table is obsoleted by TCP-MIB::tcpConnectionTable.
.1.3.6.1.2.1.6.16.1,IPV6-TCP-MIB::ipv6TcpConnEntry,,not-accessible,ipv6TcpConnLocalAddress:ipv6TcpConnLocalPort:ipv6TcpConnRemAddress:ipv6TcpConnRemPort:ipv6TcpConnIfIndex,obsolete,,A conceptual row of the ipv6TcpConnTable containing information about a particular current TCP connection. Each row of this table is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state. Note that conceptual rows in this table require an additional index object compared to tcpConnTable, since IPv6 addresses are not guaranteed to be unique on the managed node. This entry is obsoleted by TCP-MIB::tcpConnectionEntry.
.1.3.6.1.2.1.6.16.1.1,IPV6-TCP-MIB::ipv6TcpConnLocalAddress,OCTET,not-accessible,,obsolete,,The local IPv6 address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IPv6 address associated with the managed node, the value ::0 is used. This object is obsoleted by TCP-MIB::tcpConnectionLocalAddressType.
.1.3.6.1.2.1.6.16.1.2,IPV6-TCP-MIB::ipv6TcpConnLocalPort,INTEGER,not-accessible,,obsolete,,The local port number for this TCP connection. This object is obsoleted by TCP-MIB::tcpConnectionLocalPort.
.1.3.6.1.2.1.6.16.1.3,IPV6-TCP-MIB::ipv6TcpConnRemAddress,OCTET,not-accessible,,obsolete,,The remote IPv6 address for this TCP connection. This object is obsoleted by TCP-MIB::tcpConnectionRemAddress.
.1.3.6.1.2.1.6.16.1.4,IPV6-TCP-MIB::ipv6TcpConnRemPort,INTEGER,not-accessible,,obsolete,,The remote port number for this TCP connection. This object is obsoleted by TCP-MIB::tcpConnectionRemPort.
.1.3.6.1.2.1.6.16.1.5,IPV6-TCP-MIB::ipv6TcpConnIfIndex,Integer32,not-accessible,,obsolete,,An index object used to disambiguate conceptual rows in the table, since the connection 4-tuple may not be unique. If the connection's remote address (ipv6TcpConnRemAddress) is a link-local address and the connection's local address (ipv6TcpConnLocalAddress) is not a link-local address, this object identifies a local interface on the same link as the connection's remote link-local address. Otherwise, this object identifies the local interface that is associated with the ipv6TcpConnLocalAddress for this TCP connection. If such a local interface cannot be determined, this object should take on the value 0. (A possible example of this would be if the value of ipv6TcpConnLocalAddress is ::0.) The interface identified by a particular non-0 value of this index is the same interface as identified by the same value of ipv6IfIndex. The value of this object must remain constant during the life of the TCP connection. This object is obsoleted by the zone identifier in an InetAddressIPv6z address in either TCP-MIB::tcpConnectionLocalAddress or TCP-MIB::tcpConnectionRemAddress.
.1.3.6.1.2.1.6.16.1.6,IPV6-TCP-MIB::ipv6TcpConnState,INTEGER,read-write,,obsolete,closed(1):listen(2):synSent(3):synReceived(4):established(5):finWait1(6):finWait2(7):closeWait(8):lastAck(9):closing(10):timeWait(11):deleteTCB(12),The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return an error response ('badValue' for SNMPv1, 'wrongValue' for SNMPv2) if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably). This object is obsoleted by TCP-MIB::tcpConnectionState.
.1.3.6.1.2.1.6.17,TCP-MIB::tcpHCInSegs,Counter64,read-only,,current,,The total number of segments received, including those received in error. This count includes segments received on currently established connections. This object is the 64-bit equivalent of tcpInSegs. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.6.18,TCP-MIB::tcpHCOutSegs,Counter64,read-only,,current,,The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets. This object is the 64-bit equivalent of tcpOutSegs. Discontinuities in the value of this counter are indicated via discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.6.19,TCP-MIB::tcpConnectionTable,,not-accessible,,current,,A table containing information about existing TCP connections. Note that unlike earlier TCP MIBs, there is a separate table for connections in the LISTEN state.
.1.3.6.1.2.1.6.19.1,TCP-MIB::tcpConnectionEntry,,not-accessible,tcpConnectionLocalAddressType:tcpConnectionLocalAddress:tcpConnectionLocalPort:tcpConnectionRemAddressType:tcpConnectionRemAddress:tcpConnectionRemPort,current,,A conceptual row of the tcpConnectionTable containing information about a particular current TCP connection. Each row of this table is transient in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
.1.3.6.1.2.1.6.19.1.1,TCP-MIB::tcpConnectionLocalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of tcpConnectionLocalAddress.
.1.3.6.1.2.1.6.19.1.2,TCP-MIB::tcpConnectionLocalAddress,OCTET,not-accessible,,current,,The local IP address for this TCP connection. The type of this address is determined by the value of tcpConnectionLocalAddressType. As this object is used in the index for the tcpConnectionTable, implementors should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; otherwise the information cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.6.19.1.3,TCP-MIB::tcpConnectionLocalPort,Unsigned32,not-accessible,,current,,The local port number for this TCP connection.
.1.3.6.1.2.1.6.19.1.4,TCP-MIB::tcpConnectionRemAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of tcpConnectionRemAddress.
.1.3.6.1.2.1.6.19.1.5,TCP-MIB::tcpConnectionRemAddress,OCTET,not-accessible,,current,,The remote IP address for this TCP connection. The type of this address is determined by the value of tcpConnectionRemAddressType. As this object is used in the index for the tcpConnectionTable, implementors should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; otherwise the information cannot be accessed by using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.6.19.1.6,TCP-MIB::tcpConnectionRemPort,Unsigned32,not-accessible,,current,,The remote port number for this TCP connection.
.1.3.6.1.2.1.6.19.1.7,TCP-MIB::tcpConnectionState,INTEGER,read-write,,current,closed(1):listen(2):synSent(3):synReceived(4):established(5):finWait1(6):finWait2(7):closeWait(8):lastAck(9):closing(10):timeWait(11):deleteTCB(12),The state of this TCP connection. The value listen(2) is included only for parallelism to the old tcpConnTable and should not be used. A connection in LISTEN state should be present in the tcpListenerTable. The only value that may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then the TCB (as defined in [RFC793]) of the corresponding connection on the managed node is deleted, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note, however, that RST segments are not sent reliably).
.1.3.6.1.2.1.6.19.1.8,TCP-MIB::tcpConnectionProcess,Unsigned32,read-only,,current,,The system's process ID for the process associated with this connection, or zero if there is no such process. This value is expected to be the same as HOST-RESOURCES-MIB:: hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some row in the appropriate tables.
.1.3.6.1.2.1.6.20,TCP-MIB::tcpListenerTable,,not-accessible,,current,,A table containing information about TCP listeners. A listening application can be represented in three possible ways: 1. An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a tcpListenerLocalAddressType of unknown (0) and a tcpListenerLocalAddress of ''h (a zero-length octet-string). 2. An application that is willing to accept only IPv4 or IPv6 datagrams is represented by a tcpListenerLocalAddressType of the appropriate address type and a tcpListenerLocalAddress of '0.0.0.0' or '::' respectively. 3. An application that is listening for data destined only to a specific IP address, but from any remote system, is represented by a tcpListenerLocalAddressType of an appropriate address type, with tcpListenerLocalAddress as the specific local address. NOTE: The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 'sockets' to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1)).
.1.3.6.1.2.1.6.20.1,TCP-MIB::tcpListenerEntry,,not-accessible,tcpListenerLocalAddressType:tcpListenerLocalAddress:tcpListenerLocalPort,current,,A conceptual row of the tcpListenerTable containing information about a particular TCP listener.
.1.3.6.1.2.1.6.20.1.1,TCP-MIB::tcpListenerLocalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of tcpListenerLocalAddress. The value should be unknown (0) if connection initiations to all local IP addresses are accepted.
.1.3.6.1.2.1.6.20.1.2,TCP-MIB::tcpListenerLocalAddress,OCTET,not-accessible,,current,,The local IP address for this TCP connection. The value of this object can be represented in three possible ways, depending on the characteristics of the listening application: 1. For an application willing to accept both IPv4 and IPv6 datagrams, the value of this object must be ''h (a zero-length octet-string), with the value of the corresponding tcpListenerLocalAddressType object being unknown (0). 2. For an application willing to accept only IPv4 or IPv6 datagrams, the value of this object must be '0.0.0.0' or '::' respectively, with tcpListenerLocalAddressType representing the appropriate address type. 3. For an application which is listening for data destined only to a specific IP address, the value of this object is the specific local address, with tcpListenerLocalAddressType representing the appropriate address type. As this object is used in the index for the tcpListenerTable, implementors should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; otherwise the information cannot be accessed, using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.6.20.1.3,TCP-MIB::tcpListenerLocalPort,Unsigned32,not-accessible,,current,,The local port number for this TCP connection.
.1.3.6.1.2.1.6.20.1.4,TCP-MIB::tcpListenerProcess,Unsigned32,read-only,,current,,The system's process ID for the process associated with this listener, or zero if there is no such process. This value is expected to be the same as HOST-RESOURCES-MIB:: hrSWRunIndex or SYSAPPL-MIB::sysApplElmtRunIndex for some row in the appropriate tables.
.1.3.6.1.2.1.7,RFC1213-MIB::udp,,,,,,
.1.3.6.1.2.1.7.1,RFC1213-MIB::udpInDatagrams,Counter32,read-only,,mandatory,,The total number of UDP datagrams delivered to UDP users.
.1.3.6.1.2.1.7.2,RFC1213-MIB::udpNoPorts,Counter32,read-only,,mandatory,,The total number of received UDP datagrams for which there was no application at the destination port.
.1.3.6.1.2.1.7.3,RFC1213-MIB::udpInErrors,Counter32,read-only,,mandatory,,The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
.1.3.6.1.2.1.7.4,RFC1213-MIB::udpOutDatagrams,Counter32,read-only,,mandatory,,The total number of UDP datagrams sent from this entity.
.1.3.6.1.2.1.7.5,RFC1213-MIB::udpTable,,not-accessible,,mandatory,,A table containing UDP listener information.
.1.3.6.1.2.1.7.5.1,RFC1213-MIB::udpEntry,,not-accessible,udpLocalAddress:udpLocalPort,mandatory,,Information about a particular current UDP listener.
.1.3.6.1.2.1.7.5.1.1,RFC1213-MIB::udpLocalAddress,IpAddress,read-only,,mandatory,,The local IP address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.
.1.3.6.1.2.1.7.5.1.2,RFC1213-MIB::udpLocalPort,INTEGER,read-only,,mandatory,,The local port number for this UDP listener.
.1.3.6.1.2.1.7.6,IPV6-UDP-MIB::ipv6UdpTable,,not-accessible,,obsolete,,A table containing UDP listener information for UDP/IPv6 endpoints. This table is obsoleted by UDP-MIB::udpEndpointTable.
.1.3.6.1.2.1.7.6.1,IPV6-UDP-MIB::ipv6UdpEntry,,not-accessible,ipv6UdpLocalAddress:ipv6UdpLocalPort:ipv6UdpIfIndex,obsolete,,Information about a particular current UDP listener. Note that conceptual rows in this table require an additional index object compared to udpTable, since IPv6 addresses are not guaranteed to be unique on the managed node. This entry is obsoleted by UDP-MIB::udpEndpointTable.
.1.3.6.1.2.1.7.6.1.1,IPV6-UDP-MIB::ipv6UdpLocalAddress,OCTET,not-accessible,,obsolete,,The local IPv6 address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IPv6 address associated with the managed node, the value ::0 is used. This object is obsoleted by UDP-MIB::udpEndpointLocalAddress.
.1.3.6.1.2.1.7.6.1.2,IPV6-UDP-MIB::ipv6UdpLocalPort,INTEGER,not-accessible,,obsolete,,The local port number for this UDP listener. This object is obsoleted by UDP-MIB::udpEndpointLocalPort.
.1.3.6.1.2.1.7.6.1.3,IPV6-UDP-MIB::ipv6UdpIfIndex,Integer32,read-only,,obsolete,,An index object used to disambiguate conceptual rows in the table, since the ipv6UdpLocalAddress/ipv6UdpLocalPort pair may not be unique. This object identifies the local interface that is associated with ipv6UdpLocalAddress for this UDP listener. If such a local interface cannot be determined, this object should take on the value 0. (A possible example of this would be if the value of ipv6UdpLocalAddress is ::0.) The interface identified by a particular non-0 value of this index is the same interface as identified by the same value of ipv6IfIndex. The value of this object must remain constant during the life of this UDP endpoint. This object is obsoleted by the zone identifier in an InetAddressIPv6z address in UDP-MIB::udpEndpointLocalAddress.
.1.3.6.1.2.1.7.7,UDP-MIB::udpEndpointTable,,not-accessible,,current,,A table containing information about this entity's UDP endpoints on which a local application is currently accepting or sending datagrams. The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 'sockets' to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1). Unlike the udpTable in RFC 2013, this table also allows the representation of an application that completely specifies both local and remote addresses and ports. A listening application is represented in three possible ways: 1) An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a udpEndpointLocalAddressType of unknown(0) and a udpEndpointLocalAddress of ''h (a zero-length octet-string). 2) An application that is willing to accept only IPv4 or only IPv6 datagrams is represented by a udpEndpointLocalAddressType of the appropriate address type and a udpEndpointLocalAddress of '0.0.0.0' or '::' respectively. 3) An application that is listening for datagrams only for a specific IP address but from any remote system is represented by a udpEndpointLocalAddressType of the appropriate address type, with udpEndpointLocalAddress specifying the local address. In all cases where the remote is a wildcard, the udpEndpointRemoteAddressType is unknown(0), the udpEndpointRemoteAddress is ''h (a zero-length octet-string), and the udpEndpointRemotePort is 0. If the operating system is demultiplexing UDP packets by remote address and port, or if the application has 'connected' the socket specifying a default remote address and port, the udpEndpointRemote* values should be used to reflect this.
.1.3.6.1.2.1.7.7.1,UDP-MIB::udpEndpointEntry,,not-accessible,udpEndpointLocalAddressType:udpEndpointLocalAddress:udpEndpointLocalPort:udpEndpointRemoteAddressType:udpEndpointRemoteAddress:udpEndpointRemotePort:udpEndpointInstance,current,,Information about a particular current UDP endpoint. Implementers need to be aware that if the total number of elements (octets or sub-identifiers) in udpEndpointLocalAddress and udpEndpointRemoteAddress exceeds 111, then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.7.7.1.1,UDP-MIB::udpEndpointLocalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of udpEndpointLocalAddress. Only IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or unknown(0) if datagrams for all local IP addresses are accepted.
.1.3.6.1.2.1.7.7.1.2,UDP-MIB::udpEndpointLocalAddress,OCTET,not-accessible,,current,,The local IP address for this UDP endpoint. The value of this object can be represented in three possible ways, depending on the characteristics of the listening application: 1. For an application that is willing to accept both IPv4 and IPv6 datagrams, the value of this object must be ''h (a zero-length octet-string), with the value of the corresponding instance of the udpEndpointLocalAddressType object being unknown(0). 2. For an application that is willing to accept only IPv4 or only IPv6 datagrams, the value of this object must be '0.0.0.0' or '::', respectively, while the corresponding instance of the udpEndpointLocalAddressType object represents the appropriate address type. 3. For an application that is listening for data destined only to a specific IP address, the value of this object is the specific IP address for which this node is receiving packets, with the corresponding instance of the udpEndpointLocalAddressType object representing the appropriate address type. As this object is used in the index for the udpEndpointTable, implementors of this table should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; else the information cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.7.7.1.3,UDP-MIB::udpEndpointLocalPort,Unsigned32,not-accessible,,current,,The local port number for this UDP endpoint.
.1.3.6.1.2.1.7.7.1.4,UDP-MIB::udpEndpointRemoteAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of udpEndpointRemoteAddress. Only IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or unknown(0) if datagrams for all remote IP addresses are accepted. Also, note that some combinations of udpEndpointLocalAdressType and udpEndpointRemoteAddressType are not supported. In particular, if the value of this object is not unknown(0), it is expected to always refer to the same IP version as udpEndpointLocalAddressType.
.1.3.6.1.2.1.7.7.1.5,UDP-MIB::udpEndpointRemoteAddress,OCTET,not-accessible,,current,,The remote IP address for this UDP endpoint. If datagrams from any remote system are to be accepted, this value is ''h (a zero-length octet-string). Otherwise, it has the type described by udpEndpointRemoteAddressType and is the address of the remote system from which datagrams are to be accepted (or to which all datagrams will be sent). As this object is used in the index for the udpEndpointTable, implementors of this table should be careful not to create entries that would result in OIDs with more than 128 subidentifiers; else the information cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.7.7.1.6,UDP-MIB::udpEndpointRemotePort,Unsigned32,not-accessible,,current,,The remote port number for this UDP endpoint. If datagrams from any remote system are to be accepted, this value is zero.
.1.3.6.1.2.1.7.7.1.7,UDP-MIB::udpEndpointInstance,Unsigned32,not-accessible,,current,,The instance of this tuple. This object is used to distinguish among multiple processes 'connected' to the same UDP endpoint. For example, on a system implementing the BSD sockets interface, this would be used to support the SO_REUSEADDR and SO_REUSEPORT socket options.
.1.3.6.1.2.1.7.7.1.8,UDP-MIB::udpEndpointProcess,Unsigned32,read-only,,current,,The system's process ID for the process associated with this endpoint, or zero if there is no such process. This value is expected to be the same as HOST-RESOURCES-MIB::hrSWRunIndex or SYSAPPL-MIB:: sysApplElmtRunIndex for some row in the appropriate tables.
.1.3.6.1.2.1.7.8,UDP-MIB::udpHCInDatagrams,Counter64,read-only,,current,,The total number of UDP datagrams delivered to UDP users, for devices that can receive more than 1 million UDP datagrams per second. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.7.9,UDP-MIB::udpHCOutDatagrams,Counter64,read-only,,current,,The total number of UDP datagrams sent from this entity, for devices that can transmit more than 1 million UDP datagrams per second. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.8,RFC1213-MIB::egp,,,,,,
.1.3.6.1.2.1.8.1,RFC1213-MIB::egpInMsgs,Counter32,read-only,,mandatory,,The number of EGP messages received without error.
.1.3.6.1.2.1.8.2,RFC1213-MIB::egpInErrors,Counter32,read-only,,mandatory,,The number of EGP messages received that proved to be in error.
.1.3.6.1.2.1.8.3,RFC1213-MIB::egpOutMsgs,Counter32,read-only,,mandatory,,The total number of locally generated EGP messages.
.1.3.6.1.2.1.8.4,RFC1213-MIB::egpOutErrors,Counter32,read-only,,mandatory,,The number of locally generated EGP messages not sent due to resource limitations within an EGP entity.
.1.3.6.1.2.1.8.5,RFC1213-MIB::egpNeighTable,,not-accessible,,mandatory,,The EGP neighbor table.
.1.3.6.1.2.1.8.5.1,RFC1213-MIB::egpNeighEntry,,not-accessible,egpNeighAddr,mandatory,,Information about this entity's relationship with a particular EGP neighbor.
.1.3.6.1.2.1.8.5.1.1,RFC1213-MIB::egpNeighState,INTEGER,read-only,,mandatory,idle(1):acquisition(2):down(3):up(4):cease(5),The EGP state of the local system with respect to this entry's EGP neighbor. Each EGP state is represented by a value that is one greater than the numerical value associated with said state in RFC 904.
.1.3.6.1.2.1.8.5.1.2,RFC1213-MIB::egpNeighAddr,IpAddress,read-only,,mandatory,,The IP address of this entry's EGP neighbor.
.1.3.6.1.2.1.8.5.1.3,RFC1213-MIB::egpNeighAs,INTEGER,read-only,,mandatory,,The autonomous system of this EGP peer. Zero should be specified if the autonomous system number of the neighbor is not yet known.
.1.3.6.1.2.1.8.5.1.4,RFC1213-MIB::egpNeighInMsgs,Counter32,read-only,,mandatory,,The number of EGP messages received without error from this EGP peer.
.1.3.6.1.2.1.8.5.1.5,RFC1213-MIB::egpNeighInErrs,Counter32,read-only,,mandatory,,The number of EGP messages received from this EGP peer that proved to be in error (e.g., bad EGP checksum).
.1.3.6.1.2.1.8.5.1.6,RFC1213-MIB::egpNeighOutMsgs,Counter32,read-only,,mandatory,,The number of locally generated EGP messages to this EGP peer.
.1.3.6.1.2.1.8.5.1.7,RFC1213-MIB::egpNeighOutErrs,Counter32,read-only,,mandatory,,The number of locally generated EGP messages not sent to this EGP peer due to resource limitations within an EGP entity.
.1.3.6.1.2.1.8.5.1.8,RFC1213-MIB::egpNeighInErrMsgs,Counter32,read-only,,mandatory,,The number of EGP-defined error messages received from this EGP peer.
.1.3.6.1.2.1.8.5.1.9,RFC1213-MIB::egpNeighOutErrMsgs,Counter32,read-only,,mandatory,,The number of EGP-defined error messages sent to this EGP peer.
.1.3.6.1.2.1.8.5.1.10,RFC1213-MIB::egpNeighStateUps,Counter32,read-only,,mandatory,,The number of EGP state transitions to the UP state with this EGP peer.
.1.3.6.1.2.1.8.5.1.11,RFC1213-MIB::egpNeighStateDowns,Counter32,read-only,,mandatory,,The number of EGP state transitions from the UP state to any other state with this EGP peer.
.1.3.6.1.2.1.8.5.1.12,RFC1213-MIB::egpNeighIntervalHello,INTEGER,read-only,,mandatory,,The interval between EGP Hello command retransmissions (in hundredths of a second). This represents the t1 timer as defined in RFC 904.
.1.3.6.1.2.1.8.5.1.13,RFC1213-MIB::egpNeighIntervalPoll,INTEGER,read-only,,mandatory,,The interval between EGP poll command retransmissions (in hundredths of a second). This represents the t3 timer as defined in RFC 904.
.1.3.6.1.2.1.8.5.1.14,RFC1213-MIB::egpNeighMode,INTEGER,read-only,,mandatory,active(1):passive(2),The polling mode of this EGP entity, either passive or active.
.1.3.6.1.2.1.8.5.1.15,RFC1213-MIB::egpNeighEventTrigger,INTEGER,read-write,,mandatory,start(1):stop(2),A control variable used to trigger operator- initiated Start and Stop events. When read, this variable always returns the most recent value that egpNeighEventTrigger was set to. If it has not been set since the last initialization of the network management subsystem on the node, it returns a value of `stop'. When set, this variable causes a Start or Stop event on the specified neighbor, as specified on pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor acquisition and a non-Idle peer to reinitiate neighbor acquisition. A stop event causes a non-Idle peer to return to the Idle state until a Start event occurs, either via egpNeighEventTrigger or otherwise.
.1.3.6.1.2.1.8.6,RFC1213-MIB::egpAs,INTEGER,read-only,,mandatory,,The autonomous system number of this EGP entity.
.1.3.6.1.2.1.10,SNMPv2-SMI::transmission,,,,,,
.1.3.6.1.2.1.10.5,RFC1382-MIB::x25,,,,,,
.1.3.6.1.2.1.10.5.0,RFC1382-MIB::x25#,,,,,,
.1.3.6.1.2.1.10.5.0.1,RFC1382-MIB::x25Restart,,,,,,This trap means the X.25 PLE sent or received a restart packet. The restart that brings up the link should not send a x25Restart trap so the interface should send a linkUp trap. Sending this trap means the agent does not send a linkDown and linkUp trap.
.1.3.6.1.2.1.10.5.0.2,RFC1382-MIB::x25Reset,,,,,,If the PLE sends or receives a reset, the agent should send an x25Reset trap.
.1.3.6.1.2.1.10.5.1,RFC1382-MIB::x25AdmnTable,,not-accessible,,mandatory,,This table contains the administratively set configuration parameters for an X.25 Packet Level Entity (PLE). Most of the objects in this table have corresponding objects in the x25OperTable. This table contains the values as last set by the administrator. The x25OperTable contains the values actually in use by an X.25 PLE. Changing an administrative value may or may not change a current operating value. The operating value may not change until the interface is restarted. Some implementations may change the values immediately upon changing the administrative table. All implementations are required to load the values from the administrative table when initializing a PLE.
.1.3.6.1.2.1.10.5.1.1,RFC1382-MIB::x25AdmnEntry,,not-accessible,x25AdmnIndex,mandatory,,Entries of x25AdmnTable.
.1.3.6.1.2.1.10.5.1.1.1,RFC1382-MIB::x25AdmnIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the X.25 Interface.
.1.3.6.1.2.1.10.5.1.1.2,RFC1382-MIB::x25AdmnInterfaceMode,INTEGER,read-write,,mandatory,dte(1):dce(2):dxe(3),Identifies DCE/DTE mode in which the interface operates. A value of dxe indicates the mode will be determined by XID negotiation.
.1.3.6.1.2.1.10.5.1.1.3,RFC1382-MIB::x25AdmnMaxActiveCircuits,INTEGER,read-write,,mandatory,,The maximum number of circuits this PLE can support; including PVCs.
.1.3.6.1.2.1.10.5.1.1.4,RFC1382-MIB::x25AdmnPacketSequencing,INTEGER,read-write,,mandatory,modulo8(1):modulo128(2),The modulus of the packet sequence number space.
.1.3.6.1.2.1.10.5.1.1.5,RFC1382-MIB::x25AdmnRestartTimer,INTEGER,read-write,,mandatory,,The T20 restart timer in milliseconds.
.1.3.6.1.2.1.10.5.1.1.6,RFC1382-MIB::x25AdmnCallTimer,INTEGER,read-write,,mandatory,,The T21 Call timer in milliseconds.
.1.3.6.1.2.1.10.5.1.1.7,RFC1382-MIB::x25AdmnResetTimer,INTEGER,read-write,,mandatory,,The T22 Reset timer in milliseconds.
.1.3.6.1.2.1.10.5.1.1.8,RFC1382-MIB::x25AdmnClearTimer,INTEGER,read-write,,mandatory,,The T23 Clear timer in milliseconds.
.1.3.6.1.2.1.10.5.1.1.9,RFC1382-MIB::x25AdmnWindowTimer,INTEGER,read-write,,mandatory,,The T24 window status transmission timer in milliseconds. A value of 2147483647 indicates no window timer in use.
.1.3.6.1.2.1.10.5.1.1.10,RFC1382-MIB::x25AdmnDataRxmtTimer,INTEGER,read-write,,mandatory,,The T25 data retransmission timer in milliseconds. A value of 2147483647 indicates no data retransmission timer in use.
.1.3.6.1.2.1.10.5.1.1.11,RFC1382-MIB::x25AdmnInterruptTimer,INTEGER,read-write,,mandatory,,The T26 interrupt timer in milliseconds. A value of 2147483647 indicates no interrupt timer in use.
.1.3.6.1.2.1.10.5.1.1.12,RFC1382-MIB::x25AdmnRejectTimer,INTEGER,read-write,,mandatory,,The T27 Reject retransmission timer in milliseconds. A value of 2147483647 indicates no reject timer in use.
.1.3.6.1.2.1.10.5.1.1.13,RFC1382-MIB::x25AdmnRegistrationRequestTimer,INTEGER,read-write,,mandatory,,The T28 registration timer in milliseconds. A value of 2147483647 indicates no registration timer in use.
.1.3.6.1.2.1.10.5.1.1.14,RFC1382-MIB::x25AdmnMinimumRecallTimer,INTEGER,read-write,,mandatory,,Minimum time interval between unsuccessful call attempts in milliseconds.
.1.3.6.1.2.1.10.5.1.1.15,RFC1382-MIB::x25AdmnRestartCount,INTEGER,read-write,,mandatory,,The R20 restart retransmission count.
.1.3.6.1.2.1.10.5.1.1.16,RFC1382-MIB::x25AdmnResetCount,INTEGER,read-write,,mandatory,,The r22 Reset retransmission count.
.1.3.6.1.2.1.10.5.1.1.17,RFC1382-MIB::x25AdmnClearCount,INTEGER,read-write,,mandatory,,The r23 Clear retransmission count.
.1.3.6.1.2.1.10.5.1.1.18,RFC1382-MIB::x25AdmnDataRxmtCount,INTEGER,read-write,,mandatory,,The R25 Data retransmission count. This value is irrelevant if the x25AdmnDataRxmtTimer indicates no timer in use.
.1.3.6.1.2.1.10.5.1.1.19,RFC1382-MIB::x25AdmnRejectCount,INTEGER,read-write,,mandatory,,The R27 reject retransmission count. This value is irrelevant if the x25AdmnRejectTimer indicates no timer in use.
.1.3.6.1.2.1.10.5.1.1.20,RFC1382-MIB::x25AdmnRegistrationRequestCount,INTEGER,read-write,,mandatory,,The R28 Registration retransmission Count. This value is irrelevant if the x25AdmnRegistrationRequestTimer indicates no timer in use.
.1.3.6.1.2.1.10.5.1.1.21,RFC1382-MIB::x25AdmnNumberPVCs,INTEGER,read-write,,mandatory,,The number of PVC configured for this PLE. The PVCs use channel numbers from 1 to this number.
.1.3.6.1.2.1.10.5.1.1.22,RFC1382-MIB::x25AdmnDefCallParamId,OBJECT,read-write,,mandatory,,This identifies the instance of the x25CallParmIndex for the entry in the x25CallParmTable which contains the default call parameters for this PLE.
.1.3.6.1.2.1.10.5.1.1.23,RFC1382-MIB::x25AdmnLocalAddress,OCTET,read-write,,mandatory,,The local address for this PLE subnetwork. A zero length address maybe returned by PLEs that only support PVCs.
.1.3.6.1.2.1.10.5.1.1.24,RFC1382-MIB::x25AdmnProtocolVersionSupported,OBJECT,read-write,,mandatory,,Identifies the version of the X.25 protocol this interface should support. Object identifiers for common versions are defined below in the x25ProtocolVersion subtree.
.1.3.6.1.2.1.10.5.2,RFC1382-MIB::x25OperTable,,not-accessible,,mandatory,,The operation parameters in use by the X.25 PLE.
.1.3.6.1.2.1.10.5.2.1,RFC1382-MIB::x25OperEntry,,not-accessible,x25OperIndex,mandatory,,Entries of x25OperTable.
.1.3.6.1.2.1.10.5.2.1.1,RFC1382-MIB::x25OperIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the X.25 interface.
.1.3.6.1.2.1.10.5.2.1.2,RFC1382-MIB::x25OperInterfaceMode,INTEGER,read-only,,mandatory,dte(1):dce(2):dxe(3),Identifies DCE/DTE mode in which the interface operates. A value of dxe indicates the role will be determined by XID negotiation at the Link Layer and that negotiation has not yet taken place.
.1.3.6.1.2.1.10.5.2.1.3,RFC1382-MIB::x25OperMaxActiveCircuits,INTEGER,read-only,,mandatory,,Maximum number of circuits this PLE can support.
.1.3.6.1.2.1.10.5.2.1.4,RFC1382-MIB::x25OperPacketSequencing,INTEGER,read-only,,mandatory,modulo8(1):modulo128(2),The modulus of the packet sequence number space.
.1.3.6.1.2.1.10.5.2.1.5,RFC1382-MIB::x25OperRestartTimer,INTEGER,read-only,,mandatory,,The T20 restart timer in milliseconds.
.1.3.6.1.2.1.10.5.2.1.6,RFC1382-MIB::x25OperCallTimer,INTEGER,read-only,,mandatory,,The T21 Call timer in milliseconds.
.1.3.6.1.2.1.10.5.2.1.7,RFC1382-MIB::x25OperResetTimer,INTEGER,read-only,,mandatory,,The T22 Reset timer in milliseconds.
.1.3.6.1.2.1.10.5.2.1.8,RFC1382-MIB::x25OperClearTimer,INTEGER,read-only,,mandatory,,The T23 Clear timer in milliseconds.
.1.3.6.1.2.1.10.5.2.1.9,RFC1382-MIB::x25OperWindowTimer,INTEGER,read-only,,mandatory,,The T24 window status transmission timer milliseconds. A value of 2147483647 indicates no window timer in use.
.1.3.6.1.2.1.10.5.2.1.10,RFC1382-MIB::x25OperDataRxmtTimer,INTEGER,read-only,,mandatory,,The T25 Data Retransmission timer in milliseconds. A value of 2147483647 indicates no data retransmission timer in use.
.1.3.6.1.2.1.10.5.2.1.11,RFC1382-MIB::x25OperInterruptTimer,INTEGER,read-only,,mandatory,,The T26 Interrupt timer in milliseconds. A value of 2147483647 indicates interrupts are not being used.
.1.3.6.1.2.1.10.5.2.1.12,RFC1382-MIB::x25OperRejectTimer,INTEGER,read-only,,mandatory,,The T27 Reject retransmission timer in milliseconds. A value of 2147483647 indicates no reject timer in use.
.1.3.6.1.2.1.10.5.2.1.13,RFC1382-MIB::x25OperRegistrationRequestTimer,INTEGER,read-only,,mandatory,,The T28 registration timer in milliseconds. A value of 2147483647 indicates no registration timer in use.
.1.3.6.1.2.1.10.5.2.1.14,RFC1382-MIB::x25OperMinimumRecallTimer,INTEGER,read-only,,mandatory,,Minimum time interval between unsuccessful call attempts in milliseconds.
.1.3.6.1.2.1.10.5.2.1.15,RFC1382-MIB::x25OperRestartCount,INTEGER,read-only,,mandatory,,The R20 restart retransmission count.
.1.3.6.1.2.1.10.5.2.1.16,RFC1382-MIB::x25OperResetCount,INTEGER,read-only,,mandatory,,The r22 Reset retransmission count.
.1.3.6.1.2.1.10.5.2.1.17,RFC1382-MIB::x25OperClearCount,INTEGER,read-only,,mandatory,,The r23 Clear retransmission count.
.1.3.6.1.2.1.10.5.2.1.18,RFC1382-MIB::x25OperDataRxmtCount,INTEGER,read-only,,mandatory,,The R25 Data retransmission count. This value is undefined if the x25OperDataRxmtTimer indicates no timer in use.
.1.3.6.1.2.1.10.5.2.1.19,RFC1382-MIB::x25OperRejectCount,INTEGER,read-only,,mandatory,,The R27 reject retransmission count. This value is undefined if the x25OperRejectTimer indicates no timer in use.
.1.3.6.1.2.1.10.5.2.1.20,RFC1382-MIB::x25OperRegistrationRequestCount,INTEGER,read-only,,mandatory,,The R28 Registration retransmission Count. This value is undefined if the x25OperREgistrationRequestTimer indicates no timer in use.
.1.3.6.1.2.1.10.5.2.1.21,RFC1382-MIB::x25OperNumberPVCs,INTEGER,read-only,,mandatory,,The number of PVC configured for this PLE. The PVCs use channel numbers from 1 to this number.
.1.3.6.1.2.1.10.5.2.1.22,RFC1382-MIB::x25OperDefCallParamId,OBJECT,read-only,,mandatory,,This identifies the instance of the x25CallParmIndex for the entry in the x25CallParmTable that contains the default call parameters for this PLE.
.1.3.6.1.2.1.10.5.2.1.23,RFC1382-MIB::x25OperLocalAddress,OCTET,read-only,,mandatory,,The local address for this PLE subnetwork. A zero length address maybe returned by PLEs that only support PVCs.
.1.3.6.1.2.1.10.5.2.1.24,RFC1382-MIB::x25OperDataLinkId,OBJECT,read-only,,mandatory,,This identifies the instance of the index object in the first table of the most device specific MIB for the interface used by this PLE.
.1.3.6.1.2.1.10.5.2.1.25,RFC1382-MIB::x25OperProtocolVersionSupported,OBJECT,read-only,,mandatory,,Identifies the version of the X.25 protocol this interface supports. Object identifiers for common versions are defined below in the x25ProtocolVersion subtree.
.1.3.6.1.2.1.10.5.3,RFC1382-MIB::x25StatTable,,not-accessible,,mandatory,,Statistics information about this X.25 PLE.
.1.3.6.1.2.1.10.5.3.1,RFC1382-MIB::x25StatEntry,,not-accessible,x25StatIndex,mandatory,,Entries of the x25StatTable.
.1.3.6.1.2.1.10.5.3.1.1,RFC1382-MIB::x25StatIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the X.25 interface.
.1.3.6.1.2.1.10.5.3.1.2,RFC1382-MIB::x25StatInCalls,Counter32,read-only,,mandatory,,The number of incoming calls received.
.1.3.6.1.2.1.10.5.3.1.3,RFC1382-MIB::x25StatInCallRefusals,Counter32,read-only,,mandatory,,The number of incoming calls refused. This includes calls refused by the PLE and by higher layers. This also includes calls cleared because of restricted fast select.
.1.3.6.1.2.1.10.5.3.1.4,RFC1382-MIB::x25StatInProviderInitiatedClears,Counter32,read-only,,mandatory,,The number of clear requests with a cause code other than DTE initiated.
.1.3.6.1.2.1.10.5.3.1.5,RFC1382-MIB::x25StatInRemotelyInitiatedResets,Counter32,read-only,,mandatory,,The number of reset requests received with cause code DTE initiated.
.1.3.6.1.2.1.10.5.3.1.6,RFC1382-MIB::x25StatInProviderInitiatedResets,Counter32,read-only,,mandatory,,The number of reset requests received with cause code other than DTE initiated.
.1.3.6.1.2.1.10.5.3.1.7,RFC1382-MIB::x25StatInRestarts,Counter32,read-only,,mandatory,,The number of remotely initiated (including provider initiated) restarts experienced by the PLE excluding the restart associated with bringing up the PLE interface. This only counts restarts received when the PLE already has an established connection with the remove PLE.
.1.3.6.1.2.1.10.5.3.1.8,RFC1382-MIB::x25StatInDataPackets,Counter32,read-only,,mandatory,,The number of data packets received.
.1.3.6.1.2.1.10.5.3.1.9,RFC1382-MIB::x25StatInAccusedOfProtocolErrors,Counter32,read-only,,mandatory,,The number of packets received containing a procedure error cause code. These include clear, reset, restart, or diagnostic packets.
.1.3.6.1.2.1.10.5.3.1.10,RFC1382-MIB::x25StatInInterrupts,Counter32,read-only,,mandatory,,The number of interrupt packets received by the PLE or over the PVC/VC.
.1.3.6.1.2.1.10.5.3.1.11,RFC1382-MIB::x25StatOutCallAttempts,Counter32,read-only,,mandatory,,The number of calls attempted.
.1.3.6.1.2.1.10.5.3.1.12,RFC1382-MIB::x25StatOutCallFailures,Counter32,read-only,,mandatory,,The number of call attempts which failed. This includes calls that were cleared because of restrictive fast select.
.1.3.6.1.2.1.10.5.3.1.13,RFC1382-MIB::x25StatOutInterrupts,Counter32,read-only,,mandatory,,The number of interrupt packets send by the PLE or over the PVC/VC.
.1.3.6.1.2.1.10.5.3.1.14,RFC1382-MIB::x25StatOutDataPackets,Counter32,read-only,,mandatory,,The number of data packets sent by this PLE.
.1.3.6.1.2.1.10.5.3.1.15,RFC1382-MIB::x25StatOutgoingCircuits,Gauge32,read-only,,mandatory,,The number of active outgoing circuits. This includes call requests sent but not yet confirmed. This does not count PVCs.
.1.3.6.1.2.1.10.5.3.1.16,RFC1382-MIB::x25StatIncomingCircuits,Gauge32,read-only,,mandatory,,The number of active Incoming Circuits. This includes call indications received but not yet acknowledged. This does not count PVCs.
.1.3.6.1.2.1.10.5.3.1.17,RFC1382-MIB::x25StatTwowayCircuits,Gauge32,read-only,,mandatory,,The number of active two-way Circuits. This includes call requests sent but not yet confirmed. This does not count PVCs.
.1.3.6.1.2.1.10.5.3.1.18,RFC1382-MIB::x25StatRestartTimeouts,Counter32,read-only,,mandatory,,The number of times the T20 restart timer expired.
.1.3.6.1.2.1.10.5.3.1.19,RFC1382-MIB::x25StatCallTimeouts,Counter32,read-only,,mandatory,,The number of times the T21 call timer expired.
.1.3.6.1.2.1.10.5.3.1.20,RFC1382-MIB::x25StatResetTimeouts,Counter32,read-only,,mandatory,,The number of times the T22 reset timer expired.
.1.3.6.1.2.1.10.5.3.1.21,RFC1382-MIB::x25StatClearTimeouts,Counter32,read-only,,mandatory,,The number of times the T23 clear timer expired.
.1.3.6.1.2.1.10.5.3.1.22,RFC1382-MIB::x25StatDataRxmtTimeouts,Counter32,read-only,,mandatory,,The number of times the T25 data timer expired.
.1.3.6.1.2.1.10.5.3.1.23,RFC1382-MIB::x25StatInterruptTimeouts,Counter32,read-only,,mandatory,,The number of times the T26 interrupt timer expired.
.1.3.6.1.2.1.10.5.3.1.24,RFC1382-MIB::x25StatRetryCountExceededs,Counter32,read-only,,mandatory,,The number of times a retry counter was exhausted.
.1.3.6.1.2.1.10.5.3.1.25,RFC1382-MIB::x25StatClearCountExceededs,Counter32,read-only,,mandatory,,The number of times the R23 clear count was exceeded.
.1.3.6.1.2.1.10.5.4,RFC1382-MIB::x25ChannelTable,,not-accessible,,mandatory,,These objects contain information about the channel number configuration in an X.25 PLE. These values are the configured values. changes in these values after the interfaces has started may not be reflected in the operating PLE.
.1.3.6.1.2.1.10.5.4.1,RFC1382-MIB::x25ChannelEntry,,not-accessible,x25ChannelIndex,mandatory,,Entries of x25ChannelTable.
.1.3.6.1.2.1.10.5.4.1.1,RFC1382-MIB::x25ChannelIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the X.25 Interface.
.1.3.6.1.2.1.10.5.4.1.2,RFC1382-MIB::x25ChannelLIC,INTEGER,read-write,,mandatory,,Lowest Incoming channel.
.1.3.6.1.2.1.10.5.4.1.3,RFC1382-MIB::x25ChannelHIC,INTEGER,read-write,,mandatory,,Highest Incoming channel. A value of zero indicates no channels in this range.
.1.3.6.1.2.1.10.5.4.1.4,RFC1382-MIB::x25ChannelLTC,INTEGER,read-write,,mandatory,,Lowest Two-way channel.
.1.3.6.1.2.1.10.5.4.1.5,RFC1382-MIB::x25ChannelHTC,INTEGER,read-write,,mandatory,,Highest Two-way channel. A value of zero indicates no channels in this range.
.1.3.6.1.2.1.10.5.4.1.6,RFC1382-MIB::x25ChannelLOC,INTEGER,read-write,,mandatory,,Lowest outgoing channel.
.1.3.6.1.2.1.10.5.4.1.7,RFC1382-MIB::x25ChannelHOC,INTEGER,read-write,,mandatory,,Highest outgoing channel. A value of zero indicates no channels in this range.
.1.3.6.1.2.1.10.5.5,RFC1382-MIB::x25CircuitTable,,not-accessible,,mandatory,,These objects contain general information about a specific circuit of an X.25 PLE.
.1.3.6.1.2.1.10.5.5.1,RFC1382-MIB::x25CircuitEntry,,not-accessible,x25CircuitIndex:x25CircuitChannel,mandatory,,Entries of x25CircuitTable.
.1.3.6.1.2.1.10.5.5.1.1,RFC1382-MIB::x25CircuitIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the X.25 Interface.
.1.3.6.1.2.1.10.5.5.1.2,RFC1382-MIB::x25CircuitChannel,INTEGER,read-only,,mandatory,,The channel number for this circuit.
.1.3.6.1.2.1.10.5.5.1.3,RFC1382-MIB::x25CircuitStatus,INTEGER,read-write,,mandatory,invalid(1):closed(2):calling(3):open(4):clearing(5):pvc(6):pvcResetting(7):startClear(8):startPvcResetting(9):other(10),This object reports the current status of the circuit. An existing instance of this object can only be set to startClear, startPvcResetting, or invalid. An instance with the value calling or open can only be set to startClear and that action will start clearing the circuit. An instance with the value PVC can only be set to startPvcResetting or invalid and that action resets the PVC or deletes the circuit respectively. The values startClear or startPvcResetting will never be returned by an agent. An attempt to set the status of an existing instance to a value other than one of these values will result in an error. A non-existing instance can be set to PVC to create a PVC if the implementation supports dynamic creation of PVCs. Some implementations may only allow creation and deletion of PVCs if the interface is down. Since the instance identifier will supply the PLE index and the channel number, setting this object alone supplies sufficient information to create the instance. All the DEFVAL clauses for the other objects of this table are appropriate for creating a PVC; PLEs creating entries for placed or accepted calls will use values appropriate for the call rather than the value of the DEFVAL clause. Two managers trying to create the same PVC can determine from the return code which manager succeeded and which failed (the failing manager fails because it can not set a value of PVC for an existing object). An entry in the closed or invalid state may be deleted or reused at the agent's convence. If the entry is kept in the closed state, the values of the parameters associated with the entry must be correct. Closed implies the values in the circuit table are correct. The value of invalid indicates the other values in the table are invalid. Many agents may never return a value of invalid because they dynamically allocate and free unused table entries. An agent for a statically configured systems can return invalid to indicate the entry has not yet been used so the counters contain no information.
.1.3.6.1.2.1.10.5.5.1.4,RFC1382-MIB::x25CircuitEstablishTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime when the channel was associated with this circuit. For outgoing SVCs, this is the time the first call packet was sent. For incoming SVCs, this is the time the call indication was received. For PVCs this is the time the PVC was able to pass data to a higher layer entity without loss of data.
.1.3.6.1.2.1.10.5.5.1.5,RFC1382-MIB::x25CircuitDirection,INTEGER,read-write,,mandatory,incoming(1):outgoing(2):pvc(3),The direction of the call that established this circuit.
.1.3.6.1.2.1.10.5.5.1.6,RFC1382-MIB::x25CircuitInOctets,Counter32,read-only,,mandatory,,The number of octets of user data delivered to upper layer.
.1.3.6.1.2.1.10.5.5.1.7,RFC1382-MIB::x25CircuitInPdus,Counter32,read-only,,mandatory,,The number of PDUs received for this circuit.
.1.3.6.1.2.1.10.5.5.1.8,RFC1382-MIB::x25CircuitInRemotelyInitiatedResets,Counter32,read-only,,mandatory,,The number of Resets received for this circuit with cause code of DTE initiated.
.1.3.6.1.2.1.10.5.5.1.9,RFC1382-MIB::x25CircuitInProviderInitiatedResets,Counter32,read-only,,mandatory,,The number of Resets received for this circuit with cause code other than DTE initiated.
.1.3.6.1.2.1.10.5.5.1.10,RFC1382-MIB::x25CircuitInInterrupts,Counter32,read-only,,mandatory,,The number of interrupt packets received for this circuit.
.1.3.6.1.2.1.10.5.5.1.11,RFC1382-MIB::x25CircuitOutOctets,Counter32,read-only,,mandatory,,The number of octets of user data sent for this circuit.
.1.3.6.1.2.1.10.5.5.1.12,RFC1382-MIB::x25CircuitOutPdus,Counter32,read-only,,mandatory,,The number of PDUs sent for this circuit.
.1.3.6.1.2.1.10.5.5.1.13,RFC1382-MIB::x25CircuitOutInterrupts,Counter32,read-only,,mandatory,,The number of interrupt packets sent on this circuit.
.1.3.6.1.2.1.10.5.5.1.14,RFC1382-MIB::x25CircuitDataRetransmissionTimeouts,Counter32,read-only,,mandatory,,The number of times the T25 data retransmission timer expired for this circuit.
.1.3.6.1.2.1.10.5.5.1.15,RFC1382-MIB::x25CircuitResetTimeouts,Counter32,read-only,,mandatory,,The number of times the T22 reset timer expired for this circuit.
.1.3.6.1.2.1.10.5.5.1.16,RFC1382-MIB::x25CircuitInterruptTimeouts,Counter32,read-only,,mandatory,,The number of times the T26 Interrupt timer expired for this circuit.
.1.3.6.1.2.1.10.5.5.1.17,RFC1382-MIB::x25CircuitCallParamId,OBJECT,read-write,,mandatory,,This identifies the instance of the x25CallParmIndex for the entry in the x25CallParmTable which contains the call parameters in use with this circuit. The entry referenced must contain the values that are currently in use by the circuit rather than proposed values. A value of NULL indicates the circuit is a PVC or is using all the default parameters.
.1.3.6.1.2.1.10.5.5.1.18,RFC1382-MIB::x25CircuitCalledDteAddress,OCTET,read-write,,mandatory,,For incoming calls, this is the called address from the call indication packet. For outgoing calls, this is the called address from the call confirmation packet. This will be zero length for PVCs.
.1.3.6.1.2.1.10.5.5.1.19,RFC1382-MIB::x25CircuitCallingDteAddress,OCTET,read-write,,mandatory,,For incoming calls, this is the calling address from the call indication packet. For outgoing calls, this is the calling address from the call confirmation packet. This will be zero length for PVCs.
.1.3.6.1.2.1.10.5.5.1.20,RFC1382-MIB::x25CircuitOriginallyCalledAddress,OCTET,read-write,,mandatory,,For incoming calls, this is the address in the call Redirection or Call Deflection Notification facility if the call was deflected or redirected, otherwise it will be called address from the call indication packet. For outgoing calls, this is the address from the call request packet. This will be zero length for PVCs.
.1.3.6.1.2.1.10.5.5.1.21,RFC1382-MIB::x25CircuitDescr,OCTET,read-write,,mandatory,,A descriptive string associated with this circuit. This provides a place for the agent to supply any descriptive information it knows about the use or owner of the circuit. The agent may return the process identifier and user name for the process using the circuit. Alternative the agent may return the name of the configuration entry that caused a bridge to establish the circuit. A zero length value indicates the agent doesn't have any additional information.
.1.3.6.1.2.1.10.5.6,RFC1382-MIB::x25ClearedCircuitEntriesRequested,INTEGER,read-write,,mandatory,,The requested number of entries for the agent to keep in the x25ClearedCircuit table.
.1.3.6.1.2.1.10.5.7,RFC1382-MIB::x25ClearedCircuitEntriesGranted,INTEGER,read-only,,mandatory,,The actual number of entries the agent will keep in the x25ClearedCircuit Table.
.1.3.6.1.2.1.10.5.8,RFC1382-MIB::x25ClearedCircuitTable,,not-accessible,,mandatory,,A table of entries about closed circuits. Entries must be made in this table whenever circuits are closed and the close request or close indication packet contains a clearing cause other than DTE Originated or a Diagnostic code field other than Higher Layer Initiated disconnection-normal. An agent may optionally make entries for normal closes (to record closing facilities or other information). Agents will delete the oldest entry in the table when adding a new entry would exceed agent resources. Agents are required to keep the last entry put in the table and may keep more entries. The object x25OperClearEntriesGranted returns the maximum number of entries kept in the table.
.1.3.6.1.2.1.10.5.8.1,RFC1382-MIB::x25ClearedCircuitEntry,,not-accessible,x25ClearedCircuitIndex,mandatory,,Information about a cleared circuit.
.1.3.6.1.2.1.10.5.8.1.1,RFC1382-MIB::x25ClearedCircuitIndex,INTEGER,read-only,,mandatory,,An index that uniquely distinguishes one entry in the clearedCircuitTable from another. This index will start at 2147483647 and will decrease by one for each new entry added to the table. Upon reaching one, the index will reset to 2147483647. Because the index starts at 2147483647 and decreases, a manager may do a getnext on entry zero and obtain the most recent entry. When the index has the value of 1, the next entry will delete all entries in the table and that entry will be numbered 2147483647.
.1.3.6.1.2.1.10.5.8.1.2,RFC1382-MIB::x25ClearedCircuitPleIndex,INTEGER,read-only,,mandatory,,The value of ifIndex for the PLE which cleared the circuit that created the entry.
.1.3.6.1.2.1.10.5.8.1.3,RFC1382-MIB::x25ClearedCircuitTimeEstablished,TimeTicks,read-only,,mandatory,,The value of sysUpTime when the circuit was established. This will be the same value that was in the x25CircuitEstablishTime for the circuit.
.1.3.6.1.2.1.10.5.8.1.4,RFC1382-MIB::x25ClearedCircuitTimeCleared,TimeTicks,read-only,,mandatory,,The value of sysUpTime when the circuit was cleared. For locally initiated clears, this will be the time when the clear confirmation was received. For remotely initiated clears, this will be the time when the clear indication was received.
.1.3.6.1.2.1.10.5.8.1.5,RFC1382-MIB::x25ClearedCircuitChannel,INTEGER,read-only,,mandatory,,The channel number for the circuit that was cleared.
.1.3.6.1.2.1.10.5.8.1.6,RFC1382-MIB::x25ClearedCircuitClearingCause,INTEGER,read-only,,mandatory,,The Clearing Cause from the clear request or clear indication packet that cleared the circuit.
.1.3.6.1.2.1.10.5.8.1.7,RFC1382-MIB::x25ClearedCircuitDiagnosticCode,INTEGER,read-only,,mandatory,,The Diagnostic Code from the clear request or clear indication packet that cleared the circuit.
.1.3.6.1.2.1.10.5.8.1.8,RFC1382-MIB::x25ClearedCircuitInPdus,Counter32,read-only,,mandatory,,The number of PDUs received on the circuit.
.1.3.6.1.2.1.10.5.8.1.9,RFC1382-MIB::x25ClearedCircuitOutPdus,Counter32,read-only,,mandatory,,The number of PDUs transmitted on the circuit.
.1.3.6.1.2.1.10.5.8.1.10,RFC1382-MIB::x25ClearedCircuitCalledAddress,OCTET,read-only,,mandatory,,The called address from the cleared circuit.
.1.3.6.1.2.1.10.5.8.1.11,RFC1382-MIB::x25ClearedCircuitCallingAddress,OCTET,read-only,,mandatory,,The calling address from the cleared circuit.
.1.3.6.1.2.1.10.5.8.1.12,RFC1382-MIB::x25ClearedCircuitClearFacilities,OCTET,read-only,,mandatory,,The facilities field from the clear request or clear indication packet that cleared the circuit. A size of zero indicates no facilities were present.
.1.3.6.1.2.1.10.5.9,RFC1382-MIB::x25CallParmTable,,not-accessible,,mandatory,,These objects contain the parameters that can be varied between X.25 calls. The entries in this table are independent of the PLE. There exists only one of these tables for the entire system. The indexes for the entries are independent of any PLE or any circuit. Other tables reference entries in this table. Entries in this table can be used for default PLE parameters, for parameters to use to place/answer a call, for the parameters currently in use for a circuit, or parameters that were used by a circuit. The number of references to a given set of parameters can be found in the x25CallParmRefCount object sharing the same instance identifier with the parameters. The value of this reference count also affects the access of the objects in this table. An object in this table with the same instance identifier as the instance identifier of an x25CallParmRefCount must be consider associated with that reference count. An object with an associated reference count of zero can be written (if its ACCESS clause allows it). An object with an associated reference count greater than zero can not be written (regardless of the ACCESS clause). This ensures that a set of call parameters being referenced from another table can not be modified or changed in a ways inappropriate for continued use by that table.
.1.3.6.1.2.1.10.5.9.1,RFC1382-MIB::x25CallParmEntry,,not-accessible,x25CallParmIndex,mandatory,,Entries of x25CallParmTable.
.1.3.6.1.2.1.10.5.9.1.1,RFC1382-MIB::x25CallParmIndex,INTEGER,read-only,,mandatory,,A value that distinguishes this entry from another entry. Entries in this table are referenced from other objects which identify call parameters. It is impossible to know which other objects in the MIB reference entries in the table by looking at this table. Because of this, changes to parameters must be accomplished by creating a new entry in this table and then changing the referencing table to identify the new entry. Note that an agent will only use the values in this table when another table is changed to reference those values. The number of other tables that reference an index object in this table can be found in x25CallParmRefCount. The value of the reference count will affect the writability of the objects as explained above. Entries in this table which have a reference count of zero maybe deleted at the convence of the agent. Care should be taken by the agent to give the NMS sufficient time to create a reference to newly created entries. Should a Management Station not find a free index with which to create a new entry, it may feel free to delete entries with a reference count of zero. However in doing so the Management Station much realize it may impact other Management Stations.
.1.3.6.1.2.1.10.5.9.1.2,RFC1382-MIB::x25CallParmStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this call parameter entry. See RFC 1271 for details of usage.
.1.3.6.1.2.1.10.5.9.1.3,RFC1382-MIB::x25CallParmRefCount,INTEGER,read-only,,mandatory,,The number of references know by a management station to exist to this set of call parameters. This is the number of other objects that have returned a value of, and will return a value of, the index for this set of call parameters. Examples of such objects are the x25AdmnDefCallParamId, x25OperDataLinkId, or x25AdmnDefCallParamId objects defined above.
.1.3.6.1.2.1.10.5.9.1.4,RFC1382-MIB::x25CallParmInPacketSize,INTEGER,read-write,,mandatory,,The maximum receive packet size in octets for a circuit. A size of zero for a circuit means use the PLE default size. A size of zero for the PLE means use a default size of 128.
.1.3.6.1.2.1.10.5.9.1.5,RFC1382-MIB::x25CallParmOutPacketSize,INTEGER,read-write,,mandatory,,The maximum transmit packet size in octets for a circuit. A size of zero for a circuit means use the PLE default size. A size of zero for the PLE default means use a default size of 128.
.1.3.6.1.2.1.10.5.9.1.6,RFC1382-MIB::x25CallParmInWindowSize,INTEGER,read-write,,mandatory,,The receive window size for a circuit. A size of zero for a circuit means use the PLE default size. A size of zero for the PLE default means use 2.
.1.3.6.1.2.1.10.5.9.1.7,RFC1382-MIB::x25CallParmOutWindowSize,INTEGER,read-write,,mandatory,,The transmit window size for a circuit. A size of zero for a circuit means use the PLE default size. A size of zero for the PLE default means use 2.
.1.3.6.1.2.1.10.5.9.1.8,RFC1382-MIB::x25CallParmAcceptReverseCharging,INTEGER,read-write,,mandatory,default(1):accept(2):refuse(3):neverAccept(4),An enumeration defining if the PLE will accept or refuse charges. A value of default for a circuit means use the PLE default value. A value of neverAccept is only used for the PLE default and indicates the PLE will never accept reverse charging. A value of default for a PLE default means refuse.
.1.3.6.1.2.1.10.5.9.1.9,RFC1382-MIB::x25CallParmProposeReverseCharging,INTEGER,read-write,,mandatory,default(1):reverse(2):local(3),An enumeration defining if the PLE should propose reverse or local charging. The value of default for a circuit means use the PLE default. The value of default for the PLE default means use local.
.1.3.6.1.2.1.10.5.9.1.10,RFC1382-MIB::x25CallParmFastSelect,INTEGER,read-write,,mandatory,default(1):notSpecified(2):fastSelect(3):restrictedFastResponse(4):noFastSelect(5):noRestrictedFastResponse(6),Expresses preference for use of fast select facility. The value of default for a circuit is the PLE default. A value of default for the PLE means noFastSelect. A value of noFastSelect or noRestrictedFastResponse indicates a circuit may not use fast select or restricted fast response.
.1.3.6.1.2.1.10.5.9.1.11,RFC1382-MIB::x25CallParmInThruPutClasSize,INTEGER,read-write,,mandatory,tcReserved1(1):tcReserved2(2):tc75(3):tc150(4):tc300(5):tc600(6):tc1200(7):tc2400(8):tc4800(9):tc9600(10):tc19200(11):tc48000(12):tc64000(13):tcReserved14(14):tcReserved15(15):tcReserved0(16):tcNone(17):tcDefault(18),The incoming throughput class to negotiate. A value of tcDefault for a circuit means use the PLE default. A value of tcDefault for the PLE default means tcNone. A value of tcNone means do not negotiate throughtput class.
.1.3.6.1.2.1.10.5.9.1.12,RFC1382-MIB::x25CallParmOutThruPutClasSize,INTEGER,read-write,,mandatory,tcReserved1(1):tcReserved2(2):tc75(3):tc150(4):tc300(5):tc600(6):tc1200(7):tc2400(8):tc4800(9):tc9600(10):tc19200(11):tc48000(12):tc64000(13):tcReserved14(14):tcReserved15(15):tcReserved0(16):tcNone(17):tcDefault(18),The outgoing throughput class to negotiate. A value of tcDefault for a circuit means use the PLE default. A value of tcDefault for the PLE default means use tcNone. A value of tcNone means do not negotiate throughtput class.
.1.3.6.1.2.1.10.5.9.1.13,RFC1382-MIB::x25CallParmCug,OCTET,read-write,,mandatory,,The Closed User Group to specify. This consists of two or four octets containing the characters 0 through 9. A zero length string indicates no facility requested. A string length of three containing the characters DEF for a circuit means use the PLE default, (the PLE default parameter may not reference an entry of DEF.)
.1.3.6.1.2.1.10.5.9.1.14,RFC1382-MIB::x25CallParmCugoa,OCTET,read-write,,mandatory,,The Closed User Group with Outgoing Access to specify. This consists of two or four octets containing the characters 0 through 9. A string length of three containing the characters DEF for a circuit means use the PLE default (the PLE default parameters may not reference an entry of DEF). A zero length string indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.15,RFC1382-MIB::x25CallParmBcug,OCTET,read-write,,mandatory,,The Bilateral Closed User Group to specify. This consists of two octets containing the characters 0 through 9. A string length of three containing the characters DEF for a circuit means use the PLE default (the PLE default parameter may not reference an entry of DEF). A zero length string indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.16,RFC1382-MIB::x25CallParmNui,OCTET,read-write,,mandatory,,The Network User Identifier facility. This is binary value to be included immediately after the length field. The PLE will supply the length octet. A zero length string indicates no facility requested. This value is ignored for the PLE default parameters entry.
.1.3.6.1.2.1.10.5.9.1.17,RFC1382-MIB::x25CallParmChargingInfo,INTEGER,read-write,,mandatory,default(1):noFacility(2):noChargingInfo(3):chargingInfo(4),The charging Information facility. A value of default for a circuit means use the PLE default. The value of default for the default PLE parameters means use noFacility. The value of noFacility means do not include a facility.
.1.3.6.1.2.1.10.5.9.1.18,RFC1382-MIB::x25CallParmRpoa,OCTET,read-write,,mandatory,,The RPOA facility. The octet string contains n * 4 sequences of the characters 0-9 to specify a facility with n entries. The octet string containing the 3 characters DEF for a circuit specifies use of the PLE default (the entry for the PLE default may not contain DEF). A zero length string indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.19,RFC1382-MIB::x25CallParmTrnstDly,INTEGER,read-write,,mandatory,,The Transit Delay Selection and Indication value. A value of 65536 indicates no facility requested. A value of 65537 for a circuit means use the PLE default (the PLE default parameters entry may not use the value 65537). The value 65535 may only be used to indicate the value in use by a circuit.
.1.3.6.1.2.1.10.5.9.1.20,RFC1382-MIB::x25CallParmCallingExt,OCTET,read-write,,mandatory,,The Calling Extension facility. This contains one of the following: A sequence of hex digits with the value to be put in the facility. These digits will be converted to binary by the agent and put in the facility. These octets do not include the length octet. A value containing the three character DEF for a circuit means use the PLE default, (the entry for the PLE default parameters may not use the value DEF). A zero length string indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.21,RFC1382-MIB::x25CallParmCalledExt,OCTET,read-write,,mandatory,,The Called Extension facility. This contains one of the following: A sequence of hex digits with the value to be put in the facility. These digits will be converted to binary by the agent and put in the facility. These octets do not include the length octet. A value containing the three character DEF for a circuit means use the PLE default, (the entry for the PLE default parameters may not use the value DEF). A zero length string indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.22,RFC1382-MIB::x25CallParmInMinThuPutCls,INTEGER,read-write,,mandatory,,The minimum input throughput Class. A value of 16 for a circuit means use the PLE default (the PLE parameters entry may not use this value). A value of 17 indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.23,RFC1382-MIB::x25CallParmOutMinThuPutCls,INTEGER,read-write,,mandatory,,The minimum output throughput Class. A value of 16 for a circuit means use the PLE default (the PLE parameters entry may not use this value). A value of 17 indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.24,RFC1382-MIB::x25CallParmEndTrnsDly,OCTET,read-write,,mandatory,,The End-to-End Transit Delay to negotiate. An octet string of length 2, 4, or 6 contains the facility encoded as specified in ISO/IEC 8208 section 15.3.2.4. An octet string of length 3 containing the three character DEF for a circuit means use the PLE default (the entry for the PLE default can not contain the characters DEF). A zero length string indicates no facility requested.
.1.3.6.1.2.1.10.5.9.1.25,RFC1382-MIB::x25CallParmPriority,OCTET,read-write,,mandatory,,The priority facility to negotiate. The octet string encoded as specified in ISO/IEC 8208 section 15.3.2.5. A zero length string indicates no facility requested. The entry for the PLE default parameters must be zero length.
.1.3.6.1.2.1.10.5.9.1.26,RFC1382-MIB::x25CallParmProtection,OCTET,read-write,,mandatory,,A string contains the following: A hex string containing the value for the protection facility. This will be converted from hex to the octets actually in the packet by the agent. The agent will supply the length field and the length octet is not contained in this string. An string containing the 3 characters DEF for a circuit means use the PLE default (the entry for the PLE default parameters may not use the value DEF). A zero length string mean no facility requested.
.1.3.6.1.2.1.10.5.9.1.27,RFC1382-MIB::x25CallParmExptData,INTEGER,read-write,,mandatory,default(1):noExpeditedData(2):expeditedData(3),The Expedited Data facility to negotiate. A value of default for a circuit means use the PLE default value. The entry for the PLE default parameters may not have the value default.
.1.3.6.1.2.1.10.5.9.1.28,RFC1382-MIB::x25CallParmUserData,OCTET,read-write,,mandatory,,The call user data as placed in the packet. A zero length string indicates no call user data. If both the circuit call parameters and the PLE default have call user data defined, the data from the circuit call parameters will be used. If only the PLE has data defined, the PLE entry will be used. If neither the circuit call parameters or the PLE default entry has a value, no call user data will be sent.
.1.3.6.1.2.1.10.5.9.1.29,RFC1382-MIB::x25CallParmCallingNetworkFacilities,OCTET,read-write,,mandatory,,The calling network facilities. The facilities are encoded here exactly as encoded in the call packet. These facilities do not include the marker facility code. A zero length string in the entry for the parameter to use when establishing a circuit means use the PLE default. A zero length string in the entry for PLE default parameters indicates no default facilities.
.1.3.6.1.2.1.10.5.9.1.30,RFC1382-MIB::x25CallParmCalledNetworkFacilities,OCTET,read-write,,mandatory,,The called network facilities. The facilities are encoded here exactly as encoded in the call packet. These facilities do not include the marker facility code. A zero length string in the entry for the parameter to use when establishing a circuit means use the PLE default. A zero length string in the entry for PLE default parameters indicates no default facilities.
.1.3.6.1.2.1.10.5.10,RFC1382-MIB::x25ProtocolVersion,,,,,,
.1.3.6.1.2.1.10.5.10.1,RFC1382-MIB::x25protocolCcittV1976,,,,,,
.1.3.6.1.2.1.10.5.10.2,RFC1382-MIB::x25protocolCcittV1980,,,,,,
.1.3.6.1.2.1.10.5.10.3,RFC1382-MIB::x25protocolCcittV1984,,,,,,
.1.3.6.1.2.1.10.5.10.4,RFC1382-MIB::x25protocolCcittV1988,,,,,,
.1.3.6.1.2.1.10.5.10.5,RFC1382-MIB::x25protocolIso8208V1987,,,,,,
.1.3.6.1.2.1.10.5.10.6,RFC1382-MIB::x25protocolIso8208V1989,,,,,,
.1.3.6.1.2.1.10.7,EtherLike-MIB::dot3,,,,,,
.1.3.6.1.2.1.10.7.2,EtherLike-MIB::dot3StatsTable,,not-accessible,,current,,Statistics for a collection of ethernet-like interfaces attached to a particular system. There will be one row in this table for each ethernet-like interface in the system.
.1.3.6.1.2.1.10.7.2.1,EtherLike-MIB::dot3StatsEntry,,not-accessible,dot3StatsIndex,current,,Statistics for a particular interface to an ethernet-like medium.
.1.3.6.1.2.1.10.7.2.1.1,EtherLike-MIB::dot3StatsIndex,Integer32,read-only,,current,,An index value that uniquely identifies an interface to an ethernet-like medium. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.10.7.2.1.2,EtherLike-MIB::dot3StatsAlignmentErrors,Counter32,read-only,,current,,A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. This counter does not increment for group encoding schemes greater than 4 bits per group. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsAlignmentErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.3,EtherLike-MIB::dot3StatsFCSErrors,Counter32,read-only,,current,,A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. Note: Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the frame to fail the FCS check. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsFCSErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.4,EtherLike-MIB::dot3StatsSingleCollisionFrames,Counter32,read-only,,current,,A count of frames that are involved in a single collision, and are subsequently transmitted successfully. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the dot3StatsMultipleCollisionFrames object. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.5,EtherLike-MIB::dot3StatsMultipleCollisionFrames,Counter32,read-only,,current,,A count of frames that are involved in more than one collision and are subsequently transmitted successfully. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts, and is not counted by the corresponding instance of the dot3StatsSingleCollisionFrames object. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.6,EtherLike-MIB::dot3StatsSQETestErrors,Counter32,read-only,,current,,A count of times that the SQE TEST ERROR is received on a particular interface. The SQE TEST ERROR is set in accordance with the rules for verification of the SQE detection mechanism in the PLS Carrier Sense Function as described in IEEE Std. 802.3, 2000 Edition, section 7.2.4.6. This counter does not increment on interfaces operating at speeds greater than 10 Mb/s, or on interfaces operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.7,EtherLike-MIB::dot3StatsDeferredTransmissions,Counter32,read-only,,current,,A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.8,EtherLike-MIB::dot3StatsLateCollisions,Counter32,read-only,,current,,The number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.9,EtherLike-MIB::dot3StatsExcessiveCollisions,Counter32,read-only,,current,,A count of frames for which transmission on a particular interface fails due to excessive collisions. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.10,EtherLike-MIB::dot3StatsInternalMacTransmitErrors,Counter32,read-only,,current,,A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors object. The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsInternalMacTransmitErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.11,EtherLike-MIB::dot3StatsCarrierSenseErrors,Counter32,read-only,,current,,The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.13,EtherLike-MIB::dot3StatsFrameTooLongs,Counter32,read-only,,current,,A count of frames received on a particular interface that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. For interfaces operating at 10 Gb/s, this counter can roll over in less than 80 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsFrameTooLongs object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.16,EtherLike-MIB::dot3StatsInternalMacReceiveErrors,Counter32,read-only,,current,,A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors object. The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsInternalMacReceiveErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.17,EtherLike-MIB::dot3StatsEtherChipSet,OBJECT,read-only,,deprecated,,******** THIS OBJECT IS DEPRECATED ******** This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of which chip to identify via this object. The implementor should identify the chip which is usually called the Medium Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip. This object has been deprecated. Implementation feedback indicates that it is of limited use for debugging network problems in the field, and the administrative overhead involved in maintaining a registry of chipset OIDs is not justified.
.1.3.6.1.2.1.10.7.2.1.18,EtherLike-MIB::dot3StatsSymbolErrors,Counter32,read-only,,current,,For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. This counter does not increment when the interface is operating at 10 Mb/s. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsSymbolErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.2.1.19,EtherLike-MIB::dot3StatsDuplexStatus,INTEGER,read-only,,current,unknown(1):halfDuplex(2):fullDuplex(3),The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy.
.1.3.6.1.2.1.10.7.2.1.20,EtherLike-MIB::dot3StatsRateControlAbility,INTEGER,read-only,,current,true(1):false(2),'true' for interfaces operating at speeds above 1000 Mb/s that support Rate Control through lowering the average data rate of the MAC sublayer, with frame granularity, and 'false' otherwise.
.1.3.6.1.2.1.10.7.2.1.21,EtherLike-MIB::dot3StatsRateControlStatus,INTEGER,read-only,,current,rateControlOff(1):rateControlOn(2):unknown(3),The current Rate Control mode of operation of the MAC sublayer of this interface.
.1.3.6.1.2.1.10.7.5,EtherLike-MIB::dot3CollTable,,not-accessible,,current,,A collection of collision histograms for a particular set of interfaces.
.1.3.6.1.2.1.10.7.5.1,EtherLike-MIB::dot3CollEntry,,not-accessible,ifIndex:dot3CollCount,current,,A cell in the histogram of per-frame collisions for a particular interface. An instance of this object represents the frequency of individual MAC frames for which the transmission (successful or otherwise) on a particular interface is accompanied by a particular number of media collisions.
.1.3.6.1.2.1.10.7.5.1.2,EtherLike-MIB::dot3CollCount,Integer32,not-accessible,,current,,The number of per-frame media collisions for which a particular collision histogram cell represents the frequency on a particular interface.
.1.3.6.1.2.1.10.7.5.1.3,EtherLike-MIB::dot3CollFrequencies,Counter32,read-only,,current,,A count of individual MAC frames for which the transmission (successful or otherwise) on a particular interface occurs after the frame has experienced exactly the number of collisions in the associated dot3CollCount object. For example, a frame which is transmitted on interface 77 after experiencing exactly 4 collisions would be indicated by incrementing only dot3CollFrequencies.77.4. No other instance of dot3CollFrequencies would be incremented in this example. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.6,EtherLike-MIB::dot3Tests,,,,,,
.1.3.6.1.2.1.10.7.6.1,EtherLike-MIB::dot3TestTdr,,,,,,******** THIS IDENTITY IS DEPRECATED ******* The Time-Domain Reflectometry (TDR) test is specific to ethernet-like interfaces of type 10Base5 and 10Base2. The TDR value may be useful in determining the approximate distance to a cable fault. It is advisable to repeat this test to check for a consistent resulting TDR value, to verify that there is a fault. A TDR test returns as its result the time interval, measured in 10 MHz ticks or 100 nsec units, between the start of TDR test transmission and the subsequent detection of a collision or deassertion of carrier. On successful completion of a TDR test, the result is stored as the value of an appropriate instance of an appropriate vendor specific MIB object, and the OBJECT IDENTIFIER of that instance is stored in the appropriate instance of the appropriate test result code object (thereby indicating where the result has been stored). This object identity has been deprecated, since the ifTestTable in the IF-MIB was deprecated, and there is no longer a standard mechanism for initiating an interface test. This left no standard way of using this object identity.
.1.3.6.1.2.1.10.7.6.2,EtherLike-MIB::dot3TestLoopBack,,,,,,******** THIS IDENTITY IS DEPRECATED ******* This test configures the MAC chip and executes an internal loopback test of memory, data paths, and the MAC chip logic. This loopback test can only be executed if the interface is offline. Once the test has completed, the MAC chip should be reinitialized for network operation, but it should remain offline. If an error occurs during a test, the appropriate test result object will be set to indicate a failure. The two OBJECT IDENTIFIER values dot3ErrorInitError and dot3ErrorLoopbackError may be used to provided more information as values for an appropriate test result code object. This object identity has been deprecated, since the ifTestTable in the IF-MIB was deprecated, and there is no longer a standard mechanism for initiating an interface test. This left no standard way of using this object identity.
.1.3.6.1.2.1.10.7.7,EtherLike-MIB::dot3Errors,,,,,,
.1.3.6.1.2.1.10.7.7.1,EtherLike-MIB::dot3ErrorInitError,,,,,,******** THIS IDENTITY IS DEPRECATED ******* Couldn't initialize MAC chip for test. This object identity has been deprecated, since the ifTestTable in the IF-MIB was deprecated, and there is no longer a standard mechanism for initiating an interface test. This left no standard way of using this object identity.
.1.3.6.1.2.1.10.7.7.2,EtherLike-MIB::dot3ErrorLoopbackError,,,,,,******** THIS IDENTITY IS DEPRECATED ******* Expected data not received (or not received correctly) in loopback test. This object identity has been deprecated, since the ifTestTable in the IF-MIB was deprecated, and there is no longer a standard mechanism for initiating an interface test. This left no standard way of using this object identity.
.1.3.6.1.2.1.10.7.8,ETHER-CHIPSET-MIB::dot3ChipSets,,,,,,
.1.3.6.1.2.1.10.7.8.1,ETHER-CHIPSET-MIB::dot3ChipSetAMD,,,,,,
.1.3.6.1.2.1.10.7.8.1.1,ETHER-CHIPSET-MIB::dot3ChipSetAMD7990,,,,,,The authoritative identifier for the Advanced Micro Devices Am7990 Local Area Network Controller for Ethernet (LANCE).
.1.3.6.1.2.1.10.7.8.1.2,ETHER-CHIPSET-MIB::dot3ChipSetAMD79900,,,,,,The authoritative identifier for the Advanced Micro Devices Am79900 chip.
.1.3.6.1.2.1.10.7.8.1.3,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C940,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C940 Media Access Controller for Ethernet (MACE).
.1.3.6.1.2.1.10.7.8.1.4,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C90,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C90 CMOS Local Area Network Controller for Ethernet (C-LANCE).
.1.3.6.1.2.1.10.7.8.1.5,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C960,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C960 PCnet-ISA Single Chip Ethernet Controller for ISA.
.1.3.6.1.2.1.10.7.8.1.6,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C961,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C961 PCnet-ISA+ Single Chip Plug & Play Full-Duplex Ethernet Controller for ISA.
.1.3.6.1.2.1.10.7.8.1.7,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C961A,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C961A PCnet-ISA II Single Chip Plug & Play Full-Duplex Ethernet Controller for ISA.
.1.3.6.1.2.1.10.7.8.1.8,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C965,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C965 PCnet-32 Single Chip Ethernet Controller for PCI.
.1.3.6.1.2.1.10.7.8.1.9,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C970,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C970 PCnet PCI Single Chip Ethernet Controller for PCI Local Bus.
.1.3.6.1.2.1.10.7.8.1.10,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C970A,,,,,,The authoritative identifier for the Advanced Micro Devices AM79C970A PCnet PCI II Single Chip Full-Duplex Ethernet Controller for PCI Local Bus.
.1.3.6.1.2.1.10.7.8.1.11,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C971,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C971 PCnet-FAST Single Chip Full-Duplex 10/100 Mbps Ethernet Controller for PCI Local Bus.
.1.3.6.1.2.1.10.7.8.1.12,ETHER-CHIPSET-MIB::dot3ChipSetAMD79C972,,,,,,The authoritative identifier for the Advanced Micro Devices Am79C972 PCnet-FAST+ Enhanced 10/100 Mbps PCI Ethernet Controller with OnNow Support.
.1.3.6.1.2.1.10.7.8.2,ETHER-CHIPSET-MIB::dot3ChipSetIntel,,,,,,
.1.3.6.1.2.1.10.7.8.2.1,ETHER-CHIPSET-MIB::dot3ChipSetIntel82586,,,,,,The authoritative identifier for the Intel 82586 IEEE 802.3 Ethernet LAN Coprocessor.
.1.3.6.1.2.1.10.7.8.2.2,ETHER-CHIPSET-MIB::dot3ChipSetIntel82596,,,,,,The authoritative identifier for the Intel 82596 High-Performance 32-Bit Local Area Network Coprocessor.
.1.3.6.1.2.1.10.7.8.2.3,ETHER-CHIPSET-MIB::dot3ChipSetIntel82595,,,,,,The authoritative identifier for the Intel 82595 High Integration Ethernet Controller.
.1.3.6.1.2.1.10.7.8.2.4,ETHER-CHIPSET-MIB::dot3ChipSetIntel82557,,,,,,The authoritative identifier for the Intel 82557 Fast Ethernet PCI Bus Lan Controller.
.1.3.6.1.2.1.10.7.8.2.5,ETHER-CHIPSET-MIB::dot3ChipSetIntel82558,,,,,,The authoritative identifier for the Intel 82558 Fast Ethernet PCI Bus LAN Controller with Integrated PHY.
.1.3.6.1.2.1.10.7.8.3,ETHER-CHIPSET-MIB::dot3ChipSetSeeq,,,,,,
.1.3.6.1.2.1.10.7.8.3.1,ETHER-CHIPSET-MIB::dot3ChipSetSeeq8003,,,,,,The authoritative identifier for the SEEQ 8003 chip set.
.1.3.6.1.2.1.10.7.8.3.2,ETHER-CHIPSET-MIB::dot3ChipSetSeeq80C03,,,,,,The authoritative identifier for the SEEQ 80C03 Full-Duplex CMOS Ethernet Data Link Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.3,ETHER-CHIPSET-MIB::dot3ChipSetSeeq84C30,,,,,,The authoritative identifier for the SEEQ 4-Port 84C30 Full-Duplex CMOS Ethernet 10 MBit/Sec Data Link Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.4,ETHER-CHIPSET-MIB::dot3ChipSetSeeq8431,,,,,,The authoritative identifier for the SEEQ 4-Port 8431 Full-Duplex CMOS Ethernet 10 MBit/Sec Data Link Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.5,ETHER-CHIPSET-MIB::dot3ChipSetSeeq80C300,,,,,,The authoritative identifier for the SEEQ 80C300 Full-Duplex CMOS Ethernet 10/100 Mbit/Sec Data Link Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.6,ETHER-CHIPSET-MIB::dot3ChipSetSeeq84C300,,,,,,The authoritative identifier for the SEEQ 4-Port 84C300 Fast Ethernet Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.7,ETHER-CHIPSET-MIB::dot3ChipSetSeeq84301,,,,,,The authoritative identifier for the SEEQ 4-Port 84301 Fast Ethernet Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.8,ETHER-CHIPSET-MIB::dot3ChipSetSeeq84302,,,,,,The authoritative identifier for the SEEQ 4-Port 84302 Fast Ethernet Controller (MAC).
.1.3.6.1.2.1.10.7.8.3.9,ETHER-CHIPSET-MIB::dot3ChipSetSeeq8100,,,,,,The authoritative identifier for the SEEQ 8100 Gigabit Ethernet Controller (MAC & PCS).
.1.3.6.1.2.1.10.7.8.4,ETHER-CHIPSET-MIB::dot3ChipSetNational,,,,,,
.1.3.6.1.2.1.10.7.8.4.1,ETHER-CHIPSET-MIB::dot3ChipSetNational8390,,,,,,The authoritative identifier for the National Semiconductor DP8390 Network Interface Controller.
.1.3.6.1.2.1.10.7.8.4.2,ETHER-CHIPSET-MIB::dot3ChipSetNationalSonic,,,,,,The authoritative identifier for the National Semiconductor DP83932 Systems-Oriented Network Interface Controller (SONIC).
.1.3.6.1.2.1.10.7.8.4.3,ETHER-CHIPSET-MIB::dot3ChipSetNational83901,,,,,,The authoritative identifier for the National Semiconductor DP83901 Serial Network Interface Controller (SNIC).
.1.3.6.1.2.1.10.7.8.4.4,ETHER-CHIPSET-MIB::dot3ChipSetNational83902,,,,,,The authoritative identifier for the National Semiconductor DP83902 Serial Network Interface Controller for Twisted Pair (ST-NIC).
.1.3.6.1.2.1.10.7.8.4.5,ETHER-CHIPSET-MIB::dot3ChipSetNational83905,,,,,,The authoritative identifier for the National Semiconductor DP83905 AT Local Area Network Twisted-Pair Interface (AT/LANTIC).
.1.3.6.1.2.1.10.7.8.4.6,ETHER-CHIPSET-MIB::dot3ChipSetNational83907,,,,,,The authoritative identifier for the National Semiconductor DP83907 AT Twisted-Pair Enhanced Coaxial Network Interface Controller (AT/LANTIC II).
.1.3.6.1.2.1.10.7.8.4.7,ETHER-CHIPSET-MIB::dot3ChipSetNational83916,,,,,,The authoritative identifier for the National Semiconductor DP83916 Systems-Oriented Network Interface Controller (SONIC-16).
.1.3.6.1.2.1.10.7.8.4.8,ETHER-CHIPSET-MIB::dot3ChipSetNational83934,,,,,,The authoritative identifier for the National Semiconductor DP83934 Systems-Oriented Network Interface Controller with Twisted Pair Interface (SONIC-T).
.1.3.6.1.2.1.10.7.8.4.9,ETHER-CHIPSET-MIB::dot3ChipSetNational83936,,,,,,The authoritative identifier for the National Semiconductor DP83936AVUL Full-Duplex Systems- Oriented Network Interface Controller with Twisted Pair Interface (SONIC-T).
.1.3.6.1.2.1.10.7.8.5,ETHER-CHIPSET-MIB::dot3ChipSetFujitsu,,,,,,
.1.3.6.1.2.1.10.7.8.5.1,ETHER-CHIPSET-MIB::dot3ChipSetFujitsu86950,,,,,,The authoritative identifier for the Fujitsu 86950 chip.
.1.3.6.1.2.1.10.7.8.5.2,ETHER-CHIPSET-MIB::dot3ChipSetFujitsu86960,,,,,,The authoritative identifier for the Fujitsu MB86960 Network Interface Controller with Encoder/Decoder (NICE).
.1.3.6.1.2.1.10.7.8.5.3,ETHER-CHIPSET-MIB::dot3ChipSetFujitsu86964,,,,,,The authoritative identifier for the Fujitsu MB86964 Ethernet Controller with 10BASE-T Tranceiver.
.1.3.6.1.2.1.10.7.8.5.4,ETHER-CHIPSET-MIB::dot3ChipSetFujitsu86965A,,,,,,The authoritative identifier for the Fujitsu MB86965A EtherCoupler Single-Chip Ethernet Controller.
.1.3.6.1.2.1.10.7.8.5.5,ETHER-CHIPSET-MIB::dot3ChipSetFujitsu86965B,,,,,,The authoritative identifier for the Fujitsu MB86965B EtherCoupler Single-Chip Ethernet Controller (supports full-duplex).
.1.3.6.1.2.1.10.7.8.6,ETHER-CHIPSET-MIB::dot3ChipSetDigital,,,,,,
.1.3.6.1.2.1.10.7.8.6.1,ETHER-CHIPSET-MIB::dot3ChipSetDigitalDC21040,,,,,,The authoritative identifier for the Digital Semiconductor DC21040 chip.
.1.3.6.1.2.1.10.7.8.6.2,ETHER-CHIPSET-MIB::dot3ChipSetDigital21041,,,,,,The authoritative identifier for the Digital Semiconductor 21041 PCI Ethernet LAN Controller.
.1.3.6.1.2.1.10.7.8.6.3,ETHER-CHIPSET-MIB::dot3ChipSetDigital21140,,,,,,The authoritative identifier for the Digital Semiconductor 21140 PCI Fast Ethernet LAN Controller.
.1.3.6.1.2.1.10.7.8.6.4,ETHER-CHIPSET-MIB::dot3ChipSetDigital21143,,,,,,The authoritative identifier for the Digital Semiconductor 21143 PCI/CardBus 10/100-Mb/s Ethernet LAN Controller.
.1.3.6.1.2.1.10.7.8.6.5,ETHER-CHIPSET-MIB::dot3ChipSetDigital21340,,,,,,The authoritative identifier for the Digital Semiconductor 21340 10/100-MB/s managed buffered port switch.
.1.3.6.1.2.1.10.7.8.6.6,ETHER-CHIPSET-MIB::dot3ChipSetDigital21440,,,,,,The authoritative identifier for the Digital Semiconductor 21440 Multiport 10/100Mbps Ethernet Controller.
.1.3.6.1.2.1.10.7.8.6.7,ETHER-CHIPSET-MIB::dot3ChipSetDigital21540,,,,,,The authoritative identifier for the Digital Semiconductor 21540 PCI/CardBus Ethernet LAN Controller with Modem Interface.
.1.3.6.1.2.1.10.7.8.7,ETHER-CHIPSET-MIB::dot3ChipSetTI,,,,,,
.1.3.6.1.2.1.10.7.8.7.1,ETHER-CHIPSET-MIB::dot3ChipSetTIE100,,,,,,The authoritative identifier for the Texas Instruments TNETE100 ThunderLAN PCI Fast Ethernet Controller.
.1.3.6.1.2.1.10.7.8.7.2,ETHER-CHIPSET-MIB::dot3ChipSetTIE110,,,,,,The authoritative identifier for the Texas Instruments TNETE110 ThunderLAN PCI 10BASE-T Ethernet Adapter.
.1.3.6.1.2.1.10.7.8.7.3,ETHER-CHIPSET-MIB::dot3ChipSetTIX3100,,,,,,The authoritative identifier for the Texas Instruments TNETX3100 Desktop ThunderSWITCH 8/2.
.1.3.6.1.2.1.10.7.8.7.4,ETHER-CHIPSET-MIB::dot3ChipSetTIX3150,,,,,,The authoritative identifier for the Texas Instruments TNETX3150 ThunderSWITCH 12/3.
.1.3.6.1.2.1.10.7.8.7.5,ETHER-CHIPSET-MIB::dot3ChipSetTIX3270,,,,,,The authoritative identifier for the Texas Instruments TNETX3270 ThunderSWITCH 24/3.
.1.3.6.1.2.1.10.7.8.8,ETHER-CHIPSET-MIB::dot3ChipSetToshiba,,,,,,
.1.3.6.1.2.1.10.7.8.8.1,ETHER-CHIPSET-MIB::dot3ChipSetToshibaTC35815F,,,,,,The authoritative identifier for the Toshiba TC35815F PCI-Based 100/10Mbps Ethernet Controller.
.1.3.6.1.2.1.10.7.8.9,ETHER-CHIPSET-MIB::dot3ChipSetLucent,,,,,,
.1.3.6.1.2.1.10.7.8.9.1,ETHER-CHIPSET-MIB::dot3ChipSetLucentATT1MX10,,,,,,The authoritative identifier for the Lucent Technologies ATT1MX10 (Spinnaker) Quad MAC and Tranceiver for Ethernet Frame Switching.
.1.3.6.1.2.1.10.7.8.9.2,ETHER-CHIPSET-MIB::dot3ChipSetLucentLUC3M08,,,,,,The authoritative identifier for the Lucent Technologies LUC3M08 Eight Ethernet MACs for 10/100 Mbits/s Frame Switching.
.1.3.6.1.2.1.10.7.8.10,ETHER-CHIPSET-MIB::dot3ChipSetGalileo,,,,,,
.1.3.6.1.2.1.10.7.8.10.1,ETHER-CHIPSET-MIB::dot3ChipSetGalileoGT48001,,,,,,The authoritative identifier for the Galileo Technology GT-48001A Switched Ethernet Controller.
.1.3.6.1.2.1.10.7.8.10.2,ETHER-CHIPSET-MIB::dot3ChipSetGalileoGT48002,,,,,,The authoritative identifier for the Galileo Technology GT-48002A Switched Fast Ethernet Controller.
.1.3.6.1.2.1.10.7.8.10.3,ETHER-CHIPSET-MIB::dot3ChipSetGalileoGT48004,,,,,,The authoritative identifier for the Galileo Technology GT-48004A Four Port Fast Ethernet Switch for Multiport 10/100BASE-X Systems.
.1.3.6.1.2.1.10.7.8.10.4,ETHER-CHIPSET-MIB::dot3ChipSetGalileoGT48207,,,,,,The authoritative identifier for the Galileo Technology GT-48207 Low-Cost 10 Port Switched Ethernet Controller for 10+10/100BASE-X.
.1.3.6.1.2.1.10.7.8.10.5,ETHER-CHIPSET-MIB::dot3ChipSetGalileoGT48208,,,,,,The authoritative identifier for the Galileo Technology GT-48208 Advanced 10 Port Switched Ethernet Controller for 10+10/100BASE-X.
.1.3.6.1.2.1.10.7.8.10.6,ETHER-CHIPSET-MIB::dot3ChipSetGalileoGT48212,,,,,,The authoritative identifier for the Galileo Technology GT-48212 Advanced 14 Port Switched Ethernet Controller for 10+10/100BASE-X.
.1.3.6.1.2.1.10.7.8.11,ETHER-CHIPSET-MIB::dot3ChipSetJato,,,,,,
.1.3.6.1.2.1.10.7.8.11.1,ETHER-CHIPSET-MIB::dot3ChipSetJatoJT1001,,,,,,The authoritative identifier for the Jato Technologies JT1001 GigEMAC Server 10/100/1000Mbps Ethernet Controller with PCI interface.
.1.3.6.1.2.1.10.7.8.12,ETHER-CHIPSET-MIB::dot3ChipSetXaQti,,,,,,
.1.3.6.1.2.1.10.7.8.12.1,ETHER-CHIPSET-MIB::dot3ChipSetXaQtiXQ11800FP,,,,,,The authoritative identifier for the XaQTI XQ11800FP XMAC II Gigabit Ethernet Media Access Controller.
.1.3.6.1.2.1.10.7.8.12.2,ETHER-CHIPSET-MIB::dot3ChipSetXaQtiXQ18110FP,,,,,,The authoritative identifier for the XaQTI XQ18110FP GigaPower Protocol Accelerator.
.1.3.6.1.2.1.10.7.9,EtherLike-MIB::dot3ControlTable,,not-accessible,,current,,A table of descriptive and status information about the MAC Control sublayer on the ethernet-like interfaces attached to a particular system. There will be one row in this table for each ethernet-like interface in the system which implements the MAC Control sublayer. If some, but not all, of the ethernet-like interfaces in the system implement the MAC Control sublayer, there will be fewer rows in this table than in the dot3StatsTable.
.1.3.6.1.2.1.10.7.9.1,EtherLike-MIB::dot3ControlEntry,,not-accessible,dot3StatsIndex,current,,An entry in the table, containing information about the MAC Control sublayer on a single ethernet-like interface.
.1.3.6.1.2.1.10.7.9.1.1,EtherLike-MIB::dot3ControlFunctionsSupported,BITS,read-only,,current,pause(0),A list of the possible MAC Control functions implemented for this interface.
.1.3.6.1.2.1.10.7.9.1.2,EtherLike-MIB::dot3ControlInUnknownOpcodes,Counter32,read-only,,current,,A count of MAC Control frames received on this interface that contain an opcode that is not supported by this device. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCControlInUnknownOpcodes object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.9.1.3,EtherLike-MIB::dot3HCControlInUnknownOpcodes,Counter64,read-only,,current,,A count of MAC Control frames received on this interface that contain an opcode that is not supported by this device. This counter is a 64 bit version of dot3ControlInUnknownOpcodes. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.10,EtherLike-MIB::dot3PauseTable,,not-accessible,,current,,A table of descriptive and status information about the MAC Control PAUSE function on the ethernet-like interfaces attached to a particular system. There will be one row in this table for each ethernet-like interface in the system which supports the MAC Control PAUSE function (i.e., the 'pause' bit in the corresponding instance of dot3ControlFunctionsSupported is set). If some, but not all, of the ethernet-like interfaces in the system implement the MAC Control PAUSE function (for example, if some interfaces only support half-duplex), there will be fewer rows in this table than in the dot3StatsTable.
.1.3.6.1.2.1.10.7.10.1,EtherLike-MIB::dot3PauseEntry,,not-accessible,dot3StatsIndex,current,,An entry in the table, containing information about the MAC Control PAUSE function on a single ethernet-like interface.
.1.3.6.1.2.1.10.7.10.1.1,EtherLike-MIB::dot3PauseAdminMode,INTEGER,read-write,,current,disabled(1):enabledXmit(2):enabledRcv(3):enabledXmitAndRcv(4),This object is used to configure the default administrative PAUSE mode for this interface. This object represents the administratively-configured PAUSE mode for this interface. If auto-negotiation is not enabled or is not implemented for the active MAU attached to this interface, the value of this object determines the operational PAUSE mode of the interface whenever it is operating in full-duplex mode. In this case, a set to this object will force the interface into the specified mode. If auto-negotiation is implemented and enabled for the MAU attached to this interface, the PAUSE mode for this interface is determined by auto-negotiation, and the value of this object denotes the mode to which the interface will automatically revert if/when auto-negotiation is later disabled. Note that when auto-negotiation is running, administrative control of the PAUSE mode may be accomplished using the ifMauAutoNegCapAdvertisedBits object in the MAU-MIB. Note that the value of this object is ignored when the interface is not operating in full-duplex mode. An attempt to set this object to 'enabledXmit(2)' or 'enabledRcv(3)' will fail on interfaces that do not support operation at greater than 100 Mb/s.
.1.3.6.1.2.1.10.7.10.1.2,EtherLike-MIB::dot3PauseOperMode,INTEGER,read-only,,current,disabled(1):enabledXmit(2):enabledRcv(3):enabledXmitAndRcv(4),This object reflects the PAUSE mode currently in use on this interface, as determined by either (1) the result of the auto-negotiation function or (2) if auto-negotiation is not enabled or is not implemented for the active MAU attached to this interface, by the value of dot3PauseAdminMode. Interfaces operating at 100 Mb/s or less will never return 'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces operating in half-duplex mode will always return 'disabled(1)'. Interfaces on which auto-negotiation is enabled but not yet completed should return the value 'disabled(1)'.
.1.3.6.1.2.1.10.7.10.1.3,EtherLike-MIB::dot3InPauseFrames,Counter32,read-only,,current,,A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation. This counter does not increment when the interface is operating in half-duplex mode. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCInPauseFrames object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.10.1.4,EtherLike-MIB::dot3OutPauseFrames,Counter32,read-only,,current,,A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. This counter does not increment when the interface is operating in half-duplex mode. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCOutPauseFrames object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.10.1.5,EtherLike-MIB::dot3HCInPauseFrames,Counter64,read-only,,current,,A count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation. This counter does not increment when the interface is operating in half-duplex mode. This counter is a 64 bit version of dot3InPauseFrames. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.10.1.6,EtherLike-MIB::dot3HCOutPauseFrames,Counter64,read-only,,current,,A count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. This counter does not increment when the interface is operating in half-duplex mode. This counter is a 64 bit version of dot3OutPauseFrames. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.11,EtherLike-MIB::dot3HCStatsTable,,not-accessible,,current,,A table containing 64-bit versions of error counters from the dot3StatsTable. The 32-bit versions of these counters may roll over quite quickly on higher speed ethernet interfaces. The counters that have 64-bit versions in this table are the counters that apply to full-duplex interfaces, since 10 Gb/s and faster ethernet-like interfaces do not support half-duplex, and very few 1000 Mb/s ethernet-like interfaces support half-duplex. Entries in this table are recommended for interfaces capable of operating at 1000 Mb/s or faster, and are required for interfaces capable of operating at 10 Gb/s or faster. Lower speed ethernet-like interfaces do not need entries in this table, in which case there may be fewer entries in this table than in the dot3StatsTable. However, implementations containing interfaces with a mix of speeds may choose to implement entries in this table for all ethernet-like interfaces.
.1.3.6.1.2.1.10.7.11.1,EtherLike-MIB::dot3HCStatsEntry,,not-accessible,dot3StatsIndex,current,,An entry containing 64-bit statistics for a single ethernet-like interface.
.1.3.6.1.2.1.10.7.11.1.1,EtherLike-MIB::dot3HCStatsAlignmentErrors,Counter64,read-only,,current,,A count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. This counter does not increment for group encoding schemes greater than 4 bits per group. This counter is a 64 bit version of dot3StatsAlignmentErrors. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.11.1.2,EtherLike-MIB::dot3HCStatsFCSErrors,Counter64,read-only,,current,,A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. This count does not include frames received with frame-too-long or frame-too-short error. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. Note: Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the frame to fail the FCS check. This counter is a 64 bit version of dot3StatsFCSErrors. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.11.1.3,EtherLike-MIB::dot3HCStatsInternalMacTransmitErrors,Counter64,read-only,,current,,A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors object. The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted. This counter is a 64 bit version of dot3StatsInternalMacTransmitErrors. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.11.1.4,EtherLike-MIB::dot3HCStatsFrameTooLongs,Counter64,read-only,,current,,A count of frames received on a particular interface that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions pertain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC. This counter is a 64 bit version of dot3StatsFrameTooLongs. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.11.1.5,EtherLike-MIB::dot3HCStatsInternalMacReceiveErrors,Counter64,read-only,,current,,A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors object. The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted. This counter is a 64 bit version of dot3StatsInternalMacReceiveErrors. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.7.11.1.6,EtherLike-MIB::dot3HCStatsSymbolErrors,Counter64,read-only,,current,,For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. This counter is a 64 bit version of dot3StatsSymbolErrors. It should be used on interfaces operating at 10 Gb/s or faster. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.9,RFC1231-MIB::dot5,,,,,,
.1.3.6.1.2.1.10.9.1,RFC1231-MIB::dot5Table,,not-accessible,,mandatory,,This table contains Token Ring interface parameters and state variables, one entry per 802.5 interface.
.1.3.6.1.2.1.10.9.1.1,RFC1231-MIB::dot5Entry,,not-accessible,dot5IfIndex,mandatory,,A list of Token Ring status and parameter values for an 802.5 interface.
.1.3.6.1.2.1.10.9.1.1.1,RFC1231-MIB::dot5IfIndex,INTEGER,read-only,,mandatory,,The value of this object identifies the 802.5 interface for which this entry contains management information. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface.
.1.3.6.1.2.1.10.9.1.1.2,RFC1231-MIB::dot5Commands,INTEGER,read-write,,mandatory,no-op(1):open(2):reset(3):close(4),When this object is set to the value of open(2), the station should go into the open state. The progress and success of the open is given by the values of the objects dot5RingState and dot5RingOpenStatus. When this object is set to the value of reset(3), then the station should do a reset. On a reset, all MIB counters should retain their values, if possible. Other side affects are dependent on the hardware chip set. When this object is set to the value of close(4), the station should go into the stopped state by removing itself from the ring. Setting this object to a value of no-op(1) has no effect. When read, this object always has a value of no-op(1).
.1.3.6.1.2.1.10.9.1.1.3,RFC1231-MIB::dot5RingStatus,INTEGER,read-only,,mandatory,,The current interface status which can be used to diagnose fluctuating problems that can occur on token rings, after a station has successfully been added to the ring. Before an open is completed, this object has the value for the 'no status' condition. The dot5RingState and dot5RingOpenStatus objects provide for debugging problems when the station can not even enter the ring. The object's value is a sum of values, one for each currently applicable condition. The following values are defined for various conditions: 0 = No Problems detected 32 = Ring Recovery 64 = Single Station 256 = Remove Received 512 = reserved 1024 = Auto-Removal Error 2048 = Lobe Wire Fault 4096 = Transmit Beacon 8192 = Soft Error 16384 = Hard Error 32768 = Signal Loss 131072 = no status, open not completed.
.1.3.6.1.2.1.10.9.1.1.4,RFC1231-MIB::dot5RingState,INTEGER,read-only,,mandatory,opened(1):closed(2):opening(3):closing(4):openFailure(5):ringFailure(6),The current interface state with respect to entering or leaving the ring.
.1.3.6.1.2.1.10.9.1.1.5,RFC1231-MIB::dot5RingOpenStatus,INTEGER,read-only,,mandatory,noOpen(1):badParam(2):lobeFailed(3):signalLoss(4):insertionTimeout(5):ringFailed(6):beaconing(7):duplicateMAC(8):requestFailed(9):removeReceived(10):open(11),This object indicates the success, or the reason for failure, of the station's most recent attempt to enter the ring.
.1.3.6.1.2.1.10.9.1.1.6,RFC1231-MIB::dot5RingSpeed,INTEGER,read-write,,mandatory,unknown(1):oneMegabit(2):fourMegabit(3):sixteenMegabit(4),The ring's bandwidth.
.1.3.6.1.2.1.10.9.1.1.7,RFC1231-MIB::dot5UpStream,OCTET,read-only,,mandatory,,The MAC-address of the up stream neighbor station in the ring.
.1.3.6.1.2.1.10.9.1.1.8,RFC1231-MIB::dot5ActMonParticipate,INTEGER,read-write,,mandatory,true(1):false(2),If this object has a value of true(1) then this interface will participate in the active monitor selection process. If the value is false(2) then it will not. Setting this object might not have an effect until the next time the interface is opened.
.1.3.6.1.2.1.10.9.1.1.9,RFC1231-MIB::dot5Functional,OCTET,read-write,,mandatory,,The bit mask of all Token Ring functional addresses for which this interface will accept frames.
.1.3.6.1.2.1.10.9.1.1.10,TOKENRING-MIB::dot5LastBeaconSent,TimeTicks,read-only,,current,,The value of MIB-II's sysUpTime object at which the local system last transmitted a Beacon frame on this interface.
.1.3.6.1.2.1.10.9.2,RFC1231-MIB::dot5StatsTable,,not-accessible,,mandatory,,A table containing Token Ring statistics, one entry per 802.5 interface. All the statistics are defined using the syntax Counter as 32-bit wrap around counters. Thus, if an interface's hardware maintains these statistics in 16-bit counters, then the agent must read the hardware's counters frequently enough to prevent loss of significance, in order to maintain 32-bit counters in software.
.1.3.6.1.2.1.10.9.2.1,RFC1231-MIB::dot5StatsEntry,,not-accessible,dot5StatsIfIndex,mandatory,,An entry contains the 802.5 statistics for a particular interface.
.1.3.6.1.2.1.10.9.2.1.1,RFC1231-MIB::dot5StatsIfIndex,INTEGER,read-only,,mandatory,,The value of this object identifies the 802.5 interface for which this entry contains management information. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface.
.1.3.6.1.2.1.10.9.2.1.2,RFC1231-MIB::dot5StatsLineErrors,Counter32,read-only,,mandatory,,This counter is incremented when a frame or token is copied or repeated by a station, the E bit is zero in the frame or token and one of the following conditions exists: 1) there is a non-data bit (J or K bit) between the SD and the ED of the frame or token, or 2) there is an FCS error in the frame.
.1.3.6.1.2.1.10.9.2.1.3,RFC1231-MIB::dot5StatsBurstErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station detects the absence of transitions for five half-bit timers (burst-five error).
.1.3.6.1.2.1.10.9.2.1.4,RFC1231-MIB::dot5StatsACErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station receives an AMP or SMP frame in which A is equal to C is equal to 0, and then receives another SMP frame with A is equal to C is equal to 0 without first receiving an AMP frame. It denotes a station that cannot set the AC bits properly.
.1.3.6.1.2.1.10.9.2.1.5,RFC1231-MIB::dot5StatsAbortTransErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station transmits an abort delimiter while transmitting.
.1.3.6.1.2.1.10.9.2.1.6,RFC1231-MIB::dot5StatsInternalErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station recognizes an internal error.
.1.3.6.1.2.1.10.9.2.1.7,RFC1231-MIB::dot5StatsLostFrameErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station is transmitting and its TRR timer expires. This condition denotes a condition where a transmitting station in strip mode does not receive the trailer of the frame before the TRR timer goes off.
.1.3.6.1.2.1.10.9.2.1.8,RFC1231-MIB::dot5StatsReceiveCongestions,Counter32,read-only,,mandatory,,This counter is incremented when a station recognizes a frame addressed to its specific address, but has no available buffer space indicating that the station is congested.
.1.3.6.1.2.1.10.9.2.1.9,RFC1231-MIB::dot5StatsFrameCopiedErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station recognizes a frame addressed to its specific address and detects that the FS field A bits are set to 1 indicating a possible line hit or duplicate address.
.1.3.6.1.2.1.10.9.2.1.10,RFC1231-MIB::dot5StatsTokenErrors,Counter32,read-only,,mandatory,,This counter is incremented when a station acting as the active monitor recognizes an error condition that needs a token transmitted.
.1.3.6.1.2.1.10.9.2.1.11,RFC1231-MIB::dot5StatsSoftErrors,Counter32,read-only,,mandatory,,The number of Soft Errors the interface has detected. It directly corresponds to the number of Report Error MAC frames that this interface has transmitted. Soft Errors are those which are recoverable by the MAC layer protocols.
.1.3.6.1.2.1.10.9.2.1.12,RFC1231-MIB::dot5StatsHardErrors,Counter32,read-only,,mandatory,,The number of times this interface has detected an immediately recoverable fatal error. It denotes the number of times this interface is either transmitting or receiving beacon MAC frames.
.1.3.6.1.2.1.10.9.2.1.13,RFC1231-MIB::dot5StatsSignalLoss,Counter32,read-only,,mandatory,,The number of times this interface has detected the loss of signal condition from the ring.
.1.3.6.1.2.1.10.9.2.1.14,RFC1231-MIB::dot5StatsTransmitBeacons,Counter32,read-only,,mandatory,,The number of times this interface has transmitted a beacon frame.
.1.3.6.1.2.1.10.9.2.1.15,RFC1231-MIB::dot5StatsRecoverys,Counter32,read-only,,mandatory,,The number of Claim Token MAC frames received or transmitted after the interface has received a Ring Purge MAC frame. This counter signifies the number of times the ring has been purged and is being recovered back into a normal operating state.
.1.3.6.1.2.1.10.9.2.1.16,RFC1231-MIB::dot5StatsLobeWires,Counter32,read-only,,mandatory,,The number of times the interface has detected an open or short circuit in the lobe data path. The adapter will be closed and dot5RingState will signify this condition.
.1.3.6.1.2.1.10.9.2.1.17,RFC1231-MIB::dot5StatsRemoves,Counter32,read-only,,mandatory,,The number of times the interface has received a Remove Ring Station MAC frame request. When this frame is received the interface will enter the close state and dot5RingState will signify this condition.
.1.3.6.1.2.1.10.9.2.1.18,RFC1231-MIB::dot5StatsSingles,Counter32,read-only,,mandatory,,The number of times the interface has sensed that it is the only station on the ring. This will happen if the interface is the first one up on a ring, or if there is a hardware problem.
.1.3.6.1.2.1.10.9.2.1.19,RFC1231-MIB::dot5StatsFreqErrors,Counter32,read-only,,optional,,The number of times the interface has detected that the frequency of the incoming signal differs from the expected frequency by more than that specified by the IEEE 802.5 standard, see chapter 7 in [10].
.1.3.6.1.2.1.10.9.3,RFC1231-MIB::dot5Tests,,,,,,
.1.3.6.1.2.1.10.9.3.1,RFC1231-MIB::testInsertFunc,,,,,,
.1.3.6.1.2.1.10.9.3.2,TOKENRING-MIB::dot5TestFullDuplexLoopBack,,,,,,Invoking this test on a 802.5 interface causes the interface to check the path from memory through the chip set's internal logic and back to memory, thus checking the proper functioning of the system's interface to the chip set.
.1.3.6.1.2.1.10.9.4,RFC1231-MIB::dot5ChipSets,,,,,,
.1.3.6.1.2.1.10.9.4.1,RFC1231-MIB::chipSetIBM16,,,,,,
.1.3.6.1.2.1.10.9.4.2,RFC1231-MIB::chipSetTItms380,,,,,,
.1.3.6.1.2.1.10.9.4.3,RFC1231-MIB::chipSetTItms380c16,,,,,,
.1.3.6.1.2.1.10.9.5,RFC1231-MIB::dot5TimerTable,,not-accessible,,mandatory,,This table contains Token Ring interface timer values, one entry per 802.5 interface.
.1.3.6.1.2.1.10.9.5.1,RFC1231-MIB::dot5TimerEntry,,not-accessible,dot5TimerIfIndex,mandatory,,A list of Token Ring timer values for an 802.5 interface.
.1.3.6.1.2.1.10.9.5.1.1,RFC1231-MIB::dot5TimerIfIndex,INTEGER,read-only,,mandatory,,The value of this object identifies the 802.5 interface for which this entry contains timer values. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface.
.1.3.6.1.2.1.10.9.5.1.2,RFC1231-MIB::dot5TimerReturnRepeat,INTEGER,read-only,,mandatory,,The time-out value used to ensure the interface will return to Repeat State, in units of 100 micro-seconds. The value should be greater than the maximum ring latency. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.3,RFC1231-MIB::dot5TimerHolding,INTEGER,read-only,,mandatory,,Maximum period of time a station is permitted to transmit frames after capturing a token, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.4,RFC1231-MIB::dot5TimerQueuePDU,INTEGER,read-only,,mandatory,,The time-out value for enqueuing of an SMP PDU after reception of an AMP or SMP frame in which the A and C bits were equal to 0, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.5,RFC1231-MIB::dot5TimerValidTransmit,INTEGER,read-only,,mandatory,,The time-out value used by the active monitor to detect the absence of valid transmissions, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.6,RFC1231-MIB::dot5TimerNoToken,INTEGER,read-only,,mandatory,,The time-out value used to recover from various-related error situations [9]. If N is the maximum number of stations on the ring, the value of this timer is normally: dot5TimerReturnRepeat + N*dot5TimerHolding. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.7,RFC1231-MIB::dot5TimerActiveMon,INTEGER,read-only,,mandatory,,The time-out value used by the active monitor to stimulate the enqueuing of an AMP PDU for transmission, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.8,RFC1231-MIB::dot5TimerStandbyMon,INTEGER,read-only,,mandatory,,The time-out value used by the stand-by monitors to ensure that there is an active monitor on the ring and to detect a continuous stream of tokens, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.9,RFC1231-MIB::dot5TimerErrorReport,INTEGER,read-only,,mandatory,,The time-out value which determines how often a station shall send a Report Error MAC frame to report its error counters, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.10,RFC1231-MIB::dot5TimerBeaconTransmit,INTEGER,read-only,,mandatory,,The time-out value which determines how long a station shall remain in the state of transmitting Beacon frames before entering the Bypass state, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.5.1.11,RFC1231-MIB::dot5TimerBeaconReceive,INTEGER,read-only,,mandatory,,The time-out value which determines how long a station shall receive Beacon frames from its downstream neighbor before entering the Bypass state, in units of 100 micro-seconds. Implementors are encouraged to provide read-write access to this object if that is possible/useful in their system, but giving due consideration to the dangers of write-able timers.
.1.3.6.1.2.1.10.9.6,TOKENRING-MIB::dot5Conformance,,,,,,
.1.3.6.1.2.1.10.9.6.1,TOKENRING-MIB::dot5Groups,,,,,,
.1.3.6.1.2.1.10.9.6.1.1,TOKENRING-MIB::dot5StateGroup,,,,,,A collection of objects providing state information and parameters for IEEE 802.5 interfaces.
.1.3.6.1.2.1.10.9.6.1.2,TOKENRING-MIB::dot5StatsGroup,,,,,,A collection of objects providing statistics for IEEE 802.5 interfaces.
.1.3.6.1.2.1.10.9.6.2,TOKENRING-MIB::dot5Compliances,,,,,,
.1.3.6.1.2.1.10.9.6.2.1,TOKENRING-MIB::dot5Compliance,,,,,,The compliance statement for SNMPv2 entities which implement the IEEE 802.5 MIB.
.1.3.6.1.2.1.10.15,FDDI-SMT73-MIB::fddi,,,,,,
.1.3.6.1.2.1.10.15.1,RFC1285-MIB::snmpFddiSMT,,,,,,
.1.3.6.1.2.1.10.15.1.1,RFC1285-MIB::snmpFddiSMTNumber,INTEGER,read-only,,mandatory,,The number of SMT implementations (regardless of their current state) on this network management application entity. The value for this variable must remain constant at least from one re- initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.1.2,RFC1285-MIB::snmpFddiSMTTable,,not-accessible,,mandatory,,A list of SMT entries. The number of entries is given by the value of snmpFddiSMTNumber.
.1.3.6.1.2.1.10.15.1.2.1,RFC1285-MIB::snmpFddiSMTEntry,,not-accessible,snmpFddiSMTIndex,mandatory,,An SMT entry containing information common to a given SMT.
.1.3.6.1.2.1.10.15.1.2.1.1,RFC1285-MIB::snmpFddiSMTIndex,INTEGER,read-only,,mandatory,,A unique value for each SMT. Its value ranges between 1 and the value of snmpFddiSMTNumber. The value for each SMT must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.1.2.1.2,RFC1285-MIB::snmpFddiSMTStationId,OCTET,read-only,,mandatory,,Uniquely identifies an FDDI station.
.1.3.6.1.2.1.10.15.1.2.1.3,RFC1285-MIB::snmpFddiSMTOpVersionId,INTEGER,read-write,,mandatory,,The version that this station is using for its operation (refer to ANSI 7.1.2.2).
.1.3.6.1.2.1.10.15.1.2.1.4,RFC1285-MIB::snmpFddiSMTHiVersionId,INTEGER,read-only,,mandatory,,The highest version of SMT that this station supports (refer to ANSI 7.1.2.2).
.1.3.6.1.2.1.10.15.1.2.1.5,RFC1285-MIB::snmpFddiSMTLoVersionId,INTEGER,read-only,,mandatory,,The lowest version of SMT that this station supports (refer to ANSI 7.1.2.2).
.1.3.6.1.2.1.10.15.1.2.1.6,RFC1285-MIB::snmpFddiSMTMACCt,INTEGER,read-only,,mandatory,,The number of MACs in the station or concentrator.
.1.3.6.1.2.1.10.15.1.2.1.7,RFC1285-MIB::snmpFddiSMTNonMasterCt,INTEGER,read-only,,mandatory,,The number of Non Master PORTs (A, B, or S PORTs) in the station or concentrator.
.1.3.6.1.2.1.10.15.1.2.1.8,RFC1285-MIB::snmpFddiSMTMasterCt,INTEGER,read-only,,mandatory,,The number of Master PORTs in a node. If the node is not a concentrator, the value is zero.
.1.3.6.1.2.1.10.15.1.2.1.9,RFC1285-MIB::snmpFddiSMTPathsAvailable,INTEGER,read-only,,mandatory,,A value that indicates the PATH types available in the station. The value is a sum. This value initially takes the value zero, then for each type of PATH that this node has available, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 For example, a station having Primary and Local PATHs available would have a value of 5 (2**0 + 2**2).
.1.3.6.1.2.1.10.15.1.2.1.10,RFC1285-MIB::snmpFddiSMTConfigCapabilities,INTEGER,read-only,,mandatory,,A value that indicates capabilities that are present in the node. If 'holdAvailable' is present, this indicates support of the optional Hold Function (refer to ANSI SMT 9.4.3.2). If 'CF-Wrap-AB' is present, this indicates that the WRAP_AB state is forced. The value is a sum. This value initially takes the value zero, then for each of the configuration policies currently enforced on the node, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power holdAvailable 0 CF-Wrap-AB 1 
.1.3.6.1.2.1.10.15.1.2.1.11,RFC1285-MIB::snmpFddiSMTConfigPolicy,INTEGER,read-write,,mandatory,,A value that indicates the configuration policies currently enforced in the node (refer to ANSI SMT 9.4.3.2). The 'configurationHold' policy refers to the Hold flag, and should not be present only if the Hold function is supported. The 'CF-Wrap- AB' policy refers to the CF_Wrap_AB flag. The value is a sum. This value initially takes the value zero, then for each of the configuration policies currently enforced on the node, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power configurationHold 0 CF-Wrap-AB 1 
.1.3.6.1.2.1.10.15.1.2.1.12,RFC1285-MIB::snmpFddiSMTConnectionPolicy,INTEGER,read-write,,mandatory,,A value that indicates the connection policies enforced at the station. A station sets the corresponding policy for each of the connection types that it rejects. The letter designations, X and Y, in the 'rejectX-Y' names have the following significance: X represents the PC-Type of the local PORT and Y represents a PC-Neighbor in the evaluation of Connection-Policy (PC-Type, PC- Neighbor) that is done to determine the setting of T-Val(3) in the PC-Signaling sequence (refer to ANSI Section 9.6.3). The value is a sum. This value initially takes the value zero, then for each of the connection policies currently enforced on the node, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power rejectA-A 0 rejectA-B 1 rejectA-S 2 rejectA-M 3 rejectB-A 4 rejectB-B 5 rejectB-S 6 rejectB-M 7 rejectS-A 8 rejectS-B 9 rejectS-S 10 rejectS-M 11 rejectM-A 12 rejectM-B 13 rejectM-S 14 rejectM-M 15 Implementors should note that the polarity of these bits is different in different places in an SMT system. Implementors should take appropriate care.
.1.3.6.1.2.1.10.15.1.2.1.13,RFC1285-MIB::snmpFddiSMTTNotify,INTEGER,read-write,,mandatory,,The timer used in the Neighbor Notification protocol, reported in seconds and ranging from 2 to 30 seconds (refer to ANSI SMT 8.3.1).
.1.3.6.1.2.1.10.15.1.2.1.14,RFC1285-MIB::snmpFddiSMTStatusReporting,INTEGER,read-only,,mandatory,true(1):false(2),Indicates whether the node implements the Status Reporting Protocol. This object is included for compatibility with products that were designed prior to the adoption of this standard.
.1.3.6.1.2.1.10.15.1.2.1.15,RFC1285-MIB::snmpFddiSMTECMState,INTEGER,read-only,,mandatory,ec0(1):ec1(2):ec2(3):ec3(4):ec4(5):ec5(6):ec6(7):ec7(8),Indicates the current state of the ECM state machine (refer to ANSI SMT 9.5.2).
.1.3.6.1.2.1.10.15.1.2.1.16,RFC1285-MIB::snmpFddiSMTCFState,INTEGER,read-only,,mandatory,cf0(1):cf1(2):cf2(3):cf3(4):cf4(5):cf5(6),The attachment configuration for the station or concentrator (refer to ANSI SMT 9.7.4.3).
.1.3.6.1.2.1.10.15.1.2.1.17,RFC1285-MIB::snmpFddiSMTHoldState,INTEGER,read-only,,mandatory,not-holding(2):holding-prm(3):holding-sec(4),This value indicates the current state of the Hold function. The values are determined as follows: 'holding-prm' is set if the primary ring is operational and the Recovery Enable Flag is clear (NOT NO_Flag(primary) AND NOT RE_Flag). is set if the secondary ring is operational and the Recovery Enable Flag is clear (NOT NO_Flag(secondary) AND NOT RE_Flag). Ref 9.4.3. and 10.3.1. the primary or secondary, i.e., the Recovery Enable, RE_Flag, is set.
.1.3.6.1.2.1.10.15.1.2.1.18,RFC1285-MIB::snmpFddiSMTRemoteDisconnectFlag,INTEGER,read-only,,mandatory,true(1):false(2),A flag indicating that the station was remotely disconnected from the network. A station requires a Connect Action (SM_CM_CONNECT.request (Connect)) to rejoin and clear the flag (refer to ANSI 6.4.5.2).
.1.3.6.1.2.1.10.15.1.2.1.19,RFC1285-MIB::snmpFddiSMTStationAction,INTEGER,read-write,,mandatory,other(1):connect(2):disconnect(3):path-Test(4):self-Test(5),This object, when read, always returns a value of other(1). The behavior of setting this variable to each of the acceptable values is as follows: Other: Results in a badValue error. Connect: Generates an SM_CM_Connect.request(connect) signal to CMT indicating that the ECM State machine is to begin a connection sequence. The fddiSMTRemoteDisconnectFlag is cleared on the setting of this variable to 1. See ANSI Ref 9.3.1.1. Disconnect: Generates an SM_CM_Connect.request(disconnect) signal to ECM and sets the fddiSMTRemoteDisconnectFlag. See ANSI Ref 9.3.1.1. Path-Test: Initiates a station path test. The Path_Test variable (See ANSI Ref. 9.4.1) is set to Testing. The results of this action are not specified in this standard. Self-Test: Initiates a station self test. The results of this action are not specified in this standard. Attempts to set this object to all other values results in a badValue error. Agents may elect to return a badValue error on attempts to set this variable to path-Test(4) or self-Test(5).
.1.3.6.1.2.1.10.15.2,RFC1285-MIB::snmpFddiMAC,,,,,,
.1.3.6.1.2.1.10.15.2.1,RFC1285-MIB::snmpFddiMACNumber,INTEGER,read-only,,mandatory,,The total number of MAC implementations (across all SMTs) on this network management application entity. The value for this variable must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.2.2,RFC1285-MIB::snmpFddiMACTable,,not-accessible,,mandatory,,A list of MAC entries. The number of entries is given by the value of snmpFddiMACNumber.
.1.3.6.1.2.1.10.15.2.2.1,RFC1285-MIB::snmpFddiMACEntry,,not-accessible,snmpFddiMACSMTIndex:snmpFddiMACIndex,mandatory,,A MAC entry containing information common to a given MAC.
.1.3.6.1.2.1.10.15.2.2.1.1,RFC1285-MIB::snmpFddiMACSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this MAC.
.1.3.6.1.2.1.10.15.2.2.1.2,RFC1285-MIB::snmpFddiMACIndex,INTEGER,read-only,,mandatory,,A unique value for each MAC on the managed entity. The MAC identified by a particular value of this index is that identified by the same value of an ifIndex object instance. That is, if a MAC is associated with the interface whose value of ifIndex in the Internet-Standard MIB is equal to 5, then the value of snmpFddiMACIndex shall also equal 5. The value for each MAC must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.2.2.1.3,RFC1285-MIB::snmpFddiMACFrameStatusCapabilities,INTEGER,read-only,,mandatory,,A value that indicates the MAC's bridge and end- station capabilities for operating in a bridged FDDI network. The value is a sum. This value initially takes the value zero, then for each capability present, 2 raised to a power is added to the sum. The powers are according to the following table: Capability Power FSC-Type0 0 -- MAC repeats A/C indicators as received on -- copying with the intent to forward. FSC-Type1 1 -- MAC sets C but not A on copying for -- forwarding. FSC-Type2 2 -- MAC resets C and sets A on C set and -- A reset if the frame is not copied and the -- frame was addressed to this MAC FSC-Type0-programmable 8 -- Type0 capability is programmable FSC-Type1-programmable 9 -- Type1 capability is programmable FSC-Type2-programmable 10 -- Type2 capability is programmable 
.1.3.6.1.2.1.10.15.2.2.1.4,RFC1285-MIB::snmpFddiMACTMaxGreatestLowerBound,INTEGER,read-write,,mandatory,,The greatest lower bound of T_Max supported for this MAC.
.1.3.6.1.2.1.10.15.2.2.1.5,RFC1285-MIB::snmpFddiMACTVXGreatestLowerBound,INTEGER,read-only,,mandatory,,The greatest lower bound of TVX supported for this MAC.
.1.3.6.1.2.1.10.15.2.2.1.6,RFC1285-MIB::snmpFddiMACPathsAvailable,INTEGER,read-only,,mandatory,,A value that indicates the PATH types available for this MAC. The value is a sum. This value initially takes the value zero, then for each type of PATH that this MAC has available, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 
.1.3.6.1.2.1.10.15.2.2.1.7,RFC1285-MIB::snmpFddiMACCurrentPath,INTEGER,read-only,,mandatory,unknown(1):primary(2):secondary(4):local(8):isolated(16),Indicates the association of the MAC with a station PATH.
.1.3.6.1.2.1.10.15.2.2.1.8,RFC1285-MIB::snmpFddiMACUpstreamNbr,OCTET,read-only,,mandatory,,The MAC's upstream neighbor's long individual MAC address. It may be determined by the Neighbor Information Frame protocol (refer to ANSI SMT 7.2.1). The value shall be reported as '00 00 00 00 00 00' if it is unknown.
.1.3.6.1.2.1.10.15.2.2.1.9,RFC1285-MIB::snmpFddiMACOldUpstreamNbr,OCTET,read-only,,mandatory,,The previous value of the MAC's upstream neighbor's long individual MAC address. It may be determined by the Neighbor Information Frame protocol (refer to ANSI SMT 7.2.1). The value shall be reported as '00 00 00 00 00 00' if it is unknown.
.1.3.6.1.2.1.10.15.2.2.1.10,RFC1285-MIB::snmpFddiMACDupAddrTest,INTEGER,read-only,,mandatory,none(1):pass(2):fail(3),The Duplicate Address Test flag, Dup_Addr_Test (refer to ANSI 8.3.1).
.1.3.6.1.2.1.10.15.2.2.1.11,RFC1285-MIB::snmpFddiMACPathsRequested,INTEGER,read-write,,mandatory,,A value that indicates PATH(s) desired for this MAC. The value is a sum which represents the individual PATHs that are desired. This value initially takes the value zero, then for each type of PATH that this node is, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 Isolated 3 The precedence order is primary, secondary, local, and then isolated if multiple PATHs are desired are set.
.1.3.6.1.2.1.10.15.2.2.1.12,RFC1285-MIB::snmpFddiMACDownstreamPORTType,INTEGER,read-only,,mandatory,a(1):b(2):s(3):m(4):unknown(5),Indicates the PC-Type of the first port that is downstream of this MAC (the exit port).
.1.3.6.1.2.1.10.15.2.2.1.13,RFC1285-MIB::snmpFddiMACSMTAddress,OCTET,read-only,,mandatory,,The 48 bit individual address of the MAC used for SMT frames.
.1.3.6.1.2.1.10.15.2.2.1.14,RFC1285-MIB::snmpFddiMACTReq,INTEGER,read-write,,mandatory,,The value of T-Req (refer to ANSI MAC 2.2.1 and ANSI MAC 7.3.5.2).
.1.3.6.1.2.1.10.15.2.2.1.15,RFC1285-MIB::snmpFddiMACTNeg,INTEGER,read-only,,mandatory,,The value of T-Neg (refer to ANSI MAC 2.2.1 and ANSI MAC 7.3.5.2).
.1.3.6.1.2.1.10.15.2.2.1.16,RFC1285-MIB::snmpFddiMACTMax,INTEGER,read-only,,mandatory,,The value of T-Max (refer to ANSI MAC 2.2.1 and ANSI MAC 7.3.5.2).
.1.3.6.1.2.1.10.15.2.2.1.17,RFC1285-MIB::snmpFddiMACTvxValue,INTEGER,read-only,,mandatory,,The value of TvxValue (refer to ANSI MAC 2.2.1 and ANSI MAC 7.3.5.2).
.1.3.6.1.2.1.10.15.2.2.1.18,RFC1285-MIB::snmpFddiMACTMin,INTEGER,read-only,,mandatory,,The value of T-Min (refer to ANSI MAC 2.2.1 and ANSI MAC 7.3.5.2).
.1.3.6.1.2.1.10.15.2.2.1.19,RFC1285-MIB::snmpFddiMACCurrentFrameStatus,INTEGER,read-write,,mandatory,,A value that indicates the MAC's operational frame status setting functionality. The value is a sum. This value initially takes the value zero, then for each functionality present, 2 raised to a power is added to the sum. The powers are according to the following table: Functionality Power FSC-Type0 0 -- MAC repeats A/C indicators as received FSC-Type1 1 -- MAC sets C but not A on copying for -- forwarding FSC-Type2 2 -- MAC resets C and sets A on C set and A -- reset if frame is not copied 
.1.3.6.1.2.1.10.15.2.2.1.20,RFC1285-MIB::snmpFddiMACFrameCts,Counter32,read-only,,mandatory,,Frame_Ct (refer to ANSI MAC 2.2.1).
.1.3.6.1.2.1.10.15.2.2.1.21,RFC1285-MIB::snmpFddiMACErrorCts,Counter32,read-only,,mandatory,,Error_Ct (refer to ANSI MAC 2.2.1).
.1.3.6.1.2.1.10.15.2.2.1.22,RFC1285-MIB::snmpFddiMACLostCts,Counter32,read-only,,mandatory,,Lost_Ct (refer to ANSI MAC 2.2.1).
.1.3.6.1.2.1.10.15.2.2.1.23,RFC1285-MIB::snmpFddiMACFrameErrorThreshold,INTEGER,read-only,,mandatory,,A threshold for determining when a MAC Condition report should be generated. The condition is true when the ratio, ((delta snmpFddiMACLostCt + delta snmpFddiMACErrorCt) / (delta snmpFddiMACFrameCt + delta snmpFddiMACLostCt)) x 2**16. exceeds the threshold. It is used to determine when a station has an unacceptable frame error threshold. The sampling algorithm is implementation dependent. Any attempt to set this variable to a value of less than one shall result in a badValue error. Those who are familiar with the SNMP management framework will recognize that thresholds are not in keeping with the SNMP philosophy. However, this variable is supported by underlying SMT implementations already and maintaining this threshold should not pose an undue additional burden on SNMP agent implementors.
.1.3.6.1.2.1.10.15.2.2.1.24,RFC1285-MIB::snmpFddiMACFrameErrorRatio,INTEGER,read-only,,mandatory,,This attribute is the actual ratio, ((delta snmpFddiMACLostCt + delta snmpFddiMACErrorCt) / (delta snmpFddiMACFrameCt + delta snmpFddiMACLostCt)) x 2**16.
.1.3.6.1.2.1.10.15.2.2.1.25,RFC1285-MIB::snmpFddiMACRMTState,INTEGER,read-only,,mandatory,rm0(1):rm1(2):rm2(3):rm3(4):rm4(5):rm5(6):rm6(7):rm7(8),Indicates the current state of the Ring Management state machine (refer to ANSI Section 10).
.1.3.6.1.2.1.10.15.2.2.1.26,RFC1285-MIB::snmpFddiMACDaFlag,INTEGER,read-only,,mandatory,true(1):false(2),The RMT flag Duplicate Address Flag, DA_Flag (refer to ANSI 10.3.1.2).
.1.3.6.1.2.1.10.15.2.2.1.27,RFC1285-MIB::snmpFddiMACUnaDaFlag,INTEGER,read-only,,mandatory,true(1):false(2),A flag set when the upstream neighbor reports a duplicate address condition. Reset when the condition clears.
.1.3.6.1.2.1.10.15.2.2.1.28,RFC1285-MIB::snmpFddiMACFrameCondition,INTEGER,read-only,,mandatory,true(1):false(2),Indicates the MAC Condition is active when set. Cleared when the condition clears and on power up.
.1.3.6.1.2.1.10.15.2.2.1.29,RFC1285-MIB::snmpFddiMACChipSet,OBJECT,read-only,,mandatory,,This object identifies the hardware chip(s) which is (are) principally responsible for the implementation of the MAC function. A few OBJECT IDENTIFIERS are identified elsewhere in this memo. For those The assignment of additional OBJECT IDENTIFIERs to various types of hardware chip sets is managed by the IANA. For example, vendors whose chip sets are not defined in this memo may request a number from the Internet Assigned Numbers Authority (IANA) which indicates the assignment of a enterprise specific subtree which, among other things, may be used to allocate OBJECT IDENTIFIER assignments for that enterprise's chip sets. Similarly, in the absence of an appropriately assigned OBJECT IDENTIFIER in this memo or in an enterprise specific subtree of a chip vendor, a board or system vendor can request a number for a subtree from the IANA and make an appropriate assignment. It is desired that, whenever possible, the same OBJECT IDENTIFIER be used for all chips of a given type. Consequently, the assignment made in this memo for a chip, if any, should be used in preference to any other assignment and the assignment made by the chip manufacturer, if any, should be used in preference to assignments made by users of those chips. If the hardware chip set is unknown, the object identifier unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownChipSet is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value.
.1.3.6.1.2.1.10.15.2.2.1.30,RFC1285-MIB::snmpFddiMACAction,INTEGER,read-write,,mandatory,other(1):enableLLCService(2):disableLLCService(3):connectMAC(4):disconnectMAC(5),This object, when read, always returns a value of other(1). The behavior of setting this variable to each of the acceptable values is as follows: Other: Results in a badValue error. enableLLCService: enables MAC service to higher layers. disableLLCService: disables MAC service to higher layers. connectMAC: connect this MAC in station. disconnectMAC: disconnect this MAC in station. Attempts to set this object to all other values results in a badValue error.
.1.3.6.1.2.1.10.15.3,RFC1285-MIB::snmpFddiPATH,,,,,,
.1.3.6.1.2.1.10.15.4,RFC1285-MIB::snmpFddiPORT,,,,,,
.1.3.6.1.2.1.10.15.4.1,RFC1285-MIB::snmpFddiPORTNumber,INTEGER,read-only,,mandatory,,The total number of PORT implementations (across all SMTs) on this network management application entity. The value for this variable must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.4.2,RFC1285-MIB::snmpFddiPORTTable,,not-accessible,,mandatory,,A list of PORT entries. The number of entries is given by the value of snmpFddiPORTNumber.
.1.3.6.1.2.1.10.15.4.2.1,RFC1285-MIB::snmpFddiPORTEntry,,not-accessible,snmpFddiPORTSMTIndex:snmpFddiPORTIndex,mandatory,,A PORT entry containing information common to a given PORT.
.1.3.6.1.2.1.10.15.4.2.1.1,RFC1285-MIB::snmpFddiPORTSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this PORT.
.1.3.6.1.2.1.10.15.4.2.1.2,RFC1285-MIB::snmpFddiPORTIndex,INTEGER,read-only,,mandatory,,A unique value for each PORT within a given SMT. Its value ranges between 1 and the sum of the values of snmpFddiSMTNonMasterCt { snmpFddiSMTEntry 6 } and snmpFddiSMTMasterCt { snmpFddiSMTEntry 7 } on the given SMT. The value for each PORT must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.4.2.1.3,RFC1285-MIB::snmpFddiPORTPCType,INTEGER,read-only,,mandatory,a(1):b(2):s(3):m(4),PC_Type (refer to ANSI SMT 9.2.2 and ANSI SMT 9.6.3.2).
.1.3.6.1.2.1.10.15.4.2.1.4,RFC1285-MIB::snmpFddiPORTPCNeighbor,INTEGER,read-only,,mandatory,a(1):b(2):s(3):m(4):unknown(5),The type (PC_Neighbor) of the remote PORT that is determined in PC_Signaling in R_Val (1,2) (refer to ANSI SMT 9.6.3.2).
.1.3.6.1.2.1.10.15.4.2.1.5,RFC1285-MIB::snmpFddiPORTConnectionPolicies,INTEGER,read-write,,mandatory,,A value that indicates the node's PORT policies. Pc-MAC-LCT, Pc-MAC-Loop, and Pc-MAC-Placement indicate how the respective PC Signaling Capability flags should be set (refer to ANSI SMT 9.4.3.2). The value is a sum. This value initially takes the value zero, then for each PORT policy, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power Pc-MAC-LCT 0 Pc-MAC-Loop 1 Pc-MAC-Placement 2 
.1.3.6.1.2.1.10.15.4.2.1.6,RFC1285-MIB::snmpFddiPORTRemoteMACIndicated,INTEGER,read-only,,mandatory,true(1):false(2),The indication, in PC-Signaling that the remote partner intends to place a MAC in the output token PATH of this PORT. Signaled as R_Val (9) (refer to ANSI SMT 9.6.3.2).
.1.3.6.1.2.1.10.15.4.2.1.7,RFC1285-MIB::snmpFddiPORTCEState,INTEGER,read-only,,mandatory,ce0(1):ce1(2):ce2(3):ce3(4):ce4(5),Indicates the current state of PORT's Configuration Element (CE) (refer to ANSI 9.7.5). Note that this value represents the Current Path information for this PORT.
.1.3.6.1.2.1.10.15.4.2.1.8,RFC1285-MIB::snmpFddiPORTPathsRequested,INTEGER,read-write,,mandatory,,A value that indicates the desired association(s) of the port with a station PATH. The 'Primary' Path is the default. The value of 'Secondary' is only meaningful for S (slave) or M (master) PORT PC-Types. This value effects the setting of the CF_Insert_S, and CF_Insert_L flags (refer to ANSI Section 9.4.3). If the 'Primary' PATH is present, then the Primary PATH (the default PATH) is selected. If the 'Secondary' PATH is present and the 'Primary' PATH is not present, then the CF_Insert_S flag is set. If the 'Local' PATH is sent and neither the 'Primary' or 'Secondary' PATHs are sent, then the CF_Insert_L flag is set. The value is a sum. This value initially takes the value zero, then for each type of PATH desired, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 Isolated 3 
.1.3.6.1.2.1.10.15.4.2.1.9,RFC1285-MIB::snmpFddiPORTMACPlacement,INTEGER,read-only,,mandatory,,Indicates the upstream MAC, if any, that is associated with the PORT. The value shall be zero if there is no MAC associated with the PORT. Otherwise, the value shall be equal to the value of snmpFddiMACIndex associated with the MAC.
.1.3.6.1.2.1.10.15.4.2.1.10,RFC1285-MIB::snmpFddiPORTAvailablePaths,INTEGER,read-only,,mandatory,,A value that indicates the PATH types available for M and S PORTs. The value is a sum. This value initially takes the value zero, then for each type of PATH that this port has available, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 
.1.3.6.1.2.1.10.15.4.2.1.11,RFC1285-MIB::snmpFddiPORTMACLoopTime,INTEGER,read-write,,mandatory,,Time for the optional MAC Local Loop, T_Next(9), which is greater-than or equal-to 200 milliseconds (refer to ANSI SMT 9.4.4.2.3).
.1.3.6.1.2.1.10.15.4.2.1.12,RFC1285-MIB::snmpFddiPORTTBMax,INTEGER,read-write,,mandatory,,TB_Max (refer to ANSI SMT 9.4.4.2.1).
.1.3.6.1.2.1.10.15.4.2.1.13,RFC1285-MIB::snmpFddiPORTBSFlag,INTEGER,read-only,,mandatory,true(1):false(2),The Break State, BS_Flag (refer to ANSI SMT 9.4.3.4).
.1.3.6.1.2.1.10.15.4.2.1.14,RFC1285-MIB::snmpFddiPORTLCTFailCts,Counter32,read-only,,mandatory,,The count of the consecutive times the link confidence test (LCT) has failed during connection management (refer to ANSI 9.4.1).
.1.3.6.1.2.1.10.15.4.2.1.15,RFC1285-MIB::snmpFddiPORTLerEstimate,INTEGER,read-only,,mandatory,,A long term average link error rate. It ranges from 10**-4 to 10**-15 and is reported as the absolute value of the exponent of the estimate.
.1.3.6.1.2.1.10.15.4.2.1.16,RFC1285-MIB::snmpFddiPORTLemRejectCts,Counter32,read-only,,mandatory,,A link error monitoring count of the times that a link has been rejected.
.1.3.6.1.2.1.10.15.4.2.1.17,RFC1285-MIB::snmpFddiPORTLemCts,Counter32,read-only,,mandatory,,The aggregate link error monitor error count, set to zero only on station power_up.
.1.3.6.1.2.1.10.15.4.2.1.18,RFC1285-MIB::snmpFddiPORTLerCutoff,INTEGER,read-write,,mandatory,,The link error rate estimate at which a link connection will be broken. It ranges from 10**-4 to 10**-15 and is reported as the absolute value of the exponent.
.1.3.6.1.2.1.10.15.4.2.1.19,RFC1285-MIB::snmpFddiPORTLerAlarm,INTEGER,read-write,,mandatory,,The link error rate estimate at which a link connection will generate an alarm. It ranges from 10**-4 to 10**-15 and is reported as the absolute value of the exponent of the estimate.
.1.3.6.1.2.1.10.15.4.2.1.20,RFC1285-MIB::snmpFddiPORTConnectState,INTEGER,read-only,,mandatory,disabled(1):connecting(2):standby(3):active(4),An indication of the connect state of this PORT. Basically, this gives a higher level view of the state of the connection by grouping PCM states and the PC-Withhold flag state. The supported values and their corresponding PCM states and PC-Withhold condition, when relevant, are: disabled: (PC0:Off, PC9:Maint) connecting: (PC1(Break) || PC3 (Connect) || PC4 (Next) || PC5 (Signal) || PC6 (Join) || PC7 (Verify)) && (PC_Withhold = None) standby: (NOT PC_Withhold == None) active: (PC2:Trace || PC8:Active) 
.1.3.6.1.2.1.10.15.4.2.1.21,RFC1285-MIB::snmpFddiPORTPCMState,INTEGER,read-only,,mandatory,pc0(1):pc1(2):pc2(3):pc3(4):pc4(5):pc5(6):pc6(7):pc7(8):pc8(9):pc9(10),(refer to SMT 9.6.2).
.1.3.6.1.2.1.10.15.4.2.1.22,RFC1285-MIB::snmpFddiPORTPCWithhold,INTEGER,read-only,,mandatory,none(1):m-m(2):other(3),PC_Withhold, (refer to ANSI SMT 9.4.1).
.1.3.6.1.2.1.10.15.4.2.1.23,RFC1285-MIB::snmpFddiPORTLerCondition,INTEGER,read-only,,mandatory,true(1):false(2),This variable is set to true whenever LerEstimate is less than or equal to LerAlarm.
.1.3.6.1.2.1.10.15.4.2.1.24,RFC1285-MIB::snmpFddiPORTChipSet,OBJECT,read-only,,mandatory,,This object identifies the hardware chip(s) which is (are) principally responsible for the implementation of the PORT (PHY) function. A few OBJECT IDENTIFIERS are identified elsewhere in this memo. For those The assignment of additional OBJECT IDENTIFIERs to various types of hardware chip sets is managed by the IANA. For example, vendors whose chip sets are not defined in this memo may request a number from the Internet Assigned Numbers Authority (IANA) which indicates the assignment of a enterprise specific subtree which, among other things, may be used to allocate OBJECT IDENTIFIER assignments for that enterprise's chip sets. Similarly, in the absence of an appropriately assigned OBJECT IDENTIFIER in this memo or in an enterprise specific subtree of a chip vendor, a board or system vendor can request a number for a subtree from the IANA and make an appropriate assignment. It is desired that, whenever possible, the same OBJECT IDENTIFIER be used for all chips of a given type. Consequently, the assignment made in this memo for a chip, if any, should be used in preference to any other assignment and the assignment made by the chip manufacturer, if any, should be used in preference to assignments made by users of those chips. If the hardware chip set is unknown, the object identifier unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownChipSet is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value.
.1.3.6.1.2.1.10.15.4.2.1.25,RFC1285-MIB::snmpFddiPORTAction,INTEGER,read-write,,mandatory,other(1):maintPORT(2):enablePORT(3):disablePORT(4):startPORT(5):stopPORT(6),This object, when read, always returns a value of other(1). The behavior of setting this variable to each of the acceptable values is as follows: Other: Results in a badValue error. maintPORT: Signal PC_Maint enablePORT: Signal PC_Enable disablePORT: Signal PC_Disable startPORT: Signal PC_Start stopPORT: Signal PC_Stop Signals cause an SM_CM_CONTROL.request service to be generated with a control_action of `Signal' and the `variable' parameter set with the appropriate value (i.e., PC_Maint, PC_Enable, PC_Disable, PC_Start, PC_Stop). Ref. ANSI SMT Section 9.3.2. Attempts to set this object to all other values results in a badValue error.
.1.3.6.1.2.1.10.15.5,RFC1285-MIB::snmpFddiATTACHMENT,,,,,,
.1.3.6.1.2.1.10.15.5.1,RFC1285-MIB::snmpFddiATTACHMENTNumber,INTEGER,read-only,,mandatory,,The total number of attachments (across all SMTs) on this network management application entity. The value for this variable must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.5.2,RFC1285-MIB::snmpFddiATTACHMENTTable,,not-accessible,,mandatory,,A list of ATTACHMENT entries. The number of entries is given by the value of snmpFddiATTACHMENTNumber.
.1.3.6.1.2.1.10.15.5.2.1,RFC1285-MIB::snmpFddiATTACHMENTEntry,,not-accessible,snmpFddiATTACHMENTSMTIndex:snmpFddiATTACHMENTIndex,mandatory,,An ATTACHMENT entry containing information common to a given set of ATTACHMENTs. The ATTACHMENT Resource represents a PORT or a pair of PORTs plus the optional associated optical bypass that are managed as a functional unit. Because of its relationship to the PORT Objects, there is a natural association of ATTACHMENT Resource Indices to the PORT Indices. The resource index for the ATTACHMENT is equal to the associated PORT index for 'single-attachment' and 'concentrator' type snmpFddiATTACHMENTClasses. For 'dual-attachment' Classes, the ATTACHMENT Index is the PORT Index of the A PORT of the A/B PORT Pair that represents the ATTACHMENT.
.1.3.6.1.2.1.10.15.5.2.1.1,RFC1285-MIB::snmpFddiATTACHMENTSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this ATTACHMENT.
.1.3.6.1.2.1.10.15.5.2.1.2,RFC1285-MIB::snmpFddiATTACHMENTIndex,INTEGER,read-only,,mandatory,,A unique value for each ATTACHMENT on a given SMT. Its value ranges between 1 and the sum of the values of snmpFddiSMTNonMasterCt { snmpFddiSMTEntry 6 } and snmpFddiSMTMasterCt { snmpFddiSMTEntry 7 } on the given SMT. The value for each ATTACHMENT must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.5.2.1.3,RFC1285-MIB::snmpFddiATTACHMENTClass,INTEGER,read-only,,mandatory,single-attachment(1):dual-attachment(2):concentrator(3),The Attachment class. This represents a PORT or a pair of PORTs plus the associated optional optical bypass that are managed as a functional unit. The PORT associations are the following: single-attachment - S PORTs dual-attachment - A/B PORT Pairs concentrator - M PORTs 
.1.3.6.1.2.1.10.15.5.2.1.4,RFC1285-MIB::snmpFddiATTACHMENTOpticalBypassPresent,INTEGER,read-only,,mandatory,true(1):false(2),The value of this value is false for 'single- attachment' and { snmpFddiATTACHMENT 11 }. Correct operation of CMT for single-attachment and concentrator attachments requires that a bypass function must not loopback the network side of the MIC, but only the node side.
.1.3.6.1.2.1.10.15.5.2.1.5,RFC1285-MIB::snmpFddiATTACHMENTIMaxExpiration,INTEGER,read-only,,mandatory,,I_Max (refer to ANSI SMT 9.4.4.2.1). It is recognized that some currently deployed systems do not implement an optical bypass. Systems which do not implement optical bypass should return a value of 0.
.1.3.6.1.2.1.10.15.5.2.1.6,RFC1285-MIB::snmpFddiATTACHMENTInsertedStatus,INTEGER,read-only,,mandatory,true(1):false(2):unimplemented(3),Indicates whether the attachment is currently inserted in the node.
.1.3.6.1.2.1.10.15.5.2.1.7,RFC1285-MIB::snmpFddiATTACHMENTInsertPolicy,INTEGER,read-write,,mandatory,true(1):false(2):unimplemented(3),Indicates the Insert Policy for this Attachment. Insert: True (1), Don't Insert: False (2), Unimplemented (3)
.1.3.6.1.2.1.10.15.6,RFC1285-MIB::snmpFddiChipSets,,,,,,
.1.3.6.1.2.1.10.15.6.1,RFC1285-MIB::snmpFddiPHYChipSets,,,,,,
.1.3.6.1.2.1.10.15.6.2,RFC1285-MIB::snmpFddiMACChipSets,,,,,,
.1.3.6.1.2.1.10.15.6.3,RFC1285-MIB::snmpFddiPHYMACChipSets,,,,,,
.1.3.6.1.2.1.10.15.73,FDDI-SMT73-MIB::fddimib,,,,,,
.1.3.6.1.2.1.10.15.73.1,FDDI-SMT73-MIB::fddimibSMT,,,,,,
.1.3.6.1.2.1.10.15.73.1.1,FDDI-SMT73-MIB::fddimibSMTNumber,INTEGER,read-only,,mandatory,,The number of SMT implementations (regardless of their current state) on this network management application entity. The value for this variable must remain constant at least from one re- initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.73.1.2,FDDI-SMT73-MIB::fddimibSMTTable,,not-accessible,,mandatory,,A list of SMT entries. The number of entries shall not exceed the value of fddimibSMTNumber.
.1.3.6.1.2.1.10.15.73.1.2.1,FDDI-SMT73-MIB::fddimibSMTEntry,,not-accessible,fddimibSMTIndex,mandatory,,An SMT entry containing information common to a given SMT.
.1.3.6.1.2.1.10.15.73.1.2.1.1,FDDI-SMT73-MIB::fddimibSMTIndex,INTEGER,read-only,,mandatory,,A unique value for each SMT. The value for each SMT must remain constant at least from one re- initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.73.1.2.1.2,FDDI-SMT73-MIB::fddimibSMTStationId,OCTET,read-only,,mandatory,,Used to uniquely identify an FDDI station.
.1.3.6.1.2.1.10.15.73.1.2.1.3,FDDI-SMT73-MIB::fddimibSMTOpVersionId,INTEGER,read-only,,mandatory,,The version that this station is using for its operation (refer to ANSI 7.1.2.2). The value of this variable is 2 for this SMT revision.
.1.3.6.1.2.1.10.15.73.1.2.1.4,FDDI-SMT73-MIB::fddimibSMTHiVersionId,INTEGER,read-only,,mandatory,,The highest version of SMT that this station supports (refer to ANSI 7.1.2.2).
.1.3.6.1.2.1.10.15.73.1.2.1.5,FDDI-SMT73-MIB::fddimibSMTLoVersionId,INTEGER,read-only,,mandatory,,The lowest version of SMT that this station supports (refer to ANSI 7.1.2.2).
.1.3.6.1.2.1.10.15.73.1.2.1.6,FDDI-SMT73-MIB::fddimibSMTUserData,OCTET,read-write,,mandatory,,This variable contains 32 octets of user defined information. The information shall be an ASCII string.
.1.3.6.1.2.1.10.15.73.1.2.1.7,FDDI-SMT73-MIB::fddimibSMTMIBVersionId,INTEGER,read-only,,mandatory,,The version of the FDDI MIB of this station. The value of this variable is 1 for this SMT revision.
.1.3.6.1.2.1.10.15.73.1.2.1.8,FDDI-SMT73-MIB::fddimibSMTMACCts,INTEGER,read-only,,mandatory,,The number of MACs in this station or concentrator.
.1.3.6.1.2.1.10.15.73.1.2.1.9,FDDI-SMT73-MIB::fddimibSMTNonMasterCts,INTEGER,read-only,,mandatory,,The value of this variable is the number of A, B, and S ports in this station or concentrator.
.1.3.6.1.2.1.10.15.73.1.2.1.10,FDDI-SMT73-MIB::fddimibSMTMasterCts,INTEGER,read-only,,mandatory,,The number of M Ports in a node. If the node is not a concentrator, the value of the variable is zero.
.1.3.6.1.2.1.10.15.73.1.2.1.11,FDDI-SMT73-MIB::fddimibSMTAvailablePaths,INTEGER,read-only,,mandatory,,A value that indicates the PATH types available in the station. The value is a sum. This value initially takes the value zero, then for each type of PATH that this node has available, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 For example, a station having Primary and Local PATHs available would have a value of 5 (2**0 + 2**2).
.1.3.6.1.2.1.10.15.73.1.2.1.12,FDDI-SMT73-MIB::fddimibSMTConfigCapabilities,INTEGER,read-only,,mandatory,,A value that indicates the configuration capabilities of a node. The 'Hold Available' bit indicates the support of the optional Hold Function, which is controlled by fddiSMTConfigPolicy. The 'CF-Wrap-AB' bit indicates that the station has the capability of performing a wrap_ab (refer to ANSI SMT 9.7.2.2). The value is a sum. This value initially takes the value zero, then for each of the configuration policies currently enforced on the node, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power holdAvailable 0 CF-Wrap-AB 1 
.1.3.6.1.2.1.10.15.73.1.2.1.13,FDDI-SMT73-MIB::fddimibSMTConfigPolicy,INTEGER,read-write,,mandatory,,A value that indicates the configuration policies currently desired in a node. 'Hold' is one of the terms used for the Hold Flag, an optional ECM flag used to enable the optional Hold policy. The value is a sum. This value initially takes the value zero, then for each of the configuration policies currently enforced on the node, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power configurationhold 0 
.1.3.6.1.2.1.10.15.73.1.2.1.14,FDDI-SMT73-MIB::fddimibSMTConnectionPolicy,INTEGER,read-write,,mandatory,,A value representing the connection policies in effect in a node. A station sets the corresponding bit for each of the connection types that it rejects. The letter designations, X and Y, in the 'rejectX-Y' names have the following significance: X represents the PC-Type of the local PORT and Y represents the PC_Type of the adjacent PORT (PC_Neighbor). The evaluation of Connection- Policy (PC-Type, PC-Neighbor) is done to determine the setting of T- Val(3) in the PC-Signalling sequence (refer to ANSI 9.6.3). Note that Bit 15, (rejectM-M), is always set and cannot be cleared. The value is a sum. This value initially takes the value zero, then for each of the connection policies currently enforced on the node, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power rejectA-A 0 rejectA-B 1 rejectA-S 2 rejectA-M 3 rejectB-A 4 rejectB-B 5 rejectB-S 6 rejectB-M 7 rejectS-A 8 rejectS-B 9 rejectS-S 10 rejectS-M 11 rejectM-A 12 rejectM-B 13 rejectM-S 14 rejectM-M 15 
.1.3.6.1.2.1.10.15.73.1.2.1.15,FDDI-SMT73-MIB::fddimibSMTTNotify,INTEGER,read-write,,mandatory,,The timer, expressed in seconds, used in the Neighbor Notification protocol. It has a range of 2 seconds to 30 seconds, and its default value is 30 seconds (refer to ANSI SMT 8.2).
.1.3.6.1.2.1.10.15.73.1.2.1.16,FDDI-SMT73-MIB::fddimibSMTStatRptPolicy,INTEGER,read-write,,mandatory,true(1):false(2),If true, indicates that the node will generate Status Reporting Frames for its implemented events and conditions. It has an initial value of true. This variable determines the value of the SR_Enable Flag (refer to ANSI SMT 8.3.2.1).
.1.3.6.1.2.1.10.15.73.1.2.1.17,FDDI-SMT73-MIB::fddimibSMTTraceMaxExpiration,INTEGER,read-write,,mandatory,,Reference Trace_Max (refer to ANSI SMT 9.4.4.2.2).
.1.3.6.1.2.1.10.15.73.1.2.1.18,FDDI-SMT73-MIB::fddimibSMTBypassPresent,INTEGER,read-only,,mandatory,true(1):false(2),A flag indicating if the station has a bypass on its AB port pair.
.1.3.6.1.2.1.10.15.73.1.2.1.19,FDDI-SMT73-MIB::fddimibSMTECMState,INTEGER,read-only,,mandatory,ec0(1):ec1(2):ec2(3):ec3(4):ec4(5):ec5(6):ec6(7):ec7(8),Indicates the current state of the ECM state machine (refer to ANSI SMT 9.5.2).
.1.3.6.1.2.1.10.15.73.1.2.1.20,FDDI-SMT73-MIB::fddimibSMTCFState,INTEGER,read-only,,mandatory,cf0(1):cf1(2):cf2(3):cf3(4):cf4(5):cf5(6):cf6(7):cf7(8):cf8(9):cf9(10):cf10(11):cf11(12):cf12(13),The attachment configuration for the station or concentrator (refer to ANSI SMT 9.7.2.2).
.1.3.6.1.2.1.10.15.73.1.2.1.21,FDDI-SMT73-MIB::fddimibSMTRemoteDisconnectFlag,INTEGER,read-only,,mandatory,true(1):false(2),A flag indicating that the station was remotely disconnected from the network as a result of receiving an fddiSMTAction, disconnect (refer to ANSI SMT 6.4.5.3) in a Parameter Management Frame. A station requires a Connect Action to rejoin and clear the flag (refer to ANSI SMT 6.4.5.2).
.1.3.6.1.2.1.10.15.73.1.2.1.22,FDDI-SMT73-MIB::fddimibSMTStationStatus,INTEGER,read-only,,mandatory,concatenated(1):separated(2):thru(3),The current status of the primary and secondary paths within this station.
.1.3.6.1.2.1.10.15.73.1.2.1.23,FDDI-SMT73-MIB::fddimibSMTPeerWrapFlag,INTEGER,read-only,,mandatory,true(1):false(2),This variable assumes the value of the PeerWrapFlag in CFM (refer to ANSI SMT 9.7.2.4.4).
.1.3.6.1.2.1.10.15.73.1.2.1.24,FDDI-SMT73-MIB::fddimibSMTTimeStamp,INTEGER,read-only,,mandatory,,This variable assumes the value of TimeStamp (refer to ANSI SMT 8.3.2.1).
.1.3.6.1.2.1.10.15.73.1.2.1.25,FDDI-SMT73-MIB::fddimibSMTTransitionTimeStamp,INTEGER,read-only,,mandatory,,This variable assumes the value of TransitionTimeStamp (refer to ANSI SMT 8.3.2.1).
.1.3.6.1.2.1.10.15.73.1.2.1.26,FDDI-SMT73-MIB::fddimibSMTStationAction,INTEGER,read-write,,mandatory,other(1):connect(2):disconnect(3):path-Test(4):self-Test(5):disable-a(6):disable-b(7):disable-m(8),This object, when read, always returns a value of other(1). The behavior of setting this variable to each of the acceptable values is as follows: other(1): Results in an appropriate error. connect(2): Generates a Connect signal to ECM to begin a connection sequence. See ANSI Ref 9.4.2. disconnect(3): Generates a Disconnect signal to ECM. see ANSI Ref 9.4.2. path-Test(4): Initiates a station Path_Test. The Path_Test variable (see ANSI Ref 9.4.1) is set to 'Testing'. The results of this action are not specified in this standard. self-Test(5): Initiates a station Self_Test. The results of this action are not specified in this standard. disable-a(6): Causes a PC_Disable on the A port if the A port mode is peer. disable-b(7): Causes a PC_Disable on the B port if the B port mode is peer. disable-m(8): Causes a PC_Disable on all M ports. Attempts to set this object to all other values results in an appropriate error. The result of setting this variable to path-Test(4) or self- Test(5) is implementation-specific.
.1.3.6.1.2.1.10.15.73.2,FDDI-SMT73-MIB::fddimibMAC,,,,,,
.1.3.6.1.2.1.10.15.73.2.1,FDDI-SMT73-MIB::fddimibMACNumber,INTEGER,read-only,,mandatory,,The total number of MAC implementations (across all SMTs) on this network management application entity. The value for this variable must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.73.2.2,FDDI-SMT73-MIB::fddimibMACTable,,not-accessible,,mandatory,,A list of MAC entries. The number of entries shall not exceed the value of fddimibMACNumber.
.1.3.6.1.2.1.10.15.73.2.2.1,FDDI-SMT73-MIB::fddimibMACEntry,,not-accessible,fddimibMACSMTIndex:fddimibMACIndex,mandatory,,A MAC entry containing information common to a given MAC.
.1.3.6.1.2.1.10.15.73.2.2.1.1,FDDI-SMT73-MIB::fddimibMACSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this MAC.
.1.3.6.1.2.1.10.15.73.2.2.1.2,FDDI-SMT73-MIB::fddimibMACIndex,INTEGER,read-only,,mandatory,,Index variable for uniquely identifying the MAC object instances, which is the same as the corresponding resource index in SMT.
.1.3.6.1.2.1.10.15.73.2.2.1.3,FDDI-SMT73-MIB::fddimibMACIfIndex,INTEGER,read-only,,mandatory,,The value of the MIB-II ifIndex corresponding to this MAC. If none is applicable, 0 is returned.
.1.3.6.1.2.1.10.15.73.2.2.1.4,FDDI-SMT73-MIB::fddimibMACFrameStatusFunctions,INTEGER,read-only,,mandatory,,Indicates the MAC's optional Frame Status processing functions. The value is a sum. This value initially takes the value zero, then for each function present, 2 raised to a power is added to the sum. The powers are according to the following table: function Power fs-repeating 0 fs-setting 1 fs-clearing 2 
.1.3.6.1.2.1.10.15.73.2.2.1.5,FDDI-SMT73-MIB::fddimibMACTMaxCapability,INTEGER,read-only,,mandatory,,Indicates the maximum time value of fddiMACTMax that this MAC can support.
.1.3.6.1.2.1.10.15.73.2.2.1.6,FDDI-SMT73-MIB::fddimibMACTVXCapability,INTEGER,read-only,,mandatory,,Indicates the maximum time value of fddiMACTvxValue that this MAC can support.
.1.3.6.1.2.1.10.15.73.2.2.1.7,FDDI-SMT73-MIB::fddimibMACAvailablePaths,INTEGER,read-only,,mandatory,,Indicates the paths available for this MAC (refer to ANSI SMT 9.7.7). The value is a sum. This value initially takes the value zero, then for each type of PATH that this MAC has available, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 
.1.3.6.1.2.1.10.15.73.2.2.1.8,FDDI-SMT73-MIB::fddimibMACCurrentPath,INTEGER,read-only,,mandatory,isolated(1):local(2):secondary(3):primary(4):concatenated(5):thru(6),Indicates the Path into which this MAC is currently inserted (refer to ANSI 9.7.7).
.1.3.6.1.2.1.10.15.73.2.2.1.9,FDDI-SMT73-MIB::fddimibMACUpstreamNbr,OCTET,read-only,,mandatory,,The MAC's upstream neighbor's long individual MAC address. It has an initial value of the SMT- Unknown-MAC Address and is only modified as specified by the Neighbor Information Frame protocol (refer to ANSI SMT 7.2.1 and 8.2).
.1.3.6.1.2.1.10.15.73.2.2.1.10,FDDI-SMT73-MIB::fddimibMACDownstreamNbr,OCTET,read-only,,mandatory,,The MAC's downstream neighbor's long individual MAC address. It has an initial value of the SMT- Unknown-MAC Address and is only modified as specified by the Neighbor Information Frame protocol (refer to ANSI SMT 7.2.1 and 8.2).
.1.3.6.1.2.1.10.15.73.2.2.1.11,FDDI-SMT73-MIB::fddimibMACOldUpstreamNbr,OCTET,read-only,,mandatory,,The previous value of the MAC's upstream neighbor's long individual MAC address. It has an initial value of the SMT-Unknown- MAC Address and is only modified as specified by the Neighbor Information Frame protocol (refer to ANSI SMT 7.2.1 and 8.2).
.1.3.6.1.2.1.10.15.73.2.2.1.12,FDDI-SMT73-MIB::fddimibMACOldDownstreamNbr,OCTET,read-only,,mandatory,,The previous value of the MAC's downstream neighbor's long individual MAC address. It has an initial value of the SMT- Unknown-MAC Address and is only modified as specified by the Neighbor Information Frame protocol (refer to ANSI SMT 7.2.1 and 8.2).
.1.3.6.1.2.1.10.15.73.2.2.1.13,FDDI-SMT73-MIB::fddimibMACDupAddressTest,INTEGER,read-only,,mandatory,none(1):pass(2):fail(3),The Duplicate Address Test flag, Dup_Addr_Test (refer to ANSI 8.2).
.1.3.6.1.2.1.10.15.73.2.2.1.14,FDDI-SMT73-MIB::fddimibMACRequestedPaths,INTEGER,read-write,,mandatory,,List of permitted Paths which specifies the Path(s) into which the MAC may be inserted (refer to ansi SMT 9.7). The value is a sum which represents the individual paths that are desired. This value initially takes the value zero, then for each type of PATH that this node is, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power local 0 secondary-alternate 1 primary-alternate 2 concatenated-alternate 3 secondary-preferred 4 primary-preferred 5 concatenated-preferred 6 thru 7 
.1.3.6.1.2.1.10.15.73.2.2.1.15,FDDI-SMT73-MIB::fddimibMACDownstreamPORTType,INTEGER,read-only,,mandatory,a(1):b(2):s(3):m(4):none(5),Indicates the PC-Type of the first port that is downstream of this MAC (the exit port).
.1.3.6.1.2.1.10.15.73.2.2.1.16,FDDI-SMT73-MIB::fddimibMACSMTAddress,OCTET,read-only,,mandatory,,The 48-bit individual address of the MAC used for SMT frames.
.1.3.6.1.2.1.10.15.73.2.2.1.17,FDDI-SMT73-MIB::fddimibMACTReq,INTEGER,read-only,,mandatory,,This variable is the T_Req_value passed to the MAC. Without having detected a duplicate, the time value of this variable shall assume the maximum supported time value which is less than or equal to the time value of fddiPATHMaxT-Req. When a MAC has an address detected as a duplicate, it may use a time value for this variable greater than the time value of fddiPATHTMaxLowerBound. A station shall cause claim when the new T_Req may cause the value of T_Neg to change in the claim process, (i.e., time value new T_Req < T_Neg, or old T_Req = T_Neg).
.1.3.6.1.2.1.10.15.73.2.2.1.18,FDDI-SMT73-MIB::fddimibMACTNeg,INTEGER,read-only,,mandatory,,It is reported as a FddiTimeNano number.
.1.3.6.1.2.1.10.15.73.2.2.1.19,FDDI-SMT73-MIB::fddimibMACTMax,INTEGER,read-only,,mandatory,,This variable is the T_Max_value passed to the MAC. The time value of this variable shall assume the minimum suported time value which is greater than or equal to the time value of fddiPATHT- MaxLowerBound
.1.3.6.1.2.1.10.15.73.2.2.1.20,FDDI-SMT73-MIB::fddimibMACTvxValue,INTEGER,read-only,,mandatory,,This variable is the TVX_value passed to the MAC. The time value of this variable shall assume the minimum suported time value which is greater than or equal to the time value of fddiPATHTVXLowerBound.
.1.3.6.1.2.1.10.15.73.2.2.1.21,FDDI-SMT73-MIB::fddimibMACFrameCts,Counter32,read-only,,mandatory,,A count of the number of frames received by this MAC (refer to ANSI MAC 7.5.1).
.1.3.6.1.2.1.10.15.73.2.2.1.22,FDDI-SMT73-MIB::fddimibMACCopiedCts,Counter32,read-only,,mandatory,,A count that should as closely as possible match the number of frames addressed to (A bit set) and successfully copied into the station's receive buffers (C bit set) by this MAC (refer to ANSI MAC 7.5). Note that this count does not include MAC frames.
.1.3.6.1.2.1.10.15.73.2.2.1.23,FDDI-SMT73-MIB::fddimibMACTransmitCts,Counter32,read-only,,mandatory,,A count that should as closely as possible match the number of frames transmitted by this MAC (refer to ANSI MAC 7.5). Note that this count does not include MAC frames.
.1.3.6.1.2.1.10.15.73.2.2.1.24,FDDI-SMT73-MIB::fddimibMACErrorCts,Counter32,read-only,,mandatory,,A count of the number of frames that were detected in error by this MAC that had not been detected in error by another MAC (refer to ANSI MAC 7.5.2).
.1.3.6.1.2.1.10.15.73.2.2.1.25,FDDI-SMT73-MIB::fddimibMACLostCts,Counter32,read-only,,mandatory,,A count of the number of instances that this MAC detected a format error during frame reception such that the frame was stripped (refer to ANSI MAC 7.5.3).
.1.3.6.1.2.1.10.15.73.2.2.1.26,FDDI-SMT73-MIB::fddimibMACFrameErrorThreshold,INTEGER,read-write,,mandatory,,A threshold for determining when a MAC Condition report (see ANSI 8.3.1.1) shall be generated. Stations not supporting variable thresholds shall have a value of 0 and a range of (0..0).
.1.3.6.1.2.1.10.15.73.2.2.1.27,FDDI-SMT73-MIB::fddimibMACFrameErrorRatio,INTEGER,read-only,,mandatory,,This variable is the value of the ratio, ((delta fddiMACLostCts + delta fddiMACErrorCts) / (delta fddiMACFrameCts + delta fddiMACLostCts )) * 2**16 
.1.3.6.1.2.1.10.15.73.2.2.1.28,FDDI-SMT73-MIB::fddimibMACRMTState,INTEGER,read-only,,mandatory,rm0(1):rm1(2):rm2(3):rm3(4):rm4(5):rm5(6):rm6(7):rm7(8),Indicates the current state of the RMT State Machine (refer to ANSI 10.3.2).
.1.3.6.1.2.1.10.15.73.2.2.1.29,FDDI-SMT73-MIB::fddimibMACDaFlag,INTEGER,read-only,,mandatory,true(1):false(2),The RMT flag Duplicate Address Flag, DA_Flag (refer to ANSI 10.2.1.2).
.1.3.6.1.2.1.10.15.73.2.2.1.30,FDDI-SMT73-MIB::fddimibMACUnaDaFlag,INTEGER,read-only,,mandatory,true(1):false(2),A flag, UNDA_Flag (refer to ANSI 8.2.2.1), set when the upstream neighbor reports a duplicate address condition. Cleared when the condition clears.
.1.3.6.1.2.1.10.15.73.2.2.1.31,FDDI-SMT73-MIB::fddimibMACFrameErrorFlag,INTEGER,read-only,,mandatory,true(1):false(2),Indicates the MAC Frame Error Condition is present when set. Cleared when the condition clears and on station initialization.
.1.3.6.1.2.1.10.15.73.2.2.1.32,FDDI-SMT73-MIB::fddimibMACMAUnitdataAvailable,INTEGER,read-only,,mandatory,true(1):false(2),This variable shall take on the value of the MAC_Avail flag defined in RMT.
.1.3.6.1.2.1.10.15.73.2.2.1.33,FDDI-SMT73-MIB::fddimibMACHardwarePresent,INTEGER,read-only,,mandatory,true(1):false(2),This variable indicates the presence of underlying hardware support for this MAC object. If the value of this object is false(2), the reporting of the objects in this entry may be handled in an implementation-specific manner.
.1.3.6.1.2.1.10.15.73.2.2.1.34,FDDI-SMT73-MIB::fddimibMACMAUnitdataEnable,INTEGER,read-write,,mandatory,true(1):false(2),This variable determines the value of the MA_UNITDATA_Enable flag in RMT. The default and initial value of this flag is true(1).
.1.3.6.1.2.1.10.15.73.3,FDDI-SMT73-MIB::fddimibMACCounters,,,,,,
.1.3.6.1.2.1.10.15.73.3.1,FDDI-SMT73-MIB::fddimibMACCountersTable,,not-accessible,,mandatory,,A list of MAC Counters entries. The number of entries shall not exceed the value of fddimibMACNumber.
.1.3.6.1.2.1.10.15.73.3.1.1,FDDI-SMT73-MIB::fddimibMACCountersEntry,,not-accessible,fddimibMACSMTIndex:fddimibMACIndex,mandatory,,A MAC Counters entry containing information common to a given MAC.
.1.3.6.1.2.1.10.15.73.3.1.1.1,FDDI-SMT73-MIB::fddimibMACTokenCts,Counter32,read-only,,mandatory,,A count that should as closely as possible match the number of times the station has received a token (total of non-restricted and restricted) on this MAC (see ANSI MAC 7.4). This count is valuable for determination of network load.
.1.3.6.1.2.1.10.15.73.3.1.1.2,FDDI-SMT73-MIB::fddimibMACTvxExpiredCts,Counter32,read-only,,mandatory,,A count that should as closely as possible match the number of times that TVX has expired.
.1.3.6.1.2.1.10.15.73.3.1.1.3,FDDI-SMT73-MIB::fddimibMACNotCopiedCts,Counter32,read-only,,mandatory,,A count that should as closely as possible match the number of frames that were addressed to this MAC but were not copied into its receive buffers (see ANSI MAC 7.5). For example, this might occur due to local buffer congestion. Because of implementation considerations, this count may not match the actual number of frames not copied. It is not a requirement that this count be exact. Note that this count does not include MAC frames.
.1.3.6.1.2.1.10.15.73.3.1.1.4,FDDI-SMT73-MIB::fddimibMACLateCts,Counter32,read-only,,mandatory,,A count that should as closely as possible match the number of TRT expirations since this MAC was reset or a token was received (refer to ANSI MAC 7.4.5).
.1.3.6.1.2.1.10.15.73.3.1.1.5,FDDI-SMT73-MIB::fddimibMACRingOpCts,Counter32,read-only,,mandatory,,The count of the number of times the ring has entered the 'Ring_Operational' state from the 'Ring Not Operational' state. This count is updated when a SM_MA_STATUS.Indication of a change in the Ring_Operational status occurs (refer to ANSI 6.1.4). Because of implementation considerations, this count may be less than the actual RingOp_Ct. It is not a requirement that this count be exact.
.1.3.6.1.2.1.10.15.73.3.1.1.6,FDDI-SMT73-MIB::fddimibMACNotCopiedRatio,INTEGER,read-only,,mandatory,,This variable is the value of the ratio: (delta fddiMACNotCopiedCts / (delta fddiMACCopiedCts + delta fddiMACNotCopiedCts )) * 2**16 
.1.3.6.1.2.1.10.15.73.3.1.1.7,FDDI-SMT73-MIB::fddimibMACNotCopiedFlag,INTEGER,read-only,,mandatory,true(1):false(2),Indicates that the Not Copied condition is present when read as true(1). Set to false(2) when the condition clears and on station initialization.
.1.3.6.1.2.1.10.15.73.3.1.1.8,FDDI-SMT73-MIB::fddimibMACNotCopiedThreshold,INTEGER,read-write,,mandatory,,A threshold for determining when a MAC condition report shall be generated. Stations not supporting variable thresholds shall have a value of 0 and a range of (0..0).
.1.3.6.1.2.1.10.15.73.4,FDDI-SMT73-MIB::fddimibPATH,,,,,,
.1.3.6.1.2.1.10.15.73.4.1,FDDI-SMT73-MIB::fddimibPATHNumber,INTEGER,read-only,,mandatory,,The total number of PATHs possible (across all SMTs) on this network management application entity. The value for this variable must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.73.4.2,FDDI-SMT73-MIB::fddimibPATHTable,,not-accessible,,mandatory,,A list of PATH entries. The number of entries shall not exceed the value of fddimibPATHNumber.
.1.3.6.1.2.1.10.15.73.4.2.1,FDDI-SMT73-MIB::fddimibPATHEntry,,not-accessible,fddimibPATHSMTIndex:fddimibPATHIndex,mandatory,,A PATH entry containing information common to a given PATH.
.1.3.6.1.2.1.10.15.73.4.2.1.1,FDDI-SMT73-MIB::fddimibPATHSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this PATH.
.1.3.6.1.2.1.10.15.73.4.2.1.2,FDDI-SMT73-MIB::fddimibPATHIndex,INTEGER,read-only,,mandatory,,Index variable for uniquely identifying the primary, secondary and local PATH object instances. Local PATH object instances are represented with integer values 3 to 255.
.1.3.6.1.2.1.10.15.73.4.2.1.3,FDDI-SMT73-MIB::fddimibPATHTVXLowerBound,INTEGER,read-write,,mandatory,,Specifies the minimum time value of fddiMACTvxValue that shall be used by any MAC that is configured in this path. The operational value of fddiMACTvxValue is managed by settting this variable. This variable has the time value range of: 0 < fddimibPATHTVXLowerBound < fddimibPATHMaxTReq Changes to this variable shall either satisfy the time value relationship: fddimibPATHTVXLowerBound <= fddimibMACTVXCapability of each of the MACs currently on the path, or be considered out of range. The initial value of fddimibPATHTVXLowerBound shall be 2500 nsec (2.5 ms).
.1.3.6.1.2.1.10.15.73.4.2.1.4,FDDI-SMT73-MIB::fddimibPATHTMaxLowerBound,INTEGER,read-write,,mandatory,,Specifies the minimum time value of fddiMACTMax that shall be used by any MAC that is configured in this path. The operational value of fddiMACTMax is managed by setting this variable. This variable has the time value range of: fddimibPATHMaxTReq <= fddimibPATHTMaxLowerBound and an absolute time value range of: 10000nsec (10 msec) <= fddimibPATHTMaxLowerBound Changes to this variable shall either satisfy the time value relationship: fddimibPATHTMaxLowerBound < fddimibMACTMaxCapability of each of the MACs currently on the path, or be considered out of range. The initial value of fddimibPATHTMaxLowerBound shall be 165000 nsec (165 msec).
.1.3.6.1.2.1.10.15.73.4.2.1.5,FDDI-SMT73-MIB::fddimibPATHMaxTReq,INTEGER,read-write,,mandatory,,Specifies the maximum time value of fddiMACT-Req that shall be used by any MAC that is configured in this path. The operational value of fddiMACT- Req is managed by setting this variable. This variable has the time value range of: fddimibPATHTVXLowerBound < fddimibPATHMaxTReq <= fddimibPATHTMaxLowerBound. The default value of fddimibPATHMaxTReq is 165000 nsec (165 msec).
.1.3.6.1.2.1.10.15.73.4.3,FDDI-SMT73-MIB::fddimibPATHConfigTable,,not-accessible,,mandatory,,A table of Path configuration entries. This table lists all the resources that may be in this Path.
.1.3.6.1.2.1.10.15.73.4.3.1,FDDI-SMT73-MIB::fddimibPATHConfigEntry,,not-accessible,fddimibPATHConfigSMTIndex:fddimibPATHConfigPATHIndex:fddimibPATHConfigTokenOrder,mandatory,,A collection of objects containing information for a given PATH Configuration entry.
.1.3.6.1.2.1.10.15.73.4.3.1.1,FDDI-SMT73-MIB::fddimibPATHConfigSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this configuration entry.
.1.3.6.1.2.1.10.15.73.4.3.1.2,FDDI-SMT73-MIB::fddimibPATHConfigPATHIndex,INTEGER,read-only,,mandatory,,The value of the PATH resource index associated with this configuration entry.
.1.3.6.1.2.1.10.15.73.4.3.1.3,FDDI-SMT73-MIB::fddimibPATHConfigTokenOrder,INTEGER,read-only,,mandatory,,An object associated with Token order for this entry. Thus if the token passes resources a, b, c and d, in that order, then the value of this object for these resources would be 1, 2, 3 and 4 respectively.
.1.3.6.1.2.1.10.15.73.4.3.1.4,FDDI-SMT73-MIB::fddimibPATHConfigResourceType,INTEGER,read-only,,mandatory,mac(2):port(4),The type of resource associated with this configuration entry.
.1.3.6.1.2.1.10.15.73.4.3.1.5,FDDI-SMT73-MIB::fddimibPATHConfigResourceIndex,INTEGER,read-only,,mandatory,,The value of the SMT resource index used to refer to the instance of this MAC or Port resource.
.1.3.6.1.2.1.10.15.73.4.3.1.6,FDDI-SMT73-MIB::fddimibPATHConfigCurrentPath,INTEGER,read-only,,mandatory,isolated(1):local(2):secondary(3):primary(4):concatenated(5):thru(6),The current insertion status for this resource on this Path.
.1.3.6.1.2.1.10.15.73.5,FDDI-SMT73-MIB::fddimibPORT,,,,,,
.1.3.6.1.2.1.10.15.73.5.1,FDDI-SMT73-MIB::fddimibPORTNumber,INTEGER,read-only,,mandatory,,The total number of PORT implementations (across all SMTs) on this network management application entity. The value for this variable must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.73.5.2,FDDI-SMT73-MIB::fddimibPORTTable,,not-accessible,,mandatory,,A list of PORT entries. The number of entries shall not exceed the value of fddimibPORTNumber.
.1.3.6.1.2.1.10.15.73.5.2.1,FDDI-SMT73-MIB::fddimibPORTEntry,,not-accessible,fddimibPORTSMTIndex:fddimibPORTIndex,mandatory,,A PORT entry containing information common to a given PORT.
.1.3.6.1.2.1.10.15.73.5.2.1.1,FDDI-SMT73-MIB::fddimibPORTSMTIndex,INTEGER,read-only,,mandatory,,The value of the SMT index associated with this PORT.
.1.3.6.1.2.1.10.15.73.5.2.1.2,FDDI-SMT73-MIB::fddimibPORTIndex,INTEGER,read-only,,mandatory,,A unique value for each PORT within a given SMT, which is the same as the corresponding resource index in SMT. The value for each PORT must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.10.15.73.5.2.1.3,FDDI-SMT73-MIB::fddimibPORTMyType,INTEGER,read-only,,mandatory,a(1):b(2):s(3):m(4):none(5),The value of the PORT's PC_Type (refer to ANSI 9.4.1, and 9.6.3.2).
.1.3.6.1.2.1.10.15.73.5.2.1.4,FDDI-SMT73-MIB::fddimibPORTNeighborType,INTEGER,read-only,,mandatory,a(1):b(2):s(3):m(4):none(5),The type of the remote PORT as determined in PCM. This variable has an initial value of none, and is only modified in PC_RCode(3)_Actions (refer to ANSI SMT 9.6.3.2).
.1.3.6.1.2.1.10.15.73.5.2.1.5,FDDI-SMT73-MIB::fddimibPORTConnectionPolicies,INTEGER,read-write,,mandatory,,A value representing the PORT's connection policies desired in the node. The value of pc- mac-lct is a term used in the PC_MAC_LCT Flag (see 9.4.3.2). The value of pc-mac-loop is a term used in the PC_MAC_Loop Flag. The value is a sum. This value initially takes the value zero, then for each PORT policy, 2 raised to a power is added to the sum. The powers are according to the following table: Policy Power pc-mac-lct 0 pc-mac-loop 1 
.1.3.6.1.2.1.10.15.73.5.2.1.6,FDDI-SMT73-MIB::fddimibPORTMACIndicated,INTEGER,read-only,,mandatory,tVal9FalseRVal9False(1):tVal9FalseRVal9True(2):tVal9TrueRVal9False(3):tVal9TrueRVal9True(4),The indications (T_Val(9), R_Val(9)) in PC- Signalling, of the intent to place a MAC in the output token path to a PORT (refer to ANSI SMT 9.6.3.2.).
.1.3.6.1.2.1.10.15.73.5.2.1.7,FDDI-SMT73-MIB::fddimibPORTCurrentPath,INTEGER,read-only,,mandatory,ce0(1):ce1(2):ce2(3):ce3(4):ce4(5):ce5(6),Indicates the Path(s) into which this PORT is currently inserted.
.1.3.6.1.2.1.10.15.73.5.2.1.8,FDDI-SMT73-MIB::fddimibPORTRequestedPaths,OCTET,read-write,,mandatory,,This variable is a list of permitted Paths where each list element defines the Port's permitted Paths. The first octet corresponds to 'none', the second octet to 'tree', and the third octet to 'peer'.
.1.3.6.1.2.1.10.15.73.5.2.1.9,FDDI-SMT73-MIB::fddimibPORTMACPlacement,INTEGER,read-only,,mandatory,,Indicates the MAC, if any, whose transmit path exits the station via this PORT. The value shall be zero if there is no MAC associated with the PORT. Otherwise, the MACIndex of the MAC will be the value of the variable.
.1.3.6.1.2.1.10.15.73.5.2.1.10,FDDI-SMT73-MIB::fddimibPORTAvailablePaths,INTEGER,read-only,,mandatory,,Indicates the Paths which are available to this Port. In the absence of faults, the A and B Ports will always have both the Primary and Secondary Paths available. The value is a sum. This value initially takes the value zero, then for each type of PATH that this port has available, 2 raised to a power is added to the sum. The powers are according to the following table: Path Power Primary 0 Secondary 1 Local 2 
.1.3.6.1.2.1.10.15.73.5.2.1.11,FDDI-SMT73-MIB::fddimibPORTPMDClass,INTEGER,read-only,,mandatory,multimode(1):single-mode1(2):single-mode2(3):sonet(4):low-cost-fiber(5):twisted-pair(6):unknown(7):unspecified(8),This variable indicates the type of PMD entity associated with this port.
.1.3.6.1.2.1.10.15.73.5.2.1.12,FDDI-SMT73-MIB::fddimibPORTConnectionCapabilities,INTEGER,read-only,,mandatory,,A value that indicates the connection capabilities of the port. The pc-mac-lct bit indicates that the station has the capability of setting the PC_MAC_LCT Flag. The pc-mac-loop bit indicates that the station has the capability of setting the PC_MAC_Loop Flag (refer to ANSI 9.4.3.2). The value is a sum. This value initially takes the value zero, then for each capability that this port has, 2 raised to a power is added to the sum. The powers are according to the following table: capability Power pc-mac-lct 0 pc-mac-loop 1 
.1.3.6.1.2.1.10.15.73.5.2.1.13,FDDI-SMT73-MIB::fddimibPORTBSFlag,INTEGER,read-only,,mandatory,true(1):false(2),This variable assumes the value of the BS_Flag (refer to ANSI SMT 9.4.3.3).
.1.3.6.1.2.1.10.15.73.5.2.1.14,FDDI-SMT73-MIB::fddimibPORTLCTFailCts,Counter32,read-only,,mandatory,,The count of the consecutive times the link confidence test (LCT) has failed during connection management (refer to ANSI 9.4.1).
.1.3.6.1.2.1.10.15.73.5.2.1.15,FDDI-SMT73-MIB::fddimibPORTLerEstimate,INTEGER,read-only,,mandatory,,A long term average link error rate. It ranges from 10**-4 to 10**-15 and is reported as the absolute value of the base 10 logarithm (refer to ANSI SMT 9.4.7.5.).
.1.3.6.1.2.1.10.15.73.5.2.1.16,FDDI-SMT73-MIB::fddimibPORTLemRejectCts,Counter32,read-only,,mandatory,,A link error monitoring count of the times that a link has been rejected.
.1.3.6.1.2.1.10.15.73.5.2.1.17,FDDI-SMT73-MIB::fddimibPORTLemCts,Counter32,read-only,,mandatory,,The aggregate link error monitor error count, set to zero only on station initialization.
.1.3.6.1.2.1.10.15.73.5.2.1.18,FDDI-SMT73-MIB::fddimibPORTLerCutoff,INTEGER,read-write,,mandatory,,The link error rate estimate at which a link connection will be broken. It ranges from 10**-4 to 10**-15 and is reported as the absolute value of the base 10 logarithm (default of 7).
.1.3.6.1.2.1.10.15.73.5.2.1.19,FDDI-SMT73-MIB::fddimibPORTLerAlarm,INTEGER,read-write,,mandatory,,The link error rate estimate at which a link connection will generate an alarm. It ranges from 10**-4 to 10**-15 and is reported as the absolute value of the base 10 logarithm of the estimate (default of 8).
.1.3.6.1.2.1.10.15.73.5.2.1.20,FDDI-SMT73-MIB::fddimibPORTConnectState,INTEGER,read-only,,mandatory,disabled(1):connecting(2):standby(3):active(4),An indication of the connect state of this PORT and is equal to the value of Connect_State (refer to ANSI 9.4.1)
.1.3.6.1.2.1.10.15.73.5.2.1.21,FDDI-SMT73-MIB::fddimibPORTPCMState,INTEGER,read-only,,mandatory,pc0(1):pc1(2):pc2(3):pc3(4):pc4(5):pc5(6):pc6(7):pc7(8):pc8(9):pc9(10),The state of this Port's PCM state machine refer to ANSI SMT 9.6.2).
.1.3.6.1.2.1.10.15.73.5.2.1.22,FDDI-SMT73-MIB::fddimibPORTPCWithhold,INTEGER,read-only,,mandatory,none(1):m-m(2):otherincompatible(3):pathnotavailable(4),The value of PC_Withhold (refer to ANSI SMT 9.4.1).
.1.3.6.1.2.1.10.15.73.5.2.1.23,FDDI-SMT73-MIB::fddimibPORTLerFlag,INTEGER,read-only,,mandatory,true(1):false(2),The condition becomes active when the value of fddiPORTLerEstimate is less than or equal to fddiPORTLerAlarm. This will be reported with the Status Report Frames (SRF) (refer to ANSI SMT 7.2.7 and 8.3).
.1.3.6.1.2.1.10.15.73.5.2.1.24,FDDI-SMT73-MIB::fddimibPORTHardwarePresent,INTEGER,read-only,,mandatory,true(1):false(2),This variable indicates the presence of underlying hardware support for this Port object. If the value of this object is false(2), the reporting of the objects in this entry may be handled in an implementation-specific manner.
.1.3.6.1.2.1.10.15.73.5.2.1.25,FDDI-SMT73-MIB::fddimibPORTAction,INTEGER,read-write,,mandatory,other(1):maintPORT(2):enablePORT(3):disablePORT(4):startPORT(5):stopPORT(6),Causes a Control signal to be generated with a control_action of 'Signal' and the 'variable' parameter set with the appropriate value (i.e., PC_Maint, PC_Enable, PC_Disable, PC_Start, or PC_Stop) (refer to ANSI 9.4.2).
.1.3.6.1.2.1.10.16,RFC1381-MIB::lapb,,,,,,
.1.3.6.1.2.1.10.16.1,RFC1381-MIB::lapbAdmnTable,,not-accessible,,mandatory,,This table contains objects that can be changed to manage a LAPB interface. Changing one of these parameters may take effect in the operating LAPB immediately or may wait until the interface is restarted depending on the details of the implementation. Most of the objects in this read-write table have corresponding read-only objects in the lapbOperTable that return the current operating value. The operating values may be different from these configured values if changed by XID negotiation or if a configured parameter was changed after the interface was started.
.1.3.6.1.2.1.10.16.1.1,RFC1381-MIB::lapbAdmnEntry,,not-accessible,lapbAdmnIndex,mandatory,,Configured parameter values for a specific LAPB.
.1.3.6.1.2.1.10.16.1.1.1,RFC1381-MIB::lapbAdmnIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the LAPB interface.
.1.3.6.1.2.1.10.16.1.1.2,RFC1381-MIB::lapbAdmnStationType,INTEGER,read-write,,mandatory,dte(1):dce(2):dxe(3),Identifies the desired station type of this interface.
.1.3.6.1.2.1.10.16.1.1.3,RFC1381-MIB::lapbAdmnControlField,INTEGER,read-write,,mandatory,modulo8(1):modulo128(2),The desired size of the sequence numbers used to number frames.
.1.3.6.1.2.1.10.16.1.1.4,RFC1381-MIB::lapbAdmnTransmitN1FrameSize,INTEGER,read-write,,mandatory,,The default maximum N1 frame size desired in number of bits for a frame transmitted by this DTE. This excludes flags and 0 bits inserted for transparency.
.1.3.6.1.2.1.10.16.1.1.5,RFC1381-MIB::lapbAdmnReceiveN1FrameSize,INTEGER,read-write,,mandatory,,The default maximum N1 frame size desired in number of bits for a frame the DCE/remote DTE transmits to this DTE. This excludes flags and 0 bits inserted for transparency.
.1.3.6.1.2.1.10.16.1.1.6,RFC1381-MIB::lapbAdmnTransmitKWindowSize,INTEGER,read-write,,mandatory,,The default transmit window size for this Interface. This is the maximum number of unacknowledged sequenced PDUs that may be outstanding from this DTE at any one time.
.1.3.6.1.2.1.10.16.1.1.7,RFC1381-MIB::lapbAdmnReceiveKWindowSize,INTEGER,read-write,,mandatory,,The default receive window size for this Interface. This is the maximum number of unacknowledged sequenced PDUs that may be outstanding from the DCE/remote DTE at any one time.
.1.3.6.1.2.1.10.16.1.1.8,RFC1381-MIB::lapbAdmnN2RxmitCount,INTEGER,read-write,,mandatory,,The default N2 retry counter for this interface. This specifies the number of times a PDU will be resent after the T1 timer expires without an acknowledgement for the PDU.
.1.3.6.1.2.1.10.16.1.1.9,RFC1381-MIB::lapbAdmnT1AckTimer,INTEGER,read-write,,mandatory,,The default T1 timer for this interface. This specifies the maximum time in Milliseconds to wait for acknowledgment of a PDU.
.1.3.6.1.2.1.10.16.1.1.10,RFC1381-MIB::lapbAdmnT2AckDelayTimer,INTEGER,read-write,,mandatory,,The default T2 timer for this interface. This specifies the maximum time in Milliseconds to wait before sending an acknowledgment for a sequenced PDU. A value of zero means there will be no delay in acknowledgement generation.
.1.3.6.1.2.1.10.16.1.1.11,RFC1381-MIB::lapbAdmnT3DisconnectTimer,INTEGER,read-write,,mandatory,,The T3 timer for this interface. This specifies the time in Milliseconds to wait before considering the link disconnected. A value of zero indicates the link will be considered disconnected upon completion of the frame exchange to disconnect the link.
.1.3.6.1.2.1.10.16.1.1.12,RFC1381-MIB::lapbAdmnT4IdleTimer,INTEGER,read-write,,mandatory,,The T4 timer for this interface. This specifies the maximum time in Milliseconds to allow without frames being exchanged on the data link. A value of 2147483647 indicates no idle timer is being kept.
.1.3.6.1.2.1.10.16.1.1.13,RFC1381-MIB::lapbAdmnActionInitiate,INTEGER,read-write,,mandatory,sendSABM(1):sendDISC(2):sendDM(3):none(4):other(5),This identifies the action LAPB will take to initiate link set-up.
.1.3.6.1.2.1.10.16.1.1.14,RFC1381-MIB::lapbAdmnActionRecvDM,INTEGER,read-write,,mandatory,sendSABM(1):sendDISC(2):other(3),This identifies the action LAPB will take when it receives a DM response.
.1.3.6.1.2.1.10.16.2,RFC1381-MIB::lapbOperTable,,not-accessible,,mandatory,,This table contains configuration information about interface parameters currently set in the interface. Many of these objects have corresponding objects in the lapbAdmnTable.
.1.3.6.1.2.1.10.16.2.1,RFC1381-MIB::lapbOperEntry,,not-accessible,lapbOperIndex,mandatory,,Currently set parameter values for a specific LAPB.
.1.3.6.1.2.1.10.16.2.1.1,RFC1381-MIB::lapbOperIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the LAPB interface.
.1.3.6.1.2.1.10.16.2.1.2,RFC1381-MIB::lapbOperStationType,INTEGER,read-only,,mandatory,dte(1):dce(2):dxe(3),Identifies the current operating station type of this interface. A value of dxe (3) indicates XID negotiation has not yet taken place.
.1.3.6.1.2.1.10.16.2.1.3,RFC1381-MIB::lapbOperControlField,INTEGER,read-only,,mandatory,modulo8(1):modulo128(2),The current operating size of the sequence numbers used to number frames.
.1.3.6.1.2.1.10.16.2.1.4,RFC1381-MIB::lapbOperTransmitN1FrameSize,INTEGER,read-only,,mandatory,,The current operating N1 frame size used for the maximum number of bits in a frame this DTE can transmit. This excludes flags and 0 bits inserted for transparency.
.1.3.6.1.2.1.10.16.2.1.5,RFC1381-MIB::lapbOperReceiveN1FrameSize,INTEGER,read-only,,mandatory,,The current operating N1 frame size used for the maximum number of bits in a frame the DCE/remote DTE can transmit. This excludes flags and 0 bits inserted for transparency.
.1.3.6.1.2.1.10.16.2.1.6,RFC1381-MIB::lapbOperTransmitKWindowSize,INTEGER,read-only,,mandatory,,The current PDU window size this Interface uses to transmit. This is the maximum number of unacknowledged sequenced PDUs that may be outstanding from this DTE at any one time.
.1.3.6.1.2.1.10.16.2.1.7,RFC1381-MIB::lapbOperReceiveKWindowSize,INTEGER,read-only,,mandatory,,The current receive PDU window size for this Interface. This is the maximum number of unacknowledged sequenced PDUs that may be outstanding from the DCE/remote DTE at any one time.
.1.3.6.1.2.1.10.16.2.1.8,RFC1381-MIB::lapbOperN2RxmitCount,INTEGER,read-only,,mandatory,,The current N2 retry counter used for this interface. This specifies the number of times a PDU will be resent after the T1 timer expires without an acknowledgement for the PDU.
.1.3.6.1.2.1.10.16.2.1.9,RFC1381-MIB::lapbOperT1AckTimer,INTEGER,read-only,,mandatory,,The current T1 timer for this interface. This specifies the maximum time in Milliseconds to wait for acknowledgment of a PDU.
.1.3.6.1.2.1.10.16.2.1.10,RFC1381-MIB::lapbOperT2AckDelayTimer,INTEGER,read-only,,mandatory,,The current T2 timer for this interface. This specifies the maximum time in Milliseconds to wait before sending an acknowledgment for a sequenced PDU. A value of zero means there will be no delay in acknowledgement generation.
.1.3.6.1.2.1.10.16.2.1.11,RFC1381-MIB::lapbOperT3DisconnectTimer,INTEGER,read-only,,mandatory,,The current T3 timer for this interface. This specifies the time in Milliseconds to wait before considering the link disconnected. A value of zero indicates the link will be considered disconnected upon completion of the frame exchange to disconnect the link.
.1.3.6.1.2.1.10.16.2.1.12,RFC1381-MIB::lapbOperT4IdleTimer,INTEGER,read-write,,mandatory,,The current T4 timer for this interface. This specifies the maximum time in Milliseconds to allow without frames being exchanged on the data link. A value of 2147483647 indicates no idle timer is being kept.
.1.3.6.1.2.1.10.16.2.1.13,RFC1381-MIB::lapbOperPortId,OBJECT,read-only,,mandatory,,This object identifies an instance of the index object in the first group of objects in the MIB specific to the physical device or interface used to send and receive frames. If an agent does not support any such objects, it should return nullSpec OBJECT IDENTIFIER {0 0}.
.1.3.6.1.2.1.10.16.2.1.14,RFC1381-MIB::lapbOperProtocolVersionId,OBJECT,read-only,,mandatory,,This object identifies the version of the lapb protocol implemented by this interface.
.1.3.6.1.2.1.10.16.3,RFC1381-MIB::lapbFlowTable,,not-accessible,,mandatory,,This table defines the objects recorded by LAPB to provide information about the traffic flow through the interface.
.1.3.6.1.2.1.10.16.3.1,RFC1381-MIB::lapbFlowEntry,,not-accessible,lapbFlowIfIndex,mandatory,,The information regarding the effects of flow controls in LAPB.
.1.3.6.1.2.1.10.16.3.1.1,RFC1381-MIB::lapbFlowIfIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the LAPB Interface.
.1.3.6.1.2.1.10.16.3.1.2,RFC1381-MIB::lapbFlowStateChanges,Counter32,read-only,,mandatory,,The number of LAPB State Changes, including resets.
.1.3.6.1.2.1.10.16.3.1.3,RFC1381-MIB::lapbFlowChangeReason,INTEGER,read-only,,mandatory,notStarted(1):abmEntered(2):abmeEntered(3):abmReset(4):abmeReset(5):dmReceived(6):dmSent(7):discReceived(8):discSent(9):frmrReceived(10):frmrSent(11):n2Timeout(12):other(13),The reason for the most recent incrementing of lapbFlowStateChanges. A DM or DISC frame generated to initiate link set-up does not alter this object. When the MIB-II object ifOperStatus does not have a value of testing, there exists a correlation between this object and ifOperStatus. IfOperStatus will have a value of up when this object contains: abmEntered, abmeEntered, abmReset, or abmeReset. IfOperStatus will have a value of down when this object has a value of notStarted, or dmReceived through n2Timeout. There is no correlation when this object has the value other.
.1.3.6.1.2.1.10.16.3.1.4,RFC1381-MIB::lapbFlowCurrentMode,INTEGER,read-only,,mandatory,disconnected(1):linkSetup(2):frameReject(3):disconnectRequest(4):informationTransfer(5):rejFrameSent(6):waitingAcknowledgement(7):stationBusy(8):remoteStationBusy(9):bothStationsBusy(10):waitingAckStationBusy(11):waitingAckRemoteBusy(12):waitingAckBothBusy(13):rejFrameSentRemoteBusy(14):xidFrameSent(15):error(16):other(17),The current condition of the conversation.
.1.3.6.1.2.1.10.16.3.1.5,RFC1381-MIB::lapbFlowBusyDefers,Counter32,read-only,,mandatory,,The number of times this device was unable to transmit a frame due to a perceived remote busy condition. Busy conditions can result from the receipt of an RNR from the remote device, the lack of valid sequence number space (window saturation), or other conditions.
.1.3.6.1.2.1.10.16.3.1.6,RFC1381-MIB::lapbFlowRejOutPkts,Counter32,read-only,,mandatory,,The number of REJ or SREJ frames sent by this station.
.1.3.6.1.2.1.10.16.3.1.7,RFC1381-MIB::lapbFlowRejInPkts,Counter32,read-only,,mandatory,,The number of REJ or SREJ frames received by this station.
.1.3.6.1.2.1.10.16.3.1.8,RFC1381-MIB::lapbFlowT1Timeouts,Counter32,read-only,,mandatory,,The number of times a re-transmission was effected by the T1 Timer expiring.
.1.3.6.1.2.1.10.16.3.1.9,RFC1381-MIB::lapbFlowFrmrSent,OCTET,read-only,,mandatory,,The Information Field of the FRMR most recently sent. If no FRMR has been sent (the normal case) or the information isn't available, this will be an OCTET STRING of zero length.
.1.3.6.1.2.1.10.16.3.1.10,RFC1381-MIB::lapbFlowFrmrReceived,OCTET,read-only,,mandatory,,The Information Field of the FRMR most recently received. If no FRMR has been received (the normal case) or the information isn't available, this will be an OCTET STRING of zero length.
.1.3.6.1.2.1.10.16.3.1.11,RFC1381-MIB::lapbFlowXidReceived,OCTET,read-only,,mandatory,,The Information Field of the XID frame most recently received. If no XID frame has been received, this will be an OCTET STRING of zero length.
.1.3.6.1.2.1.10.16.4,RFC1381-MIB::lapbXidTable,,not-accessible,,mandatory,,This table defines values to use for XID negotiation that are not found in the lapbAdmnTable. This table is optional for implementations that don't support XID and mandatory for implementations that do initiate XID negotiation.
.1.3.6.1.2.1.10.16.4.1,RFC1381-MIB::lapbXidEntry,,not-accessible,lapbXidIndex,mandatory,,XId negotiation parameter values for a specific LAPB.
.1.3.6.1.2.1.10.16.4.1.1,RFC1381-MIB::lapbXidIndex,INTEGER,read-only,,mandatory,,The ifIndex value for the LAPB interface.
.1.3.6.1.2.1.10.16.4.1.2,RFC1381-MIB::lapbXidAdRIdentifier,OCTET,read-write,,mandatory,,The value of the Address Resolution Identifier. A zero length string indicates no Identifier value has been assigned.
.1.3.6.1.2.1.10.16.4.1.3,RFC1381-MIB::lapbXidAdRAddress,OCTET,read-write,,mandatory,,The value of the Address Resolution Address. A zero length string indicates no Address value has been assigned.
.1.3.6.1.2.1.10.16.4.1.4,RFC1381-MIB::lapbXidParameterUniqueIdentifier,OCTET,read-write,,mandatory,,The value of the parameter unique Identifier. A zero length string indicates no Unique identifier value has been assigned.
.1.3.6.1.2.1.10.16.4.1.5,RFC1381-MIB::lapbXidGroupAddress,OCTET,read-write,,mandatory,,The value of the parameter Group address. A zero length string indicates no Group address value has been assigned.
.1.3.6.1.2.1.10.16.4.1.6,RFC1381-MIB::lapbXidPortNumber,OCTET,read-write,,mandatory,,The port number assigned for this link. A zero length string indicates no local port number identifier has been assigned.
.1.3.6.1.2.1.10.16.4.1.7,RFC1381-MIB::lapbXidUserDataSubfield,OCTET,read-write,,mandatory,,A user data subfield, if any, to be transmitted in an XID frame. A zero length frame indicates no user data subfield has been assigned. The octet string should include both the User data identifier and User data field as shown in Figures 1 and 4.
.1.3.6.1.2.1.10.16.5,RFC1381-MIB::lapbProtocolVersion,,,,,,
.1.3.6.1.2.1.10.16.5.1,RFC1381-MIB::lapbProtocolIso7776v1986,,,,,,
.1.3.6.1.2.1.10.16.5.2,RFC1381-MIB::lapbProtocolCcittV1980,,,,,,
.1.3.6.1.2.1.10.16.5.3,RFC1381-MIB::lapbProtocolCcittV1984,,,,,,
.1.3.6.1.2.1.10.18,DS1-MIB::ds1,,,,,,The MIB module to describe DS1, J1, E1, DS2, and E2 interfaces objects. Copyright (c) The IETF Trust (2007). This version of this MIB module is part of RFC 4805; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.18.6,DS1-MIB::dsx1ConfigTable,,not-accessible,,current,,The DS1 Configuration table.
.1.3.6.1.2.1.10.18.6.1,DS1-MIB::dsx1ConfigEntry,,not-accessible,dsx1LineIndex,current,,An entry in the DS1 Configuration table.
.1.3.6.1.2.1.10.18.6.1.1,DS1-MIB::dsx1LineIndex,Integer32,read-only,,current,,This object should be made equal to ifIndex. The next paragraph describes its previous usage. Making the object equal to ifIndex allows proper use of the ifStackTable and ds0/ds0bundle MIBs. Previously, this object was the identifier of a DS1 interface on a managed device. If there is an ifEntry that is directly associated with this and only this DS1 interface, it should have the same value as ifIndex. Otherwise, number the dsx1LineIndices with a unique identifier following the rules of choosing a number that is greater than ifNumber and numbering the inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g., network side) with odd numbers.
.1.3.6.1.2.1.10.18.6.1.2,DS1-MIB::dsx1IfIndex,Integer32,read-only,,deprecated,,This value for this object is equal to the value of ifIndex from the Interfaces table (RFC 2863).
.1.3.6.1.2.1.10.18.6.1.3,DS1-MIB::dsx1TimeElapsed,INTEGER,read-only,,current,,The number of seconds that have elapsed since the beginning of the near-end current error- measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.10.18.6.1.4,DS1-MIB::dsx1ValidIntervals,INTEGER,read-only,,current,,The number of previous near-end intervals for which data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15-minute near-end intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.18.6.1.5,DS1-MIB::dsx1LineType,INTEGER,read-write,,current,other(1):dsx1ESF(2):dsx1D4(3):dsx1E1(4):dsx1E1CRC(5):dsx1E1MF(6):dsx1E1CRCMF(7):dsx1Unframed(8):dsx1E1Unframed(9):dsx1DS2M12(10):dsx1E2(11):dsx1E1Q50(12):dsx1E1Q50CRC(13):dsx1J1ESF(14):dsx1J1Unframed(16),This variable indicates the variety of DS1 Line implementing this circuit. The type of circuit affects the number of bits per second that the circuit can reasonably carry, as well as the interpretation of the usage and error statistics. The values, in sequence, describe: TITLE: SPECIFICATION: dsx1ESF Extended SuperFrame DS1 (T1.107) dsx1D4 AT&T D4 format DS1 (T1.107) dsx1E1 ITU-T G.704, (Table 5A) dsx1E1-CRC ITU-T G.704, (Table 5B) dsxE1-MF G.704 (Table 5A) with TS16 multiframing enabled dsx1E1-CRC-MF G.704 (Table 5B) with TS16 multiframing enabled dsx1Unframed DS1 with No Framing dsx1E1Unframed E1 with No Framing (G.703) dsx1DS2M12 DS2 frame format (T1.107) dsx1E2 E2 frame format (G.704) dsx1E1Q50 TS16 bits 5,7,8 set to 101, [in all other cases it is set to 111.] (G.704, table 14) dsx1E1Q50CRC E1Q50 with CRC dsx1J1ESF J1 according to (JT-G704, JT-G706, and JT-I431) dsx1J1Unframed J1 with No Framing For clarification, the capacity for each E1 type is as listed below: dsx1E1Unframed - E1, no framing = 32 x 64k = 2048k dsx1E1 or dsx1E1CRC - E1, with framing, no signalling = 31 x 64k = 1984k dsx1E1MF or dsx1E1CRCMF - E1, with framing, signalling = 30 x 64k = 1920k
.1.3.6.1.2.1.10.18.6.1.6,DS1-MIB::dsx1LineCoding,INTEGER,read-write,,current,dsx1JBZS(1):dsx1B8ZS(2):dsx1HDB3(3):dsx1ZBTSI(4):dsx1AMI(5):other(6):dsx1B6ZS(7),This variable describes the variety of Zero Code Suppression used on this interface, which in turn affects a number of its characteristics. dsx1JBZS refers the Jammed Bit Zero Suppression, in which the AT&T specification of at least one pulse every 8-bit period is literally implemented by forcing a pulse in bit 8 of each channel. Thus, only 7 bits per channel, or 1.344 Mbps, are available for data. dsx1B8ZS refers to the use of a specified pattern of normal bits and bipolar violations that are used to replace a sequence of 8 zero bits. ANSI Clear Channels may use dsx1ZBTSI, or Zero Byte Time Slot Interchange. E1 links, with or without CRC, use dsx1HDB3 or dsx1AMI. dsx1AMI refers to a mode wherein no Zero Code Suppression is present and the line encoding does not solve the problem directly. In this application, the higher layer must provide data that meets or exceeds the pulse density requirements, such as inverting HDLC data. dsx1B6ZS refers to the user of a specified pattern of normal bits and bipolar violations that are used to replace a sequence of 6 zero bits. Used for DS2. For more information about line coding see [ANSI-T1.102]
.1.3.6.1.2.1.10.18.6.1.7,DS1-MIB::dsx1SendCode,INTEGER,read-write,,current,dsx1SendNoCode(1):dsx1SendLineCode(2):dsx1SendPayloadCode(3):dsx1SendResetCode(4):dsx1SendQRS(5):dsx1Send511Pattern(6):dsx1Send3in24Pattern(7):dsx1SendOtherTestPattern(8),This variable indicates what type of code is being sent across the DS1 interface by the device. Setting this variable causes the interface to send the code requested. The values mean the following: dsx1SendNoCode sending looped or normal data dsx1SendLineCode sending a request for a line loopback dsx1SendPayloadCode sending a request for a payload loopback dsx1SendResetCode sending a loopback termination request dsx1SendQRS sending a Quasi-Random Signal (QRS) test pattern dsx1Send511Pattern sending a 511-bit fixed test pattern dsx1Send3in24Pattern sending a fixed test pattern of 3 bits set in 24 dsx1SendOtherTestPattern sending a test pattern other than those described by this object
.1.3.6.1.2.1.10.18.6.1.8,DS1-MIB::dsx1CircuitIdentifier,OCTET,read-write,,current,,This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting.
.1.3.6.1.2.1.10.18.6.1.9,DS1-MIB::dsx1LoopbackConfig,INTEGER,read-write,,current,dsx1NoLoop(1):dsx1PayloadLoop(2):dsx1LineLoop(3):dsx1OtherLoop(4):dsx1InwardLoop(5):dsx1DualLoop(6),This variable represents the desired loopback configuration of the DS1 interface. Agents supporting read/write access should return inconsistentValue in response to a requested loopback state that the interface does not support. The values mean: dsx1NoLoop not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as its value. dsx1PayloadLoop the received signal at this interface is looped through the device. Typically, the received signal is looped back for retransmission after it has passed through the device's framing function. dsx1LineLoop the received signal at this interface does not go through the device (minimum penetration) but is looped back out. dsx1OtherLoop loopbacks that are not defined here. dsx1InwardLoop the transmitted signal at this interface is looped back and received by the same interface. What is transmitted onto the line is product dependent. dsx1DualLoop both dsx1LineLoop and dsx1InwardLoop will be active simultaneously.
.1.3.6.1.2.1.10.18.6.1.10,DS1-MIB::dsx1LineStatus,INTEGER,read-only,,current,,This variable indicates the line status of the interface. It contains loopback, failure, received alarm and transmitted alarms information. The dsx1LineStatus is a bitmap represented as a sum; therefore, it can represent multiple failures (alarms) and a LoopbackState simultaneously. dsx1NoAlarm must be set if and only if no other flag is set. If the dsx1loopbackState bit is set, the loopback in effect can be determined from the dsx1loopbackConfig object. The various bit positions are as follows: 1 dsx1NoAlarm No alarm present 2 dsx1RcvFarEndLOF Far end LOF (a.k.a. Yellow Alarm) 4 dsx1XmtFarEndLOF Near end sending LOF indication 8 dsx1RcvAIS Far end sending AIS 16 dsx1XmtAIS Near end sending AIS 32 dsx1LossOfFrame Near end LOF (a.k.a. Red Alarm) 64 dsx1LossOfSignal Near end Loss of Signal 128 dsx1LoopbackState Near end is looped 256 dsx1T16AIS E1 TS16 AIS 512 dsx1RcvFarEndLOMF Far end sending TS16 LOMF here signal state service exceeded
.1.3.6.1.2.1.10.18.6.1.11,DS1-MIB::dsx1SignalMode,INTEGER,read-write,,current,none(1):robbedBit(2):bitOriented(3):messageOriented(4):other(5),'none' indicates that no bits are reserved for signaling on this channel. 'robbedBit' indicates that DS1 Robbed Bit Signaling is in use. 'bitOriented' indicates that E1 Channel Associated Signaling is in use. 'messageOriented' indicates that Common Channel Signaling is in use on either channel 16 of an E1 link or channel 24 of a DS1.
.1.3.6.1.2.1.10.18.6.1.12,DS1-MIB::dsx1TransmitClockSource,INTEGER,read-write,,current,loopTiming(1):localTiming(2):throughTiming(3):adaptive(4),The source of transmit clock. 'loopTiming' indicates that the recovered receive clock is used as the transmit clock. 'localTiming' indicates that a local clock source is used or when an external clock is attached to the box containing the interface. 'throughTiming' indicates that recovered receive clock from another interface is used as the transmit clock. 'adaptive' indicates that the clock is recovered based on the data flow and not based on the physical layer
.1.3.6.1.2.1.10.18.6.1.13,DS1-MIB::dsx1Fdl,INTEGER,read-write,,current,,This bitmap describes the use of the facilities data link and is the sum of the capabilities. Set any bits that are appropriate: other(1), dsx1AnsiT1403(2), dsx1Att54016(4), dsx1FdlNone(8) 'other' indicates that a protocol other than one of the following is used. 'dsx1AnsiT1403' refers to the FDL exchange recommended by ANSI. 'dsx1Att54016' refers to ESF FDL exchanges. 'dsx1FdlNone' indicates that the device does not use the FDL.
.1.3.6.1.2.1.10.18.6.1.14,DS1-MIB::dsx1InvalidIntervals,INTEGER,read-only,,current,,The number of intervals in the range from 0 to dsx1ValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals is not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.18.6.1.15,DS1-MIB::dsx1LineLength,INTEGER,read-write,,current,,The length of the DS1 line in meters. This object provides information for line build-out circuitry. This object is only useful if the interface has configurable line build-out circuitry.
.1.3.6.1.2.1.10.18.6.1.16,DS1-MIB::dsx1LineStatusLastChange,TimeTicks,read-only,,current,,The value of MIB II's sysUpTime object at the time this DS1 entered its current line status state. If the current state was entered prior to the last re-initialization of the proxy-agent, then this object contains a zero value.
.1.3.6.1.2.1.10.18.6.1.17,DS1-MIB::dsx1LineStatusChangeTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether dsx1LineStatusChange traps should be generated for this interface.
.1.3.6.1.2.1.10.18.6.1.18,DS1-MIB::dsx1LoopbackStatus,INTEGER,read-only,,current,,This variable represents the current state of the loopback on the DS1 interface. It contains information about loopbacks established by a manager and remotely from the far end. The dsx1LoopbackStatus is a bitmap represented as a sum; therefore, it can represent multiple loopbacks simultaneously. The various bit positions are as follows: 1 dsx1NoLoopback 2 dsx1NearEndPayloadLoopback 4 dsx1NearEndLineLoopback 8 dsx1NearEndOtherLoopback 16 dsx1NearEndInwardLoopback 32 dsx1FarEndPayloadLoopback 64 dsx1FarEndLineLoopback
.1.3.6.1.2.1.10.18.6.1.19,DS1-MIB::dsx1Ds1ChannelNumber,INTEGER,read-only,,current,,This variable represents the channel number of the DS1/E1 on its parent DS2/E2 or DS3/E3. A value of 0 indicates that this DS1/E1 does not have a parent DS3/E3.
.1.3.6.1.2.1.10.18.6.1.20,DS1-MIB::dsx1Channelization,INTEGER,read-write,,current,disabled(1):enabledDs0(2):enabledDs1(3),Indicates whether this DS1/E1 or DS2 is channelized or unchannelized. The value of enabledDs0(2) indicates that this is a DS1 channelized into DS0s. Setting this value will cause the creation, and resetting it to disabled(1) will cause the deletion of entries in the ifTable for the DS0s that are within the DS1. The value of enabledDs1(3) indicates that this is a DS2 channelized into DS1s. Setting this value will cause the creation, and resetting it to disabled(1) will cause the deletion of entries in the ifTable for the DS1s that are within the DS2.
.1.3.6.1.2.1.10.18.6.1.21,DS1-MIB::dsx1LineMode,INTEGER,read-write,,current,csu(1):dsu(2),This setting puts the T1 framer into either long-haul (CSU) mode or short-haul (DSU) mode.
.1.3.6.1.2.1.10.18.6.1.22,DS1-MIB::dsx1LineBuildOut,INTEGER,read-write,,current,notApplicable(1):neg75dB(2):neg15dB(3):neg225dB(4):zerodB(5),Attenuation setting for T1 framer in long haul (CSU) mode. The optional values are -7.5dB, -15dB, -22.5dB, and 0dB.
.1.3.6.1.2.1.10.18.6.1.23,DS1-MIB::dsx1LineImpedance,INTEGER,read-write,,current,notApplicable(1):unbalanced75ohms(2):balanced100ohms(3):balanced120ohms(4),Nominal line impedance. For T1 and J1 lines, the value is typically balanced100ohms(3). For E1 lines, the value is typically unbalanced75ohms(2) and balanced120ohms(4). When this object does not apply, or when the appropriate value is not known, the value should be set to notApplicable(1).
.1.3.6.1.2.1.10.18.7,DS1-MIB::dsx1CurrentTable,,not-accessible,,current,,The DS1 Current table contains various statistics being collected for the current 15-minute interval.
.1.3.6.1.2.1.10.18.7.1,DS1-MIB::dsx1CurrentEntry,,not-accessible,dsx1CurrentIndex,current,,An entry in the DS1 Current table.
.1.3.6.1.2.1.10.18.7.1.1,DS1-MIB::dsx1CurrentIndex,Integer32,read-only,,current,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object instance.
.1.3.6.1.2.1.10.18.7.1.2,DS1-MIB::dsx1CurrentESs,Gauge32,read-only,,current,,The number of Errored Seconds.
.1.3.6.1.2.1.10.18.7.1.3,DS1-MIB::dsx1CurrentSESs,Gauge32,read-only,,current,,The number of Severely Errored Seconds.
.1.3.6.1.2.1.10.18.7.1.4,DS1-MIB::dsx1CurrentSEFSs,Gauge32,read-only,,current,,The number of Severely Errored Framing Seconds.
.1.3.6.1.2.1.10.18.7.1.5,DS1-MIB::dsx1CurrentUASs,Gauge32,read-only,,current,,The number of Unavailable Seconds.
.1.3.6.1.2.1.10.18.7.1.6,DS1-MIB::dsx1CurrentCSSs,Gauge32,read-only,,current,,The number of Controlled Slip Seconds.
.1.3.6.1.2.1.10.18.7.1.7,DS1-MIB::dsx1CurrentPCVs,Gauge32,read-only,,current,,The number of Path Coding Violations.
.1.3.6.1.2.1.10.18.7.1.8,DS1-MIB::dsx1CurrentLESs,Gauge32,read-only,,current,,The number of Line Errored Seconds.
.1.3.6.1.2.1.10.18.7.1.9,DS1-MIB::dsx1CurrentBESs,Gauge32,read-only,,current,,The number of Bursty Errored Seconds.
.1.3.6.1.2.1.10.18.7.1.10,DS1-MIB::dsx1CurrentDMs,Gauge32,read-only,,deprecated,,The number of Degraded Minutes.
.1.3.6.1.2.1.10.18.7.1.11,DS1-MIB::dsx1CurrentLCVs,Gauge32,read-only,,current,,The number of Line Coding Violations (LCVs).
.1.3.6.1.2.1.10.18.8,DS1-MIB::dsx1IntervalTable,,not-accessible,,current,,The DS1 Interval table contains various statistics collected by each DS1 interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15-minute intervals. Each row in this table represents one such interval (identified by dsx1IntervalNumber) for one specific instance (identified by dsx1IntervalIndex).
.1.3.6.1.2.1.10.18.8.1,DS1-MIB::dsx1IntervalEntry,,not-accessible,dsx1IntervalIndex:dsx1IntervalNumber,current,,An entry in the DS1 Interval table.
.1.3.6.1.2.1.10.18.8.1.1,DS1-MIB::dsx1IntervalIndex,Integer32,read-only,,current,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object instance.
.1.3.6.1.2.1.10.18.8.1.2,DS1-MIB::dsx1IntervalNumber,INTEGER,read-only,,current,,A number between 1 and 96, where 1 is the most recently completed 15-minute interval and 96 is the 15-minute interval completed 23 hours and 45 minutes prior to interval 1.
.1.3.6.1.2.1.10.18.8.1.3,DS1-MIB::dsx1IntervalESs,Gauge32,read-only,,current,,The number of Errored Seconds.
.1.3.6.1.2.1.10.18.8.1.4,DS1-MIB::dsx1IntervalSESs,Gauge32,read-only,,current,,The number of Severely Errored Seconds.
.1.3.6.1.2.1.10.18.8.1.5,DS1-MIB::dsx1IntervalSEFSs,Gauge32,read-only,,current,,The number of Severely Errored Framing Seconds.
.1.3.6.1.2.1.10.18.8.1.6,DS1-MIB::dsx1IntervalUASs,Gauge32,read-only,,current,,The number of Unavailable Seconds. This object may decrease if the occurrence of unavailable seconds occurs across an interval boundary.
.1.3.6.1.2.1.10.18.8.1.7,DS1-MIB::dsx1IntervalCSSs,Gauge32,read-only,,current,,The number of Controlled Slip Seconds.
.1.3.6.1.2.1.10.18.8.1.8,DS1-MIB::dsx1IntervalPCVs,Gauge32,read-only,,current,,The number of Path Coding Violations.
.1.3.6.1.2.1.10.18.8.1.9,DS1-MIB::dsx1IntervalLESs,Gauge32,read-only,,current,,The number of Line Errored Seconds.
.1.3.6.1.2.1.10.18.8.1.10,DS1-MIB::dsx1IntervalBESs,Gauge32,read-only,,current,,The number of Bursty Errored Seconds.
.1.3.6.1.2.1.10.18.8.1.11,DS1-MIB::dsx1IntervalDMs,Gauge32,read-only,,deprecated,,The number of Degraded Minutes.
.1.3.6.1.2.1.10.18.8.1.12,DS1-MIB::dsx1IntervalLCVs,Gauge32,read-only,,current,,The number of Line Coding Violations.
.1.3.6.1.2.1.10.18.8.1.13,DS1-MIB::dsx1IntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates whether the data for this interval is valid.
.1.3.6.1.2.1.10.18.9,DS1-MIB::dsx1TotalTable,,not-accessible,,current,,The DS1 Total table contains the cumulative sum of the various statistics for the 24-hour period preceding the current interval.
.1.3.6.1.2.1.10.18.9.1,DS1-MIB::dsx1TotalEntry,,not-accessible,dsx1TotalIndex,current,,An entry in the DS1 Total table.
.1.3.6.1.2.1.10.18.9.1.1,DS1-MIB::dsx1TotalIndex,Integer32,read-only,,current,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object instance.
.1.3.6.1.2.1.10.18.9.1.2,DS1-MIB::dsx1TotalESs,Gauge32,read-only,,current,,The number of Errored Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.3,DS1-MIB::dsx1TotalSESs,Gauge32,read-only,,current,,The number of Severely Errored Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.4,DS1-MIB::dsx1TotalSEFSs,Gauge32,read-only,,current,,The number of Severely Errored Framing Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.5,DS1-MIB::dsx1TotalUASs,Gauge32,read-only,,current,,The number of Unavailable Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.6,DS1-MIB::dsx1TotalCSSs,Gauge32,read-only,,current,,The number of Controlled Slip Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.7,DS1-MIB::dsx1TotalPCVs,Gauge32,read-only,,current,,The number of Path Coding Violations encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.8,DS1-MIB::dsx1TotalLESs,Gauge32,read-only,,current,,The number of Line Errored Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.9,DS1-MIB::dsx1TotalBESs,Gauge32,read-only,,current,,The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.10,DS1-MIB::dsx1TotalDMs,Gauge32,read-only,,deprecated,,The number of Degraded Minutes (DMs) encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.9.1.11,DS1-MIB::dsx1TotalLCVs,Gauge32,read-only,,current,,The number of Line Coding Violations (LCVs) encountered by a DS1 interface in the current 15-minute interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.10,DS1-MIB::dsx1FarEndCurrentTable,,not-accessible,,current,,The DS1 Far End Current table contains various statistics being collected for the current 15-minute interval. The statistics are collected from the far-end messages on the Facilities Data Link. The definitions are the same as described for the near-end information.
.1.3.6.1.2.1.10.18.10.1,DS1-MIB::dsx1FarEndCurrentEntry,,not-accessible,dsx1FarEndCurrentIndex,current,,An entry in the DS1 Far End Current table.
.1.3.6.1.2.1.10.18.10.1.1,DS1-MIB::dsx1FarEndCurrentIndex,Integer32,read-only,,current,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is identical to the interface identified by the same value of dsx1LineIndex.
.1.3.6.1.2.1.10.18.10.1.2,DS1-MIB::dsx1FarEndTimeElapsed,INTEGER,read-only,,current,,The number of seconds that have elapsed since the beginning of the far-end current error-measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.10.18.10.1.3,DS1-MIB::dsx1FarEndValidIntervals,INTEGER,read-only,,current,,The number of previous far-end intervals for which data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15-minute far-end intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.18.10.1.4,DS1-MIB::dsx1FarEndCurrentESs,Gauge32,read-only,,current,,The number of Far End Errored Seconds.
.1.3.6.1.2.1.10.18.10.1.5,DS1-MIB::dsx1FarEndCurrentSESs,Gauge32,read-only,,current,,The number of Far End Severely Errored Seconds.
.1.3.6.1.2.1.10.18.10.1.6,DS1-MIB::dsx1FarEndCurrentSEFSs,Gauge32,read-only,,current,,The number of Far End Severely Errored Framing Seconds.
.1.3.6.1.2.1.10.18.10.1.7,DS1-MIB::dsx1FarEndCurrentUASs,Gauge32,read-only,,current,,The number of Unavailable Seconds.
.1.3.6.1.2.1.10.18.10.1.8,DS1-MIB::dsx1FarEndCurrentCSSs,Gauge32,read-only,,current,,The number of Far End Controlled Slip Seconds.
.1.3.6.1.2.1.10.18.10.1.9,DS1-MIB::dsx1FarEndCurrentLESs,Gauge32,read-only,,current,,The number of Far End Line Errored Seconds.
.1.3.6.1.2.1.10.18.10.1.10,DS1-MIB::dsx1FarEndCurrentPCVs,Gauge32,read-only,,current,,The number of Far End Path Coding Violations.
.1.3.6.1.2.1.10.18.10.1.11,DS1-MIB::dsx1FarEndCurrentBESs,Gauge32,read-only,,current,,The number of Far End Bursty Errored Seconds.
.1.3.6.1.2.1.10.18.10.1.12,DS1-MIB::dsx1FarEndCurrentDMs,Gauge32,read-only,,deprecated,,The number of Far End Degraded Minutes.
.1.3.6.1.2.1.10.18.10.1.13,DS1-MIB::dsx1FarEndInvalidIntervals,INTEGER,read-only,,current,,The number of intervals in the range from 0 to dsx1FarEndValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals is not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.18.11,DS1-MIB::dsx1FarEndIntervalTable,,not-accessible,,current,,The DS1 Far End Interval table contains various statistics collected by each DS1 interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15-minute intervals. Each row in this table represents one such interval (identified by dsx1FarEndIntervalNumber) for one specific instance (identified by dsx1FarEndIntervalIndex).
.1.3.6.1.2.1.10.18.11.1,DS1-MIB::dsx1FarEndIntervalEntry,,not-accessible,dsx1FarEndIntervalIndex:dsx1FarEndIntervalNumber,current,,An entry in the DS1 Far End Interval table.
.1.3.6.1.2.1.10.18.11.1.1,DS1-MIB::dsx1FarEndIntervalIndex,Integer32,read-only,,current,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is identical to the interface identified by the same value of dsx1LineIndex.
.1.3.6.1.2.1.10.18.11.1.2,DS1-MIB::dsx1FarEndIntervalNumber,INTEGER,read-only,,current,,A number between 1 and 96, where 1 is the most recently completed 15-minute interval and 96 is the 15 minutes interval completed 23 hours and 45 minutes prior to interval 1.
.1.3.6.1.2.1.10.18.11.1.3,DS1-MIB::dsx1FarEndIntervalESs,Gauge32,read-only,,current,,The number of Far End Errored Seconds.
.1.3.6.1.2.1.10.18.11.1.4,DS1-MIB::dsx1FarEndIntervalSESs,Gauge32,read-only,,current,,The number of Far End Severely Errored Seconds.
.1.3.6.1.2.1.10.18.11.1.5,DS1-MIB::dsx1FarEndIntervalSEFSs,Gauge32,read-only,,current,,The number of Far End Severely Errored Framing Seconds.
.1.3.6.1.2.1.10.18.11.1.6,DS1-MIB::dsx1FarEndIntervalUASs,Gauge32,read-only,,current,,The number of Unavailable Seconds.
.1.3.6.1.2.1.10.18.11.1.7,DS1-MIB::dsx1FarEndIntervalCSSs,Gauge32,read-only,,current,,The number of Far End Controlled Slip Seconds.
.1.3.6.1.2.1.10.18.11.1.8,DS1-MIB::dsx1FarEndIntervalLESs,Gauge32,read-only,,current,,The number of Far End Line Errored Seconds.
.1.3.6.1.2.1.10.18.11.1.9,DS1-MIB::dsx1FarEndIntervalPCVs,Gauge32,read-only,,current,,The number of Far End Path Coding Violations.
.1.3.6.1.2.1.10.18.11.1.10,DS1-MIB::dsx1FarEndIntervalBESs,Gauge32,read-only,,current,,The number of Far End Bursty Errored Seconds.
.1.3.6.1.2.1.10.18.11.1.11,DS1-MIB::dsx1FarEndIntervalDMs,Gauge32,read-only,,deprecated,,The number of Far End Degraded Minutes.
.1.3.6.1.2.1.10.18.11.1.12,DS1-MIB::dsx1FarEndIntervalValidData,INTEGER,read-only,,current,true(1):false(2), This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.18.12,DS1-MIB::dsx1FarEndTotalTable,,not-accessible,,current,,The DS1 Far End Total table contains the cumulative sum of the various statistics for the 24-hour period preceding the current interval.
.1.3.6.1.2.1.10.18.12.1,DS1-MIB::dsx1FarEndTotalEntry,,not-accessible,dsx1FarEndTotalIndex,current,,An entry in the DS1 Far End Total table.
.1.3.6.1.2.1.10.18.12.1.1,DS1-MIB::dsx1FarEndTotalIndex,Integer32,read-only,,current,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is identical to the interface identified by the same value of dsx1LineIndex.
.1.3.6.1.2.1.10.18.12.1.2,DS1-MIB::dsx1FarEndTotalESs,Gauge32,read-only,,current,,The number of Far End Errored Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.3,DS1-MIB::dsx1FarEndTotalSESs,Gauge32,read-only,,current,,The number of Far End Severely Errored Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.4,DS1-MIB::dsx1FarEndTotalSEFSs,Gauge32,read-only,,current,,The number of Far End Severely Errored Framing Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.5,DS1-MIB::dsx1FarEndTotalUASs,Gauge32,read-only,,current,,The number of Unavailable Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.6,DS1-MIB::dsx1FarEndTotalCSSs,Gauge32,read-only,,current,,The number of Far End Controlled Slip Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.7,DS1-MIB::dsx1FarEndTotalLESs,Gauge32,read-only,,current,,The number of Far End Line Errored Seconds encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.8,DS1-MIB::dsx1FarEndTotalPCVs,Gauge32,read-only,,current,,The number of Far End Path Coding Violations reported via the far end block error count encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.9,DS1-MIB::dsx1FarEndTotalBESs,Gauge32,read-only,,current,,The number of Bursty Errored Seconds (BESs) encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.12.1.10,DS1-MIB::dsx1FarEndTotalDMs,Gauge32,read-only,,deprecated,,The number of Degraded Minutes (DMs) encountered by a DS1 interface in the previous 24-hour interval. Invalid 15-minute intervals count as 0.
.1.3.6.1.2.1.10.18.13,DS1-MIB::dsx1FracTable,,not-accessible,,deprecated,,This table is deprecated in favor of using ifStackTable. The table was mandatory for systems dividing a DS1 into channels containing different data streams that are of local interest. Systems that are indifferent to data content, such as CSUs, need not implement it. The DS1 Fractional table identifies which DS1 channels associated with a CSU are being used to support a logical interface, i.e., an entry in the interfaces table from the Internet-standard MIB. For example, consider an application managing a North American ISDN Primary Rate link whose division is a 384-kbit/s H1 _B_ Channel for video, a second H1 for data to a primary routing peer, and 12 64-kbit/s H0 _B_ Channels. Consider that some subset of the H0 channels is used for voice and the remainder are available for dynamic data calls. We count a total of 14 interfaces multiplexed onto the DS1 interface. Six DS1 channels (for the sake of the example, channels 1..6) are used for video, six more (7..11 and 13) are used for data, and the remaining 12 are in channels 12 and 14..24. Let us further imagine that ifIndex 2 is of type DS1 and refers to the DS1 interface and that the interfaces layered onto it are numbered 3..16. We might describe the allocation of channels, in the dsx1FracTable, as follows: dsx1FracIfIndex.2. 1 = 3 dsx1FracIfIndex.2.13 = 4 dsx1FracIfIndex.2. 2 = 3 dsx1FracIfIndex.2.14 = 6 dsx1FracIfIndex.2. 3 = 3 dsx1FracIfIndex.2.15 = 7 dsx1FracIfIndex.2. 4 = 3 dsx1FracIfIndex.2.16 = 8 dsx1FracIfIndex.2. 5 = 3 dsx1FracIfIndex.2.17 = 9 dsx1FracIfIndex.2. 6 = 3 dsx1FracIfIndex.2.18 = 10 dsx1FracIfIndex.2. 7 = 4 dsx1FracIfIndex.2.19 = 11 dsx1FracIfIndex.2. 8 = 4 dsx1FracIfIndex.2.20 = 12 dsx1FracIfIndex.2. 9 = 4 dsx1FracIfIndex.2.21 = 13 dsx1FracIfIndex.2.10 = 4 dsx1FracIfIndex.2.22 = 14 dsx1FracIfIndex.2.11 = 4 dsx1FracIfIndex.2.23 = 15 dsx1FracIfIndex.2.12 = 5 dsx1FracIfIndex.2.24 = 16 For North American (DS1) interfaces, there are 24 legal channels, numbered 1 through 24. For G.704 interfaces, there are 31 legal channels, numbered 1 through 31. The channels (1..31) correspond directly to the equivalently numbered time-slots.
.1.3.6.1.2.1.10.18.13.1,DS1-MIB::dsx1FracEntry,,not-accessible,dsx1FracIndex:dsx1FracNumber,deprecated,,An entry in the DS1 Fractional table.
.1.3.6.1.2.1.10.18.13.1.1,DS1-MIB::dsx1FracIndex,INTEGER,read-only,,deprecated,,The index value that uniquely identifies the DS1 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value as a dsx1LineIndex object instance.
.1.3.6.1.2.1.10.18.13.1.2,DS1-MIB::dsx1FracNumber,INTEGER,read-only,,deprecated,,The channel number for this entry.
.1.3.6.1.2.1.10.18.13.1.3,DS1-MIB::dsx1FracIfIndex,INTEGER,read-write,,deprecated,,An index value that uniquely identifies an interface. The interface identified by a particular value of this index is the same interface as identified by the same value as an ifIndex object instance. If no interface is currently using a channel, the value should be zero. If a single interface occupies more than one time-slot, that ifIndex value will be found in multiple time-slots.
.1.3.6.1.2.1.10.18.14,DS1-MIB::ds1Conformance,,,,,,
.1.3.6.1.2.1.10.18.14.1,DS1-MIB::ds1Groups,,,,,,
.1.3.6.1.2.1.10.18.14.1.1,DS1-MIB::ds1NearEndConfigGroup,,,,,,A collection of objects providing configuration information applicable to all DS1 interfaces.
.1.3.6.1.2.1.10.18.14.1.2,DS1-MIB::ds1NearEndStatisticsGroup,,,,,,A collection of objects providing statistics information applicable to all DS1 interfaces.
.1.3.6.1.2.1.10.18.14.1.3,DS1-MIB::ds1FarEndGroup,,,,,,A collection of objects providing remote configuration and statistics information.
.1.3.6.1.2.1.10.18.14.1.4,DS1-MIB::ds1DeprecatedGroup,,,,,,A collection of obsolete objects that may be implemented for backwards compatibility.
.1.3.6.1.2.1.10.18.14.1.5,DS1-MIB::ds1NearEndOptionalConfigGroup,,,,,,A collection of objects that may be implemented on DS1 and DS2 interfaces.
.1.3.6.1.2.1.10.18.14.1.6,DS1-MIB::ds1DS2Group,,,,,,A collection of objects providing information about DS2 (6,312 kbps) and E2 (8,448 kbps) systems.
.1.3.6.1.2.1.10.18.14.1.7,DS1-MIB::ds1TransStatsGroup,,,,,,A collection of objects that are the statistics that can be collected from a DS1 interface that is running transparent or unframed lineType. Statistics not in this list should return noSuchInstance.
.1.3.6.1.2.1.10.18.14.1.8,DS1-MIB::ds1NearEndOptionalTrapGroup,,,,,,A collection of notifications that may be implemented on DS1 and DS2 interfaces.
.1.3.6.1.2.1.10.18.14.1.9,DS1-MIB::ds1ChanMappingGroup,,,,,,A collection of objects that give a mapping of DS3 Channel (dsx1Ds1ChannelNumber) to ifIndex.
.1.3.6.1.2.1.10.18.14.1.10,DS1-MIB::ds1NearEndConfigurationGroup,,,,,,A collection of objects providing configuration information applicable to all DS1 interfaces.
.1.3.6.1.2.1.10.18.14.1.11,DS1-MIB::ds1NearEndCfgGroup,,,,,,A collection of objects providing configuration information applicable to all DS1 interfaces.
.1.3.6.1.2.1.10.18.14.1.12,DS1-MIB::ds1NearEndStatGroup,,,,,,A collection of objects providing statistics information applicable to all DS1 interfaces.
.1.3.6.1.2.1.10.18.14.1.13,DS1-MIB::ds1FarEndNGroup,,,,,,A collection of objects providing remote configuration and statistics information.
.1.3.6.1.2.1.10.18.14.2,DS1-MIB::ds1Compliances,,,,,,
.1.3.6.1.2.1.10.18.14.2.1,DS1-MIB::ds1Compliance,,,,,,The compliance statement for T1 and E1 interfaces.
.1.3.6.1.2.1.10.18.14.2.2,DS1-MIB::ds1MibT1PriCompliance,,,,,,Compliance statement for using this MIB for ISDN Primary Rate interfaces on T1 lines.
.1.3.6.1.2.1.10.18.14.2.3,DS1-MIB::ds1MibE1PriCompliance,,,,,,Compliance statement for using this MIB for ISDN Primary Rate interfaces on E1 lines.
.1.3.6.1.2.1.10.18.14.2.4,DS1-MIB::ds1Ds2Compliance,,,,,,Compliance statement for using this MIB for DS2 interfaces.
.1.3.6.1.2.1.10.18.14.2.5,DS1-MIB::ds1NCompliance,,,,,,The compliance statement for T1 and E1 interfaces.
.1.3.6.1.2.1.10.18.14.2.6,DS1-MIB::ds1MibT1PriNCompliance,,,,,,Compliance statement for using this MIB for ISDN Primary Rate interfaces on T1 lines.
.1.3.6.1.2.1.10.18.14.2.7,DS1-MIB::ds1MibE1PriNCompliance,,,,,,Compliance statement for using this MIB for ISDN Primary Rate interfaces on E1 lines.
.1.3.6.1.2.1.10.18.14.2.8,DS1-MIB::ds1J1Compliance,,,,,,The compliance statement for T1, J1, and E1 interfaces.
.1.3.6.1.2.1.10.18.14.2.9,DS1-MIB::ds1NMibT1PriNCompliance,,,,,,Compliance statement for using this MIB for ISDN Primary Rate interfaces on T1 lines.
.1.3.6.1.2.1.10.18.14.2.10,DS1-MIB::ds1NMibE1PriNCompliance,,,,,,Compliance statement for using this MIB for ISDN Primary Rate interfaces on E1 lines.
.1.3.6.1.2.1.10.18.15,DS1-MIB::ds1Traps,,,,,,
.1.3.6.1.2.1.10.18.15.0,DS1-MIB::anonymous#0,,,,,,
.1.3.6.1.2.1.10.18.15.0.1,DS1-MIB::dsx1LineStatusChange,,,,,,A dsx1LineStatusChange trap is sent when the value of an instance dsx1LineStatus changes. It can be utilized by an Network Management Station (NMS) to trigger polls. When the line status change results from a higher-level line status change (i.e., DS3), then no traps for the DS1 are sent.
.1.3.6.1.2.1.10.18.16,DS1-MIB::dsx1ChanMappingTable,,not-accessible,,current,,The DS1 Channel Mapping table. This table maps a DS1 channel number on a particular DS3 into an ifIndex. In the presence of DS2s, this table can be used to map a DS2 channel number on a DS3 into an ifIndex, or used to map a DS1 channel number on a DS2 into an ifIndex.
.1.3.6.1.2.1.10.18.16.1,DS1-MIB::dsx1ChanMappingEntry,,not-accessible,ifIndex:dsx1Ds1ChannelNumber,current,,An entry in the DS1 Channel Mapping table. There is an entry in this table corresponding to each DS1 ifEntry within any interface that is channelized to the individual DS1 ifEntry level. This table is intended to facilitate mapping from channelized interface / channel number to DS1 ifEntry (e.g., mapping (DS3 ifIndex, DS1 channel number) -> ifIndex). While this table provides information that can also be found in the ifStackTable and dsx1ConfigTable, it provides this same information with a single table lookup, rather than by walking the ifStackTable to find the various constituent DS1 ifTable entries, and testing various dsx1ConfigTable entries to check for the entry with the applicable DS1 channel number.
.1.3.6.1.2.1.10.18.16.1.1,DS1-MIB::dsx1ChanMappedIfIndex,Integer32,read-only,,current,,This object indicates the ifIndex value assigned by the agent for the individual DS1 ifEntry that corresponds to the given DS1 channel number (specified by the INDEX element dsx1Ds1ChannelNumber) of the given channelized interface (specified by INDEX element ifIndex).
.1.3.6.1.2.1.10.20,ISDN-MIB::isdnMib,,,,,,The MIB module to describe the management of ISDN interfaces.
.1.3.6.1.2.1.10.20.1,ISDN-MIB::isdnMibObjects,,,,,,
.1.3.6.1.2.1.10.20.1.1,ISDN-MIB::isdnBasicRateGroup,,,,,,
.1.3.6.1.2.1.10.20.1.1.1,ISDN-MIB::isdnBasicRateTable,,not-accessible,,current,,Table containing configuration and operational parameters for all physical Basic Rate interfaces on this managed device.
.1.3.6.1.2.1.10.20.1.1.1.1,ISDN-MIB::isdnBasicRateEntry,,not-accessible,ifIndex,current,,An entry in the ISDN Basic Rate Table.
.1.3.6.1.2.1.10.20.1.1.1.1.1,ISDN-MIB::isdnBasicRateIfType,INTEGER,read-write,,current,isdns(75):isdnu(76),The physical interface type. For 'S/T' interfaces, also called 'Four-wire Basic Access Interface', the value of this object is isdns(75). For 'U' interfaces, also called 'Two-wire Basic Access Interface', the value of this object is isdnu(76).
.1.3.6.1.2.1.10.20.1.1.1.1.2,ISDN-MIB::isdnBasicRateLineTopology,INTEGER,read-write,,current,pointToPoint(1):pointToMultipoint(2),The line topology to be used for this interface. Note that setting isdnBasicRateIfType to isdns(75) does not necessarily mean a line topology of point-to-multipoint.
.1.3.6.1.2.1.10.20.1.1.1.1.3,ISDN-MIB::isdnBasicRateIfMode,INTEGER,read-write,,current,te(1):nt(2),The physical interface mode. For TE mode, the value of this object is te(1). For NT mode, the value of this object is nt(2).
.1.3.6.1.2.1.10.20.1.1.1.1.4,ISDN-MIB::isdnBasicRateSignalMode,INTEGER,read-write,,current,active(1):inactive(2),The signaling channel operational mode for this interface. If active(1) there is a signaling channel on this interface. If inactive(2) a signaling channel is not available.
.1.3.6.1.2.1.10.20.1.2,ISDN-MIB::isdnBearerGroup,,,,,,
.1.3.6.1.2.1.10.20.1.2.1,ISDN-MIB::isdnBearerTable,,not-accessible,,current,,This table defines port specific operational, statistics and active call data for ISDN B channels. Each entry in this table describes one B (bearer) channel.
.1.3.6.1.2.1.10.20.1.2.1.1,ISDN-MIB::isdnBearerEntry,,not-accessible,ifIndex,current,,Operational and statistics information relating to one port. A port is a single B channel.
.1.3.6.1.2.1.10.20.1.2.1.1.1,ISDN-MIB::isdnBearerChannelType,INTEGER,read-write,,current,dialup(1):leased(2),The B channel type. If the B channel is connected to a dialup line, this object has a value of dialup(1). In this case, it is controlled by an associated signaling channel. If the B channel is connected to a leased line, this object has a value of leased(2). For leased line B channels, there is no signaling channel control available.
.1.3.6.1.2.1.10.20.1.2.1.1.2,ISDN-MIB::isdnBearerOperStatus,INTEGER,read-only,,current,idle(1):connecting(2):connected(3):active(4),The current call control state for this port. idle(1): The B channel is idle. No call or call attempt is going on. connecting(2): A connection attempt (outgoing call) is being made on this interface. connected(3): An incoming call is in the process of validation. active(4): A call is active on this interface.
.1.3.6.1.2.1.10.20.1.2.1.1.3,ISDN-MIB::isdnBearerChannelNumber,INTEGER,read-only,,current,,The identifier being used by a signaling protocol to identify this B channel, also referred to as B channel number. If the Agent also supports the DS0 MIB, the values of isdnBearerChannelNumber and dsx0Ds0Number must be identical for a given B channel.
.1.3.6.1.2.1.10.20.1.2.1.1.4,ISDN-MIB::isdnBearerPeerAddress,OCTET,read-only,,current,,The ISDN address the current or last call is or was connected to. In some cases, the format of this information can not be predicted, since it largely depends on the type of switch or PBX the device is connected to. Therefore, the detailed format of this information is not specified and is implementation dependent. If possible, the agent should supply this information using the E.164 format. In this case, the number must start with '+'. Otherwise, IA5 number digits must be used. If the peer ISDN address is not available, this object has a length of zero.
.1.3.6.1.2.1.10.20.1.2.1.1.5,ISDN-MIB::isdnBearerPeerSubAddress,OCTET,read-only,,current,,The ISDN subaddress the current or last call is or was connected to. The subaddress is an user supplied string of up to 20 IA5 characters and is transmitted transparently through the network. If the peer subaddress is not available, this object has a length of zero.
.1.3.6.1.2.1.10.20.1.2.1.1.6,ISDN-MIB::isdnBearerCallOrigin,INTEGER,read-only,,current,unknown(1):originate(2):answer(3):callback(4),The call origin for the current or last call. If since system startup there was no call on this interface, this object has a value of unknown(1).
.1.3.6.1.2.1.10.20.1.2.1.1.7,ISDN-MIB::isdnBearerInfoType,INTEGER,read-only,,current,unknown(1):speech(2):unrestrictedDigital(3):unrestrictedDigital56(4):restrictedDigital(5):audio31(6):audio7(7):video(8):packetSwitched(9),The Information Transfer Capability for the current or last call. speech(2) refers to a non-data connection, whereas audio31(6) and audio7(7) refer to data mode connections. Note that Q.931, chapter 4.5.5, originally defined audio7(7) as '7 kHz audio' and now defines it as 'Unrestricted digital information with tones/ announcements'. If since system startup there has been no call on this interface, this object has a value of unknown(1).
.1.3.6.1.2.1.10.20.1.2.1.1.8,ISDN-MIB::isdnBearerMultirate,INTEGER,read-only,,current,true(1):false(2),This flag indicates if the current or last call used multirate. The actual information transfer rate, in detail specified in octet 4.1 (rate multiplier), is the sum of all B channel ifSpeed values for the hyperchannel. If since system startup there was no call on this interface, this object has a value of false(2).
.1.3.6.1.2.1.10.20.1.2.1.1.9,ISDN-MIB::isdnBearerCallSetupTime,TimeTicks,read-only,,current,,The value of sysUpTime when the ISDN setup message for the current or last call was sent or received. If since system startup there has been no call on this interface, this object has a value of zero.
.1.3.6.1.2.1.10.20.1.2.1.1.10,ISDN-MIB::isdnBearerCallConnectTime,TimeTicks,read-only,,current,,The value of sysUpTime when the ISDN connect message for the current or last call was sent or received. If since system startup there has been no call on this interface, this object has a value of zero.
.1.3.6.1.2.1.10.20.1.2.1.1.11,ISDN-MIB::isdnBearerChargedUnits,Gauge32,read-only,,current,,The number of charged units for the current or last connection. For incoming calls or if charging information is not supplied by the switch, the value of this object is zero.
.1.3.6.1.2.1.10.20.1.3,ISDN-MIB::isdnSignalingGroup,,,,,,
.1.3.6.1.2.1.10.20.1.3.1,ISDN-MIB::isdnSignalingGetIndex,INTEGER,read-write,,current,,The recommended procedure for selecting a new index for isdnSignalingTable row creation is to GET the value of this object, and then to SET the object with the same value. If the SET operation succeeds, the manager can use this value as an index to create a new row in this table.
.1.3.6.1.2.1.10.20.1.3.2,ISDN-MIB::isdnSignalingTable,,not-accessible,,current,,ISDN signaling table containing configuration and operational parameters for all ISDN signaling channels on this managed device.
.1.3.6.1.2.1.10.20.1.3.2.1,ISDN-MIB::isdnSignalingEntry,,not-accessible,isdnSignalingIndex,current,,An entry in the ISDN Signaling Table. To create a new entry, only isdnSignalingProtocol needs to be specified before isdnSignalingStatus can become active(1).
.1.3.6.1.2.1.10.20.1.3.2.1.1,ISDN-MIB::isdnSignalingIndex,INTEGER,not-accessible,,current,,The index value which uniquely identifies an entry in the isdnSignalingTable.
.1.3.6.1.2.1.10.20.1.3.2.1.2,ISDN-MIB::isdnSignalingIfIndex,Integer32,read-only,,current,,The ifIndex value of the interface associated with this signaling channel.
.1.3.6.1.2.1.10.20.1.3.2.1.3,ISDN-MIB::isdnSignalingProtocol,INTEGER,read-create,,current,other(1):dss1(2):etsi(3):dass2(4):ess4(5):ess5(6):dms100(7):dms250(8):ni1(9):ni2(10):ni3(11):vn2(12):vn3(13):vn4(14):vn6(15):kdd(16):ins64(17):ins1500(18):itr6(19):cornet(20):ts013(21):ts014(22):qsig(23):swissnet2(24):swissnet3(25),The particular protocol type supported by the switch providing access to the ISDN network to which this signaling channel is connected.
.1.3.6.1.2.1.10.20.1.3.2.1.4,ISDN-MIB::isdnSignalingCallingAddress,OCTET,read-create,,current,,The ISDN Address to be assigned to this signaling channel. More specifically, this is the 'Calling Address information element' as being passed to the switch in outgoing call setup messages. It can be an EAZ (1TR6), a calling number (DSS1, ETSI) or any other number necessary to identify a signaling interface. If there is no such number defined or required, this is a zero length string. It is represented in DisplayString form. Incoming calls can also be identified by this number. If the Directory Number, i.e. the Called Number in incoming calls, is different to this number, the isdnDirectoryTable has to be used to specify all possible Directory Numbers. The format of this information largely depends on the type of switch or PBX the device is connected to. Therefore, the detailed format of this information is not specified and is implementation dependent. If possible, the agent should implement this information using the E.164 number format. In this case, the number must start with '+'. Otherwise, IA5 number digits must be used.
.1.3.6.1.2.1.10.20.1.3.2.1.5,ISDN-MIB::isdnSignalingSubAddress,OCTET,read-create,,current,,Supplementary information to the ISDN address assigned to this signaling channel. Usually, this is the subaddress as defined in Q.931. If there is no such number defined or required, this is a zero length string. The subaddress is used for incoming calls as well as for outgoing calls. The subaddress is an user supplied string of up to 20 IA5 characters and is transmitted transparently through the network.
.1.3.6.1.2.1.10.20.1.3.2.1.6,ISDN-MIB::isdnSignalingBchannelCount,Integer32,read-create,,current,,The total number of B channels (bearer channels) managed by this signaling channel. The default value of this object depends on the physical interface type and is either 2 for Basic Rate interfaces or 24 (30) for Primary Rate interfaces.
.1.3.6.1.2.1.10.20.1.3.2.1.7,ISDN-MIB::isdnSignalingInfoTrapEnable,INTEGER,read-create,,current,enabled(1):disabled(2),Indicates whether isdnMibCallInformation traps should be generated for calls on this signaling channel.
.1.3.6.1.2.1.10.20.1.3.2.1.8,ISDN-MIB::isdnSignalingStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the isdnSignalingTable.
.1.3.6.1.2.1.10.20.1.3.3,ISDN-MIB::isdnSignalingStatsTable,,not-accessible,,current,,ISDN signaling table containing statistics information for all ISDN signaling channels on this managed device. Only statistical information which is not already being counted in the ifTable is being defined in this table.
.1.3.6.1.2.1.10.20.1.3.3.1,ISDN-MIB::isdnSignalingStatsEntry,,not-accessible,,current,,An entry in the ISDN Signaling statistics Table.
.1.3.6.1.2.1.10.20.1.3.3.1.1,ISDN-MIB::isdnSigStatsInCalls,Counter32,read-only,,current,,The number of incoming calls on this interface.
.1.3.6.1.2.1.10.20.1.3.3.1.2,ISDN-MIB::isdnSigStatsInConnected,Counter32,read-only,,current,,The number of incoming calls on this interface which were actually connected.
.1.3.6.1.2.1.10.20.1.3.3.1.3,ISDN-MIB::isdnSigStatsOutCalls,Counter32,read-only,,current,,The number of outgoing calls on this interface.
.1.3.6.1.2.1.10.20.1.3.3.1.4,ISDN-MIB::isdnSigStatsOutConnected,Counter32,read-only,,current,,The number of outgoing calls on this interface which were actually connected.
.1.3.6.1.2.1.10.20.1.3.3.1.5,ISDN-MIB::isdnSigStatsChargedUnits,Counter32,read-only,,current,,The number of charging units on this interface since system startup. Only the charging units applying to the local interface, i.e. for originated calls or for calls with 'Reverse charging' being active, are counted here.
.1.3.6.1.2.1.10.20.1.3.4,ISDN-MIB::isdnLapdTable,,not-accessible,,current,,Table containing configuration and statistics information for all LAPD (D channel Data Link) interfaces on this managed device. Only statistical information which is not already being counted in the ifTable is being defined in this table.
.1.3.6.1.2.1.10.20.1.3.4.1,ISDN-MIB::isdnLapdEntry,,not-accessible,ifIndex,current,,An entry in the LAPD Table.
.1.3.6.1.2.1.10.20.1.3.4.1.1,ISDN-MIB::isdnLapdPrimaryChannel,INTEGER,read-write,,current,true(1):false(2),If set to true(1), this D channel is the designated primary D channel if D channel backup is active. There must be exactly one primary D channel configured. If D channel backup is not used, this object has a value of true(1).
.1.3.6.1.2.1.10.20.1.3.4.1.2,ISDN-MIB::isdnLapdOperStatus,INTEGER,read-only,,current,inactive(1):l1Active(2):l2Active(3),The operational status of this interface: inactive all layers are inactive l1Active layer 1 is activated, layer 2 datalink not established l2Active layer 1 is activated, layer 2 datalink established.
.1.3.6.1.2.1.10.20.1.3.4.1.3,ISDN-MIB::isdnLapdPeerSabme,Counter32,read-only,,current,,The number of peer SABME frames received on this interface. This is the number of peer-initiated new connections on this interface.
.1.3.6.1.2.1.10.20.1.3.4.1.4,ISDN-MIB::isdnLapdRecvdFrmr,Counter32,read-only,,current,,The number of LAPD FRMR response frames received. This is the number of framing errors on this interface.
.1.3.6.1.2.1.10.20.1.4,ISDN-MIB::isdnEndpointGroup,,,,,,
.1.3.6.1.2.1.10.20.1.4.1,ISDN-MIB::isdnEndpointGetIndex,INTEGER,read-write,,current,,The recommended procedure for selecting a new index for isdnEndpointTable row creation is to GET the value of this object, and then to SET the object with the same value. If the SET operation succeeds, the manager can use this value as an index to create a new row in this table.
.1.3.6.1.2.1.10.20.1.4.2,ISDN-MIB::isdnEndpointTable,,not-accessible,,current,,Table containing configuration for Terminal Endpoints.
.1.3.6.1.2.1.10.20.1.4.2.1,ISDN-MIB::isdnEndpointEntry,,not-accessible,isdnEndpointIndex,current,,An entry in the Terminal Endpoint Table. The value of isdnEndpointIfType must be supplied for a row in this table to become active.
.1.3.6.1.2.1.10.20.1.4.2.1.1,ISDN-MIB::isdnEndpointIndex,INTEGER,not-accessible,,current,,The index value which uniquely identifies an entry in the isdnEndpointTable.
.1.3.6.1.2.1.10.20.1.4.2.1.2,ISDN-MIB::isdnEndpointIfIndex,Integer32,read-only,,current,,The ifIndex value of the interface associated with this Terminal Endpoint.
.1.3.6.1.2.1.10.20.1.4.2.1.3,ISDN-MIB::isdnEndpointIfType,INTEGER,read-create,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The interface type for this Terminal Endpoint. Interface types of x25ple(40) and isdn(63) are allowed. The interface type is identical to the value of ifType in the associated ifEntry.
.1.3.6.1.2.1.10.20.1.4.2.1.4,ISDN-MIB::isdnEndpointTeiType,INTEGER,read-create,,current,dynamic(1):static(2),The type of TEI (Terminal Endpoint Identifier) used for this Terminal Endpoint. In case of dynamic(1), the TEI value is selected by the switch. In case of static(2), a valid TEI value has to be entered in the isdnEndpointTeiValue object. The default value for this object depends on the interface type as well as the Terminal Endpoint type. On Primary Rate interfaces the default value is static(2). On Basic Rate interfaces the default value is dynamic(1) for isdn(63) Terminal Endpoints and static(2) for x25ple(40) Terminal Endpoints.
.1.3.6.1.2.1.10.20.1.4.2.1.5,ISDN-MIB::isdnEndpointTeiValue,INTEGER,read-create,,current,,The TEI (Terminal Endpoint Identifier) value for this Terminal Endpoint. If isdnEndpointTeiType is set to static(2), valid numbers are 0..63, while otherwise the value is set internally. The default value of this object is 0 for static TEI assignment. The default value for dynamic TEI assignment is also 0 as long as no TEI has been assigned. After TEI assignment, the assigned TEI value is returned.
.1.3.6.1.2.1.10.20.1.4.2.1.6,ISDN-MIB::isdnEndpointSpid,OCTET,read-create,,current,,The Service profile IDentifier (SPID) information for this Terminal Endpoint. The SPID is composed of 9-20 numeric characters. This information has to be defined in addition to the local number for some switch protocol types, e.g. Bellcore NI-1 and NI-2. If this object is not required, it is a zero length string.
.1.3.6.1.2.1.10.20.1.4.2.1.7,ISDN-MIB::isdnEndpointStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the isdnEndpointTable.
.1.3.6.1.2.1.10.20.1.5,ISDN-MIB::isdnDirectoryGroup,,,,,,
.1.3.6.1.2.1.10.20.1.5.1,ISDN-MIB::isdnDirectoryTable,,not-accessible,,current,,Table containing Directory Numbers.
.1.3.6.1.2.1.10.20.1.5.1.1,ISDN-MIB::isdnDirectoryEntry,,not-accessible,isdnDirectoryIndex,current,,An entry in the Directory Number Table. All objects in an entry must be set for a new row to become active.
.1.3.6.1.2.1.10.20.1.5.1.1.1,ISDN-MIB::isdnDirectoryIndex,INTEGER,not-accessible,,current,,The index value which uniquely identifies an entry in the isdnDirectoryTable.
.1.3.6.1.2.1.10.20.1.5.1.1.2,ISDN-MIB::isdnDirectoryNumber,OCTET,read-create,,current,,A Directory Number. Directory Numbers are used to identify incoming calls on the signaling channel given in isdnDirectorySigIndex. The format of this information largely depends on the type of switch or PBX the device is connected to. Therefore, the detailed format of this information is not specified and is implementation dependent. If possible, the agent should implement this information using the E.164 number format. In this case, the number must start with '+'. Otherwise, IA5 number digits must be used.
.1.3.6.1.2.1.10.20.1.5.1.1.3,ISDN-MIB::isdnDirectorySigIndex,INTEGER,read-create,,current,,An index pointing to an ISDN signaling channel. Incoming calls are accepted on this signaling channel if the isdnDirectoryNumber is presented as Called Number in the SETUP message.
.1.3.6.1.2.1.10.20.1.5.1.1.4,ISDN-MIB::isdnDirectoryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the isdnDirectoryTable.
.1.3.6.1.2.1.10.20.2,ISDN-MIB::isdnMibConformance,,,,,,
.1.3.6.1.2.1.10.20.2.0,ISDN-MIB::isdnMibTraps,,,,,,
.1.3.6.1.2.1.10.20.2.0.1,ISDN-MIB::isdnMibCallInformation,,,,,,This trap/inform is sent to the manager under the following condidions: - on incoming calls for each call which is rejected for policy reasons (e.g. unknown neighbor or access violation) - on outgoing calls whenever a call attempt is determined to have ultimately failed. In the event that call retry is active, then this will be after all retry attempts have failed. - whenever a call connects. In this case, the object isdnBearerCallConnectTime should be included in the trap. Only one such trap is sent in between successful or unsuccessful call attempts from or to a single neighbor; subsequent call attempts result in no trap. If the Dial Control MIB objects dialCtlNbrCfgId and dialCtlNbrCfgIndex are known by the entity generating this trap, both objects should be included in the trap as well. The receipt of this trap with no dial neighbor information indicates that the manager must poll the callHistoryTable of the Dial Control MIB to see what changed.
.1.3.6.1.2.1.10.20.2.1,ISDN-MIB::isdnMibCompliances,,,,,,
.1.3.6.1.2.1.10.20.2.1.1,ISDN-MIB::isdnMibCompliance,,,,,,The compliance statement for entities which implement the ISDN MIB.
.1.3.6.1.2.1.10.20.2.2,ISDN-MIB::isdnMibGroups,,,,,,
.1.3.6.1.2.1.10.20.2.2.1,ISDN-MIB::isdnMibBasicRateGroup,,,,,,A collection of objects required for ISDN Basic Rate physical interface configuration and statistics.
.1.3.6.1.2.1.10.20.2.2.2,ISDN-MIB::isdnMibBearerGroup,,,,,,A collection of objects required for ISDN Bearer channel control and statistics.
.1.3.6.1.2.1.10.20.2.2.3,ISDN-MIB::isdnMibSignalingGroup,,,,,,A collection of objects required for ISDN D channel configuration and statistics.
.1.3.6.1.2.1.10.20.2.2.4,ISDN-MIB::isdnMibEndpointGroup,,,,,,A collection of objects describing Terminal Endpoints.
.1.3.6.1.2.1.10.20.2.2.5,ISDN-MIB::isdnMibDirectoryGroup,,,,,,A collection of objects describing directory numbers.
.1.3.6.1.2.1.10.20.2.2.6,ISDN-MIB::isdnMibNotificationsGroup,,,,,,The notifications which a ISDN MIB entity is required to implement.
.1.3.6.1.2.1.10.21,DIAL-CONTROL-MIB::dialControlMib,,,,,,The MIB module to describe peer information for demand access and possibly other kinds of interfaces.
.1.3.6.1.2.1.10.21.1,DIAL-CONTROL-MIB::dialControlMibObjects,,,,,,
.1.3.6.1.2.1.10.21.1.1,DIAL-CONTROL-MIB::dialCtlConfiguration,,,,,,
.1.3.6.1.2.1.10.21.1.1.1,DIAL-CONTROL-MIB::dialCtlAcceptMode,INTEGER,read-write,,current,acceptNone(1):acceptAll(2):acceptKnown(3),The security level for acceptance of incoming calls. acceptNone(1) - incoming calls will not be accepted acceptAll(2) - incoming calls will be accepted, even if there is no matching entry in the dialCtlPeerCfgTable acceptKnown(3) - incoming calls will be accepted only if there is a matching entry in the dialCtlPeerCfgTable 
.1.3.6.1.2.1.10.21.1.1.2,DIAL-CONTROL-MIB::dialCtlTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether dialCtlPeerCallInformation and dialCtlPeerCallSetup traps should be generated for all peers. If the value of this object is enabled(1), traps will be generated for all peers. If the value of this object is disabled(2), traps will be generated only for peers having dialCtlPeerCfgTrapEnable set to enabled(1).
.1.3.6.1.2.1.10.21.1.2,DIAL-CONTROL-MIB::dialCtlPeer,,,,,,
.1.3.6.1.2.1.10.21.1.2.1,DIAL-CONTROL-MIB::dialCtlPeerCfgTable,,not-accessible,,current,,The list of peers from which the managed device will accept calls or to which it will place them.
.1.3.6.1.2.1.10.21.1.2.1.1,DIAL-CONTROL-MIB::dialCtlPeerCfgEntry,,not-accessible,dialCtlPeerCfgId:ifIndex,current,,Configuration data for a single Peer. This entry is effectively permanent, and contains information to identify the peer, how to connect to the peer, how to identify the peer and its permissions. The value of dialCtlPeerCfgOriginateAddress must be specified before a new row in this table can become active(1). Any writeable parameters in an existing entry can be modified while the entry is active. The modification will take effect when the peer in question will be called the next time. An entry in this table can only be created if the associated ifEntry already exists.
.1.3.6.1.2.1.10.21.1.2.1.1.1,DIAL-CONTROL-MIB::dialCtlPeerCfgId,INTEGER,not-accessible,,current,,This object identifies a single peer. There may be several entries in this table for one peer, defining different ways of reaching this peer. Thus, there may be several entries in this table with the same value of dialCtlPeerCfgId. Multiple entries for one peer may be used to support multilink as well as backup lines. A single peer will be identified by a unique value of this object. Several entries for one peer MUST have the same value of dialCtlPeerCfgId, but different ifEntries and thus different values of ifIndex.
.1.3.6.1.2.1.10.21.1.2.1.1.2,DIAL-CONTROL-MIB::dialCtlPeerCfgIfType,INTEGER,read-create,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The interface type to be used for calling this peer. In case of ISDN, the value of isdn(63) is to be used.
.1.3.6.1.2.1.10.21.1.2.1.1.3,DIAL-CONTROL-MIB::dialCtlPeerCfgLowerIf,Integer32,read-create,,current,,ifIndex value of an interface the peer will have to be called on. For example, on an ISDN interface, this can be the ifIndex value of a D channel or the ifIndex value of a B channel, whatever is appropriate for a given peer. As an example, for Basic Rate leased lines it will be necessary to specify a B channel ifIndex, while for semi-permanent connections the D channel ifIndex has to be specified. If the interface can be dynamically assigned, this object has a value of zero.
.1.3.6.1.2.1.10.21.1.2.1.1.4,DIAL-CONTROL-MIB::dialCtlPeerCfgOriginateAddress,OCTET,read-create,,current,,Call Address at which the peer will be called. Think of this as the set of characters following 'ATDT ' or the 'phone number' included in a D channel call request. The structure of this information will be switch type specific. If there is no address information required for reaching the peer, i.e., for leased lines, this object will be a zero length string.
.1.3.6.1.2.1.10.21.1.2.1.1.5,DIAL-CONTROL-MIB::dialCtlPeerCfgAnswerAddress,OCTET,read-create,,current,,Calling Party Number information element, as for example passed in an ISDN SETUP message by a PBX or switch, for incoming calls. This address can be used to identify the peer. If this address is either unknown or identical to dialCtlPeerCfgOriginateAddress, this object will be a zero length string.
.1.3.6.1.2.1.10.21.1.2.1.1.6,DIAL-CONTROL-MIB::dialCtlPeerCfgSubAddress,OCTET,read-create,,current,,Subaddress at which the peer will be called. If the subaddress is undefined for the given media or unused, this is a zero length string.
.1.3.6.1.2.1.10.21.1.2.1.1.7,DIAL-CONTROL-MIB::dialCtlPeerCfgClosedUserGroup,OCTET,read-create,,current,,Closed User Group at which the peer will be called. If the Closed User Group is undefined for the given media or unused, this is a zero length string.
.1.3.6.1.2.1.10.21.1.2.1.1.8,DIAL-CONTROL-MIB::dialCtlPeerCfgSpeed,INTEGER,read-create,,current,,The desired information transfer speed in bits/second when calling this peer. The detailed media specific information, e.g. information type and information transfer rate for ISDN circuits, has to be extracted from this object. If the transfer speed to be used is unknown or the default speed for this type of interfaces, the value of this object may be zero.
.1.3.6.1.2.1.10.21.1.2.1.1.9,DIAL-CONTROL-MIB::dialCtlPeerCfgInfoType,INTEGER,read-create,,current,other(1):speech(2):unrestrictedDigital(3):unrestrictedDigital56(4):restrictedDigital(5):audio31(6):audio7(7):video(8):packetSwitched(9):fax(10),The Information Transfer Capability to be used when calling this peer. speech(2) refers to a non-data connection, whereas audio31(6) and audio7(7) refer to data mode connections.
.1.3.6.1.2.1.10.21.1.2.1.1.10,DIAL-CONTROL-MIB::dialCtlPeerCfgPermission,INTEGER,read-create,,current,originate(1):answer(2):both(3):callback(4):none(5),Applicable permissions. callback(4) either rejects the call and then calls back, or uses the 'Reverse charging' information element if it is available. Note that callback(4) is supposed to control charging, not security, and applies to callback prior to accepting a call. Callback for security reasons can be handled using PPP callback.
.1.3.6.1.2.1.10.21.1.2.1.1.11,DIAL-CONTROL-MIB::dialCtlPeerCfgInactivityTimer,INTEGER,read-create,,current,,The connection will be automatically disconnected if no longer carrying useful data for a time period, in seconds, specified in this object. Useful data in this context refers to forwarding packets, including routing information; it excludes the encapsulator maintenance frames. A value of zero means the connection will not be automatically taken down due to inactivity, which implies that it is a dedicated circuit.
.1.3.6.1.2.1.10.21.1.2.1.1.12,DIAL-CONTROL-MIB::dialCtlPeerCfgMinDuration,INTEGER,read-create,,current,,Minimum duration of a call in seconds, starting from the time the call is connected until the call is disconnected. This is to accomplish the fact that in most countries charging applies to units of time, which should be matched as closely as possible.
.1.3.6.1.2.1.10.21.1.2.1.1.13,DIAL-CONTROL-MIB::dialCtlPeerCfgMaxDuration,INTEGER,read-create,,current,,Maximum call duration in seconds. Zero means 'unlimited'.
.1.3.6.1.2.1.10.21.1.2.1.1.14,DIAL-CONTROL-MIB::dialCtlPeerCfgCarrierDelay,INTEGER,read-create,,current,,The call timeout time in seconds. The default value of zero means that the call timeout as specified for the media in question will apply.
.1.3.6.1.2.1.10.21.1.2.1.1.15,DIAL-CONTROL-MIB::dialCtlPeerCfgCallRetries,INTEGER,read-create,,current,,The number of calls to a non-responding address that may be made. A retry count of zero means there is no bound. The intent is to bound the number of successive calls to an address which is inaccessible, or which refuses those calls. Some countries regulate the number of call retries to a given peer that can be made.
.1.3.6.1.2.1.10.21.1.2.1.1.16,DIAL-CONTROL-MIB::dialCtlPeerCfgRetryDelay,INTEGER,read-create,,current,,The time in seconds between call retries if a peer cannot be reached. A value of zero means that call retries may be done without any delay.
.1.3.6.1.2.1.10.21.1.2.1.1.17,DIAL-CONTROL-MIB::dialCtlPeerCfgFailureDelay,INTEGER,read-create,,current,,The time in seconds after which call attempts are to be placed again after a peer has been noticed to be unreachable, i.e. after dialCtlPeerCfgCallRetries unsuccessful call attempts. A value of zero means that a peer will not be called again after dialCtlPeerCfgCallRetries unsuccessful call attempts.
.1.3.6.1.2.1.10.21.1.2.1.1.18,DIAL-CONTROL-MIB::dialCtlPeerCfgTrapEnable,INTEGER,read-create,,current,enabled(1):disabled(2),This object indicates whether dialCtlPeerCallInformation and dialCtlPeerCallSetup traps should be generated for this peer.
.1.3.6.1.2.1.10.21.1.2.1.1.19,DIAL-CONTROL-MIB::dialCtlPeerCfgStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status of one row in this table.
.1.3.6.1.2.1.10.21.1.2.2,DIAL-CONTROL-MIB::dialCtlPeerStatsTable,,not-accessible,,current,,Statistics information for each peer entry. There will be one entry in this table for each entry in the dialCtlPeerCfgTable.
.1.3.6.1.2.1.10.21.1.2.2.1,DIAL-CONTROL-MIB::dialCtlPeerStatsEntry,,not-accessible,,current,,Statistics information for a single Peer. This entry is effectively permanent, and contains information describing the last call attempt as well as supplying statistical information.
.1.3.6.1.2.1.10.21.1.2.2.1.1,DIAL-CONTROL-MIB::dialCtlPeerStatsConnectTime,Unsigned32,read-only,,current,,Accumulated connect time to the peer since system startup. This is the total connect time, i.e. the connect time for outgoing calls plus the time for incoming calls.
.1.3.6.1.2.1.10.21.1.2.2.1.2,DIAL-CONTROL-MIB::dialCtlPeerStatsChargedUnits,Unsigned32,read-only,,current,,The total number of charging units applying to this peer since system startup. Only the charging units applying to the local interface, i.e. for originated calls or for calls with 'Reverse charging' being active, will be counted here.
.1.3.6.1.2.1.10.21.1.2.2.1.3,DIAL-CONTROL-MIB::dialCtlPeerStatsSuccessCalls,Unsigned32,read-only,,current,,Number of completed calls to this peer.
.1.3.6.1.2.1.10.21.1.2.2.1.4,DIAL-CONTROL-MIB::dialCtlPeerStatsFailCalls,Unsigned32,read-only,,current,,Number of failed call attempts to this peer since system startup.
.1.3.6.1.2.1.10.21.1.2.2.1.5,DIAL-CONTROL-MIB::dialCtlPeerStatsAcceptCalls,Unsigned32,read-only,,current,,Number of calls from this peer accepted since system startup.
.1.3.6.1.2.1.10.21.1.2.2.1.6,DIAL-CONTROL-MIB::dialCtlPeerStatsRefuseCalls,Unsigned32,read-only,,current,,Number of calls from this peer refused since system startup.
.1.3.6.1.2.1.10.21.1.2.2.1.7,DIAL-CONTROL-MIB::dialCtlPeerStatsLastDisconnectCause,OCTET,read-only,,current,,The encoded network cause value associated with the last call. This object will be updated whenever a call is started or cleared. The value of this object will depend on the interface type as well as on the protocol and protocol version being used on this interface. Some references for possible cause values are given below.
.1.3.6.1.2.1.10.21.1.2.2.1.8,DIAL-CONTROL-MIB::dialCtlPeerStatsLastDisconnectText,OCTET,read-only,,current,,ASCII text describing the reason for the last call termination. This object exists because it would be impossible for a management station to store all possible cause values for all types of interfaces. It should be used only if a management station is unable to decode the value of dialCtlPeerStatsLastDisconnectCause. This object will be updated whenever a call is started or cleared.
.1.3.6.1.2.1.10.21.1.2.2.1.9,DIAL-CONTROL-MIB::dialCtlPeerStatsLastSetupTime,TimeTicks,read-only,,current,,The value of sysUpTime when the last call to this peer was started. For ISDN media, this will be the time when the setup message was received from or sent to the network. This object will be updated whenever a call is started or cleared.
.1.3.6.1.2.1.10.21.1.3,DIAL-CONTROL-MIB::callActive,,,,,,
.1.3.6.1.2.1.10.21.1.3.1,DIAL-CONTROL-MIB::callActiveTable,,not-accessible,,current,,A table containing information about active calls to a specific destination.
.1.3.6.1.2.1.10.21.1.3.1.1,DIAL-CONTROL-MIB::callActiveEntry,,not-accessible,callActiveSetupTime:callActiveIndex,current,,The information regarding a single active Connection. An entry in this table will be created when a call is started. An entry in this table will be deleted when an active call clears.
.1.3.6.1.2.1.10.21.1.3.1.1.1,DIAL-CONTROL-MIB::callActiveSetupTime,TimeTicks,not-accessible,,current,,The value of sysUpTime when the call associated to this entry was started. This will be useful for an NMS to retrieve all calls after a specific time. Also, this object can be useful in finding large delays between the time the call was started and the time the call was connected. For ISDN media, this will be the time when the setup message was received from or sent to the network.
.1.3.6.1.2.1.10.21.1.3.1.1.2,DIAL-CONTROL-MIB::callActiveIndex,INTEGER,not-accessible,,current,,Small index variable to distinguish calls that start in the same hundredth of a second.
.1.3.6.1.2.1.10.21.1.3.1.1.3,DIAL-CONTROL-MIB::callActivePeerAddress,OCTET,read-only,,current,,The number this call is connected to. If the number is not available, then it will have a length of zero.
.1.3.6.1.2.1.10.21.1.3.1.1.4,DIAL-CONTROL-MIB::callActivePeerSubAddress,OCTET,read-only,,current,,The subaddress this call is connected to. If the subaddress is undefined or not available, this will be a zero length string.
.1.3.6.1.2.1.10.21.1.3.1.1.5,DIAL-CONTROL-MIB::callActivePeerId,INTEGER,read-only,,current,,This is the Id value of the peer table entry to which this call was made. If a peer table entry for this call does not exist or is unknown, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.3.1.1.6,DIAL-CONTROL-MIB::callActivePeerIfIndex,INTEGER,read-only,,current,,This is the ifIndex value of the peer table entry to which this call was made. If a peer table entry for this call does not exist or is unknown, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.3.1.1.7,DIAL-CONTROL-MIB::callActiveLogicalIfIndex,Integer32,read-only,,current,,This is the ifIndex value of the logical interface through which this call was made. For ISDN media, this would be the ifIndex of the B channel which was used for this call. If the ifIndex value is unknown, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.3.1.1.8,DIAL-CONTROL-MIB::callActiveConnectTime,TimeTicks,read-only,,current,,The value of sysUpTime when the call was connected. If the call is not connected, this object will have a value of zero.
.1.3.6.1.2.1.10.21.1.3.1.1.9,DIAL-CONTROL-MIB::callActiveCallState,INTEGER,read-only,,current,unknown(1):connecting(2):connected(3):active(4),The current call state. unknown(1) - The call state is unknown. connecting(2) - A connection attempt (outgoing call) is being made. connected(3) - An incoming call is in the process of validation. active(4) - The call is active. 
.1.3.6.1.2.1.10.21.1.3.1.1.10,DIAL-CONTROL-MIB::callActiveCallOrigin,INTEGER,read-only,,current,originate(1):answer(2):callback(3),The call origin.
.1.3.6.1.2.1.10.21.1.3.1.1.11,DIAL-CONTROL-MIB::callActiveChargedUnits,Unsigned32,read-only,,current,,The number of charged units for this connection. For incoming calls or if charging information is not supplied by the switch, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.3.1.1.12,DIAL-CONTROL-MIB::callActiveInfoType,INTEGER,read-only,,current,other(1):speech(2):unrestrictedDigital(3):unrestrictedDigital56(4):restrictedDigital(5):audio31(6):audio7(7):video(8):packetSwitched(9):fax(10),The information type for this call.
.1.3.6.1.2.1.10.21.1.3.1.1.13,DIAL-CONTROL-MIB::callActiveTransmitPackets,Unsigned32,read-only,,current,,The number of packets which were transmitted for this call.
.1.3.6.1.2.1.10.21.1.3.1.1.14,DIAL-CONTROL-MIB::callActiveTransmitBytes,Unsigned32,read-only,,current,,The number of bytes which were transmitted for this call.
.1.3.6.1.2.1.10.21.1.3.1.1.15,DIAL-CONTROL-MIB::callActiveReceivePackets,Unsigned32,read-only,,current,,The number of packets which were received for this call.
.1.3.6.1.2.1.10.21.1.3.1.1.16,DIAL-CONTROL-MIB::callActiveReceiveBytes,Unsigned32,read-only,,current,,The number of bytes which were received for this call.
.1.3.6.1.2.1.10.21.1.4,DIAL-CONTROL-MIB::callHistory,,,,,,
.1.3.6.1.2.1.10.21.1.4.1,DIAL-CONTROL-MIB::callHistoryTableMaxLength,INTEGER,read-write,,current,,The upper limit on the number of entries that the callHistoryTable may contain. A value of 0 will prevent any history from being retained. When this table is full, the oldest entry will be deleted and the new one will be created.
.1.3.6.1.2.1.10.21.1.4.2,DIAL-CONTROL-MIB::callHistoryRetainTimer,INTEGER,read-write,,current,,The minimum amount of time that an callHistoryEntry will be maintained before being deleted. A value of 0 will prevent any history from being retained in the callHistoryTable, but will neither prevent callCompletion traps being generated nor affect other tables.
.1.3.6.1.2.1.10.21.1.4.3,DIAL-CONTROL-MIB::callHistoryTable,,not-accessible,,current,,A table containing information about specific calls to a specific destination.
.1.3.6.1.2.1.10.21.1.4.3.1,DIAL-CONTROL-MIB::callHistoryEntry,,not-accessible,callActiveSetupTime:callActiveIndex,current,,The information regarding a single Connection.
.1.3.6.1.2.1.10.21.1.4.3.1.1,DIAL-CONTROL-MIB::callHistoryPeerAddress,OCTET,read-only,,current,,The number this call was connected to. If the number is not available, then it will have a length of zero.
.1.3.6.1.2.1.10.21.1.4.3.1.2,DIAL-CONTROL-MIB::callHistoryPeerSubAddress,OCTET,read-only,,current,,The subaddress this call was connected to. If the subaddress is undefined or not available, this will be a zero length string.
.1.3.6.1.2.1.10.21.1.4.3.1.3,DIAL-CONTROL-MIB::callHistoryPeerId,INTEGER,read-only,,current,,This is the Id value of the peer table entry to which this call was made. If a peer table entry for this call does not exist, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.4.3.1.4,DIAL-CONTROL-MIB::callHistoryPeerIfIndex,INTEGER,read-only,,current,,This is the ifIndex value of the peer table entry to which this call was made. If a peer table entry for this call does not exist, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.4.3.1.5,DIAL-CONTROL-MIB::callHistoryLogicalIfIndex,Integer32,read-only,,current,,This is the ifIndex value of the logical interface through which this call was made. For ISDN media, this would be the ifIndex of the B channel which was used for this call.
.1.3.6.1.2.1.10.21.1.4.3.1.6,DIAL-CONTROL-MIB::callHistoryDisconnectCause,OCTET,read-only,,current,,The encoded network cause value associated with this call. The value of this object will depend on the interface type as well as on the protocol and protocol version being used on this interface. Some references for possible cause values are given below.
.1.3.6.1.2.1.10.21.1.4.3.1.7,DIAL-CONTROL-MIB::callHistoryDisconnectText,OCTET,read-only,,current,,ASCII text describing the reason for call termination. This object exists because it would be impossible for a management station to store all possible cause values for all types of interfaces. It should be used only if a management station is unable to decode the value of dialCtlPeerStatsLastDisconnectCause.
.1.3.6.1.2.1.10.21.1.4.3.1.8,DIAL-CONTROL-MIB::callHistoryConnectTime,TimeTicks,read-only,,current,,The value of sysUpTime when the call was connected.
.1.3.6.1.2.1.10.21.1.4.3.1.9,DIAL-CONTROL-MIB::callHistoryDisconnectTime,TimeTicks,read-only,,current,,The value of sysUpTime when the call was disconnected.
.1.3.6.1.2.1.10.21.1.4.3.1.10,DIAL-CONTROL-MIB::callHistoryCallOrigin,INTEGER,read-only,,current,originate(1):answer(2):callback(3),The call origin.
.1.3.6.1.2.1.10.21.1.4.3.1.11,DIAL-CONTROL-MIB::callHistoryChargedUnits,Unsigned32,read-only,,current,,The number of charged units for this connection. For incoming calls or if charging information is not supplied by the switch, the value of this object will be zero.
.1.3.6.1.2.1.10.21.1.4.3.1.12,DIAL-CONTROL-MIB::callHistoryInfoType,INTEGER,read-only,,current,other(1):speech(2):unrestrictedDigital(3):unrestrictedDigital56(4):restrictedDigital(5):audio31(6):audio7(7):video(8):packetSwitched(9):fax(10),The information type for this call.
.1.3.6.1.2.1.10.21.1.4.3.1.13,DIAL-CONTROL-MIB::callHistoryTransmitPackets,Unsigned32,read-only,,current,,The number of packets which were transmitted while this call was active.
.1.3.6.1.2.1.10.21.1.4.3.1.14,DIAL-CONTROL-MIB::callHistoryTransmitBytes,Unsigned32,read-only,,current,,The number of bytes which were transmitted while this call was active.
.1.3.6.1.2.1.10.21.1.4.3.1.15,DIAL-CONTROL-MIB::callHistoryReceivePackets,Unsigned32,read-only,,current,,The number of packets which were received while this call was active.
.1.3.6.1.2.1.10.21.1.4.3.1.16,DIAL-CONTROL-MIB::callHistoryReceiveBytes,Unsigned32,read-only,,current,,The number of bytes which were received while this call was active.
.1.3.6.1.2.1.10.21.2,DIAL-CONTROL-MIB::dialControlMibTrapPrefix,,,,,,
.1.3.6.1.2.1.10.21.2.0,DIAL-CONTROL-MIB::dialControlMibTraps,,,,,,
.1.3.6.1.2.1.10.21.2.0.1,DIAL-CONTROL-MIB::dialCtlPeerCallInformation,,,,,,This trap/inform is sent to the manager whenever a successful call clears, or a failed call attempt is determined to have ultimately failed. In the event that call retry is active, then this is after all retry attempts have failed. However, only one such trap is sent in between successful call attempts; subsequent call attempts result in no trap. ifOperStatus will return the operational status of the virtual interface associated with the peer to whom this call was made to.
.1.3.6.1.2.1.10.21.2.0.2,DIAL-CONTROL-MIB::dialCtlPeerCallSetup,,,,,,This trap/inform is sent to the manager whenever a call setup message is received or sent. ifOperStatus will return the operational status of the virtual interface associated with the peer to whom this call was made to.
.1.3.6.1.2.1.10.21.3,DIAL-CONTROL-MIB::dialControlMibConformance,,,,,,
.1.3.6.1.2.1.10.21.3.1,DIAL-CONTROL-MIB::dialControlMibCompliances,,,,,,
.1.3.6.1.2.1.10.21.3.1.1,DIAL-CONTROL-MIB::dialControlMibCompliance,,,,,,The compliance statement for entities which implement the DIAL CONTROL MIB
.1.3.6.1.2.1.10.21.3.2,DIAL-CONTROL-MIB::dialControlMibGroups,,,,,,
.1.3.6.1.2.1.10.21.3.2.1,DIAL-CONTROL-MIB::dialControlGroup,,,,,,A collection of objects providing the DIAL CONTROL capability.
.1.3.6.1.2.1.10.21.3.2.2,DIAL-CONTROL-MIB::callActiveGroup,,,,,,A collection of objects providing the active call capability.
.1.3.6.1.2.1.10.21.3.2.3,DIAL-CONTROL-MIB::callHistoryGroup,,,,,,A collection of objects providing the Call History capability.
.1.3.6.1.2.1.10.21.3.2.4,DIAL-CONTROL-MIB::callNotificationsGroup,,,,,,The notifications which a Dial Control MIB entity is required to implement.
.1.3.6.1.2.1.10.23,PPP-LCP-MIB::ppp,,,,,,
.1.3.6.1.2.1.10.23.1,PPP-LCP-MIB::pppLcp,,,,,,
.1.3.6.1.2.1.10.23.1.1,PPP-LCP-MIB::pppLink,,,,,,
.1.3.6.1.2.1.10.23.1.1.1,PPP-LCP-MIB::pppLinkStatusTable,,not-accessible,,mandatory,,A table containing PPP-link specific variables for this PPP implementation.
.1.3.6.1.2.1.10.23.1.1.1.1,PPP-LCP-MIB::pppLinkStatusEntry,,not-accessible,ifIndex,mandatory,,Management information about a particular PPP Link.
.1.3.6.1.2.1.10.23.1.1.1.1.1,PPP-LCP-MIB::pppLinkStatusPhysicalIndex,INTEGER,read-only,,mandatory,,The value of ifIndex that identifies the lower-level interface over which this PPP Link is operating. This interface would usually be an HDLC or RS-232 type of interface. If there is no lower-layer interface element, or there is no ifEntry for the element, or the element can not be identified, then the value of this object is 0. For example, suppose that PPP is operating over a serial port. This would use two entries in the ifTable. The PPP could be running over `interface' number 123 and the serial port could be running over `interface' number 987. Therefore, ifSpecific.123 would contain the OBJECT IDENTIFIER ppp pppLinkStatusPhysicalIndex.123 would contain 987, and ifSpecific.987 would contain the OBJECT IDENTIFIER for the serial-port's media- specific MIB.
.1.3.6.1.2.1.10.23.1.1.1.1.2,PPP-LCP-MIB::pppLinkStatusBadAddresses,Counter32,read-only,,mandatory,,The number of packets received with an incorrect Address Field. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.
.1.3.6.1.2.1.10.23.1.1.1.1.3,PPP-LCP-MIB::pppLinkStatusBadControls,Counter32,read-only,,mandatory,,The number of packets received on this link with an incorrect Control Field. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.
.1.3.6.1.2.1.10.23.1.1.1.1.4,PPP-LCP-MIB::pppLinkStatusPacketTooLongs,Counter32,read-only,,mandatory,,The number of received packets that have been discarded because their length exceeded the MRU. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link. NOTE, packets which are longer than the MRU but which are successfully received and processed are NOT included in this count.
.1.3.6.1.2.1.10.23.1.1.1.1.5,PPP-LCP-MIB::pppLinkStatusBadFCSs,Counter32,read-only,,mandatory,,The number of received packets that have been discarded due to having an incorrect FCS. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.
.1.3.6.1.2.1.10.23.1.1.1.1.6,PPP-LCP-MIB::pppLinkStatusLocalMRU,INTEGER,read-only,,mandatory,,The current value of the MRU for the local PPP Entity. This value is the MRU that the remote entity is using when sending packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.7,PPP-LCP-MIB::pppLinkStatusRemoteMRU,INTEGER,read-only,,mandatory,,The current value of the MRU for the remote PPP Entity. This value is the MRU that the local entity is using when sending packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.8,PPP-LCP-MIB::pppLinkStatusLocalToPeerACCMap,OCTET,read-only,,mandatory,,The current value of the ACC Map used for sending packets from the local PPP entity to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.9,PPP-LCP-MIB::pppLinkStatusPeerToLocalACCMap,OCTET,read-only,,mandatory,,The ACC Map used by the remote PPP entity when transmitting packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.10,PPP-LCP-MIB::pppLinkStatusLocalToRemoteProtocolCompression,INTEGER,read-only,,mandatory,enabled(1):disabled(2),Indicates whether the local PPP entity will use Protocol Compression when transmitting packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.11,PPP-LCP-MIB::pppLinkStatusRemoteToLocalProtocolCompression,INTEGER,read-only,,mandatory,enabled(1):disabled(2),Indicates whether the remote PPP entity will use Protocol Compression when transmitting packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.12,PPP-LCP-MIB::pppLinkStatusLocalToRemoteACCompression,INTEGER,read-only,,mandatory,enabled(1):disabled(2),Indicates whether the local PPP entity will use Address and Control Compression when transmitting packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.13,PPP-LCP-MIB::pppLinkStatusRemoteToLocalACCompression,INTEGER,read-only,,mandatory,enabled(1):disabled(2),Indicates whether the remote PPP entity will use Address and Control Compression when transmitting packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.14,PPP-LCP-MIB::pppLinkStatusTransmitFcsSize,INTEGER,read-only,,mandatory,,The size of the Frame Check Sequence (FCS) in bits that the local node will generate when sending packets to the remote node. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.1.1.15,PPP-LCP-MIB::pppLinkStatusReceiveFcsSize,INTEGER,read-only,,mandatory,,The size of the Frame Check Sequence (FCS) in bits that the remote node will generate when sending packets to the local node. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).
.1.3.6.1.2.1.10.23.1.1.2,PPP-LCP-MIB::pppLinkConfigTable,,not-accessible,,mandatory,,A table containing the LCP configuration parameters for this PPP Link. These variables represent the initial configuration of the PPP Link. The actual values of the parameters may be changed when the link is brought up via the LCP options negotiation mechanism.
.1.3.6.1.2.1.10.23.1.1.2.1,PPP-LCP-MIB::pppLinkConfigEntry,,not-accessible,ifIndex,mandatory,,Configuration information about a particular PPP Link.
.1.3.6.1.2.1.10.23.1.1.2.1.1,PPP-LCP-MIB::pppLinkConfigInitialMRU,INTEGER,read-write,,mandatory,,The initial Maximum Receive Unit (MRU) that the local PPP entity will advertise to the remote entity. If the value of this variable is 0 then the local PPP entity will not advertise any MRU to the remote entity and the default MRU will be assumed. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.1.1.2.1.2,PPP-LCP-MIB::pppLinkConfigReceiveACCMap,OCTET,read-write,,mandatory,,The Asynchronous-Control-Character-Map (ACC) that the local PPP entity requires for use on its receive side. In effect, this is the ACC Map that is required in order to ensure that the local modem will successfully receive all characters. The actual ACC map used on the receive side of the link will be a combination of the local node's pppLinkConfigReceiveACCMap and the remote node's pppLinkConfigTransmitACCMap. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.1.1.2.1.3,PPP-LCP-MIB::pppLinkConfigTransmitACCMap,OCTET,read-write,,mandatory,,The Asynchronous-Control-Character-Map (ACC) that the local PPP entity requires for use on its transmit side. In effect, this is the ACC Map that is required in order to ensure that all characters can be successfully transmitted through the local modem. The actual ACC map used on the transmit side of the link will be a combination of the local node's pppLinkConfigTransmitACCMap and the remote node's pppLinkConfigReceiveACCMap. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.1.1.2.1.4,PPP-LCP-MIB::pppLinkConfigMagicNumber,INTEGER,read-write,,mandatory,false(1):true(2),If true(2) then the local node will attempt to perform Magic Number negotiation with the remote node. If false(1) then this negotiation is not performed. In any event, the local node will comply with any magic number negotiations attempted by the remote node, per the PPP specification. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.1.1.2.1.5,PPP-LCP-MIB::pppLinkConfigFcsSize,INTEGER,read-write,,mandatory,,The size of the FCS, in bits, the local node will attempt to negotiate for use with the remote node. Regardless of the value of this object, the local node will comply with any FCS size negotiations initiated by the remote node, per the PPP specification. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.1.2,PPP-LCP-MIB::pppLqr,,,,,,
.1.3.6.1.2.1.10.23.1.2.1,PPP-LCP-MIB::pppLqrTable,,not-accessible,,mandatory,,Table containing the LQR parameters and statistics for the local PPP entity.
.1.3.6.1.2.1.10.23.1.2.1.1,PPP-LCP-MIB::pppLqrEntry,,not-accessible,ifIndex,mandatory,,LQR information for a particular PPP link. A PPP link will have an entry in this table if and only if LQR Quality Monitoring has been successfully negotiated for said link.
.1.3.6.1.2.1.10.23.1.2.1.1.1,PPP-LCP-MIB::pppLqrQuality,INTEGER,read-only,,mandatory,good(1):bad(2):not-determined(3),The current quality of the link as declared by the local PPP entity's Link-Quality Management modules. No effort is made to define good or bad, nor the policy used to determine it. The not-determined value indicates that the entity does not actually evaluate the link's quality. This value is used to disambiguate the `determined to be good' case from the `no determination made and presumed to be good' case.
.1.3.6.1.2.1.10.23.1.2.1.1.2,PPP-LCP-MIB::pppLqrInGoodOctets,Counter32,read-only,,mandatory,,The LQR InGoodOctets counter for this link.
.1.3.6.1.2.1.10.23.1.2.1.1.3,PPP-LCP-MIB::pppLqrLocalPeriod,INTEGER,read-only,,mandatory,,The LQR reporting period, in hundredths of a second that is in effect for the local PPP entity.
.1.3.6.1.2.1.10.23.1.2.1.1.4,PPP-LCP-MIB::pppLqrRemotePeriod,INTEGER,read-only,,mandatory,,The LQR reporting period, in hundredths of a second, that is in effect for the remote PPP entity.
.1.3.6.1.2.1.10.23.1.2.1.1.5,PPP-LCP-MIB::pppLqrOutLQRs,Counter32,read-only,,mandatory,,The value of the OutLQRs counter on the local node for the link identified by ifIndex.
.1.3.6.1.2.1.10.23.1.2.1.1.6,PPP-LCP-MIB::pppLqrInLQRs,Counter32,read-only,,mandatory,,The value of the InLQRs counter on the local node for the link identified by ifIndex.
.1.3.6.1.2.1.10.23.1.2.2,PPP-LCP-MIB::pppLqrConfigTable,,not-accessible,,mandatory,,Table containing the LQR Configuration parameters for the local PPP entity.
.1.3.6.1.2.1.10.23.1.2.2.1,PPP-LCP-MIB::pppLqrConfigEntry,,not-accessible,ifIndex,mandatory,,LQR configuration information for a particular PPP link.
.1.3.6.1.2.1.10.23.1.2.2.1.1,PPP-LCP-MIB::pppLqrConfigPeriod,INTEGER,read-write,,mandatory,,The LQR Reporting Period that the local PPP entity will attempt to negotiate with the remote entity, in units of hundredths of a second. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.1.2.2.1.2,PPP-LCP-MIB::pppLqrConfigStatus,INTEGER,read-write,,mandatory,disabled(1):enabled(2),If enabled(2) then the local node will attempt to perform LQR negotiation with the remote node. If disabled(1) then this negotiation is not performed. In any event, the local node will comply with any magic number negotiations attempted by the remote node, per the PPP specification. Changing this object will have effect when the link is next restarted. Setting this object to the value disabled(1) has the effect of invalidating the corresponding entry in the pppLqrConfigTable object. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use.
.1.3.6.1.2.1.10.23.1.2.3,PPP-LCP-MIB::pppLqrExtnsTable,,not-accessible,,mandatory,,Table containing additional LQR information for the local PPP entity.
.1.3.6.1.2.1.10.23.1.2.3.1,PPP-LCP-MIB::pppLqrExtnsEntry,,not-accessible,ifIndex,mandatory,,Extended LQR information for a particular PPP link. Assuming that this group has been implemented, a PPP link will have an entry in this table if and only if LQR Quality Monitoring has been successfully negotiated for said link.
.1.3.6.1.2.1.10.23.1.2.3.1.1,PPP-LCP-MIB::pppLqrExtnsLastReceivedLqrPacket,OCTET,read-only,,mandatory,,This object contains the most recently received LQR packet. The format of the packet is as described in the LQM Protocol specificiation. All fields of the packet, including the `save' fields, are stored in this object. The LQR packet is stored in network byte order. The LAP-B and PPP headers are not stored in this object; the first four octets of this variable contain the Magic-Number field, the second four octets contain the LastOutLQRs field and so on. The last four octets of this object contain the SaveInOctets field of the LQR packet.
.1.3.6.1.2.1.10.23.1.3,PPP-LCP-MIB::pppTests,,,,,,
.1.3.6.1.2.1.10.23.1.3.1,PPP-LCP-MIB::pppEchoTest,,,,,,
.1.3.6.1.2.1.10.23.1.3.2,PPP-LCP-MIB::pppDiscardTest,,,,,,
.1.3.6.1.2.1.10.23.2,PPP-SEC-MIB::pppSecurity,,,,,,
.1.3.6.1.2.1.10.23.2.1,PPP-SEC-MIB::pppSecurityProtocols,,,,,,
.1.3.6.1.2.1.10.23.2.1.1,PPP-SEC-MIB::pppSecurityPapProtocol,,,,,,
.1.3.6.1.2.1.10.23.2.1.2,PPP-SEC-MIB::pppSecurityChapMD5Protocol,,,,,,
.1.3.6.1.2.1.10.23.2.2,PPP-SEC-MIB::pppSecurityConfigTable,,not-accessible,,mandatory,,Table containing the configuration and preference parameters for PPP Security.
.1.3.6.1.2.1.10.23.2.2.1,PPP-SEC-MIB::pppSecurityConfigEntry,,not-accessible,pppSecurityConfigLink:pppSecurityConfigPreference,mandatory,,Security configuration information for a particular PPP link.
.1.3.6.1.2.1.10.23.2.2.1.1,PPP-SEC-MIB::pppSecurityConfigLink,INTEGER,read-write,,mandatory,,The value of ifIndex that identifies the entry in the interface table that is associated with the local PPP entity's link for which this particular security algorithm shall be attempted. A value of 0 indicates the default algorithm - i.e., this entry applies to all links for which explicit entries in the table do not exist.
.1.3.6.1.2.1.10.23.2.2.1.2,PPP-SEC-MIB::pppSecurityConfigPreference,INTEGER,read-write,,mandatory,,The relative preference of the security protocol identified by pppSecurityConfigProtocol. Security protocols with lower values of pppSecurityConfigPreference are tried before protocols with higher values of pppSecurityConfigPreference.
.1.3.6.1.2.1.10.23.2.2.1.3,PPP-SEC-MIB::pppSecurityConfigProtocol,OBJECT,read-write,,mandatory,,Identifies the security protocol to be attempted on the link identified by pppSecurityConfigLink at the preference level identified by pppSecurityConfigPreference. 
.1.3.6.1.2.1.10.23.2.2.1.4,PPP-SEC-MIB::pppSecurityConfigStatus,INTEGER,read-write,,mandatory,invalid(1):valid(2),Setting this object to the value invalid(1) has the effect of invalidating the corresponding entry in the pppSecurityConfigTable. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant pppSecurityConfigStatus object.
.1.3.6.1.2.1.10.23.2.3,PPP-SEC-MIB::pppSecuritySecretsTable,,not-accessible,,mandatory,,Table containing the identities and secrets used by the PPP authentication protocols. As this table contains secret information, it is expected that access to this table be limited to those SNMP Party-Pairs for which a privacy protocol is in use for all SNMP messages that the parties exchange. This table contains both the ID and secret pair(s) that the local PPP entity will advertise to the remote entity and the pair(s) that the local entity will expect from the remote entity. This table allows for multiple id/secret password pairs to be specified for a particular link by using the pppSecuritySecretsIdIndex object.
.1.3.6.1.2.1.10.23.2.3.1,PPP-SEC-MIB::pppSecuritySecretsEntry,,not-accessible,pppSecuritySecretsLink:pppSecuritySecretsIdIndex,mandatory,,Secret information.
.1.3.6.1.2.1.10.23.2.3.1.1,PPP-SEC-MIB::pppSecuritySecretsLink,INTEGER,read-only,,mandatory,,The link to which this ID/Secret pair applies. By convention, if the value of this object is 0 then the ID/Secret pair applies to all links.
.1.3.6.1.2.1.10.23.2.3.1.2,PPP-SEC-MIB::pppSecuritySecretsIdIndex,INTEGER,read-only,,mandatory,,A unique value for each ID/Secret pair that has been defined for use on this link. This allows multiple ID/Secret pairs to be defined for each link. How the local entity selects which pair to use is a local implementation decision.
.1.3.6.1.2.1.10.23.2.3.1.3,PPP-SEC-MIB::pppSecuritySecretsDirection,INTEGER,read-write,,mandatory,local-to-remote(1):remote-to-local(2),This object defines the direction in which a particular ID/Secret pair is valid. If this object is local-to-remote then the local PPP entity will use the ID/Secret pair when attempting to authenticate the local PPP entity to the remote PPP entity. If this object is remote-to-local then the local PPP entity will expect the ID/Secret pair to be used by the remote PPP entity when the remote PPP entity attempts to authenticate itself to the local PPP entity.
.1.3.6.1.2.1.10.23.2.3.1.4,PPP-SEC-MIB::pppSecuritySecretsProtocol,OBJECT,read-write,,mandatory,,The security protocol (e.g. CHAP or PAP) to which this ID/Secret pair applies.
.1.3.6.1.2.1.10.23.2.3.1.5,PPP-SEC-MIB::pppSecuritySecretsIdentity,OCTET,read-write,,mandatory,,The Identity of the ID/Secret pair. The actual format, semantics, and use of pppSecuritySecretsIdentity depends on the actual security protocol used. For example, if pppSecuritySecretsProtocol is pppSecurityPapProtocol then this object will contain a PAP Peer-ID. If pppSecuritySecretsProtocol is pppSecurityChapMD5Protocol then this object would contain the CHAP NAME parameter.
.1.3.6.1.2.1.10.23.2.3.1.6,PPP-SEC-MIB::pppSecuritySecretsSecret,OCTET,read-write,,mandatory,,The secret of the ID/Secret pair. The actual format, semantics, and use of pppSecuritySecretsSecret depends on the actual security protocol used. For example, if pppSecuritySecretsProtocol is pppSecurityPapProtocol then this object will contain a PAP Password. If pppSecuritySecretsProtocol is pppSecurityChapMD5Protocol then this object would contain the CHAP MD5 Secret.
.1.3.6.1.2.1.10.23.2.3.1.7,PPP-SEC-MIB::pppSecuritySecretsStatus,INTEGER,read-write,,mandatory,invalid(1):valid(2),Setting this object to the value invalid(1) has the effect of invalidating the corresponding entry in the pppSecuritySecretsTable. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant pppSecuritySecretsStatus object.
.1.3.6.1.2.1.10.23.3,PPP-IP-NCP-MIB::pppIp,,,,,,
.1.3.6.1.2.1.10.23.3.1,PPP-IP-NCP-MIB::pppIpTable,,not-accessible,,mandatory,,Table containing the IP parameters and statistics for the local PPP entity.
.1.3.6.1.2.1.10.23.3.1.1,PPP-IP-NCP-MIB::pppIpEntry,,not-accessible,ifIndex,mandatory,,IPCP status information for a particular PPP link.
.1.3.6.1.2.1.10.23.3.1.1.1,PPP-IP-NCP-MIB::pppIpOperStatus,INTEGER,read-only,,mandatory,opened(1):not-opened(2),The operational status of the IP network protocol. If the value of this object is up then the finite state machine for the IP network protocol has reached the Opened state.
.1.3.6.1.2.1.10.23.3.1.1.2,PPP-IP-NCP-MIB::pppIpLocalToRemoteCompressionProtocol,INTEGER,read-only,,mandatory,none(1):vj-tcp(2),The IP compression protocol that the local PPP-IP entity uses when sending packets to the remote PPP-IP entity. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened).
.1.3.6.1.2.1.10.23.3.1.1.3,PPP-IP-NCP-MIB::pppIpRemoteToLocalCompressionProtocol,INTEGER,read-only,,mandatory,none(1):vj-tcp(2),The IP compression protocol that the remote PPP-IP entity uses when sending packets to the local PPP-IP entity. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened).
.1.3.6.1.2.1.10.23.3.1.1.4,PPP-IP-NCP-MIB::pppIpRemoteMaxSlotId,INTEGER,read-only,,mandatory,,The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened).
.1.3.6.1.2.1.10.23.3.1.1.5,PPP-IP-NCP-MIB::pppIpLocalMaxSlotId,INTEGER,read-only,,mandatory,,The Max-Slot-Id parameter that the local node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened).
.1.3.6.1.2.1.10.23.3.2,PPP-IP-NCP-MIB::pppIpConfigTable,,not-accessible,,mandatory,,Table containing configuration variables for the IPCP for the local PPP entity.
.1.3.6.1.2.1.10.23.3.2.1,PPP-IP-NCP-MIB::pppIpConfigEntry,,not-accessible,ifIndex,mandatory,,IPCP information for a particular PPP link.
.1.3.6.1.2.1.10.23.3.2.1.1,PPP-IP-NCP-MIB::pppIpConfigAdminStatus,INTEGER,read-write,,mandatory,open(1):close(2),The immediate desired status of the IP network protocol. Setting this object to open will inject an administrative open event into the IP network protocol's finite state machine. Setting this object to close will inject an administrative close event into the IP network protocol's finite state machine.
.1.3.6.1.2.1.10.23.3.2.1.2,PPP-IP-NCP-MIB::pppIpConfigCompression,INTEGER,read-write,,mandatory,none(1):vj-tcp(2),If none(1) then the local node will not attempt to negotiate any IP Compression option. Otherwise, the local node will attempt to negotiate compression mode indicated by the enumerated value. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.23.4,PPP-BRIDGE-NCP-MIB::pppBridge,,,,,,
.1.3.6.1.2.1.10.23.4.1,PPP-BRIDGE-NCP-MIB::pppBridgeTable,,not-accessible,,mandatory,,Table containing the parameters and statistics for the local PPP entity that are related to the operation of Bridging over the PPP.
.1.3.6.1.2.1.10.23.4.1.1,PPP-BRIDGE-NCP-MIB::pppBridgeEntry,,not-accessible,ifIndex,mandatory,,Bridging information for a particular PPP link.
.1.3.6.1.2.1.10.23.4.1.1.1,PPP-BRIDGE-NCP-MIB::pppBridgeOperStatus,INTEGER,read-only,,mandatory,opened(1):not-opened(2),The operational status of the Bridge network protocol. If the value of this object is up then the finite state machine for the Bridge network protocol has reached the Opened state.
.1.3.6.1.2.1.10.23.4.1.1.2,PPP-BRIDGE-NCP-MIB::pppBridgeLocalToRemoteTinygramCompression,INTEGER,read-only,,mandatory,false(1):true(2),Indicates whether the local node will perform Tinygram Compression when sending packets to the remote entity. If false then the local entity will not perform Tinygram Compression. If true then the local entity will perform Tinygram Compression. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
.1.3.6.1.2.1.10.23.4.1.1.3,PPP-BRIDGE-NCP-MIB::pppBridgeRemoteToLocalTinygramCompression,INTEGER,read-only,,mandatory,false(1):true(2),If false(1) then the remote entity is not expected to perform Tinygram Compression. If true then the remote entity is expected to perform Tinygram Compression. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
.1.3.6.1.2.1.10.23.4.1.1.4,PPP-BRIDGE-NCP-MIB::pppBridgeLocalToRemoteLanId,INTEGER,read-only,,mandatory,false(1):true(2),Indicates whether the local node will include the LAN Identification field in transmitted packets or not. If false(1) then the local node will not transmit this field, true(2) means that the field will be transmitted. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
.1.3.6.1.2.1.10.23.4.1.1.5,PPP-BRIDGE-NCP-MIB::pppBridgeRemoteToLocalLanId,INTEGER,read-only,,mandatory,false(1):true(2),Indicates whether the remote node has indicated that it will include the LAN Identification field in transmitted packets or not. If false(1) then the field will not be transmitted, if true(2) then the field will be transmitted. The value of this object is meaningful only when the link has reached the open state (pppBridgeOperStatus is opened).
.1.3.6.1.2.1.10.23.4.2,PPP-BRIDGE-NCP-MIB::pppBridgeConfigTable,,not-accessible,,mandatory,,Table containing the parameters and statistics for the local PPP entity that are related to the operation of Bridging over the PPP.
.1.3.6.1.2.1.10.23.4.2.1,PPP-BRIDGE-NCP-MIB::pppBridgeConfigEntry,,not-accessible,ifIndex,mandatory,,Bridging Configuration information for a particular PPP link.
.1.3.6.1.2.1.10.23.4.2.1.1,PPP-BRIDGE-NCP-MIB::pppBridgeConfigAdminStatus,INTEGER,read-write,,mandatory,open(1):close(2),The immediate desired status of the Bridging network protocol. Setting this object to open will inject an administrative open event into the Bridging network protocol's finite state machine. Setting this object to close will inject an administrative close event into the Bridging network protocol's finite state machine.
.1.3.6.1.2.1.10.23.4.2.1.2,PPP-BRIDGE-NCP-MIB::pppBridgeConfigTinygram,INTEGER,read-write,,mandatory,false(1):true(2),If false then the local BNCP entity will not initiate the Tinygram Compression Option Negotiation. If true then the local BNCP entity will initiate negotiation of this option.
.1.3.6.1.2.1.10.23.4.2.1.3,PPP-BRIDGE-NCP-MIB::pppBridgeConfigRingId,INTEGER,read-write,,mandatory,false(1):true(2),If false then the local PPP Entity will not initiate a Remote Ring Identification Option negotiation. If true then the local PPP entity will intiate this negotiation. This MIB object is relevant only if the interface is for 802.5 Token Ring bridging.
.1.3.6.1.2.1.10.23.4.2.1.4,PPP-BRIDGE-NCP-MIB::pppBridgeConfigLineId,INTEGER,read-write,,mandatory,false(1):true(2),If false then the local PPP Entity is not to initiate a Line Identification Option negotiation. If true then the local PPP entity will intiate this negotiation. This MIB object is relevant only if the interface is for 802.5 Token Ring bridging.
.1.3.6.1.2.1.10.23.4.2.1.5,PPP-BRIDGE-NCP-MIB::pppBridgeConfigLanId,INTEGER,read-write,,mandatory,false(1):true(2),If false then the local BNCP entity will not initiate the LAN Identification Option Negotiation. If true then the local BNCP entity will initiate negotiation of this option.
.1.3.6.1.2.1.10.23.4.3,PPP-BRIDGE-NCP-MIB::pppBridgeMediaTable,,not-accessible,,mandatory,,Table identifying which MAC media types are enabled for the Bridging NCPs.
.1.3.6.1.2.1.10.23.4.3.1,PPP-BRIDGE-NCP-MIB::pppBridgeMediaEntry,,not-accessible,ifIndex:pppBridgeMediaMacType,mandatory,,Status of a specific MAC Type for a specific PPP Link.
.1.3.6.1.2.1.10.23.4.3.1.1,PPP-BRIDGE-NCP-MIB::pppBridgeMediaMacType,INTEGER,read-only,,mandatory,,The MAC type for which this entry in the pppBridgeMediaTable is providing status information. Valid values for this object are defined in Section 6.6 MAC Type Support Selection of RFC1220 (Bridging Point-to-Point Protocol).
.1.3.6.1.2.1.10.23.4.3.1.2,PPP-BRIDGE-NCP-MIB::pppBridgeMediaLocalStatus,INTEGER,read-only,,mandatory,accept(1):dont-accept(2),Indicates whether the local PPP Bridging Entity will accept packets of the protocol type identified in pppBridgeMediaMacType on the PPP link identified by ifIndex or not. If this object is accept then any packets of the indicated MAC type will be received and properly processed. If this object is dont- accept then received packets of the indicated MAC type will not be properly processed.
.1.3.6.1.2.1.10.23.4.3.1.3,PPP-BRIDGE-NCP-MIB::pppBridgeMediaRemoteStatus,INTEGER,read-only,,mandatory,accept(1):dont-accept(2),Indicates whether the local PPP Bridging Entity believes that the remote PPP Bridging Entity will accept packets of the protocol type identified in pppBridgeMediaMacType on the PPP link identified by ifIndex or not.
.1.3.6.1.2.1.10.23.4.4,PPP-BRIDGE-NCP-MIB::pppBridgeMediaConfigTable,,not-accessible,,mandatory,,Table identifying which MAC media types are enabled for the Bridging NCPs.
.1.3.6.1.2.1.10.23.4.4.1,PPP-BRIDGE-NCP-MIB::pppBridgeMediaConfigEntry,,not-accessible,ifIndex:pppBridgeMediaConfigMacType,mandatory,,Status of a specific MAC Type for a specific PPP Link.
.1.3.6.1.2.1.10.23.4.4.1.1,PPP-BRIDGE-NCP-MIB::pppBridgeMediaConfigMacType,INTEGER,read-write,,mandatory,,The MAC type for which this entry in the pppBridgeMediaConfigTable is providing status information. Valid values for this object are defined in Section 6.6 MAC Type Support Selection of RFC1220 (Bridging Point-to-Point Protocol).
.1.3.6.1.2.1.10.23.4.4.1.2,PPP-BRIDGE-NCP-MIB::pppBridgeMediaConfigLocalStatus,INTEGER,read-write,,mandatory,accept(1):dont-accept(2),Indicates whether the local PPP Bridging Entity should accept packets of the protocol type identified in pppBridgeMediaConfigMacType on the PPP link identified by ifIndex or not. Setting this object to the value dont-accept has the affect of invalidating the corresponding entry in the pppBridgeMediaConfigTable object. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Changing this object will have effect when the link is next restarted.
.1.3.6.1.2.1.10.30,DS3-MIB::ds3,,,,,,The is the MIB module that describes DS3 and E3 interfaces objects. Copyright (c) The Internet Society (2004). This version of this MIB module is part of RFC 3896; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.30.5,DS3-MIB::dsx3ConfigTable,,not-accessible,,current,,The DS3/E3 Configuration table.
.1.3.6.1.2.1.10.30.5.1,DS3-MIB::dsx3ConfigEntry,,not-accessible,dsx3LineIndex,current,,An entry in the DS3/E3 Configuration table.
.1.3.6.1.2.1.10.30.5.1.1,DS3-MIB::dsx3LineIndex,Integer32,read-only,,current,,This object should be made equal to ifIndex. The next paragraph describes its previous usage. Making the object equal to ifIndex allows proper use of ifStackTable. Previously, this object was the identifier of a DS3/E3 Interface on a managed device. If there is an ifEntry that is directly associated with this and only this DS3/E3 interface, it should have the same value as ifIndex. Otherwise, number the dsx3LineIndices with an unique identifier following the rules of choosing a number that is greater than ifNumber and numbering the inside interfaces (e.g., equipment side) with even numbers and outside interfaces (e.g., network side) with odd numbers.
.1.3.6.1.2.1.10.30.5.1.2,DS3-MIB::dsx3IfIndex,Integer32,read-only,,deprecated,,This value for this object is equal to the value of ifIndex from the Interfaces table of MIB II (RFC 1213).
.1.3.6.1.2.1.10.30.5.1.3,DS3-MIB::dsx3TimeElapsed,INTEGER,read-only,,current,,The number of seconds that have elapsed since the beginning of the near end current error- measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.10.30.5.1.4,DS3-MIB::dsx3ValidIntervals,INTEGER,read-only,,current,,The number of previous near end intervals for which data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15 minute near end intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.30.5.1.5,DS3-MIB::dsx3LineType,INTEGER,read-write,,current,dsx3other(1):dsx3M23(2):dsx3SYNTRAN(3):dsx3CbitParity(4):dsx3ClearChannel(5):e3other(6):e3Framed(7):e3Plcp(8):dsx3M13(9),This variable indicates the variety of DS3 C-bit or E3 application implementing this interface. The type of interface affects the interpretation of the usage and error statistics. The rate of DS3 is 44.736 Mbps and E3 is 34.368 Mbps. The dsx3ClearChannel value means that the C-bits are not used except for sending/receiving AIS. The values, in sequence, describe: TITLE: SPECIFICATION: dsx3M23 ANSI T1.107-1988 dsx3SYNTRAN ANSI T1.107-1988 dsx3CbitParity ANSI T1.107a-1990 dsx3ClearChannel ANSI T1.102-1987 e3Framed CCITT G.751 e3Plcp ETSI T/NA(91)18 dsx3M13 ANSI T1.107a-1990.
.1.3.6.1.2.1.10.30.5.1.6,DS3-MIB::dsx3LineCoding,INTEGER,read-write,,current,dsx3Other(1):dsx3B3ZS(2):e3HDB3(3),This variable describes the variety of Zero Code Suppression used on this interface, which in turn affects a number of its characteristics. dsx3B3ZS and e3HDB3 refer to the use of specified patterns of normal bits and bipolar violations which are used to replace sequences of zero bits of a specified length.
.1.3.6.1.2.1.10.30.5.1.7,DS3-MIB::dsx3SendCode,INTEGER,read-write,,current,dsx3SendNoCode(1):dsx3SendLineCode(2):dsx3SendPayloadCode(3):dsx3SendResetCode(4):dsx3SendDS1LoopCode(5):dsx3SendTestPattern(6),This variable indicates what type of code is being sent across the DS3/E3 interface by the device. (These are optional for E3 interfaces.) Setting this variable causes the interface to begin sending the code requested. The values mean: dsx3SendNoCode sending looped or normal data dsx3SendLineCode sending a request for a line loopback dsx3SendPayloadCode sending a request for a payload loopback (i.e., all DS1/E1s in a DS3/E3 frame) dsx3SendResetCode sending a loopback deactivation request dsx3SendDS1LoopCode requesting to loopback a particular DS1/E1 within a DS3/E3 frame. The DS1/E1 is indicated in dsx3Ds1ForRemoteLoop. dsx3SendTestPattern sending a test pattern.
.1.3.6.1.2.1.10.30.5.1.8,DS3-MIB::dsx3CircuitIdentifier,OCTET,read-write,,current,,This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting.
.1.3.6.1.2.1.10.30.5.1.9,DS3-MIB::dsx3LoopbackConfig,INTEGER,read-write,,current,dsx3NoLoop(1):dsx3PayloadLoop(2):dsx3LineLoop(3):dsx3OtherLoop(4):dsx3InwardLoop(5):dsx3DualLoop(6),This variable represents the desired loopback configuration of the DS3/E3 interface. The values mean: dsx3NoLoop Not in the loopback state. A device that is not capable of performing a loopback on the interface shall always return this as its value. dsx3PayloadLoop The received signal at this interface is looped through the device. Typically the received signal is looped back for retransmission after it has passed through the device's framing function. dsx3LineLoop The received signal at this interface does not go through the device (minimum penetration) but is looped back out. dsx3OtherLoop Loopbacks that are not defined here. dsx3InwardLoop The sent signal at this interface is looped back through the device. dsx3DualLoop Both dsx1LineLoop and dsx1InwardLoop will be active simultaneously.
.1.3.6.1.2.1.10.30.5.1.10,DS3-MIB::dsx3LineStatus,INTEGER,read-only,,current,,This variable indicates the Line Status of the interface. It contains loopback state information and failure state information. The dsx3LineStatus is a bit map represented as a sum, therefore, it can represent multiple failures and a loopback (see dsx3LoopbackConfig object for the type of loopback) simultaneously. The dsx3NoAlarm must be set if and only if no other flag is set. If the dsx3loopbackState bit is set, the loopback in effect can be determined from the dsx3loopbackConfig object. The various bit positions are: 1 dsx3NoAlarm No alarm present 2 dsx3RcvRAIFailure Receiving Yellow/Remote Alarm Indication 4 dsx3XmitRAIAlarm Transmitting Yellow/Remote Alarm Indication 8 dsx3RcvAIS Receiving AIS failure state 16 dsx3XmitAIS Transmitting AIS 32 dsx3LOF Receiving LOF failure state 64 dsx3LOS Receiving LOS failure state 128 dsx3LoopbackState Looping the received signal 256 dsx3RcvTestCode Receiving a Test Pattern 512 dsx3OtherFailure any line status not defined here 1024 dsx3UnavailSigState Near End in Unavailable Signal State 2048 dsx3NetEquipOOS Carrier Equipment Out of Service
.1.3.6.1.2.1.10.30.5.1.11,DS3-MIB::dsx3TransmitClockSource,INTEGER,read-write,,current,loopTiming(1):localTiming(2):throughTiming(3),The source of Transmit Clock. loopTiming indicates that the recovered receive clock is used as the transmit clock. localTiming indicates that a local clock source is used or that an external clock is attached to the box containing the interface. throughTiming indicates that transmit clock is derived from the recovered receive clock of another DS3 interface.
.1.3.6.1.2.1.10.30.5.1.12,DS3-MIB::dsx3InvalidIntervals,INTEGER,read-only,,current,, The number of intervals in the range from 0 to dsx3ValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.30.5.1.13,DS3-MIB::dsx3LineLength,INTEGER,read-write,,current,,The length of the ds3 line in meters. This object provides information for line build out circuitry if it exists and can use this object to adjust the line build out.
.1.3.6.1.2.1.10.30.5.1.14,DS3-MIB::dsx3LineStatusLastChange,TimeTicks,read-only,,current,,The value of MIB II's sysUpTime object at the time this DS3/E3 entered its current line status state. If the current state was entered prior to the last re-initialization of the proxy-agent, then this object contains a zero value.
.1.3.6.1.2.1.10.30.5.1.15,DS3-MIB::dsx3LineStatusChangeTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether dsx3LineStatusChange traps should be generated for this interface.
.1.3.6.1.2.1.10.30.5.1.16,DS3-MIB::dsx3LoopbackStatus,INTEGER,read-only,,current,,This variable represents the current state of the loopback on the DS3 interface. It contains information about loopbacks established by a manager and remotely from the far end. The dsx3LoopbackStatus is a bit map represented as a sum, therefore is can represent multiple loopbacks simultaneously. The various bit positions are: 1 dsx3NoLoopback 2 dsx3NearEndPayloadLoopback 4 dsx3NearEndLineLoopback 8 dsx3NearEndOtherLoopback 16 dsx3NearEndInwardLoopback 32 dsx3FarEndPayloadLoopback 64 dsx3FarEndLineLoopback
.1.3.6.1.2.1.10.30.5.1.17,DS3-MIB::dsx3Channelization,INTEGER,read-write,,current,disabled(1):enabledDs1(2):enabledDs2(3),Indicates whether this ds3/e3 is channelized or unchannelized. The value of enabledDs1 indicates that this is a DS3 channelized into DS1s. The value of enabledDs3 indicated that this is a DS3 channelized into DS2s. Setting this object will cause the creation or deletion of DS2 or DS1 entries in the ifTable. 
.1.3.6.1.2.1.10.30.5.1.18,DS3-MIB::dsx3Ds1ForRemoteLoop,INTEGER,read-write,,current,,Indicates which DS1/E1 on this DS3/E3 will be indicated in the remote ds1 loopback request. A value of 0 means no DS1 will be looped. A value of 29 means all DS1s/E1s will be looped.
.1.3.6.1.2.1.10.30.6,DS3-MIB::dsx3CurrentTable,,not-accessible,,current,,The DS3/E3 current table contains various statistics being collected for the current 15 minute interval.
.1.3.6.1.2.1.10.30.6.1,DS3-MIB::dsx3CurrentEntry,,not-accessible,dsx3CurrentIndex,current,,An entry in the DS3/E3 Current table.
.1.3.6.1.2.1.10.30.6.1.1,DS3-MIB::dsx3CurrentIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3/E3 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value an dsx3LineIndex object instance.
.1.3.6.1.2.1.10.30.6.1.2,DS3-MIB::dsx3CurrentPESs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Errored Seconds.
.1.3.6.1.2.1.10.30.6.1.3,DS3-MIB::dsx3CurrentPSESs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Severely Errored Seconds.
.1.3.6.1.2.1.10.30.6.1.4,DS3-MIB::dsx3CurrentSEFSs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Framing Seconds.
.1.3.6.1.2.1.10.30.6.1.5,DS3-MIB::dsx3CurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds.
.1.3.6.1.2.1.10.30.6.1.6,DS3-MIB::dsx3CurrentLCVs,Gauge32,read-only,,current,,The counter associated with the number of Line Coding Violations.
.1.3.6.1.2.1.10.30.6.1.7,DS3-MIB::dsx3CurrentPCVs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Coding Violations.
.1.3.6.1.2.1.10.30.6.1.8,DS3-MIB::dsx3CurrentLESs,Gauge32,read-only,,current,,The number of Line Errored Seconds.
.1.3.6.1.2.1.10.30.6.1.9,DS3-MIB::dsx3CurrentCCVs,Gauge32,read-only,,current,,The number of C-bit Coding Violations.
.1.3.6.1.2.1.10.30.6.1.10,DS3-MIB::dsx3CurrentCESs,Gauge32,read-only,,current,,The number of C-bit Errored Seconds.
.1.3.6.1.2.1.10.30.6.1.11,DS3-MIB::dsx3CurrentCSESs,Gauge32,read-only,,current,,The number of C-bit Severely Errored Seconds.
.1.3.6.1.2.1.10.30.7,DS3-MIB::dsx3IntervalTable,,not-accessible,,current,,The DS3/E3 Interval Table contains various statistics collected by each DS3/E3 Interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15 minute intervals. Each row in this table represents one such interval (identified by dsx3IntervalNumber) and for one specific interface (identified by dsx3IntervalIndex).
.1.3.6.1.2.1.10.30.7.1,DS3-MIB::dsx3IntervalEntry,,not-accessible,dsx3IntervalIndex:dsx3IntervalNumber,current,,An entry in the DS3/E3 Interval table.
.1.3.6.1.2.1.10.30.7.1.1,DS3-MIB::dsx3IntervalIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3/E3 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value an dsx3LineIndex object instance.
.1.3.6.1.2.1.10.30.7.1.2,DS3-MIB::dsx3IntervalNumber,INTEGER,read-only,,current,,A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes interval completed 23 hours and 45 minutes prior to interval 1.
.1.3.6.1.2.1.10.30.7.1.3,DS3-MIB::dsx3IntervalPESs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Errored Seconds.
.1.3.6.1.2.1.10.30.7.1.4,DS3-MIB::dsx3IntervalPSESs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Severely Errored Seconds.
.1.3.6.1.2.1.10.30.7.1.5,DS3-MIB::dsx3IntervalSEFSs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Framing Seconds.
.1.3.6.1.2.1.10.30.7.1.6,DS3-MIB::dsx3IntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds. This object may decrease if the occurrence of unavailable seconds occurs across an interval boundary.
.1.3.6.1.2.1.10.30.7.1.7,DS3-MIB::dsx3IntervalLCVs,Gauge32,read-only,,current,,The counter associated with the number of Line Coding Violations.
.1.3.6.1.2.1.10.30.7.1.8,DS3-MIB::dsx3IntervalPCVs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Coding Violations.
.1.3.6.1.2.1.10.30.7.1.9,DS3-MIB::dsx3IntervalLESs,Gauge32,read-only,,current,,The number of Line Errored Seconds (BPVs or illegal zero sequences).
.1.3.6.1.2.1.10.30.7.1.10,DS3-MIB::dsx3IntervalCCVs,Gauge32,read-only,,current,,The number of C-bit Coding Violations.
.1.3.6.1.2.1.10.30.7.1.11,DS3-MIB::dsx3IntervalCESs,Gauge32,read-only,,current,,The number of C-bit Errored Seconds.
.1.3.6.1.2.1.10.30.7.1.12,DS3-MIB::dsx3IntervalCSESs,Gauge32,read-only,,current,,The number of C-bit Severely Errored Seconds.
.1.3.6.1.2.1.10.30.7.1.13,DS3-MIB::dsx3IntervalValidData,INTEGER,read-only,,current,true(1):false(2), This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.30.8,DS3-MIB::dsx3TotalTable,,not-accessible,,current,,The DS3/E3 Total Table contains the cumulative sum of the various statistics for the 24 hour period preceding the current interval.
.1.3.6.1.2.1.10.30.8.1,DS3-MIB::dsx3TotalEntry,,not-accessible,dsx3TotalIndex,current,,An entry in the DS3/E3 Total table.
.1.3.6.1.2.1.10.30.8.1.1,DS3-MIB::dsx3TotalIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3/E3 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value an dsx3LineIndex object instance.
.1.3.6.1.2.1.10.30.8.1.2,DS3-MIB::dsx3TotalPESs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Errored Seconds, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.3,DS3-MIB::dsx3TotalPSESs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Severely Errored Seconds, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.4,DS3-MIB::dsx3TotalSEFSs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Framing Seconds, encountered by a DS3/E3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.5,DS3-MIB::dsx3TotalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.6,DS3-MIB::dsx3TotalLCVs,Gauge32,read-only,,current,,The counter associated with the number of Line Coding Violations encountered by a DS3/E3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.7,DS3-MIB::dsx3TotalPCVs,Gauge32,read-only,,current,,The counter associated with the number of P-bit Coding Violations, encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.8,DS3-MIB::dsx3TotalLESs,Gauge32,read-only,,current,,The number of Line Errored Seconds (BPVs or illegal zero sequences) encountered by a DS3/E3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.9,DS3-MIB::dsx3TotalCCVs,Gauge32,read-only,,current,,The number of C-bit Coding Violations encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.10,DS3-MIB::dsx3TotalCESs,Gauge32,read-only,,current,,The number of C-bit Errored Seconds encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.8.1.11,DS3-MIB::dsx3TotalCSESs,Gauge32,read-only,,current,,The number of C-bit Severely Errored Seconds encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.9,DS3-MIB::dsx3FarEndConfigTable,,not-accessible,,current,,The DS3 Far End Configuration Table contains configuration information reported in the C-bits from the remote end.
.1.3.6.1.2.1.10.30.9.1,DS3-MIB::dsx3FarEndConfigEntry,,not-accessible,dsx3FarEndLineIndex,current,,An entry in the DS3 Far End Configuration table.
.1.3.6.1.2.1.10.30.9.1.1,DS3-MIB::dsx3FarEndLineIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3 interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value an dsx3LineIndex object instance.
.1.3.6.1.2.1.10.30.9.1.2,DS3-MIB::dsx3FarEndEquipCode,OCTET,read-write,,current,,This is the Far End Equipment Identification code that describes the specific piece of equipment. It is sent within the Path Identification Message.
.1.3.6.1.2.1.10.30.9.1.3,DS3-MIB::dsx3FarEndLocationIDCode,OCTET,read-write,,current,,This is the Far End Location Identification code that describes the specific location of the equipment. It is sent within the Path Identification Message.
.1.3.6.1.2.1.10.30.9.1.4,DS3-MIB::dsx3FarEndFrameIDCode,OCTET,read-write,,current,,This is the Far End Frame Identification code that identifies where the equipment is located within a building at a given location. It is sent within the Path Identification Message.
.1.3.6.1.2.1.10.30.9.1.5,DS3-MIB::dsx3FarEndUnitCode,OCTET,read-write,,current,,This is the Far End code that identifies the equipment location within a bay. It is sent within the Path Identification Message.
.1.3.6.1.2.1.10.30.9.1.6,DS3-MIB::dsx3FarEndFacilityIDCode,OCTET,read-write,,current,,This code identifies a specific Far End DS3 path. It is sent within the Path Identification Message.
.1.3.6.1.2.1.10.30.10,DS3-MIB::dsx3FarEndCurrentTable,,not-accessible,,current,,The DS3 Far End Current table contains various statistics being collected for the current 15 minute interval. The statistics are collected from the far end block error code within the C- bits.
.1.3.6.1.2.1.10.30.10.1,DS3-MIB::dsx3FarEndCurrentEntry,,not-accessible,dsx3FarEndCurrentIndex,current,,An entry in the DS3 Far End Current table.
.1.3.6.1.2.1.10.30.10.1.1,DS3-MIB::dsx3FarEndCurrentIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3 interface to which this entry is applicable. The interface identified by a particular value of this index is identical to the interface identified by the same value of dsx3LineIndex.
.1.3.6.1.2.1.10.30.10.1.2,DS3-MIB::dsx3FarEndTimeElapsed,INTEGER,read-only,,current,,The number of seconds that have elapsed since the beginning of the far end current error-measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.10.30.10.1.3,DS3-MIB::dsx3FarEndValidIntervals,INTEGER,read-only,,current,,The number of previous far end intervals for which data was collected. The value will be 96 unless the interface was brought online within the last 24 hours, in which case the value will be the number of complete 15 minute far end intervals since the interface has been online. In the case where the agent is a proxy, it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.30.10.1.4,DS3-MIB::dsx3FarEndCurrentCESs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Errored Seconds.
.1.3.6.1.2.1.10.30.10.1.5,DS3-MIB::dsx3FarEndCurrentCSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Severely Errored Seconds.
.1.3.6.1.2.1.10.30.10.1.6,DS3-MIB::dsx3FarEndCurrentCCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Coding Violations reported via the far end block error count.
.1.3.6.1.2.1.10.30.10.1.7,DS3-MIB::dsx3FarEndCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End unavailable seconds.
.1.3.6.1.2.1.10.30.10.1.8,DS3-MIB::dsx3FarEndInvalidIntervals,INTEGER,read-only,,current,, The number of intervals in the range from 0 to dsx3FarEndValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.30.11,DS3-MIB::dsx3FarEndIntervalTable,,not-accessible,,current,,The DS3 Far End Interval Table contains various statistics collected by each DS3 interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15 minute intervals.
.1.3.6.1.2.1.10.30.11.1,DS3-MIB::dsx3FarEndIntervalEntry,,not-accessible,dsx3FarEndIntervalIndex:dsx3FarEndIntervalNumber,current,,An entry in the DS3 Far End Interval table.
.1.3.6.1.2.1.10.30.11.1.1,DS3-MIB::dsx3FarEndIntervalIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3 interface to which this entry is applicable. The interface identified by a particular value of this index is identical to the interface identified by the same value of dsx3LineIndex.
.1.3.6.1.2.1.10.30.11.1.2,DS3-MIB::dsx3FarEndIntervalNumber,INTEGER,read-only,,current,,A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes interval completed 23 hours and 45 minutes prior to interval 1.
.1.3.6.1.2.1.10.30.11.1.3,DS3-MIB::dsx3FarEndIntervalCESs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Errored Seconds encountered by a DS3 interface in one of the previous 96, individual 15 minute, intervals. In the case where the agent is a proxy and data is not available, return noSuchInstance.
.1.3.6.1.2.1.10.30.11.1.4,DS3-MIB::dsx3FarEndIntervalCSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Severely Errored Seconds.
.1.3.6.1.2.1.10.30.11.1.5,DS3-MIB::dsx3FarEndIntervalCCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Coding Violations reported via the far end block error count.
.1.3.6.1.2.1.10.30.11.1.6,DS3-MIB::dsx3FarEndIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End unavailable seconds.
.1.3.6.1.2.1.10.30.11.1.7,DS3-MIB::dsx3FarEndIntervalValidData,INTEGER,read-only,,current,true(1):false(2), This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.30.12,DS3-MIB::dsx3FarEndTotalTable,,not-accessible,,current,,The DS3 Far End Total Table contains the cumulative sum of the various statistics for the 24 hour period preceding the current interval.
.1.3.6.1.2.1.10.30.12.1,DS3-MIB::dsx3FarEndTotalEntry,,not-accessible,dsx3FarEndTotalIndex,current,,An entry in the DS3 Far End Total table.
.1.3.6.1.2.1.10.30.12.1.1,DS3-MIB::dsx3FarEndTotalIndex,Integer32,read-only,,current,,The index value which uniquely identifies the DS3 interface to which this entry is applicable. The interface identified by a particular value of this index is identical to the interface identified by the same value of dsx3LineIndex.
.1.3.6.1.2.1.10.30.12.1.2,DS3-MIB::dsx3FarEndTotalCESs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Errored Seconds encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.12.1.3,DS3-MIB::dsx3FarEndTotalCSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Severely Errored Seconds encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.12.1.4,DS3-MIB::dsx3FarEndTotalCCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End C-bit Coding Violations reported via the far end block error count encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.12.1.5,DS3-MIB::dsx3FarEndTotalUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End unavailable seconds encountered by a DS3 interface in the previous 24 hour interval. Invalid 15 minute intervals count as 0.
.1.3.6.1.2.1.10.30.13,DS3-MIB::dsx3FracTable,,not-accessible,,deprecated,,This table is deprecated in favour of using ifStackTable. Implementation of this table was optional. It was designed for those systems dividing a DS3/E3 into channels containing different data streams that are of local interest. The DS3/E3 fractional table identifies which DS3/E3 channels associated with a CSU are being used to support a logical interface, i.e., an entry in the interfaces table from the Internet- standard MIB. For example, consider a DS3 device with 4 high speed links carrying router traffic, a feed for voice, a feed for video, and a synchronous channel for a non-routed protocol. We might describe the allocation of channels, in the dsx3FracTable, as follows: dsx3FracIfIndex.2. 1 = 3 dsx3FracIfIndex.2.15 = 4 dsx3FracIfIndex.2. 2 = 3 dsx3FracIfIndex.2.16 = 6 dsx3FracIfIndex.2. 3 = 3 dsx3FracIfIndex.2.17 = 6 dsx3FracIfIndex.2. 4 = 3 dsx3FracIfIndex.2.18 = 6 dsx3FracIfIndex.2. 5 = 3 dsx3FracIfIndex.2.19 = 6 dsx3FracIfIndex.2. 6 = 3 dsx3FracIfIndex.2.20 = 6 dsx3FracIfIndex.2. 7 = 4 dsx3FracIfIndex.2.21 = 6 dsx3FracIfIndex.2. 8 = 4 dsx3FracIfIndex.2.22 = 6 dsx3FracIfIndex.2. 9 = 4 dsx3FracIfIndex.2.23 = 6 dsx3FracIfIndex.2.10 = 4 dsx3FracIfIndex.2.24 = 6 dsx3FracIfIndex.2.11 = 4 dsx3FracIfIndex.2.25 = 6 dsx3FracIfIndex.2.12 = 5 dsx3FracIfIndex.2.26 = 6 dsx3FracIfIndex.2.13 = 5 dsx3FracIfIndex.2.27 = 6 dsx3FracIfIndex.2.14 = 5 dsx3FracIfIndex.2.28 = 6 For dsx3M23, dsx3 SYNTRAN, dsx3CbitParity, and dsx3ClearChannel there are 28 legal channels, numbered 1 through 28. For e3Framed there are 16 legal channels, numbered 1 through 16. The channels (1..16) correspond directly to the equivalently numbered time-slots.
.1.3.6.1.2.1.10.30.13.1,DS3-MIB::dsx3FracEntry,,not-accessible,dsx3FracIndex:dsx3FracNumber,deprecated,,An entry in the DS3 Fractional table.
.1.3.6.1.2.1.10.30.13.1.1,DS3-MIB::dsx3FracIndex,INTEGER,read-only,,deprecated,,The index value which uniquely identifies the DS3 interface to which this entry is applicable The interface identified by a particular value of this index is the same interface as identified by the same value an dsx3LineIndex object instance.
.1.3.6.1.2.1.10.30.13.1.2,DS3-MIB::dsx3FracNumber,INTEGER,read-only,,deprecated,,The channel number for this entry.
.1.3.6.1.2.1.10.30.13.1.3,DS3-MIB::dsx3FracIfIndex,INTEGER,read-write,,deprecated,,An index value that uniquely identifies an interface. The interface identified by a particular value of this index is the same interface as identified by the same value an ifIndex object instance. If no interface is currently using a channel, the value should be zero. If a single interface occupies more than one time slot, that ifIndex value will be found in multiple time slots.
.1.3.6.1.2.1.10.30.14,DS3-MIB::ds3Conformance,,,,,,
.1.3.6.1.2.1.10.30.14.1,DS3-MIB::ds3Groups,,,,,,
.1.3.6.1.2.1.10.30.14.1.1,DS3-MIB::ds3NearEndConfigGroup,,,,,,A collection of objects providing configuration information applicable to all DS3/E3 interfaces.
.1.3.6.1.2.1.10.30.14.1.2,DS3-MIB::ds3NearEndStatisticsGroup,,,,,,A collection of objects providing statistics information applicable to all DS3/E3 interfaces.
.1.3.6.1.2.1.10.30.14.1.3,DS3-MIB::ds3FarEndGroup,,,,,,A collection of objects providing remote configuration and statistics information applicable to C-bit Parity and SYNTRAN DS3 interfaces.
.1.3.6.1.2.1.10.30.14.1.4,DS3-MIB::ds3DeprecatedGroup,,,,,,A collection of obsolete objects that may be implemented for backwards compatibility.
.1.3.6.1.2.1.10.30.14.1.5,DS3-MIB::ds3NearEndOptionalConfigGroup,,,,,,A collection of objects that may be implemented on DS3/E3 interfaces.
.1.3.6.1.2.1.10.30.14.1.6,DS3-MIB::ds3NearEndOptionalTrapGroup,,,,,,A collection of notifications that may be implemented on DS3/E3 interfaces.
.1.3.6.1.2.1.10.30.14.2,DS3-MIB::ds3Compliances,,,,,,
.1.3.6.1.2.1.10.30.14.2.1,DS3-MIB::ds3Compliance,,,,,,The compliance statement for DS3/E3 interfaces.
.1.3.6.1.2.1.10.30.15,DS3-MIB::ds3Traps,,,,,,
.1.3.6.1.2.1.10.30.15.0,DS3-MIB::anonymous#0,,,,,,
.1.3.6.1.2.1.10.30.15.0.1,DS3-MIB::dsx3LineStatusChange,,,,,,A dsx3LineStatusChange trap is sent when the value of an instance of dsx3LineStatus changes. It can be utilized by an NMS to trigger polls. When the line status change results in a lower level line status change (i.e., ds1), then no traps for the lower level are sent.
.1.3.6.1.2.1.10.31,SIP-MIB::sip,,,,,,
.1.3.6.1.2.1.10.31.1,SIP-MIB::sipL3Table,,not-accessible,,current,,This table contains SIP L3 parameters and state variables, one entry per SIPL3 interface.
.1.3.6.1.2.1.10.31.1.1,SIP-MIB::sipL3Entry,,not-accessible,sipL3Index,current,,This list contains SIP L3 parameters and state variables.
.1.3.6.1.2.1.10.31.1.1.1,SIP-MIB::sipL3Index,Integer32,read-only,,current,,The value of this object identifies the SIP L3 interface for which this entry contains management information. 
.1.3.6.1.2.1.10.31.1.1.2,SIP-MIB::sipL3ReceivedIndividualDAs,Counter32,read-only,,deprecated,,The total number of individually addressed SIP Level 3 PDUs received from the remote system across the SNI. The total includes only unerrored L3PDUs.
.1.3.6.1.2.1.10.31.1.1.3,SIP-MIB::sipL3ReceivedGAs,Counter32,read-only,,deprecated,,The total number of group addressed SIP Level 3 PDUs received from the remote system across the SNI. The total includes only unerrored L3PDUs.
.1.3.6.1.2.1.10.31.1.1.4,SIP-MIB::sipL3UnrecognizedIndividualDAs,Counter32,read-only,,deprecated,,The number of SIP Level 3 PDUs received from the remote system with invalid or unknown individual destination addresses (Destination Address Screening violations are not included). See SMDS Subscription MIB module.
.1.3.6.1.2.1.10.31.1.1.5,SIP-MIB::sipL3UnrecognizedGAs,Counter32,read-only,,deprecated,,The number of SIP Level 3 PDUs received from the remote system with invalid or unknown group addresses. (Destination Address Screening violations are not included). See SMDS Subscription MIB module.
.1.3.6.1.2.1.10.31.1.1.6,SIP-MIB::sipL3SentIndividualDAs,Counter32,read-only,,deprecated,,The number of individually addressed SIP Level 3 PDUs that have been sent by this system across the SNI.
.1.3.6.1.2.1.10.31.1.1.7,SIP-MIB::sipL3SentGAs,Counter32,read-only,,deprecated,,The number of group addressed SIP L3PDUs that have been sent by this system across the SNI.
.1.3.6.1.2.1.10.31.1.1.8,SIP-MIB::sipL3Errors,Counter32,read-only,,deprecated,,The total number of SIP Level 3 PDUs received from the remote system that were discovered to have errors (including protocol processing and bit errors but excluding addressing-related errors) and were discarded. Includes both group addressed L3PDUs and L3PDUs containing an individual destination address.
.1.3.6.1.2.1.10.31.1.1.9,SIP-MIB::sipL3InvalidSMDSAddressTypes,Counter32,read-only,,deprecated,,The number of SIP Level 3 PDUs received from the remote system that had the Source or Destination Address_Type subfields, (the four most significant bits of the 64 bit address field), not equal to the value 1100 or 1110. Also, an error is considered to have occurred if the Address_Type field for a Source Address, the four most significant bits of the 64 bits, is equal to 1110 (a group address).
.1.3.6.1.2.1.10.31.1.1.10,SIP-MIB::sipL3VersionSupport,Integer32,read-only,,current,,A value which indicates the version(s) of SIP that this interface supports. The value is a sum. This sum initially takes the value zero. For each version, V, that this interface supports, 2 raised to (V - 1) is added to the sum. For example, a port supporting versions 1 and 2 would have a value of (2^(1-1)+2^(2-1))=3. The sipL3VersionSupport is effectively a bit mask with Version 1 equal to the least significant bit (LSB).
.1.3.6.1.2.1.10.31.2,SIP-MIB::sipL2Table,,not-accessible,,current,,This table contains SIP L2PDU parameters and state variables, one entry per SIP L2 interface.
.1.3.6.1.2.1.10.31.2.1,SIP-MIB::sipL2Entry,,not-accessible,sipL2Index,current,,This list contains SIP L2 parameters and state variables.
.1.3.6.1.2.1.10.31.2.1.1,SIP-MIB::sipL2Index,Integer32,read-only,,current,,The value of this object identifies the SIP interface for which this entry contains management information.
.1.3.6.1.2.1.10.31.2.1.2,SIP-MIB::sipL2ReceivedCounts,Counter32,read-only,,current,,The number of SIP Level 2 PDUs received from the remote system across the SNI. The total includes only unerrored L2PDUs.
.1.3.6.1.2.1.10.31.2.1.3,SIP-MIB::sipL2SentCounts,Counter32,read-only,,current,,The number of SIP Level 2 PDUs that have been sent by this system across the SNI.
.1.3.6.1.2.1.10.31.2.1.4,SIP-MIB::sipL2HcsOrCRCErrors,Counter32,read-only,,current,,The number of received SIP Level 2 PDUs that were discovered to have either a Header Check Sequence error or a Payload CRC violation.
.1.3.6.1.2.1.10.31.2.1.5,SIP-MIB::sipL2PayloadLengthErrors,Counter32,read-only,,current,,The number of received SIP Level 2 PDUs that had Payload Length errors that fall in the following specifications: - SSM L2_PDU payload length field value less - than 28 octets or greater than 44 octets, - BOM or COM L2_PDU payload length field not - equal to 44 octets, - EOM L2_PDU payload length field value less - than 4 octets or greater than 44 octets.
.1.3.6.1.2.1.10.31.2.1.6,SIP-MIB::sipL2SequenceNumberErrors,Counter32,read-only,,current,,The number of received SIP Level 2 PDUs that had a sequence number within the L2PDU not equal to the expected sequence number of the SMDS SS receive process.
.1.3.6.1.2.1.10.31.2.1.7,SIP-MIB::sipL2MidCurrentlyActiveErrors,Counter32,read-only,,current,,The number of received SIP Level 2 PDUs that are BOMs for which an active receive process is already started.
.1.3.6.1.2.1.10.31.2.1.8,SIP-MIB::sipL2BomOrSSMsMIDErrors,Counter32,read-only,,current,,The number of received SIP Level 2 PDUs that are SSMs with a MID not equal to zero or are BOMs with MIDs equal to zero.
.1.3.6.1.2.1.10.31.2.1.9,SIP-MIB::sipL2EomsMIDErrors,Counter32,read-only,,current,,The number of received SIP Level 2 PDUs that are EOMs for which there is no active receive process for the MID (i.e., the receipt of an EOM which does not correspond to a BOM) OR the EOM has a MID equal to zero.
.1.3.6.1.2.1.10.31.3,SIP-MIB::sipPLCP,,,,,,
.1.3.6.1.2.1.10.31.3.1,SIP-MIB::sipDS1PLCPTable,,not-accessible,,current,,This table contains SIP DS1 PLCP parameters and state variables, one entry per SIP port.
.1.3.6.1.2.1.10.31.3.1.1,SIP-MIB::sipDS1PLCPEntry,,not-accessible,sipDS1PLCPIndex,current,,This list contains SIP DS1 PLCP parameters and state variables.
.1.3.6.1.2.1.10.31.3.1.1.1,SIP-MIB::sipDS1PLCPIndex,Integer32,read-only,,current,,The value of this object identifies the interface for which this entry contains management information. 
.1.3.6.1.2.1.10.31.3.1.1.2,SIP-MIB::sipDS1PLCPSEFSs,Counter32,read-only,,current,,A DS1 Severely Errored Framing Second (SEFS) is a count of one-second intervals containing one or more SEF events. A Severely Errored Framing (SEF) event is declared when an error in the A1 octet and an error in the A2 octet of a framing octet pair (i.e., errors in both framing octets), or two consecutive invalid and/or nonsequential Path Overhead Identifier octets are detected.
.1.3.6.1.2.1.10.31.3.1.1.3,SIP-MIB::sipDS1PLCPAlarmState,INTEGER,read-only,,current,noAlarm(1):receivedFarEndAlarm(2):incomingLOF(3),This variable indicates if there is an alarm present for the DS1 PLCP. The value receivedFarEndAlarm means that the DS1 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS1 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. See TR-TSV-000773 for a description of alarm states.
.1.3.6.1.2.1.10.31.3.1.1.4,SIP-MIB::sipDS1PLCPUASs,Counter32,read-only,,current,,The counter associated with the number of Unavailable Seconds, as defined by TR-TSV-000773, encountered by the PLCP.
.1.3.6.1.2.1.10.31.3.2,SIP-MIB::sipDS3PLCPTable,,not-accessible,,current,,This table contains SIP DS3 PLCP parameters and state variables, one entry per SIP port.
.1.3.6.1.2.1.10.31.3.2.1,SIP-MIB::sipDS3PLCPEntry,,not-accessible,sipDS3PLCPIndex,current,,This list contains SIP DS3 PLCP parameters and state variables.
.1.3.6.1.2.1.10.31.3.2.1.1,SIP-MIB::sipDS3PLCPIndex,Integer32,read-only,,current,,The value of this object identifies the interface for which this entry contains management information. 
.1.3.6.1.2.1.10.31.3.2.1.2,SIP-MIB::sipDS3PLCPSEFSs,Counter32,read-only,,current,,A DS3 Severely Errored Framing Second (SEFS) is a count of one-second intervals containing one or more SEF events. A Severely Errored Framing (SEF) event is declared when an error in the A1 octet and an error in the A2 octet of a framing octet pair (i.e., errors in both framing octets), or two consecutive invalid and/or nonsequential Path Overhead Identifier octets are detected.
.1.3.6.1.2.1.10.31.3.2.1.3,SIP-MIB::sipDS3PLCPAlarmState,INTEGER,read-only,,current,noAlarm(1):receivedFarEndAlarm(2):incomingLOF(3),This variable indicates if there is an alarm present for the DS3 PLCP. The value receivedFarEndAlarm means that the DS3 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS3 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. See TR-TSV-000773 for a description of alarm states.
.1.3.6.1.2.1.10.31.3.2.1.4,SIP-MIB::sipDS3PLCPUASs,Counter32,read-only,,current,,The counter associated with the number of Unavailable Seconds, as defined by TR-TSV-000773, encountered by the PLCP.
.1.3.6.1.2.1.10.31.4,SIP-MIB::smdsApplications,,,,,,
.1.3.6.1.2.1.10.31.4.1,SIP-MIB::ipOverSMDS,,,,,,
.1.3.6.1.2.1.10.31.4.1.1,SIP-MIB::ipOverSMDSTable,,not-accessible,,current,,The table of addressing information relevant to this entity's IP addresses.
.1.3.6.1.2.1.10.31.4.1.1.1,SIP-MIB::ipOverSMDSEntry,,not-accessible,ipOverSMDSIndex:ipOverSMDSAddress,current,,The addressing information for one of this entity's IP addresses.
.1.3.6.1.2.1.10.31.4.1.1.1.1,SIP-MIB::ipOverSMDSIndex,Integer32,read-only,,current,,The value of this object identifies the interface for which this entry contains management information. 
.1.3.6.1.2.1.10.31.4.1.1.1.2,SIP-MIB::ipOverSMDSAddress,IpAddress,read-only,,current,,The IP address to which this entry's addressing information pertains.
.1.3.6.1.2.1.10.31.4.1.1.1.3,SIP-MIB::ipOverSMDSHA,OCTET,read-only,,current,,The SMDS Individual address of the IP station.
.1.3.6.1.2.1.10.31.4.1.1.1.4,SIP-MIB::ipOverSMDSLISGA,OCTET,read-only,,current,,The SMDS Group Address that has been configured to identify the SMDS Subscriber-Network Interfaces (SNIs) of all members of the Logical IP Subnetwork (LIS) connected to the network supporting SMDS.
.1.3.6.1.2.1.10.31.4.1.1.1.5,SIP-MIB::ipOverSMDSARPReq,OCTET,read-only,,current,,The SMDS address (individual or group) to which ARP Requests are to be sent.
.1.3.6.1.2.1.10.31.5,SIP-MIB::smdsCarrierSelection,,,,,,
.1.3.6.1.2.1.10.31.6,SIP-MIB::sipErrorLog,,,,,,
.1.3.6.1.2.1.10.31.6.1,SIP-MIB::sipL3PDUErrorTable,,not-accessible,,current,,A table that contains the latest occurrence of the following syntactical SIP L3PDU errors: - Destination Address Field Format Error, The following pertains to the 60 least significant bits of the 64 bit address field. The 60 bits contained in the address subfield can be used to represent addresses up to 15 decimal digits. Each decimal digit shall be encoded into four bits using Binary Coded Decimal (BCD), with the most significant digit occurring left-most. If not all 15 digits are required, then the remainder of this field shall be padded on the right with bits set to one. An error is considered to have occurred: a). if the first four bits of the address subfield are not BCD, OR b). if the first four bits of the address subfield are populated with the country code value 0001, AND the 40 bits which follow are not Binary Coded Decimal (BCD) encoded values of the 10 digit addresses, OR the remaining 16 least significant bits are not populated with 1's, OR c). if the address subfield is not correct according to another numbering plan which is dependent upon the carrier assigning the numbers and offering SMDS. - Source Address Field Format Error, The description of this parameter is the same as the description of the Destination Address Field Format Error. - Invalid BAsize Field Value, An error is considered to have occurred when the BAsize field of an SIP L3PDU contains a value less that 32, greater than 9220 octets without the CRC32 field present, greater than 9224 octets with the CRC32 field present, or not equal to a multiple of 4 octets, - Invalid Header Extension Length Field Value, An error is considered to have occurred when the Header Extension Length field value is not equal 3. - Invalid Header Extension - Element Length, An error is considered to have occurred when the Header Extension - Element Length is greater than 12. - Invalid Header Extension - Version Element Position, Length, or Value, An error is considered to have occurred when a Version element with Length=3, Type=0, and Value=1 does not appear first within the Header Extension, or an element Type=0 appears somewhere other than within the first three octets in the Header Extension. - Invalid Header Extension - Carrier Selection Element Position, Length, Value or Format, An error is considered to have occurred when a Carrier Selection element does not appear second within the Header Extension, if the Element Type does not equal 1, the Element Length does not equal 4, 6, or 8, the Element Value field is not four BCD encoded decimal digits used in specifying the Carrier Identification Code (CIC), or the identified CIC code is invalid. - Header Extension PAD Error An error is considered to have occurred when the Header Extension PAD is 9 octets in length, or if the Header Extension PAD is greater than zero octets in length and the Header Extension PAD does not follow all Header Extension elements or does not begin with at least one octet of all zeros. - BEtag Mismatch Error, An error is considered to have occurred when the Beginning-End Tags in the SIP L3PDU header and trailer are not equal. - BAsize Field not equal to Length Field Error, An error is considered to have occurred when the value of the BAsize Field does not equal the value of the Length Field. - Incorrect Length Error, and An error is considered to have occurred when the the Length field value is not equal to the portion of the SIP L3PDU which extends from the Destination Address field up to and including the CRC32 f
.1.3.6.1.2.1.10.31.6.1.1,SIP-MIB::sipL3PDUErrorEntry,,not-accessible,sipL3PDUErrorIndex:sipL3PDUErrorType,current,,An entry in the service disagreement table.
.1.3.6.1.2.1.10.31.6.1.1.1,SIP-MIB::sipL3PDUErrorIndex,Integer32,read-only,,current,,The value of this object identifies the interface for which this entry contains management information.
.1.3.6.1.2.1.10.31.6.1.1.2,SIP-MIB::sipL3PDUErrorType,INTEGER,read-only,,current,erroredDAFieldFormat(1):erroredSAFieldFormat(2):invalidBAsizeFieldValue(3):invalidHdrExtLength(4):invalidHdrExtElementLength(5):invalidHdrExtVersionElementPositionLenthOrValue(6):invalidHdrExtCarSelectElementPositionLenghtValueOrFormat(7):hePADError(8):beTagMismatch(9):baSizeFieldNotEqualToLengthField(10):incorrectLength(11):mriTimeout(12),The type of error.
.1.3.6.1.2.1.10.31.6.1.1.3,SIP-MIB::sipL3PDUErrorSA,OCTET,read-only,,current,,A rejected SMDS source address.
.1.3.6.1.2.1.10.31.6.1.1.4,SIP-MIB::sipL3PDUErrorDA,OCTET,read-only,,current,,A rejected SMDS destination address.
.1.3.6.1.2.1.10.31.6.1.1.5,SIP-MIB::sipL3PDUErrorTimeStamp,TimeTicks,read-only,,current,,The timestamp for the service disagreement. The timestamp contains the value of sysUpTime at the latest occurrence of this type of service disagreement. See textual description under sipL3PDUErrorTable for boundary conditions.
.1.3.6.1.2.1.10.32,FRAME-RELAY-DTE-MIB::frameRelayDTE,,,,,,The MIB module to describe the use of a Frame Relay interface by a DTE.
.1.3.6.1.2.1.10.32.0,FRAME-RELAY-DTE-MIB::frameRelayTraps,,,,,,
.1.3.6.1.2.1.10.32.0.1,FRAME-RELAY-DTE-MIB::frDLCIStatusChange,,,,,,This trap indicates that the indicated Virtual Circuit has changed state. It has either been created or invalidated, or has toggled between the active and inactive states. If, however, the reason for the state change is due to the DLCMI going down, per-DLCI traps should not be generated.
.1.3.6.1.2.1.10.32.1,FRAME-RELAY-DTE-MIB::frDlcmiTable,,not-accessible,,current,,The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.
.1.3.6.1.2.1.10.32.1.1,FRAME-RELAY-DTE-MIB::frDlcmiEntry,,not-accessible,frDlcmiIfIndex,current,,The Parameters for a particular Data Link Connection Management Interface.
.1.3.6.1.2.1.10.32.1.1.1,FRAME-RELAY-DTE-MIB::frDlcmiIfIndex,Integer32,read-only,,current,,The ifIndex value of the corresponding ifEntry.
.1.3.6.1.2.1.10.32.1.1.2,FRAME-RELAY-DTE-MIB::frDlcmiState,INTEGER,read-create,,current,noLmiConfigured(1):lmiRev1(2):ansiT1617D(3):ansiT1617B(4):itut933A(5):ansiT1617D1994(6),This variable states which Data Link Connection Management scheme is active (and by implication, what DLCI it uses) on the Frame Relay interface.
.1.3.6.1.2.1.10.32.1.1.3,FRAME-RELAY-DTE-MIB::frDlcmiAddress,INTEGER,read-create,,current,q921(1):q922March90(2):q922November90(3):q922(4),This variable states which address format is in use on the Frame Relay interface.
.1.3.6.1.2.1.10.32.1.1.4,FRAME-RELAY-DTE-MIB::frDlcmiAddressLen,INTEGER,read-create,,current,twoOctets(2):threeOctets(3):fourOctets(4),This variable states the address length in octets. In the case of Q922 format, the length indicates the entire length of the address including the control portion.
.1.3.6.1.2.1.10.32.1.1.5,FRAME-RELAY-DTE-MIB::frDlcmiPollingInterval,Integer32,read-create,,current,,This is the number of seconds between successive status enquiry messages.
.1.3.6.1.2.1.10.32.1.1.6,FRAME-RELAY-DTE-MIB::frDlcmiFullEnquiryInterval,Integer32,read-create,,current,,Number of status enquiry intervals that pass before issuance of a full status enquiry message.
.1.3.6.1.2.1.10.32.1.1.7,FRAME-RELAY-DTE-MIB::frDlcmiErrorThreshold,Integer32,read-create,,current,,This is the maximum number of unanswered Status Enquiries the equipment shall accept before declaring the interface down.
.1.3.6.1.2.1.10.32.1.1.8,FRAME-RELAY-DTE-MIB::frDlcmiMonitoredEvents,Integer32,read-create,,current,,This is the number of status polling intervals over which the error threshold is counted. For example, if within 'MonitoredEvents' number of events the station receives 'ErrorThreshold' number of errors, the interface is marked as down.
.1.3.6.1.2.1.10.32.1.1.9,FRAME-RELAY-DTE-MIB::frDlcmiMaxSupportedVCs,Integer32,read-create,,current,,The maximum number of Virtual Circuits allowed for this interface. Usually dictated by the Frame Relay network. In response to a SET, if a value less than zero or higher than the agent's maximal capability is configured, the agent should respond badValue
.1.3.6.1.2.1.10.32.1.1.10,FRAME-RELAY-DTE-MIB::frDlcmiMulticast,INTEGER,read-create,,current,nonBroadcast(1):broadcast(2),This indicates whether the Frame Relay interface is using a multicast service.
.1.3.6.1.2.1.10.32.1.1.11,FRAME-RELAY-DTE-MIB::frDlcmiStatus,INTEGER,read-only,,current,running(1):fault(2):initializing(3),This indicates the status of the Frame Relay interface as determined by the performance of the dlcmi. If no dlcmi is running, the Frame Relay interface will stay in the running state indefinitely.
.1.3.6.1.2.1.10.32.1.1.12,FRAME-RELAY-DTE-MIB::frDlcmiRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),SNMP Version 2 Row Status Variable. Writable objects in the table may be written in any RowStatus state.
.1.3.6.1.2.1.10.32.2,FRAME-RELAY-DTE-MIB::frCircuitTable,,not-accessible,,current,,A table containing information about specific Data Link Connections (DLC) or virtual circuits.
.1.3.6.1.2.1.10.32.2.1,FRAME-RELAY-DTE-MIB::frCircuitEntry,,not-accessible,frCircuitIfIndex:frCircuitDlci,current,,The information regarding a single Data Link Connection. Discontinuities in the counters contained in this table are indicated by the value in frCircuitCreationTime.
.1.3.6.1.2.1.10.32.2.1.1,FRAME-RELAY-DTE-MIB::frCircuitIfIndex,Integer32,read-only,,current,,The ifIndex Value of the ifEntry this virtual circuit is layered onto.
.1.3.6.1.2.1.10.32.2.1.2,FRAME-RELAY-DTE-MIB::frCircuitDlci,Integer32,read-only,,current,,The Data Link Connection Identifier for this virtual circuit.
.1.3.6.1.2.1.10.32.2.1.3,FRAME-RELAY-DTE-MIB::frCircuitState,INTEGER,read-create,,current,invalid(1):active(2):inactive(3),Indicates whether the particular virtual circuit is operational. In the absence of a Data Link Connection Management Interface, virtual circuit entries (rows) may be created by setting virtual circuit state to 'active', or deleted by changing Circuit state to 'invalid'. Whether or not the row actually disappears is left to the implementation, so this object may actually read as 'invalid' for some arbitrary length of time. It is also legal to set the state of a virtual circuit to 'inactive' to temporarily disable a given circuit. The use of 'invalid' is deprecated in this SNMP Version 2 MIB, in favor of frCircuitRowStatus.
.1.3.6.1.2.1.10.32.2.1.4,FRAME-RELAY-DTE-MIB::frCircuitReceivedFECNs,Counter32,read-only,,current,,Number of frames received from the network indicating forward congestion since the virtual circuit was created. This occurs when the remote DTE sets the FECN flag, or when a switch in the network enqueues the frame to a trunk whose transmission queue is congested.
.1.3.6.1.2.1.10.32.2.1.5,FRAME-RELAY-DTE-MIB::frCircuitReceivedBECNs,Counter32,read-only,,current,,Number of frames received from the network indicating backward congestion since the virtual circuit was created. This occurs when the remote DTE sets the BECN flag, or when a switch in the network receives the frame from a trunk whose transmission queue is congested.
.1.3.6.1.2.1.10.32.2.1.6,FRAME-RELAY-DTE-MIB::frCircuitSentFrames,Counter32,read-only,,current,,The number of frames sent from this virtual circuit since it was created.
.1.3.6.1.2.1.10.32.2.1.7,FRAME-RELAY-DTE-MIB::frCircuitSentOctets,Counter32,read-only,,current,,The number of octets sent from this virtual circuit since it was created. Octets counted are the full frame relay header and the payload, but do not include the flag characters or CRC.
.1.3.6.1.2.1.10.32.2.1.8,FRAME-RELAY-DTE-MIB::frCircuitReceivedFrames,Counter32,read-only,,current,,Number of frames received over this virtual circuit since it was created.
.1.3.6.1.2.1.10.32.2.1.9,FRAME-RELAY-DTE-MIB::frCircuitReceivedOctets,Counter32,read-only,,current,,Number of octets received over this virtual circuit since it was created. Octets counted include the full frame relay header, but do not include the flag characters or the CRC.
.1.3.6.1.2.1.10.32.2.1.10,FRAME-RELAY-DTE-MIB::frCircuitCreationTime,TimeTicks,read-only,,current,,The value of sysUpTime when the virtual circuit was created, whether by the Data Link Connection Management Interface or by a SetRequest.
.1.3.6.1.2.1.10.32.2.1.11,FRAME-RELAY-DTE-MIB::frCircuitLastTimeChange,TimeTicks,read-only,,current,,The value of sysUpTime when last there was a change in the virtual circuit state
.1.3.6.1.2.1.10.32.2.1.12,FRAME-RELAY-DTE-MIB::frCircuitCommittedBurst,Integer32,read-create,,current,,This variable indicates the maximum amount of data, in bits, that the network agrees to transfer under normal conditions, during the measurement interval.
.1.3.6.1.2.1.10.32.2.1.13,FRAME-RELAY-DTE-MIB::frCircuitExcessBurst,Integer32,read-create,,current,,This variable indicates the maximum amount of uncommitted data bits that the network will attempt to deliver over the measurement interval. By default, if not configured when creating the entry, the Excess Information Burst Size is set to the value of ifSpeed.
.1.3.6.1.2.1.10.32.2.1.14,FRAME-RELAY-DTE-MIB::frCircuitThroughput,Integer32,read-create,,current,,Throughput is the average number of 'Frame Relay Information Field' bits transferred per second across a user network interface in one direction, measured over the measurement interval. If the configured committed burst rate and throughput are both non-zero, the measurement interval, T, is T=frCircuitCommittedBurst/frCircuitThroughput. If the configured committed burst rate and throughput are both zero, the measurement interval, T, is T=frCircuitExcessBurst/ifSpeed.
.1.3.6.1.2.1.10.32.2.1.15,FRAME-RELAY-DTE-MIB::frCircuitMulticast,INTEGER,read-create,,current,unicast(1):oneWay(2):twoWay(3):nWay(4),This indicates whether this VC is used as a unicast VC (i.e. not multicast) or the type of multicast service subscribed to
.1.3.6.1.2.1.10.32.2.1.16,FRAME-RELAY-DTE-MIB::frCircuitType,INTEGER,read-only,,current,static(1):dynamic(2),Indication of whether the VC was manually created (static), or dynamically created (dynamic) via the data link control management interface.
.1.3.6.1.2.1.10.32.2.1.17,FRAME-RELAY-DTE-MIB::frCircuitDiscards,Counter32,read-only,,current,,The number of inbound frames dropped because of format errors, or because the VC is inactive.
.1.3.6.1.2.1.10.32.2.1.18,FRAME-RELAY-DTE-MIB::frCircuitReceivedDEs,Counter32,read-only,,current,,Number of frames received from the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the remote DTE sets the DE flag, or when in remote DTE's switch detects that the frame was received as Excess Burst data.
.1.3.6.1.2.1.10.32.2.1.19,FRAME-RELAY-DTE-MIB::frCircuitSentDEs,Counter32,read-only,,current,,Number of frames sent to the network indicating that they were eligible for discard since the virtual circuit was created. This occurs when the local DTE sets the DE flag, indicating that during Network congestion situations those frames should be discarded in preference of other frames sent without the DE bit set.
.1.3.6.1.2.1.10.32.2.1.20,FRAME-RELAY-DTE-MIB::frCircuitLogicalIfIndex,Integer32,read-create,,current,,Normally the same value as frDlcmiIfIndex, but different when an implementation associates a virtual ifEntry with a DLC or set of DLCs in order to associate higher layer objects such as the ipAddrEntry with a subset of the virtual circuits on a Frame Relay interface. The type of such ifEntries is defined by the higher layer object; for example, if PPP/Frame Relay is implemented, the ifType of this ifEntry would be PPP. If it is not so defined, as would be the case with an ipAddrEntry, it should be of type Other.
.1.3.6.1.2.1.10.32.2.1.21,FRAME-RELAY-DTE-MIB::frCircuitRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or destroy an existing row in the manner described in the definition of the RowStatus textual convention. Writable objects in the table may be written in any RowStatus state.
.1.3.6.1.2.1.10.32.3,FRAME-RELAY-DTE-MIB::frErrTable,,not-accessible,,current,,A table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.
.1.3.6.1.2.1.10.32.3.1,FRAME-RELAY-DTE-MIB::frErrEntry,,not-accessible,frErrIfIndex,current,,The error information for a single frame relay interface.
.1.3.6.1.2.1.10.32.3.1.1,FRAME-RELAY-DTE-MIB::frErrIfIndex,Integer32,read-only,,current,,The ifIndex Value of the corresponding ifEntry.
.1.3.6.1.2.1.10.32.3.1.2,FRAME-RELAY-DTE-MIB::noErrorSinceReset:,INTEGER,read-only,,current,unknownError(1):receiveShort(2):receiveLong(3):illegalAddress(4):unknownAddress(5):dlcmiProtoErr(6):dlcmiUnknownIE(7):dlcmiSequenceErr(8):dlcmiUnknownRpt(9):noErrorSinceReset(10),The type of error that was last seen on this interface: demultiplexing - the address field was incomplete, or for virtual circuits using Multiprotocol over Frame Relay, the protocol identifier was missing or incomplete. interface. active or administratively disabled. interpret link maintenance frame. Element type which is not valid for the configured link maintenance protocol. number other than the expected value. Information Element whose value was not valid for the configured link maintenance protocol. cold start or warm start.
.1.3.6.1.2.1.10.32.3.1.3,FRAME-RELAY-DTE-MIB::frErrData,OCTET,read-only,,current,,An octet string containing as much of the error packet as possible. As a minimum, it must contain the Q.922 Address or as much as was delivered. It is desirable to include all header and demultiplexing information.
.1.3.6.1.2.1.10.32.3.1.4,FRAME-RELAY-DTE-MIB::frErrTime,TimeTicks,read-only,,current,,The value of sysUpTime at which the error was detected.
.1.3.6.1.2.1.10.32.3.1.5,FRAME-RELAY-DTE-MIB::frErrFaults,Counter32,read-only,,current,,The number of times the interface has gone down since it was initialized.
.1.3.6.1.2.1.10.32.3.1.6,FRAME-RELAY-DTE-MIB::frErrFaultTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time when the interface was taken down due to excessive errors. Excessive errors is defined as the time when a DLCMI exceeds the frDlcmiErrorThreshold number of errors within frDlcmiMonitoredEvents. See FrDlcmiEntry for further details.
.1.3.6.1.2.1.10.32.4,FRAME-RELAY-DTE-MIB::frameRelayTrapControl,,,,,,
.1.3.6.1.2.1.10.32.4.1,FRAME-RELAY-DTE-MIB::frTrapState,INTEGER,read-write,,current,enabled(1):disabled(2),This variable indicates whether the system produces the frDLCIStatusChange trap.
.1.3.6.1.2.1.10.32.4.2,FRAME-RELAY-DTE-MIB::frTrapMaxRate,Integer32,read-write,,current,,This variable indicates the number of milliseconds that must elapse between trap emissions. If events occur more rapidly, the impementation may simply fail to trap, or may queue traps until an appropriate time.
.1.3.6.1.2.1.10.32.6,FRAME-RELAY-DTE-MIB::frConformance,,,,,,
.1.3.6.1.2.1.10.32.6.1,FRAME-RELAY-DTE-MIB::frGroups,,,,,,
.1.3.6.1.2.1.10.32.6.1.1,FRAME-RELAY-DTE-MIB::frPortGroup,,,,,,The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface.
.1.3.6.1.2.1.10.32.6.1.2,FRAME-RELAY-DTE-MIB::frCircuitGroup,,,,,,The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface.
.1.3.6.1.2.1.10.32.6.1.3,FRAME-RELAY-DTE-MIB::frTrapGroup,,,,,,The objects necessary to control a Frame Relay Interface's notification messages.
.1.3.6.1.2.1.10.32.6.1.4,FRAME-RELAY-DTE-MIB::frErrGroup,,,,,,Objects designed to assist in debugging Frame Relay Interfaces.
.1.3.6.1.2.1.10.32.6.1.5,FRAME-RELAY-DTE-MIB::frNotificationGroup,,,,,,Traps which may be used to enhance event driven management of the interface.
.1.3.6.1.2.1.10.32.6.1.6,FRAME-RELAY-DTE-MIB::frPortGroup0,,,,,,The objects necessary to control the Link Management Interface for a Frame Relay Interface as well as maintain the error statistics on this interface from RFC 1315.
.1.3.6.1.2.1.10.32.6.1.7,FRAME-RELAY-DTE-MIB::frCircuitGroup0,,,,,,The objects necessary to control the Virtual Circuits layered onto a Frame Relay Interface from RFC 1315.
.1.3.6.1.2.1.10.32.6.1.8,FRAME-RELAY-DTE-MIB::frErrGroup0,,,,,,Objects designed to assist in debugging Frame Relay Interfaces from RFC 1315.
.1.3.6.1.2.1.10.32.6.1.9,FRAME-RELAY-DTE-MIB::frTrapGroup0,,,,,,The objects necessary to control a Frame Relay Interface's notification messages from RFC 1315.
.1.3.6.1.2.1.10.32.6.2,FRAME-RELAY-DTE-MIB::frCompliances,,,,,,
.1.3.6.1.2.1.10.32.6.2.1,FRAME-RELAY-DTE-MIB::frCompliance,,,,,,The compliance statement 
.1.3.6.1.2.1.10.32.6.2.2,FRAME-RELAY-DTE-MIB::frCompliance0,,,,,,The compliance statement for objects and the trap defined in RFC 1315.
.1.3.6.1.2.1.10.33,RS-232-MIB::rs232,,,,,,The MIB module for RS-232-like hardware devices.
.1.3.6.1.2.1.10.33.1,RS-232-MIB::rs232Number,Integer32,read-only,,current,,The number of ports (regardless of their current state) in the RS-232-like general port table.
.1.3.6.1.2.1.10.33.2,RS-232-MIB::rs232PortTable,,not-accessible,,current,,A list of port entries. The number of entries is given by the value of rs232Number.
.1.3.6.1.2.1.10.33.2.1,RS-232-MIB::rs232PortEntry,,not-accessible,rs232PortIndex,current,,Status and parameter values for a port.
.1.3.6.1.2.1.10.33.2.1.1,RS-232-MIB::rs232PortIndex,Integer32,read-only,,current,,The value of ifIndex for the port. By convention and if possible, hardware port numbers map directly to external connectors. The value for each port must remain constant at least from one re-initialization of the network management agent to the next.
.1.3.6.1.2.1.10.33.2.1.2,RS-232-MIB::rs232PortType,INTEGER,read-only,,current,other(1):rs232(2):rs422(3):rs423(4):v35(5):x21(6),The port's hardware type.
.1.3.6.1.2.1.10.33.2.1.3,RS-232-MIB::rs232PortInSigNumber,Integer32,read-only,,current,,The number of input signals for the port in the input signal table (rs232PortInSigTable). The table contains entries only for those signals the software can detect and that are useful to observe.
.1.3.6.1.2.1.10.33.2.1.4,RS-232-MIB::rs232PortOutSigNumber,Integer32,read-only,,current,,The number of output signals for the port in the output signal table (rs232PortOutSigTable). The table contains entries only for those signals the software can assert and that are useful to observe.
.1.3.6.1.2.1.10.33.2.1.5,RS-232-MIB::rs232PortInSpeed,Integer32,read-write,,current,,The port's input speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on most implementations.
.1.3.6.1.2.1.10.33.2.1.6,RS-232-MIB::rs232PortOutSpeed,Integer32,read-write,,current,,The port's output speed in bits per second. Note that non-standard values, such as 9612, are probably not allowed on most implementations.
.1.3.6.1.2.1.10.33.2.1.7,RS-232-MIB::rs232PortInFlowType,INTEGER,read-write,,current,none(1):ctsRts(2):dsrDtr(3),The port's type of input flow control. 'none' indicates no flow control at this level. 'ctsRts' and 'dsrDtr' indicate use of the indicated hardware signals.
.1.3.6.1.2.1.10.33.2.1.8,RS-232-MIB::rs232PortOutFlowType,INTEGER,read-write,,current,none(1):ctsRts(2):dsrDtr(3),The port's type of output flow control. 'none' indicates no flow control at this level. 'ctsRts' and 'dsrDtr' indicate use of the indicated hardware signals.
.1.3.6.1.2.1.10.33.3,RS-232-MIB::rs232AsyncPortTable,,not-accessible,,current,,A list of asynchronous port entries. Entries need not exist for synchronous ports.
.1.3.6.1.2.1.10.33.3.1,RS-232-MIB::rs232AsyncPortEntry,,not-accessible,rs232AsyncPortIndex,current,,Status and parameter values for an asynchronous port.
.1.3.6.1.2.1.10.33.3.1.1,RS-232-MIB::rs232AsyncPortIndex,Integer32,read-only,,current,,A unique value for each port. Its value is the same as rs232PortIndex for the port.
.1.3.6.1.2.1.10.33.3.1.2,RS-232-MIB::rs232AsyncPortBits,INTEGER,read-write,,current,,The port's number of bits in a character.
.1.3.6.1.2.1.10.33.3.1.3,RS-232-MIB::rs232AsyncPortStopBits,INTEGER,read-write,,current,one(1):two(2):oneAndHalf(3):dynamic(4),The port's number of stop bits.
.1.3.6.1.2.1.10.33.3.1.4,RS-232-MIB::rs232AsyncPortParity,INTEGER,read-write,,current,none(1):odd(2):even(3):mark(4):space(5),The port's sense of a character parity bit.
.1.3.6.1.2.1.10.33.3.1.5,RS-232-MIB::rs232AsyncPortAutobaud,INTEGER,read-write,,current,enabled(1):disabled(2),A control for the port's ability to automatically sense input speed. When rs232PortAutoBaud is 'enabled', a port may autobaud to values different from the set values for speed, parity, and character size. As a result a network management system may temporarily observe values different from what was previously set.
.1.3.6.1.2.1.10.33.3.1.6,RS-232-MIB::rs232AsyncPortParityErrs,Counter32,read-only,,current,,Total number of characters with a parity error, input from the port since system re-initialization and while the port state was 'up' or 'test'.
.1.3.6.1.2.1.10.33.3.1.7,RS-232-MIB::rs232AsyncPortFramingErrs,Counter32,read-only,,current,,Total number of characters with a framing error, input from the port since system re-initialization and while the port state was 'up' or 'test'.
.1.3.6.1.2.1.10.33.3.1.8,RS-232-MIB::rs232AsyncPortOverrunErrs,Counter32,read-only,,current,,Total number of characters with an overrun error, input from the port since system re-initialization and while the port state was 'up' or 'test'.
.1.3.6.1.2.1.10.33.4,RS-232-MIB::rs232SyncPortTable,,not-accessible,,current,,A list of asynchronous port entries. Entries need not exist for synchronous ports.
.1.3.6.1.2.1.10.33.4.1,RS-232-MIB::rs232SyncPortEntry,,not-accessible,rs232SyncPortIndex,current,,Status and parameter values for a synchronous port.
.1.3.6.1.2.1.10.33.4.1.1,RS-232-MIB::rs232SyncPortIndex,Integer32,read-only,,current,,A unique value for each port. Its value is the same as rs232PortIndex for the port.
.1.3.6.1.2.1.10.33.4.1.2,RS-232-MIB::rs232SyncPortClockSource,INTEGER,read-write,,current,internal(1):external(2):split(3),Source of the port's bit rate clock. 'split' means the tranmit clock is internal and the receive clock is external.
.1.3.6.1.2.1.10.33.4.1.3,RS-232-MIB::rs232SyncPortFrameCheckErrs,Counter32,read-only,,current,,Total number of frames with an invalid frame check sequence, input from the port since system re-initialization and while the port state was 'up' or 'test'.
.1.3.6.1.2.1.10.33.4.1.4,RS-232-MIB::rs232SyncPortTransmitUnderrunErrs,Counter32,read-only,,current,,Total number of frames that failed to be transmitted on the port since system re-initialization and while the port state was 'up' or 'test' because data was not available to the transmitter in time.
.1.3.6.1.2.1.10.33.4.1.5,RS-232-MIB::rs232SyncPortReceiveOverrunErrs,Counter32,read-only,,current,,Total number of frames that failed to be received on the port since system re-initialization and while the port state was 'up' or 'test' because the receiver did not accept the data in time.
.1.3.6.1.2.1.10.33.4.1.6,RS-232-MIB::rs232SyncPortInterruptedFrames,Counter32,read-only,,current,,Total number of frames that failed to be received or transmitted on the port due to loss of modem signals since system re-initialization and while the port state was 'up' or 'test'.
.1.3.6.1.2.1.10.33.4.1.7,RS-232-MIB::rs232SyncPortAbortedFrames,Counter32,read-only,,current,,Number of frames aborted on the port due to receiving an abort sequence since system re-initialization and while the port state was 'up' or 'test'.
.1.3.6.1.2.1.10.33.4.1.8,RS-232-MIB::rs232SyncPortRole,INTEGER,read-write,,current,dte(1):dce(2),The role the device is playing that is using this port. dte means the device is performing the role of data terminal equipment dce means the device is performing the role of data circuit-terminating equipment.
.1.3.6.1.2.1.10.33.4.1.9,RS-232-MIB::rs232SyncPortEncoding,INTEGER,read-write,,current,nrz(1):nrzi(2),The bit stream encoding technique that is in effect for this port. nrz for Non-Return to Zero encoding nrzi for Non-Return to Zero Inverted encoding.
.1.3.6.1.2.1.10.33.4.1.10,RS-232-MIB::rs232SyncPortRTSControl,INTEGER,read-write,,current,controlled(1):constant(2),The method used to control the Request To Send (RTS) signal. controlled when the DTE is asserts RTS each time data needs to be transmitted and drops RTS at some point after data transmission begins. If rs232SyncPortRole is 'dte', the RTS is an output signal. The device will issue a RTS and wait for a CTS from the DCE before starting to transmit. If rs232SyncPortRole is 'dce', the RTS is an input signal. The device will issue a CTS only after having received RTS and waiting the rs232SyncPortRTSCTSDelay interval. constant when the DTE constantly asserts RTS.
.1.3.6.1.2.1.10.33.4.1.11,RS-232-MIB::rs232SyncPortRTSCTSDelay,Integer32,read-write,,current,,The interval (in milliseconds) that the DCE must wait after it sees RTS asserted before asserting CTS. This object exists in support of older synchronous devices that cannot recognize CTS within a certain interval after it asserts RTS.
.1.3.6.1.2.1.10.33.4.1.12,RS-232-MIB::rs232SyncPortMode,INTEGER,read-write,,current,fdx(1):hdx(2):simplex-receive(3):simplex-send(4),The mode of operation of the port with respect to the direction and simultaneity of data transfer. fdx when frames on the data link can be transmitted and received at the same time hdx when frames can either be received from the data link or transmitted onto the data link but not at the same time. simplex-receive when frames can only be received on this data link. simplex-send when frames can only be sent on this data link.
.1.3.6.1.2.1.10.33.4.1.13,RS-232-MIB::rs232SyncPortIdlePattern,INTEGER,read-write,,current,mark(1):space(2),The bit pattern used to indicate an idle line.
.1.3.6.1.2.1.10.33.4.1.14,RS-232-MIB::rs232SyncPortMinFlags,Integer32,read-write,,current,,The minimum number of flag patterns this port needs in order to recognize the end of one frame and the start of the next. Plausible values are 1 and 2.
.1.3.6.1.2.1.10.33.5,RS-232-MIB::rs232InSigTable,,not-accessible,,current,,A list of port input control signal entries implemented and visible to the software on the port, and useful to monitor.
.1.3.6.1.2.1.10.33.5.1,RS-232-MIB::rs232InSigEntry,,not-accessible,rs232InSigPortIndex:rs232InSigName,current,,Input control signal status for a hardware port.
.1.3.6.1.2.1.10.33.5.1.1,RS-232-MIB::rs232InSigPortIndex,Integer32,read-only,,current,,The value of rs232PortIndex for the port to which this entry belongs.
.1.3.6.1.2.1.10.33.5.1.2,RS-232-MIB::rs232InSigName,INTEGER,read-only,,current,rts(1):cts(2):dsr(3):dtr(4):ri(5):dcd(6):sq(7):srs(8):srts(9):scts(10):sdcd(11),Identification of a hardware signal, as follows: rts Request to Send cts Clear to Send dsr Data Set Ready dtr Data Terminal Ready ri Ring Indicator dcd Received Line Signal Detector sq Signal Quality Detector srs Data Signaling Rate Selector srts Secondary Request to Send scts Secondary Clear to Send sdcd Secondary Received Line Signal Detector 
.1.3.6.1.2.1.10.33.5.1.3,RS-232-MIB::rs232InSigState,INTEGER,read-only,,current,none(1):on(2):off(3),The current signal state.
.1.3.6.1.2.1.10.33.5.1.4,RS-232-MIB::rs232InSigChanges,Counter32,read-only,,current,,The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'.
.1.3.6.1.2.1.10.33.6,RS-232-MIB::rs232OutSigTable,,not-accessible,,current,,A list of port output control signal entries implemented and visible to the software on the port, and useful to monitor.
.1.3.6.1.2.1.10.33.6.1,RS-232-MIB::rs232OutSigEntry,,not-accessible,rs232OutSigPortIndex:rs232OutSigName,current,,Output control signal status for a hardware port.
.1.3.6.1.2.1.10.33.6.1.1,RS-232-MIB::rs232OutSigPortIndex,Integer32,read-only,,current,,The value of rs232PortIndex for the port to which this entry belongs.
.1.3.6.1.2.1.10.33.6.1.2,RS-232-MIB::rs232OutSigName,INTEGER,read-only,,current,rts(1):cts(2):dsr(3):dtr(4):ri(5):dcd(6):sq(7):srs(8):srts(9):scts(10):sdcd(11),Identification of a hardware signal, as follows: rts Request to Send cts Clear to Send dsr Data Set Ready dtr Data Terminal Ready ri Ring Indicator dcd Received Line Signal Detector sq Signal Quality Detector srs Data Signaling Rate Selector srts Secondary Request to Send scts Secondary Clear to Send sdcd Secondary Received Line Signal Detector 
.1.3.6.1.2.1.10.33.6.1.3,RS-232-MIB::rs232OutSigState,INTEGER,read-only,,current,none(1):on(2):off(3),The current signal state.
.1.3.6.1.2.1.10.33.6.1.4,RS-232-MIB::rs232OutSigChanges,Counter32,read-only,,current,,The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'.
.1.3.6.1.2.1.10.33.7,RS-232-MIB::rs232Conformance,,,,,,
.1.3.6.1.2.1.10.33.7.1,RS-232-MIB::rs232Groups,,,,,,
.1.3.6.1.2.1.10.33.7.1.1,RS-232-MIB::rs232Group,,,,,,A collection of objects providing information applicable to all RS-232-like interfaces.
.1.3.6.1.2.1.10.33.7.1.2,RS-232-MIB::rs232AsyncGroup,,,,,,A collection of objects providing information applicable to asynchronous RS-232-like interfaces.
.1.3.6.1.2.1.10.33.7.1.3,RS-232-MIB::rs232SyncGroup,,,,,,A collection of objects providing information applicable to synchronous RS-232-like interfaces.
.1.3.6.1.2.1.10.33.7.1.4,RS-232-MIB::rs232SyncSDLCGroup,,,,,,A collection of objects providing information applicable to synchronous RS-232-like interfaces running SDLC.
.1.3.6.1.2.1.10.33.7.2,RS-232-MIB::rs232Compliances,,,,,,
.1.3.6.1.2.1.10.33.7.2.1,RS-232-MIB::rs232Compliance,,,,,,The compliance statement for SNMPv2 entities which have RS-232-like hardware interfaces.
.1.3.6.1.2.1.10.34,PARALLEL-MIB::para,,,,,,The MIB module for Parallel-printer-like hardware devices.
.1.3.6.1.2.1.10.34.1,PARALLEL-MIB::paraNumber,Integer32,read-only,,current,,The number of ports (regardless of their current state) in the Parallel-printer-like port table.
.1.3.6.1.2.1.10.34.2,PARALLEL-MIB::paraPortTable,,not-accessible,,current,,A list of port entries. The number of entries is given by the value of paraNumber.
.1.3.6.1.2.1.10.34.2.1,PARALLEL-MIB::paraPortEntry,,not-accessible,paraPortIndex,current,,Status and parameter values for a port.
.1.3.6.1.2.1.10.34.2.1.1,PARALLEL-MIB::paraPortIndex,Integer32,read-only,,current,,The value of ifIndex for the port. By convention and if possible, hardware port numbers map directly to external connectors. The value for each port must remain constant at least from one re-initialization of the network management agent to the next.
.1.3.6.1.2.1.10.34.2.1.2,PARALLEL-MIB::paraPortType,INTEGER,read-only,,current,other(1):centronics(2):dataproducts(3),The port's hardware type.
.1.3.6.1.2.1.10.34.2.1.3,PARALLEL-MIB::paraPortInSigNumber,Integer32,read-only,,current,,The number of input signals for the port in the input signal table (paraPortInSigTable). The table contains entries only for those signals the software can detect and that are useful to observe.
.1.3.6.1.2.1.10.34.2.1.4,PARALLEL-MIB::paraPortOutSigNumber,Integer32,read-only,,current,,The number of output signals for the port in the output signal table (paraPortOutSigTable). The table contains entries only for those signals the software can assert and that are useful to observe.
.1.3.6.1.2.1.10.34.3,PARALLEL-MIB::paraInSigTable,,not-accessible,,current,,A list of port input control signal entries.
.1.3.6.1.2.1.10.34.3.1,PARALLEL-MIB::paraInSigEntry,,not-accessible,paraInSigPortIndex:paraInSigName,current,,Input control signal status for a hardware port.
.1.3.6.1.2.1.10.34.3.1.1,PARALLEL-MIB::paraInSigPortIndex,Integer32,read-only,,current,,The value of paraPortIndex for the port to which this entry belongs.
.1.3.6.1.2.1.10.34.3.1.2,PARALLEL-MIB::paraInSigName,INTEGER,read-only,,current,power(1):online(2):busy(3):paperout(4):fault(5),Identification of a hardware signal.
.1.3.6.1.2.1.10.34.3.1.3,PARALLEL-MIB::paraInSigState,INTEGER,read-only,,current,none(1):on(2):off(3),The current signal state.
.1.3.6.1.2.1.10.34.3.1.4,PARALLEL-MIB::paraInSigChanges,Counter32,read-only,,current,,The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'.
.1.3.6.1.2.1.10.34.4,PARALLEL-MIB::paraOutSigTable,,not-accessible,,current,,A list of port output control signal entries.
.1.3.6.1.2.1.10.34.4.1,PARALLEL-MIB::paraOutSigEntry,,not-accessible,paraOutSigPortIndex:paraOutSigName,current,,Output control signal status for a hardware port.
.1.3.6.1.2.1.10.34.4.1.1,PARALLEL-MIB::paraOutSigPortIndex,Integer32,read-only,,current,,The value of paraPortIndex for the port to which this entry belongs.
.1.3.6.1.2.1.10.34.4.1.2,PARALLEL-MIB::paraOutSigName,INTEGER,read-only,,current,power(1):online(2):busy(3):paperout(4):fault(5),Identification of a hardware signal.
.1.3.6.1.2.1.10.34.4.1.3,PARALLEL-MIB::paraOutSigState,INTEGER,read-only,,current,none(1):on(2):off(3),The current signal state.
.1.3.6.1.2.1.10.34.4.1.4,PARALLEL-MIB::paraOutSigChanges,Counter32,read-only,,current,,The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'.
.1.3.6.1.2.1.10.34.5,PARALLEL-MIB::paraConformance,,,,,,
.1.3.6.1.2.1.10.34.5.1,PARALLEL-MIB::paraGroups,,,,,,
.1.3.6.1.2.1.10.34.5.1.1,PARALLEL-MIB::paraGroup,,,,,,A collection of objects providing information applicable to all Parallel-printer-like interfaces.
.1.3.6.1.2.1.10.34.5.2,PARALLEL-MIB::paraCompliances,,,,,,
.1.3.6.1.2.1.10.34.5.2.1,PARALLEL-MIB::paraCompliance,,,,,,The compliance statement for SNMPv2 entities which have Parallel-printer-like hardware interfaces.
.1.3.6.1.2.1.10.38,MIOX25-MIB::miox,,,,,,
.1.3.6.1.2.1.10.38.1,MIOX25-MIB::mioxPle,,,,,,
.1.3.6.1.2.1.10.38.1.1,MIOX25-MIB::mioxPleTable,,not-accessible,,mandatory,,This table contains information relative to an interface to an X.25 Packet Level Entity (PLE).
.1.3.6.1.2.1.10.38.1.1.1,MIOX25-MIB::mioxPleEntry,,not-accessible,ifIndex,mandatory,,These objects manage the encapsulation of other protocols within X.25.
.1.3.6.1.2.1.10.38.1.1.1.1,MIOX25-MIB::mioxPleMaxCircuits,INTEGER,read-write,,mandatory,,The maximum number of X.25 circuits that can be open at one time for this interface. A value of zero indicates the interface will not allow any additional circuits (as it may soon be shutdown). A value of 2147483647 allows an unlimited number of circuits.
.1.3.6.1.2.1.10.38.1.1.1.2,MIOX25-MIB::mioxPleRefusedConnections,Counter32,read-only,,mandatory,,The number of X.25 calls from a remote systems to this system that were cleared by this system. The interface instance should identify the X.25 interface the call came in on.
.1.3.6.1.2.1.10.38.1.1.1.3,MIOX25-MIB::mioxPleEnAddrToX121LkupFlrs,Counter32,read-only,,mandatory,,The number of times a translation from an Encapsulated Address to an X.121 address failed to find a corresponding X.121 address. Encapsulated addresses can be looked up in the mioxPeerTable or translated via an algorithm as for the DDN. Addresses that are successfully recognized do not increment this counter. Addresses that are not recognized (reflecting an abnormal packet delivery condition) increment this counter. If an address translation fails, it may be difficult to determine which PLE entry should count the failure. In such cases the first likely entry in this table should be selected. Agents should record the failure even if they are unsure which PLE should be associated with the failure.
.1.3.6.1.2.1.10.38.1.1.1.4,MIOX25-MIB::mioxPleLastFailedEnAddr,OCTET,read-only,,mandatory,,The last Encapsulated address that failed to find a corresponding X.121 address and caused mioxPleEnAddrToX121LkupFlrs to be incremented. The first octet of this object contains the encapsulation type, the remaining octets contain the address of that type that failed. Thus for an IP address, the length will be five octets, the first octet will contain 204 (hex CC), and the last four octets will contain the IP address. For a snap encapsulation, the first byte would be 128 (hex 80) and the rest of the octet string would have the snap header.
.1.3.6.1.2.1.10.38.1.1.1.5,MIOX25-MIB::mioxPleEnAddrToX121LkupFlrTime,TimeTicks,read-only,,mandatory,,The most recent value of sysUpTime when the translation from an Encapsulated Address to X.121 address failed to find a corresponding X.121 address.
.1.3.6.1.2.1.10.38.1.1.1.6,MIOX25-MIB::mioxPleX121ToEnAddrLkupFlrs,Counter32,read-only,,mandatory,,The number of times the translation from an X.121 address to an Encapsulated Address failed to find a corresponding Encapsulated Address. Addresses successfully recognized by an algorithm do not increment this counter. This counter reflects the number of times call acceptance encountered the abnormal condition of not recognizing the peer.
.1.3.6.1.2.1.10.38.1.1.1.7,MIOX25-MIB::mioxPleLastFailedX121Address,OCTET,read-only,,mandatory,,The last X.121 address that caused mioxPleX121ToEnAddrLkupFlrs to increase.
.1.3.6.1.2.1.10.38.1.1.1.8,MIOX25-MIB::mioxPleX121ToEnAddrLkupFlrTime,TimeTicks,read-only,,mandatory,,The most recent value of sysUpTime when the translation from an X.121 address to an Encapsulated Address failed to find a corresponding Encapsulated Address.
.1.3.6.1.2.1.10.38.1.1.1.9,MIOX25-MIB::mioxPleQbitFailures,Counter32,read-only,,mandatory,,The number of times a connection was closed because of a Q-bit failure.
.1.3.6.1.2.1.10.38.1.1.1.10,MIOX25-MIB::mioxPleQbitFailureRemoteAddress,OCTET,read-only,,mandatory,,The remote address of the most recent (last) connection that was closed because of a Q-bit failure.
.1.3.6.1.2.1.10.38.1.1.1.11,MIOX25-MIB::mioxPleQbitFailureTime,TimeTicks,read-only,,mandatory,,The most recent value of sysUpTime when a connection was closed because of a Q-bit failure. This will also be the last time that mioxPleQbitFailures was incremented.
.1.3.6.1.2.1.10.38.1.1.1.12,MIOX25-MIB::mioxPleMinimumOpenTimer,INTEGER,read-write,,mandatory,,The minimum time in milliseconds this interface will keep a connection open before allowing it to be closed. A value of zero indicates no timer.
.1.3.6.1.2.1.10.38.1.1.1.13,MIOX25-MIB::mioxPleInactivityTimer,INTEGER,read-write,,mandatory,,The amount of time time in milliseconds this interface will keep an idle connection open before closing it. A value of 2147483647 indicates no timer.
.1.3.6.1.2.1.10.38.1.1.1.14,MIOX25-MIB::mioxPleHoldDownTimer,INTEGER,read-write,,mandatory,,The hold down timer in milliseconds. This is the minimum amount of time to wait before trying another call to a host that was previously unsuccessful. A value of 2147483647 indicates the host will not be retried.
.1.3.6.1.2.1.10.38.1.1.1.15,MIOX25-MIB::mioxPleCollisionRetryTimer,INTEGER,read-write,,mandatory,,The Collision Retry Timer in milliseconds. The time to delay between call attempts when the maximum number of circuits is exceeded in a call attempt.
.1.3.6.1.2.1.10.38.1.1.1.16,MIOX25-MIB::mioxPleDefaultPeerId,,read-write,,mandatory,,This identifies the instance of the index in the mioxPeerTable for the default parameters to use with this interface. The entry identified by this object may have a zero length Encapsulation address and a zero length X.121 address. These default parameters are used with connections to hosts that do not have entries in the mioxPeerTable. Such connections occur when using ddn-x25 IP-X.25 address mapping or when accepting connections from other hosts not in the mioxPeerTable. The mioxPeerEncTable entry with the same index as the mioxPeerTable entry specifies the call encapsulation types this PLE will accept for peers not in the mioxPeerTable. If the mioxPeerEncTable doesn't contain any entries, this PLE will not accept calls from entries not in the mioxPeerTable.
.1.3.6.1.2.1.10.38.2,MIOX25-MIB::mioxPeer,,,,,,
.1.3.6.1.2.1.10.38.2.1,MIOX25-MIB::mioxPeerTable,,not-accessible,,mandatory,,This table contains information about the possible peers this machine may exchange packets with.
.1.3.6.1.2.1.10.38.2.1.1,MIOX25-MIB::mioxPeerEntry,,not-accessible,mioxPeerIndex,mandatory,,Per peer information.
.1.3.6.1.2.1.10.38.2.1.1.1,MIOX25-MIB::mioxPeerIndex,INTEGER,read-only,,mandatory,,An index value that distinguished one entry from another. This index is independent of any other index.
.1.3.6.1.2.1.10.38.2.1.1.2,MIOX25-MIB::mioxPeerStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4):clearCall(5):makeCall(6),This reports the status of a peer entry. A value of valid indicates a normal entry that is in use by the agent. A value of underCreation indicates a newly created entry which isn't yet in use because the creating management station is still setting values. The value of invalid indicates the entry is no longer in use and the agent is free to delete the entry at any time. A management station is also free to use an entry in the invalid state. Entries are created by setting a value of createRequest. Only non-existent or invalid entries can be set to createRequest. Upon receiving a valid createRequest, the agent will create an entry in the underCreation state. This object can not be set to a value of underCreation directly, entries can only be created by setting a value of createRequest. Entries that exist in other than the invalid state can not be set to createRequest. Entries with a value of underCreation are not used by the system and the management station can change the values of other objects in the table entry. Management stations should also remember to configure values in the mioxPeerEncTable with the same peer index value as this peer entry. An entry in the underCreation state can be set to valid or invalid. Entries in the underCreation state will stay in that state until 1) the agent times them out, 2) they are set to valid, 3) they are set to invalid. If an agent notices an entry has been in the underCreation state for an abnormally long time, it may decide the management station has failed and invalidate the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. Once a management station has completed all fields of an entry, it will set a value of valid. This causes the entry to be activated. Entries in the valid state may also be set to makeCall or clearCall to make or clear X.25 calls to the peer. After such a set request the entry will still be in the valid state. Setting a value of makeCall causes the agent to initiate an X.25 call request to the peer specified by the entry. Setting a value of clearCall causes the agent to initiate clearing one X.25 call present to the peer. Each set request will initiate another call or clear request (up to the maximum allowed); this means that management stations that fail to get a response to a set request should query to see if a call was in fact placed or cleared before retrying the request. Entries not in the valid state can not be set to makeCall or clearCall. The values of makeCall and clearCall provide for circuit control on devices which perform Ethernet Bridging using static circuit assignment without address recognition; other devices which dynamically place calls based on destination addresses may reject such requests. An agent that (re)creates a new entry
.1.3.6.1.2.1.10.38.2.1.1.3,MIOX25-MIB::mioxPeerMaxCircuits,INTEGER,read-write,,mandatory,,The maximum number of X.25 circuits allowed to this peer.
.1.3.6.1.2.1.10.38.2.1.1.4,MIOX25-MIB::mioxPeerIfIndex,INTEGER,read-write,,mandatory,,The value of the ifIndex object for the interface to X.25 to use to call the peer.
.1.3.6.1.2.1.10.38.2.1.1.5,MIOX25-MIB::mioxPeerConnectSeconds,Counter32,read-only,,mandatory,,The number of seconds a call to this peer was active. This counter will be incremented by one for every second a connection to a peer was open. If two calls are open at the same time, one second of elapsed real time will results in two seconds of connect time.
.1.3.6.1.2.1.10.38.2.1.1.6,MIOX25-MIB::mioxPeerX25CallParamId,,read-write,,mandatory,,The instance of the index object in the x25CallParmTable from RFC 1382 for the X.25 call parameters used to communicate with the remote host. The well known value {0 0} indicates no call parameters specified.
.1.3.6.1.2.1.10.38.2.1.1.7,MIOX25-MIB::mioxPeerEnAddr,OCTET,read-write,,mandatory,,The Encapsulation address of the remote host mapped by this table entry. A length of zero indicates the remote IP address is unknown or unspecified for use as a PLE default. The first octet of this object contains the encapsulation type, the remaining octets contain an address of that type. Thus for an IP address, the length will be five octets, the first octet will contain 204 (hex CC), and the last four octets will contain the IP address. For a snap encapsulation, the first byte would be 128 (hex 80) and the rest of the octet string would have the snap header.
.1.3.6.1.2.1.10.38.2.1.1.8,MIOX25-MIB::mioxPeerX121Address,OCTET,read-write,,mandatory,,The X.25 address of the remote host mapped by this table entry. A zero length string indicates the X.25 address is unspecified for use as the PLE default.
.1.3.6.1.2.1.10.38.2.1.1.9,MIOX25-MIB::mioxPeerX25CircuitId,,read-write,,mandatory,,This object identifies the instance of the index for the X.25 circuit open to the peer mapped by this table entry. The well known value {0 0} indicates no connection currently active. For multiple connections, this identifies the index of a multiplexing table entry for the connections. This can only be written to configure use of PVCs which means the identified circuit table entry for a write must be a PVC.
.1.3.6.1.2.1.10.38.2.1.1.10,MIOX25-MIB::mioxPeerDescr,OCTET,read-write,,mandatory,,This object returns any identification information about the peer. An agent may supply the comment information found in the configuration file entry for this peer. A zero length string indicates no information available.
.1.3.6.1.2.1.10.38.2.2,MIOX25-MIB::mioxPeerEncTable,,not-accessible,,mandatory,,This table contains the list of encapsulations used to communicate with a peer. This table has two indexes, the first identifies the peer, the second distinguishes encapsulation types. The first index identifies the corresponding entry in the mioxPeerTable. The second index gives the priority of the different encapsulations. The encapsulation types are ordered in priority order. For calling a peer, the first entry (mioxPeerEncIndex of 1) is tried first. If the call doesn't succeed because the remote host clears the call due to incompatible call user data, the next entry in the list is tried. Each entry is tried until the list is exhausted. For answering a call, the encapsulation type requested by the peer must be found the list or the call will be refused. If there are no entries in this table for a peer, all call requests from the peer will be refused. Objects in this table can only be set when the mioxPeerStatus object with the same index has a value of underCreation. When that status object is set to invalid and deleted, the entry in this table with that peer index must also be deleted.
.1.3.6.1.2.1.10.38.2.2.1,MIOX25-MIB::mioxPeerEncEntry,,not-accessible,mioxPeerIndex:mioxPeerEncIndex,mandatory,,Per connection information.
.1.3.6.1.2.1.10.38.2.2.1.1,MIOX25-MIB::mioxPeerEncIndex,INTEGER,read-only,,mandatory,,The second index in the table which distinguishes different encapsulation types.
.1.3.6.1.2.1.10.38.2.2.1.2,MIOX25-MIB::mioxPeerEncType,INTEGER,read-write,,mandatory,,The value of the encapsulation type. For IP encapsulation this will have a value of 204 (hex CC). For SNAP encapsulated packets, this will have a value of 128 (hex 80). For CLNP, ISO 8473, this will have a value of 129 (hex 81). For ES-ES, ISO 9542, this will have a value of 130 (hex 82). A value of 197 (hex C5) identifies the Blacker X.25 encapsulation. A value of 0, identifies the Null encapsulation. This value can only be written when the mioxPeerStatus object with the same mioxPeerIndex has a value of underCreation. Setting this object to a value of 256 deletes the entry. When deleting an entry, all other entries in the mioxPeerEncTable with the same mioxPeerIndex and with an mioxPeerEncIndex higher then the deleted entry, will all have their mioxPeerEncIndex values decremented by one.
.1.3.6.1.2.1.10.39,SONET-MIB::sonetMIB,,,,,,The MIB module to describe SONET/SDH interface objects. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3592; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.39.1,SONET-MIB::sonetObjects,,,,,,
.1.3.6.1.2.1.10.39.1.1,SONET-MIB::sonetMedium,,,,,,
.1.3.6.1.2.1.10.39.1.1.1,SONET-MIB::sonetMediumTable,,not-accessible,,current,,The SONET/SDH Medium table.
.1.3.6.1.2.1.10.39.1.1.1.1,SONET-MIB::sonetMediumEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Medium table.
.1.3.6.1.2.1.10.39.1.1.1.1.1,SONET-MIB::sonetMediumType,INTEGER,read-write,,current,sonet(1):sdh(2),This variable identifies whether a SONET or a SDH signal is used across this interface.
.1.3.6.1.2.1.10.39.1.1.1.1.2,SONET-MIB::sonetMediumTimeElapsed,Integer32,read-only,,current,,The number of seconds, including partial seconds, that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.10.39.1.1.1.1.3,SONET-MIB::sonetMediumValidIntervals,Integer32,read-only,,current,,The number of previous 15-minute intervals for which data was collected. A SONET/SDH interface must be capable of supporting at least n intervals. The minimum value of n is 4. The default of n is 32. The maximum value of n is 96. The value will be <n> unless the measurement was (re-)started within the last (<n>*15) minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available. 
.1.3.6.1.2.1.10.39.1.1.1.1.4,SONET-MIB::sonetMediumLineCoding,INTEGER,read-write,,current,sonetMediumOther(1):sonetMediumB3ZS(2):sonetMediumCMI(3):sonetMediumNRZ(4):sonetMediumRZ(5),This variable describes the line coding for this interface. The B3ZS and CMI are used for electrical SONET/SDH signals (STS-1 and STS-3). The Non-Return to Zero (NRZ) and the Return to Zero are used for optical SONET/SDH signals.
.1.3.6.1.2.1.10.39.1.1.1.1.5,SONET-MIB::sonetMediumLineType,INTEGER,read-write,,current,sonetOther(1):sonetShortSingleMode(2):sonetLongSingleMode(3):sonetMultiMode(4):sonetCoax(5):sonetUTP(6),This variable describes the line type for this interface. The line types are Short and Long Range Single Mode fiber or Multi-Mode fiber interfaces, and coax and UTP for electrical interfaces. The value sonetOther should be used when the Line Type is not one of the listed values.
.1.3.6.1.2.1.10.39.1.1.1.1.6,SONET-MIB::sonetMediumCircuitIdentifier,OCTET,read-write,,current,,This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting. Note that the circuit identifier, if available, is also represented by ifPhysAddress.
.1.3.6.1.2.1.10.39.1.1.1.1.7,SONET-MIB::sonetMediumInvalidIntervals,Integer32,read-only,,current,,The number of intervals in the range from 0 to sonetMediumValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.39.1.1.1.1.8,SONET-MIB::sonetMediumLoopbackConfig,BITS,read-write,,current,sonetNoLoop(0):sonetFacilityLoop(1):sonetTerminalLoop(2):sonetOtherLoop(3),The current loopback state of the SONET/SDH interface. The values mean: sonetNoLoop Not in the loopback state. A device that is not capable of performing a loopback on this interface shall always return this value. sonetFacilityLoop The received signal at this interface is looped back out through the corresponding transmitter in the return direction. sonetTerminalLoop The signal that is about to be transmitted is connected to the associated incoming receiver. sonetOtherLoop Loopbacks that are not defined here.
.1.3.6.1.2.1.10.39.1.1.2,SONET-MIB::sonetSESthresholdSet,INTEGER,read-write,,current,other(1):bellcore1991(2):ansi1993(3):itu1995(4):ansi1997(5),An enumerated integer indicating which recognized set of SES thresholds that the agent uses for determining severely errored seconds and unavailable time. other(1) None of the following. bellcore1991(2) Bellcore TR-NWT-000253, 1991 [TR253], or ANSI T1M1.3/93-005R2, 1993 [T1M1.3]. See also Appendix B. ansi1993(3) ANSI T1.231, 1993 [T1.231a], or Bellcore GR-253-CORE, Issue 2, 1995 [GR253] itu1995(4) ITU Recommendation G.826, 1995 [G.826] ansi1997(5) ANSI T1.231, 1997 [T1.231b] If a manager changes the value of this object then the SES statistics collected prior to this change must be invalidated.
.1.3.6.1.2.1.10.39.1.2,SONET-MIB::sonetSection,,,,,,
.1.3.6.1.2.1.10.39.1.2.1,SONET-MIB::sonetSectionCurrentTable,,not-accessible,,current,,The SONET/SDH Section Current table.
.1.3.6.1.2.1.10.39.1.2.1.1,SONET-MIB::sonetSectionCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Section Current table.
.1.3.6.1.2.1.10.39.1.2.1.1.1,SONET-MIB::sonetSectionCurrentStatus,Integer32,read-only,,current,,This variable indicates the status of the interface. The sonetSectionCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetSectionNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetSectionNoDefect 2 sonetSectionLOS 4 sonetSectionLOF
.1.3.6.1.2.1.10.39.1.2.1.1.2,SONET-MIB::sonetSectionCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.2.1.1.3,SONET-MIB::sonetSectionCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.2.1.1.4,SONET-MIB::sonetSectionCurrentSEFSs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.2.1.1.5,SONET-MIB::sonetSectionCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH Section in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.2.2,SONET-MIB::sonetSectionIntervalTable,,not-accessible,,current,,The SONET/SDH Section Interval table.
.1.3.6.1.2.1.10.39.1.2.2.1,SONET-MIB::sonetSectionIntervalEntry,,not-accessible,ifIndex:sonetSectionIntervalNumber,current,,An entry in the SONET/SDH Section Interval table.
.1.3.6.1.2.1.10.39.1.2.2.1.1,SONET-MIB::sonetSectionIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.1.2.2.1.2,SONET-MIB::sonetSectionIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.2.2.1.3,SONET-MIB::sonetSectionIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.2.2.1.4,SONET-MIB::sonetSectionIntervalSEFSs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.2.2.1.5,SONET-MIB::sonetSectionIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH Section in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.2.2.1.6,SONET-MIB::sonetSectionIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.1.3,SONET-MIB::sonetLine,,,,,,
.1.3.6.1.2.1.10.39.1.3.1,SONET-MIB::sonetLineCurrentTable,,not-accessible,,current,,The SONET/SDH Line Current table.
.1.3.6.1.2.1.10.39.1.3.1.1,SONET-MIB::sonetLineCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Line Current table.
.1.3.6.1.2.1.10.39.1.3.1.1.1,SONET-MIB::sonetLineCurrentStatus,Integer32,read-only,,current,,This variable indicates the status of the interface. The sonetLineCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetLineNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetLineNoDefect 2 sonetLineAIS 4 sonetLineRDI
.1.3.6.1.2.1.10.39.1.3.1.1.2,SONET-MIB::sonetLineCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.3.1.1.3,SONET-MIB::sonetLineCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.3.1.1.4,SONET-MIB::sonetLineCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH Line in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.3.1.1.5,SONET-MIB::sonetLineCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.3.2,SONET-MIB::sonetLineIntervalTable,,not-accessible,,current,,The SONET/SDH Line Interval table.
.1.3.6.1.2.1.10.39.1.3.2.1,SONET-MIB::sonetLineIntervalEntry,,not-accessible,ifIndex:sonetLineIntervalNumber,current,,An entry in the SONET/SDH Line Interval table.
.1.3.6.1.2.1.10.39.1.3.2.1.1,SONET-MIB::sonetLineIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.1.3.2.1.2,SONET-MIB::sonetLineIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.3.2.1.3,SONET-MIB::sonetLineIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.3.2.1.4,SONET-MIB::sonetLineIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.3.2.1.5,SONET-MIB::sonetLineIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by a SONET/SDH Line in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.3.2.1.6,SONET-MIB::sonetLineIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.1.4,SONET-MIB::sonetFarEndLine,,,,,,
.1.3.6.1.2.1.10.39.1.4.1,SONET-MIB::sonetFarEndLineCurrentTable,,not-accessible,,current,,The SONET/SDH Far End Line Current table.
.1.3.6.1.2.1.10.39.1.4.1.1,SONET-MIB::sonetFarEndLineCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Far End Line Current table.
.1.3.6.1.2.1.10.39.1.4.1.1.1,SONET-MIB::sonetFarEndLineCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.4.1.1.2,SONET-MIB::sonetFarEndLineCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Severely Errored Seconds encountered by a SONET/SDH Medium/Section/Line interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.4.1.1.3,SONET-MIB::sonetFarEndLineCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH Medium/Section/Line interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.4.1.1.4,SONET-MIB::sonetFarEndLineCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End Unavailable Seconds encountered by a SONET/SDH Medium/Section/Line interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.1.4.2,SONET-MIB::sonetFarEndLineIntervalTable,,not-accessible,,current,,The SONET/SDH Far End Line Interval table.
.1.3.6.1.2.1.10.39.1.4.2.1,SONET-MIB::sonetFarEndLineIntervalEntry,,not-accessible,ifIndex:sonetFarEndLineIntervalNumber,current,,An entry in the SONET/SDH Far End Line Interval table.
.1.3.6.1.2.1.10.39.1.4.2.1.1,SONET-MIB::sonetFarEndLineIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.1.4.2.1.2,SONET-MIB::sonetFarEndLineIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH Line interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.4.2.1.3,SONET-MIB::sonetFarEndLineIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Severely Errored Seconds encountered by a SONET/SDH Line interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.4.2.1.4,SONET-MIB::sonetFarEndLineIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH Line interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.4.2.1.5,SONET-MIB::sonetFarEndLineIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End Unavailable Seconds encountered by a SONET/SDH Line interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.1.4.2.1.6,SONET-MIB::sonetFarEndLineIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.2,SONET-MIB::sonetObjectsPath,,,,,,
.1.3.6.1.2.1.10.39.2.1,SONET-MIB::sonetPath,,,,,,
.1.3.6.1.2.1.10.39.2.1.1,SONET-MIB::sonetPathCurrentTable,,not-accessible,,current,,The SONET/SDH Path Current table.
.1.3.6.1.2.1.10.39.2.1.1.1,SONET-MIB::sonetPathCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Path Current table.
.1.3.6.1.2.1.10.39.2.1.1.1.1,SONET-MIB::sonetPathCurrentWidth,INTEGER,read-write,,current,sts1(1):sts3cSTM1(2):sts12cSTM4(3):sts24c(4):sts48cSTM16(5):sts192cSTM64(6):sts768cSTM256(7),A value that indicates the type of the SONET/SDH Path. For SONET, the assigned types are the STS-Nc SPEs, where N = 1, 3, 12, 24, 48, 192 and 768. STS-1 is equal to 51.84 Mbps. For SDH, the assigned types are the STM-Nc VCs, where N = 1, 4, 16, 64 and 256.
.1.3.6.1.2.1.10.39.2.1.1.1.2,SONET-MIB::sonetPathCurrentStatus,Integer32,read-only,,current,,This variable indicates the status of the interface. The sonetPathCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. The sonetPathNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetPathNoDefect 2 sonetPathSTSLOP 4 sonetPathSTSAIS 8 sonetPathSTSRDI 16 sonetPathUnequipped 32 sonetPathSignalLabelMismatch
.1.3.6.1.2.1.10.39.2.1.1.1.3,SONET-MIB::sonetPathCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.1.1.1.4,SONET-MIB::sonetPathCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.1.1.1.5,SONET-MIB::sonetPathCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH Path in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.1.1.1.6,SONET-MIB::sonetPathCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by a Path in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.1.2,SONET-MIB::sonetPathIntervalTable,,not-accessible,,current,,The SONET/SDH Path Interval table.
.1.3.6.1.2.1.10.39.2.1.2.1,SONET-MIB::sonetPathIntervalEntry,,not-accessible,ifIndex:sonetPathIntervalNumber,current,,An entry in the SONET/SDH Path Interval table.
.1.3.6.1.2.1.10.39.2.1.2.1.1,SONET-MIB::sonetPathIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.2.1.2.1.2,SONET-MIB::sonetPathIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH Path in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.1.2.1.3,SONET-MIB::sonetPathIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH Path in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.1.2.1.4,SONET-MIB::sonetPathIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH Path in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.1.2.1.5,SONET-MIB::sonetPathIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by a Path in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.1.2.1.6,SONET-MIB::sonetPathIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.2.2,SONET-MIB::sonetFarEndPath,,,,,,
.1.3.6.1.2.1.10.39.2.2.1,SONET-MIB::sonetFarEndPathCurrentTable,,not-accessible,,current,,The SONET/SDH Far End Path Current table.
.1.3.6.1.2.1.10.39.2.2.1.1,SONET-MIB::sonetFarEndPathCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Far End Path Current table.
.1.3.6.1.2.1.10.39.2.2.1.1.1,SONET-MIB::sonetFarEndPathCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.2.1.1.2,SONET-MIB::sonetFarEndPathCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Severely Errored Seconds encountered by a SONET/SDH Path interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.2.1.1.3,SONET-MIB::sonetFarEndPathCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH Path interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.2.1.1.4,SONET-MIB::sonetFarEndPathCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End Unavailable Seconds encountered by a SONET/SDH Path interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.2.2.2,SONET-MIB::sonetFarEndPathIntervalTable,,not-accessible,,current,,The SONET/SDH Far End Path Interval table.
.1.3.6.1.2.1.10.39.2.2.2.1,SONET-MIB::sonetFarEndPathIntervalEntry,,not-accessible,ifIndex:sonetFarEndPathIntervalNumber,current,,An entry in the SONET/SDH Far End Path Interval table.
.1.3.6.1.2.1.10.39.2.2.2.1.1,SONET-MIB::sonetFarEndPathIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.2.2.2.1.2,SONET-MIB::sonetFarEndPathIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH Path interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.2.2.1.3,SONET-MIB::sonetFarEndPathIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Severely Errored Seconds encountered by a SONET/SDH Path interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.2.2.1.4,SONET-MIB::sonetFarEndPathIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH Path interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.2.2.1.5,SONET-MIB::sonetFarEndPathIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End Unavailable Seconds encountered by a SONET/SDH Path interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.2.2.2.1.6,SONET-MIB::sonetFarEndPathIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.3,SONET-MIB::sonetObjectsVT,,,,,,
.1.3.6.1.2.1.10.39.3.1,SONET-MIB::sonetVT,,,,,,
.1.3.6.1.2.1.10.39.3.1.1,SONET-MIB::sonetVTCurrentTable,,not-accessible,,current,,The SONET/SDH VT Current table.
.1.3.6.1.2.1.10.39.3.1.1.1,SONET-MIB::sonetVTCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH VT Current table.
.1.3.6.1.2.1.10.39.3.1.1.1.1,SONET-MIB::sonetVTCurrentWidth,INTEGER,read-write,,current,vtWidth15VC11(1):vtWidth2VC12(2):vtWidth3(3):vtWidth6VC2(4):vtWidth6c(5),A value that indicates the type of the SONET VT and SDH VC. Assigned widths are VT1.5/VC11, VT2/VC12, VT3, VT6/VC2, and VT6c.
.1.3.6.1.2.1.10.39.3.1.1.1.2,SONET-MIB::sonetVTCurrentStatus,Integer32,read-only,,current,,This variable indicates the status of the interface. The sonetVTCurrentStatus is a bit map represented as a sum, therefore, it can represent multiple defects and failures simultaneously. The sonetVTNoDefect should be set if and only if no other flag is set. The various bit positions are: 1 sonetVTNoDefect 2 sonetVTLOP 4 sonetVTPathAIS 8 sonetVTPathRDI 16 sonetVTPathRFI 32 sonetVTUnequipped 64 sonetVTSignalLabelMismatch
.1.3.6.1.2.1.10.39.3.1.1.1.3,SONET-MIB::sonetVTCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH VT in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.1.1.1.4,SONET-MIB::sonetVTCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH VT in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.1.1.1.5,SONET-MIB::sonetVTCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH VT in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.1.1.1.6,SONET-MIB::sonetVTCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by a VT in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.1.2,SONET-MIB::sonetVTIntervalTable,,not-accessible,,current,,The SONET/SDH VT Interval table.
.1.3.6.1.2.1.10.39.3.1.2.1,SONET-MIB::sonetVTIntervalEntry,,not-accessible,ifIndex:sonetVTIntervalNumber,current,,An entry in the SONET/SDH VT Interval table.
.1.3.6.1.2.1.10.39.3.1.2.1.1,SONET-MIB::sonetVTIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.3.1.2.1.2,SONET-MIB::sonetVTIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered by a SONET/SDH VT in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.1.2.1.3,SONET-MIB::sonetVTIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered by a SONET/SDH VT in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.1.2.1.4,SONET-MIB::sonetVTIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Coding Violations encountered by a SONET/SDH VT in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.1.2.1.5,SONET-MIB::sonetVTIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by a VT in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.1.2.1.6,SONET-MIB::sonetVTIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.3.2,SONET-MIB::sonetFarEndVT,,,,,,
.1.3.6.1.2.1.10.39.3.2.1,SONET-MIB::sonetFarEndVTCurrentTable,,not-accessible,,current,,The SONET/SDH Far End VT Current table.
.1.3.6.1.2.1.10.39.3.2.1.1,SONET-MIB::sonetFarEndVTCurrentEntry,,not-accessible,ifIndex,current,,An entry in the SONET/SDH Far End VT Current table.
.1.3.6.1.2.1.10.39.3.2.1.1.1,SONET-MIB::sonetFarEndVTCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.2.1.1.2,SONET-MIB::sonetFarEndVTCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Severely Errored Seconds encountered by a SONET/SDH VT interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.2.1.1.3,SONET-MIB::sonetFarEndVTCurrentCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH VT interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.2.1.1.4,SONET-MIB::sonetFarEndVTCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End Unavailable Seconds encountered by a SONET/SDH VT interface in the current 15 minute interval.
.1.3.6.1.2.1.10.39.3.2.2,SONET-MIB::sonetFarEndVTIntervalTable,,not-accessible,,current,,The SONET/SDH Far End VT Interval table.
.1.3.6.1.2.1.10.39.3.2.2.1,SONET-MIB::sonetFarEndVTIntervalEntry,,not-accessible,ifIndex:sonetFarEndVTIntervalNumber,current,,An entry in the SONET/SDH Far End VT Interval table.
.1.3.6.1.2.1.10.39.3.2.2.1.1,SONET-MIB::sonetFarEndVTIntervalNumber,Integer32,not-accessible,,current,,A number between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
.1.3.6.1.2.1.10.39.3.2.2.1.2,SONET-MIB::sonetFarEndVTIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH VT interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.2.2.1.3,SONET-MIB::sonetFarEndVTIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Far End Severely Errored Seconds encountered by a SONET/SDH VT interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.2.2.1.4,SONET-MIB::sonetFarEndVTIntervalCVs,Gauge32,read-only,,current,,The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH VT interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.2.2.1.5,SONET-MIB::sonetFarEndVTIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Far End Unavailable Seconds encountered by a SONET/SDH VT interface in a particular 15-minute interval in the past 24 hours.
.1.3.6.1.2.1.10.39.3.2.2.1.6,SONET-MIB::sonetFarEndVTIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.39.4,SONET-MIB::sonetConformance,,,,,,
.1.3.6.1.2.1.10.39.4.1,SONET-MIB::sonetGroups,,,,,,
.1.3.6.1.2.1.10.39.4.1.1,SONET-MIB::sonetMediumStuff,,,,,,A collection of objects providing configuration information applicable to all SONET/SDH interfaces.
.1.3.6.1.2.1.10.39.4.1.2,SONET-MIB::sonetSectionStuff,,,,,,A collection of objects providing information specific to SONET/SDH Section interfaces.
.1.3.6.1.2.1.10.39.4.1.3,SONET-MIB::sonetLineStuff,,,,,,A collection of objects providing information specific to SONET/SDH Line interfaces.
.1.3.6.1.2.1.10.39.4.1.4,SONET-MIB::sonetFarEndLineStuff,,,,,,A collection of objects providing information specific to SONET/SDH Line interfaces, and maintaining Line Far End information.
.1.3.6.1.2.1.10.39.4.1.5,SONET-MIB::sonetPathStuff,,,,,,A collection of objects providing information specific to SONET/SDH Path interfaces.
.1.3.6.1.2.1.10.39.4.1.6,SONET-MIB::sonetFarEndPathStuff,,,,,,A collection of objects providing information specific to SONET/SDH Path interfaces, and maintaining Path Far End information.
.1.3.6.1.2.1.10.39.4.1.7,SONET-MIB::sonetVTStuff,,,,,,A collection of objects providing information specific to SONET/SDH VT interfaces.
.1.3.6.1.2.1.10.39.4.1.8,SONET-MIB::sonetFarEndVTStuff,,,,,,A collection of objects providing information specific to SONET/SDH VT interfaces, and maintaining VT Far End information.
.1.3.6.1.2.1.10.39.4.1.9,SONET-MIB::sonetMediumStuff2,,,,,,A collection of objects providing configuration information applicable to all SONET/SDH interfaces.
.1.3.6.1.2.1.10.39.4.1.10,SONET-MIB::sonetSectionStuff2,,,,,,A collection of objects providing information specific to SONET/SDH Section interfaces.
.1.3.6.1.2.1.10.39.4.1.11,SONET-MIB::sonetLineStuff2,,,,,,A collection of objects providing information specific to SONET/SDH Line interfaces.
.1.3.6.1.2.1.10.39.4.1.12,SONET-MIB::sonetPathStuff2,,,,,,A collection of objects providing information specific to SONET/SDH Path interfaces.
.1.3.6.1.2.1.10.39.4.1.13,SONET-MIB::sonetVTStuff2,,,,,,A collection of objects providing information specific to SONET/SDH VT interfaces.
.1.3.6.1.2.1.10.39.4.1.14,SONET-MIB::sonetFarEndLineStuff2,,,,,,A collection of objects providing information specific to SONET/SDH Line interfaces, and maintaining Line Far End information.
.1.3.6.1.2.1.10.39.4.1.15,SONET-MIB::sonetFarEndPathStuff2,,,,,,A collection of objects providing information specific to SONET/SDH Path interfaces, and maintaining Path Far End information.
.1.3.6.1.2.1.10.39.4.1.16,SONET-MIB::sonetFarEndVTStuff2,,,,,,A collection of objects providing information specific to SONET/SDH VT interfaces, and maintaining VT Far End information.
.1.3.6.1.2.1.10.39.4.2,SONET-MIB::sonetCompliances,,,,,,
.1.3.6.1.2.1.10.39.4.2.1,SONET-MIB::sonetCompliance,,,,,,The compliance statement for SONET/SDH interfaces.
.1.3.6.1.2.1.10.39.4.2.2,SONET-MIB::sonetCompliance2,,,,,,The compliance statement for SONET/SDH interfaces.
.1.3.6.1.2.1.10.44,FRNETSERV-MIB::frnetservMIB,,,,,,The MIB module to describe generic objects for Frame Relay Network Service.
.1.3.6.1.2.1.10.44.1,FRNETSERV-MIB::frnetservObjects,,,,,,
.1.3.6.1.2.1.10.44.1.1,FRNETSERV-MIB::frLportTable,,not-accessible,,current,,The Frame Relay Logical Port Information table is an interface-specific addendum to the generic ifTable of the Interface MIB.
.1.3.6.1.2.1.10.44.1.1.1,FRNETSERV-MIB::frLportEntry,,not-accessible,ifIndex,current,,An entry in the Frame Relay Logical Port Information table.
.1.3.6.1.2.1.10.44.1.1.1.1,FRNETSERV-MIB::frLportNumPlan,INTEGER,read-only,,current,other(1):e164(2):x121(3):none(4),The value of this object identifies the network address numbering plan for this UNI/NNI logical port. The network address is the object ifPhysAddress. The value none(4) implies that there is no ifPhysAddress. The FRS agent will return an octet string of zero length for ifPhysAddress. The value other(1) means that an address has been assigned to this interface, but the numbering plan is not enumerated here.
.1.3.6.1.2.1.10.44.1.1.1.2,FRNETSERV-MIB::frLportContact,OCTET,read-only,,current,,The value of this object identifies the network contact for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.1.1.3,FRNETSERV-MIB::frLportLocation,OCTET,read-only,,current,,The value of this object identifies the frame relay network location for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.1.1.4,FRNETSERV-MIB::frLportType,INTEGER,read-only,,current,uni(1):nni(2),The value of this object identifies the type of network interface for this logical port.
.1.3.6.1.2.1.10.44.1.1.1.5,FRNETSERV-MIB::frLportAddrDLCILen,INTEGER,read-only,,current,twoOctets10Bits(1):threeOctets10Bits(2):threeOctets16Bits(3):fourOctets17Bits(4):fourOctets23Bits(5),The value of this object identifies the Q.922 Address field length and DLCI length for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.1.1.6,FRNETSERV-MIB::frLportVCSigProtocol,INTEGER,read-only,,current,none(1):lmi(2):ansiT1617D(3):ansiT1617B(4):ccittQ933A(5),The value of this object identifies the Local In-Channel Signaling Protocol that is used for this frame relay UNI/NNI logical port. none(1): Interface does not use a PVC signaling protocol lmi(2): Interface operates the Stratacom/ Nortel/DEC Local Management Interface Specification protocol ansiT1617D(3): Interface operates the ANSI T1.617 Annex D PVC status protocol ansiT1617B(4): Interface operates the ANSI Annex B procedures ccittQ933A(5): Interface operates the ITU Q.933 Annex A PVC status protocol
.1.3.6.1.2.1.10.44.1.1.1.7,FRNETSERV-MIB::frLportVCSigPointer,OBJECT,read-only,,deprecated,,The value of this object is used as a pointer to the table that contains the Local In-Channel Signaling Protocol parameters and errors for this UNI/NNI logical port. This object has been deprecated to reflect the fact that the local in-channel signaling parameters are accessed from a single table (frMgtVCSigTable) that includes parameters for all possible signaling protocols. Early design anticipated multiple tables, one for each signaling protocol.
.1.3.6.1.2.1.10.44.1.1.1.8,FRNETSERV-MIB::frLportDLCIIndexValue,Integer32,read-only,,current,,This object contains a hint to be used for frPVCEndptDLCIIndex when creating entries in the frPVCEndptTable. The SYNTAX of this object matches the SYNTAX of the frPVCEndptDLCIIndex - an object that is restricted to legal Q.922 DLCI values for the size of the address field. The value 0 indicates that no unassigned entries are available. To obtain the frPVCEndptDLCIIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent must modify the value to the next unassigned index to prevent assignment of the same value to multiple management systems. A management system should repeat the read to obtain a new value should an attempt to create the new row using the previously returned hint fail.
.1.3.6.1.2.1.10.44.1.1.1.9,FRNETSERV-MIB::frLportTypeAdmin,INTEGER,read-write,,current,uni(1):nni(2),The value of this object desired identifies the type of network interface for this logical port.
.1.3.6.1.2.1.10.44.1.1.1.10,FRNETSERV-MIB::frLportVCSigProtocolAdmin,INTEGER,read-write,,current,none(1):lmi(2):ansiT1617D(3):ansiT1617B(4):ccittQ933A(5),The value of this object identifies the desired Local In-Channel Signaling Protocol that is used for this frame relay UNI/NNI logical port. This value must be made the active protocol as soon as possible on the device. Refer to frLportVCSigProtocol for a description of each signaling protocol choices.
.1.3.6.1.2.1.10.44.1.1.1.11,FRNETSERV-MIB::frLportFragControl,INTEGER,read-write,,current,on(1):off(2),This object controls the transmission and reception of fragmentation frames for this UNI or NNI interface. on(1) Frames are fragmented using the interface fragmentation format Note: The customer side of the interface must also be configured to fragment frames. off(2) Frames are not fragmented using the interface fragmentation format.
.1.3.6.1.2.1.10.44.1.1.1.12,FRNETSERV-MIB::frLportFragSize,Integer32,read-write,,current,,The value of this object is the size in octets of the maximum size of each fragment to be sent when fragmenting. This object is only used by the fragmentation transmitter, and the two sides of the interface may differ. The fragment size includes the octets for the frame relay header, the UI octet, the NLPID, the fragmentation header, and the fragment payload. If frLportFragControl is set to off, this value should be zero.
.1.3.6.1.2.1.10.44.1.2,FRNETSERV-MIB::frMgtVCSigTable,,not-accessible,,current,,The Frame Relay Management VC Signaling Parameters and Errors table.
.1.3.6.1.2.1.10.44.1.2.1,FRNETSERV-MIB::frMgtVCSigEntry,,not-accessible,ifIndex,current,,An entry in the Frame Relay Management VC Signaling Parameters Errors table.
.1.3.6.1.2.1.10.44.1.2.1.1,FRNETSERV-MIB::frMgtVCSigProced,INTEGER,read-only,,current,u2nnet(1):bidirect(2):u2nuser(3),The value of this object identifies the local in-channel signaling procedural role that is used for this UNI/NNI logical port. Bidirectional procedures implies that both user-side and network-side procedural roles are used. u2nnet(1) Logical port operates user to network procedure in the role of the network side bidirect(2) Logical port operates the bidirectional procedure (both user and network side roles) u2nuser(3) Logical port operates user to network procedure in the role of the user side
.1.3.6.1.2.1.10.44.1.2.1.2,FRNETSERV-MIB::frMgtVCSigUserN391,INTEGER,read-only,,current,,The value of this object identifies the User-side N391 full status polling cycle value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated and an attempt to read will result in the noSuchInstance exception response.
.1.3.6.1.2.1.10.44.1.2.1.3,FRNETSERV-MIB::frMgtVCSigUserN392,INTEGER,read-only,,current,,The value of this object identifies the User-side N392 error threshold value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.4,FRNETSERV-MIB::frMgtVCSigUserN393,INTEGER,read-only,,current,,The value of this object identifies the User-side N393 monitored events count value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.5,FRNETSERV-MIB::frMgtVCSigUserT391,INTEGER,read-only,,current,,The value of this object identifies the User-side T391 link integrity verification polling timer value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.6,FRNETSERV-MIB::frMgtVCSigNetN392,INTEGER,read-only,,current,,The value of this object identifies the Network- side N392 error threshold value (nN2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.7,FRNETSERV-MIB::frMgtVCSigNetN393,INTEGER,read-only,,current,,The value of this object identifies the Network- side N393 monitored events count value (nN3 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.8,FRNETSERV-MIB::frMgtVCSigNetT392,INTEGER,read-only,,current,,The value of this object identifies the Network- side T392 polling verification timer value (nT2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.9,FRNETSERV-MIB::frMgtVCSigNetnN4,INTEGER,read-only,,current,,The value of this object identifies the Network- side nN4 maximum status enquires received value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this object is not instantiated. This object applies only to LMI and always has a value of 5.
.1.3.6.1.2.1.10.44.1.2.1.10,FRNETSERV-MIB::frMgtVCSigNetnT3,INTEGER,read-only,,current,,The value of this object identifies the Network- side nT3 timer (for nN4 status enquires received) value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this object is not instantiated. This object applies only to LMI.
.1.3.6.1.2.1.10.44.1.2.1.11,FRNETSERV-MIB::frMgtVCSigUserLinkRelErrors,Counter32,read-only,,current,,The number of user-side local in-channel signaling link reliability errors (i.e., non- receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.12,FRNETSERV-MIB::frMgtVCSigUserProtErrors,Counter32,read-only,,current,,The number of user-side local in-channel signaling protocol errors (i.e., protocol discriminator, unnumbered information, message type, call reference, and mandatory information element errors) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.13,FRNETSERV-MIB::frMgtVCSigUserChanInactive,Counter32,read-only,,current,,The number of times the user-side channel was declared inactive (i.e., N392 errors in N393 events) for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.14,FRNETSERV-MIB::frMgtVCSigNetLinkRelErrors,Counter32,read-only,,current,,The number of network-side local in-channel signaling link reliability errors (i.e., non- receipt of Status/Status Enquiry messages or invalid sequence numbers in a Link Integrity Verification Information Element) for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.2.1.15,FRNETSERV-MIB::frMgtVCSigNetProtErrors,Counter32,read-only,,current,,The number of network-side local in-channel signaling protocol errors (i.e., protocol discriminator, message type, call reference, and mandatory information element errors) for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.2.1.16,FRNETSERV-MIB::frMgtVCSigNetChanInactive,Counter32,read-only,,current,,The number of times the network-side channel was declared inactive (i.e., N392 errors in N393 events) for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.2.1.17,FRNETSERV-MIB::frMgtVCSigProcedAdmin,INTEGER,read-write,,current,u2nnet(1):bidirect(2):u2nuser(3),The value of this object identifies the local in-channel signaling procedural role that is used for this UNI/NNI logical port. Bidirectional procedures implies that both user-side and network-side procedural roles are used. u2nnet(1) Logical port operates user to network procedure in the role of the network side bidirect(2) Logical port operates the bidirectional procedure (both user and network side roles) u2nuser(3) Logical port operates user to network procedure in the role of the user side
.1.3.6.1.2.1.10.44.1.2.1.18,FRNETSERV-MIB::frMgtVCSigUserN391Admin,INTEGER,read-write,,current,,The value of this object identifies the desired User-side N391 full status polling cycle value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.19,FRNETSERV-MIB::frMgtVCSigUserN392Admin,INTEGER,read-write,,current,,The value of this object identifies the desired User-side N392 error threshold value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.20,FRNETSERV-MIB::frMgtVCSigUserN393Admin,INTEGER,read-write,,current,,The value of this object identifies the desired User-side N393 monitored events count value for this UNI/NNI logical port. If the logical port is not performing user-side (bidirectional) procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.21,FRNETSERV-MIB::frMgtVCSigUserT391Admin,INTEGER,read-write,,current,,The value of this object identifies the desired User-side T391 link integrity verification polling timer value for this UNI/NNI logical port. If the logical port is not performing user-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.22,FRNETSERV-MIB::frMgtVCSigNetN392Admin,INTEGER,read-write,,current,,The value of this object identifies the desired Network-side N392 error threshold value (nN2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.23,FRNETSERV-MIB::frMgtVCSigNetN393Admin,INTEGER,read-write,,current,,The value of this object identifies the desired Network-side N393 monitored events count value (nN3 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.24,FRNETSERV-MIB::frMgtVCSigNetT392Admin,INTEGER,read-write,,current,,The value of this object identifies the desired Network-side T392 polling verification timer value (nT2 for LMI) for this UNI/NNI logical port. If the logical port is not performing network-side procedures, then this object is not instantiated.
.1.3.6.1.2.1.10.44.1.2.1.25,FRNETSERV-MIB::frMgtVCSigNetnT3Admin,INTEGER,read-write,,current,,The value of this object identifies the desired Network-side nT3 timer (for nN4 status enquires received) value for this UNI/NNI logical port. If the logical port is not performing network-side procedures or is not performing LMI procedures, then this object is not instantiated. This object applies only to LMI.
.1.3.6.1.2.1.10.44.1.3,FRNETSERV-MIB::frPVCEndptTable,,not-accessible,,current,,The Frame Relay PVC End-Point table. This table is used to model a PVC end-point. This table contains the traffic parameters and statistics for a PVC end-point. This table is used to identify the traffic parameters for a bi-directional PVC segment end- point, and it also provides statistics for a PVC segment end-point. A PVC segment end-point is identified by a UNI/NNI logical port index value and DLCI index value. If the frame relay service provider allows the frame relay CNM subscriber to create, modify or delete PVCs using SNMP, then this table is used to identify and reserve the requested traffic parameters of each PVC segment end-point. The Connection table is used to 'connect' the end- points together. Not all implementations will support the capability of creating/modifying/deleting PVCs using SNMP as a feature of frame relay CNM service. Uni-directional PVCs are modeled with zero valued traffic parameters in one of the directions (In or Out direction) in this table. To create a PVC, the following procedures shall be followed: 1) Create the entries for the PVC segment endpoints in the frPVCEndptTable by specifying the traffic parameters for the bi-directional PVC segment endpoints. As shown in figure 2, a point-to-point PVC has two endpoints, thus two entries in this table. Uni-directional PVCs are modeled with zero valued traffic parameters in one direction; all the `In' direction parameters for one frame relay PVC End-point or all the `Out' direction parameters for the other frame relay PVC Endpoint. In _____________________________ Out >>>>>>| |>>>>>>>> ______| Frame Relay Network |________ Out | | In <<<<<<|_____________________________|<<<<<<<< Frame Relay Frame Relay PVC PVC Endpoint Endpoint Figure 2, PVC Terminology 2) Go to the Frame Relay Connection Group.
.1.3.6.1.2.1.10.44.1.3.1,FRNETSERV-MIB::frPVCEndptEntry,,not-accessible,ifIndex:frPVCEndptDLCIIndex,current,,An entry in the Frame Relay PVC Endpoint table.
.1.3.6.1.2.1.10.44.1.3.1.1,FRNETSERV-MIB::frPVCEndptDLCIIndex,Integer32,not-accessible,,current,,The value of this object is equal to the DLCI value for this PVC end-point. The values are restricted to the legal range for the size of address field supported by the logical port (frLportAddrDLCILen).
.1.3.6.1.2.1.10.44.1.3.1.2,FRNETSERV-MIB::frPVCEndptInMaxFrameSize,Integer32,read-create,,current,,The value of this object is the size in octets of the largest frame relay information field for this PVC end-point in the ingress direction (into the frame relay network). The value of frPVCEndptInMaxFrameSize must be less than or equal to the corresponding ifMtu for this frame relay UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.3.1.3,FRNETSERV-MIB::frPVCEndptInBc,Integer32,read-create,,current,,The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this PVC end-point in the ingress direction (into the frame relay network). Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6). Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units.
.1.3.6.1.2.1.10.44.1.3.1.4,FRNETSERV-MIB::frPVCEndptInBe,Integer32,read-create,,current,,The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this PVC end-point in the ingress direction (into the frame relay network). Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6). Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units.
.1.3.6.1.2.1.10.44.1.3.1.5,FRNETSERV-MIB::frPVCEndptInCIR,Integer32,read-create,,current,,The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this PVC end- point in the ingress direction (into the frame relay network). Note that the max value of this range is lower than the max value allowed by Q.933 (2047 * 10**6).
.1.3.6.1.2.1.10.44.1.3.1.6,FRNETSERV-MIB::frPVCEndptOutMaxFrameSize,Integer32,read-create,,current,,The value of this object is the size in octets of the largest frame relay information field for this PVC end-point in the egress direction (out of the frame relay network). The value of frPVCEndptOutMaxFrameSize must be less than or equal to the corresponding ifMtu for this frame relay UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.3.1.7,FRNETSERV-MIB::frPVCEndptOutBc,Integer32,read-create,,current,,The value of this object is equal to the committed burst size (Bc) parameter (measured in bits) for this PVC end-point in the egress direction (out of the frame relay network). Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6). Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units.
.1.3.6.1.2.1.10.44.1.3.1.8,FRNETSERV-MIB::frPVCEndptOutBe,Integer32,read-create,,current,,The value of this object is equal to the excess burst size (Be) parameter (measured in bits) for this PVC end-point in the egress direction (out of the frame relay network). Note that the max value of this range is lower than the max value allowed by Q.933 (16383 * 10**6). Note that the value is encoded in bits whilst the Q.933 Link layer core parameters information element encodes this information using octet units.
.1.3.6.1.2.1.10.44.1.3.1.9,FRNETSERV-MIB::frPVCEndptOutCIR,Integer32,read-create,,current,,The value of this object is equal to the committed information rate (CIR) parameter (measured in bits per second) for this PVC end- point in the egress direction (out of the frame relay network). Note that the max value of this range is lower than the max value allowed by Q.933 (2047 * 10**6).
.1.3.6.1.2.1.10.44.1.3.1.10,FRNETSERV-MIB::frPVCEndptConnectIdentifier,Integer32,read-only,,current,,This object is used to associate PVC end-points as being part of one PVC segment connection. This value of this object is equal to the value of frPVCConnectIndex, which is used as one of the indices into the frPVCConnectTable. A connection that has been cross-connected via the FR/ATM PVC Service IWF cross-connect table will return the value zero when this object is read. In case of these interworked connections, the frPVCEndptAtmIwfConnIndex object must be accessed to select the entry in the FR/ATM PVC Service IWF cross-connect table. The value of this object is provided by the agent, after the associated entries in the frPVCConnectTable or frAtmIwfConnectionTable have been created.
.1.3.6.1.2.1.10.44.1.3.1.11,FRNETSERV-MIB::frPVCEndptRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create new rows in this table, modify existing rows, and to delete existing rows. To create a new PVC, the entries for the PVC segment end-points in the frPVCEndptTable must first be created. Next, the frPVCConnectTable is used to associate the frame relay PVC segment end-points. In order for the manager to have the necessary error diagnostics, the frPVCEndptRowStatus object must initially be set to `createAndWait(5)'. While the frPVCEndptRowStatus object is in the `createAndWait(5)' state, the manager can set each columnar object and get the necessary error diagnostics. The frPVCEndptRowStatus object may not be set to `active(1)' unless the following columnar objects exist in this row: frPVCEndptInMaxFrameSize, frPVCEndptInBc, frPVCEndptInBe, frPVCEndptInCIR, frPVCEndptOutMaxFrameSize, frPVCEndptOutBc, frPVCEndptOutBe, and frPVCEndptOutCIR.
.1.3.6.1.2.1.10.44.1.3.1.12,FRNETSERV-MIB::frPVCEndptRcvdSigStatus,INTEGER,read-only,,current,deleted(1):active(2):inactive(3):none(4),The value of this object identifies the PVC status received via the local in-channel signaling procedures for this PVC end-point. This object is only pertinent for interfaces that perform the bidirectional procedures. Each value has the following meaning: deleted(1): This PVC is not listed in the full status reports received from the user device. The object retains this value for as long as the PVC is not listed in the full status reports active(2): This PVC is reported as active, or operational, by the user device. inactive(3): This PVC is reported as inactive, or non-operational, by the user device. none(4): This interface is only using the network-side in-channel signaling procedures, so this object does not apply.
.1.3.6.1.2.1.10.44.1.3.1.13,FRNETSERV-MIB::frPVCEndptInFrames,Counter32,read-only,,current,,The number of frames received by the network (ingress) for this PVC end-point. This includes any frames discarded by the network due to submitting more than Bc + Be data or due to any network congestion recovery procedures.
.1.3.6.1.2.1.10.44.1.3.1.14,FRNETSERV-MIB::frPVCEndptOutFrames,Counter32,read-only,,current,,The number of frames sent by the network (egress) regardless of whether they are Bc or Be frames for this PVC end-point.
.1.3.6.1.2.1.10.44.1.3.1.15,FRNETSERV-MIB::frPVCEndptInDEFrames,Counter32,read-only,,current,,The number of frames received by the network (ingress) with the DE bit set to (1) for this PVC end-point.
.1.3.6.1.2.1.10.44.1.3.1.16,FRNETSERV-MIB::frPVCEndptInExcessFrames,Counter32,read-only,,current,,The number of frames received by the network (ingress) for this PVC end-point which were treated as excess traffic. Frames which are sent to the network with DE set to zero are treated as excess when more than Bc bits are submitted to the network during the Committed Information Rate Measurement Interval (Tc). Excess traffic may or may not be discarded at the ingress if more than Bc + Be bits are submitted to the network during Tc. Traffic discarded at the ingress is not recorded in frPVCEndptInExcessFrames. Frames which are sent to the network with DE set to one are also treated as excess traffic.
.1.3.6.1.2.1.10.44.1.3.1.17,FRNETSERV-MIB::frPVCEndptOutExcessFrames,Counter32,read-only,,current,,The number of frames sent by the network (egress) for this PVC end-point which were treated as excess traffic. (The DE bit may be set to one.)
.1.3.6.1.2.1.10.44.1.3.1.18,FRNETSERV-MIB::frPVCEndptInDiscards,Counter32,read-only,,current,,The number of frames received by the network (ingress) that were discarded due to traffic enforcement for this PVC end-point. Congestion discards are not counted in this object.
.1.3.6.1.2.1.10.44.1.3.1.19,FRNETSERV-MIB::frPVCEndptInOctets,Counter32,read-only,,current,,The number of octets received by the network (ingress) for this PVC end-point. This counter should only count octets from the beginning of the frame relay header field to the end of user data. If the network supporting frame relay can not count octets, then this count should be an approximation.
.1.3.6.1.2.1.10.44.1.3.1.20,FRNETSERV-MIB::frPVCEndptOutOctets,Counter32,read-only,,current,,The number of octets sent by the network (egress) for this PVC end-point. This counter should only count octets from the beginning of the frame relay header field to the end of user data. If the network supporting frame relay can not count octets, then this count should be an approximation.
.1.3.6.1.2.1.10.44.1.3.1.21,FRNETSERV-MIB::frPVCEndptInDiscardsDESet,Counter32,read-only,,current,,The number of frames received by the network (ingress) that were discarded with the DE bit set due to traffic enforcement for this PVC end-point. Congestion discards are not counted in this object.
.1.3.6.1.2.1.10.44.1.3.1.22,FRNETSERV-MIB::frPVCEndptInFramesFECNSet,Counter32,read-only,,current,,The number of frames received by the network (ingress) that have the FECN bit set for this PVC end-point.
.1.3.6.1.2.1.10.44.1.3.1.23,FRNETSERV-MIB::frPVCEndptOutFramesFECNSet,Counter32,read-only,,current,,The number of frames sent by the network (egress) that have the FECN bit set for this PVC end- point.
.1.3.6.1.2.1.10.44.1.3.1.24,FRNETSERV-MIB::frPVCEndptInFramesBECNSet,Counter32,read-only,,current,,The number of frames received by the network (ingress) that have the BECN bit set for this PVC end-point.
.1.3.6.1.2.1.10.44.1.3.1.25,FRNETSERV-MIB::frPVCEndptOutFramesBECNSet,Counter32,read-only,,current,,The number of frames sent by the network (egress) that have the BECN bit set for this PVC end- point.
.1.3.6.1.2.1.10.44.1.3.1.26,FRNETSERV-MIB::frPVCEndptInCongDiscards,Counter32,read-only,,current,,The number of frames received by the network (ingress) that were discarded due to input buffer congestion, rather than traffic enforcement, for this PVC end-point.
.1.3.6.1.2.1.10.44.1.3.1.27,FRNETSERV-MIB::frPVCEndptInDECongDiscards,Counter32,read-only,,current,,The number of frames counted by frPVCEndptInCongDiscards with the DE bit set to (1).
.1.3.6.1.2.1.10.44.1.3.1.28,FRNETSERV-MIB::frPVCEndptOutCongDiscards,Counter32,read-only,,current,,The number of frames sent by the network (egress) that were discarded due to output buffer congestion for this PVC end-point.
.1.3.6.1.2.1.10.44.1.3.1.29,FRNETSERV-MIB::frPVCEndptOutDECongDiscards,Counter32,read-only,,current,,The number of frames counted by frPVCEndptOutCongDiscards with the DE bit set to (1).
.1.3.6.1.2.1.10.44.1.3.1.30,FRNETSERV-MIB::frPVCEndptOutDEFrames,Counter32,read-only,,current,,The number of frames sent by the network (egress) with the DE bit set to (1) for this PVC end- point.
.1.3.6.1.2.1.10.44.1.3.1.31,FRNETSERV-MIB::frPVCEndptAtmIwfConnIndex,Integer32,read-only,,current,,This object contains the index value of the FR/ATM cross-connect table entry used to link the frame relay PVC with an ATM PVC. Each row of the frPVCEndptTable that is not cross-connected with an ATM PVC must return the value zero when this object is read. The value of this object is initialized by the agent after the associated entries in the frAtmIwfConnectionTable have been created. The value of this object is reset to zero following destruction of the associated entry in the frAtmIwfConnectionTable
.1.3.6.1.2.1.10.44.1.4,FRNETSERV-MIB::frPVCConnectIndexValue,INTEGER,read-only,,current,,This object returns a hint to be used for frPVCConnectIndex when creating entries in the frPVCConnectTable. The value 0 indicates that no unassigned entries are available. To obtain the frPVCConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent must modify the value to the next unassigned index to prevent assignment of the same value to multiple management systems. A management system should repeat the read to obtain a new value should an attempt to create the new row using the previously returned hint fail.
.1.3.6.1.2.1.10.44.1.5,FRNETSERV-MIB::frPVCConnectTable,,not-accessible,,current,,The Frame Relay PVC Connect Table is used to model the bi-directional PVC segment flows including: point-to-point PVCs, point-to- multipoint PVCs, and multipoint-to-multipoint PVCs. This table has read-create access and is used to associate PVC end-points together as belonging to one connection. The frPVCConnectIndex is used to associate all the bi-directional flows. Not all implementations will support the capability of creating/modifying/deleting PVCs using SNMP as a feature of frame relay CNM service. Once the entries in the frPVCEndptTable are created, the following step are used to associate the PVC end-points as belonging to one PVC connection: 1) Obtain a unique frPVCConnectIndex using the frPVCConnectIndexValue object. 2) Connect the PVC segment endpoints together with the applicable frPVCConnectIndex value obtained via frPVCConnectIndexValue. The entries in this table are created by using the frPVCConnectRowStatus object. 3) The agent will provide the value of the corresponding instances of frPVCEndptConnectIdentifier with the frPVCConnectIndex value. 4) Set frPVCConnectAdminStatus to `active(1)' in all rows for this PVC segment to turn the PVC on. For example, the Frame Relay PVC Connection Group models a bi-directional, point-to-point PVC segment as one entry in this table. Frame Relay Frame Relay Network Network Low Port High Port __________________________________ | | _____| >> from low to high PVC flow >> |_____ | << from high to low PVC flow << | |__________________________________| The terms low and high are chosen to represent numerical ordering of a PVC segment's endpoints for representation in this table. That is, the endpoint with the lower value of ifIndex is termed 'low', while the opposite endpoint of the segment is termed 'high'. This terminology is to provide directional information; for example the frPVCConnectL2hOperStatus and frPVCConnectH2lOperStatus as illustrated above. If the Frame Relay Connection table is used to model a unidirectional PVC, then one direction (either from low to high or from high to low) has its Operational Status equal to down. A PVC segment is a portion of a PVC that traverses one Frame Relay Network, and a PVC segment is identified by its two end-points (UNI/NNI logical port index value and DLCI index value) through one Frame Relay Network.
.1.3.6.1.2.1.10.44.1.5.1,FRNETSERV-MIB::frPVCConnectEntry,,not-accessible,frPVCConnectIndex:frPVCConnectLowIfIndex:frPVCConnectLowDLCIIndex:frPVCConnectHighIfIndex:frPVCConnectHighDLCIIndex,current,,An entry in the Frame Relay PVC Connect table. This entry is used to model a PVC segment in two directions.
.1.3.6.1.2.1.10.44.1.5.1.1,FRNETSERV-MIB::frPVCConnectIndex,Integer32,not-accessible,,current,,The value of this object is equal to the frPVCConnectIndexValue obtained to uniquely identify this PVC segment connection.
.1.3.6.1.2.1.10.44.1.5.1.2,FRNETSERV-MIB::frPVCConnectLowIfIndex,Integer32,not-accessible,,current,,The value of this object is equal to IF-MIB ifIndex value of the UNI/NNI logical port for this PVC segment. The term low implies that this PVC segment end-point has the numerically lower ifIndex value than the connected/associated PVC segment end-point. RFC 1604 permitted a zero value for this object to identify termination at a non-frame relay interface. However, this cross-connect table is limited to frame relay connections. See the frame relay/ATM IWF MIB [28] for the cross-connect table used for those types of connections.
.1.3.6.1.2.1.10.44.1.5.1.3,FRNETSERV-MIB::frPVCConnectLowDLCIIndex,Integer32,not-accessible,,current,,The value of this object is equal to the DLCI value for this end-point of the PVC segment.
.1.3.6.1.2.1.10.44.1.5.1.4,FRNETSERV-MIB::frPVCConnectHighIfIndex,Integer32,not-accessible,,current,,The value of this object is equal to IF-MIB ifIndex value for the UNI/NNI logical port for this PVC segment. The term high implies that this PVC segment end-point has the numerically higher ifIndex value than the connected/associated PVC segment end-point.
.1.3.6.1.2.1.10.44.1.5.1.5,FRNETSERV-MIB::frPVCConnectHighDLCIIndex,Integer32,not-accessible,,current,,The value of this object is equal to the egress DLCI value for this end-point of the PVC segment.
.1.3.6.1.2.1.10.44.1.5.1.6,FRNETSERV-MIB::frPVCConnectAdminStatus,INTEGER,read-create,,current,active(1):inactive(2):testing(3),The value of this object identifies the desired administrative status of this bi-directional PVC segment. The active(1) state means the PVC segment is currently operational; the inactive(2) state means the PVC segment is currently not operational; the testing(3) state means the PVC segment is currently undergoing a test. This state is set by an administrative entity. This value affects the PVC status indicated across the ingress NNI/UNI of both end-points of the bi- directional PVC segment. When a PVC segment connection is created using this table, this object is initially set to `inactive(2)'. After the frPVCConnectRowStatus object is set to `active(1)' (and the corresponding/associated entries in the frPVCEndptTable have their frPVCEndptRowStatus object set to `active(1)'), the frPVCConnectAdminStatus object may be set to `active(1)' to turn on the PVC segment connection.
.1.3.6.1.2.1.10.44.1.5.1.7,FRNETSERV-MIB::frPVCConnectL2hOperStatus,INTEGER,read-only,,current,active(1):inactive(2):testing(3):unknown(4),The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the low to high direction). This value affects the PVC status indicated across the ingress NNI/UNI (low side) of the PVC segment. The values mean: active(1) - PVC is currently operational inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure. testing(3) - PVC is currently undergoing a test. This may be because of an underlying frLport or DS1 undergoing a test. unknown(4) - the status of the PVC currently can not be determined.
.1.3.6.1.2.1.10.44.1.5.1.8,FRNETSERV-MIB::frPVCConnectH2lOperStatus,INTEGER,read-only,,current,active(1):inactive(2):testing(3):unknown(4),The value of this object identifies the current operational status of the PVC segment connection in one direction; (i.e., in the high to low direction).. This value affects the PVC status indicated across the ingress NNI/UNI (high side) of the PVC segment. The values mean: active(1) - PVC is currently operational inactive(2) - PVC is currently not operational. This may be because of an underlying LMI or DS1 failure. testing(3) - PVC is currently undergoing a test. This may be because of an underlying frLport or DS1 undergoing a test. unknown(4) - the status of the PVC currently can not be determined.
.1.3.6.1.2.1.10.44.1.5.1.9,FRNETSERV-MIB::frPVCConnectL2hLastChange,TimeTicks,read-only,,current,,The value of the Interface MIB's sysUpTime object at the time this PVC segment entered its current operational state in the low to high direction. If the current state was entered prior to the last re-initialization of the FRS agent, then this object contains a zero value.
.1.3.6.1.2.1.10.44.1.5.1.10,FRNETSERV-MIB::frPVCConnectH2lLastChange,TimeTicks,read-only,,current,,The value of the Interface MIB's sysUpTime object at the time this PVC segment entered its current operational state in the high to low direction. If the current state was entered prior to the last re-initialization of the FRS agent, then this object contains a zero value.
.1.3.6.1.2.1.10.44.1.5.1.11,FRNETSERV-MIB::frPVCConnectRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry in the frPVCConnectTable. This variable is used to create new connections for the PVC end-points and to change existing connections of the PVC end- points. This object must be initially set to `createAndWait(5)'. In this state, the agent checks the parameters in the associated entries in the frPVCEndptTable to verify that the PVC end- points can be connected (i.e., the In parameters for one PVC end-point are equal to the Out parameters for the other PVC end-point). This object can not be set to `active(1)' unless the following columnar object exists in this row: frPVCConnectAdminStatus. The agent also supplies the associated value of frPVCConnectIndex for the frPVCEndptConnectIdentifier instances. To turn on a PVC segment connection, the frPVCConnectAdminStatus is set to `active(1)'.
.1.3.6.1.2.1.10.44.1.5.1.12,FRNETSERV-MIB::frPVCConnectUserName,OCTET,read-create,,current,,This is a service user assigned textual representation of a PVC.
.1.3.6.1.2.1.10.44.1.5.1.13,FRNETSERV-MIB::frPVCConnectProviderName,OCTET,read-create,,current,,This is a system supplied textual representation of PVC. It is assigned by the service provider.
.1.3.6.1.2.1.10.44.1.6,FRNETSERV-MIB::frAccountPVCTable,,not-accessible,,current,,The Frame Relay Accounting PVC table. This table is used to perform accounting on a PVC segment end-point basis.
.1.3.6.1.2.1.10.44.1.6.1,FRNETSERV-MIB::frAccountPVCEntry,,not-accessible,ifIndex:frAccountPVCDLCIIndex,current,,An entry in the Frame Relay Accounting PVC table.
.1.3.6.1.2.1.10.44.1.6.1.1,FRNETSERV-MIB::frAccountPVCDLCIIndex,Integer32,not-accessible,,current,,The value of this object is equal to the DLCI value for this PVC segment end-point.
.1.3.6.1.2.1.10.44.1.6.1.2,FRNETSERV-MIB::frAccountPVCSegmentSize,Integer32,read-only,,current,,The value of this object is equal to the Segment Size for this PVC segment end-point.
.1.3.6.1.2.1.10.44.1.6.1.3,FRNETSERV-MIB::frAccountPVCInSegments,Counter32,read-only,,current,,The value of this object is equal to the number of segments received by this PVC segment end- point.
.1.3.6.1.2.1.10.44.1.6.1.4,FRNETSERV-MIB::frAccountPVCOutSegments,Counter32,read-only,,current,,The value of this object is equal to the number of segments sent by this PVC segment end-point.
.1.3.6.1.2.1.10.44.1.7,FRNETSERV-MIB::frAccountLportTable,,not-accessible,,current,,The Frame Relay Accounting Logical Port table. This table is used to perform accounting on a UNI/NNI Logical Port basis.
.1.3.6.1.2.1.10.44.1.7.1,FRNETSERV-MIB::frAccountLportEntry,,not-accessible,ifIndex,current,,An entry in the Frame Relay Accounting Logical Port table.
.1.3.6.1.2.1.10.44.1.7.1.1,FRNETSERV-MIB::frAccountLportSegmentSize,Integer32,read-only,,current,,The value of this object is equal to the Segment Size for this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.7.1.2,FRNETSERV-MIB::frAccountLportInSegments,Counter32,read-only,,current,,The value of this object is equal to the number of segments received by this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.1.7.1.3,FRNETSERV-MIB::frAccountLportOutSegments,Counter32,read-only,,current,,The value of this object is equal to the number of segments sent by this UNI/NNI logical port.
.1.3.6.1.2.1.10.44.2,FRNETSERV-MIB::frnetservTraps,,,,,,
.1.3.6.1.2.1.10.44.2.0,FRNETSERV-MIB::frnetservTrapsPrefix,,,,,,
.1.3.6.1.2.1.10.44.2.0.2,FRNETSERV-MIB::frPVCConnectStatusNotif,,,,,,This notification indicates that the indicated PVC has changed state. This notification is not sent if an FR-UNI changes state; a linkDown or linkUp notification should be sent instead. The first instance of frPVCEndptRcvdSigStatus is for the endpoint with LowIfIndex, LowDLCIIndex. The second instance of frPVCEndptRcvdSigStatus is for the endpoint with HighIfIndex, HighDLCIIndex
.1.3.6.1.2.1.10.44.2.1,FRNETSERV-MIB::frPVCConnectStatusChange,,,,,,Refer to the description of the frPVCConnectStatusNotif notification that has replaced this notification. The notification is deprecated due to the incorrect inclusion of index values and to take advantage of the trap prefix for automatic conversion from SMIv2 to SMIv1 by making the one but last sub-ID a zero (i.e. the so-called trap prefix).
.1.3.6.1.2.1.10.44.3,FRNETSERV-MIB::frnetservConformance,,,,,,
.1.3.6.1.2.1.10.44.3.1,FRNETSERV-MIB::frnetservGroups,,,,,,
.1.3.6.1.2.1.10.44.3.1.1,FRNETSERV-MIB::frnetservLportGroup,,,,,,A collection of objects providing information applicable to a Frame Relay Logical Port. This group has been deprecated to eliminate reference to the object frLportVCSigPointer. Use the new group frnetservLportGroup2 as a replacement for this group.
.1.3.6.1.2.1.10.44.3.1.2,FRNETSERV-MIB::frnetservMgtVCSigGroup,,,,,,A collection of objects providing information applicable to the Local In-Channel Signaling Procedures used for a UNI/NNI logical port.
.1.3.6.1.2.1.10.44.3.1.3,FRNETSERV-MIB::frnetservPVCEndptGroup,,,,,,A collection of objects providing information applicable to a Frame Relay PVC end-point.
.1.3.6.1.2.1.10.44.3.1.4,FRNETSERV-MIB::frnetservPVCConnectGroup,,,,,,A collection of objects providing information applicable to a Frame Relay PVC connection.
.1.3.6.1.2.1.10.44.3.1.5,FRNETSERV-MIB::frnetservAccountPVCGroup,,,,,,A collection of objects providing accounting information application to a Frame Relay PVC end- point.
.1.3.6.1.2.1.10.44.3.1.6,FRNETSERV-MIB::frnetservAccountLportGroup,,,,,,A collection of objects providing accounting information application to a Frame Relay logical port.
.1.3.6.1.2.1.10.44.3.1.7,FRNETSERV-MIB::frnetservLportGroup2,,,,,,A collection of objects providing information applicable to a Frame Relay Logical Port. This new version of the Logical Port Group eliminates the frLportVCSigPointer and adds support for fragmentation.
.1.3.6.1.2.1.10.44.3.1.8,FRNETSERV-MIB::frnetservPVCEndptGroup2,,,,,,Additions to the PVC end-point group. These additions provide new frame counters to track frame loss. In addition, the new FR/ATM IWF MIB cross-connect index is included.
.1.3.6.1.2.1.10.44.3.1.9,FRNETSERV-MIB::frnetservPVCConnectNamesGroup,,,,,,Additions to the PVC Connect Group.
.1.3.6.1.2.1.10.44.3.1.10,FRNETSERV-MIB::frnetservLportAdminGroup,,,,,,Administrative (R/W) objects for creating a switch logical port.
.1.3.6.1.2.1.10.44.3.1.11,FRNETSERV-MIB::frnetservMgtVCSigAdminGroup,,,,,,A collection of objects providing information applicable to the Local In-Channel Signaling Procedures used for a UNI/NNI logical port.
.1.3.6.1.2.1.10.44.3.1.12,FRNETSERV-MIB::frnetservPVCNotifGroup,,,,,,Deprecated notification group. The frPVCConnectStatusChange notification was flawed because it included redundant indexes and was not properly encoded for SMIv1 conversion.
.1.3.6.1.2.1.10.44.3.1.13,FRNETSERV-MIB::frnetservPVCNotifGroup2,,,,,,A collection of notifications that apply to frame relay PVC Connections 
.1.3.6.1.2.1.10.44.3.2,FRNETSERV-MIB::frnetservCompliances,,,,,,
.1.3.6.1.2.1.10.44.3.2.1,FRNETSERV-MIB::frnetservCompliance,,,,,,The compliance statement for SNMP entities which have Frame Relay Network Service Interfaces. This compliance statement has been deprecated in favor of frnetservCompliance2. The new compliance module expands the mandatory groups to include notification and other new objects.
.1.3.6.1.2.1.10.44.3.2.2,FRNETSERV-MIB::frnetservCompliance2,,,,,,The compliance statement for SNMP entities which have Frame Relay Network Service Interfaces. The distinction between 'service' and 'switch' is that a 'switch' is configured via this MIB. Hence, the various read/write objects have write capability. A 'service' represents a passive monitor-only customer network management interface. The various read/write objects are restricted to read-only capability.
.1.3.6.1.2.1.10.44.3.2.3,FRNETSERV-MIB::frnetSwitchCompliance,,,,,,The compliance statement for SNMP entities which have Frame Relay Network Switch objects. The distinction between 'service' and 'switch' is that a 'switch' is configured via this MIB. Hence, the various read/write objects have write capability. A 'service' represents a passive monitor-only customer network management interface. The various read/write objects are restricted to read-only capability.
.1.3.6.1.2.1.10.45,DOT12-IF-MIB::dot12MIB,,,,,,This MIB module describes objects for managing IEEE 802.12 interfaces.
.1.3.6.1.2.1.10.45.1,DOT12-IF-MIB::dot12MIBObjects,,,,,,
.1.3.6.1.2.1.10.45.1.1,DOT12-IF-MIB::dot12ConfigTable,,not-accessible,,current,,Configuration information for a collection of 802.12 interfaces attached to a particular system.
.1.3.6.1.2.1.10.45.1.1.1,DOT12-IF-MIB::dot12ConfigEntry,,not-accessible,ifIndex,current,,Configuration for a particular interface to an 802.12 medium.
.1.3.6.1.2.1.10.45.1.1.1.1,DOT12-IF-MIB::dot12CurrentFramingType,INTEGER,read-only,,current,frameType88023(1):frameType88025(2):frameTypeUnknown(3),When dot12DesiredFramingType is one of 'frameType88023' or 'frameType88025', this is the type of framing asserted by the interface. When dot12DesiredFramingType is 'frameTypeEither', dot12CurrentFramingType shall be one of 'frameType88023' or 'frameType88025' when the dot12Status is 'opened'. When the dot12Status is anything other than 'opened', dot12CurrentFramingType shall take the value of 'frameTypeUnknown'.
.1.3.6.1.2.1.10.45.1.1.1.2,DOT12-IF-MIB::dot12DesiredFramingType,INTEGER,read-write,,current,frameType88023(1):frameType88025(2):frameTypeEither(3),The type of framing which will be requested by the interface during the next interface MAC initialization or open action. In master mode, this is the framing mode which will be granted by the interface. Note that for a master mode interface, this object must be equal to 'frameType88023' or 'frameType88025', since a master mode interface cannot grant 'frameTypeEither'.
.1.3.6.1.2.1.10.45.1.1.1.3,DOT12-IF-MIB::dot12FramingCapability,INTEGER,read-only,,current,frameType88023(1):frameType88025(2):frameTypeEither(3),The type of framing this interface is capable of supporting.
.1.3.6.1.2.1.10.45.1.1.1.4,DOT12-IF-MIB::dot12DesiredPromiscStatus,INTEGER,read-write,,current,singleAddressMode(1):promiscuousMode(2),This object is used to select the promiscuous mode that this interface will request in the next training packet issued on this interface. Whether the repeater grants the requested mode must be verified by examining the state of the PP bits in the corresponding instance of dot12LastTrainingConfig. In master mode, this object controls whether or not promiscuous mode will be granted by the interface when requested by the lower level device. Note that this object indicates the desired mode for the next time the interface trains. The currently active mode will be reflected in dot12LastTrainingConfig and in ifPromiscuousMode.
.1.3.6.1.2.1.10.45.1.1.1.5,DOT12-IF-MIB::dot12TrainingVersion,INTEGER,read-only,,current,,The value that will be used in the version bits (vvv bits) in training frames on this interface. This is the highest version number supported by this MAC.
.1.3.6.1.2.1.10.45.1.1.1.6,DOT12-IF-MIB::dot12LastTrainingConfig,OCTET,read-only,,current,,This 16 bit field contains the configuration bits from the most recent error-free training frame received during training on this interface. Training request frames are received when in master mode, while training response frames are received in slave mode. On master mode interfaces, this object contains the contents of the requested configuration field of the most recent training request frame. On slave mode interfaces, this object contains the contents of the allowed configuration field of the most recent training response frame. The format of the current version of this field is described in section 3.8. Please refer to the most recent version of the IEEE 802.12 standard for the most up-to-date definition of the format of this object.
.1.3.6.1.2.1.10.45.1.1.1.7,DOT12-IF-MIB::dot12Commands,INTEGER,read-write,,current,noOp(1):open(2):reset(3):close(4),If the current value of dot12Status is 'closed', setting the value of this object to 'open' will change the corresponding instance of MIB-II's ifAdminStatus to 'up', cause this interface to enter the 'opening' state, and will cause training to be initiated on this interface. The progress and success of the open is given by the values of the dot12Status object. Setting this object to 'open' when dot12Status has a value other than 'closed' has no effect. Setting the corresponding instance of ifAdminStatus to 'up' when the current value of dot12Status is 'closed' will have the same effect as setting this object to 'open'. Setting ifAdminStatus to 'up' when dot12Status has a value other than 'closed' has no effect. Setting the value of this object to 'close' will move this interface into the 'closed' state and cause all transmit and receive actions to stop. This object will then have to be set to 'open' in order to reinitiate training. Setting the corresponding instance of ifAdminStatus to 'down' will have the same effect as setting this object to 'close'. Setting the value of this object to 'reset' when the current value of dot12Status has a value other than 'closed' will reset the interface. On a reset, all MIB counters should retain their values. This will cause the MAC to initiate an acInitializeMAC action as specified in IEEE 802.12. This will cause training to be reinitiated on this interface. Setting this object to 'reset' when dot12Status has a value of 'closed' has no effect. Setting this object to 'reset' has no effect on the corresponding instance of ifAdminStatus. Setting the value of this object to 'noOp' has no effect. When read, this object will always have a value of 'noOp'.
.1.3.6.1.2.1.10.45.1.1.1.8,DOT12-IF-MIB::dot12Status,INTEGER,read-only,,current,opened(1):closed(2):opening(3):openFailure(5):linkFailure(6),The current interface status with respect to training. One of the following values: opened - Training has completed successfully. closed - MAC has been disabled by setting dot12Commands to 'close'. opening - MAC is in training. Training signals have been received. openFailure - Passed 24 error-free packets, but there is a problem, noted in the training configuration bits (dot12LastTrainingConfig). linkFailure - Training signals not received, or could not pass 24 error-free packets. Whenever the dot12Commands object is set to 'close' or ifAdminStatus is set to 'down', the MAC will go silent, dot12Status will be 'closed', and ifOperStatus will be 'down'. When the value of this object is equal to 'closed' and the dot12Commands object is set to 'open' or the ifAdminStatus object is set to 'up', training will be initiated on this interface. When the value of this object is not equal to 'closed' and the dot12Commands object is set to 'reset', training will be reinitiated on this interface. Note that sets of some other objects (e.g. dot12ControlMode) or external events (e.g. MAC protocol violations) may also cause training to be reinitiated on this interface. When training is initiated or reinitiated on an interface, the end node will send Training_Up to the master and initially go to the 'linkFailure' state and ifOperStatus will go to 'down'. When the master sends back Training_Down, dot12Status will change to the 'opening' state, and training packets will be transferred. After all of the training packets have been passed, dot12Status will change to 'linkFailure' if 24 consecutive error-free packets were not passed, 'opened' if 24 consecutive error-free packets were passed and the training configuration bits were OK, or 'openFailure' if there were 24 consecutive error-free packets, but there was a problem with the training configuration bits. When in the 'openFailure' state, the dot12LastTrainingConfig object will contain the configuration bits from the last training packet which can be examined to determine the exact reason for the training configuration failure. If training did not succeed (dot12Status is 'linkFailure' or 'openFailure), the entire process will be restarted after MAC_Retraining_Delay_Timer seconds. If training does succeed (dot12Status changes to 'opened'), ifOperStatus will change to 'up'. If training does not succeed (dot12Status changes to 'linkFailure' or 'openFailure'), ifOperStatus will remain 'down'.
.1.3.6.1.2.1.10.45.1.1.1.9,DOT12-IF-MIB::dot12ControlMode,INTEGER,read-write,,current,masterMode(1):slaveMode(2):learn(3),This object is used to configure and report whether or not this interface is operating in master mode. In a Demand Priority network, end node interfaces typically operate in slave mode, while switch interfaces may control the Demand Priority protocol and operate in master mode. This object may be implemented as a read-only object by those agents and interfaces that do not implement software control of master mode. In particular, interfaces that cannot operate in master mode, and interfaces on which master mode is controlled by a pushbutton on the device, should implement this object read-only. Some interfaces do not require network management configuration of this feature and can autosense whether to use master mode or slave mode. The value 'learn' is used for that purpose. While autosense is taking place, the value 'learn' is returned. A network management operation which modifies the value of dot12ControlMode causes the interface to retrain.
.1.3.6.1.2.1.10.45.1.2,DOT12-IF-MIB::dot12StatTable,,not-accessible,,current,,Statistics for a collection of 802.12 interfaces attached to a particular system.
.1.3.6.1.2.1.10.45.1.2.1,DOT12-IF-MIB::dot12StatEntry,,not-accessible,ifIndex,current,,Statistics for a particular interface to an 802.12 medium. The receive statistics in this table apply only to packets received by this station (i.e., packets whose destination address is either the local station address, the broadcast address, or a multicast address that this station is receiving, unless the station is in promiscuous mode).
.1.3.6.1.2.1.10.45.1.2.1.1,DOT12-IF-MIB::dot12InHighPriorityFrames,Counter32,read-only,,current,,This object is a count of high priority frames that have been received on this interface. Includes both good and bad high priority frames, as well as high priority training frames. Does not include normal priority frames which were priority promoted.
.1.3.6.1.2.1.10.45.1.2.1.2,DOT12-IF-MIB::dot12InHighPriorityOctets,Counter32,read-only,,current,,This object is a count of the number of octets contained in high priority frames that have been received on this interface. This counter is incremented by OctetCount for each frame received on this interface which is counted by dot12InHighPriorityFrames. Note that this counter will roll over very quickly. It is provided for backward compatibility for Network Management protocols that do not support 64 bit counters (e.g. SNMP version 1).
.1.3.6.1.2.1.10.45.1.2.1.3,DOT12-IF-MIB::dot12InNormPriorityFrames,Counter32,read-only,,current,,This object is a count of normal priority frames that have been received on this interface. Includes both good and bad normal priority frames, as well as normal priority training frames and normal priority frames which were priority promoted.
.1.3.6.1.2.1.10.45.1.2.1.4,DOT12-IF-MIB::dot12InNormPriorityOctets,Counter32,read-only,,current,,This object is a count of the number of octets contained in normal priority frames that have been received on this interface. This counter is incremented by OctetCount for each frame received on this interface which is counted by dot12InNormPriorityFrames. Note that this counter will roll over very quickly. It is provided for backward compatibility for Network Management protocols that do not support 64 bit counters (e.g. SNMP version 1).
.1.3.6.1.2.1.10.45.1.2.1.5,DOT12-IF-MIB::dot12InIPMErrors,Counter32,read-only,,current,,This object is a count of the number of frames that have been received on this interface with an invalid packet marker and no PMI errors. A repeater will write an invalid packet marker to the end of a frame containing errors as it is forwarded through the repeater to the other ports. This counter is incremented by one for each frame received on this interface which has had an invalid packet marker added to the end of the frame.
.1.3.6.1.2.1.10.45.1.2.1.6,DOT12-IF-MIB::dot12InOversizeFrameErrors,Counter32,read-only,,current,,This object is a count of oversize frames received on this interface. This counter is incremented by one for each frame received on this interface whose OctetCount is larger than the maximum legal frame size. The frame size which causes this counter to increment is dependent on the current framing type.
.1.3.6.1.2.1.10.45.1.2.1.7,DOT12-IF-MIB::dot12InDataErrors,Counter32,read-only,,current,,This object is a count of errored frames received on this interface. This counter is incremented by one for each frame received on this interface with any of the following errors: bad FCS (with no IPM), PMI errors (excluding frames with an IPM as the only PMI error), undersize, bad start of frame delimiter, or bad end of packet marker. Does not include frames counted by dot12InIPMErrors, dot12InNullAddressedFrames, or dot12InOversizeFrameErrors. This counter indicates problems with the cable directly attached to this interface, while dot12InIPMErrors indicates problems with remote cables.
.1.3.6.1.2.1.10.45.1.2.1.8,DOT12-IF-MIB::dot12InNullAddressedFrames,Counter32,read-only,,current,,This object is a count of null addressed frames received on this interface. This counter is incremented by one for each frame received on this interface with a destination MAC address consisting of all zero bits. Both void and training frames are included in this counter. Note that since this station would normally not receive null addressed frames, this counter is only incremented when this station is operating in promiscuous mode or in training.
.1.3.6.1.2.1.10.45.1.2.1.9,DOT12-IF-MIB::dot12OutHighPriorityFrames,Counter32,read-only,,current,,This counter is incremented by one for each high priority frame successfully transmitted out this interface.
.1.3.6.1.2.1.10.45.1.2.1.10,DOT12-IF-MIB::dot12OutHighPriorityOctets,Counter32,read-only,,current,,This counter is incremented by OctetCount for each frame counted by dot12OutHighPriorityFrames. Note that this counter will roll over very quickly. It is provided for backward compatibility for Network Management protocols that do not support 64 bit counters (e.g. SNMP version 1).
.1.3.6.1.2.1.10.45.1.2.1.11,DOT12-IF-MIB::dot12TransitionIntoTrainings,Counter32,read-only,,current,,This object is a count of the number of times this interface has entered the training state. This counter is incremented by one each time dot12Status transitions to 'linkFailure' from any state other than 'opening' or 'openFailure'.
.1.3.6.1.2.1.10.45.1.2.1.12,DOT12-IF-MIB::dot12HCInHighPriorityOctets,Counter64,read-only,,current,,This object is a count of the number of octets contained in high priority frames that have been received on this interface. This counter is incremented by OctetCount for each frame received on this interface which is counted by dot12InHighPriorityFrames. This counter is a 64 bit version of dot12InHighPriorityOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2).
.1.3.6.1.2.1.10.45.1.2.1.13,DOT12-IF-MIB::dot12HCInNormPriorityOctets,Counter64,read-only,,current,,This object is a count of the number of octets contained in normal priority frames that have been received on this interface. This counter is incremented by OctetCount for each frame received on this interface which is counted by dot12InNormPriorityFrames. This counter is a 64 bit version of dot12InNormPriorityOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2).
.1.3.6.1.2.1.10.45.1.2.1.14,DOT12-IF-MIB::dot12HCOutHighPriorityOctets,Counter64,read-only,,current,,This counter is incremented by OctetCount for each frame counted by dot12OutHighPriorityFrames. This counter is a 64 bit version of dot12OutHighPriorityOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2).
.1.3.6.1.2.1.10.45.2,DOT12-IF-MIB::dot12Conformance,,,,,,
.1.3.6.1.2.1.10.45.2.1,DOT12-IF-MIB::dot12Compliances,,,,,,
.1.3.6.1.2.1.10.45.2.1.1,DOT12-IF-MIB::dot12Compliance,,,,,,The compliance statement for managed network entities that have 802.12 interfaces.
.1.3.6.1.2.1.10.45.2.2,DOT12-IF-MIB::dot12Groups,,,,,,
.1.3.6.1.2.1.10.45.2.2.1,DOT12-IF-MIB::dot12ConfigGroup,,,,,,A collection of objects for managing the status and configuration of IEEE 802.12 interfaces.
.1.3.6.1.2.1.10.45.2.2.2,DOT12-IF-MIB::dot12StatsGroup,,,,,,A collection of objects providing statistics for IEEE 802.12 interfaces.
.1.3.6.1.2.1.10.46,IPOA-MIB::ipoaMIB,,,,,,This module defines a portion of the management information base (MIB) for managing Classical IP and ARP over ATM entities.
.1.3.6.1.2.1.10.46.1,IPOA-MIB::ipoaObjects,,,,,,
.1.3.6.1.2.1.10.46.1.1,IPOA-MIB::ipoaLisTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether ipoaLisCreate and ipoaLisDelete traps should be generated by this system. By default, this object should have the value enabled(1) for systems where ATMARP Servers are present and disabled(2) on systems where only clients reside.
.1.3.6.1.2.1.10.46.1.2,IPOA-MIB::ipoaLisTable,,not-accessible,,current,,There is one entry in this table for every Logical IP Subnet (LIS) of which this system is a member. The bulk of the objects in an ipoaLisEntry exists to control ATMARP for a particular LIS. In a PVC only environment it is implementation dependent as to whether this table should be supported.
.1.3.6.1.2.1.10.46.1.2.1,IPOA-MIB::ipoaLisEntry,,not-accessible,ipoaLisSubnetAddr,current,,Information about a single LIS of which this system is a member. Membership in a LIS is independent of the actual ATM interfaces being used. The ipoaLisTable defines all LISs that a system is a member of. The ipAddrTable and the ipoaClientTable provides the mapping from local IP address to ATM interface. The ipoaLisIfMappingTable provides the mappings between Logical IP Subnets and interfaces. The ipoaLisTable is indexed by ipoaLisSubnetAddr (IP subnet address). An entry in the ipoaLisTable should exist for each ipAddrEntry that is associated with an ATM related interface used for Classical IP and ARP over ATM traffic. Its ipAdEntAddr and ipAdEntNetMask when ANDed together should equal the ipoaLisSubnetAddr of the corresponding ipoaLisEntry.
.1.3.6.1.2.1.10.46.1.2.1.1,IPOA-MIB::ipoaLisSubnetAddr,IpAddress,read-only,,current,,The IP subnet address associated with this LIS.
.1.3.6.1.2.1.10.46.1.2.1.2,IPOA-MIB::ipoaLisDefaultMtu,Integer32,read-create,,current,,The default MTU used within this LIS. Note that the actual MTU used for a VC between two members of the LIS may be negotiated during connection setup and may be different than this value. The ipoaVcNegotiatedMtu object indicates the actual MTU in use for a particular VC.
.1.3.6.1.2.1.10.46.1.2.1.3,IPOA-MIB::ipoaLisDefaultEncapsType,INTEGER,read-create,,current,llcSnap(1):vcMuxed(2):other(3),The default encapsulation to use on VCs created for this LIS. Note that the actual encapsulation type may be negotiated during connection setup and may be different than this value. The ipoaVcNegotiatedEncapsType object indicates the actual encapsulation in use for a particular VC.
.1.3.6.1.2.1.10.46.1.2.1.4,IPOA-MIB::ipoaLisInactivityTimer,Integer32,read-create,,current,,The time, in seconds, before a call established for an ipNetToMediaEntry on a client will timeout due to no traffic being passed on the VC. A value of 0 implies no time out.
.1.3.6.1.2.1.10.46.1.2.1.5,IPOA-MIB::ipoaLisMinHoldingTime,Integer32,read-create,,current,,The minimum amount of time, in seconds, that a call will remain open. If 0 then ipoaInactivityTimer will completely determine when a call is terminated.
.1.3.6.1.2.1.10.46.1.2.1.6,IPOA-MIB::ipoaLisQDepth,Integer32,read-create,,current,,The maximum number of outstanding requests that are allowed while waiting for ATMARP replies and InATMARP replies for this LIS.
.1.3.6.1.2.1.10.46.1.2.1.7,IPOA-MIB::ipoaLisMaxCalls,Integer32,read-create,,current,,The maximum number of SVCs that can be established simultaneously for this LIS.
.1.3.6.1.2.1.10.46.1.2.1.8,IPOA-MIB::ipoaLisCacheEntryAge,Integer32,read-create,,current,,The time, in seconds, before an ipNetToMediaEntry will age out of the table. Note that the default value will be different for a client and a server. An ATMARP Server should use a default of 1200 and a client should use 900.
.1.3.6.1.2.1.10.46.1.2.1.9,IPOA-MIB::ipoaLisRetries,Integer32,read-create,,current,,The number of times the ATMARP request will be retried when no response is received in the timeout interval indicated by ipoaLisTimeout.
.1.3.6.1.2.1.10.46.1.2.1.10,IPOA-MIB::ipoaLisTimeout,Integer32,read-create,,current,,The time to wait, in seconds, before retransmission of an ARP request.
.1.3.6.1.2.1.10.46.1.2.1.11,IPOA-MIB::ipoaLisDefaultPeakCellRate,Integer32,read-create,,current,,This object is the signalling parameter that should be used when setting up all best effort VCCs (Virtual Channel Connections). This parameter applies to the forward and backward direction on a per best effort VCC basis. A value of zero implies that no configured default exists and that local policy should be used to determine the actual default to used during call setup. ATM Signaling Support for IP over ATM (RFC 1755) recommends 1/10th of the ATM interface's speed.
.1.3.6.1.2.1.10.46.1.2.1.12,IPOA-MIB::ipoaLisActiveVcs,Gauge32,read-only,,current,,Number of active SVCs for this LIS.
.1.3.6.1.2.1.10.46.1.2.1.13,IPOA-MIB::ipoaLisRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the ipoaLisTable. When the ipoaLisRowStatus deleted (by setting this object to destroy(6)), this has the side-effect of removing all entries from the ipNetToMediaTable that are associated with this LIS (in other words, it flushes the entity's ATMARP cache). It also removes the ipoaVcTable entries that were associated with those ipNetToMediaTable entries. Destroying the row also removes the corresponding entries in the ipoaArpSrvrTable, ipoaArpClientTable, ipoaLisIfMappingTable, and ipoaArpRemoteSrvrTable. Entries in both the ipNetToMediaTable and the ipoaVcTable that are associated with a ipoaConfigPvcEntry are not affected by changes to ipoaLisRowStatus.
.1.3.6.1.2.1.10.46.1.3,IPOA-MIB::ipoaLisIfMappingTable,,not-accessible,,current,,There is one entry in this table for every combination of ipoaLisEntry and IP over ATM interface.
.1.3.6.1.2.1.10.46.1.3.1,IPOA-MIB::ipoaLisIfMappingEntry,,not-accessible,ipoaLisSubnetAddr:ipoaLisIfMappingIfIndex,current,,Defines an entry in the ipoaLisIfMappingTable.
.1.3.6.1.2.1.10.46.1.3.1.1,IPOA-MIB::ipoaLisIfMappingIfIndex,Integer32,not-accessible,,current,,The ipAdEntIfIndex object from an ipAddrEntry is used as an index to this table when its ipAdEntAddr is in the subnet implied by ipoaLisSubnetAddr.
.1.3.6.1.2.1.10.46.1.3.1.2,IPOA-MIB::ipoaLisIfMappingRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the ipoaLisIfMappingTable.
.1.3.6.1.2.1.10.46.1.4,IPOA-MIB::ipoaArpClientTable,,not-accessible,,current,,The ATMARP clients running on this system.
.1.3.6.1.2.1.10.46.1.4.1,IPOA-MIB::ipoaArpClientEntry,,not-accessible,ipAdEntAddr,current,,Information about a single ATMARP Client. Clients can be started and stopped by adding and removing entries from this table. An entry in the ipoaArpClientTable has a corresponding entry in the ipAddrTable. Both are indexed by ipAdEntAddr. The ifIndex and subnet mask of a client entry are the ipAddrEntry's ipAdEntIfIndex and ipAdEntNetMask, respectively. Note that adding and removing entries from this table may have the same effect on the corresponding ipAddrTable entry. Row creation of an entry in this table requires that either the corresponding ipAddrTable entry exists or that ipAdEntIfIndex and ipAdEntNetMask be specified in the creation of an ipoaArpClientEntry at a minimum in order to create the corresponding ipAddrEntry. Specification of ipAdEntBcastAddr and ipAdEntReasmMaxSize to complete an ipAddrEntry is implementation dependent. Whether a corresponding ipAddrEntry is deleted during the deletion of an ipoaArpClientEntry is considered implementation dependent.
.1.3.6.1.2.1.10.46.1.4.1.1,IPOA-MIB::ipoaArpClientAtmAddr,OCTET,read-create,,current,,The ATM address of the client.
.1.3.6.1.2.1.10.46.1.4.1.2,IPOA-MIB::ipoaArpClientSrvrInUse,OCTET,read-only,,current,,The ATM address of the ATMARP Server, ipoaArpRemoteSrvrAtmAddr, in use by this client. A zero length octet string implies that communication with a Remote ATMARP Server is not in effect.
.1.3.6.1.2.1.10.46.1.4.1.3,IPOA-MIB::ipoaArpClientInArpInReqs,Counter32,read-only,,current,,The number of InATMARP requests received by this client.
.1.3.6.1.2.1.10.46.1.4.1.4,IPOA-MIB::ipoaArpClientInArpOutReqs,Counter32,read-only,,current,,The number of InATMARP requests sent by this client.
.1.3.6.1.2.1.10.46.1.4.1.5,IPOA-MIB::ipoaArpClientInArpInReplies,Counter32,read-only,,current,,The number of InATMARP replies received by this client.
.1.3.6.1.2.1.10.46.1.4.1.6,IPOA-MIB::ipoaArpClientInArpOutReplies,Counter32,read-only,,current,,Total number of InATMARP replies sent by this client.
.1.3.6.1.2.1.10.46.1.4.1.7,IPOA-MIB::ipoaArpClientInArpInvalidInReqs,Counter32,read-only,,current,,The number of times that this client detected an invalid InATMARP request.
.1.3.6.1.2.1.10.46.1.4.1.8,IPOA-MIB::ipoaArpClientInArpInvalidOutReqs,Counter32,read-only,,current,,The number of times that this client did not receive an InATMARP reply.
.1.3.6.1.2.1.10.46.1.4.1.9,IPOA-MIB::ipoaArpClientArpInReqs,Counter32,read-only,,current,,Total number of ATMARP requests received by this client.
.1.3.6.1.2.1.10.46.1.4.1.10,IPOA-MIB::ipoaArpClientArpOutReqs,Counter32,read-only,,current,,Total number of ATMARP requests sent by this client.
.1.3.6.1.2.1.10.46.1.4.1.11,IPOA-MIB::ipoaArpClientArpInReplies,Counter32,read-only,,current,,Total number of ATMARP replies received by this client.
.1.3.6.1.2.1.10.46.1.4.1.12,IPOA-MIB::ipoaArpClientArpOutReplies,Counter32,read-only,,current,,Total number of ATMARP replies sent by this client.
.1.3.6.1.2.1.10.46.1.4.1.13,IPOA-MIB::ipoaArpClientArpInNaks,Counter32,read-only,,current,,Total number of negative ATMARP replies received by this client.
.1.3.6.1.2.1.10.46.1.4.1.14,IPOA-MIB::ipoaArpClientArpOutNaks,Counter32,read-only,,current,,Total number of negative ATMARP replies sent by this client. Classic IP and ARP over ATM does not require an ATMARP client to transmit an ATMARP_NAK upon receipt of an ATMARP request from another ATMARP client. However, implementation experience has shown that this error condition is somewhat easy to create inadvertently by configuring one ATMARP client with an ipoaArpRemoteSrvrTable entry containing an ipoaArpRemoteSrvrAtmAddr value which is the ATM address of another ATMARP client-only system. If an ATMARP client supports the transmission of ATMARP_NAKs, then it should increment ipoaArpClientArpOutNaks each time it transmits an ATMARP_NAK. Otherwise, support of this object is considered optional.
.1.3.6.1.2.1.10.46.1.4.1.15,IPOA-MIB::ipoaArpClientArpUnknownOps,Counter32,read-only,,current,,The number of times that this client received an ATMARP message with an operation code for which it is not coded to support.
.1.3.6.1.2.1.10.46.1.4.1.16,IPOA-MIB::ipoaArpClientArpNoSrvrResps,Counter32,read-only,,current,,The number of times this client failed to receive a response from a ATMARP Server within the ipoaLisTimeout value for ipoaLisRetries times. This may imply that the client will re-elect a new primary ATMARP Server for this LIS from the ipoaArpRemoteSrvrTable.
.1.3.6.1.2.1.10.46.1.4.1.17,IPOA-MIB::ipoaArpClientRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted from the ipoaArpClientTable.
.1.3.6.1.2.1.10.46.1.5,IPOA-MIB::ipoaArpSrvrTable,,not-accessible,,current,,The ATMARP Servers running on this system.
.1.3.6.1.2.1.10.46.1.5.1,IPOA-MIB::ipoaArpSrvrEntry,,not-accessible,ipAdEntAddr:ipoaArpSrvrAddr,current,,Information about an ATMARP Server within a LIS. An entry in this table has two indexes: first ipAdEntAddr, which is the IP address that this system uses as a member of the LIS, and then ipoaArpSrvrAddr, which is the ATM address of the ATMARP Server. Entries may be created by a management application using the ipoaArpSrvrRowStatus object. Entries in this table may also be created by the system and not by a management application, for example via ILMI. Entries in this table may be deleted by setting the ipoaArpSrvrRowStatus object to 'destroy(6)'. This includes entries that were added by the system and not by a management application.
.1.3.6.1.2.1.10.46.1.5.1.1,IPOA-MIB::ipoaArpSrvrAddr,OCTET,not-accessible,,current,,The ATM address of the ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.2,IPOA-MIB::ipoaArpSrvrLis,IpAddress,read-create,,current,,The subnet address that identifies the LIS with which this server is associated.
.1.3.6.1.2.1.10.46.1.5.1.3,IPOA-MIB::ipoaArpSrvrInArpInReqs,Counter32,read-only,,current,,The number of InATMARP requests received by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.4,IPOA-MIB::ipoaArpSrvrInArpOutReqs,Counter32,read-only,,current,,The number of InATMARP requests sent by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.5,IPOA-MIB::ipoaArpSrvrInArpInReplies,Counter32,read-only,,current,,The number of InATMARP replies received by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.6,IPOA-MIB::ipoaArpSrvrInArpOutReplies,Counter32,read-only,,current,,The number of InATMARP replies sent by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.7,IPOA-MIB::ipoaArpSrvrInArpInvalidInReqs,Counter32,read-only,,current,,The number of invalid InATMARP requests received by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.8,IPOA-MIB::ipoaArpSrvrInArpInvalidOutReqs,Counter32,read-only,,current,,The number of times that this server did not receive an InATMARP reply.
.1.3.6.1.2.1.10.46.1.5.1.9,IPOA-MIB::ipoaArpSrvrArpInReqs,Counter32,read-only,,current,,Total number of ATMARP requests received by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.10,IPOA-MIB::ipoaArpSrvrArpOutReplies,Counter32,read-only,,current,,Total number of ATMARP replies sent by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.11,IPOA-MIB::ipoaArpSrvrArpOutNaks,Counter32,read-only,,current,,Total number of negative ATMARP replies sent by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.12,IPOA-MIB::ipoaArpSrvrArpDupIpAddrs,Counter32,read-only,,current,,The number of times that a duplicate IP address was detected by this ATMARP Server.
.1.3.6.1.2.1.10.46.1.5.1.13,IPOA-MIB::ipoaArpSrvrArpUnknownOps,Counter32,read-only,,current,,The number of times that this ATMARP Server received an ATMARP message with an operation code for which it is not coded to support.
.1.3.6.1.2.1.10.46.1.5.1.14,IPOA-MIB::ipoaArpSrvrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted from the ipoaArpSrvrTable.
.1.3.6.1.2.1.10.46.1.6,IPOA-MIB::ipoaArpRemoteSrvrTable,,not-accessible,,current,,A table of non-local ATMARP Servers associated with a LIS. An entry in this table has three indexes: first the ipoaLisSubnetAddr of the LIS for which the corresponding ATMARP Server provides ATMARP services, then the ipoaArpRemoteSrvrAtmAddr, which is the ATM address of the remote ATMARP Server, and finally the ifIndex of the interface on which the VC to the ATMARP Remote Server will be opened. An ifIndex value of 0 should be used when a single VC is to be shared for ATMARP purposes by multiple interfaces.
.1.3.6.1.2.1.10.46.1.6.1,IPOA-MIB::ipoaArpRemoteSrvrEntry,,not-accessible,ipoaLisSubnetAddr:ipoaArpRemoteSrvrAtmAddr:ipoaArpRemoteSrvrIfIndex,current,,Information about one non-local ATMARP Server.
.1.3.6.1.2.1.10.46.1.6.1.1,IPOA-MIB::ipoaArpRemoteSrvrAtmAddr,OCTET,not-accessible,,current,,The ATM address of the remote ATMARP Server.
.1.3.6.1.2.1.10.46.1.6.1.2,IPOA-MIB::ipoaArpRemoteSrvrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted from the ipoaArpRemoteSrvrTable. Deleting an ipoaArpRemoteSrvrEntry (by setting this object to destroy(6)) may affect ipoaArpClientTable entries. The object ipoaArpClientSrvrInUse in an ipoaArpClientSrvrEntry may contain the ATM address of an ATMARP Remote Server whose entry in the ipoaArpRemoteSrvrTable is being removed. In this case, any corresponding ipoaArpClientSrvrInUse objects should be at a minimum invalidated by setting their values to that of a zero length OCTET STRING. The value of ipoaArpRemoteSrvrOperStatus should be consistent with that of ipoaArpRemoteSrvrRowStatus. For example, successfully setting the value of this object to notInService(2) after its being in the up(1) state should result in ipoaArpRemoteSrvrOperStatus being set to down(2) if currently up(1).
.1.3.6.1.2.1.10.46.1.6.1.3,IPOA-MIB::ipoaArpRemoteSrvrIfIndex,Integer32,not-accessible,,current,,The ifIndex of the interface that the VC to the Remote ATMARP Server is associated with.
.1.3.6.1.2.1.10.46.1.6.1.4,IPOA-MIB::ipoaArpRemoteSrvrIpAddr,IpAddress,read-only,,current,,The IP Address of the Remote ATMARP Server. A value of 0.0.0.0 implies that this address isn't known.
.1.3.6.1.2.1.10.46.1.6.1.5,IPOA-MIB::ipoaArpRemoteSrvrAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired state for use of the ATMARP Server represented by an entry in this table. ipoaArpRemoteSrvrAdminStatus values: up(1) - Attempt to activate use of the ATMARP Server represented by this entry in the ipoaArpRemoteSrvrTable. down(2) - Deactivate use of this ATMARP Server. When a managed system creates an entry in this table ipoaArpRemoteSrvrAdminStatus and ipoaArpRemoteSrvrOperStatus are initialized as down(2) by default.
.1.3.6.1.2.1.10.46.1.6.1.6,IPOA-MIB::ipoaArpRemoteSrvrOperStatus,INTEGER,read-only,,current,up(1):down(2),The current operational state for use of a Remote ATMARP Server. An up(1) entry has a VC established to the respective Remote ATMARP Server: up(1) - A VC exists to Remote ATMARP Server whose IP Address is stored in ipoaArpRemoteSrvrIpAddr. This VC can be determined by searching the ipoaVcTable using ipoaArpRemoteSrvrIfIndex (if not 0, otherwise ignore ipNetToMediaIfIndex index) and ipoaArpRemoteSrvrIpAddr. An ipoaArpClientEntry should exist with its ipoaArpClientSrvrInUse object having the same value as ipoaArpRemoteSrvrAtmAddr. down(2) - Entry exists without an active VC to the Remote ATMARP Server. Transition from up(1) to down(2) status may affect ipoaArpClientTable entries. The object ipoaArpClientSrvrInUse in an ipoaArpClientSrvrEntry may contain the ATM address of an ATMARP Remote Server whose entry in the ipoaArpRemoteSrvrTable is being deactivated. In this case, any corresponding ipoaArpClientSrvrInUse objects should be at a minimum invalidated by setting their values to that of a zero length OCTET STRING. If ipoaArpRemoteSrvrAdminStatus is down(2) then ipoaArpRemoteSrvrOperStatus should be down(2). If ipoaArpRemoteSrvrAdminStatus is changed to up(1) then ipoaArpRemoteSrvrOperStatus should change to up(1) if the Remote ATMARP Server entry can be activated.
.1.3.6.1.2.1.10.46.1.7,IPOA-MIB::ipoaVcTable,,not-accessible,,current,,A system that supports IP over ATM is an IP system and therefore MUST support all of the appropriate tables in the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233), the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012), and the UDP-MIB (RFC 2013). This includes the ipNetToMediaTable (the ARP cache) that is defined within the IP-MIB (RFC 2011). The ipoaVcTable keeps a set of VCs for each entry in the ARP cache that was put there by an IP over ATM system acting as either a host or server. The ipoaVcTable doesn't augment the ipNetToMediaTable (ARP Cache) since the the correspondence between tables is not necessarily one-to-one. An ipNetToMediaPhysAddress object should contain the content as defined by the IpoaAtmAddr textual convention when used to hold an IPOA-MIB ATM Address.
.1.3.6.1.2.1.10.46.1.7.1,IPOA-MIB::ipoaVcEntry,,not-accessible,ipNetToMediaIfIndex:ipNetToMediaNetAddress:ipoaVcVpi:ipoaVcVci,current,,A VC (permanent or switched) that this host or server has opened with another member of a LIS. Additional information can be determined about the VC from the ATM-MIB. Entries in this table cannot be created by management applications. In an SVC environment, an entry is automatically added by the system as the result of ATMARP processing. In a PVC environment, an entry is automatically added to this table when an entry is created in the ipoaConfigPvcTable and the IP Address at the remote end of the PVC is discovered using InATMARP. An entry also is added to the ipNetToMediaTable.
.1.3.6.1.2.1.10.46.1.7.1.1,IPOA-MIB::ipoaVcVpi,Integer32,not-accessible,,current,,The VPI value for the Virtual Circuit.
.1.3.6.1.2.1.10.46.1.7.1.2,IPOA-MIB::ipoaVcVci,Integer32,not-accessible,,current,,The VCI value for the Virtual Circuit.
.1.3.6.1.2.1.10.46.1.7.1.3,IPOA-MIB::ipoaVcType,INTEGER,read-only,,current,pvc(1):svcIncoming(2):svcOutgoing(3):spvcInitiator(4):spvcTarget(5),The type of the Virtual Circuit.
.1.3.6.1.2.1.10.46.1.7.1.4,IPOA-MIB::ipoaVcNegotiatedEncapsType,INTEGER,read-only,,current,llcSnap(1):vcMuxed(2):other(3),The encapsulation type used when communicating over this circuit.
.1.3.6.1.2.1.10.46.1.7.1.5,IPOA-MIB::ipoaVcNegotiatedMtu,Integer32,read-only,,current,,The MTU used when communicating over this circuit.
.1.3.6.1.2.1.10.46.1.8,IPOA-MIB::ipoaConfigPvcTable,,not-accessible,,current,,This table MUST be supported when PVCs are intended to be supported in order to enable the setup of PVCs for use by IP.
.1.3.6.1.2.1.10.46.1.8.1,IPOA-MIB::ipoaConfigPvcEntry,,not-accessible,ipoaConfigPvcIfIndex:ipoaConfigPvcVpi:ipoaConfigPvcVci,current,,Defines a single PVC that exists at this host for use by IP.
.1.3.6.1.2.1.10.46.1.8.1.1,IPOA-MIB::ipoaConfigPvcIfIndex,Integer32,not-accessible,,current,,The ifIndex of the ATM Interface that this PVC is associated with.
.1.3.6.1.2.1.10.46.1.8.1.2,IPOA-MIB::ipoaConfigPvcVpi,Integer32,not-accessible,,current,,The VPI value for the Virtual Circuit.
.1.3.6.1.2.1.10.46.1.8.1.3,IPOA-MIB::ipoaConfigPvcVci,Integer32,not-accessible,,current,,The VCI value for the Virtual Circuit.
.1.3.6.1.2.1.10.46.1.8.1.4,IPOA-MIB::ipoaConfigPvcDefaultMtu,Integer32,read-create,,current,,Classical IP and ARP over ATM allows use of other MTU values for PVCs but considers how a value other than 9180 could be selected to be out of scope. ipoaConfigPvcDefaultMtu can be used to configure the MTU to be used for the PVC. Both ends MUST have the same value configured.
.1.3.6.1.2.1.10.46.1.8.1.5,IPOA-MIB::ipoaConfigPvcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows rows to be created and deleted in the ipoaConfigPvcTable. Creation of an entry in this table should eventually result in the creation of an ipNetToMediaEntry and a corresponding ipoaVcEntry after InATMARP has determined the destination address of the remote system that the PVC is connected to. Setting this object to destroy(6) should remove the corresponding ipNetToMediaTable and ipoaVcTable entries.
.1.3.6.1.2.1.10.46.2,IPOA-MIB::ipoaNotifications,,,,,,
.1.3.6.1.2.1.10.46.2.0,IPOA-MIB::ipoaTrapPrefix,,,,,,
.1.3.6.1.2.1.10.46.2.0.1,IPOA-MIB::ipoaMtuExceeded,,,,,,A frame was received that exceeds the negotiated MTU size. The VPI and VCI of the VC for which this condition was detected can be determined from the index values for ipoaVcNegotiatedMtu. In addition, the ifIndex and IP Address can be determined as well (refer to the ipoaVcTable).
.1.3.6.1.2.1.10.46.2.0.2,IPOA-MIB::ipoaDuplicateIpAddress,,,,,,The ATMARP Server has detected more than one ATM end point attempting to associate the same IP address with different ATM addresses.
.1.3.6.1.2.1.10.46.2.0.3,IPOA-MIB::ipoaLisCreate,,,,,,Generation of this trap occurs when an ipoaLisEntry is created while the ipoaLisTrapEnable.0 object has the value enabled(1).
.1.3.6.1.2.1.10.46.2.0.4,IPOA-MIB::ipoaLisDelete,,,,,,Generation of this trap occurs when an ipoaLisEntry is deleted while the ipoaLisTrapEnable.0 object has the value enabled(1).
.1.3.6.1.2.1.10.46.3,IPOA-MIB::ipoaConformance,,,,,,
.1.3.6.1.2.1.10.46.3.1,IPOA-MIB::ipoaGroups,,,,,,
.1.3.6.1.2.1.10.46.3.1.1,IPOA-MIB::ipoaGeneralGroup,,,,,,This group is mandatory for all IP over ATM entities.
.1.3.6.1.2.1.10.46.3.1.2,IPOA-MIB::ipoaClientGroup,,,,,,This group is mandatory for all hosts where an IP over ATM client is present.
.1.3.6.1.2.1.10.46.3.1.3,IPOA-MIB::ipoaSrvrGroup,,,,,,This group is mandatory for all hosts where ATMARP Servers are present.
.1.3.6.1.2.1.10.46.3.1.4,IPOA-MIB::ipoaBasicNotificationsGroup,,,,,,The notification which an IP over ATM entity is required to implement.
.1.3.6.1.2.1.10.46.3.1.5,IPOA-MIB::ipoaSrvrNotificationsGroup,,,,,,The notification which an IP over ATM ATMARP Server is required to implement.
.1.3.6.1.2.1.10.46.3.1.6,IPOA-MIB::ipoaLisNotificationsGroup,,,,,,The LIS-related notifications which are required to be implemented by an IP over ATM ATMARP server, as well as by any IP over ATM client which allows ipoaLisTrapEnable to be set to enabled(1).
.1.3.6.1.2.1.10.46.3.1.7,IPOA-MIB::ipoaLisTableGroup,,,,,,This group is mandatory for all entities which support IP over ATM SVCs. Support of objects in this group by IP over ATM clients which only support IP over ATM PVCs is optional.
.1.3.6.1.2.1.10.46.3.2,IPOA-MIB::ipoaCompliances,,,,,,
.1.3.6.1.2.1.10.46.3.2.1,IPOA-MIB::ipoaCompliance,,,,,,The compliance statement for agents that support the IPOA-MIB.
.1.3.6.1.2.1.10.47,FR-MFR-MIB::mfrMib,,,,,,This is the MIB used to control and monitor the multilink frame relay (MFR) function described in FRF.16.
.1.3.6.1.2.1.10.47.1,FR-MFR-MIB::mfrMibScalarObjects,,,,,,
.1.3.6.1.2.1.10.47.1.1,FR-MFR-MIB::mfrBundleMaxNumBundles,Integer32,read-only,,current,,This object is used to inform the manager of the maximum number of bundles supported by this device.
.1.3.6.1.2.1.10.47.1.2,FR-MFR-MIB::mfrBundleNextIndex,INTEGER,read-write,,current,,This object is used to assist the manager in selecting a value for mfrBundleIndex during row creation in the mfrBundleTable. It can also be used to avoid race conditions with multiple managers trying to create rows in the table (see RFC 2494 [RFC2494] for one such alogrithm).
.1.3.6.1.2.1.10.47.2,FR-MFR-MIB::mfrMibBundleObjects,,,,,,
.1.3.6.1.2.1.10.47.2.3,FR-MFR-MIB::mfrBundleTable,,not-accessible,,current,,The bundle configuration and status table. There is a one-to-one correspondence between a bundle and an interface represented in the ifTable. The following objects of the ifTable have specific meaning for an MFR bundle: ifAdminStatus - the bundle admin status ifOperStatus - the bundle operational status ifSpeed - the current bandwidth of the bundle ifInUcastPkts - the number of frames received on the bundle ifOutUcastPkts - the number of frames transmitted on the bundle ifInErrors - frame (not fragment) errors ifOutErrors - frame (not fragment) errors 
.1.3.6.1.2.1.10.47.2.3.1,FR-MFR-MIB::mfrBundleEntry,,not-accessible,mfrBundleIndex,current,,An entry in the bundle table.
.1.3.6.1.2.1.10.47.2.3.1.1,FR-MFR-MIB::mfrBundleIndex,Integer32,not-accessible,,current,,The index into the table. While this corresponds to an entry in the ifTable, the value of mfrBundleIndex need not match that of the ifIndex in the ifTable. A manager can use mfrBundleNextIndex to select a unique mfrBundleIndex for creating a new row.
.1.3.6.1.2.1.10.47.2.3.1.2,FR-MFR-MIB::mfrBundleIfIndex,Integer32,read-only,,current,,The value must match an entry in the interface table whose ifType must be set to frf16MfrBundle(163). For example: if the value of mfrBundleIfIndex is 10, then a corresponding entry should be present in the ifTable with an index of 10 and an ifType of 163.
.1.3.6.1.2.1.10.47.2.3.1.3,FR-MFR-MIB::mfrBundleRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The mfrBundleRowStatus object allows create, change, and delete operations on bundle entries.
.1.3.6.1.2.1.10.47.2.3.1.4,FR-MFR-MIB::mfrBundleNearEndName,OCTET,read-create,,current,,The configured name of the bundle.
.1.3.6.1.2.1.10.47.2.3.1.5,FR-MFR-MIB::mfrBundleFragmentation,INTEGER,read-create,,current,enable(1):disable(2),Controls whether the bundle performs/accepts fragmentation and re-assembly. The possible values are: enable(1) - Bundle links will fragment frames disable(2) - Bundle links will not fragment frames.
.1.3.6.1.2.1.10.47.2.3.1.6,FR-MFR-MIB::mfrBundleMaxFragSize,Integer32,read-create,,current,,The maximum fragment size supported. Note that this is only valid if mfrBundleFragmentation is set to enable(1). Zero is not a valid fragment size. A bundle that does not support fragmentation must return this object with a value of -1.
.1.3.6.1.2.1.10.47.2.3.1.7,FR-MFR-MIB::mfrBundleTimerHello,INTEGER,read-create,,current,,The configured MFR Hello Timer value.
.1.3.6.1.2.1.10.47.2.3.1.8,FR-MFR-MIB::mfrBundleTimerAck,INTEGER,read-create,,current,,The configured MFR T_ACK value.
.1.3.6.1.2.1.10.47.2.3.1.9,FR-MFR-MIB::mfrBundleCountMaxRetry,INTEGER,read-create,,current,,The MFR N_MAX_RETRY value.
.1.3.6.1.2.1.10.47.2.3.1.10,FR-MFR-MIB::mfrBundleActivationClass,INTEGER,read-create,,current,mfrBundleActivationClassA(1):mfrBundleActivationClassB(2):mfrBundleActivationClassC(3):mfrBundleActivationClassD(4),Controls the conditions under which the bundle is activated. The following settings are available: mfrBundleActivationClassA(1) - at least one must link up mfrBundleActivationClassB(2) - all links must be up mfrBundleActivationClassC(3) - a certain number must be up. Refer to mfrBundleThreshold for the required number. mfrBundleActivationClassD(4) - custom (implementation specific).
.1.3.6.1.2.1.10.47.2.3.1.11,FR-MFR-MIB::mfrBundleThreshold,Integer32,read-create,,current,,Specifies the number of links that must be in operational 'up' state before the bundle will transition to an operational up/active state. If the number of operational 'up' links falls below this value, then the bundle will transition to an inactive state. Note - this is only valid when mfrBundleActivationClass is set to mfrBundleActivationClassC or, depending upon the implementation, to mfrBundleActivationClassD. A bundle that is not set to one of these must return this object with a value of -1.
.1.3.6.1.2.1.10.47.2.3.1.12,FR-MFR-MIB::mfrBundleMaxDiffDelay,Integer32,read-create,,current,,The maximum delay difference between the bundle links. A value of -1 indicates that this object does not contain a valid value
.1.3.6.1.2.1.10.47.2.3.1.13,FR-MFR-MIB::mfrBundleSeqNumSize,INTEGER,read-create,,current,seqNumSize12bit(1):seqNumSize24bit(2),Controls whether the standard FRF.12 12-bit sequence number is used or the optional 24-bit sequence number.
.1.3.6.1.2.1.10.47.2.3.1.14,FR-MFR-MIB::mfrBundleMaxBundleLinks,Integer32,read-only,,current,,The maximum number of bundle links supported for this bundle.
.1.3.6.1.2.1.10.47.2.3.1.15,FR-MFR-MIB::mfrBundleLinksConfigured,Integer32,read-only,,current,,The number of links configured for the bundle.
.1.3.6.1.2.1.10.47.2.3.1.16,FR-MFR-MIB::mfrBundleLinksActive,Integer32,read-only,,current,,The number of links that are active.
.1.3.6.1.2.1.10.47.2.3.1.17,FR-MFR-MIB::mfrBundleBandwidth,Integer32,read-only,,current,,The amount of available bandwidth on the bundle
.1.3.6.1.2.1.10.47.2.3.1.18,FR-MFR-MIB::mfrBundleFarEndName,OCTET,read-only,,current,,Name of the bundle received from the far end.
.1.3.6.1.2.1.10.47.2.3.1.19,FR-MFR-MIB::mfrBundleResequencingErrors,Counter32,read-only,,current,,A count of the number of resequencing errors. Each event may correspond to multiple lost frames. Example: Say sequence number 56, 59 and 60 is received for DLCI 100. It is decided by some means that sequence 57 and 58 is lost. This counter should then be incremented by ONE, even though two frames were lost.
.1.3.6.1.2.1.10.47.2.4,FR-MFR-MIB::mfrBundleIfIndexMappingTable,,not-accessible,,current,,A table mapping the values of ifIndex to the mfrBundleIndex. This is required in order to find the mfrBundleIndex given an ifIndex. The mapping of mfrBundleIndex to ifIndex is provided by the mfrBundleIfIndex entry in the mfrBundleTable.
.1.3.6.1.2.1.10.47.2.4.1,FR-MFR-MIB::mfrBundleIfIndexMappingEntry,,not-accessible,ifIndex,current,,Each row describes one ifIndex to mfrBundleIndex mapping.
.1.3.6.1.2.1.10.47.2.4.1.2,FR-MFR-MIB::mfrBundleIfIndexMappingIndex,Integer32,read-only,,current,,The mfrBundleIndex of the given ifIndex.
.1.3.6.1.2.1.10.47.3,FR-MFR-MIB::mfrMibBundleLinkObjects,,,,,,
.1.3.6.1.2.1.10.47.3.1,FR-MFR-MIB::mfrBundleLinkTable,,not-accessible,,current,,The bundle link configuration and status table. There is a one-to-one correspondence between a bundle link and a physical interface represented in the ifTable. The ifIndex of the physical interface is used to index the bundle link table, and to create rows. The following objects of the ifTable have specific meaning for an MFR bundle link: ifAdminStatus - the bundle link admin status ifOperStatus - the bundle link operational status ifSpeed - the bandwidth of the bundle link interface ifInUcastPkts - the number of frames received on the bundle link ifOutUcastPkts - the number of frames transmitted on the bundle link ifInErrors - frame and fragment errors ifOutErrors - frame and fragment errors
.1.3.6.1.2.1.10.47.3.1.1,FR-MFR-MIB::mfrBundleLinkEntry,,not-accessible,ifIndex,current,,An entry in the bundle link table.
.1.3.6.1.2.1.10.47.3.1.1.1,FR-MFR-MIB::mfrBundleLinkRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The mfrBundleLinkRowStatus object allows create, change, and delete operations on mfrBundleLink entries. The create operation must fail if no physical interface is associated with the bundle link.
.1.3.6.1.2.1.10.47.3.1.1.2,FR-MFR-MIB::mfrBundleLinkConfigBundleIndex,Integer32,read-create,,current,,The mfrBundleLinkConfigBundleIndex object allows the manager to control the bundle to which the bundle link is assigned. If no value were in this field, then the bundle would remain in NOT_READY rowStatus and be unable to go to active. With an appropriate mfrBundleIndex in this field, then we could put the mfrBundleLink row in NOT_IN_SERVICE or ACTIVE rowStatus.
.1.3.6.1.2.1.10.47.3.1.1.3,FR-MFR-MIB::mfrBundleLinkNearEndName,OCTET,read-create,,current,,The configured bundle link name that is sent to the far end.
.1.3.6.1.2.1.10.47.3.1.1.4,FR-MFR-MIB::mfrBundleLinkState,INTEGER,read-only,,current,mfrBundleLinkStateAddSent(1):mfrBundleLinkStateAddRx(2):mfrBundleLinkStateAddAckRx(3):mfrBundleLinkStateUp(4):mfrBundleLinkStateIdlePending(5):mfrBundleLinkStateIdle(6):mfrBundleLinkStateDown(7):mfrBundleLinkStateDownIdle(8),Current bundle link state as defined by the MFR protocol described in Annex A of FRF.16.
.1.3.6.1.2.1.10.47.3.1.1.5,FR-MFR-MIB::mfrBundleLinkFarEndName,OCTET,read-only,,current,,Name of bundle link received from far end.
.1.3.6.1.2.1.10.47.3.1.1.6,FR-MFR-MIB::mfrBundleLinkFarEndBundleName,OCTET,read-only,,current,,Name of far end bundle for this link received from far end.
.1.3.6.1.2.1.10.47.3.1.1.7,FR-MFR-MIB::mfrBundleLinkDelay,Integer32,read-only,,current,,Current round-trip delay for this bundle link. The value -1 is returned when an implementation does not support measurement of the bundle link delay.
.1.3.6.1.2.1.10.47.3.1.1.8,FR-MFR-MIB::mfrBundleLinkFramesControlTx,Counter32,read-only,,current,,Number of MFR control frames sent.
.1.3.6.1.2.1.10.47.3.1.1.9,FR-MFR-MIB::mfrBundleLinkFramesControlRx,Counter32,read-only,,current,,Number of valid MFR control frames received.
.1.3.6.1.2.1.10.47.3.1.1.10,FR-MFR-MIB::mfrBundleLinkFramesControlInvalid,Counter32,read-only,,current,,The number of invalid MFR control frames received.
.1.3.6.1.2.1.10.47.3.1.1.11,FR-MFR-MIB::mfrBundleLinkTimerExpiredCount,Counter32,read-only,,current,,Number of times the T_HELLO or T_ACK timers expired.
.1.3.6.1.2.1.10.47.3.1.1.12,FR-MFR-MIB::mfrBundleLinkLoopbackSuspected,Counter32,read-only,,current,,The number of times a loopback has been suspected (based upon the use of magic numbers).
.1.3.6.1.2.1.10.47.3.1.1.13,FR-MFR-MIB::mfrBundleLinkUnexpectedSequence,Counter32,read-only,,current,,The number of data MFR frames discarded because the sequence number of the frame for a DLCI was less than (delayed frame) or equal to (duplicate frame) the one expected for that DLCI. Example: Say frames with sequence numbers 56, 58, 59 is received for DLCI 100. While waiting for sequence number 57 another frame with sequence number 58 arrives. Frame 58 is discarded and the counter is incremented.
.1.3.6.1.2.1.10.47.3.1.1.14,FR-MFR-MIB::mfrBundleLinkMismatch,Counter32,read-only,,current,,The number of times that the unit has been notified by the remote peer that the bundle name is inconsistent with other bundle links attached to the far-end bundle.
.1.3.6.1.2.1.10.47.4,FR-MFR-MIB::mfrMibTraps,,,,,,
.1.3.6.1.2.1.10.47.4.0,FR-MFR-MIB::mfrMibTrapsPrefix,,,,,,
.1.3.6.1.2.1.10.47.4.0.1,FR-MFR-MIB::mfrMibTrapBundleLinkMismatch,,,,,,This trap indicates that a bundle link mismatch has been detected. The following objects are reported: mfrBundleNearEndName: configured name of near end bundle mfrBundleFarEndName: previously reported name of far end bundle mfrBundleLinkNearEndName: configured name of near end bundle mfrBundleLinkFarEndName: reported name of far end bundle mfrBundleLinkFarEndBundleName: currently reported name of far end bundle Note: that the configured items may have been configured automatically. Note: The mfrBundleLinkMismatch counter is incremented when the trap is sent.
.1.3.6.1.2.1.10.47.5,FR-MFR-MIB::mfrMibConformance,,,,,,
.1.3.6.1.2.1.10.47.5.1,FR-MFR-MIB::mfrMibGroups,,,,,,
.1.3.6.1.2.1.10.47.5.1.1,FR-MFR-MIB::mfrMibBundleGroup,,,,,,Group of objects describing bundles.
.1.3.6.1.2.1.10.47.5.1.2,FR-MFR-MIB::mfrMibBundleLinkGroup,,,,,,Group of objects describing bundle links.
.1.3.6.1.2.1.10.47.5.1.3,FR-MFR-MIB::mfrMibTrapGroup,,,,,,Group of objects describing notifications (traps).
.1.3.6.1.2.1.10.47.5.2,FR-MFR-MIB::mfrMibCompliances,,,,,,
.1.3.6.1.2.1.10.47.5.2.1,FR-MFR-MIB::mfrMibCompliance,,,,,,The compliance statement for equipment that implements the FRF16 MIB. All of the current groups are mandatory, but a number of objects may be read-only if the implementation does not allow configuration.
.1.3.6.1.2.1.10.48,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMIB,,,,,,This MIB module defines a collection of objects for managing HDSL2/SHDSL lines. An agent may reside at either end of the line; however, the MIB module is designed to require no management communication between the modems beyond that inherent in the low-level EOC line protocol as defined in ANSI T1E1.4/2000-006 (for HDSL2 lines) or in ITU G.991.2 (for SHDSL lines). Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4319; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.48.0,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslNotifications,,,,,,
.1.3.6.1.2.1.10.48.0.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslLoopAttenCrossing,,,,,,This notification indicates that the loop attenuation threshold (as per the hdsl2ShdslEndpointThreshLoopAttenuation value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSNRMarginCrossing,,,,,,This notification indicates that the SNR margin threshold (as per the hdsl2ShdslEndpointThreshSNRMargin value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslPerfESThresh,,,,,,This notification indicates that the errored seconds threshold (as per the hdsl2ShdslEndpointThreshES value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslPerfSESThresh,,,,,,This notification indicates that the severely errored seconds threshold (as per the hdsl2ShdslEndpointThreshSES value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslPerfCRCanomaliesThresh,,,,,,This notification indicates that the CRC anomalies threshold (as per the hdsl2ShdslEndpointThreshCRCanomalies value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslPerfLOSWSThresh,,,,,,This notification indicates that the LOSW Seconds threshold (as per the hdsl2ShdslEndpointThreshLOSWS value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.7,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslPerfUASThresh,,,,,,This notification indicates that the unavailable seconds threshold (as per the hdsl2ShdslEndpointThreshUAS value) has been reached/exceeded for the HDSL2/SHDSL segment endpoint.
.1.3.6.1.2.1.10.48.0.8,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanInvalidNumRepeaters,,,,,,This notification indicates that a mismatch has been detected between the number of repeater/regenerator units configured for an HDSL2/SHDSL line via the hdsl2ShdslSpanConfNumRepeaters object and the actual number of repeater/regenerator units discovered via the EOC.
.1.3.6.1.2.1.10.48.0.9,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslLoopbackFailure,,,,,,This notification indicates that an endpoint maintenance loopback command failed for an HDSL2/SHDSL segment.
.1.3.6.1.2.1.10.48.0.10,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslpowerBackoff,,,,,,This notification indicates that the bit setting for powerBackoff in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
.1.3.6.1.2.1.10.48.0.11,HDSL2-SHDSL-LINE-MIB::hdsl2ShdsldeviceFault,,,,,,This notification indicates that the bit setting for deviceFault in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
.1.3.6.1.2.1.10.48.0.12,HDSL2-SHDSL-LINE-MIB::hdsl2ShdsldcContinuityFault,,,,,,This notification indicates that the bit setting for dcContinuityFault in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
.1.3.6.1.2.1.10.48.0.13,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslconfigInitFailure,,,,,,This notification indicates that the bit setting for configInitFailure in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
.1.3.6.1.2.1.10.48.0.14,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslprotocolInitFailure,,,,,,This notification indicates that the bit setting for protocolInitFailure in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
.1.3.6.1.2.1.10.48.0.15,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslnoNeighborPresent,,,,,,This notification indicates that the bit setting for noNeighborPresent in the hdsl2ShdslEndpointCurrStatus object for this endpoint has changed.
.1.3.6.1.2.1.10.48.0.16,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslLocalPowerLoss,,,,,,This notification indicates impending unit failure due to loss of local power (last gasp).
.1.3.6.1.2.1.10.48.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMibObjects,,,,,,
.1.3.6.1.2.1.10.48.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfTable,,not-accessible,,current,,This table supports overall configuration of HDSL2/SHDSL spans. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.48.1.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfEntry,,not-accessible,ifIndex,current,,An entry in the hdsl2ShdslSpanConfTable. Each entry represents the complete span in a single HDSL2/SHDSL line. It is indexed by the ifIndex of the associated HDSL2/SHDSL line.
.1.3.6.1.2.1.10.48.1.1.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfNumRepeaters,Unsigned32,read-write,,current,,This object provisions the number of repeaters/regenerators in this HDSL2/SHDSL span.
.1.3.6.1.2.1.10.48.1.1.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfProfile,OCTET,read-write,,current,,This object is a pointer to a span configuration profile in the hdsl2ShdslSpanConfProfileTable, which applies to this span. The value of this object is the index of the referenced profile in the hdsl2ShdslSpanConfProfileTable. Note that span configuration profiles are only applicable to SHDSL lines. HDSL2 lines MUST reference the default profile, 'DEFVAL'. By default, this object will have the value 'DEFVAL' (the index of the default profile). Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table, hdsl2ShdslSpanConfProfileTable, MUST be rejected.
.1.3.6.1.2.1.10.48.1.1.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfAlarmProfile,OCTET,read-write,,current,,This object is a pointer to an alarm configuration profile in the hdsl2ShdslEndpointAlarmConfProfileTable. The value of this object is the index of the referenced profile in the hdsl2ShdslEndpointAlarmConfProfileTable. The alarm threshold configuration in the referenced profile will be used by default for all segment endpoints in this span. Individual endpoints may override this profile by explicitly specifying some other profile in the hdsl2ShdslEndpointConfTable. By default, this object will have the value 'DEFVAL' (the index of the default profile). Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table, hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected.
.1.3.6.1.2.1.10.48.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanStatusTable,,not-accessible,,current,,This table provides overall status information of HDSL2/SHDSL spans. This table contains live data from equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.10.48.1.2.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanStatusEntry,,not-accessible,ifIndex,current,,An entry in the hdsl2ShdslSpanStatusTable. Each entry represents the complete span in a single HDSL2/SHDSL line. It is indexed by the ifIndex of the associated HDSL2/SHDSL line.
.1.3.6.1.2.1.10.48.1.2.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslStatusNumAvailRepeaters,Unsigned32,read-only,,current,,Contains the actual number of repeaters/regenerators discovered in this HDSL2/SHDSL span.
.1.3.6.1.2.1.10.48.1.2.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslStatusMaxAttainableLineRate,Unsigned32,read-only,,current,,Contains the maximum attainable line rate in this HDSL2/SHDSL span. This object provides the maximum rate the line is capable of achieving. This is based upon measurements made during line probing. This rate includes payload (user data) and any applicable framing overhead.
.1.3.6.1.2.1.10.48.1.2.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslStatusActualLineRate,Unsigned32,read-only,,current,,Contains the actual line rate in this HDSL2/SHDSL span. This SHOULD equal ifSpeed. This rate includes payload (user data) and any applicable framing overhead
.1.3.6.1.2.1.10.48.1.2.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslStatusTransmissionModeCurrent,BITS,read-only,,current,region1(0):region2(1),Contains the current Power Spectral Density (PSD) regional setting of the HDSL2/SHDSL span.
.1.3.6.1.2.1.10.48.1.2.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslStatusMaxAttainablePayloadRate,Unsigned32,read-only,,current,,Contains the maximum attainable payload (user data) line rate in this HDSL2/SHDSL span. This object provides the maximum rate the line is capable of achieving. This is based upon measurements made during line probing. Any framing overhead is not included.
.1.3.6.1.2.1.10.48.1.2.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslStatusActualPayloadRate,Unsigned32,read-only,,current,,Contains the actual line rate in this HDSL2/SHDSL span. Any framing overhead is not included.
.1.3.6.1.2.1.10.48.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInventoryTable,,not-accessible,,current,,This table supports retrieval of unit inventory information available via the EOC from units in an HDSL2/SHDSL line. Entries in this table are dynamically created during the line discovery process. The life cycle for these entries is as follows: - xtu discovers a device, either a far-end xtu or an xru - an inventory table entry is created for the device - the line goes down for whatever reason - inventory table entries for unreachable devices are destroyed As these entries are created/destroyed dynamically, they are NOT persistent.
.1.3.6.1.2.1.10.48.1.3.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInventoryEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex,current,,An entry in the hdsl2ShdslInventoryTable. Each entry represents inventory information for a single unit in an HDSL2/SHDSL line. It is indexed by the ifIndex of the HDSL2/SHDSL line and the Hdsl2ShdslUnitId of the associated unit.
.1.3.6.1.2.1.10.48.1.3.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvIndex,INTEGER,not-accessible,,current,xtuC(1):xtuR(2):xru1(3):xru2(4):xru3(5):xru4(6):xru5(7):xru6(8):xru7(9):xru8(10),Each entry in this table corresponds to a physical element in an HDSL2/SHDSL span. It is based on the EOC unit addressing scheme with reference to the xtuC.
.1.3.6.1.2.1.10.48.1.3.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorID,OCTET,read-only,,current,,Vendor ID as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorModelNumber,OCTET,read-only,,current,,Vendor model number as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorSerialNumber,OCTET,read-only,,current,,Vendor serial number as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorEOCSoftwareVersion,Integer32,read-only,,current,,Vendor EOC version as reported in a Discovery Response message.
.1.3.6.1.2.1.10.48.1.3.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvStandardVersion,Integer32,read-only,,current,,Version of the HDSL2/SHDSL standard implemented, as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorListNumber,OCTET,read-only,,current,,Vendor list number as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.8,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorIssueNumber,OCTET,read-only,,current,,Vendor issue number as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.9,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorSoftwareVersion,OCTET,read-only,,current,,Vendor software version as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.10,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvEquipmentCode,OCTET,read-only,,current,,Equipment code conforming to ANSI T1.213, Coded Identification of Equipment Entities.
.1.3.6.1.2.1.10.48.1.3.1.11,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvVendorOther,OCTET,read-only,,current,,Other vendor information as reported in an Inventory Response message.
.1.3.6.1.2.1.10.48.1.3.1.12,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInvTransmissionModeCapability,BITS,read-only,,current,region1(0):region2(1),Contains the transmission mode capability of the SHDSL unit.
.1.3.6.1.2.1.10.48.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointConfTable,,not-accessible,,current,,This table supports configuration parameters for segment endpoints in an HDSL2/SHDSL line. As this table is indexed by ifIndex, it MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.48.1.4.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointConfEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex:hdsl2ShdslEndpointSide:hdsl2ShdslEndpointWirePair,current,,An entry in the hdsl2ShdslEndpointConfTable. Each entry represents a single segment endpoint in an HDSL2/SHDSL line. It is indexed by the ifIndex of the HDSL2/SHDSL line, the UnitId of the associated unit, the side of the unit, and the wire pair of the associated modem.
.1.3.6.1.2.1.10.48.1.4.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointSide,INTEGER,not-accessible,,current,networkSide(1):customerSide(2),The side of the unit associated with this segment endpoint -- Network/Customer side -- as per the Hdsl2ShdslUnitSide textual convention.
.1.3.6.1.2.1.10.48.1.4.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointWirePair,INTEGER,not-accessible,,current,wirePair1(1):wirePair2(2):wirePair3(3):wirePair4(4),The wire pair of the modem associated with this segment endpoint as per the Hdsl2ShdslWirePair textual convention.
.1.3.6.1.2.1.10.48.1.4.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointAlarmConfProfile,OCTET,read-write,,current,,This object configures the alarm threshold values to be used for this segment endpoint. The values are obtained from the alarm configuration profile referenced by this object. The value of this object is the index of the referenced profile in the hdsl2ShdslEndpointAlarmConfProfileTable, or NULL (a zero-length SnmpAdminString). If the value is a zero-length SnmpAdminString, the endpoint uses the default Alarm Configuration Profile for the associated span as per the hdsl2ShdslSpanConfAlarmProfile object in the hdsl2ShdslSpanConfTable. The default value of this object is a zero-length SnmpAdminString. Any attempt to set this object to a value that is not the value of the index for an active entry in the profile table, hdsl2ShdslEndpointAlarmConfProfileTable, MUST be rejected.
.1.3.6.1.2.1.10.48.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrTable,,not-accessible,,current,,This table contains current status and performance information for segment endpoints in HDSL2/SHDSL lines. As with other tables in this MIB module indexed by ifIndex, entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.48.1.5.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex:hdsl2ShdslEndpointSide:hdsl2ShdslEndpointWirePair,current,,An entry in the hdsl2ShdslEndpointCurrTable. Each entry contains status and performance information relating to a single segment endpoint. It is indexed by the ifIndex of the HDSL2/SHDSL line, the UnitId of the associated unit, the side of the unit, and the wire pair of the associated modem.
.1.3.6.1.2.1.10.48.1.5.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrAtn,Integer32,read-only,,current,,The current loop attenuation for this endpoint as reported in a Network or Customer Side Performance Status message.
.1.3.6.1.2.1.10.48.1.5.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrSnrMgn,Integer32,read-only,,current,,The current SNR margin for this endpoint as reported in a Status Response/SNR message.
.1.3.6.1.2.1.10.48.1.5.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrStatus,BITS,read-only,,current,noDefect(0):powerBackoff(1):deviceFault(2):dcContinuityFault(3):snrMarginAlarm(4):loopAttenuationAlarm(5):loswFailureAlarm(6):configInitFailure(7):protocolInitFailure(8):noNeighborPresent(9):loopbackActive(10),Contains the current state of the endpoint. This is a bit-map of possible conditions. The various bit positions are as follows: noDefect There are no defects on the line. powerBackoff Indicates enhanced Power Backoff. deviceFault Indicates that a vendor-dependent diagnostic or self-test fault has been detected. dcContinuityFault Indicates vendor-dependent conditions that interfere with span powering such as short and open circuits. snrMarginAlarm Indicates that the SNR margin has dropped below the alarm threshold. loopAttenuationAlarm Indicates that the loop attenuation exceeds the alarm threshold. loswFailureAlarm Indicates a forward LOSW alarm. configInitFailure Endpoint failure during initialization due to paired endpoint not able to support requested configuration. protocolInitFailure Endpoint failure during initialization due to incompatible protocol used by the paired endpoint. noNeighborPresent Endpoint failure during initialization due to no activation sequence detected from paired endpoint. loopbackActive A loopback is currently active at this segment endpoint. This is intended to supplement ifOperStatus. Note that there is a 1:1 relationship between the status bits defined in this object and the notification thresholds defined elsewhere in this MIB module.
.1.3.6.1.2.1.10.48.1.5.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointES,Counter32,read-only,,current,,Count of Errored Seconds (ES) on this endpoint since the xU was last restarted.
.1.3.6.1.2.1.10.48.1.5.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointSES,Counter32,read-only,,current,,Count of Severely Errored Seconds (SES) on this endpoint since the xU was last restarted.
.1.3.6.1.2.1.10.48.1.5.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCRCanomalies,Counter32,read-only,,current,,Count of CRC anomalies on this endpoint since the xU was last restarted.
.1.3.6.1.2.1.10.48.1.5.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointLOSWS,Counter32,read-only,,current,,Count of Loss of Sync Word (LOSW) Seconds on this endpoint since the xU was last restarted.
.1.3.6.1.2.1.10.48.1.5.1.8,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointUAS,Counter32,read-only,,current,,Count of Unavailable Seconds (UAS) on this endpoint since the xU was last restarted.
.1.3.6.1.2.1.10.48.1.5.1.9,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr15MinTimeElapsed,Unsigned32,read-only,,current,,Total elapsed seconds in the current 15-minute interval.
.1.3.6.1.2.1.10.48.1.5.1.10,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr15MinES,Gauge32,read-only,,current,,Count of Errored Seconds (ES) in the current 15-minute interval.
.1.3.6.1.2.1.10.48.1.5.1.11,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr15MinSES,Gauge32,read-only,,current,,Count of Severely Errored Seconds (SES) in the current 15-minute interval.
.1.3.6.1.2.1.10.48.1.5.1.12,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr15MinCRCanomalies,Gauge32,read-only,,current,,Count of CRC anomalies in the current 15-minute interval.
.1.3.6.1.2.1.10.48.1.5.1.13,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr15MinLOSWS,Gauge32,read-only,,current,,Count of Loss of Sync Word (LOSW) Seconds in the current 15-minute interval.
.1.3.6.1.2.1.10.48.1.5.1.14,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr15MinUAS,Gauge32,read-only,,current,,Count of Unavailable Seconds (UAS) in the current 15-minute interval.
.1.3.6.1.2.1.10.48.1.5.1.15,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr1DayTimeElapsed,Unsigned32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.48.1.5.1.16,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr1DayES,Gauge32,read-only,,current,,Count of Errored Seconds (ES) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.48.1.5.1.17,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr1DaySES,Gauge32,read-only,,current,,Count of Severely Errored Seconds (SES) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.48.1.5.1.18,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr1DayCRCanomalies,Gauge32,read-only,,current,,Count of CRC anomalies during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.48.1.5.1.19,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr1DayLOSWS,Gauge32,read-only,,current,,Count of Loss of Sync Word (LOSW) Seconds during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.48.1.5.1.20,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurr1DayUAS,Gauge32,read-only,,current,,Count of Unavailable Seconds (UAS) during the current day as measured by hdsl2ShdslEndpointCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.48.1.5.1.21,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrTipRingReversal,INTEGER,read-only,,current,normal(1):reversed(2),This object indicates the state of the tip/ring for the wire pair.
.1.3.6.1.2.1.10.48.1.5.1.22,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrActivationState,INTEGER,read-only,,current,preActivation(1):activation(2):data(3),This object indicates the activation or training state of the wire pair.
.1.3.6.1.2.1.10.48.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalTable,,not-accessible,,current,,This table provides one row for each HDSL2/SHDSL endpoint performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.10.48.1.6.1,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex:hdsl2ShdslEndpointSide:hdsl2ShdslEndpointWirePair:hdsl2Shdsl15MinIntervalNumber,current,,An entry in the hdsl2Shdsl15MinIntervalTable.
.1.3.6.1.2.1.10.48.1.6.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalNumber,Unsigned32,not-accessible,,current,,Performance Data Interval number. Interval 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional.
.1.3.6.1.2.1.10.48.1.6.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalES,Gauge32,read-only,,current,,Count of Errored Seconds (ES) during the interval.
.1.3.6.1.2.1.10.48.1.6.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalSES,Gauge32,read-only,,current,,Count of Severely Errored Seconds (SES) during the interval.
.1.3.6.1.2.1.10.48.1.6.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalCRCanomalies,Gauge32,read-only,,current,,Count of CRC anomalies during the interval.
.1.3.6.1.2.1.10.48.1.6.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalLOSWS,Gauge32,read-only,,current,,Count of Loss of Sync Word (LOSW) Seconds during the interval.
.1.3.6.1.2.1.10.48.1.6.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalUAS,Gauge32,read-only,,current,,Count of Unavailable Seconds (UAS) during the interval.
.1.3.6.1.2.1.10.48.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalTable,,not-accessible,,current,,This table provides one row for each HDSL2/SHDSL endpoint performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.10.48.1.7.1,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex:hdsl2ShdslEndpointSide:hdsl2ShdslEndpointWirePair:hdsl2Shdsl1DayIntervalNumber,current,,An entry in the hdsl2Shdsl1DayIntervalTable.
.1.3.6.1.2.1.10.48.1.7.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalNumber,Unsigned32,not-accessible,,current,,History Data Interval number. Interval 1 is the most recent previous day; interval 30 is 30 days ago. Intervals 2..30 are optional.
.1.3.6.1.2.1.10.48.1.7.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalMoniSecs,Unsigned32,read-only,,current,,The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.48.1.7.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalES,Gauge32,read-only,,current,,Count of Errored Seconds (ES) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.48.1.7.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalSES,Gauge32,read-only,,current,,Count of Severely Errored Seconds (SES) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.48.1.7.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalCRCanomalies,Gauge32,read-only,,current,,Count of CRC anomalies during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.48.1.7.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalLOSWS,Gauge32,read-only,,current,,Count of Loss of Sync Word (LOSW) Seconds during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.48.1.7.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalUAS,Gauge32,read-only,,current,,Count of Unavailable Seconds (UAS) during the 1-day interval as measured by hdsl2Shdsl1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.48.1.8,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointMaintTable,,not-accessible,,current,,This table supports maintenance operations (e.g., loopbacks) to be performed on HDSL2/SHDSL segment endpoints. This table contains live data from equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.10.48.1.8.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointMaintEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex:hdsl2ShdslEndpointSide,current,,An entry in the hdsl2ShdslEndpointMaintTable. Each entry corresponds to a single segment endpoint and is indexed by the ifIndex of the HDSL2/SHDSL line, the UnitId of the associated unit, and the side of the unit.
.1.3.6.1.2.1.10.48.1.8.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintLoopbackConfig,INTEGER,read-write,,current,noLoopback(1):normalLoopback(2):specialLoopback(3),This object controls configuration of loopbacks for the associated segment endpoint. The status of the loopback is obtained via the hdsl2ShdslEndpointCurrStatus object.
.1.3.6.1.2.1.10.48.1.8.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintTipRingReversal,INTEGER,read-only,,current,normal(1):reversed(2),This object indicates the state of the tip/ring pair at the associated segment endpoint.
.1.3.6.1.2.1.10.48.1.8.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintPowerBackOff,INTEGER,read-write,,current,default(1):enhanced(2),This object configures the receiver at the associated segment endpoint to operate in default or enhanced power backoff mode.
.1.3.6.1.2.1.10.48.1.8.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintSoftRestart,INTEGER,read-write,,current,ready(1):restart(2),This object enables the manager to trigger a soft restart of the modem at the associated segment endpoint. The manager may only set this object to the 'restart(2)' value, which initiates a restart. The agent will perform a restart after approximately 5 seconds. Following the 5 second period, the agent will restore the object to the 'ready(1)' state.
.1.3.6.1.2.1.10.48.1.9,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslUnitMaintTable,,not-accessible,,current,,This table supports maintenance operations for units in a HDSL2/SHDSL line. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.48.1.9.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslUnitMaintEntry,,not-accessible,ifIndex:hdsl2ShdslInvIndex,current,,An entry in the hdsl2ShdslUnitMaintTable. Each entry corresponds to a single unit and is indexed by the ifIndex of the HDSL2/SHDSL line and the UnitId of the associated unit.
.1.3.6.1.2.1.10.48.1.9.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintLoopbackTimeout,Integer32,read-write,,current,,This object configures the timeout value for loopbacks initiated at segments endpoints contained in the associated unit. A value of 0 disables the timeout.
.1.3.6.1.2.1.10.48.1.9.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintUnitPowerSource,INTEGER,read-only,,current,local(1):span(2),This object indicates the DC power source being used by the associated unit.
.1.3.6.1.2.1.10.48.1.10,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfProfileTable,,not-accessible,,current,,This table supports definitions of span configuration profiles for SHDSL lines. HDSL2 does not support these configuration options. This table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.48.1.10.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfProfileEntry,,not-accessible,IMPLIEDhdsl2ShdslSpanConfProfileName,current,,Each entry corresponds to a single span configuration profile. Each profile contains a set of span configuration parameters. The configuration parameters in a profile are applied to those lines referencing that profile (see the hdsl2ShdslSpanConfProfile object). Profiles may be created/deleted using the row creation/deletion mechanism via hdsl2ShdslSpanConfProfileRowStatus. If an active entry is referenced in hdsl2ShdslSpanConfProfile, the entry MUST remain active until all references are removed.
.1.3.6.1.2.1.10.48.1.10.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfProfileName,OCTET,not-accessible,,current,,This object is the unique index associated with this profile. Entries in this table are referenced via the object hdsl2ShdslSpanConfProfile in Hdsl2ShdslSpanConfEntry.
.1.3.6.1.2.1.10.48.1.10.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfWireInterface,INTEGER,read-create,,current,twoWire(1):fourWire(2):sixWire(3):eightWire(4),This object configures the two-wire or optional four-wire, six-wire, or eight-wire operation for SHDSL lines.
.1.3.6.1.2.1.10.48.1.10.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfMinLineRate,Unsigned32,read-create,,current,,This object configures the minimum transmission rate for the associated SHDSL Line in bits-per-second (bps) and includes both payload (user data) and any applicable framing overhead. If the minimum line rate equals the maximum line rate (hdsl2ShdslSpanMaxLineRate), the line rate is considered 'fixed'. If the minimum line rate is less than the maximum line rate, the line rate is considered 'rate-adaptive'.
.1.3.6.1.2.1.10.48.1.10.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfMaxLineRate,Unsigned32,read-create,,current,,This object configures the maximum transmission rate for the associated SHDSL Line in bits-per-second (bps) and includes both payload (user data) and any applicable framing overhead. If the minimum line rate equals the maximum line rate (hdsl2ShdslSpanMaxLineRate), the line rate is considered 'fixed'. If the minimum line rate is less than the maximum line rate, the line rate is considered 'rate-adaptive'.
.1.3.6.1.2.1.10.48.1.10.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfPSD,INTEGER,read-create,,current,symmetric(1):asymmetric(2),This object configures use of symmetric/asymmetric PSD (Power Spectral Density) Mask for the associated SHDSL Line. Support for symmetric PSD is mandatory for all supported data rates. Support for asymmetric PSD is optional.
.1.3.6.1.2.1.10.48.1.10.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfTransmissionMode,BITS,read-create,,current,region1(0):region2(1),This object specifies the regional setting for the SHDSL line.
.1.3.6.1.2.1.10.48.1.10.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfRemoteEnabled,INTEGER,read-create,,current,enabled(1):disabled(2),This object enables/disables support for remote management of the units in an SHDSL line from the STU-R via the EOC.
.1.3.6.1.2.1.10.48.1.10.1.8,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfPowerFeeding,INTEGER,read-create,,current,noPower(1):powerFeed(2):wettingCurrent(3),This object enables/disables support for optional power feeding in an SHDSL line.
.1.3.6.1.2.1.10.48.1.10.1.9,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfCurrCondTargetMarginDown,Integer32,read-create,,current,,This object specifies the downstream current condition target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
.1.3.6.1.2.1.10.48.1.10.1.10,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfWorstCaseTargetMarginDown,Integer32,read-create,,current,,This object specifies the downstream worst-case target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
.1.3.6.1.2.1.10.48.1.10.1.11,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfCurrCondTargetMarginUp,Integer32,read-create,,current,,This object specifies the upstream current-condition target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
.1.3.6.1.2.1.10.48.1.10.1.12,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfWorstCaseTargetMarginUp,Integer32,read-create,,current,,This object specifies the upstream worst-case target SNR margin for an SHDSL line. The SNR margin is the difference between the desired SNR and the actual SNR. Target SNR margin is the desired SNR margin for a unit.
.1.3.6.1.2.1.10.48.1.10.1.13,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfUsedTargetMargins,BITS,read-create,,current,currCondDown(0):worstCaseDown(1):currCondUp(2):worstCaseUp(3),Indicates whether a target SNR margin is enabled or disabled. This is a bit-map of possible settings. The various bit positions are as follows: currCondDown - current-condition downstream target SNR margin enabled worstCaseDown - worst-case downstream target SNR margin enabled currCondUp - current-condition upstream target SNR margin enabled worstCaseUp - worst-case upstream target SNR margin enabled.
.1.3.6.1.2.1.10.48.1.10.1.14,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfReferenceClock,INTEGER,read-create,,current,localClk(1):networkClk(2):dataOrNetworkClk(3):dataClk(4),This object configures the clock reference for the STU-C in an SHDSL Line.
.1.3.6.1.2.1.10.48.1.10.1.15,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfLineProbeEnable,INTEGER,read-create,,current,disable(1):enable(2),This object enables/disables support for Line Probe of the units in an SHDSL line. When Line Probe is enabled, the system performs Line Probing to find the best possible rate. If Line Probe is disabled, the rate adaptation phase is skipped to shorten set up time.
.1.3.6.1.2.1.10.48.1.10.1.16,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls creation/deletion of the associated entry in this table per the semantics of RowStatus. If an active entry is referenced in hdsl2ShdslSpanConfProfile, the entry MUST remain active until all references are removed.
.1.3.6.1.2.1.10.48.1.11,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointAlarmConfProfileTable,,not-accessible,,current,,This table supports definitions of alarm configuration profiles for HDSL2/SHDSL segment endpoints. This table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.48.1.11.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointAlarmConfProfileEntry,,not-accessible,IMPLIEDhdsl2ShdslEndpointAlarmConfProfileName,current,,Each entry corresponds to a single alarm configuration profile. Each profile contains a set of parameters for setting alarm thresholds for various performance attributes monitored at HDSL2/SHDSL segment endpoints. Profiles may be created/deleted using the row creation/deletion mechanism via hdsl2ShdslEndpointAlarmConfProfileRowStatus. If an active entry is referenced in either hdsl2ShdslSpanConfAlarmProfile or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain active until all references are removed.
.1.3.6.1.2.1.10.48.1.11.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointAlarmConfProfileName,OCTET,not-accessible,,current,,This object is the unique index associated with this profile.
.1.3.6.1.2.1.10.48.1.11.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshLoopAttenuation,Integer32,read-create,,current,,This object configures the loop attenuation alarm threshold. When the current value of hdsl2ShdslEndpointCurrAtn reaches or exceeds this threshold, an hdsl2ShdslLoopAttenCrossing MAY be generated.
.1.3.6.1.2.1.10.48.1.11.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshSNRMargin,Integer32,read-create,,current,,This object configures the SNR margin alarm threshold. When the current value of hdsl2ShdslEndpointCurrSnrMgn reaches or drops below this threshold, a hdsl2ShdslSNRMarginCrossing MAY be generated.
.1.3.6.1.2.1.10.48.1.11.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshES,Unsigned32,read-create,,current,,This object configures the threshold for the number of Errored Seconds (ES) within any given 15-minute performance data collection interval. If the value of Errored Seconds in a particular 15-minute collection interval reaches/ exceeds this value, an hdsl2ShdslPerfESThresh MAY be generated. At most, one notification will be sent per interval per endpoint.
.1.3.6.1.2.1.10.48.1.11.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshSES,Unsigned32,read-create,,current,,This object configures the threshold for the number of Severely Errored Seconds (SES) within any given 15-minute performance data collection interval. If the value of Severely Errored Seconds in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfSESThresh MAY be generated. At most, one notification will be sent per interval per endpoint.
.1.3.6.1.2.1.10.48.1.11.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshCRCanomalies,Integer32,read-create,,current,,This object configures the threshold for the number of CRC anomalies within any given 15-minute performance data collection interval. If the value of CRC anomalies in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfCRCanomaliesThresh MAY be generated. At most, one notification will be sent per interval per endpoint.
.1.3.6.1.2.1.10.48.1.11.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshLOSWS,Unsigned32,read-create,,current,,This object configures the threshold for the number of Loss of Sync Word (LOSW) Seconds within any given 15-minute performance data collection interval. If the value of LOSW in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfLOSWSThresh MAY be generated. At most, one notification will be sent per interval per endpoint.
.1.3.6.1.2.1.10.48.1.11.1.8,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointThreshUAS,Unsigned32,read-create,,current,,This object configures the threshold for the number of Unavailable Seconds (UAS) within any given 15-minute performance data collection interval. If the value of UAS in a particular 15-minute collection interval reaches/exceeds this value, an hdsl2ShdslPerfUASThresh MAY be generated. At most, one notification will be sent per interval per endpoint.
.1.3.6.1.2.1.10.48.1.11.1.9,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointAlarmConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls creation/deletion of the associated entry in this table as per the semantics of RowStatus. If an active entry is referenced in either hdsl2ShdslSpanConfAlarmProfile or hdsl2ShdslEndpointAlarmConfProfile, the entry MUST remain active until all references are removed.
.1.3.6.1.2.1.10.48.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslConformance,,,,,,
.1.3.6.1.2.1.10.48.3.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslGroups,,,,,,
.1.3.6.1.2.1.10.48.3.1.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfGroup,,,,,,This group supports objects for configuring span-related parameters for HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanStatusGroup,,,,,,This group supports objects for retrieving span-related status for HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.3,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInventoryShdslGroup,,,,,,This group supports objects for retrieving SHDSL-specific inventory information.
.1.3.6.1.2.1.10.48.3.1.4,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanShdslStatusGroup,,,,,,This group supports objects for retrieving SHDSL-specific span-related status.
.1.3.6.1.2.1.10.48.3.1.5,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslInventoryGroup,,,,,,This group supports objects that provide unit inventory information about the units in HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.6,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointConfGroup,,,,,,This group supports objects for configuring parameters for segment endpoints in HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.7,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointCurrGroup,,,,,,This group supports objects that provide current status and performance measurements relating to segment endpoints in HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.8,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl15MinIntervalGroup,,,,,,This group supports objects that maintain historic performance measurements relating to segment endpoints in HDSL2/SHDSL lines in 15-minute intervals.
.1.3.6.1.2.1.10.48.3.1.9,HDSL2-SHDSL-LINE-MIB::hdsl2Shdsl1DayIntervalGroup,,,,,,This group supports objects that maintain historic performance measurements relating to segment endpoints in HDSL2/SHDSL lines in 1-day intervals.
.1.3.6.1.2.1.10.48.3.1.10,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslMaintenanceGroup,,,,,,This group supports objects that provide support for maintenance actions for HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.11,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslEndpointAlarmConfGroup,,,,,,This group supports objects that allow configuration of alarm thresholds for various performance parameters for HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.12,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslNotificationGroup,,,,,,This group supports notifications of significant conditions associated with HDSL2/SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.13,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslSpanConfProfileGroup,,,,,,This group supports objects that constitute configuration profiles for configuring span-related parameters in SHDSL lines.
.1.3.6.1.2.1.10.48.3.1.14,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslWirePairGroup,,,,,,This group supports objects that provide the status of SHDSL-specific wire pairs.
.1.3.6.1.2.1.10.48.3.1.15,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslPayloadRateGroup,,,,,,This group supports objects for retrieving payload rates that exclude any framing overhead.
.1.3.6.1.2.1.10.48.3.2,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslCompliances,,,,,,
.1.3.6.1.2.1.10.48.3.2.1,HDSL2-SHDSL-LINE-MIB::hdsl2ShdslLineMibCompliance,,,,,,The compliance statement for SNMP entities that implement HDSL2 and SHDSL. The version of SHDSL supported in this compliance statement is g.shdsl. **** This compliance statement is deprecated. ****
.1.3.6.1.2.1.10.48.3.2.2,HDSL2-SHDSL-LINE-MIB::hdsl2GshdslbisLineMibCompliance,,,,,,The compliance statement for SNMP entities that implement HDSL2 and SHDSL. The version of SHDSL supported in this compliance statement is g.shdsl.bis.
.1.3.6.1.2.1.10.49,APS-MIB::apsMIB,,,,,,This management information module supports the configuration and management of SONET linear APS groups. The definitions and descriptions used in this MIB have been derived from Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria, GR-253-CORE Issue 3, September 2000, section 5.3. The MIB is also consistent with the Multiplex Section Protection (MSP) protocol as specified in ITU-T Recommendation G.783, Characteristics of synchronous digital hierarchy (SDH) equipment function blocks, Annex A and B. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3498; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.10.49.1,APS-MIB::apsMIBObjects,,,,,,
.1.3.6.1.2.1.10.49.1.1,APS-MIB::apsConfig,,,,,,
.1.3.6.1.2.1.10.49.1.1.1,APS-MIB::apsConfigGroups,Gauge32,read-only,,current,,The count of APS groups. This count includes all rows in apsConfigTable, regardless of the value of apsConfigRowStatus.
.1.3.6.1.2.1.10.49.1.1.2,APS-MIB::apsConfigTable,,not-accessible,,current,,This table lists the APS groups that have been configured on the system.
.1.3.6.1.2.1.10.49.1.1.2.1,APS-MIB::apsConfigEntry,,not-accessible,IMPLIEDapsConfigName,current,,A conceptual row in the apsConfigTable.
.1.3.6.1.2.1.10.49.1.1.2.1.1,APS-MIB::apsConfigName,OCTET,not-accessible,,current,,A textual name for the APS group.
.1.3.6.1.2.1.10.49.1.1.2.1.2,APS-MIB::apsConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this APS group entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Also, all associated apsChanConfigEntry rows must represent a set of consecutive channel numbers beginning with 0 or 1, depending on the selected architecture. When set to notInService changes may be made to apsConfigMode, apsConfigRevert, apsConfigDirection, apsConfigExtraTraffic, apsConfigSdBerThreshold, apsConfigSfBerThreshold, and apsConfigWaitToRestore. Also, associated apsChanConfigTable objects may be added, deleted and modified.
.1.3.6.1.2.1.10.49.1.1.2.1.3,APS-MIB::apsConfigMode,INTEGER,read-create,,current,onePlusOne(1):oneToN(2):onePlusOneCompatible(3):onePlusOneOptimized(4),The architecture of the APS group. onePlusOne The 1+1 architecture permanently bridges the working line to the protection line. oneToN The 1:n architecture allows one protection channel to protect up to n working channels. When a fault is detected on one of the n working channels that channel is bridged over the protection channel. onePlusOneCompatible This refers to 1 + 1 bidirectional switching compatible with 1:n bidirectional switching as specified in ITU-T Recommendation G.783 (04/97) section A.3.4.1. Since this mode necessitates bidirectional switching, apsConfigDirection must be set to bidirectional whenever onePlusOneCompatible is set. onePlusOneOptimized This refers to 1 + 1 bidirectional switching optimized for a network using predominantly 1 + 1 bidirectional switching as specified in ITU-T Recommendation G.783 (04/97) section B.1. Since this mode necessitates bidirectional switching, apsConfigDirection must be set to bidirectional whenever onePlusOneOptimized is set. This object may not be modified if the associated apsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.49.1.1.2.1.4,APS-MIB::apsConfigRevert,INTEGER,read-create,,current,nonrevertive(1):revertive(2),The revertive mode of the APS group. nonrevertive Traffic remains on the protection line until another switch request is received. revertive When the condition that caused a switch to the protection line has been cleared the signal is switched back to the working line. Since switching is revertive with the 1:n architecture, apsConfigRevert must be set to revertive if apsConfigMode is set to oneToN. Switching may optionally be revertive with the 1+1 architecture. This object may not be modified if the associated apsConfigRowStatus object is equal to active(1). 
.1.3.6.1.2.1.10.49.1.1.2.1.5,APS-MIB::apsConfigDirection,INTEGER,read-create,,current,unidirectional(1):bidirectional(2),The directional mode of the APS group. unidirectional The unidirectional mode provides protection in one direction. bidirectional The bidirectional mode provides protection in both directions. This object may not be modified if the associated apsConfigRowStatus object is equal to active(1). 
.1.3.6.1.2.1.10.49.1.1.2.1.6,APS-MIB::apsConfigExtraTraffic,INTEGER,read-create,,current,enabled(1):disabled(2),This object enables or disables the transfer of extra traffic on the protection channel in a 1:n architecture. This object must be set to disabled if the architecture is 1+1. It may be necessary to disable this in order to interwork with other SONET network elements that don't support extra traffic. This object may not be modified if the associated apsConfigRowStatus object is equal to active(1). 
.1.3.6.1.2.1.10.49.1.1.2.1.7,APS-MIB::apsConfigSdBerThreshold,Integer32,read-create,,current,,The Signal Degrade Bit Error Rate. The negated value of this number is used as the exponent of 10 for computing the threshold value for the Bit Error Rate (BER). For example, a value of 5 indicates a BER threshold of 10^-5. This object may be modified if the associated apsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.49.1.1.2.1.8,APS-MIB::apsConfigSfBerThreshold,Integer32,read-create,,current,,The Signal Failure Bit Error Rate. The negated value of this number is used as the exponent of 10 for computing the threshold value for the Bit Error Rate (BER). For example, a value of 5 indicates a BER threshold of 10^-5. This object may be modified if the associated apsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.49.1.1.2.1.9,APS-MIB::apsConfigWaitToRestore,Integer32,read-create,,current,,The Wait To Restore period in seconds. After clearing of a condition that necessitated an automatic switch, the wait to restore period must elapse before reverting. This is intended to avoid rapid switch oscillations. GR-253-CORE specifies a Wait To Restore range of 5 to 12 minutes. G.783 defines a 5 to 12 minute Wait To Restore range in section 5.4.1.1.3, but also allows for a shorter WTR period in Table 2-1, WaitToRestore value (MI_WTRtime: 0..(5)..12 minutes). This object may not be modified if the associated apsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.49.1.1.2.1.10,APS-MIB::apsConfigCreationTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time the row was created
.1.3.6.1.2.1.10.49.1.1.2.1.11,APS-MIB::apsConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.49.1.2,APS-MIB::apsStatusTable,,not-accessible,,current,,This table provides status information about APS groups that have been configured on the system.
.1.3.6.1.2.1.10.49.1.2.1,APS-MIB::apsStatusEntry,,not-accessible,,current,,A conceptual row in the apsStatusTable.
.1.3.6.1.2.1.10.49.1.2.1.1,APS-MIB::apsStatusK1K2Rcv,OCTET,read-only,,current,,The current value of the K1 and K2 bytes received on the protection channel.
.1.3.6.1.2.1.10.49.1.2.1.2,APS-MIB::apsStatusK1K2Trans,OCTET,read-only,,current,,The current value of the K1 and K2 bytes transmitted on the protection channel.
.1.3.6.1.2.1.10.49.1.2.1.3,APS-MIB::apsStatusCurrent,BITS,read-only,,current,modeMismatch(0):channelMismatch(1):psbf(2):feplf(3):extraTraffic(4),The current status of the APS group. modeMismatch Modes other than 1+1 unidirectional monitor protection line K2 bit 5, which indicates the architecture and K2 bits 6-8, which indicate if the mode is unidirectional or bidirectional. A conflict between the current local mode and the received K2 mode information constitutes a mode mismatch. channelMismatch This bit indicates a mismatch between the transmitted K1 channel and the received K2 channel has been detected. psbf This bit indicates a Protection Switch Byte Failure (PSBF) is in effect. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames. feplf Modes other than 1+1 unidirectional monitor the K1 byte for Far-End Protection-Line failures. A Far-End Protection-Line defect is declared based on receiving SF on the protection line. extraTraffic This bit indicates whether extra traffic is currently being accepted on the protection line. 
.1.3.6.1.2.1.10.49.1.2.1.4,APS-MIB::apsStatusModeMismatches,Counter32,read-only,,current,,A count of Mode Mismatch conditions. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.2.1.5,APS-MIB::apsStatusChannelMismatches,Counter32,read-only,,current,,A count of Channel Mismatch conditions. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.2.1.6,APS-MIB::apsStatusPSBFs,Counter32,read-only,,current,,A count of Protection Switch Byte Failure conditions. This condition occurs when either an inconsistent APS byte or an invalid code is detected. An inconsistent APS byte occurs when no three consecutive K1 bytes of the last 12 successive frames are identical, starting with the last frame containing a previously consistent byte. An invalid code occurs when the incoming K1 byte contains an unused code or a code irrelevant for the specific switching operation (e.g., Reverse Request while no switching request is outstanding) in three consecutive frames. An invalid code also occurs when the incoming K1 byte contains an invalid channel number in three consecutive frames. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.2.1.7,APS-MIB::apsStatusFEPLFs,Counter32,read-only,,current,,A count of Far-End Protection-Line Failure conditions. This condition is declared based on receiving SF on the protection line in the K1 byte. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.2.1.8,APS-MIB::apsStatusSwitchedChannel,Integer32,read-only,,current,,This field is set to the number of the channel that is currently switched to protection. The value 0 indicates no channel is switched to protection. The values 1-14 indicate that working channel is switched to protection.
.1.3.6.1.2.1.10.49.1.2.1.9,APS-MIB::apsStatusDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this APS group's counters suffered a discontinuity. The relevant counters are the specific instances associated with this APS group of any Counter32 object contained in apsStatusTable. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.49.1.3,APS-MIB::apsMap,,,,,,
.1.3.6.1.2.1.10.49.1.3.1,APS-MIB::apsChanLTEs,Gauge32,read-only,,current,,The count of SONET LTE interfaces on the system. Each interface that is included has an ifType value of sonet(39).
.1.3.6.1.2.1.10.49.1.3.2,APS-MIB::apsMapTable,,not-accessible,,current,,This table lists the SONET LTE interfaces on the system. Each interface that is listed has an ifType value of sonet(39).
.1.3.6.1.2.1.10.49.1.3.2.1,APS-MIB::apsMapEntry,,not-accessible,ifIndex,current,,A conceptual row in the apsMapTable.
.1.3.6.1.2.1.10.49.1.3.2.1.2,APS-MIB::apsMapGroupName,OCTET,read-only,,current,,A textual name for the APS group which this channel is included in. If the channel is not part of an APS group this value is set to a string of size 0. When an instance of apsChanConfigIfIndex is set equal to an instance of ifIndex that has an ifType value of sonet(39), apsMapGroupName is set equal to the corresponding value of apsChanConfigGroupName. If an instance of ifIndex that has an ifType value of sonet(39) ceases to be equal to an instance of apsChanConfigIfIndex, either because of a change in the value of apsChanConfigIfIndex, or because of row deletion in the ApsChanConfigTable, apsMapGroupName is set to a string of size 0.
.1.3.6.1.2.1.10.49.1.3.2.1.3,APS-MIB::apsMapChanNumber,Integer32,read-only,,current,,This field is set to a unique channel number within an APS group. The value 0 indicates the null channel. The values 1-14 define a working channel. If the SONET LTE is not part of an APS group this value is set to -1. When an instance of apsChanConfigIfIndex is set equal to an instance of ifIndex that has an ifType value of sonet(39), apsMapChanNumber is set equal to the corresponding value of apsChanConfigNumber. If an instance of ifIndex that has an ifType value of sonet(39) ceases to be equal to an instance of apsChanConfigIfIndex, either because of a change in the value of apsChanConfigIfIndex, or because of row deletion in the ApsChanConfigTable, apsMapChanNumber is set to -1.
.1.3.6.1.2.1.10.49.1.4,APS-MIB::apsChanConfigTable,,not-accessible,,current,,This table lists the APS channels that have been configured in APS groups.
.1.3.6.1.2.1.10.49.1.4.1,APS-MIB::apsChanConfigEntry,,not-accessible,apsChanConfigGroupName:apsChanConfigNumber,current,,A conceptual row in the apsChanConfigTable.
.1.3.6.1.2.1.10.49.1.4.1.1,APS-MIB::apsChanConfigGroupName,OCTET,not-accessible,,current,,A textual name for the APS group which this channel is included in.
.1.3.6.1.2.1.10.49.1.4.1.2,APS-MIB::apsChanConfigNumber,Integer32,not-accessible,,current,,This field is set to a unique channel number within an APS group. The value 0 indicates the null channel. The values 1-14 define a working channel. This field must be assigned a unique number within the group.
.1.3.6.1.2.1.10.49.1.4.1.3,APS-MIB::apsChanConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this APS channel entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. A row in the apsChanConfigTable may not be created, deleted, set to notInService or otherwise modified if the apsChanConfigGroupName value is equal to an apsConfigName value and the associated apsConfigRowStatus object is equal to active. However, if the apsConfigRowStatus object is equal to notInService, a row may be created, deleted or modified. In other words, a channel may not be added, deleted or modified if the group is active. A row may be created with an apsChanConfigGroupName value that is not equal to any existing instance of apsConfigName. This action is the initial step in adding a SONET LTE to a new APS group. If this object is set to destroy, the associated instance of apsMapGroupName will be set to a string of size 0 and the apsMapChanNumber will be set to -1. The channel status entry will also be deleted by this action. apsChanConfigNumber must be set to a unique channel number within the APS group. The value 0 indicates the null channel. The values 1-14 define a working channel. When an attempt is made to set the corresponding apsConfigRowStatus field to active the apsChanConfigNumber values of all entries with equal apsChanConfigGroupName fields must represent a set of consecutive integer values beginning with 0 or 1, depending on the architecture of the group, and ending with n, where n is greater than or equal to 1 and less than or equal to 14. Otherwise, the error inconsistentValue is returned to the apsConfigRowStatus set attempt.
.1.3.6.1.2.1.10.49.1.4.1.4,APS-MIB::apsChanConfigIfIndex,Integer32,read-create,,current,,The Interface Index assigned to a SONET LTE. This is an interface with ifType sonet(39). The value of this object must be unique among all instances of apsChanConfigIfIndex. In other words, a particular SONET LTE can only be configured in one APS group. This object cannot be set if the apsChanConfigGroupName instance associated with this row is equal to an instance of apsConfigName and the corresponding apsConfigRowStatus object is set to active. In other words this value cannot be changed if the APS group is active. However, this value may be changed if the apsConfigRowStatus value is equal to notInService.
.1.3.6.1.2.1.10.49.1.4.1.5,APS-MIB::apsChanConfigPriority,INTEGER,read-create,,current,low(1):high(2),The priority of the channel. This field determines whether high or low priority SD and SF codes are used in K1 requests. This field is only applicable if the channel is to be included in a group using the 1:n architecture. It is not applicable if the channel is to be included in a group using the 1+1 architecture, and is ignored in that case. This object cannot be set if the apsChanConfigGroupName instance associated with this row is equal to an instance of apsConfigName and the corresponding apsConfigRowStatus object is set to active. In other words this value cannot be changed if the APS group is active. However, this value may be changed if the apsConfigRowStatus value is equal to notInService.
.1.3.6.1.2.1.10.49.1.4.1.6,APS-MIB::apsChanConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.49.1.5,APS-MIB::apsCommandTable,,not-accessible,,current,,This table allows commands to be sent to configured APS groups.
.1.3.6.1.2.1.10.49.1.5.1,APS-MIB::apsCommandEntry,,not-accessible,apsChanConfigGroupName:apsChanConfigNumber,current,,A conceptual row in the apsCommandTable. This row exists only if the associated apsConfigEntry is active.
.1.3.6.1.2.1.10.49.1.5.1.1,APS-MIB::apsCommandSwitch,INTEGER,read-write,,current,noCmd(1):clear(2):lockoutOfProtection(3):forcedSwitchWorkToProtect(4):forcedSwitchProtectToWork(5):manualSwitchWorkToProtect(6):manualSwitchProtectToWork(7):exercise(8),Allows the initiation of an APS switch command on the APS group and channel specified by the index values. When read this object returns the last command written or noCmd if no command has been written to this channel since initialization. The return of the last command written does not imply that this command is currently in effect. This request may have been preempted by a higher priority local or remote request. In order to determine the current state of the APS group it is necessary to read the objects apsStatusK1K2Rcv and apsStatusK1K2Trans. The value lockoutOfProtection should only be applied to the protection line channel since that switch command prevents any of the working channels from switching to the protection line. Following the same logic, forcedSwitchProtectToWork and manualSwitchProtectToWork should only be applied to the protection line channel. forcedSwitchWorkToProtect and manualSwitchWorkToProtect should only be applied to a working channel.
.1.3.6.1.2.1.10.49.1.5.1.2,APS-MIB::apsCommandControl,INTEGER,read-write,,current,noCmd(1):lockoutWorkingChannel(2):clearLockoutWorkingChannel(3),Allows the initiation of an APS control command on the APS group and channel specified by the index values. When read this object returns the last command written or noCmd if no command has been written to this channel since initialization. This object does not apply to the protection line.
.1.3.6.1.2.1.10.49.1.6,APS-MIB::apsChanStatusTable,,not-accessible,,current,,This table contains status information for all SONET LTE interfaces that are included in APS groups.
.1.3.6.1.2.1.10.49.1.6.1,APS-MIB::apsChanStatusEntry,,not-accessible,,current,,A conceptual row in the apsChanStatusTable.
.1.3.6.1.2.1.10.49.1.6.1.1,APS-MIB::apsChanStatusCurrent,BITS,read-only,,current,lockedOut(0):sd(1):sf(2):switched(3):wtr(4),Indicates the current state of the port. lockedOut This bit, when applied to a working channel, indicates that the channel is prevented from switching to the protection line. When applied to the null channel, this bit indicates that no working channel may switch to the protection line. sd A signal degrade condition is in effect. sf A signal failure condition is in effect. switched The switched bit is applied to a working channel if that channel is currently switched to the protection line. wtr A Wait-to-Restore state is in effect.
.1.3.6.1.2.1.10.49.1.6.1.2,APS-MIB::apsChanStatusSignalDegrades,Counter32,read-only,,current,,A count of Signal Degrade conditions. This condition occurs when the line Bit Error Rate exceeds the currently configured value of the relevant instance of apsConfigSdBerThreshold. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsChanStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.6.1.3,APS-MIB::apsChanStatusSignalFailures,Counter32,read-only,,current,,A count of Signal Failure conditions that have been detected on the incoming signal. This condition occurs when a loss of signal, loss of frame, AIS-L or a Line bit error rate exceeding the currently configured value of the relevant instance of apsConfigSfBerThreshold. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsChanStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.6.1.4,APS-MIB::apsChanStatusSwitchovers,Counter32,read-only,,current,,When queried with index value apsChanConfigNumber other than 0, this object will return the number of times this channel has switched to the protection line. When queried with index value apsChanConfigNumber set to 0, which is the protection line, this object will return the number of times that any working channel has been switched back to the working line from this protection line. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsChanStatusDiscontinuityTime.
.1.3.6.1.2.1.10.49.1.6.1.5,APS-MIB::apsChanStatusLastSwitchover,TimeTicks,read-only,,current,,When queried with index value apsChanConfigNumber other than 0, this object will return the value of sysUpTime when this channel last completed a switch to the protection line. If this channel has never switched to the protection line, the value 0 will be returned. When queried with index value apsChanConfigNumber set to 0, which is the protection line, this object will return the value of sysUpTime the last time that a working channel was switched back to the working line from this protection line. If no working channel has ever switched back to the working line from this protection line, the value 0 will be returned.
.1.3.6.1.2.1.10.49.1.6.1.6,APS-MIB::apsChanStatusSwitchoverSeconds,Counter32,read-only,,current,,The cumulative Protection Switching Duration (PSD) time in seconds. For a working channel, this is the cumulative number of seconds that service was carried on the protection line. For the protection line, this is the cumulative number of seconds that the protection line has been used to carry any working channel traffic. This information is only valid if revertive switching is enabled. The value 0 will be returned otherwise. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of apsChanStatusDiscontinuityTime. For example, if the value of an instance of apsChanStatusSwitchoverSeconds changes from a non-zero value to zero due to revertive switching being disabled, it is expected that the corresponding value of apsChanStatusDiscontinuityTime will be updated to reflect the time of the configuration change. 
.1.3.6.1.2.1.10.49.1.6.1.7,APS-MIB::apsChanStatusDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this channel's counters suffered a discontinuity. The relevant counters are the specific instances associated with this channel of any Counter32 object contained in apsChanStatusTable. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.49.1.7,APS-MIB::apsNotificationEnable,BITS,read-write,,current,switchover(0):modeMismatch(1):channelMismatch(2):psbf(3):feplf(4),Provides the ability to enable and disable notifications defined in this MIB. switchover Indicates apsEventSwitchover notifications should be generated. modeMismatch Indicates apsEventModeMismatch notifications should be generated. channelMismatch Indicates apsEventChannelMismatch notifications should be generated. psbf Indicates apsEventPSBF notifications should be generated. feplf Indicates apsEventFEPLF notifications should be generated. 
.1.3.6.1.2.1.10.49.2,APS-MIB::apsMIBNotifications,,,,,,
.1.3.6.1.2.1.10.49.2.0,APS-MIB::apsNotificationsPrefix,,,,,,
.1.3.6.1.2.1.10.49.2.0.1,APS-MIB::apsEventSwitchover,,,,,,An apsEventSwitchover notification is sent when the value of an instance of apsChanStatusSwitchovers increments.
.1.3.6.1.2.1.10.49.2.0.2,APS-MIB::apsEventModeMismatch,,,,,,An apsEventModeMismatch notification is sent when the value of an instance of apsStatusModeMismatches increments.
.1.3.6.1.2.1.10.49.2.0.3,APS-MIB::apsEventChannelMismatch,,,,,,An apsEventChannelMismatch notification is sent when the value of an instance of apsStatusChannelMismatches increments.
.1.3.6.1.2.1.10.49.2.0.4,APS-MIB::apsEventPSBF,,,,,,An apsEventPSBF notification is sent when the value of an instance of apsStatusPSBFs increments.
.1.3.6.1.2.1.10.49.2.0.5,APS-MIB::apsEventFEPLF,,,,,,An apsEventFEPLFs notification is sent when the value of an instance of apsStatusFEPLFs increments.
.1.3.6.1.2.1.10.49.3,APS-MIB::apsMIBConformance,,,,,,
.1.3.6.1.2.1.10.49.3.1,APS-MIB::apsGroups,,,,,,
.1.3.6.1.2.1.10.49.3.1.1,APS-MIB::apsConfigGeneral,,,,,,A collection of apsConfigTable objects providing configuration information applicable to all linear APS groups.
.1.3.6.1.2.1.10.49.3.1.2,APS-MIB::apsConfigWtr,,,,,,The apsConfigTable object that provides information which is applicable to groups supporting a configurable WTR period.
.1.3.6.1.2.1.10.49.3.1.3,APS-MIB::apsCommandOnePlusOne,,,,,,The apsCommandTable object which is applicable to groups implementing the linear APS 1+1 architecture. Also, set operations must be supported.
.1.3.6.1.2.1.10.49.3.1.4,APS-MIB::apsCommandOneToN,,,,,,A collection of apsCommandTable objects which are applicable to groups implementing the linear APS 1:n architecture. Also, set operations must be supported.
.1.3.6.1.2.1.10.49.3.1.5,APS-MIB::apsStatusGeneral,,,,,,A collection of apsStatusTable objects providing status information applicable to all linear APS groups.
.1.3.6.1.2.1.10.49.3.1.6,APS-MIB::apsChanGeneral,,,,,,A collection of channel objects providing information applicable to all linear APS channels.
.1.3.6.1.2.1.10.49.3.1.7,APS-MIB::apsChanOneToN,,,,,,The apsChanConfigTable object that provides information which is only applicable to groups implementing the linear APS 1:n architecture.
.1.3.6.1.2.1.10.49.3.1.8,APS-MIB::apsTotalsGroup,,,,,,A collection of objects providing optional counts of configured APS groups and SONET LTE interfaces.
.1.3.6.1.2.1.10.49.3.1.9,APS-MIB::apsMapGroup,,,,,,A collection of apsMapTable objects providing a mapping from sonet(39) InterfaceIndex to group name and channel number for assigned APS channels and a list of unassigned sonet(39) interfaces.
.1.3.6.1.2.1.10.49.3.1.10,APS-MIB::apsEventGroup,,,,,,A collection of SONET linear APS notifications.
.1.3.6.1.2.1.10.49.3.2,APS-MIB::apsCompliances,,,,,,
.1.3.6.1.2.1.10.49.3.2.1,APS-MIB::apsFullCompliance,,,,,,When this MIB is implemented with support for read-create, then such an implementation can claim read/write compliance. Linear APS groups can then be both monitored and configured with this MIB. Note that An agent is not required to process SNMP Set Requests that affect multiple control objects within this MIB. This is intended to simplify the processing of Set Requests for the various control tables by eliminating the possibility that a single Set PDU will contain multiple varbinds which are in conflict. 
.1.3.6.1.2.1.10.49.3.2.2,APS-MIB::apsReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-create (i.e. in read-only mode), then that implementation can claim read-only compliance. In that case, linear APS groups can be monitored but cannot be configured with this MIB.
.1.3.6.1.2.1.10.56,FC-MGMT-MIB::fcMgmtMIB,,,,,,This module defines management information specific to Fibre Channel-attached devices. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4044; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.56.1,FC-MGMT-MIB::fcmgmtObjects,,,,,,
.1.3.6.1.2.1.10.56.1.1,FC-MGMT-MIB::fcmInstanceTable,,not-accessible,,current,,Information about the local Fibre Channel management instances.
.1.3.6.1.2.1.10.56.1.1.1,FC-MGMT-MIB::fcmInstanceEntry,,not-accessible,fcmInstanceIndex,current,,A list of attributes for a particular local Fibre Channel management instance.
.1.3.6.1.2.1.10.56.1.1.1.1,FC-MGMT-MIB::fcmInstanceIndex,Unsigned32,not-accessible,,current,,An arbitrary integer value that uniquely identifies this instance amongst all local Fibre Channel management instances. It is mandatory to keep this value constant between restarts of the agent, and to make every possible effort to keep it constant across restarts (but note, it is unrealistic to expect it to remain constant across all re-configurations of the local system, e.g., across the replacement of all non- volatile storage).
.1.3.6.1.2.1.10.56.1.1.1.2,FC-MGMT-MIB::fcmInstanceWwn,OCTET,read-only,,current,,If the instance has one (or more) WWN(s), then this object contains that (or one of those) WWN(s). If the instance does not have a WWN associated with it, then this object contains the zero-length string.
.1.3.6.1.2.1.10.56.1.1.1.3,FC-MGMT-MIB::fcmInstanceFunctions,BITS,read-only,,current,other(0):hub(1):switch(2):bridge(3):gateway(4):host(5):storageSubsys(6):storageAccessDev(7):nas(8):wdmux(9):storageDevice(10),One (or more) Fibre Channel unit functions being performed by this instance.
.1.3.6.1.2.1.10.56.1.1.1.4,FC-MGMT-MIB::fcmInstancePhysicalIndex,Integer32,read-only,,current,,If this management instance corresponds to a physical component (or to a hierarchy of physical components) identified by the Entity-MIB, then this object's value is the value of the entPhysicalIndex of that component (or of the component at the root of that hierarchy). If there is no correspondence to a physical component (or no component that has an entPhysicalIndex value), then the value of this object is zero.
.1.3.6.1.2.1.10.56.1.1.1.5,FC-MGMT-MIB::fcmInstanceSoftwareIndex,Integer32,read-only,,current,,If this management instance corresponds to an installed software module identified in the Host Resources MIB, then this object's value is the value of the hrSWInstalledIndex of that module. If there is no correspondence to an installed software module (or no module that has a hrSWInstalledIndex value), then the value of this object is zero.
.1.3.6.1.2.1.10.56.1.1.1.6,FC-MGMT-MIB::fcmInstanceStatus,INTEGER,read-only,,current,unknown(1):ok(2):warning(3):failed(4),Overall status of the Fibre Channel entity/entities managed by this management instance. The value should reflect the most serious status of such entities.
.1.3.6.1.2.1.10.56.1.1.1.7,FC-MGMT-MIB::fcmInstanceTextName,OCTET,read-write,,current,,A textual name for this management instance and the Fibre Channel entity/entities that it is managing.
.1.3.6.1.2.1.10.56.1.1.1.8,FC-MGMT-MIB::fcmInstanceDescr,OCTET,read-write,,current,,A textual description of this management instance and the Fibre Channel entity/entities that it is managing.
.1.3.6.1.2.1.10.56.1.1.1.9,FC-MGMT-MIB::fcmInstanceFabricId,OCTET,read-only,,current,,The globally unique Fabric Identifier that identifies the fabric to which the Fibre Channel entity/entities managed by this management instance are connected, or, of which they are a part. This is typically the Node WWN of the principal switch of a Fibre Channel fabric. The zero-length string indicates that the fabric identifier is unknown (or not applicable). In the event that the Fibre Channel entity/entities managed by this management instance is/are connected to multiple fabrics, then this object records the first (known) one.
.1.3.6.1.2.1.10.56.1.2,FC-MGMT-MIB::fcmSwitchTable,,not-accessible,,current,,A table of information about Fibre Channel switches that are managed by Fibre Channel management instances. Each Fibre Channel management instance can manage one or more Fibre Channel switches.
.1.3.6.1.2.1.10.56.1.2.1,FC-MGMT-MIB::fcmSwitchEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex,current,,Information about a particular Fibre Channel switch that is managed by the management instance given by fcmInstanceIndex.
.1.3.6.1.2.1.10.56.1.2.1.1,FC-MGMT-MIB::fcmSwitchIndex,Unsigned32,not-accessible,,current,,An arbitrary integer that uniquely identifies a Fibre Channel switch amongst those managed by one Fibre Channel management instance. It is mandatory to keep this value constant between restarts of the agent, and to make every possible effort to keep it constant across restarts.
.1.3.6.1.2.1.10.56.1.2.1.2,FC-MGMT-MIB::fcmSwitchDomainId,Integer32,read-write,,current,,The Domain Id of this switch. A value of zero indicates that a switch has not (yet) been assigned a Domain Id.
.1.3.6.1.2.1.10.56.1.2.1.3,FC-MGMT-MIB::fcmSwitchPrincipal,INTEGER,read-only,,current,true(1):false(2),An indication of whether this switch is the principal switch within its fabric.
.1.3.6.1.2.1.10.56.1.2.1.4,FC-MGMT-MIB::fcmSwitchWWN,OCTET,read-only,,current,,The World Wide Name of this switch.
.1.3.6.1.2.1.10.56.1.3,FC-MGMT-MIB::fcmPortTable,,not-accessible,,current,,Information about Fibre Channel ports. Each Fibre Channel port is represented by one entry in the IF-MIB's ifTable.
.1.3.6.1.2.1.10.56.1.3.1,FC-MGMT-MIB::fcmPortEntry,,not-accessible,ifIndex,current,,Each entry contains information about a specific port.
.1.3.6.1.2.1.10.56.1.3.1.1,FC-MGMT-MIB::fcmPortInstanceIndex,Unsigned32,read-only,,current,,The value of fcmInstanceIndex by which the Fibre Channel management instance, which manages this port, is identified in the fcmInstanceTable.
.1.3.6.1.2.1.10.56.1.3.1.2,FC-MGMT-MIB::fcmPortWwn,OCTET,read-only,,current,,The World Wide Name of the port, or the zero-length string if the port does not have a WWN.
.1.3.6.1.2.1.10.56.1.3.1.3,FC-MGMT-MIB::fcmPortNodeWwn,OCTET,read-only,,current,,The World Wide Name of the Node that contains this port, or the zero-length string if the port does not have a node WWN.
.1.3.6.1.2.1.10.56.1.3.1.4,FC-MGMT-MIB::fcmPortAdminType,Unsigned32,read-write,,current,,The administratively desired type of this port.
.1.3.6.1.2.1.10.56.1.3.1.5,FC-MGMT-MIB::fcmPortOperType,Unsigned32,read-only,,current,,The current operational type of this port.
.1.3.6.1.2.1.10.56.1.3.1.6,FC-MGMT-MIB::fcmPortFcCapClass,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),The classes of service capability of this port.
.1.3.6.1.2.1.10.56.1.3.1.7,FC-MGMT-MIB::fcmPortFcOperClass,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),The classes of service that are currently operational on this port. For an FL_Port, this is the union of the classes being supported across all attached NL_Ports.
.1.3.6.1.2.1.10.56.1.3.1.8,FC-MGMT-MIB::fcmPortTransmitterType,INTEGER,read-only,,current,unknown(1):other(2):shortwave850nm(3):longwave1550nm(4):longwave1310nm(5):electrical(6),The technology of the port transceiver.
.1.3.6.1.2.1.10.56.1.3.1.9,FC-MGMT-MIB::fcmPortConnectorType,INTEGER,read-only,,current,unknown(1):other(2):gbic(3):embedded(4):glm(5):gbicSerialId(6):gbicNoSerialId(7):sfpSerialId(8):sfpNoSerialId(9),The module type of the port connector. This object refers to the hardware implementation of the port. It will be 'embedded' if the hardware equivalent to Gigabit interface card (GBIC) is part of the line card and is unremovable. It will be 'glm' if it's a gigabit link module (GLM). It will be 'gbicSerialId' if the GBIC serial id can be read, else it will be 'gbicNoSerialId'. It will be 'sfpSerialId' if the small form factor (SFP) pluggable GBICs serial id can be read, else it will be 'sfpNoSerialId'.
.1.3.6.1.2.1.10.56.1.3.1.10,FC-MGMT-MIB::fcmPortSerialNumber,OCTET,read-only,,current,,The serial number associated with the port (e.g., for a GBIC). If not applicable, the object's value is a zero- length string.
.1.3.6.1.2.1.10.56.1.3.1.11,FC-MGMT-MIB::fcmPortPhysicalNumber,Unsigned32,read-only,,current,,This is the port's 'Physical Port Number' as defined by GS-3.
.1.3.6.1.2.1.10.56.1.3.1.12,FC-MGMT-MIB::fcmPortAdminSpeed,INTEGER,read-write,,current,auto(1):eighthGbs(2):quarterGbs(3):halfGbs(4):oneGbs(5):twoGbs(6):fourGbs(7):tenGbs(8),The speed of the interface: 'auto' - auto-negotiation 'tenGbs' - 10Gbs 'fourGbs' - 4Gbs 'twoGbs' - 2Gbs 'oneGbs' - 1Gbs 'halfGbs' - 500Mbs 'quarterGbs' - 250Mbs 'eighthGbs' - 125Mbs
.1.3.6.1.2.1.10.56.1.3.1.13,FC-MGMT-MIB::fcmPortCapProtocols,BITS,read-only,,current,unknown(0):loop(1):fabric(2):scsi(3):tcpIp(4):vi(5):ficon(6),A bit mask specifying the higher level protocols that are capable of running over this port. Note that for generic Fx_Ports, E_Ports, and B_Ports, this object will indicate all protocols.
.1.3.6.1.2.1.10.56.1.3.1.14,FC-MGMT-MIB::fcmPortOperProtocols,BITS,read-only,,current,unknown(0):loop(1):fabric(2):scsi(3):tcpIp(4):vi(5):ficon(6),A bit mask specifying the higher level protocols that are currently operational on this port. For Fx_Ports, E_Ports, and B_Ports, this object will typically have the value 'unknown'.
.1.3.6.1.2.1.10.56.1.4,FC-MGMT-MIB::fcmPortStatsTable,,not-accessible,,current,,A list of statistics for Fibre Channel ports.
.1.3.6.1.2.1.10.56.1.4.1,FC-MGMT-MIB::fcmPortStatsEntry,,not-accessible,,current,,An entry containing statistics for a Fibre Channel port. If any counter in this table suffers a discontinuity, the value of ifCounterDiscontinuityTime (defined in the IF-MIB) must be updated.
.1.3.6.1.2.1.10.56.1.4.1.1,FC-MGMT-MIB::fcmPortBBCreditZeros,Counter64,read-only,,current,,The number of transitions in/out of the buffer-to-buffer credit zero state. The other side is not providing any credit.
.1.3.6.1.2.1.10.56.1.4.1.2,FC-MGMT-MIB::fcmPortFullInputBuffers,Counter64,read-only,,current,,The number of occurrences when all input buffers of a port were full and outbound buffer-to-buffer credit transitioned to zero, i.e., there became no credit to provide to other side.
.1.3.6.1.2.1.10.56.1.4.1.3,FC-MGMT-MIB::fcmPortClass2RxFrames,Counter64,read-only,,current,,The number of Class 2 frames received at this port.
.1.3.6.1.2.1.10.56.1.4.1.4,FC-MGMT-MIB::fcmPortClass2RxOctets,Counter64,read-only,,current,,The number of octets contained in Class 2 frames received at this port.
.1.3.6.1.2.1.10.56.1.4.1.5,FC-MGMT-MIB::fcmPortClass2TxFrames,Counter64,read-only,,current,,The number of Class 2 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.4.1.6,FC-MGMT-MIB::fcmPortClass2TxOctets,Counter64,read-only,,current,,The number of octets contained in Class 2 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.4.1.7,FC-MGMT-MIB::fcmPortClass2Discards,Counter64,read-only,,current,,The number of Class 2 frames that were discarded upon reception at this port.
.1.3.6.1.2.1.10.56.1.4.1.8,FC-MGMT-MIB::fcmPortClass2RxFbsyFrames,Counter64,read-only,,current,,The number of times that F_BSY was returned to this port as a result of a Class 2 frame that could not be delivered to the other end of the link. This can occur when either the fabric or the destination port is temporarily busy. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.4.1.9,FC-MGMT-MIB::fcmPortClass2RxPbsyFrames,Counter64,read-only,,current,,The number of times that P_BSY was returned to this port as a result of a Class 2 frame that could not be delivered to the other end of the link. This can occur when the destination port is temporarily busy.
.1.3.6.1.2.1.10.56.1.4.1.10,FC-MGMT-MIB::fcmPortClass2RxFrjtFrames,Counter64,read-only,,current,,The number of times that F_RJT was returned to this port as a result of a Class 2 frame that was rejected by the fabric. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.4.1.11,FC-MGMT-MIB::fcmPortClass2RxPrjtFrames,Counter64,read-only,,current,,The number of times that P_RJT was returned to this port as a result of a Class 2 frame that was rejected at the destination N_Port.
.1.3.6.1.2.1.10.56.1.4.1.12,FC-MGMT-MIB::fcmPortClass2TxFbsyFrames,Counter64,read-only,,current,,The number of times that F_BSY was generated by this port as a result of a Class 2 frame that could not be delivered because either the Fabric or the destination port was temporarily busy. Note that this counter will never increment for an N_Port.
.1.3.6.1.2.1.10.56.1.4.1.13,FC-MGMT-MIB::fcmPortClass2TxPbsyFrames,Counter64,read-only,,current,,The number of times that P_BSY was generated by this port as a result of a Class 2 frame that could not be delivered because the destination port was temporarily busy. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.4.1.14,FC-MGMT-MIB::fcmPortClass2TxFrjtFrames,Counter64,read-only,,current,,The number of times that F_RJT was generated by this port as a result of a Class 2 frame being rejected by the fabric. Note that this counter will never increment for an N_Port.
.1.3.6.1.2.1.10.56.1.4.1.15,FC-MGMT-MIB::fcmPortClass2TxPrjtFrames,Counter64,read-only,,current,,The number of times that P_RJT was generated by this port as a result of a Class 2 frame being rejected at the destination N_Port. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.4.1.16,FC-MGMT-MIB::fcmPortClass3RxFrames,Counter64,read-only,,current,,The number of Class 3 frames received at this port.
.1.3.6.1.2.1.10.56.1.4.1.17,FC-MGMT-MIB::fcmPortClass3RxOctets,Counter64,read-only,,current,,The number of octets contained in Class 3 frames received at this port.
.1.3.6.1.2.1.10.56.1.4.1.18,FC-MGMT-MIB::fcmPortClass3TxFrames,Counter64,read-only,,current,,The number of Class 3 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.4.1.19,FC-MGMT-MIB::fcmPortClass3TxOctets,Counter64,read-only,,current,,The number of octets contained in Class 3 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.4.1.20,FC-MGMT-MIB::fcmPortClass3Discards,Counter64,read-only,,current,,The number of Class 3 frames that were discarded upon reception at this port.
.1.3.6.1.2.1.10.56.1.4.1.21,FC-MGMT-MIB::fcmPortClassFRxFrames,Counter32,read-only,,current,,The number of Class F frames received at this port.
.1.3.6.1.2.1.10.56.1.4.1.22,FC-MGMT-MIB::fcmPortClassFRxOctets,Counter32,read-only,,current,,The number of octets contained in Class F frames received at this port.
.1.3.6.1.2.1.10.56.1.4.1.23,FC-MGMT-MIB::fcmPortClassFTxFrames,Counter32,read-only,,current,,The number of Class F frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.4.1.24,FC-MGMT-MIB::fcmPortClassFTxOctets,Counter32,read-only,,current,,The number of octets contained in Class F frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.4.1.25,FC-MGMT-MIB::fcmPortClassFDiscards,Counter32,read-only,,current,,The number of Class F frames that were discarded upon reception at this port.
.1.3.6.1.2.1.10.56.1.5,FC-MGMT-MIB::fcmPortLcStatsTable,,not-accessible,,current,,A list of Counter32-based statistics for systems that do not support Counter64.
.1.3.6.1.2.1.10.56.1.5.1,FC-MGMT-MIB::fcmPortLcStatsEntry,,not-accessible,,current,,An entry containing low-capacity (i.e., based on Counter32) statistics for a Fibre Channel port. If any counter in this table suffers a discontinuity, the value of ifCounterDiscontinuityTime (defined in the IF-MIB) must be updated.
.1.3.6.1.2.1.10.56.1.5.1.1,FC-MGMT-MIB::fcmPortLcBBCreditZeros,Counter32,read-only,,current,,The number of transitions in/out of the buffer-to-buffer credit zero state. The other side is not providing any credit.
.1.3.6.1.2.1.10.56.1.5.1.2,FC-MGMT-MIB::fcmPortLcFullInputBuffers,Counter32,read-only,,current,,The number of occurrences when all input buffers of a port were full and outbound buffer-to-buffer credit transitioned to zero, i.e., there became no credit to provide to other side.
.1.3.6.1.2.1.10.56.1.5.1.3,FC-MGMT-MIB::fcmPortLcClass2RxFrames,Counter32,read-only,,current,,The number of Class 2 frames received at this port.
.1.3.6.1.2.1.10.56.1.5.1.4,FC-MGMT-MIB::fcmPortLcClass2RxOctets,Counter32,read-only,,current,,The number of octets contained in Class 2 frames received at this port.
.1.3.6.1.2.1.10.56.1.5.1.5,FC-MGMT-MIB::fcmPortLcClass2TxFrames,Counter32,read-only,,current,,The number of Class 2 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.5.1.6,FC-MGMT-MIB::fcmPortLcClass2TxOctets,Counter32,read-only,,current,,The number of octets contained in Class 2 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.5.1.7,FC-MGMT-MIB::fcmPortLcClass2Discards,Counter32,read-only,,current,,The number of Class 2 frames that were discarded upon reception at this port.
.1.3.6.1.2.1.10.56.1.5.1.8,FC-MGMT-MIB::fcmPortLcClass2RxFbsyFrames,Counter32,read-only,,current,,The number of times that F_BSY was returned to this port as a result of a Class 2 frame that could not be delivered to the other end of the link. This can occur when either the fabric or the destination port is temporarily busy. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.5.1.9,FC-MGMT-MIB::fcmPortLcClass2RxPbsyFrames,Counter32,read-only,,current,,The number of times that P_BSY was returned to this port as a result of a Class 2 frame that could not be delivered to the other end of the link. This can occur when the destination port is temporarily busy.
.1.3.6.1.2.1.10.56.1.5.1.10,FC-MGMT-MIB::fcmPortLcClass2RxFrjtFrames,Counter32,read-only,,current,,The number of times that F_RJT was returned to this port as a result of a Class 2 frame that was rejected by the fabric. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.5.1.11,FC-MGMT-MIB::fcmPortLcClass2RxPrjtFrames,Counter32,read-only,,current,,The number of times that P_RJT was returned to this port as a result of a Class 2 frame that was rejected at the destination N_Port.
.1.3.6.1.2.1.10.56.1.5.1.12,FC-MGMT-MIB::fcmPortLcClass2TxFbsyFrames,Counter32,read-only,,current,,The number of times that F_BSY was generated by this port as a result of a Class 2 frame that could not be delivered because either the Fabric or the destination port was temporarily busy. Note that this counter will never increment for an N_Port.
.1.3.6.1.2.1.10.56.1.5.1.13,FC-MGMT-MIB::fcmPortLcClass2TxPbsyFrames,Counter32,read-only,,current,,The number of times that P_BSY was generated by this port as a result of a Class 2 frame that could not be delivered because the destination port was temporarily busy. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.5.1.14,FC-MGMT-MIB::fcmPortLcClass2TxFrjtFrames,Counter32,read-only,,current,,The number of times that F_RJT was generated by this port as a result of a Class 2 frame being rejected by the fabric. Note that this counter will never increment for an N_Port.
.1.3.6.1.2.1.10.56.1.5.1.15,FC-MGMT-MIB::fcmPortLcClass2TxPrjtFrames,Counter32,read-only,,current,,The number of times that P_RJT was generated by this port as a result of a Class 2 frame being rejected at the destination N_Port. Note that this counter will never increment for an F_Port.
.1.3.6.1.2.1.10.56.1.5.1.16,FC-MGMT-MIB::fcmPortLcClass3RxFrames,Counter32,read-only,,current,,The number of Class 3 frames received at this port.
.1.3.6.1.2.1.10.56.1.5.1.17,FC-MGMT-MIB::fcmPortLcClass3RxOctets,Counter32,read-only,,current,,The number of octets contained in Class 3 frames received at this port.
.1.3.6.1.2.1.10.56.1.5.1.18,FC-MGMT-MIB::fcmPortLcClass3TxFrames,Counter32,read-only,,current,,The number of Class 3 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.5.1.19,FC-MGMT-MIB::fcmPortLcClass3TxOctets,Counter32,read-only,,current,,The number of octets contained in Class 3 frames transmitted out of this port.
.1.3.6.1.2.1.10.56.1.5.1.20,FC-MGMT-MIB::fcmPortLcClass3Discards,Counter32,read-only,,current,,The number of Class 3 frames that were discarded upon reception at this port.
.1.3.6.1.2.1.10.56.1.6,FC-MGMT-MIB::fcmPortErrorsTable,,not-accessible,,current,,Error counters for Fibre Channel ports.
.1.3.6.1.2.1.10.56.1.6.1,FC-MGMT-MIB::fcmPortErrorsEntry,,not-accessible,,current,,Error counters for a Fibre Channel port. If any counter in this table suffers a discontinuity, the value of ifCounterDiscontinuityTime (defined in the IF-MIB) must be updated.
.1.3.6.1.2.1.10.56.1.6.1.1,FC-MGMT-MIB::fcmPortRxLinkResets,Counter32,read-only,,current,,The number of Link Reset (LR) Primitive Sequences received.
.1.3.6.1.2.1.10.56.1.6.1.2,FC-MGMT-MIB::fcmPortTxLinkResets,Counter32,read-only,,current,,The number of Link Reset (LR) Primitive Sequences transmitted.
.1.3.6.1.2.1.10.56.1.6.1.3,FC-MGMT-MIB::fcmPortLinkResets,Counter32,read-only,,current,,The number of times the reset link protocol was initiated on this port. This includes the number of Loop Initialization Primitive (LIP) events on an arbitrated loop port.
.1.3.6.1.2.1.10.56.1.6.1.4,FC-MGMT-MIB::fcmPortRxOfflineSequences,Counter32,read-only,,current,,The number of Offline (OLS) Primitive Sequences received at this port.
.1.3.6.1.2.1.10.56.1.6.1.5,FC-MGMT-MIB::fcmPortTxOfflineSequences,Counter32,read-only,,current,,The number of Offline (OLS) Primitive Sequences transmitted by this port.
.1.3.6.1.2.1.10.56.1.6.1.6,FC-MGMT-MIB::fcmPortLinkFailures,Counter32,read-only,,current,,The number of link failures. This count is part of FC-PH's Link Error Status Block (LESB).
.1.3.6.1.2.1.10.56.1.6.1.7,FC-MGMT-MIB::fcmPortLossofSynchs,Counter32,read-only,,current,,The number of instances of synchronization loss detected at this port. This count is part of FC-PH's Link Error Status Block (LESB).
.1.3.6.1.2.1.10.56.1.6.1.8,FC-MGMT-MIB::fcmPortLossofSignals,Counter32,read-only,,current,,The number of instances of signal loss detected at this port. This count is part of FC-PH's Link Error Status Block (LESB).
.1.3.6.1.2.1.10.56.1.6.1.9,FC-MGMT-MIB::fcmPortPrimSeqProtocolErrors,Counter32,read-only,,current,,The number of primitive sequence protocol errors detected at this port. This count is part of FC-PH's Link Error Status Block (LESB).
.1.3.6.1.2.1.10.56.1.6.1.10,FC-MGMT-MIB::fcmPortInvalidTxWords,Counter32,read-only,,current,,The number of invalid transmission words received at this port. This count is part of FC-PH's Link Error Status Block (LESB).
.1.3.6.1.2.1.10.56.1.6.1.11,FC-MGMT-MIB::fcmPortInvalidCRCs,Counter32,read-only,,current,,The number of frames received with an invalid CRC. This count is part of FC-PH's Link Error Status Block (LESB).
.1.3.6.1.2.1.10.56.1.6.1.12,FC-MGMT-MIB::fcmPortInvalidOrderedSets,Counter32,read-only,,current,,The number of invalid ordered sets received at this port.
.1.3.6.1.2.1.10.56.1.6.1.13,FC-MGMT-MIB::fcmPortFrameTooLongs,Counter32,read-only,,current,,The number of frames received at this port for which the frame length was greater than what was agreed to in FLOGI/PLOGI. This could be caused by losing the end of frame delimiter.
.1.3.6.1.2.1.10.56.1.6.1.14,FC-MGMT-MIB::fcmPortTruncatedFrames,Counter32,read-only,,current,,The number of frames received at this port for which the frame length was less than the minimum indicated by the frame header - normally 24 bytes, but it could be more if the DFCTL field indicates an optional header should have been present.
.1.3.6.1.2.1.10.56.1.6.1.15,FC-MGMT-MIB::fcmPortAddressErrors,Counter32,read-only,,current,,The number of frames received with unknown addressing; for example, an unknown SID or DID.
.1.3.6.1.2.1.10.56.1.6.1.16,FC-MGMT-MIB::fcmPortDelimiterErrors,Counter32,read-only,,current,,The number of invalid frame delimiters received at this port. An example is a frame with a class 2 start and a class 3 at the end.
.1.3.6.1.2.1.10.56.1.6.1.17,FC-MGMT-MIB::fcmPortEncodingDisparityErrors,Counter32,read-only,,current,,The number of encoding disparity errors received at this port.
.1.3.6.1.2.1.10.56.1.6.1.18,FC-MGMT-MIB::fcmPortOtherErrors,Counter32,read-only,,current,,The number of errors that were detected on this port but not counted by any other error counter in this row.
.1.3.6.1.2.1.10.56.1.7,FC-MGMT-MIB::fcmFxPortTable,,not-accessible,,current,,Additional information about Fibre Channel ports that is specific to Fx_Ports. This table will contain one entry for each fcmPortTable entry that represents an Fx_Port.
.1.3.6.1.2.1.10.56.1.7.1,FC-MGMT-MIB::fcmFxPortEntry,,not-accessible,ifIndex,current,,Each entry contains information about a specific Fx_Port.
.1.3.6.1.2.1.10.56.1.7.1.1,FC-MGMT-MIB::fcmFxPortRatov,Unsigned32,read-only,,current,,The Resource_Allocation_Timeout Value configured for this Fx_Port. This is used as the timeout value for determining when to reuse an Nx_Port resource such as a Recovery_Qualifier. It represents the Error_Detect_Timeout value (see fcmFxPortEdtov) plus twice the maximum time that a frame may be delayed within the Fabric and still be delivered.
.1.3.6.1.2.1.10.56.1.7.1.2,FC-MGMT-MIB::fcmFxPortEdtov,Unsigned32,read-only,,current,,The Error_Detect_Timeout value configured for this Fx_Port. This is used as the timeout value for detecting an error condition.
.1.3.6.1.2.1.10.56.1.7.1.3,FC-MGMT-MIB::fcmFxPortRttov,Unsigned32,read-only,,current,,The Receiver_Transmitter_Timeout value of this Fx_Port. This is used by the receiver logic to detect a Loss of Synchronization.
.1.3.6.1.2.1.10.56.1.7.1.4,FC-MGMT-MIB::fcmFxPortHoldTime,Unsigned32,read-only,,current,,The maximum time that this Fx_Port shall hold a frame before discarding the frame if it is unable to deliver the frame. The value 0 means that this Fx_Port does not support this parameter.
.1.3.6.1.2.1.10.56.1.7.1.5,FC-MGMT-MIB::fcmFxPortCapBbCreditMax,Integer32,read-only,,current,,The maximum number of receive buffers that this port is capable of making available for holding frames from attached Nx_Port(s).
.1.3.6.1.2.1.10.56.1.7.1.6,FC-MGMT-MIB::fcmFxPortCapBbCreditMin,Integer32,read-only,,current,,The minimum number of receive buffers that this port is capable of making available for holding frames from attached Nx_Port(s).
.1.3.6.1.2.1.10.56.1.7.1.7,FC-MGMT-MIB::fcmFxPortCapDataFieldSizeMax,Integer32,read-only,,current,,The maximum size in bytes of the Data Field in a frame that this Fx_Port is capable of receiving from an attached Nx_Port.
.1.3.6.1.2.1.10.56.1.7.1.8,FC-MGMT-MIB::fcmFxPortCapDataFieldSizeMin,Integer32,read-only,,current,,The minimum size in bytes of the Data Field in a frame that this Fx_Port is capable of receiving from an attached Nx_Port.
.1.3.6.1.2.1.10.56.1.7.1.9,FC-MGMT-MIB::fcmFxPortCapClass2SeqDeliv,INTEGER,read-only,,current,true(1):false(2),An indication of whether this Fx_Port is capable of supporting Class 2 Sequential Delivery.
.1.3.6.1.2.1.10.56.1.7.1.10,FC-MGMT-MIB::fcmFxPortCapClass3SeqDeliv,INTEGER,read-only,,current,true(1):false(2),An indication of whether this Fx_Port is capable of supporting Class 3 Sequential Delivery.
.1.3.6.1.2.1.10.56.1.7.1.11,FC-MGMT-MIB::fcmFxPortCapHoldTimeMax,Unsigned32,read-only,,current,,The maximum holding time that this Fx_Port is capable of supporting.
.1.3.6.1.2.1.10.56.1.7.1.12,FC-MGMT-MIB::fcmFxPortCapHoldTimeMin,Unsigned32,read-only,,current,,The minimum holding time that this Fx_Port is capable of supporting.
.1.3.6.1.2.1.10.56.1.8,FC-MGMT-MIB::fcmISPortTable,,not-accessible,,current,,Additional information about E_Ports, B_Ports, and any other type of Fibre Channel port to which inter-switch links can be connected. This table will contain one entry for each fcmPortTable entry that represents such a port.
.1.3.6.1.2.1.10.56.1.8.1,FC-MGMT-MIB::fcmISPortEntry,,not-accessible,ifIndex,current,,Each entry contains information about a specific port connected to an inter-switch link.
.1.3.6.1.2.1.10.56.1.8.1.1,FC-MGMT-MIB::fcmISPortClassFCredit,Integer32,read-write,,current,,The maximum number of Class F data frames that can be transmitted by the inter-switch port without receipt of ACK or Link_Response frames.
.1.3.6.1.2.1.10.56.1.8.1.2,FC-MGMT-MIB::fcmISPortClassFDataFieldSize,Integer32,read-only,,current,,The Receive Data Field Size that the inter-switch port has agreed to support for Class F frames to/from this port. The size specifies the largest Data Field Size for an FT_1 frame.
.1.3.6.1.2.1.10.56.1.9,FC-MGMT-MIB::fcmFLoginTable,,not-accessible,,current,,A table that contains one entry for each Nx_Port logged- in/attached to a particular Fx_Port in the switch. Each entry contains the services parameters established during the most recent Fabric Login, explicit or implicit. Note that an Fx_Port may have one or more Nx_Ports attached to it.
.1.3.6.1.2.1.10.56.1.9.1,FC-MGMT-MIB::fcmFLoginEntry,,not-accessible,ifIndex:fcmFLoginNxPortIndex,current,,An entry containing service parameters established from a successful Fabric Login.
.1.3.6.1.2.1.10.56.1.9.1.1,FC-MGMT-MIB::fcmFLoginNxPortIndex,Unsigned32,not-accessible,,current,,An arbitrary integer that uniquely identifies an Nx_Port amongst all those attached to the Fx_Port indicated by ifIndex. After a value of this object is assigned to a particular Nx_Port, that value can be re-used when and only when it is assigned to the same Nx_Port, or, after a reset of the value of the relevant instance of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.10.56.1.9.1.2,FC-MGMT-MIB::fcmFLoginPortWwn,OCTET,read-only,,current,,The port name of the attached Nx_Port, or the zero-length string if unknown.
.1.3.6.1.2.1.10.56.1.9.1.3,FC-MGMT-MIB::fcmFLoginNodeWwn,OCTET,read-only,,current,,The node name of the attached Nx_Port, or the zero-length string if unknown.
.1.3.6.1.2.1.10.56.1.9.1.4,FC-MGMT-MIB::fcmFLoginBbCreditModel,INTEGER,read-only,,current,regular(1):alternate(2),The buffer-to-buffer credit model in use by the Fx_Port.
.1.3.6.1.2.1.10.56.1.9.1.5,FC-MGMT-MIB::fcmFLoginBbCredit,Integer32,read-only,,current,,The number of buffers available for holding frames to be transmitted to the attached Nx_Port. These buffers are for buffer-to-buffer flow control in the direction from Fx_Port to Nx_Port.
.1.3.6.1.2.1.10.56.1.9.1.6,FC-MGMT-MIB::fcmFLoginClassesAgreed,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),The Classes of Service that the Fx_Port has agreed to support for this Nx_Port.
.1.3.6.1.2.1.10.56.1.9.1.7,FC-MGMT-MIB::fcmFLoginClass2SeqDelivAgreed,INTEGER,read-only,,current,true(1):false(2),An indication of whether the Fx_Port has agreed to support Class 2 sequential delivery for this Nx_Port. This is only meaningful if Class 2 service has been agreed upon.
.1.3.6.1.2.1.10.56.1.9.1.8,FC-MGMT-MIB::fcmFLoginClass2DataFieldSize,Integer32,read-only,,current,,The Receive Data Field Size that the Fx_Port has agreed to support for Class 2 frames to/from this Nx_Port. The size specifies the largest Data Field Size for an FT_1 frame. This is only meaningful if Class 2 service has been agreed upon.
.1.3.6.1.2.1.10.56.1.9.1.9,FC-MGMT-MIB::fcmFLoginClass3SeqDelivAgreed,INTEGER,read-only,,current,true(1):false(2),An indication of whether the Fx_Port has agreed to support Class 3 sequential delivery for this Nx_Port. This is only meaningful if Class 3 service has been agreed upon.
.1.3.6.1.2.1.10.56.1.9.1.10,FC-MGMT-MIB::fcmFLoginClass3DataFieldSize,Integer32,read-only,,current,,The Receive Data Field Size that the Fx_Port has agreed to support for Class 3 frames to/from this Nx_Port. The size specifies the largest Data Field Size for an FT_1 frame. This is only meaningful if Class 3 service has been agreed upon.
.1.3.6.1.2.1.10.56.1.10,FC-MGMT-MIB::fcmLinkTable,,not-accessible,,current,,A table containing any Fibre Channel link information that is known to local Fibre Channel managed instances. One end of such a link is typically at a local port, but the table can also contain information on links for which neither end is a local port. If one end of a link terminates locally, then that end is termed 'end1'; the other end is termed 'end2'.
.1.3.6.1.2.1.10.56.1.10.1,FC-MGMT-MIB::fcmLinkEntry,,not-accessible,fcmInstanceIndex:fcmLinkIndex,current,,An entry containing information that a particular Fibre Channel managed instance has about a Fibre Channel link. The two ends of the link are called 'end1' and 'end2'.
.1.3.6.1.2.1.10.56.1.10.1.1,FC-MGMT-MIB::fcmLinkIndex,Unsigned32,not-accessible,,current,,An arbitrary integer that uniquely identifies one link within the set of links about which a particular managed instance has information.
.1.3.6.1.2.1.10.56.1.10.1.2,FC-MGMT-MIB::fcmLinkEnd1NodeWwn,OCTET,read-only,,current,,The node name of end1, or the zero-length string if unknown.
.1.3.6.1.2.1.10.56.1.10.1.3,FC-MGMT-MIB::fcmLinkEnd1PhysPortNumber,Unsigned32,read-only,,current,,The physical port number of end1, or zero if unknown.
.1.3.6.1.2.1.10.56.1.10.1.4,FC-MGMT-MIB::fcmLinkEnd1PortWwn,OCTET,read-only,,current,,The port WWN of end1, or the zero-length string if unknown. ('end1' is local if this value is equal to the value of fcmPortWwn in one of the rows of the fcmPortTable.)
.1.3.6.1.2.1.10.56.1.10.1.5,FC-MGMT-MIB::fcmLinkEnd2NodeWwn,OCTET,read-only,,current,,The node name of end2, or the zero-length string if unknown.
.1.3.6.1.2.1.10.56.1.10.1.6,FC-MGMT-MIB::fcmLinkEnd2PhysPortNumber,Unsigned32,read-only,,current,,The physical port number of end2, or zero if unknown.
.1.3.6.1.2.1.10.56.1.10.1.7,FC-MGMT-MIB::fcmLinkEnd2PortWwn,OCTET,read-only,,current,,The port WWN of end2, or the zero-length string if unknown.
.1.3.6.1.2.1.10.56.1.10.1.8,FC-MGMT-MIB::fcmLinkEnd2AgentAddress,OCTET,read-only,,current,,The address of the management agent for the Fibre Channel Interconnect Element or Platform of which end2 is a part. The GS-4 specification provides some information about management agents. If the address is unknown, the value of this object is the zero-length string.
.1.3.6.1.2.1.10.56.1.10.1.9,FC-MGMT-MIB::fcmLinkEnd2PortType,Unsigned32,read-only,,current,,The port type of end2.
.1.3.6.1.2.1.10.56.1.10.1.10,FC-MGMT-MIB::fcmLinkEnd2UnitType,BITS,read-only,,current,other(0):hub(1):switch(2):bridge(3):gateway(4):host(5):storageSubsys(6):storageAccessDev(7):nas(8):wdmux(9):storageDevice(10),The type of/function(s) performed by the Fibre Channel Interconnect Element or Platform of which end2 is a part.
.1.3.6.1.2.1.10.56.1.10.1.11,FC-MGMT-MIB::fcmLinkEnd2FcAddressId,OCTET,read-only,,current,,The Fibre Channel Address ID of end2, or the zero-length string if unknown.
.1.3.6.1.2.1.10.56.2,FC-MGMT-MIB::fcmgmtNotifications,,,,,,
.1.3.6.1.2.1.10.56.2.0,FC-MGMT-MIB::fcmgmtNotifPrefix,,,,,,
.1.3.6.1.2.1.10.56.3,FC-MGMT-MIB::fcmgmtConformance,,,,,,
.1.3.6.1.2.1.10.56.3.1,FC-MGMT-MIB::fcmgmtCompliances,,,,,,
.1.3.6.1.2.1.10.56.3.1.1,FC-MGMT-MIB::fcmgmtCompliance,,,,,,Describes the requirements for compliance to this Fibre Channel Management MIB.
.1.3.6.1.2.1.10.56.3.2,FC-MGMT-MIB::fcmgmtGroups,,,,,,
.1.3.6.1.2.1.10.56.3.2.1,FC-MGMT-MIB::fcmInstanceBasicGroup,,,,,,Basic information about Fibre Channel managed instances.
.1.3.6.1.2.1.10.56.3.2.2,FC-MGMT-MIB::fcmSwitchBasicGroup,,,,,,Basic information about Fibre Channel switches.
.1.3.6.1.2.1.10.56.3.2.3,FC-MGMT-MIB::fcmPortBasicGroup,,,,,,Basic information about Fibre Channel ports.
.1.3.6.1.2.1.10.56.3.2.4,FC-MGMT-MIB::fcmPortStatsGroup,,,,,,Traffic statistics, which are not specific to any one class of service, for Fibre Channel ports.
.1.3.6.1.2.1.10.56.3.2.5,FC-MGMT-MIB::fcmPortClass23StatsGroup,,,,,,Traffic statistics for Class 2 and Class 3 traffic on Fibre Channel ports.
.1.3.6.1.2.1.10.56.3.2.6,FC-MGMT-MIB::fcmPortClassFStatsGroup,,,,,,Traffic statistics for Class F traffic on Fibre Channel ports.
.1.3.6.1.2.1.10.56.3.2.7,FC-MGMT-MIB::fcmPortLcStatsGroup,,,,,,Low-capacity (32-bit) statistics for Fibre Channel ports.
.1.3.6.1.2.1.10.56.3.2.8,FC-MGMT-MIB::fcmPortErrorsGroup,,,,,,Error statistics for Fibre Channel ports.
.1.3.6.1.2.1.10.56.3.2.9,FC-MGMT-MIB::fcmSwitchPortGroup,,,,,,Information about ports on a Fibre Channel switch.
.1.3.6.1.2.1.10.56.3.2.10,FC-MGMT-MIB::fcmSwitchLoginGroup,,,,,,Information known to a Fibre Channel switch about attached/logged-in Nx_Ports.
.1.3.6.1.2.1.10.56.3.2.11,FC-MGMT-MIB::fcmLinkBasicGroup,,,,,,Information about Fibre Channel links.
.1.3.6.1.2.1.10.81,DS0-MIB::ds0,,,,,,The MIB module to describe DS0 interfaces objects.
.1.3.6.1.2.1.10.81.1,DS0-MIB::dsx0ConfigTable,,not-accessible,,current,,The DS0 Configuration table.
.1.3.6.1.2.1.10.81.1.1,DS0-MIB::dsx0ConfigEntry,,not-accessible,ifIndex,current,,An entry in the DS0 Configuration table. There is an entry in this table for each DS0 interface.
.1.3.6.1.2.1.10.81.1.1.1,DS0-MIB::dsx0Ds0ChannelNumber,INTEGER,read-only,,current,,This object indicates the channel number of the ds0 on its DS1/E1.
.1.3.6.1.2.1.10.81.1.1.2,DS0-MIB::dsx0RobbedBitSignalling,INTEGER,read-write,,current,true(1):false(2),This object indicates if Robbed Bit Signalling is turned on or off for a given ds0. This only applies to DS0s on a DS1 link. For E1 links the value is always off (false).
.1.3.6.1.2.1.10.81.1.1.3,DS0-MIB::dsx0CircuitIdentifier,OCTET,read-write,,current,,This object contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting.
.1.3.6.1.2.1.10.81.1.1.4,DS0-MIB::dsx0IdleCode,INTEGER,read-write,,current,,This object contains the code transmitted in the ABCD bits when the ds0 is not connected and dsx0TransmitCodesEnable is enabled. The object is a bitmap and the various bit positions are: 1 D bit 2 C bit 4 B bit 8 A bit
.1.3.6.1.2.1.10.81.1.1.5,DS0-MIB::dsx0SeizedCode,INTEGER,read-write,,current,,This object contains the code transmitted in the ABCD bits when the ds0 is connected and dsx0TransmitCodesEnable is enabled. The object is a bitmap and the various bit positions are: 1 D bit 2 C bit 4 B bit 8 A bit
.1.3.6.1.2.1.10.81.1.1.6,DS0-MIB::dsx0ReceivedCode,INTEGER,read-only,,current,,This object contains the code being received in the ABCD bits. The object is a bitmap and the various bit positions are: 1 D bit 2 C bit 4 B bit 8 A bit
.1.3.6.1.2.1.10.81.1.1.7,DS0-MIB::dsx0TransmitCodesEnable,INTEGER,read-write,,current,true(1):false(2),This object determines if the idle and seized codes are transmitted. If the value of this object is true then the codes are transmitted.
.1.3.6.1.2.1.10.81.1.1.8,DS0-MIB::dsx0Ds0BundleMappedIfIndex,Integer32,read-only,,current,,This object indicates the ifIndex value assigned by the agent for the ds0Bundle(82) ifEntry to which the given ds0(81) ifEntry may belong. If the given ds0(81) ifEntry does not belong to any ds0Bundle(82) ifEntry, then this object has a value of zero. While this object provides information that can also be found in the ifStackTable, it provides this same information with a single table lookup, rather than by walking the ifStackTable to find the possibly non-existent ds0Bundle(82) ifEntry that may be stacked above the given ds0(81) ifTable entry.
.1.3.6.1.2.1.10.81.2,DS0-MIB::ds0Conformance,,,,,,
.1.3.6.1.2.1.10.81.2.1,DS0-MIB::ds0Groups,,,,,,
.1.3.6.1.2.1.10.81.2.1.1,DS0-MIB::ds0ConfigGroup,,,,,,A collection of objects providing configuration information applicable to all DS0 interfaces.
.1.3.6.1.2.1.10.81.2.2,DS0-MIB::ds0Compliances,,,,,,
.1.3.6.1.2.1.10.81.2.2.1,DS0-MIB::ds0Compliance,,,,,,The compliance statement for DS0 interfaces.
.1.3.6.1.2.1.10.81.3,DS0-MIB::dsx0ChanMappingTable,,not-accessible,,current,,The DS0 Channel Mapping table. This table maps a DS0 channel number on a particular DS1/E1 into an ifIndex.
.1.3.6.1.2.1.10.81.3.1,DS0-MIB::dsx0ChanMappingEntry,,not-accessible,ifIndex:dsx0Ds0ChannelNumber,current,,An entry in the DS0 Channel Mapping table. There is an entry in this table corresponding to each ds0 ifEntry within any interface that is channelized to the individual ds0 ifEntry level. This table is intended to facilitate mapping from channelized interface / channel number to DS0 ifEntry. (e.g. mapping (DS1 ifIndex, DS0 Channel Number) -> ifIndex) While this table provides information that can also be found in the ifStackTable and dsx0ConfigTable, it provides this same information with a single table lookup, rather than by walking the ifStackTable to find the various constituent ds0 ifTable entries, and testing various dsx0ConfigTable entries to check for the entry with the applicable DS0 channel number.
.1.3.6.1.2.1.10.81.3.1.1,DS0-MIB::dsx0ChanMappedIfIndex,Integer32,read-only,,current,,This object indicates the ifIndex value assigned by the agent for the individual ds0 ifEntry that corresponds to the given DS0 channel number (specified by the INDEX element dsx0Ds0ChannelNumber) of the given channelized interface (specified by INDEX element ifIndex).
.1.3.6.1.2.1.10.82,DS0BUNDLE-MIB::ds0Bundle,,,,,,The MIB module to describe DS0 Bundle interfaces objects.
.1.3.6.1.2.1.10.82.1,DS0BUNDLE-MIB::dsx0BondingTable,,not-accessible,,current,,The DS0 Bonding table.
.1.3.6.1.2.1.10.82.1.1,DS0BUNDLE-MIB::dsx0BondingEntry,,not-accessible,ifIndex,current,,An entry in the DS0 Bonding table. There is a row in this table for each DS0Bundle interface.
.1.3.6.1.2.1.10.82.1.1.1,DS0BUNDLE-MIB::dsx0BondMode,INTEGER,read-create,,current,none(1):other(2):mode0(3):mode1(4):mode2(5):mode3(6),This object indicates which BONDing mode is used, if any, for a ds0Bundle. Mode0 provides parameter and number exchange with no synchronization. Mode 1 provides parameter and number exchange. Mode 1 also provides synchronization during initialization but does not include inband monitoring. Mode 2 provides all of the above plus inband monitoring. Mode 2 also steals 1/64th of the bandwidth of each channel (thus not supporting n x 56/64 kbit/s data channels for most values of n). Mode 3 provides all of the above, but also provides n x 56/64 kbit/s data channels. Most common implementations of Mode 3 add an extra channel to support the inband monitoring overhead. ModeNone should be used when the interface is not performing bandwidth-on-demand.
.1.3.6.1.2.1.10.82.1.1.2,DS0BUNDLE-MIB::dsx0BondStatus,INTEGER,read-only,,current,idle(1):callSetup(2):dataTransfer(3),This object indicates the current status of the bonding call using this ds0Bundle. idle(1) should be used when the bonding mode is set to none(1).
.1.3.6.1.2.1.10.82.1.1.3,DS0BUNDLE-MIB::dsx0BondRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create new rows in this table, modify existing rows, and to delete existing rows.
.1.3.6.1.2.1.10.82.2,DS0BUNDLE-MIB::dsx0BundleNextIndex,INTEGER,read-write,,current,,This object is used to assist the manager in selecting a value for dsx0BundleIndex. Because this object is of syntax TestAndIncr (see the SNMPv2-TC document, RFC 1903) it can also be used to avoid race conditions with multiple managers trying to create rows in the table. If the result of the SET for dsx0BundleNextIndex is not success, this means the value has been changed from index (i.e. another manager used the value), so a new value is required. The algorithm is: done = false while done == false index = GET (dsx0BundleNextIndex.0) SET (dsx0BundleNextIndex.0=index) if (set failed) done = false else SET(dsx0BundleRowStatus.index=createAndGo) if (set failed) done = false else done = true other error handling
.1.3.6.1.2.1.10.82.3,DS0BUNDLE-MIB::dsx0BundleTable,,not-accessible,,current,,There is an row in this table for each ds0Bundle in the system. This table can be used to (indirectly) create rows in the ifTable with ifType = 'ds0Bundle(82)'.
.1.3.6.1.2.1.10.82.3.1,DS0BUNDLE-MIB::dsx0BundleEntry,,not-accessible,dsx0BundleIndex,current,,There is a row in entry in this table for each ds0Bundle interface.
.1.3.6.1.2.1.10.82.3.1.1,DS0BUNDLE-MIB::dsx0BundleIndex,INTEGER,not-accessible,,current,,A unique identifier for a ds0Bundle. This is not the same value as ifIndex. This table is not indexed by ifIndex because the manager has to choose the index in a createable row and the agent must be allowed to select ifIndex values.
.1.3.6.1.2.1.10.82.3.1.2,DS0BUNDLE-MIB::dsx0BundleIfIndex,Integer32,read-only,,current,,The ifIndex value the agent selected for the (new) ds0Bundle interface.
.1.3.6.1.2.1.10.82.3.1.3,DS0BUNDLE-MIB::dsx0BundleCircuitIdentifier,OCTET,read-create,,current,,This variable contains the transmission vendor's circuit identifier, for the purpose of facilitating troubleshooting.
.1.3.6.1.2.1.10.82.3.1.4,DS0BUNDLE-MIB::dsx0BundleRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in this table.
.1.3.6.1.2.1.10.82.4,DS0BUNDLE-MIB::ds0BundleConformance,,,,,,
.1.3.6.1.2.1.10.82.4.1,DS0BUNDLE-MIB::ds0BundleGroups,,,,,,
.1.3.6.1.2.1.10.82.4.1.1,DS0BUNDLE-MIB::ds0BondingGroup,,,,,,A collection of objects providing configuration information applicable to all DS0 interfaces.
.1.3.6.1.2.1.10.82.4.1.2,DS0BUNDLE-MIB::ds0BundleConfigGroup,,,,,,A collection of objects providing the ability to create a new ds0Bundle in the ifTable as well as configuration information about the ds0Bundle.
.1.3.6.1.2.1.10.82.4.2,DS0BUNDLE-MIB::ds0BundleCompliances,,,,,,
.1.3.6.1.2.1.10.82.4.2.1,DS0BUNDLE-MIB::ds0BundleCompliance,,,,,,The compliance statement for DS0Bundle interfaces.
.1.3.6.1.2.1.10.94,ADSL-LINE-MIB::adslMIB,,,,,,The MIB module defining objects for the management of a pair of ADSL modems at each end of the ADSL line. Each such line has an entry in an ifTable which may include multiple modem lines. An agent may reside at either end of the ADSL line however the MIB is designed to require no management communication between them beyond that inherent in the low-level ADSL line protocol. The agent may monitor and control this protocol for its needs. ADSL lines may support optional Fast or Interleaved channels. If these are supported, additional entries corresponding to the supported channels must be created in the ifTable. Thus an ADSL line that supports both channels will have three entries in the ifTable, one for each physical, fast, and interleaved, whose ifType values are equal to adsl(94), fast(125), and interleaved(124), respectively. The ifStackTable is used to represent the relationship between the entries. Naming Conventions: Atuc -- (ATUC) modem at near (Central) end of line Atur -- (ATUR) modem at Remote end of line Curr -- Current Prev -- Previous Atn -- Attenuation ES -- Errored Second. LCS -- Line Code Specific Lof -- Loss of Frame Lol -- Loss of Link Los -- Loss of Signal Lpr -- Loss of Power xxxs-- interval of Seconds in which xxx occurs (e.g., xxx=Lof, Los, Lpr) Max -- Maximum Mgn -- Margin Min -- Minimum Psd -- Power Spectral Density Snr -- Signal to Noise Ratio Tx -- Transmit Blks-- Blocks, a data unit, see adslAtuXChanCrcBlockLength 
.1.3.6.1.2.1.10.94.1,ADSL-LINE-MIB::adslLineMib,,,,,,
.1.3.6.1.2.1.10.94.1.1,ADSL-LINE-MIB::adslMibObjects,,,,,,
.1.3.6.1.2.1.10.94.1.1.1,ADSL-LINE-MIB::adslLineTable,,not-accessible,,current,,This table includes common attributes describing both ends of the line. It is required for all ADSL physical interfaces. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.1.1,ADSL-LINE-MIB::adslLineEntry,,not-accessible,ifIndex,current,,An entry in adslLineTable.
.1.3.6.1.2.1.10.94.1.1.1.1.1,ADSL-LINE-MIB::adslLineCoding,INTEGER,read-only,,current,other(1):dmt(2):cap(3):qam(4),Specifies the ADSL coding type used on this line.
.1.3.6.1.2.1.10.94.1.1.1.1.2,ADSL-LINE-MIB::adslLineType,INTEGER,read-only,,current,noChannel(1):fastOnly(2):interleavedOnly(3):fastOrInterleaved(4):fastAndInterleaved(5),Defines the type of ADSL physical line entity that exists, by defining whether and how the line is channelized. If the line is channelized, the value will be other than noChannel(1). This object defines which channel type(s) are supported. In the case that the line is channelized, the manager can use the ifStackTable to determine the ifIndex for the associated channel(s).
.1.3.6.1.2.1.10.94.1.1.1.1.3,ADSL-LINE-MIB::adslLineSpecific,OBJECT,read-only,,current,,OID instance in vendor-specific MIB. The Instance may be used to determine shelf/slot/port of the ATUC interface in a DSLAM.
.1.3.6.1.2.1.10.94.1.1.1.1.4,ADSL-LINE-MIB::adslLineConfProfile,OCTET,read-write,,current,,The value of this object identifies the row in the ADSL Line Configuration Profile Table, (adslLineConfProfileTable), which applies for this ADSL line, and channels if applicable. For `dynamic' mode, in the case which the configuration profile has not been set, the value will be set to `DEFVAL'. If the implementator of this MIB has chosen not to implement `dynamic assignment' of profiles, this object's MIN-ACCESS is read-only.
.1.3.6.1.2.1.10.94.1.1.1.1.5,ADSL-LINE-MIB::adslLineAlarmConfProfile,OCTET,read-write,,current,,The value of this object identifies the row in the ADSL Line Alarm Configuration Profile Table, (adslLineAlarmConfProfileTable), which applies to this ADSL line, and channels if applicable. For `dynamic' mode, in the case which the alarm profile has not been set, the value will be set to `DEFVAL'. If the implementator of this MIB has chosen not to implement `dynamic assignment' of profiles, this object's MIN-ACCESS is read-only.
.1.3.6.1.2.1.10.94.1.1.2,ADSL-LINE-MIB::adslAtucPhysTable,,not-accessible,,current,,This table provides one row for each ATUC. Each row contains the Physical Layer Parameters table for that ATUC. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.2.1,ADSL-LINE-MIB::adslAtucPhysEntry,,not-accessible,ifIndex,current,,An entry in the adslAtucPhysTable.
.1.3.6.1.2.1.10.94.1.1.2.1.1,ADSL-LINE-MIB::adslAtucInvSerialNumber,OCTET,read-only,,current,,The vendor specific string that identifies the vendor equipment.
.1.3.6.1.2.1.10.94.1.1.2.1.2,ADSL-LINE-MIB::adslAtucInvVendorID,OCTET,read-only,,current,,The vendor ID code is a copy of the binary vendor identification field defined by the PHY[10] and expressed as readable characters.
.1.3.6.1.2.1.10.94.1.1.2.1.3,ADSL-LINE-MIB::adslAtucInvVersionNumber,OCTET,read-only,,current,,The vendor specific version number sent by this ATU as part of the initialization messages. It is a copy of the binary version number field defined by the PHY[10] and expressed as readable characters.
.1.3.6.1.2.1.10.94.1.1.2.1.4,ADSL-LINE-MIB::adslAtucCurrSnrMgn,INTEGER,read-only,,current,,Noise Margin as seen by this ATU with respect to its received signal in tenth dB.
.1.3.6.1.2.1.10.94.1.1.2.1.5,ADSL-LINE-MIB::adslAtucCurrAtn,Gauge32,read-only,,current,,Measured difference in the total power transmitted by the peer ATU and the total power received by this ATU.
.1.3.6.1.2.1.10.94.1.1.2.1.6,ADSL-LINE-MIB::adslAtucCurrStatus,BITS,read-only,,current,noDefect(0):lossOfFraming(1):lossOfSignal(2):lossOfPower(3):lossOfSignalQuality(4):lossOfLink(5):dataInitFailure(6):configInitFailure(7):protocolInitFailure(8):noPeerAtuPresent(9),Indicates current state of the ATUC line. This is a bit-map of possible conditions. The various bit positions are: 0 noDefect There no defects on the line 1 lossOfFraming ATUC failure due to not receiving valid frame. 2 lossOfSignal ATUC failure due to not receiving signal. 3 lossOfPower ATUC failure due to loss of power. Note: the Agent may still function. 4 lossOfSignalQuality Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds 10^-7. 5 lossOfLink ATUC failure due to inability to link with ATUR. 6 dataInitFailure ATUC failure during initialization due to bit errors corrupting startup exchange data. 7 configInitFailure ATUC failure during initialization due to peer ATU not able to support requested configuration 8 protocolInitFailure ATUC failure during initialization due to incompatible protocol used by the peer ATU. 9 noPeerAtuPresent ATUC failure during initialization due to no activation sequence detected from peer ATU. This is intended to supplement ifOperStatus.
.1.3.6.1.2.1.10.94.1.1.2.1.7,ADSL-LINE-MIB::adslAtucCurrOutputPwr,INTEGER,read-only,,current,,Measured total output power transmitted by this ATU. This is the measurement that was reported during the last activation sequence.
.1.3.6.1.2.1.10.94.1.1.2.1.8,ADSL-LINE-MIB::adslAtucCurrAttainableRate,Gauge32,read-only,,current,,Indicates the maximum currently attainable data rate by the ATU. This value will be equal or greater than the current line rate.
.1.3.6.1.2.1.10.94.1.1.3,ADSL-LINE-MIB::adslAturPhysTable,,not-accessible,,current,,This table provides one row for each ATUR Each row contains the Physical Layer Parameters table for that ATUR. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.3.1,ADSL-LINE-MIB::adslAturPhysEntry,,not-accessible,ifIndex,current,,An entry in the adslAturPhysTable.
.1.3.6.1.2.1.10.94.1.1.3.1.1,ADSL-LINE-MIB::adslAturInvSerialNumber,OCTET,read-only,,current,,The vendor specific string that identifies the vendor equipment.
.1.3.6.1.2.1.10.94.1.1.3.1.2,ADSL-LINE-MIB::adslAturInvVendorID,OCTET,read-only,,current,,The vendor ID code is a copy of the binary vendor identification field defined by the PHY[10] and expressed as readable characters.
.1.3.6.1.2.1.10.94.1.1.3.1.3,ADSL-LINE-MIB::adslAturInvVersionNumber,OCTET,read-only,,current,,The vendor specific version number sent by this ATU as part of the initialization messages. It is a copy of the binary version number field defined by the PHY[10] and expressed as readable characters.
.1.3.6.1.2.1.10.94.1.1.3.1.4,ADSL-LINE-MIB::adslAturCurrSnrMgn,INTEGER,read-only,,current,,Noise Margin as seen by this ATU with respect to its received signal in tenth dB.
.1.3.6.1.2.1.10.94.1.1.3.1.5,ADSL-LINE-MIB::adslAturCurrAtn,Gauge32,read-only,,current,,Measured difference in the total power transmitted by the peer ATU and the total power received by this ATU.
.1.3.6.1.2.1.10.94.1.1.3.1.6,ADSL-LINE-MIB::adslAturCurrStatus,BITS,read-only,,current,noDefect(0):lossOfFraming(1):lossOfSignal(2):lossOfPower(3):lossOfSignalQuality(4),Indicates current state of the ATUR line. This is a bit-map of possible conditions. Due to the isolation of the ATUR when line problems occur, many state conditions like loss of power, loss of quality signal, and initialization errors, can not be determined. While trouble shooting ATUR, also use object, adslAtucCurrStatus. The various bit positions are: 0 noDefect There no defects on the line 1 lossOfFraming ATUR failure due to not receiving valid frame 2 lossOfSignal ATUR failure due to not receiving signal 3 lossOfPower ATUR failure due to loss of power 4 lossOfSignalQuality Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds 10^-7. This is intended to supplement ifOperStatus.
.1.3.6.1.2.1.10.94.1.1.3.1.7,ADSL-LINE-MIB::adslAturCurrOutputPwr,INTEGER,read-only,,current,,Measured total output power transmitted by this ATU. This is the measurement that was reported during the last activation sequence.
.1.3.6.1.2.1.10.94.1.1.3.1.8,ADSL-LINE-MIB::adslAturCurrAttainableRate,Gauge32,read-only,,current,,Indicates the maximum currently attainable data rate by the ATU. This value will be equal or greater than the current line rate.
.1.3.6.1.2.1.10.94.1.1.4,ADSL-LINE-MIB::adslAtucChanTable,,not-accessible,,current,,This table provides one row for each ATUC channel. ADSL channel interfaces are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
.1.3.6.1.2.1.10.94.1.1.4.1,ADSL-LINE-MIB::adslAtucChanEntry,,not-accessible,ifIndex,current,,An entry in the adslAtucChanTable.
.1.3.6.1.2.1.10.94.1.1.4.1.1,ADSL-LINE-MIB::adslAtucChanInterleaveDelay,Gauge32,read-only,,current,,Interleave Delay for this channel. Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity at the expense of payload latency. In the case where the ifType is Fast(125), use noSuchObject.
.1.3.6.1.2.1.10.94.1.1.4.1.2,ADSL-LINE-MIB::adslAtucChanCurrTxRate,Gauge32,read-only,,current,,Actual transmit rate on this channel.
.1.3.6.1.2.1.10.94.1.1.4.1.3,ADSL-LINE-MIB::adslAtucChanPrevTxRate,Gauge32,read-only,,current,,The rate at the time of the last adslAtucRateChangeTrap event. It is also set at initialization to prevent a trap being sent. Rate changes less than adslAtucThresh(*)RateDown or less than adslAtucThresh(*)RateUp will not cause a trap or cause this object to change. (*) == Fast or Interleave. See AdslLineAlarmConfProfileEntry.
.1.3.6.1.2.1.10.94.1.1.4.1.4,ADSL-LINE-MIB::adslAtucChanCrcBlockLength,Gauge32,read-only,,current,,Indicates the length of the channel data-block on which the CRC operates. Refer to Line Code Specific MIBs, [11] and [12] for more information.
.1.3.6.1.2.1.10.94.1.1.5,ADSL-LINE-MIB::adslAturChanTable,,not-accessible,,current,,This table provides one row for each ATUR channel. ADSL channel interfaces are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
.1.3.6.1.2.1.10.94.1.1.5.1,ADSL-LINE-MIB::adslAturChanEntry,,not-accessible,ifIndex,current,,An entry in the adslAturChanTable.
.1.3.6.1.2.1.10.94.1.1.5.1.1,ADSL-LINE-MIB::adslAturChanInterleaveDelay,Gauge32,read-only,,current,,Interleave Delay for this channel. Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity at the expense of payload latency. In the case where the ifType is Fast(125), use noSuchObject.
.1.3.6.1.2.1.10.94.1.1.5.1.2,ADSL-LINE-MIB::adslAturChanCurrTxRate,Gauge32,read-only,,current,,Actual transmit rate on this channel.
.1.3.6.1.2.1.10.94.1.1.5.1.3,ADSL-LINE-MIB::adslAturChanPrevTxRate,Gauge32,read-only,,current,,The rate at the time of the last adslAturRateChangeTrap event. It is also set at initialization to prevent a trap being sent. Rate changes less than adslAturThresh(*)RateDown or less than adslAturThresh(*)RateUp will not cause a trap or cause this object to change. (*) == Fast or Interleave. See AdslLineAlarmConfProfileEntry.
.1.3.6.1.2.1.10.94.1.1.5.1.4,ADSL-LINE-MIB::adslAturChanCrcBlockLength,Gauge32,read-only,,current,,Indicates the length of the channel data-block on which the CRC operates. Refer to Line Code Specific MIBs, [11] and [12] for more information.
.1.3.6.1.2.1.10.94.1.1.6,ADSL-LINE-MIB::adslAtucPerfDataTable,,not-accessible,,current,,This table provides one row for each ATUC. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.6.1,ADSL-LINE-MIB::adslAtucPerfDataEntry,,not-accessible,ifIndex,current,,An entry in adslAtucPerfDataTable.
.1.3.6.1.2.1.10.94.1.1.6.1.1,ADSL-LINE-MIB::adslAtucPerfLofs,Counter32,read-only,,current,,Count of the number of Loss of Framing failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.6.1.2,ADSL-LINE-MIB::adslAtucPerfLoss,Counter32,read-only,,current,,Count of the number of Loss of Signal failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.6.1.3,ADSL-LINE-MIB::adslAtucPerfLols,Counter32,read-only,,current,,Count of the number of Loss of Link failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.6.1.4,ADSL-LINE-MIB::adslAtucPerfLprs,Counter32,read-only,,current,,Count of the number of Loss of Power failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.6.1.5,ADSL-LINE-MIB::adslAtucPerfESs,Counter32,read-only,,current,,Count of the number of Errored Seconds since agent reset. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.6.1.6,ADSL-LINE-MIB::adslAtucPerfInits,Counter32,read-only,,current,,Count of the line initialization attempts since agent reset. Includes both successful and failed attempts.
.1.3.6.1.2.1.10.94.1.1.6.1.7,ADSL-LINE-MIB::adslAtucPerfValidIntervals,INTEGER,read-only,,current,,The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the maximum # of intervals supported. The value will be <n> unless the measurement was (re-)started within the last (<n>*15) minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.94.1.1.6.1.8,ADSL-LINE-MIB::adslAtucPerfInvalidIntervals,INTEGER,read-only,,current,,The number of intervals in the range from 0 to the value of adslAtucPerfValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.94.1.1.6.1.9,ADSL-LINE-MIB::adslAtucPerfCurr15MinTimeElapsed,Gauge32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.94.1.1.6.1.10,ADSL-LINE-MIB::adslAtucPerfCurr15MinLofs,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Framing.
.1.3.6.1.2.1.10.94.1.1.6.1.11,ADSL-LINE-MIB::adslAtucPerfCurr15MinLoss,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Signal.
.1.3.6.1.2.1.10.94.1.1.6.1.12,ADSL-LINE-MIB::adslAtucPerfCurr15MinLols,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Link.
.1.3.6.1.2.1.10.94.1.1.6.1.13,ADSL-LINE-MIB::adslAtucPerfCurr15MinLprs,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Power.
.1.3.6.1.2.1.10.94.1.1.6.1.14,ADSL-LINE-MIB::adslAtucPerfCurr15MinESs,Gauge32,read-only,,current,,Count of Errored Seconds in the current 15 minute interval. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.6.1.15,ADSL-LINE-MIB::adslAtucPerfCurr15MinInits,Gauge32,read-only,,current,,Count of the line initialization attempts in the current 15 minute interval. Includes both successful and failed attempts.
.1.3.6.1.2.1.10.94.1.1.6.1.16,ADSL-LINE-MIB::adslAtucPerfCurr1DayTimeElapsed,Gauge32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.94.1.1.6.1.17,ADSL-LINE-MIB::adslAtucPerfCurr1DayLofs,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Framing during the current day as measured by adslAtucPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.6.1.18,ADSL-LINE-MIB::adslAtucPerfCurr1DayLoss,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Signal during the current day as measured by adslAtucPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.6.1.19,ADSL-LINE-MIB::adslAtucPerfCurr1DayLols,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Link during the current day as measured by adslAtucPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.6.1.20,ADSL-LINE-MIB::adslAtucPerfCurr1DayLprs,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Power during the current day as measured by adslAtucPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.6.1.21,ADSL-LINE-MIB::adslAtucPerfCurr1DayESs,Gauge32,read-only,,current,,Count of Errored Seconds during the current day as measured by adslAtucPerfCurr1DayTimeElapsed. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.6.1.22,ADSL-LINE-MIB::adslAtucPerfCurr1DayInits,Gauge32,read-only,,current,,Count of the line initialization attempts in the day as measured by adslAtucPerfCurr1DayTimeElapsed. Includes both successful and failed attempts.
.1.3.6.1.2.1.10.94.1.1.6.1.23,ADSL-LINE-MIB::adslAtucPerfPrev1DayMoniSecs,INTEGER,read-only,,current,,The amount of time in the previous 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.94.1.1.6.1.24,ADSL-LINE-MIB::adslAtucPerfPrev1DayLofs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Framing within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.6.1.25,ADSL-LINE-MIB::adslAtucPerfPrev1DayLoss,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Signal within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.6.1.26,ADSL-LINE-MIB::adslAtucPerfPrev1DayLols,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Link within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.6.1.27,ADSL-LINE-MIB::adslAtucPerfPrev1DayLprs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Power within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.6.1.28,ADSL-LINE-MIB::adslAtucPerfPrev1DayESs,Gauge32,read-only,,current,,Count of Errored Seconds within the most recent previous 1-day period. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.6.1.29,ADSL-LINE-MIB::adslAtucPerfPrev1DayInits,Gauge32,read-only,,current,,Count of the line initialization attempts in the most recent previous 1-day period. Includes both successful and failed attempts.
.1.3.6.1.2.1.10.94.1.1.7,ADSL-LINE-MIB::adslAturPerfDataTable,,not-accessible,,current,,This table provides one row for each ATUR. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.7.1,ADSL-LINE-MIB::adslAturPerfDataEntry,,not-accessible,ifIndex,current,,An entry in adslAturPerfDataTable.
.1.3.6.1.2.1.10.94.1.1.7.1.1,ADSL-LINE-MIB::adslAturPerfLofs,Counter32,read-only,,current,,Count of the number of Loss of Framing failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.7.1.2,ADSL-LINE-MIB::adslAturPerfLoss,Counter32,read-only,,current,,Count of the number of Loss of Signal failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.7.1.3,ADSL-LINE-MIB::adslAturPerfLprs,Counter32,read-only,,current,,Count of the number of Loss of Power failures since agent reset.
.1.3.6.1.2.1.10.94.1.1.7.1.4,ADSL-LINE-MIB::adslAturPerfESs,Counter32,read-only,,current,,Count of the number of Errored Seconds since agent reset. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.7.1.5,ADSL-LINE-MIB::adslAturPerfValidIntervals,INTEGER,read-only,,current,,The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the maximum # of intervals supported. The value will be <n> unless the measurement was (re-)started within the last (<n>*15) minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.94.1.1.7.1.6,ADSL-LINE-MIB::adslAturPerfInvalidIntervals,INTEGER,read-only,,current,,The number of intervals in the range from 0 to the value of adslAturPerfValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.94.1.1.7.1.7,ADSL-LINE-MIB::adslAturPerfCurr15MinTimeElapsed,Gauge32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.94.1.1.7.1.8,ADSL-LINE-MIB::adslAturPerfCurr15MinLofs,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Framing.
.1.3.6.1.2.1.10.94.1.1.7.1.9,ADSL-LINE-MIB::adslAturPerfCurr15MinLoss,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Signal.
.1.3.6.1.2.1.10.94.1.1.7.1.10,ADSL-LINE-MIB::adslAturPerfCurr15MinLprs,Gauge32,read-only,,current,,Count of seconds in the current 15 minute interval when there was Loss of Power.
.1.3.6.1.2.1.10.94.1.1.7.1.11,ADSL-LINE-MIB::adslAturPerfCurr15MinESs,Gauge32,read-only,,current,,Count of Errored Seconds in the current 15 minute interval. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.7.1.12,ADSL-LINE-MIB::adslAturPerfCurr1DayTimeElapsed,Gauge32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.94.1.1.7.1.13,ADSL-LINE-MIB::adslAturPerfCurr1DayLofs,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Framing during the current day as measured by adslAturPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.7.1.14,ADSL-LINE-MIB::adslAturPerfCurr1DayLoss,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Signal during the current day as measured by adslAturPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.7.1.15,ADSL-LINE-MIB::adslAturPerfCurr1DayLprs,Gauge32,read-only,,current,,Count of the number of seconds when there was Loss of Power during the current day as measured by adslAturPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.7.1.16,ADSL-LINE-MIB::adslAturPerfCurr1DayESs,Gauge32,read-only,,current,,Count of Errored Seconds during the current day as measured by adslAturPerfCurr1DayTimeElapsed. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.7.1.17,ADSL-LINE-MIB::adslAturPerfPrev1DayMoniSecs,INTEGER,read-only,,current,,The amount of time in the previous 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.94.1.1.7.1.18,ADSL-LINE-MIB::adslAturPerfPrev1DayLofs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Framing within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.7.1.19,ADSL-LINE-MIB::adslAturPerfPrev1DayLoss,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Signal within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.7.1.20,ADSL-LINE-MIB::adslAturPerfPrev1DayLprs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Power within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.7.1.21,ADSL-LINE-MIB::adslAturPerfPrev1DayESs,Gauge32,read-only,,current,,Count of Errored Seconds within the most recent previous 1-day period. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.8,ADSL-LINE-MIB::adslAtucIntervalTable,,not-accessible,,current,,This table provides one row for each ATUC performance data collection interval. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.8.1,ADSL-LINE-MIB::adslAtucIntervalEntry,,not-accessible,ifIndex:adslAtucIntervalNumber,current,,An entry in the adslAtucIntervalTable.
.1.3.6.1.2.1.10.94.1.1.8.1.1,ADSL-LINE-MIB::adslAtucIntervalNumber,INTEGER,not-accessible,,current,,Performance Data Interval number 1 is the the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional.
.1.3.6.1.2.1.10.94.1.1.8.1.2,ADSL-LINE-MIB::adslAtucIntervalLofs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Framing.
.1.3.6.1.2.1.10.94.1.1.8.1.3,ADSL-LINE-MIB::adslAtucIntervalLoss,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Signal.
.1.3.6.1.2.1.10.94.1.1.8.1.4,ADSL-LINE-MIB::adslAtucIntervalLols,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Link.
.1.3.6.1.2.1.10.94.1.1.8.1.5,ADSL-LINE-MIB::adslAtucIntervalLprs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Power.
.1.3.6.1.2.1.10.94.1.1.8.1.6,ADSL-LINE-MIB::adslAtucIntervalESs,Gauge32,read-only,,current,,Count of Errored Seconds in the interval. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.8.1.7,ADSL-LINE-MIB::adslAtucIntervalInits,Gauge32,read-only,,current,,Count of the line initialization attempts during the interval. Includes both successful and failed attempts.
.1.3.6.1.2.1.10.94.1.1.8.1.8,ADSL-LINE-MIB::adslAtucIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.94.1.1.9,ADSL-LINE-MIB::adslAturIntervalTable,,not-accessible,,current,,This table provides one row for each ATUR performance data collection interval. ADSL physical interfaces are those ifEntries where ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.1.1.9.1,ADSL-LINE-MIB::adslAturIntervalEntry,,not-accessible,ifIndex:adslAturIntervalNumber,current,,An entry in the adslAturIntervalTable.
.1.3.6.1.2.1.10.94.1.1.9.1.1,ADSL-LINE-MIB::adslAturIntervalNumber,INTEGER,not-accessible,,current,,Performance Data Interval number 1 is the the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional.
.1.3.6.1.2.1.10.94.1.1.9.1.2,ADSL-LINE-MIB::adslAturIntervalLofs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Framing.
.1.3.6.1.2.1.10.94.1.1.9.1.3,ADSL-LINE-MIB::adslAturIntervalLoss,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Signal.
.1.3.6.1.2.1.10.94.1.1.9.1.4,ADSL-LINE-MIB::adslAturIntervalLprs,Gauge32,read-only,,current,,Count of seconds in the interval when there was Loss of Power.
.1.3.6.1.2.1.10.94.1.1.9.1.5,ADSL-LINE-MIB::adslAturIntervalESs,Gauge32,read-only,,current,,Count of Errored Seconds in the interval. The errored second parameter is a count of one-second intervals containing one or more crc anomalies, or one or more los or sef defects.
.1.3.6.1.2.1.10.94.1.1.9.1.6,ADSL-LINE-MIB::adslAturIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.94.1.1.10,ADSL-LINE-MIB::adslAtucChanPerfDataTable,,not-accessible,,current,,This table provides one row for each ATUC channel. ADSL channel interfaces are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
.1.3.6.1.2.1.10.94.1.1.10.1,ADSL-LINE-MIB::adslAtucChanPerfDataEntry,,not-accessible,ifIndex,current,,An entry in adslAtucChanPerfDataTable.
.1.3.6.1.2.1.10.94.1.1.10.1.1,ADSL-LINE-MIB::adslAtucChanReceivedBlks,Counter32,read-only,,current,,Count of all encoded blocks received on this channel since agent reset.
.1.3.6.1.2.1.10.94.1.1.10.1.2,ADSL-LINE-MIB::adslAtucChanTransmittedBlks,Counter32,read-only,,current,,Count of all encoded blocks transmitted on this channel since agent reset.
.1.3.6.1.2.1.10.94.1.1.10.1.3,ADSL-LINE-MIB::adslAtucChanCorrectedBlks,Counter32,read-only,,current,,Count of all blocks received with errors that were corrected since agent reset. These blocks are passed on as good data.
.1.3.6.1.2.1.10.94.1.1.10.1.4,ADSL-LINE-MIB::adslAtucChanUncorrectBlks,Counter32,read-only,,current,,Count of all blocks received with uncorrectable errors since agent reset.
.1.3.6.1.2.1.10.94.1.1.10.1.5,ADSL-LINE-MIB::adslAtucChanPerfValidIntervals,INTEGER,read-only,,current,,The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the maximum # of intervals supported. The value will be <n> unless the measurement was (re-)started within the last (<n>*15) minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.94.1.1.10.1.6,ADSL-LINE-MIB::adslAtucChanPerfInvalidIntervals,INTEGER,read-only,,current,,The number of intervals in the range from 0 to the value of adslAtucChanPerfValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.94.1.1.10.1.7,ADSL-LINE-MIB::adslAtucChanPerfCurr15MinTimeElapsed,Gauge32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.94.1.1.10.1.8,ADSL-LINE-MIB::adslAtucChanPerfCurr15MinReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.10.1.9,ADSL-LINE-MIB::adslAtucChanPerfCurr15MinTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.10.1.10,ADSL-LINE-MIB::adslAtucChanPerfCurr15MinCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.10.1.11,ADSL-LINE-MIB::adslAtucChanPerfCurr15MinUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.10.1.12,ADSL-LINE-MIB::adslAtucChanPerfCurr1DayTimeElapsed,Gauge32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.94.1.1.10.1.13,ADSL-LINE-MIB::adslAtucChanPerfCurr1DayReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel during the current day as measured by adslAtucChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.10.1.14,ADSL-LINE-MIB::adslAtucChanPerfCurr1DayTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel during the current day as measured by adslAtucChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.10.1.15,ADSL-LINE-MIB::adslAtucChanPerfCurr1DayCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel during the current day as measured by adslAtucChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.10.1.16,ADSL-LINE-MIB::adslAtucChanPerfCurr1DayUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel during the current day as measured by adslAtucChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.10.1.17,ADSL-LINE-MIB::adslAtucChanPerfPrev1DayMoniSecs,INTEGER,read-only,,current,,The amount of time in the previous 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.94.1.1.10.1.18,ADSL-LINE-MIB::adslAtucChanPerfPrev1DayReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.10.1.19,ADSL-LINE-MIB::adslAtucChanPerfPrev1DayTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.10.1.20,ADSL-LINE-MIB::adslAtucChanPerfPrev1DayCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.10.1.21,ADSL-LINE-MIB::adslAtucChanPerfPrev1DayUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.11,ADSL-LINE-MIB::adslAturChanPerfDataTable,,not-accessible,,current,,This table provides one row for each ATUR channel. ADSL channel interfaces are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
.1.3.6.1.2.1.10.94.1.1.11.1,ADSL-LINE-MIB::adslAturChanPerfDataEntry,,not-accessible,ifIndex,current,,An entry in adslAturChanPerfDataTable.
.1.3.6.1.2.1.10.94.1.1.11.1.1,ADSL-LINE-MIB::adslAturChanReceivedBlks,Counter32,read-only,,current,,Count of all encoded blocks received on this channel since agent reset.
.1.3.6.1.2.1.10.94.1.1.11.1.2,ADSL-LINE-MIB::adslAturChanTransmittedBlks,Counter32,read-only,,current,,Count of all encoded blocks transmitted on this channel since agent reset.
.1.3.6.1.2.1.10.94.1.1.11.1.3,ADSL-LINE-MIB::adslAturChanCorrectedBlks,Counter32,read-only,,current,,Count of all blocks received with errors that were corrected since agent reset. These blocks are passed on as good data.
.1.3.6.1.2.1.10.94.1.1.11.1.4,ADSL-LINE-MIB::adslAturChanUncorrectBlks,Counter32,read-only,,current,,Count of all blocks received with uncorrectable errors since agent reset.
.1.3.6.1.2.1.10.94.1.1.11.1.5,ADSL-LINE-MIB::adslAturChanPerfValidIntervals,INTEGER,read-only,,current,,The number of previous 15-minute intervals in the interval table for which data was collected. Given that <n> is the maximum # of intervals supported. The value will be <n> unless the measurement was (re-)started within the last (<n>*15) minutes, in which case the value will be the number of complete 15 minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy) it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.94.1.1.11.1.6,ADSL-LINE-MIB::adslAturChanPerfInvalidIntervals,INTEGER,read-only,,current,,The number of intervals in the range from 0 to the value of adslAturChanPerfValidIntervals for which no data is available. This object will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.94.1.1.11.1.7,ADSL-LINE-MIB::adslAturChanPerfCurr15MinTimeElapsed,Gauge32,read-only,,current,,Total elapsed seconds in this interval. A full interval is 900 seconds.
.1.3.6.1.2.1.10.94.1.1.11.1.8,ADSL-LINE-MIB::adslAturChanPerfCurr15MinReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.11.1.9,ADSL-LINE-MIB::adslAturChanPerfCurr15MinTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.11.1.10,ADSL-LINE-MIB::adslAturChanPerfCurr15MinCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.11.1.11,ADSL-LINE-MIB::adslAturChanPerfCurr15MinUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel within the current 15 minute interval.
.1.3.6.1.2.1.10.94.1.1.11.1.12,ADSL-LINE-MIB::adslAturChanPerfCurr1DayTimeElapsed,Gauge32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.94.1.1.11.1.13,ADSL-LINE-MIB::adslAturChanPerfCurr1DayReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel during the current day as measured by adslAturChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.11.1.14,ADSL-LINE-MIB::adslAturChanPerfCurr1DayTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel during the current day as measured by adslAturChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.11.1.15,ADSL-LINE-MIB::adslAturChanPerfCurr1DayCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel during the current day as measured by adslAturChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.11.1.16,ADSL-LINE-MIB::adslAturChanPerfCurr1DayUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel during the current day as measured by adslAturChanPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.10.94.1.1.11.1.17,ADSL-LINE-MIB::adslAturChanPerfPrev1DayMoniSecs,INTEGER,read-only,,current,,The amount of time in the previous 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.94.1.1.11.1.18,ADSL-LINE-MIB::adslAturChanPerfPrev1DayReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.11.1.19,ADSL-LINE-MIB::adslAturChanPerfPrev1DayTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.11.1.20,ADSL-LINE-MIB::adslAturChanPerfPrev1DayCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.11.1.21,ADSL-LINE-MIB::adslAturChanPerfPrev1DayUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel within the most recent previous 1-day period.
.1.3.6.1.2.1.10.94.1.1.12,ADSL-LINE-MIB::adslAtucChanIntervalTable,,not-accessible,,current,,This table provides one row for each ATUC channel's performance data collection interval. ADSL channel interfaces are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
.1.3.6.1.2.1.10.94.1.1.12.1,ADSL-LINE-MIB::adslAtucChanIntervalEntry,,not-accessible,ifIndex:adslAtucChanIntervalNumber,current,,An entry in the adslAtucIntervalTable.
.1.3.6.1.2.1.10.94.1.1.12.1.1,ADSL-LINE-MIB::adslAtucChanIntervalNumber,INTEGER,not-accessible,,current,,Performance Data Interval number 1 is the the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional.
.1.3.6.1.2.1.10.94.1.1.12.1.2,ADSL-LINE-MIB::adslAtucChanIntervalReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.12.1.3,ADSL-LINE-MIB::adslAtucChanIntervalTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.12.1.4,ADSL-LINE-MIB::adslAtucChanIntervalCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.12.1.5,ADSL-LINE-MIB::adslAtucChanIntervalUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.12.1.6,ADSL-LINE-MIB::adslAtucChanIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.94.1.1.13,ADSL-LINE-MIB::adslAturChanIntervalTable,,not-accessible,,current,,This table provides one row for each ATUR channel's performance data collection interval. ADSL channel interfaces are those ifEntries where ifType is equal to adslInterleave(124) or adslFast(125).
.1.3.6.1.2.1.10.94.1.1.13.1,ADSL-LINE-MIB::adslAturChanIntervalEntry,,not-accessible,ifIndex:adslAturChanIntervalNumber,current,,An entry in the adslAturIntervalTable.
.1.3.6.1.2.1.10.94.1.1.13.1.1,ADSL-LINE-MIB::adslAturChanIntervalNumber,INTEGER,not-accessible,,current,,Performance Data Interval number 1 is the the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are optional.
.1.3.6.1.2.1.10.94.1.1.13.1.2,ADSL-LINE-MIB::adslAturChanIntervalReceivedBlks,Gauge32,read-only,,current,,Count of all encoded blocks received on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.13.1.3,ADSL-LINE-MIB::adslAturChanIntervalTransmittedBlks,Gauge32,read-only,,current,,Count of all encoded blocks transmitted on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.13.1.4,ADSL-LINE-MIB::adslAturChanIntervalCorrectedBlks,Gauge32,read-only,,current,,Count of all blocks received with errors that were corrected on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.13.1.5,ADSL-LINE-MIB::adslAturChanIntervalUncorrectBlks,Gauge32,read-only,,current,,Count of all blocks received with uncorrectable errors on this channel during this interval.
.1.3.6.1.2.1.10.94.1.1.13.1.6,ADSL-LINE-MIB::adslAturChanIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.94.1.1.14,ADSL-LINE-MIB::adslLineConfProfileTable,,not-accessible,,current,,This table contains information on the ADSL line configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the ADSL line.
.1.3.6.1.2.1.10.94.1.1.14.1,ADSL-LINE-MIB::adslLineConfProfileEntry,,not-accessible,IMPLIEDadslLineConfProfileName,current,,Each entry consists of a list of parameters that represents the configuration of an ADSL modem. When `dynamic' profiles are implemented, a default profile will always exist. This profile's name will be set to `DEFVAL' and its parameters will be set to vendor specific values, unless otherwise specified in this document. When `static' profiles are implemented, profiles are automaticly created or destroyed as ADSL physical lines are discovered and removed by the system. The name of the profile will be equivalent to the decimal value of the line's interface index. 
.1.3.6.1.2.1.10.94.1.1.14.1.1,ADSL-LINE-MIB::adslLineConfProfileName,OCTET,not-accessible,,current,,This object is used by the line configuration table in order to identify a row of this table. When `dynamic' profiles are implemented, the profile name is user specified. Also, the system will always provide a default profile whose name is `DEFVAL'. When `static' profiles are implemented, there is an one-to-one relationship between each line and its profile. In which case, the profile name will need to algorithmicly represent the Line's ifIndex. Therefore, the profile's name is a decimalized string of the ifIndex that is fixed-length (i.e., 10) with leading zero(s). For example, the profile name for ifIndex which equals '15' will be '0000000015'.
.1.3.6.1.2.1.10.94.1.1.14.1.2,ADSL-LINE-MIB::adslAtucConfRateMode,INTEGER,read-create,,current,fixed(1):adaptAtStartup(2):adaptAtRuntime(3),Defines what form of transmit rate adaptation is configured on this modem. See ADSL Forum TR-005 [3] for more information.
.1.3.6.1.2.1.10.94.1.1.14.1.3,ADSL-LINE-MIB::adslAtucConfRateChanRatio,INTEGER,read-create,,current,,Configured allocation ratio of excess transmit bandwidth between fast and interleaved channels. Only applies when two channel mode and RADSL are supported. Distribute bandwidth on each channel in excess of the corresponding ChanConfMinTxRate so that: adslAtucConfRateChanRatio = [Fast / (Fast + Interleaved)] * 100 In other words this value is the fast channel percentage.
.1.3.6.1.2.1.10.94.1.1.14.1.4,ADSL-LINE-MIB::adslAtucConfTargetSnrMgn,INTEGER,read-create,,current,,Configured Target Signal/Noise Margin. This is the Noise Margin the modem must achieve with a BER of 10-7 or better to successfully complete initialization.
.1.3.6.1.2.1.10.94.1.1.14.1.5,ADSL-LINE-MIB::adslAtucConfMaxSnrMgn,INTEGER,read-create,,current,,Configured Maximum acceptable Signal/Noise Margin. If the Noise Margin is above this the modem should attempt to reduce its power output to optimize its operation.
.1.3.6.1.2.1.10.94.1.1.14.1.6,ADSL-LINE-MIB::adslAtucConfMinSnrMgn,INTEGER,read-create,,current,,Configured Minimum acceptable Signal/Noise Margin. If the noise margin falls below this level, the modem should attempt to increase its power output. If that is not possible the modem will attempt to re-initialize or shut down.
.1.3.6.1.2.1.10.94.1.1.14.1.7,ADSL-LINE-MIB::adslAtucConfDownshiftSnrMgn,INTEGER,read-create,,current,,Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate. In the case that RADSL mode is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.8,ADSL-LINE-MIB::adslAtucConfUpshiftSnrMgn,INTEGER,read-create,,current,,Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt to increase its transmit rate. In the case that RADSL is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.9,ADSL-LINE-MIB::adslAtucConfMinUpshiftTime,INTEGER,read-create,,current,,Minimum time that the current margin is above UpshiftSnrMgn before an upshift occurs. In the case that RADSL is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.10,ADSL-LINE-MIB::adslAtucConfMinDownshiftTime,INTEGER,read-create,,current,,Minimum time that the current margin is below DownshiftSnrMgn before a downshift occurs. In the case that RADSL mode is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.11,ADSL-LINE-MIB::adslAtucChanConfFastMinTxRate,Unsigned32,read-create,,current,,Configured Minimum Transmit rate for `Fast' channels, in bps. See adslAtucConfRateChanRatio for information regarding RADSL mode and ATUR transmit rate for ATUC receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.12,ADSL-LINE-MIB::adslAtucChanConfInterleaveMinTxRate,Unsigned32,read-create,,current,,Configured Minimum Transmit rate for `Interleave' channels, in bps. See adslAtucConfRateChanRatio for information regarding RADSL mode and see ATUR transmit rate for receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.13,ADSL-LINE-MIB::adslAtucChanConfFastMaxTxRate,Unsigned32,read-create,,current,,Configured Maximum Transmit rate for `Fast' channels, in bps. See adslAtucConfRateChanRatio for information regarding RADSL mode and see ATUR transmit rate for ATUC receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.14,ADSL-LINE-MIB::adslAtucChanConfInterleaveMaxTxRate,Unsigned32,read-create,,current,,Configured Maximum Transmit rate for `Interleave' channels, in bps. See adslAtucConfRateChanRatio for information regarding RADSL mode and ATUR transmit rate for ATUC receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.15,ADSL-LINE-MIB::adslAtucChanConfMaxInterleaveDelay,INTEGER,read-create,,current,,Configured maximum Interleave Delay for this channel. Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity at the expense of payload latency.
.1.3.6.1.2.1.10.94.1.1.14.1.16,ADSL-LINE-MIB::adslAturConfRateMode,INTEGER,read-create,,current,fixed(1):adaptAtStartup(2):adaptAtRuntime(3),Defines what form of transmit rate adaptation is configured on this modem. See ADSL Forum TR-005 [3] for more information.
.1.3.6.1.2.1.10.94.1.1.14.1.17,ADSL-LINE-MIB::adslAturConfRateChanRatio,INTEGER,read-create,,current,,Configured allocation ratio of excess transmit bandwidth between fast and interleaved channels. Only applies when two channel mode and RADSL are supported. Distribute bandwidth on each channel in excess of the corresponding ChanConfMinTxRate so that: adslAturConfRateChanRatio = [Fast / (Fast + Interleaved)] * 100 In other words this value is the fast channel percentage.
.1.3.6.1.2.1.10.94.1.1.14.1.18,ADSL-LINE-MIB::adslAturConfTargetSnrMgn,INTEGER,read-create,,current,,Configured Target Signal/Noise Margin. This is the Noise Margin the modem must achieve with a BER of 10-7 or better to successfully complete initialization.
.1.3.6.1.2.1.10.94.1.1.14.1.19,ADSL-LINE-MIB::adslAturConfMaxSnrMgn,INTEGER,read-create,,current,,Configured Maximum acceptable Signal/Noise Margin. If the Noise Margin is above this the modem should attempt to reduce its power output to optimize its operation.
.1.3.6.1.2.1.10.94.1.1.14.1.20,ADSL-LINE-MIB::adslAturConfMinSnrMgn,INTEGER,read-create,,current,,Configured Minimum acceptable Signal/Noise Margin. If the noise margin falls below this level, the modem should attempt to increase its power output. If that is not possible the modem will attempt to re-initialize or shut down.
.1.3.6.1.2.1.10.94.1.1.14.1.21,ADSL-LINE-MIB::adslAturConfDownshiftSnrMgn,INTEGER,read-create,,current,,Configured Signal/Noise Margin for rate downshift. If the noise margin falls below this level, the modem should attempt to decrease its transmit rate. In the case that RADSL mode is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.22,ADSL-LINE-MIB::adslAturConfUpshiftSnrMgn,INTEGER,read-create,,current,,Configured Signal/Noise Margin for rate upshift. If the noise margin rises above this level, the modem should attempt to increase its transmit rate. In the case that RADSL is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.23,ADSL-LINE-MIB::adslAturConfMinUpshiftTime,INTEGER,read-create,,current,,Minimum time that the current margin is above UpshiftSnrMgn before an upshift occurs. In the case that RADSL is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.24,ADSL-LINE-MIB::adslAturConfMinDownshiftTime,INTEGER,read-create,,current,,Minimum time that the current margin is below DownshiftSnrMgn before a downshift occurs. In the case that RADSL mode is not present, the value will be `0'.
.1.3.6.1.2.1.10.94.1.1.14.1.25,ADSL-LINE-MIB::adslAturChanConfFastMinTxRate,Unsigned32,read-create,,current,,Configured Minimum Transmit rate for `Fast' channels, in bps. See adslAturConfRateChanRatio for information regarding RADSL mode and ATUC transmit rate for ATUR receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.26,ADSL-LINE-MIB::adslAturChanConfInterleaveMinTxRate,Unsigned32,read-create,,current,,Configured Minimum Transmit rate for `Interleave' channels, in bps. See adslAturConfRateChanRatio for information regarding RADSL mode and ATUC transmit rate for ATUR receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.27,ADSL-LINE-MIB::adslAturChanConfFastMaxTxRate,Unsigned32,read-create,,current,,Configured Maximum Transmit rate for `Fast' channels, in bps. See adslAturConfRateChanRatio for information regarding RADSL mode and ATUC transmit rate for ATUR receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.28,ADSL-LINE-MIB::adslAturChanConfInterleaveMaxTxRate,Unsigned32,read-create,,current,,Configured Maximum Transmit rate for `Interleave' channels, in bps. See adslAturConfRateChanRatio for information regarding RADSL mode and see ATUC transmit rate for ATUR receive rates.
.1.3.6.1.2.1.10.94.1.1.14.1.29,ADSL-LINE-MIB::adslAturChanConfMaxInterleaveDelay,INTEGER,read-create,,current,,Configured maximum Interleave Delay for this channel. Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity at the expense of payload latency.
.1.3.6.1.2.1.10.94.1.1.14.1.30,ADSL-LINE-MIB::adslLineConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile activated by setting this object to `active'. When `active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `outOfService') it must be first unreferenced from all associated lines. If the implementator of this MIB has chosen not to implement `dynamic assignment' of profiles, this object's MIN-ACCESS is read-only and its value is always to be `active'.
.1.3.6.1.2.1.10.94.1.1.15,ADSL-LINE-MIB::adslLineAlarmConfProfileTable,,not-accessible,,current,,This table contains information on the ADSL line configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the modem for a physical line
.1.3.6.1.2.1.10.94.1.1.15.1,ADSL-LINE-MIB::adslLineAlarmConfProfileEntry,,not-accessible,IMPLIEDadslLineAlarmConfProfileName,current,,Each entry consists of a list of parameters that represents the configuration of an ADSL modem. When `dynamic' profiles are implemented, a default profile will always exist. This profile's name will be set to `DEFVAL' and its parameters will be set to vendor specific values, unless otherwise specified in this document. When `static' profiles are implemented, profiles are automaticly created or destroyed as ADSL physical lines are discovered and removed by the system. The name of the profile will be equivalent to the decimal value of the line's interface index. 
.1.3.6.1.2.1.10.94.1.1.15.1.1,ADSL-LINE-MIB::adslLineAlarmConfProfileName,OCTET,not-accessible,,current,,This object is used by the line alarm configuration table in order to identify a row of this table. When `dynamic' profiles are implemented, the profile name is user specified. Also, the system will always provide a default profile whose name is `DEFVAL'. When `static' profiles are implemented, there is an one-to-one relationship between each line and its profile. In which case, the profile name will need to algorithmicly represent the Line's ifIndex. Therefore, the profile's name is a decimalized string of the ifIndex that is fixed-length (i.e., 10) with leading zero(s). For example, the profile name for ifIndex which equals '15' will be '0000000015'.
.1.3.6.1.2.1.10.94.1.1.15.1.2,ADSL-LINE-MIB::adslAtucThresh15MinLofs,INTEGER,read-create,,current,,The number of Loss of Frame Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLofsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.3,ADSL-LINE-MIB::adslAtucThresh15MinLoss,INTEGER,read-create,,current,,The number of Loss of Signal Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLossThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.4,ADSL-LINE-MIB::adslAtucThresh15MinLols,INTEGER,read-create,,current,,The number of Loss of Link Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLolsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.5,ADSL-LINE-MIB::adslAtucThresh15MinLprs,INTEGER,read-create,,current,,The number of Loss of Power Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfLprsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.6,ADSL-LINE-MIB::adslAtucThresh15MinESs,INTEGER,read-create,,current,,The number of Errored Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAtucPerfESsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.7,ADSL-LINE-MIB::adslAtucThreshFastRateUp,Unsigned32,read-create,,current,,Applies to `Fast' channels only. Configured change in rate causing an adslAtucRateChangeTrap. A trap is produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.8,ADSL-LINE-MIB::adslAtucThreshInterleaveRateUp,Unsigned32,read-create,,current,,Applies to `Interleave' channels only. Configured change in rate causing an adslAtucRateChangeTrap. A trap is produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.9,ADSL-LINE-MIB::adslAtucThreshFastRateDown,Unsigned32,read-create,,current,,Applies to `Fast' channels only. Configured change in rate causing an adslAtucRateChangeTrap. A trap is produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.10,ADSL-LINE-MIB::adslAtucThreshInterleaveRateDown,Unsigned32,read-create,,current,,Applies to `Interleave' channels only. Configured change in rate causing an adslAtucRateChangeTrap. A trap is produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.11,ADSL-LINE-MIB::adslAtucInitFailureTrapEnable,INTEGER,read-create,,current,enable(1):disable(2),Enables and disables the InitFailureTrap. This object is defaulted disable(2).
.1.3.6.1.2.1.10.94.1.1.15.1.12,ADSL-LINE-MIB::adslAturThresh15MinLofs,INTEGER,read-create,,current,,The number of Loss of Frame Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAturPerfLofsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.13,ADSL-LINE-MIB::adslAturThresh15MinLoss,INTEGER,read-create,,current,,The number of Loss of Signal Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAturPerfLossThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.14,ADSL-LINE-MIB::adslAturThresh15MinLprs,INTEGER,read-create,,current,,The number of Loss of Power Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAturPerfLprsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.15,ADSL-LINE-MIB::adslAturThresh15MinESs,INTEGER,read-create,,current,,The number of Errored Seconds encountered by an ADSL interface within any given 15 minutes performance data collection period, which causes the SNMP agent to send an adslAturPerfESsThreshTrap. One trap will be sent per interval per interface. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.16,ADSL-LINE-MIB::adslAturThreshFastRateUp,Unsigned32,read-create,,current,,Applies to `Fast' channels only. Configured change in rate causing an adslAturRateChangeTrap. A trap is produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.17,ADSL-LINE-MIB::adslAturThreshInterleaveRateUp,Unsigned32,read-create,,current,,Applies to `Interleave' channels only. configured change in rate causing an adslAturRateChangeTrap. A trap is produced when: ChanCurrTxRate >= ChanPrevTxRate plus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.18,ADSL-LINE-MIB::adslAturThreshFastRateDown,Unsigned32,read-create,,current,,Applies to `Fast' channels only. Configured change in rate causing an adslAturRateChangeTrap. A trap is produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.19,ADSL-LINE-MIB::adslAturThreshInterleaveRateDown,Unsigned32,read-create,,current,,Applies to `Interleave' channels only. Configured change in rate causing an adslAturRateChangeTrap. A trap is produced when: ChanCurrTxRate <= ChanPrevTxRate minus the value of this object. A value of `0' will disable the trap.
.1.3.6.1.2.1.10.94.1.1.15.1.20,ADSL-LINE-MIB::adslLineAlarmConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile activated by setting this object to `active'. When `active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `outOfService') it must be first unreferenced from all associated lines. If the implementator of this MIB has chosen not to implement `dynamic assignment' of profiles, this object's MIN-ACCESS is read-only and its value is always to be `active'.
.1.3.6.1.2.1.10.94.1.1.16,ADSL-LINE-MIB::adslLCSMib,,,,,,
.1.3.6.1.2.1.10.94.1.2,ADSL-LINE-MIB::adslTraps,,,,,,
.1.3.6.1.2.1.10.94.1.2.1,ADSL-LINE-MIB::adslAtucTraps,,,,,,
.1.3.6.1.2.1.10.94.1.2.1.0,ADSL-LINE-MIB::anonymous#7,,,,,,
.1.3.6.1.2.1.10.94.1.2.1.0.1,ADSL-LINE-MIB::adslAtucPerfLofsThreshTrap,,,,,,Loss of Framing 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.1.0.2,ADSL-LINE-MIB::adslAtucPerfLossThreshTrap,,,,,,Loss of Signal 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.1.0.3,ADSL-LINE-MIB::adslAtucPerfLprsThreshTrap,,,,,,Loss of Power 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.1.0.4,ADSL-LINE-MIB::adslAtucPerfESsThreshTrap,,,,,,Errored Second 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.1.0.5,ADSL-LINE-MIB::adslAtucRateChangeTrap,,,,,,The ATUCs transmit rate has changed (RADSL mode only)
.1.3.6.1.2.1.10.94.1.2.1.0.6,ADSL-LINE-MIB::adslAtucPerfLolsThreshTrap,,,,,,Loss of Link 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.1.0.7,ADSL-LINE-MIB::adslAtucInitFailureTrap,,,,,,ATUC initialization failed. See adslAtucCurrStatus for potential reasons.
.1.3.6.1.2.1.10.94.1.2.2,ADSL-LINE-MIB::adslAturTraps,,,,,,
.1.3.6.1.2.1.10.94.1.2.2.0,ADSL-LINE-MIB::anonymous#12,,,,,,
.1.3.6.1.2.1.10.94.1.2.2.0.1,ADSL-LINE-MIB::adslAturPerfLofsThreshTrap,,,,,,Loss of Framing 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.2.0.2,ADSL-LINE-MIB::adslAturPerfLossThreshTrap,,,,,,Loss of Signal 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.2.0.3,ADSL-LINE-MIB::adslAturPerfLprsThreshTrap,,,,,,Loss of Power 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.2.0.4,ADSL-LINE-MIB::adslAturPerfESsThreshTrap,,,,,,Errored Second 15-minute interval threshold reached.
.1.3.6.1.2.1.10.94.1.2.2.0.5,ADSL-LINE-MIB::adslAturRateChangeTrap,,,,,,The ATURs transmit rate has changed (RADSL mode only)
.1.3.6.1.2.1.10.94.1.3,ADSL-LINE-MIB::adslConformance,,,,,,
.1.3.6.1.2.1.10.94.1.3.1,ADSL-LINE-MIB::adslGroups,,,,,,
.1.3.6.1.2.1.10.94.1.3.1.1,ADSL-LINE-MIB::adslLineGroup,,,,,,A collection of objects providing configuration information about an ADSL Line.
.1.3.6.1.2.1.10.94.1.3.1.2,ADSL-LINE-MIB::adslPhysicalGroup,,,,,,A collection of objects providing physical configuration information of the ADSL Line.
.1.3.6.1.2.1.10.94.1.3.1.3,ADSL-LINE-MIB::adslChannelGroup,,,,,,A collection of objects providing configuration information about an ADSL channel.
.1.3.6.1.2.1.10.94.1.3.1.4,ADSL-LINE-MIB::adslAtucPhysPerfRawCounterGroup,,,,,,A collection of objects providing raw performance counts on an ADSL Line (ATU-C end).
.1.3.6.1.2.1.10.94.1.3.1.5,ADSL-LINE-MIB::adslAtucPhysPerfIntervalGroup,,,,,,A collection of objects providing current 15-minute, 1-day; and previous 1-day performance counts on ADSL Line (ATU-C end) .
.1.3.6.1.2.1.10.94.1.3.1.6,ADSL-LINE-MIB::adslAturPhysPerfRawCounterGroup,,,,,,A collection of objects providing raw performance counts on an ADSL Line (ATU-R end).
.1.3.6.1.2.1.10.94.1.3.1.7,ADSL-LINE-MIB::adslAturPhysPerfIntervalGroup,,,,,,A collection of objects providing current 15-minute, 1-day; and previous 1-day performance counts on ADSL Line (ATU-R end).
.1.3.6.1.2.1.10.94.1.3.1.8,ADSL-LINE-MIB::adslAtucChanPerformanceGroup,,,,,,A collection of objects providing channel block performance information on an ADSL channel (ATU-C end).
.1.3.6.1.2.1.10.94.1.3.1.9,ADSL-LINE-MIB::adslAturChanPerformanceGroup,,,,,,A collection of objects providing channel block performance information on an ADSL channel (ATU-C end).
.1.3.6.1.2.1.10.94.1.3.1.10,ADSL-LINE-MIB::adslLineConfProfileGroup,,,,,,A collection of objects providing provisioning information about an ADSL Line.
.1.3.6.1.2.1.10.94.1.3.1.11,ADSL-LINE-MIB::adslLineAlarmConfProfileGroup,,,,,,A collection of objects providing alarm provisioning information about an ADSL Line.
.1.3.6.1.2.1.10.94.1.3.1.12,ADSL-LINE-MIB::adslLineConfProfileControlGroup,,,,,,A collection of objects providing profile control for the ADSL system.
.1.3.6.1.2.1.10.94.1.3.1.13,ADSL-LINE-MIB::adslNotificationsGroup,,,,,,The collection of adsl notifications.
.1.3.6.1.2.1.10.94.1.3.1.14,ADSL-LINE-MIB::adslAturLineGroup,,,,,,A collection of objects providing configuration information about an ADSL Line on the ATU-R side.
.1.3.6.1.2.1.10.94.1.3.1.15,ADSL-LINE-MIB::adslAturPhysicalGroup,,,,,,A collection of objects providing physical configuration information of the ADSL Line on the ATU-R side.
.1.3.6.1.2.1.10.94.1.3.1.16,ADSL-LINE-MIB::adslAturChannelGroup,,,,,,A collection of objects providing configuration information about an ADSL channel on the ATU-R side.
.1.3.6.1.2.1.10.94.1.3.1.17,ADSL-LINE-MIB::adslAturAtucPhysPerfRawCounterGroup,,,,,,A collection of objects providing raw performance counts on an ADSL Line (ATU-C end) provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.18,ADSL-LINE-MIB::adslAturAtucPhysPerfIntervalGroup,,,,,,A collection of objects providing current 15-minute, 1-day; and previous 1-day performance counts on ADSL Line (ATU-C end) provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.19,ADSL-LINE-MIB::adslAturAturPhysPerfRawCounterGroup,,,,,,A collection of objects providing raw performance counts on an ADSL Line (ATU-R end) provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.20,ADSL-LINE-MIB::adslAturAturPhysPerfIntervalGroup,,,,,,A collection of objects providing current 15-minute, 1-day; and previous 1-day performance counts on ADSL Line (ATU-R end) provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.21,ADSL-LINE-MIB::adslAturAtucChanPerformanceGroup,,,,,,A collection of objects providing channel block performance information on an ADSL channel (ATU-C end) provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.22,ADSL-LINE-MIB::adslAturAturChanPerformanceGroup,,,,,,A collection of objects providing channel block performance information on an ADSL channel (ATU-R end) provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.23,ADSL-LINE-MIB::adslAturLineAlarmConfProfileGroup,,,,,,A collection of objects providing alarm information about an ADSL Line provided by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.24,ADSL-LINE-MIB::adslAturLineConfProfileControlGroup,,,,,,A collection of objects providing profile control for the ADSL system by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.1.25,ADSL-LINE-MIB::adslAturNotificationsGroup,,,,,,The collection of ADSL notifications implemented by the ATU-R agent.
.1.3.6.1.2.1.10.94.1.3.2,ADSL-LINE-MIB::adslCompliances,,,,,,
.1.3.6.1.2.1.10.94.1.3.2.1,ADSL-LINE-MIB::adslLineMibAtucCompliance,,,,,,The compliance statement for SNMP entities which manage ADSL ATU-C interfaces.
.1.3.6.1.2.1.10.94.1.3.2.2,ADSL-LINE-MIB::adslLineMibAturCompliance,,,,,,The compliance statement for SNMP entities which manage ADSL ATU-R interfaces.
.1.3.6.1.2.1.10.94.2,ADSL-TC-MIB::adsltcmib,,,,,,The MIB module which provides a ADSL Line Coding Textual Convention to be used by ADSL Lines.
.1.3.6.1.2.1.10.94.3,ADSL-LINE-EXT-MIB::adslExtMIB,,,,,,Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3440; see the RFC itself for full legal notices. This MIB Module is a supplement to the ADSL-LINE-MIB [RFC2662].
.1.3.6.1.2.1.10.94.3.1,ADSL-LINE-EXT-MIB::adslExtMibObjects,,,,,,
.1.3.6.1.2.1.10.94.3.1.17,ADSL-LINE-EXT-MIB::adslLineExtTable,,not-accessible,,current,,This table is an extension of RFC 2662. It contains ADSL line configuration and monitoring information. This includes the ADSL line's capabilities and actual ADSL transmission system.
.1.3.6.1.2.1.10.94.3.1.17.1,ADSL-LINE-EXT-MIB::adslLineExtEntry,,not-accessible,,current,,An entry extends the adslLineEntry defined in [RFC2662]. Each entry corresponds to an ADSL line.
.1.3.6.1.2.1.10.94.3.1.17.1.1,ADSL-LINE-EXT-MIB::adslLineTransAtucCap,BITS,read-only,,current,ansit1413(0):etsi(1):q9921PotsNonOverlapped(2):q9921PotsOverlapped(3):q9921IsdnNonOverlapped(4):q9921isdnOverlapped(5):q9921tcmIsdnNonOverlapped(6):q9921tcmIsdnOverlapped(7):q9922potsNonOverlapeed(8):q9922potsOverlapped(9):q9922tcmIsdnNonOverlapped(10):q9922tcmIsdnOverlapped(11):q9921tcmIsdnSymmetric(12),The transmission modes, represented by a bitmask that the ATU-C is capable of supporting. The modes available are limited by the design of the equipment.
.1.3.6.1.2.1.10.94.3.1.17.1.2,ADSL-LINE-EXT-MIB::adslLineTransAtucConfig,BITS,read-write,,current,ansit1413(0):etsi(1):q9921PotsNonOverlapped(2):q9921PotsOverlapped(3):q9921IsdnNonOverlapped(4):q9921isdnOverlapped(5):q9921tcmIsdnNonOverlapped(6):q9921tcmIsdnOverlapped(7):q9922potsNonOverlapeed(8):q9922potsOverlapped(9):q9922tcmIsdnNonOverlapped(10):q9922tcmIsdnOverlapped(11):q9921tcmIsdnSymmetric(12),The transmission modes, represented by a bitmask, currently enabled by the ATU-C. The manager can only set those modes that are supported by the ATU-C. An ATU-C's supported modes are provided by AdslLineTransAtucCap.
.1.3.6.1.2.1.10.94.3.1.17.1.3,ADSL-LINE-EXT-MIB::adslLineTransAtucActual,BITS,read-only,,current,ansit1413(0):etsi(1):q9921PotsNonOverlapped(2):q9921PotsOverlapped(3):q9921IsdnNonOverlapped(4):q9921isdnOverlapped(5):q9921tcmIsdnNonOverlapped(6):q9921tcmIsdnOverlapped(7):q9922potsNonOverlapeed(8):q9922potsOverlapped(9):q9922tcmIsdnNonOverlapped(10):q9922tcmIsdnOverlapped(11):q9921tcmIsdnSymmetric(12),The actual transmission mode of the ATU-C. During ADSL line initialization, the ADSL Transceiver Unit - Remote terminal end (ATU-R) will determine the mode used for the link. This value will be limited a single transmission mode that is a subset of those modes enabled by the ATU-C and denoted by adslLineTransAtucConfig. After an initialization has occurred, its mode is saved as the 'Current' mode and is persistence should the link go down. This object returns 0 (i.e. BITS with no mode bit set) if the mode is not known.
.1.3.6.1.2.1.10.94.3.1.17.1.4,ADSL-LINE-EXT-MIB::adslLineGlitePowerState,INTEGER,read-only,,current,none(1):l0(2):l1(3):l3(4),The value of this object specifies the power state of this interface. L0 is power on, L1 is power on but reduced and L3 is power off. Power state cannot be configured by an operator but it can be viewed via the ifOperStatus object for the managed ADSL interface. The value of the object ifOperStatus is set to down(2) if the ADSL interface is in power state L3 and is set to up(1) if the ADSL line interface is in power state L0 or L1. If the object adslLineTransAtucActual is set to a G.992.2 (G.Lite)-type transmission mode, the value of this object will be one of the valid power states: L0(2), L1(3), or L3(4). Otherwise, its value will be none(1).
.1.3.6.1.2.1.10.94.3.1.17.1.5,ADSL-LINE-EXT-MIB::adslLineConfProfileDualLite,OCTET,read-write,,current,,This object extends the definition an ADSL line and associated channels (when applicable) for cases when it is configured in dual mode, and operating in a G.Lite-type mode as denoted by adslLineTransAtucActual. Dual mode exists when the object, adslLineTransAtucConfig, is configured with one or more full-rate modes and one or more G.Lite modes simultaneously. When 'dynamic' profiles are implemented, the value of object is equal to the index of the applicable row in the ADSL Line Configuration Profile Table, AdslLineConfProfileTable defined in ADSL-MIB [RFC2662]. In the case when dual-mode has not been enabled, the value of the object will be equal to the value of the object adslLineConfProfile [RFC2662]. When `static' profiles are implemented, in much like the case of the object, adslLineConfProfileName [RFC2662], this object's value will need to algorithmically represent the characteristics of the line. In this case, the value of the line's ifIndex plus a value indicating the line mode type (e.g., G.Lite, Full-rate) will be used. Therefore, the profile's name is a string concatenating the ifIndex and one of the follow values: Full or Lite. This string will be fixed-length (i.e., 14) with leading zero(s). For example, the profile name for ifIndex that equals '15' and is a full rate line, it will be '0000000015Full'.
.1.3.6.1.2.1.10.94.3.1.18,ADSL-LINE-EXT-MIB::adslAtucPerfDataExtTable,,not-accessible,,current,,This table extends adslAtucPerfDataTable [RFC2662] with additional ADSL physical line counter information such as unavailable seconds-line and severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.18.1,ADSL-LINE-EXT-MIB::adslAtucPerfDataExtEntry,,not-accessible,,current,,An entry extends the adslAtucPerfDataEntry defined in [RFC2662]. Each entry corresponds to an ADSL line.
.1.3.6.1.2.1.10.94.3.1.18.1.1,ADSL-LINE-EXT-MIB::adslAtucPerfStatFastR,Counter32,read-only,,current,,The value of this object reports the count of the number of fast line bs since last agent reset.
.1.3.6.1.2.1.10.94.3.1.18.1.2,ADSL-LINE-EXT-MIB::adslAtucPerfStatFailedFastR,Counter32,read-only,,current,,The value of this object reports the count of the number of failed fast line retrains since last agent reset.
.1.3.6.1.2.1.10.94.3.1.18.1.3,ADSL-LINE-EXT-MIB::adslAtucPerfStatSesL,Counter32,read-only,,current,,The value of this object reports the count of the number of severely errored seconds-line since last agent reset.
.1.3.6.1.2.1.10.94.3.1.18.1.4,ADSL-LINE-EXT-MIB::adslAtucPerfStatUasL,Counter32,read-only,,current,,The value of this object reports the count of the number of unavailable seconds-line since last agent reset.
.1.3.6.1.2.1.10.94.3.1.18.1.5,ADSL-LINE-EXT-MIB::adslAtucPerfCurr15MinFastR,Gauge32,read-only,,current,,For the current 15-minute interval, adslAtucPerfCurr15MinFastR reports the current number of seconds during which there have been fast retrains.
.1.3.6.1.2.1.10.94.3.1.18.1.6,ADSL-LINE-EXT-MIB::adslAtucPerfCurr15MinFailedFastR,Gauge32,read-only,,current,,For the current 15-minute interval, adslAtucPerfCurr15MinFailedFastR reports the current number of seconds during which there have been failed fast retrains.
.1.3.6.1.2.1.10.94.3.1.18.1.7,ADSL-LINE-EXT-MIB::adslAtucPerfCurr15MinSesL,Gauge32,read-only,,current,,For the current 15-minute interval, adslAtucPerfCurr15MinSesL reports the current number of seconds during which there have been severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.18.1.8,ADSL-LINE-EXT-MIB::adslAtucPerfCurr15MinUasL,Gauge32,read-only,,current,,For the current 15-minute interval, adslAtucPerfCurr15MinUasL reports the current number of seconds during which there have been unavailable seconds-line.
.1.3.6.1.2.1.10.94.3.1.18.1.9,ADSL-LINE-EXT-MIB::adslAtucPerfCurr1DayFastR,Gauge32,read-only,,current,,For the current day as measured by adslAtucPerfCurr1DayTimeElapsed [RFC2662], adslAtucPerfCurr1DayFastR reports the number of seconds during which there have been fast retrains.
.1.3.6.1.2.1.10.94.3.1.18.1.10,ADSL-LINE-EXT-MIB::adslAtucPerfCurr1DayFailedFastR,Gauge32,read-only,,current,,For the current day as measured by adslAtucPerfCurr1DayTimeElapsed [RFC2662], adslAtucPerfCurr1DayFailedFastR reports the number of seconds during which there have been failed fast retrains.
.1.3.6.1.2.1.10.94.3.1.18.1.11,ADSL-LINE-EXT-MIB::adslAtucPerfCurr1DaySesL,Gauge32,read-only,,current,,For the current day as measured by adslAtucPerfCurr1DayTimeElapsed [RFC2662], adslAtucPerfCurr1DaySesL reports the number of seconds during which there have been severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.18.1.12,ADSL-LINE-EXT-MIB::adslAtucPerfCurr1DayUasL,Gauge32,read-only,,current,,For the current day as measured by adslAtucPerfCurr1DayTimeElapsed [RFC2662], adslAtucPerfCurr1DayUasL reports the number of seconds during which there have been unavailable seconds-line.
.1.3.6.1.2.1.10.94.3.1.18.1.13,ADSL-LINE-EXT-MIB::adslAtucPerfPrev1DayFastR,Gauge32,read-only,,current,,For the previous day, adslAtucPerfPrev1DayFastR reports the number of seconds during which there were fast retrains.
.1.3.6.1.2.1.10.94.3.1.18.1.14,ADSL-LINE-EXT-MIB::adslAtucPerfPrev1DayFailedFastR,Gauge32,read-only,,current,,For the previous day, adslAtucPerfPrev1DayFailedFastR reports the number of seconds during which there were failed fast retrains.
.1.3.6.1.2.1.10.94.3.1.18.1.15,ADSL-LINE-EXT-MIB::adslAtucPerfPrev1DaySesL,Gauge32,read-only,,current,,For the previous day, adslAtucPerfPrev1DaySesL reports the number of seconds during which there were severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.18.1.16,ADSL-LINE-EXT-MIB::adslAtucPerfPrev1DayUasL,Gauge32,read-only,,current,,For the previous day, adslAtucPerfPrev1DayUasL reports the number of seconds during which there were unavailable seconds-line.
.1.3.6.1.2.1.10.94.3.1.19,ADSL-LINE-EXT-MIB::adslAtucIntervalExtTable,,not-accessible,,current,,This table provides one row for each ATU-C performance data collection interval for ADSL physical interfaces whose IfEntries' ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.3.1.19.1,ADSL-LINE-EXT-MIB::adslAtucIntervalExtEntry,,not-accessible,,current,,An entry in the adslAtucIntervalExtTable.
.1.3.6.1.2.1.10.94.3.1.19.1.1,ADSL-LINE-EXT-MIB::adslAtucIntervalFastR,Gauge32,read-only,,current,,For the current interval, adslAtucIntervalFastR reports the current number of seconds during which there have been fast retrains.
.1.3.6.1.2.1.10.94.3.1.19.1.2,ADSL-LINE-EXT-MIB::adslAtucIntervalFailedFastR,Gauge32,read-only,,current,,For the each interval, adslAtucIntervalFailedFastR reports the number of seconds during which there have been failed fast retrains.
.1.3.6.1.2.1.10.94.3.1.19.1.3,ADSL-LINE-EXT-MIB::adslAtucIntervalSesL,Gauge32,read-only,,current,,For the each interval, adslAtucIntervalSesL reports the number of seconds during which there have been severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.19.1.4,ADSL-LINE-EXT-MIB::adslAtucIntervalUasL,Gauge32,read-only,,current,,For the each interval, adslAtucIntervalUasL reports the number of seconds during which there have been unavailable seconds-line.
.1.3.6.1.2.1.10.94.3.1.20,ADSL-LINE-EXT-MIB::adslAturPerfDataExtTable,,not-accessible,,current,,This table contains ADSL physical line counters not defined in the adslAturPerfDataTable from the ADSL-LINE-MIB [RFC2662].
.1.3.6.1.2.1.10.94.3.1.20.1,ADSL-LINE-EXT-MIB::adslAturPerfDataExtEntry,,not-accessible,,current,,An entry extends the adslAturPerfDataEntry defined in [RFC2662]. Each entry corresponds to an ADSL line.
.1.3.6.1.2.1.10.94.3.1.20.1.1,ADSL-LINE-EXT-MIB::adslAturPerfStatSesL,Counter32,read-only,,current,,The value of this object reports the count of severely errored second-line since the last agent reset.
.1.3.6.1.2.1.10.94.3.1.20.1.2,ADSL-LINE-EXT-MIB::adslAturPerfStatUasL,Counter32,read-only,,current,,The value of this object reports the count of unavailable seconds-line since the last agent reset.
.1.3.6.1.2.1.10.94.3.1.20.1.3,ADSL-LINE-EXT-MIB::adslAturPerfCurr15MinSesL,Gauge32,read-only,,current,,For the current 15-minute interval, adslAturPerfCurr15MinSesL reports the current number of seconds during which there have been severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.20.1.4,ADSL-LINE-EXT-MIB::adslAturPerfCurr15MinUasL,Gauge32,read-only,,current,,For the current 15-minute interval, adslAturPerfCurr15MinUasL reports the current number of seconds during which there have been available seconds-line.
.1.3.6.1.2.1.10.94.3.1.20.1.5,ADSL-LINE-EXT-MIB::adslAturPerfCurr1DaySesL,Gauge32,read-only,,current,,For the current day as measured by adslAturPerfCurr1DayTimeElapsed [RFC2662], adslAturPerfCurr1DaySesL reports the number of seconds during which there have been severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.20.1.6,ADSL-LINE-EXT-MIB::adslAturPerfCurr1DayUasL,Gauge32,read-only,,current,,For the current day as measured by adslAturPerfCurr1DayTimeElapsed [RFC2662], adslAturPerfCurr1DayUasL reports the number of seconds during which there have been unavailable seconds-line.
.1.3.6.1.2.1.10.94.3.1.20.1.7,ADSL-LINE-EXT-MIB::adslAturPerfPrev1DaySesL,Gauge32,read-only,,current,,For the previous day, adslAturPerfPrev1DaySesL reports the number of seconds during which there were severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.20.1.8,ADSL-LINE-EXT-MIB::adslAturPerfPrev1DayUasL,Gauge32,read-only,,current,,For the previous day, adslAturPerfPrev1DayUasL reports the number of seconds during which there were severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.21,ADSL-LINE-EXT-MIB::adslAturIntervalExtTable,,not-accessible,,current,,This table provides one row for each ATU-R performance data collection interval for ADSL physical interfaces whose IfEntries' ifType is equal to adsl(94).
.1.3.6.1.2.1.10.94.3.1.21.1,ADSL-LINE-EXT-MIB::adslAturIntervalExtEntry,,not-accessible,,current,,An entry in the adslAturIntervalExtTable.
.1.3.6.1.2.1.10.94.3.1.21.1.1,ADSL-LINE-EXT-MIB::adslAturIntervalSesL,Gauge32,read-only,,current,,For the each interval, adslAturIntervalSesL reports the number of seconds during which there have been severely errored seconds-line.
.1.3.6.1.2.1.10.94.3.1.21.1.2,ADSL-LINE-EXT-MIB::adslAturIntervalUasL,Gauge32,read-only,,current,,For the each interval, adslAturIntervalUasL reports the number of seconds during which there have been unavailable seconds-line.
.1.3.6.1.2.1.10.94.3.1.22,ADSL-LINE-EXT-MIB::adslConfProfileExtTable,,not-accessible,,current,,The adslConfProfileExtTable extends the ADSL line profile configuration information in the adslLineConfProfileTable from the ADSL-LINE-MIB [RFC2662] by adding the ability to configure the ADSL physical line mode.
.1.3.6.1.2.1.10.94.3.1.22.1,ADSL-LINE-EXT-MIB::adslConfProfileExtEntry,,not-accessible,,current,,An entry extends the adslLineConfProfileEntry defined in [RFC2662]. Each entry corresponds to an ADSL line profile.
.1.3.6.1.2.1.10.94.3.1.22.1.1,ADSL-LINE-EXT-MIB::adslConfProfileLineType,INTEGER,read-create,,current,noChannel(1):fastOnly(2):interleavedOnly(3):fastOrInterleaved(4):fastAndInterleaved(5),This object is used to configure the ADSL physical line mode. It has following valid values: noChannel(1), when no channels exist. fastOnly(2), when only fast channel exists. interleavedOnly(3), when only interleaved channel exist. fastOrInterleaved(4), when either fast or interleaved channels can exist, but only one at any time. fastAndInterleaved(5), when both the fast channel and the interleaved channel exist. In the case when no value has been set, the default Value is noChannel(1). 
.1.3.6.1.2.1.10.94.3.1.23,ADSL-LINE-EXT-MIB::adslAlarmConfProfileExtTable,,not-accessible,,current,,This table extends the adslLineAlarmConfProfileTable and provides threshold parameters for all the counters defined in this MIB module.
.1.3.6.1.2.1.10.94.3.1.23.1,ADSL-LINE-EXT-MIB::adslAlarmConfProfileExtEntry,,not-accessible,,current,,An entry extends the adslLineAlarmConfProfileTable defined in [RFC2662]. Each entry corresponds to an ADSL alarm profile.
.1.3.6.1.2.1.10.94.3.1.23.1.1,ADSL-LINE-EXT-MIB::adslAtucThreshold15MinFailedFastR,Integer32,read-create,,current,,The first time the value of the corresponding instance of adslAtucPerfCurr15MinFailedFastR reaches or exceeds this value within a given 15-minute performance data collection period, an adslAtucFailedFastRThreshTrap notification will be generated. The value '0' will disable the notification. The default value of this object is '0'.
.1.3.6.1.2.1.10.94.3.1.23.1.2,ADSL-LINE-EXT-MIB::adslAtucThreshold15MinSesL,Integer32,read-create,,current,,The first time the value of the corresponding instance of adslAtucPerf15MinSesL reaches or exceeds this value within a given 15-minute performance data collection period, an adslAtucSesLThreshTrap notification will be generated. The value '0' will disable the notification. The default value of this object is '0'.
.1.3.6.1.2.1.10.94.3.1.23.1.3,ADSL-LINE-EXT-MIB::adslAtucThreshold15MinUasL,Integer32,read-create,,current,,The first time the value of the corresponding instance of adslAtucPerf15MinUasL reaches or exceeds this value within a given 15-minute performance data collection period, an adslAtucUasLThreshTrap notification will be generated. The value '0' will disable the notification. The default value of this object is '0'.
.1.3.6.1.2.1.10.94.3.1.23.1.4,ADSL-LINE-EXT-MIB::adslAturThreshold15MinSesL,Integer32,read-create,,current,,The first time the value of the corresponding instance of adslAturPerf15MinSesL reaches or exceeds this value within a given 15-minute performance data collection period, an adslAturSesLThreshTrap notification will be generated. The value '0' will disable the notification. The default value of this object is '0'.
.1.3.6.1.2.1.10.94.3.1.23.1.5,ADSL-LINE-EXT-MIB::adslAturThreshold15MinUasL,Integer32,read-create,,current,,The first time the value of the corresponding instance of adslAturPerf15MinUasL reaches or exceeds this value within a given 15-minute performance data collection period, an adslAturUasLThreshTrap notification will be generated. The value '0' will disable the notification. The default value of this object is '0'.
.1.3.6.1.2.1.10.94.3.1.24,ADSL-LINE-EXT-MIB::adslExtTraps,,,,,,
.1.3.6.1.2.1.10.94.3.1.24.1,ADSL-LINE-EXT-MIB::adslExtAtucTraps,,,,,,
.1.3.6.1.2.1.10.94.3.1.24.1.0,ADSL-LINE-EXT-MIB::adslExtAtucTrapsPrefix,,,,,,
.1.3.6.1.2.1.10.94.3.1.24.1.0.1,ADSL-LINE-EXT-MIB::adslAtucFailedFastRThreshTrap,,,,,,Failed Fast Retrains 15-minute threshold reached.
.1.3.6.1.2.1.10.94.3.1.24.1.0.2,ADSL-LINE-EXT-MIB::adslAtucSesLThreshTrap,,,,,,Severely errored seconds-line 15-minute threshold reached.
.1.3.6.1.2.1.10.94.3.1.24.1.0.3,ADSL-LINE-EXT-MIB::adslAtucUasLThreshTrap,,,,,,Unavailable seconds-line 15-minute threshold reached.
.1.3.6.1.2.1.10.94.3.1.24.2,ADSL-LINE-EXT-MIB::adslExtAturTraps,,,,,,
.1.3.6.1.2.1.10.94.3.1.24.2.0,ADSL-LINE-EXT-MIB::adslExtAturTrapsPrefix,,,,,,
.1.3.6.1.2.1.10.94.3.1.24.2.0.1,ADSL-LINE-EXT-MIB::adslAturSesLThreshTrap,,,,,,Severely errored seconds-line 15-minute threshold reached.
.1.3.6.1.2.1.10.94.3.1.24.2.0.2,ADSL-LINE-EXT-MIB::adslAturUasLThreshTrap,,,,,,Unavailable seconds-line 15-minute threshold reached.
.1.3.6.1.2.1.10.94.3.2,ADSL-LINE-EXT-MIB::adslExtConformance,,,,,,
.1.3.6.1.2.1.10.94.3.2.1,ADSL-LINE-EXT-MIB::adslExtGroups,,,,,,
.1.3.6.1.2.1.10.94.3.2.1.1,ADSL-LINE-EXT-MIB::adslExtLineGroup,,,,,,A collection of objects providing extended configuration information about an ADSL Line.
.1.3.6.1.2.1.10.94.3.2.1.2,ADSL-LINE-EXT-MIB::adslExtAtucPhysPerfCounterGroup,,,,,,A collection of objects providing raw performance counts on an ADSL Line (ATU-C end).
.1.3.6.1.2.1.10.94.3.2.1.3,ADSL-LINE-EXT-MIB::adslExtAturPhysPerfCounterGroup,,,,,,A collection of objects providing raw performance counts on an ADSL Line (ATU-C end).
.1.3.6.1.2.1.10.94.3.2.1.4,ADSL-LINE-EXT-MIB::adslExtLineConfProfileControlGroup,,,,,,A collection of objects providing profile control for the ADSL system.
.1.3.6.1.2.1.10.94.3.2.1.5,ADSL-LINE-EXT-MIB::adslExtLineAlarmConfProfileGroup,,,,,,A collection of objects providing alarm profile control for the ADSL system.
.1.3.6.1.2.1.10.94.3.2.1.6,ADSL-LINE-EXT-MIB::adslExtNotificationsGroup,,,,,,The collection of ADSL extension notifications.
.1.3.6.1.2.1.10.94.3.2.2,ADSL-LINE-EXT-MIB::adslExtCompliances,,,,,,
.1.3.6.1.2.1.10.94.3.2.2.1,ADSL-LINE-EXT-MIB::adslExtLineMibAtucCompliance,,,,,,The compliance statement for SNMP entities which represent ADSL ATU-C interfaces.
.1.3.6.1.2.1.10.95,L2TP-MIB::l2tp,,,,,,The MIB module that describes managed objects of general use by the Layer Two Transport Protocol.
.1.3.6.1.2.1.10.95.0,L2TP-MIB::l2tpNotifications,,,,,,
.1.3.6.1.2.1.10.95.0.1,L2TP-MIB::l2tpTunnelAuthFailure,,,,,,A l2tpTunnelAuthFailure trap signifies that an attempt to establish a tunnel to a remote peer has failed authentication.
.1.3.6.1.2.1.10.95.1,L2TP-MIB::l2tpObjects,,,,,,
.1.3.6.1.2.1.10.95.1.1,L2TP-MIB::l2tpScalar,,,,,,
.1.3.6.1.2.1.10.95.1.1.1,L2TP-MIB::l2tpConfig,,,,,,
.1.3.6.1.2.1.10.95.1.1.1.1,L2TP-MIB::l2tpAdminState,INTEGER,read-write,,current,enabled(1):disabled(2),This object defines the administrative state of the L2TP protocol. Setting this object to 'disabled' causes all tunnels to be immediately disconnected and no further tunnels to be either initiated or accepted. The value of this object must be maintained in non-volatile memory.
.1.3.6.1.2.1.10.95.1.1.1.2,L2TP-MIB::l2tpDrainTunnels,INTEGER,read-write,,current,true(1):false(2),Setting this object to 'true' will prevent any new tunnels and/or sessions to be either initiated or accepted but does NOT disconnect any active tunnels/sessions. Setting this object to true(1) causes all domains and their respective tunnels to transition to the draining state. Note that when this occurs the 'xxxDraining' status objects of the domains and their tunnels should reflect that they are 'draining'. Setting this object has no affect on the domains or their tunnels 'xxxDrainTunnels' configuration objects. To cancel a drain this object should be set to false(2). The object l2tpDrainingTunnels reflects the current L2TP draining state. The value of this object must be maintained in non-volatile memory.
.1.3.6.1.2.1.10.95.1.1.2,L2TP-MIB::l2tpStats,,,,,,
.1.3.6.1.2.1.10.95.1.1.2.1,L2TP-MIB::l2tpProtocolVersions,OCTET,read-only,,current,,Vector of supported L2TP protocol version and revision numbers. Supported versions are identified via a two octet pairing where the first octet indicates the version and the second octet contains the revision.
.1.3.6.1.2.1.10.95.1.1.2.2,L2TP-MIB::l2tpVendorName,OCTET,read-only,,current,,This object identifies the Vendor name of the L2TP protocol stack.
.1.3.6.1.2.1.10.95.1.1.2.3,L2TP-MIB::l2tpFirmwareRev,Integer32,read-only,,current,,This object defines the firmware revision for the L2TP protocol stack.
.1.3.6.1.2.1.10.95.1.1.2.4,L2TP-MIB::l2tpDrainingTunnels,INTEGER,read-only,,current,true(1):false(2),This object indicates if the local L2TP is draining off sessions from all tunnels.
.1.3.6.1.2.1.10.95.1.2,L2TP-MIB::l2tpDomainConfigTable,,not-accessible,,current,,The L2TP Domain configuration table. This table contains objects that can be used to configure the operational characteristics of a tunnel domain. There is a 1-1 correspondence between conceptual rows of this table and conceptual rows of the l2tpDomainStatsTable.
.1.3.6.1.2.1.10.95.1.2.1,L2TP-MIB::l2tpDomainConfigEntry,,not-accessible,l2tpDomainConfigId,current,,An L2TP Domain configuration entry. An entry in this table may correspond to a single endpoint or a group of tunnel endpoints.
.1.3.6.1.2.1.10.95.1.2.1.1,L2TP-MIB::l2tpDomainConfigId,OCTET,not-accessible,,current,,The identifier, usually in the form of a Domain Name (full or partial), describing a single tunnel endpoint or a domain of tunnel endpoints. This is typically used as a 'handle' to identify the tunnel configuration requirements for both incoming and outgoing tunnel connection attempts. Both the LAC and LNS could use information provided in the Host Name AVP attribute however the tunnel initiator could use other means not specified to identify the domain's tunnel configuration requirements. For example; three rows in this table have l2tpDomainConfigId values of 'lac1.isp.com', 'isp.com' and 'com'. A tunnel endpoint then identifies itself as 'lac1.isp.com' which would match the 'lac1.isp.com' entry in this table. A second tunnel endpoint then identifies itself as 'lac2.isp.com'. This endpoint is then associated with the 'isp.com' entry of this table.
.1.3.6.1.2.1.10.95.1.2.1.2,L2TP-MIB::l2tpDomainConfigAdminState,INTEGER,read-create,,current,enabled(1):disabled(2),This object defines the administrative state of this tunnel domain. Setting this object to disabled(2) causes all tunnels to be immediately disconnected and no further tunnels to be either initiated or accepted. Note that all columnar objects corresponding to this conceptual row cannot be modified when the administrative state is enabled EXCEPT those objects which specifically state otherwise.
.1.3.6.1.2.1.10.95.1.2.1.3,L2TP-MIB::l2tpDomainConfigDrainTunnels,INTEGER,read-create,,current,true(1):false(2),Setting this object to 'true' will prevent any new tunnels and/or sessions from being either initiated or accepted but does NOT disconnect any active tunnels/sessions for this tunnel domain. Setting this object to true(1) causes all tunnels within this domain to transition to the draining state. Note that when this occurs the l2tpTunnelStatsDrainingTunnel status objects of all of this domain's tunnels should reflect that they are 'draining'. Setting this object has no effect on this domain's associated tunnels l2tpTunnelConfigDrainTunnel configuration objects. To cancel a drain this object should be set to false(2). Setting this object to false(2) when the L2TP object l2tpDrainTunnels is true(1) has no affect, all domains and their tunnels will continue to drain.
.1.3.6.1.2.1.10.95.1.2.1.4,L2TP-MIB::l2tpDomainConfigAuth,INTEGER,read-create,,current,none(1):simple(2):challenge(3),This object describes how tunnel peers belonging to this domain are to be authenticated. The value simple(2) indicates that peers are authenticated simply by their host name as described in the Host Name AVP. The value challenge(3) indicates that all peers are challenged to prove their identification. This mechanism is described in the L2TP protocol.
.1.3.6.1.2.1.10.95.1.2.1.5,L2TP-MIB::l2tpDomainConfigSecret,OCTET,read-create,,current,,This object is used to configure the shared secret used during the tunnel authentication phase of tunnel establishment. This object MUST be accessible only via requests using both authentication and privacy. The agent MUST report an empty string in response to get, get-next and get-bulk requests.
.1.3.6.1.2.1.10.95.1.2.1.6,L2TP-MIB::l2tpDomainConfigTunnelSecurity,INTEGER,read-create,,current,none(1):other(2):ipSec(3),This object defines whether this tunnel domain requires that all tunnels are to be secured. The value of ipsec(3) indicates that all tunnel packets, control and session, have IP Security headers. The type of IP Security headers (AH, ESP etc) and how they are further described is outside the scope of this document.
.1.3.6.1.2.1.10.95.1.2.1.7,L2TP-MIB::l2tpDomainConfigTunnelHelloInt,Integer32,read-create,,current,,This object defines the interval in which Hello (or keep-alive) packets are to be sent by local peers belonging to this tunnel domain. The value zero effectively disables the sending of Hello packets. This object may be modified when the administrative state is enabled for this conceptual row.
.1.3.6.1.2.1.10.95.1.2.1.8,L2TP-MIB::l2tpDomainConfigTunnelIdleTO,Integer32,read-create,,current,,This object defines the period of time that an established tunnel belonging to this tunnel domain with no active sessions will wait before disconnecting the tunnel. A value of zero indicates that the tunnel will disconnect immediately after the last session disconnects. A value of -1 leaves the tunnel up indefinitely. This object may be modified when the administrative state is enabled for this conceptual row.
.1.3.6.1.2.1.10.95.1.2.1.9,L2TP-MIB::l2tpDomainConfigControlRWS,Integer32,read-create,,current,,This object defines the control channel receive window size for tunnels belonging to this domain. It specifies the maximum number of packets the tunnel peer belonging to this domain can send without waiting for an acknowledgement from this peer.
.1.3.6.1.2.1.10.95.1.2.1.10,L2TP-MIB::l2tpDomainConfigControlMaxRetx,Integer32,read-create,,current,,This object defines the maximum number of retransmissions which the L2TP stack will attempt for tunnels belonging to this domain before assuming that the peer is no longer responding.
.1.3.6.1.2.1.10.95.1.2.1.11,L2TP-MIB::l2tpDomainConfigControlMaxRetxTO,Integer32,read-create,,current,,This object defines the maximum retransmission timeout interval which the L2TP stack will wait for tunnels belonging to this domain before retransmitting a control packet that has not been acknowledged.
.1.3.6.1.2.1.10.95.1.2.1.12,L2TP-MIB::l2tpDomainConfigPayloadSeq,INTEGER,read-create,,current,onDemand(1):never(2):always(3),This object determines whether or not session payload packets will be requested to be sent with sequence numbers from tunnel peers belonging to this domain. The value onDemand(1) allows the L2TP implementation to initiate payload sequencing when necessary based on local information (e.g: during LCP/NCP negotiations or for CCP). The value never(2) indicates that L2TP will never initiate sequencing but will do sequencing if asked. The value always(3) indicates that L2TP will send the Sequencing Required AVP during session establishment.
.1.3.6.1.2.1.10.95.1.2.1.13,L2TP-MIB::l2tpDomainConfigReassemblyTO,Integer32,read-create,,current,,This object defines the number of milliseconds that local peers of this tunnel domain will wait before processing payload packets that were received out of sequence (which are waiting for the packet(s) to put them in sequence). A low value increases the chance of delayed packets to be discarded (which MAY cause the PPP decompression engine to reset) while a high value may cause more queuing and possibly degrade throughput if packets are truly lost. The default value for this object is zero which will result in all delayed packets being lost.
.1.3.6.1.2.1.10.95.1.2.1.14,L2TP-MIB::l2tpDomainConfigProxyPPPAuth,INTEGER,read-create,,current,true(1):false(2),This object is used to configure the sending or acceptance of the PPP Proxy Authentication AVP's on the LAC or LNS.
.1.3.6.1.2.1.10.95.1.2.1.15,L2TP-MIB::l2tpDomainConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' must allow write-access at a minimum to: - l2tpDomainConfigAdminState and l2tpDomainConfigDrainTunnels at all times - l2tpDomainConfigSecret if l2tpDomainConfigAuth has been configured as 'challenge' It is an implementation issue to decide if a SET for a readOnly or permanent row is accepted at all. In some contexts this may make sense, in others it may not. If a SET for a readOnly or permanent row is not accepted at all, then a 'wrongValue' error must be returned.
.1.3.6.1.2.1.10.95.1.2.1.16,L2TP-MIB::l2tpDomainConfigStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this Domain entry. Columnar objects corresponding to this conceptual row may be modified according to their description clauses when this RowStatus object is 'active'.
.1.3.6.1.2.1.10.95.1.3,L2TP-MIB::l2tpDomainStatsTable,,not-accessible,,current,,The L2TP Domain Status and Statistics table. This table contains objects that can be used to describe the current status and statistics of a tunnel domain. There is a 1-1 correspondence between conceptual rows of this table and conceptual rows of the l2tpDomainConfigTable.
.1.3.6.1.2.1.10.95.1.3.1,L2TP-MIB::l2tpDomainStatsEntry,,not-accessible,,current,,An L2TP Domain Stats entry. An entry in this table may correspond to a single endpoint or a group of tunnel endpoints.
.1.3.6.1.2.1.10.95.1.3.1.1,L2TP-MIB::l2tpDomainStatsTotalTunnels,Counter32,read-only,,current,,This object returns the total number of tunnels that have successfully reached the established state for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.2,L2TP-MIB::l2tpDomainStatsFailedTunnels,Counter32,read-only,,current,,This object returns the number of tunnels that failed (eg: connection timeout, unsupported or malformed AVP's etc) to reach the established state for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.3,L2TP-MIB::l2tpDomainStatsFailedAuths,Counter32,read-only,,current,,This object returns the number of failed tunnel connection attempts for this domain because the tunnel peer failed authentication.
.1.3.6.1.2.1.10.95.1.3.1.4,L2TP-MIB::l2tpDomainStatsActiveTunnels,Gauge32,read-only,,current,,This object returns the number of tunnels that are currently active for this domain.
.1.3.6.1.2.1.10.95.1.3.1.5,L2TP-MIB::l2tpDomainStatsTotalSessions,Counter32,read-only,,current,,This object returns the total number of sessions that have successfully reached the established state for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.6,L2TP-MIB::l2tpDomainStatsFailedSessions,Counter32,read-only,,current,,This object returns the number of sessions that failed (eg: connection timeout, unsupported or malformed AVP's etc) to reach the established state for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.7,L2TP-MIB::l2tpDomainStatsActiveSessions,Gauge32,read-only,,current,,This object returns the number of sessions that are currently active for this domain.
.1.3.6.1.2.1.10.95.1.3.1.8,L2TP-MIB::l2tpDomainStatsDrainingTunnels,INTEGER,read-only,,current,true(1):false(2),This object indicates if this domain is draining off sessions from all tunnels.
.1.3.6.1.2.1.10.95.1.3.1.9,L2TP-MIB::l2tpDomainStatsControlRxOctets,Counter32,read-only,,current,,This object returns the number of control channel octets received for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.10,L2TP-MIB::l2tpDomainStatsControlRxPkts,Counter32,read-only,,current,,This object returns the number of control packets received for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.11,L2TP-MIB::l2tpDomainStatsControlTxOctets,Counter32,read-only,,current,,This object returns the number of control channel octets that were transmitted to tunnel endpoints for this domain.
.1.3.6.1.2.1.10.95.1.3.1.12,L2TP-MIB::l2tpDomainStatsControlTxPkts,Counter32,read-only,,current,,This object returns the number of control packets that were transmitted to tunnel endpoints for this domain.
.1.3.6.1.2.1.10.95.1.3.1.13,L2TP-MIB::l2tpDomainStatsPayloadRxOctets,Counter32,read-only,,current,,This object returns the number of payload channel octets that were received for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.14,L2TP-MIB::l2tpDomainStatsPayloadRxPkts,Counter32,read-only,,current,,This object returns the number of payload packets that were received for this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.15,L2TP-MIB::l2tpDomainStatsPayloadRxDiscs,Counter32,read-only,,current,,This object returns the number of received payload packets that were discarded by this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.16,L2TP-MIB::l2tpDomainStatsPayloadTxOctets,Counter32,read-only,,current,,This object returns the number of payload channel octets that were transmitted to tunnel peers within this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.17,L2TP-MIB::l2tpDomainStatsPayloadTxPkts,Counter32,read-only,,current,,This object returns the number of payload packets that were transmitted to tunnel peers within this tunnel domain.
.1.3.6.1.2.1.10.95.1.3.1.18,L2TP-MIB::l2tpDomainStatsControlHCRxOctets,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsControlRxOctets.
.1.3.6.1.2.1.10.95.1.3.1.19,L2TP-MIB::l2tpDomainStatsControlHCRxPkts,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsControlRxPkts.
.1.3.6.1.2.1.10.95.1.3.1.20,L2TP-MIB::l2tpDomainStatsControlHCTxOctets,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsControlTxOctets.
.1.3.6.1.2.1.10.95.1.3.1.21,L2TP-MIB::l2tpDomainStatsControlHCTxPkts,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsControlTxPkts.
.1.3.6.1.2.1.10.95.1.3.1.22,L2TP-MIB::l2tpDomainStatsPayloadHCRxOctets,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsPayloadRxOctets.
.1.3.6.1.2.1.10.95.1.3.1.23,L2TP-MIB::l2tpDomainStatsPayloadHCRxPkts,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsPayloadRxPkts.
.1.3.6.1.2.1.10.95.1.3.1.24,L2TP-MIB::l2tpDomainStatsPayloadHCRxDiscs,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsPayloadRxDiscs.
.1.3.6.1.2.1.10.95.1.3.1.25,L2TP-MIB::l2tpDomainStatsPayloadHCTxOctets,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsPayloadTxOctets.
.1.3.6.1.2.1.10.95.1.3.1.26,L2TP-MIB::l2tpDomainStatsPayloadHCTxPkts,Counter64,read-only,,current,,This object is a 64-bit version of l2tpDomainStatsPayloadTxPkts.
.1.3.6.1.2.1.10.95.1.4,L2TP-MIB::l2tpTunnelConfigTable,,not-accessible,,current,,The L2TP tunnel configuration table. This table contains objects that can be used to (re)configure the operational characteristics of a single L2TP tunnel. There is a 1-1 correspondence between conceptual rows of this table and conceptual rows of the l2tpTunnelStatsTable. Entries in this table have the same persistency characteristics as that of the tunnelConfigTable.
.1.3.6.1.2.1.10.95.1.4.1,L2TP-MIB::l2tpTunnelConfigEntry,,not-accessible,l2tpTunnelConfigIfIndex,current,,A L2TP tunnel interface configuration entry. Entries in this table come and go as a result of protocol interactions or on management operations. The latter occurs when a row is instantiated in the tunnelConfigTable row and the encapsulation method is 'l2tp'.
.1.3.6.1.2.1.10.95.1.4.1.1,L2TP-MIB::l2tpTunnelConfigIfIndex,Integer32,not-accessible,,current,,This value for this object is equal to the value of ifIndex of the Interfaces MIB for tunnel interfaces of type L2TP.
.1.3.6.1.2.1.10.95.1.4.1.2,L2TP-MIB::l2tpTunnelConfigDomainId,OCTET,read-write,,current,,The tunnel domain that this tunnel belongs to. A LNS tunnel endpoint will typically inherit this value from the endpoint domain table. A LAC may be provided with this information during tunnel setup. When a zero length string is returned this tunnel does not belong belong to any particular domain.
.1.3.6.1.2.1.10.95.1.4.1.3,L2TP-MIB::l2tpTunnelConfigAuth,INTEGER,read-write,,current,none(1):simple(2):challenge(3),This object describes how L2TP tunnel peers are to be authenticated. The value 'simple' indicates that peers are authenticated simply by their host name as described in the Host Name AVP. The value 'challenge' indicates that all peers are challenged to prove their identification. This mechanism is described in the L2TP protocol. This object cannot be modified when the tunnel is in a connecting or connected state.
.1.3.6.1.2.1.10.95.1.4.1.4,L2TP-MIB::l2tpTunnelConfigSecret,OCTET,read-write,,current,,This object is used to configure the shared secret used during the tunnel authentication phase of tunnel establishment. This object cannot be modified when the tunnel is in a connecting or connected state. This object MUST be accessible only via requests using both authentication and privacy. The agent MUST report an empty string in response to get, get-next and get-bulk requests.
.1.3.6.1.2.1.10.95.1.4.1.5,L2TP-MIB::l2tpTunnelConfigSecurity,INTEGER,read-write,,current,none(1):other(2):ipsec(3),This object defines whether this tunnel is to be secured. The value of 'ipSec' indicates that all tunnel packets, control and session, have IP Security headers. The type of IP Security headers (AH, ESP etc) and how they are further described is outside the scope of this document. This object cannot be modified when the tunnel is in a connecting or connected state.
.1.3.6.1.2.1.10.95.1.4.1.6,L2TP-MIB::l2tpTunnelConfigHelloInterval,Integer32,read-write,,current,,This object defines the interval in which Hello (or keep-alive) packets are to be sent to the tunnel peer. The value zero effectively disables the sending of Hello packets. Modifications to this object have immediate effect.
.1.3.6.1.2.1.10.95.1.4.1.7,L2TP-MIB::l2tpTunnelConfigIdleTimeout,Integer32,read-write,,current,,This object defines the period of time that an established tunnel with no sessions will wait before disconnecting the tunnel. A value of zero indicates that the tunnel will disconnect immediately after the last session disconnects. A value of -1 leaves the tunnel up indefinitely. Modifications to this object have immediate effect.
.1.3.6.1.2.1.10.95.1.4.1.8,L2TP-MIB::l2tpTunnelConfigControlRWS,Integer32,read-write,,current,,This object defines the control channel receive window size. It specifies the maximum number of packets the tunnel peer can send without waiting for an acknowledgement from this peer. This object cannot be modified when the tunnel is in a con- necting or connected state.
.1.3.6.1.2.1.10.95.1.4.1.9,L2TP-MIB::l2tpTunnelConfigControlMaxRetx,Integer32,read-write,,current,,This object defines the number of retransmissions which the tunnel will attempt before assuming that the peer is no longer responding. A value of zero indicates that this peer will not attempt to retransmit an unacknowledged control packet. Modifications to this object have immediate effect.
.1.3.6.1.2.1.10.95.1.4.1.10,L2TP-MIB::l2tpTunnelConfigControlMaxRetxTO,Integer32,read-write,,current,,This object defines the maximum retransmission timeout interval which the tunnel will wait before retrans- mitting a control packet that has not been acknowledged. Modifications to this object have immediate effect.
.1.3.6.1.2.1.10.95.1.4.1.11,L2TP-MIB::l2tpTunnelConfigPayloadSeq,INTEGER,read-write,,current,onDemand(1):never(2):always(3),This object determines whether or not session payload packets will be requested to be sent with sequence numbers from tunnel peers belonging to this domain. The value onDemand(1) allows the L2TP implementation to initiate payload sequencing when necessary based on local information (e.g: during LCP/NCP negotiations or for CCP). The value never(2) indicates that L2TP will never initiate sequencing but will do sequencing if asked. The value always(3) indicates that L2TP will send the Sequencing Required AVP during session establishment. Modifications to this object have immediate effect.
.1.3.6.1.2.1.10.95.1.4.1.12,L2TP-MIB::l2tpTunnelConfigReassemblyTO,Integer32,read-write,,current,,This object defines the number of milliseconds that this tunnel will wait before processing payload packets that were received out of sequence (which are waiting for the packet(s) to put them in sequence). A low value increases the chance of delayed packets to be discarded (which MAY cause the PPP decompression engine to reset) while a high value may cause more queuing and possibly degrade throughput if packets are truly lost. The default value for this object is zero which will result in all delayed packets being lost. Modifications to this object have immediate effect.
.1.3.6.1.2.1.10.95.1.4.1.13,L2TP-MIB::l2tpTunnelConfigTransport,INTEGER,read-write,,current,other(1):none(2):udpIp(3):frameRelay(4):atm(5),This object defines the underlying transport media that is in use for this tunnel entry. Different tunnel transports may define MIB extensions to the L2TP tunnel table to realize the transport layer. For example if the value of this object is 'udpIp' then the value of ifIndex for this table may be used to determine state from the l2tpUdpStatsTable. This object cannot be modified when the tunnel is in a connecting or connected state.
.1.3.6.1.2.1.10.95.1.4.1.14,L2TP-MIB::l2tpTunnelConfigDrainTunnel,INTEGER,read-write,,current,true(1):false(2),Setting this object to 'true' will prevent any new session from being either initiated or accepted but does NOT disconnect any active sessions for this tunnel. Note that when this occurs the l2tpTunnelStatsDrainingTunnel status object of this tunnel should reflect that it is 'draining'. To cancel a drain this object should be set to false(2). Setting this object to false(2) when the L2TP objects l2tpDrainTunnels or l2tpDomainConfigDrainTunnels is true(1) has no affect, this tunnels will continue to drain.
.1.3.6.1.2.1.10.95.1.4.1.15,L2TP-MIB::l2tpTunnelConfigProxyPPPAuth,INTEGER,read-write,,current,true(1):false(2),This object is used to configure the sending or acceptance of the session PPP Proxy Authentication AVP's on the LAC or LNS.
.1.3.6.1.2.1.10.95.1.5,L2TP-MIB::l2tpTunnelStatsTable,,not-accessible,,current,,The L2TP tunnel status and statistics table. This table contains objects that can be used to describe the current status and statistics of a single L2TP tunnel. There is a 1-1 correspondence between conceptual rows of this table and conceptual rows of the l2tpTunnelConfigTable.
.1.3.6.1.2.1.10.95.1.5.1,L2TP-MIB::l2tpTunnelStatsEntry,,not-accessible,,current,,An L2TP tunnel interface stats entry.
.1.3.6.1.2.1.10.95.1.5.1.1,L2TP-MIB::l2tpTunnelStatsLocalTID,Integer32,read-only,,current,,This object contains the local tunnel Identifier.
.1.3.6.1.2.1.10.95.1.5.1.2,L2TP-MIB::l2tpTunnelStatsRemoteTID,Integer32,read-only,,current,,This object contains the remote tunnel Identifier.
.1.3.6.1.2.1.10.95.1.5.1.3,L2TP-MIB::l2tpTunnelStatsState,INTEGER,read-only,,current,tunnelIdle(1):tunnelConnecting(2):tunnelEstablished(3):tunnelDisconnecting(4),This field contains the current state of the control tunnel.
.1.3.6.1.2.1.10.95.1.5.1.4,L2TP-MIB::l2tpTunnelStatsInitiated,INTEGER,read-only,,current,locally(1):remotely(2),This object indicates whether the tunnel was initiated locally or by the remote tunnel peer.
.1.3.6.1.2.1.10.95.1.5.1.5,L2TP-MIB::l2tpTunnelStatsRemoteHostName,OCTET,read-only,,current,,This object contains the host name as discovered during the tunnel establishment phase (via the Host Name AVP) of the L2TP peer. If the tunnel is idle this object should maintain its value from the last time it was connected.
.1.3.6.1.2.1.10.95.1.5.1.6,L2TP-MIB::l2tpTunnelStatsRemoteVendorName,OCTET,read-only,,current,,This object identifies the vendor name of the peer's L2TP implementation. If the tunnel is idle this object should maintain its value from the last time it was connected.
.1.3.6.1.2.1.10.95.1.5.1.7,L2TP-MIB::l2tpTunnelStatsRemoteFirmwareRev,Integer32,read-only,,current,,This object contains the tunnel peer's firmware revision number. If the tunnel is idle this object should maintain its value from the last time it was connected.
.1.3.6.1.2.1.10.95.1.5.1.8,L2TP-MIB::l2tpTunnelStatsRemoteProtocolVer,OCTET,read-only,,current,,This object describes the protocol version and revision of the tunnel peers implementation. The first octet contains the protocol version. The second octet contains the protocol revision.
.1.3.6.1.2.1.10.95.1.5.1.9,L2TP-MIB::l2tpTunnelStatsInitialRemoteRWS,Integer32,read-only,,current,,This object contains the initial remote peer's receive window size as indicated by the tunnel peer (in the RWS AVP) during the tunnel establishment phase. If the tunnel is idle this object should maintain its value from the last time it was connected.
.1.3.6.1.2.1.10.95.1.5.1.10,L2TP-MIB::l2tpTunnelStatsBearerCaps,INTEGER,read-only,,current,none(1):digital(2):analog(3):digitalAnalog(4),This object describes the Bearer Capabilities of the tunnel peer. If the tunnel is idle this object should maintain its value from the last time it was connected.
.1.3.6.1.2.1.10.95.1.5.1.11,L2TP-MIB::l2tpTunnelStatsFramingCaps,INTEGER,read-only,,current,none(1):sync(2):async(3):syncAsync(4),This object describes the Framing Capabilities of the tunnel peer. If the tunnel is idle this object should maintain its value from the last time it was connected.
.1.3.6.1.2.1.10.95.1.5.1.12,L2TP-MIB::l2tpTunnelStatsControlRxPkts,Counter32,read-only,,current,,This object contains the number of control packets received on the tunnel.
.1.3.6.1.2.1.10.95.1.5.1.13,L2TP-MIB::l2tpTunnelStatsControlRxZLB,Counter32,read-only,,current,,This object returns a count of the number of Zero Length Body control packet acknowledgement packets that were received.
.1.3.6.1.2.1.10.95.1.5.1.14,L2TP-MIB::l2tpTunnelStatsControlOutOfSeq,Counter32,read-only,,current,,This object returns a count of the number of control packets that were not received in the correct order (as per the sequence number) on this tunnel including out of window packets.
.1.3.6.1.2.1.10.95.1.5.1.15,L2TP-MIB::l2tpTunnelStatsControlOutOfWin,Counter32,read-only,,current,,This object contains the number of control packets that were received outside of the offered receive window. It is implementation specific as to whether these packets are queued or discarded.
.1.3.6.1.2.1.10.95.1.5.1.16,L2TP-MIB::l2tpTunnelStatsControlTxPkts,Counter32,read-only,,current,,This object contains the number of control packets that were transmitted to the tunnel peer.
.1.3.6.1.2.1.10.95.1.5.1.17,L2TP-MIB::l2tpTunnelStatsControlTxZLB,Counter32,read-only,,current,,This object contains the number of Zero Length Body control packets transmitted to the tunnel peer.
.1.3.6.1.2.1.10.95.1.5.1.18,L2TP-MIB::l2tpTunnelStatsControlAckTO,Counter32,read-only,,current,,This object returns a count of the number of control packet timeouts due to the lack of a timely acknowledgement from the tunnel peer.
.1.3.6.1.2.1.10.95.1.5.1.19,L2TP-MIB::l2tpTunnelStatsCurrentRemoteRWS,Gauge32,read-only,,current,,This object contains the current remote receive window size as determined by the local flow control mechanism employed.
.1.3.6.1.2.1.10.95.1.5.1.20,L2TP-MIB::l2tpTunnelStatsTxSeq,Integer32,read-only,,current,,This object contains the next send sequence number for the control channel.
.1.3.6.1.2.1.10.95.1.5.1.21,L2TP-MIB::l2tpTunnelStatsTxSeqAck,Integer32,read-only,,current,,This object contains the send sequence number that the tunnel peer has acknowledged for the control channel. The flow control state can be determined by subtracting the l2tpTunnelStatsTxSeq from l2tpTunnelStatsTxSeqAck and comparing this value to l2tpTunnelStatsCurrentRemoteRWS (taking into consideration sequence number wraps).
.1.3.6.1.2.1.10.95.1.5.1.22,L2TP-MIB::l2tpTunnelStatsRxSeq,Integer32,read-only,,current,,This object contains the next receive sequence number expected to be received on this control channel.
.1.3.6.1.2.1.10.95.1.5.1.23,L2TP-MIB::l2tpTunnelStatsRxSeqAck,Integer32,read-only,,current,,This object contains the last receive sequence number that was acknowledged back to the tunnel peer for the control channel.
.1.3.6.1.2.1.10.95.1.5.1.24,L2TP-MIB::l2tpTunnelStatsTotalSessions,Counter32,read-only,,current,,This object contains the total number of sessions that this tunnel has successfully connected through to its tunnel peer since this tunnel was created.
.1.3.6.1.2.1.10.95.1.5.1.25,L2TP-MIB::l2tpTunnelStatsFailedSessions,Counter32,read-only,,current,,This object contains the total number of sessions that were initiated but failed to reach the established phase.
.1.3.6.1.2.1.10.95.1.5.1.26,L2TP-MIB::l2tpTunnelStatsActiveSessions,Gauge32,read-only,,current,,This object contains the total number of sessions in the established state for this tunnel.
.1.3.6.1.2.1.10.95.1.5.1.27,L2TP-MIB::l2tpTunnelStatsLastResultCode,Integer32,read-only,,current,,This object contains the last value of the result code as described in the Result Code AVP which caused the tunnel to disconnect.
.1.3.6.1.2.1.10.95.1.5.1.28,L2TP-MIB::l2tpTunnelStatsLastErrorCode,Integer32,read-only,,current,,This object contains the last value of the error code as described in the Result Code AVP which caused the tunnel to disconnect.
.1.3.6.1.2.1.10.95.1.5.1.29,L2TP-MIB::l2tpTunnelStatsLastErrorMessage,OCTET,read-only,,current,,This object contains the last value of the optional message as described in the Result Code AVP which caused the tunnel to disconnect.
.1.3.6.1.2.1.10.95.1.5.1.30,L2TP-MIB::l2tpTunnelStatsDrainingTunnel,INTEGER,read-only,,current,true(1):false(2),This object indicates if this tunnel is draining off sessions. This object will return false(2) when the tunnel is not draining sessions or after the last session has disconnected when the tunnel is in the draining state.
.1.3.6.1.2.1.10.95.1.7,L2TP-MIB::l2tpSessionStatsTable,,not-accessible,,current,,The L2TP session status and statistics table. This table contains the objects that can be used to describe the current status and statistics of a single L2TP tunneled session.
.1.3.6.1.2.1.10.95.1.7.1,L2TP-MIB::l2tpSessionStatsEntry,,not-accessible,l2tpSessionStatsTunnelIfIndex:l2tpSessionStatsLocalSID,current,,An L2TP session interface stats entry.
.1.3.6.1.2.1.10.95.1.7.1.1,L2TP-MIB::l2tpSessionStatsTunnelIfIndex,Integer32,not-accessible,,current,,This object identifies the session's associated L2TP tunnel ifIndex value.
.1.3.6.1.2.1.10.95.1.7.1.2,L2TP-MIB::l2tpSessionStatsIfIndex,Integer32,read-only,,current,,This object identifies the ifIndex value of the interface from which PPP packets are being tunneled. For example this could be a DS0 ifIndex on a LAC or it would be the PPP ifIndex on the LNS.
.1.3.6.1.2.1.10.95.1.7.1.3,L2TP-MIB::l2tpSessionStatsLocalSID,Integer32,not-accessible,,current,,This object contains the local assigned session identifier for this session.
.1.3.6.1.2.1.10.95.1.7.1.4,L2TP-MIB::l2tpSessionStatsRemoteSID,Integer32,read-only,,current,,This object contains the remote assigned session identifier for this session. When a session is starting this value may be zero until the remote tunnel endpoint has responded.
.1.3.6.1.2.1.10.95.1.7.1.5,L2TP-MIB::l2tpSessionStatsUserName,OCTET,read-only,,current,,This object identifies the peer session name on this interface. This is typically the login name of the remote user. If the user name is unknown to the local tunnel peer then this object will contain a null string.
.1.3.6.1.2.1.10.95.1.7.1.6,L2TP-MIB::l2tpSessionStatsState,INTEGER,read-only,,current,sessionIdle(1):sessionConnecting(2):sessionEstablished(3):sessionDisconnecting(4),This object contains the current state of the session.
.1.3.6.1.2.1.10.95.1.7.1.7,L2TP-MIB::l2tpSessionStatsCallType,INTEGER,read-only,,current,lacIncoming(1):lnsIncoming(2):lacOutgoing(3):lnsOutgoing(4),This object indicates the type of call and the role this tunnel peer is providing for this session. For example, lacIncoming(1) indicates that this tunnel peer is acting as a LAC and generated a Incoming-Call-Request to the tunnel peer (the LNS). Note that tunnel peers can be both LAC and LNS simultaneously.
.1.3.6.1.2.1.10.95.1.7.1.8,L2TP-MIB::l2tpSessionStatsCallSerialNumber,Unsigned32,read-only,,current,,This object contains the serial number that has been assigned to this session.
.1.3.6.1.2.1.10.95.1.7.1.9,L2TP-MIB::l2tpSessionStatsTxConnectSpeed,Unsigned32,read-only,,current,,This object returns the last known transmit baud rate for this session.
.1.3.6.1.2.1.10.95.1.7.1.10,L2TP-MIB::l2tpSessionStatsRxConnectSpeed,Unsigned32,read-only,,current,,This object returns the last known receive baud rate for this session established.
.1.3.6.1.2.1.10.95.1.7.1.11,L2TP-MIB::l2tpSessionStatsCallBearerType,INTEGER,read-only,,current,none(1):digital(2):analog(3),This object describes the bearer type of this session.
.1.3.6.1.2.1.10.95.1.7.1.12,L2TP-MIB::l2tpSessionStatsFramingType,INTEGER,read-only,,current,none(1):sync(2):async(3),This object describes the framing type of this session.
.1.3.6.1.2.1.10.95.1.7.1.13,L2TP-MIB::l2tpSessionStatsPhysChanId,Unsigned32,read-only,,current,,This object contains the physical channel identifier for the session.
.1.3.6.1.2.1.10.95.1.7.1.14,L2TP-MIB::l2tpSessionStatsDNIS,OCTET,read-only,,current,,This object identifies the Dialed Number Information String that the LAC obtained from the network for the session. If no DNIS was provided then a null string will be returned.
.1.3.6.1.2.1.10.95.1.7.1.15,L2TP-MIB::l2tpSessionStatsCLID,OCTET,read-only,,current,,This object identifies the Calling Line ID that the LAC obtained from the network for the session. If no CLID was provided then a null string will be returned.
.1.3.6.1.2.1.10.95.1.7.1.16,L2TP-MIB::l2tpSessionStatsSubAddress,OCTET,read-only,,current,,This object identifies the Sub Address that the LAC obtained from the network for the session. If no Sub Address was provided then a null string will be returned.
.1.3.6.1.2.1.10.95.1.7.1.17,L2TP-MIB::l2tpSessionStatsPrivateGroupID,OCTET,read-only,,current,,This object identifies the Private Group Identifier used for this tunneled session. If no Private Group Identifier was provided then a null string will be returned.
.1.3.6.1.2.1.10.95.1.7.1.18,L2TP-MIB::l2tpSessionStatsProxyLcp,INTEGER,read-only,,current,true(1):false(2),Indicates whether the LAC performed proxy LCP for this session.
.1.3.6.1.2.1.10.95.1.7.1.19,L2TP-MIB::l2tpSessionStatsAuthMethod,INTEGER,read-only,,current,none(1):text(2):pppChap(3):pppPap(4):pppEap(5):pppMsChapV1(6):pppMsChapV2(7):other(8),This object contains the proxy authentication method employed by the LAC for the session. If l2tpSessionProxyLcp is false(2) this object should not be interpreted.
.1.3.6.1.2.1.10.95.1.7.1.20,L2TP-MIB::l2tpSessionStatsSequencingState,INTEGER,read-only,,current,none(1):remote(2):local(3):both(4),This object defines which tunnel peers have requested payload sequencing. The value of both(4) indicates that both peers have requested payload sequencing.
.1.3.6.1.2.1.10.95.1.7.1.21,L2TP-MIB::l2tpSessionStatsOutSequence,Counter32,read-only,,current,,This object returns the total number of packets received for this session which were received out of sequence.
.1.3.6.1.2.1.10.95.1.7.1.22,L2TP-MIB::l2tpSessionStatsReassemblyTO,Counter32,read-only,,current,,This object returns the number of reassembly timeouts that have occurred for this session.
.1.3.6.1.2.1.10.95.1.7.1.23,L2TP-MIB::l2tpSessionStatsTxSeq,Integer32,read-only,,current,,This object contains the next send sequence number for for this session.
.1.3.6.1.2.1.10.95.1.7.1.24,L2TP-MIB::l2tpSessionStatsRxSeq,Integer32,read-only,,current,,This object contains the next receive sequence number expected to be received on this session.
.1.3.6.1.2.1.10.95.1.8,L2TP-MIB::l2tpTunnelMapTable,,not-accessible,,current,,The L2TP Tunnel index mapping table. This table is intended to assist management applications to quickly determine what the ifIndex value is for a given local tunnel identifier.
.1.3.6.1.2.1.10.95.1.8.1,L2TP-MIB::l2tpTunnelMapEntry,,not-accessible,l2tpTunnelMapLocalTID,current,,An L2TP tunnel index map entry.
.1.3.6.1.2.1.10.95.1.8.1.1,L2TP-MIB::l2tpTunnelMapLocalTID,Integer32,not-accessible,,current,,This object contains the local tunnel Identifier.
.1.3.6.1.2.1.10.95.1.8.1.2,L2TP-MIB::l2tpTunnelMapIfIndex,Integer32,read-only,,current,,This value for this object is equal to the value of ifIndex of the Interfaces MIB for tunnel interfaces of type L2TP.
.1.3.6.1.2.1.10.95.1.9,L2TP-MIB::l2tpSessionMapTable,,not-accessible,,current,,The L2TP Session index mapping table. This table is intended to assist management applications to map interfaces to a tunnel and session identifier.
.1.3.6.1.2.1.10.95.1.9.1,L2TP-MIB::l2tpSessionMapEntry,,not-accessible,l2tpSessionMapIfIndex,current,,An L2TP Session index map entry.
.1.3.6.1.2.1.10.95.1.9.1.1,L2TP-MIB::l2tpSessionMapIfIndex,Integer32,not-accessible,,current,,This object identifies the ifIndex value of the interface which is receiving or sending its packets over an L2TP tunnel. For example this could be a DS0 ifIndex on a LAC or a PPP ifIndex on the LNS.
.1.3.6.1.2.1.10.95.1.9.1.2,L2TP-MIB::l2tpSessionMapTunnelIfIndex,Integer32,read-create,,current,,This object identifies the sessions associated L2TP tunnel ifIndex value. When this object is set it provides a binding between a particular interface identified by l2tpSessionMapIfIndex to a particular tunnel.
.1.3.6.1.2.1.10.95.1.9.1.3,L2TP-MIB::l2tpSessionMapLocalSID,Integer32,read-only,,current,,This object contains the local assigned session identifier for this session.
.1.3.6.1.2.1.10.95.1.9.1.4,L2TP-MIB::l2tpSessionMapStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this session map entry.
.1.3.6.1.2.1.10.95.3,L2TP-MIB::l2tpTransports,,,,,,
.1.3.6.1.2.1.10.95.3.1,L2TP-MIB::l2tpTransportIpUdp,,,,,,
.1.3.6.1.2.1.10.95.3.1.1,L2TP-MIB::l2tpIpUdpObjects,,,,,,
.1.3.6.1.2.1.10.95.3.1.1.2,L2TP-MIB::l2tpUdpStatsTable,,not-accessible,,current,,The L2TP UDP/IP transport stats table. This table contains objects that can be used to describe the current status and statistics of the UDP/IP L2TP tunnel transport.
.1.3.6.1.2.1.10.95.3.1.1.2.1,L2TP-MIB::l2tpUdpStatsEntry,,not-accessible,l2tpUdpStatsIfIndex,current,,An L2TP UDP/IP transport stats entry.
.1.3.6.1.2.1.10.95.3.1.1.2.1.1,L2TP-MIB::l2tpUdpStatsIfIndex,Integer32,not-accessible,,current,,This value for this object is equal to the value of ifIndex of the Interfaces MIB for tunnel interfaces of type L2TP and which have a L2TP transport of UDP/IP.
.1.3.6.1.2.1.10.95.3.1.1.2.1.2,L2TP-MIB::l2tpUdpStatsPeerPort,Integer32,read-only,,current,,This object reflects the peer's UDP port number used for this tunnel. When not known a value of zero should be returned.
.1.3.6.1.2.1.10.95.3.1.1.2.1.3,L2TP-MIB::l2tpUdpStatsLocalPort,Integer32,read-only,,current,,This object reflects the local UDP port number that this tunnel is bound to.
.1.3.6.1.2.1.10.95.3.1.2,L2TP-MIB::l2tpIpUdpTraps,,,,,,
.1.3.6.1.2.1.10.95.4,L2TP-MIB::l2tpConformance,,,,,,
.1.3.6.1.2.1.10.95.4.1,L2TP-MIB::l2tpGroups,,,,,,
.1.3.6.1.2.1.10.95.4.1.1,L2TP-MIB::l2tpConfigGroup,,,,,,A collection of objects providing configuration information of the L2TP protocol, tunnels and sessions.
.1.3.6.1.2.1.10.95.4.1.2,L2TP-MIB::l2tpStatsGroup,,,,,,A collection of objects providing status and statistics of the L2TP protocol, tunnels and sessions.
.1.3.6.1.2.1.10.95.4.1.3,L2TP-MIB::l2tpIpUdpGroup,,,,,,A collection of objects providing status and statistics of the L2TP UDP/IP transport layer.
.1.3.6.1.2.1.10.95.4.1.4,L2TP-MIB::l2tpDomainGroup,,,,,,A collection of objects providing configuration, status and statistics of L2TP tunnel domains.
.1.3.6.1.2.1.10.95.4.1.5,L2TP-MIB::l2tpMappingGroup,,,,,,A collection of objects providing index mapping.
.1.3.6.1.2.1.10.95.4.1.6,L2TP-MIB::l2tpSecurityGroup,,,,,,A collection of objects providing L2TP security configuration.
.1.3.6.1.2.1.10.95.4.1.7,L2TP-MIB::l2tpTrapGroup,,,,,,A collection of L2TP trap events as specified in NOTIFICATION-TYPE constructs.
.1.3.6.1.2.1.10.95.4.1.8,L2TP-MIB::l2tpHCPacketGroup,,,,,,A collection of objects providing High Capacity 64-bit counter objects.
.1.3.6.1.2.1.10.95.4.2,L2TP-MIB::l2tpCompliances,,,,,,
.1.3.6.1.2.1.10.95.4.2.1,L2TP-MIB::l2tpMIBFullCompliance,,,,,,When this MIB is implemented with support for read-create and read-write, then such an implementation can claim full compliance. Such an implementation can then be both monitored and configured with this MIB.
.1.3.6.1.2.1.10.95.4.2.2,L2TP-MIB::l2tpMIBReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-create and read-write (i.e. in read-only mode), then such an implementation can claim read-only compliance. Such an implementation can then be monitored but can not be configured with this MIB.
.1.3.6.1.2.1.10.97,VDSL-LINE-MIB::vdslMIB,,,,,,The MIB module defining objects for the management of a pair of VDSL transceivers at each end of the VDSL line. Each such line has an entry in an ifTable which may include multiple transceiver lines. An agent may reside at either end of the VDSL line. However, the MIB is designed to require no management communication between them beyond that inherent in the low-level VDSL line protocol. The agent may monitor and control this protocol for its needs. VDSL lines may support optional Fast or Interleaved channels. If these are supported, additional entries corresponding to the supported channels must be created in the ifTable. Thus a VDSL line that supports both channels will have three entries in the ifTable, one for each physical, fast, and interleaved, whose ifType values are equal to vdsl(97), fast(125), and interleaved(124), respectively. The ifStackTable is used to represent the relationship between the entries. Naming Conventions: Vtuc -- (VTUC) transceiver at near (Central) end of line Vtur -- (VTUR) transceiver at Remote end of line Vtu -- One of either Vtuc or Vtur Curr -- Current Prev -- Previous Atn -- Attenuation ES -- Errored Second. SES -- Severely Errored Second UAS -- Unavailable Second LCS -- Line Code Specific Lof -- Loss of Frame Lol -- Loss of Link Los -- Loss of Signal Lpr -- Loss of Power xxxs -- Sum of Seconds in which xxx has occured (e.g., xxx = Lof, Los, Lpr, Lol) Max -- Maximum Mgn -- Margin Min -- Minimum Psd -- Power Spectral Density Snr -- Signal to Noise Ratio Tx -- Transmit Blks -- Blocks Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3728: see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.97.1,VDSL-LINE-MIB::vdslLineMib,,,,,,
.1.3.6.1.2.1.10.97.1.0,VDSL-LINE-MIB::vdslNotifications,,,,,,
.1.3.6.1.2.1.10.97.1.0.1,VDSL-LINE-MIB::vdslPerfLofsThreshNotification,,,,,,Loss of Framing 15-minute interval threshold (vdslLineAlarmConfThresh15MinLofs) reached.
.1.3.6.1.2.1.10.97.1.0.2,VDSL-LINE-MIB::vdslPerfLossThreshNotification,,,,,,Loss of Signal 15-minute interval threshold (vdslLineAlarmConfThresh15MinLoss) reached.
.1.3.6.1.2.1.10.97.1.0.3,VDSL-LINE-MIB::vdslPerfLprsThreshNotification,,,,,,Loss of Power 15-minute interval threshold (vdslLineAlarmConfThresh15MinLprs) reached.
.1.3.6.1.2.1.10.97.1.0.4,VDSL-LINE-MIB::vdslPerfLolsThreshNotification,,,,,,Loss of Link 15-minute interval threshold (vdslLineAlarmConfThresh15MinLols) reached.
.1.3.6.1.2.1.10.97.1.0.5,VDSL-LINE-MIB::vdslPerfESsThreshNotification,,,,,,Errored Seconds 15-minute interval threshold (vdslLineAlarmConfThresh15MinESs) reached.
.1.3.6.1.2.1.10.97.1.0.6,VDSL-LINE-MIB::vdslPerfSESsThreshNotification,,,,,,Severely Errored Seconds 15-minute interval threshold (vdslLineAlarmConfThresh15MinSESs) reached.
.1.3.6.1.2.1.10.97.1.0.7,VDSL-LINE-MIB::vdslPerfUASsThreshNotification,,,,,,Unavailable Seconds 15-minute interval threshold (vdslLineAlarmConfThresh15MinUASs) reached.
.1.3.6.1.2.1.10.97.1.0.8,VDSL-LINE-MIB::vdslDownMaxSnrMgnNotification,,,,,,The downstream Signal to Noise Margin exceeded vdslLineConfDownMaxSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-R.
.1.3.6.1.2.1.10.97.1.0.9,VDSL-LINE-MIB::vdslDownMinSnrMgnNotification,,,,,,The downstream Signal to Noise Margin fell below vdslLineConfDownMinSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-R.
.1.3.6.1.2.1.10.97.1.0.10,VDSL-LINE-MIB::vdslUpMaxSnrMgnNotification,,,,,,The upstream Signal to Noise Margin exceeded vdslLineConfUpMaxSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-C.
.1.3.6.1.2.1.10.97.1.0.11,VDSL-LINE-MIB::vdslUpMinSnrMgnNotification,,,,,,The upstream Signal to Noise Margin fell below vdslLineConfUpMinSnrMgn. The object vdslPhysCurrSnrMgn will contain the Signal to Noise margin as measured by the VTU-C.
.1.3.6.1.2.1.10.97.1.0.12,VDSL-LINE-MIB::vdslInitFailureNotification,,,,,,Vtu initialization failed. See vdslPhysCurrStatus for potential reasons.
.1.3.6.1.2.1.10.97.1.1,VDSL-LINE-MIB::vdslMibObjects,,,,,,
.1.3.6.1.2.1.10.97.1.1.1,VDSL-LINE-MIB::vdslLineTable,,not-accessible,,current,,This table includes common attributes describing both ends of the line. It is required for all VDSL physical interfaces. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
.1.3.6.1.2.1.10.97.1.1.1.1,VDSL-LINE-MIB::vdslLineEntry,,not-accessible,ifIndex,current,,An entry in the vdslLineTable.
.1.3.6.1.2.1.10.97.1.1.1.1.1,VDSL-LINE-MIB::vdslLineCoding,INTEGER,read-only,,current,other(1):mcm(2):scm(3),Specifies the VDSL coding type used on this line.
.1.3.6.1.2.1.10.97.1.1.1.1.2,VDSL-LINE-MIB::vdslLineType,INTEGER,read-only,,current,noChannel(1):fastOnly(2):interleavedOnly(3):fastOrInterleaved(4):fastAndInterleaved(5),Defines the type of VDSL physical line entity that exists, by defining whether and how the line is channelized. If the line is channelized, the value will be other than noChannel(1). This object defines which channel type(s) are supported. Defined values are: noChannel(1) -- no channels exist fastOnly(2) -- only fast channel exists interleavedOnly(3) -- only interleaved channel exists fastOrInterleaved(4) -- either fast or interleaved channel -- exist, but only one at a time fastAndInterleaved(5) -- both fast and interleaved channels -- exist Note that 'slow' and 'interleaved' refer to the same channel. In the case that the line is channelized, the manager can use the ifStackTable to determine the ifIndex for the associated channel(s).
.1.3.6.1.2.1.10.97.1.1.1.1.3,VDSL-LINE-MIB::vdslLineConfProfile,OCTET,read-write,,current,,The value of this object identifies the row in the VDSL Line Configuration Profile Table, vdslLineConfProfileTable, which applies for this VDSL line, and channels if applicable. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.97.1.1.1.1.4,VDSL-LINE-MIB::vdslLineAlarmConfProfile,OCTET,read-write,,current,,The value of this object identifies the row in the VDSL Line Alarm Configuration Profile Table, vdslLineAlarmConfProfileTable, which applies to this VDSL line, and channels if applicable. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.97.1.1.2,VDSL-LINE-MIB::vdslPhysTable,,not-accessible,,current,,This table provides one row for each Vtu. Each row contains the Physical Layer Parameters table for that Vtu. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
.1.3.6.1.2.1.10.97.1.1.2.1,VDSL-LINE-MIB::vdslPhysEntry,,not-accessible,ifIndex:vdslPhysSide,current,,An entry in the vdslPhysTable.
.1.3.6.1.2.1.10.97.1.1.2.1.1,VDSL-LINE-MIB::vdslPhysSide,INTEGER,not-accessible,,current,vtuc(1):vtur(2),Identifies whether the transceiver is the Vtuc or Vtur.
.1.3.6.1.2.1.10.97.1.1.2.1.2,VDSL-LINE-MIB::vdslPhysInvSerialNumber,OCTET,read-only,,current,,The vendor specific string that identifies the vendor equipment.
.1.3.6.1.2.1.10.97.1.1.2.1.3,VDSL-LINE-MIB::vdslPhysInvVendorID,OCTET,read-only,,current,,The vendor ID code is a copy of the binary vendor identification field expressed as readable characters in hexadecimal notation.
.1.3.6.1.2.1.10.97.1.1.2.1.4,VDSL-LINE-MIB::vdslPhysInvVersionNumber,OCTET,read-only,,current,,The vendor specific version number sent by this Vtu as part of the initialization messages. It is a copy of the binary version number field expressed as readable characters in hexadecimal notation.
.1.3.6.1.2.1.10.97.1.1.2.1.5,VDSL-LINE-MIB::vdslPhysCurrSnrMgn,Integer32,read-only,,current,,Noise Margin as seen by this Vtu with respect to its received signal in 0.25dB. The effective range is -31.75 to +31.75 dB.
.1.3.6.1.2.1.10.97.1.1.2.1.6,VDSL-LINE-MIB::vdslPhysCurrAtn,Gauge32,read-only,,current,,Measured difference in the total power transmitted by the peer Vtu and the total power received by this Vtu. The effective range is 0 to +63.75 dB.
.1.3.6.1.2.1.10.97.1.1.2.1.7,VDSL-LINE-MIB::vdslPhysCurrStatus,BITS,read-only,,current,noDefect(0):lossOfFraming(1):lossOfSignal(2):lossOfPower(3):lossOfSignalQuality(4):lossOfLink(5):dataInitFailure(6):configInitFailure(7):protocolInitFailure(8):noPeerVtuPresent(9),Indicates current state of the Vtu line. This is a bit-map of possible conditions. The various bit positions are: 0 noDefect There are no defects on the line. 1 lossOfFraming Vtu failure due to not receiving a valid frame. 2 lossOfSignal Vtu failure due to not receiving signal. 3 lossOfPower Vtu failure due to loss of power. 4 lossOfSignalQuality Loss of Signal Quality is declared when the Noise Margin falls below the Minimum Noise Margin, or the bit-error-rate exceeds 10^-7. 5 lossOfLink Vtu failure due to inability to link with peer Vtu. Set whenever the transceiver is in the 'Warm Start' state. 6 dataInitFailure Vtu failure during initialization due to bit errors corrupting startup exchange data. 7 configInitFailure Vtu failure during initialization due to peer Vtu not able to support requested configuration. 8 protocolInitFailure Vtu failure during initialization due to incompatible protocol used by the peer Vtu. 9 noPeerVtuPresent Vtu failure during initialization due to no activation sequence detected from peer Vtu. This is intended to supplement ifOperStatus.
.1.3.6.1.2.1.10.97.1.1.2.1.8,VDSL-LINE-MIB::vdslPhysCurrOutputPwr,Integer32,read-only,,current,,Measured total output power transmitted by this VTU. This is the measurement that was reported during the last activation sequence.
.1.3.6.1.2.1.10.97.1.1.2.1.9,VDSL-LINE-MIB::vdslPhysCurrAttainableRate,Gauge32,read-only,,current,,Indicates the maximum currently attainable data rate in steps of 1000 bits/second by the Vtu. This value will be equal to or greater than vdslPhysCurrLineRate. Note that for SCM, the minimum and maximum data rates are equal. Note: 1 kbps = 1000 bps.
.1.3.6.1.2.1.10.97.1.1.2.1.10,VDSL-LINE-MIB::vdslPhysCurrLineRate,Gauge32,read-only,,current,,Indicates the current data rate in steps of 1000 bits/second by the Vtu. This value will be less than or equal to vdslPhysCurrAttainableRate. Note: 1 kbps = 1000 bps.
.1.3.6.1.2.1.10.97.1.1.3,VDSL-LINE-MIB::vdslChanTable,,not-accessible,,current,,This table provides one row for each Vtu channel. VDSL channel interfaces are those ifEntries where ifType is equal to interleave(124) or fast(125).
.1.3.6.1.2.1.10.97.1.1.3.1,VDSL-LINE-MIB::vdslChanEntry,,not-accessible,ifIndex:vdslPhysSide,current,,An entry in the vdslChanTable.
.1.3.6.1.2.1.10.97.1.1.3.1.1,VDSL-LINE-MIB::vdslChanInterleaveDelay,Gauge32,read-only,,current,,Interleave Delay for this channel. Interleave delay applies only to the interleave (slow) channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleaver output. Larger numbers provide greater separation between consecutive input bytes in the output bit stream allowing for improved impulse noise immunity at the expense of payload latency. In the case where the ifType is fast(125), return a value of zero.
.1.3.6.1.2.1.10.97.1.1.3.1.2,VDSL-LINE-MIB::vdslChanCrcBlockLength,Gauge32,read-only,,current,,Indicates the length of the channel data-block on which the CRC operates.
.1.3.6.1.2.1.10.97.1.1.3.1.3,VDSL-LINE-MIB::vdslChanCurrTxRate,Gauge32,read-only,,current,,Actual transmit data rate on this channel. Note: 1 kbps = 1000 bps.
.1.3.6.1.2.1.10.97.1.1.3.1.4,VDSL-LINE-MIB::vdslChanCurrTxSlowBurstProtect,Gauge32,read-only,,current,,Actual level of impulse noise (burst) protection for an interleaved (slow) channel. This parameter is not applicable to fast channels. For fast channels, a value of zero shall be returned.
.1.3.6.1.2.1.10.97.1.1.3.1.5,VDSL-LINE-MIB::vdslChanCurrTxFastFec,Gauge32,read-only,,current,,Actual Forward Error Correction (FEC) redundancy related overhead for a fast channel. This parameter is not applicable to an interleaved (slow) channel. For interleaved channels, a value of zero shall be returned.
.1.3.6.1.2.1.10.97.1.1.4,VDSL-LINE-MIB::vdslPerfDataTable,,not-accessible,,current,,This table provides one row for each VDSL physical interface. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
.1.3.6.1.2.1.10.97.1.1.4.1,VDSL-LINE-MIB::vdslPerfDataEntry,,not-accessible,ifIndex:vdslPhysSide,current,,An entry in the vdslPerfDataTable.
.1.3.6.1.2.1.10.97.1.1.4.1.1,VDSL-LINE-MIB::vdslPerfDataValidIntervals,Integer32,read-only,,current,,Valid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.4.1.2,VDSL-LINE-MIB::vdslPerfDataInvalidIntervals,Integer32,read-only,,current,,Invalid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.4.1.3,VDSL-LINE-MIB::vdslPerfDataLofs,Unsigned32,read-only,,current,,Count of seconds since the unit was last reset that there was Loss of Framing.
.1.3.6.1.2.1.10.97.1.1.4.1.4,VDSL-LINE-MIB::vdslPerfDataLoss,Unsigned32,read-only,,current,,Count of seconds since the unit was last reset that there was Loss of Signal.
.1.3.6.1.2.1.10.97.1.1.4.1.5,VDSL-LINE-MIB::vdslPerfDataLprs,Unsigned32,read-only,,current,,Count of seconds since the unit was last reset that there was Loss of Power.
.1.3.6.1.2.1.10.97.1.1.4.1.6,VDSL-LINE-MIB::vdslPerfDataLols,Unsigned32,read-only,,current,,Count of seconds since the unit was last reset that there was Loss of Link.
.1.3.6.1.2.1.10.97.1.1.4.1.7,VDSL-LINE-MIB::vdslPerfDataESs,Unsigned32,read-only,,current,,Count of Errored Seconds since the unit was last reset. An Errored Second is a one-second interval containing one or more CRC anomalies, or one or more LOS or LOF defects.
.1.3.6.1.2.1.10.97.1.1.4.1.8,VDSL-LINE-MIB::vdslPerfDataSESs,Unsigned32,read-only,,current,,Count of Severely Errored Seconds since the unit was last reset.
.1.3.6.1.2.1.10.97.1.1.4.1.9,VDSL-LINE-MIB::vdslPerfDataUASs,Unsigned32,read-only,,current,,Count of Unavailable Seconds since the unit was last reset.
.1.3.6.1.2.1.10.97.1.1.4.1.10,VDSL-LINE-MIB::vdslPerfDataInits,Unsigned32,read-only,,current,,Count of the line initialization attempts since the unit was last reset. This count includes both successful and failed attempts.
.1.3.6.1.2.1.10.97.1.1.4.1.11,VDSL-LINE-MIB::vdslPerfDataCurr15MinTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.97.1.1.4.1.12,VDSL-LINE-MIB::vdslPerfDataCurr15MinLofs,Counter64,read-only,,current,,Count of seconds during this interval that there was Loss of Framing.
.1.3.6.1.2.1.10.97.1.1.4.1.13,VDSL-LINE-MIB::vdslPerfDataCurr15MinLoss,Counter64,read-only,,current,,Count of seconds during this interval that there was Loss of Signal.
.1.3.6.1.2.1.10.97.1.1.4.1.14,VDSL-LINE-MIB::vdslPerfDataCurr15MinLprs,Counter64,read-only,,current,,Count of seconds during this interval that there was Loss of Power.
.1.3.6.1.2.1.10.97.1.1.4.1.15,VDSL-LINE-MIB::vdslPerfDataCurr15MinLols,Counter64,read-only,,current,,Count of seconds during this interval that there was Loss of Link.
.1.3.6.1.2.1.10.97.1.1.4.1.16,VDSL-LINE-MIB::vdslPerfDataCurr15MinESs,Counter64,read-only,,current,,Count of Errored Seconds during this interval. An Errored Second is a one-second interval containing one or more CRC anomalies, or one or more LOS or LOF defects.
.1.3.6.1.2.1.10.97.1.1.4.1.17,VDSL-LINE-MIB::vdslPerfDataCurr15MinSESs,Counter64,read-only,,current,,Count of Severely Errored Seconds during this interval.
.1.3.6.1.2.1.10.97.1.1.4.1.18,VDSL-LINE-MIB::vdslPerfDataCurr15MinUASs,Counter64,read-only,,current,,Count of Unavailable Seconds during this interval.
.1.3.6.1.2.1.10.97.1.1.4.1.19,VDSL-LINE-MIB::vdslPerfDataCurr15MinInits,Counter64,read-only,,current,,Count of the line initialization attempts during this interval. This count includes both successful and failed attempts.
.1.3.6.1.2.1.10.97.1.1.4.1.20,VDSL-LINE-MIB::vdslPerfData1DayValidIntervals,Integer32,read-only,,current,,Valid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.4.1.21,VDSL-LINE-MIB::vdslPerfData1DayInvalidIntervals,Integer32,read-only,,current,,Invalid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.4.1.22,VDSL-LINE-MIB::vdslPerfDataCurr1DayTimeElapsed,Integer32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.23,VDSL-LINE-MIB::vdslPerfDataCurr1DayLofs,Unsigned32,read-only,,current,,Count of Loss of Framing (LOF) Seconds since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.24,VDSL-LINE-MIB::vdslPerfDataCurr1DayLoss,Unsigned32,read-only,,current,,Count of Loss of Signal (LOS) Seconds since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.25,VDSL-LINE-MIB::vdslPerfDataCurr1DayLprs,Unsigned32,read-only,,current,,Count of Loss of Power (LPR) Seconds since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.26,VDSL-LINE-MIB::vdslPerfDataCurr1DayLols,Unsigned32,read-only,,current,,Count of Loss of Link (LOL) Seconds since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.27,VDSL-LINE-MIB::vdslPerfDataCurr1DayESs,Unsigned32,read-only,,current,,Count of Errored Seconds (ES) since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.28,VDSL-LINE-MIB::vdslPerfDataCurr1DaySESs,Unsigned32,read-only,,current,,Count of Severely Errored Seconds (SES) since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.29,VDSL-LINE-MIB::vdslPerfDataCurr1DayUASs,Unsigned32,read-only,,current,,Count of Unavailable Seconds (UAS) since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.4.1.30,VDSL-LINE-MIB::vdslPerfDataCurr1DayInits,Unsigned32,read-only,,current,,Count of the line initialization attempts since the beginning of the current 1-day interval. This count includes both successful and failed attempts.
.1.3.6.1.2.1.10.97.1.1.5,VDSL-LINE-MIB::vdslPerfIntervalTable,,not-accessible,,current,,This table provides one row for each Vtu performance data collection interval. VDSL physical interfaces are those ifEntries where ifType is equal to vdsl(97).
.1.3.6.1.2.1.10.97.1.1.5.1,VDSL-LINE-MIB::vdslPerfIntervalEntry,,not-accessible,ifIndex:vdslPhysSide:vdslPerfIntervalNumber,current,,An entry in the vdslPerfIntervalTable.
.1.3.6.1.2.1.10.97.1.1.5.1.1,VDSL-LINE-MIB::vdslPerfIntervalNumber,Unsigned32,not-accessible,,current,,Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2 to 96 are optional.
.1.3.6.1.2.1.10.97.1.1.5.1.2,VDSL-LINE-MIB::vdslPerfIntervalLofs,Counter64,read-only,,current,,Count of seconds in the interval when there was Loss of Framing.
.1.3.6.1.2.1.10.97.1.1.5.1.3,VDSL-LINE-MIB::vdslPerfIntervalLoss,Counter64,read-only,,current,,Count of seconds in the interval when there was Loss of Signal.
.1.3.6.1.2.1.10.97.1.1.5.1.4,VDSL-LINE-MIB::vdslPerfIntervalLprs,Counter64,read-only,,current,,Count of seconds in the interval when there was Loss of Power.
.1.3.6.1.2.1.10.97.1.1.5.1.5,VDSL-LINE-MIB::vdslPerfIntervalLols,Counter64,read-only,,current,,Count of seconds in the interval when there was Loss of Link.
.1.3.6.1.2.1.10.97.1.1.5.1.6,VDSL-LINE-MIB::vdslPerfIntervalESs,Counter64,read-only,,current,,Count of Errored Seconds (ES) in the interval. An Errored Second is a one-second interval containing one or more CRC anomalies, one or more LOS or LOF defects.
.1.3.6.1.2.1.10.97.1.1.5.1.7,VDSL-LINE-MIB::vdslPerfIntervalSESs,Counter64,read-only,,current,,Count of Severely Errored Seconds in the interval.
.1.3.6.1.2.1.10.97.1.1.5.1.8,VDSL-LINE-MIB::vdslPerfIntervalUASs,Counter64,read-only,,current,,Count of Unavailable Seconds in the interval.
.1.3.6.1.2.1.10.97.1.1.5.1.9,VDSL-LINE-MIB::vdslPerfIntervalInits,Counter64,read-only,,current,,Count of the line initialization attempts during this interval. This count includes both successful and failed attempts.
.1.3.6.1.2.1.10.97.1.1.6,VDSL-LINE-MIB::vdslPerf1DayIntervalTable,,not-accessible,,current,,This table provides one row for each VDSL performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.10.97.1.1.6.1,VDSL-LINE-MIB::vdslPerf1DayIntervalEntry,,not-accessible,ifIndex:vdslPhysSide:vdslPerf1DayIntervalNumber,current,,An entry in the vdslPerf1DayIntervalTable.
.1.3.6.1.2.1.10.97.1.1.6.1.1,VDSL-LINE-MIB::vdslPerf1DayIntervalNumber,Unsigned32,not-accessible,,current,,History Data Interval number. Interval 1 is the most recent previous day; interval 30 is 30 days ago. Intervals 2 to 30 are optional.
.1.3.6.1.2.1.10.97.1.1.6.1.2,VDSL-LINE-MIB::vdslPerf1DayIntervalMoniSecs,Integer32,read-only,,current,,The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.97.1.1.6.1.3,VDSL-LINE-MIB::vdslPerf1DayIntervalLofs,Unsigned32,read-only,,current,,Count of Loss of Frame (LOF) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.4,VDSL-LINE-MIB::vdslPerf1DayIntervalLoss,Unsigned32,read-only,,current,,Count of Loss of Signal (LOS) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.5,VDSL-LINE-MIB::vdslPerf1DayIntervalLprs,Unsigned32,read-only,,current,,Count of Loss of Power (LPR) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.6,VDSL-LINE-MIB::vdslPerf1DayIntervalLols,Unsigned32,read-only,,current,,Count of Loss of Link (LOL) Seconds during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.7,VDSL-LINE-MIB::vdslPerf1DayIntervalESs,Unsigned32,read-only,,current,,Count of Errored Seconds (ES) during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.8,VDSL-LINE-MIB::vdslPerf1DayIntervalSESs,Unsigned32,read-only,,current,,Count of Severely Errored Seconds (SES) during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.9,VDSL-LINE-MIB::vdslPerf1DayIntervalUASs,Unsigned32,read-only,,current,,Count of Unavailable Seconds (UAS) during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.10.97.1.1.6.1.10,VDSL-LINE-MIB::vdslPerf1DayIntervalInits,Unsigned32,read-only,,current,,Count of the line initialization attempts during the 1-day interval as measured by vdslPerf1DayIntervalMoniSecs. This count includes both successful and failed attempts.
.1.3.6.1.2.1.10.97.1.1.7,VDSL-LINE-MIB::vdslChanPerfDataTable,,not-accessible,,current,,This table provides one row for each Vtu channel. VDSL channel interfaces are those ifEntries where ifType is equal to interleave(124) or fast(125).
.1.3.6.1.2.1.10.97.1.1.7.1,VDSL-LINE-MIB::vdslChanPerfDataEntry,,not-accessible,ifIndex:vdslPhysSide,current,,An entry in the vdslChanPerfDataTable.
.1.3.6.1.2.1.10.97.1.1.7.1.1,VDSL-LINE-MIB::vdslChanValidIntervals,Integer32,read-only,,current,,Valid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.7.1.2,VDSL-LINE-MIB::vdslChanInvalidIntervals,Integer32,read-only,,current,,Invalid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.7.1.3,VDSL-LINE-MIB::vdslChanFixedOctets,Counter64,read-only,,current,,Count of corrected octets since the unit was last reset.
.1.3.6.1.2.1.10.97.1.1.7.1.4,VDSL-LINE-MIB::vdslChanBadBlks,Counter64,read-only,,current,,Count of uncorrectable blocks since the unit was last reset.
.1.3.6.1.2.1.10.97.1.1.7.1.5,VDSL-LINE-MIB::vdslChanCurr15MinTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.97.1.1.7.1.6,VDSL-LINE-MIB::vdslChanCurr15MinFixedOctets,Counter64,read-only,,current,,Count of corrected octets in this interval.
.1.3.6.1.2.1.10.97.1.1.7.1.7,VDSL-LINE-MIB::vdslChanCurr15MinBadBlks,Counter64,read-only,,current,,Count of uncorrectable blocks in this interval.
.1.3.6.1.2.1.10.97.1.1.7.1.8,VDSL-LINE-MIB::vdslChan1DayValidIntervals,Integer32,read-only,,current,,Valid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.7.1.9,VDSL-LINE-MIB::vdslChan1DayInvalidIntervals,Integer32,read-only,,current,,Invalid Intervals per definition found in HC-PerfHist-TC-MIB.
.1.3.6.1.2.1.10.97.1.1.7.1.10,VDSL-LINE-MIB::vdslChanCurr1DayTimeElapsed,Integer32,read-only,,current,,Number of seconds that have elapsed since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.7.1.11,VDSL-LINE-MIB::vdslChanCurr1DayFixedOctets,Counter64,read-only,,current,,Count of corrected octets since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.7.1.12,VDSL-LINE-MIB::vdslChanCurr1DayBadBlks,Counter64,read-only,,current,,Count of uncorrectable blocks since the beginning of the current 1-day interval.
.1.3.6.1.2.1.10.97.1.1.8,VDSL-LINE-MIB::vdslChanIntervalTable,,not-accessible,,current,,This table provides one row for each Vtu channel data collection interval. VDSL channel interfaces are those ifEntries where ifType is equal to interleave(124) or fast(125).
.1.3.6.1.2.1.10.97.1.1.8.1,VDSL-LINE-MIB::vdslChanIntervalEntry,,not-accessible,ifIndex:vdslPhysSide:vdslChanIntervalNumber,current,,An entry in the vdslChanIntervalTable.
.1.3.6.1.2.1.10.97.1.1.8.1.1,VDSL-LINE-MIB::vdslChanIntervalNumber,Unsigned32,not-accessible,,current,,Performance Data Interval number 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2 to 96 are optional.
.1.3.6.1.2.1.10.97.1.1.8.1.2,VDSL-LINE-MIB::vdslChanIntervalFixedOctets,Counter64,read-only,,current,,Count of corrected octets in this interval.
.1.3.6.1.2.1.10.97.1.1.8.1.3,VDSL-LINE-MIB::vdslChanIntervalBadBlks,Counter64,read-only,,current,,Count of uncorrectable blocks in this interval.
.1.3.6.1.2.1.10.97.1.1.9,VDSL-LINE-MIB::vdslChan1DayIntervalTable,,not-accessible,,current,,This table provides one row for each VDSL performance data collection interval. This table contains live data from equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.10.97.1.1.9.1,VDSL-LINE-MIB::vdslChan1DayIntervalEntry,,not-accessible,ifIndex:vdslPhysSide:vdslChan1DayIntervalNumber,current,,An entry in the vdslChan1DayIntervalTable.
.1.3.6.1.2.1.10.97.1.1.9.1.1,VDSL-LINE-MIB::vdslChan1DayIntervalNumber,Unsigned32,not-accessible,,current,,History Data Interval number. Interval 1 is the most recent previous day; interval 30 is 30 days ago. Intervals 2 to 30 are optional.
.1.3.6.1.2.1.10.97.1.1.9.1.2,VDSL-LINE-MIB::vdslChan1DayIntervalMoniSecs,Integer32,read-only,,current,,The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason.
.1.3.6.1.2.1.10.97.1.1.9.1.3,VDSL-LINE-MIB::vdslChan1DayIntervalFixedOctets,Counter64,read-only,,current,,Count of corrected octets in this interval.
.1.3.6.1.2.1.10.97.1.1.9.1.4,VDSL-LINE-MIB::vdslChan1DayIntervalBadBlks,Counter64,read-only,,current,,Count of uncorrectable blocks in this interval.
.1.3.6.1.2.1.10.97.1.1.11,VDSL-LINE-MIB::vdslLineConfProfileTable,,not-accessible,,current,,This table contains information on the VDSL line configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the VDSL line. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.97.1.1.11.1,VDSL-LINE-MIB::vdslLineConfProfileEntry,,not-accessible,vdslLineConfProfileName,current,,Each entry consists of a list of parameters that represents the configuration of a VDSL line. A default profile with an index of 'DEFVAL', will always exist and its parameters will be set to vendor specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.97.1.1.11.1.1,VDSL-LINE-MIB::vdslLineConfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table. A default profile with an index of 'DEFVAL', will always exist and its parameters will be set to vendor specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.97.1.1.11.1.2,VDSL-LINE-MIB::vdslLineConfDownRateMode,INTEGER,read-create,,current,manual(1):adaptAtInit(2),Specifies the rate selection behavior for the line in the downstream direction. manual(1) forces the rate to the configured rate adaptAtInit(2) adapts the line based upon line quality.
.1.3.6.1.2.1.10.97.1.1.11.1.3,VDSL-LINE-MIB::vdslLineConfUpRateMode,INTEGER,read-create,,current,manual(1):adaptAtInit(2),Specifies the rate selection behavior for the line in the upstream direction. manual(1) forces the rate to the configured rate adaptAtInit(2) adapts the line based upon line quality.
.1.3.6.1.2.1.10.97.1.1.11.1.4,VDSL-LINE-MIB::vdslLineConfDownMaxPwr,Unsigned32,read-create,,current,,Specifies the maximum aggregate downstream power level in the range 0 to 14.5 dBm.
.1.3.6.1.2.1.10.97.1.1.11.1.5,VDSL-LINE-MIB::vdslLineConfUpMaxPwr,Unsigned32,read-create,,current,,Specifies the maximum aggregate upstream power level in the range 0 to 14.5 dBm.
.1.3.6.1.2.1.10.97.1.1.11.1.6,VDSL-LINE-MIB::vdslLineConfDownMaxSnrMgn,Unsigned32,read-create,,current,,Specifies the maximum downstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
.1.3.6.1.2.1.10.97.1.1.11.1.7,VDSL-LINE-MIB::vdslLineConfDownMinSnrMgn,Unsigned32,read-create,,current,,Specifies the minimum downstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
.1.3.6.1.2.1.10.97.1.1.11.1.8,VDSL-LINE-MIB::vdslLineConfDownTargetSnrMgn,Unsigned32,read-create,,current,,Specifies the target downstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB. This is the Noise Margin the transceivers must achieve with a BER of 10^-7 or better to successfully complete initialization.
.1.3.6.1.2.1.10.97.1.1.11.1.9,VDSL-LINE-MIB::vdslLineConfUpMaxSnrMgn,Unsigned32,read-create,,current,,Specifies the maximum upstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
.1.3.6.1.2.1.10.97.1.1.11.1.10,VDSL-LINE-MIB::vdslLineConfUpMinSnrMgn,Unsigned32,read-create,,current,,Specifies the minimum upstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB.
.1.3.6.1.2.1.10.97.1.1.11.1.11,VDSL-LINE-MIB::vdslLineConfUpTargetSnrMgn,Unsigned32,read-create,,current,,Specifies the target upstream Signal/Noise Margin in units of 0.25 dB, for a range of 0 to 31.75 dB. This is the Noise Margin the transceivers must achieve with a BER of 10^-7 or better to successfully complete initialization.
.1.3.6.1.2.1.10.97.1.1.11.1.12,VDSL-LINE-MIB::vdslLineConfDownFastMaxDataRate,Unsigned32,read-create,,current,,Specifies the maximum downstream fast channel data rate in steps of 1000 bits/second.
.1.3.6.1.2.1.10.97.1.1.11.1.13,VDSL-LINE-MIB::vdslLineConfDownFastMinDataRate,Unsigned32,read-create,,current,,Specifies the minimum downstream fast channel data rate in steps of 1000 bits/second.
.1.3.6.1.2.1.10.97.1.1.11.1.14,VDSL-LINE-MIB::vdslLineConfDownSlowMaxDataRate,Unsigned32,read-create,,current,,Specifies the maximum downstream slow channel data rate in steps of 1000 bits/second. The maximum aggregate downstream transmit speed of the line can be derived from the sum of maximum downstream fast and slow channel data rates.
.1.3.6.1.2.1.10.97.1.1.11.1.15,VDSL-LINE-MIB::vdslLineConfDownSlowMinDataRate,Unsigned32,read-create,,current,,Specifies the minimum downstream slow channel data rate in steps of 1000 bits/second. The minimum aggregate downstream transmit speed of the line can be derived from the sum of minimum downstream fast and slow channel data rates.
.1.3.6.1.2.1.10.97.1.1.11.1.16,VDSL-LINE-MIB::vdslLineConfUpFastMaxDataRate,Unsigned32,read-create,,current,,Specifies the maximum upstream fast channel data rate in steps of 1000 bits/second. The maximum aggregate upstream transmit speed of the line can be derived from the sum of maximum upstream fast and slow channel data rates.
.1.3.6.1.2.1.10.97.1.1.11.1.17,VDSL-LINE-MIB::vdslLineConfUpFastMinDataRate,Unsigned32,read-create,,current,,Specifies the minimum upstream fast channel data rate in steps of 1000 bits/second. The minimum aggregate upstream transmit speed of the line can be derived from the sum of minimum upstream fast and slow channel data rates.
.1.3.6.1.2.1.10.97.1.1.11.1.18,VDSL-LINE-MIB::vdslLineConfUpSlowMaxDataRate,Unsigned32,read-create,,current,,Specifies the maximum upstream slow channel data rate in steps of 1000 bits/second.
.1.3.6.1.2.1.10.97.1.1.11.1.19,VDSL-LINE-MIB::vdslLineConfUpSlowMinDataRate,Unsigned32,read-create,,current,,Specifies the minimum upstream slow channel data rate in steps of 1000 bits/second.
.1.3.6.1.2.1.10.97.1.1.11.1.20,VDSL-LINE-MIB::vdslLineConfDownRateRatio,Unsigned32,read-create,,current,,For dynamic rate adaptation at startup, the allocation of data rate in excess of the minimum data rate for each channel is controlled by the object. This object specifies the ratio of the allocation of the excess data rate between the fast and the slow channels. This allocation represents downstream Fast Channel Allocation / Slow Channel Allocation.
.1.3.6.1.2.1.10.97.1.1.11.1.21,VDSL-LINE-MIB::vdslLineConfUpRateRatio,Unsigned32,read-create,,current,,For dynamic rate adaptation at startup, the allocation of data rate in excess of the minimum data rate for each channel is controlled by the object. This object specifies the ratio of the allocation of the excess data rate between the fast and the slow channels. This allocation represents upstream Fast Channel Allocation/Slow Channel Allocation.
.1.3.6.1.2.1.10.97.1.1.11.1.22,VDSL-LINE-MIB::vdslLineConfDownMaxInterDelay,Unsigned32,read-create,,current,,Specifies the maximum interleave delay for the downstream slow channel.
.1.3.6.1.2.1.10.97.1.1.11.1.23,VDSL-LINE-MIB::vdslLineConfUpMaxInterDelay,Unsigned32,read-create,,current,,Specifies the maximum interleave delay for the upstream slow channel.
.1.3.6.1.2.1.10.97.1.1.11.1.24,VDSL-LINE-MIB::vdslLineConfDownPboControl,INTEGER,read-create,,current,disabled(1):auto(2):manual(3),Downstream power backoff (PBO) control for this line. For transceivers which do not support downstream PBO control, this object MUST be fixed at disabled(1). If auto(2) is selected, the transceiver will automatically adjust the power backoff. If manual(3) is selected, then the transceiver will use the value from vdslLineConfDownPboLevel.
.1.3.6.1.2.1.10.97.1.1.11.1.25,VDSL-LINE-MIB::vdslLineConfUpPboControl,INTEGER,read-create,,current,disabled(1):auto(2):manual(3),Upstream power backoff (PBO) control for this line. For transceivers which do not support upstream PBO control, this object MUST be fixed at disabled(1). If auto(2) is selected, the transceiver will automatically adjust the power backoff. If manual(3) is selected, then the transceiver will use the value from vdslLineConfUpPboLevel.
.1.3.6.1.2.1.10.97.1.1.11.1.26,VDSL-LINE-MIB::vdslLineConfDownPboLevel,Unsigned32,read-create,,current,,Specifies the downstream backoff level to be used when vdslLineConfDownPboControl = manual(3).
.1.3.6.1.2.1.10.97.1.1.11.1.27,VDSL-LINE-MIB::vdslLineConfUpPboLevel,Unsigned32,read-create,,current,,Specifies the upstream backoff level to be used when vdslLineConfUpPboControl = manual(3).
.1.3.6.1.2.1.10.97.1.1.11.1.28,VDSL-LINE-MIB::vdslLineConfDeploymentScenario,INTEGER,read-create,,current,fttCab(1):fttEx(2):other(3),The VDSL line deployment scenario. When using fttCab(1), the VTU-C is located in a street cabinet. When using fttEx(2), the VTU-C is located at the central office. Changes to this value will have no effect on the transceiver.
.1.3.6.1.2.1.10.97.1.1.11.1.29,VDSL-LINE-MIB::vdslLineConfAdslPresence,INTEGER,read-create,,current,none(1):adslOverPots(2):adslOverISDN(3),Indicates presence of ADSL service in the associated cable bundle/binder. none(1) indicates no ADSL service in the bundle adslOverPots(2) indicates ADSL service over POTS is present in the bundle adslOverISDN(3) indicates ADSL service over ISDN is present in the bundle
.1.3.6.1.2.1.10.97.1.1.11.1.30,VDSL-LINE-MIB::vdslLineConfApplicableStandard,INTEGER,read-create,,current,ansi(1):etsi(2):itu(3):other(4),The VDSL standard to be used for the line. ansi(1) indicates ANSI standard etsi(2) indicates ETSI standard itu(3) indicates ITU standard other(4) indicates a standard other than the above.
.1.3.6.1.2.1.10.97.1.1.11.1.31,VDSL-LINE-MIB::vdslLineConfBandPlan,INTEGER,read-create,,current,bandPlan997(1):bandPlan998(2):bandPlanFx(3):other(4),The VDSL band plan to be used for the line. bandPlan997(1) is to be used for ITU-T G.993.1 Bandplan-B ETSI Bandplan ANSI Plan 997 bandPlan998(2) is to be used for ITU-T G.993.1 Bandplan-A ANSI Plan 998 bandPlanFx(3) is to be used for ITU-T G.993.1 Bandplan-C. other(4) is to be used for non-standard bandplans. If this object is set to bandPlanFx(3), then the object vdslLineConfBandPlanFx MUST also be set.
.1.3.6.1.2.1.10.97.1.1.11.1.32,VDSL-LINE-MIB::vdslLineConfBandPlanFx,Unsigned32,read-create,,current,,The frequency limit between bands D2 and U2 when vdslLineConfBandPlan is set to bandPlanFx(3).
.1.3.6.1.2.1.10.97.1.1.11.1.33,VDSL-LINE-MIB::vdslLineConfBandOptUsage,INTEGER,read-create,,current,unused(1):upstream(2):downstream(3),Defines the VDSL link use of the optional frequency range [25kHz - 138kHz] (Opt). unused(1) indicates Opt is unused upstream(2) indicates Opt usage is for upstream downstream(3) indicates Opt usage is for downstream.
.1.3.6.1.2.1.10.97.1.1.11.1.34,VDSL-LINE-MIB::vdslLineConfUpPsdTemplate,INTEGER,read-create,,current,templateMask1(1):templateMask2(2),The upstream PSD template to be used for the line. Here, templateMask1(1) refers to a notched mask that limits the transmitted PSD within the internationally standardized HAM (Handheld Amateur Radio) radio bands, while templateMask2(2) refers to an unnotched mask. The masks themselves depend upon the applicable standard being used (vdslLineConfApplicableStandard).
.1.3.6.1.2.1.10.97.1.1.11.1.35,VDSL-LINE-MIB::vdslLineConfDownPsdTemplate,INTEGER,read-create,,current,templateMask1(1):templateMask2(2),The downstream PSD template to be used for the line. Here, templateMask1(1) refers to a notched mask that limits the transmitted PSD within the internationally standardized HAM (Handheld Amateur Radio) radio bands, while templateMask2(2) refers to an unnotched mask. The masks themselves depend upon the applicable standard being used (vdslLineConfApplicableStandard).
.1.3.6.1.2.1.10.97.1.1.11.1.36,VDSL-LINE-MIB::vdslLineConfHamBandMask,BITS,read-create,,current,customNotch1(0):customNotch2(1):amateurBand30m(2):amateurBand40m(3):amateurBand80m(4):amateurBand160m(5),The transmit power spectral density mask code, used to avoid interference with HAM (Handheld Amateur Radio) radio bands by introducing power control (notching) in one or more of these bands. Amateur radio band notching is defined in the VDSL spectrum as follows: Band Start Frequency Stop Frequency ---- ------------------ -------------------------------- 30m 1810 kHz 2000 kHz 40m 3500 kHz 3800 kHz (ETSI); 4000 kHz (ANSI) 80m 7000 kHz 7100 kHz (ETSI); 7300 kHz (ANSI) 160m 10100 kHz 10150 kHz Notching for each standard band can be enabled or disabled via the bit mask. Two custom notches may be specified. If either of these are enabled via the bit mask, then the following objects MUST be specified: If customNotch1 is enabled, then both vdslLineConfCustomNotch1Start vdslLineConfCustomNotch1Stop MUST be specified. If customNotch2 is enabled, then both vdslLineConfCustomNotch2Start vdslLineConfCustomNotch2Stop MUST be specified.
.1.3.6.1.2.1.10.97.1.1.11.1.37,VDSL-LINE-MIB::vdslLineConfCustomNotch1Start,Unsigned32,read-create,,current,,Specifies the start frequency of custom HAM (Handheld Amateur Radio) notch 1. vdslLineConfCustomNotch1Start MUST be less than or equal to vdslLineConfCustomNotch1Stop.
.1.3.6.1.2.1.10.97.1.1.11.1.38,VDSL-LINE-MIB::vdslLineConfCustomNotch1Stop,Unsigned32,read-create,,current,,Specifies the stop frequency of custom HAM (Handheld Amateur Radio) notch 1. vdslLineConfCustomNotch1Stop MUST be greater than or equal to vdslLineConfCustomNotch1Start.
.1.3.6.1.2.1.10.97.1.1.11.1.39,VDSL-LINE-MIB::vdslLineConfCustomNotch2Start,Unsigned32,read-create,,current,,Specifies the start frequency of custom HAM (Handheld Amateur Radio) notch 2. vdslLineConfCustomNotch2Start MUST be less than or equal to vdslLineConfCustomNotch2Stop.
.1.3.6.1.2.1.10.97.1.1.11.1.40,VDSL-LINE-MIB::vdslLineConfCustomNotch2Stop,Unsigned32,read-create,,current,,Specifies the stop frequency of custom HAM (Handheld Amateur Radio) notch 2. vdslLineConfCustomNotch2Stop MUST be greater than or equal to vdslLineConfCustomNotch2Start.
.1.3.6.1.2.1.10.97.1.1.11.1.41,VDSL-LINE-MIB::vdslLineConfDownTargetSlowBurst,Unsigned32,read-create,,current,,Specifies the target level of impulse noise (burst) protection for an interleaved (slow) channel.
.1.3.6.1.2.1.10.97.1.1.11.1.42,VDSL-LINE-MIB::vdslLineConfUpTargetSlowBurst,Unsigned32,read-create,,current,,Specifies the target level of impulse noise (burst) protection for an interleaved (slow) channel.
.1.3.6.1.2.1.10.97.1.1.11.1.43,VDSL-LINE-MIB::vdslLineConfDownMaxFastFec,Unsigned32,read-create,,current,,This parameter provisions the maximum level of Forward Error Correction (FEC) redundancy related overhead to be maintained for a fast channel.
.1.3.6.1.2.1.10.97.1.1.11.1.44,VDSL-LINE-MIB::vdslLineConfUpMaxFastFec,Unsigned32,read-create,,current,,This parameter provisions the maximum level of Forward Error Correction (FEC) redundancy related overhead to be maintained for a fast channel.
.1.3.6.1.2.1.10.97.1.1.11.1.45,VDSL-LINE-MIB::vdslLineConfLineType,INTEGER,read-create,,current,noChannel(1):fastOnly(2):interleavedOnly(3):fastOrInterleaved(4):fastAndInterleaved(5),This parameter provisions the VDSL physical entity at start-up by defining whether and how the line will be channelized, i.e., which channel type(s) are supported. If the line is to be channelized, the value will be other than noChannel(1). This configuration can be activated only during start-up. Afterwards, the value of vdslLineType coincides with the value of vdslLineConfLineType. Depending on this value, the corresponding entries in the ifTable for the interleaved and the fast channels are enabled or disabled according to the value of their ifOperStatus. Defined values are: noChannel(1) -- no channels exist fastOnly(2) -- only fast channel exists interleavedOnly(3) -- only interleaved channel exists fastOrInterleaved(4) -- either fast or interleaved channel -- exists, but only one at a time fastAndInterleaved(5) -- both fast and interleaved channels -- exist Note that 'slow' and 'interleaved' refer to the same channel.
.1.3.6.1.2.1.10.97.1.1.11.1.46,VDSL-LINE-MIB::vdslLineConfProfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'outOfService'), it must be first unreferenced from all associated lines. An 'active' profile may be modified at any time. Note that some changes may require that any referenced lines be restarted (e.g., vdslLineConfLineType).
.1.3.6.1.2.1.10.97.1.1.20,VDSL-LINE-MIB::vdslLineAlarmConfProfileTable,,not-accessible,,current,,This table contains information on the VDSL line alarm configuration. One entry in this table reflects a profile defined by a manager which can be used to configure the VDSL line alarm thresholds. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.97.1.1.20.1,VDSL-LINE-MIB::vdslLineAlarmConfProfileEntry,,not-accessible,vdslLineAlarmConfProfileName,current,,Each entry consists of a list of parameters that represents the configuration of a VDSL line alarm profile. A default profile with an index of 'DEFVAL', will always exist and its parameters will be set to vendor specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.97.1.1.20.1.1,VDSL-LINE-MIB::vdslLineAlarmConfProfileName,OCTET,not-accessible,,current,,The name for this profile as specified by an administrator.
.1.3.6.1.2.1.10.97.1.1.20.1.2,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinLofs,Unsigned32,read-create,,current,,This object configures the threshold for the number of loss of frame seconds (lofs) within any given 15-minute performance data collection interval. If the value of loss of frame seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfLofsThreshNotification notification will be generated. No more than one notification will be sent per interval.
.1.3.6.1.2.1.10.97.1.1.20.1.3,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinLoss,Unsigned32,read-create,,current,,This object configures the threshold for the number of loss of signal seconds (loss) within any given 15-minute performance data collection interval. If the value of loss of signal seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfLossThreshNotification notification will be generated. One notification will be sent per interval per endpoint.
.1.3.6.1.2.1.10.97.1.1.20.1.4,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinLprs,Unsigned32,read-create,,current,,This object configures the threshold for the number of loss of power seconds (lprs) within any given 15-minute performance data collection interval. If the value of loss of power seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfLprsThreshNotification notification will be generated. No more than one notification will be sent per interval.
.1.3.6.1.2.1.10.97.1.1.20.1.5,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinLols,Unsigned32,read-create,,current,,This object configures the threshold for the number of loss of link seconds (lols) within any given 15-minute performance data collection interval. If the value of loss of power seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfLolsThreshNotification notification will be generated. No more than one notification will be sent per interval.
.1.3.6.1.2.1.10.97.1.1.20.1.6,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinESs,Unsigned32,read-create,,current,,This object configures the threshold for the number of errored seconds (ESs) within any given 15-minute performance data collection interval. If the value of errored seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfESsThreshNotification notification will be generated. No more than one notification will be sent per interval.
.1.3.6.1.2.1.10.97.1.1.20.1.7,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinSESs,Unsigned32,read-create,,current,,This object configures the threshold for the number of severely errored seconds (SESs) within any given 15-minute performance data collection interval. If the value of severely errored seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfSESsThreshNotification notification will be generated. No more than one notification will be sent per interval.
.1.3.6.1.2.1.10.97.1.1.20.1.8,VDSL-LINE-MIB::vdslLineAlarmConfThresh15MinUASs,Unsigned32,read-create,,current,,This object configures the threshold for the number of unavailable seconds (UASs) within any given 15-minute performance data collection interval. If the value of unavailable seconds in a particular 15-minute collection interval reaches/exceeds this value, a vdslPerfUASsThreshNotification notification will be generated. No more than one notification will be sent per interval.
.1.3.6.1.2.1.10.97.1.1.20.1.9,VDSL-LINE-MIB::vdslLineAlarmConfInitFailure,INTEGER,read-create,,current,true(1):false(2),This object specifies if a vdslInitFailureNotification notification will be generated if an initialization failure occurs.
.1.3.6.1.2.1.10.97.1.1.20.1.10,VDSL-LINE-MIB::vdslLineAlarmConfProfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service, (by setting this object to 'destroy' or 'outOfService') it must be first unreferenced from all associated lines. An 'active' profile may be modified at any time.
.1.3.6.1.2.1.10.97.1.3,VDSL-LINE-MIB::vdslConformance,,,,,,
.1.3.6.1.2.1.10.97.1.3.1,VDSL-LINE-MIB::vdslGroups,,,,,,
.1.3.6.1.2.1.10.97.1.3.1.1,VDSL-LINE-MIB::vdslGroup,,,,,,A collection of objects providing information about a VDSL Line.
.1.3.6.1.2.1.10.97.1.3.1.2,VDSL-LINE-MIB::vdslNotificationGroup,,,,,,This group supports notifications of significant conditions associated with VDSL Lines.
.1.3.6.1.2.1.10.97.1.3.2,VDSL-LINE-MIB::vdslCompliances,,,,,,
.1.3.6.1.2.1.10.97.1.3.2.1,VDSL-LINE-MIB::vdslLineMibCompliance,,,,,,The compliance statement for SNMP entities which manage VDSL interfaces.
.1.3.6.1.2.1.10.127,DOCS-IF-MIB::docsIfMib,,,,,,This is the MIB Module for DOCSIS 2.0-compliant Radio Frequency (RF) interfaces in Cable Modems and Cable Modem Termination Systems. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4546; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.127.1,DOCS-IF-MIB::docsIfMibObjects,,,,,,
.1.3.6.1.2.1.10.127.1.1,DOCS-IF-MIB::docsIfBaseObjects,,,,,,
.1.3.6.1.2.1.10.127.1.1.1,DOCS-IF-MIB::docsIfDownstreamChannelTable,,not-accessible,,current,,This table describes the attributes of downstream channels (frequency bands).
.1.3.6.1.2.1.10.127.1.1.1.1,DOCS-IF-MIB::docsIfDownstreamChannelEntry,,not-accessible,ifIndex,current,,An entry provides a list of attributes for a single downstream channel. An entry in this table exists for each ifEntry with an ifType of docsCableDownstream(128).
.1.3.6.1.2.1.10.127.1.1.1.1.1,DOCS-IF-MIB::docsIfDownChannelId,Integer32,read-only,,current,,The Cable Modem Termination System identification of the downstream channel within this particular MAC interface. if the interface is down, the object returns the most current value. If the downstream channel ID is unknown, this object returns a value of 0.
.1.3.6.1.2.1.10.127.1.1.1.1.2,DOCS-IF-MIB::docsIfDownChannelFrequency,Integer32,read-write,,current,,The center of the downstream frequency associated with this channel. This object will return the current tuner frequency. If a CMTS provides IF output, this object will return 0, unless this CMTS is in control of the final downstream frequency. See the associated compliance object for a description of valid frequencies that may be written to this object.
.1.3.6.1.2.1.10.127.1.1.1.1.3,DOCS-IF-MIB::docsIfDownChannelWidth,Integer32,read-write,,current,,The bandwidth of this downstream channel. Most implementations are expected to support a channel width of 6 MHz (North America) and/or 8 MHz (Europe). See the associated compliance object for a description of the valid channel widths for this object.
.1.3.6.1.2.1.10.127.1.1.1.1.4,DOCS-IF-MIB::docsIfDownChannelModulation,INTEGER,read-write,,current,unknown(1):other(2):qam64(3):qam256(4),The modulation type associated with this downstream channel. If the interface is down, this object either returns the configured value (CMTS), the most current value (CM), or the value of unknown(1). See the associated conformance object for write conditions and limitations. See the reference for specifics on the modulation profiles implied by qam64 and qam256.
.1.3.6.1.2.1.10.127.1.1.1.1.5,DOCS-IF-MIB::docsIfDownChannelInterleave,INTEGER,read-write,,current,unknown(1):other(2):taps8Increment16(3):taps16Increment8(4):taps32Increment4(5):taps64Increment2(6):taps128Increment1(7):taps12increment17(8),The Forward Error Correction (FEC) interleaving used for this downstream channel. Values are defined as follows: taps8Increment16(3): protection 5.9/4.1 usec, latency .22/.15 msec taps16Increment8(4): protection 12/8.2 usec, latency .48/.33 msec taps32Increment4(5): protection 24/16 usec, latency .98/.68 msec taps64Increment2(6): protection 47/33 usec, latency 2/1.4 msec taps128Increment1(7): protection 95/66 usec, latency 4/2.8 msec taps12increment17(8): protection 18/14 usec, latency 0.43/0.32 msec The value 'taps12increment17' is supported by EuroDOCSIS cable systems only, and the others by DOCSIS cable systems. If the interface is down, this object either returns the configured value (CMTS), the most current value (CM), or the value of unknown(1). The value of other(2) is returned if the interleave is known but not defined in the above list. See the associated conformance object for write conditions and limitations. See the reference for the FEC configuration described by the setting of this object.
.1.3.6.1.2.1.10.127.1.1.1.1.6,DOCS-IF-MIB::docsIfDownChannelPower,Integer32,read-write,,current,,At the CMTS, the operational transmit power. At the CM, the received power level. If the interface is down, this object either returns the configured value (CMTS), the most current value (CM) or the value of 0. See the associated conformance object for write conditions and limitations. See the reference for recommended and required power levels.
.1.3.6.1.2.1.10.127.1.1.1.1.7,DOCS-IF-MIB::docsIfDownChannelAnnex,INTEGER,read-only,,current,unknown(1):other(2):annexA(3):annexB(4):annexC(5),The value of this object indicates the conformance of the implementation to important regional cable standards. annexA : Annex A from ITU-T J.83 is used. (equivalent to EN 300 429) annexB : Annex B from ITU-T J.83 is used. annexC : Annex C from ITU-T J.83 is used.
.1.3.6.1.2.1.10.127.1.1.1.1.8,DOCS-IF-MIB::docsIfDownChannelStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-write objects.
.1.3.6.1.2.1.10.127.1.1.2,DOCS-IF-MIB::docsIfUpstreamChannelTable,,not-accessible,,current,,This table describes the attributes of attached upstream channels.
.1.3.6.1.2.1.10.127.1.1.2.1,DOCS-IF-MIB::docsIfUpstreamChannelEntry,,not-accessible,ifIndex,current,,List of attributes for a single upstream channel. For DOCSIS 2.0 CMTSs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstreamChannel (205). For DOCSIS 1.x CM/CMTSs and DOCSIS 2.0 CMs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstream (129). For DOCSIS 2.0 CMTSs, two classes of interfaces can be defined for this table: o Upstream Physical Interfaces: The traditional DOCSIS 1.x CMTS upstream interface ifType 129 and the DOCSIS 2.0 ifType 205 that are functional. In other words, interfaces that represent upstream receivers within an RF MAC interface. Entries of physical interfaces are exposed to the management interface with their corresponding ifStack hierarchy and are not administratively created by this table. o Upstream Temporary Interfaces: A fictitious interface created for the purpose of manipulating physical interface parameters offline, then validating prior to updating the target physical interface. In case of a reinitialization of the managed system, physical interfaces values persist while the temporary interfaces are not recreated. This mechanism helps to minimize service disruptions originating in situations where a group of interface parameter values need to be consistent with each other in SET operations. A temporary buffer (temporary interface) is provided to allow the CMTS to validate the parameters offline.
.1.3.6.1.2.1.10.127.1.1.2.1.1,DOCS-IF-MIB::docsIfUpChannelId,Integer32,read-only,,current,,The CMTS identification of the upstream channel.
.1.3.6.1.2.1.10.127.1.1.2.1.2,DOCS-IF-MIB::docsIfUpChannelFrequency,Integer32,read-create,,current,,The center of the frequency band associated with this upstream interface. This object returns 0 if the frequency is undefined or unknown. Minimum permitted upstream frequency is 5,000,000 Hz for current technology. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.3,DOCS-IF-MIB::docsIfUpChannelWidth,Integer32,read-create,,current,,The bandwidth of this upstream interface. This object returns 0 if the interface width is undefined or unknown. Minimum permitted interface width is currently 200,000 Hz. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.4,DOCS-IF-MIB::docsIfUpChannelModulationProfile,Unsigned32,read-create,,current,,An entry identical to the docsIfModIndex in the docsIfCmtsModulationTable that describes this channel. This channel is further instantiated there by a grouping of interval usage codes (IUCs) that, together, fully describe the channel modulation. This object returns 0 if the docsIfCmtsModulationTable entry does not exist or is empty. See the associated conformance object for write conditions and limitations. Setting this object returns an 'inconsistentValue' error if the following conditions are not satisfied: 1. All the IUC entries in the selected modulation profile MUST have the same value of docsIfCmtsModChannelType. 2. All of the Modulation parameters in the selected modulation profile MUST be consistent with the other parameters in this docsIfUpstreamChannelEntry.
.1.3.6.1.2.1.10.127.1.1.2.1.5,DOCS-IF-MIB::docsIfUpChannelSlotSize,Unsigned32,read-create,,current,,Applicable to TDMA and ATDMA channel types only. The number of 6.25 microsecond ticks in each upstream mini-slot. Returns zero if the value is undefined or unknown or in case of an SCDMA channel. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.6,DOCS-IF-MIB::docsIfUpChannelTxTimingOffset,Unsigned32,read-only,,current,,At the CM, a measure of the current round trip time obtained from the ranging offset (initial ranging offset + ranging offset adjustments). At the CMTS, the maximum of timing offset, among all the CMs that are/were present on the channel, taking into account all ( initial + periodic ) timing offset corrections that were sent for each of the CMs. Generally, these measurements are positive, but if the measurements are negative, the value of this object is zero. Used for timing of CM upstream transmissions to ensure synchronized arrivals at the CMTS. Units are one 64th fraction of 6.25 microseconds.
.1.3.6.1.2.1.10.127.1.1.2.1.7,DOCS-IF-MIB::docsIfUpChannelRangingBackoffStart,Integer32,read-create,,current,,The initial random backoff window to use when retrying Ranging Requests. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.8,DOCS-IF-MIB::docsIfUpChannelRangingBackoffEnd,Integer32,read-create,,current,,The final random backoff window to use when retrying Ranging Requests. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.9,DOCS-IF-MIB::docsIfUpChannelTxBackoffStart,Integer32,read-create,,current,,The initial random backoff window to use when retrying transmissions. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.10,DOCS-IF-MIB::docsIfUpChannelTxBackoffEnd,Integer32,read-create,,current,,The final random backoff window to use when retrying transmissions. Expressed as a power of 2. A value of 16 at the CMTS indicates that a proprietary adaptive retry mechanism is to be used. See the associated conformance object for write conditions and limitations.
.1.3.6.1.2.1.10.127.1.1.2.1.11,DOCS-IF-MIB::docsIfUpChannelScdmaActiveCodes,Unsigned32,read-create,,current,,Applicable for SCDMA channel types only. Number of active codes. Returns zero for Non-SCDMA channel types. Note that legal values from 64..128 MUST be non-prime.
.1.3.6.1.2.1.10.127.1.1.2.1.12,DOCS-IF-MIB::docsIfUpChannelScdmaCodesPerSlot,Integer32,read-create,,current,,Applicable for SCDMA channel types only. The number of SCDMA codes per mini-slot. Returns zero if the value is undefined or unknown or in case of a TDMA or ATDMA channel.
.1.3.6.1.2.1.10.127.1.1.2.1.13,DOCS-IF-MIB::docsIfUpChannelScdmaFrameSize,Unsigned32,read-create,,current,,Applicable for SCDMA channel types only. SCDMA Frame size in units of spreading intervals. This value returns zero for non-SCDMA Profiles.
.1.3.6.1.2.1.10.127.1.1.2.1.14,DOCS-IF-MIB::docsIfUpChannelScdmaHoppingSeed,Unsigned32,read-create,,current,,Applicable for SCDMA channel types only. 15-bit seed used for code hopping sequence initialization. Returns zero for non-SCDMA channel types. Setting this value to a value different than zero for non-SCDMA channel types returns the error 'wrongValue'.
.1.3.6.1.2.1.10.127.1.1.2.1.15,DOCS-IF-MIB::docsIfUpChannelType,INTEGER,read-only,,current,unknown(0):tdma(1):atdma(2):scdma(3):tdmaAndAtdma(4),Reflects the Upstream channel type. This object returns the value of docsIfCmtsModChannelType for the modulation profile selected in docsIfUpChannelModulationProfile for this row.
.1.3.6.1.2.1.10.127.1.1.2.1.16,DOCS-IF-MIB::docsIfUpChannelCloneFrom,Integer32,read-create,,current,,This object contains the ifIndex value of the physical interface row entry whose parameters are to be adjusted. Upon setting this object to the ifIndex value of a physical interface, the following interface objects values are copied to this entry: docsIfUpChannelFrequency, docsIfUpChannelWidth, docsIfUpChannelModulationProfile, docsIfUpChannelSlotSize, docsIfUpChannelRangingBackoffStart, docsIfUpChannelRangingBackoffEnd, docsIfUpChannelTxBackoffStart, docsIfUpChannelTxBackoffEnd, docsIfUpChannelScdmaActiveCodes, docsIfUpChannelScdmaCodesPerSlot, docsIfUpChannelScdmaFrameSize, docsIfUpChannelScdmaHoppingSeed, docsIfUpChannelType, and docsIfUpChannelPreEqEnable Setting this object to the value of a non-existent or a temporary upstream interface returns the error 'wrongValue'. This object MUST contain a value of zero for physical interfaces entries. Setting this object in row entries that correspond to physical interfaces returns the error 'wrongValue'.
.1.3.6.1.2.1.10.127.1.1.2.1.17,DOCS-IF-MIB::docsIfUpChannelUpdate,INTEGER,read-create,,current,true(1):false(2),Used to perform the copy of adjusted parameters from the temporary interface entry to the physical interface indicated by the docsIfUpChannelCloneFrom object. The transfer is initiated through an SNMP SET to 'true' of this object. A SET to 'true' fails and returns error 'commitFailed' if docsIfUpChannelStatus value is 'notInService', which means that the interface parameters values are not compatible with each other or have not been validated yet. Reading this object always returns 'false'.
.1.3.6.1.2.1.10.127.1.1.2.1.18,DOCS-IF-MIB::docsIfUpChannelStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is only used for the creation of a temporary upstream row with the purpose of updating the parameters of a physical upstream channel entry. The following restrictions apply to this object: 1. This object is not writable for physical interfaces. 2. Temporary interface entries are only created by a SET of this object to createandWait(5). 3. ifAdminStatus from the Interface MIB RFC 2863 is used to take a physical upstream channel offline, to be consistent with DOCSIS 1.x operation, as indicated in RFC 2670. In addition, o ifAdminStatus 'down' is reflected in this object as 'notInService'. o ifOperStatus 'down' while ifAdminStatus 'up' is reflected in this object as 'notInservice'. 4. Temporary created rows MUST be set to 'active' with the purpose of validating upstream parameter consistency prior to transferring the parameters to the physical interface. Below is a mandatory procedure for adjusting the values of a physical interface: 1. Create a temporary interface entry through an SNMP SET using 'createAndWait'. At this point, the RowStatus reports 'notReady'. The Manager entity uses an ifIndex value outside the operational range of the physical interfaces for the creation of a temporary interface. 2. Set the docsIfUpChannelCloneFrom object to the ifIndex value of the physical row to update. Now docsIfUpChannelStatus reports 'notInService'. 3. Change the upstream parameters to the desired values in the temporary row. 4. Validate that all parameters are consistent by setting docsIfUpChannelStatus to 'active'. A failure to set the RowStatus to 'active' returns the error 'commitFailed', which means the parameters are not compatible with the target physical interface. 5. With docsIfUpChannelStatus 'active', transfer the parameters to the target physical interface by setting the object docsIfUpChannelUpdate to 'true'. 6. Delete the temporary row by setting docsIfUpChannelStatus to 'destroy'.
.1.3.6.1.2.1.10.127.1.1.2.1.19,DOCS-IF-MIB::docsIfUpChannelPreEqEnable,INTEGER,read-create,,current,true(1):false(2),At the CMTS, this object is used to enable or disable pre-equalization on the upstream channel represented by this table instance. At the CM, this object is read-only and reflects the status of pre-equalization as represented in the RNG-RSP. Pre-equalization is considered enabled at the CM if a RNG-RSP with pre-equalization data has been received at least once since the last mac reinitialization.
.1.3.6.1.2.1.10.127.1.1.3,DOCS-IF-MIB::docsIfQosProfileTable,,not-accessible,,current,,Describes the attributes for each class of service.
.1.3.6.1.2.1.10.127.1.1.3.1,DOCS-IF-MIB::docsIfQosProfileEntry,,not-accessible,docsIfQosProfIndex,current,,Describes the attributes for a single class of service. If implemented as read-create in the Cable Modem Termination System, creation of entries in this table is controlled by the value of docsIfCmtsQosProfilePermissions. If implemented as read-only, entries are created based on information in REG-REQ MAC messages received from cable modems (for Cable Modem Termination System), or based on information extracted from the TFTP option file (for Cable Modem). In the Cable Modem Termination System, read-only entries are removed if no longer referenced by docsIfCmtsServiceTable. An entry in this table MUST not be removed while it is referenced by an entry in docsIfCmServiceTable (Cable Modem) or docsIfCmtsServiceTable (Cable Modem Termination System). An entry in this table SHOULD NOT be changeable while it is referenced by an entry in docsIfCmtsServiceTable. If this table is created automatically, there SHOULD only be a single entry for each Class of Service. Multiple entries with the same Class of Service parameters are NOT RECOMMENDED.
.1.3.6.1.2.1.10.127.1.1.3.1.1,DOCS-IF-MIB::docsIfQosProfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies an entry in the docsIfQosProfileTable.
.1.3.6.1.2.1.10.127.1.1.3.1.2,DOCS-IF-MIB::docsIfQosProfPriority,Integer32,read-create,,current,,A relative priority assigned to this service when allocating bandwidth. Zero indicates lowest priority and seven indicates highest priority. Interpretation of priority is device-specific. MUST NOT be changed while this row is active.
.1.3.6.1.2.1.10.127.1.1.3.1.3,DOCS-IF-MIB::docsIfQosProfMaxUpBandwidth,Integer32,read-create,,current,,The maximum upstream bandwidth, in bits per second, allowed for a service with this service class. Zero if there is no restriction of upstream bandwidth. MUST NOT be changed while this row is active.
.1.3.6.1.2.1.10.127.1.1.3.1.4,DOCS-IF-MIB::docsIfQosProfGuarUpBandwidth,Integer32,read-create,,current,,Minimum guaranteed upstream bandwidth, in bits per second, allowed for a service with this service class. MUST NOT be changed while this row is active.
.1.3.6.1.2.1.10.127.1.1.3.1.5,DOCS-IF-MIB::docsIfQosProfMaxDownBandwidth,Integer32,read-create,,current,,The maximum downstream bandwidth, in bits per second, allowed for a service with this service class. Zero if there is no restriction of downstream bandwidth. MUST NOT be changed while this row is active.
.1.3.6.1.2.1.10.127.1.1.3.1.6,DOCS-IF-MIB::docsIfQosProfMaxTxBurst,Integer32,read-create,,deprecated,,The maximum number of mini-slots that may be requested for a single upstream transmission. A value of zero means there is no limit. MUST NOT be changed while this row is active. This object has been deprecated and replaced by docsIfQosProfMaxTransmitBurst, to fix a mismatch of the units and value range with respect to the DOCSIS Maximum Upstream Channel Transmit Burst Configuration Setting.
.1.3.6.1.2.1.10.127.1.1.3.1.7,DOCS-IF-MIB::docsIfQosProfBaselinePrivacy,INTEGER,read-create,,current,true(1):false(2),Indicates whether Baseline Privacy is enabled for this service class. MUST NOT be changed while this row is active.
.1.3.6.1.2.1.10.127.1.1.3.1.8,DOCS-IF-MIB::docsIfQosProfStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This is object is used to create or delete rows in this table. This object MUST NOT be changed from active while the row is referenced by any entry in either docsIfCmServiceTable (on the CM) or docsIfCmtsServiceTable (on the CMTS).
.1.3.6.1.2.1.10.127.1.1.3.1.9,DOCS-IF-MIB::docsIfQosProfMaxTransmitBurst,Integer32,read-create,,current,,The maximum number of bytes that may be requested for a single upstream transmission. A value of zero means there is no limit. Note: This value does not include any physical layer overhead. MUST NOT be changed while this row is active.
.1.3.6.1.2.1.10.127.1.1.3.1.10,DOCS-IF-MIB::docsIfQosProfStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for writable objects.
.1.3.6.1.2.1.10.127.1.1.4,DOCS-IF-MIB::docsIfSignalQualityTable,,not-accessible,,current,,At the CM, describes the PHY signal quality of downstream channels. At the CMTS, this object describes the PHY signal quality of upstream channels. At the CMTS, this table MAY exclude contention intervals.
.1.3.6.1.2.1.10.127.1.1.4.1,DOCS-IF-MIB::docsIfSignalQualityEntry,,not-accessible,ifIndex,current,,At the CM, this object describes the PHY characteristics of a downstream channel. At the CMTS, it describes the PHY signal quality of an upstream channel. An entry in this table exists for each ifEntry with an ifType of docsCableDownstream(128) for Cable Modems. For DOCSIS 1.1 Cable Modem Termination Systems, an entry exists for each ifEntry with an ifType of docsCableUpstream (129). For DOCSIS 2.0 Cable Modem Termination Systems, an entry exists for each ifEntry with an ifType of docsCableUpstreamChannel (205).
.1.3.6.1.2.1.10.127.1.1.4.1.1,DOCS-IF-MIB::docsIfSigQIncludesContention,INTEGER,read-only,,current,true(1):false(2),true(1) if this CMTS includes contention intervals in the counters in this table. Always false(2) for CMs.
.1.3.6.1.2.1.10.127.1.1.4.1.2,DOCS-IF-MIB::docsIfSigQUnerroreds,Counter32,read-only,,current,,Codewords received on this channel without error. This includes all codewords, whether or not they were part of frames destined for this device. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.1.4.1.3,DOCS-IF-MIB::docsIfSigQCorrecteds,Counter32,read-only,,current,,Codewords received on this channel with correctable errors. This includes all codewords, whether or not they were part of frames destined for this device. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.1.4.1.4,DOCS-IF-MIB::docsIfSigQUncorrectables,Counter32,read-only,,current,,Codewords received on this channel with uncorrectable errors. This includes all codewords, whether or not they were part of frames destined for this device. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.1.4.1.5,DOCS-IF-MIB::docsIfSigQSignalNoise,Integer32,read-only,,current,,Signal/Noise ratio as perceived for this channel. At the CM, this object describes the Signal/Noise of the downstream channel. At the CMTS, it describes the average Signal/Noise of the upstream channel.
.1.3.6.1.2.1.10.127.1.1.4.1.6,DOCS-IF-MIB::docsIfSigQMicroreflections,Integer32,read-only,,current,,Microreflections, including in-channel response as perceived on this interface, measured in dBc below the signal level. This object is not assumed to return an absolutely accurate value, but it gives a rough indication of microreflections received on this interface. It is up to the implementer to provide information as accurately as possible.
.1.3.6.1.2.1.10.127.1.1.4.1.7,DOCS-IF-MIB::docsIfSigQEqualizationData,OCTET,read-only,,current,,At the CM, this object returns the equalization data for the downstream channel. At the CMTS, this object is not applicable and is not instantiated. Note that previous CMTS implementations may instantiate this object in two ways: - An equalization value indicating an equalization average for the upstream channel. Those values have vendor-dependent interpretations. - Return a zero-length OCTET STRING to indicate that the value is unknown or if there is no equalization data available or defined.
.1.3.6.1.2.1.10.127.1.1.4.1.8,DOCS-IF-MIB::docsIfSigQExtUnerroreds,Counter64,read-only,,current,,Codewords received on this channel without error. This includes all codewords, whether or not they were part of frames destined for this device. This is the 64-bit version of docsIfSigQUnerroreds. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.1.4.1.9,DOCS-IF-MIB::docsIfSigQExtCorrecteds,Counter64,read-only,,current,,Codewords received on this channel with correctable errors. This includes all codewords, whether or not they were part of frames destined for this device. This is the 64-bit version of docsIfSigQCorrecteds. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.1.4.1.10,DOCS-IF-MIB::docsIfSigQExtUncorrectables,Counter64,read-only,,current,,Codewords received on this channel with uncorrectable errors. This includes all codewords, whether or not they were part of frames destined for this device. This is the 64-bit version of docsIfSigQUncorrectables. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.1.5,DOCS-IF-MIB::docsIfDocsisBaseCapability,INTEGER,read-only,,current,docsis10(1):docsis11(2):docsis20(3),Indication of the DOCSIS capability of the device.
.1.3.6.1.2.1.10.127.1.2,DOCS-IF-MIB::docsIfCmObjects,,,,,,
.1.3.6.1.2.1.10.127.1.2.1,DOCS-IF-MIB::docsIfCmMacTable,,not-accessible,,current,,Describes the attributes of each CM MAC interface, extending the information available from ifEntry.
.1.3.6.1.2.1.10.127.1.2.1.1,DOCS-IF-MIB::docsIfCmMacEntry,,not-accessible,ifIndex,current,,An entry containing objects describing attributes of each MAC entry, extending the information in ifEntry. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.10.127.1.2.1.1.1,DOCS-IF-MIB::docsIfCmCmtsAddress,OCTET,read-only,,current,,Identifies the CMTS that is believed to control this MAC domain. At the CM, this will be the source address from SYNC, MAP, and other MAC-layer messages. If the CMTS is unknown, returns 00-00-00-00-00-00.
.1.3.6.1.2.1.10.127.1.2.1.1.2,DOCS-IF-MIB::docsIfCmCapabilities,BITS,read-only,,current,atmCells(0):concatenation(1),Identifies the capabilities of the MAC implementation at this interface. Note that packet transmission is always supported. Therefore, there is no specific bit required to explicitly indicate this capability. Note that BITS objects are encoded most significant bit first. For example, if bit 1 is set, the value of this object is the octet string '40'H.
.1.3.6.1.2.1.10.127.1.2.1.1.3,DOCS-IF-MIB::docsIfCmRangingRespTimeout,TimeTicks,read-write,,obsolete,,Waiting time for a Ranging Response packet. This object has been obsoleted and replaced by docsIfCmRangingTimeout to correct the typing to TimeInterval.
.1.3.6.1.2.1.10.127.1.2.1.1.4,DOCS-IF-MIB::docsIfCmRangingTimeout,INTEGER,read-write,,current,,Waiting time for a Ranging Response packet. This object MUST NOT persist at reinitialization of the managed system.
.1.3.6.1.2.1.10.127.1.2.2,DOCS-IF-MIB::docsIfCmStatusTable,,not-accessible,,current,,This table maintains a number of status objects and counters for Cable Modems.
.1.3.6.1.2.1.10.127.1.2.2.1,DOCS-IF-MIB::docsIfCmStatusEntry,,not-accessible,ifIndex,current,,A set of status objects and counters for a single MAC layer instance in Cable Modem. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.10.127.1.2.2.1.1,DOCS-IF-MIB::docsIfCmStatusValue,INTEGER,read-only,,current,other(1):notReady(2):notSynchronized(3):phySynchronized(4):usParametersAcquired(5):rangingComplete(6):ipComplete(7):todEstablished(8):securityEstablished(9):paramTransferComplete(10):registrationComplete(11):operational(12):accessDenied(13),Current Cable Modem connectivity state, as specified in the RF Interface Specification. Interpretations for state values 1-12 are clearly outlined in the SP-RFI reference given below. The state value accessDenied(13) indicates the CMTS has sent a Registration Aborted message to the CM. The same state is reported as accessDenied(7) by the CMTS object docsIfCmtsCmStatusValue.
.1.3.6.1.2.1.10.127.1.2.2.1.2,DOCS-IF-MIB::docsIfCmStatusCode,OCTET,read-only,,current,,Status code for a Cable Modem as defined in the OSSI Specification. The status code consists of a single character indicating error groups, followed by a two- or three-digit number indicating the status condition, followed by a decimal. An example of a returned value could be 'T101.0'. The zero-length OCTET STRING indicates no status code yet registered.
.1.3.6.1.2.1.10.127.1.2.2.1.3,DOCS-IF-MIB::docsIfCmStatusTxPower,Integer32,read-only,,current,,The operational transmit power for the attached upstream channel.
.1.3.6.1.2.1.10.127.1.2.2.1.4,DOCS-IF-MIB::docsIfCmStatusResets,Counter32,read-only,,current,,Number of times the CM reset or initialized this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.5,DOCS-IF-MIB::docsIfCmStatusLostSyncs,Counter32,read-only,,current,,Number of times the CM lost synchronization with the downstream channel. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.6,DOCS-IF-MIB::docsIfCmStatusInvalidMaps,Counter32,read-only,,current,,Number of times the CM received invalid MAP messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.7,DOCS-IF-MIB::docsIfCmStatusInvalidUcds,Counter32,read-only,,current,,Number of times the CM received invalid UCD messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.8,DOCS-IF-MIB::docsIfCmStatusInvalidRangingResponses,Counter32,read-only,,current,,Number of times the CM received invalid ranging response messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.9,DOCS-IF-MIB::docsIfCmStatusInvalidRegistrationResponses,Counter32,read-only,,current,,Number of times the CM received invalid registration response messages. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.10,DOCS-IF-MIB::docsIfCmStatusT1Timeouts,Counter32,read-only,,current,,Number of times counter T1 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.11,DOCS-IF-MIB::docsIfCmStatusT2Timeouts,Counter32,read-only,,current,,Number of times counter T2 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.12,DOCS-IF-MIB::docsIfCmStatusT3Timeouts,Counter32,read-only,,current,,Number of times counter T3 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.13,DOCS-IF-MIB::docsIfCmStatusT4Timeouts,Counter32,read-only,,current,,Number of times counter T4 expired in the CM. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.14,DOCS-IF-MIB::docsIfCmStatusRangingAborteds,Counter32,read-only,,current,,Number of times the ranging process was aborted by the CMTS. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.15,DOCS-IF-MIB::docsIfCmStatusDocsisOperMode,INTEGER,read-only,,current,docsis10(1):docsis11(2),Indication of whether the device has registered using 1.0 Class of Service or 1.1 Quality of Service. An unregistered CM SHOULD indicate 'docsis11' for a docsIfDocsisBaseCapability value of DOCSIS 1.1/2.0. An unregistered CM SHOULD indicate 'docsis10' for a docsIfDocsisBaseCapability value of DOCSIS 1.0.
.1.3.6.1.2.1.10.127.1.2.2.1.16,DOCS-IF-MIB::docsIfCmStatusModulationType,INTEGER,read-only,,current,unknown(0):tdma(1):atdma(2):scdma(3):tdmaAndAtdma(4),Indicates modulation type status currently used by the CM. Since this object specifically identifies PHY mode, the shared upstream channel type is not permitted.
.1.3.6.1.2.1.10.127.1.2.2.1.17,DOCS-IF-MIB::docsIfCmStatusEqualizationData,OCTET,read-only,,current,,Pre-equalization data for this CM after convolution with data indicated in the RNG-RSP. This data is valid when docsIfUpChannelPreEqEnable is set to true.
.1.3.6.1.2.1.10.127.1.2.2.1.18,DOCS-IF-MIB::docsIfCmStatusUCCs,Counter32,read-only,,current,,The number of successful Upstream Channel Change transactions. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.2.1.19,DOCS-IF-MIB::docsIfCmStatusUCCFails,Counter32,read-only,,current,,The number of failed Upstream Channel Change transactions. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3,DOCS-IF-MIB::docsIfCmServiceTable,,not-accessible,,current,,Describes the attributes of each upstream service queue on a CM.
.1.3.6.1.2.1.10.127.1.2.3.1,DOCS-IF-MIB::docsIfCmServiceEntry,,not-accessible,ifIndex:docsIfCmServiceId,current,,Describes the attributes of an upstream bandwidth service queue. An entry in this table exists for each Service ID. The primary index is an ifIndex with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.10.127.1.2.3.1.1,DOCS-IF-MIB::docsIfCmServiceId,Integer32,not-accessible,,current,,Identifies a service queue for upstream bandwidth. The attributes of this service queue are shared between the CM and the CMTS. The CMTS allocates upstream bandwidth to this service queue based on requests from the CM and on the class of service associated with this queue.
.1.3.6.1.2.1.10.127.1.2.3.1.2,DOCS-IF-MIB::docsIfCmServiceQosProfile,Integer32,read-only,,current,,The index in docsIfQosProfileTable describing the quality of service attributes associated with this particular service. If no associated entry in docsIfQosProfileTable exists, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.2.3.1.3,DOCS-IF-MIB::docsIfCmServiceTxSlotsImmed,Counter32,read-only,,current,,The number of upstream mini-slots that have been used to transmit data PDUs in immediate (contention) mode. This includes only those PDUs that are presumed to have arrived at the head-end (i.e., those that were explicitly acknowledged). It does not include retransmission attempts or mini-slots used by requests. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.4,DOCS-IF-MIB::docsIfCmServiceTxSlotsDed,Counter32,read-only,,current,,The number of upstream mini-slots that have been used to transmit data PDUs in dedicated mode (i.e., as a result of a unicast Data Grant). Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.5,DOCS-IF-MIB::docsIfCmServiceTxRetries,Counter32,read-only,,current,,The number of attempts to transmit data PDUs containing requests for acknowledgment that did not result in acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.6,DOCS-IF-MIB::docsIfCmServiceTxExceededs,Counter32,read-only,,current,,The number of data PDU transmission failures due to excessive retries without acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.7,DOCS-IF-MIB::docsIfCmServiceRqRetries,Counter32,read-only,,current,,The number of attempts to transmit bandwidth requests that did not result in acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.8,DOCS-IF-MIB::docsIfCmServiceRqExceededs,Counter32,read-only,,current,,The number of requests for bandwidth that failed due to excessive retries without acknowledgment. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.9,DOCS-IF-MIB::docsIfCmServiceExtTxSlotsImmed,Counter64,read-only,,current,,The number of upstream mini-slots that have been used to transmit data PDUs in immediate (contention) mode. This includes only those PDUs that are presumed to have arrived at the head-end (i.e., those that were explicitly acknowledged). It does not include retransmission attempts or mini-slots used by requests. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.2.3.1.10,DOCS-IF-MIB::docsIfCmServiceExtTxSlotsDed,Counter64,read-only,,current,,The number of upstream mini-slots that have been used to transmit data PDUs in dedicated mode (i.e., as a result of a unicast Data Grant). Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3,DOCS-IF-MIB::docsIfCmtsObjects,,,,,,
.1.3.6.1.2.1.10.127.1.3.1,DOCS-IF-MIB::docsIfCmtsMacTable,,not-accessible,,current,,Describes the attributes of each CMTS MAC interface, extending the information available from ifEntry. Mandatory for all CMTS devices.
.1.3.6.1.2.1.10.127.1.3.1.1,DOCS-IF-MIB::docsIfCmtsMacEntry,,not-accessible,ifIndex,current,,An entry containing objects describing attributes of each MAC entry, extending the information in ifEntry. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.10.127.1.3.1.1.1,DOCS-IF-MIB::docsIfCmtsCapabilities,BITS,read-only,,current,atmCells(0):concatenation(1),Identifies the capabilities of the CMTS MAC implementation at this interface. Note that packet transmission is always supported. Therefore, there is no specific bit required to explicitly indicate this capability. Note that BITS objects are encoded most significant bit first. For example, if bit 1 is set, the value of this object is the octet string '40'H.
.1.3.6.1.2.1.10.127.1.3.1.1.2,DOCS-IF-MIB::docsIfCmtsSyncInterval,Integer32,read-write,,current,,The interval between CMTS transmission of successive SYNC messages at this interface.
.1.3.6.1.2.1.10.127.1.3.1.1.3,DOCS-IF-MIB::docsIfCmtsUcdInterval,Integer32,read-write,,current,,The interval between CMTS transmission of successive Upstream Channel Descriptor messages for each upstream channel at this interface.
.1.3.6.1.2.1.10.127.1.3.1.1.4,DOCS-IF-MIB::docsIfCmtsMaxServiceIds,Integer32,read-only,,current,,The maximum number of service IDs that may be simultaneously active.
.1.3.6.1.2.1.10.127.1.3.1.1.5,DOCS-IF-MIB::docsIfCmtsInsertionInterval,TimeTicks,read-write,,obsolete,,The amount of time to elapse between each broadcast initial maintenance grant. Broadcast initial maintenance grants are used to allow new cable modems to join the network. Zero indicates that a vendor-specific algorithm is used instead of a fixed time. The maximum amount of time permitted by the specification is 2 seconds. This object has been obsoleted and replaced by docsIfCmtsInsertInterval to fix a SYNTAX typing problem.
.1.3.6.1.2.1.10.127.1.3.1.1.6,DOCS-IF-MIB::docsIfCmtsInvitedRangingAttempts,Integer32,read-write,,current,,The maximum number of attempts to make on invitations for ranging requests. A value of zero means the system SHOULD attempt to range forever.
.1.3.6.1.2.1.10.127.1.3.1.1.7,DOCS-IF-MIB::docsIfCmtsInsertInterval,INTEGER,read-write,,current,,The amount of time to elapse between each broadcast initial maintenance grant. Broadcast initial maintenance grants are used to allow new cable modems to join the network. Zero indicates that a vendor-specific algorithm is used instead of a fixed time. The maximum amount of time permitted by the specification is 2 seconds.
.1.3.6.1.2.1.10.127.1.3.1.1.8,DOCS-IF-MIB::docsIfCmtsMacStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-write objects.
.1.3.6.1.2.1.10.127.1.3.2,DOCS-IF-MIB::docsIfCmtsStatusTable,,not-accessible,,current,,For the MAC layer, this group maintains a number of status objects and counters.
.1.3.6.1.2.1.10.127.1.3.2.1,DOCS-IF-MIB::docsIfCmtsStatusEntry,,not-accessible,ifIndex,current,,Status entry for a single MAC layer. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.10.127.1.3.2.1.1,DOCS-IF-MIB::docsIfCmtsStatusInvalidRangeReqs,Counter32,read-only,,current,,This object counts invalid RNG-REQ messages received on this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.2.1.2,DOCS-IF-MIB::docsIfCmtsStatusRangingAborteds,Counter32,read-only,,current,,This object counts ranging attempts that were explicitly aborted by the CMTS. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.2.1.3,DOCS-IF-MIB::docsIfCmtsStatusInvalidRegReqs,Counter32,read-only,,current,,This object counts invalid REG-REQ messages received on this interface; that is, syntax, out of range parameters, or erroneous requests. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.2.1.4,DOCS-IF-MIB::docsIfCmtsStatusFailedRegReqs,Counter32,read-only,,current,,This object counts failed registration attempts. Included are docsIfCmtsStatusInvalidRegReqs, authentication, and class of service failures. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.2.1.5,DOCS-IF-MIB::docsIfCmtsStatusInvalidDataReqs,Counter32,read-only,,current,,This object counts invalid data request messages received on this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.2.1.6,DOCS-IF-MIB::docsIfCmtsStatusT5Timeouts,Counter32,read-only,,current,,This object counts the number of times counter T5 expired on this interface. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3,DOCS-IF-MIB::docsIfCmtsCmStatusTable,,not-accessible,,current,,A set of objects in the CMTS, maintained for each cable modem connected to this CMTS.
.1.3.6.1.2.1.10.127.1.3.3.1,DOCS-IF-MIB::docsIfCmtsCmStatusEntry,,not-accessible,docsIfCmtsCmStatusIndex,current,,Status information for a single cable modem. An entry in this table exists for each cable modem that is connected to the CMTS implementing this table.
.1.3.6.1.2.1.10.127.1.3.3.1.1,DOCS-IF-MIB::docsIfCmtsCmStatusIndex,Integer32,not-accessible,,current,,Index value to uniquely identify an entry in this table. For an individual cable modem, this index value SHOULD NOT change during CMTS uptime.
.1.3.6.1.2.1.10.127.1.3.3.1.2,DOCS-IF-MIB::docsIfCmtsCmStatusMacAddress,OCTET,read-only,,current,,MAC address of the cable modem. If the cable modem has multiple MAC addresses, this is the MAC address associated with the Cable interface.
.1.3.6.1.2.1.10.127.1.3.3.1.3,DOCS-IF-MIB::docsIfCmtsCmStatusIpAddress,IpAddress,read-only,,deprecated,,IP address of this cable modem. If the cable modem has no IP address assigned, or the IP address is unknown, this object returns a value of 0.0.0.0. If the cable modem has multiple IP addresses, this object returns the IP address associated with the Cable interface. This object has been deprecated and replaced by docsIfCmtsCmStatusInetAddressType and docsIfCmtsCmStatusInetAddress, to enable IPv6 addressing in the future.
.1.3.6.1.2.1.10.127.1.3.3.1.4,DOCS-IF-MIB::docsIfCmtsCmStatusDownChannelIfIndex,Integer32,read-only,,current,,IfIndex of the downstream channel that this CM is connected to. If the downstream channel is unknown, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.3.3.1.5,DOCS-IF-MIB::docsIfCmtsCmStatusUpChannelIfIndex,Integer32,read-only,,current,,For DOCSIS 2.0, indicates the ifIndex of the logical upstream channel (ifType 205) this CM is connected to. For DOCSIS 1.x, indicates the ifIndex of the upstream channel (ifType 129) this CM is connected to. If the upstream channel is unknown, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.3.3.1.6,DOCS-IF-MIB::docsIfCmtsCmStatusRxPower,Integer32,read-only,,current,,The receive power as perceived for upstream data from this cable modem. If the receive power is unknown, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.3.3.1.7,DOCS-IF-MIB::docsIfCmtsCmStatusTimingOffset,Unsigned32,read-only,,current,,A measure of the current round trip time for this CM. Used for timing of CM upstream transmissions to ensure synchronized arrivals at the CMTS. Units are in terms of (6.25 microseconds/64). Returns zero if the value is unknown. For channels requiring finer resolution, please refer to object docsIfCmtsCmStatusHighResolutionTimingOffset.
.1.3.6.1.2.1.10.127.1.3.3.1.8,DOCS-IF-MIB::docsIfCmtsCmStatusEqualizationData,OCTET,read-only,,current,,Equalization data for this CM, as measured by the CMTS. Returns the zero-length OCTET STRING if the value is unknown or if there is no equalization data available or defined.
.1.3.6.1.2.1.10.127.1.3.3.1.9,DOCS-IF-MIB::docsIfCmtsCmStatusValue,INTEGER,read-only,,current,other(1):ranging(2):rangingAborted(3):rangingComplete(4):ipComplete(5):registrationComplete(6):accessDenied(7):operational(8):registeredBPIInitializing(9),Current cable modem connectivity state, as specified in the RF Interface Specification. Returned status information is the CM status, as assumed by the CMTS, and indicates the following events: other(1) Any state other than below. ranging(2) The CMTS has received an Initial Ranging Request message from the CM, and the ranging process is not yet complete. rangingAborted(3) The CMTS has sent a Ranging Abort message to the CM. rangingComplete(4) The CMTS has sent a Ranging Complete message to the CM. ipComplete(5) The CMTS has received a DHCP reply message and forwarded it to the CM. registrationComplete(6) The CMTS has sent a Registration Response message to the CM. accessDenied(7) The CMTS has sent a Registration Aborted message to the CM. operational(8) Value 8 is considered reserved and should not be defined in future revisions of this MIB module to avoid conflict with documented implementations that support value 8 to indicate operational state after completing the BPI initialization process. registeredBPIInitializing(9) Baseline Privacy (BPI) is enabled and the CMTS is in the process of completing BPI initialization. This state MAY last for a significant length of time if failures occur during the initialization process. After completion of BPI initialization, the CMTS will report registrationComplete(6). The CMTS only needs to report states it is able to detect.
.1.3.6.1.2.1.10.127.1.3.3.1.10,DOCS-IF-MIB::docsIfCmtsCmStatusUnerroreds,Counter32,read-only,,current,,Codewords received without error from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.11,DOCS-IF-MIB::docsIfCmtsCmStatusCorrecteds,Counter32,read-only,,current,,Codewords received with correctable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.12,DOCS-IF-MIB::docsIfCmtsCmStatusUncorrectables,Counter32,read-only,,current,,Codewords received with uncorrectable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.13,DOCS-IF-MIB::docsIfCmtsCmStatusSignalNoise,Integer32,read-only,,current,,Signal/Noise ratio as perceived for upstream data from this cable modem. If the Signal/Noise is unknown, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.3.3.1.14,DOCS-IF-MIB::docsIfCmtsCmStatusMicroreflections,Integer32,read-only,,current,,Total microreflections, including in-channel response as perceived on this interface, measured in dBc below the signal level. This object is not assumed to return an absolutely accurate value, but it gives a rough indication of microreflections received on this interface. It is up to the implementer to provide information as accurately as possible. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.15,DOCS-IF-MIB::docsIfCmtsCmStatusExtUnerroreds,Counter64,read-only,,current,,Codewords received without error from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.16,DOCS-IF-MIB::docsIfCmtsCmStatusExtCorrecteds,Counter64,read-only,,current,,Codewords received with correctable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.17,DOCS-IF-MIB::docsIfCmtsCmStatusExtUncorrectables,Counter64,read-only,,current,,Codewords received with uncorrectable errors from this cable modem. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.3.1.18,DOCS-IF-MIB::docsIfCmtsCmStatusDocsisRegMode,INTEGER,read-only,,current,docsis10(1):docsis11(2),Indication of whether the CM has registered using 1.0 Class of Service or 1.1 Quality of Service.
.1.3.6.1.2.1.10.127.1.3.3.1.19,DOCS-IF-MIB::docsIfCmtsCmStatusModulationType,INTEGER,read-only,,current,unknown(0):tdma(1):atdma(2):scdma(3):tdmaAndAtdma(4),Indicates modulation type currently used by the CM. Since this object specifically identifies PHY mode, the shared type is not permitted. If the upstream channel is unknown, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.3.3.1.20,DOCS-IF-MIB::docsIfCmtsCmStatusInetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of internet address of docsIfCmtsCmStatusInetAddress. If the cable modem internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.127.1.3.3.1.21,DOCS-IF-MIB::docsIfCmtsCmStatusInetAddress,OCTET,read-only,,current,,Internet address of this cable modem. If the Cable Modem has no Internet address assigned, or the Internet address is unknown, the value of this object is the zero-length OCTET STRING. If the cable modem has multiple Internet addresses, this object returns the Internet address associated with the Cable (i.e., RF MAC) interface.
.1.3.6.1.2.1.10.127.1.3.3.1.22,DOCS-IF-MIB::docsIfCmtsCmStatusValueLastUpdate,TimeTicks,read-only,,current,,The value of sysUpTime when docsIfCmtsCmStatusValue was last updated.
.1.3.6.1.2.1.10.127.1.3.3.1.23,DOCS-IF-MIB::docsIfCmtsCmStatusHighResolutionTimingOffset,Unsigned32,read-only,,current,,A measure of the current round trip time for this CM. Used for timing of CM upstream transmissions to ensure synchronized arrivals at the CMTS. Units are in terms of (6.25 microseconds/(64*256)). Returns zero if the value is unknown. This is the high resolution version of object docsIfCmtsCmStatusTimingOffset, for channels requiring finer resolution.
.1.3.6.1.2.1.10.127.1.3.4,DOCS-IF-MIB::docsIfCmtsServiceTable,,not-accessible,,current,,Describes the attributes of upstream service queues in a Cable Modem Termination System.
.1.3.6.1.2.1.10.127.1.3.4.1,DOCS-IF-MIB::docsIfCmtsServiceEntry,,not-accessible,ifIndex:docsIfCmtsServiceId,current,,Describes the attributes of a single upstream bandwidth service queue. Entries in this table exist for each ifEntry with an ifType of docsCableMaclayer(127), and for each service queue (Service ID) within this MAC layer. Entries in this table are created with the creation of individual Service IDs by the MAC layer and removed when a Service ID is removed.
.1.3.6.1.2.1.10.127.1.3.4.1.1,DOCS-IF-MIB::docsIfCmtsServiceId,Integer32,not-accessible,,current,,Identifies a service queue for upstream bandwidth. The attributes of this service queue are shared between the Cable Modem and the Cable Modem Termination System. The CMTS allocates upstream bandwidth to this service queue based on requests from the CM and on the class of service associated with this queue.
.1.3.6.1.2.1.10.127.1.3.4.1.2,DOCS-IF-MIB::docsIfCmtsServiceCmStatusIndex,Integer32,read-only,,deprecated,,Pointer to an entry in docsIfCmtsCmStatusTable identifying the cable modem using this Service Queue. If multiple cable modems are using this Service Queue, the value of this object is zero. This object has been deprecated and replaced by docsIfCmtsServiceNewCmStatusIndex, to fix a mismatch of the value range with respect to docsIfCmtsCmStatusIndex (1..2147483647).
.1.3.6.1.2.1.10.127.1.3.4.1.3,DOCS-IF-MIB::docsIfCmtsServiceAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2):destroyed(3),Allows a service class for a particular modem to be suppressed, (re-)enabled, or deleted altogether.
.1.3.6.1.2.1.10.127.1.3.4.1.4,DOCS-IF-MIB::docsIfCmtsServiceQosProfile,Integer32,read-only,,current,,The index in docsIfQosProfileTable describing the quality of service attributes associated with this particular service. If no associated docsIfQosProfileTable entry exists, this object returns a value of zero.
.1.3.6.1.2.1.10.127.1.3.4.1.5,DOCS-IF-MIB::docsIfCmtsServiceCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was created.
.1.3.6.1.2.1.10.127.1.3.4.1.6,DOCS-IF-MIB::docsIfCmtsServiceInOctets,Counter32,read-only,,current,,The cumulative number of Packet Data octets received on this Service ID. The count does not include the size of the Cable MAC header. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.4.1.7,DOCS-IF-MIB::docsIfCmtsServiceInPackets,Counter32,read-only,,current,,The cumulative number of Packet Data packets received on this Service ID. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.4.1.8,DOCS-IF-MIB::docsIfCmtsServiceNewCmStatusIndex,Integer32,read-only,,current,,Pointer (via docsIfCmtsCmStatusIndex) to an entry in docsIfCmtsCmStatusTable identifying the cable modem using this Service Queue. If multiple cable modems are using this Service Queue, the value of this object is zero.
.1.3.6.1.2.1.10.127.1.3.5,DOCS-IF-MIB::docsIfCmtsModulationTable,,not-accessible,,current,,Describes a modulation profile associated with one or more upstream channels.
.1.3.6.1.2.1.10.127.1.3.5.1,DOCS-IF-MIB::docsIfCmtsModulationEntry,,not-accessible,docsIfCmtsModIndex:docsIfCmtsModIntervalUsageCode,current,,Describes a modulation profile for an Interval Usage Code for one or more upstream channels. Entries in this table are created by the operator. Initial default entries MAY be created at system initialization time, which could report a value of 'permanent' or 'readOnly' for docsIfCmtsModStorageType. A CMTS MAY reject the creation of additional Interval Usage Codes for a modulation profile being defined at Initialization time. No individual objects have to be specified in order to create an entry in this table. Note that some objects do not have DEFVAL clauses but do have calculated defaults and need not be specified during row creation.
.1.3.6.1.2.1.10.127.1.3.5.1.1,DOCS-IF-MIB::docsIfCmtsModIndex,Integer32,not-accessible,,current,,An index into the Channel Modulation table representing a group of Interval Usage Codes, all associated with the same channel.
.1.3.6.1.2.1.10.127.1.3.5.1.2,DOCS-IF-MIB::docsIfCmtsModIntervalUsageCode,INTEGER,not-accessible,,current,request(1):requestData(2):initialRanging(3):periodicRanging(4):shortData(5):longData(6):advPhyShortData(9):advPhyLongData(10):ugs(11),An index into the Channel Modulation table that, when grouped with other Interval Usage Codes, fully instantiates all modulation sets for a given upstream channel.
.1.3.6.1.2.1.10.127.1.3.5.1.3,DOCS-IF-MIB::docsIfCmtsModControl,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Controls and reflects the status of rows in this table. There is no restriction on the changing of values in this table while their associated rows are active, with the exception of: 1. If a modulation profile is being referenced by one or more upstream channels, an attempt to set the value of docsIfCmtsModChannelType returns an 'inconsistentValue' error. 2. If a modulation profile is being referenced by one or more upstream channels, an attempt to set docsIfCmtsModControl to destroy(6) or notInService(2) returns an 'inconsistentValue' error.
.1.3.6.1.2.1.10.127.1.3.5.1.4,DOCS-IF-MIB::docsIfCmtsModType,INTEGER,read-create,,current,other(1):qpsk(2):qam16(3):qam8(4):qam32(5):qam64(6):qam128(7),The modulation type used on this channel. Returns other(1) if the modulation type is not qpsk, qam16, qam8, qam32, qam64, or qam128. Type qam128 is used for SCDMA channels only. See the reference for the modulation profiles implied by different modulation types.
.1.3.6.1.2.1.10.127.1.3.5.1.5,DOCS-IF-MIB::docsIfCmtsModPreambleLen,Integer32,read-create,,current,,The preamble length for this modulation profile in bits. Default value is the minimum needed by the implementation at the CMTS for the given modulation profile.
.1.3.6.1.2.1.10.127.1.3.5.1.6,DOCS-IF-MIB::docsIfCmtsModDifferentialEncoding,INTEGER,read-create,,current,true(1):false(2),Specifies whether or not differential encoding is used on this channel.
.1.3.6.1.2.1.10.127.1.3.5.1.7,DOCS-IF-MIB::docsIfCmtsModFECErrorCorrection,Integer32,read-create,,current,,The number of correctable errored bytes (t) used in forward error correction code. The value of 0 indicates that no correction is employed. The number of check bytes appended will be twice this value.
.1.3.6.1.2.1.10.127.1.3.5.1.8,DOCS-IF-MIB::docsIfCmtsModFECCodewordLength,Integer32,read-create,,current,,The number of data bytes (k) in the forward error correction codeword. This object is not used if docsIfCmtsModFECErrorCorrection is zero.
.1.3.6.1.2.1.10.127.1.3.5.1.9,DOCS-IF-MIB::docsIfCmtsModScramblerSeed,Integer32,read-create,,current,,The 15-bit seed value for the scrambler polynomial.
.1.3.6.1.2.1.10.127.1.3.5.1.10,DOCS-IF-MIB::docsIfCmtsModMaxBurstSize,Integer32,read-create,,current,,The maximum number of mini-slots that can be transmitted during this channel's burst time. Returns zero if the burst length is bounded by the allocation MAP rather than by this profile. Default value is 0, except for shortData, where it is 8.
.1.3.6.1.2.1.10.127.1.3.5.1.11,DOCS-IF-MIB::docsIfCmtsModGuardTimeSize,Unsigned32,read-only,,current,,The number of symbol-times that MUST follow the end of this channel's burst. Default value is the minimum time needed by the implementation for this modulation profile.
.1.3.6.1.2.1.10.127.1.3.5.1.12,DOCS-IF-MIB::docsIfCmtsModLastCodewordShortened,INTEGER,read-create,,current,true(1):false(2),Indicates whether the last FEC codeword is truncated.
.1.3.6.1.2.1.10.127.1.3.5.1.13,DOCS-IF-MIB::docsIfCmtsModScrambler,INTEGER,read-create,,current,true(1):false(2),Indicates whether the scrambler is employed.
.1.3.6.1.2.1.10.127.1.3.5.1.14,DOCS-IF-MIB::docsIfCmtsModByteInterleaverDepth,Unsigned32,read-create,,current,,ATDMA Byte Interleaver Depth (Ir). This object returns 1 for non-ATDMA profiles.
.1.3.6.1.2.1.10.127.1.3.5.1.15,DOCS-IF-MIB::docsIfCmtsModByteInterleaverBlockSize,Unsigned32,read-create,,current,,ATDMA Byte Interleaver Block size (Br). This object returns zero for non-ATDMA profiles 
.1.3.6.1.2.1.10.127.1.3.5.1.16,DOCS-IF-MIB::docsIfCmtsModPreambleType,INTEGER,read-create,,current,unknown(0):qpsk0(1):qpsk1(2),Preamble type for DOCSIS 2.0 bursts. The value 'unknown(0)' represents a row entry consisting only of DOCSIS 1.x bursts
.1.3.6.1.2.1.10.127.1.3.5.1.17,DOCS-IF-MIB::docsIfCmtsModTcmErrorCorrectionOn,INTEGER,read-create,,current,true(1):false(2),Trellis Code Modulation (TCM) On/Off. This value returns false for non-S-CDMA profiles.
.1.3.6.1.2.1.10.127.1.3.5.1.18,DOCS-IF-MIB::docsIfCmtsModScdmaInterleaverStepSize,Unsigned32,read-create,,current,, S-CDMA Interleaver step size. This value returns zero for non-S-CDMA profiles.
.1.3.6.1.2.1.10.127.1.3.5.1.19,DOCS-IF-MIB::docsIfCmtsModScdmaSpreaderEnable,INTEGER,read-create,,current,true(1):false(2), S-CDMA spreader. This value returns false for non-S-CDMA profiles. Default value for IUC 3 and 4 is OFF; for all other IUCs it is ON.
.1.3.6.1.2.1.10.127.1.3.5.1.20,DOCS-IF-MIB::docsIfCmtsModScdmaSubframeCodes,Unsigned32,read-create,,current,, S-CDMA sub-frame size. This value returns zero for non-S-CDMA profiles.
.1.3.6.1.2.1.10.127.1.3.5.1.21,DOCS-IF-MIB::docsIfCmtsModChannelType,INTEGER,read-create,,current,unknown(0):tdma(1):atdma(2):scdma(3):tdmaAndAtdma(4),Describes the modulation channel type for this modulation entry. All the active entries in a modulation profile (that is all active entries that share a common docsIfCmtsModIndex) MUST have the same value of docsIfCmtsModChannelType.
.1.3.6.1.2.1.10.127.1.3.5.1.22,DOCS-IF-MIB::docsIfCmtsModStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Entries with this object set to permanent(4) do not require write operations for read-write objects.
.1.3.6.1.2.1.10.127.1.3.6,DOCS-IF-MIB::docsIfCmtsQosProfilePermissions,BITS,read-write,,current,createByManagement(0):updateByManagement(1):createByModems(2),This object specifies permitted methods of creating entries in docsIfQosProfileTable. createByManagement(0) is set if entries can be created using SNMP. updateByManagement(1) is set if updating entries using SNMP is permitted. createByModems(2) is set if entries can be created based on information in REG-REQ MAC messages received from cable modems. Information in this object is only applicable if docsIfQosProfileTable is implemented as read-create. Otherwise, this object is implemented as read-only and returns createByModems(2). Either createByManagement(0) or updateByManagement(1) MUST be set when writing to this object. Note that BITS objects are encoded most significant bit first. For example, if bit 2 is set, the value of this object is the octet string '20'H.
.1.3.6.1.2.1.10.127.1.3.7,DOCS-IF-MIB::docsIfCmtsMacToCmTable,,not-accessible,,current,,This is a table to provide a quick access index into the docsIfCmtsCmStatusTable. There is exactly one row in this table for each row in the docsIfCmtsCmStatusTable. In general, the management station SHOULD use this table only to get a pointer into the docsIfCmtsCmStatusTable (which corresponds to the CM's RF interface MAC address) and SHOULD not iterate (e.g., GetNext through) this table.
.1.3.6.1.2.1.10.127.1.3.7.1,DOCS-IF-MIB::docsIfCmtsMacToCmEntry,,not-accessible,docsIfCmtsCmMac,current,,A row in the docsIfCmtsMacToCmTable. An entry in this table exists for each cable modem that is connected to the CMTS implementing this table.
.1.3.6.1.2.1.10.127.1.3.7.1.1,DOCS-IF-MIB::docsIfCmtsCmMac,OCTET,not-accessible,,current,,The RF side MAC address for the referenced CM (e.g., the interface on the CM that has docsCableMacLayer(127) as its ifType).
.1.3.6.1.2.1.10.127.1.3.7.1.2,DOCS-IF-MIB::docsIfCmtsCmPtr,Integer32,read-only,,current,,An row index into docsIfCmtsCmStatusTable. When queried with the correct instance value (e.g., a CM's MAC address), returns the index in docsIfCmtsCmStatusTable that represents that CM.
.1.3.6.1.2.1.10.127.1.3.8,DOCS-IF-MIB::docsIfCmtsChannelUtilizationInterval,Integer32,read-write,,current,,The time interval in seconds over which the channel utilization index is calculated. All upstream/downstream channels use the same docsIfCmtsChannelUtilizationInterval. Setting a value of zero disables utilization reporting. A channel utilization index is calculated over a fixed window applying to the most recent docsIfCmtsChannelUtilizationInterval. It would therefore be prudent to use a relatively short docsIfCmtsChannelUtilizationInterval. It is a vendor decision whether to reset the timer when docsIfCmtsChannelUtilizationInterval is changed during a utilization sampling period.
.1.3.6.1.2.1.10.127.1.3.9,DOCS-IF-MIB::docsIfCmtsChannelUtilizationTable,,not-accessible,,current,,Reports utilization statistics for attached upstream and downstream physical channels.
.1.3.6.1.2.1.10.127.1.3.9.1,DOCS-IF-MIB::docsIfCmtsChannelUtilizationEntry,,not-accessible,ifIndex:docsIfCmtsChannelUtIfType:docsIfCmtsChannelUtId,current,,Utilization statistics for a single upstream or downstream physical channel. An entry exists in this table for each ifEntry with an ifType equal to docsCableDownstream (128) or docsCableUpstream (129).
.1.3.6.1.2.1.10.127.1.3.9.1.1,DOCS-IF-MIB::docsIfCmtsChannelUtIfType,INTEGER,not-accessible,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The secondary index into this table. Indicates the IANA interface type associated with this physical channel. Only docsCableDownstream (128) and docsCableUpstream (129) are valid.
.1.3.6.1.2.1.10.127.1.3.9.1.2,DOCS-IF-MIB::docsIfCmtsChannelUtId,Integer32,not-accessible,,current,,The tertiary index into this table. Indicates the CMTS identifier for this physical channel.
.1.3.6.1.2.1.10.127.1.3.9.1.3,DOCS-IF-MIB::docsIfCmtsChannelUtUtilization,Integer32,read-only,,current,,The calculated and truncated utilization index for this physical upstream or downstream channel, accurate as of the most recent docsIfCmtsChannelUtilizationInterval. Upstream Channel Utilization Index: The upstream channel utilization index is expressed as a percentage of mini-slots utilized on the physical channel, regardless of burst type. For an Initial Maintenance region, the mini-slots for the complete region are considered utilized if the CMTS received an upstream burst within the region from any CM on the physical channel. For contention REQ and REQ/DATA regions, the mini-slots for a transmission opportunity within the region are considered utilized if the CMTS received an upstream burst within the opportunity from any CM on the physical channel. For all other regions, utilized mini-slots are those in which the CMTS granted bandwidth to any unicast SID on the physical channel. For an upstream interface that has multiple logical upstream channels enabled, the utilization index is a weighted sum of utilization indices for the logical channels. The weight for each utilization index is the percentage of upstream mini-slots allocated for the corresponding logical channel. Example: If 75% of bandwidth is allocated to the first logical channel and 25% to the second, and the utilization indices for each are 60 and 40, respectively, the utilization index for the upstream physical channel is (60 * 0.75) + (40 * 0.25) = 55. This figure applies to the most recent utilization interval. Downstream Channel Utilization Index: The downstream channel utilization index is a percentage expressing the ratio between bytes used to transmit data versus the total number of bytes transmitted in the raw bandwidth of the MPEG channel. As with the upstream utilization index, the calculated value represents the most recent utilization interval. Formula: Downstream utilization index = (100 * (data bytes / raw bytes)) Definitions: Data bytes: Number of bytes transmitted as data in the docsIfCmtsChannelUtilizationInterval. Identical to docsIfCmtsDownChannelCtrUsed Bytes measured over the utilization interval. Raw bandwidth: Total number of bytes available for transmitting data, not including bytes used for headers and other overhead. Raw bytes: (raw bandwidth * docsIfCmtsChannelUtilizationInterval). Identical to docsIfCmtsDownChannelCtrTotal Bytes measured over the utilization interval.
.1.3.6.1.2.1.10.127.1.3.10,DOCS-IF-MIB::docsIfCmtsDownChannelCounterTable,,not-accessible,,current,,This table is implemented at the CMTS to collect downstream channel statistics for utilization calculations.
.1.3.6.1.2.1.10.127.1.3.10.1,DOCS-IF-MIB::docsIfCmtsDownChannelCounterEntry,,not-accessible,ifIndex,current,,An entry provides a list of traffic counters for a single downstream channel. An entry in this table exists for each ifEntry with an ifType of docsCableDownstream(128).
.1.3.6.1.2.1.10.127.1.3.10.1.1,DOCS-IF-MIB::docsIfCmtsDownChnlCtrId,Integer32,read-only,,current,,The Cable Modem Termination System identification of the downstream channel within this particular MAC interface. If the interface is down, the object returns the most current value. If the downstream channel ID is unknown, this object returns a value of 0.
.1.3.6.1.2.1.10.127.1.3.10.1.2,DOCS-IF-MIB::docsIfCmtsDownChnlCtrTotalBytes,Counter32,read-only,,current,,At the CMTS, the total number of bytes in the Payload portion of MPEG Packets (i.e., not including MPEG header or pointer_field) transported by this downstream channel. This is the 32-bit version of docsIfCmtsDownChnlCtrExtTotalBytes, included to provide back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.10.1.3,DOCS-IF-MIB::docsIfCmtsDownChnlCtrUsedBytes,Counter32,read-only,,current,,At the CMTS, the total number of DOCSIS data bytes transported by this downstream channel. The number of data bytes is defined as the total number of bytes transported in DOCSIS payloads minus the number of stuff bytes transported in DOCSIS payloads. This is the 32-bit version of docsIfCmtsDownChnlCtrExtUsedBytes, included to provide back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.10.1.4,DOCS-IF-MIB::docsIfCmtsDownChnlCtrExtTotalBytes,Counter64,read-only,,current,,At the CMTS, the total number of bytes in the Payload portion of MPEG Packets (i.e., not including MPEG header or pointer_field) transported by this downstream channel. This is the 64-bit version of docsIfCmtsDownChnlCtrTotalBytes and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.10.1.5,DOCS-IF-MIB::docsIfCmtsDownChnlCtrExtUsedBytes,Counter64,read-only,,current,,At the CMTS, the total number of DOCSIS data bytes transported by this downstream channel. The number of data bytes is defined as the total number of bytes transported in DOCSIS payloads minus the number of stuff bytes transported in DOCSIS payloads. This is the 64-bit version of docsIfCmtsDownChnlCtrUsedBytes and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11,DOCS-IF-MIB::docsIfCmtsUpChannelCounterTable,,not-accessible,,current,,This table is implemented at the CMTS to provide upstream channel statistics appropriate for channel utilization calculations.
.1.3.6.1.2.1.10.127.1.3.11.1,DOCS-IF-MIB::docsIfCmtsUpChannelCounterEntry,,not-accessible,ifIndex,current,,List of traffic statistics for a single upstream channel. For DOCSIS 2.0 CMTSs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstreamChannel (205). For DOCSIS 1.x CMTSs, an entry in this table exists for each ifEntry with an ifType of docsCableUpstream (129).
.1.3.6.1.2.1.10.127.1.3.11.1.1,DOCS-IF-MIB::docsIfCmtsUpChnlCtrId,Integer32,read-only,,current,,The CMTS identification of the upstream channel.
.1.3.6.1.2.1.10.127.1.3.11.1.2,DOCS-IF-MIB::docsIfCmtsUpChnlCtrTotalMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of all mini-slots defined for this upstream logical channel. This count includes all IUCs and SIDs, even those allocated to the NULL SID for a 2.0 logical channel that is inactive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalMslots and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.3,DOCS-IF-MIB::docsIfCmtsUpChnlCtrUcastGrantedMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of unicast granted mini-slots on the upstream logical channel, regardless of burst type. Unicast granted mini-slots are those in which the CMTS assigned bandwidth to any unicast SID on the logical channel. However, this object does not include minis-lots for reserved IUCs, or grants to SIDs designated as meaning 'no CM'. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUcastGrantedMslots, and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.4,DOCS-IF-MIB::docsIfCmtsUpChnlCtrTotalCntnMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention mini-slots defined for this upstream logical channel. This count includes all mini-slots assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnMslots, and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.5,DOCS-IF-MIB::docsIfCmtsUpChnlCtrUsedCntnMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention mini-slots utilized on the upstream logical channel. For contention regions, utilized mini-slots are those in which the CMTS correctly received an upstream burst from any CM on the upstream logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnMslots and is included for back compatibility with SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.6,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtTotalMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of all mini-slots defined for this upstream logical channel. This count includes all IUCs and SIDs, even those allocated to the NULL SID for a 2.0 logical channel that is inactive. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.7,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtUcastGrantedMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of unicast granted mini-slots on the upstream logical channel, regardless of burst type. Unicast granted mini-slots are those in which the CMTS assigned bandwidth to any unicast SID on the logical channel. However, this object does not include mini-slots for reserved IUCs, or grants to SIDs designated as meaning 'no CM'. This is the 64-bit version of docsIfCmtsUpChnlCtrUcastGrantedMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.8,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtTotalCntnMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention mini-slots defined for this upstream logical channel. This count includes all mini-slots assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.9,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtUsedCntnMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention mini-slots utilized on the upstream logical channel. For contention regions, utilized mini-slots are those in which the CMTS correctly received an upstream burst from any CM on the upstream logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnMslots and will not be accessible to SNMPv1 managers. Support for this object is mandatory. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.10,DOCS-IF-MIB::docsIfCmtsUpChnlCtrCollCntnMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention mini-slots subjected to collisions on the upstream logical channel. For contention regions, these are the mini-slots applicable to bursts that the CMTS detected but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.11,DOCS-IF-MIB::docsIfCmtsUpChnlCtrTotalCntnReqMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention request mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC1 assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnReqMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.12,DOCS-IF-MIB::docsIfCmtsUpChnlCtrUsedCntnReqMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention request mini-slots utilized on this upstream logical channel. This count includes all contention mini-slots for IUC1 applicable to bursts that the CMTS correctly received. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnReqMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.13,DOCS-IF-MIB::docsIfCmtsUpChnlCtrCollCntnReqMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention request mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC1 applicable to bursts that the CMTS detected but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnReqMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.14,DOCS-IF-MIB::docsIfCmtsUpChnlCtrTotalCntnReqDataMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention request data mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC2 assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnReqDataMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.15,DOCS-IF-MIB::docsIfCmtsUpChnlCtrUsedCntnReqDataMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention request data mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS correctly received. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnReqDataMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.16,DOCS-IF-MIB::docsIfCmtsUpChnlCtrCollCntnReqDataMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention request data mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnReqDataMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.17,DOCS-IF-MIB::docsIfCmtsUpChnlCtrTotalCntnInitMaintMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention initial maintenance mini-slots defined for this upstream logical channel. This includes all mini-slots for IUC3 assigned to a broadcast or multicast SID on the logical channel. This is the 32-bit version of docsIfCmtsUpChnlCtrExtTotalCntnInitMaintMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.18,DOCS-IF-MIB::docsIfCmtsUpChnlCtrUsedCntnInitMaintMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention initial maintenance mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS correctly received. This is the 32-bit version of docsIfCmtsUpChnlCtrExtUsedCntnInitMaintMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.19,DOCS-IF-MIB::docsIfCmtsUpChnlCtrCollCntnInitMaintMslots,Counter32,read-only,,current,,Current count, from CMTS initialization, of contention initial maintenance mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 32-bit version of docsIfCmtsUpChnlCtrExtCollCntnInitMaintMslots and is included for back compatibility with SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.20,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtCollCntnMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of collision contention mini-slots on the upstream logical channel. For contention regions, these are the mini-slots applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.21,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtTotalCntnReqMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention request mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC1 assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnReqMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.22,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtUsedCntnReqMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention request mini-slots utilized on this upstream logical channel. This count includes all contention mini-slots for IUC1 applicable to bursts that the CMTS correctly received. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnReqMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.23,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtCollCntnReqMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention request mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC1 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnReqMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.24,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtTotalCntnReqDataMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention request data mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC2 assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnReqDataMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.25,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtUsedCntnReqDataMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention request data mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS correctly received. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnReqDataMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.26,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtCollCntnReqDataMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention request data mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC2 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnReqDataMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.27,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtTotalCntnInitMaintMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of initial maintenance mini-slots defined for this upstream logical channel. This count includes all mini-slots for IUC3 assigned to a broadcast or multicast SID on the logical channel. This is the 64-bit version of docsIfCmtsUpChnlCtrTotalCntnInitMaintMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.28,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtUsedCntnInitMaintMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of initial maintenance mini-slots utilized on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS correctly received. This is the 64-bit version of docsIfCmtsUpChnlCtrUsedCntnInitMaintMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.1.3.11.1.29,DOCS-IF-MIB::docsIfCmtsUpChnlCtrExtCollCntnInitMaintMslots,Counter64,read-only,,current,,Current count, from CMTS initialization, of contention initial maintenance mini-slots subjected to collisions on this upstream logical channel. This includes all contention mini-slots for IUC3 applicable to bursts that the CMTS detected, but could not correctly receive. This is the 64-bit version of docsIfCmtsUpChnlCtrCollCntnInitMaintMslots and will not be accessible to SNMPv1 managers. Discontinuities in the value of this counter can occur at reinitialization of the managed system, and at other times as indicated by the value of ifCounterDiscontinuityTime for the associated ifIndex.
.1.3.6.1.2.1.10.127.2,DOCS-IF-MIB::docsIfNotification,,,,,,
.1.3.6.1.2.1.10.127.3,DOCS-IF-MIB::docsIfConformance,,,,,,
.1.3.6.1.2.1.10.127.3.1,DOCS-IF-MIB::docsIfCompliances,,,,,,
.1.3.6.1.2.1.10.127.3.1.1,DOCS-IF-MIB::docsIfBasicCompliance,,,,,,The compliance statement for devices that implement DOCSIS 1.x compliant Radio Frequency Interfaces.
.1.3.6.1.2.1.10.127.3.1.2,DOCS-IF-MIB::docsIfBasicComplianceV2,,,,,,The compliance statement for devices that implement DOCSIS 2.0 Radio Frequency Interfaces.
.1.3.6.1.2.1.10.127.3.2,DOCS-IF-MIB::docsIfGroups,,,,,,
.1.3.6.1.2.1.10.127.3.2.1,DOCS-IF-MIB::docsIfBasicGroup,,,,,,Group of objects implemented in both cable modems and cable modem termination systems.
.1.3.6.1.2.1.10.127.3.2.2,DOCS-IF-MIB::docsIfCmGroup,,,,,,Group of objects implemented in cable modems.
.1.3.6.1.2.1.10.127.3.2.3,DOCS-IF-MIB::docsIfCmtsGroup,,,,,,Group of objects implemented in Cable Modem Termination Systems.
.1.3.6.1.2.1.10.127.3.2.4,DOCS-IF-MIB::docsIfObsoleteGroup,,,,,,Group of objects obsoleted.
.1.3.6.1.2.1.10.127.3.2.5,DOCS-IF-MIB::docsIfBasicGroupV2,,,,,,Group of objects implemented in both cable modems and cable modem termination systems.
.1.3.6.1.2.1.10.127.3.2.6,DOCS-IF-MIB::docsIfCmGroupV2,,,,,,Group of objects implemented in cable modems.
.1.3.6.1.2.1.10.127.3.2.7,DOCS-IF-MIB::docsIfCmtsGroupV2,,,,,,Group of objects implemented in Cable Modem Termination Systems.
.1.3.6.1.2.1.10.127.5,DOCS-BPI-MIB::Interface,,,,,,,This is the MIB Module for the DOCSIS Baseline Privacy Interface
.1.3.6.1.2.1.10.127.5.1,DOCS-BPI-MIB::docsBpiMIBObjects,,,,,,
.1.3.6.1.2.1.10.127.5.1.1,DOCS-BPI-MIB::docsBpiCmObjects,,,,,,
.1.3.6.1.2.1.10.127.5.1.1.1,DOCS-BPI-MIB::Privacy,,not-accessible,,current,,This table describes the basic and authorization-related Baseline
.1.3.6.1.2.1.10.127.5.1.1.1.1,DOCS-BPI-MIB::ifType,,not-accessible,ifIndex,current,,Each entry contains objects describing attributes of one CM MAC
.1.3.6.1.2.1.10.127.5.1.1.1.1.1,DOCS-BPI-MIB::captured,INTEGER,read-only,,current,true(1):false(2),This object identifies whether this CM is provisioned to run
.1.3.6.1.2.1.10.127.5.1.1.1.1.2,DOCS-BPI-MIB::bit,,OCTET,read-only,,current,,The value of this object is a DER-encoded RSAPublicKey ASN.1 type
.1.3.6.1.2.1.10.127.5.1.1.1.1.3,DOCS-BPI-MIB::FSM.,INTEGER,read-only,,current,authWait(2):authorized(3):reauthWait(4):authRejectWait(5),The value of this object is the state of the CM authorization
.1.3.6.1.2.1.10.127.5.1.1.1.1.4,DOCS-BPI-MIB::for,Integer32,read-only,,current,,The value of this object is the authorization key sequence number
.1.3.6.1.2.1.10.127.5.1.1.1.1.5,DOCS-BPI-MIB::the,OCTET,read-only,,current,,The value of this object is the actual clock time when the current
.1.3.6.1.2.1.10.127.5.1.1.1.1.6,DOCS-BPI-MIB::authorization,INTEGER,read-write,,current,true(1):false(2),Setting this object to TRUE generates a Reauthorize event in the
.1.3.6.1.2.1.10.127.5.1.1.1.1.7,DOCS-BPI-MIB::beginning,Integer32,read-only,,current,,The value of this object is the grace time for an authorization key.
.1.3.6.1.2.1.10.127.5.1.1.1.1.8,DOCS-BPI-MIB::seconds,Integer32,read-only,,current,,The value of this object is the grace time for a TEK. A CM is
.1.3.6.1.2.1.10.127.5.1.1.1.1.9,DOCS-BPI-MIB::docsBpiCmAuthWaitTimeout,Integer32,read-only,,current,,The value of this object is the Authorize Wait Timeout.
.1.3.6.1.2.1.10.127.5.1.1.1.1.10,DOCS-BPI-MIB::docsBpiCmReauthWaitTimeout,Integer32,read-only,,current,,The value of this object is the Reauthorize Wait Timeout in seconds.
.1.3.6.1.2.1.10.127.5.1.1.1.1.11,DOCS-BPI-MIB::docsBpiCmOpWaitTimeout,Integer32,read-only,,current,,The value of this object is the Operational Wait Timeout in seconds.
.1.3.6.1.2.1.10.127.5.1.1.1.1.12,DOCS-BPI-MIB::docsBpiCmRekeyWaitTimeout,Integer32,read-only,,current,,The value of this object is the Rekey Wait Timeout in seconds.
.1.3.6.1.2.1.10.127.5.1.1.1.1.13,DOCS-BPI-MIB::docsBpiCmAuthRejectWaitTimeout,Integer32,read-only,,current,,The value of this object is the Authorization Reject Wait Timeout in
.1.3.6.1.2.1.10.127.5.1.1.1.1.14,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CM has
.1.3.6.1.2.1.10.127.5.1.1.1.1.15,DOCS-BPI-MIB::received,Counter32,read-only,,current,,The value of this object is the count of times the CM has
.1.3.6.1.2.1.10.127.5.1.1.1.1.16,DOCS-BPI-MIB::received,Counter32,read-only,,current,,The value of this object is the count of times the CM has
.1.3.6.1.2.1.10.127.5.1.1.1.1.17,DOCS-BPI-MIB::received,Counter32,read-only,,current,,The value of this object is the count of times the CM has
.1.3.6.1.2.1.10.127.5.1.1.1.1.18,DOCS-BPI-MIB::since,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unauthorizedSid(4),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.1.1.1.19,DOCS-BPI-MIB::since,OCTET,read-only,,current,,The value of this object is the Display-String in most recent
.1.3.6.1.2.1.10.127.5.1.1.1.1.20,DOCS-BPI-MIB::since,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unsolicited(5):invalidKeySequence(6):keyRequestAuthenticationFailure(7),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.1.1.1.21,DOCS-BPI-MIB::since,OCTET,read-only,,current,,The value of this object is the Display-String in most recent
.1.3.6.1.2.1.10.127.5.1.1.2,DOCS-BPI-MIB::per,,not-accessible,,current,,This table describes the attributes of each CM Traffic Encryption Key
.1.3.6.1.2.1.10.127.5.1.1.2.1,DOCS-BPI-MIB::or,,not-accessible,ifIndex:docsIfCmServiceId,current,,Each entry contains objects describing the TEK association attributes
.1.3.6.1.2.1.10.127.5.1.1.2.1.1,DOCS-BPI-MIB::docsBpiCmPrivacyEnable,INTEGER,read-only,,current,true(1):false(2),This object identifies whether this SID is provisioned to run
.1.3.6.1.2.1.10.127.5.1.1.2.1.2,DOCS-BPI-MIB::The,INTEGER,read-only,,current,start(1):opWait(2):opReauthWait(3):operational(4):rekeyWait(5):rekeyReauthWait(6),The value of this object is the state of the indicated TEK FSM.
.1.3.6.1.2.1.10.127.5.1.1.2.1.3,DOCS-BPI-MIB::of,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration
.1.3.6.1.2.1.10.127.5.1.1.2.1.4,DOCS-BPI-MIB::of,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration
.1.3.6.1.2.1.10.127.5.1.1.2.1.5,DOCS-BPI-MIB::a,Counter32,read-only,,current,,The value of this object is the count of times the CM has transmitted
.1.3.6.1.2.1.10.127.5.1.1.2.1.6,DOCS-BPI-MIB::a,Counter32,read-only,,current,,The value of this object is the count of times the CM has received
.1.3.6.1.2.1.10.127.5.1.1.2.1.7,DOCS-BPI-MIB::a,Counter32,read-only,,current,,The value of this object is the count of times the CM has received
.1.3.6.1.2.1.10.127.5.1.1.2.1.8,DOCS-BPI-MIB::a,Counter32,read-only,,current,,The value of this object is the count of times the CM has received
.1.3.6.1.2.1.10.127.5.1.1.2.1.9,DOCS-BPI-MIB::Pending,Counter32,read-only,,current,,The value of this object is the count of times an Authorization
.1.3.6.1.2.1.10.127.5.1.1.2.1.10,DOCS-BPI-MIB::if,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedSid(4),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.1.2.1.11,DOCS-BPI-MIB::Key,OCTET,read-only,,current,,The value of this object is the Display-String in most recent Key
.1.3.6.1.2.1.10.127.5.1.1.2.1.12,DOCS-BPI-MIB::none(1),INTEGER,read-only,,current,none(1):unknown(2):invalidKeySequence(6),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.1.2.1.13,DOCS-BPI-MIB::no,OCTET,read-only,,current,,The value of this object is the Display-String in most recent TEK
.1.3.6.1.2.1.10.127.5.1.2,DOCS-BPI-MIB::docsBpiCmtsObjects,,,,,,
.1.3.6.1.2.1.10.127.5.1.2.1,DOCS-BPI-MIB::CMTS,,not-accessible,,current,,This table describes the basic Baseline Privacy attributes of each
.1.3.6.1.2.1.10.127.5.1.2.1.1,DOCS-BPI-MIB::ifType,,not-accessible,ifIndex,current,,Each entry contains objects describing attributes of one CMTS MAC
.1.3.6.1.2.1.10.127.5.1.2.1.1.1,DOCS-BPI-MIB::CMTS,Integer32,read-write,,current,,The value of this object is the default lifetime, in seconds, the
.1.3.6.1.2.1.10.127.5.1.2.1.1.2,DOCS-BPI-MIB::CMTS,Integer32,read-write,,current,,The value of this object is the default lifetime, in seconds, the
.1.3.6.1.2.1.10.127.5.1.2.1.1.3,DOCS-BPI-MIB::manages,Integer32,read-write,,obsolete,,This object was obsoleted because the provisioning system, not the CMTS,
.1.3.6.1.2.1.10.127.5.1.2.1.1.4,DOCS-BPI-MIB::manages,Integer32,read-write,,obsolete,,This object was obsoleted because the provisioning system, not the CMTS,
.1.3.6.1.2.1.10.127.5.1.2.1.1.5,DOCS-BPI-MIB::received,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.1.1.6,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.1.1.7,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.1.1.8,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.2,DOCS-BPI-MIB::each,,not-accessible,,current,,This table describes the attributes of each CM authorization
.1.3.6.1.2.1.10.127.5.1.2.2.1,DOCS-BPI-MIB::permanently,,not-accessible,ifIndex:docsBpiCmtsAuthCmMacAddress,current,,Each entry contains objects describing attributes of one
.1.3.6.1.2.1.10.127.5.1.2.2.1.1,DOCS-BPI-MIB::which,OCTET,not-accessible,,current,,The value of this object is the physical address of the CM to
.1.3.6.1.2.1.10.127.5.1.2.2.1.2,DOCS-BPI-MIB::string,OCTET,read-only,,current,,The value of this object is a DER-encoded RSAPublicKey ASN.1 type
.1.3.6.1.2.1.10.127.5.1.2.2.1.3,DOCS-BPI-MIB::for,Integer32,read-only,,current,,The value of this object is the authorization key sequence number
.1.3.6.1.2.1.10.127.5.1.2.2.1.4,DOCS-BPI-MIB::time,OCTET,read-only,,current,,The value of this object is the actual clock time when the current
.1.3.6.1.2.1.10.127.5.1.2.2.1.5,DOCS-BPI-MIB::assigns,Integer32,read-write,,current,,The value of this object is the lifetime, in seconds, the CMTS
.1.3.6.1.2.1.10.127.5.1.2.2.1.6,DOCS-BPI-MIB::authorization,Integer32,read-only,,current,,The value of this object is the grace time for the authorization key
.1.3.6.1.2.1.10.127.5.1.2.2.1.7,DOCS-BPI-MIB::been,INTEGER,read-write,,current,noResetRequested(1):invalidateAuth(2):sendAuthInvalid(3):invalidateTeks(4),Setting this object to invalidateAuth(2) causes the CMTS to
.1.3.6.1.2.1.10.127.5.1.2.2.1.8,DOCS-BPI-MIB::received,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.2.1.9,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.2.1.10,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.2.1.11,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.2.1.12,DOCS-BPI-MIB::to,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unauthorizedSid(4),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.2.2.1.13,DOCS-BPI-MIB::transmitted,OCTET,read-only,,current,,The value of this object is the Display-String in most recent
.1.3.6.1.2.1.10.127.5.1.2.2.1.14,DOCS-BPI-MIB::transmitted,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unsolicited(5):invalidKeySequence(6):keyRequestAuthenticationFailure(7),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.2.2.1.15,DOCS-BPI-MIB::transmitted,OCTET,read-only,,current,,The value of this object is the Display-String in most recent
.1.3.6.1.2.1.10.127.5.1.2.3,DOCS-BPI-MIB::SID,,not-accessible,,current,,This table describes the attributes of each CM Traffic Encryption
.1.3.6.1.2.1.10.127.5.1.2.3.1,DOCS-BPI-MIB::authorization,,not-accessible,ifIndex:docsIfCmtsServiceId,current,,Each entry contains objects describing attributes of one TEK
.1.3.6.1.2.1.10.127.5.1.2.3.1.1,DOCS-BPI-MIB::to,Integer32,read-write,,current,,The value of this object is the lifetime, in seconds, the CMTS assigns
.1.3.6.1.2.1.10.127.5.1.2.3.1.2,DOCS-BPI-MIB::TEKGraceTime,Integer32,read-only,,current,,The value of this object is the grace time for the TEK in seconds.
.1.3.6.1.2.1.10.127.5.1.2.3.1.3,DOCS-BPI-MIB::of,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration
.1.3.6.1.2.1.10.127.5.1.2.3.1.4,DOCS-BPI-MIB::of,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration
.1.3.6.1.2.1.10.127.5.1.2.3.1.5,DOCS-BPI-MIB::between,INTEGER,read-write,,current,true(1):false(2),Setting this object to TRUE causes the CMTS to invalidate the current
.1.3.6.1.2.1.10.127.5.1.2.3.1.6,DOCS-BPI-MIB::received,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.3.1.7,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.3.1.8,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.3.1.9,DOCS-BPI-MIB::transmitted,Counter32,read-only,,current,,The value of this object is the count of times the CMTS has
.1.3.6.1.2.1.10.127.5.1.2.3.1.10,DOCS-BPI-MIB::received,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedSid(4),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.2.3.1.11,DOCS-BPI-MIB::received,OCTET,read-only,,current,,The value of this object is the Display-String in the most recent
.1.3.6.1.2.1.10.127.5.1.2.3.1.12,DOCS-BPI-MIB::since,INTEGER,read-only,,current,none(1):unknown(2):invalidKeySequence(6),The value of this object is the enumerated description of the
.1.3.6.1.2.1.10.127.5.1.2.3.1.13,DOCS-BPI-MIB::length,OCTET,read-only,,current,,The value of this object is the Display-String in the most recent TEK
.1.3.6.1.2.1.10.127.5.1.2.4,DOCS-BPI-MIB::docsBpiMulticastControl,,,,,,
.1.3.6.1.2.1.10.127.5.1.2.4.1,DOCS-BPI-MIB::multicast,,not-accessible,,current,,This table describes the mapping of IP multicast address prefixes to
.1.3.6.1.2.1.10.127.5.1.2.4.1.1,DOCS-BPI-MIB::multicast,,not-accessible,ifIndex:docsBpiIpMulticastAddress:docsBpiIpMulticastPrefixLength,current,,Each entry contains objects describing the mapping of one IP
.1.3.6.1.2.1.10.127.5.1.2.4.1.1.1,DOCS-BPI-MIB::mapped,IpAddress,not-accessible,,current,,This object represents the IP multicast address (prefix) to be
.1.3.6.1.2.1.10.127.5.1.2.4.1.1.2,DOCS-BPI-MIB::address,Integer32,not-accessible,,current,,This object represents the IP multicast address prefix length
.1.3.6.1.2.1.10.127.5.1.2.4.1.1.3,DOCS-BPI-MIB::IP,Integer32,read-create,,current,,This object represents the multicast SID to be used in this
.1.3.6.1.2.1.10.127.5.1.2.4.1.1.4,DOCS-BPI-MIB::in,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls and reflects the IP multicast address prefix
.1.3.6.1.2.1.10.127.5.1.2.4.2,DOCS-BPI-MIB::CM,,not-accessible,,current,,This table describes the multicast SID authorization for each
.1.3.6.1.2.1.10.127.5.1.2.4.2.1,DOCS-BPI-MIB::cable,,not-accessible,ifIndex:docsBpiMulticastServiceId:docsBpiMulticastCmMacAddress,current,,Each entry contains objects describing the key authorization of one
.1.3.6.1.2.1.10.127.5.1.2.4.2.1.1,DOCS-BPI-MIB::docsBpiMulticastServiceId,Integer32,not-accessible,,current,,This object represents the multicast SID for authorization.
.1.3.6.1.2.1.10.127.5.1.2.4.2.1.2,DOCS-BPI-MIB::multicast,OCTET,not-accessible,,current,,This object represents the MAC address of the CM to which the
.1.3.6.1.2.1.10.127.5.1.2.4.2.1.3,DOCS-BPI-MIB::values,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls and reflects the CM authorization for each
.1.3.6.1.2.1.10.127.5.2,DOCS-BPI-MIB::docsBpiNotification,,,,,,
.1.3.6.1.2.1.10.127.5.3,DOCS-BPI-MIB::docsBpiConformance,,,,,,
.1.3.6.1.2.1.10.127.5.3.1,DOCS-BPI-MIB::docsBpiCompliances,,,,,,
.1.3.6.1.2.1.10.127.5.3.1.1,DOCS-BPI-MIB::DOCSIS,,,,,,This is the compliance statement for devices which implement the
.1.3.6.1.2.1.10.127.5.3.2,DOCS-BPI-MIB::docsBpiGroups,,,,,,
.1.3.6.1.2.1.10.127.5.3.2.1,DOCS-BPI-MIB::docsBpiCmGroup,,,,,,This collection of objects provides CM BPI status and control.
.1.3.6.1.2.1.10.127.5.3.2.2,DOCS-BPI-MIB::docsBpiCmtsGroup,,,,,,This collection of objects provides CMTS BPI status and control.
.1.3.6.1.2.1.10.127.5.3.2.3,DOCS-BPI-MIB::docsBpiObsoleteObjectsGroup,,,,,,This is a collection of obsolete BPI objects.
.1.3.6.1.2.1.10.131,TUNNEL-MIB::tunnelMIB,,,,,,The MIB module for management of IP Tunnels, independent of the specific encapsulation scheme in use. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4087; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.131.1,TUNNEL-MIB::tunnelMIBObjects,,,,,,
.1.3.6.1.2.1.10.131.1.1,TUNNEL-MIB::tunnel,,,,,,
.1.3.6.1.2.1.10.131.1.1.1,TUNNEL-MIB::tunnelIfTable,,not-accessible,,current,,The (conceptual) table containing information on configured tunnels.
.1.3.6.1.2.1.10.131.1.1.1.1,TUNNEL-MIB::tunnelIfEntry,,not-accessible,ifIndex,current,,An entry (conceptual row) containing the information on a particular configured tunnel.
.1.3.6.1.2.1.10.131.1.1.1.1.1,TUNNEL-MIB::tunnelIfLocalAddress,IpAddress,read-only,,deprecated,,The address of the local endpoint of the tunnel (i.e., the source address used in the outer IP header), or 0.0.0.0 if unknown or if the tunnel is over IPv6. Since this object does not support IPv6, it is deprecated in favor of tunnelIfLocalInetAddress.
.1.3.6.1.2.1.10.131.1.1.1.1.2,TUNNEL-MIB::tunnelIfRemoteAddress,IpAddress,read-only,,deprecated,,The address of the remote endpoint of the tunnel (i.e., the destination address used in the outer IP header), or 0.0.0.0 if unknown, or an IPv6 address, or the tunnel is not a point-to-point link (e.g., if it is a 6to4 tunnel). Since this object does not support IPv6, it is deprecated in favor of tunnelIfRemoteInetAddress.
.1.3.6.1.2.1.10.131.1.1.1.1.3,TUNNEL-MIB::tunnelIfEncapsMethod,INTEGER,read-only,,current,other(1):direct(2):gre(3):minimal(4):l2tp(5):pptp(6):l2f(7):udp(8):atmp(9):msdp(10):sixToFour(11):sixOverFour(12):isatap(13):teredo(14):ipHttps(15):softwireMesh(16):dsLite(17):aplusp(18),The encapsulation method used by the tunnel.
.1.3.6.1.2.1.10.131.1.1.1.1.4,TUNNEL-MIB::tunnelIfHopLimit,Integer32,read-write,,current,,The IPv4 TTL or IPv6 Hop Limit to use in the outer IP header. A value of 0 indicates that the value is copied from the payload's header.
.1.3.6.1.2.1.10.131.1.1.1.1.5,TUNNEL-MIB::tunnelIfSecurity,INTEGER,read-only,,current,none(1):ipsec(2):other(3),The method used by the tunnel to secure the outer IP header. The value ipsec indicates that IPsec is used between the tunnel endpoints for authentication or encryption or both. More specific security-related information may be available in a MIB module for the security protocol in use.
.1.3.6.1.2.1.10.131.1.1.1.1.6,TUNNEL-MIB::tunnelIfTOS,Integer32,read-write,,current,,The method used to set the high 6 bits (the differentiated services codepoint) of the IPv4 TOS or IPv6 Traffic Class in the outer IP header. A value of -1 indicates that the bits are copied from the payload's header. A value of -2 indicates that a traffic conditioner is invoked and more information may be available in a traffic conditioner MIB module. A value between 0 and 63 inclusive indicates that the bit field is set to the indicated value. Note: instead of the name tunnelIfTOS, a better name would have been tunnelIfDSCPMethod, but the existing name appeared in RFC 2667 and existing objects cannot be renamed.
.1.3.6.1.2.1.10.131.1.1.1.1.7,TUNNEL-MIB::tunnelIfFlowLabel,Integer32,read-write,,current,,The method used to set the IPv6 Flow Label value. This object need not be present in rows where tunnelIfAddressType indicates the tunnel is not over IPv6. A value of -1 indicates that a traffic conditioner is invoked and more information may be available in a traffic conditioner MIB. Any other value indicates that the Flow Label field is set to the indicated value.
.1.3.6.1.2.1.10.131.1.1.1.1.8,TUNNEL-MIB::tunnelIfAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address in the corresponding tunnelIfLocalInetAddress and tunnelIfRemoteInetAddress objects.
.1.3.6.1.2.1.10.131.1.1.1.1.9,TUNNEL-MIB::tunnelIfLocalInetAddress,OCTET,read-write,,current,,The address of the local endpoint of the tunnel (i.e., the source address used in the outer IP header). If the address is unknown, the value is 0.0.0.0 for IPv4 or :: for IPv6. The type of this object is given by tunnelIfAddressType.
.1.3.6.1.2.1.10.131.1.1.1.1.10,TUNNEL-MIB::tunnelIfRemoteInetAddress,OCTET,read-write,,current,,The address of the remote endpoint of the tunnel (i.e., the destination address used in the outer IP header). If the address is unknown or the tunnel is not a point-to-point link (e.g., if it is a 6to4 tunnel), the value is 0.0.0.0 for tunnels over IPv4 or :: for tunnels over IPv6. The type of this object is given by tunnelIfAddressType.
.1.3.6.1.2.1.10.131.1.1.1.1.11,TUNNEL-MIB::tunnelIfEncapsLimit,Integer32,read-write,,current,,The maximum number of additional encapsulations permitted for packets undergoing encapsulation at this node. A value of -1 indicates that no limit is present (except as a result of the packet size).
.1.3.6.1.2.1.10.131.1.1.2,TUNNEL-MIB::tunnelConfigTable,,not-accessible,,deprecated,,The (conceptual) table containing information on configured tunnels. This table can be used to map a set of tunnel endpoints to the associated ifIndex value. It can also be used for row creation. Note that every row in the tunnelIfTable with a fixed IPv4 destination address should have a corresponding row in the tunnelConfigTable, regardless of whether it was created via SNMP. Since this table does not support IPv6, it is deprecated in favor of tunnelInetConfigTable.
.1.3.6.1.2.1.10.131.1.1.2.1,TUNNEL-MIB::tunnelConfigEntry,,not-accessible,tunnelConfigLocalAddress:tunnelConfigRemoteAddress:tunnelConfigEncapsMethod:tunnelConfigID,deprecated,,An entry (conceptual row) containing the information on a particular configured tunnel. Since this entry does not support IPv6, it is deprecated in favor of tunnelInetConfigEntry.
.1.3.6.1.2.1.10.131.1.1.2.1.1,TUNNEL-MIB::tunnelConfigLocalAddress,IpAddress,not-accessible,,deprecated,,The address of the local endpoint of the tunnel, or 0.0.0.0 if the device is free to choose any of its addresses at tunnel establishment time. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigLocalAddress.
.1.3.6.1.2.1.10.131.1.1.2.1.2,TUNNEL-MIB::tunnelConfigRemoteAddress,IpAddress,not-accessible,,deprecated,,The address of the remote endpoint of the tunnel. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigRemoteAddress.
.1.3.6.1.2.1.10.131.1.1.2.1.3,TUNNEL-MIB::tunnelConfigEncapsMethod,INTEGER,not-accessible,,deprecated,other(1):direct(2):gre(3):minimal(4):l2tp(5):pptp(6):l2f(7):udp(8):atmp(9):msdp(10):sixToFour(11):sixOverFour(12):isatap(13):teredo(14):ipHttps(15):softwireMesh(16):dsLite(17):aplusp(18),The encapsulation method used by the tunnel. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigEncapsMethod.
.1.3.6.1.2.1.10.131.1.1.2.1.4,TUNNEL-MIB::tunnelConfigID,Integer32,not-accessible,,deprecated,,An identifier used to distinguish between multiple tunnels of the same encapsulation method, with the same endpoints. If the encapsulation protocol only allows one tunnel per set of endpoint addresses (such as for GRE or IP-in-IP), the value of this object is 1. For encapsulation methods (such as L2F) which allow multiple parallel tunnels, the manager is responsible for choosing any ID which does not conflict with an existing row, such as choosing a random number. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigID.
.1.3.6.1.2.1.10.131.1.1.2.1.5,TUNNEL-MIB::tunnelConfigIfIndex,Integer32,read-only,,deprecated,,If the value of tunnelConfigStatus for this row is active, then this object contains the value of ifIndex corresponding to the tunnel interface. A value of 0 is not legal in the active state, and means that the interface index has not yet been assigned. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigIfIndex.
.1.3.6.1.2.1.10.131.1.1.2.1.6,TUNNEL-MIB::tunnelConfigStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table. The agent need not support setting this object to createAndWait or notInService since there are no other writable objects in this table, and writable objects in rows of corresponding tables such as the tunnelIfTable may be modified while this row is active. To create a row in this table for an encapsulation method which does not support multiple parallel tunnels with the same endpoints, the management station should simply use a tunnelConfigID of 1, and set tunnelConfigStatus to createAndGo. For encapsulation methods such as L2F which allow multiple parallel tunnels, the management station may select a pseudo-random number to use as the tunnelConfigID and set tunnelConfigStatus to createAndGo. In the event that this ID is already in use and an inconsistentValue is returned in response to the set operation, the management station should simply select a new pseudo-random number and retry the operation. Creating a row in this table will cause an interface index to be assigned by the agent in an implementation-dependent manner, and corresponding rows will be instantiated in the ifTable and the tunnelIfTable. The status of this row will become active as soon as the agent assigns the interface index, regardless of whether the interface is operationally up. Deleting a row in this table will likewise delete the corresponding row in the ifTable and in the tunnelIfTable. Since this object does not support IPv6, it is deprecated in favor of tunnelInetConfigStatus.
.1.3.6.1.2.1.10.131.1.1.3,TUNNEL-MIB::tunnelInetConfigTable,,not-accessible,,current,,The (conceptual) table containing information on configured tunnels. This table can be used to map a set of tunnel endpoints to the associated ifIndex value. It can also be used for row creation. Note that every row in the tunnelIfTable with a fixed destination address should have a corresponding row in the tunnelInetConfigTable, regardless of whether it was created via SNMP.
.1.3.6.1.2.1.10.131.1.1.3.1,TUNNEL-MIB::tunnelInetConfigEntry,,not-accessible,tunnelInetConfigAddressType:tunnelInetConfigLocalAddress:tunnelInetConfigRemoteAddress:tunnelInetConfigEncapsMethod:tunnelInetConfigID,current,,An entry (conceptual row) containing the information on a particular configured tunnel. Note that there is a 128 subid maximum for object OIDs. Implementers need to be aware that if the total number of octets in tunnelInetConfigLocalAddress and tunnelInetConfigRemoteAddress exceeds 110 then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. In practice this is not expected to be a problem since IPv4 and IPv6 addresses will not cause the limit to be reached, but if other types are supported by an agent, care must be taken to ensure that the sum of the lengths do not cause the limit to be exceeded.
.1.3.6.1.2.1.10.131.1.1.3.1.1,TUNNEL-MIB::tunnelInetConfigAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type over which the tunnel encapsulates packets.
.1.3.6.1.2.1.10.131.1.1.3.1.2,TUNNEL-MIB::tunnelInetConfigLocalAddress,OCTET,not-accessible,,current,,The address of the local endpoint of the tunnel, or 0.0.0.0 (for IPv4) or :: (for IPv6) if the device is free to choose any of its addresses at tunnel establishment time.
.1.3.6.1.2.1.10.131.1.1.3.1.3,TUNNEL-MIB::tunnelInetConfigRemoteAddress,OCTET,not-accessible,,current,,The address of the remote endpoint of the tunnel.
.1.3.6.1.2.1.10.131.1.1.3.1.4,TUNNEL-MIB::tunnelInetConfigEncapsMethod,INTEGER,not-accessible,,current,other(1):direct(2):gre(3):minimal(4):l2tp(5):pptp(6):l2f(7):udp(8):atmp(9):msdp(10):sixToFour(11):sixOverFour(12):isatap(13):teredo(14):ipHttps(15):softwireMesh(16):dsLite(17):aplusp(18),The encapsulation method used by the tunnel.
.1.3.6.1.2.1.10.131.1.1.3.1.5,TUNNEL-MIB::tunnelInetConfigID,Integer32,not-accessible,,current,,An identifier used to distinguish between multiple tunnels of the same encapsulation method, with the same endpoints. If the encapsulation protocol only allows one tunnel per set of endpoint addresses (such as for GRE or IP-in-IP), the value of this object is 1. For encapsulation methods (such as L2F) which allow multiple parallel tunnels, the manager is responsible for choosing any ID which does not conflict with an existing row, such as choosing a random number.
.1.3.6.1.2.1.10.131.1.1.3.1.6,TUNNEL-MIB::tunnelInetConfigIfIndex,Integer32,read-only,,current,,If the value of tunnelInetConfigStatus for this row is active, then this object contains the value of ifIndex corresponding to the tunnel interface. A value of 0 is not legal in the active state, and means that the interface index has not yet been assigned.
.1.3.6.1.2.1.10.131.1.1.3.1.7,TUNNEL-MIB::tunnelInetConfigStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table. The agent need not support setting this object to createAndWait or notInService since there are no other writable objects in this table, and writable objects in rows of corresponding tables such as the tunnelIfTable may be modified while this row is active. To create a row in this table for an encapsulation method which does not support multiple parallel tunnels with the same endpoints, the management station should simply use a tunnelInetConfigID of 1, and set tunnelInetConfigStatus to createAndGo. For encapsulation methods such as L2F which allow multiple parallel tunnels, the management station may select a pseudo-random number to use as the tunnelInetConfigID and set tunnelInetConfigStatus to createAndGo. In the event that this ID is already in use and an inconsistentValue is returned in response to the set operation, the management station should simply select a new pseudo-random number and retry the operation. Creating a row in this table will cause an interface index to be assigned by the agent in an implementation-dependent manner, and corresponding rows will be instantiated in the ifTable and the tunnelIfTable. The status of this row will become active as soon as the agent assigns the interface index, regardless of whether the interface is operationally up. Deleting a row in this table will likewise delete the corresponding row in the ifTable and in the tunnelIfTable.
.1.3.6.1.2.1.10.131.1.1.3.1.8,TUNNEL-MIB::tunnelInetConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this row. If the row is permanent(4), no objects in the row need be writable.
.1.3.6.1.2.1.10.131.2,TUNNEL-MIB::tunnelMIBConformance,,,,,,
.1.3.6.1.2.1.10.131.2.1,TUNNEL-MIB::tunnelMIBCompliances,,,,,,
.1.3.6.1.2.1.10.131.2.1.1,TUNNEL-MIB::tunnelMIBCompliance,,,,,,The (deprecated) IPv4-only compliance statement for the IP Tunnel MIB. This is deprecated in favor of tunnelMIBInetFullCompliance and tunnelMIBInetReadOnlyCompliance.
.1.3.6.1.2.1.10.131.2.1.2,TUNNEL-MIB::tunnelMIBInetFullCompliance,,,,,,The full compliance statement for the IP Tunnel MIB.
.1.3.6.1.2.1.10.131.2.1.3,TUNNEL-MIB::tunnelMIBInetReadOnlyCompliance,,,,,,The read-only compliance statement for the IP Tunnel MIB.
.1.3.6.1.2.1.10.131.2.2,TUNNEL-MIB::tunnelMIBGroups,,,,,,
.1.3.6.1.2.1.10.131.2.2.1,TUNNEL-MIB::tunnelMIBBasicGroup,,,,,,A collection of objects to support basic management of IPv4 Tunnels. Since this group cannot support IPv6, it is deprecated in favor of tunnelMIBInetGroup.
.1.3.6.1.2.1.10.131.2.2.2,TUNNEL-MIB::tunnelMIBInetGroup,,,,,,A collection of objects to support basic management of IPv4 and IPv6 Tunnels.
.1.3.6.1.2.1.10.133,OPT-IF-MIB::optIfMibModule,,,,,,The MIB module to describe pre-OTN and OTN interfaces. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3591; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.133.1,OPT-IF-MIB::optIfObjects,,,,,,
.1.3.6.1.2.1.10.133.1.1,OPT-IF-MIB::optIfOTMn,,,,,,
.1.3.6.1.2.1.10.133.1.1.1,OPT-IF-MIB::optIfOTMnTable,,not-accessible,,current,,A table of OTMn structure information.
.1.3.6.1.2.1.10.133.1.1.1.1,OPT-IF-MIB::optIfOTMnEntry,,not-accessible,ifIndex,current,,A conceptual row that contains the OTMn structure information of an optical interface.
.1.3.6.1.2.1.10.133.1.1.1.1.1,OPT-IF-MIB::optIfOTMnOrder,Unsigned32,read-only,,current,,This object indicates the order of the OTM, which represents the maximum number of wavelengths that can be supported at the bit rate(s) supported on the interface.
.1.3.6.1.2.1.10.133.1.1.1.1.2,OPT-IF-MIB::optIfOTMnReduced,INTEGER,read-only,,current,true(1):false(2),This object indicates whether a reduced or full functionality is supported at the interface. A value of true means reduced. A value of false means full.
.1.3.6.1.2.1.10.133.1.1.1.1.3,OPT-IF-MIB::optIfOTMnBitRates,BITS,read-only,,current,bitRateK1(0):bitRateK2(1):bitRateK3(2),This attribute is a bit map representing the bit rate or set of bit rates supported on the interface. The meaning of each bit position is as follows: bitRateK1(0) is set if the 2.5 Gbit/s rate is supported bitRateK2(1) is set if the 10 Gbit/s rate is supported bitRateK3(2) is set if the 40 Gbit/s rate is supported Note that each bit position corresponds to one possible value of the type OptIfBitRateK. The default value of this attribute is system specific.
.1.3.6.1.2.1.10.133.1.1.1.1.4,OPT-IF-MIB::optIfOTMnInterfaceType,OCTET,read-only,,current,,This object identifies the type of interface. The value of this attribute will affect the behavior of the OTM with respect to presence/absence of OTM Overhead Signal (OOS) processing and TCM activation. For an IrDI interface, there is no OOS processing and TCM activation is limited to n levels as specified by a TCM level threshold. This object contains two fields that are separated by whitespace. The possible values are: field 1: one of the 4-character ASCII strings 'IrDI' or 'IaDI' field 2: free-form text consisting of printable UTF-8 encoded characters Note that field 2 is optional. If it is not present then there is no requirement for trailing whitespace after field 1. The default values are as follows: field 1: 'IaDI' field 2: an empty string.
.1.3.6.1.2.1.10.133.1.1.1.1.5,OPT-IF-MIB::optIfOTMnTcmMax,Unsigned32,read-write,,current,,This object identifies the maximum number of TCM levels allowed for any Optical Channel contained in this OTM. A new TCM activation will be rejected if the requested level is greater than the threshold. If InterfaceType object specifies a type of 'IaDI' for this OTM, then this attribute is irrelevant. Possible values: unsigned integers in the range from 0 to 6 inclusive. Default value: 3.
.1.3.6.1.2.1.10.133.1.1.1.1.6,OPT-IF-MIB::optIfOTMnOpticalReach,INTEGER,read-only,,current,intraOffice(1):shortHaul(2):longHaul(3):veryLongHaul(4):ultraLongHaul(5),This object indicates the length the optical signal may travel before requiring termination or regeneration. The meaning of the enumeration are: intraOffice(1) - intra-office (as defined in ITU-T G.957) shortHaul(2) - short haul (as defined in ITU-T G.957) longHaul(3) - long haul (as defined in ITU-T G.957) veryLongHaul(4) - very long haul (as defined in ITU-T G.691) ultraLongHaul(5)- ultra long haul (as defined in ITU-T G.691)
.1.3.6.1.2.1.10.133.1.2,OPT-IF-MIB::optIfPerfMon,,,,,,
.1.3.6.1.2.1.10.133.1.2.1,OPT-IF-MIB::optIfPerfMonIntervalTable,,not-accessible,,current,,A table of 15-minute performance monitoring interval information.
.1.3.6.1.2.1.10.133.1.2.1.1,OPT-IF-MIB::optIfPerfMonIntervalEntry,,not-accessible,ifIndex,current,,A conceptual row that contains 15-minute performance monitoring interval information of an interface.
.1.3.6.1.2.1.10.133.1.2.1.1.1,OPT-IF-MIB::optIfPerfMonCurrentTimeElapsed,Gauge32,read-only,,current,,Number of seconds elapsed in the current 15-minute performance monitoring interval. If, for some reason, such as an adjustment in the NE's time-of-day clock, the number of seconds elapsed exceeds the maximum value, then the maximum value will be returned.
.1.3.6.1.2.1.10.133.1.2.1.1.2,OPT-IF-MIB::optIfPerfMonCurDayTimeElapsed,Gauge32,read-only,,current,,Number of seconds elapsed in the current 24-hour interval performance monitoring period. If, for some reason, such as an adjustment in the NE's time-of-day clock, the number of seconds elapsed exceeds the maximum value, then the maximum value will be returned.
.1.3.6.1.2.1.10.133.1.2.1.1.3,OPT-IF-MIB::optIfPerfMonIntervalNumIntervals,Unsigned32,read-only,,current,,The number of 15-minute intervals for which performance monitoring data is available. The number is the same for all the associated sub layers of the interface. An optical interface must be capable of supporting at least n intervals, where n is defined as follows: The minimum value of n is 4. The default of n is 32. The maximum value of n is 96. The value of this object will be n unless performance monitoring was (re-)started for the interface within the last (n*15) minutes, in which case the value will be the number of complete 15-minute intervals since measurement was (re-)started.
.1.3.6.1.2.1.10.133.1.2.1.1.4,OPT-IF-MIB::optIfPerfMonIntervalNumInvalidIntervals,Unsigned32,read-only,,current,,The number of intervals in the range from 0 to optIfPerfMonIntervalNumIntervals for which no performance monitoring data is available and/or the data is invalid.
.1.3.6.1.2.1.10.133.1.3,OPT-IF-MIB::optIfOTSn,,,,,,
.1.3.6.1.2.1.10.133.1.3.1,OPT-IF-MIB::optIfOTSnConfigTable,,not-accessible,,current,,A table of OTSn configuration information.
.1.3.6.1.2.1.10.133.1.3.1.1,OPT-IF-MIB::optIfOTSnConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn configuration information of an interface.
.1.3.6.1.2.1.10.133.1.3.1.1.1,OPT-IF-MIB::optIfOTSnDirectionality,INTEGER,read-only,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity.
.1.3.6.1.2.1.10.133.1.3.1.1.2,OPT-IF-MIB::optIfOTSnAprStatus,OCTET,read-only,,current,,This attribute indicates the status of the Automatic Power Reduction (APR) function of the entity. Valid values are 'on' and 'off'.
.1.3.6.1.2.1.10.133.1.3.1.1.3,OPT-IF-MIB::optIfOTSnAprControl,OCTET,read-write,,current,,This object is a UTF-8 encoded string that specifies Automatic Power Reduction (APR) control actions requested of this entity (when written) and that returns the current APR control state of this entity (when read). The values are implementation-defined. Any implementation that instantiates this object must document the set of values that it allows to be written, the set of values that it will return, and what each of those values means.
.1.3.6.1.2.1.10.133.1.3.1.1.4,OPT-IF-MIB::optIfOTSnTraceIdentifierTransmitted,OCTET,read-write,,current,,The trace identifier transmitted. This object is applicable when optIfOTSnDirectionality has the value source(2) or bidirectional(3). This object does not apply to reduced-capability systems (i.e., those for which optIfOTMnReduced has the value true(1)) or at IrDI interfaces (i.e., when optIfOTMnInterfaceType field 1 has the value 'IrDI'). If no value is ever set by a management entity for the object optIfOTSnTraceIdentifierTransmitted, system-specific default value will be used. Any implementation that instantiates this object must document the system-specific default value or how it is derived.
.1.3.6.1.2.1.10.133.1.3.1.1.5,OPT-IF-MIB::optIfOTSnDAPIExpected,OCTET,read-write,,current,,The DAPI expected by the receiver. This object is applicable when optIfOTSnDirectionality has the value sink(1) or bidirectional(3). It has no effect if optIfOTSnTIMDetMode has the value off(1) or sapi(3). This object does not apply to reduced-capability systems (i.e., those for which optIfOTMnReduced has the value true(1)) or at IrDI interfaces (i.e., when optIfOTMnInterfaceType field 1 has the value 'IrDI').
.1.3.6.1.2.1.10.133.1.3.1.1.6,OPT-IF-MIB::optIfOTSnSAPIExpected,OCTET,read-write,,current,,The SAPI expected by the receiver. This object is applicable when optIfOTSnDirectionality has the value sink(1) or bidirectional(3). It has no effect if optIfOTSnTIMDetMode has the value off(1) or dapi(2). This object does not apply to reduced-capability systems (i.e., those for which optIfOTMnReduced has the value true(1)) or at IrDI interfaces (i.e., when optIfOTMnInterfaceType field 1 has the value 'IrDI').
.1.3.6.1.2.1.10.133.1.3.1.1.7,OPT-IF-MIB::optIfOTSnTraceIdentifierAccepted,OCTET,read-only,,current,,The actual trace identifier received. This object is applicable when optIfOTSnDirectionality has the value sink(1) or bidirectional(3). Its value is unspecified if optIfOTSnCurrentStatus has either or both of the losO(5) and los(6) bits set. This object does not apply to reduced-capability systems (i.e., those for which optIfOTMnReduced has the value true(1)) or at IrDI interfaces (i.e., when optIfOTMnInterfaceType field 1 has the value 'IrDI').
.1.3.6.1.2.1.10.133.1.3.1.1.8,OPT-IF-MIB::optIfOTSnTIMDetMode,INTEGER,read-write,,current,off(1):dapi(2):sapi(3):both(4),Indicates the mode of the Trace Identifier Mismatch (TIM) Detection function. This object is applicable when optIfOTSnDirectionality has the value sink(1) or bidirectional(3). The default value is off(1). This object does not apply to reduced-capability systems (i.e., those for which optIfOTMnReduced has the value true(1)) or at IrDI interfaces (i.e., when optIfOTMnInterfaceType field 1 has the value 'IrDI'). The default value of this object is off(1).
.1.3.6.1.2.1.10.133.1.3.1.1.9,OPT-IF-MIB::optIfOTSnTIMActEnabled,INTEGER,read-write,,current,true(1):false(2),Indicates whether the Trace Identifier Mismatch (TIM) Consequent Action function is enabled. This object is applicable when optIfOTSnDirectionality has the value sink(1) or bidirectional(3). It has no effect when the value of optIfOTSnTIMDetMode is off(1). This object does not apply to reduced-capability systems (i.e., those for which optIfOTMnReduced has the value true(1)) or at IrDI interfaces (i.e., when optIfOTMnInterfaceType field 1 has the value 'IrDI'). The default value of this object is false(2).
.1.3.6.1.2.1.10.133.1.3.1.1.10,OPT-IF-MIB::optIfOTSnCurrentStatus,BITS,read-only,,current,bdiP(0):bdiO(1):bdi(2):tim(3):losP(4):losO(5):los(6),Indicates the defect condition of the entity, if any. This object is applicable when optIfOTSnDirectionality has the value sink(1) or bidirectional(3). In reduced-capability systems or at IrDI interfaces the only bit position that may be set is los(6).
.1.3.6.1.2.1.10.133.1.3.2,OPT-IF-MIB::optIfOTSnSinkCurrentTable,,not-accessible,,current,,A table of OTSn sink performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.2.1,OPT-IF-MIB::optIfOTSnSinkCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn sink performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.2.1.1,OPT-IF-MIB::optIfOTSnSinkCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.2.1.2,OPT-IF-MIB::optIfOTSnSinkCurrentInputPower,Integer32,read-only,,current,,The optical power monitored at the input.
.1.3.6.1.2.1.10.133.1.3.2.1.3,OPT-IF-MIB::optIfOTSnSinkCurrentLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.2.1.4,OPT-IF-MIB::optIfOTSnSinkCurrentHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.2.1.5,OPT-IF-MIB::optIfOTSnSinkCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on input power. If optIfOTSnSinkCurrentInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.2.1.6,OPT-IF-MIB::optIfOTSnSinkCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on input power. If optIfOTSnSinkCurrentInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.2.1.7,OPT-IF-MIB::optIfOTSnSinkCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output.
.1.3.6.1.2.1.10.133.1.3.2.1.8,OPT-IF-MIB::optIfOTSnSinkCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.2.1.9,OPT-IF-MIB::optIfOTSnSinkCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.2.1.10,OPT-IF-MIB::optIfOTSnSinkCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If optIfOTSnSinkCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.2.1.11,OPT-IF-MIB::optIfOTSnSinkCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If optIfOTSnSinkCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.3,OPT-IF-MIB::optIfOTSnSinkIntervalTable,,not-accessible,,current,,A table of historical OTSn sink performance monitoring information.
.1.3.6.1.2.1.10.133.1.3.3.1,OPT-IF-MIB::optIfOTSnSinkIntervalEntry,,not-accessible,ifIndex:optIfOTSnSinkIntervalNumber,current,,A conceptual row that contains OTSn sink performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.3.3.1.1,OPT-IF-MIB::optIfOTSnSinkIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.3.3.1.2,OPT-IF-MIB::optIfOTSnSinkIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.3.1.3,OPT-IF-MIB::optIfOTSnSinkIntervalLastInputPower,Integer32,read-only,,current,,The last optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.3.3.1.4,OPT-IF-MIB::optIfOTSnSinkIntervalLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.3.3.1.5,OPT-IF-MIB::optIfOTSnSinkIntervalHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.3.3.1.6,OPT-IF-MIB::optIfOTSnSinkIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.3.3.1.7,OPT-IF-MIB::optIfOTSnSinkIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.3.3.1.8,OPT-IF-MIB::optIfOTSnSinkIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.3.4,OPT-IF-MIB::optIfOTSnSinkCurDayTable,,not-accessible,,current,,A table of OTSn sink performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.4.1,OPT-IF-MIB::optIfOTSnSinkCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn sink performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.4.1.1,OPT-IF-MIB::optIfOTSnSinkCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.4.1.2,OPT-IF-MIB::optIfOTSnSinkCurDayLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.4.1.3,OPT-IF-MIB::optIfOTSnSinkCurDayHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.4.1.4,OPT-IF-MIB::optIfOTSnSinkCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.4.1.5,OPT-IF-MIB::optIfOTSnSinkCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5,OPT-IF-MIB::optIfOTSnSinkPrevDayTable,,not-accessible,,current,,A table of OTSn sink performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1,OPT-IF-MIB::optIfOTSnSinkPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn sink performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1.1,OPT-IF-MIB::optIfOTSnSinkPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.5.1.2,OPT-IF-MIB::optIfOTSnSinkPrevDayLastInputPower,Integer32,read-only,,current,,The last optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1.3,OPT-IF-MIB::optIfOTSnSinkPrevDayLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1.4,OPT-IF-MIB::optIfOTSnSinkPrevDayHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1.5,OPT-IF-MIB::optIfOTSnSinkPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1.6,OPT-IF-MIB::optIfOTSnSinkPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.5.1.7,OPT-IF-MIB::optIfOTSnSinkPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.6,OPT-IF-MIB::optIfOTSnSrcCurrentTable,,not-accessible,,current,,A table of OTSn source performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.6.1,OPT-IF-MIB::optIfOTSnSrcCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn source performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.6.1.1,OPT-IF-MIB::optIfOTSnSrcCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.6.1.2,OPT-IF-MIB::optIfOTSnSrcCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output.
.1.3.6.1.2.1.10.133.1.3.6.1.3,OPT-IF-MIB::optIfOTSnSrcCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.6.1.4,OPT-IF-MIB::optIfOTSnSrcCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.6.1.5,OPT-IF-MIB::optIfOTSnSrcCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If optIfOTSnSrcCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.6.1.6,OPT-IF-MIB::optIfOTSnSrcCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If optIfOTSnSrcCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.6.1.7,OPT-IF-MIB::optIfOTSnSrcCurrentInputPower,Integer32,read-only,,current,,The optical power monitored at the input.
.1.3.6.1.2.1.10.133.1.3.6.1.8,OPT-IF-MIB::optIfOTSnSrcCurrentLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.6.1.9,OPT-IF-MIB::optIfOTSnSrcCurrentHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.3.6.1.10,OPT-IF-MIB::optIfOTSnSrcCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on input power. If optIfOTSnSrcCurrentInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.6.1.11,OPT-IF-MIB::optIfOTSnSrcCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on input power. If optIfOTSnSrcCurrentInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.3.7,OPT-IF-MIB::optIfOTSnSrcIntervalTable,,not-accessible,,current,,A table of historical OTSn source performance monitoring information.
.1.3.6.1.2.1.10.133.1.3.7.1,OPT-IF-MIB::optIfOTSnSrcIntervalEntry,,not-accessible,ifIndex:optIfOTSnSrcIntervalNumber,current,,A conceptual row that contains OTSn source performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.3.7.1.1,OPT-IF-MIB::optIfOTSnSrcIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.3.7.1.2,OPT-IF-MIB::optIfOTSnSrcIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.7.1.3,OPT-IF-MIB::optIfOTSnSrcIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.3.7.1.4,OPT-IF-MIB::optIfOTSnSrcIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.3.7.1.5,OPT-IF-MIB::optIfOTSnSrcIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.3.7.1.6,OPT-IF-MIB::optIfOTSnSrcIntervalLastInputPower,Integer32,read-only,,current,,The last optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.3.7.1.7,OPT-IF-MIB::optIfOTSnSrcIntervalLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.3.7.1.8,OPT-IF-MIB::optIfOTSnSrcIntervalHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.3.8,OPT-IF-MIB::optIfOTSnSrcCurDayTable,,not-accessible,,current,,A table of OTSn source performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.8.1,OPT-IF-MIB::optIfOTSnSrcCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn source performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.8.1.1,OPT-IF-MIB::optIfOTSnSrcCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.8.1.2,OPT-IF-MIB::optIfOTSnSrcCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.8.1.3,OPT-IF-MIB::optIfOTSnSrcCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.8.1.4,OPT-IF-MIB::optIfOTSnSrcCurDayLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.8.1.5,OPT-IF-MIB::optIfOTSnSrcCurDayHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9,OPT-IF-MIB::optIfOTSnSrcPrevDayTable,,not-accessible,,current,,A table of OTSn source performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1,OPT-IF-MIB::optIfOTSnSrcPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTSn source performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1.1,OPT-IF-MIB::optIfOTSnSrcPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.3.9.1.2,OPT-IF-MIB::optIfOTSnSrcPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1.3,OPT-IF-MIB::optIfOTSnSrcPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1.4,OPT-IF-MIB::optIfOTSnSrcPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1.5,OPT-IF-MIB::optIfOTSnSrcPrevDayLastInputPower,Integer32,read-only,,current,,The last optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1.6,OPT-IF-MIB::optIfOTSnSrcPrevDayLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.3.9.1.7,OPT-IF-MIB::optIfOTSnSrcPrevDayHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4,OPT-IF-MIB::optIfOMSn,,,,,,
.1.3.6.1.2.1.10.133.1.4.1,OPT-IF-MIB::optIfOMSnConfigTable,,not-accessible,,current,,A table of OMSn configuration information.
.1.3.6.1.2.1.10.133.1.4.1.1,OPT-IF-MIB::optIfOMSnConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn configuration information of an interface.
.1.3.6.1.2.1.10.133.1.4.1.1.1,OPT-IF-MIB::optIfOMSnDirectionality,INTEGER,read-only,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity.
.1.3.6.1.2.1.10.133.1.4.1.1.2,OPT-IF-MIB::optIfOMSnCurrentStatus,BITS,read-only,,current,ssfP(0):ssfO(1):ssf(2):bdiP(3):bdiO(4):bdi(5):losP(6),Indicates the defect condition of the entity, if any. This object is applicable only to full capability systems whose interface type is IaDI and for which optIfOMSnDirectionality has the value sink(1) or bidirectional(3).
.1.3.6.1.2.1.10.133.1.4.2,OPT-IF-MIB::optIfOMSnSinkCurrentTable,,not-accessible,,current,,A table of OMSn sink performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.2.1,OPT-IF-MIB::optIfOMSnSinkCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn sink performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.2.1.1,OPT-IF-MIB::optIfOMSnSinkCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.2.1.2,OPT-IF-MIB::optIfOMSnSinkCurrentAggregatedInputPower,Integer32,read-only,,current,,The aggregated optical power of all the DWDM input channels.
.1.3.6.1.2.1.10.133.1.4.2.1.3,OPT-IF-MIB::optIfOMSnSinkCurrentLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.2.1.4,OPT-IF-MIB::optIfOMSnSinkCurrentHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.2.1.5,OPT-IF-MIB::optIfOMSnSinkCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on aggregated input power. If optIfOMSnSinkCurrentAggregatedInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.2.1.6,OPT-IF-MIB::optIfOMSnSinkCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on aggregated input power. If optIfOMSnSinkCurrentAggregatedInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.2.1.7,OPT-IF-MIB::optIfOMSnSinkCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output.
.1.3.6.1.2.1.10.133.1.4.2.1.8,OPT-IF-MIB::optIfOMSnSinkCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.2.1.9,OPT-IF-MIB::optIfOMSnSinkCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.2.1.10,OPT-IF-MIB::optIfOMSnSinkCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If optIfOMSnSinkCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.2.1.11,OPT-IF-MIB::optIfOMSnSinkCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If optIfOMSnSinkCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.3,OPT-IF-MIB::optIfOMSnSinkIntervalTable,,not-accessible,,current,,A table of historical OMSn sink performance monitoring information.
.1.3.6.1.2.1.10.133.1.4.3.1,OPT-IF-MIB::optIfOMSnSinkIntervalEntry,,not-accessible,ifIndex:optIfOMSnSinkIntervalNumber,current,,A conceptual row that contains OMSn sink performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.4.3.1.1,OPT-IF-MIB::optIfOMSnSinkIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.4.3.1.2,OPT-IF-MIB::optIfOMSnSinkIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.3.1.3,OPT-IF-MIB::optIfOMSnSinkIntervalLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power of all the DWDM input channels during the interval.
.1.3.6.1.2.1.10.133.1.4.3.1.4,OPT-IF-MIB::optIfOMSnSinkIntervalLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels during the interval.
.1.3.6.1.2.1.10.133.1.4.3.1.5,OPT-IF-MIB::optIfOMSnSinkIntervalHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels during the interval.
.1.3.6.1.2.1.10.133.1.4.3.1.6,OPT-IF-MIB::optIfOMSnSinkIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power at the output during the interval.
.1.3.6.1.2.1.10.133.1.4.3.1.7,OPT-IF-MIB::optIfOMSnSinkIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power at the output during the interval.
.1.3.6.1.2.1.10.133.1.4.3.1.8,OPT-IF-MIB::optIfOMSnSinkIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power at the output during the interval.
.1.3.6.1.2.1.10.133.1.4.4,OPT-IF-MIB::optIfOMSnSinkCurDayTable,,not-accessible,,current,,A table of OMSn sink performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.4.1,OPT-IF-MIB::optIfOMSnSinkCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn sink performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.4.1.1,OPT-IF-MIB::optIfOMSnSinkCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.4.1.2,OPT-IF-MIB::optIfOMSnSinkCurDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.4.1.3,OPT-IF-MIB::optIfOMSnSinkCurDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.4.1.4,OPT-IF-MIB::optIfOMSnSinkCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.4.1.5,OPT-IF-MIB::optIfOMSnSinkCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5,OPT-IF-MIB::optIfOMSnSinkPrevDayTable,,not-accessible,,current,,A table of OMSn sink performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1,OPT-IF-MIB::optIfOMSnSinkPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn sink performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1.1,OPT-IF-MIB::optIfOMSnSinkPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.5.1.2,OPT-IF-MIB::optIfOMSnSinkPrevDayLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power of all the DWDM input channels during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1.3,OPT-IF-MIB::optIfOMSnSinkPrevDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1.4,OPT-IF-MIB::optIfOMSnSinkPrevDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1.5,OPT-IF-MIB::optIfOMSnSinkPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1.6,OPT-IF-MIB::optIfOMSnSinkPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.5.1.7,OPT-IF-MIB::optIfOMSnSinkPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.6,OPT-IF-MIB::optIfOMSnSrcCurrentTable,,not-accessible,,current,,A table of OMSn source performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.6.1,OPT-IF-MIB::optIfOMSnSrcCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn source performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.6.1.1,OPT-IF-MIB::optIfOMSnSrcCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.6.1.2,OPT-IF-MIB::optIfOMSnSrcCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output.
.1.3.6.1.2.1.10.133.1.4.6.1.3,OPT-IF-MIB::optIfOMSnSrcCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.6.1.4,OPT-IF-MIB::optIfOMSnSrcCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.6.1.5,OPT-IF-MIB::optIfOMSnSrcCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If optIfOMSnSrcCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.6.1.6,OPT-IF-MIB::optIfOMSnSrcCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If optIfOMSnSrcCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.6.1.7,OPT-IF-MIB::optIfOMSnSrcCurrentAggregatedInputPower,Integer32,read-only,,current,,The aggregated optical power at the input.
.1.3.6.1.2.1.10.133.1.4.6.1.8,OPT-IF-MIB::optIfOMSnSrcCurrentLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.6.1.9,OPT-IF-MIB::optIfOMSnSrcCurrentHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.4.6.1.10,OPT-IF-MIB::optIfOMSnSrcCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on aggregated input power. If optIfOMSnSrcCurrentAggregatedInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.6.1.11,OPT-IF-MIB::optIfOMSnSrcCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on aggregated input power. If optIfOMSnSrcCurrentAggregatedInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.4.7,OPT-IF-MIB::optIfOMSnSrcIntervalTable,,not-accessible,,current,,A table of historical OMSn source performance monitoring information.
.1.3.6.1.2.1.10.133.1.4.7.1,OPT-IF-MIB::optIfOMSnSrcIntervalEntry,,not-accessible,ifIndex:optIfOMSnSrcIntervalNumber,current,,A conceptual row that contains OMSn source performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.4.7.1.1,OPT-IF-MIB::optIfOMSnSrcIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.4.7.1.2,OPT-IF-MIB::optIfOMSnSrcIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.7.1.3,OPT-IF-MIB::optIfOMSnSrcIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.4.7.1.4,OPT-IF-MIB::optIfOMSnSrcIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.4.7.1.5,OPT-IF-MIB::optIfOMSnSrcIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.4.7.1.6,OPT-IF-MIB::optIfOMSnSrcIntervalLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power at the input during the interval.
.1.3.6.1.2.1.10.133.1.4.7.1.7,OPT-IF-MIB::optIfOMSnSrcIntervalLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power at the input during the interval.
.1.3.6.1.2.1.10.133.1.4.7.1.8,OPT-IF-MIB::optIfOMSnSrcIntervalHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power at the input during the interval.
.1.3.6.1.2.1.10.133.1.4.8,OPT-IF-MIB::optIfOMSnSrcCurDayTable,,not-accessible,,current,,A table of OMSn source performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.8.1,OPT-IF-MIB::optIfOMSnSrcCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn source performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.8.1.1,OPT-IF-MIB::optIfOMSnSrcCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.8.1.2,OPT-IF-MIB::optIfOMSnSrcCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.8.1.3,OPT-IF-MIB::optIfOMSnSrcCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.8.1.4,OPT-IF-MIB::optIfOMSnSrcCurDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.8.1.5,OPT-IF-MIB::optIfOMSnSrcCurDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9,OPT-IF-MIB::optIfOMSnSrcPrevDayTable,,not-accessible,,current,,A table of OMSn source performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1,OPT-IF-MIB::optIfOMSnSrcPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OMSn source performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1.1,OPT-IF-MIB::optIfOMSnSrcPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.4.9.1.2,OPT-IF-MIB::optIfOMSnSrcPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1.3,OPT-IF-MIB::optIfOMSnSrcPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1.4,OPT-IF-MIB::optIfOMSnSrcPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1.5,OPT-IF-MIB::optIfOMSnSrcPrevDayLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1.6,OPT-IF-MIB::optIfOMSnSrcPrevDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.4.9.1.7,OPT-IF-MIB::optIfOMSnSrcPrevDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5,OPT-IF-MIB::optIfOChGroup,,,,,,
.1.3.6.1.2.1.10.133.1.5.1,OPT-IF-MIB::optIfOChGroupConfigTable,,not-accessible,,current,,A table of OChGroup configuration information.
.1.3.6.1.2.1.10.133.1.5.1.1,OPT-IF-MIB::optIfOChGroupConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup configuration information of an interface.
.1.3.6.1.2.1.10.133.1.5.1.1.1,OPT-IF-MIB::optIfOChGroupDirectionality,INTEGER,read-only,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity.
.1.3.6.1.2.1.10.133.1.5.2,OPT-IF-MIB::optIfOChGroupSinkCurrentTable,,not-accessible,,current,,A table of OChGroup sink performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.2.1,OPT-IF-MIB::optIfOChGroupSinkCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup sink performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.2.1.1,OPT-IF-MIB::optIfOChGroupSinkCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.2.1.2,OPT-IF-MIB::optIfOChGroupSinkCurrentAggregatedInputPower,Integer32,read-only,,current,,The aggregated optical power of all the DWDM input channels in the OChGroup.
.1.3.6.1.2.1.10.133.1.5.2.1.3,OPT-IF-MIB::optIfOChGroupSinkCurrentLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels in the OChGroup during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.2.1.4,OPT-IF-MIB::optIfOChGroupSinkCurrentHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels in the OChGroup during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.2.1.5,OPT-IF-MIB::optIfOChGroupSinkCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on aggregated input power. If optIfOChGroupSinkCurrentAggregatedInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.2.1.6,OPT-IF-MIB::optIfOChGroupSinkCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on aggregated input power. If optIfOChGroupSinkCurrentAggregatedInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.2.1.7,OPT-IF-MIB::optIfOChGroupSinkCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output in the OChGroup.
.1.3.6.1.2.1.10.133.1.5.2.1.8,OPT-IF-MIB::optIfOChGroupSinkCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output in the OChGroup during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.2.1.9,OPT-IF-MIB::optIfOChGroupSinkCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output in the OChGroup during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.2.1.10,OPT-IF-MIB::optIfOChGroupSinkCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on the output power. If optIfOChGroupSinkCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.2.1.11,OPT-IF-MIB::optIfOChGroupSinkCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on the output power. If optIfOChGroupSinkCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.3,OPT-IF-MIB::optIfOChGroupSinkIntervalTable,,not-accessible,,current,,A table of historical OChGroup sink performance monitoring information.
.1.3.6.1.2.1.10.133.1.5.3.1,OPT-IF-MIB::optIfOChGroupSinkIntervalEntry,,not-accessible,ifIndex:optIfOChGroupSinkIntervalNumber,current,,A conceptual row that contains OChGroup sink performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.5.3.1.1,OPT-IF-MIB::optIfOChGroupSinkIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.5.3.1.2,OPT-IF-MIB::optIfOChGroupSinkIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.3.1.3,OPT-IF-MIB::optIfOChGroupSinkIntervalLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power of all the DWDM input channels in the OChGroup during the interval.
.1.3.6.1.2.1.10.133.1.5.3.1.4,OPT-IF-MIB::optIfOChGroupSinkIntervalLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels in the OChGroup during the interval.
.1.3.6.1.2.1.10.133.1.5.3.1.5,OPT-IF-MIB::optIfOChGroupSinkIntervalHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels in the OChGroup during the interval.
.1.3.6.1.2.1.10.133.1.5.3.1.6,OPT-IF-MIB::optIfOChGroupSinkIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output in the OChGroup during the interval.
.1.3.6.1.2.1.10.133.1.5.3.1.7,OPT-IF-MIB::optIfOChGroupSinkIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output in the OChGroup during the interval.
.1.3.6.1.2.1.10.133.1.5.3.1.8,OPT-IF-MIB::optIfOChGroupSinkIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output in the OChGroup during the interval.
.1.3.6.1.2.1.10.133.1.5.4,OPT-IF-MIB::optIfOChGroupSinkCurDayTable,,not-accessible,,current,,A table of OChGroup sink performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.4.1,OPT-IF-MIB::optIfOChGroupSinkCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup sink performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.4.1.1,OPT-IF-MIB::optIfOChGroupSinkCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.4.1.2,OPT-IF-MIB::optIfOChGroupSinkCurDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels in the OChGroup during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.4.1.3,OPT-IF-MIB::optIfOChGroupSinkCurDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels in the OChGroup during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.4.1.4,OPT-IF-MIB::optIfOChGroupSinkCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output in the OChGroup during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.4.1.5,OPT-IF-MIB::optIfOChGroupSinkCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output in the OChGroup during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5,OPT-IF-MIB::optIfOChGroupSinkPrevDayTable,,not-accessible,,current,,A table of OChGroup sink performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1,OPT-IF-MIB::optIfOChGroupSinkPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup sink performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1.1,OPT-IF-MIB::optIfOChGroupSinkPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.5.1.2,OPT-IF-MIB::optIfOChGroupSinkPrevDayLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power of all the DWDM input channels in the OChGroup during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1.3,OPT-IF-MIB::optIfOChGroupSinkPrevDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power of all the DWDM input channels in the OChGroup during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1.4,OPT-IF-MIB::optIfOChGroupSinkPrevDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power of all the DWDM input channels in the OChGroup during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1.5,OPT-IF-MIB::optIfOChGroupSinkPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output in the OChGroup during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1.6,OPT-IF-MIB::optIfOChGroupSinkPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output in the OChGroup during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.5.1.7,OPT-IF-MIB::optIfOChGroupSinkPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output in the OChGroup during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.6,OPT-IF-MIB::optIfOChGroupSrcCurrentTable,,not-accessible,,current,,A table of OChGroup source performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.6.1,OPT-IF-MIB::optIfOChGroupSrcCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup source performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.6.1.1,OPT-IF-MIB::optIfOChGroupSrcCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.6.1.2,OPT-IF-MIB::optIfOChGroupSrcCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output.
.1.3.6.1.2.1.10.133.1.5.6.1.3,OPT-IF-MIB::optIfOChGroupSrcCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.6.1.4,OPT-IF-MIB::optIfOChGroupSrcCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.6.1.5,OPT-IF-MIB::optIfOChGroupSrcCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If optIfOChGroupSrcCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.6.1.6,OPT-IF-MIB::optIfOChGroupSrcCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If optIfOChGroupSrcCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.6.1.7,OPT-IF-MIB::optIfOChGroupSrcCurrentAggregatedInputPower,Integer32,read-only,,current,,The aggregated optical power monitored at the input.
.1.3.6.1.2.1.10.133.1.5.6.1.8,OPT-IF-MIB::optIfOChGroupSrcCurrentLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.6.1.9,OPT-IF-MIB::optIfOChGroupSrcCurrentHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.5.6.1.10,OPT-IF-MIB::optIfOChGroupSrcCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on input power. If optIfOChGroupSrcCurrentAggregatedInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.6.1.11,OPT-IF-MIB::optIfOChGroupSrcCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on input power. If optIfOChGroupSrcCurrentAggregatedInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.5.7,OPT-IF-MIB::optIfOChGroupSrcIntervalTable,,not-accessible,,current,,A table of historical OChGroup source performance monitoring information.
.1.3.6.1.2.1.10.133.1.5.7.1,OPT-IF-MIB::optIfOChGroupSrcIntervalEntry,,not-accessible,ifIndex:optIfOChGroupSrcIntervalNumber,current,,A conceptual row that contains OChGroup source performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.5.7.1.1,OPT-IF-MIB::optIfOChGroupSrcIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.5.7.1.2,OPT-IF-MIB::optIfOChGroupSrcIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.7.1.3,OPT-IF-MIB::optIfOChGroupSrcIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.5.7.1.4,OPT-IF-MIB::optIfOChGroupSrcIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.5.7.1.5,OPT-IF-MIB::optIfOChGroupSrcIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.5.7.1.6,OPT-IF-MIB::optIfOChGroupSrcIntervalLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.5.7.1.7,OPT-IF-MIB::optIfOChGroupSrcIntervalLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.5.7.1.8,OPT-IF-MIB::optIfOChGroupSrcIntervalHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.5.8,OPT-IF-MIB::optIfOChGroupSrcCurDayTable,,not-accessible,,current,,A table of OChGroup source performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.8.1,OPT-IF-MIB::optIfOChGroupSrcCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup source performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.8.1.1,OPT-IF-MIB::optIfOChGroupSrcCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.8.1.2,OPT-IF-MIB::optIfOChGroupSrcCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.8.1.3,OPT-IF-MIB::optIfOChGroupSrcCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.8.1.4,OPT-IF-MIB::optIfOChGroupSrcCurDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.8.1.5,OPT-IF-MIB::optIfOChGroupSrcCurDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9,OPT-IF-MIB::optIfOChGroupSrcPrevDayTable,,not-accessible,,current,,A table of OChGroup source performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1,OPT-IF-MIB::optIfOChGroupSrcPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OChGroup source performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1.1,OPT-IF-MIB::optIfOChGroupSrcPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.5.9.1.2,OPT-IF-MIB::optIfOChGroupSrcPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1.3,OPT-IF-MIB::optIfOChGroupSrcPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1.4,OPT-IF-MIB::optIfOChGroupSrcPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1.5,OPT-IF-MIB::optIfOChGroupSrcPrevDayLastAggregatedInputPower,Integer32,read-only,,current,,The last aggregated optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1.6,OPT-IF-MIB::optIfOChGroupSrcPrevDayLowAggregatedInputPower,Integer32,read-only,,current,,The lowest aggregated optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.5.9.1.7,OPT-IF-MIB::optIfOChGroupSrcPrevDayHighAggregatedInputPower,Integer32,read-only,,current,,The highest aggregated optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6,OPT-IF-MIB::optIfOCh,,,,,,
.1.3.6.1.2.1.10.133.1.6.1,OPT-IF-MIB::optIfOChConfigTable,,not-accessible,,current,,A table of OCh configuration information.
.1.3.6.1.2.1.10.133.1.6.1.1,OPT-IF-MIB::optIfOChConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh configuration information of an interface.
.1.3.6.1.2.1.10.133.1.6.1.1.1,OPT-IF-MIB::optIfOChDirectionality,INTEGER,read-only,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity.
.1.3.6.1.2.1.10.133.1.6.1.1.2,OPT-IF-MIB::optIfOChCurrentStatus,BITS,read-only,,current,losP(0):los(1):oci(2):ssfP(3):ssfO(4):ssf(5),Indicates the defect condition of the entity, if any. This object is applicable when optIfOChDirectionality has the value sink(1) or bidirectional(3). In full-capability systems the bit position los(1) is not used. In reduced-capability systems or at IrDI interfaces only the bit positions los(1) and ssfP(3) are used.
.1.3.6.1.2.1.10.133.1.6.2,OPT-IF-MIB::optIfOChSinkCurrentTable,,not-accessible,,current,,A table of OCh sink performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.2.1,OPT-IF-MIB::optIfOChSinkCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh sink performance monitoring information for an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.2.1.1,OPT-IF-MIB::optIfOChSinkCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.2.1.2,OPT-IF-MIB::optIfOChSinkCurrentInputPower,Integer32,read-only,,current,,The optical power monitored at the input.
.1.3.6.1.2.1.10.133.1.6.2.1.3,OPT-IF-MIB::optIfOChSinkCurrentLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.2.1.4,OPT-IF-MIB::optIfOChSinkCurrentHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.2.1.5,OPT-IF-MIB::optIfOChSinkCurrentLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on input power. If optIfOChSinkCurrentInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.6.2.1.6,OPT-IF-MIB::optIfOChSinkCurrentUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on input power. If optIfOChSinkCurrentInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.6.3,OPT-IF-MIB::optIfOChSinkIntervalTable,,not-accessible,,current,,A table of historical OCh sink performance monitoring information.
.1.3.6.1.2.1.10.133.1.6.3.1,OPT-IF-MIB::optIfOChSinkIntervalEntry,,not-accessible,ifIndex:optIfOChSinkIntervalNumber,current,,A conceptual row that contains OCh sink performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.6.3.1.1,OPT-IF-MIB::optIfOChSinkIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.6.3.1.2,OPT-IF-MIB::optIfOChSinkIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.3.1.3,OPT-IF-MIB::optIfOChSinkIntervalLastInputPower,Integer32,read-only,,current,,The last optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.6.3.1.4,OPT-IF-MIB::optIfOChSinkIntervalLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.6.3.1.5,OPT-IF-MIB::optIfOChSinkIntervalHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the interval.
.1.3.6.1.2.1.10.133.1.6.4,OPT-IF-MIB::optIfOChSinkCurDayTable,,not-accessible,,current,,A table of OCh sink performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.4.1,OPT-IF-MIB::optIfOChSinkCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh sink performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.4.1.1,OPT-IF-MIB::optIfOChSinkCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.4.1.2,OPT-IF-MIB::optIfOChSinkCurDayLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.4.1.3,OPT-IF-MIB::optIfOChSinkCurDayHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.5,OPT-IF-MIB::optIfOChSinkPrevDayTable,,not-accessible,,current,,A table of OCh sink performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.5.1,OPT-IF-MIB::optIfOChSinkPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh sink performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.5.1.1,OPT-IF-MIB::optIfOChSinkPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.5.1.2,OPT-IF-MIB::optIfOChSinkPrevDayLastInputPower,Integer32,read-only,,current,,The last optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.5.1.3,OPT-IF-MIB::optIfOChSinkPrevDayLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.5.1.4,OPT-IF-MIB::optIfOChSinkPrevDayHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.6,OPT-IF-MIB::optIfOChSrcCurrentTable,,not-accessible,,current,,A table of OCh source performance monitoring information for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.6.1,OPT-IF-MIB::optIfOChSrcCurrentEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh source performance monitoring information of an interface for the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.6.1.1,OPT-IF-MIB::optIfOChSrcCurrentSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.6.1.2,OPT-IF-MIB::optIfOChSrcCurrentOutputPower,Integer32,read-only,,current,,The optical power monitored at the output.
.1.3.6.1.2.1.10.133.1.6.6.1.3,OPT-IF-MIB::optIfOChSrcCurrentLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.6.1.4,OPT-IF-MIB::optIfOChSrcCurrentHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval.
.1.3.6.1.2.1.10.133.1.6.6.1.5,OPT-IF-MIB::optIfOChSrcCurrentLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If optIfOChSrcCurrentOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.6.6.1.6,OPT-IF-MIB::optIfOChSrcCurrentUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If optIfOChSrcCurrentOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent.
.1.3.6.1.2.1.10.133.1.6.7,OPT-IF-MIB::optIfOChSrcIntervalTable,,not-accessible,,current,,A table of historical OCh source performance monitoring information.
.1.3.6.1.2.1.10.133.1.6.7.1,OPT-IF-MIB::optIfOChSrcIntervalEntry,,not-accessible,ifIndex:optIfOChSrcIntervalNumber,current,,A conceptual row that contains OCh source performance monitoring information of an interface during a particular historical interval.
.1.3.6.1.2.1.10.133.1.6.7.1.1,OPT-IF-MIB::optIfOChSrcIntervalNumber,Unsigned32,not-accessible,,current,,Uniquely identifies the interval.
.1.3.6.1.2.1.10.133.1.6.7.1.2,OPT-IF-MIB::optIfOChSrcIntervalSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.7.1.3,OPT-IF-MIB::optIfOChSrcIntervalLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.6.7.1.4,OPT-IF-MIB::optIfOChSrcIntervalLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.6.7.1.5,OPT-IF-MIB::optIfOChSrcIntervalHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the interval.
.1.3.6.1.2.1.10.133.1.6.8,OPT-IF-MIB::optIfOChSrcCurDayTable,,not-accessible,,current,,A table of OCh source performance monitoring information for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.8.1,OPT-IF-MIB::optIfOChSrcCurDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh source performance monitoring information of an interface for the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.8.1.1,OPT-IF-MIB::optIfOChSrcCurDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.8.1.2,OPT-IF-MIB::optIfOChSrcCurDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.8.1.3,OPT-IF-MIB::optIfOChSrcCurDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.9,OPT-IF-MIB::optIfOChSrcPrevDayTable,,not-accessible,,current,,A table of OCh source performance monitoring information for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.9.1,OPT-IF-MIB::optIfOChSrcPrevDayEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OCh source performance monitoring information of an interface for the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.9.1.1,OPT-IF-MIB::optIfOChSrcPrevDaySuspectedFlag,INTEGER,read-only,,current,true(1):false(2),If true, the data in this entry may be unreliable.
.1.3.6.1.2.1.10.133.1.6.9.1.2,OPT-IF-MIB::optIfOChSrcPrevDayLastOutputPower,Integer32,read-only,,current,,The last optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.9.1.3,OPT-IF-MIB::optIfOChSrcPrevDayLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.6.9.1.4,OPT-IF-MIB::optIfOChSrcPrevDayHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the previous 24-hour interval.
.1.3.6.1.2.1.10.133.1.7,OPT-IF-MIB::optIfOTUk,,,,,,
.1.3.6.1.2.1.10.133.1.7.1,OPT-IF-MIB::optIfOTUkConfigTable,,not-accessible,,current,,A table of OTUk configuration information.
.1.3.6.1.2.1.10.133.1.7.1.1,OPT-IF-MIB::optIfOTUkConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains OTUk configuration information of an interface.
.1.3.6.1.2.1.10.133.1.7.1.1.1,OPT-IF-MIB::optIfOTUkDirectionality,INTEGER,read-only,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity.
.1.3.6.1.2.1.10.133.1.7.1.1.2,OPT-IF-MIB::optIfOTUkBitRateK,Integer32,read-only,,current,,Indicates the bit rate of the entity.
.1.3.6.1.2.1.10.133.1.7.1.1.3,OPT-IF-MIB::optIfOTUkTraceIdentifierTransmitted,OCTET,read-write,,current,,The trace identifier transmitted. This object is applicable when optIfOTUkDirectionality has the value source(2) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value sink(1). If no value is ever set by a management entity for this object, system-specific default value will be used. Any implementation that instantiates this object must document the system-specific default value or how it is derived.
.1.3.6.1.2.1.10.133.1.7.1.1.4,OPT-IF-MIB::optIfOTUkDAPIExpected,OCTET,read-write,,current,,The DAPI expected by the receiver. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). This object has no effect when optIfOTUkTIMDetMode has the value off(1).
.1.3.6.1.2.1.10.133.1.7.1.1.5,OPT-IF-MIB::optIfOTUkSAPIExpected,OCTET,read-write,,current,,The SAPI expected by the receiver. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). This object has no effect when optIfOTUkTIMDetMode has the value off(1).
.1.3.6.1.2.1.10.133.1.7.1.1.6,OPT-IF-MIB::optIfOTUkTraceIdentifierAccepted,OCTET,read-only,,current,,The actual trace identifier accepted. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). The value of this object is unspecified when optIfOTUkCurrentStatus indicates a near-end defect (i.e., ssf(3), lof(4), ais(5), lom(6)) that prevents extraction of the trace message.
.1.3.6.1.2.1.10.133.1.7.1.1.7,OPT-IF-MIB::optIfOTUkTIMDetMode,INTEGER,read-write,,current,off(1):dapi(2):sapi(3):both(4),Indicates the mode of the Trace Identifier Mismatch (TIM) Detection function. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). The default value of this object is off(1).
.1.3.6.1.2.1.10.133.1.7.1.1.8,OPT-IF-MIB::optIfOTUkTIMActEnabled,INTEGER,read-write,,current,true(1):false(2),Indicates whether the Trace Identifier Mismatch (TIM) Consequent Action function is enabled. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). This object has no effect when optIfOTUkTIMDetMode has the value off(1). The default value of this object is false(2).
.1.3.6.1.2.1.10.133.1.7.1.1.9,OPT-IF-MIB::optIfOTUkDEGThr,Unsigned32,read-write,,current,,Indicates the threshold level for declaring a performance monitoring (PM) Second to be bad. A PM Second is declared bad if the percentage of detected errored blocks in that second is greater than or equal to optIfOTUkDEGThr. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). The default value of this object is Severely Errored Second (SES) Estimator (See ITU-T G.7710).
.1.3.6.1.2.1.10.133.1.7.1.1.10,OPT-IF-MIB::optIfOTUkDEGM,Unsigned32,read-write,,current,,Indicates the threshold level for declaring a Degraded Signal defect (dDEG). A dDEG shall be declared if optIfOTUkDEGM consecutive bad PM Seconds are detected. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). The default value of this object is 7 (See ITU-T G.7710).
.1.3.6.1.2.1.10.133.1.7.1.1.11,OPT-IF-MIB::optIfOTUkSinkAdaptActive,INTEGER,read-write,,current,true(1):false(2),Indicates whether the sink adaptation function is activated or not. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). The default value of this object is false(2).
.1.3.6.1.2.1.10.133.1.7.1.1.12,OPT-IF-MIB::optIfOTUkSourceAdaptActive,INTEGER,read-write,,current,true(1):false(2),Indicates whether the source adaptation function is activated or not. This object is only applicable to the source function, i.e., only when optIfOTUkDirectionality has the value source(2) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value sink(1). The default value of this object is false(2).
.1.3.6.1.2.1.10.133.1.7.1.1.13,OPT-IF-MIB::optIfOTUkSinkFECEnabled,INTEGER,read-write,,current,true(1):false(2),If Forward Error Correction (FEC) is supported, this object indicates whether FEC at the OTUk sink adaptation function is enabled or not. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2). The default value of this object is true(1).
.1.3.6.1.2.1.10.133.1.7.1.1.14,OPT-IF-MIB::optIfOTUkCurrentStatus,BITS,read-only,,current,tim(0):deg(1):bdi(2):ssf(3):lof(4):ais(5):lom(6),Indicates the defect condition of the entity, if any. This object is only applicable to the sink function, i.e., only when optIfOTUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfOTUkDirectionality has the value source(2).
.1.3.6.1.2.1.10.133.1.7.2,OPT-IF-MIB::optIfGCC0ConfigTable,,not-accessible,,current,,A table of GCC0 configuration information.
.1.3.6.1.2.1.10.133.1.7.2.1,OPT-IF-MIB::optIfGCC0ConfigEntry,,not-accessible,ifIndex:optIfGCC0Directionality,current,,A conceptual row that contains GCC0 configuration information of an interface. Each instance must correspond to an instance of optIfOTUkConfigEntry. Separate source and/or sink instances may exist for a given ifIndex value, or a single bidirectional instance may exist, but a bidirectional instance may not coexist with a source or sink instance. Instances of this conceptual row persist across agent restarts.
.1.3.6.1.2.1.10.133.1.7.2.1.1,OPT-IF-MIB::optIfGCC0Directionality,INTEGER,not-accessible,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity. The values source(2) and bidirectional(3) are not allowed if the corresponding instance of optIfOTUkDirectionality has the value sink(1). The values sink(1) and bidirectional(3) are not allowed if the corresponding instance of optIfOTUkDirectionality has the value source(2).
.1.3.6.1.2.1.10.133.1.7.2.1.2,OPT-IF-MIB::optIfGCC0Application,OCTET,read-create,,current,,Indicates the application transported by the GCC0 entity. Example applications are ECC, User data channel. The value of this object may not be changed when optIfGCC0RowStatus has the value active(1).
.1.3.6.1.2.1.10.133.1.7.2.1.3,OPT-IF-MIB::optIfGCC0RowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This columnar object is used for creating and deleting a conceptual row of the optIfGCC0 config table. It is used to model the addGCC0Access and removeGCC0Access operations of an OTUk_TTP for GCC0 access control as defined in G.874.1. Setting RowStatus to createAndGo or createAndWait implies addGCC0Access. Setting RowStatus to destroy implies removeGCC0Access.
.1.3.6.1.2.1.10.133.1.8,OPT-IF-MIB::optIfODUk,,,,,,
.1.3.6.1.2.1.10.133.1.8.1,OPT-IF-MIB::optIfODUkConfigTable,,not-accessible,,current,,A table of ODUk configuration information.
.1.3.6.1.2.1.10.133.1.8.1.1,OPT-IF-MIB::optIfODUkConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains ODUk configuration information of an interface.
.1.3.6.1.2.1.10.133.1.8.1.1.1,OPT-IF-MIB::optIfODUkDirectionality,INTEGER,read-only,,current,sink(1):source(2):bidirectional(3),Indicates the directionality of the entity.
.1.3.6.1.2.1.10.133.1.8.1.1.2,OPT-IF-MIB::optIfODUkBitRateK,Integer32,read-only,,current,,Indicates the bit rate of the entity.
.1.3.6.1.2.1.10.133.1.8.1.1.3,OPT-IF-MIB::optIfODUkTcmFieldsInUse,BITS,read-only,,current,tcmField1(0):tcmField2(1):tcmField3(2):tcmField4(3):tcmField5(4):tcmField6(5),Indicates the TCM field(s) that are currently in use. The positions of the bits correspond to the TCM fields. A bit that is set to 1 means that the corresponding TCM field is used. This object will be updated when rows are created in or deleted from the optIfODUkTConfigTable, or the optIfODUkTNimConfigTable.
.1.3.6.1.2.1.10.133.1.8.1.1.4,OPT-IF-MIB::optIfODUkPositionSeqCurrentSize,Unsigned32,read-only,,current,,This variable indicates the current size of the position sequence (i.e., number of TCM function and/or GCC12 access that have been created in the ODUk interface). When the value of this variable is greater than zero, it means that one or more TCM function and/or GCC12 access have been created in the ODUk interface. In this case, there will be as many rows in the optIfODUkPositionSeqTable as the value of optIfODUkPositionSeqCurrentSize corresponding to this ODUk interface, one row for each TCM function or GCC12 access. The position of the TCM function and/or GCC12 access within the sequence is indicated by the optIfODUkPositionSeqPosition variable in optIfODUkPositionSeqTable. The optIfODUkPositionSeqTable also provides pointers to the corresponding TCM function (optIfODUkT) and GCC12 access (optIfGCC12) entities.
.1.3.6.1.2.1.10.133.1.8.1.1.5,OPT-IF-MIB::optIfODUkTtpPresent,INTEGER,read-only,,current,true(1):false(2),This object has the value true(1) if the ifEntry under which it is instantiated contains an ODUk Trail Termination Point, i.e., is the endpoint of an ODUk path. In that case there will be a corresponding row in the ODUk TTP config table and it will not be possible to create corresponding rows in the ODUk NIM config table. This object has the value false(2) if the ifEntry under which it is instantiated contains an intermediate ODUk Connection Termination Point. In that case there is no corresponding row in the ODUk TTP config table, but it will be possible to create corresponding rows in the ODUk NIM config table. This object also affects the allowable options in rows created in the GCC12 config table and in the ODUkT config table, as specified in the DESCRIPTION clauses of the columns in those tables.
.1.3.6.1.2.1.10.133.1.8.2,OPT-IF-MIB::optIfODUkTtpConfigTable,,not-accessible,,current,,A table of ODUk TTP configuration information.
.1.3.6.1.2.1.10.133.1.8.2.1,OPT-IF-MIB::optIfODUkTtpConfigEntry,,not-accessible,ifIndex,current,,A conceptual row that contains ODUk TTP configuration information of an interface.
.1.3.6.1.2.1.10.133.1.8.2.1.1,OPT-IF-MIB::optIfODUkTtpTraceIdentifierTransmitted,OCTET,read-write,,current,,The trace identifier transmitted. This object is applicable when optIfODUkDirectionality has the value source(2) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value sink(1). If no value is ever set by a management entity for this object, system-specific default value will be used. Any implementation that instantiates this object must document the system-specific default value or how it is derived.
.1.3.6.1.2.1.10.133.1.8.2.1.2,OPT-IF-MIB::optIfODUkTtpDAPIExpected,OCTET,read-write,,current,,The DAPI expected by the receiver. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). This object has no effect when optIfODUkTtpTIMDetMode has the value off(1).
.1.3.6.1.2.1.10.133.1.8.2.1.3,OPT-IF-MIB::optIfODUkTtpSAPIExpected,OCTET,read-write,,current,,The SAPI expected by the receiver. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). This object has no effect when optIfODUkTtpTIMDetMode has the value off(1).
.1.3.6.1.2.1.10.133.1.8.2.1.4,OPT-IF-MIB::optIfODUkTtpTraceIdentifierAccepted,OCTET,read-only,,current,,The actual trace identifier accepted. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). The value of this object is unspecified when optIfODUkTtpCurrentStatus indicates a near-end defect (i.e., oci(0), lck(1), ssf(5)) that prevents extraction of the trace message.
.1.3.6.1.2.1.10.133.1.8.2.1.5,OPT-IF-MIB::optIfODUkTtpTIMDetMode,INTEGER,read-write,,current,off(1):dapi(2):sapi(3):both(4),Indicates the mode of the Trace Identifier Mismatch (TIM) Detection function. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). The default value of this object is off(1).
.1.3.6.1.2.1.10.133.1.8.2.1.6,OPT-IF-MIB::optIfODUkTtpTIMActEnabled,INTEGER,read-write,,current,true(1):false(2),Indicates whether the Trace Identifier Mismatch (TIM) Consequent Action function is enabled. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). This object has no effect when optIfODUkTtpTIMDetMode has the value off(1). The default value of this object is false(2).
.1.3.6.1.2.1.10.133.1.8.2.1.7,OPT-IF-MIB::optIfODUkTtpDEGThr,Unsigned32,read-write,,current,,Indicates the threshold level for declaring a performance monitoring (PM) Second to be bad. A PM Second is declared bad if the percentage of detected errored blocks in that second is greater than or equal to optIfODUkDEGThr. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). The default value of this object is Severely Errored Second (SES) Estimator (See ITU-T G.7710).
.1.3.6.1.2.1.10.133.1.8.2.1.8,OPT-IF-MIB::optIfODUkTtpDEGM,Unsigned32,read-write,,current,,Indicates the threshold level for declaring a Degraded Signal defect (dDEG). A dDEG shall be declared if optIfODUkDEGM consecutive bad PM Seconds are detected. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2). The default value of this object is 7 (See ITU-T G.7710).
.1.3.6.1.2.1.10.133.1.8.2.1.9,OPT-IF-MIB::optIfODUkTtpCurrentStatus,BITS,read-only,,current,oci(0):lck(1):tim(2):deg(3):bdi(4):ssf(5),Indicates the defect condition of the entity, if any. This object is only applicable to the sink function, i.e., only when optIfODUkDirectionality has the value sink(1) or bidirectional(3). It must not be instantiated in rows where optIfODUkDirectionality has the value source(2).
.1.3.6.1.2.1.10.133.1.8.3,OPT-IF-MIB::optIfODUkPositionSeqTable,,not-accessible,,current,,A table of ODUk Position Sequence information.
.1.3.6.1.2.1.10.133.1.8.3.1,OPT-IF-MIB::optIfODUkPositionSeqEntry,,not-accessible,ifIndex:optIfODUkPositionSeqIndex,current,,A conceptual row that contains ODUk position sequence information of an ODUk interface. The ODUk interface is identified by the ifIndex. Associated with each ODUk interface there may be one of more conceptual rows in the optIfODUkPositionSeqTable. Each row represents a TCM or GCC12 access function within the associated ODUk interface. Rows of the optIfODUkPositionSeqTable table are created/deleted as the result of the creation/deletion of the optIfODUkT or optIfGCC12 entities.
.1.3.6.1.2.1.10.133.1.8.3.1.1,OPT-IF-MIB::optIfODUkPositionSeqIndex,Unsigned32,not-accessible,,current,,This variable identifies a row in the optIfODUkPositionSeqTable Table. Each row of the optIfODUkPositionSeqTable Table represents a TCM or GCC12 access function within the associated ODUk interface.
.1.3.6.1.2.1.10.133.1.8.3.1.2,OPT-IF-MIB::optIfODUkPositionSeqPosition,Unsigned32,read-only,,current,,This variable indicates the position of the TCM or GCC12 access function within the sequence of TCMs & GCC12 access functions of the associated ODUk interface. The TCM or GCC12 presented by this row is referenced by the optIfODUkPositionSeqPointer variable.
.1.3.6.1.2.1.10.133.1.8.3.1.3,OPT-IF-MIB::optIfODUkPositionSeqPointer,OBJECT,read-only,,current,,This variable identifies the TCM or GCC12 access function by pointing to the corresponding optIfODUkT or optIfGCC12 entity.
.1.3.6.1.2.1.10.133.1.8.4,OPT-IF-MIB::optIfODUkNimConfigTable,,not-accessible,,current,,A table of ODUkNim configuration information.
.1.3.6.1.2.1.10.133.1.8.4.1,OPT-IF-MIB::optIfODUkNimConfigEntry,,not-accessible,ifIndex:optIfODUkNimDirectionality,current,,A conceptual row that contains ODUkNim configuration information of an interface. Each instance must correspond to an instance of optIfODUkConfigEntry for which optIfODUkTtpPresent has the value false(2). Instances of this conceptual row persist across agent restarts, and read-create columns other than the status column may be modified while the row is active.
.1.3.6.1.2.1.10.133.1.8.4.1.1,OPT-IF-MIB::optIfODUkNimDirectionality,INTEGER,not-accessible,,current,sink(1):source(2),Specifies the monitor point for the ODUk Path non-intrusive monitoring function. The value source(2) is not allowed if the corresponding instance of optIfODUkDirectionality has the value sink(1), and the value sink(1) is not allowed if the corresponding instance of optIfODUkDirectionality has the value source(2). Either the value sink(1) or source(2) is allowed if the corresponding instance of optIfODUkDirectionality has the value bidirectional(3). The value sink(1) means monitoring at the sink direction path signal of the ODUk CTP. The value source(2) means monitoring at the source direction path signal of the ODUk CTP. Monitoring the source direction of an ODUk CTP is necessary in those cases where the ODUk CTP is at an SNCP (Subnetwork Connection Protection) end (e.g., see Figure I.1.2/G.874.1). If one would like to get the performance of the protected connection, one cannot use the NIM function at both ODUk CTP sinks (before the matrix), instead one should monitor the signal at the source ODUk CTP after the matrix.
.1.3.6.1.2.1.10.133.1.8.4.1.2,OPT-IF-MIB::optIfODUkNimDAPIExpected,OCTET,read-create,,current,,The DAPI expected by the receiver. This object has no effect if optIfODUkNimTIMDetMode has the value off(1) or sapi(3).
.1.3.6.1.2.1.10.133.1.8.4.1.3,OPT-IF-MIB::optIfODUkNimSAPIExpected,OCTET,read-create,,current,,The SAPI expected by the receiver. This object has no effect if optIfODUkNimTIMDetMode has the value off(1) or dapi(2).
.1.3.6.1.2.1.10.133.1.8.4.1.4,OPT-IF-MIB::optIfODUkNimTraceIdentifierAccepted,OCTET,read-only,,current,,The actual trace identifier accepted. The value of this object is unspecified if optIfODUkNimCurrentStatus has any of the bit positions oci(0), lck(1), or ssf(5) set or if optIfODUkNimRowStatus has any value other than active(1).
.1.3.6.1.2.1.10.133.1.8.4.1.5,OPT-IF-MIB::optIfODUkNimTIMDetMode,INTEGER,read-create,,current,off(1):dapi(2):sapi(3):both(4),Indicates the mode of the Trace Identifier Mismatch (TIM) Detection function.
.1.3.6.1.2.1.10.133.1.8.4.1.6,OPT-IF-MIB::optIfODUkNimTIMActEnabled,INTEGER,read-create,,current,true(1):false(2),Indicates whether the Trace Identifier Mismatch (TIM) Consequent Action function is enabled.
.1.3.6.1.2.1.10.133.1.8.4.1.7,OPT-IF-MIB::optIfODUkNimDEGThr,Unsigned32,read-create,,current,,Indicates the threshold level for declaring a performance monitoring (PM) Second to be bad. A PM Second is declared bad if the percentage of detected errored blocks in that second is greater than or equal to optIfODUkNimDEGThr.
.1.3.6.1.2.1.10.133.1.8.4.1.8,OPT-IF-MIB::optIfODUkNimDEGM,Unsigned32,read-create,,current,,Indicates the threshold level for declaring a Degraded Signal defect (dDEG). A dDEG shall be declared if optIfODUkNimDEGM consecutive bad PM Seconds are detected.
.1.3.6.1.2.1.10.133.1.8.4.1.9,OPT-IF-MIB::optIfODUkNimCurrentStatus,BITS,read-only,,current,oci(0):lck(1):tim(2):deg(3):bdi(4):ssf(5),Indicates the defect condition of the entity, if any. The value of this object is unspecified if optIfODUkNimRowStatus has any value other than active(1).
.1.3.6.1.2.1.10.133.1.8.4.1.10,OPT-IF-MIB::optIfODUkNimRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This columnar object is used for creating and deleting a conceptual row of the optIfODUkNim config table. It is used to model the activateNim and deactivateNim operations of an OTUk_CTP for non-intrusive monitoring control as defined in G.874.1. Setting RowStatus to createAndGo or createAndWait implies activateNim. Setting RowStatus to destroy implies deactivateNim.
.1.3.6.1.2.1.10.133.1.8.5,OPT-IF-MIB::optIfGCC12ConfigTable,,not-accessible,,current,,A table of GCC12 configuration information. The GCC function processes the GCC overhead bytes passing through them but leave the remainder of the ODUk overhead and payload data alone.
.1.3.6.1.2.1.10.133.1.8.5.1,OPT-IF-MIB::optIfGCC12ConfigEntry,,not-accessible,ifIndex:optIfGCC12Codirectional:optIfGCC12GCCAccess,current,,A conceptual row that contains GCC12 configuration information of an interface. Each instance must correspond to an instance of optIfODUkConfigEntry. Separate instances providing GCC1-only access and GCC2-only access may exist for a given ifIndex value, or a single instance providing GCC1 + GCC2 may exist, but a GCC1 + GCC2 instance may not coexist with a GCC1-only or GCC2-only instance. Instances of this conceptual row persist across agent restarts.
.1.3.6.1.2.1.10.133.1.8.5.1.1,OPT-IF-MIB::optIfGCC12Codirectional,INTEGER,not-accessible,,current,true(1):false(2),Indicates the directionality of the GCC12 termination with respect to the associated ODUk CTP. The value true(1) means that the sink part of the GCC12 extracts COMMS data from the signal at the input to the ODUk CTP sink and the source part of the GCC12 inserts COMMS data into the signal at the output of the ODUk CTP source. The value false(2) means that the sink part of the GCC12 extracts COMMS data from the signal at the output of the ODUk CTP source and the source part of the GCC12 inserts COMMS data into the signal at the input of the ODUk CTP sink. This attribute may assume either value when the corresponding instance of optIfODUkTtpPresent has the value false(2). When the value of the corresponding instance of optIfODUkTtpPresent is true(1) then the only value allowed for this attribute is true(1).
.1.3.6.1.2.1.10.133.1.8.5.1.2,OPT-IF-MIB::optIfGCC12GCCAccess,INTEGER,not-accessible,,current,gcc1(1):gcc2(2):gcc1and2(3),Indicates the GCC access represented by the entity.
.1.3.6.1.2.1.10.133.1.8.5.1.3,OPT-IF-MIB::optIfGCC12GCCPassThrough,INTEGER,read-create,,current,true(1):false(2),Controls whether the selected GCC overhead bytes are passed through or modified. The value true(1) means that the selected GCC overhead bytes are passed through unmodified from the ODUk CTP input to the ODUk CTP output. The value false(2) means that the selected GCC overhead bytes are set to zero at the ODUk CTP output after the extraction of the COMMS data. This object has no effect if the corresponding instance of optIfODUkTtpPresent has the value true(1). The value of this object may not be changed when optIfGCC12RowStatus has the value active(1).
.1.3.6.1.2.1.10.133.1.8.5.1.4,OPT-IF-MIB::optIfGCC12Application,OCTET,read-create,,current,,Indicates the application transported by the GCC12 entity. Example applications are ECC, User data channel. The value of this object may not be changed when optIfGCC12RowStatus has the value active(1).
.1.3.6.1.2.1.10.133.1.8.5.1.5,OPT-IF-MIB::optIfGCC12RowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This columnar object is used for creating and deleting a conceptual row of the optIfGCC12 config table. It is used to model the addGCC12Access and removeGCC12Access operations of an ODUk_CTP or ODUk_TTP for GCC12 access control as defined in G.874.1. Setting RowStatus to createAndGo or createAndWait implies addGCC12Access. Setting RowStatus to destroy implies removeGCC12Access. Successful addition/removal of the GCC12 access function will result in updating the optIfODUkPositionSeqCurrentSize variable and the optIfODUkPositionSeqTable table of the associated ODUk entry in the optIfODUkConfigTable.
.1.3.6.1.2.1.10.133.1.9,OPT-IF-MIB::optIfODUkT,,,,,,
.1.3.6.1.2.1.10.133.1.9.1,OPT-IF-MIB::optIfODUkTConfigTable,,not-accessible,,current,,A table of ODUkT configuration information.
.1.3.6.1.2.1.10.133.1.9.1.1,OPT-IF-MIB::optIfODUkTConfigEntry,,not-accessible,ifIndex:optIfODUkTTcmField:optIfODUkTCodirectional,current,,A conceptual row that contains ODUkT configuration information of an interface. Each instance must correspond to an instance of optIfODUkConfigEntry. Rows in this table are mutually exclusive with rows in the ODUkT NIM config table -- in other words, this row object may not be instantiated for a given pair of ifIndex and TCM field values if a corresponding instance of optIfODUkTNimConfigEntry already exists. Instances of this conceptual row persist across agent restarts. Except where noted otherwise, read-create columns other than the status column may be modified while the row is active.
.1.3.6.1.2.1.10.133.1.9.1.1.1,OPT-IF-MIB::optIfODUkTTcmField,Unsigned32,not-accessible,,current,,Indicates the tandem connection monitoring field of the ODUk OH. Valid values are integers from 1 to 6.
.1.3.6.1.2.1.10.133.1.9.1.1.2,OPT-IF-MIB::optIfODUkTCodirectional,INTEGER,not-accessible,,current,true(1):false(2),Indicates the directionality of the ODUkT termination point with respect to the associated ODUk CTP. The value true(1) means that the sink part of the ODUkT TP extracts TCM data from the signal at the input to the ODUk CTP sink and the source part of the ODUkT TP inserts TCM data into the signal at the output of the ODUk CTP source. The value false(2) means that the sink part of the ODUkT TP extracts TCM data from the signal at the output of the ODUk CTP source and the source part of the ODUkT TP inserts TCM data into the signal at the input of the ODUk CTP sink. This attribute may assume either value when the corresponding instance of optIfODUkTtpPresent has the value false(2). When the value of the corresponding instance of optIfODUkTtpPresent is true(1) then the only value allowed for this attribute is true(1).
.1.3.6.1.2.1.10.133.1.9.1.1.3,OPT-IF-MIB::optIfODUkTTraceIdentifierTransmitted,OCTET,read-create,,current,,The trace identifier transmitted. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value false(2), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value true(1). It must not be instantiated in rows for all other cases.
.1.3.6.1.2.1.10.133.1.9.1.1.4,OPT-IF-MIB::optIfODUkTDAPIExpected,OCTET,read-create,,current,,The DAPI expected by the receiver. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. This object has no effect when optIfODUkTTIMDetMode has the value off(1).
.1.3.6.1.2.1.10.133.1.9.1.1.5,OPT-IF-MIB::optIfODUkTSAPIExpected,OCTET,read-create,,current,,The SAPI expected by the receiver. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. This object has no effect when optIfODUkTTIMDetMode has the value off(1).
.1.3.6.1.2.1.10.133.1.9.1.1.6,OPT-IF-MIB::optIfODUkTTraceIdentifierAccepted,OCTET,read-only,,current,,The actual trace identifier accepted. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. The value of this object is unspecified when optIfODUkTCurrentStatus indicates a near-end defect (i.e., oci(0), lck(1), ssf(5)) that prevents extraction of the trace message.
.1.3.6.1.2.1.10.133.1.9.1.1.7,OPT-IF-MIB::optIfODUkTTIMDetMode,INTEGER,read-create,,current,off(1):dapi(2):sapi(3):both(4),Indicates the mode of the Trace Identifier Mismatch (TIM) Detection function. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. The default value of this object is off(1).
.1.3.6.1.2.1.10.133.1.9.1.1.8,OPT-IF-MIB::optIfODUkTTIMActEnabled,INTEGER,read-create,,current,true(1):false(2),Indicates whether the Trace Identifier Mismatch (TIM) Consequent Action function is enabled. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. This object has no effect when optIfODUkTTIMDetMode has the value off(1). The default value of this object is false(2).
.1.3.6.1.2.1.10.133.1.9.1.1.9,OPT-IF-MIB::optIfODUkTDEGThr,Unsigned32,read-create,,current,,Indicates the threshold level for declaring a performance monitoring (PM) Second to be bad. A PM Second is declared bad if the percentage of detected errored blocks in that second is greater than or equal to optIfODUkTDEGThr. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. The default value of this object is Severely Errored Second (SES) Estimator (See ITU-T G.7710).
.1.3.6.1.2.1.10.133.1.9.1.1.10,OPT-IF-MIB::optIfODUkTDEGM,Unsigned32,read-create,,current,,Indicates the threshold level for declaring a Degraded Signal defect (dDEG). A dDEG shall be declared if optIfODUkTDEGM consecutive bad PM Seconds are detected. This object is applicable only to the following three cases. (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases. The default value of this object is 7 (See ITU-T G.7710).
.1.3.6.1.2.1.10.133.1.9.1.1.11,OPT-IF-MIB::optIfODUkTSinkMode,INTEGER,read-create,,current,operational(1):monitor(2),This variable specifies the TCM mode at the entity. The value operational(1) means that TCM Overhead (TCMOH) processes (see ITU-T G.798) shall be performed and consequent actions for AIS, Trail Signal Fail (TSF), Trail Signal Degraded (TSD) shall be initiated in case of defects. The value monitor(2) means that TCMOH processes shall be performed but consequent actions for AIS, Trail Server Failure (TSF), Trail Server Degraded (TSD) shall _not_ be initiated in case of defects. This object is applicable only when the value of optIfODUkTtpPresent is false(2) and also either one of the following three cases holds: (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases.
.1.3.6.1.2.1.10.133.1.9.1.1.12,OPT-IF-MIB::optIfODUkTSinkLockSignalAdminState,INTEGER,read-create,,current,locked(1):normal(2),Provides the capability to provision the LOCK signal, which is one of the ODUk maintenance signals, at the ODUKT sink. When a Tandem Connection endpoint is set to admin state locked, it inserts the ODUk-LCK signal in the sink direction. This object is applicable only when the value of optIfODUkTtpPresent is false(2) and also either one of the following three cases holds: (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases.
.1.3.6.1.2.1.10.133.1.9.1.1.13,OPT-IF-MIB::optIfODUkTSourceLockSignalAdminState,INTEGER,read-create,,current,locked(1):normal(2),Provides the capability to provision the LOCK signal, which is one of the ODUk maintenance signals, at the source. When a Tandem Connection endpoint is set to admin state locked, it inserts the ODUk-LCK signal in the source direction. This object is applicable only when either one of the following three cases holds: (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value false(2), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value true(1). It must not be instantiated in rows for all other cases.
.1.3.6.1.2.1.10.133.1.9.1.1.14,OPT-IF-MIB::optIfODUkTCurrentStatus,BITS,read-only,,current,oci(0):lck(1):tim(2):deg(3):bdi(4):ssf(5),Indicates the defect condition of the entity, if any. This object is applicable only when either one of the following three cases holds: (i) optIfODUkDirectionality has the value bidirectional(3), or (ii) optIfODUkDirectionality has the value sink(1) and optIfODUkTCodirectional has the value true(1), or (iii) optIfODUkDirectionality has the value source(3) and optIfODUkTCodirectional has the value false(2). It must not be instantiated in rows for all other cases.
.1.3.6.1.2.1.10.133.1.9.1.1.15,OPT-IF-MIB::optIfODUkTRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This columnar object is used for creating and deleting a conceptual row of the optIfODUkT config table. It is used to model the addTCM and removeTCM operations of an ODUk_CTP or ODUk_TTP for Tandem connection monitoring as defined in ITU-T G.874.1. Setting RowStatus to createAndGo or createAndWait implies addTCM. Setting RowStatus to destroy implies removeTCM. Successful addition/removal of TCM will result in updating the optIfODUkTcmFieldsInUse and optIfODUkPositionSeqCurrentSize variables and the optIfODUkPositionSeqTable table of the associated ODUk entry in the optIfODUkConfigTable.
.1.3.6.1.2.1.10.133.1.9.2,OPT-IF-MIB::optIfODUkTNimConfigTable,,not-accessible,,current,,A table of ODUkTNim configuration information.
.1.3.6.1.2.1.10.133.1.9.2.1,OPT-IF-MIB::optIfODUkTNimConfigEntry,,not-accessible,ifIndex:optIfODUkTNimTcmField:optIfODUkTNimDirectionality,current,,A conceptual row that contains ODUkTNim configuration information of an interface. Each instance must correspond to an instance of optIfODUkConfigEntry. Rows in this table are mutually exclusive with rows in the ODUkT config table -- in other words, this row object may not be instantiated for a given pair of ifIndex and TCM field values if a corresponding instance of optIfODUkTConfigEntry already exists. Instances of this conceptual row persist across agent restarts, and read-create columns other than the status column may be modified while the row is active.
.1.3.6.1.2.1.10.133.1.9.2.1.1,OPT-IF-MIB::optIfODUkTNimTcmField,Unsigned32,not-accessible,,current,,Indicates the tandem connection monitoring field of the ODUk OH on which non-intrusive monitoring is performed. Valid values are integers from 1 to 6.
.1.3.6.1.2.1.10.133.1.9.2.1.2,OPT-IF-MIB::optIfODUkTNimDirectionality,INTEGER,not-accessible,,current,sink(1):source(2),Specifies the monitor point for the ODUk TCM non-intrusive monitoring function. The value source(2) is not allowed if the corresponding instance of optIfODUkDirectionality has the value sink(1), and the value sink(1) is not allowed if the corresponding instance of optIfODUkDirectionality has the value source(2). Either the value sink(1) or source(2) is allowed if the corresponding instance of optIfODUkDirectionality has the value bidirectional(3). The value sink(1) means monitoring at the sink direction TCM signal of the ODUk CTP. The value source(2) means monitoring at the source direction path signal of the ODUk CTP.
.1.3.6.1.2.1.10.133.1.9.2.1.3,OPT-IF-MIB::optIfODUkTNimDAPIExpected,OCTET,read-create,,current,,The DAPI expected by the receiver. This object has no effect if optIfODUkTNimTIMDetMode has the value off(1) or sapi(3).
.1.3.6.1.2.1.10.133.1.9.2.1.4,OPT-IF-MIB::optIfODUkTNimSAPIExpected,OCTET,read-create,,current,,The SAPI expected by the receiver. This object has no effect if optIfODUkTNimTIMDetMode has the value off(1) or dapi(2).
.1.3.6.1.2.1.10.133.1.9.2.1.5,OPT-IF-MIB::optIfODUkTNimTraceIdentifierAccepted,OCTET,read-only,,current,,The actual trace identifier accepted. The value of this object is unspecified if optIfODUkTNimCurrentStatus has any of the bit positions oci(0), lck(1), or ssf(5) set or if optIfODUkTNimRowStatus has any value other than active(1).
.1.3.6.1.2.1.10.133.1.9.2.1.6,OPT-IF-MIB::optIfODUkTNimTIMDetMode,INTEGER,read-create,,current,off(1):dapi(2):sapi(3):both(4),Indicates the mode of the Trace Identifier Mismatch (TIM) Detection function.
.1.3.6.1.2.1.10.133.1.9.2.1.7,OPT-IF-MIB::optIfODUkTNimTIMActEnabled,INTEGER,read-create,,current,true(1):false(2),Indicates whether the Trace Identifier Mismatch (TIM) Consequent Action function is enabled.
.1.3.6.1.2.1.10.133.1.9.2.1.8,OPT-IF-MIB::optIfODUkTNimDEGThr,Unsigned32,read-create,,current,,Indicates the threshold level for declaring a performance monitoring (PM) Second to be bad. A PM Second is declared bad if the percentage of detected errored blocks in that second is greater than or equal to optIfODUkTNimDEGThr.
.1.3.6.1.2.1.10.133.1.9.2.1.9,OPT-IF-MIB::optIfODUkTNimDEGM,Unsigned32,read-create,,current,,Indicates the threshold level for declaring a Degraded Signal defect (dDEG). A dDEG shall be declared if optIfODUkTNimDEGM consecutive bad PM Seconds are detected.
.1.3.6.1.2.1.10.133.1.9.2.1.10,OPT-IF-MIB::optIfODUkTNimCurrentStatus,BITS,read-only,,current,oci(0):lck(1):tim(2):deg(3):bdi(4):ssf(5),Indicates the defect condition of the entity, if any. The value of this object is unspecified if optIfODUkTNimRowStatus has any value other than active(1).
.1.3.6.1.2.1.10.133.1.9.2.1.11,OPT-IF-MIB::optIfODUkTNimRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This columnar object is used for creating and deleting a conceptual row of the optIfODUkTNim config table. It is used to model the addTCM and removeTCM operations of an ODUk_CTP or ODUk_TTP for non-intrusive Tandem connection monitoring as defined in ITU-T G.874.1. Setting RowStatus to createAndGo or createAndWait implies addTCM. Setting RowStatus to destroy implies removeTCM. Successful addition/removal of Nim TCM will result in updating the optIfODUkPositionSeqCurrentSize variable and the optIfODUkPositionSeqTable table of the associated ODUk entry in the optIfODUkConfigTable.
.1.3.6.1.2.1.10.133.2,OPT-IF-MIB::optIfConfs,,,,,,
.1.3.6.1.2.1.10.133.2.1,OPT-IF-MIB::optIfGroups,,,,,,
.1.3.6.1.2.1.10.133.2.1.1,OPT-IF-MIB::optIfOTMnGroup,,,,,,A collection of OTMn structure information objects.
.1.3.6.1.2.1.10.133.2.1.2,OPT-IF-MIB::optIfPerfMonGroup,,,,,,A collection of performance monitoring interval objects.
.1.3.6.1.2.1.10.133.2.1.3,OPT-IF-MIB::optIfOTSnCommonGroup,,,,,,A collection of configuration objects applicable to all OTSn interfaces.
.1.3.6.1.2.1.10.133.2.1.4,OPT-IF-MIB::optIfOTSnSourceGroupFull,,,,,,A collection of configuration objects applicable to full-functionality/IaDI OTSn interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.5,OPT-IF-MIB::optIfOTSnAPRStatusGroup,,,,,,A collection of objects applicable to OTSn interfaces that support Automatic Power Reduction functions.
.1.3.6.1.2.1.10.133.2.1.6,OPT-IF-MIB::optIfOTSnAPRControlGroup,,,,,,A collection of objects applicable to OTSn interfaces that provide Automatic Power Reduction control functions.
.1.3.6.1.2.1.10.133.2.1.7,OPT-IF-MIB::optIfOTSnSinkGroupBasic,,,,,,A collection of configuration objects applicable to all OTSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.8,OPT-IF-MIB::optIfOTSnSinkGroupFull,,,,,,A collection of configuration objects applicable to full-functionality/IaDI OTSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.9,OPT-IF-MIB::optIfOTSnSinkPreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OTSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.10,OPT-IF-MIB::optIfOTSnSinkPreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OTSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.11,OPT-IF-MIB::optIfOTSnSourcePreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OTSn interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.12,OPT-IF-MIB::optIfOTSnSourcePreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OTSn interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.13,OPT-IF-MIB::optIfOMSnCommonGroup,,,,,,A collection of configuration objects applicable to all OMSn interfaces.
.1.3.6.1.2.1.10.133.2.1.14,OPT-IF-MIB::optIfOMSnSinkGroupBasic,,,,,,A collection of configuration objects applicable to all OMSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.15,OPT-IF-MIB::optIfOMSnSinkPreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OMSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.16,OPT-IF-MIB::optIfOMSnSinkPreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OMSn interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.17,OPT-IF-MIB::optIfOMSnSourcePreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OMSn interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.18,OPT-IF-MIB::optIfOMSnSourcePreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OMSn interfaces that that support source functions.
.1.3.6.1.2.1.10.133.2.1.19,OPT-IF-MIB::optIfOChGroupCommonGroup,,,,,,A collection of configuration objects applicable to all OChGroup interfaces.
.1.3.6.1.2.1.10.133.2.1.20,OPT-IF-MIB::optIfOChGroupSinkPreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OChGroup interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.21,OPT-IF-MIB::optIfOChGroupSinkPreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OChGroup interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.22,OPT-IF-MIB::optIfOChGroupSourcePreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OChGroup interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.23,OPT-IF-MIB::optIfOChGroupSourcePreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OChGroup interfaces that that support source functions.
.1.3.6.1.2.1.10.133.2.1.24,OPT-IF-MIB::optIfOChCommonGroup,,,,,,A collection of configuration objects applicable to all OCh interfaces.
.1.3.6.1.2.1.10.133.2.1.25,OPT-IF-MIB::optIfOChSinkGroupBasic,,,,,,A collection of configuration objects applicable to all OCh interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.26,OPT-IF-MIB::optIfOChSinkPreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OCh interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.27,OPT-IF-MIB::optIfOChSinkPreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OCh interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.28,OPT-IF-MIB::optIfOChSourcePreOtnPMGroup,,,,,,A collection of pre-OTN performance monitoring objects applicable to OCh interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.29,OPT-IF-MIB::optIfOChSourcePreOtnPMThresholdGroup,,,,,,A collection of pre-OTN performance monitoring threshold objects applicable to OCh interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.30,OPT-IF-MIB::optIfOTUkCommonGroup,,,,,,A collection of configuration objects applicable to all OTUk interfaces.
.1.3.6.1.2.1.10.133.2.1.31,OPT-IF-MIB::optIfOTUkSourceGroup,,,,,,A collection of configuration objects applicable to OTUk interfaces that support source functions.
.1.3.6.1.2.1.10.133.2.1.32,OPT-IF-MIB::optIfOTUkSinkGroup,,,,,,A collection of configuration objects applicable to OTUk interfaces that support sink functions.
.1.3.6.1.2.1.10.133.2.1.33,OPT-IF-MIB::optIfGCC0Group,,,,,,A collection of GCC0 configuration objects.
.1.3.6.1.2.1.10.133.2.1.34,OPT-IF-MIB::optIfODUkGroup,,,,,,A collection of configuration objects applicable to all ODUk interfaces.
.1.3.6.1.2.1.10.133.2.1.35,OPT-IF-MIB::optIfODUkTtpSourceGroup,,,,,,A collection of configuration objects applicable to all interfaces that support ODUk trail termination source functions.
.1.3.6.1.2.1.10.133.2.1.36,OPT-IF-MIB::optIfODUkTtpSinkGroup,,,,,,A collection of ODUk configuration objects applicable to all interfaces that support ODUk trail termination sink functions.
.1.3.6.1.2.1.10.133.2.1.37,OPT-IF-MIB::optIfODUkNimGroup,,,,,,A collection of ODUk Nim configuration objects.
.1.3.6.1.2.1.10.133.2.1.38,OPT-IF-MIB::optIfGCC12Group,,,,,,A collection of GCC12 configuration objects.
.1.3.6.1.2.1.10.133.2.1.39,OPT-IF-MIB::optIfODUkTCommonGroup,,,,,,A collection of configuration objects applicable to all ODUkT instances.
.1.3.6.1.2.1.10.133.2.1.40,OPT-IF-MIB::optIfODUkTSourceGroup,,,,,,A collection of configuration objects applicable to all ODUkT instances that provide source functions.
.1.3.6.1.2.1.10.133.2.1.41,OPT-IF-MIB::optIfODUkTSinkGroup,,,,,,A collection of configuration objects applicable to all ODUkT instances that provide sink functions.
.1.3.6.1.2.1.10.133.2.1.42,OPT-IF-MIB::optIfODUkTSinkGroupCtp,,,,,,A collection of configuration objects applicable to ODUkT instances not colocated with an ODUk TTP that provide sink functions.
.1.3.6.1.2.1.10.133.2.1.43,OPT-IF-MIB::optIfODUkTNimGroup,,,,,,A collection of ODUkT Nim configuration objects.
.1.3.6.1.2.1.10.133.2.2,OPT-IF-MIB::optIfCompl,,,,,,
.1.3.6.1.2.1.10.133.2.2.1,OPT-IF-MIB::optIfOtnConfigCompl,,,,,,Implementation requirements for the OTN configuration functions defined in this MIB module.
.1.3.6.1.2.1.10.133.2.2.2,OPT-IF-MIB::optIfPreOtnPMCompl,,,,,,Implementation requirements for Pre-OTN performance monitoring functions defined in this MIB module.
.1.3.6.1.2.1.10.134,ETHER-WIS::etherWisMIB,,,,,,The objects in this MIB module are used in conjunction with objects in the SONET-MIB and the MAU-MIB to manage the Ethernet WAN Interface Sublayer (WIS). The following reference is used throughout this MIB module: [IEEE 802.3 Std] refers to: IEEE Std 802.3, 2000 Edition: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications', as amended by IEEE Std 802.3ae-2002, 'IEEE Standard for Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Media Access Control (MAC) Parameters, Physical Layer and Management Parameters for 10 Gb/s Operation', 30 August 2002. Of particular interest are Clause 50, 'WAN Interface Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link Aggregation Management', and Clause 45, 'Management Data Input/Output (MDIO) Interface'. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3637; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.134.1,ETHER-WIS::etherWisObjects,,,,,,
.1.3.6.1.2.1.10.134.1.1,ETHER-WIS::etherWisDevice,,,,,,
.1.3.6.1.2.1.10.134.1.1.1,ETHER-WIS::etherWisDeviceTable,,not-accessible,,current,,The table for Ethernet WIS devices
.1.3.6.1.2.1.10.134.1.1.1.1,ETHER-WIS::etherWisDeviceEntry,,not-accessible,ifIndex,current,,An entry in the Ethernet WIS device table. For each instance of this object there MUST be a corresponding instance of sonetMediumEntry.
.1.3.6.1.2.1.10.134.1.1.1.1.1,ETHER-WIS::etherWisDeviceTxTestPatternMode,INTEGER,read-write,,current,none(1):squareWave(2):prbs31(3):mixedFrequency(4),This variable controls the transmit test pattern mode. The value none(1) puts the the WIS transmit path into the normal operating mode. The value squareWave(2) puts the WIS transmit path into the square wave test pattern mode described in [IEEE 802.3 Std.] subclause 50.3.8.1. The value prbs31(3) puts the WIS transmit path into the PRBS31 test pattern mode described in [IEEE 802.3 Std.] subclause 50.3.8.2. The value mixedFrequency(4) puts the WIS transmit path into the mixed frequency test pattern mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. Any attempt to set this object to a value other than none(1) when the corresponding instance of ifAdminStatus has the value up(1) MUST be rejected with the error inconsistentValue, and any attempt to set the corresponding instance of ifAdminStatus to the value up(1) when an instance of this object has a value other than none(1) MUST be rejected with the error inconsistentValue.
.1.3.6.1.2.1.10.134.1.1.1.1.2,ETHER-WIS::etherWisDeviceRxTestPatternMode,INTEGER,read-write,,current,none(1):prbs31(3):mixedFrequency(4),This variable controls the receive test pattern mode. The value none(1) puts the the WIS receive path into the normal operating mode. The value prbs31(3) puts the WIS receive path into the PRBS31 test pattern mode described in [IEEE 802.3 Std.] subclause 50.3.8.2. The value mixedFrequency(4) puts the WIS receive path into the mixed frequency test pattern mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. Any attempt to set this object to a value other than none(1) when the corresponding instance of ifAdminStatus has the value up(1) MUST be rejected with the error inconsistentValue, and any attempt to set the corresponding instance of ifAdminStatus to the value up(1) when an instance of this object has a value other than none(1) MUST be rejected with the error inconsistentValue.
.1.3.6.1.2.1.10.134.1.1.1.1.3,ETHER-WIS::etherWisDeviceRxTestPatternErrors,Gauge32,read-write,,current,,This object counts the number of errors detected when the WIS receive path is operating in the PRBS31 test pattern mode. It is reset to zero when the WIS receive path initially enters that mode, and it increments each time the PRBS pattern checker detects an error as described in [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is 65535, in which case it remains unchanged. This object is writeable so that it may be reset upon explicit request of a command generator application while the WIS receive path continues to operate in PRBS31 test pattern mode.
.1.3.6.1.2.1.10.134.1.2,ETHER-WIS::etherWisSection,,,,,,
.1.3.6.1.2.1.10.134.1.2.1,ETHER-WIS::etherWisSectionCurrentTable,,not-accessible,,current,,The table for the current state of Ethernet WIS sections.
.1.3.6.1.2.1.10.134.1.2.1.1,ETHER-WIS::etherWisSectionCurrentEntry,,not-accessible,ifIndex,current,,An entry in the etherWisSectionCurrentTable. For each instance of this object there MUST be a corresponding instance of sonetSectionCurrentEntry.
.1.3.6.1.2.1.10.134.1.2.1.1.1,ETHER-WIS::etherWisSectionCurrentJ0Transmitted,OCTET,read-write,,current,,This is the 16-octet section trace message that is transmitted in the J0 byte. The value SHOULD be '89'h followed by fifteen octets of '00'h (or some cyclic shift thereof) when the section trace function is not used, and the implementation SHOULD use that value (or a cyclic shift thereof) as a default if no other value has been set.
.1.3.6.1.2.1.10.134.1.2.1.1.2,ETHER-WIS::etherWisSectionCurrentJ0Received,OCTET,read-only,,current,,This is the 16-octet section trace message that was most recently received in the J0 byte.
.1.3.6.1.2.1.10.134.2,ETHER-WIS::etherWisObjectsPath,,,,,,
.1.3.6.1.2.1.10.134.2.1,ETHER-WIS::etherWisPath,,,,,,
.1.3.6.1.2.1.10.134.2.1.1,ETHER-WIS::etherWisPathCurrentTable,,not-accessible,,current,,The table for the current state of Ethernet WIS paths.
.1.3.6.1.2.1.10.134.2.1.1.1,ETHER-WIS::etherWisPathCurrentEntry,,not-accessible,ifIndex,current,,An entry in the etherWisPathCurrentTable. For each instance of this object there MUST be a corresponding instance of sonetPathCurrentEntry.
.1.3.6.1.2.1.10.134.2.1.1.1.1,ETHER-WIS::etherWisPathCurrentStatus,BITS,read-only,,current,etherWisPathLOP(0):etherWisPathAIS(1):etherWisPathPLM(2):etherWisPathLCD(3),This variable indicates the current status of the path payload with a bit map that can indicate multiple defects at once. The bit positions are assigned as follows: etherWisPathLOP(0) This bit is set to indicate that an LOP-P (Loss of Pointer - Path) defect is being experienced. Note: when this bit is set, sonetPathSTSLOP MUST be set in the corresponding instance of sonetPathCurrentStatus. etherWisPathAIS(1) This bit is set to indicate that an AIS-P (Alarm Indication Signal - Path) defect is being experienced. Note: when this bit is set, sonetPathSTSAIS MUST be set in the corresponding instance of sonetPathCurrentStatus. etherWisPathPLM(1) This bit is set to indicate that a PLM-P (Payload Label Mismatch - Path) defect is being experienced. Note: when this bit is set, sonetPathSignalLabelMismatch MUST be set in the corresponding instance of sonetPathCurrentStatus. etherWisPathLCD(3) This bit is set to indicate that an LCD-P (Loss of Codegroup Delination - Path) defect is being experienced. Since this defect is detected by the PCS and not by the path layer itself, there is no corresponding bit in sonetPathCurrentStatus.
.1.3.6.1.2.1.10.134.2.1.1.1.2,ETHER-WIS::etherWisPathCurrentJ1Transmitted,OCTET,read-write,,current,,This is the 16-octet path trace message that is transmitted in the J1 byte. The value SHOULD be '89'h followed by fifteen octets of '00'h (or some cyclic shift thereof) when the path trace function is not used, and the implementation SHOULD use that value (or a cyclic shift thereof) as a default if no other value has been set.
.1.3.6.1.2.1.10.134.2.1.1.1.3,ETHER-WIS::etherWisPathCurrentJ1Received,OCTET,read-only,,current,,This is the 16-octet path trace message that was most recently received in the J1 byte.
.1.3.6.1.2.1.10.134.2.2,ETHER-WIS::etherWisFarEndPath,,,,,,
.1.3.6.1.2.1.10.134.2.2.1,ETHER-WIS::etherWisFarEndPathCurrentTable,,not-accessible,,current,,The table for the current far-end state of Ethernet WIS paths.
.1.3.6.1.2.1.10.134.2.2.1.1,ETHER-WIS::etherWisFarEndPathCurrentEntry,,not-accessible,ifIndex,current,,An entry in the etherWisFarEndPathCurrentTable. For each instance of this object there MUST be a corresponding instance of sonetFarEndPathCurrentEntry.
.1.3.6.1.2.1.10.134.2.2.1.1.1,ETHER-WIS::etherWisFarEndPathCurrentStatus,BITS,read-only,,current,etherWisFarEndPayloadDefect(0):etherWisFarEndServerDefect(1),This variable indicates the current status at the far end of the path using a bit map that can indicate multiple defects at once. The bit positions are assigned as follows: etherWisFarEndPayloadDefect(0) A far end payload defect (i.e., far end PLM-P or LCD-P) is currently being signaled in G1 bits 5-7. etherWisFarEndServerDefect(1) A far end server defect (i.e., far end LOP-P or AIS-P) is currently being signaled in G1 bits 5-7. Note: when this bit is set, sonetPathSTSRDI MUST be set in the corresponding instance of sonetPathCurrentStatus.
.1.3.6.1.2.1.10.134.3,ETHER-WIS::etherWisConformance,,,,,,
.1.3.6.1.2.1.10.134.3.1,ETHER-WIS::etherWisGroups,,,,,,
.1.3.6.1.2.1.10.134.3.1.1,ETHER-WIS::etherWisDeviceGroupBasic,,,,,,A collection of objects that support test features required of all WIS devices.
.1.3.6.1.2.1.10.134.3.1.2,ETHER-WIS::etherWisDeviceGroupExtra,,,,,,A collection of objects that support optional WIS device test features.
.1.3.6.1.2.1.10.134.3.1.3,ETHER-WIS::etherWisSectionGroup,,,,,,A collection of objects that provide required information about a WIS section.
.1.3.6.1.2.1.10.134.3.1.4,ETHER-WIS::etherWisPathGroup,,,,,,A collection of objects that provide required information about a WIS path.
.1.3.6.1.2.1.10.134.3.1.5,ETHER-WIS::etherWisFarEndPathGroup,,,,,,A collection of objects that provide required information about the far end of a WIS path.
.1.3.6.1.2.1.10.134.3.2,ETHER-WIS::etherWisCompliances,,,,,,
.1.3.6.1.2.1.10.134.3.2.1,ETHER-WIS::etherWisCompliance,,,,,,The compliance statement for interfaces that include the Ethernet WIS. Compliance with the following external compliance statements is prerequisite: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 IF-INVERTED-STACK-MIB ifInvCompliance EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3
.1.3.6.1.2.1.10.166,MPLS-TC-STD-MIB::mplsStdMIB,,,,,,
.1.3.6.1.2.1.10.166.1,MPLS-TC-STD-MIB::mplsTCStdMIB,,,,,,Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3811. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module defines TEXTUAL-CONVENTIONs for concepts used in Multiprotocol Label Switching (MPLS) networks.
.1.3.6.1.2.1.10.166.2,MPLS-LSR-STD-MIB::mplsLsrStdMIB,,,,,,This MIB module contains managed object definitions for the Multiprotocol Label Switching (MPLS) Router as defined in: Rosen, E., Viswanathan, A., and R. Callon, Multiprotocol Label Switching Architecture, RFC 3031, January 2001. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3812. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.10.166.2.0,MPLS-LSR-STD-MIB::mplsLsrNotifications,,,,,,
.1.3.6.1.2.1.10.166.2.0.1,MPLS-LSR-STD-MIB::mplsXCUp,,,,,,This notification is generated when the mplsXCOperStatus object for one or more contiguous entries in mplsXCTable are about to enter the up(1) state from some other state. The included values of mplsXCOperStatus MUST both be set equal to this new state (i.e: up(1)). The two instances of mplsXCOperStatus in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of cross-connects have transitioned into the up(1) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single cross-connect entry, then the instance identifier (and values) of the two mplsXCOperStatus objects MUST be the identical.
.1.3.6.1.2.1.10.166.2.0.2,MPLS-LSR-STD-MIB::mplsXCDown,,,,,,This notification is generated when the mplsXCOperStatus object for one or more contiguous entries in mplsXCTable are about to enter the down(2) state from some other state. The included values of mplsXCOperStatus MUST both be set equal to this down(2) state. The two instances of mplsXCOperStatus in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of cross-connects have transitioned into the down(2) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single cross-connect entry, then the instance identifier (and values) of the two mplsXCOperStatus objects MUST be identical.
.1.3.6.1.2.1.10.166.2.1,MPLS-LSR-STD-MIB::mplsLsrObjects,,,,,,
.1.3.6.1.2.1.10.166.2.1.1,MPLS-LSR-STD-MIB::mplsInterfaceTable,,not-accessible,,current,,This table specifies per-interface MPLS capability and associated information.
.1.3.6.1.2.1.10.166.2.1.1.1,MPLS-LSR-STD-MIB::mplsInterfaceEntry,,not-accessible,mplsInterfaceIndex,current,,A conceptual row in this table is created automatically by an LSR for every interface capable of supporting MPLS and which is configured to do so. A conceptual row in this table will exist if and only if a corresponding entry in ifTable exists with ifType = mpls(166). If this associated entry in ifTable is operationally disabled (thus removing MPLS capabilities on that interface), the corresponding entry in this table MUST be deleted shortly thereafter. An conceptual row with index 0 is created if the LSR supports per-platform labels. This conceptual row represents the per-platform label space and contains parameters that apply to all interfaces that participate in the per-platform label space. Other conceptual rows in this table represent MPLS interfaces that may participate in either the per-platform or per- interface label spaces, or both. Implementations that either only support per-platform labels, or have only them configured, may choose to return just the mplsInterfaceEntry of 0 and not return the other rows. This will greatly reduce the number of objects returned. Further information about label space participation of an interface is provided in the DESCRIPTION clause of mplsInterfaceLabelParticipationType.
.1.3.6.1.2.1.10.166.2.1.1.1.1,MPLS-LSR-STD-MIB::mplsInterfaceIndex,Integer32,not-accessible,,current,,This is a unique index for an entry in the MplsInterfaceTable. A non-zero index for an entry indicates the ifIndex for the corresponding interface entry of the MPLS-layer in the ifTable. The entry with index 0 represents the per-platform label space and contains parameters that apply to all interfaces that participate in the per-platform label space. Other entries defined in this table represent additional MPLS interfaces that may participate in either the per-platform or per-interface label spaces, or both.
.1.3.6.1.2.1.10.166.2.1.1.1.2,MPLS-LSR-STD-MIB::mplsInterfaceLabelMinIn,Unsigned32,read-only,,current,,This is the minimum value of an MPLS label that this LSR is willing to receive on this interface.
.1.3.6.1.2.1.10.166.2.1.1.1.3,MPLS-LSR-STD-MIB::mplsInterfaceLabelMaxIn,Unsigned32,read-only,,current,,This is the maximum value of an MPLS label that this LSR is willing to receive on this interface.
.1.3.6.1.2.1.10.166.2.1.1.1.4,MPLS-LSR-STD-MIB::mplsInterfaceLabelMinOut,Unsigned32,read-only,,current,,This is the minimum value of an MPLS label that this LSR is willing to send on this interface.
.1.3.6.1.2.1.10.166.2.1.1.1.5,MPLS-LSR-STD-MIB::mplsInterfaceLabelMaxOut,Unsigned32,read-only,,current,,This is the maximum value of an MPLS label that this LSR is willing to send on this interface.
.1.3.6.1.2.1.10.166.2.1.1.1.6,MPLS-LSR-STD-MIB::mplsInterfaceTotalBandwidth,Unsigned32,read-only,,current,,This value indicates the total amount of usable bandwidth on this interface and is specified in kilobits per second (Kbps). This variable is not applicable when applied to the interface with index 0. When this value cannot be measured, this value should contain the nominal bandwidth.
.1.3.6.1.2.1.10.166.2.1.1.1.7,MPLS-LSR-STD-MIB::mplsInterfaceAvailableBandwidth,Unsigned32,read-only,,current,,This value indicates the total amount of available bandwidth available on this interface and is specified in kilobits per second (Kbps). This value is calculated as the difference between the amount of bandwidth currently in use and that specified in mplsInterfaceTotalBandwidth. This variable is not applicable when applied to the interface with index 0. When this value cannot be measured, this value should contain the nominal bandwidth.
.1.3.6.1.2.1.10.166.2.1.1.1.8,MPLS-LSR-STD-MIB::mplsInterfaceLabelParticipationType,BITS,read-only,,current,perPlatform(0):perInterface(1),If the value of the mplsInterfaceIndex for this entry is zero, then this entry corresponds to the per-platform label space for all interfaces configured to use that label space. In this case the perPlatform(0) bit MUST be set; the perInterface(1) bit is meaningless and MUST be ignored. The remainder of this description applies to entries with a non-zero value of mplsInterfaceIndex. If the perInterface(1) bit is set then the value of mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, mplsInterfaceLabelMinOut, and mplsInterfaceLabelMaxOut for this entry reflect the label ranges for this interface. If only the perPlatform(0) bit is set, then the value of mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, mplsInterfaceLabelMinOut, and mplsInterfaceLabelMaxOut for this entry MUST be identical to the instance of these objects with index 0. These objects may only vary from the entry with index 0 if both the perPlatform(0) and perInterface(1) bits are set. In all cases, at a minimum one of the perPlatform(0) or perInterface(1) bits MUST be set to indicate that at least one label space is in use by this interface. In all cases, agents MUST ensure that label ranges are specified consistently and MUST return an inconsistentValue error when they do not.
.1.3.6.1.2.1.10.166.2.1.2,MPLS-LSR-STD-MIB::mplsInterfacePerfTable,,not-accessible,,current,,This table provides MPLS performance information on a per-interface basis.
.1.3.6.1.2.1.10.166.2.1.2.1,MPLS-LSR-STD-MIB::mplsInterfacePerfEntry,,not-accessible,,current,,An entry in this table is created by the LSR for every interface capable of supporting MPLS. Its is an extension to the mplsInterfaceEntry table. Note that the discontinuity behavior of entries in this table MUST be based on the corresponding ifEntry's ifDiscontinuityTime.
.1.3.6.1.2.1.10.166.2.1.2.1.1,MPLS-LSR-STD-MIB::mplsInterfacePerfInLabelsInUse,Gauge32,read-only,,current,,This object counts the number of labels that are in use at this point in time on this interface in the incoming direction. If the interface participates in only the per-platform label space, then the value of the instance of this object MUST be identical to the value of the instance with index 0. If the interface participates in the per-interface label space, then the instance of this object MUST represent the number of per-interface labels that are in use on this interface.
.1.3.6.1.2.1.10.166.2.1.2.1.2,MPLS-LSR-STD-MIB::mplsInterfacePerfInLabelLookupFailures,Counter32,read-only,,current,,This object counts the number of labeled packets that have been received on this interface and which were discarded because there was no matching cross- connect entry. This object MUST count on a per- interface basis regardless of which label space the interface participates in.
.1.3.6.1.2.1.10.166.2.1.2.1.3,MPLS-LSR-STD-MIB::mplsInterfacePerfOutLabelsInUse,Gauge32,read-only,,current,,This object counts the number of top-most labels in the outgoing label stacks that are in use at this point in time on this interface. This object MUST count on a per-interface basis regardless of which label space the interface participates in.
.1.3.6.1.2.1.10.166.2.1.2.1.4,MPLS-LSR-STD-MIB::mplsInterfacePerfOutFragmentedPkts,Counter32,read-only,,current,,This object counts the number of outgoing MPLS packets that required fragmentation before transmission on this interface. This object MUST count on a per-interface basis regardless of which label space the interface participates in.
.1.3.6.1.2.1.10.166.2.1.3,MPLS-LSR-STD-MIB::mplsInSegmentIndexNext,OCTET,read-only,,current,,This object contains the next available value to be used for mplsInSegmentIndex when creating entries in the mplsInSegmentTable. The special value of a string containing the single octet 0x00 indicates that no new entries can be created in this table. Agents not allowing managers to create entries in this table MUST set this object to this special value.
.1.3.6.1.2.1.10.166.2.1.4,MPLS-LSR-STD-MIB::mplsInSegmentTable,,not-accessible,,current,,This table contains a description of the incoming MPLS segments (labels) to an LSR and their associated parameters. The index for this table is mplsInSegmentIndex. The index structure of this table is specifically designed to handle many different MPLS implementations that manage their labels both in a distributed and centralized manner. The table is also designed to handle existing MPLS labels as defined in RFC3031 as well as longer ones that may be necessary in the future. In cases where the label cannot fit into the mplsInSegmentLabel object, the mplsInSegmentLabelPtr will indicate this by being set to the first accessible column in the appropriate extension table's row. In this case an additional table MUST be provided and MUST be indexed by at least the indexes used by this table. In all other cases when the label is represented within the mplsInSegmentLabel object, the mplsInSegmentLabelPtr MUST be set to 0.0. Due to the fact that MPLS labels may not exceed 24 bits, the mplsInSegmentLabelPtr object is only a provision for future-proofing the MIB module. Thus, the definition of any extension tables is beyond the scope of this MIB module.
.1.3.6.1.2.1.10.166.2.1.4.1,MPLS-LSR-STD-MIB::mplsInSegmentEntry,,not-accessible,mplsInSegmentIndex,current,,An entry in this table represents one incoming segment as is represented in an LSR's LFIB. An entry can be created by a network administrator or an SNMP agent, or an MPLS signaling protocol. The creator of the entry is denoted by mplsInSegmentOwner. The value of mplsInSegmentRowStatus cannot be active(1) unless the ifTable entry corresponding to mplsInSegmentInterface exists. An entry in this table must match any incoming packets, and indicates an instance of mplsXCEntry based on which forwarding and/or switching actions are taken.
.1.3.6.1.2.1.10.166.2.1.4.1.1,MPLS-LSR-STD-MIB::mplsInSegmentIndex,OCTET,not-accessible,,current,,The index for this in-segment. The string containing the single octet 0x00 MUST not be used as an index.
.1.3.6.1.2.1.10.166.2.1.4.1.2,MPLS-LSR-STD-MIB::mplsInSegmentInterface,Integer32,read-create,,current,,This object represents the interface index for the incoming MPLS interface. A value of zero represents all interfaces participating in the per-platform label space. This may only be used in cases where the incoming interface and label are associated with the same mplsXCEntry. Specifically, given a label and any incoming interface pair from the per-platform label space, the outgoing label/interface mapping remains the same. If this is not the case, then individual entries MUST exist that can then be mapped to unique mplsXCEntries.
.1.3.6.1.2.1.10.166.2.1.4.1.3,MPLS-LSR-STD-MIB::mplsInSegmentLabel,Unsigned32,read-create,,current,,If the corresponding instance of mplsInSegmentLabelPtr is zeroDotZero then this object MUST contain the incoming label associated with this in-segment. If not this object SHOULD be zero and MUST be ignored.
.1.3.6.1.2.1.10.166.2.1.4.1.4,MPLS-LSR-STD-MIB::mplsInSegmentLabelPtr,OBJECT,read-create,,current,,If the label for this segment cannot be represented fully within the mplsInSegmentLabel object, this object MUST point to the first accessible column of a conceptual row in an external table containing the label. In this case, the mplsInSegmentTopLabel object SHOULD be set to 0 and ignored. This object MUST be set to zeroDotZero otherwise.
.1.3.6.1.2.1.10.166.2.1.4.1.5,MPLS-LSR-STD-MIB::mplsInSegmentNPop,Integer32,read-create,,current,,The number of labels to pop from the incoming packet. Normally only the top label is popped from the packet and used for all switching decisions for that packet. This is indicated by setting this object to the default value of 1. If an LSR supports popping of more than one label, this object MUST be set to that number. This object cannot be modified if mplsInSegmentRowStatus is active(1).
.1.3.6.1.2.1.10.166.2.1.4.1.6,MPLS-LSR-STD-MIB::mplsInSegmentAddrFamily,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The IANA address family [IANAFamily] of packets received on this segment, which is used at an egress LSR to deliver them to the appropriate layer 3 entity. A value of other(0) indicates that the family type is either unknown or undefined; this SHOULD NOT be used at an egress LSR. This object cannot be modified if mplsInSegmentRowStatus is active(1).
.1.3.6.1.2.1.10.166.2.1.4.1.7,MPLS-LSR-STD-MIB::mplsInSegmentXCIndex,OCTET,read-only,,current,,Index into mplsXCTable which identifies which cross- connect entry this segment is part of. The string containing the single octet 0x00 indicates that this entry is not referred to by any cross-connect entry. When a cross-connect entry is created which this in-segment is a part of, this object is automatically updated to reflect the value of mplsXCIndex of that cross-connect entry.
.1.3.6.1.2.1.10.166.2.1.4.1.8,MPLS-LSR-STD-MIB::mplsInSegmentOwner,INTEGER,read-only,,current,unknown(1):other(2):snmp(3):ldp(4):crldp(5):rsvpTe(6):policyAgent(7),Denotes the entity that created and is responsible for managing this segment.
.1.3.6.1.2.1.10.166.2.1.4.1.9,MPLS-LSR-STD-MIB::mplsInSegmentTrafficParamPtr,OBJECT,read-create,,current,,This variable represents a pointer to the traffic parameter specification for this in-segment. This value may point at an entry in the mplsTunnelResourceTable in the MPLS-TE-STD-MIB (RFC3812) to indicate which traffic parameter settings for this segment if it represents an LSP used for a TE tunnel. This value may optionally point at an externally defined traffic parameter specification table. A value of zeroDotZero indicates best-effort treatment. By having the same value of this object, two or more segments can indicate resource sharing of such things as LSP queue space, etc. This object cannot be modified if mplsInSegmentRowStatus is active(1). For entries in this table that are preserved after a re-boot, the agent MUST ensure that their integrity be preserved, or this object should be set to 0.0 if it cannot.
.1.3.6.1.2.1.10.166.2.1.4.1.10,MPLS-LSR-STD-MIB::mplsInSegmentRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the mplsInSegmentRowStatus and mplsInSegmentStorageType.
.1.3.6.1.2.1.10.166.2.1.4.1.11,MPLS-LSR-STD-MIB::mplsInSegmentStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. The agent MUST ensure that this object's value remains consistent with the associated mplsXCEntry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.2.1.5,MPLS-LSR-STD-MIB::mplsInSegmentPerfTable,,not-accessible,,current,,This table contains statistical information for incoming MPLS segments to an LSR.
.1.3.6.1.2.1.10.166.2.1.5.1,MPLS-LSR-STD-MIB::mplsInSegmentPerfEntry,,not-accessible,,current,,An entry in this table contains statistical information about one incoming segment which is configured in the mplsInSegmentTable. The counters in this entry should behave in a manner similar to that of the interface. mplsInSegmentPerfDiscontinuityTime indicates the time of the last discontinuity in all of these objects.
.1.3.6.1.2.1.10.166.2.1.5.1.1,MPLS-LSR-STD-MIB::mplsInSegmentPerfOctets,Counter32,read-only,,current,,This value represents the total number of octets received by this segment. It MUST be equal to the least significant 32 bits of mplsInSegmentPerfHCOctets if mplsInSegmentPerfHCOctets is supported according to the rules spelled out in RFC2863.
.1.3.6.1.2.1.10.166.2.1.5.1.2,MPLS-LSR-STD-MIB::mplsInSegmentPerfPackets,Counter32,read-only,,current,,Total number of packets received by this segment.
.1.3.6.1.2.1.10.166.2.1.5.1.3,MPLS-LSR-STD-MIB::mplsInSegmentPerfErrors,Counter32,read-only,,current,,The number of errored packets received on this segment.
.1.3.6.1.2.1.10.166.2.1.5.1.4,MPLS-LSR-STD-MIB::mplsInSegmentPerfDiscards,Counter32,read-only,,current,,The number of labeled packets received on this in- segment, which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a labeled packet could be to free up buffer space.
.1.3.6.1.2.1.10.166.2.1.5.1.5,MPLS-LSR-STD-MIB::mplsInSegmentPerfHCOctets,Counter64,read-only,,current,,The total number of octets received. This is the 64 bit version of mplsInSegmentPerfOctets, if mplsInSegmentPerfHCOctets is supported according to the rules spelled out in RFC2863.
.1.3.6.1.2.1.10.166.2.1.5.1.6,MPLS-LSR-STD-MIB::mplsInSegmentPerfDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this segment's Counter32 or Counter64 suffered a discontinuity. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.2.1.6,MPLS-LSR-STD-MIB::mplsOutSegmentIndexNext,OCTET,read-only,,current,,This object contains the next available value to be used for mplsOutSegmentIndex when creating entries in the mplsOutSegmentTable. The special value of a string containing the single octet 0x00 indicates that no new entries can be created in this table. Agents not allowing managers to create entries in this table MUST set this object to this special value.
.1.3.6.1.2.1.10.166.2.1.7,MPLS-LSR-STD-MIB::mplsOutSegmentTable,,not-accessible,,current,,This table contains a representation of the outgoing segments from an LSR.
.1.3.6.1.2.1.10.166.2.1.7.1,MPLS-LSR-STD-MIB::mplsOutSegmentEntry,,not-accessible,mplsOutSegmentIndex,current,,An entry in this table represents one outgoing segment. An entry can be created by a network administrator, an SNMP agent, or an MPLS signaling protocol. The object mplsOutSegmentOwner indicates the creator of this entry. The value of mplsOutSegmentRowStatus cannot be active(1) unless the ifTable entry corresponding to mplsOutSegmentInterface exists. Note that the indexing of this table uses a single, arbitrary index (mplsOutSegmentIndex) to indicate which out-segment (i.e.: label) is being switched to from which in-segment (i.e: label) or in-segments. This is necessary because it is possible to have an equal-cost multi-path situation where two identical out-going labels are assigned to the same cross-connect (i.e.: they go to two different neighboring LSRs); thus, requiring two out-segments. In order to preserve the uniqueness of the references by the mplsXCEntry, an arbitrary integer must be used as the index for this table.
.1.3.6.1.2.1.10.166.2.1.7.1.1,MPLS-LSR-STD-MIB::mplsOutSegmentIndex,OCTET,not-accessible,,current,,This value contains a unique index for this row. While a value of a string containing the single octet 0x00 is not valid as an index for entries in this table, it can be supplied as a valid value to index the mplsXCTable to represent entries for which no out-segment has been configured or exists.
.1.3.6.1.2.1.10.166.2.1.7.1.2,MPLS-LSR-STD-MIB::mplsOutSegmentInterface,Integer32,read-create,,current,,This value must contain the interface index of the outgoing interface. This object cannot be modified if mplsOutSegmentRowStatus is active(1). The mplsOutSegmentRowStatus cannot be set to active(1) until this object is set to a value corresponding to a valid ifEntry.
.1.3.6.1.2.1.10.166.2.1.7.1.3,MPLS-LSR-STD-MIB::mplsOutSegmentPushTopLabel,INTEGER,read-create,,current,true(1):false(2),This value indicates whether or not a top label should be pushed onto the outgoing packet's label stack. The value of this variable MUST be set to true(1) if the outgoing interface does not support pop-and-go (and no label stack remains). For example, on ATM interface, or if the segment represents a tunnel origination. Note that it is considered an error in the case that mplsOutSegmentPushTopLabel is set to false, but the cross-connect entry which refers to this out-segment has a non-zero mplsLabelStackIndex. The LSR MUST ensure that this situation does not happen. This object cannot be modified if mplsOutSegmentRowStatus is active(1).
.1.3.6.1.2.1.10.166.2.1.7.1.4,MPLS-LSR-STD-MIB::mplsOutSegmentTopLabel,Unsigned32,read-create,,current,,If mplsOutSegmentPushTopLabel is true then this represents the label that should be pushed onto the top of the outgoing packet's label stack. Otherwise this value SHOULD be set to 0 by the management station and MUST be ignored by the agent. This object cannot be modified if mplsOutSegmentRowStatus is active(1).
.1.3.6.1.2.1.10.166.2.1.7.1.5,MPLS-LSR-STD-MIB::mplsOutSegmentTopLabelPtr,OBJECT,read-create,,current,,If the label for this segment cannot be represented fully within the mplsOutSegmentLabel object, this object MUST point to the first accessible column of a conceptual row in an external table containing the label. In this case, the mplsOutSegmentTopLabel object SHOULD be set to 0 and ignored. This object MUST be set to zeroDotZero otherwise.
.1.3.6.1.2.1.10.166.2.1.7.1.6,MPLS-LSR-STD-MIB::mplsOutSegmentNextHopAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Indicates the next hop Internet address type. Only values unknown(0), ipv4(1) or ipv6(2) have to be supported. A value of unknown(0) is allowed only when the outgoing interface is of type point-to-point. If any other unsupported values are attempted in a set operation, the agent MUST return an inconsistentValue error.
.1.3.6.1.2.1.10.166.2.1.7.1.7,MPLS-LSR-STD-MIB::mplsOutSegmentNextHopAddr,OCTET,read-create,,current,,The internet address of the next hop. The type of this address is determined by the value of the mplslOutSegmentNextHopAddrType object. This object cannot be modified if mplsOutSegmentRowStatus is active(1).
.1.3.6.1.2.1.10.166.2.1.7.1.8,MPLS-LSR-STD-MIB::mplsOutSegmentXCIndex,OCTET,read-only,,current,,Index into mplsXCTable which identifies which cross- connect entry this segment is part of. A value of the string containing the single octet 0x00 indicates that this entry is not referred to by any cross-connect entry. When a cross-connect entry is created which this out-segment is a part of, this object MUST be updated by the agent to reflect the value of mplsXCIndex of that cross-connect entry.
.1.3.6.1.2.1.10.166.2.1.7.1.9,MPLS-LSR-STD-MIB::mplsOutSegmentOwner,INTEGER,read-only,,current,unknown(1):other(2):snmp(3):ldp(4):crldp(5):rsvpTe(6):policyAgent(7),Denotes the entity which created and is responsible for managing this segment.
.1.3.6.1.2.1.10.166.2.1.7.1.10,MPLS-LSR-STD-MIB::mplsOutSegmentTrafficParamPtr,OBJECT,read-create,,current,,This variable represents a pointer to the traffic parameter specification for this out-segment. This value may point at an entry in the MplsTunnelResourceEntry in the MPLS-TE-STD-MIB (RFC3812) RFC Editor: Please fill in RFC number. to indicate which traffic parameter settings for this segment if it represents an LSP used for a TE tunnel. This value may optionally point at an externally defined traffic parameter specification table. A value of zeroDotZero indicates best-effort treatment. By having the same value of this object, two or more segments can indicate resource sharing of such things as LSP queue space, etc. This object cannot be modified if mplsOutSegmentRowStatus is active(1). For entries in this table that are preserved after a re-boot, the agent MUST ensure that their integrity be preserved, or this object should be set to 0.0 if it cannot.
.1.3.6.1.2.1.10.166.2.1.7.1.11,MPLS-LSR-STD-MIB::mplsOutSegmentRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the mplsOutSegmentRowStatus or mplsOutSegmentStorageType.
.1.3.6.1.2.1.10.166.2.1.7.1.12,MPLS-LSR-STD-MIB::mplsOutSegmentStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. The agent MUST ensure that this object's value remains consistent with the associated mplsXCEntry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.2.1.8,MPLS-LSR-STD-MIB::mplsOutSegmentPerfTable,,not-accessible,,current,,This table contains statistical information about outgoing segments from an LSR. The counters in this entry should behave in a manner similar to that of the interface.
.1.3.6.1.2.1.10.166.2.1.8.1,MPLS-LSR-STD-MIB::mplsOutSegmentPerfEntry,,not-accessible,,current,,An entry in this table contains statistical information about one outgoing segment configured in mplsOutSegmentTable. The object mplsOutSegmentPerfDiscontinuityTime indicates the time of the last discontinuity in these objects. 
.1.3.6.1.2.1.10.166.2.1.8.1.1,MPLS-LSR-STD-MIB::mplsOutSegmentPerfOctets,Counter32,read-only,,current,,This value contains the total number of octets sent on this segment. It MUST be equal to the least significant 32 bits of mplsOutSegmentPerfHCOctets if mplsOutSegmentPerfHCOctets is supported according to the rules spelled out in RFC2863.
.1.3.6.1.2.1.10.166.2.1.8.1.2,MPLS-LSR-STD-MIB::mplsOutSegmentPerfPackets,Counter32,read-only,,current,,This value contains the total number of packets sent on this segment.
.1.3.6.1.2.1.10.166.2.1.8.1.3,MPLS-LSR-STD-MIB::mplsOutSegmentPerfErrors,Counter32,read-only,,current,,Number of packets that could not be sent due to errors on this segment.
.1.3.6.1.2.1.10.166.2.1.8.1.4,MPLS-LSR-STD-MIB::mplsOutSegmentPerfDiscards,Counter32,read-only,,current,,The number of labeled packets attempted to be transmitted on this out-segment, which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a labeled packet could be to free up buffer space.
.1.3.6.1.2.1.10.166.2.1.8.1.5,MPLS-LSR-STD-MIB::mplsOutSegmentPerfHCOctets,Counter64,read-only,,current,,Total number of octets sent. This is the 64 bit version of mplsOutSegmentPerfOctets, if mplsOutSegmentPerfHCOctets is supported according to the rules spelled out in RFC2863.
.1.3.6.1.2.1.10.166.2.1.8.1.6,MPLS-LSR-STD-MIB::mplsOutSegmentPerfDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this segment's Counter32 or Counter64 suffered a discontinuity. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.2.1.9,MPLS-LSR-STD-MIB::mplsXCIndexNext,OCTET,read-only,,current,,This object contains the next available value to be used for mplsXCIndex when creating entries in the mplsXCTable. A special value of the zero length string indicates that no more new entries can be created in the relevant table. Agents not allowing managers to create entries in this table MUST set this value to the zero length string.
.1.3.6.1.2.1.10.166.2.1.10,MPLS-LSR-STD-MIB::mplsXCTable,,not-accessible,,current,,This table specifies information for switching between LSP segments. It supports point-to-point, point-to-multipoint and multipoint-to-point connections. mplsLabelStackTable specifies the label stack information for a cross-connect LSR and is referred to from mplsXCTable.
.1.3.6.1.2.1.10.166.2.1.10.1,MPLS-LSR-STD-MIB::mplsXCEntry,,not-accessible,mplsXCIndex:mplsXCInSegmentIndex:mplsXCOutSegmentIndex,current,,A row in this table represents one cross-connect entry. It is indexed by the following objects: - cross-connect index mplsXCIndex that uniquely identifies a group of cross-connect entries - in-segment index, mplsXCInSegmentIndex - out-segment index, mplsXCOutSegmentIndex LSPs originating at this LSR: These are represented by using the special of value of mplsXCInSegmentIndex set to the string containing a single octet 0x00. In this case the mplsXCOutSegmentIndex MUST not be the string containing a single octet 0x00. LSPs terminating at this LSR: These are represented by using the special value mplsXCOutSegmentIndex set to the string containing a single octet 0x00. Special labels: Entries indexed by the strings containing the reserved MPLS label values as a single octet 0x00 through 0x0f (inclusive) imply LSPs terminating at this LSR. Note that situations where LSPs are terminated with incoming label equal to the string containing a single octet 0x00 can be distinguished from LSPs originating at this LSR because the mplsXCOutSegmentIndex equals the string containing the single octet 0x00. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS signaling protocol.
.1.3.6.1.2.1.10.166.2.1.10.1.1,MPLS-LSR-STD-MIB::mplsXCIndex,OCTET,not-accessible,,current,,Primary index for the conceptual row identifying a group of cross-connect segments. The string containing a single octet 0x00 is an invalid index.
.1.3.6.1.2.1.10.166.2.1.10.1.2,MPLS-LSR-STD-MIB::mplsXCInSegmentIndex,OCTET,not-accessible,,current,,Incoming label index. If this object is set to the string containing a single octet 0x00, this indicates a special case outlined in the table's description above. In this case no corresponding mplsInSegmentEntry shall exist.
.1.3.6.1.2.1.10.166.2.1.10.1.3,MPLS-LSR-STD-MIB::mplsXCOutSegmentIndex,OCTET,not-accessible,,current,,Index of out-segment for LSPs not terminating on this LSR if not set to the string containing the single octet 0x00. If the segment identified by this entry is terminating, then this object MUST be set to the string containing a single octet 0x00 to indicate that no corresponding mplsOutSegmentEntry shall exist.
.1.3.6.1.2.1.10.166.2.1.10.1.4,MPLS-LSR-STD-MIB::mplsXCLspId,OCTET,read-create,,current,,This value identifies the label switched path that this cross-connect entry belongs to. This object cannot be modified if mplsXCRowStatus is active(1) except for this object.
.1.3.6.1.2.1.10.166.2.1.10.1.5,MPLS-LSR-STD-MIB::mplsXCLabelStackIndex,OCTET,read-create,,current,,Primary index into mplsLabelStackTable identifying a stack of labels to be pushed beneath the top label. Note that the top label identified by the out- segment ensures that all the components of a multipoint-to-point connection have the same outgoing label. A value of the string containing the single octet 0x00 indicates that no labels are to be stacked beneath the top label. This object cannot be modified if mplsXCRowStatus is active(1).
.1.3.6.1.2.1.10.166.2.1.10.1.6,MPLS-LSR-STD-MIB::mplsXCOwner,INTEGER,read-only,,current,unknown(1):other(2):snmp(3):ldp(4):crldp(5):rsvpTe(6):policyAgent(7),Denotes the entity that created and is responsible for managing this cross-connect.
.1.3.6.1.2.1.10.166.2.1.10.1.7,MPLS-LSR-STD-MIB::mplsXCRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. When a row in this table has a row in the active(1) state, no objects in this row except this object and the mplsXCStorageType can be modified. 
.1.3.6.1.2.1.10.166.2.1.10.1.8,MPLS-LSR-STD-MIB::mplsXCStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. The agent MUST ensure that the associated in and out segments also have the same StorageType value and are restored consistently upon system restart. This value SHOULD be set to permanent(4) if created as a result of a static LSP configuration. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.2.1.10.1.9,MPLS-LSR-STD-MIB::mplsXCAdminStatus,INTEGER,read-create,,current,up(1):down(2):testing(3),The desired operational status of this segment.
.1.3.6.1.2.1.10.166.2.1.10.1.10,MPLS-LSR-STD-MIB::mplsXCOperStatus,INTEGER,read-only,,current,up(1):down(2):testing(3):unknown(4):dormant(5):notPresent(6):lowerLayerDown(7),The actual operational status of this cross- connect.
.1.3.6.1.2.1.10.166.2.1.11,MPLS-LSR-STD-MIB::mplsMaxLabelStackDepth,Unsigned32,read-only,,current,,The maximum stack depth supported by this LSR.
.1.3.6.1.2.1.10.166.2.1.12,MPLS-LSR-STD-MIB::mplsLabelStackIndexNext,OCTET,read-only,,current,,This object contains the next available value to be used for mplsLabelStackIndex when creating entries in the mplsLabelStackTable. The special string containing the single octet 0x00 indicates that no more new entries can be created in the relevant table. Agents not allowing managers to create entries in this table MUST set this value to the string containing the single octet 0x00.
.1.3.6.1.2.1.10.166.2.1.13,MPLS-LSR-STD-MIB::mplsLabelStackTable,,not-accessible,,current,,This table specifies the label stack to be pushed onto a packet, beneath the top label. Entries into this table are referred to from mplsXCTable.
.1.3.6.1.2.1.10.166.2.1.13.1,MPLS-LSR-STD-MIB::mplsLabelStackEntry,,not-accessible,mplsLabelStackIndex:mplsLabelStackLabelIndex,current,,An entry in this table represents one label which is to be pushed onto an outgoing packet, beneath the top label. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS signaling protocol.
.1.3.6.1.2.1.10.166.2.1.13.1.1,MPLS-LSR-STD-MIB::mplsLabelStackIndex,OCTET,not-accessible,,current,,Primary index for this row identifying a stack of labels to be pushed on an outgoing packet, beneath the top label. An index containing the string with a single octet 0x00 MUST not be used.
.1.3.6.1.2.1.10.166.2.1.13.1.2,MPLS-LSR-STD-MIB::mplsLabelStackLabelIndex,Unsigned32,not-accessible,,current,,Secondary index for this row identifying one label of the stack. Note that an entry with a smaller mplsLabelStackLabelIndex would refer to a label higher up the label stack and would be popped at a downstream LSR before a label represented by a higher mplsLabelStackLabelIndex at a downstream LSR.
.1.3.6.1.2.1.10.166.2.1.13.1.3,MPLS-LSR-STD-MIB::mplsLabelStackLabel,Unsigned32,read-create,,current,,The label to pushed.
.1.3.6.1.2.1.10.166.2.1.13.1.4,MPLS-LSR-STD-MIB::mplsLabelStackLabelPtr,OBJECT,read-create,,current,,If the label for this segment cannot be represented fully within the mplsLabelStackLabel object, this object MUST point to the first accessible column of a conceptual row in an external table containing the label. In this case, the mplsLabelStackLabel object SHOULD be set to 0 and ignored. This object MUST be set to zeroDotZero otherwise.
.1.3.6.1.2.1.10.166.2.1.13.1.5,MPLS-LSR-STD-MIB::mplsLabelStackRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. When a row in this table has a row in the active(1) state, no objects in this row except this object and the mplsLabelStackStorageType can be modified.
.1.3.6.1.2.1.10.166.2.1.13.1.6,MPLS-LSR-STD-MIB::mplsLabelStackStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. This object cannot be modified if mplsLabelStackRowStatus is active(1). No objects are required to be writable for rows in this table with this object set to permanent(4). The agent MUST ensure that all related entries in this table retain the same value for this object. Agents MUST ensure that the storage type for all entries related to a particular mplsXCEntry retain the same value for this object as the mplsXCEntry's StorageType.
.1.3.6.1.2.1.10.166.2.1.14,MPLS-LSR-STD-MIB::mplsInSegmentMapTable,,not-accessible,,current,,This table specifies the mapping from the mplsInSegmentIndex to the corresponding mplsInSegmentInterface and mplsInSegmentLabel objects. The purpose of this table is to provide the manager with an alternative means by which to locate in-segments.
.1.3.6.1.2.1.10.166.2.1.14.1,MPLS-LSR-STD-MIB::mplsInSegmentMapEntry,,not-accessible,mplsInSegmentMapInterface:mplsInSegmentMapLabel:mplsInSegmentMapLabelPtrIndex,current,,An entry in this table represents one interface and incoming label pair. In cases where the label cannot fit into the mplsInSegmentLabel object, the mplsInSegmentLabelPtr will indicate this by being set to the first accessible column in the appropriate extension table's row, and the mplsInSegmentLabel SHOULD be set to 0. In all other cases when the label is represented within the mplsInSegmentLabel object, the mplsInSegmentLabelPtr MUST be 0.0. Implementors need to be aware that if the value of the mplsInSegmentMapLabelPtrIndex (an OID) has more that 111 sub-identifiers, then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.10.166.2.1.14.1.1,MPLS-LSR-STD-MIB::mplsInSegmentMapInterface,Integer32,not-accessible,,current,,This index contains the same value as the mplsInSegmentIndex in the mplsInSegmentTable.
.1.3.6.1.2.1.10.166.2.1.14.1.2,MPLS-LSR-STD-MIB::mplsInSegmentMapLabel,Unsigned32,not-accessible,,current,,This index contains the same value as the mplsInSegmentLabel in the mplsInSegmentTable.
.1.3.6.1.2.1.10.166.2.1.14.1.3,MPLS-LSR-STD-MIB::mplsInSegmentMapLabelPtrIndex,OBJECT,not-accessible,,current,,This index contains the same value as the mplsInSegmentLabelPtr. If the label for the InSegment cannot be represented fully within the mplsInSegmentLabel object, this index MUST point to the first accessible column of a conceptual row in an external table containing the label. In this case, the mplsInSegmentTopLabel object SHOULD be set to 0 and ignored. This object MUST be set to zeroDotZero otherwise.
.1.3.6.1.2.1.10.166.2.1.14.1.4,MPLS-LSR-STD-MIB::mplsInSegmentMapIndex,OCTET,read-only,,current,,The mplsInSegmentIndex that corresponds to the mplsInSegmentInterface and mplsInSegmentLabel, or the mplsInSegmentInterface and mplsInSegmentLabelPtr, if applicable. The string containing the single octet 0x00 MUST not be returned.
.1.3.6.1.2.1.10.166.2.1.15,MPLS-LSR-STD-MIB::mplsXCNotificationsEnable,INTEGER,read-write,,current,true(1):false(2),If this object is set to true(1), then it enables the emission of mplsXCUp and mplsXCDown notifications; otherwise these notifications are not emitted.
.1.3.6.1.2.1.10.166.2.2,MPLS-LSR-STD-MIB::mplsLsrConformance,,,,,,
.1.3.6.1.2.1.10.166.2.2.1,MPLS-LSR-STD-MIB::mplsLsrGroups,,,,,,
.1.3.6.1.2.1.10.166.2.2.1.1,MPLS-LSR-STD-MIB::mplsInterfaceGroup,,,,,,Collection of objects needed for MPLS interface and interface performance information.
.1.3.6.1.2.1.10.166.2.2.1.2,MPLS-LSR-STD-MIB::mplsInSegmentGroup,,,,,,Collection of objects needed to implement an in- segment.
.1.3.6.1.2.1.10.166.2.2.1.3,MPLS-LSR-STD-MIB::mplsOutSegmentGroup,,,,,,Collection of objects needed to implement an out- segment.
.1.3.6.1.2.1.10.166.2.2.1.4,MPLS-LSR-STD-MIB::mplsXCGroup,,,,,,Collection of objects needed to implement a cross-connect entry.
.1.3.6.1.2.1.10.166.2.2.1.5,MPLS-LSR-STD-MIB::mplsPerfGroup,,,,,,Collection of objects providing performance information about an LSR.
.1.3.6.1.2.1.10.166.2.2.1.6,MPLS-LSR-STD-MIB::mplsHCInSegmentPerfGroup,,,,,,Object(s) providing performance information specific to out-segments for which the object mplsInterfaceInOctets wraps around too quickly.
.1.3.6.1.2.1.10.166.2.2.1.7,MPLS-LSR-STD-MIB::mplsHCOutSegmentPerfGroup,,,,,,Object(s) providing performance information specific to out-segments for which the object mplsInterfaceOutOctets wraps around too quickly.
.1.3.6.1.2.1.10.166.2.2.1.8,MPLS-LSR-STD-MIB::mplsLabelStackGroup,,,,,,Objects needed to support label stacking.
.1.3.6.1.2.1.10.166.2.2.1.9,MPLS-LSR-STD-MIB::mplsLsrNotificationGroup,,,,,,Set of notifications implemented in this module.
.1.3.6.1.2.1.10.166.2.2.2,MPLS-LSR-STD-MIB::mplsLsrCompliances,,,,,,
.1.3.6.1.2.1.10.166.2.2.2.1,MPLS-LSR-STD-MIB::mplsLsrModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for MPLS-LSR-STD-MIB. Such devices can then be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.10.166.2.2.2.2,MPLS-LSR-STD-MIB::mplsLsrModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-LSR-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module. 
.1.3.6.1.2.1.10.166.3,MPLS-TE-STD-MIB::mplsTeStdMIB,,,,,,Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3812. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module contains managed object definitions for MPLS Traffic Engineering (TE) as defined in: 1. Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001 2. Constraint-Based LSP Setup using LDP, Jamoussi (Editor), RFC 3212, January 2002 3. Requirements for Traffic Engineering Over MPLS, Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. McManus, [RFC2702], September 1999
.1.3.6.1.2.1.10.166.3.0,MPLS-TE-STD-MIB::mplsTeNotifications,,,,,,
.1.3.6.1.2.1.10.166.3.0.1,MPLS-TE-STD-MIB::mplsTunnelUp,,,,,,This notification is generated when a mplsTunnelOperStatus object for one of the configured tunnels is about to leave the down state and transition into some other state (but not into the notPresent state). This other state is indicated by the included value of mplsTunnelOperStatus.
.1.3.6.1.2.1.10.166.3.0.2,MPLS-TE-STD-MIB::mplsTunnelDown,,,,,,This notification is generated when a mplsTunnelOperStatus object for one of the configured tunnels is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of mplsTunnelOperStatus.
.1.3.6.1.2.1.10.166.3.0.3,MPLS-TE-STD-MIB::mplsTunnelRerouted,,,,,,This notification is generated when a tunnel is rerouted. If the mplsTunnelARHopTable is used, then this tunnel instance's entry in the mplsTunnelARHopTable MAY contain the new path for this tunnel some time after this trap is issued by the agent.
.1.3.6.1.2.1.10.166.3.0.4,MPLS-TE-STD-MIB::mplsTunnelReoptimized,,,,,,This notification is generated when a tunnel is reoptimized. If the mplsTunnelARHopTable is used, then this tunnel instance's entry in the mplsTunnelARHopTable MAY contain the new path for this tunnel some time after this trap is issued by the agent.
.1.3.6.1.2.1.10.166.3.1,MPLS-TE-STD-MIB::mplsTeScalars,,,,,,
.1.3.6.1.2.1.10.166.3.1.1,MPLS-TE-STD-MIB::mplsTunnelConfigured,Unsigned32,read-only,,current,,The number of tunnels configured on this device. A tunnel is considered configured if the mplsTunnelRowStatus is active(1).
.1.3.6.1.2.1.10.166.3.1.2,MPLS-TE-STD-MIB::mplsTunnelActive,Unsigned32,read-only,,current,,The number of tunnels active on this device. A tunnel is considered active if the mplsTunnelOperStatus is up(1).
.1.3.6.1.2.1.10.166.3.1.3,MPLS-TE-STD-MIB::mplsTunnelTEDistProto,BITS,read-only,,current,other(0):ospf(1):isis(2),The traffic engineering distribution protocol(s) used by this LSR. Note that an LSR may support more than one distribution protocol simultaneously.
.1.3.6.1.2.1.10.166.3.1.4,MPLS-TE-STD-MIB::mplsTunnelMaxHops,Unsigned32,read-only,,current,,The maximum number of hops that can be specified for a tunnel on this device.
.1.3.6.1.2.1.10.166.3.1.5,MPLS-TE-STD-MIB::mplsTunnelNotificationMaxRate,Unsigned32,read-write,,current,,This variable indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period, or may queue them until an appropriate time. A value of 0 means no throttling is applied and events may be notified at the rate at which they occur.
.1.3.6.1.2.1.10.166.3.2,MPLS-TE-STD-MIB::mplsTeObjects,,,,,,
.1.3.6.1.2.1.10.166.3.2.1,MPLS-TE-STD-MIB::mplsTunnelIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for mplsTunnelIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsTunnelIndex. Note that this object offers an unused value for an mplsTunnelIndex value at the ingress side of a tunnel. At other LSRs the value of mplsTunnelIndex SHOULD be taken from the value signaled by the MPLS signaling protocol. 
.1.3.6.1.2.1.10.166.3.2.2,MPLS-TE-STD-MIB::mplsTunnelTable,,not-accessible,,current,,The mplsTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multipoint-to-point and point- to-multipoint connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR.
.1.3.6.1.2.1.10.166.3.2.2.1,MPLS-TE-STD-MIB::mplsTunnelEntry,,not-accessible,mplsTunnelIndex:mplsTunnelInstance:mplsTunnelIngressLSRId:mplsTunnelEgressLSRId,current,,An entry in this table represents an MPLS tunnel. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS signalling protocol. Whenever a new entry is created with mplsTunnelIsIf set to true(1), then a corresponding entry is created in ifTable as well (see RFC 2863). The ifType of this entry is mplsTunnel(150). A tunnel entry needs to be uniquely identified across a MPLS network. Indices mplsTunnelIndex and mplsTunnelInstance uniquely identify a tunnel on the LSR originating the tunnel. To uniquely identify a tunnel across an MPLS network requires index mplsTunnelIngressLSRId. The last index mplsTunnelEgressLSRId is useful in identifying all instances of a tunnel that terminate on the same egress LSR.
.1.3.6.1.2.1.10.166.3.2.2.1.1,MPLS-TE-STD-MIB::mplsTunnelIndex,Unsigned32,not-accessible,,current,,Uniquely identifies a set of tunnel instances between a pair of ingress and egress LSRs. Managers should obtain new values for row creation in this table by reading mplsTunnelIndexNext. When the MPLS signalling protocol is rsvp(2) this value SHOULD be equal to the value signaled in the Tunnel Id of the Session object. When the MPLS signalling protocol is crldp(3) this value SHOULD be equal to the value signaled in the LSP ID.
.1.3.6.1.2.1.10.166.3.2.2.1.2,MPLS-TE-STD-MIB::mplsTunnelInstance,Unsigned32,not-accessible,,current,,Uniquely identifies a particular instance of a tunnel between a pair of ingress and egress LSRs. It is useful to identify multiple instances of tunnels for the purposes of backup and parallel tunnels. When the MPLS signaling protocol is rsvp(2) this value SHOULD be equal to the LSP Id of the Sender Template object. When the signaling protocol is crldp(3) there is no equivalent signaling object.
.1.3.6.1.2.1.10.166.3.2.2.1.3,MPLS-TE-STD-MIB::mplsTunnelIngressLSRId,Unsigned32,not-accessible,,current,,Identity of the ingress LSR associated with this tunnel instance. When the MPLS signalling protocol is rsvp(2) this value SHOULD be equal to the Tunnel Sender Address in the Sender Template object and MAY be equal to the Extended Tunnel Id field in the SESSION object. When the MPLS signalling protocol is crldp(3) this value SHOULD be equal to the Ingress LSR Router ID field in the LSPID TLV object.
.1.3.6.1.2.1.10.166.3.2.2.1.4,MPLS-TE-STD-MIB::mplsTunnelEgressLSRId,Unsigned32,not-accessible,,current,,Identity of the egress LSR associated with this tunnel instance.
.1.3.6.1.2.1.10.166.3.2.2.1.5,MPLS-TE-STD-MIB::mplsTunnelName,OCTET,read-create,,current,,The canonical name assigned to the tunnel. This name can be used to refer to the tunnel on the LSR's console port. If mplsTunnelIsIf is set to true then the ifName of the interface corresponding to this tunnel should have a value equal to mplsTunnelName. Also see the description of ifName in RFC 2863.
.1.3.6.1.2.1.10.166.3.2.2.1.6,MPLS-TE-STD-MIB::mplsTunnelDescr,OCTET,read-create,,current,,A textual string containing information about the tunnel. If there is no description this object contains a zero length string. This object is may not be signaled by MPLS signaling protocols, consequentally the value of this object at transit and egress LSRs MAY be automatically generated or absent.
.1.3.6.1.2.1.10.166.3.2.2.1.7,MPLS-TE-STD-MIB::mplsTunnelIsIf,INTEGER,read-create,,current,true(1):false(2),Denotes whether or not this tunnel corresponds to an interface represented in the interfaces group table. Note that if this variable is set to true then the ifName of the interface corresponding to this tunnel should have a value equal to mplsTunnelName. Also see the description of ifName in RFC 2863. This object is meaningful only at the ingress and egress LSRs.
.1.3.6.1.2.1.10.166.3.2.2.1.8,MPLS-TE-STD-MIB::mplsTunnelIfIndex,Integer32,read-only,,current,,If mplsTunnelIsIf is set to true, then this value contains the LSR-assigned ifIndex which corresponds to an entry in the interfaces table. Otherwise this variable should contain the value of zero indicating that a valid ifIndex was not assigned to this tunnel interface.
.1.3.6.1.2.1.10.166.3.2.2.1.9,MPLS-TE-STD-MIB::mplsTunnelOwner,INTEGER,read-only,,current,unknown(1):other(2):snmp(3):ldp(4):crldp(5):rsvpTe(6):policyAgent(7),Denotes the entity that created and is responsible for managing this tunnel. This column is automatically filled by the agent on creation of a row.
.1.3.6.1.2.1.10.166.3.2.2.1.10,MPLS-TE-STD-MIB::mplsTunnelRole,INTEGER,read-create,,current,head(1):transit(2):tail(3):headTail(4),This value signifies the role that this tunnel entry/instance represents. This value MUST be set to head(1) at the originating point of the tunnel. This value MUST be set to transit(2) at transit points along the tunnel, if transit points are supported. This value MUST be set to tail(3) at the terminating point of the tunnel if tunnel tails are supported. The value headTail(4) is provided for tunnels that begin and end on the same LSR.
.1.3.6.1.2.1.10.166.3.2.2.1.11,MPLS-TE-STD-MIB::mplsTunnelXCPointer,OBJECT,read-create,,current,,This variable points to a row in the mplsXCTable. This table identifies the segments that compose this tunnel, their characteristics, and relationships to each other. A value of zeroDotZero indicates that no LSP has been associated with this tunnel yet.
.1.3.6.1.2.1.10.166.3.2.2.1.12,MPLS-TE-STD-MIB::mplsTunnelSignallingProto,INTEGER,read-create,,current,none(1):rsvp(2):crldp(3):other(4),The signalling protocol, if any, used to setup this tunnel.
.1.3.6.1.2.1.10.166.3.2.2.1.13,MPLS-TE-STD-MIB::mplsTunnelSetupPrio,Integer32,read-create,,current,,Indicates the setup priority of this tunnel.
.1.3.6.1.2.1.10.166.3.2.2.1.14,MPLS-TE-STD-MIB::mplsTunnelHoldingPrio,Integer32,read-create,,current,,Indicates the holding priority for this tunnel.
.1.3.6.1.2.1.10.166.3.2.2.1.15,MPLS-TE-STD-MIB::mplsTunnelSessionAttributes,BITS,read-create,,current,fastReroute(0):mergingPermitted(1):isPersistent(2):isPinned(3):recordRoute(4),This bit mask indicates optional session values for this tunnel. The following describes these bit fields: fastRerouteThis flag indicates that the any tunnel hop may choose to reroute this tunnel without tearing it down. This flag permits transit routers to use a local repair mechanism which may result in violation of the explicit routing of this tunnel. When a fault is detected on an adjacent downstream link or node, a transit router can re-route traffic for fast service restoration. mergingPermitted This flag permits transit routers to merge this session with other RSVP sessions for the purpose of reducing resource overhead on downstream transit routers, thereby providing better network scaling. isPersistent Indicates whether this tunnel should be restored automatically after a failure occurs. isPinned This flag indicates whether the loose- routed hops of this tunnel are to be pinned. recordRouteThis flag indicates whether or not the signalling protocol should remember the tunnel path after it has been signaled.
.1.3.6.1.2.1.10.166.3.2.2.1.16,MPLS-TE-STD-MIB::mplsTunnelLocalProtectInUse,INTEGER,read-create,,current,true(1):false(2),Indicates that the local repair mechanism is in use to maintain this tunnel (usually in the face of an outage of the link it was previously routed over).
.1.3.6.1.2.1.10.166.3.2.2.1.17,MPLS-TE-STD-MIB::mplsTunnelResourcePointer,OBJECT,read-create,,current,,This variable represents a pointer to the traffic parameter specification for this tunnel. This value may point at an entry in the mplsTunnelResourceEntry to indicate which mplsTunnelResourceEntry is to be assigned to this LSP instance. This value may optionally point at an externally defined traffic parameter specification table. A value of zeroDotZero indicates best-effort treatment. By having the same value of this object, two or more LSPs can indicate resource sharing.
.1.3.6.1.2.1.10.166.3.2.2.1.18,MPLS-TE-STD-MIB::mplsTunnelPrimaryInstance,Unsigned32,read-only,,current,,Specifies the instance index of the primary instance of this tunnel. More details of the definition of tunnel instances and the primary tunnel instance can be found in the description of the TEXTUAL-CONVENTION MplsTunnelInstanceIndex.
.1.3.6.1.2.1.10.166.3.2.2.1.19,MPLS-TE-STD-MIB::mplsTunnelInstancePriority,Unsigned32,read-create,,current,,This value indicates which priority, in descending order, with 0 indicating the lowest priority, within a group of tunnel instances. A group of tunnel instances is defined as a set of LSPs with the same mplsTunnelIndex in this table, but with a different mplsTunnelInstance. Tunnel instance priorities are used to denote the priority at which a particular tunnel instance will supercede another. Instances of tunnels containing the same mplsTunnelInstancePriority will be used for load sharing.
.1.3.6.1.2.1.10.166.3.2.2.1.20,MPLS-TE-STD-MIB::mplsTunnelHopTableIndex,Unsigned32,read-create,,current,,Index into the mplsTunnelHopTable entry that specifies the explicit route hops for this tunnel. This object is meaningful only at the head-end of the tunnel.
.1.3.6.1.2.1.10.166.3.2.2.1.21,MPLS-TE-STD-MIB::mplsTunnelPathInUse,Unsigned32,read-create,,current,,This value denotes the configured path that was chosen for this tunnel. This value reflects the secondary index into mplsTunnelHopTable. This path may not exactly match the one in mplsTunnelARHopTable due to the fact that some CSPF modification may have taken place. See mplsTunnelARHopTable for the actual path being taken by the tunnel. A value of zero denotes that no path is currently in use or available.
.1.3.6.1.2.1.10.166.3.2.2.1.22,MPLS-TE-STD-MIB::mplsTunnelARHopTableIndex,Unsigned32,read-only,,current,,Index into the mplsTunnelARHopTable entry that specifies the actual hops traversed by the tunnel. This is automatically updated by the agent when the actual hops becomes available.
.1.3.6.1.2.1.10.166.3.2.2.1.23,MPLS-TE-STD-MIB::mplsTunnelCHopTableIndex,Unsigned32,read-only,,current,,Index into the mplsTunnelCHopTable entry that specifies the computed hops traversed by the tunnel. This is automatically updated by the agent when computed hops become available or when computed hops get modified.
.1.3.6.1.2.1.10.166.3.2.2.1.24,MPLS-TE-STD-MIB::mplsTunnelIncludeAnyAffinity,Unsigned32,read-create,,current,,A link satisfies the include-any constraint if and only if the constraint is zero, or the link and the constraint have a resource class in common.
.1.3.6.1.2.1.10.166.3.2.2.1.25,MPLS-TE-STD-MIB::mplsTunnelIncludeAllAffinity,Unsigned32,read-create,,current,,A link satisfies the include-all constraint if and only if the link contains all of the administrative groups specified in the constraint.
.1.3.6.1.2.1.10.166.3.2.2.1.26,MPLS-TE-STD-MIB::mplsTunnelExcludeAnyAffinity,Unsigned32,read-create,,current,,A link satisfies the exclude-any constraint if and only if the link contains none of the administrative groups specified in the constraint.
.1.3.6.1.2.1.10.166.3.2.2.1.27,MPLS-TE-STD-MIB::mplsTunnelTotalUpTime,TimeTicks,read-only,,current,,This value represents the aggregate up time for all instances of this tunnel, if available. If this value is unavailable, it MUST return a value of 0.
.1.3.6.1.2.1.10.166.3.2.2.1.28,MPLS-TE-STD-MIB::mplsTunnelInstanceUpTime,TimeTicks,read-only,,current,,This value identifies the total time that this tunnel instance's operStatus has been Up(1).
.1.3.6.1.2.1.10.166.3.2.2.1.29,MPLS-TE-STD-MIB::mplsTunnelPrimaryUpTime,TimeTicks,read-only,,current,,Specifies the total time the primary instance of this tunnel has been active. The primary instance of this tunnel is defined in mplsTunnelPrimaryInstance.
.1.3.6.1.2.1.10.166.3.2.2.1.30,MPLS-TE-STD-MIB::mplsTunnelPathChanges,Counter32,read-only,,current,,Specifies the number of times the actual path for this tunnel instance has changed.
.1.3.6.1.2.1.10.166.3.2.2.1.31,MPLS-TE-STD-MIB::mplsTunnelLastPathChange,TimeTicks,read-only,,current,,Specifies the time since the last change to the actual path for this tunnel instance.
.1.3.6.1.2.1.10.166.3.2.2.1.32,MPLS-TE-STD-MIB::mplsTunnelCreationTime,TimeTicks,read-only,,current,,Specifies the value of SysUpTime when the first instance of this tunnel came into existence. That is, when the value of mplsTunnelOperStatus was first set to up(1).
.1.3.6.1.2.1.10.166.3.2.2.1.33,MPLS-TE-STD-MIB::mplsTunnelStateTransitions,Counter32,read-only,,current,,Specifies the number of times the state (mplsTunnelOperStatus) of this tunnel instance has changed.
.1.3.6.1.2.1.10.166.3.2.2.1.34,MPLS-TE-STD-MIB::mplsTunnelAdminStatus,INTEGER,read-create,,current,up(1):down(2):testing(3),Indicates the desired operational status of this tunnel.
.1.3.6.1.2.1.10.166.3.2.2.1.35,MPLS-TE-STD-MIB::mplsTunnelOperStatus,INTEGER,read-only,,current,up(1):down(2):testing(3):unknown(4):dormant(5):notPresent(6):lowerLayerDown(7),Indicates the actual operational status of this tunnel, which is typically but not limited to, a function of the state of individual segments of this tunnel.
.1.3.6.1.2.1.10.166.3.2.2.1.36,MPLS-TE-STD-MIB::mplsTunnelRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsTunnelAdminStatus, mplsTunnelRowStatus and mplsTunnelStorageType.
.1.3.6.1.2.1.10.166.3.2.2.1.37,MPLS-TE-STD-MIB::mplsTunnelStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this tunnel entry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.3.2.3,MPLS-TE-STD-MIB::mplsTunnelHopListIndexNext,Unsigned32,read-only,,current,,This object contains an appropriate value to be used for mplsTunnelHopListIndex when creating entries in the mplsTunnelHopTable. If the number of unassigned entries is exhausted, a retrieval operation will return a value of 0. This object may also return a value of 0 when the LSR is unable to accept conceptual row creation, for example, if the mplsTunnelHopTable is implemented as read-only. To obtain the value of mplsTunnelHopListIndex for a new entry in the mplsTunnelHopTable, the manager issues a management protocol retrieval operation to obtain the current value of mplsTunnelHopIndex. When the SET is performed to create a row in the mplsTunnelHopTable, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds and the Command Responder (agent) changes the value of this object, according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value.
.1.3.6.1.2.1.10.166.3.2.4,MPLS-TE-STD-MIB::mplsTunnelHopTable,,not-accessible,,current,,The mplsTunnelHopTable is used to indicate the hops, strict or loose, for an instance of an MPLS tunnel defined in mplsTunnelTable, when it is established via signalling, for the outgoing direction of the tunnel. Thus at a transit LSR, this table contains the desired path of the tunnel from this LSR onwards. Each row in this table is indexed by mplsTunnelHopListIndex which corresponds to a group of hop lists or path options. Each row also has a secondary index mplsTunnelHopIndex, which indicates a group of hops (also known as a path option). Finally, the third index, mplsTunnelHopIndex indicates the specific hop information for a path option. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelHopTable.
.1.3.6.1.2.1.10.166.3.2.4.1,MPLS-TE-STD-MIB::mplsTunnelHopEntry,,not-accessible,mplsTunnelHopListIndex:mplsTunnelHopPathOptionIndex:mplsTunnelHopIndex,current,,An entry in this table represents a tunnel hop. An entry is created by a network administrator for signaled ERLSP set up by an MPLS signalling protocol.
.1.3.6.1.2.1.10.166.3.2.4.1.1,MPLS-TE-STD-MIB::mplsTunnelHopListIndex,Unsigned32,not-accessible,,current,,Primary index into this table identifying a particular explicit route object.
.1.3.6.1.2.1.10.166.3.2.4.1.2,MPLS-TE-STD-MIB::mplsTunnelHopPathOptionIndex,Unsigned32,not-accessible,,current,,Secondary index into this table identifying a particular group of hops representing a particular configured path. This is otherwise known as a path option.
.1.3.6.1.2.1.10.166.3.2.4.1.3,MPLS-TE-STD-MIB::mplsTunnelHopIndex,Unsigned32,not-accessible,,current,,Tertiary index into this table identifying a particular hop.
.1.3.6.1.2.1.10.166.3.2.4.1.4,MPLS-TE-STD-MIB::mplsTunnelHopAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):asnumber(3):unnum(4):lspid(5),The Hop Address Type of this tunnel hop. The value of this object cannot be changed if the value of the corresponding mplsTunnelHopRowStatus object is 'active'. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP. 
.1.3.6.1.2.1.10.166.3.2.4.1.5,MPLS-TE-STD-MIB::mplsTunnelHopIpAddr,OCTET,read-create,,current,,The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelHopAddrType. The value of this object cannot be changed if the value of the corresponding mplsTunnelHopRowStatus object is 'active'. 
.1.3.6.1.2.1.10.166.3.2.4.1.6,MPLS-TE-STD-MIB::mplsTunnelHopIpPrefixLen,Unsigned32,read-create,,current,,If mplsTunnelHopAddrType is set to ipv4(1) or ipv6(2), then this value will contain an appropriate prefix length for the IP address in object mplsTunnelHopIpAddr. Otherwise this value is irrelevant and should be ignored. 
.1.3.6.1.2.1.10.166.3.2.4.1.7,MPLS-TE-STD-MIB::mplsTunnelHopAsNumber,OCTET,read-create,,current,,If mplsTunnelHopAddrType is set to asnumber(3), then this value will contain the AS number of this hop. Otherwise the agent should set this object to zero- length string and the manager should ignore this.
.1.3.6.1.2.1.10.166.3.2.4.1.8,MPLS-TE-STD-MIB::mplsTunnelHopAddrUnnum,OCTET,read-create,,current,,If mplsTunnelHopAddrType is set to unnum(4), then this value will contain the interface identifier of the unnumbered interface for this hop. This object should be used in conjunction with mplsTunnelHopIpAddress which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero-length string and the manager should ignore this.
.1.3.6.1.2.1.10.166.3.2.4.1.9,MPLS-TE-STD-MIB::mplsTunnelHopLspId,OCTET,read-create,,current,,If mplsTunnelHopAddrType is set to lspid(5), then this value will contain the LSPID of a tunnel of this hop. The present tunnel being configured is tunneled through this hop (using label stacking). This object is otherwise insignificant and should contain a value of 0 to indicate this fact.
.1.3.6.1.2.1.10.166.3.2.4.1.10,MPLS-TE-STD-MIB::mplsTunnelHopType,INTEGER,read-create,,current,strict(1):loose(2),Denotes whether this tunnel hop is routed in a strict or loose fashion. The value of this object has no meaning if the mplsTunnelHopInclude object is set to 'false'.
.1.3.6.1.2.1.10.166.3.2.4.1.11,MPLS-TE-STD-MIB::mplsTunnelHopInclude,INTEGER,read-create,,current,true(1):false(2),If this value is set to true, then this indicates that this hop must be included in the tunnel's path. If this value is set to 'false', then this hop must be avoided when calculating the path for this tunnel. The default value of this object is 'true', so that by default all indicated hops are included in the CSPF path computation. If this object is set to 'false' the value of mplsTunnelHopType should be ignored.
.1.3.6.1.2.1.10.166.3.2.4.1.12,MPLS-TE-STD-MIB::mplsTunnelHopPathOptionName,OCTET,read-create,,current,,The description of this series of hops as they relate to the specified path option. The value of this object SHOULD be the same for each hop in the series that comprises a path option.
.1.3.6.1.2.1.10.166.3.2.4.1.13,MPLS-TE-STD-MIB::mplsTunnelHopEntryPathComp,INTEGER,read-create,,current,dynamic(1):explicit(2),If this value is set to dynamic, then the user should only specify the source and destination of the path and expect that the CSPF will calculate the remainder of the path. If this value is set to explicit, the user should specify the entire path for the tunnel to take. This path may contain strict or loose hops. Each hop along a specific path SHOULD have this object set to the same value
.1.3.6.1.2.1.10.166.3.2.4.1.14,MPLS-TE-STD-MIB::mplsTunnelHopRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsTunnelHopRowStatus and mplsTunnelHopStorageType.
.1.3.6.1.2.1.10.166.3.2.4.1.15,MPLS-TE-STD-MIB::mplsTunnelHopStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this Hop entry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.3.2.5,MPLS-TE-STD-MIB::mplsTunnelResourceIndexNext,Unsigned32,read-only,,current,,This object contains the next appropriate value to be used for mplsTunnelResourceIndex when creating entries in the mplsTunnelResourceTable. If the number of unassigned entries is exhausted, a retrieval operation will return a value of 0. This object may also return a value of 0 when the LSR is unable to accept conceptual row creation, for example, if the mplsTunnelTable is implemented as read-only. To obtain the mplsTunnelResourceIndex value for a new entry, the manager must first issue a management protocol retrieval operation to obtain the current value of this object. When the SET is performed to create a row in the mplsTunnelResourceTable, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds and the Command Responder (agent) changes the value of this object, according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value.
.1.3.6.1.2.1.10.166.3.2.6,MPLS-TE-STD-MIB::mplsTunnelResourceTable,,not-accessible,,current,,The mplsTunnelResourceTable allows a manager to specify which resources are desired for an MPLS tunnel. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources.
.1.3.6.1.2.1.10.166.3.2.6.1,MPLS-TE-STD-MIB::mplsTunnelResourceEntry,,not-accessible,mplsTunnelResourceIndex,current,,An entry in this table represents a set of resources for an MPLS tunnel. An entry can be created by a network administrator or by an SNMP agent as instructed by any MPLS signalling protocol. An entry in this table referenced by a tunnel instance with zero mplsTunnelInstance value indicates a configured set of resource parameter. An entry referenced by a tunnel instance with a non-zero mplsTunnelInstance reflects the in-use resource parameters for the tunnel instance which may have been negotiated or modified by the MPLS signaling protocols.
.1.3.6.1.2.1.10.166.3.2.6.1.1,MPLS-TE-STD-MIB::mplsTunnelResourceIndex,Unsigned32,not-accessible,,current,,Uniquely identifies this row.
.1.3.6.1.2.1.10.166.3.2.6.1.2,MPLS-TE-STD-MIB::mplsTunnelResourceMaxRate,Unsigned32,read-create,,current,,The maximum rate in bits/second. Note that setting mplsTunnelResourceMaxRate, mplsTunnelResourceMeanRate, and mplsTunnelResourceMaxBurstSize to 0 indicates best- effort treatment.
.1.3.6.1.2.1.10.166.3.2.6.1.3,MPLS-TE-STD-MIB::mplsTunnelResourceMeanRate,Unsigned32,read-create,,current,,This object is copied into an instance of mplsTrafficParamMeanRate in the mplsTrafficParamTable. The OID of this table entry is then copied into the corresponding mplsInSegmentTrafficParamPtr.
.1.3.6.1.2.1.10.166.3.2.6.1.4,MPLS-TE-STD-MIB::mplsTunnelResourceMaxBurstSize,Unsigned32,read-create,,current,,The maximum burst size in bytes.
.1.3.6.1.2.1.10.166.3.2.6.1.5,MPLS-TE-STD-MIB::mplsTunnelResourceMeanBurstSize,Unsigned32,read-create,,current,,The mean burst size in bytes. The implementations which do not implement this variable must return a noSuchObject exception for this object and must not allow a user to set this object.
.1.3.6.1.2.1.10.166.3.2.6.1.6,MPLS-TE-STD-MIB::mplsTunnelResourceExBurstSize,Unsigned32,read-create,,current,,The Excess burst size in bytes. The implementations which do not implement this variable must return noSuchObject exception for this object and must not allow a user to set this value.
.1.3.6.1.2.1.10.166.3.2.6.1.7,MPLS-TE-STD-MIB::mplsTunnelResourceFrequency,INTEGER,read-create,,current,unspecified(1):frequent(2):veryFrequent(3),The granularity of the availability of committed rate. The implementations which do not implement this variable must return unspecified(1) for this value and must not allow a user to set this value.
.1.3.6.1.2.1.10.166.3.2.6.1.8,MPLS-TE-STD-MIB::mplsTunnelResourceWeight,Unsigned32,read-create,,current,,The relative weight for using excess bandwidth above its committed rate. The value of 0 means that weight is not applicable for the CR-LSP.
.1.3.6.1.2.1.10.166.3.2.6.1.9,MPLS-TE-STD-MIB::mplsTunnelResourceRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsTunnelResourceRowStatus and mplsTunnelResourceStorageType.
.1.3.6.1.2.1.10.166.3.2.6.1.10,MPLS-TE-STD-MIB::mplsTunnelResourceStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this Hop entry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.3.2.7,MPLS-TE-STD-MIB::mplsTunnelARHopTable,,not-accessible,,current,,The mplsTunnelARHopTable is used to indicate the hops for an MPLS tunnel defined in mplsTunnelTable, as reported by the MPLS signalling protocol. Thus at a transit LSR, this table (if the table is supported and if the signaling protocol is recording actual route information) contains the actual route of the whole tunnel. If the signaling protocol is not recording the actual route, this table MAY report the information from the mplsTunnelHopTable or the mplsTunnelCHopTable. Each row in this table is indexed by mplsTunnelARHopListIndex. Each row also has a secondary index mplsTunnelARHopIndex, corresponding to the next hop that this row corresponds to. Please note that since the information necessary to build entries within this table is not provided by some MPLS signalling protocols, implementation of this table is optional. Furthermore, since the information in this table is actually provided by the MPLS signalling protocol after the path has been set-up, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read- only. Note also that the contents of this table may change while it is being read because of re-routing activities. A network administrator may verify that the actual route read is consistent by reference to the mplsTunnelLastPathChange object.
.1.3.6.1.2.1.10.166.3.2.7.1,MPLS-TE-STD-MIB::mplsTunnelARHopEntry,,not-accessible,mplsTunnelARHopListIndex:mplsTunnelARHopIndex,current,,An entry in this table represents a tunnel hop. An entry is created by the agent for signaled ERLSP set up by an MPLS signalling protocol.
.1.3.6.1.2.1.10.166.3.2.7.1.1,MPLS-TE-STD-MIB::mplsTunnelARHopListIndex,Unsigned32,not-accessible,,current,,Primary index into this table identifying a particular recorded hop list.
.1.3.6.1.2.1.10.166.3.2.7.1.2,MPLS-TE-STD-MIB::mplsTunnelARHopIndex,Unsigned32,not-accessible,,current,,Secondary index into this table identifying the particular hop.
.1.3.6.1.2.1.10.166.3.2.7.1.3,MPLS-TE-STD-MIB::mplsTunnelARHopAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):asnumber(3):unnum(4):lspid(5),The Hop Address Type of this tunnel hop. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP.
.1.3.6.1.2.1.10.166.3.2.7.1.4,MPLS-TE-STD-MIB::mplsTunnelARHopIpAddr,OCTET,read-only,,current,,The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelARHopAddrType. If mplsTunnelARHopAddrType is set to unnum(4), then this value contains the LSR Router ID of the unnumbered interface. Otherwise the agent SHOULD set this object to the zero-length string and the manager should ignore this object.
.1.3.6.1.2.1.10.166.3.2.7.1.5,MPLS-TE-STD-MIB::mplsTunnelARHopAddrUnnum,OCTET,read-only,,current,,If mplsTunnelARHopAddrType is set to unnum(4), then this value will contain the interface identifier of the unnumbered interface for this hop. This object should be used in conjunction with mplsTunnelARHopIpAddr which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero-length string and the manager should ignore this.
.1.3.6.1.2.1.10.166.3.2.7.1.6,MPLS-TE-STD-MIB::mplsTunnelARHopLspId,OCTET,read-only,,current,,If mplsTunnelARHopAddrType is set to lspid(5), then this value will contain the LSP ID of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact.
.1.3.6.1.2.1.10.166.3.2.8,MPLS-TE-STD-MIB::mplsTunnelCHopTable,,not-accessible,,current,,The mplsTunnelCHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as computed by a constraint- based routing protocol, based on the mplsTunnelHopTable for the outgoing direction of the tunnel. Thus at a transit LSR, this table (if the table is supported) MAY contain the path computed by the CSPF engine on (or on behalf of) this LSR. Each row in this table is indexed by mplsTunnelCHopListIndex. Each row also has a secondary index mplsTunnelCHopIndex, corresponding to the next hop that this row corresponds to. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelCHopTable. Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional. Furthermore, since the information in this table describes the path computed by the CSPF engine the entries in this table are read-only.
.1.3.6.1.2.1.10.166.3.2.8.1,MPLS-TE-STD-MIB::mplsTunnelCHopEntry,,not-accessible,mplsTunnelCHopListIndex:mplsTunnelCHopIndex,current,,An entry in this table represents a tunnel hop. An entry in this table is created by a path computation engine using CSPF techniques applied to the information collected by routing protocols and the hops specified in the corresponding mplsTunnelHopTable.
.1.3.6.1.2.1.10.166.3.2.8.1.1,MPLS-TE-STD-MIB::mplsTunnelCHopListIndex,Unsigned32,not-accessible,,current,,Primary index into this table identifying a particular computed hop list.
.1.3.6.1.2.1.10.166.3.2.8.1.2,MPLS-TE-STD-MIB::mplsTunnelCHopIndex,Unsigned32,not-accessible,,current,,Secondary index into this table identifying the particular hop.
.1.3.6.1.2.1.10.166.3.2.8.1.3,MPLS-TE-STD-MIB::mplsTunnelCHopAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):asnumber(3):unnum(4):lspid(5),The Hop Address Type of this tunnel hop. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP.
.1.3.6.1.2.1.10.166.3.2.8.1.4,MPLS-TE-STD-MIB::mplsTunnelCHopIpAddr,OCTET,read-only,,current,,The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelCHopAddrType. If mplsTunnelCHopAddrType is set to unnum(4), then this value will contain the LSR Router ID of the unnumbered interface. Otherwise the agent should set this object to the zero-length string and the manager SHOULD ignore this object.
.1.3.6.1.2.1.10.166.3.2.8.1.5,MPLS-TE-STD-MIB::mplsTunnelCHopIpPrefixLen,Unsigned32,read-only,,current,,If mplsTunnelCHopAddrType is set to ipv4(1) or ipv6(2), then this value will contain an appropriate prefix length for the IP address in object mplsTunnelCHopIpAddr. Otherwise this value is irrelevant and should be ignored. 
.1.3.6.1.2.1.10.166.3.2.8.1.6,MPLS-TE-STD-MIB::mplsTunnelCHopAsNumber,OCTET,read-only,,current,,If mplsTunnelCHopAddrType is set to asnumber(3), then this value will contain the AS number of this hop. Otherwise the agent should set this object to zero-length string and the manager should ignore this.
.1.3.6.1.2.1.10.166.3.2.8.1.7,MPLS-TE-STD-MIB::mplsTunnelCHopAddrUnnum,OCTET,read-only,,current,,If mplsTunnelCHopAddrType is set to unnum(4), then this value will contain the unnumbered interface identifier of this hop. This object should be used in conjunction with mplsTunnelCHopIpAddr which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero- length string and the manager should ignore this.
.1.3.6.1.2.1.10.166.3.2.8.1.8,MPLS-TE-STD-MIB::mplsTunnelCHopLspId,OCTET,read-only,,current,,If mplsTunnelCHopAddrType is set to lspid(5), then this value will contain the LSP ID of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact.
.1.3.6.1.2.1.10.166.3.2.8.1.9,MPLS-TE-STD-MIB::mplsTunnelCHopType,INTEGER,read-only,,current,strict(1):loose(2),Denotes whether this is tunnel hop is routed in a strict or loose fashion.
.1.3.6.1.2.1.10.166.3.2.9,MPLS-TE-STD-MIB::mplsTunnelPerfTable,,not-accessible,,current,,This table provides per-tunnel instance MPLS performance information.
.1.3.6.1.2.1.10.166.3.2.9.1,MPLS-TE-STD-MIB::mplsTunnelPerfEntry,,not-accessible,,current,,An entry in this table is created by the LSR for every tunnel. Its is an extension to mplsTunnelEntry.
.1.3.6.1.2.1.10.166.3.2.9.1.1,MPLS-TE-STD-MIB::mplsTunnelPerfPackets,Counter32,read-only,,current,,Number of packets forwarded by the tunnel. This object should represents the 32-bit value of the least significant part of the 64-bit value if both mplsTunnelPerfHCPackets is returned.
.1.3.6.1.2.1.10.166.3.2.9.1.2,MPLS-TE-STD-MIB::mplsTunnelPerfHCPackets,Counter64,read-only,,current,,High capacity counter for number of packets forwarded by the tunnel. 
.1.3.6.1.2.1.10.166.3.2.9.1.3,MPLS-TE-STD-MIB::mplsTunnelPerfErrors,Counter32,read-only,,current,,Number of packets dropped because of errors or for other reasons.
.1.3.6.1.2.1.10.166.3.2.9.1.4,MPLS-TE-STD-MIB::mplsTunnelPerfBytes,Counter32,read-only,,current,,Number of bytes forwarded by the tunnel. This object should represents the 32-bit value of the least significant part of the 64-bit value if both mplsTunnelPerfHCBytes is returned.
.1.3.6.1.2.1.10.166.3.2.9.1.5,MPLS-TE-STD-MIB::mplsTunnelPerfHCBytes,Counter64,read-only,,current,,High capacity counter for number of bytes forwarded by the tunnel.
.1.3.6.1.2.1.10.166.3.2.10,MPLS-TE-STD-MIB::mplsTunnelCRLDPResTable,,not-accessible,,current,,The mplsTunnelCRLDPResTable allows a manager to specify which CR-LDP-specific resources are desired for an MPLS tunnel if that tunnel is signaled using CR-LDP. Note that these attributes are in addition to those specified in mplsTunnelResourceTable. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources.
.1.3.6.1.2.1.10.166.3.2.10.1,MPLS-TE-STD-MIB::mplsTunnelCRLDPResEntry,,not-accessible,mplsTunnelResourceIndex,current,,An entry in this table represents a set of resources for an MPLS tunnel established using CRLDP (mplsTunnelSignallingProto equal to crldp (3)). An entry can be created by a network administrator or by an SNMP agent as instructed by any MPLS signalling protocol.
.1.3.6.1.2.1.10.166.3.2.10.1.1,MPLS-TE-STD-MIB::mplsTunnelCRLDPResMeanBurstSize,Unsigned32,read-create,,current,,The mean burst size in bytes.
.1.3.6.1.2.1.10.166.3.2.10.1.2,MPLS-TE-STD-MIB::mplsTunnelCRLDPResExBurstSize,Unsigned32,read-create,,current,,The Excess burst size in bytes.
.1.3.6.1.2.1.10.166.3.2.10.1.3,MPLS-TE-STD-MIB::mplsTunnelCRLDPResFrequency,INTEGER,read-create,,current,unspecified(1):frequent(2):veryFrequent(3),The granularity of the availability of committed rate.
.1.3.6.1.2.1.10.166.3.2.10.1.4,MPLS-TE-STD-MIB::mplsTunnelCRLDPResWeight,Unsigned32,read-create,,current,,The relative weight for using excess bandwidth above its committed rate. The value of 0 means that weight is not applicable for the CR-LSP.
.1.3.6.1.2.1.10.166.3.2.10.1.5,MPLS-TE-STD-MIB::mplsTunnelCRLDPResFlags,Unsigned32,read-create,,current,,The value of the 1 byte Flags conveyed as part of the traffic parameters during the establishment of the CRLSP. The bits in this object are to be interpreted as follows. +--+--+--+--+--+--+--+--+ | Res |F6|F5|F4|F3|F2|F1| +--+--+--+--+--+--+--+--+ Res - These bits are reserved. Zero on transmission. Ignored on receipt. F1 - Corresponds to the PDR. F2 - Corresponds to the PBS. F3 - Corresponds to the CDR. F4 - Corresponds to the CBS. F5 - Corresponds to the EBS. F6 - Corresponds to the Weight. Each flag if is a Negotiable Flag corresponding to a Traffic Parameter. The Negotiable Flag value zero denotes Not Negotiable and value one denotes Negotiable.
.1.3.6.1.2.1.10.166.3.2.10.1.6,MPLS-TE-STD-MIB::mplsTunnelCRLDPResRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsTunnelCRLDPResRowStatus and mplsTunnelCRLDPResStorageType.
.1.3.6.1.2.1.10.166.3.2.10.1.7,MPLS-TE-STD-MIB::mplsTunnelCRLDPResStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this CR-LDP Resource entry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.3.2.11,MPLS-TE-STD-MIB::mplsTunnelNotificationEnable,INTEGER,read-write,,current,true(1):false(2),If this object is true, then it enables the generation of mplsTunnelUp and mplsTunnelDown traps, otherwise these traps are not emitted.
.1.3.6.1.2.1.10.166.3.3,MPLS-TE-STD-MIB::mplsTeConformance,,,,,,
.1.3.6.1.2.1.10.166.3.3.1,MPLS-TE-STD-MIB::mplsTeGroups,,,,,,
.1.3.6.1.2.1.10.166.3.3.1.1,MPLS-TE-STD-MIB::mplsTunnelGroup,,,,,,Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the type of the tunnels supported (for example, manually configured or signaled, persistent or non- persistent, etc.), the following other groups defined below are mandatory: mplsTunnelManualGroup and/or mplsTunnelSignaledGroup, mplsTunnelIsNotIntfcGroup and/or mplsTunnelIsIntfcGroup.
.1.3.6.1.2.1.10.166.3.3.1.2,MPLS-TE-STD-MIB::mplsTunnelManualGroup,,,,,,Object(s) needed to implement manually configured tunnels.
.1.3.6.1.2.1.10.166.3.3.1.3,MPLS-TE-STD-MIB::mplsTunnelSignaledGroup,,,,,,Objects needed to implement signaled tunnels.
.1.3.6.1.2.1.10.166.3.3.1.4,MPLS-TE-STD-MIB::mplsTunnelScalarGroup,,,,,,Scalar object needed to implement MPLS tunnels.
.1.3.6.1.2.1.10.166.3.3.1.5,MPLS-TE-STD-MIB::mplsTunnelIsIntfcGroup,,,,,,Objects needed to implement tunnels that are interfaces.
.1.3.6.1.2.1.10.166.3.3.1.6,MPLS-TE-STD-MIB::mplsTunnelIsNotIntfcGroup,,,,,,Objects needed to implement tunnels that are not interfaces.
.1.3.6.1.2.1.10.166.3.3.1.7,MPLS-TE-STD-MIB::mplsTunnelCRLDPResOptionalGroup,,,,,,Set of objects implemented for resources applicable for tunnels signaled using CR-LDP.
.1.3.6.1.2.1.10.166.3.3.1.8,MPLS-TE-STD-MIB::mplsTeNotificationGroup,,,,,,Set of notifications implemented in this module. None is mandatory.
.1.3.6.1.2.1.10.166.3.3.2,MPLS-TE-STD-MIB::mplsTeCompliances,,,,,,
.1.3.6.1.2.1.10.166.3.3.2.1,MPLS-TE-STD-MIB::mplsTeModuleFullCompliance,,,,,,Compliance statement for agents that provide full support the MPLS-TE-STD-MIB module.
.1.3.6.1.2.1.10.166.3.3.2.2,MPLS-TE-STD-MIB::mplsTeModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-TE-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.
.1.3.6.1.2.1.10.166.4,MPLS-LDP-STD-MIB::mplsLdpStdMIB,,,,,,Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB contains managed object definitions for the 'Multiprotocol Label Switching, Label Distribution Protocol, LDP' document.
.1.3.6.1.2.1.10.166.4.0,MPLS-LDP-STD-MIB::mplsLdpNotifications,,,,,,
.1.3.6.1.2.1.10.166.4.0.1,MPLS-LDP-STD-MIB::mplsLdpInitSessionThresholdExceeded,,,,,,This notification is generated when the value of the 'mplsLdpEntityInitSessionThreshold' object is not zero, and the number of Session Initialization messages exceeds the value of the 'mplsLdpEntityInitSessionThreshold' object.
.1.3.6.1.2.1.10.166.4.0.2,MPLS-LDP-STD-MIB::mplsLdpPathVectorLimitMismatch,,,,,,This notification is sent when the 'mplsLdpEntityPathVectorLimit' does NOT match the value of the 'mplsLdpPeerPathVectorLimit' for a specific Entity.
.1.3.6.1.2.1.10.166.4.0.3,MPLS-LDP-STD-MIB::mplsLdpSessionUp,,,,,,If this notification is sent when the value of 'mplsLdpSessionState' enters the 'operational(5)' state.
.1.3.6.1.2.1.10.166.4.0.4,MPLS-LDP-STD-MIB::mplsLdpSessionDown,,,,,,This notification is sent when the value of 'mplsLdpSessionState' leaves the 'operational(5)' state.
.1.3.6.1.2.1.10.166.4.1,MPLS-LDP-STD-MIB::mplsLdpObjects,,,,,,
.1.3.6.1.2.1.10.166.4.1.1,MPLS-LDP-STD-MIB::mplsLdpLsrObjects,,,,,,
.1.3.6.1.2.1.10.166.4.1.1.1,MPLS-LDP-STD-MIB::mplsLdpLsrId,OCTET,read-only,,current,,The Label Switching Router's Identifier.
.1.3.6.1.2.1.10.166.4.1.1.2,MPLS-LDP-STD-MIB::mplsLdpLsrLoopDetectionCapable,INTEGER,read-only,,current,none(1):other(2):hopCount(3):pathVector(4):hopCountAndPathVector(5),A indication of whether this Label Switching Router supports loop detection. none(1) -- Loop Detection is not supported on this LSR. other(2) -- Loop Detection is supported but by a method other than those listed below. hopCount(3) -- Loop Detection is supported by Hop Count only. pathVector(4) -- Loop Detection is supported by Path Vector only. hopCountAndPathVector(5) -- Loop Detection is supported by both Hop Count And Path Vector. Since Loop Detection is determined during Session Initialization, an individual session may not be running with loop detection. This object simply gives an indication of whether or not the LSR has the ability to support Loop Detection and which types.
.1.3.6.1.2.1.10.166.4.1.2,MPLS-LDP-STD-MIB::mplsLdpEntityObjects,,,,,,
.1.3.6.1.2.1.10.166.4.1.2.1,MPLS-LDP-STD-MIB::mplsLdpEntityLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the most recent addition or deletion of an entry to/from the mplsLdpEntityTable/mplsLdpEntityStatsTable, or the most recent change in value of any objects in the mplsLdpEntityTable. If no such changes have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.4.1.2.2,MPLS-LDP-STD-MIB::mplsLdpEntityIndexNext,Unsigned32,read-only,,current,,This object contains an appropriate value to be used for mplsLdpEntityIndex when creating entries in the mplsLdpEntityTable. The value 0 indicates that no unassigned entries are available.
.1.3.6.1.2.1.10.166.4.1.2.3,MPLS-LDP-STD-MIB::mplsLdpEntityTable,,not-accessible,,current,,This table contains information about the MPLS Label Distribution Protocol Entities which exist on this Label Switching Router (LSR) or Label Edge Router (LER).
.1.3.6.1.2.1.10.166.4.1.2.3.1,MPLS-LDP-STD-MIB::mplsLdpEntityEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex,current,,An entry in this table represents an LDP entity. An entry can be created by a network administrator or by an SNMP agent as instructed by LDP.
.1.3.6.1.2.1.10.166.4.1.2.3.1.1,MPLS-LDP-STD-MIB::mplsLdpEntityLdpId,OCTET,not-accessible,,current,,The LDP identifier.
.1.3.6.1.2.1.10.166.4.1.2.3.1.2,MPLS-LDP-STD-MIB::mplsLdpEntityIndex,Unsigned32,not-accessible,,current,,This index is used as a secondary index to uniquely identify this row. Before creating a row in this table, the 'mplsLdpEntityIndexNext' object should be retrieved. That value should be used for the value of this index when creating a row in this table. NOTE: if a value of zero (0) is retrieved, that indicates that no rows can be created in this table at this time. A secondary index (this object) is meaningful to some but not all, LDP implementations. For example an LDP implementation which uses PPP would use this index to differentiate PPP sub-links. Another way to use this index is to give this the value of ifIndex. However, this is dependant on the implementation.
.1.3.6.1.2.1.10.166.4.1.2.3.1.3,MPLS-LDP-STD-MIB::mplsLdpEntityProtocolVersion,Unsigned32,read-create,,current,,The version number of the LDP protocol which will be used in the session initialization message. Section 3.5.3 in the LDP Specification specifies that the version of the LDP protocol is negotiated during session establishment. The value of this object represents the value that is sent in the initialization message.
.1.3.6.1.2.1.10.166.4.1.2.3.1.4,MPLS-LDP-STD-MIB::mplsLdpEntityAdminStatus,INTEGER,read-create,,current,enable(1):disable(2),The administrative status of this LDP Entity. If this object is changed from 'enable' to 'disable' and this entity has already attempted to establish contact with a Peer, then all contact with that Peer is lost and all information from that Peer needs to be removed from the MIB. (This implies that the network management subsystem should clean up any related entry in the mplsLdpPeerTable. This further implies that a 'tear-down' for that session is issued and the session and all information related to that session cease to exist). At this point the operator is able to change values which are related to this entity. When the admin status is set back to 'enable', then this Entity will attempt to establish a new session with the Peer.
.1.3.6.1.2.1.10.166.4.1.2.3.1.5,MPLS-LDP-STD-MIB::mplsLdpEntityOperStatus,INTEGER,read-only,,current,unknown(1):enabled(2):disabled(3),The operational status of this LDP Entity. The value of unknown(1) indicates that the operational status cannot be determined at this time. The value of unknown should be a transient condition before changing to enabled(2) or disabled(3).
.1.3.6.1.2.1.10.166.4.1.2.3.1.6,MPLS-LDP-STD-MIB::mplsLdpEntityTcpPort,Unsigned32,read-create,,current,,The TCP Port for LDP. The default value is the well-known value of this port.
.1.3.6.1.2.1.10.166.4.1.2.3.1.7,MPLS-LDP-STD-MIB::mplsLdpEntityUdpDscPort,Unsigned32,read-create,,current,,The UDP Discovery Port for LDP. The default value is the well-known value for this port.
.1.3.6.1.2.1.10.166.4.1.2.3.1.8,MPLS-LDP-STD-MIB::mplsLdpEntityMaxPduLength,Unsigned32,read-create,,current,,The maximum PDU Length that is sent in the Common Session Parameters of an Initialization Message. According to the LDP Specification [RFC3036] a value of 255 or less specifies the default maximum length of 4096 octets, this is why the value of this object starts at 256. The operator should explicitly choose the default value (i.e., 4096), or some other value. The receiving LSR MUST calculate the maximum PDU length for the session by using the smaller of its and its peer's proposals for Max PDU Length.
.1.3.6.1.2.1.10.166.4.1.2.3.1.9,MPLS-LDP-STD-MIB::mplsLdpEntityKeepAliveHoldTimer,Unsigned32,read-create,,current,,The 16-bit integer value which is the proposed keep alive hold timer for this LDP Entity.
.1.3.6.1.2.1.10.166.4.1.2.3.1.10,MPLS-LDP-STD-MIB::mplsLdpEntityHelloHoldTimer,Unsigned32,read-create,,current,,The 16-bit integer value which is the proposed Hello hold timer for this LDP Entity. The Hello Hold time in seconds. An LSR maintains a record of Hellos received from potential peers. This object represents the Hold Time in the Common Hello Parameters TLV of the Hello Message. A value of 0 is a default value and should be interpretted in conjunction with the mplsLdpEntityTargetPeer object. If the value of this object is 0: if the value of the mplsLdpEntityTargetPeer object is false(2), then this specifies that the Hold Time's actual default value is 15 seconds (i.e., the default Hold time for Link Hellos is 15 seconds). Otherwise if the value of the mplsLdpEntityTargetPeer object is true(1), then this specifies that the Hold Time's actual default value is 45 seconds (i.e., the default Hold time for Targeted Hellos is 45 seconds). A value of 65535 means infinite (i.e., wait forever). All other values represent the amount of time in seconds to wait for a Hello Message. Setting the hold time to a value smaller than 15 is not recommended, although not forbidden according to RFC3036.
.1.3.6.1.2.1.10.166.4.1.2.3.1.11,MPLS-LDP-STD-MIB::mplsLdpEntityInitSessionThreshold,Integer32,read-create,,current,,When attempting to establish a session with a given Peer, the given LDP Entity should send out the SNMP notification, 'mplsLdpInitSessionThresholdExceeded', when the number of Session Initialization messages sent exceeds this threshold. The notification is used to notify an operator when this Entity and its Peer are possibly engaged in an endless sequence of messages as each NAKs the other's Initialization messages with Error Notification messages. Setting this threshold which triggers the notification is one way to notify the operator. The notification should be generated each time this threshold is exceeded and for every subsequent Initialization message which is NAK'd with an Error Notification message after this threshold is exceeded. A value of 0 (zero) for this object indicates that the threshold is infinity, thus the SNMP notification will never be generated.
.1.3.6.1.2.1.10.166.4.1.2.3.1.12,MPLS-LDP-STD-MIB::mplsLdpEntityLabelDistMethod,INTEGER,read-create,,current,downstreamOnDemand(1):downstreamUnsolicited(2),For any given LDP session, the method of label distribution must be specified.
.1.3.6.1.2.1.10.166.4.1.2.3.1.13,MPLS-LDP-STD-MIB::mplsLdpEntityLabelRetentionMode,INTEGER,read-create,,current,conservative(1):liberal(2),The LDP Entity can be configured to use either conservative or liberal label retention mode. If the value of this object is conservative(1) then advertized label mappings are retained only if they will be used to forward packets, i.e., if label came from a valid next hop. If the value of this object is liberal(2) then all advertized label mappings are retained whether they are from a valid next hop or not.
.1.3.6.1.2.1.10.166.4.1.2.3.1.14,MPLS-LDP-STD-MIB::mplsLdpEntityPathVectorLimit,Integer32,read-create,,current,,If the value of this object is 0 (zero) then Loop Detection for Path Vectors is disabled. Otherwise, if this object has a value greater than zero, then Loop Dection for Path Vectors is enabled, and the Path Vector Limit is this value. Also, the value of the object, 'mplsLdpLsrLoopDetectionCapable', must be set to either 'pathVector(4)' or 'hopCountAndPathVector(5)', if this object has a value greater than 0 (zero), otherwise it is ignored.
.1.3.6.1.2.1.10.166.4.1.2.3.1.15,MPLS-LDP-STD-MIB::mplsLdpEntityHopCountLimit,Integer32,read-create,,current,,If the value of this object is 0 (zero), then Loop Detection using Hop Counters is disabled. If the value of this object is greater than 0 (zero) then Loop Detection using Hop Counters is enabled, and this object specifies this Entity's maximum allowable value for the Hop Count. Also, the value of the object mplsLdpLsrLoopDetectionCapable must be set to either 'hopCount(3)' or 'hopCountAndPathVector(5)' if this object has a value greater than 0 (zero), otherwise it is ignored.
.1.3.6.1.2.1.10.166.4.1.2.3.1.16,MPLS-LDP-STD-MIB::mplsLdpEntityTransportAddrKind,INTEGER,read-create,,current,interface(1):loopback(2),This specifies whether the loopback or interface address is to be used as the transport address in the transport address TLV of the hello message. If the value is interface(1), then the IP address of the interface from which hello messages are sent is used as the transport address in the hello message. Otherwise, if the value is loopback(2), then the IP address of the loopback interface is used as the transport address in the hello message.
.1.3.6.1.2.1.10.166.4.1.2.3.1.17,MPLS-LDP-STD-MIB::mplsLdpEntityTargetPeer,INTEGER,read-create,,current,true(1):false(2),If this LDP entity uses targeted peer then set this to true.
.1.3.6.1.2.1.10.166.4.1.2.3.1.18,MPLS-LDP-STD-MIB::mplsLdpEntityTargetPeerAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the internetwork layer address used for the Extended Discovery. This object indicates how the value of mplsLdpEntityTargetPeerAddr is to be interpreted.
.1.3.6.1.2.1.10.166.4.1.2.3.1.19,MPLS-LDP-STD-MIB::mplsLdpEntityTargetPeerAddr,OCTET,read-create,,current,,The value of the internetwork layer address used for the Extended Discovery. The value of mplsLdpEntityTargetPeerAddrType specifies how this address is to be interpreted.
.1.3.6.1.2.1.10.166.4.1.2.3.1.20,MPLS-LDP-STD-MIB::mplsLdpEntityLabelType,INTEGER,read-create,,current,generic(1):atm(2):frameRelay(3),Specifies the optional parameters for the LDP Initialization Message. If the value is generic(1) then no optional parameters will be sent in the LDP Initialization message associated with this Entity. If the value is atmParameters(2) then a row must be created in the mplsLdpEntityAtmTable, which corresponds to this entry. If the value is frameRelayParameters(3) then a row must be created in the mplsLdpEntityFrameRelayTable, which corresponds to this entry.
.1.3.6.1.2.1.10.166.4.1.2.3.1.21,MPLS-LDP-STD-MIB::mplsLdpEntityDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entity's counters suffered a discontinuity. The relevant counters are the specific instances associated with this entity of any Counter32 object contained in the 'mplsLdpEntityStatsTable'. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.4.1.2.3.1.22,MPLS-LDP-STD-MIB::mplsLdpEntityStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.4.1.2.3.1.23,MPLS-LDP-STD-MIB::mplsLdpEntityRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable, which enables a new session to be initiated.
.1.3.6.1.2.1.10.166.4.1.2.4,MPLS-LDP-STD-MIB::mplsLdpEntityStatsTable,,not-accessible,,current,,This table is a read-only table which augments the mplsLdpEntityTable. The purpose of this table is to keep statistical information about the LDP Entities on the LSR.
.1.3.6.1.2.1.10.166.4.1.2.4.1,MPLS-LDP-STD-MIB::mplsLdpEntityStatsEntry,,not-accessible,,current,,A row in this table contains statistical information about an LDP Entity. Some counters contained in a row are for fatal errors received during a former LDP Session associated with this entry. For example, an LDP PDU received on a TCP connection during an LDP Session contains a fatal error. That error is counted here, because the session is terminated. If the error is NOT fatal (i.e., the Session remains), then the error is counted in the mplsLdpSessionStatsEntry.
.1.3.6.1.2.1.10.166.4.1.2.4.1.1,MPLS-LDP-STD-MIB::mplsLdpEntityStatsSessionAttempts,Counter32,read-only,,current,,A count of the Session Initialization messages which were sent or received by this LDP Entity and were NAK'd. In other words, this counter counts the number of session initializations that failed. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.2,MPLS-LDP-STD-MIB::mplsLdpEntityStatsSessionRejectedNoHelloErrors,Counter32,read-only,,current,,A count of the Session Rejected/No Hello Error Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.3,MPLS-LDP-STD-MIB::mplsLdpEntityStatsSessionRejectedAdErrors,Counter32,read-only,,current,,A count of the Session Rejected/Parameters Advertisement Mode Error Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.4,MPLS-LDP-STD-MIB::mplsLdpEntityStatsSessionRejectedMaxPduErrors,Counter32,read-only,,current,,A count of the Session Rejected/Parameters Max Pdu Length Error Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.5,MPLS-LDP-STD-MIB::mplsLdpEntityStatsSessionRejectedLRErrors,Counter32,read-only,,current,,A count of the Session Rejected/Parameters Label Range Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.6,MPLS-LDP-STD-MIB::mplsLdpEntityStatsBadLdpIdentifierErrors,Counter32,read-only,,current,,This object counts the number of Bad LDP Identifier Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.7,MPLS-LDP-STD-MIB::mplsLdpEntityStatsBadPduLengthErrors,Counter32,read-only,,current,,This object counts the number of Bad PDU Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.8,MPLS-LDP-STD-MIB::mplsLdpEntityStatsBadMessageLengthErrors,Counter32,read-only,,current,,This object counts the number of Bad Message Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.9,MPLS-LDP-STD-MIB::mplsLdpEntityStatsBadTlvLengthErrors,Counter32,read-only,,current,,This object counts the number of Bad TLV Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.10,MPLS-LDP-STD-MIB::mplsLdpEntityStatsMalformedTlvValueErrors,Counter32,read-only,,current,,This object counts the number of Malformed TLV Value Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.11,MPLS-LDP-STD-MIB::mplsLdpEntityStatsKeepAliveTimerExpErrors,Counter32,read-only,,current,,This object counts the number of Session Keep Alive Timer Expired Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.12,MPLS-LDP-STD-MIB::mplsLdpEntityStatsShutdownReceivedNotifications,Counter32,read-only,,current,,This object counts the number of Shutdown Notifications received related to session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.2.4.1.13,MPLS-LDP-STD-MIB::mplsLdpEntityStatsShutdownSentNotifications,Counter32,read-only,,current,,This object counts the number of Shutdown Notfications sent related to session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.3,MPLS-LDP-STD-MIB::mplsLdpSessionObjects,,,,,,
.1.3.6.1.2.1.10.166.4.1.3.1,MPLS-LDP-STD-MIB::mplsLdpPeerLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the most recent addition or deletion to/from the mplsLdpPeerTable/mplsLdpSessionTable.
.1.3.6.1.2.1.10.166.4.1.3.2,MPLS-LDP-STD-MIB::mplsLdpPeerTable,,not-accessible,,current,,Information about LDP peers known by Entities in the mplsLdpEntityTable. The information in this table is based on information from the Entity-Peer interaction during session initialization but is not appropriate for the mplsLdpSessionTable, because objects in this table may or may not be used in session establishment.
.1.3.6.1.2.1.10.166.4.1.3.2.1,MPLS-LDP-STD-MIB::mplsLdpPeerEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId,current,,Information about a single Peer which is related to a Session. This table is augmented by the mplsLdpSessionTable.
.1.3.6.1.2.1.10.166.4.1.3.2.1.1,MPLS-LDP-STD-MIB::mplsLdpPeerLdpId,OCTET,not-accessible,,current,,The LDP identifier of this LDP Peer.
.1.3.6.1.2.1.10.166.4.1.3.2.1.2,MPLS-LDP-STD-MIB::mplsLdpPeerLabelDistMethod,INTEGER,read-only,,current,downstreamOnDemand(1):downstreamUnsolicited(2),For any given LDP session, the method of label distribution must be specified.
.1.3.6.1.2.1.10.166.4.1.3.2.1.3,MPLS-LDP-STD-MIB::mplsLdpPeerPathVectorLimit,Integer32,read-only,,current,,If the value of this object is 0 (zero) then Loop Dection for Path Vectors for this Peer is disabled. Otherwise, if this object has a value greater than zero, then Loop Dection for Path Vectors for this Peer is enabled and the Path Vector Limit is this value.
.1.3.6.1.2.1.10.166.4.1.3.2.1.4,MPLS-LDP-STD-MIB::mplsLdpPeerTransportAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the Internet address for the mplsLdpPeerTransportAddr object. The LDP specification describes this as being either an IPv4 Transport Address or IPv6 Transport Address which is used in opening the LDP session's TCP connection, or if the optional TLV is not present, then this is the IPv4/IPv6 source address for the UPD packet carrying the Hellos. This object specifies how the value of the mplsLdpPeerTransportAddr object should be interpreted.
.1.3.6.1.2.1.10.166.4.1.3.2.1.5,MPLS-LDP-STD-MIB::mplsLdpPeerTransportAddr,OCTET,read-only,,current,,The Internet address advertised by the peer in the Hello Message or the Hello source address. The type of this address is specified by the value of the mplsLdpPeerTransportAddrType object.
.1.3.6.1.2.1.10.166.4.1.3.3,MPLS-LDP-STD-MIB::mplsLdpSessionTable,,not-accessible,,current,,A table of Sessions between the LDP Entities and LDP Peers. This table AUGMENTS the mplsLdpPeerTable. Each row in this table represents a single session.
.1.3.6.1.2.1.10.166.4.1.3.3.1,MPLS-LDP-STD-MIB::mplsLdpSessionEntry,,not-accessible,,current,,An entry in this table represents information on a single session between an LDP Entity and LDP Peer. The information contained in a row is read-only. Please note: the Path Vector Limit for the Session is the value which is configured in the corresponding mplsLdpEntityEntry. The Peer's Path Vector Limit is in the mplsLdpPeerPathVectorLimit object in the mplsLdpPeerTable. Values which may differ from those configured are noted in the objects of this table, the mplsLdpAtmSessionTable and the mplsLdpFrameRelaySessionTable. A value will differ if it was negotiated between the Entity and the Peer. Values may or may not be negotiated. For example, if the values are the same then no negotiation takes place. If they are negotiated, then they may differ.
.1.3.6.1.2.1.10.166.4.1.3.3.1.1,MPLS-LDP-STD-MIB::mplsLdpSessionStateLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this Session entered its current state as denoted by the mplsLdpSessionState object.
.1.3.6.1.2.1.10.166.4.1.3.3.1.2,MPLS-LDP-STD-MIB::mplsLdpSessionState,INTEGER,read-only,,current,nonexistent(1):initialized(2):openrec(3):opensent(4):operational(5),The current state of the session, all of the states 1 to 5 are based on the state machine for session negotiation behavior.
.1.3.6.1.2.1.10.166.4.1.3.3.1.3,MPLS-LDP-STD-MIB::mplsLdpSessionRole,INTEGER,read-only,,current,unknown(1):active(2):passive(3),During session establishment the LSR/LER takes either the active role or the passive role based on address comparisons. This object indicates whether this LSR/LER was behaving in an active role or passive role during this session's establishment. The value of unknown(1), indicates that the role is not able to be determined at the present time.
.1.3.6.1.2.1.10.166.4.1.3.3.1.4,MPLS-LDP-STD-MIB::mplsLdpSessionProtocolVersion,Unsigned32,read-only,,current,,The version of the LDP Protocol which this session is using. This is the version of the LDP protocol which has been negotiated during session initialization.
.1.3.6.1.2.1.10.166.4.1.3.3.1.5,MPLS-LDP-STD-MIB::mplsLdpSessionKeepAliveHoldTimeRem,INTEGER,read-only,,current,,The keep alive hold time remaining for this session.
.1.3.6.1.2.1.10.166.4.1.3.3.1.6,MPLS-LDP-STD-MIB::mplsLdpSessionKeepAliveTime,Unsigned32,read-only,,current,,The negotiated KeepAlive Time which represents the amount of seconds between keep alive messages. The mplsLdpEntityKeepAliveHoldTimer related to this Session is the value that was proposed as the KeepAlive Time for this session. This value is negotiated during session initialization between the entity's proposed value (i.e., the value configured in mplsLdpEntityKeepAliveHoldTimer) and the peer's proposed KeepAlive Hold Timer value. This value is the smaller of the two proposed values.
.1.3.6.1.2.1.10.166.4.1.3.3.1.7,MPLS-LDP-STD-MIB::mplsLdpSessionMaxPduLength,Unsigned32,read-only,,current,,The value of maximum allowable length for LDP PDUs for this session. This value may have been negotiated during the Session Initialization. This object is related to the mplsLdpEntityMaxPduLength object. The mplsLdpEntityMaxPduLength object specifies the requested LDP PDU length, and this object reflects the negotiated LDP PDU length between the Entity and the Peer.
.1.3.6.1.2.1.10.166.4.1.3.3.1.8,MPLS-LDP-STD-MIB::mplsLdpSessionDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this session's counters suffered a discontinuity. The relevant counters are the specific instances associated with this session of any Counter32 object contained in the mplsLdpSessionStatsTable. The initial value of this object is the value of sysUpTime when the entry was created in this table. Also, a command generator can distinguish when a session between a given Entity and Peer goes away and a new session is established. This value would change and thus indicate to the command generator that this is a different session.
.1.3.6.1.2.1.10.166.4.1.3.4,MPLS-LDP-STD-MIB::mplsLdpSessionStatsTable,,not-accessible,,current,,A table of statistics for Sessions between LDP Entities and LDP Peers. This table AUGMENTS the mplsLdpPeerTable.
.1.3.6.1.2.1.10.166.4.1.3.4.1,MPLS-LDP-STD-MIB::mplsLdpSessionStatsEntry,,not-accessible,,current,,An entry in this table represents statistical information on a single session between an LDP Entity and LDP Peer.
.1.3.6.1.2.1.10.166.4.1.3.4.1.1,MPLS-LDP-STD-MIB::mplsLdpSessionStatsUnknownMesTypeErrors,Counter32,read-only,,current,,This object counts the number of Unknown Message Type Errors detected by this LSR/LER during this session. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpSessionDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.3.4.1.2,MPLS-LDP-STD-MIB::mplsLdpSessionStatsUnknownTlvErrors,Counter32,read-only,,current,,This object counts the number of Unknown TLV Errors detected by this LSR/LER during this session. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpSessionDiscontinuityTime.
.1.3.6.1.2.1.10.166.4.1.3.5,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyObjects,,,,,,
.1.3.6.1.2.1.10.166.4.1.3.5.1,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyTable,,not-accessible,,current,,A table of Hello Adjacencies for Sessions.
.1.3.6.1.2.1.10.166.4.1.3.5.1.1,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsLdpHelloAdjacencyIndex,current,,Each row represents a single LDP Hello Adjacency. An LDP Session can have one or more Hello Adjacencies.
.1.3.6.1.2.1.10.166.4.1.3.5.1.1.1,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyIndex,Unsigned32,not-accessible,,current,,An identifier for this specific adjacency.
.1.3.6.1.2.1.10.166.4.1.3.5.1.1.2,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyHoldTimeRem,INTEGER,read-only,,current,,If the value of this object is 65535, this means that the hold time is infinite (i.e., wait forever). Otherwise, the time remaining for this Hello Adjacency to receive its next Hello Message. This interval will change when the 'next' Hello Message which corresponds to this Hello Adjacency is received unless it is infinite.
.1.3.6.1.2.1.10.166.4.1.3.5.1.1.3,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyHoldTime,Unsigned32,read-only,,current,,The Hello hold time which is negotiated between the Entity and the Peer. The entity associated with this Hello Adjacency issues a proposed Hello Hold Time value in the mplsLdpEntityHelloHoldTimer object. The peer also proposes a value and this object represents the negotiated value. A value of 0 means the default, which is 15 seconds for Link Hellos and 45 seconds for Targeted Hellos. A value of 65535 indicates an infinite hold time.
.1.3.6.1.2.1.10.166.4.1.3.5.1.1.4,MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyType,INTEGER,read-only,,current,link(1):targeted(2),This adjacency is the result of a 'link' hello if the value of this object is link(1). Otherwise, it is a result of a 'targeted' hello, targeted(2).
.1.3.6.1.2.1.10.166.4.1.3.6,MPLS-LDP-STD-MIB::mplsInSegmentLdpLspTable,,not-accessible,,current,,A table of LDP LSP's which map to the mplsInSegmentTable in the MPLS-LSR-STD-MIB module.
.1.3.6.1.2.1.10.166.4.1.3.6.1,MPLS-LDP-STD-MIB::mplsInSegmentLdpLspEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsInSegmentLdpLspIndex,current,,An entry in this table represents information on a single LDP LSP which is represented by a session's index triple (mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the index for the mplsInSegmentTable (mplsInSegmentLdpLspLabelIndex) from the MPLS-LSR-STD-MIB. The information contained in a row is read-only.
.1.3.6.1.2.1.10.166.4.1.3.6.1.1,MPLS-LDP-STD-MIB::mplsInSegmentLdpLspIndex,OCTET,not-accessible,,current,,This contains the same value as the mplsInSegmentIndex in the MPLS-LSR-STD-MIB's mplsInSegmentTable.
.1.3.6.1.2.1.10.166.4.1.3.6.1.2,MPLS-LDP-STD-MIB::mplsInSegmentLdpLspLabelType,INTEGER,read-only,,current,generic(1):atm(2):frameRelay(3),The Layer 2 Label Type.
.1.3.6.1.2.1.10.166.4.1.3.6.1.3,MPLS-LDP-STD-MIB::mplsInSegmentLdpLspType,INTEGER,read-only,,current,unknown(1):terminatingLsp(2):originatingLsp(3):crossConnectingLsp(4),The type of LSP connection.
.1.3.6.1.2.1.10.166.4.1.3.7,MPLS-LDP-STD-MIB::mplsOutSegmentLdpLspTable,,not-accessible,,current,,A table of LDP LSP's which map to the mplsOutSegmentTable in the MPLS-LSR-STD-MIB.
.1.3.6.1.2.1.10.166.4.1.3.7.1,MPLS-LDP-STD-MIB::mplsOutSegmentLdpLspEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsOutSegmentLdpLspIndex,current,,An entry in this table represents information on a single LDP LSP which is represented by a session's index triple (mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the index (mplsOutSegmentLdpLspIndex) for the mplsOutSegmentTable. The information contained in a row is read-only.
.1.3.6.1.2.1.10.166.4.1.3.7.1.1,MPLS-LDP-STD-MIB::mplsOutSegmentLdpLspIndex,OCTET,not-accessible,,current,,This contains the same value as the mplsOutSegmentIndex in the MPLS-LSR-STD-MIB's mplsOutSegmentTable.
.1.3.6.1.2.1.10.166.4.1.3.7.1.2,MPLS-LDP-STD-MIB::mplsOutSegmentLdpLspLabelType,INTEGER,read-only,,current,generic(1):atm(2):frameRelay(3),The Layer 2 Label Type.
.1.3.6.1.2.1.10.166.4.1.3.7.1.3,MPLS-LDP-STD-MIB::mplsOutSegmentLdpLspType,INTEGER,read-only,,current,unknown(1):terminatingLsp(2):originatingLsp(3):crossConnectingLsp(4),The type of LSP connection.
.1.3.6.1.2.1.10.166.4.1.3.8,MPLS-LDP-STD-MIB::mplsFecObjects,,,,,,
.1.3.6.1.2.1.10.166.4.1.3.8.1,MPLS-LDP-STD-MIB::mplsFecLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the most recent addition/deletion of an entry to/from the mplsLdpFectTable or the most recent change in values to any objects in the mplsLdpFecTable. If no such changes have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.4.1.3.8.2,MPLS-LDP-STD-MIB::mplsFecIndexNext,Unsigned32,read-only,,current,,This object contains an appropriate value to be used for mplsFecIndex when creating entries in the mplsFecTable. The value 0 indicates that no unassigned entries are available.
.1.3.6.1.2.1.10.166.4.1.3.8.3,MPLS-LDP-STD-MIB::mplsFecTable,,not-accessible,,current,,This table represents the FEC (Forwarding Equivalence Class) Information associated with an LSP.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1,MPLS-LDP-STD-MIB::mplsFecEntry,,not-accessible,mplsFecIndex,current,,Each row represents a single FEC Element.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.1,MPLS-LDP-STD-MIB::mplsFecIndex,Unsigned32,not-accessible,,current,,The index which uniquely identifies this entry.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.2,MPLS-LDP-STD-MIB::mplsFecType,INTEGER,read-create,,current,prefix(1):hostAddress(2),The type of the FEC. If the value of this object is 'prefix(1)' then the FEC type described by this row is an address prefix. If the value of this object is 'hostAddress(2)' then the FEC type described by this row is a host address.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.3,MPLS-LDP-STD-MIB::mplsFecAddrPrefixLength,Unsigned32,read-create,,current,,If the value of the 'mplsFecType' is 'hostAddress(2)' then this object is undefined. If the value of 'mplsFecType' is 'prefix(1)' then the value of this object is the length in bits of the address prefix represented by 'mplsFecAddr', or zero. If the value of this object is zero, this indicates that the prefix matches all addresses. In this case the address prefix MUST also be zero (i.e., 'mplsFecAddr' should have the value of zero.)
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.4,MPLS-LDP-STD-MIB::mplsFecAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The value of this object is the type of the Internet address. The value of this object, decides how the value of the mplsFecAddr object is interpreted.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.5,MPLS-LDP-STD-MIB::mplsFecAddr,OCTET,read-create,,current,,The value of this object is interpreted based on the value of the 'mplsFecAddrType' object. This address is then further interpretted as an being used with the address prefix, or as the host address. This further interpretation is indicated by the 'mplsFecType' object. In other words, the FEC element is populated according to the Prefix FEC Element value encoding, or the Host Address FEC Element encoding.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.6,MPLS-LDP-STD-MIB::mplsFecStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.4.1.3.8.3.1.7,MPLS-LDP-STD-MIB::mplsFecRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. If the value of this object is 'active(1)', then none of the writable objects of this entry can be modified, except to set this object to 'destroy(6)'. NOTE: if this row is being referenced by any entry in the mplsLdpLspFecTable, then a request to destroy this row, will result in an inconsistentValue error.
.1.3.6.1.2.1.10.166.4.1.3.9,MPLS-LDP-STD-MIB::mplsLdpLspFecLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the most recent addition/deletion of an entry to/from the mplsLdpLspFecTable or the most recent change in values to any objects in the mplsLdpLspFecTable. If no such changes have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.4.1.3.10,MPLS-LDP-STD-MIB::mplsLdpLspFecTable,,not-accessible,,current,,A table which shows the relationship between LDP LSPs and FECs. Each row represents a single LDP LSP to FEC association.
.1.3.6.1.2.1.10.166.4.1.3.10.1,MPLS-LDP-STD-MIB::mplsLdpLspFecEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsLdpLspFecSegment:mplsLdpLspFecSegmentIndex:mplsLdpLspFecIndex,current,,An entry represents a LDP LSP to FEC association.
.1.3.6.1.2.1.10.166.4.1.3.10.1.1,MPLS-LDP-STD-MIB::mplsLdpLspFecSegment,INTEGER,not-accessible,,current,inSegment(1):outSegment(2),If the value is inSegment(1), then this indicates that the following index, mplsLdpLspFecSegmentIndex, contains the same value as the mplsInSegmentLdpLspIndex. Otherwise, if the value of this object is outSegment(2), then this indicates that following index, mplsLdpLspFecSegmentIndex, contains the same value as the mplsOutSegmentLdpLspIndex.
.1.3.6.1.2.1.10.166.4.1.3.10.1.2,MPLS-LDP-STD-MIB::mplsLdpLspFecSegmentIndex,OCTET,not-accessible,,current,,This index is interpretted by using the value of the mplsLdpLspFecSegment. If the mplsLdpLspFecSegment is inSegment(1), then this index has the same value as mplsInSegmentLdpLspIndex. If the mplsLdpLspFecSegment is outSegment(2), then this index has the same value as mplsOutSegmentLdpLspIndex.
.1.3.6.1.2.1.10.166.4.1.3.10.1.3,MPLS-LDP-STD-MIB::mplsLdpLspFecIndex,Unsigned32,not-accessible,,current,,This index identifies the FEC entry in the mplsFecTable associated with this session. In other words, the value of this index is the same as the value of the mplsFecIndex that denotes the FEC associated with this Session.
.1.3.6.1.2.1.10.166.4.1.3.10.1.4,MPLS-LDP-STD-MIB::mplsLdpLspFecStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.4.1.3.10.1.5,MPLS-LDP-STD-MIB::mplsLdpLspFecRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. If the value of this object is 'active(1)', then none of the writable objects of this entry can be modified. The Agent should delete this row when the session ceases to exist. If an operator wants to associate the session with a different FEC, the recommended procedure is (as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in theclause of the mplsLdpEntityAdminStatus object) is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. This will also cause this entry to be deleted. Then, set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated. Once the session is initiated, an entry may be added to this table to associate the new session with a FEC.
.1.3.6.1.2.1.10.166.4.1.3.11,MPLS-LDP-STD-MIB::mplsLdpSessionPeerAddrTable,,not-accessible,,current,,This table 'extends' the mplsLdpSessionTable. This table is used to store Label Address Information from Label Address Messages received by this LSR from Peers. This table is read-only and should be updated when Label Withdraw Address Messages are received, i.e., Rows should be deleted as appropriate. NOTE: since more than one address may be contained in a Label Address Message, this table 'sparse augments', the mplsLdpSessionTable's information.
.1.3.6.1.2.1.10.166.4.1.3.11.1,MPLS-LDP-STD-MIB::mplsLdpSessionPeerAddrEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsLdpSessionPeerAddrIndex,current,,An entry in this table represents information on a session's single next hop address which was advertised in an Address Message from the LDP peer. The information contained in a row is read-only.
.1.3.6.1.2.1.10.166.4.1.3.11.1.1,MPLS-LDP-STD-MIB::mplsLdpSessionPeerAddrIndex,Unsigned32,not-accessible,,current,,An index which uniquely identifies this entry within a given session.
.1.3.6.1.2.1.10.166.4.1.3.11.1.2,MPLS-LDP-STD-MIB::mplsLdpSessionPeerNextHopAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The internetwork layer address type of this Next Hop Address as specified in the Label Address Message associated with this Session. The value of this object indicates how to interpret the value of mplsLdpSessionPeerNextHopAddr.
.1.3.6.1.2.1.10.166.4.1.3.11.1.3,MPLS-LDP-STD-MIB::mplsLdpSessionPeerNextHopAddr,OCTET,read-only,,current,,The next hop address. The type of this address is specified by the value of the mplsLdpSessionPeerNextHopAddrType.
.1.3.6.1.2.1.10.166.4.2,MPLS-LDP-STD-MIB::mplsLdpConformance,,,,,,
.1.3.6.1.2.1.10.166.4.2.1,MPLS-LDP-STD-MIB::mplsLdpGroups,,,,,,
.1.3.6.1.2.1.10.166.4.2.1.1,MPLS-LDP-STD-MIB::mplsLdpGeneralGroup,,,,,,Objects that apply to all MPLS LDP implementations.
.1.3.6.1.2.1.10.166.4.2.1.2,MPLS-LDP-STD-MIB::mplsLdpLspGroup,,,,,,These objects are for LDP implementations which interface to the Label Information Base (LIB) in the MPLS-LSR-STD-MIB. The LIB is represented in the mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable.
.1.3.6.1.2.1.10.166.4.2.1.3,MPLS-LDP-STD-MIB::mplsLdpNotificationsGroup,,,,,,The notification for an MPLS LDP implementation.
.1.3.6.1.2.1.10.166.4.2.2,MPLS-LDP-STD-MIB::mplsLdpCompliances,,,,,,
.1.3.6.1.2.1.10.166.4.2.2.1,MPLS-LDP-STD-MIB::mplsLdpModuleFullCompliance,,,,,,The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.4.2.2.2,MPLS-LDP-STD-MIB::mplsLdpModuleReadOnlyCompliance,,,,,,The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.5,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmStdMIB,,,,,,Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing Asynchronous Transfer Mode (ATM) as the Layer 2 media.
.1.3.6.1.2.1.10.166.5.1,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmObjects,,,,,,
.1.3.6.1.2.1.10.166.5.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmObjects,,,,,,
.1.3.6.1.2.1.10.166.5.1.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmTable,,not-accessible,,current,,This table contains ATM specific information which could be used in the 'Optional Parameters' and other ATM specific information. This table 'sparse augments' the mplsLdpEntityTable when ATM is the Layer 2 medium.
.1.3.6.1.2.1.10.166.5.1.1.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex,current,,An entry in this table represents the ATM parameters and ATM information for this LDP entity.
.1.3.6.1.2.1.10.166.5.1.1.1.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmIfIndexOrZero,Integer32,read-create,,current,,This value represents either the InterfaceIndex or 0 (zero). The value of zero means that the InterfaceIndex is not known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex. If an ATM Label is being used in forwarding data, then the value of this object MUST be the InterfaceIndex.
.1.3.6.1.2.1.10.166.5.1.1.1.1.2,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmMergeCap,INTEGER,read-create,,current,notSupported(0):vpMerge(1):vcMerge(2):vpAndVcMerge(3),Denotes the Merge Capability of this Entity. This is the EXACT value for the ATM Session Parameter, field M (for ATM Merge Capabilities). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate. - The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.5.1.1.1.1.3,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRComponents,Unsigned32,read-only,,current,,Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityAtmLRTable which correspond to this entry. This is the EXACT value for the ATM Session Parameter, field N (for Number of label range components). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'N, Number of label range components Specifies the number of ATM Label Range Components included in the TLV.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.5.1.1.1.1.4,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmVcDirectionality,INTEGER,read-create,,current,bidirectional(0):unidirectional(1),If the value of this object is 'bidirectional(0)', a given VCI, within a given VPI, is used as a label for both directions independently. If the value of this object is 'unidirectional(1)', a given VCI within a VPI designates one direction. This is the EXACT value for the ATM Session Parameter, field D (for VC Directionality). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can (within a given VPI) support the use of a given VCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning (within a given VPI) a given VCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered VCIs in the VPI/VCI range as labels. The system with the smaller LDP Identifier may assign only even-numbered VCIs in the VPI/VCI range as labels.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.5.1.1.1.1.5,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLsrConnectivity,INTEGER,read-create,,current,direct(1):indirect(2),The peer LSR may be connected indirectly by means of an ATM VP so that the VPI values may be different on either endpoint so the label MUST be encoded entirely within the VCI field.
.1.3.6.1.2.1.10.166.5.1.1.1.1.6,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmDefaultControlVpi,INTEGER,read-create,,current,,The default VPI value for the non-MPLS connection. The default value of this is 0 (zero) but other values may be configured. This object allows a different value to be configured.
.1.3.6.1.2.1.10.166.5.1.1.1.1.7,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmDefaultControlVci,Integer32,read-create,,current,,The Default VCI value for a non-MPLS connection. The default value of this is 32 but other values may be configured. This object allows a different value to be configured.
.1.3.6.1.2.1.10.166.5.1.1.1.1.8,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmUnlabTrafVpi,INTEGER,read-create,,current,,VPI value of the VCC supporting unlabeled traffic. This non-MPLS connection is used to carry unlabeled (IP) packets. The default value is the same as the default value of the 'mplsLdpEntityAtmDefaultControlVpi', however another value may be configured.
.1.3.6.1.2.1.10.166.5.1.1.1.1.9,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmUnlabTrafVci,Integer32,read-create,,current,,VCI value of the VCC supporting unlabeled traffic. This non-MPLS connection is used to carry unlabeled (IP) packets. The default value is the same as the default value of the 'mplsLdpEntityAtmDefaultControlVci', however another value may be configured.
.1.3.6.1.2.1.10.166.5.1.1.1.1.10,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.5.1.1.1.1.11,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in theclause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated.
.1.3.6.1.2.1.10.166.5.1.1.2,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRTable,,not-accessible,,current,,The MPLS LDP Entity ATM Label Range (LR) Table. The purpose of this table is to provide a mechanism for configuring a contiguous range of vpi's with a contiguous range of vci's, or a 'label range' for LDP Entities. LDP Entities which use ATM must have at least one entry in this table. There must exist at least one entry in this table for every LDP Entity that has 'mplsLdpEntityOptionalParameters' object with a value of 'atmSessionParameters'.
.1.3.6.1.2.1.10.166.5.1.1.2.1,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLREntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpEntityAtmLRMinVpi:mplsLdpEntityAtmLRMinVci,current,,A row in the LDP Entity ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. For example, for a specific LDP Entity index, there could be one entry having LowerBound vpi/vci == 0/32, and UpperBound vpi/vci == 0/100, and a second entry for this same interface with LowerBound vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. However, there could not be a third entry with LowerBound vpi/vci == 0/200 and UpperBound vpi/vci == 0/300 because this label range overlaps with the second entry (i.e., both entries now have 0/200). A row will not become active unless a unique and non-overlapping range is specified. At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table. A request to create a row with an overlapping range should result in an inconsistentValue error.
.1.3.6.1.2.1.10.166.5.1.1.2.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRMinVpi,INTEGER,not-accessible,,current,,The minimum VPI number configured for this range. The value of zero is a valid value for the VPI portion of the label.
.1.3.6.1.2.1.10.166.5.1.1.2.1.2,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRMinVci,Integer32,not-accessible,,current,,The minimum VCI number configured for this range.
.1.3.6.1.2.1.10.166.5.1.1.2.1.3,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRMaxVpi,INTEGER,read-create,,current,,The maximum VPI number configured for this range.
.1.3.6.1.2.1.10.166.5.1.1.2.1.4,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRMaxVci,Integer32,read-create,,current,,The maximum VCI number configured for this range.
.1.3.6.1.2.1.10.166.5.1.1.2.1.5,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.5.1.1.2.1.6,MPLS-LDP-ATM-STD-MIB::mplsLdpEntityAtmLRRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in theclause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated.
.1.3.6.1.2.1.10.166.5.1.2,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmSessionObjects,,,,,,
.1.3.6.1.2.1.10.166.5.1.2.1,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmSessionTable,,not-accessible,,current,,A table which relates sessions in the 'mplsLdpSessionTable' and their label range intersections. There could be one or more label range intersections between an LDP Entity and LDP Peer using ATM as the underlying media. Each row represents a single label range intersection. This table cannot use the 'AUGMENTS' clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable.
.1.3.6.1.2.1.10.166.5.1.2.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmSessionEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsLdpSessionAtmLRLowerBoundVpi:mplsLdpSessionAtmLRLowerBoundVci,current,,An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer. The information contained in a row is read-only.
.1.3.6.1.2.1.10.166.5.1.2.1.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpSessionAtmLRLowerBoundVpi,INTEGER,not-accessible,,current,,The minimum VPI number for this range.
.1.3.6.1.2.1.10.166.5.1.2.1.1.2,MPLS-LDP-ATM-STD-MIB::mplsLdpSessionAtmLRLowerBoundVci,Integer32,not-accessible,,current,,The minimum VCI number for this range.
.1.3.6.1.2.1.10.166.5.1.2.1.1.3,MPLS-LDP-ATM-STD-MIB::mplsLdpSessionAtmLRUpperBoundVpi,INTEGER,read-only,,current,,The maximum VPI number for this range.
.1.3.6.1.2.1.10.166.5.1.2.1.1.4,MPLS-LDP-ATM-STD-MIB::mplsLdpSessionAtmLRUpperBoundVci,Integer32,read-only,,current,,The maximum VCI number for this range.
.1.3.6.1.2.1.10.166.5.2,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmConformance,,,,,,
.1.3.6.1.2.1.10.166.5.2.1,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmGroups,,,,,,
.1.3.6.1.2.1.10.166.5.2.1.1,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmGroup,,,,,,Objects that apply to all MPLS LDP implementations using ATM as the Layer 2.
.1.3.6.1.2.1.10.166.5.2.2,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmCompliances,,,,,,
.1.3.6.1.2.1.10.166.5.2.2.1,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmModuleFullCompliance,,,,,,The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.5.2.2.2,MPLS-LDP-ATM-STD-MIB::mplsLdpAtmModuleReadOnlyCompliance,,,,,,The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.6,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayStdMIB,,,,,,Copyright (C) The Internet Society (year). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing Frame Relay as the Layer 2 media.
.1.3.6.1.2.1.10.166.6.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayObjects,,,,,,
.1.3.6.1.2.1.10.166.6.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayObjects,,,,,,
.1.3.6.1.2.1.10.166.6.1.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayTable,,not-accessible,,current,,This table contains Frame Relay specific information which could be used in the 'Optional Parameters' and other Frame Relay specific information. This table 'sparse augments' the mplsLdpEntityTable when Frame Relay is the Layer 2 medium.
.1.3.6.1.2.1.10.166.6.1.1.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex,current,,An entry in this table represents the Frame Relay optional parameters associated with the LDP entity.
.1.3.6.1.2.1.10.166.6.1.1.1.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayIfIndexOrZero,Integer32,read-create,,current,,This value represents either the InterfaceIndex of the 'ifLayer' where the Frame Relay Labels 'owned' by this entry were created, or 0 (zero). The value of zero means that the InterfaceIndex is not known. For example, if the InterfaceIndex is created subsequent to the Frame Relay Label's creation, then it would not be known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex. If an Frame Relay Label is being used in forwarding data, then the value of this object MUST be the InterfaceIndex.
.1.3.6.1.2.1.10.166.6.1.1.1.1.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayMergeCap,INTEGER,read-create,,current,notSupported(0):supported(1),This represents whether or not the Frame Relay merge capability is supported. This is the EXACT value for the Frame Relay Session Parameter, field M (for Frame Relay Merge Capabilities). The Frame Relay Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, Frame Relay Merge Capabilities Specifies the merge capabilities of a Frame Relay switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 Merge supported Non-merge and merge Frame Relay LSRs may freely interoperate.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.6.1.1.1.1.3,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRComponents,Unsigned32,read-only,,current,,Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityFrameRelayLRTable which correspond to this entry. This is the EXACT value for the Frame Relay Session Parameter, field N (for Number of label range components). The Frame Relay Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'N, Number of label range components Specifies the number of Frame Relay Label Range Components included in the TLV.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.6.1.1.1.1.4,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayVcDirectionality,INTEGER,read-create,,current,bidirectional(0):unidirection(1),If the value of this object is 'bidirectional(0)', then the LSR supports the use of a given DLCI as a label for both directions independently. If the value of this object is 'unidirectional(1)', then the LSR uses the given DLCI as a label in only one direction. This is the EXACT value for the Frame Relay Session Parameter, field D (for VC Directionality). The Frame Relay Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can support the use of a given DLCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning a given DLCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered DLCIs in the range as labels. The system with the smaller LDP Identifier may assign only even-numbered DLCIs in the range as labels.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.6.1.1.1.1.5,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.6.1.1.1.1.6,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in theclause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated.
.1.3.6.1.2.1.10.166.6.1.1.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRTable,,not-accessible,,current,,This table contains information about the Optional Parameters for the Frame Relay Session in the LDP Initialization Message, specifically it contains information about the Frame Relay Label Range Components. If the value of the object 'mplsLdpEntityOptionalParameters' contains the value of 'frameRelaySessionParameters(3)' then there must be at least one corresponding entry in this table.
.1.3.6.1.2.1.10.166.6.1.1.2.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLREntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpEntityFrameRelayLRMinDlci,current,,An entry in this table represents the Frame Relay Label Range Component associated with the LDP entity.
.1.3.6.1.2.1.10.166.6.1.1.2.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRMinDlci,Integer32,not-accessible,,current,,The lower bound which is supported. This value should be the same as that in the Frame Relay Label Range Component's Minimum DLCI field. The value of zero is valid for the minimum DLCI field of the label.
.1.3.6.1.2.1.10.166.6.1.1.2.1.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRMaxDlci,Integer32,read-create,,current,,The upper bound which is supported. This value should be the same as that in the Frame Relay Label Range Component's Maximum DLCI field.
.1.3.6.1.2.1.10.166.6.1.1.2.1.3,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRLen,INTEGER,read-create,,current,tenDlciBits(0):twentyThreeDlciBits(2),This object specifies the length of the DLCI bits. This is the EXACT value for the Len field of the Frame Relay Label Range Component. The description from rfc3036.txt is: 'Len This field specifies the number of bits of the DLCI. The following values are supported: Len DLCI bits 0 10 2 23 Len values 1 and 3 are reserved.' Please refer to the following reference for a complete description of this feature.
.1.3.6.1.2.1.10.166.6.1.1.2.1.4,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.6.1.1.2.1.5,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpEntityFrameRelayLRRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in theclause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated.
.1.3.6.1.2.1.10.166.6.1.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelaySessionObjects,,,,,,
.1.3.6.1.2.1.10.166.6.1.2.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelaySessionTable,,not-accessible,,current,,A table of Frame Relay label range intersections between the LDP Entities and LDP Peers. Each row represents a single label range intersection. NOTE: this table cannot use the 'AUGMENTS' clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable.
.1.3.6.1.2.1.10.166.6.1.2.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelaySessionEntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpPeerLdpId:mplsLdpFrameRelaySessionMinDlci,current,,An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer. The information contained in a row is read-only.
.1.3.6.1.2.1.10.166.6.1.2.1.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelaySessionMinDlci,Integer32,not-accessible,,current,,The lower bound of DLCIs which are supported. The value of zero is a valid value for the minimum DLCI field of the label.
.1.3.6.1.2.1.10.166.6.1.2.1.1.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelaySessionMaxDlci,Integer32,read-only,,current,,The upper bound of DLCIs which are supported.
.1.3.6.1.2.1.10.166.6.1.2.1.1.3,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelaySessionLen,INTEGER,read-only,,current,tenDlciBits(0):twentyThreeDlciBits(2),This object specifies the DLCI bits.
.1.3.6.1.2.1.10.166.6.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayConformance,,,,,,
.1.3.6.1.2.1.10.166.6.2.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayGroups,,,,,,
.1.3.6.1.2.1.10.166.6.2.1.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayGroup,,,,,,Objects that apply to all MPLS LDP implementations using Frame Relay as the Layer 2.
.1.3.6.1.2.1.10.166.6.2.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayCompliances,,,,,,
.1.3.6.1.2.1.10.166.6.2.2.1,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayModuleFullCompliance,,,,,,The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.6.2.2.2,MPLS-LDP-FRAME-RELAY-STD-MIB::mplsLdpFrameRelayModuleReadOnlyCompliance,,,,,,The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.7,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericStdMIB,,,,,,Copyright (C) The Internet Society (year). The initial version of this MIB module was published in RFC 3815. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing ethernet as the Layer 2 media.
.1.3.6.1.2.1.10.166.7.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericObjects,,,,,,
.1.3.6.1.2.1.10.166.7.1.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericObjects,,,,,,
.1.3.6.1.2.1.10.166.7.1.1.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLRTable,,not-accessible,,current,,The MPLS LDP Entity Generic Label Range (LR) Table. The purpose of this table is to provide a mechanism for configurating a contiguous range of generic labels, or a 'label range' for LDP Entities. LDP Entities which use Generic Labels must have at least one entry in this table. In other words, this table 'extends' the mpldLdpEntityTable for Generic Labels.
.1.3.6.1.2.1.10.166.7.1.1.1.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLREntry,,not-accessible,mplsLdpEntityLdpId:mplsLdpEntityIndex:mplsLdpEntityGenericLRMin:mplsLdpEntityGenericLRMax,current,,A row in the LDP Entity Generic Label Range (LR) Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds pairs. NOTE: there is NO corresponding LDP message which relates to the information in this table, however, this table does provide a way for a user to 'reserve' a generic label range. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. A row will not be created unless a unique and non-overlapping range is specified.
.1.3.6.1.2.1.10.166.7.1.1.1.1.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLRMin,Unsigned32,not-accessible,,current,,The minimum label configured for this range.
.1.3.6.1.2.1.10.166.7.1.1.1.1.2,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLRMax,Unsigned32,not-accessible,,current,,The maximum label configured for this range.
.1.3.6.1.2.1.10.166.7.1.1.1.1.3,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLabelSpace,INTEGER,read-create,,current,perPlatform(1):perInterface(2),This value of this object is perPlatform(1), then this means that the label space type is per platform. If this object is perInterface(2), then this means that the label space type is per Interface.
.1.3.6.1.2.1.10.166.7.1.1.1.1.4,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericIfIndexOrZero,Integer32,read-create,,current,,This value represents either the InterfaceIndex of the 'ifLayer' where these Generic Label would be created, or 0 (zero). The value of zero means that the InterfaceIndex is not known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex.
.1.3.6.1.2.1.10.166.7.1.1.1.1.5,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLRStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.7.1.1.1.1.6,MPLS-LDP-GENERIC-STD-MIB::mplsLdpEntityGenericLRRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in theclause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic. To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, then set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated. There must exist at least one entry in this table for every LDP Entity that has a generic label configured.
.1.3.6.1.2.1.10.166.7.2,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericConformance,,,,,,
.1.3.6.1.2.1.10.166.7.2.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericGroups,,,,,,
.1.3.6.1.2.1.10.166.7.2.1.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericGroup,,,,,,Objects that apply to all MPLS LDP implementations using Generic Labels as the Layer 2.
.1.3.6.1.2.1.10.166.7.2.2,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericCompliances,,,,,,
.1.3.6.1.2.1.10.166.7.2.2.1,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericModuleFullCompliance,,,,,,The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.7.2.2.2,MPLS-LDP-GENERIC-STD-MIB::mplsLdpGenericModuleReadOnlyCompliance,,,,,,The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.10.166.8,MPLS-FTN-STD-MIB::mplsFTNStdMIB,,,,,,Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3814. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html This MIB module contains managed object definitions for specifying FEC to NHLFE (FTN) mappings and corresponding performance for MPLS.
.1.3.6.1.2.1.10.166.8.0,MPLS-FTN-STD-MIB::mplsFTNNotifications,,,,,,
.1.3.6.1.2.1.10.166.8.1,MPLS-FTN-STD-MIB::mplsFTNObjects,,,,,,
.1.3.6.1.2.1.10.166.8.1.1,MPLS-FTN-STD-MIB::mplsFTNIndexNext,Unsigned32,read-only,,current,,This object contains the next available valid value to be used for mplsFTNIndex when creating entries in the mplsFTNTable. When creating a new conceptual row (configuration entry) in mplsFTNTable with an SNMP SET operation the command generator (Network Management Application) must first issue a management protocol retrieval operation to obtain the current value of this object. If the command responder (agent) does not wish to allow creation of more entries in mplsFTNTable, possibly because of resource exhaustion, this object MUST return a value of 0. If a non-zero value is returned the Network Management Application must determine whether the value is indeed still unused since two Network Management Applications may attempt to create a row simultaneously and use the same value. If it is currently unused and the SET succeeds, the agent MUST change the value of this object to a currently unused non-zero value (according to an implementation specific algorithm) or zero (if no further row creation will be permitted). If the value is in use, however, the SET fails and the Network Management Application must then reread this object to obtain a new usable value.
.1.3.6.1.2.1.10.166.8.1.2,MPLS-FTN-STD-MIB::mplsFTNTableLastChanged,TimeTicks,read-only,,current,,Indicates the last time an entry was added, deleted or modified in mplsFTNTable. Management stations should consult this object to determine if mplsFTNTable requires their attention. This object is particularly useful for applications performing a retrieval on mplsFTNTable to ensure that the table is not modified during the retrieval operation.
.1.3.6.1.2.1.10.166.8.1.3,MPLS-FTN-STD-MIB::mplsFTNTable,,not-accessible,,current,,This table contains the currently defined FTN entries. This table allows FEC to NHLFE mappings to be specified. Each entry in this table defines a rule to be applied to incoming packets (on interfaces that the FTN entry is activated on using mplsFTNMapTable) and an action to be taken on matching packets (mplsFTNActionPointer). This table supports 6-tuple matching rules based on one or more of source address range, destination address range, source port range, destination port range, IPv4 Protocol field or IPv6 next-header field and the DiffServ Code Point (DSCP) to be specified. The action pointer points either to instance of mplsXCEntry in MPLS-LSR-STD-MIB when the NHLFE is a non- TE LSP, or to an instance of mplsTunnelEntry in the MPLS-TE-STD-MIB when the NHLFE is an originating TE tunnel.
.1.3.6.1.2.1.10.166.8.1.3.1,MPLS-FTN-STD-MIB::mplsFTNEntry,,not-accessible,mplsFTNIndex,current,,Each entry represents one FTN entry which defines a rule to compare incoming packets with and an action to be taken on matching packets.
.1.3.6.1.2.1.10.166.8.1.3.1.1,MPLS-FTN-STD-MIB::mplsFTNIndex,Unsigned32,not-accessible,,current,,This is the unique index for a conceptual row in mplsFTNTable. To create a new conceptual row in mplsFTNTable a Network Management Application SHOULD retrieve the current value of mplsFTNIndexNext to determine the next valid available value of mplsFTNIndex.
.1.3.6.1.2.1.10.166.8.1.3.1.2,MPLS-FTN-STD-MIB::mplsFTNRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used for controlling the creation and deletion of this row. All writeable objects in this row may be modified at any time. If a Network Management Application attempts to delete a conceptual row by setting this object to 'destroy' and there are one or more entries in mplsFTNMapTable pointing to the row (i.e., when mplsFTNIndex of the conceptual row being deleted is equal to mplsFTNMapCurrIndex for one or more entries in mplsFTNMapTable), the agent MUST also destroy the corresponding entries in mplsFTNMapTable.
.1.3.6.1.2.1.10.166.8.1.3.1.3,MPLS-FTN-STD-MIB::mplsFTNDescr,OCTET,read-create,,current,,The description of this FTN entry. Since the index for this table has no particular significance or meaning, this object should contain some meaningful text that an operator could use to further distinguish entries in this table.
.1.3.6.1.2.1.10.166.8.1.3.1.4,MPLS-FTN-STD-MIB::mplsFTNMask,BITS,read-create,,current,sourceAddr(0):destAddr(1):sourcePort(2):destPort(3):protocol(4):dscp(5),This bit map indicates which of the fields described next, namely source address range, destination address range, source port range, destination port range, IPv4 Protocol field or IPv6 next-header field and Differentiated Services Code Point (DSCP) is active for this FTN entry. If a particular bit is set to zero then the corresponding field in the packet MUST be ignored for comparison purposes.
.1.3.6.1.2.1.10.166.8.1.3.1.5,MPLS-FTN-STD-MIB::mplsFTNAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object determines the type of address contained in the source and destination address objects (mplsFTNSourceAddrMin, mplsFTNSourceAddrMax, mplsFTNDestAddrMin and mplsFTNDestAddrMax) of a conceptual row. This object MUST NOT be set to unknown(0) when mplsFTNMask has bit positions sourceAddr(0) or destAddr(1) set to one. When both these bit positions of mplsFTNMask are set to zero the value of mplsFTNAddrType SHOULD be set to unknown(0) and the corresponding source and destination address objects SHOULD be set to zero-length strings.
.1.3.6.1.2.1.10.166.8.1.3.1.6,MPLS-FTN-STD-MIB::mplsFTNSourceAddrMin,OCTET,read-create,,current,,The lower end of the source address range. The type of this object is determined by the corresponding mplsFTNAddrType object.
.1.3.6.1.2.1.10.166.8.1.3.1.7,MPLS-FTN-STD-MIB::mplsFTNSourceAddrMax,OCTET,read-create,,current,,The upper end of the source address range. The type of this object is determined by the corresponding mplsFTNAddrType object.
.1.3.6.1.2.1.10.166.8.1.3.1.8,MPLS-FTN-STD-MIB::mplsFTNDestAddrMin,OCTET,read-create,,current,,The lower end of the destination address range. The type of this object is determined by the corresponding mplsFTNAddrType object.
.1.3.6.1.2.1.10.166.8.1.3.1.9,MPLS-FTN-STD-MIB::mplsFTNDestAddrMax,OCTET,read-create,,current,,The higher end of the destination address range. The type of this object is determined by the corresponding mplsFTNAddrType object.
.1.3.6.1.2.1.10.166.8.1.3.1.10,MPLS-FTN-STD-MIB::mplsFTNSourcePortMin,Unsigned32,read-create,,current,,The lower end of the source port range.
.1.3.6.1.2.1.10.166.8.1.3.1.11,MPLS-FTN-STD-MIB::mplsFTNSourcePortMax,Unsigned32,read-create,,current,,The higher end of the source port range 
.1.3.6.1.2.1.10.166.8.1.3.1.12,MPLS-FTN-STD-MIB::mplsFTNDestPortMin,Unsigned32,read-create,,current,,The lower end of the destination port range.
.1.3.6.1.2.1.10.166.8.1.3.1.13,MPLS-FTN-STD-MIB::mplsFTNDestPortMax,Unsigned32,read-create,,current,,The higher end of the destination port range.
.1.3.6.1.2.1.10.166.8.1.3.1.14,MPLS-FTN-STD-MIB::mplsFTNProtocol,Integer32,read-create,,current,,The IP protocol to match against the IPv4 protocol number or IPv6 Next-Header number in the packet. A value of 255 means match all. Note that the protocol number of 255 is reserved by IANA, and Next-Header number of 0 is used in IPv6.
.1.3.6.1.2.1.10.166.8.1.3.1.15,MPLS-FTN-STD-MIB::mplsFTNDscp,Integer32,read-create,,current,,The contents of the DSCP field.
.1.3.6.1.2.1.10.166.8.1.3.1.16,MPLS-FTN-STD-MIB::mplsFTNActionType,INTEGER,read-create,,current,redirectLsp(1):redirectTunnel(2),The type of action to be taken on packets matching this FTN entry.
.1.3.6.1.2.1.10.166.8.1.3.1.17,MPLS-FTN-STD-MIB::mplsFTNActionPointer,OBJECT,read-create,,current,,If mplsFTNActionType is redirectLsp(1), then this object MUST contain zeroDotZero or point to a instance of mplsXCEntry indicating the LSP to redirect matching packets to. If mplsFTNActionType is redirectTunnel(2), then this object MUST contain zeroDotZero or point to a instance of mplsTunnelEntry indicating the MPLS TE tunnel to redirect matching packets to. If this object points to a conceptual row instance in a table consistent with mplsFTNActionType but this instance does not currently exist then no action will be taken on packets matching such an FTN entry till this instance comes into existence. If this object contains zeroDotZero then no action will be taken on packets matching such an FTN entry till it is populated with a valid pointer consistent with the value of mplsFTNActionType as explained above.
.1.3.6.1.2.1.10.166.8.1.3.1.18,MPLS-FTN-STD-MIB::mplsFTNStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this FTN entry. Conceptual rows having the value 'permanent' need not allow write- access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.8.1.4,MPLS-FTN-STD-MIB::mplsFTNMapTableLastChanged,TimeTicks,read-only,,current,,Indicates the last time an entry was added, deleted or modified in mplsFTNMapTable. Management stations should consult this object to determine if the table requires their attention. This object is particularly useful for applications performing a retrieval on mplsFTNMapTable to ensure that the table is not modified during the retrieval operation.
.1.3.6.1.2.1.10.166.8.1.5,MPLS-FTN-STD-MIB::mplsFTNMapTable,,not-accessible,,current,,This table contains objects which provide the capability to apply or map FTN rules as defined by entries in mplsFTNTable to specific interfaces in the system. FTN rules are compared with incoming packets in the order in which they are applied on an interface. The indexing structure of mplsFTNMapTable is as follows. - mplsFTNMapIndex indicates the interface to which the rule is being applied. A value of 0 represents the application of the rule to all interfaces. - mplsFTNMapPrevIndex specifies the rule on the interface prior to the one being applied. A value of 0 specifies that the rule is being inserted at the head of the list of rules currently applied to the interface. - mplsFTNMapCurrIndex is the index in mplsFTNTable corresponding to the rule being applied. This indexing structure makes the entries in the table behave like items in a linked-list. The object mplsFTNMapPrevIndex in each conceptual row is a pointer to the previous entry that is applied to a particular interface. This allows a new entry to be 'inserted' at an arbitrary position in a list of entries currently applied to an interface. This object is self- adjusting, i.e., its value is automatically adjusted by the agent, if necessary, after an insertion or deletion operation. Using this linked-list structure, one can retrieve FTN entries in the order of application on a per-interface basis as follows: - To determine the first FTN entry on an interface with index ifIndex perform a GETNEXT retrieval operation on mplsFTNMapRowStatus.ifIndex.0.0; the returned object, if one exists, is (say) mplsFTNMapRowStatus.ifIndex.0.n (mplsFTNMapRowStatus is the first accessible columnar object in the conceptual row). Then the index of the first FTN entry applied on this interface is n. - To determine the FTN entry applied to an interface after the one indexed by n perform a GETNEXT retrieval operation on mplsFTNMapRowStatus.ifIndex.n.0. If such an entry exists the returned object would be of the form mplsFTNMapRowStatus.ifIndex.n.m. Then the index of the next FTN entry applied on this interface is m. - If the FTN entry indexed by n is the last entry applied to the interface with index ifIndex then the object returned would either be: 1.mplsFTNMapRowStatus.ifIndexNext.0.k, where ifIndexNext is the index of the next interface in ifTable to which an FTN entry has been applied, in which case k is the index of the first FTN entry applied to the interface with index ifIndexNext; or: 2.mplsFTNMapStorageType.firstIfIndex.0.p, if there are no more entries in mplsFTNMapTable, where firstIfIndex is the first entry in ifTable to which an FTN entry has been mapped. Use the above steps to retrieve all the applied FTN entries on a per-interface basis in application order. Note that the number of retrieval operations is the same as the number of applied FTN entries (i.e., the minimum number of GETNEXT operations needed using any indexing scheme). Agents MUST NOT allow the same FTN entry as specified by mplsFTNMapCurrIndex to be applied multiple times to the same interface. Agents MUST NOT allow the creation of rows in this table until the corresponding rows are created in the mplsFTNTable. If a row in mplsFTNTable is destroyed, the agent MUST destroy the corresponding entries (i.e., ones with a matching value of mplsFTNCurrIndex) in this table as well.
.1.3.6.1.2.1.10.166.8.1.5.1,MPLS-FTN-STD-MIB::mplsFTNMapEntry,,not-accessible,mplsFTNMapIndex:mplsFTNMapPrevIndex:mplsFTNMapCurrIndex,current,,Each conceptual row represents the application of an FTN rule at a specific position in the list of FTN rules applied on an interface. 
.1.3.6.1.2.1.10.166.8.1.5.1.1,MPLS-FTN-STD-MIB::mplsFTNMapIndex,Integer32,not-accessible,,current,,The interface index that this FTN entry is being applied to. A value of zero indicates an entry that is applied all interfaces. Entries mapped to an interface by specifying its (non- zero) interface index in mplsFTNMapIndex are applied ahead of entries with mplsFTNMapIndex equal to zero.
.1.3.6.1.2.1.10.166.8.1.5.1.2,MPLS-FTN-STD-MIB::mplsFTNMapPrevIndex,Unsigned32,not-accessible,,current,,The index of the previous FTN entry that was applied to this interface. The special value zero indicates that this should be the first FTN entry in the list.
.1.3.6.1.2.1.10.166.8.1.5.1.3,MPLS-FTN-STD-MIB::mplsFTNMapCurrIndex,Unsigned32,not-accessible,,current,,Index of the current FTN entry that is being applied to this interface.
.1.3.6.1.2.1.10.166.8.1.5.1.4,MPLS-FTN-STD-MIB::mplsFTNMapRowStatus,INTEGER,read-create,,current,active(1):createAndGo(4):destroy(6),Used for controlling the creation and deletion of this row. All writable objects in this row may be modified at any time. If a conceptual row in mplsFTNMapTable points to a conceptual row in mplsFTNTable which is subsequently deleted, the corresponding conceptual row in mplsFTNMapTable MUST also be deleted by the agent.
.1.3.6.1.2.1.10.166.8.1.5.1.5,MPLS-FTN-STD-MIB::mplsFTNMapStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this entry. Conceptual rows having the value 'permanent' need not allow write- access to any columnar objects in this row.
.1.3.6.1.2.1.10.166.8.1.6,MPLS-FTN-STD-MIB::mplsFTNPerfTable,,not-accessible,,current,,This table contains performance statistics on FTN entries on a per-interface basis.
.1.3.6.1.2.1.10.166.8.1.6.1,MPLS-FTN-STD-MIB::mplsFTNPerfEntry,,not-accessible,mplsFTNPerfIndex:mplsFTNPerfCurrIndex,current,,Each entry contains performance information for the specified interface and an FTN entry mapped to this interface.
.1.3.6.1.2.1.10.166.8.1.6.1.1,MPLS-FTN-STD-MIB::mplsFTNPerfIndex,Integer32,not-accessible,,current,,The interface index of an interface that an FTN entry has been applied/mapped to. Each instance of this object corresponds to an instance of mplsFTNMapIndex.
.1.3.6.1.2.1.10.166.8.1.6.1.2,MPLS-FTN-STD-MIB::mplsFTNPerfCurrIndex,Unsigned32,not-accessible,,current,,Index of an FTN entry that has been applied/mapped to the specified interface. Each instance of this object corresponds to an instance of mplsFTNMapCurrIndex.
.1.3.6.1.2.1.10.166.8.1.6.1.3,MPLS-FTN-STD-MIB::mplsFTNPerfMatchedPackets,Counter64,read-only,,current,,Number of packets that matched the specified FTN entry if it is applied/mapped to the specified interface. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsFTNDiscontinuityTime.
.1.3.6.1.2.1.10.166.8.1.6.1.4,MPLS-FTN-STD-MIB::mplsFTNPerfMatchedOctets,Counter64,read-only,,current,,Number of octets that matched the specified FTN entry if it is applied/mapped to the specified interface. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsFTNDiscontinuityTime.
.1.3.6.1.2.1.10.166.8.1.6.1.5,MPLS-FTN-STD-MIB::mplsFTNPerfDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.8.2,MPLS-FTN-STD-MIB::mplsFTNConformance,,,,,,
.1.3.6.1.2.1.10.166.8.2.1,MPLS-FTN-STD-MIB::mplsFTNGroups,,,,,,
.1.3.6.1.2.1.10.166.8.2.1.1,MPLS-FTN-STD-MIB::mplsFTNRuleGroup,,,,,,Collection of objects that implement MPLS FTN rules.
.1.3.6.1.2.1.10.166.8.2.1.2,MPLS-FTN-STD-MIB::mplsFTNMapGroup,,,,,,Collection of objects that implement activation of MPLS FTN entries on interfaces.
.1.3.6.1.2.1.10.166.8.2.1.3,MPLS-FTN-STD-MIB::mplsFTNPerfGroup,,,,,,Collection of objects providing MPLS FTN performance information.
.1.3.6.1.2.1.10.166.8.2.2,MPLS-FTN-STD-MIB::mplsFTNCompliances,,,,,,
.1.3.6.1.2.1.10.166.8.2.2.1,MPLS-FTN-STD-MIB::mplsFTNModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for MPLS-FTN-STD-MIB.
.1.3.6.1.2.1.10.166.8.2.2.2,MPLS-FTN-STD-MIB::mplsFTNModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-FTN-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.166.9,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdMIB,,,,,,This MIB module contains managed object definitions for MPLS Label-Controlled ATM interfaces as defined in [RFC3035]. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4368; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.166.9.0,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdNotifications,,,,,,
.1.3.6.1.2.1.10.166.9.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdObjects,,,,,,
.1.3.6.1.2.1.10.166.9.1.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdInterfaceConfTable,,not-accessible,,current,,This table specifies per-interface MPLS LC-ATM capability and associated information. In particular, this table sparsely extends the MPLS-LSR-STD-MIB's mplsInterfaceConfTable.
.1.3.6.1.2.1.10.166.9.1.1.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdInterfaceConfEntry,,not-accessible,mplsInterfaceIndex,current,,An entry in this table is created by an LSR for every interface capable of supporting MPLS LC-ATM. Each entry in this table will exist only if a corresponding entry in ifTable and mplsInterfaceConfTable exists. If the associated entries in ifTable and mplsInterfaceConfTable are deleted, the corresponding entry in this table must also be deleted shortly thereafter.
.1.3.6.1.2.1.10.166.9.1.1.1.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdCtrlVpi,INTEGER,read-create,,current,,This is the VPI value over which this LSR is willing to accept control traffic on this interface.
.1.3.6.1.2.1.10.166.9.1.1.1.2,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdCtrlVci,Integer32,read-create,,current,,This is the VCI value over which this LSR is willing to accept control traffic on this interface.
.1.3.6.1.2.1.10.166.9.1.1.1.3,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdUnlabTrafVpi,INTEGER,read-create,,current,,This is the VPI value over which this LSR is willing to accept unlabeled traffic on this interface.
.1.3.6.1.2.1.10.166.9.1.1.1.4,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdUnlabTrafVci,Integer32,read-create,,current,,This is the VCI value over which this LSR is willing to accept unlabeled traffic on this interface.
.1.3.6.1.2.1.10.166.9.1.1.1.5,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdVcMerge,INTEGER,read-create,,current,true(1):false(2),If set to true(1), indicates that this interface is capable of ATM VC merge; otherwise, it MUST be set to false(2).
.1.3.6.1.2.1.10.166.9.1.1.1.6,MPLS-LC-ATM-STD-MIB::mplsLcAtmVcDirectlyConnected,INTEGER,read-create,,current,true(1):false(2),This value indicates whether an LC-ATM is directly or indirectly (by means of a VP) connected. If set to true(1), indicates that this interface is directly connected LC-ATM; otherwise, it MUST be set to false(2). Note that although it can be intimated from RFC 3057 that multiple VPs may be used, in practice only a single one is used, and therefore the authors of this MIB module have chosen to model it as such.
.1.3.6.1.2.1.10.166.9.1.1.1.7,MPLS-LC-ATM-STD-MIB::mplsLcAtmLcAtmVPI,INTEGER,read-create,,current,,This is the VPI value used for indirectly connected LC-ATM interfaces. For these interfaces, the VPI field is not available to MPLS, and the label MUST be encoded entirely within the VCI field (see [RFC3035]). If the interface is directly connected, this value MUST be set to zero.
.1.3.6.1.2.1.10.166.9.1.1.1.8,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdIfConfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete entries in this table. When configuring entries in this table, the corresponding ifEntry and mplsInterfaceConfEntry MUST exist beforehand. If a manager attempts to create an entry for a corresponding mplsInterfaceConfEntry that does not support LC-ATM, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1), except to mplsLcAtmStdIfConfRowStatus and mplsLcAtmStdIfConfStorageType.
.1.3.6.1.2.1.10.166.9.1.1.1.9,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdIfConfStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.9.2,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdConformance,,,,,,
.1.3.6.1.2.1.10.166.9.2.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdCompliances,,,,,,
.1.3.6.1.2.1.10.166.9.2.1.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for MPLS-LC-ATM-STD-MIB. Such devices can be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.10.166.9.2.1.2,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-LC-ATM-STD-MIB. Such devices can be monitored but cannot be configured using this MIB module. 
.1.3.6.1.2.1.10.166.9.2.2,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdGroups,,,,,,
.1.3.6.1.2.1.10.166.9.2.2.1,MPLS-LC-ATM-STD-MIB::mplsLcAtmStdIfGroup,,,,,,Collection of objects needed for MPLS LC-ATM interface configuration.
.1.3.6.1.2.1.10.166.10,MPLS-LC-FR-STD-MIB::mplsLcFrStdMIB,,,,,,This MIB module contains managed object definitions for MPLS Label-Controlled Frame-Relay interfaces as defined in (RFC3034). Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4368; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.166.10.0,MPLS-LC-FR-STD-MIB::mplsLcFrStdNotifications,,,,,,
.1.3.6.1.2.1.10.166.10.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdObjects,,,,,,
.1.3.6.1.2.1.10.166.10.1.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdInterfaceConfTable,,not-accessible,,current,,This table specifies per-interface MPLS LC-FR capability and associated information. In particular, this table sparsely extends the MPLS-LSR-STD-MIB's mplsInterfaceConfTable.
.1.3.6.1.2.1.10.166.10.1.1.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdInterfaceConfEntry,,not-accessible,mplsInterfaceIndex,current,,An entry in this table is created by an LSR for every interface capable of supporting MPLS LC-FR. Each entry in this table will exist only if a corresponding entry in ifTable and mplsInterfaceConfTable exists. If the associated entries in ifTable and mplsInterfaceConfTable are deleted, the corresponding entry in this table must also be deleted shortly thereafter.
.1.3.6.1.2.1.10.166.10.1.1.1.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdTrafficMinDlci,Integer32,read-create,,current,,This is the minimum DLCI value over which this LSR is willing to accept traffic on this interface.
.1.3.6.1.2.1.10.166.10.1.1.1.2,MPLS-LC-FR-STD-MIB::mplsLcFrStdTrafficMaxDlci,Integer32,read-create,,current,,This is the max DLCI value over which this LSR is willing to accept traffic on this interface.
.1.3.6.1.2.1.10.166.10.1.1.1.3,MPLS-LC-FR-STD-MIB::mplsLcFrStdCtrlMinDlci,Integer32,read-create,,current,,This is the min DLCI value over which this LSR is willing to accept control traffic on this interface.
.1.3.6.1.2.1.10.166.10.1.1.1.4,MPLS-LC-FR-STD-MIB::mplsLcFrStdCtrlMaxDlci,Integer32,read-create,,current,,This is the max DLCI value over which this LSR is willing to accept control traffic on this interface.
.1.3.6.1.2.1.10.166.10.1.1.1.5,MPLS-LC-FR-STD-MIB::mplsLcFrStdInterfaceConfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete entries in this table. When configuring entries in this table, the corresponding ifEntry and mplsInterfaceConfEntry MUST exist beforehand. If a manager attempts to create an entry for a corresponding mplsInterfaceConfEntry that does not support LC-FR, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1), except to mplsLcFrStdInterfaceConfRowStatus and mplsLcFrStdInterfaceConfStorageType.
.1.3.6.1.2.1.10.166.10.1.1.1.6,MPLS-LC-FR-STD-MIB::mplsLcFrStdInterfaceConfStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.10.2,MPLS-LC-FR-STD-MIB::mplsLcFrStdConformance,,,,,,
.1.3.6.1.2.1.10.166.10.2.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdCompliances,,,,,,
.1.3.6.1.2.1.10.166.10.2.1.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for MPLS-LC-FR-STD-MIB. Such devices can be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.10.166.10.2.1.2,MPLS-LC-FR-STD-MIB::mplsLcFrStdModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-LC-FR-STD-MIB. Such devices can be monitored but cannot be configured using this MIB module. 
.1.3.6.1.2.1.10.166.10.2.2,MPLS-LC-FR-STD-MIB::mplsLcFrStdGroups,,,,,,
.1.3.6.1.2.1.10.166.10.2.2.1,MPLS-LC-FR-STD-MIB::mplsLcFrStdIfGroup,,,,,,Collection of objects needed for MPLS LC-FR interface configuration.
.1.3.6.1.2.1.10.166.11,MPLS-L3VPN-STD-MIB::mplsL3VpnMIB,,,,,,This MIB contains managed object definitions for the Layer-3 Multiprotocol Label Switching Virtual Private Networks. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC4382; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.166.11.0,MPLS-L3VPN-STD-MIB::mplsL3VpnNotifications,,,,,,
.1.3.6.1.2.1.10.166.11.0.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfUp,,,,,,This notification is generated when: a. No interface is associated with this VRF, and the first (and only first) interface associated with it has its ifOperStatus change to up(1). b. One interface is associated with this VRF, and the ifOperStatus of this interface changes to up(1). c. Multiple interfaces are associated with this VRF, and the ifOperStatus of all interfaces is down(2), and the first of those interfaces has its ifOperStatus change to up(1).
.1.3.6.1.2.1.10.166.11.0.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfDown,,,,,,This notification is generated when: a. One interface is associated with this VRF, and the ifOperStatus of this interface changes from up(1) to down(2). b. Multiple interfaces are associated with this VRF, and the ifOperStatus of all except one of these interfaces is equal to up(1), and the ifOperStatus of that interface changes from up(1) to down(2). c. The last interface with ifOperStatus equal to up(1) is disassociated from a VRF.
.1.3.6.1.2.1.10.166.11.0.3,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRouteMidThreshExceeded,,,,,,This notification is generated when the number of routes contained by the specified VRF exceeds the value indicated by mplsL3VpnVrfMidRouteThreshold. A single notification MUST be generated when this threshold is exceeded, and no other notifications of this type should be issued until the value of mplsL3VpnVrfPerfCurrNumRoutes has fallen below that of mplsL3VpnVrfConfMidRteThresh.
.1.3.6.1.2.1.10.166.11.0.4,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfNumVrfRouteMaxThreshExceeded,,,,,,This notification is generated when the number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsL3VpnVrfMaxRouteThreshold. In cases where mplsL3VpnVrfConfHighRteThresh is set to the same value as mplsL3VpnVrfConfMaxRoutes, mplsL3VpnVrfConfHighRteThresh need not be exceeded; rather, just reached for this notification to be issued. Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval at which the this notification will be reissued after the maximum value has been exceeded (or reached if mplsL3VpnVrfConfMaxRoutes and mplsL3VpnVrfConfHighRteThresh are equal) and the initial notification has been issued. This value is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added to a VRF after it has reached its maximum value. The default value is 0 minutes. If this value is set to 0, the agent should only issue a single notification at the time that the maximum threshold has been reached, and should not issue any more notifications until the value of routes has fallen below the configured threshold value.
.1.3.6.1.2.1.10.166.11.0.5,MPLS-L3VPN-STD-MIB::mplsL3VpnNumVrfSecIllglLblThrshExcd,,,,,,This notification is generated when the number of illegal label violations on a VRF as indicated by mplsL3VpnVrfSecIllegalLblVltns has exceeded mplsL3VpnIllLblRcvThrsh. The threshold is not included in the varbind here because the value of mplsL3VpnVrfSecIllegalLblVltns should be one greater than the threshold at the time this notification is issued.
.1.3.6.1.2.1.10.166.11.0.6,MPLS-L3VPN-STD-MIB::mplsL3VpnNumVrfRouteMaxThreshCleared,,,,,,This notification is generated only after the number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold, and then falls below this value. The emission of this notification informs the operator that the error condition has been cleared without the operator having to query the device. Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval at which the mplsNumVrfRouteMaxThreshExceeded notification will be reissued after the maximum value has been exceeded (or reached if mplsL3VpnVrfConfMaxRoutes and mplsL3VpnVrfConfHighRteThresh are equal) and the initial notification has been issued. Therefore, the generation of this notification should also be emitted with this same frequency (assuming that the error condition is cleared). Specifically, if the error condition is reached and cleared several times during the period of time specified in mplsL3VpnVrfConfRteMxThrshTime, only a single notification will be issued to indicate the first instance of the error condition as well as the first time the error condition is cleared. This behavior is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added and removed to/from a VRF after it has reached its maximum value. The default value is 0. If this value is set to 0, the agent should issue a notification whenever the maximum threshold has been cleared.
.1.3.6.1.2.1.10.166.11.1,MPLS-L3VPN-STD-MIB::mplsL3VpnObjects,,,,,,
.1.3.6.1.2.1.10.166.11.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnScalars,,,,,,
.1.3.6.1.2.1.10.166.11.1.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnConfiguredVrfs,Unsigned32,read-only,,current,,The number of VRFs that are configured on this node.
.1.3.6.1.2.1.10.166.11.1.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnActiveVrfs,Gauge32,read-only,,current,,The number of VRFs that are active on this node. That is, those VRFs whose corresponding mplsL3VpnVrfOperStatus object value is equal to operational (1).
.1.3.6.1.2.1.10.166.11.1.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnConnectedInterfaces,Gauge32,read-only,,current,,Total number of interfaces connected to a VRF.
.1.3.6.1.2.1.10.166.11.1.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnNotificationEnable,INTEGER,read-write,,current,true(1):false(2),If this object is true, then it enables the generation of all notifications defined in this MIB. This object's value should be preserved across agent reboots.
.1.3.6.1.2.1.10.166.11.1.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfMaxPossRts,Unsigned32,read-only,,current,,Denotes maximum number of routes that the device will allow all VRFs jointly to hold. If this value is set to 0, this indicates that the device is unable to determine the absolute maximum. In this case, the configured maximum MAY not actually be allowed by the device.
.1.3.6.1.2.1.10.166.11.1.1.6,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfRteMxThrshTime,Unsigned32,read-only,,current,,Denotes the interval in seconds, at which the route max threshold notification may be reissued after the maximum value has been exceeded (or has been reached if mplsL3VpnVrfConfMaxRoutes and mplsL3VpnVrfConfHighRteThresh are equal) and the initial notification has been issued. This value is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added to a VRF after it has reached its maximum value. If this value is set to 0, the agent should only issue a single notification at the time that the maximum threshold has been reached, and should not issue any more notifications until the value of routes has fallen below the configured threshold value. This is the recommended default behavior.
.1.3.6.1.2.1.10.166.11.1.1.7,MPLS-L3VPN-STD-MIB::mplsL3VpnIllLblRcvThrsh,Unsigned32,read-write,,current,,The number of illegally received labels above which the mplsNumVrfSecIllglLblThrshExcd notification is issued. The persistence of this value mimics that of the device's configuration.
.1.3.6.1.2.1.10.166.11.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnConf,,,,,,
.1.3.6.1.2.1.10.166.11.1.2.1,MPLS-L3VPN-STD-MIB::mplsL3VpnIfConfTable,,not-accessible,,current,,This table specifies per-interface MPLS capability and associated information.
.1.3.6.1.2.1.10.166.11.1.2.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnIfConfEntry,,not-accessible,mplsL3VpnVrfName:mplsL3VpnIfConfIndex,current,,An entry in this table is created by an LSR for every interface capable of supporting MPLS L3VPN. Each entry in this table is meant to correspond to an entry in the Interfaces Table.
.1.3.6.1.2.1.10.166.11.1.2.1.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnIfConfIndex,Integer32,not-accessible,,current,,This is a unique index for an entry in the mplsL3VpnIfConfTable. A non-zero index for an entry indicates the ifIndex for the corresponding interface entry in the MPLS-VPN-layer in the ifTable. Note that this table does not necessarily correspond one-to-one with all entries in the Interface MIB having an ifType of MPLS-layer; rather, only those that are enabled for MPLS L3VPN functionality.
.1.3.6.1.2.1.10.166.11.1.2.1.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnIfVpnClassification,INTEGER,read-create,,current,carrierOfCarrier(1):enterprise(2):interProvider(3),Denotes whether this link participates in a carrier's carrier, enterprise, or inter-provider scenario.
.1.3.6.1.2.1.10.166.11.1.2.1.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnIfVpnRouteDistProtocol,BITS,read-create,,current,none(0):bgp(1):ospf(2):rip(3):isis(4):static(5):other(6),Denotes the route distribution protocol across the PE-CE link. Note that more than one routing protocol may be enabled at the same time; thus, this object is specified as a bitmask. For example, static(5) and ospf(2) are a typical configuration.
.1.3.6.1.2.1.10.166.11.1.2.1.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnIfConfStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this VPN If entry. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.11.1.2.1.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnIfConfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. Rows in this table signify that the specified interface is associated with this VRF. If the row creation operation succeeds, the interface will have been associated with the specified VRF, otherwise the agent MUST not allow the association. If the agent only allows read-only operations on this table, it MUST create entries in this table as they are created on the device. When a row in this table is in active(1) state, no objects in that row can be modified except mplsL3VpnIfConfStorageType and mplsL3VpnIfConfRowStatus.
.1.3.6.1.2.1.10.166.11.1.2.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfTable,,not-accessible,,current,,This table specifies per-interface MPLS L3VPN VRF Table capability and associated information. Entries in this table define VRF routing instances associated with MPLS/VPN interfaces. Note that multiple interfaces can belong to the same VRF instance. The collection of all VRF instances comprises an actual VPN.
.1.3.6.1.2.1.10.166.11.1.2.2.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfEntry,,not-accessible,mplsL3VpnVrfName,current,,An entry in this table is created by an LSR for every VRF capable of supporting MPLS L3VPN. The indexing provides an ordering of VRFs per-VPN interface.
.1.3.6.1.2.1.10.166.11.1.2.2.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfName,OCTET,not-accessible,,current,,The human-readable name of this VPN. This MAY be equivalent to the [RFC2685] VPN-ID, but may also vary. If it is set to the VPN ID, it MUST be equivalent to the value of mplsL3VpnVrfVpnId. It is strongly recommended that all sites supporting VRFs that are part of the same VPN use the same naming convention for VRFs as well as the same VPN ID.
.1.3.6.1.2.1.10.166.11.1.2.2.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfVpnId,OCTET,read-create,,current,,The VPN ID as specified in [RFC2685]. If a VPN ID has not been specified for this VRF, then this variable SHOULD be set to a zero-length OCTET STRING.
.1.3.6.1.2.1.10.166.11.1.2.2.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfDescription,OCTET,read-create,,current,,The human-readable description of this VRF.
.1.3.6.1.2.1.10.166.11.1.2.2.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRD,OCTET,read-create,,current,,The route distinguisher for this VRF.
.1.3.6.1.2.1.10.166.11.1.2.2.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfCreationTime,TimeTicks,read-only,,current,,The time at which this VRF entry was created.
.1.3.6.1.2.1.10.166.11.1.2.2.1.6,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfOperStatus,INTEGER,read-only,,current,up(1):down(2),Denotes whether or not a VRF is operational. A VRF is up(1) when there is at least one interface associated with the VRF whose ifOperStatus is up(1). A VRF is down(2) when: a. There does not exist at least one interface whose ifOperStatus is up(1). b. There are no interfaces associated with the VRF.
.1.3.6.1.2.1.10.166.11.1.2.2.1.7,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfActiveInterfaces,Gauge32,read-only,,current,,Total number of interfaces connected to this VRF with ifOperStatus = up(1). This value should increase when an interface is associated with the corresponding VRF and its corresponding ifOperStatus is equal to up(1). If an interface is associated whose ifOperStatus is not up(1), then the value is not incremented until such time as it transitions to this state. This value should be decremented when an interface is disassociated with a VRF or the corresponding ifOperStatus transitions out of the up(1) state to any other state. 
.1.3.6.1.2.1.10.166.11.1.2.2.1.8,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfAssociatedInterfaces,Unsigned32,read-only,,current,,Total number of interfaces connected to this VRF (independent of ifOperStatus type).
.1.3.6.1.2.1.10.166.11.1.2.2.1.9,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfMidRteThresh,Unsigned32,read-create,,current,,Denotes mid-level water marker for the number of routes that this VRF may hold.
.1.3.6.1.2.1.10.166.11.1.2.2.1.10,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfHighRteThresh,Unsigned32,read-create,,current,,Denotes high-level water marker for the number of routes that this VRF may hold.
.1.3.6.1.2.1.10.166.11.1.2.2.1.11,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfMaxRoutes,Unsigned32,read-create,,current,,Denotes maximum number of routes that this VRF is configured to hold. This value MUST be less than or equal to mplsL3VpnVrfConfMaxPossRts unless it is set to 0.
.1.3.6.1.2.1.10.166.11.1.2.2.1.12,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last change of this table entry, which includes changes of VRF parameters defined in this table or addition or deletion of interfaces associated with this VRF.
.1.3.6.1.2.1.10.166.11.1.2.2.1.13,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified except mplsL3VpnVrfConfAdminStatus, mplsL3VpnVrfConfRowStatus, and mplsL3VpnVrfConfStorageType.
.1.3.6.1.2.1.10.166.11.1.2.2.1.14,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfAdminStatus,INTEGER,read-create,,current,up(1):down(2):testing(3),Indicates the desired operational status of this VRF.
.1.3.6.1.2.1.10.166.11.1.2.2.1.15,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfConfStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this VPN VRF entry. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.11.1.2.3,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTTable,,not-accessible,,current,,This table specifies per-VRF route target association. Each entry identifies a connectivity policy supported as part of a VPN.
.1.3.6.1.2.1.10.166.11.1.2.3.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTEntry,,not-accessible,mplsL3VpnVrfName:mplsL3VpnVrfRTIndex:mplsL3VpnVrfRTType,current,,An entry in this table is created by an LSR for each route target configured for a VRF supporting a MPLS L3VPN instance. The indexing provides an ordering per-VRF instance. See [RFC4364] for a complete definition of a route target.
.1.3.6.1.2.1.10.166.11.1.2.3.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTIndex,Unsigned32,not-accessible,,current,,Auxiliary index for route targets configured for a particular VRF.
.1.3.6.1.2.1.10.166.11.1.2.3.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTType,INTEGER,not-accessible,,current,import(1):export(2):both(3),The route target distribution type.
.1.3.6.1.2.1.10.166.11.1.2.3.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRT,OCTET,read-create,,current,,The route target distribution policy.
.1.3.6.1.2.1.10.166.11.1.2.3.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTDescr,OCTET,read-create,,current,,Description of the route target.
.1.3.6.1.2.1.10.166.11.1.2.3.1.6,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified except mplsL3VpnVrfRTRowStatus.
.1.3.6.1.2.1.10.166.11.1.2.3.1.7,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this VPN route target (RT) entry. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.11.1.2.6,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfSecTable,,not-accessible,,current,,This table specifies per MPLS L3VPN VRF Table security-related counters.
.1.3.6.1.2.1.10.166.11.1.2.6.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfSecEntry,,not-accessible,,current,,An entry in this table is created by an LSR for every VRF capable of supporting MPLS L3VPN. Each entry in this table is used to indicate security-related information for each VRF entry.
.1.3.6.1.2.1.10.166.11.1.2.6.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfSecIllegalLblVltns,Counter32,read-only,,current,,Indicates the number of illegally received labels on this VPN/VRF. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsL3VpnVrfSecDiscontinuityTime.
.1.3.6.1.2.1.10.166.11.1.2.6.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfSecDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.11.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnPerf,,,,,,
.1.3.6.1.2.1.10.166.11.1.3.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfTable,,not-accessible,,current,,This table specifies per MPLS L3VPN VRF Table performance information.
.1.3.6.1.2.1.10.166.11.1.3.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfEntry,,not-accessible,,current,,An entry in this table is created by an LSR for every VRF capable of supporting MPLS L3VPN.
.1.3.6.1.2.1.10.166.11.1.3.1.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfRoutesAdded,Counter32,read-only,,current,,Indicates the number of routes added to this VPN/VRF since the last discontinuity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsL3VpnVrfPerfDiscTime.
.1.3.6.1.2.1.10.166.11.1.3.1.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfRoutesDeleted,Counter32,read-only,,current,,Indicates the number of routes removed from this VPN/VRF. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsL3VpnVrfPerfDiscTime.
.1.3.6.1.2.1.10.166.11.1.3.1.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfCurrNumRoutes,Gauge32,read-only,,current,,Indicates the number of routes currently used by this VRF.
.1.3.6.1.2.1.10.166.11.1.3.1.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfRoutesDropped,Counter32,read-only,,current,,This counter should be incremented when the number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsL3VpnVrfMaxRouteThreshold. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsL3VpnVrfPerfDiscTime.
.1.3.6.1.2.1.10.166.11.1.3.1.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfPerfDiscTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.166.11.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnRoute,,,,,,
.1.3.6.1.2.1.10.166.11.1.4.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteTable,,not-accessible,,current,,This table specifies per-interface MPLS L3VPN VRF Table routing information. Entries in this table define VRF routing entries associated with the specified MPLS/VPN interfaces. Note that this table contains both BGP and Interior Gateway Protocol IGP routes, as both may appear in the same VRF.
.1.3.6.1.2.1.10.166.11.1.4.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteEntry,,not-accessible,mplsL3VpnVrfName:mplsL3VpnVrfRteInetCidrDestType:mplsL3VpnVrfRteInetCidrDest:mplsL3VpnVrfRteInetCidrPfxLen:mplsL3VpnVrfRteInetCidrPolicy:mplsL3VpnVrfRteInetCidrNHopType:mplsL3VpnVrfRteInetCidrNextHop,current,,An entry in this table is created by an LSR for every route present configured (either dynamically or statically) within the context of a specific VRF capable of supporting MPLS/BGP VPN. The indexing provides an ordering of VRFs per-VPN interface. Implementers need to be aware that there are quite a few index objects that together can exceed the size allowed for an Object Identifier (OID). So implementers must make sure that OIDs of column instances in this table will have no more than 128 sub-identifiers, otherwise they cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.10.166.11.1.4.1.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrDestType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the mplsL3VpnVrfRteInetCidrDest address, as defined in the InetAddress MIB. Only those address types that may appear in an actual routing table are allowed as values of this object.
.1.3.6.1.2.1.10.166.11.1.4.1.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrDest,OCTET,not-accessible,,current,,The destination IP address of this route. The type of this address is determined by the value of the mplsL3VpnVrfRteInetCidrDestType object. The values for the index objects mplsL3VpnVrfRteInetCidrDest and mplsL3VpnVrfRteInetCidrPfxLen must be consistent. When the value of mplsL3VpnVrfRteInetCidrDest is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object mplsL3VpnVrfRteInetCidrPfxLen MUST be equal to x. If not, then the index pair is not consistent and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.10.166.11.1.4.1.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrPfxLen,Unsigned32,not-accessible,,current,,Indicates the number of leading one bits that form the mask to be logical-ANDed with the destination address before being compared to the value in the mplsL3VpnVrfRteInetCidrDest field. The values for the index objects mplsL3VpnVrfRteInetCidrDest and mplsL3VpnVrfRteInetCidrPfxLen must be consistent. When the value of mplsL3VpnVrfRteInetCidrDest is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object mplsL3VpnVrfRteInetCidrPfxLen MUST be equal to x. If not, then the index pair is not consistent and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.10.166.11.1.4.1.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrPolicy,OBJECT,not-accessible,,current,,This object is an opaque object without any defined semantics. Its purpose is to serve as an additional index that may delineate between multiple entries to the same destination. The value { 0 0 } shall be used as the default value for this object.
.1.3.6.1.2.1.10.166.11.1.4.1.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrNHopType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the mplsL3VpnVrfRteInetCidrNextHop address, as defined in the InetAddress MIB. Value should be set to unknown(0) for non-remote routes. Only those address types that may appear in an actual routing table are allowed as values of this object.
.1.3.6.1.2.1.10.166.11.1.4.1.1.6,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrNextHop,OCTET,not-accessible,,current,,On remote routes, the address of the next system en route. For non-remote routes, a zero-length string. The type of this address is determined by the value of the mplsL3VpnVrfRteInetCidrNHopType object.
.1.3.6.1.2.1.10.166.11.1.4.1.1.7,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrIfIndex,Integer32,read-create,,current,,The ifIndex value that identifies the local interface through which the next hop of this route should be reached. A value of 0 is valid and represents the scenario where no interface is specified.
.1.3.6.1.2.1.10.166.11.1.4.1.1.8,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrType,INTEGER,read-create,,current,other(1):reject(2):local(3):remote(4):blackhole(5),The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destination. Routes that do not result in traffic forwarding or rejection should not be displayed even if the implementation keeps them stored internally. reject(2) refers to a route that, if matched, discards the message as unreachable and returns a notification (e.g., ICMP error) to the message sender. This is used in some protocols as a means of correctly aggregating routes. blackhole(5) refers to a route that, if matched, discards the message silently.
.1.3.6.1.2.1.10.166.11.1.4.1.1.9,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrProto,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.2.1.10.166.11.1.4.1.1.10,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrAge,Gauge32,read-only,,current,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of 'too old' can be implied except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.2.1.10.166.11.1.4.1.1.11,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrNextHopAS,Unsigned32,read-create,,current,,The Autonomous System Number of the next hop. The semantics of this object are determined by the routing protocol specified in the route's mplsL3VpnVrfRteInetCidrProto value. When this object is unknown or not relevant, its value should be set to zero.
.1.3.6.1.2.1.10.166.11.1.4.1.1.12,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrMetric1,Integer32,read-create,,current,,The primary routing metric for this route. The semantics of this metric are determined by the routing protocol specified in the route's mplsL3VpnVrfRteInetCidrProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.10.166.11.1.4.1.1.13,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrMetric2,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing protocol specified in the route's mplsL3VpnVrfRteInetCidrProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.10.166.11.1.4.1.1.14,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrMetric3,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing protocol specified in the route's mplsL3VpnVrfRteInetCidrProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.10.166.11.1.4.1.1.15,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrMetric4,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing protocol specified in the route's mplsL3VpnVrfRteInetCidrProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.10.166.11.1.4.1.1.16,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrMetric5,Integer32,read-create,,current,,An alternate routing metric for this route. The semantics of this metric are determined by the routing protocol specified in the route's mplsL3VpnVrfRteInetCidrProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.2.1.10.166.11.1.4.1.1.17,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteXCPointer,OCTET,read-create,,current,,Index into mplsXCTable that identifies which cross- connect entry is associated with this VRF route entry by containing the mplsXCIndex of that cross-connect entry. The string containing the single-octet 0x00 indicates that a label stack is not associated with this route entry. This can be the case because the label bindings have not yet been established, or because some change in the agent has removed them. When the label stack associated with this VRF route is created, it MUST establish the associated cross-connect entry in the mplsXCTable and then set that index to the value of this object. Changes to the cross-connect object in the mplsXCTable MUST automatically be reflected in the value of this object. If this object represents a static routing entry, then the manager must ensure that this entry is maintained consistently in the corresponding mplsXCTable as well.
.1.3.6.1.2.1.10.166.11.1.4.1.1.18,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteInetCidrStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to row installation and removal conventions. A row entry cannot be modified when the status is marked as active(1).
.1.3.6.1.2.1.10.166.11.2,MPLS-L3VPN-STD-MIB::mplsL3VpnConformance,,,,,,
.1.3.6.1.2.1.10.166.11.2.1,MPLS-L3VPN-STD-MIB::mplsL3VpnGroups,,,,,,
.1.3.6.1.2.1.10.166.11.2.1.1,MPLS-L3VPN-STD-MIB::mplsL3VpnScalarGroup,,,,,,Collection of scalar objects required for MPLS VPN management.
.1.3.6.1.2.1.10.166.11.2.1.2,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfGroup,,,,,,Collection of objects needed for MPLS VPN VRF management.
.1.3.6.1.2.1.10.166.11.2.1.3,MPLS-L3VPN-STD-MIB::mplsL3VpnIfGroup,,,,,,Collection of objects needed for MPLS VPN interface management.
.1.3.6.1.2.1.10.166.11.2.1.4,MPLS-L3VPN-STD-MIB::mplsL3VpnPerfGroup,,,,,,Collection of objects needed for MPLS VPN performance information.
.1.3.6.1.2.1.10.166.11.2.1.5,MPLS-L3VPN-STD-MIB::mplsL3VpnPerfRouteGroup,,,,,,Collection of objects needed to track MPLS VPN routing table dropped routes.
.1.3.6.1.2.1.10.166.11.2.1.7,MPLS-L3VPN-STD-MIB::mplsL3VpnSecGroup,,,,,,Collection of objects needed for MPLS VPN security-related information.
.1.3.6.1.2.1.10.166.11.2.1.8,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRteGroup,,,,,,Objects required for VRF route table management.
.1.3.6.1.2.1.10.166.11.2.1.9,MPLS-L3VPN-STD-MIB::mplsL3VpnVrfRTGroup,,,,,,Objects required for VRF route target management.
.1.3.6.1.2.1.10.166.11.2.1.10,MPLS-L3VPN-STD-MIB::mplsL3VpnNotificationGroup,,,,,,Objects required for MPLS VPN notifications.
.1.3.6.1.2.1.10.166.11.2.2,MPLS-L3VPN-STD-MIB::mplsL3VpnCompliances,,,,,,
.1.3.6.1.2.1.10.166.11.2.2.1,MPLS-L3VPN-STD-MIB::mplsL3VpnModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for the MPLS-L3VPN-STD-MIB
.1.3.6.1.2.1.10.166.11.2.2.2,MPLS-L3VPN-STD-MIB::mplsL3VpnModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-L3VPN-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.166.12,GMPLS-TC-STD-MIB::gmplsTCStdMIB,,,,,,Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4801; see the RFC itself for full legal notices. This MIB module defines TEXTUAL-CONVENTIONs for concepts used in Generalized Multiprotocol Label Switching (GMPLS) networks.
.1.3.6.1.2.1.10.166.13,GMPLS-TE-STD-MIB::gmplsTeStdMIB,,,,,,Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4802; see the RFC itself for full legal notices. This MIB module contains managed object definitions for GMPLS Traffic Engineering (TE) as defined in: 1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, Berger, L. (Editor), RFC 3471, January 2003. 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. (Editor), RFC 3473, January 2003. 
.1.3.6.1.2.1.10.166.13.0,GMPLS-TE-STD-MIB::gmplsTeNotifications,,,,,,
.1.3.6.1.2.1.10.166.13.0.1,GMPLS-TE-STD-MIB::gmplsTunnelDown,,,,,,This notification is generated when an mplsTunnelOperStatus object for a tunnel in the gmplsTunnelTable is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of mplsTunnelOperStatus. The objects in this notification provide additional error information that indicates the reason why the tunnel has transitioned to down(2). Note that an implementation MUST only issue one of mplsTunnelDown and gmplsTunnelDown for any single event on a single tunnel. If the tunnel has an entry in the gmplsTunnelTable, an implementation SHOULD use gmplsTunnelDown for all tunnel-down events and SHOULD NOT use mplsTunnelDown. This notification is subject to the control of mplsTunnelNotificationEnable. When that object is set to false(2), then the notification must not be issued. Further, this notification is also subject to mplsTunnelNotificationMaxRate. That object indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit some notifications during that period, or may queue them until an appropriate time. The notification rate applies to the sum of all notifications in the MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB modules applied across the whole of the reporting device. mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate objects are found in MPLS-TE-STD-MIB.
.1.3.6.1.2.1.10.166.13.1,GMPLS-TE-STD-MIB::gmplsTeScalars,,,,,,
.1.3.6.1.2.1.10.166.13.1.1,GMPLS-TE-STD-MIB::gmplsTunnelsConfigured,Gauge32,read-only,,current,,The number of GMPLS tunnels configured on this device. A GMPLS tunnel is considered configured if an entry for the tunnel exists in the gmplsTunnelTable and the associated mplsTunnelRowStatus is active(1).
.1.3.6.1.2.1.10.166.13.1.2,GMPLS-TE-STD-MIB::gmplsTunnelsActive,Gauge32,read-only,,current,,The number of GMPLS tunnels active on this device. A GMPLS tunnel is considered active if there is an entry in the gmplsTunnelTable and the associated mplsTunnelOperStatus for the tunnel is up(1).
.1.3.6.1.2.1.10.166.13.2,GMPLS-TE-STD-MIB::gmplsTeObjects,,,,,,
.1.3.6.1.2.1.10.166.13.2.1,GMPLS-TE-STD-MIB::gmplsTunnelTable,,not-accessible,,current,,The gmplsTunnelTable sparsely extends the mplsTunnelTable of MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multipoint-to-point and point-to-multipoint connections are supported by an LSR acting as a cross-connect. Each tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. The row status of an entry in this table is controlled by the mplsTunnelRowStatus in the corresponding entry in the mplsTunnelTable. When the corresponding mplsTunnelRowStatus has value active(1), a row in this table may not be created or modified. The exception to this rule is the gmplsTunnelAdminStatusInformation object, which can be modified while the tunnel is active.
.1.3.6.1.2.1.10.166.13.2.1.1,GMPLS-TE-STD-MIB::gmplsTunnelEntry,,not-accessible,mplsTunnelIndex:mplsTunnelInstance:mplsTunnelIngressLSRId:mplsTunnelEgressLSRId,current,,An entry in this table in association with the corresponding entry in the mplsTunnelTable represents a GMPLS tunnel. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events.
.1.3.6.1.2.1.10.166.13.2.1.1.1,GMPLS-TE-STD-MIB::gmplsTunnelUnnumIf,INTEGER,read-create,,current,true(1):false(2),Denotes whether or not this tunnel corresponds to an unnumbered interface represented by an entry in the interfaces group table (the ifTable) with ifType set to mpls(166). This object is only used if mplsTunnelIsIf is set to 'true'. If both this object and the mplsTunnelIsIf object are set to 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID object to the outgoing Path message. This object contains information that is only used by the terminating LSR.
.1.3.6.1.2.1.10.166.13.2.1.1.2,GMPLS-TE-STD-MIB::gmplsTunnelAttributes,BITS,read-create,,current,labelRecordingDesired(0),This bitmask indicates optional parameters for this tunnel. These bits should be taken in addition to those defined in mplsTunnelSessionAttributes in order to determine the full set of options to be signaled (for example SESSION_ATTRIBUTES flags in RSVP-TE). The following describes these bitfields: labelRecordingDesired This flag is set to indicate that label information should be included when doing a route record. This bit is not valid unless the recordRoute bit is set.
.1.3.6.1.2.1.10.166.13.2.1.1.3,GMPLS-TE-STD-MIB::gmplsTunnelLSPEncoding,INTEGER,read-create,,current,tunnelLspNotGmpls(0):tunnelLspPacket(1):tunnelLspEthernet(2):tunnelLspAnsiEtsiPdh(3):tunnelLspSdhSonet(5):tunnelLspDigitalWrapper(7):tunnelLspLambda(8):tunnelLspFiber(9):tunnelLspFiberChannel(11):tunnelDigitalPath(12):tunnelOpticalChannel(13):tunnelLine(14),This object indicates the encoding of the LSP being requested. A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is not in use. Some objects in this MIB module may be of use for MPLS signaling extensions that do not use GMPLS signaling. By setting this object to 'tunnelLspNotGmpls', an application may indicate that only those objects meaningful in MPLS should be examined. The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB module.
.1.3.6.1.2.1.10.166.13.2.1.1.4,GMPLS-TE-STD-MIB::gmplsTunnelSwitchingType,INTEGER,read-create,,current,unknown(0):psc1(1):psc2(2):psc3(3):psc4(4):evpl(30):pbb(40):l2sc(51):tdm(100):otntdm(110):dcsc(125):lsc(150):wsonlsc(151):fsc(200),Indicates the type of switching that should be performed on a particular link. This field is needed for links that advertise more than one type of switching capability. The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsSwitchingTypeTC found in the IANA-GMPLS-TC-MIB module. This object is only meaningful if gmplsTunnelLSPEncodingType is not set to 'tunnelLspNotGmpls'.
.1.3.6.1.2.1.10.166.13.2.1.1.5,GMPLS-TE-STD-MIB::gmplsTunnelLinkProtection,BITS,read-create,,current,extraTraffic(0):unprotected(1):shared(2):dedicatedOneToOne(3):dedicatedOnePlusOne(4):enhanced(5),This bitmask indicates the level of link protection required. A value of zero (no bits set) indicates that any protection may be used. The following describes these bitfields: extraTraffic This flag is set to indicate that the LSP should use links that are protecting other (primary) traffic. Such LSPs may be preempted when the links carrying the (primary) traffic being protected fail. unprotected This flag is set to indicate that the LSP should not use any link layer protection. shared This flag is set to indicate that a shared link layer protection scheme, such as 1:N protection, should be used to support the LSP. dedicatedOneToOne This flag is set to indicate that a dedicated link layer protection scheme, i.e., 1:1 protection, should be used to support the LSP. dedicatedOnePlusOne This flag is set to indicate that a dedicated link layer protection scheme, i.e., 1+1 protection, should be used to support the LSP. enhanced This flag is set to indicate that a protection scheme that is more reliable than Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'.
.1.3.6.1.2.1.10.166.13.2.1.1.6,GMPLS-TE-STD-MIB::gmplsTunnelGPid,INTEGER,read-create,,current,unknown(0):asynchE4(5):asynchDS3T3(6):asynchE3(7):bitsynchE3(8):bytesynchE3(9):asynchDS2T2(10):bitsynchDS2T2(11):reservedByRFC3471first(12):asynchE1(13):bytesynchE1(14):bytesynch31ByDS0(15):asynchDS1T1(16):bitsynchDS1T1(17):bytesynchDS1T1(18):vc1vc12(19):reservedByRFC3471second(20):reservedByRFC3471third(21):ds1SFAsynch(22):ds1ESFAsynch(23):ds3M23Asynch(24):ds3CBitParityAsynch(25):vtLovc(26):stsSpeHovc(27):posNoScramble16BitCrc(28):posNoScramble32BitCrc(29):posScramble16BitCrc(30):posScramble32BitCrc(31):atm(32):ethernet(33):sdhSonet(34):digitalwrapper(36):lambda(37):ansiEtsiPdh(38):lapsSdh(40):fddi(41):dqdb(42):fiberChannel3(43):hdlc(44):ethernetV2DixOnly(45):ethernet802dot3Only(46):g709ODUj(47):g709OTUk(48):g709CBRorCBRa(49):g709CBRb(50):g709BSOT(51):g709BSNT(52):gfpIPorPPP(53):gfpEthernetMAC(54):gfpEthernetPHY(55):g709ESCON(56):g709FICON(57):g709FiberChannel(58):framedGFP(59):sTM1(60):sTM4(61):infiniBand(62):sDI(63):sDI1point001(64):dVBASI(65):g709ODU125G(66):g709ODUAny(67):nullTest(68):randomTest(69):sixtyfourB66BGFPFEthernet(70),This object indicates the payload carried by the LSP. It is only required when GMPLS will be used for this LSP. The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsGeneralizedPidTC found in the IANA-GMPLS-TC-MIB module. This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'.
.1.3.6.1.2.1.10.166.13.2.1.1.7,GMPLS-TE-STD-MIB::gmplsTunnelSecondary,INTEGER,read-create,,current,true(1):false(2),Indicates that the requested LSP is a secondary LSP. This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'.
.1.3.6.1.2.1.10.166.13.2.1.1.8,GMPLS-TE-STD-MIB::gmplsTunnelDirection,INTEGER,read-create,,current,forward(0):bidirectional(1),Whether this tunnel carries forward data only (is unidirectional) or is bidirectional. Values of this object other than 'forward' are meaningful only if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'.
.1.3.6.1.2.1.10.166.13.2.1.1.9,GMPLS-TE-STD-MIB::gmplsTunnelPathComp,INTEGER,read-create,,current,dynamicFull(1):explicit(2):dynamicPartial(3),This value instructs the source node on how to perform path computation on the explicit route specified by the associated entries in the gmplsTunnelHopTable. dynamicFull The user specifies at least the source and destination of the path and expects that the Constrained Shortest Path First (CSPF) will calculate the remainder of the path. explicit The user specifies the entire path for the tunnel to take. This path may contain strict or loose hops. Evaluation of the explicit route will be performed hop by hop through the network. dynamicPartial The user specifies at least the source and destination of the path and expects that the CSPF will calculate the remainder of the path. The path computed by CSPF is allowed to be only partially computed allowing the remainder of the path to be filled in across the network. When an entry is present in the gmplsTunnelTable for a tunnel, gmplsTunnelPathComp MUST be used and any corresponding mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable MUST be ignored and SHOULD not be set. mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of MPLS-TE-STD-MIB. This object should be ignored if the value of gmplsTunnelLSPEncoding is 'tunnelLspNotGmpls'.
.1.3.6.1.2.1.10.166.13.2.1.1.10,GMPLS-TE-STD-MIB::gmplsTunnelUpstreamNotifyRecipientType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object is used to aid in interpretation of gmplsTunnelUpstreamNotifyRecipient.
.1.3.6.1.2.1.10.166.13.2.1.1.11,GMPLS-TE-STD-MIB::gmplsTunnelUpstreamNotifyRecipient,OCTET,read-create,,current,,Indicates the address of the upstream recipient for Notify messages relating to this tunnel and issued by this LSR. This information is typically received from an upstream LSR in a Path message. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the head end of a tunnel since there are no upstream LSRs to which to send a Notify message. This object is interpreted in the context of the value of gmplsTunnelUpstreamNotifyRecipientType. If this object is set to 0, the value of gmplsTunnelUpstreamNotifyRecipientType MUST be set to unknown(0).
.1.3.6.1.2.1.10.166.13.2.1.1.12,GMPLS-TE-STD-MIB::gmplsTunnelSendResvNotifyRecipientType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object is used to aid in interpretation of gmplsTunnelSendResvNotifyRecipient.
.1.3.6.1.2.1.10.166.13.2.1.1.13,GMPLS-TE-STD-MIB::gmplsTunnelSendResvNotifyRecipient,OCTET,read-create,,current,,Indicates to an upstream LSR the address to which it should send downstream Notify messages relating to this tunnel. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the head end of the tunnel since no Resv messages are sent from that LSR for this tunnel. If set to 0, no Notify Request object will be included in the outgoing Resv messages. This object is interpreted in the context of the value of gmplsTunnelSendResvNotifyRecipientType. If this object is set to 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be set to unknown(0).
.1.3.6.1.2.1.10.166.13.2.1.1.14,GMPLS-TE-STD-MIB::gmplsTunnelDownstreamNotifyRecipientType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object is used to aid in interpretation of gmplsTunnelDownstreamNotifyRecipient.
.1.3.6.1.2.1.10.166.13.2.1.1.15,GMPLS-TE-STD-MIB::gmplsTunnelDownstreamNotifyRecipient,OCTET,read-create,,current,,Indicates the address of the downstream recipient for Notify messages relating to this tunnel and issued by this LSR. This information is typically received from an upstream LSR in a Resv message. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the tail end of a tunnel since there are no downstream LSRs to which to send a Notify message. This object is interpreted in the context of the value of gmplsTunnelDownstreamNotifyRecipientType. If this object is set to 0, the value of gmplsTunnelDownstreamNotifyRecipientType MUST be set to unknown(0).
.1.3.6.1.2.1.10.166.13.2.1.1.16,GMPLS-TE-STD-MIB::gmplsTunnelSendPathNotifyRecipientType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object is used to aid in interpretation of gmplsTunnelSendPathNotifyRecipient.
.1.3.6.1.2.1.10.166.13.2.1.1.17,GMPLS-TE-STD-MIB::gmplsTunnelSendPathNotifyRecipient,OCTET,read-create,,current,,Indicates to a downstream LSR the address to which it should send upstream Notify messages relating to this tunnel. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the tail end of the tunnel since no Path messages are sent from that LSR for this tunnel. If set to 0, no Notify Request object will be included in the outgoing Path messages. This object is interpreted in the context of the value of gmplsTunnelSendPathNotifyRecipientType. If this object is set to 0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be set to unknown(0).
.1.3.6.1.2.1.10.166.13.2.1.1.18,GMPLS-TE-STD-MIB::gmplsTunnelAdminStatusFlags,BITS,read-create,,current,reflect(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):oamFlowsEnabled(23):oamAlarmsEnabled(24):handover(25):lockout(26):inhibitAlarmCommunication(27):callControl(28):testing(29):administrativelyDown(30):deleteInProgress(31),Determines the setting of the Admin Status flags in the Admin Status object or TLV, as described in RFC 3471. Setting this field to a non-zero value will result in the inclusion of the Admin Status object on signaling messages. The values to use are defined in the TEXTUAL-CONVENTION IANAGmplsAdminStatusInformationTC found in the IANA-GMPLS-TC-MIB module. This value of this object can be modified when the corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus is active(1). By doing so, a new signaling message will be triggered including the requested Admin Status object or TLV.
.1.3.6.1.2.1.10.166.13.2.1.1.19,GMPLS-TE-STD-MIB::gmplsTunnelExtraParamsPtr,OBJECT,read-create,,current,,Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, Synchronous Optical Network (SONET) resource usage). Such parameters can be supplied in an external table and referenced from here. A value of zeroDotzero in this attribute indicates that there is no such additional information.
.1.3.6.1.2.1.10.166.13.2.2,GMPLS-TE-STD-MIB::gmplsTunnelHopTable,,not-accessible,,current,,The gmplsTunnelHopTable sparsely extends the mplsTunnelHopTable of MPLS-TE-STD-MIB. It is used to indicate the Explicit Labels to be used in an explicit path for a GMPLS tunnel defined in the mplsTunnelTable and gmplsTunnelTable, when it is established using signaling. It does not insert new hops, but does define new values for hops defined in the mplsTunnelHopTable. Each row in this table is indexed by the same indexes as in the mplsTunnelHopTable. It is acceptable for some rows in the mplsTunnelHopTable to have corresponding entries in this table and some to have no corresponding entry in this table. The storage type for this entry is given by the value of mplsTunnelHopStorageType in the corresponding entry in the mplsTunnelHopTable. The row status of an entry in this table is controlled by mplsTunnelHopRowStatus in the corresponding entry in the mplsTunnelHopTable. That is, it is not permitted to create a row in this table, or to modify an existing row, when the corresponding mplsTunnelHopRowStatus has the value active(1).
.1.3.6.1.2.1.10.166.13.2.2.1,GMPLS-TE-STD-MIB::gmplsTunnelHopEntry,,not-accessible,mplsTunnelHopListIndex:mplsTunnelHopPathOptionIndex:mplsTunnelHopIndex,current,,An entry in this table represents additions to a tunnel hop defined in mplsTunnelHopEntry. At an ingress to a tunnel, an entry in this table is created by a network administrator for an ERLSP to be set up by a signaling protocol. At transit and egress nodes, an entry in this table may be used to represent the explicit path instructions received using the signaling protocol.
.1.3.6.1.2.1.10.166.13.2.2.1.1,GMPLS-TE-STD-MIB::gmplsTunnelHopLabelStatuses,BITS,read-only,,current,forwardPresent(0):reversePresent(1),This bitmask indicates the presence of labels indicated by the gmplsTunnelHopExplicitForwardLabel or gmplsTunnelHopExplicitForwardLabelPtr, and gmplsTunnelHopExplicitReverseLabel or gmplsTunnelHopExplicitReverseLabelPtr objects. For the Present bits, a set bit indicates that a label is present for this hop in the route. This allows zero to be a valid label value.
.1.3.6.1.2.1.10.166.13.2.2.1.2,GMPLS-TE-STD-MIB::gmplsTunnelHopExplicitForwardLabel,Unsigned32,read-create,,current,,If gmplsTunnelHopLabelStatuses object indicates that a Forward Label is present and gmplsTunnelHopExplicitForwardLabelPtr contains the value zeroDotZero, then the label to use on this hop is represented by the value of this object.
.1.3.6.1.2.1.10.166.13.2.2.1.3,GMPLS-TE-STD-MIB::gmplsTunnelHopExplicitForwardLabelPtr,OBJECT,read-create,,current,,If the gmplsTunnelHopLabelStatuses object indicates that a Forward Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the forward direction. If the gmplsTunnelHopLabelStatuses object indicates that a Forward Label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelHopExplicitForwardLabel object.
.1.3.6.1.2.1.10.166.13.2.2.1.4,GMPLS-TE-STD-MIB::gmplsTunnelHopExplicitReverseLabel,Unsigned32,read-create,,current,,If the gmplsTunnelHopLabelStatuses object indicates that a Reverse Label is present and gmplsTunnelHopExplicitReverseLabelPtr contains the value zeroDotZero, then the label to use on this hop is found in this object encoded as a 32-bit integer.
.1.3.6.1.2.1.10.166.13.2.2.1.5,GMPLS-TE-STD-MIB::gmplsTunnelHopExplicitReverseLabelPtr,OBJECT,read-create,,current,,If the gmplsTunnelHopLabelStatuses object indicates that a Reverse Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the reverse direction. If the gmplsTunnelHopLabelStatuses object indicates that a Reverse Label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelHopExplicitReverseLabel object.
.1.3.6.1.2.1.10.166.13.2.3,GMPLS-TE-STD-MIB::gmplsTunnelARHopTable,,not-accessible,,current,,The gmplsTunnelARHopTable sparsely extends the mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate the labels currently in use for a GMPLS tunnel defined in the mplsTunnelTable and gmplsTunnelTable, as reported by the signaling protocol. It does not insert new hops, but does define new values for hops defined in the mplsTunnelARHopTable. Each row in this table is indexed by the same indexes as in the mplsTunnelARHopTable. It is acceptable for some rows in the mplsTunnelARHopTable to have corresponding entries in this table and some to have no corresponding entry in this table. Note that since the information necessary to build entries within this table is not provided by some signaling protocols and might not be returned in all cases of other signaling protocols, implementation of this table and the mplsTunnelARHopTable is optional. Furthermore, since the information in this table is actually provided by the signaling protocol after the path has been set up, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read-only.
.1.3.6.1.2.1.10.166.13.2.3.1,GMPLS-TE-STD-MIB::gmplsTunnelARHopEntry,,not-accessible,mplsTunnelARHopListIndex:mplsTunnelARHopIndex,current,,An entry in this table represents additions to a tunnel hop visible in mplsTunnelARHopEntry. An entry is created by the signaling protocol for a signaled ERLSP set up by the signaling protocol. At any node on the LSP (ingress, transit, or egress), this table and the mplsTunnelARHopTable (if the tables are supported and if the signaling protocol is recording actual route information) contain the actual route of the whole tunnel. If the signaling protocol is not recording the actual route, this table MAY report the information from the gmplsTunnelHopTable or the gmplsTunnelCHopTable. Note that the recording of actual labels is distinct from the recording of the actual route in some signaling protocols. This feature is enabled using the gmplsTunnelAttributes object.
.1.3.6.1.2.1.10.166.13.2.3.1.1,GMPLS-TE-STD-MIB::gmplsTunnelARHopLabelStatuses,BITS,read-only,,current,forwardPresent(0):reversePresent(1):forwardGlobal(2):reverseGlobal(3),This bitmask indicates the presence and status of labels indicated by the gmplsTunnelARHopExplicitForwardLabel or gmplsTunnelARHopExplicitForwardLabelPtr, and gmplsTunnelARHopExplicitReverseLabel or gmplsTunnelARHopExplicitReverseLabelPtr objects. For the Present bits, a set bit indicates that a label is present for this hop in the route. For the Global bits, a set bit indicates that the label comes from the Global Label Space; a clear bit indicates that this is a Per-Interface label. A Global bit only has meaning if the corresponding Present bit is set.
.1.3.6.1.2.1.10.166.13.2.3.1.2,GMPLS-TE-STD-MIB::gmplsTunnelARHopExplicitForwardLabel,Unsigned32,read-only,,current,,If the gmplsTunnelARHopLabelStatuses object indicates that a Forward Label is present and gmplsTunnelARHopExplicitForwardLabelPtr contains the value zeroDotZero, then the label in use on this hop is found in this object encoded as a 32-bit integer.
.1.3.6.1.2.1.10.166.13.2.3.1.3,GMPLS-TE-STD-MIB::gmplsTunnelARHopExplicitForwardLabelPtr,OBJECT,read-only,,current,,If the gmplsTunnelARHopLabelStatuses object indicates that a Forward Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label in use on this hop in the forward direction. If the gmplsTunnelARHopLabelStatuses object indicates that a Forward Label is present and this object contains the value zeroDotZero, then the label in use on this hop is found in the gmplsTunnelARHopExplicitForwardLabel object.
.1.3.6.1.2.1.10.166.13.2.3.1.4,GMPLS-TE-STD-MIB::gmplsTunnelARHopExplicitReverseLabel,Unsigned32,read-only,,current,,If the gmplsTunnelARHopLabelStatuses object indicates that a Reverse Label is present and gmplsTunnelARHopExplicitReverseLabelPtr contains the value zeroDotZero, then the label in use on this hop is found in this object encoded as a 32-bit integer.
.1.3.6.1.2.1.10.166.13.2.3.1.5,GMPLS-TE-STD-MIB::gmplsTunnelARHopExplicitReverseLabelPtr,OBJECT,read-only,,current,,If the gmplsTunnelARHopLabelStatuses object indicates that a Reverse Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label in use on this hop in the reverse direction. If the gmplsTunnelARHopLabelStatuses object indicates that a Reverse Label is present and this object contains the value zeroDotZero, then the label in use on this hop is found in the gmplsTunnelARHopExplicitReverseLabel object.
.1.3.6.1.2.1.10.166.13.2.3.1.6,GMPLS-TE-STD-MIB::gmplsTunnelARHopProtection,BITS,read-only,,current,localAvailable(0):localInUse(1),Availability and usage of protection on the reported link. localAvailable This flag is set to indicate that the link downstream of this node is protected via a local repair mechanism. localInUse This flag is set to indicate that a local repair mechanism is in use to maintain this tunnel (usually in the face of an outage of the link it was previously routed over).
.1.3.6.1.2.1.10.166.13.2.4,GMPLS-TE-STD-MIB::gmplsTunnelCHopTable,,not-accessible,,current,,The gmplsTunnelCHopTable sparsely extends the mplsTunnelCHopTable of MPLS-TE-STD-MIB. It is used to indicate additional information about the hops of a GMPLS tunnel defined in the mplsTunnelTable and gmplsTunnelTable, as computed by a constraint-based routing protocol, based on the mplsTunnelHopTable and the gmplsTunnelHopTable. Each row in this table is indexed by the same indexes as in the mplsTunnelCHopTable. It is acceptable for some rows in the mplsTunnelCHopTable to have corresponding entries in this table and some to have no corresponding entry in this table. Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional. Furthermore, since the information in this table is actually provided by a path computation component after the path has been computed, the entries in this table are provided only for observation, and hence, all objects in this table are accessible exclusively as read-only.
.1.3.6.1.2.1.10.166.13.2.4.1,GMPLS-TE-STD-MIB::gmplsTunnelCHopEntry,,not-accessible,mplsTunnelCHopListIndex:mplsTunnelCHopIndex,current,,An entry in this table represents additions to a computed tunnel hop visible in mplsTunnelCHopEntry. An entry is created by a path computation component based on the hops specified in the corresponding mplsTunnelHopTable and gmplsTunnelHopTable. At a transit LSR, this table (if the table is supported) MAY contain the path computed by a path computation engine on (or on behalf of) the transit LSR.
.1.3.6.1.2.1.10.166.13.2.4.1.1,GMPLS-TE-STD-MIB::gmplsTunnelCHopLabelStatuses,BITS,read-only,,current,forwardPresent(0):reversePresent(1),This bitmask indicates the presence of labels indicated by the gmplsTunnelCHopExplicitForwardLabel or gmplsTunnelCHopExplicitForwardLabelPtr and gmplsTunnelCHopExplicitReverseLabel or gmplsTunnelCHopExplicitReverseLabelPtr objects. A set bit indicates that a label is present for this hop in the route, thus allowing zero to be a valid label value.
.1.3.6.1.2.1.10.166.13.2.4.1.2,GMPLS-TE-STD-MIB::gmplsTunnelCHopExplicitForwardLabel,Unsigned32,read-only,,current,,If the gmplsTunnelCHopLabelStatuses object indicates that a Forward Label is present and gmplsTunnelCHopExplicitForwardLabelPtr contains the value zeroDotZero, then the label to use on this hop is found in this object encoded as a 32-bit integer.
.1.3.6.1.2.1.10.166.13.2.4.1.3,GMPLS-TE-STD-MIB::gmplsTunnelCHopExplicitForwardLabelPtr,OBJECT,read-only,,current,,If the gmplsTunnelCHopLabelStatuses object indicates that a Forward Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the forward direction. If the gmplsTunnelCHopLabelStatuses object indicates that a Forward Label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelCHopExplicitForwardLabel object.
.1.3.6.1.2.1.10.166.13.2.4.1.4,GMPLS-TE-STD-MIB::gmplsTunnelCHopExplicitReverseLabel,Unsigned32,read-only,,current,,If the gmplsTunnelCHopLabelStatuses object indicates that a Reverse Label is present and gmplsTunnelCHopExplicitReverseLabelPtr contains the value zeroDotZero, then the label to use on this hop is found in this object encoded as a 32-bit integer.
.1.3.6.1.2.1.10.166.13.2.4.1.5,GMPLS-TE-STD-MIB::gmplsTunnelCHopExplicitReverseLabelPtr,OBJECT,read-only,,current,,If the gmplsTunnelCHopLabelStatuses object indicates that a Reverse Label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the reverse direction. If the gmplsTunnelCHopLabelStatuses object indicates that a Reverse Label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelCHopExplicitReverseLabel object.
.1.3.6.1.2.1.10.166.13.2.5,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfTable,,not-accessible,,current,,This table augments the gmplsTunnelTable to provide per-tunnel packet performance information for the reverse direction of a bidirectional tunnel. It can be seen as supplementing the mplsTunnelPerfTable, which augments the mplsTunnelTable. For links that do not transport packets, these packet counters cannot be maintained. For such links, attempts to read the objects in this table will return noSuchInstance. A tunnel can be known to be bidirectional by inspecting the gmplsTunnelDirection object.
.1.3.6.1.2.1.10.166.13.2.5.1,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfEntry,,not-accessible,,current,,An entry in this table is created by the LSR for every bidirectional GMPLS tunnel where packets are visible to the LSR.
.1.3.6.1.2.1.10.166.13.2.5.1.1,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfPackets,Counter32,read-only,,current,,Number of packets forwarded on the tunnel in the reverse direction if it is bidirectional. This object represents the 32-bit value of the least significant part of the 64-bit value if both gmplsTunnelReversePerfHCPackets and this object are returned. For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return noSuchInstance.
.1.3.6.1.2.1.10.166.13.2.5.1.2,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfHCPackets,Counter64,read-only,,current,,High-capacity counter for number of packets forwarded on the tunnel in the reverse direction if it is bidirectional. For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return noSuchInstance.
.1.3.6.1.2.1.10.166.13.2.5.1.3,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfErrors,Counter32,read-only,,current,,Number of errored packets received on the tunnel in the reverse direction if it is bidirectional. For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return noSuchInstance.
.1.3.6.1.2.1.10.166.13.2.5.1.4,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfBytes,Counter32,read-only,,current,,Number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional. This object represents the 32-bit value of the least significant part of the 64-bit value if both gmplsTunnelReversePerfHCBytes and this object are returned. For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return noSuchInstance.
.1.3.6.1.2.1.10.166.13.2.5.1.5,GMPLS-TE-STD-MIB::gmplsTunnelReversePerfHCBytes,Counter64,read-only,,current,,High-capacity counter for number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional. For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return noSuchInstance.
.1.3.6.1.2.1.10.166.13.2.6,GMPLS-TE-STD-MIB::gmplsTunnelErrorTable,,not-accessible,,current,,This table augments the mplsTunnelTable. This table provides per-tunnel information about errors. Errors may be detected locally or reported through the signaling protocol. Error reporting is not exclusive to GMPLS, and this table may be applied in MPLS systems. Entries in this table are not persistent over system resets or re-initializations of the management system.
.1.3.6.1.2.1.10.166.13.2.6.1,GMPLS-TE-STD-MIB::gmplsTunnelErrorEntry,,not-accessible,,current,,An entry in this table is created by the LSR for every tunnel where error information is visible to the LSR. Note that systems that read the objects in this table one at a time and do not perform atomic operations to read entire instantiated table rows at once, should, for each conceptual column with valid data, read gmplsTunnelErrorLastTime prior to the other objects in the row and again subsequent to reading the last object of the row. They should verify that the value of gmplsTunnelErrorLastTime did not change and thereby ensure that all data read belongs to the same error event.
.1.3.6.1.2.1.10.166.13.2.6.1.1,GMPLS-TE-STD-MIB::gmplsTunnelErrorLastErrorType,INTEGER,read-only,,current,noError(0):unknown(1):protocol(2):pathComputation(3):localConfiguration(4):localResources(5):localOther(6),The nature of the last error. Provides interpretation context for gmplsTunnelErrorProtocolCode and gmplsTunnelErrorProtocolSubcode. A value of noError(0) shows that there is no error associated with this tunnel and means that the other objects in this table entry (conceptual row) have no meaning. A value of unknown(1) shows that there is an error but that no additional information about the cause is known. The error may have been received in a signaled message or generated locally. A value of protocol(2) or pathComputation(3) indicates the cause of an error and identifies an error that has been received through signaling or will itself be signaled. A value of localConfiguration(4), localResources(5) or localOther(6) identifies an error that has been detected by the local node but that will not be reported through signaling.
.1.3.6.1.2.1.10.166.13.2.6.1.2,GMPLS-TE-STD-MIB::gmplsTunnelErrorLastTime,TimeTicks,read-only,,current,,The time at which the last error occurred. This is presented as the value of SysUpTime when the error occurred or was reported to this node. If gmplsTunnelErrorLastErrorType has the value noError(0), then this object is not valid and should be ignored. Note that entries in this table are not persistent over system resets or re-initializations of the management system.
.1.3.6.1.2.1.10.166.13.2.6.1.3,GMPLS-TE-STD-MIB::gmplsTunnelErrorReporterType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the error reported. This object is used to aid in interpretation of gmplsTunnelErrorReporter.
.1.3.6.1.2.1.10.166.13.2.6.1.4,GMPLS-TE-STD-MIB::gmplsTunnelErrorReporter,OCTET,read-only,,current,,The address of the node reporting the last error, or the address of the resource (such as an interface) associated with the error. If gmplsTunnelErrorLastErrorType has the value noError(0), then this object is not valid and should be ignored. If gmplsTunnelErrorLastErrorType has the value unknown(1), localConfiguration(4), localResources(5), or localOther(6), this object MAY contain a zero value. This object should be interpreted in the context of the value of the object gmplsTunnelErrorReporterType.
.1.3.6.1.2.1.10.166.13.2.6.1.5,GMPLS-TE-STD-MIB::gmplsTunnelErrorCode,Unsigned32,read-only,,current,,The primary error code associated with the last error. The interpretation of this error code depends on the value of gmplsTunnelErrorLastErrorType. If the value of gmplsTunnelErrorLastErrorType is noError(0), the value of this object should be 0 and should be ignored. If the value of gmplsTunnelErrorLastErrorType is protocol(2), the error should be interpreted in the context of the signaling protocol identified by the mplsTunnelSignallingProto object.
.1.3.6.1.2.1.10.166.13.2.6.1.6,GMPLS-TE-STD-MIB::gmplsTunnelErrorSubcode,Unsigned32,read-only,,current,,The secondary error code associated with the last error and the protocol used to signal this tunnel. This value is interpreted in the context of the value of gmplsTunnelErrorCode. If the value of gmplsTunnelErrorLastErrorType is noError(0), the value of this object should be 0 and should be ignored.
.1.3.6.1.2.1.10.166.13.2.6.1.7,GMPLS-TE-STD-MIB::gmplsTunnelErrorTLVs,OCTET,read-only,,current,,The sequence of interface identifier TLVs reported with the error by the protocol code. The interpretation of the TLVs and the encoding within the protocol are described in the references. A value of zero in the first octet indicates that no TLVs are present.
.1.3.6.1.2.1.10.166.13.2.6.1.8,GMPLS-TE-STD-MIB::gmplsTunnelErrorHelpString,OCTET,read-only,,current,,A textual string containing information about the last error, recovery actions, and support advice. If there is no help string, this object contains a zero length string. If the value of gmplsTunnelErrorLastErrorType is noError(0), this object should contain a zero length string, but may contain a help string indicating that there is no error.
.1.3.6.1.2.1.10.166.13.3,GMPLS-TE-STD-MIB::gmplsTeConformance,,,,,,
.1.3.6.1.2.1.10.166.13.3.1,GMPLS-TE-STD-MIB::gmplsTeGroups,,,,,,
.1.3.6.1.2.1.10.166.13.3.1.1,GMPLS-TE-STD-MIB::gmplsTunnelGroup,,,,,,Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the type of the tunnels supported (for example, manually configured or signaled, persistent or non-persistent, etc.), the gmplsTunnelSignaledGroup group is mandatory.
.1.3.6.1.2.1.10.166.13.3.1.2,GMPLS-TE-STD-MIB::gmplsTunnelSignaledGroup,,,,,,Objects needed to implement signaled tunnels.
.1.3.6.1.2.1.10.166.13.3.1.3,GMPLS-TE-STD-MIB::gmplsTunnelScalarGroup,,,,,,Scalar objects needed to implement MPLS tunnels.
.1.3.6.1.2.1.10.166.13.3.1.4,GMPLS-TE-STD-MIB::gmplsTunnelOptionalGroup,,,,,,The objects in this group are optional.
.1.3.6.1.2.1.10.166.13.3.1.5,GMPLS-TE-STD-MIB::gmplsTeNotificationGroup,,,,,,Set of notifications implemented in this module. None is mandatory.
.1.3.6.1.2.1.10.166.13.3.2,GMPLS-TE-STD-MIB::gmplsTeCompliances,,,,,,
.1.3.6.1.2.1.10.166.13.3.2.1,GMPLS-TE-STD-MIB::gmplsTeModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for GMPLS-TE-STD-MIB. Such devices can then be monitored and also be configured using this MIB module. The mandatory group has to be implemented by all LSRs that originate, terminate, or act as transit for TE-LSPs/tunnels. In addition, depending on the type of tunnels supported, other groups become mandatory as explained below.
.1.3.6.1.2.1.10.166.13.3.2.2,GMPLS-TE-STD-MIB::gmplsTeModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for GMPLS-TE-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.166.15,GMPLS-LSR-STD-MIB::gmplsLsrStdMIB,,,,,,Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4803; see the RFC itself for full legal notices. This MIB module contains managed object definitions for the Generalized Multiprotocol (GMPLS) Label Switching Router as defined in Generalized Multi-Protocol Label Switching (GMPLS) Architecture, Mannie et al., RFC 3945, October 2004.
.1.3.6.1.2.1.10.166.15.1,GMPLS-LSR-STD-MIB::gmplsLsrObjects,,,,,,
.1.3.6.1.2.1.10.166.15.1.1,GMPLS-LSR-STD-MIB::gmplsInterfaceTable,,not-accessible,,current,,This table specifies per-interface GMPLS capability and associated information. It extends the information in the mplsInterfaceTable of MPLS-LSR-STD-MIB through a sparse augmentation relationship.
.1.3.6.1.2.1.10.166.15.1.1.1,GMPLS-LSR-STD-MIB::gmplsInterfaceEntry,,not-accessible,mplsInterfaceIndex,current,,A conceptual row in this table is created automatically by an LSR for each interface that is both capable of supporting GMPLS and configured to support GMPLS. Note that support of GMPLS is not limited to control plane signaling, but may include data-plane-only function configured through SNMP SET commands performed on this MIB module. A conceptual row in this table may also be created via SNMP SET commands or automatically by the LSR to supplement a conceptual row in the mplsInterfaceTable where the interface is not capable of GMPLS but where the other objects carried in this row provide useful additional information for an MPLS interface. A conceptual row in this table will exist if and only if a corresponding entry in the mplsInterfaceTable exists, and a corresponding entry in the ifTable exists with ifType = mpls(166). If the associated entry in the ifTable is operationally disabled (thus removing the GMPLS capabilities on the interface) or the entry in the mplsInterfaceTable is deleted, the corresponding entry in this table MUST be deleted shortly thereafter. The indexes are the same as for the mplsInterfaceTable. Thus, the entry with index 0 represents the per-platform label space and contains parameters that apply to all interfaces that participate in the per-platform label space.
.1.3.6.1.2.1.10.166.15.1.1.1.1,GMPLS-LSR-STD-MIB::gmplsInterfaceSignalingCaps,BITS,read-create,,current,unknown(0):rsvpGmpls(1):crldpGmpls(2):otherGmpls(3),Defines the signaling capabilities on this interface. Multiple bits may legitimately be set at once, but if 'unknown' is set then no other bit may be set. Setting no bits implies that GMPLS signaling cannot be performed on this interface and all LSPs must be manually provisioned or that this table entry is only present to supplement an entry in the mplsInterfaceTable by providing the information carried in other objects in this row.
.1.3.6.1.2.1.10.166.15.1.1.1.2,GMPLS-LSR-STD-MIB::gmplsInterfaceRsvpHelloPeriod,Unsigned32,read-create,,current,,Period, in milliseconds, between sending Resource Reservation Protocol (RSVP) Hello messages on this interface. A value of 0 indicates that no Hello messages should be sent on this interface. This object is only valid if gmplsInterfaceSignalingCaps has no bits set or includes the rsvpGmpls bit.
.1.3.6.1.2.1.10.166.15.1.2,GMPLS-LSR-STD-MIB::gmplsInSegmentTable,,not-accessible,,current,,This table sparse augments the mplsInSegmentTable of MPLS-LSR-STD-MIB to provide GMPLS-specific information about incoming segments to an LSR.
.1.3.6.1.2.1.10.166.15.1.2.1,GMPLS-LSR-STD-MIB::gmplsInSegmentEntry,,not-accessible,mplsInSegmentIndex,current,,An entry in this table extends the representation of an incoming segment represented by an entry in the mplsInSegmentTable in MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events. Note that the storage type for this entry is given by the value of mplsInSegmentStorageType in the corresponding entry of the mplsInSegmentTable.
.1.3.6.1.2.1.10.166.15.1.2.1.1,GMPLS-LSR-STD-MIB::gmplsInSegmentDirection,INTEGER,read-create,,current,forward(1):reverse(2),This object indicates the direction of data flow on this segment. This object cannot be modified if mplsInSegmentRowStatus for the corresponding entry in the mplsInSegmentTable is active(1).
.1.3.6.1.2.1.10.166.15.1.2.1.2,GMPLS-LSR-STD-MIB::gmplsInSegmentExtraParamsPtr,OBJECT,read-create,,current,,Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, Synchronous Optical Network (SONET) resource usage). Such can be supplied from an external table and referenced from here. A value of zeroDotZero in this attribute indicates that there is no such additional information.
.1.3.6.1.2.1.10.166.15.1.3,GMPLS-LSR-STD-MIB::gmplsOutSegmentTable,,not-accessible,,current,,This table sparse augments the mplsOutSegmentTable of MPLS-LSR-STD-MIB to provide GMPLS-specific information about outgoing segments from an LSR.
.1.3.6.1.2.1.10.166.15.1.3.1,GMPLS-LSR-STD-MIB::gmplsOutSegmentEntry,,not-accessible,mplsOutSegmentIndex,current,,An entry in this table extends the representation of an outgoing segment represented by an entry in the mplsOutSegmentTable of MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be created by a network administrator via SNMP SET commands, or in response to signaling protocol events. Note that the storage type for this entry is given by the value of mplsOutSegmentStorageType in the corresponding entry of the mplsOutSegmentTable.
.1.3.6.1.2.1.10.166.15.1.3.1.1,GMPLS-LSR-STD-MIB::gmplsOutSegmentDirection,INTEGER,read-create,,current,forward(1):reverse(2),This object indicates the direction of data flow on this segment. This object cannot be modified if mplsOutSegmentRowStatus for the corresponding entry in the mplsOutSegmentTable is active(1).
.1.3.6.1.2.1.10.166.15.1.3.1.2,GMPLS-LSR-STD-MIB::gmplsOutSegmentTTLDecrement,Unsigned32,read-create,,current,,This object indicates the amount by which to decrement the Time to Live (TTL) of any payload packets forwarded on this segment if per-hop decrementing is being done. A value of zero indicates that no decrement should be made or that per-hop decrementing is not in use. See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable of GMPLS-TE-STD-MIB for a value by which to decrement the TTL for the whole of a tunnel. This object cannot be modified if mplsOutSegmentRowStatus for the associated entry in the mplsOutSegmentTable is active(1).
.1.3.6.1.2.1.10.166.15.1.3.1.3,GMPLS-LSR-STD-MIB::gmplsOutSegmentExtraParamsPtr,OBJECT,read-create,,current,,Some tunnels will run over transports that can usefully support technology-specific additional parameters (for example, SONET resource usage). Such can be supplied from an external table and referenced from here. A value of zeroDotZero in this attribute indicates that there is no such additional information.
.1.3.6.1.2.1.10.166.15.2,GMPLS-LSR-STD-MIB::gmplsLsrConformance,,,,,,
.1.3.6.1.2.1.10.166.15.2.1,GMPLS-LSR-STD-MIB::gmplsLsrGroups,,,,,,
.1.3.6.1.2.1.10.166.15.2.1.1,GMPLS-LSR-STD-MIB::gmplsInterfaceGroup,,,,,,Collection of objects that provide additional information for an MPLS interface and are needed for GMPLS interface configuration and performance information.
.1.3.6.1.2.1.10.166.15.2.1.2,GMPLS-LSR-STD-MIB::gmplsInSegmentGroup,,,,,,Collection of objects that provide additional information for an MPLS in-segment and are needed for GMPLS in-segment configuration and performance information.
.1.3.6.1.2.1.10.166.15.2.1.3,GMPLS-LSR-STD-MIB::gmplsOutSegmentGroup,,,,,,Collection of objects that provide additional information for an MPLS out-segment and are needed for GMPLS out-segment configuration and performance information.
.1.3.6.1.2.1.10.166.15.2.2,GMPLS-LSR-STD-MIB::gmplsLsrCompliances,,,,,,
.1.3.6.1.2.1.10.166.15.2.2.1,GMPLS-LSR-STD-MIB::gmplsLsrModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for GMPLS-LSR-STD-MIB. The mandatory group has to be implemented by all LSRs that originate, terminate, or act as transit for TE-LSPs/tunnels. In addition, depending on the type of tunnels supported, other groups become mandatory as explained below.
.1.3.6.1.2.1.10.166.15.2.2.2,GMPLS-LSR-STD-MIB::gmplsLsrModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for GMPLS-LSR-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.166.16,GMPLS-LABEL-STD-MIB::gmplsLabelStdMIB,,,,,,Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4803; see the RFC itself for full legal notices. This MIB module contains managed object definitions for labels within GMPLS systems as defined in Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, Berger, L. (Editor), RFC 3471, January 2003.
.1.3.6.1.2.1.10.166.16.1,GMPLS-LABEL-STD-MIB::gmplsLabelObjects,,,,,,
.1.3.6.1.2.1.10.166.16.1.1,GMPLS-LABEL-STD-MIB::gmplsLabelIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for gmplsLabelIndex, or a zero to indicate that no unused value exists or is available. A management application wishing to create a row in the gmplsLabelTable may read this object and then attempt to create a row in the table. If row creation fails (because another application has already created a row with the supplied index), the management application should read this object again to get a new index value. When a row is created in the gmplsLabelTable with the gmplsLabelIndex value held by this object, an implementation MUST change the value in this object.
.1.3.6.1.2.1.10.166.16.1.2,GMPLS-LABEL-STD-MIB::gmplsLabelTable,,not-accessible,,current,,Table of GMPLS Labels. This table allows the representation of the more complex label forms required for GMPLS that cannot be held within the TEXTUAL-CONVENTION MplsLabel; that is, labels that cannot be encoded within 32 bits. It is, nevertheless, also capable of holding 32-bit labels or regular MPLS Labels if desired. Each entry in this table represents an individual GMPLS Label value. The representation of Labels in tables in other MIB modules may be achieved by a referrence to an entry in this table by means of a row pointer into this table. The indexing of this table provides for arbitrary indexing and also for concatenation of labels. For an example of label concatenation, see RFC 3945, section 7.1. In essence, a GMPLS Label may be composite in order to identify a set of resources in the data plane. Practical examples are timeslots and wavelength sets (which are not contiguous like wavebands). The indexing mechanism allows multiple entries in this table to be seen as a sequence of labels that should be concatenated. Ordering is potentially very sensitive for concatenation.
.1.3.6.1.2.1.10.166.16.1.2.1,GMPLS-LABEL-STD-MIB::gmplsLabelEntry,,not-accessible,gmplsLabelInterface:gmplsLabelIndex:gmplsLabelSubindex,current,,An entry in this table represents a single label value. There are three indexes into the table. - The interface index may be helpful to distinguish which labels are in use on which interfaces or to handle cases where there are a very large number of labels in use in the system. When label representation is desired to apply to the whole system or when it is not important to distinguish labels by their interfaces, this index MAY be set to zero. - The label index provides a way of identifying the label. - The label sub-index is only used for concatenated labels. It identifies each component label. When non-concatenated labels are used, this index SHOULD be set to zero. A storage type object is supplied to control the storage type for each entry, but implementations should note that the storage type of conceptual rows in other tables that include row pointers to an entry in this table SHOULD dictate the storage type of the rows in this table where the row in the other table is more persistent.
.1.3.6.1.2.1.10.166.16.1.2.1.1,GMPLS-LABEL-STD-MIB::gmplsLabelInterface,Integer32,not-accessible,,current,,The interface on which this label is used. If this object is set to zero, the label MUST have applicability across the whole system and not be limited to a single interface.
.1.3.6.1.2.1.10.166.16.1.2.1.2,GMPLS-LABEL-STD-MIB::gmplsLabelIndex,Unsigned32,not-accessible,,current,,An arbitrary index into the table to identify a label. Note that implementations that are representing 32-bit labels within this table MAY choose to align this index with the value of the label, and this may result in the use of the value zero since it represents a valid label value. Such implementation should be aware of the implications of sparsely populated tables. A management application may read the gmplsLabelIndexNext object to find a suitable value for this object.
.1.3.6.1.2.1.10.166.16.1.2.1.3,GMPLS-LABEL-STD-MIB::gmplsLabelSubindex,Unsigned32,not-accessible,,current,,In conjunction with gmplsLabelInterface and gmplsLabelIndex, this object uniquely identifies this row. This sub-index allows a single GMPLS Label to be defined as a concatenation of labels. This is particularly useful in TDM. The ordering of sub-labels is strict with the sub-label with the lowest gmplsLabelSubindex appearing first. Note that all sub-labels of a single GMPLS Label must share the same gmplsLabelInterface and gmplsLabelIndex values. For labels that are not composed of concatenated sub-labels, this value SHOULD be set to zero.
.1.3.6.1.2.1.10.166.16.1.2.1.4,GMPLS-LABEL-STD-MIB::gmplsLabelType,INTEGER,read-create,,current,gmplsMplsLabel(1):gmplsPortWavelengthLabel(2):gmplsFreeformGeneralizedLabel(3):gmplsSonetLabel(4):gmplsSdhLabel(5):gmplsWavebandLabel(6),Identifies the type of this label. Note that this object does not determine whether MPLS or GMPLS signaling is in use: a value of gmplsMplsLabel(1) denotes that an MPLS Packet Label is present in the gmplsLabelMplsLabel object and encoded using the MplsLabel TEXTUAL-CONVENTION (may be a 20-bit MPLS Label, a 10- or 23-bit Frame Relay Label, or an Asynchronous Transfer Mode (ATM) Label), but does not describe whether this is signaled using MPLS or GMPLS. The value of this object helps determine which of the following objects are valid. This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.5,GMPLS-LABEL-STD-MIB::gmplsLabelMplsLabel,Unsigned32,read-create,,current,,The value of an MPLS Label (that is a Packet Label) if this table is used to store it. This may be used in MPLS systems even though the label values can be adequately stored in the MPLS MIB modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Furthermore, in mixed MPLS and GMPLS systems, it may be advantageous to store all labels in a single label table. Lastly, in GMPLS systems where Packet Labels are used (that is in systems that use GMPLS signaling and GMPLS Labels for packet switching), it may be desirable to use this table. This object is only valid if gmplsLabelType is set to gmplsMplsLabel(1). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.6,GMPLS-LABEL-STD-MIB::gmplsLabelPortWavelength,Unsigned32,read-create,,current,,The value of a Port or Wavelength Label when carried as a Generalized Label. Only valid if gmplsLabelType is set to gmplsPortWavelengthLabel(2). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.7,GMPLS-LABEL-STD-MIB::gmplsLabelFreeform,OCTET,read-create,,current,,The value of a Freeform Generalized Label that does not conform to one of the standardized label encodings or that an implementation chooses to represent as an octet string without further decoding. Only valid if gmplsLabelType is set to gmplsFreeformLabel(3). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.8,GMPLS-LABEL-STD-MIB::gmplsLabelSonetSdhSignalIndex,Integer32,read-create,,current,,The Signal Index value (S) of a SONET or SDH Generalized Label. Zero indicates that this field is non-significant. Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.9,GMPLS-LABEL-STD-MIB::gmplsLabelSdhVc,Integer32,read-create,,current,,The VC Indicator (U) of an SDH Generalized Label. Zero indicates that this field is non-significant. Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.10,GMPLS-LABEL-STD-MIB::gmplsLabelSdhVcBranch,Integer32,read-create,,current,,The VC Branch Indicator (K) of an SDH Generalized Label. Zero indicates that this field is non-significant. Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.11,GMPLS-LABEL-STD-MIB::gmplsLabelSonetSdhBranch,Integer32,read-create,,current,,The Branch Indicator (L) of a SONET or SDH Generalized Label. Zero indicates that this field is non-significant. Only valid gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.12,GMPLS-LABEL-STD-MIB::gmplsLabelSonetSdhGroupBranch,Integer32,read-create,,current,,The Group Branch Indicator (M) of a SONET or SDH Generalized Label. Zero indicates that this field is non-significant. Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.13,GMPLS-LABEL-STD-MIB::gmplsLabelWavebandId,Unsigned32,read-create,,current,,The waveband identifier component of a Waveband Label. Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.14,GMPLS-LABEL-STD-MIB::gmplsLabelWavebandStart,Unsigned32,read-create,,current,,The starting label component of a Waveband Label. Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.15,GMPLS-LABEL-STD-MIB::gmplsLabelWavebandEnd,Unsigned32,read-create,,current,,The end label component of a Waveband Label. Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). This object cannot be modified if gmplsLabelRowStatus is active(1).
.1.3.6.1.2.1.10.166.16.1.2.1.16,GMPLS-LABEL-STD-MIB::gmplsLabelStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row. The agent MUST ensure that this object's value remains consistent with the storage type of any rows in other tables that contain pointers to this row. In particular, the storage type of this row must be at least as permanent as that of any row that points to it. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.16.1.2.1.17,GMPLS-LABEL-STD-MIB::gmplsLabelRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the gmplsLabelRowStatus and gmplsLabelStorageType. The gmplsLabelType object does not have a default and must be set before a row can become active. The corresponding label objects (dependent on the value of gmplsLabelType) should also be set unless they happen to need to use the specified default values as follows: gmplsLabelType setting objects to be set -------------------------------------------------------------- gmplsMplsLabel(1) gmplsLabelMplsLabel gmplsPortWavelengthLabel(2) gmplsLabelPortWavelength gmplsFreeformLabel(3) gmplsLabelFreeform gmplsSonetLabel(4) gmplsLabelSonetSdhSignalIndex gmplsLabelSdhVc gmplsLabelSdhVcBranch gmplsLabelSonetSdhBranch gmplsLabelSonetSdhGroupBranch gmplsSdhLabel(5) gmplsLabelSonetSdhSignalIndex gmplsLabelSdhVc gmplsLabelSdhVcBranch gmplsLabelSonetSdhBranch gmplsLabelSonetSdhGroupBranch gmplsWavebandLabel(6) gmplsLabelWavebandId gmplsLabelWavebandStart gmplsLabelWavebandEnd
.1.3.6.1.2.1.10.166.16.2,GMPLS-LABEL-STD-MIB::gmplsLabelConformance,,,,,,
.1.3.6.1.2.1.10.166.16.2.1,GMPLS-LABEL-STD-MIB::gmplsLabelGroups,,,,,,
.1.3.6.1.2.1.10.166.16.2.1.1,GMPLS-LABEL-STD-MIB::gmplsLabelTableGroup,,,,,,Necessary, but not sufficient, set of objects to implement label table support. In addition, depending on the type of labels supported, the following other groups defined below are mandatory: gmplsLabelWavebandGroup and/or gmplsLabelPacketGroup and/or gmplsLabelPortWavelengthGroup and/or gmplsLabelFreeformGroup and/or gmplsLabelSonetSdhGroup.
.1.3.6.1.2.1.10.166.16.2.1.2,GMPLS-LABEL-STD-MIB::gmplsLabelPacketGroup,,,,,,Object needed to implement Packet (MPLS) Labels.
.1.3.6.1.2.1.10.166.16.2.1.3,GMPLS-LABEL-STD-MIB::gmplsLabelPortWavelengthGroup,,,,,,Object needed to implement Port and Wavelength Labels.
.1.3.6.1.2.1.10.166.16.2.1.4,GMPLS-LABEL-STD-MIB::gmplsLabelFreeformGroup,,,,,,Object needed to implement Freeform Labels.
.1.3.6.1.2.1.10.166.16.2.1.5,GMPLS-LABEL-STD-MIB::gmplsLabelSonetSdhGroup,,,,,,Objects needed to implement SONET and SDH Labels.
.1.3.6.1.2.1.10.166.16.2.1.6,GMPLS-LABEL-STD-MIB::gmplsLabelWavebandGroup,,,,,,Objects needed to implement Waveband Labels.
.1.3.6.1.2.1.10.166.16.2.2,GMPLS-LABEL-STD-MIB::gmplsLabelCompliances,,,,,,
.1.3.6.1.2.1.10.166.16.2.2.1,GMPLS-LABEL-STD-MIB::gmplsLabelModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for GMPLS-LABEL-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.166.16.2.2.2,GMPLS-LABEL-STD-MIB::gmplsLabelModuleFullCompliance,,,,,,Compliance statement for agents that support the complete GMPLS-LABEL-STD-MIB module. The mandatory groups have to be implemented by GMPLS LSRs claiming support for this MIB module. This MIB module is, however, not mandatory for a working implementation of a GMPLS LSR with full MIB support if the GMPLS Labels in use can be represented within a 32-bit quantity.
.1.3.6.1.2.1.10.166.17,MPLS-TC-EXT-STD-MIB::mplsTcExtStdMIB,,,,,,This MIB module contains Textual Conventions for LSPs of MPLS- based transport networks. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.10.166.18,MPLS-ID-STD-MIB::mplsIdStdMIB,,,,,,This MIB module contains identifier object definitions for MPLS Traffic Engineering in transport networks. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.10.166.18.0,MPLS-ID-STD-MIB::mplsIdNotifications,,,,,,
.1.3.6.1.2.1.10.166.18.1,MPLS-ID-STD-MIB::mplsIdObjects,,,,,,
.1.3.6.1.2.1.10.166.18.1.1,MPLS-ID-STD-MIB::mplsIdGlobalId,OCTET,read-write,,current,,This object allows the operator or service provider to assign a unique operator identifier, also called the MPLS-TP Global_ID. If this value is used in mplsTunnelExtNodeConfigGlobalId for mapping Global_ID::Node_ID with the local identifier, then this object value MUST NOT be changed.
.1.3.6.1.2.1.10.166.18.1.2,MPLS-ID-STD-MIB::mplsIdNodeId,Unsigned32,read-write,,current,,This object allows the operator or service provider to assign a unique MPLS-TP Node_ID. The Node_ID is assigned within the scope of the Global_ID/ICC_Operator_ID. If this value is used in mplsTunnelExtNodeConfigNodeId for mapping Global_ID::Node_ID with the local identifier, then this object value SHOULD NOT be changed. If this value is used in mplsTunnelExtNodeConfigNodeId for mapping ICC_Operator_ID::Node_ID with the local identifier, then this object value MUST NOT be changed.
.1.3.6.1.2.1.10.166.18.1.3,MPLS-ID-STD-MIB::mplsIdCc,OCTET,read-write,,current,,This object allows the operator or service provider to assign a Country Code (CC) to the node. Global uniqueness of ICC is assured by concatenating the ICC with a Country Code (CC). If this value is used in mplsTunnelExtNodeConfigCcId for mapping ICC_Operator_ID::Node_ID with the local identifier, then this object value MUST NOT be changed.
.1.3.6.1.2.1.10.166.18.1.4,MPLS-ID-STD-MIB::mplsIdIcc,OCTET,read-write,,current,,This object allows the operator or service provider to assign a unique MPLS-TP ITU-T Carrier Code (ICC) to the node. Together, the CC and the ICC form the ICC_Operator_ID as CC::ICC. If this value is used in mplsTunnelExtNodeConfigIccId for mapping ICC_Operator_ID::Node_ID with the local identifier, then this object value MUST NOT be changed.
.1.3.6.1.2.1.10.166.18.2,MPLS-ID-STD-MIB::mplsIdConformance,,,,,,
.1.3.6.1.2.1.10.166.18.2.1,MPLS-ID-STD-MIB::mplsIdCompliances,,,,,,
.1.3.6.1.2.1.10.166.18.2.1.1,MPLS-ID-STD-MIB::mplsIdModuleFullCompliance,,,,,,Compliance statement for agents that provide full support of the MPLS-ID-STD-MIB module.
.1.3.6.1.2.1.10.166.18.2.1.2,MPLS-ID-STD-MIB::mplsIdModuleReadOnlyCompliance,,,,,,Compliance statement for agents that only provide read-only support for the MPLS-ID-STD-MIB module.
.1.3.6.1.2.1.10.166.18.2.2,MPLS-ID-STD-MIB::mplsIdGroups,,,,,,
.1.3.6.1.2.1.10.166.18.2.2.1,MPLS-ID-STD-MIB::mplsIdIpOperatorGroup,,,,,,The objects in this group are optional for an ICC-based node.
.1.3.6.1.2.1.10.166.18.2.2.2,MPLS-ID-STD-MIB::mplsIdIccOperatorGroup,,,,,,The objects in this group are optional for an IP-based node.
.1.3.6.1.2.1.10.166.19,MPLS-LSR-EXT-STD-MIB::mplsLsrExtStdMIB,,,,,,This MIB module contains generic object definitions for MPLS LSRs in transport networks. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.10.166.19.0,MPLS-LSR-EXT-STD-MIB::mplsLsrExtNotifications,,,,,,
.1.3.6.1.2.1.10.166.19.1,MPLS-LSR-EXT-STD-MIB::mplsLsrExtObjects,,,,,,
.1.3.6.1.2.1.10.166.19.1.1,MPLS-LSR-EXT-STD-MIB::mplsXCExtTable,,not-accessible,,current,,This table sparse augments the mplsXCTable of MPLS-LSR-STD-MIB (RFC 3813) to provide MPLS-TP-specific information about associated tunnel information
.1.3.6.1.2.1.10.166.19.1.1.1,MPLS-LSR-EXT-STD-MIB::mplsXCExtEntry,,not-accessible,mplsXCIndex:mplsXCInSegmentIndex:mplsXCOutSegmentIndex,current,,An entry in this table sparsely extends the cross-connect information represented by an entry in the mplsXCTable in MPLS-LSR-STD-MIB (RFC 3813) through a sparse augmentation. An entry can be created by a network operator via SNMP SET commands or in response to signaling protocol events.
.1.3.6.1.2.1.10.166.19.1.1.1.1,MPLS-LSR-EXT-STD-MIB::mplsXCExtTunnelPointer,OBJECT,read-only,,current,,This read-only object indicates the back pointer to the tunnel entry segment. The only valid value for Tunnel Pointer is mplsTunnelTable entry.
.1.3.6.1.2.1.10.166.19.1.1.1.2,MPLS-LSR-EXT-STD-MIB::mplsXCExtOppositeDirXCPtr,OBJECT,read-create,,current,,This object indicates the pointer to the opposite- direction XC entry. This object cannot be modified if mplsXCRowStatus for the corresponding entry in the mplsXCTable is active(1). If this pointer is not set or removed, mplsXCOperStatus should be set to down(2).
.1.3.6.1.2.1.10.166.19.2,MPLS-LSR-EXT-STD-MIB::mplsLsrExtConformance,,,,,,
.1.3.6.1.2.1.10.166.19.2.1,MPLS-LSR-EXT-STD-MIB::mplsLsrExtCompliances,,,,,,
.1.3.6.1.2.1.10.166.19.2.1.1,MPLS-LSR-EXT-STD-MIB::mplsLsrExtModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for MPLS-LSR-EXT-STD-MIB. The mandatory group has to be implemented by all LSRs that originate, terminate, or act as transit for TE-LSPs/tunnels. In addition, depending on the type of tunnels supported, other groups become mandatory as explained below.
.1.3.6.1.2.1.10.166.19.2.1.2,MPLS-LSR-EXT-STD-MIB::mplsLsrExtModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for MPLS-LSR-EXT-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.166.19.2.2,MPLS-LSR-EXT-STD-MIB::mplsLsrExtGroups,,,,,,
.1.3.6.1.2.1.10.166.19.2.2.1,MPLS-LSR-EXT-STD-MIB::mplsXCExtGroup,,,,,,This object should be supported in order to access the tunnel entry from the XC entry.
.1.3.6.1.2.1.10.166.19.2.2.2,MPLS-LSR-EXT-STD-MIB::mplsXCExtReadOnlyObjectsGroup,,,,,,This Object is needed to associate the opposite-direction (forward/reverse) XC entry.
.1.3.6.1.2.1.10.166.20,MPLS-TE-EXT-STD-MIB::mplsTeExtStdMIB,,,,,,This MIB module contains generic object definitions for extending the MPLS Traffic Engineering tunnels in transport networks. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.10.166.20.0,MPLS-TE-EXT-STD-MIB::mplsTeExtObjects,,,,,,
.1.3.6.1.2.1.10.166.20.0.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigLocalIdNext,Unsigned32,read-only,,current,,This object contains an unused value for mplsTunnelExtNodeConfigLocalId, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsTunnelExtNodeConfigLocalId.
.1.3.6.1.2.1.10.166.20.0.2,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigTable,,not-accessible,,current,,This table allows the operator to map a node or LSR identifier (IP-compatible [Global_ID::Node_ID] or ICC-based [ICC_Operator_ID::Node_ID]) with a local identifier. This table is created to reuse the existing mplsTunnelTable for MPLS-based transport network tunnels also. Since the MPLS tunnel's Ingress/Egress LSR identifiers' size (Unsigned32) value is not compatible for MPLS-TP Tunnel, i.e., Global_ID::Node_ID of size 8 bytes and ICC_Operator_ID::Node_ID of size 12 bytes, there exists a need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID with the local identifier of size 4 bytes (Unsigned32) value in order to index (Ingress/Egress LSR identifier) the existing mplsTunnelTable.
.1.3.6.1.2.1.10.166.20.0.2.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigEntry,,not-accessible,mplsTunnelExtNodeConfigLocalId,current,,An entry in this table represents a mapping identification for the operator or service provider to a node or an LSR. As per RFC 6370, IP-compatible mapping is represented as Global_ID::Node_ID. As per RFC 6923, the CC and the ICC form the ICC_Operator_ID as CC::ICC, and ICC-compatible mapping is represented as ICC_Operator_ID::Node_ID. Note: Each entry in this table should have a unique [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination.
.1.3.6.1.2.1.10.166.20.0.2.1.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigLocalId,Unsigned32,not-accessible,,current,,This object is used in accommodating the bigger- size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID with the smaller-size LSR identifier in order to index the mplsTunnelTable. The local identifier is configured between 0 and 16777215, as the valid IP address range starts from 16777216(01.00.00.00). This range is chosen to determine whether the mplsTunnelTable's Ingress/Egress LSR ID is an IP address or local identifier. If the configured range is not an IP address, the operator is expected to retrieve the complete information (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from mplsTunnelExtNodeConfigTable. This way, the existing mplsTunnelTable is reused for bidirectional tunnel extensions for MPLS-based transport networks. The local identifier allows the operator to assign a unique identifier to map Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID. As this local identifier is unique within the node and the same syntax of this object can be used for MPLS-TE tunnel also, it is up to the operator/local management entity to choose a non-conflicting value for indexing the MPLS and MPLS-TP tunnel entries.
.1.3.6.1.2.1.10.166.20.0.2.1.2,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigGlobalId,OCTET,read-create,,current,,This object indicates the Global Operator Identifier. This object has no meaning when mplsTunnelExtNodeConfigIccValid is set true.
.1.3.6.1.2.1.10.166.20.0.2.1.3,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigCcId,OCTET,read-create,,current,,This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress ID or Egress ID. This object has no meaning when mplsTunnelExtNodeConfigIccValid is set to false.
.1.3.6.1.2.1.10.166.20.0.2.1.4,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigIccId,OCTET,read-create,,current,,This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Carrier Code (ICC) either for Ingress ID or Egress ID. This object has no meaning when mplsTunnelExtNodeConfigIccValid is set to false.
.1.3.6.1.2.1.10.166.20.0.2.1.5,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigNodeId,Unsigned32,read-create,,current,,This object indicates the Node_ID within the scope of a Global_ID or ICC_Operator_ID.
.1.3.6.1.2.1.10.166.20.0.2.1.6,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigIccValid,INTEGER,read-create,,current,true(1):false(2),Denotes whether or not this entry uses mplsTunnelExtNodeConfigCcId, mplsTunnelExtNodeConfigIccId, and mplsTunnelExtNodeConfigNodeId for mapping the ICC-based identifiers with the local identifier. Note that if this variable is set to false, then the mplsTunnelExtNodeConfigGlobalId and mplsTunnelExtNodeConfigNodeId objects should have the valid information.
.1.3.6.1.2.1.10.166.20.0.2.1.7,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.20.0.2.1.8,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows the operator to create, modify, and/or delete a row in this table.
.1.3.6.1.2.1.10.166.20.0.3,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIpMapTable,,not-accessible,,current,,This read-only table allows the operator to retrieve the local identifier for a given Global_ID::Node_ID in an IP-compatible operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier (local identifier) from Src-Global_Node_ID or Dst-Global_Node_ID. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable.
.1.3.6.1.2.1.10.166.20.0.3.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIpMapEntry,,not-accessible,mplsTunnelExtNodeIpMapGlobalId:mplsTunnelExtNodeIpMapNodeId,current,,An entry in this table represents a mapping of Global_ID::Node_ID with the local identifier. An entry in this table is created automatically when the local identifier is associated with Global_ID and Node_Id in the mplsTunnelExtNodeConfigTable. Note: Each entry in this table should have a unique Global_ID and Node_ID combination.
.1.3.6.1.2.1.10.166.20.0.3.1.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIpMapGlobalId,OCTET,not-accessible,,current,,This object indicates the Global_ID.
.1.3.6.1.2.1.10.166.20.0.3.1.2,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIpMapNodeId,Unsigned32,not-accessible,,current,,This object indicates the Node_ID within the operator.
.1.3.6.1.2.1.10.166.20.0.3.1.3,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIpMapLocalId,Unsigned32,read-only,,current,,This object contains an IP-compatible local identifier that is defined in mplsTunnelExtNodeConfigTable.
.1.3.6.1.2.1.10.166.20.0.4,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIccMapTable,,not-accessible,,current,,This read-only table allows the operator to retrieve the local identifier for a given ICC_Operator_ID::Node_ID in an ICC operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier (local identifier) from Src-ICC or Dst-ICC. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable.
.1.3.6.1.2.1.10.166.20.0.4.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIccMapEntry,,not-accessible,mplsTunnelExtNodeIccMapCcId:mplsTunnelExtNodeIccMapIccId:mplsTunnelExtNodeIccMapNodeId,current,,An entry in this table represents a mapping of ICC_Operator_ID::Node_ID with the local identifier. An entry in this table is created automatically when the local identifier is associated with ICC_Operator_ID::Node_ID in the mplsTunnelExtNodeConfigTable.
.1.3.6.1.2.1.10.166.20.0.4.1.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIccMapCcId,OCTET,not-accessible,,current,,This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress or Egress LSR ID. The CC is a string of two alphabetic characters represented with uppercase letters (i.e., A-Z).
.1.3.6.1.2.1.10.166.20.0.4.1.2,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIccMapIccId,OCTET,not-accessible,,current,,This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Carrier Code (ICC) either for Ingress or Egress LSR ID. The ICC is a string of one to six characters, each character being either alphabetic (i.e., A-Z) or numeric (i.e., 0-9) characters. Alphabetic characters in the ICC should be represented with uppercase letters.
.1.3.6.1.2.1.10.166.20.0.4.1.3,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIccMapNodeId,Unsigned32,not-accessible,,current,,This object indicates the Node_ID within the ICC-based operator.
.1.3.6.1.2.1.10.166.20.0.4.1.4,MPLS-TE-EXT-STD-MIB::mplsTunnelExtNodeIccMapLocalId,Unsigned32,read-only,,current,,This object contains an ICC-based local identifier that is defined in mplsTunnelExtNodeConfigTable.
.1.3.6.1.2.1.10.166.20.0.5,MPLS-TE-EXT-STD-MIB::mplsTunnelExtTable,,not-accessible,,current,,This table represents extensions to mplsTunnelTable in order to support MPLS-TP Tunnels. As per MPLS-TP Identifiers (RFC 6370), LSP_ID for IP-based co-routed bidirectional tunnel: A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num LSP_ID for IP based associated bidirectional tunnel: A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} mplsTunnelTable is reused for forming the LSP_ID as follows: Source Tunnel_Num is mapped with mplsTunnelIndex, Source Node_ID is mapped with mplsTunnelIngressLSRId, Destination Node_ID is mapped with mplsTunnelEgressLSRId, and LSP_Num is mapped with mplsTunnelInstance. Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID are maintained in the mplsTunnelExtNodeConfigTable. mplsTunnelExtNodeConfigLocalId is used to create an entry in mplsTunnelTable.
.1.3.6.1.2.1.10.166.20.0.5.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtEntry,,not-accessible,mplsTunnelIndex:mplsTunnelInstance:mplsTunnelIngressLSRId:mplsTunnelEgressLSRId,current,,An entry in this table represents additional MPLS-TP- specific tunnel configurations.
.1.3.6.1.2.1.10.166.20.0.5.1.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtOppositeDirPtr,OBJECT,read-create,,current,,This object points to the opposite-direction tunnel entry.
.1.3.6.1.2.1.10.166.20.0.5.1.2,MPLS-TE-EXT-STD-MIB::mplsTunnelExtOppositeDirTnlValid,INTEGER,read-create,,current,true(1):false(2),Denotes whether or not this tunnel uses mplsTunnelExtOppositeDirPtr for identifying the opposite- direction tunnel information. Note that if this variable is set to true, then the mplsTunnelExtOppositeDirPtr should point to the first accessible row of the valid opposite- direction tunnel.
.1.3.6.1.2.1.10.166.20.0.5.1.3,MPLS-TE-EXT-STD-MIB::mplsTunnelExtDestTnlIndex,Unsigned32,read-create,,current,,This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries. The values of this object and the mplsTunnelExtDestTnlLspIndex object together can be used to identify an opposite-direction LSP, i.e., if the mplsTunnelIndex and mplsTunnelInstance hold the value for forward LSP, this object and mplsTunnelExtDestTnlLspIndex can be used to retrieve the reverse-direction LSP and vice versa. This object and mplsTunnelExtDestTnlLspIndex values provide the first two indices of tunnel entry, and the remaining indices can be derived as follows: the Ingress and Egress Identifiers should be swapped in order to index the other direction tunnel.
.1.3.6.1.2.1.10.166.20.0.5.1.4,MPLS-TE-EXT-STD-MIB::mplsTunnelExtDestTnlLspIndex,Unsigned32,read-create,,current,,This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries. This object holds the instance index of the opposite-direction tunnel.
.1.3.6.1.2.1.10.166.20.0.5.1.5,MPLS-TE-EXT-STD-MIB::mplsTunnelExtDestTnlValid,INTEGER,read-create,,current,true(1):false(2),Denotes whether or not this tunnel uses mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlLspIndex for identifying the opposite-direction tunnel information. Note that if this variable is set to true, then the mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlLspIndex objects should have the valid opposite-direction tunnel indices.
.1.3.6.1.2.1.10.166.20.0.5.1.6,MPLS-TE-EXT-STD-MIB::mplsTunnelExtIngressLSRLocalIdValid,INTEGER,read-create,,current,true(1):false(2),This object denotes whether the mplsTunnelIngressLSRId contains the local value that is used to reference the complete Ingress Global_ID::Node_ID or ICC_Operator_ID from the mplsTunnelExtNodeConfigTable. If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference the local identifier with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelIngressId itself provides the complete Ingress LSR ID.
.1.3.6.1.2.1.10.166.20.0.5.1.7,MPLS-TE-EXT-STD-MIB::mplsTunnelExtEgressLSRLocalIdValid,INTEGER,read-create,,current,true(1):false(2),This object denotes whether the mplsTunnelEgressLSRId contains the local value, which is used to reference the complete Egress Global_ID::Node_ID or ICC_Operator_ID::Node_ID from the mplsTunnelExtNodeConfigTable. If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference the local identifier with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelEgressId itself provides the complete Egress LSR ID.
.1.3.6.1.2.1.10.166.20.1,MPLS-TE-EXT-STD-MIB::mplsTeExtConformance,,,,,,
.1.3.6.1.2.1.10.166.20.1.1,MPLS-TE-EXT-STD-MIB::mplsTeExtCompliances,,,,,,
.1.3.6.1.2.1.10.166.20.1.1.1,MPLS-TE-EXT-STD-MIB::mplsTeExtModuleFullCompliance,,,,,,Compliance statement for agents that provide full support the MPLS-TE-EXT-STD-MIB module.
.1.3.6.1.2.1.10.166.20.1.1.2,MPLS-TE-EXT-STD-MIB::mplsTeExtModuleReadOnlyCompliance,,,,,,Compliance statement for agents that only provide read-only support for the MPLS-TE-EXT-STD-MIB module.
.1.3.6.1.2.1.10.166.20.1.2,MPLS-TE-EXT-STD-MIB::mplsTeExtGroups,,,,,,
.1.3.6.1.2.1.10.166.20.1.2.1,MPLS-TE-EXT-STD-MIB::mplsTunnelExtGroup,,,,,,Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the operating environment, the following groups are mandatory.
.1.3.6.1.2.1.10.166.20.1.2.2,MPLS-TE-EXT-STD-MIB::mplsTunnelExtIpOperatorGroup,,,,,,Object(s) needed to implement IP-compatible tunnels.
.1.3.6.1.2.1.10.166.20.1.2.3,MPLS-TE-EXT-STD-MIB::mplsTunnelExtIccOperatorGroup,,,,,,Object(s) needed to implement ICC-based tunnels.
.1.3.6.1.2.1.10.166.21,MPLS-OAM-ID-STD-MIB::mplsOamIdStdMIB,,,,,,Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB module contains generic object definitions for MPLS OAM identifiers.
.1.3.6.1.2.1.10.166.21.0,MPLS-OAM-ID-STD-MIB::mplsOamIdNotifications,,,,,,
.1.3.6.1.2.1.10.166.21.0.1,MPLS-OAM-ID-STD-MIB::mplsOamIdDefectCondition,,,,,,This notification is sent whenever the operational status of the MEG is changed.
.1.3.6.1.2.1.10.166.21.1,MPLS-OAM-ID-STD-MIB::mplsOamIdObjects,,,,,,
.1.3.6.1.2.1.10.166.21.1.1,MPLS-OAM-ID-STD-MIB::mplsOamIdMegIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for mplsOamIdMegIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsOamIdMegIndex.
.1.3.6.1.2.1.10.166.21.1.2,MPLS-OAM-ID-STD-MIB::mplsOamIdMegTable,,not-accessible,,current,,This table contains information about the Maintenance Entity Groups (MEGs). A MEG, as mentioned in the MPLS-TP OAM framework, defines a set of one or more Maintenance Entities (MEs). MEs define a relationship between any two points of a transport path in an OAM domain to which maintenance and monitoring operations apply.
.1.3.6.1.2.1.10.166.21.1.2.1,MPLS-OAM-ID-STD-MIB::mplsOamIdMegEntry,,not-accessible,mplsOamIdMegIndex,current,,An entry in this table represents an MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM framework. When a new entry is created with mplsOamIdMegOperatorType set to ipCompatible (1), then as per RFC 6370 (MEG_ID for an LSP is LSP_ID, and MEG_ID for a PW is PW_Path_ID), MEP_ID can be automatically formed. For a co-routed bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num. For an associated bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}. For an LSP, MEP_ID is formed using Global_ID::Node_ID::Tunnel_Num::LSP_Num. For a PW, MEG_ID is formed using AGI:: A1-{Global_ID::Node_ID::AC_ID}:: Z9-{Global_ID::Node_ID::AC_ID}. For a PW, MEP_ID is formed using AGI::Global_ID::Node_ID::AC_ID. MEP_ID is retrieved from the mplsOamIdMegServicePointer object based on the mplsOamIdMegServicePointerType value. The ICC MEG_ID for an LSP and a PW is formed using the objects mplsOamIdMegIdIcc and mplsOamIdMegIdUmc. MEP_ID can be formed using MEG_ID::MEP_Index.
.1.3.6.1.2.1.10.166.21.1.2.1.1,MPLS-OAM-ID-STD-MIB::mplsOamIdMegIndex,Unsigned32,not-accessible,,current,,Index for the conceptual row identifying a MEG within this MEG table. Managers should obtain new values for row creation in this table by reading mplsOamIdMegIndexNext.
.1.3.6.1.2.1.10.166.21.1.2.1.2,MPLS-OAM-ID-STD-MIB::mplsOamIdMegName,OCTET,read-create,,current,,Each MEG has a unique name amongst all those used or available to a service provider or operator. It facilitates easy identification of administrative responsibility for each MEG.
.1.3.6.1.2.1.10.166.21.1.2.1.3,MPLS-OAM-ID-STD-MIB::mplsOamIdMegOperatorType,INTEGER,read-create,,current,ipCompatible(1):iccBased(2),Indicates the operator type for the MEG. Conceptual rows having 'iccBased' as the operator type MUST have valid values for the objects mplsOamIdMegIdIcc and mplsOamIdMegIdUmc when the row status is active.
.1.3.6.1.2.1.10.166.21.1.2.1.4,MPLS-OAM-ID-STD-MIB::mplsOamIdMegIdCc,OCTET,read-create,,current,,Global uniqueness is assured by concatenating the ICC with a Country Code (CC). The Country Code (alpha-2) is a string of two alphabetic characters represented with uppercase letters (i.e., A-Z). This object MUST contain a non-null value if the MplsOamIdMegOperatorType value is iccBased (2); otherwise, a null value with octet size 0 should be assigned.
.1.3.6.1.2.1.10.166.21.1.2.1.5,MPLS-OAM-ID-STD-MIB::mplsOamIdMegIdIcc,OCTET,read-create,,current,,Unique code assigned to a network operator or service provider; maintained by the ITU-T. This is the ITU Carrier Code used to form the MEGID. This object MUST contain a non-null value if the MplsOamIdMegOperatorType value is iccBased (2); otherwise, a null value with octet size 0 should be assigned.
.1.3.6.1.2.1.10.166.21.1.2.1.6,MPLS-OAM-ID-STD-MIB::mplsOamIdMegIdUmc,OCTET,read-create,,current,,Unique code assigned by a network operator or service provider. This code is appended to mplsOamIdMegIdIcc to form the MEGID. This object MUST contain a non-null value if the MplsOamIdMegOperatorType value is iccBased (2); otherwise, a null value with octet size 0 should be assigned.
.1.3.6.1.2.1.10.166.21.1.2.1.7,MPLS-OAM-ID-STD-MIB::mplsOamIdMegServicePointerType,INTEGER,read-create,,current,tunnel(1):lsp(2):pseudowire(3):section(4),Indicates the service type for the MEG. If the service type indicates tunnel (1), the service pointer in the mplsOamIdMeTable points to an entry in the point-to-point mplsTunnelTable (RFC 3812). If the service type indicates lsp (2), the service pointer in the mplsOamIdMeTable points to an entry in the co-routed or associated bidirectional mplsTunnelTable. If the value is the pseudowire (3) service type, the service pointer in the mplsOamIdMeTable points to an entry in the pwTable (RFC 5601). If the value is the section (4) service type, the service pointer in the mplsOamIdMeTable points to an entry in the mplsTunnelTable (RFC 3812).
.1.3.6.1.2.1.10.166.21.1.2.1.8,MPLS-OAM-ID-STD-MIB::mplsOamIdMegMpLocation,INTEGER,read-create,,current,perNode(1):perInterface(2),Indicates the MP location type for this MEG. If the value is perNode, then the MEG in the LSR supports only perNode MEPs/MIPs, i.e., only one MEP/MIP in an LSR. If the value is perInterface, then the MEG in the LSR supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in an LSR.
.1.3.6.1.2.1.10.166.21.1.2.1.9,MPLS-OAM-ID-STD-MIB::mplsOamIdMegPathFlow,INTEGER,read-create,,current,unidirectionalPointToPoint(1):coRoutedBidirectionalPointToPoint(2):associatedBidirectionalPointToPoint(3):unidirectionalPointToMultiPoint(4),Indicates the transport path flow for this MEG. In the case of a unidirectional point-to-point transport path, a single unidirectional ME is defined to monitor it. In the case of associated bidirectional point-to-point transport paths, two independent unidirectional MEs are defined to independently monitor each direction. In the case of co-routed bidirectional point-to-point transport paths, a single bidirectional ME is defined to monitor both directions congruently. In the case of unidirectional point-to-multipoint transport paths, a single unidirectional ME for each leaf is defined to monitor the transport path from the root to that leaf.
.1.3.6.1.2.1.10.166.21.1.2.1.10,MPLS-OAM-ID-STD-MIB::mplsOamIdMegOperStatus,INTEGER,read-only,,current,up(1):down(2),This object specifies the operational status of the Maintenance Entity Group (MEG). This object is used to send the notification to the SNMP manager about the MEG. The value up (1) indicates that the MEG and its monitored path are operationally up. The value down (2) indicates that the MEG is operationally down. When the value of mplsOamIdMegOperStatus is up (1), all the bits of mplsOamIdMegSubOperStatus must be cleared. When the value of mplsOamIdMegOperStatus is down (2), at least one bit of mplsOamIdMegSubOperStatus must be set.
.1.3.6.1.2.1.10.166.21.1.2.1.11,MPLS-OAM-ID-STD-MIB::mplsOamIdMegSubOperStatus,BITS,read-only,,current,megDown(0):meDown(1):oamAppDown(2):pathDown(3),This object specifies the reason why the MEG operational status, as indicated by the object mplsOamIdMegOperStatus, is down. This object is used to send the notification to the SNMP manager about the MEG. The bit 0 (megDown) indicates that the MEG is down. The bit 1 (meDown) indicates that the ME table is down. The bit 2 (oamAppDown) indicates that the OAM application (LSP or PW) monitored by this MEG is down. Currently, BFD is the only supported OAM application. The bit 3 (pathDown) indicates that the underlying LSP or PW is down.
.1.3.6.1.2.1.10.166.21.1.2.1.12,MPLS-OAM-ID-STD-MIB::mplsOamIdMegRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in the active(1) state, no objects in that row can be modified by the agent except mplsOamIdMegRowStatus.
.1.3.6.1.2.1.10.166.21.1.2.1.13,MPLS-OAM-ID-STD-MIB::mplsOamIdMegStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.21.1.3,MPLS-OAM-ID-STD-MIB::mplsOamIdMeIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for mplsOamIdMeIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsOamIdMeIndex.
.1.3.6.1.2.1.10.166.21.1.4,MPLS-OAM-ID-STD-MIB::mplsOamIdMeMpIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for mplsOamIdMeMpIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsOamIdMeMpIndex.
.1.3.6.1.2.1.10.166.21.1.5,MPLS-OAM-ID-STD-MIB::mplsOamIdMeTable,,not-accessible,,current,,This table contains MPLS-TP ME information. The ME is some portion of a transport path that requires management bounded by two points (called MEPs), and the relationship between those points to which maintenance and monitoring operations apply. This table is generic enough to handle MEP and MIP information within a MEG.
.1.3.6.1.2.1.10.166.21.1.5.1,MPLS-OAM-ID-STD-MIB::mplsOamIdMeEntry,,not-accessible,mplsOamIdMegIndex:mplsOamIdMeIndex:mplsOamIdMeMpIndex,current,,An entry in this table represents an MPLS-TP ME. This entry represents the ME if the source and sink MEPs are defined. An ME is a point-to-point entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs. For a point-to-point LSP, one MEG has one ME, and this ME is associated with two MEPs (source and sink MEPs) within a MEG. Each mplsOamIdMeIndex value denotes the ME within a MEG. In the case of unidirectional point-to-point transport paths, a single unidirectional ME is defined to monitor it, and mplsOamIdMeServicePointer points to a unidirectional point-to-point path. In the case of associated bidirectional point-to-point transport paths, two independent unidirectional MEs are defined to independently monitor each direction, and each mplsOamIdMeServicePointer MIB object points to a unique unidirectional transport path. This has implications for transactions that terminate at or query a MIP, as a return path from a MIP to a source MEP does not necessarily exist within the MEG. In the case of co-routed bidirectional point-to-point transport paths, a single bidirectional ME is defined to monitor both directions congruently, and the mplsOamIdMeServicePointer MIB object points to a co-routed bidirectional point-to-point transport path. In the case of unidirectional point-to-multipoint transport paths, a single unidirectional ME for each leaf is defined to monitor the transport path from the root to that leaf, and each leaf has different transport path information in the mplsOamIdMeServicePointer MIB object. Note that the MplsOamIdMeEntry should be created manually once the MEG is configured for OAM operations.
.1.3.6.1.2.1.10.166.21.1.5.1.1,MPLS-OAM-ID-STD-MIB::mplsOamIdMeIndex,Unsigned32,not-accessible,,current,,Uniquely identifies an ME index within a MEG. Managers should obtain new values for row creation in this table by reading mplsOamIdMeIndexNext.
.1.3.6.1.2.1.10.166.21.1.5.1.2,MPLS-OAM-ID-STD-MIB::mplsOamIdMeMpIndex,Unsigned32,not-accessible,,current,,Indicates the Maintenance Point (MP) index that is used to create multiple MEPs in a node of a single ME. The value of this object can be the MEP index or the MIP index. Managers should obtain new values for row creation in this table by reading mplsOamIdMeMpIndexNext.
.1.3.6.1.2.1.10.166.21.1.5.1.3,MPLS-OAM-ID-STD-MIB::mplsOamIdMeName,OCTET,read-create,,current,,This object denotes the ME name. Each ME has a unique name within a MEG.
.1.3.6.1.2.1.10.166.21.1.5.1.4,MPLS-OAM-ID-STD-MIB::mplsOamIdMeMpIfIndex,Integer32,read-create,,current,,Indicates the MP interface. If the mplsOamIdMegMpLocation object value is perNode (1), the MP interface index should point to the incoming interface or outgoing interface, or be zero (to indicate that the MP OAM packets are initiated from the forwarding engine). If the mplsOamIdMegMpLocation object value is perInterface (2), the MP interface index should point to the incoming interface or outgoing interface.
.1.3.6.1.2.1.10.166.21.1.5.1.5,MPLS-OAM-ID-STD-MIB::mplsOamIdMeSourceMepIndex,Unsigned32,read-create,,current,,Indicates the source MEP index of the ME. This object should be configured if the mplsOamIdMegOperatorType object in the mplsOamIdMegEntry is configured as iccBased (2). If the MEG is configured for an IP-based operator, the value of this object should be set to zero, and the MEP ID will be automatically derived from the service identifiers (MPLS-TP LSP/PW Identifier).
.1.3.6.1.2.1.10.166.21.1.5.1.6,MPLS-OAM-ID-STD-MIB::mplsOamIdMeSinkMepIndex,Unsigned32,read-create,,current,,Indicates the sink MEP index of the ME. This object should be configured if the mplsOamIdMegOperatorType object in the mplsOamIdMegEntry is configured as iccBased (2). If the MEG is configured for an IP-based operator, the value of this object should be set to zero, and the MEP ID will be automatically derived from the service identifiers (MPLS-TP LSP/PW Identifier).
.1.3.6.1.2.1.10.166.21.1.5.1.7,MPLS-OAM-ID-STD-MIB::mplsOamIdMeMpType,INTEGER,read-create,,current,mep(1):mip(2),Indicates the MP type within the MEG. The object should have the value mep (1) only in the ingress or egress nodes of the transport path. The object can have the value mip (2) in the intermediate nodes and possibly in the egress nodes of the transport path.
.1.3.6.1.2.1.10.166.21.1.5.1.8,MPLS-OAM-ID-STD-MIB::mplsOamIdMeMepDirection,INTEGER,read-create,,current,up(1):down(2):notApplicable(3),Indicates the direction of the MEP. This object should be configured if mplsOamIdMeMpType is configured as mep (1); otherwise, notApplicable (3) is set.
.1.3.6.1.2.1.10.166.21.1.5.1.9,MPLS-OAM-ID-STD-MIB::mplsOamIdMeServicePointer,OBJECT,read-create,,current,,This variable represents a pointer to the MPLS-TP transport path. This value MUST point at an entry in the mplsTunnelEntry if mplsOamIdMegServicePointerType is configured as tunnel (1), lsp (2), or section (4), or at an entry in the pwEntry if mplsOamIdMegServicePointerType is configured as pseudowire (3). Note: This service pointer object is placed in the ME table instead of the MEG table, since it will be useful in the point-to-multipoint case, where each ME will point to different branches of a point-to-multipoint tree.
.1.3.6.1.2.1.10.166.21.1.5.1.10,MPLS-OAM-ID-STD-MIB::mplsOamIdMeRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in the active(1) state, no objects in that row can be modified by the agent except mplsOamIdMeRowStatus.
.1.3.6.1.2.1.10.166.21.1.5.1.11,MPLS-OAM-ID-STD-MIB::mplsOamIdMeStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.21.2,MPLS-OAM-ID-STD-MIB::mplsOamIdConformance,,,,,,
.1.3.6.1.2.1.10.166.21.2.1,MPLS-OAM-ID-STD-MIB::mplsOamIdCompliances,,,,,,
.1.3.6.1.2.1.10.166.21.2.1.1,MPLS-OAM-ID-STD-MIB::mplsOamIdModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for the MPLS-TP-OAM-STD-MIB. Such devices can then be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.10.166.21.2.1.2,MPLS-OAM-ID-STD-MIB::mplsOamIdModuleReadOnlyCompliance,,,,,,Compliance statement for agents that only provide read-only support for the MPLS-TP-OAM-STD-MIB module.
.1.3.6.1.2.1.10.166.21.2.2,MPLS-OAM-ID-STD-MIB::mplsOamIdGroups,,,,,,
.1.3.6.1.2.1.10.166.21.2.2.1,MPLS-OAM-ID-STD-MIB::mplsOamIdMegGroup,,,,,,Collection of objects needed for MPLS MEG information.
.1.3.6.1.2.1.10.166.21.2.2.2,MPLS-OAM-ID-STD-MIB::mplsOamIdMeGroup,,,,,,Collection of objects needed for MPLS ME information.
.1.3.6.1.2.1.10.166.21.2.2.3,MPLS-OAM-ID-STD-MIB::mplsOamIdNotificationObjectsGroup,,,,,,Collection of objects needed to implement notifications.
.1.3.6.1.2.1.10.166.21.2.2.4,MPLS-OAM-ID-STD-MIB::mplsOamIdNotificationGroup,,,,,,Set of notifications implemented in this module.
.1.3.6.1.2.1.10.166.22,MPLS-LPS-MIB::mplsLpsMIB,,,,,,This MIB module supports the configuration and management of MPLS-TP linear protection domains. Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.10.166.22.0,MPLS-LPS-MIB::mplsLpsNotifications,,,,,,
.1.3.6.1.2.1.10.166.22.0.1,MPLS-LPS-MIB::mplsLpsEventSwitchover,,,,,,An mplsLpsEventSwitchover notification is sent when the value of an instance of mplsLpsMeStatusSwitchovers increments.
.1.3.6.1.2.1.10.166.22.0.2,MPLS-LPS-MIB::mplsLpsEventRevertiveMismatch,,,,,,An mplsLpsEventRevertiveMismatch notification is sent when the value of mplsLpsStatusRevertiveMismatch changes.
.1.3.6.1.2.1.10.166.22.0.3,MPLS-LPS-MIB::mplsLpsEventProtecTypeMismatch,,,,,,An mplsLpsEventProtecTypeMismatch notification is sent when the value of mplsLpsStatusProtecTypeMismatch changes.
.1.3.6.1.2.1.10.166.22.0.4,MPLS-LPS-MIB::mplsLpsEventCapabilitiesMismatch,,,,,,An mplsLpsEventCapabilitiesMismatch notification is sent when the value of mplsLpsStatusCapabilitiesMismatch changes.
.1.3.6.1.2.1.10.166.22.0.5,MPLS-LPS-MIB::mplsLpsEventPathConfigMismatch,,,,,,An mplsLpsEventPathConfigMismatch notification is sent when the value of mplsLpsStatusPathConfigMismatch changes.
.1.3.6.1.2.1.10.166.22.0.6,MPLS-LPS-MIB::mplsLpsEventFopNoResponse,,,,,,An mplsLpsEventFopNoResponse notification is sent when the value of mplsLpsStatusFopNoResponses increments.
.1.3.6.1.2.1.10.166.22.0.7,MPLS-LPS-MIB::mplsLpsEventFopTimeout,,,,,,An mplsLpsEventFopTimeout notification is sent when the value of mplsLpsStatusFopTimeouts increments.
.1.3.6.1.2.1.10.166.22.1,MPLS-LPS-MIB::mplsLpsObjects,,,,,,
.1.3.6.1.2.1.10.166.22.1.1,MPLS-LPS-MIB::mplsLpsConfigDomainIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for mplsLpsConfigDomainIndex, or a zero to indicate that the number of unassigned entries has been exhausted. Negative values are not allowed, as they do not correspond to valid values of mplsLpsConfigDomainIndex.
.1.3.6.1.2.1.10.166.22.1.2,MPLS-LPS-MIB::mplsLpsConfigTable,,not-accessible,,current,,This table lists the MPLS-TP linear protection domains that have been configured on the system. An entry is created by a network operator who wants to run the MPLS-TP linear protection protocol for the protection domain.
.1.3.6.1.2.1.10.166.22.1.2.1,MPLS-LPS-MIB::mplsLpsConfigEntry,,not-accessible,mplsLpsConfigDomainIndex,current,,A conceptual row in the mplsLpsConfigTable.
.1.3.6.1.2.1.10.166.22.1.2.1.1,MPLS-LPS-MIB::mplsLpsConfigDomainIndex,Unsigned32,not-accessible,,current,,Index for the conceptual row identifying a protection domain. Operators should obtain new values for row creation in this table by reading mplsLpsConfigDomainIndexNext. When the value of this object is the same as the value of mplsLpsMeConfigDomain, the mplsLpsMeConfigDomain is defined as either the working path or the protection path for this protection domain.
.1.3.6.1.2.1.10.166.22.1.2.1.2,MPLS-LPS-MIB::mplsLpsConfigDomainName,OCTET,read-create,,current,,Textual name that represents the MPLS-TP linear protection domain. It facilitates easy administrative identification of each protection domain.
.1.3.6.1.2.1.10.166.22.1.2.1.3,MPLS-LPS-MIB::mplsLpsConfigMode,INTEGER,read-create,,current,psc(1):aps(2),The mode of the MPLS-TP linear protection mechanism. This can be either PSC or APS, as follows: PSC The Protection State Coordination mode as described in RFC 6378. APS The Automatic Protection Switching mode as described in RFC 7271. This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1). The value of this object is not supposed to be changed during operation. When the value should be changed, the protection processes in both LERs MUST be restarted with the same new value. If this value is changed at one LER during operation, the LER will generate PSC packets with a new Capabilities TLV value. This will result in mplsLpsEventCapabilitiesMismatch notifications at both LERs.
.1.3.6.1.2.1.10.166.22.1.2.1.4,MPLS-LPS-MIB::mplsLpsConfigProtectionType,INTEGER,read-create,,current,onePlusOneUnidirectional(1):oneColonOneBidirectional(2):onePlusOneBidirectional(3),The protection architecture type of the protection domain. This object represents both the bridge type, which can be either a permanent bridge (1+1) or a selector bridge (1:1); and the switching scheme, which can be either unidirectional or bidirectional. 1+1 In the 1+1 protection scheme, a fully dedicated protection path is allocated. Data traffic is copied and fed at the source to both the working path and the protection path. The traffic on the working path and protection path is transmitted simultaneously to the sink of the protection domain, where selection between the working path and the protection path is performed. 1:1 In the 1:1 protection scheme, a protection path is allocated to protect against a defect, failure, or degradation on the working path. In normal conditions, data traffic is transmitted over the working path, while the protection path functions in the idle state. If there is a defect on the working path or a specific administrative request, traffic is switched to the protection path. bidirectional In the bidirectional protection scheme, both directions will be switched simultaneously even if the fault applies to only one direction of the path. unidirectional In the unidirectional protection scheme, protection switching will be performed independently for each direction of a bidirectional transport path. This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.5,MPLS-LPS-MIB::mplsLpsConfigRevertive,INTEGER,read-create,,current,nonrevertive(1):revertive(2),This object represents the reversion mode of the linear protection domain. The reversion mode of the protection mechanism may be either revertive or non-revertive. nonrevertive In the non-revertive mode, after a service has been recovered, traffic will be forwarded on the protection path. revertive In the revertive mode, after a service has been recovered, traffic will be redirected back onto the original working path. This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.6,MPLS-LPS-MIB::mplsLpsConfigSdThreshold,Unsigned32,read-create,,current,,This object holds the threshold value of the Signal Degrade (SD) defect in percent. In order to detect the SD defect, the MPLS-TP packet loss measurement (LM) is performed every second. If either the packet loss is negative (i.e., there are more packets received than transmitted) or the packet loss ratio (lost packets/transmitted packets) in percent is greater than this threshold value, a Bad Second is declared. Otherwise, a Good Second is declared. The SD defect is detected if there are mplsLpsConfigSdBadSeconds consecutive Bad Seconds and cleared if there are mplsLpsConfigSdGoodSeconds consecutive Good Seconds. This object may be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.7,MPLS-LPS-MIB::mplsLpsConfigSdBadSeconds,Unsigned32,read-create,,current,,This object holds the number of Bad Seconds to detect the SD. If the number of consecutive Bad Seconds reaches this value, the SD defect is detected and used as an input to the protection switching process. This object may be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.8,MPLS-LPS-MIB::mplsLpsConfigSdGoodSeconds,Unsigned32,read-create,,current,,This object holds the number of Good Seconds to declare the clearance of an SD defect. After an SD defect occurs on a path, if the number of consecutive Good Seconds reaches this value for the degraded path, the clearance of the SD defect is declared and used as an input to the protection switching process. This object may be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.9,MPLS-LPS-MIB::mplsLpsConfigWaitToRestore,Unsigned32,read-create,,current,,This object holds the Wait-to-Restore timer value in minutes and can be configured in 1-minute intervals between 5 and 12 minutes. The WTR timer is used to delay the reversion of the PSC state to the Normal state when recovering from a failure condition on the working path when the protection domain is configured for revertive behavior. This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.10,MPLS-LPS-MIB::mplsLpsConfigHoldOff,Unsigned32,read-create,,current,,The hold-off time in deciseconds. Represents the time between SF/SD condition detection and declaration of an SF/SD request to the protection switching logic. It is intended to avoid unnecessary switching when a lower-layer protection mechanism is in place. Can be configured in intervals of 100 milliseconds. When a new defect or a more severe defect occurs on the active path (the path from which the selector selects the user data traffic) and this value is non-zero, the hold-off timer will be started. A defect on the standby path (the path from which the selector does not select the user data traffic) does not trigger the start of the hold-off timer, as there is no need for a traffic switchover. This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.11,MPLS-LPS-MIB::mplsLpsConfigContinualTxInterval,Unsigned32,read-create,,current,,The Continual Tx Time in seconds. Represents the time interval to send the continual PSC packet to the other end, based on the current state. This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.12,MPLS-LPS-MIB::mplsLpsConfigRapidTxInterval,Unsigned32,read-create,,current,,The Rapid Tx interval in microseconds. Represents the time interval to send the PSC packet to the other end, when there is a change in the state of the linear protection domain due to local input. The default value is 3.3 milliseconds (3300 microseconds). This object may not be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.13,MPLS-LPS-MIB::mplsLpsConfigCommand,INTEGER,read-create,,current,noCmd(1):clear(2):lockoutOfProtection(3):forcedSwitch(4):manualSwitchToWork(5):manualSwitchToProtect(6):exercise(7):freeze(8):clearfreeze(9),Allows the initiation of an operator command on the protection domain. When read, this object returns the last command written or noCmd if no command has been written since initialization. The return of the last command written does not imply that this command is currently in effect. This request may have been preempted by a higher-priority local or remote request. This object may be modified if the associated mplsLpsConfigRowStatus object is equal to active(1).
.1.3.6.1.2.1.10.166.22.1.2.1.14,MPLS-LPS-MIB::mplsLpsConfigCreationTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time the row was created.
.1.3.6.1.2.1.10.166.22.1.2.1.15,MPLS-LPS-MIB::mplsLpsConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object represents the status of the MPLS-TP linear protection domain entry. This variable is used to create, modify, and/or delete a row in this table.
.1.3.6.1.2.1.10.166.22.1.2.1.16,MPLS-LPS-MIB::mplsLpsConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.10.166.22.1.3,MPLS-LPS-MIB::mplsLpsStatusTable,,not-accessible,,current,,This table provides status information about MPLS-TP linear protection domains that have been configured on the system.
.1.3.6.1.2.1.10.166.22.1.3.1,MPLS-LPS-MIB::mplsLpsStatusEntry,,not-accessible,,current,,A conceptual row in the mplsLpsStatusTable.
.1.3.6.1.2.1.10.166.22.1.3.1.1,MPLS-LPS-MIB::mplsLpsStatusState,INTEGER,read-only,,current,normal(1):unavLOlocal(2):unavSFPlocal(3):unavSDPlocal(4):unavLOremote(5):unavSFPremote(6):unavSDPremote(7):protfailSFWlocal(8):protfailSDWlocal(9):protfailSFWremote(10):protfailSDWremote(11):switadmFSlocal(12):switadmMSWlocal(13):switadmMSPlocal(14):switadmFSremote(15):switadmMSWremote(16):switadmMSPremote(17):wtr(18):dnr(19):exerLocal(20):exerRemote(21),The current state of the PSC state machine.
.1.3.6.1.2.1.10.166.22.1.3.1.2,MPLS-LPS-MIB::mplsLpsStatusReqRcv,INTEGER,read-only,,current,noRequest(0):doNotRevert(1):reverseRequest(2):exercise(3):waitToRestore(4):manualSwitch(5):signalDegrade(7):signalFail(10):forcedSwitch(12):lockoutOfProtection(14),The current value of the PSC Request field received on the most recent PSC packet.
.1.3.6.1.2.1.10.166.22.1.3.1.3,MPLS-LPS-MIB::mplsLpsStatusReqSent,INTEGER,read-only,,current,noRequest(0):doNotRevert(1):reverseRequest(2):exercise(3):waitToRestore(4):manualSwitch(5):signalDegrade(7):signalFail(10):forcedSwitch(12):lockoutOfProtection(14),The current value of the PSC Request field sent on the most recent PSC packet.
.1.3.6.1.2.1.10.166.22.1.3.1.4,MPLS-LPS-MIB::mplsLpsStatusFpathPathRcv,OCTET,read-only,,current,,The current value of the FPath and Path fields received on the most recent PSC packet.
.1.3.6.1.2.1.10.166.22.1.3.1.5,MPLS-LPS-MIB::mplsLpsStatusFpathPathSent,OCTET,read-only,,current,,The current value of the FPath and Path fields sent on the most recent PSC packet.
.1.3.6.1.2.1.10.166.22.1.3.1.6,MPLS-LPS-MIB::mplsLpsStatusRevertiveMismatch,INTEGER,read-only,,current,true(1):false(2),This object indicates a provisioning mismatch in the revertive mode across the protection domain endpoints. The value of this object becomes true when a PSC message with an incompatible Revertive field is received or false when a PSC message with a compatible Revertive field is received.
.1.3.6.1.2.1.10.166.22.1.3.1.7,MPLS-LPS-MIB::mplsLpsStatusProtecTypeMismatch,INTEGER,read-only,,current,true(1):false(2),This object indicates a provisioning mismatch in the protection type, representing both the bridge type and the switching type, across the protection domain endpoints. The value of this object becomes true when a PSC message with an incompatible Protection Type (PT) field is received or false when a PSC message with a compatible PT field is received.
.1.3.6.1.2.1.10.166.22.1.3.1.8,MPLS-LPS-MIB::mplsLpsStatusCapabilitiesMismatch,INTEGER,read-only,,current,true(1):false(2),This object indicates a provisioning mismatch in Capabilities TLVs across the protection domain endpoints. The value of this object becomes true when a PSC message with an incompatible Capabilities TLV field is received or false when a PSC message with a compatible Capabilities TLV field is received. The Capabilities TLV with 0xF8000000 indicates that the APS mode is used for the MPLS-TP linear protection mechanism, whereas the PSC mode either (1) uses the Capabilities TLV with a value of 0x0 or (2) does not use the Capabilities TLV because the TLV does not exist.
.1.3.6.1.2.1.10.166.22.1.3.1.9,MPLS-LPS-MIB::mplsLpsStatusPathConfigMismatch,INTEGER,read-only,,current,true(1):false(2),This object indicates a provisioning mismatch in the protection path configuration for PSC communication across the protection domain endpoints. The value of this object becomes true when a PSC message is received from the working path or false when a PSC message is received from the protection path.
.1.3.6.1.2.1.10.166.22.1.3.1.10,MPLS-LPS-MIB::mplsLpsStatusFopNoResponses,Counter32,read-only,,current,,This object holds the number of occurrences of protocol failure due to a lack of response to a traffic switchover request within 50 ms. When there is a traffic switchover due to a local request, a 50 ms timer is started to detect protocol failure due to no response. If there is no PSC message received with the same Path value as the Path value in the transmitted PSC message until the 50 ms timer expires, protocol failure due to no response occurs.
.1.3.6.1.2.1.10.166.22.1.3.1.11,MPLS-LPS-MIB::mplsLpsStatusFopTimeouts,Counter32,read-only,,current,,This object holds the number of occurrences of protocol failure due to no PSC message being received during at least 3.5 times the long PSC message interval. When no PSC message is received on the protection path during at least 3.5 times the long PSC message interval and there is no defect on the protection path, protocol failure due to no PSC message occurs.
.1.3.6.1.2.1.10.166.22.1.4,MPLS-LPS-MIB::mplsLpsMeConfigTable,,not-accessible,,current,,This table lists ME associations that have been configured in protection domains.
.1.3.6.1.2.1.10.166.22.1.4.1,MPLS-LPS-MIB::mplsLpsMeConfigEntry,,not-accessible,mplsOamIdMegIndex:mplsOamIdMeIndex:mplsOamIdMeMpIndex,current,,A conceptual row in the mplsLpsMeConfigTable. There is a sparse relationship between the conceptual rows of this table and the mplsOamIdMeTable. Each time that an entry is created in the mplsOamIdMeTable for which the LER supports MPLS-TP linear protection, a row is created automatically in the mplsLpsMeConfigTable. An entry in this table is related to a single entry in the mplsOamIdMeTable. When a point-to-point transport path needs to be monitored, one ME is needed for the path, and one entry in the mplsOamIdMeTable will be created. But the ME entry in the mplsOamIdMeTable may or may not participate in protection switching. If an ME participates in protection switching, an entry in the mplsLpsMeConfigTable MUST be created, and the objects in the entry indicate which protection domain this ME belongs to and whether this ME is for the working path or the protection path. If the ME does not participate in protection switching, an entry in the mplsLpsMeConfigTable does not need to be created.
.1.3.6.1.2.1.10.166.22.1.4.1.1,MPLS-LPS-MIB::mplsLpsMeConfigDomain,Unsigned32,read-create,,current,,This object holds the mplsLpsConfigDomainIndex value for the protection domain in which this ME is included. If this ME is not part of any protection domain, then this object contains the value 0. When the value of this object is the same as the value of mplsLpsConfigDomainIndex, the object is defined as either the working path or the protection path of the protection domain corresponding to mplsLpsConfigDomainIndex.
.1.3.6.1.2.1.10.166.22.1.4.1.2,MPLS-LPS-MIB::mplsLpsMeConfigPath,INTEGER,read-create,,current,working(1):protection(2),This object represents whether the ME is configured as the working path or the protection path.
.1.3.6.1.2.1.10.166.22.1.5,MPLS-LPS-MIB::mplsLpsMeStatusTable,,not-accessible,,current,,This table contains status information of all the MEs that are included in MPLS-TP linear protection domains.
.1.3.6.1.2.1.10.166.22.1.5.1,MPLS-LPS-MIB::mplsLpsMeStatusEntry,,not-accessible,,current,,A conceptual row in the mplsLpsMeStatusTable.
.1.3.6.1.2.1.10.166.22.1.5.1.1,MPLS-LPS-MIB::mplsLpsMeStatusCurrent,BITS,read-only,,current,localSelectTraffic(0):localSD(1):localSF(2),Indicates the current state of the ME. localSelectTraffic This bit indicates that traffic is being selected from this ME. localSD This bit implies that a local Signal Degrade condition is in effect on this ME/path. localSF This bit implies that a local Signal Fail condition is in effect on this ME/path.
.1.3.6.1.2.1.10.166.22.1.5.1.2,MPLS-LPS-MIB::mplsLpsMeStatusSignalDegrades,Counter32,read-only,,current,,Represents the count of Signal Degrade conditions. For the detection and clearance of Signal Degrade, see the description of mplsLpsConfigSdThreshold.
.1.3.6.1.2.1.10.166.22.1.5.1.3,MPLS-LPS-MIB::mplsLpsMeStatusSignalFailures,Counter32,read-only,,current,,Represents the count of Signal Fail conditions. This condition occurs when the OAM running on this ME detects the Signal Fail event.
.1.3.6.1.2.1.10.166.22.1.5.1.4,MPLS-LPS-MIB::mplsLpsMeStatusSwitchovers,Counter32,read-only,,current,,Represents the count of switchovers that happened in this ME. When the mplsLpsMeConfigPath value is 'working', this object will return the number of times that traffic has been switched from this working path to the protection path. When the mplsLpsMeConfigPath value is 'protection', this object will return the number of times that traffic has been switched back to the working path from this protection path.
.1.3.6.1.2.1.10.166.22.1.5.1.5,MPLS-LPS-MIB::mplsLpsMeStatusLastSwitchover,TimeTicks,read-only,,current,,This object holds the value of sysUpTime at the time that the last switchover happened. When the mplsLpsMeConfigPath value is 'working', this object will return the value of sysUpTime when traffic was switched from this path to the protection path. If traffic has never switched to the protection path, the value 0 will be returned. When the mplsLpsMeConfigPath value is 'protection', this object will return the value of sysUpTime the last time that traffic was switched back to the working path from this path. If no traffic has ever switched back to the working path from this protection path, the value 0 will be returned.
.1.3.6.1.2.1.10.166.22.1.5.1.6,MPLS-LPS-MIB::mplsLpsMeStatusSwitchoverSeconds,Counter32,read-only,,current,,The cumulative Protection Switching Duration (PSD) time in seconds. For the working path, this is the cumulative number of seconds that traffic was selected from the protection path. For the protection path, this is the cumulative number of seconds that the working path has been used to select traffic.
.1.3.6.1.2.1.10.166.22.1.6,MPLS-LPS-MIB::mplsLpsNotificationEnable,BITS,read-write,,current,switchover(0):revertiveMismatch(1):protecTypeMismatch(2):capabilitiesMismatch(3):pathConfigMismatch(4):fopNoResponse(5):fopTimeout(6),Provides the ability to enable and disable notifications defined in this MIB module. switchover Indicates that mplsLpsEventSwitchover notifications should be generated. revertiveMismatch Indicates that mplsLpsEventRevertiveMismatch notifications should be generated. protecTypeMismatch Indicates that mplsLpsEventProtecTypeMismatch notifications should be generated. capabilitiesMismatch Indicates that mplsLpsEventCapabilitiesMismatch notifications should be generated. pathConfigMismatch Indicates that mplsLpsEventPathConfigMismatch notifications should be generated. fopNoResponse Indicates that mplsLpsEventFopNoResponse notifications should be generated. fopTimeout Indicates that mplsLpsEventFopTimeout notifications should be generated.
.1.3.6.1.2.1.10.166.22.2,MPLS-LPS-MIB::mplsLpsConformance,,,,,,
.1.3.6.1.2.1.10.166.22.2.1,MPLS-LPS-MIB::mplsLpsCompliances,,,,,,
.1.3.6.1.2.1.10.166.22.2.1.1,MPLS-LPS-MIB::mplsLpsModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for the MPLS-LPS-MIB module. Such devices can provide linear protection and also be configured using this MIB module.
.1.3.6.1.2.1.10.166.22.2.1.2,MPLS-LPS-MIB::mplsLpsModuleReadOnlyCompliance,,,,,,Compliance statement for agents that only provide read-only support for the MPLS-LPS-MIB module.
.1.3.6.1.2.1.10.166.22.2.2,MPLS-LPS-MIB::mplsLpsGroups,,,,,,
.1.3.6.1.2.1.10.166.22.2.2.1,MPLS-LPS-MIB::mplsLpsScalarGroup,,,,,,Collection of objects needed for MPLS linear protection.
.1.3.6.1.2.1.10.166.22.2.2.2,MPLS-LPS-MIB::mplsLpsTableGroup,,,,,,Collection of objects needed for MPLS linear protection configuration and statistics.
.1.3.6.1.2.1.10.166.22.2.2.3,MPLS-LPS-MIB::mplsLpsMeTableGroup,,,,,,Collection of objects needed for MPLS linear protection ME configuration and statistics.
.1.3.6.1.2.1.10.166.22.2.2.4,MPLS-LPS-MIB::mplsLpsNotificationGroup,,,,,,Collection of objects needed to implement notifications.
.1.3.6.1.2.1.10.200,TE-LINK-STD-MIB::teLinkStdMIB,,,,,,Copyright (C) 2005 The Internet Society. This version of this MIB module is part of RFC 4220; see the RFC itself for full legal notices. This MIB module contains managed object definitions for MPLS traffic engineering links as defined in 'Link Bundling in MPLS Traffic Engineering (TE)'.
.1.3.6.1.2.1.10.200.0,TE-LINK-STD-MIB::teLinkNotifications,,,,,,
.1.3.6.1.2.1.10.200.1,TE-LINK-STD-MIB::teLinkObjects,,,,,,
.1.3.6.1.2.1.10.200.1.1,TE-LINK-STD-MIB::teLinkTable,,not-accessible,,current,,This table specifies the grouping of component links into TE links and the grouping of TE links into bundled links.
.1.3.6.1.2.1.10.200.1.1.1,TE-LINK-STD-MIB::teLinkEntry,,not-accessible,ifIndex,current,,An entry in this table exists for each ifEntry with an ifType of teLink(200), i.e., for every TE link. An ifEntry in the ifTable must exist before a teLinkEntry is created with the corresponding ifIndex. If a TE link entry in the ifTable is destroyed, then so is the corresponding entry in the teLinkTable. The administrative and operational status values are controlled from the ifEntry.
.1.3.6.1.2.1.10.200.1.1.1.1,TE-LINK-STD-MIB::teLinkAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address for the TE link.
.1.3.6.1.2.1.10.200.1.1.1.2,TE-LINK-STD-MIB::teLinkLocalIpAddr,OCTET,read-create,,current,,The local Internet address for numbered links. The type of this address is determined by the value of the teLinkAddressType object. For IPv4 and IPv6 numbered links, this object represents the local IP address associated with the TE link. For an unnumbered link, the local address is of type unknown, this object is set to the zero length string, and the teLinkOutgoingIfId object then identifies the unnumbered address. If the TE link is a Forwarding Adjacency (FA), the local IP address is set to the head-end address of the FA-LSP. If ipAddrTable is implemented, this object must have the same value as the ipAdEntAddr object that belongs to the row in ipAddrTable where ipAdEntIfIndex is equal to ifIndex.
.1.3.6.1.2.1.10.200.1.1.1.3,TE-LINK-STD-MIB::teLinkRemoteIpAddr,OCTET,read-create,,current,,The remote Internet address for numbered links. The type of this address is determined by the value of the teLinkAddressType object. The remote IP address associated with the TE link (IPv4 and IPv6 numbered links). For an unnumbered link, the remote address is of type unknown, this object is set to the zero length string, and the teLinkIncomingIfId object then identifies the unnumbered address. If the TE link is a Forwarding Adjacency, the remote IP address is set to the tail-end address of the FA-LSP.
.1.3.6.1.2.1.10.200.1.1.1.4,TE-LINK-STD-MIB::teLinkMetric,Unsigned32,read-create,,current,,The traffic engineering metric for the TE link is derived from its component links. All component links within the TE link must have the same traffic engineering metric.
.1.3.6.1.2.1.10.200.1.1.1.5,TE-LINK-STD-MIB::teLinkMaximumReservableBandwidth,OCTET,read-only,,current,,This attribute specifies the maximum reservable bandwidth on the TE link. This is the union of the maximum reservable bandwidth of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.1.1.6,TE-LINK-STD-MIB::teLinkProtectionType,INTEGER,read-create,,current,extraTraffic(1):unprotected(2):shared(3):dedicated1For1(4):dedicated1Plus1(5):enhanced(6),This attribute specifies the link protection type of the TE link. Descriptions of the different protection types can be found in the 'Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)' document.
.1.3.6.1.2.1.10.200.1.1.1.7,TE-LINK-STD-MIB::teLinkWorkingPriority,Unsigned32,read-create,,current,,This object represents a priority value such that a new connection with a higher priority, i.e., numerically lower than this value, is guaranteed to be setup on a primary link and not on a secondary link.
.1.3.6.1.2.1.10.200.1.1.1.8,TE-LINK-STD-MIB::teLinkResourceClass,Unsigned32,read-create,,current,,This attribute specifies the TE link resource class. The resource class is a 32 bit bitfield. The resource class for a link bundle is derived from the resource class of its TE links. All TE links within a link bundle must have the same resource class. Encoding of the resource class is described in the 'Traffic Engineering (TE) Extensions to OSPF Version 2' document.
.1.3.6.1.2.1.10.200.1.1.1.9,TE-LINK-STD-MIB::teLinkIncomingIfId,Integer32,read-create,,current,,For unnumbered links, the incoming interface is set to the outgoing interface identifier chosen by the neighboring LSR for the reverse link corresponding to this TE link. If the link is numbered, the value of this object is 0 and the address is stored in the teLinkRemoteIpAddr instead.
.1.3.6.1.2.1.10.200.1.1.1.10,TE-LINK-STD-MIB::teLinkOutgoingIfId,Integer32,read-create,,current,,If the link is unnumbered, the outgoing interface identifier is set to the outgoing interface identifier chosen for the TE link by the advertising LSR. If the link is numbered, the value of this object is 0 and the address is stored in the teLinkLocalIpAddr instead.
.1.3.6.1.2.1.10.200.1.1.1.11,TE-LINK-STD-MIB::teLinkRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if status is active(1).
.1.3.6.1.2.1.10.200.1.1.1.12,TE-LINK-STD-MIB::teLinkStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the teLinkTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.1.2,TE-LINK-STD-MIB::teLinkDescriptorTable,,not-accessible,,current,,This table specifies the interface switching capability descriptors associated with the TE links.
.1.3.6.1.2.1.10.200.1.2.1,TE-LINK-STD-MIB::teLinkDescriptorEntry,,not-accessible,ifIndex:teLinkDescriptorId,current,,An entry in this table is created for every TE link interface switching capability descriptor. An ifEntry in the ifTable must exist before a teLinkDescriptorEntry using the same ifIndex is created. ifType of ifEntry must be teLink(200). If a TE link entry in the ifTable is destroyed, then so are all of the entries in the teLinkDescriptorTable that use the ifIndex of this TE link.
.1.3.6.1.2.1.10.200.1.2.1.1,TE-LINK-STD-MIB::teLinkDescriptorId,Unsigned32,not-accessible,,current,,This object specifies the link descriptor identifier.
.1.3.6.1.2.1.10.200.1.2.1.2,TE-LINK-STD-MIB::teLinkDescrSwitchingCapability,INTEGER,read-create,,current,packetSwitch1(1):packetSwitch2(2):packetSwitch3(3):packetSwitch4(4):layer2Switch(51):tdm(100):lambdaSwitch(150):fiberSwitch(200),This attribute specifies interface switching capability of the TE link, which is derived from its component links.
.1.3.6.1.2.1.10.200.1.2.1.3,TE-LINK-STD-MIB::teLinkDescrEncodingType,INTEGER,read-create,,current,packet(1):ethernet(2):ansiEtsiPdh(3):sdhItuSonetAnsi(5):digitalWrapper(7):lambda(8):fiber(9):fiberChannel(11),This attribute specifies the TE link encoding type.
.1.3.6.1.2.1.10.200.1.2.1.4,TE-LINK-STD-MIB::teLinkDescrMinLspBandwidth,OCTET,read-create,,current,,This attribute specifies the minimum LSP bandwidth on the TE link. This is derived from the union of the minimum LSP bandwidth of all the component links associated with the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.5,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio0,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 0 on the TE link. This is the union of the maximum LSP bandwidth at priority 0 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.6,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio1,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 1 on the TE link. This is the union of the maximum LSP bandwidth at priority 1 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.7,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio2,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 2 on the TE link. This is the union of the maximum LSP bandwidth at priority 2 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.8,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio3,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 3 on the TE link. This is the union of the maximum LSP bandwidth at priority 3 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.9,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio4,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 4 on the TE link. This is the union of the maximum LSP bandwidth at priority 4 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.10,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio5,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 5 on the TE link. This is the union of the maximum LSP bandwidth at priority 5 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.11,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio6,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 6 on the TE link. This is the union of the maximum LSP bandwidth at priority 6 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.12,TE-LINK-STD-MIB::teLinkDescrMaxLspBandwidthPrio7,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 7 on the TE link. This is the union of the maximum LSP bandwidth at priority 7 of all the component links within the TE link that can be used to carry live traffic.
.1.3.6.1.2.1.10.200.1.2.1.13,TE-LINK-STD-MIB::teLinkDescrInterfaceMtu,Unsigned32,read-create,,current,,This attribute specifies the interface MTU for the TE link descriptor.
.1.3.6.1.2.1.10.200.1.2.1.14,TE-LINK-STD-MIB::teLinkDescrIndication,INTEGER,read-create,,current,standard(0):arbitrary(1),This attribute specifies whether this interface supports Standard or Arbitrary SONET/SDH.
.1.3.6.1.2.1.10.200.1.2.1.15,TE-LINK-STD-MIB::teLinkDescrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. No read-create object can be changed if teLinkDescrRowStatus is in the active(1) state.
.1.3.6.1.2.1.10.200.1.2.1.16,TE-LINK-STD-MIB::teLinkDescrStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the teLinkDescriptorTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.1.3,TE-LINK-STD-MIB::teLinkSrlgTable,,not-accessible,,current,,This table specifies the SRLGs associated with TE links.
.1.3.6.1.2.1.10.200.1.3.1,TE-LINK-STD-MIB::teLinkSrlgEntry,,not-accessible,ifIndex:teLinkSrlg,current,,An entry in this table contains information about an SRLG associated with a TE link. An ifEntry in the ifTable must exist before a teLinkSrlgEntry using the same ifIndex is created. The ifType of ifEntry must be teLink(200). If a TE link entry in the ifTable is destroyed, then so are all of the entries in the teLinkSrlgTable that use the ifIndex of this TE link.
.1.3.6.1.2.1.10.200.1.3.1.1,TE-LINK-STD-MIB::teLinkSrlg,Unsigned32,not-accessible,,current,,This identifies an SRLG supported by the TE link. An SRLG is identified with a 32-bit number that is unique within an IGP domain. Zero is a valid SRLG number.
.1.3.6.1.2.1.10.200.1.3.1.2,TE-LINK-STD-MIB::teLinkSrlgRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. No read-create object can be modified if teLinkSrlgRowStatus is active(1).
.1.3.6.1.2.1.10.200.1.3.1.3,TE-LINK-STD-MIB::teLinkSrlgStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the teLinkSrlgTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.1.4,TE-LINK-STD-MIB::teLinkBandwidthTable,,not-accessible,,current,,This table specifies the priority-based bandwidth table for TE links.
.1.3.6.1.2.1.10.200.1.4.1,TE-LINK-STD-MIB::teLinkBandwidthEntry,,not-accessible,ifIndex:teLinkBandwidthPriority,current,,An entry in this table contains information about the priority-based bandwidth of TE links. An ifEntry in the ifTable must exist before a teLinkBandwidthEntry using the same ifIndex is created. The ifType of ifEntry must be teLink(200). If a TE link entry in the ifTable is destroyed, then so are all of the entries in the teLinkBandwidthTable that use the ifIndex of this TE link.
.1.3.6.1.2.1.10.200.1.4.1.1,TE-LINK-STD-MIB::teLinkBandwidthPriority,Unsigned32,not-accessible,,current,,This attribute specifies the priority. A value of 0 is valid as specified in the 'Traffic Engineering (TE) Extensions to OSPF Version 2' document.
.1.3.6.1.2.1.10.200.1.4.1.2,TE-LINK-STD-MIB::teLinkBandwidthUnreserved,OCTET,read-only,,current,,This attribute specifies the TE link unreserved bandwidth at priority p. It is the sum of the unreserved bandwidths at priority p of all component links associated with the TE link (excluding all links that are strictly used as protecting links).
.1.3.6.1.2.1.10.200.1.4.1.3,TE-LINK-STD-MIB::teLinkBandwidthRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. No read-create object can be modified when teLinkBandwidthRowStatus is active(1).
.1.3.6.1.2.1.10.200.1.4.1.4,TE-LINK-STD-MIB::teLinkBandwidthStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the teLinkBandwidthTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.1.5,TE-LINK-STD-MIB::componentLinkTable,,not-accessible,,current,,This table specifies the component link parameters.
.1.3.6.1.2.1.10.200.1.5.1,TE-LINK-STD-MIB::componentLinkEntry,,not-accessible,ifIndex,current,,An entry in this table exists for each ifEntry that represents a component link. An ifEntry must exist in the ifTable before a componentLinkEntry is created with the corresponding ifIndex. ifEntry's ifType can be of any interface type that has been defined for TE Link interworking. Examples include ATM, Frame Relay, Ethernet, etc. If an entry representing a component link is destroyed in the ifTable, then so is the corresponding entry in the componentLinkTable. The administrative and operational status values are controlled from the ifEntry.
.1.3.6.1.2.1.10.200.1.5.1.1,TE-LINK-STD-MIB::componentLinkMaxResBandwidth,OCTET,read-create,,current,,This attribute specifies the maximum reservable bandwidth on the component link.
.1.3.6.1.2.1.10.200.1.5.1.2,TE-LINK-STD-MIB::componentLinkPreferredProtection,INTEGER,read-create,,current,primary(1):secondary(2),This attribute specifies whether this component link is a primary or secondary entity.
.1.3.6.1.2.1.10.200.1.5.1.3,TE-LINK-STD-MIB::componentLinkCurrentProtection,INTEGER,read-only,,current,primary(1):secondary(2),This attribute specifies whether this component link is currently used as primary or secondary link.
.1.3.6.1.2.1.10.200.1.5.1.4,TE-LINK-STD-MIB::componentLinkRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. No read-create object can be modified when componentLinkRowStatus is active(1).
.1.3.6.1.2.1.10.200.1.5.1.5,TE-LINK-STD-MIB::componentLinkStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the componentLinkTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.1.6,TE-LINK-STD-MIB::componentLinkDescriptorTable,,not-accessible,,current,,This table specifies the interface switching capability descriptors associated with the component links.
.1.3.6.1.2.1.10.200.1.6.1,TE-LINK-STD-MIB::componentLinkDescriptorEntry,,not-accessible,ifIndex:componentLinkDescrId,current,,An entry in this table is created for every component link descriptor. An ifEntry in the ifTable must exist before a componentLinkDescriptorEntry using the same ifIndex is created. ifEntry's ifType can be of any interface type that has been defined for TE Link interworking. Examples include ATM, Frame Relay, Ethernet, etc. If a component link entry in the ifTable is destroyed, then so are all entries in the componentLinkDescriptorTable that use the ifIndex of this component link.
.1.3.6.1.2.1.10.200.1.6.1.1,TE-LINK-STD-MIB::componentLinkDescrId,Unsigned32,not-accessible,,current,,This object specifies the link descriptor identifier.
.1.3.6.1.2.1.10.200.1.6.1.2,TE-LINK-STD-MIB::componentLinkDescrSwitchingCapability,INTEGER,read-create,,current,packetSwitch1(1):packetSwitch2(2):packetSwitch3(3):packetSwitch4(4):layer2Switch(51):tdm(100):lambdaSwitch(150):fiberSwitch(200),This attribute specifies link multiplexing capabilities of the component link.
.1.3.6.1.2.1.10.200.1.6.1.3,TE-LINK-STD-MIB::componentLinkDescrEncodingType,INTEGER,read-create,,current,packet(1):ethernet(2):ansiEtsiPdh(3):sdhItuSonetAnsi(5):digitalWrapper(7):lambda(8):fiber(9):fiberChannel(11),This attribute specifies the component link encoding type.
.1.3.6.1.2.1.10.200.1.6.1.4,TE-LINK-STD-MIB::componentLinkDescrMinLspBandwidth,OCTET,read-create,,current,,This attribute specifies the minimum LSP bandwidth on the component link.
.1.3.6.1.2.1.10.200.1.6.1.5,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio0,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 0 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.6,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio1,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 1 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.7,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio2,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 2 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.8,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio3,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 3 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.9,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio4,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 4 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.10,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio5,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 5 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.11,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio6,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 6 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.12,TE-LINK-STD-MIB::componentLinkDescrMaxLspBandwidthPrio7,OCTET,read-create,,current,,This attribute specifies the maximum LSP bandwidth at priority 7 on the component link.
.1.3.6.1.2.1.10.200.1.6.1.13,TE-LINK-STD-MIB::componentLinkDescrInterfaceMtu,Unsigned32,read-create,,current,,This attribute specifies the interface MTU for the component link descriptor.
.1.3.6.1.2.1.10.200.1.6.1.14,TE-LINK-STD-MIB::componentLinkDescrIndication,INTEGER,read-create,,current,standard(0):arbitrary(1),This attribute specifies whether this interface supports Standard or Arbitrary SONET/SDH.
.1.3.6.1.2.1.10.200.1.6.1.15,TE-LINK-STD-MIB::componentLinkDescrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. No read-create object can be modified when componentLinkDescrRowStatus is active(1).
.1.3.6.1.2.1.10.200.1.6.1.16,TE-LINK-STD-MIB::componentLinkDescrStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the componentLinkDescriptorTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.1.7,TE-LINK-STD-MIB::componentLinkBandwidthTable,,not-accessible,,current,,This table specifies the priority-based bandwidth for component links.
.1.3.6.1.2.1.10.200.1.7.1,TE-LINK-STD-MIB::componentLinkBandwidthEntry,,not-accessible,ifIndex:componentLinkBandwidthPriority,current,,An entry in this table contains information about the priority-based bandwidth on component links. An ifEntry in the ifTable must exist before a componentLinkBandwidthEntry using the same ifIndex is created. ifEntry's ifType can be of any interface type that has been defined for TE Link interworking. Examples include ATM, Frame Relay, Ethernet, etc. If a component link entry in the ifTable is destroyed, then so are all entries in the componentLinkBandwidthTable that use the ifIndex of this component link.
.1.3.6.1.2.1.10.200.1.7.1.1,TE-LINK-STD-MIB::componentLinkBandwidthPriority,Unsigned32,not-accessible,,current,,This attribute specifies the priority. A value of 0 is valid as specified in the 'Traffic Engineering (TE) Extensions to OSPF Version 2' document.
.1.3.6.1.2.1.10.200.1.7.1.2,TE-LINK-STD-MIB::componentLinkBandwidthUnreserved,OCTET,read-only,,current,,This attribute specifies the component link unreserved bandwidth at priority p.
.1.3.6.1.2.1.10.200.1.7.1.3,TE-LINK-STD-MIB::componentLinkBandwidthRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. No read-create object can be modified when componentLinkBandwidthRowStatus is active(1).
.1.3.6.1.2.1.10.200.1.7.1.4,TE-LINK-STD-MIB::componentLinkBandwidthStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the componentLinkBandwidthTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.200.2,TE-LINK-STD-MIB::teLinkConformance,,,,,,
.1.3.6.1.2.1.10.200.2.1,TE-LINK-STD-MIB::teLinkCompliances,,,,,,
.1.3.6.1.2.1.10.200.2.1.1,TE-LINK-STD-MIB::teLinkModuleFullCompliance,,,,,,Compliance statement for agents that support read-create so that both configuration and monitoring of TE links can be accomplished via this MIB module.
.1.3.6.1.2.1.10.200.2.1.2,TE-LINK-STD-MIB::teLinkModuleReadOnlyCompliance,,,,,,Compliance statement for agents that support the monitoring of the TE link MIB module.
.1.3.6.1.2.1.10.200.2.2,TE-LINK-STD-MIB::teLinkGroups,,,,,,
.1.3.6.1.2.1.10.200.2.2.1,TE-LINK-STD-MIB::teLinkGroup,,,,,,Collection of objects needed for the management of resources associated with TE links.
.1.3.6.1.2.1.10.200.2.2.2,TE-LINK-STD-MIB::teLinkSrlgGroup,,,,,,Collection of objects needed for the management of SRLG resources associated with TE links.
.1.3.6.1.2.1.10.200.2.2.3,TE-LINK-STD-MIB::teLinkBandwidthGroup,,,,,,Collection of objects needed for the management of the bandwidth resources associated with TE links and component links.
.1.3.6.1.2.1.10.200.2.2.4,TE-LINK-STD-MIB::componentLinkBandwidthGroup,,,,,,Collection of objects needed for the management of the bandwidth parameters associated with component links.
.1.3.6.1.2.1.10.200.2.2.5,TE-LINK-STD-MIB::teLinkPscGroup,,,,,,Collection of objects needed for devices that are packet switch capable.
.1.3.6.1.2.1.10.200.2.2.6,TE-LINK-STD-MIB::teLinkTdmGroup,,,,,,Collection of objects needed for devices that are TDM switching capable.
.1.3.6.1.2.1.10.227,LMP-MIB::lmpMIB,,,,,,Copyright (C) 2006 The Internet Society. This version of the MIB module is part of RFC 4631; see the RFC itself for full legal notices. This MIB module contains managed object definitions for the Link Management Protocol (LMP) as defined in 'Link Management Protocol'.
.1.3.6.1.2.1.10.227.0,LMP-MIB::lmpNotifications,,,,,,
.1.3.6.1.2.1.10.227.0.1,LMP-MIB::lmpTeLinkPropertyMismatch,,,,,,This notification is generated when a TE link property mismatch is detected on the node. The received remote TE link ID of the misconfigured TE link is represented by either teLinkRemoteIpAddr or teLinkIncomingIfId, depending on whether the TE link is numbered or unnumbered. This notification should not be sent unless lmpLinkPropertyNotificationsEnabled is true(1). It is recommended that this notification be reported only the first time a mismatch is detected. Otherwise, for a given TE link, this notification can occur no more than once per verification interval (lmpGlobalLinkVerificationInterval).
.1.3.6.1.2.1.10.227.0.2,LMP-MIB::lmpDataLinkPropertyMismatch,,,,,,This notification is generated when a data-bearing link property mismatch is detected on the node. lmpDataLinkType is used to identify the local identifiers associated with the data link. (The data link interface index can be used to determine the TE link interface index, as this relationship is captured in the interface stack table.) The remote entity interface ID is the remote entity interface ID received in the LinkSummary message. This notification should not be sent unless lmpLinkPropertyNotificationsEnabled is true(1). It is recommended that this notification be reported only the first time a mismatch is detected. Otherwise, for a given data link, this notification can occur no more than once per verification interval (lmpGlobalLinkVerificationInterval).
.1.3.6.1.2.1.10.227.0.3,LMP-MIB::lmpUnprotected,,,,,,This notification is generated when there is more than one control channel between LMP neighbors and the last redundant control channel has failed. If the remaining operational control channel fails, then there will be no more control channels between the pair of nodes and all the TE links between the pair of nodes, will go to degraded state. This notification should not be sent unless lmpUnprotectedNotificationsEnabled is set to true(1).
.1.3.6.1.2.1.10.227.0.4,LMP-MIB::lmpControlChannelUp,,,,,,This notification is generated when a control channel transitions to the up operational state. This notification should not be sent unless lmpCcUpDownNotificationsEnabled is true(1).
.1.3.6.1.2.1.10.227.0.5,LMP-MIB::lmpControlChannelDown,,,,,,This notification is generated when a control channel transitions out of the up operational state. This notification should not be sent unless lmpCcUpDownNotificationsEnabled is true(1).
.1.3.6.1.2.1.10.227.0.6,LMP-MIB::lmpTeLinkDegraded,,,,,,This notification is generated when a lmpTeLinkOperStatus object for a TE link enters the degraded state. This notification should not be sent unless lmpTeLinkNotificationsEnabled is true(1).
.1.3.6.1.2.1.10.227.0.7,LMP-MIB::lmpTeLinkNotDegraded,,,,,,This notification is generated when a lmpTeLinkOperStatus object for a TE link leaves the degraded state. This notification should not be sent unless lmpTeLinkNotificationsEnabled is true(1).
.1.3.6.1.2.1.10.227.0.8,LMP-MIB::lmpDataLinkVerificationFailure,,,,,,This notification is generated when a data-bearing link verification fails. This notification should not be sent unless lmpDataLinkNotificationsEnabled is true(1). For a given data link, this notification can occur no more than once per verification interval (lmpGlobalLinkVerificationInterval).
.1.3.6.1.2.1.10.227.1,LMP-MIB::lmpObjects,,,,,,
.1.3.6.1.2.1.10.227.1.1,LMP-MIB::lmpAdminStatus,INTEGER,read-write,,current,up(1):down(2),The desired operational status of LMP on the node. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.2,LMP-MIB::lmpOperStatus,INTEGER,read-only,,current,up(1):down(2),The actual operational status of LMP on the node.
.1.3.6.1.2.1.10.227.1.3,LMP-MIB::lmpNbrTable,,not-accessible,,current,,This table specifies the neighbor node(s) to which control channels may be established.
.1.3.6.1.2.1.10.227.1.3.1,LMP-MIB::lmpNbrEntry,,not-accessible,lmpNbrNodeId,current,,An entry in this table is created by a LMP-enabled device for every pair of nodes that can establish control channels.
.1.3.6.1.2.1.10.227.1.3.1.1,LMP-MIB::lmpNbrNodeId,OCTET,not-accessible,,current,,This is a unique index for an entry in the LmpNbrTable. This value represents the remote Node ID.
.1.3.6.1.2.1.10.227.1.3.1.2,LMP-MIB::lmpNbrRetransmitInterval,Unsigned32,read-create,,current,,This object specifies the initial retransmission interval that is used for the retransmission of messages that require acknowledgement. This object, along with lmpNbrRetryLimit, is used to implement the congestion-handling mechanism defined in Section 10 of the Link Management Protocol specification, which is based on RFC 2914.
.1.3.6.1.2.1.10.227.1.3.1.3,LMP-MIB::lmpNbrRetryLimit,Unsigned32,read-create,,current,,This object specifies the maximum number of times a message is transmitted without being acknowledged. A value of 0 is used to indicate that a node should never stop retransmission. This object, along with lmpNbrRetransmitInterval, is used to implement the congestion-handling mechanism as defined in Section 10 of the Link Management Protocol specification, which is based on RFC 2914.
.1.3.6.1.2.1.10.227.1.3.1.4,LMP-MIB::lmpNbrRetransmitDelta,Unsigned32,read-create,,current,,This object governs the speed with which the sender increases the retransmission interval, as explained in Section 10 of the Link Management Protocol specification, which is based on RFC 2914. This value is a power used to express the exponential backoff. The ratio of two successive retransmission intervals is (1 + Delta).
.1.3.6.1.2.1.10.227.1.3.1.5,LMP-MIB::lmpNbrAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired operational status of LMP to this remote node.
.1.3.6.1.2.1.10.227.1.3.1.6,LMP-MIB::lmpNbrOperStatus,INTEGER,read-only,,current,up(1):down(2),The actual operational status of LMP to this remote node.
.1.3.6.1.2.1.10.227.1.3.1.7,LMP-MIB::lmpNbrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
.1.3.6.1.2.1.10.227.1.3.1.8,LMP-MIB::lmpNbrStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the lmpNbrTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.227.1.4,LMP-MIB::lmpCcHelloIntervalDefault,Unsigned32,read-write,,current,,This object specifies the default value for the HelloInterval parameter used in the Hello protocol keep-alive phase. It indicates how frequently LMP Hello messages will be sent. It is used as the default value for lmpCcHelloInterval. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.5,LMP-MIB::lmpCcHelloIntervalDefaultMin,Unsigned32,read-write,,current,,This object specifies the default minimum value for the HelloInterval parameter. It is used as a default value for lmpCcHelloIntervalMin. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.6,LMP-MIB::lmpCcHelloIntervalDefaultMax,Unsigned32,read-write,,current,,This object specifies the default maximum value for the HelloInterval parameter. It is used as a default value for lmpCcHelloIntervalMax. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.7,LMP-MIB::lmpCcHelloDeadIntervalDefault,Unsigned32,read-write,,current,,This object specifies the default HelloDeadInterval parameter to use in the Hello protocol keep-alive phase. It indicates how long a device should wait before declaring the control channel dead. The HelloDeadInterval parameter should be at least three times the value of HelloInterval. It is used as a default value for lmpCcHelloDeadInterval. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.8,LMP-MIB::lmpCcHelloDeadIntervalDefaultMin,Unsigned32,read-write,,current,,This object specifies the default minimum value for the HelloDeadInterval parameter. It is used as a default value for lmpCcHelloDeadIntervalMin. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.9,LMP-MIB::lmpCcHelloDeadIntervalDefaultMax,Unsigned32,read-write,,current,,This object specifies the default maximum value for the HelloDeadInterval parameter. It is used as a default value for lmpCcHelloDeadIntervalMax. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.10,LMP-MIB::lmpControlChannelTable,,not-accessible,,current,,This table specifies LMP control channel information.
.1.3.6.1.2.1.10.227.1.10.1,LMP-MIB::lmpControlChannelEntry,,not-accessible,lmpCcId,current,,An entry in this table is created by an LMP-enabled device for every control channel. Whenever a new entry is created with lmpCcIsIf set to true(1), a corresponding entry is created in ifTable as well (see RFC 2863).
.1.3.6.1.2.1.10.227.1.10.1.1,LMP-MIB::lmpCcId,Unsigned32,not-accessible,,current,,This value represents the local control channel identifier. The control channel identifier is a non-zero 32-bit number.
.1.3.6.1.2.1.10.227.1.10.1.2,LMP-MIB::lmpCcUnderlyingIfIndex,Integer32,read-create,,current,,If lmpCcIsIf is set to true(1), this object carries the index into the ifTable of the entry that represents the LMP interface over which LMP will transmit its traffic. If this object is set to zero but lmpCcIsIf is set to true(1), the control channel is not currently associated with any underlying interface, and the control channel's operational status must not be up(1); nor should the control channel forward or receive traffic. If lmpCcIsIf is set to false(2), this object should be set to zero and ignored.
.1.3.6.1.2.1.10.227.1.10.1.3,LMP-MIB::lmpCcIsIf,INTEGER,read-create,,current,true(1):false(2),In implementations where the control channels are modeled as interfaces, the value of this object is true(1), and this control channel is represented by an interface in the interfaces group table as indicated by the value of lmpCcUnderlyingIfIndex. If control channels are not modeled as interfaces, the value of this object is false(2), and there is no corresponding interface for this control channel in the interfaces group table; the value of lmpCcUnderlyingIfIndex should be ignored.
.1.3.6.1.2.1.10.227.1.10.1.4,LMP-MIB::lmpCcNbrNodeId,OCTET,read-create,,current,,This is the Node ID of the control channel remote node. This value either is configured or gets created by the node when a Config message is received or when an outgoing Config message is acknowledged by the remote node.
.1.3.6.1.2.1.10.227.1.10.1.5,LMP-MIB::lmpCcRemoteId,Unsigned32,read-only,,current,,This value represents the remote control channel identifier (32-bit number). It is determined during the negotiation phase. A value of zero means that the remote control channel identifier has not yet been learned.
.1.3.6.1.2.1.10.227.1.10.1.6,LMP-MIB::lmpCcRemoteAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This value represents the remote control channel IP address type. In point-to-point configuration, this value can be set to unknown(0).
.1.3.6.1.2.1.10.227.1.10.1.7,LMP-MIB::lmpCcRemoteIpAddr,OCTET,read-create,,current,,This value represents the remote control channel Internet address for numbered control channel. The type of this address is determined by lmpCcRemoteAddressType. The control channel must be numbered on non-point-to-point configuration. For point-to-point configuration, the remote control channel address can be of type unknown, in which case this object must be a zero-length string. The lmpCcRemoteId object then identifies the unnumbered address.
.1.3.6.1.2.1.10.227.1.10.1.8,LMP-MIB::lmpCcSetupRole,INTEGER,read-create,,current,active(1):passive(2),The role that this node should take during establishment of this control channel. An active node will initiate establishment. A passive node will wait for the remote node to initiate. A pair of nodes that both take the passive role will never establish communications.
.1.3.6.1.2.1.10.227.1.10.1.9,LMP-MIB::lmpCcAuthentication,INTEGER,read-create,,current,true(1):false(2),This object indicates whether the control channel must use authentication.
.1.3.6.1.2.1.10.227.1.10.1.10,LMP-MIB::lmpCcHelloInterval,Unsigned32,read-create,,current,,This object specifies the value of the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalDefault.
.1.3.6.1.2.1.10.227.1.10.1.11,LMP-MIB::lmpCcHelloIntervalMin,Unsigned32,read-create,,current,,This object specifies the minimum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMinDefault.
.1.3.6.1.2.1.10.227.1.10.1.12,LMP-MIB::lmpCcHelloIntervalMax,Unsigned32,read-create,,current,,This object specifies the maximum value for the HelloInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault.
.1.3.6.1.2.1.10.227.1.10.1.13,LMP-MIB::lmpCcHelloIntervalNegotiated,Unsigned32,read-only,,current,,Once the control channel is active, this object represents the negotiated HelloInterval value.
.1.3.6.1.2.1.10.227.1.10.1.14,LMP-MIB::lmpCcHelloDeadInterval,Unsigned32,read-create,,current,,This object specifies the value of the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalDefault.
.1.3.6.1.2.1.10.227.1.10.1.15,LMP-MIB::lmpCcHelloDeadIntervalMin,Unsigned32,read-create,,current,,This object specifies the minimum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloDeadIntervalMinDefault.
.1.3.6.1.2.1.10.227.1.10.1.16,LMP-MIB::lmpCcHelloDeadIntervalMax,Unsigned32,read-create,,current,,This object specifies the maximum value for the HelloDeadInterval parameter. The default value for this object should be set to lmpCcHelloIntervalMaxDefault.
.1.3.6.1.2.1.10.227.1.10.1.17,LMP-MIB::lmpCcHelloDeadIntervalNegotiated,Unsigned32,read-only,,current,,Once the control channel is active, this object represents the negotiated HelloDeadInterval value.
.1.3.6.1.2.1.10.227.1.10.1.18,LMP-MIB::lmpCcLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the control channel entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.227.1.10.1.19,LMP-MIB::lmpCcAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired operational status of this control channel.
.1.3.6.1.2.1.10.227.1.10.1.20,LMP-MIB::lmpCcOperStatus,INTEGER,read-only,,current,up(1):down(2):configSnd(3):configRcv(4):active(5):goingDown(6),The actual operational status of this control channel.
.1.3.6.1.2.1.10.227.1.10.1.21,LMP-MIB::lmpCcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
.1.3.6.1.2.1.10.227.1.10.1.22,LMP-MIB::lmpCcStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the lmpControlChannelTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.227.1.11,LMP-MIB::lmpControlChannelPerfTable,,not-accessible,,current,,This table specifies LMP control channel performance counters.
.1.3.6.1.2.1.10.227.1.11.1,LMP-MIB::lmpControlChannelPerfEntry,,not-accessible,lmpCcId,current,,An entry in this table is created by a LMP-enabled device for every control channel. lmpCcCounterDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table.
.1.3.6.1.2.1.10.227.1.11.1.1,LMP-MIB::lmpCcInOctets,Counter32,read-only,,current,,The total number of LMP message octets received on the control channel.
.1.3.6.1.2.1.10.227.1.11.1.2,LMP-MIB::lmpCcInDiscards,Counter32,read-only,,current,,The number of inbound packets that were chosen to be discarded even though no errors had been detected. One possible reason for discarding such a packet could be to free up buffer space.
.1.3.6.1.2.1.10.227.1.11.1.3,LMP-MIB::lmpCcInErrors,Counter32,read-only,,current,,The number of inbound packets that contained errors preventing them from being processed by LMP.
.1.3.6.1.2.1.10.227.1.11.1.4,LMP-MIB::lmpCcOutOctets,Counter32,read-only,,current,,The total number of LMP message octets transmitted out of the control channel.
.1.3.6.1.2.1.10.227.1.11.1.5,LMP-MIB::lmpCcOutDiscards,Counter32,read-only,,current,,The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.
.1.3.6.1.2.1.10.227.1.11.1.6,LMP-MIB::lmpCcOutErrors,Counter32,read-only,,current,,The number of outbound packets that could not be transmitted because of errors.
.1.3.6.1.2.1.10.227.1.11.1.7,LMP-MIB::lmpCcConfigReceived,Counter32,read-only,,current,,This object counts the number of Config messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.8,LMP-MIB::lmpCcConfigSent,Counter32,read-only,,current,,This object counts the number of Config messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.9,LMP-MIB::lmpCcConfigRetransmit,Counter32,read-only,,current,,This object counts the number of Config messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.11.1.10,LMP-MIB::lmpCcConfigAckReceived,Counter32,read-only,,current,,This object counts the number of ConfigAck messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.11,LMP-MIB::lmpCcConfigAckSent,Counter32,read-only,,current,,This object counts the number of ConfigAck messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.12,LMP-MIB::lmpCcConfigNackReceived,Counter32,read-only,,current,,This object counts the number of ConfigNack messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.13,LMP-MIB::lmpCcConfigNackSent,Counter32,read-only,,current,,This object counts the number of ConfigNack messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.14,LMP-MIB::lmpCcHelloReceived,Counter32,read-only,,current,,This object counts the number of Hello messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.15,LMP-MIB::lmpCcHelloSent,Counter32,read-only,,current,,This object counts the number of Hello messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.16,LMP-MIB::lmpCcBeginVerifyReceived,Counter32,read-only,,current,,This object counts the number of BeginVerify messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.17,LMP-MIB::lmpCcBeginVerifySent,Counter32,read-only,,current,,This object counts the number of BeginVerify messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.18,LMP-MIB::lmpCcBeginVerifyRetransmit,Counter32,read-only,,current,,This object counts the number of BeginVerify messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.11.1.19,LMP-MIB::lmpCcBeginVerifyAckReceived,Counter32,read-only,,current,,This object counts the number of BeginVerifyAck messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.20,LMP-MIB::lmpCcBeginVerifyAckSent,Counter32,read-only,,current,,This object counts the number of BeginVerifyAck messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.21,LMP-MIB::lmpCcBeginVerifyNackReceived,Counter32,read-only,,current,,This object counts the number of BeginVerifyNack messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.22,LMP-MIB::lmpCcBeginVerifyNackSent,Counter32,read-only,,current,,This object counts the number of BeginVerifyNack messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.23,LMP-MIB::lmpCcEndVerifyReceived,Counter32,read-only,,current,,This object counts the number of EndVerify messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.24,LMP-MIB::lmpCcEndVerifySent,Counter32,read-only,,current,,This object counts the number of EndVerify messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.25,LMP-MIB::lmpCcEndVerifyRetransmit,Counter32,read-only,,current,,This object counts the number of EndVerify messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.11.1.26,LMP-MIB::lmpCcEndVerifyAckReceived,Counter32,read-only,,current,,This object counts the number of EndVerifyAck messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.27,LMP-MIB::lmpCcEndVerifyAckSent,Counter32,read-only,,current,,This object counts the number of EndVerifyAck messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.28,LMP-MIB::lmpCcTestStatusSuccessReceived,Counter32,read-only,,current,,This object counts the number of TestStatusSuccess messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.29,LMP-MIB::lmpCcTestStatusSuccessSent,Counter32,read-only,,current,,This object counts the number of TestStatusSuccess messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.30,LMP-MIB::lmpCcTestStatusSuccessRetransmit,Counter32,read-only,,current,,This object counts the number of TestStatusSuccess messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.11.1.31,LMP-MIB::lmpCcTestStatusFailureReceived,Counter32,read-only,,current,,This object counts the number of TestStatusFailure messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.32,LMP-MIB::lmpCcTestStatusFailureSent,Counter32,read-only,,current,,This object counts the number of TestStatusFailure messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.33,LMP-MIB::lmpCcTestStatusFailureRetransmit,Counter32,read-only,,current,,This object counts the number of TestStatusFailure messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.11.1.34,LMP-MIB::lmpCcTestStatusAckReceived,Counter32,read-only,,current,,This object counts the number of TestStatusAck messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.35,LMP-MIB::lmpCcTestStatusAckSent,Counter32,read-only,,current,,This object counts the number of TestStatusAck messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.36,LMP-MIB::lmpCcLinkSummaryReceived,Counter32,read-only,,current,,This object counts the number of LinkSummary messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.37,LMP-MIB::lmpCcLinkSummarySent,Counter32,read-only,,current,,This object counts the number of LinkSummary messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.38,LMP-MIB::lmpCcLinkSummaryRetransmit,Counter32,read-only,,current,,This object counts the number of LinkSummary messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.11.1.39,LMP-MIB::lmpCcLinkSummaryAckReceived,Counter32,read-only,,current,,This object counts the number of LinkSummaryAck messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.40,LMP-MIB::lmpCcLinkSummaryAckSent,Counter32,read-only,,current,,This object counts the number of LinkSummaryAck messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.41,LMP-MIB::lmpCcLinkSummaryNackReceived,Counter32,read-only,,current,,This object counts the number of LinkSummaryNack messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.42,LMP-MIB::lmpCcLinkSummaryNackSent,Counter32,read-only,,current,,This object counts the number of LinkSummaryNack messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.43,LMP-MIB::lmpCcChannelStatusReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.44,LMP-MIB::lmpCcChannelStatusSent,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.45,LMP-MIB::lmpCcChannelStatusRetransmit,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been retransmitted on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.46,LMP-MIB::lmpCcChannelStatusAckReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatusAck messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.47,LMP-MIB::lmpCcChannelStatusAckSent,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.48,LMP-MIB::lmpCcChannelStatusReqReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatusRequest messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.49,LMP-MIB::lmpCcChannelStatusReqSent,Counter32,read-only,,current,,This object counts the number of ChannelStatusRequest messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.50,LMP-MIB::lmpCcChannelStatusReqRetransmit,Counter32,read-only,,current,,This object counts the number of ChannelStatusRequest messages that have been retransmitted on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.51,LMP-MIB::lmpCcChannelStatusRspReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatusResponse messages that have been received on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.52,LMP-MIB::lmpCcChannelStatusRspSent,Counter32,read-only,,current,,This object counts the number of ChannelStatusResponse messages that have been sent on this control channel.
.1.3.6.1.2.1.10.227.1.11.1.53,LMP-MIB::lmpCcCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one or more of this control channel's counters suffered a discontinuity. The relevant counters are the specific instances associated with this control channel of any Counter32 object contained in the lmpControlChannelPerfTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.227.1.12,LMP-MIB::lmpTeLinkTable,,not-accessible,,current,,This table specifies the LMP-specific TE link information. Overall TE link information is kept in three separate tables: ifTable for interface-specific information, lmpTeLinkTable for LMP specific information, and teLinkTable for generic TE link information. ifIndex is the common index to all tables.
.1.3.6.1.2.1.10.227.1.12.1,LMP-MIB::lmpTeLinkEntry,,not-accessible,ifIndex,current,,An entry in this table exists for each ifEntry with an ifType of teLink(200) that is managed by LMP. An ifEntry with an ifIndex must exist before the corresponding lmpTeLinkEntry is created. If a TE link entry in the ifTable is destroyed, then so is the corresponding entry in the lmpTeLinkTable. The administrative status value is controlled from the ifEntry. Setting the administrative status to testing prompts LMP to start link verification on the TE link. Information about the TE link that is not LMP specific is contained in the teLinkTable of the TE-LINK-STD-MIB MIB module.
.1.3.6.1.2.1.10.227.1.12.1.1,LMP-MIB::lmpTeLinkNbrRemoteNodeId,OCTET,read-create,,current,,This is the Node ID of the TE link remote node. This value may be learned during the control channel parameter negotiation phase (in the Config message). Node ID is an address whose type must be IPv4.
.1.3.6.1.2.1.10.227.1.12.1.2,LMP-MIB::lmpTeLinkVerification,INTEGER,read-create,,current,true(1):false(2),This object indicates whether the LMP link verification procedure is enabled for this TE link.
.1.3.6.1.2.1.10.227.1.12.1.3,LMP-MIB::lmpTeLinkFaultManagement,INTEGER,read-create,,current,true(1):false(2),This object indicates whether the LMP fault management procedure is enabled on this TE link.
.1.3.6.1.2.1.10.227.1.12.1.4,LMP-MIB::lmpTeLinkDwdm,INTEGER,read-create,,current,true(1):false(2),This object indicates whether the LMP DWDM procedure is enabled on this TE link.
.1.3.6.1.2.1.10.227.1.12.1.5,LMP-MIB::lmpTeLinkOperStatus,INTEGER,read-only,,current,up(1):down(2):testing(3):init(4):degraded(5),The actual operational status of this TE link. The status is set to testing when the TE link is performing link verification. A degraded state indicates that there is no active control channel between the pair of nodes that form the endpoints of the TE link, but that at least one data-bearing link on the TE link is allocated.
.1.3.6.1.2.1.10.227.1.12.1.6,LMP-MIB::lmpTeLinkRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
.1.3.6.1.2.1.10.227.1.12.1.7,LMP-MIB::lmpTeLinkStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the lmpTeLinkTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.227.1.13,LMP-MIB::lmpGlobalLinkVerificationInterval,Unsigned32,read-write,,current,,This object indicates how often the link verification procedure is executed. The interval is in milliseconds. A value of 0 is used to indicate that the link verification procedure should not be executed. The interval specified in this object should be large enough to allow the verification procedure to be completed before the start of the next interval. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.14,LMP-MIB::lmpLinkVerificationTable,,not-accessible,,current,,This table specifies TE link information associated with the LMP verification procedure.
.1.3.6.1.2.1.10.227.1.14.1,LMP-MIB::lmpLinkVerificationEntry,,not-accessible,ifIndex,current,,An entry in this table is created by an LMP-enabled device for every TE link that supports the LMP verification procedure.
.1.3.6.1.2.1.10.227.1.14.1.1,LMP-MIB::lmpLinkVerifyInterval,Unsigned32,read-create,,current,,This object specifies the VerifyInterval parameter used in the LMP link verification process. It indicates the interval at which the Test messages are sent.
.1.3.6.1.2.1.10.227.1.14.1.2,LMP-MIB::lmpLinkVerifyDeadInterval,Unsigned32,read-create,,current,,This object specifies the VerifyDeadInterval parameter used in the verification of the physical connectivity of data- bearing links. It specifies the observation period used to detect a Test message at the remote node.
.1.3.6.1.2.1.10.227.1.14.1.3,LMP-MIB::lmpLinkVerifyTransportMechanism,BITS,read-create,,current,payload(0):dccSectionOverheadBytes(1):dccLineOverheadBytes(2):j0Trace(3):j1Trace(4):j2Trace(5),This defines the transport mechanism for the Test messages. The scope of this bit mask is restricted to each link encoding type. The local node will set the bits corresponding to the various mechanisms it can support for transmitting LMP Test messages. The receiver chooses the appropriate mechanism in the BeginVerifyAck message.
.1.3.6.1.2.1.10.227.1.14.1.4,LMP-MIB::lmpLinkVerifyAllLinks,INTEGER,read-create,,current,true(1):false(2),A value of true(1) for this object indicates that the verification process checks all unallocated links; otherwise, only the new ports or component links that have been added to this TE link are verified.
.1.3.6.1.2.1.10.227.1.14.1.5,LMP-MIB::lmpLinkVerifyTransmissionRate,Unsigned32,read-create,,current,,This is the transmission rate of the data link over which the Test messages will be transmitted and is expressed in bytes per second.
.1.3.6.1.2.1.10.227.1.14.1.6,LMP-MIB::lmpLinkVerifyWavelength,Unsigned32,read-create,,current,,This value corresponds to the wavelength at which the Test messages will be transmitted and is measured in nanometers (nm). If each data-bearing link corresponds to a separate wavelength, then this value should be set to 0.
.1.3.6.1.2.1.10.227.1.14.1.7,LMP-MIB::lmpLinkVerifyRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
.1.3.6.1.2.1.10.227.1.14.1.8,LMP-MIB::lmpLinkVerifyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the lmpLinkVerificationTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.227.1.15,LMP-MIB::lmpTeLinkPerfTable,,not-accessible,,current,,This table specifies LMP TE link performance counters.
.1.3.6.1.2.1.10.227.1.15.1,LMP-MIB::lmpTeLinkPerfEntry,,not-accessible,ifIndex,current,,An entry in this table is created by an LMP-enabled device for every TE link. lmpTeCounterDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table.
.1.3.6.1.2.1.10.227.1.15.1.1,LMP-MIB::lmpTeInOctets,Counter32,read-only,,current,,The total number of LMP message octets received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.2,LMP-MIB::lmpTeOutOctets,Counter32,read-only,,current,,The total number of LMP message octets transmitted out for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.3,LMP-MIB::lmpTeBeginVerifyReceived,Counter32,read-only,,current,,This object counts the number of BeginVerify messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.4,LMP-MIB::lmpTeBeginVerifySent,Counter32,read-only,,current,,This object counts the number of BeginVerify messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.5,LMP-MIB::lmpTeBeginVerifyRetransmit,Counter32,read-only,,current,,This object counts the number of BeginVerify messages that have been retransmitted for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.6,LMP-MIB::lmpTeBeginVerifyAckReceived,Counter32,read-only,,current,,This object counts the number of BeginVerifyAck messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.7,LMP-MIB::lmpTeBeginVerifyAckSent,Counter32,read-only,,current,,This object counts the number of BeginVerifyAck messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.8,LMP-MIB::lmpTeBeginVerifyNackReceived,Counter32,read-only,,current,,This object counts the number of BeginVerifyNack messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.9,LMP-MIB::lmpTeBeginVerifyNackSent,Counter32,read-only,,current,,This object counts the number of BeginVerifyNack messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.10,LMP-MIB::lmpTeEndVerifyReceived,Counter32,read-only,,current,,This object counts the number of EndVerify messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.11,LMP-MIB::lmpTeEndVerifySent,Counter32,read-only,,current,,This object counts the number of EndVerify messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.12,LMP-MIB::lmpTeEndVerifyRetransmit,Counter32,read-only,,current,,This object counts the number of EndVerify messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.15.1.13,LMP-MIB::lmpTeEndVerifyAckReceived,Counter32,read-only,,current,,This object counts the number of EndVerifyAck messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.14,LMP-MIB::lmpTeEndVerifyAckSent,Counter32,read-only,,current,,This object counts the number of EndVerifyAck messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.15,LMP-MIB::lmpTeTestStatusSuccessReceived,Counter32,read-only,,current,,This object counts the number of TestStatusSuccess messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.16,LMP-MIB::lmpTeTestStatusSuccessSent,Counter32,read-only,,current,,This object counts the number of TestStatusSuccess messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.17,LMP-MIB::lmpTeTestStatusSuccessRetransmit,Counter32,read-only,,current,,This object counts the number of TestStatusSuccess messages that have been retransmitted for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.18,LMP-MIB::lmpTeTestStatusFailureReceived,Counter32,read-only,,current,,This object counts the number of TestStatusFailure messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.19,LMP-MIB::lmpTeTestStatusFailureSent,Counter32,read-only,,current,,This object counts the number of TestStatusFailure messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.20,LMP-MIB::lmpTeTestStatusFailureRetransmit,Counter32,read-only,,current,,This object counts the number of TestStatusFailure messages that have been retransmitted on this TE link.
.1.3.6.1.2.1.10.227.1.15.1.21,LMP-MIB::lmpTeTestStatusAckReceived,Counter32,read-only,,current,,This object counts the number of TestStatusAck messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.22,LMP-MIB::lmpTeTestStatusAckSent,Counter32,read-only,,current,,This object counts the number of TestStatusAck messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.23,LMP-MIB::lmpTeLinkSummaryReceived,Counter32,read-only,,current,,This object counts the number of LinkSummary messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.24,LMP-MIB::lmpTeLinkSummarySent,Counter32,read-only,,current,,This object counts the number of LinkSummary messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.25,LMP-MIB::lmpTeLinkSummaryRetransmit,Counter32,read-only,,current,,This object counts the number of LinkSummary messages that have been retransmitted over this control channel.
.1.3.6.1.2.1.10.227.1.15.1.26,LMP-MIB::lmpTeLinkSummaryAckReceived,Counter32,read-only,,current,,This object counts the number of LinkSummaryAck messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.27,LMP-MIB::lmpTeLinkSummaryAckSent,Counter32,read-only,,current,,This object counts the number of LinkSummaryAck messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.28,LMP-MIB::lmpTeLinkSummaryNackReceived,Counter32,read-only,,current,,This object counts the number of LinkSummaryNack messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.29,LMP-MIB::lmpTeLinkSummaryNackSent,Counter32,read-only,,current,,This object counts the number of LinkSummaryNack messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.30,LMP-MIB::lmpTeChannelStatusReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.31,LMP-MIB::lmpTeChannelStatusSent,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.32,LMP-MIB::lmpTeChannelStatusRetransmit,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been retransmitted for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.33,LMP-MIB::lmpTeChannelStatusAckReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatusAck messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.34,LMP-MIB::lmpTeChannelStatusAckSent,Counter32,read-only,,current,,This object counts the number of ChannelStatus messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.35,LMP-MIB::lmpTeChannelStatusReqReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatusRequest messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.36,LMP-MIB::lmpTeChannelStatusReqSent,Counter32,read-only,,current,,This object counts the number of ChannelStatusRequest messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.37,LMP-MIB::lmpTeChannelStatusReqRetransmit,Counter32,read-only,,current,,This object counts the number of ChannelStatusRequest messages that have been retransmitted for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.38,LMP-MIB::lmpTeChannelStatusRspReceived,Counter32,read-only,,current,,This object counts the number of ChannelStatusResponse messages that have been received for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.39,LMP-MIB::lmpTeChannelStatusRspSent,Counter32,read-only,,current,,This object counts the number of ChannelStatusResponse messages that have been sent for this TE link.
.1.3.6.1.2.1.10.227.1.15.1.40,LMP-MIB::lmpTeCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one or more of this TE link's counters suffered a discontinuity. The relevant counters are the specific instances associated with this TE link of any Counter32 object contained in the lmpTeLinkPerfTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.227.1.16,LMP-MIB::lmpDataLinkTable,,not-accessible,,current,,This table specifies the data-bearing links managed by the LMP.
.1.3.6.1.2.1.10.227.1.16.1,LMP-MIB::lmpDataLinkEntry,,not-accessible,ifIndex,current,,An entry in this table exists for each ifEntry that represents a data-bearing link. An ifEntry with an ifIndex must exist before the corresponding lmpDataLinkEntry is created. If an entry representing the data-bearing link is destroyed in the ifTable, then so is the corresponding entry in the lmpDataLinkTable. The administrative status value is controlled from the ifEntry. The index to this table is also used to get information in the componentLinkTable of the TE-LINK-STD-MIB MIB module.
.1.3.6.1.2.1.10.227.1.16.1.1,LMP-MIB::lmpDataLinkType,INTEGER,read-only,,current,port(1):componentLink(2),This attribute specifies whether this data-bearing link is a port or a component link. Component links are multiplex capable, whereas ports are not multiplex capable.
.1.3.6.1.2.1.10.227.1.16.1.2,LMP-MIB::lmpDataLinkAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This attribute specifies the data-bearing link IP address type. If the data-bearing link is unnumbered, the address type must be set to unknown(0).
.1.3.6.1.2.1.10.227.1.16.1.3,LMP-MIB::lmpDataLinkIpAddr,OCTET,read-create,,current,,The local Internet address for numbered links. The type of this address is determined by the value of lmpDataLinkAddressType object. For IPv4 and IPv6 numbered links, this object represents the local IP address associated with the data-bearing link. For an unnumbered link, the local address is of type unknown, and this object is set to the zero-length string; the ifIndex object then identifies the unnumbered address.
.1.3.6.1.2.1.10.227.1.16.1.4,LMP-MIB::lmpDataLinkRemoteIpAddress,OCTET,read-create,,current,,The remote Internet address for numbered data-bearing links. The type of this address is determined by the lmpDataLinkAddressType object. For IPv4 and IPv6 numbered links, this object represents the remote IP address associated with the data-bearing link. For an unnumbered link, the remote address is of type unknown, and this object is set to the zero-length string; the lmpDataLinkRemoteIfId object then identifies the unnumbered address. This information is either configured manually or communicated by the remote node during the link verification procedure.
.1.3.6.1.2.1.10.227.1.16.1.5,LMP-MIB::lmpDataLinkRemoteIfId,Integer32,read-create,,current,,Interface identifier of the remote end point. This information is either configured manually or communicated by the remote node during the link verification procedure.
.1.3.6.1.2.1.10.227.1.16.1.6,LMP-MIB::lmpDataLinkEncodingType,INTEGER,read-create,,current,packet(1):ethernet(2):ansiEtsiPdh(3):sdhItuSonetAnsi(5):digitalWrapper(7):lambda(8):fiber(9):fiberChannel(11),The encoding type of the data-bearing link.
.1.3.6.1.2.1.10.227.1.16.1.7,LMP-MIB::lmpDataLinkActiveOperStatus,INTEGER,read-only,,current,upAlloc(1):upFree(2):down(3):testing(4),The actual operational status of this data-bearing link (active FSM).
.1.3.6.1.2.1.10.227.1.16.1.8,LMP-MIB::lmpDataLinkPassiveOperStatus,INTEGER,read-only,,current,upAlloc(1):upFree(2):down(3):psvTst(4),The actual operational status of this data-bearing link (passive FSM).
.1.3.6.1.2.1.10.227.1.16.1.9,LMP-MIB::lmpDataLinkRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. None of the writable objects in a row can be changed if the status is active(1). All read-create objects must have valid and consistent values before the row can be activated.
.1.3.6.1.2.1.10.227.1.16.1.10,LMP-MIB::lmpDataLinkStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the lmpDataLinkTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.2.1.10.227.1.17,LMP-MIB::lmpDataLinkPerfTable,,not-accessible,,current,,This table specifies the data-bearing links LMP performance counters.
.1.3.6.1.2.1.10.227.1.17.1,LMP-MIB::lmpDataLinkPerfEntry,,not-accessible,ifIndex,current,,An entry in this table contains information about the LMP performance counters for the data-bearing links. lmpDataLinkDiscontinuityTime is used to indicate potential discontinuity for all counter objects in this table.
.1.3.6.1.2.1.10.227.1.17.1.1,LMP-MIB::lmpDataLinkTestReceived,Counter32,read-only,,current,,This object counts the number of Test messages that have been received on this data-bearing link.
.1.3.6.1.2.1.10.227.1.17.1.2,LMP-MIB::lmpDataLinkTestSent,Counter32,read-only,,current,,This object counts the number of Test messages that have been sent on this data-bearing link.
.1.3.6.1.2.1.10.227.1.17.1.3,LMP-MIB::lmpDataLinkActiveTestSuccess,Counter32,read-only,,current,,This object counts the number of data-bearing link tests that were successful on the active side of this data- bearing link.
.1.3.6.1.2.1.10.227.1.17.1.4,LMP-MIB::lmpDataLinkActiveTestFailure,Counter32,read-only,,current,,This object counts the number of data-bearing link tests that failed on the active side of this data-bearing link.
.1.3.6.1.2.1.10.227.1.17.1.5,LMP-MIB::lmpDataLinkPassiveTestSuccess,Counter32,read-only,,current,,This object counts the number of data-bearing link tests that were successful on the passive side of this data- bearing link.
.1.3.6.1.2.1.10.227.1.17.1.6,LMP-MIB::lmpDataLinkPassiveTestFailure,Counter32,read-only,,current,,This object counts the number of data-bearing link tests that failed on the passive side of this data-bearing link.
.1.3.6.1.2.1.10.227.1.17.1.7,LMP-MIB::lmpDataLinkDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one or more of this data-bearing link's counters suffered a discontinuity. The relevant counters are the specific instances associated with this data-bearing link of any Counter32 object contained in the lmpDataLinkPerfTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.227.1.18,LMP-MIB::lmpNotificationMaxRate,Unsigned32,read-write,,current,,The LMP notification rate depends on the size of the network, the type of links, the network configuration, the reliability of the network, etc. When this MIB was designed, care was taken to minimize the amount of notifications generated for LMP purposes. Wherever possible, notifications are state driven, meaning that the notifications are sent only when the system changes state. The only notifications that are repeated and that could cause a problem as far as congestion is concerned are the ones associated with data link verification. Without any considerations to handling of these notifications, a problem may arise if the number of data links is high. Since the data link verification notifications can happen only once per data link per link verification interval, the notification rate should be sustainable if one chooses an appropriate link verification interval for a given network configuration. For instance, a network of 100 nodes with 5 links of 128 wavelengths each and a link verification of 1 minute, where no more than 10% of the links failed at any given time, would have 1 notification per second sent from each node, or 100 notifications per second for the whole network. The rest of the notifications are negligible compared to this number. To alleviate the congestion problem, the lmpNotificationMaxRate object can be used to implement a throttling mechanism. It is also possible to enable/disable certain type of notifications. This variable indicates the maximum number of notifications issued per minute. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period or may queue them until an appropriate time. A value of 0 means that no throttling is applied and events may be notified at the rate at which they occur. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.19,LMP-MIB::lmpLinkPropertyNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),If this object is true(1), then it enables the generation of lmpTeLinkPropertyMismatch and lmpDataLinkPropertyMismatch notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.20,LMP-MIB::lmpUnprotectedNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),If this object is true(1), then it enables the generation of lmpUnprotected notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.21,LMP-MIB::lmpCcUpDownNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),If this object is true(1), then it enables the generation of lmpControlChannelUp and lmpControlChannelDown notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.22,LMP-MIB::lmpTeLinkNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),If this object is true(1), then it enables the generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded notifications; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.1.23,LMP-MIB::lmpDataLinkNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),If this object is true(1), then it enables the generation of lmpDataLinkVerificationFailure notification; otherwise, these notifications are not emitted. Implementations should save the value of this object in persistent memory so that it survives restarts or reboot.
.1.3.6.1.2.1.10.227.2,LMP-MIB::lmpConformance,,,,,,
.1.3.6.1.2.1.10.227.2.1,LMP-MIB::lmpCompliances,,,,,,
.1.3.6.1.2.1.10.227.2.1.1,LMP-MIB::lmpModuleFullCompliance,,,,,,Compliance statement for agents that support the configuration and monitoring of LMP MIB.
.1.3.6.1.2.1.10.227.2.1.2,LMP-MIB::lmpModuleReadOnlyCompliance,,,,,,Compliance statement for agents that support the monitoring of the LMP MIB.
.1.3.6.1.2.1.10.227.2.2,LMP-MIB::lmpGroups,,,,,,
.1.3.6.1.2.1.10.227.2.2.1,LMP-MIB::lmpNodeGroup,,,,,,Collection of objects that represent LMP node configuration.
.1.3.6.1.2.1.10.227.2.2.2,LMP-MIB::lmpControlChannelGroup,,,,,,Objects that can be used to configure LMP interface.
.1.3.6.1.2.1.10.227.2.2.3,LMP-MIB::lmpCcIsInterfaceGroup,,,,,,Objects that can be used to configure control channels that are interfaces.
.1.3.6.1.2.1.10.227.2.2.4,LMP-MIB::lmpCcIsNotInterfaceGroup,,,,,,Objects that can be used to configure control channels that are not interfaces.
.1.3.6.1.2.1.10.227.2.2.5,LMP-MIB::lmpLinkPropertyCorrelationGroup,,,,,,Collection of objects used to configure the link property correlation procedure.
.1.3.6.1.2.1.10.227.2.2.6,LMP-MIB::lmpLinkVerificationGroup,,,,,,Collection of objects that represent the link verification procedure configuration.
.1.3.6.1.2.1.10.227.2.2.7,LMP-MIB::lmpPerfGroup,,,,,,Collection of objects used to provide performance information about LMP interfaces and data-bearing links.
.1.3.6.1.2.1.10.227.2.2.8,LMP-MIB::lmpTeLinkGroup,,,,,,Objects that can be used to configure TE links.
.1.3.6.1.2.1.10.227.2.2.9,LMP-MIB::lmpDataLinkGroup,,,,,,Collection of objects that represent data-bearing link configuration.
.1.3.6.1.2.1.10.227.2.2.10,LMP-MIB::lmpNotificationGroup,,,,,,Set of notifications defined in this module.
.1.3.6.1.2.1.10.228,VDSL-LINE-EXT-SCM-MIB::vdslExtSCMMIB,,,,,,The VDSL-LINE-MIB found in RFC 3728 defines objects for the Vtuc -- VDSL transceiver at near (Central) end of line Vtur -- VDSL transceiver at Remote end of line Vtu -- One of either Vtuc or Vtur Curr -- Current Atn -- Attenuation LCS -- Line Code Specific Max -- Maximum Mgn -- Margin PSD -- Power Spectral Density Rx -- Receive Snr -- Signal to Noise Ratio Tx -- Transmit
.1.3.6.1.2.1.10.228.1,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMMib,,,,,,
.1.3.6.1.2.1.10.228.1.1,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMMibObjects,,,,,,
.1.3.6.1.2.1.10.228.1.1.1,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandTable,,not-accessible,,current,,This table contains transmit band descriptor configuration information for a VDSL line. Each entry in this table reflects the configuration for one of possibly many bands of a single carrier modulation (SCM) VDSL line. For each profile which is associated with a VDSL line using SCM line coding, five entries in this table will exist, one for each of the five bands. Bands which are not in use will be marked as unused. These entries are defined by a manager and can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use SCM, it has no effect on the operation of that line.
.1.3.6.1.2.1.10.228.1.1.1.1,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandEntry,,not-accessible,vdslLineConfProfileName:vdslLineSCMConfProfileBandId,current,,Each entry consists of a list of parameters that represents the configuration of a single carrier modulation VDSL modem transmit band. A default profile with an index of 'DEFVAL', will always exist and its parameters will be set to vendor specific values, unless otherwise specified in this document. All read-create objects defined in this MIB module SHOULD be stored persistently.
.1.3.6.1.2.1.10.228.1.1.1.1.1,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandId,INTEGER,not-accessible,,current,optionalBand(1):firstDownstreamBand(2):firstUpstreamBand(3):secondDownstreamBand(4):secondUpstreamBand(5):thirdDownstreamBand(6):thirdUpstreamBand(7),The BandId for this entry, which specifies which band is being referred to.
.1.3.6.1.2.1.10.228.1.1.1.1.2,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandInUse,INTEGER,read-create,,current,true(1):false(2),Indicates whether this band is in use. If set to True this band is in use.
.1.3.6.1.2.1.10.228.1.1.1.1.3,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandCenterFrequency,Unsigned32,read-create,,current,,Specifies the center frequency in Hz
.1.3.6.1.2.1.10.228.1.1.1.1.4,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandSymbolRate,Unsigned32,read-create,,current,,The requested symbol rate in baud.
.1.3.6.1.2.1.10.228.1.1.1.1.5,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandConstellationSize,Unsigned32,read-create,,current,,Specifies the constellation size.
.1.3.6.1.2.1.10.228.1.1.1.1.6,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandTransmitPSDLevel,Unsigned32,read-create,,current,,The requested transmit power spectral density for the VDSL modem. The Actual value in -0.25 dBm/Hz.
.1.3.6.1.2.1.10.228.1.1.1.1.7,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMConfProfileBandRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile activated by setting this object to `active'. When `active' is set, the system will validate the profile. None of the columns in this row may be modified while the row is in the `active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must be first unreferenced from all associated lines.
.1.3.6.1.2.1.10.228.1.1.2,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandTable,,not-accessible,,current,,This table provides one row for each SCM Vtu band. This table is read only as it reflects the current physical parameters of each band. For each ifIndex which is associated with a VDSL line using SCM line coding, five entries in this table will exist, one for each of the five bands. Bands which are not in use will be marked as unused.
.1.3.6.1.2.1.10.228.1.1.2.1,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandEntry,,not-accessible,ifIndex:vdslLineSCMPhysBandId,current,,An entry in the vdslLineSCMPhysBandTable.
.1.3.6.1.2.1.10.228.1.1.2.1.1,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandId,INTEGER,not-accessible,,current,optionalBand(1):firstDownstreamBand(2):firstUpstreamBand(3):secondDownstreamBand(4):secondUpstreamBand(5):thirdDownstreamBand(6):thirdUpstreamBand(7),The BandId for this entry, which specifies which band is being referred to.
.1.3.6.1.2.1.10.228.1.1.2.1.2,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandInUse,INTEGER,read-only,,current,true(1):false(2),Indicates whether this band is in use. If set to True this band is in use.
.1.3.6.1.2.1.10.228.1.1.2.1.3,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandCurrCenterFrequency,Unsigned32,read-only,,current,,The current center frequency in Hz for this band.
.1.3.6.1.2.1.10.228.1.1.2.1.4,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandCurrSymbolRate,Unsigned32,read-only,,current,,The current value of the symbol rate in baud for this band.
.1.3.6.1.2.1.10.228.1.1.2.1.5,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandCurrConstellationSize,Unsigned32,read-only,,current,,The current constellation size on this band.
.1.3.6.1.2.1.10.228.1.1.2.1.6,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandCurrPSDLevel,Unsigned32,read-only,,current,,The transmit power spectral density for the VDSL modem.
.1.3.6.1.2.1.10.228.1.1.2.1.7,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandCurrSnrMgn,Integer32,read-only,,current,,Noise margin as seen by this Vtu and band with respect to its received signal in 0.25 dB.
.1.3.6.1.2.1.10.228.1.1.2.1.8,VDSL-LINE-EXT-SCM-MIB::vdslLineSCMPhysBandCurrAtn,Unsigned32,read-only,,current,,Measured difference in the total power transmitted by the peer Vtu on this band and the total power received by this Vtu on this band in 0.25 dB.
.1.3.6.1.2.1.10.228.1.2,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMConformance,,,,,,
.1.3.6.1.2.1.10.228.1.2.1,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMGroups,,,,,,
.1.3.6.1.2.1.10.228.1.2.1.1,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMGroup,,,,,,A collection of objects providing configuration information for a VDSL line based upon single carrier modulation modem.
.1.3.6.1.2.1.10.228.1.2.2,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMCompliances,,,,,,
.1.3.6.1.2.1.10.228.1.2.2.1,VDSL-LINE-EXT-SCM-MIB::vdslLineExtSCMMibCompliance,,,,,,The compliance statement for SNMP entities which manage VDSL interfaces.
.1.3.6.1.2.1.10.229,VDSL-LINE-EXT-MCM-MIB::vdslExtMCMMIB,,,,,,The VDSL-LINE-MIB found in RFC 3728 defines objects for the management of a pair of VDSL transceivers at each end of the VDSL line. The VDSL-LINE-MIB configures and monitors the line code independent parameters (TC layer) of the VDSL line. This MIB module is an optional extension of the VDSL-LINE-MIB and defines objects for configuration and monitoring of the line code specific (LCS) elements (PMD layer) for VDSL lines using MCM coding. The objects in this extension MIB MUST NOT be used for VDSL lines using Single Carrier Modulation (SCM) line coding. If an object in this extension MIB is referenced by a line which does not use MCM, it has no effect on the operation of that line. Naming Conventions: Vtuc -- (VTUC) transceiver at near (Central) end of line Vtur -- (VTUR) transceiver at Remote end of line Vtu -- One of either Vtuc or Vtur Curr -- Current LCS -- Line Code Specific Max -- Maximum PSD -- Power Spectral Density Rx -- Receive Tx -- Transmit Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4070: see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.229.1,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMMib,,,,,,
.1.3.6.1.2.1.10.229.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMMibObjects,,,,,,
.1.3.6.1.2.1.10.229.1.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTable,,not-accessible,,current,,This table contains additional information on multiple carrier VDSL lines. One entry in this table reflects a profile defined by a manager which can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use MCM, it has no effect on the operation of that line. All read-create-objects defined in this table SHOULD be stored persistently.
.1.3.6.1.2.1.10.229.1.1.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileEntry,,not-accessible,vdslLineConfProfileName,current,,Each entry consists of a list of parameters that represents the configuration of a multiple carrier modulation VDSL modem.
.1.3.6.1.2.1.10.229.1.1.1.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxWindowLength,Unsigned32,read-create,,current,,Specifies the length of the transmit window, counted in samples at the sampling rate corresponding to the negotiated value of N.
.1.3.6.1.2.1.10.229.1.1.1.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by setting this object to `active'. When `active' is set, the system will validate the profile. None of the columns in this row may be modified while the row is in the 'active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must first be unreferenced from all associated lines.
.1.3.6.1.2.1.10.229.1.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxBandTable,,not-accessible,,current,,This table contains transmit band descriptor configuration information for a VDSL line. Each entry in this table reflects the configuration for one of possibly many bands with a multiple carrier modulation (MCM) VDSL line. These entries are defined by a manager and can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use MCM, it has no effect on the operation of that line. All read-create-objects defined in this table SHOULD be stored persistently.
.1.3.6.1.2.1.10.229.1.1.2.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxBandEntry,,not-accessible,vdslLineConfProfileName:vdslLineMCMConfProfileTxBandNumber,current,,Each entry consists of a transmit band descriptor, which is defined by a start and a stop tone index.
.1.3.6.1.2.1.10.229.1.1.2.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxBandNumber,Unsigned32,not-accessible,,current,,The index for this band descriptor entry.
.1.3.6.1.2.1.10.229.1.1.2.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxBandStart,Unsigned32,read-create,,current,,Start tone index for this band.
.1.3.6.1.2.1.10.229.1.1.2.1.3,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxBandStop,Unsigned32,read-create,,current,,Stop tone index for this band.
.1.3.6.1.2.1.10.229.1.1.2.1.4,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxBandRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by setting this object to `active'. When `active' is set, the system will validate the profile. Each entry must be internally consistent, the Stop Tone must be greater than the Start Tone. Each entry must also be externally consistent, all entries indexed by a specific profile must not overlap. Validation of the profile will check both internal and external consistency. None of the columns in this row may be modified while the row is in the 'active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must be first unreferenced from all associated lines.
.1.3.6.1.2.1.10.229.1.1.3,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRxBandTable,,not-accessible,,current,,This table contains receive band descriptor configuration information for a VDSL line. Each entry in this table reflects the configuration for one of possibly many bands with a multiple carrier modulation (MCM) VDSL line. These entries are defined by a manager and can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use MCM, it has no effect on the operation of that line. All read-create-objects defined in this table SHOULD be stored persistently.
.1.3.6.1.2.1.10.229.1.1.3.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRxBandEntry,,not-accessible,vdslLineConfProfileName:vdslLineMCMConfProfileRxBandNumber,current,,Each entry consists of a transmit band descriptor, which is defined by a start and a stop tone index.
.1.3.6.1.2.1.10.229.1.1.3.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRxBandNumber,Unsigned32,not-accessible,,current,,The index for this band descriptor entry.
.1.3.6.1.2.1.10.229.1.1.3.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRxBandStart,Unsigned32,read-create,,current,,Start tone index for this band.
.1.3.6.1.2.1.10.229.1.1.3.1.3,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRxBandStop,Unsigned32,read-create,,current,,Stop tone index for this band.
.1.3.6.1.2.1.10.229.1.1.3.1.4,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileRxBandRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by setting this object to `active'. When `active' is set, the system will validate the profile. Each entry must be internally consistent, the Stop Tone must be greater than the Start Tone. Each entry must also be externally consistent, all entries indexed by a specific profile must not overlap. Validation of the profile will check both internal and external consistency. None of the columns in this row may be modified while the row is in the 'active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must be first unreferenced from all associated lines.
.1.3.6.1.2.1.10.229.1.1.4,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxPSDTable,,not-accessible,,current,,This table contains transmit PSD mask descriptor configuration information for a VDSL line. Each entry in this table reflects the configuration for one tone within a multiple carrier modulation (MCM) VDSL line. These entries are defined by a manager and can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use MCM, it has no effect on the operation of that line. All read-create-objects defined in this table SHOULD be stored persistently.
.1.3.6.1.2.1.10.229.1.1.4.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxPSDEntry,,not-accessible,vdslLineConfProfileName:vdslLineMCMConfProfileTxPSDNumber,current,,Each entry consists of a transmit PSD mask descriptor, which defines the power spectral density (PSD) for a tone.
.1.3.6.1.2.1.10.229.1.1.4.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxPSDNumber,Unsigned32,not-accessible,,current,,The index for this mask descriptor entry.
.1.3.6.1.2.1.10.229.1.1.4.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxPSDTone,Unsigned32,read-create,,current,,The tone index for which the PSD is being specified.
.1.3.6.1.2.1.10.229.1.1.4.1.3,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxPSDPSD,Unsigned32,read-create,,current,,Power Spectral Density level in steps of 0.5dBm/Hz with an offset of -140dBm/Hz.
.1.3.6.1.2.1.10.229.1.1.4.1.4,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileTxPSDRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by setting this object to `active'. When `active' is set, the system will validate the profile. None of the columns in this row may be modified while the row is in the 'active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must be first unreferenced from all associated lines.
.1.3.6.1.2.1.10.229.1.1.5,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxTxPSDTable,,not-accessible,,current,,This table contains transmit maximum PSD mask descriptor configuration information for a VDSL line. Each entry in this table reflects the configuration for one tone within a multiple carrier modulation (MCM) VDSL modem. These entries are defined by a manager and can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use MCM, it has no effect on the operation of that line. All read-create-objects defined in this table SHOULD be stored persistently.
.1.3.6.1.2.1.10.229.1.1.5.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxTxPSDEntry,,not-accessible,vdslLineConfProfileName:vdslLineMCMConfProfileMaxTxPSDNumber,current,,Each entry consists of a transmit PSD mask descriptor, which defines the maximum power spectral density (PSD) for a tone.
.1.3.6.1.2.1.10.229.1.1.5.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxTxPSDNumber,Unsigned32,not-accessible,,current,,The index for this band descriptor entry.
.1.3.6.1.2.1.10.229.1.1.5.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxTxPSDTone,Unsigned32,read-create,,current,,The tone index for which the PSD is being specified. There must not be multiple rows defined, for a particular profile, with the same value for this field.
.1.3.6.1.2.1.10.229.1.1.5.1.3,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxTxPSDPSD,Unsigned32,read-create,,current,,Power Spectral Density level in steps of 0.5dBm/Hz with an offset of -140dBm/Hz.
.1.3.6.1.2.1.10.229.1.1.5.1.4,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxTxPSDRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by setting this object to `active'. When `active' is set, the system will validate the profile. There must be only one entry in this table for each tone associated with a specific profile. This will be checked during the validation process. None of the columns in this row may be modified while the row is in the 'active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must be first unreferenced from all associated lines.
.1.3.6.1.2.1.10.229.1.1.6,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxRxPSDTable,,not-accessible,,current,,This table contains maximum receive PSD mask descriptor configuration information for a VDSL line. Each entry in this table reflects the configuration for one tone within a multiple carrier modulation (MCM) VDSL modem. These entries are defined by a manager and can be used to configure the VDSL line. If an entry in this table is referenced by a line which does not use MCM, it has no effect on the operation of that line. All read-create-objects defined in this table SHOULD be stored persistently.
.1.3.6.1.2.1.10.229.1.1.6.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxRxPSDEntry,,not-accessible,vdslLineConfProfileName:vdslLineMCMConfProfileMaxRxPSDNumber,current,,Each entry consists of a transmit PSD mask descriptor, which defines the power spectral density (PSD) for a tone.
.1.3.6.1.2.1.10.229.1.1.6.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxRxPSDNumber,Unsigned32,not-accessible,,current,,The index for this band descriptor entry.
.1.3.6.1.2.1.10.229.1.1.6.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxRxPSDTone,Unsigned32,read-create,,current,,The tone index for which the PSD is being specified. There must not be multiple rows defined, for a particular profile, with the same value for this field.
.1.3.6.1.2.1.10.229.1.1.6.1.3,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxRxPSDPSD,Unsigned32,read-create,,current,,Power Spectral Density level in steps of 0.5dBm/Hz with an offset of -140dBm/Hz.
.1.3.6.1.2.1.10.229.1.1.6.1.4,VDSL-LINE-EXT-MCM-MIB::vdslLineMCMConfProfileMaxRxPSDRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table. A profile is activated by setting this object to `active'. When `active' is set, the system will validate the profile. There must be only one entry in this table for each tone associated with a specific profile. This will be checked during the validation process. None of the columns in this row may be modified while the row is in the 'active' state. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `notInService') it must be first unreferenced from all associated lines.
.1.3.6.1.2.1.10.229.1.2,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMConformance,,,,,,
.1.3.6.1.2.1.10.229.1.2.1,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMGroups,,,,,,
.1.3.6.1.2.1.10.229.1.2.1.1,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMGroup,,,,,,A collection of objects providing configuration information for a VDSL line based upon multiple carrier modulation modem.
.1.3.6.1.2.1.10.229.1.2.2,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMCompliances,,,,,,
.1.3.6.1.2.1.10.229.1.2.2.1,VDSL-LINE-EXT-MCM-MIB::vdslLineExtMCMMibCompliance,,,,,,The compliance statement for SNMP entities which manage VDSL interfaces.
.1.3.6.1.2.1.10.230,IFCP-MGMT-MIB::ifcpMgmtMIB,,,,,,This module defines management information specific to Internet Fibre Channel Protocol (iFCP) gateway management. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.10.230.1,IFCP-MGMT-MIB::ifcpGatewayObjects,,,,,,
.1.3.6.1.2.1.10.230.1.1,IFCP-MGMT-MIB::ifcpLclGatewayInfo,,,,,,
.1.3.6.1.2.1.10.230.1.1.1,IFCP-MGMT-MIB::ifcpLclGtwyInstTable,,not-accessible,,current,,Information about all local iFCP gateway instances that can
.1.3.6.1.2.1.10.230.1.1.1.1,IFCP-MGMT-MIB::ifcpLclGtwyInstEntry,,not-accessible,ifcpLclGtwyInstIndex,current,,An entry in the local iFCP gateway instance table.
.1.3.6.1.2.1.10.230.1.1.1.1.1,IFCP-MGMT-MIB::ifcpLclGtwyInstIndex,Unsigned32,not-accessible,,current,,An arbitrary integer value to uniquely identify this iFCP
.1.3.6.1.2.1.10.230.1.1.1.1.2,IFCP-MGMT-MIB::ifcpLclGtwyInstPhyIndex,Integer32,read-only,,current,,An index indicating the location of this local gateway within
.1.3.6.1.2.1.10.230.1.1.1.1.3,IFCP-MGMT-MIB::ifcpLclGtwyInstVersionMin,Unsigned32,read-only,,current,,The minimum iFCP protocol version supported by the local iFCP
.1.3.6.1.2.1.10.230.1.1.1.1.4,IFCP-MGMT-MIB::ifcpLclGtwyInstVersionMax,Unsigned32,read-only,,current,,The maximum iFCP protocol version supported by the local iFCP
.1.3.6.1.2.1.10.230.1.1.1.1.5,IFCP-MGMT-MIB::ifcpLclGtwyInstAddrTransMode,INTEGER,read-write,,current,addressTransparent(1):addressTranslation(2),The local iFCP gateway operating mode. Changing this value
.1.3.6.1.2.1.10.230.1.1.1.1.6,IFCP-MGMT-MIB::ifcpLclGtwyInstFcBrdcstSupport,INTEGER,read-write,,current,true(1):false(2),This value indicates whether the local iFCP gateway supports
.1.3.6.1.2.1.10.230.1.1.1.1.7,IFCP-MGMT-MIB::ifcpLclGtwyInstDefaultIpTOV,Unsigned32,read-write,,current,,The default IP_TOV used for iFCP sessions at this gateway.
.1.3.6.1.2.1.10.230.1.1.1.1.8,IFCP-MGMT-MIB::ifcpLclGtwyInstDefaultLTInterval,Unsigned32,read-write,,current,,The default Liveness Test Interval (LTI), in seconds, used
.1.3.6.1.2.1.10.230.1.1.1.1.9,IFCP-MGMT-MIB::ifcpLclGtwyInstDescr,OCTET,read-write,,current,,A user-entered description for this iFCP gateway.
.1.3.6.1.2.1.10.230.1.1.1.1.10,IFCP-MGMT-MIB::ifcpLclGtwyInstNumActiveSessions,Gauge32,read-only,,current,,The current total number of iFCP sessions in the open or
.1.3.6.1.2.1.10.230.1.1.1.1.11,IFCP-MGMT-MIB::ifcpLclGtwyInstStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Parameter values defined
.1.3.6.1.2.1.10.230.1.2,IFCP-MGMT-MIB::ifcpNportSessionInfo,,,,,,
.1.3.6.1.2.1.10.230.1.2.1,IFCP-MGMT-MIB::ifcpSessionAttributesTable,,not-accessible,,current,,An iFCP session consists of the pair of N_PORTs comprising
.1.3.6.1.2.1.10.230.1.2.1.1,IFCP-MGMT-MIB::ifcpSessionAttributesEntry,,not-accessible,ifcpLclGtwyInstIndex:ifcpSessionIndex,current,,Each entry contains information about one iFCP session consisting
.1.3.6.1.2.1.10.230.1.2.1.1.1,IFCP-MGMT-MIB::ifcpSessionIndex,Integer32,not-accessible,,current,,The iFCP session index is a unique value used as an index
.1.3.6.1.2.1.10.230.1.2.1.1.2,IFCP-MGMT-MIB::ifcpSessionLclPrtlIfIndex,Integer32,read-only,,current,,This is the interface index in the IF-MIB ifTable being used
.1.3.6.1.2.1.10.230.1.2.1.1.3,IFCP-MGMT-MIB::ifcpSessionLclPrtlAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address in ifcpSessionLclIfAddr.
.1.3.6.1.2.1.10.230.1.2.1.1.4,IFCP-MGMT-MIB::ifcpSessionLclPrtlAddr,OCTET,read-only,,current,,This is the external IP address of the interface being used
.1.3.6.1.2.1.10.230.1.2.1.1.5,IFCP-MGMT-MIB::ifcpSessionLclPrtlTcpPort,Unsigned32,read-only,,current,,This is the TCP port number that is being used for the iFCP
.1.3.6.1.2.1.10.230.1.2.1.1.6,IFCP-MGMT-MIB::ifcpSessionLclNpWwun,OCTET,read-only,,current,,World Wide Unique Name of the local N Port. For an unbound
.1.3.6.1.2.1.10.230.1.2.1.1.7,IFCP-MGMT-MIB::ifcpSessionLclNpFcid,OCTET,read-only,,current,,Fibre Channel Identifier of the local N Port. For an unbound
.1.3.6.1.2.1.10.230.1.2.1.1.8,IFCP-MGMT-MIB::ifcpSessionRmtNpWwun,OCTET,read-only,,current,,World Wide Unique Name of the remote N Port. For an unbound
.1.3.6.1.2.1.10.230.1.2.1.1.9,IFCP-MGMT-MIB::ifcpSessionRmtPrtlIfAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address in ifcpSessionRmtPrtlIfAddr.
.1.3.6.1.2.1.10.230.1.2.1.1.10,IFCP-MGMT-MIB::ifcpSessionRmtPrtlIfAddr,OCTET,read-only,,current,,This is the remote gateway IP address being used for the
.1.3.6.1.2.1.10.230.1.2.1.1.11,IFCP-MGMT-MIB::ifcpSessionRmtPrtlTcpPort,Unsigned32,read-only,,current,,This is the TCP port number being used for the portal on the
.1.3.6.1.2.1.10.230.1.2.1.1.12,IFCP-MGMT-MIB::ifcpSessionRmtNpFcid,OCTET,read-only,,current,,Fibre Channel Identifier of the remote N Port. For an
.1.3.6.1.2.1.10.230.1.2.1.1.13,IFCP-MGMT-MIB::ifcpSessionRmtNpFcidAlias,OCTET,read-only,,current,,Fibre Channel Identifier Alias assigned by the local gateway
.1.3.6.1.2.1.10.230.1.2.1.1.14,IFCP-MGMT-MIB::ifcpSessionIpTOV,Unsigned32,read-write,,current,,The IP_TOV being used for this iFCP session. This is the
.1.3.6.1.2.1.10.230.1.2.1.1.15,IFCP-MGMT-MIB::ifcpSessionLclLTIntvl,Unsigned32,read-only,,current,,The Liveness Test Interval (LTI) used for this iFCP session.
.1.3.6.1.2.1.10.230.1.2.1.1.16,IFCP-MGMT-MIB::ifcpSessionRmtLTIntvl,Unsigned32,read-only,,current,,The Liveness Test Interval (LTI) as requested by the remote
.1.3.6.1.2.1.10.230.1.2.1.1.17,IFCP-MGMT-MIB::ifcpSessionBound,INTEGER,read-only,,current,true(1):false(2),This value indicates whether this session is bound to a
.1.3.6.1.2.1.10.230.1.2.1.1.18,IFCP-MGMT-MIB::ifcpSessionStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Parameter values defined
.1.3.6.1.2.1.10.230.1.2.2,IFCP-MGMT-MIB::ifcpSessionStatsTable,,not-accessible,,current,,This table provides statistics on an iFCP session.
.1.3.6.1.2.1.10.230.1.2.2.1,IFCP-MGMT-MIB::ifcpSessionStatsEntry,,not-accessible,,current,,Provides iFCP-specific statistics per session.
.1.3.6.1.2.1.10.230.1.2.2.1.1,IFCP-MGMT-MIB::ifcpSessionState,INTEGER,read-only,,current,down(1):openPending(2):open(3),The current session operating state.
.1.3.6.1.2.1.10.230.1.2.2.1.2,IFCP-MGMT-MIB::ifcpSessionDuration,Unsigned32,read-only,,current,,This indicates, in seconds, how long the iFCP session has
.1.3.6.1.2.1.10.230.1.2.2.1.3,IFCP-MGMT-MIB::ifcpSessionTxOctets,Counter64,read-only,,current,,The total number of octets transmitted by the iFCP gateway
.1.3.6.1.2.1.10.230.1.2.2.1.4,IFCP-MGMT-MIB::ifcpSessionRxOctets,Counter64,read-only,,current,,The total number of octets received by the iFCP gateway for
.1.3.6.1.2.1.10.230.1.2.2.1.5,IFCP-MGMT-MIB::ifcpSessionTxFrames,Counter64,read-only,,current,,The total number of iFCP frames transmitted by the gateway
.1.3.6.1.2.1.10.230.1.2.2.1.6,IFCP-MGMT-MIB::ifcpSessionRxFrames,Counter64,read-only,,current,,The total number of iFCP frames received by the gateway
.1.3.6.1.2.1.10.230.1.2.2.1.7,IFCP-MGMT-MIB::ifcpSessionStaleFrames,Counter64,read-only,,current,,The total number of received iFCP frames that were stale and
.1.3.6.1.2.1.10.230.1.2.2.1.8,IFCP-MGMT-MIB::ifcpSessionHeaderCRCErrors,Counter64,read-only,,current,,The total number of Cyclic Redundancy Check (CRC) errors that
.1.3.6.1.2.1.10.230.1.2.2.1.9,IFCP-MGMT-MIB::ifcpSessionFcPayloadCRCErrors,Counter64,read-only,,current,,The total number of CRC errors that occurred in the Fibre
.1.3.6.1.2.1.10.230.1.2.2.1.10,IFCP-MGMT-MIB::ifcpSessionOtherErrors,Counter64,read-only,,current,,The total number of errors, other than errors explicitly
.1.3.6.1.2.1.10.230.1.2.2.1.11,IFCP-MGMT-MIB::ifcpSessionDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which
.1.3.6.1.2.1.10.230.1.2.3,IFCP-MGMT-MIB::ifcpSessionLcStatsTable,,not-accessible,,current,,This table provides low-capacity statistics for an iFCP
.1.3.6.1.2.1.10.230.1.2.3.1,IFCP-MGMT-MIB::ifcpSessionLcStatsEntry,,not-accessible,,current,,Provides iFCP-specific statistics per session.
.1.3.6.1.2.1.10.230.1.2.3.1.1,IFCP-MGMT-MIB::ifcpSessionLcTxOctets,Gauge32,read-only,,current,,The total number of octets transmitted by the iFCP gateway
.1.3.6.1.2.1.10.230.1.2.3.1.2,IFCP-MGMT-MIB::ifcpSessionLcRxOctets,Gauge32,read-only,,current,,The total number of octets received by the iFCP gateway for
.1.3.6.1.2.1.10.230.1.2.3.1.3,IFCP-MGMT-MIB::ifcpSessionLcTxFrames,Gauge32,read-only,,current,,The total number of iFCP frames transmitted by the gateway
.1.3.6.1.2.1.10.230.1.2.3.1.4,IFCP-MGMT-MIB::ifcpSessionLcRxFrames,Gauge32,read-only,,current,,The total number of iFCP frames received by the gateway
.1.3.6.1.2.1.10.230.1.2.3.1.5,IFCP-MGMT-MIB::ifcpSessionLcStaleFrames,Gauge32,read-only,,current,,The total number of received iFCP frames that were stale and
.1.3.6.1.2.1.10.230.1.2.3.1.6,IFCP-MGMT-MIB::ifcpSessionLcHeaderCRCErrors,Gauge32,read-only,,current,,The total number of CRC errors that occurred in the frame
.1.3.6.1.2.1.10.230.1.2.3.1.7,IFCP-MGMT-MIB::ifcpSessionLcFcPayloadCRCErrors,Gauge32,read-only,,current,,The total number of CRC errors that occurred in the Fibre
.1.3.6.1.2.1.10.230.1.2.3.1.8,IFCP-MGMT-MIB::ifcpSessionLcOtherErrors,Gauge32,read-only,,current,,The total number of errors, other than errors explicitly
.1.3.6.1.2.1.10.230.2,IFCP-MGMT-MIB::ifcpGatewayConformance,,,,,,
.1.3.6.1.2.1.10.230.2.1,IFCP-MGMT-MIB::ifcpCompliances,,,,,,
.1.3.6.1.2.1.10.230.2.1.1,IFCP-MGMT-MIB::the,,,,,,This MODULE-COMPLIANCE has been deprecated because address
.1.3.6.1.2.1.10.230.2.1.2,IFCP-MGMT-MIB::ifcpGatewayComplianceNoTranslation,,,,,,Implementation requirements for iFCP MIB module compliance.
.1.3.6.1.2.1.10.230.2.2,IFCP-MGMT-MIB::ifcpGroups,,,,,,
.1.3.6.1.2.1.10.230.2.2.1,IFCP-MGMT-MIB::ifcpLclGatewayGroup,,,,,,iFCP local device info group. This group provides
.1.3.6.1.2.1.10.230.2.2.4,IFCP-MGMT-MIB::active,,,,,,This OBJECT-GROUP has been deprecated because address translation
.1.3.6.1.2.1.10.230.2.2.5,IFCP-MGMT-MIB::ifcpLclGatewaySessionStatsGroup,,,,,,iFCP Session Statistics group. This group provides
.1.3.6.1.2.1.10.230.2.2.6,IFCP-MGMT-MIB::ifcpLclGatewaySessionLcStatsGroup,,,,,,iFCP Session Low-Capacity Statistics group. This group
.1.3.6.1.2.1.10.230.2.2.7,IFCP-MGMT-MIB::ifcpLclGatewaySessionGroupNoTranslation,,,,,,iFCP Session group. This group provides information
.1.3.6.1.2.1.10.238,ADSL2-LINE-MIB::adsl2MIB,,,,,, This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community for the purpose of managing ADSL, ADSL2, and ADSL2+ lines. The MIB module described in RFC 2662 [RFC2662] describes objects used for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per [T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are based upon the specifications for the ADSL Embedded Operations Channel (EOC) as defined in American National Standards Institute (ANSI) T1E1.413/1995 [T1E1.413] and International Telecommunication Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2]. This document does not obsolete RFC 2662 [RFC2662], but rather provides a more comprehensive management model that includes the ADSL2 and ADSL2+ technologies per G.992.3, G.992.4, and G.992.5 ([G.992.3], [G.992.4], and [G.992.5], respectively). In addition, objects have been added to improve the management of ADSL, ADSL2, and ADSL2+ lines. Additionally, the management framework for New Generation ADSL lines specified by the Digital Subscriber Line Forum (DSLF) has been taken into consideration [TR-90]. That framework is based on ITU-T G.997.1 standard [G.997.1] as well as two amendments: [G.997.1am1] and [G.997.1am2]. Note that the revised ITU-T G.997.1 standard also refers to the next generation of VDSL technology, known as VDSL2, per ITU-T G.993.2 [G.993.2]. However, managing VDSL2 lines is currently beyond the scope of this document. The MIB module is located in the MIB tree under MIB 2 transmission, as discussed in the IANA Considerations section of this document. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4706: see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.238.1,ADSL2-LINE-MIB::adsl2,,,,,,
.1.3.6.1.2.1.10.238.1.0,ADSL2-LINE-MIB::adsl2Notifications,,,,,,
.1.3.6.1.2.1.10.238.1.0.1,ADSL2-LINE-MIB::adsl2LinePerfFECSThreshAtuc,,,,,,This notification indicates that the FEC seconds threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.2,ADSL2-LINE-MIB::adsl2LinePerfFECSThreshAtur,,,,,,This notification indicates that the FEC seconds threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.3,ADSL2-LINE-MIB::adsl2LinePerfESThreshAtuc,,,,,,This notification indicates that the errored seconds threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.4,ADSL2-LINE-MIB::adsl2LinePerfESThreshAtur,,,,,,This notification indicates that the errored seconds threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.5,ADSL2-LINE-MIB::adsl2LinePerfSESThreshAtuc,,,,,,This notification indicates that the severely-errored seconds threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.6,ADSL2-LINE-MIB::adsl2LinePerfSESThreshAtur,,,,,,This notification indicates that the severely-errored seconds threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.7,ADSL2-LINE-MIB::adsl2LinePerfLOSSThreshAtuc,,,,,,This notification indicates that the LOS seconds threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.8,ADSL2-LINE-MIB::adsl2LinePerfLOSSThreshAtur,,,,,,This notification indicates that the LOS seconds threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.9,ADSL2-LINE-MIB::adsl2LinePerfUASThreshAtuc,,,,,,This notification indicates that the unavailable seconds threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.10,ADSL2-LINE-MIB::adsl2LinePerfUASThreshAtur,,,,,,This notification indicates that the unavailable seconds threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.11,ADSL2-LINE-MIB::adsl2LinePerfCodingViolationsThreshAtuc,,,,,,This notification indicates that the coding violations threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.12,ADSL2-LINE-MIB::adsl2LinePerfCodingViolationsThreshAtur,,,,,,This notification indicates that the coding violations threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.13,ADSL2-LINE-MIB::adsl2LinePerfCorrectedThreshAtuc,,,,,,This notification indicates that the corrected blocks (FEC events) threshold has been reached/exceeded for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.14,ADSL2-LINE-MIB::adsl2LinePerfCorrectedThreshAtur,,,,,,This notification indicates that the corrected blocks (FEC events) threshold has been reached/exceeded for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.0.15,ADSL2-LINE-MIB::adsl2LinePerfFailedFullInitThresh,,,,,,This notification indicates that the failed full initializations threshold has been reached/exceeded for the referred ADSL/ADSL2 or ADSL2+ line.
.1.3.6.1.2.1.10.238.1.0.16,ADSL2-LINE-MIB::adsl2LinePerfFailedShortInitThresh,,,,,,This notification indicates that the failed short initializations threshold has been reached/exceeded for the referred ADSL/ADSL2 or ADSL2+ line.
.1.3.6.1.2.1.10.238.1.0.17,ADSL2-LINE-MIB::adsl2LineStatusChangeAtuc,,,,,,This notification indicates that a status change is detected for the referred ATU-C.
.1.3.6.1.2.1.10.238.1.0.18,ADSL2-LINE-MIB::adsl2LineStatusChangeAtur,,,,,,This notification indicates that a status change is detected for the referred ATU-R.
.1.3.6.1.2.1.10.238.1.1,ADSL2-LINE-MIB::adsl2Line,,,,,,
.1.3.6.1.2.1.10.238.1.1.1,ADSL2-LINE-MIB::adsl2LineTable,,not-accessible,,current,,The table adsl2LineTable contains configuration, command, and status parameters of the ADSL2 line. The index of this table is an interface index where the interface has an ifType of adsl2plus(238). Several objects in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.1.1.1,ADSL2-LINE-MIB::adsl2LineEntry,,not-accessible,ifIndex,current,,The table adsl2LineTable contains configuration, commands, and status parameters of the ADSL2 line
.1.3.6.1.2.1.10.238.1.1.1.1.1,ADSL2-LINE-MIB::adsl2LineCnfgTemplate,OCTET,read-write,,current,,The value of this object identifies the row in the ADSL2 Line Configuration Templates Table, (adsl2LineConfTemplateTable), which applies for this ADSL2 line. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.1.1.1.2,ADSL2-LINE-MIB::adsl2LineAlarmCnfgTemplate,OCTET,read-write,,current,,The value of this object identifies the row in the ADSL2 Line Alarm Configuration Template Table, (adsl2LineAlarmConfTemplateTable), which applies to this ADSL2 line. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.1.1.1.3,ADSL2-LINE-MIB::adsl2LineCmndConfPmsf,INTEGER,read-write,,current,l3toL0(0):l0toL2(2):l0orL2toL3(3),Power management state forced. Defines the line states to be forced by the near-end ATU on this line. The various possible values are: l3toL0(0), l0toL2(2), or l0orL2toL3(3). This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.1.1.1.4,ADSL2-LINE-MIB::adsl2LineCmndConfLdsf,INTEGER,read-write,,current,inhibit(0):force(1),Loop diagnostics mode forced (LDSF). Defines whether the line should be forced into the loop diagnostics mode by the near-end ATU on this line or only be responsive to loop diagnostics initiated by the far-end ATU. This object MUST be maintained in a persistent manner. However, in case the operator forces loop diagnostics mode then the access node should reset the object (inhibit) when loop diagnostics mode procedures are completed.
.1.3.6.1.2.1.10.238.1.1.1.1.5,ADSL2-LINE-MIB::adsl2LineCmndConfLdsfFailReason,INTEGER,read-only,,current,none(1):success(2):inProgress(3):unsupported(4):cannotRun(5):aborted(6):failed(7):illegalMode(8):adminUp(9):tableFull(10):noResources(11),The status of the recent occasion the Loop diagnostics mode forced (LDSF) was issued for the associated line. Possible values are: none(1) - The default value in case LDSF was never requested for the associated line. success(2) - The recent command completed successfully. inProgress(3) - The Loop Diagnostics process is in progress. unsupported(4) - The NE or the line card doesn't support LDSF. cannotRun(5) - The NE cannot initiate the command, due to a nonspecific reason. aborted(6) - The Loop Diagnostics process aborted. failed(7) - The Loop Diagnostics process failed. illegalMode(8) - The NE cannot initiate the command, due to the specific mode of the relevant line. adminUp(9) - The NE cannot initiate the command, as the relevant line is administratively 'Up'. tableFull(10) - The NE cannot initiate the command, due to reaching the maximum number of rows in the results table. noResources(11) - The NE cannot initiate the command, due to lack of internal memory resources.
.1.3.6.1.2.1.10.238.1.1.1.1.6,ADSL2-LINE-MIB::adsl2LineCmndAutomodeColdStart,INTEGER,read-write,,current,true(1):false(2),Automode cold start forced. This parameter is defined in order to improve testing of the performance of ATUs supporting automode when it is enabled in the MIB. Change the value of this parameter to 'true' indicates a change in loop conditions applied to the devices under test. The ATUs shall reset any historical information used for automode and for shortening G.994.1 handshake and initialization. Automode is the case where multiple operation-modes are enabled through the adsl2LConfProfAtuTransSysEna object in the line configuration profile being used for the ADSL line, and where the selection of the actual operation-mode depends not only on the common capabilities of both ATUs (as exchanged in G.994.1), but also on achievable data rates under given loop conditions. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.1.1.1.7,ADSL2-LINE-MIB::adsl2LineStatusAtuTransSys,BITS,read-only,,current,ansit1413(0):etsi(1):g9921PotsNonOverlapped(2):g9921PotsOverlapped(3):g9921IsdnNonOverlapped(4):g9921isdnOverlapped(5):g9921tcmIsdnNonOverlapped(6):g9921tcmIsdnOverlapped(7):g9922potsNonOverlapped(8):g9922potsOverlapped(9):g9922tcmIsdnNonOverlapped(10):g9922tcmIsdnOverlapped(11):g9921tcmIsdnSymmetric(12):reserved1(13):reserved2(14):reserved3(15):reserved4(16):reserved5(17):g9923PotsNonOverlapped(18):g9923PotsOverlapped(19):g9923IsdnNonOverlapped(20):g9923isdnOverlapped(21):reserved6(22):reserved7(23):g9924potsNonOverlapped(24):g9924potsOverlapped(25):reserved8(26):reserved9(27):g9923AnnexIAllDigNonOverlapped(28):g9923AnnexIAllDigOverlapped(29):g9923AnnexJAllDigNonOverlapped(30):g9923AnnexJAllDigOverlapped(31):g9924AnnexIAllDigNonOverlapped(32):g9924AnnexIAllDigOverlapped(33):g9923AnnexLMode1NonOverlapped(34):g9923AnnexLMode2NonOverlapped(35):g9923AnnexLMode3Overlapped(36):g9923AnnexLMode4Overlapped(37):g9923AnnexMPotsNonOverlapped(38):g9923AnnexMPotsOverlapped(39):g9925PotsNonOverlapped(40):g9925PotsOverlapped(41):g9925IsdnNonOverlapped(42):g9925isdnOverlapped(43):reserved10(44):reserved11(45):g9925AnnexIAllDigNonOverlapped(46):g9925AnnexIAllDigOverlapped(47):g9925AnnexJAllDigNonOverlapped(48):g9925AnnexJAllDigOverlapped(49):g9925AnnexMPotsNonOverlapped(50):g9925AnnexMPotsOverlapped(51):reserved12(52):reserved13(53):reserved14(54):reserved15(55),The ATU Transmission System (ATS) in use. It is coded in a bit-map representation with only a single bit set to '1' (the selected coding for the ADSL line). This parameter may be derived from the handshaking procedures defined in Recommendation G.994.1. A set of ADSL2 line transmission modes, with one bit per mode.
.1.3.6.1.2.1.10.238.1.1.1.1.8,ADSL2-LINE-MIB::adsl2LineStatusPwrMngState,INTEGER,read-only,,current,l0(1):l1(2):l2(3):l3(4),The current power management state. One of four possible power management states: L0 - Synchronized and full transmission (i.e., Showtime). L1 - Low Power with reduced net data rate (G.992.2 only). L2 - Low Power with reduced net data rate (G.992.3 and G.992.4 only). L3 - No power. The various possible values are: l0(1), l1(2), l2(3), or l3(4).
.1.3.6.1.2.1.10.238.1.1.1.1.9,ADSL2-LINE-MIB::adsl2LineStatusInitResult,INTEGER,read-only,,current,noFail(0):configError(1):configNotFeasible(2):commFail(3):noPeerAtu(4):otherCause(5),Indicates the result of the last full initialization performed on the line. It is an enumeration type with the following values: noFail(0), configError(1), configNotFeasible(2), commFail(3), noPeerAtu(4), or otherCause(5).
.1.3.6.1.2.1.10.238.1.1.1.1.10,ADSL2-LINE-MIB::adsl2LineStatusLastStateDs,INTEGER,read-only,,current,atucG9941(0):atucQuiet1(1):atucComb1(2):atucQuiet2(3):atucComb2(4):atucIcomb1(5):atucLineprob(6):atucQuiet3(7):atucComb3(8):atucIComb2(9):atucMsgfmt(10):atucMsgpcb(11):atucQuiet4(12):atucReverb1(13):atucTref1(14):atucReverb2(15):atucEct(16):atucReverb3(17):atucTref2(18):atucReverb4(19):atucSegue1(20):atucMsg1(21):atucReverb5(22):atucSegue2(23):atucMedley(24):atucExchmarker(25):atucMsg2(26):atucReverb6(27):atucSegue3(28):atucParams(29):atucReverb7(30):atucSegue4(31):atucShowtime(32):aturG9941(100):aturQuiet1(101):aturComb1(102):aturQuiet2(103):aturComb2(104):aturIcomb1(105):aturLineprob(106):aturQuiet3(107):aturComb3(108):aturIcomb2(109):aturMsgfmt(110):aturMsgpcb(111):aturReverb1(112):aturQuiet4(113):aturReverb2(114):aturQuiet5(115):aturReverb3(116):aturEct(117):aturReverb4(118):aturSegue1(119):aturReverb5(120):aturSegue2(121):aturMsg1(122):aturMedley(123):aturExchmarker(124):aturMsg2(125):aturReverb6(126):aturSegue3(127):aturParams(128):aturReverb7(129):aturSegue4(130):aturShowtime(131),The last successful transmitted initialization state in the downstream direction in the last full initialization performed on the line.
.1.3.6.1.2.1.10.238.1.1.1.1.11,ADSL2-LINE-MIB::adsl2LineStatusLastStateUs,INTEGER,read-only,,current,atucG9941(0):atucQuiet1(1):atucComb1(2):atucQuiet2(3):atucComb2(4):atucIcomb1(5):atucLineprob(6):atucQuiet3(7):atucComb3(8):atucIComb2(9):atucMsgfmt(10):atucMsgpcb(11):atucQuiet4(12):atucReverb1(13):atucTref1(14):atucReverb2(15):atucEct(16):atucReverb3(17):atucTref2(18):atucReverb4(19):atucSegue1(20):atucMsg1(21):atucReverb5(22):atucSegue2(23):atucMedley(24):atucExchmarker(25):atucMsg2(26):atucReverb6(27):atucSegue3(28):atucParams(29):atucReverb7(30):atucSegue4(31):atucShowtime(32):aturG9941(100):aturQuiet1(101):aturComb1(102):aturQuiet2(103):aturComb2(104):aturIcomb1(105):aturLineprob(106):aturQuiet3(107):aturComb3(108):aturIcomb2(109):aturMsgfmt(110):aturMsgpcb(111):aturReverb1(112):aturQuiet4(113):aturReverb2(114):aturQuiet5(115):aturReverb3(116):aturEct(117):aturReverb4(118):aturSegue1(119):aturReverb5(120):aturSegue2(121):aturMsg1(122):aturMedley(123):aturExchmarker(124):aturMsg2(125):aturReverb6(126):aturSegue3(127):aturParams(128):aturReverb7(129):aturSegue4(130):aturShowtime(131),The last successful transmitted initialization state in the upstream direction in the last full initialization performed on the line.
.1.3.6.1.2.1.10.238.1.1.1.1.12,ADSL2-LINE-MIB::adsl2LineStatusAtur,BITS,read-only,,current,noDefect(0):lossOfFrame(1):lossOfSignal(2):lossOfPower(3):initFailure(4),Indicates current state (existing failures) of the ATU-R. This is a bit-map of possible conditions.
.1.3.6.1.2.1.10.238.1.1.1.1.13,ADSL2-LINE-MIB::adsl2LineStatusAtuc,BITS,read-only,,current,noDefect(0):lossOfFrame(1):lossOfSignal(2):lossOfPower(3):initFailure(4),Indicates current state (existing failures) of the ATU-C. This is a bit-map of possible conditions.
.1.3.6.1.2.1.10.238.1.1.1.1.14,ADSL2-LINE-MIB::adsl2LineStatusLnAttenDs,Unsigned32,read-only,,current,,The measured difference in the total power transmitted by the ATU-C and the total power received by the ATU-R over all sub- carriers during diagnostics mode and initialization. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is currently unavailable.
.1.3.6.1.2.1.10.238.1.1.1.1.15,ADSL2-LINE-MIB::adsl2LineStatusLnAttenUs,Unsigned32,read-only,,current,,The measured difference in the total power transmitted by the ATU-R and the total power received by the ATU-C over all sub- carriers during diagnostics mode and initialization. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is currently unavailable.
.1.3.6.1.2.1.10.238.1.1.1.1.16,ADSL2-LINE-MIB::adsl2LineStatusSigAttenDs,Unsigned32,read-only,,current,,The measured difference in the total power transmitted by the ATU-C and the total power received by the ATU-R over all sub- carriers during Showtime. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the signal attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the signal attenuation measurement is currently unavailable.
.1.3.6.1.2.1.10.238.1.1.1.1.17,ADSL2-LINE-MIB::adsl2LineStatusSigAttenUs,Unsigned32,read-only,,current,,The measured difference in the total power transmitted by the ATU-R and the total power received by the ATU-C over all sub- carriers during Showtime. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the signal attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the signal attenuation measurement is currently unavailable.
.1.3.6.1.2.1.10.238.1.1.1.1.18,ADSL2-LINE-MIB::adsl2LineStatusSnrMarginDs,Integer32,read-only,,current,,Downstream SNR Margin is the maximum increase in dB of the noise power received at the ATU-R, such that the BER requirements are met for all downstream bearer channels. It ranges from -640 to 630 units of 0.1 dB (physical values are -64 to 63 dB). A special value of 0x7FFFFFFF (2147483647) indicates the SNR Margin is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the SNR Margin measurement is currently unavailable.
.1.3.6.1.2.1.10.238.1.1.1.1.19,ADSL2-LINE-MIB::adsl2LineStatusSnrMarginUs,Integer32,read-only,,current,,Upstream SNR Margin is the maximum increase in dB of the noise power received at the ATU-C, such that the BER requirements are met for all downstream bearer channels. It ranges from -640 to 630 units of 0.1 dB (physical values are -64 to 63 dB). A special value of 0x7FFFFFFF (2147483647) indicates the SNR Margin is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the SNR Margin measurement is currently unavailable.
.1.3.6.1.2.1.10.238.1.1.1.1.20,ADSL2-LINE-MIB::adsl2LineStatusAttainableRateDs,Unsigned32,read-only,,current,,Maximum Attainable Data Rate Downstream. The maximum downstream net data rate currently attainable by the ATU-C transmitter and the ATU-R receiver, coded in bits/second.
.1.3.6.1.2.1.10.238.1.1.1.1.21,ADSL2-LINE-MIB::adsl2LineStatusAttainableRateUs,Unsigned32,read-only,,current,,Maximum Attainable Data Rate Upstream. The maximum upstream net data rate currently attainable by the ATU-R transmitter and the ATU-C receiver, coded in bits/second.
.1.3.6.1.2.1.10.238.1.1.1.1.22,ADSL2-LINE-MIB::adsl2LineStatusActPsdDs,Integer32,read-only,,current,,Actual Power Spectrum Density (PSD) Downstream. The average downstream transmit PSD over the sub-carriers used for downstream. It ranges from -900 to 0 units of 0.1 dB (physical values are -90 to 0 dBm/Hz). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.238.1.1.1.1.23,ADSL2-LINE-MIB::adsl2LineStatusActPsdUs,Integer32,read-only,,current,,Actual Power Spectrum Density (PSD) Upstream. The average upstream transmit PSD over the sub-carriers used for upstream. It ranges from -900 to 0 units of 0.1 dB (physical values are -90 to 0 dBm/Hz). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.238.1.1.1.1.24,ADSL2-LINE-MIB::adsl2LineStatusActAtpDs,Integer32,read-only,,current,,Actual Aggregate Transmit Power Downstream. The total amount of transmit power delivered by the ATU-C at the U-C reference point, at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (physical values are -31 to 31 dBm). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.238.1.1.1.1.25,ADSL2-LINE-MIB::adsl2LineStatusActAtpUs,Integer32,read-only,,current,,Actual Aggregate Transmit Power Upstream. The total amount of transmit power delivered by the ATU-R at the U-R reference point, at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (physical values are -31 to 31 dBm). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.238.1.2,ADSL2-LINE-MIB::adsl2Status,,,,,,
.1.3.6.1.2.1.10.238.1.2.1,ADSL2-LINE-MIB::adsl2ChannelStatusTable,,not-accessible,,current,,The table adsl2ChannelStatusTable contains status parameters of the ADSL2 channel. This table contains live data from equipment.
.1.3.6.1.2.1.10.238.1.2.1.1,ADSL2-LINE-MIB::adsl2ChannelStatusEntry,,not-accessible,ifIndex:adsl2ChStatusUnit,current,,The table adsl2ChannelStatusTable contains status parameters of the ADSL2 channel. The index of this table consists of an interface index, where the interface has an ifType value that is applicable for a DSL channel, along with a termination unit.
.1.3.6.1.2.1.10.238.1.2.1.1.1,ADSL2-LINE-MIB::adsl2ChStatusUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit atuc(1) or atur(2).
.1.3.6.1.2.1.10.238.1.2.1.1.2,ADSL2-LINE-MIB::adsl2ChStatusChannelNum,Unsigned32,read-only,,current,,Provides the bearer channel number associated with this row (i.e., the channel ifIndex). This enables determining the channel configuration profile and the channel thresholds profile applicable for this bearer channel.
.1.3.6.1.2.1.10.238.1.2.1.1.3,ADSL2-LINE-MIB::adsl2ChStatusActDataRate,Unsigned32,read-only,,current,,The actual net data rate that the bearer channel is operating at, if in L0 power management state. In L1 or L2 states, it relates to the previous L0 state. The data rate is coded in bits/second.
.1.3.6.1.2.1.10.238.1.2.1.1.4,ADSL2-LINE-MIB::adsl2ChStatusPrevDataRate,Unsigned32,read-only,,current,,The previous net data rate that the bearer channel was operating at just before the latest rate change event. This could be a full or short initialization, fast retrain, DRA or power management transitions, excluding transitions between L0 state and L1 or L2 states. The data rate is coded in bits/second.
.1.3.6.1.2.1.10.238.1.2.1.1.5,ADSL2-LINE-MIB::adsl2ChStatusActDelay,Unsigned32,read-only,,current,,The actual one-way interleaving delay introduced by the PMS-TC in the direction of the bearer channel, if in L0 power management state. In L1 or L2 states, it relates to the previous L0 state. It is coded in ms (rounded to the nearest ms).
.1.3.6.1.2.1.10.238.1.2.1.1.6,ADSL2-LINE-MIB::adsl2ChStatusAtmStatus,BITS,read-only,,current,noDefect(0):noCellDelineation(1):lossOfCellDelineation(2),Indicates the current state (existing failures) of the ADSL channel in case its Data Path is ATM. This is a bit-map of possible conditions. The various bit positions are: noDefect(0), noCellDelineation(1), or lossOfCellDelineation(2). In the case where the channel is not an ATM Data Path, the object is set to '0'.
.1.3.6.1.2.1.10.238.1.2.1.1.7,ADSL2-LINE-MIB::adsl2ChStatusPtmStatus,BITS,read-only,,current,noDefect(0):outOfSync(1),Indicates the current state (existing failures) of the ADSL channel in case its Data Path is PTM. This is a bit-map of possible conditions. The various bit positions are: noDefect(0), or outOfSync(1). In the case where the channel is not a PTM Data Path, the object is set to '0'.
.1.3.6.1.2.1.10.238.1.2.2,ADSL2-LINE-MIB::adsl2SCStatusTable,,not-accessible,,current,,The table adsl2SCStatusTable contains status parameters of the ADSL2 sub-carriers. The following points apply to this table: 1. The main purpose of this table is to hold the results of a DELT. 2. This table also holds parameters obtained at line initialization time. 3. The rows in this table are volatile; that is, they are lost if the SNMP agent is rebooted. 4. Due to the large OCTET STRING attributes in this table, the worst case memory requirements for this table are very high. The manager may use the row status attribute of this table to delete rows in order to reclaim memory. 5. The manager may create rows in this table. The SNMP agent may create rows in this table. Only the manager may delete rows in this table. 6. The maximum number of rows allowable in this table is indicated by the scalar attribute adsl2ScalarSCMaxInterfaces. The number of rows available in this table is indicated by the scalar attribute adsl2ScalarSCAvailInterfaces. 7. The SNMP agent is permitted to create rows in this table when a DELT completes successfully or when line initialization occurs. It is not mandatory for the SNMP agent to create rows in this table; hence, it may be necessary for the manager to create rows in this table before any results can be stored. 8. If the manager attempts to create a row in this table and there are no more rows available, the creation attempt will fail, and the response to the SNMP SET PDU will contain the error noCreation(11). 9. If the SNMP agent attempts to create a row in this table and there are no more rows available, the creation attempt will fail, and the attribute adsl2LineCmndConfLdsfFailReason will indicate the reason for the failure. The failure reason will be either tableFull(10) or noResources(11). 10. An example of use of this table is as follows: Step 1. : The DELT is started by setting the : adsl2LineCmndConfLdsf from inhibit to force. Step 2. : The DELT completes, and valid data is : available. Step 3. : The row in the adsl2SCStatusTable where the : results will be stored does not yet exist so : the SNMP agent attempts to create the row. Step 4. : Due to a low memory condition, a row in the : adsl2SCStatusTable table cannot be created at : this time. Step 5. : The reason for the failure, tableFull(10), is : indicated in the adsl2LineCmndConfLdsfFailReason : attribute. 11. Another example of use of this table is as follows : Step 1. : The DELT is started by setting the : adsl2LineCmndConfLdsf from inhibit to force. Step 2. : The DELT completes and valid data is : available. Step 3. : The row in the adsl2SCStatusTable where the : results will be stored does not yet exist so : the SNMP agent attempts to create the row. Step 4. : The row creation is successful. Step 5. : The value of the attribute : adsl2LineCmndConfLdsfFailReasonreason is set : to success(2). 12. Another example of use of this table is as follows: Step 1. : The manager creates a row in adsl2SCStatusTable : for a particular ADSL2 line. Step 2. : The DELT is started on the above-mentioned : line by setting the adsl2LineCmndConfLdsf from : inhibit to force. Step 3. : The DELT completes, and valid data is : available. Step 4. : The value of the attribute 
.1.3.6.1.2.1.10.238.1.2.2.1,ADSL2-LINE-MIB::adsl2SCStatusEntry,,not-accessible,ifIndex:adsl2SCStatusDirection,current,,The table Adsl2SCStatusEntry contains status parameters of the ADSL2 sub-carriers. The index of this table is an interface index where the interface has an ifType of adsl2plus(238).
.1.3.6.1.2.1.10.238.1.2.2.1.1,ADSL2-LINE-MIB::adsl2SCStatusDirection,INTEGER,not-accessible,,current,upstream(1):downstream(2),The direction of the sub-carrier is either upstream or downstream.
.1.3.6.1.2.1.10.238.1.2.2.1.2,ADSL2-LINE-MIB::adsl2SCStatusMtime,Unsigned32,read-only,,current,,SNR Measurement Time. The number of symbols used to measure the SNR values on the respective transmission direction. It should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval for G.992.3). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated otherwise.
.1.3.6.1.2.1.10.238.1.2.2.1.3,ADSL2-LINE-MIB::adsl2SCStatusSnr,OCTET,read-only,,current,,The SNR Margin per sub-carrier, expressing the ratio between the received signal power and received noise power per subscriber. It is an array of 512 octets, designed for supporting up to 512 (downstream) sub-carriers. The number of utilized octets on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Octet i (0 <= i < NSC) is set to a value in the range 0 to 254 to indicate that the respective downstream or upstream sub- carrier i has SNR of: (-32 + Adsl2SubcarrierSnr(i)/2) in dB (i.e., -32 to 95dB). The special value 255 means that no measurement could be done for the subcarrier because it is out of the PSD mask passband or that the noise PSD is out of range to be represented. Each value in this array is 8 bits wide.
.1.3.6.1.2.1.10.238.1.2.2.1.4,ADSL2-LINE-MIB::adsl2SCStatusBitsAlloc,OCTET,read-only,,current,,The bits allocation per sub-carrier. An array of 256 octets (512 nibbles), designed for supporting up to 512 (downstream) sub-carriers. The number of utilized nibbles on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Nibble i (0 <= i < NSC) is set to a value in the range 0 to 15 to indicate that the respective downstream or upstream sub-carrier i has the same amount of bits allocation.
.1.3.6.1.2.1.10.238.1.2.2.1.5,ADSL2-LINE-MIB::adsl2SCStatusGainAlloc,OCTET,read-only,,current,,The gain allocation per sub-carrier. An array of 512 16-bits values, designed for supporting up to 512 (downstream) sub- carriers. The number of utilized octets on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Value i (0 <= i < NSC) is in the range 0 to 4093 to indicate that the respective downstream or upstream sub-carrier i has the same amount of gain value. The gain value is represented as a multiple of 1/512 on a linear scale. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.238.1.2.2.1.6,ADSL2-LINE-MIB::adsl2SCStatusTssi,OCTET,read-only,,current,,The transmit spectrum shaping (TSSi) breakpoints expressed as the set of breakpoints exchanged during G.994.1. Each breakpoint is a pair of values occupying 3 octets with the following structure: First 2 octets - Index of the subcarrier used in the context of the breakpoint. Third octet - The shaping parameter at the breakpoint. Subcarrier index is an unsigned number in the range 1 to either NSCds (downstream direction) or NSCus (upstream direction). The shaping parameter value is in the range 0 to 127 (units of -0.5dB). The special value 127 indicates that the subcarrier is not transmitted.
.1.3.6.1.2.1.10.238.1.2.2.1.7,ADSL2-LINE-MIB::adsl2SCStatusLinScale,Unsigned32,read-only,,current,,The scale factor to be applied to the H(f) linear representation values for the respective transmission direction. This parameter is only available after a loop diagnostic procedure.
.1.3.6.1.2.1.10.238.1.2.2.1.8,ADSL2-LINE-MIB::adsl2SCStatusLinReal,OCTET,read-only,,current,,An array of up to 512 complex H(f) linear representation values in linear scale for the respective transmission direction. It is designed to support up to 512 (downstream) sub-carriers. The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Each array entry represents the real component [referred to here as a(i)] of Hlin(f = i*Df) value for a particular sub-carrier index i (0 <= i < NSC). Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where scale is Adsl2SubcarrierLinScale and a(i) and b(i) [provided by the Adsl2SubcarrierLinImg object] are in the range (-2^15+1) to (+2^15-1). A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.238.1.2.2.1.9,ADSL2-LINE-MIB::adsl2SCStatusLinImg,OCTET,read-only,,current,,An array of up to 512 complex H(f) linear representation values in linear scale for the respective transmission direction. It is designed to support up to 512 (downstream) sub-carriers. The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Each array entry represents the imaginary component [referred to here as b(i)] of Hlin(f = i*Df) value for a particular sub- carrier index i (0 <= i < NSC). Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where scale is Adsl2SubcarrierLinScale and a(i) [provided by the Adsl2SubcarrierLinReal object] and b(i) are in the range (-2^15+1) to (+2^15-1). A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.238.1.2.2.1.10,ADSL2-LINE-MIB::adsl2SCStatusLogMt,Unsigned32,read-only,,current,,The number of symbols used to measure the H(f) logarithmic measurement values for the respective transmission direction. This parameter should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval for G.992.3). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization
.1.3.6.1.2.1.10.238.1.2.2.1.11,ADSL2-LINE-MIB::adsl2SCStatusLog,OCTET,read-only,,current,,An array of up to 512 real H(f) logarithmic representation values in dB for the respective transmission direction. It is designed to support up to 512 (downstream) sub-carriers. The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Each array entry represents the real Hlog(f = i*Df) value for a particular sub-carrier index i, (0 <= i < NSC). The real Hlog(f) value is represented as (6-m(i)/10), with m(i) in the range 0 to 1022. A special value m=1023 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the attenuation is out of range to be represented. This parameter is applicable in loop diagnostic procedure and initialization. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.238.1.2.2.1.12,ADSL2-LINE-MIB::adsl2SCStatusQlnMt,Unsigned32,read-only,,current,,The number of symbols used to measure the Quiet Line Noise values on the respective transmission direction. This parameter should correspond to the value specified in the recommendation (e.g., the number of symbols in 1 second time interval for G.992.3). This parameter corresponds to 1 second in loop diagnostic procedure and should be updated in initialization 
.1.3.6.1.2.1.10.238.1.2.2.1.13,ADSL2-LINE-MIB::adsl2SCStatusQln,OCTET,read-only,,current,,An array of up to 512 real Quiet Line Noise values in dBm/Hz for the respective transmission direction. It is designed for up to 512 (downstream) sub-carriers. The number of utilized values on downstream direction depends on NSCds, and on upstream direction it depends on NSCus. This value is referred to here as NSC. Each array entry represents the QLN(f = i*Df) value for a particular sub-carrier index i, (0 <= i < NSC). The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the range 0 to 254. A special value n(i)=255 indicates that no measurement could be done for the subcarrier because it is out of the passband or that the noise PSD is out of range to be represented. This parameter is applicable in loop diagnostic procedure and initialization. Each value in this array is 8 bits wide.
.1.3.6.1.2.1.10.238.1.2.2.1.14,ADSL2-LINE-MIB::adsl2SCStatusLnAtten,Unsigned32,read-only,,current,,When referring to the downstream direction, it is the measured difference in the total power transmitted by the ATU-C and the total power received by the ATU-R over all sub-carriers during diagnostics mode. When referring to the upstream direction, it is the measured difference in the total power transmitted by the ATU-R and the total power received by the ATU-C over all sub-carriers during diagnostics mode. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is unavailable. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.238.1.2.2.1.15,ADSL2-LINE-MIB::adsl2SCStatusSigAtten,Unsigned32,read-only,,current,,When referring to the downstream direction, it is the measured difference in the total power transmitted by the ATU-C and the total power received by the ATU-R over all sub- carriers during Showtime after the diagnostics mode. When referring to the upstream direction, it is the measured difference in the total power transmitted by the ATU-R and the total power received by the ATU-C over all sub- carriers during Showtime after the diagnostics mode. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the signal attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the signal attenuation measurement is unavailable. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.238.1.2.2.1.16,ADSL2-LINE-MIB::adsl2SCStatusSnrMargin,Integer32,read-only,,current,,SNR Margin is the maximum increase in dB of the noise power received at the ATU (ATU-R on downstream direction and ATU-C on upstream direction), such that the BER requirements are met for all bearer channels received at the ATU. It ranges from -640 to 630 units of 0.1 dB (physical values are -64 to 63 dB). A special value of 0x7FFFFFFF (2147483647) indicates the SNR Margin is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the SNR Margin measurement is currently unavailable. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.238.1.2.2.1.17,ADSL2-LINE-MIB::adsl2SCStatusAttainableRate,Unsigned32,read-only,,current,,Maximum Attainable Data Rate. The maximum net data rate currently attainable by the ATU-C transmitter and ATU-R receiver (when referring to downstream direction) or by the ATU-R transmitter and ATU-C receiver (when referring to upstream direction). Value is coded in bits/second. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.238.1.2.2.1.18,ADSL2-LINE-MIB::adsl2SCStatusActAtp,Integer32,read-only,,current,,Actual Aggregate Transmit Power from the ATU (ATU-R on downstream direction and ATU-C on upstream direction), at the instant of measurement. It ranges from -310 to 310 units of 0.1 dB (physical values are -31 to 31 dBm). A value of all 1's indicates the measurement is out of range to be represented. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.238.1.2.2.1.19,ADSL2-LINE-MIB::adsl2SCStatusRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Row Status. The manager may create and delete rows of this table. Please see the description of adsl2SCStatusTable above for more details.
.1.3.6.1.2.1.10.238.1.3,ADSL2-LINE-MIB::adsl2Inventory,,,,,,
.1.3.6.1.2.1.10.238.1.3.1,ADSL2-LINE-MIB::adsl2LineInventoryTable,,not-accessible,,current,,The table adsl2LineInventoryTable contains inventory of the ADSL2 units.
.1.3.6.1.2.1.10.238.1.3.1.1,ADSL2-LINE-MIB::adsl2LineInventoryEntry,,not-accessible,ifIndex:adsl2LInvUnit,current,,The table adsl2LineInventoryTable contains inventory of the ADSL2 units. The index of this table is an interface index where the interface has an ifType of adsl2plus(238).
.1.3.6.1.2.1.10.238.1.3.1.1.1,ADSL2-LINE-MIB::adsl2LInvUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit atuc(1) or atur(2).
.1.3.6.1.2.1.10.238.1.3.1.1.2,ADSL2-LINE-MIB::adsl2LInvG994VendorId,OCTET,read-only,,current,,The ATU G.994.1 Vendor ID as inserted in the G.994.1 CL/CLR message. It consists of 8 binary octets, including a country code followed by a (regionally allocated) provider code, as defined in Recommendation T.35.
.1.3.6.1.2.1.10.238.1.3.1.1.3,ADSL2-LINE-MIB::adsl2LInvSystemVendorId,OCTET,read-only,,current,,The ATU System Vendor ID (identifies the ATU system integrator) as inserted in the Overhead Messages (both ATUs for G.992.3 and G.992.4) or in the Embedded Operations Channel (only ATU-R in G.992.1 and G.992.2). It consists of 8 binary octets, with the same format as used for Adsl2InvG994VendorId.
.1.3.6.1.2.1.10.238.1.3.1.1.4,ADSL2-LINE-MIB::adsl2LInvVersionNumber,OCTET,read-only,,current,,The ATU version number (vendor-specific information) as inserted in the Overhead Messages (both ATUs for G.992.3 and G.992.4) or in the Embedded Operations Channel (only ATU-R in G.992.1 and G.992.2). It consists of up to 16 binary octets.
.1.3.6.1.2.1.10.238.1.3.1.1.5,ADSL2-LINE-MIB::adsl2LInvSerialNumber,OCTET,read-only,,current,,The ATU serial number (vendor-specific information) as inserted in the Overhead Messages (both ATUs for G.992.3 and G.992.4) or in the Embedded Operations Channel (only ATU-R in G.992.1 and G.992.2). It is vendor-specific information. It consists of up to 32 ASCII characters.
.1.3.6.1.2.1.10.238.1.3.1.1.6,ADSL2-LINE-MIB::adsl2LInvSelfTestResult,Unsigned32,read-only,,current,,The ATU self-test result, coded as a 32-bit value. The most significant octet of the result is '0' if the self-test passed, and '1' if the self-test failed. The interpretation of the other octets is vendor discretionary.
.1.3.6.1.2.1.10.238.1.3.1.1.7,ADSL2-LINE-MIB::adsl2LInvTransmissionCapabilities,BITS,read-only,,current,ansit1413(0):etsi(1):g9921PotsNonOverlapped(2):g9921PotsOverlapped(3):g9921IsdnNonOverlapped(4):g9921isdnOverlapped(5):g9921tcmIsdnNonOverlapped(6):g9921tcmIsdnOverlapped(7):g9922potsNonOverlapped(8):g9922potsOverlapped(9):g9922tcmIsdnNonOverlapped(10):g9922tcmIsdnOverlapped(11):g9921tcmIsdnSymmetric(12):reserved1(13):reserved2(14):reserved3(15):reserved4(16):reserved5(17):g9923PotsNonOverlapped(18):g9923PotsOverlapped(19):g9923IsdnNonOverlapped(20):g9923isdnOverlapped(21):reserved6(22):reserved7(23):g9924potsNonOverlapped(24):g9924potsOverlapped(25):reserved8(26):reserved9(27):g9923AnnexIAllDigNonOverlapped(28):g9923AnnexIAllDigOverlapped(29):g9923AnnexJAllDigNonOverlapped(30):g9923AnnexJAllDigOverlapped(31):g9924AnnexIAllDigNonOverlapped(32):g9924AnnexIAllDigOverlapped(33):g9923AnnexLMode1NonOverlapped(34):g9923AnnexLMode2NonOverlapped(35):g9923AnnexLMode3Overlapped(36):g9923AnnexLMode4Overlapped(37):g9923AnnexMPotsNonOverlapped(38):g9923AnnexMPotsOverlapped(39):g9925PotsNonOverlapped(40):g9925PotsOverlapped(41):g9925IsdnNonOverlapped(42):g9925isdnOverlapped(43):reserved10(44):reserved11(45):g9925AnnexIAllDigNonOverlapped(46):g9925AnnexIAllDigOverlapped(47):g9925AnnexJAllDigNonOverlapped(48):g9925AnnexJAllDigOverlapped(49):g9925AnnexMPotsNonOverlapped(50):g9925AnnexMPotsOverlapped(51):reserved12(52):reserved13(53):reserved14(54):reserved15(55),The ATU transmission system capability list of the different coding types. It is coded in a bit-map representation with 1 or more bits set. A bit set to '1' means that the ATU supports the respective coding. The value may be derived from the handshaking procedures defined in G.994.1. A set of ADSL2 line transmission modes, with one bit per mode.
.1.3.6.1.2.1.10.238.1.4,ADSL2-LINE-MIB::adsl2PM,,,,,,
.1.3.6.1.2.1.10.238.1.4.1,ADSL2-LINE-MIB::adsl2PMLine,,,,,,
.1.3.6.1.2.1.10.238.1.4.1.1,ADSL2-LINE-MIB::adsl2PMLineCurrTable,,not-accessible,,current,,The table adsl2PMLineCurrTable contains current Performance Monitoring results of ADSL2 lines.
.1.3.6.1.2.1.10.238.1.4.1.1.1,ADSL2-LINE-MIB::adsl2PMLineCurrEntry,,not-accessible,ifIndex:adsl2PMLCurrUnit,current,,The table adsl2PMLineCurrTable contains current Performance Monitoring results of ADSL2 lines. The index of this table consists of an interface index, where the interface has an ifType of adsl2plus(238), along with a termination unit. The PM counters in the table are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.1.1.1.1,ADSL2-LINE-MIB::adsl2PMLCurrUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit atuc(1) or atur(2).
.1.3.6.1.2.1.10.238.1.4.1.1.1.2,ADSL2-LINE-MIB::adsl2PMLCurrValidIntervals,Unsigned32,read-only,,current,,Valid intervals.
.1.3.6.1.2.1.10.238.1.4.1.1.1.3,ADSL2-LINE-MIB::adsl2PMLCurrInvalidIntervals,Unsigned32,read-only,,current,,Invalid intervals.
.1.3.6.1.2.1.10.238.1.4.1.1.1.4,ADSL2-LINE-MIB::adsl2PMLCurr15MTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds since this PM interval began. Note that the PM counters are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.1.1.1.5,ADSL2-LINE-MIB::adsl2PMLCurr15MFecs,Counter32,read-only,,current,,Count of seconds during this interval where there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.238.1.4.1.1.1.6,ADSL2-LINE-MIB::adsl2PMLCurr15MEs,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >=1 OR LPR >= 1 ATU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >=1 OR RDI >=1 OR LPR-FE >=1 . This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.1.1.7,ADSL2-LINE-MIB::adsl2PMLCurr15MSes,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1 . This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.1.1.8,ADSL2-LINE-MIB::adsl2PMLCurr15MLoss,Counter32,read-only,,current,,Count of seconds during this interval where there was LOS (or LOS-FE for ATU-R).
.1.3.6.1.2.1.10.238.1.4.1.1.1.9,ADSL2-LINE-MIB::adsl2PMLCurr15MUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely-errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds.
.1.3.6.1.2.1.10.238.1.4.1.1.1.10,ADSL2-LINE-MIB::adsl2PMLCurr1DayValidIntervals,Unsigned32,read-only,,current,,Valid intervals.
.1.3.6.1.2.1.10.238.1.4.1.1.1.11,ADSL2-LINE-MIB::adsl2PMLCurr1DayInvalidIntervals,Unsigned32,read-only,,current,,Invalid intervals.
.1.3.6.1.2.1.10.238.1.4.1.1.1.12,ADSL2-LINE-MIB::adsl2PMLCurr1DayTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds since this PM interval began. Note that the PM counters are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.1.1.1.13,ADSL2-LINE-MIB::adsl2PMLCurr1DayFecs,Counter32,read-only,,current,,Count of seconds during this interval where there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.238.1.4.1.1.1.14,ADSL2-LINE-MIB::adsl2PMLCurr1DayEs,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.1.1.15,ADSL2-LINE-MIB::adsl2PMLCurr1DaySes,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1 This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.1.1.16,ADSL2-LINE-MIB::adsl2PMLCurr1DayLoss,Counter32,read-only,,current,,Count of seconds during this interval where there was LOS (or LOS-FE for ATU-R).
.1.3.6.1.2.1.10.238.1.4.1.1.1.17,ADSL2-LINE-MIB::adsl2PMLCurr1DayUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely- errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds.
.1.3.6.1.2.1.10.238.1.4.1.2,ADSL2-LINE-MIB::adsl2PMLineCurrInitTable,,not-accessible,,current,,The table adsl2PMLineCurrInitTable contains current initialization counters of the ADSL2 line. The PM counters in the table are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.1.2.1,ADSL2-LINE-MIB::adsl2PMLineCurrInitEntry,,not-accessible,ifIndex,current,,The table adsl2PMLineCurrInitTable contains current initialization counters of the ADSL2 line. The index of this table consists of an interface index, where the interface has an ifType of adsl2plus(238), and a termination unit.
.1.3.6.1.2.1.10.238.1.4.1.2.1.1,ADSL2-LINE-MIB::adsl2PMLCurrInit15MTimeElapsed,Unsigned32,read-only,,current,,Total elapsed seconds since this PM interval began. Note that the PM counters are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.1.2.1.2,ADSL2-LINE-MIB::adsl2PMLCurrInit15MFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.3,ADSL2-LINE-MIB::adsl2PMLCurrInit15MFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.4,ADSL2-LINE-MIB::adsl2PMLCurrInit15MShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.5,ADSL2-LINE-MIB::adsl2PMLCurrInit15MFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.6,ADSL2-LINE-MIB::adsl2PMLCurrInit1DayTimeElapsed,Unsigned32,read-only,,current,,Total elapsed seconds since this PM interval began. Note that the PM counters are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.1.2.1.7,ADSL2-LINE-MIB::adsl2PMLCurrInit1DayFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.8,ADSL2-LINE-MIB::adsl2PMLCurrInit1DayFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.9,ADSL2-LINE-MIB::adsl2PMLCurrInit1DayShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.2.1.10,ADSL2-LINE-MIB::adsl2PMLCurrInit1DayFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.3,ADSL2-LINE-MIB::adsl2PMLineHist15MinTable,,not-accessible,,current,,The table adsl2PMLineHist15MinTable contains PM line history for 15min intervals of the ADSL2 line.
.1.3.6.1.2.1.10.238.1.4.1.3.1,ADSL2-LINE-MIB::adsl2PMLineHist15MinEntry,,not-accessible,ifIndex:adsl2PMLHist15MUnit:adsl2PMLHist15MInterval,current,,The table adsl2PMLineHist15MinTable contains PM line history for 15min intervals of the ADSL2 line. The index of this table consists of an interface index, where the interface has an ifType of adsl2plus(238), along with a termination unit, and an interval number.
.1.3.6.1.2.1.10.238.1.4.1.3.1.1,ADSL2-LINE-MIB::adsl2PMLHist15MUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit atuc(1) or atur(2).
.1.3.6.1.2.1.10.238.1.4.1.3.1.2,ADSL2-LINE-MIB::adsl2PMLHist15MInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.238.1.4.1.3.1.3,ADSL2-LINE-MIB::adsl2PMLHist15MMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.238.1.4.1.3.1.4,ADSL2-LINE-MIB::adsl2PMLHist15MFecs,Counter32,read-only,,current,,Count of seconds during this interval where there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.238.1.4.1.3.1.5,ADSL2-LINE-MIB::adsl2PMLHist15MEs,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.3.1.6,ADSL2-LINE-MIB::adsl2PMLHist15MSes,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.3.1.7,ADSL2-LINE-MIB::adsl2PMLHist15MLoss,Counter32,read-only,,current,,Count of seconds during this interval where there was LOS (or LOS-FE for ATU-R).
.1.3.6.1.2.1.10.238.1.4.1.3.1.8,ADSL2-LINE-MIB::adsl2PMLHist15MUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely- errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds.
.1.3.6.1.2.1.10.238.1.4.1.3.1.9,ADSL2-LINE-MIB::adsl2PMLHist15MValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.238.1.4.1.4,ADSL2-LINE-MIB::adsl2PMLineHist1DayTable,,not-accessible,,current,,The table adsl2PMLineHist1DayTable contains PM line history for 24-hour intervals of the ADSL2 line.
.1.3.6.1.2.1.10.238.1.4.1.4.1,ADSL2-LINE-MIB::adsl2PMLineHist1DayEntry,,not-accessible,ifIndex:adsl2PMLHist1DUnit:adsl2PMLHist1DInterval,current,,The table adsl2PMLineHist1DayTable contains PM line history for 24-hour intervals of the ADSL2 line. The index of this table consists of an interface index, where the interface has an ifType of adsl2plus(238), along with a termination unit, and an interval number.
.1.3.6.1.2.1.10.238.1.4.1.4.1.1,ADSL2-LINE-MIB::adsl2PMLHist1DUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit.
.1.3.6.1.2.1.10.238.1.4.1.4.1.2,ADSL2-LINE-MIB::adsl2PMLHist1DInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.238.1.4.1.4.1.3,ADSL2-LINE-MIB::adsl2PMLHist1DMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.238.1.4.1.4.1.4,ADSL2-LINE-MIB::adsl2PMLHist1DFecs,Counter32,read-only,,current,,Count of seconds during this interval where there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.238.1.4.1.4.1.5,ADSL2-LINE-MIB::adsl2PMLHist1DEs,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.4.1.6,ADSL2-LINE-MIB::adsl2PMLHist1DSes,Counter32,read-only,,current,,Count of seconds during this interval where there was: ATU-C: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >> 1 OR LPR >= 1 ATU-R: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.238.1.4.1.4.1.7,ADSL2-LINE-MIB::adsl2PMLHist1DLoss,Counter32,read-only,,current,,Count of seconds during this interval where there was LOS (or LOS-FE for ATU-R).
.1.3.6.1.2.1.10.238.1.4.1.4.1.8,ADSL2-LINE-MIB::adsl2PMLHist1DUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely- errored seconds, and ends at the onset of 10 contiguous seconds with no severely-errored seconds.
.1.3.6.1.2.1.10.238.1.4.1.4.1.9,ADSL2-LINE-MIB::adsl2PMLHist1DValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.238.1.4.1.5,ADSL2-LINE-MIB::adsl2PMLineInitHist15MinTable,,not-accessible,,current,,The table adsl2PMLineInitHist15MinTable contains PM line initialization history for 15-minute intervals of the ADSL2 line.
.1.3.6.1.2.1.10.238.1.4.1.5.1,ADSL2-LINE-MIB::adsl2PMLineInitHist15MinEntry,,not-accessible,ifIndex:adsl2PMLHistInit15MInterval,current,,The table adsl2PMLineInitHist15MinTable contains PM line initialization history for 15 minutes intervals of the ADSL2 line. The index of this table consists of an interface index, where the interface has an ifType of adsl2plus(238), and an interval number.
.1.3.6.1.2.1.10.238.1.4.1.5.1.1,ADSL2-LINE-MIB::adsl2PMLHistInit15MInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.238.1.4.1.5.1.2,ADSL2-LINE-MIB::adsl2PMLHistInit15MMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.238.1.4.1.5.1.3,ADSL2-LINE-MIB::adsl2PMLHistInit15MFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.5.1.4,ADSL2-LINE-MIB::adsl2PMLHistInit15MFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.5.1.5,ADSL2-LINE-MIB::adsl2PMLHistInit15MShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.5.1.6,ADSL2-LINE-MIB::adsl2PMLHistInit15MFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.5.1.7,ADSL2-LINE-MIB::adsl2PMLHistInit15MValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.238.1.4.1.6,ADSL2-LINE-MIB::adsl2PMLineInitHist1DayTable,,not-accessible,,current,,The table adsl2PMLineInitHist1DayTable contains PM line initialization history for 24-hour intervals of the ADSL2 line.
.1.3.6.1.2.1.10.238.1.4.1.6.1,ADSL2-LINE-MIB::adsl2PMLineInitHist1DayEntry,,not-accessible,ifIndex:adsl2PMLHistinit1DInterval,current,,The table adsl2PMLineInitHist1DayTable contains PM line initialization history for 24-hour intervals of the ADSL2 line. The index of this table consists of an interface index, where the interface has an ifType of adsl2plus(238), and an interval number.
.1.3.6.1.2.1.10.238.1.4.1.6.1.1,ADSL2-LINE-MIB::adsl2PMLHistinit1DInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.238.1.4.1.6.1.2,ADSL2-LINE-MIB::adsl2PMLHistinit1DMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.238.1.4.1.6.1.3,ADSL2-LINE-MIB::adsl2PMLHistinit1DFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.6.1.4,ADSL2-LINE-MIB::adsl2PMLHistinit1DFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.6.1.5,ADSL2-LINE-MIB::adsl2PMLHistinit1DShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.238.1.4.1.6.1.6,ADSL2-LINE-MIB::adsl2PMLHistinit1DFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.238.1.4.1.6.1.7,ADSL2-LINE-MIB::adsl2PMLHistinit1DValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.238.1.4.2,ADSL2-LINE-MIB::adsl2PMChannel,,,,,,
.1.3.6.1.2.1.10.238.1.4.2.1,ADSL2-LINE-MIB::adsl2PMChCurrTable,,not-accessible,,current,,The table adsl2PMChCurrTable contains current Performance Monitoring results of the ADSL2 channel. The PM counters in the table are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.2.1.1,ADSL2-LINE-MIB::adsl2PMChCurrEntry,,not-accessible,ifIndex:adsl2PMChCurrUnit,current,,The table adsl2PMChCurrTable contains current Performance Monitoring results of the ADSL2 channel. The index of this table consists of an interface index, where the interface has an ifType value that is applicable for a DSL channel, along with a termination unit.
.1.3.6.1.2.1.10.238.1.4.2.1.1.1,ADSL2-LINE-MIB::adsl2PMChCurrUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit.
.1.3.6.1.2.1.10.238.1.4.2.1.1.2,ADSL2-LINE-MIB::adsl2PMChCurrValidIntervals,Unsigned32,read-only,,current,,Valid intervals.
.1.3.6.1.2.1.10.238.1.4.2.1.1.3,ADSL2-LINE-MIB::adsl2PMChCurrInvalidIntervals,Unsigned32,read-only,,current,,Invalid intervals.
.1.3.6.1.2.1.10.238.1.4.2.1.1.4,ADSL2-LINE-MIB::adsl2PMChCurr15MTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds since this PM interval began. Note that the PM counters are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.2.1.1.5,ADSL2-LINE-MIB::adsl2PMChCurr15MCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for ATU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.1.1.6,ADSL2-LINE-MIB::adsl2PMChCurr15MCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for ATU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.1.1.7,ADSL2-LINE-MIB::adsl2PMChCurr1DayValidIntervals,Unsigned32,read-only,,current,,Valid intervals.
.1.3.6.1.2.1.10.238.1.4.2.1.1.8,ADSL2-LINE-MIB::adsl2PMChCurr1DayInvalidIntervals,Unsigned32,read-only,,current,,Invalid intervals.
.1.3.6.1.2.1.10.238.1.4.2.1.1.9,ADSL2-LINE-MIB::adsl2PMChCurr1DayTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds since this PM interval began. Note that the PM counters are not reset even when the XTU is reinitialized. They are reinitialized only when the agent itself is reset or reinitialized.
.1.3.6.1.2.1.10.238.1.4.2.1.1.10,ADSL2-LINE-MIB::adsl2PMChCurr1DayCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for ATU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.1.1.11,ADSL2-LINE-MIB::adsl2PMChCurr1DayCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for ATU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.2,ADSL2-LINE-MIB::adsl2PMChHist15MinTable,,not-accessible,,current,,The table adsl2PMChCurrTable contains current Performance Monitoring results of the ADSL2 channel.
.1.3.6.1.2.1.10.238.1.4.2.2.1,ADSL2-LINE-MIB::adsl2PMChHist15MinEntry,,not-accessible,ifIndex:adsl2PMChHist15MUnit:adsl2PMChHist15MInterval,current,,The table adsl2PMChCurrTable contains current Performance Monitoring results of the ADSL2 channel. The index of this table consists of an interface index, where the interface has an ifType value that is applicable for a DSL channel, along with a termination unit, and the interval number.
.1.3.6.1.2.1.10.238.1.4.2.2.1.1,ADSL2-LINE-MIB::adsl2PMChHist15MUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit.
.1.3.6.1.2.1.10.238.1.4.2.2.1.2,ADSL2-LINE-MIB::adsl2PMChHist15MInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.238.1.4.2.2.1.3,ADSL2-LINE-MIB::adsl2PMChHist15MMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.238.1.4.2.2.1.4,ADSL2-LINE-MIB::adsl2PMChHist15MCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for ATU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.2.1.5,ADSL2-LINE-MIB::adsl2PMChHist15MCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for ATU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.2.1.6,ADSL2-LINE-MIB::adsl2PMChHist15MValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.238.1.4.2.3,ADSL2-LINE-MIB::adsl2PMChHist1DTable,,not-accessible,,current,,The table adsl2PMChHist1DayTable contains PM channel history for 1-day intervals of ADSL2.
.1.3.6.1.2.1.10.238.1.4.2.3.1,ADSL2-LINE-MIB::adsl2PMChHist1DEntry,,not-accessible,ifIndex:adsl2PMChHist1DUnit:adsl2PMChHist1DInterval,current,,The table adsl2PMChHist1DayTable contains PM channel history for 1-day intervals of ADSL2. The index of this table consists of an interface index, where the interface has an ifType value that is applicable for a DSL channel, along with a termination unit, and the interval number.
.1.3.6.1.2.1.10.238.1.4.2.3.1.1,ADSL2-LINE-MIB::adsl2PMChHist1DUnit,INTEGER,not-accessible,,current,atuc(1):atur(2),The termination unit.
.1.3.6.1.2.1.10.238.1.4.2.3.1.2,ADSL2-LINE-MIB::adsl2PMChHist1DInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.238.1.4.2.3.1.3,ADSL2-LINE-MIB::adsl2PMChHist1DMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.238.1.4.2.3.1.4,ADSL2-LINE-MIB::adsl2PMChHist1DCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for ATU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.3.1.5,ADSL2-LINE-MIB::adsl2PMChHist1DCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for ATU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly should increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.238.1.4.2.3.1.6,ADSL2-LINE-MIB::adsl2PMChHist1DValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.238.1.5,ADSL2-LINE-MIB::adsl2Profile,,,,,,
.1.3.6.1.2.1.10.238.1.5.1,ADSL2-LINE-MIB::adsl2ProfileLine,,,,,,
.1.3.6.1.2.1.10.238.1.5.1.1,ADSL2-LINE-MIB::adsl2LineConfTemplateTable,,not-accessible,,current,,The table adsl2LineConfTemplateTable contains ADSL2 line configuration templates. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.1.1.1,ADSL2-LINE-MIB::adsl2LineConfTemplateEntry,,not-accessible,adsl2LConfTempTemplateName,current,,The table adsl2LineConfTemplateTable contains the ADSL2 line configuration template. A default template with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor- specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.238.1.5.1.1.1.1,ADSL2-LINE-MIB::adsl2LConfTempTemplateName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.238.1.5.1.1.1.2,ADSL2-LINE-MIB::adsl2LConfTempLineProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Line Configuration Profile Table, (adsl2LineConfProfTable), which applies for this ADSL2 line.
.1.3.6.1.2.1.10.238.1.5.1.1.1.3,ADSL2-LINE-MIB::adsl2LConfTempChan1ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Configuration Profile Table, (adsl2ChConfProfileTable) that applies to ADSL2 bearer channel #1. The channel profile name specified here must match the name of an existing row in the adsl2ChConfProfileTable table.
.1.3.6.1.2.1.10.238.1.5.1.1.1.4,ADSL2-LINE-MIB::adsl2LConfTempChan1RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #1 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan1RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.5,ADSL2-LINE-MIB::adsl2LConfTempChan1RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #1 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan1RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.6,ADSL2-LINE-MIB::adsl2LConfTempChan2ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Configuration Profile Table (adsl2ChConfProfileTable) that applies to ADSL2 bearer channel #2. If the channel is unused, then the object is set to a zero-length string. This object may be set to a zero-length string only if adsl2LConfTempChan3ConfProfile contains a zero-length string.
.1.3.6.1.2.1.10.238.1.5.1.1.1.7,ADSL2-LINE-MIB::adsl2LConfTempChan2RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #2 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan2RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.8,ADSL2-LINE-MIB::adsl2LConfTempChan2RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #2 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan2RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.9,ADSL2-LINE-MIB::adsl2LConfTempChan3ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Configuration Profile Table (adsl2ChConfProfileTable) that applies to ADSL2 bearer channel #3. If the channel is unused, then the object is set to a zero-length string. This object may be set to a zero-length string only if adsl2LConfTempChan4ConfProfile contains a zero-length string. This object may be set to a non-zero-length string only if adsl2LConfTempChan2ConfProfile contains a non-zero-length string.
.1.3.6.1.2.1.10.238.1.5.1.1.1.10,ADSL2-LINE-MIB::adsl2LConfTempChan3RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #3 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan3RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.11,ADSL2-LINE-MIB::adsl2LConfTempChan3RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #3 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan3RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.12,ADSL2-LINE-MIB::adsl2LConfTempChan4ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Configuration Profile Table (adsl2ChConfProfileTable) that applies to ADSL2 bearer channel #4. If the channel is unused, then the object is set to a zero-length string. This object may be set to a non-zero-length string only if adsl2LConfTempChan3ConfProfile contains a non-zero-length string.
.1.3.6.1.2.1.10.238.1.5.1.1.1.13,ADSL2-LINE-MIB::adsl2LConfTempChan4RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #4 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan4RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels. The sum of rate adaptation ratios over all bearers on the same direction shall sum to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.14,ADSL2-LINE-MIB::adsl2LConfTempChan4RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in %) that should be taken into account for the bearer channel #4 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - adsl2LConfTempChan4RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels. The sum of rate adaptation ratios over all bearers on the same direction shall sum to 100%.
.1.3.6.1.2.1.10.238.1.5.1.1.1.15,ADSL2-LINE-MIB::adsl2LConfTempRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A template is activated by setting this object to 'active'. When 'active' is set, the system will validate the template. Before a template can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated lines.
.1.3.6.1.2.1.10.238.1.5.1.2,ADSL2-LINE-MIB::adsl2LineConfProfTable,,not-accessible,,current,,The table adsl2LineConfProfTable contains ADSL2 line profile configuration. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.1.2.1,ADSL2-LINE-MIB::adsl2LineConfProfEntry,,not-accessible,adsl2LConfProfProfileName,current,,The table adsl2LineConfProfTable contains ADSL2 line profile configuration. A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor- specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.238.1.5.1.2.1.1,ADSL2-LINE-MIB::adsl2LConfProfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.238.1.5.1.2.1.2,ADSL2-LINE-MIB::adsl2LConfProfScMaskDs,OCTET,read-create,,current,,Sub-carriers mask. A bitmap of 512 bits that allows masking up to 512 downstream sub-carriers, depending on NSCds. If bit i (0 <= i < NSCds) is set to '1', the respective downstream sub-carrier i is masked, and if set to '0', the respective sub-carrier is unmasked. Note that there should always be unmasked sub-carriers (i.e., the object cannot be all 1's). Also note that if NSCds < 512, all bits i (NSCds < i <= 512) should be set to '1'.
.1.3.6.1.2.1.10.238.1.5.1.2.1.3,ADSL2-LINE-MIB::adsl2LConfProfScMaskUs,OCTET,read-create,,current,,Sub-carriers mask. A bitmap of 64 bits that allows masking up to 64 downstream sub-carriers, depending on NSCds. If bit i (0 <= i < NSCus) is set to '1', the respective upstream sub-carrier i is masked, and if set to '0', the respective sub-carrier is unmasked. Note that there should always be unmasked sub-carriers (i.e., the object cannot be all 1's). Also note that if NSCus < 64, all bits i (NSCus < i <= 64) should be set to '1'.
.1.3.6.1.2.1.10.238.1.5.1.2.1.4,ADSL2-LINE-MIB::adsl2LConfProfRfiBandsDs,OCTET,read-create,,current,,The subset of downstream PSD mask breakpoints that shall be used to notch an RFI band. The specific interpolation around these points is defined in G.992.5. It is a bitmap of 512 bits that allows referring to up to 512 downstream sub-carriers, depending on NSCds. If bit i (0 <= i < NSCds) is set to '1', the respective downstream sub-carrier i is part of a notch filter, and if set to '0', the respective sub-carrier is not part of a notch filter. This information complements the specification provided by adsl2LConfProfPsdMaskDs. Note that if NSCds < 512, all bits i (NSCds<i<512) should be set to '0'.
.1.3.6.1.2.1.10.238.1.5.1.2.1.5,ADSL2-LINE-MIB::adsl2LConfProfRaModeDs,INTEGER,read-create,,current,manual(1):raInit(2):dynamicRa(3),The mode of operation of a rate-adaptive ATU-C in the transmit direction. The parameter can take three values: manual(1), raInit(2), or dynamicRa(3).
.1.3.6.1.2.1.10.238.1.5.1.2.1.6,ADSL2-LINE-MIB::adsl2LConfProfRaModeUs,INTEGER,read-create,,current,manual(1):raInit(2):dynamicRa(3),The mode of operation of a rate-adaptive ATU-R in the transmit direction. The parameter can take three values: manual(1), raInit(2), or dynamicRa(3).
.1.3.6.1.2.1.10.238.1.5.1.2.1.7,ADSL2-LINE-MIB::adsl2LConfProfRaUsNrmDs,Unsigned32,read-create,,current,,The Downstream Up-Shift Noise Margin value, to be used when adsl2LConfProfRaModeDs is set to dynamicRa. If the downstream noise margin is above this value and stays above it for more than the time specified by the adsl2LConfProfRaUsTimeDs, the ATU-R shall attempt to increase the downstream net data rate. The Downstream Up-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.238.1.5.1.2.1.8,ADSL2-LINE-MIB::adsl2LConfProfRaUsNrmUs,Unsigned32,read-create,,current,,The Upstream Up-Shift Noise Margin value, to be used when adsl2LConfProfRaModeUs is set to dynamicRa. If the upstream noise margin is above this value and stays above it for more than the time specified by the adsl2LConfProfRaUsTimeUs, the ATU-C shall attempt to increase the upstream net data rate. The Upstream Up-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.238.1.5.1.2.1.9,ADSL2-LINE-MIB::adsl2LConfProfRaUsTimeDs,Unsigned32,read-create,,current,,The Downstream Up-Shift Time Interval, to be used when adsl2LConfProfRaModeDs is set to dynamicRa. The interval of time that the downstream noise margin should stay above the Downstream Up-Shift Noise Margin before the ATU-R shall attempt to increase the downstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.238.1.5.1.2.1.10,ADSL2-LINE-MIB::adsl2LConfProfRaUsTimeUs,Unsigned32,read-create,,current,,The Upstream Up-Shift Time Interval, to be used when adsl2LConfProfRaModeUs is set to dynamicRa. The interval of time the upstream noise margin should stay above the Upstream Up-Shift Noise Margin before the ATU-C shall attempt to increase the upstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.238.1.5.1.2.1.11,ADSL2-LINE-MIB::adsl2LConfProfRaDsNrmsDs,Unsigned32,read-create,,current,,The Downstream Down-Shift Noise Margin value, to be used when adsl2LConfProfRaModeDs is set to dynamicRa. If the downstream noise margin is below this value and stays below that for more than the time specified by the adsl2LConfProfRaDsTimeDs, the ATU-R shall attempt to decrease the downstream net data rate. The Downstream Down-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.238.1.5.1.2.1.12,ADSL2-LINE-MIB::adsl2LConfProfRaDsNrmsUs,Unsigned32,read-create,,current,,The Upstream Down-Shift Noise Margin value, to be used when adsl2LConfProfRaModeUs is set to dynamicRa. If the upstream noise margin is below this value and stays below that for more than the time specified by the adsl2LConfProfRaDsTimeUs, the ATU-C shall attempt to decrease the upstream net data rate. The Upstream Down-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.238.1.5.1.2.1.13,ADSL2-LINE-MIB::adsl2LConfProfRaDsTimeDs,Unsigned32,read-create,,current,,The Downstream Down-Shift Time Interval, to be used when adsl2LConfProfRaModeDs is set to dynamicRa. The interval of time the downstream noise margin should stay below the Downstream Down-Shift Noise Margin before the ATU-R shall attempt to decrease the downstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.238.1.5.1.2.1.14,ADSL2-LINE-MIB::adsl2LConfProfRaDsTimeUs,Unsigned32,read-create,,current,,The Upstream Down-Shift Time Interval, to be used when adsl2LConfProfRaModeUs is set to dynamicRa. The interval of time the upstream noise margin should stay below the Upstream Down-Shift Noise Margin before the ATU-C shall attempt to decrease the upstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.238.1.5.1.2.1.15,ADSL2-LINE-MIB::adsl2LConfProfTargetSnrmDs,Unsigned32,read-create,,current,,The minimum Noise Margin the ATU-R receiver shall achieve, relative to the BER requirement for each of the downstream bearer channels, to successfully complete initialization. The target noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.238.1.5.1.2.1.16,ADSL2-LINE-MIB::adsl2LConfProfTargetSnrmUs,Unsigned32,read-create,,current,,The minimum Noise Margin the ATU-C receiver shall achieve, relative to the BER requirement for each of the upstream bearer channels, to successfully complete initialization. The target noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.238.1.5.1.2.1.17,ADSL2-LINE-MIB::adsl2LConfProfMaxSnrmDs,Unsigned32,read-create,,current,,The maximum Noise Margin the ATU-R receiver shall try to sustain. If the Noise Margin is above this level, the ATU-R shall request that the ATU-C reduce the ATU-C transmit power to get a noise margin below this limit (if this functionality is supported). The maximum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0x7FFFFFFF (2147483647) means that there is no maximum.
.1.3.6.1.2.1.10.238.1.5.1.2.1.18,ADSL2-LINE-MIB::adsl2LConfProfMaxSnrmUs,Unsigned32,read-create,,current,,The maximum Noise Margin the ATU-C receiver shall try to sustain. If the Noise Margin is above this level, the ATU-C shall request that the ATU-R reduce the ATU-R transmit power to get a noise margin below this limit (if this functionality is supported). The maximum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0x7FFFFFFF (2147483647) means that there is no maximum.
.1.3.6.1.2.1.10.238.1.5.1.2.1.19,ADSL2-LINE-MIB::adsl2LConfProfMinSnrmDs,Unsigned32,read-create,,current,,The minimum Noise Margin the ATU-R receiver shall tolerate. If the noise margin falls below this level, the ATU-R shall request that the ATU-C increase the ATU-C transmit power. If an increase to ATU-C transmit power is not possible, a loss-of-margin (LOM) defect occurs, the ATU-R shall fail and attempt to reinitialize, and the NMS shall be notified. The minimum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0 means that there is no minimum.
.1.3.6.1.2.1.10.238.1.5.1.2.1.20,ADSL2-LINE-MIB::adsl2LConfProfMinSnrmUs,Unsigned32,read-create,,current,,The minimum Noise Margin the ATU-C receiver shall tolerate. If the noise margin falls below this level, the ATU-C shall request that the ATU-R increase the ATU-R transmit power. If an increase of ATU-R transmit power is not possible, a loss-of-margin (LOM) defect occurs, the ATU-C shall fail and attempt to reinitialize, and the NMS shall be notified. The minimum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0 means that there is no minimum.
.1.3.6.1.2.1.10.238.1.5.1.2.1.21,ADSL2-LINE-MIB::adsl2LConfProfMsgMinUs,Unsigned32,read-create,,current,,Minimum Overhead Rate Upstream. Defines the minimum rate of the message-based overhead that shall be maintained by the ATU in upstream direction. Expressed in bits per second and ranges from 4000 to 63000 bps.
.1.3.6.1.2.1.10.238.1.5.1.2.1.22,ADSL2-LINE-MIB::adsl2LConfProfMsgMinDs,Unsigned32,read-create,,current,,Minimum Overhead Rate Downstream. Defines the minimum rate of the message-based overhead that shall be maintained by the ATU in downstream direction. Expressed in bits per second and ranges from 4000 to 63000 bps.
.1.3.6.1.2.1.10.238.1.5.1.2.1.23,ADSL2-LINE-MIB::adsl2LConfProfAtuTransSysEna,BITS,read-create,,current,ansit1413(0):etsi(1):g9921PotsNonOverlapped(2):g9921PotsOverlapped(3):g9921IsdnNonOverlapped(4):g9921isdnOverlapped(5):g9921tcmIsdnNonOverlapped(6):g9921tcmIsdnOverlapped(7):g9922potsNonOverlapped(8):g9922potsOverlapped(9):g9922tcmIsdnNonOverlapped(10):g9922tcmIsdnOverlapped(11):g9921tcmIsdnSymmetric(12):reserved1(13):reserved2(14):reserved3(15):reserved4(16):reserved5(17):g9923PotsNonOverlapped(18):g9923PotsOverlapped(19):g9923IsdnNonOverlapped(20):g9923isdnOverlapped(21):reserved6(22):reserved7(23):g9924potsNonOverlapped(24):g9924potsOverlapped(25):reserved8(26):reserved9(27):g9923AnnexIAllDigNonOverlapped(28):g9923AnnexIAllDigOverlapped(29):g9923AnnexJAllDigNonOverlapped(30):g9923AnnexJAllDigOverlapped(31):g9924AnnexIAllDigNonOverlapped(32):g9924AnnexIAllDigOverlapped(33):g9923AnnexLMode1NonOverlapped(34):g9923AnnexLMode2NonOverlapped(35):g9923AnnexLMode3Overlapped(36):g9923AnnexLMode4Overlapped(37):g9923AnnexMPotsNonOverlapped(38):g9923AnnexMPotsOverlapped(39):g9925PotsNonOverlapped(40):g9925PotsOverlapped(41):g9925IsdnNonOverlapped(42):g9925isdnOverlapped(43):reserved10(44):reserved11(45):g9925AnnexIAllDigNonOverlapped(46):g9925AnnexIAllDigOverlapped(47):g9925AnnexJAllDigNonOverlapped(48):g9925AnnexJAllDigOverlapped(49):g9925AnnexMPotsNonOverlapped(50):g9925AnnexMPotsOverlapped(51):reserved12(52):reserved13(53):reserved14(54):reserved15(55),ATU Transmission System Enabling (ATSE). A list of the different coding types enabled in this profile. It is coded in a bit-map representation with 1 or more bits set. A bit set to '1' means that the ATUs may apply the respective coding for the ADSL line. A bit set to '0' means that the ATUs cannot apply the respective coding for the ADSL line. All 'reserved' bits should be set to '0'.
.1.3.6.1.2.1.10.238.1.5.1.2.1.24,ADSL2-LINE-MIB::adsl2LConfProfPmMode,BITS,read-create,,current,allowTransitionsToIdle(0):allowTransitionsToLowPower(1),Power management state Enabling. Defines the power states the ATU-C or ATU-R may autonomously transition to on this line. The various bit positions are: allowTransitionsToIdle(0) and allowTransitionsToLowPower(1). A bit with a '1' value means that the ATU is allowed to transit into the respective state, and a '0' value means that the ATU is not allowed to transit into the respective state.
.1.3.6.1.2.1.10.238.1.5.1.2.1.25,ADSL2-LINE-MIB::adsl2LConfProfL0Time,Unsigned32,read-create,,current,,This minimum time (in seconds) between an Exit from the L2 state and the next Entry into the L2 state. It ranges from 0 to 255 seconds.
.1.3.6.1.2.1.10.238.1.5.1.2.1.26,ADSL2-LINE-MIB::adsl2LConfProfL2Time,Unsigned32,read-create,,current,,This minimum time (in seconds) between an Entry into the L2 state and the first Power Trim in the L2 state and between two consecutive Power Trims in the L2 State. It ranges from 0 to 255 seconds.
.1.3.6.1.2.1.10.238.1.5.1.2.1.27,ADSL2-LINE-MIB::adsl2LConfProfL2Atpr,Unsigned32,read-create,,current,,The maximum aggregate transmit power reduction (in dB) that can be performed at transition of L0 to L2 state or through a single Power Trim in the L2 state. It ranges from 0 dB to 31 dB.
.1.3.6.1.2.1.10.238.1.5.1.2.1.28,ADSL2-LINE-MIB::adsl2LConfProfL2Atprt,Unsigned32,read-create,,current,,The total maximum aggregate transmit power reduction (in dB) that can be performed in an L2 state. This is the sum of all reductions of L2 Request (i.e., at transition of L0 to L2 state) and Power Trims.
.1.3.6.1.2.1.10.238.1.5.1.2.1.29,ADSL2-LINE-MIB::adsl2LConfProfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates.
.1.3.6.1.2.1.10.238.1.5.1.3,ADSL2-LINE-MIB::adsl2LineConfProfModeSpecTable,,not-accessible,,current,,The table adsl2LineConfProfModeSpecTable extends the ADSL2 line configuration profile by ADSL Mode Specific parameters. A row in this table that has an index of adsl2LConfProfAdslMode == defMode(1) is called a 'mandatory' row. A row in this table that has an index such that adsl2LConfProfAdslMode is not equal to defMode(1) is called an 'optional' row. When a row in the adsl2LineConfProfTable table (the parent row) is created, the SNMP agent will automatically create a 'mandatory' row in this table. When the parent row is deleted, the SNMP agent will automatically delete all associated rows in this table. Any attempt to delete the 'mandatory' row using the adsl2LConfProfModeSpecRowStatus attribute will be rejected by the SNMP agent. The manager MAY create an 'optional' row in this table using the adsl2LConfProfModeSpecRowStatus attribute if the parent row exists. The manager MAY delete an 'optional' row in this table using the adsl2LConfProfModeSpecRowStatus attribute at any time. If the actual transmission mode of a DSL line does not match one of the 'optional' rows in this table, then the line will use the PSD configuration from the 'mandatory' row. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.1.3.1,ADSL2-LINE-MIB::adsl2LineConfProfModeSpecEntry,,not-accessible,adsl2LConfProfProfileName:adsl2LConfProfAdslMode,current,,The table adsl2LineConfProfModeSpecTable extends the ADSL2 line configuration profile by ADSL Mode Specific parameters.
.1.3.6.1.2.1.10.238.1.5.1.3.1.1,ADSL2-LINE-MIB::adsl2LConfProfAdslMode,INTEGER,not-accessible,,current,defMode(1):adsl(2):g9923PotsNonOverlapped(8):g9923PotsOverlapped(9):g9923IsdnNonOverlapped(10):g9923isdnOverlapped(11):g9924potsNonOverlapped(14):g9924potsOverlapped(15):g9923AnnexIAllDigNonOverlapped(18):g9923AnnexIAllDigOverlapped(19):g9923AnnexJAllDigNonOverlapped(20):g9923AnnexJAllDigOverlapped(21):g9924AnnexIAllDigNonOverlapped(22):g9924AnnexIAllDigOverlapped(23):g9923AnnexLMode1NonOverlapped(24):g9923AnnexLMode2NonOverlapped(25):g9923AnnexLMode3Overlapped(26):g9923AnnexLMode4Overlapped(27):g9923AnnexMPotsNonOverlapped(28):g9923AnnexMPotsOverlapped(29):g9925PotsNonOverlapped(30):g9925PotsOverlapped(31):g9925IsdnNonOverlapped(32):g9925isdnOverlapped(33):g9925AnnexIAllDigNonOverlapped(36):g9925AnnexIAllDigOverlapped(37):g9925AnnexJAllDigNonOverlapped(38):g9925AnnexJAllDigOverlapped(39):g9925AnnexMPotsNonOverlapped(40):g9925AnnexMPotsOverlapped(41),The ADSL Mode is a way of categorizing the various ADSL transmission modes into groups; each group (ADSL Mode) shares the same PSD configuration. There should be multiple entries in this table for a given line profile in case multiple bits are set in adsl2LConfProfAtuTransSysEna for that profile.
.1.3.6.1.2.1.10.238.1.5.1.3.1.2,ADSL2-LINE-MIB::adsl2LConfProfMaxNomPsdDs,Integer32,read-create,,current,,The maximum nominal transmit PSD in the downstream direction during initialization and Showtime. It ranges from -600 to -300 units of 0.1 dBm/Hz (physical values are -60 to -30 dBm/Hz).
.1.3.6.1.2.1.10.238.1.5.1.3.1.3,ADSL2-LINE-MIB::adsl2LConfProfMaxNomPsdUs,Integer32,read-create,,current,,The maximum nominal transmit PSD in the upstream direction during initialization and Showtime. It ranges from -600 to -300 units of 0.1 dBm/Hz (physical values are -60 to -30 dBm/Hz).
.1.3.6.1.2.1.10.238.1.5.1.3.1.4,ADSL2-LINE-MIB::adsl2LConfProfMaxNomAtpDs,Unsigned32,read-create,,current,,The maximum nominal aggregate transmit power in the downstream direction during initialization and Showtime. It ranges from 0 to 255 units of 0.1 dBm (physical values are 0 to 25.5 dBm).
.1.3.6.1.2.1.10.238.1.5.1.3.1.5,ADSL2-LINE-MIB::adsl2LConfProfMaxNomAtpUs,Unsigned32,read-create,,current,,The maximum nominal aggregate transmit power in the upstream direction during initialization and Showtime. It ranges from 0 to 255 units of 0.1 dBm (physical values are 0 to 25.5 dBm).
.1.3.6.1.2.1.10.238.1.5.1.3.1.6,ADSL2-LINE-MIB::adsl2LConfProfMaxAggRxPwrUs,Integer32,read-create,,current,,The maximum upstream aggregate receive power over the relevant set of sub-carriers. The ATU-C should verify that the upstream power cutback is such that this maximum aggregate receive power value is honored. It ranges from -255 to 255 units of 0.1 dBm (physical values are -25.5 to 25.5 dBm). A value of 0x7FFFFFFF (2147483647) means that there is no limit.
.1.3.6.1.2.1.10.238.1.5.1.3.1.7,ADSL2-LINE-MIB::adsl2LConfProfPsdMaskDs,OCTET,read-create,,current,,The downstream PSD mask applicable at the U-C2 reference point. This parameter is used only for G.992.5, and it may impose PSD restrictions (breakpoints) in addition to the Limit PSD mask defined in G.992.5. This is a string of 32 pairs of values in the following structure: Octets 0+1 - Index of 1st sub-carrier used in the context of a first breakpoint. Octet 2 - The PSD reduction for the sub-carrier indicated in octets 0 and 1. Octets 3-5 - Same, for a 2nd breakpoint. Octets 6-8 - Same, for a 3rd breakpoint. This architecture continues until octets 94-95, which are associated with a 32nd breakpoint. Each subcarrier index is an unsigned number in the range 1 to NSCds. Each PSD reduction value is in the range 0 (0dBm/Hz) to 255 (-127.5dBm/Hz) with steps of 0.5dBm/Hz. Valid values are in the range 0 to 190 (0 to -95dBm/Hz). When the number of breakpoints is less than 32, all remaining octets are set to the value 0. Note that the content of this object should be correlated with the sub-carriers mask and with the RFI setup.
.1.3.6.1.2.1.10.238.1.5.1.3.1.8,ADSL2-LINE-MIB::adsl2LConfProfPsdMaskUs,OCTET,read-create,,current,,The upstream PSD mask applicable at the U-R2 reference point. This parameter is used only for G.992.5, and it may impose PSD restrictions (breakpoints) in addition to the Limit PSD mask defined in G.992.5. This is a string of 4 pairs of values in the following structure: Octets 0+1 - Index of 1st sub-carrier used in the context of a first breakpoint. Octet 2 - The PSD reduction for the sub-carrier indicated in octets 0 and 1. Octets 3-5 - Same, for a 2nd breakpoint. Octets 6-8 - Same, for a 3rd breakpoint. This architecture continues until octets 9-11, which are associated with a 4th breakpoint. Each subcarrier index is an unsigned number in the range 1 to NSCus. Each PSD reduction value is in the range 0 (0dBm/Hz) to 255 (-127.5dBm/Hz) with steps of 0.5dBm/Hz. Valid values are in the range 0 to 190 (0 to -95dBm/Hz). When the number of breakpoints is less than 4, all remaining octets are set to the value 0. Note that the content of this object should be correlated with the sub-carriers mask and with the RFI setup.
.1.3.6.1.2.1.10.238.1.5.1.3.1.9,ADSL2-LINE-MIB::adsl2LConfProfPsdMaskSelectUs,Unsigned32,read-create,,current,,The selected upstream PSD mask. This parameter is used only for annexes J and M of G.992.3 and G.992.5, and the same selection is used for all relevant enabled bits in adsl2LConfProfAtuTransSysEna.
.1.3.6.1.2.1.10.238.1.5.1.3.1.10,ADSL2-LINE-MIB::adsl2LConfProfModeSpecRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates.
.1.3.6.1.2.1.10.238.1.5.2,ADSL2-LINE-MIB::adsl2ProfileChannel,,,,,,
.1.3.6.1.2.1.10.238.1.5.2.1,ADSL2-LINE-MIB::adsl2ChConfProfileTable,,not-accessible,,current,,The table adsl2ChConfProfileTable contains ADSL2 channel profile configuration. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.2.1.1,ADSL2-LINE-MIB::adsl2ChConfProfileEntry,,not-accessible,adsl2ChConfProfProfileName,current,,The table adsl2ChConfProfileTable contains ADSL2 channel profile configuration. A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor- specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.238.1.5.2.1.1.1,ADSL2-LINE-MIB::adsl2ChConfProfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.238.1.5.2.1.1.2,ADSL2-LINE-MIB::adsl2ChConfProfMinDataRateDs,Unsigned32,read-create,,current,,Minimum Data Rate on Downstream direction. The minimum net data rate for the bearer channel, coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.3,ADSL2-LINE-MIB::adsl2ChConfProfMinDataRateUs,Unsigned32,read-create,,current,,Minimum Data Rate on Upstream direction. The minimum net data rate for the bearer channel, coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.4,ADSL2-LINE-MIB::adsl2ChConfProfMinResDataRateDs,Unsigned32,read-create,,current,,Minimum Reserved Data Rate on Downstream direction. The minimum reserved net data rate for the bearer channel, coded in bits/second. This parameter is used only if the Rate Adaptation Mode in the direction of the bearer channel (i.e., adsl2LConfProfRaModeDs) is set to dynamicRa.
.1.3.6.1.2.1.10.238.1.5.2.1.1.5,ADSL2-LINE-MIB::adsl2ChConfProfMinResDataRateUs,Unsigned32,read-create,,current,,Minimum Reserved Data Rate on Upstream direction. The minimum reserved net data rate for the bearer channel, coded in bits/second. This parameter is used only if the Rate Adaptation Mode in the direction of the bearer channel (i.e., adsl2LConfProfRaModeUs) is set to dynamicRa.
.1.3.6.1.2.1.10.238.1.5.2.1.1.6,ADSL2-LINE-MIB::adsl2ChConfProfMaxDataRateDs,Unsigned32,read-create,,current,,Maximum Data Rate on Downstream direction. The maximum net data rate for the bearer channel, coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.7,ADSL2-LINE-MIB::adsl2ChConfProfMaxDataRateUs,Unsigned32,read-create,,current,,Maximum Data Rate on Upstream direction. The maximum net data rate for the bearer channel, coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.8,ADSL2-LINE-MIB::adsl2ChConfProfMinDataRateLowPwrDs,Unsigned32,read-create,,current,,Minimum Data Rate in Low Power state on Downstream direction. The minimum net data rate for the bearer channel, coded in bits/second, during the low power state (L1 in G.992.2, L2 in G.992.3).
.1.3.6.1.2.1.10.238.1.5.2.1.1.9,ADSL2-LINE-MIB::adsl2ChConfProfMaxDelayDs,Unsigned32,read-create,,current,,Maximum Interleave Delay on Downstream direction. The maximum one-way interleaving delay introduced by the PMS-TC on Downstream direction. The ATUs shall choose the S (factor) and D (depth) values such that the actual one-way interleaving delay (adsl2ChStatusActDelay) is as close as possible to, but less than or equal to, adsl2ChConfProfMaxDelayDs. The delay is coded in ms, with the value 0 indicating no delay bound is being imposed.
.1.3.6.1.2.1.10.238.1.5.2.1.1.10,ADSL2-LINE-MIB::adsl2ChConfProfMaxDelayUs,Unsigned32,read-create,,current,,Maximum Interleave Delay on Upstream direction. The maximum one-way interleaving delay introduced by the PMS-TC on Upstream direction. The ATUs shall choose the S (factor) and D (depth) values such that the actual one-way interleaving delay (adsl2ChStatusActDelay) is as close as possible to, but less than or equal to, adsl2ChConfProfMaxDelayUs. The delay is coded in ms, with the value 0 indicating no delay bound is being imposed.
.1.3.6.1.2.1.10.238.1.5.2.1.1.11,ADSL2-LINE-MIB::adsl2ChConfProfMinProtectionDs,INTEGER,read-create,,current,noProtection(1):halfSymbol(2):singleSymbol(3):twoSymbols(4):threeSymbols(5):fourSymbols(6):fiveSymbols(7):sixSymbols(8):sevenSymbols(9):eightSymbols(10):nineSymbols(11):tenSymbols(12):elevenSymbols(13):twelveSymbols(14):thirteeSymbols(15):fourteenSymbols(16):fifteenSymbols(17):sixteenSymbols(18),Minimum Impulse Noise Protection on Downstream direction. The minimum impulse noise protection for the bearer channel, expressed in symbols. The parameter can take the following values: noProtection (i.e., INP not required), halfSymbol (i.e., INP length is 1/2 symbol), and 1-16 symbols in steps of 1 symbol.
.1.3.6.1.2.1.10.238.1.5.2.1.1.12,ADSL2-LINE-MIB::adsl2ChConfProfMinProtectionUs,INTEGER,read-create,,current,noProtection(1):halfSymbol(2):singleSymbol(3):twoSymbols(4):threeSymbols(5):fourSymbols(6):fiveSymbols(7):sixSymbols(8):sevenSymbols(9):eightSymbols(10):nineSymbols(11):tenSymbols(12):elevenSymbols(13):twelveSymbols(14):thirteeSymbols(15):fourteenSymbols(16):fifteenSymbols(17):sixteenSymbols(18),Minimum Impulse Noise Protection on Upstream direction. The minimum impulse noise protection for the bearer channel, expressed in symbols. The parameter can take the following values: noProtection (i.e., INP not required), halfSymbol (i.e., INP length is 1/2 symbol), and 1-16 symbols in steps of 1 symbol.
.1.3.6.1.2.1.10.238.1.5.2.1.1.13,ADSL2-LINE-MIB::adsl2ChConfProfMaxBerDs,INTEGER,read-create,,current,eminus3(1):eminus5(2):eminus7(3),Maximum Bit Error Ratio on Downstream direction. The maximum bit error ratio for the bearer channel. The parameter can take the following values (for 1E-3, 1E-5 or 1E-7): eminus3(1), eminus5(2), or eminus7(3).
.1.3.6.1.2.1.10.238.1.5.2.1.1.14,ADSL2-LINE-MIB::adsl2ChConfProfMaxBerUs,INTEGER,read-create,,current,eminus3(1):eminus5(2):eminus7(3),Maximum Bit Error Ratio on Upstream direction. The maximum bit error ratio for the bearer channel. The parameter can take the following values (for 1E-3, 1E-5 or 1E-7): eminus3(1), eminus5(2), or eminus7(3).
.1.3.6.1.2.1.10.238.1.5.2.1.1.15,ADSL2-LINE-MIB::adsl2ChConfProfUsDataRateDs,Unsigned32,read-create,,current,,Data Rate Threshold Up shift for downstream direction. An 'Up-shift rate change' event is triggered when the actual downstream data rate exceeds, by more than the threshold, the data rate at the last entry into Showtime. The parameter is coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.16,ADSL2-LINE-MIB::adsl2ChConfProfDsDataRateDs,Unsigned32,read-create,,current,,Data Rate Threshold Down-shift for downstream direction. A 'Down-shift rate change' event is triggered when the actual downstream data rate is below the data rate at the last entry into Showtime, by more than the threshold. The parameter is coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.17,ADSL2-LINE-MIB::adsl2ChConfProfUsDataRateUs,Unsigned32,read-create,,current,,Data Rate Threshold Up shift for upstream direction. An 'Up-shift rate change' event is triggered when the actual upstream data rate exceeds, by more than the threshold, the data rate at the last entry into Showtime. The parameter is coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.18,ADSL2-LINE-MIB::adsl2ChConfProfDsDataRateUs,Unsigned32,read-create,,current,,Data Rate Threshold Down-shift for upstream direction. A 'Down-shift rate change' event is triggered when the actual upstream data rate is below the data rate at the last entry into Showtime, by more than the threshold. The parameter is coded in bits/second.
.1.3.6.1.2.1.10.238.1.5.2.1.1.19,ADSL2-LINE-MIB::adsl2ChConfProfImaEnabled,INTEGER,read-create,,current,true(1):false(2),IMA Mode Enable. The parameter enables the IMA operation mode in the ATM Data Path. Relevant only if the channel is an ATM Data Path. When in 'enable' state, the ATM data path should comply with the requirements for IMA transmission.
.1.3.6.1.2.1.10.238.1.5.2.1.1.20,ADSL2-LINE-MIB::adsl2ChConfProfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates.
.1.3.6.1.2.1.10.238.1.5.3,ADSL2-LINE-MIB::adsl2ProfileAlarmConf,,,,,,
.1.3.6.1.2.1.10.238.1.5.3.1,ADSL2-LINE-MIB::adsl2LineAlarmConfTemplateTable,,not-accessible,,current,,The table adsl2LineAlarmConfTemplateTable contains ADSL2 line configuration templates. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.3.1.1,ADSL2-LINE-MIB::adsl2LineAlarmConfTemplateEntry,,not-accessible,adsl2LAlarmConfTempTemplateName,current,,The table adsl2LineAlarmConfTemplateTable contains ADSL2 line PM thresholds templates. A default template with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor- specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.238.1.5.3.1.1.1,ADSL2-LINE-MIB::adsl2LAlarmConfTempTemplateName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.238.1.5.3.1.1.2,ADSL2-LINE-MIB::adsl2LAlarmConfTempLineProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Line Thresholds Configuration Profile Table (adsl2LineAlarmConfProfileTable) that applies to this ADSL2 line.
.1.3.6.1.2.1.10.238.1.5.3.1.1.3,ADSL2-LINE-MIB::adsl2LAlarmConfTempChan1ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Thresholds Configuration Profile Table (adsl2ChAlarmConfProfileTable) that applies for ADSL2 bearer channel #1. The channel profile name specified here must match the name of an existing row in the adsl2ChAlarmConfProfileTable table.
.1.3.6.1.2.1.10.238.1.5.3.1.1.4,ADSL2-LINE-MIB::adsl2LAlarmConfTempChan2ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Thresholds Configuration Profile Table (adsl2ChAlarmConfProfileTable) that applies for ADSL2 bearer channel #2. The channel profile name specified here must match the name of an existing row in the adsl2ChAlarmConfProfileTable table. If the channel is unused, then the object is set to a zero-length string.
.1.3.6.1.2.1.10.238.1.5.3.1.1.5,ADSL2-LINE-MIB::adsl2LAlarmConfTempChan3ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Thresholds Configuration Profile Table (adsl2ChAlarmConfProfileTable) that applies for ADSL2 bearer channel #3. The channel profile name specified here must match the name of an existing row in the adsl2ChAlarmConfProfileTable table. This object may be set to a non-zero-length string only if adsl2LAlarmConfTempChan2ConfProfile contains a non-zero- length string.
.1.3.6.1.2.1.10.238.1.5.3.1.1.6,ADSL2-LINE-MIB::adsl2LAlarmConfTempChan4ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the ADSL2 Channel Thresholds Configuration Profile Table (adsl2ChAlarmConfProfileTable) that applies for ADSL2 bearer channel #4. The channel profile name specified here must match the name of an existing row in the adsl2ChAlarmConfProfileTable table. This object may be set to a non-zero-length string only if adsl2LAlarmConfTempChan3ConfProfile contains a non-zero- length string.
.1.3.6.1.2.1.10.238.1.5.3.1.1.7,ADSL2-LINE-MIB::adsl2LAlarmConfTempRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A template is activated by setting this object to 'active'. When 'active' is set, the system will validate the template. Before a template can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated lines.
.1.3.6.1.2.1.10.238.1.5.3.2,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileTable,,not-accessible,,current,,The table adsl2LineAlarmConfProfileTable contains ADSL2 line PM thresholds profiles. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.3.2.1,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileEntry,,not-accessible,adsl2LineAlarmConfProfileName,current,,The table adsl2LineAlarmConfProfileTable contains ADSL2 line PM thresholds profiles. A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor- specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.238.1.5.3.2.1.1,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.238.1.5.3.2.1.2,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAtucThresh15MinFecs,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MFecs counter, when adsl2PMLCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.3,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAtucThresh15MinEs,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MEs counter, when adsl2PMLCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.4,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAtucThresh15MinSes,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MSes counter, when adsl2PMLCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.5,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAtucThresh15MinLoss,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MLoss counter, when adsl2PMLCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.6,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAtucThresh15MinUas,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MUas counter, when adsl2PMLCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.7,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAturThresh15MinFecs,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MFecs counter, when adsl2PMLCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.8,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAturThresh15MinEs,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MEs counter, when adsl2PMLCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.9,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAturThresh15MinSes,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MSes counter, when adsl2PMLCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.10,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAturThresh15MinLoss,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MLoss counter, when adsl2PMLCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.11,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileAturThresh15MinUas,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurr15MUas counter, when adsl2PMLCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.12,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileThresh15MinFailedFullInt,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurrInit15MfailedFullInits counter. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.13,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileThresh15MinFailedShrtInt,Unsigned32,read-create,,current,,A threshold for the adsl2PMLCurrInit15MFailedShortInits counter. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.2.1.14,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates.
.1.3.6.1.2.1.10.238.1.5.3.3,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileTable,,not-accessible,,current,,The table adsl2ChAlarmConfProfileTable contains ADSL2 channel PM thresholds profiles. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.238.1.5.3.3.1,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileEntry,,not-accessible,adsl2ChAlarmConfProfileName,current,,The table adsl2ChAlarmConfProfileTable contains ADSL2 channel PM thresholds profiles. A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor- specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.238.1.5.3.3.1.1,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.238.1.5.3.3.1.2,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileAtucThresh15MinCodingViolations,Unsigned32,read-create,,current,,A threshold for the adsl2PMChCurr15MCodingViolations counter, when adsl2PMChCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.3.1.3,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileAtucThresh15MinCorrected,Unsigned32,read-create,,current,,A threshold for the adsl2PMChCurr15MCorrectedBlocks counter, when adsl2PMChCurrUnit is atuc(1). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.3.1.4,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileAturThresh15MinCodingViolations,Unsigned32,read-create,,current,,A threshold for the adsl2PMChCurr15MCodingViolations counter, when adsl2PMChCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.3.1.5,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileAturThresh15MinCorrected,Unsigned32,read-create,,current,,A threshold for the adsl2PMChCurr15MCorrectedBlocks counter, when adsl2PMChCurrUnit is atur(2). The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.238.1.5.3.3.1.6,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates.
.1.3.6.1.2.1.10.238.1.6,ADSL2-LINE-MIB::adsl2Scalar,,,,,,
.1.3.6.1.2.1.10.238.1.6.1,ADSL2-LINE-MIB::adsl2ScalarSC,,,,,,
.1.3.6.1.2.1.10.238.1.6.1.1,ADSL2-LINE-MIB::adsl2ScalarSCMaxInterfaces,Unsigned32,read-only,,current,,This value determines the upper size of adsl2SCStatusTable. The maximum number of entries in adsl2SCStatusTable is equal to two times the value of this attribute.
.1.3.6.1.2.1.10.238.1.6.1.2,ADSL2-LINE-MIB::adsl2ScalarSCAvailInterfaces,Unsigned32,read-only,,current,,This value determines the amount of space that is currently available in adsl2SCStatusTable. The number of entries available in adsl2SCStatusTable is equal to two times the value of this attribute.
.1.3.6.1.2.1.10.238.1.7,ADSL2-LINE-MIB::adsl2Conformance,,,,,,
.1.3.6.1.2.1.10.238.1.7.1,ADSL2-LINE-MIB::adsl2Groups,,,,,,
.1.3.6.1.2.1.10.238.1.7.1.1,ADSL2-LINE-MIB::adsl2LineGroup,,,,,,The group of configuration, status, and commands objects on the line level.
.1.3.6.1.2.1.10.238.1.7.1.2,ADSL2-LINE-MIB::adsl2ChannelStatusGroup,,,,,,The group of status objects on the channel level.
.1.3.6.1.2.1.10.238.1.7.1.3,ADSL2-LINE-MIB::adsl2ChannelStatusAtmGroup,,,,,,The group of status objects on the data path level when it is ATM.
.1.3.6.1.2.1.10.238.1.7.1.4,ADSL2-LINE-MIB::adsl2ChannelStatusPtmGroup,,,,,,The group of status objects on the data path level when it is PTM.
.1.3.6.1.2.1.10.238.1.7.1.5,ADSL2-LINE-MIB::adsl2SCStatusGroup,,,,,,The group of status objects on the sub-carrier level. They are updated as a result of a DELT process.
.1.3.6.1.2.1.10.238.1.7.1.6,ADSL2-LINE-MIB::adsl2LineInventoryGroup,,,,,,The group of inventory objects per XTU.
.1.3.6.1.2.1.10.238.1.7.1.7,ADSL2-LINE-MIB::adsl2LineConfTemplateGroup,,,,,,The group of objects in a line configuration template.
.1.3.6.1.2.1.10.238.1.7.1.8,ADSL2-LINE-MIB::adsl2LineConfProfGroup,,,,,,The group of objects in a line configuration profile.
.1.3.6.1.2.1.10.238.1.7.1.9,ADSL2-LINE-MIB::adsl2LineConfProfRaGroup,,,,,,The group of objects required for controlling the rate- adaptive behavior of the line.
.1.3.6.1.2.1.10.238.1.7.1.10,ADSL2-LINE-MIB::adsl2LineConfProfMsgMinGroup,,,,,,The group of objects required for controlling the rate reserved for Overhead traffic.
.1.3.6.1.2.1.10.238.1.7.1.11,ADSL2-LINE-MIB::adsl2LineConfProfModeSpecGroup,,,,,,The group of objects in a line configuration profile that have an instance for each operation mode allowed.
.1.3.6.1.2.1.10.238.1.7.1.12,ADSL2-LINE-MIB::adsl2ChConfProfileGroup,,,,,,The group of objects in a channel configuration profile.
.1.3.6.1.2.1.10.238.1.7.1.13,ADSL2-LINE-MIB::adsl2ChConfProfileAtmGroup,,,,,,The group of configuration objects required when the data path is ATM.
.1.3.6.1.2.1.10.238.1.7.1.14,ADSL2-LINE-MIB::adsl2ChConfProfileMinResGroup,,,,,,The group of configuration objects required for the reserved data rate.
.1.3.6.1.2.1.10.238.1.7.1.15,ADSL2-LINE-MIB::adsl2LineAlarmConfTemplateGroup,,,,,,The group of objects in a line alarm template.
.1.3.6.1.2.1.10.238.1.7.1.16,ADSL2-LINE-MIB::adsl2LineAlarmConfProfileGroup,,,,,,The group of objects in a line alarm profile.
.1.3.6.1.2.1.10.238.1.7.1.17,ADSL2-LINE-MIB::adsl2ChAlarmConfProfileGroup,,,,,,The group of objects in a channel alarm profile.
.1.3.6.1.2.1.10.238.1.7.1.18,ADSL2-LINE-MIB::adsl2PMLineCurrGroup,,,,,,The group of objects that report the line-level counters for current PM intervals.
.1.3.6.1.2.1.10.238.1.7.1.19,ADSL2-LINE-MIB::adsl2PMLineCurrInitGroup,,,,,,The group of objects that report the full initialization counters for current PM intervals.
.1.3.6.1.2.1.10.238.1.7.1.20,ADSL2-LINE-MIB::adsl2PMLineCurrInitShortGroup,,,,,,The group of objects that report the short initialization counters for current PM intervals.
.1.3.6.1.2.1.10.238.1.7.1.21,ADSL2-LINE-MIB::adsl2PMLineHist15MinGroup,,,,,,The group of line-level PM counters for the previous 15-minute interval.
.1.3.6.1.2.1.10.238.1.7.1.22,ADSL2-LINE-MIB::adsl2PMLineHist1DayGroup,,,,,,The group of line-level PM counters for the previous 24-hour interval.
.1.3.6.1.2.1.10.238.1.7.1.23,ADSL2-LINE-MIB::adsl2PMLineInitHist15MinGroup,,,,,,The group of PM counters for the previous 15-minute interval's full initializations.
.1.3.6.1.2.1.10.238.1.7.1.24,ADSL2-LINE-MIB::adsl2PMLineInitHist15MinShortGroup,,,,,,The group of PM counters for the previous 15-minute interval's short initializations.
.1.3.6.1.2.1.10.238.1.7.1.25,ADSL2-LINE-MIB::adsl2PMLineInitHist1DayGroup,,,,,,The group of PM counters for the previous 24-hour interval's full initializations.
.1.3.6.1.2.1.10.238.1.7.1.26,ADSL2-LINE-MIB::adsl2PMLineInitHist1DayShortGroup,,,,,,The group of PM counters for the previous 24-hour interval's short initializations.
.1.3.6.1.2.1.10.238.1.7.1.27,ADSL2-LINE-MIB::adsl2PMChCurrGroup,,,,,,The group of objects that report the channel-level counters for current PM intervals.
.1.3.6.1.2.1.10.238.1.7.1.28,ADSL2-LINE-MIB::adsl2PMChHist15MinGroup,,,,,,The group of objects that report the channel-level counters for previous 15-minute PM intervals.
.1.3.6.1.2.1.10.238.1.7.1.29,ADSL2-LINE-MIB::adsl2PMChHist1DGroup,,,,,,The group of objects that report the channel-level counters for previous 24-hour PM intervals.
.1.3.6.1.2.1.10.238.1.7.1.30,ADSL2-LINE-MIB::adsl2ScalarSCGroup,,,,,,The group of objects that report the available memory resources for DELT processes.
.1.3.6.1.2.1.10.238.1.7.1.31,ADSL2-LINE-MIB::adsl2ThreshNotificationGroup,,,,,,This group supports notifications of significant conditions associated with ADSL/ADSL2/ADSL2+ lines.
.1.3.6.1.2.1.10.238.1.7.1.32,ADSL2-LINE-MIB::adsl2StatusChangeNotificationGroup,,,,,,This group supports notifications of threshold crossing associated with ADSL/ADSL2/ADSL2+ lines.
.1.3.6.1.2.1.10.238.1.7.2,ADSL2-LINE-MIB::adsl2Compliances,,,,,,
.1.3.6.1.2.1.10.238.1.7.2.1,ADSL2-LINE-MIB::adsl2LineMibCompliance,,,,,,The compliance statement for SNMP entities that manage ADSL/ADSL2 or ADSL2+ interfaces.
.1.3.6.1.2.1.10.238.2,ADSL2-LINE-TC-MIB::adsl2TCMIB,,,,,,This MIB Module provides Textual Conventions to be used by the ADSL2-LINE-MIB module for the purpose of managing ADSL, ADSL2, and ADSL2+ lines. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4706: see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.239,DVB-RCS-MIB::dvbRcsMib,,,,,,DVB-RCS MIB subtree. This MIB module applies to equipment that is a Return Channel Satellite Terminal (RCST), defined in the Digital Video Broadcasting Return Channel via Satellite system (DVB-RCS) standard (ETSI EN 301 790 Digital Video Broadcasting (DVB); Interaction Channel for Satellite Distribution Systems, European Telecommunications Standards Institute (ETSI)). It defines a set of MIB objects to characterize the behavior and performance of network-layer entities implementing DVB-RCS. This MIB module is intended to be used by DVB-RCS equipment following the SatLabs System Recommendations, defined by the SatLabs Group and available at www.satlabs.org. Note that, if not stated otherwise in the objectclause, all writable objects are persistent. Copyright (C) The IETF Trust (2010). This version of this MIB module is part of RFC 5728; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.239.1,DVB-RCS-MIB::dvbRcsMibObjects,,,,,,
.1.3.6.1.2.1.10.239.1.1,DVB-RCS-MIB::dvbRcsRcst,,,,,,
.1.3.6.1.2.1.10.239.1.1.1,DVB-RCS-MIB::dvbRcsRcstSystem,,,,,,
.1.3.6.1.2.1.10.239.1.1.1.1,DVB-RCS-MIB::dvbRcsSystemMibRevision,OCTET,read-only,,current,,This object allows the SNMP agent to report the implemented MIB module revision. The supported REVISION of this module is reported.
.1.3.6.1.2.1.10.239.1.1.1.2,DVB-RCS-MIB::dvbRcsSystemSatLabsProfilesDeclaration,BITS,read-only,,current,dvbs(0):dvbs2ccm(1):dvbs2acm(2):spare1(3):spare2(4):spare3(5):spare4(6):spare5(7):spare6(8):spare7(9):spare8(10):spare9(11):spare10(12):spare11(13):spare12(14):spare13(15):spare14(16):spare15(17):spare16(18):spare17(19):spare18(20):spare19(21):spare20(22):spare21(23):spare22(24):spare23(25):spare24(26):spare25(27):spare26(28):spare27(29):spare28(30):spare29(31),Indicates the SatLabs profiles supported, as defined in the SatLabs System Recommendations.
.1.3.6.1.2.1.10.239.1.1.1.3,DVB-RCS-MIB::dvbRcsSystemSatLabsOptionsDeclaration,BITS,read-only,,current,mpegTrf(0):coarseSync(1):wideHop(2):fastHop(3):dynamicMfTdma(4):contentionSync(5):qpskLow(6):mod16Apsk(7):mod32Apsk(8):normalFec(9):multiTs(10):gsTs(11):enhQoS(12):pep(13):http(14):ftp(15):dns(16):chIdStrict(17):nlid(18):snmpMisc(19):spare1(20):spare2(21):spare3(22):spare4(23):spare5(24):spare6(25):spare7(26):spare8(27):spare9(28):spare10(29):spare11(30):spare12(31),Indicates the SatLabs options supported, as defined in the SatLabs System Recommendations.
.1.3.6.1.2.1.10.239.1.1.1.4,DVB-RCS-MIB::dvbRcsSystemSatLabsFeaturesDeclaration,BITS,read-only,,current,rcstPara(0):installLog(1):enhClassifier(2):routeId(3):oduList(4):extNetwork(5):extControl(6):extConfig(7):extStatus(8):mpaf(9):spare1(10):spare2(11):spare3(12):spare4(13):spare5(14):spare6(15):spare7(16):spare8(17):spare9(18):spare10(19):spare11(20):spare12(21):spare13(22):spare14(23):spare15(24):spare16(25):spare17(26):spare18(27):spare19(28):spare20(29):spare21(30):spare22(31),Indicates the optional compatibility features and minor options supported, as defined in the SatLabs System Recommendations.
.1.3.6.1.2.1.10.239.1.1.1.5,DVB-RCS-MIB::dvbRcsSystemLocation,OCTET,read-write,,current,,Physical location of the ODU antenna expressed as longitude, latitude, and altitude. The string shall have 31 characters in the following format: <xxxx.xxx>,<a>,<yyyyy.yyy>,<b>,<zzzz.z>,M where x, y and z represents digits, a=N or S, b=E or W, Reading the digits from left to right: 'x' 7 latitude digits; x digits 1-2 contain the degrees, x digits 3-7 contain the minutes in decimal; 'y' 8 longitude digits; y digits 1-3 contain the degrees, y digits 4-8 contain the minutes in decimal; 'z' 5 altitude digits; meters above sea level in decimal; '.' is the decimal point; ',' is the field separator; 'M' is the indicator for altitude meters. This format is a modified subset of the NMEA 0183 (National Marine Electronics Association, Interface Standard) format for Global Positioning System Fix Data. This location and the satellite position are used to calculate the RCST-satellite path delay. Note: The system.sysLocation object of MIB-II provides physical location of the IDU unit.
.1.3.6.1.2.1.10.239.1.1.1.6,DVB-RCS-MIB::dvbRcsSystemOduAntennaSize,Unsigned32,read-write,,current,,Diameter of the antenna.
.1.3.6.1.2.1.10.239.1.1.1.7,DVB-RCS-MIB::dvbRcsSystemOduAntennaGain,Unsigned32,read-write,,current,,Antenna peak gain of the ODU.
.1.3.6.1.2.1.10.239.1.1.1.8,DVB-RCS-MIB::dvbRcsSystemOduSspa,Unsigned32,read-write,,current,,Power level of the Solid State Power Amplifier installed in the ODU.
.1.3.6.1.2.1.10.239.1.1.1.9,DVB-RCS-MIB::dvbRcsSystemOduTxType,OCTET,read-write,,current,,Type of transmitter installed in the ODU.
.1.3.6.1.2.1.10.239.1.1.1.10,DVB-RCS-MIB::dvbRcsSystemOduRxType,OCTET,read-write,,current,,Type of LNB installed in the ODU, with information such as vendor type, output type (single, twin, quad,...), etc.
.1.3.6.1.2.1.10.239.1.1.1.11,DVB-RCS-MIB::dvbRcsSystemOduRxBand,INTEGER,read-write,,current,oduHighRxBand(0):oduLowRxBand(1),LNB High Band / Low Band selector. High Band corresponds to the emission of an 18-26 kHz tone with 0.4-0.8 Vpp in the Rx IFL cable: (0) - High Band (1) - Low Band
.1.3.6.1.2.1.10.239.1.1.1.12,DVB-RCS-MIB::dvbRcsSystemOduRxLO,Unsigned32,read-write,,current,,Frequency of LNB Local Oscillator (in 100 Hz)
.1.3.6.1.2.1.10.239.1.1.1.13,DVB-RCS-MIB::dvbRcsSystemOduTxLO,Unsigned32,read-write,,current,,Frequency of Block Up-Converter Local Oscillator (in 100 Hz).
.1.3.6.1.2.1.10.239.1.1.1.14,DVB-RCS-MIB::dvbRcsSystemIduPep,,,,,,
.1.3.6.1.2.1.10.239.1.1.1.14.1,DVB-RCS-MIB::dvbRcsTcpPep,INTEGER,read-write,,current,disabled(0):enabled(1),Status and control of embedded TCP PEP. 0 - disabled or not implemented 1 - enabled
.1.3.6.1.2.1.10.239.1.1.1.14.2,DVB-RCS-MIB::dvbRcsHttpPep,INTEGER,read-write,,current,disabled(0):enabled(1),Status and control of embedded HTTP PEP. 0 - disabled or not implemented 1 - enabled
.1.3.6.1.2.1.10.239.1.1.1.15,DVB-RCS-MIB::dvbRcsOduTx,,,,,,
.1.3.6.1.2.1.10.239.1.1.1.15.1,DVB-RCS-MIB::dvbRcsOduTxTypeTable,,not-accessible,,current,,This table contains the identification of each well- known BUC type supported by the IDU and provides its associated index.
.1.3.6.1.2.1.10.239.1.1.1.15.1.1,DVB-RCS-MIB::dvbRcsOduTxTypeEntry,,not-accessible,dvbRcsOduTxTypeIndex,current,,An entry in the BUC type table.
.1.3.6.1.2.1.10.239.1.1.1.15.1.1.1,DVB-RCS-MIB::dvbRcsOduTxTypeIndex,Unsigned32,not-accessible,,current,,Index for the BUC type.
.1.3.6.1.2.1.10.239.1.1.1.15.1.1.2,DVB-RCS-MIB::dvbRcsOduTxTypeDescription,OCTET,read-only,,current,,Text-based identification of a BUC type.
.1.3.6.1.2.1.10.239.1.1.1.15.2,DVB-RCS-MIB::dvbRcsOduTxType,Unsigned32,read-write,,current,,Index of the selected BUC type.
.1.3.6.1.2.1.10.239.1.1.1.16,DVB-RCS-MIB::dvbRcsOduRx,,,,,,
.1.3.6.1.2.1.10.239.1.1.1.16.1,DVB-RCS-MIB::dvbRcsOduRxTypeTable,,not-accessible,,current,,This table contains the identification of each well- known LNB type supported by the IDU and provides its associated index.
.1.3.6.1.2.1.10.239.1.1.1.16.1.1,DVB-RCS-MIB::dvbRcsOduRxTypeEntry,,not-accessible,dvbRcsOduRxTypeIndex,current,,An entry in the LNB type table.
.1.3.6.1.2.1.10.239.1.1.1.16.1.1.1,DVB-RCS-MIB::dvbRcsOduRxTypeIndex,Unsigned32,not-accessible,,current,,Index for the LNB type.
.1.3.6.1.2.1.10.239.1.1.1.16.1.1.2,DVB-RCS-MIB::dvbRcsOduRxTypeDescription,OCTET,read-only,,current,,Text-based identification of an LNB type.
.1.3.6.1.2.1.10.239.1.1.1.16.2,DVB-RCS-MIB::dvbRcsOduRxType,Unsigned32,read-write,,current,,Index of the selected LNB type.
.1.3.6.1.2.1.10.239.1.1.1.17,DVB-RCS-MIB::dvbRcsOduAntenna,,,,,,
.1.3.6.1.2.1.10.239.1.1.1.17.1,DVB-RCS-MIB::dvbRcsOduAntennaTypeTable,,not-accessible,,current,,This table contains the identification of each well- known antenna type supported by the IDU and provides its associated index.
.1.3.6.1.2.1.10.239.1.1.1.17.1.1,DVB-RCS-MIB::dvbRcsOduAntennaTypeEntry,,not-accessible,dvbRcsOduAntennaTypeIndex,current,,An entry in the antenna type table.
.1.3.6.1.2.1.10.239.1.1.1.17.1.1.1,DVB-RCS-MIB::dvbRcsOduAntennaTypeIndex,Unsigned32,not-accessible,,current,,Index for the antenna type.
.1.3.6.1.2.1.10.239.1.1.1.17.1.1.2,DVB-RCS-MIB::dvbRcsOduAntennaTypeDescription,OCTET,read-only,,current,,Text-based identification of an antenna type.
.1.3.6.1.2.1.10.239.1.1.1.17.2,DVB-RCS-MIB::dvbRcsOduAntennaType,Unsigned32,read-write,,current,,Index of the selected antenna type.
.1.3.6.1.2.1.10.239.1.1.2,DVB-RCS-MIB::dvbRcsRcstNetwork,,,,,,
.1.3.6.1.2.1.10.239.1.1.2.1,DVB-RCS-MIB::dvbRcsNetworkOamInetAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsNetworkOamInetAddress. If the terminal OAM Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.2.2,DVB-RCS-MIB::dvbRcsNetworkOamInetAddress,OCTET,read-write,,current,,OAM IP Address of the RCST. This object is used with both IP and interfaces MIB-II subgroups. It uniquely determines the interface through which OAM traffic passes. The OAM IP address may be statically or dynamically assigned. It is system dependent whether the OAM IP address and the Traffic IP address are the same address. If the terminal has no OAM Internet address assigned or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsNetworkOamInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.2.3,DVB-RCS-MIB::dvbRcsNetworkOamInetAddressPrefixLength,Unsigned32,read-write,,current,,Prefix length for the OAM IP Address. If this address prefix is unknown or does not apply, the value is zero.
.1.3.6.1.2.1.10.239.1.1.2.4,DVB-RCS-MIB::dvbRcsNetworkOamInetAddressAssign,INTEGER,read-write,,current,oamInetAddressStatic(1):oamInetAddressDynamic(2),Identifies whether the OAM IP address is statically (1) or dynamically (2) assigned.
.1.3.6.1.2.1.10.239.1.1.2.5,DVB-RCS-MIB::dvbRcsNetworkLanInetAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsNetworkLanInetAddress. If the terminal Internet address on the LAN interface is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.2.6,DVB-RCS-MIB::dvbRcsNetworkLanInetAddress,OCTET,read-write,,current,,IP address of the LAN interface of the terminal. If the terminal has no Internet address assigned on the LAN interface or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsNetworkLanInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.2.7,DVB-RCS-MIB::dvbRcsNetworkLanInetAddressPrefixLength,Unsigned32,read-write,,current,,Prefix length for the LAN IP Address of the terminal. If this address prefix is unknown or does not apply, the value is zero.
.1.3.6.1.2.1.10.239.1.1.2.8,DVB-RCS-MIB::dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress. If the default gateway Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.2.9,DVB-RCS-MIB::dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress,OCTET,read-write,,current,,IP address of the default gateway for the air interface. If the terminal has no default gateway assigned on the air interface or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.2.10,DVB-RCS-MIB::dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressPrefixLength,Unsigned32,read-write,,current,,Prefix length for the IP address of the default gateway for the air interface. If this address prefix is unknown or does not apply, the value is zero.
.1.3.6.1.2.1.10.239.1.1.2.11,DVB-RCS-MIB::dvbRcsNetworkDnsServers,,,,,,
.1.3.6.1.2.1.10.239.1.1.2.11.1,DVB-RCS-MIB::dvbRcsPrimaryDnsServerInetAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsPrimaryDnsServerInetAddress. If the primary DNS server Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.2.11.2,DVB-RCS-MIB::dvbRcsPrimaryDnsServerInetAddress,OCTET,read-write,,current,,IP address of the primary DNS server in the NCC. If the terminal has no primary DNS server assigned or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsPrimaryDnsServerInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.2.11.3,DVB-RCS-MIB::dvbRcsPrimaryDnsServerInetAddressPrefixLength,Unsigned32,read-write,,current,,Prefix length for the IP address of the primary DNS server in the NCC. If this address prefix is unknown or does not apply, the value is zero.
.1.3.6.1.2.1.10.239.1.1.2.11.4,DVB-RCS-MIB::dvbRcsSecondaryDnsServerInetAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsSecondaryDnsServerInetAddress. If the secondary DNS server Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.2.11.5,DVB-RCS-MIB::dvbRcsSecondaryDnsServerInetAddress,OCTET,read-write,,current,,IP address of the secondary DNS server in the NCC. If the terminal has no secondary DNS server assigned or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsSecondaryDnsServerInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.2.11.6,DVB-RCS-MIB::dvbRcsSecondaryDnsServerInetAddressPrefixLength,Unsigned32,read-write,,current,,Prefix length for the IP address of the secondary DNS server in the NCC. If this address prefix is unknown or does not apply, the value is zero.
.1.3.6.1.2.1.10.239.1.1.2.12,DVB-RCS-MIB::dvbRcsNetworkNccMgtInetAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsNetworkNccMgtInetAddress. If the management server Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.2.13,DVB-RCS-MIB::dvbRcsNetworkNccMgtInetAddress,OCTET,read-write,,current,,IP address of the management server in the NCC. If the terminal has no management server assigned or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsNetworkNccMgtInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.2.14,DVB-RCS-MIB::dvbRcsNetworkNccMgtInetAddressPrefixLength,Unsigned32,read-write,,current,,Prefix length for the IP address of the management server in the NCC. If this address prefix is unknown or does not apply, the value is zero.
.1.3.6.1.2.1.10.239.1.1.2.15,DVB-RCS-MIB::dvbRcsNetworkConfigFileDownloadUrl,OCTET,read-write,,current,,Full path name for the configuration file download. It includes the protocol type (TFTP or FTP) and the associated server IP address or hostname. Hostname can only be used if DNS is supported by the RCST. The format of this parameter follows RFC 3986.
.1.3.6.1.2.1.10.239.1.1.2.16,DVB-RCS-MIB::dvbRcsNetworkInstallLogFileDownloadUrl,OCTET,read-write,,current,,Full path of the installation log file to download. It includes the protocol type (TFTP or FTP) and the associated server IP address or hostname. Hostname can only be used if DNS is supported by the RCST. The installation log file can be created on the installer's computer and downloaded to the RCST. The format of this parameter follows RFC 3986.
.1.3.6.1.2.1.10.239.1.1.2.17,DVB-RCS-MIB::dvbRcsNetworkConfigFileUploadUrl,OCTET,read-write,,current,,Full path name for the configuration file upload. It includes the protocol type (TFTP or FTP) and the associated server IP address or hostname. Hostname can only be used if DNS is supported by the RCST. The format of this parameter follows RFC 3986.
.1.3.6.1.2.1.10.239.1.1.2.18,DVB-RCS-MIB::dvbRcsNetworkLogFileUploadUrl,OCTET,read-write,,current,,Full path of the event log file. It includes the protocol type (TFTP or FTP) and the associated server IP address or hostname. Hostname can only be used if DNS is supported by the RCST. The format of this parameter follows RFC 3986.
.1.3.6.1.2.1.10.239.1.1.2.19,DVB-RCS-MIB::dvbRcsNetworkInstallLogFileUploadUrl,OCTET,read-write,,current,,Full path of the installation log file. It includes the protocol type (TFTP or FTP) and the associated server IP address or hostname. Hostname can only be used if DNS is supported by the RCST. The installation log file can be retrieved from the RCST by the NCC or by the installer via the LAN. The format of this parameter follows RFC 3986.
.1.3.6.1.2.1.10.239.1.1.3,DVB-RCS-MIB::dvbRcsRcstInstall,,,,,,
.1.3.6.1.2.1.10.239.1.1.3.1,DVB-RCS-MIB::dvbRcsInstallAntennaAlignmentState,INTEGER,read-write,,current,antennaAlignmentStart(1):antennaAlignmentDeny(2):antennaAlignmentContinue(3):antennaAlignmentStop(4):antennaAlignmentSuccess(5):antennaAlignmentFail(6),Indicates the alignment state of the antenna: (1)-Start; (2)-Deny; (3)-Continue; (4)-Stop; (5)-Success; (6)-Fail
.1.3.6.1.2.1.10.239.1.1.3.2,DVB-RCS-MIB::dvbRcsInstallCwFrequency,Unsigned32,read-write,,current,,Frequency of the transmitted Continuous Wave carrier (in 100 Hz). Minimum required precision is 1 kHz.
.1.3.6.1.2.1.10.239.1.1.3.3,DVB-RCS-MIB::dvbRcsInstallCwMaxDuration,Unsigned32,read-write,,current,,Time after which the Continuous Wave carrier must be put down (in seconds).
.1.3.6.1.2.1.10.239.1.1.3.4,DVB-RCS-MIB::dvbRcsInstallCwPower,Integer32,read-write,,current,,IDU TX output level when the IDU is configured to send CW. The resolution is 0.1 dBm and the accuracy is +/- 1 dBm. Reconfiguration is applied immediately to a CW.
.1.3.6.1.2.1.10.239.1.1.3.5,DVB-RCS-MIB::dvbRcsInstallCoPolReading,Unsigned32,read-write,,current,,Co-polarization measured value during installation procedure (in 0.1 dB).
.1.3.6.1.2.1.10.239.1.1.3.6,DVB-RCS-MIB::dvbRcsInstallXPolReading,Unsigned32,read-write,,current,,Cross-polarization measured value during installation procedure (in 0.1 dB).
.1.3.6.1.2.1.10.239.1.1.3.7,DVB-RCS-MIB::dvbRcsInstallCoPolTarget,Unsigned32,read-write,,current,,Co-polarization target value during installation procedure (in 0.1 dB).
.1.3.6.1.2.1.10.239.1.1.3.8,DVB-RCS-MIB::dvbRcsInstallXPolTarget,Unsigned32,read-write,,current,,Cross-polarization target value during installation procedure (in 0.1 dB).
.1.3.6.1.2.1.10.239.1.1.3.9,DVB-RCS-MIB::dvbRcsInstallStandByDuration,Unsigned32,read-write,,current,,Time to wait in stand-by mode (in seconds).
.1.3.6.1.2.1.10.239.1.1.3.10,DVB-RCS-MIB::dvbRcsInstallTargetEsN0,Unsigned32,read-write,,current,,This value describes the wanted Es/N0 value that enables operation of the return link with the required error performance. The values shall be given in tenth of dB and the initial value shall be equal to 7 dB. The range shall be from 0 dB to 31.5 dB, with a precision of 0.1 dB.
.1.3.6.1.2.1.10.239.1.1.4,DVB-RCS-MIB::dvbRcsRcstQos,,,,,,
.1.3.6.1.2.1.10.239.1.1.4.1,DVB-RCS-MIB::dvbRcsPktClassTable,,not-accessible,,current,,This table describes the packet classification used in the DVB-RCS terminal. The number of entries is specified by dvbRcsPktClassIndex. 
.1.3.6.1.2.1.10.239.1.1.4.1.1,DVB-RCS-MIB::dvbRcsPktClassEntry,,not-accessible,dvbRcsPktClassIndex,current,,An entry in the packet classification table. One object type of each entry may have a value in the active range (a non-default value). The other object types are then assumed to be set to 'inactive'. The entry with the lowest index value takes precedence when classifying a packet.
.1.3.6.1.2.1.10.239.1.1.4.1.1.1,DVB-RCS-MIB::dvbRcsPktClassIndex,Unsigned32,not-accessible,,current,,Index automatically incremented by one at row creation.
.1.3.6.1.2.1.10.239.1.1.4.1.1.2,DVB-RCS-MIB::dvbRcsPktClassDscpLow,Integer32,read-create,,current,,This object specifies the low value of a range of Diffserv Code Point (DSCP) values to which a packet is compared.
.1.3.6.1.2.1.10.239.1.1.4.1.1.3,DVB-RCS-MIB::dvbRcsPktClassDscpHigh,Integer32,read-create,,current,,This object specifies the high value of a range of Diffserv Code Point (DSCP) values to which a packet is compared.
.1.3.6.1.2.1.10.239.1.1.4.1.1.4,DVB-RCS-MIB::dvbRcsPktClassDscpMarkValue,Integer32,read-create,,current,,This object is the Diffserv Code Point (DSCP) value used to mark the packet; -1 indicates no DSCP marking. Possible DSCP marks values are (0..63)
.1.3.6.1.2.1.10.239.1.1.4.1.1.5,DVB-RCS-MIB::dvbRcsPktClassIpProtocol,Unsigned32,read-create,,current,,This object specifies the IP protocol to which a packet is compared. A value of 255 means match all.
.1.3.6.1.2.1.10.239.1.1.4.1.1.6,DVB-RCS-MIB::dvbRcsPktClassSrcInetAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsPktClassSrcInetAddress. If the packet class source Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.4.1.1.7,DVB-RCS-MIB::dvbRcsPktClassSrcInetAddress,OCTET,read-create,,current,,This object specifies the IP source address to which a packet is compared. If the packet class has no source Internet address assigned or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsPktClassSrcInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.4.1.1.8,DVB-RCS-MIB::dvbRcsPktClassSrcInetAddressPrefixLength,Unsigned32,read-create,,current,,Prefix length of the IP source address that will be matched for this packet class. A value of zero indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.9,DVB-RCS-MIB::dvbRcsPktClassDstInetAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of dvbRcsPktClassDstInetAddress. If the packet class destination Internet address is unassigned or unknown, then the value of this object is unknown(0).
.1.3.6.1.2.1.10.239.1.1.4.1.1.10,DVB-RCS-MIB::dvbRcsPktClassDstInetAddress,OCTET,read-create,,current,,This object specifies the IP destination address to which a packet is compared. If the packet class has no destination Internet address assigned or if this Internet address is unknown, the value of this object is the zero-length OCTET STRING. The InetAddressType is given by the dvbRcsPktClassDstInetAddressType object.
.1.3.6.1.2.1.10.239.1.1.4.1.1.11,DVB-RCS-MIB::dvbRcsPktClassDstInetAddressPrefixLength,Unsigned32,read-create,,current,,Prefix length of the IP source address that will be matched for this packet class. A value of zero indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.12,DVB-RCS-MIB::dvbRcsPktClassSrcPortLow,Unsigned32,read-create,,current,,This object specifies the low range of the source port to which a packet is compared. A value of 0 indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.13,DVB-RCS-MIB::dvbRcsPktClassSrcPortHigh,Unsigned32,read-create,,current,,This object specifies the high range of the source port to which a packet is compared. A value of 0 indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.14,DVB-RCS-MIB::dvbRcsPktClassDstPortLow,Unsigned32,read-create,,current,,This object specifies the low range of the destination port to which a packet is compared. A value of 0 indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.15,DVB-RCS-MIB::dvbRcsPktClassDstPortHigh,Unsigned32,read-create,,current,,This object specifies the high range of the destination port to which a packet is compared. A value of 0 indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.16,DVB-RCS-MIB::dvbRcsPktClassVlanUserPri,Integer32,read-create,,current,,This object specifies the VLAN User Priority to which a packet is compared. A value of -1 indicates that the selectivity is inactive.
.1.3.6.1.2.1.10.239.1.1.4.1.1.17,DVB-RCS-MIB::dvbRcsPktClassPhbAssociation,Unsigned32,read-create,,current,,Associate the filter entry to a specific PHB (refer to dvbRcsPhbIdentifier).
.1.3.6.1.2.1.10.239.1.1.4.1.1.18,DVB-RCS-MIB::dvbRcsPktClassRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time.
.1.3.6.1.2.1.10.239.1.1.4.2,DVB-RCS-MIB::dvbRcsPhbMappingTable,,not-accessible,,current,,This table is a list of Per-Hop Behavior (PHB) MIB entries. It describes the PHB mapping to the Request Class.
.1.3.6.1.2.1.10.239.1.1.4.2.1,DVB-RCS-MIB::dvbRcsPhbMappingEntry,,not-accessible,dvbRcsPhbIdentifier,current,,An entry in the PHB mapping table.
.1.3.6.1.2.1.10.239.1.1.4.2.1.1,DVB-RCS-MIB::dvbRcsPhbIdentifier,Unsigned32,not-accessible,,current,,Identification of the Per-Hop Behavior (PHB). It follows the unsigned 16-bit binary encoding as specified in RFC 3140. The value 0 designates the Default PHB.
.1.3.6.1.2.1.10.239.1.1.4.2.1.2,DVB-RCS-MIB::dvbRcsPhbName,OCTET,read-create,,current,,The name of the Per-Hop Behavior (PHB).
.1.3.6.1.2.1.10.239.1.1.4.2.1.3,DVB-RCS-MIB::dvbRcsPhbRequestClassAssociation,Unsigned32,read-create,,current,,This object is an association of this Per-Hop Behavior (PHB) to a Request Class (by reference to a Request Class index).
.1.3.6.1.2.1.10.239.1.1.4.2.1.4,DVB-RCS-MIB::dvbRcsPhbMappingRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time.
.1.3.6.1.2.1.10.239.1.1.4.3,DVB-RCS-MIB::dvbRcsRequestClassTable,,not-accessible,,current,,This table is a list of Request Class entries. This class describes the layer 2 QoS objects.
.1.3.6.1.2.1.10.239.1.1.4.3.1,DVB-RCS-MIB::dvbRcsRequestClassEntry,,not-accessible,dvbRcsRequestClassIndex,current,,An entry in the Request Class table.
.1.3.6.1.2.1.10.239.1.1.4.3.1.1,DVB-RCS-MIB::dvbRcsRequestClassIndex,Unsigned32,not-accessible,,current,,Index of the Request Class table. A total of 16 entries are supported.
.1.3.6.1.2.1.10.239.1.1.4.3.1.2,DVB-RCS-MIB::dvbRcsRequestClassName,OCTET,read-create,,current,,Name of the Request Class.
.1.3.6.1.2.1.10.239.1.1.4.3.1.3,DVB-RCS-MIB::dvbRcsRequestClassChanId,Unsigned32,read-create,,current,,Channel ID of the Request Class.
.1.3.6.1.2.1.10.239.1.1.4.3.1.4,DVB-RCS-MIB::dvbRcsRequestClassVccVpi,Unsigned32,read-create,,current,,Defines the VPI used for the Request Class (ATM profile).
.1.3.6.1.2.1.10.239.1.1.4.3.1.5,DVB-RCS-MIB::dvbRcsRequestClassVccVci,Unsigned32,read-create,,current,,Defines the VCI used for the Request Class (ATM profile).
.1.3.6.1.2.1.10.239.1.1.4.3.1.6,DVB-RCS-MIB::dvbRcsRequestClassPidPoolReference,Unsigned32,read-create,,current,,Reference to the Packet IDentifier (PID) pool applicable for the Request Class.
.1.3.6.1.2.1.10.239.1.1.4.3.1.7,DVB-RCS-MIB::dvbRcsRequestClassCra,Unsigned32,read-create,,current,,Defines the Continuous Rate Assignment (CRA) level for the Request Class in bits per second (bit/s).
.1.3.6.1.2.1.10.239.1.1.4.3.1.8,DVB-RCS-MIB::dvbRcsRequestClassRbdcMax,Unsigned32,read-create,,current,,Maximum Rate-Based Dynamic Capacity (RBDC) that can be requested for the Request Class, in number of 2 kbit/s.
.1.3.6.1.2.1.10.239.1.1.4.3.1.9,DVB-RCS-MIB::dvbRcsRequestClassRbdcTimeout,Unsigned32,read-create,,current,,Persistence of the Rate-Based Dynamic Capacity (RBDC) request, expressed in superframes.
.1.3.6.1.2.1.10.239.1.1.4.3.1.10,DVB-RCS-MIB::dvbRcsRequestClassVbdcMax,Unsigned32,read-create,,current,,Maximum Volume-Based Dynamic Capacity (VBDC) that can be allocated to the Request Class, in payload units (one ATM cell or one MPEG packet) per superframe.
.1.3.6.1.2.1.10.239.1.1.4.3.1.11,DVB-RCS-MIB::dvbRcsRequestClassVbdcTimeout,Unsigned32,read-create,,current,,Time after which the RCST considers that the pending requests are lost. The RCST may issue new requests for that traffic. Volume-Based Dynamic Capacity (VBDC) Timeout is expressed in superframes.
.1.3.6.1.2.1.10.239.1.1.4.3.1.12,DVB-RCS-MIB::dvbRcsRequestClassVbdcMaxBackLog,Unsigned32,read-create,,current,,Volume-Based Dynamic Capacity (VBDC) back log per Request Class (expressed in bytes).
.1.3.6.1.2.1.10.239.1.1.4.3.1.13,DVB-RCS-MIB::dvbRcsRequestClassRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. It is not possible to change values in a row of this table while the row is active.
.1.3.6.1.2.1.10.239.1.1.4.4,DVB-RCS-MIB::dvbRcsPidPoolTable,,not-accessible,,current,,This table contains the Packet IDentifier (PID) pools. For the MPEG profile, several Request Classes may be mapped within a pool of several PIDs to allow Section Packing across several Request Classes. A PID value may occur in more than one PID pool. Each PID value can effectively occur only once in each pool.
.1.3.6.1.2.1.10.239.1.1.4.4.1,DVB-RCS-MIB::dvbRcsPidPoolEntry,,not-accessible,dvbRcsPidPoolIndex:dvbRcsPidIndex,current,,An entry in the PID pool table.
.1.3.6.1.2.1.10.239.1.1.4.4.1.1,DVB-RCS-MIB::dvbRcsPidPoolIndex,Unsigned32,not-accessible,,current,,Index of the PID pool in the PID pool table.
.1.3.6.1.2.1.10.239.1.1.4.4.1.2,DVB-RCS-MIB::dvbRcsPidIndex,Unsigned32,not-accessible,,current,,Index of the PID entry within the PID pool.
.1.3.6.1.2.1.10.239.1.1.4.4.1.3,DVB-RCS-MIB::dvbRcsPidValue,Unsigned32,read-create,,current,,Defines one of the PIDs to be used in a PID pool of dvbRcsPidPoolIndex. A PID value may occur in more than one PID pool. Each PID value can effectively occur only once in each pool.
.1.3.6.1.2.1.10.239.1.1.4.4.1.4,DVB-RCS-MIB::dvbRcsPidPoolRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time.
.1.3.6.1.2.1.10.239.1.1.4.5,DVB-RCS-MIB::dvbRcsQosGlobalRbdcMax,Unsigned32,read-write,,current,,Global maximum RBDC that can be requested for the RCST, in number of 2 kbit/s.
.1.3.6.1.2.1.10.239.1.1.4.6,DVB-RCS-MIB::dvbRcsQosGlobalVbdcMax,Unsigned32,read-write,,current,,Global maximum VBDC that can be allocated to the RCST, in payload units (one ATM cell or one MPEG packet) per superframe.
.1.3.6.1.2.1.10.239.1.1.4.7,DVB-RCS-MIB::dvbRcsQosGlobalVbdcMaxBackLog,Unsigned32,read-write,,current,,Global VBDC back log at the RCST level (expressed in bytes). It is used only if the VBDC back log is not configured in the Request Class (expressed in bytes).
.1.3.6.1.2.1.10.239.1.1.4.8,DVB-RCS-MIB::dvbRcsQosChannelIdStrictDispatching,INTEGER,read-write,,current,notStrict(0):strict(1),Indicates whether the RCST will strictly follow RC association when signaled through Channel_ID in the TBTP: (0)- no strict association (1)- strict association
.1.3.6.1.2.1.10.239.1.1.5,DVB-RCS-MIB::dvbRcsRcstControl,,,,,,
.1.3.6.1.2.1.10.239.1.1.5.1,DVB-RCS-MIB::dvbRcsCtrlRebootCommand,INTEGER,read-write,,current,idle(1):normal(2):alternate(3),This variable shall force the RCST to reboot: (1)- idle (2)- normal reboot (from current software load) (3)- reboot from alternate load (swap to alternate load before reboot)
.1.3.6.1.2.1.10.239.1.1.5.2,DVB-RCS-MIB::dvbRcsCtrlRcstTxDisable,INTEGER,read-write,,current,idle(1):disable(2),This variable shall force the RCST to stop transmission (transmit disabled as defined in SatLabs System Recommendations): (1)- idle (2)- initiate Tx Disabled
.1.3.6.1.2.1.10.239.1.1.5.3,DVB-RCS-MIB::dvbRcsCtrlUserTrafficDisable,INTEGER,read-write,,current,idle(1):disable(2),This variable shall disable user traffic (only RCST management traffic can be transmitted): (1)- idle (2)- disable user traffic
.1.3.6.1.2.1.10.239.1.1.5.4,DVB-RCS-MIB::dvbRcsCtrlCwEnable,INTEGER,read-write,,current,off(1):on(2),This variable will force the RCST to start transmission of CW, if the RCST is first set to the installation state and is properly configured for CW transmission: (1)- off (2)- on
.1.3.6.1.2.1.10.239.1.1.5.5,DVB-RCS-MIB::dvbRcsCtrlOduTxReferenceEnable,INTEGER,read-write,,current,off(1):on(2),Enables activation and deactivation of the 10 MHz reference clock in the Tx IFL cable: (1) off (2) on
.1.3.6.1.2.1.10.239.1.1.5.6,DVB-RCS-MIB::dvbRcsCtrlOduTxDCEnable,INTEGER,read-write,,current,off(1):on(2),Enables activation and deactivation of DC in the Tx IFL cable: (1) off (2) on
.1.3.6.1.2.1.10.239.1.1.5.7,DVB-RCS-MIB::dvbRcsCtrlOduRxDCEnable,INTEGER,read-write,,current,off(1):on(2),Enables activation and deactivation of DC in the Rx IFL cable: (1) off (2) on
.1.3.6.1.2.1.10.239.1.1.5.8,DVB-RCS-MIB::dvbRcsCtrlDownloadFileCommand,INTEGER,read-write,,current,idle(1):config(2):installationLog(3),This variable will initiate an RCST configuration file download process: (1) idle (2) download RCST configuration file from TFTP/FTP server (3) download RCST installation log file from TFTP/FTP server (INSTALL_LOG feature)
.1.3.6.1.2.1.10.239.1.1.5.9,DVB-RCS-MIB::dvbRcsCtrlUploadFileCommand,INTEGER,read-write,,current,idle(1):config(2):eventAlarm(3):installationLog(4),This variable will initiate an RCST upload process: (1) idle (2) upload RCST configuration file to TFTP/FTP server (3) upload RCST event/alarm log file to TFTP/FTP server (4) upload RCST installation log file to TFTP/FTP server (INSTALL_LOG feature)
.1.3.6.1.2.1.10.239.1.1.5.10,DVB-RCS-MIB::dvbRcsCtrlActivateConfigFileCommand,INTEGER,read-write,,current,idle(1):activate(2),Triggers the RCST to use the configuration file and update its parameters accordingly. Some RCST implementations may require a reboot for the parameters to take effect (vendor specific). (1) idle (2) activate
.1.3.6.1.2.1.10.239.1.1.5.11,DVB-RCS-MIB::dvbRcsCtrlRcstLogonCommand,INTEGER,read-write,,current,idle(1):logon(2),This variable will initiate an RCST logon: (1) idle (2) initiate RCST logon
.1.3.6.1.2.1.10.239.1.1.5.12,DVB-RCS-MIB::dvbRcsCtrlRcstLogoffCommand,INTEGER,read-write,,current,idle(1):logoff(2),This variable will initiate an RCST logoff: (1) idle (2) initiate RCST logoff
.1.3.6.1.2.1.10.239.1.1.5.13,DVB-RCS-MIB::dvbRcsCtrlRcstRxReacquire,INTEGER,read-write,,current,idle(1):reacquireForwardLink(2),This variable will force the RCST to acquire the forward link and start receiving: (1) idle (2) reacquire forward link
.1.3.6.1.2.1.10.239.1.1.6,DVB-RCS-MIB::dvbRcsRcstState,,,,,,
.1.3.6.1.2.1.10.239.1.1.6.1,DVB-RCS-MIB::dvbRcsRcstMode,INTEGER,read-write,,current,installation(0):operational(1),Identifies the current mode of the RCST and allows the RCST to return to the installation mode when needed. Values for the RCST mode are: Installation (0) Operational (1)
.1.3.6.1.2.1.10.239.1.1.6.2,DVB-RCS-MIB::dvbRcsRcstFaultStatus,INTEGER,read-only,,current,nofault(0):fault(1),Provides the fault status of the terminal. The fault status management is vendor specific. Values for the fault status are: no fault (0) fault (1)
.1.3.6.1.2.1.10.239.1.1.6.3,DVB-RCS-MIB::dvbRcsRcstFwdLinkStatus,INTEGER,read-only,,current,notAcquired(0):acquired(1),Provides the status of the RCST forward link. Values for the forward link status are: Not acquired (0) Acquired (1)
.1.3.6.1.2.1.10.239.1.1.6.4,DVB-RCS-MIB::dvbRcsRcstRtnLinkStatus,INTEGER,read-only,,current,loggedOff(0):loggedOn(1),Provides the status of the RCST return link. Values for the return link status are: Logged-off (0) Logged-on (1)
.1.3.6.1.2.1.10.239.1.1.6.5,DVB-RCS-MIB::dvbRcsRcstLogUpdated,INTEGER,read-only,,current,noUpdate(0):logfileUpdated(1),Indicates the existence of an updated event log file: No update (0) Event Log file updated (1) The RCST should remove the 'Event Log file updated' indication as the log file is fetched by the NCC.
.1.3.6.1.2.1.10.239.1.1.6.6,DVB-RCS-MIB::dvbRcsRcstCurrentSoftwareVersion,OCTET,read-only,,current,,Current RCST software version.
.1.3.6.1.2.1.10.239.1.1.6.7,DVB-RCS-MIB::dvbRcsRcstAlternateSoftwareVersion,OCTET,read-only,,current,,Alternate (backup/new) RCST software version.
.1.3.6.1.2.1.10.239.1.1.6.8,DVB-RCS-MIB::dvbRcsRcstActivatedConfigFileVersion,OCTET,read-only,,current,,Version of the most recently activated configuration file. The version is vendor specific.
.1.3.6.1.2.1.10.239.1.1.6.9,DVB-RCS-MIB::dvbRcsRcstDownloadedConfigFileVersion,OCTET,read-only,,current,,Version of the most recently downloaded configuration file. Version is vendor specific. If the value is different from dvbRcsRcstActivatedConfigFileVersion, it is pending for activation.
.1.3.6.1.2.1.10.239.1.2,DVB-RCS-MIB::dvbRcsFwdLink,,,,,,
.1.3.6.1.2.1.10.239.1.2.1,DVB-RCS-MIB::dvbRcsFwdConfig,,,,,,
.1.3.6.1.2.1.10.239.1.2.1.1,DVB-RCS-MIB::dvbRcsFwdStartTable,,not-accessible,,current,,Lists forward link attachment points (e.g., different for installation and operation). The table describes the forward link parameters used for the start-up stream with the NCC.
.1.3.6.1.2.1.10.239.1.2.1.1.1,DVB-RCS-MIB::dvbRcsFwdStartEntry,,not-accessible,dvbRcsFwdStartIndex,current,,An entry in the Forward Link Start Configuration table.
.1.3.6.1.2.1.10.239.1.2.1.1.1.1,DVB-RCS-MIB::dvbRcsFwdStartIndex,Unsigned32,not-accessible,,current,,Index of the Forward Link StartConfig table.
.1.3.6.1.2.1.10.239.1.2.1.1.1.2,DVB-RCS-MIB::dvbRcsFwdStartPopId,Integer32,read-create,,current,,Population identifier associated with the start-up forward link: -1: any (auto) 0-65535: specific StartPopId If 'any' is set, the RCST will assume membership of any announced population ID and will commence with logon in accordance with this assumption.
.1.3.6.1.2.1.10.239.1.2.1.1.1.3,DVB-RCS-MIB::dvbRcsFwdStartFrequency,Unsigned32,read-create,,current,,Frequency of the start transponder carrying a Network Information Table to which any RCST shall trigger to acquire forward link. Its value shall be given in multiples of 100 kHz.
.1.3.6.1.2.1.10.239.1.2.1.1.1.4,DVB-RCS-MIB::dvbRcsFwdStartPolar,INTEGER,read-create,,current,linearHorizontal(0):linearVertical(1):circularLeft(2):circularRight(3),2-bit field giving the polarization of the start transponder carrying a Network Information Table to which any RCST shall trigger to acquire forward link: 00: linear and horizontal 01: linear and vertical 10: circular left 11: circular right
.1.3.6.1.2.1.10.239.1.2.1.1.1.5,DVB-RCS-MIB::dvbRcsFwdStartFormat,INTEGER,read-create,,current,auto(-1):dvbs(0):dvbs2ccm(1):dvbs2acm(2),Specifies the transmission format standard applied for the startup stream. The start transport stream carries a Network Information Table that the RCST uses for acquiring the forward link signaling. Supported values are: -1: unspecified (automatic format acquisition is assumed) 0: DVB-S (support of this value is mandatory if DVB-S support is claimed) 1: DVB-S2 with CCM (support of this value is mandatory if DVB-S2 CCM support is claimed) 2: DVB-S2 with VCM or ACM (support of this value is mandatory if DVB-S2 ACM support is claimed) This allows the RCST to discriminate between CCM and VCM/ACM when selecting the forward link. The support of automatic format selection is optional. One or several of the other format selections must be supported, according to the claimed SatLabs profile support.
.1.3.6.1.2.1.10.239.1.2.1.1.1.6,DVB-RCS-MIB::dvbRcsFwdStartRolloff,INTEGER,read-create,,current,autoRolloff(0):rolloff020(1):rolloff025(2):rolloff035(3),Specifies the receive filter roll-off applied on the start transponder. The start transponder carries a Network Information Table that the RCST uses for acquiring the forward link signaling. Supported values are: 0: any (auto) 1: 0.20 2: 0.25 3: 0.35
.1.3.6.1.2.1.10.239.1.2.1.1.1.7,DVB-RCS-MIB::dvbRcsFwdStartSymbolRate,Unsigned32,read-create,,current,,Specifies the symbol rate on the start transponder carrying a Network Information Table to which any RCST shall trigger to acquire forward link. Its value shall be given in multiples of 100 symbols/s.
.1.3.6.1.2.1.10.239.1.2.1.1.1.8,DVB-RCS-MIB::dvbRcsFwdStartInnerFec,INTEGER,read-create,,current,autoFec(-1):fecRate12(0):fecRate23(1):fecRate34(2):fecRate56(3):fecRate78(4):fecRate89(5):fecRate35(6):fecRate45(7):fecRate910(8):fecRate25(9):fecRate13(10):fecRate14(11):noInnerCode(12),Specifies the inner Forward Error Correction used on the start transponder carrying a Network Information Table to which any RCST shall trigger to acquire forward link. Supported values are: autoFec (-1), fecRate1/2 (0), fecRate2/3 (1), fecRate3/4 (2), fecRate5/6 (3), fecRate7/8 (4), fecRate8/9 (5), fecRate3/5 (6), fecRate4/5 (7), fecRate9/10 (8), fecRate2/5 (9), fecRate1/3 (10), fecRate1/4 (11), noInnerCode (12) The support of autoFec is optional.
.1.3.6.1.2.1.10.239.1.2.1.1.1.9,DVB-RCS-MIB::dvbRcsFwdStartRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. It is not possible to change values in a row of this table while the row is active.
.1.3.6.1.2.1.10.239.1.2.2,DVB-RCS-MIB::dvbRcsFwdStatus,,,,,,
.1.3.6.1.2.1.10.239.1.2.2.1,DVB-RCS-MIB::dvbRcsFwdStatusPopId,Unsigned32,read-only,,current,,Population identifier applied at log-on: 0-65535: specific StartPopId If the RCST was allowed to logon with any population, the RCST will report the base number of the announced population ID indicated by the RCS Map Table linkage descriptor used at logon.
.1.3.6.1.2.1.10.239.1.2.2.2,DVB-RCS-MIB::dvbRcsFwdStatusTable,,not-accessible,,current,,This table describes the current status of Forward Link interfaces.
.1.3.6.1.2.1.10.239.1.2.2.2.1,DVB-RCS-MIB::dvbRcsFwdStatusEntry,,not-accessible,dvbRcsFwdStatusIndex,current,,An entry in the forward link status table. Each entry is associated with a physical interface. An RCST shall support at least one entry.
.1.3.6.1.2.1.10.239.1.2.2.2.1.1,DVB-RCS-MIB::dvbRcsFwdStatusIndex,Unsigned32,not-accessible,,current,,Index of the forward link status table.
.1.3.6.1.2.1.10.239.1.2.2.2.1.2,DVB-RCS-MIB::dvbRcsFwdStatusIfReference,Unsigned32,read-only,,current,,Cross reference to the interface table.
.1.3.6.1.2.1.10.239.1.2.2.2.1.3,DVB-RCS-MIB::dvbRcsFwdStatusNetId,Unsigned32,read-only,,current,,Interactive network identifier of the forward link (from the RCS Map Table).
.1.3.6.1.2.1.10.239.1.2.2.2.1.4,DVB-RCS-MIB::dvbRcsFwdStatusNetName,OCTET,read-only,,current,,The name of the interactive network of the forward link (from the RCS Map Table).
.1.3.6.1.2.1.10.239.1.2.2.2.1.5,DVB-RCS-MIB::dvbRcsFwdStatusFormat,INTEGER,read-only,,current,dvbs(0):dvbs2ccm(1):dvbs2acm(2):reservedFormat(3),Specifies the transmission format applied on the forward link. Supported values are (from RCS Map Table): 0: DVB-S 1: DVB-S2 using CCM 2: DVB-S2 using VCM or ACM 3: reserved
.1.3.6.1.2.1.10.239.1.2.2.2.1.6,DVB-RCS-MIB::dvbRcsFwdStatusFrequency,Unsigned32,read-only,,current,,An estimate of the frequency of the forward link. Its value shall be given in multiples of 100 kHz.
.1.3.6.1.2.1.10.239.1.2.2.2.1.7,DVB-RCS-MIB::dvbRcsFwdStatusPolar,INTEGER,read-only,,current,linearHorizontal(0):linearVertical(1):circularLeft(2):circularRight(3),2-bit field giving the polarization of the forward link Supported values are (from RCS Map Table): 00: linear and horizontal 01: linear and vertical 10: circular left 11: circular right
.1.3.6.1.2.1.10.239.1.2.2.2.1.8,DVB-RCS-MIB::dvbRcsFwdStatusInnerFec,INTEGER,read-only,,current,unknown(-1):fecRate12(0):fecRate23(1):fecRate34(2):fecRate56(3):fecRate78(4):fecRate89(5):fecRate35(6):fecRate45(7):fecRate910(8):fecRate25(9):fecRate13(10):fecRate14(11):noInnerCode(12),Specifies the inner Forward Error Correction used on the forward link for transmission to the RCST. Supported values are: unknown (-1), fecRate1/2 (0), fecRate2/3 (1), fecRate3/4 (2), fecRate5/6 (3), fecRate7/8 (4), fecRate8/9 (5), fecRate3/5 (6), fecRate4/5 (7), fecRate9/10 (8), fecRate2/5 (9), fecRate1/3 (10), fecRate1/4 (11), noInnerCode (12) The RCST will report a value that has been used for transmission to the RCST within the most recent 60 seconds. If this is not relevant, the RCST will report 'unknown'.
.1.3.6.1.2.1.10.239.1.2.2.2.1.9,DVB-RCS-MIB::dvbRcsFwdStatusSymbolRate,Unsigned32,read-only,,current,,An estimate of the symbol rate of the forward link. Its value shall be given in multiples of 100 symbols/s.
.1.3.6.1.2.1.10.239.1.2.2.2.1.10,DVB-RCS-MIB::dvbRcsFwdStatusRolloff,INTEGER,read-only,,current,undefRolloff(0):rolloff020(1):rolloff025(2):rolloff035(3),An estimate of the roll-off applied on the forward link. Supported values are: 0: undefined 1: 0.20 2: 0.25 3: 0.35
.1.3.6.1.2.1.10.239.1.2.2.2.1.11,DVB-RCS-MIB::dvbRcsFwdStatusModulation,INTEGER,read-only,,current,unknown(0):mBPSK(1):mQPSK(2):m8PSK(3):m16APSK(4):m32APSK(5),Indicates the modulation on the forward link used for transmission to the RCST. Supported values are: 0: unknown 1: BPSK 2: QPSK 3: 8PSK 4: 16APSK 5: 32APSK The RCST will report a value that has been used for transmission to the RCST within the most recent 60 seconds. If this is not relevant, the RCST will report 'unknown'.
.1.3.6.1.2.1.10.239.1.2.2.2.1.12,DVB-RCS-MIB::dvbRcsFwdStatusFecFrame,INTEGER,read-only,,current,unknown(0):shortframe(1):longframe(2),Indicates the frame length used on the forward link for transmission to the RCST. Supported values are: 0: Unknown 1: Short frame 2: Normal frame The RCST will report a value that has been used for transmission to the RCST within the most recent 60 seconds. If this is not relevant, the RCST will report 'unknown'.
.1.3.6.1.2.1.10.239.1.2.2.2.1.13,DVB-RCS-MIB::dvbRcsFwdStatusPilot,INTEGER,read-only,,current,unknown(0):pilotNotused(1):pilotUsed(2),Indicates whether pilots are used on the forward link for transmission to the RCST. Supported values are: 0: Unknown 1: Pilots are not used 2: Pilots are used The RCST will report a value that has been used for transmission to the RCST within the most recent 60 seconds. If this is not relevant, the RCST will report 'unknown'.
.1.3.6.1.2.1.10.239.1.2.2.2.1.14,DVB-RCS-MIB::dvbRcsFwdStatusBer,Integer32,read-only,,current,,Provides the RCST BER on the Forward Link in log10 units.
.1.3.6.1.2.1.10.239.1.2.2.2.1.15,DVB-RCS-MIB::dvbRcsFwdStatusCnr,Integer32,read-only,,current,,Provides the RCST CNR on the Forward Link in 0.1 dB units.
.1.3.6.1.2.1.10.239.1.2.2.2.1.16,DVB-RCS-MIB::dvbRcsFwdStatusRxPower,Integer32,read-only,,current,,Provides the power level of the forward link as received at the IDU, in 0.1 dBm units.
.1.3.6.1.2.1.10.239.1.3,DVB-RCS-MIB::dvbRcsRtnLink,,,,,,
.1.3.6.1.2.1.10.239.1.3.1,DVB-RCS-MIB::dvbRcsRtnConfig,,,,,,
.1.3.6.1.2.1.10.239.1.3.1.1,DVB-RCS-MIB::dvbRcsRtnConfigMaxEirp,Integer32,read-write,,current,,Max Equivalent Isotropic Radiated Power (EIRP) of the RCST, given in resolution of 0.1 dBm and applied when the IDU can, itself, set the necessary IDU TX output level, e.g., when using a BUC that has a power level detector and that provides sufficient feedback to the IDU.
.1.3.6.1.2.1.10.239.1.3.1.2,DVB-RCS-MIB::dvbRcsRtnConfigDefIfLevel,Integer32,read-write,,current,,IDU TX output level applied in case the dvbRcsRtnConfigMaxEirp cannot be used. The resolution is 0.1 dBm and the accuracy is +/- 1 dBm.
.1.3.6.1.2.1.10.239.1.3.2,DVB-RCS-MIB::dvbRcsRtnStatus,,,,,,
.1.3.6.1.2.1.10.239.1.3.2.1,DVB-RCS-MIB::dvbRcsRtnStatusEbN0,Integer32,read-only,,current,,The EbN0 value reported for the return link, referenced to the regular SYNC burst transmission, in 0.1 dB units.
.1.3.6.1.2.1.10.239.1.3.2.2,DVB-RCS-MIB::dvbRcsRtnStatusSFDuration,Unsigned32,read-only,,current,,The duration of the currently applied return link superframe structure, in tenths of milliseconds.
.1.3.6.1.2.1.10.239.1.3.2.3,DVB-RCS-MIB::dvbRcsRtnStatusPayloadUnit,INTEGER,read-only,,current,unitATM(0):unitMPEG(1),Indicates if the payload unit used for the return link is ATM or MPEG.
.1.3.6.1.2.1.10.239.2,DVB-RCS-MIB::dvbRcsConformance,,,,,,
.1.3.6.1.2.1.10.239.2.1,DVB-RCS-MIB::dvbRcsRcstGroups,,,,,,
.1.3.6.1.2.1.10.239.2.1.1,DVB-RCS-MIB::dvbRcsRcstSystemGroup,,,,,,A collection of objects providing information applicable for basic device management support.
.1.3.6.1.2.1.10.239.2.1.2,DVB-RCS-MIB::dvbRcsRcstNetworkGroup,,,,,,A collection of objects providing basic networking management support.
.1.3.6.1.2.1.10.239.2.1.3,DVB-RCS-MIB::dvbRcsRcstExtNetworkGroup,,,,,,A collection of objects providing extended networking management support.
.1.3.6.1.2.1.10.239.2.1.4,DVB-RCS-MIB::dvbRcsRcstDnsGroup,,,,,,A collection of objects providing DNS management support.
.1.3.6.1.2.1.10.239.2.1.5,DVB-RCS-MIB::dvbRcsRcstInstallGroup,,,,,,A collection of objects providing information applicable for basic installation support.
.1.3.6.1.2.1.10.239.2.1.6,DVB-RCS-MIB::dvbRcsRcstExtInstallGroup,,,,,,A collection of objects providing extended device installation support.
.1.3.6.1.2.1.10.239.2.1.7,DVB-RCS-MIB::dvbRcsRcstQosGroup,,,,,,A collection of objects providing basic access to QoS configuration data.
.1.3.6.1.2.1.10.239.2.1.8,DVB-RCS-MIB::dvbRcsRcstEnhancedClassifierGroup,,,,,,A collection of objects providing support for management of the enhanced classifier.
.1.3.6.1.2.1.10.239.2.1.9,DVB-RCS-MIB::dvbRcsRcstMpegQosGroup,,,,,,A collection of objects providing access to MPEG-related link QoS configuration data.
.1.3.6.1.2.1.10.239.2.1.10,DVB-RCS-MIB::dvbRcsRcstGlobalQosGroup,,,,,,A collection of objects providing access to global RCST QoS configuration data.
.1.3.6.1.2.1.10.239.2.1.11,DVB-RCS-MIB::dvbRcsRcstStrictQosGroup,,,,,,A collection of objects allowing management of strict channel ID dispatching.
.1.3.6.1.2.1.10.239.2.1.12,DVB-RCS-MIB::dvbRcsRcstControlGroup,,,,,,A collection of objects allowing basic RCST control.
.1.3.6.1.2.1.10.239.2.1.13,DVB-RCS-MIB::dvbRcsRcstExtControlGroup,,,,,,A collection of objects allowing extended RCST control.
.1.3.6.1.2.1.10.239.2.1.14,DVB-RCS-MIB::dvbRcsRcstStateGroup,,,,,,A collection of objects allowing access to RCST state.
.1.3.6.1.2.1.10.239.2.1.15,DVB-RCS-MIB::dvbRcsFwdConfigGroup,,,,,,A collection of objects providing basic start forward link configuration support.
.1.3.6.1.2.1.10.239.2.1.16,DVB-RCS-MIB::dvbRcsFwdStatusGroup,,,,,,A collection of objects providing forward link status.
.1.3.6.1.2.1.10.239.2.1.17,DVB-RCS-MIB::dvbRcsRtnConfigGroup,,,,,,A collection of objects providing basic return link configuration support.
.1.3.6.1.2.1.10.239.2.1.18,DVB-RCS-MIB::dvbRcsRtnExtConfigGroup,,,,,,A collection of objects providing extended return link configuration support.
.1.3.6.1.2.1.10.239.2.1.19,DVB-RCS-MIB::dvbRcsRtnStatusGroup,,,,,,A collection of objects allowing access to return link status.
.1.3.6.1.2.1.10.239.2.1.20,DVB-RCS-MIB::dvbRcsRtnExtStatusGroup,,,,,,A collection of objects allowing access to extended return link status.
.1.3.6.1.2.1.10.239.2.1.21,DVB-RCS-MIB::dvbRcsRcstOduListGroup,,,,,,A collection of objects supporting flexible selection of ODU devices.
.1.3.6.1.2.1.10.239.2.2,DVB-RCS-MIB::dvbRcsRcstCompliances,,,,,,
.1.3.6.1.2.1.10.239.2.2.1,DVB-RCS-MIB::dvbRcsRcstCompliance1,,,,,,The compliance statement for DVB-RCS terminals that are compliant with SatLabs System Recommendations. Compliance is linked to the support by the terminal of the options or features defined in the SatLabs System Recommendations. The supported options and features of a terminal are declared in objects dvbRcsSystemSatLabsOptionsDeclaration and dvbRcsSystemSatLabsFeaturesDeclaration respectively.
.1.3.6.1.2.1.10.246,PW-STD-MIB::pwStdMIB,,,,,,This MIB module contains managed object definitions for pseudowire operation as in Bryant, S. and P. Pate, 'Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture' [RFC3985], Martini, L., et al, 'Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)' [RFC4447], and Townsley, M., et al, 'Layer Two Tunneling Protocol (Version 3)' [RFC3931]. This MIB module enables the use of any underlying packet switched network (PSN). MIB nodules that will support PW operations over specific PSN types are defined in separate memos. The indexes for this MIB module are also used to index the PSN-specific tables and the PW-specific tables. The PW Type dictates which PW-specific MIB module to use. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5601; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.10.246.0,PW-STD-MIB::pwNotifications,,,,,,
.1.3.6.1.2.1.10.246.0.1,PW-STD-MIB::pwDown,,,,,,This notification is generated when the pwOperStatus object for one or more contiguous entries in the pwTable are about to enter the down(2) or lowerLayerDown(6) state from any other state, except for transition from the notPresent(5) state. For the purpose of deciding when these notifications occur, the lowerLayerDown(6) state and the down(2) state are considered to be equivalent; i.e., there is no notification on transition from lowerLayerDown(6) into down(2), and there is a trap on transition from any other state except down(2) (and notPresent) into lowerLayerDown(6). The included values of pwOperStatus MUST each be equal to down(2) or lowerLayerDown(6). The two instances of pwOperStatus in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of cross-connects have transitioned into the down(2) and lowerLayerDown(6) states at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single cross-connect entry, then the instance identifier (and values) of the two pwOperStatus objects MUST be identical.
.1.3.6.1.2.1.10.246.0.2,PW-STD-MIB::pwUp,,,,,,This notification is generated when the pwOperStatus object for one or more contiguous entries in the pwTable are about to enter the up(1) state from some other state except the notPresent(5) state and given that the pwDown notification been issued for these entries. The included values of pwOperStatus MUST both be set equal to this new state (i.e., up(1)). The two instances of pwOperStatus in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of cross-connects have transitioned into the up(1) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single cross-connect entry, then the instance identifier (and values) of the two pwOperStatus objects MUST be identical.
.1.3.6.1.2.1.10.246.0.3,PW-STD-MIB::pwDeleted,,,,,,This notification is generated when the PW has been deleted, i.e., when the pwRowStatus has been set to destroy(6) or the PW has been deleted by a non-MIB application or due to an auto-discovery process. 
.1.3.6.1.2.1.10.246.1,PW-STD-MIB::pwObjects,,,,,,
.1.3.6.1.2.1.10.246.1.1,PW-STD-MIB::pwIndexNext,Unsigned32,read-only,,current,,This object contains an appropriate value to be used for pwIndex when creating entries in the pwTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwIndex for a new entry in the pwTable, the manager issues a management protocol retrieval operation. The agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.10.246.1.2,PW-STD-MIB::pwTable,,not-accessible,,current,,This table specifies information for configuring and status monitoring that is common to all service types and PSN types.
.1.3.6.1.2.1.10.246.1.2.1,PW-STD-MIB::pwEntry,,not-accessible,pwIndex,current,,A row in this table represents a pseudowire (PW) virtual connection across a packet network. It is indexed by pwIndex, which uniquely identifies a singular connection. A row can be created by an operator command from a management plan of a PE, by signaling, or due to auto- discovery process. An operator's command can be issued via a non-SNMP application; in such case, a row will be created implicitly by the agent. The read-create objects in this table are divided into three categories: 1) Objects that MUST NOT be changed after row activation. These are objects that define basic properties of the PW (for example type, destination, etc.). 2) Objects that MAY be changed when the PW is defined as not active. A change of these objects involves re-signaling of the PW or it might be traffic affecting. PW not active is defined as one of the following conditions: a) The pwRowStatus is notInService(2). b) The pwRowStatus is notReady(3). c) The pwAdminStatus is down(2). If the operator needs to change one of the values for an active row, the operator can either set the pwRowStatus to notInService(2) or set pwAdminStatus to down(2). Signaling (or traffic) is initiated again upon setting the pwRowStatus to active(1) or setting the pwAdminStatus to up(1) or testing(3), respectively. 3) Objects that MAY be changed at any time. A PW MAY have an entry in the ifTable in addition to the entry in this table. In this case, a special ifType for PW will be set in the ifTable, and the ifIndex in the ifTable of the PW will be set in the pwIfIndex object in this table. By default, all the read-create objects MUST NOT be changed after row activation, unless specifically indicated in the individual object description. Manual entries in this table SHOULD be preserved after a reboot; the agent MUST ensure the integrity of those entries. If the set of entries of a specific row are found to be inconsistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5). 
.1.3.6.1.2.1.10.246.1.2.1.1,PW-STD-MIB::pwIndex,Unsigned32,not-accessible,,current,,A unique index for the conceptual row identifying a PW within this table.
.1.3.6.1.2.1.10.246.1.2.1.2,PW-STD-MIB::pwType,INTEGER,read-create,,current,other(0):frameRelayDlciMartiniMode(1):atmAal5SduVcc(2):atmTransparent(3):ethernetTagged(4):ethernet(5):hdlc(6):ppp(7):cem(8):atmCellNto1Vcc(9):atmCellNto1Vpc(10):ipLayer2Transport(11):atmCell1to1Vcc(12):atmCell1to1Vpc(13):atmAal5PduVcc(14):frameRelayPortMode(15):cep(16):e1Satop(17):t1Satop(18):e3Satop(19):t3Satop(20):basicCesPsn(21):basicTdmIp(22):tdmCasCesPsn(23):tdmCasTdmIp(24):frDlci(25):wildcard(32767),This value indicates the emulated service to be carried over this PW. 
.1.3.6.1.2.1.10.246.1.2.1.3,PW-STD-MIB::pwOwner,INTEGER,read-create,,current,manual(1):pwIdFecSignaling(2):genFecSignaling(3):l2tpControlProtocol(4):other(5),This object is set by the operator to indicate the protocol responsible for establishing this PW. 'manual' is used in all cases where no maintenance protocol (PW signaling) is used to set up the PW, i.e., configuration of entries in the PW tables including PW labels, etc., is done by setting the MIB fields manually. 'pwIdFecSignaling' is used in case of signaling with the Pwid FEC element with LDP signaling. 'genFecSignaling' is used in case of LDP signaling with the generalized FEC. 'l2tpControlProtocol' indicates the use of the L2TP control protocol. 'other' is used for other types of signaling.
.1.3.6.1.2.1.10.246.1.2.1.4,PW-STD-MIB::pwPsnType,INTEGER,read-create,,current,mpls(1):l2tp(2):udpOverIp(3):mplsOverIp(4):mplsOverGre(5):other(6),This object is set by the operator to indicate the PSN type. Based on this object, the relevant PSN table's entry is created in the PSN-specific MIB modules. 
.1.3.6.1.2.1.10.246.1.2.1.5,PW-STD-MIB::pwSetUpPriority,Integer32,read-create,,current,,This object defines the relative priority of the PW during set-up in a lowest-to-highest fashion, where 0 is the highest priority. PWs with the same priority are treated with equal priority. PWs that have not yet completed setup will report 'dormant' in the pwOperStatus. This value is significant if there are competing resources among PWs and the implementation supports this feature. Equal priority handling with competing resources is implementation specific. This object MAY be changed at any time.
.1.3.6.1.2.1.10.246.1.2.1.6,PW-STD-MIB::pwHoldingPriority,Integer32,read-create,,current,,This object defines the relative holding priority of the PW in a lowest-to-highest fashion, where 0 is the highest priority. PWs with the same priority are treated equally. This value is significant if there are competing resources among PWs and the implementation supports this feature. Equal priority handling with competing resources is implementation specific. This object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.8,PW-STD-MIB::pwPeerAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Denotes the address type of the peer node. It should be set to 'unknown' if PE/PW maintenance protocol is not used and the address is unknown.
.1.3.6.1.2.1.10.246.1.2.1.9,PW-STD-MIB::pwPeerAddr,OCTET,read-create,,current,,This object contains the value of the peer node address of the PW/PE maintenance protocol entity. This object SHOULD contain a value of all zeroes if not applicable (pwPeerAddrType is 'unknown').
.1.3.6.1.2.1.10.246.1.2.1.10,PW-STD-MIB::pwAttachedPwIndex,Unsigned32,read-create,,current,,If the PW is attached to another PW instead of a local native service, this item indicates the pwIndex of the attached PW. Otherwise, this object MUST be set to zero. Attachment to another PW will have no PW specific entry in any of the service MIB modules.
.1.3.6.1.2.1.10.246.1.2.1.11,PW-STD-MIB::pwIfIndex,Integer32,read-create,,current,,This object indicates the ifIndex of the PW if the PW is represented in the ifTable. Otherwise, it MUST be set to zero.
.1.3.6.1.2.1.10.246.1.2.1.12,PW-STD-MIB::pwID,Unsigned32,read-create,,current,,Pseudowire identifier. If the pwOwner object is 'pwIdFecSignaling' or 'l2tpControlProtocol', then this object is signaled in the outgoing PW ID field within the 'Virtual Circuit FEC Element'. For other values of pwOwner, this object is not signaled and it MAY be set to zero. For implementations that support the pwIndexMappingTable, a non-zero value is RECOMMENDED, even if this identifier is not signaled. This is so that reverse mappings can be provided by pwIndexMappingTable and pwPeerMappingTable. It is therefore RECOMMENDED that the value of this pwID be unique (or if pwPeerAddrType is not 'unknown', at least [pwType, pwID, pwPeerAddrType, pwPeerAddr] is unique.)
.1.3.6.1.2.1.10.246.1.2.1.13,PW-STD-MIB::pwLocalGroupID,Unsigned32,read-create,,current,,Used in the Group ID field sent to the peer PW End Service within the maintenance protocol used for PW setup. It SHOULD be set to zero if a maintenance protocol is not used.
.1.3.6.1.2.1.10.246.1.2.1.14,PW-STD-MIB::pwGroupAttachmentID,OCTET,read-create,,current,,This object is an octet string representing the attachment group identifier (AGI) that this PW belongs to, which typically identifies the VPN ID. Applicable if pwOwner equals 'genFecSignaling'.
.1.3.6.1.2.1.10.246.1.2.1.15,PW-STD-MIB::pwLocalAttachmentID,OCTET,read-create,,current,,This object is an octet string representing the local forwarder attachment individual identifier (AII) to be used by this PW. It is used as the Source AII (SAII) for outgoing signaling messages and the Target AII (TAII) in the incoming messages from the peer. Applicable if pwOwner equal 'genFecSignaling'.
.1.3.6.1.2.1.10.246.1.2.1.16,PW-STD-MIB::pwRemoteAttachmentID,OCTET,read-create,,current,,This object is an octet string representing the remote forwarder attachment individual identifier (AII) to be used by this PW. It is used as the TAII for outgoing signaling messages and the SAII in the incoming messages from the peer. Applicable if pwOwner equals 'genFecSignaling'.
.1.3.6.1.2.1.10.246.1.2.1.17,PW-STD-MIB::pwCwPreference,INTEGER,read-create,,current,true(1):false(2),Defines if the control word will be sent with each packet by the local node. Some PW types mandate the use of a control word, and in such cases, the value configured for this object has no effect on the existence of the control word. This object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.18,PW-STD-MIB::pwLocalIfMtu,Unsigned32,read-create,,current,,If not equal to zero, the optional IfMtu object in the signaling protocol will be sent with this value, which represents the locally supported MTU size over the interface (or the virtual interface) associated with the PW. This object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.19,PW-STD-MIB::pwLocalIfString,INTEGER,read-create,,current,true(1):false(2),A PW MAY be associated to an interface (or a virtual interface) in the ifTable of the node as part of the service configuration. This object defines if the maintenance protocol will send the interface's name (ifAlias) as it appears in the ifTable. If set to false, the optional element will not be sent. This object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.20,PW-STD-MIB::pwLocalCapabAdvert,BITS,read-create,,current,pwStatusIndication(0):pwVCCV(1),If a maintenance protocol is used, it indicates the capabilities the local node will advertise to the peer. The operator MAY selectively assign a partial set of capabilities. In case of manual configuration of the PW, the operator SHOULD set non-conflicting options (for example, only a single type of Operations, Administration, and Management (OAM)) out of the available options in the implementation. It is possible to change the value of this object when the PW is not active. The agent MUST reject any attempt to set a capability that is not supported. The default value MUST be the full set of local node capabilities.
.1.3.6.1.2.1.10.246.1.2.1.21,PW-STD-MIB::pwRemoteGroupID,Unsigned32,read-only,,current,,This object is obtained from the Group ID field as received via the maintenance protocol used for PW setup. Value of zero will be reported if not used. Value of 0xFFFFFFFF shall be used if the object is yet to be defined by the PW maintenance protocol.
.1.3.6.1.2.1.10.246.1.2.1.22,PW-STD-MIB::pwCwStatus,INTEGER,read-only,,current,waitingForNextMsg(1):sentWrongBitErrorCode(2):rxWithdrawWithWrongBitErrorCode(3):illegalReceivedBit(4):cwPresent(5):cwNotPresent(6):notYetKnown(7),If signaling is used for PW establishment, this object indicates the status of the control word negotiation. For either signaling or manual configuration, it indicates if the control word (CW) is to be present for this PW.
.1.3.6.1.2.1.10.246.1.2.1.23,PW-STD-MIB::pwRemoteIfMtu,Unsigned32,read-only,,current,,The remote interface MTU as (optionally) received from the remote node via the maintenance protocol. The object SHOULD report zero if the MTU is not available.
.1.3.6.1.2.1.10.246.1.2.1.24,PW-STD-MIB::pwRemoteIfString,OCTET,read-only,,current,,Indicates the interface description string as received by the maintenance protocol. It MUST be a NULL string if a maintenance protocol is not used or the value is not known yet.
.1.3.6.1.2.1.10.246.1.2.1.25,PW-STD-MIB::pwRemoteCapabilities,BITS,read-only,,current,pwStatusIndication(0):pwVCCV(1),Indicates the capabilities as received from the peer.
.1.3.6.1.2.1.10.246.1.2.1.26,PW-STD-MIB::pwFragmentCfgSize,Unsigned32,read-create,,current,,If set to a value other than zero, indicates that fragmentation is desired for this PW. This object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.27,PW-STD-MIB::pwRmtFragCapability,BITS,read-only,,current,noFrag(0):cfgFragGreaterThanPsnMtu(1):cfgFragButRemoteIncapable(2):remoteFragCapable(3):fragEnabled(4),The status of the fragmentation based on the local configuration and the peer capabilities as received from the peer when a control protocol is used.
.1.3.6.1.2.1.10.246.1.2.1.28,PW-STD-MIB::pwFcsRetentionCfg,INTEGER,read-create,,current,fcsRetentionDisable(1):fcsRetentionEnable(2),The local configuration of Frame Check Sequence (FCS) retention for this PW. FCS retention can be configured for PW types High-Level Data Link Control (HDLC), Point-to-Point Protocol (PPP), and Ethernet only. If the implementation does not support FCS retention, an error MUST be reported in pwFcsRetentionStatus. This object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.29,PW-STD-MIB::pwFcsRetentionStatus,BITS,read-only,,current,remoteIndicationUnknown(0):remoteRequestFcsRetention(1):fcsRetentionEnabled(2):fcsRetentionDisabled(3):localFcsRetentionCfgErr(4):fcsRetentionFcsSizeMismatch(5),The status of the FCS retention negotiation process based on local configuration and the remote advertisement. remoteIndicationUnknown - set if a FEC has not been received from the remote. remoteRequestFcsRetention - indicates that the peer has requested FCS retention. FCS retention will be used if the local node is capable and configured to use it for this PW. fcsRetentionEnabled - FCS retention is enabled (both peers were configured for FCS retention for signaled PW, or the local node is configured and capable of FCS retention for manually assigned PWs). fcsRetentionDisabled - FCS retention is disabled (not configured locally or not advertised by the peer). localFcsRetentionCfgErr - set if the local node has been configured for FCS retention but is not capable to support it. fcsRetentionFcsSizeMismatch - set if there is an FCS size mismatch between the local and the peer node. 
.1.3.6.1.2.1.10.246.1.2.1.30,PW-STD-MIB::pwOutboundLabel,Unsigned32,read-create,,current,,The PW label used in the outbound direction (i.e., toward the PSN). It might be set manually if pwOwner is 'manual'; otherwise, it is set automatically. For MPLS, MPLS over IP, or MPLS over Generic Routing Encapsulation (GRE) PSN, it represents the 20-bit PW tag; for L2TP, it represents the 32-bit Session ID; and for IP PSN, it represents the destination UDP port number. If the label is not yet known (signaling in process), the object SHOULD return a value of 0xFFFFFFFF. For manual configuration, this object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.31,PW-STD-MIB::pwInboundLabel,Unsigned32,read-create,,current,,The PW label used in the inbound direction (i.e., packets received from the PSN). It may be set manually if pwOwner is 'manual'; otherwise, it is set automatically. For MPLS, MPLS over IP, or MPLS over GRE PSN, it represents the 20-bit PW tag; for L2TP, it represents the 32-bit Session ID; and for IP PSN, it represents the source UDP port number. If the label is not yet known (signaling in process), the object SHOULD return a value of 0xFFFFFFFF. For manual configuration, this object MAY be changed only if the PW is not active.
.1.3.6.1.2.1.10.246.1.2.1.32,PW-STD-MIB::pwName,OCTET,read-create,,current,,The canonical name assigned to the PW. This object MAY be changed at any time.
.1.3.6.1.2.1.10.246.1.2.1.33,PW-STD-MIB::pwDescr,OCTET,read-create,,current,,A textual string containing information about the PW. If there is no description, this object contains a zero- length string. This object MAY be changed at any time.
.1.3.6.1.2.1.10.246.1.2.1.34,PW-STD-MIB::pwCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time this PW was created.
.1.3.6.1.2.1.10.246.1.2.1.35,PW-STD-MIB::pwUpTime,TimeTicks,read-only,,current,,Specifies the time since last change of pwOperStatus to Up(1).
.1.3.6.1.2.1.10.246.1.2.1.36,PW-STD-MIB::pwLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the PW entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.10.246.1.2.1.37,PW-STD-MIB::pwAdminStatus,INTEGER,read-create,,current,up(1):down(2):testing(3),The desired operational status of this PW. This object MAY be set at any time.
.1.3.6.1.2.1.10.246.1.2.1.38,PW-STD-MIB::pwOperStatus,INTEGER,read-only,,current,up(1):down(2):testing(3):dormant(4):notPresent(5):lowerLayerDown(6),This object indicates the operational status of the PW; it does not reflect the status of the Customer Edge (CE) bound interface. It is set to down only if pwNotForwarding, psnFacingPwRxFault, or psnFacingPwTxFault indications are set in pwLocalStatus or pwRemoteStatus. It indicates 'lowerLayerDown' if the only reason for not being in the 'up' state is that either the outer tunnel or physical layer of the network side is in the 'down' state. All other states are declared based on the description of the PwOperStatusTC. 
.1.3.6.1.2.1.10.246.1.2.1.39,PW-STD-MIB::pwLocalStatus,BITS,read-only,,current,pwNotForwarding(0):servicePwRxFault(1):servicePwTxFault(2):psnPwRxFault(3):psnPwTxFault(4),Indicates the status of the PW in the local node. The various indications in this object SHOULD be available independent of the ability of the local node to advertise them or the remote node to accept these status indications through the control protocol. 
.1.3.6.1.2.1.10.246.1.2.1.40,PW-STD-MIB::pwRemoteStatusCapable,INTEGER,read-only,,current,notApplicable(1):notYetKnown(2):remoteCapable(3):remoteNotCapable(4),Indicates the remote node capability to advertise the PW status notification. notApplicable SHOULD be reported for a manually set PW, or if the local node is not capable of accepting the status notification object. notYetKnown SHOULD be reported if the signaling protocol has not yet finished the process of capability determination. remoteCapable and remoteNotcapable SHOULD be reported based on the initial signaling exchange that has determined the remote node capability. 
.1.3.6.1.2.1.10.246.1.2.1.41,PW-STD-MIB::pwRemoteStatus,BITS,read-only,,current,pwNotForwarding(0):servicePwRxFault(1):servicePwTxFault(2):psnPwRxFault(3):psnPwTxFault(4),Indicates the status of the PW as was advertised by the remote. If the remote is not capable of advertising the status object, or the local node is not able to accept the status object through signaling, then the applicable bit is 'pwNotForwarding', which is set if the remote has sent label release or label withdraw for this PW. 
.1.3.6.1.2.1.10.246.1.2.1.42,PW-STD-MIB::pwTimeElapsed,Integer32,read-only,,current,,The number of seconds, including partial seconds, that have elapsed since the beginning of the current interval measurement period.
.1.3.6.1.2.1.10.246.1.2.1.43,PW-STD-MIB::pwValidIntervals,Integer32,read-only,,current,,The number of previous 15-minute intervals for which data was collected.
.1.3.6.1.2.1.10.246.1.2.1.44,PW-STD-MIB::pwRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. This object MAY be changed at any time.
.1.3.6.1.2.1.10.246.1.2.1.45,PW-STD-MIB::pwStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object.
.1.3.6.1.2.1.10.246.1.2.1.46,PW-STD-MIB::pwOamEnable,INTEGER,read-create,,current,true(1):false(2),This variable indicates if OAM is enabled for this PW. It MAY be changed at any time.
.1.3.6.1.2.1.10.246.1.2.1.47,PW-STD-MIB::pwGenAGIType,Unsigned32,read-create,,current,,This variable indicates the AGI type if generalized FEC (129) is used for PW signaling or configuration. It SHOULD return the value of zero otherwise.
.1.3.6.1.2.1.10.246.1.2.1.48,PW-STD-MIB::pwGenLocalAIIType,Unsigned32,read-create,,current,,This object is the type of the local forwarder attachment individual identifier (AII) to be used by this PW if generalized FEC (129) is used for PW signaling or configuration.
.1.3.6.1.2.1.10.246.1.2.1.49,PW-STD-MIB::pwGenRemoteAIIType,Unsigned32,read-create,,current,,This object is the type of the remote forwarder attachment individual identifier (AII) to be used by this PW if generalized FEC (129) is used for PW signaling or configuration.
.1.3.6.1.2.1.10.246.1.3,PW-STD-MIB::pwPerfCurrentTable,,not-accessible,,current,,This table provides per-PW performance information for the current interval.
.1.3.6.1.2.1.10.246.1.3.1,PW-STD-MIB::pwPerfCurrentEntry,,not-accessible,pwIndex,current,,An entry in this table is created by the agent for every PW.
.1.3.6.1.2.1.10.246.1.3.1.1,PW-STD-MIB::pwPerfCurrentInHCPackets,Counter64,read-only,,current,,High-capacity counter for number of packets received by the PW (from the PSN) in the current 15-minute interval. This is the 64-bit version of pwPerfCurrentInPackets, if pwPerfCurrentInHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.2,PW-STD-MIB::pwPerfCurrentInHCBytes,Counter64,read-only,,current,,High-capacity counter for number of bytes received by the PW (from the PSN) in the current 15-minute interval. This is the 64-bit version of pwPerfCurrentInBytes, if pwPerfCurrentInHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.3,PW-STD-MIB::pwPerfCurrentOutHCPackets,Counter64,read-only,,current,,High-capacity counter for number of packets forwarded by the PW (to the PSN) in the current 15-minute interval. This is the 64-bit version of pwPerfCurrentOutPackets, if pwPerfCurrentOutHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.4,PW-STD-MIB::pwPerfCurrentOutHCBytes,Counter64,read-only,,current,,High-capacity counter for number of bytes forwarded by the PW (to the PSN) in the current 15-minute interval. This is the 64-bit version of pwPerfCurrentOutBytes, if pwPerfCurrentOutHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.5,PW-STD-MIB::pwPerfCurrentInPackets,Gauge32,read-only,,current,,The counter for number of packets received by the PW (from the PSN) in the current 15-minute interval. This is the 32-bit version of pwPerfCurrentInHCPackets, if pwPerfCurrentInHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.6,PW-STD-MIB::pwPerfCurrentInBytes,Gauge32,read-only,,current,,The counter for number of bytes received by the PW (from the PSN) in the current 15-minute interval. It MUST be equal to the least significant 32 bits of pwPerfCurrentInHCBytes, if pwPerfCurrentInHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.7,PW-STD-MIB::pwPerfCurrentOutPackets,Gauge32,read-only,,current,,The counter for number of packets forwarded by the PW (to the PSN) in the current 15-minute interval. It MUST be equal to the least significant 32 bits of pwPerfCurrentOutHCPackets, if pwPerfCurrentOutHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.3.1.8,PW-STD-MIB::pwPerfCurrentOutBytes,Gauge32,read-only,,current,,The counter for number of bytes forwarded by the PW (to the PSN) in the current 15-minute interval. It MUST be equal to the least significant 32 bits of pwPerfCurrentOutHCBytes, if pwPerfCurrentOutHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4,PW-STD-MIB::pwPerfIntervalTable,,not-accessible,,current,,This table provides per-PW performance information for each interval.
.1.3.6.1.2.1.10.246.1.4.1,PW-STD-MIB::pwPerfIntervalEntry,,not-accessible,pwIndex:pwPerfIntervalNumber,current,,An entry in this table is created by the agent for every PW.
.1.3.6.1.2.1.10.246.1.4.1.1,PW-STD-MIB::pwPerfIntervalNumber,Integer32,not-accessible,,current,,A number N, between 1 and 96, which identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15-minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1. The minimum range of N is 1 through 4. The default range is 1 to 32. The maximum range of N is 1 through 96.
.1.3.6.1.2.1.10.246.1.4.1.2,PW-STD-MIB::pwPerfIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.246.1.4.1.3,PW-STD-MIB::pwPerfIntervalTimeElapsed,Integer32,read-only,,current,,The duration of this interval in seconds.
.1.3.6.1.2.1.10.246.1.4.1.4,PW-STD-MIB::pwPerfIntervalInHCPackets,Counter64,read-only,,current,,High-capacity counter for number of packets received by the PW (from the PSN) during the interval. This is the 64-bit version of pwPerfIntervalInPackets, if pwPerfIntervalInHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.5,PW-STD-MIB::pwPerfIntervalInHCBytes,Counter64,read-only,,current,,High-capacity counter for number of bytes received by the PW (from the PSN) during the interval. This is the 64-bit version of pwPerfIntervalInBytes, if pwPerfIntervalInHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.6,PW-STD-MIB::pwPerfIntervalOutHCPackets,Counter64,read-only,,current,,High-capacity counter for number of packets forwarded by the PW (to the PSN) during the interval. This is the 64-bit version of pwPerfIntervalOutPackets, if pwPerfIntervalOutHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.7,PW-STD-MIB::pwPerfIntervalOutHCBytes,Counter64,read-only,,current,,High-capacity counter for number of bytes forwarded by the PW (to the PSN) during the interval. This is the 64-bit version of pwPerfIntervalOutBytes, if pwPerfIntervalOutHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.8,PW-STD-MIB::pwPerfIntervalInPackets,Gauge32,read-only,,current,,This value represents the number of packets received by this PW during the interval. It MUST be equal to the least significant 32 bits of pwPerfIntervalInHCPackets, if pwPerfIntervalInHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.9,PW-STD-MIB::pwPerfIntervalInBytes,Gauge32,read-only,,current,,This value represents the number of bytes received by this PW during the interval. It MUST be equal to the least significant 32 bits of pwPerfIntervalInHCBytes, if pwPerfIntervalInHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.10,PW-STD-MIB::pwPerfIntervalOutPackets,Gauge32,read-only,,current,,This value represents the number of packets sent by this PW during the interval. It MUST be equal to the least significant 32 bits of pwPerfIntervalOutHCPackets, if pwPerfIntervalOutHCPackets is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.4.1.11,PW-STD-MIB::pwPerfIntervalOutBytes,Gauge32,read-only,,current,,This value represents the number of bytes sent by this PW during the interval. It MUST be equal to the least significant 32 bits of pwPerfIntervalOutHCBytes, if pwPerfIntervalOutHCBytes is supported according to the rules spelled out in RFC 2863.
.1.3.6.1.2.1.10.246.1.5,PW-STD-MIB::pwPerf1DayIntervalTable,,not-accessible,,current,,This table provides per-PW performance information for the current day's measurement and the previous day's interval.
.1.3.6.1.2.1.10.246.1.5.1,PW-STD-MIB::pwPerf1DayIntervalEntry,,not-accessible,pwIndex:pwPerf1DayIntervalNumber,current,,An entry in this table is created by the agent for every PW.
.1.3.6.1.2.1.10.246.1.5.1.1,PW-STD-MIB::pwPerf1DayIntervalNumber,Unsigned32,not-accessible,,current,,History Data Interval number. Interval 1 is the current day's measurement period, interval 2 is the most recent previous day, and interval 30 is 31 days ago. Intervals 3..31 are optional.
.1.3.6.1.2.1.10.246.1.5.1.2,PW-STD-MIB::pwPerf1DayIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.246.1.5.1.3,PW-STD-MIB::pwPerf1DayIntervalTimeElapsed,Integer32,read-only,,current,,The number of seconds in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in a situation where performance monitoring data could not be collected for any reason or where agent clock adjustments have been made.
.1.3.6.1.2.1.10.246.1.5.1.4,PW-STD-MIB::pwPerf1DayIntervalInHCPackets,Counter64,read-only,,current,,High-capacity counter for the total number of packets received by the PW (from the PSN).
.1.3.6.1.2.1.10.246.1.5.1.5,PW-STD-MIB::pwPerf1DayIntervalInHCBytes,Counter64,read-only,,current,,High-capacity counter for the total number of bytes received by the PW (from the PSN).
.1.3.6.1.2.1.10.246.1.5.1.6,PW-STD-MIB::pwPerf1DayIntervalOutHCPackets,Counter64,read-only,,current,,High-capacity counter for the total number of packets forwarded by the PW (to the PSN).
.1.3.6.1.2.1.10.246.1.5.1.7,PW-STD-MIB::pwPerf1DayIntervalOutHCBytes,Counter64,read-only,,current,,High-capacity counter for the total number of bytes forwarded by the PW (to the PSN).
.1.3.6.1.2.1.10.246.1.6,PW-STD-MIB::pwPerfTotalErrorPackets,Counter32,read-only,,current,,Counter for number of errors at the PW processing level, for example, packets received with unknown PW label.
.1.3.6.1.2.1.10.246.1.7,PW-STD-MIB::pwIndexMappingTable,,not-accessible,,current,,This table enables the reverse mapping of the unique PWid parameters [peer IP, PW type, and PW ID] and the pwIndex. The table is not applicable for PWs created manually or by using the generalized FEC.
.1.3.6.1.2.1.10.246.1.7.1,PW-STD-MIB::pwIndexMappingEntry,,not-accessible,pwIndexMappingPwType:pwIndexMappingPwID:pwIndexMappingPeerAddrType:pwIndexMappingPeerAddr,current,,An entry in this table MUST be created by the agent for every PW created by the pwTable for which pwOwner equals pwIdFecSignaling and pwID is not zero. Implementers need to be aware that if the value of the pwIndexMappingPeerAddr (an OID) has more than 113 sub-identifiers, then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.10.246.1.7.1.1,PW-STD-MIB::pwIndexMappingPwType,INTEGER,not-accessible,,current,other(0):frameRelayDlciMartiniMode(1):atmAal5SduVcc(2):atmTransparent(3):ethernetTagged(4):ethernet(5):hdlc(6):ppp(7):cem(8):atmCellNto1Vcc(9):atmCellNto1Vpc(10):ipLayer2Transport(11):atmCell1to1Vcc(12):atmCell1to1Vpc(13):atmAal5PduVcc(14):frameRelayPortMode(15):cep(16):e1Satop(17):t1Satop(18):e3Satop(19):t3Satop(20):basicCesPsn(21):basicTdmIp(22):tdmCasCesPsn(23):tdmCasTdmIp(24):frDlci(25):wildcard(32767),The PW type (indicates the service) of this PW.
.1.3.6.1.2.1.10.246.1.7.1.2,PW-STD-MIB::pwIndexMappingPwID,Unsigned32,not-accessible,,current,,The PW ID of this PW. Zero if the PW is configured manually.
.1.3.6.1.2.1.10.246.1.7.1.3,PW-STD-MIB::pwIndexMappingPeerAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),IP address type of the peer node.
.1.3.6.1.2.1.10.246.1.7.1.4,PW-STD-MIB::pwIndexMappingPeerAddr,OCTET,not-accessible,,current,,IP address of the peer node.
.1.3.6.1.2.1.10.246.1.7.1.5,PW-STD-MIB::pwIndexMappingPwIndex,Unsigned32,read-only,,current,,The value that represents the PW in the pwTable.
.1.3.6.1.2.1.10.246.1.8,PW-STD-MIB::pwPeerMappingTable,,not-accessible,,current,,This table provides reverse mapping of the existing PW based on PW type and PW ID ordering. This table is typically useful for the element management system (EMS) ordered query of existing PWs.
.1.3.6.1.2.1.10.246.1.8.1,PW-STD-MIB::pwPeerMappingEntry,,not-accessible,pwPeerMappingPeerAddrType:pwPeerMappingPeerAddr:pwPeerMappingPwType:pwPeerMappingPwID,current,,An entry in this table is created by the agent for every PW entry in the pwTable. Implementers need to be aware that if the value of the pwPeerMappingPeerAddr (an OID) has more than 113 sub-identifiers, then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.10.246.1.8.1.1,PW-STD-MIB::pwPeerMappingPeerAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),IP address type of the peer node.
.1.3.6.1.2.1.10.246.1.8.1.2,PW-STD-MIB::pwPeerMappingPeerAddr,OCTET,not-accessible,,current,,IP address of the peer node.
.1.3.6.1.2.1.10.246.1.8.1.3,PW-STD-MIB::pwPeerMappingPwType,INTEGER,not-accessible,,current,other(0):frameRelayDlciMartiniMode(1):atmAal5SduVcc(2):atmTransparent(3):ethernetTagged(4):ethernet(5):hdlc(6):ppp(7):cem(8):atmCellNto1Vcc(9):atmCellNto1Vpc(10):ipLayer2Transport(11):atmCell1to1Vcc(12):atmCell1to1Vpc(13):atmAal5PduVcc(14):frameRelayPortMode(15):cep(16):e1Satop(17):t1Satop(18):e3Satop(19):t3Satop(20):basicCesPsn(21):basicTdmIp(22):tdmCasCesPsn(23):tdmCasTdmIp(24):frDlci(25):wildcard(32767),The PW type (indicates the emulated service) of this PW.
.1.3.6.1.2.1.10.246.1.8.1.4,PW-STD-MIB::pwPeerMappingPwID,Unsigned32,not-accessible,,current,,The PW ID of this PW. Zero if the PW is configured manually.
.1.3.6.1.2.1.10.246.1.8.1.5,PW-STD-MIB::pwPeerMappingPwIndex,Unsigned32,read-only,,current,,The value that represents the PW in the pwTable.
.1.3.6.1.2.1.10.246.1.9,PW-STD-MIB::pwUpDownNotifEnable,INTEGER,read-write,,current,true(1):false(2),If this object is set to true(1), then it enables the emission of pwUp and pwDown notifications; otherwise, these notifications are not emitted.
.1.3.6.1.2.1.10.246.1.10,PW-STD-MIB::pwDeletedNotifEnable,INTEGER,read-write,,current,true(1):false(2),If this object is set to true(1), then it enables the emission of pwDeleted notification; otherwise, this notification is not emitted.
.1.3.6.1.2.1.10.246.1.11,PW-STD-MIB::pwNotifRate,Unsigned32,read-write,,current,,This object defines the maximum number of PW notifications that can be emitted from the device per second.
.1.3.6.1.2.1.10.246.1.12,PW-STD-MIB::pwGenFecIndexMappingTable,,not-accessible,,current,,This table enables the reverse mapping of the unique PWid parameters [GroupAttachmentID, LocalAttachmentID, and PeerAttachmentID] and the pwIndex. The table is only applicable for PW using the generalized FEC.
.1.3.6.1.2.1.10.246.1.12.1,PW-STD-MIB::pwGenFecIndexMappingEntry,,not-accessible,pwGenFecIndexMappingAGIType:pwGenFecIndexMappingAGI:pwGenFecIndexMappingLocalAIIType:pwGenFecIndexMappingLocalAII:pwGenFecIndexMappingRemoteAIIType:pwGenFecIndexMappingRemoteAII,current,,An entry in this table MUST be created by the agent for every PW created by the pwTable for which pwOwner equals genFecSignaling. Implementers need to be aware that if the combined value of pwGenFecIndexMappingAGI, pwGenFecIndexMappingLocalAII, and pwGenFecIndexMappingRemoteAII (OIDs) has more than 113 sub-identifiers, then OIDs of column instances in this table will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.10.246.1.12.1.1,PW-STD-MIB::pwGenFecIndexMappingAGIType,Unsigned32,not-accessible,,current,,This object is the type of the attachment group identifier (AGI) that this PW belongs to.
.1.3.6.1.2.1.10.246.1.12.1.2,PW-STD-MIB::pwGenFecIndexMappingAGI,OCTET,not-accessible,,current,,This object is an octet string representing the attachment group identifier (AGI) that this PW belongs to, which typically identifies the VPN ID.
.1.3.6.1.2.1.10.246.1.12.1.3,PW-STD-MIB::pwGenFecIndexMappingLocalAIIType,Unsigned32,not-accessible,,current,,This object is the type of the local forwarder attachment individual identifier (AII) to be used by this PW.
.1.3.6.1.2.1.10.246.1.12.1.4,PW-STD-MIB::pwGenFecIndexMappingLocalAII,OCTET,not-accessible,,current,,This object is an octet string representing the local forwarder attachment individual identifier (AII) to be used by this PW. It is used as the SAII for outgoing signaling messages and the TAII in the incoming messages from the peer.
.1.3.6.1.2.1.10.246.1.12.1.5,PW-STD-MIB::pwGenFecIndexMappingRemoteAIIType,Unsigned32,not-accessible,,current,,This object is the type of the remote forwarder attachment individual identifier (AII) to be used by this PW.
.1.3.6.1.2.1.10.246.1.12.1.6,PW-STD-MIB::pwGenFecIndexMappingRemoteAII,OCTET,not-accessible,,current,,This object is an octet string representing the peer forwarder attachment individual identifier (AII) to be used by this PW. It is used as the TAII for outgoing signaling messages and the SAII in the incoming messages from the peer.
.1.3.6.1.2.1.10.246.1.12.1.7,PW-STD-MIB::pwGenFecIndexMappingPwIndex,Unsigned32,read-only,,current,,The value that represents the PW in the pwTable.
.1.3.6.1.2.1.10.246.2,PW-STD-MIB::pwConformance,,,,,,
.1.3.6.1.2.1.10.246.2.1,PW-STD-MIB::pwGroups,,,,,,
.1.3.6.1.2.1.10.246.2.1.1,PW-STD-MIB::pwBasicGroup,,,,,,Collection of objects that are required in all implementations that support the PW MIB module.
.1.3.6.1.2.1.10.246.2.1.2,PW-STD-MIB::pwPwIdGroup,,,,,,Collection of objects required for PW ID configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.3,PW-STD-MIB::pwGeneralizedFecGroup,,,,,,Collection of objects required for generalized FEC configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.4,PW-STD-MIB::pwFcsGroup,,,,,,Collection of objects required for FCS retention configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.5,PW-STD-MIB::pwFragGroup,,,,,,Collection of objects required for fragmentation configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.6,PW-STD-MIB::pwPwStatusGroup,,,,,,Collection of objects required for PW status configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.7,PW-STD-MIB::pwGetNextGroup,,,,,,Collection of objects for getting the next available index.
.1.3.6.1.2.1.10.246.2.1.8,PW-STD-MIB::pwPriorityGroup,,,,,,Collection of objects for controlling the PW setup and holding priority.
.1.3.6.1.2.1.10.246.2.1.9,PW-STD-MIB::pwAttachmentGroup,,,,,,Collection of objects for PW configuration as ifIndex.
.1.3.6.1.2.1.10.246.2.1.10,PW-STD-MIB::pwPerformanceGeneralGroup,,,,,,Collection of general objects needed for managing the total running performance parameters.
.1.3.6.1.2.1.10.246.2.1.11,PW-STD-MIB::pwPeformance1DayIntervalGroup,,,,,,Collection of objects needed for a PW running 1-day interval performance collection.
.1.3.6.1.2.1.10.246.2.1.12,PW-STD-MIB::pwPerformanceIntervalGeneralGroup,,,,,,Collection of general objects needed for managing the interval performance parameters.
.1.3.6.1.2.1.10.246.2.1.13,PW-STD-MIB::pwPeformanceIntervalGroup,,,,,,Collection of 32-bit objects needed for PW performance collection in 15-minute intervals.
.1.3.6.1.2.1.10.246.2.1.14,PW-STD-MIB::pwHCPeformanceIntervalGroup,,,,,,Collection of HC objects needed for PW performance collection in 15-minute intervals.
.1.3.6.1.2.1.10.246.2.1.15,PW-STD-MIB::pwMappingTablesGroup,,,,,,Collection of objects contained in the reverse mapping tables.
.1.3.6.1.2.1.10.246.2.1.16,PW-STD-MIB::pwNotificationControlGroup,,,,,,Collection of objects for controlling the PW notifications.
.1.3.6.1.2.1.10.246.2.1.17,PW-STD-MIB::pwNotificationGroup,,,,,,Collection of PW notifications objects.
.1.3.6.1.2.1.10.246.2.1.18,PW-STD-MIB::pwSignalingGroup,,,,,,Collection of objects for use in implementations that support the PW signaling.
.1.3.6.1.2.1.10.246.2.2,PW-STD-MIB::pwCompliances,,,,,,
.1.3.6.1.2.1.10.246.2.2.1,PW-STD-MIB::pwModuleFullCompliance,,,,,,The compliance statement for agents that provide full support for the PW MIB module. Such devices can then be monitored and configured using this MIB module.
.1.3.6.1.2.1.10.246.2.2.2,PW-STD-MIB::pwModuleReadOnlyCompliance,,,,,,The compliance statement for agents that provide read- only support for the PW MIB module. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.251,VDSL2-LINE-MIB::vdsl2MIB,,,,,, This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community for the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines. The MIB module described in RFC 2662 [RFC2662] defines objects used for managing Asymmetric Bit-Rate DSL (ADSL) interfaces per [T1E1.413], [G.992.1], and [G.992.2]. These object descriptions are based upon the specifications for the ADSL Embedded Operations Channel (EOC) as defined in American National Standards Institute (ANSI) T1E1.413 [T1E1.413] and International Telecommunication Union (ITU-T) G.992.1 [G.992.1] and G.992.2 [G.992.2]. The MIB module described in RFC 4706 [RFC4706] defines objects used for managing ADSL2 interfaces per [G.992.3] and [G.992.4], and ADSL2+ interfaces per [G.992.5]. That MIB is also capable of managing ADSL interfaces per [T1E1.413], [G.992.1], and [G.992.2]. This document does not obsolete RFC 2662 [RFC2662] or RFC 4706 [RFC4706], but rather provides a more comprehensive management model that manages VDSL2 interfaces per G.993.2 [G.993.2] as well as ADSL, ADSL2, and ADSL2+ technologies per T1E1.413, G.992.1, G.992.2, G.992.3, G.992.4, and G.992.5 ([T1E1.413], [G.992.1], [G.992.2], [G.992.3], [G.992.4], and [G.992.5], respectively). Additionally, the management framework for VDSL2 lines specified by the Digital Subscriber Line Forum (DSLF) has been taken into consideration [TR-129]. That framework is based on the ITU-T G.997.1 standard [G.997.1] and its amendment 1 [G.997.1-Am1]. The MIB module is located in the MIB tree under MIB 2 transmission, as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of this document. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5650; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.251.0,VDSL2-LINE-MIB::xdsl2Notifications,,,,,,
.1.3.6.1.2.1.10.251.0.1,VDSL2-LINE-MIB::xdsl2LinePerfFECSThreshXtuc,,,,,,This notification indicates that the FEC seconds threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.2,VDSL2-LINE-MIB::xdsl2LinePerfFECSThreshXtur,,,,,,This notification indicates that the FEC seconds threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.3,VDSL2-LINE-MIB::xdsl2LinePerfESThreshXtuc,,,,,,This notification indicates that the errored seconds threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.4,VDSL2-LINE-MIB::xdsl2LinePerfESThreshXtur,,,,,,This notification indicates that the errored seconds threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.5,VDSL2-LINE-MIB::xdsl2LinePerfSESThreshXtuc,,,,,,This notification indicates that the severely errored seconds threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.6,VDSL2-LINE-MIB::xdsl2LinePerfSESThreshXtur,,,,,,This notification indicates that the severely errored seconds threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.7,VDSL2-LINE-MIB::xdsl2LinePerfLOSSThreshXtuc,,,,,,This notification indicates that the LOS seconds threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.8,VDSL2-LINE-MIB::xdsl2LinePerfLOSSThreshXtur,,,,,,This notification indicates that the LOS seconds threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.9,VDSL2-LINE-MIB::xdsl2LinePerfUASThreshXtuc,,,,,,This notification indicates that the unavailable seconds threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.10,VDSL2-LINE-MIB::xdsl2LinePerfUASThreshXtur,,,,,,This notification indicates that the unavailable seconds threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.11,VDSL2-LINE-MIB::xdsl2LinePerfCodingViolationsThreshXtuc,,,,,,This notification indicates that the coding violations threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.12,VDSL2-LINE-MIB::xdsl2LinePerfCodingViolationsThreshXtur,,,,,,This notification indicates that the coding violations threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.13,VDSL2-LINE-MIB::xdsl2LinePerfCorrectedThreshXtuc,,,,,,This notification indicates that the corrected blocks (FEC events) threshold has been reached/exceeded for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.14,VDSL2-LINE-MIB::xdsl2LinePerfCorrectedThreshXtur,,,,,,This notification indicates that the corrected blocks (FEC events) threshold has been reached/exceeded for the referred xTU-R.
.1.3.6.1.2.1.10.251.0.15,VDSL2-LINE-MIB::xdsl2LinePerfFailedFullInitThresh,,,,,,This notification indicates that the failed full initializations threshold has been reached/exceeded for the referred ADSL/ADSL2 or ADSL2 line.
.1.3.6.1.2.1.10.251.0.16,VDSL2-LINE-MIB::xdsl2LinePerfFailedShortInitThresh,,,,,,This notification indicates that the failed short initializations threshold has been reached/exceeded for the referred VDSL2/ADSL/ADSL2 or ADSL2+ line.
.1.3.6.1.2.1.10.251.0.17,VDSL2-LINE-MIB::xdsl2LineStatusChangeXtuc,,,,,,This notification indicates that a status change is detected for the referred xTU-C.
.1.3.6.1.2.1.10.251.0.18,VDSL2-LINE-MIB::xdsl2LineStatusChangeXtur,,,,,,This notification indicates that a status change is detected for the referred xTU-R.
.1.3.6.1.2.1.10.251.1,VDSL2-LINE-MIB::xdsl2Objects,,,,,,
.1.3.6.1.2.1.10.251.1.1,VDSL2-LINE-MIB::xdsl2Line,,,,,,
.1.3.6.1.2.1.10.251.1.1.1,VDSL2-LINE-MIB::xdsl2LineTable,,not-accessible,,current,,The table xdsl2LineTable contains configuration, command and status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line. Several objects in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.1.1.1,VDSL2-LINE-MIB::xdsl2LineEntry,,not-accessible,ifIndex,current,,The index of this table is an interface index where the interface has an ifType of vdsl2(251).
.1.3.6.1.2.1.10.251.1.1.1.1.1,VDSL2-LINE-MIB::xdsl2LineConfTemplate,OCTET,read-write,,current,,The value of this object identifies the row in the xDSL2 Line Configuration Template Table, xdsl2LineConfTemplateTable, that applies for this line. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.1.1.1.2,VDSL2-LINE-MIB::xdsl2LineConfFallbackTemplate,OCTET,read-write,,current,,This object is used to identify the template that will be used if the xDSL2 line fails to operate using the primary template. The primary template is identified using the xdsl2LineConfTemplate object. For example, a xDSL2 line may fall back to a template with a lower rate if the rate specified in the primary template cannot be achieved. The value of this object identifies a row in the xDSL2 Line Configuration Template Table, xdsl2LineConfTemplateTable. Any row in the xdsl2LineConfTemplateTable table may be used as a fall-back template. If the xDSL2 line fails to operate using the fall-back template, then the primary template should be retried. The xTU-C should continue to alternate between the primary and fall-back templates until one of them succeeds. If the value of this object is a zero-length string, then no fall-back template is defined and only the primary template will be used. Note that implementation of this object is not mandatory. If this object is not supported, any attempt to modify this object should result in the SET request being rejected. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.1.1.1.3,VDSL2-LINE-MIB::xdsl2LineAlarmConfTemplate,OCTET,read-write,,current,,The value of this object identifies the row in the xDSL2 Line Alarm Configuration Template Table, xdsl2LineAlarmConfTemplateTable, which applies to this line. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.1.1.1.4,VDSL2-LINE-MIB::xdsl2LineCmndConfPmsf,INTEGER,read-write,,current,l3toL0(0):l0toL2(2):l0orL2toL3(3),Power management state forced (PMSF). Defines the line states to be forced by the near-end xTU on this line. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.1.1.1.5,VDSL2-LINE-MIB::xdsl2LineCmndConfLdsf,INTEGER,read-write,,current,inhibit(0):force(1),Loop diagnostic state forced (LDSF). Defines whether the line should be forced into the loop diagnostics mode by the near-end xTU of this line. Note that a loop diagnostic may be initiated by the far-end xTU at any time. Only when the xdsl2LineStatusPwrMngState object is in the 'l3' state and the xdsl2LineCmndConfPmsf object is in the 'l0orL2toL3' state, can the line be forced into loop diagnostic mode procedures. Upon successful completion of the loop diagnostic mode procedures, the Access Node shall set this object to 'inhibit', and xdsl2LineStatusPwrMngState will remain in the 'l3' state. The loop diagnostic data shall be available at least until xdsl2LineCmndConfPmsf is set to the 'l3toL0' state. The results of the loop diagnostic procedure are stored in the tables xdsl2SCStatusTable, xdsl2SCStatusBandTable, and xdsl2SCStatusSegmentTable. The status of the loop diagnostic procedure is indicated by xdsl2LineCmndConfLdsfFailReason. As long as loop diagnostic procedures are not completed successfully, attempts shall be made to do so, until the loop diagnostic mode is no longer forced on the line through this configuration parameter.
.1.3.6.1.2.1.10.251.1.1.1.1.6,VDSL2-LINE-MIB::xdsl2LineCmndConfLdsfFailReason,INTEGER,read-only,,current,none(1):success(2):inProgress(3):unsupported(4):cannotRun(5):aborted(6):failed(7):illegalMode(8):adminUp(9):tableFull(10):noResources(11),The status of the most recent occasion when the loop diagnostics state forced (LDSF) command was issued for the associated line.
.1.3.6.1.2.1.10.251.1.1.1.1.7,VDSL2-LINE-MIB::xdsl2LineCmndConfBpsc,INTEGER,read-write,,current,idle(1):measure(2),Request a bits-per-subcarrier measurement to be made. A request for a bits-per-subcarrier measurement is made by setting this object to the value of 'measure'. Upon completion of the measurement request, the Access Node shall set this object to 'idle'. The SNMP agent should allow initiating a bits-per-subcarrier measurement process only if there is no other bits-per-subcarrier measurement already running, and respond with an SNMP error (e.g., wrongValue) otherwise. Note that a bits-per-subcarrier measurement is also performed during a line diagnostic procedure. This object provides an additional mechanism to fetch the bits-per-subcarrier data. This additional mechanism is provided so that bits-per-subcarrier data may be fetched without forcing the line into no power state. This is useful because the bits-per-subcarrier allocation may be adjusted at show time due to rate adaption and bit swapping. The implementation of this additional mechanism for measuring bits per subcarrier is not mandatory. The results of the bits-per-subcarrier measurement are stored in xdsl2LineSegmentTable. The status of the bits-per-subcarrier measurement is indicated by xdsl2LineCmndConfBpscFailReason.
.1.3.6.1.2.1.10.251.1.1.1.1.8,VDSL2-LINE-MIB::xdsl2LineCmndConfBpscFailReason,INTEGER,read-only,,current,none(1):success(2):inProgress(3):unsupported(4):failed(5):noResources(6),The status of the most recent bits-per-subcarrier measurement request issued for the associated line.
.1.3.6.1.2.1.10.251.1.1.1.1.9,VDSL2-LINE-MIB::xdsl2LineCmndConfBpscRequests,Counter32,read-only,,current,,Measurement request counter. This counter is incremented by one every time a request for a bits-per-subcarrier measurement is made. A measurement request is made by modifying the xdsl2LineCmndConfBpsc object from idle(1) to the value measure(2). The measurement results may be very large and will not fit into a single PDU; hence, multiple SNMP GET requests may be required to fetch the measurement results. Because the measurement results cannot be fetched atomically, it is possible for a second manager to start a new measurement before a first manager has fetched all of its results. An SNMP manager can use this object to ensure that the measurement results retrieved using one or more GET requests all belong to the measurement initiated by that manager. The following steps are suggested in order for the SNMP manager to initiate the bits-per-subcarrier measurement: 1. Wait for xdsl2LineCmndConfBpsc value to be idle(1). 2. Perform an SNMP GET for xdsl2LineCmndConfBpscRequests. 3. Wait a short delay (4 -> 8 seconds). 4. Perform an SNMP SET on xdsl2LineCmndConfBpsc with the value measure(2). 5. If step 4 returns an error, then go to step 1. 6. Wait for xdsl2LineCmndConfBpsc value to be idle(1). 7. Fetch measurement results using one or more GET PDUs. 8. Perform an SNMP GET for xdsl2LineCmndConfBpscRequests. 9. Compute the difference between the two values of xdsl2LineCmndConfBpscRequests. If the value is one, then the results are valid, else go to step 1.
.1.3.6.1.2.1.10.251.1.1.1.1.10,VDSL2-LINE-MIB::xdsl2LineCmndAutomodeColdStart,INTEGER,read-write,,current,true(1):false(2),Automode cold start forced. This parameter is defined in order to improve testing of the performance of xTUs supporting automode when it is enabled in the MIB. Change the value of this parameter to 'true' to indicate a change in loop conditions applied to the devices under the test. The xTUs shall reset any historical information used for automode and for shortening G.994.1 handshake and initialization. Automode is the case where multiple operation-modes are enabled through the xdsl2LConfProfXtuTransSysEna object in the line configuration profile being used for the line, and where the selection of the actual operation-mode depends not only on the common capabilities of both xTUs (as exchanged in G.994.1), but also on achievable data rates under given loop conditions.
.1.3.6.1.2.1.10.251.1.1.1.1.11,VDSL2-LINE-MIB::xdsl2LineCmndConfReset,INTEGER,read-write,,current,idle(1):reset(2),Request a line reset to occur. If this object is set to the value of 'reset', then force the line to reset (i.e., the modems will retrain). When the line has successfully reset, the SNMP agent will set the value of this object to 'idle'. Note that the xdsl2LineCmndConfPmsf object will always take precedence over this object. If the xdsl2LineCmndConfPmsf object is set to the value 'l0orL2toL3', then the line MUST NOT return to the Showtime state due to a reset request action performed using this object.
.1.3.6.1.2.1.10.251.1.1.1.1.12,VDSL2-LINE-MIB::xdsl2LineStatusActTemplate,OCTET,read-only,,current,,This object is used to identify the template that is currently in use for this line. This object is updated when a successful line initialization occurs. This object indicates if the primary template (xdsl2LineConfTemplate) is in use or the fall-back template (xdsl2LineConfFallbackTemplate) is in use. If the line is not successfully initialized, then the value of this object will be a zero-length string.
.1.3.6.1.2.1.10.251.1.1.1.1.13,VDSL2-LINE-MIB::xdsl2LineStatusXtuTransSys,BITS,read-only,,current,ansit1413(0):etsi(1):g9921PotsNonOverlapped(2):g9921PotsOverlapped(3):g9921IsdnNonOverlapped(4):g9921isdnOverlapped(5):g9921tcmIsdnNonOverlapped(6):g9921tcmIsdnOverlapped(7):g9922potsNonOverlapped(8):g9922potsOverlapped(9):g9922tcmIsdnNonOverlapped(10):g9922tcmIsdnOverlapped(11):g9921tcmIsdnSymmetric(12):reserved1(13):reserved2(14):reserved3(15):reserved4(16):reserved5(17):g9923PotsNonOverlapped(18):g9923PotsOverlapped(19):g9923IsdnNonOverlapped(20):g9923isdnOverlapped(21):reserved6(22):reserved7(23):g9924potsNonOverlapped(24):g9924potsOverlapped(25):reserved8(26):reserved9(27):g9923AnnexIAllDigNonOverlapped(28):g9923AnnexIAllDigOverlapped(29):g9923AnnexJAllDigNonOverlapped(30):g9923AnnexJAllDigOverlapped(31):g9924AnnexIAllDigNonOverlapped(32):g9924AnnexIAllDigOverlapped(33):g9923AnnexLMode1NonOverlapped(34):g9923AnnexLMode2NonOverlapped(35):g9923AnnexLMode3Overlapped(36):g9923AnnexLMode4Overlapped(37):g9923AnnexMPotsNonOverlapped(38):g9923AnnexMPotsOverlapped(39):g9925PotsNonOverlapped(40):g9925PotsOverlapped(41):g9925IsdnNonOverlapped(42):g9925isdnOverlapped(43):reserved10(44):reserved11(45):g9925AnnexIAllDigNonOverlapped(46):g9925AnnexIAllDigOverlapped(47):g9925AnnexJAllDigNonOverlapped(48):g9925AnnexJAllDigOverlapped(49):g9925AnnexMPotsNonOverlapped(50):g9925AnnexMPotsOverlapped(51):reserved12(52):reserved13(53):reserved14(54):reserved15(55):g9932AnnexA(56):g9932AnnexB(57):g9932AnnexC(58):reserved16(59):reserved17(60):reserved18(61):reserved19(62):reserved20(63),The xTU Transmission System (xTS) in use. It is coded in a bitmap representation with one bit set to '1' (the selected coding for the DSL line). This parameter may be derived from the handshaking procedures defined in Recommendation G.994.1. A set of xDSL line transmission modes, with one bit per mode.
.1.3.6.1.2.1.10.251.1.1.1.1.14,VDSL2-LINE-MIB::xdsl2LineStatusPwrMngState,INTEGER,read-only,,current,l0(1):l1(2):l2(3):l3(4),The current power management state.
.1.3.6.1.2.1.10.251.1.1.1.1.15,VDSL2-LINE-MIB::xdsl2LineStatusInitResult,INTEGER,read-only,,current,noFail(0):configError(1):configNotFeasible(2):commFail(3):noPeerAtu(4):otherCause(5),Indicates the result of the last full initialization performed on the line.
.1.3.6.1.2.1.10.251.1.1.1.1.16,VDSL2-LINE-MIB::xdsl2LineStatusLastStateDs,INTEGER,read-only,,current,atucG9941(0):atucQuiet1(1):atucComb1(2):atucQuiet2(3):atucComb2(4):atucIcomb1(5):atucLineprob(6):atucQuiet3(7):atucComb3(8):atucIComb2(9):atucMsgfmt(10):atucMsgpcb(11):atucQuiet4(12):atucReverb1(13):atucTref1(14):atucReverb2(15):atucEct(16):atucReverb3(17):atucTref2(18):atucReverb4(19):atucSegue1(20):atucMsg1(21):atucReverb5(22):atucSegue2(23):atucMedley(24):atucExchmarker(25):atucMsg2(26):atucReverb6(27):atucSegue3(28):atucParams(29):atucReverb7(30):atucSegue4(31):atucShowtime(32):aturG9941(100):aturQuiet1(101):aturComb1(102):aturQuiet2(103):aturComb2(104):aturIcomb1(105):aturLineprob(106):aturQuiet3(107):aturComb3(108):aturIcomb2(109):aturMsgfmt(110):aturMsgpcb(111):aturReverb1(112):aturQuiet4(113):aturReverb2(114):aturQuiet5(115):aturReverb3(116):aturEct(117):aturReverb4(118):aturSegue1(119):aturReverb5(120):aturSegue2(121):aturMsg1(122):aturMedley(123):aturExchmarker(124):aturMsg2(125):aturReverb6(126):aturSegue3(127):aturParams(128):aturReverb7(129):aturSegue4(130):aturShowtime(131):vtucG9941(200):vtucQuiet1(201):vtucChDiscov1(202):vtucSynchro1(203):vtucPilot1(204):vtucQuiet2(205):vtucPeriodic1(206):vtucSynchro2(207):vtucChDiscov2(208):vtucSynchro3(209):vtucTraining1(210):vtucSynchro4(211):vtucPilot2(212):vtucTeq(213):vtucEct(214):vtucPilot3(215):vtucPeriodic2(216):vtucTraining2(217):vtucSynchro5(218):vtucMedley(219):vtucSynchro6(220):vtucShowtime(221):vturG9941(300):vturQuiet1(301):vturChDiscov1(302):vturSynchro1(303):vturLineprobe(304):vturPeriodic1(305):vturSynchro2(306):vturChDiscov2(307):vturSynchro3(308):vturQuiet2(309):vturTraining1(310):vturSynchro4(311):vturTeq(312):vturQuiet3(313):vturEct(314):vturPeriodic2(315):vturTraining2(316):vturSynchro5(317):vturMedley(318):vturSynchro6(319):vturShowtime(320),The last successful transmitted initialization state in the downstream direction in the last full initialization performed on the line.
.1.3.6.1.2.1.10.251.1.1.1.1.17,VDSL2-LINE-MIB::xdsl2LineStatusLastStateUs,INTEGER,read-only,,current,atucG9941(0):atucQuiet1(1):atucComb1(2):atucQuiet2(3):atucComb2(4):atucIcomb1(5):atucLineprob(6):atucQuiet3(7):atucComb3(8):atucIComb2(9):atucMsgfmt(10):atucMsgpcb(11):atucQuiet4(12):atucReverb1(13):atucTref1(14):atucReverb2(15):atucEct(16):atucReverb3(17):atucTref2(18):atucReverb4(19):atucSegue1(20):atucMsg1(21):atucReverb5(22):atucSegue2(23):atucMedley(24):atucExchmarker(25):atucMsg2(26):atucReverb6(27):atucSegue3(28):atucParams(29):atucReverb7(30):atucSegue4(31):atucShowtime(32):aturG9941(100):aturQuiet1(101):aturComb1(102):aturQuiet2(103):aturComb2(104):aturIcomb1(105):aturLineprob(106):aturQuiet3(107):aturComb3(108):aturIcomb2(109):aturMsgfmt(110):aturMsgpcb(111):aturReverb1(112):aturQuiet4(113):aturReverb2(114):aturQuiet5(115):aturReverb3(116):aturEct(117):aturReverb4(118):aturSegue1(119):aturReverb5(120):aturSegue2(121):aturMsg1(122):aturMedley(123):aturExchmarker(124):aturMsg2(125):aturReverb6(126):aturSegue3(127):aturParams(128):aturReverb7(129):aturSegue4(130):aturShowtime(131):vtucG9941(200):vtucQuiet1(201):vtucChDiscov1(202):vtucSynchro1(203):vtucPilot1(204):vtucQuiet2(205):vtucPeriodic1(206):vtucSynchro2(207):vtucChDiscov2(208):vtucSynchro3(209):vtucTraining1(210):vtucSynchro4(211):vtucPilot2(212):vtucTeq(213):vtucEct(214):vtucPilot3(215):vtucPeriodic2(216):vtucTraining2(217):vtucSynchro5(218):vtucMedley(219):vtucSynchro6(220):vtucShowtime(221):vturG9941(300):vturQuiet1(301):vturChDiscov1(302):vturSynchro1(303):vturLineprobe(304):vturPeriodic1(305):vturSynchro2(306):vturChDiscov2(307):vturSynchro3(308):vturQuiet2(309):vturTraining1(310):vturSynchro4(311):vturTeq(312):vturQuiet3(313):vturEct(314):vturPeriodic2(315):vturTraining2(316):vturSynchro5(317):vturMedley(318):vturSynchro6(319):vturShowtime(320),The last successful transmitted initialization state in the upstream direction in the last full initialization performed on the line.
.1.3.6.1.2.1.10.251.1.1.1.1.18,VDSL2-LINE-MIB::xdsl2LineStatusXtur,BITS,read-only,,current,noDefect(0):lossOfFraming(1):lossOfSignal(2):lossOfPower(3):initFailure(4),Indicates the current state (existing failures) of the xTU-R. This is a bitmap of possible conditions.
.1.3.6.1.2.1.10.251.1.1.1.1.19,VDSL2-LINE-MIB::xdsl2LineStatusXtuc,BITS,read-only,,current,noDefect(0):lossOfFraming(1):lossOfSignal(2):lossOfPower(3):initFailure(4),Indicates the current state (existing failures) of the xTU-C. This is a bitmap of possible conditions.
.1.3.6.1.2.1.10.251.1.1.1.1.20,VDSL2-LINE-MIB::xdsl2LineStatusAttainableRateDs,Unsigned32,read-only,,current,,Maximum Attainable Data Rate Downstream. The maximum downstream net data rate currently attainable by the xTU-C transmitter and the xTU-R receiver, coded in bit/s.
.1.3.6.1.2.1.10.251.1.1.1.1.21,VDSL2-LINE-MIB::xdsl2LineStatusAttainableRateUs,Unsigned32,read-only,,current,,Maximum Attainable Data Rate Upstream. The maximum upstream net data rate currently attainable by the xTU-R transmitter and the xTU-C receiver, coded in bit/s.
.1.3.6.1.2.1.10.251.1.1.1.1.22,VDSL2-LINE-MIB::xdsl2LineStatusActPsdDs,Integer32,read-only,,current,,Actual Power Spectral Density (PSD) Downstream. The average downstream transmit PSD over the subcarriers used for downstream. It ranges from -900 to 0 units of 0.1 dBm/Hz (physical values are -90 to 0 dBm/Hz). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.251.1.1.1.1.23,VDSL2-LINE-MIB::xdsl2LineStatusActPsdUs,Integer32,read-only,,current,,Actual Power Spectral Density (PSD) Upstream. The average upstream transmit PSD over the subcarriers used for upstream. It ranges from -900 to 0 units of 0.1 dBm/Hz (physical values are -90 to 0 dBm/Hz). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.251.1.1.1.1.24,VDSL2-LINE-MIB::xdsl2LineStatusActAtpDs,Integer32,read-only,,current,,Actual Aggregate Transmit Power Downstream. The total amount of transmit power delivered by the xTU-C at the U-C reference point, at the instant of measurement. It ranges from -310 to 310 units of 0.1 dBm (physical values are -31 to 31 dBm). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.251.1.1.1.1.25,VDSL2-LINE-MIB::xdsl2LineStatusActAtpUs,Integer32,read-only,,current,,Actual Aggregate Transmit Power Upstream. The total amount of transmit power delivered by the xTU-R at the U-R reference point, at the instant of measurement. It ranges from -310 to 310 units of 0.1 dBm (physical values are -31 to 31 dBm). A value of 0x7FFFFFFF (2147483647) indicates the measurement is out of range to be represented.
.1.3.6.1.2.1.10.251.1.1.1.1.26,VDSL2-LINE-MIB::xdsl2LineStatusActProfile,BITS,read-only,,current,profile8a(0):profile8b(1):profile8c(2):profile8d(3):profile12a(4):profile12b(5):profile17a(6):profile30a(7),The G.993.2 profile in use. The configuration parameter xdsl2LConfProfProfiles defines the set of allowed G.993.2 profiles. This parameter indicates the profile in use on this line. This parameter may be derived from the handshaking procedures defined in ITU-T Recommendation G.994.1.
.1.3.6.1.2.1.10.251.1.1.1.1.27,VDSL2-LINE-MIB::xdsl2LineStatusActLimitMask,BITS,read-only,,current,profile8Limit1(0):profile8Limit2(1):profile8Limit3(2):profile8Limit4(3):profile8Limit5(4):profile8Limit6(5):profile8Limit7(6):profile8Limit8(7):profile8Limit9(8):profile8Limit10(9):profile8Limit11(10):profile8Limit12(11):profile8Limit13(12):profile8Limit14(13):profile8Limit15(14):profile8Limit16(15):profile12Limit1(16):profile12Limit2(17):profile12Limit3(18):profile12Limit4(19):profile12Limit5(20):profile12Limit6(21):profile12Limit7(22):profile12Limit8(23):profile12Limit9(24):profile12Limit10(25):profile12Limit11(26):profile12Limit12(27):profile12Limit13(28):profile12Limit14(29):profile12Limit15(30):profile12Limit16(31):profile17Limit1(32):profile17Limit2(33):profile17Limit3(34):profile17Limit4(35):profile17Limit5(36):profile17Limit6(37):profile17Limit7(38):profile17Limit8(39):profile17Limit9(40):profile17Limit10(41):profile17Limit11(42):profile17Limit12(43):profile17Limit13(44):profile17Limit14(45):profile17Limit15(46):profile17Limit16(47):profile30Limit1(48):profile30Limit2(49):profile30Limit3(50):profile30Limit4(51):profile30Limit5(52):profile30Limit6(53):profile30Limit7(54):profile30Limit8(55):profile30Limit9(56):profile30Limit10(57):profile30Limit11(58):profile30Limit12(59):profile30Limit13(60):profile30Limit14(61):profile30Limit15(62):profile30Limit16(63),The Limit PSD mask and band plan in use. The configuration parameter xdsl2LConfProfLimitMask defines the set of allowed G.993.2 limit PSD masks. This parameter indicates the limit PSD mask in use on this line.
.1.3.6.1.2.1.10.251.1.1.1.1.28,VDSL2-LINE-MIB::xdsl2LineStatusActUs0Mask,BITS,read-only,,current,eu32(0):eu36(1):eu40(2):eu44(3):eu48(4):eu52(5):eu56(6):eu60(7):eu64(8):eu128(9):reserved1(10):reserved2(11):reserved3(12):reserved4(13):reserved5(14):reserved6(15):adlu32(16):adlu36(17):adlu40(18):adlu44(19):adlu48(20):adlu52(21):adlu56(22):adlu60(23):adlu64(24):adlu128(25):reserved7(26):reserved8(27):reserved9(28):reserved10(29):reserved11(30):reserved12(31),The US0 PSD mask in use. The configuration parameter xdsl2LConfProfUs0Mask defines the set of allowed US0 PSD masks. This parameter indicates the US0 PSD mask in use on this line. This parameter may be derived from the handshaking procedures defined in ITU-T Recommendation G.994.1.
.1.3.6.1.2.1.10.251.1.1.1.1.29,VDSL2-LINE-MIB::xdsl2LineStatusActSnrModeDs,INTEGER,read-only,,current,virtualNoiseDisabled(1):virtualNoiseEnabled(2),This parameter indicates if the transmitter-referred virtual noise is active on the line in the downstream direction. The configuration parameter xdsl2LConfProfSnrModeDs is used to configure referred virtual noise.
.1.3.6.1.2.1.10.251.1.1.1.1.30,VDSL2-LINE-MIB::xdsl2LineStatusActSnrModeUs,INTEGER,read-only,,current,virtualNoiseDisabled(1):virtualNoiseEnabled(2),This parameter indicates if the transmitter-referred virtual noise is active on the line in the upstream direction. The configuration parameter xdsl2LConfProfSnrModeUs is used to configure referred virtual noise.
.1.3.6.1.2.1.10.251.1.1.1.1.31,VDSL2-LINE-MIB::xdsl2LineStatusElectricalLength,Unsigned32,read-only,,current,,This parameter contains the estimated electrical length expressed in dB at 1 MHz, kl0. This is the final electrical length that would have been sent from the VTU-O to VTU-R if the electrical length was not forced by the CO-MIB. The value ranges from 0 to 128 dB in steps of 0.1 dB.
.1.3.6.1.2.1.10.251.1.1.1.1.32,VDSL2-LINE-MIB::xdsl2LineStatusTssiDs,OCTET,read-only,,current,,The transmit spectrum shaping (TSSi) breakpoints expressed as the set of breakpoints exchanged during G.994.1 (Downstream).
.1.3.6.1.2.1.10.251.1.1.1.1.33,VDSL2-LINE-MIB::xdsl2LineStatusTssiUs,OCTET,read-only,,current,,The transmit spectrum shaping (TSSi) breakpoints expressed as the set of breakpoints exchanged during G.994.1 (Upstream).
.1.3.6.1.2.1.10.251.1.1.1.1.34,VDSL2-LINE-MIB::xdsl2LineStatusMrefPsdDs,OCTET,read-only,,current,,The MEDLEY Reference PSD status parameters in the downstream direction expressed as the set of breakpoints exchanged at initialization.
.1.3.6.1.2.1.10.251.1.1.1.1.35,VDSL2-LINE-MIB::xdsl2LineStatusMrefPsdUs,OCTET,read-only,,current,,The MEDLEY Reference PSD status parameters in the upstream direction expressed as the set of breakpoints exchanged at initialization.
.1.3.6.1.2.1.10.251.1.1.1.1.36,VDSL2-LINE-MIB::xdsl2LineStatusTrellisDs,INTEGER,read-only,,current,true(1):false(2),This parameter reports whether trellis coding is in use in the downstream direction.
.1.3.6.1.2.1.10.251.1.1.1.1.37,VDSL2-LINE-MIB::xdsl2LineStatusTrellisUs,INTEGER,read-only,,current,true(1):false(2),This parameter reports whether trellis coding is in use in the upstream direction.
.1.3.6.1.2.1.10.251.1.1.1.1.38,VDSL2-LINE-MIB::xdsl2LineStatusActualCe,Unsigned32,read-only,,current,,(ACTUALCE) This parameter reports the cyclic extension used on the line. It is coded as an unsigned integer from 2 to 16 in units of N/32 samples, where 2N is the Inverse Discrete Fourier Transform (IDFT) size.
.1.3.6.1.2.1.10.251.1.1.2,VDSL2-LINE-MIB::xdsl2LineBandTable,,not-accessible,,current,,The table xdsl2LineBandTable contains the, per-band line status parameters of the VDSL2/ADSL/ADSL2 or ADSL2+ line. The parameters in this table are updated at line initialization time and at Showtime.
.1.3.6.1.2.1.10.251.1.1.2.1,VDSL2-LINE-MIB::xdsl2LineBandEntry,,not-accessible,ifIndex:xdsl2LineBand,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is a per-band index covering both VDSL2 and ADSL/ADSL2/ADSL2+.
.1.3.6.1.2.1.10.251.1.1.2.1.1,VDSL2-LINE-MIB::xdsl2LineBand,INTEGER,not-accessible,,current,upstream(1):downstream(2):us0(3):ds1(4):us1(5):ds2(6):us2(7):ds3(8):us3(9):ds4(10):us4(11),Identifies the band(s) associated with this line. For ADSL/ADSL2/ADSL2+, the values 'upstream' and 'downstream' will always be present. For VDSL2, a subset of {'us0', 'ds1', 'us1' ... 'ds4', 'us4' } will always be present, together with rows for 'upstream' and 'downstream', in which only the xdsl2LineBandStatusSnrMargin object is expected to hold a valid (average) measurement.
.1.3.6.1.2.1.10.251.1.1.2.1.2,VDSL2-LINE-MIB::xdsl2LineBandStatusLnAtten,Unsigned32,read-only,,current,,Line Attenuation. When referring to a band in the downstream direction, it is the measured difference in the total power transmitted by the xTU-C and the total power received by the xTU-R over all subcarriers of that band during initialization. When referring to a band in the upstream direction, it is the measured difference in the total power transmitted by the xTU-R and the total power received by the xTU-C over all subcarriers of that band during initialization. Values range from 0 to 1270 in units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is unavailable.
.1.3.6.1.2.1.10.251.1.1.2.1.3,VDSL2-LINE-MIB::xdsl2LineBandStatusSigAtten,Unsigned32,read-only,,current,,Signal Attenuation. When referring to a band in the downstream direction, it is the measured difference in the total power transmitted by the xTU-C and the total power received by the xTU-R over all subcarriers of that band during Showtime. When referring to a band in the upstream direction, it is the measured difference in the total power transmitted by the xTU-R and the total power received by the xTU-C over all subcarriers of that band during Showtime. Values range from 0 to 1270 in units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is unavailable.
.1.3.6.1.2.1.10.251.1.1.2.1.4,VDSL2-LINE-MIB::xdsl2LineBandStatusSnrMargin,Integer32,read-only,,current,,SNR Margin is the maximum increase in dB of the noise power received at the xTU (xTU-R for a band in the downstream direction and xTU-C for a band in the upstream direction), such that the BER requirements are met for all bearer channels received at the xTU. Values range from -640 to 630 in units of 0.1 dB (physical values are -64 to 63 dB). A special value of 0x7FFFFFFF (2147483647) indicates the SNR Margin is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the SNR Margin measurement is currently unavailable.
.1.3.6.1.2.1.10.251.1.2,VDSL2-LINE-MIB::xdsl2Status,,,,,,
.1.3.6.1.2.1.10.251.1.2.1,VDSL2-LINE-MIB::xdsl2LineSegmentTable,,not-accessible,,current,,The table xdsl2LineSegmentTable contains status parameters of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers. The parameters in this table are updated when a measurement request is made using the xdsl2LineCmndConfBpsc object. Note that a bits-per-subcarrier measurement is also performed during a line diagnostic procedure. This table provides an additional mechanism to fetch the bits-per-subcarrier data. This additional mechanism is provided so that bits-per-subcarrier data may be fetched without forcing the line into no power state. This is useful because the bits-per-subcarrier allocation may be adjusted at Showtime due to rate adaption and bit swapping. The implementation of this additional mechanism for measuring bits per subcarrier is not mandatory.
.1.3.6.1.2.1.10.251.1.2.1.1,VDSL2-LINE-MIB::xdsl2LineSegmentEntry,,not-accessible,ifIndex:xdsl2LineSegmentDirection:xdsl2LineSegment,current,,The table xdsl2LineSegmentEntry contains status parameters of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers. Objects in the table refer to NSus and NSds. For G.993.2, the value of NSus and NSds are, respectively, the indices of the highest supported upstream and downstream subcarriers according to the selected implementation profile. For ADSL, NSus is equal to NSCus-1 and NSds is equal to NSCds-1. One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the transmission direction. A third index identifies the specific segment of the subcarriers status addressed.
.1.3.6.1.2.1.10.251.1.2.1.1.1,VDSL2-LINE-MIB::xdsl2LineSegmentDirection,INTEGER,not-accessible,,current,upstream(1):downstream(2),The direction of the subcarrier either upstream or downstream.
.1.3.6.1.2.1.10.251.1.2.1.1.2,VDSL2-LINE-MIB::xdsl2LineSegment,Unsigned32,not-accessible,,current,,The segment of the subcarriers status information provided by this row. Status parameters in this table are retrieved in segments. The first segment of the status information is retrieved with xdsl2LineSegment=1, the second segment is retrieved with xdsl2LineSegment=2, and so on. When a status parameter is retrieved in n segments where n<8) then, for that parameter, GET operations for the remaining segment numbers (n+1 to 8) will respond with a zero-length OCTET STRING.
.1.3.6.1.2.1.10.251.1.2.1.1.3,VDSL2-LINE-MIB::xdsl2LineSegmentBitsAlloc,OCTET,read-only,,current,,The bits allocation per subcarrier. An array of 256 octets (512 nibbles), designed for supporting up to 512 (downstream) subcarriers. When more than 512 subcarriers are supported, the status information is reported through multiple (up to 8) segments. The first segment is then used for the first 512 subcarriers. The second segment is used for the subcarriers 512 to 1023 and so on. The aggregate number of utilized nibbles in the downstream direction (in all segments) depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. The segment number is in xdsl2SCStatusSegment. Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each segment is set to a value in the range 0 to 15 to indicate that the respective downstream or upstream subcarrier j (j=(segement-1)*512+i) has the same amount of bits allocation.
.1.3.6.1.2.1.10.251.1.2.1.1.4,VDSL2-LINE-MIB::xdsl2LineSegmentRowStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Row Status. The SNMP agent will create a row in this table for storing the results of a measurement performed on the associated line, if the row does not already exist. The SNMP manager is not permitted to create rows in this table or set the row status to 'notInService'. In the first case, if the SNMP manager tries to create a new row, the SNMP agent responds with the value 'noCreation' in the error status field of the response-PDU. In the latter case, the SNMP agent responds with the value 'wrongValue' in the error status field of the response-PDU. The SNMP agent may have limited resources; therefore, if multiple rows coexist in this table, it may fail to add new rows to this table or allocate memory resources. If that occurs, the SNMP agent responds with the value 'noResources' (for the xdsl2LineCmndConfBpscFailReason object in xdsl2LineTable). The management system (the operator) may delete rows from this table according to any scheme. For example, after retrieving the results. When the SNMP manager deletes any row in this table, the SNMP agent MUST delete all rows in this table that have the same ifIndex value.
.1.3.6.1.2.1.10.251.1.2.2,VDSL2-LINE-MIB::xdsl2ChannelStatusTable,,not-accessible,,current,,The table xdsl2ChannelStatusTable contains status parameters of VDSL2/ADSL/ADSL2 or ADSL2+ channel. This table contains live data from equipment.
.1.3.6.1.2.1.10.251.1.2.2.1,VDSL2-LINE-MIB::xdsl2ChannelStatusEntry,,not-accessible,ifIndex:xdsl2ChStatusUnit,current,,One index of this table is an interface index where the interface has an ifType of a DSL channel. A second index of this table is the termination unit.
.1.3.6.1.2.1.10.251.1.2.2.1.1,VDSL2-LINE-MIB::xdsl2ChStatusUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.2.2.1.2,VDSL2-LINE-MIB::xdsl2ChStatusActDataRate,Unsigned32,read-only,,current,,The actual net data rate at which the bearer channel is operating, if in L0 power management state. In L1 or L2 states, it relates to the previous L0 state. The data rate is coded in bit/s.
.1.3.6.1.2.1.10.251.1.2.2.1.3,VDSL2-LINE-MIB::xdsl2ChStatusPrevDataRate,Unsigned32,read-only,,current,,The previous net data rate that the bearer channel was operating at just before the latest rate change event. This could be a full or short initialization, fast retrain, DRA or power management transitions, excluding transitions between L0 state and L1 or L2 states. The data rate is coded in bit/s.
.1.3.6.1.2.1.10.251.1.2.2.1.4,VDSL2-LINE-MIB::xdsl2ChStatusActDelay,Unsigned32,read-only,,current,,The actual one-way interleaving delay introduced by the PMS-TC in the direction of the bearer channel, if in L0 power management state. In L1 or L2 states, it relates to the previous L0 state. It is coded in ms (rounded to the nearest ms).
.1.3.6.1.2.1.10.251.1.2.2.1.5,VDSL2-LINE-MIB::xdsl2ChStatusActInp,Unsigned32,read-only,,current,,Actual impulse noise protection. This parameter reports the actual impulse noise protection (INP) on the bearer channel in the L0 state. In the L1 or L2 state, the parameter contains the INP in the previous L0 state. For ADSL, this value is computed according to the formula specified in the relevant Recommendation based on the actual framing parameters. For ITU-T Recommendation G.993.2, the method to report this value is according to the INPREPORT parameter. The value is coded in fractions of DMT symbols with a granularity of 0.1 symbols. The range is from 0 to 25.4. The special value of 255 indicates an ACTINP higher than 25.4.
.1.3.6.1.2.1.10.251.1.2.2.1.6,VDSL2-LINE-MIB::xdsl2ChStatusInpReport,INTEGER,read-only,,current,inpComputedUsingFormula(1):inpEstimatedByXtur(2),Impulse noise protection reporting mode.
.1.3.6.1.2.1.10.251.1.2.2.1.7,VDSL2-LINE-MIB::xdsl2ChStatusNFec,Unsigned32,read-only,,current,,Actual size of Reed-Solomon codeword. This parameter reports the actual number of Reed-Solomon redundancy bytes per codeword used in the latency path in which the bearer channel is transported. The value is coded in bytes. It ranges from 0 to 16. The value 0 indicates no Reed-Solomon coding.
.1.3.6.1.2.1.10.251.1.2.2.1.8,VDSL2-LINE-MIB::xdsl2ChStatusRFec,Unsigned32,read-only,,current,,Actual number of Reed-Solomon redundancy bytes. This parameter reports the actual number of Reed-Solomon redundancy bytes per codeword used in the latency path in which the bearer channel is transported. The value is coded in bytes. It ranges from 0 to 16. The value 0 indicates no Reed-Solomon coding.
.1.3.6.1.2.1.10.251.1.2.2.1.9,VDSL2-LINE-MIB::xdsl2ChStatusLSymb,Unsigned32,read-only,,current,,Actual number of bits per symbol. This parameter reports the actual number of bits per symbol assigned to the latency path in which the bearer channel is transported. This value does not include trellis overhead. The value is coded in bits. It ranges from 0 to 65535.
.1.3.6.1.2.1.10.251.1.2.2.1.10,VDSL2-LINE-MIB::xdsl2ChStatusIntlvDepth,Unsigned32,read-only,,current,,Actual interleaving depth. This parameter reports the actual depth of the interleaver used in the latency path in which the bearer channel is transported. The value ranges from 1 to 4096 in steps of 1. The value 1 indicates no interleaving.
.1.3.6.1.2.1.10.251.1.2.2.1.11,VDSL2-LINE-MIB::xdsl2ChStatusIntlvBlock,Unsigned32,read-only,,current,,Actual interleaving block length. This parameter reports the actual block length of the interleaver used in the latency path in which the bearer channel is transported. The value ranges from 4 to 255 in steps of 1.
.1.3.6.1.2.1.10.251.1.2.2.1.12,VDSL2-LINE-MIB::xdsl2ChStatusLPath,Unsigned32,read-only,,current,,Actual latency path. This parameter reports the index of the actual latency path in which the bearer is transported. The valid values are 0, 1, 2 and 3. For G.992.1, the FAST path shall be mapped to the latency index 0, and the INTERLEAVED path shall be mapped to the latency index 1.
.1.3.6.1.2.1.10.251.1.2.2.1.13,VDSL2-LINE-MIB::xdsl2ChStatusAtmStatus,BITS,read-only,,current,noDefect(0):noCellDelineation(1):lossOfCellDelineation(2),Indicates current state (existing failures) of the DSL channel in case its Data Path is ATM. This is a bitmap of possible conditions. In case the channel is not of ATM Data Path, the object is set to '0'.
.1.3.6.1.2.1.10.251.1.2.2.1.14,VDSL2-LINE-MIB::xdsl2ChStatusPtmStatus,BITS,read-only,,current,noDefect(0):outOfSync(1),Indicates current state (existing failures) of the DSL channel in case its Data Path is PTM (Packet Transfer Mode). This is a bitmap of possible conditions. In case the channel is not of PTM Data Path, the object is set to '0'.
.1.3.6.1.2.1.10.251.1.2.3,VDSL2-LINE-MIB::xdsl2SCStatusTable,,not-accessible,,current,,The table xdsl2SCStatusTable contains status parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that provide information about the size of parameters in xdsl2SCStatusSegmentTable. The parameters in this table MUST be updated after a loop diagnostic procedure, MAY be updated after a line initialization, and MAY be updated at Showtime.
.1.3.6.1.2.1.10.251.1.2.3.1,VDSL2-LINE-MIB::xdsl2SCStatusEntry,,not-accessible,ifIndex:xdsl2SCStatusDirection,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the transmission direction.
.1.3.6.1.2.1.10.251.1.2.3.1.1,VDSL2-LINE-MIB::xdsl2SCStatusDirection,INTEGER,not-accessible,,current,upstream(1):downstream(2),The direction of the subcarrier either upstream or downstream.
.1.3.6.1.2.1.10.251.1.2.3.1.2,VDSL2-LINE-MIB::xdsl2SCStatusLinScale,Unsigned32,read-only,,current,,The scale factor to be applied to the H(f) linear representation values for the respective transmission direction. This parameter is only available after a loop diagnostic procedure. It is represented as an unsigned integer in the range from 1 to 2^16-1.
.1.3.6.1.2.1.10.251.1.2.3.1.3,VDSL2-LINE-MIB::xdsl2SCStatusLinScGroupSize,Unsigned32,read-only,,current,,Number of subcarriers per group used to report the H(f) linear representation values for the respective transmission direction. The valid values are 1, 2, 4, and 8. For ADSL, this parameter is equal to one and, for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters. This parameter is only available after a loop diagnostic procedure.
.1.3.6.1.2.1.10.251.1.2.3.1.4,VDSL2-LINE-MIB::xdsl2SCStatusLogMt,Unsigned32,read-only,,current,,This parameter contains the number of symbols used to measure the Hlog(f) values. It is represented as an unsigned integer in the range from 1 to 2^16-1. After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the Hlog(f). It should correspond to the value specified in the Recommendation (e.g., the number of symbols in 1 s time interval for ITU-T Recommendation. G.992.3).
.1.3.6.1.2.1.10.251.1.2.3.1.5,VDSL2-LINE-MIB::xdsl2SCStatusLogScGroupSize,Unsigned32,read-only,,current,,Number of subcarriers per group used to report the H(f) logarithmic representation values for the respective transmission direction. The valid values are 1, 2, 4, and 8. For ADSL, this parameter is equal to 1, and for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters.
.1.3.6.1.2.1.10.251.1.2.3.1.6,VDSL2-LINE-MIB::xdsl2SCStatusQlnMt,Unsigned32,read-only,,current,,This parameter contains the number of symbols used to measure the QLN(f) values. It is an unsigned integer in the range from 1 to 2^16-1. After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the QLN(f). It should correspond to the value specified in the Recommendation (e.g., the number of symbols in 1 s time interval for ITU-T Recommendation G.992.3).
.1.3.6.1.2.1.10.251.1.2.3.1.7,VDSL2-LINE-MIB::xdsl2SCStatusQlnScGroupSize,Unsigned32,read-only,,current,,Number of subcarriers per group used to report the Quiet Line Noise values for the respective transmission direction. The valid values are 1, 2, 4, and 8. For ADSL, this parameter is equal to 1, and for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters.
.1.3.6.1.2.1.10.251.1.2.3.1.8,VDSL2-LINE-MIB::xdsl2SCStatusSnrMtime,Unsigned32,read-only,,current,,This parameter contains the number of symbols used to measure the SNR(f) values. It is an unsigned integer in the range from 1 to 2^16-1. After a loop diagnostic procedure, this parameter shall contain the number of symbols used to measure the SNR(f). It should correspond to the value specified in the Recommendation (e.g., the number of symbols in 1 s time interval for ITU-T Recommendation G.992.3).
.1.3.6.1.2.1.10.251.1.2.3.1.9,VDSL2-LINE-MIB::xdsl2SCStatusSnrScGroupSize,Unsigned32,read-only,,current,,Number of subcarriers per group used to report the SNR values on the respective transmission direction. The valid values are 1, 2, 4, and 8. For ADSL, this parameter is equal to 1, and for VDSL2, it is equal to the size of a subcarrier group used to compute these parameters.
.1.3.6.1.2.1.10.251.1.2.3.1.10,VDSL2-LINE-MIB::xdsl2SCStatusAttainableRate,Unsigned32,read-only,,current,,Maximum Attainable Data Rate. The maximum net data rate currently attainable by the xTU-C transmitter and xTU-R receiver (when referring to downstream direction) or by the xTU-R transmitter and xTU-C receiver (when referring to upstream direction). Value is coded in bits/s. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.251.1.2.3.1.11,VDSL2-LINE-MIB::xdsl2SCStatusRowStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Row Status. The SNMP agent will create a row in this table for storing the results of a DELT performed on the associated line, if the row does not already exist. When a row is created in this table, the SNMP agent should also create corresponding rows in the tables xdsl2SCStatusBandTable and xdsl2SCStatusSegmentTable. The SNMP manager is not permitted to create rows in this table or set the row status to 'notInService'. In the first case, if the SNMP manager tries to create a new row, the SNMP agent responds with the value 'noCreation' in the error status field of the response-PDU. In the latter case the SNMP agent responds with the value 'wrongValue' in the error status field of the response-PDU. When a row is deleted in this table, the SNMP agent should also delete corresponding rows in the tables xdsl2SCStatusBandTable and xdsl2SCStatusSegmentTable. The SNMP agent may have limited resources; therefore, if multiple rows coexist in this table, it may fail to add new rows to this table or allocate memory resources for a new DELT process. If that occurs, the SNMP agent responds with either the value 'tableFull' or the value 'noResources' (for the xdsl2LineCmndConfLdsfFailReason object in xdsl2LineTable). The management system (the operator) may delete rows from this table according to any scheme. For example, after retrieving the results.
.1.3.6.1.2.1.10.251.1.2.4,VDSL2-LINE-MIB::xdsl2SCStatusBandTable,,not-accessible,,current,,The table xdsl2SCStatusBandTable contains subcarrier status parameters for VDSL2/ADSL/ADSL2 and ADSL2+ that are grouped per- band. For ADSL/ADSL2/ADSL2+, there is a single upstream band and a single downstream band. For VDSL2, there are several downstream bands and several upstream bands. The parameters in this table are only available after a loop diagnostic procedure.
.1.3.6.1.2.1.10.251.1.2.4.1,VDSL2-LINE-MIB::xdsl2SCStatusBandEntry,,not-accessible,ifIndex:xdsl2SCStatusBand,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the transmission band.
.1.3.6.1.2.1.10.251.1.2.4.1.1,VDSL2-LINE-MIB::xdsl2SCStatusBand,INTEGER,not-accessible,,current,upstream(1):downstream(2):us0(3):ds1(4):us1(5):ds2(6):us2(7):ds3(8):us3(9):ds4(10):us4(11),The transmission band.
.1.3.6.1.2.1.10.251.1.2.4.1.2,VDSL2-LINE-MIB::xdsl2SCStatusBandLnAtten,Unsigned32,read-only,,current,,When referring to a band in the downstream direction, it is the measured difference in the total power transmitted by the xTU-C and the total power received by the xTU-R over all subcarriers during diagnostics mode. When referring to a band in the upstream direction, it is the measured difference in the total power transmitted by the xTU-R and the total power received by the xTU-C over all subcarriers during diagnostics mode. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is unavailable. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.251.1.2.4.1.3,VDSL2-LINE-MIB::xdsl2SCStatusBandSigAtten,Unsigned32,read-only,,current,,When referring to a band in the downstream direction, it is the measured difference in the total power transmitted by the xTU-C and the total power received by the xTU-R over all subcarriers during Showtime after the diagnostics mode. When referring to the upstream direction, it is the measured difference in the total power transmitted by the xTU-R and the total power received by the xTU-C over all subcarriers during Showtime after the diagnostics mode. It ranges from 0 to 1270 units of 0.1 dB (physical values are 0 to 127 dB). A special value of 0x7FFFFFFF (2147483647) indicates the line attenuation is out of range to be represented. A special value of 0x7FFFFFFE (2147483646) indicates the line attenuation measurement is unavailable. This object reflects the value of the parameter following the most recent DELT performed on the associated line. Once the DELT process is over, the parameter no longer changes until the row is deleted or a new DELT process is initiated.
.1.3.6.1.2.1.10.251.1.2.5,VDSL2-LINE-MIB::xdsl2SCStatusSegmentTable,,not-accessible,,current,,The table xdsl2SCStatusSegmentTable contains status parameters of VDSL2/ADSL/ADSL2 and ADSL2+ subcarriers. Several objects in the table refer to NSus and NSds. For G.993.2, the value of NSus and NSds are, respectively, the indices of the highest supported upstream and downstream subcarriers according to the selected implementation profile. For ADSL, NSus is equal to NSCus-1 and NSds is equal to NSCds-1. The parameters in this table MUST be updated after a loop diagnostic procedure and MAY be updated after a line initialization and MAY be updated at Showtime.
.1.3.6.1.2.1.10.251.1.2.5.1,VDSL2-LINE-MIB::xdsl2SCStatusSegmentEntry,,not-accessible,ifIndex:xdsl2SCStatusDirection:xdsl2SCStatusSegment,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the transmission direction. A third index identifies the specific segment of the subcarriers status addressed.
.1.3.6.1.2.1.10.251.1.2.5.1.1,VDSL2-LINE-MIB::xdsl2SCStatusSegment,Unsigned32,not-accessible,,current,,The segment of the subcarriers status information provided by this row. Several status parameters in this table are retrieved in segments. The first segment of the status information is retrieved with xdsl2SCStatusSegment=1, the second segment is retrieved with xdsl2SCStatusSegment=2, and so on. When any status parameter is retrieved in n segments where n<8), then for that parameter, GET operations for the remaining segment numbers (n+1 to 8) will respond with a zero-length OCTET STRING.
.1.3.6.1.2.1.10.251.1.2.5.1.2,VDSL2-LINE-MIB::xdsl2SCStatusSegmentLinReal,OCTET,read-only,,current,,An array of up to 512 complex H(f) linear representation values in linear scale for the respective transmission direction. It is designed to support up to 512 (downstream) subcarrier groups and can be retrieved in a single segment. The number of utilized values in the downstream direction depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. Each array entry represents the real component (referred to here as a(i)) of Hlin(f = i*Df) value for a particular subcarrier group index i (0 <= i <= NS). Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where scale is xdsl2SCStatusLinScale and a(i) and b(i) (provided by the xdsl2SCStatusSegmentLinImg object) are in the range (-2^15+1) to (+2^15-1). A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier group because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.251.1.2.5.1.3,VDSL2-LINE-MIB::xdsl2SCStatusSegmentLinImg,OCTET,read-only,,current,,An array of up to 512 complex H(f) linear representation values in linear scale for the respective transmission direction. It is designed to support up to 512 (downstream) subcarrier groups and can be retrieved in a single segment. The number of utilized values in the downstream direction depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. Each array entry represents the imaginary component (referred to here as b(i)) of Hlin(f = i*Df) value for a particular subcarrier group index i (0 <= i <= NS). Hlin(f) is represented as ((scale/2^15)*((a(i)+j*b(i))/2^15)), where scale is xdsl2SCStatusLinScale and a(i) (provided by the xdsl2SCStatusSegmentLinReal object) and b(i) are in the range (-2^15+1) to (+2^15-1). A special value a(i)=b(i)= -2^15 indicates that no measurement could be done for the subcarrier group because it is out of the passband or that the attenuation is out of range to be represented. This parameter is only available after a loop diagnostic procedure. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.251.1.2.5.1.4,VDSL2-LINE-MIB::xdsl2SCStatusSegmentLog,OCTET,read-only,,current,,An array of up to 512 real H(f) logarithmic representation values in dB for the respective transmission direction. It is designed to support up to 512 (downstream) subcarrier groups and can be retrieved in a single segment. The number of utilized values in the downstream direction depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. Each array entry represents the real Hlog(f = i*Df) value for a particular subcarrier group index i, (0 <= i <= NS). The real Hlog(f) value is represented as (6-m(i)/10), with m(i) in the range 0 to 1022. A special value m=1023 indicates that no measurement could be done for the subcarrier group because it is out of the passband or that the attenuation is out of range to be represented. This parameter is applicable in loop diagnostic procedure and initialization. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.251.1.2.5.1.5,VDSL2-LINE-MIB::xdsl2SCStatusSegmentQln,OCTET,read-only,,current,,An array of up to 512 real Quiet Line Noise values in dBm/Hz for the respective transmission direction. It is designed for up to 512 (downstream) subcarrier groups and can be retrieved in a single segment. The number of utilized values in the downstream direction depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. Each array entry represents the QLN(f = i*Df) value for a particular subcarrier index i, (0 <= i <= NS). The QLN(f) is represented as ( -23-n(i)/2), with n(i) in the range 0 to 254. A special value n(i)=255 indicates that no measurement could be done for the subcarrier group because it is out of the passband or that the noise PSD is out of range to be represented. This parameter is applicable in loop diagnostic procedure and initialization. Each value in this array is 8 bits wide.
.1.3.6.1.2.1.10.251.1.2.5.1.6,VDSL2-LINE-MIB::xdsl2SCStatusSegmentSnr,OCTET,read-only,,current,,The SNR Margin per subcarrier group, expressing the ratio between the received signal power and received noise power per subscriber group. It is an array of 512 octets, designed for supporting up to 512 (downstream) subcarrier groups and can be retrieved in a single segment. The number of utilized octets in the downstream direction depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. Octet i (0 <= i <= NS) is set to a value in the range 0 to 254 to indicate that the respective downstream or upstream subcarrier group i has an SNR of: (-32 + xdsl2SCStatusSegmentSnr(i)/2) in dB (i.e., -32 to 95 dB). The special value 255 means that no measurement could be done for the subcarrier group because it is out of the PSD mask passband or that the noise PSD is out of range to be represented. Each value in this array is 8 bits wide.
.1.3.6.1.2.1.10.251.1.2.5.1.7,VDSL2-LINE-MIB::xdsl2SCStatusSegmentBitsAlloc,OCTET,read-only,,current,,The bits allocation per subcarrier. An array of 256 octets (512 nibbles) designed for supporting up to 512 (downstream) subcarriers. When more than 512 subcarriers are supported, the status information is reported through multiple (up to 8) segments. The first segment is then used for the first 512 subcarriers. The second segment is used for the subcarriers 512 to 1023 and so on. The aggregate number of utilized nibbles in the downstream direction (in all segments) depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. The segment number is in xdsl2SCStatusSegment. Nibble i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each segment is set to a value in the range 0 to 15 to indicate that the respective downstream or upstream subcarrier j (j=(segement-1)*512+i) has the same amount of bits allocation.
.1.3.6.1.2.1.10.251.1.2.5.1.8,VDSL2-LINE-MIB::xdsl2SCStatusSegmentGainAlloc,OCTET,read-only,,current,,The gain allocation per subcarrier. An array of 512 16-bit values, designed for supporting up to 512 (downstream) subcarriers. When more then 512 subcarriers are supported, the status information is reported through multiple (up to 8) segments. The first segment is then used for the first 512 subcarriers. The second segment is used for the subcarriers 512 to 1023 and so on. The aggregate number of utilized octets in the downstream direction depends on NSds; in the upstream direction, it depends on NSus. This value is referred to here as NS. The segment number is in xdsl2SCStatusSegment. Value i (0 <= i < MIN((NS+1)-(segment-1)*512,512)) in each segment is set to a value in the range 0 to 4093 to indicate that the respective downstream or upstream subcarrier j (j=(segement-1)*512+i) has the same amount of gain value. The gain value is represented as a multiple of 1/512 on a linear scale. Each value in this array is 16 bits wide and is stored in big endian format.
.1.3.6.1.2.1.10.251.1.3,VDSL2-LINE-MIB::xdsl2Inventory,,,,,,
.1.3.6.1.2.1.10.251.1.3.1,VDSL2-LINE-MIB::xdsl2LineInventoryTable,,not-accessible,,current,,The table xdsl2LineInventoryTable contains an inventory of the DSL termination unit.
.1.3.6.1.2.1.10.251.1.3.1.1,VDSL2-LINE-MIB::xdsl2LineInventoryEntry,,not-accessible,ifIndex:xdsl2LInvUnit,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the termination unit.
.1.3.6.1.2.1.10.251.1.3.1.1.1,VDSL2-LINE-MIB::xdsl2LInvUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.3.1.1.2,VDSL2-LINE-MIB::xdsl2LInvG994VendorId,OCTET,read-only,,current,,The ADSL Transceiver Unit (ATU) G.994.1 Vendor ID as inserted in the G.994.1 CL/CLR message. It consists of 8 binary octets, including a country code followed by a (regionally allocated) provider code, as defined in Recommendation T.35.
.1.3.6.1.2.1.10.251.1.3.1.1.3,VDSL2-LINE-MIB::xdsl2LInvSystemVendorId,OCTET,read-only,,current,,The ATU System Vendor ID (identifies the xTU system integrator) as inserted in the Overhead Messages (both xTUs for G.992.3, G.992.4, G.992.5, and G.993.2) or in the Embedded Operations Channel (xTU-R in G.992.1 and G.992.2). It consists of 8 binary octets, with same format as used for Xdsl2InvG994VendorId.
.1.3.6.1.2.1.10.251.1.3.1.1.4,VDSL2-LINE-MIB::xdsl2LInvVersionNumber,OCTET,read-only,,current,,The xTU version number (vendor-specific information) as inserted in the Overhead Messages (both xTUs for G.992.3, G.992.4, G.992.5, and G.993.2) or in the Embedded Operations Channel (xTU-R in G.992.1 and G.992.2). It consists of up to 16 binary octets.
.1.3.6.1.2.1.10.251.1.3.1.1.5,VDSL2-LINE-MIB::xdsl2LInvSerialNumber,OCTET,read-only,,current,,The xTU serial number (vendor-specific information) as inserted in the Overhead Messages (both xTUs for G.992.3, G.992.4, G.992.5, and G.993.2) or in the Embedded Operations Channel (xTU-R in G.992.1 and G.992.2). It is vendor-specific information consisting of up to 32 ASCII characters.
.1.3.6.1.2.1.10.251.1.3.1.1.6,VDSL2-LINE-MIB::xdsl2LInvSelfTestResult,Unsigned32,read-only,,current,,The xTU self-test result, coded as a 32-bit value. The most significant octet of the result is '0' if the self-test passed, and '1' if the self-test failed. The interpretation of the other octets is vendor discretionary.
.1.3.6.1.2.1.10.251.1.3.1.1.7,VDSL2-LINE-MIB::xdsl2LInvTransmissionCapabilities,BITS,read-only,,current,ansit1413(0):etsi(1):g9921PotsNonOverlapped(2):g9921PotsOverlapped(3):g9921IsdnNonOverlapped(4):g9921isdnOverlapped(5):g9921tcmIsdnNonOverlapped(6):g9921tcmIsdnOverlapped(7):g9922potsNonOverlapped(8):g9922potsOverlapped(9):g9922tcmIsdnNonOverlapped(10):g9922tcmIsdnOverlapped(11):g9921tcmIsdnSymmetric(12):reserved1(13):reserved2(14):reserved3(15):reserved4(16):reserved5(17):g9923PotsNonOverlapped(18):g9923PotsOverlapped(19):g9923IsdnNonOverlapped(20):g9923isdnOverlapped(21):reserved6(22):reserved7(23):g9924potsNonOverlapped(24):g9924potsOverlapped(25):reserved8(26):reserved9(27):g9923AnnexIAllDigNonOverlapped(28):g9923AnnexIAllDigOverlapped(29):g9923AnnexJAllDigNonOverlapped(30):g9923AnnexJAllDigOverlapped(31):g9924AnnexIAllDigNonOverlapped(32):g9924AnnexIAllDigOverlapped(33):g9923AnnexLMode1NonOverlapped(34):g9923AnnexLMode2NonOverlapped(35):g9923AnnexLMode3Overlapped(36):g9923AnnexLMode4Overlapped(37):g9923AnnexMPotsNonOverlapped(38):g9923AnnexMPotsOverlapped(39):g9925PotsNonOverlapped(40):g9925PotsOverlapped(41):g9925IsdnNonOverlapped(42):g9925isdnOverlapped(43):reserved10(44):reserved11(45):g9925AnnexIAllDigNonOverlapped(46):g9925AnnexIAllDigOverlapped(47):g9925AnnexJAllDigNonOverlapped(48):g9925AnnexJAllDigOverlapped(49):g9925AnnexMPotsNonOverlapped(50):g9925AnnexMPotsOverlapped(51):reserved12(52):reserved13(53):reserved14(54):reserved15(55):g9932AnnexA(56):g9932AnnexB(57):g9932AnnexC(58):reserved16(59):reserved17(60):reserved18(61):reserved19(62):reserved20(63),The xTU transmission system capability list of the different coding types. It is coded in a bitmap representation with 1 or more bits set. A bit set to '1' means that the xTU supports the respective coding. The value may be derived from the handshaking procedures defined in G.994.1. A set of xDSL line transmission modes, with one bit per mode.
.1.3.6.1.2.1.10.251.1.4,VDSL2-LINE-MIB::xdsl2PM,,,,,,
.1.3.6.1.2.1.10.251.1.4.1,VDSL2-LINE-MIB::xdsl2PMLine,,,,,,
.1.3.6.1.2.1.10.251.1.4.1.1,VDSL2-LINE-MIB::xdsl2PMLineCurrTable,,not-accessible,,current,,The table xdsl2PMLineCurrTable contains current Performance Monitoring results for DSL lines.
.1.3.6.1.2.1.10.251.1.4.1.1.1,VDSL2-LINE-MIB::xdsl2PMLineCurrEntry,,not-accessible,ifIndex:xdsl2PMLCurrUnit,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the termination unit.
.1.3.6.1.2.1.10.251.1.4.1.1.1.1,VDSL2-LINE-MIB::xdsl2PMLCurrUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.4.1.1.1.2,VDSL2-LINE-MIB::xdsl2PMLCurr15MValidIntervals,Unsigned32,read-only,,current,,The number of 15-minute PM intervals for which data was collected. The value will typically be equal to the maximum number of 15-minute intervals the implementation is planned to store (i.e., beyond the scope of this MIB module) unless the measurement was (re-)started recently, in which case the value will be the number of complete 15-minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.251.1.4.1.1.1.3,VDSL2-LINE-MIB::xdsl2PMLCurr15MInvalidIntervals,Unsigned32,read-only,,current,,The number of 15-minute PM intervals for which no data is available. The value will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.251.1.4.1.1.1.4,VDSL2-LINE-MIB::xdsl2PMLCurr15MTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.251.1.4.1.1.1.5,VDSL2-LINE-MIB::xdsl2PMLCurr15MFecs,Counter32,read-only,,current,,Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.251.1.4.1.1.1.6,VDSL2-LINE-MIB::xdsl2PMLCurr15MEs,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >=1 OR LPR >= 1. xTU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >=1 OR RDI >=1 OR LPR-FE >=1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.1.1.7,VDSL2-LINE-MIB::xdsl2PMLCurr15MSes,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: (CRC-8 anomalies in one or more of the received bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: (FEBE anomalies in one or more of the received bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.1.1.8,VDSL2-LINE-MIB::xdsl2PMLCurr15MLoss,Counter32,read-only,,current,,Count of seconds during this interval that there was LOS (or LOS-FE for xTU-R).
.1.3.6.1.2.1.10.251.1.4.1.1.1.9,VDSL2-LINE-MIB::xdsl2PMLCurr15MUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely errored seconds, and ends at the onset of 10 contiguous seconds with no severely errored seconds.
.1.3.6.1.2.1.10.251.1.4.1.1.1.10,VDSL2-LINE-MIB::xdsl2PMLCurr1DayValidIntervals,Unsigned32,read-only,,current,,The number of 24-hour PM intervals for which data was collected. The value will typically be equal to the maximum number of 24-hour intervals the implementation is planned to store (i.e., beyond the scope of this MIB module) unless the measurement was (re-)started recently, in which case the value will be the number of complete 24-hour intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.251.1.4.1.1.1.11,VDSL2-LINE-MIB::xdsl2PMLCurr1DayInvalidIntervals,Unsigned32,read-only,,current,,The number of 24-hour PM intervals for which no data is available. The value will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.251.1.4.1.1.1.12,VDSL2-LINE-MIB::xdsl2PMLCurr1DayTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.251.1.4.1.1.1.13,VDSL2-LINE-MIB::xdsl2PMLCurr1DayFecs,Counter32,read-only,,current,,Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.251.1.4.1.1.1.14,VDSL2-LINE-MIB::xdsl2PMLCurr1DayEs,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.1.1.15,VDSL2-LINE-MIB::xdsl2PMLCurr1DaySes,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: (CRC-8 anomalies in one or more of the received bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: (FEBE anomalies in one or more of the received bearer channels) >= 18 OR LOS-FE >= 1. OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.1.1.16,VDSL2-LINE-MIB::xdsl2PMLCurr1DayLoss,Counter32,read-only,,current,,Count of seconds during this interval that there was LOS (or LOS-FE for xTU-R).
.1.3.6.1.2.1.10.251.1.4.1.1.1.17,VDSL2-LINE-MIB::xdsl2PMLCurr1DayUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely errored seconds, and ends at the onset of 10 contiguous seconds with no severely errored seconds.
.1.3.6.1.2.1.10.251.1.4.1.2,VDSL2-LINE-MIB::xdsl2PMLineInitCurrTable,,not-accessible,,current,,The table xdsl2PMLineInitCurrTable contains current initialization counters for DSL lines.
.1.3.6.1.2.1.10.251.1.4.1.2.1,VDSL2-LINE-MIB::xdsl2PMLineInitCurrEntry,,not-accessible,ifIndex,current,,The index of this table is an interface index where the interface has an ifType of vdsl2(251).
.1.3.6.1.2.1.10.251.1.4.1.2.1.1,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MValidIntervals,Unsigned32,read-only,,current,,The number of 15-minute PM intervals for which data was collected. The value will typically be equal to the maximum number of 15-minute intervals the implementation is planned to store (i.e., beyond the scope of this MIB module) unless the measurement was (re-)started recently, in which case the value will be the number of complete 15-minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.251.1.4.1.2.1.2,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MInvalidIntervals,Unsigned32,read-only,,current,,The number of 15-minute PM intervals for which no data is available. The value will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.251.1.4.1.2.1.3,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MTimeElapsed,Unsigned32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.4,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.5,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.6,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.7,VDSL2-LINE-MIB::xdsl2PMLInitCurr15MFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.8,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayValidIntervals,Unsigned32,read-only,,current,,The number of 24-hour PM intervals for which data was collected. The value will typically be equal to the maximum number of 24-hour intervals the implementation is planned to store (i.e., beyond the scope of this MIB module) unless the measurement was (re-)started recently, in which case the value will be the number of complete 24-hour intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.251.1.4.1.2.1.9,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayInvalidIntervals,Unsigned32,read-only,,current,,The number of 24-hour PM intervals for which no data is available. The value will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.251.1.4.1.2.1.10,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayTimeElapsed,Unsigned32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.11,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.12,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.13,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.2.1.14,VDSL2-LINE-MIB::xdsl2PMLInitCurr1DayFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.3,VDSL2-LINE-MIB::xdsl2PMLineHist15MinTable,,not-accessible,,current,,The table xdsl2PMLineHist15MinTable contains PM line history for 15-minute intervals of DSL line.
.1.3.6.1.2.1.10.251.1.4.1.3.1,VDSL2-LINE-MIB::xdsl2PMLineHist15MinEntry,,not-accessible,ifIndex:xdsl2PMLHist15MUnit:xdsl2PMLHist15MInterval,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the transmission unit. The third index is the interval number.
.1.3.6.1.2.1.10.251.1.4.1.3.1.1,VDSL2-LINE-MIB::xdsl2PMLHist15MUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.4.1.3.1.2,VDSL2-LINE-MIB::xdsl2PMLHist15MInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.251.1.4.1.3.1.3,VDSL2-LINE-MIB::xdsl2PMLHist15MMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.251.1.4.1.3.1.4,VDSL2-LINE-MIB::xdsl2PMLHist15MFecs,Counter32,read-only,,current,,Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.251.1.4.1.3.1.5,VDSL2-LINE-MIB::xdsl2PMLHist15MEs,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.3.1.6,VDSL2-LINE-MIB::xdsl2PMLHist15MSes,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: (CRC-8 anomalies in one or more of the received bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: (FEBE anomalies in one or more of the received bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.3.1.7,VDSL2-LINE-MIB::xdsl2PMLHist15MLoss,Counter32,read-only,,current,,Count of seconds during this interval that there was LOS (or LOS-FE for xTU-R).
.1.3.6.1.2.1.10.251.1.4.1.3.1.8,VDSL2-LINE-MIB::xdsl2PMLHist15MUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely errored seconds, and ends at the onset of 10 contiguous seconds with no severely errored seconds.
.1.3.6.1.2.1.10.251.1.4.1.3.1.9,VDSL2-LINE-MIB::xdsl2PMLHist15MValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.251.1.4.1.4,VDSL2-LINE-MIB::xdsl2PMLineHist1DayTable,,not-accessible,,current,,The table xdsl2PMLineHist1DayTable contains PM line history for 24-hour intervals of DSL line.
.1.3.6.1.2.1.10.251.1.4.1.4.1,VDSL2-LINE-MIB::xdsl2PMLineHist1DayEntry,,not-accessible,ifIndex:xdsl2PMLHist1DUnit:xdsl2PMLHist1DInterval,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index of this table is the transmission unit.The third index is the interval number.
.1.3.6.1.2.1.10.251.1.4.1.4.1.1,VDSL2-LINE-MIB::xdsl2PMLHist1DUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.4.1.4.1.2,VDSL2-LINE-MIB::xdsl2PMLHist1DInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.251.1.4.1.4.1.3,VDSL2-LINE-MIB::xdsl2PMLHist1DMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.251.1.4.1.4.1.4,VDSL2-LINE-MIB::xdsl2PMLHist1DFecs,Counter32,read-only,,current,,Count of seconds during this interval that there was at least one FEC correction event for one or more bearer channels in this line. This parameter is inhibited during UAS or SES.
.1.3.6.1.2.1.10.251.1.4.1.4.1.5,VDSL2-LINE-MIB::xdsl2PMLHist1DEs,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.4.1.6,VDSL2-LINE-MIB::xdsl2PMLHist1DSes,Counter32,read-only,,current,,Count of seconds during this interval that there was: xTU-C: (CRC-8 anomalies in one or more of the received bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1. xTU-R: (FEBE anomalies in one or more of the received bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1. This parameter is inhibited during UAS.
.1.3.6.1.2.1.10.251.1.4.1.4.1.7,VDSL2-LINE-MIB::xdsl2PMLHist1DLoss,Counter32,read-only,,current,,Count of seconds during this interval that there was LOS (or LOS-FE for xTU-R).
.1.3.6.1.2.1.10.251.1.4.1.4.1.8,VDSL2-LINE-MIB::xdsl2PMLHist1DUas,Counter32,read-only,,current,,Count of seconds in Unavailability State during this interval. Unavailability begins at the onset of 10 contiguous severely errored seconds, and ends at the onset of 10 contiguous seconds with no severely errored seconds.
.1.3.6.1.2.1.10.251.1.4.1.4.1.9,VDSL2-LINE-MIB::xdsl2PMLHist1DValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.251.1.4.1.5,VDSL2-LINE-MIB::xdsl2PMLineInitHist15MinTable,,not-accessible,,current,,The table xdsl2PMLineInitHist15MinTable contains PM line initialization history for 15-minute intervals of DSL line.
.1.3.6.1.2.1.10.251.1.4.1.5.1,VDSL2-LINE-MIB::xdsl2PMLineInitHist15MinEntry,,not-accessible,ifIndex:xdsl2PMLInitHist15MInterval,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index is the interval number.
.1.3.6.1.2.1.10.251.1.4.1.5.1.1,VDSL2-LINE-MIB::xdsl2PMLInitHist15MInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.251.1.4.1.5.1.2,VDSL2-LINE-MIB::xdsl2PMLInitHist15MMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.251.1.4.1.5.1.3,VDSL2-LINE-MIB::xdsl2PMLInitHist15MFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.5.1.4,VDSL2-LINE-MIB::xdsl2PMLInitHist15MFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.5.1.5,VDSL2-LINE-MIB::xdsl2PMLInitHist15MShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.5.1.6,VDSL2-LINE-MIB::xdsl2PMLInitHist15MFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.5.1.7,VDSL2-LINE-MIB::xdsl2PMLInitHist15MValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.251.1.4.1.6,VDSL2-LINE-MIB::xdsl2PMLineInitHist1DayTable,,not-accessible,,current,,The table xdsl2PMLineInitHist1DayTable contains PM line initialization history for 24-hour intervals for DSL lines.
.1.3.6.1.2.1.10.251.1.4.1.6.1,VDSL2-LINE-MIB::xdsl2PMLineInitHist1DayEntry,,not-accessible,ifIndex:xdsl2PMLInitHist1DInterval,current,,One index of this table is an interface index where the interface has an ifType of vdsl2(251). A second index is the interval number.
.1.3.6.1.2.1.10.251.1.4.1.6.1.1,VDSL2-LINE-MIB::xdsl2PMLInitHist1DInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.251.1.4.1.6.1.2,VDSL2-LINE-MIB::xdsl2PMLInitHist1DMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.251.1.4.1.6.1.3,VDSL2-LINE-MIB::xdsl2PMLInitHist1DFullInits,Unsigned32,read-only,,current,,Count of full initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.6.1.4,VDSL2-LINE-MIB::xdsl2PMLInitHist1DFailedFullInits,Unsigned32,read-only,,current,,Count of failed full initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.6.1.5,VDSL2-LINE-MIB::xdsl2PMLInitHist1DShortInits,Unsigned32,read-only,,current,,Count of short initializations attempted on the line (successful and failed) during this interval.
.1.3.6.1.2.1.10.251.1.4.1.6.1.6,VDSL2-LINE-MIB::xdsl2PMLInitHist1DFailedShortInits,Unsigned32,read-only,,current,,Count of failed short initializations on the line during this interval.
.1.3.6.1.2.1.10.251.1.4.1.6.1.7,VDSL2-LINE-MIB::xdsl2PMLInitHist1DValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.251.1.4.2,VDSL2-LINE-MIB::xdsl2PMChannel,,,,,,
.1.3.6.1.2.1.10.251.1.4.2.1,VDSL2-LINE-MIB::xdsl2PMChCurrTable,,not-accessible,,current,,The table xdsl2PMChCurrTable contains current Performance Monitoring results for DSL channels.
.1.3.6.1.2.1.10.251.1.4.2.1.1,VDSL2-LINE-MIB::xdsl2PMChCurrEntry,,not-accessible,ifIndex:xdsl2PMChCurrUnit,current,,One index of this table is an interface index where the interface has an ifType of a DSL channel. A second index of this table is the termination unit.
.1.3.6.1.2.1.10.251.1.4.2.1.1.1,VDSL2-LINE-MIB::xdsl2PMChCurrUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.4.2.1.1.2,VDSL2-LINE-MIB::xdsl2PMChCurr15MValidIntervals,Unsigned32,read-only,,current,,The number of 15-minute PM intervals for which data was collected. The value will typically be equal to the maximum number of 15-minute intervals the implementation is planned to store (i.e., beyond the scope of this MIB module) unless the measurement was (re-)started recently, in which case the value will be the number of complete 15-minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.251.1.4.2.1.1.3,VDSL2-LINE-MIB::xdsl2PMChCurr15MInvalidIntervals,Unsigned32,read-only,,current,,The number of 15-minute PM intervals for which no data is available. The value will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.251.1.4.2.1.1.4,VDSL2-LINE-MIB::xdsl2PMChCurr15MTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.251.1.4.2.1.1.5,VDSL2-LINE-MIB::xdsl2PMChCurr15MCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for xTU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.1.1.6,VDSL2-LINE-MIB::xdsl2PMChCurr15MCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for xTU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.1.1.7,VDSL2-LINE-MIB::xdsl2PMChCurr1DayValidIntervals,Unsigned32,read-only,,current,,The number of 24-hour PM intervals for which data was collected. The value will typically be equal to the maximum number of 24-hour intervals the implementation is planned to store (i.e., beyond the scope of this MIB module) unless the measurement was (re-)started recently, in which case the value will be the number of complete 24-hour intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.10.251.1.4.2.1.1.8,VDSL2-LINE-MIB::xdsl2PMChCurr1DayInvalidIntervals,Unsigned32,read-only,,current,,The number of 24-hour PM intervals for which no data is available. The value will typically be zero except in cases where the data for some intervals are not available (e.g., in proxy situations).
.1.3.6.1.2.1.10.251.1.4.2.1.1.9,VDSL2-LINE-MIB::xdsl2PMChCurr1DayTimeElapsed,Integer32,read-only,,current,,Total elapsed seconds in this interval.
.1.3.6.1.2.1.10.251.1.4.2.1.1.10,VDSL2-LINE-MIB::xdsl2PMChCurr1DayCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for xTU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.1.1.11,VDSL2-LINE-MIB::xdsl2PMChCurr1DayCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for xTU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.2,VDSL2-LINE-MIB::xdsl2PMChHist15MinTable,,not-accessible,,current,,The table xdsl2PMChHist15MinTable contains Performance Monitoring (PM) history for 15-minute intervals for DSL channels PM.
.1.3.6.1.2.1.10.251.1.4.2.2.1,VDSL2-LINE-MIB::xdsl2PMChHist15MinEntry,,not-accessible,ifIndex:xdsl2PMChHist15MUnit:xdsl2PMChHist15MInterval,current,,One index of this table is an interface index where the interface has an ifType of a DSL channel. A second index of this table is the transmission unit. The third index is the interval number.
.1.3.6.1.2.1.10.251.1.4.2.2.1.1,VDSL2-LINE-MIB::xdsl2PMChHist15MUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.4.2.2.1.2,VDSL2-LINE-MIB::xdsl2PMChHist15MInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.251.1.4.2.2.1.3,VDSL2-LINE-MIB::xdsl2PMChHist15MMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.251.1.4.2.2.1.4,VDSL2-LINE-MIB::xdsl2PMChHist15MCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for xTU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.2.1.5,VDSL2-LINE-MIB::xdsl2PMChHist15MCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for xTU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.2.1.6,VDSL2-LINE-MIB::xdsl2PMChHist15MValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.251.1.4.2.3,VDSL2-LINE-MIB::xdsl2PMChHist1DTable,,not-accessible,,current,,The table xdsl2PMChHist1DTable contains Performance Monitoring (PM) history for 1-day intervals for DSL channels PM.
.1.3.6.1.2.1.10.251.1.4.2.3.1,VDSL2-LINE-MIB::xdsl2PMChHist1DEntry,,not-accessible,ifIndex:xdsl2PMChHist1DUnit:xdsl2PMChHist1DInterval,current,,One index of this table is an interface index where the interface has an ifType of a DSL channel. A second index of this table is the transmission unit. The third index is the interval number.
.1.3.6.1.2.1.10.251.1.4.2.3.1.1,VDSL2-LINE-MIB::xdsl2PMChHist1DUnit,INTEGER,not-accessible,,current,xtuc(1):xtur(2),The termination unit.
.1.3.6.1.2.1.10.251.1.4.2.3.1.2,VDSL2-LINE-MIB::xdsl2PMChHist1DInterval,Unsigned32,not-accessible,,current,,The interval number.
.1.3.6.1.2.1.10.251.1.4.2.3.1.3,VDSL2-LINE-MIB::xdsl2PMChHist1DMonitoredTime,Unsigned32,read-only,,current,,Total seconds monitored in this interval.
.1.3.6.1.2.1.10.251.1.4.2.3.1.4,VDSL2-LINE-MIB::xdsl2PMChHist1DCodingViolations,Unsigned32,read-only,,current,,Count of CRC-8 (FEBE for xTU-R) anomalies occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the CRC is applied over multiple channels, then each related CRC-8 (or FEBE) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.3.1.5,VDSL2-LINE-MIB::xdsl2PMChHist1DCorrectedBlocks,Unsigned32,read-only,,current,,Count of FEC (FFEC for xTU-R) anomalies (corrected code words) occurring in the channel during the interval. This parameter is inhibited during UAS or SES. If the FEC is applied over multiple channels, then each related FEC (or FFEC) anomaly SHOULD increment each of the counters related to the individual channels.
.1.3.6.1.2.1.10.251.1.4.2.3.1.6,VDSL2-LINE-MIB::xdsl2PMChHist1DValidInterval,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.10.251.1.5,VDSL2-LINE-MIB::xdsl2Profile,,,,,,
.1.3.6.1.2.1.10.251.1.5.1,VDSL2-LINE-MIB::xdsl2ProfileLine,,,,,,
.1.3.6.1.2.1.10.251.1.5.1.1,VDSL2-LINE-MIB::xdsl2LineConfTemplateTable,,not-accessible,,current,,The table xdsl2LineConfTemplateTable contains VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration templates. Note that this table is also used to configure the number of bearer channels. When the number of bearer channels is increased, the SNMP agent SHOULD create rows in all tables indexed by a channel index. When the number of bearer channels is decreased, the SNMP agent SHOULD delete rows in all tables indexed by a channel index. For example, if the value of xdsl2LConfTempChan4ConfProfile is set to a non-null value, then rows SHOULD be created in xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other tables indexed by a channel index. For example, if the value of xdsl2LConfTempChan2ConfProfile is set to a null value, then rows SHOULD be deleted in xdsl2ChannelStatusTable, xdsl2PMChCurrTable, and all other tables indexed by a channel index. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.1.1.1,VDSL2-LINE-MIB::xdsl2LineConfTemplateEntry,,not-accessible,xdsl2LConfTempTemplateName,current,,A default template with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.251.1.5.1.1.1.1,VDSL2-LINE-MIB::xdsl2LConfTempTemplateName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.251.1.5.1.1.1.2,VDSL2-LINE-MIB::xdsl2LConfTempLineProfile,OCTET,read-create,,current,,The value of this object identifies the row in the VDSL2/ADSL/ADSL2 and ADSL2+ line configuration Profile Table (xdsl2LineConfProfTable) that applies for this DSL line.
.1.3.6.1.2.1.10.251.1.5.1.1.1.3,VDSL2-LINE-MIB::xdsl2LConfTempChan1ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the VDSL2/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table (xdsl2ChConfProfileTable) that applies to DSL bearer channel #1. The channel profile name specified here MUST match the name of an existing row in the xdsl2ChConfProfileTable table.
.1.3.6.1.2.1.10.251.1.5.1.1.1.4,VDSL2-LINE-MIB::xdsl2LConfTempChan1RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #1 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan1RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.5,VDSL2-LINE-MIB::xdsl2LConfTempChan1RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #1 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan1RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.6,VDSL2-LINE-MIB::xdsl2LConfTempChan2ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the VDSL2/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table (xdsl2ChConfProfileTable) that applies to DSL bearer channel #2. If the channel is unused, then the object is set to a zero-length string. This object may be set to a zero-length string only if xdsl2LConfTempChan3ConfProfile contains a zero-length string.
.1.3.6.1.2.1.10.251.1.5.1.1.1.7,VDSL2-LINE-MIB::xdsl2LConfTempChan2RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #2 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan2RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.8,VDSL2-LINE-MIB::xdsl2LConfTempChan2RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #2 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan2RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.9,VDSL2-LINE-MIB::xdsl2LConfTempChan3ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the VDSL2/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table (xdsl2ChConfProfileTable) that applies to DSL bearer channel #3. If the channel is unused, then the object is set to a zero-length string. This object may be set to a zero-length string only if xdsl2LConfTempChan4ConfProfile contains a zero-length string. This object may be set to a non-zero-length string only if xdsl2LConfTempChan2ConfProfile contains a non-zero-length string.
.1.3.6.1.2.1.10.251.1.5.1.1.1.10,VDSL2-LINE-MIB::xdsl2LConfTempChan3RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #3 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan3RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels on Downstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.11,VDSL2-LINE-MIB::xdsl2LConfTempChan3RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #3 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan3RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels on Upstream direction. The sum of rate adaptation ratios over all bearers on the same direction shall be equal to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.12,VDSL2-LINE-MIB::xdsl2LConfTempChan4ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the VDSL2/ ADSL/ADSL2 and ADSL2+ channel configuration Profile Table (xdsl2ChConfProfileTable) that applies to DSL bearer channel #4. If the channel is unused, then the object is set to a zero-length string. This object may be set to a non-zero-length string only if xdsl2LConfTempChan3ConfProfile contains a non-zero-length string.
.1.3.6.1.2.1.10.251.1.5.1.1.1.13,VDSL2-LINE-MIB::xdsl2LConfTempChan4RaRatioDs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #4 when performing rate adaptation on Downstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan4RaRatioDs is the ratio of excess data rate to be assigned to all other bearer channels. The sum of rate adaptation ratios over all bearers on the same direction shall sum to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.14,VDSL2-LINE-MIB::xdsl2LConfTempChan4RaRatioUs,Unsigned32,read-create,,current,,Rate Adaptation Ratio. The ratio (in percent) that should be taken into account for the bearer channel #4 when performing rate adaptation on Upstream. The ratio refers to the available data rate in excess of the Minimum Data Rate, summed over all bearer channels. Also, the 100 - xdsl2LConfTempChan4RaRatioUs is the ratio of excess data rate to be assigned to all other bearer channels. The sum of rate adaptation ratios over all bearers on the same direction shall sum to 100%.
.1.3.6.1.2.1.10.251.1.5.1.1.1.15,VDSL2-LINE-MIB::xdsl2LConfTempRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A template is activated by setting this object to 'active'. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it MUST be first unreferenced from all associated lines. A row in this table is said to be unreferenced when there is no instance of xdsl2LineConfTemplate or xdsl2LineConfFallbackTemplate that refers to the row.
.1.3.6.1.2.1.10.251.1.5.1.2,VDSL2-LINE-MIB::xdsl2LineConfProfTable,,not-accessible,,current,,The table xdsl2LineConfProfTable contains VDSL2/ADSL/ ADSL2 and ADSL2+ line configuration profiles. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.1.2.1,VDSL2-LINE-MIB::xdsl2LineConfProfEntry,,not-accessible,xdsl2LConfProfProfileName,current,,A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.251.1.5.1.2.1.1,VDSL2-LINE-MIB::xdsl2LConfProfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.251.1.5.1.2.1.2,VDSL2-LINE-MIB::xdsl2LConfProfScMaskDs,OCTET,read-create,,current,,Subcarrier mask. A bitmap of 4096 bits that allows masking up to 4096 downstream subcarriers. If bit i (0 <= i < NSCds) is set to '1', the respective downstream subcarrier is masked, and if set to '0', the respective subcarrier is unmasked. Note that there should always be unmasked subcarriers (i.e., this object cannot be all 1's). Also note that if NSCds < 4096, all bits i (NSCds < i <= 4096) should be set to '1'.
.1.3.6.1.2.1.10.251.1.5.1.2.1.3,VDSL2-LINE-MIB::xdsl2LConfProfScMaskUs,OCTET,read-create,,current,,Subcarrier mask. A bitmap of 4096 bits that allows masking up to 4096 upstream subcarriers. If bit i (0 <= i < NSCus) is set to '1', the respective upstream subcarrier is masked, and if set to '0', the respective subcarrier is unmasked. Note that there should always be unmasked subcarriers (i.e., this object cannot be all 1's). Also note that if NSCus < 4096, all bits i (NSCus < i <= 4096) should be set to '1'.
.1.3.6.1.2.1.10.251.1.5.1.2.1.4,VDSL2-LINE-MIB::xdsl2LConfProfVdsl2CarMask,OCTET,read-create,,current,,VDSL2-specific subcarrier mask. This configuration parameter defines the restrictions, additional to the band plan, to determine the set of subcarriers allowed for transmission in both the upstream and downstream directions. The parameter shall describe the not masked subcarriers as one or more frequency bands. Each band is represented by start and stop subcarrier indices with a subcarrier spacing of 4.3125 kHz. The valid range of subcarrier indices runs from 0 to at least the index of the highest allowed subcarrier in both transmission directions among all profiles enabled by the parameter xdsl2LConfProfProfiles. Up to 32 bands may be specified. Other subcarriers shall be masked.
.1.3.6.1.2.1.10.251.1.5.1.2.1.5,VDSL2-LINE-MIB::xdsl2LConfProfRfiBands,OCTET,read-create,,current,,For ITU-T Recommendation G.992.5, this configuration parameter defines the subset of downstream PSD mask breakpoints, as specified in xdsl2LConfProfPsdMaskDs (PSDMASKds), that shall be used to notch an RFI band. This subset consists of pairs of consecutive subcarrier indices belonging to breakpoints: [ti; ti + 1], corresponding to the low level of the notch. The specific interpolation around these points is defined in the relevant Recommendations (e.g., ITU-T Recommendation G.992.5). The CO-MIB shall define the RFI notches using breakpoints in xdsl2LConfProfPsdMaskDs (PSDMASKds) as specified in the relevant Recommendations (e.g., ITU-T Recommendation G.992.5). For ITU-T Recommendation G.993.2, this configuration parameter defines the bands where the PSD shall be reduced as specified in #7.2.1.2/G.993.2. Each band shall be represented by a start and stop subcarrier indices with a subcarrier spacing of 4.3125 kHz. Up to 16 bands may be specified. This parameter defines the RFI bands for both the upstream and downstream directions.
.1.3.6.1.2.1.10.251.1.5.1.2.1.6,VDSL2-LINE-MIB::xdsl2LConfProfRaModeDs,INTEGER,read-create,,current,manual(1):raInit(2):dynamicRa(3),The mode of operation of a rate-adaptive xTU-C in the transmit direction.
.1.3.6.1.2.1.10.251.1.5.1.2.1.7,VDSL2-LINE-MIB::xdsl2LConfProfRaModeUs,INTEGER,read-create,,current,manual(1):raInit(2):dynamicRa(3),The mode of operation of a rate-adaptive xTU-R in the transmit direction.
.1.3.6.1.2.1.10.251.1.5.1.2.1.8,VDSL2-LINE-MIB::xdsl2LConfProfRaUsNrmDs,Unsigned32,read-create,,current,,The Downstream Up-Shift Noise Margin value, to be used when xdsl2LConfProfRaModeDs is set to 'dynamicRa'. If the downstream noise margin is above this value, and stays above it, for more than the time specified by the xdsl2LConfProfRaUsTimeDs, the xTU-R shall attempt to increase the downstream net data rate. The Downstream Up-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.251.1.5.1.2.1.9,VDSL2-LINE-MIB::xdsl2LConfProfRaUsNrmUs,Unsigned32,read-create,,current,,The Upstream Up-Shift Noise Margin value, to be used when xdsl2LConfProfRaModeUs is set to 'dynamicRa'. If the upstream noise margin is above this value, and stays above it, for more than the time specified by the xdsl2LConfProfRaUsTimeUs, the xTU-C shall attempt to increase the upstream net data rate. The Upstream Up-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.251.1.5.1.2.1.10,VDSL2-LINE-MIB::xdsl2LConfProfRaUsTimeDs,Unsigned32,read-create,,current,,The Downstream Up-Shift Time Interval, to be used when xdsl2LConfProfRaModeDs is set to 'dynamicRa'. The interval of time that the downstream noise margin should stay above the Downstream Up-Shift Noise Margin before the xTU-R shall attempt to increase the downstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.251.1.5.1.2.1.11,VDSL2-LINE-MIB::xdsl2LConfProfRaUsTimeUs,Unsigned32,read-create,,current,,The Upstream Up-Shift Time Interval, to be used when xdsl2LConfProfRaModeUs is set to 'dynamicRa'. The interval of time the upstream noise margin should stay above the Upstream Up-Shift Noise Margin before the xTU-C shall attempt to increase the upstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.251.1.5.1.2.1.12,VDSL2-LINE-MIB::xdsl2LConfProfRaDsNrmDs,Unsigned32,read-create,,current,,The Downstream Down-Shift Noise Margin value, to be used when xdsl2LConfProfRaModeDs is set to 'dynamicRa'. If the downstream noise margin is below this value and stays below that value, for more than the time specified by the xdsl2LConfProfRaDsTimeDs, the xTU-R shall attempt to decrease the downstream net data rate. The Downstream Down-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.251.1.5.1.2.1.13,VDSL2-LINE-MIB::xdsl2LConfProfRaDsNrmUs,Unsigned32,read-create,,current,,The Upstream Downshift Noise Margin value, to be used when xdsl2LConfProfRaModeUs is set to 'dynamicRa'. If the upstream noise margin is below this value and stays below that value, for more than the time specified by the xdsl2LConfProfRaDsTimeUs, the xTU-C shall attempt to decrease the upstream net data rate. The Upstream Down-Shift Noise Margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.251.1.5.1.2.1.14,VDSL2-LINE-MIB::xdsl2LConfProfRaDsTimeDs,Unsigned32,read-create,,current,,The Downstream Downshift Time Interval, to be used when xdsl2LConfProfRaModeDs is set to 'dynamicRa'. The interval of time the downstream noise margin should stay below the Downstream Down-Shift Noise Margin before the xTU-R shall attempt to decrease the downstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.251.1.5.1.2.1.15,VDSL2-LINE-MIB::xdsl2LConfProfRaDsTimeUs,Unsigned32,read-create,,current,,The Upstream Down-Shift Time Interval, to be used when xdsl2LConfProfRaModeUs is set to 'dynamicRa'. The interval of time the upstream noise margin should stay below the Upstream Down-Shift Noise Margin before the xTU-C shall attempt to decrease the upstream net data rate. The time interval ranges from 0 to 16383 seconds.
.1.3.6.1.2.1.10.251.1.5.1.2.1.16,VDSL2-LINE-MIB::xdsl2LConfProfTargetSnrmDs,Unsigned32,read-create,,current,,The minimum Noise Margin the xTU-R receiver shall achieve, relative to the BER requirement for each of the downstream bearer channels, to successfully complete initialization. The target noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.251.1.5.1.2.1.17,VDSL2-LINE-MIB::xdsl2LConfProfTargetSnrmUs,Unsigned32,read-create,,current,,The minimum Noise Margin the xTU-C receiver shall achieve, relative to the BER requirement for each of the upstream bearer channels, to successfully complete initialization. The target noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB).
.1.3.6.1.2.1.10.251.1.5.1.2.1.18,VDSL2-LINE-MIB::xdsl2LConfProfMaxSnrmDs,Unsigned32,read-create,,current,,The maximum Noise Margin the xTU-R receiver shall try to sustain. If the Noise Margin is above this level, the xTU-R shall request that the xTU-C reduce the xTU-C transmit power to get a noise margin below this limit (if this functionality is supported). The maximum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0x7FFFFFFF (2147483647) means that there is no maximum.
.1.3.6.1.2.1.10.251.1.5.1.2.1.19,VDSL2-LINE-MIB::xdsl2LConfProfMaxSnrmUs,Unsigned32,read-create,,current,,The maximum Noise Margin the xTU-C receiver shall try to sustain. If the Noise Margin is above this level, the xTU-C shall request that the xTU-R reduce the xTU-R transmit power to get a noise margin below this limit (if this functionality is supported). The maximum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0x7FFFFFFF (2147483647) means that there is no maximum.
.1.3.6.1.2.1.10.251.1.5.1.2.1.20,VDSL2-LINE-MIB::xdsl2LConfProfMinSnrmDs,Unsigned32,read-create,,current,,The minimum Noise Margin the xTU-R receiver shall tolerate. If the noise margin falls below this level, the xTU-R shall request that the xTU-C increase the xTU-C transmit power. If an increase to xTU-C transmit power is not possible, a loss- of-margin (LOM) defect occurs, the xTU-R shall fail and attempt to reinitialize and the NMS shall be notified. The minimum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0 means that there is no minimum.
.1.3.6.1.2.1.10.251.1.5.1.2.1.21,VDSL2-LINE-MIB::xdsl2LConfProfMinSnrmUs,Unsigned32,read-create,,current,,The minimum Noise Margin the xTU-C receiver shall tolerate. If the noise margin falls below this level, the xTU-C shall request that the xTU-R increase the xTU-R transmit power. If an increase of xTU-R transmit power is not possible, a loss- of-margin (LOM) defect occurs, the xTU-C shall fail and attempt to re-initialize and the NMS shall be notified. The minimum noise margin ranges from 0 to 310 units of 0.1 dB (physical values are 0 to 31 dB). A value of 0 means that there is no minimum.
.1.3.6.1.2.1.10.251.1.5.1.2.1.22,VDSL2-LINE-MIB::xdsl2LConfProfMsgMinUs,Unsigned32,read-create,,current,,Minimum Overhead Rate Upstream. Defines the minimum rate of the message-based overhead that shall be maintained by the xTU in upstream direction. Expressed in bits per second and ranges from 4000 to 248000 bits/s.
.1.3.6.1.2.1.10.251.1.5.1.2.1.23,VDSL2-LINE-MIB::xdsl2LConfProfMsgMinDs,Unsigned32,read-create,,current,,Minimum Overhead Rate Downstream. Defines the minimum rate of the message-based overhead that shall be maintained by the xTU in the downstream direction. Expressed in bits per second and ranges from 4000 to 248000 bits/s.
.1.3.6.1.2.1.10.251.1.5.1.2.1.24,VDSL2-LINE-MIB::xdsl2LConfProfCeFlag,BITS,read-create,,current,enableCyclicExtension(0),This parameter is a bit that enables the use of the optional cyclic extension values.
.1.3.6.1.2.1.10.251.1.5.1.2.1.25,VDSL2-LINE-MIB::xdsl2LConfProfSnrModeDs,INTEGER,read-create,,current,virtualNoiseDisabled(1):virtualNoiseEnabled(2),This parameter enables the transmitter-referred virtual noise in the downstream direction.
.1.3.6.1.2.1.10.251.1.5.1.2.1.26,VDSL2-LINE-MIB::xdsl2LConfProfSnrModeUs,INTEGER,read-create,,current,virtualNoiseDisabled(1):virtualNoiseEnabled(2),This parameter enables the transmitter-referred virtual noise in the upstream direction.
.1.3.6.1.2.1.10.251.1.5.1.2.1.27,VDSL2-LINE-MIB::xdsl2LConfProfTxRefVnDs,OCTET,read-create,,current,,This configuration parameter defines the downstream transmitter-referred virtual noise. The TXREFVNds shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index t, with a subcarrier spacing of 4.3125 kHz, and a noise PSD level (expressed in dBm/Hz) at that subcarrier. The set of breakpoints can then be represented as: [(t1,PSD1), (t2, PSD2), ... , (tN, PSDN)].
.1.3.6.1.2.1.10.251.1.5.1.2.1.28,VDSL2-LINE-MIB::xdsl2LConfProfTxRefVnUs,OCTET,read-create,,current,,This configuration parameter defines the upstream transmitter-referred virtual noise. The TXREFVNus shall be specified through a set of breakpoints. Each breakpoint shall consist of a subcarrier index t, with a subcarrier spacing of 4.3125 kHz, and a noise PSD level (expressed in dBm/Hz) at that subcarrier. The set of breakpoints can then be represented as: [(t1, PSD1), (t2, PSD2), ... , (tN, PSDN)].
.1.3.6.1.2.1.10.251.1.5.1.2.1.29,VDSL2-LINE-MIB::xdsl2LConfProfXtuTransSysEna,BITS,read-create,,current,ansit1413(0):etsi(1):g9921PotsNonOverlapped(2):g9921PotsOverlapped(3):g9921IsdnNonOverlapped(4):g9921isdnOverlapped(5):g9921tcmIsdnNonOverlapped(6):g9921tcmIsdnOverlapped(7):g9922potsNonOverlapped(8):g9922potsOverlapped(9):g9922tcmIsdnNonOverlapped(10):g9922tcmIsdnOverlapped(11):g9921tcmIsdnSymmetric(12):reserved1(13):reserved2(14):reserved3(15):reserved4(16):reserved5(17):g9923PotsNonOverlapped(18):g9923PotsOverlapped(19):g9923IsdnNonOverlapped(20):g9923isdnOverlapped(21):reserved6(22):reserved7(23):g9924potsNonOverlapped(24):g9924potsOverlapped(25):reserved8(26):reserved9(27):g9923AnnexIAllDigNonOverlapped(28):g9923AnnexIAllDigOverlapped(29):g9923AnnexJAllDigNonOverlapped(30):g9923AnnexJAllDigOverlapped(31):g9924AnnexIAllDigNonOverlapped(32):g9924AnnexIAllDigOverlapped(33):g9923AnnexLMode1NonOverlapped(34):g9923AnnexLMode2NonOverlapped(35):g9923AnnexLMode3Overlapped(36):g9923AnnexLMode4Overlapped(37):g9923AnnexMPotsNonOverlapped(38):g9923AnnexMPotsOverlapped(39):g9925PotsNonOverlapped(40):g9925PotsOverlapped(41):g9925IsdnNonOverlapped(42):g9925isdnOverlapped(43):reserved10(44):reserved11(45):g9925AnnexIAllDigNonOverlapped(46):g9925AnnexIAllDigOverlapped(47):g9925AnnexJAllDigNonOverlapped(48):g9925AnnexJAllDigOverlapped(49):g9925AnnexMPotsNonOverlapped(50):g9925AnnexMPotsOverlapped(51):reserved12(52):reserved13(53):reserved14(54):reserved15(55):g9932AnnexA(56):g9932AnnexB(57):g9932AnnexC(58):reserved16(59):reserved17(60):reserved18(61):reserved19(62):reserved20(63),xTU Transmission System Enabling (XTSE). A list of the different coding types enabled in this profile. It is coded in a bitmap representation with 1 or more bits set. A bit set to '1' means that the xTUs may apply the respective coding for the DSL line. A bit set to '0' means that the xTUs cannot apply the respective coding for the ADSL line. All 'reserved' bits should be set to '0'.
.1.3.6.1.2.1.10.251.1.5.1.2.1.30,VDSL2-LINE-MIB::xdsl2LConfProfPmMode,BITS,read-create,,current,allowTransitionsToIdle(0):allowTransitionsToLowPower(1),Power management state Enabling (PMMode). Defines the power states the xTU-C or xTU-R may autonomously transition to on this line. This is a set of bits, where any bit with a '1' value means that the xTU is allowed to transit into the respective state and any bit with a '0' value means that the xTU is not allowed to transit into the respective state.
.1.3.6.1.2.1.10.251.1.5.1.2.1.31,VDSL2-LINE-MIB::xdsl2LConfProfL0Time,Unsigned32,read-create,,current,,The minimum time (in seconds) between an Exit from the L2 state and the next Entry into the L2 state. It ranges from 0 to 255 seconds.
.1.3.6.1.2.1.10.251.1.5.1.2.1.32,VDSL2-LINE-MIB::xdsl2LConfProfL2Time,Unsigned32,read-create,,current,,The minimum time (in seconds) between an Entry into the L2 state and the first Power Trim in the L2 state and between two consecutive Power Trims in the L2 state. It ranges from 0 to 255 seconds.
.1.3.6.1.2.1.10.251.1.5.1.2.1.33,VDSL2-LINE-MIB::xdsl2LConfProfL2Atpr,Unsigned32,read-create,,current,,The maximum aggregate transmit power reduction (in dB) that can be performed at transition of L0 to L2 state or through a single Power Trim in the L2 state. It ranges from 0 dB to 31 dB.
.1.3.6.1.2.1.10.251.1.5.1.2.1.34,VDSL2-LINE-MIB::xdsl2LConfProfL2Atprt,Unsigned32,read-create,,current,,The total maximum aggregate transmit power reduction (in dB) that can be performed in an L2 state. This is the sum of all reductions of L2 Requests (i.e., at transition of L0 to L2 state) and Power Trims.
.1.3.6.1.2.1.10.251.1.5.1.2.1.35,VDSL2-LINE-MIB::xdsl2LConfProfProfiles,BITS,read-create,,current,profile8a(0):profile8b(1):profile8c(2):profile8d(3):profile12a(4):profile12b(5):profile17a(6):profile30a(7),The configuration parameter contains the G.993.2 profiles to be allowed by the near-end xTU on this line. It is coded in a bitmap representation (0 if not allowed, 1 if allowed).
.1.3.6.1.2.1.10.251.1.5.1.2.1.36,VDSL2-LINE-MIB::xdsl2LConfProfDpboEPsd,OCTET,read-create,,current,,This configuration parameter defines the PSD mask that is assumed to be permitted at the exchange. This parameter shall use the same format as xdsl2LConfProfPsdMaskDs (PSDMASKds). The maximum number of breakpoints for xdsl2LConfProfDpboEPsd is 16.
.1.3.6.1.2.1.10.251.1.5.1.2.1.37,VDSL2-LINE-MIB::xdsl2LConfProfDpboEsEL,Unsigned32,read-create,,current,,This configuration parameter defines the assumed electrical length of cables (E-side cables) connecting exchange-based DSL services to a remote flexibility point (cabinet), that hosts the xTU-C that is subject to spectrally shaped downstream power back- off (DPBO) depending on this length. The electrical length is defined as the loss (in dB) of an equivalent length of hypothetical cable at a reference frequency defined by the network operator or in spectrum management regulations. This parameter shall be coded as an unsigned integer representing an electrical length from 0 dB (coded as 0) to 255.5 dB (coded as 511) in steps of 0.5 dB. All values in the range are valid. If this parameter is set to '0', the DPBO shall be disabled.
.1.3.6.1.2.1.10.251.1.5.1.2.1.38,VDSL2-LINE-MIB::xdsl2LConfProfDpboEsCableModelA,Unsigned32,read-create,,current,,The E-side Cable Model parameter A (DPBOESCMA) of the cable model (DPBOESCM) for cables connecting exchange-based DSL services to a remote flexibility point (cabinet), that hosts the xTU-C that is subject to spectrally shaped downstream power back- off (DPBO) depending on this value. The cable model is in terms of three scalars xdsl2LConfProfDpboEsCableModelA (DPBOESCMA), xdsl2LConfProfDpboEsCableModelB(DPBOESCMB), and xdsl2LConfProfDpboEsCableModelC (DPBOESCMC), that are used to estimate the frequency dependent loss of E-side cables calculated from the xdsl2LConfProfDpboEsEL (DPBOESEL) parameter. Possible values shall be coded as unsigned integers representing a scalar value from -1 (coded as 0) to 1.5 (coded as 640) in steps of 2^-8. All values in the range are valid. This parameter is used only for G.993.2.
.1.3.6.1.2.1.10.251.1.5.1.2.1.39,VDSL2-LINE-MIB::xdsl2LConfProfDpboEsCableModelB,Unsigned32,read-create,,current,,The E-side Cable Model parameter B (DPBOESCMB) of the cable model (DPBOESCM) for cables connecting exchange-based DSL services to a remote flexibility point (cabinet), that hosts the xTU-C that is subject to spectrally shaped downstream power back- off (DPBO) depending on this value. The cable model is in terms of three scalars dsl2LConfProfDpboEsCableModelA (DPBOESCMA), xdsl2LConfProfDpboEsCableModelB(DPBOESCMB), and xdsl2LConfProfDpboEsCableModelC (DPBOESCMC), that are used to estimate the frequency dependent loss of E-side cables calculated from the xdsl2LConfProfDpboEsEL (DPBOESEL) parameter. Possible values shall be coded as unsigned integers representing a scalar value from -1 (coded as 0) to 1.5 (coded as 640) in steps of 2^-8. All values in the range are valid. This parameter is used only for G.993.2.
.1.3.6.1.2.1.10.251.1.5.1.2.1.40,VDSL2-LINE-MIB::xdsl2LConfProfDpboEsCableModelC,Unsigned32,read-create,,current,,The E-side Cable Model parameter C (DPBOESCMC) of the cable model (DPBOESCM) for cables connecting exchange-based DSL services to a remote flexibility point (cabinet), that hosts the xTU-C that is subject to spectrally shaped downstream power back- off (DPBO) depending on this value. The cable model is in terms of three scalars xdsl2LConfProfDpboEsCableModelA (DPBOESCMA), xdsl2LConfProfDpboEsCableModelB(DPBOESCMB), and xdsl2LConfProfDpboEsCableModelC (DPBOESCMC), that are used to estimate the frequency dependent loss of E-side cables calculated from the xdsl2LConfProfDpboEsEL (DPBOESEL) parameter. Possible values shall be coded as unsigned integers representing a scalar value from -1 (coded as 0) to 1.5 (coded as 640) in steps of 2^-8. All values in the range are valid. This parameter is used only for G.993.2.
.1.3.6.1.2.1.10.251.1.5.1.2.1.41,VDSL2-LINE-MIB::xdsl2LConfProfDpboMus,Unsigned32,read-create,,current,,This configuration parameter defines the assumed Minimum Usable receive PSD mask (in dBm/Hz) for exchange-based services, used to modify parameter xdsl2LConfProfDpboFMax (DPBOFMAX) defined below (to determine the DPBO). It shall be coded as an unsigned integer representing a PSD mask level from 0 dBm/Hz (coded as 0) to -127.5 dBm/Hz (coded as 255) in steps of 0.5 dBm/Hz. All values in the range are valid. NOTE - The PSD mask level is 3.5 dB above the signal PSD level. This parameter is used only for G.993.2.
.1.3.6.1.2.1.10.251.1.5.1.2.1.42,VDSL2-LINE-MIB::xdsl2LConfProfDpboFMin,Unsigned32,read-create,,current,,This configuration parameter defines the minimum frequency from which the DPBO shall be applied. It ranges from 0 kHz (coded as 0) to 8832 kHz (coded as 2048) in steps of 4.3125 kHz. This parameter is used only for G.993.2.
.1.3.6.1.2.1.10.251.1.5.1.2.1.43,VDSL2-LINE-MIB::xdsl2LConfProfDpboFMax,Unsigned32,read-create,,current,,This configuration parameter defines the maximum frequency at which DPBO may be applied. It ranges from 138 kHz (coded as 32) to 29997.75 kHz (coded as 6956) in steps of 4.3125 kHz. This parameter is used only for G.993.2.
.1.3.6.1.2.1.10.251.1.5.1.2.1.44,VDSL2-LINE-MIB::xdsl2LConfProfUpboKL,Unsigned32,read-create,,current,,This configuration parameter defines the electrical length expressed in dB at 1 MHz, kl0, configured by the CO-MIB. The value ranges from 0 (coded as 0) to 128 dB (coded as 1280) in steps of 0.1 dB. This parameter is relevant only if xdsl2LConfProfUpboKLF is set to 'override(2)', which indicates that this parameter's value will override the VTUs' determination of the electrical length. If xdsl2LConfProfUpboKLF is set either to auto(1) or disableUpbo(3), then this parameter will be ignored.
.1.3.6.1.2.1.10.251.1.5.1.2.1.45,VDSL2-LINE-MIB::xdsl2LConfProfUpboKLF,INTEGER,read-create,,current,auto(1):override(2):disableUpbo(3),Defines the upstream power backoff force mode.
.1.3.6.1.2.1.10.251.1.5.1.2.1.46,VDSL2-LINE-MIB::xdsl2LConfProfUs0Mask,BITS,read-create,,current,eu32(0):eu36(1):eu40(2):eu44(3):eu48(4):eu52(5):eu56(6):eu60(7):eu64(8):eu128(9):reserved1(10):reserved2(11):reserved3(12):reserved4(13):reserved5(14):reserved6(15):adlu32(16):adlu36(17):adlu40(18):adlu44(19):adlu48(20):adlu52(21):adlu56(22):adlu60(23):adlu64(24):adlu128(25):reserved7(26):reserved8(27):reserved9(28):reserved10(29):reserved11(30):reserved12(31),The configuration parameter contains the US0 PSD masks to be allowed by the near-end xTU on the line. This parameter is only defined for G.993.2 Annex A. It is represented as a bitmap (0 if not allowed and 1 if allowed).
.1.3.6.1.2.1.10.251.1.5.1.2.1.47,VDSL2-LINE-MIB::xdsl2LConfProfForceInp,INTEGER,read-create,,current,true(1):false(2),This parameter, when set to 'true' indicates that the framer settings of the bearer shall be selected such that the impulse noise protection computed according to the formula specified in the relevant Recommendation is greater than or equal to the minimal impulse noise protection requirement. This flag shall have the same value for all the bearers of one line in the same direction.
.1.3.6.1.2.1.10.251.1.5.1.2.1.48,VDSL2-LINE-MIB::xdsl2LConfProfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it MUST be first unreferenced from all templates. A row in this table is said to be unreferenced when there is no instance of xdsl2LConfTempLineProfile that refers to the row. When a row is created in this table, the SNMP agent should also create corresponding rows in the tables xdsl2LineConfProfModeSpecTable and xdsl2LineConfProfModeSpecBandUsTable. When a row is deleted in this table, the SNMP agent should also delete corresponding rows in the tables xdsl2LineConfProfModeSpecTable and xdsl2LineConfProfModeSpecBandUsTable.
.1.3.6.1.2.1.10.251.1.5.1.3,VDSL2-LINE-MIB::xdsl2LineConfProfModeSpecTable,,not-accessible,,current,,The table xdsl2LineConfProfModeSpecTable extends the DSL line configuration profile by xDSL Mode-Specific parameters. A row in this table that has an index of xdsl2LConfProfXdslMode == defMode(1), is called a 'mandatory' row or 'default' row. A row in this table that has an index such that xdsl2LConfProfXdslMode is not equal to defMode(1), is called an 'optional' row or 'mode-specific' row. When a row in the xdsl2LineConfProfTable table (the parent row) is created, the SNMP agent will automatically create a 'mandatory' row in this table. When the parent row is deleted, the SNMP agent will automatically delete all associated rows in this table. Any attempt to delete the 'mandatory' row using the xdsl2LConfProfModeSpecRowStatus object will be rejected by the SNMP agent. The manager MAY create an 'optional' row in this table using the xdsl2LConfProfModeSpecRowStatus object if the parent row exists. The manager MAY delete an 'optional' row in this table using the xdsl2LConfProfModeSpecRowStatus object at any time. If the actual transmission mode of a DSL line does not match one of the 'optional' rows in this table, then the line will use the PSD configuration from the 'mandatory' row. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.1.3.1,VDSL2-LINE-MIB::xdsl2LineConfProfModeSpecEntry,,not-accessible,xdsl2LConfProfProfileName:xdsl2LConfProfXdslMode,current,,The table xdsl2LineConfProfModeSpecTable extends the DSL line configuration profile by DSL Mode-Specific parameters.
.1.3.6.1.2.1.10.251.1.5.1.3.1.1,VDSL2-LINE-MIB::xdsl2LConfProfXdslMode,INTEGER,not-accessible,,current,defMode(1):ansit1413(2):etsi(3):g9921PotsNonOverlapped(4):g9921PotsOverlapped(5):g9921IsdnNonOverlapped(6):g9921isdnOverlapped(7):g9921tcmIsdnNonOverlapped(8):g9921tcmIsdnOverlapped(9):g9922potsNonOverlapped(10):g9922potsOverlapped(11):g9922tcmIsdnNonOverlapped(12):g9922tcmIsdnOverlapped(13):g9921tcmIsdnSymmetric(14):g9923PotsNonOverlapped(20):g9923PotsOverlapped(21):g9923IsdnNonOverlapped(22):g9923isdnOverlapped(23):g9924potsNonOverlapped(26):g9924potsOverlapped(27):g9923AnnexIAllDigNonOverlapped(30):g9923AnnexIAllDigOverlapped(31):g9923AnnexJAllDigNonOverlapped(32):g9923AnnexJAllDigOverlapped(33):g9924AnnexIAllDigNonOverlapped(34):g9924AnnexIAllDigOverlapped(35):g9923AnnexLMode1NonOverlapped(36):g9923AnnexLMode2NonOverlapped(37):g9923AnnexLMode3Overlapped(38):g9923AnnexLMode4Overlapped(39):g9923AnnexMPotsNonOverlapped(40):g9923AnnexMPotsOverlapped(41):g9925PotsNonOverlapped(42):g9925PotsOverlapped(43):g9925IsdnNonOverlapped(44):g9925isdnOverlapped(45):g9925AnnexIAllDigNonOverlapped(48):g9925AnnexIAllDigOverlapped(49):g9925AnnexJAllDigNonOverlapped(50):g9925AnnexJAllDigOverlapped(51):g9925AnnexMPotsNonOverlapped(52):g9925AnnexMPotsOverlapped(53):g9932AnnexA(58):g9932AnnexB(59):g9932AnnexC(60),The DSL Mode is a way of categorizing the various xDSL transmission modes into groups, each group (xDSL Mode) shares the same PSD configuration. There should be multiple entries in this table for a given line profile in case multiple bits are set in xdsl2LConfProfXtuTransSysEna for that profile.
.1.3.6.1.2.1.10.251.1.5.1.3.1.2,VDSL2-LINE-MIB::xdsl2LConfProfMaxNomPsdDs,Integer32,read-create,,current,,The maximum nominal transmit PSD in the downstream direction during initialization and Showtime. It ranges from -600 to -300 units of 0.1 dBm/Hz (physical values are -60 to -30 dBm/Hz).
.1.3.6.1.2.1.10.251.1.5.1.3.1.3,VDSL2-LINE-MIB::xdsl2LConfProfMaxNomPsdUs,Integer32,read-create,,current,,The maximum nominal transmit PSD in the upstream direction during initialization and Showtime. It ranges from -600 to -300 units of 0.1 dBm/Hz (physical values are -60 to -30 dBm/Hz).
.1.3.6.1.2.1.10.251.1.5.1.3.1.4,VDSL2-LINE-MIB::xdsl2LConfProfMaxNomAtpDs,Unsigned32,read-create,,current,,The maximum nominal aggregate to transmit power in the downstream direction during initialization and Showtime. It ranges from 0 to 255 units of 0.1 dBm (physical values are 0 to 25.5 dBm).
.1.3.6.1.2.1.10.251.1.5.1.3.1.5,VDSL2-LINE-MIB::xdsl2LConfProfMaxNomAtpUs,Unsigned32,read-create,,current,,The maximum nominal aggregate transmit power in the upstream direction during initialization and Showtime. It ranges from 0 to 255 units of 0.1 dBm (physical values are 0 to 25.5 dBm).
.1.3.6.1.2.1.10.251.1.5.1.3.1.6,VDSL2-LINE-MIB::xdsl2LConfProfMaxAggRxPwrUs,Integer32,read-create,,current,,The maximum upstream aggregate receive power over the relevant set of subcarriers. The xTU-C should verify that the upstream power cutback is such that this maximum aggregate receive power value is honored. It ranges from -255 to 255 units of 0.1 dBm (physical values are -25.5 to 25.5 dBm). A value of 0x7FFFFFFF (2147483647) means that there is no limit.
.1.3.6.1.2.1.10.251.1.5.1.3.1.7,VDSL2-LINE-MIB::xdsl2LConfProfPsdMaskDs,OCTET,read-create,,current,,The downstream PSD mask applicable at the U-C2 reference point. This parameter is used only for G.992.5 and it may impose PSD restrictions (breakpoints) in addition to the Limit PSD mask defined in G.992.5. This is a string of 32 pairs of values in the following structure: Octets 0-1 - Index of the first subcarrier used in the context of a first breakpoint. Octet 2 - The PSD reduction for the subcarrier indicated in octets 0 and 1. Octets 3-5 - Same, for a second breakpoint. Octets 6-8 - Same, for a third breakpoint. This architecture continues until octets 94-95, which are associated with a 32nd breakpoint. Each subcarrier index is an unsigned number in the range 0 and NSCds-1. Each PSD reduction value is in the range 0 (0 dBm/Hz) to 255 (-127.5 dBm/Hz) with steps of 0.5 dBm/Hz. Valid values are in the range 0 to 190 (0 to -95 dBm/Hz). When the number of breakpoints is less than 32, all remaining octets are set to the value '0'. Note that the content of this object should be correlated with the subcarrier mask and with the RFI setup.
.1.3.6.1.2.1.10.251.1.5.1.3.1.8,VDSL2-LINE-MIB::xdsl2LConfProfPsdMaskUs,OCTET,read-create,,current,,The upstream PSD mask applicable at the U-R2 reference point. This parameter is used only for G.992.5, and it may impose PSD restrictions (breakpoints) in addition to the Limit PSD mask defined in G.992.5. This is a string of 16 pairs of values in the following structure: Octets 0-1 - Index of the first subcarrier used in the context of a first breakpoint. Octet 2 - The PSD reduction for the subcarrier indicated in octets 0 and 1. Octets 3-5 - Same, for a second breakpoint. Octets 6-8 - Same, for a third breakpoint. This architecture continues until octets 9-47, which are associated with a 16th breakpoint. Each subcarrier index is an unsigned number in the range 0 and NSCus-1. Each PSD reduction value is in the range 0 (0 dBm/Hz) to 255 (-127.5 dBm/Hz) with steps of 0.5 dBm/Hz. Valid values are in the range 0 to 190 (0 to -95 dBm/Hz). When the number of breakpoints is less than 16, all remaining octets are set to the value '0'. Note that the content of this object should be correlated with the subcarrier mask and with the RFI setup.
.1.3.6.1.2.1.10.251.1.5.1.3.1.9,VDSL2-LINE-MIB::xdsl2LConfProfPsdMaskSelectUs,INTEGER,read-create,,current,adlu32Eu32(1):adlu36Eu36(2):adlu40Eu40(3):adlu44Eu44(4):adlu48Eu48(5):adlu52Eu52(6):adlu56Eu56(7):adlu60Eu60(8):adlu64Eu64(9),The selected upstream PSD mask. This parameter is used only for Annexes J and M of G.992.3 and G.992.5, and the same selection is used for all relevant enabled bits in xdsl2LConfProfXtuTransSysEna.
.1.3.6.1.2.1.10.251.1.5.1.3.1.10,VDSL2-LINE-MIB::xdsl2LConfProfClassMask,INTEGER,read-create,,current,none(1):a998ORb997M1cORc998B(2):b997M1xOR998co(3):b997M2x(4):b998M1x(5):b998M2x(6):b998AdeM2x(7):bHpeM1(8),In order to reduce the number of configuration possibilities, the limit Power Spectral Density masks (see LIMITMASK) are grouped in PSD mask classes. Each class is designed such that the PSD levels of each limit PSD mask of a specific class are equal in their respective passband above 552 kHz. This parameter is defined per VDSL2 Annex enabled in the xdsl2LConfProfXtuTransSysEna object. It selects a single PSD mask class per Annex that is activated at the VTU-O.
.1.3.6.1.2.1.10.251.1.5.1.3.1.11,VDSL2-LINE-MIB::xdsl2LConfProfLimitMask,BITS,read-create,,current,profile8Limit1(0):profile8Limit2(1):profile8Limit3(2):profile8Limit4(3):profile8Limit5(4):profile8Limit6(5):profile8Limit7(6):profile8Limit8(7):profile8Limit9(8):profile8Limit10(9):profile8Limit11(10):profile8Limit12(11):profile8Limit13(12):profile8Limit14(13):profile8Limit15(14):profile8Limit16(15):profile12Limit1(16):profile12Limit2(17):profile12Limit3(18):profile12Limit4(19):profile12Limit5(20):profile12Limit6(21):profile12Limit7(22):profile12Limit8(23):profile12Limit9(24):profile12Limit10(25):profile12Limit11(26):profile12Limit12(27):profile12Limit13(28):profile12Limit14(29):profile12Limit15(30):profile12Limit16(31):profile17Limit1(32):profile17Limit2(33):profile17Limit3(34):profile17Limit4(35):profile17Limit5(36):profile17Limit6(37):profile17Limit7(38):profile17Limit8(39):profile17Limit9(40):profile17Limit10(41):profile17Limit11(42):profile17Limit12(43):profile17Limit13(44):profile17Limit14(45):profile17Limit15(46):profile17Limit16(47):profile30Limit1(48):profile30Limit2(49):profile30Limit3(50):profile30Limit4(51):profile30Limit5(52):profile30Limit6(53):profile30Limit7(54):profile30Limit8(55):profile30Limit9(56):profile30Limit10(57):profile30Limit11(58):profile30Limit12(59):profile30Limit13(60):profile30Limit14(61):profile30Limit15(62):profile30Limit16(63),This configuration parameter contains the G.993.2 limit PSD masks of the selected PSD mask class, enabled by the near-end xTU on this line for each class of profiles. This parameter is defined per VDSL2 Annex enabled in the xdsl2LConfProfXtuTransSysEna object. Through this parameter, several limit PSD masks of the selected PSD mask class (xdsl2LConfProfClassMask) may be enabled. The enabling parameter is coded in a bitmap representation (0 if the associated mask is not allowed, 1 if it is allowed).
.1.3.6.1.2.1.10.251.1.5.1.3.1.12,VDSL2-LINE-MIB::xdsl2LConfProfUs0Disable,BITS,read-create,,current,profile8Us0Disable1(0):profile8Us0Disable2(1):profile8Us0Disable3(2):profile8Us0Disable4(3):profile8Us0Disable5(4):profile8Us0Disable6(5):profile8Us0Disable7(6):profile8Us0Disable8(7):profile8Us0Disable9(8):profile8Us0Disable10(9):profile8Us0Disable11(10):profile8Us0Disable12(11):profile8Us0Disable13(12):profile8Us0Disable14(13):profile8Us0Disable15(14):profile8Us0Disable16(15):profile12Us0Disable1(16):profile12Us0Disable2(17):profile12Us0Disable3(18):profile12Us0Disable4(19):profile12Us0Disable5(20):profile12Us0Disable6(21):profile12Us0Disable7(22):profile12Us0Disable8(23):profile12Us0Disable9(24):profile12Us0Disable10(25):profile12Us0Disable11(26):profile12Us0Disable12(27):profile12Us0Disable13(28):profile12Us0Disable14(29):profile12Us0Disable15(30):profile12Us0Disable16(31):profile17Us0Disable1(32):profile17Us0Disable2(33):profile17Us0Disable3(34):profile17Us0Disable4(35):profile17Us0Disable5(36):profile17Us0Disable6(37):profile17Us0Disable7(38):profile17Us0Disable8(39):profile17Us0Disable9(40):profile17Us0Disable10(41):profile17Us0Disable11(42):profile17Us0Disable12(43):profile17Us0Disable13(44):profile17Us0Disable14(45):profile17Us0Disable15(46):profile17Us0Disable16(47):profile30Us0Disable1(48):profile30Us0Disable2(49):profile30Us0Disable3(50):profile30Us0Disable4(51):profile30Us0Disable5(52):profile30Us0Disable6(53):profile30Us0Disable7(54):profile30Us0Disable8(55):profile30Us0Disable9(56):profile30Us0Disable10(57):profile30Us0Disable11(58):profile30Us0Disable12(59):profile30Us0Disable13(60):profile30Us0Disable14(61):profile30Us0Disable15(62):profile30Us0Disable16(63),This configuration parameter indicates if the use of the US0 is disabled for each limit PSD mask enabled in the xdsl2LConfProfLimitMask parameter. This parameter is defined per VDSL2 Annex enabled in the xdsl2LConfProfXtuTransSysEna object. For each limit PSD mask enabled in the xdsl2LConfProfLimitMask parameter, a bit shall indicate if the US0 is disabled. The disabling parameter is coded as a bitmap. The bit is set to '1' if the US0 is disabled for the associated limit mask. This parameter and the xdsl2LConfProfLimitMask parameter use the same structure.
.1.3.6.1.2.1.10.251.1.5.1.3.1.13,VDSL2-LINE-MIB::xdsl2LConfProfModeSpecRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. This row is activated by setting this object to 'active'. A 'mandatory' row, as defined in the DESCRIPTION clause of xdsl2LineConfProfModeSpecTable, cannot be deleted at all. A 'mandatory' row can be taken out of service (by setting this object to 'notInService') if the parent row in the xdsl2LineConfProfTable table is not in the 'active' state. An 'optional' row (or 'mode-specific' row) can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService') at any time.
.1.3.6.1.2.1.10.251.1.5.1.4,VDSL2-LINE-MIB::xdsl2LineConfProfModeSpecBandUsTable,,not-accessible,,current,,The table xdsl2LineConfProfModeSpecBandUsTable extends xdsl2LineConfProfModeSpecTable with upstream-band-specific parameters for VDSL2, such as upstream power back-off parameters xdsl2LConfProfUpboPsdA and xdsl2LConfProfUpboPsdB (UPBOPSD-pb). When a parent 'mandatory row' is created in xdsl2LineConfProfModeSpecTable, the SNMP agent will automatically create several 'mandatory' rows in this table -- one for each upstream band: Note: A mandatory row is one where xdsl2LConfProfXdslMode = defMode(1). When the parent row is deleted, the SNMP agent will automatically delete all associated rows in this table. Any attempt to delete a 'mandatory' row using the xdsl2LConfProfModeSpecBandUsRowStatus object will be rejected by the SNMP agent. The manager MAY create a new 'optional' row in this table using the xdsl2LConfProfModeSpecBandUsRowStatus object if the associated parent row exists, and the value of xdsl2LConfProfXdslMode is a G.993.2 value. The manager MAY delete an 'optional' row in this table using the xdsl2LConfProfModeSpecBandUsRowStatus object at any time. With respect to the xdsl2LConfProfUpboPsdA and xdsl2LConfProfUpboPsdB parameters, for a given upstream band, if an optional row is missing from this table, then that means upstream power back-off is disabled for that upstream band. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.1.4.1,VDSL2-LINE-MIB::xdsl2LineConfProfModeSpecBandUsEntry,,not-accessible,xdsl2LConfProfProfileName:xdsl2LConfProfXdslMode:xdsl2LConfProfXdslBandUs,current,,The table xdsl2LineConfProfModeSpecBandUsTable extends xdsl2LineConfProfModeSpecTable with upstream-band-specific parameters for VDSL2, such as upstream power back-off parameters xdsl2LConfProfUpboPsdA and xdsl2LConfProfUpboPsdB (UPBOPSD- pb).
.1.3.6.1.2.1.10.251.1.5.1.4.1.1,VDSL2-LINE-MIB::xdsl2LConfProfXdslBandUs,INTEGER,not-accessible,,current,us1(5):us2(7):us3(9):us4(11),Each value identifies a specific band in the upstream transmission direction (excluding the US0 band).
.1.3.6.1.2.1.10.251.1.5.1.4.1.2,VDSL2-LINE-MIB::xdsl2LConfProfUpboPsdA,Integer32,read-create,,current,,This configuration parameter defines the 'a' reference parameter of the UPBO reference PSD used to compute the upstream power back-off for the upstream band. A UPBO PSD defined for each band shall consist of two parameters [a, b]. Parameter 'a' (xdsl2LConfProfUpboPsdA) ranges from 40 dBm/Hz (coded as 4000) to 80.95 dBm/Hz (coded as 8095) in steps of 0.01 dBm/Hz; and parameter 'b' (xdsl2LConfProfUpboPsdB) ranges from 0 dBm/Hz (coded as 0) to 40.95 dBm/Hz (coded as 4095) in steps of 0.01 dBm/Hz. The UPBO reference PSD at the frequency 'f' expressed in MHz shall be equal to '-a-b(SQRT(f))'. Setting xdsl2LConfProfUpboPsdA to 4000 and xdsl2LConfProfUpboPsdB to 0 is a special configuration to disable UPBO in the respective upstream band.
.1.3.6.1.2.1.10.251.1.5.1.4.1.3,VDSL2-LINE-MIB::xdsl2LConfProfUpboPsdB,Integer32,read-create,,current,,This configuration parameter defines the 'b' reference parameter of the UPBO reference PSD used to compute the upstream power back-off for the upstream band. A UPBO PSD defined for each band shall consist of two parameters [a, b]. Parameter 'a' (xdsl2LConfProfUpboPsdA) ranges from 40 dBm/Hz (coded as 4000) to 80.95 dBm/Hz (coded as 8095) in steps of 0.01 dBm/Hz; and parameter 'b' (xdsl2LConfProfUpboPsdB) ranges from 0 dBm/Hz (coded as 0) to 40.95 dBm/Hz (coded as 4095) in steps of 0.01 dBm/Hz. The UPBO reference PSD at the frequency 'f' expressed in MHz shall be equal to '-a-b(SQRT(f))'. Setting xdsl2LConfProfUpboPsdA to 4000 and xdsl2LConfProfUpboPsdB to 0 is a special configuration to disable UPBO in the respective upstream band.
.1.3.6.1.2.1.10.251.1.5.1.4.1.4,VDSL2-LINE-MIB::xdsl2LConfProfModeSpecBandUsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. This row is activated by setting this object to 'active'. A 'mandatory' row, as defined in the DESCRIPTION clause of xdsl2LineConfProfModeSpecBandUsTable, cannot be deleted at all. A 'mandatory' row can be taken out of service (by setting this object to 'notInService') if the parent row in the xdsl2LineConfProfModeSpecTable table is not in the 'active' state. An 'optional' row (or 'mode-specific' row) can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService') at any time.
.1.3.6.1.2.1.10.251.1.5.2,VDSL2-LINE-MIB::xdsl2ProfileChannel,,,,,,
.1.3.6.1.2.1.10.251.1.5.2.1,VDSL2-LINE-MIB::xdsl2ChConfProfileTable,,not-accessible,,current,,The table xdsl2ChConfProfileTable contains DSL channel profile configuration. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.2.1.1,VDSL2-LINE-MIB::xdsl2ChConfProfileEntry,,not-accessible,xdsl2ChConfProfProfileName,current,,A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.251.1.5.2.1.1.1,VDSL2-LINE-MIB::xdsl2ChConfProfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.251.1.5.2.1.1.2,VDSL2-LINE-MIB::xdsl2ChConfProfMinDataRateDs,Unsigned32,read-create,,current,,Minimum Data Rate on Downstream direction. The minimum net data rate for the bearer channel, coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.3,VDSL2-LINE-MIB::xdsl2ChConfProfMinDataRateUs,Unsigned32,read-create,,current,,Minimum Data Rate on Upstream direction. The minimum net data rate for the bearer channel, coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.4,VDSL2-LINE-MIB::xdsl2ChConfProfMinResDataRateDs,Unsigned32,read-create,,current,,Minimum Reserved Data Rate on Downstream direction. The minimum reserved net data rate for the bearer channel, coded in bit/s. This parameter is used only if the Rate Adaptation Mode in the direction of the bearer channel (i.e., xdsl2LConfProfRaModeDs) is set to 'dynamicRa'.
.1.3.6.1.2.1.10.251.1.5.2.1.1.5,VDSL2-LINE-MIB::xdsl2ChConfProfMinResDataRateUs,Unsigned32,read-create,,current,,Minimum Reserved Data Rate on Upstream direction. The minimum reserved net data rate for the bearer channel, coded in bit/s. This parameter is used only if the Rate Adaptation Mode in the direction of the bearer channel (i.e., xdsl2LConfProfRaModeUs) is set to 'dynamicRa'.
.1.3.6.1.2.1.10.251.1.5.2.1.1.6,VDSL2-LINE-MIB::xdsl2ChConfProfMaxDataRateDs,Unsigned32,read-create,,current,,Maximum Data Rate on Downstream direction. The maximum net data rate for the bearer channel, coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.7,VDSL2-LINE-MIB::xdsl2ChConfProfMaxDataRateUs,Unsigned32,read-create,,current,,Maximum Data Rate on Upstream direction. The maximum net data rate for the bearer channel, coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.8,VDSL2-LINE-MIB::xdsl2ChConfProfMinDataRateLowPwrDs,Unsigned32,read-create,,current,,This parameter specifies the minimum net data rate for the bearer channel as desired by the operator of the system during the low power state (L1/L2). The power management low power states L1 and L2 are defined in ITU-T Recommendations G.992.2 and G.992.3, respectively. The data rate is coded in steps of bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.9,VDSL2-LINE-MIB::xdsl2ChConfProfMinDataRateLowPwrUs,Unsigned32,read-create,,current,,This parameter specifies the minimum net data rate for the bearer channel as desired by the operator of the system during the low power state (L1/L2). The power management low power states L1 and L2 are defined in ITU-T Recommendations G.992.2 and G.992.3, respectively. The data rate is coded in steps of bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.10,VDSL2-LINE-MIB::xdsl2ChConfProfMaxDelayDs,Unsigned32,read-create,,current,,Maximum Interleave Delay on Downstream direction. The maximum one-way interleaving delay introduced by the PMS-TC on Downstream direction. The xTUs shall choose the S (factor) and D (depth) values such that the actual one-way interleaving delay (Xdsl2ChStatusActDelay) is as close as possible to, but less than or equal to, xdsl2ChConfProfMaxDelayDs. The delay is coded in ms, with the value 0 indicating no delay bound is being imposed.
.1.3.6.1.2.1.10.251.1.5.2.1.1.11,VDSL2-LINE-MIB::xdsl2ChConfProfMaxDelayUs,Unsigned32,read-create,,current,,Maximum Interleave Delay on Upstream direction. The maximum one-way interleaving delay introduced by the PMS-TC on Upstream direction. The xTUs shall choose the S (factor) and D (depth) values such that the actual one-way interleaving delay (Xdsl2ChStatusActDelay) is as close as possible to, but less than or equal to, xdsl2ChConfProfMaxDelayUs. The delay is coded in ms, with the value 0 indicating no delay bound is being imposed.
.1.3.6.1.2.1.10.251.1.5.2.1.1.12,VDSL2-LINE-MIB::xdsl2ChConfProfMinProtectionDs,INTEGER,read-create,,current,noProtection(1):halfSymbol(2):singleSymbol(3):twoSymbols(4):threeSymbols(5):fourSymbols(6):fiveSymbols(7):sixSymbols(8):sevenSymbols(9):eightSymbols(10):nineSymbols(11):tenSymbols(12):elevenSymbols(13):twelveSymbols(14):thirteeSymbols(15):fourteenSymbols(16):fifteenSymbols(17):sixteenSymbols(18),This parameter specifies the minimum impulse noise protection for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 4.3125 kHz. The impulse noise protection is expressed in DMT symbols with a subcarrier spacing of 4.3125 kHz and can take the values 1/2 and any integer from 0 to 16, inclusive. If the xTU does not support the configured INPMIN value, it shall use the nearest supported impulse noise protection greater than INPMIN.
.1.3.6.1.2.1.10.251.1.5.2.1.1.13,VDSL2-LINE-MIB::xdsl2ChConfProfMinProtectionUs,INTEGER,read-create,,current,noProtection(1):halfSymbol(2):singleSymbol(3):twoSymbols(4):threeSymbols(5):fourSymbols(6):fiveSymbols(7):sixSymbols(8):sevenSymbols(9):eightSymbols(10):nineSymbols(11):tenSymbols(12):elevenSymbols(13):twelveSymbols(14):thirteeSymbols(15):fourteenSymbols(16):fifteenSymbols(17):sixteenSymbols(18),This parameter specifies the minimum impulse noise protection for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 4.3125 kHz. The impulse noise protection is expressed in DMT symbols with a subcarrier spacing of 4.3125 kHz and can take the values 1/2 and any integer from 0 to 16, inclusive. If the xTU does not support the configured INPMIN value, it shall use the nearest supported impulse noise protection greater than INPMIN.
.1.3.6.1.2.1.10.251.1.5.2.1.1.14,VDSL2-LINE-MIB::xdsl2ChConfProfMinProtection8Ds,INTEGER,read-create,,current,noProtection(1):singleSymbol(2):twoSymbols(3):threeSymbols(4):fourSymbols(5):fiveSymbols(6):sixSymbols(7):sevenSymbols(8):eightSymbols(9):nineSymbols(10):tenSymbols(11):elevenSymbols(12):twelveSymbols(13):thirteeSymbols(14):fourteenSymbols(15):fifteenSymbols(16):sixteenSymbols(17),This parameter specifies the minimum impulse noise protection for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 8.625 kHz. The impulse noise protection is expressed in DMT symbols with a subcarrier spacing of 8.625 kHz.
.1.3.6.1.2.1.10.251.1.5.2.1.1.15,VDSL2-LINE-MIB::xdsl2ChConfProfMinProtection8Us,INTEGER,read-create,,current,noProtection(1):singleSymbol(2):twoSymbols(3):threeSymbols(4):fourSymbols(5):fiveSymbols(6):sixSymbols(7):sevenSymbols(8):eightSymbols(9):nineSymbols(10):tenSymbols(11):elevenSymbols(12):twelveSymbols(13):thirteeSymbols(14):fourteenSymbols(15):fifteenSymbols(16):sixteenSymbols(17),This parameter specifies the minimum impulse noise protection for the bearer channel if it is transported over DMT symbols with a subcarrier spacing of 8.625 kHz. The impulse noise protection is expressed in DMT symbols with a subcarrier spacing of 8.625 kHz.
.1.3.6.1.2.1.10.251.1.5.2.1.1.16,VDSL2-LINE-MIB::xdsl2ChConfProfMaxBerDs,INTEGER,read-create,,current,eminus3(1):eminus5(2):eminus7(3),Maximum Bit Error Ratio on Downstream direction. The maximum bit error ratio for the bearer channel.
.1.3.6.1.2.1.10.251.1.5.2.1.1.17,VDSL2-LINE-MIB::xdsl2ChConfProfMaxBerUs,INTEGER,read-create,,current,eminus3(1):eminus5(2):eminus7(3),Maximum Bit Error Ratio on Upstream direction. The maximum bit error ratio for the bearer channel.
.1.3.6.1.2.1.10.251.1.5.2.1.1.18,VDSL2-LINE-MIB::xdsl2ChConfProfUsDataRateDs,Unsigned32,read-create,,current,,Data Rate Threshold Upshift for Downstream direction. An 'Up-Shift rate change' event is triggered when the actual downstream data rate exceeds, by more than the threshold, the data rate at the last entry into Showtime. The parameter is coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.19,VDSL2-LINE-MIB::xdsl2ChConfProfDsDataRateDs,Unsigned32,read-create,,current,,Data Rate Threshold Downshift for Downstream direction. A 'Down-Shift rate change' event is triggered when the actual downstream data rate is below the data rate at the last entry into Showtime, by more than the threshold. The parameter is coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.20,VDSL2-LINE-MIB::xdsl2ChConfProfUsDataRateUs,Unsigned32,read-create,,current,,Data Rate Threshold Upshift for Upstream direction. An 'Up-Shift rate change' event is triggered when the actual upstream data rate exceeds, by more than the threshold, the data rate at the last entry into Showtime. The parameter is coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.21,VDSL2-LINE-MIB::xdsl2ChConfProfDsDataRateUs,Unsigned32,read-create,,current,,Data Rate Threshold Downshift for Upstream direction. A 'Down-Shift rate change' event is triggered when the actual upstream data rate is below the data rate at the last entry into Showtime, by more than the threshold. The parameter is coded in bit/s.
.1.3.6.1.2.1.10.251.1.5.2.1.1.22,VDSL2-LINE-MIB::xdsl2ChConfProfImaEnabled,INTEGER,read-create,,current,true(1):false(2),IMA Mode Enable. The parameter enables the IMA operation mode in the ATM Data Path. Relevant only if the channel is of ATM Data Path. When in 'enable' state, the ATM Data Path should comply with the requirements for IMA transmission.
.1.3.6.1.2.1.10.251.1.5.2.1.1.23,VDSL2-LINE-MIB::xdsl2ChConfProfMaxDelayVar,Unsigned32,read-create,,current,,Maximum delay variation (DVMAX). This optional VDSL2-specific parameter specifies the maximum value for the delay variation allowed in an OLR procedure. It is ranges from 1 to 254 units of 0.1 milliseconds (i.e., 0.1 to 25.4 milliseconds) with the special value 255, which indicates that no delay variation bound is imposed.
.1.3.6.1.2.1.10.251.1.5.2.1.1.24,VDSL2-LINE-MIB::xdsl2ChConfProfInitPolicy,INTEGER,read-create,,current,policy0(1):policy1(2),Channel Initialization Policy Selection (CIPOLICY). This optional parameter indicates which policy shall be applied to determine the transceiver configuration parameters at initialization. Those policies are defined in the respective Recommendations.
.1.3.6.1.2.1.10.251.1.5.2.1.1.25,VDSL2-LINE-MIB::xdsl2ChConfProfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it MUST be first unreferenced from all associated templates. A row in xdsl2ChConfProfTable is said to be unreferenced when there is no instance of xdsl2LConfTempChan1ConfProfile, xdsl2LConfTempChan2ConfProfile, xdsl2LConfTempChan3ConfProfile, or xdsl2LConfTempChan4ConfProfile that refers to the row.
.1.3.6.1.2.1.10.251.1.5.3,VDSL2-LINE-MIB::xdsl2ProfileAlarmConf,,,,,,
.1.3.6.1.2.1.10.251.1.5.3.1,VDSL2-LINE-MIB::xdsl2LineAlarmConfTemplateTable,,not-accessible,,current,,The table xdsl2LineAlarConfTemplateTable contains DSL line alarm configuration templates. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.3.1.1,VDSL2-LINE-MIB::xdsl2LineAlarmConfTemplateEntry,,not-accessible,xdsl2LAlarmConfTempTemplateName,current,,A default template with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.251.1.5.3.1.1.1,VDSL2-LINE-MIB::xdsl2LAlarmConfTempTemplateName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.251.1.5.3.1.1.2,VDSL2-LINE-MIB::xdsl2LAlarmConfTempLineProfile,OCTET,read-create,,current,,The value of this object identifies the row in the DSL Line Thresholds Configuration Profile Table (xdsl2LineAlarmConfProfileTable) that applies to this line.
.1.3.6.1.2.1.10.251.1.5.3.1.1.3,VDSL2-LINE-MIB::xdsl2LAlarmConfTempChan1ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the DSL Channel Thresholds Configuration Profile Table (xdsl2ChAlarmConfProfileTable) that applies for DSL bearer channel #1. The channel profile name specified here MUST match the name of an existing row in the xdsl2ChAlarmConfProfileTable table.
.1.3.6.1.2.1.10.251.1.5.3.1.1.4,VDSL2-LINE-MIB::xdsl2LAlarmConfTempChan2ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the DSL Channel Thresholds Configuration Profile Table (xdsl2ChAlarmConfProfileTable) that applies for DSL bearer channel #2. The channel profile name specified here MUST match the name of an existing row in the xdsl2ChAlarmConfProfileTable table. If the channel is unused, then the object is set to a zero-length string.
.1.3.6.1.2.1.10.251.1.5.3.1.1.5,VDSL2-LINE-MIB::xdsl2LAlarmConfTempChan3ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the DSL Channel Thresholds Configuration Profile Table (xdsl2ChAlarmConfProfileTable) that applies for DSL bearer channel #3. The channel profile name specified here MUST match the name of an existing row in the xdsl2ChAlarmConfProfileTable table. This object may be set to a non-zero-length string only if xdsl2LAlarmConfTempChan2ConfProfile contains a non-zero-length string.
.1.3.6.1.2.1.10.251.1.5.3.1.1.6,VDSL2-LINE-MIB::xdsl2LAlarmConfTempChan4ConfProfile,OCTET,read-create,,current,,The value of this object identifies the row in the DSL Channel Thresholds Configuration Profile Table (xdsl2ChAlarmConfProfileTable) that applies for DSL bearer channel #4. The channel profile name specified here MUST match the name of an existing row in the xdsl2ChAlarmConfProfileTable table. This object may be set to a non-zero-length string only if xdsl2LAlarmConfTempChan3ConfProfile contains a non-zero-length string.
.1.3.6.1.2.1.10.251.1.5.3.1.1.7,VDSL2-LINE-MIB::xdsl2LAlarmConfTempRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A template is activated by setting this object to 'active'. Before a template can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it MUST be first unreferenced from all associated lines. A row in this table is said to be unreferenced when there is no instance of xdsl2LineAlarmConfTemplate that refers to the row.
.1.3.6.1.2.1.10.251.1.5.3.2,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileTable,,not-accessible,,current,,The table xdsl2LineAlarmConfProfileTable contains DSL line performance threshold values. If a performance counter exceeds the threshold value specified in this table, then the SNMP agent will issue a threshold trap. Each performance counter has a unique trap type (see NOTIFICATION-TYPE definitions below). One trap will be sent per interval, per interface, per trap type. A value of 0 will disable the trap. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.3.2.1,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileEntry,,not-accessible,xdsl2LineAlarmConfProfileName,current,,A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.251.1.5.3.2.1.1,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.251.1.5.3.2.1.2,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXtucThresh15MinFecs,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MFecs counter, when xdsl2PMLCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.3,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXtucThresh15MinEs,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MEs counter, when xdsl2PMLCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.4,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXtucThresh15MinSes,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MSes counter, when xdsl2PMLCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.5,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXtucThresh15MinLoss,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MLoss counter, when xdsl2PMLCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.6,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXtucThresh15MinUas,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MUas counter, when xdsl2PMLCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.7,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXturThresh15MinFecs,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MFecs counter, when xdsl2PMLCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.8,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXturThresh15MinEs,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MEs counter, when xdsl2PMLCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.9,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXturThresh15MinSes,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MSes counter, when xdsl2PMLCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.10,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXturThresh15MinLoss,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MLoss counter, when xdsl2PMLCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.11,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileXturThresh15MinUas,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLCurr15MUas counter, when xdsl2PMLCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.12,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileThresh15MinFailedFullInt,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLInitCurr15MfailedFullInits counter. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.13,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt,Unsigned32,read-create,,current,,A threshold for the xdsl2PMLInitCurr15MFailedShortInits counter. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.2.1.14,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it MUST be first unreferenced from all associated templates. A row in this table is said to be unreferenced when there is no instance of xdsl2LAlarmConfTempLineProfile that refers to the row.
.1.3.6.1.2.1.10.251.1.5.3.3,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileTable,,not-accessible,,current,,The table xdsl2ChAlarmConfProfileTable contains DSL channel performance threshold values. If a performance counter exceeds the threshold value specified in this table, then the SNMP agent will issue a threshold trap. Each performance counter has a unique trap type (see NOTIFICATION-TYPE definitions below). One trap will be sent per interval per interface per trap type. A value of 0 will disable the trap. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.10.251.1.5.3.3.1,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileEntry,,not-accessible,xdsl2ChAlarmConfProfileName,current,,A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values, unless otherwise specified in this document.
.1.3.6.1.2.1.10.251.1.5.3.3.1.1,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileName,OCTET,not-accessible,,current,,This object identifies a row in this table.
.1.3.6.1.2.1.10.251.1.5.3.3.1.2,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations,Unsigned32,read-create,,current,,A threshold for the xdsl2PMChCurr15MCodingViolations counter, when xdsl2PMChCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.3.1.3,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileXtucThresh15MinCorrected,Unsigned32,read-create,,current,,A threshold for the xdsl2PMChCurr15MCorrectedBlocks counter, when xdsl2PMChCurrUnit is xtuc {1}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.3.1.4,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations,Unsigned32,read-create,,current,,A threshold for the xdsl2PMChCurr15MCodingViolations counter, when xdsl2PMChCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.3.1.5,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileXturThresh15MinCorrected,Unsigned32,read-create,,current,,A threshold for the xdsl2PMChCurr15MCorrectedBlocks counter, when xdsl2PMChCurrUnit is xtur {2}. The value 0 means that no threshold is specified for the associated counter.
.1.3.6.1.2.1.10.251.1.5.3.3.1.6,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it MUST be first unreferenced from all associated templates. A row in xdsl2ChConfProfTable is said to be unreferenced when there is no instance of xdsl2LAlarmConfTempChan1ConfProfile, xdsl2LAlarmConfTempChan2ConfProfile, xdsl2LAlarmConfTempChan3ConfProfile, or xdsl2LAlarmConfTempChan4ConfProfile that refers to the row.
.1.3.6.1.2.1.10.251.1.6,VDSL2-LINE-MIB::xdsl2Scalar,,,,,,
.1.3.6.1.2.1.10.251.1.6.1,VDSL2-LINE-MIB::xdsl2ScalarSC,,,,,,
.1.3.6.1.2.1.10.251.1.6.1.1,VDSL2-LINE-MIB::xdsl2ScalarSCMaxInterfaces,Unsigned32,read-only,,current,,This value determines the maximum number of interfaces supported by xdsl2SCStatusTable, xdsl2SCStatusBandTable, and xdsl2SCStatusSegmentTable.
.1.3.6.1.2.1.10.251.1.6.1.2,VDSL2-LINE-MIB::xdsl2ScalarSCAvailInterfaces,Unsigned32,read-only,,current,,This value determines the currently available number of interfaces listed in xdsl2SCStatusTable, xdsl2SCStatusBandTable, and xdsl2SCStatusSegmentTable.
.1.3.6.1.2.1.10.251.2,VDSL2-LINE-MIB::xdsl2Conformance,,,,,,
.1.3.6.1.2.1.10.251.2.1,VDSL2-LINE-MIB::xdsl2Groups,,,,,,
.1.3.6.1.2.1.10.251.2.1.1,VDSL2-LINE-MIB::xdsl2LineGroup,,,,,,The group of configuration, status, and commands objects on the line level.
.1.3.6.1.2.1.10.251.2.1.2,VDSL2-LINE-MIB::xdsl2LineFallbackGroup,,,,,,The group of configuration, status, and commands objects on the line level that are associated with the fallback feature.
.1.3.6.1.2.1.10.251.2.1.3,VDSL2-LINE-MIB::xdsl2LineBpscGroup,,,,,,The group of configuration, status, and commands objects on the line level that are associated with requesting a bits-per-subcarrier measurement.
.1.3.6.1.2.1.10.251.2.1.4,VDSL2-LINE-MIB::xdsl2LineSegmentGroup,,,,,,The group of status and commands objects on the line level that are used to hold the results of the bits-per-subcarrier measurement.
.1.3.6.1.2.1.10.251.2.1.5,VDSL2-LINE-MIB::xdsl2ChannelStatusGroup,,,,,,The group of status objects on the channel level.
.1.3.6.1.2.1.10.251.2.1.6,VDSL2-LINE-MIB::xdsl2ChannelStatusAtmGroup,,,,,,The group of status objects on the data path level when it is ATM.
.1.3.6.1.2.1.10.251.2.1.7,VDSL2-LINE-MIB::xdsl2ChannelStatusPtmGroup,,,,,,The group of status objects on the data path level when it is PTM.
.1.3.6.1.2.1.10.251.2.1.8,VDSL2-LINE-MIB::xdsl2SCStatusGroup,,,,,,The group of status objects on the subcarrier level. They are updated as a result of a DELT process.
.1.3.6.1.2.1.10.251.2.1.9,VDSL2-LINE-MIB::xdsl2LineInventoryGroup,,,,,,The group of inventory objects per xTU.
.1.3.6.1.2.1.10.251.2.1.10,VDSL2-LINE-MIB::xdsl2LineConfTemplateGroup,,,,,,The group of objects in a line configuration template.
.1.3.6.1.2.1.10.251.2.1.11,VDSL2-LINE-MIB::xdsl2LineConfProfGroup,,,,,,The group of objects in a line configuration profile.
.1.3.6.1.2.1.10.251.2.1.12,VDSL2-LINE-MIB::xdsl2LineConfProfRaGroup,,,,,,The group of objects required for controlling the rate-adaptive behavior of the line.
.1.3.6.1.2.1.10.251.2.1.13,VDSL2-LINE-MIB::xdsl2LineConfProfMsgMinGroup,,,,,,The group of objects required for controlling the rate reserved for Overhead traffic.
.1.3.6.1.2.1.10.251.2.1.14,VDSL2-LINE-MIB::xdsl2LineConfProfModeSpecGroup,,,,,,The group of objects in a line configuration profile that have an instance for each operation mode allowed.
.1.3.6.1.2.1.10.251.2.1.15,VDSL2-LINE-MIB::xdsl2LineConfProfModeSpecBandUsGroup,,,,,,The group of objects in a line configuration profile that have several per-upstream-band instances for each operation mode allowed.
.1.3.6.1.2.1.10.251.2.1.16,VDSL2-LINE-MIB::xdsl2ChConfProfileGroup,,,,,,The group of objects in a channel configuration profile.
.1.3.6.1.2.1.10.251.2.1.17,VDSL2-LINE-MIB::xdsl2ChConfProfileAtmGroup,,,,,,The group of configuration objects required when the data path is ATM.
.1.3.6.1.2.1.10.251.2.1.18,VDSL2-LINE-MIB::xdsl2ChConfProfileMinResGroup,,,,,,The group of configuration objects required for the reserved data rate.
.1.3.6.1.2.1.10.251.2.1.19,VDSL2-LINE-MIB::xdsl2ChConfProfileOptAttrGroup,,,,,,The group of various optional channel configuration parameters.
.1.3.6.1.2.1.10.251.2.1.20,VDSL2-LINE-MIB::xdsl2LineAlarmConfTemplateGroup,,,,,,The group of objects in a line alarm template.
.1.3.6.1.2.1.10.251.2.1.21,VDSL2-LINE-MIB::xdsl2LineAlarmConfProfileGroup,,,,,,The group of objects in a line alarm profile.
.1.3.6.1.2.1.10.251.2.1.22,VDSL2-LINE-MIB::xdsl2ChAlarmConfProfileGroup,,,,,,The group of objects in a channel alarm profile.
.1.3.6.1.2.1.10.251.2.1.23,VDSL2-LINE-MIB::xdsl2PMLineCurrGroup,,,,,,The group of objects that report the line-level counters for current PM intervals.
.1.3.6.1.2.1.10.251.2.1.24,VDSL2-LINE-MIB::xdsl2PMLineInitCurrGroup,,,,,,The group of objects that report the full initialization counters for current PM intervals.
.1.3.6.1.2.1.10.251.2.1.25,VDSL2-LINE-MIB::xdsl2PMLineInitCurrShortGroup,,,,,,The group of objects that report the short initialization counters for current PM intervals.
.1.3.6.1.2.1.10.251.2.1.26,VDSL2-LINE-MIB::xdsl2PMLineHist15MinGroup,,,,,,The group of line-level PM counters for the previous 15-minute intervals.
.1.3.6.1.2.1.10.251.2.1.27,VDSL2-LINE-MIB::xdsl2PMLineHist1DayGroup,,,,,,The group of line-level PM counters for the previous 24-hour intervals.
.1.3.6.1.2.1.10.251.2.1.28,VDSL2-LINE-MIB::xdsl2PMLineInitHist15MinGroup,,,,,,The group of PM counters for the previous 15-minute interval full initializations.
.1.3.6.1.2.1.10.251.2.1.29,VDSL2-LINE-MIB::xdsl2PMLineInitHist15MinShortGroup,,,,,,The group of PM counters for the previous 15-minute interval short initializations.
.1.3.6.1.2.1.10.251.2.1.30,VDSL2-LINE-MIB::xdsl2PMLineInitHist1DayGroup,,,,,,The group of PM counters for the previous 24-hour interval full initializations.
.1.3.6.1.2.1.10.251.2.1.31,VDSL2-LINE-MIB::xdsl2PMLineInitHist1DayShortGroup,,,,,,The group of PM counters for the previous 24-hour interval short initializations.
.1.3.6.1.2.1.10.251.2.1.32,VDSL2-LINE-MIB::xdsl2PMChCurrGroup,,,,,,The group of objects that report the channel-level counters for current PM intervals.
.1.3.6.1.2.1.10.251.2.1.33,VDSL2-LINE-MIB::xdsl2PMChHist15MinGroup,,,,,,The group of objects that report the channel-level counters for previous 15-minute PM intervals.
.1.3.6.1.2.1.10.251.2.1.34,VDSL2-LINE-MIB::xdsl2PMChHist1DGroup,,,,,,The group of objects that report the channel-level counters for previous 24-hour PM intervals.
.1.3.6.1.2.1.10.251.2.1.35,VDSL2-LINE-MIB::xdsl2ScalarSCGroup,,,,,,The group of objects that report the available memory resources for DELT processes.
.1.3.6.1.2.1.10.251.2.1.36,VDSL2-LINE-MIB::xdsl2ThreshNotificationGroup,,,,,,This group supports notifications of significant conditions associated with DSL lines.
.1.3.6.1.2.1.10.251.2.1.37,VDSL2-LINE-MIB::xdsl2StatusChangeNotificationGroup,,,,,,This group supports notifications of thresholds crossing associated with DSL lines.
.1.3.6.1.2.1.10.251.2.2,VDSL2-LINE-MIB::xdsl2Compliances,,,,,,
.1.3.6.1.2.1.10.251.2.2.1,VDSL2-LINE-MIB::xdsl2LineMibCompliance,,,,,,The compliance statement for SNMP entities which manage VDSL2/ADSL/ADSL2 and ADSL2+ interfaces.
.1.3.6.1.2.1.10.251.3,VDSL2-LINE-TC-MIB::vdsl2TCMIB,,,,,,This MIB Module provides Textual Conventions to be used by the VDSL2-LINE-MIB module for the purpose of managing VDSL2, ADSL, ADSL2, and ADSL2+ lines. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5650; see the RFC itself for full legal notices.
.1.3.6.1.2.1.10.273,TED-MIB::tedMIB,,,,,,This MIB module contains managed object definitions for TED in
.1.3.6.1.2.1.10.273.0,TED-MIB::tedNotifications,,,,,,
.1.3.6.1.2.1.10.273.0.1,TED-MIB::tedStatusChange,,,,,,This notification signifies that there has been change in the TE information of tedTable, tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable, and/or tedSrlgTable. For example, this should be generated when tedUnreservedBandwidth is changed to create or delete LSP using the registered TE link.
.1.3.6.1.2.1.10.273.0.2,TED-MIB::tedEntryCreated,,,,,,This notification signifies that there has been new registration in the TED table by receiving new TE link information. For example, this should be generated when a new index (tedLinkIndex) is registered in the TED table.
.1.3.6.1.2.1.10.273.0.3,TED-MIB::tedEntryDeleted,,,,,,This notification signifies that there has been deletion of an entry in the TED table. For example, this should be generated when one of the existing entries is deleted in the TED table.
.1.3.6.1.2.1.10.273.1,TED-MIB::tedObjects,,,,,,
.1.3.6.1.2.1.10.273.1.1,TED-MIB::tedTable,,not-accessible,,current,,This table indicates multiple TED information, which has been supported by RFC 3630 and RFC 5305.
.1.3.6.1.2.1.10.273.1.1.1,TED-MIB::tedEntry,,not-accessible,tedLocalRouterId:tedRemoteRouterId:tedLinkInformationSource:tedLinkIndex,current,,This entry contains TED information commonly utilized in both MPLS and GMPLS.
.1.3.6.1.2.1.10.273.1.1.1.1,TED-MIB::tedLinkInformationSource,INTEGER,not-accessible,,current,unknown(0):locallyConfigured(1):ospfv2(2):ospfv3(3):isis(4):other(5),This object indicates the source of the information about the TE link.
.1.3.6.1.2.1.10.273.1.1.1.2,TED-MIB::tedLocalRouterId,OCTET,not-accessible,,current,,This object represents the Router ID of the router originating the LSA. If OSPF is used to advertise LSA, this represents a Router ID. If IS-IS is used, this represents a System ID. Otherwise, this represents zero.
.1.3.6.1.2.1.10.273.1.1.1.3,TED-MIB::tedRemoteRouterId,OCTET,not-accessible,,current,,This object indicates the router at the remote end of the link from the originating router. If OSPF is used to advertise LSA, this represents a Link ID in the Link TLV. If IS-IS is used, this represents a neighbor System ID defined in RFC 5305. Otherwise, this represents zero.
.1.3.6.1.2.1.10.273.1.1.1.4,TED-MIB::tedLinkIndex,OCTET,not-accessible,,current,,This object indicates the link state identifier. If OSPF is used, this represents an ospfLsdbID. If IS-IS is used, this represents an isisLSPID. Otherwise, this represents a unique identifier within a node.
.1.3.6.1.2.1.10.273.1.1.1.5,TED-MIB::tedLinkInformationData,OBJECT,read-only,,current,,If tedLinkInformationSource has the value unknown(0), this object MUST contain a value of zeroDotZero. If tedLinkInformationSource has the value locallyConfigured(1), an implementation can use this object to supply the identifier of the corresponding row entry in the teLinkTable of TE-LINK- STD-MIB (RFC 4220), the identifier of the corresponding row in a local proprietary TE link MIB module, or the value of zeroDotZero. If tedLinkInformationSource has the value ospfv2(2) and ospfv3(3), an implementation can use this object to supply the identifier of the corresponding row entry in the ospfLocalLsdbTable (OSPFv2-MIB) and the ospfv3AreaLsdbTable (OSPFv3-MIB), or the value of zeroDotZero. If tedLinkInformationSource has the value isis(4), an implementation can use this object to supply the identifier of the corresponding row entry in the isisAreaAddr of ISIS-MIB (RFC 4444), or the value of zeroDotZero. If tedLinkInformationSource has the value other(5), an implementation can use this object to supply the identifier of the corresponding row entry in the local proprietary MIB module, or the value of zeroDotZero.
.1.3.6.1.2.1.10.273.1.1.1.6,TED-MIB::tedLinkState,INTEGER,read-only,,current,unknown(0):up(1):down(2),This object represents the actual operational state of this TE link. For instance, if a row is created in the TED table, but the actual TE link is not available for some reason (e.g., when there is not yet a physical link or the link has been manually disabled), then the object would be down(2) state. In contrast, if a row is added and the TE link is available, this would be operationally up(1).
.1.3.6.1.2.1.10.273.1.1.1.7,TED-MIB::tedAreaId,OCTET,read-only,,current,,This object indicates the area identifier of the IGP. If OSPF is used to advertise LSA, this represents an ospfArea. If IS-IS is used, this represents an area address. Otherwise, this represents zero.
.1.3.6.1.2.1.10.273.1.1.1.8,TED-MIB::tedLinkType,INTEGER,read-only,,current,pointToPoint(1):multiAccess(2),This indicates the type of the link, such as point to point or multi-access.
.1.3.6.1.2.1.10.273.1.1.1.9,TED-MIB::tedTeRouterIdAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the TE-Router ID address type. Only values unknown(0), ipv4(1), or ipv6(2) are supported.
.1.3.6.1.2.1.10.273.1.1.1.10,TED-MIB::tedTeRouterIdAddr,OCTET,read-only,,current,,This object indicates the TE-Router ID.
.1.3.6.1.2.1.10.273.1.1.1.11,TED-MIB::tedLinkIdAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the address type of the TE Link ID. Only values unknown(0), ipv4(1), or ipv6(2) are supported.
.1.3.6.1.2.1.10.273.1.1.1.12,TED-MIB::tedLinkIdAddr,OCTET,read-only,,current,,This indicates the Router ID of the neighbor in the case of point-to-point links. This also indicates the interface address of the designated router in the case of multi-access links.
.1.3.6.1.2.1.10.273.1.1.1.13,TED-MIB::tedMetric,Integer32,read-only,,current,,This indicates the traffic engineering metric value of the TE link.
.1.3.6.1.2.1.10.273.1.1.1.14,TED-MIB::tedMaxBandwidth,OCTET,read-only,,current,,This indicates the maximum bandwidth that can be used on this link in this direction.
.1.3.6.1.2.1.10.273.1.1.1.15,TED-MIB::tedMaxReservableBandwidth,OCTET,read-only,,current,,This indicates the maximum bandwidth that may be reserved on this link in this direction.
.1.3.6.1.2.1.10.273.1.1.1.16,TED-MIB::tedUnreservedBandwidthPri0,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 0.
.1.3.6.1.2.1.10.273.1.1.1.17,TED-MIB::tedUnreservedBandwidthPri1,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 1.
.1.3.6.1.2.1.10.273.1.1.1.18,TED-MIB::tedUnreservedBandwidthPri2,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 2.
.1.3.6.1.2.1.10.273.1.1.1.19,TED-MIB::tedUnreservedBandwidthPri3,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 3.
.1.3.6.1.2.1.10.273.1.1.1.20,TED-MIB::tedUnreservedBandwidthPri4,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 4.
.1.3.6.1.2.1.10.273.1.1.1.21,TED-MIB::tedUnreservedBandwidthPri5,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 5.
.1.3.6.1.2.1.10.273.1.1.1.22,TED-MIB::tedUnreservedBandwidthPri6,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 6.
.1.3.6.1.2.1.10.273.1.1.1.23,TED-MIB::tedUnreservedBandwidthPri7,OCTET,read-only,,current,,This indicates the amount of bandwidth not yet reserved at the priority 7.
.1.3.6.1.2.1.10.273.1.1.1.24,TED-MIB::tedAdministrativeGroup,Integer32,read-only,,current,,This indicates the Administrative Group to which the link belongs. Since the value is a bit mask, the link can belong to multiple groups. This is also called Resource Class/Color.
.1.3.6.1.2.1.10.273.1.1.1.25,TED-MIB::tedLocalId,Integer32,read-only,,current,,This indicates the Link Local Identifier of an unnumbered link.
.1.3.6.1.2.1.10.273.1.1.1.26,TED-MIB::tedRemoteId,Integer32,read-only,,current,,This indicates the Link Remote Identifier of an unnumbered link.
.1.3.6.1.2.1.10.273.1.1.1.27,TED-MIB::tedLinkProtectionType,BITS,read-only,,current,extraTraffic(0):unprotected(1):shared(2):dedicatedOneToOne(3):dedicatedOnePlusOne(4):enhanced(5),This object indicates the protection type of the TE link.
.1.3.6.1.2.1.10.273.1.2,TED-MIB::tedLocalIfAddrTable,,not-accessible,,current,,This table contains the IP address information of a local TE link.
.1.3.6.1.2.1.10.273.1.2.1,TED-MIB::tedLocalIfAddrEntry,,not-accessible,tedLinkIndex:tedLocalIfAddr,current,,This entry contains the IP address information of the local TE link.
.1.3.6.1.2.1.10.273.1.2.1.1,TED-MIB::tedLocalIfAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the address type of the local TE link. Only values unknown(0), ipv4(1), or ipv6(2) have to be supported.
.1.3.6.1.2.1.10.273.1.2.1.2,TED-MIB::tedLocalIfAddr,OCTET,not-accessible,,current,,This object indicates the address of the local TE link.
.1.3.6.1.2.1.10.273.1.3,TED-MIB::tedRemoteIfAddrTable,,not-accessible,,current,,This table contains the IP address information of a remote TE link.
.1.3.6.1.2.1.10.273.1.3.1,TED-MIB::tedRemoteIfAddrEntry,,not-accessible,tedLinkIndex:tedRemoteIfAddr,current,,This entry contains the IP address information of the remote TE link.
.1.3.6.1.2.1.10.273.1.3.1.1,TED-MIB::tedRemoteIfAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the address type of the remote TE link.
.1.3.6.1.2.1.10.273.1.3.1.2,TED-MIB::tedRemoteIfAddr,OCTET,not-accessible,,current,,This object indicates the address of the remote TE link.
.1.3.6.1.2.1.10.273.1.4,TED-MIB::tedSwCapTable,,not-accessible,,current,,This table contains the GMPLS TED switching capability information.
.1.3.6.1.2.1.10.273.1.4.1,TED-MIB::tedSwCapEntry,,not-accessible,tedLinkIndex:tedSwCapIndex,current,,This entry relates each TE link with its GMPLS TE switching capability information. If the MIB module deals with only OSPF- TE information, the value of each object related with GMPLS TE extensions should be null.
.1.3.6.1.2.1.10.273.1.4.1.1,TED-MIB::tedSwCapIndex,Unsigned32,not-accessible,,current,,This index is utilized to identify multiple switching functions on a local or remote TE link according to definitions of textual conventions of GMPLS, RFC 4801.
.1.3.6.1.2.1.10.273.1.4.1.2,TED-MIB::tedSwCapType,INTEGER,read-only,,current,unknown(0):psc1(1):psc2(2):psc3(3):psc4(4):evpl(30):pbb(40):l2sc(51):tdm(100):otntdm(110):dcsc(125):lsc(150):wsonlsc(151):fsc(200),This object indicates the GMPLS switching capability assigned to the TE link according to definitions of textual conventions of GMPLS, RFC 4801.
.1.3.6.1.2.1.10.273.1.4.1.3,TED-MIB::tedSwCapEncoding,INTEGER,read-only,,current,tunnelLspNotGmpls(0):tunnelLspPacket(1):tunnelLspEthernet(2):tunnelLspAnsiEtsiPdh(3):tunnelLspSdhSonet(5):tunnelLspDigitalWrapper(7):tunnelLspLambda(8):tunnelLspFiber(9):tunnelLspFiberChannel(11):tunnelDigitalPath(12):tunnelOpticalChannel(13):tunnelLine(14),This object indicates the GMPLS encoding type assigned to the TE link.
.1.3.6.1.2.1.10.273.1.4.1.4,TED-MIB::tedSwCapMaxLspBandwidthPri0,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 0 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.5,TED-MIB::tedSwCapMaxLspBandwidthPri1,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 1 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.6,TED-MIB::tedSwCapMaxLspBandwidthPri2,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 2 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.7,TED-MIB::tedSwCapMaxLspBandwidthPri3,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 3 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.8,TED-MIB::tedSwCapMaxLspBandwidthPri4,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 4 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.9,TED-MIB::tedSwCapMaxLspBandwidthPri5,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 5 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.10,TED-MIB::tedSwCapMaxLspBandwidthPri6,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 6 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.11,TED-MIB::tedSwCapMaxLspBandwidthPri7,OCTET,read-only,,current,,This object indicates the maximum bandwidth of the TE link at the priority 7 for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.1.4.1.12,TED-MIB::tedSwCapMinLspBandwidth,OCTET,read-only,,current,,This object indicates the minimum bandwidth of the TE link for GMPLS LSP creation if the switching capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4.
.1.3.6.1.2.1.10.273.1.4.1.13,TED-MIB::tedSwCapIfMtu,Integer32,read-only,,current,,This object indicates the MTU of the local or remote TE link.
.1.3.6.1.2.1.10.273.1.4.1.14,TED-MIB::tedSwCapIndication,INTEGER,read-only,,current,standard(0):arbitrary(1),This object indicates whether the interface supports Standard or Arbitrary SONET/SDH.
.1.3.6.1.2.1.10.273.1.5,TED-MIB::tedSrlgTable,,not-accessible,,current,,This table contains the SRLG information of the TE link.
.1.3.6.1.2.1.10.273.1.5.1,TED-MIB::tedSrlgEntry,,not-accessible,tedLinkIndex:tedSrlgIndex,current,,This entry relates each TE link with its SRLG information.
.1.3.6.1.2.1.10.273.1.5.1.1,TED-MIB::tedSrlgIndex,Unsigned32,not-accessible,,current,,This index is utilized to identify multiple SRLG values on a local or remote TE link. This object represents an arbitrary value, which is locally defined in a router.
.1.3.6.1.2.1.10.273.1.5.1.2,TED-MIB::tedSrlg,Integer32,read-only,,current,,This object indicates the SRLG value assigned to a local or remote TE link.
.1.3.6.1.2.1.10.273.1.6,TED-MIB::tedStatusChangeNotificationMaxRate,Unsigned32,read-write,,current,,A lot of notifications relating to the status change are expected to generate in a node, especially when a network failure occurs and might cause a performance degradation of the node itself. To avoid such a defect, this object provides the maximum number of notifications generated per minute. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period, or may queue them until an appropriate time. A value of 0 means no throttling is applied and events may be notified at the rate at which they occur.
.1.3.6.1.2.1.10.273.1.7,TED-MIB::tedCreatedDeletedNotificationMaxRate,Unsigned32,read-write,,current,,A lot of notifications relating to new registration in the TED table by receiving new TE link information or deletion of existing entries in the TED table are expected to generate in a node. This object provides the maximum number of notifications generated per minute.
.1.3.6.1.2.1.10.273.2,TED-MIB::tedConformance,,,,,,
.1.3.6.1.2.1.10.273.2.1,TED-MIB::tedCompliances,,,,,,
.1.3.6.1.2.1.10.273.2.1.1,TED-MIB::tedModuleFullCompliance,,,,,,Compliance statement for agents provides full support for the TED MIB.
.1.3.6.1.2.1.10.273.2.1.2,TED-MIB::tedModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations only provides read- only support for TED. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.10.273.2.2,TED-MIB::tedGroups,,,,,,
.1.3.6.1.2.1.10.273.2.2.1,TED-MIB::tedMainGroup,,,,,,Collection of objects for TED management
.1.3.6.1.2.1.10.273.2.2.2,TED-MIB::tedObjectsGroup,,,,,,The objects needed to implement notification.
.1.3.6.1.2.1.10.273.2.2.3,TED-MIB::tedNotificationGroup,,,,,,This group is mandatory for those implementations that can implement the notifications contained in this group.
.1.3.6.1.2.1.10.273.2.2.4,TED-MIB::tedUnnumberedLinkGroup,,,,,,The objects needed to implement the unnumbered links.
.1.3.6.1.2.1.10.273.2.2.5,TED-MIB::tedNumberedLinkGroup,,,,,,The objects needed to implement the numbered links.
.1.3.6.1.2.1.10.273.2.2.6,TED-MIB::tedSwCapGroup,,,,,,The objects needed to implement the TE links with GMPLS TE switching capability information.
.1.3.6.1.2.1.10.273.2.2.7,TED-MIB::tedSwCapMinLspBandwidthGroup,,,,,,The objects needed to implement the minimum bandwidth of the TE link for GMPLS LSP creation.
.1.3.6.1.2.1.10.273.2.2.8,TED-MIB::tedSwCapIfMtuGroup,,,,,,The objects needed to implement the MTU information of the local or remote TE link.
.1.3.6.1.2.1.10.273.2.2.9,TED-MIB::tedSwCapIndicationGroup,,,,,,The objects needed to implement the indication of whether the interface supports Standard or Arbitrary SONET/SDH.
.1.3.6.1.2.1.10.273.2.2.10,TED-MIB::tedSrlgGroup,,,,,,The objects needed to implement multiple SRLG values with GMPLS TE information.
.1.3.6.1.2.1.10.274,VPLS-GENERIC-MIB::vplsGenericMIB,,,,,,Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The initial version of this MIB module was published in RFC 7257; for full legal notices see the RFC itself. This MIB module contains generic managed object definitions for Virtual Private LAN Service as defined in RFC 4761 and RFC 4762. This MIB module enables the use of any underlying pseudowire network.
.1.3.6.1.2.1.10.274.0,VPLS-GENERIC-MIB::vplsNotifications,,,,,,
.1.3.6.1.2.1.10.274.0.1,VPLS-GENERIC-MIB::vplsStatusChanged,,,,,,The vplsStatusChanged notification is generated when there is a change in the administrative or operating status of a VPLS service. The object instances included in the notification are the ones associated with the VPLS service whose status has changed.
.1.3.6.1.2.1.10.274.0.2,VPLS-GENERIC-MIB::vplsFwdFullAlarmRaised,,,,,,The vplsFwdFullAlarmRaised notification is generated when the utilization of the Forwarding database is above the value specified by vplsConfigFwdFullHighWatermark. The object instances included in the notification are the ones associated with the VPLS service that has exceeded the threshold.
.1.3.6.1.2.1.10.274.0.3,VPLS-GENERIC-MIB::vplsFwdFullAlarmCleared,,,,,,The vplsFwdFullAlarmCleared notification is generated when the utilization of the Forwarding database is below the value specified by vplsConfigFwdFullLowWatermark. The object instances included in the notification are the ones associated with the VPLS service that has fallen below the threshold.
.1.3.6.1.2.1.10.274.1,VPLS-GENERIC-MIB::vplsObjects,,,,,,
.1.3.6.1.2.1.10.274.1.1,VPLS-GENERIC-MIB::vplsConfigIndexNext,Unsigned32,read-only,,current,,This object contains an appropriate value to be used for vplsConfigIndex when creating entries in the vplsConfigTable. The value 0 indicates that no unassigned entries are available. To obtain the value of vplsConfigIndex for a new entry in the vplsConfigTable, the manager issues a management protocol retrieval operation to obtain the current value of vplsConfigIndex. After each retrieval operation, the agent should modify the value to reflect the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.10.274.1.2,VPLS-GENERIC-MIB::vplsConfigTable,,not-accessible,,current,,This table specifies information for configuring and monitoring Virtual Private LAN Service (VPLS). 
.1.3.6.1.2.1.10.274.1.2.1,VPLS-GENERIC-MIB::vplsConfigEntry,,not-accessible,vplsConfigIndex,current,,A row in this table represents a Virtual Private LAN Service (VPLS) in a packet network. It is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. A row is created via SNMP or by the agent if a VPLS service is created by a non-SNMP application or due to the Auto-Discovery process. All of the read-create objects values except vplsConfigSignalingType can be changed when vplsConfigRowStatus is in the active(1) state. Changes for vplsConfigSignalingType are only allowed when the vplsConfigRowStatus is in notInService(2) or notReady(3) states. 
.1.3.6.1.2.1.10.274.1.2.1.1,VPLS-GENERIC-MIB::vplsConfigIndex,Unsigned32,not-accessible,,current,,Unique index for the conceptual row identifying a VPLS service.
.1.3.6.1.2.1.10.274.1.2.1.2,VPLS-GENERIC-MIB::vplsConfigName,OCTET,read-create,,current,,A textual name of the VPLS. If there is no local name, or this object is otherwise not applicable, then this object MUST contain a zero-length octet string.
.1.3.6.1.2.1.10.274.1.2.1.3,VPLS-GENERIC-MIB::vplsConfigDescr,OCTET,read-create,,current,,A textual string containing information about the VPLS service. If there is no information for this VPLS service, then this object MUST contain a zero-length octet string.
.1.3.6.1.2.1.10.274.1.2.1.4,VPLS-GENERIC-MIB::vplsConfigAdminStatus,INTEGER,read-create,,current,up(1):down(2):testing(3),The desired administrative state of the VPLS service. If the administrative status of the VPLS service is changed to enabled, then this service is able to utilize pseudowires to perform the tasks of a VPLS service. The testing(3) state indicates that no operational packets can be passed.
.1.3.6.1.2.1.10.274.1.2.1.6,VPLS-GENERIC-MIB::vplsConfigMacLearning,INTEGER,read-create,,current,true(1):false(2),This object specifies if MAC Learning is enabled in this service. If this object is true then MAC Learning is enabled. If false, then MAC Learning is disabled.
.1.3.6.1.2.1.10.274.1.2.1.7,VPLS-GENERIC-MIB::vplsConfigDiscardUnknownDest,INTEGER,read-create,,current,true(1):false(2),If the value of this object is 'true', then frames received with an unknown destination MAC are discarded in this VPLS. If 'false', then the packets are processed.
.1.3.6.1.2.1.10.274.1.2.1.8,VPLS-GENERIC-MIB::vplsConfigMacAging,INTEGER,read-create,,current,true(1):false(2),If the value of this object is 'true', then the MAC aging process is enabled in this VPLS. If 'false', then the MAC aging process is disabled.
.1.3.6.1.2.1.10.274.1.2.1.10,VPLS-GENERIC-MIB::vplsConfigFwdFullHighWatermark,Unsigned32,read-create,,current,,This object specifies the utilization of the forwarding database for this VPLS instance at which the vplsFwdFullAlarmRaised notification will be sent. The value of this object must be higher than vplsConfigFwdFullLowWatermark.
.1.3.6.1.2.1.10.274.1.2.1.11,VPLS-GENERIC-MIB::vplsConfigFwdFullLowWatermark,Unsigned32,read-create,,current,,This object specifies the utilization of the forwarding database for this VPLS instance at which the vplsFwdFullAlarmCleared notification will be sent. The value of this object must be less than vplsConfigFwdFullHighWatermark.
.1.3.6.1.2.1.10.274.1.2.1.12,VPLS-GENERIC-MIB::vplsConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. All other objects in this row must be set to valid values before this object can be set to active(1). None of the read-create objects in the conceptual rows may be changed when this object is in the active(1) state. If this object is set to destroy(6) or deleted by the agent, all associated entries in the vplsPwBindTable, vplsBgpRteTargetTable, and vplsBgpVETable shall be deleted.
.1.3.6.1.2.1.10.274.1.2.1.13,VPLS-GENERIC-MIB::vplsConfigMtu,Unsigned32,read-create,,current,,The value of this object specifies the MTU of this VPLS instance. This can be used to limit the MTU to a value lower than the MTU supported by the associated pseudowires.
.1.3.6.1.2.1.10.274.1.2.1.14,VPLS-GENERIC-MIB::vplsConfigVpnId,OCTET,read-create,,current,,This objects indicates the IEEE 802-1990 VPN ID of the associated VPLS service.
.1.3.6.1.2.1.10.274.1.2.1.15,VPLS-GENERIC-MIB::vplsConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.10.274.1.2.1.16,VPLS-GENERIC-MIB::vplsConfigSignalingType,INTEGER,read-create,,current,ldp(1):bgp(2):none(3),Desired signaling type of the VPLS service. If the value of this object is ldp(1), then a corresponding entry in vplsLdpConfigTable is required. If the value of this object is bgp(2), then a corresponding entry in vplsBgpConfigTable is required. If the value of this object is none(3), then it indicates a static configuration of PW labels.
.1.3.6.1.2.1.10.274.1.3,VPLS-GENERIC-MIB::vplsStatusTable,,not-accessible,,current,,This table provides information for monitoring Virtual Private LAN Service (VPLS). 
.1.3.6.1.2.1.10.274.1.3.1,VPLS-GENERIC-MIB::vplsStatusEntry,,not-accessible,,current,,A row in this table represents a Virtual Private LAN Service (VPLS) in a packet network. It is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. A row in this table is automatically created by the agent when a VPLS service is first set to active. 
.1.3.6.1.2.1.10.274.1.3.1.1,VPLS-GENERIC-MIB::vplsStatusOperStatus,INTEGER,read-only,,current,other(0):up(1):down(2),The current operational state of this VPLS service.
.1.3.6.1.2.1.10.274.1.3.1.2,VPLS-GENERIC-MIB::vplsStatusPeerCount,Counter32,read-only,,current,,This objects specifies the number of peers (pseudowires) present in this VPLS instance.
.1.3.6.1.2.1.10.274.1.4,VPLS-GENERIC-MIB::vplsPwBindTable,,not-accessible,,current,,This table provides an association between a VPLS service and the corresponding pseudowires. A service can have more than one pseudowire association. Pseudowires are defined in the pwTable
.1.3.6.1.2.1.10.274.1.4.1,VPLS-GENERIC-MIB::vplsPwBindEntry,,not-accessible,vplsConfigIndex:pwIndex,current,,Each row represents an association between a VPLS instance and a pseudowire defined in the pwTable. Each index is unique in describing an entry in this table. However, both indexes are required to define the one to many association of service to pseudowire. Entries in this table may be created or deleted through SNMP, as side effects of console or other non-SNMP management commands, or upon learning via autodiscovery. It is optional for the agent to allow entries to be created that point to nonexistent entries in vplsConfigTable.
.1.3.6.1.2.1.10.274.1.4.1.1,VPLS-GENERIC-MIB::vplsPwBindConfigType,INTEGER,read-create,,current,manual(1):autodiscovery(2),The value of this object indicates whether the pseudowire Binding was created via SNMP/Console or via Auto-Discovery. The value of this object must be specified when the row is created and cannot be changed while the row status is active(1)
.1.3.6.1.2.1.10.274.1.4.1.2,VPLS-GENERIC-MIB::vplsPwBindType,INTEGER,read-create,,current,mesh(1):spoke(2),The value of this object indicates whether the pseudowire Binding is of type mesh or spoke. The value of this object must be specified when the row is created and cannot be changed while the row status is active(1)
.1.3.6.1.2.1.10.274.1.4.1.3,VPLS-GENERIC-MIB::vplsPwBindRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. All other objects in this row must be set to valid values before this object can be set to active(1). None of the read-create objects in the conceptual rows may be changed when this object is in the active(1) state. If autodiscovered entries are deleted they would likely re-appear in the next autodiscovery interval.
.1.3.6.1.2.1.10.274.1.4.1.4,VPLS-GENERIC-MIB::vplsPwBindStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.10.274.1.5,VPLS-GENERIC-MIB::vplsBgpADConfigTable,,not-accessible,,current,,This table specifies information for configuring BGP Auto-Discovery parameters for a given VPLS service. 
.1.3.6.1.2.1.10.274.1.5.1,VPLS-GENERIC-MIB::vplsBgpADConfigEntry,,not-accessible,vplsConfigIndex,current,,A row in this table indicates that BGP based Auto- Discovery is in use for this instance of VPLS. A row in this table is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. Entries in this table may be created or deleted through SNMP, as side effects of console or other non-SNMP management commands, or upon learning via autodiscovery. All of the read-create objects can be changed when vplsBGPADConfigRowStatus is in active(1) state.
.1.3.6.1.2.1.10.274.1.5.1.1,VPLS-GENERIC-MIB::vplsBgpADConfigRouteDistinguisher,OCTET,read-create,,current,,The route distinguisher for this VPLS. See RFC 4364 for a complete definition of a route distinguisher. For more details on use of a route distinguisher for a VPLS service, see RFC 4761. When not configured, the value is derived from the lower 6 bytes of vplsBgpADConfigVplsId. 
.1.3.6.1.2.1.10.274.1.5.1.2,VPLS-GENERIC-MIB::vplsBgpADConfigPrefix,Unsigned32,read-create,,current,,In case of auto-discovery, the default prefix advertised is the IP address of the loopback. In case the user wants to override the loopback address, vplsBgpADConfigPrefix should be set. When this value is non-zero, this value is used along with vplsBgpADConfigRouteDistinguisher in the Network Layer Reachability Information (NLRI), see RFC 6074. 
.1.3.6.1.2.1.10.274.1.5.1.3,VPLS-GENERIC-MIB::vplsBgpADConfigVplsId,OCTET,read-create,,current,,VplsId is a unique identifier for all Virtual Switch Instances (VSIs) belonging to the same VPLS. It is advertised as an extended community. 
.1.3.6.1.2.1.10.274.1.5.1.4,VPLS-GENERIC-MIB::vplsBgpADConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. All other objects in this row must be set to valid values before this object can be set to active(1). None of the read-create objects in the conceptual rows may be changed when this object is in the active(1) state.
.1.3.6.1.2.1.10.274.1.5.1.5,VPLS-GENERIC-MIB::vplsBgpADConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.10.274.1.6,VPLS-GENERIC-MIB::vplsBgpRteTargetTable,,not-accessible,,current,,This table specifies the list of Route Targets imported or exported by BGP during auto-discovery of VPLS. 
.1.3.6.1.2.1.10.274.1.6.1,VPLS-GENERIC-MIB::vplsBgpRteTargetEntry,,not-accessible,vplsConfigIndex:vplsBgpRteTargetIndex,current,,An entry in this table specifies the value of the Route Target being used by BGP. Depending on the value of vplsBgpRteTargetType, a Route Target might be exported, imported, or both. Every VPLS that uses auto-discovery for finding peer nodes can import and export multiple Route Targets. This representation allows support for hierarchical VPLS. Entries in this table may be created or deleted through SNMP, as side effects of console or other non-SNMP management commands, or upon learning via autodiscovery. It is optional for the agent to allow entries to be created that point to nonexistent entries in vplsConfigTable.
.1.3.6.1.2.1.10.274.1.6.1.1,VPLS-GENERIC-MIB::vplsBgpRteTargetIndex,Unsigned32,not-accessible,,current,,This index, along with vplsConfigIndex, identifies one entry in the vplsBgpRteTargetTable. By keeping vplsConfigIndex constant and using a new value of vplsBgpRteTargetIndex, users can configure multiple Route Targets for the same VPLS. 
.1.3.6.1.2.1.10.274.1.6.1.2,VPLS-GENERIC-MIB::vplsBgpRteTargetRTType,INTEGER,read-create,,current,import(1):export(2):both(3),Used to define the type of a Route Target usage. Route Targets can be specified to be imported, exported, or both. For a complete definition of a Route Target, see RFC 4364.
.1.3.6.1.2.1.10.274.1.6.1.3,VPLS-GENERIC-MIB::vplsBgpRteTargetRT,OCTET,read-create,,current,,The Route Target associated with the VPLS service. For more details on use of Route Targets for a VPLS service, see RFC 4761. 
.1.3.6.1.2.1.10.274.1.6.1.4,VPLS-GENERIC-MIB::vplsBgpRteTargetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. All other objects in this row must be set to valid values before this object can be set to active(1). When a row in this table is in active(1) state, no objects in that row can be modified. If autodiscovered entries are deleted they would likely re-appear in the next autodiscovery interval.
.1.3.6.1.2.1.10.274.1.6.1.5,VPLS-GENERIC-MIB::vplsBgpRteTargetStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.10.274.1.7,VPLS-GENERIC-MIB::vplsStatusNotifEnable,INTEGER,read-write,,current,true(1):false(2),If this object is set to true(1), then it enables the emission of a vplsStatusChanged notification; otherwise, this notification is not emitted.
.1.3.6.1.2.1.10.274.1.8,VPLS-GENERIC-MIB::vplsNotificationMaxRate,Unsigned32,read-write,,current,,This object indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period, or it may queue them until an appropriate time. A value of 0 means no throttling is applied and events may be notified at the rate at which they occur.
.1.3.6.1.2.1.10.274.2,VPLS-GENERIC-MIB::vplsConformance,,,,,,
.1.3.6.1.2.1.10.274.2.1,VPLS-GENERIC-MIB::vplsCompliances,,,,,,
.1.3.6.1.2.1.10.274.2.1.1,VPLS-GENERIC-MIB::vplsModuleFullCompliance,,,,,,Compliance requirement for implementations that provide full support for VPLS-GENERIC-MIB. Such devices can then be monitored and configured using this MIB module.
.1.3.6.1.2.1.10.274.2.1.2,VPLS-GENERIC-MIB::vplsModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for VPLS-GENERIC-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.
.1.3.6.1.2.1.10.274.2.2,VPLS-GENERIC-MIB::vplsGroups,,,,,,
.1.3.6.1.2.1.10.274.2.2.1,VPLS-GENERIC-MIB::vplsGroup,,,,,,The group of objects supporting management of L2VPN VPLS services
.1.3.6.1.2.1.10.274.2.2.2,VPLS-GENERIC-MIB::vplsPwBindGroup,,,,,,The group of objects supporting management of pseudowire (PW) Binding to VPLS.
.1.3.6.1.2.1.10.274.2.2.3,VPLS-GENERIC-MIB::vplsNotificationGroup,,,,,,The group of notifications supporting the Notifications generated for VPLS services.
.1.3.6.1.2.1.10.275,VPLS-LDP-MIB::vplsLdpMIB,,,,,,Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The initial version of this MIB module was published in RFC 7257; for full legal notices see the RFC itself. This MIB module contains managed object definitions for LDP-signaled Virtual Private LAN Services as in RFC 4762. This MIB module enables the use of any underlying pseudowire network.
.1.3.6.1.2.1.10.275.0,VPLS-LDP-MIB::vplsLdpNotifications,,,,,,
.1.3.6.1.2.1.10.275.0.1,VPLS-LDP-MIB::vplsLdpPwBindMacTableFull,,,,,,The vplsLdpPwBindMacTableFull notification is generated when the number of learned MAC addresses increases to the value specified in vplsLdpPwBindMacAddressLimit.
.1.3.6.1.2.1.10.275.1,VPLS-LDP-MIB::vplsLdpObjects,,,,,,
.1.3.6.1.2.1.10.275.1.1,VPLS-LDP-MIB::vplsLdpConfigTable,,not-accessible,,current,,This table specifies information for configuring and monitoring LDP-specific parameters for Virtual Private LAN Service (VPLS).
.1.3.6.1.2.1.10.275.1.1.1,VPLS-LDP-MIB::vplsLdpConfigEntry,,not-accessible,vplsConfigIndex,current,,A row in this table represents LDP-specific information for Virtual Private LAN Service (VPLS) in a packet network. It is indexed by vplsConfigIndex, which uniquely identifies a single VPLS. A row is automatically created when a VPLS service is configured using LDP signaling. All of the writable objects values can be changed when vplsConfigRowStatus is in the active(1) state. 
.1.3.6.1.2.1.10.275.1.1.1.1,VPLS-LDP-MIB::vplsLdpConfigMacAddrWithdraw,INTEGER,read-write,,current,true(1):false(2),This object specifies if MAC address withdrawal is enabled in this service. If this object is 'true', then MAC address withdrawal is enabled. If 'false', then MAC address withdrawal is disabled.
.1.3.6.1.2.1.10.275.1.2,VPLS-LDP-MIB::vplsLdpPwBindTable,,not-accessible,,current,,This table provides LDP-specific information for an association between a VPLS service and the corresponding pseudowires. A service can have more than one pseudowire association. Pseudowires are defined in the pwTable.
.1.3.6.1.2.1.10.275.1.2.1,VPLS-LDP-MIB::vplsLdpPwBindEntry,,not-accessible,vplsConfigIndex:pwIndex,current,,Each row represents an association between a VPLS instance and one or more pseudowires defined in the pwTable. Each index is unique in describing an entry in this table. However, both indexes are required to define the one-to-many association of service to pseudowire. An entry in this table in instantiated only when LDP signaling is used to configure VPLS service. Each entry in this table provides LDP-specific information for the VPLS represented by vplsConfigIndex.
.1.3.6.1.2.1.10.275.1.2.1.1,VPLS-LDP-MIB::vplsLdpPwBindMacAddressLimit,Unsigned32,read-write,,current,,The value of this object specifies the maximum number of learned and static entries allowed in the Forwarding database for this PW Binding. The value 0 means there is no limit for this PW Binding.
.1.3.6.1.2.1.10.275.2,VPLS-LDP-MIB::vplsLdpConformance,,,,,,
.1.3.6.1.2.1.10.275.2.1,VPLS-LDP-MIB::vplsLdpCompliances,,,,,,
.1.3.6.1.2.1.10.275.2.1.1,VPLS-LDP-MIB::vplsLdpModuleFullCompliance,,,,,,Compliance requirement for implementations that provide full support for VPLS-LDP-MIB. Such devices can then be monitored and configured using this MIB module.
.1.3.6.1.2.1.10.275.2.1.2,VPLS-LDP-MIB::vplsLdpModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for VPLS-LDP-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.
.1.3.6.1.2.1.10.275.2.2,VPLS-LDP-MIB::vplsLdpGroups,,,,,,
.1.3.6.1.2.1.10.275.2.2.1,VPLS-LDP-MIB::vplsLdpGroup,,,,,,The group of objects supporting management of L2VPN VPLS services using LDP.
.1.3.6.1.2.1.10.275.2.2.2,VPLS-LDP-MIB::vplsLdpNotificationGroup,,,,,,The group of notifications supporting the Notifications generated for VPLS LDP Service.
.1.3.6.1.2.1.10.276,VPLS-BGP-MIB::vplsBgpMIB,,,,,,Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The initial version of this MIB module was published in RFC 7257; for full legal notices see the RFC itself. This MIB module contains managed object definitions for BGP signaled Virtual Private LAN Service as in RFC 4761. This MIB module enables the use of any underlying pseudowire network.
.1.3.6.1.2.1.10.276.1,VPLS-BGP-MIB::vplsBgpObjects,,,,,,
.1.3.6.1.2.1.10.276.1.1,VPLS-BGP-MIB::vplsBgpConfigTable,,not-accessible,,current,,This table specifies information for configuring and monitoring BGP-specific parameters for Virtual Private LAN Service (VPLS).
.1.3.6.1.2.1.10.276.1.1.1,VPLS-BGP-MIB::vplsBgpConfigEntry,,not-accessible,vplsConfigIndex,current,,A row in this table represents BGP-specific information for Virtual Private LAN Service (VPLS) in a packet network. It is indexed by vplsConfigIndex, which uniquely identifies a single instance of a VPLS service. A row is automatically created when a VPLS service is created that is configured to use BGP signaling. All of the writable object values can be changed when vplsConfigRowStatus is in the active(1) state. 
.1.3.6.1.2.1.10.276.1.1.1.1,VPLS-BGP-MIB::vplsBgpConfigVERangeSize,Unsigned32,read-write,,current,,Specifies the size of the range of VPLS Edge Identifier (VE ID) in this VPLS service. This number controls the size of the label block advertised for this VE by the PE. A value of 0 indicates that the range is not configured and the PE derives the range value from received advertisements from other PEs. The VE ID takes 2 octets in VPLS BGP NLRI according to RFC 4761. Hence we have limited the range of this object to 65535.
.1.3.6.1.2.1.10.276.1.2,VPLS-BGP-MIB::vplsBgpVETable,,not-accessible,,current,,This table associates VPLS Edge devices to a VPLS service
.1.3.6.1.2.1.10.276.1.2.1,VPLS-BGP-MIB::vplsBgpVEEntry,,not-accessible,vplsConfigIndex:vplsBgpVEId,current,,An entry in this table is created for each VE ID configured on a PE for a particular VPLS service instance. Entries in this table may be created or deleted through SNMP, as side effects of console or other non-SNMP management commands, or upon learning via autodiscovery. It is optional for the agent to allow entries to be created that point to nonexistent entries in vplsConfigTable.
.1.3.6.1.2.1.10.276.1.2.1.1,VPLS-BGP-MIB::vplsBgpVEId,Unsigned32,not-accessible,,current,,A secondary index identifying a VE within an instance of a VPLS service. The VE ID takes 2 octets in VPLS BGP NLRI according to RFC 4761. Hence, we have limited the range of this object to 65535.
.1.3.6.1.2.1.10.276.1.2.1.2,VPLS-BGP-MIB::vplsBgpVEName,OCTET,read-create,,current,,Descriptive name for the site or user-facing PE (U-PE) associated with this VE ID.
.1.3.6.1.2.1.10.276.1.2.1.3,VPLS-BGP-MIB::vplsBgpVEPreference,Unsigned32,read-create,,current,,Specifies the preference of the VE ID on this Provider Edge (PE) if the site is multihomed and VE ID is reused.
.1.3.6.1.2.1.10.276.1.2.1.5,VPLS-BGP-MIB::vplsBgpVERowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. All other objects in this row must be set to valid values before this object can be set to active(1). When a row in this table is in active(1) state, no objects in that row can be modified except vplsBgpSiteRowStatus.
.1.3.6.1.2.1.10.276.1.2.1.6,VPLS-BGP-MIB::vplsBgpVEStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.10.276.1.3,VPLS-BGP-MIB::vplsBgpPwBindTable,,not-accessible,,current,,This table provides BGP-specific information for an association between a VPLS service and the corresponding pseudowires. A service can have more than one pseudowire association. Pseudowires are defined in the pwTable.
.1.3.6.1.2.1.10.276.1.3.1,VPLS-BGP-MIB::vplsBgpPwBindEntry,,not-accessible,vplsConfigIndex:pwIndex,current,,Each row represents an association between a VPLS instance and one or more pseudowires defined in the pwTable. Each index is unique in describing an entry in this table. However, both indexes are required to define the one to many association of service to pseudowire. An entry in this table in instantiated only when BGP signaling is used to configure VPLS service. Each entry in this table provides BGP-specific information for the VPLS represented by vplsConfigIndex.
.1.3.6.1.2.1.10.276.1.3.1.1,VPLS-BGP-MIB::vplsBgpPwBindLocalVEId,Unsigned32,read-only,,current,,Identifies the local VE with which this pseudowire is associated. The VE ID takes 2 octets in VPLS BGP NLRI according to RFC 4761. Hence, we have limited the range of this object to 65535.
.1.3.6.1.2.1.10.276.1.3.1.2,VPLS-BGP-MIB::vplsBgpPwBindRemoteVEId,Unsigned32,read-only,,current,,Identifies the remote VE with which this pseudowire is associated. The VE ID takes 2 octets in VPLS BGP NLRI according to RFC 4761. Hence, we have limited the range of this object to 65535.
.1.3.6.1.2.1.10.276.2,VPLS-BGP-MIB::vplsBgpConformance,,,,,,
.1.3.6.1.2.1.10.276.2.1,VPLS-BGP-MIB::vplsBgpCompliances,,,,,,
.1.3.6.1.2.1.10.276.2.1.1,VPLS-BGP-MIB::vplsBgpModuleFullCompliance,,,,,,Compliance requirement for implementations that provide full support for VPLS-BGP-MIB. Such devices can then be monitored and configured using this MIB module.
.1.3.6.1.2.1.10.276.2.1.2,VPLS-BGP-MIB::vplsBgpModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for VPLS-BGP-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.
.1.3.6.1.2.1.10.276.2.2,VPLS-BGP-MIB::vplsBgpGroups,,,,,,
.1.3.6.1.2.1.10.276.2.2.1,VPLS-BGP-MIB::vplsBgpConfigGroup,,,,,,The group of objects supporting configuration of L2VPN VPLS services using BGP.
.1.3.6.1.2.1.10.276.2.2.2,VPLS-BGP-MIB::vplsBgpVEGroup,,,,,,The group of objects supporting management of VPLS Edge devices for L2VPN VPLS services using BGP.
.1.3.6.1.2.1.10.276.2.2.3,VPLS-BGP-MIB::vplsBgpPwBindGroup,,,,,,The group of objects supporting management of pseudowires for L2VPN VPLS services using BGP.
.1.3.6.1.2.1.11,SNMPv2-MIB::snmp,,,,,,
.1.3.6.1.2.1.11.1,SNMPv2-MIB::snmpInPkts,Counter32,read-only,,current,,The total number of messages delivered to the SNMP entity from the transport service.
.1.3.6.1.2.1.11.2,SNMPv2-MIB::snmpOutPkts,Counter32,read-only,,obsolete,,The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.
.1.3.6.1.2.1.11.3,SNMPv2-MIB::snmpInBadVersions,Counter32,read-only,,current,,The total number of SNMP messages which were delivered to the SNMP entity and were for an unsupported SNMP version.
.1.3.6.1.2.1.11.4,SNMPv2-MIB::snmpInBadCommunityNames,Counter32,read-only,,current,,The total number of community-based SNMP messages (for example, SNMPv1) delivered to the SNMP entity which used an SNMP community name not known to said entity. Also, implementations which authenticate community-based SNMP messages using check(s) in addition to matching the community name (for example, by also checking whether the message originated from a transport address allowed to use a specified community name) MAY include in this value the number of messages which failed the additional check(s). It is strongly RECOMMENDED that the documentation for any security model which is used to authenticate community-based SNMP messages specify the precise conditions that contribute to this value.
.1.3.6.1.2.1.11.5,SNMPv2-MIB::snmpInBadCommunityUses,Counter32,read-only,,current,,The total number of community-based SNMP messages (for example, SNMPv1) delivered to the SNMP entity which represented an SNMP operation that was not allowed for the SNMP community named in the message. The precise conditions under which this counter is incremented (if at all) depend on how the SNMP entity implements its access control mechanism and how its applications interact with that access control mechanism. It is strongly RECOMMENDED that the documentation for any access control mechanism which is used to control access to and visibility of MIB instrumentation specify the precise conditions that contribute to this value.
.1.3.6.1.2.1.11.6,SNMPv2-MIB::snmpInASNParseErrs,Counter32,read-only,,current,,The total number of ASN.1 or BER errors encountered by the SNMP entity when decoding received SNMP messages.
.1.3.6.1.2.1.11.8,SNMPv2-MIB::snmpInTooBigs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `tooBig'.
.1.3.6.1.2.1.11.9,SNMPv2-MIB::snmpInNoSuchNames,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `noSuchName'.
.1.3.6.1.2.1.11.10,SNMPv2-MIB::snmpInBadValues,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `badValue'.
.1.3.6.1.2.1.11.11,SNMPv2-MIB::snmpInReadOnlys,Counter32,read-only,,obsolete,,The total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP.
.1.3.6.1.2.1.11.12,SNMPv2-MIB::snmpInGenErrs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field was `genErr'.
.1.3.6.1.2.1.11.13,SNMPv2-MIB::snmpInTotalReqVars,Counter32,read-only,,obsolete,,The total number of MIB objects which have been retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs.
.1.3.6.1.2.1.11.14,SNMPv2-MIB::snmpInTotalSetVars,Counter32,read-only,,obsolete,,The total number of MIB objects which have been altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs.
.1.3.6.1.2.1.11.15,SNMPv2-MIB::snmpInGetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.16,SNMPv2-MIB::snmpInGetNexts,Counter32,read-only,,obsolete,,The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.17,SNMPv2-MIB::snmpInSetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.18,SNMPv2-MIB::snmpInGetResponses,Counter32,read-only,,obsolete,,The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.19,SNMPv2-MIB::snmpInTraps,Counter32,read-only,,obsolete,,The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.
.1.3.6.1.2.1.11.20,SNMPv2-MIB::snmpOutTooBigs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field was `tooBig.'
.1.3.6.1.2.1.11.21,SNMPv2-MIB::snmpOutNoSuchNames,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status was `noSuchName'.
.1.3.6.1.2.1.11.22,SNMPv2-MIB::snmpOutBadValues,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field was `badValue'.
.1.3.6.1.2.1.11.24,SNMPv2-MIB::snmpOutGenErrs,Counter32,read-only,,obsolete,,The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field was `genErr'.
.1.3.6.1.2.1.11.25,SNMPv2-MIB::snmpOutGetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.26,SNMPv2-MIB::snmpOutGetNexts,Counter32,read-only,,obsolete,,The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.27,SNMPv2-MIB::snmpOutSetRequests,Counter32,read-only,,obsolete,,The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.28,SNMPv2-MIB::snmpOutGetResponses,Counter32,read-only,,obsolete,,The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.29,SNMPv2-MIB::snmpOutTraps,Counter32,read-only,,obsolete,,The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.
.1.3.6.1.2.1.11.30,SNMPv2-MIB::snmpEnableAuthenTraps,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the SNMP entity is permitted to generate authenticationFailure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authenticationFailure traps may be disabled. Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant across re-initializations of the network management system.
.1.3.6.1.2.1.11.31,SNMPv2-MIB::snmpSilentDrops,Counter32,read-only,,current,,The total number of Confirmed Class PDUs (such as GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs) delivered to the SNMP entity which were silently dropped because the size of a reply containing an alternate Response Class PDU (such as a Response-PDU) with an empty variable-bindings field was greater than either a local constraint or the maximum message size associated with the originator of the request.
.1.3.6.1.2.1.11.32,SNMPv2-MIB::snmpProxyDrops,Counter32,read-only,,current,,The total number of Confirmed Class PDUs (such as GetRequest-PDUs, GetNextRequest-PDUs, GetBulkRequest-PDUs, SetRequest-PDUs, and InformRequest-PDUs) delivered to the SNMP entity which were silently dropped because the transmission of the (possibly translated) message to a proxy target failed in a manner (other than a time-out) such that no Response Class PDU (such as a Response-PDU) could be returned.
.1.3.6.1.2.1.13,APPLETALK-MIB::appletalk,,,,,,
.1.3.6.1.2.1.13.1,APPLETALK-MIB::llap,,,,,,
.1.3.6.1.2.1.13.1.1,APPLETALK-MIB::llapTable,,not-accessible,,mandatory,,The list of LLAP entries.
.1.3.6.1.2.1.13.1.1.1,APPLETALK-MIB::llapEntry,,not-accessible,llapIfIndex,mandatory,,An LLAP entry containing objects for the LocalTalk Link Access Protocol for a particular LocalTalk interface. As an example, an instance of the llapOutPkts object might be named llapOutPks.1
.1.3.6.1.2.1.13.1.1.1.1,APPLETALK-MIB::llapIfIndex,INTEGER,read-only,,mandatory,,The LLAP interface to which this entry pertains. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.13.1.1.1.2,APPLETALK-MIB::llapInPkts,Counter32,read-only,,deprecated,,The total number of good data packets received on this LocalTalk interface.
.1.3.6.1.2.1.13.1.1.1.3,APPLETALK-MIB::llapOutPkts,Counter32,read-only,,deprecated,,The total number of data packets transmitted on this LocalTalk interface.
.1.3.6.1.2.1.13.1.1.1.4,APPLETALK-MIB::llapInNoHandlers,Counter32,read-only,,deprecated,,The total number of good packets received on this LocalTalk interface for which there was no protocol handler.
.1.3.6.1.2.1.13.1.1.1.5,APPLETALK-MIB::llapInLengthErrors,Counter32,read-only,,mandatory,,The total number of packets received on this LocalTalk interface whose actual length did not match the length in the header.
.1.3.6.1.2.1.13.1.1.1.6,APPLETALK-MIB::llapInErrors,Counter32,read-only,,deprecated,,The total number of packets containing errors received on this LocalTalk interface.
.1.3.6.1.2.1.13.1.1.1.7,APPLETALK-MIB::llapCollisions,Counter32,read-only,,mandatory,,The total number of collisions assumed on this LocalTalk interface due to the lack of a lapCTS reply.
.1.3.6.1.2.1.13.1.1.1.8,APPLETALK-MIB::llapDefers,Counter32,read-only,,mandatory,,The total number of times this LocalTalk interface deferred to other packets.
.1.3.6.1.2.1.13.1.1.1.9,APPLETALK-MIB::llapNoDataErrors,Counter32,read-only,,mandatory,,The total number of times this LocalTalk interface received a lapRTS packet and expected a data packet, but did not receive any data packet.
.1.3.6.1.2.1.13.1.1.1.10,APPLETALK-MIB::llapRandomCTSErrors,Counter32,read-only,,mandatory,,The total number of times this LocalTalk interface received a lapCTS packet that was not solicited by a lapRTS packet.
.1.3.6.1.2.1.13.1.1.1.11,APPLETALK-MIB::llapFCSErrors,Counter32,read-only,,mandatory,,The total number of times this LocalTalk interface received a packet with an FCS (Frame Check Sequence) error.
.1.3.6.1.2.1.13.2,APPLETALK-MIB::aarp,,,,,,
.1.3.6.1.2.1.13.2.1,APPLETALK-MIB::aarpTable,,not-accessible,,mandatory,,The AppleTalk Address Translation Table contains an equivalence of AppleTalk Network Addresses to the link layer physical address.
.1.3.6.1.2.1.13.2.1.1,APPLETALK-MIB::aarpEntry,,not-accessible,aarpIfIndex:aarpNetAddress,mandatory,,Each entry contains one AppleTalk Network Address to physical address equivalence. As an example, an instance of the aarpPhysAddress object might be named aarpPhysAddress.1.0.80.234
.1.3.6.1.2.1.13.2.1.1.1,APPLETALK-MIB::aarpIfIndex,INTEGER,read-only,,mandatory,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.13.2.1.1.2,APPLETALK-MIB::aarpPhysAddress,OCTET,read-write,,mandatory,,The media-dependent physical address.
.1.3.6.1.2.1.13.2.1.1.3,APPLETALK-MIB::aarpNetAddress,OCTET,read-only,,mandatory,,The AppleTalk Network Address corresponding to the media-dependent physical address.
.1.3.6.1.2.1.13.2.1.1.4,APPLETALK-MIB::aarpStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),The status of this AARP entry. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the aarpTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant aarpStatus object.
.1.3.6.1.2.1.13.2.2,APPLETALK-MIB::aarpLookups,Counter32,read-only,,mandatory,,The number of times the AARP cache for this entity was searched.
.1.3.6.1.2.1.13.2.3,APPLETALK-MIB::aarpHits,Counter32,read-only,,mandatory,,The number of times an entry was searched for and found in the AARP cache for this entity.
.1.3.6.1.2.1.13.3,APPLETALK-MIB::atport,,,,,,
.1.3.6.1.2.1.13.3.1,APPLETALK-MIB::atportTable,,not-accessible,,mandatory,,A list of AppleTalk ports for this entity.
.1.3.6.1.2.1.13.3.1.1,APPLETALK-MIB::atportEntry,,not-accessible,atportIndex,mandatory,,The description of one of the AppleTalk ports on this entity. As an example, an instance of the atportNetFrom object might be named atportNetFrom.2
.1.3.6.1.2.1.13.3.1.1.1,APPLETALK-MIB::atportIndex,INTEGER,read-only,,mandatory,,A unique value for each AppleTalk port. Its value is between 1 and the total number of AppleTalk ports. The value for each port must remain constant at least from the re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.13.3.1.1.2,APPLETALK-MIB::atportDescr,OCTET,read-write,,mandatory,,A text string containing information about the port. This string is intended for presentation to a human; it must not contain anything but printable ASCII characters.
.1.3.6.1.2.1.13.3.1.1.3,APPLETALK-MIB::atportType,INTEGER,read-write,,mandatory,other(1):localtalk(2):ethertalk1(3):ethertalk2(4):tokentalk(5):iptalk(6):serialPPP(7):serialNonstandard(8):virtual(9):fdditalk(10):arctalk(11):smdstalk(12):aurp(13):frameRelay(14):x25(15):ip(16):osi(17):decnetIV(18):arap(19):isdnInThePacketMode(20):nonAppleTalk3Com(21):ipx(22):arns(23):hdlc(24),The type of port, distinguished by the protocol immediately below DDP in the protocol stack.
.1.3.6.1.2.1.13.3.1.1.4,APPLETALK-MIB::atportNetStart,OCTET,read-write,,mandatory,,The first AppleTalk network address in the range configured for this port. If this port is not a native AppleTalk port, this object shall have the value of two octets of zero.
.1.3.6.1.2.1.13.3.1.1.5,APPLETALK-MIB::atportNetEnd,OCTET,read-write,,mandatory,,The last AppleTalk network address in the range configured for this port. If the network to which this AppleTalk port is connected is a non-extended network, or if it is not a native AppleTalk port, the value for atportNetEnd shall be two octets of zero.
.1.3.6.1.2.1.13.3.1.1.6,APPLETALK-MIB::atportNetAddress,OCTET,read-write,,mandatory,,The AppleTalk network address configured for this port. In addition, this value may be used as a hint for an initial node number used during node-finding. If this port is not a native AppleTalk port, this object shall have the value of three octets of zero.
.1.3.6.1.2.1.13.3.1.1.7,APPLETALK-MIB::atportStatus,INTEGER,read-write,,mandatory,routing(1):unconfigured(2):off(3):invalid(4):endNode(5):offDueToConflict(6):other(7),The configuration status of this port. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry in the atportTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atportStatus object.
.1.3.6.1.2.1.13.3.1.1.8,APPLETALK-MIB::atportNetConfig,INTEGER,read-write,,mandatory,conflictOrientedSeed(1):garnered(2):guessed(3):unconfigured(4):conflictAverseSeed(5):softSeed(6),The status of the network information for this port. If this port is not a native AppleTalk port, this object shall have the value unconfigured(4).
.1.3.6.1.2.1.13.3.1.1.9,APPLETALK-MIB::atportZoneConfig,INTEGER,read-write,,mandatory,conflictOrientedSeed(1):garnered(2):guessed(3):unconfigured(4):conflictAverseSeed(5):softSeed(6),The status of the zone information for this port. If this port is not a native AppleTalk port, this object shall have the value unconfigured(4).
.1.3.6.1.2.1.13.3.1.1.10,APPLETALK-MIB::atportZoneDefault,OCTET,read-write,,mandatory,,The name of the default zone for this port. If this port only has one zone, that zone is represented here. If this port is not a native AppleTalk port, this object shall contain an octet string of zero length. When this value is changed in a router, the router must send a zipNotify packet on the associated network.
.1.3.6.1.2.1.13.3.1.1.11,APPLETALK-MIB::atportIfIndex,INTEGER,read-write,,mandatory,,The physical interface associated with this AppleTalk port. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.2.1.13.3.1.1.12,APPLETALK-MIB::atportNetFrom,OCTET,read-only,,mandatory,,When atportNetConfig is set to garnered(2), this variable contains the DDP address of an entity from which the AppleTalk network number was garnered. When atportNetConfig is set to conflictOrientedSeed(1), conflictAverseSeed(5), or softSeed(6), this variable contains the DDP address of an entity which confirmed or supplied our AppleTalk network number, for example by replying to a ZIP GetNetInfo request. If atportNetConfig is set to guessed(3) or unconfigured(4), or if the entity has not received any network number confirmation, this variable should be set to three octets of zero.
.1.3.6.1.2.1.13.3.1.1.13,APPLETALK-MIB::atportZoneFrom,OCTET,read-only,,mandatory,,When atportZoneConfig is set to garnered(2), this variable contains the DDP address of an entity from which the AppleTalk zone list was garnered. When atportZoneConfig is set to conflictOrientedSeed(1), conflictAverseSeed(5), or softSeed(6), this variable contains the DDP address of an entity which confirmed or supplied our AppleTalk zone information, for example by replying to a ZIP GetNetInfo request or a ZIP Query. If atportZoneConfig is set to guessed(3) or unconfigured(4), or if the entity has not received any zone confirmation, this variable should be set to three octets of zero.
.1.3.6.1.2.1.13.3.1.1.14,APPLETALK-MIB::atportInPkts,Counter32,read-only,,mandatory,,The number of packets received by this entity on this port.
.1.3.6.1.2.1.13.3.1.1.15,APPLETALK-MIB::atportOutPkts,Counter32,read-only,,mandatory,,The number of packets transmitted by this entity on this port.
.1.3.6.1.2.1.13.3.1.1.16,APPLETALK-MIB::atportHome,INTEGER,read-only,,mandatory,home(1):notHome(2),An indication of whether or not the entity is homed on this port, that is to say, a port on which the entity could perform NBP registrations for services that it chooses to advertise.
.1.3.6.1.2.1.13.3.1.1.17,APPLETALK-MIB::atportCurrentZone,OCTET,read-write,,mandatory,,The current zone for the port. In general, this is the zone name in which services on this port will be registered. If this port is not a native AppleTalk port, this object shall contain an octet string of zero length. Note that modifications to this object do not affect the nbpTable.
.1.3.6.1.2.1.13.3.1.1.18,APPLETALK-MIB::atportConflictPhysAddr,OCTET,read-only,,mandatory,,The link-layer address of a device which caused this entity to set atportStatus to offDueToConflict(6). If this address is not available, or if the entity has not set atportStatus to offDueToConflict, this object shall be a zero length OCTET STRING.
.1.3.6.1.2.1.13.3.2,APPLETALK-MIB::atportZoneTable,,not-accessible,,mandatory,,The table of zone information for non-default zones on ports.
.1.3.6.1.2.1.13.3.2.1,APPLETALK-MIB::atportZoneEntry,,not-accessible,atportZonePort:atportZoneName,mandatory,,An entry of zone information for a port. As an example, an instance of the atportZoneStatus object might be named atportZoneStatus.2.8.84.119.105.108.105.103.104.116
.1.3.6.1.2.1.13.3.2.1.1,APPLETALK-MIB::atportZonePort,INTEGER,not-accessible,,mandatory,,An integer representing the port to which this zone belongs. The port identified by a particular value of this object is the same port as identified by the same value of atportIndex.
.1.3.6.1.2.1.13.3.2.1.2,APPLETALK-MIB::atportZoneName,OCTET,not-accessible,,mandatory,,A zone name configured for the AppleTalk port referred to in the corresponding entry of atportZonePort. When this value is changed in a router, the router must send a zipNotify packet on the associated network.
.1.3.6.1.2.1.13.3.2.1.3,APPLETALK-MIB::atportZoneStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),The status of this zone entry. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the atportZoneTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atportZoneStatus object.
.1.3.6.1.2.1.13.4,APPLETALK-MIB::ddp,,,,,,
.1.3.6.1.2.1.13.4.1,APPLETALK-MIB::ddpOutRequests,Counter32,read-only,,mandatory,,The total number of DDP datagrams which were supplied to DDP by local DDP clients in requests for transmission. Note that this counter does not include any datagrams counted in ddpForwRequests.
.1.3.6.1.2.1.13.4.2,APPLETALK-MIB::ddpOutShorts,Counter32,read-only,,mandatory,,The total number of short DDP datagrams which were transmitted from this entity.
.1.3.6.1.2.1.13.4.3,APPLETALK-MIB::ddpOutLongs,Counter32,read-only,,mandatory,,The total number of long DDP datagrams which were transmitted from this entity.
.1.3.6.1.2.1.13.4.4,APPLETALK-MIB::ddpInReceives,Counter32,read-only,,mandatory,,The total number of input datagrams received by DDP, including those received in error.
.1.3.6.1.2.1.13.4.5,APPLETALK-MIB::ddpForwRequests,Counter32,read-only,,mandatory,,The number of input datagrams for which this entity was not their final DDP destination, as a result of which an attempt was made to find a route to forward them to that final destination.
.1.3.6.1.2.1.13.4.6,APPLETALK-MIB::ddpInLocalDatagrams,Counter32,read-only,,mandatory,,The total number of input DDP datagrams for which this entity was their final DDP destination.
.1.3.6.1.2.1.13.4.7,APPLETALK-MIB::ddpNoProtocolHandlers,Counter32,read-only,,mandatory,,The total number of DDP datagrams addressed to this entity that were addressed to an upper layer protocol for which no protocol handler existed.
.1.3.6.1.2.1.13.4.8,APPLETALK-MIB::ddpOutNoRoutes,Counter32,read-only,,mandatory,,The total number of DDP datagrams dropped because a route could not be found to their final destination.
.1.3.6.1.2.1.13.4.9,APPLETALK-MIB::ddpTooShortErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams dropped because the received data length was less than the data length specified in the DDP header or the received data length was less than the length of the expected DDP header.
.1.3.6.1.2.1.13.4.10,APPLETALK-MIB::ddpTooLongErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams dropped because they exceeded the maximum DDP datagram size.
.1.3.6.1.2.1.13.4.11,APPLETALK-MIB::ddpBroadcastErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams dropped because this entity was not their final destination and they were addressed to the link level broadcast.
.1.3.6.1.2.1.13.4.12,APPLETALK-MIB::ddpShortDDPErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams dropped because this entity was not their final destination and their type was short DDP.
.1.3.6.1.2.1.13.4.13,APPLETALK-MIB::ddpHopCountErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams dropped because this entity was not their final destination and their hop count would exceed 15.
.1.3.6.1.2.1.13.4.14,APPLETALK-MIB::ddpChecksumErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams for which this DDP entity was their final destination, and which were dropped because of a checksum error.
.1.3.6.1.2.1.13.4.15,APPLETALK-MIB::ddpListenerTable,,not-accessible,,mandatory,,The ddpListenerTable stores information for each DDP socket that has a listener.
.1.3.6.1.2.1.13.4.15.1,APPLETALK-MIB::ddpListenerEntry,,not-accessible,ddpListenerAddress,mandatory,,This ddpListenerEntry contains information about a particular socket that has a socket listener. As an example, an instance of the ddpListenerStatus object might be named ddpListenerStatus.0.80.220.1
.1.3.6.1.2.1.13.4.15.1.1,APPLETALK-MIB::ddpListenerAddress,OCTET,not-accessible,,mandatory,,The DDP address that this socket listener is bound to. If this socket listener isn't bound to a particular address, for instance if it is intended for all interfaces, this object shall have the value of three octets of zero followed by one octet of socket number. The socket number must not equal zero.
.1.3.6.1.2.1.13.4.15.1.2,APPLETALK-MIB::ddpListenerInPkts,Counter32,read-only,,mandatory,,The number of packets received for this listener.
.1.3.6.1.2.1.13.4.15.1.3,APPLETALK-MIB::ddpListenerStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),The status of this socket listener. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ddpListenerTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ddpListenerStatus object.
.1.3.6.1.2.1.13.4.16,APPLETALK-MIB::ddpForwardingTable,,not-accessible,,mandatory,,A table of forwarding entries for DDP. This table contains a route for each AppleTalk network currently known to the entity.
.1.3.6.1.2.1.13.4.16.1,APPLETALK-MIB::ddpForwardingEntry,,not-accessible,ddpForwardingNetEnd,mandatory,,A forwarding entry for a particular AppleTalk network. As an example, an instance of the ddpForwardingPort object might be named ddpForwardingPort.0.90
.1.3.6.1.2.1.13.4.16.1.1,APPLETALK-MIB::ddpForwardingNetEnd,OCTET,not-accessible,,mandatory,,The last network number in the network range matched by this forwarding entry. This will not be zero even if this corresponds to a non-extended net.
.1.3.6.1.2.1.13.4.16.1.2,APPLETALK-MIB::ddpForwardingNetStart,OCTET,read-only,,mandatory,,The first network number in the network range matched by this forwarding entry.
.1.3.6.1.2.1.13.4.16.1.3,APPLETALK-MIB::ddpForwardingNextHop,OCTET,read-only,,mandatory,,The next hop in the route to this entry's destination network. The format of this address can be determined by examinating the atportType corresponding to this entry.
.1.3.6.1.2.1.13.4.16.1.4,APPLETALK-MIB::ddpForwardingProto,OBJECT,read-only,,mandatory,,The routing mechanism by which this route was learned.
.1.3.6.1.2.1.13.4.16.1.5,APPLETALK-MIB::ddpForwardingModifiedTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time of the last modification to this entry. The initial value of ddpForwardingModified time shall be the value of sysUpTime at the time the entry is created.
.1.3.6.1.2.1.13.4.16.1.6,APPLETALK-MIB::ddpForwardingUseCounts,Counter32,read-only,,mandatory,,The number of times this entry has been used to route a packet to the destination network. Note that this counter is not cleared when the corresponding ddpForwardingNextHop variable changes.
.1.3.6.1.2.1.13.4.16.1.7,APPLETALK-MIB::ddpForwardingPort,INTEGER,read-only,,mandatory,,The AppleTalk port through which ddpForwardingNextHop is reached. The interface identified by a particular value of this variable is the same interface as identified by the same value of atportIndex.
.1.3.6.1.2.1.13.4.17,APPLETALK-MIB::ddpForwProtoOids,,,,,,
.1.3.6.1.2.1.13.4.17.1,APPLETALK-MIB::rtmpRoutingProto,,,,,,
.1.3.6.1.2.1.13.4.17.2,APPLETALK-MIB::kipRoutingProto,,,,,,
.1.3.6.1.2.1.13.4.18,APPLETALK-MIB::ddpForwardingTableOverflows,Counter32,read-only,,mandatory,,The number of times the entity attempted to add an entry to the forwarding table but failed due to overflow.
.1.3.6.1.2.1.13.5,APPLETALK-MIB::rtmp,,,,,,
.1.3.6.1.2.1.13.5.1,APPLETALK-MIB::rtmpTable,,not-accessible,,mandatory,,A list of Routing Table Maintenance Protocol entries for this entity.
.1.3.6.1.2.1.13.5.1.1,APPLETALK-MIB::rtmpEntry,,not-accessible,rtmpRangeStart,mandatory,,The route entry to a particular network range. As an example, an instance of the rtmpPort object might be named rtmpPort.0.80
.1.3.6.1.2.1.13.5.1.1.1,APPLETALK-MIB::rtmpRangeStart,OCTET,read-only,,mandatory,,The first DDP network address in the network range to which this routing entry pertains. This is a two octet DDP network address in network byte order.
.1.3.6.1.2.1.13.5.1.1.2,APPLETALK-MIB::rtmpRangeEnd,OCTET,read-only,,mandatory,,The last DDP network address in the network range to which this routing entry pertains. This is a two octet DDP network address in network byte order. If the network to which this routing entry pertains is a non-extended network, the value for rtmpRangeEnd shall be two octets of zero.
.1.3.6.1.2.1.13.5.1.1.3,APPLETALK-MIB::rtmpNextHop,OCTET,read-only,,mandatory,,The next internet router in the route to this entry's destination network. The format of this address can be determined by examinating the atportType corresponding to this entry.
.1.3.6.1.2.1.13.5.1.1.4,APPLETALK-MIB::rtmpType,INTEGER,read-only,,mandatory,other(1):appletalk(2):serialPPP(3):serialNonstandard(4),The type of network over which this route points.
.1.3.6.1.2.1.13.5.1.1.5,APPLETALK-MIB::rtmpPort,INTEGER,read-only,,mandatory,,The AppleTalk port over which this route points. The interface identified by a particular value of this variable is the same interface as identified by the same value of atportIndex.
.1.3.6.1.2.1.13.5.1.1.6,APPLETALK-MIB::rtmpHops,INTEGER,read-only,,mandatory,,The number of hops required to reach the destination network to which this routing entry pertains.
.1.3.6.1.2.1.13.5.1.1.7,APPLETALK-MIB::rtmpState,INTEGER,read-write,,mandatory,good(1):suspect(2):badZero(3):badOne(4):invalid(5),The status of the information contained in this route entry. Setting this object to the value invalid(5) has the effect of invalidating the corresponding entry in the rtmpTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant rtmpState object.
.1.3.6.1.2.1.13.5.2,APPLETALK-MIB::rtmpInDataPkts,Counter32,read-only,,mandatory,,A count of the number of good RTMP data packets received by this entity.
.1.3.6.1.2.1.13.5.3,APPLETALK-MIB::rtmpOutDataPkts,Counter32,read-only,,mandatory,,A count of the number of RTMP packets sent by this entity.
.1.3.6.1.2.1.13.5.4,APPLETALK-MIB::rtmpInRequestPkts,Counter32,read-only,,mandatory,,A count of the number of good RTMP Request packets received by this entity.
.1.3.6.1.2.1.13.5.5,APPLETALK-MIB::rtmpNextIREqualChanges,Counter32,read-only,,mandatory,,A count of the number of times RTMP changes the Next Internet Router in a routing entry because the hop count advertised in a routing tuple was equal to the current hop count for a particular network.
.1.3.6.1.2.1.13.5.6,APPLETALK-MIB::rtmpNextIRLessChanges,Counter32,read-only,,mandatory,,A count of the number of times RTMP changes the Next Internet Router in a routing entry because the hop count advertised in a routing tuple was less than the current hop count for a particular network.
.1.3.6.1.2.1.13.5.7,APPLETALK-MIB::rtmpRouteDeletes,Counter32,read-only,,mandatory,,A count of the number of times RTMP deletes a route because it was aged out of the table. This can help to detect routing problems.
.1.3.6.1.2.1.13.5.8,APPLETALK-MIB::rtmpRoutingTableOverflows,Counter32,read-only,,mandatory,,The number of times RTMP attempted to add a route to the RTMP table but failed due to lack of space.
.1.3.6.1.2.1.13.6,APPLETALK-MIB::kip,,,,,,
.1.3.6.1.2.1.13.6.1,APPLETALK-MIB::kipTable,,not-accessible,,mandatory,,The table of routing information for KIP networks.
.1.3.6.1.2.1.13.6.1.1,APPLETALK-MIB::kipEntry,,not-accessible,kipNetStart,mandatory,,An entry in the routing table for KIP networks. As an example, an instance of the kipCore object might be named kipCore.0.80
.1.3.6.1.2.1.13.6.1.1.1,APPLETALK-MIB::kipNetStart,OCTET,read-only,,mandatory,,The first AppleTalk network address in the range for this routing entry. This address is a two octet DDP network address in network byte order.
.1.3.6.1.2.1.13.6.1.1.2,APPLETALK-MIB::kipNetEnd,OCTET,read-write,,mandatory,,The last AppleTalk network address in the range for this routing entry. This address is a two octet DDP network address in network byte order. If the network to which this AppleTalk port is connected is a non-extended network, the value for kipNetEnd shall be two octets of zero.
.1.3.6.1.2.1.13.6.1.1.3,APPLETALK-MIB::kipNextHop,IpAddress,read-write,,mandatory,,The IP address of the next hop in the route to this entry's destination network.
.1.3.6.1.2.1.13.6.1.1.4,APPLETALK-MIB::kipHopCount,INTEGER,read-write,,mandatory,,The number of hops required to reach the destination network to which this entry pertains.
.1.3.6.1.2.1.13.6.1.1.5,APPLETALK-MIB::kipBCastAddr,IpAddress,read-write,,mandatory,,The form of the IP address used to broadcast on this network.
.1.3.6.1.2.1.13.6.1.1.6,APPLETALK-MIB::kipCore,INTEGER,read-write,,mandatory,core(1):notcore(2),The status of kipNextHop as a core gateway.
.1.3.6.1.2.1.13.6.1.1.7,APPLETALK-MIB::kipType,INTEGER,read-write,,mandatory,kipRouter(1):net(2):host(3):other(4):async(5),The type of the entity that this route points to.
.1.3.6.1.2.1.13.6.1.1.8,APPLETALK-MIB::kipState,INTEGER,read-write,,mandatory,configured(1):learned(2):invalid(3),The state of this network entry. Setting this object to the value invalid(3) has the effect of invalidating the corresponding entry in the kipTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant kipState object.
.1.3.6.1.2.1.13.6.1.1.9,APPLETALK-MIB::kipShare,INTEGER,read-write,,mandatory,shared(1):private(2),If the information in this entry is propagated to other routers as part of the AA routing protocol, the value of this variable is equal to shared(1). Otherwise its value is private(2).
.1.3.6.1.2.1.13.6.1.1.10,APPLETALK-MIB::kipFrom,IpAddress,read-only,,mandatory,,The IP address from which the routing entry was learned via the AA protocol. If this entry was not created via the AA protocol, it should contain IP address 0.0.0.0.
.1.3.6.1.2.1.13.7,APPLETALK-MIB::zipRouter,,,,,,
.1.3.6.1.2.1.13.7.1,APPLETALK-MIB::zipTable,,not-accessible,,mandatory,,The table of zone information for reachable AppleTalk networks.
.1.3.6.1.2.1.13.7.1.1,APPLETALK-MIB::zipEntry,,not-accessible,zipZoneNetStart:zipZoneIndex,mandatory,,An entry of zone information for a particular zone and network combination. As an example, an instance of the zipZoneState object might be named zipZoneState.0.80.4
.1.3.6.1.2.1.13.7.1.1.1,APPLETALK-MIB::zipZoneName,OCTET,read-only,,mandatory,,The zone name of this entry. This is stored in Mac ASCII format. If the full zone list for the entry is not known, the value for zipZoneName shall be a zero length octet string.
.1.3.6.1.2.1.13.7.1.1.2,APPLETALK-MIB::zipZoneIndex,INTEGER,read-only,,mandatory,,An integer that is unique to the zipZoneName that is present in this entry. For any given zone name, every zipEntry that has an equal zone name will have the same zipZoneIndex. When a zone name is discovered which is not currently in the table, it will be assigned an index greater than any previously assigned index.
.1.3.6.1.2.1.13.7.1.1.3,APPLETALK-MIB::zipZoneNetStart,OCTET,read-only,,mandatory,,The network that starts the range for this entry. This address is a two octet DDP network address in network byte order.
.1.3.6.1.2.1.13.7.1.1.4,APPLETALK-MIB::zipZoneNetEnd,OCTET,read-only,,mandatory,,The network that ends the range for this entry. This address is a two octet DDP network address in network byte order. If the network to which this zip entry pertains is a non-extended network, the value for zipZoneNetEnd shall be two octets of zero.
.1.3.6.1.2.1.13.7.1.1.5,APPLETALK-MIB::zipZoneState,INTEGER,read-write,,mandatory,valid(1):invalid(2),The state of this zip entry. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the zipTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant zipZoneState object.
.1.3.6.1.2.1.13.7.1.1.6,APPLETALK-MIB::zipZoneFrom,OCTET,read-only,,mandatory,,The address from which this zone name to network number mapping was learned. The format of this address can be determined by examining the atportType corresponding to this entry. When this mapping is learned from the entity itself, this object shall have the value of three octets of zero.
.1.3.6.1.2.1.13.7.1.1.7,APPLETALK-MIB::zipZonePort,INTEGER,read-only,,mandatory,,The AppleTalk port through which this zone name to network number mapping was learned. The interface identified by a particular value of this variable is the same interface as identified by the same value of atportIndex.
.1.3.6.1.2.1.13.7.2,APPLETALK-MIB::zipInZipQueries,Counter32,read-only,,mandatory,,The number of ZIP Queries received by this entity.
.1.3.6.1.2.1.13.7.3,APPLETALK-MIB::zipInZipReplies,Counter32,read-only,,mandatory,,The number of ZIP Replies received by this entity.
.1.3.6.1.2.1.13.7.4,APPLETALK-MIB::zipInZipExtendedReplies,Counter32,read-only,,mandatory,,The number of ZIP Extended Replies received by this entity.
.1.3.6.1.2.1.13.7.5,APPLETALK-MIB::zipZoneConflictErrors,Counter32,read-only,,mandatory,,The number of times a conflict has been detected between this entity's zone information and another entity's zone information.
.1.3.6.1.2.1.13.7.6,APPLETALK-MIB::zipInObsoletes,Counter32,read-only,,mandatory,,The number of ZIP Takedown or ZIP Bringup packets received by this entity. Note that as the ZIP Takedown and ZIP Bringup packets have been obsoleted, the receipt of one of these packets indicates that a node sent it in error.
.1.3.6.1.2.1.13.7.7,APPLETALK-MIB::zipRouterNetInfoTable,,not-accessible,,mandatory,,The table of Net Info packets received by each port on this entity.
.1.3.6.1.2.1.13.7.7.1,APPLETALK-MIB::zipRouterNetInfoEntry,,not-accessible,atportIndex,mandatory,,The description of the Net Info packets received on a particular port on this entity. One such entry shall exist for each atport on this router entity. As an example, an instance of the zipInGetNetInfos object might be named zipInGetNetInfos.2
.1.3.6.1.2.1.13.7.7.1.1,APPLETALK-MIB::zipInGetNetInfos,Counter32,read-only,,mandatory,,The number of ZIP GetNetInfo packets received on this port by this entity.
.1.3.6.1.2.1.13.7.7.1.2,APPLETALK-MIB::zipOutGetNetInfoReplies,Counter32,read-only,,mandatory,,The number of ZIP GetNetInfo Reply packets sent out this port by this entity.
.1.3.6.1.2.1.13.7.7.1.3,APPLETALK-MIB::zipZoneOutInvalids,Counter32,read-only,,mandatory,,The number of times this entity has sent a ZIP GetNetInfo Reply with the zone invalid bit set in response to a GetNetInfo Request with an invalid zone name.
.1.3.6.1.2.1.13.7.7.1.4,APPLETALK-MIB::zipAddressInvalids,Counter32,read-only,,mandatory,,The number of times this entity had to broadcast a ZIP GetNetInfo Reply because the GetNetInfo Request had an invalid address.
.1.3.6.1.2.1.13.8,APPLETALK-MIB::nbp,,,,,,
.1.3.6.1.2.1.13.8.1,APPLETALK-MIB::nbpTable,,not-accessible,,mandatory,,The table of NBP services registered on this entity.
.1.3.6.1.2.1.13.8.1.1,APPLETALK-MIB::nbpEntry,,not-accessible,nbpIndex,mandatory,,The description of an NBP service registered on this entity. As an example, an instance of the nbpZone object might be named nbpZone.2
.1.3.6.1.2.1.13.8.1.1.1,APPLETALK-MIB::nbpIndex,INTEGER,read-write,,mandatory,,The index of this NBP entry. This index is unique with respect to the indexes of all other NBP entries, and shall remain constant throughout the lifetime of this object.
.1.3.6.1.2.1.13.8.1.1.2,APPLETALK-MIB::nbpObject,OCTET,read-write,,mandatory,,The name of the service described by this entity. When this variable is changed, the entity should perform an NBP registration using the new nbpObject.
.1.3.6.1.2.1.13.8.1.1.3,APPLETALK-MIB::nbpType,OCTET,read-write,,mandatory,,The type of the service described by this entity. When this variable is changed, the entity should perform an NBP registration using the new nbpType.
.1.3.6.1.2.1.13.8.1.1.4,APPLETALK-MIB::nbpZone,OCTET,read-write,,mandatory,,The zone the service described by this entity is registered in. This must be the actual zone name, without any wildcard characters. When this variable is changed, the entity should perform an NBP registration using the new nbpZone.
.1.3.6.1.2.1.13.8.1.1.5,APPLETALK-MIB::nbpState,INTEGER,read-write,,mandatory,valid(1):registering(2):registrationFailed(3):invalid(4),The state of this NBP entry. When the registration for an entry in the nbpTable fails, it is an implementation-specific matter as to how long the entry will remain in the registrationFailed(3) state before moving to the invalid(4) state. Note that the entry may pass immediately from the registrationFailed state to the invalid state. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry in the nbpTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant nbpState object.
.1.3.6.1.2.1.13.8.1.1.6,APPLETALK-MIB::nbpAddress,OCTET,read-write,,mandatory,,The DDP network, node, and socket number of this entity. If this is unspecified, for instance if the registration is on all ports of a multiport device, this object shall have the value of three octets of zero, followed by one octet of socket number.
.1.3.6.1.2.1.13.8.1.1.7,APPLETALK-MIB::nbpEnumerator,INTEGER,read-only,,mandatory,,The enumerator assigned to this entity.
.1.3.6.1.2.1.13.8.2,APPLETALK-MIB::nbpInLookUpRequests,Counter32,read-only,,mandatory,,The number of NBP LookUp Requests received.
.1.3.6.1.2.1.13.8.3,APPLETALK-MIB::nbpInLookUpReplies,Counter32,read-only,,mandatory,,The number of NBP LookUp Replies received.
.1.3.6.1.2.1.13.8.4,APPLETALK-MIB::nbpInBroadcastRequests,Counter32,read-only,,mandatory,,The number of NBP Broadcast Requests received.
.1.3.6.1.2.1.13.8.5,APPLETALK-MIB::nbpInForwardRequests,Counter32,read-only,,mandatory,,The number of NBP Forward Requests received.
.1.3.6.1.2.1.13.8.6,APPLETALK-MIB::nbpOutLookUpReplies,Counter32,read-only,,mandatory,,The number of NBP LookUp Replies sent.
.1.3.6.1.2.1.13.8.7,APPLETALK-MIB::nbpRegistrationFailures,Counter32,read-only,,mandatory,,The number of times this node experienced a failure in attempting to register an NBP entity.
.1.3.6.1.2.1.13.8.8,APPLETALK-MIB::nbpInErrors,Counter32,read-only,,mandatory,,The number of NBP packets received by this entity that were rejected for any error.
.1.3.6.1.2.1.13.9,APPLETALK-MIB::atecho,,,,,,
.1.3.6.1.2.1.13.9.1,APPLETALK-MIB::atechoRequests,Counter32,read-only,,mandatory,,The number of AppleTalk Echo requests received.
.1.3.6.1.2.1.13.9.2,APPLETALK-MIB::atechoReplies,Counter32,read-only,,mandatory,,The number of AppleTalk Echo replies sent.
.1.3.6.1.2.1.13.9.3,APPLETALK-MIB::atechoOutRequests,Counter32,read-only,,mandatory,,The count of AppleTalk Echo requests sent.
.1.3.6.1.2.1.13.9.4,APPLETALK-MIB::atechoInReplies,Counter32,read-only,,mandatory,,The count of AppleTalk Echo replies received.
.1.3.6.1.2.1.13.10,APPLETALK-MIB::atp,,,,,,
.1.3.6.1.2.1.13.10.1,APPLETALK-MIB::atpInPkts,Counter32,read-only,,mandatory,,The number of ATP packets received by this entity.
.1.3.6.1.2.1.13.10.2,APPLETALK-MIB::atpOutPkts,Counter32,read-only,,mandatory,,The number of ATP packets sent by this entity.
.1.3.6.1.2.1.13.10.3,APPLETALK-MIB::atpTRequestRetransmissions,Counter32,read-only,,mandatory,,The number of times that a timeout occurred and a Transaction Request packet needed to be retransmitted by this host.
.1.3.6.1.2.1.13.10.4,APPLETALK-MIB::atpTResponseRetransmissions,Counter32,read-only,,mandatory,,The number of times a timeout was detected and a Transaction Response packet needed to be retransmitted by this host.
.1.3.6.1.2.1.13.10.5,APPLETALK-MIB::atpReleaseTimerExpiredCounts,Counter32,read-only,,mandatory,,The number of times the release timer expired, as a result of which a Request Control Block had to be deleted.
.1.3.6.1.2.1.13.10.6,APPLETALK-MIB::atpRetryCountExceededs,Counter32,read-only,,mandatory,,The number of times the retry count was exceeded, and an error was returned to the client of ATP.
.1.3.6.1.2.1.13.10.7,APPLETALK-MIB::atpListenerTable,,not-accessible,,mandatory,,The atpListenerTable stores information for each ATP socket that has a listener.
.1.3.6.1.2.1.13.10.7.1,APPLETALK-MIB::atpListenerEntry,,not-accessible,atpListenerAddress,mandatory,,This atpListenerEntry contains information about a particular socket that has a socket listener. As an example, an instance of the atpListenerStatus object might be named atpListenerStatus.0.80.220.3
.1.3.6.1.2.1.13.10.7.1.1,APPLETALK-MIB::atpListenerAddress,OCTET,not-accessible,,mandatory,,The DDP address that this socket listener is bound to. If this socket listener isn't bound to a particular address, for instance if it is intended for all interfaces, this object shall have the value of three octets of zero followed by one octet of socket number.
.1.3.6.1.2.1.13.10.7.1.2,APPLETALK-MIB::atpListenerStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),The status of this socket. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the atpListenerTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant atpListenerStatus object.
.1.3.6.1.2.1.13.11,APPLETALK-MIB::pap,,,,,,
.1.3.6.1.2.1.13.11.1,APPLETALK-MIB::papInOpenConns,Counter32,read-only,,mandatory,,The number of PAP Open Connection requests received by this entity.
.1.3.6.1.2.1.13.11.2,APPLETALK-MIB::papOutOpenConns,Counter32,read-only,,mandatory,,The number of PAP Open Connection requests sent by this entity.
.1.3.6.1.2.1.13.11.3,APPLETALK-MIB::papInDatas,Counter32,read-only,,mandatory,,The number of PAP Data messages received by this entity.
.1.3.6.1.2.1.13.11.4,APPLETALK-MIB::papOutDatas,Counter32,read-only,,mandatory,,The number of PAP Data messages sent by this entity.
.1.3.6.1.2.1.13.11.5,APPLETALK-MIB::papInCloseConns,Counter32,read-only,,mandatory,,The number of PAP Close Connection requests received by this entity.
.1.3.6.1.2.1.13.11.6,APPLETALK-MIB::papOutCloseConns,Counter32,read-only,,mandatory,,The number of PAP Close Connection requests sent by this entity.
.1.3.6.1.2.1.13.11.7,APPLETALK-MIB::papTickleTimeoutCloses,Counter32,read-only,,mandatory,,The number of times the PAP entity on this node closed a connection because it didn't receive a Tickle message before its timer expired.
.1.3.6.1.2.1.13.11.8,APPLETALK-MIB::papServerTable,,not-accessible,,mandatory,,A list of servers on this entity that are accessible through the Printer Access Protocol.
.1.3.6.1.2.1.13.11.8.1,APPLETALK-MIB::papServerEntry,,not-accessible,papServerIndex,mandatory,,A set of information about a particular PAP server's configuration and performance. As an example, an instance of the papServerStatus object might be named papServerStatus.1
.1.3.6.1.2.1.13.11.8.1.1,APPLETALK-MIB::papServerIndex,INTEGER,not-accessible,,mandatory,,An unique value for each Printer Access Protocol Server.
.1.3.6.1.2.1.13.11.8.1.2,APPLETALK-MIB::papServerListeningSocket,OCTET,read-write,,mandatory,,The Server Listening Socket that this PAP server is listening on.
.1.3.6.1.2.1.13.11.8.1.3,APPLETALK-MIB::papServerStatus,OCTET,read-only,,mandatory,,The status string of this server. This is the message as it would appear in a PAP Status Reply from this server.
.1.3.6.1.2.1.13.11.8.1.4,APPLETALK-MIB::papServerCompletedJobs,Counter32,read-only,,mandatory,,The number of jobs that have been accepted and successfully executed by this server.
.1.3.6.1.2.1.13.11.8.1.5,APPLETALK-MIB::papServerBusyJobs,INTEGER,read-only,,mandatory,,The number of GetNextJob calls that have accepted and are currently executing a job.
.1.3.6.1.2.1.13.11.8.1.6,APPLETALK-MIB::papServerFreeJobs,INTEGER,read-only,,mandatory,,The minimum number of GetNextJob calls that are currently waiting for a job.
.1.3.6.1.2.1.13.11.8.1.7,APPLETALK-MIB::papServerAuthenticationFailures,Counter32,read-only,,mandatory,,The number of times this PAP server rejected a job because the job was not correctly authenticated.
.1.3.6.1.2.1.13.11.8.1.8,APPLETALK-MIB::papServerAccountingFailures,Counter32,read-only,,mandatory,,The number of times this PAP server rejected a job because the job did not fit some accounting rule, such as exceeding a quota.
.1.3.6.1.2.1.13.11.8.1.9,APPLETALK-MIB::papServerGeneralFailures,Counter32,read-only,,mandatory,,The number of times this PAP server rejected a job for some reason other than authentication or accounting failures.
.1.3.6.1.2.1.13.11.8.1.10,APPLETALK-MIB::papServerState,INTEGER,read-write,,mandatory,valid(1):invalid(2),The state of this PAP Server entry. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the papServerTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant papServerState object.
.1.3.6.1.2.1.13.11.8.1.11,APPLETALK-MIB::papServerLastStatusMsg,OCTET,read-only,,mandatory,,The last status message that was transmitted by this server.
.1.3.6.1.2.1.13.12,APPLETALK-MIB::asp,,,,,,
.1.3.6.1.2.1.13.12.1,APPLETALK-MIB::aspInputTransactions,Counter32,read-only,,mandatory,,The number of ASP requests and replies received by this entity. Note that this is not necessarily the number of packets containing ASP transactions.
.1.3.6.1.2.1.13.12.2,APPLETALK-MIB::aspOutputTransactions,Counter32,read-only,,mandatory,,The number of ASP requests and replies sent by this entity. Note that this is not necessarily the number of packets containing ASP transactions.
.1.3.6.1.2.1.13.12.3,APPLETALK-MIB::aspInOpenSessions,Counter32,read-only,,mandatory,,The number of ASP Open Session requests and replies received by this entity.
.1.3.6.1.2.1.13.12.4,APPLETALK-MIB::aspOutOpenSessions,Counter32,read-only,,mandatory,,The number of ASP Open Session requests and replies sent by this entity.
.1.3.6.1.2.1.13.12.5,APPLETALK-MIB::aspInCloseSessions,Counter32,read-only,,mandatory,,The number of ASP Close Session requests and replies received by this entity.
.1.3.6.1.2.1.13.12.6,APPLETALK-MIB::aspOutCloseSessions,Counter32,read-only,,mandatory,,The number of ASP Close Session requests and replies sent by this entity.
.1.3.6.1.2.1.13.12.7,APPLETALK-MIB::aspNoMoreSessionsErrors,Counter32,read-only,,mandatory,,The number of times an error condition was returned because this server implementation could not support another session.
.1.3.6.1.2.1.13.12.8,APPLETALK-MIB::aspTickleTimeOutCloses,Counter32,read-only,,mandatory,,The number of times the ASP entity on this node closed a connection because it didn't receive any messages from the remote end before its timer expired.
.1.3.6.1.2.1.13.12.9,APPLETALK-MIB::aspConnTable,,not-accessible,,mandatory,,A list of ASP connections on this entity.
.1.3.6.1.2.1.13.12.9.1,APPLETALK-MIB::aspConnEntry,,not-accessible,aspConnLocalAddress:aspConnRemoteAddress:aspConnID,mandatory,,A set of information describing an ASP connection. As an example, an instance of the aspConnState object might be named aspConnState.0.80.220.135.0.80.239.119.12
.1.3.6.1.2.1.13.12.9.1.1,APPLETALK-MIB::aspConnLocalAddress,OCTET,not-accessible,,mandatory,,The local address of this ASP connection.
.1.3.6.1.2.1.13.12.9.1.2,APPLETALK-MIB::aspConnRemoteAddress,OCTET,not-accessible,,mandatory,,The remote address of this ASP connection. If this entry is in the listening mode, this object shall have a value of four octets of zero.
.1.3.6.1.2.1.13.12.9.1.3,APPLETALK-MIB::aspConnID,INTEGER,not-accessible,,mandatory,,The remote Connection ID of this ASP connection. If this entry is in the listening mode, this object shall have a value of zero.
.1.3.6.1.2.1.13.12.9.1.4,APPLETALK-MIB::aspConnLastReqNum,INTEGER,read-only,,mandatory,,The last request number on this ASP connection. If this entry is in the listening mode, this object shall have a value of zero.
.1.3.6.1.2.1.13.12.9.1.5,APPLETALK-MIB::aspConnServerEnd,INTEGER,read-only,,mandatory,sss(1):wss(2):sls(3),Specifies what mode the local session end is in.
.1.3.6.1.2.1.13.12.9.1.6,APPLETALK-MIB::aspConnState,INTEGER,read-write,,mandatory,open(1):closed(2):invalid(3),The state of this ASP connection. Setting this object to the value invalid(3) has the effect of invalidating the corresponding entry in the aspConnTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant aspConnState object.
.1.3.6.1.2.1.13.13,APPLETALK-MIB::adsp,,,,,,
.1.3.6.1.2.1.13.13.1,APPLETALK-MIB::adspInPkts,Counter32,read-only,,mandatory,,The number of ADSP packets received by this entity.
.1.3.6.1.2.1.13.13.2,APPLETALK-MIB::adspOutPkts,Counter32,read-only,,mandatory,,The number of ADSP packets sent by this entity.
.1.3.6.1.2.1.13.13.3,APPLETALK-MIB::adspInOctets,Counter32,read-only,,mandatory,,The number of data octets contained in ADSP packets received by this entity. Note that this does not include EOM bits.
.1.3.6.1.2.1.13.13.4,APPLETALK-MIB::adspOutOctets,Counter32,read-only,,mandatory,,The number of data octets contained in ADSP packets sent by this entity. Note that this does not include EOM bits.
.1.3.6.1.2.1.13.13.5,APPLETALK-MIB::adspInDataPkts,Counter32,read-only,,mandatory,,The number of ADSP data packets this entity has received.
.1.3.6.1.2.1.13.13.6,APPLETALK-MIB::adspOutDataPkts,Counter32,read-only,,mandatory,,The number of ADSP data packets this entity has sent.
.1.3.6.1.2.1.13.13.7,APPLETALK-MIB::adspTimeoutErrors,Counter32,read-only,,mandatory,,The number of times the ADSP on this entity detected an expired connection timer.
.1.3.6.1.2.1.13.13.8,APPLETALK-MIB::adspTimeoutCloseErrors,Counter32,read-only,,mandatory,,The number of times the ADSP on this entity closed a connection because of too many timeouts.
.1.3.6.1.2.1.13.13.9,APPLETALK-MIB::adspConnTable,,not-accessible,,mandatory,,A list of ADSP connections on this entity.
.1.3.6.1.2.1.13.13.9.1,APPLETALK-MIB::adspConnEntry,,not-accessible,adspConnLocalAddress:adspConnRemoteAddress:adspConnLocalConnID,mandatory,,A set of information describing an ADSP connection. As an example, an instance of the adspConnState object might be named adspConnState.0.80.220.7.0.80.239.142.31231
.1.3.6.1.2.1.13.13.9.1.1,APPLETALK-MIB::adspConnLocalAddress,OCTET,not-accessible,,mandatory,,The local DDP address of this ADSP connection.
.1.3.6.1.2.1.13.13.9.1.2,APPLETALK-MIB::adspConnLocalConnID,INTEGER,not-accessible,,mandatory,,The local Connection ID of this ADSP connection. If this entry specifies an ADSP listener, this value shall be zero.
.1.3.6.1.2.1.13.13.9.1.3,APPLETALK-MIB::adspConnRemoteAddress,OCTET,not-accessible,,mandatory,,The remote DDP address of this ADSP connection. If this entry specifies an ADSP listener, this value shall be zero.
.1.3.6.1.2.1.13.13.9.1.4,APPLETALK-MIB::adspConnRemoteConnID,INTEGER,read-only,,mandatory,,The remote Connection ID of this ADSP connection. If this entry specifies an ADSP listener, this value shall be zero.
.1.3.6.1.2.1.13.13.9.1.5,APPLETALK-MIB::adspConnState,INTEGER,read-write,,mandatory,open(1):localHalfOpen(2):remoteHalfOpen(3):listening(4):closed(5):invalid(6),The state of this ADSP connection. The state is open if both ends are established. If only one end is established, then the state is half-open. If neither end is established, then the state is closed. If an ADSP server is listening on a socket and is not yet connected, its state is set to listening, and the adspConnRemoteAddress, adspConnRemoteSocket, adspConnRemoteConnID, and adspConnRemoteWindowSize are all set to zero. Setting this object to the value invalid(6) has the effect of invalidating the corresponding entry in the adspConnTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant adspConnState object.
.1.3.6.1.2.1.13.14,APPLETALK-MIB::atportptop,,,,,,
.1.3.6.1.2.1.13.14.1,APPLETALK-MIB::atportPtoPTable,,not-accessible,,mandatory,,A list of AppleTalk point-to-point connections for this entity.
.1.3.6.1.2.1.13.14.1.1,APPLETALK-MIB::atportPtoPEntry,,not-accessible,atportPtoPIndex,mandatory,,The description of one of the AppleTalk point-to-point connections on this entity. As an example, an instance of the atportPtoPRemoteAddress object might be named atportPtoPRemoteAddress.2
.1.3.6.1.2.1.13.14.1.1.1,APPLETALK-MIB::atportPtoPIndex,INTEGER,not-accessible,,mandatory,,A unique value for each AppleTalk point-to-point connection. Its value is between 1 and the total number of AppleTalk point-to-point connections. The value for each connection must remain constant at least from the re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.13.14.1.1.2,APPLETALK-MIB::atportPtoPProtocol,OBJECT,read-write,,mandatory,,The protocol type used over the point-to-point connection.
.1.3.6.1.2.1.13.14.1.1.3,APPLETALK-MIB::atportPtoPRemoteName,OCTET,read-write,,mandatory,,A text string containing the network node name of the entity at the other end of the point-to-point link. If the name is unknown or undefined, then this string is zero length.
.1.3.6.1.2.1.13.14.1.1.4,APPLETALK-MIB::atportPtoPRemoteAddress,OCTET,read-write,,mandatory,,The network address of the entity at the other end of the point-to-point link in network byte order. The format of this address can be determined by examinating the atportType corresponding to this entry. If the address is unknown or undefined, then this string is zero length.
.1.3.6.1.2.1.13.14.1.1.5,APPLETALK-MIB::atportPtoPPortIndex,INTEGER,read-write,,mandatory,,The AppleTalk port associated with this point-to-point connection. The interface identified by a particular value of this index is the same interface as identified by the same value of atportIndex.
.1.3.6.1.2.1.13.14.1.1.6,APPLETALK-MIB::atportPtoPStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),The status of this entry in the atportPtoPTable. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the atportPtoPTable. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examinationr of the relevant atportPtoPStatus object.
.1.3.6.1.2.1.13.14.2,APPLETALK-MIB::atportPtoPProtoOids,,,,,,
.1.3.6.1.2.1.13.14.2.1,APPLETALK-MIB::pToPProtoOther,,,,,,
.1.3.6.1.2.1.13.14.2.2,APPLETALK-MIB::pToPProtoAurp,,,,,,
.1.3.6.1.2.1.13.14.2.3,APPLETALK-MIB::pToPProtoCaymanUdp,,,,,,
.1.3.6.1.2.1.13.14.2.4,APPLETALK-MIB::pToPProtoAtkvmsDecnetIV,,,,,,
.1.3.6.1.2.1.13.14.2.5,APPLETALK-MIB::pToPProtoLiaisonUdp,,,,,,
.1.3.6.1.2.1.13.14.2.6,APPLETALK-MIB::pToPProtoIpx,,,,,,
.1.3.6.1.2.1.13.14.2.7,APPLETALK-MIB::pToPProtoShivaIp,,,,,,
.1.3.6.1.2.1.13.16,APPLETALK-MIB::rtmpStub,,,,,,
.1.3.6.1.2.1.13.16.1,APPLETALK-MIB::rtmpOutRequestPkts,Counter32,read-only,,mandatory,,A count of the number of RTMP Request packets sent by this entity.
.1.3.6.1.2.1.13.16.2,APPLETALK-MIB::rtmpInVersionMismatches,Counter32,read-only,,mandatory,,A count of the number of RTMP packets received by this entity that were rejected due to a version mismatch.
.1.3.6.1.2.1.13.16.3,APPLETALK-MIB::rtmpInErrors,Counter32,read-only,,mandatory,,A count of the number of RTMP packets received by this entity that were rejected for an error other than version mismatch.
.1.3.6.1.2.1.13.17,APPLETALK-MIB::zipEndNode,,,,,,
.1.3.6.1.2.1.13.17.1,APPLETALK-MIB::zipNetInfoTable,,not-accessible,,mandatory,,The table of Net Info packets received by each port on this entity.
.1.3.6.1.2.1.13.17.1.1,APPLETALK-MIB::zipNetInfoEntry,,not-accessible,atportIndex,mandatory,,The description of the Net Info packets received on a particular port on this entity. One such entry shall exist for each atport on this entity. As an example, an instance of the zipOutGetNetInfos object might be named zipOutGetNetInfos.2
.1.3.6.1.2.1.13.17.1.1.1,APPLETALK-MIB::zipOutGetNetInfos,Counter32,read-only,,mandatory,,The number of ZIP GetNetInfo packets sent out this port by this entity.
.1.3.6.1.2.1.13.17.1.1.2,APPLETALK-MIB::zipInGetNetInfoReplies,Counter32,read-only,,mandatory,,The number of ZIP GetNetInfo Reply packets received on this port by this entity.
.1.3.6.1.2.1.13.17.1.1.3,APPLETALK-MIB::zipZoneInInvalids,Counter32,read-only,,mandatory,,The number of times this entity has received a ZIP GetNetInfo Reply with the zone invalid bit set because the corresponding GetNetInfo Request had an invalid zone name.
.1.3.6.1.2.1.13.17.2,APPLETALK-MIB::zipInErrors,Counter32,read-only,,mandatory,,The number of ZIP packets received by this entity that were rejected for any error.
.1.3.6.1.2.1.13.18,APPLETALK-MIB::perPort,,,,,,
.1.3.6.1.2.1.13.18.1,APPLETALK-MIB::perPortTable,,not-accessible,,mandatory,,The table of per-port statistics for this entity.
.1.3.6.1.2.1.13.18.1.1,APPLETALK-MIB::perPortEntry,,not-accessible,atportIndex,mandatory,,The statistics available for a particular port on this entity. As an example, an instance of the perPortAarpInProbes object might be named perPortAarpInProbes.2
.1.3.6.1.2.1.13.18.1.1.1,APPLETALK-MIB::perPortAarpInProbes,Counter32,read-only,,mandatory,,The total number of AARP Probe packets received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.2,APPLETALK-MIB::perPortAarpOutProbes,Counter32,read-only,,mandatory,,The total number of AARP Probe packets sent by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.3,APPLETALK-MIB::perPortAarpInReqs,Counter32,read-only,,mandatory,,The total number of AARP Request packets received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.4,APPLETALK-MIB::perPortAarpOutReqs,Counter32,read-only,,mandatory,,The total number of AARP Request packets sent by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.5,APPLETALK-MIB::perPortAarpInRsps,Counter32,read-only,,mandatory,,The total number of AARP Response packets received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.6,APPLETALK-MIB::perPortAarpOutRsps,Counter32,read-only,,mandatory,,The total number of AARP Response packets sent by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.7,APPLETALK-MIB::perPortDdpInReceives,Counter32,read-only,,mandatory,,The total number of input datagrams received by DDP on this port, including those received in error.
.1.3.6.1.2.1.13.18.1.1.8,APPLETALK-MIB::perPortDdpInLocalDatagrams,Counter32,read-only,,mandatory,,The total number of input DDP datagrams on this port for which this entity was their final DDP destination.
.1.3.6.1.2.1.13.18.1.1.9,APPLETALK-MIB::perPortDdpNoProtocolHandlers,Counter32,read-only,,mandatory,,The total number of DDP datagrams addressed to this entity on this port that were addressed to an upper layer protocol for which no protocol handler existed.
.1.3.6.1.2.1.13.18.1.1.10,APPLETALK-MIB::perPortDdpTooShortErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams on this port dropped because the received data length was less than the data length specified in the DDP header or the received data length was less than the length of the expected DDP header.
.1.3.6.1.2.1.13.18.1.1.11,APPLETALK-MIB::perPortDdpTooLongErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams on this port dropped because they exceeded the maximum DDP datagram size.
.1.3.6.1.2.1.13.18.1.1.12,APPLETALK-MIB::perPortDdpChecksumErrors,Counter32,read-only,,mandatory,,The total number of input DDP datagrams on this port for which this DDP entity was their final destination, and which were dropped because of a checksum error.
.1.3.6.1.2.1.13.18.1.1.13,APPLETALK-MIB::perPortDdpForwRequests,Counter32,read-only,,mandatory,,The number of input datagrams on this port for which this entity was not their final DDP destination, as a result of which an attempt was made to find a route to forward them to that final destination.
.1.3.6.1.2.1.13.18.1.1.14,APPLETALK-MIB::perPortRtmpInDataPkts,Counter32,read-only,,mandatory,,A count of the number of good RTMP data packets received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.15,APPLETALK-MIB::perPortRtmpOutDataPkts,Counter32,read-only,,mandatory,,A count of the number of RTMP packets sent by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.16,APPLETALK-MIB::perPortRtmpInRequestPkts,Counter32,read-only,,mandatory,,A count of the number of good RTMP Request packets received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.17,APPLETALK-MIB::perPortRtmpRouteDeletes,Counter32,read-only,,mandatory,,A count of the number of times RTMP deletes a route on this port because it was aged out of the table.
.1.3.6.1.2.1.13.18.1.1.18,APPLETALK-MIB::perPortZipInZipQueries,Counter32,read-only,,mandatory,,The number of ZIP Queries received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.19,APPLETALK-MIB::perPortZipInZipReplies,Counter32,read-only,,mandatory,,The number of ZIP Replies received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.20,APPLETALK-MIB::perPortZipInZipExtendedReplies,Counter32,read-only,,mandatory,,The number of ZIP Extended Replies received by this entity on this port.
.1.3.6.1.2.1.13.18.1.1.21,APPLETALK-MIB::perPortZipZoneConflictErrors,Counter32,read-only,,mandatory,,The number of times a conflict has been detected on this port between this entity's zone information and another entity's zone information.
.1.3.6.1.2.1.13.18.1.1.22,APPLETALK-MIB::perPortZipInErrors,Counter32,read-only,,mandatory,,The number of ZIP packets received by this entity on this port that were rejected for any error.
.1.3.6.1.2.1.13.18.1.1.23,APPLETALK-MIB::perPortNbpInLookUpRequests,Counter32,read-only,,mandatory,,The number of NBP LookUp Requests received on this port.
.1.3.6.1.2.1.13.18.1.1.24,APPLETALK-MIB::perPortNbpInLookUpReplies,Counter32,read-only,,mandatory,,The number of NBP LookUp Replies received on this port.
.1.3.6.1.2.1.13.18.1.1.25,APPLETALK-MIB::perPortNbpInBroadcastRequests,Counter32,read-only,,mandatory,,The number of NBP Broadcast Requests received on this port.
.1.3.6.1.2.1.13.18.1.1.26,APPLETALK-MIB::perPortNbpInForwardRequests,Counter32,read-only,,mandatory,,The number of NBP Forward Requests received on this port.
.1.3.6.1.2.1.13.18.1.1.27,APPLETALK-MIB::perPortNbpOutLookUpReplies,Counter32,read-only,,mandatory,,The number of NBP LookUp Replies sent on this port.
.1.3.6.1.2.1.13.18.1.1.28,APPLETALK-MIB::perPortNbpRegistrationFailures,Counter32,read-only,,mandatory,,The number of times this node experienced a failure in attempting to register an NBP entity on this port.
.1.3.6.1.2.1.13.18.1.1.29,APPLETALK-MIB::perPortNbpInErrors,Counter32,read-only,,mandatory,,The number of NBP packets received by this entity on this port that were rejected for any error.
.1.3.6.1.2.1.13.18.1.1.30,APPLETALK-MIB::perPortEchoRequests,Counter32,read-only,,mandatory,,The number of AppleTalk Echo requests received on this port.
.1.3.6.1.2.1.13.18.1.1.31,APPLETALK-MIB::perPortEchoReplies,Counter32,read-only,,mandatory,,The count of AppleTalk Echo replies received on this port.
.1.3.6.1.2.1.14,OSPF-MIB::ospf,,,,,,The MIB module to describe the OSPF Version 2 Protocol. Note that some objects in this MIB module may pose a significant security risk. Refer to the Security Considerations section in RFC 4750 for more information. Copyright (C) The IETF Trust (2006). This version of this MIB module is part of RFC 4750; see the RFC itself for full legal notices.
.1.3.6.1.2.1.14.1,OSPF-MIB::ospfGeneralGroup,,,,,,
.1.3.6.1.2.1.14.1.1,OSPF-MIB::ospfRouterId,IpAddress,read-write,,current,,A 32-bit integer uniquely identifying the router in the Autonomous System. By convention, to ensure uniqueness, this should default to the value of one of the router's IP interface addresses. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.2,OSPF-MIB::ospfAdminStat,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative status of OSPF in the router. The value 'enabled' denotes that the OSPF Process is active on at least one interface; 'disabled' disables it on all interfaces. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.3,OSPF-MIB::ospfVersionNumber,INTEGER,read-only,,current,version2(2),The current version number of the OSPF protocol is 2.
.1.3.6.1.2.1.14.1.4,OSPF-MIB::ospfAreaBdrRtrStatus,INTEGER,read-only,,current,true(1):false(2),A flag to note whether this router is an Area Border Router.
.1.3.6.1.2.1.14.1.5,OSPF-MIB::ospfASBdrRtrStatus,INTEGER,read-write,,current,true(1):false(2),A flag to note whether this router is configured as an Autonomous System Border Router. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.6,OSPF-MIB::ospfExternLsaCount,Gauge32,read-only,,current,,The number of external (LS type-5) link state advertisements in the link state database.
.1.3.6.1.2.1.14.1.7,OSPF-MIB::ospfExternLsaCksumSum,Integer32,read-only,,current,,The 32-bit sum of the LS checksums of the external link state advertisements contained in the link state database. This sum can be used to determine if there has been a change in a router's link state database and to compare the link state database of two routers. The value should be treated as unsigned when comparing two sums of checksums.
.1.3.6.1.2.1.14.1.8,OSPF-MIB::ospfTOSSupport,INTEGER,read-write,,current,true(1):false(2),The router's support for type-of-service routing. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.9,OSPF-MIB::ospfOriginateNewLsas,Counter32,read-only,,current,,The number of new link state advertisements that have been originated. This number is incremented each time the router originates a new LSA. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.1.10,OSPF-MIB::ospfRxNewLsas,Counter32,read-only,,current,,The number of link state advertisements received that are determined to be new instantiations. This number does not include newer instantiations of self-originated link state advertisements. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.1.11,OSPF-MIB::ospfExtLsdbLimit,Integer32,read-write,,current,,The maximum number of non-default AS-external LSAs entries that can be stored in the link state database. If the value is -1, then there is no limit. When the number of non-default AS-external LSAs in a router's link state database reaches ospfExtLsdbLimit, the router enters overflow state. The router never holds more than ospfExtLsdbLimit non-default AS-external LSAs in its database. OspfExtLsdbLimit MUST be set identically in all routers attached to the OSPF backbone and/or any regular OSPF area (i.e., OSPF stub areas and NSSAs are excluded). This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.12,OSPF-MIB::ospfMulticastExtensions,Integer32,read-write,,current,,A bit mask indicating whether the router is forwarding IP multicast (Class D) datagrams based on the algorithms defined in the multicast extensions to OSPF. Bit 0, if set, indicates that the router can forward IP multicast datagrams in the router's directly attached areas (called intra-area multicast routing). Bit 1, if set, indicates that the router can forward IP multicast datagrams between OSPF areas (called inter-area multicast routing). Bit 2, if set, indicates that the router can forward IP multicast datagrams between Autonomous Systems (called inter-AS multicast routing). Only certain combinations of bit settings are allowed, namely: 0 (no multicast forwarding is enabled), 1 (intra-area multicasting only), 3 (intra-area and inter-area multicasting), 5 (intra-area and inter-AS multicasting), and 7 (multicasting everywhere). By default, no multicast forwarding is enabled. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.13,OSPF-MIB::ospfExitOverflowInterval,Integer32,read-write,,current,,The number of seconds that, after entering OverflowState, a router will attempt to leave OverflowState. This allows the router to again originate non-default AS-external LSAs. When set to 0, the router will not leave overflow state until restarted. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.14,OSPF-MIB::ospfDemandExtensions,INTEGER,read-write,,current,true(1):false(2),The router's support for demand routing. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.15,OSPF-MIB::ospfRFC1583Compatibility,INTEGER,read-write,,current,true(1):false(2),Indicates metrics used to choose among multiple AS-external LSAs. When RFC1583Compatibility is set to enabled, only cost will be used when choosing among multiple AS-external LSAs advertising the same destination. When RFC1583Compatibility is set to disabled, preference will be driven first by type of path using cost only to break ties. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.16,OSPF-MIB::ospfOpaqueLsaSupport,INTEGER,read-only,,current,true(1):false(2),The router's support for Opaque LSA types.
.1.3.6.1.2.1.14.1.17,OSPF-MIB::ospfReferenceBandwidth,Unsigned32,read-write,,current,,Reference bandwidth in kilobits/second for calculating default interface metrics. The default value is 100,000 KBPS (100 MBPS). This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.18,OSPF-MIB::ospfRestartSupport,INTEGER,read-write,,current,none(1):plannedOnly(2):plannedAndUnplanned(3),The router's support for OSPF graceful restart. Options include: no restart support, only planned restarts, or both planned and unplanned restarts. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.19,OSPF-MIB::ospfRestartInterval,Integer32,read-write,,current,,Configured OSPF graceful restart timeout interval. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.20,OSPF-MIB::ospfRestartStrictLsaChecking,INTEGER,read-write,,current,true(1):false(2),Indicates if strict LSA checking is enabled for graceful restart. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.21,OSPF-MIB::ospfRestartStatus,INTEGER,read-only,,current,notRestarting(1):plannedRestart(2):unplannedRestart(3),Current status of OSPF graceful restart.
.1.3.6.1.2.1.14.1.22,OSPF-MIB::ospfRestartAge,Unsigned32,read-only,,current,,Remaining time in current OSPF graceful restart interval.
.1.3.6.1.2.1.14.1.23,OSPF-MIB::ospfRestartExitReason,INTEGER,read-only,,current,none(1):inProgress(2):completed(3):timedOut(4):topologyChanged(5),Describes the outcome of the last attempt at a graceful restart. If the value is 'none', no restart has yet been attempted. If the value is 'inProgress', a restart attempt is currently underway.
.1.3.6.1.2.1.14.1.24,OSPF-MIB::ospfAsLsaCount,Gauge32,read-only,,current,,The number of AS-scope link state advertisements in the AS-scope link state database.
.1.3.6.1.2.1.14.1.25,OSPF-MIB::ospfAsLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the LS checksums of the AS link state advertisements contained in the AS-scope link state database. This sum can be used to determine if there has been a change in a router's AS-scope link state database, and to compare the AS-scope link state database of two routers.
.1.3.6.1.2.1.14.1.26,OSPF-MIB::ospfStubRouterSupport,INTEGER,read-only,,current,true(1):false(2),The router's support for stub router functionality.
.1.3.6.1.2.1.14.1.27,OSPF-MIB::ospfStubRouterAdvertisement,INTEGER,read-write,,current,doNotAdvertise(1):advertise(2),This object controls the advertisement of stub router LSAs by the router. The value doNotAdvertise will result in the advertisement of a standard router LSA and is the default value. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.1.28,OSPF-MIB::ospfDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one of this MIB's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.14.2,OSPF-MIB::ospfAreaTable,,not-accessible,,current,,Information describing the configured parameters and cumulative statistics of the router's attached areas. The interfaces and virtual links are configured as part of these areas. Area 0.0.0.0, by definition, is the backbone area.
.1.3.6.1.2.1.14.2.1,OSPF-MIB::ospfAreaEntry,,not-accessible,ospfAreaId,current,,Information describing the configured parameters and cumulative statistics of one of the router's attached areas. The interfaces and virtual links are configured as part of these areas. Area 0.0.0.0, by definition, is the backbone area. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.2.1.1,OSPF-MIB::ospfAreaId,IpAddress,read-only,,current,,A 32-bit integer uniquely identifying an area. Area ID 0.0.0.0 is used for the OSPF backbone.
.1.3.6.1.2.1.14.2.1.2,OSPF-MIB::ospfAuthType,INTEGER,read-create,,obsolete,none(0):simplePassword(1):md5(2),The authentication type specified for an area.
.1.3.6.1.2.1.14.2.1.3,OSPF-MIB::ospfImportAsExtern,INTEGER,read-create,,current,importExternal(1):importNoExternal(2):importNssa(3),Indicates if an area is a stub area, NSSA, or standard area. Type-5 AS-external LSAs and type-11 Opaque LSAs are not imported into stub areas or NSSAs. NSSAs import AS-external data as type-7 LSAs
.1.3.6.1.2.1.14.2.1.4,OSPF-MIB::ospfSpfRuns,Counter32,read-only,,current,,The number of times that the intra-area route table has been calculated using this area's link state database. This is typically done using Dijkstra's algorithm. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.2.1.5,OSPF-MIB::ospfAreaBdrRtrCount,Gauge32,read-only,,current,,The total number of Area Border Routers reachable within this area. This is initially zero and is calculated in each Shortest Path First (SPF) pass.
.1.3.6.1.2.1.14.2.1.6,OSPF-MIB::ospfAsBdrRtrCount,Gauge32,read-only,,current,,The total number of Autonomous System Border Routers reachable within this area. This is initially zero and is calculated in each SPF pass.
.1.3.6.1.2.1.14.2.1.7,OSPF-MIB::ospfAreaLsaCount,Gauge32,read-only,,current,,The total number of link state advertisements in this area's link state database, excluding AS-external LSAs.
.1.3.6.1.2.1.14.2.1.8,OSPF-MIB::ospfAreaLsaCksumSum,Integer32,read-only,,current,,The 32-bit sum of the link state advertisements' LS checksums contained in this area's link state database. This sum excludes external (LS type-5) link state advertisements. The sum can be used to determine if there has been a change in a router's link state database, and to compare the link state database of two routers. The value should be treated as unsigned when comparing two sums of checksums.
.1.3.6.1.2.1.14.2.1.9,OSPF-MIB::ospfAreaSummary,INTEGER,read-create,,current,noAreaSummary(1):sendAreaSummary(2),The variable ospfAreaSummary controls the import of summary LSAs into stub and NSSA areas. It has no effect on other areas. If it is noAreaSummary, the router will not originate summary LSAs into the stub or NSSA area. It will rely entirely on its default route. If it is sendAreaSummary, the router will both summarize and propagate summary LSAs.
.1.3.6.1.2.1.14.2.1.10,OSPF-MIB::ospfAreaStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.2.1.11,OSPF-MIB::ospfAreaNssaTranslatorRole,INTEGER,read-create,,current,always(1):candidate(2),Indicates an NSSA border router's ability to perform NSSA translation of type-7 LSAs into type-5 LSAs.
.1.3.6.1.2.1.14.2.1.12,OSPF-MIB::ospfAreaNssaTranslatorState,INTEGER,read-only,,current,enabled(1):elected(2):disabled(3),Indicates if and how an NSSA border router is performing NSSA translation of type-7 LSAs into type-5 LSAs. When this object is set to enabled, the NSSA Border router's OspfAreaNssaExtTranslatorRole has been set to always. When this object is set to elected, a candidate NSSA Border router is Translating type-7 LSAs into type-5. When this object is set to disabled, a candidate NSSA border router is NOT translating type-7 LSAs into type-5.
.1.3.6.1.2.1.14.2.1.13,OSPF-MIB::ospfAreaNssaTranslatorStabilityInterval,Integer32,read-create,,current,,The number of seconds after an elected translator determines its services are no longer required, that it should continue to perform its translation duties.
.1.3.6.1.2.1.14.2.1.14,OSPF-MIB::ospfAreaNssaTranslatorEvents,Counter32,read-only,,current,,Indicates the number of translator state changes that have occurred since the last boot-up. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.3,OSPF-MIB::ospfStubAreaTable,,not-accessible,,current,,The set of metrics that will be advertised by a default Area Border Router into a stub area.
.1.3.6.1.2.1.14.3.1,OSPF-MIB::ospfStubAreaEntry,,not-accessible,ospfStubAreaId:ospfStubTOS,current,,The metric for a given Type of Service that will be advertised by a default Area Border Router into a stub area. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.3.1.1,OSPF-MIB::ospfStubAreaId,IpAddress,read-only,,current,,The 32-bit identifier for the stub area. On creation, this can be derived from the instance.
.1.3.6.1.2.1.14.3.1.2,OSPF-MIB::ospfStubTOS,Integer32,read-only,,current,,The Type of Service associated with the metric. On creation, this can be derived from the instance.
.1.3.6.1.2.1.14.3.1.3,OSPF-MIB::ospfStubMetric,Integer32,read-create,,current,,The metric value applied at the indicated Type of Service. By default, this equals the least metric at the Type of Service among the interfaces to other areas.
.1.3.6.1.2.1.14.3.1.4,OSPF-MIB::ospfStubStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.3.1.5,OSPF-MIB::ospfStubMetricType,INTEGER,read-create,,current,ospfMetric(1):comparableCost(2):nonComparable(3),This variable displays the type of metric advertised as a default route.
.1.3.6.1.2.1.14.4,OSPF-MIB::ospfLsdbTable,,not-accessible,,current,,The OSPF Process's link state database (LSDB). The LSDB contains the link state advertisements from throughout the areas that the device is attached to.
.1.3.6.1.2.1.14.4.1,OSPF-MIB::ospfLsdbEntry,,not-accessible,ospfLsdbAreaId:ospfLsdbType:ospfLsdbLsid:ospfLsdbRouterId,current,,A single link state advertisement.
.1.3.6.1.2.1.14.4.1.1,OSPF-MIB::ospfLsdbAreaId,IpAddress,read-only,,current,,The 32-bit identifier of the area from which the LSA was received.
.1.3.6.1.2.1.14.4.1.2,OSPF-MIB::ospfLsdbType,INTEGER,read-only,,current,routerLink(1):networkLink(2):summaryLink(3):asSummaryLink(4):asExternalLink(5):multicastLink(6):nssaExternalLink(7):areaOpaqueLink(10),The type of the link state advertisement. Each link state type has a separate advertisement format. Note: External link state advertisements are permitted for backward compatibility, but should be displayed in the ospfAsLsdbTable rather than here.
.1.3.6.1.2.1.14.4.1.3,OSPF-MIB::ospfLsdbLsid,IpAddress,read-only,,current,,The Link State ID is an LS Type Specific field containing either a Router ID or an IP address; it identifies the piece of the routing domain that is being described by the advertisement.
.1.3.6.1.2.1.14.4.1.4,OSPF-MIB::ospfLsdbRouterId,IpAddress,read-only,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.14.4.1.5,OSPF-MIB::ospfLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It starts with the value '80000001'h, or -'7FFFFFFF'h, and increments until '7FFFFFFF'h. Thus, a typical sequence number will be very negative. It is used to detect old and duplicate Link State Advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.14.4.1.6,OSPF-MIB::ospfLsdbAge,Integer32,read-only,,current,,This field is the age of the link state advertisement in seconds.
.1.3.6.1.2.1.14.4.1.7,OSPF-MIB::ospfLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.14.4.1.8,OSPF-MIB::ospfLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header. Note that for variable length LSAs, SNMP agents may not be able to return the largest string size.
.1.3.6.1.2.1.14.5,OSPF-MIB::ospfAreaRangeTable,,not-accessible,,obsolete,,The Address Range Table acts as an adjunct to the Area Table. It describes those Address Range Summaries that are configured to be propagated from an Area to reduce the amount of information about it that is known beyond its borders. It contains a set of IP address ranges specified by an IP address/IP network mask pair. For example, class B address range of X.X.X.X with a network mask of 255.255.0.0 includes all IP addresses from X.X.0.0 to X.X.255.255. Note that this table is obsoleted and is replaced by the Area Aggregate Table.
.1.3.6.1.2.1.14.5.1,OSPF-MIB::ospfAreaRangeEntry,,not-accessible,ospfAreaRangeAreaId:ospfAreaRangeNet,obsolete,,A single area address range. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.5.1.1,OSPF-MIB::ospfAreaRangeAreaId,IpAddress,read-only,,obsolete,,The area that the address range is to be found within.
.1.3.6.1.2.1.14.5.1.2,OSPF-MIB::ospfAreaRangeNet,IpAddress,read-only,,obsolete,,The IP address of the net or subnet indicated by the range.
.1.3.6.1.2.1.14.5.1.3,OSPF-MIB::ospfAreaRangeMask,IpAddress,read-create,,obsolete,,The subnet mask that pertains to the net or subnet.
.1.3.6.1.2.1.14.5.1.4,OSPF-MIB::ospfAreaRangeStatus,INTEGER,read-create,,obsolete,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.5.1.5,OSPF-MIB::ospfAreaRangeEffect,INTEGER,read-create,,obsolete,advertiseMatching(1):doNotAdvertiseMatching(2),Subnets subsumed by ranges either trigger the advertisement of the indicated summary (advertiseMatching) or result in the subnet's not being advertised at all outside the area.
.1.3.6.1.2.1.14.6,OSPF-MIB::ospfHostTable,,not-accessible,,current,,The Host/Metric Table indicates what hosts are directly attached to the router, what metrics and types of service should be advertised for them, and what areas they are found within.
.1.3.6.1.2.1.14.6.1,OSPF-MIB::ospfHostEntry,,not-accessible,ospfHostIpAddress:ospfHostTOS,current,,A metric to be advertised, for a given type of service, when a given host is reachable. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.6.1.1,OSPF-MIB::ospfHostIpAddress,IpAddress,read-only,,current,,The IP address of the host.
.1.3.6.1.2.1.14.6.1.2,OSPF-MIB::ospfHostTOS,Integer32,read-only,,current,,The Type of Service of the route being configured.
.1.3.6.1.2.1.14.6.1.3,OSPF-MIB::ospfHostMetric,Integer32,read-create,,current,,The metric to be advertised.
.1.3.6.1.2.1.14.6.1.4,OSPF-MIB::ospfHostStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.6.1.5,OSPF-MIB::ospfHostAreaID,IpAddress,read-only,,deprecated,,The OSPF area to which the host belongs. Deprecated by ospfHostCfgAreaID.
.1.3.6.1.2.1.14.6.1.6,OSPF-MIB::ospfHostCfgAreaID,IpAddress,read-create,,current,,To configure the OSPF area to which the host belongs.
.1.3.6.1.2.1.14.7,OSPF-MIB::ospfIfTable,,not-accessible,,current,,The OSPF Interface Table describes the interfaces from the viewpoint of OSPF. It augments the ipAddrTable with OSPF specific information.
.1.3.6.1.2.1.14.7.1,OSPF-MIB::ospfIfEntry,,not-accessible,ospfIfIpAddress:ospfAddressLessIf,current,,The OSPF interface entry describes one interface from the viewpoint of OSPF. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.7.1.1,OSPF-MIB::ospfIfIpAddress,IpAddress,read-only,,current,,The IP address of this OSPF interface.
.1.3.6.1.2.1.14.7.1.2,OSPF-MIB::ospfAddressLessIf,Integer32,read-only,,current,,For the purpose of easing the instancing of addressed and addressless interfaces; this variable takes the value 0 on interfaces with IP addresses and the corresponding value of ifIndex for interfaces having no IP address.
.1.3.6.1.2.1.14.7.1.3,OSPF-MIB::ospfIfAreaId,IpAddress,read-create,,current,,A 32-bit integer uniquely identifying the area to which the interface connects. Area ID 0.0.0.0 is used for the OSPF backbone.
.1.3.6.1.2.1.14.7.1.4,OSPF-MIB::ospfIfType,INTEGER,read-create,,current,broadcast(1):nbma(2):pointToPoint(3):pointToMultipoint(5),The OSPF interface type. By way of a default, this field may be intuited from the corresponding value of ifType. Broadcast LANs, such as Ethernet and IEEE 802.5, take the value 'broadcast', X.25 and similar technologies take the value 'nbma', and links that are definitively point to point take the value 'pointToPoint'.
.1.3.6.1.2.1.14.7.1.5,OSPF-MIB::ospfIfAdminStat,INTEGER,read-create,,current,enabled(1):disabled(2),The OSPF interface's administrative status. The value formed on the interface, and the interface will be advertised as an internal route to some area. The value 'disabled' denotes that the interface is external to OSPF.
.1.3.6.1.2.1.14.7.1.6,OSPF-MIB::ospfIfRtrPriority,Integer32,read-create,,current,,The priority of this interface. Used in multi-access networks, this field is used in the designated router election algorithm. The value 0 signifies that the router is not eligible to become the designated router on this particular network. In the event of a tie in this value, routers will use their Router ID as a tie breaker.
.1.3.6.1.2.1.14.7.1.7,OSPF-MIB::ospfIfTransitDelay,Integer32,read-create,,current,,The estimated number of seconds it takes to transmit a link state update packet over this interface. Note that the minimal value SHOULD be 1 second.
.1.3.6.1.2.1.14.7.1.8,OSPF-MIB::ospfIfRetransInterval,Integer32,read-create,,current,,The number of seconds between link state advertisement retransmissions, for adjacencies belonging to this interface. This value is also used when retransmitting database description and Link State request packets. Note that minimal value SHOULD be 1 second.
.1.3.6.1.2.1.14.7.1.9,OSPF-MIB::ospfIfHelloInterval,Integer32,read-create,,current,,The length of time, in seconds, between the Hello packets that the router sends on the interface. This value must be the same for all routers attached to a common network.
.1.3.6.1.2.1.14.7.1.10,OSPF-MIB::ospfIfRtrDeadInterval,Integer32,read-create,,current,,The number of seconds that a router's Hello packets have not been seen before its neighbors declare the router down. This should be some multiple of the Hello interval. This value must be the same for all routers attached to a common network.
.1.3.6.1.2.1.14.7.1.11,OSPF-MIB::ospfIfPollInterval,Integer32,read-create,,current,,The larger time interval, in seconds, between the Hello packets sent to an inactive non-broadcast multi-access neighbor.
.1.3.6.1.2.1.14.7.1.12,OSPF-MIB::ospfIfState,INTEGER,read-only,,current,down(1):loopback(2):waiting(3):pointToPoint(4):designatedRouter(5):backupDesignatedRouter(6):otherDesignatedRouter(7),The OSPF Interface State.
.1.3.6.1.2.1.14.7.1.13,OSPF-MIB::ospfIfDesignatedRouter,IpAddress,read-only,,current,,The IP address of the designated router.
.1.3.6.1.2.1.14.7.1.14,OSPF-MIB::ospfIfBackupDesignatedRouter,IpAddress,read-only,,current,,The IP address of the backup designated router.
.1.3.6.1.2.1.14.7.1.15,OSPF-MIB::ospfIfEvents,Counter32,read-only,,current,,The number of times this OSPF interface has changed its state or an error has occurred. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.7.1.16,OSPF-MIB::ospfIfAuthKey,OCTET,read-create,,current,,The cleartext password used as an OSPF authentication key when simplePassword security is enabled. This object does not access any OSPF cryptogaphic (e.g., MD5) authentication key under any circumstance. If the key length is shorter than 8 octets, the agent will left adjust and zero fill to 8 octets. Unauthenticated interfaces need no authentication key, and simple password authentication cannot use a key of more than 8 octets. Note that the use of simplePassword authentication is NOT recommended when there is concern regarding attack upon the OSPF system. SimplePassword authentication is only sufficient to protect against accidental misconfigurations because it re-uses cleartext passwords [RFC1704]. When read, ospfIfAuthKey always returns an octet string of length zero.
.1.3.6.1.2.1.14.7.1.17,OSPF-MIB::ospfIfStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.7.1.18,OSPF-MIB::ospfIfMulticastForwarding,INTEGER,read-create,,current,blocked(1):multicast(2):unicast(3),The way multicasts should be forwarded on this interface: not forwarded, forwarded as data link multicasts, or forwarded as data link unicasts. Data link multicasting is not meaningful on point-to-point and NBMA interfaces, and setting ospfMulticastForwarding to 0 effectively disables all multicast forwarding.
.1.3.6.1.2.1.14.7.1.19,OSPF-MIB::ospfIfDemand,INTEGER,read-create,,current,true(1):false(2),Indicates whether Demand OSPF procedures (hello suppression to FULL neighbors and setting the DoNotAge flag on propagated LSAs) should be performed on this interface.
.1.3.6.1.2.1.14.7.1.20,OSPF-MIB::ospfIfAuthType,INTEGER,read-create,,current,none(0):simplePassword(1):md5(2),The authentication type specified for an interface. Note that this object can be used to engage in significant attacks against an OSPF router.
.1.3.6.1.2.1.14.7.1.21,OSPF-MIB::ospfIfLsaCount,Gauge32,read-only,,current,,The total number of link-local link state advertisements in this interface's link-local link state database.
.1.3.6.1.2.1.14.7.1.22,OSPF-MIB::ospfIfLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the Link State Advertisements' LS checksums contained in this interface's link-local link state database. The sum can be used to determine if there has been a change in the interface's link state database and to compare the interface link state database of routers attached to the same subnet.
.1.3.6.1.2.1.14.7.1.23,OSPF-MIB::ospfIfDesignatedRouterId,IpAddress,read-only,,current,,The Router ID of the designated router.
.1.3.6.1.2.1.14.7.1.24,OSPF-MIB::ospfIfBackupDesignatedRouterId,IpAddress,read-only,,current,,The Router ID of the backup designated router.
.1.3.6.1.2.1.14.8,OSPF-MIB::ospfIfMetricTable,,not-accessible,,current,,The Metric Table describes the metrics to be advertised for a specified interface at the various types of service. As such, this table is an adjunct of the OSPF Interface Table. Types of service, as defined by RFC 791, have the ability to request low delay, high bandwidth, or reliable linkage. For the purposes of this specification, the measure of bandwidth: Metric = referenceBandwidth / ifSpeed is the default value. The default reference bandwidth is 10^8. For multiple link interfaces, note that ifSpeed is the sum of the individual link speeds. This yields a number having the following typical values: Network Type/bit rate Metric >= 100 MBPS 1 Ethernet/802.3 10 E1 48 T1 (ESF) 65 64 KBPS 1562 56 KBPS 1785 19.2 KBPS 5208 9.6 KBPS 10416 Routes that are not specified use the default (TOS 0) metric. Note that the default reference bandwidth can be configured using the general group object ospfReferenceBandwidth.
.1.3.6.1.2.1.14.8.1,OSPF-MIB::ospfIfMetricEntry,,not-accessible,ospfIfMetricIpAddress:ospfIfMetricAddressLessIf:ospfIfMetricTOS,current,,A particular TOS metric for a non-virtual interface identified by the interface index. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.8.1.1,OSPF-MIB::ospfIfMetricIpAddress,IpAddress,read-only,,current,,The IP address of this OSPF interface. On row creation, this can be derived from the instance.
.1.3.6.1.2.1.14.8.1.2,OSPF-MIB::ospfIfMetricAddressLessIf,Integer32,read-only,,current,,For the purpose of easing the instancing of addressed and addressless interfaces; this variable takes the value 0 on interfaces with IP addresses and the value of ifIndex for interfaces having no IP address. On row creation, this can be derived from the instance.
.1.3.6.1.2.1.14.8.1.3,OSPF-MIB::ospfIfMetricTOS,Integer32,read-only,,current,,The Type of Service metric being referenced. On row creation, this can be derived from the instance.
.1.3.6.1.2.1.14.8.1.4,OSPF-MIB::ospfIfMetricValue,Integer32,read-create,,current,,The metric of using this Type of Service on this interface. The default value of the TOS 0 metric is 10^8 / ifSpeed.
.1.3.6.1.2.1.14.8.1.5,OSPF-MIB::ospfIfMetricStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.9,OSPF-MIB::ospfVirtIfTable,,not-accessible,,current,,Information about this router's virtual interfaces that the OSPF Process is configured to carry on.
.1.3.6.1.2.1.14.9.1,OSPF-MIB::ospfVirtIfEntry,,not-accessible,ospfVirtIfAreaId:ospfVirtIfNeighbor,current,,Information about a single virtual interface. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.9.1.1,OSPF-MIB::ospfVirtIfAreaId,IpAddress,read-only,,current,,The transit area that the virtual link traverses. By definition, this is not 0.0.0.0.
.1.3.6.1.2.1.14.9.1.2,OSPF-MIB::ospfVirtIfNeighbor,IpAddress,read-only,,current,,The Router ID of the virtual neighbor.
.1.3.6.1.2.1.14.9.1.3,OSPF-MIB::ospfVirtIfTransitDelay,Integer32,read-create,,current,,The estimated number of seconds it takes to transmit a Link State update packet over this interface. Note that the minimal value SHOULD be 1 second.
.1.3.6.1.2.1.14.9.1.4,OSPF-MIB::ospfVirtIfRetransInterval,Integer32,read-create,,current,,The number of seconds between link state avertisement retransmissions, for adjacencies belonging to this interface. This value is also used when retransmitting database description and Link State request packets. This value should be well over the expected round-trip time. Note that the minimal value SHOULD be 1 second.
.1.3.6.1.2.1.14.9.1.5,OSPF-MIB::ospfVirtIfHelloInterval,Integer32,read-create,,current,,The length of time, in seconds, between the Hello packets that the router sends on the interface. This value must be the same for the virtual neighbor.
.1.3.6.1.2.1.14.9.1.6,OSPF-MIB::ospfVirtIfRtrDeadInterval,Integer32,read-create,,current,,The number of seconds that a router's Hello packets have not been seen before its neighbors declare the router down. This should be some multiple of the Hello interval. This value must be the same for the virtual neighbor.
.1.3.6.1.2.1.14.9.1.7,OSPF-MIB::ospfVirtIfState,INTEGER,read-only,,current,down(1):pointToPoint(4),OSPF virtual interface states.
.1.3.6.1.2.1.14.9.1.8,OSPF-MIB::ospfVirtIfEvents,Counter32,read-only,,current,,The number of state changes or error events on this virtual link. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.9.1.9,OSPF-MIB::ospfVirtIfAuthKey,OCTET,read-create,,current,,The cleartext password used as an OSPF authentication key when simplePassword security is enabled. This object does not access any OSPF cryptogaphic (e.g., MD5) authentication key under any circumstance. If the key length is shorter than 8 octets, the agent will left adjust and zero fill to 8 octets. Unauthenticated interfaces need no authentication key, and simple password authentication cannot use a key of more than 8 octets. Note that the use of simplePassword authentication is NOT recommended when there is concern regarding attack upon the OSPF system. SimplePassword authentication is only sufficient to protect against accidental misconfigurations because it re-uses cleartext passwords. [RFC1704] When read, ospfIfAuthKey always returns an octet string of length zero.
.1.3.6.1.2.1.14.9.1.10,OSPF-MIB::ospfVirtIfStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.9.1.11,OSPF-MIB::ospfVirtIfAuthType,INTEGER,read-create,,current,none(0):simplePassword(1):md5(2),The authentication type specified for a virtual interface. Note that this object can be used to engage in significant attacks against an OSPF router.
.1.3.6.1.2.1.14.9.1.12,OSPF-MIB::ospfVirtIfLsaCount,Gauge32,read-only,,current,,The total number of link-local link state advertisements in this virtual interface's link-local link state database.
.1.3.6.1.2.1.14.9.1.13,OSPF-MIB::ospfVirtIfLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the link state advertisements' LS checksums contained in this virtual interface's link-local link state database. The sum can be used to determine if there has been a change in the virtual interface's link state database, and to compare the virtual interface link state database of the virtual neighbors.
.1.3.6.1.2.1.14.10,OSPF-MIB::ospfNbrTable,,not-accessible,,current,,A table describing all non-virtual neighbors in the locality of the OSPF router.
.1.3.6.1.2.1.14.10.1,OSPF-MIB::ospfNbrEntry,,not-accessible,ospfNbrIpAddr:ospfNbrAddressLessIndex,current,,The information regarding a single neighbor. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.10.1.1,OSPF-MIB::ospfNbrIpAddr,IpAddress,read-only,,current,,The IP address this neighbor is using in its IP source address. Note that, on addressless links, this will not be 0.0.0.0 but the address of another of the neighbor's interfaces.
.1.3.6.1.2.1.14.10.1.2,OSPF-MIB::ospfNbrAddressLessIndex,Integer32,read-only,,current,,On an interface having an IP address, zero. On addressless interfaces, the corresponding value of ifIndex in the Internet Standard MIB. On row creation, this can be derived from the instance.
.1.3.6.1.2.1.14.10.1.3,OSPF-MIB::ospfNbrRtrId,IpAddress,read-only,,current,,A 32-bit integer (represented as a type IpAddress) uniquely identifying the neighboring router in the Autonomous System.
.1.3.6.1.2.1.14.10.1.4,OSPF-MIB::ospfNbrOptions,Integer32,read-only,,current,,A bit mask corresponding to the neighbor's options field. Bit 0, if set, indicates that the system will operate on Type of Service metrics other than TOS 0. If zero, the neighbor will ignore all metrics except the TOS 0 metric. Bit 1, if set, indicates that the associated area accepts and operates on external information; if zero, it is a stub area. Bit 2, if set, indicates that the system is capable of routing IP multicast datagrams, that is that it implements the multicast extensions to OSPF. Bit 3, if set, indicates that the associated area is an NSSA. These areas are capable of carrying type-7 external advertisements, which are translated into type-5 external advertisements at NSSA borders.
.1.3.6.1.2.1.14.10.1.5,OSPF-MIB::ospfNbrPriority,Integer32,read-create,,current,,The priority of this neighbor in the designated router election algorithm. The value 0 signifies that the neighbor is not eligible to become the designated router on this particular network.
.1.3.6.1.2.1.14.10.1.6,OSPF-MIB::ospfNbrState,INTEGER,read-only,,current,down(1):attempt(2):init(3):twoWay(4):exchangeStart(5):exchange(6):loading(7):full(8),The state of the relationship with this neighbor.
.1.3.6.1.2.1.14.10.1.7,OSPF-MIB::ospfNbrEvents,Counter32,read-only,,current,,The number of times this neighbor relationship has changed state or an error has occurred. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.10.1.8,OSPF-MIB::ospfNbrLsRetransQLen,Gauge32,read-only,,current,,The current length of the retransmission queue.
.1.3.6.1.2.1.14.10.1.9,OSPF-MIB::ospfNbmaNbrStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.10.1.10,OSPF-MIB::ospfNbmaNbrPermanence,INTEGER,read-only,,current,dynamic(1):permanent(2),This variable displays the status of the entry; 'dynamic' and 'permanent' refer to how the neighbor became known.
.1.3.6.1.2.1.14.10.1.11,OSPF-MIB::ospfNbrHelloSuppressed,INTEGER,read-only,,current,true(1):false(2),Indicates whether Hellos are being suppressed to the neighbor.
.1.3.6.1.2.1.14.10.1.12,OSPF-MIB::ospfNbrRestartHelperStatus,INTEGER,read-only,,current,notHelping(1):helping(2),Indicates whether the router is acting as a graceful restart helper for the neighbor.
.1.3.6.1.2.1.14.10.1.13,OSPF-MIB::ospfNbrRestartHelperAge,Unsigned32,read-only,,current,,Remaining time in current OSPF graceful restart interval, if the router is acting as a restart helper for the neighbor.
.1.3.6.1.2.1.14.10.1.14,OSPF-MIB::ospfNbrRestartHelperExitReason,INTEGER,read-only,,current,none(1):inProgress(2):completed(3):timedOut(4):topologyChanged(5),Describes the outcome of the last attempt at acting as a graceful restart helper for the neighbor.
.1.3.6.1.2.1.14.11,OSPF-MIB::ospfVirtNbrTable,,not-accessible,,current,,This table describes all virtual neighbors. Since virtual links are configured in the Virtual Interface Table, this table is read-only.
.1.3.6.1.2.1.14.11.1,OSPF-MIB::ospfVirtNbrEntry,,not-accessible,ospfVirtNbrArea:ospfVirtNbrRtrId,current,,Virtual neighbor information.
.1.3.6.1.2.1.14.11.1.1,OSPF-MIB::ospfVirtNbrArea,IpAddress,read-only,,current,,The Transit Area Identifier.
.1.3.6.1.2.1.14.11.1.2,OSPF-MIB::ospfVirtNbrRtrId,IpAddress,read-only,,current,,A 32-bit integer uniquely identifying the neighboring router in the Autonomous System.
.1.3.6.1.2.1.14.11.1.3,OSPF-MIB::ospfVirtNbrIpAddr,IpAddress,read-only,,current,,The IP address this virtual neighbor is using.
.1.3.6.1.2.1.14.11.1.4,OSPF-MIB::ospfVirtNbrOptions,Integer32,read-only,,current,,A bit mask corresponding to the neighbor's options field. Bit 1, if set, indicates that the system will operate on Type of Service metrics other than TOS 0. If zero, the neighbor will ignore all metrics except the TOS 0 metric. Bit 2, if set, indicates that the system is network multicast capable, i.e., that it implements OSPF multicast routing.
.1.3.6.1.2.1.14.11.1.5,OSPF-MIB::ospfVirtNbrState,INTEGER,read-only,,current,down(1):attempt(2):init(3):twoWay(4):exchangeStart(5):exchange(6):loading(7):full(8),The state of the virtual neighbor relationship.
.1.3.6.1.2.1.14.11.1.6,OSPF-MIB::ospfVirtNbrEvents,Counter32,read-only,,current,,The number of times this virtual link has changed its state or an error has occurred. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ospfDiscontinuityTime.
.1.3.6.1.2.1.14.11.1.7,OSPF-MIB::ospfVirtNbrLsRetransQLen,Gauge32,read-only,,current,,The current length of the retransmission queue.
.1.3.6.1.2.1.14.11.1.8,OSPF-MIB::ospfVirtNbrHelloSuppressed,INTEGER,read-only,,current,true(1):false(2),Indicates whether Hellos are being suppressed to the neighbor.
.1.3.6.1.2.1.14.11.1.9,OSPF-MIB::ospfVirtNbrRestartHelperStatus,INTEGER,read-only,,current,notHelping(1):helping(2),Indicates whether the router is acting as a graceful restart helper for the neighbor.
.1.3.6.1.2.1.14.11.1.10,OSPF-MIB::ospfVirtNbrRestartHelperAge,Unsigned32,read-only,,current,,Remaining time in current OSPF graceful restart interval, if the router is acting as a restart helper for the neighbor.
.1.3.6.1.2.1.14.11.1.11,OSPF-MIB::ospfVirtNbrRestartHelperExitReason,INTEGER,read-only,,current,none(1):inProgress(2):completed(3):timedOut(4):topologyChanged(5),Describes the outcome of the last attempt at acting as a graceful restart helper for the neighbor.
.1.3.6.1.2.1.14.12,OSPF-MIB::ospfExtLsdbTable,,not-accessible,,deprecated,,The OSPF Process's external LSA link state database. This table is identical to the OSPF LSDB Table in format, but contains only external link state advertisements. The purpose is to allow external LSAs to be displayed once for the router rather than once in each non-stub area. Note that external LSAs are also in the AS-scope link state database.
.1.3.6.1.2.1.14.12.1,OSPF-MIB::ospfExtLsdbEntry,,not-accessible,ospfExtLsdbType:ospfExtLsdbLsid:ospfExtLsdbRouterId,deprecated,,A single link state advertisement.
.1.3.6.1.2.1.14.12.1.1,OSPF-MIB::ospfExtLsdbType,INTEGER,read-only,,deprecated,asExternalLink(5),The type of the link state advertisement. Each link state type has a separate advertisement format.
.1.3.6.1.2.1.14.12.1.2,OSPF-MIB::ospfExtLsdbLsid,IpAddress,read-only,,deprecated,,The Link State ID is an LS Type Specific field containing either a Router ID or an IP address; it identifies the piece of the routing domain that is being described by the advertisement.
.1.3.6.1.2.1.14.12.1.3,OSPF-MIB::ospfExtLsdbRouterId,IpAddress,read-only,,deprecated,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.14.12.1.4,OSPF-MIB::ospfExtLsdbSequence,Integer32,read-only,,deprecated,,The sequence number field is a signed 32-bit integer. It starts with the value '80000001'h, or -'7FFFFFFF'h, and increments until '7FFFFFFF'h. Thus, a typical sequence number will be very negative. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.14.12.1.5,OSPF-MIB::ospfExtLsdbAge,Integer32,read-only,,deprecated,,This field is the age of the link state advertisement in seconds.
.1.3.6.1.2.1.14.12.1.6,OSPF-MIB::ospfExtLsdbChecksum,Integer32,read-only,,deprecated,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.14.12.1.7,OSPF-MIB::ospfExtLsdbAdvertisement,OCTET,read-only,,deprecated,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.14.13,OSPF-MIB::ospfRouteGroup,,,,,,
.1.3.6.1.2.1.14.13.1,OSPF-MIB::ospfIntraArea,,,,,,
.1.3.6.1.2.1.14.13.2,OSPF-MIB::ospfInterArea,,,,,,
.1.3.6.1.2.1.14.13.3,OSPF-MIB::ospfExternalType1,,,,,,
.1.3.6.1.2.1.14.13.4,OSPF-MIB::ospfExternalType2,,,,,,
.1.3.6.1.2.1.14.14,OSPF-MIB::ospfAreaAggregateTable,,not-accessible,,current,,The Area Aggregate Table acts as an adjunct to the Area Table. It describes those address aggregates that are configured to be propagated from an area. Its purpose is to reduce the amount of information that is known beyond an Area's borders. It contains a set of IP address ranges specified by an IP address/IP network mask pair. For example, a class B address range of X.X.X.X with a network mask of 255.255.0.0 includes all IP addresses from X.X.0.0 to X.X.255.255. Note that if ranges are configured such that one range subsumes another range (e.g., 10.0.0.0 mask 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the most specific match is the preferred one.
.1.3.6.1.2.1.14.14.1,OSPF-MIB::ospfAreaAggregateEntry,,not-accessible,ospfAreaAggregateAreaID:ospfAreaAggregateLsdbType:ospfAreaAggregateNet:ospfAreaAggregateMask,current,,A single area aggregate entry. Information in this table is persistent and when this object is written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.14.1.1,OSPF-MIB::ospfAreaAggregateAreaID,IpAddress,read-only,,current,,The area within which the address aggregate is to be found.
.1.3.6.1.2.1.14.14.1.2,OSPF-MIB::ospfAreaAggregateLsdbType,INTEGER,read-only,,current,summaryLink(3):nssaExternalLink(7),The type of the address aggregate. This field specifies the Lsdb type that this address aggregate applies to.
.1.3.6.1.2.1.14.14.1.3,OSPF-MIB::ospfAreaAggregateNet,IpAddress,read-only,,current,,The IP address of the net or subnet indicated by the range.
.1.3.6.1.2.1.14.14.1.4,OSPF-MIB::ospfAreaAggregateMask,IpAddress,read-only,,current,,The subnet mask that pertains to the net or subnet.
.1.3.6.1.2.1.14.14.1.5,OSPF-MIB::ospfAreaAggregateStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.14.14.1.6,OSPF-MIB::ospfAreaAggregateEffect,INTEGER,read-create,,current,advertiseMatching(1):doNotAdvertiseMatching(2),Subnets subsumed by ranges either trigger the advertisement of the indicated aggregate (advertiseMatching) or result in the subnet's not being advertised at all outside the area.
.1.3.6.1.2.1.14.14.1.7,OSPF-MIB::ospfAreaAggregateExtRouteTag,Unsigned32,read-create,,current,,External route tag to be included in NSSA (type-7) LSAs.
.1.3.6.1.2.1.14.15,OSPF-MIB::ospfConformance,,,,,,
.1.3.6.1.2.1.14.15.1,OSPF-MIB::ospfGroups,,,,,,
.1.3.6.1.2.1.14.15.1.1,OSPF-MIB::ospfBasicGroup,,,,,,These objects are used to monitor/manage global OSPF parameters. This object group conforms to RFC 1850.
.1.3.6.1.2.1.14.15.1.2,OSPF-MIB::ospfAreaGroup,,,,,,These objects are used for OSPF systems supporting areas per RFC 1850.
.1.3.6.1.2.1.14.15.1.3,OSPF-MIB::ospfStubAreaGroup,,,,,,These objects are used for OSPF systems supporting stub areas.
.1.3.6.1.2.1.14.15.1.4,OSPF-MIB::ospfLsdbGroup,,,,,,These objects are used for OSPF systems that display their link state database.
.1.3.6.1.2.1.14.15.1.5,OSPF-MIB::ospfAreaRangeGroup,,,,,,These objects are used for non-CIDR OSPF systems that support multiple areas. This object group is obsolete.
.1.3.6.1.2.1.14.15.1.6,OSPF-MIB::ospfHostGroup,,,,,,These objects are used for OSPF systems that support attached hosts.
.1.3.6.1.2.1.14.15.1.7,OSPF-MIB::ospfIfGroup,,,,,,These objects are used to monitor/manage OSPF interfaces. This object group conforms to RFC 1850.
.1.3.6.1.2.1.14.15.1.8,OSPF-MIB::ospfIfMetricGroup,,,,,,These objects are used for OSPF systems for supporting interface metrics.
.1.3.6.1.2.1.14.15.1.9,OSPF-MIB::ospfVirtIfGroup,,,,,,These objects are used for OSPF systems for supporting virtual interfaces. This object group conforms to RFC 1850.
.1.3.6.1.2.1.14.15.1.10,OSPF-MIB::ospfNbrGroup,,,,,,These objects are used to monitor/manage OSPF neighbors. This object group conforms to RFC 1850.
.1.3.6.1.2.1.14.15.1.11,OSPF-MIB::ospfVirtNbrGroup,,,,,,These objects are used to monitor/manage OSPF virtual neighbors. This object group conforms to RFC 1850.
.1.3.6.1.2.1.14.15.1.12,OSPF-MIB::ospfExtLsdbGroup,,,,,,These objects are used for OSPF systems that display their link state database. This object group conforms to RFC 1850. This object group is replaced by the ospfAsLsdbGroup in order to support any AS-scope LSA type in a single table.
.1.3.6.1.2.1.14.15.1.13,OSPF-MIB::ospfAreaAggregateGroup,,,,,,These objects are used for OSPF systems to support network prefix aggregation across areas.
.1.3.6.1.2.1.14.15.1.14,OSPF-MIB::ospfLocalLsdbGroup,,,,,,These objects are used for OSPF systems that display their link-local link state databases for non-virtual links.
.1.3.6.1.2.1.14.15.1.15,OSPF-MIB::ospfVirtLocalLsdbGroup,,,,,,These objects are used for OSPF systems that display their link-local link state databases for virtual links.
.1.3.6.1.2.1.14.15.1.16,OSPF-MIB::ospfAsLsdbGroup,,,,,,These objects are used for OSPF systems that display their AS-scope link state database.
.1.3.6.1.2.1.14.15.1.17,OSPF-MIB::ospfBasicGroup2,,,,,,These objects are used to monitor/manage OSPF global parameters.
.1.3.6.1.2.1.14.15.1.18,OSPF-MIB::ospfAreaGroup2,,,,,,These objects are used by OSPF systems to support areas.
.1.3.6.1.2.1.14.15.1.19,OSPF-MIB::ospfIfGroup2,,,,,,These objects are used to monitor/manage OSPF interfaces.
.1.3.6.1.2.1.14.15.1.20,OSPF-MIB::ospfVirtIfGroup2,,,,,,These objects are used to monitor/manage OSPF virtual interfaces.
.1.3.6.1.2.1.14.15.1.21,OSPF-MIB::ospfNbrGroup2,,,,,,These objects are used to monitor/manage OSPF neighbors.
.1.3.6.1.2.1.14.15.1.22,OSPF-MIB::ospfVirtNbrGroup2,,,,,,These objects are used to monitor/manage OSPF virtual neighbors.
.1.3.6.1.2.1.14.15.1.23,OSPF-MIB::ospfAreaAggregateGroup2,,,,,,These objects are used for OSPF systems to support network prefix aggregation across areas.
.1.3.6.1.2.1.14.15.1.24,OSPF-MIB::ospfAreaLsaCountGroup,,,,,,These objects are used for OSPF systems that display per-area, per-LSA-type counters.
.1.3.6.1.2.1.14.15.1.25,OSPF-MIB::ospfHostGroup2,,,,,,These objects are used for OSPF systems that support attached hosts.
.1.3.6.1.2.1.14.15.1.26,OSPF-MIB::ospfObsoleteGroup,,,,,,These objects are obsolete and are no longer required for OSPF systems. They are placed into this group for SMI conformance.
.1.3.6.1.2.1.14.15.2,OSPF-MIB::ospfCompliances,,,,,,
.1.3.6.1.2.1.14.15.2.1,OSPF-MIB::ospfCompliance,,,,,,The compliance statement for OSPF systems conforming to RFC 1850.
.1.3.6.1.2.1.14.15.2.2,OSPF-MIB::ospfCompliance2,,,,,,The compliance statement.
.1.3.6.1.2.1.14.15.2.3,OSPF-MIB::ospfComplianceObsolete,,,,,,Contains obsolete object groups.
.1.3.6.1.2.1.14.16,OSPF-TRAP-MIB::ospfTrap,,,,,,The MIB module to describe traps for the OSPF Version 2 Protocol. Copyright (C) The IETF Trust (2006). This version of this MIB module is part of RFC 4750; see the RFC itself for full legal notices.
.1.3.6.1.2.1.14.16.1,OSPF-TRAP-MIB::ospfTrapControl,,,,,,
.1.3.6.1.2.1.14.16.1.1,OSPF-TRAP-MIB::ospfSetTrap,OCTET,read-write,,current,,A 4-octet string serving as a bit map for the trap events defined by the OSPF traps. This object is used to enable and disable specific OSPF traps where a 1 in the bit field represents enabled. The right-most bit (least significant) represents trap 0. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.14.16.1.2,OSPF-TRAP-MIB::ospfConfigErrorType,INTEGER,read-only,,current,badVersion(1):areaMismatch(2):unknownNbmaNbr(3):unknownVirtualNbr(4):authTypeMismatch(5):authFailure(6):netMaskMismatch(7):helloIntervalMismatch(8):deadIntervalMismatch(9):optionMismatch(10):mtuMismatch(11):duplicateRouterId(12):noError(13),Potential types of configuration conflicts. Used by the ospfConfigError and ospfConfigVirtError traps. When the last value of a trap using this object is needed, but no traps of that type have been sent, this value pertaining to this object should be returned as noError.
.1.3.6.1.2.1.14.16.1.3,OSPF-TRAP-MIB::ospfPacketType,INTEGER,read-only,,current,hello(1):dbDescript(2):lsReq(3):lsUpdate(4):lsAck(5):nullPacket(6),OSPF packet types. When the last value of a trap using this object is needed, but no traps of that type have been sent, this value pertaining to this object should be returned as nullPacket.
.1.3.6.1.2.1.14.16.1.4,OSPF-TRAP-MIB::ospfPacketSrc,IpAddress,read-only,,current,,The IP address of an inbound packet that cannot be identified by a neighbor instance. When the last value of a trap using this object is needed, but no traps of that type have been sent, this value pertaining to this object should be returned as 0.0.0.0.
.1.3.6.1.2.1.14.16.2,OSPF-TRAP-MIB::ospfTraps,,,,,,
.1.3.6.1.2.1.14.16.2.1,OSPF-TRAP-MIB::ospfVirtIfStateChange,,,,,,An ospfVirtIfStateChange trap signifies that there has been a change in the state of an OSPF virtual interface. This trap should be generated when the interface state regresses (e.g., goes from Point-to-Point to Down) or progresses to a terminal state (i.e., Point-to-Point).
.1.3.6.1.2.1.14.16.2.2,OSPF-TRAP-MIB::ospfNbrStateChange,,,,,,An ospfNbrStateChange trap signifies that there has been a change in the state of a non-virtual OSPF neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When an neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the trap should be generated by the designated router. A designated router transitioning to Down will be noted by ospfIfStateChange.
.1.3.6.1.2.1.14.16.2.3,OSPF-TRAP-MIB::ospfVirtNbrStateChange,,,,,,An ospfVirtNbrStateChange trap signifies that there has been a change in the state of an OSPF virtual neighbor. This trap should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full).
.1.3.6.1.2.1.14.16.2.4,OSPF-TRAP-MIB::ospfIfConfigError,,,,,,An ospfIfConfigError trap signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an adjacency from forming.
.1.3.6.1.2.1.14.16.2.5,OSPF-TRAP-MIB::ospfVirtIfConfigError,,,,,,An ospfVirtIfConfigError trap signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a trap only if it prevents an adjacency from forming.
.1.3.6.1.2.1.14.16.2.6,OSPF-TRAP-MIB::ospfIfAuthFailure,,,,,,An ospfIfAuthFailure trap signifies that a packet has been received on a non-virtual interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.
.1.3.6.1.2.1.14.16.2.7,OSPF-TRAP-MIB::ospfVirtIfAuthFailure,,,,,,An ospfVirtIfAuthFailure trap signifies that a packet has been received on a virtual interface from a router whose authentication key or authentication type conflicts with this router's authentication key or authentication type.
.1.3.6.1.2.1.14.16.2.8,OSPF-TRAP-MIB::ospfIfRxBadPacket,,,,,,An ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.
.1.3.6.1.2.1.14.16.2.9,OSPF-TRAP-MIB::ospfVirtIfRxBadPacket,,,,,,An ospfVirtIfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.
.1.3.6.1.2.1.14.16.2.10,OSPF-TRAP-MIB::ospfTxRetransmit,,,,,,An ospfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a non-virtual interface. All packets that may be retransmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
.1.3.6.1.2.1.14.16.2.11,OSPF-TRAP-MIB::ospfVirtIfTxRetransmit,,,,,,An ospfVirtIfTxRetransmit trap signifies than an OSPF packet has been retransmitted on a virtual interface. All packets that may be retransmitted are associated with an LSDB entry. The LS type, LS ID, and Router ID are used to identify the LSDB entry.
.1.3.6.1.2.1.14.16.2.12,OSPF-TRAP-MIB::ospfOriginateLsa,,,,,,An ospfOriginateLsa trap signifies that a new LSA has been originated by this router. This trap should not be invoked for simple refreshes of LSAs (which happens every 30 minutes), but instead will only be invoked when an LSA is (re)originated due to a topology change. Additionally, this trap does not include LSAs that are being flushed because they have reached MaxAge.
.1.3.6.1.2.1.14.16.2.13,OSPF-TRAP-MIB::ospfMaxAgeLsa,,,,,,An ospfMaxAgeLsa trap signifies that one of the LSAs in the router's link state database has aged to MaxAge.
.1.3.6.1.2.1.14.16.2.14,OSPF-TRAP-MIB::ospfLsdbOverflow,,,,,,An ospfLsdbOverflow trap signifies that the number of LSAs in the router's link state database has exceeded ospfExtLsdbLimit.
.1.3.6.1.2.1.14.16.2.15,OSPF-TRAP-MIB::ospfLsdbApproachingOverflow,,,,,,An ospfLsdbApproachingOverflow trap signifies that the number of LSAs in the router's link state database has exceeded ninety percent of ospfExtLsdbLimit.
.1.3.6.1.2.1.14.16.2.16,OSPF-TRAP-MIB::ospfIfStateChange,,,,,,An ospfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup).
.1.3.6.1.2.1.14.16.2.17,OSPF-TRAP-MIB::ospfNssaTranslatorStatusChange,,,,,,An ospfNssaTranslatorStatusChange trap indicates that there has been a change in the router's ability to translate OSPF type-7 LSAs into OSPF type-5 LSAs. This trap should be generated when the translator status transitions from or to any defined status on a per-area basis.
.1.3.6.1.2.1.14.16.2.18,OSPF-TRAP-MIB::ospfRestartStatusChange,,,,,,An ospfRestartStatusChange trap signifies that there has been a change in the graceful restart state for the router. This trap should be generated when the router restart status changes.
.1.3.6.1.2.1.14.16.2.19,OSPF-TRAP-MIB::ospfNbrRestartHelperStatusChange,,,,,,An ospfNbrRestartHelperStatusChange trap signifies that there has been a change in the graceful restart helper state for the neighbor. This trap should be generated when the neighbor restart helper status transitions for a neighbor.
.1.3.6.1.2.1.14.16.2.20,OSPF-TRAP-MIB::ospfVirtNbrRestartHelperStatusChange,,,,,,An ospfVirtNbrRestartHelperStatusChange trap signifies that there has been a change in the graceful restart helper state for the virtual neighbor. This trap should be generated when the virtual neighbor restart helper status transitions for a virtual neighbor.
.1.3.6.1.2.1.14.16.3,OSPF-TRAP-MIB::ospfTrapConformance,,,,,,
.1.3.6.1.2.1.14.16.3.1,OSPF-TRAP-MIB::ospfTrapGroups,,,,,,
.1.3.6.1.2.1.14.16.3.1.1,OSPF-TRAP-MIB::ospfTrapControlGroup,,,,,,These objects are required to control traps from OSPF systems.
.1.3.6.1.2.1.14.16.3.1.2,OSPF-TRAP-MIB::ospfTrapEventGroup,,,,,,A grouping of OSPF trap events, as specified in NOTIFICATION-TYPE constructs.
.1.3.6.1.2.1.14.16.3.2,OSPF-TRAP-MIB::ospfTrapCompliances,,,,,,
.1.3.6.1.2.1.14.16.3.2.1,OSPF-TRAP-MIB::ospfTrapCompliance,,,,,,The compliance statement.
.1.3.6.1.2.1.14.16.3.2.2,OSPF-TRAP-MIB::ospfTrapCompliance2,,,,,,The compliance statement.
.1.3.6.1.2.1.14.17,OSPF-MIB::ospfLocalLsdbTable,,not-accessible,,current,,The OSPF Process's link-local link state database for non-virtual links. This table is identical to the OSPF LSDB Table in format, but contains only link-local Link State Advertisements for non-virtual links. The purpose is to allow link-local LSAs to be displayed for each non-virtual interface. This table is implemented to support type-9 LSAs that are defined in 'The OSPF Opaque LSA Option'.
.1.3.6.1.2.1.14.17.1,OSPF-MIB::ospfLocalLsdbEntry,,not-accessible,ospfLocalLsdbIpAddress:ospfLocalLsdbAddressLessIf:ospfLocalLsdbType:ospfLocalLsdbLsid:ospfLocalLsdbRouterId,current,,A single link state advertisement.
.1.3.6.1.2.1.14.17.1.1,OSPF-MIB::ospfLocalLsdbIpAddress,IpAddress,not-accessible,,current,,The IP address of the interface from which the LSA was received if the interface is numbered.
.1.3.6.1.2.1.14.17.1.2,OSPF-MIB::ospfLocalLsdbAddressLessIf,Integer32,not-accessible,,current,,The interface index of the interface from which the LSA was received if the interface is unnumbered.
.1.3.6.1.2.1.14.17.1.3,OSPF-MIB::ospfLocalLsdbType,INTEGER,not-accessible,,current,localOpaqueLink(9),The type of the link state advertisement. Each link state type has a separate advertisement format.
.1.3.6.1.2.1.14.17.1.4,OSPF-MIB::ospfLocalLsdbLsid,IpAddress,not-accessible,,current,,The Link State ID is an LS Type Specific field containing a 32-bit identifier in IP address format; it identifies the piece of the routing domain that is being described by the advertisement.
.1.3.6.1.2.1.14.17.1.5,OSPF-MIB::ospfLocalLsdbRouterId,IpAddress,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.14.17.1.6,OSPF-MIB::ospfLocalLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It starts with the value '80000001'h, or -'7FFFFFFF'h, and increments until '7FFFFFFF'h. Thus, a typical sequence number will be very negative. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.14.17.1.7,OSPF-MIB::ospfLocalLsdbAge,Integer32,read-only,,current,,This field is the age of the link state advertisement in seconds.
.1.3.6.1.2.1.14.17.1.8,OSPF-MIB::ospfLocalLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.14.17.1.9,OSPF-MIB::ospfLocalLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header. Note that for variable length LSAs, SNMP agents may not be able to return the largest string size.
.1.3.6.1.2.1.14.18,OSPF-MIB::ospfVirtLocalLsdbTable,,not-accessible,,current,,The OSPF Process's link-local link state database for virtual links. This table is identical to the OSPF LSDB Table in format, but contains only link-local Link State Advertisements for virtual links. The purpose is to allow link-local LSAs to be displayed for each virtual interface. This table is implemented to support type-9 LSAs that are defined in 'The OSPF Opaque LSA Option'.
.1.3.6.1.2.1.14.18.1,OSPF-MIB::ospfVirtLocalLsdbEntry,,not-accessible,ospfVirtLocalLsdbTransitArea:ospfVirtLocalLsdbNeighbor:ospfVirtLocalLsdbType:ospfVirtLocalLsdbLsid:ospfVirtLocalLsdbRouterId,current,,A single link state advertisement.
.1.3.6.1.2.1.14.18.1.1,OSPF-MIB::ospfVirtLocalLsdbTransitArea,IpAddress,not-accessible,,current,,The transit area that the virtual link traverses. By definition, this is not 0.0.0.0.
.1.3.6.1.2.1.14.18.1.2,OSPF-MIB::ospfVirtLocalLsdbNeighbor,IpAddress,not-accessible,,current,,The Router ID of the virtual neighbor.
.1.3.6.1.2.1.14.18.1.3,OSPF-MIB::ospfVirtLocalLsdbType,INTEGER,not-accessible,,current,localOpaqueLink(9),The type of the link state advertisement. Each link state type has a separate advertisement format.
.1.3.6.1.2.1.14.18.1.4,OSPF-MIB::ospfVirtLocalLsdbLsid,IpAddress,not-accessible,,current,,The Link State ID is an LS Type Specific field containing a 32-bit identifier in IP address format; it identifies the piece of the routing domain that is being described by the advertisement.
.1.3.6.1.2.1.14.18.1.5,OSPF-MIB::ospfVirtLocalLsdbRouterId,IpAddress,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.14.18.1.6,OSPF-MIB::ospfVirtLocalLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It starts with the value '80000001'h, or -'7FFFFFFF'h, and increments until '7FFFFFFF'h. Thus, a typical sequence number will be very negative. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.14.18.1.7,OSPF-MIB::ospfVirtLocalLsdbAge,Integer32,read-only,,current,,This field is the age of the link state advertisement in seconds.
.1.3.6.1.2.1.14.18.1.8,OSPF-MIB::ospfVirtLocalLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.14.18.1.9,OSPF-MIB::ospfVirtLocalLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.14.19,OSPF-MIB::ospfAsLsdbTable,,not-accessible,,current,,The OSPF Process's AS-scope LSA link state database. The database contains the AS-scope Link State Advertisements from throughout the areas that the device is attached to. This table is identical to the OSPF LSDB Table in format, but contains only AS-scope Link State Advertisements. The purpose is to allow AS-scope LSAs to be displayed once for the router rather than once in each non-stub area.
.1.3.6.1.2.1.14.19.1,OSPF-MIB::ospfAsLsdbEntry,,not-accessible,ospfAsLsdbType:ospfAsLsdbLsid:ospfAsLsdbRouterId,current,,A single link state advertisement.
.1.3.6.1.2.1.14.19.1.1,OSPF-MIB::ospfAsLsdbType,INTEGER,not-accessible,,current,asExternalLink(5):asOpaqueLink(11),The type of the link state advertisement. Each link state type has a separate advertisement format.
.1.3.6.1.2.1.14.19.1.2,OSPF-MIB::ospfAsLsdbLsid,IpAddress,not-accessible,,current,,The Link State ID is an LS Type Specific field containing either a Router ID or an IP address; it identifies the piece of the routing domain that is being described by the advertisement.
.1.3.6.1.2.1.14.19.1.3,OSPF-MIB::ospfAsLsdbRouterId,IpAddress,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.14.19.1.4,OSPF-MIB::ospfAsLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It starts with the value '80000001'h, or -'7FFFFFFF'h, and increments until '7FFFFFFF'h. Thus, a typical sequence number will be very negative. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.14.19.1.5,OSPF-MIB::ospfAsLsdbAge,Integer32,read-only,,current,,This field is the age of the link state advertisement in seconds.
.1.3.6.1.2.1.14.19.1.6,OSPF-MIB::ospfAsLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.14.19.1.7,OSPF-MIB::ospfAsLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.14.20,OSPF-MIB::ospfAreaLsaCountTable,,not-accessible,,current,,This table maintains per-area, per-LSA-type counters
.1.3.6.1.2.1.14.20.1,OSPF-MIB::ospfAreaLsaCountEntry,,not-accessible,ospfAreaLsaCountAreaId:ospfAreaLsaCountLsaType,current,,An entry with a number of link advertisements of a given type for a given area.
.1.3.6.1.2.1.14.20.1.1,OSPF-MIB::ospfAreaLsaCountAreaId,IpAddress,not-accessible,,current,,This entry Area ID.
.1.3.6.1.2.1.14.20.1.2,OSPF-MIB::ospfAreaLsaCountLsaType,INTEGER,not-accessible,,current,routerLink(1):networkLink(2):summaryLink(3):asSummaryLink(4):multicastLink(6):nssaExternalLink(7):areaOpaqueLink(10),This entry LSA type.
.1.3.6.1.2.1.14.20.1.3,OSPF-MIB::ospfAreaLsaCountNumber,Gauge32,read-only,,current,,Number of LSAs of a given type for a given area.
.1.3.6.1.2.1.15,BGP4-MIB::bgp,,,,,,The MIB module for the BGP-4 protocol. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4273; see the RFC itself for full legal notices.
.1.3.6.1.2.1.15.0,BGP4-MIB::bgpNotification,,,,,,
.1.3.6.1.2.1.15.0.1,BGP4-MIB::bgpEstablishedNotification,,,,,,The bgpEstablishedNotification event is generated when the BGP FSM enters the established state. This Notification replaces the bgpEstablished Notification.
.1.3.6.1.2.1.15.0.2,BGP4-MIB::bgpBackwardTransNotification,,,,,,The bgpBackwardTransNotification event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. This Notification replaces the bgpBackwardsTransition Notification.
.1.3.6.1.2.1.15.1,BGP4-MIB::bgpVersion,OCTET,read-only,,current,,Vector of supported BGP protocol version numbers. Each peer negotiates the version from this vector. Versions are identified via the string of bits contained within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15, and so on, with the most significant bit referring to the lowest bit number in the octet (e.g., the MSB of the first octet refers to bit 0). If a bit, i, is present and set, then the version (i+1) of the BGP is supported.
.1.3.6.1.2.1.15.2,BGP4-MIB::bgpLocalAs,Integer32,read-only,,current,,The local autonomous system number.
.1.3.6.1.2.1.15.3,BGP4-MIB::bgpPeerTable,,not-accessible,,current,,BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers.
.1.3.6.1.2.1.15.3.1,BGP4-MIB::bgpPeerEntry,,not-accessible,bgpPeerRemoteAddr,current,,Entry containing information about the connection with a BGP peer.
.1.3.6.1.2.1.15.3.1.1,BGP4-MIB::bgpPeerIdentifier,IpAddress,read-only,,current,,The BGP Identifier of this entry's BGP peer. This entry MUST be 0.0.0.0 unless the bgpPeerState is in the openconfirm or the established state.
.1.3.6.1.2.1.15.3.1.2,BGP4-MIB::bgpPeerState,INTEGER,read-only,,current,idle(1):connect(2):active(3):opensent(4):openconfirm(5):established(6),The BGP peer connection state.
.1.3.6.1.2.1.15.3.1.3,BGP4-MIB::bgpPeerAdminStatus,INTEGER,read-write,,current,stop(1):start(2),The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Manual Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Manual Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication.
.1.3.6.1.2.1.15.3.1.4,BGP4-MIB::bgpPeerNegotiatedVersion,Integer32,read-only,,current,,The negotiated version of BGP running between the two peers. This entry MUST be zero (0) unless the bgpPeerState is in the openconfirm or the established state. Note that legal values for this object are between 0 and 255.
.1.3.6.1.2.1.15.3.1.5,BGP4-MIB::bgpPeerLocalAddr,IpAddress,read-only,,current,,The local IP address of this entry's BGP connection.
.1.3.6.1.2.1.15.3.1.6,BGP4-MIB::bgpPeerLocalPort,Integer32,read-only,,current,,The local port for the TCP connection between the BGP peers.
.1.3.6.1.2.1.15.3.1.7,BGP4-MIB::bgpPeerRemoteAddr,IpAddress,read-only,,current,,The remote IP address of this entry's BGP peer.
.1.3.6.1.2.1.15.3.1.8,BGP4-MIB::bgpPeerRemotePort,Integer32,read-only,,current,,The remote port for the TCP connection between the BGP peers. Note that the objects bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddr, and bgpPeerRemotePort provide the appropriate reference to the standard MIB TCP connection table.
.1.3.6.1.2.1.15.3.1.9,BGP4-MIB::bgpPeerRemoteAs,Integer32,read-only,,current,,The remote autonomous system number received in the BGP OPEN message.
.1.3.6.1.2.1.15.3.1.10,BGP4-MIB::bgpPeerInUpdates,Counter32,read-only,,current,,The number of BGP UPDATE messages received on this connection.
.1.3.6.1.2.1.15.3.1.11,BGP4-MIB::bgpPeerOutUpdates,Counter32,read-only,,current,,The number of BGP UPDATE messages transmitted on this connection.
.1.3.6.1.2.1.15.3.1.12,BGP4-MIB::bgpPeerInTotalMessages,Counter32,read-only,,current,,The total number of messages received from the remote peer on this connection.
.1.3.6.1.2.1.15.3.1.13,BGP4-MIB::bgpPeerOutTotalMessages,Counter32,read-only,,current,,The total number of messages transmitted to the remote peer on this connection.
.1.3.6.1.2.1.15.3.1.14,BGP4-MIB::bgpPeerLastError,OCTET,read-only,,current,,The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode.
.1.3.6.1.2.1.15.3.1.15,BGP4-MIB::bgpPeerFsmEstablishedTransitions,Counter32,read-only,,current,,The total number of times the BGP FSM transitioned into the established state for this peer.
.1.3.6.1.2.1.15.3.1.16,BGP4-MIB::bgpPeerFsmEstablishedTime,Gauge32,read-only,,current,,This timer indicates how long (in seconds) this peer has been in the established state or how long since this peer was last in the established state. It is set to zero when a new peer is configured or when the router is booted.
.1.3.6.1.2.1.15.3.1.17,BGP4-MIB::bgpPeerConnectRetryInterval,Integer32,read-write,,current,,Time interval (in seconds) for the ConnectRetry timer. The suggested value for this timer is 120 seconds.
.1.3.6.1.2.1.15.3.1.18,BGP4-MIB::bgpPeerHoldTime,Integer32,read-only,,current,,Time interval (in seconds) for the Hold Timer established with the peer. The value of this object is calculated by this BGP speaker, using the smaller of the values in bgpPeerHoldTimeConfigured and the Hold Time received in the OPEN message. This value must be at least three seconds if it is not zero (0). If the Hold Timer has not been established with the peer this object MUST have a value of zero (0). If the bgpPeerHoldTimeConfigured object has a value of (0), then this object MUST have a value of (0).
.1.3.6.1.2.1.15.3.1.19,BGP4-MIB::bgpPeerKeepAlive,Integer32,read-only,,current,,Time interval (in seconds) for the KeepAlive timer established with the peer. The value of this object is calculated by this BGP speaker such that, when compared with bgpPeerHoldTime, it has the same proportion that bgpPeerKeepAliveConfigured has, compared with bgpPeerHoldTimeConfigured. If the KeepAlive timer has not been established with the peer, this object MUST have a value of zero (0). If the of bgpPeerKeepAliveConfigured object has a value of (0), then this object MUST have a value of (0).
.1.3.6.1.2.1.15.3.1.20,BGP4-MIB::bgpPeerHoldTimeConfigured,Integer32,read-write,,current,,Time interval (in seconds) for the Hold Time configured for this BGP speaker with this peer. This value is placed in an OPEN message sent to this peer by this BGP speaker, and is compared with the Hold Time field in an OPEN message received from the peer when determining the Hold Time (bgpPeerHoldTime) with the peer. This value must not be less than three seconds if it is not zero (0). If it is zero (0), the Hold Time is NOT to be established with the peer. The suggested value for this timer is 90 seconds.
.1.3.6.1.2.1.15.3.1.21,BGP4-MIB::bgpPeerKeepAliveConfigured,Integer32,read-write,,current,,Time interval (in seconds) for the KeepAlive timer configured for this BGP speaker with this peer. The value of this object will only determine the KEEPALIVE messages' frequency relative to the value specified in bgpPeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by bgpPeerKeepAlive. A reasonable maximum value for this timer would be one third of that of bgpPeerHoldTimeConfigured. If the value of this object is zero (0), no periodical KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds.
.1.3.6.1.2.1.15.3.1.22,BGP4-MIB::bgpPeerMinASOriginationInterval,Integer32,read-write,,current,,Time interval (in seconds) for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds.
.1.3.6.1.2.1.15.3.1.23,BGP4-MIB::bgpPeerMinRouteAdvertisementInterval,Integer32,read-write,,current,,Time interval (in seconds) for the MinRouteAdvertisementInterval timer. The suggested value for this timer is 30 seconds for EBGP connections and 5 seconds for IBGP connections.
.1.3.6.1.2.1.15.3.1.24,BGP4-MIB::bgpPeerInUpdateElapsedTime,Gauge32,read-only,,current,,Elapsed time (in seconds) since the last BGP UPDATE message was received from the peer. Each time bgpPeerInUpdates is incremented, the value of this object is set to zero (0).
.1.3.6.1.2.1.15.4,BGP4-MIB::bgpIdentifier,IpAddress,read-only,,current,,The BGP Identifier of the local system.
.1.3.6.1.2.1.15.5,BGP4-MIB::bgpRcvdPathAttrTable,,not-accessible,,obsolete,,The BGP Received Path Attribute Table contains information about paths to destination networks, received from all peers running BGP version 3 or less.
.1.3.6.1.2.1.15.5.1,BGP4-MIB::bgpPathAttrEntry,,not-accessible,bgpPathAttrDestNetwork:bgpPathAttrPeer,obsolete,,Information about a path to a network.
.1.3.6.1.2.1.15.5.1.1,BGP4-MIB::bgpPathAttrPeer,IpAddress,read-only,,obsolete,,The IP address of the peer where the path information was learned.
.1.3.6.1.2.1.15.5.1.2,BGP4-MIB::bgpPathAttrDestNetwork,IpAddress,read-only,,obsolete,,The address of the destination network.
.1.3.6.1.2.1.15.5.1.3,BGP4-MIB::bgpPathAttrOrigin,INTEGER,read-only,,obsolete,igp(1):egp(2):incomplete(3),The ultimate origin of the path information.
.1.3.6.1.2.1.15.5.1.4,BGP4-MIB::bgpPathAttrASPath,OCTET,read-only,,obsolete,,The set of ASes that must be traversed to reach the network. This object is probably best represented as SEQUENCE OF INTEGER. For SMI compatibility, though, it is represented as OCTET STRING. Each AS is represented as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;
.1.3.6.1.2.1.15.5.1.5,BGP4-MIB::bgpPathAttrNextHop,IpAddress,read-only,,obsolete,,The address of the border router that should be used for the destination network.
.1.3.6.1.2.1.15.5.1.6,BGP4-MIB::bgpPathAttrInterASMetric,Integer32,read-only,,obsolete,,The optional inter-AS metric. If this attribute has not been provided for this route, the value for this object is 0.
.1.3.6.1.2.1.15.6,BGP4-MIB::bgp4PathAttrTable,,not-accessible,,current,,The BGP-4 Received Path Attribute Table contains information about paths to destination networks, received from all BGP4 peers.
.1.3.6.1.2.1.15.6.1,BGP4-MIB::bgp4PathAttrEntry,,not-accessible,bgp4PathAttrIpAddrPrefix:bgp4PathAttrIpAddrPrefixLen:bgp4PathAttrPeer,current,,Information about a path to a network.
.1.3.6.1.2.1.15.6.1.1,BGP4-MIB::bgp4PathAttrPeer,IpAddress,read-only,,current,,The IP address of the peer where the path information was learned.
.1.3.6.1.2.1.15.6.1.2,BGP4-MIB::bgp4PathAttrIpAddrPrefixLen,Integer32,read-only,,current,,Length in bits of the IP address prefix in the Network Layer Reachability Information field.
.1.3.6.1.2.1.15.6.1.3,BGP4-MIB::bgp4PathAttrIpAddrPrefix,IpAddress,read-only,,current,,An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by bgp4PathAttrIpAddrPrefixLen. Any bits beyond the length specified by bgp4PathAttrIpAddrPrefixLen are zeroed.
.1.3.6.1.2.1.15.6.1.4,BGP4-MIB::bgp4PathAttrOrigin,INTEGER,read-only,,current,igp(1):egp(2):incomplete(3),The ultimate origin of the path information.
.1.3.6.1.2.1.15.6.1.5,BGP4-MIB::bgp4PathAttrASPathSegment,OCTET,read-only,,current,,The sequence of AS path segments. Each AS path segment is represented by a triple <type, length, value>. The type is a 1-octet field that has two possible values: 1 AS_SET: unordered set of ASes that a route in the UPDATE message has traversed 2 AS_SEQUENCE: ordered set of ASes that a route in the UPDATE message has traversed. The length is a 1-octet field containing the number of ASes in the value field. The value field contains one or more AS numbers. Each AS is represented in the octet string as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255; Known Issues: o BGP Confederations will result in a type of either 3 or 4. o An AS Path may be longer than 255 octets. This may result in this object containing a truncated AS Path.
.1.3.6.1.2.1.15.6.1.6,BGP4-MIB::bgp4PathAttrNextHop,IpAddress,read-only,,current,,The address of the border router that should be used for the destination network. This address is the NEXT_HOP address received in the UPDATE packet.
.1.3.6.1.2.1.15.6.1.7,BGP4-MIB::bgp4PathAttrMultiExitDisc,Integer32,read-only,,current,,This metric is used to discriminate between multiple exit points to an adjacent autonomous system. A value of -1 indicates the absence of this attribute. Known Issues: o The BGP-4 specification uses an unsigned 32 bit number. Thus, this object cannot represent the full range of the protocol.
.1.3.6.1.2.1.15.6.1.8,BGP4-MIB::bgp4PathAttrLocalPref,Integer32,read-only,,current,,The originating BGP4 speaker's degree of preference for an advertised route. A value of -1 indicates the absence of this attribute. Known Issues: o The BGP-4 specification uses an unsigned 32 bit number and thus this object cannot represent the full range of the protocol.
.1.3.6.1.2.1.15.6.1.9,BGP4-MIB::bgp4PathAttrAtomicAggregate,INTEGER,read-only,,current,lessSpecificRouteNotSelected(1):lessSpecificRouteSelected(2),If the ATOMIC_AGGREGATE attribute is present in the Path Attributes then this object MUST have a value of 'lessSpecificRouteNotSelected'. If the ATOMIC_AGGREGATE attribute is missing in the Path Attributes then this object MUST have a value of 'lessSpecificRouteSelected'. Note that ATOMIC_AGGREGATE is now a primarily informational attribute.
.1.3.6.1.2.1.15.6.1.10,BGP4-MIB::bgp4PathAttrAggregatorAS,Integer32,read-only,,current,,The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute. Note that propagation of AS of zero is illegal in the Internet.
.1.3.6.1.2.1.15.6.1.11,BGP4-MIB::bgp4PathAttrAggregatorAddr,IpAddress,read-only,,current,,The IP address of the last BGP4 speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute.
.1.3.6.1.2.1.15.6.1.12,BGP4-MIB::bgp4PathAttrCalcLocalPref,Integer32,read-only,,current,,The degree of preference calculated by the receiving BGP4 speaker for an advertised route. A value of -1 indicates the absence of this attribute. Known Issues: o The BGP-4 specification uses an unsigned 32 bit number and thus this object cannot represent the full range of the protocol.
.1.3.6.1.2.1.15.6.1.13,BGP4-MIB::bgp4PathAttrBest,INTEGER,read-only,,current,false(1):true(2),An indication of whether this route was chosen as the best BGP4 route for this destination.
.1.3.6.1.2.1.15.6.1.14,BGP4-MIB::bgp4PathAttrUnknown,OCTET,read-only,,current,,One or more path attributes not understood by this BGP4 speaker. Path attributes are recorded in the Update Path attribute format of type, length, value. Size zero (0) indicates the absence of such attributes. Octets beyond the maximum size, if any, are not recorded by this object. Known Issues: o Attributes understood by this speaker, but not represented in this MIB, are unavailable to the agent.
.1.3.6.1.2.1.15.7,BGP4-MIB::bgpTraps,,,,,,
.1.3.6.1.2.1.15.7.1,BGP4-MIB::bgpEstablished,,,,,,The bgpEstablished event is generated when the BGP FSM enters the established state. This Notification has been replaced by the bgpEstablishedNotification Notification.
.1.3.6.1.2.1.15.7.2,BGP4-MIB::bgpBackwardTransition,,,,,,The bgpBackwardTransition event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. This Notification has been replaced by the bgpBackwardTransNotification Notification.
.1.3.6.1.2.1.15.8,BGP4-MIB::bgp4MIBConformance,,,,,,
.1.3.6.1.2.1.15.8.1,BGP4-MIB::bgp4MIBCompliances,,,,,,
.1.3.6.1.2.1.15.8.1.1,BGP4-MIB::bgp4MIBCompliance,,,,,,The compliance statement for entities which implement the BGP4 mib.
.1.3.6.1.2.1.15.8.1.2,BGP4-MIB::bgp4MIBDeprecatedCompliances,,,,,,The compliance statement documenting deprecated objects in the BGP4 mib.
.1.3.6.1.2.1.15.8.1.3,BGP4-MIB::bgp4MIBObsoleteCompliances,,,,,,The compliance statement documenting obsolete objects in the BGP4 mib.
.1.3.6.1.2.1.15.8.2,BGP4-MIB::bgp4MIBGroups,,,,,,
.1.3.6.1.2.1.15.8.2.1,BGP4-MIB::bgp4MIBGlobalsGroup,,,,,,A collection of objects providing information on global BGP state.
.1.3.6.1.2.1.15.8.2.2,BGP4-MIB::bgp4MIBPeerGroup,,,,,,A collection of objects for managing BGP peers.
.1.3.6.1.2.1.15.8.2.3,BGP4-MIB::bgpRcvdPathAttrGroup,,,,,,A collection of objects for managing BGP-3 and earlier path entries. This conformance group, like BGP-3, is obsolete.
.1.3.6.1.2.1.15.8.2.4,BGP4-MIB::bgp4MIBPathAttrGroup,,,,,,A collection of objects for managing BGP path entries.
.1.3.6.1.2.1.15.8.2.5,BGP4-MIB::bgp4MIBTrapGroup,,,,,,A collection of notifications for signaling changes in BGP peer relationships. Obsoleted by bgp4MIBNotificationGroup
.1.3.6.1.2.1.15.8.2.6,BGP4-MIB::bgp4MIBNotificationGroup,,,,,,A collection of notifications for signaling changes in BGP peer relationships. Obsoletes bgp4MIBTrapGroup.
.1.3.6.1.2.1.16,RMON-MIB::rmon,,,,,,
.1.3.6.1.2.1.16.0,RMON-MIB::rmonEventsV2,,,,,,Definition point for RMON notifications.
.1.3.6.1.2.1.16.0.1,RMON-MIB::risingAlarm,,,,,,The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.
.1.3.6.1.2.1.16.0.2,RMON-MIB::fallingAlarm,,,,,,The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.
.1.3.6.1.2.1.16.1,RMON-MIB::statistics,,,,,,
.1.3.6.1.2.1.16.1.1,RMON-MIB::etherStatsTable,,not-accessible,,current,,A list of Ethernet statistics entries.
.1.3.6.1.2.1.16.1.1.1,RMON-MIB::etherStatsEntry,,not-accessible,etherStatsIndex,current,,A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1
.1.3.6.1.2.1.16.1.1.1.1,RMON-MIB::etherStatsIndex,Integer32,read-only,,current,,The value of this object uniquely identifies this etherStats entry.
.1.3.6.1.2.1.16.1.1.1.2,RMON-MIB::etherStatsDataSource,OBJECT,read-create,,current,,This object identifies the source of the data that this etherStats entry is configured to analyze. This source can be any ethernet interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated etherStatsStatus object is equal to valid(1).
.1.3.6.1.2.1.16.1.1.1.3,RMON-MIB::etherStatsDropEvents,Counter32,read-only,,current,,The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.1.1.1.4,RMON-MIB::etherStatsOctets,Counter32,read-only,,current,,The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). This object can be used as a reasonable estimate of 10-Megabit ethernet utilization. If greater precision is desired, the etherStatsPkts and etherStatsOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows: Pkts * (9.6 + 6.4) + (Octets * .8) Utilization = ------------------------------------- Interval * 10,000 The result of this equation is the value Utilization which is the percent utilization of the ethernet segment on a scale of 0 to 100 percent.
.1.3.6.1.2.1.16.1.1.1.5,RMON-MIB::etherStatsPkts,Counter32,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
.1.3.6.1.2.1.16.1.1.1.6,RMON-MIB::etherStatsBroadcastPkts,Counter32,read-only,,current,,The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
.1.3.6.1.2.1.16.1.1.1.7,RMON-MIB::etherStatsMulticastPkts,Counter32,read-only,,current,,The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.1.1.1.8,RMON-MIB::etherStatsCRCAlignErrors,Counter32,read-only,,current,,The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
.1.3.6.1.2.1.16.1.1.1.9,RMON-MIB::etherStatsUndersizePkts,Counter32,read-only,,current,,The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
.1.3.6.1.2.1.16.1.1.1.10,RMON-MIB::etherStatsOversizePkts,Counter32,read-only,,current,,The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
.1.3.6.1.2.1.16.1.1.1.11,RMON-MIB::etherStatsFragments,Counter32,read-only,,current,,The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
.1.3.6.1.2.1.16.1.1.1.12,RMON-MIB::etherStatsJabbers,Counter32,read-only,,current,,The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
.1.3.6.1.2.1.16.1.1.1.13,RMON-MIB::etherStatsCollisions,Counter32,read-only,,current,,The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.
.1.3.6.1.2.1.16.1.1.1.14,RMON-MIB::etherStatsPkts64Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.15,RMON-MIB::etherStatsPkts65to127Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.16,RMON-MIB::etherStatsPkts128to255Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.17,RMON-MIB::etherStatsPkts256to511Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.18,RMON-MIB::etherStatsPkts512to1023Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.19,RMON-MIB::etherStatsPkts1024to1518Octets,Counter32,read-only,,current,,The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.1.1.20,RMON-MIB::etherStatsOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.1.1.1.21,RMON-MIB::etherStatsStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this etherStats entry.
.1.3.6.1.2.1.16.1.2,TOKEN-RING-RMON-MIB::tokenRingMLStatsTable,,not-accessible,,mandatory,,A list of Mac-Layer Token Ring statistics entries.
.1.3.6.1.2.1.16.1.2.1,TOKEN-RING-RMON-MIB::tokenRingMLStatsEntry,,not-accessible,tokenRingMLStatsIndex,mandatory,,A collection of Mac-Layer statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.1.2.1.1,TOKEN-RING-RMON-MIB::tokenRingMLStatsIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies this tokenRingMLStats entry.
.1.3.6.1.2.1.16.1.2.1.2,TOKEN-RING-RMON-MIB::tokenRingMLStatsDataSource,OBJECT,read-write,,mandatory,,This object identifies the source of the data that this tokenRingMLStats entry is configured to analyze. This source can be any tokenRing interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [3], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all error reports on the local network segment attached to the identified interface. This object may not be modified if the associated tokenRingMLStatsStatus object is equal to valid(1).
.1.3.6.1.2.1.16.1.2.1.3,TOKEN-RING-RMON-MIB::tokenRingMLStatsDropEvents,Counter32,read-only,,mandatory,,The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. This value is the same as the corresponding tokenRingPStatsDropEvents.
.1.3.6.1.2.1.16.1.2.1.4,TOKEN-RING-RMON-MIB::tokenRingMLStatsMacOctets,Counter32,read-only,,mandatory,,The total number of octets of data in MAC packets (excluding those that were not good frames) received on the network (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.2.1.5,TOKEN-RING-RMON-MIB::tokenRingMLStatsMacPkts,Counter32,read-only,,mandatory,,The total number of MAC packets (excluding packets that were not good frames) received.
.1.3.6.1.2.1.16.1.2.1.6,TOKEN-RING-RMON-MIB::tokenRingMLStatsRingPurgeEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters the ring purge state from normal ring state. The ring purge state that comes in response to the claim token or beacon state is not counted.
.1.3.6.1.2.1.16.1.2.1.7,TOKEN-RING-RMON-MIB::tokenRingMLStatsRingPurgePkts,Counter32,read-only,,mandatory,,The total number of ring purge MAC packets detected by probe.
.1.3.6.1.2.1.16.1.2.1.8,TOKEN-RING-RMON-MIB::tokenRingMLStatsBeaconEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters a beaconing state (beaconFrameStreamingState, beaconBitStreamingState, beaconSetRecoveryModeState, or beaconRingSignalLossState) from a non-beaconing state. Note that a change of the source address of the beacon packet does not constitute a new beacon event.
.1.3.6.1.2.1.16.1.2.1.9,TOKEN-RING-RMON-MIB::tokenRingMLStatsBeaconTime,INTEGER,read-only,,mandatory,,The total amount of time that the ring has been in the beaconing state.
.1.3.6.1.2.1.16.1.2.1.10,TOKEN-RING-RMON-MIB::tokenRingMLStatsBeaconPkts,Counter32,read-only,,mandatory,,The total number of beacon MAC packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.11,TOKEN-RING-RMON-MIB::tokenRingMLStatsClaimTokenEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters the claim token state from normal ring state or ring purge state. The claim token state that comes in response to a beacon state is not counted.
.1.3.6.1.2.1.16.1.2.1.12,TOKEN-RING-RMON-MIB::tokenRingMLStatsClaimTokenPkts,Counter32,read-only,,mandatory,,The total number of claim token MAC packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.13,TOKEN-RING-RMON-MIB::tokenRingMLStatsNAUNChanges,Counter32,read-only,,mandatory,,The total number of NAUN changes detected by the probe.
.1.3.6.1.2.1.16.1.2.1.14,TOKEN-RING-RMON-MIB::tokenRingMLStatsLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.15,TOKEN-RING-RMON-MIB::tokenRingMLStatsInternalErrors,Counter32,read-only,,mandatory,,The total number of adapter internal errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.16,TOKEN-RING-RMON-MIB::tokenRingMLStatsBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.17,TOKEN-RING-RMON-MIB::tokenRingMLStatsACErrors,Counter32,read-only,,mandatory,,The total number of AC (Address Copied) errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.18,TOKEN-RING-RMON-MIB::tokenRingMLStatsAbortErrors,Counter32,read-only,,mandatory,,The total number of abort delimiters reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.19,TOKEN-RING-RMON-MIB::tokenRingMLStatsLostFrameErrors,Counter32,read-only,,mandatory,,The total number of lost frame errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.20,TOKEN-RING-RMON-MIB::tokenRingMLStatsCongestionErrors,Counter32,read-only,,mandatory,,The total number of receive congestion errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.21,TOKEN-RING-RMON-MIB::tokenRingMLStatsFrameCopiedErrors,Counter32,read-only,,mandatory,,The total number of frame copied errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.22,TOKEN-RING-RMON-MIB::tokenRingMLStatsFrequencyErrors,Counter32,read-only,,mandatory,,The total number of frequency errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.23,TOKEN-RING-RMON-MIB::tokenRingMLStatsTokenErrors,Counter32,read-only,,mandatory,,The total number of token errors reported in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.1.2.1.24,TOKEN-RING-RMON-MIB::tokenRingMLStatsSoftErrorReports,Counter32,read-only,,mandatory,,The total number of soft error report frames detected by the probe.
.1.3.6.1.2.1.16.1.2.1.25,TOKEN-RING-RMON-MIB::tokenRingMLStatsRingPollEvents,Counter32,read-only,,mandatory,,The total number of ring poll events detected by the probe (i.e. the number of ring polls initiated by the active monitor that were detected).
.1.3.6.1.2.1.16.1.2.1.26,TOKEN-RING-RMON-MIB::tokenRingMLStatsOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.1.2.1.27,TOKEN-RING-RMON-MIB::tokenRingMLStatsStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this tokenRingMLStats entry.
.1.3.6.1.2.1.16.1.3,TOKEN-RING-RMON-MIB::tokenRingPStatsTable,,not-accessible,,mandatory,,A list of promiscuous Token Ring statistics entries.
.1.3.6.1.2.1.16.1.3.1,TOKEN-RING-RMON-MIB::tokenRingPStatsEntry,,not-accessible,tokenRingPStatsIndex,mandatory,,A collection of promiscuous statistics kept for non-MAC packets on a particular Token Ring interface.
.1.3.6.1.2.1.16.1.3.1.1,TOKEN-RING-RMON-MIB::tokenRingPStatsIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies this tokenRingPStats entry.
.1.3.6.1.2.1.16.1.3.1.2,TOKEN-RING-RMON-MIB::tokenRingPStatsDataSource,OBJECT,read-write,,mandatory,,This object identifies the source of the data that this tokenRingPStats entry is configured to analyze. This source can be any tokenRing interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in MIB-II [3], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all non-MAC packets on the local network segment attached to the identified interface. This object may not be modified if the associated tokenRingPStatsStatus object is equal to valid(1).
.1.3.6.1.2.1.16.1.3.1.3,TOKEN-RING-RMON-MIB::tokenRingPStatsDropEvents,Counter32,read-only,,mandatory,,The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. This value is the same as the corresponding tokenRingMLStatsDropEvents
.1.3.6.1.2.1.16.1.3.1.4,TOKEN-RING-RMON-MIB::tokenRingPStatsDataOctets,Counter32,read-only,,mandatory,,The total number of octets of data in good frames received on the network (excluding framing bits but including FCS octets) in non-MAC packets.
.1.3.6.1.2.1.16.1.3.1.5,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts,Counter32,read-only,,mandatory,,The total number of non-MAC packets in good frames. received.
.1.3.6.1.2.1.16.1.3.1.6,TOKEN-RING-RMON-MIB::tokenRingPStatsDataBroadcastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were directed to an LLC broadcast address (0xFFFFFFFFFFFF or 0xC000FFFFFFFF).
.1.3.6.1.2.1.16.1.3.1.7,TOKEN-RING-RMON-MIB::tokenRingPStatsDataMulticastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were directed to a local or global multicast or functional address. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.1.3.1.8,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts18to63Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.9,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts64to127Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 64 and 127 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.10,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts128to255Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 128 and 255 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.11,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts256to511Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 256 and 511 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.12,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts512to1023Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 512 and 1023 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.13,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts1024to2047Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 1024 and 2047 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.14,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts2048to4095Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 2048 and 4095 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.15,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts4096to8191Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 4096 and 8191 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.16,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPkts8192to18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were between 8192 and 18000 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.17,TOKEN-RING-RMON-MIB::tokenRingPStatsDataPktsGreaterThan18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received that were greater than 18000 octets in length, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.1.3.1.18,TOKEN-RING-RMON-MIB::tokenRingPStatsOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.1.3.1.19,TOKEN-RING-RMON-MIB::tokenRingPStatsStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this tokenRingPStats entry.
.1.3.6.1.2.1.16.1.4,RMON2-MIB::etherStats2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.4.1,RMON2-MIB::etherStats2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.4.1.1,RMON2-MIB::etherStatsDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.1.4.1.2,RMON2-MIB::etherStatsCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.1.5,RMON2-MIB::tokenRingMLStats2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.1.5.1,RMON2-MIB::tokenRingMLStats2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.5.1.1,RMON2-MIB::tokenRingMLStatsDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.1.5.1.2,RMON2-MIB::tokenRingMLStatsCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.1.6,RMON2-MIB::tokenRingPStats2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.1.6.1,RMON2-MIB::tokenRingPStats2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.1.6.1.1,RMON2-MIB::tokenRingPStatsDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.1.6.1.2,RMON2-MIB::tokenRingPStatsCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.1.7,HC-RMON-MIB::etherStatsHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 etherStatsTable.
.1.3.6.1.2.1.16.1.7.1,HC-RMON-MIB::etherStatsHighCapacityEntry,,not-accessible,etherStatsIndex,current,,Contains the High Capacity RMON extensions to the RMON-1 etherStatsEntry. These objects will be created by the agent for all etherStatsEntries it deems appropriate.
.1.3.6.1.2.1.16.1.7.1.1,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts,Counter32,read-only,,current,,The number of times the associated etherStatsPkts counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.2,HC-RMON-MIB::etherStatsHighCapacityPkts,Counter64,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
.1.3.6.1.2.1.16.1.7.1.3,HC-RMON-MIB::etherStatsHighCapacityOverflowOctets,Counter32,read-only,,current,,The number of times the associated etherStatsOctets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.4,HC-RMON-MIB::etherStatsHighCapacityOctets,Counter64,read-only,,current,,The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). If the network is half-duplex Fast Ethernet, this object can be used as a reasonable estimate of utilization. If greater precision is desired, the etherStatsHighCapacityPkts and etherStatsHighCapacityOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows: Pkts * (.96 + .64) + (Octets * .08) Utilization = ------------------------------------- Interval * 10,000 The result of this equation is the value Utilization which is the percent utilization of the ethernet segment on a scale of 0 to 100 percent. This table is not appropriate for monitoring full-duplex ethernets. If the network is a full-duplex ethernet and the mediaIndependentTable is monitoring that network, the utilization can be calculated as follows: 1) Determine the utilization of the inbound path by using the appropriate equation (for ethernet or fast ethernet) to determine the utilization, substituting mediaIndependentInPkts for etherStatsHighCapacityPkts, and mediaIndependentInOctets for etherStatsHighCapacityOctets. Call the resulting utilization inUtilization. 2) Determine the utilization of the outbound path by using the same equation to determine the utilization, substituting mediaIndependentOutPkts for etherStatsHighCapacityPkts, and mediaIndependentOutOctets for etherStatsHighCapacityOctets. Call the resulting utilization outUtilization. 3) The utilization is the maximum of inUtilization and outUtilization. This metric shows the amount of percentage of bandwidth that is left before congestion will be experienced on the link.
.1.3.6.1.2.1.16.1.7.1.5,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts64Octets,Counter32,read-only,,current,,The number of times the associated etherStatsPkts64Octets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.6,HC-RMON-MIB::etherStatsHighCapacityPkts64Octets,Counter64,read-only,,current,,The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.7.1.7,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts65to127Octets,Counter32,read-only,,current,,The number of times the associated etherStatsPkts65to127Octets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.8,HC-RMON-MIB::etherStatsHighCapacityPkts65to127Octets,Counter64,read-only,,current,,The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.7.1.9,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts128to255Octets,Counter32,read-only,,current,,The number of times the associated etherStatsPkts128to255Octets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.10,HC-RMON-MIB::etherStatsHighCapacityPkts128to255Octets,Counter64,read-only,,current,,The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.7.1.11,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts256to511Octets,Counter32,read-only,,current,,The number of times the associated etherStatsPkts256to511Octets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.12,HC-RMON-MIB::etherStatsHighCapacityPkts256to511Octets,Counter64,read-only,,current,,The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.7.1.13,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts512to1023Octets,Counter32,read-only,,current,,The number of times the associated etherStatsPkts512to1023Octets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.14,HC-RMON-MIB::etherStatsHighCapacityPkts512to1023Octets,Counter64,read-only,,current,,The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.1.7.1.15,HC-RMON-MIB::etherStatsHighCapacityOverflowPkts1024to1518Octets,Counter32,read-only,,current,,The number of times the associated etherStatsPkts1024to1518Octets counter has overflowed.
.1.3.6.1.2.1.16.1.7.1.16,HC-RMON-MIB::etherStatsHighCapacityPkts1024to1518Octets,Counter64,read-only,,current,,The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.2,RMON-MIB::history,,,,,,
.1.3.6.1.2.1.16.2.1,RMON-MIB::historyControlTable,,not-accessible,,current,,A list of history control entries.
.1.3.6.1.2.1.16.2.1.1,RMON-MIB::historyControlEntry,,not-accessible,historyControlIndex,current,,A list of parameters that set up a periodic sampling of statistics. As an example, an instance of the historyControlInterval object might be named historyControlInterval.2
.1.3.6.1.2.1.16.2.1.1.1,RMON-MIB::historyControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the historyControl table. Each such entry defines a set of samples at a particular interval for an interface on the device.
.1.3.6.1.2.1.16.2.1.1.2,RMON-MIB::historyControlDataSource,OBJECT,read-create,,current,,This object identifies the source of the data for which historical data was collected and placed in a media-specific table on behalf of this historyControlEntry. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated historyControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.2.1.1.3,RMON-MIB::historyControlBucketsRequested,Integer32,read-create,,current,,The requested number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControlEntry. When this object is created or modified, the probe should set historyControlBucketsGranted as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.2.1.1.4,RMON-MIB::historyControlBucketsGranted,Integer32,read-only,,current,,The number of discrete sampling intervals over which data shall be saved in the part of the media-specific table associated with this historyControlEntry. When the associated historyControlBucketsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. The probe must not lower this value except as a result of a modification to the associated historyControlBucketsRequested object. There will be times when the actual number of buckets associated with this entry is less than the value of this object. In this case, at the end of each sampling interval, a new bucket will be added to the media-specific table. When the number of buckets reaches the value of this object and a new bucket is to be added to the media-specific table, the oldest bucket associated with this historyControlEntry shall be deleted by the agent so that the new bucket can be added. When the value of this object changes to a value less than the current value, entries are deleted from the media-specific table associated with this historyControlEntry. Enough of the oldest of these entries shall be deleted by the agent so that their number remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated media- specific entries may be allowed to grow.
.1.3.6.1.2.1.16.2.1.1.5,RMON-MIB::historyControlInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControlEntry. This interval can be set to any number of seconds between 1 and 3600 (1 hour). Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the historyControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the etherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated historyControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.2.1.1.6,RMON-MIB::historyControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.2.1.1.7,RMON-MIB::historyControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this historyControl entry. Each instance of the media-specific table associated with this historyControlEntry will be deleted by the agent if this historyControlEntry is not equal to valid(1).
.1.3.6.1.2.1.16.2.2,RMON-MIB::etherHistoryTable,,not-accessible,,current,,A list of Ethernet history entries.
.1.3.6.1.2.1.16.2.2.1,RMON-MIB::etherHistoryEntry,,not-accessible,etherHistoryIndex:etherHistorySampleIndex,current,,An historical sample of Ethernet statistics on a particular Ethernet interface. This sample is associated with the historyControlEntry which set up the parameters for a regular collection of these samples. As an example, an instance of the etherHistoryPkts object might be named etherHistoryPkts.2.89
.1.3.6.1.2.1.16.2.2.1.1,RMON-MIB::etherHistoryIndex,Integer32,read-only,,current,,The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
.1.3.6.1.2.1.16.2.2.1.2,RMON-MIB::etherHistorySampleIndex,Integer32,read-only,,current,,An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.2.2.1.3,RMON-MIB::etherHistoryIntervalStart,TimeTicks,read-only,,current,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.2.2.1.4,RMON-MIB::etherHistoryDropEvents,Counter32,read-only,,current,,The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.2.2.1.5,RMON-MIB::etherHistoryOctets,Counter32,read-only,,current,,The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.2.2.1.6,RMON-MIB::etherHistoryPkts,Counter32,read-only,,current,,The number of packets (including bad packets) received during this sampling interval.
.1.3.6.1.2.1.16.2.2.1.7,RMON-MIB::etherHistoryBroadcastPkts,Counter32,read-only,,current,,The number of good packets received during this sampling interval that were directed to the broadcast address.
.1.3.6.1.2.1.16.2.2.1.8,RMON-MIB::etherHistoryMulticastPkts,Counter32,read-only,,current,,The number of good packets received during this sampling interval that were directed to a multicast address. Note that this number does not include packets addressed to the broadcast address.
.1.3.6.1.2.1.16.2.2.1.9,RMON-MIB::etherHistoryCRCAlignErrors,Counter32,read-only,,current,,The number of packets received during this sampling interval that had a length (excluding framing bits but including FCS octets) between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
.1.3.6.1.2.1.16.2.2.1.10,RMON-MIB::etherHistoryUndersizePkts,Counter32,read-only,,current,,The number of packets received during this sampling interval that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.
.1.3.6.1.2.1.16.2.2.1.11,RMON-MIB::etherHistoryOversizePkts,Counter32,read-only,,current,,The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed.
.1.3.6.1.2.1.16.2.2.1.12,RMON-MIB::etherHistoryFragments,Counter32,read-only,,current,,The total number of packets received during this sampling interval that were less than 64 octets in length (excluding framing bits but including FCS octets) had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that it is entirely normal for etherHistoryFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
.1.3.6.1.2.1.16.2.2.1.13,RMON-MIB::etherHistoryJabbers,Counter32,read-only,,current,,The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
.1.3.6.1.2.1.16.2.2.1.14,RMON-MIB::etherHistoryCollisions,Counter32,read-only,,current,,The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.
.1.3.6.1.2.1.16.2.2.1.15,RMON-MIB::etherHistoryUtilization,Integer32,read-only,,current,,The best estimate of the mean physical layer network utilization on this interface during this sampling interval, in hundredths of a percent.
.1.3.6.1.2.1.16.2.3,TOKEN-RING-RMON-MIB::tokenRingMLHistoryTable,,not-accessible,,mandatory,,A list of Mac-Layer Token Ring statistics entries.
.1.3.6.1.2.1.16.2.3.1,TOKEN-RING-RMON-MIB::tokenRingMLHistoryEntry,,not-accessible,tokenRingMLHistoryIndex:tokenRingMLHistorySampleIndex,mandatory,,A collection of Mac-Layer statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.2.3.1.1,TOKEN-RING-RMON-MIB::tokenRingMLHistoryIndex,INTEGER,read-only,,mandatory,,The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
.1.3.6.1.2.1.16.2.3.1.2,TOKEN-RING-RMON-MIB::tokenRingMLHistorySampleIndex,INTEGER,read-only,,mandatory,,An index that uniquely identifies the particular Mac-Layer sample this entry represents among all Mac-Layer samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.2.3.1.3,TOKEN-RING-RMON-MIB::tokenRingMLHistoryIntervalStart,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.2.3.1.4,TOKEN-RING-RMON-MIB::tokenRingMLHistoryDropEvents,Counter32,read-only,,mandatory,,The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.2.3.1.5,TOKEN-RING-RMON-MIB::tokenRingMLHistoryMacOctets,Counter32,read-only,,mandatory,,The total number of octets of data in MAC packets (excluding those that were not good frames) received on the network during this sampling interval (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.2.3.1.6,TOKEN-RING-RMON-MIB::tokenRingMLHistoryMacPkts,Counter32,read-only,,mandatory,,The total number of MAC packets (excluding those that were not good frames) received during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.7,TOKEN-RING-RMON-MIB::tokenRingMLHistoryRingPurgeEvents,Counter32,read-only,,mandatory,,The total number of times that the ring entered the ring purge state from normal ring state during this sampling interval. The ring purge state that comes from the claim token or beacon state is not counted.
.1.3.6.1.2.1.16.2.3.1.8,TOKEN-RING-RMON-MIB::tokenRingMLHistoryRingPurgePkts,Counter32,read-only,,mandatory,,The total number of Ring Purge MAC packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.9,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBeaconEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters a beaconing state (beaconFrameStreamingState, beaconBitStreamingState, beaconSetRecoveryModeState, or beaconRingSignalLossState) during this sampling interval. Note that a change of the source address of the beacon packet does not constitute a new beacon event.
.1.3.6.1.2.1.16.2.3.1.10,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBeaconTime,INTEGER,read-only,,mandatory,,The amount of time that the ring has been in the beaconing state during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.11,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBeaconPkts,Counter32,read-only,,mandatory,,The total number of beacon MAC packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.12,TOKEN-RING-RMON-MIB::tokenRingMLHistoryClaimTokenEvents,Counter32,read-only,,mandatory,,The total number of times that the ring enters the claim token state from normal ring state or ring purge state during this sampling interval. The claim token state that comes from the beacon state is not counted.
.1.3.6.1.2.1.16.2.3.1.13,TOKEN-RING-RMON-MIB::tokenRingMLHistoryClaimTokenPkts,Counter32,read-only,,mandatory,,The total number of claim token MAC packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.14,TOKEN-RING-RMON-MIB::tokenRingMLHistoryNAUNChanges,Counter32,read-only,,mandatory,,The total number of NAUN changes detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.15,TOKEN-RING-RMON-MIB::tokenRingMLHistoryLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.16,TOKEN-RING-RMON-MIB::tokenRingMLHistoryInternalErrors,Counter32,read-only,,mandatory,,The total number of adapter internal errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.17,TOKEN-RING-RMON-MIB::tokenRingMLHistoryBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.18,TOKEN-RING-RMON-MIB::tokenRingMLHistoryACErrors,Counter32,read-only,,mandatory,,The total number of AC (Address Copied) errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.19,TOKEN-RING-RMON-MIB::tokenRingMLHistoryAbortErrors,Counter32,read-only,,mandatory,,The total number of abort delimiters reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.20,TOKEN-RING-RMON-MIB::tokenRingMLHistoryLostFrameErrors,Counter32,read-only,,mandatory,,The total number of lost frame errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.21,TOKEN-RING-RMON-MIB::tokenRingMLHistoryCongestionErrors,Counter32,read-only,,mandatory,,The total number of receive congestion errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.22,TOKEN-RING-RMON-MIB::tokenRingMLHistoryFrameCopiedErrors,Counter32,read-only,,mandatory,,The total number of frame copied errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.23,TOKEN-RING-RMON-MIB::tokenRingMLHistoryFrequencyErrors,Counter32,read-only,,mandatory,,The total number of frequency errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.24,TOKEN-RING-RMON-MIB::tokenRingMLHistoryTokenErrors,Counter32,read-only,,mandatory,,The total number of token errors reported in error reporting packets detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.25,TOKEN-RING-RMON-MIB::tokenRingMLHistorySoftErrorReports,Counter32,read-only,,mandatory,,The total number of soft error report frames detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.26,TOKEN-RING-RMON-MIB::tokenRingMLHistoryRingPollEvents,Counter32,read-only,,mandatory,,The total number of ring poll events detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.3.1.27,TOKEN-RING-RMON-MIB::tokenRingMLHistoryActiveStations,INTEGER,read-only,,mandatory,,The maximum number of active stations on the ring detected by the probe during this sampling interval.
.1.3.6.1.2.1.16.2.4,TOKEN-RING-RMON-MIB::tokenRingPHistoryTable,,not-accessible,,mandatory,,A list of promiscuous Token Ring statistics entries.
.1.3.6.1.2.1.16.2.4.1,TOKEN-RING-RMON-MIB::tokenRingPHistoryEntry,,not-accessible,tokenRingPHistoryIndex:tokenRingPHistorySampleIndex,mandatory,,A collection of promiscuous statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.2.4.1.1,TOKEN-RING-RMON-MIB::tokenRingPHistoryIndex,INTEGER,read-only,,mandatory,,The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
.1.3.6.1.2.1.16.2.4.1.2,TOKEN-RING-RMON-MIB::tokenRingPHistorySampleIndex,INTEGER,read-only,,mandatory,,An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.2.4.1.3,TOKEN-RING-RMON-MIB::tokenRingPHistoryIntervalStart,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.2.4.1.4,TOKEN-RING-RMON-MIB::tokenRingPHistoryDropEvents,Counter32,read-only,,mandatory,,The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.2.4.1.5,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataOctets,Counter32,read-only,,mandatory,,The total number of octets of data in good frames received on the network (excluding framing bits but including FCS octets) in non-MAC packets during this sampling interval.
.1.3.6.1.2.1.16.2.4.1.6,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval.
.1.3.6.1.2.1.16.2.4.1.7,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataBroadcastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were directed to an LLC broadcast address (0xFFFFFFFFFFFF or 0xC000FFFFFFFF).
.1.3.6.1.2.1.16.2.4.1.8,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataMulticastPkts,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were directed to a local or global multicast or functional address. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.2.4.1.9,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts18to63Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.10,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts64to127Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 64 and 127 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.11,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts128to255Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 128 and 255 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.12,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts256to511Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 256 and 511 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.13,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts512to1023Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 512 and 1023 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.14,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts1024to2047Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 1024 and 2047 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.15,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts2048to4095Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 2048 and 4095 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.16,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts4096to8191Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 4096 and 8191 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.17,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPkts8192to18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were between 8192 and 18000 octets in length inclusive, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.4.1.18,TOKEN-RING-RMON-MIB::tokenRingPHistoryDataPktsGreaterThan18000Octets,Counter32,read-only,,mandatory,,The total number of good non-MAC frames received during this sampling interval that were greater than 18000 octets in length, excluding framing bits but including FCS octets.
.1.3.6.1.2.1.16.2.5,RMON2-MIB::historyControl2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.2.5.1,RMON2-MIB::historyControl2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.2.5.1.1,RMON2-MIB::historyControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.2.6,HC-RMON-MIB::etherHistoryHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 etherHistoryTable.
.1.3.6.1.2.1.16.2.6.1,HC-RMON-MIB::etherHistoryHighCapacityEntry,,not-accessible,etherHistoryIndex:etherHistorySampleIndex,current,,Contains the High Capacity RMON extensions to the RMON-1 etherHistoryEntry. These objects will be created by the agent for all etherHistoryEntries associated with whichever historyControlEntries it deems appropriate. (i.e., either all etherHistoryHighCapacityEntries associated with a particular historyControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.2.6.1.1,HC-RMON-MIB::etherHistoryHighCapacityOverflowPkts,Gauge32,read-only,,current,,The number of times the associated etherHistoryPkts Gauge overflowed during this sampling interval.
.1.3.6.1.2.1.16.2.6.1.2,HC-RMON-MIB::etherHistoryHighCapacityPkts,Counter64,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received during this sampling interval.
.1.3.6.1.2.1.16.2.6.1.3,HC-RMON-MIB::etherHistoryHighCapacityOverflowOctets,Gauge32,read-only,,current,,The number of times the associated etherHistoryOctets counter has overflowed during this sampling interval.
.1.3.6.1.2.1.16.2.6.1.4,HC-RMON-MIB::etherHistoryHighCapacityOctets,Counter64,read-only,,current,,The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets) during this sampling interval.
.1.3.6.1.2.1.16.3,RMON-MIB::alarm,,,,,,
.1.3.6.1.2.1.16.3.1,RMON-MIB::alarmTable,,not-accessible,,current,,A list of alarm entries.
.1.3.6.1.2.1.16.3.1.1,RMON-MIB::alarmEntry,,not-accessible,alarmIndex,current,,A list of parameters that set up a periodic checking for alarm conditions. For example, an instance of the alarmValue object might be named alarmValue.8
.1.3.6.1.2.1.16.3.1.1.1,RMON-MIB::alarmIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device.
.1.3.6.1.2.1.16.3.1.1.2,RMON-MIB::alarmInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this variable, care should be taken in the case of deltaValue sampling - the interval should be set short enough that the sampled variable is very unlikely to increase or decrease by more than 2^31 - 1 during a single sampling interval. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.3,RMON-MIB::alarmVariable,OBJECT,read-create,,current,,The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32, Counter32, Counter64, Gauge, or TimeTicks) may be sampled. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. During a set operation, if the supplied variable name is not available in the selected MIB view, a badValue error must be returned. If at any time the variable name of an established alarmEntry is no longer available in the selected MIB view, the probe must change the status of this alarmEntry to invalid(4). This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.4,RMON-MIB::alarmSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is absoluteValue(1), the value of the selected variable will be compared directly with the thresholds at the end of the sampling interval. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.5,RMON-MIB::alarmValue,Integer32,read-only,,current,,The value of the statistic during the last sampling period. For example, if the sample type is deltaValue, this value will be the difference between the samples at the beginning and end of the period. If the sample type is absoluteValue, this value will be the sampled value at the end of the period. This is the value that is compared with the rising and falling thresholds. The value during the current sampling period is not made available until the period is completed and will remain available until the next period completes.
.1.3.6.1.2.1.16.3.1.1.6,RMON-MIB::alarmStartupAlarm,INTEGER,read-create,,current,risingAlarm(1):fallingAlarm(2):risingOrFallingAlarm(3),The alarm that may be sent when this entry is first set to valid. If the first sample after this entry becomes valid is greater than or equal to the risingThreshold and alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the fallingThreshold and alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3), then a single falling alarm will be generated. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.7,RMON-MIB::alarmRisingThreshold,Integer32,read-create,,current,,A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the alarmFallingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.8,RMON-MIB::alarmFallingThreshold,Integer32,read-create,,current,,A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the alarmRisingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.9,RMON-MIB::alarmRisingEventIndex,Integer32,read-create,,current,,The index of the eventEntry that is used when a rising threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.10,RMON-MIB::alarmFallingEventIndex,Integer32,read-create,,current,,The index of the eventEntry that is used when a falling threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated alarmStatus object is equal to valid(1).
.1.3.6.1.2.1.16.3.1.1.11,RMON-MIB::alarmOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.3.1.1.12,RMON-MIB::alarmStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this alarm entry.
.1.3.6.1.2.1.16.4,RMON-MIB::hosts,,,,,,
.1.3.6.1.2.1.16.4.1,RMON-MIB::hostControlTable,,not-accessible,,current,,A list of host table control entries.
.1.3.6.1.2.1.16.4.1.1,RMON-MIB::hostControlEntry,,not-accessible,hostControlIndex,current,,A list of parameters that set up the discovery of hosts on a particular interface and the collection of statistics about these hosts. For example, an instance of the hostControlTableSize object might be named hostControlTableSize.1
.1.3.6.1.2.1.16.4.1.1.1,RMON-MIB::hostControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostControl table. Each such entry defines a function that discovers hosts on a particular interface and places statistics about them in the hostTable and the hostTimeTable on behalf of this hostControlEntry.
.1.3.6.1.2.1.16.4.1.1.2,RMON-MIB::hostControlDataSource,OBJECT,read-create,,current,,This object identifies the source of the data for this instance of the host function. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated hostControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.4.1.1.3,RMON-MIB::hostControlTableSize,Integer32,read-only,,current,,The number of hostEntries in the hostTable and the hostTimeTable associated with this hostControlEntry.
.1.3.6.1.2.1.16.4.1.1.4,RMON-MIB::hostControlLastDeleteTime,TimeTicks,read-only,,current,,The value of sysUpTime when the last entry was deleted from the portion of the hostTable associated with this hostControlEntry. If no deletions have occurred, this value shall be zero.
.1.3.6.1.2.1.16.4.1.1.5,RMON-MIB::hostControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.4.1.1.6,RMON-MIB::hostControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this hostControl entry. If this object is not equal to valid(1), all associated entries in the hostTable, hostTimeTable, and the hostTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.4.2,RMON-MIB::hostTable,,not-accessible,,current,,A list of host entries.
.1.3.6.1.2.1.16.4.2.1,RMON-MIB::hostEntry,,not-accessible,hostIndex:hostAddress,current,,A collection of statistics for a particular host that has been discovered on an interface of this device. For example, an instance of the hostOutBroadcastPkts object might be named hostOutBroadcastPkts.1.6.8.0.32.27.3.176
.1.3.6.1.2.1.16.4.2.1.1,RMON-MIB::hostAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.4.2.1.2,RMON-MIB::hostCreationOrder,Integer32,read-only,,current,,An index that defines the relative ordering of the creation time of hosts captured for a particular hostControlEntry. This index shall be between 1 and N, where N is the value of the associated hostControlTableSize. The ordering of the indexes is based on the order of each entry's insertion into the table, in which entries added earlier have a lower index value than entries added later. It is important to note that the order for a particular entry may change as an (earlier) entry is deleted from the table. Because this order may change, management stations should make use of the hostControlLastDeleteTime variable in the hostControlEntry associated with the relevant portion of the hostTable. By observing this variable, the management station may detect the circumstances where a previous association between a value of hostCreationOrder and a hostEntry may no longer hold.
.1.3.6.1.2.1.16.4.2.1.3,RMON-MIB::hostIndex,Integer32,read-only,,current,,The set of collected host statistics of which this entry is a part. The set of hosts identified by a particular value of this index is associated with the hostControlEntry as identified by the same value of hostControlIndex.
.1.3.6.1.2.1.16.4.2.1.4,RMON-MIB::hostInPkts,Counter32,read-only,,current,,The number of good packets transmitted to this address since it was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.5,RMON-MIB::hostOutPkts,Counter32,read-only,,current,,The number of packets, including bad packets, transmitted by this address since it was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.6,RMON-MIB::hostInOctets,Counter32,read-only,,current,,The number of octets transmitted to this address since it was added to the hostTable (excluding framing bits but including FCS octets), except for those octets in bad packets.
.1.3.6.1.2.1.16.4.2.1.7,RMON-MIB::hostOutOctets,Counter32,read-only,,current,,The number of octets transmitted by this address since it was added to the hostTable (excluding framing bits but including FCS octets), including those octets in bad packets.
.1.3.6.1.2.1.16.4.2.1.8,RMON-MIB::hostOutErrors,Counter32,read-only,,current,,The number of bad packets transmitted by this address since this host was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.9,RMON-MIB::hostOutBroadcastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to the broadcast address since this host was added to the hostTable.
.1.3.6.1.2.1.16.4.2.1.10,RMON-MIB::hostOutMulticastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to a multicast address since this host was added to the hostTable. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.4.3,RMON-MIB::hostTimeTable,,not-accessible,,current,,A list of time-ordered host table entries.
.1.3.6.1.2.1.16.4.3.1,RMON-MIB::hostTimeEntry,,not-accessible,hostTimeIndex:hostTimeCreationOrder,current,,A collection of statistics for a particular host that has been discovered on an interface of this device. This collection includes the relative ordering of the creation time of this object. For example, an instance of the hostTimeOutBroadcastPkts object might be named hostTimeOutBroadcastPkts.1.687
.1.3.6.1.2.1.16.4.3.1.1,RMON-MIB::hostTimeAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.4.3.1.2,RMON-MIB::hostTimeCreationOrder,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostTime table among those entries associated with the same hostControlEntry. This index shall be between 1 and N, where N is the value of the associated hostControlTableSize. The ordering of the indexes is based on the order of each entry's insertion into the table, in which entries added earlier have a lower index value than entries added later. Thus the management station has the ability to learn of new entries added to this table without downloading the entire table. It is important to note that the index for a particular entry may change as an (earlier) entry is deleted from the table. Because this order may change, management stations should make use of the hostControlLastDeleteTime variable in the hostControlEntry associated with the relevant portion of the hostTimeTable. By observing this variable, the management station may detect the circumstances where a download of the table may have missed entries, and where a previous association between a value of hostTimeCreationOrder and a hostTimeEntry may no longer hold.
.1.3.6.1.2.1.16.4.3.1.3,RMON-MIB::hostTimeIndex,Integer32,read-only,,current,,The set of collected host statistics of which this entry is a part. The set of hosts identified by a particular value of this index is associated with the hostControlEntry as identified by the same value of hostControlIndex.
.1.3.6.1.2.1.16.4.3.1.4,RMON-MIB::hostTimeInPkts,Counter32,read-only,,current,,The number of good packets transmitted to this address since it was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.5,RMON-MIB::hostTimeOutPkts,Counter32,read-only,,current,,The number of packets, including bad packets, transmitted by this address since it was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.6,RMON-MIB::hostTimeInOctets,Counter32,read-only,,current,,The number of octets transmitted to this address since it was added to the hostTimeTable (excluding framing bits but including FCS octets), except for those octets in bad packets.
.1.3.6.1.2.1.16.4.3.1.7,RMON-MIB::hostTimeOutOctets,Counter32,read-only,,current,,The number of octets transmitted by this address since it was added to the hostTimeTable (excluding framing bits but including FCS octets), including those octets in bad packets.
.1.3.6.1.2.1.16.4.3.1.8,RMON-MIB::hostTimeOutErrors,Counter32,read-only,,current,,The number of bad packets transmitted by this address since this host was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.9,RMON-MIB::hostTimeOutBroadcastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to the broadcast address since this host was added to the hostTimeTable.
.1.3.6.1.2.1.16.4.3.1.10,RMON-MIB::hostTimeOutMulticastPkts,Counter32,read-only,,current,,The number of good packets transmitted by this address that were directed to a multicast address since this host was added to the hostTimeTable. Note that this number does not include packets directed to the broadcast address.
.1.3.6.1.2.1.16.4.4,RMON2-MIB::hostControl2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.4.4.1,RMON2-MIB::hostControl2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.4.4.1.1,RMON2-MIB::hostControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.4.4.1.2,RMON2-MIB::hostControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.4.5,HC-RMON-MIB::hostHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 hostTable.
.1.3.6.1.2.1.16.4.5.1,HC-RMON-MIB::hostHighCapacityEntry,,not-accessible,hostIndex:hostAddress,current,,Contains the High Capacity RMON extensions to the RMON-1 hostEntry. These objects will be created by the agent for all hostEntries associated with whichever hostControlEntries it deems appropriate. (i.e., either all hostHighCapacityEntries associated with a particular hostControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.4.5.1.1,HC-RMON-MIB::hostHighCapacityInOverflowPkts,Counter32,read-only,,current,,The number of times the associated hostInPkts counter has overflowed.
.1.3.6.1.2.1.16.4.5.1.2,HC-RMON-MIB::hostHighCapacityInPkts,Counter64,read-only,,current,,The number of good packets transmitted to this address since it was added to the hostHighCapacityTable.
.1.3.6.1.2.1.16.4.5.1.3,HC-RMON-MIB::hostHighCapacityOutOverflowPkts,Counter32,read-only,,current,,The number of times the associated hostOutPkts counter has overflowed.
.1.3.6.1.2.1.16.4.5.1.4,HC-RMON-MIB::hostHighCapacityOutPkts,Counter64,read-only,,current,,The number of packets, including bad packets, transmitted by this address since it was added to the hostHighCapacityTable.
.1.3.6.1.2.1.16.4.5.1.5,HC-RMON-MIB::hostHighCapacityInOverflowOctets,Counter32,read-only,,current,,The number of times the associated hostInOctets counter has overflowed.
.1.3.6.1.2.1.16.4.5.1.6,HC-RMON-MIB::hostHighCapacityInOctets,Counter64,read-only,,current,,The number of octets transmitted to this address since it was added to the hostHighCapacityTable (excluding framing bits but including FCS octets), except for those octets in bad packets.
.1.3.6.1.2.1.16.4.5.1.7,HC-RMON-MIB::hostHighCapacityOutOverflowOctets,Counter32,read-only,,current,,The number of times the associated hostOutOctets counter has overflowed.
.1.3.6.1.2.1.16.4.5.1.8,HC-RMON-MIB::hostHighCapacityOutOctets,Counter64,read-only,,current,,The number of octets transmitted by this address since it was added to the hostHighCapacityTable (excluding framing bits but including FCS octets), including those octets in bad packets.
.1.3.6.1.2.1.16.4.6,HC-RMON-MIB::hostTimeHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 hostTimeTable.
.1.3.6.1.2.1.16.4.6.1,HC-RMON-MIB::hostTimeHighCapacityEntry,,not-accessible,hostTimeIndex:hostTimeCreationOrder,current,,Contains the High Capacity RMON extensions to the RMON-1 hostTimeEntry. These objects will be created by the agent for all hostTimeEntries associated with whichever hostControlEntries it deems appropriate. (i.e., either all hostTimeHighCapacityEntries associated with a particular hostControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.4.6.1.1,HC-RMON-MIB::hostTimeHighCapacityInOverflowPkts,Counter32,read-only,,current,,The number of times the associated hostTimeInPkts counter has overflowed.
.1.3.6.1.2.1.16.4.6.1.2,HC-RMON-MIB::hostTimeHighCapacityInPkts,Counter64,read-only,,current,,The number of good packets transmitted to this address since it was added to the hostTimeHighCapacityTable.
.1.3.6.1.2.1.16.4.6.1.3,HC-RMON-MIB::hostTimeHighCapacityOutOverflowPkts,Counter32,read-only,,current,,The number of times the associated hostTimeOutPkts counter has overflowed.
.1.3.6.1.2.1.16.4.6.1.4,HC-RMON-MIB::hostTimeHighCapacityOutPkts,Counter64,read-only,,current,,The number of packets, including bad packets, transmitted by this address since it was added to the hostTimeHighCapacityTable.
.1.3.6.1.2.1.16.4.6.1.5,HC-RMON-MIB::hostTimeHighCapacityInOverflowOctets,Counter32,read-only,,current,,The number of times the associated hostTimeInOctets counter has overflowed.
.1.3.6.1.2.1.16.4.6.1.6,HC-RMON-MIB::hostTimeHighCapacityInOctets,Counter64,read-only,,current,,The number of octets transmitted to this address since it was added to the hostTimeHighCapacityTable (excluding framing bits but including FCS octets), except for those octets in bad packets.
.1.3.6.1.2.1.16.4.6.1.7,HC-RMON-MIB::hostTimeHighCapacityOutOverflowOctets,Counter32,read-only,,current,,The number of times the associated hostTimeOutOctets counter has overflowed.
.1.3.6.1.2.1.16.4.6.1.8,HC-RMON-MIB::hostTimeHighCapacityOutOctets,Counter64,read-only,,current,,The number of octets transmitted by this address since it was added to the hostTimeTable (excluding framing bits but including FCS octets), including those octets in bad packets.
.1.3.6.1.2.1.16.5,RMON-MIB::hostTopN,,,,,,
.1.3.6.1.2.1.16.5.1,RMON-MIB::hostTopNControlTable,,not-accessible,,current,,A list of top N host control entries.
.1.3.6.1.2.1.16.5.1.1,RMON-MIB::hostTopNControlEntry,,not-accessible,hostTopNControlIndex,current,,A set of parameters that control the creation of a report of the top N hosts according to several metrics. For example, an instance of the hostTopNDuration object might be named hostTopNDuration.3
.1.3.6.1.2.1.16.5.1.1.1,RMON-MIB::hostTopNControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostTopNControl table. Each such entry defines one top N report prepared for one interface.
.1.3.6.1.2.1.16.5.1.1.2,RMON-MIB::hostTopNHostIndex,Integer32,read-create,,current,,The host table for which a top N report will be prepared on behalf of this entry. The host table identified by a particular value of this index is associated with the same host table as identified by the same value of hostIndex. This object may not be modified if the associated hostTopNStatus object is equal to valid(1).
.1.3.6.1.2.1.16.5.1.1.3,RMON-MIB::hostTopNRateBase,INTEGER,read-create,,current,hostTopNInPkts(1):hostTopNOutPkts(2):hostTopNInOctets(3):hostTopNOutOctets(4):hostTopNOutErrors(5):hostTopNOutBroadcastPkts(6):hostTopNOutMulticastPkts(7),The variable for each host that the hostTopNRate variable is based upon. This object may not be modified if the associated hostTopNStatus object is equal to valid(1).
.1.3.6.1.2.1.16.5.1.1.4,RMON-MIB::hostTopNTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, which is loaded into the associated hostTopNDuration object. When this object is set to a non-zero value, any associated hostTopNEntries shall be made inaccessible by the monitor. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated hostTopNEntries shall remain inaccessible. At the time that this object decrements to zero, the report is made accessible in the hostTopNTable. Thus, the hostTopN table needs to be created only at the end of the collection interval.
.1.3.6.1.2.1.16.5.1.1.5,RMON-MIB::hostTopNDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval. When the associated hostTopNTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the hostTopNTimeRemaining is set. This value shall be zero if no reports have been requested for this hostTopNControlEntry.
.1.3.6.1.2.1.16.5.1.1.6,RMON-MIB::hostTopNRequestedSize,Integer32,read-create,,current,,The maximum number of hosts requested for the top N table. When this object is created or modified, the probe should set hostTopNGrantedSize as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.5.1.1.7,RMON-MIB::hostTopNGrantedSize,Integer32,read-only,,current,,The maximum number of hosts in the top N table. When the associated hostTopNRequestedSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe must not lower this value except as a result of a set to the associated hostTopNRequestedSize object. Hosts with the highest value of hostTopNRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more hosts.
.1.3.6.1.2.1.16.5.1.1.8,RMON-MIB::hostTopNStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated hostTopNTimeRemaining object was modified to start the requested report.
.1.3.6.1.2.1.16.5.1.1.9,RMON-MIB::hostTopNOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.5.1.1.10,RMON-MIB::hostTopNStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this hostTopNControl entry. If this object is not equal to valid(1), all associated hostTopNEntries shall be deleted by the agent.
.1.3.6.1.2.1.16.5.2,RMON-MIB::hostTopNTable,,not-accessible,,current,,A list of top N host entries.
.1.3.6.1.2.1.16.5.2.1,RMON-MIB::hostTopNEntry,,not-accessible,hostTopNReport:hostTopNIndex,current,,A set of statistics for a host that is part of a top N report. For example, an instance of the hostTopNRate object might be named hostTopNRate.3.10
.1.3.6.1.2.1.16.5.2.1.1,RMON-MIB::hostTopNReport,Integer32,read-only,,current,,This object identifies the top N report of which this entry is a part. The set of hosts identified by a particular value of this object is part of the same report as identified by the same value of the hostTopNControlIndex object.
.1.3.6.1.2.1.16.5.2.1.2,RMON-MIB::hostTopNIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the hostTopN table among those in the same report. This index is between 1 and N, where N is the number of entries in this table. Increasing values of hostTopNIndex shall be assigned to entries with decreasing values of hostTopNRate until index N is assigned to the entry with the lowest value of hostTopNRate or there are no more hostTopNEntries.
.1.3.6.1.2.1.16.5.2.1.3,RMON-MIB::hostTopNAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.5.2.1.4,RMON-MIB::hostTopNRate,Integer32,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this host's instance of the object selected by hostTopNRateBase.
.1.3.6.1.2.1.16.5.3,HC-RMON-MIB::hostTopNHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 hostTopNTable when hostTopNRateBase specifies a High Capacity TopN Report.
.1.3.6.1.2.1.16.5.3.1,HC-RMON-MIB::hostTopNHighCapacityEntry,,not-accessible,hostTopNReport:hostTopNIndex,current,,Contains the High Capacity RMON extensions to the RMON-1 hostTopNEntry when hostTopNRateBase specifies a High Capacity TopN Report. These objects will be created by the agent for all hostTopNEntries associated with whichever hostTopNControlEntries have a hostTopNRateBase that specify a high capacity report.
.1.3.6.1.2.1.16.5.3.1.1,HC-RMON-MIB::hostTopNHighCapacityAddress,OCTET,read-only,,current,,The physical address of this host.
.1.3.6.1.2.1.16.5.3.1.2,HC-RMON-MIB::hostTopNHighCapacityBaseRate,Gauge32,read-only,,current,,The amount of change in the selected variable during this sampling interval, modulo 2^32. The selected variable is this host's instance of the object selected by hostTopNRateBase.
.1.3.6.1.2.1.16.5.3.1.3,HC-RMON-MIB::hostTopNHighCapacityOverflowRate,Gauge32,read-only,,current,,The amount of change in the selected variable during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32). The selected variable is this host's instance of the object selected by hostTopNRateBase.
.1.3.6.1.2.1.16.5.3.1.4,HC-RMON-MIB::hostTopNHighCapacityRate,Counter64,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this host's instance of the object selected by hostTopNRateBase.
.1.3.6.1.2.1.16.6,RMON-MIB::matrix,,,,,,
.1.3.6.1.2.1.16.6.1,RMON-MIB::matrixControlTable,,not-accessible,,current,,A list of information entries for the traffic matrix on each interface.
.1.3.6.1.2.1.16.6.1.1,RMON-MIB::matrixControlEntry,,not-accessible,matrixControlIndex,current,,Information about a traffic matrix on a particular interface. For example, an instance of the matrixControlLastDeleteTime object might be named matrixControlLastDeleteTime.1
.1.3.6.1.2.1.16.6.1.1.1,RMON-MIB::matrixControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the matrixControl table. Each such entry defines a function that discovers conversations on a particular interface and places statistics about them in the matrixSDTable and the matrixDSTable on behalf of this matrixControlEntry.
.1.3.6.1.2.1.16.6.1.1.2,RMON-MIB::matrixControlDataSource,OBJECT,read-create,,current,,This object identifies the source of the data from which this entry creates a traffic matrix. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 2233 [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated matrixControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.6.1.1.3,RMON-MIB::matrixControlTableSize,Integer32,read-only,,current,,The number of matrixSDEntries in the matrixSDTable for this interface. This must also be the value of the number of entries in the matrixDSTable for this interface.
.1.3.6.1.2.1.16.6.1.1.4,RMON-MIB::matrixControlLastDeleteTime,TimeTicks,read-only,,current,,The value of sysUpTime when the last entry was deleted from the portion of the matrixSDTable or matrixDSTable associated with this matrixControlEntry. If no deletions have occurred, this value shall be zero.
.1.3.6.1.2.1.16.6.1.1.5,RMON-MIB::matrixControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.6.1.1.6,RMON-MIB::matrixControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this matrixControl entry. If this object is not equal to valid(1), all associated entries in the matrixSDTable and the matrixDSTable shall be deleted by the agent.
.1.3.6.1.2.1.16.6.2,RMON-MIB::matrixSDTable,,not-accessible,,current,,A list of traffic matrix entries indexed by source and destination MAC address.
.1.3.6.1.2.1.16.6.2.1,RMON-MIB::matrixSDEntry,,not-accessible,matrixSDIndex:matrixSDSourceAddress:matrixSDDestAddress,current,,A collection of statistics for communications between two addresses on a particular interface. For example, an instance of the matrixSDPkts object might be named matrixSDPkts.1.6.8.0.32.27.3.176.6.8.0.32.10.8.113
.1.3.6.1.2.1.16.6.2.1.1,RMON-MIB::matrixSDSourceAddress,OCTET,read-only,,current,,The source physical address.
.1.3.6.1.2.1.16.6.2.1.2,RMON-MIB::matrixSDDestAddress,OCTET,read-only,,current,,The destination physical address.
.1.3.6.1.2.1.16.6.2.1.3,RMON-MIB::matrixSDIndex,Integer32,read-only,,current,,The set of collected matrix statistics of which this entry is a part. The set of matrix statistics identified by a particular value of this index is associated with the same matrixControlEntry as identified by the same value of matrixControlIndex.
.1.3.6.1.2.1.16.6.2.1.4,RMON-MIB::matrixSDPkts,Counter32,read-only,,current,,The number of packets transmitted from the source address to the destination address (this number includes bad packets).
.1.3.6.1.2.1.16.6.2.1.5,RMON-MIB::matrixSDOctets,Counter32,read-only,,current,,The number of octets (excluding framing bits but including FCS octets) contained in all packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.2.1.6,RMON-MIB::matrixSDErrors,Counter32,read-only,,current,,The number of bad packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.3,RMON-MIB::matrixDSTable,,not-accessible,,current,,A list of traffic matrix entries indexed by destination and source MAC address.
.1.3.6.1.2.1.16.6.3.1,RMON-MIB::matrixDSEntry,,not-accessible,matrixDSIndex:matrixDSDestAddress:matrixDSSourceAddress,current,,A collection of statistics for communications between two addresses on a particular interface. For example, an instance of the matrixSDPkts object might be named matrixSDPkts.1.6.8.0.32.10.8.113.6.8.0.32.27.3.176
.1.3.6.1.2.1.16.6.3.1.1,RMON-MIB::matrixDSSourceAddress,OCTET,read-only,,current,,The source physical address.
.1.3.6.1.2.1.16.6.3.1.2,RMON-MIB::matrixDSDestAddress,OCTET,read-only,,current,,The destination physical address.
.1.3.6.1.2.1.16.6.3.1.3,RMON-MIB::matrixDSIndex,Integer32,read-only,,current,,The set of collected matrix statistics of which this entry is a part. The set of matrix statistics identified by a particular value of this index is associated with the same matrixControlEntry as identified by the same value of matrixControlIndex.
.1.3.6.1.2.1.16.6.3.1.4,RMON-MIB::matrixDSPkts,Counter32,read-only,,current,,The number of packets transmitted from the source address to the destination address (this number includes bad packets).
.1.3.6.1.2.1.16.6.3.1.5,RMON-MIB::matrixDSOctets,Counter32,read-only,,current,,The number of octets (excluding framing bits but including FCS octets) contained in all packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.3.1.6,RMON-MIB::matrixDSErrors,Counter32,read-only,,current,,The number of bad packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.4,RMON2-MIB::matrixControl2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.6.4.1,RMON2-MIB::matrixControl2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.6.4.1.1,RMON2-MIB::matrixControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.6.4.1.2,RMON2-MIB::matrixControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.6.5,HC-RMON-MIB::matrixSDHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 matrixSDTable.
.1.3.6.1.2.1.16.6.5.1,HC-RMON-MIB::matrixSDHighCapacityEntry,,not-accessible,matrixSDIndex:matrixSDSourceAddress:matrixSDDestAddress,current,,Contains the High Capacity RMON extensions to the RMON-1 matrixSDEntry. These objects will be created by the agent for all matrixSDEntries associated with whichever matrixControlEntries it deems appropriate. (i.e., either all matrixSDHighCapacityEntries associated with a particular matrixControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.6.5.1.1,HC-RMON-MIB::matrixSDHighCapacityOverflowPkts,Counter32,read-only,,current,,The number of times the associated matrixSDPkts counter has overflowed.
.1.3.6.1.2.1.16.6.5.1.2,HC-RMON-MIB::matrixSDHighCapacityPkts,Counter64,read-only,,current,,The number of packets transmitted from the source address to the destination address (this number includes bad packets).
.1.3.6.1.2.1.16.6.5.1.3,HC-RMON-MIB::matrixSDHighCapacityOverflowOctets,Counter32,read-only,,current,,The number of times the associated matrixSDOctets counter has overflowed.
.1.3.6.1.2.1.16.6.5.1.4,HC-RMON-MIB::matrixSDHighCapacityOctets,Counter64,read-only,,current,,The number of octets (excluding framing bits but including FCS octets) contained in all packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.6.6,HC-RMON-MIB::matrixDSHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 matrixDSTable.
.1.3.6.1.2.1.16.6.6.1,HC-RMON-MIB::matrixDSHighCapacityEntry,,not-accessible,matrixDSIndex:matrixDSDestAddress:matrixDSSourceAddress,current,,Contains the High Capacity RMON extensions to the RMON-1 matrixDSEntry. These objects will be created by the agent for all matrixDSEntries associated with whichever matrixControlEntries it deems appropriate. (i.e., either all matrixDSHighCapacityEntries associated with a particular matrixControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.6.6.1.1,HC-RMON-MIB::matrixDSHighCapacityOverflowPkts,Counter32,read-only,,current,,The number of times the associated matrixDSPkts counter has overflowed.
.1.3.6.1.2.1.16.6.6.1.2,HC-RMON-MIB::matrixDSHighCapacityPkts,Counter64,read-only,,current,,The number of packets transmitted from the source address to the destination address (this number includes bad packets).
.1.3.6.1.2.1.16.6.6.1.3,HC-RMON-MIB::matrixDSHighCapacityOverflowOctets,Counter32,read-only,,current,,The number of times the associated matrixDSOctets counter has overflowed.
.1.3.6.1.2.1.16.6.6.1.4,HC-RMON-MIB::matrixDSHighCapacityOctets,Counter64,read-only,,current,,The number of octets (excluding framing bits but including FCS octets) contained in all packets transmitted from the source address to the destination address.
.1.3.6.1.2.1.16.7,RMON-MIB::filter,,,,,,
.1.3.6.1.2.1.16.7.1,RMON-MIB::filterTable,,not-accessible,,current,,A list of packet filter entries.
.1.3.6.1.2.1.16.7.1.1,RMON-MIB::filterEntry,,not-accessible,filterIndex,current,,A set of parameters for a packet filter applied on a particular interface. As an example, an instance of the filterPktData object might be named filterPktData.12
.1.3.6.1.2.1.16.7.1.1.1,RMON-MIB::filterIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the filter table. Each such entry defines one filter that is to be applied to every packet received on an interface.
.1.3.6.1.2.1.16.7.1.1.2,RMON-MIB::filterChannelIndex,Integer32,read-create,,current,,This object identifies the channel of which this filter is a part. The filters identified by a particular value of this object are associated with the same channel as identified by the same value of the channelIndex object.
.1.3.6.1.2.1.16.7.1.1.3,RMON-MIB::filterPktDataOffset,Integer32,read-create,,current,,The offset from the beginning of each packet where a match of packet data will be attempted. This offset is measured from the point in the physical layer packet after the framing bits, if any. For example, in an Ethernet frame, this point is at the beginning of the destination MAC address. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.4,RMON-MIB::filterPktData,OCTET,read-create,,current,,The data that is to be matched with the input packet. For each packet received, this filter and the accompanying filterPktDataMask and filterPktDataNotMask will be adjusted for the offset. The only bits relevant to this match algorithm are those that have the corresponding filterPktDataMask bit equal to one. The following three rules are then applied to every packet: (1) If the packet is too short and does not have data corresponding to part of the filterPktData, the packet will fail this data match. (2) For each relevant bit from the packet with the corresponding filterPktDataNotMask bit set to zero, if the bit from the packet is not equal to the corresponding bit from the filterPktData, then the packet will fail this data match. (3) If for every relevant bit from the packet with the corresponding filterPktDataNotMask bit set to one, the bit from the packet is equal to the corresponding bit from the filterPktData, then the packet will fail this data match. Any packets that have not failed any of the three matches above have passed this data match. In particular, a zero length filter will match any packet. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.5,RMON-MIB::filterPktDataMask,OCTET,read-create,,current,,The mask that is applied to the match process. After adjusting this mask for the offset, only those bits in the received packet that correspond to bits set in this mask are relevant for further processing by the match algorithm. The offset is applied to filterPktDataMask in the same way it is applied to the filter. For the purposes of the matching algorithm, if the associated filterPktData object is longer than this mask, this mask is conceptually extended with '1' bits until it reaches the length of the filterPktData object. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.6,RMON-MIB::filterPktDataNotMask,OCTET,read-create,,current,,The inversion mask that is applied to the match process. After adjusting this mask for the offset, those relevant bits in the received packet that correspond to bits cleared in this mask must all be equal to their corresponding bits in the filterPktData object for the packet to be accepted. In addition, at least one of those relevant bits in the received packet that correspond to bits set in this mask must be different to its corresponding bit in the filterPktData object. For the purposes of the matching algorithm, if the associated filterPktData object is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the length of the filterPktData object. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.7,RMON-MIB::filterPktStatus,Integer32,read-create,,current,,The status that is to be matched with the input packet. The only bits relevant to this match algorithm are those that have the corresponding filterPktStatusMask bit equal to one. The following two rules are then applied to every packet: (1) For each relevant bit from the packet status with the corresponding filterPktStatusNotMask bit set to zero, if the bit from the packet status is not equal to the corresponding bit from the filterPktStatus, then the packet will fail this status match. (2) If for every relevant bit from the packet status with the corresponding filterPktStatusNotMask bit set to one, the bit from the packet status is equal to the corresponding bit from the filterPktStatus, then the packet will fail this status match. Any packets that have not failed either of the two matches above have passed this status match. In particular, a zero length status filter will match any packet's status. The value of the packet status is a sum. This sum initially takes the value zero. Then, for each error, E, that has been discovered in this packet, 2 raised to a value representing E is added to the sum. The errors and the bits that represent them are dependent on the media type of the interface that this channel is receiving packets from. The errors defined for a packet captured off of an Ethernet interface are as follows: bit # Error 0 Packet is longer than 1518 octets 1 Packet is shorter than 64 octets 2 Packet experienced a CRC or Alignment error For example, an Ethernet fragment would have a value of 6 (2^1 + 2^2). As this MIB is expanded to new media types, this object will have other media-specific errors defined. For the purposes of this status matching algorithm, if the packet status is longer than this filterPktStatus object, this object is conceptually extended with '0' bits until it reaches the size of the packet status. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.8,RMON-MIB::filterPktStatusMask,Integer32,read-create,,current,,The mask that is applied to the status match process. Only those bits in the received packet that correspond to bits set in this mask are relevant for further processing by the status match algorithm. For the purposes of the matching algorithm, if the associated filterPktStatus object is longer than this mask, this mask is conceptually extended with '1' bits until it reaches the size of the filterPktStatus. In addition, if a packet status is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the size of the packet status. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.9,RMON-MIB::filterPktStatusNotMask,Integer32,read-create,,current,,The inversion mask that is applied to the status match process. Those relevant bits in the received packet status that correspond to bits cleared in this mask must all be equal to their corresponding bits in the filterPktStatus object for the packet to be accepted. In addition, at least one of those relevant bits in the received packet status that correspond to bits set in this mask must be different to its corresponding bit in the filterPktStatus object for the packet to be accepted. For the purposes of the matching algorithm, if the associated filterPktStatus object or a packet status is longer than this mask, this mask is conceptually extended with '0' bits until it reaches the longer of the lengths of the filterPktStatus object and the packet status. This object may not be modified if the associated filterStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.1.1.10,RMON-MIB::filterOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.7.1.1.11,RMON-MIB::filterStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this filter entry.
.1.3.6.1.2.1.16.7.2,RMON-MIB::channelTable,,not-accessible,,current,,A list of packet channel entries.
.1.3.6.1.2.1.16.7.2.1,RMON-MIB::channelEntry,,not-accessible,channelIndex,current,,A set of parameters for a packet channel applied on a particular interface. As an example, an instance of the channelMatches object might be named channelMatches.3
.1.3.6.1.2.1.16.7.2.1.1,RMON-MIB::channelIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the channel table. Each such entry defines one channel, a logical data and event stream. It is suggested that before creating a channel, an application should scan all instances of the filterChannelIndex object to make sure that there are no pre-existing filters that would be inadvertently be linked to the channel.
.1.3.6.1.2.1.16.7.2.1.2,RMON-MIB::channelIfIndex,Integer32,read-create,,current,,The value of this object uniquely identifies the interface on this remote network monitoring device to which the associated filters are applied to allow data into this channel. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in RFC 2233 [17]. The filters in this group are applied to all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate an invalidation of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it invalidate this entry. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.3,RMON-MIB::channelAcceptType,INTEGER,read-create,,current,acceptMatched(1):acceptFailed(2),This object controls the action of the filters associated with this channel. If this object is equal to acceptMatched(1), packets will be accepted to this channel if they are accepted by both the packet data and packet status matches of an associated filter. If this object is equal to acceptFailed(2), packets will be accepted to this channel only if they fail either the packet data match or the packet status match of each of the associated filters. In particular, a channel with no associated filters will match no packets if set to acceptMatched(1) case and will match all packets in the acceptFailed(2) case. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.4,RMON-MIB::channelDataControl,INTEGER,read-create,,current,on(1):off(2),This object controls the flow of data through this channel. If this object is on(1), data, status and events flow through this channel. If this object is off(2), data, status and events will not flow through this channel.
.1.3.6.1.2.1.16.7.2.1.5,RMON-MIB::channelTurnOnEventIndex,Integer32,read-create,,current,,The value of this object identifies the event that is configured to turn the associated channelDataControl from off to on when the event is generated. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelTurnOnEventIndex must be set to zero, a non-existent event index. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.6,RMON-MIB::channelTurnOffEventIndex,Integer32,read-create,,current,,The value of this object identifies the event that is configured to turn the associated channelDataControl from on to off when the event is generated. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelTurnOffEventIndex must be set to zero, a non-existent event index. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.7,RMON-MIB::channelEventIndex,Integer32,read-create,,current,,The value of this object identifies the event that is configured to be generated when the associated channelDataControl is on and a packet is matched. The event identified by a particular value of this object is the same event as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In fact, if no event is intended for this channel, channelEventIndex must be set to zero, a non-existent event index. This object may not be modified if the associated channelStatus object is equal to valid(1).
.1.3.6.1.2.1.16.7.2.1.8,RMON-MIB::channelEventStatus,INTEGER,read-create,,current,eventReady(1):eventFired(2):eventAlwaysReady(3),The event status of this channel. If this channel is configured to generate events when packets are matched, a means of controlling the flow of those events is often needed. When this object is equal to eventReady(1), a single event may be generated, after which this object will be set by the probe to eventFired(2). While in the eventFired(2) state, no events will be generated until the object is modified to eventReady(1) (or eventAlwaysReady(3)). The management station can thus easily respond to a notification of an event by re-enabling this object. If the management station wishes to disable this flow control and allow events to be generated at will, this object may be set to eventAlwaysReady(3). Disabling the flow control is discouraged as it can result in high network traffic or other performance problems.
.1.3.6.1.2.1.16.7.2.1.9,RMON-MIB::channelMatches,Counter32,read-only,,current,,The number of times this channel has matched a packet. Note that this object is updated even when channelDataControl is set to off.
.1.3.6.1.2.1.16.7.2.1.10,RMON-MIB::channelDescription,OCTET,read-create,,current,,A comment describing this channel.
.1.3.6.1.2.1.16.7.2.1.11,RMON-MIB::channelOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.7.2.1.12,RMON-MIB::channelStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this channel entry.
.1.3.6.1.2.1.16.7.3,RMON2-MIB::channel2Table,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.7.3.1,RMON2-MIB::channel2Entry,,not-accessible,,current,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.7.3.1.1,RMON2-MIB::channelDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.7.3.1.2,RMON2-MIB::channelCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.7.4,RMON2-MIB::filter2Table,,not-accessible,,current,,Provides a variable-length packet filter feature to the RMON-1 filter table.
.1.3.6.1.2.1.16.7.4.1,RMON2-MIB::filter2Entry,,not-accessible,,current,,Provides a variable-length packet filter feature to the RMON-1 filter table.
.1.3.6.1.2.1.16.7.4.1.1,RMON2-MIB::filterProtocolDirDataLocalIndex,Integer32,read-create,,current,,When this object is set to a non-zero value, the filter that it is associated with performs the following operations on every packet: 1) If the packet doesn't match the protocol directory entry identified by this object, discard the packet and exit (i.e., discard the packet if it is not of the identified protocol). 2) If the associated filterProtocolDirLocalIndex is non-zero and the packet doesn't match the protocol directory entry identified by that object, discard the packet and exit. 3) If the packet matches, perform the regular filter algorithm as if the beginning of this named protocol is the beginning of the packet, potentially applying the filterOffset value to move further into the packet.
.1.3.6.1.2.1.16.7.4.1.2,RMON2-MIB::filterProtocolDirLocalIndex,Integer32,read-create,,current,,When this object is set to a non-zero value, the filter that it is associated with will discard the packet if the packet doesn't match this protocol directory entry.
.1.3.6.1.2.1.16.8,RMON-MIB::capture,,,,,,
.1.3.6.1.2.1.16.8.1,RMON-MIB::bufferControlTable,,not-accessible,,current,,A list of buffers control entries.
.1.3.6.1.2.1.16.8.1.1,RMON-MIB::bufferControlEntry,,not-accessible,bufferControlIndex,current,,A set of parameters that control the collection of a stream of packets that have matched filters. As an example, an instance of the bufferControlCaptureSliceSize object might be named bufferControlCaptureSliceSize.3
.1.3.6.1.2.1.16.8.1.1.1,RMON-MIB::bufferControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the bufferControl table. The value of this index shall never be zero. Each such entry defines one set of packets that is captured and controlled by one or more filters.
.1.3.6.1.2.1.16.8.1.1.2,RMON-MIB::bufferControlChannelIndex,Integer32,read-create,,current,,An index that identifies the channel that is the source of packets for this bufferControl table. The channel identified by a particular value of this index is the same as identified by the same value of the channelIndex object. This object may not be modified if the associated bufferControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.8.1.1.3,RMON-MIB::bufferControlFullStatus,INTEGER,read-only,,current,spaceAvailable(1):full(2),This object shows whether the buffer has room to accept new packets or if it is full. If the status is spaceAvailable(1), the buffer is accepting new packets normally. If the status is full(2) and the associated bufferControlFullAction object is wrapWhenFull, the buffer is accepting new packets by deleting enough of the oldest packets to make room for new ones as they arrive. Otherwise, if the status is full(2) and the bufferControlFullAction object is lockWhenFull, then the buffer has stopped collecting packets. When this object is set to full(2) the probe must not later set it to spaceAvailable(1) except in the case of a significant gain in resources such as an increase of bufferControlOctetsGranted. In particular, the wrap-mode action of deleting old packets to make room for newly arrived packets must not affect the value of this object.
.1.3.6.1.2.1.16.8.1.1.4,RMON-MIB::bufferControlFullAction,INTEGER,read-create,,current,lockWhenFull(1):wrapWhenFull(2),Controls the action of the buffer when it reaches the full status. When in the lockWhenFull(1) state and a packet is added to the buffer that fills the buffer, the bufferControlFullStatus will be set to full(2) and this buffer will stop capturing packets.
.1.3.6.1.2.1.16.8.1.1.5,RMON-MIB::bufferControlCaptureSliceSize,Integer32,read-create,,current,,The maximum number of octets of each packet that will be saved in this capture buffer. For example, if a 1500 octet packet is received by the probe and this object is set to 500, then only 500 octets of the packet will be stored in the associated capture buffer. If this variable is set to 0, the capture buffer will save as many octets as is possible. This object may not be modified if the associated bufferControlStatus object is equal to valid(1).
.1.3.6.1.2.1.16.8.1.1.6,RMON-MIB::bufferControlDownloadSliceSize,Integer32,read-create,,current,,The maximum number of octets of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. For example, if 500 octets of a packet have been stored in the associated capture buffer, the associated bufferControlDownloadOffset is 0, and this object is set to 100, then the captureBufferPacket object that contains the packet will contain only the first 100 octets of the packet. A prudent manager will take into account possible interoperability or fragmentation problems that may occur if the download slice size is set too large. In particular, conformant SNMP implementations are not required to accept messages whose length exceeds 484 octets, although they are encouraged to support larger datagrams whenever feasible.
.1.3.6.1.2.1.16.8.1.1.7,RMON-MIB::bufferControlDownloadOffset,Integer32,read-create,,current,,The offset of the first octet of each packet in this capture buffer that will be returned in an SNMP retrieval of that packet. For example, if 500 octets of a packet have been stored in the associated capture buffer and this object is set to 100, then the captureBufferPacket object that contains the packet will contain bytes starting 100 octets into the packet.
.1.3.6.1.2.1.16.8.1.1.8,RMON-MIB::bufferControlMaxOctetsRequested,Integer32,read-create,,current,,The requested maximum number of octets to be saved in this captureBuffer, including any implementation-specific overhead. If this variable is set to -1, the capture buffer will save as many octets as is possible. When this object is created or modified, the probe should set bufferControlMaxOctetsGranted as closely to this object as is possible for the particular probe implementation and available resources. However, if the object has the special value of -1, the probe must set bufferControlMaxOctetsGranted to -1.
.1.3.6.1.2.1.16.8.1.1.9,RMON-MIB::bufferControlMaxOctetsGranted,Integer32,read-only,,current,,The maximum number of octets that can be saved in this captureBuffer, including overhead. If this variable is -1, the capture buffer will save as many octets as possible. When the bufferControlMaxOctetsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. However, if the request object has the special value of -1, the probe must set this object to -1. The probe must not lower this value except as a result of a modification to the associated bufferControlMaxOctetsRequested object. When this maximum number of octets is reached and a new packet is to be added to this capture buffer and the corresponding bufferControlFullAction is set to wrapWhenFull(2), enough of the oldest packets associated with this capture buffer shall be deleted by the agent so that the new packet can be added. If the corresponding bufferControlFullAction is set to lockWhenFull(1), the new packet shall be discarded. In either case, the probe must set bufferControlFullStatus to full(2). When the value of this object changes to a value less than the current value, entries are deleted from the captureBufferTable associated with this bufferControlEntry. Enough of the oldest of these captureBufferEntries shall be deleted by the agent so that the number of octets used remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated captureBufferEntries may be allowed to grow.
.1.3.6.1.2.1.16.8.1.1.10,RMON-MIB::bufferControlCapturedPackets,Integer32,read-only,,current,,The number of packets currently in this captureBuffer.
.1.3.6.1.2.1.16.8.1.1.11,RMON-MIB::bufferControlTurnOnTime,TimeTicks,read-only,,current,,The value of sysUpTime when this capture buffer was first turned on.
.1.3.6.1.2.1.16.8.1.1.12,RMON-MIB::bufferControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.8.1.1.13,RMON-MIB::bufferControlStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this buffer Control Entry.
.1.3.6.1.2.1.16.8.2,RMON-MIB::captureBufferTable,,not-accessible,,current,,A list of packets captured off of a channel.
.1.3.6.1.2.1.16.8.2.1,RMON-MIB::captureBufferEntry,,not-accessible,captureBufferControlIndex:captureBufferIndex,current,,A packet captured off of an attached network. As an example, an instance of the captureBufferPacketData object might be named captureBufferPacketData.3.1783
.1.3.6.1.2.1.16.8.2.1.1,RMON-MIB::captureBufferControlIndex,Integer32,read-only,,current,,The index of the bufferControlEntry with which this packet is associated.
.1.3.6.1.2.1.16.8.2.1.2,RMON-MIB::captureBufferIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the captureBuffer table associated with a particular bufferControlEntry. This index will start at 1 and increase by one for each new packet added with the same captureBufferControlIndex. Should this value reach 2147483647, the next packet added with the same captureBufferControlIndex shall cause this value to wrap around to 1.
.1.3.6.1.2.1.16.8.2.1.3,RMON-MIB::captureBufferPacketID,Integer32,read-only,,current,,An index that describes the order of packets that are received on a particular interface. The packetID of a packet captured on an interface is defined to be greater than the packetID's of all packets captured previously on the same interface. As the captureBufferPacketID object has a maximum positive value of 2^31 - 1, any captureBufferPacketID object shall have the value of the associated packet's packetID mod 2^31.
.1.3.6.1.2.1.16.8.2.1.4,RMON-MIB::captureBufferPacketData,OCTET,read-only,,current,,The data inside the packet, starting at the beginning of the packet plus any offset specified in the associated bufferControlDownloadOffset, including any link level headers. The length of the data in this object is the minimum of the length of the captured packet minus the offset, the length of the associated bufferControlCaptureSliceSize minus the offset, and the associated bufferControlDownloadSliceSize. If this minimum is less than zero, this object shall have a length of zero.
.1.3.6.1.2.1.16.8.2.1.5,RMON-MIB::captureBufferPacketLength,Integer32,read-only,,current,,The actual length (off the wire) of the packet stored in this entry, including FCS octets.
.1.3.6.1.2.1.16.8.2.1.6,RMON-MIB::captureBufferPacketTime,Integer32,read-only,,current,,The number of milliseconds that had passed since this capture buffer was first turned on when this packet was captured.
.1.3.6.1.2.1.16.8.2.1.7,RMON-MIB::captureBufferPacketStatus,Integer32,read-only,,current,,A value which indicates the error status of this packet. The value of this object is defined in the same way as filterPktStatus. The value is a sum. This sum initially takes the value zero. Then, for each error, E, that has been discovered in this packet, 2 raised to a value representing E is added to the sum. The errors defined for a packet captured off of an Ethernet interface are as follows: bit # Error 0 Packet is longer than 1518 octets 1 Packet is shorter than 64 octets 2 Packet experienced a CRC or Alignment error 3 First packet in this capture buffer after it was detected that some packets were not processed correctly. 4 Packet's order in buffer is only approximate (May only be set for packets sent from the probe) For example, an Ethernet fragment would have a value of 6 (2^1 + 2^2). As this MIB is expanded to new media types, this object will have other media-specific errors defined.
.1.3.6.1.2.1.16.8.3,HC-RMON-MIB::captureBufferHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-1 captureBufferTable.
.1.3.6.1.2.1.16.8.3.1,HC-RMON-MIB::captureBufferHighCapacityEntry,,not-accessible,captureBufferControlIndex:captureBufferIndex,current,,Contains the High Capacity RMON extensions to the RMON-1 captureBufferEntry. These objects will be created by the agent for all captureBufferEntries associated with whichever bufferControlEntries it deems appropriate. (i.e., either all captureBufferHighCapacityEntries associated with a particular bufferControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.8.3.1.1,HC-RMON-MIB::captureBufferPacketHighCapacityTime,Integer32,read-only,,current,,The number of nanoseconds that had passed since this capture buffer was first turned on when this packet was captured, modulo 10^6. This object is used in conjunction with the captureBufferPacketTime object. This object returns the number of nano-seconds to be added to to number of milli-seconds obtained from the captureBufferPacketTime object, to obtain more accurate inter packet arrival time.
.1.3.6.1.2.1.16.9,RMON-MIB::event,,,,,,
.1.3.6.1.2.1.16.9.1,RMON-MIB::eventTable,,not-accessible,,current,,A list of events to be generated.
.1.3.6.1.2.1.16.9.1.1,RMON-MIB::eventEntry,,not-accessible,eventIndex,current,,A set of parameters that describe an event to be generated when certain conditions are met. As an example, an instance of the eventLastTimeSent object might be named eventLastTimeSent.6
.1.3.6.1.2.1.16.9.1.1.1,RMON-MIB::eventIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the event table. Each such entry defines one event that is to be generated when the appropriate conditions occur.
.1.3.6.1.2.1.16.9.1.1.2,RMON-MIB::eventDescription,OCTET,read-create,,current,,A comment describing this event entry.
.1.3.6.1.2.1.16.9.1.1.3,RMON-MIB::eventType,INTEGER,read-create,,current,none(1):log(2):snmptrap(3):logandtrap(4),The type of notification that the probe will make about this event. In the case of log, an entry is made in the log table for each event. In the case of snmp-trap, an SNMP trap is sent to one or more management stations.
.1.3.6.1.2.1.16.9.1.1.4,RMON-MIB::eventCommunity,OCTET,read-create,,current,,If an SNMP trap is to be sent, it will be sent to the SNMP community specified by this octet string.
.1.3.6.1.2.1.16.9.1.1.5,RMON-MIB::eventLastTimeSent,TimeTicks,read-only,,current,,The value of sysUpTime at the time this event entry last generated an event. If this entry has not generated any events, this value will be zero.
.1.3.6.1.2.1.16.9.1.1.6,RMON-MIB::eventOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it. If this object contains a string starting with 'monitor' and has associated entries in the log table, all connected management stations should retrieve those log entries, as they may have significance to all management stations connected to this device
.1.3.6.1.2.1.16.9.1.1.7,RMON-MIB::eventStatus,INTEGER,read-create,,current,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this event entry. If this object is not equal to valid(1), all associated log entries shall be deleted by the agent.
.1.3.6.1.2.1.16.9.2,RMON-MIB::logTable,,not-accessible,,current,,A list of events that have been logged.
.1.3.6.1.2.1.16.9.2.1,RMON-MIB::logEntry,,not-accessible,logEventIndex:logIndex,current,,A set of data describing an event that has been logged. For example, an instance of the logDescription object might be named logDescription.6.47
.1.3.6.1.2.1.16.9.2.1.1,RMON-MIB::logEventIndex,Integer32,read-only,,current,,The event entry that generated this log entry. The log identified by a particular value of this index is associated with the same eventEntry as identified by the same value of eventIndex.
.1.3.6.1.2.1.16.9.2.1.2,RMON-MIB::logIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the log table amongst those generated by the same eventEntries. These indexes are assigned beginning with 1 and increase by one with each new log entry. The association between values of logIndex and logEntries is fixed for the lifetime of each logEntry. The agent may choose to delete the oldest instances of logEntry as required because of lack of memory. It is an implementation-specific matter as to when this deletion may occur.
.1.3.6.1.2.1.16.9.2.1.3,RMON-MIB::logTime,TimeTicks,read-only,,current,,The value of sysUpTime when this log entry was created.
.1.3.6.1.2.1.16.9.2.1.4,RMON-MIB::logDescription,OCTET,read-only,,current,,An implementation dependent description of the event that activated this log entry.
.1.3.6.1.2.1.16.10,TOKEN-RING-RMON-MIB::tokenRing,,,,,,
.1.3.6.1.2.1.16.10.1,TOKEN-RING-RMON-MIB::ringStationControlTable,,not-accessible,,mandatory,,A list of ringStation table control entries.
.1.3.6.1.2.1.16.10.1.1,TOKEN-RING-RMON-MIB::ringStationControlEntry,,not-accessible,ringStationControlIfIndex,mandatory,,A list of parameters that set up the discovery of stations on a particular interface and the collection of statistics about these stations.
.1.3.6.1.2.1.16.10.1.1.1,TOKEN-RING-RMON-MIB::ringStationControlIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device from which ringStation data is collected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB- II [3].
.1.3.6.1.2.1.16.10.1.1.2,TOKEN-RING-RMON-MIB::ringStationControlTableSize,INTEGER,read-only,,mandatory,,The number of ringStationEntries in the ringStationTable associated with this ringStationControlEntry.
.1.3.6.1.2.1.16.10.1.1.3,TOKEN-RING-RMON-MIB::ringStationControlActiveStations,INTEGER,read-only,,mandatory,,The number of active ringStationEntries in the ringStationTable associated with this ringStationControlEntry.
.1.3.6.1.2.1.16.10.1.1.4,TOKEN-RING-RMON-MIB::ringStationControlRingState,INTEGER,read-only,,mandatory,normalOperation(1):ringPurgeState(2):claimTokenState(3):beaconFrameStreamingState(4):beaconBitStreamingState(5):beaconRingSignalLossState(6):beaconSetRecoveryModeState(7),The current status of this ring.
.1.3.6.1.2.1.16.10.1.1.5,TOKEN-RING-RMON-MIB::ringStationControlBeaconSender,OCTET,read-only,,mandatory,,The address of the sender of the last beacon frame received by the probe on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero.
.1.3.6.1.2.1.16.10.1.1.6,TOKEN-RING-RMON-MIB::ringStationControlBeaconNAUN,OCTET,read-only,,mandatory,,The address of the NAUN in the last beacon frame received by the probe on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero.
.1.3.6.1.2.1.16.10.1.1.7,TOKEN-RING-RMON-MIB::ringStationControlActiveMonitor,OCTET,read-only,,mandatory,,The address of the Active Monitor on this segment. If this address is unknown, this object shall be equal to six octets of zero.
.1.3.6.1.2.1.16.10.1.1.8,TOKEN-RING-RMON-MIB::ringStationControlOrderChanges,Counter32,read-only,,mandatory,,The number of add and delete events in the ringStationOrderTable optionally associated with this ringStationControlEntry.
.1.3.6.1.2.1.16.10.1.1.9,TOKEN-RING-RMON-MIB::ringStationControlOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.10.1.1.10,TOKEN-RING-RMON-MIB::ringStationControlStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this ringStationControl entry. If this object is not equal to valid(1), all associated entries in the ringStationTable shall be deleted by the agent.
.1.3.6.1.2.1.16.10.2,TOKEN-RING-RMON-MIB::ringStationTable,,not-accessible,,mandatory,,A list of ring station entries. An entry will exist for each station that is now or has previously been detected as physically present on this ring.
.1.3.6.1.2.1.16.10.2.1,TOKEN-RING-RMON-MIB::ringStationEntry,,not-accessible,ringStationIfIndex:ringStationMacAddress,mandatory,,A collection of statistics for a particular station that has been discovered on a ring monitored by this device.
.1.3.6.1.2.1.16.10.2.1.1,TOKEN-RING-RMON-MIB::ringStationIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.2.1.2,TOKEN-RING-RMON-MIB::ringStationMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.2.1.3,TOKEN-RING-RMON-MIB::ringStationLastNAUN,OCTET,read-only,,mandatory,,The physical address of last known NAUN of this station.
.1.3.6.1.2.1.16.10.2.1.4,TOKEN-RING-RMON-MIB::ringStationStationStatus,INTEGER,read-only,,mandatory,active(1):inactive(2):forcedRemoval(3),The status of this station on the ring.
.1.3.6.1.2.1.16.10.2.1.5,TOKEN-RING-RMON-MIB::ringStationLastEnterTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time this station last entered the ring. If the time is unknown, this value shall be zero.
.1.3.6.1.2.1.16.10.2.1.6,TOKEN-RING-RMON-MIB::ringStationLastExitTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time the probe detected that this station last exited the ring. If the time is unknown, this value shall be zero.
.1.3.6.1.2.1.16.10.2.1.7,TOKEN-RING-RMON-MIB::ringStationDuplicateAddresses,Counter32,read-only,,mandatory,,The number of times this station experienced a duplicate address error.
.1.3.6.1.2.1.16.10.2.1.8,TOKEN-RING-RMON-MIB::ringStationInLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.9,TOKEN-RING-RMON-MIB::ringStationOutLineErrors,Counter32,read-only,,mandatory,,The total number of line errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.10,TOKEN-RING-RMON-MIB::ringStationInternalErrors,Counter32,read-only,,mandatory,,The total number of adapter internal errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.11,TOKEN-RING-RMON-MIB::ringStationInBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.12,TOKEN-RING-RMON-MIB::ringStationOutBurstErrors,Counter32,read-only,,mandatory,,The total number of burst errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.13,TOKEN-RING-RMON-MIB::ringStationACErrors,Counter32,read-only,,mandatory,,The total number of AC (Address Copied) errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.14,TOKEN-RING-RMON-MIB::ringStationAbortErrors,Counter32,read-only,,mandatory,,The total number of abort delimiters reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.15,TOKEN-RING-RMON-MIB::ringStationLostFrameErrors,Counter32,read-only,,mandatory,,The total number of lost frame errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.16,TOKEN-RING-RMON-MIB::ringStationCongestionErrors,Counter32,read-only,,mandatory,,The total number of receive congestion errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.17,TOKEN-RING-RMON-MIB::ringStationFrameCopiedErrors,Counter32,read-only,,mandatory,,The total number of frame copied errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.18,TOKEN-RING-RMON-MIB::ringStationFrequencyErrors,Counter32,read-only,,mandatory,,The total number of frequency errors reported by this station in error reporting packets detected by the probe.
.1.3.6.1.2.1.16.10.2.1.19,TOKEN-RING-RMON-MIB::ringStationTokenErrors,Counter32,read-only,,mandatory,,The total number of token errors reported by this station in error reporting frames detected by the probe.
.1.3.6.1.2.1.16.10.2.1.20,TOKEN-RING-RMON-MIB::ringStationInBeaconErrors,Counter32,read-only,,mandatory,,The total number of beacon frames sent by this station and detected by the probe.
.1.3.6.1.2.1.16.10.2.1.21,TOKEN-RING-RMON-MIB::ringStationOutBeaconErrors,Counter32,read-only,,mandatory,,The total number of beacon frames detected by the probe that name this station as the NAUN.
.1.3.6.1.2.1.16.10.2.1.22,TOKEN-RING-RMON-MIB::ringStationInsertions,Counter32,read-only,,mandatory,,The number of times the probe detected this station inserting onto the ring.
.1.3.6.1.2.1.16.10.3,TOKEN-RING-RMON-MIB::ringStationOrderTable,,not-accessible,,mandatory,,A list of ring station entries for stations in the ring poll, ordered by their ring-order.
.1.3.6.1.2.1.16.10.3.1,TOKEN-RING-RMON-MIB::ringStationOrderEntry,,not-accessible,ringStationOrderIfIndex:ringStationOrderOrderIndex,mandatory,,A collection of statistics for a particular station that is active on a ring monitored by this device. This table will contain information for every interface that has a ringStationControlStatus equal to valid.
.1.3.6.1.2.1.16.10.3.1.1,TOKEN-RING-RMON-MIB::ringStationOrderIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.3.1.2,TOKEN-RING-RMON-MIB::ringStationOrderOrderIndex,INTEGER,read-only,,mandatory,,This index denotes the location of this station with respect to other stations on the ring. This index is one more than the number of hops downstream that this station is from the rmon probe. The rmon probe itself gets the value one.
.1.3.6.1.2.1.16.10.3.1.3,TOKEN-RING-RMON-MIB::ringStationOrderMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.4,TOKEN-RING-RMON-MIB::ringStationConfigControlTable,,not-accessible,,mandatory,,A list of ring station configuration control entries.
.1.3.6.1.2.1.16.10.4.1,TOKEN-RING-RMON-MIB::ringStationConfigControlEntry,,not-accessible,ringStationConfigControlIfIndex:ringStationConfigControlMacAddress,mandatory,,This entry controls active management of stations by the probe. One entry exists in this table for each active station in the ringStationTable.
.1.3.6.1.2.1.16.10.4.1.1,TOKEN-RING-RMON-MIB::ringStationConfigControlIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.4.1.2,TOKEN-RING-RMON-MIB::ringStationConfigControlMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.4.1.3,TOKEN-RING-RMON-MIB::ringStationConfigControlRemove,INTEGER,read-write,,mandatory,stable(1):removing(2),Setting this object to `removing(2)' causes a Remove Station MAC frame to be sent. The agent will set this object to `stable(1)' after processing the request.
.1.3.6.1.2.1.16.10.4.1.4,TOKEN-RING-RMON-MIB::ringStationConfigControlUpdateStats,INTEGER,read-write,,mandatory,stable(1):updating(2),Setting this object to `updating(2)' causes the configuration information associate with this entry to be updated. The agent will set this object to `stable(1)' after processing the request.
.1.3.6.1.2.1.16.10.5,TOKEN-RING-RMON-MIB::ringStationConfigTable,,not-accessible,,mandatory,,A list of configuration entries for stations on a ring monitored by this probe.
.1.3.6.1.2.1.16.10.5.1,TOKEN-RING-RMON-MIB::ringStationConfigEntry,,not-accessible,ringStationConfigIfIndex:ringStationConfigMacAddress,mandatory,,A collection of statistics for a particular station that has been discovered on a ring monitored by this probe.
.1.3.6.1.2.1.16.10.5.1.1,TOKEN-RING-RMON-MIB::ringStationConfigIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.5.1.2,TOKEN-RING-RMON-MIB::ringStationConfigMacAddress,OCTET,read-only,,mandatory,,The physical address of this station.
.1.3.6.1.2.1.16.10.5.1.3,TOKEN-RING-RMON-MIB::ringStationConfigUpdateTime,TimeTicks,read-only,,mandatory,,The value of sysUpTime at the time this configuration information was last updated (completely).
.1.3.6.1.2.1.16.10.5.1.4,TOKEN-RING-RMON-MIB::ringStationConfigLocation,OCTET,read-only,,mandatory,,The assigned physical location of this station.
.1.3.6.1.2.1.16.10.5.1.5,TOKEN-RING-RMON-MIB::ringStationConfigMicrocode,OCTET,read-only,,mandatory,,The microcode EC level of this station.
.1.3.6.1.2.1.16.10.5.1.6,TOKEN-RING-RMON-MIB::ringStationConfigGroupAddress,OCTET,read-only,,mandatory,,The low-order 4 octets of the group address recognized by this station.
.1.3.6.1.2.1.16.10.5.1.7,TOKEN-RING-RMON-MIB::ringStationConfigFunctionalAddress,OCTET,read-only,,mandatory,,the functional addresses recognized by this station.
.1.3.6.1.2.1.16.10.6,TOKEN-RING-RMON-MIB::sourceRoutingStatsTable,,not-accessible,,mandatory,,A list of source routing statistics entries.
.1.3.6.1.2.1.16.10.6.1,TOKEN-RING-RMON-MIB::sourceRoutingStatsEntry,,not-accessible,sourceRoutingStatsIfIndex,mandatory,,A collection of source routing statistics kept for a particular Token Ring interface.
.1.3.6.1.2.1.16.10.6.1.1,TOKEN-RING-RMON-MIB::sourceRoutingStatsIfIndex,INTEGER,read-only,,mandatory,,The value of this object uniquely identifies the interface on this remote network monitoring device on which source routing statistics will be detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in MIB-II [3].
.1.3.6.1.2.1.16.10.6.1.2,TOKEN-RING-RMON-MIB::sourceRoutingStatsRingNumber,INTEGER,read-only,,mandatory,,The ring number of the ring monitored by this entry. When any object in this entry is created, the probe will attempt to discover the ring number. Only after the ring number is discovered will this object be created. After creating an object in this entry, the management station should poll this object to detect when it is created. Only after this object is created can the management station set the sourceRoutingStatsStatus entry to valid(1).
.1.3.6.1.2.1.16.10.6.1.3,TOKEN-RING-RMON-MIB::sourceRoutingStatsInFrames,Counter32,read-only,,mandatory,,The count of frames sent into this ring from another ring.
.1.3.6.1.2.1.16.10.6.1.4,TOKEN-RING-RMON-MIB::sourceRoutingStatsOutFrames,Counter32,read-only,,mandatory,,The count of frames sent from this ring to another ring.
.1.3.6.1.2.1.16.10.6.1.5,TOKEN-RING-RMON-MIB::sourceRoutingStatsThroughFrames,Counter32,read-only,,mandatory,,The count of frames sent from another ring, through this ring, to another ring.
.1.3.6.1.2.1.16.10.6.1.6,TOKEN-RING-RMON-MIB::sourceRoutingStatsAllRoutesBroadcastFrames,Counter32,read-only,,mandatory,,The total number of good frames received that were All Routes Broadcast.
.1.3.6.1.2.1.16.10.6.1.7,TOKEN-RING-RMON-MIB::sourceRoutingStatsSingleRouteBroadcastFrames,Counter32,read-only,,mandatory,,The total number of good frames received that were Single Route Broadcast.
.1.3.6.1.2.1.16.10.6.1.8,TOKEN-RING-RMON-MIB::sourceRoutingStatsInOctets,Counter32,read-only,,mandatory,,The count of octets in good frames sent into this ring from another ring.
.1.3.6.1.2.1.16.10.6.1.9,TOKEN-RING-RMON-MIB::sourceRoutingStatsOutOctets,Counter32,read-only,,mandatory,,The count of octets in good frames sent from this ring to another ring.
.1.3.6.1.2.1.16.10.6.1.10,TOKEN-RING-RMON-MIB::sourceRoutingStatsThroughOctets,Counter32,read-only,,mandatory,,The count of octets in good frames sent another ring, through this ring, to another ring.
.1.3.6.1.2.1.16.10.6.1.11,TOKEN-RING-RMON-MIB::sourceRoutingStatsAllRoutesBroadcastOctets,Counter32,read-only,,mandatory,,The total number of octets in good frames received that were All Routes Broadcast.
.1.3.6.1.2.1.16.10.6.1.12,TOKEN-RING-RMON-MIB::sourceRoutingStatsSingleRoutesBroadcastOctets,Counter32,read-only,,mandatory,,The total number of octets in good frames received that were Single Route Broadcast.
.1.3.6.1.2.1.16.10.6.1.13,TOKEN-RING-RMON-MIB::sourceRoutingStatsLocalLLCFrames,Counter32,read-only,,mandatory,,The total number of frames received who had no RIF field (or had a RIF field that only included the local ring's number) and were not All Route Broadcast Frames.
.1.3.6.1.2.1.16.10.6.1.14,TOKEN-RING-RMON-MIB::sourceRoutingStats1HopFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 1 hop, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.15,TOKEN-RING-RMON-MIB::sourceRoutingStats2HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 2 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.16,TOKEN-RING-RMON-MIB::sourceRoutingStats3HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 3 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.17,TOKEN-RING-RMON-MIB::sourceRoutingStats4HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 4 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.18,TOKEN-RING-RMON-MIB::sourceRoutingStats5HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 5 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.19,TOKEN-RING-RMON-MIB::sourceRoutingStats6HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 6 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.20,TOKEN-RING-RMON-MIB::sourceRoutingStats7HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 7 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.21,TOKEN-RING-RMON-MIB::sourceRoutingStats8HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had 8 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.22,TOKEN-RING-RMON-MIB::sourceRoutingStatsMoreThan8HopsFrames,Counter32,read-only,,mandatory,,The total number of frames received whose route had more than 8 hops, were not All Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
.1.3.6.1.2.1.16.10.6.1.23,TOKEN-RING-RMON-MIB::sourceRoutingStatsOwner,OCTET,read-write,,mandatory,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.10.6.1.24,TOKEN-RING-RMON-MIB::sourceRoutingStatsStatus,INTEGER,read-write,,mandatory,valid(1):createRequest(2):underCreation(3):invalid(4),The status of this sourceRoutingStats entry.
.1.3.6.1.2.1.16.10.7,RMON2-MIB::ringStationControl2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.10.7.1,RMON2-MIB::ringStationControl2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.10.7.1.1,RMON2-MIB::ringStationControlDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.10.7.1.2,RMON2-MIB::ringStationControlCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.10.8,RMON2-MIB::sourceRoutingStats2Table,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.10.8.1,RMON2-MIB::sourceRoutingStats2Entry,,not-accessible,,deprecated,,Contains the RMON-2 augmentations to RMON-1.
.1.3.6.1.2.1.16.10.8.1.1,RMON2-MIB::sourceRoutingStatsDroppedFrames,Counter32,read-only,,deprecated,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.10.8.1.2,RMON2-MIB::sourceRoutingStatsCreateTime,TimeTicks,read-only,,deprecated,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.11,RMON2-MIB::protocolDir,,,,,,
.1.3.6.1.2.1.16.11.1,RMON2-MIB::protocolDirLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the protocol directory was last modified, either through insertions or deletions, or through modifications of the protocolDirAddressMapConfig, protocolDirHostConfig, or protocolDirMatrixConfig.
.1.3.6.1.2.1.16.11.2,RMON2-MIB::protocolDirTable,,not-accessible,,current,,This table lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network-layer, transport-layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don't support the application-layer groups.
.1.3.6.1.2.1.16.11.2.1,RMON2-MIB::protocolDirEntry,,not-accessible,protocolDirID:protocolDirParameters,current,,A conceptual row in the protocolDirTable. An example of the indexing of this entry is protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.2.0.0, which is the encoding of a length of 8, followed by 8 subids encoding the protocolDirID of 1.2048, followed by a length of 2 and the 2 subids encoding zero-valued parameters. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.11.2.1.1,RMON2-MIB::protocolDirID,OCTET,not-accessible,,current,,A unique identifier for a particular protocol. Standard identifiers will be defined in such a manner that they can often be used as specifications for new protocols - i.e., a tree-structured assignment mechanism that matches the protocol encapsulation 'tree' and that has algorithmic assignment mechanisms for certain subtrees. See RFC 2074 for more details. Despite the algorithmic mechanism, the probe will only place entries in here for those protocols it chooses to collect. In other words, it need not populate this table with all possible ethernet protocol types, nor need it create them on the fly when it sees them. Whether it does these things is a matter of product definition (cost/benefit, usability) and is up to the designer of the product. If an entry is written to this table with a protocolDirID that the agent doesn't understand, either directly or algorithmically, the SET request will be rejected with an inconsistentName or badValue (for SNMPv1) error.
.1.3.6.1.2.1.16.11.2.1.2,RMON2-MIB::protocolDirParameters,OCTET,not-accessible,,current,,A set of parameters for the associated protocolDirID. See the associated RMON2 Protocol Identifiers document for a description of the possible parameters. There will be one octet in this string for each sub-identifier in the protocolDirID, and the parameters will appear here in the same order as the associated sub-identifiers appear in the protocolDirID. Every node in the protocolDirID tree has a different, optional set of parameters defined (that is, the definition of parameters for a node is optional). The proper parameter value for each node is included in this string. Note that the inclusion of a parameter value in this string for each node is not optional. What is optional is that a node may have no parameters defined, in which case the parameter field for that node will be zero.
.1.3.6.1.2.1.16.11.2.1.3,RMON2-MIB::protocolDirLocalIndex,Integer32,read-only,,current,,The locally arbitrary but unique identifier associated with this protocolDir entry. The value for each supported protocol must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization, except that if a protocol is deleted and re-created, it must be re-created with a new value that has not been used since the last re-initialization. The specific value is meaningful only within a given SNMP entity. A protocolDirLocalIndex must not be re-used until the next agent restart in the event that the protocol directory entry is deleted.
.1.3.6.1.2.1.16.11.2.1.4,RMON2-MIB::protocolDirDescr,OCTET,read-create,,current,,A textual description of the protocol encapsulation. A probe may choose to describe only a subset of the entire encapsulation (e.g., only the highest layer). This object is intended for human consumption only. This object may not be modified if the associated protocolDirStatus object is equal to active(1).
.1.3.6.1.2.1.16.11.2.1.5,RMON2-MIB::protocolDirType,BITS,read-only,,current,extensible(0):addressRecognitionCapable(1),This object describes 2 attributes of this protocol directory entry. The presence or absence of the 'extensible' bit describes whether this protocol directory entry can be extended by the user by creating protocol directory entries that are children of this protocol. An example of an entry that will often allow extensibility is 'ip.udp'. The probe may automatically populate some children of this node, such as 'ip.udp.snmp' and 'ip.udp.dns'. A probe administrator or user may also populate additional children via remote SNMP requests that create entries in this table. When a child node is added for a protocol for which the probe has no built-in support extending a parent node (for which the probe does have built-in support), that child node is not extendable. This is termed 'limited extensibility'. When a child node is added through this extensibility mechanism, the values of protocolDirLocalIndex and protocolDirType shall be assigned by the agent. The other objects in the entry will be assigned by the manager who is creating the new entry. This object also describes whether this agent can recognize addresses for this protocol, should it be a network-level protocol. That is, while a probe may be able to recognize packets of a particular network-layer protocol and count them, it takes additional logic to be able to recognize the addresses in this protocol and to populate network-layer or application-layer tables with the addresses in this protocol. If this bit is set, the agent will recognize network-layer addresses for this protocol and populate the network- and application-layer host and matrix tables with these protocols. Note that when an entry is created, the agent will supply values for the bits that match the capabilities of the agent with respect to this protocol. Note that since row creations usually exercise the limited extensibility feature, these bits will usually be set to zero.
.1.3.6.1.2.1.16.11.2.1.6,RMON2-MIB::protocolDirAddressMapConfig,INTEGER,read-create,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for address mapping for this protocol. When the probe creates entries in this table for all protocols that it understands, it will set the entry to notSupported(1) if it doesn't have the capability to perform address mapping for the protocol or if this protocol is not a network-layer protocol. When an entry is created in this table by a management operation as part of the limited extensibility feature, the probe must set this value to notSupported(1), because limited extensibility of the protocolDirTable does not extend to interpreting addresses of the extended protocols. If the value of this object is notSupported(1), the probe will not perform address mapping for this protocol and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports address mapping for this protocol and is configured to perform address mapping for this protocol for all addressMappingControlEntries and all interfaces. If the value of this object is supportedOff(2), the probe supports address mapping for this protocol but is configured to not perform address mapping for this protocol for any addressMappingControlEntries and all interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall delete all related entries in the addressMappingTable.
.1.3.6.1.2.1.16.11.2.1.7,RMON2-MIB::protocolDirHostConfig,INTEGER,read-create,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for the network-layer and application-layer host tables for this protocol. When the probe creates entries in this table for all protocols that it understands, it will set the entry to notSupported(1) if it doesn't have the capability to track the nlHostTable for this protocol or if the alHostTable is implemented but doesn't have the capability to track this protocol. Note that if the alHostTable is implemented, the probe may only support a protocol if it is supported in both the nlHostTable and the alHostTable. If the associated protocolDirType object has the addressRecognitionCapable bit set, then this is a network- layer protocol for which the probe recognizes addresses, and thus the probe will populate the nlHostTable and alHostTable with addresses it discovers for this protocol. If the value of this object is notSupported(1), the probe will not track the nlHostTable or alHostTable for this protocol and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports tracking of the nlHostTable and alHostTable for this protocol and is configured to track both tables for this protocol for all control entries and all interfaces. If the value of this object is supportedOff(2), the probe supports tracking of the nlHostTable and alHostTable for this protocol but is configured to not track these tables for any control entries or interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall delete all related entries in the nlHostTable and alHostTable. Note that since each alHostEntry references 2 protocol directory entries, one for the network address and one for the type of the highest protocol recognized, an entry will only be created in that table if this value is supportedOn(3) for both protocols.
.1.3.6.1.2.1.16.11.2.1.8,RMON2-MIB::protocolDirMatrixConfig,INTEGER,read-create,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for the network-layer and application-layer matrix tables for this protocol. When the probe creates entries in this table for all protocols that it understands, it will set the entry to notSupported(1) if it doesn't have the capability to track the nlMatrixTables for this protocol or if the alMatrixTables are implemented but don't have the capability to track this protocol. Note that if the alMatrix tables are implemented, the probe may only support a protocol if it is supported in both of the nlMatrixTables and both of the alMatrixTables. If the associated protocolDirType object has the addressRecognitionCapable bit set, then this is a network- layer protocol for which the probe recognizes addresses, and thus the probe will populate both of the nlMatrixTables and both of the alMatrixTables with addresses it discovers for this protocol. If the value of this object is notSupported(1), the probe will not track either of the nlMatrixTables or the alMatrixTables for this protocol and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports tracking of both of the nlMatrixTables and (if implemented) both of the alMatrixTables for this protocol and is configured to track these tables for this protocol for all control entries and all interfaces. If the value of this object is supportedOff(2), the probe supports tracking of both of the nlMatrixTables and (if implemented) both of the alMatrixTables for this protocol but is configured to not track these tables for this protocol for any control entries or interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall delete all related entries in the nlMatrixTables and the alMatrixTables. Note that since each alMatrixEntry references 2 protocol directory entries, one for the network address and one for the type of the highest protocol recognized, an entry will only be created in that table if this value is supportedOn(3) for both protocols.
.1.3.6.1.2.1.16.11.2.1.9,RMON2-MIB::protocolDirOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.11.2.1.10,RMON2-MIB::protocolDirStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this protocol directory entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlHostTable, nlMatrixSDTable, nlMatrixDSTable, alHostTable, alMatrixSDTable, and alMatrixDSTable shall be deleted.
.1.3.6.1.2.1.16.12,RMON2-MIB::protocolDist,,,,,,
.1.3.6.1.2.1.16.12.1,RMON2-MIB::protocolDistControlTable,,not-accessible,,current,,Controls the setup of protocol type distribution statistics tables. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of protocol statistics is available. Rationale: This table controls collection of very basic statistics for any or all of the protocols detected on a given interface. An NMS can use this table to quickly determine bandwidth allocation utilized by different protocols. A media-specific statistics collection could also be configured (e.g., etherStats, trPStats) to easily obtain total frame, octet, and droppedEvents for the same interface.
.1.3.6.1.2.1.16.12.1.1,RMON2-MIB::protocolDistControlEntry,,not-accessible,protocolDistControlIndex,current,,A conceptual row in the protocolDistControlTable. An example of the indexing of this entry is protocolDistControlDroppedFrames.7
.1.3.6.1.2.1.16.12.1.1.1,RMON2-MIB::protocolDistControlIndex,Integer32,not-accessible,,current,,A unique index for this protocolDistControlEntry.
.1.3.6.1.2.1.16.12.1.1.2,RMON2-MIB::protocolDistControlDataSource,OBJECT,read-create,,current,,The source of data for the this protocol distribution. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated protocolDistControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.12.1.1.3,RMON2-MIB::protocolDistControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.12.1.1.4,RMON2-MIB::protocolDistControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.12.1.1.5,RMON2-MIB::protocolDistControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.12.1.1.6,RMON2-MIB::protocolDistControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the protocolDistStatsTable shall be deleted.
.1.3.6.1.2.1.16.12.2,RMON2-MIB::protocolDistStatsTable,,not-accessible,,current,,An entry is made in this table for every protocol in the protocolDirTable that has been seen in at least one packet. Counters are updated in this table for every protocol type that is encountered when parsing a packet, but no counters are updated for packets with MAC-layer errors. Note that if a protocolDirEntry is deleted, all associated entries in this table are removed.
.1.3.6.1.2.1.16.12.2.1,RMON2-MIB::protocolDistStatsEntry,,not-accessible,protocolDistControlIndex:protocolDirLocalIndex,current,,A conceptual row in the protocolDistStatsTable. The index is composed of the protocolDistControlIndex of the associated protocolDistControlEntry, followed by the protocolDirLocalIndex of the associated protocol that this entry represents. In other words, the index identifies the protocol distribution an entry is a part of and the particular protocol that it represents. An example of the indexing of this entry is protocolDistStatsPkts.1.18
.1.3.6.1.2.1.16.12.2.1.1,RMON2-MIB::protocolDistStatsPkts,Gauge32,read-only,,current,,The number of packets of this protocol type received without errors. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.12.2.1.2,RMON2-MIB::protocolDistStatsOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type received since it was added to the protocolDistStatsTable (excluding framing bits, but including FCS octets), except for those octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.12.3,HC-RMON-MIB::protocolDistStatsHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 protocolDistStatsTable.
.1.3.6.1.2.1.16.12.3.1,HC-RMON-MIB::protocolDistStatsHighCapacityEntry,,not-accessible,protocolDistControlIndex:protocolDirLocalIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 protocolDistStatsTable. These objects will be created by the agent for all protocolDistStatsEntries associated with whichever protocolDistControlEntries it deems appropriate. (i.e., either all protocolDistStatsHighCapacityEntries associated with a particular protocolDistControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.12.3.1.1,HC-RMON-MIB::protocolDistStatsHighCapacityOverflowPkts,Gauge32,read-only,,current,,The number of times the associated protocolDistStatsPkts counter has overflowed.
.1.3.6.1.2.1.16.12.3.1.2,HC-RMON-MIB::protocolDistStatsHighCapacityPkts,Counter64,read-only,,current,,The number of packets without errors received of this protocol type. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.12.3.1.3,HC-RMON-MIB::protocolDistStatsHighCapacityOverflowOctets,Gauge32,read-only,,current,,The number of times the associated protocolDistStatsOctets counter has overflowed.
.1.3.6.1.2.1.16.12.3.1.4,HC-RMON-MIB::protocolDistStatsHighCapacityOctets,Counter64,read-only,,current,,The number of octets in packets received of this protocol type since it was added to the protocolDistStatsTable (excluding framing bits but including FCS octets), except for those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.13,RMON2-MIB::addressMap,,,,,,
.1.3.6.1.2.1.16.13.1,RMON2-MIB::addressMapInserts,Counter32,read-only,,current,,The number of times an address mapping entry has been inserted into the addressMapTable. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. Note that the table size can be determined by subtracting addressMapDeletes from addressMapInserts.
.1.3.6.1.2.1.16.13.2,RMON2-MIB::addressMapDeletes,Counter32,read-only,,current,,The number of times an address mapping entry has been deleted from the addressMapTable (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. Note that the table size can be determined by subtracting addressMapDeletes from addressMapInserts.
.1.3.6.1.2.1.16.13.3,RMON2-MIB::addressMapMaxDesiredEntries,Integer32,read-write,,current,,The maximum number of entries that are desired in the addressMapTable. The probe will not create more than this number of entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.13.4,RMON2-MIB::addressMapControlTable,,not-accessible,,current,,A table to control the collection of mappings from network layer address to physical address to interface. Note that this is not like the typical RMON controlTable and dataTable in which each entry creates its own data table. Each entry in this table enables the discovery of addresses on a new interface and the placement of address mappings into the central addressMapTable. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of address mappings is available.
.1.3.6.1.2.1.16.13.4.1,RMON2-MIB::addressMapControlEntry,,not-accessible,addressMapControlIndex,current,,A conceptual row in the addressMapControlTable. An example of the indexing of this entry is addressMapControlDroppedFrames.1
.1.3.6.1.2.1.16.13.4.1.1,RMON2-MIB::addressMapControlIndex,Integer32,not-accessible,,current,,A unique index for this entry in the addressMapControlTable.
.1.3.6.1.2.1.16.13.4.1.2,RMON2-MIB::addressMapControlDataSource,OBJECT,read-create,,current,,The source of data for this addressMapControlEntry.
.1.3.6.1.2.1.16.13.4.1.3,RMON2-MIB::addressMapControlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.13.4.1.4,RMON2-MIB::addressMapControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.13.4.1.5,RMON2-MIB::addressMapControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this addressMap control entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the addressMapTable shall be deleted.
.1.3.6.1.2.1.16.13.5,RMON2-MIB::addressMapTable,,not-accessible,,current,,A table of mappings from network layer address to physical address to interface. The probe will add entries to this table based on the source MAC and network addresses seen in packets without MAC-level errors. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirAddressMapConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirAddressMapConfig value of supportedOff(2).
.1.3.6.1.2.1.16.13.5.1,RMON2-MIB::addressMapEntry,,not-accessible,addressMapTimeMark:protocolDirLocalIndex:addressMapNetworkAddress:addressMapSource,current,,A conceptual row in the addressMapTable. The protocolDirLocalIndex in the index identifies the network layer protocol of the addressMapNetworkAddress. An example of the indexing of this entry is addressMapSource.783495.18.4.128.2.6.6.11.1.3.6.1.2.1.2.2.1.1.1. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.13.5.1.1,RMON2-MIB::addressMapTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.13.5.1.2,RMON2-MIB::addressMapNetworkAddress,OCTET,not-accessible,,current,,The network address for this relation. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.13.5.1.3,RMON2-MIB::addressMapSource,OBJECT,not-accessible,,current,,The interface or port on which the associated network address was most recently seen. If this address mapping was discovered on an interface, this object shall identify the instance of the ifIndex object, defined in [RFC2863], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. If this address mapping was discovered on a port, this object shall identify the instance of the rptrGroupPortIndex object, defined in [RFC2108], for the desired port. For example, if an entry were to receive data from group #1, port #1, this object would be set to rptrGroupPortIndex.1.1. Note that while the dataSource associated with this entry may only point to index objects, this object may at times point to repeater port objects. This situation occurs when the dataSource points to an interface that is a locally attached repeater and the agent has additional information about the source port of traffic seen on that repeater.
.1.3.6.1.2.1.16.13.5.1.4,RMON2-MIB::addressMapPhysicalAddress,OCTET,read-only,,current,,The last source physical address on which the associated network address was seen. If the protocol of the associated network address was encapsulated inside of a network-level or higher protocol, this will be the address of the next-lower protocol with the addressRecognitionCapable bit enabled and will be formatted as specified for that protocol.
.1.3.6.1.2.1.16.13.5.1.5,RMON2-MIB::addressMapLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this entry was last created or the values of the physical address changed. This can be used to help detect duplicate address problems, in which case this object will be updated frequently.
.1.3.6.1.2.1.16.14,RMON2-MIB::nlHost,,,,,,
.1.3.6.1.2.1.16.14.1,RMON2-MIB::hlHostControlTable,,not-accessible,,current,,A list of higher-layer (i.e., non-MAC) host table control entries. These entries will enable the collection of the network- and application-level host tables indexed by network addresses. Both the network- and application-level host tables are controlled by this table so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore. (Note that if an implementation stores application-layer host records in memory, it can derive network-layer host records from them.) Entries in the nlHostTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alHostTable, entries in the alHostTable will be created on behalf of each entry in this table. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of host statistics is available.
.1.3.6.1.2.1.16.14.1.1,RMON2-MIB::hlHostControlEntry,,not-accessible,hlHostControlIndex,current,,A conceptual row in the hlHostControlTable. An example of the indexing of this entry is hlHostControlNlDroppedFrames.1
.1.3.6.1.2.1.16.14.1.1.1,RMON2-MIB::hlHostControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the hlHostControlTable. Each such entry defines a function that discovers hosts on a particular interface and places statistics about them in the nlHostTable, and optionally in the alHostTable, on behalf of this hlHostControlEntry.
.1.3.6.1.2.1.16.14.1.1.2,RMON2-MIB::hlHostControlDataSource,OBJECT,read-create,,current,,The source of data for the associated host tables. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated hlHostControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.14.1.1.3,RMON2-MIB::hlHostControlNlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for the associated nlHost entries for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the nlHostTable is inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.14.1.1.4,RMON2-MIB::hlHostControlNlInserts,Counter32,read-only,,current,,The number of times an nlHost entry has been inserted into the nlHost table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlNlDeletes from hlHostControlNlInserts.
.1.3.6.1.2.1.16.14.1.1.5,RMON2-MIB::hlHostControlNlDeletes,Counter32,read-only,,current,,The number of times an nlHost entry has been deleted from the nlHost table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlNlDeletes from hlHostControlNlInserts.
.1.3.6.1.2.1.16.14.1.1.6,RMON2-MIB::hlHostControlNlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the nlHostTable on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlHostControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.14.1.1.7,RMON2-MIB::hlHostControlAlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for the associated alHost entries for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the alHostTable is not implemented or is inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.14.1.1.8,RMON2-MIB::hlHostControlAlInserts,Counter32,read-only,,current,,The number of times an alHost entry has been inserted into the alHost table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlAlDeletes from hlHostControlAlInserts.
.1.3.6.1.2.1.16.14.1.1.9,RMON2-MIB::hlHostControlAlDeletes,Counter32,read-only,,current,,The number of times an alHost entry has been deleted from the alHost table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlHostControlAlDeletes from hlHostControlAlInserts.
.1.3.6.1.2.1.16.14.1.1.10,RMON2-MIB::hlHostControlAlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the alHost table on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlHostControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.14.1.1.11,RMON2-MIB::hlHostControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.14.1.1.12,RMON2-MIB::hlHostControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this hlHostControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlHostTable and alHostTable shall be deleted.
.1.3.6.1.2.1.16.14.2,RMON2-MIB::nlHostTable,,not-accessible,,current,,A collection of statistics for a particular network layer address that has been discovered on an interface of this device. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors.
.1.3.6.1.2.1.16.14.2.1,RMON2-MIB::nlHostEntry,,not-accessible,hlHostControlIndex:nlHostTimeMark:protocolDirLocalIndex:nlHostAddress,current,,A conceptual row in the nlHostTable. The hlHostControlIndex value in the index identifies the hlHostControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network layer protocol of the nlHostAddress. An example of the indexing of this entry is nlHostOutPkts.1.783495.18.4.128.2.6.6. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.14.2.1.1,RMON2-MIB::nlHostTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.14.2.1.2,RMON2-MIB::nlHostAddress,OCTET,not-accessible,,current,,The network address for this nlHostEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.14.2.1.3,RMON2-MIB::nlHostInPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted to this address since it was added to the nlHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.2.1.4,RMON2-MIB::nlHostOutPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted by this address since it was added to the nlHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.2.1.5,RMON2-MIB::nlHostInOctets,Gauge32,read-only,,current,,The number of octets transmitted to this address since it was added to the nlHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.14.2.1.6,RMON2-MIB::nlHostOutOctets,Gauge32,read-only,,current,,The number of octets transmitted by this address since it was added to the nlHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.14.2.1.7,RMON2-MIB::nlHostOutMacNonUnicastPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted by this address that were directed to any MAC broadcast addresses or to any MAC multicast addresses since this host was added to the nlHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.2.1.8,RMON2-MIB::nlHostCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.14.3,HC-RMON-MIB::nlHostHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 nlHostTable.
.1.3.6.1.2.1.16.14.3.1,HC-RMON-MIB::nlHostHighCapacityEntry,,not-accessible,hlHostControlIndex:nlHostTimeMark:protocolDirLocalIndex:nlHostAddress,current,,Contains the High Capacity RMON extensions to the RMON-2 nlHostEntry. These objects will be created by the agent for all nlHostEntries associated with whichever hlHostControlEntries it deems appropriate. (i.e., either all nlHostHighCapacityEntries associated with a particular hlHostControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.14.3.1.1,HC-RMON-MIB::nlHostHighCapacityInOverflowPkts,Gauge32,read-only,,current,,The number of times the associated nlHostInPkts counter has overflowed.
.1.3.6.1.2.1.16.14.3.1.2,HC-RMON-MIB::nlHostHighCapacityInPkts,Counter64,read-only,,current,,The number of packets without errors transmitted to this address since it was added to the nlHostHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.3.1.3,HC-RMON-MIB::nlHostHighCapacityOutOverflowPkts,Gauge32,read-only,,current,,The number of times the associated nlHostOutPkts counter has overflowed.
.1.3.6.1.2.1.16.14.3.1.4,HC-RMON-MIB::nlHostHighCapacityOutPkts,Counter64,read-only,,current,,The number of packets without errors transmitted by this address since it was added to the nlHostHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.14.3.1.5,HC-RMON-MIB::nlHostHighCapacityInOverflowOctets,Gauge32,read-only,,current,,The number of times the associated nlHostInOctets counter has overflowed.
.1.3.6.1.2.1.16.14.3.1.6,HC-RMON-MIB::nlHostHighCapacityInOctets,Counter64,read-only,,current,,The number of octets transmitted to this address since it was added to the nlHostHighCapacityTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.14.3.1.7,HC-RMON-MIB::nlHostHighCapacityOutOverflowOctets,Gauge32,read-only,,current,,The number of times the associated nlHostOutOctets counter has overflowed.
.1.3.6.1.2.1.16.14.3.1.8,HC-RMON-MIB::nlHostHighCapacityOutOctets,Counter64,read-only,,current,,The number of octets transmitted by this address since it was added to the nlHostHighCapacityTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15,RMON2-MIB::nlMatrix,,,,,,
.1.3.6.1.2.1.16.15.1,RMON2-MIB::hlMatrixControlTable,,not-accessible,,current,,A list of higher-layer (i.e., non-MAC) matrix control entries. These entries will enable the collection of the network- and application-level matrix tables containing conversation statistics indexed by pairs of network addresses. Both the network- and application-level matrix tables are controlled by this table so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore. (Note that if an implementation stores application-layer matrix records in memory, it can derive network-layer matrix records from them.) Entries in the nlMatrixSDTable and nlMatrixDSTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alMatrix tables, entries in the alMatrix tables will be created on behalf of each entry in this table.
.1.3.6.1.2.1.16.15.1.1,RMON2-MIB::hlMatrixControlEntry,,not-accessible,hlMatrixControlIndex,current,,A conceptual row in the hlMatrixControlTable. An example of indexing of this entry is hlMatrixControlNlDroppedFrames.1
.1.3.6.1.2.1.16.15.1.1.1,RMON2-MIB::hlMatrixControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the hlMatrixControlTable. Each such entry defines a function that discovers conversations on a particular interface and places statistics about them in the nlMatrixSDTable and the nlMatrixDSTable, and optionally the alMatrixSDTable and alMatrixDSTable, on behalf of this hlMatrixControlEntry.
.1.3.6.1.2.1.16.15.1.1.2,RMON2-MIB::hlMatrixControlDataSource,OBJECT,read-create,,current,,The source of the data for the associated matrix tables. The statistics in this group reflect all packets on the local network segment attached to the identified interface. This object may not be modified if the associated hlMatrixControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.15.1.1.3,RMON2-MIB::hlMatrixControlNlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the nlMatrixTables are inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.15.1.1.4,RMON2-MIB::hlMatrixControlNlInserts,Counter32,read-only,,current,,The number of times an nlMatrix entry has been inserted into the nlMatrix tables. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the nlMatrixSDTable and nlMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the sum of then nlMatrixSDTable and nlMatrixDSTable sizes can be determined by subtracting hlMatrixControlNlDeletes from hlMatrixControlNlInserts.
.1.3.6.1.2.1.16.15.1.1.5,RMON2-MIB::hlMatrixControlNlDeletes,Counter32,read-only,,current,,The number of times an nlMatrix entry has been deleted from the nlMatrix tables (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the nlMatrixSDTable and nlMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlMatrixControlNlDeletes from hlMatrixControlNlInserts.
.1.3.6.1.2.1.16.15.1.1.6,RMON2-MIB::hlMatrixControlNlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the nlMatrix tables on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlMatrixControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.15.1.1.7,RMON2-MIB::hlMatrixControlAlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the probe and therefore not accounted for in the *StatsDropEvents, but that the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the alMatrixTables are not implemented or are inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.15.1.1.8,RMON2-MIB::hlMatrixControlAlInserts,Counter32,read-only,,current,,The number of times an alMatrix entry has been inserted into the alMatrix tables. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the alMatrixSDTable and alMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlMatrixControlAlDeletes from hlMatrixControlAlInserts.
.1.3.6.1.2.1.16.15.1.1.9,RMON2-MIB::hlMatrixControlAlDeletes,Counter32,read-only,,current,,The number of times an alMatrix entry has been deleted from the alMatrix tables. If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the alMatrixSDTable and alMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting hlMatrixControlAlDeletes from hlMatrixControlAlInserts.
.1.3.6.1.2.1.16.15.1.1.10,RMON2-MIB::hlMatrixControlAlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the alMatrix tables on behalf of this control entry. The probe will not create more than this number of associated entries in the table but may choose to create fewer entries in this table for any reason, including the lack of resources. If this object is set to a value less than the current number of entries, enough entries are chosen in an implementation-dependent manner and deleted so that the number of entries in the table equals the value of this object. If this value is set to -1, the probe may create any number of entries in this table. If the associated hlMatrixControlStatus object is equal to 'active', this object may not be modified. This object may be used to control how resources are allocated on the probe for the various RMON functions.
.1.3.6.1.2.1.16.15.1.1.11,RMON2-MIB::hlMatrixControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.15.1.1.12,RMON2-MIB::hlMatrixControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this hlMatrixControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlMatrixSDTable, nlMatrixDSTable, alMatrixSDTable, and alMatrixDSTable shall be deleted by the agent.
.1.3.6.1.2.1.16.15.2,RMON2-MIB::nlMatrixSDTable,,not-accessible,,current,,A list of traffic matrix entries that collect statistics for conversations between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all conversations from a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixDSTable with the same source address and destination address.
.1.3.6.1.2.1.16.15.2.1,RMON2-MIB::nlMatrixSDEntry,,not-accessible,hlMatrixControlIndex:nlMatrixSDTimeMark:protocolDirLocalIndex:nlMatrixSDSourceAddress:nlMatrixSDDestAddress,current,,A conceptual row in the nlMatrixSDTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network-layer protocol of the nlMatrixSDSourceAddress and nlMatrixSDDestAddress. An example of the indexing of this table is nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.15.2.1.1,RMON2-MIB::nlMatrixSDTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.15.2.1.2,RMON2-MIB::nlMatrixSDSourceAddress,OCTET,not-accessible,,current,,The network source address for this nlMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.2.1.3,RMON2-MIB::nlMatrixSDDestAddress,OCTET,not-accessible,,current,,The network destination address for this nlMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.2.1.4,RMON2-MIB::nlMatrixSDPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted from the source address to the destination address since this entry was added to the nlMatrixSDTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.15.2.1.5,RMON2-MIB::nlMatrixSDOctets,Gauge32,read-only,,current,,The number of octets transmitted from the source address to the destination address since this entry was added to the nlMatrixSDTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15.2.1.6,RMON2-MIB::nlMatrixSDCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.15.3,RMON2-MIB::nlMatrixDSTable,,not-accessible,,current,,A list of traffic matrix entries that collect statistics for conversations between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all conversations to a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixSDTable with the same source address and destination address.
.1.3.6.1.2.1.16.15.3.1,RMON2-MIB::nlMatrixDSEntry,,not-accessible,hlMatrixControlIndex:nlMatrixDSTimeMark:protocolDirLocalIndex:nlMatrixDSDestAddress:nlMatrixDSSourceAddress,current,,A conceptual row in the nlMatrixDSTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the network-layer protocol of the nlMatrixDSSourceAddress and nlMatrixDSDestAddress. An example of the indexing of this table is nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.15.3.1.1,RMON2-MIB::nlMatrixDSTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.15.3.1.2,RMON2-MIB::nlMatrixDSSourceAddress,OCTET,not-accessible,,current,,The network source address for this nlMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.3.1.3,RMON2-MIB::nlMatrixDSDestAddress,OCTET,not-accessible,,current,,The network destination address for this nlMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.3.1.4,RMON2-MIB::nlMatrixDSPkts,Gauge32,read-only,,current,,The number of packets without errors transmitted from the source address to the destination address since this entry was added to the nlMatrixDSTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.15.3.1.5,RMON2-MIB::nlMatrixDSOctets,Gauge32,read-only,,current,,The number of octets transmitted from the source address to the destination address since this entry was added to the nlMatrixDSTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15.3.1.6,RMON2-MIB::nlMatrixDSCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.15.4,RMON2-MIB::nlMatrixTopNControlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N matrix entries according to a selected metric.
.1.3.6.1.2.1.16.15.4.1,RMON2-MIB::nlMatrixTopNControlEntry,,not-accessible,nlMatrixTopNControlIndex,current,,A conceptual row in the nlMatrixTopNControlTable. An example of the indexing of this table is nlMatrixTopNControlDuration.3
.1.3.6.1.2.1.16.15.4.1.1,RMON2-MIB::nlMatrixTopNControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the nlMatrixTopNControlTable. Each such entry defines one topN report prepared for one interface.
.1.3.6.1.2.1.16.15.4.1.2,RMON2-MIB::nlMatrixTopNControlMatrixIndex,Integer32,read-create,,current,,The nlMatrix[SD/DS] table for which a topN report will be prepared on behalf of this entry. The nlMatrix[SD/DS] table is identified by the value of the hlMatrixControlIndex for that table - that value is used here to identify the particular table. This object may not be modified if the associated nlMatrixTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.15.4.1.3,RMON2-MIB::nlMatrixTopNControlRateBase,INTEGER,read-create,,current,nlMatrixTopNPkts(1):nlMatrixTopNOctets(2):nlMatrixTopNHighCapacityPkts(3):nlMatrixTopNHighCapacityOctets(4),The variable for each nlMatrix[SD/DS] entry that the nlMatrixTopNEntries are sorted by, as well as a control for the table that the results will be reported in. This object may not be modified if the associated nlMatrixTopNControlStatus object is equal to active(1). If this value is less than or equal to 2, when the report is prepared, entries are created in the nlMatrixTopNTable associated with this object. If this value is greater than or equal to 3, when the report is prepared, entries are created in the nlMatrixTopNHighCapacityTable associated with this object.
.1.3.6.1.2.1.16.15.4.1.4,RMON2-MIB::nlMatrixTopNControlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report and is immediately loaded into the associated nlMatrixTopNControlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of nlMatrixTopNControlTimeRemaining. Thus, the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the nlMatrixTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the nlMatrixTopNTable shall be deleted. (Note that this is a different algorithm than the one used in the hostTopNTable).
.1.3.6.1.2.1.16.15.4.1.5,RMON2-MIB::nlMatrixTopNControlGeneratedReports,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.15.4.1.6,RMON2-MIB::nlMatrixTopNControlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated nlMatrixTopNControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the nlMatrixTopNControlTimeRemaining is set. This value shall be zero if no reports have been requested for this nlMatrixTopNControlEntry.
.1.3.6.1.2.1.16.15.4.1.7,RMON2-MIB::nlMatrixTopNControlRequestedSize,Integer32,read-create,,current,,The maximum number of matrix entries requested for this report. When this object is created or modified, the probe should set nlMatrixTopNControlGrantedSize as closely to this object as possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.15.4.1.8,RMON2-MIB::nlMatrixTopNControlGrantedSize,Integer32,read-only,,current,,The maximum number of matrix entries in this report. When the associated nlMatrixTopNControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as possible for the particular implementation and available resources. The probe must not lower this value except as a side-effect of a set to the associated nlMatrixTopNControlRequestedSize object. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNPkts, when the next topN report is generated, matrix entries with the highest value of nlMatrixTopNPktRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNOctets, when the next topN report is generated, matrix entries with the highest value of nlMatrixTopNOctetRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. It is an implementation-specific matter how entries with the same value of nlMatrixTopNPktRate or nlMatrixTopNOctetRate are sorted. It is also an implementation-specific matter as to whether zero-valued entries are available.
.1.3.6.1.2.1.16.15.4.1.9,RMON2-MIB::nlMatrixTopNControlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this topN report was last started. In other words, this is the time that the associated nlMatrixTopNControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine whether a report was missed.
.1.3.6.1.2.1.16.15.4.1.10,RMON2-MIB::nlMatrixTopNControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.15.4.1.11,RMON2-MIB::nlMatrixTopNControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this nlMatrixTopNControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the nlMatrixTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.15.5,RMON2-MIB::nlMatrixTopNTable,,not-accessible,,current,,A set of statistics for those network-layer matrix entries that have counted the highest number of octets or packets.
.1.3.6.1.2.1.16.15.5.1,RMON2-MIB::nlMatrixTopNEntry,,not-accessible,nlMatrixTopNControlIndex:nlMatrixTopNIndex,current,,A conceptual row in the nlMatrixTopNTable. The nlMatrixTopNControlIndex value in the index identifies the nlMatrixTopNControlEntry on whose behalf this entry was created. An example of the indexing of this table is nlMatrixTopNPktRate.3.10
.1.3.6.1.2.1.16.15.5.1.1,RMON2-MIB::nlMatrixTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the nlMatrixTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNPkts, increasing values of nlMatrixTopNIndex shall be assigned to entries with decreasing values of nlMatrixTopNPktRate until index N is assigned or there are no more nlMatrixTopNEntries. If the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNOctets, increasing values of nlMatrixTopNIndex shall be assigned to entries with decreasing values of nlMatrixTopNOctetRate until index N is assigned or there are no more nlMatrixTopNEntries.
.1.3.6.1.2.1.16.15.5.1.2,RMON2-MIB::nlMatrixTopNProtocolDirLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex of the network-layer protocol of this entry's network address.
.1.3.6.1.2.1.16.15.5.1.3,RMON2-MIB::nlMatrixTopNSourceAddress,OCTET,read-only,,current,,The network-layer address of the source host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated nlMatrixTopNProtocolDirLocalIndex. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.5.1.4,RMON2-MIB::nlMatrixTopNDestAddress,OCTET,read-only,,current,,The network-layer address of the destination host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated nlMatrixTopNProtocolDirLocalIndex. For example, if the nlMatrixTopNProtocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.15.5.1.5,RMON2-MIB::nlMatrixTopNPktRate,Gauge32,read-only,,current,,The number of packets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the nlMatrixSDPkts object. If the value of nlMatrixTopNControlRateBase is nlMatrixTopNPkts, this variable will be used to sort this report.
.1.3.6.1.2.1.16.15.5.1.6,RMON2-MIB::nlMatrixTopNReversePktRate,Gauge32,read-only,,current,,The number of packets seen from the destination host to the source host during this sampling interval, counted using the rules for counting the nlMatrixSDPkts object. (Note that the corresponding nlMatrixSDPkts object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNPkts, the sort of topN entries is based entirely on nlMatrixTopNPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.5.1.7,RMON2-MIB::nlMatrixTopNOctetRate,Gauge32,read-only,,current,,The number of octets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the nlMatrixSDOctets object. If the value of nlMatrixTopNControlRateBase is nlMatrixTopNOctets, this variable will be used to sort this report.
.1.3.6.1.2.1.16.15.5.1.8,RMON2-MIB::nlMatrixTopNReverseOctetRate,Gauge32,read-only,,current,,The number of octets seen from the destination host to the source host during this sampling interval, counted using the rules for counting the nlMatrixDSOctets object. (Note that the corresponding nlMatrixSDOctets object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNOctets, the sort of topN entries is based entirely on nlMatrixTopNOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.6,HC-RMON-MIB::nlMatrixSDHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 nlMatrixTable.
.1.3.6.1.2.1.16.15.6.1,HC-RMON-MIB::nlMatrixSDHighCapacityEntry,,not-accessible,hlMatrixControlIndex:nlMatrixSDTimeMark:protocolDirLocalIndex:nlMatrixSDSourceAddress:nlMatrixSDDestAddress,current,,Contains the High Capacity RMON extensions to the RMON-2 nlMatrixEntry. These objects will be created by the agent for all nlMatrixSDEntries associated with whichever hlMatrixControlEntries it deems appropriate. (i.e., either all nlMatrixSDHighCapacityEntries associated with a particular hlMatrixControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.15.6.1.1,HC-RMON-MIB::nlMatrixSDHighCapacityOverflowPkts,Gauge32,read-only,,current,,The number of times the associated nlMatrixSDPkts counter has overflowed.
.1.3.6.1.2.1.16.15.6.1.2,HC-RMON-MIB::nlMatrixSDHighCapacityPkts,Counter64,read-only,,current,,The number of packets without errors transmitted from the source address to the destination address since this entry was added to the nlMatrixSDHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.15.6.1.3,HC-RMON-MIB::nlMatrixSDHighCapacityOverflowOctets,Gauge32,read-only,,current,,The number of times the associated nlMatrixSDOctets counter has overflowed.
.1.3.6.1.2.1.16.15.6.1.4,HC-RMON-MIB::nlMatrixSDHighCapacityOctets,Counter64,read-only,,current,,The number of octets transmitted from the source address to the destination address since this entry was added to the nlMatrixSDHighCapacityTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15.7,HC-RMON-MIB::nlMatrixDSHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 nlMatrixDSTable.
.1.3.6.1.2.1.16.15.7.1,HC-RMON-MIB::nlMatrixDSHighCapacityEntry,,not-accessible,hlMatrixControlIndex:nlMatrixDSTimeMark:protocolDirLocalIndex:nlMatrixDSDestAddress:nlMatrixDSSourceAddress,current,,Contains the High Capacity RMON extensions to the RMON-2 nlMatrixDSEntry. These objects will be created by the agent for all nlMatrixDSEntries associated with whichever hlmatrixControlEntries it deems appropriate. (i.e., either all nlMatrixDSHighCapacityEntries associated with a particular hlMatrixControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.15.7.1.1,HC-RMON-MIB::nlMatrixDSHighCapacityOverflowPkts,Gauge32,read-only,,current,,The number of times the associated nlMatrixDSPkts counter has overflowed.
.1.3.6.1.2.1.16.15.7.1.2,HC-RMON-MIB::nlMatrixDSHighCapacityPkts,Counter64,read-only,,current,,The number of packets without errors transmitted from the source address to the destination address since this entry was added to the nlMatrixDSHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.15.7.1.3,HC-RMON-MIB::nlMatrixDSHighCapacityOverflowOctets,Gauge32,read-only,,current,,The number of times the associated nlMatrixDSOctets counter has overflowed.
.1.3.6.1.2.1.16.15.7.1.4,HC-RMON-MIB::nlMatrixDSHighCapacityOctets,Counter64,read-only,,current,,The number of octets transmitted from the source address to the destination address since this entry was added to the nlMatrixDSHighCapacityTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.15.8,HC-RMON-MIB::nlMatrixTopNHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 nlMatrixTopNTable when nlMatrixTopNControlRateBase specifies a High Capacity TopN Report.
.1.3.6.1.2.1.16.15.8.1,HC-RMON-MIB::nlMatrixTopNHighCapacityEntry,,not-accessible,nlMatrixTopNControlIndex:nlMatrixTopNIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 nlMatrixTopNEntry when nlMatrixTopNControlRateBase specifies a High Capacity TopN Report. These objects will be created by the agent for all nlMatrixTopNEntries associated with whichever nlMatrixTopNControlEntries have a nlMatrixTopNControlRateBase that specify a high capacity report.
.1.3.6.1.2.1.16.15.8.1.1,HC-RMON-MIB::nlMatrixTopNHighCapacityProtocolDirLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex of the network layer protocol of this entry's network address.
.1.3.6.1.2.1.16.15.8.1.2,HC-RMON-MIB::nlMatrixTopNHighCapacitySourceAddress,OCTET,read-only,,current,,The network layer address of the source host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated nlMatrixTopNProtocolDirLocalIndex. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.
.1.3.6.1.2.1.16.15.8.1.3,HC-RMON-MIB::nlMatrixTopNHighCapacityDestAddress,OCTET,read-only,,current,,The network layer address of the destination host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated nlMatrixTopNProtocolDirLocalIndex. For example, if the nlMatrixTopNProtocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.
.1.3.6.1.2.1.16.15.8.1.4,HC-RMON-MIB::nlMatrixTopNHighCapacityBasePktRate,Gauge32,read-only,,current,,The number of packets seen from the source host to the destination host during this sampling interval, modulo 2^32, counted using the rules for counting the nlMatrixSDPkts object.
.1.3.6.1.2.1.16.15.8.1.5,HC-RMON-MIB::nlMatrixTopNHighCapacityOverflowPktRate,Gauge32,read-only,,current,,The number of packets seen from the source host to the destination host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the nlMatrixSDPkts object.
.1.3.6.1.2.1.16.15.8.1.6,HC-RMON-MIB::nlMatrixTopNHighCapacityPktRate,Counter64,read-only,,current,,The number of packets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the nlMatrixSDPkts object. If the value of nlMatrixTopNControlRateBase is nlMatrixTopNHighCapacityPkts, this variable will be used to sort this report.
.1.3.6.1.2.1.16.15.8.1.7,HC-RMON-MIB::nlMatrixTopNHighCapacityReverseBasePktRate,Gauge32,read-only,,current,,The number of packets seen from the destination host to the source host during this sampling interval, modulo 2^32, counted using the rules for counting the nlMatrixSDPkts object (note that the corresponding nlMatrixSDPkts object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNHighCapacityPkts, the sort of topN entries is based entirely on nlMatrixTopNHighCapacityPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.8.1.8,HC-RMON-MIB::nlMatrixTopNHighCapacityReverseOverflowPktRate,Gauge32,read-only,,current,,The number of packets seen from the destination host to the source host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the nlMatrixSDPkts object (note that the corresponding nlMatrixSDPkts object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNHighCapacityPkts, the sort of topN entries is based entirely on nlMatrixTopNHighCapacityPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.8.1.9,HC-RMON-MIB::nlMatrixTopNHighCapacityReversePktRate,Counter64,read-only,,current,,The number of packets seen from the destination host to the source host during this sampling interval, counted using the rules for counting the nlMatrixSDPkts object (note that the corresponding nlMatrixSDPkts object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNHighCapacityPkts, the sort of topN entries is based entirely on nlMatrixTopNHighCapacityPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.8.1.10,HC-RMON-MIB::nlMatrixTopNHighCapacityBaseOctetRate,Gauge32,read-only,,current,,The number of octets seen from the source host to the destination host during this sampling interval, modulo 2^32, counted using the rules for counting the nlMatrixSDOctets object.
.1.3.6.1.2.1.16.15.8.1.11,HC-RMON-MIB::nlMatrixTopNHighCapacityOverflowOctetRate,Gauge32,read-only,,current,,The number of octets seen from the source host to the destination host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the nlMatrixSDOctets object.
.1.3.6.1.2.1.16.15.8.1.12,HC-RMON-MIB::nlMatrixTopNHighCapacityOctetRate,Counter64,read-only,,current,,The number of octets seen from the source host to the destination host during this sampling interval, counted using the rules for counting the nlMatrixSDOctets object. If the value of nlMatrixTopNControlRateBase is nlMatrixTopNHighCapacityOctets, this variable will be used to sort this report.
.1.3.6.1.2.1.16.15.8.1.13,HC-RMON-MIB::nlMatrixTopNHighCapacityReverseBaseOctetRate,Gauge32,read-only,,current,,The number of octets seen from the destination host to the source host during this sampling interval, modulo 2^32, counted using the rules for counting the nlMatrixSDOctets object (note that the corresponding nlMatrixSDOctets object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNHighCapacityOctets, the sort of topN entries is based entirely on nlMatrixTopNHighCapacityOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.8.1.14,HC-RMON-MIB::nlMatrixTopNHighCapacityReverseOverflowOctetRate,Gauge32,read-only,,current,,The number of octets seen from the destination host to the source host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the nlMatrixSDOctets object (note that the corresponding nlMatrixSDOctets object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNHighCapacityOctets, the sort of topN entries is based entirely on nlMatrixTopNHighCapacityOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.15.8.1.15,HC-RMON-MIB::nlMatrixTopNHighCapacityReverseOctetRate,Counter64,read-only,,current,,The number of octets seen from the destination host to the source host during this sampling interval, counted using the rules for counting the nlMatrixSDOctets object (note that the corresponding nlMatrixSDOctets object selected is the one whose source address is equal to nlMatrixTopNDestAddress and whose destination address is equal to nlMatrixTopNSourceAddress.) Note that if the value of nlMatrixTopNControlRateBase is equal to nlMatrixTopNHighCapacityOctets, the sort of topN entries is based entirely on nlMatrixTopNHighCapacityOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.16,RMON2-MIB::alHost,,,,,,
.1.3.6.1.2.1.16.16.1,RMON2-MIB::alHostTable,,not-accessible,,current,,A collection of statistics for a particular protocol from a particular network address that has been discovered on an interface of this device. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address exists in the nlHostTable and will be deleted from this table if their address is deleted from the nlHostTable.
.1.3.6.1.2.1.16.16.1.1,RMON2-MIB::alHostEntry,,not-accessible,hlHostControlIndex:alHostTimeMark:protocolDirLocalIndex:nlHostAddress:protocolDirLocalIndex,current,,A conceptual row in the alHostTable. The hlHostControlIndex value in the index identifies the hlHostControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network-layer protocol of the address. The nlHostAddress value in the index identifies the network- layer address of this entry. The second protocolDirLocalIndex value in the index identifies the protocol that is counted by this entry. An example of the indexing in this entry is alHostOutPkts.1.783495.18.4.128.2.6.6.34. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.16.1.1.1,RMON2-MIB::alHostTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.16.1.1.2,RMON2-MIB::alHostInPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted to this address since it was added to the alHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.16.1.1.3,RMON2-MIB::alHostOutPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted by this address since it was added to the alHostTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.16.1.1.4,RMON2-MIB::alHostInOctets,Gauge32,read-only,,current,,The number of octets transmitted to this address of this protocol type since it was added to the alHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.16.1.1.5,RMON2-MIB::alHostOutOctets,Gauge32,read-only,,current,,The number of octets transmitted by this address of this protocol type since it was added to the alHostTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.16.1.1.6,RMON2-MIB::alHostCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.16.2,HC-RMON-MIB::alHostHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 alHostTable.
.1.3.6.1.2.1.16.16.2.1,HC-RMON-MIB::alHostHighCapacityEntry,,not-accessible,hlHostControlIndex:alHostTimeMark:protocolDirLocalIndex:nlHostAddress:protocolDirLocalIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 alHostEntry. These objects will be created by the agent for all alHostEntries associated with whichever hlHostControlEntries it deems appropriate. (i.e., either all alHostHighCapacityEntries associated with a particular hlHostControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.16.2.1.1,HC-RMON-MIB::alHostHighCapacityInOverflowPkts,Gauge32,read-only,,current,,The number of times the associated alHostInPkts counter has overflowed.
.1.3.6.1.2.1.16.16.2.1.2,HC-RMON-MIB::alHostHighCapacityInPkts,Counter64,read-only,,current,,The number of packets of this protocol type without errors transmitted to this address since it was added to the alHostHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.16.2.1.3,HC-RMON-MIB::alHostHighCapacityOutOverflowPkts,Gauge32,read-only,,current,,The number of times the associated alHostOutPkts counter has overflowed.
.1.3.6.1.2.1.16.16.2.1.4,HC-RMON-MIB::alHostHighCapacityOutPkts,Counter64,read-only,,current,,The number of packets of this protocol type without errors transmitted by this address since it was added to the alHostHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.16.2.1.5,HC-RMON-MIB::alHostHighCapacityInOverflowOctets,Gauge32,read-only,,current,,The number of times the associated alHostInOctets counter has overflowed.
.1.3.6.1.2.1.16.16.2.1.6,HC-RMON-MIB::alHostHighCapacityInOctets,Counter64,read-only,,current,,The number of octets transmitted to this address of this protocol type since it was added to the alHostHighCapacityTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.16.2.1.7,HC-RMON-MIB::alHostHighCapacityOutOverflowOctets,Gauge32,read-only,,current,,The number of times the associated alHostOutOctets counter has overflowed.
.1.3.6.1.2.1.16.16.2.1.8,HC-RMON-MIB::alHostHighCapacityOutOctets,Counter64,read-only,,current,,The number of octets transmitted by this address of this protocol type since it was added to the alHostHighCapacityTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17,RMON2-MIB::alMatrix,,,,,,
.1.3.6.1.2.1.16.17.1,RMON2-MIB::alMatrixSDTable,,not-accessible,,current,,A list of application traffic matrix entries that collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all statistics from a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixSDTable and will be deleted from this table if the address pair is deleted from the nlMatrixSDTable.
.1.3.6.1.2.1.16.17.1.1,RMON2-MIB::alMatrixSDEntry,,not-accessible,hlMatrixControlIndex:alMatrixSDTimeMark:protocolDirLocalIndex:nlMatrixSDSourceAddress:nlMatrixSDDestAddress:protocolDirLocalIndex,current,,A conceptual row in the alMatrixSDTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network-layer protocol of the nlMatrixSDSourceAddress and nlMatrixSDDestAddress. The nlMatrixSDSourceAddress value in the index identifies the network-layer address of the source host in this conversation. The nlMatrixSDDestAddress value in the index identifies the network-layer address of the destination host in this conversation. The second protocolDirLocalIndex value in the index identifies the protocol that is counted by this entry. An example of the indexing of this entry is alMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.34. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.17.1.1.1,RMON2-MIB::alMatrixSDTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.17.1.1.2,RMON2-MIB::alMatrixSDPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted from the source address to the destination address since this entry was added to the alMatrixSDTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.17.1.1.3,RMON2-MIB::alMatrixSDOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixSDTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17.1.1.4,RMON2-MIB::alMatrixSDCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.17.2,RMON2-MIB::alMatrixDSTable,,not-accessible,,current,,A list of application traffic matrix entries that collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all statistics to a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixDSTable and will be deleted from this table if the address pair is deleted from the nlMatrixDSTable.
.1.3.6.1.2.1.16.17.2.1,RMON2-MIB::alMatrixDSEntry,,not-accessible,hlMatrixControlIndex:alMatrixDSTimeMark:protocolDirLocalIndex:nlMatrixDSDestAddress:nlMatrixDSSourceAddress:protocolDirLocalIndex,current,,A conceptual row in the alMatrixDSTable. The hlMatrixControlIndex value in the index identifies the hlMatrixControlEntry on whose behalf this entry was created. The first protocolDirLocalIndex value in the index identifies the network-layer protocol of the alMatrixDSSourceAddress and alMatrixDSDestAddress. The nlMatrixDSDestAddress value in the index identifies the network-layer address of the destination host in this conversation. The nlMatrixDSSourceAddress value in the index identifies the network-layer address of the source host in this conversation. The second protocolDirLocalIndex value in the index identifies the protocol that is counted by this entry. An example of the indexing of this entry is alMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.34. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.17.2.1.1,RMON2-MIB::alMatrixDSTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.16.17.2.1.2,RMON2-MIB::alMatrixDSPkts,Gauge32,read-only,,current,,The number of packets of this protocol type without errors transmitted from the source address to the destination address since this entry was added to the alMatrixDSTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.17.2.1.3,RMON2-MIB::alMatrixDSOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixDSTable (excluding framing bits, but including FCS octets), excluding octets in packets that contained errors. Note that this doesn't count just those octets in the particular protocol frames but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17.2.1.4,RMON2-MIB::alMatrixDSCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.17.3,RMON2-MIB::alMatrixTopNControlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N matrix entries according to a selected metric.
.1.3.6.1.2.1.16.17.3.1,RMON2-MIB::alMatrixTopNControlEntry,,not-accessible,alMatrixTopNControlIndex,current,,A conceptual row in the alMatrixTopNControlTable. An example of the indexing of this table is alMatrixTopNControlDuration.3
.1.3.6.1.2.1.16.17.3.1.1,RMON2-MIB::alMatrixTopNControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the alMatrixTopNControlTable. Each such entry defines one topN report prepared for one interface.
.1.3.6.1.2.1.16.17.3.1.2,RMON2-MIB::alMatrixTopNControlMatrixIndex,Integer32,read-create,,current,,The alMatrix[SD/DS] table for which a topN report will be prepared on behalf of this entry. The alMatrix[SD/DS] table is identified by the value of the hlMatrixControlIndex for that table - that value is used here to identify the particular table. This object may not be modified if the associated alMatrixTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.17.3.1.3,RMON2-MIB::alMatrixTopNControlRateBase,INTEGER,read-create,,current,alMatrixTopNTerminalsPkts(1):alMatrixTopNTerminalsOctets(2):alMatrixTopNAllPkts(3):alMatrixTopNAllOctets(4):alMatrixTopNTerminalsHighCapacityPkts(5):alMatrixTopNTerminalsHighCapacityOctets(6):alMatrixTopNAllHighCapacityPkts(7):alMatrixTopNAllHighCapacityOctets(8),This object controls which alMatrix[SD/DS] entry that the alMatrixTopNEntries are sorted by, which view of the matrix table that will be used, as well as which table the results will be reported in. The values alMatrixTopNTerminalsPkts, alMatrixTopNTerminalsOctets, alMatrixTopNTerminalsHighCapacityPkts, and alMatrixTopNTerminalsHighCapacityOctets cause collection only from protocols that have no child protocols that are counted. The values alMatrixTopNAllPkts, alMatrixTopNAllOctets, alMatrixTopNAllHighCapacityPkts, and alMatrixTopNAllHighCapacityOctets cause collection from all alMatrix entries. This object may not be modified if the associated alMatrixTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.17.3.1.4,RMON2-MIB::alMatrixTopNControlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report and is immediately loaded into the associated alMatrixTopNControlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of alMatrixTopNControlTimeRemaining. Thus, the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the alMatrixTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the alMatrixTopNTable shall be deleted. (Note that this is a different algorithm than the one used in the hostTopNTable).
.1.3.6.1.2.1.16.17.3.1.5,RMON2-MIB::alMatrixTopNControlGeneratedReports,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.17.3.1.6,RMON2-MIB::alMatrixTopNControlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated alMatrixTopNControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the alMatrixTopNControlTimeRemaining is set. This value shall be zero if no reports have been requested for this alMatrixTopNControlEntry.
.1.3.6.1.2.1.16.17.3.1.7,RMON2-MIB::alMatrixTopNControlRequestedSize,Integer32,read-create,,current,,The maximum number of matrix entries requested for this report. When this object is created or modified, the probe should set alMatrixTopNControlGrantedSize as closely to this object as possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.17.3.1.8,RMON2-MIB::alMatrixTopNControlGrantedSize,Integer32,read-only,,current,,The maximum number of matrix entries in this report. When the associated alMatrixTopNControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as possible for the particular implementation and available resources. The probe must not lower this value except as a side-effect of a set to the associated alMatrixTopNControlRequestedSize object. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, when the next topN report is generated, matrix entries with the highest value of alMatrixTopNPktRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, when the next topN report is generated, matrix entries with the highest value of alMatrixTopNOctetRate shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. It is an implementation-specific matter how entries with the same value of alMatrixTopNPktRate or alMatrixTopNOctetRate are sorted. It is also an implementation-specific matter as to whether zero-valued entries are available.
.1.3.6.1.2.1.16.17.3.1.9,RMON2-MIB::alMatrixTopNControlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this topN report was last started. In other words, this is the time that the associated alMatrixTopNControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine whether a report was missed.
.1.3.6.1.2.1.16.17.3.1.10,RMON2-MIB::alMatrixTopNControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.17.3.1.11,RMON2-MIB::alMatrixTopNControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this alMatrixTopNControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the alMatrixTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.17.4,RMON2-MIB::alMatrixTopNTable,,not-accessible,,current,,A set of statistics for those application-layer matrix entries that have counted the highest number of octets or packets.
.1.3.6.1.2.1.16.17.4.1,RMON2-MIB::alMatrixTopNEntry,,not-accessible,alMatrixTopNControlIndex:alMatrixTopNIndex,current,,A conceptual row in the alMatrixTopNTable. The alMatrixTopNControlIndex value in the index identifies the alMatrixTopNControlEntry on whose behalf this entry was created. An example of the indexing of this table is alMatrixTopNPktRate.3.10
.1.3.6.1.2.1.16.17.4.1.1,RMON2-MIB::alMatrixTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the alMatrixTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, increasing values of alMatrixTopNIndex shall be assigned to entries with decreasing values of alMatrixTopNPktRate until index N is assigned or there are no more alMatrixTopNEntries. If the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, increasing values of alMatrixTopNIndex shall be assigned to entries with decreasing values of alMatrixTopNOctetRate until index N is assigned or there are no more alMatrixTopNEntries.
.1.3.6.1.2.1.16.17.4.1.2,RMON2-MIB::alMatrixTopNProtocolDirLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex of the network-layer protocol of this entry's network address.
.1.3.6.1.2.1.16.17.4.1.3,RMON2-MIB::alMatrixTopNSourceAddress,OCTET,read-only,,current,,The network-layer address of the source host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated alMatrixTopNProtocolDirLocalIndex. For example, if the alMatrixTopNProtocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.17.4.1.4,RMON2-MIB::alMatrixTopNDestAddress,OCTET,read-only,,current,,The network-layer address of the destination host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated alMatrixTopNProtocolDirLocalIndex. For example, if the alMatrixTopNProtocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order.
.1.3.6.1.2.1.16.17.4.1.5,RMON2-MIB::alMatrixTopNAppProtocolDirLocalIndex,Integer32,read-only,,current,,The type of the protocol counted by this matrix entry.
.1.3.6.1.2.1.16.17.4.1.6,RMON2-MIB::alMatrixTopNPktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the alMatrixSDPkts object. If the value of alMatrixTopNControlRateBase is alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, this variable will be used to sort this report.
.1.3.6.1.2.1.16.17.4.1.7,RMON2-MIB::alMatrixTopNReversePktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the alMatrixDSPkts object. (Note that the corresponding alMatrixSDPkts object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.) Note that if the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, the sort of topN entries is based entirely on alMatrixTopNPktRate, and not on the value of this object.
.1.3.6.1.2.1.16.17.4.1.8,RMON2-MIB::alMatrixTopNOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the alMatrixSDOctets object. If the value of alMatrixTopNControlRateBase is alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, this variable will be used to sort this report.
.1.3.6.1.2.1.16.17.4.1.9,RMON2-MIB::alMatrixTopNReverseOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the alMatrixDSOctets object. (Note that the corresponding alMatrixSDOctets object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.) Note that if the value of alMatrixTopNControlRateBase is equal to alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, the sort of topN entries is based entirely on alMatrixTopNOctetRate, and not on the value of this object.
.1.3.6.1.2.1.16.17.5,HC-RMON-MIB::alMatrixSDHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 alMatrixSDTable.
.1.3.6.1.2.1.16.17.5.1,HC-RMON-MIB::alMatrixSDHighCapacityEntry,,not-accessible,hlMatrixControlIndex:alMatrixSDTimeMark:protocolDirLocalIndex:nlMatrixSDSourceAddress:nlMatrixSDDestAddress:protocolDirLocalIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 alMatrixSDEntry. These objects will be created by the agent for all alMatrixSDEntries associated with whichever hlMatrixControlEntries it deems appropriate. (i.e., either all alMatrixSDHighCapacityEntries associated with a particular hlMatrixControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.17.5.1.1,HC-RMON-MIB::alMatrixSDHighCapacityOverflowPkts,Gauge32,read-only,,current,,The number of times the associated alMatrixSDPkts counter has overflowed.
.1.3.6.1.2.1.16.17.5.1.2,HC-RMON-MIB::alMatrixSDHighCapacityPkts,Counter64,read-only,,current,,The number of good packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixSDHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.17.5.1.3,HC-RMON-MIB::alMatrixSDHighCapacityOverflowOctets,Gauge32,read-only,,current,,The number of times the associated alMatrixSDOctets counter has overflowed.
.1.3.6.1.2.1.16.17.5.1.4,HC-RMON-MIB::alMatrixSDHighCapacityOctets,Counter64,read-only,,current,,The number of octets in good packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixSDHighCapacityTable (excluding framing bits but including FCS octets). Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17.6,HC-RMON-MIB::alMatrixDSHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 alMatrixDSTable.
.1.3.6.1.2.1.16.17.6.1,HC-RMON-MIB::alMatrixDSHighCapacityEntry,,not-accessible,hlMatrixControlIndex:alMatrixDSTimeMark:protocolDirLocalIndex:nlMatrixDSDestAddress:nlMatrixDSSourceAddress:protocolDirLocalIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 alMatrixSDTable. These objects will be created by the agent for all alMatrixDSEntries associated with whichever hlMatrixControlEntries it deems appropriate. (i.e., either all alMatrixDSHighCapacityEntries associated with a particular hlMatrixControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.17.6.1.1,HC-RMON-MIB::alMatrixDSHighCapacityOverflowPkts,Gauge32,read-only,,current,,The number of times the associated alMatrixDSPkts counter has overflowed.
.1.3.6.1.2.1.16.17.6.1.2,HC-RMON-MIB::alMatrixDSHighCapacityPkts,Counter64,read-only,,current,,The number of good packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixDSHighCapacityTable. Note that this is the number of link-layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.17.6.1.3,HC-RMON-MIB::alMatrixDSHighCapacityOverflowOctets,Gauge32,read-only,,current,,The number of times the associated alMatrixDSOctets counter has overflowed.
.1.3.6.1.2.1.16.17.6.1.4,HC-RMON-MIB::alMatrixDSHighCapacityOctets,Counter64,read-only,,current,,The number of octets in good packets of this protocol type transmitted from the source address to the destination address since this entry was added to the alMatrixDSHighCapacityTable (excluding framing bits but including FCS octets). Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.17.7,HC-RMON-MIB::alMatrixTopNHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 alMatrixTopNTable when alMatrixTopNControlRateBase specifies a High Capacity TopN Report.
.1.3.6.1.2.1.16.17.7.1,HC-RMON-MIB::alMatrixTopNHighCapacityEntry,,not-accessible,alMatrixTopNControlIndex:alMatrixTopNIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 alMatrixTopNEntry when alMatrixTopNControlRateBase specifies a High Capacity TopN Report. These objects will be created by the agent for all alMatrixTopNEntries associated with whichever alMatrixTopNControlEntries have a alMatrixTopNControlRateBase that specify a high capacity report.
.1.3.6.1.2.1.16.17.7.1.1,HC-RMON-MIB::alMatrixTopNHighCapacityProtocolDirLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex of the network layer protocol of this entry's network address.
.1.3.6.1.2.1.16.17.7.1.2,HC-RMON-MIB::alMatrixTopNHighCapacitySourceAddress,OCTET,read-only,,current,,The network layer address of the source host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated alMatrixTopNProtocolDirLocalIndex. For example, if the alMatrixTopNProtocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.
.1.3.6.1.2.1.16.17.7.1.3,HC-RMON-MIB::alMatrixTopNHighCapacityDestAddress,OCTET,read-only,,current,,The network layer address of the destination host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated alMatrixTopNProtocolDirLocalIndex. For example, if the alMatrixTopNProtocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order.
.1.3.6.1.2.1.16.17.7.1.4,HC-RMON-MIB::alMatrixTopNHighCapacityAppProtocolDirLocalIndex,Integer32,read-only,,current,,The type of the protocol counted by this entry.
.1.3.6.1.2.1.16.17.7.1.5,HC-RMON-MIB::alMatrixTopNHighCapacityBasePktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, modulo 2^32, counted using the rules for counting the alMatrixSDPkts object.
.1.3.6.1.2.1.16.17.7.1.6,HC-RMON-MIB::alMatrixTopNHighCapacityOverflowPktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the alMatrixSDPkts object.
.1.3.6.1.2.1.16.17.7.1.7,HC-RMON-MIB::alMatrixTopNHighCapacityPktRate,Counter64,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the alMatrixSDPkts object. If the value of alMatrixTopNControlRateBase is alMatrixTopNTerminalsPkts, alMatrixTopNAllPkts, alMatrixTopNTerminalsHighCapacityPkts, or alMatrixTopNAllHighCapacityPkts, this variable will be used to sort this report.
.1.3.6.1.2.1.16.17.7.1.8,HC-RMON-MIB::alMatrixTopNHighCapacityReverseBasePktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, modulo 2^32, counted using the rules for counting the alMatrixSDPkts object (note that the corresponding alMatrixSDPkts object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.17.7.1.9,HC-RMON-MIB::alMatrixTopNHighCapacityReverseOverflowPktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the alMatrixSDPkts object (note that the corresponding alMatrixSDPkts object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.17.7.1.10,HC-RMON-MIB::alMatrixTopNHighCapacityReversePktRate,Counter64,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the alMatrixSDPkts object (note that the corresponding alMatrixSDPkts object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.17.7.1.11,HC-RMON-MIB::alMatrixTopNHighCapacityBaseOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, modulo 2^32, counted using the rules for counting the alMatrixSDOctets object.
.1.3.6.1.2.1.16.17.7.1.12,HC-RMON-MIB::alMatrixTopNHighCapacityOverflowOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the alMatrixSDOctets object.
.1.3.6.1.2.1.16.17.7.1.13,HC-RMON-MIB::alMatrixTopNHighCapacityOctetRate,Counter64,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the alMatrixSDOctets object. If the value of alMatrixTopNControlRateBase is alMatrixTopNTerminalsOctets, alMatrixTopNAllOctets, alMatrixTopNTerminalsHighCapacityOctets, or alMatrixTopNAllHighCapacityOctets, this variable will be used to sort this report.
.1.3.6.1.2.1.16.17.7.1.14,HC-RMON-MIB::alMatrixTopNHighCapacityReverseBaseOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, modulo 2^32, counted using the rules for counting the alMatrixSDOctets object (note that the corresponding alMatrixSDOctets object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.17.7.1.15,HC-RMON-MIB::alMatrixTopNHighCapacityReverseOverflowOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, divided by 2^32, truncating fractions (i.e., X DIV 2^32), and counted using the rules for counting the alMatrixSDOctets object (note that the corresponding alMatrixSDOctets object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.17.7.1.16,HC-RMON-MIB::alMatrixTopNHighCapacityReverseOctetRate,Counter64,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the alMatrixSDOctets object (note that the corresponding alMatrixSDOctets object selected is the one whose source address is equal to alMatrixTopNDestAddress and whose destination address is equal to alMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.18,RMON2-MIB::usrHistory,,,,,,
.1.3.6.1.2.1.16.18.1,RMON2-MIB::usrHistoryControlTable,,not-accessible,,current,,A list of data-collection configuration entries.
.1.3.6.1.2.1.16.18.1.1,RMON2-MIB::usrHistoryControlEntry,,not-accessible,usrHistoryControlIndex,current,,A list of parameters that set up a group of user-defined MIB objects to be sampled periodically (called a bucket-group). For example, an instance of usrHistoryControlInterval might be named usrHistoryControlInterval.1
.1.3.6.1.2.1.16.18.1.1.1,RMON2-MIB::usrHistoryControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the usrHistoryControlTable. Each such entry defines a set of samples at a particular interval for a specified set of MIB instances available from the managed system.
.1.3.6.1.2.1.16.18.1.1.2,RMON2-MIB::usrHistoryControlObjects,Integer32,read-create,,current,,The number of MIB objects to be collected in the portion of usrHistoryTable associated with this usrHistoryControlEntry. This object may not be modified if the associated instance of usrHistoryControlStatus is equal to active(1).
.1.3.6.1.2.1.16.18.1.1.3,RMON2-MIB::usrHistoryControlBucketsRequested,Integer32,read-create,,current,,The requested number of discrete time intervals over which data is to be saved in the part of the usrHistoryTable associated with this usrHistoryControlEntry. When this object is created or modified, the probe should set usrHistoryControlBucketsGranted as closely to this object as possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.18.1.1.4,RMON2-MIB::usrHistoryControlBucketsGranted,Integer32,read-only,,current,,The number of discrete sampling intervals over which data shall be saved in the part of the usrHistoryTable associated with this usrHistoryControlEntry. When the associated usrHistoryControlBucketsRequested object is created or modified, the probe should set this object as closely to the requested value as possible for the particular probe implementation and available resources. The probe must not lower this value except as a result of a modification to the associated usrHistoryControlBucketsRequested object. The associated usrHistoryControlBucketsRequested object should be set before or at the same time as this object to allow the probe to accurately estimate the resources required for this usrHistoryControlEntry. There will be times when the actual number of buckets associated with this entry is less than the value of this object. In this case, at the end of each sampling interval, a new bucket will be added to the usrHistoryTable. When the number of buckets reaches the value of this object and a new bucket is to be added to the usrHistoryTable, the oldest bucket associated with this usrHistoryControlEntry shall be deleted by the agent so that the new bucket can be added. When the value of this object changes to a value less than the current value, entries are deleted from the usrHistoryTable associated with this usrHistoryControlEntry. Enough of the oldest of these entries shall be deleted by the agent so that their number remains less than or equal to the new value of this object. When the value of this object changes to a value greater than the current value, the number of associated usrHistory entries may be allowed to grow.
.1.3.6.1.2.1.16.18.1.1.5,RMON2-MIB::usrHistoryControlInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled for each bucket in the part of the usrHistory table associated with this usrHistoryControlEntry. Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and to set the usrHistoryControlInterval object to a value less than this interval. This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.18.1.1.6,RMON2-MIB::usrHistoryControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.18.1.1.7,RMON2-MIB::usrHistoryControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this variable history control entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the usrHistoryTable shall be deleted.
.1.3.6.1.2.1.16.18.2,RMON2-MIB::usrHistoryObjectTable,,not-accessible,,current,,A list of data-collection configuration entries.
.1.3.6.1.2.1.16.18.2.1,RMON2-MIB::usrHistoryObjectEntry,,not-accessible,usrHistoryControlIndex:usrHistoryObjectIndex,current,,A list of MIB instances to be sampled periodically. Entries in this table are created when an associated usrHistoryControlObjects object is created. The usrHistoryControlIndex value in the index is that of the associated usrHistoryControlEntry. For example, an instance of usrHistoryObjectVariable might be usrHistoryObjectVariable.1.3
.1.3.6.1.2.1.16.18.2.1.1,RMON2-MIB::usrHistoryObjectIndex,Integer32,not-accessible,,current,,An index used to uniquely identify an entry in the usrHistoryObject table. Each such entry defines a MIB instance to be collected periodically.
.1.3.6.1.2.1.16.18.2.1.2,RMON2-MIB::usrHistoryObjectVariable,OBJECT,read-create,,current,,The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of Integer32 (Integer32, Counter, Gauge, or TimeTicks) may be sampled. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the user history mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. See USM [RFC3414] and VACM [RFC3415] for more information. During a set operation, if the supplied variable name is not available in the selected MIB view, a badValue error must be returned. This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.18.2.1.3,RMON2-MIB::usrHistoryObjectSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The method of sampling the selected variable for storage in the usrHistoryTable. If the value of this object is absoluteValue(1), the value of the selected variable will be copied directly into the history bucket. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference will be stored in the history bucket. If the associated usrHistoryObjectVariable instance could not be obtained at the previous sample interval, then a delta sample is not possible, and the value of the associated usrHistoryValStatus object for this interval will be valueNotAvailable(1). This object may not be modified if the associated usrHistoryControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.18.3,RMON2-MIB::usrHistoryTable,,not-accessible,,current,,A list of user-defined history entries.
.1.3.6.1.2.1.16.18.3.1,RMON2-MIB::usrHistoryEntry,,not-accessible,usrHistoryControlIndex:usrHistorySampleIndex:usrHistoryObjectIndex,current,,A historical sample of user-defined variables. This sample is associated with the usrHistoryControlEntry that set up the parameters for a regular collection of these samples. The usrHistoryControlIndex value in the index identifies the usrHistoryControlEntry on whose behalf this entry was created. The usrHistoryObjectIndex value in the index identifies the usrHistoryObjectEntry on whose behalf this entry was created. For example, an instance of usrHistoryAbsValue, which represents the 14th sample of a variable collected as specified by usrHistoryControlEntry.1 and usrHistoryObjectEntry.1.5, would be named usrHistoryAbsValue.1.14.5
.1.3.6.1.2.1.16.18.3.1.1,RMON2-MIB::usrHistorySampleIndex,Integer32,not-accessible,,current,,An index that uniquely identifies the particular sample this entry represents among all samples associated with the same usrHistoryControlEntry. This index starts at 1 and increases by one as each new sample is taken.
.1.3.6.1.2.1.16.18.3.1.2,RMON2-MIB::usrHistoryIntervalStart,TimeTicks,read-only,,current,,The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require that the probe delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample that is currently being collected is not accessible in this table until the end of its interval.
.1.3.6.1.2.1.16.18.3.1.3,RMON2-MIB::usrHistoryIntervalEnd,TimeTicks,read-only,,current,,The value of sysUpTime at the end of the interval over which this sample was measured.
.1.3.6.1.2.1.16.18.3.1.4,RMON2-MIB::usrHistoryAbsValue,Gauge32,read-only,,current,,The absolute value (i.e., unsigned value) of the user-specified statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed. To obtain the true value for this sampling interval, the associated instance of usrHistoryValStatus must be checked, and usrHistoryAbsValue adjusted as necessary. If the MIB instance could not be accessed during the sampling interval, then this object will have a value of zero, and the associated instance of usrHistoryValStatus will be set to 'valueNotAvailable(1)'. The access control check prescribed in the definition of usrHistoryObjectVariable SHOULD be checked for each sampling interval. If this check determines that access should not be allowed, then this object will have a value of zero, and the associated instance of usrHistoryValStatus will be set to 'valueNotAvailable(1)'.
.1.3.6.1.2.1.16.18.3.1.5,RMON2-MIB::usrHistoryValStatus,INTEGER,read-only,,current,valueNotAvailable(1):valuePositive(2):valueNegative(3),This object indicates the validity and sign of the data in the associated instance of usrHistoryAbsValue. If the MIB instance could not be accessed during the sampling interval, then 'valueNotAvailable(1)' will be returned. If the sample is valid and the actual value of the sample is greater than or equal to zero, then 'valuePositive(2)' is returned. If the sample is valid and the actual value of the sample is less than zero, 'valueNegative(3)' will be returned. The associated instance of usrHistoryAbsValue should be multiplied by -1 to obtain the true sample value.
.1.3.6.1.2.1.16.18.4,HC-RMON-MIB::usrHistoryHighCapacityTable,,not-accessible,,current,,Contains the High Capacity RMON extensions to the RMON-2 usrHistoryTable.
.1.3.6.1.2.1.16.18.4.1,HC-RMON-MIB::usrHistoryHighCapacityEntry,,not-accessible,usrHistoryControlIndex:usrHistorySampleIndex:usrHistoryObjectIndex,current,,Contains the High Capacity RMON extensions to the RMON-2 usrHistoryEntry. These objects will be created by the agent for all usrHistoryEntries associated with whichever usrHistoryControlEntries it deems appropriate. (i.e., either all usrHistoryHighCapacityEntries associated with a particular usrHistoryControlEntry will be created, or none of them will be.)
.1.3.6.1.2.1.16.18.4.1.1,HC-RMON-MIB::usrHistoryHighCapacityOverflowAbsValue,Gauge32,read-only,,current,,The absolute value (i.e. unsigned value) of the user-specified statistic during the last sampling period, divided by 2^32, truncating fractions (i.e., X DIV 2^32). The value during the current sampling period is not made available until the period is completed. To obtain the true value for this sampling interval, the associated instance of usrHistoryValStatus should be checked, and usrHistoryAbsValue adjusted as necessary. If the MIB instance could not be accessed during the sampling interval, then this object will have a value of zero and the associated instance of usrHistoryValStatus will be set to 'valueNotAvailable(1)'.
.1.3.6.1.2.1.16.18.4.1.2,HC-RMON-MIB::usrHistoryHighCapacityAbsValue,Counter64,read-only,,current,,The absolute value (i.e. unsigned value) of the user-specified statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed. To obtain the true value for this sampling interval, the associated instance of usrHistoryValStatus should be checked, and usrHistoryHighCapacityAbsValue adjusted as necessary. If the MIB instance could not be accessed during the sampling interval, then this object will have a value of zero and the associated instance of usrHistoryValStatus will be set to 'valueNotAvailable(1)'.
.1.3.6.1.2.1.16.19,RMON2-MIB::probeConfig,,,,,,
.1.3.6.1.2.1.16.19.1,RMON2-MIB::probeCapabilities,BITS,read-only,,current,etherStats(0):historyControl(1):etherHistory(2):alarm(3):hosts(4):hostTopN(5):matrix(6):filter(7):capture(8):event(9):tokenRingMLStats(10):tokenRingPStats(11):tokenRingMLHistory(12):tokenRingPHistory(13):ringStation(14):ringStationOrder(15):ringStationConfig(16):sourceRouting(17):protocolDirectory(18):protocolDistribution(19):addressMapping(20):nlHost(21):nlMatrix(22):alHost(23):alMatrix(24):usrHistory(25):probeConfig(26),An indication of the RMON MIB groups supported on at least one interface by this probe.
.1.3.6.1.2.1.16.19.2,RMON2-MIB::probeSoftwareRev,OCTET,read-only,,current,,The software revision of this device. This string will have a zero length if the revision is unknown.
.1.3.6.1.2.1.16.19.3,RMON2-MIB::probeHardwareRev,OCTET,read-only,,current,,The hardware revision of this device. This string will have a zero length if the revision is unknown.
.1.3.6.1.2.1.16.19.4,RMON2-MIB::probeDateTime,OCTET,read-write,,current,,Probe's current date and time. field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11 10 11 minutes from UTC 0..59 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then time zone information (fields 8-10) is not present, and that if no time information is known, the null string is returned.
.1.3.6.1.2.1.16.19.5,RMON2-MIB::probeResetControl,INTEGER,read-write,,current,running(1):warmBoot(2):coldBoot(3),Setting this object to warmBoot(2) causes the device to restart the application software with current configuration parameters saved in non-volatile memory. Setting this object to coldBoot(3) causes the device to reinitialize configuration parameters in non-volatile memory to default values and to restart the application software. When the device is running normally, this variable has a value of running(1).
.1.3.6.1.2.1.16.19.6,RMON2-MIB::probeDownloadFile,OCTET,read-write,,deprecated,,The file name to be downloaded from the TFTP server when a download is next requested via this MIB. This value is set to the zero-length string when no file name has been specified. This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.7,RMON2-MIB::probeDownloadTFTPServer,IpAddress,read-write,,deprecated,,The IP address of the TFTP server that contains the boot image to load when a download is next requested via this MIB. This value is set to '0.0.0.0' when no IP address has been specified. This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.8,RMON2-MIB::probeDownloadAction,INTEGER,read-write,,deprecated,notDownloading(1):downloadToPROM(2):downloadToRAM(3),When this object is set to downloadToRAM(3) or downloadToPROM(2), the device will discontinue its normal operation and begin download of the image specified by probeDownloadFile from the server specified by probeDownloadTFTPServer using the TFTP protocol. If downloadToRAM(3) is specified, the new image is copied to RAM only (the old image remains unaltered in the flash EPROM). If downloadToPROM(2) is specified, the new image is written to the flash EPROM memory after its checksum has been verified to be correct. When the download process is completed, the device will warm boot to restart the newly loaded application. When the device is not downloading, this object will have a value of notDownloading(1). This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.9,RMON2-MIB::probeDownloadStatus,INTEGER,read-only,,deprecated,downloadSuccess(1):downloadStatusUnknown(2):downloadGeneralError(3):downloadNoResponseFromServer(4):downloadChecksumError(5):downloadIncompatibleImage(6):downloadTftpFileNotFound(7):downloadTftpAccessViolation(8),The status of the last download procedure, if any. This object will have a value of downloadStatusUnknown(2) if no download process has been performed. This object has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.10,RMON2-MIB::serialConfigTable,,not-accessible,,deprecated,,A table of serial interface configuration entries. This data will be stored in non-volatile memory and preserved across probe resets or power loss. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.10.1,RMON2-MIB::serialConfigEntry,,not-accessible,ifIndex,deprecated,,A set of configuration parameters for a particular serial interface on this device. If the device has no serial interfaces, this table is empty. The index is composed of the ifIndex assigned to this serial line interface.
.1.3.6.1.2.1.16.19.10.1.1,RMON2-MIB::serialMode,INTEGER,read-create,,deprecated,direct(1):modem(2),The type of incoming connection to be expected on this serial interface.
.1.3.6.1.2.1.16.19.10.1.2,RMON2-MIB::serialProtocol,INTEGER,read-create,,deprecated,other(1):slip(2):ppp(3),The type of data link encapsulation to be used on this serial interface.
.1.3.6.1.2.1.16.19.10.1.3,RMON2-MIB::serialTimeout,Integer32,read-create,,deprecated,,This timeout value is used when the Management Station has initiated the conversation over the serial link. This variable represents the number of seconds of inactivity allowed before terminating the connection on this serial interface. Use the serialDialoutTimeout in the case where the probe has initiated the connection for the purpose of sending a trap.
.1.3.6.1.2.1.16.19.10.1.4,RMON2-MIB::serialModemInitString,OCTET,read-create,,deprecated,,A control string that controls how a modem attached to this serial interface should be initialized. The initialization is performed once during startup and again after each connection is terminated if the associated serialMode has the value of modem(2). A control string that is appropriate for a wide variety of modems is: '^s^MATE0Q0V1X4 S0=1 S2=43^M'.
.1.3.6.1.2.1.16.19.10.1.5,RMON2-MIB::serialModemHangUpString,OCTET,read-create,,deprecated,,A control string that specifies how to disconnect a modem connection on this serial interface. This object is only meaningful if the associated serialMode has the value of modem(2). A control string that is appropriate for a wide variety of modems is: '^d2^s+++^d2^sATH0^M^d2'.
.1.3.6.1.2.1.16.19.10.1.6,RMON2-MIB::serialModemConnectResp,OCTET,read-create,,deprecated,,An ASCII string containing substrings that describe the expected modem connection response code and associated bps rate. The substrings are delimited by the first character in the string, for example: /CONNECT/300/CONNECT 1200/1200/CONNECT 2400/2400/ CONNECT 4800/4800/CONNECT 9600/9600 will be interpreted as: response code bps rate CONNECT 300 CONNECT 1200 1200 CONNECT 2400 2400 CONNECT 4800 4800 CONNECT 9600 9600 The agent will use the information in this string to adjust the bps rate of this serial interface once a modem connection is established. A value that is appropriate for a wide variety of modems is: '/CONNECT/300/CONNECT 1200/1200/CONNECT 2400/2400/ CONNECT 4800/4800/CONNECT 9600/9600/CONNECT 14400/14400/ CONNECT 19200/19200/CONNECT 38400/38400/'.
.1.3.6.1.2.1.16.19.10.1.7,RMON2-MIB::serialModemNoConnectResp,OCTET,read-create,,deprecated,,An ASCII string containing response codes that may be generated by a modem to report the reason why a connection attempt has failed. The response codes are delimited by the first character in the string, for example: /NO CARRIER/BUSY/NO DIALTONE/NO ANSWER/ERROR/ If one of these response codes is received via this serial interface while attempting to make a modem connection, the agent will issue the hang up command as specified by serialModemHangUpString. A value that is appropriate for a wide variety of modems is: '/NO CARRIER/BUSY/NO DIALTONE/NO ANSWER/ERROR/'.
.1.3.6.1.2.1.16.19.10.1.8,RMON2-MIB::serialDialoutTimeout,Integer32,read-create,,deprecated,,This timeout value is used when the probe initiates the serial connection with the intention of contacting a management station. This variable represents the number of seconds of inactivity allowed before terminating the connection on this serial interface.
.1.3.6.1.2.1.16.19.10.1.9,RMON2-MIB::serialStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this serialConfigEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.11,RMON2-MIB::netConfigTable,,not-accessible,,deprecated,,A table of netConfigEntries. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.11.1,RMON2-MIB::netConfigEntry,,not-accessible,ifIndex,deprecated,,A set of configuration parameters for a particular network interface on this device. If the device has no network interface, this table is empty. The index is composed of the ifIndex assigned to the corresponding interface.
.1.3.6.1.2.1.16.19.11.1.1,RMON2-MIB::netConfigIPAddress,IpAddress,read-create,,deprecated,,The IP address of this Net interface. The default value for this object is 0.0.0.0. If either the netConfigIPAddress or netConfigSubnetMask is 0.0.0.0, then when the device boots, it may use BOOTP to try to figure out what these values should be. If BOOTP fails before the device can talk on the network, this value must be configured (e.g., through a terminal attached to the device). If BOOTP is used, care should be taken to not send BOOTP broadcasts too frequently and to eventually send them very infrequently if no replies are received.
.1.3.6.1.2.1.16.19.11.1.2,RMON2-MIB::netConfigSubnetMask,IpAddress,read-create,,deprecated,,The subnet mask of this Net interface. The default value for this object is 0.0.0.0. If either the netConfigIPAddress or netConfigSubnetMask is 0.0.0.0, then when the device boots, it may use BOOTP to try to figure out what these values should be. If BOOTP fails before the device can talk on the network, this value must be configured (e.g., through a terminal attached to the device). If BOOTP is used, care should be taken to not send BOOTP broadcasts too frequently and to eventually send them very infrequently if no replies are received.
.1.3.6.1.2.1.16.19.11.1.3,RMON2-MIB::netConfigStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this netConfigEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.12,RMON2-MIB::netDefaultGateway,IpAddress,read-write,,deprecated,,The IP Address of the default gateway. If this value is undefined or unknown, it shall have the value 0.0.0.0.
.1.3.6.1.2.1.16.19.13,RMON2-MIB::trapDestTable,,not-accessible,,deprecated,,A list of trap destination entries.
.1.3.6.1.2.1.16.19.13.1,RMON2-MIB::trapDestEntry,,not-accessible,trapDestIndex,deprecated,,This entry includes a destination IP address to which traps are sent for this community.
.1.3.6.1.2.1.16.19.13.1.1,RMON2-MIB::trapDestIndex,Integer32,not-accessible,,deprecated,,A value that uniquely identifies this trapDestEntry.
.1.3.6.1.2.1.16.19.13.1.2,RMON2-MIB::trapDestCommunity,OCTET,read-create,,deprecated,,A community to which this destination address belongs. This entry is associated with any eventEntries in the RMON MIB whose value of eventCommunity is equal to the value of this object. Every time an associated event entry sends a trap due to an event, that trap will be sent to each address in the trapDestTable with a trapDestCommunity equal to eventCommunity, as long as no access control mechanism precludes it (e.g., VACM). This object may not be modified if the associated trapDestStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.13.1.3,RMON2-MIB::trapDestProtocol,INTEGER,read-create,,deprecated,ip(1):ipx(2),The protocol with which this trap is to be sent.
.1.3.6.1.2.1.16.19.13.1.4,RMON2-MIB::trapDestAddress,OCTET,read-create,,deprecated,,The destination address for traps on behalf of this entry. If the associated trapDestProtocol object is equal to ip(1), the encoding of this object is the same as the snmpUDPAddress textual convention in RFC 3417, 'Transport Mappings for the Simple Network Management Protocol (SNMP)' [RFC3417]: -- for a SnmpUDPAddress of length 6: -- -- octets contents encoding -- 1-4 IP-address network-byte order -- 5-6 UDP-port network-byte order If the associated trapDestProtocol object is equal to ipx(2), the encoding of this object is the same as the snmpIPXAddress textual convention in RFC 3417, 'Transport Mappings for the Simple Network Management Protocol (SNMP)' [RFC3417]: -- for a SnmpIPXAddress of length 12: -- -- octets contents encoding -- 1-4 network-number network-byte order -- 5-10 physical-address network-byte order -- 11-12 socket-number network-byte order This object may not be modified if the associated trapDestStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.13.1.5,RMON2-MIB::trapDestOwner,OCTET,read-create,,deprecated,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.19.13.1.6,RMON2-MIB::trapDestStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this trap destination entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.14,RMON2-MIB::serialConnectionTable,,not-accessible,,deprecated,,A list of serialConnectionEntries. This table has been deprecated, as it has not had enough independent implementations to demonstrate interoperability to meet the requirements of a Draft Standard.
.1.3.6.1.2.1.16.19.14.1,RMON2-MIB::serialConnectionEntry,,not-accessible,serialConnectIndex,deprecated,,Configuration for a SLIP link over a serial line.
.1.3.6.1.2.1.16.19.14.1.1,RMON2-MIB::serialConnectIndex,Integer32,not-accessible,,deprecated,,A value that uniquely identifies this serialConnection entry.
.1.3.6.1.2.1.16.19.14.1.2,RMON2-MIB::serialConnectDestIpAddress,IpAddress,read-create,,deprecated,,The IP Address that can be reached at the other end of this serial connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.3,RMON2-MIB::serialConnectType,INTEGER,read-create,,deprecated,direct(1):modem(2):switch(3):modemSwitch(4),The type of outgoing connection to be made. If this object has the value direct(1), then a direct serial connection is assumed. If this object has the value modem(2), then serialConnectDialString will be used to make a modem connection. If this object has the value switch(3), then serialConnectSwitchConnectSeq will be used to establish the connection over a serial data switch, and serialConnectSwitchDisconnectSeq will be used to terminate the connection. If this object has the value modem-switch(4), then a modem connection will be made first, followed by the switch connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.4,RMON2-MIB::serialConnectDialString,OCTET,read-create,,deprecated,,A control string that specifies how to dial the phone number in order to establish a modem connection. The string should include the dialing prefix and suffix. For example: '^s^MATD9,888-1234^M' will instruct the Probe to send a carriage return, followed by the dialing prefix 'ATD', the phone number '9,888-1234', and a carriage return as the dialing suffix. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.5,RMON2-MIB::serialConnectSwitchConnectSeq,OCTET,read-create,,deprecated,,A control string that specifies how to establish a data switch connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.6,RMON2-MIB::serialConnectSwitchDisconnectSeq,OCTET,read-create,,deprecated,,A control string that specifies how to terminate a data switch connection. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.7,RMON2-MIB::serialConnectSwitchResetSeq,OCTET,read-create,,deprecated,,A control string that specifies how to reset a data switch in the event of a timeout. This object may not be modified if the associated serialConnectStatus object is equal to active(1).
.1.3.6.1.2.1.16.19.14.1.8,RMON2-MIB::serialConnectOwner,OCTET,read-create,,deprecated,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.19.14.1.9,RMON2-MIB::serialConnectStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this serialConnectionEntry. If the manager attempts to set this object to active(1) when the serialConnectType is set to modem(2) or modem-switch(4) and the serialConnectDialString is a zero-length string or cannot be correctly parsed as a ConnectString, the set request will be rejected with badValue(3). If the manager attempts to set this object to active(1) when the serialConnectType is set to switch(3) or modem-switch(4) and the serialConnectSwitchConnectSeq, the serialConnectSwitchDisconnectSeq, or the serialConnectSwitchResetSeq is a zero-length string or cannot be correctly parsed as a ConnectString, the set request will be rejected with badValue(3). An entry may not exist in the active state unless all objects in the entry have an appropriate value.
.1.3.6.1.2.1.16.19.15,SMON-MIB::smonCapabilities,BITS,read-only,,current,smonVlanStats(0):smonPrioStats(1):dataSource(2):smonUnusedBit(3):portCopy(4),An indication of the SMON MIB groups supported by this agent.
.1.3.6.1.2.1.16.19.16,HC-RMON-MIB::hcRMONCapabilities,BITS,read-only,,current,mediaIndependentGroup(0):etherStatsHighCapacityGroup(1):etherHistoryHighCapacityGroup(2):hostHighCapacityGroup(3):hostTopNHighCapacityGroup(4):matrixHighCapacityGroup(5):captureBufferHighCapacityGroup(6):protocolDistributionHighCapacityGroup(7):nlHostHighCapacityGroup(8):nlMatrixHighCapacityGroup(9):nlMatrixTopNHighCapacityGroup(10):alHostHighCapacityGroup(11):alMatrixHighCapacityGroup(12):alMatrixTopNHighCapacityGroup(13):usrHistoryHighCapacityGroup(14),An indication of the High Capacity RMON MIB groups supported on at least one interface by this probe.
.1.3.6.1.2.1.16.20,RMON-MIB::rmonConformance,,,,,,
.1.3.6.1.2.1.16.20.1,RMON2-MIB::rmon2MIBCompliances,,,,,,
.1.3.6.1.2.1.16.20.1.1,RMON2-MIB::rmon2MIBCompliance,,,,,,Describes the requirements for conformance to the RMON2 MIB
.1.3.6.1.2.1.16.20.1.2,RMON2-MIB::rmon2MIBApplicationLayerCompliance,,,,,,Describes the requirements for conformance to the RMON2 MIB with Application-Layer Enhancements.
.1.3.6.1.2.1.16.20.2,RMON2-MIB::rmon2MIBGroups,,,,,,
.1.3.6.1.2.1.16.20.2.1,RMON2-MIB::protocolDirectoryGroup,,,,,,Lists the inventory of protocols the probe has the capability of monitoring and allows the addition, deletion, and configuration of entries in this list.
.1.3.6.1.2.1.16.20.2.2,RMON2-MIB::protocolDistributionGroup,,,,,,Collects the relative amounts of octets and packets for the different protocols detected on a network segment.
.1.3.6.1.2.1.16.20.2.3,RMON2-MIB::addressMapGroup,,,,,,Lists MAC address to network address bindings discovered by the probe and what interface they were last seen on.
.1.3.6.1.2.1.16.20.2.4,RMON2-MIB::nlHostGroup,,,,,,Counts the amount of traffic sent from and to each network address discovered by the probe. Note that while the hlHostControlTable also has objects that control an optional alHostTable, implementation of the alHostTable is not required to fully implement this group.
.1.3.6.1.2.1.16.20.2.5,RMON2-MIB::nlMatrixGroup,,,,,,Counts the amount of traffic sent between each pair of network addresses discovered by the probe. Note that while the hlMatrixControlTable also has objects that control optional alMatrixTables, implementation of the alMatrixTables is not required to fully implement this group.
.1.3.6.1.2.1.16.20.2.6,RMON2-MIB::alHostGroup,,,,,,Counts the amount of traffic, by protocol, sent from and to each network address discovered by the probe. Implementation of this group requires implementation of the Network-Layer Host Group.
.1.3.6.1.2.1.16.20.2.7,RMON2-MIB::alMatrixGroup,,,,,,Counts the amount of traffic, by protocol, sent between each pair of network addresses discovered by the probe. Implementation of this group requires implementation of the Network-Layer Matrix Group.
.1.3.6.1.2.1.16.20.2.8,RMON2-MIB::usrHistoryGroup,,,,,,The usrHistoryGroup provides user-defined collection of historical information from MIB objects on the probe.
.1.3.6.1.2.1.16.20.2.9,RMON2-MIB::probeInformationGroup,,,,,,This group describes various operating parameters of the probe and controls the local time of the probe.
.1.3.6.1.2.1.16.20.2.10,RMON2-MIB::probeConfigurationGroup,,,,,,This group controls the configuration of various operating parameters of the probe. This group is not referenced by any MODULE-COMPLIANCE macro because it is 'grandfathered' from more recent MIB review rules that would require it.
.1.3.6.1.2.1.16.20.2.11,RMON2-MIB::rmon1EnhancementGroup,,,,,,This group adds some enhancements to RMON-1 that help management stations.
.1.3.6.1.2.1.16.20.2.12,RMON2-MIB::rmon1EthernetEnhancementGroup,,,,,,This group adds some enhancements to RMON-1 that help management stations.
.1.3.6.1.2.1.16.20.2.13,RMON2-MIB::rmon1TokenRingEnhancementGroup,,,,,,This group adds some enhancements to RMON-1 that help management stations. This group is not referenced by any MODULE-COMPLIANCE macro because it is 'grandfathered' from more recent MIB review rules that would require it.
.1.3.6.1.2.1.16.20.3,SMON-MIB::smonMIBCompliances,,,,,,
.1.3.6.1.2.1.16.20.3.1,SMON-MIB::smonMIBCompliance,,,,,,Describes the requirements for full conformance with the SMON MIB
.1.3.6.1.2.1.16.20.3.2,SMON-MIB::smonMIBVlanStatsCompliance,,,,,,Describes the requirements for conformance with the SMON MIB with support for VLAN Statistics. Mandatory for a SMON probe in environment where IEEE 802.1Q bridging is implemented.
.1.3.6.1.2.1.16.20.3.3,SMON-MIB::smonMIBPrioStatsCompliance,,,,,,Describes the requirements for conformance with the SMON MIB with support for priority level Statistics. Mandatory for a SMON probe in a environment where IEEE 802.1p priority-switching is implemented.
.1.3.6.1.2.1.16.20.3.4,SMON-MIB::portCopyCompliance,,,,,,Describes the requirements for conformance with the port copy functionality defined by the SMON MIB
.1.3.6.1.2.1.16.20.4,SMON-MIB::smonMIBGroups,,,,,,
.1.3.6.1.2.1.16.20.4.1,SMON-MIB::dataSourceCapsGroup,,,,,,Defines the objects that describe the capabilities of RMON data sources.
.1.3.6.1.2.1.16.20.4.2,SMON-MIB::smonVlanStatsGroup,,,,,,Defines the switch monitoring specific statistics - per VLAN Id on interfaces of 10MB or less.
.1.3.6.1.2.1.16.20.4.3,SMON-MIB::smonPrioStatsGroup,,,,,,Defines the switch monitoring specific statistics - per VLAN Id on interface.
.1.3.6.1.2.1.16.20.4.4,SMON-MIB::smonHcTo100mbGroup,,,,,,Defines the additional high capacity statistics needed to be kept on interfaces with ifSpeed greater than 10MB/sec and less than or equal to 100MB/sec.
.1.3.6.1.2.1.16.20.4.5,SMON-MIB::smonHc100mbPlusGroup,,,,,,Defines the additional high capacity statistics needed to be kept on interfaces with ifSpeed of more than 100MB/sec. These statistics MUST also be kept on smonDataSources of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.20.4.6,SMON-MIB::hcVlanTo100mbGroup,,,,,,Defines the additional high capacity VLAN statistics needed to be kept on interfaces with ifSpeed greater than 10MB/sec and less than or equal to 100MB/sec.
.1.3.6.1.2.1.16.20.4.7,SMON-MIB::hcVlan100mbPlusGroup,,,,,,Defines the additional high capacity VLAN statistics needed to be kept on interfaces with ifSpeed of more than 100MB/sec. These statistics MUST also be kept on smonDataSources of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.20.4.8,SMON-MIB::hcPrioTo100mbGroup,,,,,,Defines the additional high capacity VLAN priority statistics needed to be kept on interfaces with ifSpeed of greater than 10MB/sec and less than or equal to 100MB/sec.
.1.3.6.1.2.1.16.20.4.9,SMON-MIB::hcPrio100mbPlusGroup,,,,,,Defines the additional high capacity VLAN priority statistics needed to be kept on interfaces with ifSpeed of greater than 100MB/sec. These statistics MUST also be kept on smonDataSources of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.20.4.10,SMON-MIB::smonVlanStatsExtGroup,,,,,,Defines the switch monitoring specific statistics for systems capable of counting non-unicast octets for a given dataSource (as described in the dataSourceRmonCaps object).
.1.3.6.1.2.1.16.20.4.11,SMON-MIB::smonInformationGroup,,,,,,An indication of the SMON capabilities supported by this agent.
.1.3.6.1.2.1.16.20.4.12,SMON-MIB::portCopyConfigGroup,,,,,,Defines the control objects for copy port operations.
.1.3.6.1.2.1.16.20.5,HC-RMON-MIB::hcRMON,,,,,,The MIB module for managing remote monitoring device implementations. This MIB module augments the original RMON MIB as specified in RFC 2819 and RFC 1513 and RMON-2 MIB as specified in RFC 2021.
.1.3.6.1.2.1.16.20.6,HC-RMON-MIB::hcRmonMIBCompliances,,,,,,
.1.3.6.1.2.1.16.20.6.1,HC-RMON-MIB::hcMediaIndependentCompliance,,,,,,Describes the requirements for conformance to the High Capacity Media Independent Group.
.1.3.6.1.2.1.16.20.6.2,HC-RMON-MIB::hcRmon1MIBCompliance,,,,,,Describes the requirements for conformance to the High Capacity RMON-1 MIB
.1.3.6.1.2.1.16.20.6.3,HC-RMON-MIB::hcRmon2MIBCompliance,,,,,,Describes the requirements for conformance to the High Capacity RMON-2 MIB
.1.3.6.1.2.1.16.20.6.4,HC-RMON-MIB::hcRmon2MIBApplicationLayerCompliance,,,,,,Describes the requirements for conformance to the High Capacity RMON-2 MIB with Application Layer Enhancements.
.1.3.6.1.2.1.16.20.7,HC-RMON-MIB::hcRmonMIBGroups,,,,,,
.1.3.6.1.2.1.16.20.7.1,HC-RMON-MIB::mediaIndependentGroup,,,,,,Collects utilization statistics for any type of network.
.1.3.6.1.2.1.16.20.7.2,HC-RMON-MIB::etherStatsHighCapacityGroup,,,,,,Collects utilization statistics for ethernet networks.
.1.3.6.1.2.1.16.20.7.3,HC-RMON-MIB::etherHistoryHighCapacityGroup,,,,,,Collects utilization statistics for ethernet networks.
.1.3.6.1.2.1.16.20.7.4,HC-RMON-MIB::hostHighCapacityGroup,,,,,,Collects utilization and error statistics per host.
.1.3.6.1.2.1.16.20.7.5,HC-RMON-MIB::hostTopNHighCapacityGroup,,,,,,Prepares sorted reports of utilization and error statistics per host.
.1.3.6.1.2.1.16.20.7.6,HC-RMON-MIB::matrixHighCapacityGroup,,,,,,Collects utilization statistics per conversation.
.1.3.6.1.2.1.16.20.7.7,HC-RMON-MIB::captureBufferHighCapacityGroup,,,,,,Provides finer granularity time stamps.
.1.3.6.1.2.1.16.20.7.8,HC-RMON-MIB::protocolDistributionHighCapacityGroup,,,,,,Collects the relative amounts of octets and packets for the different protocols detected on a network segment.
.1.3.6.1.2.1.16.20.7.9,HC-RMON-MIB::nlHostHighCapacityGroup,,,,,,Counts the amount of traffic sent from and to each network address discovered by the probe.
.1.3.6.1.2.1.16.20.7.10,HC-RMON-MIB::nlMatrixHighCapacityGroup,,,,,,Counts the amount of traffic sent between each pair of network addresses discovered by the probe.
.1.3.6.1.2.1.16.20.7.11,HC-RMON-MIB::nlMatrixTopNHighCapacityGroup,,,,,,Prepares sorted reports of the amount of traffic sent between each pair of network addresses discovered by the probe.
.1.3.6.1.2.1.16.20.7.12,HC-RMON-MIB::alHostHighCapacityGroup,,,,,,Counts the amount of traffic, by protocol, sent from and to each network address discovered by the probe.
.1.3.6.1.2.1.16.20.7.13,HC-RMON-MIB::alMatrixHighCapacityGroup,,,,,,Counts the amount of traffic, by protocol, sent between each pair of network addresses discovered by the probe.
.1.3.6.1.2.1.16.20.7.14,HC-RMON-MIB::alMatrixTopNHighCapacityGroup,,,,,,Prepares sorted reports of the amount of traffic per protocol sent between each pair of network addresses discovered by the probe.
.1.3.6.1.2.1.16.20.7.15,HC-RMON-MIB::usrHistoryHighCapacityGroup,,,,,,Provides user-defined collection of historical information from MIB objects on the probe with scalability to statistics from high-capacity networks.
.1.3.6.1.2.1.16.20.7.16,HC-RMON-MIB::hcRMONInformationGroup,,,,,,An indication of the high capacity RMON groups supported on at least one interface by this probe.
.1.3.6.1.2.1.16.20.8,RMON-MIB::rmonMibModule,,,,,,Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. This MIB defines objects for managing remote network monitoring devices.
.1.3.6.1.2.1.16.20.9,RMON-MIB::rmonCompliances,,,,,,
.1.3.6.1.2.1.16.20.9.1,RMON-MIB::rmonCompliance,,,,,,The requirements for conformance to the RMON MIB. At least one of the groups in this module must be implemented to conform to the RMON MIB. Implementations of this MIB must also implement the system group of MIB-II [16] and the IF-MIB [17].
.1.3.6.1.2.1.16.20.10,RMON-MIB::rmonGroups,,,,,,
.1.3.6.1.2.1.16.20.10.1,RMON-MIB::rmonEtherStatsGroup,,,,,,The RMON Ethernet Statistics Group.
.1.3.6.1.2.1.16.20.10.2,RMON-MIB::rmonHistoryControlGroup,,,,,,The RMON History Control Group.
.1.3.6.1.2.1.16.20.10.3,RMON-MIB::rmonEthernetHistoryGroup,,,,,,The RMON Ethernet History Group.
.1.3.6.1.2.1.16.20.10.4,RMON-MIB::rmonAlarmGroup,,,,,,The RMON Alarm Group.
.1.3.6.1.2.1.16.20.10.5,RMON-MIB::rmonHostGroup,,,,,,The RMON Host Group.
.1.3.6.1.2.1.16.20.10.6,RMON-MIB::rmonHostTopNGroup,,,,,,The RMON Host Top 'N' Group.
.1.3.6.1.2.1.16.20.10.7,RMON-MIB::rmonMatrixGroup,,,,,,The RMON Matrix Group.
.1.3.6.1.2.1.16.20.10.8,RMON-MIB::rmonFilterGroup,,,,,,The RMON Filter Group.
.1.3.6.1.2.1.16.20.10.9,RMON-MIB::rmonPacketCaptureGroup,,,,,,The RMON Packet Capture Group.
.1.3.6.1.2.1.16.20.10.10,RMON-MIB::rmonEventGroup,,,,,,The RMON Event Group.
.1.3.6.1.2.1.16.20.10.11,RMON-MIB::rmonNotificationGroup,,,,,,The RMON Notification Group.
.1.3.6.1.2.1.16.21,HC-RMON-MIB::mediaIndependentStats,,,,,,
.1.3.6.1.2.1.16.21.1,HC-RMON-MIB::mediaIndependentTable,,not-accessible,,current,,Media independent statistics for promiscuous monitoring of any media. The following table defines media independent statistics that provide information for full and/or half-duplex links as well as high capacity links. For half-duplex links, or full-duplex-capable links operating in half-duplex mode, the mediaIndependentIn* objects shall be used and the mediaIndependentOut* objects shall not increment. For full-duplex links, the mediaIndependentOut* objects shall be present and shall increment. Whenever possible, the probe should count packets moving away from the closest terminating equipment as output packets. Failing that, the probe should count packets moving away from the DTE as output packets.
.1.3.6.1.2.1.16.21.1.1,HC-RMON-MIB::mediaIndependentEntry,,not-accessible,mediaIndependentIndex,current,,Media independent statistics for promiscuous monitoring of any media.
.1.3.6.1.2.1.16.21.1.1.1,HC-RMON-MIB::mediaIndependentIndex,Integer32,not-accessible,,current,,The value of this object uniquely identifies this mediaIndependent entry.
.1.3.6.1.2.1.16.21.1.1.2,HC-RMON-MIB::mediaIndependentDataSource,OBJECT,read-create,,current,,This object identifies the source of the data that this mediaIndependent entry is configured to analyze. This source can be any interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in RFC 1213 and RFC 2233 [16,17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all packets on the local network segment attached to the identified interface. An agent may or may not be able to tell if fundamental changes to the media of the interface have occurred and necessitate a deletion of this entry. For example, a hot-pluggable ethernet card could be pulled out and replaced by a token-ring card. In such a case, if the agent has such knowledge of the change, it is recommended that it delete this entry. This object may not be modified if the associated mediaIndependentStatus object is equal to active(1).
.1.3.6.1.2.1.16.21.1.1.3,HC-RMON-MIB::mediaIndependentDropEvents,Counter32,read-only,,current,,The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
.1.3.6.1.2.1.16.21.1.1.4,HC-RMON-MIB::mediaIndependentDroppedFrames,Counter32,read-only,,current,,The total number of frames which were received by the probe and therefore not accounted for in the mediaIndependentDropEvents, but for which the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.21.1.1.5,HC-RMON-MIB::mediaIndependentInPkts,Counter32,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.6,HC-RMON-MIB::mediaIndependentInOverflowPkts,Counter32,read-only,,current,,The number of times the associated mediaIndependentInPkts counter has overflowed.
.1.3.6.1.2.1.16.21.1.1.7,HC-RMON-MIB::mediaIndependentInHighCapacityPkts,Counter64,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.8,HC-RMON-MIB::mediaIndependentOutPkts,Counter32,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received on a full-duplex link in the direction of the network.
.1.3.6.1.2.1.16.21.1.1.9,HC-RMON-MIB::mediaIndependentOutOverflowPkts,Counter32,read-only,,current,,The number of times the associated mediaIndependentOutPkts counter has overflowed.
.1.3.6.1.2.1.16.21.1.1.10,HC-RMON-MIB::mediaIndependentOutHighCapacityPkts,Counter64,read-only,,current,,The total number of packets (including bad packets, broadcast packets, and multicast packets) received on a full-duplex link in the direction of the network.
.1.3.6.1.2.1.16.21.1.1.11,HC-RMON-MIB::mediaIndependentInOctets,Counter32,read-only,,current,,The total number of octets of data (including those in bad packets) received (excluding framing bits but including FCS octets) on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.12,HC-RMON-MIB::mediaIndependentInOverflowOctets,Counter32,read-only,,current,,The number of times the associated mediaIndependentInOctets counter has overflowed.
.1.3.6.1.2.1.16.21.1.1.13,HC-RMON-MIB::mediaIndependentInHighCapacityOctets,Counter64,read-only,,current,,The total number of octets of data (including those in bad packets) received (excluding framing bits but including FCS octets) on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.14,HC-RMON-MIB::mediaIndependentOutOctets,Counter32,read-only,,current,,The total number of octets of data (including those in bad packets) received on a full-duplex link in the direction of the network (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.21.1.1.15,HC-RMON-MIB::mediaIndependentOutOverflowOctets,Counter32,read-only,,current,,The number of times the associated mediaIndependentOutOctets counter has overflowed.
.1.3.6.1.2.1.16.21.1.1.16,HC-RMON-MIB::mediaIndependentOutHighCapacityOctets,Counter64,read-only,,current,,The total number of octets of data (including those in bad packets) received on a full-duplex link in the direction of the network (excluding framing bits but including FCS octets).
.1.3.6.1.2.1.16.21.1.1.17,HC-RMON-MIB::mediaIndependentInNUCastPkts,Counter32,read-only,,current,,The total number of non-unicast packets (including bad packets) received on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.18,HC-RMON-MIB::mediaIndependentInNUCastOverflowPkts,Counter32,read-only,,current,,The number of times the associated mediaIndependentInNUCastPkts counter has overflowed.
.1.3.6.1.2.1.16.21.1.1.19,HC-RMON-MIB::mediaIndependentInNUCastHighCapacityPkts,Counter64,read-only,,current,,The total number of non-unicast packets (including bad packets) received on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.20,HC-RMON-MIB::mediaIndependentOutNUCastPkts,Counter32,read-only,,current,,The total number of non-unicast packets (including bad packets) received on a full-duplex link in the direction of the network.
.1.3.6.1.2.1.16.21.1.1.21,HC-RMON-MIB::mediaIndependentOutNUCastOverflowPkts,Counter32,read-only,,current,,The number of times the associated mediaIndependentOutNUCastPkts counter has overflowed.
.1.3.6.1.2.1.16.21.1.1.22,HC-RMON-MIB::mediaIndependentOutNUCastHighCapacityPkts,Counter64,read-only,,current,,The total number of packets (including bad packets) received on a full-duplex link in the direction of the network.
.1.3.6.1.2.1.16.21.1.1.23,HC-RMON-MIB::mediaIndependentInErrors,Counter32,read-only,,current,,The total number of bad packets received on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.21.1.1.24,HC-RMON-MIB::mediaIndependentOutErrors,Counter32,read-only,,current,,The total number of bad packets received on a full-duplex link in the direction of the network.
.1.3.6.1.2.1.16.21.1.1.25,HC-RMON-MIB::mediaIndependentInputSpeed,Gauge32,read-only,,current,,The nominal maximum speed in kilobits per second of this half-duplex link or on the inbound connection of this full-duplex link. If the speed is unknown or there is no fixed maximum (e.g. a compressed link), this value shall be zero.
.1.3.6.1.2.1.16.21.1.1.26,HC-RMON-MIB::mediaIndependentOutputSpeed,Gauge32,read-only,,current,,The nominal maximum speed in kilobits per second of this full-duplex link in the direction of the network. If the speed is unknown, the link is half-duplex, or there is no fixed maximum (e.g. a compressed link), this value shall be zero.
.1.3.6.1.2.1.16.21.1.1.27,HC-RMON-MIB::mediaIndependentDuplexMode,INTEGER,read-only,,current,halfduplex(1):fullduplex(2),The current mode of this link. Note that if the link has full-duplex capabilities but is operating in half-duplex mode, this value will be halfduplex(1).
.1.3.6.1.2.1.16.21.1.1.28,HC-RMON-MIB::mediaIndependentDuplexChanges,Counter32,read-only,,current,,The number of times this link has changed from full-duplex mode to half-duplex mode or from half-duplex mode to full-duplex mode.
.1.3.6.1.2.1.16.21.1.1.29,HC-RMON-MIB::mediaIndependentDuplexLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the duplex status of this link last changed.
.1.3.6.1.2.1.16.21.1.1.30,HC-RMON-MIB::mediaIndependentOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.21.1.1.31,HC-RMON-MIB::mediaIndependentStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this media independent statistics entry.
.1.3.6.1.2.1.16.22,SMON-MIB::switchRMON,,,,,,The MIB module for managing remote monitoring device implementations for Switched Networks
.1.3.6.1.2.1.16.22.1,SMON-MIB::smonMIBObjects,,,,,,
.1.3.6.1.2.1.16.22.1.1,SMON-MIB::dataSourceCaps,,,,,,
.1.3.6.1.2.1.16.22.1.1.1,SMON-MIB::dataSourceCapsTable,,not-accessible,,current,,This table describes RMON data sources and port copy capabilities. An NMS MAY use this table to discover the identity and attributes of the data sources on a given agent implementation. Similar to the probeCapabilities object, actual row-creation operations will succeed or fail based on the resources available and parameter values used in each row-creation operation. Upon restart of the RMON agent, the dataSourceTable, ifTable, and perhaps entPhysicalTable are initialized for the available dataSources. For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry the agent MUST create an associated ifEntry with a ifType value of 'propVirtual(53)'. This ifEntry will be used as the actual value in RMON control table dataSource objects. The assigned ifIndex value is copied into the associated dataSourceCapsIfIndex object. It is understood that dataSources representing VLANs may not always be instantiated immediately upon restart, but rather as VLAN usage is detected by the agent. The agent SHOULD attempt to create dataSource and interface entries for all dataSources as soon as possible.
.1.3.6.1.2.1.16.22.1.1.1.1,SMON-MIB::dataSourceCapsEntry,,not-accessible,IMPLIEDdataSourceCapsObject,current,,Entries per data source containing descriptions of data source and port copy capabilities. This table is populated by the SMON agent with one entry for each supported data source.
.1.3.6.1.2.1.16.22.1.1.1.1.1,SMON-MIB::dataSourceCapsObject,OBJECT,not-accessible,,current,,Defines an object that can be a SMON data source or a source or a destination for a port copy operation.
.1.3.6.1.2.1.16.22.1.1.1.1.2,SMON-MIB::dataSourceRmonCaps,BITS,read-only,,current,countErrFrames(0):countAllGoodFrames(1):countAnyRmonTables(2):babyGiantsCountAsGood(3), General attributes of the specified dataSource. Note that these are static attributes, which SHOULD NOT be adjusted because of current resources or configuration. The agent sets this bit for the dataSource if errored frames received on this dataSource can actually be monitored by the agent The agent clears this bit if any errored frames are not visible to the RMON data collector. The agent sets this bit for the dataSource if all good frames received on this dataSource can actually be monitored by the agent. The agent clears this bit if any good frames are not visible for RMON collection, e.g., the dataSource is a non-promiscuous interface or an internal switch interface which may not receive frames which were switched in hardware or dropped by the bridge forwarding function. The agent sets this bit if this dataSource can actually be used in any of the implemented RMON tables, resources notwithstanding. The agent clears this bit if this dataSourceCapsEntry is present simply to identify a dataSource that may only be used as portCopySource and/or a portCopyDest, but not the source of an actual RMON data collection. The agent sets this bit if it can distinguish, for counting purposes, between true giant frames and frames that exceed Ethernet maximum frame size 1518 due to VLAN tagging ('baby giants'). Specifically, this BIT means that frames up to 1522 octets are counted as good. Agents not capable of detecting 'baby giants' will clear this bit and will view all frames less than or equal to 1518 octets as 'good frames' and all frames larger than 1518 octets as 'bad frames' for the purpose of counting in the smonVlanIdStats and smonPrioStats tables. Agents capable of detecting 'baby giants' SHALL consider them as 'good frames' for the purpose of counting in the smonVlanIdStats and smonPrioStats tables.
.1.3.6.1.2.1.16.22.1.1.1.1.3,SMON-MIB::dataSourceCopyCaps,BITS,read-only,,current,copySourcePort(0):copyDestPort(1):copySrcTxTraffic(2):copySrcRxTraffic(3):countDestDropEvents(4):copyErrFrames(5):copyUnalteredFrames(6):copyAllGoodFrames(7),PortCopy function capabilities of the specified dataSource. The agent sets this bit if this dataSource is capable of acting as a source of a portCopy operation. The agent clears this bit otherwise. The agent sets this bit if this dataSource is capable of acting as a destination of a portCopy operation. The agent clears this bit otherwise. If the copySourcePort bit is set: The agent sets this bit if this dataSource is capable of copying frames transmitted out this portCopy source. The agent clears this bit otherwise. This function is needed to support full-duplex ports. Else: this bit SHOULD be cleared. If the copySourcePort bit is set: The agent sets this bit if this dataSource is capable of copying frames received on this portCopy source. The agent clears this bit otherwise. This function is needed to support full-duplex ports. Else: this bit SHOULD be cleared. If the copyDestPort bit is set: The agent sets this bit if it is capable of incrementing portCopyDestDropEvents, when this dataSource is the target of a portCopy operation and a frame destined to this dataSource is dropped (for RMON counting purposes). Else: this BIT SHOULD be cleared. If the copySourcePort bit is set: The agent sets this bit if it is capable of copying all errored frames from this portCopy source-port, for errored frames received on this dataSource. Else: this BIT SHOULD be cleared. If the copySourcePort bit is set: The agent sets the copyUnalteredFrames bit If it is capable of copying all frames from this portCopy source-port without alteration in any way; Else: this bit SHOULD be cleared. If the copySourcePort bit is set: The agent sets this bit for the dataSource if all good frames received on this dataSource are normally capable of being copied by the agent. The agent clears this bit if any good frames are not visible for the RMON portCopy operation, e.g., the dataSource is a non-promiscuous interface or an internal switch interface which may not receive frames which were switched in hardware or dropped by the bridge forwarding function. Else: this bit SHOULD be cleared.
.1.3.6.1.2.1.16.22.1.1.1.1.4,SMON-MIB::dataSourceCapsIfIndex,Integer32,read-only,,current,,This object contains the ifIndex value of the ifEntry associated with this smonDataSource. The agent MUST create 'propVirtual' ifEntries for each dataSourceCapsEntry of type VLAN or entPhysicalEntry.
.1.3.6.1.2.1.16.22.1.2,SMON-MIB::smonStats,,,,,,
.1.3.6.1.2.1.16.22.1.2.1,SMON-MIB::smonVlanStatsControlTable,,not-accessible,,current,,Controls the setup of VLAN statistics tables. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection.
.1.3.6.1.2.1.16.22.1.2.1.1,SMON-MIB::smonVlanStatsControlEntry,,not-accessible,smonVlanStatsControlIndex,current,,A conceptual row in the smonVlanStatsControlTable.
.1.3.6.1.2.1.16.22.1.2.1.1.1,SMON-MIB::smonVlanStatsControlIndex,Integer32,not-accessible,,current,,A unique arbitrary index for this smonVlanStatsControlEntry.
.1.3.6.1.2.1.16.22.1.2.1.1.2,SMON-MIB::smonVlanStatsControlDataSource,OBJECT,read-create,,current,,The source of data for this set of VLAN statistics. This object MAY NOT be modified if the associated smonVlanStatsControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.22.1.2.1.1.3,SMON-MIB::smonVlanStatsControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This object allows to a management station to detect deletion and recreation cycles between polls.
.1.3.6.1.2.1.16.22.1.2.1.1.4,SMON-MIB::smonVlanStatsControlOwner,OCTET,read-create,,current,,Administratively assigned named of the owner of this entry. It usually defines the entity that created this entry and is therefore using the resources assigned to it, though there is no enforcement mechanism, nor assurance that rows created are ever used.
.1.3.6.1.2.1.16.22.1.2.1.1.5,SMON-MIB::smonVlanStatsControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MAY NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the smonVlanIdStatsTable SHALL be deleted.
.1.3.6.1.2.1.16.22.1.2.2,SMON-MIB::smonVlanIdStatsTable,,not-accessible,,current,,Contains the VLAN statistics data. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection. This function applies the same rules for attributing frames to VLAN-based collections. RMON VLAN statistics are collected after the Ingress Rules defined in section 3.13 of the VLAN Specification [20] are applied. It is possible that entries in this table will be garbage-collected, based on agent resources, and VLAN configuration. Agents are encouraged to support all 4094 index values and not garbage collect this table.
.1.3.6.1.2.1.16.22.1.2.2.1,SMON-MIB::smonVlanIdStatsEntry,,not-accessible,smonVlanStatsControlIndex:smonVlanIdStatsId,current,,A conceptual row in smonVlanIdStatsTable.
.1.3.6.1.2.1.16.22.1.2.2.1.1,SMON-MIB::smonVlanIdStatsId,Integer32,not-accessible,,current,,The unique identifier of the VLAN monitored for this specific statistics collection. Tagged packets match the VID for the range between 1 and 4094. An external RMON probe MAY detect VID=0 on an Inter Switch Link, in which case the packet belongs to a VLAN determined by the PVID of the ingress port. The VLAN to which such a packet belongs can be determined only by a RMON probe internal to the switch.
.1.3.6.1.2.1.16.22.1.2.2.1.2,SMON-MIB::smonVlanIdStatsTotalPkts,Counter32,read-only,,current,,The total number of packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.3,SMON-MIB::smonVlanIdStatsTotalOverflowPkts,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsTotalPkts counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.4,SMON-MIB::smonVlanIdStatsTotalHCPkts,Counter64,read-only,,current,,The total number of packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.5,SMON-MIB::smonVlanIdStatsTotalOctets,Counter32,read-only,,current,,The total number of octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.6,SMON-MIB::smonVlanIdStatsTotalOverflowOctets,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsTotalOctets counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.7,SMON-MIB::smonVlanIdStatsTotalHCOctets,Counter64,read-only,,current,,The total number of octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.8,SMON-MIB::smonVlanIdStatsNUcastPkts,Counter32,read-only,,current,,The total number of non-unicast packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.9,SMON-MIB::smonVlanIdStatsNUcastOverflowPkts,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsNUcastPkts counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.10,SMON-MIB::smonVlanIdStatsNUcastHCPkts,Counter64,read-only,,current,,The total number of non-unicast packets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.11,SMON-MIB::smonVlanIdStatsNUcastOctets,Counter32,read-only,,current,,The total number of non-unicast octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.12,SMON-MIB::smonVlanIdStatsNUcastOverflowOctets,Counter32,read-only,,current,,The number of times the associated smonVlanIdStatsNUcastOctets counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.2.1.13,SMON-MIB::smonVlanIdStatsNUcastHCOctets,Counter64,read-only,,current,,The total number of Non-unicast octets counted on this VLAN.
.1.3.6.1.2.1.16.22.1.2.2.1.14,SMON-MIB::smonVlanIdStatsCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This object allows to a management station to detect deletion and recreation cycles between polls.
.1.3.6.1.2.1.16.22.1.2.3,SMON-MIB::smonPrioStatsControlTable,,not-accessible,,current,,Controls the setup of priority statistics tables. The smonPrioStatsControlTable allows configuration of collections based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19],[20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes.
.1.3.6.1.2.1.16.22.1.2.3.1,SMON-MIB::smonPrioStatsControlEntry,,not-accessible,smonPrioStatsControlIndex,current,,A conceptual row in the smonPrioStatsControlTable.
.1.3.6.1.2.1.16.22.1.2.3.1.1,SMON-MIB::smonPrioStatsControlIndex,Integer32,not-accessible,,current,,A unique arbitrary index for this smonPrioStatsControlEntry.
.1.3.6.1.2.1.16.22.1.2.3.1.2,SMON-MIB::smonPrioStatsControlDataSource,OBJECT,read-create,,current,,The source of data for this set of VLAN statistics. This object MAY NOT be modified if the associated smonPrioStatsControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.22.1.2.3.1.3,SMON-MIB::smonPrioStatsControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was created. This object allows to a management station to detect deletion and recreation cycles between polls.
.1.3.6.1.2.1.16.22.1.2.3.1.4,SMON-MIB::smonPrioStatsControlOwner,OCTET,read-create,,current,,Administratively assigned named of the owner of this entry. It usually defines the entity that created this entry and is therefore using the resources assigned to it, though there is no enforcement mechanism, nor assurance that rows created are ever used.
.1.3.6.1.2.1.16.22.1.2.3.1.5,SMON-MIB::smonPrioStatsControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MAY NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the smonPrioStatsTable SHALL be deleted.
.1.3.6.1.2.1.16.22.1.2.4,SMON-MIB::smonPrioStatsTable,,not-accessible,,current,,Contains the priority statistics. The collections are based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19], [20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes. No garbage collection is designed for this table, as there always are at most eight rows per statistical set, and the low memory requirements do not justify the implementation of such a mechanism.
.1.3.6.1.2.1.16.22.1.2.4.1,SMON-MIB::smonPrioStatsEntry,,not-accessible,smonPrioStatsControlIndex:smonPrioStatsId,current,,A conceptual row in smonPrioStatsTable.
.1.3.6.1.2.1.16.22.1.2.4.1.1,SMON-MIB::smonPrioStatsId,Integer32,not-accessible,,current,,The unique identifier of the priority level monitored for this specific statistics collection.
.1.3.6.1.2.1.16.22.1.2.4.1.2,SMON-MIB::smonPrioStatsPkts,Counter32,read-only,,current,,The total number of packets counted on this priority level.
.1.3.6.1.2.1.16.22.1.2.4.1.3,SMON-MIB::smonPrioStatsOverflowPkts,Counter32,read-only,,current,,The number of times the associated smonPrioStatsPkts counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.4.1.4,SMON-MIB::smonPrioStatsHCPkts,Counter64,read-only,,current,,The total number of packets counted on this priority level.
.1.3.6.1.2.1.16.22.1.2.4.1.5,SMON-MIB::smonPrioStatsOctets,Counter32,read-only,,current,,The total number of octets counted on this priority level.
.1.3.6.1.2.1.16.22.1.2.4.1.6,SMON-MIB::smonPrioStatsOverflowOctets,Counter32,read-only,,current,,The number of times the associated smonPrioStatsOctets counter has overflowed.
.1.3.6.1.2.1.16.22.1.2.4.1.7,SMON-MIB::smonPrioStatsHCOctets,Counter64,read-only,,current,,The total number of octets counted on this priority level.
.1.3.6.1.2.1.16.22.1.3,SMON-MIB::portCopyConfig,,,,,,
.1.3.6.1.2.1.16.22.1.3.1,SMON-MIB::portCopyTable,,not-accessible,,current,, Port Copy provides the ability to copy all frames from a specified source to specified destination within a switch. Source and destinations MUST be ifEntries, as defined by [22]. One to one, one to many, many to one and many to many source to destination relationships may be configured. Applicable counters on the destination will increment for all packets transiting the port, be it by normal bridging/switching or due to packet copy. Note that this table manages no RMON data collection by itself, and an agent may possibly implement no RMON objects except objects related to the port copy operation defined by the portCopyCompliance conformance macro. That allows for a switch with no other embedded RMON capability to perform port copy operations to a destination port at which a different external RMON probe is connected. One to one, many to one and one to many source to destination relationships may be configured. Each row that exists in this table defines such a relationship. By disabling a row in this table the port copy relationship no longer exists. The number of entries and the types of port copies (1-1, many-1, 1-many) are implementation specific and could possibly be dynamic due to changing resource availability. In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to 'up(1)'. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to 'notReady(3)'. The capability of an interface to be source or destination of a port copy operation is described by the 'copySourcePort(0)' and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits SHOULD be appropriately set by the agent, in order to allow for a portCopyEntry to be created. Applicable counters on the destination will increment for all packets transmitted, be it by normal bridging/switching or due to packet copy.
.1.3.6.1.2.1.16.22.1.3.1.1,SMON-MIB::portCopyEntry,,not-accessible,portCopySource:portCopyDest,current,,Describes a particular port copy entry.
.1.3.6.1.2.1.16.22.1.3.1.1.1,SMON-MIB::portCopySource,Integer32,not-accessible,,current,,The ifIndex of the source which will have all packets redirected to the destination as defined by portCopyDest.
.1.3.6.1.2.1.16.22.1.3.1.1.2,SMON-MIB::portCopyDest,Integer32,not-accessible,,current,,Defines the ifIndex destination for the copy operation.
.1.3.6.1.2.1.16.22.1.3.1.1.3,SMON-MIB::portCopyDestDropEvents,Counter32,read-only,,current,,The total number of events in which port copy packets were dropped by the switch at the destination port due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. A single dropped event counter is maintained for each portCopyDest. Thus all instances associated with a given portCopyDest will have the same portCopyDestDropEvents value.
.1.3.6.1.2.1.16.22.1.3.1.1.4,SMON-MIB::portCopyDirection,INTEGER,read-create,,current,copyRxOnly(1):copyTxOnly(2):copyBoth(3),This object affects the way traffic is copied from a switch source port, for the indicated port copy operation. If this object has the value 'copyRxOnly(1)', then only traffic received on the indicated source port will be copied to the indicated destination port. If this object has the value 'copyTxOnly(2)', then only traffic transmitted out the indicated source port will be copied to the indicated destination port. If this object has the value 'copyBoth(3)', then all traffic received or transmitted on the indicated source port will be copied to the indicated destination port. The creation and deletion of instances of this object is controlled by the portCopyRowStatus object. Note that there is no guarantee that changes in the value of this object performed while the associated portCopyRowStatus object is equal to active will not cause traffic discontinuities in the packet stream.
.1.3.6.1.2.1.16.22.1.3.1.1.5,SMON-MIB::portCopyStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Defines the status of the port copy entry. In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to 'up(1)'. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to 'notReady(3)'. The capability of an interface to be source or destination of a port copy operation is described by the 'copySourcePort(0)' and 'copyDestPort(1)' bits in dataSourceCopyCaps. Those bits SHOULD be appropriately set by the agent, in order to allow for a portCopyEntry to be created.
.1.3.6.1.2.1.16.22.1.4,SMON-MIB::smonRegistrationPoints,,,,,,
.1.3.6.1.2.1.16.22.1.4.1,SMON-MIB::smonVlanDataSource,,,,,,
.1.3.6.1.2.1.16.23,APM-MIB::apm,,,,,,The MIB module for measuring application performance as experienced by end-users. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3729; see the RFC itself for full legal notices.
.1.3.6.1.2.1.16.23.0,APM-MIB::apmNotifications,,,,,,
.1.3.6.1.2.1.16.23.0.1,APM-MIB::apmTransactionResponsivenessAlarm,,,,,,Notification sent when a transaction exceeds a threshold defined in the apmException table. The index of the included apmExceptionResponsivenessThreshold object identifies the apmExceptionEntry that specified the threshold. The apmTransactionResponsiveness variable identifies the actual transaction and its responsiveness. Agent implementors are urged to include additional data objects in the alarm that may explain the reason for the alarm. It is helpful to include such data in the alarm because it describes the situation at the time the alarm was generated, where polls after the fact may not provide meaningful information. Examples of such information are CPU load, memory utilization, network utilization, and transaction statistics.
.1.3.6.1.2.1.16.23.0.2,APM-MIB::apmTransactionUnsuccessfulAlarm,,,,,,Notification sent when a transaction is unsuccessful. The index of the included apmExceptionResponsivenessThreshold object identifies both the type of the transaction that caused this notification as well as the apmExceptionEntry that specified the threshold. Agent implementors are urged to include additional data objects in the alarm that may explain the reason for the alarm. It is helpful to include such data in the alarm because it describes the situation at the time the alarm was generated, where polls after the fact may not provide meaningful information. Examples of such information are CPU load, memory utilization, network utilization, and transaction statistics.
.1.3.6.1.2.1.16.23.1,APM-MIB::apmMibObjects,,,,,,
.1.3.6.1.2.1.16.23.1.1,APM-MIB::apmAppDirTable,,not-accessible,,current,,The APM MIB directory of applications and application verbs. The agent will populate this table with all applications/verbs of any responsivenessType it has the capability to monitor. Since the agent populates this table with every entry it has the capability to monitor, the entries in this table are read-write, allowing the management station to modify parameters in this table but not to add new entries or delete entries (however, entries may be disabled). If new entries are added to the apmHttpFilterTable or the apmUserDefinedAppTable, the agent will add the corresponding entries to this table. It is an implementation-dependent matter as to how the agent sets these default parameters. For example, it may leave certain entries in this table 'off(0)' if the agent developer believes that combination will be infrequently used, allowing a manager that needs that capability to set it to 'on(1)'. Some applications are registered in the RMON2 protocol directory and some are registered in other tables in this MIB Module. Regardless of where an application is originally registered, it is assigned an AppLocalIndex value that is the primary index for this table. The contents of this table affect all reports and exceptions generated by this agent. Accordingly, modification of this table should be performed by a manager acting in the role of administrator. In particular, management software should not require or enforce particular configuration of this table - it should reflect the preferences of the site administrator, not the software author. As a practical matter, this requires management software to allow the administrator to configure the values it will use so that it can be adapted to the site policy.
.1.3.6.1.2.1.16.23.1.1.1,APM-MIB::apmAppDirEntry,,not-accessible,apmAppDirAppLocalIndex:apmAppDirResponsivenessType,current,,The APM MIB directory of applications and application verbs. An entry will exist in this table for all applications for which application performance measurement is supported.
.1.3.6.1.2.1.16.23.1.1.1.1,APM-MIB::apmAppDirAppLocalIndex,Unsigned32,not-accessible,,current,,The AppLocalIndex assigned for this application Directory entry.
.1.3.6.1.2.1.16.23.1.1.1.2,APM-MIB::apmAppDirResponsivenessType,INTEGER,not-accessible,,current,transactionOriented(1):throughputOriented(2):streamingOriented(3),This object describes and configures the agent's support for application performance measurement for this application. There are 3 types of measurements for different types of applications: Transaction-Oriented applications have a fairly constant workload to perform for all transactions. The responsiveness metric for transaction-oriented applications is application response time (from first request to final delivery of service) and is measured in milliseconds. This is commonly referred to as end-user response time. Throughput-Oriented applications have widely varying workloads based on the nature of the client request. In particular, throughput-oriented applications vary widely in the amount of data that must be transported to satisfy the request. The responsiveness metric for throughput-oriented applications is kilobits per second. Streaming-Oriented applications deliver data at a constant metered rate of speed regardless of the responsiveness of the networking and computing infrastructure. This constant rate of speed is generally specified to be below (sometimes well below) the nominal capability of the infrastructure. However, when the infrastructures cannot deliver data at this speed, interruption of service or degradation of service can result. The responsiveness metric for streaming-oriented applications is the ratio of time that the service is degraded or interrupted to the total service time. This metric is measured in parts per million. Note that for some applications, measuring more than one responsiveness type may be interesting. For agents that wish to support more than one measurement for a application, they will populate this table with multiple entries for that application, one for each type.
.1.3.6.1.2.1.16.23.1.1.1.3,APM-MIB::apmAppDirConfig,INTEGER,read-write,,current,off(1):on(2),This object describes and configures support for application performance measurement for this application. If the value of this object is on(2), the agent supports measurement of application performance metrics for this application and is configured to measure such metrics for all APM MIB functions and all interfaces. If the value of this object is off(1), the agent supports measurement of application performance for this application but is configured to not measure these metrics for any APM MIB functions or interfaces. Whenever this value changes from on(2) to off(1), the agent shall delete all related entries in all tables in this MIB Module. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.1.1.4,APM-MIB::apmAppDirResponsivenessBoundary1,Unsigned32,read-write,,current,,The boundary value between bucket1 and bucket 2. If this value is modified, all entries in the apmReportTable must be deleted by the agent. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.1.1.5,APM-MIB::apmAppDirResponsivenessBoundary2,Unsigned32,read-write,,current,,The boundary value between bucket2 and bucket 3. If this value is modified, all entries in the apmReportTable must be deleted by the agent. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.1.1.6,APM-MIB::apmAppDirResponsivenessBoundary3,Unsigned32,read-write,,current,,The boundary value between bucket3 and bucket 4. If this value is modified, all entries in the apmReportTable must be deleted by the agent. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.1.1.7,APM-MIB::apmAppDirResponsivenessBoundary4,Unsigned32,read-write,,current,,The boundary value between bucket4 and bucket 5. If this value is modified, all entries in the apmReportTable must be deleted by the agent. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.1.1.8,APM-MIB::apmAppDirResponsivenessBoundary5,Unsigned32,read-write,,current,,The boundary value between bucket5 and bucket 6. If this value is modified, all entries in the apmReportTable must be deleted by the agent. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.1.1.9,APM-MIB::apmAppDirResponsivenessBoundary6,Unsigned32,read-write,,current,,The boundary value between bucket6 and bucket 7. If this value is modified, all entries in the apmReportTable must be deleted by the agent. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.2,APM-MIB::apmBucketBoundaryLastChange,TimeTicks,read-only,,current,,The value of sysUpTime the last time that any bucket boundary in any appDirEntry was changed. This object can help to determine if two managers are both trying to enforce different configurations of this table.
.1.3.6.1.2.1.16.23.1.3,APM-MIB::apmAppDirID,OBJECT,read-write,,current,,This object allows managers to avoid downloading application directory information when the directory is set to a known (usually fixed) configuration. If the value of this object isn't 0.0, it signifies that the entire contents of the apmAppDirTable, apmHttpFilterTable, apmUserDefinedAppTable and protocolDirTable are equal to a known state identified by the value of this object. If a manager recognizes this value as identifying a directory configuration it has a local copy of, it may use this local copy rather than downloading these tables. Note that it may have downloaded this local copy (and the ID) from another agent and used this copy for all other agents that advertised the same ID. If an agent recognizes that the entire contents of the apmAppDirTable, apmHttpFilterTable, apmUserDefinedAppTable and protocolDirTable are equal to a known state to which an ID has been assigned, it should set this object to that ID. In many cases when this feature is used, the application directory information will be in read-only memory and thus the tables may not be modified via SNMP requests. In the event that the tables are writable and a modification is made, the agent is responsible for setting this object to 0.0 if it cannot determine that the state is equal to a known state. An agent is not obligated to recognize and advertise all such registered states as it may not have knowledge of all states. Thus, a manager may encounter agents whose DirectoryID value is 0.0 even though the contents of the directory were equal to a registered state. Note that the contents of those tables includes the protocolDirLocalIndex and appLocalIndex values. In other words, these values can't be assigned randomly on each agent, but must be equal to values that are part of the known state. While it is possible for a manager to download application directory details using SNMP and to set the appropriate directoryID, the manager would need to have some scheme to ensure consistent values of LocalIndex variables from agent to agent. Such schemes are outside the scope of this specification. Application directory registrations are unique within an administrative domain. Typically these registrations will be made by an agent software developer who will set the application directory tables to a read-only state and assign a DirectoryID to that state. Thus, all agents running this software would share the same DirectoryID. As the application directory might change from one software release to the next, the developer may register different DirectoryID's for each software release. A customer could also create a site-wide application directory configuration and assign a DirectoryID to that configuration as long as consistent values of LocalIndex variables can be ensured. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.4,APM-MIB::apmHttpFilterTable,,not-accessible,,current,,A table that creates virtual applications which measure the performance of certain web pages or sets of web pages. When an entry is added to this table, the agent will automatically create one or more entries in the apmAppDirTable (one for each responsivenessType it is capable of measuring). Note that when entries exist in this table some HTTP transactions will be summarized twice: in applications represented here as well as the HTTP application. If entries in this table overlap, these transactions may be summarized additional times. The contents of this table affect all reports and exceptions generated by this agent. Accordingly, modification of this table should be performed by a manager acting in the role of administrator. In particular, management software should not require or enforce particular configuration of this table - it should reflect the preferences of the site administrator, not the software author.
.1.3.6.1.2.1.16.23.1.4.1,APM-MIB::apmHttpFilterEntry,,not-accessible,apmHttpFilterIndex,current,,A virtual application which measure the performance of certain web pages or sets of web pages.
.1.3.6.1.2.1.16.23.1.4.1.1,APM-MIB::apmHttpFilterIndex,Unsigned32,not-accessible,,current,,An index that uniquely identifies an entry in the apmHttpFilterTable.
.1.3.6.1.2.1.16.23.1.4.1.2,APM-MIB::apmHttpFilterAppLocalIndex,Unsigned32,read-only,,current,,The AppLocalIndex that represents HTTP transactions that match this entry. This object is read-only. A value is created by the agent from an unused AppLocalIndex value when this apmHttpFilterEntry is created.
.1.3.6.1.2.1.16.23.1.4.1.3,APM-MIB::apmHttpFilterServerProtocol,Unsigned32,read-create,,current,,The protocolDirLocalIndex value of the network level protocol of the apmHttpFilterServerAddress.
.1.3.6.1.2.1.16.23.1.4.1.4,APM-MIB::apmHttpFilterServerAddress,OCTET,read-create,,current,,This entry will only represent transactions coming from the network address specified in this object. This is represented as an octet string with specific semantics and length as identified by the associated apmHttpFilterServerProtocol object. If this object is the zero-length string, then this entry will match one of the addresses represented by the 'host' component of the associated apmHttpFilterURLPath object, where the format if a URL [9] is http://<host>:<port>/<path>?<searchpart>.
.1.3.6.1.2.1.16.23.1.4.1.5,APM-MIB::apmHttpFilterURLPath,OCTET,read-create,,current,,This entry will only represent HTTP transactions where the URL path component in the request matches this value. This value represents the requested path regardless of any substitution that the server might perform. Prior to the matching, the URL is stripped of any server address or DNS name and consists solely of the path name on that server. If the length of this object is zero, then this entry will match if the associated apmHttpFilterServerAddress match. If the length of that object is also zero, then this entry will match nothing. The value of the associated apmHttpFilterMatchType dictates the type of matching that will be attempted.
.1.3.6.1.2.1.16.23.1.4.1.6,APM-MIB::apmHttpFilterMatchType,INTEGER,read-create,,current,exact(1):stripTrailingSlash(2):prefix(3),The matching algorithm used to compare the URL pathname. If the value is exact(1), then the pathname component will be compared with the associated apmHttpFilterURLPath and will only be associated with this entry if it matches exactly. If the value is stripTrailingSlash(2), then the pathname component will be compared with the associated apmHttpFilterURLPath and will only be associated with this entry if it matches exactly or if the pathname ends with a '/' symbol and matches apmHttpFilterURLPath if the '/' symbol is removed from the pathname. This option exists for those paths where an optional trailing slash is possible but for which a prefix match would be too broad. If the value is prefix(3), then the pathname component will be compared with the associated apmHttpFilterURLPath and will only be associated with this entry if the beginning of the pathname matches every octet of this value. Octets that extend beyond the length of this value are ignored.
.1.3.6.1.2.1.16.23.1.4.1.7,APM-MIB::apmHttpFilterOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.23.1.4.1.8,APM-MIB::apmHttpFilterStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this apmHttpFilterEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.23.1.4.1.9,APM-MIB::apmHttpFilterRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this apmHttpFilterEntry. No objects in this row may be modified while the row's status is 'active'.
.1.3.6.1.2.1.16.23.1.5,APM-MIB::apmHttpIgnoreUnregisteredURLs,INTEGER,read-write,,current,true(1):false(2),When true, APM measurements of HTTP transactions will only measure transactions relating to URLs that match a filter in the apmHttpFilterTable. Thus, measurements for the HTTP application will present aggregated statistics for URL-matching HTTP transactions and measurements for the HTTP GET application verb will present aggregated statistics for URL-matching HTTP GET transactions. This will be used in environments that wish to monitor only targeted URLs and to ignore large volumes of internet web browsing traffic. This object affects all APM reports and exceptions generated by this agent. Accordingly, modification of this object should be performed by a manager acting in the role of administrator. In particular, management software should not require or enforce particular configuration of this object - it should reflect the preferences of the site administrator, not the software author. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.6,APM-MIB::apmHttp4xxIsFailure,INTEGER,read-write,,current,true(1):false(2),When true, this agent will recognize HTTP errors in the range of 400 through 499 and will treat them as unavailable transactions. When false or when this object isn't supported, they will be treated as successful transactions. This object allows such error pages to be tracked at the possible expense of having user typos treated as poor service on the part of the web server. This object affects all reports and exceptions generated by this agent. Accordingly, modification of this object should be performed by a manager acting in the role of administrator. In particular, management software should not require or enforce particular configuration of this object - it should reflect the preferences of the site administrator, not the software author. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.7,APM-MIB::apmUserDefinedAppTable,,not-accessible,,current,,A table that advertises user-defined applications that the agent is measuring. The agent will automatically create one or more entries in the apmAppDirTable (one for each responsivenessType it is capable of measuring) for each entry in this table. Note that when entries exist in this table some transactions can be summarized more than once if there is overlap between applications defined here and applications defined in the protocol directory or in the httpFilter table.
.1.3.6.1.2.1.16.23.1.7.1,APM-MIB::apmUserDefinedAppEntry,,not-accessible,apmAppDirAppLocalIndex,current,,A user-defined application that the agent is measuring, along with its AppLocalIndex assignment. The apmAppDirAppLocalIndex value in the index identifies the agent-assigned AppLocalIndex value for this user-defined application.
.1.3.6.1.2.1.16.23.1.7.1.1,APM-MIB::apmUserDefinedAppParentIndex,Unsigned32,read-only,,current,,The protocolDirLocalIndex value of the highest-layer protocol defined in the protocolDirTable that this application is a child of.
.1.3.6.1.2.1.16.23.1.7.1.2,APM-MIB::apmUserDefinedAppApplication,OCTET,read-only,,current,,A human readable descriptive tag for this application.
.1.3.6.1.2.1.16.23.1.8,APM-MIB::apmNameTable,,not-accessible,,current,,A client machine may have multiple addresses during a period of monitoring. The apmNameTable assigns a long-lived identifier to a client and records what addresses were assigned to that client for periods of time. Various implementation techniques exist for tracking this mapping but if an agent is unable to track client address mappings, it may map client identifiers to client addresses rather than to distinct client machines. A particular apmNameClientID should be a constant attribute of a particular client. When available, the agent may also record the machine name and/or user name which may be valuable for displaying to humans. The apmNameMachineName and apmNameUserName are relatively constant, changing only if these attributes actually change on the client. The agent will store a historical log of these entries, aging out old entries as the log becomes too large. Since this table contains information vital to the interpretation of other tables (e.g., the apmReportTable), the agent should ensure that the log doesn't age out entries that would be referenced by data in those tables. Note that an entry for a clientID is active from its StartTime until the StartTime of another entry (for the same clientID) that supersedes it, or 'now' if none supersede it. Therefore, if a clientID only has a single entry, it is by definition very new and should never be aged out. No entry for a clientID should be aged out unless it has been updated by a new entry for the client (i.e., with an updated address) and only if the new entry is 'old' enough. To determine how old is old enough, compute the maximum value of Interval * (NumReports + 1) of all entries in the apmReportControlTable (the '+ 1' is to allow a reasonable period of time for the report to be downloaded). Then take the larger of this value and the age in seconds of the oldest entry in the current transaction table. If an entry for a clientID is superseded by another entry whose StartTime is more than this many seconds ago, then the older entry may be deleted.
.1.3.6.1.2.1.16.23.1.8.1,APM-MIB::apmNameEntry,,not-accessible,apmNameClientID:protocolDirLocalIndex:apmNameClientAddress:apmNameMappingStartTime,current,,An entry in the APM name table. An entry exists for each period of time that a client has been associated with a particular address. The protocolDirLocalIndex value in the index identifies the network layer protocol for the ClientAddress for this entry. Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.23.1.8.1.1,APM-MIB::apmNameClientID,Unsigned32,not-accessible,,current,,A unique ID assigned to the machine represented by this mapping. This ID is assigned by the agent using an implementation-specific algorithm.
.1.3.6.1.2.1.16.23.1.8.1.2,APM-MIB::apmNameClientAddress,OCTET,not-accessible,,current,,The network client address for this client when this mapping was active. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. This object may not be the zero length string. Since this object is an index variable, it is encoded in the index according to the index encoding rules. For example, if the protocolDirLocalIndex component of the index indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order. Care should be taken to avoid values of this object that, in conjunction with the other index variables, would result in an index longer than SNMP's maximum of 128 subidentifiers.
.1.3.6.1.2.1.16.23.1.8.1.3,APM-MIB::apmNameMappingStartTime,OCTET,not-accessible,,current,,The time that the agent first discovered this mapping as active.
.1.3.6.1.2.1.16.23.1.8.1.4,APM-MIB::apmNameMachineName,OCTET,read-only,,current,,The human readable name of the client machine. If the client has no machine name or the agent is unable to learn the machine name, this object will be a zero-length string.
.1.3.6.1.2.1.16.23.1.8.1.5,APM-MIB::apmNameUserName,OCTET,read-only,,current,,The human readable name of a human user using the client machine. If more than one user name are available simultaneously, it is an implementation-dependent matter as to which is used here. However, if the user name changes, this object should change to reflect that change. Non-human user names like 'root' or 'administrator' aren't intended as values for this object. If the client has no recorded user name or the agent is unable to learn a user name, this object will be a zero-length string.
.1.3.6.1.2.1.16.23.1.9,APM-MIB::apmReportControlTable,,not-accessible,,current,,Parameters that control the creation of a set of reports that aggregate application performance.
.1.3.6.1.2.1.16.23.1.9.1,APM-MIB::apmReportControlEntry,,not-accessible,apmReportControlIndex,current,,A conceptual row in the apmReportControlTable. An example of the indexing of this table is apmReportControlInterval.3
.1.3.6.1.2.1.16.23.1.9.1.1,APM-MIB::apmReportControlIndex,Unsigned32,not-accessible,,current,,An index that uniquely identifies an entry in the apmReportControlTable. Each such entry defines a unique report whose results are placed in the apmReportTable on behalf of this apmReportControlEntry.
.1.3.6.1.2.1.16.23.1.9.1.2,APM-MIB::apmReportControlDataSource,OBJECT,read-create,,current,,The source of the data for APM Reports generated on behalf of this apmReportControlEntry. If the measurement is being performed by a probe, this should be set to interface or port where data was received for analysis. If the measurement isn't being performed by a probe, this should be set to the primary interface over which the measurement is being performed. If the measurement isn't being performed by a probe and there is no primary interface or this information isn't known, this object should be set to 0.0. This object may not be modified if the associated apmReportControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.23.1.9.1.3,APM-MIB::apmReportControlAggregationType,INTEGER,read-create,,current,flows(1):clients(2):servers(3):applications(4),The type of aggregation being performed for this set of reports. The metrics for a single transaction are the responsiveness of the transaction and whether the transaction succeeded (a boolean). When such metrics are aggregated in this MIB Module, these metrics are replaced by averages and distributions of responsiveness and availability. The metrics describing aggregates are constant no matter which type of aggregation is being performed. These metrics may be found in the apmReportTable. The flows(1) aggregation is the simplest. All transactions that share common application/server/client 3-tuples are aggregated together, resulting in a set of metrics for all such unique 3-tuples. The clients(2) aggregation results in somewhat more aggregation (i.e., fewer resulting records). All transactions that share common application/client tuples are aggregated together, resulting in a set of metrics for all such unique tuples. The servers(3) aggregation usually results in still more aggregation (i.e., fewer resulting records). All transactions that share common application/server tuples are aggregated together, resulting in a set of metrics for all such unique tuples. The applications(4) aggregation results in the most aggregation (i.e., the fewest resulting records). All transactions that share a common application are aggregated together, resulting in a set of metrics for all such unique applications. Note that it is not meaningful to aggregate applications, as different applications have widely varying characteristics. As a result, this set of aggregations is complete. This object may not be modified if the associated apmReportControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.23.1.9.1.4,APM-MIB::apmReportControlInterval,Unsigned32,read-create,,current,,The interval in seconds over which data is accumulated before being aggregated into a report in the apmReportTable. All reports with the same apmReportControlIndex will be based on the same interval. This object must be greater than zero. Many users desire that these reports be synchronized to within seconds of the beginning of the hour because the results may be correlated more meaningfully to business behavior and so that data from multiple agents is aggregated over the same time periods. Thus management software may take extra effort to synchronize reports to the beginning of the hour and to one another. However, the agent must not allow reports to 'drift' over time as they will quickly become unsynchronized. In particular, if there is any fixed processing delay between reports, the reports should deduct this time from the interval so that reports don't drift. This object may not be modified if the associated apmReportControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.23.1.9.1.5,APM-MIB::apmReportControlRequestedSize,Unsigned32,read-create,,current,,The number of entries requested to be allocated for each report generated on behalf of this entry.
.1.3.6.1.2.1.16.23.1.9.1.6,APM-MIB::apmReportControlGrantedSize,Unsigned32,read-only,,current,,The number of entries per report the agent has allocated based on the requested amount in apmReportControlRequestedSize. Since multiple reports are saved, the total number of entries allocated will be this number multiplied by the value of apmReportControlGrantedReports, or 1 if that object doesn't exist. When the associated apmReportControlRequestedSize object is created or modified, the agent should set this object as closely to the requested value as is possible for the particular implementation and available resources. When considering resources available, the agent must consider its ability to allocate this many entries for all reports. Note that while the actual number of entries stored in the reports may fluctuate due to changing conditions, the agent must continue to have storage available to satisfy the full report size for all reports when necessary. Further, the agent must not lower this value except as a result of a set to the associated apmReportControlRequestedSize object.
.1.3.6.1.2.1.16.23.1.9.1.7,APM-MIB::apmReportControlRequestedReports,Unsigned32,read-create,,current,,The number of saved reports requested to be allocated on behalf of this entry.
.1.3.6.1.2.1.16.23.1.9.1.8,APM-MIB::apmReportControlGrantedReports,Unsigned32,read-only,,current,,The number of saved reports the agent has allocated based on the requested amount in apmReportControlRequestedReports. Since each report can have many entries, the total number of entries allocated will be this number multiplied by the value of apmReportControlGrantedSize, or 1 if that object doesn't exist. When the associated apmReportControlRequestedReports object is created or modified, the agent should set this object as closely to the requested value as is possible for the particular implementation and available resources. When considering resources available, the agent must consider its ability to allocate this many reports each with the number of entries represented by apmReportControlGrantedSize, or 1 if that object doesn't exist. Note that while the storage required for each report may fluctuate due to changing conditions, the agent must continue to have storage available to satisfy the full report size for all reports when necessary. Further, the agent must not lower this value except as a result of a set to the associated apmReportControlRequestedSize object.
.1.3.6.1.2.1.16.23.1.9.1.9,APM-MIB::apmReportControlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when the system began processing the report in progress. Note that the report in progress is not available. This object may be used by the management station to figure out the start time for all previous reports saved for this apmReportControlEntry, as reports are started at fixed intervals.
.1.3.6.1.2.1.16.23.1.9.1.10,APM-MIB::apmReportControlReportNumber,Unsigned32,read-only,,current,,The number of the report in progress. When an apmReportControlEntry is activated, the first report will be numbered one.
.1.3.6.1.2.1.16.23.1.9.1.11,APM-MIB::apmReportControlDeniedInserts,Counter32,read-only,,current,,The number of failed attempts to add an entry to reports for this apmReportControlEntry because the number of entries would have exceeded apmReportControlGrantedSize. This number is valuable in determining if enough entries have been allocated for reports in light of fluctuating network usage. Note that since an entry that is denied will often be attempted again, this number will not predict the exact number of additional entries needed, but can be used to understand the relative magnitude of the problem. Also note that there is no ordering specified for the entries in the report, thus there are no rules for which entries will be omitted when not enough entries are available. As a consequence, the agent is not required to delete 'least valuable' entries first.
.1.3.6.1.2.1.16.23.1.9.1.12,APM-MIB::apmReportControlDroppedFrames,Counter32,read-only,,current,,The total number of frames which were received by the agent and therefore not accounted for in the *StatsDropEvents, but for which the agent chose not to count for this entry for whatever reason. Most often, this event occurs when the agent is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. This counter is only relevant if this apm report is based on a data source whose collection methodology is based on analyzing network traffic. Note that if the apmReportTables are inactive because no applications are enabled in the application directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.23.1.9.1.13,APM-MIB::apmReportControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.23.1.9.1.14,APM-MIB::apmReportControlStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this apmReportControlEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.23.1.9.1.15,APM-MIB::apmReportControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this apmReportControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. The only objects in the entry that may be modified while the entry is in the active state are apmReportControlRequestedSize and apmReportControlRequestedReports. If this object is not equal to active(1), all associated entries in the apmReportTable shall be deleted by the agent.
.1.3.6.1.2.1.16.23.1.10,APM-MIB::apmReportTable,,not-accessible,,current,,The data resulting from aggregated APM reports. Consult the definition of apmReportControlAggregationType for the definition of the various types of aggregations.
.1.3.6.1.2.1.16.23.1.10.1,APM-MIB::apmReportEntry,,not-accessible,apmReportControlIndex:apmReportIndex:apmAppDirAppLocalIndex:apmAppDirResponsivenessType:protocolDirLocalIndex:apmReportServerAddress:apmNameClientID,current,,A conceptual row in the apmReportTable. The apmReportControlIndex value in the index identifies the apmReportControlEntry on whose behalf this entry was created. The apmReportIndex value in the index identifies which report (in the series of reports) this entry is a part of. The apmAppDirAppLocalIndex value in the index identifies the common application of the transactions aggregated in this entry. The apmAppDirResponsivenessType value in the index identifies the type of responsiveness metric reported by this entry and uniquely identifies this entry when more than one responsiveness metric is measured for a flow. Entries will only exist in this table for those combinations of AppLocalIndex and ResponsivenessType that are configured 'on(1)'. The protocolDirLocalIndex value in the index identifies the network layer protocol of the apmReportServerAddress. When the associated apmReportControlAggregationType value is equal to applications(4) or clients(2), this protocolDirLocalIndex value will equal 0. The apmReportServerAddress value in the index identifies the network layer address of the server in transactions aggregated in this entry. The apmNameClientID value in the index identifies the client in transactions aggregated in this entry. If the associated apmReportControlAggregationType is equal to applications(4) or servers(3), then this protocolDirLocalIndex value will equal 0. An example of the indexing of this entry is apmReportTransactionCount.3.15.3.1.8.4.192.168.1.2.3232235788 Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.23.1.10.1.1,APM-MIB::apmReportIndex,Unsigned32,not-accessible,,current,,The value of apmReportControlReportNumber for the report to which this entry belongs.
.1.3.6.1.2.1.16.23.1.10.1.2,APM-MIB::apmReportServerAddress,OCTET,not-accessible,,current,,The network server address for this apmReportEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. Since this object is an index variable, it is encoded in the index according to the index encoding rules. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order. Care should be taken to avoid values of this object that, in conjunction with the other index variables, would result in an index longer than SNMP's maximum of 128 subidentifiers. If the associated apmReportControlAggregationType is equal to applications(4) or clients(2), then this object will be a null string and will be encoded simply as a length octet of 0.
.1.3.6.1.2.1.16.23.1.10.1.3,APM-MIB::apmReportTransactionCount,Unsigned32,read-only,,current,,The total number of transactions aggregated into this record.
.1.3.6.1.2.1.16.23.1.10.1.4,APM-MIB::apmReportSuccessfulTransactions,Unsigned32,read-only,,current,,The total number of successful transactions aggregated into this record.
.1.3.6.1.2.1.16.23.1.10.1.5,APM-MIB::apmReportResponsivenessMean,Unsigned32,read-only,,current,,The arithmetic mean of the responsiveness metrics for all successful transactions aggregated into this record.
.1.3.6.1.2.1.16.23.1.10.1.6,APM-MIB::apmReportResponsivenessMin,Unsigned32,read-only,,current,,The minimum of the responsiveness metrics for all successful transactions aggregated into this record.
.1.3.6.1.2.1.16.23.1.10.1.7,APM-MIB::apmReportResponsivenessMax,Unsigned32,read-only,,current,,The maximum of the responsiveness metrics for all successful transactions aggregated into this record.
.1.3.6.1.2.1.16.23.1.10.1.8,APM-MIB::apmReportResponsivenessB1,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness was less than boundary1 value for this application.
.1.3.6.1.2.1.16.23.1.10.1.9,APM-MIB::apmReportResponsivenessB2,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness did not fall into Bucket 1 and was greater than or equal to the boundary1 value for this application and less than the boundary2 value for this application.
.1.3.6.1.2.1.16.23.1.10.1.10,APM-MIB::apmReportResponsivenessB3,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness did not fall into Bucket 1 or 2 and as greater than or equal to the boundary2 value for this application and less than the boundary3 value for this application.
.1.3.6.1.2.1.16.23.1.10.1.11,APM-MIB::apmReportResponsivenessB4,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness did not fall into Buckets 1 through 3 and was greater than or equal to the boundary3 value for this application and less than the boundary4 value for this application.
.1.3.6.1.2.1.16.23.1.10.1.12,APM-MIB::apmReportResponsivenessB5,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness did not fall into Buckets 1 through 4 and was greater than or equal to the boundary4 value for this application and less than the boundary5 value for this application.
.1.3.6.1.2.1.16.23.1.10.1.13,APM-MIB::apmReportResponsivenessB6,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness did not fall into Buckets 1 through 5 and was greater than or equal to the boundary5 value for this application and less than the boundary6 value for this application.
.1.3.6.1.2.1.16.23.1.10.1.14,APM-MIB::apmReportResponsivenessB7,Unsigned32,read-only,,current,,The number of successful transactions aggregated into this record whose responsiveness did not fall into Buckets 1 through 6 and was greater than or equal to the boundary6 value for this application.
.1.3.6.1.2.1.16.23.1.11,APM-MIB::apmTransactionTable,,not-accessible,,current,,This table contains transactions that are currently running or have recently finished.
.1.3.6.1.2.1.16.23.1.11.1,APM-MIB::apmTransactionEntry,,not-accessible,apmAppDirAppLocalIndex:apmAppDirResponsivenessType:protocolDirLocalIndex:apmTransactionServerAddress:apmNameClientID:apmTransactionID,current,,A conceptual row in the apmTransactionTable. The apmAppDirAppLocalIndex value in the index identifies the application of the transaction represented by this entry. The apmAppDirResponsivenessType value in the index identifies the type of responsiveness metric reported by this entry and uniquely identifies this entry when more than one responsiveness metric is measured for a flow. Entries will only exist in this table for those combinations of AppLocalIndex and ResponsivenessType that are configured 'on(1)'. The protocolDirLocalIndex value in the index identifies the network layer protocol of the apmTransactionServerAddress. The apmTransactionServerAddress value in the index identifies the network layer address of the server in the transaction represented by this entry. The apmNameClientID value in the index identifies the client in the transaction represented by this entry. An example of the indexing of this entry is apmTransactionCount.3.1.8.4.192.168.1.2.3232235788.2987 Note that some combinations of index values may result in an index that exceeds 128 sub-identifiers in length which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.16.23.1.11.1.1,APM-MIB::apmTransactionServerAddress,OCTET,not-accessible,,current,,The network server address for this apmTransactionEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. This object may not be the zero length string. For example, if the protocolDirLocalIndex indicates an encapsulation of ip, this object is encoded as a length octet of 4, followed by the 4 octets of the ip address, in network byte order. Care should be taken to avoid values of this object that, in conjunction with the other index variables, would result in an index longer than SNMP's maximum of 128 subidentifiers.
.1.3.6.1.2.1.16.23.1.11.1.2,APM-MIB::apmTransactionID,Unsigned32,not-accessible,,current,,A unique value for this transaction amongst other transactions sharing the same application layer protocol and server and client addresses. Implementations may choose to use the value of the client's source port, when possible.
.1.3.6.1.2.1.16.23.1.11.1.3,APM-MIB::apmTransactionResponsiveness,Unsigned32,read-only,,current,,The current value of the responsiveness metric for this transaction. If this transaction has completed, the final value of the metric will be available. Note that this value may change over the lifetime of the transaction and it is the final value of this metric that is recorded as the responsiveness of the transaction for use in other APM MIB functions.
.1.3.6.1.2.1.16.23.1.11.1.4,APM-MIB::apmTransactionAge,INTEGER,read-only,,current,,If this transaction is still executing, this value shall be the length of time since it was started. If it has completed, this value shall be the length of time it was executing.
.1.3.6.1.2.1.16.23.1.11.1.5,APM-MIB::apmTransactionSuccess,INTEGER,read-only,,current,true(1):false(2),The success of this transaction up to this time. Once a transaction has been marked as failed, it cannot move back into the successful state.
.1.3.6.1.2.1.16.23.1.12,APM-MIB::apmTransactionsRequestedHistorySize,Unsigned32,read-write,,current,,The maximum number of completed transactions desired to be retained in the apmTransactionTable. If the agent doesn't have enough resources to retain this many, it will retain as many as possible. Regardless of this value, the agent must attempt to keep records for all current transactions it is monitoring. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.13,APM-MIB::apmExceptionTable,,not-accessible,,current,,This table creates filters so that a management station can get immediate notification of a transaction that has had poor availability or responsiveness. Each apmExceptionEntry is associated with a particular type of transaction and is applied to all transactions of that type. Multiple apmExceptionEntries may be associated with a particular type of transaction. A transaction type is identified by the value of the apmAppDirAppLocalIndex component of the index. Because the quality of a transaction is not known until it is completed, these thresholds are only applied after the transaction has completed.
.1.3.6.1.2.1.16.23.1.13.1,APM-MIB::apmExceptionEntry,,not-accessible,apmAppDirAppLocalIndex:apmAppDirResponsivenessType:apmExceptionIndex,current,,A conceptual row in the apmExceptionTable. The apmAppDirAppLocalIndex value in the index identifies the application this entry will monitor. The apmAppDirResponsivenessType value in the index identifies the type of responsiveness metric this entry will monitor.
.1.3.6.1.2.1.16.23.1.13.1.1,APM-MIB::apmExceptionIndex,Unsigned32,not-accessible,,current,,An index that uniquely identifies an entry in the apmExceptionTable amongst other entries with equivalent index values for apmAppDirAppLocalIndex and apmAppDirResponsivenessType. Each such entry sets up thresholds for a particular measurement of a particular application.
.1.3.6.1.2.1.16.23.1.13.1.2,APM-MIB::apmExceptionResponsivenessComparison,INTEGER,read-create,,current,none(1):greater(2):less(3),If this value is greater(2) or less(3), the associated apmExceptionResponsivenessThreshold will be compared to this value and an exception will be created if the responsiveness is greater than the threshold (greater(2)) or less than the threshold (less(3)).
.1.3.6.1.2.1.16.23.1.13.1.3,APM-MIB::apmExceptionResponsivenessThreshold,Unsigned32,read-create,,current,,The threshold that responsiveness metrics are compared to.
.1.3.6.1.2.1.16.23.1.13.1.4,APM-MIB::apmExceptionUnsuccessfulException,INTEGER,read-create,,current,off(1):on(2),If this value is on(2), an exception will be created if a transaction of the associated type is unsuccessful.
.1.3.6.1.2.1.16.23.1.13.1.5,APM-MIB::apmExceptionResponsivenessEvents,Counter32,read-only,,current,,The total number of responsiveness exceptions generated. This counter will be incremented even if no notification was sent due to notifications not being configured or due to exceeding the apmNotificationMaxRate value.
.1.3.6.1.2.1.16.23.1.13.1.6,APM-MIB::apmExceptionUnsuccessfulEvents,Counter32,read-only,,current,,The total number of unsuccessful exceptions generated. This counter will be incremented even if no notification was sent due to notifications not being configured or due to exceeding the apmNotificationMaxRate value.
.1.3.6.1.2.1.16.23.1.13.1.7,APM-MIB::apmExceptionOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.23.1.13.1.8,APM-MIB::apmExceptionStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this apmReportControlEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.23.1.13.1.9,APM-MIB::apmExceptionStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this apmExceptionEntry. The only objects in the entry that may be modified while the entry is in the active state are apmExceptionResponsivenessComparison, apmExceptionResponsivenessThreshold and apmExceptionUnsuccessfulException.
.1.3.6.1.2.1.16.23.1.14,APM-MIB::apmThroughputExceptionMinTime,Unsigned32,read-write,,current,,Because the responsiveness for throughput-oriented transactions is divided by the elapsed time, it can be very sensitive to short-term performance variations for transactions that take a short period of time. For example, when downloading a very short file, a single dropped packet could double or triple the total response time. Further, throughput is usually examined for applications that transfer a lot of data, and when doing so it is helpful to conceptualize transaction costs that are proportional to the amount of data separately from those costs that are relatively fixed (i.e., independent of the amount of data). For very short transactions, these fixed transaction costs (handshake, setup time, authentication, round-trip time) may dominate the total response time for the transaction, resulting in throughput measurements that aren't really proportional to the network's, server's and client's combined data throughput capability. This object controls the minimum number of seconds that an throughput-based transaction must exceed before an exception can be generated for it. If this object is set to zero, then all throughput-based transactions are candidates for exceptions. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.1.15,APM-MIB::apmNotificationMaxRate,Unsigned32,read-write,,current,,The maximum number of notifications that can be generated from this agent by the apmExceptionTable in any 60 second period. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.23.2,APM-MIB::apmConformance,,,,,,
.1.3.6.1.2.1.16.23.2.1,APM-MIB::apmCompliances,,,,,,
.1.3.6.1.2.1.16.23.2.1.1,APM-MIB::apmCompliance,,,,,,Describes the requirements for conformance to the APM MIB
.1.3.6.1.2.1.16.23.2.2,APM-MIB::apmGroups,,,,,,
.1.3.6.1.2.1.16.23.2.2.1,APM-MIB::apmAppDirGroup,,,,,,The APM MIB directory of applications and application verbs.
.1.3.6.1.2.1.16.23.2.2.2,APM-MIB::apmUserDefinedApplicationsGroup,,,,,,Objects used for creating and managing user-defined applications.
.1.3.6.1.2.1.16.23.2.2.3,APM-MIB::apmReportGroup,,,,,,The apm report group controls the creation and retrieval of reports that aggregate application performance.
.1.3.6.1.2.1.16.23.2.2.4,APM-MIB::apmTransactionGroup,,,,,,The apm transaction group contains statistics for individual transactions.
.1.3.6.1.2.1.16.23.2.2.5,APM-MIB::apmExceptionGroup,,,,,,The apm exception group causes notifications to be sent whenever transactions are detected that had poor availability or responsiveness.
.1.3.6.1.2.1.16.23.2.2.6,APM-MIB::apmNotificationGroup,,,,,,Notifications sent by an APM MIB agent.
.1.3.6.1.2.1.16.26,DSMON-MIB::dsmonMIB,,,,,,This module defines Remote Monitoring MIB extensions for Differentiated Services enabled networks. RMON DIFFSERV DSCP statistics * Per Counter Aggregation Group * Per Protocol Per Counter Aggregation Group * Per Counter Aggregation Group Per Host * Per Counter Aggregation Group Per Host-Pair In order to maintain the RMON 'look-and-feel' and semantic consistency, some of the text from the RMON-2 and HC-RMON MIBs by Steve Waldbusser has been adapted for use in this MIB.
.1.3.6.1.2.1.16.26.1,DSMON-MIB::dsmonObjects,,,,,,
.1.3.6.1.2.1.16.26.1.1,DSMON-MIB::dsmonAggObjects,,,,,,
.1.3.6.1.2.1.16.26.1.1.1,DSMON-MIB::dsmonMaxAggGroups,Integer32,read-only,,current,,The maximum number of counter aggregation groups that this agent can support. The agent will allow this number of distinct groups to be configured in the dsmonAggProfileTable, numbered from '0' to 'dsmonMaxAggGroups - 1', for each counter aggregation profile entry supported by the agent. The agent MUST NOT lower this value during system operation, and SHOULD set this object to an appropriate value during system initialization.
.1.3.6.1.2.1.16.26.1.1.2,DSMON-MIB::dsmonAggControlLocked,INTEGER,read-write,,current,true(1):false(2),Controls the setup of counter aggregation groups for this agent. If this object contains the value 'true', then write access to the objects in the dsmonAggControlTable (except the dsmonAggControlOwner object), dsmonAggProfileTable, and dsmonAggGroupTable is not permitted, and data collection is possible. This object only controls write access to these MIB objects. The DSMON data collection control tables (e.g., dsmonHostCtlTable) can be configured at any time, regardless of the value of this object. If this object contains the value 'false', write access to the objects in the dsmonAggControlTable, dsmonAggProfileTable, and dsmonAggGroupTable is permitted, and data collection is not possible. In addition, all objects in all DSMON data tables (e.g., dsmonStatsTable) shall be deleted. An agent is not required to process SNMP Set Requests for this object in conjunction with other objects from this MIB. This is intended to simplify the processing of Set Requests for tables such as the dsmonAggProfileTable, by eliminating the possibility that a single Set PDU will contain multiple varbinds which are in conflict, such as a PDU which both modifies the dsmonAggProfileTable and locks the dsmonAggProfileTable at the same time. Note that the agent is not required to validate the entire counter aggregation configuration when an attempt is made to transition an instance of this object from 'true' to 'false'. That validation is done if and when a DSMON data collection is activated. An agent is required to reactivate any suspended data collections when this object transitions to 'true', Each active data control entry (e.g., dsmonStatsControlEntry), will be validated with respect to the new counter aggregation configuration. If the counter aggregation profile referenced in the data collection is valid, then that collection will be restarted. Otherwise, the RowStatus object (e.g., dsmonStatsControlStatus) will be set to 'notReady' for that collection control entry.
.1.3.6.1.2.1.16.26.1.1.3,DSMON-MIB::dsmonAggControlChanges,Counter32,read-only,,current,,This object counts the number of times the value of the dsmonAggControlLocked object has changed. A management station can use this object to detect if counters in the DSMON data tables (e.g., dsmonStatsEntry) have been deleted and recreated between polls. This object shall be incremented by one each time the dsmonAggControlLocked object changes from 'false' to 'true', or from 'true' to 'false'.
.1.3.6.1.2.1.16.26.1.1.4,DSMON-MIB::dsmonAggControlLastChangeTime,TimeTicks,read-only,,current,,This object identifies the value of sysUpTime at the moment the dsmonAggControlLocked object was last modified. A management station can use this object to detect if counters in the DSMON data tables (e.g., dsmonStatsEntry) have been deleted and recreated between polls. This object shall be updated with the current value of sysUpTime, if the dsmonAggControlLocked object changes from 'false' to 'true', or from 'true' to 'false'. Upon system initialization, this object shall contain the value zero.
.1.3.6.1.2.1.16.26.1.1.5,DSMON-MIB::dsmonAggControlTable,,not-accessible,,current,,This table provides an overall description and control point for all dsmonAggProfileEntries with the same dsmonAggControlIndex value. A management application SHOULD create a counter aggregation profile by first creating and activating an entry in this table. This will cause the agent to create a set of 64 dsmonAggProfileEntries on behalf of this control entry. An application can then set the individual counter aggregation group assignments for each of the 64 DSCP values, This table MUST NOT be modified if the dsmonAggControlLocked object is equal to 'true'. Note that an agent MAY choose to limit the actual number of entries which may be created in this table, and (independently) the number of counter aggregation profiles which may be applied to a particular data source. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905]. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Otherwise, each potential counter aggregation group description string SHOULD contain the empty string.
.1.3.6.1.2.1.16.26.1.1.5.1,DSMON-MIB::dsmonAggControlEntry,,not-accessible,dsmonAggControlIndex,current,,A conceptual row in the dsmonAggControlTable.
.1.3.6.1.2.1.16.26.1.1.5.1.1,DSMON-MIB::dsmonAggControlIndex,Integer32,not-accessible,,current,,An arbitrary integer index value used to identify the counter aggregation profile specified by this control entry.
.1.3.6.1.2.1.16.26.1.1.5.1.2,DSMON-MIB::dsmonAggControlDescr,OCTET,read-create,,current,,An administratively assigned description of the counter aggregation profile identified by this entry. Upon first creation of an instance of this object, the agent SHOULD set this object to the empty string. If the agent supports non-volatile storage, then this object SHOULD be re-initialized with its stored value after a system reboot. This object MUST NOT be modified if the associated dsmonAggControlStatus object is equal to 'active', or the dsmonAggControlLocked object is equal to 'true'.
.1.3.6.1.2.1.16.26.1.1.5.1.3,DSMON-MIB::dsmonAggControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.1.5.1.4,DSMON-MIB::dsmonAggControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. Upon setting this object to active(1), the agent will create a complete set of 64 associated entries in the dsmonAggProfileTable. If this object is not equal to active(1), all associated entries in the dsmonAggProfileTable shall be deleted. This object MUST NOT be modified if the dsmonAggControlLocked object is equal to 'true'.
.1.3.6.1.2.1.16.26.1.1.6,DSMON-MIB::dsmonAggProfileTable,,not-accessible,,current,,Controls the setup of counter aggregation profiles for this agent. For each such profile, every DSCP value MUST be configured into exactly one counter aggregation group. This table MUST NOT be modified if the dsmonAggControlLocked object is equal to 'true'. The agent will create a set of 64 entries in this table (with the same dsmonAggControlIndex value) when the associated dsmonAggControlEntry is activated. If the agent supports non-volatile configuration of this table, then upon system initialization, this table SHOULD be initialized with the saved values.
.1.3.6.1.2.1.16.26.1.1.6.1,DSMON-MIB::dsmonAggProfileEntry,,not-accessible,dsmonAggControlIndex:dsmonAggProfileDSCP,current,,A conceptual row in the dsmonAggProfileTable. The dsmonAggControlIndex value in the index identifies the dsmonAggControlEntry associated with each entry in this table.
.1.3.6.1.2.1.16.26.1.1.6.1.1,DSMON-MIB::dsmonAggProfileDSCP,Integer32,not-accessible,,current,,The specific DSCP value for the DSCP counter which is configured in a counter aggregation group by this entry.
.1.3.6.1.2.1.16.26.1.1.6.1.2,DSMON-MIB::dsmonAggGroupIndex,Integer32,read-write,,current,,The counter aggregation group which contains this DSCP value. Upon creation of a new sub-tree (set of 64 entries with the same dsmonAggControlIndex value) in this table, the agent SHOULD initialize all related instances of this object to the value zero. This object MUST NOT be modified if the dsmonAggControlLocked object is equal to 'true'.
.1.3.6.1.2.1.16.26.1.1.7,DSMON-MIB::dsmonAggGroupTable,,not-accessible,,current,,This table provides a description of each counter aggregation group configured on this system. Note that the semantics of a particular counter aggregation group are only relevant within the scope of a particular counter aggregation profile. This table MUST NOT be modified if the dsmonAggControlLocked object is equal to 'true'. Note that an agent MAY choose to limit the actual number of entries which may be created in this table, and (independently) the number of counter aggregation profiles which may be applied to a particular data source. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905]. If the agent supports non-volatile configuration of this table, then upon system initialization, this table SHOULD be initialized with the saved values. Otherwise, each potential counter aggregation group description string SHOULD contain the empty string. An agent SHOULD allow entries to be created or modified in this table, even if the specified dsmonAggControlIndex value does not identify a valid dsmonAggControlEntry or a complete set of valid dsmonAggProfileEntries, to reduce row creation order dependencies.
.1.3.6.1.2.1.16.26.1.1.7.1,DSMON-MIB::dsmonAggGroupEntry,,not-accessible,dsmonAggControlIndex:dsmonAggGroupIndex,current,,A conceptual row in the dsmonAggGroupTable. The dsmonAggGroupIndex value in the INDEX identifies the counter aggregation group associated with each entry. The dsmonAggControlIndex in the index identifies the counter aggregation profile associated with each entry, identified by the dsmonAggControlEntry and dsmonAggProfileEntries with the same index value. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. The dsmonAggGroupIndex in the index identifies the counter aggregation group associated with each entry. This object SHOULD be indexed from zero to 'N', where 'N' is less than the value of the dsmonMaxAggGroups for this agent.
.1.3.6.1.2.1.16.26.1.1.7.1.1,DSMON-MIB::dsmonAggGroupDescr,OCTET,read-create,,current,,An administratively assigned description of the counter aggregation group identified by this entry. Upon first creation of an instance of this object, the agent SHOULD set this object to the empty string. This object MUST NOT be modified if the associated dsmonAggGroupStatus object is equal to 'active', or the dsmonAggControlLocked object is equal to 'true'.
.1.3.6.1.2.1.16.26.1.1.7.1.2,DSMON-MIB::dsmonAggGroupStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. This object MUST NOT be modified if the dsmonAggControlLocked object is equal to 'true'.
.1.3.6.1.2.1.16.26.1.2,DSMON-MIB::dsmonStatsObjects,,,,,,
.1.3.6.1.2.1.16.26.1.2.1,DSMON-MIB::dsmonStatsControlTable,,not-accessible,,current,,Controls the setup of per data source per counter aggregation group distribution statistics. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.2.1.1,DSMON-MIB::dsmonStatsControlEntry,,not-accessible,dsmonStatsControlIndex,current,,A conceptual row in the dsmonStatsControlTable. Entries are created and deleted from this table by management action only, using the dsmonStatsControlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonStatsTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.2.1.1.1,DSMON-MIB::dsmonStatsControlIndex,Integer32,not-accessible,,current,,An arbitrary and unique index for this dsmonStatsControlEntry.
.1.3.6.1.2.1.16.26.1.2.1.1.2,DSMON-MIB::dsmonStatsControlDataSource,OBJECT,read-create,,current,,The data source of this per protocol per counter aggregation group distribution. Note that only packets that contain a network protocol encapsulation which contains a DS field [RFC2474] will be counted in this table. This object MUST NOT be modified if the associated dsmonStatsControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.2.1.1.3,DSMON-MIB::dsmonStatsControlAggProfile,Integer32,read-create,,current,,The dsmonAggControlIndex value identifying the counter aggregation profile which should be used on behalf of this dsmonStatsControlEntry. The associated dsmonAggControlEntry and dsmonAggProfileEntries, identified by the same dsmonAggControlIndex index value, MUST be active in order for this entry to remain active. It is possible for the counter aggregation configuration to change from a valid to invalid state for this dsmonStats collection. In this case, the associated dsmonStatsControlStatus object will be changed to the 'notReady' state, and data collection will not occur on behalf of this control entry. Note that an agent MAY choose to limit the actual number of counter aggregation profiles which may be applied to a particular data source. This object MUST NOT be modified if the associated dsmonStatsControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.2.1.1.4,DSMON-MIB::dsmonStatsControlDroppedFrames,Counter32,read-only,,current,,The total number of frames which were received by the probe and therefore not accounted for in the *StatsDropEvents, but for which the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.26.1.2.1.1.5,DSMON-MIB::dsmonStatsControlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to detect if the table has been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.2.1.1.6,DSMON-MIB::dsmonStatsControlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.2.1.1.7,DSMON-MIB::dsmonStatsControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonStatsTable shall be deleted.
.1.3.6.1.2.1.16.26.1.2.2,DSMON-MIB::dsmonStatsTable,,not-accessible,,current,,A list of information on counter aggregation group usage for each monitored data source. The following table defines per counter aggregation group statistics for full and/or half-duplex links as well as high capacity links. For half-duplex links, or full-duplex-capable links operating in half-duplex mode, the dsmonStatsIn* objects shall be used and the dsmonStatsOut* objects will not increment. For full-duplex links, the dsmonStatsOut* objects will be present. Whenever possible, the probe SHOULD count packets moving away from the closest terminating equipment as output packets. Failing that, the probe SHOULD count packets moving away from the DTE as output packets. If the dsmonAggControlLocked object is equal to 'false', then all entries in this table will be deleted and the agent will not process packets on behalf of any dsmonStatsControlEntry.
.1.3.6.1.2.1.16.26.1.2.2.1,DSMON-MIB::dsmonStatsEntry,,not-accessible,dsmonStatsControlIndex:dsmonAggGroupIndex,current,,A list of information on Differentiated Services DSCP usage, containing inbound and outbound packet and octet counters for each counter aggregation group configured for collection. The dsmonStatsControlIndex value in the index identifies the dsmonStatsControlEntry on whose behalf this entry was created. The dsmonAggGroupIndex value in the index is determined by examining the DSCP value in each monitored packet, and the dsmonAggProfileTable entry for that DSCP value. Note that only packets that contain a network protocol encapsulation which contains a DS field [RFC2474] will be counted in this table. An example of the indexing of this entry is dsmonStatsOutPkts.1.16
.1.3.6.1.2.1.16.26.1.2.2.1.1,DSMON-MIB::dsmonStatsInPkts,Gauge32,read-only,,current,,The number of packets using one of the DSCP values in the indicated counter aggregation group, received on a half- duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.26.1.2.2.1.2,DSMON-MIB::dsmonStatsInOctets,Gauge32,read-only,,current,,The number of octets in packets, using one of the DSCP values in the indicated counter aggregation group, received on a half-duplex link or on the inbound connection of a full-duplex link.
.1.3.6.1.2.1.16.26.1.2.2.1.3,DSMON-MIB::dsmonStatsInOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonStatsInPkts counter has overflowed. Note that this object will only be instantiated if the associated dsmonStatsInHCPkts object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.4,DSMON-MIB::dsmonStatsInOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonStatsInOctets counter has overflowed. Note that this object will only be instantiated if the associated dsmonStatsInHCOctets object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.5,DSMON-MIB::dsmonStatsInHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonStatsInPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.6,DSMON-MIB::dsmonStatsInHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonStatsInOctets object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.7,DSMON-MIB::dsmonStatsOutPkts,Gauge32,read-only,,current,,The number of packets using one of the DSCP values in the indicated counter aggregation group, received on a full- duplex link in the direction of the network.
.1.3.6.1.2.1.16.26.1.2.2.1.8,DSMON-MIB::dsmonStatsOutOctets,Gauge32,read-only,,current,,The number of octets in packets, using one of the DSCP values in the indicated counter aggregation group, received on a full-duplex link in the direction of the network.
.1.3.6.1.2.1.16.26.1.2.2.1.9,DSMON-MIB::dsmonStatsOutOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonStatsOutPkts counter has overflowed. Note that this object will only be instantiated if the associated dsmonStatsOutHCPkts object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.10,DSMON-MIB::dsmonStatsOutOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonStatsOutOctets counter has overflowed. Note that this object will only be instantiated if the associated dsmonStatsOutHCOctets object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.11,DSMON-MIB::dsmonStatsOutHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonStatsOutPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.2.2.1.12,DSMON-MIB::dsmonStatsOutHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonStatsOutOctets object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.3,DSMON-MIB::dsmonPdistObjects,,,,,,
.1.3.6.1.2.1.16.26.1.3.1,DSMON-MIB::dsmonPdistCtlTable,,not-accessible,,current,,Controls the setup of per application per counter aggregation group distribution statistics. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.3.1.1,DSMON-MIB::dsmonPdistCtlEntry,,not-accessible,dsmonPdistCtlIndex,current,,A conceptual row in the dsmonPdistCtlTable. Entries are created and deleted from this table by management action only, using the dsmonPdistCtlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonPdistStatsTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.3.1.1.1,DSMON-MIB::dsmonPdistCtlIndex,Integer32,not-accessible,,current,,An arbitrary and unique index for this dsmonPdistCtlEntry.
.1.3.6.1.2.1.16.26.1.3.1.1.2,DSMON-MIB::dsmonPdistCtlDataSource,OBJECT,read-create,,current,,The source of data for the this per protocol counter aggregation group distribution. This object MUST NOT be modified if the associated dsmonPdistCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.3.1.1.3,DSMON-MIB::dsmonPdistCtlAggProfile,Integer32,read-create,,current,,The dsmonAggControlIndex value identifying the counter aggregation profile which should be used on behalf of this dsmonPdistCtlEntry. The associated dsmonAggControlEntry and dsmonAggProfileEntries, identified by the same dsmonAggControlIndex index value, MUST be active in order for this entry to remain active. It is possible for the counter aggregation configuration to change from a valid to invalid state for this dsmonPdist collection. In this case, the associated dsmonPdistCtlStatus object will be changed to the 'notReady' state, and data collection will not occur on behalf of this control entry. Note that an agent MAY choose to limit the actual number of counter aggregation profiles which may be applied to a particular data source. This object MUST NOT be modified if the associated dsmonPdistCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.3.1.1.4,DSMON-MIB::dsmonPdistCtlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the dsmonPdistStatsTable on behalf of this control entry. The probe will not create more than this number of associated entries in the table, but MAY choose to create fewer entries in this table for any reason including the lack of resources. If this value is set to -1, the probe MAY create any number of entries in this table. This object MUST NOT be modified if the associated dsmonPdistCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.3.1.1.5,DSMON-MIB::dsmonPdistCtlDroppedFrames,Counter32,read-only,,current,,The total number of frames which were received by the probe and therefore not accounted for in the *StatsDropEvents, but for which the probe chose not to count for this entry for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.26.1.3.1.1.6,DSMON-MIB::dsmonPdistCtlInserts,Counter32,read-only,,current,,The number of times a dsmonPdist entry has been inserted into the dsmonPdistTable. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents MAY delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting dsmonPdistCtlDeletes from dsmonPdistCtlInserts.
.1.3.6.1.2.1.16.26.1.3.1.1.7,DSMON-MIB::dsmonPdistCtlDeletes,Counter32,read-only,,current,,The number of times a dsmonPdist entry has been deleted from the dsmonPdist table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents MAY delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting dsmonPdistCtlDeletes from dsmonPdistCtlInserts.
.1.3.6.1.2.1.16.26.1.3.1.1.8,DSMON-MIB::dsmonPdistCtlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to detect if the table has been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.3.1.1.9,DSMON-MIB::dsmonPdistCtlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.3.1.1.10,DSMON-MIB::dsmonPdistCtlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonPdistStatsTable shall be deleted.
.1.3.6.1.2.1.16.26.1.3.2,DSMON-MIB::dsmonPdistStatsTable,,not-accessible,,current,,A list of information on a per protocol per counter aggregation group usage. If the dsmonAggControlLocked object is equal to 'false', then all entries in this table will be deleted and the agent will not process packets on behalf of any dsmonPdistCtlEntry.
.1.3.6.1.2.1.16.26.1.3.2.1,DSMON-MIB::dsmonPdistStatsEntry,,not-accessible,dsmonPdistCtlIndex:dsmonPdistTimeMark:dsmonAggGroupIndex:protocolDirLocalIndex,current,,A list of information on Differentiated Services DSCP usage, containing packet and octet counters for each counter aggregation group configured for collection, and each protocol (as identified by the protocolDirLocalIndex for the protocol) identified in each monitored packet. The dsmonPdistCtlIndex value in the index identifies the dsmonPdistCtlEntry on whose behalf this entry was created. Note that only packets that contain a network protocol encapsulation which contains a DS field [RFC2474] will be counted in this table. The dsmonAggGroupIndex value in the index is determined by examining the DSCP value in each monitored packet, and the dsmonAggProfileTable entry for that value. The protocolDirLocalIndex in the index identifies the protocolDirEntry for the protocol encapsulation of each monitored packet. The agent will include only application layer protocols in the associated dsmonPdistStatsTable. Any 'terminal' protocol is considered to be an application protocol. An example of the indexing of this entry is dsmonPdistStatsPkts.9.29943.0.42.
.1.3.6.1.2.1.16.26.1.3.2.1.1,DSMON-MIB::dsmonPdistTimeMark,TimeTicks,not-accessible,,current,,The Time Filter index for this table. This object may be used by a management station to retrieve only rows which have been created or modified since a particular time. Note that the current value for a row are always returned and the TimeFilter is not a historical data archiving mechanism. Refer to RFC 2021 [RFC2021] for a detailed description of TimeFilter operation.
.1.3.6.1.2.1.16.26.1.3.2.1.2,DSMON-MIB::dsmonPdistStatsPkts,Gauge32,read-only,,current,,The number of packets, using one of the DSCP values in the indicated counter aggregation group, for the protocol identified by the associated protocolDirLocalIndex value.
.1.3.6.1.2.1.16.26.1.3.2.1.3,DSMON-MIB::dsmonPdistStatsOctets,Gauge32,read-only,,current,,The number of octets in packets, using one of the DSCP values in the indicated counter aggregation group, for the protocol identified by the associated protocolDirLocalIndex value. Note that this object doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.26.1.3.2.1.4,DSMON-MIB::dsmonPdistStatsOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonPdistStatsPkts counter has overflowed. Note that this object will only be instantiated if the associated dsmonPdistStatsHCPkts object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.3.2.1.5,DSMON-MIB::dsmonPdistStatsOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonPdistStatsOctets counter has overflowed. Note that this object will only be instantiated if the associated dsmonPdistStatsHCOctets object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.3.2.1.6,DSMON-MIB::dsmonPdistStatsHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonPdistStatsPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.3.2.1.7,DSMON-MIB::dsmonPdistStatsHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonPdistStatsOctets object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.3.2.1.8,DSMON-MIB::dsmonPdistStatsCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this dsmonPdistStats entry was last instantiated by the agent. This can be used by the management station to detect if the entry has been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.3.3,DSMON-MIB::dsmonPdistTopNCtlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N dsmonPdist entries according to a particular metric. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.3.3.1,DSMON-MIB::dsmonPdistTopNCtlEntry,,not-accessible,dsmonPdistTopNCtlIndex,current,,A conceptual row in the dsmonPdistTopNCtlTable. Entries are created and deleted from this table by management action only, using the dsmonPdistTopNCtlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonPdistTopNTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.3.3.1.1,DSMON-MIB::dsmonPdistTopNCtlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the dsmonPdistTopNCtlTable, with the same dsmonPdistTopNCtlIndex value as this object. Each entry in this table defines one Top N report prepared on behalf of the dsmonPdistStatsEntry collection with the same dsmonPdistCtlIndex as this object.
.1.3.6.1.2.1.16.26.1.3.3.1.2,DSMON-MIB::dsmonPdistTopNCtlPdistIndex,Integer32,read-create,,current,,The dsmonPdistTable for which a top N report will be prepared on behalf of this entry. The dsmonPdistTable is identified by the value of the dsmonPdistCtlIndex for that table - that value is used here to identify the particular table. This object MUST NOT be modified if the associated dsmonPdistTopNCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.3.3.1.3,DSMON-MIB::dsmonPdistTopNCtlRateBase,INTEGER,read-create,,current,dsmonPdistTopNPkts(1):dsmonPdistTopNOctets(2):dsmonPdistTopNHCPkts(3):dsmonPdistTopNHCOctets(4),The variable for each dsmonPdist that the dsmonPdistTopNRate and dsmonPdistTopNHCRate variables are based upon. Each dsmonPdistTopN report generated on behalf of this control entry will be ranked in descending order, based on the associated dsmonPdistStatsTable counter, identified by this object. The following table identifies the dsmonPdistTable counter associated with each enumeration: Enumeration RateBase MIB Object ----------- ------------------- dsmonPdistTopNPkts dsmonPdistStatsPkts dsmonPdistTopNOctets dsmonPdistStatsOctets dsmonPdistTopNHCPkts dsmonPdistStatsHCPkts dsmonPdistTopNHCOctets dsmonPdistStatsHCOctets Note that the dsmonPdistTopNHCPkts and dsmonPdistTopNHCOctets enumerations are only available if the agent supports High Capacity monitoring. This object MUST NOT be modified if the associated dsmonPdistTopNCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.3.3.1.4,DSMON-MIB::dsmonPdistTopNCtlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, and is immediately loaded into the associated dsmonPdistTopNCtlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of dsmonPdistTopNCtlTimeRemaining. Thus the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the dsmonPdistTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the dsmonPdistTopNTable shall be deleted.
.1.3.6.1.2.1.16.26.1.3.3.1.5,DSMON-MIB::dsmonPdistTopNCtlGeneratedReprts,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.26.1.3.3.1.6,DSMON-MIB::dsmonPdistTopNCtlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated dsmonPdistTopNCtlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the dsmonPdistTopNCtlTimeRemaining is set. This value shall be zero if no reports have been requested for this dsmonPdistTopNCtlEntry.
.1.3.6.1.2.1.16.26.1.3.3.1.7,DSMON-MIB::dsmonPdistTopNCtlRequestedSize,Integer32,read-create,,current,,The maximum number of dsmonPdist entries requested for this report. When this object is created or modified, the probe SHOULD set dsmonPdistTopNCtlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.26.1.3.3.1.8,DSMON-MIB::dsmonPdistTopNCtlGrantedSize,Integer32,read-only,,current,,The maximum number of dsmonPdist entries in this report. When the associated dsmonPdistTopNCtlRequestedSize object is created or modified, the probe SHOULD set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe MUST NOT lower this value except as a result of a set to the associated dsmonPdistTopNCtlRequestedSize object. Protocol entries with the highest value of dsmonPdistTopNRate or dsmonPdistTopNHCRate (depending on the value of the associated dsmonPdistTopNCtlRateBase object) shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more dsmonPdist entries.
.1.3.6.1.2.1.16.26.1.3.3.1.9,DSMON-MIB::dsmonPdistTopNCtlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated dsmonPdistTopNCtlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine if a report was missed or not.
.1.3.6.1.2.1.16.26.1.3.3.1.10,DSMON-MIB::dsmonPdistTopNCtlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.3.3.1.11,DSMON-MIB::dsmonPdistTopNCtlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this dsmonPdistTopNCtlEntry. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonPdistTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.26.1.3.4,DSMON-MIB::dsmonPdistTopNTable,,not-accessible,,current,,A set of statistics for those protocol distribution entries that have counted the highest number of octets or packets. If the dsmonAggControlLocked object is equal to 'false', then all entries in this table SHALL be deleted, and the agent will not process TopN reports on behalf of any dsmonPdistTopNCtlEntry. When the dsmonAggControlLocked object is set to 'true', then particular reports SHOULD be restarted from the beginning, on behalf of all active rows in the dsmonPdistTopNCtlTable. Note that dsmonPdist entries which did not increment at all during the report interval SHOULD NOT be included in dsmonPdistTopN reports.
.1.3.6.1.2.1.16.26.1.3.4.1,DSMON-MIB::dsmonPdistTopNEntry,,not-accessible,dsmonPdistTopNCtlIndex:dsmonPdistTopNIndex,current,,A conceptual row in the dsmonPdistTopNTable. The dsmonPdistTopNCtlIndex value in the index identifies the dsmonPdistTopNCtlEntry on whose behalf this entry was created. Entries in this table are ordered from 1 to 'N', where lower numbers represent higher values of the rate base object, over the report interval.
.1.3.6.1.2.1.16.26.1.3.4.1.1,DSMON-MIB::dsmonPdistTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the dsmonPdistTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. Note that 'N' may change over time, and may also be less than the dsmonPdistTopNCtlGrantedSize value associated with this entry.
.1.3.6.1.2.1.16.26.1.3.4.1.2,DSMON-MIB::dsmonPdistTopNPDLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex value which identifies the protocol associated with this entry. If the protocolDirEntry associated with the protocolDirLocalIndex with the same value as this object is de-activated or deleted, then the agent MUST delete this dsmonPdistTopN entry.
.1.3.6.1.2.1.16.26.1.3.4.1.3,DSMON-MIB::dsmonPdistTopNAggGroup,Integer32,read-only,,current,,The DSCP counter aggregation group index value associated with protocol identified in this entry. This object identifies the dsmonAggGroupEntry with the same dsmonAggControlIndex value as the associated dsmonPdistCtlAggProfile object and the same dsmonAggGroupIndex value as this object.
.1.3.6.1.2.1.16.26.1.3.4.1.4,DSMON-MIB::dsmonPdistTopNRate,Gauge32,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this protocol's instance of the object selected by dsmonPdistTopNCtlRateBase. If the associated dsmonPdistTopNCtlRateBase is equal to 'dsmonPdistTopNHCPkts' or 'dsmonPdistTopNHCOctets', then this object will contain the the least significant 32 bits of the associated dsmonPdistTopNHCRate object.
.1.3.6.1.2.1.16.26.1.3.4.1.5,DSMON-MIB::dsmonPdistTopNRateOvfl,Gauge32,read-only,,deprecated,,The most significant 32 bits of the associated dsmonPdistTopNHCRate object. If the associated dsmonPdistTopNCtlRateBase is equal to 'dsmonPdistTopNHCPkts' or 'dsmonPdistTopNHCOctets', then this object will contain the upper 32 bits of the associated dsmonPdistTopNHCRate object. If the associated dsmonPdistTopNCtlRateBase is equal to 'dsmonPdistTopNPkts' or 'dsmonPdistTopNOctets', then this object will contain the value zero. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.3.4.1.6,DSMON-MIB::dsmonPdistTopNHCRate,Counter64,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this protocol's instance of the object selected by dsmonPdistTopNCtlRateBase. If the associated dsmonPdistTopNCtlRateBase is equal to 'dsmonPdistTopNPkts' or 'dsmonPdistTopNOctets', then this object will contain the value zero, and the associated dsmonPdistTopNRate object will contain the change in the selected variable during the sampling interval. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.4,DSMON-MIB::dsmonHostObjects,,,,,,
.1.3.6.1.2.1.16.26.1.4.1,DSMON-MIB::dsmonHostCtlTable,,not-accessible,,current,,Controls setup of per counter aggregation group, per network layer host distribution statistics. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.4.1.1,DSMON-MIB::dsmonHostCtlEntry,,not-accessible,dsmonHostCtlIndex,current,,A conceptual row in the dsmonHostCtlTable. Entries are created and deleted from this table by management action only, using the dsmonHostCtlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonHostTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.4.1.1.1,DSMON-MIB::dsmonHostCtlIndex,Integer32,not-accessible,,current,,An arbitrary and unique index for this dsmonHostCtlEntry.
.1.3.6.1.2.1.16.26.1.4.1.1.2,DSMON-MIB::dsmonHostCtlDataSource,OBJECT,read-create,,current,,The source of data for the associated dsmonHostTable. Note that only packets that contain a network protocol encapsulation which contains a DS field [RFC2474] will be counted in this table. This object MUST NOT be modified if the associated dsmonHostCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.1.1.3,DSMON-MIB::dsmonHostCtlAggProfile,Integer32,read-create,,current,,The dsmonAggControlIndex value identifying the counter aggregation profile which should be used on behalf of this dsmonHostCtlEntry. The associated dsmonAggControlEntry and dsmonAggProfileEntries, identified by the same dsmonAggControlIndex index value, MUST be active in order for this entry to remain active. It is possible for the counter aggregation configuration to change from a valid to invalid state for this dsmonHost collection. In this case, the associated dsmonHostCtlStatus object will be changed to the 'notReady' state, and data collection will not occur on behalf of this control entry. Note that an agent MAY choose to limit the actual number of counter aggregation profiles which may be applied to a particular data source. This object MUST NOT be modified if the associated dsmonHostCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.1.1.4,DSMON-MIB::dsmonHostCtlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the dsmonHostTable on behalf of this control entry. The probe will not create more than this number of associated entries in the table, but MAY choose to create fewer entries in this table for any reason including the lack of resources. If this value is set to -1, the probe MAY create any number of entries in this table. This object MUST NOT be modified if the associated dsmonHostCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.1.1.5,DSMON-MIB::dsmonHostCtlIPv4PrefixLen,Integer32,read-create,,current,,The number of 'leftmost' contiguous bits in the host address field for encapsulations of IPv4, that should be maintained in this collection. This object controls how the dsmonHostAddress object is derived for packets which contain an encapsulation of IPv4. If this object has a value less than 32, then 'm' rightmost bits, where 'm' is equal to '32 - dsmonHostCtlIPv4PrefixLen', will be cleared to zero for counting purposes only. The 'leftmost' bit is the most significant bit of the first network-byte-order octet of the address. If this object is equal to 32, then no bits are cleared in each dsmonHostAddress field. This object MUST NOT be modified if the associated dsmonHostCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.1.1.6,DSMON-MIB::dsmonHostCtlIPv6PrefixLen,Integer32,read-create,,current,,The number of 'leftmost' contiguous bits in the host address field for encapsulations of IPv6, that should be maintained in this collection. This object controls how the dsmonHostAddress object is derived for packets which contain an encapsulation of IPv6. If this object has a value less than 128, then 'm' rightmost bits, where 'm' is equal to '128 - dsmonHostCtlIPv6PrefixLen', will be cleared to zero for counting purposes only. The 'leftmost' bit is the most significant bit of the first network-byte-order octet of the address. If this object is equal to 128, then no bits are cleared in each dsmonHostAddress field. This object MUST NOT be modified if the associated dsmonHostCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.1.1.7,DSMON-MIB::dsmonHostCtlDroppedFrames,Counter32,read-only,,current,,The total number of frames which were received by the probe and therefore not accounted for in the *StatsDropEvents, but for which the probe chose not to count for the associated dsmonHost entries for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the dsmonHostTable is inactive because no appropriate protocols are enabled in the protocol directory, this value SHOULD be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.26.1.4.1.1.8,DSMON-MIB::dsmonHostCtlInserts,Counter32,read-only,,current,,The number of times a dsmonHost entry has been inserted into the dsmonHost table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents MAY delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting dsmonHostCtlDeletes from dsmonHostCtlInserts.
.1.3.6.1.2.1.16.26.1.4.1.1.9,DSMON-MIB::dsmonHostCtlDeletes,Counter32,read-only,,current,,The number of times a dsmonHost entry has been deleted from the dsmonHost table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents MAY delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting dsmonHostCtlDeletes from dsmonHostCtlInserts.
.1.3.6.1.2.1.16.26.1.4.1.1.10,DSMON-MIB::dsmonHostCtlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to detect if the table has been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.4.1.1.11,DSMON-MIB::dsmonHostCtlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.4.1.1.12,DSMON-MIB::dsmonHostCtlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this dsmonHostCtlEntry. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonHostTable shall be deleted.
.1.3.6.1.2.1.16.26.1.4.2,DSMON-MIB::dsmonHostTable,,not-accessible,,current,,A collection of statistics for particular network protocols which contain a DS field, and that has been discovered on a particular dataSource. The probe will add to this table all appropriate network protocols, for each network address seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. If the dsmonAggControlLocked object is equal to 'false', then all entries in this table will be deleted, and the agent will not process packets on behalf of any dsmonHostCtlEntry.
.1.3.6.1.2.1.16.26.1.4.2.1,DSMON-MIB::dsmonHostEntry,,not-accessible,dsmonHostCtlIndex:dsmonHostTimeMark:dsmonAggGroupIndex:protocolDirLocalIndex:dsmonHostAddress,current,,A list of information on Differentiated Services DSCP usage, containing packet and octet counters for each counter aggregation group index configured for collection per host address, as identified in the dsmonAggProfileTable. The dsmonHostCtlIndex value in the index identifies the dsmonHostCtlEntry on whose behalf this entry was created. The protocolDirLocalIndex value in the index identifies the specific network layer protocol encapsulation associated with each entry, and the network protocol type of the dsmonHostAddress object. It MUST identify a protocolDirEntry which contains a DS field (e.g., IPv4 or IPv6). Note that if a protocol encapsulation with multiple network layers is specified, then associated entries in this table refer to the innermost network protocol layer host address. The dsmonAggGroupIndex value in the index is determined by examining the DSCP value in each monitored packet, and the dsmonAggProfileTable entry configured for that value. An example of the indexing of this entry is dsmonHostOutPkts.1.27273.3.200.4.171.69.120.0
.1.3.6.1.2.1.16.26.1.4.2.1.1,DSMON-MIB::dsmonHostTimeMark,TimeTicks,not-accessible,,current,,The Time Filter index for this table. This object may be used by a management station to retrieve only rows which have been created or modified since a particular time. Note that the current value for a row are always returned and the TimeFilter is not a historical data archiving mechanism. Refer to RFC 2021 [RFC2021] for a detailed description of TimeFilter operation.
.1.3.6.1.2.1.16.26.1.4.2.1.2,DSMON-MIB::dsmonHostAddress,OCTET,not-accessible,,current,,The network address for this dsmonHostEntry. This object is encoded according to the protocol type indicated by the protocolDirLocalIndex value in the index. In addition, this object may have some 'rightmost' bits cleared to zero for counting purposes, as indicated by the associated dsmonHostCtlIPv4PrefixLen or dsmonHostCtlIPv6PrefixLen objects.
.1.3.6.1.2.1.16.26.1.4.2.1.3,DSMON-MIB::dsmonHostInPkts,Gauge32,read-only,,current,,The number of packets without errors, using one of the DSCP values in the indicated counter aggregation group, and transmitted to this address, since this entry was added to the dsmonHostTable. Note that this is the number of link- layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.26.1.4.2.1.4,DSMON-MIB::dsmonHostInOctets,Gauge32,read-only,,current,,The number of octets in all packets, transmitted to this address and using one of the DSCP values in the indicated counter aggregation group, since this entry was added to the dsmonHostTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.26.1.4.2.1.5,DSMON-MIB::dsmonHostInOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonHostInPkts counter has overflowed. Note that this object will only be instantiated if the associated dsmonHostInHCPkts object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.6,DSMON-MIB::dsmonHostInOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonHostInOctets counter has overflowed. Note that this object will only be instantiated if the associated dsmonHostInHCOctets object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.7,DSMON-MIB::dsmonHostInHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonHostInPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.8,DSMON-MIB::dsmonHostInHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonHostInOctets object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.9,DSMON-MIB::dsmonHostOutPkts,Gauge32,read-only,,current,,The number of packets without errors, using one of the DSCP values in the indicated counter aggregation group, and transmitted by this address, since this entry was added to the dsmonHostTable. Note that this is the number of link- layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.26.1.4.2.1.10,DSMON-MIB::dsmonHostOutOctets,Gauge32,read-only,,current,,The number of octets, transmitted by this address and using one of the DSCP values in the identified counter aggregation group, since this entry was added to the dsmonHostTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.26.1.4.2.1.11,DSMON-MIB::dsmonHostOutOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonHostOutPkts counter has overflowed. Note that this object will only be instantiated if the associated dsmonHostOutHCPkts object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.12,DSMON-MIB::dsmonHostOutOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonHostOutOctets counter has overflowed. Note that this object will only be instantiated if the associated dsmonHostOutHCOctets object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.13,DSMON-MIB::dsmonHostOutHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonHostOutPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.14,DSMON-MIB::dsmonHostOutHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonHostOutOctets object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.4.2.1.15,DSMON-MIB::dsmonHostCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this dsmonHost entry was last instantiated by the agent. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.4.3,DSMON-MIB::dsmonHostTopNCtlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N dsmonHost entries according to a selected metric. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.4.3.1,DSMON-MIB::dsmonHostTopNCtlEntry,,not-accessible,dsmonHostTopNCtlIndex,current,,A conceptual row in the dsmonHostTopNCtlTable. Entries are created and deleted from this table by management action only, using the dsmonHostTopNCtlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonHostTopNTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.4.3.1.1,DSMON-MIB::dsmonHostTopNCtlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the dsmonHostTopNCtlTable. Each such entry defines one Top N report prepared for one RMON dataSource.
.1.3.6.1.2.1.16.26.1.4.3.1.2,DSMON-MIB::dsmonHostTopNCtlHostIndex,Integer32,read-create,,current,,The dsmonHostTable for which a top N report will be prepared on behalf of this entry. The dsmonHostTable is identified by the value of the dsmonHostCtlIndex for that table - that value is used here to identify the particular table. This object MUST NOT be modified if the associated dsmonHostTopNCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.3.1.3,DSMON-MIB::dsmonHostTopNCtlRateBase,INTEGER,read-create,,current,dsmonHostTopNInPkts(1):dsmonHostTopNInOctets(2):dsmonHostTopNOutPkts(3):dsmonHostTopNOutOctets(4):dsmonHostTopNTotalPkts(5):dsmonHostTopNTotalOctets(6):dsmonHostTopNInHCPkts(7):dsmonHostTopNInHCOctets(8):dsmonHostTopNOutHCPkts(9):dsmonHostTopNOutHCOctets(10):dsmonHostTopNTotalHCPkts(11):dsmonHostTopNTotalHCOctets(12),The variable(s) for each dsmonHost that the dsmonHostTopNRate and dsmonHostTopNHCRate variables are based upon. Each dsmonHostTopN report generated on behalf of this control entry will be ranked in descending order, based on the associated dsmonHostTable counter(s), identified by this object. The following table identifies the dsmonHostTable counters associated with each enumeration: Enumeration RateBase MIB Objects ----------- -------------------- dsmonHostTopNInPkts dsmonHostInPkts dsmonHostTopNInOctets dsmonHostInOctets dsmonHostTopNOutPkts dsmonHostOutPkts dsmonHostTopNOutOctets dsmonHostOutOctets dsmonHostTopNTotalPkts dsmonHostInPkts + dsmonHostOutPkts dsmonHostTopNTotalOctets dsmonHostInOctets + dsmonHostOutOctets dsmonHostTopNInHCPkts dsmonHostInHCPkts dsmonHostTopNInHCOctets dsmonHostInHCOctets dsmonHostTopNOutHCPkts dsmonHostOutHCPkts dsmonHostTopNOutHCOctets dsmonHostOutHCPkts dsmonHostTopNTotalHCPkts dsmonHostInHCPkts + dsmonHostOutHCPkts dsmonHostTopNTotalHCOctets dsmonHostInHCOctets + dsmonHostOutHCOctets The following enumerations are only available if the agent supports High Capacity monitoring: dsmonHostTopNInHCPkts dsmonHostTopNInHCOctets dsmonHostTopNOutHCPkts dsmonHostTopNOutHCOctets dsmonHostTopNTotalHCPkts dsmonHostTopNTotalHCOctets It is an implementation-specific matter whether an agent can detect an overflow condition resulting from the addition of two counter delta values for the following enumerations: dsmonHostTopNTotalPkts dsmonHostTopNTotalOctets dsmonHostTopNTotalHCPkts dsmonHostTopNTotalHCOctets In the event such an overflow condition can be detected by the agent, the associated dsmonHostTopNRate, dsmonHostTopNRateOvfl, and/or dsmonHostTopNHCRate objects should be set to their maximum value. This object MUST NOT be modified if the associated dsmonHostTopNCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.4.3.1.4,DSMON-MIB::dsmonHostTopNCtlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, and is immediately loaded into the associated dsmonHostTopNCtlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of dsmonHostTopNCtlTimeRemaining. Thus the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the dsmonHostTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the dsmonHostTopNTable shall be deleted.
.1.3.6.1.2.1.16.26.1.4.3.1.5,DSMON-MIB::dsmonHostTopNCtlGeneratedReports,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.26.1.4.3.1.6,DSMON-MIB::dsmonHostTopNCtlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated dsmonHostTopNCtlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the dsmonHostTopNCtlTimeRemaining is set. This value shall be zero if no reports have been requested for this dsmonHostTopNCtlEntry.
.1.3.6.1.2.1.16.26.1.4.3.1.7,DSMON-MIB::dsmonHostTopNCtlRequestedSize,Integer32,read-create,,current,,The maximum number of dsmonHost entries requested for this report. When this object is created or modified, the probe SHOULD set dsmonHostTopNCtlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.26.1.4.3.1.8,DSMON-MIB::dsmonHostTopNCtlGrantedSize,Integer32,read-only,,current,,The maximum number of dsmonHost entries in this report. When the associated dsmonHostTopNCtlRequestedSize object is created or modified, the probe SHOULD set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe MUST NOT lower this value except as a result of a set to the associated dsmonHostTopNCtlRequestedSize object. Protocol entries with the highest value of dsmonHostTopNRate or dsmonHostTopNHCRate (depending on the value of the associated dsmonHostTopNCtlRateBase object) shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more dsmonHost entries.
.1.3.6.1.2.1.16.26.1.4.3.1.9,DSMON-MIB::dsmonHostTopNCtlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated dsmonHostTopNCtlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine if a report was missed or not.
.1.3.6.1.2.1.16.26.1.4.3.1.10,DSMON-MIB::dsmonHostTopNCtlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.4.3.1.11,DSMON-MIB::dsmonHostTopNCtlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this dsmonHostTopNCtlEntry. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonHostTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.26.1.4.4,DSMON-MIB::dsmonHostTopNTable,,not-accessible,,current,,A set of statistics for those dsmonHost entries that have counted the highest number of octets or packets. If the dsmonAggControlLocked object is equal to 'false', then all entries in this table SHALL be deleted, and the agent will not process TopN reports on behalf of any dsmonHostTopNCtlEntry. When the dsmonAggControlLocked object is set to 'true', then particular reports SHOULD be restarted from the beginning, on behalf of all active rows in the dsmonHostTopNCtlTable. Note that dsmonHost entries which did not increment at all during the report interval SHOULD NOT be included in dsmonHostTopN reports.
.1.3.6.1.2.1.16.26.1.4.4.1,DSMON-MIB::dsmonHostTopNEntry,,not-accessible,dsmonHostTopNCtlIndex:dsmonHostTopNIndex,current,,A conceptual row in the dsmonHostTopNTable. The dsmonHostTopNCtlIndex value in the index identifies the dsmonHostTopNCtlEntry on whose behalf this entry was created. Entries in this table are ordered from 1 to 'N', where lower numbers represent higher values of the rate base object, over the report interval.
.1.3.6.1.2.1.16.26.1.4.4.1.1,DSMON-MIB::dsmonHostTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the dsmonHostTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report.
.1.3.6.1.2.1.16.26.1.4.4.1.2,DSMON-MIB::dsmonHostTopNPDLocalIndex,Integer32,read-only,,current,,The protocolDirLocalIndex value which identifies the protocol associated with the dsmonHostTopNAddress object in this entry. If the protocolDirEntry associated with the protocolDirLocalIndex with the same value as this object is de-activated or deleted, then the agent MUST delete this dsmonHostTopN entry.
.1.3.6.1.2.1.16.26.1.4.4.1.3,DSMON-MIB::dsmonHostTopNAddress,OCTET,read-only,,current,,The dsmonHostAddress value for the network host identified in this entry. The associated dsmonHostTopNPDLocalIndex object identifies the network protocol type and the encoding rules for this object.
.1.3.6.1.2.1.16.26.1.4.4.1.4,DSMON-MIB::dsmonHostTopNAggGroup,Integer32,read-only,,current,,The counter aggregation group index value associated with host identified in this entry. This object identifies the dsmonAggGroupEntry with the same dsmonAggControlIndex value as the associated dsmonHostCtlAggProfile object and the same dsmonAggGroupIndex value as this object.
.1.3.6.1.2.1.16.26.1.4.4.1.5,DSMON-MIB::dsmonHostTopNRate,Gauge32,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this host's instance of the object selected by dsmonHostTopNCtlRateBase. If the associated dsmonHostTopNCtlRateBase indicates a High Capacity monitoring enumeration, (e.g. 'dsmonHostTopNInHCPkts'), then this object will contain the the least significant 32 bits of the associated dsmonHostTopNHCRate object.
.1.3.6.1.2.1.16.26.1.4.4.1.6,DSMON-MIB::dsmonHostTopNRateOvfl,Gauge32,read-only,,deprecated,,The most significant 32 bits of the associated dsmonHostTopNHCRate object. If the associated dsmonHostTopNCtlRateBase is equal to any of the High Capacity monitoring enumerations (e.g. 'dsmonHostTopNInHCPkts'), then this object will contain the upper 32 bits of the associated dsmonHostTopNHCRate object. If the associated dsmonHostTopNCtlRateBase is not equal to any of High Capacity monitoring enumerations, then this object will contain the value zero. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.4.4.1.7,DSMON-MIB::dsmonHostTopNHCRate,Counter64,read-only,,current,,The amount of change in the selected variable during this sampling interval. The selected variable is this host's instance of the object selected by dsmonHostTopNCtlRateBase. If the associated dsmonHostTopNCtlRateBase is not equal to any of the High Capacity monitoring enumerations (e.g., 'dsmonHostTopNInPkts'), then this object will contain the value zero, and the associated dsmonHostTopNRate object will contain the change in the selected variable during the sampling interval. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.5,DSMON-MIB::dsmonCapsObjects,,,,,,
.1.3.6.1.2.1.16.26.1.5.1,DSMON-MIB::dsmonCapabilities,BITS,read-only,,current,dsmonCounterAggControl(0):dsmonStats(1):dsmonStatsOvfl(2):dsmonStatsHC(3):dsmonPdist(4):dsmonPdistOvfl(5):dsmonPdistHC(6):dsmonHost(7):dsmonHostOvfl(8):dsmonHostHC(9):dsmonCaps(10):dsmonMatrix(11):dsmonMatrixOvfl(12):dsmonMatrixHC(13),This object provides an indication of the DSMON groups supported by the agent. If a bit is set, then the agent implements all of the objects in the DSMON object group, where bit 'n' represents the MIB group identified by the OBJECT IDENTIFIER value { dsmonGroups n+1 }.
.1.3.6.1.2.1.16.26.1.6,DSMON-MIB::dsmonMatrixObjects,,,,,,
.1.3.6.1.2.1.16.26.1.6.1,DSMON-MIB::dsmonMatrixCtlTable,,not-accessible,,current,,Controls setup of per counter aggregation group, per host- pair, application protocol distribution statistics. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.6.1.1,DSMON-MIB::dsmonMatrixCtlEntry,,not-accessible,dsmonMatrixCtlIndex,current,,A conceptual row in the dsmonMatrixCtlTable. Entries are created and deleted from this table by management action only, using the dsmonMatrixCtlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonMatrixSDTable and dsmonMatrixDSTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.6.1.1.1,DSMON-MIB::dsmonMatrixCtlIndex,Integer32,not-accessible,,current,,An arbitrary and unique index for this dsmonMatrixCtlEntry.
.1.3.6.1.2.1.16.26.1.6.1.1.2,DSMON-MIB::dsmonMatrixCtlDataSource,OBJECT,read-create,,current,,The source of data for the associated dsmonMatrixSDTable and dsmonMatrixDSTable. Note that only packets that contain a network protocol encapsulation which contains a DS field [RFC2474] will be counted in this table. This object MUST NOT be modified if the associated dsmonMatrixCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.6.1.1.3,DSMON-MIB::dsmonMatrixCtlAggProfile,Integer32,read-create,,current,,The dsmonAggControlIndex value identifying the counter aggregation profile which should be used on behalf of this dsmonMatrixCtlEntry. The associated dsmonAggControlEntry and dsmonAggProfileEntries, identified by the same dsmonAggControlIndex index value, MUST be active in order for this entry to remain active. It is possible for the counter aggregation configuration to change from a valid to invalid state for this dsmonMatrix collection. In this case, the associated dsmonMatrixCtlStatus object will be changed to the 'notReady' state, and data collection will not occur on behalf of this control entry. Note that an agent MAY choose to limit the actual number of counter aggregation profiles which may be applied to a particular data source. This object MUST NOT be modified if the associated dsmonMatrixCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.6.1.1.4,DSMON-MIB::dsmonMatrixCtlMaxDesiredEntries,Integer32,read-create,,current,,The maximum number of entries that are desired in the dsmonMatrix tables on behalf of this control entry. The probe will not create more than this number of associated entries in these tables, but may choose to create fewer entries in this table for any reason including the lack of resources. If this value is set to -1, the probe may create any number of entries in this table. This object MUST NOT be modified if the associated dsmonMatrixCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.6.1.1.5,DSMON-MIB::dsmonMatrixCtlDroppedFrames,Counter32,read-only,,current,,The total number of frames which were received by the probe and therefore not accounted for in the *StatsDropEvents, but for which the probe chose not to count for the associated dsmonMatrixSD and dsmonMatrixDS entries for whatever reason. Most often, this event occurs when the probe is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the dsmonMatrix tables are inactive because no appropriate protocols are enabled in the protocol directory, this value SHOULD be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.26.1.6.1.1.6,DSMON-MIB::dsmonMatrixCtlInserts,Counter32,read-only,,current,,The number of times a dsmonMatrix entry has been inserted into the dsmonMatrix tables. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the dsmonMatrixSDTable and dsmonMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the sum of the dsmonMatrixSDTable and dsmonMatrixDSTable sizes can be determined by subtracting dsmonMatrixCtlDeletes from dsmonMatrixCtlInserts.
.1.3.6.1.2.1.16.26.1.6.1.1.7,DSMON-MIB::dsmonMatrixCtlDeletes,Counter32,read-only,,current,,The number of times a dsmonMatrix entry has been deleted from the dsmonMatrix tables (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the dsmonMatrixSDTable and dsmonMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents MAY delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the sum of the dsmonMatrixSDTable and dsmonMatrixDSTable sizes can be determined by subtracting dsmonMatrixCtlDeletes from dsmonMatrixCtlInserts.
.1.3.6.1.2.1.16.26.1.6.1.1.8,DSMON-MIB::dsmonMatrixCtlCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this control entry was last activated. This can be used by the management station to detect if the table has been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.6.1.1.9,DSMON-MIB::dsmonMatrixCtlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.6.1.1.10,DSMON-MIB::dsmonMatrixCtlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this dsmonMatrixCtlEntry. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonMatrixSDTable and dsmonMatrixDSTable shall be deleted.
.1.3.6.1.2.1.16.26.1.6.2,DSMON-MIB::dsmonMatrixSDTable,,not-accessible,,current,,A list of application traffic matrix entries which collect statistics for conversations of a particular application protocol between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all statistics from a particular address. The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors.
.1.3.6.1.2.1.16.26.1.6.2.1,DSMON-MIB::dsmonMatrixSDEntry,,not-accessible,dsmonMatrixCtlIndex:dsmonMatrixTimeMark:dsmonAggGroupIndex:dsmonMatrixNLIndex:dsmonMatrixSourceAddress:dsmonMatrixDestAddress:dsmonMatrixALIndex,current,,A conceptual row in the dsmonMatrixSDTable. The dsmonMatrixCtlIndex value in the index identifies the dsmonMatrixCtlEntry on whose behalf this entry was created. The dsmonAggGroupIndex value in the index is determined by examining the DSCP value in each monitored packet, and the dsmonAggProfileTable entry configured for that value.
.1.3.6.1.2.1.16.26.1.6.2.1.1,DSMON-MIB::dsmonMatrixTimeMark,TimeTicks,not-accessible,,current,,The Time Filter index for this table. This object may be used by a management station to retrieve only rows which have been created or modified since a particular time. Note that the current value for a row are always returned and the TimeFilter is not a historical data archiving mechanism. Refer to RFC 2021 [RFC2021] for a detailed description of TimeFilter operation.
.1.3.6.1.2.1.16.26.1.6.2.1.2,DSMON-MIB::dsmonMatrixNLIndex,Integer32,not-accessible,,current,,The protocolDirLocalIndex value of a protocolDirEntry representing the specific network layer protocol encapsulation associated with each entry, and the network protocol type of the dsmonMatrixSourceAddress and dsmonMatrixDestAddress objects.
.1.3.6.1.2.1.16.26.1.6.2.1.3,DSMON-MIB::dsmonMatrixSourceAddress,OCTET,not-accessible,,current,,The network source address for this dsmonMatrix entry. This is represented as an octet string with specific semantics and length as identified by the dsmonMatrixNLIndex component of the index. For example, if the dsmonMatrixNLIndex indicates an encapsulation of IPv4, this object is encoded as a length octet of 4, followed by the 4 octets of the IPv4 address, in network byte order.
.1.3.6.1.2.1.16.26.1.6.2.1.4,DSMON-MIB::dsmonMatrixDestAddress,OCTET,not-accessible,,current,,The network destination address for this dsmonMatrix entry. This is represented as an octet string with specific semantics and length as identified by the dsmonMatrixNLIndex component of the index. For example, if the dsmonMatrixNLIndex indicates an encapsulation of IPv4, this object is encoded as a length octet of 4, followed by the 4 octets of the IPv4 address, in network byte order.
.1.3.6.1.2.1.16.26.1.6.2.1.5,DSMON-MIB::dsmonMatrixALIndex,Integer32,not-accessible,,current,,The protocolDirLocalIndex value of the protocolDirEntry representing the specific application layer protocol associated with each entry. It MUST identify an protocolDirEntry which is a direct or indirect descendant of the protocolDirEntry identified by the associated dsmonMatrixNLIndex object.
.1.3.6.1.2.1.16.26.1.6.2.1.6,DSMON-MIB::dsmonMatrixSDPkts,Gauge32,read-only,,current,,The number of packets of this protocol type (indicated by the associated dsmonMatrixALIndex object) without errors transmitted from the source address to the destination address since this entry was added to the dsmonMatrixSDTable. Note that this is the number of link- layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.26.1.6.2.1.7,DSMON-MIB::dsmonMatrixSDOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonMatrixSDPkts counter has overflowed, since this entry was added to the dsmonMatrixSDTable.
.1.3.6.1.2.1.16.26.1.6.2.1.8,DSMON-MIB::dsmonMatrixSDHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonMatrixSDPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.6.2.1.9,DSMON-MIB::dsmonMatrixSDOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type transmitted from the source address to the destination address since this entry was added to the dsmonMatrixSDTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.26.1.6.2.1.10,DSMON-MIB::dsmonMatrixSDOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonMatrixSDOctets counter has overflowed, since this entry was added to the dsmonMatrixSDTable.
.1.3.6.1.2.1.16.26.1.6.2.1.11,DSMON-MIB::dsmonMatrixSDHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonMatrixSDPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.6.2.1.12,DSMON-MIB::dsmonMatrixSDCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.6.3,DSMON-MIB::dsmonMatrixDSTable,,not-accessible,,current,,A list of application traffic matrix entries which collect statistics for conversations of a particular application protocol between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all statistics from a particular address. The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors.
.1.3.6.1.2.1.16.26.1.6.3.1,DSMON-MIB::dsmonMatrixDSEntry,,not-accessible,dsmonMatrixCtlIndex:dsmonMatrixTimeMark:dsmonAggGroupIndex:dsmonMatrixNLIndex:dsmonMatrixDestAddress:dsmonMatrixSourceAddress:dsmonMatrixALIndex,current,,A conceptual row in the dsmonMatrixDSTable. Note that this table is conceptually a re-ordered version of the dsmonMatrixSDTable. Therefore, all of the index values from that table are used by reference, and their semantics are exactly as described in the dsmonMatrixSDTable. The dsmonMatrixCtlIndex value in the index identifies the dsmonMatrixCtlEntry on whose behalf this entry was created. The dsmonMatrixTimeMark value in the index identifies the Time Filter index for this table. The dsmonAggGroupIndex value in the index is determined by examining the DSCP value in each monitored packet, and the dsmonAggProfileTable entry configured for that value. The dsmonMatrixNLIndex value in the index identifies the protocolDirLocalIndex value of a protocolDirEntry representing the specific network layer protocol encapsulation associated with each entry, and the network protocol type of the dsmonMatrixSourceAddress and dsmonMatrixDestAddress objects. The dsmonMatrixDestAddress value in the index identifies the network destination address for this dsmonMatrix entry. The dsmonMatrixSourceAddress value in the index identifies the network source address for this dsmonMatrix entry. The dsmonMatrixALIndex value in the index identifies the protocolDirLocalIndex value of the protocolDirEntry representing the specific application layer protocol associated with each entry.
.1.3.6.1.2.1.16.26.1.6.3.1.1,DSMON-MIB::dsmonMatrixDSPkts,Gauge32,read-only,,current,,The number of packets of this protocol type (indicated by the associated dsmonMatrixALIndex object) without errors transmitted from the source address to the destination address since this entry was added to the dsmonMatrixDSTable. Note that this is the number of link- layer packets, so if a single network-layer packet is fragmented into several link-layer frames, this counter is incremented several times.
.1.3.6.1.2.1.16.26.1.6.3.1.2,DSMON-MIB::dsmonMatrixDSOvflPkts,Gauge32,read-only,,deprecated,,The number of times the associated dsmonMatrixDSPkts counter has overflowed, since this entry was added to the dsmonMatrixDSTable.
.1.3.6.1.2.1.16.26.1.6.3.1.3,DSMON-MIB::dsmonMatrixDSHCPkts,Counter64,read-only,,current,,The 64-bit version of the dsmonMatrixDSPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.6.3.1.4,DSMON-MIB::dsmonMatrixDSOctets,Gauge32,read-only,,current,,The number of octets in packets of this protocol type transmitted from the source address to the destination address since this entry was added to the dsmonMatrixDSTable (excluding framing bits but including FCS octets), excluding those octets in packets that contained errors. Note this doesn't count just those octets in the particular protocol frames, but includes the entire packet that contained the protocol.
.1.3.6.1.2.1.16.26.1.6.3.1.5,DSMON-MIB::dsmonMatrixDSOvflOctets,Gauge32,read-only,,deprecated,,The number of times the associated dsmonMatrixDSOctets counter has overflowed, since this entry was added to the dsmonMatrixDSTable.
.1.3.6.1.2.1.16.26.1.6.3.1.6,DSMON-MIB::dsmonMatrixDSHCOctets,Counter64,read-only,,current,,The 64-bit version of the dsmonMatrixDSPkts object. Note that this object will only be instantiated if the RMON agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.26.1.6.3.1.7,DSMON-MIB::dsmonMatrixDSCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls.
.1.3.6.1.2.1.16.26.1.6.4,DSMON-MIB::dsmonMatrixTopNCtlTable,,not-accessible,,current,,A set of parameters that control the creation of a report of the top N dsmonMatrix entries according to a selected metric. Note that an agent MAY choose to limit the actual number of entries which may be created in this table. In this case, the agent SHOULD return an error-status of 'resourceUnavailable(13)', as per section 4.2.5 of the 'Protocol Operations for SNMPv2' specification [RFC1905].
.1.3.6.1.2.1.16.26.1.6.4.1,DSMON-MIB::dsmonMatrixTopNCtlEntry,,not-accessible,dsmonMatrixTopNCtlIndex,current,,A conceptual row in the dsmonMatrixTopNCtlTable. Entries are created and deleted from this table by management action only, using the dsmonMatrixTopNCtlStatus RowStatus object. The agent SHOULD support non-volatile configuration of this table, and upon system initialization, the table SHOULD be initialized with the saved values. Activation of a control row in this table will cause an associated dsmonMatrixTopNTable to be created and maintained by the agent.
.1.3.6.1.2.1.16.26.1.6.4.1.1,DSMON-MIB::dsmonMatrixTopNCtlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the dsmonMatrixTopNCtlTable. Each such entry defines one Top N report prepared for one RMON dataSource.
.1.3.6.1.2.1.16.26.1.6.4.1.2,DSMON-MIB::dsmonMatrixTopNCtlMatrixIndex,Integer32,read-create,,current,,The dsmonMatrixSDTable for which a top N report will be prepared on behalf of this entry. The dsmonMatrixSDTable is identified by the same value of the dsmonMatrixCtlIndex object. This object MUST NOT be modified if the associated dsmonMatrixTopNCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.6.4.1.3,DSMON-MIB::dsmonMatrixTopNCtlRateBase,INTEGER,read-create,,current,dsmonMatrixTopNPkts(1):dsmonMatrixTopNOctets(2):dsmonMatrixTopNHCPkts(3):dsmonMatrixTopNHCOctets(4),The variable for each dsmonMatrixSD entry that the dsmonMatrixTopNRate and dsmonMatrixTopNHCRate variables are based upon. Each dsmonMatrixTopN report generated on behalf of this control entry will be ranked in descending order, based on the associated dsmonMatrixSDTable counter, identified by this object. The following table identifies the dsmonMatrixSDTable counters associated with each enumeration: Enumeration RateBase MIB Objects ----------- -------------------- dsmonMatrixTopNPkts dsmonMatrixSDPkts dsmonMatrixTopNOctets dsmonMatrixSDOctets dsmonMatrixTopNHCPkts dsmonMatrixSDHCPkts dsmonMatrixTopNHCOctets dsmonMatrixSDHCOctets The following enumerations are only available if the agent supports High Capacity monitoring: dsmonMatrixTopNHCPkts dsmonMatrixTopNHCOctets This object MUST NOT be modified if the associated dsmonMatrixTopNCtlStatus object is equal to active(1).
.1.3.6.1.2.1.16.26.1.6.4.1.4,DSMON-MIB::dsmonMatrixTopNCtlTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, and is immediately loaded into the associated dsmonMatrixTopNCtlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of dsmonMatrixTopNCtlTimeRemaining. Thus the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the dsmonMatrixTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the dsmonMatrixTopNTable shall be deleted.
.1.3.6.1.2.1.16.26.1.6.4.1.5,DSMON-MIB::dsmonMatrixTopNCtlGeneratedRpts,Counter32,read-only,,current,,The number of reports that have been generated by this entry.
.1.3.6.1.2.1.16.26.1.6.4.1.6,DSMON-MIB::dsmonMatrixTopNCtlDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval. When the associated dsmonMatrixTopNCtlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the dsmonMatrixTopNCtlTimeRemaining is set. This value shall be zero if no reports have been requested for this dsmonMatrixTopNCtlEntry.
.1.3.6.1.2.1.16.26.1.6.4.1.7,DSMON-MIB::dsmonMatrixTopNCtlRequestedSize,Integer32,read-create,,current,,The maximum number of dsmonMatrix entries requested for this report. When this object is created or modified, the probe SHOULD set dsmonMatrixTopNCtlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources.
.1.3.6.1.2.1.16.26.1.6.4.1.8,DSMON-MIB::dsmonMatrixTopNCtlGrantedSize,Integer32,read-only,,current,,The maximum number of dsmonMatrix entries in this report. When the associated dsmonMatrixTopNCtlRequestedSize object is created or modified, the probe SHOULD set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe MUST NOT lower this value except as a result of a set to the associated dsmonMatrixTopNCtlRequestedSize object. Protocol entries with the highest value of dsmonMatrixTopNRate or dsmonMatrixTopNHCRate (depending on the value of the associated dsmonMatrixTopNCtlRateBase object) shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more dsmonMatrix entries.
.1.3.6.1.2.1.16.26.1.6.4.1.9,DSMON-MIB::dsmonMatrixTopNCtlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated dsmonMatrixTopNCtlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine if a report was missed or not.
.1.3.6.1.2.1.16.26.1.6.4.1.10,DSMON-MIB::dsmonMatrixTopNCtlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.26.1.6.4.1.11,DSMON-MIB::dsmonMatrixTopNCtlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this dsmonMatrixTopNCtlEntry. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the dsmonMatrixTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.26.1.6.5,DSMON-MIB::dsmonMatrixTopNTable,,not-accessible,,current,,A set of statistics for those dsmonMatrix entries that have counted the highest number of octets or packets. If the dsmonAggControlLocked object is equal to 'false', then all entries in this table SHALL be deleted, and the agent will not process TopN reports on behalf of any dsmonMatrixTopNCtlEntry. When the dsmonAggControlLocked object is set to 'true', then particular reports SHOULD be restarted from the beginning, on behalf of all active rows in the dsmonMatrixTopNCtlTable. Note that dsmonMatrix entries which did not increment at all during the report interval SHOULD NOT be included in dsmonMatrixTopN reports.
.1.3.6.1.2.1.16.26.1.6.5.1,DSMON-MIB::dsmonMatrixTopNEntry,,not-accessible,dsmonMatrixTopNCtlIndex:dsmonMatrixTopNIndex,current,,A conceptual row in the dsmonMatrixTopNTable. The dsmonMatrixTopNCtlIndex value in the index identifies the dsmonMatrixTopNCtlEntry on whose behalf this entry was created. Entries in this table are ordered from 1 to 'N', where lower numbers represent higher values of the rate base object, over the report interval.
.1.3.6.1.2.1.16.26.1.6.5.1.1,DSMON-MIB::dsmonMatrixTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the dsmonMatrixTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report.
.1.3.6.1.2.1.16.26.1.6.5.1.2,DSMON-MIB::dsmonMatrixTopNAggGroup,Integer32,read-only,,current,,The counter aggregation group index value associated with host identified in this entry. This object identifies the dsmonAggGroupEntry with the same dsmonAggControlIndex value as the associated dsmonMatrixCtlAggProfile object and the same dsmonAggGroupIndex value as this object.
.1.3.6.1.2.1.16.26.1.6.5.1.3,DSMON-MIB::dsmonMatrixTopNNLIndex,Integer32,read-only,,current,,The protocolDirLocalIndex value which identifies the protocol associated with the dsmonMatrixTopNSourceAddress and dsmonMatrixTopNDestAddress objects in this entry. If the protocolDirEntry associated with the protocolDirLocalIndex with the same value as this object is de-activated or deleted, then the agent MUST delete this dsmonMatrixTopN entry.
.1.3.6.1.2.1.16.26.1.6.5.1.4,DSMON-MIB::dsmonMatrixTopNSourceAddress,OCTET,read-only,,current,,The dsmonMatrixSDSourceAddress value for the source network host identified in this entry. The associated dsmonMatrixTopNNLIndex object identifies the network protocol type and the encoding rules for this object.
.1.3.6.1.2.1.16.26.1.6.5.1.5,DSMON-MIB::dsmonMatrixTopNDestAddress,OCTET,read-only,,current,,The dsmonMatrixSDDestAddress value for the destination network host identified in this entry. The associated dsmonMatrixTopNNLIndex object identifies the network protocol type and the encoding rules for this object.
.1.3.6.1.2.1.16.26.1.6.5.1.6,DSMON-MIB::dsmonMatrixTopNALIndex,Integer32,read-only,,current,,The protocolDirLocalIndex value which identifies the application protocol associated with this entry. If the protocolDirEntry associated with the protocolDirLocalIndex with the same value as this object is de-activated or deleted, then the agent MUST delete this dsmonMatrixTopN entry.
.1.3.6.1.2.1.16.26.1.6.5.1.7,DSMON-MIB::dsmonMatrixTopNPktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the dsmonMatrixSDPkts object. If the value of dsmonMatrixTopNCtlRateBase is dsmonMatrixTopNPkts, this variable will be used to sort this report. If the value of the dsmonMatrixTopNCtlRateBase is dsmonMatrixTopNHCPkts or dsmonMatrixTopNHCOctets, then this object will contain the the least significant 32 bits of the associated dsmonMatrixTopNHCPktRate object.
.1.3.6.1.2.1.16.26.1.6.5.1.8,DSMON-MIB::dsmonMatrixTopNPktRateOvfl,Gauge32,read-only,,deprecated,,The most significant 32 bits of the associated dsmonMatrixTopNHCPktRate object. If the associated dsmonMatrixTopNCtlRateBase is equal to dsmonMatrixTopNHCPkts or dsmonMatrixTopNHCOctets, then this object will contain the most significant 32 bits of the associated dsmonMatrixTopNHCPktRate object, otherwise this object will contain the value zero. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.9,DSMON-MIB::dsmonMatrixTopNHCPktRate,Counter64,read-only,,current,,The number of packets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the dsmonMatrixSDHCPkts object. If the value of dsmonMatrixTopNCtlRateBase is dsmonMatrixTopNHCPkts, this variable will be used to sort this report. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.10,DSMON-MIB::dsmonMatrixTopNRevPktRate,Gauge32,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the dsmonMatrixDSPkts object (note that the corresponding dsmonMatrixSDPkts object selected is the one whose source address is equal to dsmonMatrixTopNDestAddress and whose destination address is equal to dsmonMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.26.1.6.5.1.11,DSMON-MIB::dsmonMatrixTopNRevPktRateOvfl,Gauge32,read-only,,deprecated,,The most significant 32 bits of the associated dsmonMatrixTopNHCRevPktRate object. If the associated dsmonMatrixTopNCtlRateBase is equal to dsmonMatrixTopNHCPkts or dsmonMatrixTopNHCOCtets, then this object will contain the most significant 32 bits of the associated dsmonMatrixTopNHCRevPktRate object, otherwise this object will contain the value zero. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.12,DSMON-MIB::dsmonMatrixTopNHCRevPktRate,Counter64,read-only,,current,,The number of packets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the dsmonMatrixDSHCPkts object (note that the corresponding dsmonMatrixSDHCPkts object selected is the one whose source address is equal to dsmonMatrixTopNDestAddress and whose destination address is equal to dsmonMatrixTopNSourceAddress.) The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.13,DSMON-MIB::dsmonMatrixTopNOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the dsmonMatrixSDOctets object. If the value of dsmonMatrixTopNCtlRateBase is dsmonMatrixTopNOctets, this variable will be used to sort this report. If the value of the dsmonMatrixTopNCtlRateBase is dsmonMatrixTopNHCPkts or dsmonMatrixTopNHCOctets, then this object will contain the the least significant 32 bits of the associated dsmonMatrixTopNHCPktRate object.
.1.3.6.1.2.1.16.26.1.6.5.1.14,DSMON-MIB::dsmonMatrixTopNOctetRateOvfl,Gauge32,read-only,,deprecated,,The most significant 32 bits of the associated dsmonMatrixTopNHCOctetRate object. If the associated dsmonMatrixTopNCtlRateBase is equal to dsmonMatrixTopNHCPkts or dsmonMatrixTopNHCOctets, then this object will contain the most significant 32 bits of the associated dsmonMatrixTopNHCOctetRate object, otherwise this object will contain the value zero. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.15,DSMON-MIB::dsmonMatrixTopNHCOctetRate,Counter64,read-only,,current,,The number of octets seen of this protocol from the source host to the destination host during this sampling interval, counted using the rules for counting the dsmonMatrixSDHCOctets object. If the value of dsmonMatrixTopNCtlRateBase is dsmonMatrixTopNHCOctets, this variable will be used to sort this report. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.16,DSMON-MIB::dsmonMatrixTopNRevOctetRate,Gauge32,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the dsmonMatrixDSOctets object (note that the corresponding dsmonMatrixSDOctets object selected is the one whose source address is equal to dsmonMatrixTopNDestAddress and whose destination address is equal to dsmonMatrixTopNSourceAddress.)
.1.3.6.1.2.1.16.26.1.6.5.1.17,DSMON-MIB::dsmonMatrixTopNRevOctetRateOvfl,Gauge32,read-only,,deprecated,,The most significant 32 bits of the associated dsmonMatrixTopNHCRevOctetRate object. If the associated dsmonMatrixTopNCtlRateBase is equal to dsmonMatrixTopNHCPkts or dsmonMatrixTopNHCOCtets, then this object will contain the most significant 32 bits of the associated dsmonMatrixTopNHCRevPktRate object, otherwise this object will contain the value zero. The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.1.6.5.1.18,DSMON-MIB::dsmonMatrixTopNHCRevOctetRate,Counter64,read-only,,current,,The number of octets seen of this protocol from the destination host to the source host during this sampling interval, counted using the rules for counting the dsmonMatrixDSHCOctets object (note that the corresponding dsmonMatrixSDHCOctets object selected is the one whose source address is equal to dsmonMatrixTopNDestAddress and whose destination address is equal to dsmonMatrixTopNSourceAddress.) The agent MAY choose not to instantiate this object if High Capacity monitoring is not supported.
.1.3.6.1.2.1.16.26.2,DSMON-MIB::dsmonNotifications,,,,,,
.1.3.6.1.2.1.16.26.3,DSMON-MIB::dsmonConformance,,,,,,
.1.3.6.1.2.1.16.26.3.1,DSMON-MIB::dsmonCompliances,,,,,,
.1.3.6.1.2.1.16.26.3.1.1,DSMON-MIB::dsmonCompliance,,,,,,Describes the requirements for conformance to the Differentiated Services Monitoring MIB.
.1.3.6.1.2.1.16.26.3.1.2,DSMON-MIB::dsmonHCCompliance,,,,,,Describes the requirements for conformance to the Differentiated Services Monitoring MIB for agents which also support High Capacity monitoring and the Counter64 data type.
.1.3.6.1.2.1.16.26.3.1.3,DSMON-MIB::dsmonHCNoC64Compliance,,,,,,Describes the requirements for conformance to the Differentiated Services Monitoring MIB for an agent which supports high capacity monitoring, but does not support the Counter64 data type (e.g., only supports the SNMPv1 protocol).
.1.3.6.1.2.1.16.26.3.2,DSMON-MIB::dsmonGroups,,,,,,
.1.3.6.1.2.1.16.26.3.2.1,DSMON-MIB::dsmonCounterAggControlGroup,,,,,,A collection of objects used to configure and manage counter aggregation groups for DSMON collection purposes.
.1.3.6.1.2.1.16.26.3.2.2,DSMON-MIB::dsmonStatsGroup,,,,,,A collection of objects providing per DSCP statistics.
.1.3.6.1.2.1.16.26.3.2.3,DSMON-MIB::dsmonStatsOvflGroup,,,,,,A collection of objects providing per-DSCP overflow counters for systems with high capacity data sources, but without support for the Counter64 data type.
.1.3.6.1.2.1.16.26.3.2.4,DSMON-MIB::dsmonStatsHCGroup,,,,,,A collection of objects providing per DSCP statistics for high capacity data sources.
.1.3.6.1.2.1.16.26.3.2.5,DSMON-MIB::dsmonPdistGroup,,,,,,A collection of objects providing per protocol DSCP monitoring extensions to the RMON-2 MIB.
.1.3.6.1.2.1.16.26.3.2.6,DSMON-MIB::dsmonPdistOvflGroup,,,,,,A collection of objects providing per-protocol DSCP overflow counters for systems with high capacity data sources, but without support for the Counter64 data type.
.1.3.6.1.2.1.16.26.3.2.7,DSMON-MIB::dsmonPdistHCGroup,,,,,,A collection of objects providing per protocol DSCP monitoring extensions to the RMON-2 MIB for High Capacity networks.
.1.3.6.1.2.1.16.26.3.2.8,DSMON-MIB::dsmonHostGroup,,,,,,A collection of objects providing per Host monitoring functions.
.1.3.6.1.2.1.16.26.3.2.9,DSMON-MIB::dsmonHostOvflGroup,,,,,,A collection of objects providing per host DSCP overflow counters for systems with high capacity data sources, but without support for the Counter64 data type.
.1.3.6.1.2.1.16.26.3.2.10,DSMON-MIB::dsmonHostHCGroup,,,,,,A collection of objects providing per Host monitoring functions for High Capacity networks.
.1.3.6.1.2.1.16.26.3.2.11,DSMON-MIB::dsmonCapsGroup,,,,,,A collection of objects providing an indication of the DSMON monitoring functions supported by the agent.
.1.3.6.1.2.1.16.26.3.2.12,DSMON-MIB::dsmonMatrixGroup,,,,,,A collection of objects providing per conversation monitoring functions.
.1.3.6.1.2.1.16.26.3.2.13,DSMON-MIB::dsmonMatrixOvflGroup,,,,,,A collection of objects providing per conversation monitoring functions for systems with high capacity data sources, but without support for the Counter64 data type.
.1.3.6.1.2.1.16.26.3.2.14,DSMON-MIB::dsmonMatrixHCGroup,,,,,,A collection of objects providing per conversation monitoring functions for High Capacity networks.
.1.3.6.1.2.1.16.27,INTERFACETOPN-MIB::interfaceTopNMIB,,,,,,The MIB module for sorting device interfaces for RMON and SMON monitoring in a multiple device implementation.
.1.3.6.1.2.1.16.27.1,INTERFACETOPN-MIB::interfaceTopNObjects,,,,,,
.1.3.6.1.2.1.16.27.1.1,INTERFACETOPN-MIB::values,BITS,read-only,,current,ifInOctets(0):ifInUcastPkts(1):ifInNUcastPkts(2):ifInDiscards(3):ifInErrors(4):ifInUnknownProtos(5):ifOutOctets(6):ifOutUcastPkts(7):ifOutNUcastPkts(8):ifOutDiscards(9):ifOutErrors(10):ifInMulticastPkts(11):ifInBroadcastPkts(12):ifOutMulticastPkts(13):ifOutBroadcastPkts(14):ifHCInOctets(15):ifHCInUcastPkts(16):ifHCInMulticastPkts(17):ifHCInBroadcastPkts(18):ifHCOutOctets(19):ifHCOutUcastPkts(20):ifHCOutMulticastPkts(21):ifHCOutBroadcastPkts(22):dot3StatsAlignmentErrors(23):dot3StatsFCSErrors(24):dot3StatsSingleCollisionFrames(25):dot3StatsMultipleCollisionFrames(26):dot3StatsSQETestErrors(27):dot3StatsDeferredTransmissions(28):dot3StatsLateCollisions(29):dot3StatsExcessiveCollisions(30):dot3StatsInternalMacTxErrors(31):dot3StatsCarrierSenseErrors(32):dot3StatsFrameTooLongs(33):dot3StatsInternalMacRxErrors(34):dot3StatsSymbolErrors(35):dot3InPauseFrames(36):dot3OutPauseFrames(37):dot5StatsLineErrors(38):dot5StatsBurstErrors(39):dot5StatsACErrors(40):dot5StatsAbortTransErrors(41):dot5StatsInternalErrors(42):dot5StatsLostFrameErrors(43):dot5StatsReceiveCongestions(44):dot5StatsFrameCopiedErrors(45):dot5StatsTokenErrors(46):dot5StatsSoftErrors(47):dot5StatsHardErrors(48):dot5StatsSignalLoss(49):dot5StatsTransmitBeacons(50):dot5StatsRecoverys(51):dot5StatsLobeWires(52):dot5StatsRemoves(53):dot5StatsSingles(54):dot5StatsFreqErrors(55):etherStatsDropEvents(56):etherStatsOctets(57):etherStatsPkts(58):etherStatsBroadcastPkts(59):etherStatsMulticastPkts(60):etherStatsCRCAlignErrors(61):etherStatsUndersizePkts(62):etherStatsOversizePkts(63):etherStatsFragments(64):etherStatsJabbers(65):etherStatsCollisions(66):etherStatsPkts64Octets(67):etherStatsPkts65to127Octets(68):etherStatsPkts128to255Octets(69):etherStatsPkts256to511Octets(70):etherStatsPkts512to1023Octets(71):etherStatsPkts1024to1518Octets(72):dot1dTpPortInFrames(73):dot1dTpPortOutFrames(74):dot1dTpPortInDiscards(75),The type(s) of sorting capabilities supported by the agent.
.1.3.6.1.2.1.16.27.1.2,INTERFACETOPN-MIB::interfaceTopNControlTable,,not-accessible,,current,,A table of control records for reports on the top `N' interfaces for the value or rate of a selected object. The number of entries depends on the configuration of the agent. The maximum number of entries is implementation dependent.
.1.3.6.1.2.1.16.27.1.2.1,INTERFACETOPN-MIB::interfaceTopNControlEntry,,not-accessible,interfaceTopNControlIndex,current,,A set of parameters that control the creation of a report of the top N ports according to several metrics.
.1.3.6.1.2.1.16.27.1.2.1.1,INTERFACETOPN-MIB::interfaceTopNControlIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the interfaceTopNControl table. Each such entry defines one top N report prepared for a probe.
.1.3.6.1.2.1.16.27.1.2.1.2,INTERFACETOPN-MIB::interfaceTopNObjectVariable,INTEGER,read-create,,current,ifInOctets(0):ifInUcastPkts(1):ifInNUcastPkts(2):ifInDiscards(3):ifInErrors(4):ifInUnknownProtos(5):ifOutOctets(6):ifOutUcastPkts(7):ifOutNUcastPkts(8):ifOutDiscards(9):ifOutErrors(10):ifInMulticastPkts(11):ifInBroadcastPkts(12):ifOutMulticastPkts(13):ifOutBroadcastPkts(14):ifHCInOctets(15):ifHCInUcastPkts(16):ifHCInMulticastPkts(17):ifHCInBroadcastPkts(18):ifHCOutOctets(19):ifHCOutUcastPkts(20):ifHCOutMulticastPkts(21):ifHCOutBroadcastPkts(22):dot3StatsAlignmentErrors(23):dot3StatsFCSErrors(24):dot3StatsSingleCollisionFrames(25):dot3StatsMultipleCollisionFrames(26):dot3StatsSQETestErrors(27):dot3StatsDeferredTransmissions(28):dot3StatsLateCollisions(29):dot3StatsExcessiveCollisions(30):dot3StatsInternalMacTxErrors(31):dot3StatsCarrierSenseErrors(32):dot3StatsFrameTooLongs(33):dot3StatsInternalMacRxErrors(34):dot3StatsSymbolErrors(35):dot3InPauseFrames(36):dot3OutPauseFrames(37):dot5StatsLineErrors(38):dot5StatsBurstErrors(39):dot5StatsACErrors(40):dot5StatsAbortTransErrors(41):dot5StatsInternalErrors(42):dot5StatsLostFrameErrors(43):dot5StatsReceiveCongestions(44):dot5StatsFrameCopiedErrors(45):dot5StatsTokenErrors(46):dot5StatsSoftErrors(47):dot5StatsHardErrors(48):dot5StatsSignalLoss(49):dot5StatsTransmitBeacons(50):dot5StatsRecoverys(51):dot5StatsLobeWires(52):dot5StatsRemoves(53):dot5StatsSingles(54):dot5StatsFreqErrors(55):etherStatsDropEvents(56):etherStatsOctets(57):etherStatsPkts(58):etherStatsBroadcastPkts(59):etherStatsMulticastPkts(60):etherStatsCRCAlignErrors(61):etherStatsUndersizePkts(62):etherStatsOversizePkts(63):etherStatsFragments(64):etherStatsJabbers(65):etherStatsCollisions(66):etherStatsPkts64Octets(67):etherStatsPkts65to127Octets(68):etherStatsPkts128to255Octets(69):etherStatsPkts256to511Octets(70):etherStatsPkts512to1023Octets(71):etherStatsPkts1024to1518Octets(72):dot1dTpPortInFrames(73):dot1dTpPortOutFrames(74):dot1dTpPortInDiscards(75),The particular variable to be sampled. Values between 0 and 22, point to MIB objects defined in IF-MIB [RFC2863]. Values between 23 and 37, point to MIB objects defined in EtherLike-MIB [RFC2665]. Values between 38 and 55, point to MIB objects defined in TOKENRING-MIB [RFC1748]. Values between 56 and 72, point to MIB objects defined in RMON-MIB [RFC2819]. Values between 73 and 75, point to MIB objects defined in BRIDGE-MIB [RFC1493]. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the TopN mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. During a set operation, if the supplied variable name is not available in the selected MIB view, or does not conform the other conditions mentioned above, a badValue error must be returned. This object may not be modified if the associated interfaceTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.27.1.2.1.3,INTERFACETOPN-MIB::interfaceTopNObjectSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2):bandwidthPercentage(3),The method of sampling the selected variable for storage in the interfaceTopNTable. If the value of this object is absoluteValue(1), the value of the selected variable will be copied directly into the topNValue. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference will be stored in topNValue. If the value of this object is bandwidthPercentage(3), the agent records the total number of octets sent over an interval divided by the total number of octets that represent '100% bandwidth' for that interface. This ratio is multiplied by 1000 to retain a 3 digit integer (0..1000) in units of 'tenth of one percent'. This type of computation is accurate for the octet counters. The usage of this option with respect to packets or error counters is not recommended. This object may not be modified if the associated interfaceTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.27.1.2.1.4,INTERFACETOPN-MIB::interfaceTopNNormalizationReq,INTEGER,read-create,,current,true(1):false(2),This object indicates whether normalization is required in the computation of the selected value. If the value of this object is 'true', the value of the selected variable will be multiplied by a factor equal to the interfaceTopNNormalizationFactor divided by the value of effective speed of the interface If the value of this object is 'false', the value of the selected variable will be taken 'as is' in the TopN computation. If the value of the object interfaceTopNSampleType is bandwidthPercentage(3), the object interfaceTopNNormalizationReq cannot take the value 'true'. The value of this object MUST be false if the effective speed of the interface sub-layer as determined from ifSpeed is zero. This conforms to the ifSpeed definition in [RFC2863]for a sub-layer that has no concept of bandwidth. This object may not be modified if the associated interfaceTopNControlStatus object is equal to active(1).
.1.3.6.1.2.1.16.27.1.2.1.5,INTERFACETOPN-MIB::interfaceTopNNormalizationFactor,Integer32,read-create,,current,,The value used for normalization if interfaceTopNNormalizationReq has the value 'true'.
.1.3.6.1.2.1.16.27.1.2.1.6,INTERFACETOPN-MIB::interfaceTopNTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, which is loaded into the associated interfaceTopNDuration object. When this object is set to a non-zero value, any associated interfaceTopNEntries shall be made inaccessible by the agent. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated interfaceTopNEntries shall remain inaccessible. At the time that this object decrements to zero, the report is made accessible in the interfaceTopNTable. Thus, the interfaceTopN table needs to be created only at the end of the collection interval. If the value of this object is set to zero while the associated report is running, the running report is aborted and no associated interfaceTopNEntries are created.
.1.3.6.1.2.1.16.27.1.2.1.7,INTERFACETOPN-MIB::interfaceTopNDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval. When the associated interfaceTopNTimeRemaining object is set, this object shall be set by the agent to the same value and shall not be modified until the next time the interfaceTopNTimeRemaining is set. This value shall be zero if no reports have been requested for this interfaceTopNControlEntry.
.1.3.6.1.2.1.16.27.1.2.1.8,INTERFACETOPN-MIB::interfaceTopNRequestedSize,Integer32,read-create,,current,,The maximum number of interfaces requested for the Top N Table. When this object is created or modified, the agent should set interfaceTopNGrantedSize as close to this object as is possible for the particular implementation and available resources.
.1.3.6.1.2.1.16.27.1.2.1.9,INTERFACETOPN-MIB::interfaceTopNGrantedSize,Integer32,read-only,,current,,The maximum number of interfaces in the top N table. When the associated interfaceTopNRequestedSize object is created or modified, the agent should set this object as closely to the requested value as is possible for the particular implementation and available resources. The agent must not lower this value except as a result of a set to the associated interfaceTopNRequestedSize object.
.1.3.6.1.2.1.16.27.1.2.1.10,INTERFACETOPN-MIB::interfaceTopNStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated interfaceTopNTimeRemaining object was modified to start the requested report. If the report has not yet been started, the value of this object is zero.
.1.3.6.1.2.1.16.27.1.2.1.11,INTERFACETOPN-MIB::interfaceTopNOwner,OCTET,read-create,,current,,The entity that configured this entry and is using the resources assigned to it.
.1.3.6.1.2.1.16.27.1.2.1.12,INTERFACETOPN-MIB::interfaceTopNLastCompletionTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last completed. If no report was yet completed, the value of this object is zero.
.1.3.6.1.2.1.16.27.1.2.1.13,INTERFACETOPN-MIB::interfaceTopNRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. If the value of this object is not equal to active(1), all associated entries in the interfaceTopNTable shall be deleted by the agent.
.1.3.6.1.2.1.16.27.1.3,INTERFACETOPN-MIB::interfaceTopNTable,,not-accessible,,current,,A table of reports for the top `N' ports based on setting of associated control table entries. The maximum number of entries depends on the number of entries in table interfaceTopNControlTable and the value of object interfaceTopNGrantedSize for each entry. For each entry in the interfaceTopNControlTable, interfaces with the highest value of interfaceTopNValue shall be placed in this table in decreasing order of that rate until there is no more room or until there are no more ports.
.1.3.6.1.2.1.16.27.1.3.1,INTERFACETOPN-MIB::interfaceTopNEntry,,not-accessible,interfaceTopNControlIndex:interfaceTopNIndex,current,,A set of statistics for an interface that is part of a top N report.
.1.3.6.1.2.1.16.27.1.3.1.1,INTERFACETOPN-MIB::interfaceTopNIndex,Integer32,not-accessible,,current,,An index that uniquely identifies an entry in the interfaceTopN table among those in the same report. This index is between 1 and N, where N is the number of entries in this report. Increasing values of interfaceTopNIndex shall be assigned to entries with decreasing values of interfaceTopNValue or interfaceTopNValue64, whichever applies, until index N is assigned to the entry with the lowest value of interfaceTopNValue / interfaceTopNValue64 or there are no more interfaceTopNEntries. No ports are included in a report where their value of interfaceTopNValue would be zero.
.1.3.6.1.2.1.16.27.1.3.1.2,INTERFACETOPN-MIB::interfaceTopNDataSourceIndex,Integer32,read-only,,current,,This object identifies the index corresponding to the dataSource for this entry. For sorted values of variables belonging to the IF-MIB, EtherLike-MIB or TOKENRING-MIB, this value equals the ifIndex of the interface. For sorted values of variables belonging to the RMON-MIB, this value equals the interface corresponding to the data source, pointed to by the value of etherStatsDataSource. For sorted values of variables belonging to the BRIDGE-MIB, this value equals the interface corresponding to the bridge port, pointed to by the value of dot1dBasePortIfIndex.
.1.3.6.1.2.1.16.27.1.3.1.3,INTERFACETOPN-MIB::interfaceTopNValue,Gauge32,read-only,,current,,The value at the end of the sampling interval, or the amount of change in the selected variable during this sampling interval for the identified interface. The selected variable is that interfaces's instance of the object selected by interfaceTopNObjectVariable. This value may be normalized if interfaceTopNNormalization required equals 'true'. This value of this object will be computed for all cases when interfaceTopNObjectVariable points to a 32-bit counter or Gauge or when interfaceTopNObjectSampleType equals bandwidthPercentage(3), and will be zero for all other cases.
.1.3.6.1.2.1.16.27.1.3.1.4,INTERFACETOPN-MIB::interfaceTopNValue64,Counter64,read-only,,current,,The value at the end of the sampling interval, or the amount of change in the selected variable during this sampling interval for the identified interface. The selected variable is that interfaces's instance of the object selected by interfaceTopNObjectVariable. This value may be normalized if interfaceTopNNormalization required equals 'true'. This value of this object will be computed for all cases when interfaceTopNObjectVariable points to a 64-bit counter, and will be zero for all other cases.
.1.3.6.1.2.1.16.27.2,INTERFACETOPN-MIB::interfaceTopNNotifications,,,,,,
.1.3.6.1.2.1.16.27.3,INTERFACETOPN-MIB::interfaceTopNConformance,,,,,,
.1.3.6.1.2.1.16.27.3.1,INTERFACETOPN-MIB::interfaceTopNCompliances,,,,,,
.1.3.6.1.2.1.16.27.3.1.1,INTERFACETOPN-MIB::interfaceTopNCompliance,,,,,,Describes the requirements for conformance to the InterfaceTopN MIB.
.1.3.6.1.2.1.16.27.3.2,INTERFACETOPN-MIB::interfaceTopNGroups,,,,,,
.1.3.6.1.2.1.16.27.3.2.1,INTERFACETOPN-MIB::interfaceTopNGroup,,,,,,A collection of objects providing interfaceTopN data for a multiple interfaces device.
.1.3.6.1.2.1.16.28,SSPM-MIB::sspmMIB,,,,,,This SSPM MIB module is applicable to probes implementing Synthetic Source for Performance Monitoring functions. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4149; see the RFC itself for full legal notices.
.1.3.6.1.2.1.16.28.1,SSPM-MIB::sspmMIBObjects,,,,,,
.1.3.6.1.2.1.16.28.1.1,SSPM-MIB::sspmGeneral,,,,,,
.1.3.6.1.2.1.16.28.1.1.1,SSPM-MIB::sspmGeneralClockResolution,Unsigned32,read-only,,current,,A read-only variable indicating the resolution of the measurements possible by this device.
.1.3.6.1.2.1.16.28.1.1.2,SSPM-MIB::sspmGeneralClockMaxSkew,Integer32,read-only,,current,,A read-only variable indicating the maximum offset error due to skew of the local clock over the time interval 86400 seconds, in seconds.
.1.3.6.1.2.1.16.28.1.1.3,SSPM-MIB::sspmGeneralClockSource,Integer32,read-only,,current,,A read-only variable indicating the source of the clock. This is provided to allow a user to determine how accurate the timing mechanism is compared with other devices. This is needed for the coordination of time values between probes for one-way measurements.
.1.3.6.1.2.1.16.28.1.1.4,SSPM-MIB::sspmGeneralMinFrequency,Unsigned32,read-only,,current,,A read-only variable that indicates the devices' capability for the minimum supported sspmSourceFrequency. If sspmSourceFrequency is set to a value lower than the value reported by this attribute, then the set of sspmSourceFrequency will fail with an inconsistent value error.
.1.3.6.1.2.1.16.28.1.1.5,SSPM-MIB::sspmCapabilitiesTable,,not-accessible,,current,,The table of SSPM capabilities.
.1.3.6.1.2.1.16.28.1.1.5.1,SSPM-MIB::sspmCapabilitiesEntry,,not-accessible,sspmCapabilitiesInstance,current,,Details about a particular SSPM capability.
.1.3.6.1.2.1.16.28.1.1.5.1.1,SSPM-MIB::sspmCapabilitiesInstance,Unsigned32,read-only,,current,,Indicates whether SSPM configuration of the corresponding AppLocalIndex is supported by this device. Generally, entries in this table are only made by the device when the configuration of the measurement is available.
.1.3.6.1.2.1.16.28.1.2,SSPM-MIB::sspmSource,,,,,,
.1.3.6.1.2.1.16.28.1.2.1,SSPM-MIB::sspmSourceProfileTable,,not-accessible,,current,,The table of SSPM Source Profiles configured.
.1.3.6.1.2.1.16.28.1.2.1.1,SSPM-MIB::sspmSourceProfileEntry,,not-accessible,sspmSourceProfileInstance,current,,Details about a particular SSPM Source Profile configuration. Entries must exist in this table in order to be referenced by rows in the sspmSourceControlTable.
.1.3.6.1.2.1.16.28.1.2.1.1.1,SSPM-MIB::sspmSourceProfileInstance,Unsigned32,not-accessible,,current,,An arbitrary index.
.1.3.6.1.2.1.16.28.1.2.1.1.2,SSPM-MIB::sspmSourceProfileType,Unsigned32,read-create,,current,,The AppLocalIndex value that uniquely identifies the measurement per the APM-MIB. In order to create a row in this table, there must be a corresponding row in the sspmCapabilitiesTable. When attempting to set this object, if no corresponding row exists in the sspmCapabilitiesTable, then the agent should return a 'badValue' error.
.1.3.6.1.2.1.16.28.1.2.1.1.3,SSPM-MIB::sspmSourceProfilePacketSize,Unsigned32,read-create,,current,,The size of packet to be transmitted in bytes. The size accounts for all data within the IPv4 or IPv6 payloads, excluding the IP headers, IP header options and link-level protocol headers. If the size is set smaller than the minimum allowed packet size or greater than the maximum allowed packet size, then the set should fail, and the agent should return a 'badValue' error.
.1.3.6.1.2.1.16.28.1.2.1.1.4,SSPM-MIB::sspmSourceProfilePacketFillType,INTEGER,read-create,,current,random(1):pattern(2):url(3),Indicates how the packet is filled. 'random' indicates that the packet contains random data patterns. This is probe and implementation dependent. 'pattern' indicates that the pattern defined in the sspmSourceProfilePacketFillValue attribute is used to fill the packet. 'url' indicates that the value of sspmSourceProfilePacketFillValue should contain a URL. The contents of the document at that URL are retrieved when sspmSourceStatus becomes active and utilized in the packet. If the attempt to access that URL fails, then the row status is set to 'notReady', and the set should fail with 'inconsistentValue'. This value must contain a dereferencable URL of the type 'http:', 'https:', or 'ftp:' only.
.1.3.6.1.2.1.16.28.1.2.1.1.5,SSPM-MIB::sspmSourceProfilePacketFillValue,OCTET,read-create,,current,,The string value with which to fill the packet. If sspmSourceProfilePacketFillType is set to 'pattern', then this pattern is repeated until the packet is sspmSourcePacketSize in bytes. Note that if the length of the octet string specified for this value does not divide evenly into the packet size, then an incomplete last copy of this data may be copied into the packet. If the value of sspmSourceProfilePacketFillType is set to 'random', then this attribute is unused. If the value of the sspmSourceProfilePacketFillType is set to 'url', then the URL specified in this attribute is retrieved and used by the probe. In the case of a URL, this value must contain a dereferencable URL of the type 'http:', 'https:', or 'ftp:' only.
.1.3.6.1.2.1.16.28.1.2.1.1.6,SSPM-MIB::sspmSourceProfileTOS,Integer32,read-create,,current,,Represents the TOS field in the IP packet header. The value of this object defaults to zero if not set.
.1.3.6.1.2.1.16.28.1.2.1.1.7,SSPM-MIB::sspmSourceProfileFlowLabel,Integer32,read-create,,current,,This object is used to specify the Flow Label in a IPv6 packet (RFC 2460) to force special handling by the IPv6 routers; e.g., non-default quality-of-service handling. This object is meaningful only when the object sspmSourceDestAddressType is IPv6(2). The value of this object defaults to zero if not set.
.1.3.6.1.2.1.16.28.1.2.1.1.8,SSPM-MIB::sspmSourceProfileLooseSrcRteFill,OCTET,read-create,,current,,In the event that the test should run over a specific route, the intent is to force the route using the Loose Source Route option in IPv4 [RFC791] and IPv6 [RFC2460]. This object contains a series of IP addresses along the path that would be put into the loose source route option in the IP header. The IPv4 addresses are to be listed as 32-bit address values, and the IPv6 addresses are to be listed as a string of 128-bit addresses. The maximum length allowed within the IPv4 source route option is 63 addresses. To simply account for IPv6 addresses as well, the maximum length of the octet string is 240. This allows up to 60 IPv4 addresses or up to 15 IPv6 addresses in the string.
.1.3.6.1.2.1.16.28.1.2.1.1.9,SSPM-MIB::sspmSourceProfileLooseSrcRteLen,Integer32,read-create,,current,,In the event that the test should run over a specific route, the intent is to force the route. This attribute specifies the length of data to be copied from the sspmSourceProfileLooseSrcRteFill into the route data fields of the loose source route options in the IPv4 or IPv6 headers.
.1.3.6.1.2.1.16.28.1.2.1.1.10,SSPM-MIB::sspmSourceProfileTTL,Integer32,read-create,,current,,If non-zero, this specifies the value to place into the TTL field on transmission.
.1.3.6.1.2.1.16.28.1.2.1.1.11,SSPM-MIB::sspmSourceProfileNoFrag,INTEGER,read-create,,current,true(1):false(2),When true, the 'Don't Fragment Bit' should be set on the packet header.
.1.3.6.1.2.1.16.28.1.2.1.1.12,SSPM-MIB::sspmSourceProfile8021Tagging,Integer32,read-create,,current,,IEEE 802.1Q tagging used in IEEE 802.1D bridged environments. A value of -1 indicates that the packets are untagged. A value of 0 to 65535 is the value of the tag to be inserted in the tagged packets. Note that according to IEEE 802.1Q, VLAN-ID tags with a value of 4095 shall not be transmitted on the wire. As the VLAN-ID is encoded in the 12 least significant bits on the tag, values that translate in a binary representation of all 1's in the last 12 bits SHALL NOT be configured. In this case, the set should fail, and return an error-status of 'inconsistentValue'.
.1.3.6.1.2.1.16.28.1.2.1.1.13,SSPM-MIB::sspmSourceProfileUsername,OCTET,read-create,,current,,An optional username used by the application protocol.
.1.3.6.1.2.1.16.28.1.2.1.1.14,SSPM-MIB::sspmSourceProfilePassword,OCTET,read-create,,current,,An optional password used by the application protocol.
.1.3.6.1.2.1.16.28.1.2.1.1.15,SSPM-MIB::sspmSourceProfileParameter,OCTET,read-create,,current,,An optional parameter used by the application protocol. For DNS, this would be the hostname or IP. For HTTP, this would be the URL. For nntp, this would be the news group. For TCP, this would be the port number. For SMTP, this would be the recipient (and could assume the message is predefined).
.1.3.6.1.2.1.16.28.1.2.1.1.16,SSPM-MIB::sspmSourceProfileOwner,OCTET,read-create,,current,,Name of the management station/application that set up the profile.
.1.3.6.1.2.1.16.28.1.2.1.1.17,SSPM-MIB::sspmSourceProfileStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this sspmSourceProfileEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.28.1.2.1.1.18,SSPM-MIB::sspmSourceProfileStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status of this profile. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Once this object is set to active(1), no objects in the sspmSourceProfileTable can be changed.
.1.3.6.1.2.1.16.28.1.2.2,SSPM-MIB::sspmSourceControlTable,,not-accessible,,current,,The table of SSPM measurements configured.
.1.3.6.1.2.1.16.28.1.2.2.1,SSPM-MIB::sspmSourceControlEntry,,not-accessible,sspmSourceControlInstance,current,,Details about a particular SSPM configuration.
.1.3.6.1.2.1.16.28.1.2.2.1.1,SSPM-MIB::sspmSourceControlInstance,Unsigned32,not-accessible,,current,,An arbitrary index.
.1.3.6.1.2.1.16.28.1.2.2.1.2,SSPM-MIB::sspmSourceControlProfile,Integer32,read-create,,current,,A pointer to the profile (sspmSourceProfileEntry) that this control entry uses to define the test being performed.
.1.3.6.1.2.1.16.28.1.2.2.1.3,SSPM-MIB::sspmSourceControlSrc,Integer32,read-create,,current,,The ifIndex where the packet should originate from the probe (if it matters). A value of zero indicates that it does not matter and that the device decides.
.1.3.6.1.2.1.16.28.1.2.2.1.4,SSPM-MIB::sspmSourceControlDestAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address by which the destination is accessed.
.1.3.6.1.2.1.16.28.1.2.2.1.5,SSPM-MIB::sspmSourceControlDestAddr,OCTET,read-create,,current,,The Internet address for the destination. The formatting of this object is controlled by the sspmSourceControlDestAddrType object above. When this object contains a DNS name, then the name is resolved to an address each time measurement is to be made. Further, the agent should not cache this address, but instead should perform the resolution prior to each measurement.
.1.3.6.1.2.1.16.28.1.2.2.1.6,SSPM-MIB::sspmSourceControlEnabled,INTEGER,read-create,,current,true(1):false(2),When set to 'true', this test is enabled. When set to 'false', it is disabled.
.1.3.6.1.2.1.16.28.1.2.2.1.7,SSPM-MIB::sspmSourceControlTimeOut,Unsigned32,read-create,,current,,Timeout value for the measurement response. If no response is received in the time specified, then the test fails.
.1.3.6.1.2.1.16.28.1.2.2.1.8,SSPM-MIB::sspmSourceControlSamplingDist,INTEGER,read-create,,current,deterministic(1):poisson(2),When this attribute is set to 'deterministic', then packets are generated at with a fixed inter-packet injection time specified by sspmSourceFrequency. When this attribute is set to 'Poisson', then packets are generated with inter-packet injection times sampled from an exponential distribution with the single distributional parameter determined by the inverse frequency).
.1.3.6.1.2.1.16.28.1.2.2.1.9,SSPM-MIB::sspmSourceControlFrequency,Unsigned32,read-create,,current,,The inverse of this value is the rate at which packets are generated. Refer to sspmSourceSamplingDistribution. If the value set is less than the value of sspmGeneralMinFrequency, then the set will fail with an error-status of 'inconsistentValue'.
.1.3.6.1.2.1.16.28.1.2.2.1.10,SSPM-MIB::sspmSourceControlFirstSeqNum,Unsigned32,read-create,,current,,The first sequence number of packets to be transmitted.
.1.3.6.1.2.1.16.28.1.2.2.1.11,SSPM-MIB::sspmSourceControlLastSeqNum,Unsigned32,read-only,,current,,The last sequence number transmitted. This value is updated by the agent after packet generation.
.1.3.6.1.2.1.16.28.1.2.2.1.12,SSPM-MIB::sspmSourceControlOwner,OCTET,read-create,,current,,Name of the management station/application that set up the test.
.1.3.6.1.2.1.16.28.1.2.2.1.13,SSPM-MIB::sspmSourceControlStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this sspmSourceControlEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.28.1.2.2.1.14,SSPM-MIB::sspmSourceControlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status of this source control entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. When this attribute has the value of 'active', none of the read-write or read-create attributes in this table may be modified, with the exception of sspmSourceControlEnabled.
.1.3.6.1.2.1.16.28.1.5,SSPM-MIB::sspmSink,,,,,,
.1.3.6.1.2.1.16.28.1.5.1,SSPM-MIB::sspmSinkTable,,not-accessible,,current,,A table configuring the sink for measurements.
.1.3.6.1.2.1.16.28.1.5.1.1,SSPM-MIB::sspmSinkEntry,,not-accessible,sspmSinkInstance,current,,The details of a particular sink entry. If the measurement is a round-trip type, then the sink entry will be on the same probe as the corresponding sspmSourceEntry. If the measurement is a one-way, type then the sink entry will be on a different probe.
.1.3.6.1.2.1.16.28.1.5.1.1.1,SSPM-MIB::sspmSinkInstance,Unsigned32,not-accessible,,current,,An index. When the measurement is for a round-trip measurement, then this table entry is on the same probe as the corresponding sspmSourceEntry, and the value of this attribute should correspond to the value of sspmSourceInstance. Management applications configuring sinks for one-way measurements could define some scheme whereby the sspmSinkInstance is unique across all probes. Note that the unique key to this entry is also constructed with sspmSinkType, sspmSinkSourceAddressType, and sspmSinkSourceAddress. To make the implementation simpler, those other attributes are not included in the index but uniqueness is still needed to receive all the packets.
.1.3.6.1.2.1.16.28.1.5.1.1.2,SSPM-MIB::sspmSinkType,Unsigned32,read-create,,current,,The AppLocalIndex value that uniquely identifies the measurement per the APM-MIB. In order to create a row in this table, there must be a corresponding row in the sspmCapabilitiesTable. If there is no corresponding row in the sspmCapabilitiestable, then the agent will return an error-status of 'inconsistentValue'.
.1.3.6.1.2.1.16.28.1.5.1.1.3,SSPM-MIB::sspmSinkSourceAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address of the source.
.1.3.6.1.2.1.16.28.1.5.1.1.4,SSPM-MIB::sspmSinkSourceAddress,OCTET,read-create,,current,,The Internet address of the source. The formatting of this object is controlled by the sspmSinkSourceAddressType object above. This object should be set only to a valid device address that has been administratively configured into the device. If a set attempts to set this object to an address that does not belong (i.e., is not administratively configured into the device), the set should fail, and the agent should return a error-status of 'inconsistentValue'.
.1.3.6.1.2.1.16.28.1.5.1.1.5,SSPM-MIB::sspmSinkExpectedRate,Unsigned32,read-create,,current,,The expected rate at which packets will arrive.
.1.3.6.1.2.1.16.28.1.5.1.1.6,SSPM-MIB::sspmSinkEnable,INTEGER,read-create,,current,true(1):false(2),Indicates if the sink is enabled or not.
.1.3.6.1.2.1.16.28.1.5.1.1.7,SSPM-MIB::sspmSinkExpectedFirstSequenceNum,Unsigned32,read-create,,current,,The expected first sequence number of packets. This is used by the sink to determine if packets were lost at the initiation of the test.
.1.3.6.1.2.1.16.28.1.5.1.1.8,SSPM-MIB::sspmSinkLastSequenceNumber,Unsigned32,read-only,,current,,The last sequence number received.
.1.3.6.1.2.1.16.28.1.5.1.1.9,SSPM-MIB::sspmSinkLastSequenceInvalid,Counter32,read-only,,current,,The number of packets that arrived whose sequence number was not one plus the value of sspmSinkLastSequenceNumber.
.1.3.6.1.2.1.16.28.1.5.1.1.10,SSPM-MIB::sspmSinkStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this sspmSinkEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.28.1.5.1.1.11,SSPM-MIB::sspmSinkStatus,INTEGER,of,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status of this conceptual row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Once this object is set to active(1), no objects with be changed.
.1.3.6.1.2.1.16.28.2,SSPM-MIB::sspmMIBNotifications,,,,,,
.1.3.6.1.2.1.16.28.3,SSPM-MIB::sspmMIBConformance,,,,,,
.1.3.6.1.2.1.16.28.3.1,SSPM-MIB::sspmCompliances,,,,,,
.1.3.6.1.2.1.16.28.3.1.1,SSPM-MIB::sspmGeneralCompliance,,,,,,A general compliance that allows all things to be optional.
.1.3.6.1.2.1.16.28.3.1.2,SSPM-MIB::sspmSourceFullCompliance,,,,,,A source compliance. Use this compliance when implementing a traffic-source-only device. This is useful for implementing devices that probe other devices for intrusive application monitoring. It is also useful for implementing the source of one-way tests used with a sink-only device.
.1.3.6.1.2.1.16.28.3.1.3,SSPM-MIB::sspmSinkFullCompliance,,,,,,A sink-only compliance. Use this compliance when implementing a sink-only device. This is useful for devices to receive one-way measurements.
.1.3.6.1.2.1.16.28.3.2,SSPM-MIB::sspmGroups,,,,,,
.1.3.6.1.2.1.16.28.3.2.1,SSPM-MIB::sspmGeneralGroup,,,,,,The objects in the SSPM General Group.
.1.3.6.1.2.1.16.28.3.2.2,SSPM-MIB::sspmSourceGroup,,,,,,The objects in the SSPM Source Group.
.1.3.6.1.2.1.16.28.3.2.3,SSPM-MIB::sspmUserPassGroup,,,,,,The objects in the SSPM Username and password group.
.1.3.6.1.2.1.16.28.3.2.4,SSPM-MIB::sspmSinkGroup,,,,,,The objects in the SSPM Sink Group.
.1.3.6.1.2.1.16.29,HC-ALARM-MIB::hcAlarmMIB,,,,,,This module defines Remote Monitoring MIB extensions for High Capacity Alarms. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3434; see the RFC itself for full legal notices.
.1.3.6.1.2.1.16.29.1,HC-ALARM-MIB::hcAlarmObjects,,,,,,
.1.3.6.1.2.1.16.29.1.1,HC-ALARM-MIB::hcAlarmControlObjects,,,,,,
.1.3.6.1.2.1.16.29.1.1.1,HC-ALARM-MIB::hcAlarmTable,,not-accessible,,current,,A list of entries for the configuration of high capacity alarms.
.1.3.6.1.2.1.16.29.1.1.1.1,HC-ALARM-MIB::hcAlarmEntry,,not-accessible,hcAlarmIndex,current,,A conceptual row in the hcAlarmTable. Entries are usually created in this table by management application action, but may also be created by agent action as well.
.1.3.6.1.2.1.16.29.1.1.1.1.1,HC-ALARM-MIB::hcAlarmIndex,Integer32,not-accessible,,current,,An arbitrary integer index value used to uniquely identify this high capacity alarm entry.
.1.3.6.1.2.1.16.29.1.1.1.1.2,HC-ALARM-MIB::hcAlarmInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this variable, care should be taken in the case of deltaValue sampling - the interval should be set short enough that the sampled variable is very unlikely to increase or decrease by more than 2^63 - 1 during a single sampling interval. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.3,HC-ALARM-MIB::hcAlarmVariable,OBJECT,read-create,,current,,The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32, Counter32, Counter64, Gauge, or TimeTicks) may be sampled. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.4,HC-ALARM-MIB::hcAlarmSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is absoluteValue(1), the value of the selected variable will be compared directly with the thresholds at the end of the sampling interval. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds. If the associated hcAlarmVariable instance could not be obtained at the previous sample interval, then a delta sample is not possible, and the value of the associated hcAlarmValueStatus object for this interval will be valueNotAvailable(1). This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.5,HC-ALARM-MIB::hcAlarmAbsValue,Counter64,read-only,,current,,The absolute value (i.e., unsigned value) of the hcAlarmVariable statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed. To obtain the true value for this sampling interval, the associated instance of hcAlarmValueStatus must be checked, and the value of this object adjusted as necessary. If the MIB instance could not be accessed during the sampling interval, then this object will have a value of zero and the associated instance of hcAlarmValueStatus will be set to 'valueNotAvailable(1)'.
.1.3.6.1.2.1.16.29.1.1.1.1.6,HC-ALARM-MIB::hcAlarmValueStatus,INTEGER,read-only,,current,valueNotAvailable(1):valuePositive(2):valueNegative(3),This object indicates the validity and sign of the data for the hcAlarmAbsValue object, as described in the HcValueStatus textual convention.
.1.3.6.1.2.1.16.29.1.1.1.1.7,HC-ALARM-MIB::hcAlarmStartupAlarm,INTEGER,read-create,,current,risingAlarm(1):fallingAlarm(2):risingOrFallingAlarm(3),The alarm that may be sent when this entry is first set to active. If the first sample after this entry becomes active is greater than or equal to the rising threshold and this object is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the falling threshold and this object is equal to fallingAlarm(2) or risingOrFallingAlarm(3), then a single falling alarm will be generated. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.8,HC-ALARM-MIB::hcAlarmRisingThreshAbsValueLo,Unsigned32,read-create,,current,,The lower 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmRisingThreshAbsValueHi and hcAlarmRisingThresholdValStatus objects, as follows: ABS(threshold) = hcAlarmRisingThreshAbsValueLo + (hcAlarmRisingThreshAbsValueHi * 2^^32) The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the rising threshold for this entry. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the threshold identified by the hcAlarmFallingThreshAbsValueLo, hcAlarmFallingThreshAbsValueHi, and hcAlarmFallingThresholdValStatus objects. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.9,HC-ALARM-MIB::hcAlarmRisingThreshAbsValueHi,Unsigned32,read-create,,current,,The upper 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmRisingThreshAbsValueLo and hcAlarmRisingThresholdValStatus objects, as follows: ABS(threshold) = hcAlarmRisingThreshAbsValueLo + (hcAlarmRisingThreshAbsValueHi * 2^^32) The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the rising threshold for this entry. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the threshold identified by the hcAlarmFallingThreshAbsValueLo, hcAlarmFallingThreshAbsValueHi, and hcAlarmFallingThresholdValStatus objects. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.10,HC-ALARM-MIB::hcAlarmRisingThresholdValStatus,INTEGER,read-create,,current,valueNotAvailable(1):valuePositive(2):valueNegative(3),This object indicates the sign of the data for the rising threshold, as defined by the hcAlarmRisingThresAbsValueLo and hcAlarmRisingThresAbsValueHi objects, as described in the HcValueStatus textual convention. The enumeration 'valueNotAvailable(1)' is not allowed, and the associated hcAlarmStatus object cannot be equal to 'active(1)' if this object is set to this value. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.11,HC-ALARM-MIB::hcAlarmFallingThreshAbsValueLo,Unsigned32,read-create,,current,,The lower 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmFallingThreshAbsValueHi and hcAlarmFallingThresholdValStatus objects, as follows: ABS(threshold) = hcAlarmFallingThreshAbsValueLo + (hcAlarmFallingThreshAbsValueHi * 2^^32) The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the falling threshold for this entry. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the threshold identified by the hcAlarmRisingThreshAbsValueLo, hcAlarmRisingThreshAbsValueHi, and hcAlarmRisingThresholdValStatus objects. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.12,HC-ALARM-MIB::hcAlarmFallingThreshAbsValueHi,Unsigned32,read-create,,current,,The upper 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmFallingThreshAbsValueLo and hcAlarmFallingThresholdValStatus objects, as follows: ABS(threshold) = hcAlarmFallingThreshAbsValueLo + (hcAlarmFallingThreshAbsValueHi * 2^^32) The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the falling threshold for this entry. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the threshold identified by the hcAlarmRisingThreshAbsValueLo, hcAlarmRisingThreshAbsValueHi, and hcAlarmRisingThresholdValStatus objects. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.13,HC-ALARM-MIB::hcAlarmFallingThresholdValStatus,INTEGER,read-create,,current,valueNotAvailable(1):valuePositive(2):valueNegative(3),This object indicates the sign of the data for the falling threshold, as defined by the hcAlarmFallingThreshAbsValueLo and hcAlarmFallingThreshAbsValueHi objects, as described in the HcValueStatus textual convention. The enumeration 'valueNotAvailable(1)' is not allowed, and the associated hcAlarmStatus object cannot be equal to 'active(1)' if this object is set to this value. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.14,HC-ALARM-MIB::hcAlarmRisingEventIndex,Integer32,read-create,,current,,The index of the eventEntry that is used when a rising threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.15,HC-ALARM-MIB::hcAlarmFallingEventIndex,Integer32,read-create,,current,,The index of the eventEntry that is used when a falling threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated hcAlarmStatus object is equal to active(1).
.1.3.6.1.2.1.16.29.1.1.1.1.16,HC-ALARM-MIB::hcAlarmValueFailedAttempts,Counter32,read-only,,current,,The number of times the associated hcAlarmVariable instance was polled on behalf of this hcAlarmEntry, (while in the active state) and the value was not available. This counter may experience a discontinuity if the agent restarts, indicated by the value of sysUpTime.
.1.3.6.1.2.1.16.29.1.1.1.1.17,HC-ALARM-MIB::hcAlarmOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it.
.1.3.6.1.2.1.16.29.1.1.1.1.18,HC-ALARM-MIB::hcAlarmStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The type of non-volatile storage configured for this entry. If this object is equal to 'permanent(4)', then the associated hcAlarmRisingEventIndex and hcAlarmFallingEventIndex objects must be writable.
.1.3.6.1.2.1.16.29.1.1.1.1.19,HC-ALARM-MIB::hcAlarmStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value, as described in the description clause for each writable object. The hcAlarmStatus object may be modified if the associated instance of this object is equal to active(1), notInService(2), or notReady(3). All other writable objects may be modified if the associated instance of this object is equal to notInService(2) or notReady(3).
.1.3.6.1.2.1.16.29.1.2,HC-ALARM-MIB::hcAlarmCapabilitiesObjects,,,,,,
.1.3.6.1.2.1.16.29.1.2.1,HC-ALARM-MIB::hcAlarmCapabilities,BITS,read-only,,current,hcAlarmCreation(0):hcAlarmNvStorage(1),An indication of the high capacity alarm capabilities supported by this agent. If the 'hcAlarmCreation' BIT is set, then this agent allows NMS applications to create entries in the hcAlarmTable. If the 'hcAlarmNvStorage' BIT is set, then this agent allows entries in the hcAlarmTable which will be recreated after a system restart, as controlled by the hcAlarmStorageType object.
.1.3.6.1.2.1.16.29.2,HC-ALARM-MIB::hcAlarmNotifications,,,,,,
.1.3.6.1.2.1.16.29.2.0,HC-ALARM-MIB::hcAlarmNotifPrefix,,,,,,
.1.3.6.1.2.1.16.29.2.0.1,HC-ALARM-MIB::hcRisingAlarm,,,,,,The SNMP notification that is generated when a high capacity alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps. The hcAlarmEntry object instances identified in the OBJECTS clause are from the entry that causes this notification to be generated.
.1.3.6.1.2.1.16.29.2.0.2,HC-ALARM-MIB::hcFallingAlarm,,,,,,The SNMP notification that is generated when a high capacity alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps. The hcAlarmEntry object instances identified in the OBJECTS clause are from the entry that causes this notification to be generated.
.1.3.6.1.2.1.16.29.3,HC-ALARM-MIB::hcAlarmConformance,,,,,,
.1.3.6.1.2.1.16.29.3.1,HC-ALARM-MIB::hcAlarmCompliances,,,,,,
.1.3.6.1.2.1.16.29.3.1.1,HC-ALARM-MIB::hcAlarmCompliance,,,,,,Describes the requirements for conformance to the High Capacity Alarm MIB.
.1.3.6.1.2.1.16.29.3.2,HC-ALARM-MIB::hcAlarmGroups,,,,,,
.1.3.6.1.2.1.16.29.3.2.1,HC-ALARM-MIB::hcAlarmControlGroup,,,,,,A collection of objects used to configure entries for high capacity alarm threshold monitoring purposes.
.1.3.6.1.2.1.16.29.3.2.2,HC-ALARM-MIB::hcAlarmCapabilitiesGroup,,,,,,A collection of objects used to indicate an agent's high capacity alarm threshold monitoring capabilities.
.1.3.6.1.2.1.16.29.3.2.3,HC-ALARM-MIB::hcAlarmNotificationsGroup,,,,,,A collection of notifications to deliver information related to a high capacity rising or falling threshold event to a management application.
.1.3.6.1.2.1.16.30,TPM-MIB::tpmMIB,,,,,,This module defines extensions to the RMON2-MIB module for the collection of Performance Metrics related to application traffic in a network. In particular, it describes managed objects used for monitoring selectable performance metrics and statistics derived from the monitoring of network packets and sub-application level transactions. In order to maintain the RMON 'look-and-feel', some of the text from the RMON2 [RFC2021] and HC-RMON [RFC3273] MIBs by Steve Waldbusser have been used in this MIB module. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4150; see the RFC itself for full legal notices.
.1.3.6.1.2.1.16.30.1,TPM-MIB::tpmCapabilities,,,,,,
.1.3.6.1.2.1.16.30.1.1,TPM-MIB::tpmClockResolution,Unsigned32,read-only,,current,,A read-only variable indicating the resolution of the measurements possible by this device.
.1.3.6.1.2.1.16.30.1.2,TPM-MIB::tpmClockMaxSkew,Integer32,read-only,,current,,A read-only variable indicating the maximum offset error due to skew of the local clock over the time interval 86400 seconds, in seconds.
.1.3.6.1.2.1.16.30.1.3,TPM-MIB::tpmClockSource,Integer32,read-only,,current,,A read-only variable indicating the source of the clock. This is provided to allow a user to determine how accurate the timing mechanism is compared with other devices.
.1.3.6.1.2.1.16.30.1.4,TPM-MIB::tpmTransMetricDirLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the tpmTransMetricDirTable was last modified, through modifications of the tpmTransMetricDirConfig object.
.1.3.6.1.2.1.16.30.1.5,TPM-MIB::tpmTransMetricDirTable,,not-accessible,,current,,This table is used to describe and link sets of performance metrics and protocols to an entry in the application directory. This table, with the tpmMetricDefTable, describes the capability of the agent to collection sub-application level data related to each entry in the apmAppDirectoryTable. This table lists the protocol transactions and their corresponding performance metrics that this agent has the capability to compute and collect, for the specified application. There is one entry in this table for each such application, protocol transaction, and metric combination supported by this agent. The entries in this table represent the metrics that are collected for each protocol transaction that comprise the application. The agent should boot up with this table pre-configured with those combinations of applications, protocol transactions, and metrics that it knows about and wishes to monitor. Implementations must populate the table with all possible application, protocol transaction, and metric combinations and have the default configuration objects set to supportedOff(2). This table does not support the creation of new combinations by the management application. The deletion of an entry in the apmAppDirectoryTable will cause the removal of entries from this table. These entries must be removed because the appLocalIndex value will no longer be visible in the apmAppDirectoryTable. When an entry is created in the apmAppDirectoryTable and the agent has the ability to support metrics for these protocol transactions, the appropriate entries must be made in the tpmTransMetricDefTable.
.1.3.6.1.2.1.16.30.1.5.1,TPM-MIB::tpmTransMetricDirEntry,,not-accessible,tpmTransMetricAppLocalIndex:tpmTransMetricIndex,current,,A conceptual row in the tpmTransMetricDirTable. An example of the indexing of this entry is tpmTransMetricDirConfig.5.2 where 5 is the value of a valid and visible appLocalIndex object in the appLocalDir table. The entries describe the transaction and metric pairs monitored for this application. The tpmTransMetricProtocolIndex identifies the protocol transaction and the tpmMetricDefIndex describes the metric monitored.
.1.3.6.1.2.1.16.30.1.5.1.1,TPM-MIB::tpmTransMetricAppLocalIndex,Unsigned32,not-accessible,,current,,An index used to uniquely identify the application with which the entries in the tpmTransMetricDir table are associated.
.1.3.6.1.2.1.16.30.1.5.1.2,TPM-MIB::tpmTransMetricIndex,Unsigned32,not-accessible,,current,,An index used to uniquely identify an entry in the tpmTransMetricDir table. Each such entry defines protocol transaction and metric instance to be monitored for a specific application.
.1.3.6.1.2.1.16.30.1.5.1.3,TPM-MIB::tpmTransMetricProtocolIndex,Unsigned32,read-only,,current,,The protocolDirLocalIndex of the particular transaction to be analyzed when computing and generating the selected metric for a specific application.
.1.3.6.1.2.1.16.30.1.5.1.4,TPM-MIB::tpmTransMetricMetricIndex,Unsigned32,read-only,,current,,The tpmMetricDefinitionID of the particular metric to be generated.
.1.3.6.1.2.1.16.30.1.5.1.5,TPM-MIB::tpmTransMetricDirConfig,INTEGER,read-write,,current,notSupported(1):supportedOff(2):supportedOn(3),This object describes and configures the probe's support for this performance metric in relationship to the specified transaction and application. The agent creates entries in this table for all metric and transaction combinations that it can generate. Because the probe will only populate this table with supported entries, and the table cannot have entries added, the notSupported(1) setting is only used to signify that other configuration parameters are causing the agent currently not to support the generation and collection of this metric for the specified protocol and application. Also, the status of this object will not change to notSupported(1) due to a change to supportedOff(2) in the tpmMetricDir table. If the value of this object is notSupported(1), the probe will not perform computations for this performance metric and transaction combination and will not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports computations for this performance metric and protocol and is configured to perform the computations for this performance metric and protocol combination for the application for all interfaces. If the value of this object is supportedOff(2), the probe supports computations for this performance metric for the specified protocol, but is configured not to perform the computations for this performance metric and protocol for the application for any interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall cause the deletion of all entries in the tpmReportGroup tables, for all appropriate studies configured in the tpmAggrReportCntrlTable. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.30.1.6,TPM-MIB::tpmMetricDefTable,,not-accessible,,current,,The tpmMetricDefTable describes the metrics available to the TPM-MIB. The tpmMetricDefTable can define metrics by referencing existing IETF, ITU, and other standards organizations' documents, including enterprise-specific documents. Examples of appropriate references include the ITU-T Recommendation Y.1540 [Y.1540] on IP packet transfer performance metrics and the IETF documents from the IPPM WG; e.g., RFC2681 on the round trip delay metric [RFC2681] or RFC3393 on the delay variation metric [RFC3393]. Other examples include RFC2679 [RFC2679], RFC2680 [RFC2680], and RFC3432 [RFC3432]. Although no specific metric is mandatory, implementations should, at a minimum, support a round-trip delay and a round-trip loss metric. This table contains one row per metric supported by this agent, and it should be populated during system initialization.
.1.3.6.1.2.1.16.30.1.6.1,TPM-MIB::tpmMetricDefEntry,,not-accessible,tpmMetricDefinitionID,current,,Information about a particular metric.
.1.3.6.1.2.1.16.30.1.6.1.1,TPM-MIB::tpmMetricDefinitionID,Unsigned32,not-accessible,,current,,The index for this entry. This object identifies the particular metric in this MIB module.
.1.3.6.1.2.1.16.30.1.6.1.2,TPM-MIB::tpmMetricDefType,INTEGER,read-only,,current,other(1):connectMetric(2):delayMetric(3):lossMetric(4),The basic type of metric indicated by this entry. The value 'other(1)' indicates that this metric cannot be characterized by any of the remaining enumerations specified for this object. The value 'connectMetric(2)' indicates that this metric measures connectivity characteristics. The value 'delayMetric(3)' indicates that this metric measures delay characteristics. The value 'lossMetric(4)' indicates that this metric measures loss characteristics.
.1.3.6.1.2.1.16.30.1.6.1.3,TPM-MIB::tpmMetricDefDirType,INTEGER,read-only,,current,oneWay(1):twoWay(2):multiWay(3),The directional characteristics of the this metric. The value 'oneWay(1)' indicates that this metric is measured with some sort of unidirectional test. The value 'twoWay(2)' indicates that this metric is measured with some sort of bidirectional test. The value 'multiWay(3)' indicates that this metric is measured with some combination of unidirectional and/or bidirectional tests.
.1.3.6.1.2.1.16.30.1.6.1.4,TPM-MIB::tpmMetricDefName,OCTET,read-only,,current,,The textual name of this metric. For example, if this tpmMetricDefEntry identified the IPPM metric for round trip delay, then this object should contain the value, e.g., 'Type-P-Round-Trip-Delay'.
.1.3.6.1.2.1.16.30.1.6.1.5,TPM-MIB::tpmMetricDefReference,OCTET,read-only,,current,,This object contains a reference to the document that defines this metric. If this document is available online via electronic download, then a de-referencable URL should be specified in this object. The implementation must support an HTTP URL type and may support additional types of de-referencable URLs such as an FTP type. For example, if this tpmMetricDefName identified the IPPM metric 'Type-P-Round-Trip-Delay', then this object should contain the value, e.g., 'http://www.ietf.org/rfc/rfc2681.txt'.
.1.3.6.1.2.1.16.30.1.6.1.6,TPM-MIB::tpmMetricDefGlobalID,OBJECT,read-only,,current,,This object contains a reference to the Object ID in a metrics registration MIB being developed in the IPPM WG at the IETF; e.g., the IPPM-REGISTRY-MIB [RFC4148], which defines the metric. In the event that this metric has no corresponding object identifier (OID) or until the IPPM-REGISTRY-MIB is defined, then the value should be set to 0.0 for none.
.1.3.6.1.2.1.16.30.2,TPM-MIB::tpmReports,,,,,,
.1.3.6.1.2.1.16.30.2.1,TPM-MIB::tpmAggrReportCntrlTable,,not-accessible,,current,,The tpmAggrReportCntrlTable is the controlling entry that manages the population of studies in the Transport Aggregate Report for selected interfaces, metrics, and transaction protocols and applications. Note that this is not like the typical RMON controlTable and dataTable in which each entry creates its own data table. Each entry in this table enables the creation of multiple data tables on a study basis. For each interval, the study is updated in place, and the current data content of the table becomes invalid. The control table entries are persistent across system reboots.
.1.3.6.1.2.1.16.30.2.1.1,TPM-MIB::tpmAggrReportCntrlEntry,,not-accessible,tpmAggrReportCntrlIndex,current,,A conceptual row in the tpmAggrReportCntrlTable. An example of the indexing of this entry is tpmAggrReportCntrlDataSource.1
.1.3.6.1.2.1.16.30.2.1.1.1,TPM-MIB::tpmAggrReportCntrlIndex,Unsigned32,not-accessible,,current,,An index that uniquely identifies an entry in the tpmAggrReportCntrlTable. Each such entry defines a unique report whose results are placed in the tpmAggrReportTable on behalf of this tpmAggrReportCntrlEntry.
.1.3.6.1.2.1.16.30.2.1.1.2,TPM-MIB::tpmAggrReportCntrlApmCntrlIndex,Unsigned32,read-create,,current,,This index associates this TpmAggrReportCntrlEntry directly with an existing ApmReportControlEntry. This link is used to synchronize reports in the associated tpmAggrReportTable. A value of 0 (zero) enables an independent control table that will report entries to tpmAggrReportTable based only on the other objects in this table. A non-zero value indicates that this row is defined through the APM-MIB. In this case, all row objects are set to their corresponding values in the APM-MIB. In the event that a SET is issued to a row object, while the value of the tpmAggrReportCntrlApmCntrlIndex is non-zero, the agent MUST respond as if the object of the SET command had MAX-ACCESS of read-only. This object may not be modified if the associated tpmAggrReportCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.3,TPM-MIB::tpmAggrReportCntrlDataSource,OBJECT,read-create,,current,,The source of the data for TPM Reports generated on behalf of this tpmAggrReportCntrlEntry. If the measurement is being performed by a probe, this should be set to the interface or port where data was received for analysis. If the measurement isn't being performed by a probe this should be set to the primary interface over which the measurement is being performed. If the measurement isn't being performed by a probe and there is no primary interface, or if this information isn't known, this object should be set to 0.0. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object is set to the corresponding apmReportControlTable object in the APM-MIB [RFC3729]. This object may not be modified if the associated tpmAggrReportCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.4,TPM-MIB::tpmAggrReportCntrlAggrType,INTEGER,read-create,,current,flows(1):clients(2):servers(3):applications(4),The type of aggregation being performed for this set of reports. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlAggregationType object. This object may not be modified if the associated tpmAggrReportCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.5,TPM-MIB::tpmAggrReportCntrlInterval,Unsigned32,read-create,,current,,The interval in seconds over which data is accumulated before being aggregated into a report in the tpmAggrReportTable. All reports with the same tpmAggrReportCntrlIndex will be based on the same interval. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlControlInterval object. This object may not be modified if the associated tpmReportAggregateCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.6,TPM-MIB::tpmAggrReportCntrlReqSize,Unsigned32,read-create,,current,,The maximum number of Client and Server combination entries requested for this report. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlRequestedSize object. When this object is created or modified, the probe should set tpmReportCntrlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources. It is important to note that this value is the number of requested entries in the tpmAggrReportTable only. Because the probe can derive this table from the apmReportTable, the probe must make sure that sufficient resources exist to support the creation of the apmReportTable, plus any additional resources required to convert or support this table. This object may not be modified if the associated tpmReportAggregateCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.7,TPM-MIB::tpmAggrReportCntrlGrantedSize,Unsigned32,read-only,,current,,The maximum number of performance entries in this report. When the associated tpmAggrReportCntrlReqSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe must not lower this value except as a result of a set to the associated tpmAggrReportCntrlReqSize object. It is an implementation-specific matter as to whether zero-valued entries are available.
.1.3.6.1.2.1.16.30.2.1.1.8,TPM-MIB::tpmAggrReportCntrlReqReports,Unsigned32,read-create,,current,,The number of saved reports requested to be allocated on behalf of this entry. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlcwRequestedReportsDataSource object. This object may not be modified if the associated tpmReportAggregateCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.9,TPM-MIB::tpmAggrReportCntrlGrantedReports,Unsigned32,read-only,,current,,The number of saved reports the agent has allocated based on the requested amount in tpmAggrReportCntrlReqReports. Because each report can have many entries, the total number of entries allocated will be this number multiplied by the value of tpmAggrReportCntrlGrantedSize, or by 1 if that object doesn't exist. When the associated tpmAggrReportCntrlReqReports object is created or modified, the agent should set this object as closely to the requested value as is possible for the particular implementation and available resources. When considering available resources, the agent must consider its ability to allocate this many reports, each with the number of entries represented by tpmAggrReportCntrlGrantedSize, or by 1 if that object doesn't exist. Note that although the storage required for each report may fluctuate due to changing conditions, the agent must continue to have storage available to satisfy the full report size for all reports, when necessary. Further, the agent must not lower this value except as a result of a set to the associated tpmAggrReportCntrlReqSize object.
.1.3.6.1.2.1.16.30.2.1.1.10,TPM-MIB::tpmAggrReportCntrlStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when the system began processing the report in progress. Note that the report in progress is not available. This object may be used by the management station to figure out the start time for all previous reports saved for this tpmAggrReportCntrlEntry, as reports are started at fixed intervals. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object is set to the corresponding apmReportControlTable object in the APM-MIB defined in the IETF's RMONMIB WG.
.1.3.6.1.2.1.16.30.2.1.1.11,TPM-MIB::tpmAggrReportCntrlReportNumber,Unsigned32,read-only,,current,,The number of the report in progress. When an tpmAggrReportCntrlEntry is activated, the first report will be numbered zero. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlReportNumber object.
.1.3.6.1.2.1.16.30.2.1.1.12,TPM-MIB::tpmAggrReportCntrlInsertsDenied,Counter32,read-only,,current,,The number of attempts to add an entry to reports for this TpmAggrReportCntrlEntry that failed because the number of entries would have exceeded tpmAggrReportCntrlGrantedSize. This number is valuable in determining if enough entries have been allocated for reports in light of fluctuating network usage. Note that an entry that is denied will often be attempted again, so this number will not predict the exact number of additional entries needed, but it can be used to understand the relative magnitude of the problem. Also note that there is no ordering specified for the entries in the report; thus, there are no rules for which entries will be omitted when not enough entries are available. As a consequence, the agent is not required to delete 'least valuable' entries first.
.1.3.6.1.2.1.16.30.2.1.1.13,TPM-MIB::tpmAggrReportCntrlDroppedFrames,Counter32,read-only,,current,,The total number of frames that were received by the agent and therefore not accounted for in the *StatsDropEvents, but for which the agent chose not to count for this entry for whatever reason. Most often, this event occurs when the agent is out of some resources and decides to shed load from this collection. This count does not include packets that were not counted because they had MAC-layer errors. Note that if the alMatrixTables are not implemented or are inactive because no protocols are enabled in the protocol directory, this value should be 0. Note that, unlike the dropEvents counter, this number is the exact number of frames dropped.
.1.3.6.1.2.1.16.30.2.1.1.14,TPM-MIB::tpmAggrReportCntrlOwner,OCTET,read-create,,current,,The entity that configured this entry and is therefore using the resources assigned to it. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlReportNumber object. This object may not be modified if the associated tpmReportAggregateCntrlStatus object is equal to active(1).
.1.3.6.1.2.1.16.30.2.1.1.15,TPM-MIB::tpmAggrReportCntrlStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this tpmAggrReportCntrlEntry. If the value of this object is 'permanent', no objects in this row need to be writable.
.1.3.6.1.2.1.16.30.2.1.1.16,TPM-MIB::tpmAggrReportCntrlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this performance control entry. An entry may not exist in the active state unless each object in the entry has an appropriate value. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object should be set by the agent to the value of the apmReportControlReportNumber object. Once this object is set to active(1), no objects in the tpmAggrReportCntrlTable can be changed. If this object is not equal to active(1), all associated entries in the tpmAggrReportTable shall be deleted.
.1.3.6.1.2.1.16.30.2.2,TPM-MIB::tpmAggrReportTable,,not-accessible,,current,,This table contains transport performance metric studies for each of the control table entries in tpmAggrReportCntrlTable. These studies are provided based on the selections and parameters found for the entry in the tpmAggregateReportCntrlTable. The performance statistics are specified in the tpmTransMetricDirTable associated with the application in question and indexed by appLocalIndex and tpmTransMetricIndex.
.1.3.6.1.2.1.16.30.2.2.1,TPM-MIB::tpmAggrReportEntry,,not-accessible,tpmAggrReportCntrlIndex:tpmAggrReportIndex:tpmAggrReportAppLocalIndex:tpmAggrReportTransMetricIndex:protocolDirLocalIndex:tpmAggrReportServerAddress:tpmAggrReportApmNameClientID,current,,A conceptual row in the tpmAggrReportTable. The tpmAggrReportCntrlIndex value in the index identifies the tpmAggrReportCntrlEntry on whose behalf this entry was created. The tpmAggrReportIndex value in the index identifies which report (in the series of reports) this entry is a part of. The tpmAggrReportAppLocalIndex value in the index identifies the application protocol that is being reported. The tpmTransMetricIndex value in the index identifies the transaction protocol-metric pair for the traffic flows aggregated in this entry. The protocolDirLocalIndex value in the index identifies the network layer protocol of the tpmAggrReportServerAddress. When the associated tpmAggrReportCntrlAggrType value is equal to applications(4) or clients(2), this value will equal 0. The tpmAggrReportServerAddress value in the index identifies the network layer address of the server in traffic flows aggregated in this entry. The tpmAggrReportApmNameClientID value in the index identifies the client in traffic flows aggregated in this entry. If the associated tpmAggrReportCntrlAggrType is equal to applications(4) or servers(3), then this object will be set to 0. An example of the indexing of this entry is tpmAggrReportStatN.3.15.34.262.18.4.128.2.6.7.3256521
.1.3.6.1.2.1.16.30.2.2.1.1,TPM-MIB::tpmAggrReportIndex,Unsigned32,not-accessible,,current,,The value of tpmAggrReportCntrlNumber for the report to which this entry belongs.
.1.3.6.1.2.1.16.30.2.2.1.2,TPM-MIB::tpmAggrReportAppLocalIndex,Unsigned32,not-accessible,,current,,The common application of the transactions aggregated in this entry.
.1.3.6.1.2.1.16.30.2.2.1.3,TPM-MIB::tpmAggrReportTransMetricIndex,Unsigned32,not-accessible,,current,,A unique index that identifies the transaction and metric associated with the statistics reported here.
.1.3.6.1.2.1.16.30.2.2.1.4,TPM-MIB::tpmAggrReportServerAddress,OCTET,not-accessible,,current,,The network layer address of the server host in this conversation. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. Because this object is an index variable, it is encoded in the index according to the index encoding rules. For example, if the protocolDirLocalIndex indicates an encapsulation of IPv4, this object is encoded as a length octet of 4, followed by the 4 octets of the IPv4 address, in network byte order. If the associated tpmAggrReportCntrlAggrType is equal to application(4) or client(2), then this object will be a null string and will be encoded simply as a length octet of 0.
.1.3.6.1.2.1.16.30.2.2.1.5,TPM-MIB::tpmAggrReportApmNameClientID,Unsigned32,not-accessible,,current,,A unique ID assigned to the machine represented by this mapping. This ID is assigned by the agent using an implementation-specific algorithm.
.1.3.6.1.2.1.16.30.2.2.1.6,TPM-MIB::tpmAggrReportStatN,Gauge32,read-only,,current,,The count of the total number of data points for the specified metric. This number always represents the total size of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results for one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.2.1.7,TPM-MIB::tpmAggrReportOverflowStatN,Gauge32,read-only,,current,,The number of times the associated tpmAggrReportStatN counter has overflowed. Note that this object will only be instantiated if the associated tpmAggrReportHCStatN object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.8,TPM-MIB::tpmAggrReportHCStatN,Counter64,read-only,,current,,The high-capacity version of tpmAggrReportStatN. Note that this object will only be instantiated if the agent supports high-capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.9,TPM-MIB::tpmAggrReportStatSumX,Gauge32,read-only,,current,,The sum of all the data point values for the specified metric. This number always represents the total values of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.2.1.10,TPM-MIB::tpmAggrReportOverflowStatSumX,Gauge32,read-only,,current,,The number of times the associated tpmAggrReportStatSumX counter has overflowed. Note that this object will only be instantiated if the associated tpmAggrReportHCStatSumX object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.11,TPM-MIB::tpmAggrReportHCStatSumX,Counter64,read-only,,current,,The high-capacity version of tpmAggrReportStatSumX. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.12,TPM-MIB::tpmAggrReportStatMaximum,Gauge32,read-only,,current,,The single maximum data point value observed during the study period for the specified metric. This number always represents the maximum value of any single statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.2.1.13,TPM-MIB::tpmAggrReportStatMinimum,Gauge32,read-only,,current,,The single minimum data point value observed during the study period for the specified metric. This number always represents the minimum value of any single statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.2.1.14,TPM-MIB::tpmAggrReportStatSumSq,Gauge32,read-only,,current,,The sum of all the squared data point values for the specified metric. This number always represents the total of the squared values of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.2.1.15,TPM-MIB::tpmAggrReportOverflowStatSumSq,Gauge32,read-only,,current,,The number of times the associated tpmAggrReportStatSumSq counter has overflowed. Note that this object will only be instantiated if the associated tpmAggrReportHCStatSumSq object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.16,TPM-MIB::tpmAggrReportHCStatSumSq,Counter64,read-only,,current,,The high-capacity version of tpmAggrReportStatSumSq. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.17,TPM-MIB::tpmAggrReportStatSumIX,Gauge32,read-only,,current,,For each interval, each data point is associated with a value I, I = 1..N where N is the number of data points; tpmAggrReportStatSumIX is the multiplication of the data point value with the current I. This value along with the other statistics values allow the calculation of the slope of the least-squares line through the data points.
.1.3.6.1.2.1.16.30.2.2.1.18,TPM-MIB::tpmAggrReportOverflowStatSumIX,Gauge32,read-only,,current,,The number of times the associated tpmAggrReportStatSumIX counter has overflowed. Note that this object will only be instantiated if the associated tpmAggrReportHCStatSumIX object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.19,TPM-MIB::tpmAggrReportHCStatSumIX,Counter64,read-only,,current,,The high-capacity version of tpmAggrReportStatSumIX. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.20,TPM-MIB::tpmAggrReportStatSumIXSq,Gauge32,read-only,,current,,For each interval, each data point is associated with a value I, I = 1..N where N is the number of data points; tpmAggrReportStatSumIXSq is the multiplication of the data point value with the current I. This value along with the other statistics values allow the calculation of the slope of the least-squares line through the data points.
.1.3.6.1.2.1.16.30.2.2.1.21,TPM-MIB::tpmAggrReportOverflowStatSumIXSq,Gauge32,read-only,,current,,The number of times the associated tpmAggrReportStatSumIXSq counter has overflowed. Note that this object will only be instantiated if the associated tpmAggrReportHCStatSumIXSq object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.2.1.22,TPM-MIB::tpmAggrReportHCStatSumIXSq,Counter64,read-only,,current,,The high-capacity version of tpmAggrReportStatSumIXSq. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.3,TPM-MIB::tpmCurReportTable,,not-accessible,,current,,This table will contain entries associated with an apmReportControlEntry that consitute a current 'snapshot' of the metrics being collected in association with a set of TPM-related application transactions. This table contains all sub-flow metrics for transactions that have been started but have not yet finished (i.e., current) and a history of those that have finished (i.e., completed). It may not always be obvious from the context whether a transaction is currently in-progress or has been completed. Therefore, the completion status of a transaction is indicated by the value of the tpmCurReportCompletion object.
.1.3.6.1.2.1.16.30.2.3.1,TPM-MIB::tpmCurReportEntry,,not-accessible,tpmAggrReportCntrlIndex:tpmCurReportAppLocalIndex:tpmCurReportTransMetricIndex:protocolDirLocalIndex:tpmCurReportServerAddress:tpmCurReportApmNameClientID:tpmCurReportApmTransactionID,current,,A conceptual row in the tpmCurReportTable. The tpmAggrReportControlIndex value in the index identifies the tpmAggrReportCntrlEntry on whose behalf this entry was created. The tpmCurReportAppLocalIndex value in the index identifies the application protocol that is being reported. The protocolDirLocalIndex value in the index identifies the network layer protocol of the tpmAggrReportServerAddress. When the associated tpmAggrReportCntrlAggrType value is equal to applications(4), this value will equal 0. The tpmCurReportServerAddress value in the index identifies the network layer address of the server in traffic flows aggregated in this entry. The tpmCurReportCurrentApmNameClientID value in the index identifies the network layer address of the client in traffic flows aggregated in this entry. The tpmCurReportCurrentMetricIndex value in the index identifies the transported application protocol of the traffic flows aggregated in this entry. Note that the order of protocolDirLocalIndex variables is the opposite of that in the RMON2 MIB (application.network instead of network.application); the report entries are sorted by application first, server second, and client third. The tpmCurReportCntrIndex value in the index identifies the tpmAggrReportCntrlEntry on whose behalf this entry was created. The tpmCurReportMetricIndex value in the index identifies the metric and protocol of the tpmCurReportServerAddress, via the tpmTransMetricDir table. An example of the indexing of this table is tpmCurReportStatisticN.3.34.262.18.4.128.2.6.6.3256521.29667
.1.3.6.1.2.1.16.30.2.3.1.1,TPM-MIB::tpmCurReportAppLocalIndex,Unsigned32,not-accessible,,current,,The common application of the transactions reported in this entry.
.1.3.6.1.2.1.16.30.2.3.1.2,TPM-MIB::tpmCurReportTransMetricIndex,Unsigned32,not-accessible,,current,,A unique index that identifies the transaction and metric associated with the statistics reported here.
.1.3.6.1.2.1.16.30.2.3.1.3,TPM-MIB::tpmCurReportServerAddress,OCTET,not-accessible,,current,,The network server address for this tpmCurReportEntry. This is represented as an octet string with specific semantics and length as identified by the protocolDirLocalIndex component of the index. For example, if the protocolDirLocalIndex indicates an encapsulation of IPv4, this object is encoded as a length octet of 4, followed by the 4 octets of the IPv4 address, in network byte order.
.1.3.6.1.2.1.16.30.2.3.1.4,TPM-MIB::tpmCurReportApmNameClientID,Unsigned32,not-accessible,,current,,A unique ID assigned to the machine represented by this mapping. This ID is assigned by the agent using an implementation-specific algorithm.
.1.3.6.1.2.1.16.30.2.3.1.5,TPM-MIB::tpmCurReportApmTransactionID,Unsigned32,not-accessible,,current,,A unique value for this transaction amongst other transactions sharing the same application, transaction-layer protocol and metric, and server and client addresses. Implementations may choose to use the value of the client's source port, when possible. If the tpmAggrReportCntrlApmCntrlIndex is non-zero, then this object is set to the corresponding apmTransactionID object in the APM-MIB developed in the IETF's RMONMIB WG.
.1.3.6.1.2.1.16.30.2.3.1.6,TPM-MIB::tpmCurReportMetricValue,Gauge32,read-only,,current,,The current value of the metric being evaluated. For some transaction types this value may be 0, e.g., the current round-trip time for a DNS query. For other transaction types, this will represent the current value of a continuously measured metric, e.g., the current throughput of an FTP transaction.
.1.3.6.1.2.1.16.30.2.3.1.7,TPM-MIB::tpmCurReportCompletion,INTEGER,read-only,,current,completed(2),The status of this transaction. It is not always obvious from context whether a transaction is ongoing or completed. E.g., an ftp-GET transaction may last several minutes or hours, and a value found in the tpmCurReportMetricValue object lists to observed throughput for the transaction up to this point in time. The value of the tpmCurReportCompletion indicates whether the transaction has been completed.
.1.3.6.1.2.1.16.30.2.4,TPM-MIB::tpmCurReportSize,Unsigned32,read-write,,current,,The maximum number of completed transactions desired to be retained in the tpmCurReportTable. If the agent doesn't have enough resources to retain this many, it will retain as many as possible. Regardless of this value, the agent must attempt to keep records for all current transactions it is monitoring. The agent should consider this value to give a hint as to how many transactions to save. This is not a hard limit, just a hint to a maximum value of interest. If this value is reduced by the management station, the agent can take note, it may free some records, or it may do nothing. The value of this object must persist across reboots.
.1.3.6.1.2.1.16.30.2.5,TPM-MIB::tpmExcpReportTable,,not-accessible,,current,,This table contains all sub-flow metrics for transactions that have been tagged by the apmExceptionTable filter as having had poor performance.
.1.3.6.1.2.1.16.30.2.5.1,TPM-MIB::tpmExcpReportEntry,,not-accessible,apmAppDirAppLocalIndex:apmAppDirResponsivenessType:apmExceptionIndex:tpmExcpReportTransMetricIndex,current,,A conceptual row in the tpmExcpReportTable. This table contains aggregated information associated with exceptions counted in the apmExceptionTable. The information is aggregated in a manner identical to the aggregation in the tpmAggrReportTable, with the exception that data only from transactions associated with a flagged application is included. The indexing into this table follows the indexing in the APM-MIB but adds the tpmTransMetricIndex to identify the sub-application transaction and metric pair.
.1.3.6.1.2.1.16.30.2.5.1.1,TPM-MIB::tpmExcpReportTransMetricIndex,Unsigned32,not-accessible,,current,,A unique index that identifies the transaction and metric associated with the data reported here.
.1.3.6.1.2.1.16.30.2.5.1.2,TPM-MIB::tpmExcpReportStatN,Gauge32,read-only,,current,,The count of the total number of data points for the specified metric. This number always represents the total size of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.5.1.3,TPM-MIB::tpmExcpReportOverflowStatN,Gauge32,read-only,,current,,The number of times the associated tpmExcpReportStatN counter has overflowed. Note that this object will only be instantiated if the associated tpmExcpReportHCStatN object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.4,TPM-MIB::tpmExcpReportHCStatN,Counter64,read-only,,current,,The high-capacity version of tpmExcpReportStatN. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.5,TPM-MIB::tpmExcpReportStatSumX,Gauge32,read-only,,current,,The sum of all the data point values for the specified metric. This number always represents the total values of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.5.1.6,TPM-MIB::tpmExcpReportOverflowStatSumX,Gauge32,read-only,,current,,The number of times the associated tpmExcpReportStatSumX counter has overflowed. Note that this object will only be instantiated if the associated tpmExcpReportHCStatSumX object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.7,TPM-MIB::tpmExcpReportHCStatSumX,Counter64,read-only,,current,,The high-capacity version of tpmExcpReportStatSumX. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.8,TPM-MIB::tpmExcpReportStatMaximum,Gauge32,read-only,,current,,The single maximum data point value observed during the study period for the specified metric. This number always represents the maximum value of any single statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.5.1.9,TPM-MIB::tpmExcpReportStatMinimum,Gauge32,read-only,,current,,The single minimum data point value observed during the study period for the specified metric. This number always represents the minimum value of any single statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.5.1.10,TPM-MIB::tpmExcpReportStatSumSq,Gauge32,read-only,,current,,The sum of all the squared data point values for the specified metric. This number always represents the total of the squared values of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved.
.1.3.6.1.2.1.16.30.2.5.1.11,TPM-MIB::tpmExcpReportOverflowStatSumSq,Gauge32,read-only,,current,,The number of times the associated tpmExcpReportStatSumSq counter has overflowed. Note that this object will only be instantiated if the associated tpmExcpReportHCStatSumSq object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.12,TPM-MIB::tpmExcpReportHCStatSumSq,Counter64,read-only,,current,,The high-capacity version of tpmExcpReportStatSumSq. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.13,TPM-MIB::tpmExcpReportStatSumIX,Gauge32,read-only,,current,,For each interval, each data point is associated with a value I, I = 1..N where N is the number of data points; tpmExcpReportStatSumIX is the multiplication of the data point value with the current I. This value along with the other statistics values allow the calculation of the slope of the least-squares line through the data points.
.1.3.6.1.2.1.16.30.2.5.1.14,TPM-MIB::tpmExcpReportOverflowStatSumIX,Gauge32,read-only,,current,,The number of times the associated tpmExcpReportStatSumIX counter has overflowed. Note that this object will only be instantiated if the associated tpmExcpReportHCStatSumIX object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.15,TPM-MIB::tpmExcpReportHCStatSumIX,Counter64,read-only,,current,,The high-capacity version of tpmExcpReportStatSumIX. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.16,TPM-MIB::tpmExcpReportStatSumIXSq,Gauge32,read-only,,current,,For each interval, each data point is associated with a value I, I = 1..N where N is the number of data points; tpmExcpReportStatSumIXSq is the multiplication of the data point value with the current I. This value along with the other statistics values allow the calculation of the slope of the least-squares line through the data points.
.1.3.6.1.2.1.16.30.2.5.1.17,TPM-MIB::tpmExcpReportOverflowStatSumIXSq,Gauge32,read-only,,current,,The number of times the associated tpmExcpReportStatSumIXSq counter has overflowed. Note that this object will only be instantiated if the associated tpmExcpReportHCStatSumIXSq object is also instantiated for a particular dataSource.
.1.3.6.1.2.1.16.30.2.5.1.18,TPM-MIB::tpmExcpReportHCStatSumIXSq,Counter64,read-only,,current,,The high-capacity version of tpmExcpReportStatSumIXSq. Note that this object will only be instantiated if the agent supports High Capacity monitoring for a particular dataSource.
.1.3.6.1.2.1.16.30.3,TPM-MIB::tpmConformance,,,,,,
.1.3.6.1.2.1.16.30.3.1,TPM-MIB::tpmMIBCompliances,,,,,,
.1.3.6.1.2.1.16.30.3.1.1,TPM-MIB::tpmMIBCompliance,,,,,,Describes the requirements for conformance to the TPM-MIB. This compliance statement defines the following TPM-MIB implementation: - tpmCapabilitiesGroup (minimum) - tpmAggregateReportsGroup (minimum) - tpmCurrentReportsGroup (optional) - tpmExceptionReportsGroup (optional). In order to implement the (optional) tpmExceptionReportsGroup, it is necessary to implement pieces of the APM-MIB as described in the tpmApmMIBCompliance MODULE below. Further, in the event that the TPM-MIB is used to provide a drill-down capability, which is the true value of this MIB, then the tpmApmReportControlGroup must be implemented.
.1.3.6.1.2.1.16.30.3.1.2,TPM-MIB::tpmCurrentReportsCompliance,,,,,,This defines the Current Reports compliance. This is useful when information on in-progress and historical transaction-level data is desired.
.1.3.6.1.2.1.16.30.3.1.3,TPM-MIB::tpmExceptionReportsCompliance,,,,,,This defines the Exception Reports compliance. This is useful when information on transactions whose performance is deemed out-of-bounds.
.1.3.6.1.2.1.16.30.3.2,TPM-MIB::tpmGroups,,,,,,
.1.3.6.1.2.1.16.30.3.2.1,TPM-MIB::tpmCapabilitiesGroup,,,,,,The tpmCapabilitiesGroup specifies various capabilities associated with the monitoring agent.
.1.3.6.1.2.1.16.30.3.2.2,TPM-MIB::tpmAggregateReportsGroup,,,,,,The tpmAggregateReportsGroup provides control and reporting of aggregate measurement statistics.
.1.3.6.1.2.1.16.30.3.2.3,TPM-MIB::tpmCurrentReportsGroup,,,,,,The tpmCurrentReportsGroup contains metric information relating to ongoing measurements as well as historical values.
.1.3.6.1.2.1.16.30.3.2.4,TPM-MIB::tpmExceptionReportsGroup,,,,,,The tpmExceptionReportsGroup reports sub-application level statistics associated with errant applications.
.1.3.6.1.2.1.16.31,RAQMON-MIB::raqmonMIB,,,,,,Real-Time Application QoS Monitoring MIB. Copyright (c) The Internet Society (2006). This version of this MIB module is part of RFC 4711; See the RFC itself for full legal notices.
.1.3.6.1.2.1.16.31.0,RAQMON-MIB::raqmonNotifications,,,,,,
.1.3.6.1.2.1.16.31.0.1,RAQMON-MIB::raqmonSessionAlarm,,,,,,A notification generated by an entry in the raqmonSessionExceptionTable.
.1.3.6.1.2.1.16.31.1,RAQMON-MIB::raqmonMIBObjects,,,,,,
.1.3.6.1.2.1.16.31.1.1,RAQMON-MIB::raqmonSession,,,,,,
.1.3.6.1.2.1.16.31.1.1.1,RAQMON-MIB::raqmonParticipantTable,,not-accessible,,current,,This table contains information about participants in both active and closed (terminated) sessions.
.1.3.6.1.2.1.16.31.1.1.1.1,RAQMON-MIB::raqmonParticipantEntry,,not-accessible,raqmonParticipantStartDate:raqmonParticipantIndex,current,,Each row contains information for a single session (application) run by one participant. Indexation by the start time of the session aims to ease sorting by management applications. Agents MUST NOT report identical start times for any two sessions on the same host. Rows are removed for inactive sessions when implementation-specific age or space limits are reached.
.1.3.6.1.2.1.16.31.1.1.1.1.1,RAQMON-MIB::raqmonParticipantStartDate,OCTET,not-accessible,,current,,The date and time of this entry. It will be the date and time of the first report received.
.1.3.6.1.2.1.16.31.1.1.1.1.2,RAQMON-MIB::raqmonParticipantIndex,Unsigned32,not-accessible,,current,,The index of the conceptual row, which is for SNMP purposes only and has no relation to any protocol value. There is no requirement that these rows be created or maintained sequentially. The index will be unique for a particular date and time.
.1.3.6.1.2.1.16.31.1.1.1.1.3,RAQMON-MIB::raqmonParticipantReportCaps,BITS,read-only,,current,raqmonPartRepDsrcName(0):raqmonPartRepRecvName(1):raqmonPartRepDsrcPort(2):raqmonPartRepRecvPort(3):raqmonPartRepSetupTime(4):raqmonPartRepSetupDelay(5):raqmonPartRepSessionDuration(6):raqmonPartRepSetupStatus(7):raqmonPartRepRTEnd2EndNetDelay(8):raqmonPartRepOWEnd2EndNetDelay(9):raqmonPartApplicationDelay(10):raqmonPartRepIAJitter(11):raqmonPartRepIPDV(12):raqmonPartRepRcvdPackets(13):raqmonPartRepRcvdOctets(14):raqmonPartRepSentPackets(15):raqmonPartRepSentOctets(16):raqmonPartRepCumPacketsLoss(17):raqmonPartRepFractionPacketsLoss(18):raqmonPartRepCumDiscards(19):raqmonPartRepFractionDiscards(20):raqmonPartRepSrcPayloadType(21):raqmonPartRepDestPayloadType(22):raqmonPartRepSrcLayer2Priority(23):raqmonPartRepSrcTosDscp(24):raqmonPartRepDestLayer2Priority(25):raqmonPartRepDestTosDscp(26):raqmonPartRepCPU(27):raqmonPartRepMemory(28):raqmonPartRepAppName(29),The Report capabilities of the participant, as perceived by the Collector. If the participant can report the Data Source Name as defined in [RFC4710], Section 5.3, then the raqmonPartRepDsrcName bit will be set. If the participant can report the Receiver Name as defined in [RFC4710], Section 5.4, then the raqmonPartRepRecvName bit will be set. If the participant can report the Data Source Port as defined in [RFC4710], Section 5.5, then the raqmonPartRepDsrcPort bit will be set. If the participant can report the Receiver Port as defined in [RFC4710], Section 5.6, then the raqmonPartRepRecvPort bit will be set. If the participant can report the Session Setup Time as defined in [RFC4710], Section 5.7, then the raqmonPartRepSetupTime bit will be set. If the participant can report the Session Setup Delay as defined in [RFC4710], Section 5.8, then the raqmonPartRepSetupDelay bit will be set. If the participant can report the Session Duration as defined in [RFC4710], Section 5.9, then the raqmonPartRepSessionDuration bit will be set. If the participant can report the Setup Status as defined in [RFC4710], Section 5.10, then the raqmonPartRepSetupStatus bit will be set. If the participant can report the Round-Trip End-to-end Network Delay as defined in [RFC4710], Section 5.11, then the raqmonPartRepRTEnd2EndNetDelay bit will be set. If the participant can report the One-way End-to-end Network Delay as defined in [RFC4710], Section 5.12, then the raqmonPartRepOWEnd2EndNetDelay bit will be set. If the participant can report the Application Delay as defined in [RFC4710], Section 5.13, then the raqmonPartApplicationDelay bit will be set. If the participant can report the Inter-Arrival Jitter as defined in [RFC4710], Section 5.14, then the raqmonPartRepIAJitter bit will be set. If the participant can report the IP Packet Delay Variation as defined in [RFC4710], Section 5.15, then the raqmonPartRepIPDV bit will be set. If the participant can report the number of application packets received as defined in [RFC4710], Section 5.16, then the raqmonPartRepRcvdPackets bit will be set. If the participant can report the number of application octets received as defined in [RFC4710], Section 5.17, then the raqmonPartRepRcvdOctets bit will be set. If the participant can report the number of application packets sent as defined in [RFC4710], Section 5.18, then the raqmonPartRepSentPackets bit will be set. If the participant can report the number of application octets sent as defined in [RFC4710], Section 5.19, then the raqmonPartRepSentOctets bit will be set. If the participant can report the number of cumulative packets lost as defined in [RFC4710], Section 5.20, then the raqmonPartRepCumPacketsLoss bit will be set. If the participant can report the fraction of packet loss as defined in [RFC4710], Section 5.21, then the raqmonPartRepFractionPacketsLoss bit will be set. If the participant can report the number of cumulative discards as defined in [RFC4710], Section 5.22, then the raqmonPartRepCumDiscards bit will be set. If the participant can report the fraction of discards as defined in [RFC4710], Section 5.23, then the raqmonPartRepFractionDiscards bit will be set. If the participant can report
.1.3.6.1.2.1.16.31.1.1.1.1.4,RAQMON-MIB::raqmonParticipantAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the Internet address of the participant for this session.
.1.3.6.1.2.1.16.31.1.1.1.1.5,RAQMON-MIB::raqmonParticipantAddr,OCTET,read-only,,current,,The Internet Address of the participant for this session. Formatting of this object is determined by the value of raqmonParticipantAddrType.
.1.3.6.1.2.1.16.31.1.1.1.1.6,RAQMON-MIB::raqmonParticipantSendPort,Unsigned32,read-only,,current,,Port from which session data is sent. If the value was not reported to the collector, this object will have the value 0.
.1.3.6.1.2.1.16.31.1.1.1.1.7,RAQMON-MIB::raqmonParticipantRecvPort,Unsigned32,read-only,,current,,Port on which session data is received. If the value was not reported to the collector, this object will have the value 0.
.1.3.6.1.2.1.16.31.1.1.1.1.8,RAQMON-MIB::raqmonParticipantSetupDelay,Integer32,read-only,,current,,Session setup time. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.9,RAQMON-MIB::raqmonParticipantName,OCTET,read-only,,current,,The data source name for the participant.
.1.3.6.1.2.1.16.31.1.1.1.1.10,RAQMON-MIB::raqmonParticipantAppName,OCTET,read-only,,current,,A string giving the name and possibly the version of the application generating the stream, e.g., 'videotool 1.2.' This information may be useful for debugging purposes and is similar to the Mailer or Mail-System-Version SMTP headers. The tool value is expected to remain constant for the duration of the session.
.1.3.6.1.2.1.16.31.1.1.1.1.11,RAQMON-MIB::raqmonParticipantQosCount,Gauge32,read-only,,current,,The current number of entries in the raqmonQosTable for this participant and session.
.1.3.6.1.2.1.16.31.1.1.1.1.12,RAQMON-MIB::raqmonParticipantEndDate,OCTET,read-only,,current,,The date and time of the most recent report received.
.1.3.6.1.2.1.16.31.1.1.1.1.13,RAQMON-MIB::raqmonParticipantDestPayloadType,Integer32,read-only,,current,,Destination Payload Type. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.14,RAQMON-MIB::raqmonParticipantSrcPayloadType,Integer32,read-only,,current,,Source Payload Type. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.15,RAQMON-MIB::raqmonParticipantActive,INTEGER,read-only,,current,true(1):false(2),Value 'true' indicates that the session for this participant is active (open). Value 'false' indicates that the session is closed (terminated).
.1.3.6.1.2.1.16.31.1.1.1.1.16,RAQMON-MIB::raqmonParticipantPeer,OBJECT,read-only,,current,,The pointer to the corresponding entry in this table for the other peer participant. If there is no such entry in the participant table of the collector represented by this SNMP agent, then the value will be { 0 0 }. 
.1.3.6.1.2.1.16.31.1.1.1.1.17,RAQMON-MIB::raqmonParticipantPeerAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the Internet address of the peer participant for this session.
.1.3.6.1.2.1.16.31.1.1.1.1.18,RAQMON-MIB::raqmonParticipantPeerAddr,OCTET,read-only,,current,,The Internet Address of the peer participant for this session. Formatting of this object is determined by the value of raqmonParticipantPeerAddrType.
.1.3.6.1.2.1.16.31.1.1.1.1.19,RAQMON-MIB::raqmonParticipantSrcL2Priority,Integer32,read-only,,current,,Source Layer 2 Priority. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.20,RAQMON-MIB::raqmonParticipantDestL2Priority,Integer32,read-only,,current,,Destination Layer 2 Priority. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.21,RAQMON-MIB::raqmonParticipantSrcDSCP,Integer32,read-only,,current,,Source Layer 3 DSCP value. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.22,RAQMON-MIB::raqmonParticipantDestDSCP,Integer32,read-only,,current,,Destination Layer 3 DSCP value.
.1.3.6.1.2.1.16.31.1.1.1.1.23,RAQMON-MIB::raqmonParticipantCpuMean,Integer32,read-only,,current,,Mean CPU utilization. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.24,RAQMON-MIB::raqmonParticipantCpuMin,Integer32,read-only,,current,,Minimum CPU utilization. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.25,RAQMON-MIB::raqmonParticipantCpuMax,Integer32,read-only,,current,,Maximum CPU utilization. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.26,RAQMON-MIB::raqmonParticipantMemoryMean,Integer32,read-only,,current,,Mean memory utilization. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.27,RAQMON-MIB::raqmonParticipantMemoryMin,Integer32,read-only,,current,,Minimum memory utilization. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.28,RAQMON-MIB::raqmonParticipantMemoryMax,Integer32,read-only,,current,,Maximum memory utilization. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.29,RAQMON-MIB::raqmonParticipantNetRTTMean,Integer32,read-only,,current,,Mean round-trip end-to-end network delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.30,RAQMON-MIB::raqmonParticipantNetRTTMin,Integer32,read-only,,current,,Minimum round-trip end-to-end network delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.31,RAQMON-MIB::raqmonParticipantNetRTTMax,Integer32,read-only,,current,,Maximum round-trip end-to-end network delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.32,RAQMON-MIB::raqmonParticipantIAJitterMean,Integer32,read-only,,current,,Mean inter-arrival jitter over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.33,RAQMON-MIB::raqmonParticipantIAJitterMin,Integer32,read-only,,current,,Minimum inter-arrival jitter over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.34,RAQMON-MIB::raqmonParticipantIAJitterMax,Integer32,read-only,,current,,Maximum inter-arrival jitter over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.35,RAQMON-MIB::raqmonParticipantIPDVMean,Integer32,read-only,,current,,Mean IP packet delay variation over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.36,RAQMON-MIB::raqmonParticipantIPDVMin,Integer32,read-only,,current,,Minimum IP packet delay variation over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.37,RAQMON-MIB::raqmonParticipantIPDVMax,Integer32,read-only,,current,,Maximum IP packet delay variation over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.38,RAQMON-MIB::raqmonParticipantNetOwdMean,Integer32,read-only,,current,,Mean Network one-way delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.39,RAQMON-MIB::raqmonParticipantNetOwdMin,Integer32,read-only,,current,,Minimum Network one-way delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.40,RAQMON-MIB::raqmonParticipantNetOwdMax,Integer32,read-only,,current,,Maximum Network one-way delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.41,RAQMON-MIB::raqmonParticipantAppDelayMean,Integer32,read-only,,current,,Mean application delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.42,RAQMON-MIB::raqmonParticipantAppDelayMin,Integer32,read-only,,current,,Minimum application delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.43,RAQMON-MIB::raqmonParticipantAppDelayMax,Integer32,read-only,,current,,Maximum application delay over the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.44,RAQMON-MIB::raqmonParticipantPacketsRcvd,Integer32,read-only,,current,,Count of packets received for the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.45,RAQMON-MIB::raqmonParticipantPacketsSent,Integer32,read-only,,current,,Count of packets sent for the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.46,RAQMON-MIB::raqmonParticipantOctetsRcvd,Integer32,read-only,,current,,Count of octets received for the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.47,RAQMON-MIB::raqmonParticipantOctetsSent,Integer32,read-only,,current,,Count of octets sent for the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.48,RAQMON-MIB::raqmonParticipantLostPackets,Integer32,read-only,,current,,Count of packets lost by this receiver for the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.49,RAQMON-MIB::raqmonParticipantLostPacketsFrct,Integer32,read-only,,current,,Fraction of lost packets out of total packets received. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.50,RAQMON-MIB::raqmonParticipantDiscards,Integer32,read-only,,current,,Count of packets discarded by this receiver for the entire session. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.1.1.51,RAQMON-MIB::raqmonParticipantDiscardsFrct,Integer32,read-only,,current,,Fraction of discarded packets out of total packets received. If the value was not reported to the collector, this object will have the value -1.
.1.3.6.1.2.1.16.31.1.1.2,RAQMON-MIB::raqmonQosTable,,not-accessible,,current,,Table of historical information about quality-of-service data during sessions.
.1.3.6.1.2.1.16.31.1.1.2.1,RAQMON-MIB::raqmonQosEntry,,not-accessible,raqmonParticipantStartDate:raqmonParticipantIndex:raqmonQosTime,current,,Each entry contains information from a single RAQMON packet, related to a single session (application) run by one participant. Indexation by the start time of the session aims to ease sorting by management applications. Agents MUST NOT report identical start times for any two sessions on the same host. Rows are removed for inactive sessions when implementation-specific time or space limits are reached.
.1.3.6.1.2.1.16.31.1.1.2.1.1,RAQMON-MIB::raqmonQosTime,Unsigned32,not-accessible,,current,,Time of this entry measured from the start of the corresponding participant session.
.1.3.6.1.2.1.16.31.1.1.2.1.2,RAQMON-MIB::raqmonQoSEnd2EndNetDelay,Integer32,read-only,,current,,The round-trip time. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.3,RAQMON-MIB::raqmonQoSInterArrivalJitter,Integer32,read-only,,current,,An estimate of delay variation as observed by this receiver. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.4,RAQMON-MIB::raqmonQosRcvdPackets,Integer32,read-only,,current,,Count of packets received by this receiver since the previous entry. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.5,RAQMON-MIB::raqmonQosRcvdOctets,Integer32,read-only,,current,,Count of octets received by this receiver since the previous report. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.6,RAQMON-MIB::raqmonQosSentPackets,Integer32,read-only,,current,,Count of packets sent since the previous report. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.7,RAQMON-MIB::raqmonQosSentOctets,Integer32,read-only,,current,,Count of octets sent since the previous report. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.8,RAQMON-MIB::raqmonQosLostPackets,Integer32,read-only,,current,,A count of packets lost as observed by this receiver since the previous report. Will contain the previous value if there was no report for this time, or -1 if the value has never been reported.
.1.3.6.1.2.1.16.31.1.1.2.1.9,RAQMON-MIB::raqmonQosSessionStatus,OCTET,read-only,,current,,The session status. Will contain the previous value if there was no report for this time or the zero-length string if no value was ever reported.
.1.3.6.1.2.1.16.31.1.1.3,RAQMON-MIB::raqmonParticipantAddrTable,,not-accessible,,current,,Maps raqmonParticipantAddr to the index of the raqmonParticipantTable. This table allows management applications to find entries sorted by raqmonParticipantAddr rather than raqmonParticipantStartDate.
.1.3.6.1.2.1.16.31.1.1.3.1,RAQMON-MIB::raqmonParticipantAddrEntry,,not-accessible,raqmonParticipantAddrType:raqmonParticipantAddr:raqmonParticipantStartDate:raqmonParticipantIndex,current,,Each entry corresponds to exactly one entry in the raqmonParticipantEntry: the entry containing the index pair raqmonParticipantStartDate, raqmonParticipantIndex. Note that there is no concern about the indexation of this table exceeding the limits defined by RFC 2578, Section 3.5. According to [RFC4710], Section 5.1, only IPv4 and IPv6 addresses can be reported as participant addresses.
.1.3.6.1.2.1.16.31.1.1.3.1.1,RAQMON-MIB::raqmonParticipantAddrEndDate,OCTET,read-only,,current,,The value of raqmonParticipantEndDate for the corresponding raqmonParticipantEntry.
.1.3.6.1.2.1.16.31.1.2,RAQMON-MIB::raqmonException,,,,,,
.1.3.6.1.2.1.16.31.1.2.2,RAQMON-MIB::raqmonSessionExceptionTable,,not-accessible,,current,,This table defines thresholds for the management station to get notifications about sessions that encountered poor quality of service. The information in this table MUST be persistent across agent reboots.
.1.3.6.1.2.1.16.31.1.2.2.1,RAQMON-MIB::raqmonSessionExceptionEntry,,not-accessible,raqmonSessionExceptionIndex,current,,A conceptual row in the raqmonSessionExceptionTable.
.1.3.6.1.2.1.16.31.1.2.2.1.2,RAQMON-MIB::raqmonSessionExceptionIndex,Unsigned32,not-accessible,,current,,An index that uniquely identifies an entry in the raqmonSessionExceptionTable. Management applications can determine unused indices by performing GetNext or GetBulk operations on the Table.
.1.3.6.1.2.1.16.31.1.2.2.1.3,RAQMON-MIB::raqmonSessionExceptionIAJitterThreshold,Unsigned32,read-create,,current,,Threshold for jitter. The value during a session must be greater than or equal to this value for an exception to be created.
.1.3.6.1.2.1.16.31.1.2.2.1.4,RAQMON-MIB::raqmonSessionExceptionNetRTTThreshold,Unsigned32,read-create,,current,,Threshold for round-trip time. The value during a session must be greater than or equal to this value for an exception to be created.
.1.3.6.1.2.1.16.31.1.2.2.1.5,RAQMON-MIB::raqmonSessionExceptionLostPacketsThreshold,Unsigned32,read-create,,current,,Threshold for lost packets in units of tenths of a percent. The value during a session must be greater than or equal to this value for an exception to be created.
.1.3.6.1.2.1.16.31.1.2.2.1.7,RAQMON-MIB::raqmonSessionExceptionRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object has a value of 'active' when exceptions are being monitored by the system. A newly-created conceptual row must have all the read-create objects initialized before becoming 'active'. A conceptual row that is in the 'notReady' or 'notInService' state MAY be removed after 5 minutes. No writeable objects can be changed while the row is active.
.1.3.6.1.2.1.16.31.1.3,RAQMON-MIB::raqmonConfig,,,,,,
.1.3.6.1.2.1.16.31.1.3.1,RAQMON-MIB::raqmonConfigPort,Unsigned32,read-write,,current,,The UDP port to listen on for RAQMON reports, running on transport protocols other than SNMP. If the RAQMON PDU transport protocol is SNMP, a write operation on this object has no effect, as the standard port 162 is always used. The value of this object MUST be persistent across agent reboots.
.1.3.6.1.2.1.16.31.1.3.2,RAQMON-MIB::raqmonConfigPduTransport,BITS,read-only,,current,other(0):tcp(1):snmp(2),The PDU transport(s) used by this collector. If other(0) is set, the collector supports a transport other than SNMP or TCP. If tcp(1) is set, the collector supports TCP as a transport protocol. If snmp(2) is set, the collector supports SNMP as a transport protocol.
.1.3.6.1.2.1.16.31.1.3.3,RAQMON-MIB::raqmonConfigRaqmonPdus,Counter32,read-only,,current,,Count of RAQMON PDUs received by the Collector.
.1.3.6.1.2.1.16.31.1.3.4,RAQMON-MIB::raqmonConfigRDSTimeout,Unsigned32,read-write,,current,,The number of seconds since the reception of the last RAQMON PDU from a RDS after which a session between the respective RDS and the collector will be considered terminated. The value of this object MUST be persistent across agent reboots.
.1.3.6.1.2.1.16.31.2,RAQMON-MIB::raqmonConformance,,,,,,
.1.3.6.1.2.1.16.31.2.1,RAQMON-MIB::raqmonCompliances,,,,,,
.1.3.6.1.2.1.16.31.2.1.1,RAQMON-MIB::raqmonCompliance,,,,,,Describes the requirements for conformance to the RAQMON MIB.
.1.3.6.1.2.1.16.31.2.2,RAQMON-MIB::raqmonGroups,,,,,,
.1.3.6.1.2.1.16.31.2.2.1,RAQMON-MIB::raqmonCollectorGroup,,,,,,Objects used in RAQMON by a collector.
.1.3.6.1.2.1.16.31.2.2.2,RAQMON-MIB::raqmonCollectorNotificationsGroup,,,,,,Notifications emitted by a RAQMON collector.
.1.3.6.1.2.1.16.32,RAQMON-RDS-MIB::raqmonDsMIB,,,,,,This is the RAQMON Data Source notification MIB Module. It provides a mapping of RAQMON PDUs to SNMP notifications. Ds stands for data source. Note that all of the object types defined in this module are accessible-for-notify and would consequently not be available to a browser using simple Get, GetNext, or GetBulk requests. Copyright (c) The Internet Society (2006). This version of this MIB module is part of RFC 4712; See the RFC itself for full legal notices.
.1.3.6.1.2.1.16.32.0,RAQMON-RDS-MIB::raqmonDsNotifications,,,,,,
.1.3.6.1.2.1.16.32.0.1,RAQMON-RDS-MIB::raqmonDsStaticNotification,,,,,,This notification maps the static parameters in the BASIC RAQMON PDU onto an SNMP transport. This notification is expected to be sent once per session, or when a new sub-session is initiated. The following objects MAY be carried by the raqmonDsStaticNotification: raqmonDsDataSourceDevicePort, raqmonDsReceiverDevicePort, raqmonDsSessionSetupDateTime, raqmonDsSessionSetupDelay, raqmonDsSessionDuration, raqmonDsSourcePayloadType, raqmonDsReceiverPayloadType, raqmonDsSourceLayer2Priority, raqmonDsSourceDscp, raqmonDsDestinationLayer2Priority, raqmonDsDestinationDscp It is RECOMMENDED to keep the size of a notification within the MTU size limits in order to avoid fragmentation.
.1.3.6.1.2.1.16.32.0.2,RAQMON-RDS-MIB::raqmonDsDynamicNotification,,,,,,This notification maps the dynamic parameters in the BASIC RAQMON PDU onto an SNMP transport. The following objects MAY be carried by the raqmonDsDynamicNotification: raqmonDsRoundTripEndToEndNetDelay, raqmonDsOneWayEndToEndNetDelay, raqmonDsApplicationDelay, raqmonDsInterArrivalJitter, raqmonDsIPPacketDelayVariation, raqmonDsTotalPacketsSent, raqmonDsTotalOctetsReceived, raqmonDsTotalOctetsSent, raqmonDsCumulativePacketLoss, raqmonDsPacketLossFraction, raqmonDsCumulativeDiscards, raqmonDsDiscardsFraction, raqmonDsCpuUtilization, raqmonDsMemoryUtilization It is RECOMMENDED to keep the size of a notification within the MTU size limits in order to avoid fragmentation.
.1.3.6.1.2.1.16.32.0.3,RAQMON-RDS-MIB::raqmonDsByeNotification,,,,,,The BYE Notification. This Notification is the equivalent of the RAQMON NULL PDU, which signals the end of a RAQMON session.
.1.3.6.1.2.1.16.32.1,RAQMON-RDS-MIB::raqmonDsMIBObjects,,,,,,
.1.3.6.1.2.1.16.32.1.1,RAQMON-RDS-MIB::raqmonDsNotificationTable,,not-accessible,,current,,This conceptual table provides the SNMP mapping of the RAQMON BASIC PDU. It is indexed by the RAQMON Data Source, sub-session, and address of the peer entity. Note that there is no concern about the indexation of this table exceeding the limits defined by RFC 2578 Section 3.5. According to [RFC4710], Section 5.1, only IPv4 and IPv6 addresses can be reported as participant addresses.
.1.3.6.1.2.1.16.32.1.1.1,RAQMON-RDS-MIB::raqmonDsNotificationEntry,,not-accessible,raqmonDsDSRC:raqmonDsRCN:raqmonDsPeerAddrType:raqmonDsPeerAddr,current,,The entry (row) is not retrievable and is not kept by RDSs. It serves data organization purposes only.
.1.3.6.1.2.1.16.32.1.1.1.1,RAQMON-RDS-MIB::raqmonDsDSRC,Unsigned32,not-accessible,,current,,Data Source identifier represents a unique session descriptor that points to a specific session between communicating entities. Identifiers unique for sessions conducted between two entities are generated by the communicating entities. Zero is a valid value, with no special semantics.
.1.3.6.1.2.1.16.32.1.1.1.2,RAQMON-RDS-MIB::raqmonDsRCN,Unsigned32,not-accessible,,current,,The Record Count Number indicates a sub-session within a communication session. A maximum number of 16 sub-sessions are supported; this limitation is dictated by reasons of compatibility with other transport protocols.
.1.3.6.1.2.1.16.32.1.1.1.3,RAQMON-RDS-MIB::raqmonDsPeerAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the Internet address of the peer participant for this session.
.1.3.6.1.2.1.16.32.1.1.1.4,RAQMON-RDS-MIB::raqmonDsPeerAddr,OCTET,not-accessible,,current,,The Internet Address of the peer participant for this session.
.1.3.6.1.2.1.16.32.1.1.1.5,RAQMON-RDS-MIB::raqmonDsAppName,OCTET,accessible-for-notify,,current,,This is a text string giving the name and possibly the version of the application associated with that session, e.g., 'XYZ VoIP Agent 1.2'.
.1.3.6.1.2.1.16.32.1.1.1.6,RAQMON-RDS-MIB::raqmonDsDataSourceDevicePort,Unsigned32,accessible-for-notify,,current,,The port number from which data for this session was sent by the Data Source device.
.1.3.6.1.2.1.16.32.1.1.1.7,RAQMON-RDS-MIB::raqmonDsReceiverDevicePort,Unsigned32,accessible-for-notify,,current,,The port number where the data for this session was received.
.1.3.6.1.2.1.16.32.1.1.1.8,RAQMON-RDS-MIB::raqmonDsSessionSetupDateTime,OCTET,accessible-for-notify,,current,,The time when session was initiated.
.1.3.6.1.2.1.16.32.1.1.1.9,RAQMON-RDS-MIB::raqmonDsSessionSetupDelay,Unsigned32,accessible-for-notify,,current,,Session setup time.
.1.3.6.1.2.1.16.32.1.1.1.10,RAQMON-RDS-MIB::raqmonDsSessionDuration,Unsigned32,accessible-for-notify,,current,,Session duration, including setup time. The SYNTAX of this object allows expression of the duration of sessions that do not exceed 4660 hours and 20 minutes.
.1.3.6.1.2.1.16.32.1.1.1.11,RAQMON-RDS-MIB::raqmonDsSessionSetupStatus,OCTET,accessible-for-notify,,current,,Describes appropriate communication session states, e.g., Call Established successfully, RSVP reservation failed, etc.
.1.3.6.1.2.1.16.32.1.1.1.12,RAQMON-RDS-MIB::raqmonDsRoundTripEndToEndNetDelay,Unsigned32,accessible-for-notify,,current,,Most recent available information about the round-trip end-to-end network delay.
.1.3.6.1.2.1.16.32.1.1.1.13,RAQMON-RDS-MIB::raqmonDsOneWayEndToEndNetDelay,Unsigned32,accessible-for-notify,,current,,Most recent available information about the one-way end-to-end network delay.
.1.3.6.1.2.1.16.32.1.1.1.14,RAQMON-RDS-MIB::raqmonDsApplicationDelay,Unsigned32,accessible-for-notify,,current,,Most recent available information about the application delay.
.1.3.6.1.2.1.16.32.1.1.1.15,RAQMON-RDS-MIB::raqmonDsInterArrivalJitter,Unsigned32,accessible-for-notify,,current,,An estimate of the inter-arrival jitter.
.1.3.6.1.2.1.16.32.1.1.1.16,RAQMON-RDS-MIB::raqmonDsIPPacketDelayVariation,Unsigned32,accessible-for-notify,,current,,An estimate of the inter-arrival delay variation.
.1.3.6.1.2.1.16.32.1.1.1.17,RAQMON-RDS-MIB::raqmonDsTotalPacketsReceived,Counter32,accessible-for-notify,,current,,The number of packets transmitted within a communication session by the receiver since the start of the session.
.1.3.6.1.2.1.16.32.1.1.1.18,RAQMON-RDS-MIB::raqmonDsTotalPacketsSent,Counter32,accessible-for-notify,,current,,The number of packets transmitted within a communication session by the sender since the start of the session.
.1.3.6.1.2.1.16.32.1.1.1.19,RAQMON-RDS-MIB::raqmonDsTotalOctetsReceived,Counter32,accessible-for-notify,,current,,The total number of payload octets (i.e., not including header or padding octets) transmitted in packets by the receiver within a communication session since the start of the session.
.1.3.6.1.2.1.16.32.1.1.1.20,RAQMON-RDS-MIB::raqmonDsTotalOctetsSent,Counter32,accessible-for-notify,,current,,The number of payload octets (i.e., not including headers or padding) transmitted in packets by the sender within a communication sub-session since the start of the session.
.1.3.6.1.2.1.16.32.1.1.1.21,RAQMON-RDS-MIB::raqmonDsCumulativePacketLoss,Counter32,accessible-for-notify,,current,,The number of packets from this session whose loss had been detected since the start of the session.
.1.3.6.1.2.1.16.32.1.1.1.22,RAQMON-RDS-MIB::raqmonDsPacketLossFraction,Unsigned32,accessible-for-notify,,current,,The percentage of lost packets with respect to the overall packets sent. This is defined to be 100 times the number of packets lost divided by the number of packets expected.
.1.3.6.1.2.1.16.32.1.1.1.23,RAQMON-RDS-MIB::raqmonDsCumulativeDiscards,Counter32,accessible-for-notify,,current,,The number of packet discards detected since the start of the session.
.1.3.6.1.2.1.16.32.1.1.1.24,RAQMON-RDS-MIB::raqmonDsDiscardsFraction,Unsigned32,accessible-for-notify,,current,,The percentage of discards with respect to the overall packets sent. This is defined to be 100 times the number of discards divided by the number of packets expected.
.1.3.6.1.2.1.16.32.1.1.1.25,RAQMON-RDS-MIB::raqmonDsSourcePayloadType,Unsigned32,accessible-for-notify,,current,,The payload type of the packet sent by this RDS.
.1.3.6.1.2.1.16.32.1.1.1.26,RAQMON-RDS-MIB::raqmonDsReceiverPayloadType,Unsigned32,accessible-for-notify,,current,,The payload type of the packet received by this RDS.
.1.3.6.1.2.1.16.32.1.1.1.27,RAQMON-RDS-MIB::raqmonDsSourceLayer2Priority,Unsigned32,accessible-for-notify,,current,,Source Layer 2 priority used by the data source to send packets to the receiver by this data source during this communication session.
.1.3.6.1.2.1.16.32.1.1.1.28,RAQMON-RDS-MIB::raqmonDsSourceDscp,Integer32,accessible-for-notify,,current,,Layer 3 TOS/DSCP values used by the Data Source to prioritize traffic sent.
.1.3.6.1.2.1.16.32.1.1.1.29,RAQMON-RDS-MIB::raqmonDsDestinationLayer2Priority,Unsigned32,accessible-for-notify,,current,,Destination Layer 2 priority. This is the priority used by the peer communicating entity to send packets to the data source.
.1.3.6.1.2.1.16.32.1.1.1.30,RAQMON-RDS-MIB::raqmonDsDestinationDscp,Integer32,accessible-for-notify,,current,,Layer 3 TOS/DSCP values used by the peer communicating entity to prioritize traffic sent to the source.
.1.3.6.1.2.1.16.32.1.1.1.31,RAQMON-RDS-MIB::raqmonDsCpuUtilization,Unsigned32,accessible-for-notify,,current,,Latest available information about the total CPU utilization.
.1.3.6.1.2.1.16.32.1.1.1.32,RAQMON-RDS-MIB::raqmonDsMemoryUtilization,Unsigned32,accessible-for-notify,,current,,Latest available information about the total memory utilization.
.1.3.6.1.2.1.16.32.2,RAQMON-RDS-MIB::raqmonDsConformance,,,,,,
.1.3.6.1.2.1.16.32.2.1,RAQMON-RDS-MIB::raqmonDsCompliance,,,,,,
.1.3.6.1.2.1.16.32.2.1.1,RAQMON-RDS-MIB::raqmonDsBasicCompliance,,,,,,The compliance statement for SNMP entities that implement this MIB module. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT raqmonDsPeerAddrType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. -- -- OBJECT raqmonDsPeerAddr -- SYNTAX InetAddress (SIZE(4|16)) -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. -- 
.1.3.6.1.2.1.16.32.2.2,RAQMON-RDS-MIB::raqmonDsGroups,,,,,,
.1.3.6.1.2.1.16.32.2.2.1,RAQMON-RDS-MIB::raqmonDsNotificationGroup,,,,,,Standard RAQMON Data Source Notification group.
.1.3.6.1.2.1.16.32.2.2.2,RAQMON-RDS-MIB::raqmonDsPayloadGroup,,,,,,Standard RAQMON Data Source payload MIB objects group.
.1.3.6.1.2.1.17,BRIDGE-MIB::dot1dBridge,,,,,,The Bridge MIB module for managing devices that support IEEE 802.1D. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4188; see the RFC itself for full legal notices.
.1.3.6.1.2.1.17.0,BRIDGE-MIB::dot1dNotifications,,,,,,
.1.3.6.1.2.1.17.0.1,BRIDGE-MIB::newRoot,,,,,,The newRoot trap indicates that the sending agent has become the new root of the Spanning Tree; the trap is sent by a bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer, immediately subsequent to its election. Implementation of this trap is optional.
.1.3.6.1.2.1.17.0.2,BRIDGE-MIB::topologyChange,,,,,,A topologyChange trap is sent by a bridge when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a newRoot trap is sent for the same transition. Implementation of this trap is optional.
.1.3.6.1.2.1.17.1,BRIDGE-MIB::dot1dBase,,,,,,
.1.3.6.1.2.1.17.1.1,BRIDGE-MIB::dot1dBaseBridgeAddress,OCTET,read-only,,current,,The MAC address used by this bridge when it must be referred to in a unique fashion. It is recommended that this be the numerically smallest MAC address of all ports that belong to this bridge. However, it is only required to be unique. When concatenated with dot1dStpPriority, a unique BridgeIdentifier is formed, which is used in the Spanning Tree Protocol.
.1.3.6.1.2.1.17.1.2,BRIDGE-MIB::dot1dBaseNumPorts,Integer32,read-only,,current,,The number of ports controlled by this bridging entity.
.1.3.6.1.2.1.17.1.3,BRIDGE-MIB::dot1dBaseType,INTEGER,read-only,,current,unknown(1):transparent-only(2):sourceroute-only(3):srt(4),Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging, this will be indicated by entries in the port table for the given type.
.1.3.6.1.2.1.17.1.4,BRIDGE-MIB::dot1dBasePortTable,,not-accessible,,current,,A table that contains generic information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included.
.1.3.6.1.2.1.17.1.4.1,BRIDGE-MIB::dot1dBasePortEntry,,not-accessible,dot1dBasePort,current,,A list of information for each port of the bridge.
.1.3.6.1.2.1.17.1.4.1.1,BRIDGE-MIB::dot1dBasePort,Integer32,read-only,,current,,The port number of the port for which this entry contains bridge management information.
.1.3.6.1.2.1.17.1.4.1.2,BRIDGE-MIB::dot1dBasePortIfIndex,Integer32,read-only,,current,,The value of the instance of the ifIndex object, defined in IF-MIB, for the interface corresponding to this port.
.1.3.6.1.2.1.17.1.4.1.3,BRIDGE-MIB::dot1dBasePortCircuit,OBJECT,read-only,,current,,For a port that (potentially) has the same value of dot1dBasePortIfIndex as another port on the same bridge. This object contains the name of an object instance unique to this port. For example, in the case where multiple ports correspond one-to-one with multiple X.25 virtual circuits, this value might identify an (e.g., the first) object instance associated with the X.25 virtual circuit corresponding to this port. For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value { 0 0 }.
.1.3.6.1.2.1.17.1.4.1.4,BRIDGE-MIB::dot1dBasePortDelayExceededDiscards,Counter32,read-only,,current,,The number of frames discarded by this port due to excessive transit delay through the bridge. It is incremented by both transparent and source route bridges.
.1.3.6.1.2.1.17.1.4.1.5,BRIDGE-MIB::dot1dBasePortMtuExceededDiscards,Counter32,read-only,,current,,The number of frames discarded by this port due to an excessive size. It is incremented by both transparent and source route bridges.
.1.3.6.1.2.1.17.2,BRIDGE-MIB::dot1dStp,,,,,,
.1.3.6.1.2.1.17.2.1,BRIDGE-MIB::dot1dStpProtocolSpecification,INTEGER,read-only,,current,unknown(1):decLb100(2):ieee8021d(3),An indication of what version of the Spanning Tree Protocol is being run. The value 'decLb100(2)' indicates the DEC LANbridge 100 Spanning Tree protocol. IEEE 802.1D implementations will return 'ieee8021d(3)'. If future versions of the IEEE Spanning Tree Protocol that are incompatible with the current version are released a new value will be defined.
.1.3.6.1.2.1.17.2.2,BRIDGE-MIB::dot1dStpPriority,Integer32,read-write,,current,,The value of the write-able portion of the Bridge ID (i.e., the first two octets of the (8 octet long) Bridge ID). The other (last) 6 octets of the Bridge ID are given by the value of dot1dBaseBridgeAddress. On bridges supporting IEEE 802.1t or IEEE 802.1w, permissible values are 0-61440, in steps of 4096.
.1.3.6.1.2.1.17.2.3,BRIDGE-MIB::dot1dStpTimeSinceTopologyChange,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last time a topology change was detected by the bridge entity. For RSTP, this reports the time since the tcWhile timer for any port on this Bridge was nonzero.
.1.3.6.1.2.1.17.2.4,BRIDGE-MIB::dot1dStpTopChanges,Counter32,read-only,,current,,The total number of topology changes detected by this bridge since the management entity was last reset or initialized.
.1.3.6.1.2.1.17.2.5,BRIDGE-MIB::dot1dStpDesignatedRoot,OCTET,read-only,,current,,The bridge identifier of the root of the spanning tree, as determined by the Spanning Tree Protocol, as executed by this node. This value is used as the Root Identifier parameter in all Configuration Bridge PDUs originated by this node.
.1.3.6.1.2.1.17.2.6,BRIDGE-MIB::dot1dStpRootCost,Integer32,read-only,,current,,The cost of the path to the root as seen from this bridge.
.1.3.6.1.2.1.17.2.7,BRIDGE-MIB::dot1dStpRootPort,Integer32,read-only,,current,,The port number of the port that offers the lowest cost path from this bridge to the root bridge.
.1.3.6.1.2.1.17.2.8,BRIDGE-MIB::dot1dStpMaxAge,Integer32,read-only,,current,,The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this bridge is currently using.
.1.3.6.1.2.1.17.2.9,BRIDGE-MIB::dot1dStpHelloTime,Integer32,read-only,,current,,The amount of time between the transmission of Configuration bridge PDUs by this node on any port when it is the root of the spanning tree, or trying to become so, in units of hundredths of a second. This is the actual value that this bridge is currently using.
.1.3.6.1.2.1.17.2.10,BRIDGE-MIB::dot1dStpHoldTime,Integer32,read-only,,current,,This time value determines the interval length during which no more than two Configuration bridge PDUs shall be transmitted by this node, in units of hundredths of a second.
.1.3.6.1.2.1.17.2.11,BRIDGE-MIB::dot1dStpForwardDelay,Integer32,read-only,,current,,This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the Listening and Learning states, which precede the Forwarding state. This value is also used when a topology change has been detected and is underway, to age all dynamic entries in the Forwarding Database. [Note that this value is the one that this bridge is currently using, in contrast to dot1dStpBridgeForwardDelay, which is the value that this bridge and all others would start using if/when this bridge were to become the root.]
.1.3.6.1.2.1.17.2.12,BRIDGE-MIB::dot1dStpBridgeMaxAge,Integer32,read-write,,current,,The value that all bridges use for MaxAge when this bridge is acting as the root. Note that 802.1D-1998 specifies that the range for this parameter is related to the value of dot1dStpBridgeHelloTime. The granularity of this timer is specified by 802.1D-1998 to be 1 second. An agent may return a badValue error if a set is attempted to a value that is not a whole number of seconds.
.1.3.6.1.2.1.17.2.13,BRIDGE-MIB::dot1dStpBridgeHelloTime,Integer32,read-write,,current,,The value that all bridges use for HelloTime when this bridge is acting as the root. The granularity of this timer is specified by 802.1D-1998 to be 1 second. An agent may return a badValue error if a set is attempted to a value that is not a whole number of seconds.
.1.3.6.1.2.1.17.2.14,BRIDGE-MIB::dot1dStpBridgeForwardDelay,Integer32,read-write,,current,,The value that all bridges use for ForwardDelay when this bridge is acting as the root. Note that 802.1D-1998 specifies that the range for this parameter is related to the value of dot1dStpBridgeMaxAge. The granularity of this timer is specified by 802.1D-1998 to be 1 second. An agent may return a badValue error if a set is attempted to a value that is not a whole number of seconds.
.1.3.6.1.2.1.17.2.15,BRIDGE-MIB::dot1dStpPortTable,,not-accessible,,current,,A table that contains port-specific information for the Spanning Tree Protocol.
.1.3.6.1.2.1.17.2.15.1,BRIDGE-MIB::dot1dStpPortEntry,,not-accessible,dot1dStpPort,current,,A list of information maintained by every port about the Spanning Tree Protocol state for that port.
.1.3.6.1.2.1.17.2.15.1.1,BRIDGE-MIB::dot1dStpPort,Integer32,read-only,,current,,The port number of the port for which this entry contains Spanning Tree Protocol management information.
.1.3.6.1.2.1.17.2.15.1.2,BRIDGE-MIB::dot1dStpPortPriority,Integer32,read-write,,current,,The value of the priority field that is contained in the first (in network byte order) octet of the (2 octet long) Port ID. The other octet of the Port ID is given by the value of dot1dStpPort. On bridges supporting IEEE 802.1t or IEEE 802.1w, permissible values are 0-240, in steps of 16.
.1.3.6.1.2.1.17.2.15.1.3,BRIDGE-MIB::dot1dStpPortState,INTEGER,read-only,,current,disabled(1):blocking(2):listening(3):learning(4):forwarding(5):broken(6),The port's current state, as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning, it will place that port into the broken(6) state. For ports that are disabled (see dot1dStpPortEnable), this object will have a value of disabled(1).
.1.3.6.1.2.1.17.2.15.1.4,BRIDGE-MIB::dot1dStpPortEnable,INTEGER,read-write,,current,enabled(1):disabled(2),The enabled/disabled status of the port.
.1.3.6.1.2.1.17.2.15.1.5,BRIDGE-MIB::dot1dStpPortPathCost,Integer32,read-write,,current,,The contribution of this port to the path cost of paths towards the spanning tree root which include this port. 802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN. New implementations should support dot1dStpPortPathCost32. If the port path costs exceeds the maximum value of this object then this object should report the maximum value, namely 65535. Applications should try to read the dot1dStpPortPathCost32 object if this object reports the maximum value.
.1.3.6.1.2.1.17.2.15.1.6,BRIDGE-MIB::dot1dStpPortDesignatedRoot,OCTET,read-only,,current,,The unique Bridge Identifier of the Bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached.
.1.3.6.1.2.1.17.2.15.1.7,BRIDGE-MIB::dot1dStpPortDesignatedCost,Integer32,read-only,,current,,The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs.
.1.3.6.1.2.1.17.2.15.1.8,BRIDGE-MIB::dot1dStpPortDesignatedBridge,OCTET,read-only,,current,,The Bridge Identifier of the bridge that this port considers to be the Designated Bridge for this port's segment.
.1.3.6.1.2.1.17.2.15.1.9,BRIDGE-MIB::dot1dStpPortDesignatedPort,OCTET,read-only,,current,,The Port Identifier of the port on the Designated Bridge for this port's segment.
.1.3.6.1.2.1.17.2.15.1.10,BRIDGE-MIB::dot1dStpPortForwardTransitions,Counter32,read-only,,current,,The number of times this port has transitioned from the Learning state to the Forwarding state.
.1.3.6.1.2.1.17.2.15.1.11,BRIDGE-MIB::dot1dStpPortPathCost32,Integer32,read-write,,current,,The contribution of this port to the path cost of paths towards the spanning tree root which include this port. 802.1D-1998 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN. This object replaces dot1dStpPortPathCost to support IEEE 802.1t.
.1.3.6.1.2.1.17.2.16,RSTP-MIB::dot1dStpVersion,INTEGER,read-write,,current,stpCompatible(0):rstp(2),The version of Spanning Tree Protocol the bridge is currently running. The value 'stpCompatible(0)' indicates the Spanning Tree Protocol specified in IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid Spanning Tree Protocol specified in IEEE 802.1w and clause 17 of 802.1D-2004. The values are directly from the IEEE standard. New values may be defined as future versions of the protocol become available. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.2.17,RSTP-MIB::dot1dStpTxHoldCount,Integer32,read-write,,current,,The value used by the Port Transmit state machine to limit the maximum transmission rate. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.2.19,RSTP-MIB::dot1dStpExtPortTable,,not-accessible,,current,,A table that contains port-specific Rapid Spanning Tree information.
.1.3.6.1.2.1.17.2.19.1,RSTP-MIB::dot1dStpExtPortEntry,,not-accessible,,current,,A list of Rapid Spanning Tree information maintained by each port.
.1.3.6.1.2.1.17.2.19.1.1,RSTP-MIB::dot1dStpPortProtocolMigration,INTEGER,read-write,,current,true(1):false(2),When operating in RSTP (version 2) mode, writing true(1) to this object forces this port to transmit RSTP BPDUs. Any other operation on this object has no effect and it always returns false(2) when read.
.1.3.6.1.2.1.17.2.19.1.2,RSTP-MIB::dot1dStpPortAdminEdgePort,INTEGER,read-write,,current,true(1):false(2),The administrative value of the Edge Port parameter. A value of true(1) indicates that this port should be assumed as an edge-port, and a value of false(2) indicates that this port should be assumed as a non-edge-port. Setting this object will also cause the corresponding instance of dot1dStpPortOperEdgePort to change to the same value. Note that even when this object's value is true, the value of the corresponding instance of dot1dStpPortOperEdgePort can be false if a BPDU has been received. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.2.19.1.3,RSTP-MIB::dot1dStpPortOperEdgePort,INTEGER,read-only,,current,true(1):false(2),The operational value of the Edge Port parameter. The object is initialized to the value of the corresponding instance of dot1dStpPortAdminEdgePort. When the corresponding instance of dot1dStpPortAdminEdgePort is set, this object will be changed as well. This object will also be changed to false on reception of a BPDU.
.1.3.6.1.2.1.17.2.19.1.4,RSTP-MIB::dot1dStpPortAdminPointToPoint,INTEGER,read-write,,current,forceTrue(0):forceFalse(1):auto(2),The administrative point-to-point status of the LAN segment attached to this port, using the enumeration values of the IEEE 802.1w clause. A value of forceTrue(0) indicates that this port should always be treated as if it is connected to a point-to-point link. A value of forceFalse(1) indicates that this port should be treated as having a shared media connection. A value of auto(2) indicates that this port is considered to have a point-to-point link if it is an Aggregator and all of its members are aggregatable, or if the MAC entity is configured for full duplex operation, either through auto-negotiation or by management means. Manipulating this object changes the underlying adminPortToPortMAC. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.2.19.1.5,RSTP-MIB::dot1dStpPortOperPointToPoint,INTEGER,read-only,,current,true(1):false(2),The operational point-to-point status of the LAN segment attached to this port. It indicates whether a port is considered to have a point-to-point connection. If adminPointToPointMAC is set to auto(2), then the value of operPointToPointMAC is determined in accordance with the specific procedures defined for the MAC entity concerned, as defined in IEEE 802.1w, clause 6.5. The value is determined dynamically; that is, it is re-evaluated whenever the value of adminPointToPointMAC changes, and whenever the specific procedures defined for the MAC entity evaluate a change in its point-to-point status.
.1.3.6.1.2.1.17.2.19.1.6,RSTP-MIB::dot1dStpPortAdminPathCost,Integer32,read-write,,current,,The administratively assigned value for the contribution of this port to the path cost of paths toward the spanning tree root. Writing a value of '0' assigns the automatically calculated default Path Cost value to the port. If the default Path Cost is being used, this object returns '0' when read. This complements the object dot1dStpPortPathCost or dot1dStpPortPathCost32, which returns the operational value of the path cost. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.3,BRIDGE-MIB::dot1dSr,,,,,,
.1.3.6.1.2.1.17.3.1,SOURCE-ROUTING-MIB::dot1dSrPortTable,,not-accessible,,mandatory,,A table that contains information about every port that is associated with this source route bridge.
.1.3.6.1.2.1.17.3.1.1,SOURCE-ROUTING-MIB::dot1dSrPortEntry,,not-accessible,dot1dSrPort,mandatory,,A list of information for each port of a source route bridge.
.1.3.6.1.2.1.17.3.1.1.1,SOURCE-ROUTING-MIB::dot1dSrPort,INTEGER,read-only,,mandatory,,The port number of the port for which this entry contains Source Route management information.
.1.3.6.1.2.1.17.3.1.1.2,SOURCE-ROUTING-MIB::dot1dSrPortHopCount,INTEGER,read-write,,mandatory,,The maximum number of routing descriptors allowed in an All Paths or Spanning Tree Explorer frames.
.1.3.6.1.2.1.17.3.1.1.3,SOURCE-ROUTING-MIB::dot1dSrPortLocalSegment,INTEGER,read-write,,mandatory,,The segment number that uniquely identifies the segment to which this port is connected. Current source routing protocols limit this value to the range: 0 through 4095. (The value 0 is used by some management applications for special test cases.) A value of 65535 signifies that no segment number is assigned to this port.
.1.3.6.1.2.1.17.3.1.1.4,SOURCE-ROUTING-MIB::dot1dSrPortBridgeNum,INTEGER,read-write,,mandatory,,A bridge number uniquely identifies a bridge when more than one bridge is used to span the same two segments. Current source routing protocols limit this value to the range: 0 through 15. A value of 65535 signifies that no bridge number is assigned to this bridge.
.1.3.6.1.2.1.17.3.1.1.5,SOURCE-ROUTING-MIB::dot1dSrPortTargetSegment,INTEGER,read-write,,mandatory,,The segment number that corresponds to the target segment this port is considered to be connected to by the bridge. Current source routing protocols limit this value to the range: 0 through 4095. (The value 0 is used by some management applications for special test cases.) A value of 65535 signifies that no target segment is assigned to this port.
.1.3.6.1.2.1.17.3.1.1.6,SOURCE-ROUTING-MIB::dot1dSrPortLargestFrame,INTEGER,read-write,,mandatory,,The maximum size of the INFO field (LLC and above) that this port can send/receive. It does not include any MAC level (framing) octets. The value of this object is used by this bridge to determine whether a modification of the LargestFrame (LF, see [14]) field of the Routing Control field of the Routing Information Field is necessary. 64 valid values are defined by the IEEE 802.5M SRT Addendum: 516, 635, 754, 873, 993, 1112, 1231, 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906, 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812, 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197, 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587, 10997, 11407, 12199, 12992, 13785, 14578, 15370, 16163, 16956, 17749, 20730, 23711, 26693, 29674, 32655, 35637, 38618, 41600, 44591, 47583, 50575, 53567, 56559, 59551, and 65535. An illegal value will not be accepted by the bridge.
.1.3.6.1.2.1.17.3.1.1.7,SOURCE-ROUTING-MIB::dot1dSrPortSTESpanMode,INTEGER,read-write,,mandatory,auto-span(1):disabled(2):forced(3),Determines how this port behaves when presented with a Spanning Tree Explorer frame. The value 'disabled(2)' indicates that the port will not accept or send Spanning Tree Explorer packets; any STE packets received will be silently discarded. The value 'forced(3)' indicates the port will always accept and propagate Spanning Tree Explorer frames. This allows a manually configured Spanning Tree for this class of packet to be configured. Note that unlike transparent bridging, this is not catastrophic to the network if there are loops. The value 'auto-span(1)' can only be returned by a bridge that both implements the Spanning Tree Protocol and has use of the protocol enabled on this port. The behavior of the port for Spanning Tree Explorer frames is determined by the state of dot1dStpPortState. If the port is in the 'forwarding' state, the frame will be accepted or propagated. Otherwise, it will be silently discarded.
.1.3.6.1.2.1.17.3.1.1.8,SOURCE-ROUTING-MIB::dot1dSrPortSpecInFrames,Counter32,read-only,,mandatory,,The number of Specifically Routed frames, also referred to as Source Routed Frames, that have been received from this port's segment.
.1.3.6.1.2.1.17.3.1.1.9,SOURCE-ROUTING-MIB::dot1dSrPortSpecOutFrames,Counter32,read-only,,mandatory,,The number of Specifically Routed frames, also referred to as Source Routed Frames, that this port has transmitted on its segment.
.1.3.6.1.2.1.17.3.1.1.10,SOURCE-ROUTING-MIB::dot1dSrPortApeInFrames,Counter32,read-only,,mandatory,,The number of All Paths Explorer frames, also referred to as All Routes Explorer frames, that have been received by this port from its segment.
.1.3.6.1.2.1.17.3.1.1.11,SOURCE-ROUTING-MIB::dot1dSrPortApeOutFrames,Counter32,read-only,,mandatory,,The number of all Paths Explorer Frames, also referred to as All Routes Explorer frames, that have been transmitted by this port on its segment.
.1.3.6.1.2.1.17.3.1.1.12,SOURCE-ROUTING-MIB::dot1dSrPortSteInFrames,Counter32,read-only,,mandatory,,The number of spanning tree explorer frames that have been received by this port from its segment.
.1.3.6.1.2.1.17.3.1.1.13,SOURCE-ROUTING-MIB::dot1dSrPortSteOutFrames,Counter32,read-only,,mandatory,,The number of spanning tree explorer frames that have been transmitted by this port on its segment.
.1.3.6.1.2.1.17.3.1.1.14,SOURCE-ROUTING-MIB::dot1dSrPortSegmentMismatchDiscards,Counter32,read-only,,mandatory,,The number of explorer frames that have been discarded by this port because the routing descriptor field contained an invalid adjacent segment value.
.1.3.6.1.2.1.17.3.1.1.15,SOURCE-ROUTING-MIB::dot1dSrPortDuplicateSegmentDiscards,Counter32,read-only,,mandatory,,The number of frames that have been discarded by this port because the routing descriptor field contained a duplicate segment identifier.
.1.3.6.1.2.1.17.3.1.1.16,SOURCE-ROUTING-MIB::dot1dSrPortHopCountExceededDiscards,Counter32,read-only,,mandatory,,The number of explorer frames that have been discarded by this port because the Routing Information Field has exceeded the maximum route descriptor length.
.1.3.6.1.2.1.17.3.1.1.17,SOURCE-ROUTING-MIB::dot1dSrPortDupLanIdOrTreeErrors,Counter32,read-only,,mandatory,,The number of duplicate LAN IDs or Tree errors. This helps in detection of problems in networks containing older IBM Source Routing Bridges.
.1.3.6.1.2.1.17.3.1.1.18,SOURCE-ROUTING-MIB::dot1dSrPortLanIdMismatches,Counter32,read-only,,mandatory,,The number of ARE and STE frames that were discarded because the last LAN ID in the routing information field did not equal the LAN-in ID. This error can occur in implementations which do only a LAN-in ID and Bridge Number check instead of a LAN-in ID, Bridge Number, and LAN-out ID check before they forward broadcast frames.
.1.3.6.1.2.1.17.3.2,SOURCE-ROUTING-MIB::dot1dSrBridgeLfMode,INTEGER,read-write,,mandatory,mode3(1):mode6(2),Indicates whether the bridge operates using older 3 bit length negotiation fields or the newer 6 bit length field in its RIF.
.1.3.6.1.2.1.17.4,BRIDGE-MIB::dot1dTp,,,,,,
.1.3.6.1.2.1.17.4.1,BRIDGE-MIB::dot1dTpLearnedEntryDiscards,Counter32,read-only,,current,,The total number of Forwarding Database entries that have been or would have been learned, but have been discarded due to a lack of storage space in the Forwarding Database. If this counter is increasing, it indicates that the Forwarding Database is regularly becoming full (a condition that has unpleasant performance effects on the subnetwork). If this counter has a significant value but is not presently increasing, it indicates that the problem has been occurring but is not persistent.
.1.3.6.1.2.1.17.4.2,BRIDGE-MIB::dot1dTpAgingTime,Integer32,read-write,,current,,The timeout period in seconds for aging out dynamically-learned forwarding information. 802.1D-1998 recommends a default of 300 seconds.
.1.3.6.1.2.1.17.4.3,BRIDGE-MIB::dot1dTpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.
.1.3.6.1.2.1.17.4.3.1,BRIDGE-MIB::dot1dTpFdbEntry,,not-accessible,dot1dTpFdbAddress,current,,Information about a specific unicast MAC address for which the bridge has some forwarding and/or filtering information.
.1.3.6.1.2.1.17.4.3.1.1,BRIDGE-MIB::dot1dTpFdbAddress,OCTET,read-only,,current,,A unicast MAC address for which the bridge has forwarding and/or filtering information.
.1.3.6.1.2.1.17.4.3.1.2,BRIDGE-MIB::dot1dTpFdbPort,Integer32,read-only,,current,,Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1dTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned, but that the bridge does have some forwarding/filtering information about this address (e.g., in the dot1dStaticTable). Implementors are encouraged to assign the port value to this object whenever it is learned, even for addresses for which the corresponding value of dot1dTpFdbStatus is not learned(3).
.1.3.6.1.2.1.17.4.3.1.3,BRIDGE-MIB::dot1dTpFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5),The status of this entry. The meanings of the values are: other(1) - none of the following. This would include the case where some other MIB object (not the corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticTable) is being used to determine if and how frames addressed to the value of the corresponding instance of dot1dTpFdbAddress are being forwarded. invalid(2) - this entry is no longer valid (e.g., it was learned but has since aged out), but has not yet been flushed from the table. learned(3) - the value of the corresponding instance of dot1dTpFdbPort was learned, and is being used. self(4) - the value of the corresponding instance of dot1dTpFdbAddress represents one of the bridge's addresses. The corresponding instance of dot1dTpFdbPort indicates which of the bridge's ports has this address. mgmt(5) - the value of the corresponding instance of dot1dTpFdbAddress is also the value of an existing instance of dot1dStaticAddress.
.1.3.6.1.2.1.17.4.4,BRIDGE-MIB::dot1dTpPortTable,,not-accessible,,current,,A table that contains information about every port that is associated with this transparent bridge.
.1.3.6.1.2.1.17.4.4.1,BRIDGE-MIB::dot1dTpPortEntry,,not-accessible,dot1dTpPort,current,,A list of information for each port of a transparent bridge.
.1.3.6.1.2.1.17.4.4.1.1,BRIDGE-MIB::dot1dTpPort,Integer32,read-only,,current,,The port number of the port for which this entry contains Transparent bridging management information.
.1.3.6.1.2.1.17.4.4.1.2,BRIDGE-MIB::dot1dTpPortMaxInfo,Integer32,read-only,,current,,The maximum size of the INFO (non-MAC) field that this port will receive or transmit.
.1.3.6.1.2.1.17.4.4.1.3,BRIDGE-MIB::dot1dTpPortInFrames,Counter32,read-only,,current,,The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.4.1.4,BRIDGE-MIB::dot1dTpPortOutFrames,Counter32,read-only,,current,,The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.4.1.5,BRIDGE-MIB::dot1dTpPortInDiscards,Counter32,read-only,,current,,Count of received valid frames that were discarded (i.e., filtered) by the Forwarding Process.
.1.3.6.1.2.1.17.4.5,P-BRIDGE-MIB::dot1dTpHCPortTable,,not-accessible,,current,,A table that contains information about every high- capacity port that is associated with this transparent bridge.
.1.3.6.1.2.1.17.4.5.1,P-BRIDGE-MIB::dot1dTpHCPortEntry,,not-accessible,dot1dTpPort,current,,Statistics information for each high-capacity port of a transparent bridge.
.1.3.6.1.2.1.17.4.5.1.1,P-BRIDGE-MIB::dot1dTpHCPortInFrames,Counter64,read-only,,current,,The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.5.1.2,P-BRIDGE-MIB::dot1dTpHCPortOutFrames,Counter64,read-only,,current,,The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.
.1.3.6.1.2.1.17.4.5.1.3,P-BRIDGE-MIB::dot1dTpHCPortInDiscards,Counter64,read-only,,current,,Count of valid frames that have been received by this port from its segment that were discarded (i.e., filtered) by the Forwarding Process.
.1.3.6.1.2.1.17.4.6,P-BRIDGE-MIB::dot1dTpPortOverflowTable,,not-accessible,,current,,A table that contains the most-significant bits of statistics counters for ports that are associated with this transparent bridge that are on high-capacity interfaces, as defined in the conformance clauses for this table. This table is provided as a way to read 64-bit counters for agents that support only SNMPv1. Note that the reporting of most-significant and least-significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification.
.1.3.6.1.2.1.17.4.6.1,P-BRIDGE-MIB::dot1dTpPortOverflowEntry,,not-accessible,dot1dTpPort,current,,The most significant bits of statistics counters for a high- capacity interface of a transparent bridge. Each object is associated with a corresponding object in dot1dTpPortTable that indicates the least significant bits of the counter.
.1.3.6.1.2.1.17.4.6.1.1,P-BRIDGE-MIB::dot1dTpPortInOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1dTpPortInFrames counter has overflowed.
.1.3.6.1.2.1.17.4.6.1.2,P-BRIDGE-MIB::dot1dTpPortOutOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1dTpPortOutFrames counter has overflowed.
.1.3.6.1.2.1.17.4.6.1.3,P-BRIDGE-MIB::dot1dTpPortInOverflowDiscards,Counter32,read-only,,current,,The number of times the associated dot1dTpPortInDiscards counter has overflowed.
.1.3.6.1.2.1.17.5,BRIDGE-MIB::dot1dStatic,,,,,,
.1.3.6.1.2.1.17.5.1,BRIDGE-MIB::dot1dStaticTable,,not-accessible,,current,,A table containing filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific destination addresses are allowed to be forwarded. The value of zero in this table, as the port number from which frames with a specific destination address are received, is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast and for group/broadcast addresses.
.1.3.6.1.2.1.17.5.1.1,BRIDGE-MIB::dot1dStaticEntry,,not-accessible,dot1dStaticAddress:dot1dStaticReceivePort,current,,Filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from a specific port and containing a specific destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.5.1.1.1,BRIDGE-MIB::dot1dStaticAddress,OCTET,read-create,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object can take the value of a unicast address, a group address, or the broadcast address.
.1.3.6.1.2.1.17.5.1.1.2,BRIDGE-MIB::dot1dStaticReceivePort,Integer32,read-create,,current,,Either the value '0', or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.
.1.3.6.1.2.1.17.5.1.1.3,BRIDGE-MIB::dot1dStaticAllowedToGoTo,OCTET,read-create,,current,,The set of ports to which frames received from a specific port and destined for a specific MAC address, are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each port of the bridge is represented by a single bit within the value of this object. If that bit has a value of '1', then that port is included in the set of ports; the port is not included if its bit has a value of '0'. (Note that the setting of the bit corresponding to the port from which a frame is received is irrelevant.) The default value of this object is a string of ones of appropriate length. The value of this object may exceed the required minimum maximum message size of some SNMP transport (484 bytes, in the case of SNMP over UDP, see RFC 3417, section 3.2). SNMP engines on bridges supporting a large number of ports must support appropriate maximum message sizes.
.1.3.6.1.2.1.17.5.1.1.4,BRIDGE-MIB::dot1dStaticStatus,INTEGER,read-create,,current,other(1):invalid(2):permanent(3):deleteOnReset(4):deleteOnTimeout(5),This object indicates the status of this entry. The default value is permanent(3). other(1) - this entry is currently in use but the conditions under which it will remain so are different from each of the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out.
.1.3.6.1.2.1.17.6,P-BRIDGE-MIB::pBridgeMIB,,,,,,The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998, including Restricted Group Registration defined by IEEE 802.1t-2001. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4363; See the RFC itself for full legal notices.
.1.3.6.1.2.1.17.6.1,P-BRIDGE-MIB::pBridgeMIBObjects,,,,,,
.1.3.6.1.2.1.17.6.1.1,P-BRIDGE-MIB::dot1dExtBase,,,,,,
.1.3.6.1.2.1.17.6.1.1.1,P-BRIDGE-MIB::dot1dDeviceCapabilities,BITS,read-only,,current,dot1dExtendedFilteringServices(0):dot1dTrafficClasses(1):dot1qStaticEntryIndividualPort(2):dot1qIVLCapable(3):dot1qSVLCapable(4):dot1qHybridCapable(5):dot1qConfigurablePvidTagging(6):dot1dLocalVlanCapable(7),Indicates the optional parts of IEEE 802.1D and 802.1Q that are implemented by this device and are manageable through this MIB. Capabilities that are allowed on a per-port basis are indicated in dot1dPortCapabilities. dot1dExtendedFilteringServices(0), -- can perform filtering of -- individual multicast addresses -- controlled by GMRP. dot1dTrafficClasses(1), -- can map user priority to -- multiple traffic classes. dot1qStaticEntryIndividualPort(2), -- dot1qStaticUnicastReceivePort & -- dot1qStaticMulticastReceivePort -- can represent non-zero entries. dot1qIVLCapable(3), -- Independent VLAN Learning (IVL). dot1qSVLCapable(4), -- Shared VLAN Learning (SVL). dot1qHybridCapable(5), -- both IVL & SVL simultaneously. dot1qConfigurablePvidTagging(6), -- whether the implementation -- supports the ability to -- override the default PVID -- setting and its egress status -- (VLAN-Tagged or Untagged) on -- each port. dot1dLocalVlanCapable(7) -- can support multiple local -- bridges, outside of the scope -- of 802.1Q defined VLANs.
.1.3.6.1.2.1.17.6.1.1.2,P-BRIDGE-MIB::dot1dTrafficClassesEnabled,INTEGER,read-write,,current,true(1):false(2),The value true(1) indicates that Traffic Classes are enabled on this bridge. When false(2), the bridge operates with a single priority level for all traffic. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.1.3,P-BRIDGE-MIB::dot1dGmrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative status requested by management for GMRP. The value enabled(1) indicates that GMRP should be enabled on this device, in all VLANs, on all ports for which it has not been specifically disabled. When disabled(2), GMRP is disabled, in all VLANs and on all ports, and all GMRP packets will be forwarded transparently. This object affects both Applicant and Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all GMRP state machines on all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.1.4,P-BRIDGE-MIB::dot1dPortCapabilitiesTable,,not-accessible,,current,,A table that contains capabilities information about every port that is associated with this bridge.
.1.3.6.1.2.1.17.6.1.1.4.1,P-BRIDGE-MIB::dot1dPortCapabilitiesEntry,,not-accessible,,current,,A set of capabilities information about this port indexed by dot1dBasePort.
.1.3.6.1.2.1.17.6.1.1.4.1.1,P-BRIDGE-MIB::dot1dPortCapabilities,BITS,read-only,,current,dot1qDot1qTagging(0):dot1qConfigurableAcceptableFrameTypes(1):dot1qIngressFiltering(2),Indicates the parts of IEEE 802.1D and 802.1Q that are optional on a per-port basis, that are implemented by this device, and that are manageable through this MIB. dot1qDot1qTagging(0), -- supports 802.1Q VLAN tagging of -- frames and GVRP. dot1qConfigurableAcceptableFrameTypes(1), -- allows modified values of -- dot1qPortAcceptableFrameTypes. dot1qIngressFiltering(2) -- supports the discarding of any -- frame received on a Port whose -- VLAN classification does not -- include that Port in its Member -- set.
.1.3.6.1.2.1.17.6.1.2,P-BRIDGE-MIB::dot1dPriority,,,,,,
.1.3.6.1.2.1.17.6.1.2.1,P-BRIDGE-MIB::dot1dPortPriorityTable,,not-accessible,,current,,A table that contains information about every port that is associated with this transparent bridge.
.1.3.6.1.2.1.17.6.1.2.1.1,P-BRIDGE-MIB::dot1dPortPriorityEntry,,not-accessible,,current,,A list of Default User Priorities for each port of a transparent bridge. This is indexed by dot1dBasePort.
.1.3.6.1.2.1.17.6.1.2.1.1.1,P-BRIDGE-MIB::dot1dPortDefaultUserPriority,Integer32,read-write,,current,,The default ingress User Priority for this port. This only has effect on media, such as Ethernet, that do not support native User Priority. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.1.1.2,P-BRIDGE-MIB::dot1dPortNumTrafficClasses,Integer32,read-write,,current,,The number of egress traffic classes supported on this port. This object may optionally be read-only. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.2,P-BRIDGE-MIB::dot1dUserPriorityRegenTable,,not-accessible,,current,,A list of Regenerated User Priorities for each received User Priority on each port of a bridge. The Regenerated User Priority value may be used to index the Traffic Class Table for each input port. This only has effect on media that support native User Priority. The default values for Regenerated User Priorities are the same as the User Priorities.
.1.3.6.1.2.1.17.6.1.2.2.1,P-BRIDGE-MIB::dot1dUserPriorityRegenEntry,,not-accessible,dot1dBasePort:dot1dUserPriority,current,,A mapping of incoming User Priority to a Regenerated User Priority.
.1.3.6.1.2.1.17.6.1.2.2.1.1,P-BRIDGE-MIB::dot1dUserPriority,Integer32,not-accessible,,current,,The User Priority for a frame received on this port.
.1.3.6.1.2.1.17.6.1.2.2.1.2,P-BRIDGE-MIB::dot1dRegenUserPriority,Integer32,read-write,,current,,The Regenerated User Priority that the incoming User Priority is mapped to for this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.3,P-BRIDGE-MIB::dot1dTrafficClassTable,,not-accessible,,current,,A table mapping evaluated User Priority to Traffic Class, for forwarding by the bridge. Traffic class is a number in the range (0..(dot1dPortNumTrafficClasses-1)).
.1.3.6.1.2.1.17.6.1.2.3.1,P-BRIDGE-MIB::dot1dTrafficClassEntry,,not-accessible,dot1dBasePort:dot1dTrafficClassPriority,current,,User Priority to Traffic Class mapping.
.1.3.6.1.2.1.17.6.1.2.3.1.1,P-BRIDGE-MIB::dot1dTrafficClassPriority,Integer32,not-accessible,,current,,The Priority value determined for the received frame. This value is equivalent to the priority indicated in the tagged frame received, or one of the evaluated priorities, determined according to the media-type. For untagged frames received from Ethernet media, this value is equal to the dot1dPortDefaultUserPriority value for the ingress port. For untagged frames received from non-Ethernet media, this value is equal to the dot1dRegenUserPriority value for the ingress port and media-specific user priority.
.1.3.6.1.2.1.17.6.1.2.3.1.2,P-BRIDGE-MIB::dot1dTrafficClass,Integer32,read-write,,current,,The Traffic Class the received frame is mapped to. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.2.4,P-BRIDGE-MIB::dot1dPortOutboundAccessPriorityTable,,not-accessible,,current,,A table mapping Regenerated User Priority to Outbound Access Priority. This is a fixed mapping for all port types, with two options for 802.5 Token Ring.
.1.3.6.1.2.1.17.6.1.2.4.1,P-BRIDGE-MIB::dot1dPortOutboundAccessPriorityEntry,,not-accessible,dot1dBasePort:dot1dRegenUserPriority,current,,Regenerated User Priority to Outbound Access Priority mapping.
.1.3.6.1.2.1.17.6.1.2.4.1.1,P-BRIDGE-MIB::dot1dPortOutboundAccessPriority,Integer32,read-only,,current,,The Outbound Access Priority the received frame is mapped to.
.1.3.6.1.2.1.17.6.1.3,P-BRIDGE-MIB::dot1dGarp,,,,,,
.1.3.6.1.2.1.17.6.1.3.1,P-BRIDGE-MIB::dot1dPortGarpTable,,not-accessible,,current,,A table of GARP control information about every bridge port. This is indexed by dot1dBasePort.
.1.3.6.1.2.1.17.6.1.3.1.1,P-BRIDGE-MIB::dot1dPortGarpEntry,,not-accessible,,current,,GARP control information for a bridge port.
.1.3.6.1.2.1.17.6.1.3.1.1.1,P-BRIDGE-MIB::dot1dPortGarpJoinTime,INTEGER,read-write,,current,,The GARP Join time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.3.1.1.2,P-BRIDGE-MIB::dot1dPortGarpLeaveTime,INTEGER,read-write,,current,,The GARP Leave time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.3.1.1.3,P-BRIDGE-MIB::dot1dPortGarpLeaveAllTime,INTEGER,read-write,,current,,The GARP LeaveAll time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.4,P-BRIDGE-MIB::dot1dGmrp,,,,,,
.1.3.6.1.2.1.17.6.1.4.1,P-BRIDGE-MIB::dot1dPortGmrpTable,,not-accessible,,current,,A table of GMRP control and status information about every bridge port. Augments the dot1dBasePortTable.
.1.3.6.1.2.1.17.6.1.4.1.1,P-BRIDGE-MIB::dot1dPortGmrpEntry,,not-accessible,,current,,GMRP control and status information for a bridge port.
.1.3.6.1.2.1.17.6.1.4.1.1.1,P-BRIDGE-MIB::dot1dPortGmrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative state of GMRP operation on this port. The value enabled(1) indicates that GMRP is enabled on this port in all VLANs as long as dot1dGmrpStatus is also enabled(1). A value of disabled(2) indicates that GMRP is disabled on this port in all VLANs: any GMRP packets received will be silently discarded, and no GMRP registrations will be propagated from other ports. Setting this to a value of enabled(1) will be stored by the agent but will only take effect on the GMRP protocol operation if dot1dGmrpStatus also indicates the value enabled(1). This object affects all GMRP Applicant and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a reset of all GMRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.1.4.1.1.2,P-BRIDGE-MIB::dot1dPortGmrpFailedRegistrations,Counter32,read-only,,current,,The total number of failed GMRP registrations, for any reason, in all VLANs, on this port.
.1.3.6.1.2.1.17.6.1.4.1.1.3,P-BRIDGE-MIB::dot1dPortGmrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last GMRP message received on this port.
.1.3.6.1.2.1.17.6.1.4.1.1.4,P-BRIDGE-MIB::dot1dPortRestrictedGroupRegistration,INTEGER,read-write,,current,true(1):false(2),The state of Restricted Group Registration on this port. If the value of this control is true(1), then creation of a new dynamic entry is permitted only if there is a Static Filtering Entry for the VLAN concerned, in which the Registrar Administrative Control value is Normal Registration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.6.2,P-BRIDGE-MIB::pBridgeConformance,,,,,,
.1.3.6.1.2.1.17.6.2.1,P-BRIDGE-MIB::pBridgeGroups,,,,,,
.1.3.6.1.2.1.17.6.2.1.1,P-BRIDGE-MIB::pBridgeExtCapGroup,,,,,,A collection of objects indicating the optional capabilities of the device.
.1.3.6.1.2.1.17.6.2.1.2,P-BRIDGE-MIB::pBridgeDeviceGmrpGroup,,,,,,A collection of objects providing device-level control for the Multicast Filtering extended bridge services.
.1.3.6.1.2.1.17.6.2.1.3,P-BRIDGE-MIB::pBridgeDevicePriorityGroup,,,,,,A collection of objects providing device-level control for the Priority services.
.1.3.6.1.2.1.17.6.2.1.4,P-BRIDGE-MIB::pBridgeDefaultPriorityGroup,,,,,,A collection of objects defining the User Priority applicable to each port for media that do not support native User Priority.
.1.3.6.1.2.1.17.6.2.1.5,P-BRIDGE-MIB::pBridgeRegenPriorityGroup,,,,,,A collection of objects defining the User Priorities applicable to each port for media that support native User Priority.
.1.3.6.1.2.1.17.6.2.1.6,P-BRIDGE-MIB::pBridgePriorityGroup,,,,,,A collection of objects defining the traffic classes within a bridge for each evaluated User Priority.
.1.3.6.1.2.1.17.6.2.1.7,P-BRIDGE-MIB::pBridgeAccessPriorityGroup,,,,,,A collection of objects defining the media-dependent outbound access level for each priority.
.1.3.6.1.2.1.17.6.2.1.8,P-BRIDGE-MIB::pBridgePortGarpGroup,,,,,,A collection of objects providing port level control and status information for GARP operation.
.1.3.6.1.2.1.17.6.2.1.9,P-BRIDGE-MIB::pBridgePortGmrpGroup,,,,,,A collection of objects providing port level control and status information for GMRP operation.
.1.3.6.1.2.1.17.6.2.1.10,P-BRIDGE-MIB::pBridgeHCPortGroup,,,,,,A collection of objects providing 64-bit statistics counters for high-capacity bridge ports.
.1.3.6.1.2.1.17.6.2.1.11,P-BRIDGE-MIB::pBridgePortOverflowGroup,,,,,,A collection of objects providing overflow statistics counters for high-capacity bridge ports.
.1.3.6.1.2.1.17.6.2.1.12,P-BRIDGE-MIB::pBridgePortGmrpGroup2,,,,,,A collection of objects providing port level control and status information for GMRP operation.
.1.3.6.1.2.1.17.6.2.2,P-BRIDGE-MIB::pBridgeCompliances,,,,,,
.1.3.6.1.2.1.17.6.2.2.1,P-BRIDGE-MIB::pBridgeCompliance,,,,,,The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
.1.3.6.1.2.1.17.6.2.2.2,P-BRIDGE-MIB::pBridgeCompliance2,,,,,,The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
.1.3.6.1.2.1.17.7,Q-BRIDGE-MIB::qBridgeMIB,,,,,,The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE 802.1Q-2003, including Restricted Vlan Registration defined by IEEE 802.1u-2001 and Vlan Classification defined by IEEE 802.1v-2001. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4363; See the RFC itself for full legal notices.
.1.3.6.1.2.1.17.7.1,Q-BRIDGE-MIB::qBridgeMIBObjects,,,,,,
.1.3.6.1.2.1.17.7.1.1,Q-BRIDGE-MIB::dot1qBase,,,,,,
.1.3.6.1.2.1.17.7.1.1.1,Q-BRIDGE-MIB::dot1qVlanVersionNumber,INTEGER,read-only,,current,version1(1),The version number of IEEE 802.1Q that this device supports.
.1.3.6.1.2.1.17.7.1.1.2,Q-BRIDGE-MIB::dot1qMaxVlanId,Integer32,read-only,,current,,The maximum IEEE 802.1Q VLAN-ID that this device supports.
.1.3.6.1.2.1.17.7.1.1.3,Q-BRIDGE-MIB::dot1qMaxSupportedVlans,Unsigned32,read-only,,current,,The maximum number of IEEE 802.1Q VLANs that this device supports.
.1.3.6.1.2.1.17.7.1.1.4,Q-BRIDGE-MIB::dot1qNumVlans,Unsigned32,read-only,,current,,The current number of IEEE 802.1Q VLANs that are configured in this device.
.1.3.6.1.2.1.17.7.1.1.5,Q-BRIDGE-MIB::dot1qGvrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative status requested by management for GVRP. The value enabled(1) indicates that GVRP should be enabled on this device, on all ports for which it has not been specifically disabled. When disabled(2), GVRP is disabled on all ports, and all GVRP packets will be forwarded transparently. This object affects all GVRP Applicant and Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all GVRP state machines on all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2,Q-BRIDGE-MIB::dot1qTp,,,,,,
.1.3.6.1.2.1.17.7.1.2.1,Q-BRIDGE-MIB::dot1qFdbTable,,not-accessible,,current,,A table that contains configuration and control information for each Filtering Database currently operating on this device. Entries in this table appear automatically when VLANs are assigned FDB IDs in the dot1qVlanCurrentTable.
.1.3.6.1.2.1.17.7.1.2.1.1,Q-BRIDGE-MIB::dot1qFdbEntry,,not-accessible,dot1qFdbId,current,,Information about a specific Filtering Database.
.1.3.6.1.2.1.17.7.1.2.1.1.1,Q-BRIDGE-MIB::dot1qFdbId,Unsigned32,not-accessible,,current,,The identity of this Filtering Database.
.1.3.6.1.2.1.17.7.1.2.1.1.2,Q-BRIDGE-MIB::dot1qFdbDynamicCount,Counter32,read-only,,current,,The current number of dynamic entries in this Filtering Database.
.1.3.6.1.2.1.17.7.1.2.2,Q-BRIDGE-MIB::dot1qTpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the device has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.
.1.3.6.1.2.1.17.7.1.2.2.1,Q-BRIDGE-MIB::dot1qTpFdbEntry,,not-accessible,dot1qFdbId:dot1qTpFdbAddress,current,,Information about a specific unicast MAC address for which the device has some forwarding and/or filtering information.
.1.3.6.1.2.1.17.7.1.2.2.1.1,Q-BRIDGE-MIB::dot1qTpFdbAddress,OCTET,not-accessible,,current,,A unicast MAC address for which the device has forwarding and/or filtering information.
.1.3.6.1.2.1.17.7.1.2.2.1.2,Q-BRIDGE-MIB::dot1qTpFdbPort,Integer32,read-only,,current,,Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1qTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned but that the device does have some forwarding/filtering information about this address (e.g., in the dot1qStaticUnicastTable). Implementors are encouraged to assign the port value to this object whenever it is learned, even for addresses for which the corresponding value of dot1qTpFdbStatus is not learned(3).
.1.3.6.1.2.1.17.7.1.2.2.1.3,Q-BRIDGE-MIB::dot1qTpFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5),The status of this entry. The meanings of the values are: other(1) - none of the following. This may include the case where some other MIB object (not the corresponding instance of dot1qTpFdbPort, nor an entry in the dot1qStaticUnicastTable) is being used to determine if and how frames addressed to the value of the corresponding instance of dot1qTpFdbAddress are being forwarded. invalid(2) - this entry is no longer valid (e.g., it was learned but has since aged out), but has not yet been flushed from the table. learned(3) - the value of the corresponding instance of dot1qTpFdbPort was learned and is being used. self(4) - the value of the corresponding instance of dot1qTpFdbAddress represents one of the device's addresses. The corresponding instance of dot1qTpFdbPort indicates which of the device's ports has this address. mgmt(5) - the value of the corresponding instance of dot1qTpFdbAddress is also the value of an existing instance of dot1qStaticAddress.
.1.3.6.1.2.1.17.7.1.2.3,Q-BRIDGE-MIB::dot1qTpGroupTable,,not-accessible,,current,,A table containing filtering information for VLANs configured into the bridge by (local or network) management, or learned dynamically, specifying the set of ports to which frames received on a VLAN for this FDB and containing a specific Group destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.7.1.2.3.1,Q-BRIDGE-MIB::dot1qTpGroupEntry,,not-accessible,dot1qVlanIndex:dot1qTpGroupAddress,current,,Filtering information configured into the bridge by management, or learned dynamically, specifying the set of ports to which frames received on a VLAN and containing a specific Group destination address are allowed to be forwarded. The subset of these ports learned dynamically is also provided.
.1.3.6.1.2.1.17.7.1.2.3.1.1,Q-BRIDGE-MIB::dot1qTpGroupAddress,OCTET,not-accessible,,current,,The destination Group MAC address in a frame to which this entry's filtering information applies.
.1.3.6.1.2.1.17.7.1.2.3.1.2,Q-BRIDGE-MIB::dot1qTpGroupEgressPorts,OCTET,read-only,,current,,The complete set of ports, in this VLAN, to which frames destined for this Group MAC address are currently being explicitly forwarded. This does not include ports for which this address is only implicitly forwarded, in the dot1qForwardAllPorts list.
.1.3.6.1.2.1.17.7.1.2.3.1.3,Q-BRIDGE-MIB::dot1qTpGroupLearnt,OCTET,read-only,,current,,The subset of ports in dot1qTpGroupEgressPorts that were learned by GMRP or some other dynamic mechanism, in this Filtering database.
.1.3.6.1.2.1.17.7.1.2.4,Q-BRIDGE-MIB::dot1qForwardAllTable,,not-accessible,,current,,A table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of all multicasts applies, configured statically by management or dynamically by GMRP. An entry appears in this table for all VLANs that are currently instantiated.
.1.3.6.1.2.1.17.7.1.2.4.1,Q-BRIDGE-MIB::dot1qForwardAllEntry,,not-accessible,dot1qVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which all multicasts should be forwarded, configured statically by management or dynamically by GMRP.
.1.3.6.1.2.1.17.7.1.2.4.1.1,Q-BRIDGE-MIB::dot1qForwardAllPorts,OCTET,read-only,,current,,The complete set of ports in this VLAN to which all multicast group-addressed frames are to be forwarded. This includes ports for which this need has been determined dynamically by GMRP, or configured statically by management.
.1.3.6.1.2.1.17.7.1.2.4.1.2,Q-BRIDGE-MIB::dot1qForwardAllStaticPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN to which all multicast group-addressed frames are to be forwarded. Ports entered in this list will also appear in the complete set shown by dot1qForwardAllPorts. This value will be restored after the device is reset. This only applies to ports that are members of the VLAN, defined by dot1qVlanCurrentEgressPorts. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardAllForbiddenPorts. The default value is a string of ones of appropriate length, to indicate the standard behaviour of using basic filtering services, i.e., forward all multicasts to all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2.4.1.3,Q-BRIDGE-MIB::dot1qForwardAllForbiddenPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward All Multicast Groups may not be dynamically registered by GMRP. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardAllStaticPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2.5,Q-BRIDGE-MIB::dot1qForwardUnregisteredTable,,not-accessible,,current,,A table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of multicast group-addressed frames for which no more specific forwarding information applies. This is configured statically by management and determined dynamically by GMRP. An entry appears in this table for all VLANs that are currently instantiated.
.1.3.6.1.2.1.17.7.1.2.5.1,Q-BRIDGE-MIB::dot1qForwardUnregisteredEntry,,not-accessible,dot1qVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which all multicasts for which there is no more specific forwarding information shall be forwarded. This is configured statically by management or dynamically by GMRP.
.1.3.6.1.2.1.17.7.1.2.5.1.1,Q-BRIDGE-MIB::dot1qForwardUnregisteredPorts,OCTET,read-only,,current,,The complete set of ports in this VLAN to which multicast group-addressed frames for which there is no more specific forwarding information will be forwarded. This includes ports for which this need has been determined dynamically by GMRP, or configured statically by management.
.1.3.6.1.2.1.17.7.1.2.5.1.2,Q-BRIDGE-MIB::dot1qForwardUnregisteredStaticPorts,OCTET,read-write,,current,,The set of ports configured by management, in this VLAN, to which multicast group-addressed frames for which there is no more specific forwarding information are to be forwarded. Ports entered in this list will also appear in the complete set shown by dot1qForwardUnregisteredPorts. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardUnregisteredForbiddenPorts. The default value is a string of zeros of appropriate length, although this has no effect with the default value of dot1qForwardAllStaticPorts. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.2.5.1.3,Q-BRIDGE-MIB::dot1qForwardUnregisteredForbiddenPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward Unregistered Multicast Groups may not be dynamically registered by GMRP. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in dot1qForwardUnregisteredStaticPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3,Q-BRIDGE-MIB::dot1qStatic,,,,,,
.1.3.6.1.2.1.17.7.1.3.1,Q-BRIDGE-MIB::dot1qStaticUnicastTable,,not-accessible,,current,,A table containing filtering information for Unicast MAC addresses for each Filtering Database, configured into the device by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific unicast destination addresses are allowed to be forwarded. A value of zero in this table (as the port number from which frames with a specific destination address are received) is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast addresses only.
.1.3.6.1.2.1.17.7.1.3.1.1,Q-BRIDGE-MIB::dot1qStaticUnicastEntry,,not-accessible,dot1qFdbId:dot1qStaticUnicastAddress:dot1qStaticUnicastReceivePort,current,,Filtering information configured into the device by (local or network) management specifying the set of ports to which frames received from a specific port and containing a specific unicast destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.7.1.3.1.1.1,Q-BRIDGE-MIB::dot1qStaticUnicastAddress,OCTET,not-accessible,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object must take the value of a unicast address.
.1.3.6.1.2.1.17.7.1.3.1.1.2,Q-BRIDGE-MIB::dot1qStaticUnicastReceivePort,Integer32,not-accessible,,current,,Either the value '0' or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which there is no other applicable entry.
.1.3.6.1.2.1.17.7.1.3.1.1.3,Q-BRIDGE-MIB::dot1qStaticUnicastAllowedToGoTo,OCTET,read-write,,current,,The set of ports for which a frame with a specific unicast address will be flooded in the event that it has not been learned. It also specifies the set of ports on which a specific unicast address may be dynamically learned. The dot1qTpFdbTable will have an equivalent entry with a dot1qTpFdbPort value of '0' until this address has been learned, at which point it will be updated with the port the address has been seen on. This only applies to ports that are members of the VLAN, defined by dot1qVlanCurrentEgressPorts. The default value of this object is a string of ones of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.1.1.4,Q-BRIDGE-MIB::dot1qStaticUnicastStatus,INTEGER,read-write,,current,other(1):invalid(2):permanent(3):deleteOnReset(4):deleteOnTimeout(5),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.2,Q-BRIDGE-MIB::dot1qStaticMulticastTable,,not-accessible,,current,,A table containing filtering information for Multicast and Broadcast MAC addresses for each VLAN, configured into the device by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific Multicast and Broadcast destination addresses are allowed to be forwarded. A value of zero in this table (as the port number from which frames with a specific destination address are received) is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for Multicast and Broadcast addresses only.
.1.3.6.1.2.1.17.7.1.3.2.1,Q-BRIDGE-MIB::dot1qStaticMulticastEntry,,not-accessible,dot1qVlanIndex:dot1qStaticMulticastAddress:dot1qStaticMulticastReceivePort,current,,Filtering information configured into the device by (local or network) management specifying the set of ports to which frames received from this specific port for this VLAN and containing this Multicast or Broadcast destination address are allowed to be forwarded.
.1.3.6.1.2.1.17.7.1.3.2.1.1,Q-BRIDGE-MIB::dot1qStaticMulticastAddress,OCTET,not-accessible,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object must take the value of a Multicast or Broadcast address.
.1.3.6.1.2.1.17.7.1.3.2.1.2,Q-BRIDGE-MIB::dot1qStaticMulticastReceivePort,Integer32,not-accessible,,current,,Either the value '0' or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which there is no other applicable entry.
.1.3.6.1.2.1.17.7.1.3.2.1.3,Q-BRIDGE-MIB::dot1qStaticMulticastStaticEgressPorts,OCTET,read-write,,current,,The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC address must be forwarded, regardless of any dynamic information, e.g., from GMRP. A port may not be added in this set if it is already a member of the set of ports in dot1qStaticMulticastForbiddenEgressPorts. The default value of this object is a string of ones of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.2.1.4,Q-BRIDGE-MIB::dot1qStaticMulticastForbiddenEgressPorts,OCTET,read-write,,current,,The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC address must not be forwarded, regardless of any dynamic information, e.g., from GMRP. A port may not be added in this set if it is already a member of the set of ports in dot1qStaticMulticastStaticEgressPorts. The default value of this object is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.3.2.1.5,Q-BRIDGE-MIB::dot1qStaticMulticastStatus,INTEGER,read-write,,current,other(1):invalid(2):permanent(3):deleteOnReset(4):deleteOnTimeout(5),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4,Q-BRIDGE-MIB::dot1qVlan,,,,,,
.1.3.6.1.2.1.17.7.1.4.1,Q-BRIDGE-MIB::dot1qVlanNumDeletes,Counter32,read-only,,current,,The number of times a VLAN entry has been deleted from the dot1qVlanCurrentTable (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2.
.1.3.6.1.2.1.17.7.1.4.2,Q-BRIDGE-MIB::dot1qVlanCurrentTable,,not-accessible,,current,,A table containing current configuration information for each VLAN currently configured into the device by (local or network) management, or dynamically created as a result of GVRP requests received.
.1.3.6.1.2.1.17.7.1.4.2.1,Q-BRIDGE-MIB::dot1qVlanCurrentEntry,,not-accessible,dot1qVlanTimeMark:dot1qVlanIndex,current,,Information for a VLAN configured into the device by (local or network) management, or dynamically created as a result of GVRP requests received.
.1.3.6.1.2.1.17.7.1.4.2.1.1,Q-BRIDGE-MIB::dot1qVlanTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.6.1.2.1.17.7.1.4.2.1.2,Q-BRIDGE-MIB::dot1qVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier referring to this VLAN.
.1.3.6.1.2.1.17.7.1.4.2.1.3,Q-BRIDGE-MIB::dot1qVlanFdbId,Unsigned32,read-only,,current,,The Filtering Database used by this VLAN. This is one of the dot1qFdbId values in the dot1qFdbTable. This value is allocated automatically by the device whenever the VLAN is created: either dynamically by GVRP, or by management, in dot1qVlanStaticTable. Allocation of this value follows the learning constraints defined for this VLAN in dot1qLearningConstraintsTable.
.1.3.6.1.2.1.17.7.1.4.2.1.4,Q-BRIDGE-MIB::dot1qVlanCurrentEgressPorts,OCTET,read-only,,current,,The set of ports that are transmitting traffic for this VLAN as either tagged or untagged frames.
.1.3.6.1.2.1.17.7.1.4.2.1.5,Q-BRIDGE-MIB::dot1qVlanCurrentUntaggedPorts,OCTET,read-only,,current,,The set of ports that are transmitting traffic for this VLAN as untagged frames.
.1.3.6.1.2.1.17.7.1.4.2.1.6,Q-BRIDGE-MIB::dot1qVlanStatus,INTEGER,read-only,,current,other(1):permanent(2):dynamicGvrp(3),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. permanent(2) - this entry, corresponding to an entry in dot1qVlanStaticTable, is currently in use and will remain so after the next reset of the device. The port lists for this entry include ports from the equivalent dot1qVlanStaticTable entry and ports learned dynamically. dynamicGvrp(3) - this entry is currently in use and will remain so until removed by GVRP. There is no static entry for this VLAN, and it will be removed when the last port leaves the VLAN.
.1.3.6.1.2.1.17.7.1.4.2.1.7,Q-BRIDGE-MIB::dot1qVlanCreationTime,TimeTicks,read-only,,current,,The value of sysUpTime when this VLAN was created.
.1.3.6.1.2.1.17.7.1.4.3,Q-BRIDGE-MIB::dot1qVlanStaticTable,,not-accessible,,current,,A table containing static configuration information for each VLAN configured into the device by (local or network) management. All entries are permanent and will be restored after the device is reset.
.1.3.6.1.2.1.17.7.1.4.3.1,Q-BRIDGE-MIB::dot1qVlanStaticEntry,,not-accessible,dot1qVlanIndex,current,,Static information for a VLAN configured into the device by (local or network) management.
.1.3.6.1.2.1.17.7.1.4.3.1.1,Q-BRIDGE-MIB::dot1qVlanStaticName,OCTET,read-create,,current,,An administratively assigned string, which may be used to identify the VLAN.
.1.3.6.1.2.1.17.7.1.4.3.1.2,Q-BRIDGE-MIB::dot1qVlanStaticEgressPorts,OCTET,read-create,,current,,The set of ports that are permanently assigned to the egress list for this VLAN by management. Changes to a bit in this object affect the per-port, per-VLAN Registrar control for Registration Fixed for the relevant GVRP state machine on each port. A port may not be added in this set if it is already a member of the set of ports in dot1qVlanForbiddenEgressPorts. The default value of this object is a string of zeros of appropriate length, indicating not fixed.
.1.3.6.1.2.1.17.7.1.4.3.1.3,Q-BRIDGE-MIB::dot1qVlanForbiddenEgressPorts,OCTET,read-create,,current,,The set of ports that are prohibited by management from being included in the egress list for this VLAN. Changes to this object that cause a port to be included or excluded affect the per-port, per-VLAN Registrar control for Registration Forbidden for the relevant GVRP state machine on each port. A port may not be added in this set if it is already a member of the set of ports in dot1qVlanStaticEgressPorts. The default value of this object is a string of zeros of appropriate length, excluding all ports from the forbidden set.
.1.3.6.1.2.1.17.7.1.4.3.1.4,Q-BRIDGE-MIB::dot1qVlanStaticUntaggedPorts,OCTET,read-create,,current,,The set of ports that should transmit egress packets for this VLAN as untagged. The default value of this object for the default VLAN (dot1qVlanIndex = 1) is a string of appropriate length including all ports. There is no specified default for other VLANs. If a device agent cannot support the set of ports being set, then it will reject the set operation with an error. For example, a manager might attempt to set more than one VLAN to be untagged on egress where the device does not support this IEEE 802.1Q option.
.1.3.6.1.2.1.17.7.1.4.3.1.5,Q-BRIDGE-MIB::dot1qVlanStaticRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.6.1.2.1.17.7.1.4.4,Q-BRIDGE-MIB::dot1qNextFreeLocalVlanIndex,Integer32,read-only,,current,,The next available value for dot1qVlanIndex of a local VLAN entry in dot1qVlanStaticTable. This will report values >=4096 if a new Local VLAN may be created or else the value 0 if this is not possible. A row creation operation in this table for an entry with a local VlanIndex value may fail if the current value of this object is not used as the index. Even if the value read is used, there is no guarantee that it will still be the valid index when the create operation is attempted; another manager may have already got in during the intervening time interval. In this case, dot1qNextFreeLocalVlanIndex should be re-read and the creation re-tried with the new value. This value will automatically change when the current value is used to create a new row.
.1.3.6.1.2.1.17.7.1.4.5,Q-BRIDGE-MIB::dot1qPortVlanTable,,not-accessible,,current,,A table containing per-port control and status information for VLAN configuration in the device.
.1.3.6.1.2.1.17.7.1.4.5.1,Q-BRIDGE-MIB::dot1qPortVlanEntry,,not-accessible,,current,,Information controlling VLAN configuration for a port on the device. This is indexed by dot1dBasePort.
.1.3.6.1.2.1.17.7.1.4.5.1.1,Q-BRIDGE-MIB::dot1qPvid,Unsigned32,read-write,,current,,The PVID, the VLAN-ID assigned to untagged frames or Priority-Tagged frames received on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.2,Q-BRIDGE-MIB::dot1qPortAcceptableFrameTypes,INTEGER,read-write,,current,admitAll(1):admitOnlyVlanTagged(2),When this is admitOnlyVlanTagged(2), the device will discard untagged frames or Priority-Tagged frames received on this port. When admitAll(1), untagged frames or Priority-Tagged frames received on this port will be accepted and assigned to a VID based on the PVID and VID Set for this port. This control does not affect VLAN-independent Bridge Protocol Data Unit (BPDU) frames, such as GVRP and Spanning Tree Protocol (STP). It does affect VLAN- dependent BPDU frames, such as GMRP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.3,Q-BRIDGE-MIB::dot1qPortIngressFiltering,INTEGER,read-write,,current,true(1):false(2),When this is true(1), the device will discard incoming frames for VLANs that do not include this Port in its Member set. When false(2), the port will accept all incoming frames. This control does not affect VLAN-independent BPDU frames, such as GVRP and STP. It does affect VLAN- dependent BPDU frames, such as GMRP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.4,Q-BRIDGE-MIB::dot1qPortGvrpStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The state of GVRP operation on this port. The value enabled(1) indicates that GVRP is enabled on this port, as long as dot1qGvrpStatus is also enabled for this device. When disabled(2) but dot1qGvrpStatus is still enabled for the device, GVRP is disabled on this port: any GVRP packets received will be silently discarded, and no GVRP registrations will be propagated from other ports. This object affects all GVRP Applicant and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a reset of all GVRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.5.1.5,Q-BRIDGE-MIB::dot1qPortGvrpFailedRegistrations,Counter32,read-only,,current,,The total number of failed GVRP registrations, for any reason, on this port.
.1.3.6.1.2.1.17.7.1.4.5.1.6,Q-BRIDGE-MIB::dot1qPortGvrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last GVRP message received on this port.
.1.3.6.1.2.1.17.7.1.4.5.1.7,Q-BRIDGE-MIB::dot1qPortRestrictedVlanRegistration,INTEGER,read-write,,current,true(1):false(2),The state of Restricted VLAN Registration on this port. If the value of this control is true(1), then creation of a new dynamic VLAN entry is permitted only if there is a Static VLAN Registration Entry for the VLAN concerned, in which the Registrar Administrative Control value for this port is Normal Registration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.6,Q-BRIDGE-MIB::dot1qPortVlanStatisticsTable,,not-accessible,,current,,A table containing per-port, per-VLAN statistics for traffic received. Separate objects are provided for both the most-significant and least-significant bits of statistics counters for ports that are associated with this transparent bridge. The most-significant bit objects are only required on high-capacity interfaces, as defined in the conformance clauses for these objects. This mechanism is provided as a way to read 64-bit counters for agents that support only SNMPv1. Note that the reporting of most-significant and least- significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification.
.1.3.6.1.2.1.17.7.1.4.6.1,Q-BRIDGE-MIB::dot1qPortVlanStatisticsEntry,,not-accessible,dot1dBasePort:dot1qVlanIndex,current,,Traffic statistics for a VLAN on an interface.
.1.3.6.1.2.1.17.7.1.4.6.1.1,Q-BRIDGE-MIB::dot1qTpVlanPortInFrames,Counter32,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN. Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by the local forwarding process for this VLAN. This object includes received bridge management frames classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP.
.1.3.6.1.2.1.17.7.1.4.6.1.2,Q-BRIDGE-MIB::dot1qTpVlanPortOutFrames,Counter32,read-only,,current,,The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN. This includes bridge management frames originated by this device that are classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP).
.1.3.6.1.2.1.17.7.1.4.6.1.3,Q-BRIDGE-MIB::dot1qTpVlanPortInDiscards,Counter32,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN and that were discarded due to VLAN-related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and Discard on Ingress Filtering.
.1.3.6.1.2.1.17.7.1.4.6.1.4,Q-BRIDGE-MIB::dot1qTpVlanPortInOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1qTpVlanPortInFrames counter has overflowed.
.1.3.6.1.2.1.17.7.1.4.6.1.5,Q-BRIDGE-MIB::dot1qTpVlanPortOutOverflowFrames,Counter32,read-only,,current,,The number of times the associated dot1qTpVlanPortOutFrames counter has overflowed.
.1.3.6.1.2.1.17.7.1.4.6.1.6,Q-BRIDGE-MIB::dot1qTpVlanPortInOverflowDiscards,Counter32,read-only,,current,,The number of times the associated dot1qTpVlanPortInDiscards counter has overflowed.
.1.3.6.1.2.1.17.7.1.4.7,Q-BRIDGE-MIB::dot1qPortVlanHCStatisticsTable,,not-accessible,,current,,A table containing per-port, per-VLAN statistics for traffic on high-capacity interfaces.
.1.3.6.1.2.1.17.7.1.4.7.1,Q-BRIDGE-MIB::dot1qPortVlanHCStatisticsEntry,,not-accessible,dot1dBasePort:dot1qVlanIndex,current,,Traffic statistics for a VLAN on a high-capacity interface.
.1.3.6.1.2.1.17.7.1.4.7.1.1,Q-BRIDGE-MIB::dot1qTpVlanPortHCInFrames,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN. Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by the local forwarding process for this VLAN. This object includes received bridge management frames classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP).
.1.3.6.1.2.1.17.7.1.4.7.1.2,Q-BRIDGE-MIB::dot1qTpVlanPortHCOutFrames,Counter64,read-only,,current,,The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN. This includes bridge management frames originated by this device that are classified as belonging to this VLAN (e.g., GMRP, but not GVRP or STP).
.1.3.6.1.2.1.17.7.1.4.7.1.3,Q-BRIDGE-MIB::dot1qTpVlanPortHCInDiscards,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN and that were discarded due to VLAN-related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and Discard on Ingress Filtering.
.1.3.6.1.2.1.17.7.1.4.8,Q-BRIDGE-MIB::dot1qLearningConstraintsTable,,not-accessible,,current,,A table containing learning constraints for sets of Shared and Independent VLANs.
.1.3.6.1.2.1.17.7.1.4.8.1,Q-BRIDGE-MIB::dot1qLearningConstraintsEntry,,not-accessible,dot1qConstraintVlan:dot1qConstraintSet,current,,A learning constraint defined for a VLAN.
.1.3.6.1.2.1.17.7.1.4.8.1.1,Q-BRIDGE-MIB::dot1qConstraintVlan,Unsigned32,not-accessible,,current,,The index of the row in dot1qVlanCurrentTable for the VLAN constrained by this entry.
.1.3.6.1.2.1.17.7.1.4.8.1.2,Q-BRIDGE-MIB::dot1qConstraintSet,Integer32,not-accessible,,current,,The identity of the constraint set to which dot1qConstraintVlan belongs. These values may be chosen by the management station.
.1.3.6.1.2.1.17.7.1.4.8.1.3,Q-BRIDGE-MIB::dot1qConstraintType,INTEGER,read-create,,current,independent(1):shared(2),The type of constraint this entry defines. independent(1) - the VLAN, dot1qConstraintVlan, uses a filtering database independent from all other VLANs in the same set, defined by dot1qConstraintSet. shared(2) - the VLAN, dot1qConstraintVlan, shares the same filtering database as all other VLANs in the same set, defined by dot1qConstraintSet.
.1.3.6.1.2.1.17.7.1.4.8.1.4,Q-BRIDGE-MIB::dot1qConstraintStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry.
.1.3.6.1.2.1.17.7.1.4.9,Q-BRIDGE-MIB::dot1qConstraintSetDefault,Integer32,read-write,,current,,The identity of the constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in dot1qLearningConstraintsTable. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.4.10,Q-BRIDGE-MIB::dot1qConstraintTypeDefault,INTEGER,read-write,,current,independent(1):shared(2),The type of constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in dot1qLearningConstraintsTable. The types are as defined for dot1qConstraintType. The value of this object MUST be retained across reinitializations of the management system.
.1.3.6.1.2.1.17.7.1.5,Q-BRIDGE-MIB::dot1vProtocol,,,,,,
.1.3.6.1.2.1.17.7.1.5.1,Q-BRIDGE-MIB::dot1vProtocolGroupTable,,not-accessible,,current,,A table that contains mappings from Protocol Templates to Protocol Group Identifiers used for Port-and-Protocol-based VLAN Classification.
.1.3.6.1.2.1.17.7.1.5.1.1,Q-BRIDGE-MIB::dot1vProtocolGroupEntry,,not-accessible,dot1vProtocolTemplateFrameType:dot1vProtocolTemplateProtocolValue,current,,A mapping from a Protocol Template to a Protocol Group Identifier.
.1.3.6.1.2.1.17.7.1.5.1.1.1,Q-BRIDGE-MIB::dot1vProtocolTemplateFrameType,INTEGER,not-accessible,,current,ethernet(1):rfc1042(2):snap8021H(3):snapOther(4):llcOther(5),The data-link encapsulation format or the 'detagged_frame_type' in a Protocol Template.
.1.3.6.1.2.1.17.7.1.5.1.1.2,Q-BRIDGE-MIB::dot1vProtocolTemplateProtocolValue,OCTET,not-accessible,,current,,The identification of the protocol above the data-link layer in a Protocol Template. Depending on the frame type, the octet string will have one of the following values: For 'ethernet', 'rfc1042' and 'snap8021H', this is the 16-bit (2-octet) IEEE 802.3 Type Field. For 'snapOther', this is the 40-bit (5-octet) PID. For 'llcOther', this is the 2-octet IEEE 802.2 Link Service Access Point (LSAP) pair: first octet for Destination Service Access Point (DSAP) and second octet for Source Service Access Point (SSAP).
.1.3.6.1.2.1.17.7.1.5.1.1.3,Q-BRIDGE-MIB::dot1vProtocolGroupId,Integer32,read-create,,current,,Represents a group of protocols that are associated together when assigning a VID to a frame.
.1.3.6.1.2.1.17.7.1.5.1.1.4,Q-BRIDGE-MIB::dot1vProtocolGroupRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.6.1.2.1.17.7.1.5.2,Q-BRIDGE-MIB::dot1vProtocolPortTable,,not-accessible,,current,,A table that contains VID sets used for Port-and-Protocol-based VLAN Classification.
.1.3.6.1.2.1.17.7.1.5.2.1,Q-BRIDGE-MIB::dot1vProtocolPortEntry,,not-accessible,dot1dBasePort:dot1vProtocolPortGroupId,current,,A VID set for a port.
.1.3.6.1.2.1.17.7.1.5.2.1.1,Q-BRIDGE-MIB::dot1vProtocolPortGroupId,Integer32,not-accessible,,current,,Designates a group of protocols in the Protocol Group Database.
.1.3.6.1.2.1.17.7.1.5.2.1.2,Q-BRIDGE-MIB::dot1vProtocolPortGroupVid,Integer32,read-create,,current,,The VID associated with a group of protocols for each port.
.1.3.6.1.2.1.17.7.1.5.2.1.3,Q-BRIDGE-MIB::dot1vProtocolPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.6.1.2.1.17.7.2,Q-BRIDGE-MIB::qBridgeConformance,,,,,,
.1.3.6.1.2.1.17.7.2.1,Q-BRIDGE-MIB::qBridgeGroups,,,,,,
.1.3.6.1.2.1.17.7.2.1.1,Q-BRIDGE-MIB::qBridgeBaseGroup,,,,,,A collection of objects providing device-level control and status information for the Virtual LAN bridge services.
.1.3.6.1.2.1.17.7.2.1.2,Q-BRIDGE-MIB::qBridgeFdbUnicastGroup,,,,,,A collection of objects providing information about all unicast addresses, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.6.1.2.1.17.7.2.1.3,Q-BRIDGE-MIB::qBridgeFdbMulticastGroup,,,,,,A collection of objects providing information about all multicast addresses, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.6.1.2.1.17.7.2.1.4,Q-BRIDGE-MIB::qBridgeServiceRequirementsGroup,,,,,,A collection of objects providing information about service requirements, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.6.1.2.1.17.7.2.1.5,Q-BRIDGE-MIB::qBridgeFdbStaticGroup,,,,,,A collection of objects providing information about unicast and multicast addresses statically configured by management, in each Filtering Database or VLAN.
.1.3.6.1.2.1.17.7.2.1.6,Q-BRIDGE-MIB::qBridgeVlanGroup,,,,,,A collection of objects providing information about all VLANs currently configured on this device.
.1.3.6.1.2.1.17.7.2.1.7,Q-BRIDGE-MIB::qBridgeVlanStaticGroup,,,,,,A collection of objects providing information about VLANs statically configured by management.
.1.3.6.1.2.1.17.7.2.1.8,Q-BRIDGE-MIB::qBridgePortGroup,,,,,,A collection of objects providing port-level VLAN control and status information for all ports.
.1.3.6.1.2.1.17.7.2.1.9,Q-BRIDGE-MIB::qBridgeVlanStatisticsGroup,,,,,,A collection of objects providing per-port packet statistics for all VLANs currently configured on this device.
.1.3.6.1.2.1.17.7.2.1.10,Q-BRIDGE-MIB::qBridgeVlanStatisticsOverflowGroup,,,,,,A collection of objects providing overflow counters for per-port packet statistics for all VLANs currently configured on this device for high-capacity interfaces, defined as those that have the value of the corresponding instance of ifSpeed greater than 650,000,000 bits/second.
.1.3.6.1.2.1.17.7.2.1.11,Q-BRIDGE-MIB::qBridgeVlanHCStatisticsGroup,,,,,,A collection of objects providing per-port packet statistics for all VLANs currently configured on this device for high-capacity interfaces, defined as those that have the value of the corresponding instance of ifSpeed greater than 650,000,000 bits/second.
.1.3.6.1.2.1.17.7.2.1.12,Q-BRIDGE-MIB::qBridgeLearningConstraintsGroup,,,,,,A collection of objects defining the Filtering Database constraints all VLANs have with each other.
.1.3.6.1.2.1.17.7.2.1.13,Q-BRIDGE-MIB::qBridgeLearningConstraintDefaultGroup,,,,,,A collection of objects defining the default Filtering Database constraints for VLANs that have no specific constraints defined.
.1.3.6.1.2.1.17.7.2.1.14,Q-BRIDGE-MIB::qBridgeClassificationDeviceGroup,,,,,,VLAN classification information for the bridge.
.1.3.6.1.2.1.17.7.2.1.15,Q-BRIDGE-MIB::qBridgeClassificationPortGroup,,,,,,VLAN classification information for individual ports.
.1.3.6.1.2.1.17.7.2.1.16,Q-BRIDGE-MIB::qBridgePortGroup2,,,,,,A collection of objects providing port-level VLAN control and status information for all ports.
.1.3.6.1.2.1.17.7.2.2,Q-BRIDGE-MIB::qBridgeCompliances,,,,,,
.1.3.6.1.2.1.17.7.2.2.1,Q-BRIDGE-MIB::qBridgeCompliance,,,,,,The compliance statement for device support of Virtual LAN Bridge services. RFC2674 was silent about the expected persistence of the read-write objects in this MIB module. Applications MUST NOT assume that the values of the read-write objects are persistent across reinitializations of the management system and MUST NOT assume that the values are not persistent across reinitializations of the management system.
.1.3.6.1.2.1.17.7.2.2.2,Q-BRIDGE-MIB::qBridgeCompliance2,,,,,,The compliance statement for device support of Virtual LAN Bridge services. This document clarifies the persistence requirements for the read-write objects in this MIB module. All implementations claiming compliance to qBridgeCompliance2 MUST retain the values of those read-write objects that specify this requirement.
.1.3.6.1.2.1.17.8,BRIDGE-MIB::dot1dConformance,,,,,,
.1.3.6.1.2.1.17.8.1,BRIDGE-MIB::dot1dGroups,,,,,,
.1.3.6.1.2.1.17.8.1.1,BRIDGE-MIB::dot1dBaseBridgeGroup,,,,,,Bridge level information for this device.
.1.3.6.1.2.1.17.8.1.2,BRIDGE-MIB::dot1dBasePortGroup,,,,,,Information for each port on this device.
.1.3.6.1.2.1.17.8.1.3,BRIDGE-MIB::dot1dStpBridgeGroup,,,,,,Bridge level Spanning Tree data for this device.
.1.3.6.1.2.1.17.8.1.4,BRIDGE-MIB::dot1dStpPortGroup,,,,,,Spanning Tree data for each port on this device.
.1.3.6.1.2.1.17.8.1.5,BRIDGE-MIB::dot1dStpPortGroup2,,,,,,Spanning Tree data for each port on this device.
.1.3.6.1.2.1.17.8.1.6,BRIDGE-MIB::dot1dStpPortGroup3,,,,,,Spanning Tree data for devices supporting 32-bit path costs.
.1.3.6.1.2.1.17.8.1.7,BRIDGE-MIB::dot1dTpBridgeGroup,,,,,,Bridge level Transparent Bridging data.
.1.3.6.1.2.1.17.8.1.8,BRIDGE-MIB::dot1dTpFdbGroup,,,,,,Filtering Database information for the Bridge.
.1.3.6.1.2.1.17.8.1.9,BRIDGE-MIB::dot1dTpGroup,,,,,,Dynamic Filtering Database information for each port of the Bridge.
.1.3.6.1.2.1.17.8.1.10,BRIDGE-MIB::dot1dStaticGroup,,,,,,Static Filtering Database information for each port of the Bridge.
.1.3.6.1.2.1.17.8.1.11,BRIDGE-MIB::dot1dNotificationGroup,,,,,,Group of objects describing notifications (traps).
.1.3.6.1.2.1.17.8.2,BRIDGE-MIB::dot1dCompliances,,,,,,
.1.3.6.1.2.1.17.8.2.1,BRIDGE-MIB::bridgeCompliance1493,,,,,,The compliance statement for device support of bridging services, as per RFC1493.
.1.3.6.1.2.1.17.8.2.2,BRIDGE-MIB::bridgeCompliance4188,,,,,,The compliance statement for device support of bridging services. This supports 32-bit Path Cost values and the more restricted bridge and port priorities, as per IEEE 802.1t. Full support for the 802.1D management objects requires that the SNMPv2-MIB [RFC3418] objects sysDescr, and sysUpTime, as well as the IF-MIB [RFC2863] objects ifIndex, ifType, ifDescr, ifPhysAddress, and ifLastChange are implemented.
.1.3.6.1.2.1.17.10,SOURCE-ROUTING-MIB::dot1dPortPair,,,,,,
.1.3.6.1.2.1.17.10.1,SOURCE-ROUTING-MIB::dot1dPortPairTableSize,Gauge32,read-only,,mandatory,,The total number of entries in the Bridge Port Pair Database.
.1.3.6.1.2.1.17.10.2,SOURCE-ROUTING-MIB::dot1dPortPairTable,,not-accessible,,mandatory,,A table that contains information about every port pair database entity associated with this source routing bridge.
.1.3.6.1.2.1.17.10.2.1,SOURCE-ROUTING-MIB::dot1dPortPairEntry,,not-accessible,dot1dPortPairLowPort:dot1dPortPairHighPort,mandatory,,A list of information for each port pair entity of a bridge.
.1.3.6.1.2.1.17.10.2.1.1,SOURCE-ROUTING-MIB::dot1dPortPairLowPort,INTEGER,read-write,,mandatory,,The port number of the lower numbered port for which this entry contains port pair database information.
.1.3.6.1.2.1.17.10.2.1.2,SOURCE-ROUTING-MIB::dot1dPortPairHighPort,INTEGER,read-write,,mandatory,,The port number of the higher numbered port for which this entry contains port pair database information.
.1.3.6.1.2.1.17.10.2.1.3,SOURCE-ROUTING-MIB::dot1dPortPairBridgeNum,INTEGER,read-write,,mandatory,,A bridge number that uniquely identifies the path provided by this source routing bridge between the segments connected to dot1dPortPairLowPort and dot1dPortPairHighPort. The purpose of bridge number is to disambiguate between multiple paths connecting the same two LANs.
.1.3.6.1.2.1.17.10.2.1.4,SOURCE-ROUTING-MIB::dot1dPortPairBridgeState,INTEGER,read-write,,mandatory,enabled(1):disabled(2):invalid(3),The state of dot1dPortPairBridgeNum. Writing 'invalid(3)' to this object removes the corresponding entry.
.1.3.6.1.2.1.18,DECNET-PHIV-MIB::phiv,,,,,,
.1.3.6.1.2.1.18.1,DECNET-PHIV-MIB::phivSystem,,,,,,
.1.3.6.1.2.1.18.1.1,DECNET-PHIV-MIB::phivSystemState,INTEGER,read-write,,mandatory,on(1):off(2):shut(3):restricted(4),This represents the operational state of the executor node. The possible states are: ON Allows logical links. OFF Allows no new links, terminates existing links, and stops routing traffic through. SHUT Allows no new logical links, does not destroy existing logical links, and goes to the OFF state when all logical links are gone. RESTRICTED Allows no new incoming logical links from other nodes. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155).
.1.3.6.1.2.1.18.1.2,DECNET-PHIV-MIB::phivExecIdent,OCTET,read-write,,mandatory,,This is a text string that describes the executor node (for example, 'Research Lab'). The string is up to 32 characters of any type.
.1.3.6.1.2.1.18.2,DECNET-PHIV-MIB::phivManagement,,,,,,
.1.3.6.1.2.1.18.2.1,DECNET-PHIV-MIB::phivMgmtMgmtVers,OCTET,read-only,,mandatory,,This is the read-only Network Management Version, consisting of the version number, the Engineering Change Order (ECO) number, and the user ECO number (for example, 3.0.0). This parameter applies to the executor node only.
.1.3.6.1.2.1.18.3,DECNET-PHIV-MIB::session,,,,,,
.1.3.6.1.2.1.18.3.1,DECNET-PHIV-MIB::phivSessionSystemName,OCTET,read-only,,mandatory,,Name to be associated with the node identification. Only one name can be assigned to a node address or a circuit identification. No name should be used more than once in a DECnet network. Node-name is one to six upper case alphanumeric characters with at least one alpha character. A length of 0 indicates no name.
.1.3.6.1.2.1.18.3.2,DECNET-PHIV-MIB::phivSessionInTimer,INTEGER,read-write,,mandatory,,This value represents the maximum duration between the time a connect is received for a process at the executor node and the time that process accepts or rejects it. If the connect is not accepted or rejected by the user within the number of seconds specified, Session Control rejects it for the user. A value of 0 indicates no timer is running.
.1.3.6.1.2.1.18.3.3,DECNET-PHIV-MIB::phivSessionOutTimer,INTEGER,read-write,,mandatory,,This value represents the duration between the time the executor requests a connect and the time that connect is acknowledged by the destination node. If the connect is not acknowledged within the number of seconds specified, Session Control returns an error. A value of 0 indicates no timer is running.
.1.3.6.1.2.1.18.4,DECNET-PHIV-MIB::end,,,,,,
.1.3.6.1.2.1.18.4.1,DECNET-PHIV-MIB::phivEndRemoteTable,,not-accessible,,mandatory,,Information about the state of sessions between the node under study and the nodes found in the table.
.1.3.6.1.2.1.18.4.1.1,DECNET-PHIV-MIB::phivEndRemoteEntry,,not-accessible,phivEndRemoteHostNodeID,mandatory,,Information about a particular remote node as seen from the end communication layer.
.1.3.6.1.2.1.18.4.1.1.1,DECNET-PHIV-MIB::phivEndRemoteHostNodeID,OCTET,read-only,,mandatory,,This value is the address of the remote node to be evaluated.
.1.3.6.1.2.1.18.4.1.1.2,DECNET-PHIV-MIB::phivEndRemoteState,INTEGER,read-write,,mandatory,on(1):off(2):shut(3):restricted(4),This represents the operational state of the remote node being evaluated. The possible states are: ON Allows logical links. OFF Allows no new links, terminates existing links, and stops routing traffic through. SHUT Allows no new logical links, does not destroy existing logical links, and goes to the OFF state when all logical links are gone. RESTRICTED Allows no new incoming logical links from other nodes. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155.
.1.3.6.1.2.1.18.4.1.1.3,DECNET-PHIV-MIB::phivEndCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known circuit used to communicate with the remote node. This is the same value as phivCircuitIndex.
.1.3.6.1.2.1.18.4.1.1.4,DECNET-PHIV-MIB::phivEndActiveLinks,INTEGER,read-only,,mandatory,,This read-only parameter represents the number of active logical links from the executor to the destination node.
.1.3.6.1.2.1.18.4.1.1.5,DECNET-PHIV-MIB::phivEndDelay,INTEGER,read-only,,mandatory,,This read-only parameter is the average round trip delay in seconds to the destination node. This parameter is kept on a remote node basis.
.1.3.6.1.2.1.18.4.2,DECNET-PHIV-MIB::phivEndCountTable,,not-accessible,,mandatory,,Information about the counters associated with each end system that is known to the entity. These counters reflect totals from the perspective of the executor node.
.1.3.6.1.2.1.18.4.2.1,DECNET-PHIV-MIB::phivEndCountEntry,,not-accessible,phivEndCountHostNodeID,mandatory,,Information about a particular session between two end systems.
.1.3.6.1.2.1.18.4.2.1.1,DECNET-PHIV-MIB::phivEndCountHostNodeID,OCTET,read-only,,mandatory,,This value is the address of the remote node to be evaluated.
.1.3.6.1.2.1.18.4.2.1.2,DECNET-PHIV-MIB::phivEndCountSecsLastZeroed,INTEGER,read-only,,mandatory,,This value is the number of seconds that have elapsed since the counters for the node in this table row were last set to zero. This counter is located in the network management layer, but is returned with the end system information which follows.
.1.3.6.1.2.1.18.4.2.1.3,DECNET-PHIV-MIB::phivEndCountUsrBytesRec,INTEGER,read-only,,mandatory,,Number of user bytes received from the target host.
.1.3.6.1.2.1.18.4.2.1.4,DECNET-PHIV-MIB::phivEndCountUsrBytesSent,INTEGER,read-only,,mandatory,,Number of user bytes sent to the target host.
.1.3.6.1.2.1.18.4.2.1.5,DECNET-PHIV-MIB::phivEndUCountUsrMessRec,INTEGER,read-only,,mandatory,,Number of user messages received from the target host.
.1.3.6.1.2.1.18.4.2.1.6,DECNET-PHIV-MIB::phivEndCountUsrMessSent,INTEGER,read-only,,mandatory,,Number of user messages sent to the target host.
.1.3.6.1.2.1.18.4.2.1.7,DECNET-PHIV-MIB::phivEndCountTotalBytesRec,INTEGER,read-only,,mandatory,,Number of bytes received from the target host.
.1.3.6.1.2.1.18.4.2.1.8,DECNET-PHIV-MIB::phivEndCountTotalBytesSent,INTEGER,read-only,,mandatory,,Number of bytes sent to the target host.
.1.3.6.1.2.1.18.4.2.1.9,DECNET-PHIV-MIB::phivEndCountTotalMessRec,INTEGER,read-only,,mandatory,,Number of messages received from the target host.
.1.3.6.1.2.1.18.4.2.1.10,DECNET-PHIV-MIB::phivEndCountTotalMessSent,INTEGER,read-only,,mandatory,,Number of messages sent to the target host.
.1.3.6.1.2.1.18.4.2.1.11,DECNET-PHIV-MIB::phivEndCountConnectsRecd,INTEGER,read-only,,mandatory,,Number of connects received from the target host.
.1.3.6.1.2.1.18.4.2.1.12,DECNET-PHIV-MIB::phivEndCountConnectsSent,INTEGER,read-only,,mandatory,,Number of connects sent to the target host.
.1.3.6.1.2.1.18.4.2.1.13,DECNET-PHIV-MIB::phivEndCountReponseTimeouts,INTEGER,read-only,,mandatory,,Number of response timeouts.
.1.3.6.1.2.1.18.4.2.1.14,DECNET-PHIV-MIB::phivEndCountRecdConnectResErrs,INTEGER,read-only,,mandatory,,Number of received connect resource errors.
.1.3.6.1.2.1.18.4.3,DECNET-PHIV-MIB::phivEndMaxLinks,INTEGER,read-write,,mandatory,,This value represents the maximum active logical link count allowed for the executor.
.1.3.6.1.2.1.18.4.4,DECNET-PHIV-MIB::phivEndNSPVers,OCTET,read-only,,mandatory,,This read-only parameter represents the version number of the node End Communication S/W. The format is version number, ECO, and user ECO, e.g., 4.1.0
.1.3.6.1.2.1.18.4.5,DECNET-PHIV-MIB::phivEndRetransmitFactor,INTEGER,read-write,,mandatory,,This value represents the maximum number of times the source End Communication at the executor node will restart the retransmission timer when it expires. If the number is exceeded, Session Control disconnects the logical link for the user.
.1.3.6.1.2.1.18.4.6,DECNET-PHIV-MIB::phivEndDelayFact,INTEGER,read-write,,mandatory,,This is the number by which to multiply one sixteenth of the estimated round trip delay to a node to set the retransmission timer to that node.
.1.3.6.1.2.1.18.4.7,DECNET-PHIV-MIB::phivEndDelayWeight,INTEGER,read-write,,mandatory,,This number represents the weight to apply to a current round trip delay estimate to a remote node when updating the estimated round trip delay to a node. On some systems the number must be 1 less than a power of 2 for computational efficiency.
.1.3.6.1.2.1.18.4.8,DECNET-PHIV-MIB::phivEndInactivityTimer,INTEGER,read-write,,mandatory,,This value represents the maximum duration of inactivity (no data in either direction) on a logical link before the node checks to see if the logical link still works. If no activity occurs within the minimum number of seconds, End Communication generates artificial traffic to test the link (End Communication specification).
.1.3.6.1.2.1.18.4.9,DECNET-PHIV-MIB::phivEndCountZeroCount,INTEGER,read-write,,mandatory,other(1):reset(2),When this value is set to 2, all of the counters in the End System Counter Table are set to zero.
.1.3.6.1.2.1.18.4.10,DECNET-PHIV-MIB::phivEndMaxLinksActive,INTEGER,read-write,,mandatory,,This value represents the high water mark for the number of links that were active at any one time.
.1.3.6.1.2.1.18.5,DECNET-PHIV-MIB::routing,,,,,,
.1.3.6.1.2.1.18.5.1,DECNET-PHIV-MIB::phivRouteBroadcastRouteTimer,INTEGER,read-write,,mandatory,,This value determines the maximum time in seconds allowed between Routing updates on Ethernet circuits. When this timer expired before a routing update occurs, a routing update is forced. With a standard calculation, Routing also uses this timer to enforce a minimum delay between routing updates.
.1.3.6.1.2.1.18.5.2,DECNET-PHIV-MIB::phivRouteBuffSize,INTEGER,read-write,,mandatory,,This parameter value determines the maximum size of a Routing message. It therefore determines the maximum size message that can be forwarded. This size includes protocol overhead down to and including the End Communication layer, plus a constant value of 6. (This value of 6 is included to provide compatibility with the parameter definition in Phase III, which included the Routing overhead.) It does not include Routing or Data link overhead (except for the constant value of 6). There is one buffer size for all circuits. NOTE: The BUFFER SIZE defines the maximum size messages that the Routing layer can forward. The SEGMENT BUFFER SIZE (defined below) defines the maximum size messages that the End Communication layer can transmit or receive. The SEGMENT BUFFER SIZE is always less than or equal to the BUFFER SIZE. Normally the two parameters will be equal. They may be different to allow the network manager to alter buffer sizes on all nodes without interruption of service. They both include an extra 6 bytes for compatibility with Phase III.
.1.3.6.1.2.1.18.5.3,DECNET-PHIV-MIB::phivRouteRoutingVers,OCTET,read-only,,mandatory,,This read-only parameter identifies the executor node's Routing version number. The format is version number, ECO, and user ECO, e.g., 4.1.0
.1.3.6.1.2.1.18.5.4,DECNET-PHIV-MIB::phivRouteMaxAddr,INTEGER,read-write,,mandatory,,This value represents the largest node number and, therefore, number of nodes that can be known about by the executor node's home area.
.1.3.6.1.2.1.18.5.5,DECNET-PHIV-MIB::phivRouteMaxBdcastNonRouters,INTEGER,read-write,,mandatory,,This value represents the maximum total number of nonrouters the executor node can have on its Ethernet circuits.
.1.3.6.1.2.1.18.5.6,DECNET-PHIV-MIB::phivRouteMaxBdcastRouters,INTEGER,read-write,,mandatory,,This value represents the maximum total number of routers the executor node can have on its Ethernet circuits.
.1.3.6.1.2.1.18.5.7,DECNET-PHIV-MIB::phivRouteMaxBuffs,INTEGER,read-write,,mandatory,,This value represents the maximum number of transmit buffers that Routing may use for all circuits.
.1.3.6.1.2.1.18.5.8,DECNET-PHIV-MIB::phivRouteMaxCircuits,INTEGER,read-write,,mandatory,,This value represents the maximum number of Routing circuits that the executor node can know about.
.1.3.6.1.2.1.18.5.9,DECNET-PHIV-MIB::phivRouteMaxCost,INTEGER,read-write,,mandatory,,This value represents the maximum total path cost allowed from the executor to any node within an area. The path cost is the sum of the circuit costs along a path between two nodes. This parameter defines the point where the executor node's Routing routing decision algorithm declares another node unreachable because the cost of the least costly path to the other node is excessive. For correct operation, this parameter must not be less than the maximum path cost of the network.
.1.3.6.1.2.1.18.5.10,DECNET-PHIV-MIB::phivRouteMaxHops,INTEGER,read-write,,mandatory,,This value represents the maximum number of routing hops allowable from the executor to any other reachable node within an area. (A hop is the logical distance over a circuit between two adjacent nodes.) This parameter defines the point where the executor node's Routing routing decision algorithm declares another node unreachable because the length of the shortest path between the two nodes is too long. For correct operation, this parameter must not be less than the network diameter. (The network diameter is the reachability distance between the two nodes of the network having the greatest reachability distance, where reachability distance is the length the shortest path between a given pair of nodes.)
.1.3.6.1.2.1.18.5.11,DECNET-PHIV-MIB::phivRouteMaxVisits,INTEGER,read-write,,mandatory,,This value represents the maximum number of nodes a message coming into the executor node can have visited. If the message is not for this node and the MAXIMUM VISITS number is exceeded, the message is discarded. The MAXIMUM VISITS parameter defines the point where the packet lifetime control algorithm discards a packet that has traversed too many nodes. For correct operation, this parameter must not be less than the maximum path length of the network. (The maximum path length is the routing distance between the two nodes of the network having the greatest routing distance, where routing distance is the length of the least costly path between a given pair of nodes.)
.1.3.6.1.2.1.18.5.12,DECNET-PHIV-MIB::phivRouteRoutingTimer,INTEGER,read-write,,mandatory,,This value determines the maximum time in seconds allowed between Routing updates on non-Ethernet circuits. When this timer expires before a routing update occurs, a routing update is forced.
.1.3.6.1.2.1.18.5.13,DECNET-PHIV-MIB::phivRouteSegBuffSize,INTEGER,read-write,,mandatory,,This parameter value determines the maximum size of an end-to-end segment. The size is a decimal integer in the range 1-65535. This size is in bytes. This size includes protocol overhead down to and including the End Communication layer, plus a constant value of 6. (This value of 6 is included to provide compatibility with the BUFFER SIZE parameter definition.) It does not include Routing or Data link overhead (except for the constant value of 6).
.1.3.6.1.2.1.18.5.14,DECNET-PHIV-MIB::phivRouteType,INTEGER,read-only,,obsolete,routing-III(1):nonrouting-III(2):area(3):routing-IV(4):nonrouting-IV(5),This parameter indicates the type of the executor node. The node-type is one of the following: routing-III nonrouting-III routing-IV ronrouting-IV area A routing node has full routing capability. A nonrouting node contains a subset of the Routing routing modules. The III and IV indicate the DNA phase of the node. Nonrouting nodes can deliver and receive packets to and from any node, but cannot route packets from other nodes through to other nodes. An area node routes between areas. Refer to the Routing specification for details. For adjacent nodes, this is a read-only parameter that indicates the type of the reachable adjacent node. NOTE: The ROUTING-III and NONROUTING-III values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155)
.1.3.6.1.2.1.18.5.15,DECNET-PHIV-MIB::phivRouteCountAgedPktLoss,INTEGER,read-only,,mandatory,,Number of aged packet losses.
.1.3.6.1.2.1.18.5.16,DECNET-PHIV-MIB::phivRouteCountNodeUnrPktLoss,INTEGER,read-only,,mandatory,,Number of node unreachable packet losses.
.1.3.6.1.2.1.18.5.17,DECNET-PHIV-MIB::phivRouteCountOutRngePktLoss,INTEGER,read-only,,mandatory,,Number of node out-of-range packet losses.
.1.3.6.1.2.1.18.5.18,DECNET-PHIV-MIB::phivRouteCountOverSzePktLoss,INTEGER,read-only,,mandatory,,Number of Oversized packet losses.
.1.3.6.1.2.1.18.5.19,DECNET-PHIV-MIB::phivRouteCountPacketFmtErr,INTEGER,read-only,,mandatory,,Number of packet format errors.
.1.3.6.1.2.1.18.5.20,DECNET-PHIV-MIB::phivRouteCountPtlRteUpdtLoss,INTEGER,read-only,,mandatory,,Number of partial routing update losses.
.1.3.6.1.2.1.18.5.21,DECNET-PHIV-MIB::phivRouteCountVerifReject,INTEGER,read-only,,mandatory,,Number of verification rejects.
.1.3.6.1.2.1.18.5.22,DECNET-PHIV-MIB::phivLevel1RouteTable,,not-accessible,,mandatory,,Information about the currently known DECnet Phase IV Routes.
.1.3.6.1.2.1.18.5.22.1,DECNET-PHIV-MIB::phivLevel1RouteEntry,,not-accessible,phivLevel1RouteNodeAddr,mandatory,,Information about the currently known DECnet Phase IV Routes.
.1.3.6.1.2.1.18.5.22.1.1,DECNET-PHIV-MIB::phivLevel1RouteNodeAddr,OCTET,read-only,,mandatory,,This value is the address of the node about which routing information is contained in this level 1 routing table.
.1.3.6.1.2.1.18.5.22.1.2,DECNET-PHIV-MIB::phivLevel1RouteCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known circuit. This is the index to the circuit state table and is the same value as phivCircuitIndex.
.1.3.6.1.2.1.18.5.22.1.3,DECNET-PHIV-MIB::phivLevel1RouteCost,INTEGER,read-only,,mandatory,,This read-only parameter represents the total cost over the current path to the destination node. Cost is a positive integer value associated with using a circuit. Routing routes messages (data) along the path between two nodes with the smallest cost. COST is kept on a remote node basis.
.1.3.6.1.2.1.18.5.22.1.4,DECNET-PHIV-MIB::phivLevel1RouteHops,INTEGER,read-only,,mandatory,,This read-only parameter represents the number of hops over to a destination node. A hop is Routing value representing the logical distance between two nodes in a network. HOPS is kept on a remote node basis.
.1.3.6.1.2.1.18.5.22.1.5,DECNET-PHIV-MIB::phivLevel1RouteNextNode,OCTET,read-only,,mandatory,,This read-only value indicates the next node on the circuit used to get to the node under scrutiny (next hop).
.1.3.6.1.2.1.18.5.23,DECNET-PHIV-MIB::phivRouteCountZeroCount,INTEGER,read-write,,mandatory,other(1):reset(2),When this value is set to 2, the following objects are set to Zero: phivRouteCountAgedPktLoss, phivRouteCountNodeUnrPktLoss, phivRouteCountOutRngePktLoss, phivRouteCountOverSzePktLoss, phivRouteCountPacketFmtErr, phivRouteCountPtlRteUpdtLoss, and phivRouteCountVerifReject.
.1.3.6.1.2.1.18.5.24,DECNET-PHIV-MIB::phivRouteSystemAddr,OCTET,read-only,,obsolete,,DECnet Phase IV node address.
.1.3.6.1.2.1.18.5.25,DECNET-PHIV-MIB::phivRouteRoutingType,INTEGER,read-write,,mandatory,routing-III(1):nonrouting-III(2):area(3):routing-IV(4):nonrouting-IV(5),This read-write parameter indicates the type of the executor node. The node-type is one of the following: routing-III nonrouting-III routing-IV ronrouting-IV area A routing node has full routing capability. A nonrouting node contains a subset of the Routing routing modules. The III and IV indicate the DNA phase of the node. Nonrouting nodes can deliver and receive packets to and from any node, but cannot route packets from other nodes through to other nodes. An area node routes between areas. Refer to the Routing specification for details. For adjacent nodes, this is a read-only parameter that indicates the type of the reachable adjacent node. NOTE: The ROUTING-III and NONROUTING-III values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155)
.1.3.6.1.2.1.18.5.26,DECNET-PHIV-MIB::phivRouteSystemAddress,OCTET,read-write,,mandatory,,DECnet Phase IV node address.
.1.3.6.1.2.1.18.6,DECNET-PHIV-MIB::circuit,,,,,,
.1.3.6.1.2.1.18.6.1,DECNET-PHIV-MIB::phivCircuitParametersTable,,not-accessible,,mandatory,,Information about the parameters associated with all circuits currently known.
.1.3.6.1.2.1.18.6.1.1,DECNET-PHIV-MIB::phivCircuitParametersEntry,,not-accessible,phivCircuitIndex,mandatory,,Parameters information about all circuits currently known.
.1.3.6.1.2.1.18.6.1.1.1,DECNET-PHIV-MIB::phivCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known circuit.
.1.3.6.1.2.1.18.6.1.1.2,DECNET-PHIV-MIB::phivCircuitLineIndex,INTEGER,read-only,,mandatory,,The line on which this circuit is active. This is the same as the ifIndex.
.1.3.6.1.2.1.18.6.1.1.3,DECNET-PHIV-MIB::phivCircuitCommonState,INTEGER,read-write,,mandatory,on(1):off(2):service(3):cleared(4),This value represents the circuit's Network Management operational state. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155.
.1.3.6.1.2.1.18.6.1.1.4,DECNET-PHIV-MIB::phivCircuitCommonSubState,INTEGER,read-only,,mandatory,starting(1):reflecting(2):looping(3):loading(4):dumping(5):triggering(6):autoservice(7):autoloading(8):autodumping(9):autotriggering(10):synchronizing(11):failed(12):running(13),This value represents the circuit's Network Management operational and service substate. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155.
.1.3.6.1.2.1.18.6.1.1.5,DECNET-PHIV-MIB::phivCircuitCommonName,OCTET,read-only,,mandatory,,The name of the circuit entry in the table, for example, SVA-0 or in a level 2 router ASYNC-8 or ETHER-1).
.1.3.6.1.2.1.18.6.1.1.6,DECNET-PHIV-MIB::phivCircuitExecRecallTimer,INTEGER,read-write,,mandatory,,This parameter represents the minimum number of seconds to wait before restarting the circuit. A value of 0 indicates not timer is running.
.1.3.6.1.2.1.18.6.1.1.7,DECNET-PHIV-MIB::phivCircuitCommonType,INTEGER,read-only,,mandatory,ddcmp-point(1):ddcmp-control(2):ddcmp-tributary(3):x25(4):ddcmp-dmc(5):ethernet(6):ci(7):qp2-dte20(8):bisync(9):other(14):fddi(15),Represents the type of the circuit. For X.25 circuits, the value must be set to X25. For DDCMP and Ethernet circuits it is read only and is the same value as the protocol of the associated line. NOTE: Values 1 - 5 are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155.
.1.3.6.1.2.1.18.6.1.1.8,DECNET-PHIV-MIB::phivCircuitService,INTEGER,read-write,,mandatory,enabled(1):disabled(2),This value indicates whether or not Network Management allows service operations on a circuit. The values for service-control are as follows: ENABLED SERVICE state and/or service functions are allowed. DISABLED SERVICE state and/or service functions are not allowed. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155.
.1.3.6.1.2.1.18.6.1.1.9,DECNET-PHIV-MIB::phivCircuitExecCost,INTEGER,read-write,,mandatory,,This value represents the routing cost of the circuit. Routing sends messages along the path between two nodes having the smallest cost.
.1.3.6.1.2.1.18.6.1.1.10,DECNET-PHIV-MIB::phivCircuitExecHelloTimer,INTEGER,read-write,,mandatory,,This value determines the frequency of Routing Hello messages sent to the adjacent node on the circuit.
.1.3.6.1.2.1.18.6.2,DECNET-PHIV-MIB::phivCircuitCountTable,,not-accessible,,mandatory,,Information about the counters associated with all circuits currently known.
.1.3.6.1.2.1.18.6.2.1,DECNET-PHIV-MIB::phivCircuitCountEntry,,not-accessible,phivCircuitIndex,mandatory,,Counter information about all circuits currently known
.1.3.6.1.2.1.18.6.2.1.1,DECNET-PHIV-MIB::phivCircuitCountSecLastZeroed,INTEGER,read-only,,mandatory,,Number of seconds since the circuit counters for this circuit were last zeroed.
.1.3.6.1.2.1.18.6.2.1.2,DECNET-PHIV-MIB::phivCircuitCountTermPacketsRecd,INTEGER,read-only,,mandatory,,Number of terminating packets received on this circuit.
.1.3.6.1.2.1.18.6.2.1.3,DECNET-PHIV-MIB::phivCircuitCountOriginPackSent,INTEGER,read-only,,mandatory,,Number of originating packets sent on this circuit.
.1.3.6.1.2.1.18.6.2.1.4,DECNET-PHIV-MIB::phivCircuitCountTermCongLoss,INTEGER,read-only,,mandatory,,Number of terminating congestion losses on this circuit.
.1.3.6.1.2.1.18.6.2.1.5,DECNET-PHIV-MIB::phivCircuitCountCorruptLoss,INTEGER,read-only,,mandatory,,Number of corruption losses on this circuit.
.1.3.6.1.2.1.18.6.2.1.6,DECNET-PHIV-MIB::phivCircuitCountTransitPksRecd,INTEGER,read-only,,mandatory,,Number of Transit packets received on this circuit.
.1.3.6.1.2.1.18.6.2.1.7,DECNET-PHIV-MIB::phivCircuitCountTransitPkSent,INTEGER,read-only,,mandatory,,Number of transit packets sent on this circuit.
.1.3.6.1.2.1.18.6.2.1.8,DECNET-PHIV-MIB::phivCircuitCountTransitCongestLoss,INTEGER,read-only,,mandatory,,Number of transit congestion losses on this circuit.
.1.3.6.1.2.1.18.6.2.1.9,DECNET-PHIV-MIB::phivCircuitCountCircuitDown,INTEGER,read-only,,mandatory,,Number of circuit downs on this circuit.
.1.3.6.1.2.1.18.6.2.1.10,DECNET-PHIV-MIB::phivCircuitCountInitFailure,INTEGER,read-only,,mandatory,,Number of Initialization failures on this circuit.
.1.3.6.1.2.1.18.6.2.1.11,DECNET-PHIV-MIB::phivCircuitCountAdjDown,INTEGER,read-only,,mandatory,,This counter indicates the number of adjacency losses that result from any of the following: Node listener timeout Invalid data received at node listener Unexpected control (initialization or verification) message received Routing message received with a checksum error Node identification from a routing message or a Hello message that is not the one expected Hello message received indicating that connectivity became one-way Adjacency idled.
.1.3.6.1.2.1.18.6.2.1.12,DECNET-PHIV-MIB::phivCircuitCountPeakAdj,INTEGER,read-only,,mandatory,,This counter indicates the maximum number of nodes that are up on the circuit.
.1.3.6.1.2.1.18.6.2.1.13,DECNET-PHIV-MIB::phivCircuitCountBytesRecd,INTEGER,read-only,,mandatory,,Number of bytes received on this circuit.
.1.3.6.1.2.1.18.6.2.1.14,DECNET-PHIV-MIB::phivCircuitCountBytesSent,INTEGER,read-only,,mandatory,,Number of bytes sent on this circuit.
.1.3.6.1.2.1.18.6.2.1.15,DECNET-PHIV-MIB::phivCircuitCountDataBlocksRecd,INTEGER,read-only,,mandatory,,Number of data blocks received on this circuit.
.1.3.6.1.2.1.18.6.2.1.16,DECNET-PHIV-MIB::phivCircuitCountDataBlocksSent,INTEGER,read-only,,mandatory,,Number of data blocks sent on this circuit.
.1.3.6.1.2.1.18.6.2.1.17,DECNET-PHIV-MIB::phivCircuitCountUsrBuffUnav,INTEGER,read-only,,mandatory,,Number of user buffer unavailable errors.
.1.3.6.1.2.1.18.6.3,DECNET-PHIV-MIB::phivCircuitOrigQueueLimit,INTEGER,read-write,,mandatory,,This parameter indicates the maximum number of originating packets that may be outstanding on this circuit. This does not include route-thru traffic.
.1.3.6.1.2.1.18.6.4,DECNET-PHIV-MIB::phivCircuitCountZeroCount,INTEGER,read-write,,mandatory,other(1):reset(2),When this value is set to 2, all of the counters in the Circuit Counter Table are set to zero.
.1.3.6.1.2.1.18.7,DECNET-PHIV-MIB::ddcmp,,,,,,
.1.3.6.1.2.1.18.7.1,DECNET-PHIV-MIB::phivDDCMPCircuitParametersTable,,not-accessible,,mandatory,,Information about DDCMP circuit parameters.
.1.3.6.1.2.1.18.7.1.1,DECNET-PHIV-MIB::phivDDCMPCircuitParametersEntry,,not-accessible,phivDDCMPCircuitIndex,mandatory,,Parameters information about DDCMP circuits currently known.
.1.3.6.1.2.1.18.7.1.1.1,DECNET-PHIV-MIB::phivDDCMPCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known DDCMP circuit. This is the same value as phivCircuitIndex.
.1.3.6.1.2.1.18.7.1.1.2,DECNET-PHIV-MIB::phivDDCMPCircuitAdjNodeAddr,OCTET,read-only,,mandatory,,The address of the adjacent node.
.1.3.6.1.2.1.18.7.1.1.3,DECNET-PHIV-MIB::phivDDCMPCircuitTributary,INTEGER,read-only,,mandatory,,This value represents the Data Link physical tributary address of the circuit.
.1.3.6.1.2.1.18.7.2,DECNET-PHIV-MIB::phivDDCMPCircuitCountTable,,not-accessible,,mandatory,,Information about the DDCMP counters associated with all circuits currently known.
.1.3.6.1.2.1.18.7.2.1,DECNET-PHIV-MIB::phivDDCMPCircuitCountEntry,,not-accessible,phivCircuitIndex,mandatory,,Counter information about DDCMP circuits now known
.1.3.6.1.2.1.18.7.2.1.1,DECNET-PHIV-MIB::phivDDCMPCircuitErrorsInbd,INTEGER,read-only,,mandatory,,Number of Data errors inbound.
.1.3.6.1.2.1.18.7.2.1.2,DECNET-PHIV-MIB::phivDDCMPCircuitErrorsOutbd,INTEGER,read-only,,mandatory,,Number of outbound data errors.
.1.3.6.1.2.1.18.7.2.1.3,DECNET-PHIV-MIB::phivDDCMPCircuitRmteReplyTimeouts,INTEGER,read-only,,mandatory,,Number of remote reply timeouts.
.1.3.6.1.2.1.18.7.2.1.4,DECNET-PHIV-MIB::phivDDCMPCircuitLocalReplyTimeouts,INTEGER,read-only,,mandatory,,Number of local Reply timeouts.
.1.3.6.1.2.1.18.7.2.1.5,DECNET-PHIV-MIB::phivDDCMPCircuitRmteBuffErrors,INTEGER,read-only,,mandatory,,Number of remote reply time out errors.
.1.3.6.1.2.1.18.7.2.1.6,DECNET-PHIV-MIB::phivDDCMPCircuitLocalBuffErrors,INTEGER,read-only,,mandatory,,Number of local buffer errors.
.1.3.6.1.2.1.18.7.2.1.7,DECNET-PHIV-MIB::phivDDCMPCircuitSelectIntervalsElap,INTEGER,read-only,,mandatory,,Selection intervals that have elapsed.
.1.3.6.1.2.1.18.7.2.1.8,DECNET-PHIV-MIB::phivDDCMPCircuitSelectTimeouts,INTEGER,read-only,,mandatory,,Number of selection timeouts.
.1.3.6.1.2.1.18.7.3,DECNET-PHIV-MIB::phivDDCMPLineCountTable,,not-accessible,,mandatory,,The DDCMP Line Count Table.
.1.3.6.1.2.1.18.7.3.1,DECNET-PHIV-MIB::phivDDCMPLineCountEntry,,not-accessible,phivDDCMPLineCountIndex,mandatory,,There is one entry in the table for each line.
.1.3.6.1.2.1.18.7.3.1.1,DECNET-PHIV-MIB::phivDDCMPLineCountIndex,INTEGER,read-only,,mandatory,,The line on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of phivLineIndex. This value is the ifIndex.
.1.3.6.1.2.1.18.7.3.1.2,DECNET-PHIV-MIB::phivDDCMPLineCountDataErrsIn,INTEGER,read-only,,mandatory,,Number of data errors inbound.
.1.3.6.1.2.1.18.7.3.1.3,DECNET-PHIV-MIB::phivDDCMPLineCountRmteStationErrs,INTEGER,read-only,,mandatory,,Number of remote station errors.
.1.3.6.1.2.1.18.7.3.1.4,DECNET-PHIV-MIB::phivDDCMPLineCountLocalStationErrs,INTEGER,read-only,,mandatory,,Number of local station errors.
.1.3.6.1.2.1.18.8,DECNET-PHIV-MIB::control,,,,,,
.1.3.6.1.2.1.18.8.1,DECNET-PHIV-MIB::phivControlSchedTimer,INTEGER,read-only,,mandatory,,This value represents the number of milliseconds between recalculation of tributary polling priorities.
.1.3.6.1.2.1.18.8.2,DECNET-PHIV-MIB::phivControlDeadTimer,INTEGER,read-only,,mandatory,,This value represents the number of milliseconds between polls of one of the set of dead tributaries.
.1.3.6.1.2.1.18.8.3,DECNET-PHIV-MIB::phivControlDelayTimer,INTEGER,read-only,,mandatory,,This value represents the minimum number of milliseconds to delay between polls. The delay timer limits the effect of a very fast control station on slow tributaries.
.1.3.6.1.2.1.18.8.4,DECNET-PHIV-MIB::phivControlStreamTimer,INTEGER,read-only,,mandatory,,This value represents the number of milliseconds a tributary or a half duplex remote station is allowed to hold the line. NOTE: This parameter can also be applied to half-duplex lines of type DDCMP POINT.
.1.3.6.1.2.1.18.8.5,DECNET-PHIV-MIB::phivControlParametersTable,,not-accessible,,mandatory,,Information about control circuit parameters.
.1.3.6.1.2.1.18.8.5.1,DECNET-PHIV-MIB::phivControlParametersEntry,,not-accessible,phivControlCircuitIndex,mandatory,,Parameters information about control circuits currently known.
.1.3.6.1.2.1.18.8.5.1.1,DECNET-PHIV-MIB::phivControlCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known multipoint control circuit. This is the same value as phivCircuitIndex.
.1.3.6.1.2.1.18.8.5.1.2,DECNET-PHIV-MIB::phivControlBabbleTimer,INTEGER,read-write,,mandatory,,This value represents the number of milliseconds that a selected tributary or remote half-duplex station is allowed to transmit.
.1.3.6.1.2.1.18.8.5.1.3,DECNET-PHIV-MIB::phivControlMaxBuffs,INTEGER,read-write,,mandatory,,This value represents the maximum number of buffers the tributary can use from a common buffer pool. If not set, there is no common buffer pool and buffers are explicitly supplied by the higher level. Count is a decimal integer in the range 1-254.
.1.3.6.1.2.1.18.8.5.1.4,DECNET-PHIV-MIB::phivControlMaxTransmits,INTEGER,read-write,,mandatory,,This value represents the maximum number of data messages that can be transmitted at one time. Count is a decimal integer in the range 1-255.
.1.3.6.1.2.1.18.8.5.1.5,DECNET-PHIV-MIB::phivControlDyingBase,INTEGER,read-write,,mandatory,,This value represents the base priority to which a tributary is reset each time it has been polled. A separate base can be set for each of the indicated polling states. Base is a decimal integer in the range 0-255. If not set, the defaults are: active, 255; inactive, 0; and dying, 0.
.1.3.6.1.2.1.18.8.5.1.6,DECNET-PHIV-MIB::phivControlDyingIncrement,INTEGER,read-write,,mandatory,,This value represents the increment added to the tributary priority each time the scheduling timer expires. If not set, the defaults are: active, 0; inactive, 64; and dying, 16.
.1.3.6.1.2.1.18.8.5.1.7,DECNET-PHIV-MIB::phivControlDeadThreshold,INTEGER,read-write,,mandatory,,This value represents the number of times to poll the active, inactive, or dying tributary before changing its polling state to dead because of receive timeouts. Count is a decimal integer in the range 0-255.
.1.3.6.1.2.1.18.8.5.1.8,DECNET-PHIV-MIB::phivControlDyingThreshold,INTEGER,read-write,,mandatory,,This value represents the number of times to poll the active or inactive tributary before changing its polling state to dying because of receive timeouts. Count is a decimal integer in the range 0-255.
.1.3.6.1.2.1.18.8.5.1.9,DECNET-PHIV-MIB::phivControlInactTreshold,INTEGER,read-write,,mandatory,,This value represents the number of times to poll the active tributary before changing its polling state to inactive because of no data response. Count is a decimal integer in the range 0-255.
.1.3.6.1.2.1.18.8.5.1.10,DECNET-PHIV-MIB::phivControlPollingState,INTEGER,read-write,,mandatory,automatic(1):active(2):inactive(3):dying(4):dead(5),This value represents the state of the tributary relative to the multipoint polling algorithm. If not set the default is AUTOMATIC. The possible states are: AUTOMATIC The tributary's state is allowed to vary according to the operation of the polling algorithm. ACTIVE/INACTIVE/DYING/DEAD The tributary is locked in the specified state. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155.
.1.3.6.1.2.1.18.8.5.1.11,DECNET-PHIV-MIB::phivControlPollingSubState,INTEGER,read-only,,mandatory,active(1):inactive(2):dying(3):dead(4),This value represents the tributary's state as determined by the polling algorithm. This applies only when the polling state is AUTOMATIC and is read-only to Network Management. Polling-substate is one of ACTIVE, INACTIVE, DYING, or DEAD. It is displayed as a tag on the polling state, for example: AUTOMATIC-INACTIVE.
.1.3.6.1.2.1.18.8.5.1.12,DECNET-PHIV-MIB::phivControlTransTimer,INTEGER,read-write,,mandatory,,This value represents the number of milliseconds to delay between data message transmits. Milliseconds is a decimal integer in the range 0-65535.
.1.3.6.1.2.1.18.9,DECNET-PHIV-MIB::ethernet,,,,,,
.1.3.6.1.2.1.18.9.1,DECNET-PHIV-MIB::phivEthLinkParametersTable,,not-accessible,,mandatory,,Information about ethernet link parameters.
.1.3.6.1.2.1.18.9.1.1,DECNET-PHIV-MIB::phivEthLinkParametersEntry,,not-accessible,phivEthLinkIndex,mandatory,,Parameter information about ethernet links currently known.
.1.3.6.1.2.1.18.9.1.1.1,DECNET-PHIV-MIB::phivEthLinkIndex,INTEGER,read-only,,mandatory,,The circuit over which this links information is collected. This is the same as phivCircuitIndex.
.1.3.6.1.2.1.18.9.1.1.2,DECNET-PHIV-MIB::phivEthDesigRouterNodeAddr,OCTET,read-only,,mandatory,,This value is the address of the designated router.
.1.3.6.1.2.1.18.9.1.1.3,DECNET-PHIV-MIB::phivEthMaxRouters,INTEGER,read-write,,mandatory,,This parameter is the maximum number of routers (other than the executor itself) allowed on the circuit by Routing for circuits that are owned by the executor node.
.1.3.6.1.2.1.18.9.1.1.4,DECNET-PHIV-MIB::phivEthRouterPri,INTEGER,read-write,,mandatory,,This parameter is the priority that this router is to have in the selection of designated router for the circuit on circuits that are owned by the executor node.
.1.3.6.1.2.1.18.9.1.1.5,DECNET-PHIV-MIB::phivEthHardwareAddr,OCTET,read-only,,mandatory,,This read-only parameter is the address that is associated with the line device hardware as seen by the DECnet Software. This value is not the same as ifPhysAddress.
.1.3.6.1.2.1.18.10,DECNET-PHIV-MIB::counters,,,,,,
.1.3.6.1.2.1.18.10.1,DECNET-PHIV-MIB::phivCountersCountTable,,not-accessible,,mandatory,,Information about ethernet link counters.
.1.3.6.1.2.1.18.10.1.1,DECNET-PHIV-MIB::phivCountersCountEntry,,not-accessible,phivCountersIndex,mandatory,,Counter information about ethernet links currently known.
.1.3.6.1.2.1.18.10.1.1.1,DECNET-PHIV-MIB::phivCountersIndex,INTEGER,read-only,,mandatory,,The interface to which these counters apply. This is the same interface as identified by the same value of phivLineIndex. This value is the ifIndex.
.1.3.6.1.2.1.18.10.1.1.2,DECNET-PHIV-MIB::phivCountersCountBytesRecd,INTEGER,read-only,,mandatory,,Number of bytes received over this link.
.1.3.6.1.2.1.18.10.1.1.3,DECNET-PHIV-MIB::phivCountersCountBytesSent,INTEGER,read-only,,mandatory,,Number of bytes sent over this link.
.1.3.6.1.2.1.18.10.1.1.4,DECNET-PHIV-MIB::phivCountersCountDataBlocksRecd,INTEGER,read-only,,obsolete,,Number of data blocks received over this link.
.1.3.6.1.2.1.18.10.1.1.5,DECNET-PHIV-MIB::phivCountersCountDataBlocksSent,INTEGER,read-only,,obsolete,,Number of data blocks sent over this link.
.1.3.6.1.2.1.18.10.1.1.6,DECNET-PHIV-MIB::phivCountersCountEthUsrBuffUnav,INTEGER,read-only,,mandatory,,Number of user buffer unavailable errors over this link.
.1.3.6.1.2.1.18.10.1.1.7,DECNET-PHIV-MIB::phivCountersCountMcastBytesRecd,INTEGER,read-only,,mandatory,,Number of multicast bytes received over this link.
.1.3.6.1.2.1.18.10.1.1.8,DECNET-PHIV-MIB::phivCountersCountDataBlksRecd,INTEGER,read-only,,mandatory,,Number of data blocks received over this link.
.1.3.6.1.2.1.18.10.1.1.9,DECNET-PHIV-MIB::phivCountersCountDataBlksSent,INTEGER,read-only,,mandatory,,Number of data blocks sent over this link.
.1.3.6.1.2.1.18.10.1.1.10,DECNET-PHIV-MIB::phivCountersCountMcastBlksRecd,INTEGER,read-only,,mandatory,,Number of multicast blocks received over this link.
.1.3.6.1.2.1.18.10.1.1.11,DECNET-PHIV-MIB::phivCountersCountBlksSentDef,INTEGER,read-only,,mandatory,,Number of blocks sent, initially deferred over this link.
.1.3.6.1.2.1.18.10.1.1.12,DECNET-PHIV-MIB::phivCountersCountBlksSentSingleCol,INTEGER,read-only,,mandatory,,Number of blocks sent, single collision over this link.
.1.3.6.1.2.1.18.10.1.1.13,DECNET-PHIV-MIB::phivCountersCountBlksSentMultCol,INTEGER,read-only,,mandatory,,Number of blocks sent, multiple collisions over this link.
.1.3.6.1.2.1.18.10.1.1.14,DECNET-PHIV-MIB::phivCountersCountSendFailure,INTEGER,read-only,,mandatory,,Number of send failures over this link.
.1.3.6.1.2.1.18.10.1.1.15,DECNET-PHIV-MIB::phivCountersCountCollDetectFailure,INTEGER,read-only,,mandatory,,Number of collision detect check failures over this link.
.1.3.6.1.2.1.18.10.1.1.16,DECNET-PHIV-MIB::phivCountersCountReceiveFailure,INTEGER,read-only,,mandatory,,Number of receive failures over this link.
.1.3.6.1.2.1.18.10.1.1.17,DECNET-PHIV-MIB::phivCountersCountUnrecFrameDest,INTEGER,read-only,,mandatory,,Number of unrecognized frame destinations over this link.
.1.3.6.1.2.1.18.10.1.1.18,DECNET-PHIV-MIB::phivCountersCountDataOver,INTEGER,read-only,,mandatory,,Number of data overruns over this link.
.1.3.6.1.2.1.18.10.1.1.19,DECNET-PHIV-MIB::phivCountersCountSysBuffUnav,INTEGER,read-only,,mandatory,,Number of system buffer unavailables over this link.
.1.3.6.1.2.1.18.10.1.1.20,DECNET-PHIV-MIB::phivCountersCountUsrBuffUnav,INTEGER,read-only,,mandatory,,Number of user buffer unavailables.
.1.3.6.1.2.1.18.11,DECNET-PHIV-MIB::adjacency,,,,,,
.1.3.6.1.2.1.18.11.1,DECNET-PHIV-MIB::phivAdjTable,,not-accessible,,obsolete,,The Adjacency Table.
.1.3.6.1.2.1.18.11.1.1,DECNET-PHIV-MIB::phivAdjEntry,,not-accessible,phivAdjCircuitIndex,obsolete,,There is one entry in the table for each adjacency.
.1.3.6.1.2.1.18.11.1.1.1,DECNET-PHIV-MIB::phivAdjCircuitIndex,INTEGER,read-only,,obsolete,,A unique index value for each known circuit.
.1.3.6.1.2.1.18.11.1.1.2,DECNET-PHIV-MIB::phivAdjNodeAddr,OCTET,read-only,,obsolete,,The address of the adjacent node.
.1.3.6.1.2.1.18.11.1.1.3,DECNET-PHIV-MIB::phivAdjBlockSize,INTEGER,read-only,,obsolete,,This read-only parameter is the block size that was negotiated with the adjacent Routing layer during Routing initialization over a particular circuit. It includes the routing header, but excludes the data link header. This parameter is qualified by ADJACENT NODE.
.1.3.6.1.2.1.18.11.1.1.4,DECNET-PHIV-MIB::phivAdjListenTimer,INTEGER,read-only,,obsolete,,This value determines the maximum number of seconds allowed to elapse before Routing receives some message (either a Hello message or a user message) from the adjacent node on the circuit. It was agreed during Routing initialization with the adjacent Routing layer. This parameter is qualified by ADJACENT NODE.
.1.3.6.1.2.1.18.11.1.1.5,DECNET-PHIV-MIB::phivAdjCircuitEtherServPhysAddr,OCTET,read-only,,obsolete,,This parameter indicates the Ethernet physical address of an adjacent node that is being serviced on this circuit. This parameter is a qualifier for SERVICE SUBSTATE.
.1.3.6.1.2.1.18.11.1.1.6,DECNET-PHIV-MIB::phivAdjType,INTEGER,read-only,,obsolete,routing-III(1):nonrouting-III(2):area(3):routing-IV(4):nonrouting-IV(5),This parameter indicates the type of adjacency. For adjacent nodes, this is a read-only parameter that indicates the type of the reachable adjacent node. NOTE: The routing-III and nonrouting-III values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155)
.1.3.6.1.2.1.18.11.1.1.7,DECNET-PHIV-MIB::phivAdjState,INTEGER,read-only,,obsolete,initializing(1):up(2):run(3):circuit-rejected(4):data-link-start(5):routing-layer-initialize(6):routing-layer-verify(7):routing-layer-complete(8):off(9):halt(10),This value indicates the state of a router adjacency. On adjacencies over a circuit of type (phivCircuitCommonType) Ethernet, CI, or FDDI, with an adjacent node of type (phivAdjType) ROUTING IV or AREA, this variable is the state of the Ethernet Initialization Layer for this adjacency, and can have values INITIALIZING or UP. (See Section 9.1.1 of DECnet Phase IV Routing Layer Functional Specification.) On adjacencies over a circuit of type (phivCircuitCommonType) Ethernet, CI, or FDDI, with an adjacent node of type (phivAdjType) NONROUTING IV, this variable will always take on the value UP. On adjacencies over a circuit of type (phivCircuitCommonType) DDCMP POINT, DDCMP CONTROL, DDCMP TRIBUTARY, DDCMP DMC, or X.25, this variable is the state of the Routing Layer Initialization Circuit State. (See section 7.3, ibid.) It can have values between RUN and HALT. On adjacencies over a circuit of type (phivCircuitCommonType) OTHER, this variable may be used in a manner consistent with the Initialization Layer used on that circuit.
.1.3.6.1.2.1.18.11.1.1.8,DECNET-PHIV-MIB::phivAdjPriority,INTEGER,read-only,,obsolete,,Priority assigned by the adjacent node for this circuit.
.1.3.6.1.2.1.18.11.1.1.9,DECNET-PHIV-MIB::phivAdjExecListenTimer,INTEGER,read-only,,obsolete,,This read-only value determines the maximum number of seconds allowed to elapse before Routing receives some message (either a Hello message or a user message) from the adjacent node on the circuit. It was agreed during Routing initialization with the adjacent Routing layer.
.1.3.6.1.2.1.18.11.2,DECNET-PHIV-MIB::phivAdjNodeTable,,not-accessible,,mandatory,,The Adjacent Node Table.
.1.3.6.1.2.1.18.11.2.1,DECNET-PHIV-MIB::phivAdjNodeEntry,,not-accessible,phivAdjNodeCircuitIndex:phivAdjAddr,mandatory,,There is one entry in the table for each adjacency.
.1.3.6.1.2.1.18.11.2.1.1,DECNET-PHIV-MIB::phivAdjNodeCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known circuit. This value is the same as phivCircuitIndex and identifies the circuit over which the adjacency is realized.
.1.3.6.1.2.1.18.11.2.1.2,DECNET-PHIV-MIB::phivAdjAddr,OCTET,read-only,,mandatory,,The address of the adjacent node.
.1.3.6.1.2.1.18.11.2.1.3,DECNET-PHIV-MIB::phivAdjNodeBlockSize,INTEGER,read-only,,mandatory,,This read-only parameter is the block size that was negotiated with the adjacent Routing layer during Routing initialization over a particular circuit. It includes the routing header, but excludes the data link header. This parameter is qualified by ADJACENT NODE.
.1.3.6.1.2.1.18.11.2.1.4,DECNET-PHIV-MIB::phivAdjNodeListenTimer,INTEGER,read-only,,mandatory,,This value determines the maximum number of seconds allowed to elapse before Routing receives some message (either a Hello message or a user message) from the adjacent node on the circuit. It was agreed during Routing initialization with the adjacent Routing layer. This parameter is qualified by ADJACENT NODE.
.1.3.6.1.2.1.18.11.2.1.5,DECNET-PHIV-MIB::phivAdjNodeCircuitEtherServPhysAddr,OCTET,read-only,,mandatory,,This parameter indicates the Ethernet physical address of an adjacent node that is being serviced on this circuit. This parameter is a qualifier for SERVICE SUBSTATE.
.1.3.6.1.2.1.18.11.2.1.6,DECNET-PHIV-MIB::phivAdjNodeType,INTEGER,read-only,,mandatory,routing-III(1):nonrouting-III(2):area(3):routing-IV(4):nonrouting-IV(5),This parameter indicates the type of adjacency. For adjacent nodes, this is a read-only parameter that indicates the type of the reachable adjacent node. NOTE: The routing-III and nonrouting-III values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155)
.1.3.6.1.2.1.18.11.2.1.7,DECNET-PHIV-MIB::phivAdjNodeState,INTEGER,read-only,,mandatory,initializing(1):up(2):run(3):circuit-rejected(4):data-link-start(5):routing-layer-initialize(6):routing-layer-verify(7):routing-layer-complete(8):off(9):halt(10),This value indicates the state of a router adjacency. On adjacencies over a circuit of type (phivCircuitCommonType) Ethernet, CI, or FDDI, with an adjacent node of type (phivAdjNodeType) ROUTING IV or AREA, this variable is the state of the Ethernet Initialization Layer for this adjacency, and can have values INITIALIZING or UP. (See Section 9.1.1 of DECnet Phase IV Routing Layer Functional Specification.) On adjacencies over a circuit of type (phivCircuitCommonType) Ethernet, CI, or FDDI, with an adjacent node of type (phivAdjNodeType) NONROUTING IV, this variable will always take on the value UP. On adjacencies over a circuit of type (phivCircuitCommonType) DDCMP POINT, DDCMP CONTROL, DDCMP TRIBUTARY, DDCMP DMC, or X.25, this variable is the state of the Routing Layer Initialization Circuit State. (See section 7.3, ibid.) It can have values between RUN and HALT. On adjacencies over a circuit of type (phivCircuitCommonType) OTHER, this variable may be used in a manner consistent with the Initialization Layer used on that circuit.
.1.3.6.1.2.1.18.11.2.1.8,DECNET-PHIV-MIB::phivAdjNodePriority,INTEGER,read-only,,mandatory,,Priority assigned by the adjacent node for this circuit.
.1.3.6.1.2.1.18.12,DECNET-PHIV-MIB::line,,,,,,
.1.3.6.1.2.1.18.12.1,DECNET-PHIV-MIB::phivLineTable,,not-accessible,,mandatory,,The Line Table.
.1.3.6.1.2.1.18.12.1.1,DECNET-PHIV-MIB::phivLineEntry,,not-accessible,phivLineIndex,mandatory,,There is one entry in the table for each line.
.1.3.6.1.2.1.18.12.1.1.1,DECNET-PHIV-MIB::phivLineIndex,INTEGER,read-only,,mandatory,,The line on which this entry's equivalence is effective. This is the same as the ifIndex.
.1.3.6.1.2.1.18.12.1.1.2,DECNET-PHIV-MIB::phivLineName,OCTET,read-only,,mandatory,,The name of the line on this row of the table.
.1.3.6.1.2.1.18.12.1.1.3,DECNET-PHIV-MIB::phivLineState,INTEGER,read-only,,mandatory,on(1):off(2):service(3):cleared(4),This value represents Network Management operational state. NOTE that these values are incremented by one compared to the standard DECnet values.
.1.3.6.1.2.1.18.12.1.1.4,DECNET-PHIV-MIB::phivLineSubstate,INTEGER,read-only,,mandatory,starting(1):reflecting(2):looping(3):loading(4):dumping(5):triggering(6):auto-service(7):auto-loading(8):auto-dumping(9):auto-triggering(10):synchronizing(11):failed(12):running(13),This value represents the line's read-only Network Management substate. NOTE that these values are incremented by one compared to the standard DECnet values.
.1.3.6.1.2.1.18.12.1.1.5,DECNET-PHIV-MIB::phivLineService,INTEGER,read-only,,mandatory,starting(1):reflecting(2):looping(3):other(4),This value represents the line's read-only Network Management service. NOTE that these values are incremented by one compared to the standard DECnet values and OTHER is a new addition.
.1.3.6.1.2.1.18.12.1.1.6,DECNET-PHIV-MIB::phivLineDevice,OCTET,read-only,,mandatory,,This value represents the Physical Link device to be used on the line.
.1.3.6.1.2.1.18.12.1.1.7,DECNET-PHIV-MIB::phivLineReceiveBuffs,INTEGER,read-only,,mandatory,,This value represents the number of receive buffers reserved for the line. It is a decimal number in the range 0-65535. 0 is supported for those vendors that do not reserve buffers on a per line basis and use a pool of buffers that can be used by any line.
.1.3.6.1.2.1.18.12.1.1.8,DECNET-PHIV-MIB::phivLineProtocol,INTEGER,read-only,,mandatory,ddcmp-point(1):ddcmp-control(2):ddcmp-tributary(3):reserved(4):ddcmp-dmc(5):olapb(6):ethernet(7):ci(8):qp2(9):other(14):fddi(15),This value represents the protocol used on the line device. Note that these values are incremented by one compared to the standard DECnet values.
.1.3.6.1.2.1.18.12.1.1.9,DECNET-PHIV-MIB::phivLineServiceTimer,INTEGER,read-only,,mandatory,,This value represents the amount of time in milliseconds allowed to elapse before a Data Link receive request completes while doing service operations.
.1.3.6.1.2.1.18.12.1.1.10,DECNET-PHIV-MIB::phivLineMaxBlock,INTEGER,read-only,,mandatory,,This value represents the Data Link maximum block size on the line.
.1.3.6.1.2.1.18.14,DECNET-PHIV-MIB::nonBroadcastLine,,,,,,
.1.3.6.1.2.1.18.14.1,DECNET-PHIV-MIB::phivNonBroadcastTable,,not-accessible,,mandatory,,The Non Broadcast Table.
.1.3.6.1.2.1.18.14.1.1,DECNET-PHIV-MIB::phivNonBroadcastEntry,,not-accessible,phivNonBroadcastIndex,mandatory,,There is one entry in the table for each Non Broadcast line.
.1.3.6.1.2.1.18.14.1.1.1,DECNET-PHIV-MIB::phivNonBroadcastIndex,INTEGER,read-only,,mandatory,,The Non Broadcast line on which this entry's equivalence is effective. This is the same value as the ifIndex.
.1.3.6.1.2.1.18.14.1.1.2,DECNET-PHIV-MIB::phivNonBroadcastController,INTEGER,read-only,,mandatory,normal(1):loopback(2):other(3),This value represents the Physical Link hardware controller mode for the line device. The values for controller-mode are: NORMAL For normal controller operating mode. LOOPBACK For software controllable loopback of the controller. On those devices that can support this mode, it causes all transmitted messages to be looped back from within the controller itself. This is accomplished without any manual intervention other than the setting of this parameter value. OTHER indicates function is not supported Note that these values are incremented by one compared to the standard DECnet values.
.1.3.6.1.2.1.18.14.1.1.3,DECNET-PHIV-MIB::phivNonBroadcastDuplex,INTEGER,read-only,,mandatory,full(1):half(2),This value represents the Physical Link hardware duplex mode of the line device. The possible modes are: FULL Full-duplex HALF Half-duplex Note that these values are incremented by one compared to the standard DECnet values.
.1.3.6.1.2.1.18.14.1.1.4,DECNET-PHIV-MIB::phivNonBroadcastClock,INTEGER,read-only,,mandatory,external(1):internal(2):other(3),This value represents the Physical Link hardware clock mode for the line device. The values for clock-mode are: INTERNAL For software controllable loopback use of the clock. On those devices that can support this mode, it causes the device to supply a clock signal such that a transmitted messages can be looped back from outside the device. This may require manual intervention other than the setting of this parameter value. For example, the operator may have to connect a loopback plug in place of the normal line. EXTERNAL For normal clock operating mode, where the clock signal is supplied externally to the controller. Note that these values are incremented by one compared to the standard DECnet values.
.1.3.6.1.2.1.18.14.1.1.5,DECNET-PHIV-MIB::phivNonBroadcastRetransmitTimer,INTEGER,read-only,,mandatory,,This value represents number of milliseconds before the Data Link retransmits a block on the line. On half-duplex lines, this parameter is the select timer.
.1.3.6.1.2.1.18.15,DECNET-PHIV-MIB::area,,,,,,
.1.3.6.1.2.1.18.15.1,DECNET-PHIV-MIB::phivAreaTable,,not-accessible,,mandatory,,Table of information kept on all areas known to this unit.
.1.3.6.1.2.1.18.15.1.1,DECNET-PHIV-MIB::phivAreaEntry,,not-accessible,phivAreaNum,mandatory,,The area routing information.
.1.3.6.1.2.1.18.15.1.1.1,DECNET-PHIV-MIB::phivAreaNum,INTEGER,read-only,,mandatory,,This value indicates the area number of this entry.
.1.3.6.1.2.1.18.15.1.1.2,DECNET-PHIV-MIB::phivAreaState,INTEGER,read-only,,mandatory,reachable(4):unreachable(5),This value indicates the state of the area
.1.3.6.1.2.1.18.15.1.1.3,DECNET-PHIV-MIB::phivAreaCost,Gauge32,read-only,,mandatory,,The total cost over the current path to the destination area. Cost is a value associated with using a circuit. Routing routes messages (data) along the path between 2 areas with the smallest cost.
.1.3.6.1.2.1.18.15.1.1.4,DECNET-PHIV-MIB::phivAreaHops,INTEGER,read-only,,mandatory,,The number of hops to a destination area. A hop is the routing value representing the logical distance between two areas in network.
.1.3.6.1.2.1.18.15.1.1.5,DECNET-PHIV-MIB::phivAreaNextNode,OCTET,read-only,,mandatory,,The next node on the circuit used to get to the area under scrutiny.
.1.3.6.1.2.1.18.15.1.1.6,DECNET-PHIV-MIB::phivAreaCircuitIndex,INTEGER,read-only,,mandatory,,A unique index value for each known circuit.
.1.3.6.1.2.1.18.15.2,DECNET-PHIV-MIB::phivAreaMaxCost,INTEGER,read-write,,mandatory,,This value represents the maximum total path cost allowed from the executor to any other level 2 routing node. The AREA MAXIMUM COST number is decimal in the range 1-1022. This parameter is only applicable if the executor node is of type AREA.
.1.3.6.1.2.1.18.15.3,DECNET-PHIV-MIB::phivAreaMaxHops,INTEGER,read-write,,mandatory,,This value represents the maximum number of routing hops allowable from the executor to any other level 2 routing node. This parameter is only applicable if the executor node is of type AREA.
.1.3.6.1.2.1.18.15.4,DECNET-PHIV-MIB::phivRouteMaxArea,INTEGER,read-write,,mandatory,,This value represents the largest area number and, therefore, number of areas that can be known about by the executor node's Routing. This parameter is only applicable if the executor node is of type AREA.
.1.3.6.1.2.1.19,CHARACTER-MIB::char,,,,,,The MIB module for character stream devices.
.1.3.6.1.2.1.19.1,CHARACTER-MIB::charNumber,Integer32,read-only,,current,,The number of entries in charPortTable, regardless of their current state.
.1.3.6.1.2.1.19.2,CHARACTER-MIB::charPortTable,,not-accessible,,current,,A list of port entries. The number of entries is given by the value of charNumber.
.1.3.6.1.2.1.19.2.1,CHARACTER-MIB::charPortEntry,,not-accessible,charPortIndex,current,,Status and parameter values for a character port.
.1.3.6.1.2.1.19.2.1.1,CHARACTER-MIB::charPortIndex,Integer32,read-only,,current,,A unique value for each character port, perhaps corresponding to the same value of ifIndex when the character port is associated with a hardware port represented by an ifIndex.
.1.3.6.1.2.1.19.2.1.2,CHARACTER-MIB::charPortName,,,,current,,An administratively assigned name for the port, typically with some local significance.
.1.3.6.1.2.1.19.2.1.3,CHARACTER-MIB::charPortType,INTEGER,read-only,,current,physical(1):virtual(2),The port's type, 'physical' if the port represents an external hardware connector, 'virtual' if it does not.
.1.3.6.1.2.1.19.2.1.4,CHARACTER-MIB::charPortHardware,OBJECT,read-only,,current,,A reference to hardware MIB definitions specific to a physical port's external connector. For example, if the connector is RS-232, then the value of this object refers to a MIB sub-tree defining objects specific to RS-232. If an agent is not configured to have such values, the agent returns the object identifier: nullHardware OBJECT IDENTIFIER ::= { 0 0 } 
.1.3.6.1.2.1.19.2.1.5,CHARACTER-MIB::charPortReset,INTEGER,read-write,,current,ready(1):execute(2),A control to force the port into a clean, initial state, both hardware and software, disconnecting all the port's existing sessions. In response to a get-request or get-next-request, the agent always returns 'ready' as the value. Setting the value to 'execute' causes a reset.
.1.3.6.1.2.1.19.2.1.6,CHARACTER-MIB::charPortAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2):off(3):maintenance(4),The port's desired state, independent of flow control. 'enabled' indicates that the port is allowed to pass characters and form new sessions. 'disabled' indicates that the port is allowed to pass characters but not form new sessions. 'off' indicates that the port is not allowed to pass characters or have any sessions. 'maintenance' indicates a maintenance mode, exclusive of normal operation, such as running a test. 'enabled' corresponds to ifAdminStatus 'up'. 'disabled' and 'off' correspond to ifAdminStatus 'down'. 'maintenance' corresponds to ifAdminStatus 'test'.
.1.3.6.1.2.1.19.2.1.7,CHARACTER-MIB::charPortOperStatus,INTEGER,read-only,,current,up(1):down(2):maintenance(3):absent(4):active(5),The port's actual, operational state, independent of flow control. 'up' indicates able to function normally. 'down' indicates inability to function for administrative or operational reasons. 'maintenance' indicates a maintenance mode, exclusive of normal operation, such as running a test. 'absent' indicates that port hardware is not present. 'active' indicates up with a user present (e.g. logged in). 'up' and 'active' correspond to ifOperStatus 'up'. 'down' and 'absent' correspond to ifOperStatus 'down'. 'maintenance' corresponds to ifOperStatus 'test'.
.1.3.6.1.2.1.19.2.1.8,CHARACTER-MIB::charPortLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the port entered its current operational state. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.19.2.1.9,CHARACTER-MIB::charPortInFlowType,INTEGER,read-write,,deprecated,none(1):xonXoff(2):hardware(3):ctsRts(4):dsrDtr(5),The port's type of input flow control. 'none' indicates no flow control at this level or below. 'xonXoff' indicates software flow control by recognizing XON and XOFF characters. 'hardware' indicates flow control delegated to the lower level, for example a parallel port. 'ctsRts' and 'dsrDtr' are specific to RS-232-like ports. Although not architecturally pure, they are included here for simplicity's sake.
.1.3.6.1.2.1.19.2.1.10,CHARACTER-MIB::charPortOutFlowType,INTEGER,read-write,,deprecated,none(1):xonXoff(2):hardware(3):ctsRts(4):dsrDtr(5),The port's type of output flow control. 'none' indicates no flow control at this level or below. 'xonXoff' indicates software flow control by recognizing XON and XOFF characters. 'hardware' indicates flow control delegated to the lower level, for example a parallel port. 'ctsRts' and 'dsrDtr' are specific to RS-232-like ports. Although not architecturally pure, they are included here for simplicy's sake.
.1.3.6.1.2.1.19.2.1.11,CHARACTER-MIB::charPortInFlowState,INTEGER,read-only,,current,none(1):unknown(2):stop(3):go(4),The current operational state of input flow control on the port. 'none' indicates not applicable. 'unknown' indicates this level does not know. 'stop' indicates flow not allowed. 'go' indicates flow allowed.
.1.3.6.1.2.1.19.2.1.12,CHARACTER-MIB::charPortOutFlowState,INTEGER,read-only,,current,none(1):unknown(2):stop(3):go(4),The current operational state of output flow control on the port. 'none' indicates not applicable. 'unknown' indicates this level does not know. 'stop' indicates flow not allowed. 'go' indicates flow allowed.
.1.3.6.1.2.1.19.2.1.13,CHARACTER-MIB::charPortInCharacters,Counter32,read-only,,current,,Total number of characters detected as input from the port since system re-initialization and while the port operational state was 'up', 'active', or 'maintenance', including, for example, framing, flow control (i.e. XON and XOFF), each occurrence of a BREAK condition, locally-processed input, and input sent to all sessions.
.1.3.6.1.2.1.19.2.1.14,CHARACTER-MIB::charPortOutCharacters,Counter32,read-only,,current,,Total number of characters detected as output to the port since system re-initialization and while the port operational state was 'up', 'active', or 'maintenance', including, for example, framing, flow control (i.e. XON and XOFF), each occurrence of a BREAK condition, locally-created output, and output received from all sessions.
.1.3.6.1.2.1.19.2.1.15,CHARACTER-MIB::charPortAdminOrigin,INTEGER,read-write,,current,dynamic(1):network(2):local(3):none(4),The administratively allowed origin for establishing session on the port. 'dynamic' allows 'network' or 'local' session establishment. 'none' disallows session establishment.
.1.3.6.1.2.1.19.2.1.16,CHARACTER-MIB::charPortSessionMaximum,INTEGER,read-write,,current,,The maximum number of concurrent sessions allowed on the port. A value of -1 indicates no maximum. Setting the maximum to less than the current number of sessions has unspecified results.
.1.3.6.1.2.1.19.2.1.17,CHARACTER-MIB::charPortSessionNumber,Gauge32,read-only,,current,,The number of open sessions on the port that are in the connecting, connected, or disconnecting state.
.1.3.6.1.2.1.19.2.1.18,CHARACTER-MIB::charPortSessionIndex,INTEGER,read-only,,current,,The value of charSessIndex for the port's first or only active session. If the port has no active session, the agent returns the value zero.
.1.3.6.1.2.1.19.2.1.19,CHARACTER-MIB::charPortInFlowTypes,OCTET,read-write,,current,,The port's types of input flow control at the software level. Hardware-level flow control is independently controlled by the appropriate hardware-level MIB. A value of zero indicates no flow control. Depending on the specific implementation, any or all combinations of flow control may be chosen by adding the values: 128 xonXoff, recognizing XON and XOFF characters 64 enqHost, ENQ/ACK to allow input to host 32 enqTerm, ACK to allow output to port 
.1.3.6.1.2.1.19.2.1.20,CHARACTER-MIB::charPortOutFlowTypes,OCTET,read-write,,current,,The port's types of output flow control at the software level. Hardware-level flow control is independently controlled by the appropriate hardware-level MIB. A value of zero indicates no flow control. Depending on the specific implementation, any or all combinations of flow control may be chosen by adding the values: 128 xonXoff, recognizing XON and XOFF characters 64 enqHost, ENQ/ACK to allow input to host 32 enqTerm, ACK to allow output to port 
.1.3.6.1.2.1.19.2.1.21,CHARACTER-MIB::charPortLowerIfIndex,Integer32,read-only,,current,,The ifIndex value of the lower level hardware supporting this character port, zero if none.
.1.3.6.1.2.1.19.3,CHARACTER-MIB::charSessTable,,not-accessible,,current,,A list of port session entries.
.1.3.6.1.2.1.19.3.1,CHARACTER-MIB::charSessEntry,,not-accessible,charSessPortIndex:charSessIndex,current,,Status and parameter values for a character port session.
.1.3.6.1.2.1.19.3.1.1,CHARACTER-MIB::charSessPortIndex,Integer32,read-only,,current,,The value of charPortIndex for the port to which this session belongs.
.1.3.6.1.2.1.19.3.1.2,CHARACTER-MIB::charSessIndex,INTEGER,read-only,,current,,The session index in the context of the port, a non-zero positive integer. Session indexes within a port need not be sequential. Session indexes may be reused for different ports. For example, port 1 and port 3 may both have a session 2 at the same time. Session indexes may have any valid integer value, with any meaning convenient to the agent implementation.
.1.3.6.1.2.1.19.3.1.3,CHARACTER-MIB::charSessKill,INTEGER,read-write,,current,ready(1):execute(2),A control to terminate the session. In response to a get-request or get-next-request, the agent always returns 'ready' as the value. Setting the value to 'execute' causes termination.
.1.3.6.1.2.1.19.3.1.4,CHARACTER-MIB::charSessState,INTEGER,read-only,,current,connecting(1):connected(2):disconnecting(3),The current operational state of the session, disregarding flow control. 'connected' indicates that character data could flow on the network side of session. 'connecting' indicates moving from nonexistent toward 'connected'. 'disconnecting' indicates moving from 'connected' or 'connecting' to nonexistent.
.1.3.6.1.2.1.19.3.1.5,CHARACTER-MIB::charSessProtocol,OBJECT,read-only,,current,,The network protocol over which the session is running. Other OBJECT IDENTIFIER values may be defined elsewhere, in association with specific protocols. However, this document assigns those of known interest as of this writing.
.1.3.6.1.2.1.19.3.1.6,CHARACTER-MIB::charSessOperOrigin,INTEGER,read-only,,current,unknown(1):network(2):local(3),The session's source of establishment.
.1.3.6.1.2.1.19.3.1.7,CHARACTER-MIB::charSessInCharacters,Counter32,read-only,,current,,This session's subset of charPortInCharacters.
.1.3.6.1.2.1.19.3.1.8,CHARACTER-MIB::charSessOutCharacters,Counter32,read-only,,current,,This session's subset of charPortOutCharacters.
.1.3.6.1.2.1.19.3.1.9,CHARACTER-MIB::charSessConnectionId,OBJECT,read-only,,current,,A reference to additional local MIB information. This should be the highest available related MIB, corresponding to charSessProtocol, such as Telnet. For example, the value for a TCP connection (in the absence of a Telnet MIB) is the object identifier of tcpConnState. If an agent is not configured to have such values, the agent returns the object identifier: nullConnectionId OBJECT IDENTIFIER ::= { 0 0 } 
.1.3.6.1.2.1.19.3.1.10,CHARACTER-MIB::charSessStartTime,TimeTicks,read-only,,current,,The value of sysUpTime in MIB-2 when the session entered connecting state.
.1.3.6.1.2.1.19.4,CHARACTER-MIB::wellKnownProtocols,,,,,,
.1.3.6.1.2.1.19.4.1,CHARACTER-MIB::protocolOther,,,,,,
.1.3.6.1.2.1.19.4.2,CHARACTER-MIB::protocolTelnet,,,,,,
.1.3.6.1.2.1.19.4.3,CHARACTER-MIB::protocolRlogin,,,,,,
.1.3.6.1.2.1.19.4.4,CHARACTER-MIB::protocolLat,,,,,,
.1.3.6.1.2.1.19.4.5,CHARACTER-MIB::protocolX29,,,,,,
.1.3.6.1.2.1.19.4.6,CHARACTER-MIB::protocolVtp,,,,,,
.1.3.6.1.2.1.19.5,CHARACTER-MIB::charConformance,,,,,,
.1.3.6.1.2.1.19.5.1,CHARACTER-MIB::charGroups,,,,,,
.1.3.6.1.2.1.19.5.1.1,CHARACTER-MIB::charGroup,,,,,,A collection of objects providing information applicable to all Character interfaces.
.1.3.6.1.2.1.19.5.2,CHARACTER-MIB::charCompliances,,,,,,
.1.3.6.1.2.1.19.5.2.1,CHARACTER-MIB::charCompliance,,,,,,The compliance statement for SNMPv2 entities which have Character hardware interfaces.
.1.3.6.1.2.1.22,SNMP-REPEATER-MIB::snmpDot3RptrMgt,,,,,,
.1.3.6.1.2.1.22.0,SNMP-REPEATER-MIB::anonymous#4,,,,,,
.1.3.6.1.2.1.22.0.1,SNMP-REPEATER-MIB::rptrHealth,,,,,,********* THIS OBJECT IS DEPRECATED ********** In a system containing a single managed repeater, the rptrHealth notification conveys information related to the operational status of the repeater. It is sent either when the value of rptrOperStatus changes, or upon completion of a non-disruptive test. The rptrHealth notification must contain the rptrOperStatus object. The agent may optionally include the rptrHealthText object in the varBind list. See the rptrOperStatus and rptrHealthText objects for descriptions of the information that is sent. The agent must throttle the generation of consecutive rptrHealth traps so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.)
.1.3.6.1.2.1.22.0.2,SNMP-REPEATER-MIB::rptrGroupChange,,,,,,********* THIS OBJECT IS DEPRECATED ********** In a system containing a single managed repeater, this notification is sent when a change occurs in the group structure of the repeater. This occurs only when a group is logically or physically removed from or added to a repeater. The varBind list contains the identifier of the group that was removed or added. The agent must throttle the generation of consecutive rptrGroupChange traps for the same group so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.)
.1.3.6.1.2.1.22.0.3,SNMP-REPEATER-MIB::rptrResetEvent,,,,,,********* THIS OBJECT IS DEPRECATED ********** In a system containing a single managed repeater-unit, the rptrResetEvent notification conveys information related to the operational status of the repeater. This trap is sent on completion of a repeater reset action. A repeater reset action is defined as an a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std], when triggered by a management command (e.g., an SNMP Set on the rptrReset object). The agent must throttle the generation of consecutive rptrResetEvent traps so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.) The rptrResetEvent trap is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the rptrOperStatus object as an optional object with its coldStart and warmStart trap PDUs. The rptrOperStatus object must be included in the varbind list sent with this trap. The agent may optionally include the rptrHealthText object as well.
.1.3.6.1.2.1.22.0.4,SNMP-REPEATER-MIB::rptrInfoHealth,,,,,,In a system containing multiple managed repeaters, the rptrInfoHealth notification conveys information related to the operational status of a repeater. It is sent either when the value of rptrInfoOperStatus changes, or upon completion of a non-disruptive test. The agent must throttle the generation of consecutive rptrInfoHealth notifications for the same repeater so that there is at least a five-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a notification means sending to all configured recipients.)
.1.3.6.1.2.1.22.0.5,SNMP-REPEATER-MIB::rptrInfoResetEvent,,,,,,In a system containing multiple managed repeaters, the rptrInfoResetEvent notification conveys information related to the operational status of a repeater. This notification is sent on completion of a repeater reset action. A repeater reset action is defined as a transition to the START state of Fig 9-2 in section 9 of [IEEE 802.3 Std], when triggered by a management command (e.g., an SNMP Set on the rptrInfoReset object). The agent must throttle the generation of consecutive rptrInfoResetEvent notifications for a single repeater so that there is at least a five-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a notification means sending to all configured recipients.) The rptrInfoResetEvent is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. However, it is recommended that a repeater agent send the rptrInfoOperStatus object as an optional object with its coldStart and warmStart trap PDUs.
.1.3.6.1.2.1.22.1,SNMP-REPEATER-MIB::rptrBasicPackage,,,,,,
.1.3.6.1.2.1.22.1.1,SNMP-REPEATER-MIB::rptrRptrInfo,,,,,,
.1.3.6.1.2.1.22.1.1.1,SNMP-REPEATER-MIB::rptrGroupCapacity,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** The rptrGroupCapacity is the number of groups that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range from 1 to rptrGroupCapacity. Some groups may not be present in the repeater, in which case the actual number of groups present will be less than rptrGroupCapacity. The number of groups present will never be greater than rptrGroupCapacity. Note: In practice, this will generally be the number of field-replaceable units (i.e., modules, cards, or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to numbers marked on the physical enclosure.
.1.3.6.1.2.1.22.1.1.2,SNMP-REPEATER-MIB::rptrOperStatus,INTEGER,read-only,,deprecated,other(1):ok(2):rptrFailure(3):groupFailure(4):portFailure(5):generalFailure(6),********* THIS OBJECT IS DEPRECATED ********** The rptrOperStatus object indicates the operational state of the repeater. The rptrHealthText object may be consulted for more specific information about the state of the repeater's health. In the case of multiple kinds of failures (e.g., repeater failure and port failure), the value of this attribute shall reflect the highest priority failure in the following order, listed highest priority first: rptrFailure(3) groupFailure(4) portFailure(5) generalFailure(6).
.1.3.6.1.2.1.22.1.1.3,SNMP-REPEATER-MIB::rptrHealthText,OCTET,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** The health text object is a text string that provides information relevant to the operational state of the repeater. Agents may use this string to provide detailed information on current failures, including how they were detected, and/or instructions for problem resolution. The contents are agent-specific.
.1.3.6.1.2.1.22.1.1.4,SNMP-REPEATER-MIB::rptrReset,INTEGER,read-write,,deprecated,noReset(1):reset(2),********* THIS OBJECT IS DEPRECATED ********** Setting this object to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, and the START state of Fig 27-2 in section 27 of that standard for a 100Mb/s repeater. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. After receiving a request to set this variable to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. This action does not reset the management counters defined in this document nor does it affect the portAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including rptrOperStatus and rptrHealthText), and send a rptrHealth trap.
.1.3.6.1.2.1.22.1.1.5,SNMP-REPEATER-MIB::rptrNonDisruptTest,INTEGER,read-write,,deprecated,noSelfTest(1):selfTest(2),********* THIS OBJECT IS DEPRECATED ********** Setting this object to selfTest(2) causes the repeater to perform a agent-specific, non- disruptive self-test that has the following characteristics: a) The nature of the tests is not specified. b) The test does not change the state of the repeater or management information about the repeater. c) The test does not inject packets onto any segment. d) The test does not prevent the relay of any packets. e) The test does not interfere with management functions. After performing this test, the agent will update the repeater health information (including rptrOperStatus and rptrHealthText) and send a rptrHealth trap. Note that this definition allows returning an 'okay' result after doing a trivial test. Setting this object to noSelfTest(1) has no effect. The agent will always return the value noSelfTest(1) when this object is read.
.1.3.6.1.2.1.22.1.1.6,SNMP-REPEATER-MIB::rptrTotalPartitionedPorts,Gauge32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: rptrPortOperStatus does not have the value notPresent(3), rptrPortAdminStatus is enabled(1), and rptrPortAutoPartitionState is autoPartitioned(2).
.1.3.6.1.2.1.22.1.2,SNMP-REPEATER-MIB::rptrGroupInfo,,,,,,
.1.3.6.1.2.1.22.1.2.1,SNMP-REPEATER-MIB::rptrGroupTable,,not-accessible,,current,,Table of descriptive and status information about the groups of ports.
.1.3.6.1.2.1.22.1.2.1.1,SNMP-REPEATER-MIB::rptrGroupEntry,,not-accessible,rptrGroupIndex,current,,An entry in the table, containing information about a single group of ports.
.1.3.6.1.2.1.22.1.2.1.1.1,SNMP-REPEATER-MIB::rptrGroupIndex,Integer32,read-only,,current,,This object identifies the group within the system for which this entry contains information.
.1.3.6.1.2.1.22.1.2.1.1.2,SNMP-REPEATER-MIB::rptrGroupDescr,OCTET,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** A textual description of the group. This value should include the full name and version identification of the group's hardware type and indicate how the group is differentiated from other types of groups in the repeater. Plug-in Module, Rev A' or 'Barney Rubble 10BASE-T 4-port SIMM socket Version 2.1' are examples of valid group descriptions. It is mandatory that this only contain printable ASCII characters.
.1.3.6.1.2.1.22.1.2.1.1.3,SNMP-REPEATER-MIB::rptrGroupObjectID,OBJECT,read-only,,current,,The vendor's authoritative identification of the group. This value may be allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of group is being managed. For example, this object could take the value 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, and had assigned the identifier 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 6-Port FOIRL Plug-in Module.'
.1.3.6.1.2.1.22.1.2.1.1.4,SNMP-REPEATER-MIB::rptrGroupOperStatus,INTEGER,read-only,,current,other(1):operational(2):malfunctioning(3):notPresent(4):underTest(5):resetInProgress(6),An object that indicates the operational status of the group. A status of notPresent(4) indicates that the group is temporarily or permanently physically and/or logically not a part of the repeater. It is an implementation-specific matter as to whether the agent effectively removes notPresent entries from the table. A status of operational(2) indicates that the group is functioning, and a status of malfunctioning(3) indicates that the group is malfunctioning in some way.
.1.3.6.1.2.1.22.1.2.1.1.5,SNMP-REPEATER-MIB::rptrGroupLastOperStatusChange,TimeTicks,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** An object that contains the value of sysUpTime at the time when the last of the following occurred: 1) the agent cold- or warm-started; 2) the row for the group was created (such as when the group was added to the system); or 3) the value of rptrGroupOperStatus for the group changed. A value of zero indicates that the group's operational status has not changed since the agent last restarted.
.1.3.6.1.2.1.22.1.2.1.1.6,SNMP-REPEATER-MIB::rptrGroupPortCapacity,Integer32,read-only,,current,,The rptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-2147483647. Within each group, the ports are uniquely numbered in the range from 1 to rptrGroupPortCapacity. Some ports may not be present in the system, in which case the actual number of ports present will be less than the value of rptrGroupPortCapacity. The number of ports present in the group will never be greater than the value of rptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.
.1.3.6.1.2.1.22.1.3,SNMP-REPEATER-MIB::rptrPortInfo,,,,,,
.1.3.6.1.2.1.22.1.3.1,SNMP-REPEATER-MIB::rptrPortTable,,not-accessible,,current,,Table of descriptive and status information about the repeater ports in the system. The number of entries is independent of the number of repeaters in the managed system.
.1.3.6.1.2.1.22.1.3.1.1,SNMP-REPEATER-MIB::rptrPortEntry,,not-accessible,rptrPortGroupIndex:rptrPortIndex,current,,An entry in the table, containing information about a single port.
.1.3.6.1.2.1.22.1.3.1.1.1,SNMP-REPEATER-MIB::rptrPortGroupIndex,Integer32,read-only,,current,,This object identifies the group containing the port for which this entry contains information.
.1.3.6.1.2.1.22.1.3.1.1.2,SNMP-REPEATER-MIB::rptrPortIndex,Integer32,read-only,,current,,This object identifies the port within the group for which this entry contains information. This identifies the port independently from the repeater it may be attached to. The numbering scheme for ports is implementation specific; however, this value can never be greater than rptrGroupPortCapacity for the associated group.
.1.3.6.1.2.1.22.1.3.1.1.3,SNMP-REPEATER-MIB::rptrPortAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. (In effect, when a port is disabled, the value of rptrPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the rptrPortAutoPartitionState becomes notAutoPartitioned(1), regardless of its pre-disabling state.)
.1.3.6.1.2.1.22.1.3.1.1.4,SNMP-REPEATER-MIB::rptrPortAutoPartitionState,INTEGER,read-only,,current,notAutoPartitioned(1):autoPartitioned(2),The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Sections 9 and 27 of [IEEE 802.3 Std]. They are not differentiated here.
.1.3.6.1.2.1.22.1.3.1.1.5,SNMP-REPEATER-MIB::rptrPortOperStatus,INTEGER,read-only,,current,operational(1):notOperational(2):notPresent(3),This object indicates the port's operational status. The notPresent(3) status indicates the port is physically removed (note this may or may not be possible depending on the type of port.) The operational(1) status indicates that the port is enabled (see rptrPortAdminStatus) and working, even though it might be auto-partitioned (see rptrPortAutoPartitionState). If this object has the value operational(1) and rptrPortAdminStatus is set to disabled(2), it is expected that this object's value will soon change to notOperational(2).
.1.3.6.1.2.1.22.1.3.1.1.6,SNMP-REPEATER-MIB::rptrPortRptrId,Integer32,read-only,,current,,This object identifies the repeater to which this port belongs. The repeater identified by a particular value of this object is the same as that identified by the same value of rptrInfoId. A value of zero indicates that this port currently is not a member of any repeater.
.1.3.6.1.2.1.22.1.4,SNMP-REPEATER-MIB::rptrAllRptrInfo,,,,,,
.1.3.6.1.2.1.22.1.4.1,SNMP-REPEATER-MIB::rptrInfoTable,,not-accessible,,current,,A table of information about each non-trivial repeater. The number of entries depends on the physical configuration of the managed system.
.1.3.6.1.2.1.22.1.4.1.1,SNMP-REPEATER-MIB::rptrInfoEntry,,not-accessible,rptrInfoId,current,,An entry in the table, containing information about a single non-trivial repeater.
.1.3.6.1.2.1.22.1.4.1.1.1,SNMP-REPEATER-MIB::rptrInfoId,Integer32,read-only,,current,,This object identifies the repeater for which this entry contains information.
.1.3.6.1.2.1.22.1.4.1.1.2,SNMP-REPEATER-MIB::rptrInfoRptrType,INTEGER,read-only,,current,other(1):tenMb(2):onehundredMbClassI(3):onehundredMbClassII(4),The rptrInfoRptrType returns a value that identifies the CSMA/CD repeater type.
.1.3.6.1.2.1.22.1.4.1.1.3,SNMP-REPEATER-MIB::rptrInfoOperStatus,INTEGER,read-only,,current,other(1):ok(2):failure(3),The rptrInfoOperStatus object indicates the operational state of the repeater.
.1.3.6.1.2.1.22.1.4.1.1.4,SNMP-REPEATER-MIB::rptrInfoReset,INTEGER,read-write,,current,noReset(1):reset(2),Setting this object to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std] for a 10Mb/s repeater, and to the START state of Fig 27-2 in section 27 of that standard for a 100Mb/s repeater. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. After receiving a request to set this variable to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. This action does not reset the management counters defined in this document nor does it affect the portAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including rptrInfoOperStatus), and send a rptrInfoResetEvent notification.
.1.3.6.1.2.1.22.1.4.1.1.5,SNMP-REPEATER-MIB::rptrInfoPartitionedPorts,Gauge32,read-only,,current,,This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: rptrPortOperStatus does not have the value notPresent(3), rptrPortAdminStatus is enabled(1), and rptrPortAutoPartitionState is autoPartitioned(2).
.1.3.6.1.2.1.22.1.4.1.1.6,SNMP-REPEATER-MIB::rptrInfoLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when any of the following conditions occurred: 1) agent cold- or warm-started; 2) this instance of repeater was created (such as when a device or module was added to the system); 3) a change in the value of rptrInfoOperStatus; 4) ports were added or removed as members of the repeater; or 5) any of the counters associated with this repeater had a discontinuity.
.1.3.6.1.2.1.22.2,SNMP-REPEATER-MIB::rptrMonitorPackage,,,,,,
.1.3.6.1.2.1.22.2.1,SNMP-REPEATER-MIB::rptrMonitorRptrInfo,,,,,,
.1.3.6.1.2.1.22.2.1.1,SNMP-REPEATER-MIB::rptrMonitorTransmitCollisions,Counter32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** For a clause 9 (10Mb/s) repeater, this counter is incremented every time the repeater state machine enters the TRANSMIT COLLISION state from any state other than ONE PORT LEFT (Ref: Fig 9-2 [IEEE 802.3 Std]). For a clause 27 repeater, this counter is incremented every time the repeater core state diagram enters the Jam state as a result of Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). The approximate minimum time for rollover of this counter is 16 hours in a 10Mb/s repeater and 1.6 hours in a 100Mb/s repeater.
.1.3.6.1.2.1.22.2.2,SNMP-REPEATER-MIB::rptrMonitorGroupInfo,,,,,,
.1.3.6.1.2.1.22.2.2.1,SNMP-REPEATER-MIB::rptrMonitorGroupTable,,not-accessible,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** Table of performance and error statistics for the groups within the repeater. The number of entries is the same as that in the rptrGroupTable.
.1.3.6.1.2.1.22.2.2.1.1,SNMP-REPEATER-MIB::rptrMonitorGroupEntry,,not-accessible,rptrMonitorGroupIndex,deprecated,,********* THIS OBJECT IS DEPRECATED ********** An entry in the table, containing total performance and error statistics for a single group. Regular retrieval of the information in this table provides a means of tracking the performance and health of the networked devices attached to this group's ports. The counters in this table are redundant in the sense that they are the summations of information already available through other objects. However, these sums provide a considerable optimization of network management traffic over the otherwise necessary retrieval of the individual counters included in each sum. Note: Group-level counters are deprecated in this MIB. It is recommended that management applications instead use the repeater-level counters contained in the rptrMonTable.
.1.3.6.1.2.1.22.2.2.1.1.1,SNMP-REPEATER-MIB::rptrMonitorGroupIndex,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object identifies the group within the repeater for which this entry contains information.
.1.3.6.1.2.1.22.2.2.1.1.2,SNMP-REPEATER-MIB::rptrMonitorGroupTotalFrames,Counter32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** The total number of frames of valid frame length that have been received on the ports in this group and for which the FCSError and CollisionEvent signals were not asserted. This counter is the summation of the values of the rptrMonitorPortReadableFrames counters for all of the ports in the group. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.2.1.1.3,SNMP-REPEATER-MIB::rptrMonitorGroupTotalOctets,Counter32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** The total number of octets contained in the valid frames that have been received on the ports in this group. This counter is the summation of the values of the rptrMonitorPortReadableOctets counters for all of the ports in the group. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter is 58 minutes in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.2.1.1.4,SNMP-REPEATER-MIB::rptrMonitorGroupTotalErrors,Counter32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** The total number of errors which have occurred on all of the ports in this group. This counter is the summation of the values of the rptrMonitorPortTotalErrors counters for all of the ports in the group.
.1.3.6.1.2.1.22.2.3,SNMP-REPEATER-MIB::rptrMonitorPortInfo,,,,,,
.1.3.6.1.2.1.22.2.3.1,SNMP-REPEATER-MIB::rptrMonitorPortTable,,not-accessible,,current,,Table of performance and error statistics for the ports. The number of entries is the same as that in the rptrPortTable. The columnar object rptrMonitorPortLastChange is used to indicate possible discontinuities of counter type columnar objects in the table.
.1.3.6.1.2.1.22.2.3.1.1,SNMP-REPEATER-MIB::rptrMonitorPortEntry,,not-accessible,rptrMonitorPortGroupIndex:rptrMonitorPortIndex,current,,An entry in the table, containing performance and error statistics for a single port.
.1.3.6.1.2.1.22.2.3.1.1.1,SNMP-REPEATER-MIB::rptrMonitorPortGroupIndex,Integer32,read-only,,current,,This object identifies the group containing the port for which this entry contains information.
.1.3.6.1.2.1.22.2.3.1.1.2,SNMP-REPEATER-MIB::rptrMonitorPortIndex,Integer32,read-only,,current,,This object identifies the port within the group for which this entry contains information.
.1.3.6.1.2.1.22.2.3.1.1.3,SNMP-REPEATER-MIB::rptrMonitorPortReadableFrames,Counter32,read-only,,current,,This object is the number of frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1) and for which the FCSError and CollisionEvent signals are not asserted. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours at 10Mb/s.
.1.3.6.1.2.1.22.2.3.1.1.4,SNMP-REPEATER-MIB::rptrMonitorPortReadableOctets,Counter32,read-only,,current,,This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame (i.e., including FCS octets but excluding framing bits and dribble bits). A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter in a 10Mb/s repeater is 58 minutes. For ports receiving traffic at a maximum rate in a 100Mb/s repeater, this counter can roll over in less than 6 minutes. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information a management station is advised to also poll the rptrMonitorPortUpper32Octets object, or to use the 64-bit counter defined by rptrMonitorPortHCReadableOctets instead of the two 32-bit counters.
.1.3.6.1.2.1.22.2.3.1.1.5,SNMP-REPEATER-MIB::rptrMonitorPortFCSErrors,Counter32,read-only,,current,,This counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError and CollisionEvent signals deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 80 hours at 10Mb/s.
.1.3.6.1.2.1.22.2.3.1.1.6,SNMP-REPEATER-MIB::rptrMonitorPortAlignmentErrors,Counter32,read-only,,current,,This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and CollisionEvent signal deasserted and whose OctetCount is greater than or equal to minFrameSize and less than or equal to maxFrameSize (Ref: IEEE 802.3 Std, 4.4.2.1). If rptrMonitorPortAlignmentErrors is incremented then the rptrMonitorPortFCSErrors Counter shall not be incremented for the same frame. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 80 hours at 10Mb/s.
.1.3.6.1.2.1.22.2.3.1.1.7,SNMP-REPEATER-MIB::rptrMonitorPortFrameTooLongs,Counter32,read-only,,current,,This counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std). If rptrMonitorPortFrameTooLongs is incremented then neither the rptrMonitorPortAlignmentErrors nor the rptrMonitorPortFCSErrors counter shall be incremented for the frame. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 61 days in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.3.1.1.8,SNMP-REPEATER-MIB::rptrMonitorPortShortEvents,Counter32,read-only,,current,,This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Notes: ShortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network. Implementors may wish to consider selecting the ShortEventMaxTime towards the lower end of the allowed tolerance range to accommodate bit losses suffered through physical channel devices not budgeted for within this standard. The significance of this attribute is different in 10 and 100 Mb/s collision domains. Clause 9 repeaters perform fragment extension of short events which would be counted as runts on the interconnect ports of other repeaters. Clause 27 repeaters do not perform fragment extension. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 16 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.3.1.1.9,SNMP-REPEATER-MIB::rptrMonitorPortRunts,Counter32,read-only,,current,,This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than ValidPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times. An event whose length is greater than 74 bit times but less than 82 bit times shall increment either the shortEvents counter or the runts counter but not both. A CarrierEvent greater than or equal to 552 bit times but less than 565 bit times may or may not be counted as a runt. ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine. Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of collision fragments may exceed ValidPacketMinTime. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 16 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.3.1.1.10,SNMP-REPEATER-MIB::rptrMonitorPortCollisions,Counter32,read-only,,current,,For a clause 9 repeater, this counter is incremented by one for any CarrierEvent signal on any port for which the CollisionEvent signal on this port is asserted. For a clause 27 repeater port the counter increments on entering the Collision Count Increment state of the partition state diagram (fig 27-8 of [IEEE 802.3 Std]). A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 16 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.3.1.1.11,SNMP-REPEATER-MIB::rptrMonitorPortLateEvents,Counter32,read-only,,current,,For a clause 9 repeater port, this counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variable transitions to the value SQE (Ref: 9.6.6.2, IEEE 802.3 Std) while the ActivityDuration is greater than the LateEventThreshold. For a clause 27 repeater port, this counter is incremented by one on entering the Collision Count Increment state of the partition state diagram (fig 27-8) while the ActivityDuration is greater than the LateEvent- Threshold. Such a CarrierEvent is counted twice, as both a collision and as a lateEvent. The LateEventThreshold is greater than 480 bit times and less than 565 bit times. LateEventThreshold has tolerances included to permit an implementation to build a single threshold to serve as both the LateEventThreshold and ValidPacketMinTime threshold. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 81 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.3.1.1.12,SNMP-REPEATER-MIB::rptrMonitorPortVeryLongEvents,Counter32,read-only,,current,,For a clause 9 repeater port, this counter is incremented by one for each CarrierEvent whose ActivityDuration is greater than the MAU Jabber Lockup Protection timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std). For a clause 27 repeater port, this counter is incremented by one on entry to the Rx Jabber state of the receiver timer state diagram (fig 27-7). Other counters may be incremented as appropriate. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.3.1.1.13,SNMP-REPEATER-MIB::rptrMonitorPortDataRateMismatches,Counter32,read-only,,current,,This counter is incremented by one for each frame received by this port that meets all of the conditions required by only one of the following two measurement methods: Measurement method A: 1) The CollisionEvent signal is not asserted (10Mb/s operation) or the Collision Count Increment state of the partition state diagram (fig 27-8 of [IEEE 802.3 Std]) has not been entered (100Mb/s operation). 2) The ActivityDuration is greater than ValidPacketMinTime. 3) The frequency (data rate) is detectably mismatched from the local transmit frequency. Measurement method B: 1) The CollisionEvent signal is not asserted (10Mb/s operation) or the Collision Count Increment state of the partition state diagram (fig 27-8 of [IEEE 802.3 Std]) has not been entered (100Mb/s operation). 2) The OctetCount is greater than 63. 3) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing. When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.3.1.1.14,SNMP-REPEATER-MIB::rptrMonitorPortAutoPartitions,Counter32,read-only,,current,,This counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause a clause 9 repeater port to partition are specified in the partition state diagram in clause 9 of [IEEE 802.3 Std]. They are not differentiated here. A clause 27 repeater port partitions on entry to the Partition Wait state of the partition state diagram (fig 27-8 in [IEEE 802.3 Std]). A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.3.1.1.15,SNMP-REPEATER-MIB::rptrMonitorPortTotalErrors,Counter32,read-only,,current,,The total number of errors which have occurred on this port. This counter is the summation of the values of other error counters (for the same port), namely: rptrMonitorPortFCSErrors, rptrMonitorPortAlignmentErrors, rptrMonitorPortFrameTooLongs, rptrMonitorPortShortEvents, rptrMonitorPortLateEvents, rptrMonitorPortVeryLongEvents, rptrMonitorPortDataRateMismatches, and rptrMonitorPortSymbolErrors. This counter is redundant in the sense that it is the summation of information already available through other objects. However, it is included specifically because the regular retrieval of this object as a means of tracking the health of a port provides a considerable optimization of network management traffic over the otherwise necessary retrieval of the summed counters. Note that rptrMonitorPortRunts is not included in this total; this is because runts usually indicate collision fragments, a normal network event. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.3.1.1.16,SNMP-REPEATER-MIB::rptrMonitorPortLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when the last of the following occurred: 1) the agent cold- or warm-started; 2) the row for the port was created (such as when a device or module was added to the system); or 3) any condition that would cause one of the counters for the row to experience a discontinuity.
.1.3.6.1.2.1.22.2.3.2,SNMP-REPEATER-MIB::rptrMonitor100PortTable,,not-accessible,,current,,Table of additional performance and error statistics for 100Mb/s ports, above and beyond those parameters that apply to both 10 and 100Mbps ports. Entries exist only for ports attached to 100Mbps repeaters. The columnar object rptrMonitorPortLastChange is used to indicate possible discontinuities of counter type columnar objects in this table.
.1.3.6.1.2.1.22.2.3.2.1,SNMP-REPEATER-MIB::rptrMonitor100PortEntry,,not-accessible,rptrMonitorPortGroupIndex:rptrMonitorPortIndex,current,,An entry in the table, containing performance and error statistics for a single 100Mb/s port.
.1.3.6.1.2.1.22.2.3.2.1.1,SNMP-REPEATER-MIB::rptrMonitorPortIsolates,Counter32,read-only,,current,,This counter is incremented by one each time that the repeater port automatically isolates as a consequence of false carrier events. The conditions which cause a port to automatically isolate are defined by the transition from the False Carrier state to the Link Unstable state of the carrier integrity state diagram (figure 27-9) [IEEE 802.3 Standard]. Note: Isolates do not affect the value of the PortOperStatus object. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.3.2.1.2,SNMP-REPEATER-MIB::rptrMonitorPortSymbolErrors,Counter32,read-only,,current,,This counter is incremented by one each time when valid length packet was received at the port and there was at least one occurrence of an invalid data symbol. This can increment only once per valid carrier event. A collision presence at any port of the repeater containing port N, will not cause this attribute to increment. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 7.4 hours at 100Mb/s.
.1.3.6.1.2.1.22.2.3.2.1.3,SNMP-REPEATER-MIB::rptrMonitorPortUpper32Octets,Counter32,read-only,,current,,This object is the number of octets contained in valid frames that have been received on this port, modulo 2**32. That is, it contains the upper 32 bits of a 64-bit octets counter, of which the lower 32 bits are contained in the rptrMonitorPortReadableOctets object. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMP V1) and are used to manage a repeater type of 100Mb/s. Conformance clauses for this MIB are defined such that implementation of this object is not required in a system which does not support 100Mb/s. However, systems with mixed 10 and 100Mb/s ports may implement this object across all ports, including 10Mb/s. If this object is implemented, it must be according to the definition in the first paragraph of this description; that is, the value of this object MUST be a valid count. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.3.2.1.4,SNMP-REPEATER-MIB::rptrMonitorPortHCReadableOctets,Counter64,read-only,,current,,This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame (i.e., including FCS octets but excluding framing bits and dribble bits). This statistic provides an indicator of the total data transferred. This counter is a 64-bit version of rptrMonitor- PortReadableOctets. It should be used by network management protocols which suppport 64-bit counters (e.g. SNMPv2). Conformance clauses for this MIB are defined such that implementation of this object is not required in a system which does not support 100Mb/s. However, systems with mixed 10 and 100Mb/s ports may implement this object across all ports, including 10Mb/s. If this object is implemented, it must be according to the definition in the first paragraph of this description; that is, the value of this object MUST be a valid count. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
.1.3.6.1.2.1.22.2.4,SNMP-REPEATER-MIB::rptrMonitorAllRptrInfo,,,,,,
.1.3.6.1.2.1.22.2.4.1,SNMP-REPEATER-MIB::rptrMonTable,,not-accessible,,current,,A table of information about each non-trivial repeater. The number of entries in this table is the same as the number of entries in the rptrInfoTable. The columnar object rptrInfoLastChange is used to indicate possible discontinuities of counter type columnar objects in this table.
.1.3.6.1.2.1.22.2.4.1.1,SNMP-REPEATER-MIB::rptrMonEntry,,not-accessible,rptrInfoId,current,,An entry in the table, containing information about a single non-trivial repeater.
.1.3.6.1.2.1.22.2.4.1.1.1,SNMP-REPEATER-MIB::rptrMonTxCollisions,Counter32,read-only,,current,,For a clause 9 (10Mb/s) repeater, this counter is incremented every time the repeater state machine enters the TRANSMIT COLLISION state from any state other than ONE PORT LEFT (Ref: Fig 9-2 [IEEE 802.3 Std]). For a clause 27 repeater, this counter is incremented every time the repeater core state diagram enters the Jam state as a result of Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]). The approximate minimum time for rollover of this counter is 16 hours in a 10Mb/s repeater and 1.6 hours in a 100Mb/s repeater.
.1.3.6.1.2.1.22.2.4.1.1.3,SNMP-REPEATER-MIB::rptrMonTotalFrames,Counter32,read-only,,current,,The number of frames of valid frame length that have been received on the ports in this repeater and for which the FCSError and CollisionEvent signals were not asserted. If an implementation can not obtain a count of frames as seen by the repeater itself, this counter may be implemented as the summation of the values of the rptrMonitorPortReadableFrames counters for all of the ports in the repeater. This statistic provides one of the parameters necessary for obtaining the packet error rate. The approximate minimum time for rollover of this counter is 80 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.2.4.1.1.4,SNMP-REPEATER-MIB::rptrMonTotalErrors,Counter32,read-only,,current,,The total number of errors which have occurred on all of the ports in this repeater. The errors included in this count are the same as those listed for the rptrMonitorPortTotalErrors counter. If an implementation can not obtain a count of these errors as seen by the repeater itself, this counter may be implemented as the summation of the values of the rptrMonitorPortTotalErrors counters for all of the ports in the repeater.
.1.3.6.1.2.1.22.2.4.1.1.5,SNMP-REPEATER-MIB::rptrMonTotalOctets,Counter32,read-only,,current,,The total number of octets contained in the valid frames that have been received on the ports in this group. If an implementation can not obtain a count of octets as seen by the repeater itself, this counter may be the summation of the values of the rptrMonitorPortReadableOctets counters for all of the ports in the group. This statistic provides an indicator of the total data transferred. The approximate minimum time for rollover of this counter in a 10Mb/s repeater is 58 minutes divided by the number of ports in the repeater. For 100Mb/s repeaters processing traffic at a maximum rate, this counter can roll over in less than 6 minutes divided by the number of ports in the repeater. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information a management station is advised to also poll the rptrMonUpper32TotalOctets object, or to use the 64-bit counter defined by rptrMonHCTotalOctets instead of the two 32-bit counters.
.1.3.6.1.2.1.22.2.4.2,SNMP-REPEATER-MIB::rptrMon100Table,,not-accessible,,current,,A table of additional information about each 100Mb/s repeater, augmenting the entries in the rptrMonTable. Entries exist in this table only for 100Mb/s repeaters. The columnar object rptrInfoLastChange is used to indicate possible discontinuities of counter type columnar objects in this table.
.1.3.6.1.2.1.22.2.4.2.1,SNMP-REPEATER-MIB::rptrMon100Entry,,not-accessible,rptrInfoId,current,,An entry in the table, containing information about a single 100Mbps repeater.
.1.3.6.1.2.1.22.2.4.2.1.1,SNMP-REPEATER-MIB::rptrMonUpper32TotalOctets,Counter32,read-only,,current,,The total number of octets contained in the valid frames that have been received on the ports in this repeater, modulo 2**32. That is, it contains the upper 32 bits of a 64-bit counter, of which the lower 32 bits are contained in the rptrMonTotalOctets object. If an implementation can not obtain a count of octets as seen by the repeater itself, the 64-bit value may be the summation of the values of the rptrMonitorPortReadableOctets counters combined with the corresponding rptrMonitorPortUpper32Octets counters for all of the ports in the repeater. This statistic provides an indicator of the total data transferred within the repeater. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMP V1) and are used to manage a repeater type of 100Mb/s. Conformance clauses for this MIB are defined such that implementation of this object is not required in a system which does not support 100Mb/s. However, systems with mixed 10 and 100Mb/s ports may implement this object across all ports, including 10Mb/s. If this object is implemented, it must be according to the definition in the first paragraph of this description; that is, the value of this object MUST be a valid count.
.1.3.6.1.2.1.22.2.4.2.1.2,SNMP-REPEATER-MIB::rptrMonHCTotalOctets,Counter64,read-only,,current,,The total number of octets contained in the valid frames that have been received on the ports in this group. If a implementation can not obtain a count of octets as seen by the repeater itself, this counter may be the summation of the values of the rptrMonitorPortReadableOctets counters for all of the ports in the group. This statistic provides an indicator of the total data transferred. This counter is a 64-bit (high-capacity) version of rptrMonUpper32TotalOctets and rptrMonTotalOctets. It should be used by network management protocols which support 64-bit counters (e.g. SNMPv2). Conformance clauses for this MIB are defined such that implementation of this object is not required in a system which does not support 100Mb/s. However, systems with mixed 10 and 100Mb/s ports may implement this object across all ports, including 10Mb/s. If this object is implemented, it must be according to the definition in the first paragraph of this description; that is, the value of this object MUST be a valid count.
.1.3.6.1.2.1.22.3,SNMP-REPEATER-MIB::rptrAddrTrackPackage,,,,,,
.1.3.6.1.2.1.22.3.1,SNMP-REPEATER-MIB::rptrAddrTrackRptrInfo,,,,,,
.1.3.6.1.2.1.22.3.1.1,SNMP-REPEATER-MIB::rptrAddrSearchTable,,not-accessible,,current,,This table contains one entry per repeater in the system. It defines objects which allow a network management application to instruct an agent to watch for a given MAC address and report which port it was seen on. Only one address search can be in progress on each repeater at any one time. Before starting an address search, a management application should obtain 'ownership' of the entry in rptrAddrSearchTable for the repeater that is to perform the search. This is accomplished with the rptrAddrSearchLock and rptrAddrSearchStatus as follows: try_again: get(rptrAddrSearchLock, rptrAddrSearchStatus) while (rptrAddrSearchStatus != notInUse) { /* Loop waiting for objects to be available*/ short delay get(rptrAddrSearchLock, rptrAddrSearchStatus) } /* Try to claim map objects */ lock_value = rptrAddrSearchLock if ( set(rptrAddrSearchLock = lock_value, rptrAddrSearchStatus = inUse, rptrAddrSearchOwner = 'my-IP-address) == FAILURE) /* Another manager got the lock */ goto try_again /* I have the lock */ set (rptrAddrSearchAddress = <search target>) wait for rptrAddrSearchState to change from none if (rptrAddrSearchState == single) get (rptrAddrSearchGroup, rptrAddrSearchPort) /* release the lock, making sure not to overwrite anyone else's lock */ set (rptrAddrSearchLock = lock_value+1, rptrAddrSearchStatus = notInUse, rptrAddrSearchOwner = '') A management station first retrieves the values of the appropriate instances of the rptrAddrSearchLock and rptrAddrSearchStatus objects, periodically repeating the retrieval if necessary, until the value of rptrAddrSearchStatus is 'notInUse'. The management station then tries to set the same instance of the rptrAddrSearchLock object to the value it just retrieved, the same instance of the rptrAddrSearchStatus object to 'inUse', and the corresponding instance of rptrAddrSearchOwner to a value indicating itself. If the set operation succeeds, then the management station has obtained ownership of the rptrAddrSearchEntry, and the value of rptrAddrSearchLock is incremented by the agent (as per the semantics of TestAndIncr). Failure of the set operation indicates that some other manager has obtained ownership of the rptrAddrSearchEntry. Once ownership is obtained, the management station can proceed with the search operation. Note that the agent will reset rptrAddrSearchStatus to 'notInUse' if it has been in the 'inUse' state for an abnormally long period of time, to prevent a misbehaving manager from permanently locking the entry. It is suggested that this timeout period be between one and five minutes. When the management station has completed its search operation, it should free the entry by setting the instance of the rptrAddrSearchLock object to the previous value + 1, the instance of the rptrAddrSearchStatus to 'notInUse', and the instance of rptrAddrSearchOwner to a zero length string. This is done to prevent overwriting another station's lock.
.1.3.6.1.2.1.22.3.1.1.1,SNMP-REPEATER-MIB::rptrAddrSearchEntry,,not-accessible,rptrInfoId,current,,An entry containing objects for invoking an address search on a repeater.
.1.3.6.1.2.1.22.3.1.1.1.1,SNMP-REPEATER-MIB::rptrAddrSearchLock,INTEGER,read-write,,current,,This object is used by a management station as an advisory lock for this rptrAddrSearchEntry.
.1.3.6.1.2.1.22.3.1.1.1.2,SNMP-REPEATER-MIB::rptrAddrSearchStatus,INTEGER,read-write,,current,notInUse(1):inUse(2),This object is used to indicate that some management station is currently using this rptrAddrSearchEntry. Cooperating managers should set this object to 'notInUse' when they are finished using this entry. The agent will automatically set the value of this object to 'notInUse' if it has been set to 'inUse' for an unusually long period of time.
.1.3.6.1.2.1.22.3.1.1.1.3,SNMP-REPEATER-MIB::rptrAddrSearchAddress,OCTET,read-write,,current,,This object is used to search for a specified MAC address. When this object is set, an address search begins. This automatically sets the corresponding instance of the rptrAddrSearchState object to 'none' and the corresponding instances of the rptrAddrSearchGroup and rptrAddrSearchPort objects to 0. When a valid frame is received by this repeater with a source MAC address which matches the current value of rptrAddrSearchAddress, the agent will update the corresponding instances of rptrAddrSearchState, rptrAddrSearchGroup and rptrAddrSearchPort to reflect the current status of the search, and the group and port on which the frame was seen.
.1.3.6.1.2.1.22.3.1.1.1.4,SNMP-REPEATER-MIB::rptrAddrSearchState,INTEGER,read-only,,current,none(1):single(2):multiple(3),The current state of the MAC address search on this repeater. This object is initialized to 'none' when the corresponding instance of rptrAddrSearchAddress is set. If the agent detects the address on exactly one port, it will set this object to 'single', and set the corresponding instances of rptrAddrSearchGroup and rptrAddrSearchPort to reflect the group and port on which the address was heard. If the agent detects the address on more than one port, it will set this object to 'multiple'.
.1.3.6.1.2.1.22.3.1.1.1.5,SNMP-REPEATER-MIB::rptrAddrSearchGroup,Integer32,read-only,,current,,The group from which an error-free frame whose source address is equal to the corresponding instance of rptrAddrSearchAddress has been received. The value of this object is undefined when the corresponding instance of rptrAddrSearchState is equal to 'none' or 'multiple'.
.1.3.6.1.2.1.22.3.1.1.1.6,SNMP-REPEATER-MIB::rptrAddrSearchPort,Integer32,read-only,,current,,The port rom which an error-free frame whose source address is equal to the corresponding instance of rptrAddrSearchAddress has been received. The value of this object is undefined when the corresponding instance of rptrAddrSearchState is equal to 'none' or 'multiple'.
.1.3.6.1.2.1.22.3.1.1.1.7,SNMP-REPEATER-MIB::rptrAddrSearchOwner,OCTET,read-write,,current,,The entity which currently has 'ownership' of this rptrAddrSearchEntry.
.1.3.6.1.2.1.22.3.2,SNMP-REPEATER-MIB::rptrAddrTrackGroupInfo,,,,,,
.1.3.6.1.2.1.22.3.3,SNMP-REPEATER-MIB::rptrAddrTrackPortInfo,,,,,,
.1.3.6.1.2.1.22.3.3.1,SNMP-REPEATER-MIB::rptrAddrTrackTable,,not-accessible,,current,,Table of address mapping information about the ports.
.1.3.6.1.2.1.22.3.3.1.1,SNMP-REPEATER-MIB::rptrAddrTrackEntry,,not-accessible,rptrAddrTrackGroupIndex:rptrAddrTrackPortIndex,current,,An entry in the table, containing address mapping information about a single port.
.1.3.6.1.2.1.22.3.3.1.1.1,SNMP-REPEATER-MIB::rptrAddrTrackGroupIndex,INTEGER,read-only,,current,,This object identifies the group containing the port for which this entry contains information.
.1.3.6.1.2.1.22.3.3.1.1.2,SNMP-REPEATER-MIB::rptrAddrTrackPortIndex,INTEGER,read-only,,current,,This object identifies the port within the group for which this entry contains information.
.1.3.6.1.2.1.22.3.3.1.1.3,SNMP-REPEATER-MIB::rptrAddrTrackLastSourceAddress,OCTET,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object is the SourceAddress of the last readable frame (i.e., counted by rptrMonitorPortReadableFrames) received by this port. This object has been deprecated because its value is undefined when no frames have been observed on this port. The replacement object is rptrAddrTrackNewLastSrcAddress.
.1.3.6.1.2.1.22.3.3.1.1.4,SNMP-REPEATER-MIB::rptrAddrTrackSourceAddrChanges,Counter32,read-only,,current,,This counter is incremented by one for each time that the rptrAddrTrackLastSourceAddress attribute for this port has changed. This may indicate whether a link is connected to a single DTE or another multi-user segment. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes. The approximate minimum time for rollover of this counter is 81 hours in a 10Mb/s repeater.
.1.3.6.1.2.1.22.3.3.1.1.5,SNMP-REPEATER-MIB::rptrAddrTrackNewLastSrcAddress,OCTET,read-only,,current,,This object is the SourceAddress of the last readable frame (i.e., counted by rptrMonitorPortReadableFrames) received by this port. If no frames have been received by this port since the agent began monitoring the port activity, the agent shall return a string of length zero.
.1.3.6.1.2.1.22.3.3.1.1.6,SNMP-REPEATER-MIB::rptrAddrTrackCapacity,Integer32,read-only,,current,,The maximum number of addresses that can be detected on this port. This value indicates to the maximum number of entries in the rptrExtAddrTrackTable relative to this port. If this object has the value of 1, the agent implements only the LastSourceAddress mechanism described by RFC 1368 or RFC 1516.
.1.3.6.1.2.1.22.3.3.2,SNMP-REPEATER-MIB::rptrExtAddrTrackTable,,not-accessible,,current,,A table to extend the address tracking table (i.e., rptrAddrTrackTable) with a list of source MAC addresses that were recently received on each port. The number of ports is the same as the number of entries in table rptrPortTable. The number of entries in this table depends on the agent/repeater implementation and the number of different addresses received on each port. The first entry for each port contains the same MAC address that is given by the rptrAddrTrackNewLastSrcAddress for that port. Entries in this table for a particular port are retained when that port is switched from one repeater to another. The ordering of MAC addresses listed for a particular port is implementation dependent.
.1.3.6.1.2.1.22.3.3.2.1,SNMP-REPEATER-MIB::rptrExtAddrTrackEntry,,not-accessible,rptrAddrTrackGroupIndex:rptrAddrTrackPortIndex:rptrExtAddrTrackMacIndex,current,,A row in the table of extended address tracking information for ports. Entries can not be directly created or deleted via SNMP operations.
.1.3.6.1.2.1.22.3.3.2.1.1,SNMP-REPEATER-MIB::rptrExtAddrTrackMacIndex,Integer32,read-only,,current,,The index of a source MAC address seen on the port. The ordering of MAC addresses listed for a particular port is implementation dependent. There is no implied relationship between a particular index and a particular MAC address. The index for a particular MAC address may change without notice.
.1.3.6.1.2.1.22.3.3.2.1.2,SNMP-REPEATER-MIB::rptrExtAddrTrackSourceAddress,OCTET,read-only,,current,,The source MAC address from a readable frame (i.e., counted by rptrMonitorPortReadableFrames) recently received by the port.
.1.3.6.1.2.1.22.4,SNMP-REPEATER-MIB::rptrTopNPackage,,,,,,
.1.3.6.1.2.1.22.4.1,SNMP-REPEATER-MIB::rptrTopNRptrInfo,,,,,,
.1.3.6.1.2.1.22.4.2,SNMP-REPEATER-MIB::rptrTopNGroupInfo,,,,,,
.1.3.6.1.2.1.22.4.3,SNMP-REPEATER-MIB::rptrTopNPortInfo,,,,,,
.1.3.6.1.2.1.22.4.3.1,SNMP-REPEATER-MIB::rptrTopNPortControlTable,,not-accessible,,current,,A table of control records for reports on the top `N' ports for the rate of a selected counter. The number of entries depends on the configuration of the agent. The maximum number of entries is implementation dependent.
.1.3.6.1.2.1.22.4.3.1.1,SNMP-REPEATER-MIB::rptrTopNPortControlEntry,,not-accessible,rptrTopNPortControlIndex,current,,A set of parameters that control the creation of a report of the top N ports according to several metrics.
.1.3.6.1.2.1.22.4.3.1.1.1,SNMP-REPEATER-MIB::rptrTopNPortControlIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the rptrTopNPortControl table. Each such entry defines one top N report prepared for a repeater or system.
.1.3.6.1.2.1.22.4.3.1.1.2,SNMP-REPEATER-MIB::rptrTopNPortRepeaterId,Integer32,read-create,,current,,Identifies the repeater for which a top N report will be prepared (see rptrInfoId). If the value of this object is positive, only ports assigned to this repeater will be used to form the list in which to order the Top N table. If this value is zero, all ports will be eligible for inclusion on the list. The value of this object may not be modified if the associated rptrTopNPortRowStatus object is equal to active(1). If, for a particular row in this table, the repeater specified by the value of this object goes away (is removed from the rptrInfoTable) while the associated rptrTopNPortRowStatus object is equal to active(1), the row in this table is preserved by the agent but the value of rptrTopNPortRowStatus is changed to notInService(2), and the agent may time out the row if appropriate. If the specified repeater comes back (reappears in the rptrInfoTable) before the row has been timed out, the management station must set the value of the rptrTopNPortRowStatus object back to active(1) if desired (the agent doesn't do this automatically).
.1.3.6.1.2.1.22.4.3.1.1.3,SNMP-REPEATER-MIB::rptrTopNPortRateBase,INTEGER,read-create,,current,readableFrames(1):readableOctets(2):fcsErrors(3):alignmentErrors(4):frameTooLongs(5):shortEvents(6):runts(7):collisions(8):lateEvents(9):veryLongEvents(10):dataRateMismatches(11):autoPartitions(12):totalErrors(13):isolates(14):symbolErrors(15),The monitored variable, which the rptrTopNPortRate variable is based upon. The value of this object may not be modified if the associated rptrTopNPortRowStatus object has a value of active(1).
.1.3.6.1.2.1.22.4.3.1.1.4,SNMP-REPEATER-MIB::rptrTopNPortTimeRemaining,Integer32,read-create,,current,,The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, which is loaded into the associated rptrTopNPortDuration object. When this object is set to a non-zero value, any associated rptrTopNPortEntries shall be made inaccessible by the agent. While the value of this object is non-zero, it decrements by one per second until it reaches zero. During this time, all associated rptrTopNPortEntries shall remain inaccessible. At the time that this object decrements to zero, the report is made accessible in the rptrTopNPortTable. Thus, the rptrTopNPort table needs to be created only at the end of the collection interval. If the value of this object is set to zero while the associated report is running, the running report is aborted and no associated rptrTopNPortEntries are created.
.1.3.6.1.2.1.22.4.3.1.1.5,SNMP-REPEATER-MIB::rptrTopNPortDuration,Integer32,read-only,,current,,The number of seconds that this report has collected during the last sampling interval, or if this report is currently being collected, the number of seconds that this report is being collected during this sampling interval. When the associated rptrTopNPortTimeRemaining object is set, this object shall be set by the agent to the same value and shall not be modified until the next time the rptrTopNPortTimeRemaining is set. This value shall be zero if no reports have been requested for this rptrTopNPortControlEntry.
.1.3.6.1.2.1.22.4.3.1.1.6,SNMP-REPEATER-MIB::rptrTopNPortRequestedSize,Integer32,read-create,,current,,The maximum number of repeater ports requested for the Top N Table. When this object is created or modified, the agent should set rptrTopNPortGrantedSize as close to this object as is possible for the particular implementation and available resources.
.1.3.6.1.2.1.22.4.3.1.1.7,SNMP-REPEATER-MIB::rptrTopNPortGrantedSize,Integer32,read-only,,current,,The maximum number of repeater ports in the top N table. When the associated rptrTopNPortRequestedSize object is created or modified, the agent should set this object as closely to the requested value as is possible for the particular implementation and available resources. The agent must not lower this value except as a result of a set to the associated rptrTopNPortRequestedSize object.
.1.3.6.1.2.1.22.4.3.1.1.8,SNMP-REPEATER-MIB::rptrTopNPortStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated rptrTopNPortTimeRemaining object was modified to start the requested report. If the report has not yet been started, the value of this object is zero.
.1.3.6.1.2.1.22.4.3.1.1.9,SNMP-REPEATER-MIB::rptrTopNPortOwner,OCTET,read-create,,current,,The entity that configured this entry and is using the resources assigned to it.
.1.3.6.1.2.1.22.4.3.1.1.10,SNMP-REPEATER-MIB::rptrTopNPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. If the value of this object is not equal to active(1), all associated entries in the rptrTopNPortTable shall be deleted by the agent.
.1.3.6.1.2.1.22.4.3.2,SNMP-REPEATER-MIB::rptrTopNPortTable,,not-accessible,,current,,A table of reports for the top `N' ports based on setting of associated control table entries. The maximum number of entries depends on the number of entries in table rptrTopNPortControlTable and the value of object rptrTopNPortGrantedSize for each entry. For each entry in the rptrTopNPortControlTable, repeater ports with the highest value of rptrTopNPortRate shall be placed in this table in decreasing order of that rate until there is no more room or until there are no more ports.
.1.3.6.1.2.1.22.4.3.2.1,SNMP-REPEATER-MIB::rptrTopNPortEntry,,not-accessible,rptrTopNPortControlIndex:rptrTopNPortIndex,current,,A set of statistics for a repeater port that is part of a top N report.
.1.3.6.1.2.1.22.4.3.2.1.1,SNMP-REPEATER-MIB::rptrTopNPortIndex,Integer32,read-only,,current,,An index that uniquely identifies an entry in the rptrTopNPort table among those in the same report. This index is between 1 and N, where N is the number of entries in this report. Increasing values of rptrTopNPortIndex shall be assigned to entries with decreasing values of rptrTopNPortRate until index N is assigned to the entry with the lowest value of rptrTopNPortRate or there are no more rptrTopNPortEntries. No ports are included in a report where their value of rptrTopNPortRate would be zero.
.1.3.6.1.2.1.22.4.3.2.1.2,SNMP-REPEATER-MIB::rptrTopNPortGroupIndex,Integer32,read-only,,current,,This object identifes the group containing the port for this entry. (See also object type rptrGroupIndex.)
.1.3.6.1.2.1.22.4.3.2.1.3,SNMP-REPEATER-MIB::rptrTopNPortPortIndex,Integer32,read-only,,current,,The index of the repeater port. (See object type rptrPortIndex.)
.1.3.6.1.2.1.22.4.3.2.1.4,SNMP-REPEATER-MIB::rptrTopNPortRate,Gauge32,read-only,,current,,The amount of change in the selected variable during this sampling interval for the identified port. The selected variable is that port's instance of the object selected by rptrTopNPortRateBase.
.1.3.6.1.2.1.22.5,SNMP-REPEATER-MIB::snmpRptrMod,,,,,,Management information for 802.3 repeaters. The following references are used throughout this MIB module: [IEEE 802.3 Std] refers to IEEE 802.3/ISO 8802-3 Information processing systems - Local area networks - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications (1993). [IEEE 802.3 Mgt] refers to IEEE 802.3u-1995, '10 Mb/s & 100 Mb/s Management, Section 30,' Supplement to ANSI/IEEE 802.3. The following terms are used throughout this MIB module. For complete formal definitions, the IEEE 802.3 standards should be consulted wherever possible: System - A managed entity compliant with this MIB, and incorporating at least one managed 802.3 repeater. Chassis - An enclosure for one managed repeater, part of a managed repeater, or several managed repeaters. It typically contains an integral power supply and a variable number of available module slots. Repeater-unit - The portion of the repeater set that is inboard of the physical media interfaces. The physical media interfaces (MAUs, AUIs) may be physically separated from the repeater-unit, or they may be integrated into the same physical package. Trivial repeater-unit - An isolated port that can gather statistics. Group - A recommended, but optional, entity defined by the IEEE 802.3 management standard, in order to support a modular numbering scheme. The classical example allows an implementor to represent field-replaceable units as groups of ports, with the port numbering matching the modular hardware implementation. System interconnect segment - An internal segment allowing interconnection of ports belonging to different physical entities into the same logical manageable repeater. Examples of implementation might be backplane busses in modular hubs, or chaining cables in stacks of hubs. Stack - A scalable system that may include managed repeaters, in which modularity is achieved by interconnecting a number of different chassis. Module - A building block in a modular chassis. It typically maps into one 'slot'; however, the range of configurations may be very large, with several modules entering one slot, or one module covering several slots. 
.1.3.6.1.2.1.22.5.1,SNMP-REPEATER-MIB::snmpRptrModConf,,,,,,
.1.3.6.1.2.1.22.5.1.1,SNMP-REPEATER-MIB::snmpRptrModCompls,,,,,,
.1.3.6.1.2.1.22.5.1.1.1,SNMP-REPEATER-MIB::snmpRptrModComplRFC1368,,,,,,Compliance for RFC 1368. NOTE: this module compliance is OBSOLETE and replaced by snmpRptrModComplRFC1516.
.1.3.6.1.2.1.22.5.1.1.2,SNMP-REPEATER-MIB::snmpRptrModComplRFC1516,,,,,,********* THIS COMPLIANCE IS DEPRECATED ********** Compliance for RFC 1516 and for backwards compatibility with single-repeater, 10Mb/s-only implementations.
.1.3.6.1.2.1.22.5.1.1.3,SNMP-REPEATER-MIB::snmpRptrModCompl,,,,,,Compliance for the multi-segment version of the MIB module for a system with one or more repeater-units.
.1.3.6.1.2.1.22.5.1.2,SNMP-REPEATER-MIB::snmpRptrModObjGrps,,,,,,
.1.3.6.1.2.1.22.5.1.2.1,SNMP-REPEATER-MIB::snmpRptrGrpBasic1516,,,,,,********* THIS GROUP IS DEPRECATED ********** Basic group from RFCs 1368 and 1516. NOTE: this object group is DEPRECATED and replaced with snmpRptrGrpBasic.
.1.3.6.1.2.1.22.5.1.2.2,SNMP-REPEATER-MIB::snmpRptrGrpMonitor1516,,,,,,********* THIS GROUP IS DEPRECATED ********** Monitor group from RFCs 1368 and 1516. NOTE: this object group is DEPRECATED and replaced with snmpRptrGrpMonitor.
.1.3.6.1.2.1.22.5.1.2.3,SNMP-REPEATER-MIB::snmpRptrGrpAddrTrack1368,,,,,,Address tracking group from RFC 1368. NOTE: this object group is OBSOLETE and replaced with snmpRptrGrpAddrTrack1516.
.1.3.6.1.2.1.22.5.1.2.4,SNMP-REPEATER-MIB::snmpRptrGrpAddrTrack1516,,,,,,********* THIS GROUP IS DEPRECATED ********** Address tracking group from RFC 1516. NOTE: this object group is DEPRECATED and replaced with snmpRptrGrpAddrTrack.
.1.3.6.1.2.1.22.5.1.2.5,SNMP-REPEATER-MIB::snmpRptrGrpBasic,,,,,,Basic group for a system with one or more repeater-units in multi-segment (post-RFC 1516) version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.6,SNMP-REPEATER-MIB::snmpRptrGrpMonitor,,,,,,Monitor group for a system with one or more repeater-units in multi-segment (post-RFC 1516) version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.7,SNMP-REPEATER-MIB::snmpRptrGrpMonitor100,,,,,,Monitor group for 100Mb/s ports and repeaters in a system with one or more repeater-units in multi-segment (post-RFC 1516) version of the MIB module. Systems which support Counter64 should also implement snmpRptrGrpMonitor100w64.
.1.3.6.1.2.1.22.5.1.2.8,SNMP-REPEATER-MIB::snmpRptrGrpMonitor100w64,,,,,,Monitor group for 100Mb/s ports and repeaters in a system with one or more repeater-units and support for Counter64.
.1.3.6.1.2.1.22.5.1.2.9,SNMP-REPEATER-MIB::snmpRptrGrpAddrTrack,,,,,,Passive address tracking group for post-RFC 1516 version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.10,SNMP-REPEATER-MIB::snmpRptrGrpExtAddrTrack,,,,,,Extended passive address tracking group for a system with one or more repeater-units in post-RFC 1516 version of the MIB module.
.1.3.6.1.2.1.22.5.1.2.11,SNMP-REPEATER-MIB::snmpRptrGrpRptrAddrSearch,,,,,,Active MAC address search group and topology mapping support for repeaters.
.1.3.6.1.2.1.22.5.1.2.12,SNMP-REPEATER-MIB::snmpRptrGrpTopNPort,,,,,,Top `N' group for repeater ports.
.1.3.6.1.2.1.22.5.1.3,SNMP-REPEATER-MIB::snmpRptrModNotGrps,,,,,,
.1.3.6.1.2.1.23,RFC1389-MIB::rip2,,,,,,
.1.3.6.1.2.1.23.1,RFC1389-MIB::rip2GlobalGroup,,,,,,
.1.3.6.1.2.1.23.1.1,RFC1389-MIB::rip2GlobalRouteChanges,Counter32,read-only,,mandatory,,The number of route changes made to the IP Route Database by RIP. This does not include the refresh of a route's age.
.1.3.6.1.2.1.23.1.2,RFC1389-MIB::rip2GlobalQueries,Counter32,read-only,,mandatory,,The number of responses sent to RIP queries from other systems.
.1.3.6.1.2.1.23.2,RFC1389-MIB::rip2IfStatTable,,not-accessible,,mandatory,,A list of subnets which require separate status monitoring in RIP.
.1.3.6.1.2.1.23.2.1,RFC1389-MIB::rip2IfStatEntry,,not-accessible,rip2IfStatAddress,mandatory,,A Single Routing Domain in a single Subnet.
.1.3.6.1.2.1.23.2.1.1,RFC1389-MIB::rip2IfStatAddress,IpAddress,read-only,,mandatory,,The IP Address of this system on the indicated subnet. For unnumbered interfaces, the value 0.0.0.N, where the least significant 24 bits (N) is the ifIndex for the IP Interface in network byte order.
.1.3.6.1.2.1.23.2.1.2,RFC1389-MIB::rip2IfStatRcvBadPackets,Counter32,read-only,,mandatory,,The number of RIP response packets received by the RIP process which were subsequently discarded for any reason (e.g. a version 0 packet, or an unknown command type).
.1.3.6.1.2.1.23.2.1.3,RFC1389-MIB::rip2IfStatRcvBadRoutes,Counter32,read-only,,mandatory,,The number of routes, in valid RIP packets, which were ignored for any reason (e.g. unknown address family, or invalid metric).
.1.3.6.1.2.1.23.2.1.4,RFC1389-MIB::rip2IfStatSentUpdates,Counter32,read-only,,mandatory,,The number of triggered RIP updates actually sent on this interface. This explicitly does NOT include full updates sent containing new information.
.1.3.6.1.2.1.23.2.1.5,RFC1389-MIB::rip2IfStatStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),Writing invalid has the effect of deleting this interface.
.1.3.6.1.2.1.23.3,RFC1389-MIB::rip2IfConfTable,,not-accessible,,mandatory,,A list of subnets which require separate configuration in RIP.
.1.3.6.1.2.1.23.3.1,RFC1389-MIB::rip2IfConfEntry,,not-accessible,rip2IfConfAddress,mandatory,,A Single Routing Domain in a single Subnet.
.1.3.6.1.2.1.23.3.1.1,RFC1389-MIB::rip2IfConfAddress,IpAddress,read-only,,mandatory,,The IP Address of this system on the indicated subnet. For unnumbered interfaces, the value 0.0.0.N, where the least significant 24 bits (N) is the ifIndex for the IP Interface in network byte order.
.1.3.6.1.2.1.23.3.1.2,RFC1389-MIB::rip2IfConfDomain,OCTET,read-write,,deprecated,,Value inserted into the Routing Domain field of all RIP packets sent on this interface.
.1.3.6.1.2.1.23.3.1.3,RFC1389-MIB::rip2IfConfAuthType,INTEGER,read-write,,mandatory,noAuthentication(1):simplePassword(2):md5(3),The type of Authentication used on this interface.
.1.3.6.1.2.1.23.3.1.4,RFC1389-MIB::rip2IfConfAuthKey,OCTET,read-write,,mandatory,,The value to be used as the Authentication Key whenever the corresponding instance of rip2IfConfAuthType has the value simplePassword word. A modification of the corresponding instance of rip2IfConfAuthType does not modify the rip2IfConfAuthKey value. If a string shorter than 16 octets is supplied, it will be left- justified and padded to 16 octets, on the right, with nulls (0x00). Reading this object always results in an OCTET STRING of length zero; authentication may not be bypassed by reading the MIB object.
.1.3.6.1.2.1.23.3.1.5,RFC1389-MIB::rip2IfConfSend,INTEGER,read-write,,mandatory,doNotSend(1):ripVersion1(2):rip1Compatible(3):ripVersion2(4):ripV1Demand(5):ripV2Demand(6),What the router sends on this interface. ripVersion1 implies sending RIP updates compliant with RFC 1058. rip1Compatible implies broadcasting RIP-2 updates using RFC 1058 route subsumption rules. ripVersion2 implies multicasting RIP-2 updates. ripV1Demand indicates the use of Demand RIP on a WAN interface under RIP Version 1 rules. ripV2Demand indicates the use of Demand RIP on a WAN interface under Version 2 rules.
.1.3.6.1.2.1.23.3.1.6,RFC1389-MIB::rip2IfConfReceive,INTEGER,read-write,,mandatory,rip1(1):rip2(2):rip1OrRip2(3):doNotRecieve(4),This indicates which version of RIP updates are to be accepted. Note that rip2 and rip1OrRip2 implies reception of multicast packets.
.1.3.6.1.2.1.23.3.1.7,RFC1389-MIB::rip2IfConfDefaultMetric,INTEGER,read-write,,mandatory,,This variable indicates the metric that is to be used for the default route entry in RIP updates originated on this interface. A value of zero indicates that no default route should be originated; in this case, a default route via another router may be propagated.
.1.3.6.1.2.1.23.3.1.8,RFC1389-MIB::rip2IfConfStatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),Writing invalid has the effect of deleting this interface.
.1.3.6.1.2.1.23.3.1.9,RFC1389-MIB::rip2IfConfSrcAddress,IpAddress,read-write,,mandatory,,The IP Address this system will use as a source address on this interface. If it is a numbered interface, this MUST be the same value as rip2IfConfAddress. On unnumbered interfaces, it must be the value of rip2IfConfAddress for some interface on the system.
.1.3.6.1.2.1.23.4,RFC1389-MIB::rip2PeerTable,,not-accessible,,mandatory,,A list of RIP Peers.
.1.3.6.1.2.1.23.4.1,RFC1389-MIB::rip2PeerEntry,,not-accessible,rip2PeerAddress:rip2PeerDomain,mandatory,,Information regarding a single routing peer.
.1.3.6.1.2.1.23.4.1.1,RFC1389-MIB::rip2PeerAddress,IpAddress,read-only,,mandatory,,The IP Address that the peer is using as its source address. Note that on an unnumbered link, this may not be a member of any subnet on the system.
.1.3.6.1.2.1.23.4.1.2,RFC1389-MIB::rip2PeerDomain,OCTET,read-only,,mandatory,,The value in the Routing Domain field in RIP packets received from the peer. As domain suuport is deprecated, this must be zero.
.1.3.6.1.2.1.23.4.1.3,RFC1389-MIB::rip2PeerLastUpdate,TimeTicks,read-only,,mandatory,,The value of sysUpTime when the most recent RIP update was received from this system.
.1.3.6.1.2.1.23.4.1.4,RFC1389-MIB::rip2PeerVersion,INTEGER,read-only,,mandatory,,The RIP version number in the header of the last RIP packet received.
.1.3.6.1.2.1.23.4.1.5,RFC1389-MIB::rip2PeerRcvBadPackets,Counter32,read-only,,mandatory,,The number of RIP response packets from this peer discarded as invalid.
.1.3.6.1.2.1.23.4.1.6,RFC1389-MIB::rip2PeerRcvBadRoutes,Counter32,read-only,,mandatory,,The number of routes from this peer that were ignored because the entry format was invalid.
.1.3.6.1.2.1.23.5,RIPv2-MIB::rip2Conformance,,,,,,
.1.3.6.1.2.1.23.5.1,RIPv2-MIB::rip2Groups,,,,,,
.1.3.6.1.2.1.23.5.1.1,RIPv2-MIB::rip2GlobalGroup,,,,,,This group defines global controls for RIP-II systems.
.1.3.6.1.2.1.23.5.1.2,RIPv2-MIB::rip2IfStatGroup,,,,,,This group defines interface statistics for RIP-II systems.
.1.3.6.1.2.1.23.5.1.3,RIPv2-MIB::rip2IfConfGroup,,,,,,This group defines interface configuration for RIP-II systems.
.1.3.6.1.2.1.23.5.1.4,RIPv2-MIB::rip2PeerGroup,,,,,,This group defines peer information for RIP-II systems.
.1.3.6.1.2.1.23.5.2,RIPv2-MIB::rip2Compliances,,,,,,
.1.3.6.1.2.1.23.5.2.1,RIPv2-MIB::rip2Compliance,,,,,,The compliance statement 
.1.3.6.1.2.1.24,RFC1414-MIB::ident,,,,,,
.1.3.6.1.2.1.24.1,RFC1414-MIB::identInfo,,,,,,
.1.3.6.1.2.1.24.1.1,RFC1414-MIB::identTable,,not-accessible,,mandatory,,A table containing user information for TCP connections. Note that this table contains entries for all TCP connections on a managed system. The corresponding instance of tcpConnState (defined in MIB-II) indicates the state of a particular connection.
.1.3.6.1.2.1.24.1.1.1,RFC1414-MIB::identEntry,,not-accessible,tcpConnLocalAddress:tcpConnLocalPort:tcpConnRemAddress:tcpConnRemPort,mandatory,,User information about a particular TCP connection.
.1.3.6.1.2.1.24.1.1.1.1,RFC1414-MIB::identStatus,INTEGER,read-only,,mandatory,noError(1):unknownError(2),Indicates whether user information for the associated TCP connection can be determined. A value of `noError(1)' indicates that user information is available. A value of `unknownError(2)' indicates that user information is not available.
.1.3.6.1.2.1.24.1.1.1.2,RFC1414-MIB::identOpSys,OCTET,read-only,,mandatory,,Indicates the type of operating system in use. In addition to identifying an operating system, each assignment made for this purpose also (implicitly) identifies the textual format and maximum size of the corresponding identUserid and identMisc objects. The legal values for the `indentOpSys' strings are those listed in the SYSTEM NAMES section of the most recent edition of the ASSIGNED NUMBERS RFC [8].
.1.3.6.1.2.1.24.1.1.1.3,RFC1414-MIB::identCharset,OCTET,read-only,,mandatory,,Indicates the repertoire of the corresponding identUserid and identMisc objects. The legal values for the `identCharset' strings are those listed in the CHARACTER SET section of the most recent edition of the ASSIGNED NUMBERS RFC [8].
.1.3.6.1.2.1.24.1.1.1.4,RFC1414-MIB::identUserid,OCTET,read-only,,mandatory,,Indicates the user's identity. Interpretation of this object requires examination of the corresponding value of the identOpSys and identCharset objects.
.1.3.6.1.2.1.24.1.1.1.5,RFC1414-MIB::identMisc,OCTET,read-only,,mandatory,,Indicates miscellaneous information about the user. Interpretation of this object requires examination of the corresponding value of the identOpSys and identCharset objects.
.1.3.6.1.2.1.25,HOST-RESOURCES-MIB::host,,,,,,
.1.3.6.1.2.1.25.1,HOST-RESOURCES-MIB::hrSystem,,,,,,
.1.3.6.1.2.1.25.1.1,HOST-RESOURCES-MIB::hrSystemUptime,TimeTicks,read-only,,current,,The amount of time since this host was last initialized. Note that this is different from sysUpTime in the SNMPv2-MIB [RFC1907] because sysUpTime is the uptime of the network management portion of the system.
.1.3.6.1.2.1.25.1.2,HOST-RESOURCES-MIB::hrSystemDate,OCTET,read-write,,current,,The host's notion of the local date and time of day.
.1.3.6.1.2.1.25.1.3,HOST-RESOURCES-MIB::hrSystemInitialLoadDevice,Integer32,read-write,,current,,The index of the hrDeviceEntry for the device from which this host is configured to load its initial operating system configuration (i.e., which operating system code and/or boot parameters). Note that writing to this object just changes the configuration that will be used the next time the operating system is loaded and does not actually cause the reload to occur.
.1.3.6.1.2.1.25.1.4,HOST-RESOURCES-MIB::hrSystemInitialLoadParameters,OCTET,read-write,,current,,This object contains the parameters (e.g. a pathname and parameter) supplied to the load device when requesting the initial operating system configuration from that device. Note that writing to this object just changes the configuration that will be used the next time the operating system is loaded and does not actually cause the reload to occur.
.1.3.6.1.2.1.25.1.5,HOST-RESOURCES-MIB::hrSystemNumUsers,Gauge32,read-only,,current,,The number of user sessions for which this host is storing state information. A session is a collection of processes requiring a single act of user authentication and possibly subject to collective job control.
.1.3.6.1.2.1.25.1.6,HOST-RESOURCES-MIB::hrSystemProcesses,Gauge32,read-only,,current,,The number of process contexts currently loaded or running on this system.
.1.3.6.1.2.1.25.1.7,HOST-RESOURCES-MIB::hrSystemMaxProcesses,Integer32,read-only,,current,,The maximum number of process contexts this system can support. If there is no fixed maximum, the value should be zero. On systems that have a fixed maximum, this object can help diagnose failures that occur when this maximum is reached.
.1.3.6.1.2.1.25.2,HOST-RESOURCES-MIB::hrStorage,,,,,,
.1.3.6.1.2.1.25.2.1,HOST-RESOURCES-MIB::hrStorageTypes,,,,,,
.1.3.6.1.2.1.25.2.1.1,HOST-RESOURCES-TYPES::hrStorageOther,,,,,,The storage type identifier used when no other defined type is appropriate.
.1.3.6.1.2.1.25.2.1.2,HOST-RESOURCES-TYPES::hrStorageRam,,,,,,The storage type identifier used for RAM.
.1.3.6.1.2.1.25.2.1.3,HOST-RESOURCES-TYPES::hrStorageVirtualMemory,,,,,,The storage type identifier used for virtual memory, temporary storage of swapped or paged memory.
.1.3.6.1.2.1.25.2.1.4,HOST-RESOURCES-TYPES::hrStorageFixedDisk,,,,,,The storage type identifier used for non-removable rigid rotating magnetic storage devices.
.1.3.6.1.2.1.25.2.1.5,HOST-RESOURCES-TYPES::hrStorageRemovableDisk,,,,,,The storage type identifier used for removable rigid rotating magnetic storage devices.
.1.3.6.1.2.1.25.2.1.6,HOST-RESOURCES-TYPES::hrStorageFloppyDisk,,,,,,The storage type identifier used for non-rigid rotating magnetic storage devices.
.1.3.6.1.2.1.25.2.1.7,HOST-RESOURCES-TYPES::hrStorageCompactDisc,,,,,,The storage type identifier used for read-only rotating optical storage devices.
.1.3.6.1.2.1.25.2.1.8,HOST-RESOURCES-TYPES::hrStorageRamDisk,,,,,,The storage type identifier used for a file system that is stored in RAM.
.1.3.6.1.2.1.25.2.1.9,HOST-RESOURCES-TYPES::hrStorageFlashMemory,,,,,,The storage type identifier used for flash memory.
.1.3.6.1.2.1.25.2.1.10,HOST-RESOURCES-TYPES::hrStorageNetworkDisk,,,,,,The storage type identifier used for a networked file system.
.1.3.6.1.2.1.25.2.2,HOST-RESOURCES-MIB::hrMemorySize,Integer32,read-only,,current,,The amount of physical read-write main memory, typically RAM, contained by the host.
.1.3.6.1.2.1.25.2.3,HOST-RESOURCES-MIB::hrStorageTable,,not-accessible,,current,,The (conceptual) table of logical storage areas on the host. An entry shall be placed in the storage table for each logical area of storage that is allocated and has fixed resource limits. The amount of storage represented in an entity is the amount actually usable by the requesting entity, and excludes loss due to formatting or file system reference information. These entries are associated with logical storage areas, as might be seen by an application, rather than physical storage entities which are typically seen by an operating system. Storage such as tapes and floppies without file systems on them are typically not allocated in chunks by the operating system to requesting applications, and therefore shouldn't appear in this table. Examples of valid storage for this table include disk partitions, file systems, ram (for some architectures this is further segmented into regular memory, extended memory, and so on), backing store for virtual memory (`swap space'). This table is intended to be a useful diagnostic for `out of memory' and `out of buffers' types of failures. In addition, it can be a useful performance monitoring tool for tracking memory, disk, or buffer usage.
.1.3.6.1.2.1.25.2.3.1,HOST-RESOURCES-MIB::hrStorageEntry,,not-accessible,hrStorageIndex,current,,A (conceptual) entry for one logical storage area on the host. As an example, an instance of the hrStorageType object might be named hrStorageType.3
.1.3.6.1.2.1.25.2.3.1.1,HOST-RESOURCES-MIB::hrStorageIndex,Integer32,read-only,,current,,A unique value for each logical storage area contained by the host.
.1.3.6.1.2.1.25.2.3.1.2,HOST-RESOURCES-MIB::hrStorageType,OBJECT,read-only,,current,,The type of storage represented by this entry.
.1.3.6.1.2.1.25.2.3.1.3,HOST-RESOURCES-MIB::hrStorageDescr,OCTET,read-only,,current,,A description of the type and instance of the storage described by this entry.
.1.3.6.1.2.1.25.2.3.1.4,HOST-RESOURCES-MIB::hrStorageAllocationUnits,Integer32,read-only,,current,,The size, in bytes, of the data objects allocated from this pool. If this entry is monitoring sectors, blocks, buffers, or packets, for example, this number will commonly be greater than one. Otherwise this number will typically be one.
.1.3.6.1.2.1.25.2.3.1.5,HOST-RESOURCES-MIB::hrStorageSize,Integer32,read-write,,current,,The size of the storage represented by this entry, in units of hrStorageAllocationUnits. This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system. For example, the amount of main memory allocated to a buffer pool might be modified or the amount of disk space allocated to virtual memory might be modified.
.1.3.6.1.2.1.25.2.3.1.6,HOST-RESOURCES-MIB::hrStorageUsed,Integer32,read-only,,current,,The amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.
.1.3.6.1.2.1.25.2.3.1.7,HOST-RESOURCES-MIB::hrStorageAllocationFailures,of,read-only,,current,,The number of requests for storage represented by this entry that could not be honored due to not enough storage. It should be noted that as this object has a initial value. However, it is recommended that this object be initialized to zero, even though management stations must not depend on such an initialization.
.1.3.6.1.2.1.25.3,HOST-RESOURCES-MIB::hrDevice,,,,,,
.1.3.6.1.2.1.25.3.1,HOST-RESOURCES-MIB::hrDeviceTypes,,,,,,
.1.3.6.1.2.1.25.3.1.1,HOST-RESOURCES-TYPES::hrDeviceOther,,,,,,The device type identifier used when no other defined type is appropriate.
.1.3.6.1.2.1.25.3.1.2,HOST-RESOURCES-TYPES::hrDeviceUnknown,,,,,,The device type identifier used when the device type is unknown.
.1.3.6.1.2.1.25.3.1.3,HOST-RESOURCES-TYPES::hrDeviceProcessor,,,,,,The device type identifier used for a CPU.
.1.3.6.1.2.1.25.3.1.4,HOST-RESOURCES-TYPES::hrDeviceNetwork,,,,,,The device type identifier used for a network interface.
.1.3.6.1.2.1.25.3.1.5,HOST-RESOURCES-TYPES::hrDevicePrinter,,,,,,The device type identifier used for a printer.
.1.3.6.1.2.1.25.3.1.6,HOST-RESOURCES-TYPES::hrDeviceDiskStorage,,,,,,The device type identifier used for a disk drive.
.1.3.6.1.2.1.25.3.1.10,HOST-RESOURCES-TYPES::hrDeviceVideo,,,,,,The device type identifier used for a video device.
.1.3.6.1.2.1.25.3.1.11,HOST-RESOURCES-TYPES::hrDeviceAudio,,,,,,The device type identifier used for an audio device.
.1.3.6.1.2.1.25.3.1.12,HOST-RESOURCES-TYPES::hrDeviceCoprocessor,,,,,,The device type identifier used for a co-processor.
.1.3.6.1.2.1.25.3.1.13,HOST-RESOURCES-TYPES::hrDeviceKeyboard,,,,,,The device type identifier used for a keyboard device.
.1.3.6.1.2.1.25.3.1.14,HOST-RESOURCES-TYPES::hrDeviceModem,,,,,,The device type identifier used for a modem.
.1.3.6.1.2.1.25.3.1.15,HOST-RESOURCES-TYPES::hrDeviceParallelPort,,,,,,The device type identifier used for a parallel port.
.1.3.6.1.2.1.25.3.1.16,HOST-RESOURCES-TYPES::hrDevicePointing,,,,,,The device type identifier used for a pointing device (e.g., a mouse).
.1.3.6.1.2.1.25.3.1.17,HOST-RESOURCES-TYPES::hrDeviceSerialPort,,,,,,The device type identifier used for a serial port.
.1.3.6.1.2.1.25.3.1.18,HOST-RESOURCES-TYPES::hrDeviceTape,,,,,,The device type identifier used for a tape storage device.
.1.3.6.1.2.1.25.3.1.19,HOST-RESOURCES-TYPES::hrDeviceClock,,,,,,The device type identifier used for a clock device.
.1.3.6.1.2.1.25.3.1.20,HOST-RESOURCES-TYPES::hrDeviceVolatileMemory,,,,,,The device type identifier used for a volatile memory storage device.
.1.3.6.1.2.1.25.3.1.21,HOST-RESOURCES-TYPES::hrDeviceNonVolatileMemory,,,,,,The device type identifier used for a non-volatile memory storage device.
.1.3.6.1.2.1.25.3.2,HOST-RESOURCES-MIB::hrDeviceTable,,not-accessible,,current,,The (conceptual) table of devices contained by the host.
.1.3.6.1.2.1.25.3.2.1,HOST-RESOURCES-MIB::hrDeviceEntry,,not-accessible,hrDeviceIndex,current,,A (conceptual) entry for one device contained by the host. As an example, an instance of the hrDeviceType object might be named hrDeviceType.3
.1.3.6.1.2.1.25.3.2.1.1,HOST-RESOURCES-MIB::hrDeviceIndex,Integer32,read-only,,current,,A unique value for each device contained by the host. The value for each device must remain constant at least from one re-initialization of the agent to the next re-initialization.
.1.3.6.1.2.1.25.3.2.1.2,HOST-RESOURCES-MIB::hrDeviceType,OBJECT,read-only,,current,,An indication of the type of device. If this value is `hrDeviceProcessor { hrDeviceTypes 3 }' then an entry exists in the hrProcessorTable which corresponds to this device. If this value is `hrDeviceNetwork { hrDeviceTypes 4 }', then an entry exists in the hrNetworkTable which corresponds to this device. If this value is `hrDevicePrinter { hrDeviceTypes 5 }', then an entry exists in the hrPrinterTable which corresponds to this device. If this value is `hrDeviceDiskStorage { hrDeviceTypes 6 }', then an entry exists in the hrDiskStorageTable which corresponds to this device.
.1.3.6.1.2.1.25.3.2.1.3,HOST-RESOURCES-MIB::hrDeviceDescr,OCTET,read-only,,current,,A textual description of this device, including the device's manufacturer and revision, and optionally, its serial number.
.1.3.6.1.2.1.25.3.2.1.4,HOST-RESOURCES-MIB::hrDeviceID,OBJECT,read-only,,current,,The product ID for this device.
.1.3.6.1.2.1.25.3.2.1.5,HOST-RESOURCES-MIB::hrDeviceStatus,INTEGER,read-only,,current,unknown(1):running(2):warning(3):testing(4):down(5),The current operational state of the device described by this row of the table. A value unknown(1) indicates that the current state of the device is unknown. running(2) indicates that the device is up and running and that no unusual error conditions are known. The warning(3) state indicates that agent has been informed of an unusual error condition by the operational software (e.g., a disk device driver) but that the device is still 'operational'. An example would be a high number of soft errors on a disk. A value of testing(4), indicates that the device is not available for use because it is in the testing state. The state of down(5) is used only when the agent has been informed that the device is not available for any use.
.1.3.6.1.2.1.25.3.2.1.6,HOST-RESOURCES-MIB::hrDeviceErrors,Counter32,read-only,,current,,The number of errors detected on this device. It should be noted that as this object has a SYNTAX of Counter32, that it does not have a defined initial value. However, it is recommended that this object be initialized to zero, even though management stations must not depend on such an initialization.
.1.3.6.1.2.1.25.3.3,HOST-RESOURCES-MIB::hrProcessorTable,,not-accessible,,current,,The (conceptual) table of processors contained by the host. Note that this table is potentially sparse: a (conceptual) entry exists only if the correspondent value of the hrDeviceType object is `hrDeviceProcessor'.
.1.3.6.1.2.1.25.3.3.1,HOST-RESOURCES-MIB::hrProcessorEntry,,not-accessible,hrDeviceIndex,current,,A (conceptual) entry for one processor contained by the host. The hrDeviceIndex in the index represents the entry in the hrDeviceTable that corresponds to the hrProcessorEntry. As an example of how objects in this table are named, an instance of the hrProcessorFrwID object might be named hrProcessorFrwID.3
.1.3.6.1.2.1.25.3.3.1.1,HOST-RESOURCES-MIB::hrProcessorFrwID,OBJECT,read-only,,current,,The product ID of the firmware associated with the processor.
.1.3.6.1.2.1.25.3.3.1.2,HOST-RESOURCES-MIB::hrProcessorLoad,Integer32,read-only,,current,,The average, over the last minute, of the percentage of time that this processor was not idle. Implementations may approximate this one minute smoothing period if necessary.
.1.3.6.1.2.1.25.3.4,HOST-RESOURCES-MIB::hrNetworkTable,,not-accessible,,current,,The (conceptual) table of network devices contained by the host. Note that this table is potentially sparse: a (conceptual) entry exists only if the correspondent value of the hrDeviceType object is `hrDeviceNetwork'.
.1.3.6.1.2.1.25.3.4.1,HOST-RESOURCES-MIB::hrNetworkEntry,,not-accessible,hrDeviceIndex,current,,A (conceptual) entry for one network device contained by the host. The hrDeviceIndex in the index represents the entry in the hrDeviceTable that corresponds to the hrNetworkEntry. As an example of how objects in this table are named, an instance of the hrNetworkIfIndex object might be named hrNetworkIfIndex.3
.1.3.6.1.2.1.25.3.4.1.1,HOST-RESOURCES-MIB::hrNetworkIfIndex,Integer32,read-only,,current,,The value of ifIndex which corresponds to this network device. If this device is not represented in the ifTable, then this value shall be zero.
.1.3.6.1.2.1.25.3.5,HOST-RESOURCES-MIB::hrPrinterTable,,not-accessible,,current,,The (conceptual) table of printers local to the host. Note that this table is potentially sparse: a (conceptual) entry exists only if the correspondent value of the hrDeviceType object is `hrDevicePrinter'.
.1.3.6.1.2.1.25.3.5.1,HOST-RESOURCES-MIB::hrPrinterEntry,,not-accessible,hrDeviceIndex,current,,A (conceptual) entry for one printer local to the host. The hrDeviceIndex in the index represents the entry in the hrDeviceTable that corresponds to the hrPrinterEntry. As an example of how objects in this table are named, an instance of the hrPrinterStatus object might be named hrPrinterStatus.3
.1.3.6.1.2.1.25.3.5.1.1,HOST-RESOURCES-MIB::hrPrinterStatus,INTEGER,read-only,,current,other(1):unknown(2):idle(3):printing(4):warmup(5),The current status of this printer device.
.1.3.6.1.2.1.25.3.5.1.2,HOST-RESOURCES-MIB::hrPrinterDetectedErrorState,OCTET,read-only,,current,,This object represents any error conditions detected by the printer. The error conditions are encoded as bits in an octet string, with the following definitions: Condition Bit # lowPaper 0 noPaper 1 lowToner 2 noToner 3 doorOpen 4 jammed 5 offline 6 serviceRequested 7 inputTrayMissing 8 outputTrayMissing 9 markerSupplyMissing 10 outputNearFull 11 outputFull 12 inputTrayEmpty 13 overduePreventMaint 14 Bits are numbered starting with the most significant bit of the first byte being bit 0, the least significant bit of the first byte being bit 7, the most significant bit of the second byte being bit 8, and so on. A one bit encodes that the condition was detected, while a zero bit encodes that the condition was not detected. This object is useful for alerting an operator to specific warning or error conditions that may occur, especially those requiring human intervention.
.1.3.6.1.2.1.25.3.6,HOST-RESOURCES-MIB::hrDiskStorageTable,,not-accessible,,current,,The (conceptual) table of long-term storage devices contained by the host. In particular, disk devices accessed remotely over a network are not included here. Note that this table is potentially sparse: a (conceptual) entry exists only if the correspondent value of the hrDeviceType object is `hrDeviceDiskStorage'.
.1.3.6.1.2.1.25.3.6.1,HOST-RESOURCES-MIB::hrDiskStorageEntry,,not-accessible,hrDeviceIndex,current,,A (conceptual) entry for one long-term storage device contained by the host. The hrDeviceIndex in the index represents the entry in the hrDeviceTable that corresponds to the hrDiskStorageEntry. As an example, an instance of the hrDiskStorageCapacity object might be named hrDiskStorageCapacity.3
.1.3.6.1.2.1.25.3.6.1.1,HOST-RESOURCES-MIB::hrDiskStorageAccess,INTEGER,read-only,,current,readWrite(1):readOnly(2),An indication if this long-term storage device is readable and writable or only readable. This should reflect the media type, any write-protect mechanism, and any device configuration that affects the entire device.
.1.3.6.1.2.1.25.3.6.1.2,HOST-RESOURCES-MIB::hrDiskStorageMedia,INTEGER,read-only,,current,other(1):unknown(2):hardDisk(3):floppyDisk(4):opticalDiskROM(5):opticalDiskWORM(6):opticalDiskRW(7):ramDisk(8),An indication of the type of media used in this long- term storage device.
.1.3.6.1.2.1.25.3.6.1.3,HOST-RESOURCES-MIB::hrDiskStorageRemoveble,INTEGER,read-only,,current,true(1):false(2),Denotes whether or not the disk media may be removed from the drive.
.1.3.6.1.2.1.25.3.6.1.4,HOST-RESOURCES-MIB::hrDiskStorageCapacity,Integer32,read-only,,current,,The total size for this long-term storage device. If the media is removable and is currently removed, this value should be zero.
.1.3.6.1.2.1.25.3.7,HOST-RESOURCES-MIB::hrPartitionTable,,not-accessible,,current,,The (conceptual) table of partitions for long-term storage devices contained by the host. In particular, partitions accessed remotely over a network are not included here.
.1.3.6.1.2.1.25.3.7.1,HOST-RESOURCES-MIB::hrPartitionEntry,,not-accessible,hrDeviceIndex:hrPartitionIndex,current,,A (conceptual) entry for one partition. The hrDeviceIndex in the index represents the entry in the hrDeviceTable that corresponds to the hrPartitionEntry. As an example of how objects in this table are named, an instance of the hrPartitionSize object might be named hrPartitionSize.3.1
.1.3.6.1.2.1.25.3.7.1.1,HOST-RESOURCES-MIB::hrPartitionIndex,Integer32,read-only,,current,,A unique value for each partition on this long-term storage device. The value for each long-term storage device must remain constant at least from one re- initialization of the agent to the next re- initialization.
.1.3.6.1.2.1.25.3.7.1.2,HOST-RESOURCES-MIB::hrPartitionLabel,OCTET,read-only,,current,,A textual description of this partition.
.1.3.6.1.2.1.25.3.7.1.3,HOST-RESOURCES-MIB::hrPartitionID,OCTET,read-only,,current,,A descriptor which uniquely represents this partition to the responsible operating system. On some systems, this might take on a binary representation.
.1.3.6.1.2.1.25.3.7.1.4,HOST-RESOURCES-MIB::hrPartitionSize,Integer32,read-only,,current,,The size of this partition.
.1.3.6.1.2.1.25.3.7.1.5,HOST-RESOURCES-MIB::hrPartitionFSIndex,Integer32,read-only,,current,,The index of the file system mounted on this partition. If no file system is mounted on this partition, then this value shall be zero. Note that multiple partitions may point to one file system, denoting that that file system resides on those partitions. Multiple file systems may not reside on one partition.
.1.3.6.1.2.1.25.3.8,HOST-RESOURCES-MIB::hrFSTable,,not-accessible,,current,,The (conceptual) table of file systems local to this host or remotely mounted from a file server. File systems that are in only one user's environment on a multi-user system will not be included in this table.
.1.3.6.1.2.1.25.3.8.1,HOST-RESOURCES-MIB::hrFSEntry,,not-accessible,hrFSIndex,current,,A (conceptual) entry for one file system local to this host or remotely mounted from a file server. File systems that are in only one user's environment on a multi-user system will not be included in this table. As an example of how objects in this table are named, an instance of the hrFSMountPoint object might be named hrFSMountPoint.3
.1.3.6.1.2.1.25.3.8.1.1,HOST-RESOURCES-MIB::hrFSIndex,Integer32,read-only,,current,,A unique value for each file system local to this host. The value for each file system must remain constant at least from one re-initialization of the agent to the next re-initialization.
.1.3.6.1.2.1.25.3.8.1.2,HOST-RESOURCES-MIB::hrFSMountPoint,OCTET,read-only,,current,,The path name of the root of this file system.
.1.3.6.1.2.1.25.3.8.1.3,HOST-RESOURCES-MIB::hrFSRemoteMountPoint,OCTET,read-only,,current,,A description of the name and/or address of the server that this file system is mounted from. This may also include parameters such as the mount point on the remote file system. If this is not a remote file system, this string should have a length of zero.
.1.3.6.1.2.1.25.3.8.1.4,HOST-RESOURCES-MIB::hrFSType,OBJECT,read-only,,current,,The value of this object identifies the type of this file system.
.1.3.6.1.2.1.25.3.8.1.5,HOST-RESOURCES-MIB::hrFSAccess,INTEGER,read-only,,current,readWrite(1):readOnly(2),An indication if this file system is logically configured by the operating system to be readable and writable or only readable. This does not represent any local access-control policy, except one that is applied to the file system as a whole.
.1.3.6.1.2.1.25.3.8.1.6,HOST-RESOURCES-MIB::hrFSBootable,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether this file system is bootable.
.1.3.6.1.2.1.25.3.8.1.7,HOST-RESOURCES-MIB::hrFSStorageIndex,Integer32,read-only,,current,,The index of the hrStorageEntry that represents information about this file system. If there is no such information available, then this value shall be zero. The relevant storage entry will be useful in tracking the percent usage of this file system and diagnosing errors that may occur when it runs out of space.
.1.3.6.1.2.1.25.3.8.1.8,HOST-RESOURCES-MIB::hrFSLastFullBackupDate,OCTET,read-write,,current,,The last date at which this complete file system was copied to another storage device for backup. This information is useful for ensuring that backups are being performed regularly. If this information is not known, then this variable shall have the value corresponding to January 1, year 0000, 00:00:00.0, which is encoded as (hex)'00 00 01 01 00 00 00 00'.
.1.3.6.1.2.1.25.3.8.1.9,HOST-RESOURCES-MIB::hrFSLastPartialBackupDate,OCTET,read-write,,current,,The last date at which a portion of this file system was copied to another storage device for backup. This information is useful for ensuring that backups are being performed regularly. If this information is not known, then this variable shall have the value corresponding to January 1, year 0000, 00:00:00.0, which is encoded as (hex)'00 00 01 01 00 00 00 00'.
.1.3.6.1.2.1.25.3.9,HOST-RESOURCES-MIB::hrFSTypes,,,,,,
.1.3.6.1.2.1.25.3.9.1,HOST-RESOURCES-TYPES::hrFSOther,,,,,,The file system type identifier used when no other defined type is appropriate.
.1.3.6.1.2.1.25.3.9.2,HOST-RESOURCES-TYPES::hrFSUnknown,,,,,,The file system type identifier used when the type of file system is unknown.
.1.3.6.1.2.1.25.3.9.3,HOST-RESOURCES-TYPES::hrFSBerkeleyFFS,,,,,,The file system type identifier used for the Berkeley Fast File System.
.1.3.6.1.2.1.25.3.9.4,HOST-RESOURCES-TYPES::hrFSSys5FS,,,,,,The file system type identifier used for the System V File System.
.1.3.6.1.2.1.25.3.9.5,HOST-RESOURCES-TYPES::hrFSFat,,,,,,The file system type identifier used for DOS's FAT file system.
.1.3.6.1.2.1.25.3.9.6,HOST-RESOURCES-TYPES::hrFSHPFS,,,,,,The file system type identifier used for OS/2's High Performance File System.
.1.3.6.1.2.1.25.3.9.7,HOST-RESOURCES-TYPES::hrFSHFS,,,,,,The file system type identifier used for the Macintosh Hierarchical File System.
.1.3.6.1.2.1.25.3.9.8,HOST-RESOURCES-TYPES::hrFSMFS,,,,,,The file system type identifier used for the Macintosh File System.
.1.3.6.1.2.1.25.3.9.9,HOST-RESOURCES-TYPES::hrFSNTFS,,,,,,The file system type identifier used for the Windows NT File System.
.1.3.6.1.2.1.25.3.9.10,HOST-RESOURCES-TYPES::hrFSVNode,,,,,,The file system type identifier used for the VNode File System.
.1.3.6.1.2.1.25.3.9.11,HOST-RESOURCES-TYPES::hrFSJournaled,,,,,,The file system type identifier used for the Journaled File System.
.1.3.6.1.2.1.25.3.9.12,HOST-RESOURCES-TYPES::hrFSiso9660,,,,,,The file system type identifier used for the ISO 9660 File System for CD's.
.1.3.6.1.2.1.25.3.9.13,HOST-RESOURCES-TYPES::hrFSRockRidge,,,,,,The file system type identifier used for the RockRidge File System for CD's.
.1.3.6.1.2.1.25.3.9.14,HOST-RESOURCES-TYPES::hrFSNFS,,,,,,The file system type identifier used for the NFS File System.
.1.3.6.1.2.1.25.3.9.15,HOST-RESOURCES-TYPES::hrFSNetware,,,,,,The file system type identifier used for the Netware File System.
.1.3.6.1.2.1.25.3.9.16,HOST-RESOURCES-TYPES::hrFSAFS,,,,,,The file system type identifier used for the Andrew File System.
.1.3.6.1.2.1.25.3.9.17,HOST-RESOURCES-TYPES::hrFSDFS,,,,,,The file system type identifier used for the OSF DCE Distributed File System.
.1.3.6.1.2.1.25.3.9.18,HOST-RESOURCES-TYPES::hrFSAppleshare,,,,,,The file system type identifier used for the AppleShare File System.
.1.3.6.1.2.1.25.3.9.19,HOST-RESOURCES-TYPES::hrFSRFS,,,,,,The file system type identifier used for the RFS File System.
.1.3.6.1.2.1.25.3.9.20,HOST-RESOURCES-TYPES::hrFSDGCFS,,,,,,The file system type identifier used for the Data General DGCFS.
.1.3.6.1.2.1.25.3.9.21,HOST-RESOURCES-TYPES::hrFSBFS,,,,,,The file system type identifier used for the SVR4 Boot File System.
.1.3.6.1.2.1.25.3.9.22,HOST-RESOURCES-TYPES::hrFSFAT32,,,,,,The file system type identifier used for the Windows FAT32 File System.
.1.3.6.1.2.1.25.3.9.23,HOST-RESOURCES-TYPES::hrFSLinuxExt2,,,,,,The file system type identifier used for the Linux EXT2 File System.
.1.3.6.1.2.1.25.4,HOST-RESOURCES-MIB::hrSWRun,,,,,,
.1.3.6.1.2.1.25.4.1,HOST-RESOURCES-MIB::hrSWOSIndex,Integer32,read-only,,current,,The value of the hrSWRunIndex for the hrSWRunEntry that represents the primary operating system running on this host. This object is useful for quickly and uniquely identifying that primary operating system.
.1.3.6.1.2.1.25.4.2,HOST-RESOURCES-MIB::hrSWRunTable,,not-accessible,,current,,The (conceptual) table of software running on the host.
.1.3.6.1.2.1.25.4.2.1,HOST-RESOURCES-MIB::hrSWRunEntry,,not-accessible,hrSWRunIndex,current,,A (conceptual) entry for one piece of software running on the host Note that because the installed software table only contains information for software stored locally on this host, not every piece of running software will be found in the installed software table. This is true of software that was loaded and run from a non-local source, such as a network-mounted file system. As an example of how objects in this table are named, an instance of the hrSWRunName object might be named hrSWRunName.1287
.1.3.6.1.2.1.25.4.2.1.1,HOST-RESOURCES-MIB::hrSWRunIndex,Integer32,read-only,,current,,A unique value for each piece of software running on the host. Wherever possible, this should be the system's native, unique identification number.
.1.3.6.1.2.1.25.4.2.1.2,HOST-RESOURCES-MIB::hrSWRunName,OCTET,read-only,,current,,A textual description of this running piece of software, including the manufacturer, revision, and the name by which it is commonly known. If this software was installed locally, this should be the same string as used in the corresponding hrSWInstalledName.
.1.3.6.1.2.1.25.4.2.1.3,HOST-RESOURCES-MIB::hrSWRunID,OBJECT,read-only,,current,,The product ID of this running piece of software.
.1.3.6.1.2.1.25.4.2.1.4,HOST-RESOURCES-MIB::hrSWRunPath,OCTET,read-only,,current,,A description of the location on long-term storage (e.g. a disk drive) from which this software was loaded.
.1.3.6.1.2.1.25.4.2.1.5,HOST-RESOURCES-MIB::hrSWRunParameters,OCTET,read-only,,current,,A description of the parameters supplied to this software when it was initially loaded.
.1.3.6.1.2.1.25.4.2.1.6,HOST-RESOURCES-MIB::hrSWRunType,INTEGER,read-only,,current,unknown(1):operatingSystem(2):deviceDriver(3):application(4),The type of this software.
.1.3.6.1.2.1.25.4.2.1.7,HOST-RESOURCES-MIB::hrSWRunStatus,INTEGER,read-write,,current,running(1):runnable(2):notRunnable(3):invalid(4),The status of this running piece of software. Setting this value to invalid(4) shall cause this software to stop running and to be unloaded. Sets to other values are not valid.
.1.3.6.1.2.1.25.5,HOST-RESOURCES-MIB::hrSWRunPerf,,,,,,
.1.3.6.1.2.1.25.5.1,HOST-RESOURCES-MIB::hrSWRunPerfTable,,not-accessible,,current,,The (conceptual) table of running software performance metrics.
.1.3.6.1.2.1.25.5.1.1,HOST-RESOURCES-MIB::hrSWRunPerfEntry,,not-accessible,,current,,A (conceptual) entry containing software performance metrics. As an example, an instance of the hrSWRunPerfCPU object might be named hrSWRunPerfCPU.1287
.1.3.6.1.2.1.25.5.1.1.1,HOST-RESOURCES-MIB::hrSWRunPerfCPU,Integer32,read-only,,current,,The number of centi-seconds of the total system's CPU resources consumed by this process. Note that on a multi-processor system, this value may increment by more than one centi-second in one centi-second of real (wall clock) time.
.1.3.6.1.2.1.25.5.1.1.2,HOST-RESOURCES-MIB::hrSWRunPerfMem,Integer32,read-only,,current,,The total amount of real system memory allocated to this process.
.1.3.6.1.2.1.25.6,HOST-RESOURCES-MIB::hrSWInstalled,,,,,,
.1.3.6.1.2.1.25.6.1,HOST-RESOURCES-MIB::hrSWInstalledLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when an entry in the hrSWInstalledTable was last added, renamed, or deleted. Because this table is likely to contain many entries, polling of this object allows a management station to determine when re-downloading of the table might be useful.
.1.3.6.1.2.1.25.6.2,HOST-RESOURCES-MIB::hrSWInstalledLastUpdateTime,TimeTicks,read-only,,current,,The value of sysUpTime when the hrSWInstalledTable was last completely updated. Because caching of this data will be a popular implementation strategy, retrieval of this object allows a management station to obtain a guarantee that no data in this table is older than the indicated time.
.1.3.6.1.2.1.25.6.3,HOST-RESOURCES-MIB::hrSWInstalledTable,,not-accessible,,current,,The (conceptual) table of software installed on this host.
.1.3.6.1.2.1.25.6.3.1,HOST-RESOURCES-MIB::hrSWInstalledEntry,,not-accessible,hrSWInstalledIndex,current,,A (conceptual) entry for a piece of software installed on this host. As an example of how objects in this table are named, an instance of the hrSWInstalledName object might be named hrSWInstalledName.96
.1.3.6.1.2.1.25.6.3.1.1,HOST-RESOURCES-MIB::hrSWInstalledIndex,Integer32,read-only,,current,,A unique value for each piece of software installed on the host. This value shall be in the range from 1 to the number of pieces of software installed on the host.
.1.3.6.1.2.1.25.6.3.1.2,HOST-RESOURCES-MIB::hrSWInstalledName,OCTET,read-only,,current,,A textual description of this installed piece of software, including the manufacturer, revision, the name by which it is commonly known, and optionally, its serial number.
.1.3.6.1.2.1.25.6.3.1.3,HOST-RESOURCES-MIB::hrSWInstalledID,OBJECT,read-only,,current,,The product ID of this installed piece of software.
.1.3.6.1.2.1.25.6.3.1.4,HOST-RESOURCES-MIB::hrSWInstalledType,INTEGER,read-only,,current,unknown(1):operatingSystem(2):deviceDriver(3):application(4),The type of this software.
.1.3.6.1.2.1.25.6.3.1.5,HOST-RESOURCES-MIB::hrSWInstalledDate,OCTET,read-only,,current,,The last-modification date of this application as it would appear in a directory listing. If this information is not known, then this variable shall have the value corresponding to January 1, year 0000, 00:00:00.0, which is encoded as (hex)'00 00 01 01 00 00 00 00'.
.1.3.6.1.2.1.25.7,HOST-RESOURCES-MIB::hrMIBAdminInfo,,,,,,
.1.3.6.1.2.1.25.7.1,HOST-RESOURCES-MIB::hostResourcesMibModule,,,,,,This MIB is for use in managing host systems. The term `host' is construed to mean any computer that communicates with other similar computers attached to the internet and that is directly used by one or more human beings. Although this MIB does not necessarily apply to devices whose primary function is communications services (e.g., terminal servers, routers, bridges, monitoring equipment), such relevance is not explicitly precluded. This MIB instruments attributes common to all internet hosts including, for example, both personal computers and systems that run variants of Unix.
.1.3.6.1.2.1.25.7.2,HOST-RESOURCES-MIB::hrMIBCompliances,,,,,,
.1.3.6.1.2.1.25.7.2.1,HOST-RESOURCES-MIB::hrMIBCompliance,,,,,,The requirements for conformance to the Host Resources MIB.
.1.3.6.1.2.1.25.7.3,HOST-RESOURCES-MIB::hrMIBGroups,,,,,,
.1.3.6.1.2.1.25.7.3.1,HOST-RESOURCES-MIB::hrSystemGroup,,,,,,The Host Resources System Group.
.1.3.6.1.2.1.25.7.3.2,HOST-RESOURCES-MIB::hrStorageGroup,,,,,,The Host Resources Storage Group.
.1.3.6.1.2.1.25.7.3.3,HOST-RESOURCES-MIB::hrDeviceGroup,,,,,,The Host Resources Device Group.
.1.3.6.1.2.1.25.7.3.4,HOST-RESOURCES-MIB::hrSWRunGroup,,,,,,The Host Resources Running Software Group.
.1.3.6.1.2.1.25.7.3.5,HOST-RESOURCES-MIB::hrSWRunPerfGroup,,,,,,The Host Resources Running Software Performance Group.
.1.3.6.1.2.1.25.7.3.6,HOST-RESOURCES-MIB::hrSWInstalledGroup,,,,,,The Host Resources Installed Software Group.
.1.3.6.1.2.1.25.7.4,HOST-RESOURCES-TYPES::hostResourcesTypesModule,,,,,,This MIB module registers type definitions for storage types, device types, and file system types. After the initial revision, this module will be maintained by IANA.
.1.3.6.1.2.1.26,IANA-MAU-MIB::snmpDot3MauMgt,,,,,,
.1.3.6.1.2.1.26.0,MAU-MIB::snmpDot3MauTraps,,,,,,
.1.3.6.1.2.1.26.0.1,MAU-MIB::rpMauJabberTrap,,,,,,This trap is sent whenever a managed repeater MAU enters the jabber state. The agent MUST throttle the generation of consecutive rpMauJabberTraps so that there is at least a five-second gap between them.
.1.3.6.1.2.1.26.0.2,MAU-MIB::ifMauJabberTrap,,,,,,This trap is sent whenever a managed interface MAU enters the jabber state. The agent MUST throttle the generation of consecutive ifMauJabberTraps so that there is at least a five-second gap between them.
.1.3.6.1.2.1.26.1,MAU-MIB::dot3RpMauBasicGroup,,,,,,
.1.3.6.1.2.1.26.1.1,MAU-MIB::rpMauTable,,not-accessible,,current,,Table of descriptive and status information about the MAU(s) attached to the ports of a repeater.
.1.3.6.1.2.1.26.1.1.1,MAU-MIB::rpMauEntry,,not-accessible,rpMauGroupIndex:rpMauPortIndex:rpMauIndex,current,,An entry in the table, containing information about a single MAU.
.1.3.6.1.2.1.26.1.1.1.1,MAU-MIB::rpMauGroupIndex,Integer32,read-only,,current,,This variable uniquely identifies the group containing the port to which the MAU described by this entry is connected. Note: In practice, a group will generally be a field-replaceable unit (i.e., module, card, or board) that can fit in the physical system enclosure, and the group number will correspond to a number marked on the physical enclosure. The group denoted by a particular value of this object is the same as the group denoted by the same value of rptrGroupIndex.
.1.3.6.1.2.1.26.1.1.1.2,MAU-MIB::rpMauPortIndex,Integer32,read-only,,current,,This variable uniquely identifies the repeater port within group rpMauGroupIndex to which the MAU described by this entry is connected.
.1.3.6.1.2.1.26.1.1.1.3,MAU-MIB::rpMauIndex,Integer32,read-only,,current,,This variable uniquely identifies the MAU described by this entry from among other MAUs connected to the same port (rpMauPortIndex).
.1.3.6.1.2.1.26.1.1.1.4,MAU-MIB::rpMauType,OBJECT,read-only,,current,,This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined in the IANA maintained IANA-MAU-MIB module, as OBJECT-IDENTITIES of dot3MauType. If the MAU type is unknown, the object identifier zeroDotZero is returned.
.1.3.6.1.2.1.26.1.1.1.5,MAU-MIB::rpMauStatus,INTEGER,read-write,,current,other(1):unknown(2):operational(3):standby(4):shutdown(5):reset(6),The current state of the MAU. This object MAY be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAU state. Some agents may not support setting the value of this object to some of the enumerated values. The value other(1) is returned if the MAU is in a state other than one of the states 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. A MAU in the operational(3) state is fully functional; it operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI to idle, and the media transmitter to idle or fault, if supported. Standby(4) mode only applies to link type MAUs. The state of rpMauMediaAvailable is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter, as though it were powered down or not connected. The MAU MAY return other(1) value for the rpMauJabberState and rpMauMediaAvailable objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power-on cycle of at least one-half second would. The agent is not required to return the value reset(6). Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state, except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state.
.1.3.6.1.2.1.26.1.1.1.6,MAU-MIB::rpMauMediaAvailable,INTEGER,read-only,,current,other(1):unknown(2):available(3):notAvailable(4):remoteFault(5):invalidSignal(6):remoteJabber(7):remoteLinkLoss(8):remoteTest(9):offline(10):autoNegError(11):pmdLinkFault(12):wisFrameLoss(13):wisSignalLoss(14):pcsLinkFault(15):excessiveBER(16):dxsLinkFault(17):pxsLinkFault(18):availableReduced(19):ready(20),This object identifies Media Available state of the MAU, complementary to the rpMauStatus. Values for the standard IEEE 802.3 Media Available states are defined in the IANA maintained IANA-MAU-MIB module, as IANAifMauMediaAvailable TC.
.1.3.6.1.2.1.26.1.1.1.7,MAU-MIB::rpMauMediaAvailableStateExits,Counter32,read-only,,current,,A count of the number of times that rpMauMediaAvailable for this MAU instance leaves the state available(3). Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of rptrMonitorPortLastChange.
.1.3.6.1.2.1.26.1.1.1.8,MAU-MIB::rpMauJabberState,INTEGER,read-only,,current,other(1):unknown(2):noJabber(3):jabbering(4),The value other(1) is returned if the jabber state is not 2, 3, or 4. The agent MUST always return other(1) for MAU type dot3MauTypeAUI. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. If the MAU is not jabbering the agent returns noJabber(3). This is the 'normal' state. If the MAU is in jabber state the agent returns the jabbering(4) value.
.1.3.6.1.2.1.26.1.1.1.9,MAU-MIB::rpMauJabberingStateEnters,Counter32,read-only,,current,,A count of the number of times that mauJabberState for this MAU instance enters the state jabbering(4). For MAUs of type dot3MauTypeAUI, dot3MauType100BaseT4, dot3MauType100BaseTX, dot3MauType100BaseFX, and all 1000Mbps types, this counter will always indicate zero. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of rptrMonitorPortLastChange.
.1.3.6.1.2.1.26.1.1.1.10,MAU-MIB::rpMauFalseCarriers,Counter32,read-only,,current,,A count of the number of false carrier events during IDLE in 100BASE-X links. This counter does not increment at the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100 ms until the next carrier event. This counter increments only for MAUs of type dot3MauType100BaseT4, dot3MauType100BaseTX, dot3MauType100BaseFX, and all 1000Mbps types. For all other MAU types, this counter will always indicate zero. The approximate minimum time for rollover of this counter is 7.4 hours. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of rptrMonitorPortLastChange.
.1.3.6.1.2.1.26.1.2,MAU-MIB::rpJackTable,,not-accessible,,current,,Information about the external jacks attached to MAUs attached to the ports of a repeater.
.1.3.6.1.2.1.26.1.2.1,MAU-MIB::rpJackEntry,,not-accessible,rpMauGroupIndex:rpMauPortIndex:rpMauIndex:rpJackIndex,current,,An entry in the table, containing information about a particular jack.
.1.3.6.1.2.1.26.1.2.1.1,MAU-MIB::rpJackIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU (rpMauIndex).
.1.3.6.1.2.1.26.1.2.1.2,MAU-MIB::rpJackType,INTEGER,read-only,,current,other(1):rj45(2):rj45S(3):db9(4):bnc(5):fAUI(6):mAUI(7):fiberSC(8):fiberMIC(9):fiberST(10):telco(11):mtrj(12):hssdc(13):fiberLC(14):cx4(15):sfpPlusDA(16),The jack connector type, as it appears on the outside of the system.
.1.3.6.1.2.1.26.2,MAU-MIB::dot3IfMauBasicGroup,,,,,,
.1.3.6.1.2.1.26.2.1,MAU-MIB::ifMauTable,,not-accessible,,current,,Table of descriptive and status information about MAU(s) attached to an interface.
.1.3.6.1.2.1.26.2.1.1,MAU-MIB::ifMauEntry,,not-accessible,ifMauIfIndex:ifMauIndex,current,,An entry in the table, containing information about a single MAU.
.1.3.6.1.2.1.26.2.1.1.1,MAU-MIB::ifMauIfIndex,Integer32,read-only,,current,,This variable uniquely identifies the interface to which the MAU described by this entry is connected.
.1.3.6.1.2.1.26.2.1.1.2,MAU-MIB::ifMauIndex,Integer32,read-only,,current,,This variable uniquely identifies the MAU described by this entry from among other MAUs connected to the same interface (ifMauIfIndex).
.1.3.6.1.2.1.26.2.1.1.3,MAU-MIB::ifMauType,OBJECT,read-only,,current,,This object identifies the MAU type. Values for standard IEEE 802.3 MAU types are defined in the IANA maintained IANA-MAU-MIB module, as OBJECT-IDENTITIES of dot3MauType. If the MAU type is unknown, the object identifier zeroDotZero is returned. This object represents the operational type of the MAU, as determined by either 1) the result of the auto-negotiation function or 2) if auto-negotiation is not enabled or is not implemented for this MAU, by the value of the object ifMauDefaultType. In case 2), a set to the object ifMauDefaultType will force the MAU into the new operating mode.
.1.3.6.1.2.1.26.2.1.1.4,MAU-MIB::ifMauStatus,INTEGER,read-write,,current,other(1):unknown(2):operational(3):standby(4):shutdown(5):reset(6),The current state of the MAU. This object MAY be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAU state. Some agents may not support setting the value of this object to some of the enumerated values. The value other(1) is returned if the MAU is in a state other than one of the states 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. A MAU in the operational(3) state is fully functional; it operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI to idle and the media transmitter to idle or fault, if supported. Standby(4) mode only applies to link type MAUs. The state of ifMauMediaAvailable is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter, as though it were powered down or not connected. The MAU MAY return other(1) value for the ifMauJabberState and ifMauMediaAvailable objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power-on cycle of at least one-half second would. The agent is not required to return the value reset(6). Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state, except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state.
.1.3.6.1.2.1.26.2.1.1.5,MAU-MIB::ifMauMediaAvailable,INTEGER,read-only,,current,other(1):unknown(2):available(3):notAvailable(4):remoteFault(5):invalidSignal(6):remoteJabber(7):remoteLinkLoss(8):remoteTest(9):offline(10):autoNegError(11):pmdLinkFault(12):wisFrameLoss(13):wisSignalLoss(14):pcsLinkFault(15):excessiveBER(16):dxsLinkFault(17):pxsLinkFault(18):availableReduced(19):ready(20),This object identifies Media Available state of the MAU, complementary to the ifMauStatus. Values for the standard IEEE 802.3 Media Available states are defined in the IANA maintained IANA-MAU-MIB module, as IANAifMauMediaAvailable TC.
.1.3.6.1.2.1.26.2.1.1.6,MAU-MIB::ifMauMediaAvailableStateExits,Counter32,read-only,,current,,A count of the number of times that ifMauMediaAvailable for this MAU instance leaves the state available(3). Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.26.2.1.1.7,MAU-MIB::ifMauJabberState,INTEGER,read-only,,current,other(1):unknown(2):noJabber(3):jabbering(4),The value other(1) is returned if the jabber state is not 2, 3, or 4. The agent MUST always return other(1) for MAU type dot3MauTypeAUI. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. If the MAU is not jabbering the agent returns noJabber(3). This is the 'normal' state. If the MAU is in jabber state the agent returns the jabbering(4) value.
.1.3.6.1.2.1.26.2.1.1.8,MAU-MIB::ifMauJabberingStateEnters,Counter32,read-only,,current,,A count of the number of times that mauJabberState for this MAU instance enters the state jabbering(4). This counter will always indicate zero for MAUs of type dot3MauTypeAUI and those of speeds above 10Mbps. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.26.2.1.1.9,MAU-MIB::ifMauFalseCarriers,Counter32,read-only,,current,,A count of the number of false carrier events during IDLE in 100BASE-X and 1000BASE-X links. For all other MAU types, this counter will always indicate zero. This counter does not increment at the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100 ms for 100BASE-X and once per 10us for 1000BASE-X until the next CarrierEvent. This counter can roll over very quickly. A management station is advised to poll the ifMauHCFalseCarriers instead of this counter in order to avoid loss of information. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.26.2.1.1.10,MAU-MIB::ifMauTypeList,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object has been deprecated in favour of ifMauTypeListBits. A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. The value is a sum that initially takes the value zero. Then, for each type capability of this MAU, 2 raised to the power noted below is added to the sum. For example, a MAU that has the capability to be only 10BASE-T would have a value of 512 (2**9). In contrast, a MAU that supports both 10Base-T (full duplex) and 100BASE-TX (full duplex) would have a value of ((2**11) + (2**16)), or 67584. The powers of 2 assigned to the capabilities are these: Power Capability 0 other or unknown 1 AUI 2 10BASE-5 3 FOIRL 4 10BASE-2 5 10BASE-T duplex mode unknown 6 10BASE-FP 7 10BASE-FB 8 10BASE-FL duplex mode unknown 9 10BROAD36 10 10BASE-T half duplex mode 11 10BASE-T full duplex mode 12 10BASE-FL half duplex mode 13 10BASE-FL full duplex mode 14 100BASE-T4 15 100BASE-TX half duplex mode 16 100BASE-TX full duplex mode 17 100BASE-FX half duplex mode 18 100BASE-FX full duplex mode 19 100BASE-T2 half duplex mode 20 100BASE-T2 full duplex mode If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapability.
.1.3.6.1.2.1.26.2.1.1.11,MAU-MIB::ifMauDefaultType,OBJECT,read-write,,current,,This object identifies the default administrative baseband MAU type to be used in conjunction with the operational MAU type denoted by ifMauType. The set of possible values for this object is the same as the set defined for the ifMauType object. This object represents the administratively-configured type of the MAU. If auto-negotiation is not enabled or is not implemented for this MAU, the value of this object determines the operational type of the MAU. In this case, a set to this object will force the MAU into the specified operating mode. If auto-negotiation is implemented and enabled for this MAU, the operational type of the MAU is determined by auto-negotiation, and the value of this object denotes the type to which the MAU will automatically revert if/when auto-negotiation is later disabled. NOTE TO IMPLEMENTORS: It may be necessary to provide for underlying hardware implementations which do not follow the exact behavior specified above. In particular, when ifMauAutoNegAdminStatus transitions from enabled to disabled, the agent implementation MUST ensure that the operational type of the MAU (as reported by ifMauType) correctly transitions to the value specified by this object, rather than continuing to operate at the value earlier determined by the auto-negotiation function.
.1.3.6.1.2.1.26.2.1.1.12,MAU-MIB::ifMauAutoNegSupported,INTEGER,read-only,,current,true(1):false(2),This object indicates whether or not auto-negotiation is supported on this MAU.
.1.3.6.1.2.1.26.2.1.1.13,MAU-MIB::ifMauTypeListBits,BITS,read-only,,current,bOther(0):bAUI(1):b10base5(2):bFoirl(3):b10base2(4):b10baseT(5):b10baseFP(6):b10baseFB(7):b10baseFL(8):b10broad36(9):b10baseTHD(10):b10baseTFD(11):b10baseFLHD(12):b10baseFLFD(13):b100baseT4(14):b100baseTXHD(15):b100baseTXFD(16):b100baseFXHD(17):b100baseFXFD(18):b100baseT2HD(19):b100baseT2FD(20):b1000baseXHD(21):b1000baseXFD(22):b1000baseLXHD(23):b1000baseLXFD(24):b1000baseSXHD(25):b1000baseSXFD(26):b1000baseCXHD(27):b1000baseCXFD(28):b1000baseTHD(29):b1000baseTFD(30):b10GbaseX(31):b10GbaseLX4(32):b10GbaseR(33):b10GbaseER(34):b10GbaseLR(35):b10GbaseSR(36):b10GbaseW(37):b10GbaseEW(38):b10GbaseLW(39):b10GbaseSW(40):b10GbaseCX4(41):b2BaseTL(42):b10PassTS(43):b100BaseBX10D(44):b100BaseBX10U(45):b100BaseLX10(46):b1000BaseBX10D(47):b1000BaseBX10U(48):b1000BaseLX10(49):b1000BasePX10D(50):b1000BasePX10U(51):b1000BasePX20D(52):b1000BasePX20U(53):b10GbaseT(54):b10GbaseLRM(55):b1000baseKX(56):b10GbaseKX4(57):b10GbaseKR(58):b10G1GbasePRXD1(59):b10G1GbasePRXD2(60):b10G1GbasePRXD3(61):b10G1GbasePRXU1(62):b10G1GbasePRXU2(63):b10G1GbasePRXU3(64):b10GbasePRD1(65):b10GbasePRD2(66):b10GbasePRD3(67):b10GbasePRU1(68):b10GbasePRU3(69):b40GbaseKR4(70):b40GbaseCR4(71):b40GbaseSR4(72):b40GbaseFR(73):b40GbaseLR4(74):b100GbaseCR10(75):b100GbaseSR10(76):b100GbaseLR4(77):b100GbaseER4(78):b1000baseT1(79):b1000basePX30D(80):b1000basePX30U(81):b1000basePX40D(82):b1000basePX40U(83):b10G1GbasePRXD4(84):b10G1GbasePRXU4(85):b10GbasePRD4(86):b10GbasePRU4(87):b25GbaseCR(88):b25GbaseCRS(89):b25GbaseKR(90):b25GbaseKRS(91):b25GbaseR(92):b25GbaseSR(93):b25GbaseT(94):b40GbaseER4(95):b40GbaseR(96):b40GbaseT(97):b100GbaseCR4(98):b100GbaseKR4(99):b100GbaseKP4(100):b100GbaseR(101):b100GbaseSR4(102),A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapabilityBits. Note that this MAU may be capable of operating as a MAU type that is beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for standard capabilities that are listed in the IANAifMauTypeListBits TC.
.1.3.6.1.2.1.26.2.1.1.14,MAU-MIB::ifMauHCFalseCarriers,Counter64,read-only,,current,,A count of the number of false carrier events during IDLE in 100BASE-X and 1000BASE-X links. For all other MAU types, this counter will always indicate zero. This counter does not increment at the symbol rate. This counter is a 64-bit version of ifMauFalseCarriers. Since the 32-bit version of this counter can roll over very quickly, management stations are advised to poll the 64-bit version instead, in order to avoid loss of information. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.26.2.2,MAU-MIB::ifJackTable,,not-accessible,,current,,Information about the external jacks attached to MAUs attached to an interface.
.1.3.6.1.2.1.26.2.2.1,MAU-MIB::ifJackEntry,,not-accessible,ifMauIfIndex:ifMauIndex:ifJackIndex,current,,An entry in the table, containing information about a particular jack.
.1.3.6.1.2.1.26.2.2.1.1,MAU-MIB::ifJackIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the jack described by this entry from among other jacks attached to the same MAU.
.1.3.6.1.2.1.26.2.2.1.2,MAU-MIB::ifJackType,INTEGER,read-only,,current,other(1):rj45(2):rj45S(3):db9(4):bnc(5):fAUI(6):mAUI(7):fiberSC(8):fiberMIC(9):fiberST(10):telco(11):mtrj(12):hssdc(13):fiberLC(14):cx4(15):sfpPlusDA(16),The jack connector type, as it appears on the outside of the system.
.1.3.6.1.2.1.26.3,MAU-MIB::dot3BroadMauBasicGroup,,,,,,
.1.3.6.1.2.1.26.3.1,MAU-MIB::broadMauBasicTable,,not-accessible,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This entire table has been deprecated. There have been no reported implementations of this table, and it is unlikely that there ever will be. IEEE recommends that broadband MAU types should not be used for new installations. Table of descriptive and status information about the broadband MAUs connected to interfaces.
.1.3.6.1.2.1.26.3.1.1,MAU-MIB::broadMauBasicEntry,,not-accessible,broadMauIfIndex:broadMauIndex,deprecated,,********* THIS OBJECT IS DEPRECATED ********** An entry in the table, containing information about a single broadband MAU.
.1.3.6.1.2.1.26.3.1.1.1,MAU-MIB::broadMauIfIndex,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This variable uniquely identifies the interface to which the MAU described by this entry is connected.
.1.3.6.1.2.1.26.3.1.1.2,MAU-MIB::broadMauIndex,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This variable uniquely identifies the MAU connected to interface broadMauIfIndex that is described by this entry.
.1.3.6.1.2.1.26.3.1.1.3,MAU-MIB::broadMauXmtRcvSplitType,INTEGER,read-only,,deprecated,other(1):single(2):dual(3),********* THIS OBJECT IS DEPRECATED ********** This object indicates the type of frequency multiplexing/cabling system used to separate the transmit and receive paths for the 10BROAD36 MAU. The value other(1) is returned if the split type is not either single or dual. The value single(2) indicates a single cable system. The value dual(3) indicates a dual cable system, offset normally zero.
.1.3.6.1.2.1.26.3.1.1.4,MAU-MIB::broadMauXmtCarrierFreq,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This variable indicates the transmit carrier frequency of the 10BROAD36 MAU in MHz/4; that is, in units of 250 kHz.
.1.3.6.1.2.1.26.3.1.1.5,MAU-MIB::broadMauTranslationFreq,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This variable indicates the translation offset frequency of the 10BROAD36 MAU in MHz/4; that is, in units of 250 kHz.
.1.3.6.1.2.1.26.4,IANA-MAU-MIB::dot3MauType,,,,,,
.1.3.6.1.2.1.26.4.1,IANA-MAU-MIB::dot3MauTypeAUI,,,,,,no internal MAU, view from AUI
.1.3.6.1.2.1.26.4.2,IANA-MAU-MIB::dot3MauType10Base5,,,,,,thick coax MAU
.1.3.6.1.2.1.26.4.3,IANA-MAU-MIB::dot3MauTypeFoirl,,,,,,FOIRL MAU
.1.3.6.1.2.1.26.4.4,IANA-MAU-MIB::dot3MauType10Base2,,,,,,thin coax MAU
.1.3.6.1.2.1.26.4.5,IANA-MAU-MIB::dot3MauType10BaseT,,,,,,UTP MAU. Note that it is strongly recommended that agents return either dot3MauType10BaseTHD or dot3MauType10BaseTFD if the duplex mode is known. However, management applications should be prepared to receive this MAU type value from older agent implementations.
.1.3.6.1.2.1.26.4.6,IANA-MAU-MIB::dot3MauType10BaseFP,,,,,,passive fiber MAU
.1.3.6.1.2.1.26.4.7,IANA-MAU-MIB::dot3MauType10BaseFB,,,,,,sync fiber MAU
.1.3.6.1.2.1.26.4.8,IANA-MAU-MIB::dot3MauType10BaseFL,,,,,,async fiber MAU. Note that it is strongly recommended that agents return either dot3MauType10BaseFLHD or dot3MauType10BaseFLFD if the duplex mode is known. However, management applications should be prepared to receive this MAU type value from older agent implementations.
.1.3.6.1.2.1.26.4.9,IANA-MAU-MIB::dot3MauType10Broad36,,,,,,broadband DTE MAU. Note that 10BROAD36 MAUs can be attached to interfaces but not to repeaters.
.1.3.6.1.2.1.26.4.10,IANA-MAU-MIB::dot3MauType10BaseTHD,,,,,,UTP MAU, half duplex mode
.1.3.6.1.2.1.26.4.11,IANA-MAU-MIB::dot3MauType10BaseTFD,,,,,,UTP MAU, full duplex mode
.1.3.6.1.2.1.26.4.12,IANA-MAU-MIB::dot3MauType10BaseFLHD,,,,,,async fiber MAU, half duplex mode
.1.3.6.1.2.1.26.4.13,IANA-MAU-MIB::dot3MauType10BaseFLFD,,,,,,async fiber MAU, full duplex mode
.1.3.6.1.2.1.26.4.14,IANA-MAU-MIB::dot3MauType100BaseT4,,,,,,4 pair category 3 UTP
.1.3.6.1.2.1.26.4.15,IANA-MAU-MIB::dot3MauType100BaseTXHD,,,,,,2 pair category 5 UTP, half duplex mode
.1.3.6.1.2.1.26.4.16,IANA-MAU-MIB::dot3MauType100BaseTXFD,,,,,,2 pair category 5 UTP, full duplex mode
.1.3.6.1.2.1.26.4.17,IANA-MAU-MIB::dot3MauType100BaseFXHD,,,,,,X fiber over PMT, half duplex mode
.1.3.6.1.2.1.26.4.18,IANA-MAU-MIB::dot3MauType100BaseFXFD,,,,,,X fiber over PMT, full duplex mode
.1.3.6.1.2.1.26.4.19,IANA-MAU-MIB::dot3MauType100BaseT2HD,,,,,,2 pair category 3 UTP, half duplex mode
.1.3.6.1.2.1.26.4.20,IANA-MAU-MIB::dot3MauType100BaseT2FD,,,,,,2 pair category 3 UTP, full duplex mode
.1.3.6.1.2.1.26.4.21,IANA-MAU-MIB::dot3MauType1000BaseXHD,,,,,,PCS/PMA, unknown PMD, half duplex mode
.1.3.6.1.2.1.26.4.22,IANA-MAU-MIB::dot3MauType1000BaseXFD,,,,,,PCS/PMA, unknown PMD, full duplex mode
.1.3.6.1.2.1.26.4.23,IANA-MAU-MIB::dot3MauType1000BaseLXHD,,,,,,Fiber over long-wavelength laser, half duplex mode
.1.3.6.1.2.1.26.4.24,IANA-MAU-MIB::dot3MauType1000BaseLXFD,,,,,,Fiber over long-wavelength laser, full duplex mode
.1.3.6.1.2.1.26.4.25,IANA-MAU-MIB::dot3MauType1000BaseSXHD,,,,,,Fiber over short-wavelength laser, half duplex mode
.1.3.6.1.2.1.26.4.26,IANA-MAU-MIB::dot3MauType1000BaseSXFD,,,,,,Fiber over short-wavelength laser, full duplex mode
.1.3.6.1.2.1.26.4.27,IANA-MAU-MIB::dot3MauType1000BaseCXHD,,,,,,Copper over 150-Ohm balanced cable, half duplex mode
.1.3.6.1.2.1.26.4.28,IANA-MAU-MIB::dot3MauType1000BaseCXFD,,,,,,Copper over 150-Ohm balanced cable, full duplex mode
.1.3.6.1.2.1.26.4.29,IANA-MAU-MIB::dot3MauType1000BaseTHD,,,,,,Four-pair Category 5 UTP, half duplex mode
.1.3.6.1.2.1.26.4.30,IANA-MAU-MIB::dot3MauType1000BaseTFD,,,,,,Four-pair Category 5 UTP, full duplex mode
.1.3.6.1.2.1.26.4.31,IANA-MAU-MIB::dot3MauType10GigBaseX,,,,,,X PCS/PMA, unknown PMD.
.1.3.6.1.2.1.26.4.32,IANA-MAU-MIB::dot3MauType10GigBaseLX4,,,,,,X fiber over WWDM optics
.1.3.6.1.2.1.26.4.33,IANA-MAU-MIB::dot3MauType10GigBaseR,,,,,,R PCS/PMA, unknown PMD.
.1.3.6.1.2.1.26.4.34,IANA-MAU-MIB::dot3MauType10GigBaseER,,,,,,R fiber over 1550 nm optics
.1.3.6.1.2.1.26.4.35,IANA-MAU-MIB::dot3MauType10GigBaseLR,,,,,,R fiber over 1310 nm optics
.1.3.6.1.2.1.26.4.36,IANA-MAU-MIB::dot3MauType10GigBaseSR,,,,,,R fiber over 850 nm optics
.1.3.6.1.2.1.26.4.37,IANA-MAU-MIB::dot3MauType10GigBaseW,,,,,,W PCS/PMA, unknown PMD.
.1.3.6.1.2.1.26.4.38,IANA-MAU-MIB::dot3MauType10GigBaseEW,,,,,,W fiber over 1550 nm optics
.1.3.6.1.2.1.26.4.39,IANA-MAU-MIB::dot3MauType10GigBaseLW,,,,,,W fiber over 1310 nm optics
.1.3.6.1.2.1.26.4.40,IANA-MAU-MIB::dot3MauType10GigBaseSW,,,,,,W fiber over 850 nm optics
.1.3.6.1.2.1.26.4.41,IANA-MAU-MIB::dot3MauType10GigBaseCX4,,,,,,X copper over 8 pair 100-Ohm balanced cable
.1.3.6.1.2.1.26.4.42,IANA-MAU-MIB::dot3MauType2BaseTL,,,,,,Voice grade UTP copper, up to 2700m, optional PAF
.1.3.6.1.2.1.26.4.43,IANA-MAU-MIB::dot3MauType10PassTS,,,,,,Voice grade UTP copper, up to 750m, optional PAF
.1.3.6.1.2.1.26.4.44,IANA-MAU-MIB::dot3MauType100BaseBX10D,,,,,,One single-mode fiber OLT, long wavelength, 10km
.1.3.6.1.2.1.26.4.45,IANA-MAU-MIB::dot3MauType100BaseBX10U,,,,,,One single-mode fiber ONU, long wavelength, 10km
.1.3.6.1.2.1.26.4.46,IANA-MAU-MIB::dot3MauType100BaseLX10,,,,,,Two single-mode fibers, long wavelength, 10km
.1.3.6.1.2.1.26.4.47,IANA-MAU-MIB::dot3MauType1000BaseBX10D,,,,,,One single-mode fiber OLT, long wavelength, 10km
.1.3.6.1.2.1.26.4.48,IANA-MAU-MIB::dot3MauType1000BaseBX10U,,,,,,One single-mode fiber ONU, long wavelength, 10km
.1.3.6.1.2.1.26.4.49,IANA-MAU-MIB::dot3MauType1000BaseLX10,,,,,,Two sigle-mode fiber, long wavelength, 10km
.1.3.6.1.2.1.26.4.50,IANA-MAU-MIB::dot3MauType1000BasePX10D,,,,,,One single-mode fiber EPON OLT, 10km
.1.3.6.1.2.1.26.4.51,IANA-MAU-MIB::dot3MauType1000BasePX10U,,,,,,One single-mode fiber EPON ONU, 10km
.1.3.6.1.2.1.26.4.52,IANA-MAU-MIB::dot3MauType1000BasePX20D,,,,,,One single-mode fiber EPON OLT, 20km
.1.3.6.1.2.1.26.4.53,IANA-MAU-MIB::dot3MauType1000BasePX20U,,,,,,One single-mode fiber EPON ONU, 20km
.1.3.6.1.2.1.26.4.54,IANA-MAU-MIB::dot3MauType10GbaseT,,,,,,Four-pair Category 6A or better, full duplex mode only
.1.3.6.1.2.1.26.4.55,IANA-MAU-MIB::dot3MauType10GbaseLRM,,,,,,R multimode fiber over 1310 nm optics
.1.3.6.1.2.1.26.4.56,IANA-MAU-MIB::dot3MauType1000baseKX,,,,,,X backplane, full duplex mode only
.1.3.6.1.2.1.26.4.57,IANA-MAU-MIB::dot3MauType10GbaseKX4,,,,,,4 lane X backplane, full duplex mode only
.1.3.6.1.2.1.26.4.58,IANA-MAU-MIB::dot3MauType10GbaseKR,,,,,,R backplane, full duplex mode only
.1.3.6.1.2.1.26.4.59,IANA-MAU-MIB::dot3MauType10G1GbasePRXD1,,,,,,One single-mode fiber asymmetric-rate EPON OLT, supporting low power budget (PRX10)
.1.3.6.1.2.1.26.4.60,IANA-MAU-MIB::dot3MauType10G1GbasePRXD2,,,,,,One single-mode fiber asymmetric-rate EPON OLT, supporting medium power budget (PRX20)
.1.3.6.1.2.1.26.4.61,IANA-MAU-MIB::dot3MauType10G1GbasePRXD3,,,,,,One single-mode fiber asymmetric-rate EPON OLT, supporting high power budget (PRX30)
.1.3.6.1.2.1.26.4.62,IANA-MAU-MIB::dot3MauType10G1GbasePRXU1,,,,,,One single-mode fiber asymmetric-rate EPON ONU, supporting low power budget (PRX10)
.1.3.6.1.2.1.26.4.63,IANA-MAU-MIB::dot3MauType10G1GbasePRXU2,,,,,,One single-mode fiber asymmetric-rate EPON ONU, supporting medium power budget (PRX20)
.1.3.6.1.2.1.26.4.64,IANA-MAU-MIB::dot3MauType10G1GbasePRXU3,,,,,,One single-mode fiber asymmetric-rate EPON ONU, supporting high power budget (PRX30)
.1.3.6.1.2.1.26.4.65,IANA-MAU-MIB::dot3MauType10GbasePRD1,,,,,,One single-mode fiber symmetric-rate EPON OLT, supporting low power budget (PR10)
.1.3.6.1.2.1.26.4.66,IANA-MAU-MIB::dot3MauType10GbasePRD2,,,,,,One single-mode fiber symmetric-rate EPON OLT, supporting medium power budget (PR20)
.1.3.6.1.2.1.26.4.67,IANA-MAU-MIB::dot3MauType10GbasePRD3,,,,,,One single-mode fiber symmetric-rate EPON OLT, supporting high power budget (PR30)
.1.3.6.1.2.1.26.4.68,IANA-MAU-MIB::dot3MauType10GbasePRU1,,,,,,One single-mode fiber symmetric-rate EPON ONU, supporting low and medium power budget (PR10 and PR20)
.1.3.6.1.2.1.26.4.69,IANA-MAU-MIB::dot3MauType10GbasePRU3,,,,,,One single-mode fiber symmetric-rate EPON ONU, supporting high power budget (PR30)
.1.3.6.1.2.1.26.4.70,IANA-MAU-MIB::dot3MauType40GbaseKR4,,,,,,40GBASE-R PCS/PMA over an electrical backplane
.1.3.6.1.2.1.26.4.71,IANA-MAU-MIB::dot3MauType40GbaseCR4,,,,,,40GBASE-R PCS/PMA over 4 lane shielded copper balanced cable
.1.3.6.1.2.1.26.4.72,IANA-MAU-MIB::dot3MauType40GbaseSR4,,,,,,40GBASE-R PCS/PMA over 4 lane multimode fiber
.1.3.6.1.2.1.26.4.73,IANA-MAU-MIB::dot3MauType40GbaseFR,,,,,,40GBASE-R PCS/PMA over single mode fiber
.1.3.6.1.2.1.26.4.74,IANA-MAU-MIB::dot3MauType40GbaseLR4,,,,,,40GBASE-R PCS/PMA over 4 WDM lane single mode fiber
.1.3.6.1.2.1.26.4.75,IANA-MAU-MIB::dot3MauType100GbaseCR10,,,,,,100GBASE-R PCS/PMA over 10 lane shielded copper balanced cable
.1.3.6.1.2.1.26.4.76,IANA-MAU-MIB::dot3MauType100GbaseSR10,,,,,,100GBASE-R PCS/PMA over 10 lane multimode fiber
.1.3.6.1.2.1.26.4.77,IANA-MAU-MIB::dot3MauType100GbaseLR4,,,,,,100GBASE-R PCS/PMA over 4 WDM lane single mode fiber, long reach
.1.3.6.1.2.1.26.4.78,IANA-MAU-MIB::dot3MauType100GbaseER4,,,,,,100GBASE-R PCS/PMA over 4 WDM lane single mode fiber PMD, extended reach
.1.3.6.1.2.1.26.4.79,IANA-MAU-MIB::dot3MauType1000baseT1,,,,,,1000BASE-T1 single balanced twisted-pair copper cabling PHY
.1.3.6.1.2.1.26.4.80,IANA-MAU-MIB::dot3MauType1000basePX30D,,,,,,One single-mode fiber EPON OLT, 20km, 1:32 split ratio
.1.3.6.1.2.1.26.4.81,IANA-MAU-MIB::dot3MauType1000basePX30U,,,,,,One single-mode fiber EPON ONU, 20km, 1:32 split ratio
.1.3.6.1.2.1.26.4.82,IANA-MAU-MIB::dot3MauType1000basePX40D,,,,,,One single-mode fiber EPON OLT, 20km, 1:64 split ratio
.1.3.6.1.2.1.26.4.83,IANA-MAU-MIB::dot3MauType1000basePX40U,,,,,,One single-mode fiber EPON ONU, 20km, 1:64 split ratio
.1.3.6.1.2.1.26.4.84,IANA-MAU-MIB::dot3MauType10G1GbasePRXD4,,,,,,One single-mode fiber asymmetric-rate EPON OLT, supporting extended power budget (PRX40)
.1.3.6.1.2.1.26.4.85,IANA-MAU-MIB::dot3MauType10G1GbasePRXU4,,,,,,One single-mode fiber asymmetric-rate EPON ONU, supporting extended power budget (PRX40)
.1.3.6.1.2.1.26.4.86,IANA-MAU-MIB::dot3MauType10GbasePRD4,,,,,,One single-mode fiber symmetric-rate EPON OLT, supporting extended power budget (PR40)
.1.3.6.1.2.1.26.4.87,IANA-MAU-MIB::dot3MauType10GbasePRU4,,,,,,One single-mode fiber symmetric-rate EPON ONU, supporting extended power budget (PR40)
.1.3.6.1.2.1.26.4.88,IANA-MAU-MIB::dot3MauType25GbaseCR,,,,,,25GBASE-R PCS/PMA over shielded balanced copper cable
.1.3.6.1.2.1.26.4.89,IANA-MAU-MIB::dot3MauType25GbaseCRS,,,,,,25GBASE-R PCS/PMA over shielded balanced copper cable without RS-FEC
.1.3.6.1.2.1.26.4.90,IANA-MAU-MIB::dot3MauType25GbaseKR,,,,,,25GBASE-R PCS/PMA over an electrical backplane
.1.3.6.1.2.1.26.4.91,IANA-MAU-MIB::dot3MauType25GbaseKRS,,,,,,25GBASE-R PCS/PMA over an electrical backplane without RS-FEC
.1.3.6.1.2.1.26.4.92,IANA-MAU-MIB::dot3MauType25GbaseR,,,,,,25GBASE-R PCS/PMA over undefined PMD
.1.3.6.1.2.1.26.4.93,IANA-MAU-MIB::dot3MauType25GbaseSR,,,,,,25GBASE-R PCS/PMA over multimode fiber
.1.3.6.1.2.1.26.4.94,IANA-MAU-MIB::dot3MauType25GbaseT,,,,,,Four-pair twisted-pair balanced copper cabling
.1.3.6.1.2.1.26.4.95,IANA-MAU-MIB::dot3MauType40GbaseER4,,,,,,40GBASE-R PCS/PMA over 4 WDM lane single mode fiber
.1.3.6.1.2.1.26.4.96,IANA-MAU-MIB::dot3MauType40GbaseR,,,,,,40GBASE-R PCS as over undefined PMA/PMD
.1.3.6.1.2.1.26.4.97,IANA-MAU-MIB::dot3MauType40GbaseT,,,,,,Four-pair twisted-pair balanced copper cabling
.1.3.6.1.2.1.26.4.98,IANA-MAU-MIB::dot3MauType100GbaseCR4,,,,,, 100GBASE-R PCS/PMA over 4 lane shielded copper balanced cable
.1.3.6.1.2.1.26.4.99,IANA-MAU-MIB::dot3MauType100GbaseKR4,,,,,,100GBASE-R PCS/PMA over an electrical backplane
.1.3.6.1.2.1.26.4.100,IANA-MAU-MIB::dot3MauType100GbaseKP4,,,,,,100GBASE-P PCS/PMA over an electrical backplane PMD
.1.3.6.1.2.1.26.4.101,IANA-MAU-MIB::dot3MauType100GbaseR,,,,,,100GBASE-R Multi-lane PCS over undefined PMA/PMD
.1.3.6.1.2.1.26.4.102,IANA-MAU-MIB::dot3MauType100GbaseSR4,,,,,,100GBASE-R PCS/PMA over 4 lane multimode fiber
.1.3.6.1.2.1.26.5,MAU-MIB::dot3IfMauAutoNegGroup,,,,,,
.1.3.6.1.2.1.26.5.1,MAU-MIB::ifMauAutoNegTable,,not-accessible,,current,,Configuration and status objects for the auto-negotiation function of MAUs attached to interfaces. The ifMauAutoNegTable applies to systems in which auto-negotiation is supported on one or more MAUs attached to interfaces. Note that if auto-negotiation is present and enabled, the ifMauType object reflects the result of the auto-negotiation function.
.1.3.6.1.2.1.26.5.1.1,MAU-MIB::ifMauAutoNegEntry,,not-accessible,ifMauIfIndex:ifMauIndex,current,,An entry in the table, containing configuration and status information for the auto-negotiation function of a particular MAU.
.1.3.6.1.2.1.26.5.1.1.1,MAU-MIB::ifMauAutoNegAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),Setting this object to enabled(1) will cause the interface that has the auto-negotiation signaling ability to be enabled. If the value of this object is disabled(2) then the interface will act as it would if it had no auto-negotiation signaling. Under these conditions, an IEEE 802.3 MAU will immediately be forced to the state indicated by the value of the object ifMauDefaultType. NOTE TO IMPLEMENTORS: When ifMauAutoNegAdminStatus transitions from enabled to disabled, the agent implementation MUST ensure that the operational type of the MAU (as reported by ifMauType) correctly transitions to the value specified by the ifMauDefaultType object, rather than continuing to operate at the value earlier determined by the auto-negotiation function.
.1.3.6.1.2.1.26.5.1.1.2,MAU-MIB::ifMauAutoNegRemoteSignaling,INTEGER,read-only,,current,detected(1):notdetected(2),A value indicating whether the remote end of the link is using auto-negotiation signaling. It takes the value detected(1) if and only if, during the previous link negotiation, FLP Bursts were received.
.1.3.6.1.2.1.26.5.1.1.4,MAU-MIB::ifMauAutoNegConfig,INTEGER,read-only,,current,other(1):configuring(2):complete(3):disabled(4):parallelDetectFail(5),A value indicating the current status of the auto-negotiation process. The enumeration parallelDetectFail(5) maps to a failure in parallel detection as defined in 28.2.3.1 of [IEEE802.3].
.1.3.6.1.2.1.26.5.1.1.5,MAU-MIB::ifMauAutoNegCapability,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object has been deprecated in favour of ifMauAutoNegCapabilityBits. A value that uniquely identifies the set of capabilities of the local auto-negotiation entity. The value is a sum that initially takes the value zero. Then, for each capability of this interface, 2 raised to the power noted below is added to the sum. For example, an interface that has the capability to support only 100Base-TX half duplex would have a value of 32768 (2**15). In contrast, an interface that supports both 100Base-TX half duplex and 100Base-TX full duplex would have a value of 98304 ((2**15) + (2**16)). The powers of 2 assigned to the capabilities are these: Power Capability 0 other or unknown (1-9) (reserved) 10 10BASE-T half duplex mode 11 10BASE-T full duplex mode 12 (reserved) 13 (reserved) 14 100BASE-T4 15 100BASE-TX half duplex mode 16 100BASE-TX full duplex mode 17 (reserved) 18 (reserved) 19 100BASE-T2 half duplex mode 20 100BASE-T2 full duplex mode Note that interfaces that support this MIB may have capabilities that extend beyond the scope of this MIB.
.1.3.6.1.2.1.26.5.1.1.6,MAU-MIB::ifMauAutoNegCapAdvertised,Integer32,read-write,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object has been deprecated in favour of ifMauAutoNegCapAdvertisedBits. A value that uniquely identifies the set of capabilities advertised by the local auto-negotiation entity. Refer to ifMauAutoNegCapability for a description of the possible values of this object. Capabilities in this object that are not available in ifMauAutoNegCapability cannot be enabled.
.1.3.6.1.2.1.26.5.1.1.7,MAU-MIB::ifMauAutoNegCapReceived,Integer32,read-only,,deprecated,,********* THIS OBJECT IS DEPRECATED ********** This object has been deprecated in favour of ifMauAutoNegCapReceivedBits. A value that uniquely identifies the set of capabilities received from the remote auto-negotiation entity. Refer to ifMauAutoNegCapability for a description of the possible values of this object. Note that interfaces that support this MIB may be attached to remote auto-negotiation entities that have capabilities beyond the scope of this MIB.
.1.3.6.1.2.1.26.5.1.1.8,MAU-MIB::ifMauAutoNegRestart,INTEGER,read-write,,current,restart(1):norestart(2),If the value of this object is set to restart(1) then this will force auto-negotiation to begin link renegotiation. If auto-negotiation signaling is disabled, a write to this object has no effect. Setting the value of this object to norestart(2) has no effect.
.1.3.6.1.2.1.26.5.1.1.9,MAU-MIB::ifMauAutoNegCapabilityBits,BITS,read-only,,current,bOther(0):b10baseT(1):b10baseTFD(2):b100baseT4(3):b100baseTX(4):b100baseTXFD(5):b100baseT2(6):b100baseT2FD(7):bFdxPause(8):bFdxAPause(9):bFdxSPause(10):bFdxBPause(11):b1000baseX(12):b1000baseXFD(13):b1000baseT(14):b1000baseTFD(15):b10GbaseT(16):b1000baseKX(17):b10GbaseKX4(18):b10GbaseKR(19):b40GbaseKR4(20):b40GbaseCR4(21):b100GbaseCR10(22):b1000baseT1(23):b25GbaseRS(24):b25GbaseR(25):bRSFEC25Greq(26):bBaseFEC25Greq(27):b25GbaseT(28):b40GbaseT(29):b100GbaseCR4(30):b100GbaseKR4(31):b100GbaseKP4(32):bForceMS(33),A value that uniquely identifies the set of capabilities of the local auto-negotiation entity. Note that interfaces that support this MIB may have capabilities that extend beyond the scope of this MIB. Note that the local auto-negotiation entity may support some capabilities beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for standard capabilities that are listed in the IANAifMauAutoNegCapBits TC.
.1.3.6.1.2.1.26.5.1.1.10,MAU-MIB::ifMauAutoNegCapAdvertisedBits,BITS,read-write,,current,bOther(0):b10baseT(1):b10baseTFD(2):b100baseT4(3):b100baseTX(4):b100baseTXFD(5):b100baseT2(6):b100baseT2FD(7):bFdxPause(8):bFdxAPause(9):bFdxSPause(10):bFdxBPause(11):b1000baseX(12):b1000baseXFD(13):b1000baseT(14):b1000baseTFD(15):b10GbaseT(16):b1000baseKX(17):b10GbaseKX4(18):b10GbaseKR(19):b40GbaseKR4(20):b40GbaseCR4(21):b100GbaseCR10(22):b1000baseT1(23):b25GbaseRS(24):b25GbaseR(25):bRSFEC25Greq(26):bBaseFEC25Greq(27):b25GbaseT(28):b40GbaseT(29):b100GbaseCR4(30):b100GbaseKR4(31):b100GbaseKP4(32):bForceMS(33),A value that uniquely identifies the set of capabilities advertised by the local auto-negotiation entity. Capabilities in this object that are not available in ifMauAutoNegCapabilityBits cannot be enabled. Note that the local auto-negotiation entity may advertise some capabilities beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for standard capabilities that are listed in the IANAifMauAutoNegCapBits TC.
.1.3.6.1.2.1.26.5.1.1.11,MAU-MIB::ifMauAutoNegCapReceivedBits,BITS,read-only,,current,bOther(0):b10baseT(1):b10baseTFD(2):b100baseT4(3):b100baseTX(4):b100baseTXFD(5):b100baseT2(6):b100baseT2FD(7):bFdxPause(8):bFdxAPause(9):bFdxSPause(10):bFdxBPause(11):b1000baseX(12):b1000baseXFD(13):b1000baseT(14):b1000baseTFD(15):b10GbaseT(16):b1000baseKX(17):b10GbaseKX4(18):b10GbaseKR(19):b40GbaseKR4(20):b40GbaseCR4(21):b100GbaseCR10(22):b1000baseT1(23):b25GbaseRS(24):b25GbaseR(25):bRSFEC25Greq(26):bBaseFEC25Greq(27):b25GbaseT(28):b40GbaseT(29):b100GbaseCR4(30):b100GbaseKR4(31):b100GbaseKP4(32):bForceMS(33),A value that uniquely identifies the set of capabilities received from the remote auto-negotiation entity. Note that interfaces that support this MIB may be attached to remote auto-negotiation entities that have capabilities beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for standard capabilities that are listed in the IANAifMauAutoNegCapBits TC.
.1.3.6.1.2.1.26.5.1.1.12,MAU-MIB::ifMauAutoNegRemoteFaultAdvertised,INTEGER,read-write,,current,noError(1):offline(2):linkFailure(3):autoNegError(4),A value that identifies any local fault indications that this MAU has detected and will advertise at the next auto-negotiation interaction for 1000Mbps MAUs.
.1.3.6.1.2.1.26.5.1.1.13,MAU-MIB::ifMauAutoNegRemoteFaultReceived,INTEGER,read-only,,current,noError(1):offline(2):linkFailure(3):autoNegError(4),A value that identifies any fault indications received from the far end of a link by the local auto-negotiation entity for 1000Mbps MAUs.
.1.3.6.1.2.1.26.6,MAU-MIB::mauMod,,,,,,Management information for 802.3 MAUs. The following reference is used throughout this MIB module: [IEEE802.3] refers to: IEEE Std 802.3, 2005 Edition: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications'. Of particular interest is Clause 30, 'Management'. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4836; see the RFC itself for full legal notices.
.1.3.6.1.2.1.26.6.1,MAU-MIB::mauModConf,,,,,,
.1.3.6.1.2.1.26.6.1.1,MAU-MIB::mauModCompls,,,,,,
.1.3.6.1.2.1.26.6.1.1.1,MAU-MIB::mauModRpCompl,,,,,,******** THIS COMPLIANCE IS DEPRECATED ******** Compliance for MAUs attached to repeater ports. This compliance is deprecated and replaced by mauModRpCompl2, which corrects an oversight by allowing rpMauStatus to be implemented read-only.
.1.3.6.1.2.1.26.6.1.1.2,MAU-MIB::mauModIfCompl,,,,,,******** THIS COMPLIANCE IS DEPRECATED ******** Compliance for MAUs attached to interfaces. This compliance is deprecated and replaced by mauModIfCompl2.
.1.3.6.1.2.1.26.6.1.1.3,MAU-MIB::mauModIfCompl2,,,,,,******** THIS COMPLIANCE IS DEPRECATED ******** Compliance for MAUs attached to interfaces. This compliance is deprecated and replaced by mauModIfCompl3.
.1.3.6.1.2.1.26.6.1.1.4,MAU-MIB::mauModRpCompl2,,,,,,Compliance for MAUs attached to repeater ports. Note that compliance with this compliance statement requires compliance with the snmpRptrModCompl MODULE-COMPLIANCE statement of the SNMP-REPEATER-MIB (RFC 2108).
.1.3.6.1.2.1.26.6.1.1.5,MAU-MIB::mauModIfCompl3,,,,,,Compliance for MAUs attached to interfaces. Note that compliance with this compliance statement requires compliance with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB (RFC 2863) and the dot3Compliance2 MODULE-COMPLIANCE statement of the EtherLike-MIB (RFC3635).
.1.3.6.1.2.1.26.6.1.2,MAU-MIB::mauModObjGrps,,,,,,
.1.3.6.1.2.1.26.6.1.2.1,MAU-MIB::mauRpGrpBasic,,,,,,Basic conformance group for MAUs attached to repeater ports. This group is also the conformance specification for RFC 1515 implementations.
.1.3.6.1.2.1.26.6.1.2.2,MAU-MIB::mauRpGrp100Mbs,,,,,,Conformance group for MAUs attached to repeater ports with 100 Mb/s or greater capability.
.1.3.6.1.2.1.26.6.1.2.3,MAU-MIB::mauRpGrpJack,,,,,,Conformance group for MAUs attached to repeater ports with managed jacks.
.1.3.6.1.2.1.26.6.1.2.4,MAU-MIB::mauIfGrpBasic,,,,,,Basic conformance group for MAUs attached to interfaces. This group also provides a conformance specification for RFC 1515 implementations.
.1.3.6.1.2.1.26.6.1.2.5,MAU-MIB::mauIfGrp100Mbs,,,,,,********* THIS GROUP IS DEPRECATED ********** Conformance group for MAUs attached to interfaces with 100 Mb/s capability. This object group has been deprecated in favor of mauIfGrpHighCapacity.
.1.3.6.1.2.1.26.6.1.2.6,MAU-MIB::mauIfGrpJack,,,,,,Conformance group for MAUs attached to interfaces with managed jacks.
.1.3.6.1.2.1.26.6.1.2.7,MAU-MIB::mauIfGrpAutoNeg,,,,,,********* THIS GROUP IS DEPRECATED ********** Conformance group for MAUs attached to interfaces with managed auto-negotiation. This object group has been deprecated in favor of mauIfGrpAutoNeg2.
.1.3.6.1.2.1.26.6.1.2.8,MAU-MIB::mauBroadBasic,,,,,,********* THIS GROUP IS DEPRECATED ********** Conformance group for broadband MAUs attached to interfaces. This object group is deprecated. There have been no reported implementations of this group, and it was felt to be unlikely that there will be any future implementations.
.1.3.6.1.2.1.26.6.1.2.9,MAU-MIB::mauIfGrpHighCapacity,,,,,,Conformance group for MAUs attached to interfaces with 100 Mb/s or greater capability.
.1.3.6.1.2.1.26.6.1.2.10,MAU-MIB::mauIfGrpAutoNeg2,,,,,,Conformance group for MAUs attached to interfaces with managed auto-negotiation.
.1.3.6.1.2.1.26.6.1.2.11,MAU-MIB::mauIfGrpAutoNeg1000Mbps,,,,,,Conformance group for 1000Mbps MAUs attached to interfaces with managed auto-negotiation.
.1.3.6.1.2.1.26.6.1.2.12,MAU-MIB::mauIfGrpHCStats,,,,,,Conformance for high capacity statistics for MAUs attached to interfaces.
.1.3.6.1.2.1.26.6.1.3,MAU-MIB::mauModNotGrps,,,,,,
.1.3.6.1.2.1.26.6.1.3.1,MAU-MIB::rpMauNotifications,,,,,,Notifications for repeater MAUs.
.1.3.6.1.2.1.26.6.1.3.2,MAU-MIB::ifMauNotifications,,,,,,Notifications for interface MAUs.
.1.3.6.1.2.1.27,NETWORK-SERVICES-MIB::application,,,,,,The MIB module describing network service applications
.1.3.6.1.2.1.27.1,NETWORK-SERVICES-MIB::applTable,,not-accessible,,current,,The table holding objects which apply to all different kinds of applications providing network services. Each network service application capable of being monitored should have a single entry in this table.
.1.3.6.1.2.1.27.1.1,NETWORK-SERVICES-MIB::applEntry,,not-accessible,applIndex,current,,An entry associated with a single network service application.
.1.3.6.1.2.1.27.1.1.1,NETWORK-SERVICES-MIB::applIndex,INTEGER,not-accessible,,current,,An index to uniquely identify the network service application. This attribute is the index used for lexicographic ordering of the table.
.1.3.6.1.2.1.27.1.1.2,NETWORK-SERVICES-MIB::applName,OCTET,read-only,,current,,The name the network service application chooses to be known by.
.1.3.6.1.2.1.27.1.1.3,NETWORK-SERVICES-MIB::applDirectoryName,OCTET,read-only,,current,,The Distinguished Name of the directory entry where static information about this application is stored. An empty string indicates that no information about the application is available in the directory.
.1.3.6.1.2.1.27.1.1.4,NETWORK-SERVICES-MIB::applVersion,OCTET,read-only,,current,,The version of network service application software. This field is usually defined by the vendor of the network service application software.
.1.3.6.1.2.1.27.1.1.5,NETWORK-SERVICES-MIB::applUptime,TimeTicks,read-only,,current,,The value of sysUpTime at the time the network service application was last initialized. If the application was last initialized prior to the last initialization of the network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.27.1.1.6,NETWORK-SERVICES-MIB::applOperStatus,INTEGER,read-only,,current,up(1):down(2):halted(3):congested(4):restarting(5):quiescing(6),Indicates the operational status of the network service application. 'down' indicates that the network service is not available. 'up' indicates that the network service is operational and available. 'halted' indicates that the service is operational but not available. 'congested' indicates that the service is operational but no additional inbound associations can be accommodated. 'restarting' indicates that the service is currently unavailable but is in the process of restarting and will be available soon. 'quiescing' indicates that service is currently operational but is in the process of shutting down. Additional inbound associations may be rejected by applications in the 'quiescing' state.
.1.3.6.1.2.1.27.1.1.7,NETWORK-SERVICES-MIB::applLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the network service application entered its current operational state. If the current state was entered prior to the last initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.27.1.1.8,NETWORK-SERVICES-MIB::applInboundAssociations,Gauge32,read-only,,current,,The number of current associations to the network service application, where it is the responder. An inbound association occurs when another application successfully connects to this one.
.1.3.6.1.2.1.27.1.1.9,NETWORK-SERVICES-MIB::applOutboundAssociations,Gauge32,read-only,,current,,The number of current associations to the network service application, where it is the initiator. An outbound association occurs when this application successfully connects to another one.
.1.3.6.1.2.1.27.1.1.10,NETWORK-SERVICES-MIB::applAccumulatedInboundAssociations,Counter32,read-only,,current,,The total number of associations to the application entity since application initialization, where it was the responder.
.1.3.6.1.2.1.27.1.1.11,NETWORK-SERVICES-MIB::applAccumulatedOutboundAssociations,Counter32,read-only,,current,,The total number of associations to the application entity since application initialization, where it was the initiator.
.1.3.6.1.2.1.27.1.1.12,NETWORK-SERVICES-MIB::applLastInboundActivity,TimeTicks,read-only,,current,,The value of sysUpTime at the time this application last had an inbound association. If the last association occurred prior to the last initialization of the network subsystem, then this object contains a zero value.
.1.3.6.1.2.1.27.1.1.13,NETWORK-SERVICES-MIB::applLastOutboundActivity,TimeTicks,read-only,,current,,The value of sysUpTime at the time this application last had an outbound association. If the last association occurred prior to the last initialization of the network subsystem, then this object contains a zero value.
.1.3.6.1.2.1.27.1.1.14,NETWORK-SERVICES-MIB::applRejectedInboundAssociations,Counter32,read-only,,current,,The total number of inbound associations the application entity has rejected, since application initialization. Rejected associations are not counted in the accumulated association totals. Note that this only counts associations the application entity has rejected itself; it does not count rejections that occur at lower layers of the network. Thus, this counter may not reflect the true number of failed inbound associations.
.1.3.6.1.2.1.27.1.1.15,NETWORK-SERVICES-MIB::applFailedOutboundAssociations,Counter32,read-only,,current,,The total number associations where the application entity is initiator and association establishment has failed, since application initialization. Failed associations are not counted in the accumulated association totals.
.1.3.6.1.2.1.27.1.1.16,NETWORK-SERVICES-MIB::applDescription,OCTET,read-only,,current,,A text description of the application. This information is intended to identify and briefly describe the application in a status display.
.1.3.6.1.2.1.27.1.1.17,NETWORK-SERVICES-MIB::applURL,OCTET,read-only,,current,,A URL pointing to a description of the application. This information is intended to identify and describe the application in a status display.
.1.3.6.1.2.1.27.2,NETWORK-SERVICES-MIB::assocTable,,not-accessible,,current,,The table holding a set of all active application associations.
.1.3.6.1.2.1.27.2.1,NETWORK-SERVICES-MIB::assocEntry,,not-accessible,applIndex:assocIndex,current,,An entry associated with an association for a network service application.
.1.3.6.1.2.1.27.2.1.1,NETWORK-SERVICES-MIB::assocIndex,INTEGER,not-accessible,,current,,An index to uniquely identify each association for a network service application. This attribute is the index that is used for lexicographic ordering of the table. Note that the table is also indexed by the applIndex.
.1.3.6.1.2.1.27.2.1.2,NETWORK-SERVICES-MIB::assocRemoteApplication,OCTET,read-only,,current,,The name of the system running remote network service application. For an IP-based application this should be either a domain name or IP address. For an OSI application it should be the string encoded distinguished name of the managed object. For X.400(1984) MTAs which do not have a Distinguished Name, the RFC 2156 syntax 'mta in globalid' used in X400-Received: fields can be used. Note, however, that not all connections an MTA makes are necessarily to another MTA.
.1.3.6.1.2.1.27.2.1.3,NETWORK-SERVICES-MIB::assocApplicationProtocol,OBJECT,read-only,,current,,An identification of the protocol being used for the application. For an OSI Application, this will be the Application Context. For Internet applications, OID values of the form {applTCPProtoID port} or {applUDPProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol. The usual IANA procedures may be used to register ports for new protocols.
.1.3.6.1.2.1.27.2.1.4,NETWORK-SERVICES-MIB::assocApplicationType,INTEGER,read-only,,current,uainitiator(1):uaresponder(2):peerinitiator(3):peerresponder(4),This indicates whether the remote application is some type of client making use of this network service (e.g., a Mail User Agent) or a server acting as a peer. Also indicated is whether the remote end initiated an incoming connection to the network service or responded to an outgoing connection made by the local application. MTAs and messaging gateways are considered to be peers for the purposes of this variable.
.1.3.6.1.2.1.27.2.1.5,NETWORK-SERVICES-MIB::assocDuration,TimeTicks,read-only,,current,,The value of sysUpTime at the time this association was started. If this association started prior to the last initialization of the network subsystem, then this object contains a zero value.
.1.3.6.1.2.1.27.3,NETWORK-SERVICES-MIB::applConformance,,,,,,
.1.3.6.1.2.1.27.3.1,NETWORK-SERVICES-MIB::applGroups,,,,,,
.1.3.6.1.2.1.27.3.1.2,NETWORK-SERVICES-MIB::assocRFC1565Group,,,,,,A collection of objects providing basic monitoring of network service applications' associations. This is the original set of such objects defined in RFC 1565.
.1.3.6.1.2.1.27.3.1.3,NETWORK-SERVICES-MIB::applRFC2248Group,,,,,,A collection of objects providing basic monitoring of network service applications. This group was originally defined in RFC 2248; note that applDirectoryName is missing.
.1.3.6.1.2.1.27.3.1.4,NETWORK-SERVICES-MIB::assocRFC2248Group,,,,,,A collection of objects providing basic monitoring of network service applications' associations. This group was originally defined by RFC 2248.
.1.3.6.1.2.1.27.3.1.5,NETWORK-SERVICES-MIB::applRFC2788Group,,,,,,A collection of objects providing basic monitoring of network service applications. This is the appropriate group for RFC 2788 -- it adds the applDirectoryName object missing in RFC 2248.
.1.3.6.1.2.1.27.3.1.6,NETWORK-SERVICES-MIB::assocRFC2788Group,,,,,,A collection of objects providing basic monitoring of network service applications' associations. This is the appropriate group for RFC 2788.
.1.3.6.1.2.1.27.3.1.7,NETWORK-SERVICES-MIB::applRFC1565Group,,,,,,A collection of objects providing basic monitoring of network service applications. This is the original set of such objects defined in RFC 1565.
.1.3.6.1.2.1.27.3.2,NETWORK-SERVICES-MIB::applCompliances,,,,,,
.1.3.6.1.2.1.27.3.2.1,NETWORK-SERVICES-MIB::applCompliance,,,,,,The compliance statement for RFC 1565 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications. This is the basic compliance statement for RFC 1565.
.1.3.6.1.2.1.27.3.2.2,NETWORK-SERVICES-MIB::assocCompliance,,,,,,The compliance statement for RFC 1565 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.
.1.3.6.1.2.1.27.3.2.3,NETWORK-SERVICES-MIB::applRFC2248Compliance,,,,,,The compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications.
.1.3.6.1.2.1.27.3.2.4,NETWORK-SERVICES-MIB::assocRFC2248Compliance,,,,,,The compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.
.1.3.6.1.2.1.27.3.2.5,NETWORK-SERVICES-MIB::applRFC2788Compliance,,,,,,The compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications.
.1.3.6.1.2.1.27.3.2.6,NETWORK-SERVICES-MIB::assocRFC2788Compliance,,,,,,The compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.
.1.3.6.1.2.1.27.4,NETWORK-SERVICES-MIB::applTCPProtoID,,,,,,
.1.3.6.1.2.1.27.5,NETWORK-SERVICES-MIB::applUDPProtoID,,,,,,
.1.3.6.1.2.1.28,MTA-MIB::mta,,,,,,The MIB module describing Message Transfer Agents (MTAs)
.1.3.6.1.2.1.28.1,MTA-MIB::mtaTable,,not-accessible,,current,,The table holding information specific to an MTA.
.1.3.6.1.2.1.28.1.1,MTA-MIB::mtaEntry,,not-accessible,applIndex,current,,The entry associated with each MTA.
.1.3.6.1.2.1.28.1.1.1,MTA-MIB::mtaReceivedMessages,Counter32,read-only,,current,,The number of messages received since MTA initialization. This includes messages transmitted to this MTA from other MTAs as well as messages that have been submitted to the MTA directly by end-users or applications.
.1.3.6.1.2.1.28.1.1.2,MTA-MIB::mtaStoredMessages,Gauge32,read-only,,current,,The total number of messages currently stored in the MTA. This includes messages that are awaiting transmission to some other MTA or are waiting for delivery to an end-user or application.
.1.3.6.1.2.1.28.1.1.3,MTA-MIB::mtaTransmittedMessages,Counter32,read-only,,current,,The number of messages transmitted since MTA initialization. This includes messages that were transmitted to some other MTA or are waiting for delivery to an end-user or application.
.1.3.6.1.2.1.28.1.1.4,MTA-MIB::mtaReceivedVolume,Counter32,read-only,,current,,The total volume of messages received since MTA initialization, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data. This includes messages transmitted to this MTA from other MTAs as well as messages that have been submitted to the MTA directly by end-users or applications.
.1.3.6.1.2.1.28.1.1.5,MTA-MIB::mtaStoredVolume,Gauge32,read-only,,current,,The total volume of messages currently stored in the MTA, measured in kilo-octets. This volume should include all stored data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA would use the number of kilo-octets of P2 data. This includes messages that are awaiting transmission to some other MTA or are waiting for delivery to an end-user or application.
.1.3.6.1.2.1.28.1.1.6,MTA-MIB::mtaTransmittedVolume,Counter32,read-only,,current,,The total volume of messages transmitted since MTA initialization, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data. This includes messages that were transmitted to some other MTA or are waiting for delivery to an end-user or application.
.1.3.6.1.2.1.28.1.1.7,MTA-MIB::mtaReceivedRecipients,Counter32,read-only,,current,,The total number of recipients specified in all messages received since MTA initialization. Recipients this MTA has no responsibility for, i.e. inactive envelope recipients or ones referred to in message headers, should not be counted even if information about such recipients is available. This includes messages transmitted to this MTA from other MTAs as well as messages that have been submitted to the MTA directly by end-users or applications.
.1.3.6.1.2.1.28.1.1.8,MTA-MIB::mtaStoredRecipients,Gauge32,read-only,,current,,The total number of recipients specified in all messages currently stored in the MTA. Recipients this MTA has no responsibility for, i.e. inactive envelope recipients or ones referred to in message headers, should not be counted. This includes messages that are awaiting transmission to some other MTA or are waiting for delivery to an end-user or application.
.1.3.6.1.2.1.28.1.1.9,MTA-MIB::mtaTransmittedRecipients,Counter32,read-only,,current,,The total number of recipients specified in all messages transmitted since MTA initialization. Recipients this MTA had no responsibility for, i.e. inactive envelope recipients or ones referred to in message headers, should not be counted. This includes messages that were transmitted to some other MTA or are waiting for delivery to an end-user or application.
.1.3.6.1.2.1.28.1.1.10,MTA-MIB::mtaSuccessfulConvertedMessages,Counter32,read-only,,current,,The number of messages that have been successfully converted from one form to another since MTA initialization.
.1.3.6.1.2.1.28.1.1.11,MTA-MIB::mtaFailedConvertedMessages,Counter32,read-only,,current,,The number of messages for which an unsuccessful attempt was made to convert them from one form to another since MTA initialization.
.1.3.6.1.2.1.28.1.1.12,MTA-MIB::mtaLoopsDetected,Counter32,read-only,,current,,A message loop is defined as a situation where the MTA decides that a given message will never be delivered to one or more recipients and instead will continue to loop endlessly through one or more MTAs. This variable counts the number of times the MTA has detected such a situation since MTA initialization. Note that the mechanism MTAs use to detect loops (e.g., trace field counting, count of references to this MTA in a trace field, examination of DNS or other directory information, etc.), the level at which loops are detected (e.g., per message, per recipient, per directory entry, etc.), and the handling of a loop once it is detected (e.g., looping messages are held, looping messages are bounced or sent to the postmaster, messages that the MTA knows will loop won't be accepted, etc.) vary widely from one MTA to the next and cannot be inferred from this variable.
.1.3.6.1.2.1.28.2,MTA-MIB::mtaGroupTable,,not-accessible,,current,,The table holding information specific to each MTA group.
.1.3.6.1.2.1.28.2.1,MTA-MIB::mtaGroupEntry,,not-accessible,applIndex:mtaGroupIndex,current,,The entry associated with each MTA group.
.1.3.6.1.2.1.28.2.1.1,MTA-MIB::mtaGroupIndex,INTEGER,not-accessible,,current,,The index associated with a group for a given MTA.
.1.3.6.1.2.1.28.2.1.2,MTA-MIB::mtaGroupReceivedMessages,Counter32,read-only,,current,,The number of messages received to this group since group creation.
.1.3.6.1.2.1.28.2.1.3,MTA-MIB::mtaGroupRejectedMessages,Counter32,read-only,,current,,The number of messages rejected by this group since group creation.
.1.3.6.1.2.1.28.2.1.4,MTA-MIB::mtaGroupStoredMessages,Gauge32,read-only,,current,,The total number of messages currently stored in this group's queue.
.1.3.6.1.2.1.28.2.1.5,MTA-MIB::mtaGroupTransmittedMessages,Counter32,read-only,,current,,The number of messages transmitted by this group since group creation.
.1.3.6.1.2.1.28.2.1.6,MTA-MIB::mtaGroupReceivedVolume,Counter32,read-only,,current,,The total volume of messages received to this group since group creation, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data.
.1.3.6.1.2.1.28.2.1.7,MTA-MIB::mtaGroupStoredVolume,Gauge32,read-only,,current,,The total volume of messages currently stored in this group's queue, measured in kilo-octets. This volume should include all stored data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA would use the number of kilo-octets of P2 data.
.1.3.6.1.2.1.28.2.1.8,MTA-MIB::mtaGroupTransmittedVolume,Counter32,read-only,,current,,The total volume of messages transmitted by this group since group creation, measured in kilo-octets. This volume should include all transferred data that is logically above the mail transport protocol level. For example, an SMTP-based MTA should use the number of kilo-octets in the message header and body, while an X.400-based MTA should use the number of kilo-octets of P2 data.
.1.3.6.1.2.1.28.2.1.9,MTA-MIB::mtaGroupReceivedRecipients,Counter32,read-only,,current,,The total number of recipients specified in all messages received to this group since group creation. Recipients this MTA has no responsibility for should not be counted.
.1.3.6.1.2.1.28.2.1.10,MTA-MIB::mtaGroupStoredRecipients,Gauge32,read-only,,current,,The total number of recipients specified in all messages currently stored in this group's queue. Recipients this MTA has no responsibility for should not be counted.
.1.3.6.1.2.1.28.2.1.11,MTA-MIB::mtaGroupTransmittedRecipients,Counter32,read-only,,current,,The total number of recipients specified in all messages transmitted by this group since group creation. Recipients this MTA had no responsibility for should not be counted.
.1.3.6.1.2.1.28.2.1.12,MTA-MIB::mtaGroupOldestMessageStored,INTEGER,read-only,,current,,Time since the oldest message in this group's queue was placed in the queue.
.1.3.6.1.2.1.28.2.1.13,MTA-MIB::mtaGroupInboundAssociations,Gauge32,read-only,,current,,The number of current associations to the group, where the group is the responder.
.1.3.6.1.2.1.28.2.1.14,MTA-MIB::mtaGroupOutboundAssociations,Gauge32,read-only,,current,,The number of current associations to the group, where the group is the initiator.
.1.3.6.1.2.1.28.2.1.15,MTA-MIB::mtaGroupAccumulatedInboundAssociations,Counter32,read-only,,current,,The total number of associations to the group since group creation, where the MTA was the responder.
.1.3.6.1.2.1.28.2.1.16,MTA-MIB::mtaGroupAccumulatedOutboundAssociations,Counter32,read-only,,current,,The total number of associations from the group since group creation, where the MTA was the initiator.
.1.3.6.1.2.1.28.2.1.17,MTA-MIB::mtaGroupLastInboundActivity,INTEGER,read-only,,current,,Time since the last time that this group had an active inbound association for purposes of message reception.
.1.3.6.1.2.1.28.2.1.18,MTA-MIB::mtaGroupLastOutboundActivity,INTEGER,read-only,,current,,Time since the last time that this group had a successful outbound association for purposes of message delivery.
.1.3.6.1.2.1.28.2.1.19,MTA-MIB::mtaGroupRejectedInboundAssociations,Counter32,read-only,,current,,The total number of inbound associations the group has rejected, since group creation. Rejected associations are not counted in the accumulated association totals.
.1.3.6.1.2.1.28.2.1.20,MTA-MIB::mtaGroupFailedOutboundAssociations,Counter32,read-only,,current,,The total number associations where the group was the initiator and association establishment has failed, since group creation. Failed associations are not counted in the accumulated association totals.
.1.3.6.1.2.1.28.2.1.21,MTA-MIB::mtaGroupInboundRejectionReason,OCTET,read-only,,current,,The failure reason, if any, for the last association this group refused to respond to. If no association attempt has been made since the MTA was initialized the value should be 'never'.
.1.3.6.1.2.1.28.2.1.22,MTA-MIB::mtaGroupOutboundConnectFailureReason,OCTET,read-only,,current,,The failure reason, if any, for the last association attempt this group initiated. If no association attempt has been made since the MTA was initialized the value should be 'never'.
.1.3.6.1.2.1.28.2.1.23,MTA-MIB::mtaGroupScheduledRetry,INTEGER,read-only,,current,,The amount of time until this group is next scheduled to attempt to make an association.
.1.3.6.1.2.1.28.2.1.24,MTA-MIB::mtaGroupMailProtocol,OBJECT,read-only,,current,,An identification of the protocol being used by this group. For an group employing OSI protocols, this will be the Application Context. For Internet applications, OID values of the form {applTCPProtoID port} or {applUDPProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol. The usual IANA procedures may be used to register ports for new protocols. applTCPProtoID and applUDPProtoID are defined in the NETWORK-SERVICES-MIB, RFC 2788.
.1.3.6.1.2.1.28.2.1.25,MTA-MIB::mtaGroupName,OCTET,read-only,,current,,A descriptive name for the group. If this group connects to a single remote MTA this should be the name of that MTA. If this in turn is an Internet MTA this should be the domain name. For an OSI MTA it should be the string encoded distinguished name of the managed object using the format defined in RFC 2253. For X.400(1984) MTAs which do not have a Distinguished Name, the RFC 2156 syntax 'mta in globalid' used in X400-Received: fields can be used.
.1.3.6.1.2.1.28.2.1.26,MTA-MIB::mtaGroupSuccessfulConvertedMessages,Counter32,read-only,,current,,The number of messages that have been successfully converted from one form to another in this group since group creation.
.1.3.6.1.2.1.28.2.1.27,MTA-MIB::mtaGroupFailedConvertedMessages,Counter32,read-only,,current,,The number of messages for which an unsuccessful attempt was made to convert them from one form to another in this group since group creation.
.1.3.6.1.2.1.28.2.1.28,MTA-MIB::mtaGroupDescription,OCTET,read-only,,current,,A description of the group's purpose. This information is intended to identify the group in a status display.
.1.3.6.1.2.1.28.2.1.29,MTA-MIB::mtaGroupURL,OCTET,read-only,,current,,A URL pointing to a description of the group. This information is intended to identify and briefly describe the group in a status display.
.1.3.6.1.2.1.28.2.1.30,MTA-MIB::mtaGroupCreationTime,INTEGER,read-only,,current,,Time since this group was first created.
.1.3.6.1.2.1.28.2.1.31,MTA-MIB::mtaGroupHierarchy,INTEGER,read-only,,current,,Describes how this group fits into the hierarchy. A positive value is interpreted as an mtaGroupIndex value for some other group whose variables include those of this group (and usually others). A negative value is interpreted as a group collection code: Groups with common negative hierarchy values comprise one particular breakdown of MTA activity as a whole. A zero value means that this MIB implementation doesn't implement hierarchy indicators and thus the overall group hierarchy cannot be determined.
.1.3.6.1.2.1.28.2.1.32,MTA-MIB::mtaGroupOldestMessageId,OCTET,read-only,,current,,Message ID of the oldest message in the group's queue. Whenever possible this should be in the form of an RFC 822 msg-id; X.400 may convert X.400 message identifiers to this form by following the rules laid out in RFC2156.
.1.3.6.1.2.1.28.2.1.33,MTA-MIB::mtaGroupLoopsDetected,Counter32,read-only,,current,,A message loop is defined as a situation where the MTA decides that a given message will never be delivered to one or more recipients and instead will continue to loop endlessly through one or more MTAs. This variable counts the number of times the MTA has detected such a situation in conjunction with something associated with this group since group creation. Note that the mechanism MTAs use to detect loops (e.g., trace field counting, count of references to this MTA in a trace field, examination of DNS or other directory information, etc.), the level at which loops are detected (e.g., per message, per recipient, per directory entry, etc.), and the handling of a loop once it is detected (e.g., looping messages are held, looping messages are bounced or sent to the postmaster, messages that the MTA knows will loop won't be accepted, etc.) vary widely from one MTA to the next and cannot be inferred from this variable.
.1.3.6.1.2.1.28.2.1.34,MTA-MIB::mtaGroupLastOutboundAssociationAttempt,INTEGER,read-only,,current,,Time since the last time that this group attempted to make an outbound association for purposes of message delivery.
.1.3.6.1.2.1.28.3,MTA-MIB::mtaGroupAssociationTable,,not-accessible,,current,,The table holding information regarding the associations for each MTA group.
.1.3.6.1.2.1.28.3.1,MTA-MIB::mtaGroupAssociationEntry,,not-accessible,applIndex:mtaGroupIndex:mtaGroupAssociationIndex,current,,The entry holding information regarding the associations for each MTA group.
.1.3.6.1.2.1.28.3.1.1,MTA-MIB::mtaGroupAssociationIndex,INTEGER,read-only,,current,,Reference into association table to allow correlation of this group's active associations with the association table.
.1.3.6.1.2.1.28.4,MTA-MIB::mtaConformance,,,,,,
.1.3.6.1.2.1.28.4.1,MTA-MIB::mtaGroups,,,,,,
.1.3.6.1.2.1.28.4.1.4,MTA-MIB::mtaRFC2249Group,,,,,,A collection of objects providing basic monitoring of MTAs. This group was originally defined in RFC 2249.
.1.3.6.1.2.1.28.4.1.5,MTA-MIB::mtaRFC2249AssocGroup,,,,,,A collection of objects providing monitoring of MTA associations. This group was originally defined in RFC 2249.
.1.3.6.1.2.1.28.4.1.6,MTA-MIB::mtaRFC2249ErrorGroup,,,,,,A collection of objects providing monitoring of detailed MTA errors. This group was originally defined in RFC 2249.
.1.3.6.1.2.1.28.4.1.7,MTA-MIB::mtaRFC2789Group,,,,,,A collection of objects providing basic monitoring of MTAs. This is the appropriate group for RFC 2789.
.1.3.6.1.2.1.28.4.1.8,MTA-MIB::mtaRFC2789AssocGroup,,,,,,A collection of objects providing monitoring of MTA associations. This is the appropriate group for RFC 2789 association monitoring.
.1.3.6.1.2.1.28.4.1.9,MTA-MIB::mtaRFC2789ErrorGroup,,,,,,A collection of objects providing monitoring of detailed MTA errors. This is the appropriate group for RFC 2789 error monitoring.
.1.3.6.1.2.1.28.4.1.10,MTA-MIB::mtaRFC1566Group,,,,,,A collection of objects providing basic monitoring of MTAs. This is the original set of such objects defined in RFC 1566.
.1.3.6.1.2.1.28.4.1.11,MTA-MIB::mtaRFC1566AssocGroup,,,,,,A collection of objects providing monitoring of MTA associations. This is the original set of such objects defined in RFC 1566.
.1.3.6.1.2.1.28.4.2,MTA-MIB::mtaCompliances,,,,,,
.1.3.6.1.2.1.28.4.2.1,MTA-MIB::mtaCompliance,,,,,,The compliance statement for RFC 1566 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs.
.1.3.6.1.2.1.28.4.2.2,MTA-MIB::mtaAssocCompliance,,,,,,The compliance statement for RFC 1566 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations.
.1.3.6.1.2.1.28.4.2.5,MTA-MIB::mtaRFC2249Compliance,,,,,,The compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs.
.1.3.6.1.2.1.28.4.2.6,MTA-MIB::mtaRFC2249AssocCompliance,,,,,,The compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations.
.1.3.6.1.2.1.28.4.2.7,MTA-MIB::mtaRFC2249ErrorCompliance,,,,,,The compliance statement for RFC 2249 implementations which support the Mail Monitoring MIB for monitoring of MTAs and detailed errors.
.1.3.6.1.2.1.28.4.2.8,MTA-MIB::mtaRFC2249FullCompliance,,,,,,The compliance statement for RFC 2249 implementations which support the full Mail Monitoring MIB for monitoring of MTAs, associations, and detailed errors.
.1.3.6.1.2.1.28.4.2.9,MTA-MIB::mtaRFC2789Compliance,,,,,,The compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for basic monitoring of MTAs.
.1.3.6.1.2.1.28.4.2.10,MTA-MIB::mtaRFC2789AssocCompliance,,,,,,The compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for monitoring of MTAs and their associations.
.1.3.6.1.2.1.28.4.2.11,MTA-MIB::mtaRFC2789ErrorCompliance,,,,,,The compliance statement for RFC 2789 implementations which support the Mail Monitoring MIB for monitoring of MTAs and detailed errors.
.1.3.6.1.2.1.28.4.2.12,MTA-MIB::mtaRFC2789FullCompliance,,,,,,The compliance statement for RFC 2789 implementations which support the full Mail Monitoring MIB for monitoring of MTAs, associations, and detailed errors.
.1.3.6.1.2.1.28.5,MTA-MIB::mtaGroupErrorTable,,not-accessible,,current,,The table holding information regarding accumulated errors for each MTA group.
.1.3.6.1.2.1.28.5.1,MTA-MIB::mtaGroupErrorEntry,,not-accessible,applIndex:mtaGroupIndex:mtaStatusCode,current,,The entry holding information regarding accumulated errors for each MTA group.
.1.3.6.1.2.1.28.5.1.1,MTA-MIB::mtaGroupInboundErrorCount,Counter32,read-only,,current,,Count of the number of errors of a given type that have been accumulated in association with a particular group while processing incoming messages. In the case of SMTP these will typically be errors reporting by an SMTP server to the remote client; in the case of X.400 these will typically be errors encountered while processing an incoming message.
.1.3.6.1.2.1.28.5.1.2,MTA-MIB::mtaGroupInternalErrorCount,Counter32,read-only,,current,,Count of the number of errors of a given type that have been accumulated in association with a particular group during internal MTA processing.
.1.3.6.1.2.1.28.5.1.3,MTA-MIB::mtaGroupOutboundErrorCount,Counter32,read-only,,current,,Count of the number of errors of a given type that have been accumulated in association with a particular group's outbound connection activities. In the case of an SMTP client these will typically be errors reported while attempting to contact or while communicating with the remote SMTP server. In the case of X.400 these will typically be errors encountered while constructing or attempting to deliver an outgoing message.
.1.3.6.1.2.1.28.5.1.4,MTA-MIB::mtaStatusCode,INTEGER,not-accessible,,current,,An index capable of representing an Enhanced Mail System Status Code. Enhanced Mail System Status Codes are defined in RFC 1893. These codes have the form class.subject.detail Here 'class' is either 2, 4, or 5 and both 'subject' and 'detail' are integers in the range 0..999. Given a status code the corresponding index value is defined to be ((class * 1000) + subject) * 1000 + detail. Both SMTP error response codes and X.400 reason and diagnostic codes can be mapped into these codes, resulting in a namespace capable of describing most error conditions a mail system encounters in a generic yet detailed way.
.1.3.6.1.2.1.29,DSA-MIB::dsaMIB,,,,,, The MIB module for monitoring Directory System Agents.
.1.3.6.1.2.1.29.1,DSA-MIB::dsaOpsTable,,not-accessible,,current,, The table holding information related to the DSA operations.
.1.3.6.1.2.1.29.1.1,DSA-MIB::dsaOpsEntry,,not-accessible,applIndex,current,, Entry containing operations related statistics for a DSA.
.1.3.6.1.2.1.29.1.1.1,DSA-MIB::dsaAnonymousBinds,Counter32,read-only,,current,, Number of anonymous binds to this DSA from DUAs since application start.
.1.3.6.1.2.1.29.1.1.2,DSA-MIB::dsaUnauthBinds,Counter32,read-only,,current,, Number of un-authenticated binds to this DSA since application start.
.1.3.6.1.2.1.29.1.1.3,DSA-MIB::dsaSimpleAuthBinds,Counter32,read-only,,current,, Number of binds to this DSA that were authenticated using simple authentication procedures since application start.
.1.3.6.1.2.1.29.1.1.4,DSA-MIB::dsaStrongAuthBinds,Counter32,read-only,,current,, Number of binds to this DSA that were authenticated using the strong authentication procedures since application start. This includes the binds that were authenticated using external authentication procedures.
.1.3.6.1.2.1.29.1.1.5,DSA-MIB::dsaBindSecurityErrors,Counter32,read-only,,current,, Number of bind operations that have been rejected by this DSA due to inappropriateAuthentication or invalidCredentials.
.1.3.6.1.2.1.29.1.1.6,DSA-MIB::dsaInOps,Counter32,read-only,,current,, Number of operations forwarded to this DSA from DUAs or other DSAs since application start up.
.1.3.6.1.2.1.29.1.1.7,DSA-MIB::dsaReadOps,Counter32,read-only,,current,, Number of read operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.8,DSA-MIB::dsaCompareOps,Counter32,read-only,,current,, Number of compare operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.9,DSA-MIB::dsaAddEntryOps,Counter32,read-only,,current,, Number of addEntry operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.10,DSA-MIB::dsaRemoveEntryOps,Counter32,read-only,,current,, Number of removeEntry operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.11,DSA-MIB::dsaModifyEntryOps,Counter32,read-only,,current,, Number of modifyEntry operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.12,DSA-MIB::dsaModifyRDNOps,Counter32,read-only,,current,, Number of modifyRDN operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.13,DSA-MIB::dsaListOps,Counter32,read-only,,current,, Number of list operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.14,DSA-MIB::dsaSearchOps,Counter32,read-only,,current,, Number of search operations- baseObjectSearches, oneLevelSearches and subTreeSearches, serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.15,DSA-MIB::dsaOneLevelSearchOps,Counter32,read-only,,current,, Number of oneLevelSearch operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.16,DSA-MIB::dsaWholeTreeSearchOps,Counter32,read-only,,current,, Number of wholeTreeSearch operations serviced by this DSA since application startup.
.1.3.6.1.2.1.29.1.1.17,DSA-MIB::dsaReferrals,Counter32,read-only,,current,, Number of referrals returned by this DSA in response to requests for operations since application startup.
.1.3.6.1.2.1.29.1.1.18,DSA-MIB::dsaChainings,Counter32,read-only,,current,, Number of operations forwarded by this DSA to other DSAs since application startup.
.1.3.6.1.2.1.29.1.1.19,DSA-MIB::dsaSecurityErrors,Counter32,read-only,,current,, Number of operations forwarded to this DSA which did not meet the security requirements. 
.1.3.6.1.2.1.29.1.1.20,DSA-MIB::dsaErrors,Counter32,read-only,,current,, Number of operations that could not be serviced due to errors other than security errors, and referrals. A partially serviced operation will not be counted as an error. The errors include NameErrors, UpdateErrors, Attribute errors and ServiceErrors.
.1.3.6.1.2.1.29.2,DSA-MIB::dsaEntriesTable,,not-accessible,,current,, The table holding information related to the entry statistics and cache performance of the DSAs.
.1.3.6.1.2.1.29.2.1,DSA-MIB::dsaEntriesEntry,,not-accessible,applIndex,current,, Entry containing statistics pertaining to entries held by a DSA.
.1.3.6.1.2.1.29.2.1.1,DSA-MIB::dsaMasterEntries,Gauge32,read-only,,current,, Number of entries mastered in the DSA.
.1.3.6.1.2.1.29.2.1.2,DSA-MIB::dsaCopyEntries,Gauge32,read-only,,current,, Number of entries for which systematic (slave) copies are maintained in the DSA.
.1.3.6.1.2.1.29.2.1.3,DSA-MIB::dsaCacheEntries,Gauge32,read-only,,current,, Number of entries cached (non-systematic copies) in the DSA. This will include the entries that are cached partially. The negative cache is not counted.
.1.3.6.1.2.1.29.2.1.4,DSA-MIB::dsaCacheHits,Counter32,read-only,,current,, Number of operations that were serviced from the locally held cache since application startup.
.1.3.6.1.2.1.29.2.1.5,DSA-MIB::dsaSlaveHits,Counter32,read-only,,current,, Number of operations that were serviced from the locally held object replications [ shadow entries] since application startup.
.1.3.6.1.2.1.29.3,DSA-MIB::dsaIntTable,,not-accessible,,current,, Each row of this table contains some details related to the history of the interaction of the monitored DSAs with their respective peer DSAs.
.1.3.6.1.2.1.29.3.1,DSA-MIB::dsaIntEntry,,not-accessible,applIndex:dsaIntIndex,current,, Entry containing interaction details of a DSA with a peer DSA.
.1.3.6.1.2.1.29.3.1.1,DSA-MIB::dsaIntIndex,INTEGER,not-accessible,,current,, Together with applIndex it forms the unique key to identify the conceptual row which contains useful info on the (attempted) interaction between the DSA (referred to by applIndex) and a peer DSA.
.1.3.6.1.2.1.29.3.1.2,DSA-MIB::dsaName,OCTET,read-only,,current,, Distinguished Name of the peer DSA to which this entry pertains.
.1.3.6.1.2.1.29.3.1.3,DSA-MIB::dsaTimeOfCreation,TimeTicks,read-only,,current,, The value of sysUpTime when this row was created. If the entry was created before the network management subsystem was initialized, this object will contain a value of zero.
.1.3.6.1.2.1.29.3.1.4,DSA-MIB::dsaTimeOfLastAttempt,TimeTicks,read-only,,current,, The value of sysUpTime when the last attempt was made to contact this DSA. If the last attempt was made before the network management subsystem was initialized, this object will contain a value of zero.
.1.3.6.1.2.1.29.3.1.5,DSA-MIB::dsaTimeOfLastSuccess,TimeTicks,read-only,,current,, The value of sysUpTime when the last attempt made to contact this DSA was successful. If there have been no successful attempts this entry will have a value of zero. If the last successful attempt was made before the network management subsystem was initialized, this object will contain a value of zero.
.1.3.6.1.2.1.29.3.1.6,DSA-MIB::dsaFailuresSinceLastSuccess,Counter32,read-only,,current,, The number of failures since the last time an attempt to contact this DSA was successful. If there has been no successful attempts, this counter will contain the number of failures since this entry was created.
.1.3.6.1.2.1.29.3.1.7,DSA-MIB::dsaFailures,Counter32,read-only,,current,, Cumulative failures since the creation of this entry.
.1.3.6.1.2.1.29.3.1.8,DSA-MIB::dsaSuccesses,Counter32,read-only,,current,, Cumulative successes since the creation of this entry.
.1.3.6.1.2.1.29.4,DSA-MIB::dsaConformance,,,,,,
.1.3.6.1.2.1.29.4.1,DSA-MIB::dsaGroups,,,,,,
.1.3.6.1.2.1.29.4.1.1,DSA-MIB::dsaOpsGroup,,,,,, A collection of objects for monitoring the DSA operations.
.1.3.6.1.2.1.29.4.1.2,DSA-MIB::dsaEntryGroup,,,,,, A collection of objects for monitoring the DSA entry statistics and cache performance.
.1.3.6.1.2.1.29.4.1.3,DSA-MIB::dsaIntGroup,,,,,, A collection of objects for monitoring the DSA's interaction with peer DSAs.
.1.3.6.1.2.1.29.4.2,DSA-MIB::dsaCompliances,,,,,,
.1.3.6.1.2.1.29.4.2.1,DSA-MIB::dsaOpsCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the DSA-MIB for monitoring DSA operations.
.1.3.6.1.2.1.29.4.2.2,DSA-MIB::dsaEntryCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the DSA-MIB for monitoring DSA operations, entry statistics and cache performance.
.1.3.6.1.2.1.29.4.2.3,DSA-MIB::dsaIntCompliance,,,,,, The compliance statement for SNMPv2 entities which implement the DSA-MIB for monitoring DSA operations and the interaction of the DSA with peer DSAs.
.1.3.6.1.2.1.30,IANAifType-MIB::ianaifType,,,,,,This MIB module defines the IANAifType Textual Convention, and thus the enumerated values of the ifType object defined in MIB-II's ifTable.
.1.3.6.1.2.1.31,IF-MIB::ifMIB,,,,,,The MIB module to describe generic objects for network interface sub-layers. This MIB is an updated version of MIB-II's ifTable, and incorporates the extensions defined in RFC 1229.
.1.3.6.1.2.1.31.1,IF-MIB::ifMIBObjects,,,,,,
.1.3.6.1.2.1.31.1.1,IF-MIB::ifXTable,,not-accessible,,current,,A list of interface entries. The number of entries is given by the value of ifNumber. This table contains additional objects for the interface table.
.1.3.6.1.2.1.31.1.1.1,IF-MIB::ifXEntry,,not-accessible,,current,,An entry containing additional management information applicable to a particular interface.
.1.3.6.1.2.1.31.1.1.1.1,IF-MIB::ifName,OCTET,read-only,,current,,The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's `console'. This might be a text name, such as `le0' or a simple port number, such as `1', depending on the interface naming syntax of the device. If several entries in the ifTable together represent a single interface as named by the device, then each will have the same value of ifName. Note that for an agent which responds to SNMP queries concerning an interface on some other (proxied) device, then the value of ifName for such an interface is the proxied device's local name for it. If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.
.1.3.6.1.2.1.31.1.1.1.2,IF-MIB::ifInMulticastPkts,Counter32,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.3,IF-MIB::ifInBroadcastPkts,Counter32,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.4,IF-MIB::ifOutMulticastPkts,Counter32,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.5,IF-MIB::ifOutBroadcastPkts,Counter32,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.6,IF-MIB::ifHCInOctets,Counter64,read-only,,current,,The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.7,IF-MIB::ifHCInUcastPkts,Counter64,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. This object is a 64-bit version of ifInUcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.8,IF-MIB::ifHCInMulticastPkts,Counter64,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifInMulticastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.9,IF-MIB::ifHCInBroadcastPkts,Counter64,read-only,,current,,The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer. This object is a 64-bit version of ifInBroadcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.10,IF-MIB::ifHCOutOctets,Counter64,read-only,,current,,The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.11,IF-MIB::ifHCOutUcastPkts,Counter64,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutUcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.12,IF-MIB::ifHCOutMulticastPkts,Counter64,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifOutMulticastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.13,IF-MIB::ifHCOutBroadcastPkts,Counter64,read-only,,current,,The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutBroadcastPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.31.1.1.1.14,IF-MIB::ifLinkUpDownTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether linkUp/linkDown traps should be generated for this interface. By default, this object should have the value enabled(1) for interfaces which do not operate on 'top' of any other interface (as defined in the ifStackTable), and disabled(2) otherwise.
.1.3.6.1.2.1.31.1.1.1.15,IF-MIB::ifHighSpeed,Gauge32,read-only,,current,,An estimate of the interface's current bandwidth in units of 1,000,000 bits per second. If this object reports a value of `n' then the speed of the interface is somewhere in the range of `n-500,000' to `n+499,999'. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. For a sub-layer which has no concept of bandwidth, this object should be zero.
.1.3.6.1.2.1.31.1.1.1.16,IF-MIB::ifPromiscuousMode,INTEGER,read-write,,current,true(1):false(2),This object has a value of false(2) if this interface only accepts packets/frames that are addressed to this station. This object has a value of true(1) when the station accepts all packets/frames transmitted on the media. The value true(1) is only legal on certain types of media. If legal, setting this object to a value of true(1) may require the interface to be reset before becoming effective. The value of ifPromiscuousMode does not affect the reception of broadcast and multicast packets/frames by the interface.
.1.3.6.1.2.1.31.1.1.1.17,IF-MIB::ifConnectorPresent,INTEGER,read-only,,current,true(1):false(2),This object has the value 'true(1)' if the interface sublayer has a physical connector and the value 'false(2)' otherwise.
.1.3.6.1.2.1.31.1.1.1.18,IF-MIB::ifAlias,OCTET,read-write,,current,,This object is an 'alias' name for the interface as specified by a network manager, and provides a non-volatile 'handle' for the interface. On the first instantiation of an interface, the value of ifAlias associated with that interface is the zero-length string. As and when a value is written into an instance of ifAlias through a network management set operation, then the agent must retain the supplied value in the ifAlias instance associated with the same interface for as long as that interface remains instantiated, including across all re- initializations/reboots of the network management system, including those which result in a change of the interface's ifIndex value. An example of the value which a network manager might store in this object for a WAN interface is the (Telco's) circuit number/identifier of the interface. Some agents may support write-access only for interfaces having particular values of ifType. An agent which supports write access to this object is required to keep the value in non-volatile storage, but it may limit the length of new values depending on how much storage is already occupied by the current values for other interfaces.
.1.3.6.1.2.1.31.1.1.1.19,IF-MIB::ifCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the ifTable or ifXTable. If no such discontinuities have occurred since the last re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.31.1.2,IF-MIB::ifStackTable,,not-accessible,,current,,The table containing information on the relationships between the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'on top of' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs over the sub-layer with ifIndex value y, then this table contains: ifStackStatus.x.y=active For each ifIndex value, I, which identifies an active interface, there are always at least two instantiated rows in this table associated with I. For one of these rows, I is the value of ifStackHigherLayer; for the other, I is the value of ifStackLowerLayer. (If I is not involved in multiplexing, then these are the only two rows associated with I.) For example, two rows exist even for an interface which has no others stacked on top or below it: ifStackStatus.0.x=active ifStackStatus.x.0=active 
.1.3.6.1.2.1.31.1.2.1,IF-MIB::ifStackEntry,,not-accessible,ifStackHigherLayer:ifStackLowerLayer,current,,Information on a particular relationship between two sub- layers, specifying that one sub-layer runs on 'top' of the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable.
.1.3.6.1.2.1.31.1.2.1.1,IF-MIB::ifStackHigherLayer,Integer32,not-accessible,,current,,The value of ifIndex corresponding to the higher sub-layer of the relationship, i.e., the sub-layer which runs on 'top' of the sub-layer identified by the corresponding instance of ifStackLowerLayer. If there is no higher sub-layer (below the internetwork layer), then this object has the value 0.
.1.3.6.1.2.1.31.1.2.1.2,IF-MIB::ifStackLowerLayer,Integer32,not-accessible,,current,,The value of ifIndex corresponding to the lower sub-layer of the relationship, i.e., the sub-layer which runs 'below' the sub-layer identified by the corresponding instance of ifStackHigherLayer. If there is no lower sub-layer, then this object has the value 0.
.1.3.6.1.2.1.31.1.2.1.3,IF-MIB::ifStackStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the relationship between two sub-layers. Changing the value of this object from 'active' to 'notInService' or 'destroy' will likely have consequences up and down the interface stack. Thus, write access to this object is likely to be inappropriate for some types of interfaces, and many implementations will choose not to support write-access for any type of interface.
.1.3.6.1.2.1.31.1.3,IF-MIB::ifTestTable,,not-accessible,,deprecated,,This table contains one entry per interface. It defines objects which allow a network manager to instruct an agent to test an interface for various faults. Tests for an interface are defined in the media-specific MIB for that interface. After invoking a test, the object ifTestResult can be read to determine the outcome. If an agent can not perform the test, ifTestResult is set to so indicate. The object ifTestCode can be used to provide further test- specific or interface-specific (or even enterprise-specific) information concerning the outcome of the test. Only one test can be in progress on each interface at any one time. If one test is in progress when another test is invoked, the second test is rejected. Some agents may reject a test when a prior test is active on another interface. Before starting a test, a manager-station must first obtain 'ownership' of the entry in the ifTestTable for the interface to be tested. This is accomplished with the ifTestId and ifTestStatus objects as follows: try_again: get (ifTestId, ifTestStatus) while (ifTestStatus != notInUse) /* * Loop while a test is running or some other * manager is configuring a test. */ short delay get (ifTestId, ifTestStatus) } /* * Is not being used right now -- let's compete * to see who gets it. */ lock_value = ifTestId if ( set(ifTestId = lock_value, ifTestStatus = inUse, ifTestOwner = 'my-IP-address') == FAILURE) /* * Another manager got the ifTestEntry -- go * try again */ goto try_again; /* * I have the lock */ set up any test parameters. /* * This starts the test */ set(ifTestType = test_to_run); wait for test completion by polling ifTestResult when test completes, agent sets ifTestResult agent also sets ifTestStatus = 'notInUse' retrieve any additional test results, and ifTestId if (ifTestId == lock_value+1) results are valid A manager station first retrieves the value of the appropriate ifTestId and ifTestStatus objects, periodically repeating the retrieval if necessary, until the value of ifTestStatus is 'notInUse'. The manager station then tries to set the same ifTestId object to the value it just retrieved, the same ifTestStatus object to 'inUse', and the corresponding ifTestOwner object to a value indicating itself. If the set operation succeeds then the manager has obtained ownership of the ifTestEntry, and the value of the ifTestId object is incremented by the agent (per the semantics of TestAndIncr). Failure of the set operation indicates that some other manager has obtained ownership of the ifTestEntry. Once ownership is obtained, any test parameters can be setup, and then the test is initiated by setting ifTestType. On completion of the test, the agent sets ifTestStatus to 'notInUse'. Once this occurs, the manager can retrieve the results. In the (rare) event that the invocation of tests by two network managers were to overlap, then there would be a possibility that the first test's results might be overwritten by the second test's results prior to the first results being read. This unlikely circumstance ca
.1.3.6.1.2.1.31.1.3.1,IF-MIB::ifTestEntry,,not-accessible,,deprecated,,An entry containing objects for invoking tests on an interface.
.1.3.6.1.2.1.31.1.3.1.1,IF-MIB::ifTestId,INTEGER,read-write,,deprecated,,This object identifies the current invocation of the interface's test.
.1.3.6.1.2.1.31.1.3.1.2,IF-MIB::ifTestStatus,INTEGER,read-write,,deprecated,notInUse(1):inUse(2),This object indicates whether or not some manager currently has the necessary 'ownership' required to invoke a test on this interface. A write to this object is only successful when it changes its value from 'notInUse(1)' to 'inUse(2)'. After completion of a test, the agent resets the value back to 'notInUse(1)'.
.1.3.6.1.2.1.31.1.3.1.3,IF-MIB::ifTestType,OBJECT,read-write,,deprecated,,A control variable used to start and stop operator- initiated interface tests. Most OBJECT IDENTIFIER values assigned to tests are defined elsewhere, in association with specific types of interface. However, this document assigns a value for a full-duplex loopback test, and defines the special meanings of the subject identifier: noTest OBJECT IDENTIFIER ::= { 0 0 } When the value noTest is written to this object, no action is taken unless a test is in progress, in which case the test is aborted. Writing any other value to this object is only valid when no test is currently in progress, in which case the indicated test is initiated. When read, this object always returns the most recent value that ifTestType was set to. If it has not been set since the last initialization of the network management subsystem on the agent, a value of noTest is returned.
.1.3.6.1.2.1.31.1.3.1.4,IF-MIB::ifTestResult,INTEGER,read-only,,deprecated,none(1):success(2):inProgress(3):notSupported(4):unAbleToRun(5):aborted(6):failed(7),This object contains the result of the most recently requested test, or the value none(1) if no tests have been requested since the last reset. Note that this facility provides no provision for saving the results of one test when starting another, as could be required if used by multiple managers concurrently.
.1.3.6.1.2.1.31.1.3.1.5,IF-MIB::ifTestCode,OBJECT,read-only,,deprecated,,This object contains a code which contains more specific information on the test result, for example an error-code after a failed test. Error codes and other values this object may take are specific to the type of interface and/or test. The value may have the semantics of either the AutonomousType or InstancePointer textual conventions as defined in RFC 2579. The identifier: testCodeUnknown OBJECT IDENTIFIER ::= { 0 0 } is defined for use if no additional result code is available.
.1.3.6.1.2.1.31.1.3.1.6,IF-MIB::ifTestOwner,OCTET,read-write,,deprecated,,The entity which currently has the 'ownership' required to invoke a test on this interface.
.1.3.6.1.2.1.31.1.4,IF-MIB::ifRcvAddressTable,,not-accessible,,current,,This table contains an entry for each address (broadcast, multicast, or uni-cast) for which the system will receive packets/frames on a particular interface, except as follows: - for an interface operating in promiscuous mode, entries are only required for those addresses for which the system would receive frames were it not operating in promiscuous mode. - for 802.5 functional addresses, only one entry is required, for the address which has the functional address bit ANDed with the bit mask of all functional addresses for which the interface will accept frames. A system is normally able to use any unicast address which corresponds to an entry in this table as a source address.
.1.3.6.1.2.1.31.1.4.1,IF-MIB::ifRcvAddressEntry,,not-accessible,ifIndex:ifRcvAddressAddress,current,,A list of objects identifying an address for which the system will accept packets/frames on the particular interface identified by the index value ifIndex.
.1.3.6.1.2.1.31.1.4.1.1,IF-MIB::ifRcvAddressAddress,OCTET,not-accessible,,current,,An address for which the system will accept packets/frames on this entry's interface.
.1.3.6.1.2.1.31.1.4.1.2,IF-MIB::ifRcvAddressStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the ifRcvAddressTable.
.1.3.6.1.2.1.31.1.4.1.3,IF-MIB::ifRcvAddressType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3),This object has the value nonVolatile(3) for those entries in the table which are valid and will not be deleted by the next restart of the managed system. Entries having the value volatile(2) are valid and exist, but have not been saved, so that will not exist after the next restart of the managed system. Entries having the value other(1) are valid and exist but are not classified as to whether they will continue to exist after the next restart.
.1.3.6.1.2.1.31.1.5,IF-MIB::ifTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last creation or deletion of an entry in the ifTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.31.1.6,IF-MIB::ifStackLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last change of the (whole) interface stack. A change of the interface stack is defined to be any creation, deletion, or change in value of any instance of ifStackStatus. If the interface stack has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.31.2,IF-MIB::ifConformance,,,,,,
.1.3.6.1.2.1.31.2.1,IF-MIB::ifGroups,,,,,,
.1.3.6.1.2.1.31.2.1.1,IF-MIB::ifGeneralGroup,,,,,,A collection of objects deprecated in favour of ifGeneralInformationGroup.
.1.3.6.1.2.1.31.2.1.2,IF-MIB::ifFixedLengthGroup,,,,,,A collection of objects providing information specific to non-high speed (non-high speed interfaces transmit and receive at speeds less than or equal to 20,000,000 bits/second) character-oriented or fixed-length-transmission network interfaces.
.1.3.6.1.2.1.31.2.1.3,IF-MIB::ifHCFixedLengthGroup,,,,,,A collection of objects providing information specific to high speed (greater than 20,000,000 bits/second) character- oriented or fixed-length-transmission network interfaces.
.1.3.6.1.2.1.31.2.1.4,IF-MIB::ifPacketGroup,,,,,,A collection of objects providing information specific to non-high speed (non-high speed interfaces transmit and receive at speeds less than or equal to 20,000,000 bits/second) packet-oriented network interfaces.
.1.3.6.1.2.1.31.2.1.5,IF-MIB::ifHCPacketGroup,,,,,,A collection of objects providing information specific to high speed (greater than 20,000,000 bits/second but less than or equal to 650,000,000 bits/second) packet-oriented network interfaces.
.1.3.6.1.2.1.31.2.1.6,IF-MIB::ifVHCPacketGroup,,,,,,A collection of objects providing information specific to higher speed (greater than 650,000,000 bits/second) packet- oriented network interfaces.
.1.3.6.1.2.1.31.2.1.7,IF-MIB::ifRcvAddressGroup,,,,,,A collection of objects providing information on the multiple addresses which an interface receives.
.1.3.6.1.2.1.31.2.1.8,IF-MIB::ifTestGroup,,,,,,A collection of objects providing the ability to invoke tests on an interface.
.1.3.6.1.2.1.31.2.1.9,IF-MIB::ifStackGroup,,,,,,The previous collection of objects providing information on the layering of MIB-II interfaces.
.1.3.6.1.2.1.31.2.1.10,IF-MIB::ifGeneralInformationGroup,,,,,,A collection of objects providing information applicable to all network interfaces.
.1.3.6.1.2.1.31.2.1.11,IF-MIB::ifStackGroup2,,,,,,A collection of objects providing information on the layering of MIB-II interfaces.
.1.3.6.1.2.1.31.2.1.12,IF-MIB::ifOldObjectsGroup,,,,,,The collection of objects deprecated from the original MIB- II interfaces group.
.1.3.6.1.2.1.31.2.1.13,IF-MIB::ifCounterDiscontinuityGroup,,,,,,A collection of objects providing information specific to interface counter discontinuities.
.1.3.6.1.2.1.31.2.1.14,IF-MIB::linkUpDownNotificationsGroup,,,,,,The notifications which indicate specific changes in the value of ifOperStatus.
.1.3.6.1.2.1.31.2.2,IF-MIB::ifCompliances,,,,,,
.1.3.6.1.2.1.31.2.2.1,IF-MIB::ifCompliance,,,,,,A compliance statement defined in a previous version of this MIB module, for SNMP entities which have network interfaces.
.1.3.6.1.2.1.31.2.2.2,IF-MIB::ifCompliance2,,,,,,A compliance statement defined in a previous version of this MIB module, for SNMP entities which have network interfaces.
.1.3.6.1.2.1.31.2.2.3,IF-MIB::ifCompliance3,,,,,,The compliance statement for SNMP entities which have network interfaces.
.1.3.6.1.2.1.32,DNS-SERVER-MIB::dns,,,,,,The OID assigned to DNS MIB work by the IANA.
.1.3.6.1.2.1.32.1,DNS-SERVER-MIB::dnsServMIB,,,,,,The MIB module for entities implementing the server side of the Domain Name System (DNS) protocol.
.1.3.6.1.2.1.32.1.1,DNS-SERVER-MIB::dnsServMIBObjects,,,,,,
.1.3.6.1.2.1.32.1.1.1,DNS-SERVER-MIB::dnsServConfig,,,,,,
.1.3.6.1.2.1.32.1.1.1.1,DNS-SERVER-MIB::dnsServConfigImplementIdent,OCTET,read-only,,current,,The implementation identification string for the DNS server software in use on the system, for example; `FNS-2.1'
.1.3.6.1.2.1.32.1.1.1.2,DNS-SERVER-MIB::dnsServConfigRecurs,INTEGER,read-write,,current,available(1):restricted(2):unavailable(3),This represents the recursion services offered by this name server. The values that can be read or written are: available(1) - performs recursion on requests from clients. restricted(2) - recursion is performed on requests only from certain clients, for example; clients on an access control list. unavailable(3) - recursion is not available.
.1.3.6.1.2.1.32.1.1.1.3,DNS-SERVER-MIB::dnsServConfigUpTime,Gauge32,read-only,,current,,If the server has a persistent state (e.g., a process), this value will be the time elapsed since it started. For software without persistant state, this value will be zero.
.1.3.6.1.2.1.32.1.1.1.4,DNS-SERVER-MIB::dnsServConfigResetTime,Gauge32,read-only,,current,,If the server has a persistent state (e.g., a process) and supports a `reset' operation (e.g., can be told to re-read configuration files), this value will be the time elapsed since the last time the name server was `reset.' For software that does not have persistence or does not support a `reset' operation, this value will be zero.
.1.3.6.1.2.1.32.1.1.1.5,DNS-SERVER-MIB::dnsServConfigReset,INTEGER,read-write,,current,other(1):reset(2):initializing(3):running(4),Status/action object to reinitialize any persistant name server state. When set to reset(2), any persistant name server state (such as a process) is reinitialized as if the name server had just been started. This value will never be returned by a read operation. When read, one of the following values will be returned: other(1) - server in some unknown state; initializing(3) - server (re)initializing; running(4) - server currently running.
.1.3.6.1.2.1.32.1.1.2,DNS-SERVER-MIB::dnsServCounter,,,,,,
.1.3.6.1.2.1.32.1.1.2.2,DNS-SERVER-MIB::dnsServCounterAuthAns,Counter32,read-only,,current,,Number of queries which were authoritatively answered.
.1.3.6.1.2.1.32.1.1.2.3,DNS-SERVER-MIB::dnsServCounterAuthNoNames,Counter32,read-only,,current,,Number of queries for which `authoritative no such name' responses were made.
.1.3.6.1.2.1.32.1.1.2.4,DNS-SERVER-MIB::dnsServCounterAuthNoDataResps,Counter32,read-only,,current,,Number of queries for which `authoritative no such data' (empty answer) responses were made.
.1.3.6.1.2.1.32.1.1.2.5,DNS-SERVER-MIB::dnsServCounterNonAuthDatas,Counter32,read-only,,current,,Number of queries which were non-authoritatively answered (cached data).
.1.3.6.1.2.1.32.1.1.2.6,DNS-SERVER-MIB::dnsServCounterNonAuthNoDatas,Counter32,read-only,,current,,Number of queries which were non-authoritatively answered with no data (empty answer).
.1.3.6.1.2.1.32.1.1.2.7,DNS-SERVER-MIB::dnsServCounterReferrals,Counter32,read-only,,current,,Number of requests that were referred to other servers.
.1.3.6.1.2.1.32.1.1.2.8,DNS-SERVER-MIB::dnsServCounterErrors,Counter32,read-only,,current,,Number of requests the server has processed that were answered with errors (RCODE values other than 0 and 3).
.1.3.6.1.2.1.32.1.1.2.9,DNS-SERVER-MIB::dnsServCounterRelNames,Counter32,read-only,,current,,Number of requests received by the server for names that are only 1 label long (text form - no internal dots).
.1.3.6.1.2.1.32.1.1.2.10,DNS-SERVER-MIB::dnsServCounterReqRefusals,Counter32,read-only,,current,,Number of DNS requests refused by the server.
.1.3.6.1.2.1.32.1.1.2.11,DNS-SERVER-MIB::dnsServCounterReqUnparses,Counter32,read-only,,current,,Number of requests received which were unparseable.
.1.3.6.1.2.1.32.1.1.2.12,DNS-SERVER-MIB::dnsServCounterOtherErrors,Counter32,read-only,,current,,Number of requests which were aborted for other (local) server errors.
.1.3.6.1.2.1.32.1.1.2.13,DNS-SERVER-MIB::dnsServCounterTable,,not-accessible,,current,,Counter information broken down by DNS class and type.
.1.3.6.1.2.1.32.1.1.2.13.1,DNS-SERVER-MIB::dnsServCounterEntry,,not-accessible,dnsServCounterOpCode:dnsServCounterQClass:dnsServCounterQType:dnsServCounterTransport,current,,This table contains count information for each DNS class and type value known to the server. The index allows management software to to create indices to the table to get the specific information desired, e.g., number of queries over UDP for records with type value `A' which came to this server. In order to prevent an uncontrolled expansion of rows in the table; if dnsServCounterRequests is 0 and dnsServCounterResponses is 0, then the row does not exist and `no such' is returned when the agent is queried for such instances.
.1.3.6.1.2.1.32.1.1.2.13.1.1,DNS-SERVER-MIB::dnsServCounterOpCode,INTEGER,not-accessible,,current,,The DNS OPCODE being counted in this row of the table.
.1.3.6.1.2.1.32.1.1.2.13.1.2,DNS-SERVER-MIB::dnsServCounterQClass,INTEGER,not-accessible,,current,,The class of record being counted in this row of the table.
.1.3.6.1.2.1.32.1.1.2.13.1.3,DNS-SERVER-MIB::dnsServCounterQType,INTEGER,not-accessible,,current,,The type of record which is being counted in this row in the table.
.1.3.6.1.2.1.32.1.1.2.13.1.4,DNS-SERVER-MIB::dnsServCounterTransport,INTEGER,not-accessible,,current,udp(1):tcp(2):other(3),A value of udp(1) indicates that the queries reported on this row were sent using UDP. A value of tcp(2) indicates that the queries reported on this row were sent using TCP. A value of other(3) indicates that the queries reported on this row were sent using a transport that was neither TCP nor UDP.
.1.3.6.1.2.1.32.1.1.2.13.1.5,DNS-SERVER-MIB::dnsServCounterRequests,Counter32,read-only,,current,,Number of requests (queries) that have been recorded in this row of the table.
.1.3.6.1.2.1.32.1.1.2.13.1.6,DNS-SERVER-MIB::dnsServCounterResponses,Counter32,read-only,,current,,Number of responses made by the server since initialization for the kind of query identified on this row of the table.
.1.3.6.1.2.1.32.1.1.3,DNS-SERVER-MIB::dnsServOptCounter,,,,,,
.1.3.6.1.2.1.32.1.1.3.1,DNS-SERVER-MIB::dnsServOptCounterSelfAuthAns,Counter32,read-only,,current,,Number of requests the server has processed which originated from a resolver on the same host for which there has been an authoritative answer.
.1.3.6.1.2.1.32.1.1.3.2,DNS-SERVER-MIB::dnsServOptCounterSelfAuthNoNames,Counter32,read-only,,current,,Number of requests the server has processed which originated from a resolver on the same host for which there has been an authoritative no such name answer given.
.1.3.6.1.2.1.32.1.1.3.3,DNS-SERVER-MIB::dnsServOptCounterSelfAuthNoDataResps,Counter32,read-only,,current,,Number of requests the server has processed which originated from a resolver on the same host for which there has been an authoritative no such data answer (empty answer) made.
.1.3.6.1.2.1.32.1.1.3.4,DNS-SERVER-MIB::dnsServOptCounterSelfNonAuthDatas,Counter32,read-only,,current,,Number of requests the server has processed which originated from a resolver on the same host for which a non-authoritative answer (cached data) was made.
.1.3.6.1.2.1.32.1.1.3.5,DNS-SERVER-MIB::dnsServOptCounterSelfNonAuthNoDatas,Counter32,read-only,,current,,Number of requests the server has processed which originated from a resolver on the same host for which a `non-authoritative, no such data' response was made (empty answer).
.1.3.6.1.2.1.32.1.1.3.6,DNS-SERVER-MIB::dnsServOptCounterSelfReferrals,Counter32,read-only,,current,,Number of queries the server has processed which originated from a resolver on the same host and were referred to other servers.
.1.3.6.1.2.1.32.1.1.3.7,DNS-SERVER-MIB::dnsServOptCounterSelfErrors,Counter32,read-only,,current,,Number of requests the server has processed which originated from a resolver on the same host which have been answered with errors (RCODEs other than 0 and 3).
.1.3.6.1.2.1.32.1.1.3.8,DNS-SERVER-MIB::dnsServOptCounterSelfRelNames,Counter32,read-only,,current,,Number of requests received for names that are only 1 label long (text form - no internal dots) the server has processed which originated from a resolver on the same host.
.1.3.6.1.2.1.32.1.1.3.9,DNS-SERVER-MIB::dnsServOptCounterSelfReqRefusals,Counter32,read-only,,current,,Number of DNS requests refused by the server which originated from a resolver on the same host.
.1.3.6.1.2.1.32.1.1.3.10,DNS-SERVER-MIB::dnsServOptCounterSelfReqUnparses,Counter32,read-only,,current,,Number of requests received which were unparseable and which originated from a resolver on the same host.
.1.3.6.1.2.1.32.1.1.3.11,DNS-SERVER-MIB::dnsServOptCounterSelfOtherErrors,Counter32,read-only,,current,,Number of requests which were aborted for other (local) server errors and which originated on the same host.
.1.3.6.1.2.1.32.1.1.3.12,DNS-SERVER-MIB::dnsServOptCounterFriendsAuthAns,Counter32,read-only,,current,,Number of queries originating from friends which were authoritatively answered. The definition of friends is a locally defined matter.
.1.3.6.1.2.1.32.1.1.3.13,DNS-SERVER-MIB::dnsServOptCounterFriendsAuthNoNames,Counter32,read-only,,current,,Number of queries originating from friends, for which authoritative `no such name' responses were made. The definition of friends is a locally defined matter.
.1.3.6.1.2.1.32.1.1.3.14,DNS-SERVER-MIB::dnsServOptCounterFriendsAuthNoDataResps,Counter32,read-only,,current,,Number of queries originating from friends for which authoritative no such data (empty answer) responses were made. The definition of friends is a locally defined matter.
.1.3.6.1.2.1.32.1.1.3.15,DNS-SERVER-MIB::dnsServOptCounterFriendsNonAuthDatas,Counter32,read-only,,current,,Number of queries originating from friends which were non-authoritatively answered (cached data). The definition of friends is a locally defined matter.
.1.3.6.1.2.1.32.1.1.3.16,DNS-SERVER-MIB::dnsServOptCounterFriendsNonAuthNoDatas,Counter32,read-only,,current,,Number of queries originating from friends which were non-authoritatively answered with no such data (empty answer).
.1.3.6.1.2.1.32.1.1.3.17,DNS-SERVER-MIB::dnsServOptCounterFriendsReferrals,Counter32,read-only,,current,,Number of requests which originated from friends that were referred to other servers. The definition of friends is a locally defined matter.
.1.3.6.1.2.1.32.1.1.3.18,DNS-SERVER-MIB::dnsServOptCounterFriendsErrors,Counter32,read-only,,current,,Number of requests the server has processed which originated from friends and were answered with errors (RCODE values other than 0 and 3). The definition of friends is a locally defined matter.
.1.3.6.1.2.1.32.1.1.3.19,DNS-SERVER-MIB::dnsServOptCounterFriendsRelNames,Counter32,read-only,,current,,Number of requests received for names from friends that are only 1 label long (text form - no internal dots) the server has processed.
.1.3.6.1.2.1.32.1.1.3.20,DNS-SERVER-MIB::dnsServOptCounterFriendsReqRefusals,Counter32,read-only,,current,,Number of DNS requests refused by the server which were received from `friends'.
.1.3.6.1.2.1.32.1.1.3.21,DNS-SERVER-MIB::dnsServOptCounterFriendsReqUnparses,Counter32,read-only,,current,,Number of requests received which were unparseable and which originated from `friends'.
.1.3.6.1.2.1.32.1.1.3.22,DNS-SERVER-MIB::dnsServOptCounterFriendsOtherErrors,Counter32,read-only,,current,,Number of requests which were aborted for other (local) server errors and which originated from `friends'.
.1.3.6.1.2.1.32.1.1.4,DNS-SERVER-MIB::dnsServZone,,,,,,
.1.3.6.1.2.1.32.1.1.4.1,DNS-SERVER-MIB::dnsServZoneTable,,not-accessible,,current,,Table of zones for which this name server provides information. Each of the zones may be loaded from stable storage via an implementation-specific mechanism or may be obtained from another name server via a zone transfer. If name server doesn't load any zones, this table is empty.
.1.3.6.1.2.1.32.1.1.4.1.1,DNS-SERVER-MIB::dnsServZoneEntry,,not-accessible,dnsServZoneName:dnsServZoneClass,current,,An entry in the name server zone table. New rows may be added either via SNMP or by the name server itself.
.1.3.6.1.2.1.32.1.1.4.1.1.1,DNS-SERVER-MIB::dnsServZoneName,OCTET,not-accessible,,current,,DNS name of the zone described by this row of the table. This is the owner name of the SOA RR that defines the top of the zone. This is name is in uppercase: characters 'a' through 'z' are mapped to 'A' through 'Z' in order to make the lexical ordering useful.
.1.3.6.1.2.1.32.1.1.4.1.1.2,DNS-SERVER-MIB::dnsServZoneClass,INTEGER,not-accessible,,current,,DNS class of the RRs in this zone.
.1.3.6.1.2.1.32.1.1.4.1.1.3,DNS-SERVER-MIB::dnsServZoneLastReloadSuccess,Gauge32,read-only,,current,,Elapsed time in seconds since last successful reload of this zone.
.1.3.6.1.2.1.32.1.1.4.1.1.4,DNS-SERVER-MIB::dnsServZoneLastReloadAttempt,Gauge32,read-only,,current,,Elapsed time in seconds since last attempted reload of this zone.
.1.3.6.1.2.1.32.1.1.4.1.1.5,DNS-SERVER-MIB::dnsServZoneLastSourceAttempt,IpAddress,read-only,,current,,IP address of host from which most recent zone transfer of this zone was attempted. This value should match the value of dnsServZoneSourceSuccess if the attempt was succcessful. If zone transfer has not been attempted within the memory of this name server, this value should be 0.0.0.0.
.1.3.6.1.2.1.32.1.1.4.1.1.6,DNS-SERVER-MIB::dnsServZoneStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the information represented in this row of the table.
.1.3.6.1.2.1.32.1.1.4.1.1.7,DNS-SERVER-MIB::dnsServZoneSerial,Counter32,read-only,,current,,Zone serial number (from the SOA RR) of the zone represented by this row of the table. If the zone has not been successfully loaded within the memory of this name server, the value of this variable is zero.
.1.3.6.1.2.1.32.1.1.4.1.1.8,DNS-SERVER-MIB::dnsServZoneCurrent,INTEGER,read-only,,current,true(1):false(2),Whether the server's copy of the zone represented by this row of the table is currently valid. If the zone has never been successfully loaded or has expired since it was last succesfully loaded, this variable will have the value false(2), otherwise this variable will have the value true(1).
.1.3.6.1.2.1.32.1.1.4.1.1.9,DNS-SERVER-MIB::dnsServZoneLastSourceSuccess,IpAddress,read-only,,current,,IP address of host which was the source of the most recent successful zone transfer for this zone. If unknown (e.g., zone has never been successfully transfered) or irrelevant (e.g., zone was loaded from stable storage), this value should be 0.0.0.0.
.1.3.6.1.2.1.32.1.1.4.2,DNS-SERVER-MIB::dnsServZoneSrcTable,,not-accessible,,current,,This table is a list of IP addresses from which the server will attempt to load zone information using DNS zone transfer operations. A reload may occur due to SNMP operations that create a row in dnsServZoneTable or a SET to object dnsServZoneReload. This table is only used when the zone is loaded via zone transfer.
.1.3.6.1.2.1.32.1.1.4.2.1,DNS-SERVER-MIB::dnsServZoneSrcEntry,,not-accessible,dnsServZoneSrcName:dnsServZoneSrcClass:dnsServZoneSrcAddr,current,,An entry in the name server zone source table.
.1.3.6.1.2.1.32.1.1.4.2.1.1,DNS-SERVER-MIB::dnsServZoneSrcName,OCTET,not-accessible,,current,,DNS name of the zone to which this entry applies.
.1.3.6.1.2.1.32.1.1.4.2.1.2,DNS-SERVER-MIB::dnsServZoneSrcClass,INTEGER,not-accessible,,current,,DNS class of zone to which this entry applies.
.1.3.6.1.2.1.32.1.1.4.2.1.3,DNS-SERVER-MIB::dnsServZoneSrcAddr,IpAddress,not-accessible,,current,,IP address of name server host from which this zone might be obtainable.
.1.3.6.1.2.1.32.1.1.4.2.1.4,DNS-SERVER-MIB::dnsServZoneSrcStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the information represented in this row of the table.
.1.3.6.1.2.1.32.1.2,DNS-SERVER-MIB::dnsServMIBGroups,,,,,,
.1.3.6.1.2.1.32.1.2.1,DNS-SERVER-MIB::dnsServConfigGroup,,,,,,A collection of objects providing basic configuration control of a DNS name server.
.1.3.6.1.2.1.32.1.2.2,DNS-SERVER-MIB::dnsServCounterGroup,,,,,,A collection of objects providing basic instrumentation of a DNS name server.
.1.3.6.1.2.1.32.1.2.3,DNS-SERVER-MIB::dnsServOptCounterGroup,,,,,,A collection of objects providing extended instrumentation of a DNS name server.
.1.3.6.1.2.1.32.1.2.4,DNS-SERVER-MIB::dnsServZoneGroup,,,,,,A collection of objects providing configuration control of a DNS name server which loads authoritative zones.
.1.3.6.1.2.1.32.1.3,DNS-SERVER-MIB::dnsServMIBCompliances,,,,,,
.1.3.6.1.2.1.32.1.3.1,DNS-SERVER-MIB::dnsServMIBCompliance,,,,,,The compliance statement for agents implementing the DNS name server MIB extensions.
.1.3.6.1.2.1.32.2,DNS-RESOLVER-MIB::dnsResMIB,,,,,,The MIB module for entities implementing the client (resolver) side of the Domain Name System (DNS) protocol.
.1.3.6.1.2.1.32.2.1,DNS-RESOLVER-MIB::dnsResMIBObjects,,,,,,
.1.3.6.1.2.1.32.2.1.1,DNS-RESOLVER-MIB::dnsResConfig,,,,,,
.1.3.6.1.2.1.32.2.1.1.1,DNS-RESOLVER-MIB::dnsResConfigImplementIdent,OCTET,read-only,,current,,The implementation identification string for the resolver software in use on the system, for example; `RES-2.1'
.1.3.6.1.2.1.32.2.1.1.2,DNS-RESOLVER-MIB::dnsResConfigService,INTEGER,read-only,,current,recursiveOnly(1):iterativeOnly(2):recursiveAndIterative(3),Kind of DNS resolution service provided: recursiveOnly(1) indicates a stub resolver. iterativeOnly(2) indicates a normal full service resolver. recursiveAndIterative(3) indicates a full-service resolver which performs a mix of recursive and iterative queries.
.1.3.6.1.2.1.32.2.1.1.3,DNS-RESOLVER-MIB::dnsResConfigMaxCnames,INTEGER,read-write,,current,,Limit on how many CNAMEs the resolver should allow before deciding that there's a CNAME loop. Zero means that resolver has no explicit CNAME limit.
.1.3.6.1.2.1.32.2.1.1.4,DNS-RESOLVER-MIB::dnsResConfigSbeltTable,,not-accessible,,current,,Table of safety belt information used by the resolver when it hasn't got any better idea of where to send a query, such as when the resolver is booting or is a stub resolver.
.1.3.6.1.2.1.32.2.1.1.4.1,DNS-RESOLVER-MIB::dnsResConfigSbeltEntry,,not-accessible,dnsResConfigSbeltAddr:dnsResConfigSbeltSubTree:dnsResConfigSbeltClass,current,,An entry in the resolver's Sbelt table. Rows may be created or deleted at any time by the DNS resolver and by SNMP SET requests. Whether the values changed via SNMP are saved in stable storage across `reset' operations is implementation-specific.
.1.3.6.1.2.1.32.2.1.1.4.1.1,DNS-RESOLVER-MIB::dnsResConfigSbeltAddr,IpAddress,not-accessible,,current,,The IP address of the Sbelt name server identified by this row of the table.
.1.3.6.1.2.1.32.2.1.1.4.1.2,DNS-RESOLVER-MIB::dnsResConfigSbeltName,OCTET,read-create,,current,,The DNS name of a Sbelt nameserver identified by this row of the table. A zero-length string indicates that the name is not known by the resolver.
.1.3.6.1.2.1.32.2.1.1.4.1.3,DNS-RESOLVER-MIB::dnsResConfigSbeltRecursion,INTEGER,read-create,,current,iterative(1):recursive(2):recursiveAndIterative(3),Kind of queries resolver will be sending to the name server identified in this row of the table: iterative(1) indicates that resolver will be directing iterative queries to this name server (RD bit turned off). recursive(2) indicates that resolver will be directing recursive queries to this name server (RD bit turned on). recursiveAndIterative(3) indicates that the resolver will be directing both recursive and iterative queries to the server identified in this row of the table.
.1.3.6.1.2.1.32.2.1.1.4.1.4,DNS-RESOLVER-MIB::dnsResConfigSbeltPref,INTEGER,read-create,,current,,This value identifies the preference for the name server identified in this row of the table. The lower the value, the more desirable the resolver considers this server.
.1.3.6.1.2.1.32.2.1.1.4.1.5,DNS-RESOLVER-MIB::dnsResConfigSbeltSubTree,OCTET,not-accessible,,current,,Queries sent to the name server identified by this row of the table are limited to those for names in the name subtree identified by this variable. If no such limitation applies, the value of this variable is the name of the root domain (a DNS name consisting of a single zero octet).
.1.3.6.1.2.1.32.2.1.1.4.1.6,DNS-RESOLVER-MIB::dnsResConfigSbeltClass,INTEGER,not-accessible,,current,,The class of DNS queries that will be sent to the server identified by this row of the table.
.1.3.6.1.2.1.32.2.1.1.4.1.7,DNS-RESOLVER-MIB::dnsResConfigSbeltStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Row status column for this row of the Sbelt table.
.1.3.6.1.2.1.32.2.1.1.5,DNS-RESOLVER-MIB::dnsResConfigUpTime,Gauge32,read-only,,current,,If the resolver has a persistent state (e.g., a process), this value will be the time elapsed since it started. For software without persistant state, this value will be 0.
.1.3.6.1.2.1.32.2.1.1.6,DNS-RESOLVER-MIB::dnsResConfigResetTime,Gauge32,read-only,,current,,If the resolver has a persistent state (e.g., a process) and supports a `reset' operation (e.g., can be told to re-read configuration files), this value will be the time elapsed since the last time the resolver was `reset.' For software that does not have persistence or does not support a `reset' operation, this value will be zero.
.1.3.6.1.2.1.32.2.1.1.7,DNS-RESOLVER-MIB::dnsResConfigReset,INTEGER,read-write,,current,other(1):reset(2):initializing(3):running(4),Status/action object to reinitialize any persistant resolver state. When set to reset(2), any persistant resolver state (such as a process) is reinitialized as if the resolver had just been started. This value will never be returned by a read operation. When read, one of the following values will be returned: other(1) - resolver in some unknown state; initializing(3) - resolver (re)initializing; running(4) - resolver currently running.
.1.3.6.1.2.1.32.2.1.2,DNS-RESOLVER-MIB::dnsResCounter,,,,,,
.1.3.6.1.2.1.32.2.1.2.3,DNS-RESOLVER-MIB::dnsResCounterByOpcodeTable,,not-accessible,,current,,Table of the current count of resolver queries and answers.
.1.3.6.1.2.1.32.2.1.2.3.1,DNS-RESOLVER-MIB::dnsResCounterByOpcodeEntry,,not-accessible,dnsResCounterByOpcodeCode,current,,Entry in the resolver counter table. Entries are indexed by DNS OpCode.
.1.3.6.1.2.1.32.2.1.2.3.1.1,DNS-RESOLVER-MIB::dnsResCounterByOpcodeCode,INTEGER,not-accessible,,current,,The index to this table. The OpCodes that have already been defined are found in RFC-1035.
.1.3.6.1.2.1.32.2.1.2.3.1.2,DNS-RESOLVER-MIB::dnsResCounterByOpcodeQueries,Counter32,read-only,,current,,Total number of queries that have sent out by the resolver since initialization for the OpCode which is the index to this row of the table.
.1.3.6.1.2.1.32.2.1.2.3.1.3,DNS-RESOLVER-MIB::dnsResCounterByOpcodeResponses,Counter32,read-only,,current,,Total number of responses that have been received by the resolver since initialization for the OpCode which is the index to this row of the table.
.1.3.6.1.2.1.32.2.1.2.4,DNS-RESOLVER-MIB::dnsResCounterByRcodeTable,,not-accessible,,current,,Table of the current count of responses to resolver queries.
.1.3.6.1.2.1.32.2.1.2.4.1,DNS-RESOLVER-MIB::dnsResCounterByRcodeEntry,,not-accessible,dnsResCounterByRcodeCode,current,,Entry in the resolver response table. Entries are indexed by DNS response code.
.1.3.6.1.2.1.32.2.1.2.4.1.1,DNS-RESOLVER-MIB::dnsResCounterByRcodeCode,INTEGER,not-accessible,,current,,The index to this table. The Response Codes that have already been defined are found in RFC-1035.
.1.3.6.1.2.1.32.2.1.2.4.1.2,DNS-RESOLVER-MIB::dnsResCounterByRcodeResponses,Counter32,read-only,,current,,Number of responses the resolver has received for the response code value which identifies this row of the table.
.1.3.6.1.2.1.32.2.1.2.5,DNS-RESOLVER-MIB::dnsResCounterNonAuthDataResps,Counter32,read-only,,current,,Number of requests made by the resolver for which a non-authoritative answer (cached data) was received.
.1.3.6.1.2.1.32.2.1.2.6,DNS-RESOLVER-MIB::dnsResCounterNonAuthNoDataResps,Counter32,read-only,,current,,Number of requests made by the resolver for which a non-authoritative answer - no such data response (empty answer) was received.
.1.3.6.1.2.1.32.2.1.2.7,DNS-RESOLVER-MIB::dnsResCounterMartians,Counter32,read-only,,current,,Number of responses received which were received from servers that the resolver does not think it asked.
.1.3.6.1.2.1.32.2.1.2.8,DNS-RESOLVER-MIB::dnsResCounterRecdResponses,Counter32,read-only,,current,,Number of responses received to all queries.
.1.3.6.1.2.1.32.2.1.2.9,DNS-RESOLVER-MIB::dnsResCounterUnparseResps,Counter32,read-only,,current,,Number of responses received which were unparseable.
.1.3.6.1.2.1.32.2.1.2.10,DNS-RESOLVER-MIB::dnsResCounterFallbacks,Counter32,read-only,,current,,Number of times the resolver had to fall back to its seat belt information.
.1.3.6.1.2.1.32.2.1.3,DNS-RESOLVER-MIB::dnsResLameDelegation,,,,,,
.1.3.6.1.2.1.32.2.1.3.1,DNS-RESOLVER-MIB::dnsResLameDelegationOverflows,Counter32,read-only,,current,,Number of times the resolver attempted to add an entry to the Lame Delegation table but was unable to for some reason such as space constraints.
.1.3.6.1.2.1.32.2.1.3.2,DNS-RESOLVER-MIB::dnsResLameDelegationTable,,not-accessible,,current,,Table of name servers returning lame delegations. A lame delegation has occured when a parent zone delegates authority for a child zone to a server that appears not to think that it is authoritative for the child zone in question.
.1.3.6.1.2.1.32.2.1.3.2.1,DNS-RESOLVER-MIB::dnsResLameDelegationEntry,,not-accessible,dnsResLameDelegationSource:dnsResLameDelegationName:dnsResLameDelegationClass,current,,Entry in lame delegation table. Only the resolver may create rows in this table. SNMP SET requests may be used to delete rows.
.1.3.6.1.2.1.32.2.1.3.2.1.1,DNS-RESOLVER-MIB::dnsResLameDelegationSource,IpAddress,not-accessible,,current,,Source of lame delegation.
.1.3.6.1.2.1.32.2.1.3.2.1.2,DNS-RESOLVER-MIB::dnsResLameDelegationName,OCTET,not-accessible,,current,,DNS name for which lame delegation was received.
.1.3.6.1.2.1.32.2.1.3.2.1.3,DNS-RESOLVER-MIB::dnsResLameDelegationClass,INTEGER,not-accessible,,current,,DNS class of received lame delegation.
.1.3.6.1.2.1.32.2.1.3.2.1.4,DNS-RESOLVER-MIB::dnsResLameDelegationCounts,Counter32,read-only,,current,,How many times this lame delegation has been received.
.1.3.6.1.2.1.32.2.1.3.2.1.5,DNS-RESOLVER-MIB::dnsResLameDelegationStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status column for the lame delegation table. Since only the agent (DNS resolver) creates rows in this table, the only values that a manager may write to this variable are active(1) and destroy(6).
.1.3.6.1.2.1.32.2.1.4,DNS-RESOLVER-MIB::dnsResCache,,,,,,
.1.3.6.1.2.1.32.2.1.4.1,DNS-RESOLVER-MIB::dnsResCacheStatus,INTEGER,read-write,,current,enabled(1):disabled(2):clear(3),Status/action for the resolver's cache. enabled(1) means that the use of the cache is allowed. Query operations can return this state. disabled(2) means that the cache is not being used. Query operations can return this state. Setting this variable to clear(3) deletes the entire contents of the resolver's cache, but does not otherwise change the resolver's state. The status will retain its previous value from before the clear operation (i.e., enabled(1) or disabled(2)). The value of clear(3) can NOT be returned by a query operation.
.1.3.6.1.2.1.32.2.1.4.2,DNS-RESOLVER-MIB::dnsResCacheMaxTTL,Gauge32,read-write,,current,,Maximum Time-To-Live for RRs in this cache. If the resolver does not implement a TTL ceiling, the value of this field should be zero.
.1.3.6.1.2.1.32.2.1.4.3,DNS-RESOLVER-MIB::dnsResCacheGoodCaches,Counter32,read-only,,current,,Number of RRs the resolver has cached successfully.
.1.3.6.1.2.1.32.2.1.4.4,DNS-RESOLVER-MIB::dnsResCacheBadCaches,Counter32,read-only,,current,,Number of RRs the resolver has refused to cache because they appear to be dangerous or irrelevant. E.g., RRs with suspiciously high TTLs, unsolicited root information, or that just don't appear to be relevant to the question the resolver asked.
.1.3.6.1.2.1.32.2.1.4.5,DNS-RESOLVER-MIB::dnsResCacheRRTable,,not-accessible,,current,,This table contains information about all the resource records currently in the resolver's cache.
.1.3.6.1.2.1.32.2.1.4.5.1,DNS-RESOLVER-MIB::dnsResCacheRREntry,,not-accessible,dnsResCacheRRName:dnsResCacheRRClass:dnsResCacheRRType:dnsResCacheRRIndex,current,,An entry in the resolvers's cache. Rows may be created only by the resolver. SNMP SET requests may be used to delete rows.
.1.3.6.1.2.1.32.2.1.4.5.1.1,DNS-RESOLVER-MIB::dnsResCacheRRName,OCTET,not-accessible,,current,,Owner name of the Resource Record in the cache which is identified in this row of the table. As described in RFC-1034, the owner of the record is the domain name were the RR is found.
.1.3.6.1.2.1.32.2.1.4.5.1.2,DNS-RESOLVER-MIB::dnsResCacheRRClass,INTEGER,not-accessible,,current,,DNS class of the Resource Record in the cache which is identified in this row of the table.
.1.3.6.1.2.1.32.2.1.4.5.1.3,DNS-RESOLVER-MIB::dnsResCacheRRType,INTEGER,not-accessible,,current,,DNS type of the Resource Record in the cache which is identified in this row of the table.
.1.3.6.1.2.1.32.2.1.4.5.1.4,DNS-RESOLVER-MIB::dnsResCacheRRTTL,Gauge32,read-only,,current,,Time-To-Live of RR in DNS cache. This is the initial TTL value which was received with the RR when it was originally received.
.1.3.6.1.2.1.32.2.1.4.5.1.5,DNS-RESOLVER-MIB::dnsResCacheRRElapsedTTL,Gauge32,read-only,,current,,Elapsed seconds since RR was received.
.1.3.6.1.2.1.32.2.1.4.5.1.6,DNS-RESOLVER-MIB::dnsResCacheRRSource,IpAddress,read-only,,current,,Host from which RR was received, 0.0.0.0 if unknown.
.1.3.6.1.2.1.32.2.1.4.5.1.7,DNS-RESOLVER-MIB::dnsResCacheRRData,OCTET,read-only,,current,,RDATA portion of a cached RR. The value is in the format defined for the particular DNS class and type of the resource record.
.1.3.6.1.2.1.32.2.1.4.5.1.8,DNS-RESOLVER-MIB::dnsResCacheRRStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status column for the resolver cache table. Since only the agent (DNS resolver) creates rows in this table, the only values that a manager may write to this variable are active(1) and destroy(6).
.1.3.6.1.2.1.32.2.1.4.5.1.9,DNS-RESOLVER-MIB::dnsResCacheRRIndex,Integer32,not-accessible,,current,,A value which makes entries in the table unique when the other index values (dnsResCacheRRName, dnsResCacheRRClass, and dnsResCacheRRType) do not provide a unique index.
.1.3.6.1.2.1.32.2.1.4.5.1.10,DNS-RESOLVER-MIB::dnsResCacheRRPrettyName,OCTET,read-only,,current,,Name of the RR at this row in the table. This is identical to the dnsResCacheRRName variable, except that character case is preserved in this variable, per DNS conventions.
.1.3.6.1.2.1.32.2.1.5,DNS-RESOLVER-MIB::dnsResNCache,,,,,,
.1.3.6.1.2.1.32.2.1.5.1,DNS-RESOLVER-MIB::dnsResNCacheStatus,INTEGER,read-write,,current,enabled(1):disabled(2):clear(3),Status/action for the resolver's negative response cache. enabled(1) means that the use of the negative response cache is allowed. Query operations can return this state. disabled(2) means that the negative response cache is not being used. Query operations can return this state. Setting this variable to clear(3) deletes the entire contents of the resolver's negative response cache. The status will retain its previous value from before the clear operation (i.e., enabled(1) or disabled(2)). The value of clear(3) can NOT be returned by a query operation.
.1.3.6.1.2.1.32.2.1.5.2,DNS-RESOLVER-MIB::dnsResNCacheMaxTTL,Gauge32,read-write,,current,,Maximum Time-To-Live for cached authoritative errors. If the resolver does not implement a TTL ceiling, the value of this field should be zero.
.1.3.6.1.2.1.32.2.1.5.3,DNS-RESOLVER-MIB::dnsResNCacheGoodNCaches,Counter32,read-only,,current,,Number of authoritative errors the resolver has cached successfully.
.1.3.6.1.2.1.32.2.1.5.4,DNS-RESOLVER-MIB::dnsResNCacheBadNCaches,Counter32,read-only,,current,,Number of authoritative errors the resolver would have liked to cache but was unable to because the appropriate SOA RR was not supplied or looked suspicious.
.1.3.6.1.2.1.32.2.1.5.5,DNS-RESOLVER-MIB::dnsResNCacheErrTable,,not-accessible,,current,,The resolver's negative response cache. This table contains information about authoritative errors that have been cached by the resolver.
.1.3.6.1.2.1.32.2.1.5.5.1,DNS-RESOLVER-MIB::dnsResNCacheErrEntry,,not-accessible,dnsResNCacheErrQName:dnsResNCacheErrQClass:dnsResNCacheErrQType:dnsResNCacheErrIndex,current,,An entry in the resolver's negative response cache table. Only the resolver can create rows. SNMP SET requests may be used to delete rows.
.1.3.6.1.2.1.32.2.1.5.5.1.1,DNS-RESOLVER-MIB::dnsResNCacheErrQName,OCTET,not-accessible,,current,,QNAME associated with a cached authoritative error.
.1.3.6.1.2.1.32.2.1.5.5.1.2,DNS-RESOLVER-MIB::dnsResNCacheErrQClass,INTEGER,not-accessible,,current,,DNS QCLASS associated with a cached authoritative error.
.1.3.6.1.2.1.32.2.1.5.5.1.3,DNS-RESOLVER-MIB::dnsResNCacheErrQType,INTEGER,not-accessible,,current,,DNS QTYPE associated with a cached authoritative error.
.1.3.6.1.2.1.32.2.1.5.5.1.4,DNS-RESOLVER-MIB::dnsResNCacheErrTTL,Gauge32,read-only,,current,,Time-To-Live of a cached authoritative error at the time of the error, it should not be decremented by the number of seconds since it was received. This should be the TTL as copied from the MINIMUM field of the SOA that accompanied the authoritative error, or a smaller value if the resolver implements a ceiling on negative response cache TTLs.
.1.3.6.1.2.1.32.2.1.5.5.1.5,DNS-RESOLVER-MIB::dnsResNCacheErrElapsedTTL,Gauge32,read-only,,current,,Elapsed seconds since authoritative error was received.
.1.3.6.1.2.1.32.2.1.5.5.1.6,DNS-RESOLVER-MIB::dnsResNCacheErrSource,IpAddress,read-only,,current,,Host which sent the authoritative error, 0.0.0.0 if unknown.
.1.3.6.1.2.1.32.2.1.5.5.1.7,DNS-RESOLVER-MIB::dnsResNCacheErrCode,INTEGER,read-only,,current,nonexistantName(1):noData(2):other(3),The authoritative error that has been cached: nonexistantName(1) indicates an authoritative name error (RCODE = 3). noData(2) indicates an authoritative response with no error (RCODE = 0) and no relevant data. other(3) indicates some other cached authoritative error. At present, no such errors are known to exist.
.1.3.6.1.2.1.32.2.1.5.5.1.8,DNS-RESOLVER-MIB::dnsResNCacheErrStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Status column for the resolver negative response cache table. Since only the agent (DNS resolver) creates rows in this table, the only values that a manager may write to this variable are active(1) and destroy(6).
.1.3.6.1.2.1.32.2.1.5.5.1.9,DNS-RESOLVER-MIB::dnsResNCacheErrIndex,Integer32,read-only,,current,,A value which makes entries in the table unique when the other index values (dnsResNCacheErrQName, dnsResNCacheErrQClass, and dnsResNCacheErrQType) do not provide a unique index.
.1.3.6.1.2.1.32.2.1.5.5.1.10,DNS-RESOLVER-MIB::dnsResNCacheErrPrettyName,OCTET,read-only,,current,,QNAME associated with this row in the table. This is identical to the dnsResNCacheErrQName variable, except that character case is preserved in this variable, per DNS conventions.
.1.3.6.1.2.1.32.2.1.6,DNS-RESOLVER-MIB::dnsResOptCounter,,,,,,
.1.3.6.1.2.1.32.2.1.6.1,DNS-RESOLVER-MIB::dnsResOptCounterReferals,Counter32,read-only,,current,,Number of responses which were received from servers redirecting query to another server.
.1.3.6.1.2.1.32.2.1.6.2,DNS-RESOLVER-MIB::dnsResOptCounterRetrans,Counter32,read-only,,current,,Number requests retransmitted for all reasons.
.1.3.6.1.2.1.32.2.1.6.3,DNS-RESOLVER-MIB::dnsResOptCounterNoResponses,Counter32,read-only,,current,,Number of queries that were retransmitted because of no response.
.1.3.6.1.2.1.32.2.1.6.4,DNS-RESOLVER-MIB::dnsResOptCounterRootRetrans,Counter32,read-only,,current,,Number of queries that were retransmitted that were to root servers.
.1.3.6.1.2.1.32.2.1.6.5,DNS-RESOLVER-MIB::dnsResOptCounterInternals,Counter32,read-only,,current,,Number of requests internally generated by the resolver.
.1.3.6.1.2.1.32.2.1.6.6,DNS-RESOLVER-MIB::dnsResOptCounterInternalTimeOuts,Counter32,read-only,,current,,Number of requests internally generated which timed out.
.1.3.6.1.2.1.32.2.2,DNS-RESOLVER-MIB::dnsResMIBGroups,,,,,,
.1.3.6.1.2.1.32.2.2.1,DNS-RESOLVER-MIB::dnsResConfigGroup,,,,,,A collection of objects providing basic configuration information for a DNS resolver implementation.
.1.3.6.1.2.1.32.2.2.2,DNS-RESOLVER-MIB::dnsResCounterGroup,,,,,,A collection of objects providing basic instrumentation of a DNS resolver implementation.
.1.3.6.1.2.1.32.2.2.3,DNS-RESOLVER-MIB::dnsResLameDelegationGroup,,,,,,A collection of objects providing instrumentation of `lame delegation' failures.
.1.3.6.1.2.1.32.2.2.4,DNS-RESOLVER-MIB::dnsResCacheGroup,,,,,,A collection of objects providing access to and control of a DNS resolver's cache.
.1.3.6.1.2.1.32.2.2.5,DNS-RESOLVER-MIB::dnsResNCacheGroup,,,,,,A collection of objects providing access to and control of a DNS resolver's negative response cache.
.1.3.6.1.2.1.32.2.2.6,DNS-RESOLVER-MIB::dnsResOptCounterGroup,,,,,,A collection of objects providing further instrumentation applicable to many but not all DNS resolvers.
.1.3.6.1.2.1.32.2.3,DNS-RESOLVER-MIB::dnsResMIBCompliances,,,,,,
.1.3.6.1.2.1.32.2.3.1,DNS-RESOLVER-MIB::dnsResMIBCompliance,,,,,,The compliance statement for agents implementing the DNS resolver MIB extensions.
.1.3.6.1.2.1.33,UPS-MIB::upsMIB,,,,,,The MIB module to describe Uninterruptible Power Supplies.
.1.3.6.1.2.1.33.1,UPS-MIB::upsObjects,,,,,,
.1.3.6.1.2.1.33.1.1,UPS-MIB::upsIdent,,,,,,
.1.3.6.1.2.1.33.1.1.1,UPS-MIB::upsIdentManufacturer,OCTET,read-only,,current,,The name of the UPS manufacturer.
.1.3.6.1.2.1.33.1.1.2,UPS-MIB::upsIdentModel,OCTET,read-only,,current,,The UPS Model designation.
.1.3.6.1.2.1.33.1.1.3,UPS-MIB::upsIdentUPSSoftwareVersion,OCTET,read-only,,current,,The UPS firmware/software version(s). This variable may or may not have the same value as upsIdentAgentSoftwareVersion in some implementations.
.1.3.6.1.2.1.33.1.1.4,UPS-MIB::upsIdentAgentSoftwareVersion,OCTET,read-only,,current,,The UPS agent software version. This variable may or may not have the same value as upsIdentUPSSoftwareVersion in some implementations.
.1.3.6.1.2.1.33.1.1.5,UPS-MIB::upsIdentName,OCTET,read-write,,current,,A string identifying the UPS. This object should be set by the administrator.
.1.3.6.1.2.1.33.1.1.6,UPS-MIB::upsIdentAttachedDevices,OCTET,read-write,,current,,A string identifying the devices attached to the output(s) of the UPS. This object should be set by the administrator.
.1.3.6.1.2.1.33.1.2,UPS-MIB::upsBattery,,,,,,
.1.3.6.1.2.1.33.1.2.1,UPS-MIB::upsBatteryStatus,INTEGER,read-only,,current,unknown(1):batteryNormal(2):batteryLow(3):batteryDepleted(4),The indication of the capacity remaining in the UPS system's batteries. A value of batteryNormal indicates that the remaining run-time is greater than upsConfigLowBattTime. A value of batteryLow indicates that the remaining battery run-time is less than or equal to upsConfigLowBattTime. A value of batteryDepleted indicates that the UPS will be unable to sustain the present load when and if the utility power is lost (including the possibility that the utility power is currently absent and the UPS is unable to sustain the output).
.1.3.6.1.2.1.33.1.2.2,UPS-MIB::upsSecondsOnBattery,INTEGER,read-only,,current,,If the unit is on battery power, the elapsed time since the UPS last switched to battery power, or the time since the network management subsystem was last restarted, whichever is less. Zero shall be returned if the unit is not on battery power.
.1.3.6.1.2.1.33.1.2.3,UPS-MIB::upsEstimatedMinutesRemaining,INTEGER,read-only,,current,,An estimate of the time to battery charge depletion under the present load conditions if the utility power is off and remains off, or if it were to be lost and remain off.
.1.3.6.1.2.1.33.1.2.4,UPS-MIB::upsEstimatedChargeRemaining,INTEGER,read-only,,current,,An estimate of the battery charge remaining expressed as a percent of full charge.
.1.3.6.1.2.1.33.1.2.5,UPS-MIB::upsBatteryVoltage,INTEGER,read-only,,current,,The magnitude of the present battery voltage.
.1.3.6.1.2.1.33.1.2.6,UPS-MIB::upsBatteryCurrent,Integer32,read-only,,current,,The present battery current.
.1.3.6.1.2.1.33.1.2.7,UPS-MIB::upsBatteryTemperature,Integer32,read-only,,current,,The ambient temperature at or near the UPS Battery casing.
.1.3.6.1.2.1.33.1.3,UPS-MIB::upsInput,,,,,,
.1.3.6.1.2.1.33.1.3.1,UPS-MIB::upsInputLineBads,Counter32,read-only,,current,,A count of the number of times the input entered an out-of-tolerance condition as defined by the manufacturer. This count is incremented by one each time the input transitions from zero out-of-tolerance lines to one or more input lines out-of-tolerance.
.1.3.6.1.2.1.33.1.3.2,UPS-MIB::upsInputNumLines,INTEGER,read-only,,current,,The number of input lines utilized in this device. This variable indicates the number of rows in the input table.
.1.3.6.1.2.1.33.1.3.3,UPS-MIB::upsInputTable,,not-accessible,,current,,A list of input table entries. The number of entries is given by the value of upsInputNumLines.
.1.3.6.1.2.1.33.1.3.3.1,UPS-MIB::upsInputEntry,,not-accessible,upsInputLineIndex,current,,An entry containing information applicable to a particular input line.
.1.3.6.1.2.1.33.1.3.3.1.1,UPS-MIB::upsInputLineIndex,INTEGER,not-accessible,,current,,The input line identifier.
.1.3.6.1.2.1.33.1.3.3.1.2,UPS-MIB::upsInputFrequency,INTEGER,read-only,,current,,The present input frequency.
.1.3.6.1.2.1.33.1.3.3.1.3,UPS-MIB::upsInputVoltage,INTEGER,read-only,,current,,The magnitude of the present input voltage.
.1.3.6.1.2.1.33.1.3.3.1.4,UPS-MIB::upsInputCurrent,INTEGER,read-only,,current,,The magnitude of the present input current.
.1.3.6.1.2.1.33.1.3.3.1.5,UPS-MIB::upsInputTruePower,INTEGER,read-only,,current,,The magnitude of the present input true power.
.1.3.6.1.2.1.33.1.4,UPS-MIB::upsOutput,,,,,,
.1.3.6.1.2.1.33.1.4.1,UPS-MIB::upsOutputSource,INTEGER,read-only,,current,other(1):none(2):normal(3):bypass(4):battery(5):booster(6):reducer(7),The present source of output power. The enumeration none(2) indicates that there is no source of output power (and therefore no output power), for example, the system has opened the output breaker.
.1.3.6.1.2.1.33.1.4.2,UPS-MIB::upsOutputFrequency,INTEGER,read-only,,current,,The present output frequency.
.1.3.6.1.2.1.33.1.4.3,UPS-MIB::upsOutputNumLines,INTEGER,read-only,,current,,The number of output lines utilized in this device. This variable indicates the number of rows in the output table.
.1.3.6.1.2.1.33.1.4.4,UPS-MIB::upsOutputTable,,not-accessible,,current,,A list of output table entries. The number of entries is given by the value of upsOutputNumLines.
.1.3.6.1.2.1.33.1.4.4.1,UPS-MIB::upsOutputEntry,,not-accessible,upsOutputLineIndex,current,,An entry containing information applicable to a particular output line.
.1.3.6.1.2.1.33.1.4.4.1.1,UPS-MIB::upsOutputLineIndex,INTEGER,not-accessible,,current,,The output line identifier.
.1.3.6.1.2.1.33.1.4.4.1.2,UPS-MIB::upsOutputVoltage,INTEGER,read-only,,current,,The present output voltage.
.1.3.6.1.2.1.33.1.4.4.1.3,UPS-MIB::upsOutputCurrent,INTEGER,read-only,,current,,The present output current.
.1.3.6.1.2.1.33.1.4.4.1.4,UPS-MIB::upsOutputPower,INTEGER,read-only,,current,,The present output true power.
.1.3.6.1.2.1.33.1.4.4.1.5,UPS-MIB::upsOutputPercentLoad,INTEGER,read-only,,current,,The percentage of the UPS power capacity presently being used on this output line, i.e., the greater of the percent load of true power capacity and the percent load of VA.
.1.3.6.1.2.1.33.1.5,UPS-MIB::upsBypass,,,,,,
.1.3.6.1.2.1.33.1.5.1,UPS-MIB::upsBypassFrequency,INTEGER,read-only,,current,,The present bypass frequency.
.1.3.6.1.2.1.33.1.5.2,UPS-MIB::upsBypassNumLines,INTEGER,read-only,,current,,The number of bypass lines utilized in this device. This entry indicates the number of rows in the bypass table.
.1.3.6.1.2.1.33.1.5.3,UPS-MIB::upsBypassTable,,not-accessible,,current,,A list of bypass table entries. The number of entries is given by the value of upsBypassNumLines.
.1.3.6.1.2.1.33.1.5.3.1,UPS-MIB::upsBypassEntry,,not-accessible,upsBypassLineIndex,current,,An entry containing information applicable to a particular bypass input.
.1.3.6.1.2.1.33.1.5.3.1.1,UPS-MIB::upsBypassLineIndex,INTEGER,not-accessible,,current,,The bypass line identifier.
.1.3.6.1.2.1.33.1.5.3.1.2,UPS-MIB::upsBypassVoltage,INTEGER,read-only,,current,,The present bypass voltage.
.1.3.6.1.2.1.33.1.5.3.1.3,UPS-MIB::upsBypassCurrent,INTEGER,read-only,,current,,The present bypass current.
.1.3.6.1.2.1.33.1.5.3.1.4,UPS-MIB::upsBypassPower,INTEGER,read-only,,current,,The present true power conveyed by the bypass.
.1.3.6.1.2.1.33.1.6,UPS-MIB::upsAlarm,,,,,,
.1.3.6.1.2.1.33.1.6.1,UPS-MIB::upsAlarmsPresent,Gauge32,read-only,,current,,The present number of active alarm conditions.
.1.3.6.1.2.1.33.1.6.2,UPS-MIB::upsAlarmTable,,not-accessible,,current,,A list of alarm table entries. The table contains zero, one, or many rows at any moment, depending upon the number of alarm conditions in effect. The table is initially empty at agent startup. The agent creates a row in the table each time a condition is detected and deletes that row when that condition no longer pertains. The agent creates the first row with upsAlarmId equal to 1, and increments the value of upsAlarmId each time a new row is created, wrapping to the first free value greater than or equal to 1 when the maximum value of upsAlarmId would otherwise be exceeded. Consequently, after multiple operations, the table may become sparse, e.g., containing entries for rows 95, 100, 101, and 203 and the entries should not be assumed to be in chronological order because upsAlarmId might have wrapped. Alarms are named by an AutonomousType (OBJECT IDENTIFIER), upsAlarmDescr, to allow a single table to reflect well known alarms plus alarms defined by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. No two rows will have the same value of upsAlarmDescr, since alarms define conditions. In order to meet this requirement, care should be taken in the definition of alarm conditions to insure that a system cannot enter the same condition multiple times simultaneously. The number of rows in the table at any given time is reflected by the value of upsAlarmsPresent.
.1.3.6.1.2.1.33.1.6.2.1,UPS-MIB::upsAlarmEntry,,not-accessible,upsAlarmId,current,,An entry containing information applicable to a particular alarm.
.1.3.6.1.2.1.33.1.6.2.1.1,UPS-MIB::upsAlarmId,INTEGER,not-accessible,,current,,A unique identifier for an alarm condition. This value must remain constant.
.1.3.6.1.2.1.33.1.6.2.1.2,UPS-MIB::upsAlarmDescr,OBJECT,read-only,,current,,A reference to an alarm description object. The object referenced should not be accessible, but rather be used to provide a unique description of the alarm condition.
.1.3.6.1.2.1.33.1.6.2.1.3,UPS-MIB::upsAlarmTime,TimeTicks,read-only,,current,,The value of sysUpTime when the alarm condition was detected. If the alarm condition was detected at the time of agent startup and presumably existed before agent startup, the value of upsAlarmTime shall equal 0.
.1.3.6.1.2.1.33.1.6.3,UPS-MIB::upsWellKnownAlarms,,,,,,
.1.3.6.1.2.1.33.1.6.3.1,UPS-MIB::upsAlarmBatteryBad,,,,,,One or more batteries have been determined to require replacement.
.1.3.6.1.2.1.33.1.6.3.2,UPS-MIB::upsAlarmOnBattery,,,,,,The UPS is drawing power from the batteries.
.1.3.6.1.2.1.33.1.6.3.3,UPS-MIB::upsAlarmLowBattery,,,,,,The remaining battery run-time is less than or equal to upsConfigLowBattTime.
.1.3.6.1.2.1.33.1.6.3.4,UPS-MIB::upsAlarmDepletedBattery,,,,,,The UPS will be unable to sustain the present load when and if the utility power is lost.
.1.3.6.1.2.1.33.1.6.3.5,UPS-MIB::upsAlarmTempBad,,,,,,A temperature is out of tolerance.
.1.3.6.1.2.1.33.1.6.3.6,UPS-MIB::upsAlarmInputBad,,,,,,An input condition is out of tolerance.
.1.3.6.1.2.1.33.1.6.3.7,UPS-MIB::upsAlarmOutputBad,,,,,,An output condition (other than OutputOverload) is out of tolerance.
.1.3.6.1.2.1.33.1.6.3.8,UPS-MIB::upsAlarmOutputOverload,,,,,,The output load exceeds the UPS output capacity.
.1.3.6.1.2.1.33.1.6.3.9,UPS-MIB::upsAlarmOnBypass,,,,,,The Bypass is presently engaged on the UPS.
.1.3.6.1.2.1.33.1.6.3.10,UPS-MIB::upsAlarmBypassBad,,,,,,The Bypass is out of tolerance.
.1.3.6.1.2.1.33.1.6.3.11,UPS-MIB::upsAlarmOutputOffAsRequested,,,,,,The UPS has shutdown as requested, i.e., the output is off.
.1.3.6.1.2.1.33.1.6.3.12,UPS-MIB::upsAlarmUpsOffAsRequested,,,,,,The entire UPS has shutdown as commanded.
.1.3.6.1.2.1.33.1.6.3.13,UPS-MIB::upsAlarmChargerFailed,,,,,,An uncorrected problem has been detected within the UPS charger subsystem.
.1.3.6.1.2.1.33.1.6.3.14,UPS-MIB::upsAlarmUpsOutputOff,,,,,,The output of the UPS is in the off state.
.1.3.6.1.2.1.33.1.6.3.15,UPS-MIB::upsAlarmUpsSystemOff,,,,,,The UPS system is in the off state.
.1.3.6.1.2.1.33.1.6.3.16,UPS-MIB::upsAlarmFanFailure,,,,,,The failure of one or more fans in the UPS has been detected.
.1.3.6.1.2.1.33.1.6.3.17,UPS-MIB::upsAlarmFuseFailure,,,,,,The failure of one or more fuses has been detected.
.1.3.6.1.2.1.33.1.6.3.18,UPS-MIB::upsAlarmGeneralFault,,,,,,A general fault in the UPS has been detected.
.1.3.6.1.2.1.33.1.6.3.19,UPS-MIB::upsAlarmDiagnosticTestFailed,,,,,,The result of the last diagnostic test indicates a failure.
.1.3.6.1.2.1.33.1.6.3.20,UPS-MIB::upsAlarmCommunicationsLost,,,,,,A problem has been encountered in the communications between the agent and the UPS.
.1.3.6.1.2.1.33.1.6.3.21,UPS-MIB::upsAlarmAwaitingPower,,,,,,The UPS output is off and the UPS is awaiting the return of input power.
.1.3.6.1.2.1.33.1.6.3.22,UPS-MIB::upsAlarmShutdownPending,,,,,,A upsShutdownAfterDelay countdown is underway.
.1.3.6.1.2.1.33.1.6.3.23,UPS-MIB::upsAlarmShutdownImminent,,,,,,The UPS will turn off power to the load in less than 5 seconds; this may be either a timed shutdown or a low battery shutdown.
.1.3.6.1.2.1.33.1.6.3.24,UPS-MIB::upsAlarmTestInProgress,,,,,,A test is in progress, as initiated and indicated by the Test Group. Tests initiated via other implementation-specific mechanisms can indicate the presence of the testing in the alarm table, if desired, via a OBJECT-IDENTITY macro in the MIB document specific to that implementation and are outside the scope of this OBJECT-IDENTITY.
.1.3.6.1.2.1.33.1.7,UPS-MIB::upsTest,,,,,,
.1.3.6.1.2.1.33.1.7.1,UPS-MIB::upsTestId,OBJECT,read-write,,current,,The test is named by an OBJECT IDENTIFIER which allows a standard mechanism for the initiation of tests, including the well known tests identified in this document as well as those introduced by a particular implementation, i.e., as documented in the private enterprise MIB definition for the device. Setting this variable initiates the named test. Sets to this variable require the presence of upsTestSpinLock in the same SNMP message. The set request will be rejected with an appropriate error message if the requested test cannot be performed, including attempts to start a test when another test is already in progress. The status of the current or last test is maintained in upsTestResultsSummary. Tests in progress may be aborted by setting the upsTestId variable to upsTestAbortTestInProgress. Read operations return the value of the name of the test in progress if a test is in progress or the name of the last test performed if no test is in progress, unless no test has been run, in which case the well known value upsTestNoTestsInitiated is returned.
.1.3.6.1.2.1.33.1.7.2,UPS-MIB::upsTestSpinLock,INTEGER,read-write,,current,,A spin lock on the test subsystem. The spinlock is used as follows. Before starting a test, a manager-station should make sure that a test is not in progress as follows: try_again: get (upsTestSpinLock) while (upsTestResultsSummary == inProgress) { /* loop while a test is running for another manager */ short delay get (upsTestSpinLock) } lock_value = upsTestSpinLock /* no test in progress, start the test */ set (upsTestSpinLock = lock_value, upsTestId = requested_test) if (error_index == 1) { /* (upsTestSpinLock failed) */ /* if problem is not access control, then some other manager slipped in ahead of us */ goto try_again } if (error_index == 2) { /* (upsTestId) */ /* cannot perform the test */ give up } /* test started ok */ /* wait for test completion by polling upsTestResultsSummary */ get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) while (upsTestResultsSummary == inProgress) { short delay get (upsTestSpinLock, upsTestResultsSummary, upsTestResultsDetail) } /* when test completes, retrieve any additional test results */ /* if upsTestSpinLock == lock_value + 1, then these are our test */ /* results (as opposed to another manager's */ The initial value of upsTestSpinLock at agent initialization shall be 1.
.1.3.6.1.2.1.33.1.7.3,UPS-MIB::upsTestResultsSummary,INTEGER,read-only,,current,donePass(1):doneWarning(2):doneError(3):aborted(4):inProgress(5):noTestsInitiated(6),The results of the current or last UPS diagnostics test performed. The values for donePass(1), doneWarning(2), and doneError(3) indicate that the test completed either successfully, with a warning, or with an error, respectively. The value aborted(4) is returned for tests which are aborted by setting the value of upsTestId to upsTestAbortTestInProgress. Tests which have not yet concluded are indicated by inProgress(5). The value noTestsInitiated(6) indicates that no previous test results are available, such as is the case when no tests have been run since the last reinitialization of the network management subsystem and the system has no provision for non- volatile storage of test results.
.1.3.6.1.2.1.33.1.7.4,UPS-MIB::upsTestResultsDetail,OCTET,read-only,,current,,Additional information about upsTestResultsSummary. If no additional information available, a zero length string is returned.
.1.3.6.1.2.1.33.1.7.5,UPS-MIB::upsTestStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time the test in progress was initiated, or, if no test is in progress, the time the previous test was initiated. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestStartTime has the value 0.
.1.3.6.1.2.1.33.1.7.6,UPS-MIB::upsTestElapsedTime,INTEGER,read-only,,current,,The amount of time, in TimeTicks, since the test in progress was initiated, or, if no test is in progress, the previous test took to complete. If the value of upsTestResultsSummary is noTestsInitiated(6), upsTestElapsedTime has the value 0.
.1.3.6.1.2.1.33.1.7.7,UPS-MIB::upsWellKnownTests,,,,,,
.1.3.6.1.2.1.33.1.7.7.1,UPS-MIB::upsTestNoTestsInitiated,,,,,,No tests have been initiated and no test is in progress.
.1.3.6.1.2.1.33.1.7.7.2,UPS-MIB::upsTestAbortTestInProgress,,,,,,The test in progress is to be aborted / the test in progress was aborted.
.1.3.6.1.2.1.33.1.7.7.3,UPS-MIB::upsTestGeneralSystemsTest,,,,,,The manufacturer's standard test of UPS device systems.
.1.3.6.1.2.1.33.1.7.7.4,UPS-MIB::upsTestQuickBatteryTest,,,,,,A test that is sufficient to determine if the battery needs replacement.
.1.3.6.1.2.1.33.1.7.7.5,UPS-MIB::upsTestDeepBatteryCalibration,,,,,,The system is placed on battery to a discharge level, set by the manufacturer, sufficient to determine battery replacement and battery run-time with a high degree of confidence. WARNING: this test will leave the battery in a low charge state and will require time for recharging to a level sufficient to provide normal battery duration for the protected load.
.1.3.6.1.2.1.33.1.8,UPS-MIB::upsControl,,,,,,
.1.3.6.1.2.1.33.1.8.1,UPS-MIB::upsShutdownType,INTEGER,read-write,,current,output(1):system(2),This object determines the nature of the action to be taken at the time when the countdown of the upsShutdownAfterDelay and upsRebootWithDuration objects reaches zero. Setting this object to output(1) indicates that shutdown requests should cause only the output of the UPS to turn off. Setting this object to system(2) indicates that shutdown requests will cause the entire UPS system to turn off.
.1.3.6.1.2.1.33.1.8.2,UPS-MIB::upsShutdownAfterDelay,INTEGER,read-write,,current,,Setting this object will shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) after the indicated number of seconds, or less if the UPS batteries become depleted. Setting this object to 0 will cause the shutdown to occur immediately. Setting this object to -1 will abort the countdown. If the system is already in the desired state at the time the countdown reaches 0, then nothing will happen. That is, there is no additional action at that time if upsShutdownType = system and the system is already off. Similarly, there is no additional action at that time if upsShutdownType = output and the output is already off. When read, upsShutdownAfterDelay will return the number of seconds remaining until shutdown, or -1 if no shutdown countdown is in effect. On some systems, if the agent is restarted while a shutdown countdown is in effect, the countdown may be aborted. Sets to this object override any upsShutdownAfterDelay already in effect.
.1.3.6.1.2.1.33.1.8.3,UPS-MIB::upsStartupAfterDelay,INTEGER,read-write,,current,,Setting this object will start the output after the indicated number of seconds, including starting the UPS, if necessary. Setting this object to 0 will cause the startup to occur immediately. Setting this object to -1 will abort the countdown. If the output is already on at the time the countdown reaches 0, then nothing will happen. Sets to this object override the effect of any upsStartupAfterDelay countdown or upsRebootWithDuration countdown in progress. When read, upsStartupAfterDelay will return the number of seconds until startup, or -1 if no startup countdown is in effect. If the countdown expires during a utility failure, the startup shall not occur until the utility power is restored. On some systems, if the agent is restarted while a startup countdown is in effect, the countdown is aborted.
.1.3.6.1.2.1.33.1.8.4,UPS-MIB::upsRebootWithDuration,INTEGER,read-write,,current,,Setting this object will immediately shutdown (i.e., turn off) either the UPS output or the UPS system (as determined by the value of upsShutdownType at the time of shutdown) for a period equal to the indicated number of seconds, after which time the output will be started, including starting the UPS, if necessary. If the number of seconds required to perform the request is greater than the requested duration, then the requested shutdown and startup cycle shall be performed in the minimum time possible, but in no case shall this require more than the requested duration plus 60 seconds. When read, upsRebootWithDuration shall return the number of seconds remaining in the countdown, or -1 if no countdown is in progress. If the startup should occur during a utility failure, the startup shall not occur until the utility power is restored.
.1.3.6.1.2.1.33.1.8.5,UPS-MIB::upsAutoRestart,INTEGER,read-write,,current,on(1):off(2),Setting this object to 'on' will cause the UPS system to restart after a shutdown if the shutdown occurred during a power loss as a result of either a upsShutdownAfterDelay or an internal battery depleted condition. Setting this object to 'off' will prevent the UPS system from restarting after a shutdown until an operator manually or remotely explicitly restarts it. If the UPS is in a startup or reboot countdown, then the UPS will not restart until that delay has been satisfied.
.1.3.6.1.2.1.33.1.9,UPS-MIB::upsConfig,,,,,,
.1.3.6.1.2.1.33.1.9.1,UPS-MIB::upsConfigInputVoltage,INTEGER,read-write,,current,,The magnitude of the nominal input voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.
.1.3.6.1.2.1.33.1.9.2,UPS-MIB::upsConfigInputFreq,INTEGER,read-write,,current,,The nominal input frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.
.1.3.6.1.2.1.33.1.9.3,UPS-MIB::upsConfigOutputVoltage,INTEGER,read-write,,current,,The magnitude of the nominal output voltage. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.
.1.3.6.1.2.1.33.1.9.4,UPS-MIB::upsConfigOutputFreq,INTEGER,read-write,,current,,The nominal output frequency. On those systems which support read-write access to this object, if there is an attempt to set this variable to a value that is not supported, the request must be rejected and the agent shall respond with an appropriate error message, i.e., badValue for SNMPv1, or inconsistentValue for SNMPv2.
.1.3.6.1.2.1.33.1.9.5,UPS-MIB::upsConfigOutputVA,INTEGER,read-only,,current,,The magnitude of the nominal Volt-Amp rating.
.1.3.6.1.2.1.33.1.9.6,UPS-MIB::upsConfigOutputPower,INTEGER,read-only,,current,,The magnitude of the nominal true power rating.
.1.3.6.1.2.1.33.1.9.7,UPS-MIB::upsConfigLowBattTime,INTEGER,read-write,,current,,The value of upsEstimatedMinutesRemaining at which a lowBattery condition is declared. For agents which support only discrete (discontinuous) values, then the agent shall round up to the next supported value. If the requested value is larger than the largest supported value, then the largest supported value shall be selected.
.1.3.6.1.2.1.33.1.9.8,UPS-MIB::upsConfigAudibleStatus,INTEGER,read-write,,current,disabled(1):enabled(2):muted(3),The requested state of the audible alarm. When in the disabled state, the audible alarm should never sound. The enabled state is self-describing. Setting this object to muted(3) when the audible alarm is sounding shall temporarily silence the alarm. It will remain muted until it would normally stop sounding and the value returned for read operations during this period shall equal muted(3). At the end of this period, the value shall revert to enabled(2). Writes of the value muted(3) when the audible alarm is not sounding shall be accepted but otherwise shall have no effect.
.1.3.6.1.2.1.33.1.9.9,UPS-MIB::upsConfigLowVoltageTransferPoint,INTEGER,read-write,,current,,The minimum input line voltage allowed before the UPS system transfers to battery backup.
.1.3.6.1.2.1.33.1.9.10,UPS-MIB::upsConfigHighVoltageTransferPoint,INTEGER,read-write,,current,,The maximum line voltage allowed before the UPS system transfers to battery backup.
.1.3.6.1.2.1.33.2,UPS-MIB::upsTraps,,,,,,
.1.3.6.1.2.1.33.2.1,UPS-MIB::upsTrapOnBattery,,,,,,The UPS is operating on battery power. This trap is persistent and is resent at one minute intervals until the UPS either turns off or is no longer running on battery.
.1.3.6.1.2.1.33.2.2,UPS-MIB::upsTrapTestCompleted,,,,,,This trap is sent upon completion of a UPS diagnostic test.
.1.3.6.1.2.1.33.2.3,UPS-MIB::upsTrapAlarmEntryAdded,,,,,,This trap is sent each time an alarm is inserted into to the alarm table. It is sent on the insertion of all alarms except for upsAlarmOnBattery and upsAlarmTestInProgress.
.1.3.6.1.2.1.33.2.4,UPS-MIB::upsTrapAlarmEntryRemoved,,,,,,This trap is sent each time an alarm is removed from the alarm table. It is sent on the removal of all alarms except for upsAlarmTestInProgress.
.1.3.6.1.2.1.33.3,UPS-MIB::upsConformance,,,,,,
.1.3.6.1.2.1.33.3.1,UPS-MIB::upsCompliances,,,,,,
.1.3.6.1.2.1.33.3.1.1,UPS-MIB::upsSubsetCompliance,,,,,,The compliance statement for UPSs that only support the two-contact communication protocol.
.1.3.6.1.2.1.33.3.1.2,UPS-MIB::upsBasicCompliance,,,,,,The compliance statement for UPSs that support full-featured functions, such as control.
.1.3.6.1.2.1.33.3.1.3,UPS-MIB::upsFullCompliance,,,,,,The compliance statement for UPSs that support advanced full-featured functions.
.1.3.6.1.2.1.33.3.2,UPS-MIB::upsGroups,,,,,,
.1.3.6.1.2.1.33.3.2.1,UPS-MIB::upsSubsetGroups,,,,,,
.1.3.6.1.2.1.33.3.2.1.1,UPS-MIB::upsSubsetIdentGroup,,,,,,The upsSubsetIdentGroup defines objects which are common across all UPSs which meet subset compliance. Most devices which conform to the upsSubsetIdentGroup will provide access to these objects via a proxy agent. If the proxy agent is compatible with multiple UPS types, configuration of the proxy agent will require specifying some of these values, either individually, or as a group (perhaps through a table lookup mechanism based on the UPS model number).
.1.3.6.1.2.1.33.3.2.1.2,UPS-MIB::upsSubsetBatteryGroup,,,,,,The upsSubsetBatteryGroup defines the objects that are common to battery groups of two-contact UPSs.
.1.3.6.1.2.1.33.3.2.1.3,UPS-MIB::upsSubsetInputGroup,,,,,,The upsSubsetInputGroup defines the objects that are common to the Input groups of two-contact UPSs.
.1.3.6.1.2.1.33.3.2.1.4,UPS-MIB::upsSubsetOutputGroup,,,,,,The upsSubsetOutputGroup defines the objects that are common to the Output groups of two-contact UPSs.
.1.3.6.1.2.1.33.3.2.1.6,UPS-MIB::upsSubsetAlarmGroup,,,,,,The upsSubsetAlarmGroup defines the objects that are common to the Alarm groups of two-contact UPSs.
.1.3.6.1.2.1.33.3.2.1.8,UPS-MIB::upsSubsetControlGroup,,,,,,The upsSubsetControlGroup defines the objects that are common to the Control groups of two-contact UPSs.
.1.3.6.1.2.1.33.3.2.1.9,UPS-MIB::upsSubsetConfigGroup,,,,,,The upsSubsetConfigGroup defines the objects that are common to the Config groups of two-contact UPSs.
.1.3.6.1.2.1.33.3.2.2,UPS-MIB::upsBasicGroups,,,,,,
.1.3.6.1.2.1.33.3.2.2.1,UPS-MIB::upsBasicIdentGroup,,,,,,The upsBasicIdentGroup defines objects which are common to the Ident group of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.2,UPS-MIB::upsBasicBatteryGroup,,,,,,The upsBasicBatteryGroup defines the objects that are common to the battery groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.3,UPS-MIB::upsBasicInputGroup,,,,,,The upsBasicInputGroup defines the objects that are common to the Input groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.4,UPS-MIB::upsBasicOutputGroup,,,,,,The upsBasicOutputGroup defines the objects that are common to the Output groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.5,UPS-MIB::upsBasicBypassGroup,,,,,,The upsBasicBypassGroup defines the objects that are common to the Bypass groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.6,UPS-MIB::upsBasicAlarmGroup,,,,,,The upsBasicAlarmGroup defines the objects that are common to the Alarm groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.7,UPS-MIB::upsBasicTestGroup,,,,,,The upsBasicTestGroup defines the objects that are common to the Test groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.8,UPS-MIB::upsBasicControlGroup,,,,,,The upsBasicControlGroup defines the objects that are common to the Control groups of compliant UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.2.9,UPS-MIB::upsBasicConfigGroup,,,,,,The upsBasicConfigGroup defines the objects that are common to the Config groups of UPSs which support basic functions.
.1.3.6.1.2.1.33.3.2.3,UPS-MIB::upsFullGroups,,,,,,
.1.3.6.1.2.1.33.3.2.3.1,UPS-MIB::upsFullIdentGroup,,,,,,The upsFullIdentGroup defines objects which are common to the Ident group of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.2,UPS-MIB::upsFullBatteryGroup,,,,,,The upsFullBatteryGroup defines the objects that are common to the battery groups of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.3,UPS-MIB::upsFullInputGroup,,,,,,The upsFullInputGroup defines the objects that are common to the Input groups of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.4,UPS-MIB::upsFullOutputGroup,,,,,,The upsFullOutputGroup defines the objects that are common to the Output groups of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.5,UPS-MIB::upsFullBypassGroup,,,,,,The upsFullBypassGroup defines the objects that are common to the Bypass groups of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.6,UPS-MIB::upsFullAlarmGroup,,,,,,The upsFullAlarmGroup defines the objects that are common to the Alarm groups of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.7,UPS-MIB::upsFullTestGroup,,,,,,The upsFullTestGroup defines the objects that are common to the Test groups of fully compliant UPSs.
.1.3.6.1.2.1.33.3.2.3.8,UPS-MIB::common,,,,,,The upsFullControlGroup defines the objects that are
.1.3.6.1.2.1.33.3.2.3.9,UPS-MIB::upsFullConfigGroup,,,,,,The upsFullConfigGroup defines the objects that are common to the Config groups of fully compliant UPSs.
.1.3.6.1.2.1.34,SNA-NAU-MIB::snanauMIB,,,,,,This is the MIB module for objects used to manage SNA devices.
.1.3.6.1.2.1.34.1,SNA-NAU-MIB::snanauObjects,,,,,,
.1.3.6.1.2.1.34.1.1,SNA-NAU-MIB::snaNode,,,,,,
.1.3.6.1.2.1.34.1.1.1,SNA-NAU-MIB::snaNodeAdminTable,,not-accessible,,current,,This table contains objects which describe the configuration parameters for an SNA Node. Link specific configuration objects are contained in a separate MIB module (e.g., SNA DLC MIB) corresponding to the link type. The table snaNodeAdminLinkTable contains objects which identify the relationship between node instances and link instances. The entries (i.e., rows) in this table can be created by either an Agent or a Management Station. The Management Station can do this through setting the appropriate value in the snaNodeAdminRowStatus. The snaNodeAdminRowStatus object describes the status of an entry and is used to change the status of an entry. The entry is deleted by an Agent based on the value of the snaNodeAdminRowStatus. The snaNodeAdminState object describes the desired operational state of a Node and is used to change the operational state of a Node. For example, such information may be obtained from a configuration file. How an Agent or a Management Station obtains the initial value of each object at creation time is an implementation specific issue. For each entry in this table, there is a corresponding entry in the snaNodeOperTable. While the objects in this table describe the desired or configured operational values of the SNA Node, the actual runtime values are contained in snaNodeOperTable.
.1.3.6.1.2.1.34.1.1.1.1,SNA-NAU-MIB::snaNodeAdminEntry,,not-accessible,snaNodeAdminIndex,current,,An entry contains the configuration parameters for one SNA Node instance. The objects in the entry have read-create access. An entry can be created, modified or deleted. The object snaNodeAdminRowStatus is used (i.e., set) to create or delete a row entry.
.1.3.6.1.2.1.34.1.1.1.1.1,SNA-NAU-MIB::snaNodeAdminIndex,Integer32,not-accessible,,current,,Index used to uniquely identify each Node instance. If an Agent creates the entry, then it will assign this number otherwise a Management Station generates a random number when it reserves the entry for creation.
.1.3.6.1.2.1.34.1.1.1.1.2,SNA-NAU-MIB::snaNodeAdminName,OCTET,read-create,,current,,The value indicates the desired name of the Node for use during Node activation. In Type 2.1 networks, this is a fully-qualified name, meaning that the Node name is preceded by the NetId (if present) with a period as the delimiter. A write operation to this object will not change the operational value reflected in snaNodeOperName until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.1.1.1.3,SNA-NAU-MIB::snaNodeAdminType,INTEGER,read-create,,current,other(1):pu10(2):pu20(3):t21len(4):endNode(5):networkNode(6),The value indicates the type of SNA Node. A write operation to this object will not change the operational value reflected in snaNodeOperType until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.1.1.1.4,SNA-NAU-MIB::snaNodeAdminXidFormat,INTEGER,read-create,,current,format0(1):format1(2):format3(3),The value indicates the type of XID format used for this Node. Note that there is no format type 2. A write operation to this object will not change the operational value reflected in snaNodeOperAdminXidFormat until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.1.1.1.5,SNA-NAU-MIB::snaNodeAdminBlockNum,OCTET,read-create,,current,,The value indicates the block number for this Node instance. It is the first 3 hexadecimal digits of the SNA Node id. A write operation to this object will not change the operational value reflected in snaNodeOperBlockNum until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.1.1.1.6,SNA-NAU-MIB::snaNodeAdminIdNum,OCTET,read-create,,current,,The value indicates the ID number for this Node instance. This is the last 5 hexadecimal digits of the SNA Node id. A write operation to this object will not change the operational value reflected in snaNodeOperIdNum until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.1.1.1.7,SNA-NAU-MIB::snaNodeAdminEnablingMethod,INTEGER,read-create,,current,other(1):startup(2):demand(3):onlyMS(4),The value indicates how the Node should be activated for the first time. The values have the following meanings: other (1) - may be used for proprietary methods not listed in this enumeration, startup (2) - at SNA services' initialization time (this is the default), demand (3) - only when LU is requested by application, or onlyMS (4) - by a Management Station only. A write operation to this object may immediately change the operational value reflected in snaNodeOperEnablingMethod depending on the Agent implementation. If the Agent implementation accepts immediate changes, then the behavior of the Node changes immediately and not only after the next system startup of the SNA services. An immediate change may only apply when the current value 'demand (3)' is changed to 'onlyMS (4)' and vice versa.
.1.3.6.1.2.1.34.1.1.1.1.8,SNA-NAU-MIB::snaNodeAdminLuTermDefault,INTEGER,read-create,,current,unbind(1):termself(2):rshutd(3):poweroff(4),The value indicates the desired default method used to deactivate LUs for this Node For LU6.2s, 'unbind(1)' is the only valid value. unbind(1) - terminate the LU-LU session by sending an SNA UNBIND request. termself(2) - terminate the LU-LU session by sending an SNA TERM-SELF (Terminate Self) request on the SSCP-LU session. The SSCP will inform the remote session LU partner to send an UNBIND request to terminate the session. rshutd(3) - terminate the LU-LU session by sending an SNA RSHUTD (Request ShutDown) request to the remote session LU partner. The remote LU will then send an UNBIND request to terminate the session. poweroff(4) - terminate the LU-LU session by sending either an SNA LUSTAT (LU Status) request on the LU-LU session or an SNA NOTIFY request on the SSCP-LU session indicating that the LU has been powered off. Sending both is also acceptable. The result should be that the remote session LU partner will send an UNBIND to terminate the session. The default behavior indicated by the value of this object may be overridden for an LU instance. The override is performed by setting the snaLuAdminTerm object instance in the snaLuAdminTable to the desired value. A write operation to this object may immediately change the operational value reflected in snaNodeOperLuTermDefault depending on the Agent implementation.
.1.3.6.1.2.1.34.1.1.1.1.9,SNA-NAU-MIB::snaNodeAdminMaxLu,Integer32,read-create,,current,,The maximum number of LUs that may be activated for this Node. For PU2.1, this object refers to the number of dependent LUs. A write operation to this object will not change the operational value reflected in snaNodeOperMaxLu until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.1.1.1.10,SNA-NAU-MIB::snaNodeAdminHostDescription,OCTET,read-create,,current,,The value identifies the remote host associated with this Node. Since SSCP Id's may not be unique across hosts, the host description is required to uniquely identify the SSCP. This object is only applicable to PU2.0 type Nodes. If the remote host is unknown, then the value is the null string. A write operation to this object may immediately change the operational value reflected in snaNodeOperHostDescription depending on the Agent implementation.
.1.3.6.1.2.1.34.1.1.1.1.11,SNA-NAU-MIB::snaNodeAdminStopMethod,INTEGER,read-create,,current,other(1):normal(2):immed(3):force(4),The value indicates the desired method to be used by the Agent to stop a Node (i.e., change the Node's operational state to inactive(1) ). The values have the following meaning: other (1) - used for proprietary methods not listed in this enumeration. normal(2) - deactivate only when there is no more activity on this Node (i.e., all data flows have been completed and all sessions have been terminated). immed(3) - deactivate immediately regardless of current activities on this Node. Wait for deactivation responses (from remote Node) before changing the Node state to inactive. force(4) - deactivate immediately regardless of current activities on this Node. Do not wait for deactivation responses (from remote Node) before changing the Node state to inactive. A write operation to this object may immediately change the operational value reflected in snaNodeOperStopMethod depending on the Agent implementation.
.1.3.6.1.2.1.34.1.1.1.1.12,SNA-NAU-MIB::snaNodeAdminState,INTEGER,read-create,,current,inactive(1):active(2),The value indicates the desired operational state of the SNA Node. This object is used by the Management Station to activate or deactivate the Node. If the current value in snaNodeOperState is 'active (2)', then setting this object to 'inactive (1)' will initiate the Node shutdown process using the method indicated by snaNodeOperStopMethod. If the current value in snaNodeOperState is 'inactive (1)', then setting this object to 'active (2)' will initiate the Node's activation. A Management Station can always set this object to 'active (2)' irrespective of the value in the snaOperEnablingMethod.
.1.3.6.1.2.1.34.1.1.1.1.13,SNA-NAU-MIB::snaNodeAdminRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by a Management Station to create or delete the row entry in the snaNodeAdminTable following the RowStatus textual convention. Upon successful creation of the row, an Agent automatically creates a corresponding entry in the snaNodeOperTable with snaNodeOperState equal to 'inactive (1)'. Row deletion can be Management Station or Agent initiated: (a) The Management Station can set the value to 'destroy (6)' only when the value of snaNodeOperState of this Node instance is 'inactive (1)'. The Agent will then delete the rows corresponding to this Node instance from the snaNodeAdminTable and the snaNodeOperTable. (b) The Agent detects that a row is in the 'notReady (3)' state for greater than a default period of 5 minutes. (c) All rows with the snaNodeAdminRowStatus object's value of 'notReady (3)' will be removed upon the next initialization of the SNA services.
.1.3.6.1.2.1.34.1.1.2,SNA-NAU-MIB::snaNodeAdminTableLastChange,TimeTicks,read-only,,current,,The value indicates the timestamp (e.g., the Agent's sysUpTime value) of the last change made to any object in the snaNodeAdminTable, including row deletions/additions (e.g., changes to snaNodeAdminRowStatus values). This object can be used to reduce frequent retrievals of the snaNodeAdminTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node configuration information has been changed. Only then will the Management Station retrieve the entire table.
.1.3.6.1.2.1.34.1.1.3,SNA-NAU-MIB::snaNodeOperTable,,not-accessible,,current,,This table contains the dynamic parameters which have read-only access. These objects reflect the actual status of the Node. The entries in this table cannot be created or modified by a Management Station. This table augments the snaNodeAdminTable.
.1.3.6.1.2.1.34.1.1.3.1,SNA-NAU-MIB::snaNodeOperEntry,,not-accessible,,current,,The entry contains parameters which describe the state of one Node. The entries are created by the Agent. They have read-only access.
.1.3.6.1.2.1.34.1.1.3.1.1,SNA-NAU-MIB::snaNodeOperName,OCTET,read-only,,current,,The value identifies the current name of the Node. In Type 2.1 networks, this is a fully-qualified name, meaning that the Node name is preceded by the NetId (if present) with a period as the delimiter.
.1.3.6.1.2.1.34.1.1.3.1.2,SNA-NAU-MIB::snaNodeOperType,INTEGER,read-only,,current,other(1):pu10(2):pu20(3):t21LEN(4):endNode(5):networkNode(6),The value identifies the current type of the Node.
.1.3.6.1.2.1.34.1.1.3.1.3,SNA-NAU-MIB::snaNodeOperXidFormat,INTEGER,read-only,,current,format0(1):format1(2):format3(3),The value identifies the type of XID format currently used for this Node. Note that there is no format type 2.
.1.3.6.1.2.1.34.1.1.3.1.4,SNA-NAU-MIB::snaNodeOperBlockNum,OCTET,read-only,,current,,The value identifies the block number for this Node instance. It is the first 3 hexadecimal digits of the SNA Node id.
.1.3.6.1.2.1.34.1.1.3.1.5,SNA-NAU-MIB::snaNodeOperIdNum,OCTET,read-only,,current,,The value identifies the ID number for this Node instance. This is the last 5 hexadecimal digits of the SNA Node id.
.1.3.6.1.2.1.34.1.1.3.1.6,SNA-NAU-MIB::snaNodeOperEnablingMethod,INTEGER,read-only,,current,other(1):startup(2):demand(3):onlyMS(4),The value indicates how the Node is activated for the first time. The values have the following meanings: other (1) - not at boot time, LU activation or by a Management Station; startup (2) - at SNA services' initialization time (this is the default), demand (3) - only when LU is requested by application, onlyMS (4) - by a network Management Station only.
.1.3.6.1.2.1.34.1.1.3.1.7,SNA-NAU-MIB::snaNodeOperLuTermDefault,INTEGER,read-only,,current,unbind(1):termself(2):rshutd(3):poweroff(4),The value identifies the default method used to deactivate LUs for this Node. For LU6.2s, 'unbind(1)' is the only valid value. unbind(1) - terminate the LU-LU session by sending an SNA UNBIND request. termself(2) - terminate the LU-LU session by sending an SNA TERM-SELF (Terminate Self) request on the SSCP-LU session. The SSCP will inform the remote session LU partner to send an UNBIND request to terminate the session. rshutd(3) - terminate the LU-LU session by sending an SNA RSHUTD (Request ShutDown) request to the remote session LU partner. The remote LU will then send an UNBIND request to terminate the session. poweroff(4) - terminate the LU-LU session by sending either an SNA LUSTAT (LU Status) request on the LU-LU session or an SNA NOTIFY request on the SSCP-LU session indicating that the LU has been powered off. Sending both is also acceptable. The result should be that the remote session LU partner will send an UNBIND to terminate the session. This object describes the default behavior for this Node; however, it is possible that for a specific LU the behavior indicated by the snaLuOperTerm object is different.
.1.3.6.1.2.1.34.1.1.3.1.8,SNA-NAU-MIB::snaNodeOperMaxLu,Integer32,read-only,,current,,This value identifies the current, maximum number of LUs that are activated for this Node. For PU2.1, this object refers to the number of dependent LUs.
.1.3.6.1.2.1.34.1.1.3.1.9,SNA-NAU-MIB::snaNodeOperHostDescription,OCTET,read-only,,current,,This value identifies the remote host currently associated with this Node. Since SSCP Id's may not be unique across hosts, the host description is required to uniquely identify the SSCP.
.1.3.6.1.2.1.34.1.1.3.1.10,SNA-NAU-MIB::snaNodeOperStopMethod,INTEGER,read-only,,current,other(1):normal(2):immed(3):force(4),This value identifies the current Node shutdown method to be used by the Agent to stop the Node. When the Agent changes the Node's state to 'inactive (1)', the Agent must use the shutdown method indicated by this object. The values have the following meaning: other (1) - proprietary method not listed in this enumeration normal(2) - deactivate only when there is no more activity on this Node (i.e., all data flows have been completed and all sessions have been terminated). immed(3) - deactivate immediately regardless of current activities on this Node. Wait for deactivation responses (from remote Node) before changing the Node state to inactive. force(4) - deactivate immediately regardless of current activities on this Node. Do not wait for deactivation responses (from remote Node) before changing the Node state to inactive. Note that a write operation to snaNodeAdminOperStopMethod may immediately change the value of snaNodeOperStopMethod depending on the Agent implementation.
.1.3.6.1.2.1.34.1.1.3.1.11,SNA-NAU-MIB::snaNodeOperState,INTEGER,read-only,,current,inactive(1):active(2):waiting(3):stopping(4),The current state of the Node. The values have the following meanings: inactive (1), a row representing the Node has been created in the AdminTable and, the Node is ready for activation -or- an active Node has been stopped -or- a waiting Node has returned to the inactive state. waiting (3), a request to have the Node activated has been issued, and the Node is pending activation. active (2), the Node is ready and operating. stopping (4), the request to stop the Node has been issued while the StopMethod normal or immediate is used.
.1.3.6.1.2.1.34.1.1.3.1.12,SNA-NAU-MIB::snaNodeOperHostSscpId,OCTET,read-only,,current,,This value identifies the current SSCP Id associated with the Node. This object is only applicable to PU 2.0s. If the Node is not a PU 2.0 type, then this object contains a zero length string.
.1.3.6.1.2.1.34.1.1.3.1.13,SNA-NAU-MIB::snaNodeOperStartTime,TimeTicks,read-only,,current,,The timestamp (e.g, the Agent's sysUpTime value) at the Node activation.
.1.3.6.1.2.1.34.1.1.3.1.14,SNA-NAU-MIB::snaNodeOperLastStateChange,TimeTicks,read-only,,current,,The timestamp (e.g., the Agent's sysUpTime value) at the last state change of the Node.
.1.3.6.1.2.1.34.1.1.3.1.15,SNA-NAU-MIB::snaNodeOperActFailures,Counter32,read-only,,current,,This value identifies the number of failed Node activation attempts.
.1.3.6.1.2.1.34.1.1.3.1.16,SNA-NAU-MIB::snaNodeOperActFailureReason,INTEGER,read-only,,current,other(1):linkFailure(2):noResources(3):badConfiguration(4):internalError(5),The value indicates the reason for the activation failure. The value 'other (1)' indicates a reason not listed in the enumeration. This object will be sent in the trap snaNodeActFailTrap.
.1.3.6.1.2.1.34.1.1.4,SNA-NAU-MIB::snaNodeOperTableLastChange,TimeTicks,read-only,,current,,The timestamp (e.g., the Agent's sysUpTime value) at the last change made to any object in the snaNodeOperTable, including row deletions/additions made as a result of changes to the snaNodeAdminRowStatus object. This object can be used to reduce frequent retrievals of the snaNodeOperTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node operational information has been changed. Only then will the Management Station retrieve the entire table.
.1.3.6.1.2.1.34.1.1.5,SNA-NAU-MIB::snaPu20StatsTable,,not-accessible,,current,,This table contains the dynamic parameters which have read-only access. The entries in this table correspond to PU 2.0 entries in the snaNodeOperTable and cannot be created by a Management Station.
.1.3.6.1.2.1.34.1.1.5.1,SNA-NAU-MIB::snaPu20StatsEntry,,not-accessible,snaNodeAdminIndex,current,,The entry contains parameters which describe the statistics for one PU 2.0. They have read-only access. The counters represent traffic for all kinds of sessions: LU-LU, SSCP-PU, SSCP-LU. Each Node of PU Type 2.0 from the snaNodeAdminTable has one entry in this table and the index used here has the same value as snaNodeAdminIndex of that PU. The entry is created by the Agent.
.1.3.6.1.2.1.34.1.1.5.1.1,SNA-NAU-MIB::snaPu20StatsSentBytes,Counter32,read-only,,current,,The number of bytes sent by this Node.
.1.3.6.1.2.1.34.1.1.5.1.2,SNA-NAU-MIB::snaPu20StatsReceivedBytes,Counter32,read-only,,current,,The number of bytes received by this Node.
.1.3.6.1.2.1.34.1.1.5.1.3,SNA-NAU-MIB::snaPu20StatsSentPius,Counter32,read-only,,current,,The number of PIUs sent by this Node.
.1.3.6.1.2.1.34.1.1.5.1.4,SNA-NAU-MIB::snaPu20StatsReceivedPius,Counter32,read-only,,current,,The number of PIUs received by this Node.
.1.3.6.1.2.1.34.1.1.5.1.5,SNA-NAU-MIB::snaPu20StatsSentNegativeResps,Counter32,read-only,,current,,The number of negative responses sent by this Node.
.1.3.6.1.2.1.34.1.1.5.1.6,SNA-NAU-MIB::snaPu20StatsReceivedNegativeResps,Counter32,read-only,,current,,The number of negative responses received by this Node.
.1.3.6.1.2.1.34.1.1.5.1.7,SNA-NAU-MIB::snaPu20StatsActLus,Gauge32,read-only,,current,,The number of LUs on this PU which have received and responded to ACTLU from the host.
.1.3.6.1.2.1.34.1.1.5.1.8,SNA-NAU-MIB::snaPu20StatsInActLus,Gauge32,read-only,,current,,The number of LUs on this PU which have not received an ACTLU from the host. This is possible if the number of configured LUs exceeds that on the host.
.1.3.6.1.2.1.34.1.1.5.1.9,SNA-NAU-MIB::snaPu20StatsBindLus,Gauge32,read-only,,current,,The number of LUs on this PU which have received and acknowledged a BIND request from the host.
.1.3.6.1.2.1.34.1.1.6,SNA-NAU-MIB::snaNodeLinkAdminTable,,not-accessible,,current,,This table contains the references to link specific tables. If a Node is configured for multiple links, then the Node will have multiple entries in this table. The entries in this table can be generated initially, after initialization of SNA service, by the Agent which uses information from Node configuration file. Subsequent modifications of parameters, creation of new Nodes link entries and deletion of entries is possible. The modification to this table can be saved in the Node configuration file for the next initialization of SNA service, but the mechanism for this function is not defined here.
.1.3.6.1.2.1.34.1.1.6.1,SNA-NAU-MIB::snaNodeLinkAdminEntry,,not-accessible,snaNodeAdminIndex:snaNodeLinkAdminIndex,current,,Entry contains the configuration information that associates a Node instance to one link instance. The objects in the entry have read-create access. Entry can be created, modified or deleted. The object snaNodeLinkAdminRowStatus is used (set) to create or delete an entry. The object snaNodeLinkAdminSpecific can be set later, after the entry has been created.
.1.3.6.1.2.1.34.1.1.6.1.1,SNA-NAU-MIB::snaNodeLinkAdminIndex,Integer32,not-accessible,,current,,This value is used to index the instances of objects. If an Agent creates the entry, then it will assign this number otherwise a Management Station generates a random number when it reserves the entry for creation.
.1.3.6.1.2.1.34.1.1.6.1.2,SNA-NAU-MIB::snaNodeLinkAdminSpecific,OBJECT,read-create,,current,,This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module).
.1.3.6.1.2.1.34.1.1.6.1.3,SNA-NAU-MIB::snaNodeLinkAdminMaxPiu,Integer32,read-create,,current,,This value identifies the maximum number of octets that can be exchanged by this Node in one Path Information Unit (PIU).
.1.3.6.1.2.1.34.1.1.6.1.4,SNA-NAU-MIB::snaNodeLinkAdminRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by a Management Station to create or delete the row entry in the snaNodeLinkAdminTable. To activate a row, a Management Station sets the value to 'active (1)' or 'notReady (3)'. Upon successful creation of the row, the Agent automatically creates a corresponding entry in the snaNodeLinkOperTable. Row deletion can be Management Station or Agent initiated: (a) The Management Station can set the value to 'destroy (6)' only when the value of snaNodeLinkOperState of this Link instance is 'inactive (1)'. The Agent will then delete the row corresponding to this Link instance from snaNodeLinkOperTable and from snaNodeLinkAdminTable. (b) The Agent detects that a row is in the 'notReady (3)' state for greater than a default period of 5 minutes. (c) The Agent will not include a row with RowStatus= 'notReady (3)', after SNA system re-initialization (e.g., reboot).
.1.3.6.1.2.1.34.1.1.7,SNA-NAU-MIB::snaNodeLinkAdminTableLastChange,TimeTicks,read-only,,current,,The timestamp (e.g., the Agent's sysUpTime value) at the last change made to any object in the snaNodeLinkAdminTable, including row deletions/additions (i.e., changes to the snaNodeLinkAdminRowStatus object). This object can be used to reduce frequent retrievals of the snaNodeLinkAdminTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node operational information has been changed. Only then will the Management Station retrieve the entire table.
.1.3.6.1.2.1.34.1.1.8,SNA-NAU-MIB::snaNodeLinkOperTable,,not-accessible,,current,,This table contains all references to link specific tables for operational parameters. If a Node is configured for multiple links, then the Node will have multiple entries in this table. This table augments the snaNodeLinkAdminTable.
.1.3.6.1.2.1.34.1.1.8.1,SNA-NAU-MIB::snaNodeLinkOperEntry,,not-accessible,,current,,Entry contains all current parameters for one Node link. The objects in the entry have read-only access.
.1.3.6.1.2.1.34.1.1.8.1.1,SNA-NAU-MIB::snaNodeLinkOperSpecific,OBJECT,read-only,,current,,This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSOperTable of the SNA DLC MIB module).
.1.3.6.1.2.1.34.1.1.8.1.2,SNA-NAU-MIB::snaNodeLinkOperMaxPiu,Integer32,read-only,,current,,Maximum number of octets that can be exchanged by this Node in one Path Information Unit (PIU).
.1.3.6.1.2.1.34.1.1.9,SNA-NAU-MIB::snaNodeLinkOperTableLastChange,TimeTicks,read-only,,current,,The timestamp of the last change made to any object in the snaNodeLinkOperTable, including row deletions/additions. This object can be used to reduce frequent retrievals of the snaNodeLinkOperTable by a Management Station. It is expected that a Management Station will periodically poll this object and compare its current value with the previous one. A difference indicates that some Node operational information has been changed. Only then will the Management Station retrieve the entire table.
.1.3.6.1.2.1.34.1.1.10,SNA-NAU-MIB::snaNodeTraps,,,,,,
.1.3.6.1.2.1.34.1.1.10.1,SNA-NAU-MIB::snaNodeStateChangeTrap,,,,,,This trap indicates that the operational state (i.e., value of the snaNodeOperState object) of a Node has changed. The following variables are returned: snaNodeOperName - current name of the Node, with the instance identifying the Node; and, snaNodeOperState - current state after the change.
.1.3.6.1.2.1.34.1.1.10.2,SNA-NAU-MIB::snaNodeActFailTrap,,,,,,This trap indicates a Node activation failure. The value of snaNodeOperState indicates the current state after the activation attempt. The value of snaNodeOperActFailureReason indicates the failure reason.
.1.3.6.1.2.1.34.1.2,SNA-NAU-MIB::snaLu,,,,,,
.1.3.6.1.2.1.34.1.2.1,SNA-NAU-MIB::snaLuAdminTable,,not-accessible,,current,,This table contains LU configuration information. The rows in this table can be created and deleted by a Management Station. Only objects which are common to all types of LUs are included in this table.
.1.3.6.1.2.1.34.1.2.1.1,SNA-NAU-MIB::snaLuAdminEntry,,not-accessible,snaNodeAdminIndex:snaLuAdminLuIndex,current,,Contains configuration variables for an LU.
.1.3.6.1.2.1.34.1.2.1.1.1,SNA-NAU-MIB::snaLuAdminLuIndex,Integer32,not-accessible,,current,,This value identifies the unique index for an LU instance within a Node.
.1.3.6.1.2.1.34.1.2.1.1.2,SNA-NAU-MIB::snaLuAdminName,OCTET,read-create,,current,,This value identifies the user configurable name for this LU. If a name is not assigned to the LU, then this object contains a zero length string. A write operation to this object will not change the operational value reflected in snaLuOperName until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.1.1.3,SNA-NAU-MIB::snaLuAdminSnaName,OCTET,read-create,,current,,This value identifies the SNA LU name used in exchange of SNA data. A write operation to this object will not change the operational value reflected in snaLuOperSnaName until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.1.1.4,SNA-NAU-MIB::snaLuAdminType,INTEGER,read-create,,current,other(1):lu0(2):lu1(3):lu2(4):lu3(5):lu4(6):lu62(7):lu7(8),This value identifies the LU type. A write operation to this object will not change the operational value reflected in snaLuOperAdminType until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.1.1.5,SNA-NAU-MIB::snaLuAdminDepType,INTEGER,read-create,,current,dependent(1):independent(2),This value identifies whether the LU is dependent or independent. A write operation to this object will not change the operational value reflected in snaLuOperDepType until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.1.1.6,SNA-NAU-MIB::snaLuAdminLocalAddress,OCTET,read-create,,current,,The local address for this LU is a byte with a value ranging from 0 to 254.For dependent LUs, this value ranges from 1 to 254 and for independent LUs this value is always 0. A write operation to this object will not change the operational value reflected in snaLuOperLocalAddress until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.1.1.7,SNA-NAU-MIB::snaLuAdminDisplayModel,INTEGER,read-create,,current,invalid(1):model2A(2):model2B(3):model3A(4):model3B(5):model4A(6):model4B(7):model5A(8):model5B(9):dynamic(10),The value of this object identifies the model type and screen size of the terminal connected to the host. This is only valid for LU Type 2. The values have the following meaning: model2A(2) - Model 2 (24 rows x 80 cols) with base attributes model2B(3) - Model 2 (24 rows x 80 cols) with extended attributes model3A(4) - Model 3 (32 rows x 80 cols) with base attributes model3B(5) - Model 3 (32 rows x 80 cols) with extended attributes model4A(6) - Model 4 (43 rows x 80 cols) with base attributes model4B(7) - Model 4 (43 rows x 80 cols) with extended attributes model5A(8) - Model 5 (27 rows x 132 cols) with base attributes model5B(9) - Model 5 (27 rows x 132 cols) with extended attributes dynamic(10) - Screen size determine with BIND and Read Partition Query. In case this LU is not Type 2, then this object should contain the invalid(1) value.
.1.3.6.1.2.1.34.1.2.1.1.8,SNA-NAU-MIB::snaLuAdminTerm,INTEGER,read-create,,current,unbind(1):termself(2):rshutd(3):poweroff(4),This value identifies the desired method for deactivation of this LU. This value overrides the default method (snaNodeOperLuTermDefault) for this Node. For LU 6.2, only the value 'unbind (1)' applies. unbind(1) - terminate the LU-LU session by sending an SNA UNBIND request. termself(2) - terminate the LU-LU session by sending an SNA TERM-SELF (Terminate Self) request on the SSCP-LU session. The SSCP will inform the remote session LU partner to send an UNBIND request to terminate the session. rshutd(3) - terminate the LU-LU session by sending an SNA RSHUTD (Request ShutDown) request to the remote session LU partner. The remote LU will then send an UNBIND request to terminate the session. poweroff(4) - terminate the LU-LU session by sending either an SNA LUSTAT (LU Status) request on the LU-LU session or an SNA NOTIFY request on the SSCP-LU session indicating that the LU has been powered off. Sending both is also acceptable. The result should be that the remote session LU partner will send an UNBIND to terminate the session. A write operation to this object may immediately change the operational value reflected in snaLuOperTerm depending on the Agent implementation.
.1.3.6.1.2.1.34.1.2.1.1.9,SNA-NAU-MIB::snaLuAdminRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by a Management Station to create or delete the row entry in the snaLuAdminTable. To activate a row, the Management Station sets the value to 'active (1)' or 'notReady (3)'. Upon successful creation of the row, the Agent automatically creates a corresponding entry in the snaLuOperTable with snaLuOperState equal to 'inactive (1)'. Row deletion can be Management Station or Agent initiated: (a) The Management Station can set the value to 'destroy (6)' only when the value of snaLuOperState of this LU instance is 'inactive (1)'. The Agent will then delete the row corresponding to this LU instance from snaLuAdminTable and from snaLuOperTable. (b) The Agent detects that a row is in the 'notReady (3)' state for greater than a default period of 5 minutes. (c) The Agent will not create a row with RowStatus equal to 'notReady (3)', after SNA system re-initialization (e.g., reboot).
.1.3.6.1.2.1.34.1.2.2,SNA-NAU-MIB::snaLuOperTable,,not-accessible,,current,,This table contains dynamic runtime information and control variables relating to LUs. Only objects which are common to all types of LUs are included in this table. This table augments the snaLuAdminTable.
.1.3.6.1.2.1.34.1.2.2.1,SNA-NAU-MIB::snaLuOperEntry,,not-accessible,,current,,Contains objects reflecting current information for an LU. Each entry is created by the Agent. All entries have read-only access.
.1.3.6.1.2.1.34.1.2.2.1.1,SNA-NAU-MIB::snaLuOperName,OCTET,read-only,,current,,User configurable name for this LU. If a name is not assigned, then this object contains a zero length string.
.1.3.6.1.2.1.34.1.2.2.1.2,SNA-NAU-MIB::snaLuOperSnaName,OCTET,read-only,,current,,The value identifies the current SNA LU name.
.1.3.6.1.2.1.34.1.2.2.1.3,SNA-NAU-MIB::snaLuOperType,INTEGER,read-only,,current,other(1):lu0(2):lu1(3):lu2(4):lu3(5):lu4(6):lu62(7):lu7(8),The value identifies the current LU type.
.1.3.6.1.2.1.34.1.2.2.1.4,SNA-NAU-MIB::snaLuOperDepType,INTEGER,read-only,,current,dependent(1):independent(2),The value identifies whether the LU is currently dependent or independent. A write operation to this object will not change the operational value reflected in snaLuOperDepType until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.2.1.5,SNA-NAU-MIB::snaLuOperLocalAddress,OCTET,read-only,,current,,The local address for this LU is a byte with a value ranging from 0 to 254. For dependent LUs, this value ranges from 1 to 254; for independent LUs this value is always 0. A write operation to this object will not change the operational value reflected in snaLuOperLocalAddress until the Node has been re-activated (e.g., after the next initialization of the SNA services).
.1.3.6.1.2.1.34.1.2.2.1.6,SNA-NAU-MIB::snaLuOperDisplayModel,INTEGER,read-only,,current,invalid(1):model2A(2):model2B(3):model3A(4):model3B(5):model4A(6):model4B(7):model5A(8):model5B(9):dynamic(10),The screen model type of the terminal connected to the host. If this LU is not Type 2, then this object should contain the 'invalid(1)' value.
.1.3.6.1.2.1.34.1.2.2.1.7,SNA-NAU-MIB::snaLuOperTerm,INTEGER,read-only,,current,unbind(1):termself(2):rshutd(3):poweroff(4),The value identifies the current method for deactivation of this LU. This value overrides the default method (snaNodeOperLuTermDefault) for this Node. For LU 6.2, only the value 'unbind (1)' applies. unbind(1) - terminate the LU-LU session by sending an SNA UNBIND request. termself(2) - terminate the LU-LU session by sending an SNA TERM-SELF (Terminate Self) request on the SSCP-LU session. The SSCP will inform the remote session LU partner to send an UNBIND request to terminate the session. rshutd(3) - terminate the LU-LU session by sending an SNA RSHUTD (Request ShutDown) request to the remote session LU partner. The remote LU will then send an UNBIND request to terminate the session. poweroff(4) - terminate the LU-LU session by sending either an SNA LUSTAT (LU Status) request on the LU-LU session or an SNA NOTIFY request on the SSCP-LU session indicating that the LU has been powered off. Sending both is also acceptable. The result should be that the remote session LU partner will send an UNBIND to terminate the session.
.1.3.6.1.2.1.34.1.2.2.1.8,SNA-NAU-MIB::snaLuOperState,INTEGER,read-only,,current,inactive(1):active(2),The value identifies the current operational state of this LU. It has different meanings for dependent and independent LUs. For dependent LUs the values indicate the following: inactive (1) - LU didn't receive ACTLU, or it received DACTLU, or received ACTLU and sent negative response. active (2) - LU received ACTLU and acknowledged positively. For independent LUs the values indicate the following: active (2) - the LU is defined and is able to send and receive BIND. inactive (1) - the LU has a session count equal to 0.
.1.3.6.1.2.1.34.1.2.2.1.9,SNA-NAU-MIB::snaLuOperSessnCount,Gauge32,read-only,,current,,The number of currently active LU-LU sessions of this LU. For the independent LU, if this object has value 0, it indicates that LU is inactive.
.1.3.6.1.2.1.34.1.2.3,SNA-NAU-MIB::snaLuSessnTable,,not-accessible,,current,,This is a table containing objects which describe the operational state of LU sessions. Only objects which are common to all types of LU sessions are included in this table. When a session's snaLuSessnOperState value changes to 'pendingBind (2)', then the corresponding entry in the session table is created by the Agent. When the session's snaLuSessnOperState value changes to 'unbound (1)', then the session will be removed from the session table by the Agent.
.1.3.6.1.2.1.34.1.2.3.1,SNA-NAU-MIB::snaLuSessnEntry,,not-accessible,snaNodeAdminIndex:snaLuAdminLuIndex:snaLuSessnRluIndex:snaLuSessnIndex,current,,An entry contains dynamic parameters for an LU-LU session. The indices identify the Node, local LU, and remote LU for this session.
.1.3.6.1.2.1.34.1.2.3.1.1,SNA-NAU-MIB::snaLuSessnRluIndex,Integer32,read-only,,current,,This value may be used to identify information about the session partner LU in a table of information about remote LUs. Such a table is not defined in this document. If a table of remote LU information is not implemented, or if the table is implemented but it does not contain information about the partner LU for a particular session (as for dependent LU-LU sessions) then this object will have a value of zero.
.1.3.6.1.2.1.34.1.2.3.1.2,SNA-NAU-MIB::snaLuSessnIndex,Integer32,read-only,,current,,This value identifies the unique index of the session. It is recommended that an Agent should not reuse the index of a deactivated session for a significant period of time (e.g., one week).
.1.3.6.1.2.1.34.1.2.3.1.3,SNA-NAU-MIB::snaLuSessnLocalApplName,OCTET,read-only,,current,,The name of the local application using this LU. If the local application is unknown, then this object contains a zero length string.
.1.3.6.1.2.1.34.1.2.3.1.4,SNA-NAU-MIB::snaLuSessnRemoteLuName,OCTET,read-only,,current,,For dependent LUs which are indicated by the snaLuOperDepType object containing the value 'dependent (1)', this object contains the Primary LU (PLU) name. For independent LUs, this object contains the fully-qualified remote LU name of this 6.2 session. A fully qualified name is an SNA NAU entity name preceded by the NetId and a period as the delimiter.
.1.3.6.1.2.1.34.1.2.3.1.5,SNA-NAU-MIB::snaLuSessnMaxSndRuSize,INTEGER,read-only,,current,,The maximum RU size used on this session for sending RUs.
.1.3.6.1.2.1.34.1.2.3.1.6,SNA-NAU-MIB::snaLuSessnMaxRcvRuSize,INTEGER,read-only,,current,,The maximum RU size used on this session for receiving RUs.
.1.3.6.1.2.1.34.1.2.3.1.7,SNA-NAU-MIB::snaLuSessnSndPacingSize,INTEGER,read-only,,current,,The size of the send pacing window on this session.
.1.3.6.1.2.1.34.1.2.3.1.8,SNA-NAU-MIB::snaLuSessnRcvPacingSize,INTEGER,read-only,,current,,The size of the receive pacing window on this session.
.1.3.6.1.2.1.34.1.2.3.1.9,SNA-NAU-MIB::snaLuSessnActiveTime,TimeTicks,read-only,,current,,The timestamp (e.g., the Agent's sysUpTime value) when this session becomes active.
.1.3.6.1.2.1.34.1.2.3.1.10,SNA-NAU-MIB::snaLuSessnAdminState,INTEGER,read-write,,current,unbound(1):bound(3),The value indicates the desired operational state of the session. This object is used to change the operational state of the session. A Management Station can only change the operational state of the session to 'unbound (1)'. Session deactivation: If a session is in the operational state 'bound (3)' then setting the value of this object to 'unbound (1)' will initiate the session shutdown. If a session is in the operational state 'pendingBind (2)' then setting the value of this object to 'unbound (1)' will initiate the session shutdown. If a session is in the operational state 'pendingUnbind (4)' for an abnormally long period of time (e.g., three minutes) then setting the value of this object to 'unbound (1)' will change the session operational state to 'unbound (1)'. Note: for dependent LUs, deactivating the session is the same as deactivating the LU.
.1.3.6.1.2.1.34.1.2.3.1.11,SNA-NAU-MIB::snaLuSessnOperState,INTEGER,read-only,,current,unbound(1):pendingBind(2):bound(3):pendingUnbind(4),The value indicates the current operational state of the session. 'unbound (1)' - session has been unbound; in this state it will be removed from the session table by the Agent. 'pendingBind (2)' - this state has different meanings for dependent and independent LUs; for dependent LU - waiting for BIND from the host, for independent LU - waiting for BIND response. When a session enters this state, the corresponding entry in the session table is created by the Agent. 'bound (3)' - session has been successfully bound. 'pendingUnbind (4)' - session enters this state when an UNBIND is sent and before the rsp(UNBIND) is received.
.1.3.6.1.2.1.34.1.2.3.1.12,SNA-NAU-MIB::snaLuSessnSenseData,OCTET,read-only,,current,,The value identifies the sense code when there is a BIND failure. It is taken from the negative BIND response or UNBIND request. This is displayed as 8 hexadecimal digits.
.1.3.6.1.2.1.34.1.2.3.1.13,SNA-NAU-MIB::snaLuSessnTerminationRu,INTEGER,read-only,,current,other(1):bindFailure(2):unbind(3),The value identifies the SNA RU that terminated the session. If the session is not in the unbound state, this object has a value of 'other (1)'.
.1.3.6.1.2.1.34.1.2.3.1.14,SNA-NAU-MIB::snaLuSessnUnbindType,OCTET,read-only,,current,,If the session is in the unbound state, and it was terminated by an UNBIND, then this object contains the UNBIND type value (byte 1 of the UNBIND RU); otherwise the string is null.
.1.3.6.1.2.1.34.1.2.3.1.15,SNA-NAU-MIB::snaLuSessnLinkIndex,Integer32,read-only,,current,,This value identifies the link over which the session passes. It is an index into snaNodeLinkAdminTable. If the index value is not known, the value of this object shall be zero.
.1.3.6.1.2.1.34.1.2.4,SNA-NAU-MIB::snaLuSessnStatsTable,,not-accessible,,current,,This table contains dynamic statistics information relating to LU sessions. The entries in this table augment the entries in the snaLuSessnTable and cannot be created by a Management Station.
.1.3.6.1.2.1.34.1.2.4.1,SNA-NAU-MIB::snaLuSessnStatsEntry,,not-accessible,,current,,Contains statistics information for an LU session. Each entry is created by the Agent. Objects in this table have read-only access. Each session from snaLuSessnTable has one entry in this table.
.1.3.6.1.2.1.34.1.2.4.1.1,SNA-NAU-MIB::snaLuSessnStatsSentBytes,Counter32,read-only,,current,,The number of bytes sent by the local LU.
.1.3.6.1.2.1.34.1.2.4.1.2,SNA-NAU-MIB::snaLuSessnStatsReceivedBytes,Counter32,read-only,,current,,The number of bytes received by the local LU.
.1.3.6.1.2.1.34.1.2.4.1.3,SNA-NAU-MIB::snaLuSessnStatsSentRus,Counter32,read-only,,current,,The number of RUs sent by the local LU.
.1.3.6.1.2.1.34.1.2.4.1.4,SNA-NAU-MIB::snaLuSessnStatsReceivedRus,Counter32,read-only,,current,,The number of RUs received by the local LU.
.1.3.6.1.2.1.34.1.2.4.1.5,SNA-NAU-MIB::snaLuSessnStatsSentNegativeResps,Counter32,read-only,,current,,The number of negative responses sent by the local LU.
.1.3.6.1.2.1.34.1.2.4.1.6,SNA-NAU-MIB::snaLuSessnStatsReceivedNegativeResps,Counter32,read-only,,current,,The number of negative responses received by the local LU.
.1.3.6.1.2.1.34.1.2.5,SNA-NAU-MIB::snaLuTraps,,,,,,
.1.3.6.1.2.1.34.1.2.5.1,SNA-NAU-MIB::snaLuStateChangeTrap,,,,,,This trap indicates that the operational state (i.e., snaLuOperState value) of the LU has changed. The value of snaLuOperName indicates the name of the LU. The value of snaLuOperSnaName indicates the SNA name of LU. The value of snaLuOperState indicates the current state after change.
.1.3.6.1.2.1.34.1.2.5.2,SNA-NAU-MIB::snaLuSessnBindFailTrap,,,,,,This trap indicates the failure of a BIND. The value of snaLuSessnLocalApplName indicates the local application name. The value of snaLuSessnPartnerName indicates the partner name. The value of snaLuSessnOperState indicates the current state after change. The value of snaLuSessnBindFailureReason indicates the failure reason. The Agent should not generate more than 1 trap of this type per minute to minimize the level of management traffic on the network.
.1.3.6.1.2.1.34.1.3,SNA-NAU-MIB::snaMgtTools,,,,,,
.1.3.6.1.2.1.34.1.3.1,SNA-NAU-MIB::snaLuRtmTable,,not-accessible,,current,,This table contains Response Time Monitoring (RTM) information relating to an LU (Type 2). Each entry corresponds to an LU 2 entry in snaLuAdminTable.
.1.3.6.1.2.1.34.1.3.1.1,SNA-NAU-MIB::snaLuRtmEntry,,not-accessible,snaLuRtmPuIndex:snaLuRtmLuIndex,current,,Contains RTM information for an LU (Type 2). Each entry is created by the Agent.
.1.3.6.1.2.1.34.1.3.1.1.1,SNA-NAU-MIB::snaLuRtmPuIndex,Integer32,not-accessible,,current,,The value identifies the PU 2.0 with which this LU is associated.
.1.3.6.1.2.1.34.1.3.1.1.2,SNA-NAU-MIB::snaLuRtmLuIndex,Integer32,not-accessible,,current,,The value uniquely identifies an LU in a PU 2.0.
.1.3.6.1.2.1.34.1.3.1.1.3,SNA-NAU-MIB::snaLuRtmState,INTEGER,read-only,,current,off(1):on(2),The value indicates the current RTM state of an LU.
.1.3.6.1.2.1.34.1.3.1.1.4,SNA-NAU-MIB::snaLuRtmStateTime,TimeTicks,read-only,,current,,The timestamp (e.g., the Agent's sysUpTime value) when this session's RTM state (e.g., snaLuRtmState) changes value.
.1.3.6.1.2.1.34.1.3.1.1.5,SNA-NAU-MIB::snaLuRtmDef,INTEGER,read-only,,current,firstChar(1):kb(2):cdeb(3),The value indicates the mode of measurement for this RTM request. The values have following meaning: firstChar(1) - time to first character on screen kb(2) - time to keyboard usable by operator cdeb(3) - time to Change Direction/End Bracket.
.1.3.6.1.2.1.34.1.3.1.1.6,SNA-NAU-MIB::snaLuRtmBoundary1,Integer32,read-only,,current,,This object contains the value of the first boundary in units of 1/10th of a second.
.1.3.6.1.2.1.34.1.3.1.1.7,SNA-NAU-MIB::snaLuRtmBoundary2,Integer32,read-only,,current,,This object contains the value of the second boundary in units of 1/10th of a second.
.1.3.6.1.2.1.34.1.3.1.1.8,SNA-NAU-MIB::snaLuRtmBoundary3,Integer32,read-only,,current,,This object contains the value of the third boundary in units of 1/10th of a second.
.1.3.6.1.2.1.34.1.3.1.1.9,SNA-NAU-MIB::snaLuRtmBoundary4,Integer32,read-only,,current,,This object contains the value of the fourth boundary in units of 1/10th of a second.
.1.3.6.1.2.1.34.1.3.1.1.10,SNA-NAU-MIB::snaLuRtmCounter1,Counter32,read-only,,current,,This value indicates the number of transactions which fall in the range specified by the first boundary.
.1.3.6.1.2.1.34.1.3.1.1.11,SNA-NAU-MIB::snaLuRtmCounter2,Counter32,read-only,,current,,This value indicates the number of transactions which fall in the range specified by the second boundary.
.1.3.6.1.2.1.34.1.3.1.1.12,SNA-NAU-MIB::snaLuRtmCounter3,Counter32,read-only,,current,,This value indicates the number of transactions which fall in the range specified by the third boundary.
.1.3.6.1.2.1.34.1.3.1.1.13,SNA-NAU-MIB::snaLuRtmCounter4,Counter32,read-only,,current,,This value indicates the number of transactions which fall in the range specified by the fourth boundary.
.1.3.6.1.2.1.34.1.3.1.1.14,SNA-NAU-MIB::snaLuRtmOverFlows,Counter32,read-only,,current,,This value indicates the number of transactions which exceed the highest range specified by the boundaries.
.1.3.6.1.2.1.34.1.3.1.1.15,SNA-NAU-MIB::snaLuRtmObjPercent,Integer32,read-only,,current,,This value indicates the desired percentage of transactions which should be under a designated boundary range indicated by snaLuRtmObjRange.
.1.3.6.1.2.1.34.1.3.1.1.16,SNA-NAU-MIB::snaLuRtmObjRange,INTEGER,read-only,,current,other(1):range1(2):range2(3):range3(4):range4(5):range5(6),This value indicates the designated boundary range to which the snaLuRtmObject refers. The values have the following meanings: other(1) - not specified range1(2) - less than boundary 1 range2(3) - between boundary 1 and 2 range3(4) - between boundary 2 and 3 range4(5) - between boundary 3 and 4 range5(6) - greater than boundary 4.
.1.3.6.1.2.1.34.1.3.1.1.17,SNA-NAU-MIB::snaLuRtmNumTrans,Integer32,read-only,,current,,This value indicates the total number of transactions executed since the RTM monitoring began (i.e., snaLuRtmState changed to 'on(2)') for this LU.
.1.3.6.1.2.1.34.1.3.1.1.18,SNA-NAU-MIB::snaLuRtmLastRspTime,Integer32,read-only,,current,,This value indicates the response time for the last transaction in units of 1/10th of a second.
.1.3.6.1.2.1.34.1.3.1.1.19,SNA-NAU-MIB::snaLuRtmAvgRspTime,Integer32,read-only,,current,,This value indicates the average response time for all transactions in units of 1/10th of a second.
.1.3.6.1.2.1.34.2,SNA-NAU-MIB::snanauConformance,,,,,,
.1.3.6.1.2.1.34.2.1,SNA-NAU-MIB::snanauCompliances,,,,,,
.1.3.6.1.2.1.34.2.1.1,SNA-NAU-MIB::snanauCompliance,,,,,,The compliance statement for the SNMPv2 entities which implement the snanau MIB.
.1.3.6.1.2.1.34.2.2,SNA-NAU-MIB::snanauGroups,,,,,,
.1.3.6.1.2.1.34.2.2.1,SNA-NAU-MIB::snaNodeGroup,,,,,,A collection of objects providing the instrumentation of SNA nodes.
.1.3.6.1.2.1.34.2.2.2,SNA-NAU-MIB::snaLuGroup,,,,,,A collection of objects providing the instrumentation of SNA LUs.
.1.3.6.1.2.1.34.2.2.3,SNA-NAU-MIB::snaSessionGroup,,,,,,A collection of objects providing the instrumentation of SNA sessions.
.1.3.6.1.2.1.34.2.2.4,SNA-NAU-MIB::snaPu20Group,,,,,,A collection of objects providing the instrumentation of PU 2.0.
.1.3.6.1.2.1.34.2.2.5,SNA-NAU-MIB::snaMgtToolsRtmGroup,,,,,,A collection of objects providing the instrumentation of RTM for SNA LU 2.0.
.1.3.6.1.2.1.34.3,APPC-MIB::appcMIB,,,,,,This is the MIB module for objects used to manage network devices with APPC capabilities.
.1.3.6.1.2.1.34.3.1,APPC-MIB::appcObjects,,,,,,
.1.3.6.1.2.1.34.3.1.1,APPC-MIB::appcGlobal,,,,,,
.1.3.6.1.2.1.34.3.1.1.1,APPC-MIB::appcCntrlAdminGroup,,,,,,
.1.3.6.1.2.1.34.3.1.1.1.1,APPC-MIB::appcCntrlAdminStat,INTEGER,read-write,,current,notActive(1):active(2),Indicates the desired state of statistics collection: notActive collection of counters is not active. active collection of counters is active. When this object is set to notActive, all of the entries are removed from the appcSessStatsTable.
.1.3.6.1.2.1.34.3.1.1.1.2,APPC-MIB::appcCntrlAdminRscv,INTEGER,read-write,,current,notActive(1):active(2),Indicates the desired state of RSCV information collection: notActive collection of route selection control vectors is not active. active collection of route selection control vectors is active.
.1.3.6.1.2.1.34.3.1.1.1.3,APPC-MIB::appcCntrlAdminTrace,INTEGER,read-write,,current,notActive(1):active(2),Indicates the desired state of tracing: notActive collection of tracing information is not active active collection of tracing information is active
.1.3.6.1.2.1.34.3.1.1.1.4,APPC-MIB::appcCntrlAdminTraceParm,OCTET,read-write,,current,,Specifies the parameter to be used in conjunction with activating tracing. The actual content is implementation dependent.
.1.3.6.1.2.1.34.3.1.1.2,APPC-MIB::appcCntrlOperGroup,,,,,,
.1.3.6.1.2.1.34.3.1.1.2.1,APPC-MIB::appcCntrlOperStat,INTEGER,read-only,,current,notActive(1):active(2),Indicates the current collection options in effect: notActive collection of counters is not active. active collection of counters is active. Statistical entries are present in the appcSessStatsTable only when the value of this object is 'active'.
.1.3.6.1.2.1.34.3.1.1.2.2,APPC-MIB::appcCntrlOperStatTime,TimeTicks,read-only,,current,,Time since the appcCntrlOperStat object last changed. This time is in hundreds of a second.
.1.3.6.1.2.1.34.3.1.1.2.3,APPC-MIB::appcCntrlOperRscv,INTEGER,read-only,,current,notActive(1):active(2),Indicates the current collection options in effect: notActive collection of route selection control vectors is not active. active collection of route selection control vectors is active.
.1.3.6.1.2.1.34.3.1.1.2.4,APPC-MIB::appcCntrlOperRscvTime,TimeTicks,read-only,,current,,Time since the appcCntrlOperRscv object last changed. This time is in hundreds of a second.
.1.3.6.1.2.1.34.3.1.1.2.5,APPC-MIB::appcCntrlOperTrace,INTEGER,read-only,,current,notActive(1):active(2),Indicates the current state of tracing: notActive collection of tracing information is not active. active collection of tracing information is active.
.1.3.6.1.2.1.34.3.1.1.2.6,APPC-MIB::appcCntrlOperTraceTime,TimeTicks,read-only,,current,,Time since the appcCntrlOperTrace object last changed. This time is in hundreds of a second.
.1.3.6.1.2.1.34.3.1.1.2.7,APPC-MIB::appcCntrlOperTraceParm,OCTET,read-only,,current,,Specifies the parameter used in conjunction with activating tracing. The actual content is implementation dependent.
.1.3.6.1.2.1.34.3.1.1.3,APPC-MIB::appcGlobalObjects,,,,,,
.1.3.6.1.2.1.34.3.1.1.3.1,APPC-MIB::appcUpTime,TimeTicks,read-only,,current,,The time, in hundredths of a second, since the APPC portion of the system was last reinitialized.
.1.3.6.1.2.1.34.3.1.1.3.2,APPC-MIB::appcDefaultModeName,OCTET,read-only,,current,,Specifies the mode name to be used under the following conditions: When an incoming BIND request contains a mode name not defined at the local node. The parameters defined for this mode are used for the inbound implicit mode capability. When an APPC program issues an [MC_]ALLOCATE, [MC_]SEND_CONVERSATION, or CNOS verb, or when a CPI-C program issues an Allocate (CMALLC) call, specifying a mode name not defined at the local node. The parameters defined for this mode are used for the outbound implicit mode capability. This mode name must match a defined entry in the appcModeAdminTable.
.1.3.6.1.2.1.34.3.1.1.3.3,APPC-MIB::appcDefaultLuName,OCTET,read-only,,current,,Specifies the name of the local LU that is to serve as the default LU. This is the default LU to which are routed inbound BIND requests that exclude the secondary LU name. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. This local LU name must match a defined entry in the appcLluAdminTable.
.1.3.6.1.2.1.34.3.1.1.3.4,APPC-MIB::appcDefaultImplInbndPlu,INTEGER,read-only,,current,no(1):yes(2),Specifies whether or not inbound implicit partner LU support is enabled. The following values are defined: no - Specifies that inbound implicit partner LU support is disabled, which means that an incoming bind that specifies a partner LU that is not defined at the local node will be rejected. yes - Specifies that inbound implicit partner LU support is enabled, which provides the capability to accept an incoming BIND request that contains a partner LU name that is not defined at the local node.
.1.3.6.1.2.1.34.3.1.1.3.5,APPC-MIB::appcDefaultMaxMcLlSndSize,Integer32,read-only,,current,,Specifies the maximum size of a logical record to be used for a mapped conversation when sending data to either the inbound or outbound implicit partner LU. This size is the maximum number of bytes in a single logical record, as indicated in the LL field of the record. The default value is 32767. Note that this object does not limit the maximum size that an application program can supply on the Send Data call for a mapped conversation.
.1.3.6.1.2.1.34.3.1.1.3.6,APPC-MIB::appcDefaultFileSpec,OCTET,read-only,,current,,The local file specification that is to be searched by the APPC attach manager when no DEFINE_TP verb has been issued for the TP name received on an incoming attach. In this case, the attach manager will attempt to start a program whose file name is the same as the incoming TP name. If found, the program is loaded. If not found, the attach is rejected. The value '*' indicates that the normal search path for executable programs is to be used for locating an undefined transaction program. A null string indicates that there is no default file specification for undefined transaction programs.
.1.3.6.1.2.1.34.3.1.1.3.7,APPC-MIB::appcDefaultTpOperation,INTEGER,read-only,,current,other(1):queuedOperatorStarted(2):queuedOperatorPreloaded(3):queuedAmStarted(4):nonqueuedAmStarted(5),Specifies how the program will be started. other - Specifies that the default TP operation is none of the methods specified below. It may be a product-specific method. queuedOperatorStarted - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, APPC will issue a message to the operator to start the specified program. Subsequent attaches that arrive while the program is active will be queued. queuedOperatorPreloaded - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, the Attach will be rejected. The APPC attach manager determines that a TP has started upon reception of an APPC RECEIVE_ALLOCATE verb, or a CPI-C Accept_Conversation (CMACCP) or Specify_Local_TP_Name (CMSLTP) call. No message is sent to the operator. Subsequent attaches that arrive while the program is active are queued. queuedAmStarted - Specifies that one version of the program will be run at a time and will be started by the APPC attach manager. Subsequent attaches that arrive while the program is active will be queued. nonqueuedAmStarted - Specifies that multiple copies of the program will be run at a time and will be started by the APPC attach manager. 
.1.3.6.1.2.1.34.3.1.1.3.8,APPC-MIB::appcDefaultTpConvSecRqd,INTEGER,read-only,,current,no(1):yes(2),Specifies whether or not conversation security will be used for default TPs. no - Specifies that the incoming attach does not have to contain security information. yes - Specifies that the incoming attach must contain valid authentication information (e.g., user ID and password).
.1.3.6.1.2.1.34.3.1.1.3.9,APPC-MIB::appcLocalCpName,OCTET,read-only,,current,,Specifies the name of the local control point. This field is from 0 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.1.3.10,APPC-MIB::appcActiveSessions,Gauge32,read-only,,current,,Specifies the total number of active APPC sessions supported by this implementation. Sessions for which both LUs are local are counted twice.
.1.3.6.1.2.1.34.3.1.1.3.11,APPC-MIB::appcActiveHprSessions,Gauge32,read-only,,current,,Specifies the total number of active HPR APPC sessions.
.1.3.6.1.2.1.34.3.1.1.4,APPC-MIB::appcCnosControl,,,,,,
.1.3.6.1.2.1.34.3.1.1.4.1,APPC-MIB::appcCnosCommand,INTEGER,read-write,,current,initSesslimit(1):changeSesslimit(2):resetSesslimit(3),Specifies the CNOS command or verb to issue. First set the values of the particular CNOS parameter objects (from the range { appcCnosControl 2 } through { appcCnosControl 8 }) that apply to the CNOS command to be executed, set the three CNOS target objects ({ appcCnosControl 9 } through { appcCnosControl 11 }), then set this object to the command to be executed. Here is the list of parameter objects that must be set for each of the CNOS commands: INIT_SESSION_LIMIT - appcCnosMaxSessLimit appcCnosMinCwinLimit appcCnosMinClosLimit appcCnosTargetLocLuName appcCnosTargetParLuName appcCnosTargetModeName CHANGE_SESSION_LIMIT - appcCnosMaxSessLimit appcCnosMinCwinLimit appcCnosMinClosLimit appcCnosResponsible appcCnosTargetLocLuName appcCnosTargetParLuName appcCnosTargetModeName RESET_SESSION_LIMIT - appcCnosResponsible appcCnosDrainPart appcCnosForce appcCnosTargetLocLuName appcCnosTargetParLuName appcCnosTargetModeName 
.1.3.6.1.2.1.34.3.1.1.4.2,APPC-MIB::appcCnosMaxSessLimit,Integer32,read-write,,current,,Specifies the maximum value that the local LU is to use, during CNOS processing, for the session limit. The local LU, as a target LU, will negotiate a higher session limit it receives in the CNOS request down to this maximum value. The local LU, as a source LU, will restrict the session limit it sends in a CNOS request to a value less than or equal to this maximum value. If set (i.e., greater than 0), this overrides the maximum session limit defined in the appcModeAdminTable. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the INITIALIZE_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.
.1.3.6.1.2.1.34.3.1.1.4.3,APPC-MIB::appcCnosMinCwinLimit,Integer32,read-write,,current,,Specifies the default minimum contention winner sessions limit. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the INITIALIZE_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.
.1.3.6.1.2.1.34.3.1.1.4.4,APPC-MIB::appcCnosMinClosLimit,Integer32,read-write,,current,,Specifies the default minimum contention loser sessions limit. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the INITIALIZE_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.
.1.3.6.1.2.1.34.3.1.1.4.5,APPC-MIB::appcCnosDrainSelf,INTEGER,read-write,,current,no(1):yes(2),Specifies whether the local LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the local LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stopped or BIS protocol). This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies only to the RESET_SESSION_LIMIT verb.
.1.3.6.1.2.1.34.3.1.1.4.6,APPC-MIB::appcCnosDrainPart,INTEGER,read-write,,current,no(1):yes(2),Specifies whether the partner LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the partner LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stop or BIS protocol). This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies only to the RESET_SESSION_LIMIT verb.
.1.3.6.1.2.1.34.3.1.1.4.7,APPC-MIB::appcCnosResponsible,INTEGER,read-write,,current,source(1):target(2),Specifies which LU is responsible for selecting and deactivating sessions as a result of a change that decreases the session limit or the maximum number of contention winner sessions for the source or target LU. If no session need to be deactivated, this parameter is ignored. source - specifies that the source (local) LU is responsible. The target (partner) LU cannot negotiate this value. target - specifies that the target (partner) LU is responsible. The target LU can negotiate this value to source. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to the RESET_SESSION_LIMIT and CHANGE_SESSION_LIMIT verbs.
.1.3.6.1.2.1.34.3.1.1.4.8,APPC-MIB::appcCnosForce,INTEGER,read-write,,current,no(1):yes(2),Specifies whether the local LU should force the resetting of the session limit when certain error conditions occur that prevent the successful exchange of CNOS request and reply. This parameter should be set to the desired value before setting the command (appcCnosCommand). This parameter applies only to the RESET_SESSION_LIMIT verb.
.1.3.6.1.2.1.34.3.1.1.4.9,APPC-MIB::appcCnosTargetLocLuName,OCTET,read-write,,current,,The SNA name of the local LU to which the CNOS command is to be applied. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. This object should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to all CNOS verbs.
.1.3.6.1.2.1.34.3.1.1.4.10,APPC-MIB::appcCnosTargetParLuName,OCTET,read-write,,current,,The SNA name of the partner LU to which the CNOS command is to be applied. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. This object should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to all CNOS verbs.
.1.3.6.1.2.1.34.3.1.1.4.11,APPC-MIB::appcCnosTargetModeName,OCTET,read-write,,current,,Specifies the mode name to which the CNOS command is to be applied. This object should be set to the desired value before setting the command (appcCnosCommand). This parameter applies to all CNOS verbs.
.1.3.6.1.2.1.34.3.1.2,APPC-MIB::appcLu,,,,,,
.1.3.6.1.2.1.34.3.1.2.1,APPC-MIB::appcLluAdminTable,,not-accessible,,current,,APPC Local LU Admin Table.
.1.3.6.1.2.1.34.3.1.2.1.1,APPC-MIB::appcLluAdminEntry,,not-accessible,appcLluAdminName,current,,Information about local APPC LUs. 
.1.3.6.1.2.1.34.3.1.2.1.1.1,APPC-MIB::appcLluAdminName,OCTET,not-accessible,,current,,Specifies the name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.2.1.1.2,APPC-MIB::appcLluAdminDepType,INTEGER,read-only,,current,dependent(1):independent(2),This value identifies whether the LU is dependent or independent.
.1.3.6.1.2.1.34.3.1.2.1.1.3,APPC-MIB::appcLluAdminLocalAddress,OCTET,read-only,,current,,The local address for this LU is a byte with a value ranging from 0 to 254. For dependent LUs, this value ranges from 1 to 254; for independent LUs this value is always 0.
.1.3.6.1.2.1.34.3.1.2.1.1.4,APPC-MIB::appcLluAdminSessLimit,Integer32,read-only,,current,,The maximum number of sessions supported by this LU.
.1.3.6.1.2.1.34.3.1.2.1.1.5,APPC-MIB::appcLluAdminBindRspMayQ,INTEGER,read-only,,current,no(1):yes(2),Indicates whether or not the local LU, as the sender of a BIND request, allows a partner partner LU to delay sending the BIND response if the partner LU cannot process the BIND request immediately.
.1.3.6.1.2.1.34.3.1.2.1.1.6,APPC-MIB::appcLluAdminCompression,INTEGER,read-only,,current,prohibited(1):required(2):negotiable(3),Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated.
.1.3.6.1.2.1.34.3.1.2.1.1.7,APPC-MIB::appcLluAdminInBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcLluAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.1.1.8,APPC-MIB::appcLluAdminOutBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcLluAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.1.1.9,APPC-MIB::appcLluAdminCompRleBeforeLZ,INTEGER,read-only,,current,no(1):yes(2),Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used.
.1.3.6.1.2.1.34.3.1.2.1.1.10,APPC-MIB::appcLluAdminAlias,OCTET,read-only,,current,,A local alias for the local LU. If not known or not applicable, this object contains a zero-length string.
.1.3.6.1.2.1.34.3.1.2.2,APPC-MIB::appcLluOperTable,,not-accessible,,current,,APPC Local LU Operational Table.
.1.3.6.1.2.1.34.3.1.2.2.1,APPC-MIB::appcLluOperEntry,,not-accessible,appcLluOperName,current,,Information about local APPC LUs.
.1.3.6.1.2.1.34.3.1.2.2.1.1,APPC-MIB::appcLluOperName,OCTET,not-accessible,,current,,Specifies the name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.2.2.1.2,APPC-MIB::appcLluOperDepType,INTEGER,read-only,,current,dependent(1):independent(2),This value identifies whether the LU is dependent or independent.
.1.3.6.1.2.1.34.3.1.2.2.1.3,APPC-MIB::appcLluOperLocalAddress,OCTET,read-only,,current,,The local address for this LU is a byte with a value ranging from 0 to 254. For dependent LUs, this value ranges from 1 to 254; for independent LUs this value is always 0.
.1.3.6.1.2.1.34.3.1.2.2.1.4,APPC-MIB::appcLluOperSessLimit,Integer32,read-only,,current,,The maximum number of sessions supported by this LU.
.1.3.6.1.2.1.34.3.1.2.2.1.5,APPC-MIB::appcLluOperBindRspMayQ,INTEGER,read-only,,current,no(1):yes(2),Indicates whether or not the local LU, as the sender of a BIND request, allows a partner LU to delay sending the BIND response if the partner LU cannot process the BIND request immediately.
.1.3.6.1.2.1.34.3.1.2.2.1.6,APPC-MIB::appcLluOperCompression,INTEGER,read-only,,current,prohibited(1):required(2):negotiable(3),Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated.
.1.3.6.1.2.1.34.3.1.2.2.1.7,APPC-MIB::appcLluOperInBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcLluOperCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.2.1.8,APPC-MIB::appcLluOperOutBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcLluAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.2.1.9,APPC-MIB::appcLluOperCompRleBeforeLZ,INTEGER,read-only,,current,no(1):yes(2),Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used.
.1.3.6.1.2.1.34.3.1.2.2.1.10,APPC-MIB::appcLluOperAlias,OCTET,read-only,,current,,A local alias for the local LU. If not known or not applicable, this object contains a zero-length string.
.1.3.6.1.2.1.34.3.1.2.2.1.11,APPC-MIB::appcLluOperActiveSessions,Gauge32,read-only,,current,,Specifies the total number of active APPC sessions for this LU.
.1.3.6.1.2.1.34.3.1.2.3,APPC-MIB::appcLuPairAdminTable,,not-accessible,,current,,APPC Partner LU administrative Table
.1.3.6.1.2.1.34.3.1.2.3.1,APPC-MIB::appcLuPairAdminEntry,,not-accessible,appcLuPairAdminLocLuName:appcLuPairAdminParLuName,current,,Entry of APPC Partner LU Information Table. It is indexed by the local and partner LU Names.
.1.3.6.1.2.1.34.3.1.2.3.1.1,APPC-MIB::appcLuPairAdminLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU to which this partner LU definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the partner LU definition applies to all local LUs, and not just to a single local LU.
.1.3.6.1.2.1.34.3.1.2.3.1.2,APPC-MIB::appcLuPairAdminParLuName,OCTET,not-accessible,,current,,The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.2.3.1.3,APPC-MIB::appcLuPairAdminParLuAlias,OCTET,read-only,,current,,A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.
.1.3.6.1.2.1.34.3.1.2.3.1.4,APPC-MIB::appcLuPairAdminSessLimit,Integer32,read-only,,current,,The maximum number of sessions supported by this partner LU.
.1.3.6.1.2.1.34.3.1.2.3.1.5,APPC-MIB::appcLuPairAdminSessSec,INTEGER,read-only,,current,required(1):accepted(2):notAllowed(3),Specifies the type of session-level security information that a local LU will accept on BIND requests it receives from the partner LU. required - Specifies that the BIND request must carry session level verification information that will be verified upon receipt. accepted - Specifies that the BIND request may carry session level verification information that will be verified upon receipt. notAllowed - Specifies that the BIND request must not carry session level verification information.
.1.3.6.1.2.1.34.3.1.2.3.1.6,APPC-MIB::appcLuPairAdminSecAccept,INTEGER,read-only,,current,none(1):conversation(2):alreadyVerified(3):persistentVerification(4):aVandpV(5),Specifies support for different levels of access security information in ATTACH requests received from this partner LU. Possible values are: none - No access security information will be accepted on allocation requests (ATTACH) from this LU. conversation - Allocation requests will not be accepted that include already verified or persistent verification indicators. Accept conversation-level access security information, which must include both a user Id and password, and may also include a profile. alreadyVerified - Allocation requests will be accepted that include already verified indicators. Persistent verification indicators will not be accepted. persistentVerification - Allocation requests will be accepted that include persistent verification indicators. Already verified indicators will not be accepted. aVandpV - Allocation requests will be accepted that include already verified or persistent verification indicators.
.1.3.6.1.2.1.34.3.1.2.3.1.7,APPC-MIB::appcLuPairAdminLinkObjId,OBJECT,read-only,,current,,Specifies the link associated with this partner LU. This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module). This object may be NULL if the link is not specified or if a link is not applicable (as for APPN-level nodes).
.1.3.6.1.2.1.34.3.1.2.3.1.8,APPC-MIB::appcLuPairAdminParaSessSup,INTEGER,read-only,,current,no(1):yes(2),Defined Parallel Sessions Supported. Indicates whether or not multiple sessions between the partner LU and its associated local LU are permitted. Parallel session support also indicates that Change Number of Sessions (CNOS) will be used to negotiate session limits between the LUs.
.1.3.6.1.2.1.34.3.1.2.4,APPC-MIB::appcLuPairOperTable,,not-accessible,,current,,Table of active partner/local LU pairs. Two entries are present in the table when both LUs in a pair are local.
.1.3.6.1.2.1.34.3.1.2.4.1,APPC-MIB::appcLuPairOperEntry,,not-accessible,appcLuPairOperLocLuName:appcLuPairOperParLuName,current,,Entry representing one partner/local LU pair.
.1.3.6.1.2.1.34.3.1.2.4.1.1,APPC-MIB::appcLuPairOperLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).
.1.3.6.1.2.1.34.3.1.2.4.1.2,APPC-MIB::appcLuPairOperParLuName,OCTET,not-accessible,,current,,The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.2.4.1.3,APPC-MIB::appcLuPairOperParLuAlias,OCTET,read-only,,current,,A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.
.1.3.6.1.2.1.34.3.1.2.4.1.4,APPC-MIB::appcLuPairOperSessLimit,Integer32,read-only,,current,,The maximum number of sessions supported by this partner LU.
.1.3.6.1.2.1.34.3.1.2.4.1.5,APPC-MIB::appcLuPairOperSessSec,INTEGER,read-only,,current,required(1):accepted(2):notAllowed(3),Specifies the type of security information that a local LU will accept on BIND requests it receives from the partner LU. required - Specifies that the BIND request must carry session level verification information that will be verified upon receipt. accepted - Specifies that the BIND request may carry session level verification information that will be verified upon receipt. notAllowed - Specifies that the BIND request must not carry session level verification information.
.1.3.6.1.2.1.34.3.1.2.4.1.6,APPC-MIB::appcLuPairOperSecAccept,INTEGER,read-only,,current,none(1):conversation(2):alreadyVerified(3):persistentVerification(4):aVandpV(5),Specifies support for different levels of security acceptance information in ATTACH requests received from this partner LU. Possible values are: none - No access security information will be accepted on allocation requests (ATTACH) from this LU. conversation - Allocation requests will not be accepted that include already verified or persistent verification indicators. Accept conversation-level access security information, which must include both a user Id and password, and may also include a profile. alreadyVerified - Allocation requests will be accepted that include already verified indicators. Persistent verification indicators will not be accepted. persistentVerification - Allocation requests will be accepted that include persistent verification indicators. Already verified indicators will not be accepted. aVandpV - Allocation requests will be accepted that include already verified or persistent verification indicators.
.1.3.6.1.2.1.34.3.1.2.4.1.7,APPC-MIB::appcLuPairOperLinkObjId,OBJECT,read-only,,current,,Specifies the link associated with this partner LU. This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module). This object may be NULL if the link is not specified or if a link is not applicable (as for APPN-level nodes).
.1.3.6.1.2.1.34.3.1.2.4.1.8,APPC-MIB::appcLuPairOperParaSessSup,INTEGER,read-only,,current,no(1):yes(2),Active Parallel Sessions Supported. Indicates whether or not multiple session between the partner LU and its associated local LU are permitted. Parallel session support also indicates that Change Number of Sessions (CNOS) will be used to negotiate session limits between the LUs.
.1.3.6.1.2.1.34.3.1.2.4.1.9,APPC-MIB::appcLuPairOperParaSessSupLS,INTEGER,read-only,,current,no(1):yes(2),Active Parallel Sessions Supported - last starting value. This object represents the initial value proposed by the local LU the last time this capability was negotiated, i.e., when the first session was bound between the local LU and its partner.
.1.3.6.1.2.1.34.3.1.2.4.1.10,APPC-MIB::appcLuPairOperState,INTEGER,read-only,,current,inactive(1):active(2),The value identifies the current operational state of this LU pair: inactive (1) - no active or pending session exists between the LUs. active (2) - an active or pending session exists between the LUs.
.1.3.6.1.2.1.34.3.1.2.5,APPC-MIB::appcModeAdminTable,,not-accessible,,current,,APPC Mode Table
.1.3.6.1.2.1.34.3.1.2.5.1,APPC-MIB::appcModeAdminEntry,,not-accessible,appcModeAdminLocLuName:appcModeAdminParLuName:appcModeAdminModeName,current,,Entry of APPC Mode Information Table.
.1.3.6.1.2.1.34.3.1.2.5.1.1,APPC-MIB::appcModeAdminLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU to which this mode definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the mode definition applies to all local LUs for the SNA node identified by appcLocalCpName, and not just to a single local LU.
.1.3.6.1.2.1.34.3.1.2.5.1.2,APPC-MIB::appcModeAdminParLuName,OCTET,not-accessible,,current,,The SNA name of the partner LU to which this mode definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the mode definition applies to all partner LUs for the SNA node identified by appcModeAdminLocLuName, and not just to a single partner LU.
.1.3.6.1.2.1.34.3.1.2.5.1.3,APPC-MIB::appcModeAdminModeName,OCTET,not-accessible,,current,,Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters). 
.1.3.6.1.2.1.34.3.1.2.5.1.4,APPC-MIB::appcModeAdminCosName,OCTET,read-only,,current,,Specifies the class of service (COS) name associated with this mode. If the implementation does not support COS names, a null string is returned.
.1.3.6.1.2.1.34.3.1.2.5.1.5,APPC-MIB::appcModeAdminSessEndTpName,OCTET,read-only,,current,,Specifies the name of the transaction program (TP) to be invoked when a session using this mode is deactivated or ended. If no such TP is defined, this object is a null string. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non- displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes). 
.1.3.6.1.2.1.34.3.1.2.5.1.6,APPC-MIB::appcModeAdminMaxSessLimit,Integer32,read-only,,current,,Specifies the maximum value that the local LU is to use, during CNOS processing, for the session limit. The local LU, as a target LU, will negotiate a higher session limit it receives in the CNOS request down to this maximum value. The local LU, as a source LU, will restrict the session limit it sends in a CNOS request to a value less than or equal to this maximum value.
.1.3.6.1.2.1.34.3.1.2.5.1.7,APPC-MIB::appcModeAdminMinCwinLimit,Integer32,read-only,,current,,Specifies the default minimum contention winner sessions limit. Some implementations internally issue a INITIALIZE_SESSION_LIMIT verb when a Mode is created. This value is the parameter used for the CNOS processing of that verb. This parameter is not used when issuing an explicit INITIALIZE_SESSION_LIMIT verb. The equivalent object in appcCnosCommandTable is used.
.1.3.6.1.2.1.34.3.1.2.5.1.8,APPC-MIB::appcModeAdminMinClosLimit,Integer32,read-only,,current,,Specifies the default minimum contention loser sessions limit. Some implementations internally issue a INITIALIZE_SESSION_LIMIT verb when a Mode is created. This value is the parameter used for the CNOS processing of that verb. This is the same as target minimum contention winner sessions. This parameter is not used when issuing an explicit INITIALIZE_SESSION_LIMIT verb. The equivalent object in appcCnosCommandTable is used.
.1.3.6.1.2.1.34.3.1.2.5.1.9,APPC-MIB::appcModeAdminConWinAutoActLmt,Integer32,read-only,,current,,Specifies the limit on the number of contention winner sessions to be automatically activated when the minimum number of contention winner sessions increases (as a result of CNOS processing). The actual number of sessions activated is the lesser of this value and the new minimum number of contention winner sessions. 
.1.3.6.1.2.1.34.3.1.2.5.1.10,APPC-MIB::appcModeAdminRecvPacWinSz,Integer32,read-only,,current,,Specifies the size of the receive pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing No limit on window size fixed pacing No pacing is supported
.1.3.6.1.2.1.34.3.1.2.5.1.11,APPC-MIB::appcModeAdminSendPacWinSz,Integer32,read-only,,current,,Specifies the size of the send pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing No limit on window size fixed pacing No pacing is supported
.1.3.6.1.2.1.34.3.1.2.5.1.12,APPC-MIB::appcModeAdminPrefRecvRuSz,Integer32,read-only,,current,,Specifies the preferred receive RU (Request Unit) size of normal-flow requests on the sessions. This value must be less than or equal to the value specified in appcModeAdminRecvRuSzUpBnd and greater than or equal to the value specified in appcModeAdminRecvRuSzLoBnd. The local LU specifies this value for the receive maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeAdminRecvRuSzUpBnd value or down to the appcModeAdminRecvRuSzLoBnd value.
.1.3.6.1.2.1.34.3.1.2.5.1.13,APPC-MIB::appcModeAdminPrefSendRuSz,Integer32,read-only,,current,,Specifies the preferred send RU (Request Unit) size of normal- flow requests on the sessions. This value must be less than or equal to the value specified in appcModeAdminSendRuSzUpBnd and greater than or equal to the value specified in appcModeAdminSendRuSzLoBnd. The local LU specifies this value for the send maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeAdminSendRuSzUpBnd value or down to the appcModeAdminSendRuSzLoBnd value.
.1.3.6.1.2.1.34.3.1.2.5.1.14,APPC-MIB::appcModeAdminRecvRuSzUpBnd,Integer32,read-only,,current,,Specifies the upper bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.5.1.15,APPC-MIB::appcModeAdminSendRuSzUpBnd,Integer32,read-only,,current,,Specifies the upper bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.5.1.16,APPC-MIB::appcModeAdminRecvRuSzLoBnd,Integer32,read-only,,current,,Specifies the lower bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.5.1.17,APPC-MIB::appcModeAdminSendRuSzLoBnd,Integer32,read-only,,current,,Specifies the lower bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.5.1.18,APPC-MIB::appcModeAdminSingSessReinit,INTEGER,read-only,,current,notApplicable(1):operatorControlled(2):primaryOnly(3):secondaryOnly(4):primaryOrSecondary(5),Specifies the responsibility for session reinitiation of a single session with the partner LU (when the session goes down). The local LU uses this parameter to specify the session reinitiation responsibility in session activation (SNA BIND) requests and responses. notApplicable - specifies that this parameter has no meaning since the value of appcLuPairAdminParaSessSup is yes. The field in the SNA BIND is reserved (set to zero). operatorControlled - specifies that neither LU will automatically attempt to reinitiate the session. The operator on either side will manually reactivate the session. A contention race (both side reinitiating at the same time) is won by the LU with the lexicographically greater fully- qualified LU name. primaryOnly - specifies that the primary LU will automatically attempt to reinitiate the session. secondaryOnly - specifies that the secondary LU will automatically attempt to reinitiate the session. primaryOrSecondary - specifies that either the primary or the secondary may automatically attempt to reinitiate the session. A contention race is handled the same way as with operatorControlled. 
.1.3.6.1.2.1.34.3.1.2.5.1.19,APPC-MIB::appcModeAdminCompression,INTEGER,read-only,,current,prohibited(1):required(2):negotiable(3),Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated.
.1.3.6.1.2.1.34.3.1.2.5.1.20,APPC-MIB::appcModeAdminInBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcModeAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.5.1.21,APPC-MIB::appcModeAdminOutBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcModeAdminCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.5.1.22,APPC-MIB::appcModeAdminCompRleBeforeLZ,INTEGER,read-only,,current,no(1):yes(2),Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used.
.1.3.6.1.2.1.34.3.1.2.5.1.23,APPC-MIB::appcModeAdminSyncLvl,INTEGER,read-only,,current,none(1):noneConfirm(2):noneConfirmSyncPoint(3),Specifies the sync level support. This value is used for negotiation during session activations (SNA BIND). none - No sync level is supported. noneConfirm - None and Confirm levels supported. noneConfirmSyncPoint - None, Confirm, and Sync Point is supported. 
.1.3.6.1.2.1.34.3.1.2.5.1.24,APPC-MIB::appcModeAdminCrypto,INTEGER,read-only,,current,notSupported(1):selective(3),Specifies whether session-level cryptography is supported. This value is used for negotiation during session activations (SNA BIND). notSupported - Specifies session-level cryptography is not to be used. mandatory - Specifies session-level cryptography must be used. selective - Specifies session-level cryptography is required just on selected requests flowing on the sessions.
.1.3.6.1.2.1.34.3.1.2.6,APPC-MIB::appcModeOperTable,,not-accessible,,current,,Operational APPC Mode Information. Two entries are present in the table when both LUs in a pair are local.
.1.3.6.1.2.1.34.3.1.2.6.1,APPC-MIB::appcModeOperEntry,,not-accessible,appcModeOperLocLuName:appcModeOperParLuName:appcModeOperModeName,current,,Entry of APPC mode operational information table. This entry does not augment the appcModeAdminEntry, but reflects an actual operational mode for a given local LU - partner LU pair.
.1.3.6.1.2.1.34.3.1.2.6.1.1,APPC-MIB::appcModeOperLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).
.1.3.6.1.2.1.34.3.1.2.6.1.2,APPC-MIB::appcModeOperParLuName,OCTET,not-accessible,,current,,The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).
.1.3.6.1.2.1.34.3.1.2.6.1.3,APPC-MIB::appcModeOperModeName,OCTET,not-accessible,,current,,Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters). 
.1.3.6.1.2.1.34.3.1.2.6.1.4,APPC-MIB::appcModeOperCosName,OCTET,read-only,,current,,Specifies the class of service (COS) name associated with this mode. If the implementation does not support COS names, a zero-length string is returned.
.1.3.6.1.2.1.34.3.1.2.6.1.5,APPC-MIB::appcModeOperSessEndTpName,OCTET,read-only,,current,,Specifies the name of the transaction program (TP) to be invoked when a session using this mode is deactivated or ended. If the name is NULL, no transaction program is invoked. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non- displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes).
.1.3.6.1.2.1.34.3.1.2.6.1.6,APPC-MIB::appcModeOperSessLimit,Integer32,read-only,,current,,Specifies the current session limit of this mode as negotiated through APPC CNOS (Change Number of Sessions) processing. Identifies the total number of sessions that can be established between the local and partner LU using this mode.
.1.3.6.1.2.1.34.3.1.2.6.1.7,APPC-MIB::appcModeOperMaxSessLimit,Integer32,read-only,,current,,Specifies the maximum value that the local LU is to use, during CNOS processing, for the session limit. The local LU, as a target LU, will negotiate a higher session limit it receives in the CNOS request down to this maximum value. The local LU, as a source LU, will restrict the session limit it sends in a CNOS request to a value less than or equal to this maximum value.
.1.3.6.1.2.1.34.3.1.2.6.1.8,APPC-MIB::appcModeOperMinCwinLimit,Integer32,read-only,,current,,Specifies the minimum contention winner sessions limit that was negotiated via CNOS processing.
.1.3.6.1.2.1.34.3.1.2.6.1.9,APPC-MIB::appcModeOperMinClosLimit,Integer32,read-only,,current,,Specifies the minimum contention loser sessions limit that was negotiated via CNOS processing. This is the same as target minimum contention winner sessions.
.1.3.6.1.2.1.34.3.1.2.6.1.10,APPC-MIB::appcModeOperConWinAutoActLmt,Integer32,read-only,,current,,Specifies the limit on the number of contention winner sessions to be automatically activated when the minimum number of contention winner sessions increases (as a result of CNOS processing). The actual number of sessions activated is the lesser of this value and the new minimum number of contention winner sessions. 
.1.3.6.1.2.1.34.3.1.2.6.1.11,APPC-MIB::appcModeOperRecvPacWinSz,Integer32,read-only,,current,,Specifies the size of the receive pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing - No limit on window size fixed pacing - No pacing is supported
.1.3.6.1.2.1.34.3.1.2.6.1.12,APPC-MIB::appcModeOperSendPacWinSz,Integer32,read-only,,current,,Specifies the size of the send pacing window. This value is used for negotiation during session activations (SNA BIND). The meaning of this value when set to 0 depends on whether adaptive pacing is supported: adaptive pacing No limit on window size fixed pacing No pacing is supported
.1.3.6.1.2.1.34.3.1.2.6.1.13,APPC-MIB::appcModeOperPrefRecvRuSz,Integer32,read-only,,current,,Specifies the preferred receive RU (Request Unit) size of normal-flow requests on the sessions. This value must be less than or equal to the value specified in appcModeOperRecvRuSzUpBnd and greater than or equal to the value specified in appcModeOperRecvRuSzLoBnd. The local LU specifies this value for the receive maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeOperRecvRuSzUpBnd value or down to the appcModeOperRecvRuSzLoBnd value.
.1.3.6.1.2.1.34.3.1.2.6.1.14,APPC-MIB::appcModeOperPrefSendRuSz,Integer32,read-only,,current,,Specifies the preferred send RU (Request Unit) size of normal- flow requests on the sessions. This value must be less than or equal to the value specified in appcModeOperSendRuSzUpBnd and greater than or equal to the value specified in appcModeOperSendRuSzLoBnd. The local LU specifies this value for the send maximum RU size in session activation (SNA BIND) requests and responses. It will allow negotiation up to the appcModeOperSendRuSzUpBnd value or down to the appcModeOperSendRuSzLoBnd value.
.1.3.6.1.2.1.34.3.1.2.6.1.15,APPC-MIB::appcModeOperRecvRuSzUpBnd,Integer32,read-only,,current,,Specifies the upper bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.6.1.16,APPC-MIB::appcModeOperSendRuSzUpBnd,Integer32,read-only,,current,,Specifies the upper bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.6.1.17,APPC-MIB::appcModeOperRecvRuSzLoBnd,Integer32,read-only,,current,,Specifies the lower bound for the maximum receive RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.6.1.18,APPC-MIB::appcModeOperSendRuSzLoBnd,Integer32,read-only,,current,,Specifies the lower bound for the maximum send RU (Request Unit) size of normal-flow requests. This is used for negotiation during session activations (SNA BIND). 
.1.3.6.1.2.1.34.3.1.2.6.1.19,APPC-MIB::appcModeOperSingSessReinit,INTEGER,read-only,,current,notApplicable(1):operatorControlled(2):primaryOnly(3):secondaryOnly(4):primaryOrSecondary(5),Specifies the responsibility for session reinitiation of a single session with the partner LU (when the session goes down). The local LU uses this parameter to specify the session reinitiation responsibility in session activation (SNA BIND) requests and responses. notApplicable - specifies that this parameter has no meaning since the value of appcLuPairOperParaSessSup is yes. The field in the SNA BIND is reserved (set to zero). operatorControlled - specifies that neither LU will automatically attempt to reinitiate the session. The operator on either side will manually reactivate the session. A contention race (both side reinitiating at the same time) is won by the LU with the lexicographically greater fully- qualified LU name. primaryOnly - specifies that the primary LU will automatically attempt to reinitiate the session. secondaryOnly - specifies that the secondary LU will automatically attempt to reinitiate the session. primaryOrSecondary - specifies that either the primary or the secondary may automatically attempt to reinitiate the session. A contention race is handled the same way as with operatorControlled. 
.1.3.6.1.2.1.34.3.1.2.6.1.20,APPC-MIB::appcModeOperCompression,INTEGER,read-only,,current,prohibited(1):required(2):negotiable(3),Specifies whether compression is supported. The local LU uses this value for negotiation during session activation (SNA BIND). prohibited - specifies that no compression is to be used. required - specifies that compression is required. negotiable - specifies that the usage of compression is to be negotiated between the LUs. The level of compression is also negotiated.
.1.3.6.1.2.1.34.3.1.2.6.1.21,APPC-MIB::appcModeOperInBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for inbound data. The local LU uses this value in conjunction with appcModeOperCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.6.1.22,APPC-MIB::appcModeOperOutBoundCompLevel,INTEGER,read-only,,current,none(1):rle(2):lz9(3):lz10(4):lz12(5),Specifies the maximum level of compression supported for outbound data. The local LU uses this value in conjunction with appcModeOperCompression for negotiation during session activation (SNA BIND). none - specifies that no compression is to be used. rle - specifies run-length encoding compression in which a 1 or 2 byte sequence substitution is used for each repeated run of the same character. lz9 - specifies Lempel-Ziv-like compression in which 9 bit codes are used to substitute repeated substrings in the data stream. These codes are indices that refer to entries in a common dictionary generated adaptively at both sender and receiver as the data flows and compression occurs. The larger of number bits used for the code, the more storage space is required for the dictionary, but the larger the compression ratio. lz10 - specifies a 10 bit code Lempel-Ziv-like compression. lz12 - specifies a 12 bit code Lempel-Ziv-like compression.
.1.3.6.1.2.1.34.3.1.2.6.1.23,APPC-MIB::appcModeOperCompRleBeforeLZ,INTEGER,read-only,,current,no(1):yes(2),Specifies whether run-length encoding is to be applied to the data before applying Lempel-Ziv-like compression. The local LU uses this value for negotiation during session activation (SNA BIND). This parameter is only supported if LZ compression is used.
.1.3.6.1.2.1.34.3.1.2.6.1.24,APPC-MIB::appcModeOperSyncLvl,INTEGER,read-only,,current,none(1):noneConfirm(2):noneConfirmSyncPoint(3),Specifies the sync level support for sessions involving this LU pair and mode name. none - No sync level is supported. noneConfirm - None and Confirm level supported. noneConfirmSyncPoint - None, Confirm and Sync Point is supported. 
.1.3.6.1.2.1.34.3.1.2.6.1.25,APPC-MIB::appcModeOperCrypto,INTEGER,read-only,,current,notSupported(1):selective(3),Specifies whether session-level cryptography is supported for sessions involving this LU pair and mode name. notSupported - Specifies session-level cryptography is not being used. mandatory - Specifies session-level cryptography in being used on all requests flowing on the sessions. selective - Specifies session-level cryptography is required just on selected requests flowing on the sessions.
.1.3.6.1.2.1.34.3.1.2.6.1.26,APPC-MIB::appcModeOperSyncLvlLastStart,INTEGER,read-only,,current,none(1):noneConfirm(2):noneConfirmSyncPoint(3),Specifies the sync level support. This value represents the initial value proposed by the local LU the last time this capability was negotiated, i.e., when the first session was bound between the local LU and its partner. none - No sync level is supported. noneConfirm - None and Confirm level supported. noneConfirmSyncPoint - None, Confirm and Sync Point is supported. 
.1.3.6.1.2.1.34.3.1.2.6.1.27,APPC-MIB::appcModeOperCryptoLastStart,INTEGER,read-only,,current,notSupported(1):selective(3),Specifies whether session-level cryptography is supported. This value represents the initial value proposed by the local LU the last time this capability was negotiated, i.e., when the first session was bound between the local LU and its partner. notSupported - Specifies session-level cryptography is not to be used. mandatory - Specifies session-level cryptography must be used. selective - Specifies session-level cryptography is required just on selected requests flowing on the sessions.
.1.3.6.1.2.1.34.3.1.2.6.1.28,APPC-MIB::appcModeOperCNOSNeg,INTEGER,read-only,,current,no(1):yes(2),Specifies whether CNOS negotiation is in process. CNOS negotiation is used to set or change the various session limits for a mode.
.1.3.6.1.2.1.34.3.1.2.6.1.29,APPC-MIB::appcModeOperActCwin,Gauge32,read-only,,current,,Specifies the number of active contention winner sessions.
.1.3.6.1.2.1.34.3.1.2.6.1.30,APPC-MIB::appcModeOperActClos,Gauge32,read-only,,current,,Specifies the number of active contention loser sessions.
.1.3.6.1.2.1.34.3.1.2.6.1.31,APPC-MIB::appcModeOperPndCwin,Gauge32,read-only,,current,,Specifies the number of contention winner sessions that are pending activation.
.1.3.6.1.2.1.34.3.1.2.6.1.32,APPC-MIB::appcModeOperPndClos,Gauge32,read-only,,current,,Specifies the number of contention loser sessions that are pending activation.
.1.3.6.1.2.1.34.3.1.2.6.1.33,APPC-MIB::appcModeOperPtmCwin,Gauge32,read-only,,current,,Specifies the number of contention winner sessions that are pending termination.
.1.3.6.1.2.1.34.3.1.2.6.1.34,APPC-MIB::appcModeOperPtmClos,Gauge32,read-only,,current,,Specifies the number of contention loser sessions that are pending termination.
.1.3.6.1.2.1.34.3.1.2.6.1.35,APPC-MIB::appcModeOperDrainSelf,INTEGER,read-only,,current,no(1):yes(2),Specifies whether the local LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the local LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stopped or BIS protocol). 
.1.3.6.1.2.1.34.3.1.2.6.1.36,APPC-MIB::appcModeOperDrainPart,INTEGER,read-only,,current,no(1):yes(2),Specifies whether the partner LU is draining its conversations for this mode. When a mode session limit is reset (via a CNOS RESET_SESSION_LIMIT request), the partner LU could be set to process all queued conversations before deactivating all of the sessions (using the SNA Bracket Initiation Stop or BIS protocol). 
.1.3.6.1.2.1.34.3.1.3,APPC-MIB::appcTp,,,,,,
.1.3.6.1.2.1.34.3.1.3.1,APPC-MIB::appcTpAdminTable,,not-accessible,,current,,APPC Local TP Table
.1.3.6.1.2.1.34.3.1.3.1.1,APPC-MIB::appcTpAdminEntry,,not-accessible,appcTpAdminLocLuName:appcTpAdminTpName,current,,Entry of APPC Local TP Information Table.
.1.3.6.1.2.1.34.3.1.3.1.1.1,APPC-MIB::appcTpAdminLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU to which this TP definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the TP definition applies to all local LUs, and not just to a single local LU.
.1.3.6.1.2.1.34.3.1.3.1.1.2,APPC-MIB::appcTpAdminTpName,OCTET,not-accessible,,current,,The local transaction program name. This name is sent on an ATTACH remote allocation request. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non-displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes).
.1.3.6.1.2.1.34.3.1.3.1.1.3,APPC-MIB::appcTpAdminFileSpec,OCTET,read-only,,current,,The local file specification of the transaction program. May be a zero-length string if not applicable.
.1.3.6.1.2.1.34.3.1.3.1.1.4,APPC-MIB::appcTpAdminStartParm,OCTET,read-only,,current,,A parameter string passed to the transaction program when it is started. May be a zero-length string if not supported. 
.1.3.6.1.2.1.34.3.1.3.1.1.5,APPC-MIB::appcTpAdminTpOperation,INTEGER,read-only,,current,other(1):queuedOperatorStarted(2):queuedOperatorPreloaded(3):queuedAmStarted(4):nonqueuedAmStarted(5),Specifies how the program will be started. other - Specifies that the program operation is none of the methods specified. It may be a product-specific method. queuedOperatorStarted - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, APPC will issue a message to the operator to start the specified program. Subsequent attaches that arrive while the program is active will be queued. queuedOperatorPreloaded - Specifies that one version of the program will be run at a time. If an incoming attach arrives and the program has not been started yet, the Attach will be rejected. The APPC attach manager determines that a TP has started upon reception of an APPC RECEIVE_ALLOCATE verb, or a CPI-C Accept_Conversation (CMACCP) or Specify_Local_TP_Name (CMSLTP) call. No message is sent to the operator. Subsequent attaches that arrive while the program is active are queued. queuedAmStarted - Specifies that one version of the program will be run at a time and will be started by the APPC attach manager. Subsequent attaches that arrive while the program is active will be queued. nonqueuedAmStarted - Specifies that multiple copies of the program will be run at a time and will be started by the APPC attach manager.
.1.3.6.1.2.1.34.3.1.3.1.1.6,APPC-MIB::appcTpAdminInAttachTimeout,Integer32,read-only,,current,,This object specifies the number of seconds incoming attaches will be queued waiting for an APPC program to issue a RECEIVE_ALLOCATE verb or for a CPI-C program to issue an Accept_Conversation (CMACCP) call. This parameter is meaningful only when appcTpAdminTpOperation has one of the following values: queuedOperatorStarted queuedOperatorPreloaded queuedAmStarted A value of zero indicates that there is no timeout.
.1.3.6.1.2.1.34.3.1.3.1.1.7,APPC-MIB::appcTpAdminRcvAllocTimeout,Integer32,read-only,,current,,This object specifies the number of seconds an APPC program's RECEIVE_ALLOCATE verb or a CPI-C program's Accept_Conversation (CMACCP) call will wait for an incoming attach to arrive. A value of zero indicates that there is no timeout.
.1.3.6.1.2.1.34.3.1.3.1.1.8,APPC-MIB::appcTpAdminSyncLvl,INTEGER,read-only,,current,none(1):confirm(2):noneAndConfirm(3):syncpoint(4):noneAndSyncpoint(5):confirmAndSyncpoint(6):all(7),Indicates the synchronization level or levels that the transaction program supports. The levels are defined as follows: none - allocation requests indicating a synchronization level of none are allowed to start the program. confirm - allocation requests indicating a synchronization level of confirm are allowed to start the program. syncpoint - allocation requests indicating a synchronization level of sync point are allowed to start the program.
.1.3.6.1.2.1.34.3.1.3.1.1.9,APPC-MIB::appcTpAdminInstLmt,Integer32,read-only,,current,,The maximum number of concurrent instances of this transaction program that will be supported for a local LU. A value of zero indicates that there is no limit.
.1.3.6.1.2.1.34.3.1.3.1.1.10,APPC-MIB::appcTpAdminStatus,INTEGER,read-only,,current,enabled(1):tempDisabled(2):permDisabled(3),Indicates the status of the TP relative to starting execution when the local LU receives an allocation (ATTACH) request naming this program. enabled - the local LU can start the program. tempDisabled - the local LU cannot start the program. The local LU rejects the request with an indication that the TP is not available but retry is possible. permDisabled - the local LU cannot start the program. The local LU rejects the request with an indication that the TP is not available and retry is not possible.
.1.3.6.1.2.1.34.3.1.3.1.1.11,APPC-MIB::appcTpAdminLongRun,INTEGER,read-only,,current,no(1):yes(2),Indicates whether this is a long-running transaction program (i.e., one that stays around even after the conversation goes away).
.1.3.6.1.2.1.34.3.1.3.1.1.12,APPC-MIB::appcTpAdminConvType,INTEGER,read-only,,current,basic(1):mapped(2):basicOrMapped(3),Specifies the conversation type (basic or mapped) that will be used by the TP. This value is verified upon receipt of an incoming attach. The acceptable values are: basic - Indicates that this transaction program supports basic conversations. mapped - Indicates that this transaction program supports mapped conversations. basicOrMapped - Indicates that this transaction program supports both basic and mapped conversations.
.1.3.6.1.2.1.34.3.1.3.1.1.13,APPC-MIB::appcTpAdminConvDuplex,INTEGER,read-only,,current,half(1):full(2):halfOrFull(3),Specifies the conversation duplex type (half or full) that will be used by the TP. This value is verified upon receipt of an incoming attach. The acceptable values are: half - Indicates that this transaction program supports half duplex conversations. full - Indicates that this transaction program supports full duplex conversations. halfOrFull - Indicates that this transaction program supports either half or full duplex conversations.
.1.3.6.1.2.1.34.3.1.3.1.1.14,APPC-MIB::appcTpAdminConvSecReq,INTEGER,read-only,,current,no(1):yes(2),Indicates whether conversation-level security information is required on incoming attaches designating this TP name. Conversation-level security verification is always performed on those requests that include security information. yes - Indicates that conversation-level security information is required. ATTACHs designating the transaction program must carry a user_id and either a password or an already verified indicator. no - Indicates that no security information is required. ATTACHs designating the transaction program can omit or include security information.
.1.3.6.1.2.1.34.3.1.3.1.1.15,APPC-MIB::appcTpAdminVerPip,INTEGER,read-only,,current,no(1):yes(2),Specifies whether the number of PIP (Program Initialization Parameters) subfields should be verified against the number expected (appcTpAdminPipSubNum).
.1.3.6.1.2.1.34.3.1.3.1.1.16,APPC-MIB::appcTpAdminPipSubNum,Integer32,read-only,,current,,Specifies the number of PIP subfields expected by the TP.
.1.3.6.1.2.1.34.3.1.4,APPC-MIB::appcSession,,,,,,
.1.3.6.1.2.1.34.3.1.4.1,APPC-MIB::appcActSessTable,,not-accessible,,current,,Table of active APPC sessions. Two entries are present in the table when both session partners are local.
.1.3.6.1.2.1.34.3.1.4.1.1,APPC-MIB::appcActSessEntry,,not-accessible,appcActSessLocLuName:appcActSessParLuName:appcActSessIndex,current,,Entry of APPC Session Information Table. Indexed by LU pair and integer-valued session index.
.1.3.6.1.2.1.34.3.1.4.1.1.1,APPC-MIB::appcActSessLocLuName,OCTET,not-accessible,,current,,Specifies the name of the local LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).
.1.3.6.1.2.1.34.3.1.4.1.1.2,APPC-MIB::appcActSessParLuName,OCTET,not-accessible,,current,,Specifies the name of the partner LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).
.1.3.6.1.2.1.34.3.1.4.1.1.3,APPC-MIB::appcActSessIndex,Integer32,not-accessible,,current,,This value identifies the index of the session, which is unique for this LU pair. It is recommended that an Agent not reuse the index of a deactivated session for a significant period of time (e.g., one week).
.1.3.6.1.2.1.34.3.1.4.1.1.4,APPC-MIB::appcActSessPcidCpName,OCTET,read-only,,current,,The network-qualified CP name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.4.1.1.5,APPC-MIB::appcActSessPcid,OCTET,read-only,,current,,The procedure correlation identifier (PCID) of a session. It is an 8-octet value assigned by the control point providing session services for the primary LU. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.4.1.1.6,APPC-MIB::appcActSessPluIndicator,INTEGER,read-only,,current,localLuIsPlu(1):partnerLuIsPlu(2),Indicates which LU is the PLU for this session. For independent LUs, the PLU (primary LU) is the one that initiated the session (sent BIND), while the SLU (secondary LU) is the one that accepted the session initiation (received BIND). The 'local' LU is the one identified by appcLluOperName. The 'partner' LU is the one identified by appcLuPairOperParLuName.
.1.3.6.1.2.1.34.3.1.4.1.1.7,APPC-MIB::appcActSessModeName,OCTET,read-only,,current,,The mode name used for this session.
.1.3.6.1.2.1.34.3.1.4.1.1.8,APPC-MIB::appcActSessCosName,OCTET,read-only,,current,,The Class of Service (COS) name used for this session. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.4.1.1.9,APPC-MIB::appcActSessTransPriority,INTEGER,read-only,,current,unknown(1):low(2):medium(3):high(4):network(5),The transmission priority of this session. 1 = unknown priority 2 = low priority 3 = medium priority 4 = high priority 5 = network priority 
.1.3.6.1.2.1.34.3.1.4.1.1.10,APPC-MIB::appcActSessEnhanceSecSup,INTEGER,read-only,,current,none(1):level1(2):level2(3),Enhanced security supported. Indicates the level of enhanced security support: 1 = none 2 = level 1 3 = level 2 
.1.3.6.1.2.1.34.3.1.4.1.1.11,APPC-MIB::appcActSessSendPacingType,INTEGER,read-only,,current,none(1):fixed(2):adaptive(3),The type of pacing being used for sending data.
.1.3.6.1.2.1.34.3.1.4.1.1.12,APPC-MIB::appcActSessSendRpc,Gauge32,read-only,,current,,The send residual pace count. This represents the number of MUs that can still be sent in the current session window.
.1.3.6.1.2.1.34.3.1.4.1.1.13,APPC-MIB::appcActSessSendNxWndwSize,Gauge32,read-only,,current,,The size of the next window which will be used to send data.
.1.3.6.1.2.1.34.3.1.4.1.1.14,APPC-MIB::appcActSessRecvPacingType,INTEGER,read-only,,current,none(1):fixed(2):adaptive(3),The type of pacing being used for receiving data.
.1.3.6.1.2.1.34.3.1.4.1.1.15,APPC-MIB::appcActSessRecvRpc,Gauge32,read-only,,current,,The receive residual pace count. This represents the number of MUs that can still be received in the current session window.
.1.3.6.1.2.1.34.3.1.4.1.1.16,APPC-MIB::appcActSessRecvNxWndwSize,Gauge32,read-only,,current,,The size of the next window which will be used to receive data.
.1.3.6.1.2.1.34.3.1.4.1.1.17,APPC-MIB::appcActSessRscv,OCTET,read-only,,current,,The route selection control vector (RSCV CV2B) used for this session. It is present for APPN-level implementations. LEN-level implementations will return a null string. The internal format of this vector is described in SNA Formats. This object contains an uninterpreted copy of the control vector (including the length and key fields).
.1.3.6.1.2.1.34.3.1.4.1.1.18,APPC-MIB::appcActSessInUse,INTEGER,read-only,,current,no(1):yes(2),Specifies whether the session is currently in use (i.e., in bracket with a conversation).
.1.3.6.1.2.1.34.3.1.4.1.1.19,APPC-MIB::appcActSessMaxSndRuSize,INTEGER,read-only,,current,,The maximum RU size used on this session for sending RUs.
.1.3.6.1.2.1.34.3.1.4.1.1.20,APPC-MIB::appcActSessMaxRcvRuSize,INTEGER,read-only,,current,,The maximum RU size used on this session for receiving RUs.
.1.3.6.1.2.1.34.3.1.4.1.1.21,APPC-MIB::appcActSessSndPacingSize,INTEGER,read-only,,current,,The size of the send pacing window on this session.
.1.3.6.1.2.1.34.3.1.4.1.1.22,APPC-MIB::appcActSessRcvPacingSize,INTEGER,read-only,,current,,The size of the receive pacing window on this session.
.1.3.6.1.2.1.34.3.1.4.1.1.23,APPC-MIB::appcActSessOperState,INTEGER,read-write,,current,unbound(1):pendingBind(2):bound(3):pendingUnbind(4),The value indicates the current operational state of the session. 'unbound (1)' - session has been unbound; in this state it will be removed from the session table by the Agent. 'pendingBind (2)' - this state has different meanings for dependent and independent LUs; for dependent LU - waiting for BIND from the host, for independent LU - waiting for BIND response. When a session enters this state, the corresponding entry in the session table is created by the Agent. 'bound (3)' - session has been successfully bound. 'pendingUnbind (4)' - session enters this state when an UNBIND is sent and before the rsp(UNBIND) is received. Session deactivation: If a session is in the operational state 'bound (3)' then setting the value of this object to 'unbound (1)' will initiate the session shutdown. If a session is in the operational state 'pendingBind (2)' then setting the value of this object to 'unbound (1)' will initiate the session shutdown. If a session is in the operational state 'pendingUnbind (4)' for an abnormally long period of time (e.g., three minutes) then setting the value of this object to 'unbound (1)' will change the session operational state to 'unbound (1)'. 
.1.3.6.1.2.1.34.3.1.4.1.1.24,APPC-MIB::appcActSessUpTime,TimeTicks,read-only,,current,,The length of time the session has been active, measured in hundredths of a second.
.1.3.6.1.2.1.34.3.1.4.1.1.25,APPC-MIB::appcActSessRtpNceId,OCTET,read-only,,current,,The local HPR Network Connection Endpoint of the session.
.1.3.6.1.2.1.34.3.1.4.1.1.26,APPC-MIB::appcActSessRtpTcid,OCTET,read-only,,current,,The local RTP connection TCID of the session.
.1.3.6.1.2.1.34.3.1.4.1.1.27,APPC-MIB::appcActSessLinkIndex,OBJECT,read-only,,current,,This value identifies the link over which the session passes. This value points to the row in the table containing information on the link instance. (e.g., the sdlcLSAdminTable of the SNA DLC MIB module). This object may be NULL if the link is not specified or if a link is not applicable (as for APPN-level nodes).
.1.3.6.1.2.1.34.3.1.4.2,APPC-MIB::appcSessStatsTable,,not-accessible,,current,,This table contains dynamic statistical information relating to active APPC sessions. The entries in this table cannot be created by a Management Station. Two entries are present in the table when both session partners are local. This table is populated only when the value of appcCntrlOperStat is 'active'.
.1.3.6.1.2.1.34.3.1.4.2.1,APPC-MIB::appcSessStatsEntry,,not-accessible,appcSessStatsLocLuName:appcSessStatsParLuName:appcSessStatsSessIndex,current,,Contains statistics information for an APPC session. Each entry is created by the Agent. Objects in this table have read-only access. Each session from appcActSessTable has one entry in this table.
.1.3.6.1.2.1.34.3.1.4.2.1.1,APPC-MIB::appcSessStatsLocLuName,OCTET,not-accessible,,current,,Specifies the name of the local LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).
.1.3.6.1.2.1.34.3.1.4.2.1.2,APPC-MIB::appcSessStatsParLuName,OCTET,not-accessible,,current,,Specifies the name of the partner LU for the session. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).
.1.3.6.1.2.1.34.3.1.4.2.1.3,APPC-MIB::appcSessStatsSessIndex,Integer32,not-accessible,,current,,This value identifies the index of the session, which is unique for this LU pair. It is recommended that an Agent not reuse the index of a deactivated session for a significant period of time (e.g., one week). If this object has the same value as appcActSessIndex for the same LU pair, then the two entries being indexed apply to the same resource (specifically, to the same session).
.1.3.6.1.2.1.34.3.1.4.2.1.4,APPC-MIB::appcSessStatsSentFmdBytes,Counter32,read-only,,current,,The number of function management data (FMD) bytes sent by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.5,APPC-MIB::appcSessStatsSentNonFmdBytes,Counter32,read-only,,current,,The number of non-function management data (non-FMD) bytes sent by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.6,APPC-MIB::appcSessStatsRcvdFmdBytes,Counter32,read-only,,current,,The number of function management data (FMD) bytes received by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.7,APPC-MIB::appcSessStatsRcvdNonFmdBytes,Counter32,read-only,,current,,The number of non-function management data (non-FMD) bytes received by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.8,APPC-MIB::appcSessStatsSentFmdRus,Counter32,read-only,,current,,The number of function management data (FMD) RUs sent by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.9,APPC-MIB::appcSessStatsSentNonFmdRus,Counter32,read-only,,current,,The number of non-function management data (non-FMD) RUs sent by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.10,APPC-MIB::appcSessStatsRcvdFmdRus,Counter32,read-only,,current,,The number of function management data (FMD) RUs received by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.11,APPC-MIB::appcSessStatsRcvdNonFmdRus,Counter32,read-only,,current,,The number of non-function management data (non-FMD) RUs received by the local LU.
.1.3.6.1.2.1.34.3.1.4.2.1.12,APPC-MIB::appcSessStatsCtrUpTime,TimeTicks,read-only,,current,,The length of time the counters for this session have been active, measured in hundredths of a second.
.1.3.6.1.2.1.34.3.1.4.3,APPC-MIB::appcHistSessTable,,not-accessible,,current,,Table of historical information about APPC sessions that terminated abnormally. Two entries may be present in the table when both session partners are local. It is an implementation choice how long to retain information about a given session.
.1.3.6.1.2.1.34.3.1.4.3.1,APPC-MIB::appcHistSessEntry,,not-accessible,appcHistSessIndex,current,,Entry of APPC Session History Table. This table is indexed by an integer which is continuously incremented until it eventually wraps.
.1.3.6.1.2.1.34.3.1.4.3.1.1,APPC-MIB::appcHistSessIndex,INTEGER,not-accessible,,current,,Table index. The value of the index begins at zero and is incremented up to a maximum value of 2**31-1 (2,147,483,647) before wrapping.
.1.3.6.1.2.1.34.3.1.4.3.1.2,APPC-MIB::appcHistSessTime,OCTET,read-only,,current,,The time at which the session was either terminated or failed to be established.
.1.3.6.1.2.1.34.3.1.4.3.1.3,APPC-MIB::appcHistSessType,INTEGER,read-only,,current,recvNegBindRsp(1):sendNegBindRsp(2):sessActRejected(3):unbindSent(4):unbindReceived(5),Indicates the type of event that caused the entry to be made: recvNegBindRsp - Received a negative bind response from the partner LU. sendNegBindRsp - Sent a negative bind response to the partner LU. sessActRejected - Session activation rejected by the partner LU. unbindSent - Unbind sent to the partner LU. unbindReceived - Unbind received from the partner LU. These event types correspond to the five SNA/MS Alerts LU62001 through LU62005, documented in the SNA Management Services Reference.
.1.3.6.1.2.1.34.3.1.4.3.1.4,APPC-MIB::appcHistSessLocLuName,OCTET,read-only,,current,,The network-qualified local LU name. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.4.3.1.5,APPC-MIB::appcHistSessParLuName,OCTET,read-only,,current,,The network-qualified partner LU name. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.4.3.1.6,APPC-MIB::appcHistSessModeName,OCTET,read-only,,current,,The mode name of the session.
.1.3.6.1.2.1.34.3.1.4.3.1.7,APPC-MIB::appcHistSessUnbindType,OCTET,read-only,,current,,The type of unbind which terminated the session. This value is consists of one (1) octet; and its meaning is defined in SNA Formats.
.1.3.6.1.2.1.34.3.1.4.3.1.8,APPC-MIB::appcHistSessSenseData,OCTET,read-only,,current,,The sense data associated with the termination of the session, taken from the negative BIND response or UNBIND request.
.1.3.6.1.2.1.34.3.1.4.3.1.9,APPC-MIB::appcHistSessComponentId,OCTET,read-only,,current,,The implementation-specific name of the component which detected the problem.
.1.3.6.1.2.1.34.3.1.4.3.1.10,APPC-MIB::appcHistSessDetectModule,OCTET,read-only,,current,,The implementation-specific name of the module which detected the problem.
.1.3.6.1.2.1.34.3.1.4.4,APPC-MIB::appcSessRtpTable,,not-accessible,,current,,A table indicating how many APPC sessions terminating in this node are transported by each RTP connection.
.1.3.6.1.2.1.34.3.1.4.4.1,APPC-MIB::appcSessRtpEntry,,not-accessible,appcSessRtpNceId:appcSessRtpTcid,current,,Entry of APPC session RTP table.
.1.3.6.1.2.1.34.3.1.4.4.1.1,APPC-MIB::appcSessRtpNceId,OCTET,not-accessible,,current,,The local Network Connection Endpoint of the RTP connection.
.1.3.6.1.2.1.34.3.1.4.4.1.2,APPC-MIB::appcSessRtpTcid,OCTET,not-accessible,,current,,The local TCID of the RTP connection.
.1.3.6.1.2.1.34.3.1.4.4.1.3,APPC-MIB::appcSessRtpSessions,Gauge32,read-only,,current,,The number of APPC sessions terminating in this node that are using this RTP connection.
.1.3.6.1.2.1.34.3.1.5,APPC-MIB::appcConversation,,,,,,
.1.3.6.1.2.1.34.3.1.5.1,APPC-MIB::appcActiveConvTable,,not-accessible,,current,,Table of information about active APPC Conversations. In this context 'active' means that a conversation is currently associated with a particular session. Two entries are present in the table when both LUs for the session are local.
.1.3.6.1.2.1.34.3.1.5.1.1,APPC-MIB::appcActiveConvEntry,,not-accessible,appcActiveConvLocLuName:appcActiveConvParLuName:appcActiveConvSessIndex,current,,Entry representing one active APPC Conversation.
.1.3.6.1.2.1.34.3.1.5.1.1.1,APPC-MIB::appcActiveConvLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLluOperName, then the two entries being indexed apply to the same resource (specifically, to the same local LU).
.1.3.6.1.2.1.34.3.1.5.1.1.2,APPC-MIB::appcActiveConvParLuName,OCTET,not-accessible,,current,,The SNA name of the partner LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. If this object has the same value as appcLuPairOperParLuName, then the two entries being indexed apply to the same resource (specifically, to the same partner LU).
.1.3.6.1.2.1.34.3.1.5.1.1.3,APPC-MIB::appcActiveConvSessIndex,Integer32,not-accessible,,current,,Index of entry in appcActSessTable that is associated with this conversation. If this object has the same value as appcActSessIndex for the same LU pair, then the two entries being indexed apply to the same resource (specifically, to the same session).
.1.3.6.1.2.1.34.3.1.5.1.1.4,APPC-MIB::appcActiveConvId,OCTET,read-only,,current,,The 4-byte ID of the conversation.
.1.3.6.1.2.1.34.3.1.5.1.1.5,APPC-MIB::appcActiveConvState,INTEGER,read-only,,current,reset(1):send(2):receive(3):confirm(4):confirmSend(5):confirmDealloc(6):pendingDeallocate(7):pendingPost(8):sendReceive(9):sendOnly(10):receiveOnly(11):deferReceive(12):deferDeallocate(13):syncpoint(14):syncpointSend(15):syncpointDeallocate(16):backoutRequired(17),Indicates the state of the conversation at the instant when the information was retrieved. The values are: reset The conversation is reset (i.e., deallocated). send The conversation can send data. This value also is returned if the conversation is in Send-Pending state. receive The conversation can receive data. confirm The conversation has received a confirm indicator. It can issue an [MC_]CONFIRMED or [MC_]SEND_ERROR verb to change state. It will continue in Receive state if an [MC_]CONFIRMED verb is issued. confirmSend The conversation is in Confirm state and changes to Send state when an [MC_]CONFIRMED verb is issued. confirmDealloc The conversation is in Confirm state and becomes inactive when an [MC_]CONFIRMED verb is issued. pendingDeallocate The conversation is in Pending-Deallocate state while it waits for (MC_)DEALLOCATE TYPE (sync_level) to complete. pendingPost The conversation is in Pending-Post state while it waits for the [MC_]RECEIVE_AND_POST verb to complete its receive function. sendReceive The full-duplex conversation can send or receive data. sendOnly The full-duplex conversation can send data, but it does not have permission to receive data, because the partner TP has already deallocated its side of the conversation. receiveOnly The full-duplex conversation can receive data, but it does not have permission to send data, because it has already deallocated its side of the conversation. deferReceive Waiting for a successful SYNCPT verb operation to go into the receive state. deferDeallocate Waiting for a successful SYNCPT verb operation to go into the reset state. syncpoint Need to response to a SYNCPT verb issued. After successful operation, the next state will be receive. syncpointSend Need to response to a SYNCPT verb issued. After successful operation, the next state will be send. syncpointDeallocate Need to response to a SYNCPT verb issued. After successful operation, the next state will be reset. backoutRequired TP must execute a BACKOUT verb to backout the transaction.
.1.3.6.1.2.1.34.3.1.5.1.1.6,APPC-MIB::appcActiveConvType,INTEGER,read-only,,current,basic(1):mapped(2),Indicates the type of conversation. The values are: basic Indicates that this conversation supports basic verbs. mapped Indicates that this conversation supports mapped verbs.
.1.3.6.1.2.1.34.3.1.5.1.1.7,APPC-MIB::appcActiveConvCorrelator,OCTET,read-only,,current,,This is an 8-byte identifier that the source LU assigns to the conversation; the source LU is the one that sent the allocation request. The conversation correlator is included on the allocation request. The conversation correlator uniquely identifies a conversation, from among all conversations, between the local and partner LUs. It may be used, for example, during problem determination associated with a conversation. A length of 0 indicates that no conversation correlator is defined.
.1.3.6.1.2.1.34.3.1.5.1.1.8,APPC-MIB::appcActiveConvSyncLvl,INTEGER,read-only,,current,none(1):confirm(2):syncpt(3),Indicates the highest sync level support for the conversation. The values are: none Indicates that no sync-level processing can be performed on this conversation. The transaction program does not issue verbs or recognize any returned parameters relating to any sync-level function. confirm Indicates that confirmation processing can be performed on this conversation. The transaction program can issue verbs and recognize returned parameters relating to confirmation. syncpt Indicates that syncpt and confirmation processing can be performed on this conversation. The transaction program can issue verbs and recognize returned parameters relating to syncpt and confirmation.
.1.3.6.1.2.1.34.3.1.5.1.1.9,APPC-MIB::appcActiveConvSource,INTEGER,read-only,,current,localLu(1):partnerLu(2),Indicates whether the local or partner LU is the source of the conversation, that is, which LU started the conversation by sending the allocation request. localLu The local LU is the source of the conversation, and the partner LU is the target of the conversation. partnerLu The partner LU is the source of the conversation, and the local LU is the target of the conversation.
.1.3.6.1.2.1.34.3.1.5.1.1.10,APPC-MIB::appcActiveConvDuplex,INTEGER,read-only,,current,half(1):full(2),Indicates the conversation duplex style in effect for the conversation. half Indicates that information can be transferred in both directions, but only in one direction at a time. full Indicates that information can be transferred in both directions at the same time.
.1.3.6.1.2.1.34.3.1.5.1.1.11,APPC-MIB::appcActiveConvUpTime,TimeTicks,read-only,,current,,The length of time since the conversation started, measured in hundredths of a second.
.1.3.6.1.2.1.34.3.1.5.1.1.12,APPC-MIB::appcActiveConvSendBytes,Counter32,read-only,,current,,Indicates the number of bytes that was sent on the conversation. The count includes all SNA RU bytes sent, including those in the FMH-5 (Attach), FMH-7 (Error Description), SIGNAL, LUSTAT, and SNA responses; it does not include SNA TH and RH bytes.
.1.3.6.1.2.1.34.3.1.5.1.1.13,APPC-MIB::appcActiveConvRcvBytes,Counter32,read-only,,current,,Indicates the number of bytes that was received on the conversation. The count includes all SNA RU bytes sent, including those in the FMH-5 (Attach), FMH-7 (Error Description), SIGNAL, LUSTAT, and SNA responses; it does not include SNA TH and RH bytes.
.1.3.6.1.2.1.34.3.1.5.1.1.14,APPC-MIB::appcActiveConvUserid,OCTET,read-only,,current,,The user ID that the initiating program provided in the incoming attach.
.1.3.6.1.2.1.34.3.1.5.1.1.15,APPC-MIB::appcActiveConvPcidNauName,OCTET,read-only,,current,,The network-qualified NAU name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.5.1.1.16,APPC-MIB::appcActiveConvPcid,OCTET,read-only,,current,,The procedure correlation identifier (PCID) of the session. It is an 8-octet value assigned by the control point providing session services for the primary LU. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.5.1.1.17,APPC-MIB::appcActiveConvModeName,OCTET,read-only,,current,,The Mode Name used for this conversation. This is a 1-8 character name.
.1.3.6.1.2.1.34.3.1.5.1.1.18,APPC-MIB::appcActiveConvLuwIdName,OCTET,read-only,,current,,The SNA name of the LU that initiated the logical unit of work that is associated with this active TP. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the LU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.5.1.1.19,APPC-MIB::appcActiveConvLuwIdInstance,OCTET,read-only,,current,,The instance identifier for the logical unit of work.
.1.3.6.1.2.1.34.3.1.5.1.1.20,APPC-MIB::appcActiveConvLuwIdSequence,OCTET,read-only,,current,,The sequence identifier for the logical unit of work.
.1.3.6.1.2.1.34.3.1.5.1.1.21,APPC-MIB::appcActiveConvTpName,OCTET,read-only,,current,,The transaction program name which started this conversation. This name could either be from a FMH5 ATTACH for a remotely started conversation, otherwise it could the name of the local TP if available. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non- displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes). This name is NULL if the conversation is started locally (i.e., not with a FMH5 ATTACH).
.1.3.6.1.2.1.34.3.1.5.2,APPC-MIB::appcHistConvTable,,not-accessible,,current,,Table of historical information about APPC Conversations that ended in error. Possible categories of error conditions that could be saved in this table are: - allocation errors, - deallocate abend, - program errors, and - service errors.
.1.3.6.1.2.1.34.3.1.5.2.1,APPC-MIB::appcHistConvEntry,,not-accessible,appcHistConvIndex,current,,Entry representing one APPC Conversation.
.1.3.6.1.2.1.34.3.1.5.2.1.1,APPC-MIB::appcHistConvIndex,Integer32,not-accessible,,current,,Index for entry in Conversation table. This value identifies the unique index of the conversation. It is recommended that an Agent not reuse the index of a deactivated conversation for a significant period of time (e.g. one week).
.1.3.6.1.2.1.34.3.1.5.2.1.2,APPC-MIB::appcHistConvEndTime,OCTET,read-only,,current,,The time at which the conversation ended.
.1.3.6.1.2.1.34.3.1.5.2.1.3,APPC-MIB::appcHistConvLocLuName,OCTET,read-only,,current,,The name of the local LU for this conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.5.2.1.4,APPC-MIB::appcHistConvParLuName,OCTET,read-only,,current,,The SNA name of the partner LU for the conversation. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.5.2.1.5,APPC-MIB::appcHistConvTpName,OCTET,read-only,,current,,The transaction program name which started this conversation. This name could either be from a FMH5 ATTACH for a remotely started conversation, otherwise it could the name of the local TP if available. When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non- displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes). This name is NULL if the conversation is started locally (i.e., not with a FMH5 ATTACH).
.1.3.6.1.2.1.34.3.1.5.2.1.6,APPC-MIB::appcHistConvPcidNauName,OCTET,read-only,,current,,The network-qualified NAU name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. This field is from 3 to 17 characters in length, including a period (.) which separates the NetId from the NAU name. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.5.2.1.7,APPC-MIB::appcHistConvPcid,OCTET,read-only,,current,,The procedure correlation identifier (PCID) of the session. It is an 8-octet value assigned by the control point providing session services for the primary LU. A null string indicates that the value is unknown.
.1.3.6.1.2.1.34.3.1.5.2.1.8,APPC-MIB::appcHistConvSenseData,OCTET,read-only,,current,,The sense data associated with the action that ended this conversation, e.g., FMH-7 or UNBIND.
.1.3.6.1.2.1.34.3.1.5.2.1.9,APPC-MIB::appcHistConvLogData,OCTET,read-only,,current,,The first 32 bytes of the data portion of the Log Data GDS Variable that is associated with the last FMH-7 that occurred on this conversation. If there was no Log Data GDS Variable associated with the FMH-7, this object is null. This object reflects only the data portion of the Log Data GDS Variable (i.e. not the LL or GDS Id).
.1.3.6.1.2.1.34.3.1.5.2.1.10,APPC-MIB::appcHistConvEndedBy,INTEGER,read-only,,current,localLu(1):partnerLu(2),Indicates which LU ended the conversation.
.1.3.6.1.2.1.34.3.1.6,APPC-MIB::appcCPIC,,,,,,
.1.3.6.1.2.1.34.3.1.6.1,APPC-MIB::appcCpicAdminTable,,not-accessible,,current,,APPC CPI-C side information table.
.1.3.6.1.2.1.34.3.1.6.1.1,APPC-MIB::appcCpicAdminEntry,,not-accessible,appcCpicAdminLocLuName:appcCpicAdminSymbDestName,current,,Entry of APPC CPI-C side information Table.
.1.3.6.1.2.1.34.3.1.6.1.1.1,APPC-MIB::appcCpicAdminLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU to which this CPI-C side information definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the definition applies to all local LUs, and not just to a single local LU.
.1.3.6.1.2.1.34.3.1.6.1.1.2,APPC-MIB::appcCpicAdminSymbDestName,OCTET,not-accessible,,current,,Specifies the symbolic destination name used by CPI-C applications to identify this definition.
.1.3.6.1.2.1.34.3.1.6.1.1.3,APPC-MIB::appcCpicAdminParLuAlias,OCTET,read-only,,current,,A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.
.1.3.6.1.2.1.34.3.1.6.1.1.4,APPC-MIB::appcCpicAdminParLuName,OCTET,read-only,,current,,The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.6.1.1.5,APPC-MIB::appcCpicAdminModeName,OCTET,read-only,,current,,Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters).
.1.3.6.1.2.1.34.3.1.6.1.1.6,APPC-MIB::appcCpicAdminTpNameType,INTEGER,read-only,,current,normal(1):snaServiceTp(2),Specifies whether the TP name in appcCpicAdminTpName identifies a normal TP or an SNA service TP. In this context, a normal TP is one with a name consisting only of displayable characters, while an SNA service TP has a name containing octets that do not map to displayable characters.
.1.3.6.1.2.1.34.3.1.6.1.1.7,APPC-MIB::appcCpicAdminTpName,OCTET,read-only,,current,,Specifies the name of the partner TP to be used when a CPI-C application initiates a conversation specifying this side information entry. Display convention When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non-displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes).
.1.3.6.1.2.1.34.3.1.6.1.1.8,APPC-MIB::appcCpicAdminUserid,OCTET,read-only,,current,,The security userid, if any, associated with the side information definition.
.1.3.6.1.2.1.34.3.1.6.1.1.9,APPC-MIB::appcCpicAdminSecurity,INTEGER,read-only,,current,none(1):same(2):pgm(3):pgmStrong(4):distributed(5):mutual(6),Specifies the security information to be used for allocating the conversation. none - No security information. same - Use the security environment currently associated with this TP. pgm - Use the program-supplied user_id and password. pgmStrong - Use the program-supplied user_id and password. The local LU will insure that the password is not exposed in clear-text form on the physical network. distributed - Use the security environment and a distributed security system to generate the authentication information for this request. If distributed security tokens cannot be generated, then fail the conversation. mutual - Authenticate both the user to the destination system and the destination system to the user.
.1.3.6.1.2.1.34.3.1.6.2,APPC-MIB::appcCpicOperTable,,not-accessible,,current,,APPC CPI-C side information operational table.
.1.3.6.1.2.1.34.3.1.6.2.1,APPC-MIB::appcCpicOperEntry,,not-accessible,appcCpicOperLocLuName:appcCpicOperSymbDestName,current,,Entry of APPC CPI-C side information Table.
.1.3.6.1.2.1.34.3.1.6.2.1.1,APPC-MIB::appcCpicOperLocLuName,OCTET,not-accessible,,current,,The SNA name of the local LU to which this CPI-C side information definition applies. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present. The reserved value '*ALL' indicates that the definition applies to all local LUs, and not just to a single local LU.
.1.3.6.1.2.1.34.3.1.6.2.1.2,APPC-MIB::appcCpicOperSymbDestName,OCTET,not-accessible,,current,,Specifies the symbolic destination name used by CPI-C applications to identify this definition.
.1.3.6.1.2.1.34.3.1.6.2.1.3,APPC-MIB::appcCpicOperParLuAlias,OCTET,read-only,,current,,A local alias for the partner LU. If not known or not applicable, this object contains a zero-length string.
.1.3.6.1.2.1.34.3.1.6.2.1.4,APPC-MIB::appcCpicOperParLuName,OCTET,read-only,,current,,The SNA name of the partner LU. This field is from 1 to 17 characters in length, including a period (.) which separates the NetId from the NAU name if the NetId is present.
.1.3.6.1.2.1.34.3.1.6.2.1.5,APPC-MIB::appcCpicOperModeName,OCTET,read-only,,current,,Specifies the mode name. A mode defines the characteristics for a group of sessions. The mode name can be blank (8 space characters).
.1.3.6.1.2.1.34.3.1.6.2.1.6,APPC-MIB::appcCpicOperTpNameType,INTEGER,read-only,,current,normal(1):snaServiceTp(2),Specifies whether the TP name in appcCpicOperTpName identifies a normal TP or an SNA service TP. In this context, a normal TP is one with a name consisting only of displayable characters, while an SNA service TP has a name containing octets that do not map to displayable characters.
.1.3.6.1.2.1.34.3.1.6.2.1.7,APPC-MIB::appcCpicOperTpName,OCTET,read-only,,current,,Specifies the name of the partner TP to be used when a CPI-C application initiates a conversation specifying this side information entry. Display convention When the TP name consists entirely of displayable EBCDIC code points, it is mapped directly to the equivalent ASCII display string. However, registered TP names always have a non-displayable EBCDIC code point (value less than or equal to x'3F') as the first character, so they cannot be directly mapped to an ASCII display string. These TP names are converted to a display string that is equivalent to a hexadecimal display of the EBCDIC code points. For example, the 2-byte TP name x'06F1' (CNOS) is converted to the 6-byte ASCII display string '06F1' (including the two single quotes).
.1.3.6.1.2.1.34.3.1.6.2.1.8,APPC-MIB::appcCpicOperUserid,OCTET,read-only,,current,,The security userid, if any, associated with the active side information definition.
.1.3.6.1.2.1.34.3.1.6.2.1.9,APPC-MIB::appcCpicOperSecurity,INTEGER,read-only,,current,none(1):same(2):pgm(3):pgmStrong(4):distributed(5):mutual(6),Specifies the security information to be used for allocating the conversation. none - No security information. same - Use the security environment currently associated with this TP. pgm - Use the program-supplied user_id and password. pgmStrong - Use the program-supplied user_id and password. The local LU will insure that the password is not exposed in clear-text form on the physical network. distributed - Use the security environment and a distributed security system to generate the authentication information for this request. If distributed security tokens cannot be generated, then fail the conversation. mutual - Authenticate both the user to the destination system and the destination system to the user.
.1.3.6.1.2.1.34.3.2,APPC-MIB::appcConformance,,,,,,
.1.3.6.1.2.1.34.3.2.1,APPC-MIB::appcCompliances,,,,,,
.1.3.6.1.2.1.34.3.2.1.1,APPC-MIB::appcCompliance,,,,,,The compliance statement for the SNMPv2 entities which implement the APPC MIB.
.1.3.6.1.2.1.34.3.2.2,APPC-MIB::appcGroups,,,,,,
.1.3.6.1.2.1.34.3.2.2.1,APPC-MIB::appcGlobalConfGroup,,,,,,A collection of objects providing the instrumentation of APPC global information and defaults.
.1.3.6.1.2.1.34.3.2.2.2,APPC-MIB::appcLluConfGroup,,,,,,A collection of objects providing the instrumentation of APPC local LU6.2s.
.1.3.6.1.2.1.34.3.2.2.3,APPC-MIB::appcParLuConfGroup,,,,,,A collection of objects providing the instrumentation of APPC partner LUs.
.1.3.6.1.2.1.34.3.2.2.4,APPC-MIB::appcModeConfGroup,,,,,,A collection of objects providing the instrumentation of APPC modes.
.1.3.6.1.2.1.34.3.2.2.5,APPC-MIB::appcTpConfGroup,,,,,,A collection of objects providing the instrumentation of APPC Transaction Programs.
.1.3.6.1.2.1.34.3.2.2.6,APPC-MIB::appcSessionConfGroup,,,,,,A collection of objects providing the instrumentation of APPC LU6.2 sessions.
.1.3.6.1.2.1.34.3.2.2.7,APPC-MIB::appcControlConfGroup,,,,,,A collection of objects providing the instrumentation of APPC control.
.1.3.6.1.2.1.34.3.2.2.8,APPC-MIB::appcCnosConfGroup,,,,,,A collection of objects providing the instrumentation of APPC CNOS processing.
.1.3.6.1.2.1.34.3.2.2.9,APPC-MIB::appcCpicConfGroup,,,,,,A collection of objects providing the instrumentation of APPC CPI-C side information.
.1.3.6.1.2.1.34.3.2.2.10,APPC-MIB::appcConversationConfGroup,,,,,,A collection of objects providing the instrumentation of APPC conversations.
.1.3.6.1.2.1.34.4,APPN-MIB::appnMIB,,,,,,This is the MIB module for objects used to manage network devices with APPN capabilities.
.1.3.6.1.2.1.34.4.0,APPN-TRAP-MIB::appnTrapMIB,,,,,,This MIB module defines notifications to be generated by network devices with APPN capabilities. It presupposes support for the APPN MIB. It also presupposes support for the DLUR MIB for implementations that support the DLUR-related groups.
.1.3.6.1.2.1.34.4.0.1,APPN-TRAP-MIB::appnIsrAccountingDataTrap,,,,,,When it has been enabled, this notification is generated by an APPN node whenever an ISR session passing through the node is taken down, regardless of whether the session went down normally or abnormally. Its purpose is to allow a management application (primarily an accounting application) that is monitoring the ISR counts to receive the final values of these counts, so that the application can properly account for the amounts the counts were incremented since the last time the application polled them. The appnIsInSessUpTime object provides the total amount of time that the session was active. This notification is not a substitute for polling the ISR counts. In particular, the count values reported in this notification cannot be assumed to be the complete totals for the life of the session, since they may have wrapped while the session was up. The session to which the objects in this notification apply is identified by the fully qualified CP name and PCID that make up the table index. An instance of this notification will contain exactly one instance of each of its objects, and these objects will all belong to the same conceptual row of the appnIsInTable. Generation of this notification is controlled by the same object in the APPN MIB, appnIsInGlobeCtrAdminStatus, that controls whether the count objects themselves are being incremented.
.1.3.6.1.2.1.34.4.0.2,APPN-TRAP-MIB::appnLocalTgOperStateChangeTrap,,,,,,When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of local TG operational state changes, and thus to reduce the frequency with which it polls for these changes. This notification is sent whenever there is a change to the appnLocalTgOperational object in a row of the appnLocalTgTable. This notification is only sent for row creation if the row is created with a value of 'true' for appnLocalTgOperational. This notification is only sent for row deletion if the last value of appnLocalTgOperational was 'true'. In this case, the value of appnLocalTgOperational in the notification shall be 'false', since the deletion of a row indicates that the TG is no longer operational. The notification is more than a simple 'poll me now' indication. It carries both a count of local TG topology changes, and the current operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLocalTgTable again. This is the same count as used in the appnLocalCpCpStateChangeTrap. A lost notification could indicate a local TG CP-CP session state change or an operational state change. Generation of this notification is controlled by the appnTrapControl object.
.1.3.6.1.2.1.34.4.0.3,APPN-TRAP-MIB::appnLocalTgCpCpChangeTrap,,,,,,When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of local TG control-point to control-point (CP-CP) session state changes, and thus to reduce the frequency with which it polls for these changes. This notification is sent whenever there is a change to the appnLocalTgCpCpSession object but NOT the appnLocalTgOperational object in a row of the appnLocalTgTable. This notification is never sent for appnLocalTgTable row creation or deletion. The notification is more than a simple 'poll me now' indication. It carries both a count of local TG topology changes, and the current CP-CP session state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLocalTgTable again. This is the same count as used in the appnLocalTgOperStateChangeTrap. A lost notification could indicate a local TG CP-CP session state change or an operational state change. Generation of this notification is controlled by the appnTrapControl object.
.1.3.6.1.2.1.34.4.0.4,APPN-TRAP-MIB::appnPortOperStateChangeTrap,,,,,,When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of port operational state changes, and thus to reduce the frequency with which it polls for these changes. This notification is only sent when a appnPortOperState has transitioned to a value of 'active' or 'inactive'. This notification is sent whenever there is a appnPortOperState object transition to 'inactive' or 'active' state in the appnPortTable. This notification is only sent for row creation if the row is created with a value of 'active' for appnPortOperState. This notification is only sent for row deletion if the last value of appnPortOperState was 'active'. In this case, the value of appnPortOperState in the notification shall be 'inactive', since the deletion of a row indicates that the port is no longer active. The notification is more than a simple 'poll me now' indication. It carries both a count of port table changes, and the operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnPortTable again. Generation of this notification is controlled by the appnTrapControl object.
.1.3.6.1.2.1.34.4.0.5,APPN-TRAP-MIB::appnLsOperStateChangeTrap,,,,,,When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of link station operational state changes, and thus to reduce the frequency with which it polls for these changes. This notification is only sent when a appnLsOperState has transitioned to a value of 'active' or 'inactive'. This notification is sent whenever there is a appnLsOperState object transition to 'inactive' or 'active' state in the appnLsTable. This notification is only sent for row creation if the row is created with a value of 'active' for appnLsOperState. This notification is only sent for row deletion if the last value of appnLsOperState was 'active'. In this case, the value of appnLsOperState in the notification shall be 'inactive', since the deletion of a row indicates that the link station is no longer active. The notification is more than a simple 'poll me now' indication. It carries both a count of link station table changes, and the operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLsTable again. Generation of this notification is controlled by the appnTrapControl object.
.1.3.6.1.2.1.34.4.0.6,APPN-TRAP-MIB::dlurDlusStateChangeTrap,,,,,,When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of DLUR-DLUS session changes, and thus to reduce the frequency with which it polls for these changes. This notification is sent whenever there is a dlurDlusSessnStatus object transition to 'inactive' or 'active' state in the dlurDlusTable. This notification is only sent for row creation if the row is created with a value of 'active' for dlurDlusSessnStatus. This notification is only sent for row deletion if the last value of dlurDlusSessnStatus was 'active'. In this case, the value of dlurDlusSessnStatus in the notification shall be 'inactive', since the deletion of a row indicates that the session is no longer active. The notification is more than a simple 'poll me now' indication. It carries both a count of DLUR-DLUS table changes, and the session status itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire dlurDlusTable again. Generation of this notification is controlled by the appnTrapControl object.
.1.3.6.1.2.1.34.4.1,APPN-MIB::appnObjects,,,,,,
.1.3.6.1.2.1.34.4.1.1,APPN-MIB::appnNode,,,,,,
.1.3.6.1.2.1.34.4.1.1.1,APPN-MIB::appnGeneralInfoAndCaps,,,,,,
.1.3.6.1.2.1.34.4.1.1.1.1,APPN-MIB::appnNodeCpName,OCTET,read-only,,current,,Administratively assigned network name for this node.
.1.3.6.1.2.1.34.4.1.1.1.2,APPN-MIB::appnNodeMibVersion,OCTET,read-only,,deprecated,,The value of LAST-UPDATED from this module's MODULE-IDENTITY macro. This object gives a Management Station an easy way of determining the level of the MIB supported by an agent. Since this object incorporates the Year 2000-unfriendly 2-digit year specified in SMI for the LAST-UPDATED field, and since it was not found to be particularly useful, it has been deprecated. No replacement object has been defined.
.1.3.6.1.2.1.34.4.1.1.1.3,APPN-MIB::appnNodeId,OCTET,read-only,,current,,This node's Node Identification, which it sends in bytes 2-5 of XID.
.1.3.6.1.2.1.34.4.1.1.1.4,APPN-MIB::appnNodeType,INTEGER,read-only,,current,networkNode(1):endNode(2):t21len(4),Type of APPN node: networkNode(1) - APPN network node endNode(2) - APPN end node t21len(4) - LEN end node Note: A branch network node SHALL return endNode(2) as the value of this object. A management application can distinguish between a branch network node and an actual end node by retrieving the appnNodeBrNn object.
.1.3.6.1.2.1.34.4.1.1.1.5,APPN-MIB::appnNodeUpTime,TimeTicks,read-only,,current,,Amount of time (in hundredths of a second) since the APPN node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.6,APPN-MIB::appnNodeParallelTg,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node supports parallel TGs.
.1.3.6.1.2.1.34.4.1.1.1.7,APPN-MIB::appnNodeAdaptiveBindPacing,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node supports adaptive bind pacing for dependent LUs.
.1.3.6.1.2.1.34.4.1.1.1.8,APPN-MIB::appnNodeHprSupport,INTEGER,read-only,,current,noHprSupport(1):hprBaseOnly(2):rtpTower(3):controlFlowsOverRtpTower(4),Indicates this node's level of support for high-performance routing (HPR): noHprSupport(1) - no HPR support hprBaseOnly(2) - HPR base (option set 1400) supported rtpTower(3) - HPR base and RTP tower (option set 1401) supported controlFlowsOverRtpTower(4) - HPR base, RTP tower, and control flows over RTP (option set 1402) supported This object corresponds to cv4580, byte 9, bits 3-4.
.1.3.6.1.2.1.34.4.1.1.1.9,APPN-MIB::appnNodeMaxSessPerRtpConn,Gauge32,read-only,,current,,This object represents a configuration parameter indicating the maximum number of sessions that the APPN node is to put on any HPR connection. The value is zero if not applicable.
.1.3.6.1.2.1.34.4.1.1.1.10,APPN-MIB::appnNodeHprIntRteSetups,Counter32,read-only,,current,,The total number of HPR route setups received for routes passing through this node since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.11,APPN-MIB::appnNodeHprIntRteRejects,Counter32,read-only,,current,,The number of HPR route setups rejected by this node for routes passing through it since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.12,APPN-MIB::appnNodeHprOrgRteSetups,Counter32,read-only,,current,,The total number of HPR route setups sent for routes originating in this node since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.13,APPN-MIB::appnNodeHprOrgRteRejects,Counter32,read-only,,current,,The number of HPR route setups rejected by other nodes for routes originating in this node since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.14,APPN-MIB::appnNodeHprEndRteSetups,Counter32,read-only,,current,,The total number of HPR route setups received for routes ending in this node since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.15,APPN-MIB::appnNodeHprEndRteRejects,Counter32,read-only,,current,,The number of HPR route setups rejected by this node for routes ending in it since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.16,APPN-MIB::appnNodeCounterDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object the last time the APPN node was reinitialized.
.1.3.6.1.2.1.34.4.1.1.1.17,APPN-MIB::appnNodeLsCounterType,INTEGER,read-only,,current,other(1):noAnr(2):anrForLocalNces(3):allAnr(4),Indicates which ANR traffic, if any, the node includes in the counts returned by the APPN link station counters appnLsInXidBytes, appnLsInMsgBytes, appnLsInXidFrames, appnLsInMsgFrames, appnLsOutXidBytes, appnLsOutMsgBytes, appnLsOutXidFrames, and appnLsOutMsgFrames. These counters are always incremented for ISR traffic. The following values are defined: other(1) - the node does something different from all the options listed below noAnr(2) - the node does not include any ANR traffic in these counts anrForLocalNces(3) - the node includes in these counts ANR traffic for RTP connections that terminate in this node, but not ANR traffic for RTP connections that pass through this node without terminating in it allAnr(4) - the node includes all ANR traffic in these counts.
.1.3.6.1.2.1.34.4.1.1.1.18,APPN-MIB::appnNodeBrNn,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node is currently configured as a branch network node. Note: throughout the remainder of this MIB module, branch network node is treated as a third node type, parallel to network node and end node. This is not how branch network nodes are treated in the base APPN architecture, but it increases clarity to do it here.
.1.3.6.1.2.1.34.4.1.1.2,APPN-MIB::appnNnUniqueInfoAndCaps,,,,,,
.1.3.6.1.2.1.34.4.1.1.2.1,APPN-MIB::appnNodeNnCentralDirectory,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node supports central directory services. This object corresponds to cv4580, byte 8, bit 1.
.1.3.6.1.2.1.34.4.1.1.2.2,APPN-MIB::appnNodeNnTreeCache,INTEGER,read-only,,current,noCache(1):cacheNoIncrUpdate(2):cacheWithIncrUpdate(3),Indicates this node's level of support for caching of route trees. Three levels are specified: noCache(1) - caching of route trees is not supported cacheNoIncrUpdate(2) - caching of route trees is supported, but without incremental updates cacheWithIncrUpdate(3) - caching of route trees with incremental updates is supported
.1.3.6.1.2.1.34.4.1.1.2.3,APPN-MIB::appnNodeNnRouteAddResist,INTEGER,read-only,,current,,Route addition resistance. This administratively assigned value indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing. This object corresponds to cv4580, byte 6.
.1.3.6.1.2.1.34.4.1.1.2.4,APPN-MIB::appnNodeNnIsr,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node supports intermediate session routing. This object corresponds to cv4580, byte 8, bit 2.
.1.3.6.1.2.1.34.4.1.1.2.5,APPN-MIB::appnNodeNnFrsn,Unsigned32,read-only,,current,,The last flow-reduction sequence number (FRSN) sent by this node in a topology update to an adjacent network node.
.1.3.6.1.2.1.34.4.1.1.2.6,APPN-MIB::appnNodeNnPeriBorderSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node has peripheral border node support. This object corresponds to cv4580, byte 9, bit 0.
.1.3.6.1.2.1.34.4.1.1.2.7,APPN-MIB::appnNodeNnInterchangeSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node has interchange node support. This object corresponds to cv4580, byte 9, bit 1.
.1.3.6.1.2.1.34.4.1.1.2.8,APPN-MIB::appnNodeNnExteBorderSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node has extended border node support. This object corresponds to cv4580, byte 9, bit 2.
.1.3.6.1.2.1.34.4.1.1.2.9,APPN-MIB::appnNodeNnSafeStoreFreq,INTEGER,read-write,,current,,The topology safe store frequency. If this number is not zero, then the topology database is saved each time the total number of topology database updates (TDUs) received by this node increases by this number. A value of zero indicates that the topology database is not being saved.
.1.3.6.1.2.1.34.4.1.1.2.10,APPN-MIB::appnNodeNnRsn,Unsigned32,read-only,,current,,Resource sequence number for this node, which it assigns and controls. This object corresponds to the numeric value in cv4580, bytes 2-5.
.1.3.6.1.2.1.34.4.1.1.2.11,APPN-MIB::appnNodeNnCongested,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node is congested. Other network nodes stop routing traffic to this node while this flag is on. This object corresponds to cv4580, byte 7, bit 0.
.1.3.6.1.2.1.34.4.1.1.2.12,APPN-MIB::appnNodeNnIsrDepleted,INTEGER,read-only,,current,true(1):false(2),Indicate whether intermediated session routing resources are depleted. Other network nodes stop routing traffic through this node while this flag is on. This object corresponds to cv4580, byte 7, bit 1.
.1.3.6.1.2.1.34.4.1.1.2.13,APPN-MIB::appnNodeNnQuiescing,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node is quiescing. This object corresponds to cv4580, byte 7, bit 5.
.1.3.6.1.2.1.34.4.1.1.2.14,APPN-MIB::appnNodeNnGateway,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node has gateway services support. This object corresponds to cv4580, byte 8, bit 0.
.1.3.6.1.2.1.34.4.1.1.3,APPN-MIB::appnEnUniqueCaps,,,,,,
.1.3.6.1.2.1.34.4.1.1.3.1,APPN-MIB::appnNodeEnModeCosMap,INTEGER,read-only,,current,true(1):false(2),Indicates whether this end node supports mode name to COS name mapping.
.1.3.6.1.2.1.34.4.1.1.3.2,APPN-MIB::appnNodeEnNnServer,OCTET,read-only,,current,,The fully qualified name of the current NN server for this end node. An NN server is identified using the format specified in the SnaControlPointName textual convention. The value is a zero-length string when there is no active NN server. A branch network node shall also implement this object.
.1.3.6.1.2.1.34.4.1.1.3.3,APPN-MIB::appnNodeEnLuSearch,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node is to be searched for LUs as part of a network broadcast search. A branch network node shall also implement this object.
.1.3.6.1.2.1.34.4.1.1.4,APPN-MIB::appnPortInformation,,,,,,
.1.3.6.1.2.1.34.4.1.1.4.1,APPN-MIB::appnPortTable,,not-accessible,,current,,The Port table describes the configuration and current status of the ports used by APPN. When it is known to the APPN component, an OBJECT IDENTIFIER pointing to additional information related to the port is included. This may, but need not, be a RowPointer to an ifTable entry for a DLC interface immediately 'below' the port.
.1.3.6.1.2.1.34.4.1.1.4.1.1,APPN-MIB::appnPortEntry,,not-accessible,appnPortName,current,,The port name is used as the index to this table.
.1.3.6.1.2.1.34.4.1.1.4.1.1.1,APPN-MIB::appnPortName,OCTET,not-accessible,,current,,Administratively assigned name for this APPN port.
.1.3.6.1.2.1.34.4.1.1.4.1.1.2,APPN-MIB::appnPortCommand,INTEGER,read-write,,current,deactivate(1):activate(2):recycle(3):ready(4),Object by which a Management Station can activate, deactivate, or recycle (i.e., cause to be deactivated and then immediately activated) a port, by setting the value to activate(1), deactivate(2), or recycle(3), respectively. The value ready(4) is returned on GET operations until a SET has been processed; after that the value received on the most recent SET is returned.
.1.3.6.1.2.1.34.4.1.1.4.1.1.3,APPN-MIB::appnPortOperState,INTEGER,read-only,,current,inactive(1):pendactive(2):active(3):pendinact(4),Indicates the current state of this port: inactive(1) - port is inactive pendactive(2) - port is pending active active(3) - port is active pendinact(4) - port is pending inactive
.1.3.6.1.2.1.34.4.1.1.4.1.1.4,APPN-MIB::appnPortDlcType,INTEGER,read-only,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The type of DLC interface, distinguished according to the protocol immediately 'below' this layer.
.1.3.6.1.2.1.34.4.1.1.4.1.1.5,APPN-MIB::appnPortPortType,INTEGER,read-only,,current,leased(1):switched(2):sharedAccessFacilities(3),Identifies the type of line used by this port: leased(1) - leased line switched(2) - switched line sharedAccessFacilities(3) - shared access facility, such as a LAN.
.1.3.6.1.2.1.34.4.1.1.4.1.1.6,APPN-MIB::appnPortSIMRIM,INTEGER,read-only,,current,true(1):false(2),Indicates whether Set Initialization Mode (SIM) and Receive Initialization Mode (RIM) are supported for this port.
.1.3.6.1.2.1.34.4.1.1.4.1.1.7,APPN-MIB::appnPortLsRole,INTEGER,read-only,,current,primary(1):secondary(2):negotiable(3):abm(4),Initial role for link stations activated through this port. The values map to the following settings in the initial XID, where 'ABM' indicates asynchronous balanced mode and 'NRM' indicated normal response mode: primary(1): ABM support = 0 ( = NRM) role = 01 ( = primary) secondary(2): ABM support = 0 ( = NRM) role = 00 ( = secondary) negotiable(3): ABM support = 0 ( = NRM) role = 11 ( = negotiable) abm(4): ABM support = 1 ( = ABM) role = 11 ( = negotiable)
.1.3.6.1.2.1.34.4.1.1.4.1.1.8,APPN-MIB::appnPortNegotLs,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node supports negotiable link stations for this port.
.1.3.6.1.2.1.34.4.1.1.4.1.1.9,APPN-MIB::appnPortDynamicLinkSupport,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node allows call-in on this port from nodes not defined locally.
.1.3.6.1.2.1.34.4.1.1.4.1.1.10,APPN-MIB::appnPortMaxRcvBtuSize,INTEGER,read-only,,current,,Maximum Basic Transmission Unit (BTU) size that a link station on this port can receive. This object corresponds to bytes 21-22 of XID3.
.1.3.6.1.2.1.34.4.1.1.4.1.1.11,APPN-MIB::appnPortMaxIframeWindow,Gauge32,read-only,,current,,Maximum number of I-frames that can be received by the XID sender before an acknowledgement is received.
.1.3.6.1.2.1.34.4.1.1.4.1.1.12,APPN-MIB::appnPortDefLsGoodXids,Counter32,read-only,,current,,The total number of successful XID exchanges that have occurred on all defined link stations on this port since the last time this port was started.
.1.3.6.1.2.1.34.4.1.1.4.1.1.13,APPN-MIB::appnPortDefLsBadXids,Counter32,read-only,,current,,The total number of unsuccessful XID exchanges that have occurred on all defined link stations on this port since the last time this port was started.
.1.3.6.1.2.1.34.4.1.1.4.1.1.14,APPN-MIB::appnPortDynLsGoodXids,Counter32,read-only,,current,,The total number of successful XID exchanges that have occurred on all dynamic link stations on this port since the last time this port was started.
.1.3.6.1.2.1.34.4.1.1.4.1.1.15,APPN-MIB::appnPortDynLsBadXids,Counter32,read-only,,current,,The total number of unsuccessful XID exchanges that have occurred on all dynamic link stations on this port since the last time this port was started.
.1.3.6.1.2.1.34.4.1.1.4.1.1.16,APPN-MIB::appnPortSpecific,OBJECT,read-only,,current,,Identifies the object, e.g., one in a DLC-specific MIB, that can provide additional information related to this port. If the agent is unable to identify such an object, the value 0.0 is returned.
.1.3.6.1.2.1.34.4.1.1.4.1.1.17,APPN-MIB::appnPortDlcLocalAddr,OCTET,read-only,,current,,Local DLC address of this port.
.1.3.6.1.2.1.34.4.1.1.4.1.1.18,APPN-MIB::appnPortCounterDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object the last time the port was started.
.1.3.6.1.2.1.34.4.1.1.5,APPN-MIB::appnLinkStationInformation,,,,,,
.1.3.6.1.2.1.34.4.1.1.5.1,APPN-MIB::appnLsTable,,not-accessible,,current,,This table contains detailed information about the link station configuration and its current status.
.1.3.6.1.2.1.34.4.1.1.5.1.1,APPN-MIB::appnLsEntry,,not-accessible,appnLsName,current,,This table is indexed by the link station name.
.1.3.6.1.2.1.34.4.1.1.5.1.1.1,APPN-MIB::appnLsName,OCTET,not-accessible,,current,,Administratively assigned name for the link station. The name can be from one to ten characters.
.1.3.6.1.2.1.34.4.1.1.5.1.1.2,APPN-MIB::appnLsCommand,INTEGER,read-write,,current,deactivate(1):activate(2):recycle(3):ready(4),Object by which a Management Station can activate, deactivate, or recycle (i.e., cause to be deactivated and then immediately reactivated) a link station, by setting the value to activate(1), deactivate(2), or recycle(3), respectively. The value ready(4) is returned on GET operations until a SET has been processed; after that the value received on the most recent SET is returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.3,APPN-MIB::appnLsOperState,INTEGER,read-only,,current,inactive(1):sentConnectOut(2):pendXidExch(3):sendActAs(4):sendSetMode(5):otherPendingActive(6):active(7):sentDeactAsOrd(8):sentDiscOrd(9):sentDiscImmed(10):otherPendingInact(11),State of this link station. The comments map these more granular states to the 'traditional' four states for SNA resources. Values (2) through (5) represent the normal progression of states when a link station is being activated. Value (6) represents some other state of a link station in the process of being activated. Values (8) through (10) represent different ways a link station can be deactivated. Value (11) represents some other state of a link station in the process of being deactivated.
.1.3.6.1.2.1.34.4.1.1.5.1.1.4,APPN-MIB::appnLsPortName,OCTET,read-only,,current,,Administratively assigned name for the port associated with this link station. The name can be from one to ten characters.
.1.3.6.1.2.1.34.4.1.1.5.1.1.5,APPN-MIB::appnLsDlcType,INTEGER,read-only,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The type of DLC interface, distinguished according to the protocol immediately 'below' this layer.
.1.3.6.1.2.1.34.4.1.1.5.1.1.6,APPN-MIB::appnLsDynamic,INTEGER,read-only,,current,true(1):false(2),Identifies whether this is a dynamic link station. Dynamic link stations are created when links that have not been locally defined are established by adjacent nodes.
.1.3.6.1.2.1.34.4.1.1.5.1.1.7,APPN-MIB::appnLsAdjCpName,OCTET,read-only,,current,,Fully qualified name of the adjacent node for this link station. An adjacent node is identified using the format specified in the SnaControlPointName textual convention. The value of this object is determined as follows: 1. If the adjacent node's name was received on XID, it is returned. 2. If the adjacent node's name was not received on XID, but a locally-defined value is available, it is returned. 3. Otherwise a string of length 0 is returned, indicating that no name is known for the adjacent node.
.1.3.6.1.2.1.34.4.1.1.5.1.1.8,APPN-MIB::appnLsAdjNodeType,INTEGER,read-only,,current,networkNode(1):endNode(2):t21len(4):unknown(255),Node type of the adjacent node on this link: networkNode(1) - APPN network node endNode(2) - APPN end node t21len(4) - LEN end node unknown(255) - the agent does not know the node type of the adjacent node 
.1.3.6.1.2.1.34.4.1.1.5.1.1.9,APPN-MIB::appnLsTgNum,INTEGER,read-only,,current,,Number associated with the TG to this link station, with a range from 0 to 256. A value of 256 indicates that the TG number has not been negotiated and is unknown at this time.
.1.3.6.1.2.1.34.4.1.1.5.1.1.10,APPN-MIB::appnLsLimResource,INTEGER,read-only,,current,true(1):false(2),Indicates whether the link station is a limited resource. A link station that is a limited resource is deactivated when it is no longer in use.
.1.3.6.1.2.1.34.4.1.1.5.1.1.11,APPN-MIB::appnLsActOnDemand,INTEGER,read-only,,current,true(1):false(2),Indicates whether the link station is activatable on demand. Such a link station is reported in the topology as active regardless of its actual state, so that it can be considered in route calculations. If the link station is inactive and is chosen for a route, it will be activated at that time.
.1.3.6.1.2.1.34.4.1.1.5.1.1.12,APPN-MIB::appnLsMigration,INTEGER,read-only,,current,true(1):false(2),Indicates whether this link station will be used for connections to down-level or migration partners. In general, migration nodes do not append their CP names on XID3. Such nodes: (1) will not support parallel TGs, (2) should be sent an ACTIVATE PHYSICAL UNIT (ACTPU), provided that the partner supports ACTPUs, and (3) should not be sent segmented BINDs. However, if this node receives an XID3 with an appended CP name, then the partner node will not be treated as a migration node. In the case of DYNAMIC TGs this object should be set to 'no'.
.1.3.6.1.2.1.34.4.1.1.5.1.1.13,APPN-MIB::appnLsPartnerNodeId,OCTET,read-only,,current,,The partner's Node Identification, from bytes 2-5 of the XID received from the partner. If this value is not available, then the characters '00000000' are returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.14,APPN-MIB::appnLsCpCpSessionSupport,INTEGER,read-only,,current,true(1):false(2),Indicates whether CP-CP sessions are supported by this link station. For a dynamic link, this object represents the default ('Admin') value.
.1.3.6.1.2.1.34.4.1.1.5.1.1.15,APPN-MIB::appnLsMaxSendBtuSize,INTEGER,read-only,,current,,Numeric value between 99 and 32767 inclusive indicating the maximum number of bytes in a Basic Transmission Unit (BTU) sent on this link. When the link state (returned by the appnLsOperState object) is inactive or pending active, the value configured at this node is returned. When the link state is active, the value that was negotiated for it is returned. This negotiated value is the smaller of the value configured at this node and the partner's maximum receive BTU length, received in XID.
.1.3.6.1.2.1.34.4.1.1.5.1.1.16,APPN-MIB::appnLsInXidBytes,Counter32,read-only,,current,,Number of XID bytes received. All of the bytes in the SNA basic transmission unit (BTU), i.e., all of the bytes in the DLC XID Information Field, are counted.
.1.3.6.1.2.1.34.4.1.1.5.1.1.17,APPN-MIB::appnLsInMsgBytes,Counter32,read-only,,current,,Number of message (I-frame) bytes received. All of the bytes in the SNA basic transmission unit (BTU), including the transmission header (TH), are counted.
.1.3.6.1.2.1.34.4.1.1.5.1.1.18,APPN-MIB::appnLsInXidFrames,Counter32,read-only,,current,,Number of XID frames received.
.1.3.6.1.2.1.34.4.1.1.5.1.1.19,APPN-MIB::appnLsInMsgFrames,Counter32,read-only,,current,,Number of message (I-frame) frames received.
.1.3.6.1.2.1.34.4.1.1.5.1.1.20,APPN-MIB::appnLsOutXidBytes,Counter32,read-only,,current,,Number of XID bytes sent. All of the bytes in the SNA basic transmission unit (BTU), i.e., all of the bytes in the DLC XID Information Field, are counted.
.1.3.6.1.2.1.34.4.1.1.5.1.1.21,APPN-MIB::appnLsOutMsgBytes,Counter32,read-only,,current,,Number of message (I-frame) bytes sent. All of the bytes in the SNA basic transmission unit (BTU), including the transmission header (TH), are counted.
.1.3.6.1.2.1.34.4.1.1.5.1.1.22,APPN-MIB::appnLsOutXidFrames,Counter32,read-only,,current,,Number of XID frames sent.
.1.3.6.1.2.1.34.4.1.1.5.1.1.23,APPN-MIB::appnLsOutMsgFrames,Counter32,read-only,,current,,Number of message (I-frame) frames sent.
.1.3.6.1.2.1.34.4.1.1.5.1.1.24,APPN-MIB::appnLsEchoRsps,Counter32,read-only,,current,,Number of echo responses returned from adjacent link station. A response should be returned for each test frame sent by this node. Test frames are sent to adjacent nodes periodically to verify connectivity and to measure the actual round trip time, that is, the time interval from when the test frame is sent until when the response is received.
.1.3.6.1.2.1.34.4.1.1.5.1.1.25,APPN-MIB::appnLsCurrentDelay,Gauge32,read-only,,current,,The time that it took for the last test signal to be sent and returned from this link station to the adjacent link station. This time is represented in milliseconds.
.1.3.6.1.2.1.34.4.1.1.5.1.1.26,APPN-MIB::appnLsMaxDelay,Gauge32,read-only,,current,,The longest time it took for a test signal to be sent and returned from this link station to the adjacent link station. This time is represented in milliseconds . The value 0 is returned if no test signal has been sent and returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.27,APPN-MIB::appnLsMinDelay,Gauge32,read-only,,current,,The shortest time it took for a test signal to be sent and returned from this link station to the adjacent link station. This time is represented in milliseconds. The value 0 is returned if no test signal has been sent and returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.28,APPN-MIB::appnLsMaxDelayTime,OCTET,read-only,,current,,The time when the longest delay occurred. This time can be used to identify when this high water mark occurred in relation to other events in the APPN node, for example, the time at which an APPC session was either terminated or failed to be established. This latter time is available in the appcHistSessTime object in the APPC MIB. The value 00000000 is returned if no test signal has been sent and returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.29,APPN-MIB::appnLsGoodXids,Counter32,read-only,,current,,The total number of successful XID exchanges that have occurred on this link station since the time it was started.
.1.3.6.1.2.1.34.4.1.1.5.1.1.30,APPN-MIB::appnLsBadXids,Counter32,read-only,,current,,The total number of unsuccessful XID exchanges that have occurred on this link station since the time it was started.
.1.3.6.1.2.1.34.4.1.1.5.1.1.31,APPN-MIB::appnLsSpecific,OBJECT,read-only,,current,,Identifies the object, e.g., one in a DLC-specific MIB, that can provide additional information related to this link station. If the agent is unable to identify such an object, the value 0.0 is returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.32,APPN-MIB::appnLsActiveTime,Unsigned32,read-only,,current,,The cumulative amount of time since the node was last reinitialized, measured in hundredths of a second, that this link station has been in the active state. A zero value indicates that the link station has never been active since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.1.5.1.1.33,APPN-MIB::appnLsCurrentStateTime,TimeTicks,read-only,,current,,The amount of time, measured in hundredths of a second, that the link station has been in its current state.
.1.3.6.1.2.1.34.4.1.1.5.1.1.34,APPN-MIB::appnLsHprSup,INTEGER,read-only,,current,noHprSupport(1):hprBaseOnly(2):rtpTower(3):controlFlowsOverRtpTower(4),Indicates the level of high performance routing (HPR) support over this link: noHprSupport(1) - no HPR support hprBaseOnly(2) - HPR base (option set 1400) supported rtpTower(3) - HPR base and RTP tower (option set 1401) supported controlFlowsOverRtpTower(4) - HPR base, RTP tower, and control flows over RTP (option set 1402) supported If the link is not active, the defined value is returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.35,APPN-MIB::appnLsErrRecoSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether the link station is supporting HPR link-level error recovery.
.1.3.6.1.2.1.34.4.1.1.5.1.1.36,APPN-MIB::appnLsForAnrLabel,OCTET,read-only,,current,,The forward Automatic Network Routing (ANR) label for this link station. If the link does not support HPR or the value is unknown, a zero-length string is returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.37,APPN-MIB::appnLsRevAnrLabel,OCTET,read-only,,current,,The reverse Automatic Network Routing (ANR) label for this link station. If the link does not support HPR or the value is unknown, a zero-length string is returned.
.1.3.6.1.2.1.34.4.1.1.5.1.1.38,APPN-MIB::appnLsCpCpNceId,OCTET,read-only,,current,,The network connection endpoint identifier (NCE ID) for CP-CP sessions if this node supports the HPR transport tower, a zero-length string if the value is unknown or not meaningful for this node.
.1.3.6.1.2.1.34.4.1.1.5.1.1.39,APPN-MIB::appnLsRouteNceId,OCTET,read-only,,current,,The network connection endpoint identifier (NCE ID) for Route Setup if this node supports the HPR transport tower, a zero- length string if the value is unknown or not meaningful for this node.
.1.3.6.1.2.1.34.4.1.1.5.1.1.40,APPN-MIB::appnLsBfNceId,OCTET,read-only,,current,,The network connection endpoint identifier (NCE ID) for the APPN/HPR boundary function if this node supports the HPR transport tower, a zero-length string if the value is unknown or not meaningful for this node.
.1.3.6.1.2.1.34.4.1.1.5.1.1.41,APPN-MIB::appnLsLocalAddr,OCTET,read-only,,current,,Local address of this link station.
.1.3.6.1.2.1.34.4.1.1.5.1.1.42,APPN-MIB::appnLsRemoteAddr,OCTET,read-only,,current,,Address of the remote link station on this link.
.1.3.6.1.2.1.34.4.1.1.5.1.1.43,APPN-MIB::appnLsRemoteLsName,OCTET,read-only,,current,,Remote link station discovered from the XID exchange. The name can be from one to ten characters. A zero-length string indicates that the value is not known.
.1.3.6.1.2.1.34.4.1.1.5.1.1.44,APPN-MIB::appnLsCounterDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object the last time the link station was started.
.1.3.6.1.2.1.34.4.1.1.5.1.1.45,APPN-MIB::appnLsMltgMember,INTEGER,read-only,,current,true(1):false(2),Indicates whether the link is a member of a multi-link TG. If the link's TG has been brought up as a multi-link TG, then the link is reported as a member of a multi-link TG, even if it is currently the only active link in the TG.
.1.3.6.1.2.1.34.4.1.1.5.2,APPN-MIB::appnLsStatusTable,,not-accessible,,current,,This table contains information related to exceptional and potentially exceptional conditions that occurred during the activation, XID exchange, and termination of a connection. No entries are created when these activities proceed normally. It is an implementation option when entries are removed from this table.
.1.3.6.1.2.1.34.4.1.1.5.2.1,APPN-MIB::appnLsStatusEntry,,not-accessible,appnLsStatusIndex,current,,This table is indexed by the LsStatusIndex, which is an integer that is continuously updated until it eventually wraps.
.1.3.6.1.2.1.34.4.1.1.5.2.1.1,APPN-MIB::appnLsStatusIndex,INTEGER,not-accessible,,current,,Table index. The value of the index begins at zero and is incremented up to a maximum value of 2**31-1 (2,147,483,647) before wrapping.
.1.3.6.1.2.1.34.4.1.1.5.2.1.2,APPN-MIB::appnLsStatusTime,OCTET,read-only,,current,,Time when the exception condition occurred. This time can be used to identify when this event occurred in relation to other events in the APPN node, for example, the time at which an APPC session was either terminated or failed to be established. This latter time is available in the appcHistSessTime object in the APPC MIB.
.1.3.6.1.2.1.34.4.1.1.5.2.1.3,APPN-MIB::appnLsStatusLsName,OCTET,read-only,,current,,Administratively assigned name for the link station experiencing the condition.
.1.3.6.1.2.1.34.4.1.1.5.2.1.4,APPN-MIB::appnLsStatusCpName,OCTET,read-only,,current,,Fully qualified name of the adjacent node for this link station. An adjacent node is identified using the format specified in the SnaControlPointName textual convention. The value of this object is determined as follows: 1. If the adjacent node's name was received on XID, it is returned. 2. If the adjacent node's name was not received on XID, but a locally-defined value is available, it is returned. 3. Otherwise a string of length 0 is returned, indicating that no name is known for the adjacent node.
.1.3.6.1.2.1.34.4.1.1.5.2.1.5,APPN-MIB::appnLsStatusPartnerId,OCTET,read-only,,current,,The partner's Node Identification, from bytes 2-5 of the XID received from the partner. If this value is not available, then the characters '00000000' are returned.
.1.3.6.1.2.1.34.4.1.1.5.2.1.6,APPN-MIB::appnLsStatusTgNum,INTEGER,read-only,,current,,Number associated with the TG to this link station, with a range from 0 to 256. A value of 256 indicates that the TG number was unknown at the time of the failure.
.1.3.6.1.2.1.34.4.1.1.5.2.1.7,APPN-MIB::appnLsStatusGeneralSense,OCTET,read-only,,current,,The error sense data associated with the start sequence of activation of a link up to the beginning of the XID sequence. This is the sense data that came from Configuration Services whenever the link did not activate or when it went inactive.
.1.3.6.1.2.1.34.4.1.1.5.2.1.8,APPN-MIB::appnLsStatusRetry,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node will retry the start request to activate the link.
.1.3.6.1.2.1.34.4.1.1.5.2.1.9,APPN-MIB::appnLsStatusEndSense,OCTET,read-only,,current,,The sense data associated with the termination of the link connection to adjacent node. This is the sense data that came from the DLC layer.
.1.3.6.1.2.1.34.4.1.1.5.2.1.10,APPN-MIB::appnLsStatusXidLocalSense,OCTET,read-only,,current,,The sense data associated with the rejection of the XID. This is the sense data that came from the local node (this node) when it built the XID Negotiation Error control vector (cv22) to send to the remote node.
.1.3.6.1.2.1.34.4.1.1.5.2.1.11,APPN-MIB::appnLsStatusXidRemoteSense,OCTET,read-only,,current,,The sense data the adjacent node returned to this node indicating the reason the XID was rejected. This is the sense data that came from the remote node in the XID Negotiation Error control vector (cv22) it sent to the local node (this node).
.1.3.6.1.2.1.34.4.1.1.5.2.1.12,APPN-MIB::appnLsStatusXidByteInError,INTEGER,read-only,,current,,This object identifies the actual byte in the XID that caused the error. The value 65536 indicates that the object has no meaning. For values in the range 0-65535, this object corresponds to bytes 2-3 of the XID Negotiation (X'22') control vector.
.1.3.6.1.2.1.34.4.1.1.5.2.1.13,APPN-MIB::appnLsStatusXidBitInError,INTEGER,read-only,,current,,This object identifies the actual bit in error (0 through 7) within the errored byte of the XID. The value 8 indicates that this object has no meaning. For values in the range 0-7, this object corresponds to byte 4 of the XID Negotiation (X'22') control vector.
.1.3.6.1.2.1.34.4.1.1.5.2.1.14,APPN-MIB::appnLsStatusDlcType,INTEGER,read-only,,current,other(1):regular1822(2):hdh1822(3):ddnX25(4):rfc877x25(5):ethernetCsmacd(6):iso88023Csmacd(7):iso88024TokenBus(8):iso88025TokenRing(9):iso88026Man(10):starLan(11):proteon10Mbit(12):proteon80Mbit(13):hyperchannel(14):fddi(15):lapb(16):sdlc(17):ds1(18):e1(19):basicISDN(20):primaryISDN(21):propPointToPointSerial(22):ppp(23):softwareLoopback(24):eon(25):ethernet3Mbit(26):nsip(27):slip(28):ultra(29):ds3(30):sip(31):frameRelay(32):rs232(33):para(34):arcnet(35):arcnetPlus(36):atm(37):miox25(38):sonet(39):x25ple(40):iso88022llc(41):localTalk(42):smdsDxi(43):frameRelayService(44):v35(45):hssi(46):hippi(47):modem(48):aal5(49):sonetPath(50):sonetVT(51):smdsIcip(52):propVirtual(53):propMultiplexor(54):ieee80212(55):fibreChannel(56):hippiInterface(57):frameRelayInterconnect(58):aflane8023(59):aflane8025(60):cctEmul(61):fastEther(62):isdn(63):v11(64):v36(65):g703at64k(66):g703at2mb(67):qllc(68):fastEtherFX(69):channel(70):ieee80211(71):ibm370parChan(72):escon(73):dlsw(74):isdns(75):isdnu(76):lapd(77):ipSwitch(78):rsrb(79):atmLogical(80):ds0(81):ds0Bundle(82):bsc(83):async(84):cnr(85):iso88025Dtr(86):eplrs(87):arap(88):propCnls(89):hostPad(90):termPad(91):frameRelayMPI(92):x213(93):adsl(94):radsl(95):sdsl(96):vdsl(97):iso88025CRFPInt(98):myrinet(99):voiceEM(100):voiceFXO(101):voiceFXS(102):voiceEncap(103):voiceOverIp(104):atmDxi(105):atmFuni(106):atmIma(107):pppMultilinkBundle(108):ipOverCdlc(109):ipOverClaw(110):stackToStack(111):virtualIpAddress(112):mpc(113):ipOverAtm(114):iso88025Fiber(115):tdlc(116):gigabitEthernet(117):hdlc(118):lapf(119):v37(120):x25mlp(121):x25huntGroup(122):transpHdlc(123):interleave(124):fast(125):ip(126):docsCableMaclayer(127):docsCableDownstream(128):docsCableUpstream(129):a12MppSwitch(130):tunnel(131):coffee(132):ces(133):atmSubInterface(134):l2vlan(135):l3ipvlan(136):l3ipxvlan(137):digitalPowerline(138):mediaMailOverIp(139):dtm(140):dcn(141):ipForward(142):msdsl(143):ieee1394(144):if-gsn(145):dvbRccMacLayer(146):dvbRccDownstream(147):dvbRccUpstream(148):atmVirtual(149):mplsTunnel(150):srp(151):voiceOverAtm(152):voiceOverFrameRelay(153):idsl(154):compositeLink(155):ss7SigLink(156):propWirelessP2P(157):frForward(158):rfc1483(159):usb(160):ieee8023adLag(161):bgppolicyaccounting(162):frf16MfrBundle(163):h323Gatekeeper(164):h323Proxy(165):mpls(166):mfSigLink(167):hdsl2(168):shdsl(169):ds1FDL(170):pos(171):dvbAsiIn(172):dvbAsiOut(173):plc(174):nfas(175):tr008(176):gr303RDT(177):gr303IDT(178):isup(179):propDocsWirelessMaclayer(180):propDocsWirelessDownstream(181):propDocsWirelessUpstream(182):hiperlan2(183):propBWAp2Mp(184):sonetOverheadChannel(185):digitalWrapperOverheadChannel(186):aal2(187):radioMAC(188):atmRadio(189):imt(190):mvl(191):reachDSL(192):frDlciEndPt(193):atmVciEndPt(194):opticalChannel(195):opticalTransport(196):propAtm(197):voiceOverCable(198):infiniband(199):teLink(200):q2931(201):virtualTg(202):sipTg(203):sipSig(204):docsCableUpstreamChannel(205):econet(206):pon155(207):pon622(208):bridge(209):linegroup(210):voiceEMFGD(211):voiceFGDEANA(212):voiceDID(213):mpegTransport(214):sixToFour(215):gtp(216):pdnEtherLoop1(217):pdnEtherLoop2(218):opticalChannelGroup(219):homepna(220):gfp(221):ciscoISLvlan(222):actelisMetaLOOP(223):fcipLink(224):rpr(225):qam(226):lmp(227):cblVectaStar(228):docsCableMCmtsDownstream(229):adsl2(230):macSecControlledIF(231):macSecUncontrolledIF(232):aviciOpticalEther(233):atmbond(234):voiceFGDOS(235):mocaVersion1(236):ieee80216WMAN(237):adsl2plus(238):dvbRcsMacLayer(239):dvbTdm(240):dvbRcsTdma(241):x86Laps(242):wwanPP(243):wwanPP2(244):voiceEBS(245):ifPwType(246):ilan(247):pip(248):aluELP(249):gpon(250):vdsl2(251):capwapDot11Profile(252):capwapDot11Bss(253):capwapWtpVirtualRadio(254):bits(255):docsCableUpstreamRfPort(256):cableDownstreamRfPort(257):vmwareVirtualNic(258):ieee802154(259):otnOdu(260):otnOtu(261):ifVfiType(262):g9981(263):g9982(264):g9983(265):aluEpon(266):aluEponOnu(267):aluEponPhysicalUni(268):aluEponLogicalLink(269):aluGponOnu(270):aluGponPhysicalUni(271):vmwareNicTeam(272):docsOfdmDownstream(277):docsOfdmaUpstream(278):gfast(279):sdci(280):xboxWireless(281):fastdsl(282):docsCableScte55d1FwdOob(283):docsCableScte55d1RetOob(284):docsCableScte55d2DsOob(285):docsCableScte55d2UsOob(286):docsCableNdf(287):docsCableNdr(288):ptm(289):ghn(290):otnOtsi(291):otnOtuc(292):otnOduc(293):otnOtsig(294):microwaveCarrierTermination(295):microwaveRadioLinkTerminal(296),The type of DLC interface, distinguished according to the protocol immediately 'below' this layer.
.1.3.6.1.2.1.34.4.1.1.5.2.1.15,APPN-MIB::appnLsStatusLocalAddr,OCTET,read-only,,current,,Local address of this link station.
.1.3.6.1.2.1.34.4.1.1.5.2.1.16,APPN-MIB::appnLsStatusRemoteAddr,OCTET,read-only,,current,,Address of the remote link station on this link.
.1.3.6.1.2.1.34.4.1.1.6,APPN-MIB::appnVrnInfo,,,,,,
.1.3.6.1.2.1.34.4.1.1.6.1,APPN-MIB::appnVrnTable,,not-accessible,,current,,This table relates a virtual routing node to an APPN port.
.1.3.6.1.2.1.34.4.1.1.6.1.1,APPN-MIB::appnVrnEntry,,not-accessible,appnVrnName:appnVrnTgNum:appnVrnPortName,current,,This table is indexed by the virtual routing node name, TG number, and port name. There will be a matching entry in the appnLocalTgTable to represent status and characteristics of the TG representing each virtual routing node definition.
.1.3.6.1.2.1.34.4.1.1.6.1.1.1,APPN-MIB::appnVrnName,OCTET,not-accessible,,current,,Administratively assigned name of the virtual routing node. This is a fully qualified name, and matches the appnLocalTgDest name in the appnLocalTgTable.
.1.3.6.1.2.1.34.4.1.1.6.1.1.2,APPN-MIB::appnVrnTgNum,INTEGER,not-accessible,,current,,Number associated with the transmission group representing this virtual routing node definition.
.1.3.6.1.2.1.34.4.1.1.6.1.1.3,APPN-MIB::appnVrnPortName,OCTET,read-only,,current,,The name of the port this virtual routing node definition is defined to.
.1.3.6.1.2.1.34.4.1.2,APPN-MIB::appnNn,,,,,,
.1.3.6.1.2.1.34.4.1.2.1,APPN-MIB::appnNnTopo,,,,,,
.1.3.6.1.2.1.34.4.1.2.1.1,APPN-MIB::appnNnTopoMaxNodes,Gauge32,read-only,,current,,Maximum number of node entries allowed in the APPN topology database. It is an implementation choice whether to count only network-node entries, or to count all node entries. If the number of node entries exceeds this value, APPN will issue an Alert and the node can no longer participate as a network node. The value 0 indicates that the local node has no defined limit, and the number of node entries is bounded only by memory.
.1.3.6.1.2.1.34.4.1.2.1.2,APPN-MIB::appnNnTopoCurNumNodes,Gauge32,read-only,,current,,Current number of node entries in this node's topology database. It is an implementation choice whether to count only network-node entries, or to count all node entries, but an implementation must make the same choice here that it makes for the appnNnTopoMaxNodes object. If this value exceeds the maximum number of nodes allowed (appnNnTopoMaxNodes, if that field in not 0), APPN Alert CPDB002 is issued.
.1.3.6.1.2.1.34.4.1.2.1.3,APPN-MIB::appnNnTopoNodePurges,Counter32,read-only,,current,,Total number of topology node records purged from this node's topology database since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.2.1.4,APPN-MIB::appnNnTopoTgPurges,Counter32,read-only,,current,,Total number of topology TG records purged from this node's topology database since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.2.1.5,APPN-MIB::appnNnTopoTotalTduWars,Counter32,read-only,,current,,Number of TDU wars detected by this node since its last initialization.
.1.3.6.1.2.1.34.4.1.2.2,APPN-MIB::appnNnTopology,,,,,,
.1.3.6.1.2.1.34.4.1.2.2.3,APPN-MIB::appnNnTopologyFRTable,,not-accessible,,current,,Portion of the APPN topology database that describes all of the APPN network nodes and virtual routing nodes known to this node.
.1.3.6.1.2.1.34.4.1.2.2.3.1,APPN-MIB::appnNnTopologyFREntry,,not-accessible,appnNnNodeFRFrsn:appnNnNodeFRName,current,,The FRSN and the fully qualified node name are used to index this table.
.1.3.6.1.2.1.34.4.1.2.2.3.1.1,APPN-MIB::appnNnNodeFRFrsn,Unsigned32,not-accessible,,current,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last relative time this resource was updated at the agent node.
.1.3.6.1.2.1.34.4.1.2.2.3.1.2,APPN-MIB::appnNnNodeFRName,OCTET,not-accessible,,current,,Administratively assigned network name that is locally defined at each network node.
.1.3.6.1.2.1.34.4.1.2.2.3.1.3,APPN-MIB::appnNnNodeFREntryTimeLeft,INTEGER,read-only,,current,,Number of days before deletion of this network node entry.
.1.3.6.1.2.1.34.4.1.2.2.3.1.4,APPN-MIB::appnNnNodeFRType,INTEGER,read-only,,current,networkNode(1):virtualRoutingNode(3),Type of APPN node.
.1.3.6.1.2.1.34.4.1.2.2.3.1.5,APPN-MIB::appnNnNodeFRRsn,Unsigned32,read-only,,current,,Resource sequence number, which is assigned and controlled by the network node that owns this resource. An odd number indicates that information about the resource is inconsistent. This object corresponds to the numeric value in cv4580, bytes 2-5.
.1.3.6.1.2.1.34.4.1.2.2.3.1.6,APPN-MIB::appnNnNodeFRRouteAddResist,INTEGER,read-only,,current,,Route addition resistance. This administratively assigned value indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing. This object corresponds to cv4580, byte 6.
.1.3.6.1.2.1.34.4.1.2.2.3.1.7,APPN-MIB::appnNnNodeFRCongested,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node is congested. This node is not be included in route selection by other nodes when this congestion exists. This object corresponds to cv4580, byte 7, bit 0.
.1.3.6.1.2.1.34.4.1.2.2.3.1.8,APPN-MIB::appnNnNodeFRIsrDepleted,INTEGER,read-only,,current,true(1):false(2),Indicates whether intermediate session routing resources are depleted. This node is not included in intermediate route selection by other nodes when resources are depleted. This object corresponds to cv4580, byte 7, bit 1.
.1.3.6.1.2.1.34.4.1.2.2.3.1.9,APPN-MIB::appnNnNodeFRQuiescing,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node is quiescing. This node is not included in route selection by other nodes when the node is quiescing. This object corresponds to cv4580, byte 7, bit 5.
.1.3.6.1.2.1.34.4.1.2.2.3.1.10,APPN-MIB::appnNnNodeFRGateway,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node provide gateway services. This object corresponds to cv4580, byte 8, bit 0.
.1.3.6.1.2.1.34.4.1.2.2.3.1.11,APPN-MIB::appnNnNodeFRCentralDirectory,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node supports central directory services. This object corresponds to cv4580, byte 8, bit 1.
.1.3.6.1.2.1.34.4.1.2.2.3.1.12,APPN-MIB::appnNnNodeFRIsr,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node supports intermediate session routing (ISR). This object corresponds to cv4580, byte 8, bit 2.
.1.3.6.1.2.1.34.4.1.2.2.3.1.13,APPN-MIB::appnNnNodeFRGarbageCollect,INTEGER,read-only,,current,true(1):false(2),Indicates whether the node has been marked for garbage collection (deletion from the topology database) upon the next garbage collection cycle. This object corresponds to cv4580, byte 7, bit 3.
.1.3.6.1.2.1.34.4.1.2.2.3.1.14,APPN-MIB::appnNnNodeFRHprSupport,INTEGER,read-only,,current,noHprSupport(1):hprBaseOnly(2):rtpTower(3):controlFlowsOverRtpTower(4),Indicates the node's level of support for high-performance routing (HPR): noHprSupport(1) - no HPR support hprBaseOnly(2) - HPR base (option set 1400) supported rtpTower(3) - HPR base and RTP tower (option set 1401) supported controlFlowsOverRtpTower(4) - HPR base, RTP tower, and control flows over RTP (option set 1402) supported This object corresponds to cv4580, byte 9, bits 3-4.
.1.3.6.1.2.1.34.4.1.2.2.3.1.15,APPN-MIB::appnNnNodeFRPeriBorderSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node has peripheral border node support. This object corresponds to cv4580, byte 9, bit 0.
.1.3.6.1.2.1.34.4.1.2.2.3.1.16,APPN-MIB::appnNnNodeFRInterchangeSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node has interchange node support. This object corresponds to cv4580, byte 9, bit 1.
.1.3.6.1.2.1.34.4.1.2.2.3.1.17,APPN-MIB::appnNnNodeFRExteBorderSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node has extended border node support. This object corresponds to cv4580, byte 9, bit 2.
.1.3.6.1.2.1.34.4.1.2.2.3.1.18,APPN-MIB::appnNnNodeFRBranchAwareness,INTEGER,read-only,,current,true(1):false(2),Indicates whether this node supports branch awareness. This object corresponds to cv4580, byte 8, bit 4.
.1.3.6.1.2.1.34.4.1.2.2.4,APPN-MIB::appnNnTgTopologyFRTable,,not-accessible,,current,,Portion of the APPN topology database that describes all of the APPN transmissions groups between nodes in the database.
.1.3.6.1.2.1.34.4.1.2.2.4.1,APPN-MIB::appnNnTgTopologyFREntry,,not-accessible,appnNnTgFRFrsn:appnNnTgFROwner:appnNnTgFRDest:appnNnTgFRNum,current,,This table is indexed by four columns: FRSN, TG owner fully qualified node name, TG destination fully qualified node name, and TG number.
.1.3.6.1.2.1.34.4.1.2.2.4.1.1,APPN-MIB::appnNnTgFRFrsn,Unsigned32,not-accessible,,current,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node.
.1.3.6.1.2.1.34.4.1.2.2.4.1.2,APPN-MIB::appnNnTgFROwner,OCTET,not-accessible,,current,,Administratively assigned name for the originating node for this TG. This is the same name specified in the node table.
.1.3.6.1.2.1.34.4.1.2.2.4.1.3,APPN-MIB::appnNnTgFRDest,OCTET,not-accessible,,current,,Administratively assigned fully qualified network name for the destination node for this TG.
.1.3.6.1.2.1.34.4.1.2.2.4.1.4,APPN-MIB::appnNnTgFRNum,INTEGER,not-accessible,,current,,Number associated with this transmission group. Range is 0-255.
.1.3.6.1.2.1.34.4.1.2.2.4.1.5,APPN-MIB::appnNnTgFREntryTimeLeft,INTEGER,read-only,,current,,Number of days before deletion of this network node TG entry if it is not operational or has an odd (inconsistent) RSN.
.1.3.6.1.2.1.34.4.1.2.2.4.1.6,APPN-MIB::appnNnTgFRDestVirtual,INTEGER,read-only,,current,true(1):false(2),Indicates whether the destination node is a virtual routing node.
.1.3.6.1.2.1.34.4.1.2.2.4.1.7,APPN-MIB::appnNnTgFRDlcData,OCTET,read-only,,current,,DLC-specific data related to a link connection network.
.1.3.6.1.2.1.34.4.1.2.2.4.1.8,APPN-MIB::appnNnTgFRRsn,Unsigned32,read-only,,current,,Current owning node's resource sequence number for this resource. An odd number indicates that information about the resource is inconsistent. This object corresponds to the numeric value in cv47, bytes 2-5
.1.3.6.1.2.1.34.4.1.2.2.4.1.9,APPN-MIB::appnNnTgFROperational,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is operational. This object corresponds to cv47, byte 6, bit 0.
.1.3.6.1.2.1.34.4.1.2.2.4.1.10,APPN-MIB::appnNnTgFRQuiescing,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is quiescing. If the TG owner is either an extended border node or a branch-aware network node (indicated, respectively, by the appnNnNodeFRExteBorderSup and appnNnNodeFRBranchAwareness objects in the corresponding appnNnTopologyFREntry), then this indicator is artificially set to TRUE in the APPN topology database, to remove the TG from other nodes' route calculations. A management application can determine whether the TG is actually quiescing by examining its appnLocalTgQuiescing object at the TG owner. This object corresponds to cv47, byte 6, bit 2.
.1.3.6.1.2.1.34.4.1.2.2.4.1.11,APPN-MIB::appnNnTgFRCpCpSession,INTEGER,read-only,,current,supportedUnknownStatus(1):supportedActive(2):notSupported(3):supportedNotActive(4),Indicates whether CP-CP sessions are supported on this TG, and whether the TG owner's contention-winner session is active on this TG. Some nodes in the network are not able to differentiate support and status of CP-CP sessions, and thus may report the 'supportedUnknownStatus' value. This object corresponds to cv47, byte 6, bits 3-4.
.1.3.6.1.2.1.34.4.1.2.2.4.1.12,APPN-MIB::appnNnTgFREffCap,OCTET,read-only,,current,,Effective capacity for this TG.
.1.3.6.1.2.1.34.4.1.2.2.4.1.13,APPN-MIB::appnNnTgFRConnCost,INTEGER,read-only,,current,,Cost per connect time. This is an administratively assigned value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255, which indicates maximum cost. This object corresponds to cv47, byte 13.
.1.3.6.1.2.1.34.4.1.2.2.4.1.14,APPN-MIB::appnNnTgFRByteCost,INTEGER,read-only,,current,,Cost per byte transmitted. This is an administratively assigned value representing the relative cost of transmitting a byte over this TG. Range is from 0, which means no cost, to 255, which indicates maximum cost. This object corresponds to cv47, byte 14.
.1.3.6.1.2.1.34.4.1.2.2.4.1.15,APPN-MIB::appnNnTgFRSecurity,INTEGER,read-only,,current,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Administratively assigned security level of this TG. This object corresponds to cv47, byte 16.
.1.3.6.1.2.1.34.4.1.2.2.4.1.16,APPN-MIB::appnNnTgFRDelay,OCTET,read-only,,current,,Administratively assigned delay associated with this TG. This object corresponds to cv47, byte 17.
.1.3.6.1.2.1.34.4.1.2.2.4.1.17,APPN-MIB::appnNnTgFRUsr1,INTEGER,read-only,,current,,First user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG. This object corresponds to cv47, byte 19.
.1.3.6.1.2.1.34.4.1.2.2.4.1.18,APPN-MIB::appnNnTgFRUsr2,INTEGER,read-only,,current,,Second user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG. This object corresponds to cv47, byte 20.
.1.3.6.1.2.1.34.4.1.2.2.4.1.19,APPN-MIB::appnNnTgFRUsr3,INTEGER,read-only,,current,,Third user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG. This object corresponds to cv47, byte 21.
.1.3.6.1.2.1.34.4.1.2.2.4.1.20,APPN-MIB::appnNnTgFRGarbageCollect,INTEGER,read-only,,current,true(1):false(2),Indicates whether the TG has been marked for garbage collection (deletion from the topology database) upon the next garbage collection cycle. This object corresponds to cv47, byte 6, bit 1.
.1.3.6.1.2.1.34.4.1.2.2.4.1.21,APPN-MIB::appnNnTgFRSubareaNum,Unsigned32,read-only,,current,,The subarea number associated with this TG. This object corresponds to cv4680, bytes m+2 through m+5.
.1.3.6.1.2.1.34.4.1.2.2.4.1.22,APPN-MIB::appnNnTgFRHprSup,INTEGER,read-only,,current,true(1):false(2),Indicates whether high performance routing (HPR) is supported over this TG. This object corresponds to cv4680, byte m+1, bit 2.
.1.3.6.1.2.1.34.4.1.2.2.4.1.23,APPN-MIB::appnNnTgFRDestHprTrans,INTEGER,read-only,,current,true(1):false(2),Indicates whether the destination node supports high performance routing (HPR) transport tower. This object corresponds to cv4680, byte m+1, bit 7.
.1.3.6.1.2.1.34.4.1.2.2.4.1.24,APPN-MIB::appnNnTgFRTypeIndicator,INTEGER,read-only,,current,unknown(1):appnOrBfTg(2):interchangeTg(3):virtualRouteTg(4),Indicates the type of the TG. This object corresponds to cv4680, byte m+1, bits 3-4.
.1.3.6.1.2.1.34.4.1.2.2.4.1.25,APPN-MIB::appnNnTgFRIntersubnet,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is an intersubnet TG, which defines a border between subnetworks. This object corresponds to cv4680, byte m+1, bit 5.
.1.3.6.1.2.1.34.4.1.2.2.4.1.26,APPN-MIB::appnNnTgFRMltgLinkType,INTEGER,read-only,,current,true(1):false(2),This object indicates whether the transmission group is a multi-link TG. A TG that has been brought up as a multi-link TG is reported as one, even if it currently has only one link active. This object corresponds to cv47, byte 6, bit 5.
.1.3.6.1.2.1.34.4.1.2.2.4.1.27,APPN-MIB::appnNnTgFRBranchTg,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is a branch TG (equivalently, whether the destination of the transmission group is a branch network node). This object corresponds to cv4680, byte m+1, bit 1.
.1.3.6.1.2.1.34.4.1.3,APPN-MIB::appnLocalTopology,,,,,,
.1.3.6.1.2.1.34.4.1.3.1,APPN-MIB::appnLocalTgTable,,not-accessible,,current,,TG Table describes all of the TGs owned by this node. The TG destination can be a virtual node, network node, LEN node, or end node.
.1.3.6.1.2.1.34.4.1.3.1.1,APPN-MIB::appnLocalTgEntry,,not-accessible,appnLocalTgDest:appnLocalTgNum,current,,This table is indexed by the destination CpName and the TG number.
.1.3.6.1.2.1.34.4.1.3.1.1.1,APPN-MIB::appnLocalTgDest,OCTET,not-accessible,,current,,Administratively assigned name of the destination node for this TG. This is the fully qualified name of a network node, end node, LEN node, or virtual routing node.
.1.3.6.1.2.1.34.4.1.3.1.1.2,APPN-MIB::appnLocalTgNum,INTEGER,not-accessible,,current,,Number associated with this transmission group.
.1.3.6.1.2.1.34.4.1.3.1.1.3,APPN-MIB::appnLocalTgDestVirtual,INTEGER,read-only,,current,true(1):false(2),Indicates whether the destination node for this TG is a virtual routing node.
.1.3.6.1.2.1.34.4.1.3.1.1.4,APPN-MIB::appnLocalTgDlcData,OCTET,read-only,,current,,DLC-specific data related to a link connection network.
.1.3.6.1.2.1.34.4.1.3.1.1.5,APPN-MIB::appnLocalTgPortName,OCTET,read-only,,current,,Administratively assigned name for the local port associated with this TG. A zero-length string indicates that this value is unknown.
.1.3.6.1.2.1.34.4.1.3.1.1.6,APPN-MIB::appnLocalTgQuiescing,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is quiescing.
.1.3.6.1.2.1.34.4.1.3.1.1.7,APPN-MIB::appnLocalTgOperational,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is operational.
.1.3.6.1.2.1.34.4.1.3.1.1.8,APPN-MIB::appnLocalTgCpCpSession,INTEGER,read-only,,current,supportedUnknownStatus(1):supportedActive(2):notSupported(3):supportedNotActive(4),Indicates whether CP-CP sessions are supported on this TG, and whether the TG owner's contention-winner session is active on this TG. Some nodes in the network are not able to differentiate support and status of CP-CP sessions, and thus may report the 'supportedUnknownStatus' value.
.1.3.6.1.2.1.34.4.1.3.1.1.9,APPN-MIB::appnLocalTgEffCap,OCTET,read-only,,current,,Effective capacity for this TG.
.1.3.6.1.2.1.34.4.1.3.1.1.10,APPN-MIB::appnLocalTgConnCost,INTEGER,read-only,,current,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.3.1.1.11,APPN-MIB::appnLocalTgByteCost,INTEGER,read-only,,current,,Relative cost of transmitting a byte over this link. Range is from 0 (lowest cost) to 255.
.1.3.6.1.2.1.34.4.1.3.1.1.12,APPN-MIB::appnLocalTgSecurity,INTEGER,read-only,,current,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Administratively assigned security level of this TG.
.1.3.6.1.2.1.34.4.1.3.1.1.13,APPN-MIB::appnLocalTgDelay,OCTET,read-only,,current,,Administratively assigned delay associated with this TG.
.1.3.6.1.2.1.34.4.1.3.1.1.14,APPN-MIB::appnLocalTgUsr1,INTEGER,read-only,,current,,First user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG.
.1.3.6.1.2.1.34.4.1.3.1.1.15,APPN-MIB::appnLocalTgUsr2,INTEGER,read-only,,current,,Second user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG.
.1.3.6.1.2.1.34.4.1.3.1.1.16,APPN-MIB::appnLocalTgUsr3,INTEGER,read-only,,current,,Third user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG.
.1.3.6.1.2.1.34.4.1.3.1.1.17,APPN-MIB::appnLocalTgHprSup,INTEGER,read-only,,current,noHprSupport(1):hprBaseOnly(2):rtpTower(3):controlFlowsOverRtpTower(4),Indicates the level of high performance routing (HPR) support over this TG : noHprSupport(1) - no HPR support hprBaseOnly(2) - HPR base (option set 1400) supported rtpTower(3) - HPR base and RTP tower (option set 1401) supported controlFlowsOverRtpTower(4) - HPR base, RTP tower, and control flows over RTP (option set 1402) supported
.1.3.6.1.2.1.34.4.1.3.1.1.18,APPN-MIB::appnLocalTgIntersubnet,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is an intersubnet TG, which defines a border between subnetworks.
.1.3.6.1.2.1.34.4.1.3.1.1.19,APPN-MIB::appnLocalTgMltgLinkType,INTEGER,read-only,,current,true(1):false(2),This object indicates whether the transmission group is a multi-link TG. A TG that has been brought up as a multi-link TG is reported as one, even if it currently has only one link active.
.1.3.6.1.2.1.34.4.1.3.1.1.20,APPN-MIB::appnLocalTgBranchLinkType,INTEGER,read-only,,current,other(1):uplink(2):downlink(3):downlinkToBranchNetworkNode(4):none(5):unknown(255),Branch link type of this TG: other(1) = the agent has determined the TG's branch link type to be a value other than branch uplink or branch downlink. This is the value used for a connection network TG owned by a branch network node. uplink(2) = the TG is a branch uplink. downlink(3) = the TG is a branch downlink to an end node. downlinkToBranchNetworkNode(4) = the TG is a branch downlink to a cascaded branch network node. none(5) = the TG is not a branch TG. unknown(255) = the agent cannot determine the branch link type of the TG.
.1.3.6.1.2.1.34.4.1.3.2,APPN-MIB::appnLocalEnTgTable,,not-accessible,,current,,Table describing all of the TGs owned by the end nodes known to this node via TG registration. This node does not represent its own view of the TG on behalf of the partner node in this table. The TG destination can be a virtual routing node, network node, or end node.
.1.3.6.1.2.1.34.4.1.3.2.1,APPN-MIB::appnLocalEnTgEntry,,not-accessible,appnLocalEnTgOrigin:appnLocalEnTgDest:appnLocalEnTgNum,current,,This table requires multiple indexes to uniquely identify each TG. They are originating CPname, destination CPname, and the TG number.
.1.3.6.1.2.1.34.4.1.3.2.1.1,APPN-MIB::appnLocalEnTgOrigin,OCTET,not-accessible,,current,,Administratively assigned name of the origin node for this TG. This is a fully qualified network name.
.1.3.6.1.2.1.34.4.1.3.2.1.2,APPN-MIB::appnLocalEnTgDest,OCTET,not-accessible,,current,,Administratively assigned name of the destination node for this TG. This is the fully qualified name of a network node, end node, LEN node, or virtual routing node.
.1.3.6.1.2.1.34.4.1.3.2.1.3,APPN-MIB::appnLocalEnTgNum,INTEGER,not-accessible,,current,,Number associated with this transmission group.
.1.3.6.1.2.1.34.4.1.3.2.1.4,APPN-MIB::appnLocalEnTgEntryTimeLeft,INTEGER,read-only,,current,,Number of days before deletion of this end node TG entry.
.1.3.6.1.2.1.34.4.1.3.2.1.5,APPN-MIB::appnLocalEnTgDestVirtual,INTEGER,read-only,,current,true(1):false(2),Indicates whether the destination node is a virtual routing node.
.1.3.6.1.2.1.34.4.1.3.2.1.6,APPN-MIB::appnLocalEnTgDlcData,OCTET,read-only,,current,,DLC-specific data related to a link connection network.
.1.3.6.1.2.1.34.4.1.3.2.1.7,APPN-MIB::appnLocalEnTgOperational,INTEGER,read-only,,current,true(1):false(2),Indicates whether the transmission group is operational.
.1.3.6.1.2.1.34.4.1.3.2.1.8,APPN-MIB::appnLocalEnTgCpCpSession,INTEGER,read-only,,current,supportedUnknownStatus(1):supportedActive(2):notSupported(3):supportedNotActive(4),Indicates whether CP-CP sessions are supported on this TG, and whether the TG owner's contention-winner session is active on this TG. Some nodes in the network are not able to differentiate support and status of CP-CP sessions, and thus may report the 'supportedUnknownStatus' value.
.1.3.6.1.2.1.34.4.1.3.2.1.9,APPN-MIB::appnLocalEnTgEffCap,OCTET,read-only,,current,,Effective capacity for this TG.
.1.3.6.1.2.1.34.4.1.3.2.1.10,APPN-MIB::appnLocalEnTgConnCost,INTEGER,read-only,,current,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.3.2.1.11,APPN-MIB::appnLocalEnTgByteCost,INTEGER,read-only,,current,,Relative cost of transmitting a byte over this link. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.3.2.1.12,APPN-MIB::appnLocalEnTgSecurity,INTEGER,read-only,,current,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Administratively assigned security level of this TG.
.1.3.6.1.2.1.34.4.1.3.2.1.13,APPN-MIB::appnLocalEnTgDelay,OCTET,read-only,,current,,Administratively assigned delay associated with this TG.
.1.3.6.1.2.1.34.4.1.3.2.1.14,APPN-MIB::appnLocalEnTgUsr1,INTEGER,read-only,,current,,First user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG.
.1.3.6.1.2.1.34.4.1.3.2.1.15,APPN-MIB::appnLocalEnTgUsr2,INTEGER,read-only,,current,,Second user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG.
.1.3.6.1.2.1.34.4.1.3.2.1.16,APPN-MIB::appnLocalEnTgUsr3,INTEGER,read-only,,current,,Third user-defined TG characteristic for this TG. This is an administratively assigned value associated with the TG.
.1.3.6.1.2.1.34.4.1.3.2.1.17,APPN-MIB::appnLocalEnTgMltgLinkType,INTEGER,read-only,,current,true(1):false(2),This object indicates whether the transmission group is a multi-link TG. A TG that has been brought up as a multi-link TG is reported as one, even if it currently has only one link active.
.1.3.6.1.2.1.34.4.1.4,APPN-MIB::appnDir,,,,,,
.1.3.6.1.2.1.34.4.1.4.1,APPN-MIB::appnDirPerf,,,,,,
.1.3.6.1.2.1.34.4.1.4.1.1,APPN-MIB::appnDirMaxCaches,Unsigned32,read-only,,current,,Maximum number of cache entries allowed. This is an administratively assigned value.
.1.3.6.1.2.1.34.4.1.4.1.2,APPN-MIB::appnDirCurCaches,Gauge32,read-only,,current,,Current number of cache entries.
.1.3.6.1.2.1.34.4.1.4.1.3,APPN-MIB::appnDirCurHomeEntries,Gauge32,read-only,,current,,Current number of home entries.
.1.3.6.1.2.1.34.4.1.4.1.4,APPN-MIB::appnDirRegEntries,Gauge32,read-only,,current,,Current number of registered entries.
.1.3.6.1.2.1.34.4.1.4.1.5,APPN-MIB::appnDirInLocates,Counter32,read-only,,current,,Number of directed Locates received since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.4.1.6,APPN-MIB::appnDirInBcastLocates,Counter32,read-only,,current,,Number of broadcast Locates received since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.4.1.7,APPN-MIB::appnDirOutLocates,Counter32,read-only,,current,,Number of directed Locates sent since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.4.1.8,APPN-MIB::appnDirOutBcastLocates,Counter32,read-only,,current,,Number of broadcast Locates sent since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.4.1.9,APPN-MIB::appnDirNotFoundLocates,Counter32,read-only,,current,,Number of directed Locates returned with a 'not found' since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.4.1.10,APPN-MIB::appnDirNotFoundBcastLocates,Counter32,read-only,,current,,Number of broadcast Locates returned with a 'not found' since the node was last reinitialized.
.1.3.6.1.2.1.34.4.1.4.1.11,APPN-MIB::appnDirLocateOutstands,Gauge32,read-only,,current,,Current number of outstanding Locates, both directed and broadcast. This value varies. A value of zero indicates that no Locates are unanswered.
.1.3.6.1.2.1.34.4.1.4.2,APPN-MIB::appnDirTable,,not-accessible,,current,,Table containing information about all known LUs.
.1.3.6.1.2.1.34.4.1.4.2.1,APPN-MIB::appnDirEntry,,not-accessible,appnDirLuName,current,,This table is indexed by the LU name.
.1.3.6.1.2.1.34.4.1.4.2.1.1,APPN-MIB::appnDirLuName,OCTET,not-accessible,,current,,Fully qualified network LU name in the domain of the serving network node. Entries take one of three forms: - Explicit entries do not contain the character '*'. - Partial wildcard entries have the form 'ccc*', where 'ccc' represents one to sixteen characters in a legal SNA LuName. - A full wildcard entry consists of the single character '*'
.1.3.6.1.2.1.34.4.1.4.2.1.2,APPN-MIB::appnDirNnServerName,OCTET,read-only,,current,,Fully qualified control point (CP) name of the network node server. For unassociated end node entries, a zero-length string is returned.
.1.3.6.1.2.1.34.4.1.4.2.1.3,APPN-MIB::appnDirLuOwnerName,OCTET,read-only,,current,,Fully qualified CP name of the node at which the LU is located. This name is the same as the serving NN name when the LU is located at a network node. It is also the same as the fully qualified LU name when this is the control point LU for this node.
.1.3.6.1.2.1.34.4.1.4.2.1.4,APPN-MIB::appnDirLuLocation,INTEGER,read-only,,current,local(1):domain(2):xdomain(3),Specifies the location of the LU with respect to the local node.
.1.3.6.1.2.1.34.4.1.4.2.1.5,APPN-MIB::appnDirType,INTEGER,read-only,,current,home(1):cache(2):registered(3),Directory types are: 1 - Home The LU is in the domain of the local node, and the LU information has been configured at the local node. 2 - Cache The LU has previously been located by a broadcast search, and the location information has been saved. 3 - Registered The LU is at an end node that is in the domain of the local network node. Registered entries are registered by the served end node.
.1.3.6.1.2.1.34.4.1.4.2.1.6,APPN-MIB::appnDirApparentLuOwnerName,OCTET,read-only,,current,,Fully qualified CP name of the node at which the LU appears to be located. This object and the appnDirLuOwnerName object are related as follows: Implementations that support this object save in their directory database information about an LU's owning control point that was communicated in two control vectors: - an Associated Resource Entry (X'3C') CV with resource type X'00F4' (ENCP) - a Real Owning Control Point (X'4A') CV. The X'4A' CV is created by a branch network node to preserve the name of the real owning control point for an LU below the branch network node, before it overwrites this name with its own name in the X'3C' CV. The X'4A' CV is not present for LUs that are not below branch network nodes. If the information a node has about an LU's owning CP came only in a X'3C' CV, then the name from the X'3C' is returned in the appnDirLuOwnerName object, and a null string is returned in this object. If the information a node has about an LU's owning CP came in both X'3C' and X'4A' CVs, then the name from the X'4A' is returned in the appnDirLuOwnerName object, and the name from the X'3C' (which will be the branch network node's name) is returned in this object.
.1.3.6.1.2.1.34.4.1.5,APPN-MIB::appnCos,,,,,,
.1.3.6.1.2.1.34.4.1.5.1,APPN-MIB::appnCosModeTable,,not-accessible,,current,,Table representing all of the defined mode names for this node. The table contains the matching COS name for each mode name.
.1.3.6.1.2.1.34.4.1.5.1.1,APPN-MIB::appnCosModeEntry,,not-accessible,appnCosModeName,current,,This table is indexed by the mode name.
.1.3.6.1.2.1.34.4.1.5.1.1.1,APPN-MIB::appnCosModeName,OCTET,not-accessible,,current,,Administratively assigned name for this mode.
.1.3.6.1.2.1.34.4.1.5.1.1.2,APPN-MIB::appnCosModeCosName,OCTET,read-only,,current,,Administratively assigned name for this class of service.
.1.3.6.1.2.1.34.4.1.5.2,APPN-MIB::appnCosNameTable,,not-accessible,,current,,Table mapping all of the defined class-of-service names for this node to their network transmission priorities.
.1.3.6.1.2.1.34.4.1.5.2.1,APPN-MIB::appnCosNameEntry,,not-accessible,appnCosName,current,,The COS name is the index to this table.
.1.3.6.1.2.1.34.4.1.5.2.1.1,APPN-MIB::appnCosName,OCTET,not-accessible,,current,,Administratively assigned name for this class of service.
.1.3.6.1.2.1.34.4.1.5.2.1.2,APPN-MIB::appnCosTransPriority,INTEGER,read-only,,current,low(1):medium(2):high(3):network(4),Transmission priority for this class of service: low(1) - (X'01'): low priority medium(2) - (X'02'): medium priority high(3) - (X'03'): high priority network(4) - (X'04'): network priority
.1.3.6.1.2.1.34.4.1.5.3,APPN-MIB::appnCosNodeRowTable,,not-accessible,,current,,This table contains all node-row information for all classes of service defined in this node.
.1.3.6.1.2.1.34.4.1.5.3.1,APPN-MIB::appnCosNodeRowEntry,,not-accessible,appnCosNodeRowName:appnCosNodeRowIndex,current,,A node entry for a given class of service.
.1.3.6.1.2.1.34.4.1.5.3.1.1,APPN-MIB::appnCosNodeRowName,OCTET,not-accessible,,current,,Administratively assigned name for this class of service.
.1.3.6.1.2.1.34.4.1.5.3.1.2,APPN-MIB::appnCosNodeRowIndex,INTEGER,not-accessible,,current,,Subindex under appnCosNodeRowName, corresponding to a row in the node table for the class of service identified in appnCosNodeRowName. For each class of service, this subindex orders rows in the appnCosNodeRowTable in the same order as that used for route calculation in the APPN node.
.1.3.6.1.2.1.34.4.1.5.3.1.3,APPN-MIB::appnCosNodeRowWgt,OCTET,read-only,,current,,Weight to be associated with the nodes that fit the criteria specified by this node row. This value can either be a character representation of an integer, or a formula for calculating the weight.
.1.3.6.1.2.1.34.4.1.5.3.1.4,APPN-MIB::appnCosNodeRowResistMin,INTEGER,read-only,,current,,Minimum route addition resistance value for this node. Range of values is 0-255. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.2.1.34.4.1.5.3.1.5,APPN-MIB::appnCosNodeRowResistMax,INTEGER,read-only,,current,,Maximum route addition resistance value for this node. Range of values is 0-255. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.2.1.34.4.1.5.3.1.6,APPN-MIB::appnCosNodeRowMinCongestAllow,INTEGER,read-only,,current,,Indicates whether low congestion will be tolerated. This object and appnCosNodeRowMaxCongestAllow together delineate a range of acceptable congestion states for a node. For the ordered pair (minimum congestion allowed, maximum congestion allowed), the values are interpreted as follows: - (0,0): only low congestion is acceptable - (0,1): either low or high congestion is acceptable - (1,1): only high congestion is acceptable. Note that the combination (1,0) is not defined, since it would identify a range whose lower bound was high congestion and whose upper bound was low congestion.
.1.3.6.1.2.1.34.4.1.5.3.1.7,APPN-MIB::appnCosNodeRowMaxCongestAllow,INTEGER,read-only,,current,,Indicates whether low congestion will be tolerated. This object and appnCosNodeRowMinCongestAllow together delineate a range of acceptable congestion states for a node. For the ordered pair (minimum congestion allowed, maximum congestion allowed), the values are interpreted as follows: - (0,0): only low congestion is acceptable - (0,1): either low or high congestion is acceptable - (1,1): only high congestion is acceptable. Note that the combination (1,0) is not defined, since it would identify a range whose lower bound was high congestion and whose upper bound was low congestion.
.1.3.6.1.2.1.34.4.1.5.4,APPN-MIB::appnCosTgRowTable,,not-accessible,,current,,Table containing all the TG-row information for all classes of service defined in this node.
.1.3.6.1.2.1.34.4.1.5.4.1,APPN-MIB::appnCosTgRowEntry,,not-accessible,appnCosTgRowName:appnCosTgRowIndex,current,,A TG entry for a given class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.1,APPN-MIB::appnCosTgRowName,OCTET,not-accessible,,current,,Administratively assigned name for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.2,APPN-MIB::appnCosTgRowIndex,INTEGER,not-accessible,,current,,Subindex under appnCosTgRowName, corresponding to a row in the TG table for the class of service identified in appnCosTgRowName. For each class of service, this subindex orders rows in the appnCosTgRowTable in the same order as that used for route calculation in the APPN node.
.1.3.6.1.2.1.34.4.1.5.4.1.3,APPN-MIB::appnCosTgRowWgt,OCTET,read-only,,current,,Weight to be associated with the TGs that fit the criteria specified by this TG row. This value can either be a character representation of an integer, or a formula for calculating the weight.
.1.3.6.1.2.1.34.4.1.5.4.1.4,APPN-MIB::appnCosTgRowEffCapMin,OCTET,read-only,,current,,Minimum acceptable capacity for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.5,APPN-MIB::appnCosTgRowEffCapMax,OCTET,read-only,,current,,Maximum acceptable capacity for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.6,APPN-MIB::appnCosTgRowConnCostMin,INTEGER,read-only,,current,,Minimum acceptable cost per connect time for this class of service. Cost per connect time: a value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.5.4.1.7,APPN-MIB::appnCosTgRowConnCostMax,INTEGER,read-only,,current,,Maximum acceptable cost per connect time for this class of service. Cost per connect time: a value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.5.4.1.8,APPN-MIB::appnCosTgRowByteCostMin,INTEGER,read-only,,current,,Minimum acceptable cost per byte transmitted for this class of service. Cost per byte transmitted: a value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.5.4.1.9,APPN-MIB::appnCosTgRowByteCostMax,INTEGER,read-only,,current,,Maximum acceptable cost per byte transmitted for this class of service. Cost per byte transmitted: a value representing the relative cost of transmitting a byte over this TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.2.1.34.4.1.5.4.1.10,APPN-MIB::appnCosTgRowSecurityMin,INTEGER,read-only,,current,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Minimum acceptable security for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.11,APPN-MIB::appnCosTgRowSecurityMax,INTEGER,read-only,,current,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Maximum acceptable security for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.12,APPN-MIB::appnCosTgRowDelayMin,OCTET,read-only,,current,,Minimum acceptable propagation delay for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.13,APPN-MIB::appnCosTgRowDelayMax,OCTET,read-only,,current,,Maximum acceptable propagation delay for this class of service.
.1.3.6.1.2.1.34.4.1.5.4.1.14,APPN-MIB::appnCosTgRowUsr1Min,INTEGER,read-only,,current,,Minimum acceptable value for this user-defined characteristic.
.1.3.6.1.2.1.34.4.1.5.4.1.15,APPN-MIB::appnCosTgRowUsr1Max,INTEGER,read-only,,current,,Maximum acceptable value for this user-defined characteristic.
.1.3.6.1.2.1.34.4.1.5.4.1.16,APPN-MIB::appnCosTgRowUsr2Min,INTEGER,read-only,,current,,Minimum acceptable value for this user-defined characteristic.
.1.3.6.1.2.1.34.4.1.5.4.1.17,APPN-MIB::appnCosTgRowUsr2Max,INTEGER,read-only,,current,,Maximum acceptable value for this user-defined characteristic.
.1.3.6.1.2.1.34.4.1.5.4.1.18,APPN-MIB::appnCosTgRowUsr3Min,INTEGER,read-only,,current,,Minimum acceptable value for this user-defined characteristic.
.1.3.6.1.2.1.34.4.1.5.4.1.19,APPN-MIB::appnCosTgRowUsr3Max,INTEGER,read-only,,current,,Maximum acceptable value for this user-defined characteristic.
.1.3.6.1.2.1.34.4.1.6,APPN-MIB::appnSessIntermediate,,,,,,
.1.3.6.1.2.1.34.4.1.6.1,APPN-MIB::appnIsInGlobal,,,,,,
.1.3.6.1.2.1.34.4.1.6.1.1,APPN-MIB::appnIsInGlobeCtrAdminStatus,INTEGER,read-write,,current,notActive(1):active(2):ready(3),Object by which a Management Station can deactivate or activate capture of intermediate-session counts and names, by setting the value to notActive(1) or active(2), respectively. The value ready(3) is returned on GET operations until a SET has been processed; after that the value received on the most recent SET is returned. The counts referred to here are the eight objects in the AppnIsInTable, from appnIsInP2SFmdPius through appnIsInS2PNonFmdBytes. The names are the four objects in this table, from appnIsInPriLuName through appnIsInCosName. Setting this object to the following values has the following effects: notActive(1) stop collecting count data. If a count is queried, it returns the value 0. Collection of names may, but need not be, disabled. active(2) start collecting count data. If it is supported, collection of names is enabled.
.1.3.6.1.2.1.34.4.1.6.1.2,APPN-MIB::appnIsInGlobeCtrOperStatus,INTEGER,read-only,,current,notActive(1):active(2),Indicates whether or not the intermediate session counts are active. The counts referred to here are the eight objects in the AppnIsInTable, from appnIsInP2SFmdPius through appnIsInS2PNonFmdBytes. These eight counts are of type Unsigned32 rather than Counter32 because when this object enters the notActive state, either because a Management Station has set appnInInGlobeCtrAdminStatus to notActive or because of a locally-initiated transition, the counts are all reset to 0. The values for this object are: notActive(1): collection of counts is not active; if it is queried, a count returns the value 0. active(2): collection of counts is active.
.1.3.6.1.2.1.34.4.1.6.1.3,APPN-MIB::appnIsInGlobeCtrStatusTime,TimeTicks,read-only,,current,,The time since the appnIsInGlobeCtrOperStatus object last changed, measured in hundredths of a second. This time can be used to identify when this change occurred in relation to other events in the agent, such as the last time the APPN node was reinitialized.
.1.3.6.1.2.1.34.4.1.6.1.4,APPN-MIB::appnIsInGlobeRscv,INTEGER,read-write,,current,notActive(1):active(2),Indicates the current route selection control vector (RSCV) collection option in effect, and allows a Management Station to change the option. The values for this object are: notActive(1): collection of route selection control vectors is not active. active(2): collection of route selection control vectors is active.
.1.3.6.1.2.1.34.4.1.6.1.5,APPN-MIB::appnIsInGlobeRscvTime,TimeTicks,read-only,,current,,The time since the appnIsInGlobeRscv object last changed, measured in hundredths of a second. This time can be used to identify when this change occurred in relation to other events in the agent, such as the last time the APPN node was reinitialized.
.1.3.6.1.2.1.34.4.1.6.1.6,APPN-MIB::appnIsInGlobeActSess,Gauge32,read-only,,current,,The number of currently active intermediate sessions.
.1.3.6.1.2.1.34.4.1.6.1.7,APPN-MIB::appnIsInGlobeHprBfActSess,Gauge32,read-only,,current,,The number of currently active HPR intermediate sessions.
.1.3.6.1.2.1.34.4.1.6.2,APPN-MIB::appnIsInTable,,not-accessible,,current,,Intermediate Session Information Table
.1.3.6.1.2.1.34.4.1.6.2.1,APPN-MIB::appnIsInEntry,,not-accessible,appnIsInFqCpName:appnIsInPcid,current,,Entry of Intermediate Session Information Table.
.1.3.6.1.2.1.34.4.1.6.2.1.1,APPN-MIB::appnIsInFqCpName,OCTET,not-accessible,,current,,The network-qualified control point name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. For resources served by a dependent LU requester (DLUR), it is the name of the owning system services control point (SSCP).
.1.3.6.1.2.1.34.4.1.6.2.1.2,APPN-MIB::appnIsInPcid,OCTET,not-accessible,,current,,The procedure correlation identifier (PCID) of a session. It is an 8-byte value assigned by the primary LU.
.1.3.6.1.2.1.34.4.1.6.2.1.3,APPN-MIB::appnIsInSessState,INTEGER,read-write,,current,inactive(1):pendactive(2):active(3):pendinact(4),Indicates the state of the session: inactive(1) - session is inactive pendactive(2) - session is pending active active(3) - session is active pendinact(4) - session is pending inactive Active sessions can be deactivated by setting this object to inactive(1).
.1.3.6.1.2.1.34.4.1.6.2.1.4,APPN-MIB::appnIsInPriLuName,OCTET,read-only,,current,,The primary LU name of the session. A zero-length string indicates that this name is not available.
.1.3.6.1.2.1.34.4.1.6.2.1.5,APPN-MIB::appnIsInSecLuName,OCTET,read-only,,current,,The secondary LU name of the session. A zero-length string indicates that this name is not available.
.1.3.6.1.2.1.34.4.1.6.2.1.6,APPN-MIB::appnIsInModeName,OCTET,read-only,,current,,The mode name used for this session.
.1.3.6.1.2.1.34.4.1.6.2.1.7,APPN-MIB::appnIsInCosName,OCTET,read-only,,current,,The Class of Service (COS) name used for this session.
.1.3.6.1.2.1.34.4.1.6.2.1.8,APPN-MIB::appnIsInTransPriority,INTEGER,read-only,,current,low(1):medium(2):high(3):network(4),Transmission priority for this class of service. Values are: low(1) - (X'01'): low priority medium(2) - (X'02'): medium priority high(3) - (X'03'): high priority network(4) - (X'04'): network priority
.1.3.6.1.2.1.34.4.1.6.2.1.9,APPN-MIB::appnIsInSessType,INTEGER,read-only,,current,unknown(1):lu62(2):lu0thru3(3):lu62dlur(4):lu0thru3dlur(5),The type of intermediate session. Defined values are unknown The session type is not known. lu62 A session between LUs of type 6.2 (as indicated by the LU type in Bind) lu0thru3 A session between LUs of type 0, 1, 2, or 3 (as indicated by the LU type in Bind) lu62dlur A session between LUs of type 6.2 (as indicated by the LU type in Bind). One of the LUs is a dependent LU supported by the dependent LU requester (DLUR) function at this node. lu0thru3dlur A session between LUs of type 0, 1, 2, or 3 (as indicated by the LU type in Bind) One of the LUs is a dependent LU supported by the dependent LU requester (DLUR) function at this node.
.1.3.6.1.2.1.34.4.1.6.2.1.10,APPN-MIB::appnIsInSessUpTime,TimeTicks,read-only,,current,,Length of time the session has been active, measured in hundredths of a second.
.1.3.6.1.2.1.34.4.1.6.2.1.11,APPN-MIB::appnIsInCtrUpTime,TimeTicks,read-only,,current,,Length of time the session counters have been active, measured in hundredths of a second.
.1.3.6.1.2.1.34.4.1.6.2.1.12,APPN-MIB::appnIsInP2SFmdPius,Unsigned32,read-only,,current,,Number of function management data (FMD) path information units (PIUs) sent from the Primary LU to the Secondary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.13,APPN-MIB::appnIsInS2PFmdPius,Unsigned32,read-only,,current,,Number of FMD PIUs sent from the Secondary LU to the Primary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.14,APPN-MIB::appnIsInP2SNonFmdPius,Unsigned32,read-only,,current,,Number of non-FMD PIUs sent from the Primary LU to the Secondary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.15,APPN-MIB::appnIsInS2PNonFmdPius,Unsigned32,read-only,,current,,Number of non-FMD PIUs sent from the Secondary LU to the Primary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.16,APPN-MIB::appnIsInP2SFmdBytes,Unsigned32,read-only,,current,,Number of FMD bytes sent from the Primary LU to the Secondary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.17,APPN-MIB::appnIsInS2PFmdBytes,Unsigned32,read-only,,current,,Number of FMD bytes sent from the Secondary LU to the Primary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.18,APPN-MIB::appnIsInP2SNonFmdBytes,Unsigned32,read-only,,current,,Number of non-FMD bytes sent from the Primary LU to the Secondary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.19,APPN-MIB::appnIsInS2PNonFmdBytes,Unsigned32,read-only,,current,,Number of non-FMD bytes sent from the Secondary LU to the Primary LU since the counts were last activated.
.1.3.6.1.2.1.34.4.1.6.2.1.20,APPN-MIB::appnIsInPsAdjCpName,OCTET,read-only,,current,,The primary stage adjacent CP name of this session. If the session stage traverses an RTP connection, the CP name of the remote RTP endpoint is returned.
.1.3.6.1.2.1.34.4.1.6.2.1.21,APPN-MIB::appnIsInPsAdjTgNum,INTEGER,read-only,,current,,The primary stage adjacent transmission group (TG) number associated with this session. If the session stage traverses an RTP connection, the value 256 is returned. Values between 257 and 300 are available for other possible TG 'stand-ins' that may be added to APPN in the future.
.1.3.6.1.2.1.34.4.1.6.2.1.22,APPN-MIB::appnIsInPsSendMaxBtuSize,INTEGER,read-only,,current,,The primary stage maximum basic transmission unit (BTU) size for sending data.
.1.3.6.1.2.1.34.4.1.6.2.1.23,APPN-MIB::appnIsInPsSendPacingType,INTEGER,read-only,,current,fixed(1):adaptive(2),The primary stage type of pacing being used for sending data.
.1.3.6.1.2.1.34.4.1.6.2.1.24,APPN-MIB::appnIsInPsSendRpc,Gauge32,read-only,,current,,The primary stage send residual pace count. This represents the primary stage number of message units (MUs) that can still be sent in the current session window.
.1.3.6.1.2.1.34.4.1.6.2.1.25,APPN-MIB::appnIsInPsSendNxWndwSize,Gauge32,read-only,,current,,The primary stage size of the next window which will be used to send data.
.1.3.6.1.2.1.34.4.1.6.2.1.26,APPN-MIB::appnIsInPsRecvPacingType,INTEGER,read-only,,current,fixed(1):adaptive(2),The primary stage type of pacing being used for receiving data.
.1.3.6.1.2.1.34.4.1.6.2.1.27,APPN-MIB::appnIsInPsRecvRpc,Gauge32,read-only,,current,,The primary stage receive residual pace count. This represents the primary stage number of message units (MUs) that can still be received in the current session window.
.1.3.6.1.2.1.34.4.1.6.2.1.28,APPN-MIB::appnIsInPsRecvNxWndwSize,Gauge32,read-only,,current,,The primary stage size of the next window which will be used to receive data.
.1.3.6.1.2.1.34.4.1.6.2.1.29,APPN-MIB::appnIsInSsAdjCpName,OCTET,read-only,,current,,The secondary stage adjacent CP name of this session. If the session stage traverses an RTP connection, the CP name of the remote RTP endpoint is returned.
.1.3.6.1.2.1.34.4.1.6.2.1.30,APPN-MIB::appnIsInSsAdjTgNum,INTEGER,read-only,,current,,The secondary stage adjacent transmission group (TG) number associated with this session. If the session stage traverses an RTP connection, the value 256 is returned. Values between 257 and 300 are available for other possible TG 'stand-ins' that may be added to APPN in the future.
.1.3.6.1.2.1.34.4.1.6.2.1.31,APPN-MIB::appnIsInSsSendMaxBtuSize,INTEGER,read-only,,current,,The secondary stage maximum basic transmission unit (BTU) size for sending data.
.1.3.6.1.2.1.34.4.1.6.2.1.32,APPN-MIB::appnIsInSsSendPacingType,INTEGER,read-only,,current,fixed(1):adaptive(2),The secondary stage type of pacing being used for sending data.
.1.3.6.1.2.1.34.4.1.6.2.1.33,APPN-MIB::appnIsInSsSendRpc,Gauge32,read-only,,current,,The secondary stage send residual pace count. This represents the secondary stage number of message units (MUs) that can still be sent in the current session window.
.1.3.6.1.2.1.34.4.1.6.2.1.34,APPN-MIB::appnIsInSsSendNxWndwSize,Gauge32,read-only,,current,,The secondary stage size of the next window which will be used to send data.
.1.3.6.1.2.1.34.4.1.6.2.1.35,APPN-MIB::appnIsInSsRecvPacingType,INTEGER,read-only,,current,fixed(1):adaptive(2),The secondary stage type of pacing being used for receiving data.
.1.3.6.1.2.1.34.4.1.6.2.1.36,APPN-MIB::appnIsInSsRecvRpc,Gauge32,read-only,,current,,The secondary stage receive residual pace count. This represents the secondary stage number of message units (MUs) that can still be received in the current session window.
.1.3.6.1.2.1.34.4.1.6.2.1.37,APPN-MIB::appnIsInSsRecvNxWndwSize,Gauge32,read-only,,current,,The secondary stage size of the next window which will be used to receive data.
.1.3.6.1.2.1.34.4.1.6.2.1.38,APPN-MIB::appnIsInRouteInfo,OCTET,read-only,,current,,The route selection control vector (RSCV X'2B') used for this session. It is present for APPN nodes; but is not present for LEN nodes. The format of this vector is described in SNA Formats. If no RSCV is available, a zero-length string is returned.
.1.3.6.1.2.1.34.4.1.6.2.1.39,APPN-MIB::appnIsInRtpNceId,OCTET,read-only,,current,,The HPR local Network Connection Endpoint of the session.
.1.3.6.1.2.1.34.4.1.6.2.1.40,APPN-MIB::appnIsInRtpTcid,OCTET,read-only,,current,,The RTP connection local TCID of the session.
.1.3.6.1.2.1.34.4.1.6.3,APPN-MIB::appnIsRtpTable,,not-accessible,,current,,A table indicating how many ISR sessions are transported by each RTP connection.
.1.3.6.1.2.1.34.4.1.6.3.1,APPN-MIB::appnIsRtpEntry,,not-accessible,appnIsRtpNceId:appnIsRtpTcid,current,,Entry of Intermediate Session RTP Table.
.1.3.6.1.2.1.34.4.1.6.3.1.1,APPN-MIB::appnIsRtpNceId,OCTET,not-accessible,,current,,The local Network Connection Endpoint of the RTP connection.
.1.3.6.1.2.1.34.4.1.6.3.1.2,APPN-MIB::appnIsRtpTcid,OCTET,not-accessible,,current,,The local TCID of the RTP connection.
.1.3.6.1.2.1.34.4.1.6.3.1.3,APPN-MIB::appnIsRtpSessions,Gauge32,read-only,,current,,The number of intermediate sessions using this RTP connection.
.1.3.6.1.2.1.34.4.1.7,APPN-TRAP-MIB::appnTrapObjects,,,,,,
.1.3.6.1.2.1.34.4.1.7.1,APPN-TRAP-MIB::appnTrapControl,BITS,read-write,,current,appnLocalTgOperStateChangeTrap(0):appnLocalTgCpCpChangeTrap(1):appnPortOperStateChangeTrap(2):appnLsOperStateChangeTrap(3):dlurDlusStateChangeTrap(4),An object to turn APPN notification generation on and off. Setting a notification type's bit to 1 enables generation of notifications of that type, subject to further filtering resulting from entries in the snmpNotificationMIB. Setting this bit to 0 disables generation of notifications of that type. Note that generation of the appnIsrAccountingDataTrap is controlled by the appnIsInGlobeCtrAdminStatus object in the APPN MIB: if counts of intermediate session traffic are being kept at all, then the notification is also enabled.
.1.3.6.1.2.1.34.4.1.7.2,APPN-TRAP-MIB::appnLocalTgTableChanges,Counter32,read-only,,current,,A count of the number of times a row in the appnLocalTgTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnLocalTgOperStateChangeTrap or appnLocalTgCpCpChangeTrap notification to be sent, whether or not those notifications are enabled.
.1.3.6.1.2.1.34.4.1.7.3,APPN-TRAP-MIB::appnPortTableChanges,Counter32,read-only,,current,,A count of the number of times a row in the appnPortTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnPortOperStateChangeTrap notification to be sent, whether or not this notification is enabled.
.1.3.6.1.2.1.34.4.1.7.4,APPN-TRAP-MIB::appnLsTableChanges,Counter32,read-only,,current,,A count of the number of times a row in the appnLsTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnLsOperStateChangeTrap notification to be sent, whether or not this notification is enabled.
.1.3.6.1.2.1.34.4.1.7.5,APPN-TRAP-MIB::dlurDlusTableChanges,Counter32,read-only,,current,,A count of the number of times a row in the dlurDlusTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a dlurDlusStateChangeTrap notification to be sent, whether or not this notification is enabled.
.1.3.6.1.2.1.34.4.2,APPN-MIB::appnTraps,,,,,,
.1.3.6.1.2.1.34.4.2.1,APPN-MIB::alertTrap,,,,,,This trap carries a 32-bit SNA Management Services (SNA/MS) Alert ID Number, as specified in SNA/MS Formats.
.1.3.6.1.2.1.34.4.2.2,APPN-MIB::alertIdNumber,OCTET,accessible-for-notify,,current,,A 32-bit SNA Management Services (SNA/MS) Alert ID Number, as specified in SNA/MS Formats.
.1.3.6.1.2.1.34.4.2.3,APPN-MIB::affectedObject,OBJECT,accessible-for-notify,,current,,The MIB object associated with the Alert condition, if there is an object associated with it. If no associated object can be identified, the value 0.0 is passed in the trap.
.1.3.6.1.2.1.34.4.3,APPN-MIB::appnConformance,,,,,,
.1.3.6.1.2.1.34.4.3.1,APPN-MIB::appnCompliances,,,,,,
.1.3.6.1.2.1.34.4.3.1.1,APPN-MIB::appnCompliance,,,,,,The compliance statement for the SNMPv2 entities that implement the APPN MIB. This is the compliance statement for the RFC 2155-level version of the APPN MIB. It was deprecated as new objects were added to the MIB for MLTG, branch network node, and other extensions to the APPN architecture.
.1.3.6.1.2.1.34.4.3.1.2,APPN-TRAP-MIB::appnTrapMibCompliance,,,,,,The compliance statement for the SNMP entities that implement the APPN-TRAP-MIB.
.1.3.6.1.2.1.34.4.3.1.3,APPN-MIB::appnCompliance2,,,,,,The compliance statement for the SNMPv2 entities that implement the APPN MIB. In the descriptions for the conditionally mandatory groups that follow, the branch network node is treated as a third node type, parallel to network node and end node. This is not how branch network nodes are treated in the base APPN architecture, but it increases clarity here to do it.
.1.3.6.1.2.1.34.4.3.2,APPN-MIB::appnGroups,,,,,,
.1.3.6.1.2.1.34.4.3.2.1,APPN-MIB::appnGeneralConfGroup,,,,,,A collection of objects providing the instrumentation of APPN general information and capabilities. This RFC 2155-level group was deprecated when the appnNodeMibVersion object was removed and the appnNodeLsCounterType and appnNodeBrNn objects were added.
.1.3.6.1.2.1.34.4.3.2.2,APPN-MIB::appnPortConfGroup,,,,,,A collection of objects providing the instrumentation of APPN port information.
.1.3.6.1.2.1.34.4.3.2.3,APPN-MIB::appnLinkConfGroup,,,,,,A collection of objects providing the instrumentation of APPN link information. This RFC 2155-level group was deprecated when the appnLsMltgMember object was added.
.1.3.6.1.2.1.34.4.3.2.4,APPN-MIB::appnLocalTgConfGroup,,,,,,A collection of objects providing the instrumentation of APPN local TG information. This RFC 2155-level group was deprecated when the appnLocalTgMltgLinkType object was added.
.1.3.6.1.2.1.34.4.3.2.5,APPN-MIB::appnDirTableConfGroup,,,,,,A collection of objects providing the instrumentation of the APPN directory database. This RFC 2155-level group was deprecated when the appnDirApparentLuOwnerName object was added.
.1.3.6.1.2.1.34.4.3.2.6,APPN-MIB::appnNnUniqueConfGroup,,,,,,A collection of objects providing instrumentation unique to APPN network nodes.
.1.3.6.1.2.1.34.4.3.2.7,APPN-MIB::appnEnUniqueConfGroup,,,,,,A collection of objects providing instrumentation for APPN end nodes. Some of these objects also appear in the instrumentation for a branch network node.
.1.3.6.1.2.1.34.4.3.2.8,APPN-MIB::appnVrnConfGroup,,,,,,An object providing the instrumentation for virtual routing node support in an APPN node.
.1.3.6.1.2.1.34.4.3.2.9,APPN-MIB::appnNnTopoConfGroup,,,,,,The appnNnTopoConfGroup is mandatory only for network nodes. This RFC 2155-level group was deprecated when the appnNnNodeFRBranchAwareness, appnNnTgFRMltgLinkType, and appnNnFRBranchTg objects were added.
.1.3.6.1.2.1.34.4.3.2.10,APPN-MIB::appnLocalEnTopoConfGroup,,,,,,The appnLocalEnTopoConfGroup is mandatory only for network nodes. This RFC 2155-level group was deprecated when the appnLocalEnTgMltgLinkType object was added.
.1.3.6.1.2.1.34.4.3.2.11,APPN-MIB::appnLocalDirPerfConfGroup,,,,,,The appnLocalDirPerfConfGroup is mandatory only for APPN network nodes and end nodes.
.1.3.6.1.2.1.34.4.3.2.12,APPN-MIB::appnCosConfGroup,,,,,,The appnCosConfGroup is mandatory only for APPN network nodes and end nodes.
.1.3.6.1.2.1.34.4.3.2.13,APPN-MIB::appnIntSessConfGroup,,,,,,The appnIntSessConfGroup is mandatory only for network nodes.
.1.3.6.1.2.1.34.4.3.2.14,APPN-MIB::appnHprBaseConfGroup,,,,,,The appnHprBaseConfGroup is mandatory only for nodes that implement the HPR base (APPN option set 1400).
.1.3.6.1.2.1.34.4.3.2.15,APPN-MIB::appnHprRtpConfGroup,,,,,,The appnHprRtpConfGroup is mandatory only for nodes that implement the HPR RTP tower (APPN option set 1401).
.1.3.6.1.2.1.34.4.3.2.16,APPN-MIB::appnHprCtrlFlowsRtpConfGroup,,,,,,The appnHprCtrlFlowsRtpConfGroup is mandatory only for nodes that implement the HPR Control Flows over RTP tower (APPN option set 1402).
.1.3.6.1.2.1.34.4.3.2.17,APPN-MIB::appnHprBfConfGroup,,,,,,The appnHprBfConfGroup is mandatory only for nodes that implement the APPN/HPR boundary function.
.1.3.6.1.2.1.34.4.3.2.18,APPN-MIB::appnTrapConfGroup,,,,,,The appnTrapConfGroup is optional for all APPN nodes. Nodes implementing this group shall also implement the appnTrapNotifGroup.
.1.3.6.1.2.1.34.4.3.2.19,APPN-MIB::appnTrapNotifGroup,,,,,,The appnTrapNotifGroup is optional for all APPN nodes. Nodes implementing this group shall also implement the appnTrapConfGroup.
.1.3.6.1.2.1.34.4.3.2.20,APPN-MIB::appnBrNnConfGroup,,,,,,A collection of objects providing instrumentation for branch network nodes. Some of these objects also appear in the instrumentation for an end node. Note: A branch network node always returns endNode(2) as the value of the appnNodeType object from the appnGeneralConfGroup2 conformance group.
.1.3.6.1.2.1.34.4.3.2.21,APPN-TRAP-MIB::appnTrapMibIsrNotifGroup,,,,,,A notification for reporting the final values of the APPN MIB's ISR counters.
.1.3.6.1.2.1.34.4.3.2.22,APPN-TRAP-MIB::appnTrapMibTopoConfGroup,,,,,,A collection of objects for reducing the polling associated with the local topology tables in the APPN MIB. Nodes that implement this group SHALL also implement the appnTrapMibTopoNotifGroup.
.1.3.6.1.2.1.34.4.3.2.23,APPN-TRAP-MIB::appnTrapMibTopoNotifGroup,,,,,,A collection of notifications for reducing the polling associated with the local topology tables in the APPN MIB. Nodes that implement this group SHALL also implement the appnTrapMibTopoConfGroup.
.1.3.6.1.2.1.34.4.3.2.24,APPN-TRAP-MIB::appnTrapMibDlurConfGroup,,,,,,A collection of objects for reducing the polling associated with the dlurDlusTable in the DLUR MIB. Nodes that implement this group SHALL also implement the appnTrapMibDlurNotifGroup.
.1.3.6.1.2.1.34.4.3.2.25,APPN-TRAP-MIB::appnTrapMibDlurNotifGroup,,,,,,A notification for reducing the polling associated with the dlurDlusTable in the DLUR MIB. Nodes that implement this group SHALL also implement the appnTrapMibDlurConfGroup.
.1.3.6.1.2.1.34.4.3.2.26,APPN-MIB::appnGeneralConfGroup2,,,,,,A collection of objects providing the instrumentation of APPN general information and capabilities.
.1.3.6.1.2.1.34.4.3.2.27,APPN-MIB::appnLinkConfGroup2,,,,,,A collection of objects providing the instrumentation of APPN link information.
.1.3.6.1.2.1.34.4.3.2.28,APPN-MIB::appnLocalTgConfGroup2,,,,,,A collection of objects providing the instrumentation of APPN local TG information.
.1.3.6.1.2.1.34.4.3.2.29,APPN-MIB::appnDirTableConfGroup2,,,,,,A collection of objects providing the instrumentation of the APPN directory database.
.1.3.6.1.2.1.34.4.3.2.30,APPN-MIB::appnNnTopoConfGroup2,,,,,,The appnNnTopoConfGroup is mandatory only for network nodes.
.1.3.6.1.2.1.34.4.3.2.31,APPN-MIB::appnLocalEnTopoConfGroup2,,,,,,A collection of objects providing the instrumentation of the information that a network node possesses about the end nodes directly attached to it.
.1.3.6.1.2.1.34.5,APPN-DLUR-MIB::dlurMIB,,,,,,This is the MIB module for objects used to manage network devices with DLUR capabilities. This MIB contains information that is useful for managing an APPN product that implements a DLUR (Dependent Logical Unit Requester). The DLUR product has a client/server relationship with an APPN product that implements a DLUS (Dependent Logical Unit Server).
.1.3.6.1.2.1.34.5.1,APPN-DLUR-MIB::dlurObjects,,,,,,
.1.3.6.1.2.1.34.5.1.1,APPN-DLUR-MIB::dlurNodeInfo,,,,,,
.1.3.6.1.2.1.34.5.1.1.1,APPN-DLUR-MIB::dlurNodeCapabilities,,,,,,
.1.3.6.1.2.1.34.5.1.1.1.1,APPN-DLUR-MIB::dlurNodeCpName,OCTET,read-only,,current,,Administratively assigned network name for the APPN node where this DLUR implementation resides. If this object has the same value as the appnNodeCpName object in the APPN MIB, then the two objects are referring to the same APPN node.
.1.3.6.1.2.1.34.5.1.1.1.2,APPN-DLUR-MIB::dlurReleaseLevel,OCTET,read-only,,current,,The DLUR release level of this implementation. This is the value that is encoded in the DLUR/DLUS Capabilites (CV 51). To insure consistent display, this one-byte value is encoded here as two displayable characters that are equivalent to a hexadecimal display. For example, if the one-byte value as encoded in CV51 is X'01', this object will contain the displayable string '01'.
.1.3.6.1.2.1.34.5.1.1.1.3,APPN-DLUR-MIB::dlurAnsSupport,INTEGER,read-only,,current,continueOrStop(1):stopOnly(2),Automatic Network Shutdown (ANS) capability of this node. - 'continueOrStop' indicates that the DLUR implementation supports either ANS value (continue or stop) as specified by the DLUS on ACTPU for each PU. - 'stopOnly' indicates that the DLUR implementation only supports the ANS value of stop. ANS = continue means that the DLUR node will keep LU-LU sessions active even if SSCP-PU and SSCP-LU control sessions are interrupted. ANS = stop means that LU-LU sessions will be interrupted when the SSCP-PU and SSCP-LU sessions are interrupted.
.1.3.6.1.2.1.34.5.1.1.1.4,APPN-DLUR-MIB::dlurMultiSubnetSupport,INTEGER,read-only,,current,true(1):false(2),Indication of whether this DLUR implementation can support CPSVRMGR sessions that cross NetId boundaries.
.1.3.6.1.2.1.34.5.1.1.1.5,APPN-DLUR-MIB::dlurDefaultDefPrimDlusName,OCTET,read-only,,current,,The SNA name of the defined default primary DLUS for all of the PUs served by this DLUR. This can be overridden for a particular PU by a defined primary DLUS for that PU, represented by the dlurPuDefPrimDlusName object.
.1.3.6.1.2.1.34.5.1.1.1.6,APPN-DLUR-MIB::dlurNetworkNameForwardingSupport,INTEGER,read-only,,current,true(1):false(2),Indication of whether this DLUR implementation supports forwarding of Network Name control vectors on ACTPUs and ACTLUs to DLUR-served PUs and their associated LUs. This object corresponds to byte 9. bit 3 of cv51.
.1.3.6.1.2.1.34.5.1.1.1.7,APPN-DLUR-MIB::dlurNondisDlusDlurSessDeactSup,INTEGER,read-only,,current,true(1):false(2),Indication of whether this DLUR implementation supports nondisruptive deactivation of its DLUR-DLUS sessions. Upon receiving from a DLUS an UNBIND for the CPSVRMGR pipe with sense data X'08A0 000B', a DLUR that supports this option immediately begins attempting to activate a CPSVRMGR pipe with a DLUS other than the one that sent the UNBIND. This object corresponds to byte 9. bit 4 of cv51.
.1.3.6.1.2.1.34.5.1.1.2,APPN-DLUR-MIB::dlurDefaultDefBackupDlusTable,,not-accessible,,current,,This table contains an ordered list of defined backup DLUSs for all of the PUs served by this DLUR. These can be overridden for a particular PU by a list of defined backup DLUSs for that PU, represented by the dlurPuDefBackupDlusNameTable. Entries in this table are ordered from most preferred default backup DLUS to least preferred.
.1.3.6.1.2.1.34.5.1.1.2.1,APPN-DLUR-MIB::dlurDefaultDefBackupDlusEntry,,not-accessible,dlurDefaultDefBackupDlusIndex,current,,This table is indexed by an integer-valued index, which orders the entries from most preferred default backup DLUS to least preferred.
.1.3.6.1.2.1.34.5.1.1.2.1.1,APPN-DLUR-MIB::dlurDefaultDefBackupDlusIndex,Unsigned32,not-accessible,,current,,Index for this table. The index values start at 1, which identifies the most preferred default backup DLUS.
.1.3.6.1.2.1.34.5.1.1.2.1.2,APPN-DLUR-MIB::dlurDefaultDefBackupDlusName,OCTET,read-only,,current,,Fully qualified name of a default backup DLUS for PUs served by this DLUR.
.1.3.6.1.2.1.34.5.1.2,APPN-DLUR-MIB::dlurPuInfo,,,,,,
.1.3.6.1.2.1.34.5.1.2.1,APPN-DLUR-MIB::dlurPuTable,,not-accessible,,current,,Information about the PUs supported by this DLUR.
.1.3.6.1.2.1.34.5.1.2.1.1,APPN-DLUR-MIB::dlurPuEntry,,not-accessible,dlurPuName,current,,Entry in a table of PU information, indexed by PU name.
.1.3.6.1.2.1.34.5.1.2.1.1.1,APPN-DLUR-MIB::dlurPuName,OCTET,not-accessible,,current,,Locally administered name of the PU.
.1.3.6.1.2.1.34.5.1.2.1.1.2,APPN-DLUR-MIB::dlurPuSscpSuppliedName,OCTET,read-only,,current,,The SNA name of the PU. This value is supplied to a PU by the SSCP that activated it. If a value has not been supplied, a zero-length string is returned.
.1.3.6.1.2.1.34.5.1.2.1.1.3,APPN-DLUR-MIB::dlurPuStatus,INTEGER,read-only,,current,reset(1):pendReqActpuRsp(2):pendActpu(3):pendActpuRsp(4):active(5):pendLinkact(6):pendDactpuRsp(7):pendInop(8):pendInopActpu(9),Status of the DLUR-supported PU. The following values are defined: reset(1) - reset pendReqActpuRsp(2) - pending a response from the DLUS to a Request ACTPU pendActpu(3) - pending an ACTPU from the DLUS pendActpuRsp(4) - pending an ACTPU response from the PU active(5) - active pendLinkact(6) - pending activation of the link to a downstream PU pendDactpuRsp(7) - pending a DACTPU response from the PU pendInop(8) - the CPSVRMGR pipe became inoperative while the DLUR was pending an ACTPU response from the PU pendInopActpu(9) - when the DLUR was in the pendInop state, a CPSVRMGR pipe became active and a new ACTPU was received over it, before a response to the previous ACTPU was received from the PU.
.1.3.6.1.2.1.34.5.1.2.1.1.4,APPN-DLUR-MIB::dlurPuAnsSupport,INTEGER,read-only,,current,continue(1):stop(2),The Automatic Network Shutdown (ANS) support configured for this PU. This value (as configured by the network administrator) is sent by DLUS with ACTPU for each PU. - 'continue' means that the DLUR node will attempt to keep LU-LU sessions active even if SSCP-PU and SSCP-LU control sessions are interrupted. - 'stop' means that LU-LU sessions will be interrupted when the SSCP-PU and SSCP-LU sessions are interrupted.
.1.3.6.1.2.1.34.5.1.2.1.1.5,APPN-DLUR-MIB::dlurPuLocation,INTEGER,read-only,,current,internal(1):downstream(2),Location of the DLUR-support PU: internal(1) - internal to the APPN node itself (no link) downstream(2) - downstream of the APPN node (connected via a link).
.1.3.6.1.2.1.34.5.1.2.1.1.6,APPN-DLUR-MIB::dlurPuLsName,OCTET,read-only,,current,,Administratively assigned name of the link station through which a downstream PU is connected to this DLUR. A zero-length string is returned for internal PUs. If this object has the same value as the appnLsName object in the APPN MIB, then the two are identifying the same link station.
.1.3.6.1.2.1.34.5.1.2.1.1.7,APPN-DLUR-MIB::dlurPuDlusSessnStatus,INTEGER,read-only,,current,reset(1):pendingActive(2):active(3):pendingInactive(4),Status of the control session to the DLUS identified in dlurPuActiveDlusName. This is a combination of the separate states for the contention-winner and contention-loser sessions: reset(1) - none of the cases below pendingActive(2) - either contention-winner session or contention-loser session is pending active active(3) - contention-winner and contention-loser sessions are both active pendingInactive(4) - either contention-winner session or contention-loser session is pending inactive - this test is made AFTER the 'pendingActive' test. The following matrix provides a different representation of how the values of this object are related to the individual states of the contention-winner and contention-loser sessions: Conwinner | pA | pI | A | X = !(pA | pI | A) C ++++++++++++++++++++++++++++++++++ o pA | 2 | 2 | 2 | 2 n ++++++++++++++++++++++++++++++++++ l pI | 2 | 4 | 4 | 4 o ++++++++++++++++++++++++++++++++++ s A | 2 | 4 | 3 | 1 e ++++++++++++++++++++++++++++++++++ r X | 2 | 4 | 1 | 1 ++++++++++++++++++++++++++++++++++ 
.1.3.6.1.2.1.34.5.1.2.1.1.8,APPN-DLUR-MIB::dlurPuActiveDlusName,OCTET,read-only,,current,,The SNA name of the active DLUS for this PU. If its length is not zero, this name follows the SnaControlPointName textual convention. A zero-length string indicates that the PU does not currently have an active DLUS.
.1.3.6.1.2.1.34.5.1.2.1.1.9,APPN-DLUR-MIB::dlurPuDefPrimDlusName,OCTET,read-only,,current,,The SNA name of the defined primary DLUS for this PU, if one has been defined. If present, this name follows the SnaControlPointName textual convention. A zero-length string indicates that no primary DLUS has been defined for this PU, in which case the global default represented by the dlurDefaultDefPrimDlusName object is used.
.1.3.6.1.2.1.34.5.1.2.2,APPN-DLUR-MIB::dlurPuDefBackupDlusTable,,not-accessible,,current,,This table contains an ordered list of defined backup DLUSs for those PUs served by this DLUR that have their own defined backup DLUSs. PUs that have no entries in this table use the global default backup DLUSs for the DLUR, represented by the dlurDefaultDefBackupDlusNameTable. Entries in this table are ordered from most preferred backup DLUS to least preferred for each PU.
.1.3.6.1.2.1.34.5.1.2.2.1,APPN-DLUR-MIB::dlurPuDefBackupDlusEntry,,not-accessible,dlurPuDefBackupDlusPuName:dlurPuDefBackupDlusIndex,current,,This table is indexed by PU name and by an integer-valued index, which orders the entries from most preferred backup DLUS for the PU to least preferred.
.1.3.6.1.2.1.34.5.1.2.2.1.1,APPN-DLUR-MIB::dlurPuDefBackupDlusPuName,OCTET,not-accessible,,current,,Locally administered name of the PU. If this object has the same value as the dlurPuName object, then the two are identifying the same PU.
.1.3.6.1.2.1.34.5.1.2.2.1.2,APPN-DLUR-MIB::dlurPuDefBackupDlusIndex,Unsigned32,not-accessible,,current,,Secondary index for this table. The index values start at 1, which identifies the most preferred backup DLUS for the PU.
.1.3.6.1.2.1.34.5.1.2.2.1.3,APPN-DLUR-MIB::dlurPuDefBackupDlusName,OCTET,read-only,,current,,Fully qualified name of a backup DLUS for this PU.
.1.3.6.1.2.1.34.5.1.3,APPN-DLUR-MIB::dlurDlusInfo,,,,,,
.1.3.6.1.2.1.34.5.1.3.1,APPN-DLUR-MIB::dlurDlusTable,,not-accessible,,current,,Information about DLUS control sessions.
.1.3.6.1.2.1.34.5.1.3.1.1,APPN-DLUR-MIB::dlurDlusEntry,,not-accessible,dlurDlusName,current,,This entry is indexed by the name of the DLUS.
.1.3.6.1.2.1.34.5.1.3.1.1.1,APPN-DLUR-MIB::dlurDlusName,OCTET,not-accessible,,current,,The SNA name of a DLUS with which this DLUR currently has a CPSVRMGR pipe established.
.1.3.6.1.2.1.34.5.1.3.1.1.2,APPN-DLUR-MIB::dlurDlusSessnStatus,INTEGER,read-only,,current,reset(1):pendingActive(2):active(3):pendingInactive(4),Status of the CPSVRMGR pipe between the DLUR and this DLUS. This is a combination of the separate states for the contention-winner and contention-loser sessions: reset(1) - none of the cases below pendingActive(2) - either contention-winner session or contention-loser session is pending active active(3) - contention-winner and contention-loser sessions are both active pendingInactive(4) - either contention-winner session or contention-loser session is pending inactive - this test is made AFTER the 'pendingActive' test. The following matrix provides a different representation of how the values of this object are related to the individual states of the contention-winner and contention-loser sessions: Conwinner | pA | pI | A | X = !(pA | pI | A) C ++++++++++++++++++++++++++++++++++ o pA | 2 | 2 | 2 | 2 n ++++++++++++++++++++++++++++++++++ l pI | 2 | 4 | 4 | 4 o ++++++++++++++++++++++++++++++++++ s A | 2 | 4 | 3 | 1 e ++++++++++++++++++++++++++++++++++ r X | 2 | 4 | 1 | 1 ++++++++++++++++++++++++++++++++++ 
.1.3.6.1.2.1.34.5.2,APPN-DLUR-MIB::dlurConformance,,,,,,
.1.3.6.1.2.1.34.5.2.1,APPN-DLUR-MIB::dlurCompliances,,,,,,
.1.3.6.1.2.1.34.5.2.1.1,APPN-DLUR-MIB::dlurCompliance,,,,,,The compliance statement for the SNMPv2 entities which implement the DLUR MIB.
.1.3.6.1.2.1.34.5.2.2,APPN-DLUR-MIB::dlurGroups,,,,,,
.1.3.6.1.2.1.34.5.2.2.1,APPN-DLUR-MIB::dlurConfGroup,,,,,,A collection of objects providing information on an implementation of APPN DLUR.
.1.3.6.1.2.1.34.6,HPR-MIB::hprMIB,,,,,,This is the MIB module for objects used to manage network devices with HPR capabilities.
.1.3.6.1.2.1.34.6.1,HPR-MIB::hprObjects,,,,,,
.1.3.6.1.2.1.34.6.1.1,HPR-MIB::hprGlobal,,,,,,
.1.3.6.1.2.1.34.6.1.1.1,HPR-MIB::hprNodeCpName,OCTET,read-only,,current,,Administratively assigned network name for the APPN node where this HPR implementation resides. If this object has the same value as the appnNodeCpName object in the APPN MIB, then the two objects are referring to the same APPN node.
.1.3.6.1.2.1.34.6.1.1.2,HPR-MIB::hprOperatorPathSwitchSupport,INTEGER,read-only,,current,notSupported(1):switchTriggerSupported(2):switchToPathSupported(3),This object indicates an implementation's level of support for an operator-requested path switch. notSupported(1) - the agent does not support operator-requested path switches switchTriggerSupported(2) - the agent supports a 'switch path now' command from an operator, but not a command to switch to a specified path switchToPathSupported(3) - the agent supports both a 'switch path now' command and a command to switch to a specified path. Note that the latter command is not available via this MIB; a system that supports it must do so via other means, such as a local operator interface.
.1.3.6.1.2.1.34.6.1.2,HPR-MIB::hprAnrRouting,,,,,,
.1.3.6.1.2.1.34.6.1.2.1,HPR-MIB::hprAnrsAssigned,Counter32,read-only,,current,,The count of ANR labels assigned by this node since it was last re-initialized. A Management Station can detect discontinuities in this counter by monitoring the appnNodeCounterDisconTime object in the APPN MIB.
.1.3.6.1.2.1.34.6.1.2.2,HPR-MIB::hprAnrCounterState,INTEGER,read-write,,current,notActive(1):active(2),This object is used for a network management station to turn on/off the counting of ANR packets in the hprAnrRoutingTable. The initial value of this object is an implementation choice. notActive(1) - the counter hprAnrPacketsReceived returns no meaningful value active(2) - the counter hprAnrPacketsReceived is being incremented and is returning meaningful values
.1.3.6.1.2.1.34.6.1.2.3,HPR-MIB::hprAnrCounterStateTime,OCTET,read-only,,current,,The time when the hprAnrCounterState object last changed its value. The initial value returned by this object is the time at which the APPN node instrumented with this MIB was last brought up.
.1.3.6.1.2.1.34.6.1.2.4,HPR-MIB::hprAnrRoutingTable,,not-accessible,,current,,The ANR Routing table provides a means of correlating an incoming ANR label (i.e., one assigned by this node) with the TG over which a packet containing the label will be forwarded. When the ANR label identifies a local NCE, the hprAnrOutTgDest and hprAnrOutTgNum objects have no meaning. The table also contains an object to count the number of packets received with a given ANR label.
.1.3.6.1.2.1.34.6.1.2.4.1,HPR-MIB::hprAnrRoutingEntry,,not-accessible,hprAnrLabel,current,,The ANR label is used to index this table.
.1.3.6.1.2.1.34.6.1.2.4.1.1,HPR-MIB::hprAnrLabel,OCTET,not-accessible,,current,,The first ANR label in an incoming packet.
.1.3.6.1.2.1.34.6.1.2.4.1.2,HPR-MIB::hprAnrType,INTEGER,read-only,,current,nce(1):tg(2),An object indicating whether an ANR label assigned by this node identifies a local NCE or a TG on which outgoing packets are forwarded. nce(1) - the ANR label identifies a local NCE. In this case the hprAnrOutTgDest and hprAnrOutTgNum objects have no meaning. tg(2) - the ANR label identifies a TG.
.1.3.6.1.2.1.34.6.1.2.4.1.3,HPR-MIB::hprAnrOutTgDest,OCTET,read-only,,current,,Destination node for the TG over which packets with this ANR label are forwarded. This is the fully qualified name of an APPN network node or end node, formatted according to the SnaControlPointName textual convention. If the ANR label identifies a local NCE, then this object returns a zero-length string. This object corresponds to the appnLocalTgDest object in the APPN MIB.
.1.3.6.1.2.1.34.6.1.2.4.1.4,HPR-MIB::hprAnrOutTgNum,INTEGER,read-only,,current,,Number of the TG over which packets with this ANR label are forwarded. If the ANR label identifies a local NCE, then this object returns the value 0, since 0 is not a valid TG number for a TG that supports HPR. This object corresponds to the appnLocalTgNum object in the APPN MIB.
.1.3.6.1.2.1.34.6.1.2.4.1.5,HPR-MIB::hprAnrPacketsReceived,Counter32,read-only,,current,,The count of packets received with this ANR label as their first label. A Management Station can detect discontinuities in this counter by monitoring the hprAnrCounterDisconTime object in the same row.
.1.3.6.1.2.1.34.6.1.2.4.1.6,HPR-MIB::hprAnrCounterDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the hprAnrPacketsReceived counter for this ANR label last experienced a discontinuity. This will be the more recent of two times: the time at which the ANR label was associated with either an outgoing TG or a local NCE, or the time at which the ANR counters were last turned on or off.
.1.3.6.1.2.1.34.6.1.3,HPR-MIB::hprTransportUser,,,,,,
.1.3.6.1.2.1.34.6.1.3.1,HPR-MIB::hprNceTable,,not-accessible,,current,,The Network Connection Endpoint (NCE) table.
.1.3.6.1.2.1.34.6.1.3.1.1,HPR-MIB::hprNceEntry,,not-accessible,hprNceId,current,,The NCE ID is used to index this table.
.1.3.6.1.2.1.34.6.1.3.1.1.1,HPR-MIB::hprNceId,OCTET,not-accessible,,current,,The Network Connection Endpoint (NCE) ID. NCEs identify Control Points (Cp), Logical Units (Lu), HPR Boundary Functions (Bf) and Route Setup (Rs) Functions. A value for this object can be retrieved from any of the following objects in the APPN MIB: - appnLsCpCpNceId - appnLsRouteNceId - appnLsBfNceId - appnIsInRtpNceId - appnIsRtpNceId In each case this value identifies a row in this table containing information related to that in the APPN MIB.
.1.3.6.1.2.1.34.6.1.3.1.1.2,HPR-MIB::hprNceType,BITS,read-only,,current,controlPoint(0):logicalUnit(1):boundaryFunction(2):routeSetup(3),A bit string identifying the function types provided by this Network Connection Endpoint (NCE).
.1.3.6.1.2.1.34.6.1.3.1.1.3,HPR-MIB::hprNceDefault,BITS,read-only,,current,controlPoint(0):logicalUnit(1):boundaryFunction(2):routeSetup(3),A bit string identifying the function types for which this Network Connection Endpoint (NCE) is the default NCE. While default NCEs are not explicitly defined in the architecture, some implementations provide them; for such implementations, it is useful to make this information available to a Management Station.
.1.3.6.1.2.1.34.6.1.3.1.1.4,HPR-MIB::hprNceInstanceId,OCTET,read-only,,current,,The NCE instance identifier (NCEII) identifying the current instance of this NCE. An NCEII is used to denote different instances (IPLs) of an NCE component. Each time an NCE is activated (IPL'd), it acquires a different, unique NCEII.
.1.3.6.1.2.1.34.6.1.4,HPR-MIB::hprRtp,,,,,,
.1.3.6.1.2.1.34.6.1.4.1,HPR-MIB::hprRtpGlobe,,,,,,
.1.3.6.1.2.1.34.6.1.4.1.1,HPR-MIB::hprRtpGlobeConnSetups,Counter32,read-only,,current,,The count of RTP connection setups in which this node has participated, as either sender or receiver, since it was last re-initialized. Retries of a setup attempt do not cause the counter to be incremented. A Management Station can detect discontinuities in this counter by monitoring the appnNodeCounterDisconTime object in the APPN MIB.
.1.3.6.1.2.1.34.6.1.4.1.2,HPR-MIB::hprRtpGlobeCtrState,INTEGER,read-write,,current,notActive(1):active(2),This object allows a network management station to turn the counters in the hprRtpTable on and off. The initial value of this object is an implementation choice. notActive(1) - the counters in the hprRtpTable are returning no meaningful values active(2) - the counters in the hprRtpTable are being incremented and are returning meaningful values
.1.3.6.1.2.1.34.6.1.4.1.3,HPR-MIB::hprRtpGlobeCtrStateTime,OCTET,read-only,,current,,The time when the value of the hprRtpGlobeCtrState object last changed. The initial value returned by this object is the time at which the APPN node instrumented with this MIB was last brought up.
.1.3.6.1.2.1.34.6.1.4.2,HPR-MIB::hprRtpTable,,not-accessible,,current,,The RTP Connection table
.1.3.6.1.2.1.34.6.1.4.2.1,HPR-MIB::hprRtpEntry,,not-accessible,hprRtpLocNceId:hprRtpLocTcid,current,,The local NCE ID and local TCID are used to index this table.
.1.3.6.1.2.1.34.6.1.4.2.1.1,HPR-MIB::hprRtpLocNceId,OCTET,not-accessible,,current,,The local Network Connection Endpoint (NCE) ID of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components. A value for this object can be retrieved from any of the following objects in the APPN MIB: - appnLsCpCpNceId - appnLsRouteNceId - appnLsBfNceId - appnIsInRtpNceId - appnIsRtpNceId In each case this value identifies a row in this table containing information related to that in the APPN MIB.
.1.3.6.1.2.1.34.6.1.4.2.1.2,HPR-MIB::hprRtpLocTcid,OCTET,not-accessible,,current,,The local TCID of this RTP connection. A value for this object can be retrieved from either the appnIsInRtpTcid object or the appnIsRtpTcid object the APPN MIB; in each case this value identifies a row in this table containing information related to that in the APPN MIB.
.1.3.6.1.2.1.34.6.1.4.2.1.3,HPR-MIB::hprRtpRemCpName,OCTET,read-only,,current,,Administratively assigned network name for the remote node of this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.4,HPR-MIB::hprRtpRemNceId,OCTET,read-only,,current,,The remote Network Connection Endpoint (NCE) of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components.
.1.3.6.1.2.1.34.6.1.4.2.1.5,HPR-MIB::hprRtpRemTcid,OCTET,read-only,,current,,The remote TCID of this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.6,HPR-MIB::hprRtpPathSwitchTrigger,INTEGER,read-write,,current,ready(1):switchPathNow(2),Object by which a Management Station can trigger an operator- requested path switch, by setting the value to switchPathNow(2). Setting this object to switchPathNow(2) triggers a path switch even if its previous value was already switchPathNow(2). The value ready(1) is returned on GET operations until a SET has been processed; after that the value received on the most recent SET is returned. This MIB module provides no support for an operator-requested switch to a specified path.
.1.3.6.1.2.1.34.6.1.4.2.1.7,HPR-MIB::hprRtpRscv,OCTET,read-only,,current,,The forward Route Selection Control Vector for this RTP connection. The format of this vector is described in SNA Formats. The value returned in this object during a path switch is implementation-dependent: it may be the old path, the new path, a zero-length string, or some other valid RSCV string.
.1.3.6.1.2.1.34.6.1.4.2.1.8,HPR-MIB::hprRtpTopic,OCTET,read-only,,current,,The topic for this RTP connection. This is used to indicate the Class of Service.
.1.3.6.1.2.1.34.6.1.4.2.1.9,HPR-MIB::hprRtpState,INTEGER,read-only,,current,rtpListening(1):rtpCalling(2):rtpConnected(3):rtpPathSwitching(4):rtpDisconnecting(5):other(99),The state of the RTP connection, from the perspective of the local RTP protocol machine: rtpListening - connection open; waiting for other end to call in rtpCalling - connection opened, attempting to call out, have not yet received any data from other end rtpConnected - connection is active; responded to a call-in or received other end's TCID from a call-out attempt rtpPathSwitching - the path switch timer is running; attempting to find a new path for this connection. rtpDisconnecting - no sessions are using this connection; in process of bringing it down other - the connection is not in any of the states listed above.
.1.3.6.1.2.1.34.6.1.4.2.1.10,HPR-MIB::hprRtpUpTime,TimeTicks,read-only,,current,,The length of time the RTP connection has been up, measured in 1/100ths of a second.
.1.3.6.1.2.1.34.6.1.4.2.1.11,HPR-MIB::hprRtpLivenessTimer,Unsigned32,read-only,,current,,The value of the liveness (ALIVE) timer of this RTP connection, in units of 1/100th of a second. When this timer expires and no packet has arrived from the partner since it was last set, packets with Status Request indicators will be sent to see if the RTP connection is still alive.
.1.3.6.1.2.1.34.6.1.4.2.1.12,HPR-MIB::hprRtpShortReqTimer,Unsigned32,read-only,,current,,The value of the RTP SHORT_REQ timer, in units of 1/100 of a second. This timer represents the maximum time that a sender waits for a reply from a receiver.
.1.3.6.1.2.1.34.6.1.4.2.1.13,HPR-MIB::hprRtpPathSwTimer,Unsigned32,read-only,,current,,The length of time that RTP should attempt a path switch for a connection, in units of 1/100th of a second.
.1.3.6.1.2.1.34.6.1.4.2.1.14,HPR-MIB::hprRtpLivenessTimeouts,Counter32,read-only,,current,,The count of liveness timeouts for this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.15,HPR-MIB::hprRtpShortReqTimeouts,Counter32,read-only,,current,,The count of short request timeouts for this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.16,HPR-MIB::hprRtpMaxSendRate,Gauge32,read-only,,current,,The high-water mark for this RTP connection's send rate, in units of bytes per second. This is the high-water mark for the entire life of the connection, not just the high-water mark for the connection's current path. For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.
.1.3.6.1.2.1.34.6.1.4.2.1.17,HPR-MIB::hprRtpMinSendRate,Gauge32,read-only,,current,,The low-water mark for this RTP connection's send rate, in units of bytes per second. This is the low-water mark for the entire life of the connection, not just the low-water mark for the connection's current path. For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.
.1.3.6.1.2.1.34.6.1.4.2.1.18,HPR-MIB::hprRtpCurSendRate,Gauge32,read-only,,current,,The current send rate for this RTP connection, in units of bytes per second. For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.
.1.3.6.1.2.1.34.6.1.4.2.1.19,HPR-MIB::hprRtpSmRdTripDelay,Gauge32,read-only,,current,,The smoothed round trip delay for this RTP connection, in units of 1/1000th of a second (ms). For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.
.1.3.6.1.2.1.34.6.1.4.2.1.20,HPR-MIB::hprRtpSendPackets,Counter32,read-only,,current,,The count of packets successfully sent on this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.21,HPR-MIB::hprRtpRecvPackets,Counter32,read-only,,current,,The count of packets received on this RTP connection. The counter is incremented only once if duplicate copies of a packet are received.
.1.3.6.1.2.1.34.6.1.4.2.1.22,HPR-MIB::hprRtpSendBytes,Counter32,read-only,,current,,The count of bytes sent on this RTP connection. Both RTP Transport Header (THDR) bytes and data bytes are included in this count.
.1.3.6.1.2.1.34.6.1.4.2.1.23,HPR-MIB::hprRtpRecvBytes,Counter32,read-only,,current,,The count of bytes received on this RTP connection. Both RTP Transport Header (THDR) bytes and data bytes are included in this count.
.1.3.6.1.2.1.34.6.1.4.2.1.24,HPR-MIB::hprRtpRetrPackets,Counter32,read-only,,current,,The count of packets retransmitted on this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.25,HPR-MIB::hprRtpPacketsDiscarded,Counter32,read-only,,current,,The count of packets received on this RTP connection and then discarded. A packet may be discarded because it is determined to be a duplicate, or for other reasons.
.1.3.6.1.2.1.34.6.1.4.2.1.26,HPR-MIB::hprRtpDetectGaps,Counter32,read-only,,current,,The count of gaps detected on this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.27,HPR-MIB::hprRtpRateReqSends,Counter32,read-only,,current,,The count of Rate Requests sent on this RTP connection.
.1.3.6.1.2.1.34.6.1.4.2.1.28,HPR-MIB::hprRtpOkErrPathSws,Counter32,read-only,,current,,The count of successful path switch attempts for this RTP connection due to errors.
.1.3.6.1.2.1.34.6.1.4.2.1.29,HPR-MIB::hprRtpBadErrPathSws,Counter32,read-only,,current,,The count of unsuccessful path switches for this RTP connection due to errors.
.1.3.6.1.2.1.34.6.1.4.2.1.30,HPR-MIB::hprRtpOkOpPathSws,Counter32,read-only,,current,,The count of successful path switches for this RTP connection due to operator requests.
.1.3.6.1.2.1.34.6.1.4.2.1.31,HPR-MIB::hprRtpBadOpPathSws,Counter32,read-only,,current,,The count of unsuccessful path switches for this RTP connection due to operator requests. This counter is not incremented by an implementation that does not support operator-requested path switches, even if a Management Station requests such a path switch by setting the hprRtpPathSwitchTrigger object.
.1.3.6.1.2.1.34.6.1.4.2.1.32,HPR-MIB::hprRtpCounterDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for this RTP connection last experienced a discontinuity. This will be the more recent of two times: the time at which the connection was established or the time at which the HPR counters were last turned on or off.
.1.3.6.1.2.1.34.6.1.4.3,HPR-MIB::hprRtpStatusTable,,not-accessible,,current,,RTP Connection Status Table: This table contains historical information on RTP connections. An entry is created in this table when a path switch is completed, either successfully or unsuccessfully.
.1.3.6.1.2.1.34.6.1.4.3.1,HPR-MIB::hprRtpStatusEntry,,not-accessible,hprRtpStatusLocNceId:hprRtpStatusLocTcid:hprRtpStatusIndex,current,,This table is indexed by local NCE ID, local TCID, and an integer hprRtpStatusIndex. Thus the primary grouping of table rows is by RTP connection, with the multiple entries for a given RTP connection ordered by time.
.1.3.6.1.2.1.34.6.1.4.3.1.1,HPR-MIB::hprRtpStatusLocNceId,OCTET,not-accessible,,current,,The local Network Connection Endpoint (NCE) of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components.
.1.3.6.1.2.1.34.6.1.4.3.1.2,HPR-MIB::hprRtpStatusLocTcid,OCTET,not-accessible,,current,,The local TCID of this RTP connection.
.1.3.6.1.2.1.34.6.1.4.3.1.3,HPR-MIB::hprRtpStatusIndex,Unsigned32,not-accessible,,current,,Table index. This value begins at one and is incremented when a new entry is added to the table. It is an implementation choice whether to run a single counter for all entries in the table, or to run a separate counter for the entries for each RTP connection. In the unlikely event of a wrap, it is assumed that Management Stations will have the ability to order table entries correctly.
.1.3.6.1.2.1.34.6.1.4.3.1.4,HPR-MIB::hprRtpStatusStartTime,OCTET,read-only,,current,,The time when the path switch began.
.1.3.6.1.2.1.34.6.1.4.3.1.5,HPR-MIB::hprRtpStatusEndTime,OCTET,read-only,,current,,The time when the path switch was ended, either successfully or unsuccessfully.
.1.3.6.1.2.1.34.6.1.4.3.1.6,HPR-MIB::hprRtpStatusRemCpName,OCTET,read-only,,current,,Administratively assigned network name for the remote node of this RTP connection.
.1.3.6.1.2.1.34.6.1.4.3.1.7,HPR-MIB::hprRtpStatusRemNceId,OCTET,read-only,,current,,The remote Network Connection Endpoint (NCE) of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components.
.1.3.6.1.2.1.34.6.1.4.3.1.8,HPR-MIB::hprRtpStatusRemTcid,OCTET,read-only,,current,,The remote TCID of this RTP connection.
.1.3.6.1.2.1.34.6.1.4.3.1.9,HPR-MIB::hprRtpStatusNewRscv,OCTET,read-only,,current,,The new Route Selection Control Vector for this RTP connection. A zero-length string indicates that no value is available, perhaps because the implementation does not save RSCVs.
.1.3.6.1.2.1.34.6.1.4.3.1.10,HPR-MIB::hprRtpStatusOldRscv,OCTET,read-only,,current,,The old Route Selection Control Vector for this RTP connection. A zero-length string indicates that no value is available, perhaps because the implementation does not save RSCVs.
.1.3.6.1.2.1.34.6.1.4.3.1.11,HPR-MIB::hprRtpStatusCause,INTEGER,read-only,,current,other(1):rtpConnFail(2):locLinkFail(3):remLinkFail(4):operRequest(5),The reason for the path switch: other(1) - Reason other than those listed below, rtpConnFail(2) - RTP connection failure detected, locLinkFail(3) - Local link failure, remLinkFail(4) - Remote link failure (learned from TDUs), operRequest(5) - Operator requested path switch. 
.1.3.6.1.2.1.34.6.1.4.3.1.12,HPR-MIB::hprRtpStatusLastAttemptResult,INTEGER,read-only,,current,successful(1):initiatorMoving(2):directorySearchFailed(3):rscvCalculationFailed(4):negativeRouteSetupReply(5):backoutRouteSetupReply(6):timeoutDuringFirstAttempt(7):otherUnsuccessful(8),The result of the last completed path switch attempt. If the path switch is aborted in the middle of a path switch attempt because the path switch timer expires, the result of the previous path switch attempt is reported. The values are defined as follows: successful(1) - The final path switch attempt was successful. initiatorMoving(2) - The final path switch attempt failed because the initiator is mobile, and there was no active link out of this node. directorySearchFailed(3) - The final path switch attempt failed because a directory search for the destination node's CP name failed. rscvCalculationFailed(4) - The final path switch attempt failed because an RSCV to the node containing the remote RTP endpoint could not be calculated. negativeRouteSetupReply(5) - The final path switch attempt failed because route setup failed for the new path. backoutRouteSetupReply(6) - The final path switch attempt failed because the remote RTP endpoint refused to continue the RTP connection. timeoutDuringFirstAttempt(7) - The path switch timer expired during the first path switch attempt. otherUnsuccessful(8) - The final path switch attempt failed for a reason other than those listed above.
.1.3.6.1.2.1.34.6.1.5,HPR-IP-MIB::hprIp,,,,,,The MIB module for HPR over IP. This module contains two groups: - the HPR over IP Monitoring Group provides a count of the UDP packets sent by a link station for each APPN traffic type. - the HPR over IP Configuration Group provides for reading and setting the mappings between APPN traffic types and TOS Precedence settings in the IP header. These mappings are configured at the APPN port level, and are inherited by the APPN connection networks and link stations associated with an APPN port. A port-level mapping can, however, be overridden for a particular connection network or link station.
.1.3.6.1.2.1.34.6.1.5.1,HPR-IP-MIB::hprIpActiveLsTable,,not-accessible,,current,,The HPR/IP active link station table. This table provides counts of the number of UDP packets sent for each APPN traffic type.
.1.3.6.1.2.1.34.6.1.5.1.1,HPR-IP-MIB::hprIpActiveLsEntry,,not-accessible,hprIpActiveLsLsName:hprIpActiveLsAppnTrafficType,current,,Entry of the HPR/IP link station table.
.1.3.6.1.2.1.34.6.1.5.1.1.1,HPR-IP-MIB::hprIpActiveLsLsName,OCTET,not-accessible,,current,,Administratively assigned name for the link station. If this object has the same value as the appnLsName in the APPN MIB, then the two objects are referring to the same APPN link station.
.1.3.6.1.2.1.34.6.1.5.1.1.2,HPR-IP-MIB::hprIpActiveLsAppnTrafficType,INTEGER,not-accessible,,current,low(1):medium(2):high(3):network(4):llcAndFnRoutedNlp(5),APPN traffic type being sent through the link station.
.1.3.6.1.2.1.34.6.1.5.1.1.3,HPR-IP-MIB::hprIpActiveLsUdpPackets,Counter32,read-only,,current,,The count of outgoing UDP packets carrying this type of APPN traffic. A discontinuity in the counter is indicated by the appnLsCounterDisconTime object in the APPN MIB.
.1.3.6.1.2.1.34.6.1.5.2,HPR-IP-MIB::hprIpAppnPortTable,,not-accessible,,current,,The HPR/IP APPN port table. This table supports reading and setting the mapping between APPN traffic types and TOS Precedence settings for all the link stations at this APPN port. This mapping can be overridden for an individual link station or an individual connection network via, respectively, the hprIpLsTOSPrecedence and the hprIpCnTOSPrecedence objects.
.1.3.6.1.2.1.34.6.1.5.2.1,HPR-IP-MIB::hprIpAppnPortEntry,,not-accessible,hprIpAppnPortName:hprIpAppnPortAppnTrafficType,current,,Entry of the HPR/IP APPN port table. Entries exist for every APPN port defined to support HPR over IP.
.1.3.6.1.2.1.34.6.1.5.2.1.1,HPR-IP-MIB::hprIpAppnPortName,OCTET,not-accessible,,current,,Administratively assigned name for this APPN port. If this object has the same value as the appnPortName in the APPN MIB, then the two objects are referring to the same APPN port.
.1.3.6.1.2.1.34.6.1.5.2.1.2,HPR-IP-MIB::hprIpAppnPortAppnTrafficType,INTEGER,not-accessible,,current,low(1):medium(2):high(3):network(4):llcAndFnRoutedNlp(5),APPN traffic type sent through the port.
.1.3.6.1.2.1.34.6.1.5.2.1.3,HPR-IP-MIB::hprIpAppnPortTOSPrecedence,OCTET,read-write,,current,,A setting for the three TOS Precedence bits in the IP Type of Service field for this APPN traffic type. When this value is changed via a Set operation, the new setting for the TOS Precedence bits takes effect immediately, rather than waiting for some event such as reinitialization of the port or of the APPN node itself.
.1.3.6.1.2.1.34.6.1.5.3,HPR-IP-MIB::hprIpLsTable,,not-accessible,,current,,The HPR/IP link station table. Values for TOS Precedence at the link station level override those at the level of the containing port. If there is no entry in this table for a given link station, then that link station inherits its TOS Precedence values from its port.
.1.3.6.1.2.1.34.6.1.5.3.1,HPR-IP-MIB::hprIpLsEntry,,not-accessible,hprIpLsLsName:hprIpLsAppnTrafficType,current,,Entry of the HPR/IP link station table.
.1.3.6.1.2.1.34.6.1.5.3.1.1,HPR-IP-MIB::hprIpLsLsName,OCTET,not-accessible,,current,,Administratively assigned name for the link station. If this object has the same value as the appnLsName in the APPN MIB, then the two objects are referring to the same APPN link station.
.1.3.6.1.2.1.34.6.1.5.3.1.2,HPR-IP-MIB::hprIpLsAppnTrafficType,INTEGER,not-accessible,,current,low(1):medium(2):high(3):network(4):llcAndFnRoutedNlp(5),APPN traffic type sent through the link station.
.1.3.6.1.2.1.34.6.1.5.3.1.3,HPR-IP-MIB::hprIpLsTOSPrecedence,OCTET,read-create,,current,,A setting for the three TOS Precedence bits in the IP Type of Service field for this APPN traffic type. When this value is changed via a Set operation, the new setting for the TOS Precedence bits takes effect immediately, rather than waiting for some event such as reinitialization of the port or of the APPN node itself.
.1.3.6.1.2.1.34.6.1.5.3.1.4,HPR-IP-MIB::hprIpLsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the hprIpLsTable. As soon as an entry becomes active, the mapping between APPN traffic types and TOS Precedence settings that it specifies becomes effective. The value of the other accessible object in this entry, hprIpLsTOSPrecedence, can be changed via a Set operation when this object's value is active(1). An entry in this table is deleted by setting this object to destroy(6). Deleting an entry in this table causes the link station to revert to the default TOS Precedence mapping for its port.
.1.3.6.1.2.1.34.6.1.5.4,HPR-IP-MIB::hprIpCnTable,,not-accessible,,current,,The HPR/IP connection network table. Values for TOS Precedence at the connection network level override those at the level of the containing port. If there is no entry in this table for a given connection network, then that connection network inherits its TOS Precedence values from its port. A node may have connections to a given connection network through multiple ports. There is no provision in the HPR-IP architecture for variations in TOS Precedence values for a single connection network based on the port through which traffic is flowing to the connection network. Thus an entry in this table overrides the port-level settings for all the ports through which the node can reach the connection network.
.1.3.6.1.2.1.34.6.1.5.4.1,HPR-IP-MIB::hprIpCnEntry,,not-accessible,hprIpCnVrnName:hprIpCnAppnTrafficType,current,,Entry of the HPR/IP connection network table.
.1.3.6.1.2.1.34.6.1.5.4.1.1,HPR-IP-MIB::hprIpCnVrnName,OCTET,not-accessible,,current,,SNA control point name of the virtual routing node (VRN) that identifies the connection network in the APPN topology database. If this object has the same value as the appnVrnName in the APPN MIB, then the two objects are referring to the same APPN VRN.
.1.3.6.1.2.1.34.6.1.5.4.1.2,HPR-IP-MIB::hprIpCnAppnTrafficType,INTEGER,not-accessible,,current,low(1):medium(2):high(3):network(4):llcAndFnRoutedNlp(5),APPN traffic type sent to this connection network.
.1.3.6.1.2.1.34.6.1.5.4.1.3,HPR-IP-MIB::hprIpCnTOSPrecedence,OCTET,read-create,,current,,A setting for the three TOS Precedence bits in the IP Type of Service field for this APPN traffic type. This setting applies to all traffic sent to this connection network by this node, regardless of the port through which the traffic is sent. When this value is changed via a Set operation, the new setting for the TOS Precedence bits takes effect immediately, rather than waiting for some event such as reinitialization of a port or of the APPN node itself.
.1.3.6.1.2.1.34.6.1.5.4.1.4,HPR-IP-MIB::hprIpCnRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the hprIpCnTable. As soon as an entry becomes active, the mapping between APPN traffic types and TOS Precedence settings that it specifies becomes effective. The value of the other accessible object in this entry, hprIpCnTOSPrecedence, can be changed via a Set operation when this object's value is active(1). An entry in this table is deleted by setting this object to destroy(6). Deleting an entry in this table causes the connection network to revert to the default TOS Precedence mapping for each port through which it is accessed.
.1.3.6.1.2.1.34.6.2,HPR-MIB::hprConformance,,,,,,
.1.3.6.1.2.1.34.6.2.1,HPR-MIB::hprCompliances,,,,,,
.1.3.6.1.2.1.34.6.2.1.1,HPR-MIB::hprCompliance,,,,,,The compliance statement for the SNMPv2 entities that implement the HPR MIB.
.1.3.6.1.2.1.34.6.2.1.2,HPR-IP-MIB::hprIpCompliance,,,,,,Compliance statement for the HPR over IP MIB module.
.1.3.6.1.2.1.34.6.2.2,HPR-MIB::hprGroups,,,,,,
.1.3.6.1.2.1.34.6.2.2.1,HPR-MIB::hprGlobalConfGroup,,,,,,A collection of objects providing the instrumentation of HPR general information and capabilities.
.1.3.6.1.2.1.34.6.2.2.2,HPR-MIB::hprAnrRoutingConfGroup,,,,,,A collection of objects providing instrumentation for the node's ANR routing.
.1.3.6.1.2.1.34.6.2.2.3,HPR-MIB::hprTransportUserConfGroup,,,,,,A collection of objects providing information on the users of the HPR transport known to the node.
.1.3.6.1.2.1.34.6.2.2.4,HPR-MIB::hprRtpConfGroup,,,,,,A collection of objects providing the instrumentation for RTP connection end points.
.1.3.6.1.2.1.34.6.2.2.5,HPR-IP-MIB::hprIpMonitoringGroup,,,,,,An object for counting outgoing HPR/IP traffic for each APPN traffic type.
.1.3.6.1.2.1.34.6.2.2.6,HPR-IP-MIB::hprIpConfigurationGroup,,,,,,A collection of HPR/IP objects representing the mappings between APPN traffic types and TOS Precedence bits at the APPN port, APPN link station, and APPN connection network levels.
.1.3.6.1.2.1.34.7,EBN-MIB::ebnMIB,,,,,, The MIB Module for Extended Border Node
.1.3.6.1.2.1.34.7.1,EBN-MIB::ebnObjects,,,,,,
.1.3.6.1.2.1.34.7.1.1,EBN-MIB::ebnDir,,,,,,
.1.3.6.1.2.1.34.7.1.1.1,EBN-MIB::ebnDirTable,,not-accessible,,current,,The EBN Directory Table. This table is an extension to the APPN MIB's appnDirTable. Entries in this table are in one-to-one correspondence with entries in the appnDirTable, with corresponding entries having identical values for their respective indexes.
.1.3.6.1.2.1.34.7.1.1.1.1,EBN-MIB::ebnDirEntry,,not-accessible,ebnDirLuName,current,,Entry in the EBN Directory Table.
.1.3.6.1.2.1.34.7.1.1.1.1.1,EBN-MIB::ebnDirLuName,OCTET,not-accessible,,current,,Fully qualified network LU name in the domain of a serving network node. If this object has the same value as the appnDirLuName object in the APPN MIB, then the two objects are referring to the same LU.
.1.3.6.1.2.1.34.7.1.1.1.1.2,EBN-MIB::ebnDirSubnetAffiliation,INTEGER,read-only,,current,native(1):nonNative(2):subarea(3),Specifies the subnetwork affiliation of the LU: - native(1) : The LU is in the native APPN subnetwork. - nonNative(2) : The LU is in a non-native APPN subnetwork. - subarea(3) : The LU is in a subarea network.
.1.3.6.1.2.1.34.7.1.2,EBN-MIB::ebnIsRscv,,,,,,
.1.3.6.1.2.1.34.7.1.2.1,EBN-MIB::ebnIsRscvTable,,not-accessible,,current,,The EBN Intermediate Session RSCV table. This table is an extension to the appnIsInTable. It contains the RSCV and COS used in the direction of the BIND destination. There is an entry in this table for each session that traverses an ISTG when it enters or leaves this EBN, with corresponding entries having identical values for their respective indexes.
.1.3.6.1.2.1.34.7.1.2.1.1,EBN-MIB::ebnIsRscvEntry,,not-accessible,ebnIsRscvCpName:ebnIsRscvPcid,current,,Entry in ebnIsRscvTable.
.1.3.6.1.2.1.34.7.1.2.1.1.1,EBN-MIB::ebnIsRscvCpName,OCTET,not-accessible,,current,,The network-qualified control point name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. For DLUR resources it is the name of the owning SSCP. If this object has the same value as the appnIsInFqCpName object in the APPN MIB, then the two objects are referring to the same APPN control point.
.1.3.6.1.2.1.34.7.1.2.1.1.2,EBN-MIB::ebnIsRscvPcid,OCTET,not-accessible,,current,,The procedure correlation identifier (PCID) of a session. It is an 8-octet value. If this object has the same value as the appnIsInPcid object in the APPN MIB, and if the corresponding ebnIsRscvCpName object has the same value as the corresponding appnIsInFqCpName object, then the entries indexed by these objects are referring to the same session.
.1.3.6.1.2.1.34.7.1.2.1.1.3,EBN-MIB::ebnIsRscvDestinationRoute,OCTET,read-only,,current,,The route selection control vector (RSCV x'2B') used in the direction towards the SLU.
.1.3.6.1.2.1.34.7.1.2.1.1.4,EBN-MIB::ebnIsRscvDestinationCos,OCTET,read-only,,current,,The Class of Service (COS) name used in the direction towards the SLU. Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization.
.1.3.6.1.2.1.34.7.1.3,EBN-MIB::ebnDirConfig,,,,,,
.1.3.6.1.2.1.34.7.1.3.1,EBN-MIB::ebnSearchCacheTime,Unsigned32,read-only,,current,,The amount of time in minutes an extended border node will retain information about a multi-subnetwork search, once that that search terminates. A value 0 indicates that the EBN has no defined limit, and the number of entries is bounded only by memory.
.1.3.6.1.2.1.34.7.1.3.2,EBN-MIB::ebnMaxSearchCache,Unsigned32,read-only,,current,,The maximum number of multi-subnet entries to be cached. The value 0 indicates that the local node has no defined limit, and the number of entries is bounded only by memory.
.1.3.6.1.2.1.34.7.1.3.3,EBN-MIB::ebnDefaultSubnetVisitCount,Unsigned32,read-only,,current,,The default maximum number of subnetworks a LOCATE search procedure may traverse.
.1.3.6.1.2.1.34.7.1.4,EBN-MIB::ebnCOS,,,,,,
.1.3.6.1.2.1.34.7.1.4.1,EBN-MIB::ebnCosMapTable,,not-accessible,,current,,The EBN COS Mapping Table. This table specifies how non- native COS values are mapped to COS values defined in the native subnetwork. Note: The COS mappings that an EBN performs are determined by multiple factors, one of which is a set of user-defined initial mappings. This table returns the COS mappings that the EBN is actually performing at the time it is queried, rather than the user-defined initial ones.
.1.3.6.1.2.1.34.7.1.4.1.1,EBN-MIB::ebnCosMapEntry,,not-accessible,ebnCosMapCpName:ebnCosMapNonNativeCos,current,,An entry in the EBN COS Mapping table.
.1.3.6.1.2.1.34.7.1.4.1.1.1,EBN-MIB::ebnCosMapCpName,OCTET,not-accessible,,current,,Fully qualified network CP name for which the COS mapping applies.
.1.3.6.1.2.1.34.7.1.4.1.1.2,EBN-MIB::ebnCosMapNonNativeCos,OCTET,not-accessible,,current,,This object contains one of the following values: - An 8-character COS name used in a non-native subnetwork. - The single character '*', identifying the entry with the default native COS for a non-native CP name. This entry is used when there is no entry in the table for a non-native CP name / non-native COS pair. Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization.
.1.3.6.1.2.1.34.7.1.4.1.1.3,EBN-MIB::ebnCosMapNativeCos,OCTET,read-only,,current,,An 8-byte name for the class-of-service, as known in the native subnetwork. Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization.
.1.3.6.1.2.1.34.7.1.5,EBN-MIB::ebnSubnetRoutingList,,,,,,
.1.3.6.1.2.1.34.7.1.5.1,EBN-MIB::ebnSubnetSearchTable,,not-accessible,,current,,This table contains one entry for each fully qualified LU name for which an associated subnet routing list has been defined. An entry in this table contains general characteristics of the subnet search routing list for an LU name. The routing list itself is represented by a set of contiguous entries in the ebnSearchTable.
.1.3.6.1.2.1.34.7.1.5.1.1,EBN-MIB::ebnSubnetSearchEntry,,not-accessible,ebnSubnetSearchLuName,current,,An entry for the ebnSubnetSearchTable. The entry represents the configured parameters the EBN uses when it is determining how to search for the LU identified by the ebnSubnetSearchLuName object.
.1.3.6.1.2.1.34.7.1.5.1.1.1,EBN-MIB::ebnSubnetSearchLuName,OCTET,not-accessible,,current,,Fully qualified network LU name.
.1.3.6.1.2.1.34.7.1.5.1.1.2,EBN-MIB::ebnSubnetSearchDynamics,INTEGER,read-only,,current,none(1):limited(2):full(3),Indicates whether an EBN may add dynamic entries to a subnetwork routing list. none(1) means no entries may be added to the subnetwork routing list. limited(2) means only likely entries may be added to the subnetwork routing list. full(3) means all native extended border nodes and adjacent, non-native EBNs and NNs will be added to the subnetwork routing list.
.1.3.6.1.2.1.34.7.1.5.1.1.3,EBN-MIB::ebnSubnetSearchOrdering,INTEGER,read-only,,current,priority(1):defined(2),Indicates whether an EBN may reorder a subnetwork routing list so that entries which are more likely to be successful move to the top of the subnetwork routing list and entries which are more likely to be unsuccessful move to the bottom of the list. The following values are defined: - priority(1): Entries may be reordered. - defined(2): Entries must not be reordered.
.1.3.6.1.2.1.34.7.1.5.2,EBN-MIB::ebnSearchTable,,not-accessible,,current,,This table indicates the CONFIGURED list of control points to which the EBN sends Locate searches for a given fully qualified LU name. Each entry in the table indicates one control point that should be included in a multi-subnet search for a particular LU name.
.1.3.6.1.2.1.34.7.1.5.2.1,EBN-MIB::ebnSearchEntry,,not-accessible,ebnSearchLuName:ebnSearchIndex,current,,An entry in the ebnSearchTable. An entry can exist in this table only if an entry exists in the ebnSubnetSearchTable with an ebnSubnetSearchLuName value matching this entry's ebnSearchLuName. For a given ebnSearchLuName value, the ordering of entries provides by the ebnSearchIndex values corresponds to the order in which the control points to be searched appear in the CONFIGURED search list for the ebnSearchLuName.
.1.3.6.1.2.1.34.7.1.5.2.1.1,EBN-MIB::ebnSearchLuName,OCTET,not-accessible,,current,,Fully qualified network LU name. If this object has the same value as the ebnSubnetSearchLuName object, then the two objects are referring to the same LU.
.1.3.6.1.2.1.34.7.1.5.2.1.2,EBN-MIB::ebnSearchIndex,Unsigned32,not-accessible,,current,,Secondary index enumerating the CONFIGURED order in which a search is forwarded to CPs for a particular LU name. The order for an actual search is determined dynamically by the EBN, based on this configured information and on other factors, including whether search dynamics and search ordering are enabled. Information on these last two settings is available in, respectively, the ebnSubnetSearchDynamics and ebnSubnetSearch ordering objects.
.1.3.6.1.2.1.34.7.1.5.2.1.3,EBN-MIB::ebnSearchCpName,OCTET,read-only,,current,,This object specifies the CP(s) to which a search should be forwarded. It either follows the SnaNAUWildcardName textual convention or takes one of the following special formats: '*' indicates that all native EBNs and all adjacent non- native EBNs and NNs may be added to the routing list dynamically, '*SELF' indicates that the EBN should search itself and its native subnetwork at this time during the cross-subnet search, '*EBNS' indicates all native EBNs. Because the characters allowed in a CP name come from a restricted character set, and because the three formats listed here use no special characters, this object is not subject to internationalization.
.1.3.6.1.2.1.34.7.1.5.2.1.4,EBN-MIB::ebnSearchSNVC,Unsigned32,read-only,,current,,The maximum number of subnets a Locate search procedure may traverse. 
.1.3.6.1.2.1.34.7.1.6,EBN-MIB::hbn,,,,,,
.1.3.6.1.2.1.34.7.1.6.1,EBN-MIB::hbnIsInTable,,not-accessible,,current,,The HBN Intermediate Session table.
.1.3.6.1.2.1.34.7.1.6.1.1,EBN-MIB::hbnIsInEntry,,not-accessible,hbnIsInFqCpName:hbnIsInPcid,current,,Entry of the HBN Intermediate Session Table. An entry exists in this table for every intermediate session being routed between back-to-back RTP connections in the HBN. When an entry for a session exists in this table, the NceIds and Tcids for the back-to-back RTP connections are made available in the following four objects: RTP connection in the direction of the PLU: - NceId: appnIsInRtpNceId (in the APPN MIB) - Tcid: appnIsinRtpTcid (in the APPN MIB). RTP connection in the direction of the SLU: - NceId: hbnIsInRtpNceId (in this table) - Tcid: hbnIsInRtpTcid (in this table).
.1.3.6.1.2.1.34.7.1.6.1.1.1,EBN-MIB::hbnIsInFqCpName,OCTET,not-accessible,,current,,The network-qualified control point name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either the CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. If this object has the same value as the appnIsInFqCpName object in the APPN MIB, then the two objects are referring to the same APPN control point.
.1.3.6.1.2.1.34.7.1.6.1.1.2,EBN-MIB::hbnIsInPcid,OCTET,not-accessible,,current,,The procedure correlation identifier (PCID) of a session. It is an 8-octet value. If this object has the same value as the appnIsInPcid object in the APPN MIB, and if the corresponding hbnIsInFqCpName object has the same value as the corresponding appnIsInFqCpName object, then the entries indexed by these objects are referring to the same session.
.1.3.6.1.2.1.34.7.1.6.1.1.3,EBN-MIB::hbnIsInRtpNceId,OCTET,read-only,,current,,The HPR local Network Connection Endpoint of the session in the direction of the SLU.
.1.3.6.1.2.1.34.7.1.6.1.1.4,EBN-MIB::hbnIsInRtpTcid,OCTET,read-only,,current,,The RTP connection local TCID of the session in the direction of the SLU.
.1.3.6.1.2.1.34.7.2,EBN-MIB::ebnConformance,,,,,,
.1.3.6.1.2.1.34.7.2.1,EBN-MIB::ebnCompliances,,,,,,
.1.3.6.1.2.1.34.7.2.1.1,EBN-MIB::ebnCompliance,,,,,,The compliance statement for the SNMPv2 entities which implement the ebnMIB.
.1.3.6.1.2.1.34.7.2.2,EBN-MIB::ebnGroups,,,,,,
.1.3.6.1.2.1.34.7.2.2.1,EBN-MIB::ebnDirectoryGroup,,,,,,The EBN-related directory objects.
.1.3.6.1.2.1.34.7.2.2.2,EBN-MIB::ebnIsRscvGroup,,,,,,Two objects representing RSCV and class of service information saved by an EBN.
.1.3.6.1.2.1.34.7.2.2.3,EBN-MIB::ebnDirectoryConfigGroup,,,,,,The EBN Directory Configuration Group.
.1.3.6.1.2.1.34.7.2.2.4,EBN-MIB::ebnCosMappingGroup,,,,,,The EBN COS Mapping Group.
.1.3.6.1.2.1.34.7.2.2.5,EBN-MIB::ebnSubnetRoutingListGroup,,,,,,The Subnet Routing List Group.
.1.3.6.1.2.1.34.7.2.2.6,EBN-MIB::hbnIsInGroup,,,,,,The HBN-related Intermediate Session Objects.
.1.3.6.1.2.1.34.8,TN3270E-MIB::tn3270eMIB,,,,,,This module defines a portion of the management information base (MIB) for managing TN3270E servers.
.1.3.6.1.2.1.34.8.0,TN3270E-MIB::tn3270eNotifications,,,,,,
.1.3.6.1.2.1.34.8.1,TN3270E-MIB::tn3270eObjects,,,,,,
.1.3.6.1.2.1.34.8.1.1,TN3270E-MIB::tn3270eSrvrConfTable,,not-accessible,,current,,This table defines the configuration elements for TN3270E servers. The number of entries in this table is expected to vary depending on the location of the table. A particular TN3270E server is expected to have a single entry. Modeling of the configuration elements as a table allows multiple TN3270E servers to be serviced by the same SNMP agent. An implementation SHOULD NOT retain an SNMP-created entry in this table across re-IPLs (Initial Program Loads) of the corresponding TN3270E server.
.1.3.6.1.2.1.34.8.1.1.1,TN3270E-MIB::tn3270eSrvrConfEntry,,not-accessible,tn3270eSrvrConfIndex,current,,Definition of the configuration elements for a single TN3270E server.
.1.3.6.1.2.1.34.8.1.1.1.1,TN3270E-MIB::tn3270eSrvrConfIndex,Unsigned32,not-accessible,,current,,Identifier for a single TN3270E server. tn3270eSrvrConfIndex values need not be contiguous.
.1.3.6.1.2.1.34.8.1.1.1.2,TN3270E-MIB::tn3270eSrvrConfInactivityTimeout,Unsigned32,read-create,,current,,The inactivity time-out specified in seconds. When a connection has been inactive for the number of seconds specified by this object it is closed. Only user traffic is considered when determining whether there has been activity on a connection. The default value 0 means that no inactivity time-out is in effect.
.1.3.6.1.2.1.34.8.1.1.1.3,TN3270E-MIB::tn3270eSrvrConfConnectivityChk,INTEGER,read-create,,current,timingMark(1):nop(2):noCheck(3),This object enables TIMING-MARK processing, NOP processing, or neither for a TN3270E server.
.1.3.6.1.2.1.34.8.1.1.1.4,TN3270E-MIB::tn3270eSrvrConfTmNopInactTime,Unsigned32,read-create,,current,,The amount of time a connection must have had no traffic on it in order for a TIMING-MARK or NOP request to be sent on the connection. This value applies only when connections are being examined for recent activity on a scan interval controlled by the value of the tn3270eSrvrConfTmNopInterval object.
.1.3.6.1.2.1.34.8.1.1.1.5,TN3270E-MIB::tn3270eSrvrConfTmNopInterval,Unsigned32,read-create,,current,,The scan interval to be used by a TN3270E server when it examines its Telnet connections for recent activity. The server scans its Telnet connections on the interval provided by this object, looking for ones that have been idle for more than the value provided by the tn3270eSrvrConfTmNopInactTime object. A TIMING-MARK or NOP request is sent for each connection that has exhibited no activity for this period of time.
.1.3.6.1.2.1.34.8.1.1.1.6,TN3270E-MIB::tn3270eSrvrFunctionsSupported,BITS,read-only,,current,transmitBinary(0):timemark(1):endOfRecord(2):terminalType(3):tn3270Regime(4):scsCtlCodes(5):dataStreamCtl(6):responses(7):bindImage(8):sysreq(9),This object indicates the functions supported by a TN3270E server.
.1.3.6.1.2.1.34.8.1.1.1.7,TN3270E-MIB::tn3270eSrvrConfAdminStatus,INTEGER,read-create,,current,up(1):down(2):stopImmediate(3),The desired state of the TN3270E server represented by this entry in the table: up(1) - Activate this TN3270E server. down(2) - Informs the associated TN3270E server to gracefully terminate its processing. stopImmediate(3) - Informs the associated TN3270E server to terminate itself immediately. When a managed system creates an entry in this table, tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus are initialized as up(1) by default. The exact behavior of a server in response to a down(2) or stopImmediate(3) command is left implementation- dependent. A TN3270E server that is capable of it SHOULD close all of its TN3270 and TN3270E sessions during a graceful termination. Often the function enabled via stopImmediate(3) is used as a last resort by a system administrator, to attempt to either bring down a hung TN3270E server or free up its resources immediately to aid in general system availability, or to shut down a TN3270E server that is not recognizing a down(2) request. A TN3270E server that does not distinguish between down(2) or stopImmediate(3) transitions should not support stopImmediate(3).
.1.3.6.1.2.1.34.8.1.1.1.8,TN3270E-MIB::tn3270eSrvrConfOperStatus,INTEGER,read-only,,current,up(1):down(2):busy(3):shuttingDown(4),The current operational state of a TN3270E server. The following values are defined: up(1) - the server is active and accepting new client connections down(2) - the server is not active busy(3) - the server is active, but is not accepting new client connections because it lacks the resources to do so shuttingDown(4) - the server is active, but is not accepting new client connections because it is in the process of performing a graceful shutdown.
.1.3.6.1.2.1.34.8.1.1.1.9,TN3270E-MIB::tn3270eSrvrConfSessionTermState,INTEGER,read-create,,current,terminate(1):luSessionPend(2):queueSession(3),This object determines what a TN3270E server should do when a TN3270 Session terminates: terminate(1) => Terminate the TCP connection. luSessionPend(2) => Do not drop the TCP connection associated with a client when its TN3270 session ends. Processing should redrive session initialization as if the client were first connecting. queueSession(3) => This value relates to the Close Destination PASS (CLSDST PASS) operation in VTAM. An example provides the easiest explanation. Suppose a TN3270E client is in session with APPL1, and APPL1 does a CLSDST PASS of the client's session to APPL2. queueSession(3) specifies that the TN3270E server must keep the TCP connection with the client active after it receives the UNBIND from APPL1, waiting for the BIND from APPL2.
.1.3.6.1.2.1.34.8.1.1.1.10,TN3270E-MIB::tn3270eSrvrConfSrvrType,INTEGER,read-only,,current,host(1):gateway(2),This object indicates the type of TN3270E server. The existence of MIB tables and objects that will be defined by follow-on MIBs may be predicated on whether the TN3270E server can be local to the same host as a target application (host(1)) or will always be remote (gateway(2)). A host TN3270E server refers to an implementation where the TN3270E server is collocated with the Systems Network Architecture (SNA) System Services Control Point (SSCP) for the dependent Secondary Logical Units (SLUs) that the server makes available to its clients for connecting into an SNA network. A gateway TN3270E server resides on an SNA node other than an SSCP, either an SNA type 2.0 node or an APPN node acting in the role of a Dependent LU Requester (DLUR). Host and gateway TN3270E server implementations typically differ greatly as to their internal implementation and system definition (SYSDEF) requirements.
.1.3.6.1.2.1.34.8.1.1.1.11,TN3270E-MIB::tn3270eSrvrConfContact,OCTET,read-create,,current,,This object provides a scratch pad for a TN3270E server administrator for storing information for later retrieval.
.1.3.6.1.2.1.34.8.1.1.1.12,TN3270E-MIB::tn3270eSrvrConfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the tn3270eSrvrConfTable. Entries may also be created and deleted as a result of implementation- dependent operations. With the exception of tn3270eSrvrConfSrvrType, which an implementation can easily fill in for itself, all the columnar objects in this table have DEFVALs associated with them. Consequently, a Management Station can create a conceptual row via a SET operation that specifies a value only for this object. When a tn3270eSrvrConfEntry is deleted (by setting this object to destroy(6)), this has the side-effect of removing all the associated entries (i.e., those having the same tn3270eSrvrConfIndex) from the tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the tn3270eClientGroupTable, the tn3270eResPoolTable, the tn3270eSnaMapTable, the tn3270eClientResMapTable, and the tn3270eResMapTable. All entries in the tn3270eTcpConnTable that belong to a TN3270E server that has been deleted MUST also be removed. In other words, a tn3270eSrvrConfEntry must exist for a TN3270E server in order for it to have entries in any of the other tables defined by this MIB.
.1.3.6.1.2.1.34.8.1.1.1.13,TN3270E-MIB::tn3270eSrvrConfLastActTime,OCTET,read-only,,current,,This object reports the DateAndTime when a TN3270E server was most recently activated. The special value of all '00'Hs indicates that the server has never been active, i.e., that the value of tn3270eSrvrOperStatus has never been anything other than down(2).
.1.3.6.1.2.1.34.8.1.1.1.14,TN3270E-MIB::tn3270eSrvrConfTmTimeout,Unsigned32,read-create,,current,,The TIMING-MARK time-out, specified in seconds.
.1.3.6.1.2.1.34.8.1.2,TN3270E-MIB::tn3270eSrvrPortTable,,not-accessible,,current,,This table defines the TCP ports associated with TN3270E servers. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing. An implementation SHOULD NOT retain SNMP-created entries in this table across re-IPLs (Initial Program Loads) of the corresponding TN3270E server.
.1.3.6.1.2.1.34.8.1.2.1,TN3270E-MIB::tn3270eSrvrPortEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eSrvrPort:tn3270eSrvrPortAddrType:tn3270eSrvrPortAddress,current,,Definition of a single TCP port assignment to a TN3270E server. Assignment of a port on a local address basis is enabled though use of tn3270eSrvrPortAddrType and tn3270eSrvrPortAddress. A TCP port assignment that is not restricted to a local address SHALL specify a tn3270eSrvrPortAddrType of unknown(0), and SHALL use a zero-length octet string for the tn3270eSrvrPortAddress.
.1.3.6.1.2.1.34.8.1.2.1.1,TN3270E-MIB::tn3270eSrvrPort,Unsigned32,not-accessible,,current,,Indicates a port assigned to a server.
.1.3.6.1.2.1.34.8.1.2.1.2,TN3270E-MIB::tn3270eSrvrPortAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),Indicates the type of an address local to the host on which the TN3270E server resides that is represented in tn3270eSrvrPortAddress. A value of unknown(0) SHALL be used for this object when the port is not to be restricted to a local address.
.1.3.6.1.2.1.34.8.1.2.1.3,TN3270E-MIB::tn3270eSrvrPortAddress,OCTET,not-accessible,,current,,A local address on the host that a TN3270E server resides on that is associated with a TCP port that is to be used or is in use by a TN3270E server. tn3270eClientGroupAddrType indicates the address type (IPv4 or IPv6, for example). A zero-length octet string SHALL be used as the value of this object when a local address isn't being specified.
.1.3.6.1.2.1.34.8.1.2.1.4,TN3270E-MIB::tn3270eSrvrPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the tn3270eSrvrPortTable. Entries may also be created and deleted as a result of implementation- dependent operations. Since this is the only accessible object in this table, a Management Station can create a conceptual row via a SET operation that specifies a value only for this object. An entry in this table is deleted by setting this object to destroy(6). Deletion of a tn3270eSrvrPortEntry has no effect on any other table entry defined by this MIB.
.1.3.6.1.2.1.34.8.1.3,TN3270E-MIB::tn3270eSrvrStatsTable,,not-accessible,,current,,This table defines a set of statistics concerning TN3270E server performance. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing.
.1.3.6.1.2.1.34.8.1.3.1,TN3270E-MIB::tn3270eSrvrStatsEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eSrvrPort:tn3270eSrvrPortAddrType:tn3270eSrvrPortAddress,current,,A collection of statistical and maximum usage objects for a single TN3270 server. An entry can represent the total activity of the server, or it can represent the activity occurring at the server on either a port or a port-and-local-address basis. Collection of the statistics represented by the objects in this table is not mandatory. An implementation of this table MUST use only one of the three levels of refinement that this table supports for the entries associated with each TN3270E server. The indexing for a row that represents total server statistics is as follows: tn3270eSrvrConfIndex value identifying the server tn3270eSrvrPort 0 tn3270eSrvrPortAddrType unknown(0) tn3270eSrvrPortAddress zero-length octet string. On a port basis: tn3270eSrvrConfIndex value identifying the server tn3270eSrvrPort > 0 tn3270eSrvrPortAddrType unknown(0) tn3270eSrvrPortAddress zero-length octet string. On a port-and-local-address basis: tn3270eSrvrConfIndex value identifying the server tn3270eSrvrPort > 0 tn3270eSrvrPortAddrType valid value other than unknown(0) tn3270eSrvrPortAddress non-zero-length octet string. 
.1.3.6.1.2.1.34.8.1.3.1.2,TN3270E-MIB::tn3270eSrvrStatsUpTime,TimeTicks,read-only,,current,,The value of the sysUpTime object the last time the TN3270E server was re-initialized. Server re-initialization is the only discontinuity event for the counters in this table. Even if table entries are on a port or port-and-local-address basis, port deactivation and reactivation do not result in counter discontinuities.
.1.3.6.1.2.1.34.8.1.3.1.3,TN3270E-MIB::tn3270eSrvrStatsMaxTerms,Unsigned32,read-only,,current,,Indicates the maximum number of terminal LUs available for use at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
.1.3.6.1.2.1.34.8.1.3.1.4,TN3270E-MIB::tn3270eSrvrStatsInUseTerms,Gauge32,read-only,,current,,Indicates the number of terminal LUs currently in use at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
.1.3.6.1.2.1.34.8.1.3.1.5,TN3270E-MIB::tn3270eSrvrStatsSpareTerms,Gauge32,read-only,,current,,Indicates the number of free terminal LUs at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). It is possible that the difference between tn3270eSrvrStatsMaxTerms and tn3270eSrvrStatsInUseTerms in a conceptual row does not equal the value of tn3270eSrvrStatsSpareTerms in that row: an LU may exist but not be usable by a client connection. Alternatively, the administrative ceiling represented by tn3270eSrvrStatsMaxTerms may have been lowered to a point where it is less than the current value of tn3270eSrvrStatsInUseTerms. In this case tn3270eSrvrStatsSpareTerms returns the value 0.
.1.3.6.1.2.1.34.8.1.3.1.6,TN3270E-MIB::tn3270eSrvrStatsMaxPtrs,Unsigned32,read-only,,current,,Indicates the maximum number of printer resources available for use by a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
.1.3.6.1.2.1.34.8.1.3.1.7,TN3270E-MIB::tn3270eSrvrStatsInUsePtrs,Gauge32,read-only,,current,,Indicates the number of printer resources currently in use by a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
.1.3.6.1.2.1.34.8.1.3.1.8,TN3270E-MIB::tn3270eSrvrStatsSparePtrs,Gauge32,read-only,,current,,Indicates the number of free printer resources at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). It is possible that the difference between tn3270eSrvrStatsMaxPtrs and tn3270eSrvrStatsInUsePtrs in a conceptual row does not equal the value of tn3270eSrvrStatsSparePtrs in that row: a printer resource may exist but not be usable by a client connection. Alternatively, the administrative ceiling represented by tn3270eSrvrStatsMaxPtrs may have been lowered to a point where it is less than the current value of tn3270eSrvrStatsInUsePtrs. In this case tn3270eSrvrStatsSparePtrs returns the value 0.
.1.3.6.1.2.1.34.8.1.3.1.9,TN3270E-MIB::tn3270eSrvrStatsInConnects,Counter32,read-only,,current,,Indicates the number of client (TCP) connections that succeeded at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). The tn3270eSrvrStatsConnResrceRejs and tn3270eSrvrStatsConnErrorRejs objects provide a count of failed connection attempts. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.10,TN3270E-MIB::tn3270eSrvrStatsConnResrceRejs,Counter32,read-only,,current,,Indicates the number of (TCP) connections rejected during connection setup at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address) due to a lack of resources at the server. An example of when this counter would be incremented is when no terminal or printer resource is available to associate with a client's TCP connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.11,TN3270E-MIB::tn3270eSrvrStatsDisconnects,Counter32,read-only,,current,,Indicates the number of (TCP) connections that were disconnected at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.12,TN3270E-MIB::tn3270eSrvrStatsHCInOctets,Counter64,read-only,,current,,Indicates the number of octets received from TN3270 and TN3270E clients for the granularity of this conceptual row (server-wide, port, or port-and-local-address). A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.13,TN3270E-MIB::tn3270eSrvrStatsInOctets,Counter32,read-only,,current,,Low-order 32 bits of tn3270eSrvrStatsHCInOctets for this conceptual row. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.14,TN3270E-MIB::tn3270eSrvrStatsHCOutOctets,Counter64,read-only,,current,,Indicates the number of octets sent to TN3270 and TN3270E clients for the granularity of this conceptual row (server-wide, port, or port-and-local-address). A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.15,TN3270E-MIB::tn3270eSrvrStatsOutOctets,Counter32,read-only,,current,,Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for this conceptual row. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.3.1.16,TN3270E-MIB::tn3270eSrvrStatsConnErrorRejs,Counter32,read-only,,current,,Indicates the number of (TCP) connections rejected during connection setup at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address) due to an error of some type. An example of when this counter would be incremented is when the client and the server cannot agree on a common set of TN3270E functions for the connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
.1.3.6.1.2.1.34.8.1.4,TN3270E-MIB::tn3270eClientGroupTable,,not-accessible,,current,,This table defines client address groupings for use by a TN3270E server. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing. An implementation SHOULD NOT retain SNMP-created entries in this table across re-IPLs (Initial Program Loads) of the corresponding TN3270E server.
.1.3.6.1.2.1.34.8.1.4.1,TN3270E-MIB::tn3270eClientGroupEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eClientGroupName:tn3270eClientGroupAddrType:tn3270eClientGroupAddress,current,,Definition of a single client address entry. All entries with the same first two indexes, tn3270eSrvrConfIndex and tn3270eClientGroupName, are considered to be in the same client group.
.1.3.6.1.2.1.34.8.1.4.1.1,TN3270E-MIB::tn3270eClientGroupName,OCTET,not-accessible,,current,,The name of a client group. Note: client group names are required to be unique only with respect to a single TN3270E server.
.1.3.6.1.2.1.34.8.1.4.1.2,TN3270E-MIB::tn3270eClientGroupAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),Indicates the type of the address represented in tn3270eClientGroupAddress.
.1.3.6.1.2.1.34.8.1.4.1.3,TN3270E-MIB::tn3270eClientGroupAddress,OCTET,not-accessible,,current,,The client address of a member of a client group. The value of tn3270eClientGroupAddrType indicates the address type (IPv4 or IPv6, for example).
.1.3.6.1.2.1.34.8.1.4.1.4,TN3270E-MIB::tn3270eClientGroupSubnetMask,IpAddress,read-create,,current,,The corresponding subnet mask associated with tn3270eClientGroupAddress. A single IP address is represented by having this object contain the value of 255.255.255.255. This object's value is meaningful only if tn3270eClientGroupAddrType has a value of ipv4(1).
.1.3.6.1.2.1.34.8.1.4.1.5,TN3270E-MIB::tn3270eClientGroupPfxLength,Unsigned32,read-create,,current,,The corresponding IPv6 network prefix length. This object's value is meaningful only if tn3270eClientGroupAddrType has a value of ipv6(2).
.1.3.6.1.2.1.34.8.1.4.1.6,TN3270E-MIB::tn3270eClientGroupRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the tn3270eClientGroupTable. Entries may also be created and deleted as a result of implementation- dependent operations. An entry in this table is deleted by setting this object to destroy(6). When the number of entries in this table for a given client group becomes 0, this has the side- effect of removing any entries for the group in the tn3270eClientResMapTable.
.1.3.6.1.2.1.34.8.1.5,TN3270E-MIB::tn3270eResPoolTable,,not-accessible,,current,,This table defines resource groupings; the term 'pool' is used as it is defined by RFC 2355. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing. An implementation SHOULD NOT retain SNMP-created entries in this table across re-IPLs (Initial Program Loads) of the corresponding TN3270E server.
.1.3.6.1.2.1.34.8.1.5.1,TN3270E-MIB::tn3270eResPoolEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eResPoolName:tn3270eResPoolElementName,current,,Definition of a single resource pool member. All entries with the same first two indexes, tn3270eSrvrConfIndex and tn3270eResPoolName, are considered to be in the same pool.
.1.3.6.1.2.1.34.8.1.5.1.1,TN3270E-MIB::tn3270eResPoolName,OCTET,not-accessible,,current,,The name of a resource pool.
.1.3.6.1.2.1.34.8.1.5.1.2,TN3270E-MIB::tn3270eResPoolElementName,OCTET,not-accessible,,current,,The name of a member of a resource pool.
.1.3.6.1.2.1.34.8.1.5.1.3,TN3270E-MIB::tn3270eResPoolElementType,INTEGER,read-create,,current,other(1):terminal(2):printer(3):terminalOrPrinter(4),The type of the entity in a resource pool.
.1.3.6.1.2.1.34.8.1.5.1.4,TN3270E-MIB::tn3270eResPoolRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the tn3270eResPoolTable. Entries may also be created and deleted as a result of implementation- dependent operations. An entry in this table is deleted by setting this object to destroy(6). When all entries in this table associated with the same tn3270eResPoolElementName have been removed, then any associated (tn3270eResPoolElementName matching tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex values) entries in the tn3270eClientResMapTable SHALL also be removed.
.1.3.6.1.2.1.34.8.1.6,TN3270E-MIB::tn3270eSnaMapTable,,not-accessible,,current,,This table provide a mapping from the name by which a secondary LU is known in the SNA network to the name by which it is known locally at the TN3270e server. This latter name serves as an index into the tn3270eResPoolTable and the tn3270eResMapTable. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing.
.1.3.6.1.2.1.34.8.1.6.1,TN3270E-MIB::tn3270eSnaMapEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eSnaMapSscpSuppliedName,current,,Definition of a single mapping from an SSCP-supplied SLU name to a local SLU name. Note: In certain pathological cases, it is possible that an SSCP will send on an ACTLU for a local LU an SLU name currently represented by an entry in this table that associates it with a different local LU. In these cases the association from the newer ACTLU SHOULD be the one represented in this table.
.1.3.6.1.2.1.34.8.1.6.1.1,TN3270E-MIB::tn3270eSnaMapSscpSuppliedName,OCTET,not-accessible,,current,,The name of the secondary LU (SLU) as it is known in the SNA network. This name is sent by the SSCP on the Activate Logical Unit (ACTLU) request.
.1.3.6.1.2.1.34.8.1.6.1.2,TN3270E-MIB::tn3270eSnaMapLocalName,OCTET,read-only,,current,,The local name of the secondary LU (SLU).
.1.3.6.1.2.1.34.8.1.6.1.3,TN3270E-MIB::tn3270eSnaMapPrimaryLuName,OCTET,read-only,,current,,When there is a currently active LU-LU session for this connection, this object returns the primary LU (PLU) name from the BIND. When there is no active LU-LU session, or when the PLU name is unavailable for some other reason, this object returns a zero-length octet string.
.1.3.6.1.2.1.34.8.1.7,TN3270E-MIB::tn3270eClientResMapTable,,not-accessible,,current,,This table defines resource-pool to client-group mappings. Since both the resource pool name and client group name are included in the index clause of this table, multiple resource pools can be assigned to the same client group. This enables use of multiple resource pools for use in client to resource mapping. Assigning multiple client groups to the same resource pool is also allowed, but is not the primary purpose for how the indexing is structured. Assignment of a resource pool to client group can be restricted based on TCP port. An index value of 0 for tn3270eClientResMapClientPort disables restriction of resource assignment based on client target port selection. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing. An implementation SHOULD NOT retain SNMP-created entries in this table across re-IPLs (Initial Program Loads) of the corresponding TN3270E server.
.1.3.6.1.2.1.34.8.1.7.1,TN3270E-MIB::tn3270eClientResMapEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eClientResMapPoolName:tn3270eClientResMapClientGroupName:tn3270eClientResMapClientPort,current,,Definition of a single resource pool to client group mapping.
.1.3.6.1.2.1.34.8.1.7.1.1,TN3270E-MIB::tn3270eClientResMapPoolName,OCTET,not-accessible,,current,,The name of a resource pool.
.1.3.6.1.2.1.34.8.1.7.1.2,TN3270E-MIB::tn3270eClientResMapClientGroupName,OCTET,not-accessible,,current,,The name of the client group that is mapped to a resource pool.
.1.3.6.1.2.1.34.8.1.7.1.3,TN3270E-MIB::tn3270eClientResMapClientPort,Unsigned32,not-accessible,,current,,A port number restricting the scope of a mapping from a resource pool to a client group. The value 0 for this object indicates that the scope of the mapping is not restricted.
.1.3.6.1.2.1.34.8.1.7.1.4,TN3270E-MIB::tn3270eClientResMapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the tn3270eClientResMapTable. Entries may also be created and deleted as a result of implementation- dependent operations. An entry in this table is deleted by setting this object to destroy(6). Removing an entry from this table doesn't affect any other table entry defined in this MIB.
.1.3.6.1.2.1.34.8.1.8,TN3270E-MIB::tn3270eResMapTable,,not-accessible,,current,,This table defines the actual mapping of a resource to a client address. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing.
.1.3.6.1.2.1.34.8.1.8.1,TN3270E-MIB::tn3270eResMapEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eResMapElementName,current,,Definition of the mapping of a Resource Element to a client address.
.1.3.6.1.2.1.34.8.1.8.1.1,TN3270E-MIB::tn3270eResMapElementName,OCTET,not-accessible,,current,,The name of a resource element. This is the name by which the server implementing this table knows the resource. It may be different from the name by which the resource is known in the SNA network. This latter name is returned in the tn3270eResMapSscpSuppliedName object.
.1.3.6.1.2.1.34.8.1.8.1.2,TN3270E-MIB::tn3270eResMapAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2),Indicates the type of the client address represented in tn3270eResMapAddress.
.1.3.6.1.2.1.34.8.1.8.1.3,TN3270E-MIB::tn3270eResMapAddress,OCTET,read-only,,current,,A client address.
.1.3.6.1.2.1.34.8.1.8.1.4,TN3270E-MIB::tn3270eResMapPort,Unsigned32,read-only,,current,,A client port.
.1.3.6.1.2.1.34.8.1.8.1.5,TN3270E-MIB::tn3270eResMapElementType,INTEGER,read-only,,current,other(1):terminal(2):printer(3):terminalOrPrinter(4),The type of the associated resource element.
.1.3.6.1.2.1.34.8.1.8.1.6,TN3270E-MIB::tn3270eResMapSscpSuppliedName,OCTET,read-only,,current,,The name of the secondary LU (SLU) as it is known in a SNA network. This name is sent by the SSCP on the Activate Logical Unit (ACTLU) request. If this name is not known, this object returns a zero-length octet string.
.1.3.6.1.2.1.34.8.1.9,TN3270E-MIB::tn3270eTcpConnTable,,not-accessible,,current,,This table has an entry for each TN3270(E) client connection that is currently active at a TN3270E server. An implementation MAY retain entries for connections that have been terminated, but which entries are retained, how many entries are retained, and how long they are retained is entirely implementation-dependent. The indexing for this table is designed to support the use of an SNMP GET-NEXT operation using only the remote address type, remote address, and remote port, as a way for a Management Station to retrieve the table entries related to a particular TN3270(E) client.
.1.3.6.1.2.1.34.8.1.9.1,TN3270E-MIB::tn3270eTcpConnEntry,,not-accessible,tn3270eTcpConnRemAddrType:tn3270eTcpConnRemAddress:tn3270eTcpConnRemPort:tn3270eTcpConnLocalAddrType:tn3270eTcpConnLocalAddress:tn3270eTcpConnLocalPort,current,,Provides information about a single TN3270/TN3270E session. Note: a tn3270eSrvrConfIndex is not needed in this table, since the combination of remote and local addresses and ports is sufficient to guarantee uniqueness across the TN3270E servers serviced by an SNMP agent. Because of this indexing structure, however, this table does not support view-based access control policies that provide access to table rows on a per-server basis.
.1.3.6.1.2.1.34.8.1.9.1.1,TN3270E-MIB::tn3270eTcpConnRemAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),Indicates the type of the value of the tn3270eTcpConnRemAddress object. For example, ipv4(1) or ipv6(2).
.1.3.6.1.2.1.34.8.1.9.1.2,TN3270E-MIB::tn3270eTcpConnRemAddress,OCTET,not-accessible,,current,,The remote address associated with a TN3270E client. tn3270eTcpConnRemAddrType indicates the address type (IPv4 or IPv6, for example). If a TN3270(E) client is connected to its server via a proxy client the address represented by the value of this object shall be the remote client's address, not the proxy client's address.
.1.3.6.1.2.1.34.8.1.9.1.3,TN3270E-MIB::tn3270eTcpConnRemPort,Unsigned32,not-accessible,,current,,The remote port associated with a TN3270E client. The value 0 is used if the tn3270eTcpConnRemAddrType identifies an address type that does not support ports. If a TN3270(E) client is connected to its server via a proxy client, the port represented by the value of this object shall be the remote client's port, not the proxy client's port.
.1.3.6.1.2.1.34.8.1.9.1.4,TN3270E-MIB::tn3270eTcpConnLocalAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),Indicates the type of the value of the tn3270eTcpConnLocalAddress object. For example, ipv4(1) or ipv6(2).
.1.3.6.1.2.1.34.8.1.9.1.5,TN3270E-MIB::tn3270eTcpConnLocalAddress,OCTET,not-accessible,,current,,The local address associated with a TN3270E client. tn3270eTcpConnRemAddrType indicates the address type (IPv4 or IPv6, for example).
.1.3.6.1.2.1.34.8.1.9.1.6,TN3270E-MIB::tn3270eTcpConnLocalPort,Unsigned32,not-accessible,,current,,The remote port associated with a TN3270E client.
.1.3.6.1.2.1.34.8.1.9.1.7,TN3270E-MIB::tn3270eTcpConnLastActivity,TimeTicks,read-only,,current,,The number of 100ths of seconds since any data was transferred for the associated TCP Connection.
.1.3.6.1.2.1.34.8.1.9.1.8,TN3270E-MIB::tn3270eTcpConnBytesIn,Counter32,read-only,,current,,The number of bytes received by the server from TCP for this connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eTcpConnActivationTime object.
.1.3.6.1.2.1.34.8.1.9.1.9,TN3270E-MIB::tn3270eTcpConnBytesOut,Counter32,read-only,,current,,The number of bytes sent to TCP for this connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eTcpConnActivationTime object.
.1.3.6.1.2.1.34.8.1.9.1.10,TN3270E-MIB::tn3270eTcpConnResourceElement,OCTET,read-only,,current,,LU/Print secondary name for connecting an client into an SNA network.
.1.3.6.1.2.1.34.8.1.9.1.11,TN3270E-MIB::tn3270eTcpConnResourceType,INTEGER,read-only,,current,other(1):terminal(2):printer(3):terminalOrPrinter(4),Indicates the type of resource identified by tn3270eTcpConnResourceElement.
.1.3.6.1.2.1.34.8.1.9.1.12,TN3270E-MIB::tn3270eTcpConnDeviceType,INTEGER,read-only,,current,ibm3278d2(1):ibm3278d2E(2):ibm3278d3(3):ibm3278d3E(4):ibm3278d4(5):ibm3278d4E(6):ibm3278d5(7):ibm3278d5E(8):ibmDynamic(9):ibm3287d1(10):unknown(100),Indicates the device type if negotiated with the client. A value of unknown(100) should be used as the value of this object when a device type is not negotiated. Refer to RFC 2355 for how device types can be negotiated.
.1.3.6.1.2.1.34.8.1.9.1.13,TN3270E-MIB::tn3270eTcpConnFunctions,BITS,read-only,,current,transmitBinary(0):timemark(1):endOfRecord(2):terminalType(3):tn3270Regime(4):scsCtlCodes(5):dataStreamCtl(6):responses(7):bindImage(8):sysreq(9),This object indicates which of the TN3270 and TN3270E functions were negotiated by the server and the client for this TCP connection. Refer to tn3270eSrvrFunctionsSupported for the list of these functions supported by the server.
.1.3.6.1.2.1.34.8.1.9.1.14,TN3270E-MIB::tn3270eTcpConnId,Unsigned32,read-only,,current,,The connection identifier associated with a TN3270 or a TN3270E session's TCP connection. TCP implementations often assign a unique (with respect to itself) unsigned integer as an identifier for a TCP connection. The value 0 indicates that a connection does not have a valid connection identifier.
.1.3.6.1.2.1.34.8.1.9.1.15,TN3270E-MIB::tn3270eTcpConnClientIdFormat,INTEGER,read-only,,current,none(1):other(2):ipv4(3):ipv6(4):domainName(5):truncDomainName(6):string(7):certificate(8):userId(9):x509dn(10),The format of a corresponding tn3270eTcpConnClientId object as defined by the IANSTn3270eClientType textual convention imported from the IANATn3270eTC-MIB.
.1.3.6.1.2.1.34.8.1.9.1.16,TN3270E-MIB::tn3270eTcpConnClientId,OCTET,read-only,,current,,Additional client identification information. The type of this information is indicated by the value of the corresponding tn3270eTcpConnClientIdFormat object. All values are returned in network-byte order. The purpose of this object is to provide an alternate means of identifying a client, other than though the remote address returned in tn3270eTcpConnRemAddress.
.1.3.6.1.2.1.34.8.1.9.1.17,TN3270E-MIB::tn3270eTcpConnTraceData,OCTET,read-only,,current,,Trace data for this session.
.1.3.6.1.2.1.34.8.1.9.1.18,TN3270E-MIB::tn3270eTcpConnLogInfo,OCTET,read-only,,current,,Log information, encoded as specified in the IANATn3270eLogData textual convention from the IANAtn3270eTC-MIB.
.1.3.6.1.2.1.34.8.1.9.1.19,TN3270E-MIB::tn3270eTcpConnLuLuBindImage,OCTET,read-only,,current,,When there is a currently active LU-LU session for this connection, this object returns the BIND Image (defined to be bytes 1-p of the complete BIND Request Unit -- see 'SNA Formats' for more information) that was received from the PLU during session activation. When there is no active LU-LU session, or when a BIND image is unavailable for some other reason, this object returns a zero-length octet string.
.1.3.6.1.2.1.34.8.1.9.1.20,TN3270E-MIB::tn3270eTcpConnSnaState,INTEGER,read-only,,current,unknown(1):noSluSession(2):sscpLuSession(3):luLuSession(4):sscpLuSessionAndLuLuSession(5),The current state of the SNA side of the end-to-end TN3270 connection. The following states are defined: unknown(1) - The true state is not known. noSluSession(2) - The SLU has neither an SSCP-LU nor an LU-LU session active. sscpLuSession(3) - The SSCP-LU session for the SLU is active, but the SLU is not currently in session with a PLU. luLuSession(4) - The SLU is currently in session with a PLU, but the SSCP-LU session for the LU is not active. sscpLuSessionAndLuLuSession(5) - The SLU currently has an active session with a PLU, and the SSCP-LU session for the SLU is active.
.1.3.6.1.2.1.34.8.1.9.1.21,TN3270E-MIB::tn3270eTcpConnStateLastDiscReason,INTEGER,read-only,,current,unknown(1):hostSendsUnbind(2):hostDontAcceptConnection(3):outOfResource(4):clientProtocolError(5):invalidDeviceName(6):deviceInUse(7):inactivityTimeout(8):hostNotResponding(9):clientNotResponding(10):serverClose(11):sysreqLogoff(12):serverSpecificHexCode(13),The last disconnect reason. A session that has not experienced a disconnect shall use the value unknown(1) for this object. Depending on when an implementation removes entries from this table, certain states may never be returned.
.1.3.6.1.2.1.34.8.1.9.1.22,TN3270E-MIB::tn3270eTcpConnSrvrConfIndex,Unsigned32,read-only,,current,,tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry belonging to the TN3270E server to which this entry belongs.
.1.3.6.1.2.1.34.8.1.9.1.23,TN3270E-MIB::tn3270eTcpConnActivationTime,TimeTicks,read-only,,current,,The value of the sysUpTime object the last time this TCP connection became active.
.1.3.6.1.2.1.34.8.1.10,TN3270E-MIB::tn3270eConfSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow cooperating TN3270E-MIB applications to coordinate their use of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the tn3270eClientGroupTable, the tn3270eResPoolTable, and the tn3270eClientResMapTable. When creating a new entry or altering an existing entry in the any of the tables mentioned above, an application should make use of tn3270eRtSpinLock to serialize application changes or additions. Since this is an advisory lock, the use of this lock is not enforced.
.1.3.6.1.2.1.34.8.3,TN3270E-MIB::tn3270eConformance,,,,,,
.1.3.6.1.2.1.34.8.3.1,TN3270E-MIB::tn3270eGroups,,,,,,
.1.3.6.1.2.1.34.8.3.1.1,TN3270E-MIB::tn3270eBasicGroup,,,,,,This group is mandatory for all hosts supporting the TN3270E-MIB.
.1.3.6.1.2.1.34.8.3.1.2,TN3270E-MIB::tn3270eSessionGroup,,,,,,This group is mandatory for all hosts supporting the TN3270E-MIB.
.1.3.6.1.2.1.34.8.3.1.3,TN3270E-MIB::tn3270eResMapGroup,,,,,,This group is optional for all hosts supporting the TN3270E-MIB.
.1.3.6.1.2.1.34.8.3.1.4,TN3270E-MIB::tn3270eHiCapacityGroup,,,,,,Support of these objects is REQUIRED when the Counter32 versions can potentially wrap too frequently. This group is optional for all other hosts supporting the TN3270E-MIB. The IF-MIB (RFC 2233) requires that the 64-bit versions of its counters be implemented when an interface can support rates of around 20 million bits per second or greater. This implies a minimum wrap rate of just over 28 minutes. It is recommended that this same guideline be used for determining whether an implementation implements these objects. This group contains two objects with the syntax Counter64. An implementation that doesn't support these objects should return noSuchObject, since returning a zero is misleading.
.1.3.6.1.2.1.34.8.3.2,TN3270E-MIB::tn3270eCompliances,,,,,,
.1.3.6.1.2.1.34.8.3.2.1,TN3270E-MIB::tn3270eCompliance,,,,,,The compliance statement for agents that support the TN3270E-MIB.
.1.3.6.1.2.1.34.9,TN3270E-RT-MIB::tn3270eRtMIB,,,,,,This module defines a portion of the management information base (MIB) that enables monitoring of TN3270 and TN3270E clients' response times by a TN3270E server.
.1.3.6.1.2.1.34.9.0,TN3270E-RT-MIB::tn3270eRtNotifications,,,,,,
.1.3.6.1.2.1.34.9.0.1,TN3270E-RT-MIB::tn3270eRtExceeded,,,,,,This notification is generated when the average response time, tn3270eRtDataAvgRt, exceeds tn3270eRtCollCtlThresholdHigh at the end of a collection interval specified by tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult. Note that the corresponding tn3270eCollCtlType must have traps(5) and average(3) set for this notification to be generated. In addition, tn3270eRtDataAvgCountTrans, tn3270eRtCollCtlThreshHigh, and tn3270eRtDataAvgRt are algorithmically compared to tn3270eRtCollCtlIdleCount for determination if this notification will be suppressed.
.1.3.6.1.2.1.34.9.0.2,TN3270E-RT-MIB::tn3270eRtOkay,,,,,,This notification is generated when the average response time, tn3270eRtDataAvgRt, falls below tn3270eRtCollCtlThresholdLow at the end of a collection interval specified by tn3270eCollCtlSPeriod times tn3270eCollCtlSPMult, after a tn3270eRtExceeded notification was generated. Note that the corresponding tn3270eCollCtlType must have traps(5) and average(3) set for this notification to be generated.
.1.3.6.1.2.1.34.9.0.3,TN3270E-RT-MIB::tn3270eRtCollStart,,,,,,This notification is generated when response time data collection is enabled for a member of a client group. In order for this notification to occur the corresponding tn3270eRtCollCtlType must have traps(5) selected. tn3270eResMapElementType contains a valid value only if tn3270eRtDataClientAddress contains a valid address (rather than a zero-length octet string).
.1.3.6.1.2.1.34.9.0.4,TN3270E-RT-MIB::tn3270eRtCollEnd,,,,,,This notification is generated when an tn3270eRtDataEntry is deleted after being active (actual data collected), in order to enable a management application monitoring an tn3270eRtDataEntry to get the entry's final values. Note that the corresponding tn3270eCollCtlType must have traps(5) set for this notification to be generated.
.1.3.6.1.2.1.34.9.1,TN3270E-RT-MIB::tn3270eRtObjects,,,,,,
.1.3.6.1.2.1.34.9.1.1,TN3270E-RT-MIB::tn3270eRtCollCtlTable,,not-accessible,,current,,The response time monitoring collection control table, which allows a management application to control the types of response time data being collected, and the clients for which it is being collected. This table is indexed by tn3270eSrvrConfIndex and tn3270eClientGroupName imported from the TN3270E-MIB. tn3270eSrvrConfIndex indicates within a host which TN3270E server an entry applies to. tn3270eClientGroupName it identifies the set of IP clients for which response time data is being collected. The particular IP clients making up the set are identified in the tn3270eClientGroupTable in the TN3270E-MIB.
.1.3.6.1.2.1.34.9.1.1.1,TN3270E-RT-MIB::tn3270eRtCollCtlEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eClientGroupName,current,,An entry in the TN3270E response time monitoring collection control table. To handle the case of multiple TN3270E servers on the same host, the first index of this table is the tn3270eSrvrConfIndex from the TN3270E-MIB.
.1.3.6.1.2.1.34.9.1.1.1.2,TN3270E-RT-MIB::tn3270eRtCollCtlType,OCTET,read-create,,current,,This object controls what types of response time data to collect, whether to summarize the data across the members of a client group or keep it individually, whether to introduce dynamic definite responses, and whether to generate traps. aggregate(0) - Aggregate response time data for the client group as a whole. If this bit is set to 0, then maintain response time data separately for each member of the client group. excludeIpComponent(1) - Do not include the IP-network component in any response times. ddr(2) - Enable dynamic definite response. average(3) - Produce an average response time based on a specified collection interval. buckets(4) - Maintain tn3270eRtDataBucket values in a corresponding tn3270eRtDataEntry, based on the bucket boundaries specified in the tn3270eRtCollCtlBucketBndry objects . traps(5) - generate the notifications specified in this MIB module. The tn3270eRtExceeded and tn3270eRtOkay notifications are generated only if average(3) is also specified.
.1.3.6.1.2.1.34.9.1.1.1.3,TN3270E-RT-MIB::tn3270eRtCollCtlSPeriod,Unsigned32,read-create,,current,,The number of seconds that defines the sample period. The actual interval is defined as tn3270eRtCollCtlSPeriod times tn3270eRtCollCtlSPMult. The value of this object is used only if the corresponding tn3270eRtCollCtlType has the average(3) setting.
.1.3.6.1.2.1.34.9.1.1.1.4,TN3270E-RT-MIB::tn3270eRtCollCtlSPMult,Unsigned32,read-create,,current,,The sample period multiplier; this value is multiplied by the sample period, tn3270eRtCollCtlSPeriod, to determine the collection interval. Sliding-window average calculation can, if necessary, be disabled, by setting the sample period multiplier, tn3270eRtCollCtlSPMult, to 1, and setting the sample period, tn3270eRtCollCtlSPeriod, to the required collection interval. The value of this object is used only if the corresponding tn3270eRtCollCtlType has the average(3) setting.
.1.3.6.1.2.1.34.9.1.1.1.5,TN3270E-RT-MIB::tn3270eRtCollCtlThreshHigh,Unsigned32,read-create,,current,,The threshold for generating a tn3270eRtExceeded notification, signalling that a monitored total response time has exceeded the specified limit. A value of zero for this object suppresses generation of this notification. The value of this object is used only if the corresponding tn3270eRtCollCtlType has average(3) and traps(5) selected. A tn3270eRtExceeded notification is not generated again for a tn3270eRtDataEntry until an average response time falling below the low threshold tn3270eRtCollCtlThreshLow specified for the client group has occurred for the entry.
.1.3.6.1.2.1.34.9.1.1.1.6,TN3270E-RT-MIB::tn3270eRtCollCtlThreshLow,Unsigned32,read-create,,current,,The threshold for generating a tn3270eRtOkay notification, signalling that a monitored total response time has fallen below the specified limit. A value of zero for this object suppresses generation of this notification. The value of this object is used only if the corresponding tn3270eRtCollCtlType has average(3) and traps(5) selected. A tn3270eRtOkay notification is not generated again for a tn3270eRtDataEntry until an average response time exceeding the high threshold tn3270eRtCollCtlThreshHigh specified for the client group has occurred for the entry.
.1.3.6.1.2.1.34.9.1.1.1.7,TN3270E-RT-MIB::tn3270eRtCollCtlIdleCount,Unsigned32,read-create,,current,,The value of this object is used to determine whether a sample that yields an average response time exceeding the value of tn3270eRtCollCtlThreshHigh was a statistically valid one. If the following statement is true, then the sample was statistically valid, and so a tn3270eRtExceeded notification should be generated: AvgCountTrans * ((AvgRt/ThreshHigh - 1) ** 2) >= IdleCount This comparison is done only if the corresponding tn3270eRtCollCtlType has average(3) and traps(5) selected.
.1.3.6.1.2.1.34.9.1.1.1.8,TN3270E-RT-MIB::tn3270eRtCollCtlBucketBndry1,Unsigned32,read-create,,current,,The value of this object defines the range of transaction response times counted in the Tn3270eRtDataBucket1Rts object: those less than or equal to this value.
.1.3.6.1.2.1.34.9.1.1.1.9,TN3270E-RT-MIB::tn3270eRtCollCtlBucketBndry2,Unsigned32,read-create,,current,,The value of this object, together with that of the tn3270eRtCollCtlBucketBndry1 object, defines the range of transaction response times counted in the Tn3270eRtDataBucket2Rts object: those greater than the value of the tn3270eRtCollCtlBucketBndry1 object, and less than or equal to the value of this object.
.1.3.6.1.2.1.34.9.1.1.1.10,TN3270E-RT-MIB::tn3270eRtCollCtlBucketBndry3,Unsigned32,read-create,,current,,The value of this object, together with that of the tn3270eRtCollCtlBucketBndry2 object, defines the range of transaction response times counted in the Tn3270eRtDataBucket3Rts object: those greater than the value of the tn3270eRtCollCtlBucketBndry2 object, and less than or equal to the value of this object.
.1.3.6.1.2.1.34.9.1.1.1.11,TN3270E-RT-MIB::tn3270eRtCollCtlBucketBndry4,Unsigned32,read-create,,current,,The value of this object, together with that of the tn3270eRtCollCtlBucketBndry3 object, defines the range of transaction response times counted in the Tn3270eRtDataBucket4Rts object: those greater than the value of the tn3270eRtCollCtlBucketBndry3 object, and less than or equal to the value of this object. The value of this object also defines the range of transaction response times counted in the Tn3270eRtDataBucket5Rts object: those greater than the value of this object.
.1.3.6.1.2.1.34.9.1.1.1.12,TN3270E-RT-MIB::tn3270eRtCollCtlRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the tn3270eRtCollCtlTable. An entry in this table is deleted by setting this object to destroy(6). Deleting an entry in this table has the side-effect of removing all entries from the tn3270eRtDataTable that are associated with the entry being deleted.
.1.3.6.1.2.1.34.9.1.2,TN3270E-RT-MIB::tn3270eRtDataTable,,not-accessible,,current,,The response time data table. Entries in this table are created based on entries in the tn3270eRtCollCtlTable.
.1.3.6.1.2.1.34.9.1.2.1,TN3270E-RT-MIB::tn3270eRtDataEntry,,not-accessible,tn3270eSrvrConfIndex:tn3270eClientGroupName:tn3270eRtDataClientAddrType:tn3270eRtDataClientAddress:tn3270eRtDataClientPort,current,,Entries in this table are created based upon the tn3270eRtCollCtlTable. When the corresponding tn3270eRtCollCtlType has aggregate(0) specified, a single entry is created in this table, with a tn3270eRtDataClientAddrType of unknown(0), a zero-length octet string value for tn3270eRtDataClientAddress, and a tn3270eRtDataClientPort value of 0. When aggregate(0) is not specified, a separate entry is created for each client in the group. Note that the following objects defined within an entry in this table can wrap: tn3270eRtDataTotalRts tn3270eRtDataTotalIpRts tn3270eRtDataCountTrans tn3270eRtDataCountDrs tn3270eRtDataElapsRnTrpSq tn3270eRtDataElapsIpRtSq tn3270eRtDataBucket1Rts tn3270eRtDataBucket2Rts tn3270eRtDataBucket3Rts tn3270eRtDataBucket4Rts tn3270eRtDataBucket5Rts
.1.3.6.1.2.1.34.9.1.2.1.1,TN3270E-RT-MIB::tn3270eRtDataClientAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),Indicates the type of address represented by the value of tn3270eRtDataClientAddress. The value unknown(0) is used if aggregate data is being collected for the client group.
.1.3.6.1.2.1.34.9.1.2.1.2,TN3270E-RT-MIB::tn3270eRtDataClientAddress,OCTET,not-accessible,,current,,Contains the IP address of the TN3270 client being monitored. A zero-length octet string is used if aggregate data is being collected for the client group.
.1.3.6.1.2.1.34.9.1.2.1.3,TN3270E-RT-MIB::tn3270eRtDataClientPort,Unsigned32,not-accessible,,current,,Contains the client port number of the TN3270 client being monitored. The value 0 is used if aggregate data is being collected for the client group, or if the tn3270eRtDataClientAddrType identifies an address type that does not support ports.
.1.3.6.1.2.1.34.9.1.2.1.4,TN3270E-RT-MIB::tn3270eRtDataAvgRt,Gauge32,read-only,,current,,The average total response time measured over the last collection interval.
.1.3.6.1.2.1.34.9.1.2.1.5,TN3270E-RT-MIB::tn3270eRtDataAvgIpRt,Gauge32,read-only,,current,,The average IP response time measured over the last collection interval.
.1.3.6.1.2.1.34.9.1.2.1.6,TN3270E-RT-MIB::tn3270eRtDataAvgCountTrans,Gauge32,read-only,,current,,The sliding transaction count used for calculating the values of the tn3270eRtDataAvgRt and tn3270eRtDataAvgIpRt objects. The actual transaction count is available in the tn3270eRtDataCountTrans object. The initial value of this object, before any averages have been calculated, is 0.
.1.3.6.1.2.1.34.9.1.2.1.7,TN3270E-RT-MIB::tn3270eRtDataIntTimeStamp,OCTET,read-only,,current,,The date and time of the last interval that tn3270eRtDataAvgRt, tn3270eRtDataAvgIpRt, and tn3270eRtDataAvgCountTrans were calculated. Prior to the calculation of the first interval averages, this object returns the value 0x0000000000000000000000. When this value is returned, the remaining objects in the entry have no significance.
.1.3.6.1.2.1.34.9.1.2.1.8,TN3270E-RT-MIB::tn3270eRtDataTotalRts,Counter32,read-only,,current,,The count of the total response times collected. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.9,TN3270E-RT-MIB::tn3270eRtDataTotalIpRts,Counter32,read-only,,current,,The count of the total IP-network response times collected. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.10,TN3270E-RT-MIB::tn3270eRtDataCountTrans,Counter32,read-only,,current,,The count of the total number of transactions detected. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.11,TN3270E-RT-MIB::tn3270eRtDataCountDrs,Counter32,read-only,,current,,The count of the total number of definite responses detected. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.12,TN3270E-RT-MIB::tn3270eRtDataElapsRndTrpSq,Unsigned32,read-only,,current,,The sum of the elapsed round trip time squared. The sum of the squares is kept in order to enable calculation of a variance.
.1.3.6.1.2.1.34.9.1.2.1.13,TN3270E-RT-MIB::tn3270eRtDataElapsIpRtSq,Unsigned32,read-only,,current,,The sum of the elapsed IP round trip time squared. The sum of the squares is kept in order to enable calculation of a variance.
.1.3.6.1.2.1.34.9.1.2.1.14,TN3270E-RT-MIB::tn3270eRtDataBucket1Rts,Counter32,read-only,,current,,The count of the response times falling into bucket 1. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.15,TN3270E-RT-MIB::tn3270eRtDataBucket2Rts,Counter32,read-only,,current,,The count of the response times falling into bucket 2. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.16,TN3270E-RT-MIB::tn3270eRtDataBucket3Rts,Counter32,read-only,,current,,The count of the response times falling into bucket 3. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.17,TN3270E-RT-MIB::tn3270eRtDataBucket4Rts,Counter32,read-only,,current,,The count of the response times falling into bucket 4. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.18,TN3270E-RT-MIB::tn3270eRtDataBucket5Rts,Counter32,read-only,,current,,The count of the response times falling into bucket 5. A management application can detect discontinuities in this counter by monitoring the tn3270eRtDataDiscontinuityTime object.
.1.3.6.1.2.1.34.9.1.2.1.19,TN3270E-RT-MIB::tn3270eRtDataRtMethod,INTEGER,read-only,,current,none(0):responses(1):timingMark(2),The value of this object indicates the method that was used in calculating the IP network time. The value 'none(0) indicates that response times were not calculated for the IP network.
.1.3.6.1.2.1.34.9.1.2.1.20,TN3270E-RT-MIB::tn3270eRtDataDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one or more of this entry's counter objects suffered a discontinuity. This may happen if a TN3270E server is stopped and then restarted, and local methods are used to set up collection policy (tn3270eRtCollCtlTable entries).
.1.3.6.1.2.1.34.9.1.3,TN3270E-RT-MIB::tn3270eRtSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow cooperating TN3270E-RT-MIB applications to coordinate their use of the tn3270eRtCollCtlTable. When creating a new entry or altering an existing entry in the tn3270eRtCollCtlTable, an application should make use of tn3270eRtSpinLock to serialize application changes or additions. Since this is an advisory lock, the use of this lock is not enforced.
.1.3.6.1.2.1.34.9.3,TN3270E-RT-MIB::tn3270eRtConformance,,,,,,
.1.3.6.1.2.1.34.9.3.1,TN3270E-RT-MIB::tn3270eRtGroups,,,,,,
.1.3.6.1.2.1.34.9.3.1.1,TN3270E-RT-MIB::tn3270eRtGroup,,,,,,This group is mandatory for all implementations that support the TN3270E-RT-MIB. 
.1.3.6.1.2.1.34.9.3.1.2,TN3270E-RT-MIB::tn3270eRtNotGroup,,,,,,The notifications that must be supported when the TN3270E-RT-MIB is implemented. 
.1.3.6.1.2.1.34.9.3.2,TN3270E-RT-MIB::tn3270eRtCompliances,,,,,,
.1.3.6.1.2.1.34.9.3.2.1,TN3270E-RT-MIB::tn3270eRtCompliance,,,,,,The compliance statement for agents that support the TN327E-RT-MIB.
.1.3.6.1.2.1.35,EtherLike-MIB::etherMIB,,,,,,The MIB module to describe generic objects for ethernet-like network interfaces. The following reference is used throughout this MIB module: [IEEE 802.3 Std] refers to: IEEE Std 802.3, 2002 Edition: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications', as amended by IEEE Std 802.3ae-2002: 'Amendment: Media Access Control (MAC) Parameters, Physical Layer, and Management Parameters for 10 Gb/s Operation', August, 2002. Of particular interest is Clause 30, '10 Mb/s, 100 Mb/s, 1000 Mb/s, and 10 Gb/s Management'. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3635; see the RFC itself for full legal notices.
.1.3.6.1.2.1.35.1,EtherLike-MIB::etherMIBObjects,,,,,,
.1.3.6.1.2.1.35.2,EtherLike-MIB::etherConformance,,,,,,
.1.3.6.1.2.1.35.2.1,EtherLike-MIB::etherGroups,,,,,,
.1.3.6.1.2.1.35.2.1.1,EtherLike-MIB::etherStatsGroup,,,,,,********* THIS GROUP IS DEPRECATED ********** A collection of objects providing information applicable to all ethernet-like network interfaces. This object group has been deprecated and replaced by etherStatsBaseGroup and etherStatsLowSpeedGroup.
.1.3.6.1.2.1.35.2.1.2,EtherLike-MIB::etherCollisionTableGroup,,,,,,A collection of objects providing a histogram of packets successfully transmitted after experiencing exactly N collisions.
.1.3.6.1.2.1.35.2.1.3,EtherLike-MIB::etherStats100MbsGroup,,,,,,********* THIS GROUP IS DEPRECATED ********** A collection of objects providing information applicable to 100 Mb/sec ethernet-like network interfaces. This object group has been deprecated and replaced by etherStatsBaseGroup and etherStatsHighSpeedGroup.
.1.3.6.1.2.1.35.2.1.4,EtherLike-MIB::etherStatsBaseGroup,,,,,,********* THIS GROUP IS DEPRECATED ********** A collection of objects providing information applicable to all ethernet-like network interfaces. This object group has been deprecated and replaced by etherStatsBaseGroup2 and etherStatsHalfDuplexGroup, to separate objects which must be implemented by all ethernet-like network interfaces from objects that need only be implemented on ethernet-like network interfaces that are capable of half-duplex operation.
.1.3.6.1.2.1.35.2.1.5,EtherLike-MIB::etherStatsLowSpeedGroup,,,,,,A collection of objects providing information applicable to ethernet-like network interfaces capable of operating at 10 Mb/s or slower in half-duplex mode.
.1.3.6.1.2.1.35.2.1.6,EtherLike-MIB::etherStatsHighSpeedGroup,,,,,,A collection of objects providing information applicable to ethernet-like network interfaces capable of operating at 100 Mb/s or faster.
.1.3.6.1.2.1.35.2.1.7,EtherLike-MIB::etherDuplexGroup,,,,,,A collection of objects providing information about the duplex mode of an ethernet-like network interface.
.1.3.6.1.2.1.35.2.1.8,EtherLike-MIB::etherControlGroup,,,,,,A collection of objects providing information about the MAC Control sublayer on ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.9,EtherLike-MIB::etherControlPauseGroup,,,,,,A collection of objects providing information about and control of the MAC Control PAUSE function on ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.10,EtherLike-MIB::etherStatsBaseGroup2,,,,,,A collection of objects providing information applicable to all ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.11,EtherLike-MIB::etherStatsHalfDuplexGroup,,,,,,A collection of objects providing information applicable only to half-duplex ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.12,EtherLike-MIB::etherHCStatsGroup,,,,,,A collection of objects providing high-capacity statistics applicable to higher-speed ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.13,EtherLike-MIB::etherHCControlGroup,,,,,,A collection of objects providing high-capacity statistics for the MAC Control sublayer on higher-speed ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.14,EtherLike-MIB::etherHCControlPauseGroup,,,,,,A collection of objects providing high-capacity statistics for the MAC Control PAUSE function on higher-speed ethernet-like network interfaces.
.1.3.6.1.2.1.35.2.1.15,EtherLike-MIB::etherRateControlGroup,,,,,,A collection of objects providing information about the Rate Control function on ethernet-like interfaces.
.1.3.6.1.2.1.35.2.2,EtherLike-MIB::etherCompliances,,,,,,
.1.3.6.1.2.1.35.2.2.1,EtherLike-MIB::etherCompliance,,,,,,******** THIS COMPLIANCE IS DEPRECATED ******** The compliance statement for managed network entities which have ethernet-like network interfaces. This compliance is deprecated and replaced by dot3Compliance.
.1.3.6.1.2.1.35.2.2.2,EtherLike-MIB::ether100MbsCompliance,,,,,,******** THIS COMPLIANCE IS DEPRECATED ******** The compliance statement for managed network entities which have 100 Mb/sec ethernet-like network interfaces. This compliance is deprecated and replaced by dot3Compliance.
.1.3.6.1.2.1.35.2.2.3,EtherLike-MIB::dot3Compliance,,,,,,******** THIS COMPLIANCE IS DEPRECATED ******** The compliance statement for managed network entities which have ethernet-like network interfaces. This compliance is deprecated and replaced by dot3Compliance2.
.1.3.6.1.2.1.35.2.2.4,EtherLike-MIB::dot3Compliance2,,,,,,The compliance statement for managed network entities which have ethernet-like network interfaces. Note that compliance with this MIB module requires compliance with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB (RFC2863). In addition, compliance with this MIB module requires compliance with the mauModIfCompl3 MODULE-COMPLIANCE statement of the MAU-MIB (RFC3636).
.1.3.6.1.2.1.36,SIP-MIB::sipMIB,,,,,,The MIB module to describe SMDS interfaces objects.
.1.3.6.1.2.1.36.1,SIP-MIB::sipMIBObjects,,,,,,
.1.3.6.1.2.1.36.1.1,SIP-MIB::sipDxiTable,,not-accessible,,current,,The DXI table.
.1.3.6.1.2.1.36.1.1.1,SIP-MIB::sipDxiEntry,,not-accessible,ifIndex,current,,An entry in the DXI table.
.1.3.6.1.2.1.36.1.1.1.1,SIP-MIB::sipDxiCrc,INTEGER,read-only,,current,crc16(1):crc32(2),The value of this object indicates the type of Frame Checksum used by DXI. Current choices include CCITT CRC16 or CRC32.
.1.3.6.1.2.1.36.1.1.1.2,SIP-MIB::sipDxiOutDiscards,Counter32,read-only,,current,,The number of outbound frames discarded because of congestion.
.1.3.6.1.2.1.36.1.1.1.3,SIP-MIB::sipDxiInErrors,Counter32,read-only,,current,,The number of inbound frames discarded because of errors such as frame checksum (CRC) violations, non-integral number of octets, address and control field violations, and frame size errors.
.1.3.6.1.2.1.36.1.1.1.4,SIP-MIB::sipDxiInAborts,Counter32,read-only,,current,,The number of inbound frames discarded because of an abort bit sequence (1111111) received before closing flag.
.1.3.6.1.2.1.36.1.1.1.5,SIP-MIB::sipDxiInTestFrames,Counter32,read-only,,current,,The number of unerrored, inbound Test frames received (generally as part of Heart Beat Poll procedure).
.1.3.6.1.2.1.36.1.1.1.6,SIP-MIB::sipDxiOutTestFrames,Counter32,read-only,,current,,The number of unerrored, outbound Test frames sent (generally as part of Heart Beat Poll procedure).
.1.3.6.1.2.1.36.1.1.1.7,SIP-MIB::sipDxiHbpNoAcks,Counter32,read-only,,current,,The number of Heart Beat Poll (HBP) No Ack timeouts.
.1.3.6.1.2.1.36.2,SIP-MIB::smdsConformance,,,,,,
.1.3.6.1.2.1.36.2.1,SIP-MIB::smdsGroups,,,,,,
.1.3.6.1.2.1.36.2.1.1,SIP-MIB::sipLevel3Stuff,,,,,,A collection of objects providing information applicable to all SMDS interfaces.
.1.3.6.1.2.1.36.2.1.2,SIP-MIB::sipLevel2Stuff,,,,,,A collection of objects providing information specific to interfaces using the SIP Level 2.
.1.3.6.1.2.1.36.2.1.3,SIP-MIB::sipDS1PLCPStuff,,,,,,A collection of objects providing information specific to interfaces using the DS1 PLCP.
.1.3.6.1.2.1.36.2.1.4,SIP-MIB::sipDS3PLCPStuff,,,,,,A collection of objects providing information specific to interfaces using the DS3 PLCP.
.1.3.6.1.2.1.36.2.1.5,SIP-MIB::sipIPApplicationsStuff,,,,,,A collection of objects providing information for running IP over SMDS.
.1.3.6.1.2.1.36.2.1.6,SIP-MIB::sipDxiStuff,,,,,,A collection of objects providing information specific to interfaces using the DXI protocol.
.1.3.6.1.2.1.36.2.2,SIP-MIB::smdsCompliances,,,,,,
.1.3.6.1.2.1.36.2.2.1,SIP-MIB::smdsCompliance,,,,,,The compliance statement for SMDS interfaces.
.1.3.6.1.2.1.37,ATM-TC-MIB::anonymous#1,,,,,,
.1.3.6.1.2.1.37.1,ATM-TC-MIB::anonymous#2,,,,,,
.1.3.6.1.2.1.37.1.1,ATM-TC-MIB::atmTrafficDescriptorTypes,,,,,,
.1.3.6.1.2.1.37.1.1.1,ATM-TC-MIB::atmNoTrafficDescriptor,,,,,,This identifies the no ATM traffic descriptor type. Parameters 1, 2, 3, 4, and 5 are not used. This traffic descriptor type can be used for best effort traffic.
.1.3.6.1.2.1.37.1.1.2,ATM-TC-MIB::atmNoClpNoScr,,,,,,This traffic descriptor type is for no CLP and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: not used Parameter 3: not used Parameter 4: not used Parameter 5: not used.
.1.3.6.1.2.1.37.1.1.3,ATM-TC-MIB::atmClpNoTaggingNoScr,,,,,,This traffic descriptor is for CLP without tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: peak cell rate in cells/second for CLP=0 traffic Parameter 3: not used Parameter 4: not used Parameter 5: not used.
.1.3.6.1.2.1.37.1.1.4,ATM-TC-MIB::atmClpTaggingNoScr,,,,,,This traffic descriptor is for CLP with tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: peak cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: not used Parameter 4: not used Parameter 5: not used.
.1.3.6.1.2.1.37.1.1.5,ATM-TC-MIB::atmNoClpScr,,,,,,This traffic descriptor type is for no CLP with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: not used Parameter 5: not used.
.1.3.6.1.2.1.37.1.1.6,ATM-TC-MIB::atmClpNoTaggingScr,,,,,,This traffic descriptor type is for CLP with Sustained Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic Parameter 3: maximum burst size in cells Parameter 4: not used Parameter 5: not used.
.1.3.6.1.2.1.37.1.1.7,ATM-TC-MIB::atmClpTaggingScr,,,,,,This traffic descriptor type is for CLP with tagging and Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: maximum burst size in cells Parameter 4: not used Parameter 5: not used.
.1.3.6.1.2.1.37.1.1.8,ATM-TC-MIB::atmClpNoTaggingMcr,,,,,,This traffic descriptor type is for CLP with Minimum Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: minimum cell rate in cells/second Parameter 4: unused Parameter 5: unused.
.1.3.6.1.2.1.37.1.1.9,ATM-TC-MIB::atmClpTransparentNoScr,,,,,,This traffic descriptor type is for the CLP- transparent model and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type is applicable to connections following the CBR.1 conformance definition. Connections specifying this traffic descriptor type will be rejected at UNI 3.0 or UNI 3.1 interfaces. For a similar traffic descriptor type that can be accepted at UNI 3.0 and UNI 3.1 interfaces, see atmNoClpNoScr.
.1.3.6.1.2.1.37.1.1.10,ATM-TC-MIB::atmClpTransparentScr,,,,,,This traffic descriptor type is for the CLP- transparent model with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to connections following the VBR.1 conformance definition. Connections specifying this traffic descriptor type will be rejected at UNI 3.0 or UNI 3.1 interfaces. For a similar traffic descriptor type that can be accepted at UNI 3.0 and UNI 3.1 interfaces, see atmNoClpScr.
.1.3.6.1.2.1.37.1.1.11,ATM-TC-MIB::atmNoClpTaggingNoScr,,,,,,This traffic descriptor type is for no CLP with tagging and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type is applicable to connections following the UBR.2 conformance definition .
.1.3.6.1.2.1.37.1.1.12,ATM-TC-MIB::atmNoClpNoScrCdvt,,,,,,This traffic descriptor type is for no CLP and no Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: CDVT in tenths of microseconds Parameter 3: not used Parameter 4: not used Parameter 5: not used. This traffic descriptor type is applicable to CBR connections following the UNI 3.0/3.1 conformance definition for PCR CLP=0+1. These CBR connections differ from CBR.1 connections in that the CLR objective applies only to the CLP=0 cell flow. This traffic descriptor type is also applicable to connections following the UBR.1 conformance definition.
.1.3.6.1.2.1.37.1.1.13,ATM-TC-MIB::atmNoClpScrCdvt,,,,,,This traffic descriptor type is for no CLP with Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0+1 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to VBR connections following the UNI 3.0/3.1 conformance definition for PCR CLP=0+1 and SCR CLP=0+1. These VBR connections differ from VBR.1 connections in that the CLR objective applies only to the CLP=0 cell flow.
.1.3.6.1.2.1.37.1.1.14,ATM-TC-MIB::atmClpNoTaggingScrCdvt,,,,,,This traffic descriptor type is for CLP with Sustained Cell Rate and no tagging. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to connections following the VBR.2 conformance definition.
.1.3.6.1.2.1.37.1.1.15,ATM-TC-MIB::atmClpTaggingScrCdvt,,,,,,This traffic descriptor type is for CLP with tagging and Sustained Cell Rate. The use of the parameter vector for this type: Parameter 1: peak cell rate in cells/second for CLP=0+1 traffic Parameter 2: sustainable cell rate in cells/second for CLP=0 traffic, excess tagged as CLP=1 Parameter 3: maximum burst size in cells Parameter 4: CDVT in tenths of microseconds Parameter 5: not used. This traffic descriptor type is applicable to connections following the VBR.3 conformance definition.
.1.3.6.1.2.1.37.1.2,ATM-MIB::atmInterfaceConfTable,,not-accessible,,current,,This table contains ATM local interface configuration parameters, one entry per ATM interface port.
.1.3.6.1.2.1.37.1.2.1,ATM-MIB::atmInterfaceConfEntry,,not-accessible,ifIndex,current,,This list contains ATM interface configuration parameters and state variables and is indexed by ifIndex values of ATM interfaces.
.1.3.6.1.2.1.37.1.2.1.1,ATM-MIB::atmInterfaceMaxVpcs,INTEGER,read-write,,current,,The maximum number of VPCs (PVPCs and SVPCs) supported at this ATM interface. At the ATM UNI, the maximum number of VPCs (PVPCs and SVPCs) ranges from 0 to 256 only.
.1.3.6.1.2.1.37.1.2.1.2,ATM-MIB::atmInterfaceMaxVccs,INTEGER,read-write,,current,,The maximum number of VCCs (PVCCs and SVCCs) supported at this ATM interface.
.1.3.6.1.2.1.37.1.2.1.3,ATM-MIB::atmInterfaceConfVpcs,INTEGER,read-only,,current,,The number of VPCs (PVPC, Soft PVPC and SVPC) currently in use at this ATM interface. It includes the number of PVPCs and Soft PVPCs that are configured at the interface, plus the number of SVPCs that are currently established at the interface. At the ATM UNI, the configured number of VPCs (PVPCs and SVPCs) can range from 0 to 256 only.
.1.3.6.1.2.1.37.1.2.1.4,ATM-MIB::atmInterfaceConfVccs,INTEGER,read-only,,current,,The number of VCCs (PVCC, Soft PVCC and SVCC) currently in use at this ATM interface. It includes the number of PVCCs and Soft PVCCs that are configured at the interface, plus the number of SVCCs that are currently established at the interface.
.1.3.6.1.2.1.37.1.2.1.5,ATM-MIB::atmInterfaceMaxActiveVpiBits,INTEGER,read-write,,current,,The maximum number of active VPI bits configured for use at the ATM interface. At the ATM UNI, the maximum number of active VPI bits configured for use ranges from 0 to 8 only.
.1.3.6.1.2.1.37.1.2.1.6,ATM-MIB::atmInterfaceMaxActiveVciBits,INTEGER,read-write,,current,,The maximum number of active VCI bits configured for use at this ATM interface.
.1.3.6.1.2.1.37.1.2.1.7,ATM-MIB::atmInterfaceIlmiVpi,INTEGER,read-write,,current,,The VPI value of the VCC supporting the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.
.1.3.6.1.2.1.37.1.2.1.8,ATM-MIB::atmInterfaceIlmiVci,INTEGER,read-write,,current,,The VCI value of the VCC supporting the ILMI at this ATM interface. If the values of atmInterfaceIlmiVpi and atmInterfaceIlmiVci are both equal to zero then the ILMI is not supported at this ATM interface.
.1.3.6.1.2.1.37.1.2.1.9,ATM-MIB::atmInterfaceAddressType,INTEGER,read-only,,deprecated,private(1):nsapE164(2):nativeE164(3):other(4),The type of primary ATM address configured for use at this ATM interface.
.1.3.6.1.2.1.37.1.2.1.10,ATM-MIB::atmInterfaceAdminAddress,OCTET,read-only,,deprecated,,The primary address assigned for administrative purposes, for example, an address associated with the service provider side of a public network UNI (thus, the value of this address corresponds with the value of ifPhysAddress at the host side). If this interface has no assigned administrative address, or when the address used for administrative purposes is the same as that used for ifPhysAddress, then this is an octet string of zero length.
.1.3.6.1.2.1.37.1.2.1.11,ATM-MIB::atmInterfaceMyNeighborIpAddress,IpAddress,read-write,,current,,The IP address of the neighbor system connected to the far end of this interface, to which a Network Management Station can send SNMP messages, as IP datagrams sent to UDP port 161, in order to access network management information concerning the operation of that system. Note that the value of this object may be obtained in different ways, e.g., by manual configuration, or through ILMI interaction with the neighbor system.
.1.3.6.1.2.1.37.1.2.1.12,ATM-MIB::atmInterfaceMyNeighborIfName,OCTET,read-write,,current,,The textual name of the interface on the neighbor system on the far end of this interface, and to which this interface connects. If the neighbor system is manageable through SNMP and supports the object ifName, the value of this object must be identical with that of ifName for the ifEntry of the lowest level physical interface for this port. If this interface does not have a textual name, the value of this object is a zero length string. Note that the value of this object may be obtained in different ways, e.g., by manual configuration, or through ILMI interaction with the neighbor system.
.1.3.6.1.2.1.37.1.2.1.13,ATM-MIB::atmInterfaceCurrentMaxVpiBits,INTEGER,read-only,,current,,The maximum number of VPI Bits that may currently be used at this ATM interface. The value is the minimum of atmInterfaceMaxActiveVpiBits, and the atmInterfaceMaxActiveVpiBits of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the number of VPI Bits that can be used on the interface, then the value of this object must equal atmInterfaceMaxActiveVpiBits.
.1.3.6.1.2.1.37.1.2.1.14,ATM-MIB::atmInterfaceCurrentMaxVciBits,INTEGER,read-only,,current,,The maximum number of VCI Bits that may currently be used at this ATM interface. The value is the minimum of atmInterfaceMaxActiveVciBits, and the atmInterfaceMaxActiveVciBits of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the number of VCI Bits that can be used on the interface, then the value of this object must equal atmInterfaceMaxActiveVciBits.
.1.3.6.1.2.1.37.1.2.1.15,ATM-MIB::atmInterfaceSubscrAddress,OCTET,read-write,,current,,The identifier assigned by a service provider to the network side of a public network UNI. If this interface has no assigned service provider address, or for other interfaces this is an octet string of zero length.
.1.3.6.1.2.1.37.1.3,ATM-MIB::atmInterfaceDs3PlcpTable,,not-accessible,,current,,This table contains ATM interface DS3 PLCP parameters and state variables, one entry per ATM interface port.
.1.3.6.1.2.1.37.1.3.1,ATM-MIB::atmInterfaceDs3PlcpEntry,,not-accessible,ifIndex,current,,This list contains DS3 PLCP parameters and state variables at the ATM interface and is indexed by the ifIndex value of the ATM interface.
.1.3.6.1.2.1.37.1.3.1.1,ATM-MIB::atmInterfaceDs3PlcpSEFSs,Counter32,read-only,,current,,The number of DS3 PLCP Severely Errored Framing Seconds (SEFS). Each SEFS represents a one-second interval which contains one or more SEF events.
.1.3.6.1.2.1.37.1.3.1.2,ATM-MIB::atmInterfaceDs3PlcpAlarmState,INTEGER,read-only,,current,noAlarm(1):receivedFarEndAlarm(2):incomingLOF(3),This variable indicates if there is an alarm present for the DS3 PLCP. The value receivedFarEndAlarm means that the DS3 PLCP has received an incoming Yellow Signal, the value incomingLOF means that the DS3 PLCP has declared a loss of frame (LOF) failure condition, and the value noAlarm means that there are no alarms present. Transition from the failure to the no alarm state occurs when no defects (e.g., LOF) are received for more than 10 seconds.
.1.3.6.1.2.1.37.1.3.1.3,ATM-MIB::atmInterfaceDs3PlcpUASs,Counter32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered by the PLCP.
.1.3.6.1.2.1.37.1.4,ATM-MIB::atmInterfaceTCTable,,not-accessible,,current,,This table contains ATM interface TC Sublayer parameters and state variables, one entry per ATM interface port.
.1.3.6.1.2.1.37.1.4.1,ATM-MIB::atmInterfaceTCEntry,,not-accessible,ifIndex,current,,This list contains TC Sublayer parameters and state variables at the ATM interface and is indexed by the ifIndex value of the ATM interface.
.1.3.6.1.2.1.37.1.4.1.1,ATM-MIB::atmInterfaceOCDEvents,Counter32,read-only,,current,,The number of times the Out of Cell Delineation (OCD) events occur. If seven consecutive ATM cells have Header Error Control (HEC) violations, an OCD event occurs. A high number of OCD events may indicate a problem with the TC Sublayer.
.1.3.6.1.2.1.37.1.4.1.2,ATM-MIB::atmInterfaceTCAlarmState,INTEGER,read-only,,current,noAlarm(1):lcdFailure(2),This variable indicates if there is an alarm present for the TC Sublayer. The value lcdFailure(2) indicates that the TC Sublayer is currently in the Loss of Cell Delineation (LCD) defect maintenance state. The value noAlarm(1) indicates that the TC Sublayer is currently not in the LCD defect maintenance state.
.1.3.6.1.2.1.37.1.5,ATM-MIB::atmTrafficDescrParamTable,,not-accessible,,current,,This table contains information on ATM traffic descriptor type and the associated parameters.
.1.3.6.1.2.1.37.1.5.1,ATM-MIB::atmTrafficDescrParamEntry,,not-accessible,atmTrafficDescrParamIndex,current,,This list contains ATM traffic descriptor type and the associated parameters.
.1.3.6.1.2.1.37.1.5.1.1,ATM-MIB::atmTrafficDescrParamIndex,INTEGER,not-accessible,,current,,This object is used by the virtual link table (i.e., VPL or VCL table) to identify the row of this table. When creating a new row in the table the value of this index may be obtained by retrieving the value of atmTrafficDescrParamIndexNext.
.1.3.6.1.2.1.37.1.5.1.2,ATM-MIB::atmTrafficDescrType,OBJECT,read-create,,current,,The value of this object identifies the type of ATM traffic descriptor. The type may indicate no traffic descriptor or traffic descriptor with one or more parameters. These parameters are specified as a parameter vector, in the corresponding instances of the objects: atmTrafficDescrParam1 atmTrafficDescrParam2 atmTrafficDescrParam3 atmTrafficDescrParam4 atmTrafficDescrParam5.
.1.3.6.1.2.1.37.1.5.1.3,ATM-MIB::atmTrafficDescrParam1,Integer32,read-create,,current,,The first parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
.1.3.6.1.2.1.37.1.5.1.4,ATM-MIB::atmTrafficDescrParam2,Integer32,read-create,,current,,The second parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
.1.3.6.1.2.1.37.1.5.1.5,ATM-MIB::atmTrafficDescrParam3,Integer32,read-create,,current,,The third parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
.1.3.6.1.2.1.37.1.5.1.6,ATM-MIB::atmTrafficDescrParam4,Integer32,read-create,,current,,The fourth parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
.1.3.6.1.2.1.37.1.5.1.7,ATM-MIB::atmTrafficDescrParam5,Integer32,read-create,,current,,The fifth parameter of the ATM traffic descriptor used according to the value of atmTrafficDescrType.
.1.3.6.1.2.1.37.1.5.1.8,ATM-MIB::atmTrafficQoSClass,INTEGER,read-create,,deprecated,,The value of this object identifies the QoS Class. Four Service classes have been specified in the ATM Forum UNI Specification: Service Class A: Constant bit rate video and Circuit emulation Service Class B: Variable bit rate video/audio Service Class C: Connection-oriented data Service Class D: Connectionless data Four QoS classes numbered 1, 2, 3, and 4 have been specified with the aim to support service classes A, B, C, and D respectively. An unspecified QoS Class numbered `0' is used for best effort traffic.
.1.3.6.1.2.1.37.1.5.1.9,ATM-MIB::atmTrafficDescrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create a new row or modify or delete an existing row in this table.
.1.3.6.1.2.1.37.1.5.1.10,ATM-MIB::atmServiceCategory,INTEGER,read-create,,current,other(1):cbr(2):rtVbr(3):nrtVbr(4):abr(5):ubr(6),The ATM service category.
.1.3.6.1.2.1.37.1.5.1.11,ATM-MIB::atmTrafficFrameDiscard,INTEGER,read-create,,current,true(1):false(2),If set to 'true', this object indicates that the network is requested to treat data for this connection, in the given direction, as frames (e.g. AAL5 CPCS_PDU's) rather than as individual cells. While the precise implementation is network-specific, this treatment may for example involve discarding entire frames during congestion, rather than a few cells from many frames.
.1.3.6.1.2.1.37.1.6,ATM-MIB::atmVplTable,,not-accessible,,current,,The Virtual Path Link (VPL) table. A bi-directional VPL is modeled as one entry in this table. This table can be used for PVCs, SVCs and Soft PVCs. Entries are not present in this table for the VPIs used by entries in the atmVclTable.
.1.3.6.1.2.1.37.1.6.1,ATM-MIB::atmVplEntry,,not-accessible,ifIndex:atmVplVpi,current,,An entry in the VPL table. This entry is used to model a bi-directional VPL. To create a VPL at an ATM interface, either of the following procedures are used: Negotiated VPL establishment (1) The management application creates a VPL entry in the atmVplTable by setting atmVplRowStatus to createAndWait(5). This may fail for the following reasons: - The selected VPI value is unavailable, - The selected VPI value is in use. Otherwise, the agent creates a row and reserves the VPI value on that port. (2) The manager selects an existing row(s) in the atmTrafficDescrParamTable, thereby, selecting a set of self-consistent ATM traffic parameters and the service category for receive and transmit directions of the VPL. (2a) If no suitable row(s) in the atmTrafficDescrParamTable exists, the manager must create a new row(s) in that table. (2b) The manager characterizes the VPL's traffic parameters through setting the atmVplReceiveTrafficDescrIndex and the atmVplTransmitTrafficDescrIndex values in the VPL table, which point to the rows containing desired ATM traffic parameter values in the atmTrafficDescrParamTable. The agent will check the availability of resources and may refuse the request. If the transmit and receive service categories are inconsistent, the agent should refuse the request. (3) The manager activates the VPL by setting the the atmVplRowStatus to active(1). If this set is successful, the agent has reserved the resources to satisfy the requested traffic parameter values and the service category for that VPL. (4) If the VPL terminates a VPC in the ATM host or switch, the manager turns on the atmVplAdminStatus to up(1) to turn the VPL traffic flow on. Otherwise, the atmVpCrossConnectTable must be used to cross-connect the VPL to another VPL(s) in an ATM switch or network. One-Shot VPL Establishment A VPL may also be established in one step by a set-request with all necessary VPL parameter values and atmVplRowStatus set to createAndGo(4). In contrast to the negotiated VPL establishment which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VPL establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VPL Retirement A VPL is released by setting atmVplRowStatus to destroy(6), and the agent may release all associated resources.
.1.3.6.1.2.1.37.1.6.1.1,ATM-MIB::atmVplVpi,INTEGER,not-accessible,,current,,The VPI value of the VPL.
.1.3.6.1.2.1.37.1.6.1.2,ATM-MIB::atmVplAdminStatus,INTEGER,read-create,,current,up(1):down(2),This object is instanciated only for a VPL which terminates a VPC (i.e., one which is NOT cross-connected to other VPLs). Its value specifies the desired administrative state of the VPL.
.1.3.6.1.2.1.37.1.6.1.3,ATM-MIB::atmVplOperStatus,INTEGER,read-only,,current,up(1):down(2):unknown(3),The current operational status of the VPL.
.1.3.6.1.2.1.37.1.6.1.4,ATM-MIB::atmVplLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this VPL entered its current operational state.
.1.3.6.1.2.1.37.1.6.1.5,ATM-MIB::atmVplReceiveTrafficDescrIndex,INTEGER,read-create,,current,,The value of this object identifies the row in the atmTrafficDescrParamTable which applies to the receive direction of the VPL.
.1.3.6.1.2.1.37.1.6.1.6,ATM-MIB::atmVplTransmitTrafficDescrIndex,INTEGER,read-create,,current,,The value of this object identifies the row in the atmTrafficDescrParamTable which applies to the transmit direction of the VPL.
.1.3.6.1.2.1.37.1.6.1.7,ATM-MIB::atmVplCrossConnectIdentifier,INTEGER,read-only,,current,,This object is instantiated only for a VPL which is cross-connected to other VPLs that belong to the same VPC. All such associated VPLs have the same value of this object, and all their cross-connections are identified either by entries that are indexed by the same value of atmVpCrossConnectIndex in the atmVpCrossConnectTable of this MIB module or by the same value of the cross-connect index in the cross-connect table for SVCs and Soft PVCs (defined in a separate MIB module). At no time should entries in these respective cross-connect tables exist simultaneously with the same cross-connect index value. The value of this object is initialized by the agent after the associated entries in the atmVpCrossConnectTable have been created.
.1.3.6.1.2.1.37.1.6.1.8,ATM-MIB::atmVplRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, delete or modify a row in this table. To create a new VCL, this object is initially set to 'createAndWait' or 'createAndGo'. This object should not be set to 'active' unless the following columnar objects have been set to their desired value in this row: atmVplReceiveTrafficDescrIndex and atmVplTransmitTrafficDescrIndex. The DESCRIPTION of atmVplEntry provides further guidance to row treatment in this table.
.1.3.6.1.2.1.37.1.6.1.9,ATM-MIB::atmVplCastType,INTEGER,read-create,,current,p2p(1):p2mpRoot(2):p2mpLeaf(3),The connection topology type.
.1.3.6.1.2.1.37.1.6.1.10,ATM-MIB::atmVplConnKind,INTEGER,read-create,,current,pvc(1):svcIncoming(2):svcOutgoing(3):spvcInitiator(4):spvcTarget(5),The use of call control.
.1.3.6.1.2.1.37.1.7,ATM-MIB::atmVclTable,,not-accessible,,current,,The Virtual Channel Link (VCL) table. A bi-directional VCL is modeled as one entry in this table. This table can be used for PVCs, SVCs and Soft PVCs.
.1.3.6.1.2.1.37.1.7.1,ATM-MIB::atmVclEntry,,not-accessible,ifIndex:atmVclVpi:atmVclVci,current,,An entry in the VCL table. This entry is used to model a bi-directional VCL. To create a VCL at an ATM interface, either of the following procedures are used: Negotiated VCL establishment (1) The management application creates a VCL entry in the atmVclTable by setting atmVclRowStatus to createAndWait(5). This may fail for the following reasons: - The selected VPI/VCI values are unavailable, - The selected VPI/VCI values are in use. Otherwise, the agent creates a row and reserves the VPI/VCI values on that port. (2) The manager selects an existing row(s) in the atmTrafficDescrParamTable, thereby, selecting a set of self-consistent ATM traffic parameters and the service category for receive and transmit directions of the VCL. (2a) If no suitable row(s) in the atmTrafficDescrParamTable exists, the manager must create a new row(s) in that table. (2b) The manager characterizes the VCL's traffic parameters through setting the atmVclReceiveTrafficDescrIndex and the atmVclTransmitTrafficDescrIndex values in the VCL table, which point to the rows containing desired ATM traffic parameter values in the atmTrafficDescrParamTable. The agent will check the availability of resources and may refuse the request. If the transmit and receive service categories are inconsistent, the agent should refuse the request. (3) The manager activates the VCL by setting the the atmVclRowStatus to active(1) (for requirements on this activation see the description of atmVclRowStatus). If this set is successful, the agent has reserved the resources to satisfy the requested traffic parameter values and the service category for that VCL. (4) If the VCL terminates a VCC in the ATM host or switch, the manager turns on the atmVclAdminStatus to up(1) to turn the VCL traffic flow on. Otherwise, the atmVcCrossConnectTable must be used to cross-connect the VCL to another VCL(s) in an ATM switch or network. One-Shot VCL Establishment A VCL may also be established in one step by a set-request with all necessary VCL parameter values and atmVclRowStatus set to createAndGo(4). In contrast to the negotiated VCL establishment which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VCL establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VCL Retirement A VCL is released by setting atmVclRowStatus to destroy(6), and the agent may release all associated resources.
.1.3.6.1.2.1.37.1.7.1.1,ATM-MIB::atmVclVpi,INTEGER,not-accessible,,current,,The VPI value of the VCL.
.1.3.6.1.2.1.37.1.7.1.2,ATM-MIB::atmVclVci,INTEGER,not-accessible,,current,,The VCI value of the VCL.
.1.3.6.1.2.1.37.1.7.1.3,ATM-MIB::atmVclAdminStatus,INTEGER,read-create,,current,up(1):down(2),This object is instanciated only for a VCL which terminates a VCC (i.e., one which is NOT cross-connected to other VCLs). Its value specifies the desired administrative state of the VCL.
.1.3.6.1.2.1.37.1.7.1.4,ATM-MIB::atmVclOperStatus,INTEGER,read-only,,current,up(1):down(2):unknown(3),The current operational status of the VCL.
.1.3.6.1.2.1.37.1.7.1.5,ATM-MIB::atmVclLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this VCL entered its current operational state.
.1.3.6.1.2.1.37.1.7.1.6,ATM-MIB::atmVclReceiveTrafficDescrIndex,INTEGER,read-create,,current,,The value of this object identifies the row in the ATM Traffic Descriptor Table which applies to the receive direction of this VCL.
.1.3.6.1.2.1.37.1.7.1.7,ATM-MIB::atmVclTransmitTrafficDescrIndex,INTEGER,read-create,,current,,The value of this object identifies the row of the ATM Traffic Descriptor Table which applies to the transmit direction of this VCL.
.1.3.6.1.2.1.37.1.7.1.8,ATM-MIB::atmVccAalType,INTEGER,read-create,,current,aal1(1):aal34(2):aal5(3):other(4):unknown(5):aal2(6),An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL is in use. The type of AAL used on this VCC. The AAL type includes AAL1, AAL2, AAL3/4, and AAL5. The other(4) may be user-defined AAL type. The unknown type indicates that the AAL type cannot be determined.
.1.3.6.1.2.1.37.1.7.1.9,ATM-MIB::atmVccAal5CpcsTransmitSduSize,INTEGER,read-create,,current,,An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The maximum AAL5 CPCS SDU size in octets that is supported on the transmit direction of this VCC.
.1.3.6.1.2.1.37.1.7.1.10,ATM-MIB::atmVccAal5CpcsReceiveSduSize,INTEGER,read-create,,current,,An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The maximum AAL5 CPCS SDU size in octets that is supported on the receive direction of this VCC.
.1.3.6.1.2.1.37.1.7.1.11,ATM-MIB::atmVccAal5EncapsType,INTEGER,read-create,,current,vcMultiplexRoutedProtocol(1):vcMultiplexBridgedProtocol8023(2):vcMultiplexBridgedProtocol8025(3):vcMultiplexBridgedProtocol8026(4):vcMultiplexLANemulation8023(5):vcMultiplexLANemulation8025(6):llcEncapsulation(7):multiprotocolFrameRelaySscs(8):other(9):unknown(10),An instance of this object only exists when the local VCL end-point is also the VCC end-point, and AAL5 is in use. The type of data encapsulation used over the AAL5 SSCS layer. The definitions reference RFC 1483 Multiprotocol Encapsulation over ATM AAL5 and to the ATM Forum LAN Emulation specification.
.1.3.6.1.2.1.37.1.7.1.12,ATM-MIB::atmVclCrossConnectIdentifier,INTEGER,read-only,,current,,This object is instantiated only for a VCL which is cross-connected to other VCLs that belong to the same VCC. All such associated VCLs have the same value of this object, and all their cross-connections are identified either by entries that are indexed by the same value of atmVcCrossConnectIndex in the atmVcCrossConnectTable of this MIB module or by the same value of the cross-connect index in the cross-connect table for SVCs and Soft PVCs (defined in a separate MIB module). At no time should entries in these respective cross-connect tables exist simultaneously with the same cross-connect index value. The value of this object is initialized by the agent after the associated entries in the atmVcCrossConnectTable have been created.
.1.3.6.1.2.1.37.1.7.1.13,ATM-MIB::atmVclRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, delete or modify a row in this table. To create a new VCL, this object is initially set to 'createAndWait' or 'createAndGo'. This object should not be set to 'active' unless the following columnar objects have been set to their desired value in this row: atmVclReceiveTrafficDescrIndex, atmVclTransmitTrafficDescrIndex. In addition, if the local VCL end-point is also the VCC end-point: atmVccAalType. In addition, for AAL5 connections only: atmVccAal5CpcsTransmitSduSize, atmVccAal5CpcsReceiveSduSize, and atmVccAal5EncapsType. (The existence of these objects imply the AAL connection type.). The DESCRIPTION of atmVclEntry provides further guidance to row treatment in this table.
.1.3.6.1.2.1.37.1.7.1.14,ATM-MIB::atmVclCastType,INTEGER,read-create,,current,p2p(1):p2mpRoot(2):p2mpLeaf(3),The connection topology type.
.1.3.6.1.2.1.37.1.7.1.15,ATM-MIB::atmVclConnKind,INTEGER,read-create,,current,pvc(1):svcIncoming(2):svcOutgoing(3):spvcInitiator(4):spvcTarget(5),The use of call control.
.1.3.6.1.2.1.37.1.8,ATM-MIB::atmVpCrossConnectIndexNext,INTEGER,read-only,,current,,This object contains an appropriate value to be used for atmVpCrossConnectIndex when creating entries in the atmVpCrossConnectTable. The value 0 indicates that no unassigned entries are available. To obtain the atmVpCrossConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.37.1.9,ATM-MIB::atmVpCrossConnectTable,,not-accessible,,current,,The ATM VP Cross Connect table for PVCs. An entry in this table models two cross-connected VPLs. Each VPL must have its atmConnKind set to pvc(1).
.1.3.6.1.2.1.37.1.9.1,ATM-MIB::atmVpCrossConnectEntry,,not-accessible,atmVpCrossConnectIndex:atmVpCrossConnectLowIfIndex:atmVpCrossConnectLowVpi:atmVpCrossConnectHighIfIndex:atmVpCrossConnectHighVpi,current,,An entry in the ATM VP Cross Connect table. This entry is used to model a bi-directional ATM VP cross-connect which cross-connects two VPLs. Step-wise Procedures to set up a VP Cross-connect Once the entries in the atmVplTable are created, the following procedures are used to cross-connect the VPLs together. (1) The manager obtains a unique atmVpCrossConnectIndex by reading the atmVpCrossConnectIndexNext object. (2) Next, the manager creates a set of one or more rows in the ATM VP Cross Connect Table, one for each cross-connection between two VPLs. Each row is indexed by the ATM interface port numbers and VPI values of the two ends of that cross-connection. This set of rows specifies the topology of the VPC cross-connect and is identified by a single value of atmVpCrossConnectIndex. Negotiated VP Cross-Connect Establishment (2a) The manager creates a row in this table by setting atmVpCrossConnectRowStatus to createAndWait(5). The agent checks the requested topology and the mutual sanity of the ATM traffic parameters and service categories, i.e., the row creation fails if: - the requested topology is incompatible with associated values of atmVplCastType, - the requested topology is not supported by the agent, - the traffic/service category parameter values associated with the requested row are incompatible with those of already existing rows for this VP cross-connect. [For example, for setting up a point-to-point VP cross-connect, the ATM traffic parameters in the receive direction of a VPL at the low end of the cross-connect must equal to the traffic parameters in the transmit direction of the other VPL at the high end of the cross-connect, otherwise, the row creation fails.] The agent also checks for internal errors in building the cross-connect. The atmVpCrossConnectIndex values in the corresponding atmVplTable rows are filled in by the agent at this point. (2b) The manager promotes the row in the atmVpCrossConnectTable by setting atmVpCrossConnectRowStatus to active(1). If this set is successful, the agent has reserved the resources specified by the ATM traffic parameter and Service category values for each direction of the VP cross-connect in an ATM switch or network. (3) The manager sets the atmVpCrossConnectAdminStatus to up(1) in all rows of this VP cross-connect to turn the traffic flow on. One-Shot VP Cross-Connect Establishment A VP cross-connect may also be established in one step by a set-request with all necessary parameter values and atmVpCrossConnectRowStatus set to createAndGo(4). In contrast to the negotiated VP cross-connect establishment which allows for detailed error checking (i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VP cross-connect establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VP Cross-Connect Retirement A VP cross-connect identified by a particular value of atmVpCrossConnectIndex is released by: (1) Setting atmVpCrossConnectRowStatus of all rows identified by this value of atmVpCrossConnectIndex to destroy(6). The agent may release all associated resources, and the atmVpCrossConnectIndex values in the corresponding atmVplTable row are removed. Note that a situation when only a subset of the associated rows are delete
.1.3.6.1.2.1.37.1.9.1.1,ATM-MIB::atmVpCrossConnectIndex,INTEGER,not-accessible,,current,,A unique value to identify this VP cross-connect. For each VPL associated with this cross-connect, the agent reports this cross-connect index value in the atmVplCrossConnectIdentifier attribute of the corresponding atmVplTable entries.
.1.3.6.1.2.1.37.1.9.1.2,ATM-MIB::atmVpCrossConnectLowIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the ATM interface for this VP cross-connect. The term low implies that this ATM interface has the numerically lower ifIndex value than the other ATM interface identified in the same atmVpCrossConnectEntry.
.1.3.6.1.2.1.37.1.9.1.3,ATM-MIB::atmVpCrossConnectLowVpi,INTEGER,not-accessible,,current,,The VPI value at the ATM interface associated with the VP cross-connect that is identified by atmVpCrossConnectLowIfIndex.
.1.3.6.1.2.1.37.1.9.1.4,ATM-MIB::atmVpCrossConnectHighIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the ATM interface for this VP cross-connect. The term high implies that this ATM interface has the numerically higher ifIndex value than the other ATM interface identified in the same atmVpCrossConnectEntry.
.1.3.6.1.2.1.37.1.9.1.5,ATM-MIB::atmVpCrossConnectHighVpi,INTEGER,not-accessible,,current,,The VPI value at the ATM interface associated with the VP cross-connect that is identified by atmVpCrossConnectHighIfIndex.
.1.3.6.1.2.1.37.1.9.1.6,ATM-MIB::atmVpCrossConnectAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired administrative status of this bi-directional VP cross-connect.
.1.3.6.1.2.1.37.1.9.1.7,ATM-MIB::atmVpCrossConnectL2HOperStatus,INTEGER,read-only,,current,up(1):down(2):unknown(3),The operational status of the VP cross-connect in one direction; (i.e., from the low to high direction).
.1.3.6.1.2.1.37.1.9.1.8,ATM-MIB::atmVpCrossConnectH2LOperStatus,INTEGER,read-only,,current,up(1):down(2):unknown(3),The operational status of the VP cross-connect in one direction; (i.e., from the high to low direction).
.1.3.6.1.2.1.37.1.9.1.9,ATM-MIB::atmVpCrossConnectL2HLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this VP cross-connect entered its current operational state in the low to high direction.
.1.3.6.1.2.1.37.1.9.1.10,ATM-MIB::atmVpCrossConnectH2LLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this VP cross-connect entered its current operational in the high to low direction.
.1.3.6.1.2.1.37.1.9.1.11,ATM-MIB::atmVpCrossConnectRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry in the atmVpCrossConnectTable. This object is used to create a cross-connect for cross-connecting VPLs which are created using the atmVplTable or to change or delete an existing cross-connect. This object must be initially set to `createAndWait' or 'createAndGo'. To turn on a VP cross-connect, the atmVpCrossConnectAdminStatus is set to `up'.
.1.3.6.1.2.1.37.1.10,ATM-MIB::atmVcCrossConnectIndexNext,INTEGER,read-only,,current,,This object contains an appropriate value to be used for atmVcCrossConnectIndex when creating entries in the atmVcCrossConnectTable. The value 0 indicates that no unassigned entries are available. To obtain the atmVcCrossConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.37.1.11,ATM-MIB::atmVcCrossConnectTable,,not-accessible,,current,,The ATM VC Cross Connect table for PVCs. An entry in this table models two cross-connected VCLs. Each VCL must have its atmConnKind set to pvc(1).
.1.3.6.1.2.1.37.1.11.1,ATM-MIB::atmVcCrossConnectEntry,,not-accessible,atmVcCrossConnectIndex:atmVcCrossConnectLowIfIndex:atmVcCrossConnectLowVpi:atmVcCrossConnectLowVci:atmVcCrossConnectHighIfIndex:atmVcCrossConnectHighVpi:atmVcCrossConnectHighVci,current,,An entry in the ATM VC Cross Connect table. This entry is used to model a bi-directional ATM VC cross-connect cross-connecting two end points. Step-wise Procedures to set up a VC Cross-connect Once the entries in the atmVclTable are created, the following procedures are used to cross-connect the VCLs together to form a VCC segment. (1) The manager obtains a unique atmVcCrossConnectIndex by reading the atmVcCrossConnectIndexNext object. (2) Next, the manager creates a set of one or more rows in the ATM VC Cross Connect Table, one for each cross-connection between two VCLs. Each row is indexed by the ATM interface port numbers and VPI/VCI values of the two ends of that cross-connection. This set of rows specifies the topology of the VCC cross-connect and is identified by a single value of atmVcCrossConnectIndex. Negotiated VC Cross-Connect Establishment (2a) The manager creates a row in this table by setting atmVcCrossConnectRowStatus to createAndWait(5). The agent checks the requested topology and the mutual sanity of the ATM traffic parameters and service categories, i.e., the row creation fails if: - the requested topology is incompatible with associated values of atmVclCastType, - the requested topology is not supported by the agent, - the traffic/service category parameter values associated with the requested row are incompatible with those of already existing rows for this VC cross-connect. [For example, for setting up a point-to-point VC cross-connect, the ATM traffic parameters in the receive direction of a VCL at the low end of the cross-connect must equal to the traffic parameters in the transmit direction of the other VCL at the high end of the cross-connect, otherwise, the row creation fails.] The agent also checks for internal errors in building the cross-connect. The atmVcCrossConnectIndex values in the corresponding atmVclTable rows are filled in by the agent at this point. (2b) The manager promotes the row in the atmVcCrossConnectTable by setting atmVcCrossConnectRowStatus to active(1). If this set is successful, the agent has reserved the resources specified by the ATM traffic parameter and Service category values for each direction of the VC cross-connect in an ATM switch or network. (3) The manager sets the atmVcCrossConnectAdminStatus to up(1) in all rows of this VC cross-connect to turn the traffic flow on. One-Shot VC Cross-Connect Establishment A VC cross-connect may also be established in one step by a set-request with all necessary parameter values and atmVcCrossConnectRowStatus set to createAndGo(4). In contrast to the negotiated VC cross-connect establishment which allows for detailed error checking i.e., set errors are explicitly linked to particular resource acquisition failures), the one-shot VC cross-connect establishment performs the setup on one operation but does not have the advantage of step-wise error checking. VC Cross-Connect Retirement A VC cross-connect identified by a particular value of atmVcCrossConnectIndex is released by: (1) Setting atmVcCrossConnectRowStatus of all rows identified by this value of atmVcCrossConnectIndex to destroy(6). The agent may release all associated resources, and the atmVcCrossConnectIndex values in the corresponding atmVclTable row are removed. Note that a situation when only a subset of 
.1.3.6.1.2.1.37.1.11.1.1,ATM-MIB::atmVcCrossConnectIndex,INTEGER,not-accessible,,current,,A unique value to identify this VC cross-connect. For each VCL associated with this cross-connect, the agent reports this cross-connect index value in the atmVclCrossConnectIdentifier attribute of the corresponding atmVclTable entries.
.1.3.6.1.2.1.37.1.11.1.2,ATM-MIB::atmVcCrossConnectLowIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the ATM interface for this VC cross-connect. The term low implies that this ATM interface has the numerically lower ifIndex value than the other ATM interface identified in the same atmVcCrossConnectEntry.
.1.3.6.1.2.1.37.1.11.1.3,ATM-MIB::atmVcCrossConnectLowVpi,INTEGER,not-accessible,,current,,The VPI value at the ATM interface associated with the VC cross-connect that is identified by atmVcCrossConnectLowIfIndex.
.1.3.6.1.2.1.37.1.11.1.4,ATM-MIB::atmVcCrossConnectLowVci,INTEGER,not-accessible,,current,,The VCI value at the ATM interface associated with this VC cross-connect that is identified by atmVcCrossConnectLowIfIndex.
.1.3.6.1.2.1.37.1.11.1.5,ATM-MIB::atmVcCrossConnectHighIfIndex,Integer32,not-accessible,,current,,The ifIndex value for the ATM interface for this VC cross-connect. The term high implies that this ATM interface has the numerically higher ifIndex value than the other ATM interface identified in the same atmVcCrossConnectEntry.
.1.3.6.1.2.1.37.1.11.1.6,ATM-MIB::atmVcCrossConnectHighVpi,INTEGER,not-accessible,,current,,The VPI value at the ATM interface associated with the VC cross-connect that is identified by atmVcCrossConnectHighIfIndex.
.1.3.6.1.2.1.37.1.11.1.7,ATM-MIB::atmVcCrossConnectHighVci,INTEGER,not-accessible,,current,,The VCI value at the ATM interface associated with the VC cross-connect that is identified by atmVcCrossConnectHighIfIndex.
.1.3.6.1.2.1.37.1.11.1.8,ATM-MIB::atmVcCrossConnectAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired administrative status of this bi-directional VC cross-connect.
.1.3.6.1.2.1.37.1.11.1.9,ATM-MIB::atmVcCrossConnectL2HOperStatus,INTEGER,read-only,,current,up(1):down(2):unknown(3),The current operational status of the VC cross-connect in one direction; (i.e., from the low to high direction).
.1.3.6.1.2.1.37.1.11.1.10,ATM-MIB::atmVcCrossConnectH2LOperStatus,INTEGER,read-only,,current,up(1):down(2):unknown(3),The current operational status of the VC cross-connect in one direction; (i.e., from the high to low direction).
.1.3.6.1.2.1.37.1.11.1.11,ATM-MIB::atmVcCrossConnectL2HLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this VC cross-connect entered its current operational state in low to high direction.
.1.3.6.1.2.1.37.1.11.1.12,ATM-MIB::atmVcCrossConnectH2LLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this VC cross-connect entered its current operational state in high to low direction.
.1.3.6.1.2.1.37.1.11.1.13,ATM-MIB::atmVcCrossConnectRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry in the atmVcCrossConnectTable. This object is used to create a new cross-connect for cross-connecting VCLs which are created using the atmVclTable or to change or delete existing cross-connect. This object must be initially set to `createAndWait' or 'createAndGo'. To turn on a VC cross-connect, the atmVcCrossConnectAdminStatus is set to `up'.
.1.3.6.1.2.1.37.1.12,ATM-MIB::aal5VccTable,,not-accessible,,current,,This table contains AAL5 VCC performance parameters.
.1.3.6.1.2.1.37.1.12.1,ATM-MIB::aal5VccEntry,,not-accessible,ifIndex:aal5VccVpi:aal5VccVci,current,,This list contains the AAL5 VCC performance parameters and is indexed by ifIndex values of AAL5 interfaces and the associated VPI/VCI values.
.1.3.6.1.2.1.37.1.12.1.1,ATM-MIB::aal5VccVpi,INTEGER,not-accessible,,current,,The VPI value of the AAL5 VCC at the interface identified by the ifIndex.
.1.3.6.1.2.1.37.1.12.1.2,ATM-MIB::aal5VccVci,INTEGER,not-accessible,,current,,The VCI value of the AAL5 VCC at the interface identified by the ifIndex.
.1.3.6.1.2.1.37.1.12.1.3,ATM-MIB::aal5VccCrcErrors,Counter32,read-only,,current,,The number of AAL5 CPCS PDUs received with CRC-32 errors on this AAL5 VCC at the interface associated with an AAL5 entity.
.1.3.6.1.2.1.37.1.12.1.4,ATM-MIB::aal5VccSarTimeOuts,Counter32,read-only,,current,,The number of partially re-assembled AAL5 CPCS PDUs which were discarded on this AAL5 VCC at the interface associated with an AAL5 entity because they were not fully re-assembled within the required time period. If the re-assembly timer is not supported, then this object contains a zero value.
.1.3.6.1.2.1.37.1.12.1.5,ATM-MIB::aal5VccOverSizedSDUs,Counter32,read-only,,current,,The number of AAL5 CPCS PDUs discarded on this AAL5 VCC at the interface associated with an AAL5 entity because the AAL5 SDUs were too large.
.1.3.6.1.2.1.37.1.13,ATM-MIB::atmTrafficDescrParamIndexNext,INTEGER,read-only,,current,,This object contains an appropriate value to be used for atmTrafficDescrParamIndex when creating entries in the atmTrafficDescrParamTable. The value 0 indicates that no unassigned entries are available. To obtain the atmTrafficDescrParamIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.37.1.14,ATM2-MIB::atm2MIB,,,,,,Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3606; see the RFC itself for full legal notices. This MIB Module is a supplement to the ATM-MIB defined in RFC 2515.
.1.3.6.1.2.1.37.1.14.1,ATM2-MIB::atm2MIBObjects,,,,,,
.1.3.6.1.2.1.37.1.14.1.1,ATM2-MIB::atmSvcVpCrossConnectTable,,not-accessible,,current,,The ATM SVPC Cross-Connect table. A bi-directional VP cross-connect between two switched VPLs is modeled as one entry in this table. A Soft PVPC cross-connect, between a soft permanent VPL and a switched VPL, is also modeled as one entry in this table.
.1.3.6.1.2.1.37.1.14.1.1.1,ATM2-MIB::atmSvcVpCrossConnectEntry,,not-accessible,atmSvcVpCrossConnectIndex:atmSvcVpCrossConnectLowIfIndex:atmSvcVpCrossConnectLowVpi:atmSvcVpCrossConnectHighIfIndex:atmSvcVpCrossConnectHighVpi,current,,An entry in the ATM SVPC Cross-Connect table. This entry is used to model a bi-directional ATM VP cross-connect between two VPLs.
.1.3.6.1.2.1.37.1.14.1.1.1.1,ATM2-MIB::atmSvcVpCrossConnectIndex,INTEGER,not-accessible,,current,,A unique value to identify this SVPC cross-connect. For each VP associated with this cross-connect, the agent reports this cross-connect index value in the atmVplCrossConnectIdentifer attribute of the corresponding atmVplTable entries.
.1.3.6.1.2.1.37.1.14.1.1.1.2,ATM2-MIB::atmSvcVpCrossConnectLowIfIndex,Integer32,not-accessible,,current,,The value of this object is equal to the ifIndex value of the ATM interface port for this SVPC cross-connect. The term low implies that this ATM interface has the numerically lower ifIndex value than the other ATM interface identified in the same atmSvcVpCrossConnectEntry.
.1.3.6.1.2.1.37.1.14.1.1.1.3,ATM2-MIB::atmSvcVpCrossConnectLowVpi,INTEGER,not-accessible,,current,,The value of this object is equal to the VPI value associated with the SVPC cross-connect at the ATM interface that is identified by atmSvcVpCrossConnectLowIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvpcVpi at the low ATM interface port.
.1.3.6.1.2.1.37.1.14.1.1.1.4,ATM2-MIB::atmSvcVpCrossConnectHighIfIndex,Integer32,not-accessible,,current,,The value of this object is equal to the ifIndex value of the ATM interface port for this SVC VP cross-connect. The term high implies that this ATM interface has the numerically higher ifIndex value than the other ATM interface identified in the same atmSvcVpCrossConnectEntry.
.1.3.6.1.2.1.37.1.14.1.1.1.5,ATM2-MIB::atmSvcVpCrossConnectHighVpi,INTEGER,not-accessible,,current,,The value of this object is equal to the VPI value associated with the SVPC cross-connect at the ATM interface that is identified by atmSvcVpCrossConnectHighIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvpcVpi at the high ATM interface port.
.1.3.6.1.2.1.37.1.14.1.1.1.6,ATM2-MIB::atmSvcVpCrossConnectCreationTime,TimeTicks,read-only,,current,,The value of the sysUpTime object at the time this bi-directional SVPC cross-connect was created. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
.1.3.6.1.2.1.37.1.14.1.1.1.7,ATM2-MIB::atmSvcVpCrossConnectRowStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to delete rows in the atmSvcVpCrossConnectTable.
.1.3.6.1.2.1.37.1.14.1.2,ATM2-MIB::atmSvcVcCrossConnectTable,,not-accessible,,current,,The ATM SVCC Cross-Connect table. A bi-directional VC cross-connect between two switched VCLs is modeled as one entry in this table. A Soft PVCC cross-connect, between a soft permanent VCL and a switched VCL, is also modeled as one entry in this table.
.1.3.6.1.2.1.37.1.14.1.2.1,ATM2-MIB::atmSvcVcCrossConnectEntry,,not-accessible,atmSvcVcCrossConnectIndex:atmSvcVcCrossConnectLowIfIndex:atmSvcVcCrossConnectLowVpi:atmSvcVcCrossConnectLowVci:atmSvcVcCrossConnectHighIfIndex:atmSvcVcCrossConnectHighVpi:atmSvcVcCrossConnectHighVci,current,,An entry in the ATM SVCC Cross-Connect table. This entry is used to model a bi-directional ATM VC cross-connect between two VCLs.
.1.3.6.1.2.1.37.1.14.1.2.1.1,ATM2-MIB::atmSvcVcCrossConnectIndex,INTEGER,not-accessible,,current,,A unique value to identify this SVCC cross-connect. For each VP associated with this cross-connect, the agent reports this cross-connect index value in the atmVclCrossConnectIdentifier attribute of the corresponding atmVplTable entries.
.1.3.6.1.2.1.37.1.14.1.2.1.2,ATM2-MIB::atmSvcVcCrossConnectLowIfIndex,Integer32,not-accessible,,current,,The value of this object is equal to the ifIndex value of the ATM interface port for this SVCC cross-connect. The term low implies that this ATM interface has the numerically lower ifIndex value than the other ATM interface identified in the same atmSvcVcCrossConnectEntry.
.1.3.6.1.2.1.37.1.14.1.2.1.3,ATM2-MIB::atmSvcVcCrossConnectLowVpi,INTEGER,not-accessible,,current,,The value of this object is equal to the VPI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectLowIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvccVpi at the low ATM interface port.
.1.3.6.1.2.1.37.1.14.1.2.1.4,ATM2-MIB::atmSvcVcCrossConnectLowVci,INTEGER,not-accessible,,current,,The value of this object is equal to the VCI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectLowIfIndex. The VCI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvccVci at the low ATM interface port.
.1.3.6.1.2.1.37.1.14.1.2.1.5,ATM2-MIB::atmSvcVcCrossConnectHighIfIndex,Integer32,not-accessible,,current,,The value of this object is equal to the ifIndex value for the ATM interface port for this SVCC cross-connect. The term high implies that this ATM interface has the numerically higher ifIndex value than the other ATM interface identified in the same atmSvcVcCrossConnectEntry.
.1.3.6.1.2.1.37.1.14.1.2.1.6,ATM2-MIB::atmSvcVcCrossConnectHighVpi,INTEGER,not-accessible,,current,,The value of this object is equal to the VPI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectHighIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvccVpi at the high ATM interface port.
.1.3.6.1.2.1.37.1.14.1.2.1.7,ATM2-MIB::atmSvcVcCrossConnectHighVci,INTEGER,not-accessible,,current,,The value of this object is equal to the VCI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectHighIfIndex. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the high ATM interface port.
.1.3.6.1.2.1.37.1.14.1.2.1.8,ATM2-MIB::atmSvcVcCrossConnectCreationTime,TimeTicks,read-only,,current,,The value of the sysUpTime object at the time this bi-directional SVCC cross-connect was created. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.
.1.3.6.1.2.1.37.1.14.1.2.1.9,ATM2-MIB::atmSvcVcCrossConnectRowStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to delete rows in the atmSvcVcCrossConnectTable.
.1.3.6.1.2.1.37.1.14.1.3,ATM2-MIB::atmSigStatTable,,not-accessible,,current,,This table contains ATM interface signalling statistics, one entry per ATM signalling interface.
.1.3.6.1.2.1.37.1.14.1.3.1,ATM2-MIB::atmSigStatEntry,,not-accessible,ifIndex,current,,This list contains signalling statistics variables.
.1.3.6.1.2.1.37.1.14.1.3.1.1,ATM2-MIB::atmSigSSCOPConEvents,Counter32,read-only,,current,,SSCOP Connection Events Counter. This counter counts the sum of the following errors: 1) SSCOP Connection Disconnect Counter The abnormal occurrence of this event is characterized by the expiry of Timer_NO_RESPONSE. (This event is communicated to the layer management with MAA-ERROR code P. See ITU-T Q.2110.) 2) SSCOP Connection Initiation Failure This condition indicates the inability to establish an SSCOP connection. This event occurs whenever the number of expiries of the connection control timer (Timer_CC) equals or exceeds the MaxCC, or upon receipt of a connection reject message BGREJ PDU. (This event is communicated to layer management with MAA-ERROR code O. See ITU-T Q.2110.) 3) SSCOP Connection Re-Establ/Resynch This event occurs upon receipt of a BGN PDU or RS PDU.
.1.3.6.1.2.1.37.1.14.1.3.1.2,ATM2-MIB::atmSigSSCOPErrdPdus,Counter32,read-only,,current,,SSCOP Errored PDUs Counter. This counter counts the sum of the following errors: 1) Invalid PDUs. These are defined in SSCOP and consist of PDUs with an incorrect length (MAA-ERROR code U), an undefined PDU type code, or that are not 32-bit aligned. 2) PDUs that result in MAA-ERROR codes and are discarded. See MAA-ERROR codes A-D, F-M, and Q-T defined in ITU-T Q.2110.
.1.3.6.1.2.1.37.1.14.1.3.1.3,ATM2-MIB::atmSigDetectSetupAttempts,Counter32,read-only,,current,,Call Setup Attempts Counter. This counter counts the number of call setup attempts (both successful and unsuccessful) detected on this interface.
.1.3.6.1.2.1.37.1.14.1.3.1.4,ATM2-MIB::atmSigEmitSetupAttempts,Counter32,read-only,,current,,Call Setup Attempts Counter. This counter counts the number of call setup attempts (both successful and unsuccessful) transmitted on this interface.
.1.3.6.1.2.1.37.1.14.1.3.1.5,ATM2-MIB::atmSigDetectUnavailRoutes,Counter32,read-only,,current,,Number of Route Unavailability detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.6,ATM2-MIB::atmSigEmitUnavailRoutes,Counter32,read-only,,message,,Number of Route Unavailability transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.7,ATM2-MIB::atmSigDetectUnavailResrcs,Counter32,read-only,,message,,Number of Resource Unavailability detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.8,ATM2-MIB::atmSigEmitUnavailResrcs,Counter32,read-only,,current,,Number of Resource Unavailability transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.9,ATM2-MIB::atmSigDetectCldPtyEvents,Counter32,read-only,,current,,Number of Called Party Responsible For Unsuccessful Call detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line identification restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure.
.1.3.6.1.2.1.37.1.14.1.3.1.10,ATM2-MIB::atmSigEmitCldPtyEvents,Counter32,read-only,,current,,Number of Called Party Responsible For Unsuccessful Call transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line identification restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure.
.1.3.6.1.2.1.37.1.14.1.3.1.11,ATM2-MIB::atmSigDetectMsgErrors,Counter32,read-only,,current,,Number of Incorrect Messages detected on this interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted, that contain any of the Cause values listed below. - Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: 1. Message with invalid protocol discriminator 2. Message with errors in the call reference I.E. - Bits 5-8 of the first octet not equal to '0000' - Bits 1-4 of the first octet indicating a length other than 3 octets - RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress - SETUP message received with call reference flag incorrectly set to 1 - SETUP message received with a call reference for a call that is already active or in progress. 3. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.12,ATM2-MIB::atmSigEmitMsgErrors,Counter32,read-only,,current,,Number of Incorrect Messages transmitted on this interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted or received, that contain any of the Cause values listed below. - Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: 1. Message with invalid protocol discriminator 2. Message with errors in the call reference I.E. - Bits 5-8 of the first octet not equal to '0000' - Bits 1-4 of the first octet indicating a length other than 3 octets - RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress - SETUP message received with call reference flag incorrectly set to 1 - SETUP message received with a call reference for a call that is already active or in progress. 3. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.13,ATM2-MIB::atmSigDetectClgPtyEvents,Counter32,read-only,,current,,Number of Calling Party Events detected on this interface. This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 78 AAL parameters cannot be supported (UNI3.1 only) 91 invalid transit network selection 93 AAL parameters cannot be supported (UNI3.0 only) NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.14,ATM2-MIB::atmSigEmitClgPtyEvents,Counter32,read-only,,current,,Number of Calling Party Events transmitted from this interface. This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 78 AAL parameters cannot be supported (UNI3.1 only) 91 invalid transit network selection 93 AAL parameters cannot be supported (UNI3.0 only) NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.15,ATM2-MIB::atmSigDetectTimerExpireds,Counter32,read-only,,current,,Number of Timer Expiries detected on this interface. The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The conditions for incrementing this counter are: - Expiry of any network timer - Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.16,ATM2-MIB::atmSigEmitTimerExpireds,Counter32,read-only,,current,,Number of Timer Expiries transmitted from this interface. The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The conditions for incrementing this counter are: - Expiry of any network timer - Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted.
.1.3.6.1.2.1.37.1.14.1.3.1.17,ATM2-MIB::atmSigDetectRestarts,Counter32,read-only,,current,,Number of Restart Activity errors detected on this interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when receiving a RESTART message.
.1.3.6.1.2.1.37.1.14.1.3.1.18,ATM2-MIB::atmSigEmitRestarts,Counter32,read-only,,current,,Number of Restart Activity errors transmitted from this interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when transmitting a RESTART message.
.1.3.6.1.2.1.37.1.14.1.3.1.19,ATM2-MIB::atmSigInEstabls,Counter32,read-only,,current,,Number of SVCs established at this signalling entity for incoming connections.
.1.3.6.1.2.1.37.1.14.1.3.1.20,ATM2-MIB::atmSigOutEstabls,Counter32,read-only,,current,,Number of SVCs established at this signalling entity for outgoing connections.
.1.3.6.1.2.1.37.1.14.1.4,ATM2-MIB::atmSigSupportTable,,not-accessible,,current,,This table contains ATM local interface configuration parameters, one entry per ATM signalling interface.
.1.3.6.1.2.1.37.1.14.1.4.1,ATM2-MIB::atmSigSupportEntry,,not-accessible,ifIndex,current,,This list contains signalling configuration parameters and state variables.
.1.3.6.1.2.1.37.1.14.1.4.1.1,ATM2-MIB::atmSigSupportClgPtyNumDel,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether the Calling Party Number Information Element is transferred to the called party address. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.2,ATM2-MIB::atmSigSupportClgPtySubAddr,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether to accept and transfer the Calling Party Subaddress Information Element from the calling party to the called party. Calling party subaddress information shall only be transferred to the called party if calling party number delivery is enabled (i.e., atmSigSupportClgPtyNumDel = 'enabled(1)'. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.3,ATM2-MIB::atmSigSupportCldPtySubAddr,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether to accept, transfer, and deliver the Called Party Subaddress Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.4,ATM2-MIB::atmSigSupportHiLyrInfo,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether to accept, transfer, and deliver the Broadband High Layer Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.5,ATM2-MIB::atmSigSupportLoLyrInfo,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether to accept, transfer, and deliver the Broadband Low Layer Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.6,ATM2-MIB::atmSigSupportBlliRepeatInd,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether to accept, transfer, and deliver the Broadband Repeat Indicator with two or three instances of the Broadband Low Layer Information Element for low layer information selection from the calling party to the called party. This object's value should always be disabled(2) if the value of atmSigSupportLolyrInfo is disabled(2). The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.7,ATM2-MIB::atmSigSupportAALInfo,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether to accept, transfer, and deliver the ATM Adaptation Layer Parameters Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party.
.1.3.6.1.2.1.37.1.14.1.4.1.8,ATM2-MIB::atmSigSupportPrefCarrier,OCTET,read-write,,current,,This parameter identifies the carrier to which intercarrier calls originated from this interface are routed when transit network selection information is not provided by the calling party. If a Carrier Identification Code (CIC) is used the parameter shall contain the CIC. For three-digit CICs, the first octet shall be '0' and the CIC is contained in the three following octets. If the preferred carrier feature is not supported the value is a zero-length string.
.1.3.6.1.2.1.37.1.14.1.5,ATM2-MIB::atmSigDescrParamTable,,not-accessible,,current,,A table contains signalling capabilities of VCLs except the Traffic Descriptor. Traffic descriptors are described in the atmTrafficDescrParamTable.
.1.3.6.1.2.1.37.1.14.1.5.1,ATM2-MIB::atmSigDescrParamEntry,,not-accessible,atmSigDescrParamIndex,current,,Each entry in this table represents a set of signalling capabilities that can be applied to a VCL. There is no requirement for unique entries, except that the index must be unique.
.1.3.6.1.2.1.37.1.14.1.5.1.1,ATM2-MIB::atmSigDescrParamIndex,INTEGER,not-accessible,,current,,The value of this object is used by the atmVclGenSigDescrIndex object in the atmVclGenTable to identify a row in this table.
.1.3.6.1.2.1.37.1.14.1.5.1.2,ATM2-MIB::atmSigDescrParamAalType,INTEGER,read-create,,current,other(1):aal1(2):aal34(3):aal5(4):userDefined(5):aal2(6),The AAL type. The value of this object is set to other(1) when not defined.
.1.3.6.1.2.1.37.1.14.1.5.1.3,ATM2-MIB::atmSigDescrParamAalSscsType,INTEGER,read-create,,current,other(1):assured(2):nonassured(3):frameRelay(4):null(5),The SSCS type used by this entry.
.1.3.6.1.2.1.37.1.14.1.5.1.4,ATM2-MIB::atmSigDescrParamBhliType,INTEGER,read-create,,current,other(1):iso(2):user(3):hiProfile(4):vendorSpecific(5),The Broadband high layer type.
.1.3.6.1.2.1.37.1.14.1.5.1.5,ATM2-MIB::atmSigDescrParamBhliInfo,OCTET,read-create,,current,,The Broadband high layer information. When atmSigDescrParamBhliType is set to iso(2), the value of this object is a zero length string. When atmSigDescrParamBhliType is set to user(3), the value of this object is an octet string with length ranging from 0 to 8. When atmSigDescrParamBhliType is set to hiProfile(4), the value of this object is a length of 4 octet string containing user to user profile identifier. When atmSigDescrParamBhliType is set to vendorSpecific(5), the value of this object is a length of 7 octet string, where the most significant 3 octets consist of a globally- administered OUI, and the least significant 4 octets are the vender administered application OUI.
.1.3.6.1.2.1.37.1.14.1.5.1.6,ATM2-MIB::atmSigDescrParamBbcConnConf,INTEGER,read-create,,current,ptp(1):ptmp(2),The Broadband bearer capability user plane connection configuration parameter.
.1.3.6.1.2.1.37.1.14.1.5.1.7,ATM2-MIB::atmSigDescrParamBlliLayer2,INTEGER,read-create,,current,other(1):iso1745(2):q921(3):x25linklayer(4):x25multilink(5):lapb(6):hdlcArm(7):hdlcNrm(8):hdlcAbm(9):iso88022(10):x75slp(11):q922(12):userDef(13):iso7776(14),The Broadband low layer information, protocol type of layer 2. The value of this object is other(1) if layer 2 protocol is not used.
.1.3.6.1.2.1.37.1.14.1.5.1.8,ATM2-MIB::atmSigDescrParamBlliLayer3,INTEGER,read-create,,current,other(1):x25pkt(2):isoiec8208(3):x223iso8878(4):isoiec8473(5):t70(6):tr9577(7):userDef(8),The Broadband low layer information, protocol type of layer 3. The value of this object is other(1) if layer 3 protocol is not used.
.1.3.6.1.2.1.37.1.14.1.5.1.9,ATM2-MIB::atmSigDescrParamBlliPktSize,INTEGER,read-create,,current,other(1):s16(2):s32(3):s64(4):s128(5):s256(6):s512(7):s1024(8):s2048(9):s4096(10),The default packet size defined in B-LLI.
.1.3.6.1.2.1.37.1.14.1.5.1.10,ATM2-MIB::atmSigDescrParamBlliSnapId,INTEGER,read-create,,current,other(1):true(2):false(3),The SNAP ID used for Broadband low layer protocol layer 3. The value of this object is other(1) if atmSigDescrParamBlliLayer3 is set to other(1).
.1.3.6.1.2.1.37.1.14.1.5.1.11,ATM2-MIB::atmSigDescrParamBlliOuiPid,OCTET,read-create,,current,,The OUI/PID encoding for Broadband low layer protocol layer 3. The value of this object is a zero length string if atmSigDescrParamBlliLayer3 is set to other(1). When used, it is always 5 octets with the most significant octet as the OUI Octet 1 and the least significant octet as the PID Octet 2.
.1.3.6.1.2.1.37.1.14.1.5.1.12,ATM2-MIB::atmSigDescrParamRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the atmSigDescrParamTable.
.1.3.6.1.2.1.37.1.14.1.6,ATM2-MIB::atmIfRegisteredAddrTable,,not-accessible,,current,,This table contains a list of ATM addresses that can be used for calls to and from a given interface by a switch or service. The ATM addresses are either registered by the endsystem via ILMI or statically configured. This table does not expose PNNI reachability information. ILMI registered addresses cannot be deleted using this table. This table only applies to switches and network services.
.1.3.6.1.2.1.37.1.14.1.6.1,ATM2-MIB::atmIfRegisteredAddrEntry,,not-accessible,ifIndex:atmIfRegAddrAddress,current,,An entry in the ATM Interface Registered Address table.
.1.3.6.1.2.1.37.1.14.1.6.1.1,ATM2-MIB::atmIfRegAddrAddress,OCTET,not-accessible,,current,,An address registered for a given switch or service interface.
.1.3.6.1.2.1.37.1.14.1.6.1.2,ATM2-MIB::atmIfRegAddrAddressSource,INTEGER,read-only,,current,other(1):static(2):dynamic(3),The type of address source for a given ATM Address. The value dynamic(3) is indicated when ILMI is used.
.1.3.6.1.2.1.37.1.14.1.6.1.3,ATM2-MIB::atmIfRegAddrOrgScope,INTEGER,read-create,,current,localNetwork(1):localNetworkPlusOne(2):localNetworkPlusTwo(3):siteMinusOne(4):intraSite(5):sitePlusOne(6):organizationMinusOne(7):intraOrganization(8):organizationPlusOne(9):communityMinusOne(10):intraCommunity(11):communityPlusOne(12):regional(13):interRegional(14):global(15),This object indicates the organizational scope for the referenced address. The information of the referenced address shall not be distributed outside the indicated scope. Refer to Annex 5.3 of ATM Forum UNI Signalling 4.0 for guidelines regarding the use of organizational scopes. This value cannot be configured for ILMI-registered addresses. The default values for organizational scope are localNetwork(1) for ATM group addresses, and global(15) for individual addresses.
.1.3.6.1.2.1.37.1.14.1.6.1.4,ATM2-MIB::atmIfRegAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete rows in the atmIfRegisteredAddrTable. Rows created dynamically (e.g., ILMI- registered addresses) cannot be deleted using this object.
.1.3.6.1.2.1.37.1.14.1.7,ATM2-MIB::atmVclAddrTable,,not-accessible,,current,,This table provides a mapping between the atmVclTable and the ATM called party/calling party address. This table can be used to retrieve the calling party and called party ATM address pair for a given VCL. Note that there can be more than one pair of calling party and called party ATM addresses for a VCL in a point to multi-point call.
.1.3.6.1.2.1.37.1.14.1.7.1,ATM2-MIB::atmVclAddrEntry,,not-accessible,ifIndex:atmVclVpi:atmVclVci:atmVclAddrAddr,current,,Each entry in this table represents a binding between a VCL and an ATM address associated with this call. This ATM address can be either the called party address or the calling party address. There can be more than one pair of calling/called party ATM addresses associated with the VCL entry for point to multi-point calls. Objects atmVclAddrType, and atmVclAddrRowStatus are required during row creation.
.1.3.6.1.2.1.37.1.14.1.7.1.1,ATM2-MIB::atmVclAddrAddr,OCTET,not-accessible,,current,,An ATM address on one end of the VCL. For SVCs, the agent supplies the value of this object at creation time. For PVC VCL, the manager can supply the value of this object during or after the PVC VCL creation.
.1.3.6.1.2.1.37.1.14.1.7.1.2,ATM2-MIB::atmVclAddrType,INTEGER,read-create,,current,callingParty(1):calledParty(2),The type of ATM Address represented by the object atmVclAddrAddr. Choices are either the calling party ATM address or the called party ATM address.
.1.3.6.1.2.1.37.1.14.1.7.1.3,ATM2-MIB::atmVclAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create or destroy an entry from this table. Note that the manager entity can only destroy the PVC VCLs.
.1.3.6.1.2.1.37.1.14.1.8,ATM2-MIB::atmAddrVclTable,,not-accessible,,current,,This table provides an alternative way to retrieve the atmVclTable. This table can be used to retrieve the indexing to the atmVclTable by an ATM address.
.1.3.6.1.2.1.37.1.14.1.8.1,ATM2-MIB::atmAddrVclEntry,,not-accessible,atmVclAddrAddr:atmAddrVclAtmIfIndex:atmAddrVclVpi:atmAddrVclVci,current,,Each entry in this table represents an entry in the atmVclTable of the ATM-MIB by its ATM address. The ATM address is either the calling or called party ATM address of the call. Entries in this table are read only. They show up when entries are created in the atmVclAddrTable.
.1.3.6.1.2.1.37.1.14.1.8.1.1,ATM2-MIB::atmAddrVclAtmIfIndex,Integer32,not-accessible,,current,,The interface index of the ATM interface to which this VCL pertains. This object combined with the atmAddrVclVpi and atmAddrVclVci objects serves as an index to the atmVclTable.
.1.3.6.1.2.1.37.1.14.1.8.1.2,ATM2-MIB::atmAddrVclVpi,INTEGER,not-accessible,,current,,The VPI value of the VCL. This object combined with the atmAddrVclAtmIfIndex and atmAddrVclVci objects serves as an index to the atmVclTable.
.1.3.6.1.2.1.37.1.14.1.8.1.3,ATM2-MIB::atmAddrVclVci,INTEGER,not-accessible,,current,,The VCI value of the VCL. This object combined with the atmAddrVclAtmIfIndex and atmAddrVclVpi objects serves as an index to the atmVclTable.
.1.3.6.1.2.1.37.1.14.1.8.1.4,ATM2-MIB::atmAddrVclAddrType,INTEGER,read-only,,current,callingParty(1):calledParty(2),The type of ATM Address represented by the object atmVclAddrAddr. Choices are either calling party address or called party address.
.1.3.6.1.2.1.37.1.14.1.9,ATM2-MIB::atmVplStatTable,,not-accessible,,current,,This table contains all statistics counters per VPL. It is used to monitor the usage of the VPL in terms of incoming cells and outgoing cells.
.1.3.6.1.2.1.37.1.14.1.9.1,ATM2-MIB::atmVplStatEntry,,not-accessible,ifIndex:atmVplVpi,current,,Each entry in this table represents a VPL.
.1.3.6.1.2.1.37.1.14.1.9.1.1,ATM2-MIB::atmVplStatTotalCellIns,Counter32,read-only,,current,,The total number of valid ATM cells received by this VPL including both CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic policing.
.1.3.6.1.2.1.37.1.14.1.9.1.2,ATM2-MIB::atmVplStatClp0CellIns,Counter32,read-only,,current,,The number of valid ATM cells received by this VPL with CLP=0. The cells are counted prior to the application of the traffic policing.
.1.3.6.1.2.1.37.1.14.1.9.1.3,ATM2-MIB::atmVplStatTotalDiscards,Counter32,read-only,,current,,The total number of valid ATM cells discarded by the traffic policing entity. This includes cells originally received with CLP=0 and CLP=1.
.1.3.6.1.2.1.37.1.14.1.9.1.4,ATM2-MIB::atmVplStatClp0Discards,Counter32,read-only,,current,,The total number of valid ATM cells received with CLP=0 and discarded by the traffic policing entity.
.1.3.6.1.2.1.37.1.14.1.9.1.5,ATM2-MIB::atmVplStatTotalCellOuts,Counter32,read-only,,current,,The total number of valid ATM cells transmitted by this VPL. This includes both CLP=0 and CLP=1 cells.
.1.3.6.1.2.1.37.1.14.1.9.1.6,ATM2-MIB::atmVplStatClp0CellOuts,Counter32,read-only,,current,,The total number of valid ATM cells transmitted with CLP=0 by this VPL.
.1.3.6.1.2.1.37.1.14.1.9.1.7,ATM2-MIB::atmVplStatClp0Tagged,Counter32,read-only,,current,,The total number of valid ATM cells tagged by the traffic policing entity from CLP=0 to CLP=1.
.1.3.6.1.2.1.37.1.14.1.10,ATM2-MIB::atmVplLogicalPortTable,,not-accessible,,current,,Indicates whether the VPL is an ATM Logical Port interface (ifType=80).
.1.3.6.1.2.1.37.1.14.1.10.1,ATM2-MIB::atmVplLogicalPortEntry,,not-accessible,,current,,An entry with information about the ATM Logical Port interface.
.1.3.6.1.2.1.37.1.14.1.10.1.1,ATM2-MIB::atmVplLogicalPortDef,INTEGER,read-create,,current,notLogicalIf(1):isLogicalIf(2),Indicates whether the VPC at this VPL interface is an ATM Logical Port interface.
.1.3.6.1.2.1.37.1.14.1.10.1.2,ATM2-MIB::atmVplLogicalPortIndex,Integer32,read-only,,current,,The ifTable index of the ATM logical port interface associated with this VPL. The distinguished value of zero indicates that the agent has not (yet) assigned such an ifTable Index. The zero value must be assigned by the agent if the value of atmVplLogicalPortDef is set to notLogicalIf, or if the VPL row is not active.
.1.3.6.1.2.1.37.1.14.1.11,ATM2-MIB::atmVclStatTable,,not-accessible,,current,,This table contains all statistics counters per VCL. It is used to monitor the usage of the VCL in terms of incoming cells and outgoing cells.
.1.3.6.1.2.1.37.1.14.1.11.1,ATM2-MIB::atmVclStatEntry,,not-accessible,ifIndex:atmVclVpi:atmVclVci,current,,Each entry in this table represents a VCL.
.1.3.6.1.2.1.37.1.14.1.11.1.1,ATM2-MIB::atmVclStatTotalCellIns,Counter32,read-only,,current,,The total number of valid ATM cells received by this VCL including both CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic policing.
.1.3.6.1.2.1.37.1.14.1.11.1.2,ATM2-MIB::atmVclStatClp0CellIns,Counter32,read-only,,current,,The number of valid ATM cells received by this VCL with CLP=0. The cells are counted prior to the application of the traffic policing.
.1.3.6.1.2.1.37.1.14.1.11.1.3,ATM2-MIB::atmVclStatTotalDiscards,Counter32,read-only,,current,,The total number of valid ATM cells discarded by the traffic policing entity. This includes cells originally received with CLP=0 and CLP=1.
.1.3.6.1.2.1.37.1.14.1.11.1.4,ATM2-MIB::atmVclStatClp0Discards,Counter32,read-only,,current,,The total number of valid ATM cells received with CLP=0 and discarded by the traffic policing entity.
.1.3.6.1.2.1.37.1.14.1.11.1.5,ATM2-MIB::atmVclStatTotalCellOuts,Counter32,read-only,,current,,The total number of valid ATM cells transmitted by this VCL. This includes both CLP=0 and CLP=1 cells.
.1.3.6.1.2.1.37.1.14.1.11.1.6,ATM2-MIB::atmVclStatClp0CellOuts,Counter32,read-only,,current,,The total number of valid ATM cells transmitted with CLP=0 by this VCL.
.1.3.6.1.2.1.37.1.14.1.11.1.7,ATM2-MIB::atmVclStatClp0Tagged,Counter32,read-only,,current,,The total number of valid ATM cells tagged by the traffic policing entity from CLP=0 to CLP=1.
.1.3.6.1.2.1.37.1.14.1.12,ATM2-MIB::atmAal5VclStatTable,,not-accessible,,current,,This table provides a collection of objects providing AAL5 configuration and performance statistics of a VCL.
.1.3.6.1.2.1.37.1.14.1.12.1,ATM2-MIB::atmAal5VclStatEntry,,not-accessible,ifIndex:atmVclVpi:atmVclVci,current,,Each entry in this table represents an AAL5 VCL, and is indexed by ifIndex values of AAL5 interfaces and the associated VPI/VCI values.
.1.3.6.1.2.1.37.1.14.1.12.1.1,ATM2-MIB::atmAal5VclInPkts,Counter32,read-only,,current,,The number of AAL5 CPCS PDUs received on the AAL5 VCC at the interface identified by the ifIndex.
.1.3.6.1.2.1.37.1.14.1.12.1.2,ATM2-MIB::atmAal5VclOutPkts,Counter32,read-only,,current,,The number of AAL5 CPCS PDUs transmitted on the AAL5 VCC at the interface identified by the ifIndex.
.1.3.6.1.2.1.37.1.14.1.12.1.3,ATM2-MIB::atmAal5VclInOctets,Counter32,read-only,,current,,The number of octets contained in AAL5 CPCS PDUs received on the AAL5 VCC at the interface identified by the ifIndex.
.1.3.6.1.2.1.37.1.14.1.12.1.4,ATM2-MIB::atmAal5VclOutOctets,Counter32,read-only,,current,,The number of octets contained in AAL5 CPCS PDUs transmitted on the AAL5 VCC at the interface identified by the ifIndex.
.1.3.6.1.2.1.37.1.14.1.13,ATM2-MIB::atmVclGenTable,,not-accessible,,current,,General Information for each VC.
.1.3.6.1.2.1.37.1.14.1.13.1,ATM2-MIB::atmVclGenEntry,,not-accessible,,current,,An entry with general information about the ATM VC.
.1.3.6.1.2.1.37.1.14.1.13.1.1,ATM2-MIB::atmVclGenSigDescrIndex,INTEGER,read-create,,current,,The value of this object identifies the row in the ATM Signalling Descriptor Parameter Table which applies to this VCL.
.1.3.6.1.2.1.37.1.14.1.14,ATM2-MIB::atmInterfaceExtTable,,not-accessible,,current,,This table contains ATM interface configuration and monitoring information not defined in the atmInterfaceConfTable from the ATM-MIB. This includes the type of connection setup procedures, ILMI information, and information on the VPI/VCI range.
.1.3.6.1.2.1.37.1.14.1.14.1,ATM2-MIB::atmInterfaceExtEntry,,not-accessible,,current,,An entry extends the atmInterfaceConfEntry defined in the ATM- MIB. Each entry corresponds to an ATM interface.
.1.3.6.1.2.1.37.1.14.1.14.1.1,ATM2-MIB::atmIntfConfigType,INTEGER,read-write,,current,other(1):autoConfig(2):ituDss2(3):atmfUni3Dot0(4):atmfUni3Dot1(5):atmfUni4Dot0(6):atmfIispUni3Dot0(7):atmfIispUni3Dot1(8):atmfIispUni4Dot0(9):atmfPnni1Dot0(10):atmfBici2Dot0(11):atmfUniPvcOnly(12):atmfNniPvcOnly(13),The type of connection setup procedures configured for the ATM interface. Setting this variable to a value of 'other' is not allowed.
.1.3.6.1.2.1.37.1.14.1.14.1.2,ATM2-MIB::atmIntfActualType,INTEGER,read-only,,current,other(1):autoConfig(2):ituDss2(3):atmfUni3Dot0(4):atmfUni3Dot1(5):atmfUni4Dot0(6):atmfIispUni3Dot0(7):atmfIispUni3Dot1(8):atmfIispUni4Dot0(9):atmfPnni1Dot0(10):atmfBici2Dot0(11):atmfUniPvcOnly(12):atmfNniPvcOnly(13),The type of connection setup procedures currently being used on the interface. This may reflect a manually configured value for the interface type, or may be determined by other means such as auto-configuration. A value of `autoConfig' indicates that auto-configuration was requested but has not yet been completed.
.1.3.6.1.2.1.37.1.14.1.14.1.3,ATM2-MIB::atmIntfConfigSide,INTEGER,read-write,,current,other(1):user(2):network(3),The configured role of the managed entity as one side of the ATM interface. This value does not apply when the object atmIntfConfigType is set to `autoConfig', `atmfPnni1Dot0', or `atmfBici2Dot0'.
.1.3.6.1.2.1.37.1.14.1.14.1.4,ATM2-MIB::atmIntfActualSide,INTEGER,read-only,,current,other(1):user(2):network(3):symmetric(4),The current role used by the managed entity to represent one side of the ATM interface.
.1.3.6.1.2.1.37.1.14.1.14.1.5,ATM2-MIB::atmIntfIlmiAdminStatus,BITS,read-write,,current,ilmi(0):ilmiAddressRegistration(1):ilmiConnectivity(2):ilmiPvcPvpMgmt(3):ilmiSigVccParamNegotiation(4),Indicates which components of ILMI are administratively enabled on this interface. If the 'ilmi' bit is not set, then no ILMI components are operational. ILMI components other than auto- configuration that are not represented in the value have their administrative status determined according to the 'ilmi' bit. The ILMI auto-configuration component is enabled/disabled by the atmIntfConfigType object.
.1.3.6.1.2.1.37.1.14.1.14.1.6,ATM2-MIB::atmIntfIlmiOperStatus,BITS,read-only,,current,ilmi(0):ilmiAddressRegistration(1):ilmiConnectivity(2):ilmiPvcPvpMgmt(3):ilmiSigVccParamNegotiation(4),Indicates which components of ILMI are operational on this interface.
.1.3.6.1.2.1.37.1.14.1.14.1.7,ATM2-MIB::atmIntfIlmiFsmState,INTEGER,read-only,,current,stopped(1):linkFailing(2):establishing(3):configuring(4):retrievingNetworkPrefixes(5):registeringNetworkPrefixes(6):retrievingAddresses(7):registeringAddresses(8):verifying(9),Indicates the state of the ILMI Finite State Machine associated with this interface.
.1.3.6.1.2.1.37.1.14.1.14.1.8,ATM2-MIB::atmIntfIlmiEstablishConPollIntvl,Integer32,read-write,,current,,The amount of time S between successive transmissions of ILMI messages on this interface for the purpose of detecting establishment of ILMI connectivity.
.1.3.6.1.2.1.37.1.14.1.14.1.9,ATM2-MIB::atmIntfIlmiCheckConPollIntvl,Integer32,read-write,,current,,The amount of time T between successive transmissions of ILMI messages on this interface for the purpose of detecting loss of ILMI connectivity. The distinguished value zero disables ILMI connectivity procedures on this interface.
.1.3.6.1.2.1.37.1.14.1.14.1.10,ATM2-MIB::atmIntfIlmiConPollInactFactor,Integer32,read-write,,current,,The number K of consecutive polls on this interface for which no ILMI response message is received before ILMI connectivity is declared lost.
.1.3.6.1.2.1.37.1.14.1.14.1.11,ATM2-MIB::atmIntfIlmiPublicPrivateIndctr,INTEGER,read-write,,current,other(1):public(2):private(3),Specifies whether this end of the interface is advertised in ILMI as a device of the `public' or `private' type.
.1.3.6.1.2.1.37.1.14.1.14.1.12,ATM2-MIB::atmInterfaceConfMaxSvpcVpi,INTEGER,read-write,,current,,The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual path connections.
.1.3.6.1.2.1.37.1.14.1.14.1.13,ATM2-MIB::atmInterfaceCurrentMaxSvpcVpi,INTEGER,read-only,,current,,The maximum VPI that the signalling stack on the ATM interface may currently allocate to switched virtual path connections. This value is the minimum of atmInterfaceConfMaxSvpcVpi, and the atmInterfaceMaxSvpcVpi of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the maximum VPI that can be allocated to SVPCs on the interface, then the value of this object must equal atmInterfaceConfMaxSvpcVpi. 
.1.3.6.1.2.1.37.1.14.1.14.1.14,ATM2-MIB::atmInterfaceConfMaxSvccVpi,INTEGER,read-write,,current,,The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections.
.1.3.6.1.2.1.37.1.14.1.14.1.15,ATM2-MIB::atmInterfaceCurrentMaxSvccVpi,INTEGER,read-only,,current,,The maximum VPI that the signalling stack on the ATM interface may currently allocate to switched virtual channel connections. This value is the minimum of atmInterfaceConfMaxSvccVpi, and the atmInterfaceConfMaxSvccVpi of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the maximum VPI that can be allocated to SVCCs on the interface, then the value of this object must equal atmInterfaceConfMaxSvccVpi.
.1.3.6.1.2.1.37.1.14.1.14.1.16,ATM2-MIB::atmInterfaceConfMinSvccVci,INTEGER,read-write,,current,,The minimum VCI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections.
.1.3.6.1.2.1.37.1.14.1.14.1.17,ATM2-MIB::atmInterfaceCurrentMinSvccVci,INTEGER,read-only,,current,,The minimum VCI that the signalling stack on the ATM interface may currently allocate to switched virtual channel connections. This value is the maximum of atmInterfaceConfMinSvccVci, and the atmInterfaceConfMinSvccVci of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the minimum VCI that can be allocated to SVCCs on the interface, then the value of this object must equal atmInterfaceConfMinSvccVci.
.1.3.6.1.2.1.37.1.14.1.14.1.18,ATM2-MIB::atmIntfSigVccRxTrafficDescrIndex,INTEGER,read-write,,current,,This object identifies the row in the atmTrafficDescrParamTable used during ILMI auto-configuration to specify the advertised signalling VCC traffic parameters for the receive direction. The traffic descriptor resulting from ILMI auto-configuration of the signalling VCC is indicated in the atmVclTable.
.1.3.6.1.2.1.37.1.14.1.14.1.19,ATM2-MIB::atmIntfSigVccTxTrafficDescrIndex,INTEGER,read-write,,current,,This object identifies the row in the atmTrafficDescrParamTable used during ILMI auto-configuration to specify the advertised signalling VCC traffic parameters for the transmit direction. The traffic descriptor resulting from ILMI auto-configuration of the signalling VCC is indicated in the atmVclTable.
.1.3.6.1.2.1.37.1.14.1.14.1.20,ATM2-MIB::atmIntfPvcFailures,Counter32,read-only,,current,,The number of times the operational status of a PVPL or PVCL on this interface has gone down.
.1.3.6.1.2.1.37.1.14.1.14.1.21,ATM2-MIB::atmIntfCurrentlyFailingPVpls,Gauge32,read-only,,current,,The current number of VPLs on this interface for which there is an active row in the atmVplTable having an atmVplConnKind value of `pvc' and an atmVplOperStatus with a value other than `up'.
.1.3.6.1.2.1.37.1.14.1.14.1.22,ATM2-MIB::atmIntfCurrentlyFailingPVcls,Gauge32,read-only,,current,,The current number of VCLs on this interface for which there is an active row in the atmVclTable having an atmVclConnKind value of `pvc' and an atmVclOperStatus with a value other than `up'.
.1.3.6.1.2.1.37.1.14.1.14.1.23,ATM2-MIB::atmIntfPvcFailuresTrapEnable,INTEGER,read-write,,current,true(1):false(2),Allows the generation of traps in response to PVCL or PVPL failures on this interface.
.1.3.6.1.2.1.37.1.14.1.14.1.24,ATM2-MIB::atmIntfPvcNotificationInterval,INTEGER,read-write,,current,,The minimum interval between the sending of atmIntfPvcFailuresTrap notifications for this interface.
.1.3.6.1.2.1.37.1.14.1.14.1.25,ATM2-MIB::atmIntfLeafSetupFailures,Counter32,read-only,,current,,Number of setup failures. For root, this is the number of rejected setup requests and for leaf, this is the number of setup failure received.
.1.3.6.1.2.1.37.1.14.1.14.1.26,ATM2-MIB::atmIntfLeafSetupRequests,Counter32,read-only,,current,,Number of setup requests. For root, this includes both incoming setup request and root intiated setup requests.
.1.3.6.1.2.1.37.1.14.1.15,ATM2-MIB::atmIlmiSrvcRegTable,,not-accessible,,current,,This table contains a list of all the ATM network services known by this device. The characteristics of these services are made available through the ILMI, using the ILMI general-purpose service registry MIB. These services may be made available to all ATM interfaces (atmIlmiSrvcRegIndex = 0) or to some specific ATM interfaces only (atmIlmiSrvcRegIndex = ATM interface index).
.1.3.6.1.2.1.37.1.14.1.15.1,ATM2-MIB::atmIlmiSrvcRegEntry,,not-accessible,atmIlmiSrvcRegIndex:atmIlmiSrvcRegServiceID:atmIlmiSrvcRegAddressIndex,current,,Information about a single service provider that is available to the user-side of an adjacent device through the ILMI. Implementors need to be aware that if the size of the atmIlmiSrvcRegServiceID exceeds 112 sub-identifiers then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2, or SNMPv3.
.1.3.6.1.2.1.37.1.14.1.15.1.1,ATM2-MIB::atmIlmiSrvcRegIndex,Integer32,not-accessible,,current,,The ATM interface where the service defined in this entry can be made available to an ATM device attached to this interface. The value of 0 has a special meaning: when an ATM service is defined in an entry whose atmIlmiSrvcRegIndex is zero, the ATM service is available to ATM devices connected to any ATM interface. (default value(s)). When the user-side of an adjacent device queries the content of the ILMI service registry MIB (using the ILMI protocol), the local network-side responds with the ATM services defined in atmIlmiSrvcRegTable entries, provided that these entries are indexed by: - the corresponding ifIndex value (atmIlmiSrvcRegIndex equal to the ifIndex of the interface to which the adjacent device is connected) - zero (atmIlmiSrvcRegIndex=0).
.1.3.6.1.2.1.37.1.14.1.15.1.2,ATM2-MIB::atmIlmiSrvcRegServiceID,OBJECT,not-accessible,,current,,This is the service identifier which uniquely identifies the type of service at the address provided in the table. The object identifiers for the LAN Emulation Configuration Server (LECS) and the ATM Name Server (ANS) are defined in the ATM Forum ILMI Service Registry MIB. The object identifiers for the ATMARP Server, the Multicast Address Resolution Server (MARS), and the NHRP Server (NHS) are defined in RFC 2601, RFC 2602, and RFC 2603, respectively.
.1.3.6.1.2.1.37.1.14.1.15.1.3,ATM2-MIB::atmIlmiSrvcRegAddressIndex,INTEGER,not-accessible,,current,,An arbitrary integer to differentiate multiple rows containing different ATM addresses for the same service on the same interface. This number need NOT be the same as the corresponding ILMI atmfSrvcRegAddressIndex MIB object.
.1.3.6.1.2.1.37.1.14.1.15.1.4,ATM2-MIB::atmIlmiSrvcRegATMAddress,OCTET,read-create,,current,,This is the full address of the service. The user-side of the adjacent device may use this address to establish a connection with the service.
.1.3.6.1.2.1.37.1.14.1.15.1.5,ATM2-MIB::atmIlmiSrvcRegParm1,OCTET,read-create,,current,,An octet string used according to the value of atmIlmiSrvcRegServiceID.
.1.3.6.1.2.1.37.1.14.1.15.1.6,ATM2-MIB::atmIlmiSrvcRegRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create or destroy an entry from this table.
.1.3.6.1.2.1.37.1.14.1.16,ATM2-MIB::atmIlmiNetworkPrefixTable,,not-accessible,,current,,A table specifying per-interface network prefix(es) supplied by the network side of the UNI during ILMI address registration. When no network prefixes are specified for a particular interface, one or more network prefixes based on the switch address(es) may be used for ILMI address registration.
.1.3.6.1.2.1.37.1.14.1.16.1,ATM2-MIB::atmIlmiNetworkPrefixEntry,,not-accessible,ifIndex:atmIlmiNetPrefixPrefix,current,,Information about a single network prefix supplied by the network side of the UNI during ILMI address registration. Note that the index variable atmIlmiNetPrefixPrefix is a variable- length string, and as such the rule for variable-length strings in section 7.7 of RFC 2578 applies.
.1.3.6.1.2.1.37.1.14.1.16.1.1,ATM2-MIB::atmIlmiNetPrefixPrefix,OCTET,not-accessible,,current,,The network prefix specified for use in ILMI address registration.
.1.3.6.1.2.1.37.1.14.1.16.1.2,ATM2-MIB::atmIlmiNetPrefixRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create, delete, activate and de-activate network prefixes used in ILMI address registration.
.1.3.6.1.2.1.37.1.14.1.17,ATM2-MIB::atmSwitchAddressTable,,not-accessible,,current,,This table contains one or more ATM endsystem addresses on a per-switch basis. These addresses are used to identify the switch. When no ILMI network prefixes are configured for certain interfaces, network prefixes based on the switch address(es) may be used for ILMI address registration.
.1.3.6.1.2.1.37.1.14.1.17.1,ATM2-MIB::atmSwitchAddressEntry,,not-accessible,atmSwitchAddressIndex,current,,An entry in the ATM Switch Address table.
.1.3.6.1.2.1.37.1.14.1.17.1.1,ATM2-MIB::atmSwitchAddressIndex,Integer32,not-accessible,,current,,An arbitrary index used to enumerate the ATM endsystem addresses for this switch.
.1.3.6.1.2.1.37.1.14.1.17.1.2,ATM2-MIB::atmSwitchAddressAddress,OCTET,read-create,,current,,An ATM endsystem address or address prefix used to identify this switch. When no ESI or SEL field is specified, the switch may generate the ESI and SEL fields automatically to obtain a complete 20-byte ATM endsystem address.
.1.3.6.1.2.1.37.1.14.1.17.1.3,ATM2-MIB::atmSwitchAddressRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create, delete, activate, and de-activate addresses used to identify this switch.
.1.3.6.1.2.1.37.1.14.1.18,ATM2-MIB::atmVpCrossConnectXTable,,not-accessible,,current,,This table contains one row per VP Cross-Connect represented in the atmVpCrossConnectTable.
.1.3.6.1.2.1.37.1.14.1.18.1,ATM2-MIB::atmVpCrossConnectXEntry,,not-accessible,,current,,Information about a particular ATM VP Cross-Connect. Each entry provides an two objects that name the Cross-Connect. One is assigned by the Service User and the other by the Service Provider.
.1.3.6.1.2.1.37.1.14.1.18.1.1,ATM2-MIB::atmVpCrossConnectUserName,OCTET,read-create,,current,,This is a service user assigned textual representation of a VPC PVC.
.1.3.6.1.2.1.37.1.14.1.18.1.2,ATM2-MIB::atmVpCrossConnectProviderName,OCTET,read-only,,current,,This is a system supplied textual representation of VPC PVC. It is assigned by the service provider.
.1.3.6.1.2.1.37.1.14.1.19,ATM2-MIB::atmVcCrossConnectXTable,,not-accessible,,current,,This table contains one row per VC Cross-Connect represented in the atmVcCrossConnectTable.
.1.3.6.1.2.1.37.1.14.1.19.1,ATM2-MIB::atmVcCrossConnectXEntry,,not-accessible,,current,,Information about a particular ATM VC Cross-Connect. Each entry provides an two objects that name the Cross-Connect. One is assigned by the Service User and the other by the Service Provider.
.1.3.6.1.2.1.37.1.14.1.19.1.1,ATM2-MIB::atmVcCrossConnectUserName,OCTET,read-create,,current,,This is a service user assigned textual representation of a VCC PVC.
.1.3.6.1.2.1.37.1.14.1.19.1.2,ATM2-MIB::atmVcCrossConnectProviderName,OCTET,read-only,,current,,This is a system supplied textual representation of VCC PVC. It is assigned by the service provider.
.1.3.6.1.2.1.37.1.14.1.20,ATM2-MIB::atmCurrentlyFailingPVplTable,,not-accessible,,current,,A table indicating all VPLs for which there is an active row in the atmVplTable having an atmVplConnKind value of `pvc' and an atmVplOperStatus with a value other than `up'.
.1.3.6.1.2.1.37.1.14.1.20.1,ATM2-MIB::atmCurrentlyFailingPVplEntry,,not-accessible,ifIndex:atmVplVpi,current,,Each entry in this table represents a VPL for which the atmVplRowStatus is `active', the atmVplConnKind is `pvc', and the atmVplOperStatus is other than `up'.
.1.3.6.1.2.1.37.1.14.1.20.1.1,ATM2-MIB::atmCurrentlyFailingPVplTimeStamp,TimeTicks,read-only,,current,,The time at which this PVPL began to fail.
.1.3.6.1.2.1.37.1.14.1.21,ATM2-MIB::atmCurrentlyFailingPVclTable,,not-accessible,,current,,A table indicating all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of `pvc' and an atmVclOperStatus with a value other than `up'.
.1.3.6.1.2.1.37.1.14.1.21.1,ATM2-MIB::atmCurrentlyFailingPVclEntry,,not-accessible,ifIndex:atmVclVpi:atmVclVci,current,,Each entry in this table represents a VCL for which the atmVclRowStatus is `active', the atmVclConnKind is `pvc', and the atmVclOperStatus is other than `up'.
.1.3.6.1.2.1.37.1.14.1.21.1.1,ATM2-MIB::atmCurrentlyFailingPVclTimeStamp,TimeTicks,read-only,,current,,The time at which this PVCL began to fail.
.1.3.6.1.2.1.37.1.14.2,ATM2-MIB::atm2MIBTraps,,,,,,
.1.3.6.1.2.1.37.1.14.2.1,ATM2-MIB::atmPvcTraps,,,,,,
.1.3.6.1.2.1.37.1.14.2.1.0,ATM2-MIB::atmPvcTrapsPrefix,,,,,,
.1.3.6.1.2.1.37.1.14.2.1.0.1,ATM2-MIB::atmIntfPvcFailuresTrap,,,,,,A notification indicating that one or more PVPLs or PVCLs on this interface has failed since the last atmPvcFailuresTrap was sent. If this trap has not been sent for the last atmIntfPvcNotificationInterval, then it will be sent on the next increment of atmIntfPvcFailures.
.1.3.6.1.2.1.37.1.14.3,ATM2-MIB::atm2MIBConformance,,,,,,
.1.3.6.1.2.1.37.1.14.3.1,ATM2-MIB::atm2MIBGroups,,,,,,
.1.3.6.1.2.1.37.1.14.3.1.1,ATM2-MIB::atmCommonGroup,,,,,,A collection of objects providing information for a Switch/Service/Host that implements ATM interfaces.
.1.3.6.1.2.1.37.1.14.3.1.2,ATM2-MIB::atmCommonStatsGroup,,,,,,A collection of objects providing information for a Switch/Service/Host that implements ATM VCL and VPL Statistics
.1.3.6.1.2.1.37.1.14.3.1.3,ATM2-MIB::atmSwitchServcGroup,,,,,,A collection of objects providing information for a Switch/Service that implements ATM interfaces.
.1.3.6.1.2.1.37.1.14.3.1.4,ATM2-MIB::atmSwitchServcSigGroup,,,,,,A collection of objects providing information for a Switch/Service that implements ATM signalling.
.1.3.6.1.2.1.37.1.14.3.1.5,ATM2-MIB::atmSwitchServcNotifGroup,,,,,,A collection of notifications providing information for a Switch/Service that implements ATM interfaces.
.1.3.6.1.2.1.37.1.14.3.1.6,ATM2-MIB::atmSwitchGroup,,,,,,A collection of objects providing information for an ATM switch.
.1.3.6.1.2.1.37.1.14.3.1.7,ATM2-MIB::atmServcGroup,,,,,,A collection of objects providing information for an ATM Network Service.
.1.3.6.1.2.1.37.1.14.3.1.8,ATM2-MIB::atmHostGroup,,,,,,A collection of objects providing information for a Host that implements ATM interfaces.
.1.3.6.1.2.1.37.1.14.3.1.9,ATM2-MIB::atmHostSigDescrGroup,,,,,,A collection of objects providing information for a Host that implements ATM interfaces.
.1.3.6.1.2.1.37.1.14.3.2,ATM2-MIB::atm2MIBCompliances,,,,,,
.1.3.6.1.2.1.37.1.14.3.2.1,ATM2-MIB::atm2MIBCompliance,,,,,,The compliance statement for SNMP entities which represent ATM interfaces. The compliance statements are used to determine if a particular group or object applies to hosts, networks/switches, or both. The Common group is defined as applicable to all three.
.1.3.6.1.2.1.37.2,ATM-MIB::atmMIBConformance,,,,,,
.1.3.6.1.2.1.37.2.1,ATM-MIB::atmMIBGroups,,,,,,
.1.3.6.1.2.1.37.2.1.1,ATM-MIB::atmInterfaceConfGroup,,,,,,A collection of objects providing configuration information about an ATM interface.
.1.3.6.1.2.1.37.2.1.2,ATM-MIB::atmTrafficDescrGroup,,,,,,A collection of objects providing information about ATM traffic descriptor type and the associated parameters.
.1.3.6.1.2.1.37.2.1.3,ATM-MIB::atmInterfaceDs3PlcpGroup,,,,,,A collection of objects providing information about DS3 PLCP layer at an ATM interface.
.1.3.6.1.2.1.37.2.1.4,ATM-MIB::atmInterfaceTCGroup,,,,,,A collection of objects providing information about TC sublayer at an ATM interface.
.1.3.6.1.2.1.37.2.1.5,ATM-MIB::atmVpcTerminationGroup,,,,,,A collection of objects providing information about a VPL at an ATM interface which terminates a VPC (i.e., one which is NOT cross-connected to other VPLs).
.1.3.6.1.2.1.37.2.1.6,ATM-MIB::atmVccTerminationGroup,,,,,,A collection of objects providing information about a VCL at an ATM interface which terminates a VCC (i.e., one which is NOT cross-connected to other VCLs).
.1.3.6.1.2.1.37.2.1.7,ATM-MIB::atmVpCrossConnectGroup,,,,,,A collection of objects providing information about a VP cross-connect and the associated VPLs that are cross-connected together.
.1.3.6.1.2.1.37.2.1.8,ATM-MIB::atmVcCrossConnectGroup,,,,,,A collection of objects providing information about a VC cross-connect and the associated VCLs that are cross-connected together.
.1.3.6.1.2.1.37.2.1.9,ATM-MIB::aal5VccGroup,,,,,,A collection of objects providing AAL5 configuration and performance statistics of a VCC.
.1.3.6.1.2.1.37.2.1.10,ATM-MIB::atmInterfaceConfGroup2,,,,,,A collection of objects providing configuration information about an ATM interface.
.1.3.6.1.2.1.37.2.1.11,ATM-MIB::atmTrafficDescrGroup2,,,,,,A collection of objects providing information about ATM traffic descriptor type and the associated parameters.
.1.3.6.1.2.1.37.2.1.12,ATM-MIB::atmVpcTerminationGroup2,,,,,,A collection of objects providing information about a VPL at an ATM interface which terminates a VPC (i.e., one which is NOT cross-connected to other VPLs).
.1.3.6.1.2.1.37.2.1.13,ATM-MIB::atmVccTerminationGroup2,,,,,,A collection of objects providing information about a VCL at an ATM interface which terminates a VCC (i.e., one which is NOT cross-connected to other VCLs).
.1.3.6.1.2.1.37.2.1.14,ATM-MIB::atmVplCrossConnectGroup,,,,,,A collection of objects providing information about the VPLs that are cross-connected together.
.1.3.6.1.2.1.37.2.1.15,ATM-MIB::atmVpPvcCrossConnectGroup,,,,,,A collection of objects providing information about a VP cross-connect for PVCs. These objects are not used for Soft PVCs or SVCs.
.1.3.6.1.2.1.37.2.1.16,ATM-MIB::atmVclCrossConnectGroup,,,,,,A collection of objects providing information about the VCLs that are cross-connected together.
.1.3.6.1.2.1.37.2.1.17,ATM-MIB::atmVcPvcCrossConnectGroup,,,,,,A collection of objects providing information about a VC cross-connect for PVCs. These objects are not used for Soft PVCs or SVCs.
.1.3.6.1.2.1.37.2.2,ATM-MIB::atmMIBCompliances,,,,,,
.1.3.6.1.2.1.37.2.2.1,ATM-MIB::atmMIBCompliance,,,,,,The compliance statement for SNMP entities including networks which have ATM and AAL5 interfaces.
.1.3.6.1.2.1.37.2.2.2,ATM-MIB::atmMIBCompliance2,,,,,,The compliance statement for SNMP entities including networks which have ATM and AAL5 interfaces.
.1.3.6.1.2.1.37.3,ATM-TC-MIB::atmTCMIB,,,,,,This MIB Module provides Textual Conventions and OBJECT-IDENTITY Objects to be used by ATM systems.
.1.3.6.1.2.1.37.3.1,ATM-TC-MIB::atmObjectIdentities,,,,,,
.1.3.6.1.2.1.38,Modem-MIB::mdmMib,,,,,,
.1.3.6.1.2.1.38.1,Modem-MIB::mdmMIB,,,,,,The MIB module for management of dial-up modems.
.1.3.6.1.2.1.38.1.1,Modem-MIB::mdmMIBObjects,,,,,,
.1.3.6.1.2.1.38.1.1.1,Modem-MIB::mdmNumber,Integer32,read-only,,current,,The number of modem rows in the modem table. This value defines the maximum value of the mdmIndex object.
.1.3.6.1.2.1.38.1.1.2,Modem-MIB::mdmIDTable,,not-accessible,,current,,The base table for the modems managed by this MIB. The mdmLineTable, mdmDTEInterfaceTable, mdmCallControlTable, and mdmStatsTable all augment the rows defined in this table.
.1.3.6.1.2.1.38.1.1.2.1,Modem-MIB::mdmIDEntry,,not-accessible,mdmIndex,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.2.1.1,Modem-MIB::mdmIndex,Integer32,not-accessible,,current,,A unique number for each modem that ranges from 1 to mdmNumber. The value must remain constant at least from one re-initialization of the network management agent to the next.
.1.3.6.1.2.1.38.1.1.2.1.2,Modem-MIB::mdmIDManufacturerOID,OBJECT,read-only,,current,,This value is intended to identify the manufacturer, model, and version of this modem. This may be used to identify the existance of enterprise-specific functions and behaviours.
.1.3.6.1.2.1.38.1.1.2.1.3,Modem-MIB::mdmIDProductDetails,OCTET,read-only,,current,,A textual description of this device, including the manufacturer's name, modem model name, hardware revision, firmware revision, and optionally, its serial number. The exact format of this description is defined by the vendor. This description may only contain characters from the NVT ASCII character set.
.1.3.6.1.2.1.38.1.1.3,Modem-MIB::mdmLineTable,,not-accessible,,current,,The modem Line Table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.3.1,Modem-MIB::mdmLineEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.3.1.1,Modem-MIB::mdmLineCarrierLossTime,Integer32,read-write,,current,,Duration in 10ths of a second the modem waits after loss of carrier before hanging up. If this value is set to `255', the modem will not hang up upon loss of carrier. This allows the modem to distinguish between a momentary lapse in line quality and a true disconnect and can be useful to tune the tolerance of the modem to lines of poor quality.
.1.3.6.1.2.1.38.1.1.3.1.2,Modem-MIB::mdmLineState,INTEGER,read-write,,current,unknown(1):onHook(2):offHook(3):connected(4):busiedOut(5):reset(6),Allows the inspection and alteration of the state of the modem. Management commands may change the state to `on- hook', `busied-out', or `reset' from any state. No other alterations are permitted from the management protocol. When this object is set to reset, the modem shall be reset and the value will change to the modem's new, implementation dependent state.
.1.3.6.1.2.1.38.1.1.4,Modem-MIB::mdmLineCapabilitiesTable,,not-accessible,,current,,A list of protocol capabilities for this modem.
.1.3.6.1.2.1.38.1.1.4.1,Modem-MIB::mdmLineCapabilitiesEntry,,not-accessible,mdmIndex:mdmLineCapabilitiesIndex,current,,A listing of the protocol(s) that this modem is capable of. Entries in this table are created only by the agent. One entry exists for each protocol that the modem is capable of, regardless of whether that protocol is enabled or not. This table is useful for providing an inventory of the capabilities on a modem, and allowing the manager to enable or disable capabilities from the menu of available possibilities. Row creation is not required to enable or disable capabilities.
.1.3.6.1.2.1.38.1.1.4.1.1,Modem-MIB::mdmLineCapabilitiesIndex,Integer32,not-accessible,,current,,A unique index for this capabilities entry.
.1.3.6.1.2.1.38.1.1.4.1.2,Modem-MIB::mdmLineCapabilitiesID,OBJECT,read-only,,current,,An identifier for this capability. Standard protocol capabilities will have identifiers registered in this document or other companion standards documents. Proprietary protocol capabilities will be registered by their respective organization. All capabilities, standard or vendor-specific, shall be registered in this table.
.1.3.6.1.2.1.38.1.1.4.1.3,Modem-MIB::mdmLineCapabilitiesEnableRequested,INTEGER,read-write,,current,disabled(1):preferred(3),The requested configuration of this capability. If this value is 'disabled(1)', this is a request to disable this protocol. If this value is 'preferred(3)', this is a request to enable this protocol, and to prefer it in any negotiation over other appropriate protocols that have a value of 'optional(2)'.
.1.3.6.1.2.1.38.1.1.4.1.4,Modem-MIB::mdmLineCapabilitiesEnableGranted,INTEGER,read-only,,current,disabled(1):preferred(3),The actual configuration of this capability. The agent shall attempt to set this as close as possible to the associated mdmLineCapabilitiesEnableRequested value. The agent shall make this determination in an implementation- specific manner that may take into account the configuration of other capabilities or other considerations. The modem will choose in an implementation-specific manner between multiple mutually-exclusive capabilities that each have the same (non-disabled) value. However, the modem must prefer all capabilities with a value of 'preferred(3)' over all capabilities with a value of 'optional(2)'. In other words, if there are one or more mutually-exclusive capabilities (e.g. V.32 and V.32bis) that are set to `preferred', the agent must choose one in an implementation-specific manner. Otherwise, if there are one or more mutually-exclusive capabilities that are set to `optional', the agent must choose one in an implementation- specific manner.
.1.3.6.1.2.1.38.1.1.5,Modem-MIB::mdmLineCapabilities,,,,,,
.1.3.6.1.2.1.38.1.1.5.1,Modem-MIB::mdmLineCapabilitiesV21,,,,,,ITU V.21
.1.3.6.1.2.1.38.1.1.5.2,Modem-MIB::mdmLineCapabilitiesV22,,,,,,ITU V.22
.1.3.6.1.2.1.38.1.1.5.3,Modem-MIB::mdmLineCapabilitiesV22bis,,,,,,ITU V.22bis
.1.3.6.1.2.1.38.1.1.5.4,Modem-MIB::mdmLineCapabilitiesV23CC,,,,,,ITU V.23CC
.1.3.6.1.2.1.38.1.1.5.5,Modem-MIB::mdmLineCapabilitiesV23SC,,,,,,ITU V.23SC
.1.3.6.1.2.1.38.1.1.5.6,Modem-MIB::mdmLineCapabilitiesV25bis,,,,,,ITU V.25bis
.1.3.6.1.2.1.38.1.1.5.7,Modem-MIB::mdmLineCapabilitiesV26bis,,,,,,ITU V.26bis
.1.3.6.1.2.1.38.1.1.5.8,Modem-MIB::mdmLineCapabilitiesV26ter,,,,,,ITU V.26ter
.1.3.6.1.2.1.38.1.1.5.9,Modem-MIB::mdmLineCapabilitiesV27ter,,,,,,ITU V.27ter
.1.3.6.1.2.1.38.1.1.5.10,Modem-MIB::mdmLineCapabilitiesV32,,,,,,ITU V.32
.1.3.6.1.2.1.38.1.1.5.11,Modem-MIB::mdmLineCapabilitiesV32bis,,,,,,ITU V.32bis
.1.3.6.1.2.1.38.1.1.5.12,Modem-MIB::mdmLineCapabilitiesV32terbo,,,,,,ITU V.32terbo
.1.3.6.1.2.1.38.1.1.5.13,Modem-MIB::mdmLineCapabilitiesVFC,,,,,,ITU V.FC
.1.3.6.1.2.1.38.1.1.5.14,Modem-MIB::mdmLineCapabilitiesV34,,,,,,ITU V.34
.1.3.6.1.2.1.38.1.1.5.15,Modem-MIB::mdmLineCapabilitiesV42,,,,,,ITU V.42
.1.3.6.1.2.1.38.1.1.5.16,Modem-MIB::mdmLineCapabilitiesV42bis,,,,,,ITU V.42bis
.1.3.6.1.2.1.38.1.1.5.17,Modem-MIB::mdmLineCapabilitiesMNP1,,,,,,MNP1
.1.3.6.1.2.1.38.1.1.5.18,Modem-MIB::mdmLineCapabilitiesMNP2,,,,,,MNP2
.1.3.6.1.2.1.38.1.1.5.19,Modem-MIB::mdmLineCapabilitiesMNP3,,,,,,MNP3
.1.3.6.1.2.1.38.1.1.5.20,Modem-MIB::mdmLineCapabilitiesMNP4,,,,,,MNP4
.1.3.6.1.2.1.38.1.1.5.21,Modem-MIB::mdmLineCapabilitiesMNP5,,,,,,MNP5
.1.3.6.1.2.1.38.1.1.5.22,Modem-MIB::mdmLineCapabilitiesMNP6,,,,,,MNP6
.1.3.6.1.2.1.38.1.1.5.23,Modem-MIB::mdmLineCapabilitiesMNP7,,,,,,MNP7
.1.3.6.1.2.1.38.1.1.5.24,Modem-MIB::mdmLineCapabilitiesMNP8,,,,,,MNP8
.1.3.6.1.2.1.38.1.1.5.25,Modem-MIB::mdmLineCapabilitiesMNP9,,,,,,MNP9
.1.3.6.1.2.1.38.1.1.5.26,Modem-MIB::mdmLineCapabilitiesMNP10,,,,,,MNP10
.1.3.6.1.2.1.38.1.1.5.27,Modem-MIB::mdmLineCapabilitiesV29,,,,,,ITU V.29
.1.3.6.1.2.1.38.1.1.5.28,Modem-MIB::mdmLineCapabilitiesV33,,,,,,ITU V.33
.1.3.6.1.2.1.38.1.1.5.29,Modem-MIB::mdmLineCapabilitiesBell208,,,,,,Bell 208
.1.3.6.1.2.1.38.1.1.6,Modem-MIB::mdmDTEInterfaceTable,,not-accessible,,current,,The modem DTE Interface Table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.6.1,Modem-MIB::mdmDTEInterfaceEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.6.1.1,Modem-MIB::mdmDTEActionDTROnToOff,INTEGER,read-write,,current,ignore(1):escapeToCommandMode(2):disconnectCall(3):resetModem(4),Defines the action the modem will take when DTR drops. If the value is set to ignore(1), the modem takes no action when DTR drops. Typically, mdmDTEActionDTROffToOn would also be set to ignore(1) if this object is set to ignore(1). If the value is escapeToCommandMode(2), the modem remains connected and enters command mode. If the value is disconnectCall(3), the current call (if any) is terminated and the modem will not auto-answer while DTR is off. If the value is resetModem(4), the current call (if any) is terminated and the modem is reset.
.1.3.6.1.2.1.38.1.1.6.1.2,Modem-MIB::mdmDTEActionDTROffToOn,INTEGER,read-write,,current,ignore(1):enableDial(2):autoAnswerEnable(3):establishConnection(4),Defines the action the modem will take when DTR is raised. If the value is set to ignore(1), the modem takes no action when DTR is raised. Typically, mdmDTEActionDTROnToOff would also be set to ignore(1) if this object is set to ignore(1). If the value is set to enableDial(2), the modem prepares to dial an outgoing call. If the value is set to autoAnswerEnable(3), the modem will be configured to answer any incoming call. If the value is set to establishConnection(4), the modem dials an implementation specific number. Immediately after any reset or power-on of the modem, if the DTR is high, the action specified here will be executed.
.1.3.6.1.2.1.38.1.1.6.1.3,Modem-MIB::mdmDTESyncTimingSource,INTEGER,read-write,,current,internal(1):external(2):loopback(3):network(4),The clock source for synchronous transmissions. If set to internal(1), the modem is the clock source and sends the clock signals to the DTE. If set to external(2), the transmit clock signals are provided by the DTE. If loopback(3), the modem receiver clock is used for the transmit clock. If network(4), the clock signals are supplied by the DCE interface. If the modem is not in synchronous mode, setting this object will have no effect on the current operations of the modem.
.1.3.6.1.2.1.38.1.1.6.1.4,Modem-MIB::mdmDTESyncAsyncMode,INTEGER,read-write,,current,async(1):sync(2):syncAfterDial(3),The operational mode of the modem. If the value is syncAfterDial(3), the modem will accept commands in asynchronous mode and change to synchronous mode to pass data after a dial sequence has been executed.
.1.3.6.1.2.1.38.1.1.6.1.5,Modem-MIB::mdmDTEInactivityTimeout,Integer32,read-write,,current,,The amount of idle time in minutes that the modem will wait before disconnecting a connection. When a call is connected and no data is transferred (continuous marking condition) on both circuits 103 and 104 for the specified time, the DCE disconnects the call. If the value is 0, no idle disconnect will occur. This function applies to asynchronous dial operations only and is intended for administrative control over idle connections.
.1.3.6.1.2.1.38.1.1.7,Modem-MIB::mdmCallControlTable,,not-accessible,,current,,The modem Call Control Table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.7.1,Modem-MIB::mdmCallControlEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.7.1.1,Modem-MIB::mdmCCRingsBeforeAnswer,Integer32,read-write,,current,,Determines which ring the modem will wait to answer the phone on. If this value is `0', the modem will not go offhook and answer a call when a ring signal is detected.
.1.3.6.1.2.1.38.1.1.7.1.2,Modem-MIB::mdmCCCallSetUpFailTimer,Integer32,read-write,,current,,This parameter specifies the amount of time, in seconds, that the modem shall allow between either answering a call (automatically or manually) or completion of dialing, and establishment of a connection with the remote modem. If no connection is established during this time, the modem disconnects from the line and returns a result code indicating the cause of the disconnection. In TIA-602, this is controlled by the value in the S7 register.
.1.3.6.1.2.1.38.1.1.7.1.3,Modem-MIB::mdmCCResultCodeEnable,INTEGER,read-write,,current,disabled(1):numericEnabled(2):verboseEnabled(3),When disabled, the DCE shall issue no 'result codes' of any kind to the DTE either in response to unsolicited events (eg. ring signal), or commands. In TIA-602, this is controlled by the ATQ command. When numericEnabled, the DCE shall issue result codes in numeric form. When verboseEnabled, the DCE shall issue result codes in a verbose, textual form.
.1.3.6.1.2.1.38.1.1.7.1.4,Modem-MIB::mdmCCEscapeAction,INTEGER,read-write,,current,ignoreEscape(1):hangUp(2):enterCommandMode(3),The modem's action upon successfully recognizing the 'escape to command mode' character sequence.
.1.3.6.1.2.1.38.1.1.7.1.5,Modem-MIB::mdmCCCallDuration,Integer32,read-only,,current,,Present or last completed connection time in seconds. If there have been no previous connections, this value should be -1.
.1.3.6.1.2.1.38.1.1.7.1.6,Modem-MIB::mdmCCConnectionFailReason,INTEGER,read-only,,current,unknown(1):other(2):managementCommand(3):inactivityTimeout(4):mnpIncompatibility(5):protocolError(6):powerLoss(10):equipmentFailure(11):dtrDrop(20):noDialTone(30):lineBusy(31):noAnswer(32):voiceDetected(33):carrierLost(40):trainingFailed(41):faxDetected(42),Indicates the reason that the last connection or attempt failed. The meaning of each reason code is explained below. unknown: This code means the failure reason is unknown or there has been no previous call. other: This code used when no other code is applicable. Additional vendor information may be available elsewhere. managementCommand: A management command terminated the call. These commands include escaping to command mode, initiating dialing, restoring lines, and disconnecting. inactivityTimeout: The call was terminated because it was inactive for at the minimum duration specified. mnpIncompatibility: The modems are unable to resolve MNP protocol differences. protocolError: An error occured in one of protocol in use. Further information is required to determine in which protocol the error occurred, and the exact nature of the error. powerLoss: The modem lost power and disconnected the call. equipmentFailure: The modem equipment failed. dtrDrop: DTR has been turned off while the modem is to disconnect on DTR drop. (Ref: V.58 cct108TurnedOff) noDialTone: If the modem is to monitor for call progress tones, but the modem has failed to detect dial tone while attempting to dial a number. lineBusy: Busy signal is detected while busy signal detection is enabled, or while the 'W' or '@' dial modifier is used. (Ref: V.58 engagedTone) noAnswer: The call was not answered. voiceDetected: A voice was detected on the call. carrierLost: Indicates that the modem has disconnected due to detection of loss of carrier. In TIA-602, the S10 register determines the time that loss of carrier must be detected before the modem disconnects. trainingFailed: Indicates that the modems did not successfully train and reach data mode on the previous connection. faxDetected: A fax was detected on the call.
.1.3.6.1.2.1.38.1.1.8,Modem-MIB::mdmCCStoredDialStringTable,,not-accessible,,current,,The table of stored dial strings.
.1.3.6.1.2.1.38.1.1.8.1,Modem-MIB::mdmCCStoredDialStringEntry,,not-accessible,mdmIndex:mdmCCStoredDialStringIndex,current,,A stored dial string.
.1.3.6.1.2.1.38.1.1.8.1.1,Modem-MIB::mdmCCStoredDialStringIndex,Integer32,not-accessible,,current,,The unique index of a particular dial string.
.1.3.6.1.2.1.38.1.1.8.1.2,Modem-MIB::mdmCCStoredDialString,OCTET,read-write,,current,,A dial string stored in the modem.
.1.3.6.1.2.1.38.1.1.9,Modem-MIB::mdmECTable,,not-accessible,,current,,The modem error correcting table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.9.1,Modem-MIB::mdmECEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.9.1.1,Modem-MIB::mdmECErrorControlUsed,OBJECT,read-only,,current,,Indicates the error control method used during the current or previous call. This shall be one of the values for error control protocols registered in the capabilities table for this modem. If no error control protocol is in use, this object shall have the value '{0 0}'.
.1.3.6.1.2.1.38.1.1.10,Modem-MIB::mdmDCTable,,not-accessible,,current,,The modem data compression table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.10.1,Modem-MIB::mdmDCEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.10.1.1,Modem-MIB::mdmDCCompressionTypeUsed,OBJECT,read-only,,current,,Indicates the data compression method used during the current or previous call. This shall be one of the values for compression protocols registered in the capabilities table for this modem. If no compression protocol is in use, this object shall have the value '{0 0}'.
.1.3.6.1.2.1.38.1.1.11,Modem-MIB::mdmSCTable,,not-accessible,,current,,The modem signal convertor table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.11.1,Modem-MIB::mdmSCEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.11.1.1,Modem-MIB::mdmSCCurrentLineTransmitRate,Integer32,read-only,,current,,The current link transmit rate of a connection, or the last link transmit rate of the last connection in bits per second.
.1.3.6.1.2.1.38.1.1.11.1.2,Modem-MIB::mdmSCCurrentLineReceiveRate,Integer32,read-only,,current,,The current link receive rate of a connection, or the last link receive rate of the last connection in bits per second.
.1.3.6.1.2.1.38.1.1.11.1.3,Modem-MIB::mdmSCInitialLineTransmitRate,Integer32,read-only,,current,,The initial link transmit rate of the current connection, or the initial link transmit rate of the last connection in bits per second.
.1.3.6.1.2.1.38.1.1.11.1.4,Modem-MIB::mdmSCInitialLineReceiveRate,Integer32,read-only,,current,,The initial link receive rate of the current connection, or the initial link receive rate of the last connection in bits per second.
.1.3.6.1.2.1.38.1.1.11.1.5,Modem-MIB::mdmSCModulationSchemeUsed,OBJECT,read-only,,current,,The modulation scheme of the current or previous call. This shall be one of the values for modulation protocols registered in the capabilities table for this modem.
.1.3.6.1.2.1.38.1.1.12,Modem-MIB::mdmStatsTable,,not-accessible,,current,,The modem statistics Table augments the modem ID table.
.1.3.6.1.2.1.38.1.1.12.1,Modem-MIB::mdmStatsEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each modem managed by the agent.
.1.3.6.1.2.1.38.1.1.12.1.1,Modem-MIB::mdmStatsRingNoAnswers,Counter32,read-only,,current,,The number of events in which ringing was detected but the call was not answered.
.1.3.6.1.2.1.38.1.1.12.1.2,Modem-MIB::mdmStatsIncomingConnectionFailures,Counter32,read-only,,current,,The number of incoming connection requests that this modem answered in which it could not train with the other DCE.
.1.3.6.1.2.1.38.1.1.12.1.3,Modem-MIB::mdmStatsIncomingConnectionCompletions,Counter32,read-only,,current,,The number of incoming connection requests that this modem answered and successfully trained with the other DCE.
.1.3.6.1.2.1.38.1.1.12.1.4,Modem-MIB::mdmStatsFailedDialAttempts,Counter32,read-only,,current,,The number of call attempts that failed because the modem didn't go off hook, or there was no dialtone.
.1.3.6.1.2.1.38.1.1.12.1.5,Modem-MIB::mdmStatsOutgoingConnectionFailures,Counter32,read-only,,current,,The number of outgoing calls from this modem which sucessfully went off hook and dialed, in which it could not train with the other DCE.
.1.3.6.1.2.1.38.1.1.12.1.6,Modem-MIB::mdmStatsOutgoingConnectionCompletions,Counter32,read-only,,current,,The number of outgoing calls from this modem which resulted in successfully training with the other DCE.
.1.3.6.1.2.1.38.1.1.12.1.7,Modem-MIB::mdmStatsRetrains,Counter32,read-only,,current,,The number of retrains experienced on connections on this line.
.1.3.6.1.2.1.38.1.1.12.1.8,Modem-MIB::mdmStats2400OrLessConnections,Counter32,read-only,,current,,The number of connections initially established at a modulation speed of 2400 bits per second or less.
.1.3.6.1.2.1.38.1.1.12.1.9,Modem-MIB::mdmStats2400To14400Connections,Counter32,read-only,,current,,The number of connections initially established at a modulation speed of greater than 2400 bits per second and less than 14400 bits per second.
.1.3.6.1.2.1.38.1.1.12.1.10,Modem-MIB::mdmStatsGreaterThan14400Connections,Counter32,read-only,,current,,The number of connections initially established at a modulation speed of greater than 14400 bits per second.
.1.3.6.1.2.1.38.1.1.12.1.11,Modem-MIB::mdmStatsErrorControlledConnections,Counter32,read-only,,current,,The number of established connections using an error control protocol.
.1.3.6.1.2.1.38.1.1.12.1.12,Modem-MIB::mdmStatsCompressedConnections,Counter32,read-only,,current,,The number of established connections using a compression protocol.
.1.3.6.1.2.1.38.1.1.12.1.13,Modem-MIB::mdmStatsCompressionEfficiency,Integer32,read-only,,current,,The number of bytes transferred into the compression encoder divided by the number of bytes transferred out of the encoder, multiplied by 100 for either the current or last call. If a data compression protocol is not in use, this value shall be `100'.
.1.3.6.1.2.1.38.1.1.12.1.14,Modem-MIB::mdmStatsSentOctets,Counter32,read-only,,current,,The number of octets presented to the modem by the DTE.
.1.3.6.1.2.1.38.1.1.12.1.15,Modem-MIB::mdmStatsReceivedOctets,Counter32,read-only,,current,,The number of octets presented to the DTE by the modem.
.1.3.6.1.2.1.38.1.1.12.1.16,Modem-MIB::mdmStatsSentDataFrames,Counter32,read-only,,current,,The number of data frames sent on the line interface. If there is no frame-oriented protocol in use on the line interface, this counter shall not increment.
.1.3.6.1.2.1.38.1.1.12.1.17,Modem-MIB::mdmStatsReceivedDataFrames,Counter32,read-only,,current,,The number of data frames received on the line interface. If there is no frame-oriented protocol in use on the line interface, this counter shall not increment.
.1.3.6.1.2.1.38.1.1.12.1.18,Modem-MIB::mdmStatsResentFrames,Counter32,read-only,,current,,The number of times this modem retransmits frames on the line interface. If there is no frame-oriented protocol in use on the line interface, this counter shall not increment.
.1.3.6.1.2.1.38.1.1.12.1.19,Modem-MIB::mdmStatsErrorFrames,Counter32,read-only,,current,,The number of block errors received on the link. If there is no frame-oriented protocol in use on the line interface, this counter shall not increment.
.1.3.6.1.2.1.38.1.2,Modem-MIB::mdmConformance,,,,,,
.1.3.6.1.2.1.38.1.2.1,Modem-MIB::mdmCompliances,,,,,,
.1.3.6.1.2.1.38.1.2.1.1,Modem-MIB::mdmCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the modem MIB.
.1.3.6.1.2.1.38.1.2.2,Modem-MIB::mdmGroups,,,,,,
.1.3.6.1.2.1.38.1.2.2.1,Modem-MIB::mdmIDGroup,,,,,,A collection of objects that identify the manufacturer and model information for a modem.
.1.3.6.1.2.1.38.1.2.2.2,Modem-MIB::mdmLineInterfaceGroup,,,,,,A collection of objects that describe the configuration and state of the modem's line interface.
.1.3.6.1.2.1.38.1.2.2.3,Modem-MIB::mdmDTEInterfaceGroup,,,,,,A collection of objects that describe the configuration and state of the modem's DTE interface.
.1.3.6.1.2.1.38.1.2.2.4,Modem-MIB::mdmCallControlGroup,,,,,,A collection of objects that describe the configuration of call control capabilities on the modem and the status of calls placed with this modem.
.1.3.6.1.2.1.38.1.2.2.5,Modem-MIB::mdmErrorControlGroup,,,,,,A collection of objects that describe the configuration and state of error control on a modem.
.1.3.6.1.2.1.38.1.2.2.6,Modem-MIB::mdmDataCompressionGroup,,,,,,A collection of objects that describe the configuration and state of data compression on a modem.
.1.3.6.1.2.1.38.1.2.2.7,Modem-MIB::mdmSignalConvertorGroup,,,,,,A collection of objects that describe the configuration and state of error control on a modem.
.1.3.6.1.2.1.38.1.2.2.8,Modem-MIB::mdmStatisticsGroup,,,,,,A collection of objects that describe the state of calls on this modem.
.1.3.6.1.2.1.39,RDBMS-MIB::rdbmsMIB,,,,,,The MIB module to describe objects for generic relational databases.
.1.3.6.1.2.1.39.1,RDBMS-MIB::rdbmsObjects,,,,,,
.1.3.6.1.2.1.39.1.1,RDBMS-MIB::rdbmsDbTable,,not-accessible,,current,,The table of databases installed on a system.
.1.3.6.1.2.1.39.1.1.1,RDBMS-MIB::rdbmsDbEntry,,not-accessible,rdbmsDbIndex,current,,An entry for a single database on the host. Whether a particular database is represented by a row in rdbmsDbTable may be dependent on the activity level of that database, according to the product's implementation. An instance of rdbmsRelState having the value active, other, or restricted implies that an entry, corresponding to that instance, will be present.
.1.3.6.1.2.1.39.1.1.1.1,RDBMS-MIB::rdbmsDbIndex,INTEGER,not-accessible,,current,,A numeric index, unique among all the databases from all products on this host. This value is a surrogate for the conceptually unique key, which is {PrivateMibOID, databasename}
.1.3.6.1.2.1.39.1.1.1.2,RDBMS-MIB::rdbmsDbPrivateMibOID,OBJECT,read-only,,current,,The authoritative identification for the private MIB for this database, presumably based on the vendor, e.g., { enterprises 111 <optional subidentifiers>} for Oracle databases, {enterprises 757 <optional subidentifiers>} for Ingres databases, { enterprises 897 <optional subidentifiers>} for Sybase databases, etc. If no OBJECT IDENTIFIER exists for the private MIB, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.1.1.3,RDBMS-MIB::rdbmsDbVendorName,OCTET,read-only,,current,,The name of the vendor whose RDBMS manages this database, for informational purposes.
.1.3.6.1.2.1.39.1.1.1.4,RDBMS-MIB::rdbmsDbName,OCTET,read-only,,current,,The name of this database, in a product specific format. The product may need to qualify the name in some way to resolve conflicts if it is possible for a database name to be duplicated on a host. It might be necessary to construct a hierarchical name embedding the RDBMS instance/installation on the host, and/or the owner of the database. For instance, '/test-installation/database-owner/database-name'.
.1.3.6.1.2.1.39.1.1.1.5,RDBMS-MIB::rdbmsDbContact,OCTET,read-write,,current,,The textual identification of the contact person for this managed database, together with information on how to contact this person. Note: if there is no server associated with this database, an agent may need to keep this in other persistent storage, e.g., a configuration file. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.2,RDBMS-MIB::rdbmsDbInfoTable,,not-accessible,,current,,The table of additional information about databases present on the host.
.1.3.6.1.2.1.39.1.2.1,RDBMS-MIB::rdbmsDbInfoEntry,,not-accessible,rdbmsDbIndex,current,,Information that must be present if the database is actively opened. If the database is not actively opened, then attempts to access corresponding instances in this table may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2). 'Actively opened' means at least one of the rdbmsRelState entries for this database in the rdbmsRelTable is active(2).
.1.3.6.1.2.1.39.1.2.1.1,RDBMS-MIB::rdbmsDbInfoProductName,OCTET,read-only,,current,,The textual product name of the server that created or last restructured this database. The format is product specific.
.1.3.6.1.2.1.39.1.2.1.2,RDBMS-MIB::rdbmsDbInfoVersion,OCTET,read-only,,current,,The version number of the server that created or last restructured this database. The format is product specific.
.1.3.6.1.2.1.39.1.2.1.3,RDBMS-MIB::rdbmsDbInfoSizeUnits,INTEGER,read-only,,current,bytes(1):kbytes(2):mbytes(3):gbytes(4):tbytes(5),Identification of the units used to measure the size of this database in rdbmsDbInfoSizeAllocated and rdbmsDbInfoSizeUsed. bytes(1) indicates individual bytes, kbytes(2) indicates units of kilobytes, mbytes(3) indicates units of megabytes, gbytes(4) indicates units of gigabytes, and tbytes(5) indicates units of terabytes. All are binary multiples -- 1K = 1024. If writable, changes here are reflected in the get values of the associated objects.
.1.3.6.1.2.1.39.1.2.1.4,RDBMS-MIB::rdbmsDbInfoSizeAllocated,INTEGER,read-write,,current,,The estimated size of this database (in rdbmsDbInfoSizeUnits), which is the disk space that has been allocated to it and is no longer available to users on this host. rdbmsDbInfoSize does not necessarily indicate the amount of space actually in use for database data. Some databases may support extending allocated size, and others may not. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.2.1.5,RDBMS-MIB::rdbmsDbInfoSizeUsed,INTEGER,read-only,,current,,The estimated size of this database, in rdbmsDbInfoSizeUnits, which is actually in use for database data.
.1.3.6.1.2.1.39.1.2.1.6,RDBMS-MIB::rdbmsDbInfoLastBackup,OCTET,read-only,,current,,The date and time that the latest complete or partial backup of the database was taken. If a database has never been backed up, then attempts to access this object will result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.3,RDBMS-MIB::rdbmsDbParamTable,,not-accessible,,current,,The table of configuration parameters for a database. Entries should be populated according to the following guidelines: (1) The value should be specified through administrative (human) intervention. (2) It should be configured on a per-database basis. (3) One of the following is true: (a) The parameter has a non-numeric value; (b) The current value is numeric, but it only changes due to human intervention; (c) The current value is numeric and dynamic, but the RDBMS does not track access/allocation failures related to the parameter; (d) The current value is numeric and dynamic, the RDBMS tracks changes in access/allocation failures related to the parameter, but the failure has no significant impact on RDBMS performance or availability. (e) The current value is numeric and dynamic, the RDBMS tracks changes in access/allocation failures related to the parameter, the failure has significant impact on RDBMS performance or availability, and is shown in the rdbmsDbLimitedResource table.
.1.3.6.1.2.1.39.1.3.1,RDBMS-MIB::rdbmsDbParamEntry,,not-accessible,rdbmsDbIndex:rdbmsDbParamName:rdbmsDbParamSubIndex,current,,An entry for a single configuration parameter for a database. Parameters with single values have a subindex value of one. If the parameter is naturally considered to contain a variable number of members of a class, e.g. members of the DBA user group, or files which are part of the database, then it must be presented as a set of rows. If, on the other hand, the parameter represents a set of choices from a class, e.g. the permissions on a file or the options chosen out of the set of all options allowed, AND is guaranteed to always fit in the 255 character length of a DisplayString, then it may be presented as a comma separated list with a subindex value of one. Zero may not be used as a subindex value. If the database is not actively opened, then attempts to access corresponding instances in this table may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2). 'Actively opened' means at least one of the rdbmsRelState entries for this database in the rdbmsRelTable is active(2).
.1.3.6.1.2.1.39.1.3.1.1,RDBMS-MIB::rdbmsDbParamName,OCTET,not-accessible,,current,,The name of a configuration parameter for a database. This name is product-specific. The length is limited to 64 characters to constrain the number of sub-identifiers needed for instance identification (and to minimize network traffic).
.1.3.6.1.2.1.39.1.3.1.2,RDBMS-MIB::rdbmsDbParamSubIndex,INTEGER,not-accessible,,current,,The subindex value for this parameter. If the parameter is naturally considered to contain a variable number of members of a class, e.g. members of the DBA user group, or files which are part of the database, then it must be presented as a set of rows. If, on the other hand, the parameter represents a set of choices from a class, e.g. the permissions on a file or the options chosen out of the set of all options allowed, AND is guaranteed to always fit in the 255 character length of a DisplayString, then it may be presented as a comma separated list with a subindex value of one. Zero may not be used as a value.
.1.3.6.1.2.1.39.1.3.1.3,RDBMS-MIB::rdbmsDbParamID,OBJECT,read-only,,current,,The ID of the parameter which may be described in some other MIB (e.g., an enterprise-specific MIB module). If there is no ID for this rdbmsDbParamName, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.3.1.4,RDBMS-MIB::rdbmsDbParamCurrValue,OCTET,read-write,,current,,The value for a configuration parameter now in effect, the actual setting for the database. While there may multiple values in the temporal domain of interest (for instance, the value to take effect at the next restart), this is the current setting. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.3.1.5,RDBMS-MIB::rdbmsDbParamComment,OCTET,read-write,,current,,Annotation which describes the purpose of a configuration parameter or the reason for a particular parameter's setting. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.4,RDBMS-MIB::rdbmsDbLimitedResourceTable,,not-accessible,,current,,The table of limited resources that are kept per-database.
.1.3.6.1.2.1.39.1.4.1,RDBMS-MIB::rdbmsDbLimitedResourceEntry,,not-accessible,rdbmsDbIndex:rdbmsDbLimitedResourceName,current,,An entry for a single limited resource kept per-database. A limited resource has maximum use determined by a parameter that might or might not be changeable at run time, or visible in the rdbmsDbParamTable. Examples would be the number of available locks, or disk space on a partition. Arrays of resources are supported through an integer sub index, which should have the value of one for single-instance names. Limited resources that are shared across databases, are best put in the rdbmsSvrLimitedResourceTable instead of this one. If the database is not actively opened, then attempts to access corresponding instances in this table may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2). 'Actively opened' means at least one of the rdbmsRelState entries for this database in the rdbmsRelTable is active(2).
.1.3.6.1.2.1.39.1.4.1.1,RDBMS-MIB::rdbmsDbLimitedResourceName,OCTET,not-accessible,,current,,The name of the resource, for instance 'global locks' or 'locks for the FOO database', or 'data space on /dev/rdsk/5s0 for FOO'. The length is limited to 64 characters to constrain the number of sub-identifiers needed for instance identification (and to minimize network traffic).
.1.3.6.1.2.1.39.1.4.1.2,RDBMS-MIB::rdbmsDbLimitedResourceID,OBJECT,read-only,,current,,The ID of the resource which may be described in some other MIB (e.g., an enterprise-specific MIB module). If there is no ID for this rdbmsDbLimitedResourceName, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.4.1.3,RDBMS-MIB::rdbmsDbLimitedResourceLimit,INTEGER,read-write,,current,,The maximum value the resource use may attain. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.4.1.4,RDBMS-MIB::rdbmsDbLimitedResourceCurrent,INTEGER,read-only,,current,,The current value for the resource.
.1.3.6.1.2.1.39.1.4.1.5,RDBMS-MIB::rdbmsDbLimitedResourceHighwater,INTEGER,read-only,,current,,The maximum value of the resource seen since applUpTime was reset for the earliest server which has the database actively opened. If there are two servers with the database open, and the oldest one dies, the proper way to invalidate the value is by resetting sysUpTime.
.1.3.6.1.2.1.39.1.4.1.6,RDBMS-MIB::rdbmsDbLimitedResourceFailures,Counter32,read-only,,current,,The number of times the system wanted to exceed the limit of the resource since applUpTime was reset for the earliest server which has the database actively opened. If there are two servers with the DB open, and the oldest one dies, the proper way to invalidate the value is by resetting sysUpTime.
.1.3.6.1.2.1.39.1.4.1.7,RDBMS-MIB::rdbmsDbLimitedResourceDescription,OCTET,read-write,,current,,A description of the resource and the meaning of the integer units used for Limit, Current, and Highwater. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.5,RDBMS-MIB::rdbmsSrvTable,,not-accessible,,current,,The table of database servers running or installed on a system.
.1.3.6.1.2.1.39.1.5.1,RDBMS-MIB::rdbmsSrvEntry,,not-accessible,applIndex,current,,An entry for a single database server. A server is an independent entity that provides access to one or more databases. Failure of one does not affect access to databases through any other servers. There might be one or more servers providing access to a database. A server may be a 'process' or collection of 'processes', as interpreted by the product.
.1.3.6.1.2.1.39.1.5.1.1,RDBMS-MIB::rdbmsSrvPrivateMibOID,OBJECT,read-only,,current,,The authoritative identification for the private MIB for this server, presumably based on the vendor, e.g., { enterprises 111 <optional subidentifiers>} for Oracle servers, { enterprises 757 <optional subidentifiers>} for Ingres servers, { enterprises 897 <optional subidentifiers>} for Sybase servers, etc. If no OBJECT IDENTIFIER exists for the private MIB, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.5.1.2,RDBMS-MIB::rdbmsSrvVendorName,OCTET,read-only,,current,,The name of the vendor whose RDBMS manages this database, for informational purposes.
.1.3.6.1.2.1.39.1.5.1.3,RDBMS-MIB::rdbmsSrvProductName,OCTET,read-only,,current,,The product name of this server. This is normally the vendor's formal name for the product, in product specific format.
.1.3.6.1.2.1.39.1.5.1.4,RDBMS-MIB::rdbmsSrvContact,OCTET,read-write,,current,,The textual identification of the contact person for this managed server, together with information on how to contact this person. Note: if there is no active server associated with this object, an agent may need to keep this in other persistent storage, e.g., a configuration file. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.6,RDBMS-MIB::rdbmsSrvInfoTable,,not-accessible,,current,,The table of additional information about database servers. Entries in this table correspond to applications in the APPLICATION-MIB applTable. Some objects in that table are application-specific. When they are associated with an RDBMS server in this table, the objects have the following meanings. applName - The name of this server, i.e., the process or group of processes providing access to this database. The exact format will be product and host specific. applVersion - The version number of this server, in product specific format. applOperStatus - up(1) means operational and available for general use. down(2) means the server is not available for use, but is known to the agent. The other states have broad meaning, and may need to be supplemented by the vendor private MIB. Halted(3) implies an administrative state of unavailability. Congested(4) implies a resource or or administrative limit is prohibiting new inbound associations. The 'available soon' description of restarting(5) may include an indeterminate amount of recovery. applLastChange is the time the agent noticed the most recent change to applOperStatus. applInboundAssociation is the number of currently active local and remote conversations (usually SQL connects). applOutboundAssociations is not provided by this MIB. applAccumulatedInboundAssociations is the total number of local and remote conversations started since the server came up. applAccumulatedOutbound associations is not provided by this MIB. applLastInboundActivity is the time the most recent local or remote conversation was attempted or disconnected. applLastOutboundActivity is not provided by this MIB. applRejectedInboundAssociations is the number of local or remote conversations rejected by the server for administrative reasons or because of resource limitations. applFailedOutboundAssociations is not provided by this MIB.
.1.3.6.1.2.1.39.1.6.1,RDBMS-MIB::rdbmsSrvInfoEntry,,not-accessible,applIndex,current,,Information that must be present for a single 'up' database server, with visibility determined by the value of the corresponding applOperStatus object. If an instance of applOperStatus is not up(1), then attempts to access corresponding instances in this table may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2) being returned by the agent.
.1.3.6.1.2.1.39.1.6.1.1,RDBMS-MIB::rdbmsSrvInfoStartupTime,OCTET,read-only,,current,,The date and time at which this server was last started.
.1.3.6.1.2.1.39.1.6.1.2,RDBMS-MIB::rdbmsSrvInfoFinishedTransactions,Gauge32,read-only,,current,,The number of transactions visible to this server that have been completed by either commit or abort. Some database operations, such as read-only queries, may not result in the creation of a transaction.
.1.3.6.1.2.1.39.1.6.1.3,RDBMS-MIB::rdbmsSrvInfoDiskReads,Counter32,read-only,,current,,The total number of reads of database files issued to the operating system by this server since startup. Numbers are not comparable between products. What constitutes a readand how it is accounted is product-specific.
.1.3.6.1.2.1.39.1.6.1.4,RDBMS-MIB::rdbmsSrvInfoLogicalReads,Counter32,read-only,,current,,The total number of logical reads of database files made internally by this server since startup. The values of this object and those of rdbmsSrvInfoDiskReads reveal the effect of caching on read operation. Numbers are not comparable between products, and may only be meaningful when aggregated across all servers sharing a common cache.
.1.3.6.1.2.1.39.1.6.1.5,RDBMS-MIB::rdbmsSrvInfoDiskWrites,Counter32,read-only,,current,,The total number of writes to database files issued to the operating system by this server since startup. Numbers are not comparable between products.
.1.3.6.1.2.1.39.1.6.1.6,RDBMS-MIB::rdbmsSrvInfoLogicalWrites,Counter32,read-only,,current,,The total number of times parts of the database files have been marked 'dirty' and in need of writing to the disk. This value and rdbmsSrvInfoDiskWrites give some indication of the effect of 'write-behind' strategies in reducing the number of disk writes compared to database operations. Because the writes may be done by servers other than those marking the parts of the database files dirty, these values may only be meaningful when aggregated across all servers sharing a common cache. Numbers are not comparable between products.
.1.3.6.1.2.1.39.1.6.1.7,RDBMS-MIB::rdbmsSrvInfoPageReads,Counter32,read-only,,current,,The total number of pages in database files read by this server since startup. 'Pages' are product specific units of disk i/o operations. This value, along with rdbmsSrvInfoDiskReads, reveals the effect of any grouping read-ahead that may be used to enhance performance of some queries, such as scans.
.1.3.6.1.2.1.39.1.6.1.8,RDBMS-MIB::rdbmsSrvInfoPageWrites,Counter32,read-only,,current,,The total number of pages in database files written by this server since startup. Pages are product-specific units of disk I/O. This value, with rdbmsSrvInfoDiskWrites, shows the effect of write strategies that collapse logical writes of contiguous pages into single calls to the operating system.
.1.3.6.1.2.1.39.1.6.1.9,RDBMS-MIB::rdbmsSrvInfoDiskOutOfSpaces,Counter32,read-only,,current,,The total number of times the server has been unable to obtain disk space that it wanted, since server startup. This would be inspected by an agent on receipt of an rdbmsOutOfSpace trap.
.1.3.6.1.2.1.39.1.6.1.10,RDBMS-MIB::rdbmsSrvInfoHandledRequests,Counter32,read-only,,current,,The total number of requests made to the server on inbound associations. The meaning of 'requests' is product specific, and is not comparable between products. This is intended to encapsulate high level semantic operations between clients and servers, or between peers. For instance, one request might correspond to a 'select' or an 'insert' statement. It is not intended to capture disk i/o described in rdbmsSrvInfoDiskReads and rdbmsSrvInfoDiskWrites.
.1.3.6.1.2.1.39.1.6.1.11,RDBMS-MIB::rdbmsSrvInfoRequestRecvs,Counter32,read-only,,current,,The number of receive operations made processing any requests on inbound associations. The meaning of operations is product specific, and is not comparable between products. This is intended to capture lower-level i/o operations than shown by HandledRequests, between clients and servers, or between peers. For instance, it might roughly correspond to the amount of data given with an 'insert' statement. It is not intended to capture disk i/o described in rdbmsSrvInfoDiskReads and rdbmsSrvInfoDiskWrites.
.1.3.6.1.2.1.39.1.6.1.12,RDBMS-MIB::rdbmsSrvInfoRequestSends,Counter32,read-only,,current,,The number of send operations made processing requests handled on inbound associations. The meaning of operations is product specific, and is not comparable between products. This is intended to capture lower-level i/o operations than shown by HandledRequests, between between clients and servers, or between peers. It might roughly correspond to the number of rows returned by a 'select' statement. It is not intended to capture disk i/o described in DiskReads.
.1.3.6.1.2.1.39.1.6.1.13,RDBMS-MIB::rdbmsSrvInfoHighwaterInboundAssociations,Gauge32,read-only,,current,,The greatest number of inbound associations that have been simultaneously open to this server since startup.
.1.3.6.1.2.1.39.1.6.1.14,RDBMS-MIB::rdbmsSrvInfoMaxInboundAssociations,Gauge32,read-write,,current,,The greatest number of inbound associations that can be simultaneously open with this server. If there is no limit, then the value should be zero. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.7,RDBMS-MIB::rdbmsSrvParamTable,,not-accessible,,current,,The table of configuration parameters for a server. Entries should be populated according to the following guidelines: (1) The value should be specified through administrative (human) intervention. (2) It should be configured on a per-server or a more global basis, with duplicate entries for each server sharing use of the parameter. (3) One of the following is true: (a) The parameter has a non-numeric value; (b) The current value is numeric, but it only changes due to human intervention; (c) The current value is numeric and dynamic, but the RDBMS does not track access/allocation failures related to the parameter; (d) The current value is numeric and dynamic, the RDBMS tracks changes in access/allocation failures related to the parameter, but the failure has no significant impact on RDBMS performance or availability. (e) The current value is numeric and dynamic, the RDBMS tracks changes in access/allocation failures related to the parameter, the failure has significant impact on RDBMS performance or availability, and is shown in the rdbmsSrvLimitedResource table.
.1.3.6.1.2.1.39.1.7.1,RDBMS-MIB::rdbmsSrvParamEntry,,not-accessible,applIndex:rdbmsSrvParamName:rdbmsSrvParamSubIndex,current,,An entry for a single configuration parameter for a server. Parameters with single values have a subindex value of one. If the parameter is naturally considered to contain a variable number of members of a class, e.g. members of the DBA user group, or tracepoints active in the server, then it must be presented as a set of rows. If, on the other hand, the parameter represents a set of choices from a class, e.g. the permissions on a file or the options chosen out of the set of all options allowed, AND is guaranteed to always fit in the 255 character length of a DisplayString, then it may be presented as a comma separated list with a subindex value of one. Zero may not be used as a subindex value. Entries for a server must be present if the value of the corresponding applOperStatus object is up(1). If an instance of applOperStatus is not up(1), then attempts to access corresponding instances in this table may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2) being returned by the agent.
.1.3.6.1.2.1.39.1.7.1.1,RDBMS-MIB::rdbmsSrvParamName,OCTET,not-accessible,,current,,The name of a configuration parameter for a server. This name is product-specific. The length is limited to 64 characters to constrain the number of sub-identifiers needed for instance identification (and to minimize network traffic).
.1.3.6.1.2.1.39.1.7.1.2,RDBMS-MIB::rdbmsSrvParamSubIndex,INTEGER,not-accessible,,current,,The subindex value for this parameter. If the parameter is naturally considered to contain a variable number of members of a class, e.g. members of the DBA user group, or files which are part of the database, then it must be presented as a set of rows. If, on the other hand, the parameter represents a set of choices from a class, e.g. the permissions on a file or the options chosen out of the set of all options allowed, AND is guaranteed to always fit in the 255 character length of a DisplayString, then it may be presented as a comma separated list with a subindex value of one. Zero may not be used as a value.
.1.3.6.1.2.1.39.1.7.1.3,RDBMS-MIB::rdbmsSrvParamID,OBJECT,read-only,,current,,The ID of the parameter which may be described in some other MIB. If there is no ID for this rdbmsSrvParamName, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.7.1.4,RDBMS-MIB::rdbmsSrvParamCurrValue,OCTET,read-write,,current,,The value for a configuration parameter now in effect, the actual setting for the server. While there may multiple values in the temporal domain of interest (for instance, the value to take effect at the next restart), this is the current setting. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.7.1.5,RDBMS-MIB::rdbmsSrvParamComment,OCTET,read-write,,current,,Annotation which describes the purpose of a configuration parameter or the reason for a particular parameter's setting. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.8,RDBMS-MIB::rdbmsSrvLimitedResourceTable,,not-accessible,,current,,The table of limited resources relevant to a server.
.1.3.6.1.2.1.39.1.8.1,RDBMS-MIB::rdbmsSrvLimitedResourceEntry,,not-accessible,applIndex:rdbmsSrvLimitedResourceName,current,,An entry for a single limited resource kept by the server. A limited resource has maximum use determined by a parameter that might or might not changeable at run time, or visible in the rbmsSrvParamTable. Examples would be the number of available locks, or number of concurrent executions allowed in a server. Arrays of resources are supported through an integer subindex, which should have the value of one for single-instance names. Limited resources that are shared across servers or databases are best duplicated in this table across all servers accessing the resource.
.1.3.6.1.2.1.39.1.8.1.1,RDBMS-MIB::rdbmsSrvLimitedResourceName,OCTET,not-accessible,,current,,The name of the resource, for instance 'threads' or 'semaphores', or 'buffer pages'
.1.3.6.1.2.1.39.1.8.1.2,RDBMS-MIB::rdbmsSrvLimitedResourceID,OBJECT,read-only,,current,,The ID of the resource which may be described in some other MIB. If there is no ID for this rdbmsSrvLimitedResourceName, attempts to access this object will return noSuchName (SNMPv1) or noSuchInstance (SNMPv2).
.1.3.6.1.2.1.39.1.8.1.3,RDBMS-MIB::rdbmsSrvLimitedResourceLimit,INTEGER,read-write,,current,,The maximum value the resource use may attain. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.8.1.4,RDBMS-MIB::rdbmsSrvLimitedResourceCurrent,INTEGER,read-only,,current,,The current value for the resource.
.1.3.6.1.2.1.39.1.8.1.5,RDBMS-MIB::rdbmsSrvLimitedResourceHighwater,INTEGER,read-only,,current,,The maximum value of the resource seen since applUpTime was reset.
.1.3.6.1.2.1.39.1.8.1.6,RDBMS-MIB::rdbmsSrvLimitedResourceFailures,Counter32,read-only,,current,,The number of times the system wanted to exceed the limit of the resource since applUpTime was reset.
.1.3.6.1.2.1.39.1.8.1.7,RDBMS-MIB::rdbmsSrvLimitedResourceDescription,OCTET,read-write,,current,,A description of the resource and the meaning of the integer units used for Limit, Current, and Highwater. Note that a compliant agent does not need to allow write access to this object.
.1.3.6.1.2.1.39.1.9,RDBMS-MIB::rdbmsRelTable,,not-accessible,,current,,A table relating databases and servers present on a host.
.1.3.6.1.2.1.39.1.9.1,RDBMS-MIB::rdbmsRelEntry,,not-accessible,rdbmsDbIndex:applIndex,current,,An entry relating a single database server to a single database to which it may provide access. The table is indexed first by the index of rdbmsDbTable, and then rdbmsSrvTable, so that all servers capable of providing access to a given database may be found by SNMP traversal operations (get-next and get-bulk). The makeup of this table depends on the product's architecture, e.g. if it is one server - many databases, then each server will appear n times, where n is the number of databases it may access, and each database will appear once. If the architecture is one database - many servers, then each server will appear once and each database will appear n times, where n is the number of servers that may be accessing it.
.1.3.6.1.2.1.39.1.9.1.1,RDBMS-MIB::rdbmsRelState,INTEGER,read-only,,current,other(1):active(2):available(3):restricted(4):unavailable(5),The state of this server's access to this database. Active(2) means the server is actively using the database. Available(3) means the server could use the database if necessary. Restricted(4) means the database is in some administratively determined state of less-than-complete availability. Unavailable(5) means the database is not available through this server. Other(1) means the database/server is in some other condition, possibly described in the vendor private MIB.
.1.3.6.1.2.1.39.1.9.1.2,RDBMS-MIB::rdbmsRelActiveTime,OCTET,read-only,,current,,The time the database was made active by the server. If an instance of rdbmsRelState is not active(1), then attempts to access the corresponding instance of this object may result in either noSuchName (SNMPv1) or noSuchInstance (SNMPv2) being returned by the agent.
.1.3.6.1.2.1.39.1.10,RDBMS-MIB::rdbmsWellKnownLimitedResources,,,,,,
.1.3.6.1.2.1.39.1.10.1,RDBMS-MIB::rdbmsLogSpace,,,,,,Storage allocated for redo and undo logs.
.1.3.6.1.2.1.39.2,RDBMS-MIB::rdbmsTraps,,,,,,
.1.3.6.1.2.1.39.2.1,RDBMS-MIB::rdbmsStateChange,,,,,,An rdbmsStateChange trap signifies that one of the database server/databases managed by this agent has changed its rdbmsRelState in a way that makes it less accessible for use. For these purposes, both active(2) and available(3) are considered fully accessible. The state sent with the trap is the new, less accessible state.
.1.3.6.1.2.1.39.2.2,RDBMS-MIB::rdbmsOutOfSpace,,,,,,An rdbmsOutOfSpace trap signifies that one of the database servers managed by this agent has been unable to allocate space for one of the databases managed by this agent. Care should be taken to avoid flooding the network with these traps.
.1.3.6.1.2.1.39.3,RDBMS-MIB::rdbmsConformance,,,,,,
.1.3.6.1.2.1.39.3.1,RDBMS-MIB::rdbmsCompliances,,,,,,
.1.3.6.1.2.1.39.3.1.1,RDBMS-MIB::rdbmsCompliance,,,,,,The compliance statement for SNMP entities which implement the RDBMS MIB
.1.3.6.1.2.1.39.3.2,RDBMS-MIB::rdbmsGroups,,,,,,
.1.3.6.1.2.1.39.3.2.1,RDBMS-MIB::rdbmsGroup,,,,,,A collection of objects providing basic instrumentation of an RDBMS entity.
.1.3.6.1.2.1.40,FLOW-METER-MIB::flowMIB,,,,,,MIB for the RTFM Traffic Flow Meter.
.1.3.6.1.2.1.40.1,FLOW-METER-MIB::flowControl,,,,,,
.1.3.6.1.2.1.40.1.1,FLOW-METER-MIB::flowRuleSetInfoTable,,not-accessible,,current,,An array of information about the RuleSets held in the meter. Any manager may configure a new RuleSet for the meter by creating a row in this table with status active(1), and setting values for all the objects in its rules. At this stage the new RuleSet is available but not 'running', i.e. it is not being used by the meter to produce entries in the flow table. To actually 'run' a RuleSet a manager must create a row in the flowManagerInfoTable, set it's flowManagerStatus to active(1), and set either its CurrentRuleSet or StandbyRuleSet to point to the RuleSet to be run. Once a RuleSet is running a manager may not change any of the objects within the RuleSet itself. Any attempt to do so should result in a notWritable(17) SNMP error-status for such objects. A manager may stop a RuleSet running by removing all references to it in the flowManagerInfoTable (i.e. by setting CurrentRuleSet and StandbyRuleSet values to 0). This provides a way to stop RuleSets left running if a manager fails. For example, when a manager is started, it could search the meter's flowManager table and stop all RuleSets having a specified value of flowRuleInfoOwner. To prevent a manager from interfering with variables belonging to another manager, the meter should use MIB views [RFC2575] so as to limit each manager's access to the meter's variables, effectively dividing the single meter into several virtual meters, one for each independent manager.
.1.3.6.1.2.1.40.1.1.1,FLOW-METER-MIB::flowRuleSetInfoEntry,,not-accessible,flowRuleInfoIndex,current,,Information about a particular RuleSet.
.1.3.6.1.2.1.40.1.1.1.1,FLOW-METER-MIB::flowRuleInfoIndex,Integer32,not-accessible,,current,,An index which selects an entry in the flowRuleSetInfoTable. Each such entry contains control information for a particular RuleSet which the meter may run.
.1.3.6.1.2.1.40.1.1.1.2,FLOW-METER-MIB::flowRuleInfoSize,Integer32,read-create,,current,,Number of rules in this RuleSet. Setting this variable will cause the meter to allocate space for these rules.
.1.3.6.1.2.1.40.1.1.1.3,FLOW-METER-MIB::flowRuleInfoOwner,OCTET,read-create,,current,,Identifies the manager which 'owns' this RuleSet. A manager must set this variable when creating a row in this table.
.1.3.6.1.2.1.40.1.1.1.4,FLOW-METER-MIB::flowRuleInfoTimeStamp,TimeTicks,read-only,,current,,Time this row's associated RuleSet was last changed.
.1.3.6.1.2.1.40.1.1.1.5,FLOW-METER-MIB::flowRuleInfoStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this flowRuleSetInfoEntry. If this value is not active(1) the meter must not attempt to use the row's associated RuleSet. Once its value has been set to active(1) a manager may not change any of the other variables in the row, nor the contents of the associated RuleSet. Any attempt to do so should result in a notWritable(17) SNMP error-status for such variables or objects. To download a RuleSet, a manger could: - Locate an open slot in the RuleSetInfoTable. - Create a RuleSetInfoEntry by setting the status for this open slot to createAndWait(5). - Set flowRuleInfoSize and flowRuleInfoName as required. - Download the rules into the row's rule table. - Set flowRuleInfoStatus to active(1). The RuleSet would then be ready to run. The manager is not allowed to change the value of flowRuleInfoStatus from active(1) if the associated RuleSet is being referenced by any of the entries in the flowManagerInfoTable. Setting RuleInfoStatus to destroy(6) destroys the associated RuleSet together with any flow data collected by it.
.1.3.6.1.2.1.40.1.1.1.6,FLOW-METER-MIB::flowRuleInfoName,OCTET,read-create,,current,,An alphanumeric identifier used by managers and readers to identify a RuleSet. For example, a manager wishing to run a RuleSet named WWW-FLOWS could search the flowRuleSetInfoTable to see whether the WWW-FLOWS RuleSet is already available on the meter. Note that references to RuleSets in the flowManagerInfoTable use indexes for their flowRuleSetInfoTable entries. These may be different each time the RuleSet is loaded into a meter.
.1.3.6.1.2.1.40.1.1.1.7,FLOW-METER-MIB::flowRuleInfoRulesReady,INTEGER,read-create,,deprecated,true(1):false(2),Indicates whether the rules for this row's associated RuleSet are ready for use. The meter will refuse to 'run' the RuleSet unless this variable has been set to true(1). While RulesReady is false(2), the manager may modify the RuleSet, for example by downloading rules into it.
.1.3.6.1.2.1.40.1.1.1.8,FLOW-METER-MIB::flowRuleInfoFlowRecords,Integer32,read-only,,current,,The number of entries in the flow table for this RuleSet. These may be current (waiting for collection by one or more meter readers) or idle (waiting for the meter to recover their memory).
.1.3.6.1.2.1.40.1.2,FLOW-METER-MIB::flowInterfaceTable,,not-accessible,,current,,An array of information specific to each meter interface.
.1.3.6.1.2.1.40.1.2.1,FLOW-METER-MIB::flowInterfaceEntry,,not-accessible,ifIndex,current,,Information about a particular interface.
.1.3.6.1.2.1.40.1.2.1.1,FLOW-METER-MIB::flowInterfaceSampleRate,Integer32,read-write,,current,,The parameter N for statistical counting on this interface. Set to N to count 1/Nth of the packets appearing at this interface. A sampling rate of 1 counts all packets. A sampling rate of 0 results in the interface being ignored by the meter. A meter should choose its own algorithm to introduce variance into the sampling so that exactly every Nth packet is counted. The IPPM Working Group's RFC 'Framework for IP Performance Metrics' [IPPM-FRM] explains why this should be done, and sets out an algorithm for doing it.
.1.3.6.1.2.1.40.1.2.1.2,FLOW-METER-MIB::flowInterfaceLostPackets,Counter32,read-only,,current,,The number of packets the meter has lost for this interface. Such losses may occur because the meter has been unable to keep up with the traffic volume.
.1.3.6.1.2.1.40.1.3,FLOW-METER-MIB::flowReaderInfoTable,,not-accessible,,current,,An array of information about meter readers which have registered their intent to collect flow data from this meter.
.1.3.6.1.2.1.40.1.3.1,FLOW-METER-MIB::flowReaderInfoEntry,,not-accessible,flowReaderIndex,current,,Information about a particular meter reader.
.1.3.6.1.2.1.40.1.3.1.1,FLOW-METER-MIB::flowReaderIndex,Integer32,not-accessible,,current,,An index which selects an entry in the flowReaderInfoTable.
.1.3.6.1.2.1.40.1.3.1.2,FLOW-METER-MIB::flowReaderTimeout,Integer32,read-create,,current,,Specifies the maximum time (in seconds) between flow data collections for this meter reader. If this time elapses without a collection, the meter should assume that this meter reader has stopped collecting, and delete this row from the table. A value of zero indicates that this row should not be timed out.
.1.3.6.1.2.1.40.1.3.1.3,FLOW-METER-MIB::flowReaderOwner,OCTET,read-create,,current,,Identifies the meter reader which created this row.
.1.3.6.1.2.1.40.1.3.1.4,FLOW-METER-MIB::flowReaderLastTime,TimeTicks,read-create,,current,,Time this meter reader began its most recent data collection. This variable should be written by a meter reader as its first step in reading flow data. The meter will set this LastTime value to its current Uptime, and set its PreviousTime value (below) to the old LastTime. This allows the meter to recover flows which have been inactive since PreviousTime, for these have been collected at least once. If the meter reader fails to write flowLastReadTime, collection may still proceed but the meter may not be able to recover inactive flows until the flowReaderTimeout has been reached for this entry.
.1.3.6.1.2.1.40.1.3.1.5,FLOW-METER-MIB::flowReaderPreviousTime,TimeTicks,read-only,,current,,Time this meter reader began the collection before last.
.1.3.6.1.2.1.40.1.3.1.6,FLOW-METER-MIB::flowReaderStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this FlowReaderInfoEntry. A value of active(1) implies that the associated reader should be collecting data from the meter. Once this variable has been set to active(1) a manager may only change this row's flowReaderLastTime and flowReaderTimeout variables.
.1.3.6.1.2.1.40.1.3.1.7,FLOW-METER-MIB::flowReaderRuleSet,Integer32,read-create,,current,,An index to the array of RuleSets. Specifies a set of rules of interest to this meter reader. The reader will attempt to collect any data generated by the meter for this RuleSet, and the meter will not recover the memory of any of the RuleSet's flows until this collection has taken place. Note that a reader may have entries in this table for several RuleSets.
.1.3.6.1.2.1.40.1.4,FLOW-METER-MIB::flowManagerInfoTable,,not-accessible,,current,,An array of information about managers which have registered their intent to run RuleSets on this meter.
.1.3.6.1.2.1.40.1.4.1,FLOW-METER-MIB::flowManagerInfoEntry,,not-accessible,flowManagerIndex,current,,Information about a particular meter 'task.' By creating an entry in this table and activating it, a manager requests that the meter 'run' the indicated RuleSet. The entry also specifies a HighWaterMark and a StandbyRuleSet. If the meter's flow table usage exceeds this task's HighWaterMark the meter will stop running the task's CurrentRuleSet and switch to its StandbyRuleSet. If the value of the task's StandbyRuleSet is 0 when its HighWaterMark is exceeded, the meter simply stops running the task's CurrentRuleSet. By careful selection of HighWaterMarks for the various tasks a manager can ensure that the most critical RuleSets are the last to stop running as the number of flows increases. When a manager has determined that the demand for flow table space has abated, it may cause the task to switch back to its CurrentRuleSet by setting its flowManagerRunningStandby variable to false(2).
.1.3.6.1.2.1.40.1.4.1.1,FLOW-METER-MIB::flowManagerIndex,Integer32,not-accessible,,current,,An index which selects an entry in the flowManagerInfoTable.
.1.3.6.1.2.1.40.1.4.1.2,FLOW-METER-MIB::flowManagerCurrentRuleSet,Integer32,read-create,,current,,Index to the array of RuleSets. Specifies which set of rules is the 'current' one for this task. The meter will be 'running' the current RuleSet if this row's flowManagerRunningStandby value is false(2). When the manager sets this variable the meter will stop using the task's old current RuleSet and start using the new one. Specifying RuleSet 0 (the empty set) stops flow measurement for this task.
.1.3.6.1.2.1.40.1.4.1.3,FLOW-METER-MIB::flowManagerStandbyRuleSet,Integer32,read-create,,current,,Index to the array of RuleSets. After reaching HighWaterMark (see below) the manager will switch to using the task's StandbyRuleSet in place of its CurrentRuleSet. For this to be effective the designated StandbyRuleSet should have a coarser reporting granularity then the CurrentRuleSet. The manager may also need to decrease the meter reading interval so that the meter can recover flows measured by this task's CurrentRuleSet.
.1.3.6.1.2.1.40.1.4.1.4,FLOW-METER-MIB::flowManagerHighWaterMark,Integer32,read-create,,current,,A value expressed as a percentage, interpreted by the meter as an indication of how full the flow table should be before it should switch to the standby RuleSet (if one has been specified) for this task. Values of 0% or 100% disable the checking represented by this variable.
.1.3.6.1.2.1.40.1.4.1.5,FLOW-METER-MIB::flowManagerCounterWrap,INTEGER,read-create,,deprecated,wrap(1):scale(2),Specifies whether PDU and octet counters should wrap when they reach the top of their range (normal behaviour for Counter64 objects), or whether their scale factors should be used instead. The combination of counter and scale factor allows counts to be returned as non-negative binary floating point numbers, with 64-bit mantissas and 8-bit exponents.
.1.3.6.1.2.1.40.1.4.1.6,FLOW-METER-MIB::flowManagerOwner,OCTET,read-create,,current,,Identifies the manager which created this row.
.1.3.6.1.2.1.40.1.4.1.7,FLOW-METER-MIB::flowManagerTimeStamp,TimeTicks,read-only,,current,,Time this row was last changed by its manager.
.1.3.6.1.2.1.40.1.4.1.8,FLOW-METER-MIB::flowManagerStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row in the flowManagerInfoTable. A value of active(1) implies that this task may be activated, by setting its CurrentRuleSet and StandbyRuleSet variables. Its HighWaterMark and RunningStandby variables may also be changed.
.1.3.6.1.2.1.40.1.4.1.9,FLOW-METER-MIB::flowManagerRunningStandby,INTEGER,read-create,,current,true(1):false(2),Set to true(1) by the meter to indicate that it has switched to runnning this task's StandbyRuleSet in place of its CurrentRuleSet. To switch back to the CurrentRuleSet, the manager may simply set this variable to false(2).
.1.3.6.1.2.1.40.1.5,FLOW-METER-MIB::flowFloodMark,Integer32,read-write,,current,,A value expressed as a percentage, interpreted by the meter as an indication of how full the flow table should be before it should take some action to avoid running out of resources to handle new flows, as discussed in section 4.6 (Handling Increasing Traffic Levels) of the RTFM Architecture RFC [RTFM-ARC]. Values of 0% or 100% disable the checking represented by this variable.
.1.3.6.1.2.1.40.1.6,FLOW-METER-MIB::flowInactivityTimeout,Integer32,read-write,,current,,The time in seconds since the last packet seen, after which a flow becomes 'idle.' Note that although a flow may be idle, it will not be discarded (and its memory recovered) until after its data has been collected by all the meter readers registered for its RuleSet.
.1.3.6.1.2.1.40.1.7,FLOW-METER-MIB::flowActiveFlows,Integer32,read-only,,current,,The number of flows which are currently in use.
.1.3.6.1.2.1.40.1.8,FLOW-METER-MIB::flowMaxFlows,Integer32,read-only,,current,,The maximum number of flows allowed in the meter's flow table. At present this is determined when the meter is first started up.
.1.3.6.1.2.1.40.1.9,FLOW-METER-MIB::flowFloodMode,INTEGER,read-write,,current,true(1):false(2),Indicates that the meter has passed its FloodMark and is not running in its normal mode. When the manager notices this it should take action to remedy the problem which caused the flooding. It should then monitor flowActiveFlows so as to determine when the flood has receded. At that point the manager may set flowFloodMode to false(2) to resume normal operation.
.1.3.6.1.2.1.40.2,FLOW-METER-MIB::flowData,,,,,,
.1.3.6.1.2.1.40.2.1,FLOW-METER-MIB::flowDataTable,,not-accessible,,current,,The list of all flows being measured.
.1.3.6.1.2.1.40.2.1.1,FLOW-METER-MIB::flowDataEntry,,not-accessible,flowDataRuleSet:flowDataTimeMark:flowDataIndex,current,,The flow data record for a particular flow.
.1.3.6.1.2.1.40.2.1.1.1,FLOW-METER-MIB::flowDataIndex,Integer32,not-accessible,,current,,Value of this flow data record's index within the meter's flow table.
.1.3.6.1.2.1.40.2.1.1.2,FLOW-METER-MIB::flowDataTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. Allows GetNext and GetBulk to find flow table rows which have changed since a specified value of the meter's Uptime.
.1.3.6.1.2.1.40.2.1.1.3,FLOW-METER-MIB::flowDataStatus,INTEGER,read-only,,deprecated,inactive(1),Status of this flow data record.
.1.3.6.1.2.1.40.2.1.1.4,FLOW-METER-MIB::flowDataSourceInterface,Integer32,read-only,,current,,Index of the interface associated with the source address for this flow. It's value is one of those contained in the ifIndex field of the meter's interfaces table.
.1.3.6.1.2.1.40.2.1.1.5,FLOW-METER-MIB::flowDataSourceAdjacentType,INTEGER,read-only,,current,ip(1):nsap(3):ethernet(7):tokenring(9):ipx(11):appletalk(12):decnet(13):fddi(15),Adjacent address type of the source for this flow. If metering is being performed at the network level, AdjacentType will indicate the medium for the interface on which the flow was observed and AdjacentAddress will be the MAC address for that interface. This is the usual case. If traffic is being metered inside a tunnel, AdjacentType will be the peer type of the host at the end of the tunnel and AdjacentAddress will be the peer address for that host.
.1.3.6.1.2.1.40.2.1.1.6,FLOW-METER-MIB::flowDataSourceAdjacentAddress,OCTET,read-only,,current,,Address of the adjacent device on the path for the source for this flow.
.1.3.6.1.2.1.40.2.1.1.7,FLOW-METER-MIB::flowDataSourceAdjacentMask,OCTET,read-only,,current,,1-bits in this mask indicate which bits must match when comparing the adjacent source address for this flow.
.1.3.6.1.2.1.40.2.1.1.8,FLOW-METER-MIB::flowDataSourcePeerType,INTEGER,read-only,,current,ipv4(1):ipv6(2):nsap(3):ipx(11):appletalk(12):decnet(13),Peer address type of the source for this flow.
.1.3.6.1.2.1.40.2.1.1.9,FLOW-METER-MIB::flowDataSourcePeerAddress,OCTET,read-only,,current,,Address of the peer device for the source of this flow.
.1.3.6.1.2.1.40.2.1.1.10,FLOW-METER-MIB::flowDataSourcePeerMask,OCTET,read-only,,current,,1-bits in this mask indicate which bits must match when comparing the source peer address for this flow.
.1.3.6.1.2.1.40.2.1.1.11,FLOW-METER-MIB::flowDataSourceTransType,Integer32,read-only,,current,,Transport address type of the source for this flow. The value of this attribute will depend on the peer address type.
.1.3.6.1.2.1.40.2.1.1.12,FLOW-METER-MIB::flowDataSourceTransAddress,OCTET,read-only,,current,,Transport address for the source of this flow.
.1.3.6.1.2.1.40.2.1.1.13,FLOW-METER-MIB::flowDataSourceTransMask,OCTET,read-only,,current,,1-bits in this mask indicate which bits must match when comparing the transport source address for this flow.
.1.3.6.1.2.1.40.2.1.1.14,FLOW-METER-MIB::flowDataDestInterface,Integer32,read-only,,current,,Index of the interface associated with the dest address for this flow. This value is one of the values contained in the ifIndex field of the interfaces table.
.1.3.6.1.2.1.40.2.1.1.15,FLOW-METER-MIB::flowDataDestAdjacentType,INTEGER,read-only,,current,ip(1):nsap(3):ethernet(7):tokenring(9):ipx(11):appletalk(12):decnet(13):fddi(15),Adjacent address type of the destination for this flow.
.1.3.6.1.2.1.40.2.1.1.16,FLOW-METER-MIB::flowDataDestAdjacentAddress,OCTET,read-only,,current,,Address of the adjacent device on the path for the destination for this flow.
.1.3.6.1.2.1.40.2.1.1.17,FLOW-METER-MIB::flowDataDestAdjacentMask,OCTET,read-only,,current,,1-bits in this mask indicate which bits must match when comparing the adjacent destination address for this flow.
.1.3.6.1.2.1.40.2.1.1.18,FLOW-METER-MIB::flowDataDestPeerType,INTEGER,read-only,,current,ipv4(1):ipv6(2):nsap(3):ipx(11):appletalk(12):decnet(13),Peer address type of the destination for this flow.
.1.3.6.1.2.1.40.2.1.1.19,FLOW-METER-MIB::flowDataDestPeerAddress,OCTET,read-only,,current,,Address of the peer device for the destination of this flow.
.1.3.6.1.2.1.40.2.1.1.20,FLOW-METER-MIB::flowDataDestPeerMask,OCTET,read-only,,current,,1-bits in this mask indicate which bits must match when comparing the destination peer type for this flow.
.1.3.6.1.2.1.40.2.1.1.21,FLOW-METER-MIB::flowDataDestTransType,Integer32,read-only,,current,,Transport address type of the destination for this flow. The value of this attribute will depend on the peer address type.
.1.3.6.1.2.1.40.2.1.1.22,FLOW-METER-MIB::flowDataDestTransAddress,OCTET,read-only,,current,,Transport address for the destination of this flow.
.1.3.6.1.2.1.40.2.1.1.23,FLOW-METER-MIB::flowDataDestTransMask,OCTET,read-only,,current,,1-bits in this mask indicate which bits must match when comparing the transport destination address for this flow.
.1.3.6.1.2.1.40.2.1.1.24,FLOW-METER-MIB::flowDataPDUScale,Integer32,read-only,,current,,The scale factor applied to this particular flow. Indicates the number of bits the PDU counter values should be moved left to obtain the actual values.
.1.3.6.1.2.1.40.2.1.1.25,FLOW-METER-MIB::flowDataOctetScale,Integer32,read-only,,current,,The scale factor applied to this particular flow. Indicates the number of bits the octet counter values should be moved left to obtain the actual values.
.1.3.6.1.2.1.40.2.1.1.26,FLOW-METER-MIB::flowDataRuleSet,Integer32,not-accessible,,current,,The RuleSet number of the RuleSet which created this flow. Allows a manager to use GetNext or GetBulk requests to find flows belonging to a particular RuleSet.
.1.3.6.1.2.1.40.2.1.1.27,FLOW-METER-MIB::flowDataToOctets,Counter64,read-only,,current,,The count of octets flowing from source to destination for this flow.
.1.3.6.1.2.1.40.2.1.1.28,FLOW-METER-MIB::flowDataToPDUs,Counter64,read-only,,current,,The count of packets flowing from source to destination for this flow.
.1.3.6.1.2.1.40.2.1.1.29,FLOW-METER-MIB::flowDataFromOctets,Counter64,read-only,,current,,The count of octets flowing from destination to source for this flow.
.1.3.6.1.2.1.40.2.1.1.30,FLOW-METER-MIB::flowDataFromPDUs,Counter64,read-only,,current,,The count of packets flowing from destination to source for this flow.
.1.3.6.1.2.1.40.2.1.1.31,FLOW-METER-MIB::flowDataFirstTime,TimeTicks,read-only,,current,,The time at which this flow was first entered in the table
.1.3.6.1.2.1.40.2.1.1.32,FLOW-METER-MIB::flowDataLastActiveTime,TimeTicks,read-only,,current,,The last time this flow had activity, i.e. the time of arrival of the most recent PDU belonging to this flow.
.1.3.6.1.2.1.40.2.1.1.33,FLOW-METER-MIB::flowDataSourceSubscriberID,OCTET,read-only,,current,,Subscriber ID associated with the source address for this flow. A Subscriber ID is an unspecified text string, used to ascribe traffic flows to individual users. At this time the means by which a Subscriber ID may be associated with a flow is unspecified.
.1.3.6.1.2.1.40.2.1.1.34,FLOW-METER-MIB::flowDataDestSubscriberID,OCTET,read-only,,current,,Subscriber ID associated with the destination address for this flow. A Subscriber ID is an unspecified text string, used to ascribe traffic flows to individual users. At this time the means by which a Subscriber ID may be associated with a flow is unspecified.
.1.3.6.1.2.1.40.2.1.1.35,FLOW-METER-MIB::flowDataSessionID,OCTET,read-only,,current,,Session ID for this flow. Such an ID might be allocated by a network access server to distinguish a series of sessions between the same pair of addresses, which would otherwise appear to be parts of the same accounting flow.
.1.3.6.1.2.1.40.2.1.1.36,FLOW-METER-MIB::flowDataSourceClass,Integer32,read-only,,current,,Source class for this flow. Determined by the rules, set by a PushRule action when this flow was entered in the table.
.1.3.6.1.2.1.40.2.1.1.37,FLOW-METER-MIB::flowDataDestClass,Integer32,read-only,,current,,Destination class for this flow. Determined by the rules, set by a PushRule action when this flow was entered in the table.
.1.3.6.1.2.1.40.2.1.1.38,FLOW-METER-MIB::flowDataClass,Integer32,read-only,,current,,Class for this flow. Determined by the rules, set by a PushRule action when this flow was entered in the table.
.1.3.6.1.2.1.40.2.1.1.39,FLOW-METER-MIB::flowDataSourceKind,Integer32,read-only,,current,,Source kind for this flow. Determined by the rules, set by a PushRule action when this flow was entered in the table.
.1.3.6.1.2.1.40.2.1.1.40,FLOW-METER-MIB::flowDataDestKind,Integer32,read-only,,current,,Destination kind for this flow. Determined by the rules, set by a PushRule action when this flow was entered in the table.
.1.3.6.1.2.1.40.2.1.1.41,FLOW-METER-MIB::flowDataKind,Integer32,read-only,,current,,Class for this flow. Determined by the rules, set by a PushRule action when this flow was entered in the table.
.1.3.6.1.2.1.40.2.2,FLOW-METER-MIB::flowColumnActivityTable,,not-accessible,,deprecated,,Index into the Flow Table. Allows a meter reader to retrieve a list containing the flow table indexes of flows which were last active at or after a given time, together with the values of a specified attribute for each such flow.
.1.3.6.1.2.1.40.2.2.1,FLOW-METER-MIB::flowColumnActivityEntry,,not-accessible,flowColumnActivityAttribute:flowColumnActivityTime:flowColumnActivityIndex,deprecated,,The Column Activity Entry for a particular attribute, activity time and flow.
.1.3.6.1.2.1.40.2.2.1.1,FLOW-METER-MIB::flowColumnActivityAttribute,INTEGER,read-only,,deprecated,flowIndex(1):flowStatus(2):flowTimeMark(3):sourceInterface(4):sourceAdjacentType(5):sourceAdjacentAddress(6):sourceAdjacentMask(7):sourcePeerType(8):sourcePeerAddress(9):sourcePeerMask(10):sourceTransType(11):sourceTransAddress(12):sourceTransMask(13):destInterface(14):destAdjacentType(15):destAdjacentAddress(16):destAdjacentMask(17):destPeerType(18):destPeerAddress(19):destPeerMask(20):destTransType(21):destTransAddress(22):destTransMask(23):pduScale(24):octetScale(25):ruleSet(26):toOctets(27):toPDUs(28):fromOctets(29):fromPDUs(30):firstTime(31):lastActiveTime(32):sourceSubscriberID(33):destSubscriberID(34):sessionID(35):sourceClass(36):destClass(37):flowClass(38):sourceKind(39):destKind(40):flowKind(41),Specifies the attribute for which values are required from active flows.
.1.3.6.1.2.1.40.2.2.1.2,FLOW-METER-MIB::flowColumnActivityTime,TimeTicks,read-only,,deprecated,,This variable is a copy of flowDataLastActiveTime in the flow data record identified by the flowColumnActivityIndex value of this flowColumnActivityTable entry.
.1.3.6.1.2.1.40.2.2.1.3,FLOW-METER-MIB::flowColumnActivityIndex,Integer32,read-only,,deprecated,,Index of a flow table entry which was active at or after a specified flowColumnActivityTime.
.1.3.6.1.2.1.40.2.2.1.4,FLOW-METER-MIB::flowColumnActivityData,OCTET,read-only,,deprecated,,Collection of attribute data for flows active after flowColumnActivityTime. Within the OCTET STRING is a sequence of { flow index, attribute value } pairs, one for each active flow. The end of the sequence is marked by a flow index value of 0, indicating that there are no more rows in this column. The format of objects inside flowColumnFlowData is as follows. All numbers are unsigned. Numbers and strings appear with their high-order bytes leading. Numbers are fixed size, as specified by their SYNTAX in the flow table (above), i.e. one octet for flowAddressType and small constants, and four octets for Counter and TimeStamp. Strings are variable-length, with the length given in a single leading octet. The following is an attempt at an ASN.1 definition of flowColumnActivityData: flowColumnActivityData ::= SEQUENCE flowRowItemEntry flowRowItemEntry ::= SEQUENCE { flowRowNumber Integer32 (1..65535), -- 0 indicates the end of this column flowDataValue flowDataType -- Choice depends on attribute } flowDataType ::= CHOICE { flowByteValue Integer32 (1..255), flowShortValue Integer32 (1..65535), flowLongValue Integer32, flowStringValue OCTET STRING -- Length (n) in first byte, -- n+1 bytes total length, trailing zeroes truncated }
.1.3.6.1.2.1.40.2.3,FLOW-METER-MIB::flowDataPackageTable,,not-accessible,,current,,Index into the Flow Table. Allows a meter reader to retrieve a sequence containing the values of a specified set of attributes for a flow which came from a specified RuleSet and which was last active at or after a given time.
.1.3.6.1.2.1.40.2.3.1,FLOW-METER-MIB::flowDataPackageEntry,,not-accessible,flowPackageSelector:flowPackageRuleSet:flowPackageTime:flowPackageIndex,current,,The data package containing selected variables from active rows in the flow table.
.1.3.6.1.2.1.40.2.3.1.1,FLOW-METER-MIB::flowPackageSelector,OCTET,not-accessible,,current,,Specifies the attributes for which values are required from an active flow. These are encoded as a sequence of octets each containing a FlowAttribute number, preceded by an octet giving the length of the sequence (not including the length octet). For a flowPackageSelector to be valid, it must contain at least one attribute.
.1.3.6.1.2.1.40.2.3.1.2,FLOW-METER-MIB::flowPackageRuleSet,Integer32,not-accessible,,current,,Specifies the index (in the flowRuleSetInfoTable) of the rule set which produced the required flow.
.1.3.6.1.2.1.40.2.3.1.3,FLOW-METER-MIB::flowPackageTime,TimeTicks,not-accessible,,current,,This variable is a copy of flowDataLastActiveTime in the flow data record identified by the flowPackageIndex value of this flowPackageTable entry.
.1.3.6.1.2.1.40.2.3.1.4,FLOW-METER-MIB::flowPackageIndex,Integer32,not-accessible,,current,,Index of a flow table entry which was active at or after a specified flowPackageTime.
.1.3.6.1.2.1.40.2.3.1.5,FLOW-METER-MIB::flowPackageData,OCTET,read-only,,current,,A collection of attribute values for a single flow, as specified by this row's indexes. The attribute values are contained within a BER-encoded sequence [ASN-1, ASN-BER], in the order they appear in their flowPackageSelector. For example, to retrieve a flowPackage containing values for attributes 11, 18 and 29, for a flow in RuleSet 7, with flow index 3447, one would GET the package whose Object Identifier (OID) is flowPackageData . 3.11.18.29 . 7. 0 . 3447 To get a package for the next such flow which had been active since time 12345 one would GETNEXT the package whose Object Identifier (OID) is flowPackageData . 3.11.18.29 . 7. 12345 . 3447
.1.3.6.1.2.1.40.3,FLOW-METER-MIB::flowRules,,,,,,
.1.3.6.1.2.1.40.3.1,FLOW-METER-MIB::flowRuleTable,,not-accessible,,current,,Contains all the RuleSets which may be used by the meter.
.1.3.6.1.2.1.40.3.1.1,FLOW-METER-MIB::flowRuleEntry,,not-accessible,flowRuleSet:flowRuleIndex,current,,The rule record itself.
.1.3.6.1.2.1.40.3.1.1.1,FLOW-METER-MIB::flowRuleSet,Integer32,not-accessible,,current,,Selects a RuleSet from the array of RuleSets.
.1.3.6.1.2.1.40.3.1.1.2,FLOW-METER-MIB::flowRuleIndex,Integer32,not-accessible,,current,,The index into the Rule table. N.B: These values will normally be consecutive, given the fall-through semantics of processing the table.
.1.3.6.1.2.1.40.3.1.1.3,FLOW-METER-MIB::flowRuleSelector,INTEGER,read-write,,current,null(0):sourceInterface(4):sourceAdjacentType(5):sourceAdjacentAddress(6):sourcePeerType(8):sourcePeerAddress(9):sourceTransType(11):sourceTransAddress(12):destInterface(14):destAdjacentType(15):destAdjacentAddress(16):destPeerType(18):destPeerAddress(19):destTransType(21):destTransAddress(22):sourceSubscriberID(33):destSubscriberID(34):sessionID(35):sourceClass(36):destClass(37):flowClass(38):sourceKind(39):destKind(40):flowKind(41):matchingStoD(50):v1(51):v2(52):v3(53):v4(54):v5(55),Indicates the attribute to be matched. null(0) is a special case; null rules always succeed. matchingStoD(50) is set by the meter's Packet Matching Engine. Its value is true(1) if the PME is attempting to match the packet with its addresses in Source-to-Destination order (i.e. as they appear in the packet), and false(2) otherwise. Details of how packets are matched are given in the 'Traffic Flow Measurement: Architecture' document [RTFM-ARC]. v1(51), v2(52), v3(53), v4(54) and v5(55) select meter variables, each of which can hold the name (i.e. selector value) of an address attribute. When one of these is used as a selector, its value specifies the attribute to be tested. Variable values are set by an Assign action.
.1.3.6.1.2.1.40.3.1.1.4,FLOW-METER-MIB::flowRuleMask,OCTET,read-write,,current,,The initial mask used to compute the desired value. If the mask is zero the rule's test will always succeed.
.1.3.6.1.2.1.40.3.1.1.5,FLOW-METER-MIB::flowRuleMatchedValue,OCTET,read-write,,current,,The resulting value to be matched for equality. Specifically, if the attribute chosen by the flowRuleSelector logically ANDed with the mask specified by the flowRuleMask equals the value specified in the flowRuleMatchedValue, then continue processing the table entry based on the action specified by the flowRuleAction entry. Otherwise, proceed to the next entry in the rule table.
.1.3.6.1.2.1.40.3.1.1.6,FLOW-METER-MIB::flowRuleAction,INTEGER,read-write,,current,ignore(1):noMatch(2):count(3):countPkt(4):return(5):gosub(6):gosubAct(7):assign(8):assignAct(9):goto(10):gotoAct(11):pushRuleTo(12):pushRuleToAct(13):pushPktTo(14):pushPktToAct(15):popTo(16):popToAct(17),The action to be taken if this rule's test succeeds, or if the meter's 'test' flag is off. Actions are opcodes for the meter's Packet Matching Engine; details are given in the 'Traffic Flow Measurement: Architecture' document [RTFM-ARC].
.1.3.6.1.2.1.40.3.1.1.7,FLOW-METER-MIB::flowRuleParameter,Integer32,read-write,,current,,A parameter value providing extra information for this rule's action. Most of the actions use the parameter value to specify which rule to execute after this rule's test has failed; details are given in the 'Traffic Flow Measurement: Architecture' document [RTFM-ARC].
.1.3.6.1.2.1.40.4,FLOW-METER-MIB::flowMIBConformance,,,,,,
.1.3.6.1.2.1.40.4.1,FLOW-METER-MIB::flowMIBCompliances,,,,,,
.1.3.6.1.2.1.40.4.1.1,FLOW-METER-MIB::flowMIBCompliance,,,,,,The compliance statement for a Traffic Flow Meter.
.1.3.6.1.2.1.40.4.2,FLOW-METER-MIB::flowMIBGroups,,,,,,
.1.3.6.1.2.1.40.4.2.1,FLOW-METER-MIB::flowControlGroup,,,,,,The control group defines objects which are used to control an accounting meter.
.1.3.6.1.2.1.40.4.2.2,FLOW-METER-MIB::flowDataTableGroup,,,,,,The flow table group defines objects which provide the structure for the flow table, including the creation time and activity time indexes into it. In addition it defines objects which provide a base set of flow attributes for the adjacent, peer and transport layers, together with a flow's counters and times. Finally it defines a flow's class and kind attributes, which are set by rule actions.
.1.3.6.1.2.1.40.4.2.3,FLOW-METER-MIB::flowDataScaleGroup,,,,,,The flow scale group defines objects which specify scale factors for counters.
.1.3.6.1.2.1.40.4.2.4,FLOW-METER-MIB::flowDataSubscriberGroup,,,,,,The flow subscriber group defines objects which may be used to identify the end point(s) of a flow.
.1.3.6.1.2.1.40.4.2.5,FLOW-METER-MIB::flowDataColumnTableGroup,,,,,,The flow column table group defines objects which can be used to collect part of a column of attribute values from the flow table.
.1.3.6.1.2.1.40.4.2.6,FLOW-METER-MIB::flowDataPackageGroup,,,,,,The data package group defines objects which can be used to collect a specified set of attribute values from a row of the flow table.
.1.3.6.1.2.1.40.4.2.7,FLOW-METER-MIB::flowRuleTableGroup,,,,,,The rule table group defines objects which hold the set(s) of rules specifying which traffic flows are to be accounted for.
.1.3.6.1.2.1.40.4.2.8,FLOW-METER-MIB::flowDataScaleGroup2,,,,,,The flow scale group defines objects which specify scale factors for counters. This group replaces the earlier version of flowDataScaleGroup above (now deprecated).
.1.3.6.1.2.1.40.4.2.9,FLOW-METER-MIB::flowControlGroup2,,,,,,The control group defines objects which are used to control an accounting meter. It replaces the earlier version of flowControlGroup above (now deprecated).
.1.3.6.1.2.1.41,SNA-SDLC-MIB::snaDLC,,,,,,This is the MIB module for objects used to manage SDLC devices.
.1.3.6.1.2.1.41.1,SNA-SDLC-MIB::sdlc,,,,,,
.1.3.6.1.2.1.41.1.1,SNA-SDLC-MIB::sdlcPortGroup,,,,,,
.1.3.6.1.2.1.41.1.1.1,SNA-SDLC-MIB::sdlcPortAdminTable,,not-accessible,,current,,This table contains objects that can be changed to manage an SDLC port. Changing one of these parameters may take effect in the operating port immediately or may wait until the interface is restarted depending on the details of the implementation. Most of the objects in this read-write table have corresponding read-only objects in the sdlcPortOperTable that return the current operating value. The operating values may be different from these configured values if a configured parameter was changed after the interface was started.
.1.3.6.1.2.1.41.1.1.1.1,SNA-SDLC-MIB::sdlcPortAdminEntry,,not-accessible,ifIndex,current,,A list of configured values for an SDLC port.
.1.3.6.1.2.1.41.1.1.1.1.1,SNA-SDLC-MIB::sdlcPortAdminName,OCTET,read-write,,current,,An octet string that defines the physical port to which this interface is assigned. It has implementation-specific significance. Its value shall be unique within the administered system. It must contain only ASCII printable characters. Should an implementation choose to accept a write operation for this object, it causes the logical port definition associated with the table instance to be moved to a different physical port. A write operation shall not take effect until the port is cycled inactive.
.1.3.6.1.2.1.41.1.1.1.1.2,SNA-SDLC-MIB::sdlcPortAdminRole,INTEGER,read-write,,current,primary(1):secondary(2):negotiable(3),This object describes the role that the link station shall assume the next time a connection is established. Even though this is defined as a port object, it is a link station attribute in the sense that a role is per link station. However, it is not possible to vary link station roles on a particular port. For example, if an SDLC port is configured to primary, all link stations on that port must be primary.
.1.3.6.1.2.1.41.1.1.1.1.3,SNA-SDLC-MIB::sdlcPortAdminType,INTEGER,read-write,,current,leased(1):switched(2),This parameter defines whether the SDLC port is to connect to a leased or switched line. A write operation to this administrative value shall not take effect until the SDLC port has been cycled inactive.
.1.3.6.1.2.1.41.1.1.1.1.4,SNA-SDLC-MIB::sdlcPortAdminTopology,INTEGER,read-write,,current,pointToPoint(1):multipoint(2),This parameter defines whether the SDLC port is capable of operating in either a point-to-point or multipoint topology. sdlcPortAdminTopology == multipoint implies the port can also operate in a point-to-point topology. sdlcPortAdminTopology == pointToPoint does not imply the port can operate in a multipoint topology. A write operation to this administrative value shall not take effect until the SDLC port has been cycled inactive.
.1.3.6.1.2.1.41.1.1.1.1.5,SNA-SDLC-MIB::sdlcPortAdminISTATUS,INTEGER,read-write,,current,inactive(1):active(2),This parameter controls the initial value of the administrative status, ifAdminStatus, of this SDLC port at port start-up. Depending on the implementation, a write operation to this administrative object may not take effect until the SDLC port has been cycled inactive.
.1.3.6.1.2.1.41.1.1.1.1.6,SNA-SDLC-MIB::sdlcPortAdminACTIVTO,INTEGER,read-write,,current,,This parameter defines the period of time (in 1/100ths of a second) that the port will allow a switched line to remain inactive before disconnecting. A switched line is considered to be inactive if there are no I-Frames being transferred. A value of zero indicates no timeout. Depending on the implementation, a write operation to this administered value may not take effect until the port is cycled inactive. This object only has meaning for SDLC ports where sdlcPortAdminType == switched The object descriptor contains the name of an NCP configuration parameter, ACTIVTO. Please note that the value of this object represents 1/100ths of a second while the NCP ACTIVTO is represented in seconds.
.1.3.6.1.2.1.41.1.1.1.1.7,SNA-SDLC-MIB::sdlcPortAdminPAUSE,INTEGER,read-write,,current,,This object defines the minimum elapsed time (in 1/100ths of a second) between any two traversals of the poll list for a primary SDLC port. Depending on the implementation, a write operation to this administered value may not take effect until the port is cycled inactive. The object descriptor contains the name of an NCP configuration parameter, PAUSE. Please note that the value of this object represents 1/100ths of a second while the NCP PAUSE is represented in 1/10ths of a second. This object only has meaning for SDLC ports where sdlcPortAdminRole == primary 
.1.3.6.1.2.1.41.1.1.1.1.8,SNA-SDLC-MIB::sdlcPortAdminSERVLIM,Integer32,read-write,,current,,This object defines the number of times the active poll list will be traversed before polling a station on the slow poll list for a primary, multipoint SDLC port. Depending on the implementation, a write operation to this administered value may not take effect until the port is cycled inactive. This object only has meaning for SDLC ports where sdlcPortAdminRole == primary and sdlcPortAdminTopology == multipoint 
.1.3.6.1.2.1.41.1.1.1.1.9,SNA-SDLC-MIB::sdlcPortAdminSlowPollTimer,INTEGER,read-write,,current,,This object describes the elapsed time (in 1/100ths of a second) between polls for failed secondary link station addresses. Depending on the implementation, a write operation to this administered value may not take effect until the port is cycled inactive. This object only has meaning for SDLC ports where sdlcPortAdminRole == primary and sdlcPortAdminTopology == multipoint 
.1.3.6.1.2.1.41.1.1.2,SNA-SDLC-MIB::sdlcPortOperTable,,not-accessible,,current,,This table contains current SDLC port parameters. Many of these objects have corresponding objects inthe sdlcPortAdminTable.
.1.3.6.1.2.1.41.1.1.2.1,SNA-SDLC-MIB::sdlcPortOperEntry,,not-accessible,ifIndex,current,,Currently set parameters for a specific SDLC port.
.1.3.6.1.2.1.41.1.1.2.1.1,SNA-SDLC-MIB::sdlcPortOperName,OCTET,read-only,,current,,An octet string that describes the physical port to which this interface is currently attached. It has implementation-specific significance.
.1.3.6.1.2.1.41.1.1.2.1.2,SNA-SDLC-MIB::sdlcPortOperRole,INTEGER,read-only,,current,primary(1):secondary(2):undefined(3),This object describes the role that the link station has assumed on this connection. Even though this is defined as a port object, it is a link station attribute in the sense that a role is per link station. However, it is not possible to vary link station roles on a particular port. For example, if an SDLC port is configured to primary, all link stations on that port must be primary. The value of sdlcPortOperRole is undefined(3) whenever the link station role has not yet been established by the mode setting command.
.1.3.6.1.2.1.41.1.1.2.1.3,SNA-SDLC-MIB::sdlcPortOperType,INTEGER,read-only,,current,leased(1):switched(2),This parameter defines whether the SDLC port is currently operating as though connected to a leased or switched line.
.1.3.6.1.2.1.41.1.1.2.1.4,SNA-SDLC-MIB::sdlcPortOperTopology,INTEGER,read-only,,current,pointToPoint(1):multipoint(2),This parameter defines whether the SDLC port is currently operating in a point-to-point or multipoint topology.
.1.3.6.1.2.1.41.1.1.2.1.5,SNA-SDLC-MIB::sdlcPortOperISTATUS,INTEGER,read-only,,current,inactive(1):active(2),This parameter describes the initial value of the administrative status, ifAdminStatus, of this SDLC port at last port start-up.
.1.3.6.1.2.1.41.1.1.2.1.6,SNA-SDLC-MIB::sdlcPortOperACTIVTO,INTEGER,read-only,,current,,This parameter defines the period of time (in 100ths of a second) that the port will allow a switched line to remain inactive before disconnecting. A switched line is considered to be inactive if there are no I-Frames being transferred. The object descriptor contains the name of an NCP configuration parameter, ACTIVTO. Please note that the value of this object represents 1/100ths of a second while the NCP ACTIVTO is represented in seconds. A value of zero indicates no timeout.
.1.3.6.1.2.1.41.1.1.2.1.7,SNA-SDLC-MIB::sdlcPortOperPAUSE,INTEGER,read-only,,current,,This object describes the current minimum elapsed time (in 1/100ths of a second) between any two traversals of the poll list for a primary SDLC port. The object descriptor contains the name of an NCP configuration parameter, PAUSE. Please note that the value of this object represents 1/100ths of a second while the NCP PAUSE is represented in 1/10ths of a second. This object only has meaning for SDLC ports where sdlcPortAdminRole == primary 
.1.3.6.1.2.1.41.1.1.2.1.8,SNA-SDLC-MIB::sdlcPortOperSlowPollMethod,INTEGER,read-only,,current,servlim(1):pollpause(2):other(3),This object defines the exact method that is in effect for periodically polling failed secondary link station addresses. If sdlcPortOperSlowPollMethod == servlim, then sdlcPortOperSERVLIM defines the actual polling characteristics. If sdlcPortOperSlowPollMethod == pollpause, then sdlcPortOperSlowPollTimer defines the actual polling characteristics. If sdlcPortOperSlowPollMethod == other, then the polling characteristics are modeled in vendor-specific objects. This object only has meaning for SDLC ports where sdlcPortOperRole == primary and sdlcPortOperTopology == multipoint 
.1.3.6.1.2.1.41.1.1.2.1.9,SNA-SDLC-MIB::sdlcPortOperSERVLIM,Integer32,read-only,,current,,This object describes the number of times the active poll list is currently being traversed before polling a station on the slow poll list for a primary, multipoint SDLC port. This object only has meaning for SDLC ports where sdlcPortOperRole == primary and sdlcPortOperTopology == multipoint 
.1.3.6.1.2.1.41.1.1.2.1.10,SNA-SDLC-MIB::sdlcPortOperSlowPollTimer,INTEGER,read-only,,current,,This object describes the elapsed time (in 1/100ths of a second) between polls for failed secondary link station addresses. This object only has meaning for SDLC ports where sdlcPortOperRole == primary and sdlcPortOperTopology == multipoint 
.1.3.6.1.2.1.41.1.1.2.1.11,SNA-SDLC-MIB::sdlcPortOperLastModifyTime,TimeTicks,read-only,,current,,This object describes the value of sysUpTime when this port definition was last modified. If the port has not been modified, then this value shall be zero.
.1.3.6.1.2.1.41.1.1.2.1.12,SNA-SDLC-MIB::sdlcPortOperLastFailTime,TimeTicks,read-only,,current,,This object describes the value of sysUpTime when this SDLC port last failed. If the port has not failed, then this value shall be zero.
.1.3.6.1.2.1.41.1.1.2.1.13,SNA-SDLC-MIB::sdlcPortOperLastFailCause,INTEGER,read-only,,current,undefined(1):physical(2),This enumerated object describes the cause of the last failure of this SDLC port. If the port has not failed, then this object has a value of undefined(1).
.1.3.6.1.2.1.41.1.1.3,SNA-SDLC-MIB::sdlcPortStatsTable,,not-accessible,,current,,Each entry in this table contains statistics for a specific SDLC port.
.1.3.6.1.2.1.41.1.1.3.1,SNA-SDLC-MIB::sdlcPortStatsEntry,,not-accessible,ifIndex,current,,A list of statistics for an SDLC port.
.1.3.6.1.2.1.41.1.1.3.1.1,SNA-SDLC-MIB::sdlcPortStatsPhysicalFailures,Counter32,read-only,,current,,This object reflects the total number of times this port has failed due to its physical media since port startup. At port startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.1.3.1.2,SNA-SDLC-MIB::sdlcPortStatsInvalidAddresses,Counter32,read-only,,current,,This object reflects the total number of frames received by this port with invalid link station addresses.
.1.3.6.1.2.1.41.1.1.3.1.3,SNA-SDLC-MIB::sdlcPortStatsDwarfFrames,Counter32,read-only,,current,,This object reflects the total number of frames received by this port which were delivered intact by the physical layer but were too short to be legal. Ignoring the frame check sequence (FCS), a frame is considered to be too short if it is less than 2 bytes for sdlcLSOperMODULO of eight, or if it is less than 3 bytes for sdlcLSOperMODULO of onetwentyeight.
.1.3.6.1.2.1.41.1.1.3.1.4,SNA-SDLC-MIB::sdlcPortStatsPollsIn,Counter32,read-only,,current,,This object reflects the total number of polls received by this port since the port was created.
.1.3.6.1.2.1.41.1.1.3.1.5,SNA-SDLC-MIB::sdlcPortStatsPollsOut,Counter32,read-only,,current,,This object reflects the total number of polls sent by this port since the port was created.
.1.3.6.1.2.1.41.1.1.3.1.6,SNA-SDLC-MIB::sdlcPortStatsPollRspsIn,Counter32,read-only,,current,,This object reflects the total number of poll responses received by this port since the port was created.
.1.3.6.1.2.1.41.1.1.3.1.7,SNA-SDLC-MIB::sdlcPortStatsPollRspsOut,Counter32,read-only,,current,,This object reflects the total number of poll responses sent by this port since the port was created.
.1.3.6.1.2.1.41.1.1.3.1.8,SNA-SDLC-MIB::sdlcPortStatsLocalBusies,Counter32,read-only,,current,,This object reflects the total number of times that the local SDLC link stations on this port have entered a busy state (RNR). This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.9,SNA-SDLC-MIB::sdlcPortStatsRemoteBusies,Counter32,read-only,,current,,This object reflects the total number of times that the adjacent (i.e., remote) SDLC link stations on this port have entered a busy state (RNR). This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.10,SNA-SDLC-MIB::sdlcPortStatsIFramesIn,Counter32,read-only,,current,,This object reflects the total number of I-Frames that have been received by SDLC link stations on this port. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.11,SNA-SDLC-MIB::sdlcPortStatsIFramesOut,Counter32,read-only,,current,,This object reflects the total number of I-Frames that have been transmitted by SDLC link stations on this port. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.12,SNA-SDLC-MIB::sdlcPortStatsOctetsIn,Counter32,read-only,,current,,This object reflects the total octets received from adjacent SDLC link stations on this port. This object covers the address, control, and information field of I-Frames only. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.13,SNA-SDLC-MIB::sdlcPortStatsOctetsOut,Counter32,read-only,,current,,This object reflects the total octets transmitted to adjacent SDLC link stations on this port. This object covers the address, control, and information field of I-Frames only. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.14,SNA-SDLC-MIB::sdlcPortStatsProtocolErrs,Counter32,read-only,,current,,This object reflects the total number of times that the SDLC link stations on this port have deactivated the link as a result of having received a protocol violation from the adjacent link station. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.15,SNA-SDLC-MIB::sdlcPortStatsActivityTOs,Counter32,read-only,,current,,This object reflects the total number of times that the SDLC link stations on this port have deactivated the link as a result of no activity on the link. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.16,SNA-SDLC-MIB::sdlcPortStatsRNRLIMITs,Counter32,read-only,,current,,This object reflects the total number of times that the SDLC link stations on this port have deactivated the link as a result of its RNRLIMIT timer expiring. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.17,SNA-SDLC-MIB::sdlcPortStatsRetriesExps,Counter32,read-only,,current,,This object reflects the total number of times that the SDLC link stations on this port have deactivated the link as a result of a retry sequence being exhausted. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.18,SNA-SDLC-MIB::sdlcPortStatsRetransmitsIn,Counter32,read-only,,current,,This object reflects the total number of I-Frames retransmitted by remote link stations for all SDLC link stations on this port. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.1.3.1.19,SNA-SDLC-MIB::sdlcPortStatsRetransmitsOut,Counter32,read-only,,current,,This object reflects the total number of I-Frames retransmitted by all local SDLC link stations on this port. This object is initialized to zero when the port is created.
.1.3.6.1.2.1.41.1.2,SNA-SDLC-MIB::sdlcLSGroup,,,,,,
.1.3.6.1.2.1.41.1.2.1,SNA-SDLC-MIB::sdlcLSAdminTable,,not-accessible,,current,,This table contains objects that can be changed to manage an SDLC link station. Changing one of these parameters may take effect in the operating link immediately or may wait until the link is restarted depending on the details of the implementation. The entries in sdlcLSAdminTable can be created either by an agent or a management station. The management station can create an entry in sdlcLSAdminTable by setting the appropriate value in sdlcLSAdminRowStatus. Most of the objects in this read-create table have corresponding read-only objects in the sdlcLSOperTable that reflect the current operating value. The operating values may be different from these configured values if changed by XID negotiation or if a configured parameter was changed after the link was started.
.1.3.6.1.2.1.41.1.2.1.1,SNA-SDLC-MIB::sdlcLSAdminEntry,,not-accessible,ifIndex:sdlcLSAddress,current,,A list of configured values for an SDLC link station.
.1.3.6.1.2.1.41.1.2.1.1.1,SNA-SDLC-MIB::sdlcLSAddress,INTEGER,read-create,,current,,This value is the poll address of the secondary link station for this SDLC link. It uniquely identifies the SDLC link station within a single SDLC port.
.1.3.6.1.2.1.41.1.2.1.1.2,SNA-SDLC-MIB::sdlcLSAdminName,OCTET,read-create,,current,,An octet string that defines the local name of the SDLC link station. This field may be sent in the XID3 control vector 0x0E, type 0xF7.
.1.3.6.1.2.1.41.1.2.1.1.3,SNA-SDLC-MIB::sdlcLSAdminState,INTEGER,read-create,,current,inactive(1):active(2),This object controls the desired state of the SDLC station. The managed system shall attempt to keep the operational state, sdlcLSOperState, consistent with this value.
.1.3.6.1.2.1.41.1.2.1.1.4,SNA-SDLC-MIB::sdlcLSAdminISTATUS,INTEGER,read-create,,current,inactive(1):active(2),This parameter controls the desired state, sdlcLSAdminState, of the SDLC link station at link station start-up.
.1.3.6.1.2.1.41.1.2.1.1.5,SNA-SDLC-MIB::sdlcLSAdminMAXDATASend,Integer32,read-create,,current,,This object contains the maximum PDU size that the local link station thinks it can send to the adjacent link station before having received any XID from the ALS. After the maximum PDU size that the ALS can receive is known (via XID exchange) that value is reflected in sdlcLSOperMAXDATASend and takes precedence over this object. This value includes the Transmission Header (TH) and the Request Header (RH).
.1.3.6.1.2.1.41.1.2.1.1.6,SNA-SDLC-MIB::sdlcLSAdminMAXDATARcv,Integer32,read-create,,current,,This object contains the maximum PDU size that the local link station can receive from the adjacent link station. This value is sent in the XID to the ALS. This value includes the Transmission Header (TH) and the Request Header (RH).
.1.3.6.1.2.1.41.1.2.1.1.7,SNA-SDLC-MIB::sdlcLSAdminREPLYTO,INTEGER,read-create,,current,,This object controls the reply timeout (in 1/100ths of a second) for an SDLC link station. If the link station does not receive a response to a poll or message before the specified time expires then the appropriate error recovery shall be initiated. The object descriptor contains the name of an NCP configuration parameter, REPLYTO. Please note that the value of this object represents 1/100ths of a second while the NCP REPLYTO is represented in 1/10ths of a second. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperREPLYTO, until the link station is cycled inactive. This object only has meaning for SDLC ports where sdlcPortAdminRole == primary 
.1.3.6.1.2.1.41.1.2.1.1.8,SNA-SDLC-MIB::sdlcLSAdminMAXIN,INTEGER,read-create,,current,,This object controls the maximum number of unacknowledged I-frames which an SDLC link station may receive. This should range from 1 to (sdlcLSAdminMODULO - 1). This value is sent in the XID to the ALS. A write operation to this administered value will not change the operational value, sdlcLSOperMAXIN, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.9,SNA-SDLC-MIB::sdlcLSAdminMAXOUT,INTEGER,read-create,,current,,This object controls the maximum number of consecutive unacknowledged I-frames which an SDLC link station shall send without an acknowledgement. This shall range from 1 to (sdlcLSAdminMODULO - 1). For link stations on switched SDLC lines, certain implementions may choose to override this administered value with the value received in the XID exchange. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperMAXOUT, until the link station is cycled inactive. An implementation can support only modulo 8, only modulo 128, or both.
.1.3.6.1.2.1.41.1.2.1.1.10,SNA-SDLC-MIB::sdlcLSAdminMODULO,INTEGER,read-create,,current,eight(8):onetwentyeight(128),This object controls the modulus for an SDLC link station. This modulus determines the size of the rotating acknowledgement window used the SDLC link station pair. A write operation to this administered value will not change the operational value, sdlcLSOperMODULO, until the link station is cycled inactive. An implementation can support only modulo 8, only modulo 128, or both.
.1.3.6.1.2.1.41.1.2.1.1.11,SNA-SDLC-MIB::sdlcLSAdminRETRIESm,INTEGER,read-create,,current,,This object controls number of retries in a retry sequence for the local SDLC link station. A retry sequence is a series of retransmitted frames ( data or control) for which no positive acknowledgement is received. The number of times that the retry sequence is to be repeated is controlled by the object: sdlcLSAdminRETRIESn. The interval between retry sequences is controlled by the object: sdlcLSAdminRETRIESt. A value of zero indicates no retries. If the value of sdlcLSAdminRETRIESm is zero, then the values of sdlcLSAdminRETRIESt and sdlcLSAdminRETRIESn should also be zero. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperRETRIESm, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.12,SNA-SDLC-MIB::sdlcLSAdminRETRIESt,INTEGER,read-create,,current,,This object controls the interval (in 1/100ths of a second) between retry sequences for the local SDLC link station if multiple retry sequences are specified . A retry sequence is a series of retransmitted frames ( data or control) for which no positive acknowledgement is received. The number of repeated retries sequences is controlled by the object: sdlcLSAdminRETRIESn. The retries per sequence is controlled by the object: sdlcLSAdminRETRIESm. The object descriptor contains the name of an NCP configuration parameter, RETRIESt. Please note that the value of this object represents 1/100ths of a second while the NCP RETRIESt is represented in seconds. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperRETRIESt, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.13,SNA-SDLC-MIB::sdlcLSAdminRETRIESn,Integer32,read-create,,current,,This object controls the number of times that a retry sequence is repeated for the local SDLC link station. A retry sequence is a series of retransmitted frames ( data or control) for which no positive acknowledgement is received. The interval between retry sequences is controlled by the object: sdlcLSAdminRETRIESn. The retries per sequence is controlled by the object: sdlcLSAdminRETRIESm. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperRETRIESn, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.14,SNA-SDLC-MIB::sdlcLSAdminRNRLIMIT,INTEGER,read-create,,current,,This object controls the length of time (in 1/100ths of a second) that an SDLC link station will allow its adjacent link station to remain in a busy (RNR) state before declaring it inoperative. A value of sdlcLSAdminRNRLIMIT == 0 means there is no limit. The object descriptor contains the name of an NCP configuration parameter, RNRLIMIT. Please note that the value of this object represents 1/100ths of a second while the NCP RNRLIMIT is represented in minutes. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperRNRLIMIT, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.15,SNA-SDLC-MIB::sdlcLSAdminDATMODE,INTEGER,read-create,,current,half(1):full(2),This object controls whether communications mode with the adjacent link station is two-way-alternate (half) or two-way-simultaneous (full). A write operation to this administered value will not change the operational value, sdlcLSOperDATMODE, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.16,SNA-SDLC-MIB::sdlcLSAdminGPoll,INTEGER,read-create,,current,,This object describes the group poll address for this link station instance. If group poll is not in effect for this link station instance, the value for sdlcLSAdminGPoll should be zero. Depending on the implementation, a write operation to this administered value may not change the operational value, sdlcLSOperGPoll, until the link station is cycled inactive.
.1.3.6.1.2.1.41.1.2.1.1.17,SNA-SDLC-MIB::sdlcLSAdminSimRim,INTEGER,read-create,,current,no(1):yes(2),This object controls the support for transmission and receipt of SIM and RIM control frames for this link station. The value of this object controls the setting of the transmit-receive capability sent in the XID field.
.1.3.6.1.2.1.41.1.2.1.1.18,SNA-SDLC-MIB::sdlcLSAdminXmitRcvCap,INTEGER,read-create,,current,twa(1):tws(2),This object controls the transmit-receive capabilities for this SDLC link station. The value of this object establishes the value of the transmit-receive capability indicator sent in the XID image to the adjacent link station.
.1.3.6.1.2.1.41.1.2.1.1.19,SNA-SDLC-MIB::sdlcLSAdminRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by a management station to create or delete the row entry in sdlcLSAdminTable following the RowStatus textual convention. Upon successful creation of the row, an agent automatically creates a corresponding entry in the sdlcLSOperTable with sdlcLSOperState equal to 'discontacted (1)'.
.1.3.6.1.2.1.41.1.2.2,SNA-SDLC-MIB::sdlcLSOperTable,,not-accessible,,current,,This table contains current SDLC link parameters. Many of these objects have corresponding objects in the sdlcLSAdminTable.
.1.3.6.1.2.1.41.1.2.2.1,SNA-SDLC-MIB::sdlcLSOperEntry,,not-accessible,ifIndex:sdlcLSAddress,current,,A list of status and control values for an SDLC link station.
.1.3.6.1.2.1.41.1.2.2.1.1,SNA-SDLC-MIB::sdlcLSOperName,OCTET,read-only,,current,,An octet string that defines the name of the remote SDLC link station. This field is received in the XID3 control vector 0x0E, type 0xF7.
.1.3.6.1.2.1.41.1.2.2.1.2,SNA-SDLC-MIB::sdlcLSOperRole,INTEGER,read-only,,current,primary(1):secondary(2):undefined(3),This object reflects the current role that the link station is assuming. The value of sdlcLSOperRole is undefined(3) whenever the link station role has not yet been established by the mode setting command.
.1.3.6.1.2.1.41.1.2.2.1.3,SNA-SDLC-MIB::sdlcLSOperState,INTEGER,read-only,,current,discontacted(1):contactPending(2):contacted(3):discontactPending(4),This object describes the operational state of the SDLC link station. The managed system shall attempt to keep this value consistent with the administered state, sdlcLSAdminState
.1.3.6.1.2.1.41.1.2.2.1.4,SNA-SDLC-MIB::sdlcLSOperMAXDATASend,Integer32,read-only,,current,,This object contains the actual maximum PDU size that the local link station can send to the adjacent link station. This object is established from the value received in the XID from the adjacent link station. If no XID is received, then this value is implementation dependent (for instance, it could be the value of sdlcLSAdminMAXDATASend). This value includes the Transmission Header (TH) and the Request Header (RH).
.1.3.6.1.2.1.41.1.2.2.1.5,SNA-SDLC-MIB::sdlcLSOperREPLYTO,INTEGER,read-only,,current,,This object reflects the current reply timeout (in 1/100ths of a second) for an SDLC link station. If the link station does not receive a response to a poll or message before the specified time expires then the appropriate error recovery shall be initiated. The object descriptor contains the name of an NCP configuration parameter, REPLYTO. Please note that the value of this object represents 1/100ths of a second while the NCP REPLYTO is represented in 1/10ths of a second. This object only has meaning for SDLC ports where sdlcPortOperRole == primary 
.1.3.6.1.2.1.41.1.2.2.1.6,SNA-SDLC-MIB::sdlcLSOperMAXIN,INTEGER,read-only,,current,,This object reflects the current maximum number of unacknowledged I-frames which an SDLC link station may receive. This shall range from 1 to (sdlcLSOperMODULO - 1).
.1.3.6.1.2.1.41.1.2.2.1.7,SNA-SDLC-MIB::sdlcLSOperMAXOUT,INTEGER,read-only,,current,,This object controls the maximum number of consecutive unacknowledged I-frames which an SDLC link station shall send without an acknowledgement. This shall range from 1 to (sdlcLSAdminMODULO - 1). This value may controlled by the administered MAXOUT, sdlcLSAdminMAXOUT, or by the MAXIN value received during the XID exchange.
.1.3.6.1.2.1.41.1.2.2.1.8,SNA-SDLC-MIB::sdlcLSOperMODULO,INTEGER,read-only,,current,eight(8):onetwentyeight(128),This object reflects the current modulus for an SDLC link station. This modulus determines the size of rotating acknowledgement window used by the SDLC link station pair.
.1.3.6.1.2.1.41.1.2.2.1.9,SNA-SDLC-MIB::sdlcLSOperRETRIESm,INTEGER,read-only,,current,,This object controls number of retries in a retry sequence for an SDLC link station. A retry sequence is a series of retransmitted frames ( data or control) for which no positive acknowledgement is received. The current number of times that the retry sequence is to be repeated is reflected by the object: sdlcLSOperRETRIESn. The current interval between retry sequences is reflected by the object: sdlcLSOperRETRIESt.
.1.3.6.1.2.1.41.1.2.2.1.10,SNA-SDLC-MIB::sdlcLSOperRETRIESt,INTEGER,read-only,,current,,This object reflects the current interval (in 1/100ths of a second) between retry sequences for an SDLC link station if multiple retry sequences are specified. A retry sequence is a series of retransmitted frames ( data or control) for which no positive acknowledgement is received. The object descriptor contains the name of an NCP configuration parameter, RETRIESt. Please note that the value of this object represents 1/100ths of a second while the NCP RETRIESt is represented in seconds. The current number of repeated retries sequences is reflected by the object: sdlcLSOperRETRIESn. The current retries per sequence is reflected by the object: sdlcLSOperRETRIESm.
.1.3.6.1.2.1.41.1.2.2.1.11,SNA-SDLC-MIB::sdlcLSOperRETRIESn,INTEGER,read-only,,current,,This object reflects the current number of times that a retry sequence is repeated for an SDLC link station. A retry sequence is a series of retransmitted frames ( data or control) for which no positive acknowledgement is received. The current interval between retry sequences is reflected by the object: sdlcLSOperRETRIESn. The current retries per sequence is reflected by the object: sdlcLSOperRETRIESm.
.1.3.6.1.2.1.41.1.2.2.1.12,SNA-SDLC-MIB::sdlcLSOperRNRLIMIT,INTEGER,read-only,,current,,This object reflects the current length of time (in 1/100ths of a second) that an SDLC link station will allow its adjacent link station to remain in a busy (RNR) state before declaring it inoperative. The object descriptor contains the name of an NCP configuration parameter, RNRLIMIT. Please note that the value of this object represents 1/100ths of a second while the NCP RNRLIMIT is represented in minutes. A value of sdlcLSOperRNRLIMIT == 0 means there is no limit.
.1.3.6.1.2.1.41.1.2.2.1.13,SNA-SDLC-MIB::sdlcLSOperDATMODE,INTEGER,read-only,,current,half(1):full(2),This object reflects whether the current communications mode with the adjacent link station is two-way-alternate (half) or two-way-simultaneous (full).
.1.3.6.1.2.1.41.1.2.2.1.14,SNA-SDLC-MIB::sdlcLSOperLastModifyTime,TimeTicks,read-only,,current,,This object describes the value of sysUpTime when this link station definition was last modified. If the link station has not been modified, then this value shall be zero.
.1.3.6.1.2.1.41.1.2.2.1.15,SNA-SDLC-MIB::sdlcLSOperLastFailTime,TimeTicks,read-only,,current,,This object describes the value of sysUpTime when this SDLC link station last failed. If the link station has not failed, then this value shall be zero.
.1.3.6.1.2.1.41.1.2.2.1.16,SNA-SDLC-MIB::sdlcLSOperLastFailCause,INTEGER,read-only,,current,undefined(1):rxFRMR(2):txFRMR(3):noResponse(4):protocolErr(5):noActivity(6):rnrLimit(7):retriesExpired(8),This enumerated object reflects the cause of the last failure of this SDLC link station. If the link station has not failed, then this object will have a value of undefined(1).
.1.3.6.1.2.1.41.1.2.2.1.17,SNA-SDLC-MIB::sdlcLSOperLastFailCtrlIn,OCTET,read-only,,current,,This object reflects the last control octet or octets (depending on modulus) received by this SDLC link station at the time of the last failure. If the link station has not failed, then this value has no meaning.
.1.3.6.1.2.1.41.1.2.2.1.18,SNA-SDLC-MIB::sdlcLSOperLastFailCtrlOut,OCTET,read-only,,current,,This object reflects the last control octet or octets (depending on modulus) sent by this SDLC link station at the time of the last failure. If the link station has not failed, then this value has no meaning.
.1.3.6.1.2.1.41.1.2.2.1.19,SNA-SDLC-MIB::sdlcLSOperLastFailFRMRInfo,OCTET,read-only,,current,,This object reflects the information field of the FRMR frame if the last failure for this SDLC link station was as a result of an invalid frame. Otherwise, this field has no meaning.
.1.3.6.1.2.1.41.1.2.2.1.20,SNA-SDLC-MIB::sdlcLSOperLastFailREPLYTOs,Counter32,read-only,,current,,This object reflects the number of times that the REPLYTO timer had expired for an SDLC link station at the time of the last failure. If the link station has not failed, then this value has no meaning.
.1.3.6.1.2.1.41.1.2.2.1.21,SNA-SDLC-MIB::sdlcLSOperEcho,INTEGER,read-only,,current,no(1):yes(2),This object identifies whether the echo bit is in effect for this particular link station.
.1.3.6.1.2.1.41.1.2.2.1.22,SNA-SDLC-MIB::sdlcLSOperGPoll,INTEGER,read-only,,current,,This object describes the group poll address in effect for this link station instance.
.1.3.6.1.2.1.41.1.2.2.1.23,SNA-SDLC-MIB::sdlcLSOperSimRim,INTEGER,read-only,,current,no(1):yes(2),This object reflects the support for transmission and receipt of SIM and RIM control frames for the adjacent link station. The value of this object is set from the XID field received from the adjacent link station.
.1.3.6.1.2.1.41.1.2.2.1.24,SNA-SDLC-MIB::sdlcLSOperXmitRcvCap,INTEGER,read-only,,current,twa(1):tws(2),This object reflects the transmit-receive capabilities for the adjacent SDLC link station. The value of this object is the value of the transmit-receive capability indicator received in the XID image from the adjacent link station.
.1.3.6.1.2.1.41.1.2.3,SNA-SDLC-MIB::sdlcLSStatsTable,,not-accessible,,current,,Each entry in this table contains statistics for a specific SDLC link station.
.1.3.6.1.2.1.41.1.2.3.1,SNA-SDLC-MIB::sdlcLSStatsEntry,,not-accessible,ifIndex:sdlcLSAddress,current,,A list of statistics for an SDLC link station.
.1.3.6.1.2.1.41.1.2.3.1.1,SNA-SDLC-MIB::sdlcLSStatsBLUsIn,Counter32,read-only,,current,,This object reflects the total basic link units (BLUs; frames) received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.2,SNA-SDLC-MIB::sdlcLSStatsBLUsOut,Counter32,read-only,,current,,This object reflects the total basic link units (BLUs; frames), transmitted to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.3,SNA-SDLC-MIB::sdlcLSStatsOctetsIn,Counter32,read-only,,current,,This object reflects the total octets received from an adjacent SDLC link station since link station startup. This object covers the address, control, and information field of I-Frames only. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.4,SNA-SDLC-MIB::sdlcLSStatsOctetsOut,Counter32,read-only,,current,,This object reflects the total octets transmitted to an adjacent SDLC link station since link station startup. This object covers the address, control, and information field of I-Frames only. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.5,SNA-SDLC-MIB::sdlcLSStatsPollsIn,Counter32,read-only,,current,,This object reflects the total polls received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.6,SNA-SDLC-MIB::sdlcLSStatsPollsOut,Counter32,read-only,,current,,This object reflects the total polls sent to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.7,SNA-SDLC-MIB::sdlcLSStatsPollRspsOut,Counter32,read-only,,current,,This object reflects the total number of poll responses sent to the adjacent SDLC link station since link station startup. This value includes I-frames that are sent in response to a poll. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.8,SNA-SDLC-MIB::sdlcLSStatsPollRspsIn,Counter32,read-only,,current,,This object reflects the total number of poll responses received from the adjacent SDLC link station since station startup. This value includes I-frames that are received in response to a poll. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.9,SNA-SDLC-MIB::sdlcLSStatsLocalBusies,Counter32,read-only,,current,,This object reflects the total number of times that the local SDLC link station has entered a busy state (RNR) since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.10,SNA-SDLC-MIB::sdlcLSStatsRemoteBusies,Counter32,read-only,,current,,This object reflects the total number of times that an adjacent ( remote) SDLC link station has entered a busy state (RNR) since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.11,SNA-SDLC-MIB::sdlcLSStatsIFramesIn,Counter32,read-only,,current,,This object reflects the total I-frames received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.12,SNA-SDLC-MIB::sdlcLSStatsIFramesOut,Counter32,read-only,,current,,This object reflects the total I-frames transmitted to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.13,SNA-SDLC-MIB::sdlcLSStatsUIFramesIn,Counter32,read-only,,current,,This object reflects the total UI-frames received from an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.14,SNA-SDLC-MIB::sdlcLSStatsUIFramesOut,Counter32,read-only,,current,,This object reflects the total UI-frames transmitted to an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.15,SNA-SDLC-MIB::sdlcLSStatsXIDsIn,Counter32,read-only,,current,,This object reflects the total XID frames received from an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.16,SNA-SDLC-MIB::sdlcLSStatsXIDsOut,Counter32,read-only,,current,,This object reflects the total XID frames transmitted to an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.17,SNA-SDLC-MIB::sdlcLSStatsTESTsIn,Counter32,read-only,,current,,This object reflects the total TEST frames, commands or responses, received from an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.18,SNA-SDLC-MIB::sdlcLSStatsTESTsOut,Counter32,read-only,,current,,This object reflects the total TEST frames, commands or responses, transmitted to an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.19,SNA-SDLC-MIB::sdlcLSStatsREJsIn,Counter32,read-only,,current,,This object reflects the total REJ frames received from an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.20,SNA-SDLC-MIB::sdlcLSStatsREJsOut,Counter32,read-only,,current,,This object reflects the total REJ frames transmitted to an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.21,SNA-SDLC-MIB::sdlcLSStatsFRMRsIn,Counter32,read-only,,current,,This object reflects the total frame reject (FRMR) frames received from an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.22,SNA-SDLC-MIB::sdlcLSStatsFRMRsOut,Counter32,read-only,,current,,This object reflects the total frame reject (FRMR) frames transmitted to an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.23,SNA-SDLC-MIB::sdlcLSStatsSIMsIn,Counter32,read-only,,current,,This object reflects the total set initialization mode (SIM) frames received from an adjacent SDLC link station since link station startup.
.1.3.6.1.2.1.41.1.2.3.1.24,SNA-SDLC-MIB::sdlcLSStatsSIMsOut,Counter32,read-only,,current,,This object reflects the total set initialization mode (SIM) frames transmitted to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.25,SNA-SDLC-MIB::sdlcLSStatsRIMsIn,Counter32,read-only,,current,,This object reflects the total request initialization mode (RIM) frames received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.26,SNA-SDLC-MIB::sdlcLSStatsRIMsOut,Counter32,read-only,,current,,This object reflects the total request initialization mode (RIM) frames transmitted to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.27,SNA-SDLC-MIB::sdlcLSStatsDISCIn,Counter32,read-only,,current,,This object reflects the total number of disconnect (DISC) requests received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.28,SNA-SDLC-MIB::sdlcLSStatsDISCOut,Counter32,read-only,,current,,This object reflects the total number of disconnect (DISC) requests transmited to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.29,SNA-SDLC-MIB::sdlcLSStatsUAIn,Counter32,read-only,,current,,This object reflects the total number of unnumbered acknowledgements (UA) requests received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.30,SNA-SDLC-MIB::sdlcLSStatsUAOut,Counter32,read-only,,current,,This object reflects the total number of unnumbered acknowledgements (UA) requests transmited to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.31,SNA-SDLC-MIB::sdlcLSStatsDMIn,Counter32,read-only,,current,,This object reflects the total number of disconnect mode (DM) requests received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.32,SNA-SDLC-MIB::sdlcLSStatsDMOut,Counter32,read-only,,current,,This object reflects the total number of disconnect mode (DM) requests transmited to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.33,SNA-SDLC-MIB::sdlcLSStatsSNRMIn,Counter32,read-only,,current,,This object reflects the total number of set normal response mode (SNRM/SNRME) requests received from an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.34,SNA-SDLC-MIB::sdlcLSStatsSNRMOut,Counter32,read-only,,current,,This object reflects the total number of set normal response mode (SNRM/SNRME) requests transmited to an adjacent SDLC link station since link station startup. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.35,SNA-SDLC-MIB::sdlcLSStatsProtocolErrs,Counter32,read-only,,current,,This object reflects the total occurrences, since link station startup, where this SDLC link station has inactivated the link as a result of receiving a frame from its adjacent link station which was in violation of the protocol. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.36,SNA-SDLC-MIB::sdlcLSStatsActivityTOs,Counter32,read-only,,current,,This object reflects the total occurrences, since startup, where this SDLC link station has inactivated the link as a result of no activity on the link. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.37,SNA-SDLC-MIB::sdlcLSStatsRNRLIMITs,Counter32,read-only,,current,,This object reflects the total occurrences, since startup, where this SDLC link station has inactivated the link as a result of its RNRLIMIT timer expiring. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.38,SNA-SDLC-MIB::sdlcLSStatsRetriesExps,Counter32,read-only,,current,,This object reflects the total occurrences, since startup, where this SDLC link station has inactivated the link as a result of a retry sequence being exhausted. At link station startup time, this object must be initialized to zero.
.1.3.6.1.2.1.41.1.2.3.1.39,SNA-SDLC-MIB::sdlcLSStatsRetransmitsIn,Counter32,read-only,,current,,This object reflects the total number of information frames retransmitted by the remote link station because the N(s) received from that link station indicated that one or more information frames sent by that station were lost. This event causes the first missing information frame of a window and all subsequent information frames to be retransmitted. At link station startup time, this object must be initialized to zero. Management: If the value of sdlcLSStatsRetransmitsIn grows over time, then the quality of the serial line is in question. You might want to look at decreasing the value for sdlcLSAdminMAXDATASend to compensate for the lower quality line.
.1.3.6.1.2.1.41.1.2.3.1.40,SNA-SDLC-MIB::sdlcLSStatsRetransmitsOut,Counter32,read-only,,current,,This object reflects the total number of information frames retransmitted to a remote link station because the N(r) received from that link station indicated that one or more information frames sent to that station were lost. This event causes the first missing information frame of a window and all subsequent information frames to be retransmitted. At link station startup time, this object must be initialized to zero. Management: If the value of sdlcLSStatsRetransmitsOut grows over time, then the quality of the serial line is in question. You might want to look at decreasing the value for sdlcLSAdminMAXDATASend to compensate for the lower quality line.
.1.3.6.1.2.1.41.1.3,SNA-SDLC-MIB::sdlcTraps,,,,,,
.1.3.6.1.2.1.41.1.3.1,SNA-SDLC-MIB::sdlcPortStatusChange,,,,,,This trap indicates that the state of an SDLC port has transitioned to active or inactive.
.1.3.6.1.2.1.41.1.3.2,SNA-SDLC-MIB::sdlcLSStatusChange,,,,,,This trap indicates that the state of an SDLC link station has transitioned to contacted or discontacted.
.1.3.6.1.2.1.41.1.4,SNA-SDLC-MIB::sdlcConformance,,,,,,
.1.3.6.1.2.1.41.1.4.1,SNA-SDLC-MIB::sdlcCompliances,,,,,,
.1.3.6.1.2.1.41.1.4.1.1,SNA-SDLC-MIB::sdlcCoreCompliance,,,,,,The core compliance statement for all SDLC nodes.
.1.3.6.1.2.1.41.1.4.1.2,SNA-SDLC-MIB::sdlcPrimaryCompliance,,,,,,The compliance statement for all nodes that are performing the role of a Primary link station.
.1.3.6.1.2.1.41.1.4.1.3,SNA-SDLC-MIB::sdlcPrimaryMultipointCompliance,,,,,,The compliance statement for all nodes that are performing the role of a primary link station on a multipoint line.
.1.3.6.1.2.1.41.1.4.2,SNA-SDLC-MIB::sdlcGroups,,,,,,
.1.3.6.1.2.1.41.1.4.2.1,SNA-SDLC-MIB::sdlcCoreGroups,,,,,,
.1.3.6.1.2.1.41.1.4.2.1.1,SNA-SDLC-MIB::sdlcCorePortAdminGroup,,,,,,The sdlcCorePortAdminGroup defines objects which are common to the PortAdmin group of all compliant link stations.
.1.3.6.1.2.1.41.1.4.2.1.2,SNA-SDLC-MIB::sdlcCorePortOperGroup,,,,,,The sdlcCorePortOperGroup defines objects which are common to the PortOper group of all compliant link stations.
.1.3.6.1.2.1.41.1.4.2.1.3,SNA-SDLC-MIB::sdlcCorePortStatsGroup,,,,,,The sdlcCorePortStatsGroup defines objects which are common to the PortStats group of all compliant link stations.
.1.3.6.1.2.1.41.1.4.2.1.4,SNA-SDLC-MIB::sdlcCoreLSAdminGroup,,,,,,The sdlcCorePortAdminGroup defines objects which are common to the PortAdmin group of all compliant link stations.
.1.3.6.1.2.1.41.1.4.2.1.5,SNA-SDLC-MIB::sdlcCoreLSOperGroup,,,,,,The sdlcCorePortOperGroup defines objects which are common to the PortOper group of all compliant link stations.
.1.3.6.1.2.1.41.1.4.2.1.6,SNA-SDLC-MIB::sdlcCoreLSStatsGroup,,,,,,The sdlcCorePortStatsGroup defines objects which are common to the PortStats group of all compliant link stations.
.1.3.6.1.2.1.41.1.4.2.2,SNA-SDLC-MIB::sdlcPrimaryGroups,,,,,,
.1.3.6.1.2.1.41.1.4.2.2.1,SNA-SDLC-MIB::sdlcPrimaryGroup,,,,,,The sdlcPrimaryGroup defines objects which are common to all compliant primary link stations.
.1.3.6.1.2.1.41.1.4.2.2.2,SNA-SDLC-MIB::sdlcPrimaryMultipointGroup,,,,,,The sdlcPrimaryMultipointGroup defines objects which are common to all compliant primary link stations that are in a multipoint topology.
.1.3.6.1.2.1.42,TOKENRING-STATION-SR-MIB::dot5SrMIB,,,,,,The MIB module for managing source routes in end-stations on IEEE 802.5 Token Ring networks.
.1.3.6.1.2.1.42.1,TOKENRING-STATION-SR-MIB::dot5SrMIBObjects,,,,,,
.1.3.6.1.2.1.42.1.1,TOKENRING-STATION-SR-MIB::dot5SrRouteTable,,not-accessible,,current,,The table of source-routing routes. This represents the 802.5 RIF database.
.1.3.6.1.2.1.42.1.1.1,TOKENRING-STATION-SR-MIB::dot5SrRouteEntry,,not-accessible,ifIndex:dot5SrRouteDestination,current,,Information on a specific route. An entry is created whenever a 'Single Path Explorer' or an 'All Paths Explorer' discovers a route to a neighbor not currently in the table, or whenever an 'All Paths Explorer' discovers a better (e.g., shorter) route than the route currently stored in the table. This is done on behalf of any network layer client. The ifIndex value in the INDEX clause refers to the value of MIB-II's ifIndex object for the interface on which the route is in effect.
.1.3.6.1.2.1.42.1.1.1.2,TOKENRING-STATION-SR-MIB::dot5SrRouteDestination,OCTET,not-accessible,,current,,The destination of this route.
.1.3.6.1.2.1.42.1.1.1.3,TOKENRING-STATION-SR-MIB::dot5SrRouteControl,OCTET,read-create,,current,,The value of Routing Control field for this route.
.1.3.6.1.2.1.42.1.1.1.4,TOKENRING-STATION-SR-MIB::dot5SrRouteDescr,OCTET,read-create,,current,,The embedded sequence of bridge and ring ID's for this route. For destinations on the local ring, the value of this object is the zero-length string.
.1.3.6.1.2.1.42.1.1.1.5,TOKENRING-STATION-SR-MIB::dot5SrRouteStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of the instances of dot5SrRouteControl and dot5SrRouteDescr can be modified while the row's status is 'active.
.1.3.6.1.2.1.42.2,TOKENRING-STATION-SR-MIB::dot5SrConformance,,,,,,
.1.3.6.1.2.1.42.2.1,TOKENRING-STATION-SR-MIB::dot5SrGroups,,,,,,
.1.3.6.1.2.1.42.2.1.1,TOKENRING-STATION-SR-MIB::dot5SrRouteGroup,,,,,,A collection of objects providing for the management of source routes in stations on IEEE 802.5 source-routing networks.
.1.3.6.1.2.1.42.2.2,TOKENRING-STATION-SR-MIB::dot5SrCompliances,,,,,,
.1.3.6.1.2.1.42.2.2.1,TOKENRING-STATION-SR-MIB::dot5SrCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the IEEE 802.5 Station Source Route MIB.
.1.3.6.1.2.1.43,Printer-MIB::printmib,,,,,,The MIB module for management of printers. Copyright (C) The Internet Society (2004). This version of this MIB module was published in RFC 3805. For full legal notices see the RFC itself.
.1.3.6.1.2.1.43.2,Printer-MIB::prtMIBConformance,,,,,,
.1.3.6.1.2.1.43.2.1,Printer-MIB::prtMIBCompliance,,,,,,The compliance statement for agents that implement the printer MIB as defined by RFC 1759.
.1.3.6.1.2.1.43.2.2,Printer-MIB::prtMIBGroups,,,,,,
.1.3.6.1.2.1.43.2.2.1,Printer-MIB::prtGeneralGroup,,,,,,The general printer group.
.1.3.6.1.2.1.43.2.2.2,Printer-MIB::prtResponsiblePartyGroup,,,,,,The responsible party group contains contact information for humans responsible for the printer.
.1.3.6.1.2.1.43.2.2.3,Printer-MIB::prtInputGroup,,,,,,The input group.
.1.3.6.1.2.1.43.2.2.4,Printer-MIB::prtExtendedInputGroup,,,,,,The extended input group.
.1.3.6.1.2.1.43.2.2.5,Printer-MIB::prtInputMediaGroup,,,,,,The input media group.
.1.3.6.1.2.1.43.2.2.6,Printer-MIB::prtOutputGroup,,,,,,The output group.
.1.3.6.1.2.1.43.2.2.7,Printer-MIB::prtExtendedOutputGroup,,,,,,The extended output group.
.1.3.6.1.2.1.43.2.2.8,Printer-MIB::prtOutputDimensionsGroup,,,,,,The output dimensions group
.1.3.6.1.2.1.43.2.2.9,Printer-MIB::prtOutputFeaturesGroup,,,,,,The output features group.
.1.3.6.1.2.1.43.2.2.10,Printer-MIB::prtMarkerGroup,,,,,,The marker group.
.1.3.6.1.2.1.43.2.2.11,Printer-MIB::prtMarkerSuppliesGroup,,,,,,The marker supplies group.
.1.3.6.1.2.1.43.2.2.12,Printer-MIB::prtMarkerColorantGroup,,,,,,The marker colorant group.
.1.3.6.1.2.1.43.2.2.13,Printer-MIB::prtMediaPathGroup,,,,,,The media path group.
.1.3.6.1.2.1.43.2.2.14,Printer-MIB::prtChannelGroup,,,,,,The channel group.
.1.3.6.1.2.1.43.2.2.15,Printer-MIB::prtInterpreterGroup,,,,,,The interpreter group.
.1.3.6.1.2.1.43.2.2.16,Printer-MIB::prtConsoleGroup,,,,,,The console group.
.1.3.6.1.2.1.43.2.2.17,Printer-MIB::prtAlertTableGroup,,,,,,The alert table group.
.1.3.6.1.2.1.43.2.2.18,Printer-MIB::prtAlertTimeGroup,,,,,,The alert time group. Implementation of prtAlertTime is strongly RECOMMENDED.
.1.3.6.1.2.1.43.2.2.19,Printer-MIB::prtAuxiliarySheetGroup,,,,,,The auxiliary sheet group.
.1.3.6.1.2.1.43.2.2.20,Printer-MIB::prtInputSwitchingGroup,,,,,,The input switching group.
.1.3.6.1.2.1.43.2.2.21,Printer-MIB::prtGeneralV2Group,,,,,,The general printer group with new v2 objects.
.1.3.6.1.2.1.43.2.2.22,Printer-MIB::prtAlertTableV2Group,,,,,,The alert table group with new v2 objects and prtAlertIndex changed to MAX-ACCESS of 'read-only' for inclusion in the trap bindings (as originally defined in RFC 1759).
.1.3.6.1.2.1.43.2.2.23,Printer-MIB::prtChannelV2Group,,,,,,The channel group with a new v2 object.
.1.3.6.1.2.1.43.2.2.24,Printer-MIB::prtAlertTrapGroup,,,,,,The alert trap group.
.1.3.6.1.2.1.43.2.3,Printer-MIB::prtMIB2Compliance,,,,,,The compliance statement for agents that implement the printer MIB V2.
.1.3.6.1.2.1.43.2.4,Printer-MIB::prtMIB2Groups,,,,,,
.1.3.6.1.2.1.43.2.5,Finisher-MIB::finMIBCompliance,,,,,,The compliance statement for agents that implement the finisher MIB.
.1.3.6.1.2.1.43.2.6,Finisher-MIB::finMIBGroups,,,,,,
.1.3.6.1.2.1.43.2.6.1,Finisher-MIB::finDeviceGroup,,,,,,The finisher device group.
.1.3.6.1.2.1.43.2.6.2,Finisher-MIB::finSupplyGroup,,,,,,The finisher supply group.
.1.3.6.1.2.1.43.2.6.3,Finisher-MIB::finSupplyMediaInputGroup,,,,,,The finisher supply, media input group.
.1.3.6.1.2.1.43.2.6.4,Finisher-MIB::finDeviceAttributeGroup,,,,,,The finisher device attribute group. This group is mandatory for a finisher device that contains an inserter subunit.
.1.3.6.1.2.1.43.5,Printer-MIB::prtGeneral,,,,,,
.1.3.6.1.2.1.43.5.1,Printer-MIB::prtGeneralTable,,not-accessible,,current,,A table of general information per printer. Objects in this table are defined in various places in the MIB, nearby the groups to which they apply. They are all defined here to minimize the number of tables that would otherwise need to exist.
.1.3.6.1.2.1.43.5.1.1,Printer-MIB::prtGeneralEntry,,not-accessible,hrDeviceIndex,current,,An entry exists in this table for each device entry in the host resources MIB device table with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.1,Printer-MIB::prtGeneralConfigChanges,Counter32,read-only,,current,,Counts configuration changes within the printer. A configuration change is defined to be an action that results in a change to any MIB object other than those that reflect status or level, or those that act as counters or gauges. In addition, any action that results in a row being added or deleted from any table in the Printer MIB is considered a configuration change. Such changes will often affect the capability of the printer to service certain types of print jobs. Management applications may cache infrequently changed configuration information about sub units within the printer. This object should be incremented whenever the agent wishes to notify management applications that any cached configuration information for this device is to be considered 'stale'. At this point, the management application should flush any configuration information cached about this device and fetch new configuration information. The following are examples of actions that would cause the prtGeneralConfigChanges object to be incremented: - Adding an output bin - Changing the media in a sensing input tray - Changing the value of prtInputMediaType Note that the prtGeneralConfigChanges counter would not be incremented when an input tray is temporarily removed to load additional paper or when the level of an input device changes. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.2,Printer-MIB::prtGeneralCurrentLocalization,Integer32,read-write,,current,,The value of the prtLocalizationIndex corresponding to the current language, country, and character set to be used for localized string values that are identified as being dependent on the value of this object. Note that this object does not apply to localized strings in the prtConsole group or to any object that is not explicitly identified as being localized according to prtGeneralCurrentLocalization. When an object's 'charset' is controlled by the value of prtGeneralCurrentLocalization, it MUST specify PrtLocalizedDescriptionStringTC as its syntax. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.3,Printer-MIB::prtGeneralReset,INTEGER,read-write,,current,notResetting(3):powerCycleReset(4):resetToNVRAM(5):resetToFactoryDefaults(6),Setting this value to 'powerCycleReset', 'resetToNVRAM', or 'resetToFactoryDefaults' will result in the resetting of the printer. When read, this object will always have the value 'notResetting(3)', and a SET of the value 'notResetting' shall have no effect on the printer. Some of the defined values are optional. However, every implementation must support at least the values 'notResetting' and 'resetToNVRAM'.
.1.3.6.1.2.1.43.5.1.1.4,Printer-MIB::prtGeneralCurrentOperator,OCTET,read-write,,current,,The name of the person who is responsible for operating this printer. It is suggested that this string include information that would enable other humans to reach the operator, such as a phone number. As a convention to facilitate automatic notification of the operator by the agent or network management station, the phone number, fax number or email address should be indicated by the URL schemes 'tel:', 'fax:' and 'mailto:', respectively. If either the phone, fax, or email information is not available, then a line should not be included for this information. NOTE: For interoperability purposes, it is advisable to use email addresses formatted according to [RFC2822] requirements. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.5,Printer-MIB::prtGeneralServicePerson,OCTET,read-write,,current,,The name of the person responsible for servicing this printer. It is suggested that this string include information that would enable other humans to reach the service person, such as a phone number. As a convention to facilitate automatic notification of the operator by the agent or network management station, the phone number, fax number or email address should be indicated by the URL schemes 'tel:', 'fax:' and 'mailto:', respectively. If either the phone, fax, or email information is not available, then a line should not be included for this information. NOTE: For interoperability purposes, it is advisable to use email addresses formatted per [RFC2822] requirements. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.6,Printer-MIB::prtInputDefaultIndex,Integer32,read-write,,current,,The value of prtInputIndex corresponding to the default input sub-unit: that is, this object selects the default source of input media.
.1.3.6.1.2.1.43.5.1.1.7,Printer-MIB::prtOutputDefaultIndex,Integer32,read-write,,current,,The value of prtOutputIndex corresponding to the default output sub-unit; that is, this object selects the default output destination.
.1.3.6.1.2.1.43.5.1.1.8,Printer-MIB::prtMarkerDefaultIndex,Integer32,read-write,,current,,The value of prtMarkerIndex corresponding to the default marker sub-unit; that is, this object selects the default marker.
.1.3.6.1.2.1.43.5.1.1.9,Printer-MIB::prtMediaPathDefaultIndex,Integer32,read-write,,current,,The value of prtMediaPathIndex corresponding to the default media path; that is, the selection of the default media path.
.1.3.6.1.2.1.43.5.1.1.10,Printer-MIB::prtConsoleLocalization,Integer32,read-write,,current,,The value of the prtLocalizationIndex corresponding to the language, country, and character set to be used for the console. This localization applies both to the actual display on the console as well as the encoding of these console objects in management operations. When an object's 'charset' is controlled by the value of prtConsoleLocalization, it MUST specify PrtConsoleDescriptionStringTC as its syntax. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.11,Printer-MIB::prtConsoleNumberOfDisplayLines,Integer32,read-only,,current,,The number of lines on the printer's physical display. This value is 0 if there are no lines on the physical display or if there is no physical display
.1.3.6.1.2.1.43.5.1.1.12,Printer-MIB::prtConsoleNumberOfDisplayChars,Integer32,read-only,,current,,The number of characters per line displayed on the physical display. This value is 0 if there are no lines on the physical display or if there is no physical display
.1.3.6.1.2.1.43.5.1.1.13,Printer-MIB::prtConsoleDisable,INTEGER,read-write,,current,enabled(3):disabled(4),This value indicates how input is (or is not) accepted from the operator console. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.1.1.14,Printer-MIB::prtAuxiliarySheetStartupPage,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),Used to enable or disable printing a startup page. If enabled, a startup page will be printed shortly after power-up, when the device is ready. Typical startup pages include test patterns and/or printer configuration information.
.1.3.6.1.2.1.43.5.1.1.15,Printer-MIB::prtAuxiliarySheetBannerPage,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),Used to enable or disable printing banner pages at the beginning of jobs. This is a master switch which applies to all jobs, regardless of interpreter.
.1.3.6.1.2.1.43.5.1.1.16,Printer-MIB::prtGeneralPrinterName,OCTET,read-write,,current,,An administrator-specified name for this printer. Depending upon implementation of this printer, the value of this object may or may not be same as the value for the MIB-II 'SysName' object.
.1.3.6.1.2.1.43.5.1.1.17,Printer-MIB::prtGeneralSerialNumber,OCTET,read-write,,current,,A recorded serial number for this device that indexes some type device catalog or inventory. This value is usually set by the device manufacturer but the MIB supports the option of writing for this object for site-specific administration of device inventory or tracking.
.1.3.6.1.2.1.43.5.1.1.18,Printer-MIB::prtAlertCriticalEvents,Counter32,read-only,,current,,A running counter of the number of critical alert events that have been recorded in the alert table. The value of this object is RESET in the event of a power cycle operation (i.e., the value is not persistent.
.1.3.6.1.2.1.43.5.1.1.19,Printer-MIB::prtAlertAllEvents,Counter32,read-only,,current,,A running counter of the total number of alert event entries (critical and non-critical) that have been recorded in the alert table
.1.3.6.1.2.1.43.5.2,Printer-MIB::prtStorageRefTable,,not-accessible,,current,,This table defines which printer, amongst multiple printers serviced by one agent, owns which storage units. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.2.1,Printer-MIB::prtStorageRefEntry,,not-accessible,hrStorageIndex:prtStorageRefSeqNumber,current,,This table will have an entry for each entry in the Host Resources MIB storage table that represents storage associated with a printer managed by this agent. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.2.1.1,Printer-MIB::prtStorageRefSeqNumber,Integer32,not-accessible,,current,,This value will be unique amongst all entries with a common value of hrStorageIndex. This object allows a storage entry to point to the multiple printer devices with which it is associated.
.1.3.6.1.2.1.43.5.2.1.2,Printer-MIB::prtStorageRefIndex,Integer32,read-only,,current,,The value of the hrDeviceIndex of the printer device that this storageEntry is associated with.
.1.3.6.1.2.1.43.5.3,Printer-MIB::prtDeviceRefTable,,not-accessible,,current,,This table defines which printer, amongst multiple printers serviced by one agent, is associated with which devices. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.3.1,Printer-MIB::prtDeviceRefEntry,,not-accessible,hrDeviceIndex:prtDeviceRefSeqNumber,current,,This table will have an entry for each entry in the Host Resources MIB device table that represents a device associated with a printer managed by this agent. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.5.3.1.1,Printer-MIB::prtDeviceRefSeqNumber,Integer32,not-accessible,,current,,This value will be unique amongst all entries with a common value of hrDeviceIndex. This object allows a device entry to point to the multiple printer devices with which it is associated.
.1.3.6.1.2.1.43.5.3.1.2,Printer-MIB::prtDeviceRefIndex,Integer32,read-only,,current,,The value of the hrDeviceIndex of the printer device that this deviceEntry is associated with.
.1.3.6.1.2.1.43.6,Printer-MIB::prtCover,,,,,,
.1.3.6.1.2.1.43.6.1,Printer-MIB::prtCoverTable,,not-accessible,,current,,A table of the covers and interlocks of the printer.
.1.3.6.1.2.1.43.6.1.1,Printer-MIB::prtCoverEntry,,not-accessible,hrDeviceIndex:prtCoverIndex,current,,Information about a cover or interlock. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.6.1.1.1,Printer-MIB::prtCoverIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this Cover sub unit. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new cover sub-units to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.6.1.1.2,Printer-MIB::prtCoverDescription,OCTET,read-only,,current,,The manufacturer provided cover sub-mechanism name in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.6.1.1.3,Printer-MIB::prtCoverStatus,INTEGER,read-only,,current,other(1):unknown(2):coverOpen(3):coverClosed(4):interlockOpen(5):interlockClosed(6),The status of this cover sub-unit.
.1.3.6.1.2.1.43.7,Printer-MIB::prtLocalization,,,,,,
.1.3.6.1.2.1.43.7.1,Printer-MIB::prtLocalizationTable,,not-accessible,,current,,The available localizations in this printer.
.1.3.6.1.2.1.43.7.1.1,Printer-MIB::prtLocalizationEntry,,not-accessible,hrDeviceIndex:prtLocalizationIndex,current,,A description of a localization. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.7.1.1.1,Printer-MIB::prtLocalizationIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this localization entry. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new localization data to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.7.1.1.2,Printer-MIB::prtLocalizationLanguage,OCTET,read-only,,current,,A two character language code from ISO 639. Examples en, es, fr, de. NOTE: These examples were shown as upper case in RFC 1759 and are now shown as lower case to agree with ISO 639.
.1.3.6.1.2.1.43.7.1.1.3,Printer-MIB::prtLocalizationCountry,OCTET,read-only,,current,,A two character country code from ISO 3166, a blank string (two space characters) shall indicate that the country is not defined. Examples: US, GB, FR, DE, ...
.1.3.6.1.2.1.43.7.1.1.4,Printer-MIB::prtLocalizationCharacterSet,INTEGER,read-only,,current,other(1):unknown(2):csASCII(3):csISOLatin1(4):csISOLatin2(5):csISOLatin3(6):csISOLatin4(7):csISOLatinCyrillic(8):csISOLatinArabic(9):csISOLatinGreek(10):csISOLatinHebrew(11):csISOLatin5(12):csISOLatin6(13):csISOTextComm(14):csHalfWidthKatakana(15):csJISEncoding(16):csShiftJIS(17):csEUCPkdFmtJapanese(18):csEUCFixWidJapanese(19):csISO4UnitedKingdom(20):csISO11SwedishForNames(21):csISO15Italian(22):csISO17Spanish(23):csISO21German(24):csISO60DanishNorwegian(25):csISO69French(26):csISO10646UTF1(27):csISO646basic1983(28):csINVARIANT(29):csISO2IntlRefVersion(30):csNATSSEFI(31):csNATSSEFIADD(32):csNATSDANO(33):csNATSDANOADD(34):csISO10Swedish(35):csKSC56011987(36):csISO2022KR(37):csEUCKR(38):csISO2022JP(39):csISO2022JP2(40):csISO13JISC6220jp(41):csISO14JISC6220ro(42):csISO16Portuguese(43):csISO18Greek7Old(44):csISO19LatinGreek(45):csISO25French(46):csISO27LatinGreek1(47):csISO5427Cyrillic(48):csISO42JISC62261978(49):csISO47BSViewdata(50):csISO49INIS(51):csISO50INIS8(52):csISO51INISCyrillic(53):csISO54271981(54):csISO5428Greek(55):csISO57GB1988(56):csISO58GB231280(57):csISO61Norwegian2(58):csISO70VideotexSupp1(59):csISO84Portuguese2(60):csISO85Spanish2(61):csISO86Hungarian(62):csISO87JISX0208(63):csISO88Greek7(64):csISO89ASMO449(65):csISO90(66):csISO91JISC62291984a(67):csISO92JISC62991984b(68):csISO93JIS62291984badd(69):csISO94JIS62291984hand(70):csISO95JIS62291984handadd(71):csISO96JISC62291984kana(72):csISO2033(73):csISO99NAPLPS(74):csISO102T617bit(75):csISO103T618bit(76):csISO111ECMACyrillic(77):csa71(78):csa72(79):csISO123CSAZ24341985gr(80):csISO88596E(81):csISO88596I(82):csISO128T101G2(83):csISO88598E(84):csISO88598I(85):csISO139CSN369103(86):csISO141JUSIB1002(87):csISO143IECP271(88):csISO146Serbian(89):csISO147Macedonian(90):csISO150(91):csISO151Cuba(92):csISO6937Add(93):csISO153GOST1976874(94):csISO8859Supp(95):csISO10367Box(96):csISO158Lap(97):csISO159JISX02121990(98):csISO646Danish(99):csUSDK(100):csDKUS(101):csKSC5636(102):csUnicode11UTF7(103):csISO2022CN(104):csISO2022CNEXT(105):csUTF8(106):csISO885913(109):csISO885914(110):csISO885915(111):csISO885916(112):csGBK(113):csGB18030(114):csOSDEBCDICDF0415(115):csOSDEBCDICDF03IRV(116):csOSDEBCDICDF041(117):csISO115481(118):csKZ1048(119):csUnicode(1000):csUCS4(1001):csUnicodeASCII(1002):csUnicodeLatin1(1003):csUnicodeJapanese(1004):csUnicodeIBM1261(1005):csUnicodeIBM1268(1006):csUnicodeIBM1276(1007):csUnicodeIBM1264(1008):csUnicodeIBM1265(1009):csUnicode11(1010):csSCSU(1011):csUTF7(1012):csUTF16BE(1013):csUTF16LE(1014):csUTF16(1015):csCESU8(1016):csUTF32(1017):csUTF32BE(1018):csUTF32LE(1019):csBOCU1(1020):csWindows30Latin1(2000):csWindows31Latin1(2001):csWindows31Latin2(2002):csWindows31Latin5(2003):csHPRoman8(2004):csAdobeStandardEncoding(2005):csVenturaUS(2006):csVenturaInternational(2007):csDECMCS(2008):csPC850Multilingual(2009):csPCp852(2010):csPC8CodePage437(2011):csPC8DanishNorwegian(2012):csPC862LatinHebrew(2013):csPC8Turkish(2014):csIBMSymbols(2015):csIBMThai(2016):csHPLegal(2017):csHPPiFont(2018):csHPMath8(2019):csHPPSMath(2020):csHPDesktop(2021):csVenturaMath(2022):csMicrosoftPublishing(2023):csWindows31J(2024):csGB2312(2025):csBig5(2026):csMacintosh(2027):csIBM037(2028):csIBM038(2029):csIBM273(2030):csIBM274(2031):csIBM275(2032):csIBM277(2033):csIBM278(2034):csIBM280(2035):csIBM281(2036):csIBM284(2037):csIBM285(2038):csIBM290(2039):csIBM297(2040):csIBM420(2041):csIBM423(2042):csIBM424(2043):csIBM500(2044):csIBM851(2045):csIBM855(2046):csIBM857(2047):csIBM860(2048):csIBM861(2049):csIBM863(2050):csIBM864(2051):csIBM865(2052):csIBM868(2053):csIBM869(2054):csIBM870(2055):csIBM871(2056):csIBM880(2057):csIBM891(2058):csIBM903(2059):csIBBM904(2060):csIBM905(2061):csIBM918(2062):csIBM1026(2063):csIBMEBCDICATDE(2064):csEBCDICATDEA(2065):csEBCDICCAFR(2066):csEBCDICDKNO(2067):csEBCDICDKNOA(2068):csEBCDICFISE(2069):csEBCDICFISEA(2070):csEBCDICFR(2071):csEBCDICIT(2072):csEBCDICPT(2073):csEBCDICES(2074):csEBCDICESA(2075):csEBCDICESS(2076):csEBCDICUK(2077):csEBCDICUS(2078):csUnknown8BiT(2079):csMnemonic(2080):csMnem(2081):csVISCII(2082):csVIQR(2083):csKOI8R(2084):csHZGB2312(2085):csIBM866(2086):csPC775Baltic(2087):csKOI8U(2088):csIBM00858(2089):csIBM00924(2090):csIBM01140(2091):csIBM01141(2092):csIBM01142(2093):csIBM01143(2094):csIBM01144(2095):csIBM01145(2096):csIBM01146(2097):csIBM01147(2098):csIBM01148(2099):csIBM01149(2100):csBig5HKSCS(2101):csIBM1047(2102):csPTCP154(2103):csAmiga1251(2104):csKOI7switched(2105):csBRF(2106):csTSCII(2107):csCP51932(2108):cswindows874(2109):cswindows1250(2250):cswindows1251(2251):cswindows1252(2252):cswindows1253(2253):cswindows1254(2254):cswindows1255(2255):cswindows1256(2256):cswindows1257(2257):cswindows1258(2258):csTIS620(2259):cs50220(2260):reserved(3000),The coded character set used for this localization.
.1.3.6.1.2.1.43.8,Printer-MIB::prtInput,,,,,,
.1.3.6.1.2.1.43.8.2,Printer-MIB::prtInputTable,,not-accessible,,current,,A table of the devices capable of providing media for input to the printing process.
.1.3.6.1.2.1.43.8.2.1,Printer-MIB::prtInputEntry,,not-accessible,hrDeviceIndex:prtInputIndex,current,,Attributes of a device capable of providing media for input to the printing process. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.8.2.1.1,Printer-MIB::prtInputIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this input sub-unit. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new input sub-units to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.8.2.1.2,Printer-MIB::prtInputType,INTEGER,read-only,,current,other(1):unknown(2):sheetFeedAutoRemovableTray(3):sheetFeedAutoNonRemovableTray(4):sheetFeedManual(5):continuousRoll(6):continuousFanFold(7):sheetFeedPull(8),The type of technology (discriminated primarily according to feeder mechanism type) employed by the input sub-unit. Note, the Input Class provides for a descriptor field to further qualify the other choice.
.1.3.6.1.2.1.43.8.2.1.3,Printer-MIB::prtInputDimUnit,INTEGER,read-only,,current,tenThousandthsOfInches(3):micrometers(4),The unit of measurement for use calculating and relaying dimensional values for this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.4,Printer-MIB::prtInputMediaDimFeedDirDeclared,Integer32,read-write,,current,,This object provides the value of the declared dimension, in the feed direction, of the media that is (or, if empty, was or will be) in this input sub-unit. The feed direction is the direction in which the media is fed on this sub-unit. This dimension is measured in input sub-unit dimensional units (controlled by prtInputDimUnit, which uses PrtMediaUnitTC). If this input sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed by management requests. Otherwise, the value may be changed. The value (-1) means other and specifically means that this sub-unit places no restriction on this parameter. The value (-2) indicates unknown.
.1.3.6.1.2.1.43.8.2.1.5,Printer-MIB::prtInputMediaDimXFeedDirDeclared,Integer32,read-write,,current,,This object provides the value of the declared dimension, in the cross feed direction, of the media that is (or, if empty, was or will be) in this input sub-unit. The cross feed direction is ninety degrees relative to the feed direction associated with this sub-unit. This dimension is measured in input sub-unit dimensional units (controlled by prtInputDimUnit,which uses PrtMediaUnitTC). If this input sub- unit can reliably sense this value, the value is sensed by the printer and may not be changed by management requests. Otherwise, the value may be changed. The value (-1) means other and specifically means that this sub-unit places no restriction on this parameter. The value (-2) indicates unknown.
.1.3.6.1.2.1.43.8.2.1.6,Printer-MIB::prtInputMediaDimFeedDirChosen,Integer32,read-only,,current,,The printer will act as if media of the chosen dimension (in the feed direction) is present in this input source. Note that this value will be used even if the input tray is empty. Feed dimension measurements are taken relative to the feed direction associated with that sub-unit and are in input sub-unit dimensional units (controlled by prtInputDimUnit, which uses PrtMediaUnitTC). If the printer supports the declared dimension,the granted dimension is the same as the declared dimension. If not, the granted dimension is set to the closest dimension that the printer supports when the declared dimension is set. The value (-1) means other and specifically indicates that this sub-unit places no restriction on this parameter. The value (-2)indicates unknown.
.1.3.6.1.2.1.43.8.2.1.7,Printer-MIB::prtInputMediaDimXFeedDirChosen,Integer32,read-only,,current,,The printer will act as if media of the chosen dimension (in the cross feed direction) is present in this input source. Note that this value will be used even if the input tray is empty. The cross feed direction is ninety degrees relative to the feed direction associated with this sub-unit. This dimension is measured in input sub-unit dimensional units (controlled by prtInputDimUnit, which uses PrtMediaUnitTC). If the printer supports the declare dimension, the granted dimension is the same as the declared dimension. If not, the granted dimension is set to the closest dimension that the printer supports when the declared dimension is set. The value (-1) means other and specifically indicates that this sub-unit places no restriction on this parameter. The value (-2) indicates unknown.
.1.3.6.1.2.1.43.8.2.1.8,Printer-MIB::prtInputCapacityUnit,INTEGER,read-only,,current,other(1):unknown(2):tenThousandthsOfInches(3):micrometers(4):sheets(8):feet(16):meters(17):items(18):percent(19),The unit of measurement for use in calculating and relaying capacity values for this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.9,Printer-MIB::prtInputMaxCapacity,Integer32,read-write,,current,,The maximum capacity of the input sub-unit in input sub-unit capacity units (PrtCapacityUnitTC). There is no convention associated with the media itself so this value reflects claimed capacity. If this input sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed by management requests; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.8.2.1.10,Printer-MIB::prtInputCurrentLevel,Integer32,read-write,,current,,The current capacity of the input sub-unit in input sub-unit capacity units (PrtCapacityUnitTC). If this input sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed by management requests; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. The value (-3) means that the printer knows that at least one unit remains.
.1.3.6.1.2.1.43.8.2.1.11,Printer-MIB::prtInputStatus,INTEGER,read-only,,current,,The current status of this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.12,Printer-MIB::prtInputMediaName,OCTET,read-write,,current,,A description of the media contained in this input sub-unit; This description is to be used by a client to format and Localize a string for display to a human operator. This description is not processed by the printer. It is used to provide information not expressible in terms of the other media attributes (e.g., prtInputMediaDimFeedDirChosen, prtInputMediaDimXFeedDirChosen, prtInputMediaWeight, prtInputMediaType).
.1.3.6.1.2.1.43.8.2.1.13,Printer-MIB::prtInputName,OCTET,read-write,,current,,The name assigned to this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.14,Printer-MIB::prtInputVendorName,OCTET,read-only,,current,,The vendor name of this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.15,Printer-MIB::prtInputModel,OCTET,read-only,,current,,The model name of this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.16,Printer-MIB::prtInputVersion,OCTET,read-only,,current,,The version of this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.17,Printer-MIB::prtInputSerialNumber,OCTET,read-only,,current,,The serial number assigned to this input sub-unit.
.1.3.6.1.2.1.43.8.2.1.18,Printer-MIB::prtInputDescription,OCTET,read-only,,current,,A free-form text description of this input sub-unit in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.8.2.1.19,Printer-MIB::prtInputSecurity,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),Indicates if this input sub-unit has some security associated with it.
.1.3.6.1.2.1.43.8.2.1.20,Printer-MIB::prtInputMediaWeight,Integer32,read-write,,current,,The weight of the medium associated with this input sub-unit in grams / per meter squared. The value (-2) means unknown.
.1.3.6.1.2.1.43.8.2.1.21,Printer-MIB::prtInputMediaType,OCTET,read-write,,current,,The name of the type of medium associated with this input sub unit. This name need not be processed by the printer; it might simply be displayed to an operator. NOTE: The above description has been modified from RFC 1759.
.1.3.6.1.2.1.43.8.2.1.22,Printer-MIB::prtInputMediaColor,OCTET,read-write,,current,,The name of the color of the medium associated with this input sub-unit using standardized string values. NOTE: The above description has been modified from RFC 1759.
.1.3.6.1.2.1.43.8.2.1.23,Printer-MIB::prtInputMediaFormParts,Integer32,read-write,,current,,The number of parts associated with the medium associated with this input sub-unit if the medium is a multi-part form. The value (-1) means other and specifically indicates that the device places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.8.2.1.24,Printer-MIB::prtInputMediaLoadTimeout,Integer32,read-write,,current,,When the printer is not able to print due to a subunit being empty or the requested media must be manually loaded, the printer will wait for the duration (in seconds) specified by this object. Upon expiration of the time-out, the printer will take the action specified by prtInputNextIndex. The event which causes the printer to enter the waiting state is product specific. If the printer is not waiting for manually fed media, it may switch from an empty subunit to a different subunit without waiting for the time-out to expire. A value of (-1) implies 'other' or 'infinite' which translates to 'wait forever'. The action which causes printing to continue is product specific. A value of (-2) implies 'unknown'.
.1.3.6.1.2.1.43.8.2.1.25,Printer-MIB::prtInputNextIndex,Integer32,read-write,,current,,The value of prtInputIndex corresponding to the input subunit which will be used when this input subunit is emptied and the time-out specified by prtInputMediaLoadTimeout expires. A value of zero(0) indicates that auto input switching will not occur when this input subunit is emptied. If the time-out specified by prtInputLoadMediaTimeout expires and this value is zero(0), the job will be aborted. A value of (-1) means other. The value (-2)means 'unknown' and specifically indicates that an implementation specific method will determine the next input subunit to use at the time this subunit is emptied and the time out expires. The value(-3) means input switching is not supported for this subunit.
.1.3.6.1.2.1.43.9,Printer-MIB::prtOutput,,,,,,
.1.3.6.1.2.1.43.9.2,Printer-MIB::prtOutputTable,,not-accessible,,current,,A table of the devices capable of receiving media delivered from the printing process.
.1.3.6.1.2.1.43.9.2.1,Printer-MIB::prtOutputEntry,,not-accessible,hrDeviceIndex:prtOutputIndex,current,,Attributes of a device capable of receiving media delivered from the printing process. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.9.2.1.1,Printer-MIB::prtOutputIndex,Integer32,not-accessible,,current,,A unique value used by this printer to identify this output sub-unit. Although these values may change due to a major reconfiguration of the sub-unit (e.g., the addition of new output devices to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.9.2.1.2,Printer-MIB::prtOutputType,INTEGER,read-only,,current,other(1):unknown(2):removableBin(3):unRemovableBin(4):continuousRollDevice(5):mailBox(6):continuousFanFold(7),The type of technology supported by this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.3,Printer-MIB::prtOutputCapacityUnit,INTEGER,read-only,,current,other(1):unknown(2):tenThousandthsOfInches(3):micrometers(4):sheets(8):feet(16):meters(17):items(18):percent(19),The unit of measurement for use in calculating and relaying capacity values for this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.4,Printer-MIB::prtOutputMaxCapacity,Integer32,read-write,,current,,The maximum capacity of this output sub-unit in output sub- unit capacity units (PrtCapacityUnitTC). There is no convention associated with the media itself so this value essentially reflects claimed capacity. If this output sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed by management requests; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.9.2.1.5,Printer-MIB::prtOutputRemainingCapacity,Integer32,read-write,,current,,The remaining capacity of the possible output sub-unit capacity in output sub-unit capacity units (PrtCapacityUnitTC)of this output sub-unit. If this output sub- unit can reliably sense this value, the value is sensed by the printer and may not be modified by management requests; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. The value (-3) means that the printer knows that there remains capacity for at least one unit.
.1.3.6.1.2.1.43.9.2.1.6,Printer-MIB::prtOutputStatus,INTEGER,read-only,,current,,The current status of this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.7,Printer-MIB::prtOutputName,OCTET,read-write,,current,,The name assigned to this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.8,Printer-MIB::prtOutputVendorName,OCTET,read-only,,current,,The vendor name of this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.9,Printer-MIB::prtOutputModel,OCTET,read-only,,current,,The model name assigned to this output sub-unit. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.9.2.1.10,Printer-MIB::prtOutputVersion,OCTET,read-only,,current,,The version of this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.11,Printer-MIB::prtOutputSerialNumber,OCTET,read-only,,current,,The serial number assigned to this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.12,Printer-MIB::prtOutputDescription,OCTET,read-only,,current,,A free-form text description of this output sub-unit in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.9.2.1.13,Printer-MIB::prtOutputSecurity,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),Indicates if this output sub-unit has some security associated with it and if that security is enabled or not.
.1.3.6.1.2.1.43.9.2.1.14,Printer-MIB::prtOutputDimUnit,INTEGER,read-only,,current,tenThousandthsOfInches(3):micrometers(4),The unit of measurement for use in calculating and relaying dimensional values for this output sub-unit.
.1.3.6.1.2.1.43.9.2.1.15,Printer-MIB::prtOutputMaxDimFeedDir,Integer32,read-write,,current,,The maximum dimensions supported by this output sub-unit for measurements taken parallel relative to the feed direction associated with that sub-unit in output sub-unit dimensional units (controlled by prtOutputDimUnit, which uses PrtMediaUnitTC). If this output sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed with management protocol operations. The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. NOTE: The above description has been modified from RFC 1759 for clarification and to explain the purpose of (-1) and (-2).
.1.3.6.1.2.1.43.9.2.1.16,Printer-MIB::prtOutputMaxDimXFeedDir,Integer32,read-write,,current,,The maximum dimensions supported by this output sub-unit for measurements taken ninety degrees relative to the feed direction associated with that sub-unit in output sub-unit dimensional units (controlled by prtOutputDimUnit, which uses PrtMediaUnitTC). If this output sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed with management protocol operations. The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. NOTE: The above description has been modified from RFC 1759 for clarification and to explain the purpose of (-1) and (-2).
.1.3.6.1.2.1.43.9.2.1.17,Printer-MIB::prtOutputMinDimFeedDir,Integer32,read-write,,current,,The minimum dimensions supported by this output sub-unit for measurements taken parallel relative to the feed direction associated with that sub-unit in output sub-unit dimensional units (controlled by prtOutputDimUnit, which uses PrtMediaUnitTC). If this output sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed with management protocol operations. The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. NOTE: The above description has been modified from RFC 1759 for clarification and to explain the purpose of (-1) and (-2).
.1.3.6.1.2.1.43.9.2.1.18,Printer-MIB::prtOutputMinDimXFeedDir,Integer32,read-write,,current,,The minimum dimensions supported by this output sub-unit for measurements taken ninety degrees relative to the feed direction associated with that sub-unit in output sub-unit dimensional units (controlled by prtOutputDimUnit, which uses PrtMediaUnitTC). If this output sub-unit can reliably sense this value, the value is sensed by the printer and may not be changed with management protocol operations. The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. NOTE: The above description has been modified from RFC 1759 for clarification and to explain the purpose of (-1) and (-2).
.1.3.6.1.2.1.43.9.2.1.19,Printer-MIB::prtOutputStackingOrder,INTEGER,read-write,,current,unknown(2):firstToLast(3):lastToFirst(4),The current state of the stacking order for the associated output sub-unit. 'FirstToLast' means that as pages are output the front of the next page is placed against the back of the previous page. 'LasttoFirst' means that as pages are output the back of the next page is placed against the front of the previous page.
.1.3.6.1.2.1.43.9.2.1.20,Printer-MIB::prtOutputPageDeliveryOrientation,INTEGER,read-write,,current,faceUp(3):faceDown(4),The reading surface that will be 'up' when pages are delivered to the associated output sub-unit. Values are faceUp and faceDown. (Note: interpretation of these values is in general context-dependent based on locale; presentation of these values to an end-user should be normalized to the expectations of the user).
.1.3.6.1.2.1.43.9.2.1.21,Printer-MIB::prtOutputBursting,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),This object indicates that the outputting sub-unit supports bursting, and if so, whether the feature is enabled. Bursting is the process by which continuous media is separated into individual sheets, typically by bursting along pre-formed perforations.
.1.3.6.1.2.1.43.9.2.1.22,Printer-MIB::prtOutputDecollating,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),This object indicates that the output supports decollating, and if so, whether the feature is enabled. Decollating is the process by which the individual parts within a multi-part form are separated and sorted into separate stacks for each part.
.1.3.6.1.2.1.43.9.2.1.23,Printer-MIB::prtOutputPageCollated,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),This object indicates that the output sub-unit supports page collation, and if so, whether the feature is enabled. See RFC 3805 Appendix A, Glossary Of Terms, for definition of how this document defines collation. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.9.2.1.24,Printer-MIB::prtOutputOffsetStacking,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),This object indicates that the output supports offset stacking,and if so, whether the feature is enabled. See RFC 3805 Appendix A, Glossary Of Terms, for how Offset Stacking is defined by this document. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10,Printer-MIB::prtMarker,,,,,,
.1.3.6.1.2.1.43.10.2,Printer-MIB::prtMarkerTable,,not-accessible,,current,,The marker table provides a description of each marker sub-unit contained within the printer. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1,Printer-MIB::prtMarkerEntry,,not-accessible,hrDeviceIndex:prtMarkerIndex,current,,Entries in this table define the characteristics and status of each marker sub-unit in the printer. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.1,Printer-MIB::prtMarkerIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this marking SubUnit. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new marking sub-units to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.2,Printer-MIB::prtMarkerMarkTech,INTEGER,read-only,,current,other(1):unknown(2):electrophotographicLED(3):electrophotographicLaser(4):electrophotographicOther(5):impactMovingHeadDotMatrix9pin(6):impactMovingHeadDotMatrix24pin(7):impactMovingHeadDotMatrixOther(8):impactMovingHeadFullyFormed(9):impactBand(10):impactOther(11):inkjetAqueous(12):inkjetSolid(13):inkjetOther(14):pen(15):thermalTransfer(16):thermalSensitive(17):thermalDiffusion(18):thermalOther(19):electroerosion(20):electrostatic(21):photographicMicrofiche(22):photographicImagesetter(23):photographicOther(24):ionDeposition(25):eBeam(26):typesetter(27),The type of marking technology used for this marking sub-unit.
.1.3.6.1.2.1.43.10.2.1.3,Printer-MIB::prtMarkerCounterUnit,INTEGER,read-only,,current,tenThousandthsOfInches(3):micrometers(4):characters(5):lines(6):impressions(7):sheets(8):dotRow(9):hours(11):feet(16):meters(17),The unit that will be used by the printer when reporting counter values for this marking sub-unit. The time units of measure are provided for a device like a strip recorder that does not or cannot track the physical dimensions of the media and does not use characters, lines or sheets.
.1.3.6.1.2.1.43.10.2.1.4,Printer-MIB::prtMarkerLifeCount,Counter32,read-only,,current,,The count of the number of units of measure counted during the life of printer using units of measure as specified by prtMarkerCounterUnit. Note: This object should be implemented as a persistent object with a reliable value throughout the lifetime of the printer.
.1.3.6.1.2.1.43.10.2.1.5,Printer-MIB::prtMarkerPowerOnCount,Counter32,read-only,,current,,The count of the number of units of measure counted since the equipment was most recently powered on using units of measure as specified by prtMarkerCounterUnit.
.1.3.6.1.2.1.43.10.2.1.6,Printer-MIB::prtMarkerProcessColorants,Integer32,read-only,,current,,The number of process colors supported by this marker. A process color of 1 implies monochrome. The value of this object and prtMarkerSpotColorants cannot both be 0. The value of prtMarkerProcessColorants must be 0 or greater. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.7,Printer-MIB::prtMarkerSpotColorants,Integer32,read-only,,current,,The number of spot colors supported by this marker. The value of this object and prtMarkerProcessColorants cannot both be 0. Must be 0 or greater. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.8,Printer-MIB::prtMarkerAddressabilityUnit,INTEGER,read-only,,current,tenThousandthsOfInches(3):micrometers(4),The unit of measure of distances, as applied to the marker's resolution. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.9,Printer-MIB::prtMarkerAddressabilityFeedDir,Integer32,read-only,,current,,The maximum number of addressable marking positions in the feed direction per 10000 units of measure specified by prtMarkerAddressabilityUnit. A value of (-1) implies 'other' or 'infinite' while a value of (-2) implies 'unknown'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.10,Printer-MIB::prtMarkerAddressabilityXFeedDir,Integer32,read-only,,current,,The maximum number of addressable marking positions in the cross feed direction in 10000 units of measure specified by prtMarkerAddressabilityUnit. A value of (-1) implies 'other' or 'infinite' while a value of (-2) implies 'unknown'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.10.2.1.11,Printer-MIB::prtMarkerNorthMargin,Integer32,read-only,,current,,The margin, in units identified by prtMarkerAddressabilityUnit, from the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the observer. Printing within the area bounded by all four margins is guaranteed for all interpreters. The value (-2) means unknown.
.1.3.6.1.2.1.43.10.2.1.12,Printer-MIB::prtMarkerSouthMargin,Integer32,read-only,,current,,The margin from the South edge (see prtMarkerNorthMargin) of the medium in units identified by prtMarkerAddressabilityUnit. Printing within the area bounded by all four margins is guaranteed for all interpreters. The value (-2) means unknown.
.1.3.6.1.2.1.43.10.2.1.13,Printer-MIB::prtMarkerWestMargin,Integer32,read-only,,current,,The margin from the West edge (see prtMarkerNorthMargin) of the medium in units identified by prtMarkerAddressabilityUnit. Printing within the area bounded by all four margins is guaranteed for all interpreters. The value (-2) means unknown.
.1.3.6.1.2.1.43.10.2.1.14,Printer-MIB::prtMarkerEastMargin,Integer32,read-only,,current,,The margin from the East edge (see prtMarkerNorthMargin) of the medium in units identified by prtMarkerAddressabilityUnit. Printing within the area bounded by all four margins is guaranteed for all interpreters. The value (-2) means unknown.
.1.3.6.1.2.1.43.10.2.1.15,Printer-MIB::prtMarkerStatus,INTEGER,read-only,,current,,The current status of this marker sub-unit.
.1.3.6.1.2.1.43.11,Printer-MIB::prtMarkerSupplies,,,,,,
.1.3.6.1.2.1.43.11.1,Printer-MIB::prtMarkerSuppliesTable,,not-accessible,,current,,A table of the marker supplies available on this printer.
.1.3.6.1.2.1.43.11.1.1,Printer-MIB::prtMarkerSuppliesEntry,,not-accessible,hrDeviceIndex:prtMarkerSuppliesIndex,current,,Attributes of a marker supply. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.11.1.1.1,Printer-MIB::prtMarkerSuppliesIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this marker supply. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new marker supplies to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.11.1.1.2,Printer-MIB::prtMarkerSuppliesMarkerIndex,Integer32,read-only,,current,,The value of prtMarkerIndex corresponding to the marking sub unit with which this marker supply sub-unit is associated.
.1.3.6.1.2.1.43.11.1.1.3,Printer-MIB::prtMarkerSuppliesColorantIndex,Integer32,read-only,,current,,The value of prtMarkerColorantIndex corresponding to the colorant with which this marker supply sub-unit is associated. This value shall be 0 if there is no colorant table or if this supply does not depend on a single specified colorant. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.11.1.1.4,Printer-MIB::prtMarkerSuppliesClass,INTEGER,read-only,,current,other(1):supplyThatIsConsumed(3):receptacleThatIsFilled(4),Indicates whether this supply entity represents a supply that is consumed or a receptacle that is filled. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.11.1.1.5,Printer-MIB::prtMarkerSuppliesType,INTEGER,read-only,,current,other(1):unknown(2):toner(3):wasteToner(4):ink(5):inkCartridge(6):inkRibbon(7):wasteInk(8):opc(9):developer(10):fuserOil(11):solidWax(12):ribbonWax(13):wasteWax(14):fuser(15):coronaWire(16):fuserOilWick(17):cleanerUnit(18):fuserCleaningPad(19):transferUnit(20):tonerCartridge(21):fuserOiler(22):water(23):wasteWater(24):glueWaterAdditive(25):wastePaper(26):bindingSupply(27):bandingSupply(28):stitchingWire(29):shrinkWrap(30):paperWrap(31):staples(32):inserts(33):covers(34):matteToner(35):matteInk(36),The type of this supply.
.1.3.6.1.2.1.43.11.1.1.6,Printer-MIB::prtMarkerSuppliesDescription,OCTET,read-only,,current,,The description of this supply container/receptacle in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.11.1.1.7,Printer-MIB::prtMarkerSuppliesSupplyUnit,INTEGER,read-only,,current,other(1):unknown(2):tenThousandthsOfInches(3):micrometers(4):impressions(7):sheets(8):hours(11):thousandthsOfOunces(12):tenthsOfGrams(13):hundrethsOfFluidOunces(14):tenthsOfMilliliters(15):feet(16):meters(17):items(18):percent(19),Unit of measure of this marker supply container/receptacle. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.11.1.1.8,Printer-MIB::prtMarkerSuppliesMaxCapacity,Integer32,read-write,,current,,The maximum capacity of this supply container/receptacle expressed in prtMarkerSuppliesSupplyUnit. If this supply container/receptacle can reliably sense this value, the value is reported by the printer and is read-only; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.11.1.1.9,Printer-MIB::prtMarkerSuppliesLevel,Integer32,read-write,,current,,The current level if this supply is a container; the remaining space if this supply is a receptacle. If this supply container/receptacle can reliably sense this value, the value is reported by the printer and is read-only; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. A value of (-3) means that the printer knows that there is some supply/remaining space, respectively.
.1.3.6.1.2.1.43.12,Printer-MIB::prtMarkerColorant,,,,,,
.1.3.6.1.2.1.43.12.1,Printer-MIB::prtMarkerColorantTable,,not-accessible,,current,,A table of all of the colorants available on the printer.
.1.3.6.1.2.1.43.12.1.1,Printer-MIB::prtMarkerColorantEntry,,not-accessible,hrDeviceIndex:prtMarkerColorantIndex,current,,Attributes of a colorant available on the printer. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.12.1.1.1,Printer-MIB::prtMarkerColorantIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this colorant. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new colorants to the printer) , values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.12.1.1.2,Printer-MIB::prtMarkerColorantMarkerIndex,Integer32,read-only,,current,,The value of prtMarkerIndex corresponding to the marker sub unit with which this colorant entry is associated.
.1.3.6.1.2.1.43.12.1.1.3,Printer-MIB::prtMarkerColorantRole,INTEGER,read-only,,current,other(1):process(3):spot(4),The role played by this colorant.
.1.3.6.1.2.1.43.12.1.1.4,Printer-MIB::prtMarkerColorantValue,OCTET,read-only,,current,,The name of the color of this colorant using standardized string names from ISO 10175 (DPA) and ISO 10180 (SPDL) such as: other unknown white red green blue cyan magenta yellow black Implementers may add additional string values. The naming conventions in ISO 9070 are recommended in order to avoid potential name clashes
.1.3.6.1.2.1.43.12.1.1.5,Printer-MIB::prtMarkerColorantTonality,Integer32,read-only,,current,,The distinct levels of tonality realizable by a marking sub unit when using this colorant. This value does not include the number of levels of tonal difference that an interpreter can obtain by techniques such as half toning. This value must be at least 2.
.1.3.6.1.2.1.43.13,Printer-MIB::prtMediaPath,,,,,,
.1.3.6.1.2.1.43.13.4,Printer-MIB::prtMediaPathTable,,not-accessible,,current,,The media path table includes both physical and logical paths within the printer. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1,Printer-MIB::prtMediaPathEntry,,not-accessible,hrDeviceIndex:prtMediaPathIndex,current,,Entries may exist in the table for each device index with a device type of 'printer' Each entry defines the physical characteristics of and the status of the media path. The data provided indicates the maximum throughput and the media size limitations of these subunits. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1.1,Printer-MIB::prtMediaPathIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this media path. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new media paths to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1.2,Printer-MIB::prtMediaPathMaxSpeedPrintUnit,INTEGER,read-only,,current,tenThousandthsOfInchesPerHour(3):micrometersPerHour(4):charactersPerHour(5):linesPerHour(6):impressionsPerHour(7):sheetsPerHour(8):dotRowPerHour(9):feetPerHour(16):metersPerHour(17),The unit of measure used in specifying the speed of all media paths in the printer.
.1.3.6.1.2.1.43.13.4.1.3,Printer-MIB::prtMediaPathMediaSizeUnit,INTEGER,read-only,,current,tenThousandthsOfInches(3):micrometers(4),The units of measure of media size for use in calculating and relaying dimensional values for all media paths in the printer.
.1.3.6.1.2.1.43.13.4.1.4,Printer-MIB::prtMediaPathMaxSpeed,Integer32,read-only,,current,,The maximum printing speed of this media path expressed in prtMediaPathMaxSpeedUnit's. A value of (-1) implies 'other'.
.1.3.6.1.2.1.43.13.4.1.5,Printer-MIB::prtMediaPathMaxMediaFeedDir,Integer32,read-only,,current,,The maximum physical media size in the feed direction of this media path expressed in units of measure specified by PrtMediaPathMediaSizeUnit. A value of (-1) implies 'unlimited' a value of (-2) implies 'unknown'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1.6,Printer-MIB::prtMediaPathMaxMediaXFeedDir,Integer32,read-only,,current,,The maximum physical media size across the feed direction of this media path expressed in units of measure specified by prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1.7,Printer-MIB::prtMediaPathMinMediaFeedDir,Integer32,read-only,,current,,The minimum physical media size in the feed direction of this media path expressed in units of measure specified by prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1.8,Printer-MIB::prtMediaPathMinMediaXFeedDir,Integer32,read-only,,current,,The minimum physical media size across the feed direction of this media path expressed in units of measure specified by prtMediaPathMediaSizeUnit. A value of (-2) implies 'unknown'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.13.4.1.9,Printer-MIB::prtMediaPathType,INTEGER,read-only,,current,other(1):unknown(2):longEdgeBindingDuplex(3):shortEdgeBindingDuplex(4):simplex(5),The type of the media path for this media path.
.1.3.6.1.2.1.43.13.4.1.10,Printer-MIB::prtMediaPathDescription,OCTET,read-only,,current,,The manufacturer-provided description of this media path in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.13.4.1.11,Printer-MIB::prtMediaPathStatus,INTEGER,read-only,,current,,The current status of this media path.
.1.3.6.1.2.1.43.14,Printer-MIB::prtChannel,,,,,,
.1.3.6.1.2.1.43.14.1,Printer-MIB::prtChannelTable,,not-accessible,,current,,The channel table represents the set of input data sources which can provide print data to one or more of the interpreters available on a printer. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.14.1.1,Printer-MIB::prtChannelEntry,,not-accessible,hrDeviceIndex:prtChannelIndex,current,,Entries may exist in the table for each device index with a device type of 'printer'. Each channel table entry is characterized by a unique protocol stack and/or addressing. The channel may also have printer dependent features that are associated with a printing language. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.14.1.1.1,Printer-MIB::prtChannelIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this data channel. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new data channels to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.14.1.1.2,Printer-MIB::prtChannelType,INTEGER,read-only,,current,other(1):unknown(2):chSerialPort(3):chParallelPort(4):chIEEE1284Port(5):chSCSIPort(6):chAppleTalkPAP(7):chLPDServer(8):chNetwareRPrinter(9):chNetwarePServer(10):chPort9100(11):chAppSocket(12):chFTP(13):chTFTP(14):chDLCLLCPort(15):chIBM3270(16):chIBM5250(17):chFax(18):chIEEE1394(19):chTransport1(20):chCPAP(21):chDCERemoteProcCall(22):chONCRemoteProcCall(23):chOLE(24):chNamedPipe(25):chPCPrint(26):chServerMessageBlock(27):chDPMF(28):chDLLAPI(29):chVxDAPI(30):chSystemObjectManager(31):chDECLAT(32):chNPAP(33):chUSB(34):chIRDA(35):chPrintXChange(36):chPortTCP(37):chBidirPortTCP(38):chUNPP(39):chAppleTalkADSP(40):chPortSPX(41):chPortHTTP(42):chNDPS(43):chIPP(44):chSMTP(45):chWSPrint(46),The type of this print data channel. This object provides the linkage to ChannelType-specific groups that may (conceptually) extend the prtChannelTable with additional details about that channel.
.1.3.6.1.2.1.43.14.1.1.3,Printer-MIB::prtChannelProtocolVersion,OCTET,read-only,,current,,The version of the protocol used on this channel. The format used for version numbering depends on prtChannelType.
.1.3.6.1.2.1.43.14.1.1.4,Printer-MIB::prtChannelCurrentJobCntlLangIndex,Integer32,read-write,,current,,The value of prtInterpreterIndex corresponding to the Control Language Interpreter for this channel. This interpreter defines the syntax used for control functions, such as querying or changing environment variables and identifying job boundaries (e.g., PJL, PostScript, NPAP). A value of zero indicates that there is no current Job Control Language Interpreter for this channel. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.14.1.1.5,Printer-MIB::prtChannelDefaultPageDescLangIndex,Integer32,read-write,,current,,The value of prtInterpreterIndex corresponding to the Page Description Language Interpreter for this channel. This interpreter defines the default Page Description Language interpreter to be used for the print data unless the Control Language is used to select a specific interpreter (e.g., PCL, PostScript Language, auto-sense). A value of zero indicates that there is no default page description language interpreter for this channel. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.14.1.1.6,Printer-MIB::prtChannelState,INTEGER,read-write,,current,other(1):printDataAccepted(3):noDataAccepted(4),The state of this print data channel. The value determines whether control information and print data is allowed through this channel or not.
.1.3.6.1.2.1.43.14.1.1.7,Printer-MIB::prtChannelIfIndex,Integer32,read-write,,current,,The value of ifIndex in the ifTable; see the Interfaces Group MIB [RFC2863] which corresponds to this channel. When more than one row of the ifTable is relevant, this is the index of the row representing the topmost layer in the interface hierarchy. A value of zero indicates that no interface is associated with this channel. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.14.1.1.8,Printer-MIB::prtChannelStatus,INTEGER,read-only,,current,,The current status of the channel.
.1.3.6.1.2.1.43.14.1.1.9,Printer-MIB::prtChannelInformation,OCTET,read-only,,current,,Auxiliary information to allow a printing application to use the channel for data submission to the printer. An application capable of using a specific PrtChannelType should be able to use the combined information from the prtChannelInformation and other channel and interface group objects to 'bootstrap' its use of the channel. prtChannelInformation is not intended to provide a general channel description, nor to provide information that is available once the channel is in use. The encoding and interpretation of the prtChannelInformation object is specific to channel type. The description of each PrtChannelType enum value for which prtChannelInformation is defined specifies the appropriate encoding and interpretation, including interaction with other objects. For channel types that do not specify a prtChannelInformation value, its value shall be null (0 length). When a new PrtChannelType enumeration value is registered, its accompanying description must specify the encoding and interpretation of the prtChannelInformation value for the channel type. prtChannelInformation semantics for an existing PrtChannelType may be added or amended in the same manner as described in section 2.4.1 for type 2 enumeration values. The prtChannelInformation specifies values for a collection of channel attributes, represented as text according to the following rules: 1. The prtChannelInformation is not affected by localization. 2. The prtChannelInformation is a list of entries representing the attribute values. Each entry consists of the following items, in order: a. A keyword, composed of alphabetic characters (A-Z, a-z) represented by their NVT ASCII [RFC854] codes, that identifies a channel attribute, b. The NVT ASCII code for an Equals Sign (=) (code 61) to delimit the keyword, c. A data value encoded using rules specific to the PrtChannelType to with the prtChannelInformation applies which must in no case allow an octet with value 10 (the NVT ASCII Line Feed code), d. the NVT ASCII code for a Line Feed character (code 10) to delimit the data value. No other octets shall be present. Keywords are case-sensitive. Conventionally, keywords are capitalized (including each word of a multi-word keyword) and since they occupy space in the prtChannelInformation, they are kept short. 3. If a channel attribute has multiple values, it is represented by multiple entries with the same keyword, each specifying one value. Otherwise, there shall be at most one entry for each attribute. 4. By default, entries may appear in any order. If there are ordering constraints for particular entries, these must be specified in their definitions. 5. The prtChannelInformation value by default consists of text represented by NVT ASCII graphics character codes. However, other representations may be specified: a. In cases where the prtChannelInformation value contains information not normally coded in textual form, whatever symbolic representation is conventionally used for the information should be used for encoding the prtChannelInformation value. (For instance, a binary port value might be represented as a decimal number using NVT ASCII codes.) Such encoding must be specified in the definition of the value. b. The value may contain textual information in a character set other than NVT ASCII graphics characters. (For instance, an identifier might consist of ISO 10646 text encoded using the UTF-8 encoding scheme.) Such a character set and its encoding must be specified in the definition of the value. 6. For each P
.1.3.6.1.2.1.43.15,Printer-MIB::prtInterpreter,,,,,,
.1.3.6.1.2.1.43.15.1,Printer-MIB::prtInterpreterTable,,not-accessible,,current,,The interpreter table is a table representing the interpreters in the printer. An entry shall be placed in the interpreter table for each interpreter on the printer. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.15.1.1,Printer-MIB::prtInterpreterEntry,,not-accessible,hrDeviceIndex:prtInterpreterIndex,current,,Entries may exist in the table for each device index with a device type of 'printer'. Each table entry provides a complete description of the interpreter, including version information, rendering resolutions, default character sets, output orientation, and communication capabilities. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.15.1.1.1,Printer-MIB::prtInterpreterIndex,Integer32,not-accessible,,current,,A unique value for each PDL or control language for which there exists an interpreter or emulator in the printer. The value is used to identify this interpreter. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new interpreters to the printer), values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.15.1.1.2,Printer-MIB::prtInterpreterLangFamily,INTEGER,read-only,,current,other(1):unknown(2):langPCL(3):langHPGL(4):langPJL(5):langPS(6):langIPDS(7):langPPDS(8):langEscapeP(9):langEpson(10):langDDIF(11):langInterpress(12):langISO6429(13):langLineData(14):langMODCA(15):langREGIS(16):langSCS(17):langSPDL(18):langTEK4014(19):langPDS(20):langIGP(21):langCodeV(22):langDSCDSE(23):langWPS(24):langLN03(25):langCCITT(26):langQUIC(27):langCPAP(28):langDecPPL(29):langSimpleText(30):langNPAP(31):langDOC(32):langimPress(33):langPinwriter(34):langNPDL(35):langNEC201PL(36):langAutomatic(37):langPages(38):langLIPS(39):langTIFF(40):langDiagnostic(41):langPSPrinter(42):langCaPSL(43):langEXCL(44):langLCDS(45):langXES(46):langPCLXL(47):langART(48):langTIPSI(49):langPrescribe(50):langLinePrinter(51):langIDP(52):langXJCL(53):langPDF(54):langRPDL(55):langIntermecIPL(56):langUBIFingerprint(57):langUBIDirectProtocol(58):langFujitsu(59):langCGM(60):langJPEG(61):langCALS1(62):langCALS2(63):langNIRS(64):langC4(65):langXPS(66):langOpenXPS(67):langJDF(68):langJMF(69):langPPML(70):langXHTMLPrint(71):langPDFis(72):langPDF13(73):langPDF14(74):langPDF15(75):langPDF16(76):langPDF17(77):langPS2(78):langPS3(79):langPCL3(80):langPCL3GUI(81):langPCL5e(82):langPCL5c(83):langPWGRaster(84):langAppleRaster(85),The family name of a Page Description Language (PDL) or control language which this interpreter in the printer can interpret or emulate. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.15.1.1.3,Printer-MIB::prtInterpreterLangLevel,OCTET,read-only,,current,,The level of the language which this interpreter is interpreting or emulating. This might contain a value like '5e'for an interpreter which is emulating level 5e of the PCL language. It might contain '2' for an interpreter which is emulating level 2 of the PostScript language. Similarly it might contain '2' for an interpreter which is emulating level 2 of the HPGL language.
.1.3.6.1.2.1.43.15.1.1.4,Printer-MIB::prtInterpreterLangVersion,OCTET,read-only,,current,,The date code or version of the language which this interpreter is interpreting or emulating.
.1.3.6.1.2.1.43.15.1.1.5,Printer-MIB::prtInterpreterDescription,OCTET,read-only,,current,,A string to identify this interpreter in the localization specified by prtGeneralCurrentLocalization as opposed to the language which is being interpreted. It is anticipated that this string will allow manufacturers to unambiguously identify their interpreters.
.1.3.6.1.2.1.43.15.1.1.6,Printer-MIB::prtInterpreterVersion,OCTET,read-only,,current,,The date code, version number, or other product specific information tied to this interpreter. This value is associated with the interpreter, rather than with the version of the language which is being interpreted or emulated.
.1.3.6.1.2.1.43.15.1.1.7,Printer-MIB::prtInterpreterDefaultOrientation,INTEGER,read-write,,current,other(1):portrait(3):landscape(4),The current orientation default for this interpreter. This value may be overridden for a particular job (e.g., by a command in the input data stream).
.1.3.6.1.2.1.43.15.1.1.8,Printer-MIB::prtInterpreterFeedAddressability,Integer32,read-only,,current,,The maximum interpreter addressability in the feed direction in 10000 prtMarkerAddressabilityUnits (as specified by prtMarkerDefaultIndex) for this interpreter. The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.15.1.1.9,Printer-MIB::prtInterpreterXFeedAddressability,Integer32,read-only,,current,,The maximum interpreter addressability in the cross feed direction in 10000 prtMarkerAddressabilityUnits (as specified by prtMarkerDefaultIndex) for this interpreter. The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.15.1.1.10,Printer-MIB::prtInterpreterDefaultCharSetIn,INTEGER,read-write,,current,other(1):unknown(2):csASCII(3):csISOLatin1(4):csISOLatin2(5):csISOLatin3(6):csISOLatin4(7):csISOLatinCyrillic(8):csISOLatinArabic(9):csISOLatinGreek(10):csISOLatinHebrew(11):csISOLatin5(12):csISOLatin6(13):csISOTextComm(14):csHalfWidthKatakana(15):csJISEncoding(16):csShiftJIS(17):csEUCPkdFmtJapanese(18):csEUCFixWidJapanese(19):csISO4UnitedKingdom(20):csISO11SwedishForNames(21):csISO15Italian(22):csISO17Spanish(23):csISO21German(24):csISO60DanishNorwegian(25):csISO69French(26):csISO10646UTF1(27):csISO646basic1983(28):csINVARIANT(29):csISO2IntlRefVersion(30):csNATSSEFI(31):csNATSSEFIADD(32):csNATSDANO(33):csNATSDANOADD(34):csISO10Swedish(35):csKSC56011987(36):csISO2022KR(37):csEUCKR(38):csISO2022JP(39):csISO2022JP2(40):csISO13JISC6220jp(41):csISO14JISC6220ro(42):csISO16Portuguese(43):csISO18Greek7Old(44):csISO19LatinGreek(45):csISO25French(46):csISO27LatinGreek1(47):csISO5427Cyrillic(48):csISO42JISC62261978(49):csISO47BSViewdata(50):csISO49INIS(51):csISO50INIS8(52):csISO51INISCyrillic(53):csISO54271981(54):csISO5428Greek(55):csISO57GB1988(56):csISO58GB231280(57):csISO61Norwegian2(58):csISO70VideotexSupp1(59):csISO84Portuguese2(60):csISO85Spanish2(61):csISO86Hungarian(62):csISO87JISX0208(63):csISO88Greek7(64):csISO89ASMO449(65):csISO90(66):csISO91JISC62291984a(67):csISO92JISC62991984b(68):csISO93JIS62291984badd(69):csISO94JIS62291984hand(70):csISO95JIS62291984handadd(71):csISO96JISC62291984kana(72):csISO2033(73):csISO99NAPLPS(74):csISO102T617bit(75):csISO103T618bit(76):csISO111ECMACyrillic(77):csa71(78):csa72(79):csISO123CSAZ24341985gr(80):csISO88596E(81):csISO88596I(82):csISO128T101G2(83):csISO88598E(84):csISO88598I(85):csISO139CSN369103(86):csISO141JUSIB1002(87):csISO143IECP271(88):csISO146Serbian(89):csISO147Macedonian(90):csISO150(91):csISO151Cuba(92):csISO6937Add(93):csISO153GOST1976874(94):csISO8859Supp(95):csISO10367Box(96):csISO158Lap(97):csISO159JISX02121990(98):csISO646Danish(99):csUSDK(100):csDKUS(101):csKSC5636(102):csUnicode11UTF7(103):csISO2022CN(104):csISO2022CNEXT(105):csUTF8(106):csISO885913(109):csISO885914(110):csISO885915(111):csISO885916(112):csGBK(113):csGB18030(114):csOSDEBCDICDF0415(115):csOSDEBCDICDF03IRV(116):csOSDEBCDICDF041(117):csISO115481(118):csKZ1048(119):csUnicode(1000):csUCS4(1001):csUnicodeASCII(1002):csUnicodeLatin1(1003):csUnicodeJapanese(1004):csUnicodeIBM1261(1005):csUnicodeIBM1268(1006):csUnicodeIBM1276(1007):csUnicodeIBM1264(1008):csUnicodeIBM1265(1009):csUnicode11(1010):csSCSU(1011):csUTF7(1012):csUTF16BE(1013):csUTF16LE(1014):csUTF16(1015):csCESU8(1016):csUTF32(1017):csUTF32BE(1018):csUTF32LE(1019):csBOCU1(1020):csWindows30Latin1(2000):csWindows31Latin1(2001):csWindows31Latin2(2002):csWindows31Latin5(2003):csHPRoman8(2004):csAdobeStandardEncoding(2005):csVenturaUS(2006):csVenturaInternational(2007):csDECMCS(2008):csPC850Multilingual(2009):csPCp852(2010):csPC8CodePage437(2011):csPC8DanishNorwegian(2012):csPC862LatinHebrew(2013):csPC8Turkish(2014):csIBMSymbols(2015):csIBMThai(2016):csHPLegal(2017):csHPPiFont(2018):csHPMath8(2019):csHPPSMath(2020):csHPDesktop(2021):csVenturaMath(2022):csMicrosoftPublishing(2023):csWindows31J(2024):csGB2312(2025):csBig5(2026):csMacintosh(2027):csIBM037(2028):csIBM038(2029):csIBM273(2030):csIBM274(2031):csIBM275(2032):csIBM277(2033):csIBM278(2034):csIBM280(2035):csIBM281(2036):csIBM284(2037):csIBM285(2038):csIBM290(2039):csIBM297(2040):csIBM420(2041):csIBM423(2042):csIBM424(2043):csIBM500(2044):csIBM851(2045):csIBM855(2046):csIBM857(2047):csIBM860(2048):csIBM861(2049):csIBM863(2050):csIBM864(2051):csIBM865(2052):csIBM868(2053):csIBM869(2054):csIBM870(2055):csIBM871(2056):csIBM880(2057):csIBM891(2058):csIBM903(2059):csIBBM904(2060):csIBM905(2061):csIBM918(2062):csIBM1026(2063):csIBMEBCDICATDE(2064):csEBCDICATDEA(2065):csEBCDICCAFR(2066):csEBCDICDKNO(2067):csEBCDICDKNOA(2068):csEBCDICFISE(2069):csEBCDICFISEA(2070):csEBCDICFR(2071):csEBCDICIT(2072):csEBCDICPT(2073):csEBCDICES(2074):csEBCDICESA(2075):csEBCDICESS(2076):csEBCDICUK(2077):csEBCDICUS(2078):csUnknown8BiT(2079):csMnemonic(2080):csMnem(2081):csVISCII(2082):csVIQR(2083):csKOI8R(2084):csHZGB2312(2085):csIBM866(2086):csPC775Baltic(2087):csKOI8U(2088):csIBM00858(2089):csIBM00924(2090):csIBM01140(2091):csIBM01141(2092):csIBM01142(2093):csIBM01143(2094):csIBM01144(2095):csIBM01145(2096):csIBM01146(2097):csIBM01147(2098):csIBM01148(2099):csIBM01149(2100):csBig5HKSCS(2101):csIBM1047(2102):csPTCP154(2103):csAmiga1251(2104):csKOI7switched(2105):csBRF(2106):csTSCII(2107):csCP51932(2108):cswindows874(2109):cswindows1250(2250):cswindows1251(2251):cswindows1252(2252):cswindows1253(2253):cswindows1254(2254):cswindows1255(2255):cswindows1256(2256):cswindows1257(2257):cswindows1258(2258):csTIS620(2259):cs50220(2260):reserved(3000),The default coded character set for input octets encountered outside a context in which the Page Description Language established the interpretation of the octets. (Input octets are presented to the interpreter through a path defined in the channel group.)
.1.3.6.1.2.1.43.15.1.1.11,Printer-MIB::prtInterpreterDefaultCharSetOut,INTEGER,read-write,,current,other(1):unknown(2):csASCII(3):csISOLatin1(4):csISOLatin2(5):csISOLatin3(6):csISOLatin4(7):csISOLatinCyrillic(8):csISOLatinArabic(9):csISOLatinGreek(10):csISOLatinHebrew(11):csISOLatin5(12):csISOLatin6(13):csISOTextComm(14):csHalfWidthKatakana(15):csJISEncoding(16):csShiftJIS(17):csEUCPkdFmtJapanese(18):csEUCFixWidJapanese(19):csISO4UnitedKingdom(20):csISO11SwedishForNames(21):csISO15Italian(22):csISO17Spanish(23):csISO21German(24):csISO60DanishNorwegian(25):csISO69French(26):csISO10646UTF1(27):csISO646basic1983(28):csINVARIANT(29):csISO2IntlRefVersion(30):csNATSSEFI(31):csNATSSEFIADD(32):csNATSDANO(33):csNATSDANOADD(34):csISO10Swedish(35):csKSC56011987(36):csISO2022KR(37):csEUCKR(38):csISO2022JP(39):csISO2022JP2(40):csISO13JISC6220jp(41):csISO14JISC6220ro(42):csISO16Portuguese(43):csISO18Greek7Old(44):csISO19LatinGreek(45):csISO25French(46):csISO27LatinGreek1(47):csISO5427Cyrillic(48):csISO42JISC62261978(49):csISO47BSViewdata(50):csISO49INIS(51):csISO50INIS8(52):csISO51INISCyrillic(53):csISO54271981(54):csISO5428Greek(55):csISO57GB1988(56):csISO58GB231280(57):csISO61Norwegian2(58):csISO70VideotexSupp1(59):csISO84Portuguese2(60):csISO85Spanish2(61):csISO86Hungarian(62):csISO87JISX0208(63):csISO88Greek7(64):csISO89ASMO449(65):csISO90(66):csISO91JISC62291984a(67):csISO92JISC62991984b(68):csISO93JIS62291984badd(69):csISO94JIS62291984hand(70):csISO95JIS62291984handadd(71):csISO96JISC62291984kana(72):csISO2033(73):csISO99NAPLPS(74):csISO102T617bit(75):csISO103T618bit(76):csISO111ECMACyrillic(77):csa71(78):csa72(79):csISO123CSAZ24341985gr(80):csISO88596E(81):csISO88596I(82):csISO128T101G2(83):csISO88598E(84):csISO88598I(85):csISO139CSN369103(86):csISO141JUSIB1002(87):csISO143IECP271(88):csISO146Serbian(89):csISO147Macedonian(90):csISO150(91):csISO151Cuba(92):csISO6937Add(93):csISO153GOST1976874(94):csISO8859Supp(95):csISO10367Box(96):csISO158Lap(97):csISO159JISX02121990(98):csISO646Danish(99):csUSDK(100):csDKUS(101):csKSC5636(102):csUnicode11UTF7(103):csISO2022CN(104):csISO2022CNEXT(105):csUTF8(106):csISO885913(109):csISO885914(110):csISO885915(111):csISO885916(112):csGBK(113):csGB18030(114):csOSDEBCDICDF0415(115):csOSDEBCDICDF03IRV(116):csOSDEBCDICDF041(117):csISO115481(118):csKZ1048(119):csUnicode(1000):csUCS4(1001):csUnicodeASCII(1002):csUnicodeLatin1(1003):csUnicodeJapanese(1004):csUnicodeIBM1261(1005):csUnicodeIBM1268(1006):csUnicodeIBM1276(1007):csUnicodeIBM1264(1008):csUnicodeIBM1265(1009):csUnicode11(1010):csSCSU(1011):csUTF7(1012):csUTF16BE(1013):csUTF16LE(1014):csUTF16(1015):csCESU8(1016):csUTF32(1017):csUTF32BE(1018):csUTF32LE(1019):csBOCU1(1020):csWindows30Latin1(2000):csWindows31Latin1(2001):csWindows31Latin2(2002):csWindows31Latin5(2003):csHPRoman8(2004):csAdobeStandardEncoding(2005):csVenturaUS(2006):csVenturaInternational(2007):csDECMCS(2008):csPC850Multilingual(2009):csPCp852(2010):csPC8CodePage437(2011):csPC8DanishNorwegian(2012):csPC862LatinHebrew(2013):csPC8Turkish(2014):csIBMSymbols(2015):csIBMThai(2016):csHPLegal(2017):csHPPiFont(2018):csHPMath8(2019):csHPPSMath(2020):csHPDesktop(2021):csVenturaMath(2022):csMicrosoftPublishing(2023):csWindows31J(2024):csGB2312(2025):csBig5(2026):csMacintosh(2027):csIBM037(2028):csIBM038(2029):csIBM273(2030):csIBM274(2031):csIBM275(2032):csIBM277(2033):csIBM278(2034):csIBM280(2035):csIBM281(2036):csIBM284(2037):csIBM285(2038):csIBM290(2039):csIBM297(2040):csIBM420(2041):csIBM423(2042):csIBM424(2043):csIBM500(2044):csIBM851(2045):csIBM855(2046):csIBM857(2047):csIBM860(2048):csIBM861(2049):csIBM863(2050):csIBM864(2051):csIBM865(2052):csIBM868(2053):csIBM869(2054):csIBM870(2055):csIBM871(2056):csIBM880(2057):csIBM891(2058):csIBM903(2059):csIBBM904(2060):csIBM905(2061):csIBM918(2062):csIBM1026(2063):csIBMEBCDICATDE(2064):csEBCDICATDEA(2065):csEBCDICCAFR(2066):csEBCDICDKNO(2067):csEBCDICDKNOA(2068):csEBCDICFISE(2069):csEBCDICFISEA(2070):csEBCDICFR(2071):csEBCDICIT(2072):csEBCDICPT(2073):csEBCDICES(2074):csEBCDICESA(2075):csEBCDICESS(2076):csEBCDICUK(2077):csEBCDICUS(2078):csUnknown8BiT(2079):csMnemonic(2080):csMnem(2081):csVISCII(2082):csVIQR(2083):csKOI8R(2084):csHZGB2312(2085):csIBM866(2086):csPC775Baltic(2087):csKOI8U(2088):csIBM00858(2089):csIBM00924(2090):csIBM01140(2091):csIBM01141(2092):csIBM01142(2093):csIBM01143(2094):csIBM01144(2095):csIBM01145(2096):csIBM01146(2097):csIBM01147(2098):csIBM01148(2099):csIBM01149(2100):csBig5HKSCS(2101):csIBM1047(2102):csPTCP154(2103):csAmiga1251(2104):csKOI7switched(2105):csBRF(2106):csTSCII(2107):csCP51932(2108):cswindows874(2109):cswindows1250(2250):cswindows1251(2251):cswindows1252(2252):cswindows1253(2253):cswindows1254(2254):cswindows1255(2255):cswindows1256(2256):cswindows1257(2257):cswindows1258(2258):csTIS620(2259):cs50220(2260):reserved(3000),The default character set for data coming from this interpreter through the printer's output channel (i.e. the 'backchannel').
.1.3.6.1.2.1.43.15.1.1.12,Printer-MIB::prtInterpreterTwoWay,INTEGER,read-only,,current,yes(3):no(4),Indicates whether or not this interpreter returns information back to the host.
.1.3.6.1.2.1.43.16,Printer-MIB::prtConsoleDisplayBuffer,,,,,,
.1.3.6.1.2.1.43.16.5,Printer-MIB::prtConsoleDisplayBufferTable,,not-accessible,,current,,Physical display buffer for printer console display or operator panel NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.16.5.1,Printer-MIB::prtConsoleDisplayBufferEntry,,not-accessible,hrDeviceIndex:prtConsoleDisplayBufferIndex,current,,This table contains one entry for each physical line on the display. Lines cannot be added or deleted. Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.16.5.1.1,Printer-MIB::prtConsoleDisplayBufferIndex,Integer32,not-accessible,,current,,A unique value for each console line in the printer. The value is used to identify this console line. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new console lines to the printer). Values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.16.5.1.2,Printer-MIB::prtConsoleDisplayBufferText,OCTET,read-write,,current,,The content of a line in the logical display buffer of the operator's console of the printer. When a write operation occurs, normally a critical message, to one of the LineText strings, the agent should make that line displayable if a physical display is present. Writing a zero length string clears the line. It is an implementation- specific matter as to whether the agent allows a line to be overwritten before it has been cleared. Printer generated strings shall be in the localization specified by prtConsoleLocalization.Management Application generated strings should be localized by the Management Application.
.1.3.6.1.2.1.43.17,Printer-MIB::prtConsoleLights,,,,,,
.1.3.6.1.2.1.43.17.6,Printer-MIB::prtConsoleLightTable,,not-accessible,,current,,The console light table provides a description and state information for each light present on the printer console. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.17.6.1,Printer-MIB::prtConsoleLightEntry,,not-accessible,hrDeviceIndex:prtConsoleLightIndex,current,,Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.17.6.1.1,Printer-MIB::prtConsoleLightIndex,Integer32,not-accessible,,current,,A unique value used by the printer to identify this light. Although these values may change due to a major reconfiguration of the device (e.g., the addition of new lights to the printer). Values SHOULD remain stable across successive printer power cycles. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.17.6.1.2,Printer-MIB::prtConsoleOnTime,Integer32,read-write,,current,,This object, in conjunction with prtConsoleOffTime, defines the current status of the light. If both prtConsoleOnTime and prtConsoleOffTime are non-zero, the lamp is blinking and the values presented define the on time and off time, respectively, in milliseconds. If prtConsoleOnTime is zero and prtConsoleOffTime is non-zero, the lamp is off. If prtConsoleOffTime is zero and prtConsoleOnTime is non-zero, the lamp is on. If both values are zero the lamp is off. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.17.6.1.3,Printer-MIB::prtConsoleOffTime,Integer32,read-write,,current,,This object, in conjunction with prtConsoleOnTime, defines the current status of the light. If both prtConsoleOnTime and prtConsoleOffTime are non-zero, the lamp is blinking and the values presented define the on time and off time, respectively, in milliseconds. If prtConsoleOnTime is zero and prtConsoleOffTime is non-zero, the lamp is off. If prtConsoleOffTime is zero and prtConsoleOnTime is non-zero, the lamp is on. If both values are zero the lamp is off. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.17.6.1.4,Printer-MIB::prtConsoleColor,INTEGER,read-only,,current,other(1):unknown(2):white(3):red(4):green(5):blue(6):cyan(7):magenta(8):yellow(9):orange(10),The color of this light.
.1.3.6.1.2.1.43.17.6.1.5,Printer-MIB::prtConsoleDescription,OCTET,read-only,,current,,The vendor description or label of this light in the localization specified by prtConsoleLocalization.
.1.3.6.1.2.1.43.18,Printer-MIB::prtAlert,,,,,,
.1.3.6.1.2.1.43.18.1,Printer-MIB::prtAlertTable,,not-accessible,,current,,The prtAlertTable lists all the critical and non-critical alerts currently active in the printer. A critical alert is one that stops the printer from printing immediately and printing can not continue until the critical alert condition is eliminated. Non-critical alerts are those items that do not stop printing but may at some future time. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1,Printer-MIB::prtAlertEntry,,not-accessible,hrDeviceIndex:prtAlertIndex,current,,Entries may exist in the table for each device index with a device type of 'printer'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1.1,Printer-MIB::prtAlertIndex,Integer32,read-only,,current,,The index value used to determine which alerts have been added or removed from the alert table. This is an incrementing integer initialized to 1 when the printer is reset. (i.e., The first event placed in the alert table after a reset of the printer shall have an index value of 1.) When the printer adds an alert to the table, that alert is assigned the next higher integer value from the last item entered into the table. If the index value reaches its maximum value, the next index value used must be 1. NOTE: The management application will read the alert table when a trap or event notification occurs or at a periodic rate and then parse the table to determine if any new entries were added by comparing the last known index value with the current highest index value. The management application will then update its copy of the alert table. When the printer discovers that an alert is no longer active, the printer shall remove the row for that alert from the table and shall reduce the number of rows in the table. The printer may add or delete any number of rows from the table at any time. The management station can detect when binary change alerts have been deleted by requesting an attribute of each alert, and noting alerts as deleted when that retrieval is not possible. The objects 'prtAlertCriticalEvents'and 'prtAlertAllEvents' in the 'prtGeneralTable' reduce the need for management applications to scan the 'prtAlertTable'. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1.2,Printer-MIB::prtAlertSeverityLevel,INTEGER,read-only,,current,other(1):critical(3):warning(4):warningBinaryChangeEvent(5),The level of severity of this alert table entry. The printer determines the severity level assigned to each entry into the table.
.1.3.6.1.2.1.43.18.1.1.3,Printer-MIB::prtAlertTrainingLevel,INTEGER,read-only,,current,other(1):unknown(2):untrained(3):trained(4):fieldService(5):management(6):noInterventionRequired(7),See TEXTUAL-CONVENTION PrtAlertTrainingLevelTC. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1.4,Printer-MIB::prtAlertGroup,INTEGER,read-only,,current,other(1):unknown(2):hostResourcesMIBStorageTable(3):hostResourcesMIBDeviceTable(4):generalPrinter(5):cover(6):localization(7):input(8):output(9):marker(10):markerSupplies(11):markerColorant(12):mediaPath(13):channel(14):interpreter(15):consoleDisplayBuffer(16):consoleLights(17):alert(18):finDevice(30):finSupply(31):finSupplyMediaInput(32):finAttribute(33),The type of sub-unit within the printer model that this alert is related. Input, output, and markers are examples of printer model groups, i.e., examples of types of sub-units. Wherever possible, these enumerations match the sub-identifier that identifies the relevant table in the printmib.
.1.3.6.1.2.1.43.18.1.1.5,Printer-MIB::prtAlertGroupIndex,Integer32,read-only,,current,,The low-order index of the row within the table identified by prtAlertGroup that represents the sub-unit of the printer that caused this alert, or -1 if not applicable. The combination of the prtAlertGroup and the prtAlertGroupIndex defines exactly which printer sub-unit caused the alert; for example, Input #3, Output#2, and Marker #1. Every object in this MIB is indexed with hrDeviceIndex and optionally, another index variable. If this other index variable is present in the table that generated the alert, it will be used as the value for this object. Otherwise, this value shall be -1. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1.6,Printer-MIB::prtAlertLocation,Integer32,read-only,,current,,The sub-unit location that is defined by the printer manufacturer to further refine the location of this alert within the designated sub-unit. The location is used in conjunction with the Group and GroupIndex values; for example, there is an alert in Input #2 at location number 7. The value (-2) indicates unknown. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1.7,Printer-MIB::prtAlertCode,INTEGER,read-only,,current,other(1):unknown(2):coverOpen(3):coverClosed(4):interlockOpen(5):interlockClosed(6):configurationChange(7):jam(8):subunitMissing(9):subunitLifeAlmostOver(10):subunitLifeOver(11):subunitAlmostEmpty(12):subunitEmpty(13):subunitAlmostFull(14):subunitFull(15):subunitNearLimit(16):subunitAtLimit(17):subunitOpened(18):subunitClosed(19):subunitTurnedOn(20):subunitTurnedOff(21):subunitOffline(22):subunitPowerSaver(23):subunitWarmingUp(24):subunitAdded(25):subunitRemoved(26):subunitResourceAdded(27):subunitResourceRemoved(28):subunitRecoverableFailure(29):subunitUnrecoverableFailure(30):subunitRecoverableStorageError(31):subunitUnrecoverableStorageError(32):subunitMotorFailure(33):subunitMemoryExhausted(34):subunitUnderTemperature(35):subunitOverTemperature(36):subunitTimingFailure(37):subunitThermistorFailure(38):doorOpen(501):doorClosed(502):powerUp(503):powerDown(504):printerNMSReset(505):printerManualReset(506):printerReadyToPrint(507):inputMediaTrayMissing(801):inputMediaSizeChange(802):inputMediaWeightChange(803):inputMediaTypeChange(804):inputMediaColorChange(805):inputMediaFormPartsChange(806):inputMediaSupplyLow(807):inputMediaSupplyEmpty(808):inputMediaChangeRequest(809):inputManualInputRequest(810):inputTrayPositionFailure(811):inputTrayElevationFailure(812):inputCannotFeedSizeSelected(813):outputMediaTrayMissing(901):outputMediaTrayAlmostFull(902):outputMediaTrayFull(903):outputMailboxSelectFailure(904):markerFuserUnderTemperature(1001):markerFuserOverTemperature(1002):markerFuserTimingFailure(1003):markerFuserThermistorFailure(1004):markerAdjustingPrintQuality(1005):markerTonerEmpty(1101):markerInkEmpty(1102):markerPrintRibbonEmpty(1103):markerTonerAlmostEmpty(1104):markerInkAlmostEmpty(1105):markerPrintRibbonAlmostEmpty(1106):markerWasteTonerReceptacleAlmostFull(1107):markerWasteInkReceptacleAlmostFull(1108):markerWasteTonerReceptacleFull(1109):markerWasteInkReceptacleFull(1110):markerOpcLifeAlmostOver(1111):markerOpcLifeOver(1112):markerDeveloperAlmostEmpty(1113):markerDeveloperEmpty(1114):markerTonerCartridgeMissing(1115):mediaPathMediaTrayMissing(1301):mediaPathMediaTrayAlmostFull(1302):mediaPathMediaTrayFull(1303):mediaPathCannotDuplexMediaSelected(1304):interpreterMemoryIncrease(1501):interpreterMemoryDecrease(1502):interpreterCartridgeAdded(1503):interpreterCartridgeDeleted(1504):interpreterResourceAdded(1505):interpreterResourceDeleted(1506):interpreterResourceUnavailable(1507):interpreterComplexPageEncountered(1509):alertRemovalOfBinaryChangeEntry(1801):staplerCoverOpen(30203):staplerCoverClosed(30204):staplerInterlockOpen(30205):staplerInterlockClosed(30206):staplerConfigurationChange(30207):staplerJam(30208):staplerMissing(30209):staplerLifeAlmostOver(30210):staplerLifeOver(30211):staplerAlmostEmpty(30212):staplerEmpty(30213):staplerAlmostFull(30214):staplerFull(30215):staplerNearLimit(30216):staplerAtLimit(30217):staplerOpened(30218):staplerClosed(30219):staplerTurnedOn(30220):staplerTurnedOff(30221):staplerOffline(30222):staplerPowerSaver(30223):staplerWarmingUp(30224):staplerAdded(30225):staplerRemoved(30226):staplerResourceAdded(30227):staplerResourceRemoved(30228):staplerRecoverableFailure(30229):staplerUnrecoverableFailure(30230):staplerRecoverableStorageError(30231):staplerUnrecoverableStorageError(30232):staplerMotorFailure(30233):staplerMemoryExhausted(30234):staplerUnderTemperature(30235):staplerOverTemperature(30236):staplerTimingFailure(30237):staplerThermistorFailure(30238):stitcherCoverOpen(30303):stitcherCoverClosed(30304):stitcherInterlockOpen(30305):stitcherInterlockClosed(30306):stitcherConfigurationChange(30307):stitcherJam(30308):stitcherMissing(30309):stitcherLifeAlmostOver(30310):stitcherLifeOver(30311):stitcherAlmostEmpty(30312):stitcherEmpty(30313):stitcherAlmostFull(30314):stitcherFull(30315):stitcherNearLimit(30316):stitcherAtLimit(30317):stitcherOpened(30318):stitcherClosed(30319):stitcherTurnedOn(30320):stitcherTurnedOff(30321):stitcherOffline(30322):stitcherPowerSaver(30323):stitcherWarmingUp(30324):stitcherAdded(30325):stitcherRemoved(30326):stitcherResourceAdded(30327):stitcherResourceRemoved(30328):stitcherRecoverableFailure(30329):stitcherUnrecoverableFailure(30330):stitcherRecoverableStorageError(30331):stitcherUnrecoverableStorageError(30332):stitcherMotorFailure(30333):stitcherMemoryExhausted(30334):stitcherUnderTemperature(30335):stitcherOverTemperature(30336):stitcherTimingFailure(30337):stitcherThermistorFailure(30338):folderCoverOpen(30403):folderCoverClosed(30404):folderInterlockOpen(30405):folderInterlockClosed(30406):folderConfigurationChange(30407):folderJam(30408):folderMissing(30409):folderLifeAlmostOver(30410):folderLifeOver(30411):folderAlmostEmpty(30412):folderEmpty(30413):folderAlmostFull(30414):folderFull(30415):folderNearLimit(30416):folderAtLimit(30417):folderOpened(30418):folderClosed(30419):folderTurnedOn(30420):folderTurnedOff(30421):folderOffline(30422):folderPowerSaver(30423):folderWarmingUp(30424):folderAdded(30425):folderRemoved(30426):folderResourceAdded(30427):folderResourceRemoved(30428):folderRecoverableFailure(30429):folderUnrecoverableFailure(30430):folderRecoverableStorageError(30431):folderUnrecoverableStorageError(30432):folderMotorFailure(30433):folderMemoryExhausted(30434):folderUnderTemperature(30435):folderOverTemperature(30436):folderTimingFailure(30437):folderThermistorFailure(30438):binderCoverOpen(30503):binderCoverClosed(30504):binderInterlockOpen(30505):binderInterlockClosed(30506):binderConfigurationChange(30507):binderJam(30508):binderMissing(30509):binderLifeAlmostOver(30510):binderLifeOver(30511):binderAlmostEmpty(30512):binderEmpty(30513):binderAlmostFull(30514):binderFull(30515):binderNearLimit(30516):binderAtLimit(30517):binderOpened(30518):binderClosed(30519):binderTurnedOn(30520):binderTurnedOff(30521):binderOffline(30522):binderPowerSaver(30523):binderWarmingUp(30524):binderAdded(30525):binderRemoved(30526):binderResourceAdded(30527):binderResourceRemoved(30528):binderRecoverableFailure(30529):binderUnrecoverableFailure(30530):binderRecoverableStorageError(30531):binderUnrecoverableStorageError(30532):binderMotorFailure(30533):binderMemoryExhausted(30534):binderUnderTemperature(30535):binderOverTemperature(30536):binderTimingFailure(30537):binderThermistorFailure(30538):trimmerCoverOpen(30603):trimmerCoverClosed(30604):trimmerInterlockOpen(30605):trimmerInterlockClosed(30606):trimmerConfigurationChange(30607):trimmerJam(30608):trimmerMissing(30609):trimmerLifeAlmostOver(30610):trimmerLifeOver(30611):trimmerAlmostEmpty(30612):trimmerEmpty(30613):trimmerAlmostFull(30614):trimmerFull(30615):trimmerNearLimit(30616):trimmerAtLimit(30617):trimmerOpened(30618):trimmerClosed(30619):trimmerTurnedOn(30620):trimmerTurnedOff(30621):trimmerOffline(30622):trimmerPowerSaver(30623):trimmerWarmingUp(30624):trimmerAdded(30625):trimmerRemoved(30626):trimmerResourceAdded(30627):trimmerResourceRemoved(30628):trimmerRecoverableFailure(30629):trimmerUnrecoverableFailure(30630):trimmerRecoverableStorageError(30631):trimmerUnrecoverableStorageError(30632):trimmerMotorFailure(30633):trimmerMemoryExhausted(30634):trimmerUnderTemperature(30635):trimmerOverTemperature(30636):trimmerTimingFailure(30637):trimmerThermistorFailure(30638):dieCutterCoverOpen(30703):dieCutterCoverClosed(30704):dieCutterInterlockOpen(30705):dieCutterInterlockClosed(30706):dieCutterConfigurationChange(30707):dieCutterJam(30708):dieCutterMissing(30709):dieCutterLifeAlmostOver(30710):dieCutterLifeOver(30711):dieCutterAlmostEmpty(30712):dieCutterEmpty(30713):dieCutterAlmostFull(30714):dieCutterFull(30715):dieCutterNearLimit(30716):dieCutterAtLimit(30717):dieCutterOpened(30718):dieCutterClosed(30719):dieCutterTurnedOn(30720):dieCutterTurnedOff(30721):dieCutterOffline(30722):dieCutterPowerSaver(30723):dieCutterWarmingUp(30724):dieCutterAdded(30725):dieCutterRemoved(30726):dieCutterResourceAdded(30727):dieCutterResourceRemoved(30728):dieCutterRecoverableFailure(30729):dieCutterUnrecoverableFailure(30730):dieCutterRecoverableStorageError(30731):dieCutterUnrecoverableStorageError(30732):dieCutterMotorFailure(30733):dieCutterMemoryExhausted(30734):dieCutterUnderTemperature(30735):dieCutterOverTemperature(30736):dieCutterTimingFailure(30737):dieCutterThermistorFailure(30738):puncherCoverOpen(30803):puncherCoverClosed(30804):puncherInterlockOpen(30805):puncherInterlockClosed(30806):puncherConfigurationChange(30807):puncherJam(30808):puncherMissing(30809):puncherLifeAlmostOver(30810):puncherLifeOver(30811):puncherAlmostEmpty(30812):puncherEmpty(30813):puncherAlmostFull(30814):puncherFull(30815):puncherNearLimit(30816):puncherAtLimit(30817):puncherOpened(30818):puncherClosed(30819):puncherTurnedOn(30820):puncherTurnedOff(30821):puncherOffline(30822):puncherPowerSaver(30823):puncherWarmingUp(30824):puncherAdded(30825):puncherRemoved(30826):puncherResourceAdded(30827):puncherResourceRemoved(30828):puncherRecoverableFailure(30829):puncherUnrecoverableFailure(30830):puncherRecoverableStorageError(30831):puncherUnrecoverableStorageError(30832):puncherMotorFailure(30833):puncherMemoryExhausted(30834):puncherUnderTemperature(30835):puncherOverTemperature(30836):puncherTimingFailure(30837):puncherThermistorFailure(30838):perforaterCoverOpen(30903):perforaterCoverClosed(30904):perforaterInterlockOpen(30905):perforaterInterlockClosed(30906):perforaterConfigurationChange(30907):perforaterJam(30908):perforaterMissing(30909):perforaterLifeAlmostOver(30910):perforaterLifeOver(30911):perforaterAlmostEmpty(30912):perforaterEmpty(30913):perforaterAlmostFull(30914):perforaterFull(30915):perforaterNearLimit(30916):perforaterAtLimit(30917):perforaterOpened(30918):perforaterClosed(30919):perforaterTurnedOn(30920):perforaterTurnedOff(30921):perforaterOffline(30922):perforaterPowerSaver(30923):perforaterWarmingUp(30924):perforaterAdded(30925):perforaterRemoved(30926):perforaterResourceAdded(30927):perforaterResourceRemoved(30928):perforaterRecoverableFailure(30929):perforaterUnrecoverableFailure(30930):perforaterRecoverableStorageError(30931):perforaterUnrecoverableStorageError(30932):perforaterMotorFailure(30933):perforaterMemoryExhausted(30934):perforaterUnderTemperature(30935):perforaterOverTemperature(30936):perforaterTimingFailure(30937):perforaterThermistorFailure(30938):slitterCoverOpen(31003):slitterCoverClosed(31004):slitterInterlockOpen(31005):slitterInterlockClosed(31006):slitterConfigurationChange(31007):slitterJam(31008):slitterMissing(31009):slitterLifeAlmostOver(31010):slitterLifeOver(31011):slitterAlmostEmpty(31012):slitterEmpty(31013):slitterAlmostFull(31014):slitterFull(31015):slitterNearLimit(31016):slitterAtLimit(31017):slitterOpened(31018):slitterClosed(31019):slitterTurnedOn(31020):slitterTurnedOff(31021):slitterOffline(31022):slitterPowerSaver(31023):slitterWarmingUp(31024):slitterAdded(31025):slitterRemoved(31026):slitterResourceAdded(31027):slitterResourceRemoved(31028):slitterRecoverableFailure(31029):slitterUnrecoverableFailure(31030):slitterRecoverableStorageError(31031):slitterUnrecoverableStorageError(31032):slitterMotorFailure(31033):slitterMemoryExhausted(31034):slitterUnderTemperature(31035):slitterOverTemperature(31036):slitterTimingFailure(31037):slitterThermistorFailure(31038):separationCutterCoverOpen(31103):separationCutterCoverClosed(31104):separationCutterInterlockOpen(31105):separationCutterInterlockClosed(31106):separationCutterConfigurationChange(31107):separationCutterJam(31108):separationCutterMissing(31109):separationCutterLifeAlmostOver(31110):separationCutterLifeOver(31111):separationCutterAlmostEmpty(31112):separationCutterEmpty(31113):separationCutterAlmostFull(31114):separationCutterFull(31115):separationCutterNearLimit(31116):separationCutterAtLimit(31117):separationCutterOpened(31118):separationCutterClosed(31119):separationCutterTurnedOn(31120):separationCutterTurnedOff(31121):separationCutterOffline(31122):separationCutterPowerSaver(31123):separationCutterWarmingUp(31124):separationCutterAdded(31125):separationCutterRemoved(31126):separationCutterResourceAdded(31127):separationCutterResourceRemoved(31128):separationCutterRecoverableFailure(31129):separationCutterUnrecoverableFailure(31130):separationCutterRecoverableStorageError(31131):separationCutterUnrecoverableStorageError(31132):separationCutterMotorFailure(31133):separationCutterMemoryExhausted(31134):separationCutterUnderTemperature(31135):separationCutterOverTemperature(31136):separationCutterTimingFailure(31137):separationCutterThermistorFailure(31138):imprinterCoverOpen(31203):imprinterCoverClosed(31204):imprinterInterlockOpen(31205):imprinterInterlockClosed(31206):imprinterConfigurationChange(31207):imprinterJam(31208):imprinterMissing(31209):imprinterLifeAlmostOver(31210):imprinterLifeOver(31211):imprinterAlmostEmpty(31212):imprinterEmpty(31213):imprinterAlmostFull(31214):imprinterFull(31215):imprinterNearLimit(31216):imprinterAtLimit(31217):imprinterOpened(31218):imprinterClosed(31219):imprinterTurnedOn(31220):imprinterTurnedOff(31221):imprinterOffline(31222):imprinterPowerSaver(31223):imprinterWarmingUp(31224):imprinterAdded(31225):imprinterRemoved(31226):imprinterResourceAdded(31227):imprinterResourceRemoved(31228):imprinterRecoverableFailure(31229):imprinterUnrecoverableFailure(31230):imprinterRecoverableStorageError(31231):imprinterUnrecoverableStorageError(31232):imprinterMotorFailure(31233):imprinterMemoryExhausted(31234):imprinterUnderTemperature(31235):imprinterOverTemperature(31236):imprinterTimingFailure(31237):imprinterThermistorFailure(31238):wrapperCoverOpen(31303):wrapperCoverClosed(31304):wrapperInterlockOpen(31305):wrapperInterlockClosed(31306):wrapperConfigurationChange(31307):wrapperJam(31308):wrapperMissing(31309):wrapperLifeAlmostOver(31310):wrapperLifeOver(31311):wrapperAlmostEmpty(31312):wrapperEmpty(31313):wrapperAlmostFull(31314):wrapperFull(31315):wrapperNearLimit(31316):wrapperAtLimit(31317):wrapperOpened(31318):wrapperClosed(31319):wrapperTurnedOn(31320):wrapperTurnedOff(31321):wrapperOffline(31322):wrapperPowerSaver(31323):wrapperWarmingUp(31324):wrapperAdded(31325):wrapperRemoved(31326):wrapperResourceAdded(31327):wrapperResourceRemoved(31328):wrapperRecoverableFailure(31329):wrapperUnrecoverableFailure(31330):wrapperRecoverableStorageError(31331):wrapperUnrecoverableStorageError(31332):wrapperMotorFailure(31333):wrapperMemoryExhausted(31334):wrapperUnderTemperature(31335):wrapperOverTemperature(31336):wrapperTimingFailure(31337):wrapperThermistorFailure(31338):banderCoverOpen(31403):banderCoverClosed(31404):banderInterlockOpen(31405):banderInterlockClosed(31406):banderConfigurationChange(31407):banderJam(31408):banderMissing(31409):banderLifeAlmostOver(31410):banderLifeOver(31411):banderAlmostEmpty(31412):banderEmpty(31413):banderAlmostFull(31414):banderFull(31415):banderNearLimit(31416):banderAtLimit(31417):banderOpened(31418):banderClosed(31419):banderTurnedOn(31420):banderTurnedOff(31421):banderOffline(31422):banderPowerSaver(31423):banderWarmingUp(31424):banderAdded(31425):banderRemoved(31426):banderResourceAdded(31427):banderResourceRemoved(31428):banderRecoverableFailure(31429):banderUnrecoverableFailure(31430):banderRecoverableStorageError(31431):banderUnrecoverableStorageError(31432):banderMotorFailure(31433):banderMemoryExhausted(31434):banderUnderTemperature(31435):banderOverTemperature(31436):banderTimingFailure(31437):banderThermistorFailure(31438):makeEnvelopeCoverOpen(31503):makeEnvelopeCoverClosed(31504):makeEnvelopeInterlockOpen(31505):makeEnvelopeInterlockClosed(31506):makeEnvelopeConfigurationChange(31507):makeEnvelopeJam(31508):makeEnvelopeMissing(31509):makeEnvelopeLifeAlmostOver(31510):makeEnvelopeLifeOver(31511):makeEnvelopeAlmostEmpty(31512):makeEnvelopeEmpty(31513):makeEnvelopeAlmostFull(31514):makeEnvelopeFull(31515):makeEnvelopeNearLimit(31516):makeEnvelopeAtLimit(31517):makeEnvelopeOpened(31518):makeEnvelopeClosed(31519):makeEnvelopeTurnedOn(31520):makeEnvelopeTurnedOff(31521):makeEnvelopeOffline(31522):makeEnvelopePowerSaver(31523):makeEnvelopeWarmingUp(31524):makeEnvelopeAdded(31525):makeEnvelopeRemoved(31526):makeEnvelopeResourceAdded(31527):makeEnvelopeResourceRemoved(31528):makeEnvelopeRecoverableFailure(31529):makeEnvelopeUnrecoverableFailure(31530):makeEnvelopeRecoverableStorageError(31531):makeEnvelopeUnrecoverableStorageError(31532):makeEnvelopeMotorFailure(31533):makeEnvelopeMemoryExhausted(31534):makeEnvelopeUnderTemperature(31535):makeEnvelopeOverTemperature(31536):makeEnvelopeTimingFailure(31537):makeEnvelopeThermistorFailure(31538):stackerCoverOpen(31603):stackerCoverClosed(31604):stackerInterlockOpen(31605):stackerInterlockClosed(31606):stackerConfigurationChange(31607):stackerJam(31608):stackerMissing(31609):stackerLifeAlmostOver(31610):stackerLifeOver(31611):stackerAlmostEmpty(31612):stackerEmpty(31613):stackerAlmostFull(31614):stackerFull(31615):stackerNearLimit(31616):stackerAtLimit(31617):stackerOpened(31618):stackerClosed(31619):stackerTurnedOn(31620):stackerTurnedOff(31621):stackerOffline(31622):stackerPowerSaver(31623):stackerWarmingUp(31624):stackerAdded(31625):stackerRemoved(31626):stackerResourceAdded(31627):stackerResourceRemoved(31628):stackerRecoverableFailure(31629):stackerUnrecoverableFailure(31630):stackerRecoverableStorageError(31631):stackerUnrecoverableStorageError(31632):stackerMotorFailure(31633):stackerMemoryExhausted(31634):stackerUnderTemperature(31635):stackerOverTemperature(31636):stackerTimingFailure(31637):stackerThermistorFailure(31638):sheetRotatorCoverOpen(31703):sheetRotatorCoverClosed(31704):sheetRotatorInterlockOpen(31705):sheetRotatorInterlockClosed(31706):sheetRotatorConfigurationChange(31707):sheetRotatorJam(31708):sheetRotatorMissing(31709):sheetRotatorLifeAlmostOver(31710):sheetRotatorLifeOver(31711):sheetRotatorAlmostEmpty(31712):sheetRotatorEmpty(31713):sheetRotatorAlmostFull(31714):sheetRotatorFull(31715):sheetRotatorNearLimit(31716):sheetRotatorAtLimit(31717):sheetRotatorOpened(31718):sheetRotatorClosed(31719):sheetRotatorTurnedOn(31720):sheetRotatorTurnedOff(31721):sheetRotatorOffline(31722):sheetRotatorPowerSaver(31723):sheetRotatorWarmingUp(31724):sheetRotatorAdded(31725):sheetRotatorRemoved(31726):sheetRotatorResourceAdded(31727):sheetRotatorResourceRemoved(31728):sheetRotatorRecoverableFailure(31729):sheetRotatorUnrecoverableFailure(31730):sheetRotatorRecoverableStorageError(31731):sheetRotatorUnrecoverableStorageError(31732):sheetRotatorMotorFailure(31733):sheetRotatorMemoryExhausted(31734):sheetRotatorUnderTemperature(31735):sheetRotatorOverTemperature(31736):sheetRotatorTimingFailure(31737):sheetRotatorThermistorFailure(31738):inserterCoverOpen(31803):inserterCoverClosed(31804):inserterInterlockOpen(31805):inserterInterlockClosed(31806):inserterConfigurationChange(31807):inserterJam(31808):inserterMissing(31809):inserterLifeAlmostOver(31810):inserterLifeOver(31811):inserterAlmostEmpty(31812):inserterEmpty(31813):inserterAlmostFull(31814):inserterFull(31815):inserterNearLimit(31816):inserterAtLimit(31817):inserterOpened(31818):inserterClosed(31819):inserterTurnedOn(31820):inserterTurnedOff(31821):inserterOffline(31822):inserterPowerSaver(31823):inserterWarmingUp(31824):inserterAdded(31825):inserterRemoved(31826):inserterResourceAdded(31827):inserterResourceRemoved(31828):inserterRecoverableFailure(31829):inserterUnrecoverableFailure(31830):inserterRecoverableStorageError(31831):inserterUnrecoverableStorageError(31832):inserterMotorFailure(31833):inserterMemoryExhausted(31834):inserterUnderTemperature(31835):inserterOverTemperature(31836):inserterTimingFailure(31837):inserterThermistorFailure(31838),See associated TEXTUAL-CONVENTION PrtAlertCodeTC. NOTE: The above description has been modified from RFC 1759 for clarification.
.1.3.6.1.2.1.43.18.1.1.8,Printer-MIB::prtAlertDescription,OCTET,read-only,,current,,A description of this alert entry in the localization specified by prtGeneralCurrentLocalization. The description is provided by the printer to further elaborate on the enumerated alert or provide information in the case where the code is classified as 'other' or 'unknown'. The printer is required to return a description string but the string may be a null string.
.1.3.6.1.2.1.43.18.1.1.9,Printer-MIB::prtAlertTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that this alert was generated.
.1.3.6.1.2.1.43.18.2,Printer-MIB::printerV1Alert,,,,,,The value of the enterprise-specific OID in an SNMPv1 trap sent signaling a critical event in the prtAlertTable.
.1.3.6.1.2.1.43.18.2.0,Printer-MIB::printerV2AlertPrefix,,,,,,
.1.3.6.1.2.1.43.18.2.0.1,Printer-MIB::printerV2Alert,,,,,,This trap is sent whenever a critical event is added to the prtAlertTable. NOTE: The prtAlertIndex object was redundantly included in the bindings of the 'printerV2Alert' notification in RFC 1759, even though the value exists in the instance qualifier of all the other bindings. This object has been retained to provide compatiblity with existing RFC 1759 implementaions.
.1.3.6.1.2.1.43.30,Finisher-MIB::finDevice,,,,,,
.1.3.6.1.2.1.43.30.1,Finisher-MIB::finDeviceTable,,not-accessible,,current,,This table defines the finishing device subunits, including information regarding possible configuration options and the status for each finisher device subunit.
.1.3.6.1.2.1.43.30.1.1,Finisher-MIB::finDeviceEntry,,not-accessible,hrDeviceIndex:finDeviceIndex,current,,There is an entry in the finishing device table for each possible finisher process. Each individual finisher process is implemented by a finishing device represented in this table.
.1.3.6.1.2.1.43.30.1.1.1,Finisher-MIB::finDeviceIndex,Integer32,not-accessible,,current,,A unique value used to identify a finisher process. Although these values may change due to a major reconfiguration of the printer system (e.g., the addition of new finishing processes), the values are normally expected to remain stable across successive power cycles.
.1.3.6.1.2.1.43.30.1.1.2,Finisher-MIB::finDeviceType,INTEGER,read-only,,current,other(1):unknown(2):stitcher(3):folder(4):binder(5):trimmer(6):dieCutter(7):puncher(8):perforater(9):slitter(10):separationCutter(11):imprinter(12):wrapper(13):bander(14):makeEnvelope(15):stacker(16):sheetRotator(17):inserter(18),Defines the type of finishing process associated with this table row entry.
.1.3.6.1.2.1.43.30.1.1.3,Finisher-MIB::finDevicePresentOnOff,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),Indicates if this finishing device subunit is available and whether the device subunit is enabled.
.1.3.6.1.2.1.43.30.1.1.4,Finisher-MIB::finDeviceCapacityUnit,INTEGER,read-only,,current,other(1):unknown(2):tenThousandthsOfInches(3):micrometers(4):sheets(8):feet(16):meters(17):items(18):percent(19),The unit of measure for specifying the capacity of this finisher device subunit.
.1.3.6.1.2.1.43.30.1.1.5,Finisher-MIB::finDeviceMaxCapacity,Integer32,read-write,,current,,The maximum capacity of this finisher device subunit in finDeviceCapacityUnits. If the device can reliably sense this value, the value is sensed by the finisher device and is read-only: otherwise the value may be written by a management or control console application. The value (-1) means other and specifically indicates that the device places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.30.1.1.6,Finisher-MIB::finDeviceCurrentCapacity,Integer32,read-write,,current,,The current capacity of this finisher device subunit in finDeviceCapacityUnits. If the device can reliably sense this value, the value is sensed by the finisher and is read-only: otherwise the value may be written by a management or control console application. The value (-1) means other and specifically indicates that the device places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.30.1.1.7,Finisher-MIB::finDeviceAssociatedMediaPaths,OCTET,read-only,,current,,Indicates the media paths which can supply media for this finisher device. The value of this object is a bit map in an octet string with each position representing the value of a prtMediaPathIndex. For a media path that can be a source for this finisher device subunit, the bit position equal to one less than the value of prtMediaPathIndex will be set. The bits are numbered starting with the most significant bit of the first byte being bit 0, the least significant bit of the first byte being bit 7, the most significant of the second byte being bit 8, and so on.
.1.3.6.1.2.1.43.30.1.1.8,Finisher-MIB::finDeviceAssociatedOutputs,OCTET,read-only,,current,,Indicates the printer output subunits this finisher device subunit services. The value of this object is a bit map in an octet string with each position representing the value of a prtOutputIndex. For an output subunit that is serviced by this finisher device subunit, the bit position equal to one less than the value of prtOutputIndex will be set. The bits are numbered starting with the most significant bit of the first byte being bit 0, the least significant bit of the first byte being bit 7, the most significant of the second byte being bit 8, and so on.
.1.3.6.1.2.1.43.30.1.1.9,Finisher-MIB::finDeviceStatus,INTEGER,read-only,,current,,Indicates the current status of this finisher device subunit.
.1.3.6.1.2.1.43.30.1.1.10,Finisher-MIB::finDeviceDescription,OCTET,read-only,,current,,A free form text description of this device subunit in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.31,Finisher-MIB::finSupply,,,,,,
.1.3.6.1.2.1.43.31.1,Finisher-MIB::finSupplyTable,,not-accessible,,current,,Each unique source of supply is an entry in the finisher supply table. Each supply entry has its own characteristics associated with it such as colorant and current supply level.
.1.3.6.1.2.1.43.31.1.1,Finisher-MIB::finSupplyEntry,,not-accessible,hrDeviceIndex:finSupplyIndex,current,,A list of finisher devices, with their associated supplies and supplies characteristics.
.1.3.6.1.2.1.43.31.1.1.1,Finisher-MIB::finSupplyIndex,Integer32,not-accessible,,current,,A unique value used by a finisher to identify this supply container/receptacle. Although these values may change due to a major reconfiguration of the finisher (e.g., the addition of new supply sources to the finisher), values are normally expected to remain stable across successive power cycles.
.1.3.6.1.2.1.43.31.1.1.2,Finisher-MIB::finSupplyDeviceIndex,Integer32,read-only,,current,,The value of finDeviceIndex corresponding to the finishing device subunit with which this finisher supply is associated. The value zero indicates the associated finishing device is Unknown.
.1.3.6.1.2.1.43.31.1.1.3,Finisher-MIB::finSupplyClass,INTEGER,read-only,,current,other(1):supplyThatIsConsumed(3):receptacleThatIsFilled(4),This value indicates whether this supply entity represents a supply that is consumed or a container that is filled.
.1.3.6.1.2.1.43.31.1.1.4,Finisher-MIB::finSupplyType,INTEGER,read-only,,current,other(1):unknown(2):toner(3):wasteToner(4):ink(5):inkCartridge(6):inkRibbon(7):wasteInk(8):opc(9):developer(10):fuserOil(11):solidWax(12):ribbonWax(13):wasteWax(14):fuser(15):coronaWire(16):fuserOilWick(17):cleanerUnit(18):fuserCleaningPad(19):transferUnit(20):tonerCartridge(21):fuserOiler(22):water(23):wasteWater(24):glueWaterAdditive(25):wastePaper(26):bindingSupply(27):bandingSupply(28):stitchingWire(29):shrinkWrap(30):paperWrap(31):staples(32):inserts(33):covers(34):matteToner(35):matteInk(36),The type of this supply.
.1.3.6.1.2.1.43.31.1.1.5,Finisher-MIB::finSupplyDescription,OCTET,read-only,,current,,The description of this supply/receptacle in text useful for operators and management applications and in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.31.1.1.6,Finisher-MIB::finSupplyUnit,INTEGER,read-only,,current,other(1):unknown(2):tenThousandthsOfInches(3):micrometers(4):impressions(7):sheets(8):hours(11):thousandthsOfOunces(12):tenthsOfGrams(13):hundrethsOfFluidOunces(14):tenthsOfMilliliters(15):feet(16):meters(17):items(18):percent(19),Unit of measure of this finisher supply container or receptacle.
.1.3.6.1.2.1.43.31.1.1.7,Finisher-MIB::finSupplyMaxCapacity,Integer32,read-write,,current,,The maximum capacity of this supply container/receptacle expressed in Supply Units. If this supply container/ receptacle can reliably sense this value, the value is sensed and is read-only; otherwise the value may be written by a control panel or management application. The value (-1) means other and places no restrictions on this parameter. The value (-2) means unknown.
.1.3.6.1.2.1.43.31.1.1.8,Finisher-MIB::finSupplyCurrentLevel,Integer32,read-write,,current,,The current level if this supply is a container; the remaining space if this supply is a receptacle. If this supply container/receptacle can reliably sense this value, the value is sensed and is read-only; otherwise the value may be written by a control panel or management application. The value (-1) means other and places no restrictions on this parameter. The value (-2) means unknown. A value of (-3) means that the printer knows there is some supply or remaining space.
.1.3.6.1.2.1.43.31.1.1.9,Finisher-MIB::finSupplyColorName,OCTET,read-only,,current,,The name of the color associated with this supply.
.1.3.6.1.2.1.43.32,Finisher-MIB::finSupplyMediaInput,,,,,,
.1.3.6.1.2.1.43.32.1,Finisher-MIB::finSupplyMediaInputTable,,not-accessible,,current,,The input subunits associated with a finisher supply media are each represented by an entry in this table.
.1.3.6.1.2.1.43.32.1.1,Finisher-MIB::finSupplyMediaInputEntry,,not-accessible,hrDeviceIndex:finSupplyMediaInputIndex,current,,A list of finisher supply media input subunit features and characteristics.
.1.3.6.1.2.1.43.32.1.1.1,Finisher-MIB::finSupplyMediaInputIndex,Integer32,not-accessible,,current,,A unique value used by a finisher to identify this supply media input subunit. Although these values may change due to a major reconfiguration of the finisher (e.g., the addition of new supply media input sources to the finisher), values are normally expected to remain stable across successive power cycles.
.1.3.6.1.2.1.43.32.1.1.2,Finisher-MIB::finSupplyMediaInputDeviceIndex,Integer32,read-only,,current,,The value of finDeviceIndex corresponding to the finishing device subunit with which this finisher media supply is associated. The value zero indicates the associated device is unknown.
.1.3.6.1.2.1.43.32.1.1.3,Finisher-MIB::finSupplyMediaInputSupplyIndex,Integer32,read-only,,current,,The value of finSupplyIndex corresponding to the finishing supply subunit with which this finisher media supply is associated. The value zero indicates the associated finishing supply is unknown or there is no applicable finisher supply table entry.
.1.3.6.1.2.1.43.32.1.1.4,Finisher-MIB::finSupplyMediaInputType,INTEGER,read-only,,current,other(1):unknown(2):sheetFeedAutoRemovableTray(3):sheetFeedAutoNonRemovableTray(4):sheetFeedManual(5):continuousRoll(6):continuousFanFold(7):sheetFeedPull(8),The type of technology (discriminated primarily according to the feeder mechanism type) employed by the input subunit.
.1.3.6.1.2.1.43.32.1.1.5,Finisher-MIB::finSupplyMediaInputDimUnit,INTEGER,read-only,,current,tenThousandthsOfInches(3):micrometers(4),The unit of measure for specifying dimensional values for this input device.
.1.3.6.1.2.1.43.32.1.1.6,Finisher-MIB::finSupplyMediaInputMediaDimFeedDir,Integer32,read-write,,current,,This object provides the value of the dimension in the feed direction of the media that is placed or will be placed in this input device. Feed dimension measurements are taken parallel to the feed direction of the device and measured in finSupplyMediaInputDimUnits. If this input device can reliably sense this value, the value is sensed and is read-only access. Otherwise the value is read-write access and may be written by management or control panel applications. The value (-1) means other and specifically indicates that this device places no restrictions on this parameter. The value (-2) indicates unknown. 
.1.3.6.1.2.1.43.32.1.1.7,Finisher-MIB::finSupplyMediaInputMediaDimXFeedDir,Integer32,read-write,,current,,This object provides the value of the dimension across the feed direction of the media that is placed or will be placed in this input device. The cross feed direction is ninety degrees relative to the feed direction on this device and measured in finSupplyMediaInputDimUnits. If this input device can reliably sense this value, the value is sensed and is read-only access. Otherwise the value is read-write access and may be written by management or control panel applications. The value (-1) means other and specifically indicates that this device places no restrictions on this parameter. The value (-2) indicates unknown. 
.1.3.6.1.2.1.43.32.1.1.8,Finisher-MIB::finSupplyMediaInputStatus,INTEGER,read-only,,current,,This value indicates the current status of this input device.
.1.3.6.1.2.1.43.32.1.1.9,Finisher-MIB::finSupplyMediaInputMediaName,OCTET,read-write,,current,,The name of the current media contained in this input device. Examples are Engineering Manual Cover, Section A Tab Divider or any ISO standard names.
.1.3.6.1.2.1.43.32.1.1.10,Finisher-MIB::finSupplyMediaInputName,OCTET,read-write,,current,,The name assigned to this input subunit.
.1.3.6.1.2.1.43.32.1.1.11,Finisher-MIB::finSupplyMediaInputDescription,OCTET,read-only,,current,,A free form text description of this input subunit in the localization specified by prtGeneralCurrentLocalization.
.1.3.6.1.2.1.43.32.1.1.12,Finisher-MIB::finSupplyMediaInputSecurity,INTEGER,read-write,,current,other(1):on(3):off(4):notPresent(5),Indicates if this subunit has some security associated with it.
.1.3.6.1.2.1.43.32.1.1.13,Finisher-MIB::finSupplyMediaInputMediaWeight,Integer32,read-write,,current,,The weight of the media associated with this Input device in grams per meter squared. The value (-1) means other and specifically indicates that the device places no restriction on this parameter. The value (-2) means unknown. This object can be used to calculate the weight of individual pages processed by the document finisher. This value, when multiplied by the number of pages in a finished set, can be used to calculate the weight of a set before it is inserted into a mailing envelope.
.1.3.6.1.2.1.43.32.1.1.14,Finisher-MIB::finSupplyMediaInputMediaThickness,Integer32,read-write,,current,,This object identifies the thickness of the input media processed by this document input subunit measured in micrometers. This value may be used by devices (or operators) to set up proper machine tolerances for the feeder operation. The value (-2) indicates that the media thickness is unknown or not used in the setup for this input subunit.
.1.3.6.1.2.1.43.32.1.1.15,Finisher-MIB::finSupplyMediaInputMediaType,OCTET,read-write,,current,,The name of the type of medium associated with this input subunit. 
.1.3.6.1.2.1.43.33,Finisher-MIB::finDeviceAttribute,,,,,,
.1.3.6.1.2.1.43.33.1,Finisher-MIB::finDeviceAttributeTable,,not-accessible,,current,,The attribute table defines special parameters that are applicable only to a minority of the finisher devices. An attribute table entry is used, rather than unique objects, to minimize the number of MIB objects and to allow for expansion without the addition of MIB objects. Each finisher device is represented by a separate row in the device subunit attribute table.
.1.3.6.1.2.1.43.33.1.1,Finisher-MIB::finDeviceAttributeEntry,,not-accessible,hrDeviceIndex:finDeviceIndex:finDeviceAttributeTypeIndex:finDeviceAttributeInstanceIndex,current,,Each entry defines a finisher function parameter that cannot be represented by an object in the finisher device subunit table.
.1.3.6.1.2.1.43.33.1.1.1,Finisher-MIB::finDeviceAttributeTypeIndex,INTEGER,not-accessible,,current,other(1):deviceName(3):deviceVendorName(4):deviceModel(5):deviceVersion(6):deviceSerialNumber(7):maximumSheets(8):finProcessOffsetUnits(9):finReferenceEdge(10):finAxisOffset(11):finJogEdge(12):finHeadLocation(13):finOperationRestrictions(14):finNumberOfPositions(15):namedConfiguration(16):finMediaTypeRestriction(17):finPrinterInputTraySupported(18):finPreviousFinishingOperation(19):finNextFinishingOperation(20):stitchingType(30):stitchingDirection(31):foldingType(40):bindingType(50):punchHoleType(80):punchHoleSizeLongDim(81):punchHoleSizeShortDim(82):punchPattern(83):slittingType(100):wrappingType(130):stackOutputType(160):stackOffset(161):stackRotation(162),Defines the attribute type represented by this row.
.1.3.6.1.2.1.43.33.1.1.2,Finisher-MIB::finDeviceAttributeInstanceIndex,Integer32,not-accessible,,current,,An index that allows the discrimination of an attribute instance when the same attribute occurs multiple times for a specific instance of a finisher function. The value of this index shall be 1 if only a single instance of the attribute occurs for the specific finisher function. Additional values shall be assigned in a contiguous manner.
.1.3.6.1.2.1.43.33.1.1.3,Finisher-MIB::finDeviceAttributeValueAsInteger,Integer32,read-write,,current,,Defines the integer value of the attribute. The value of the attribute is represented as an integer if the finAttributeTypeTC description for the attribute has the tag 'INTEGER:'. Depending upon the attribute enum definition, this object may be either an integer, a counter, an index, or an enum. Attributes for which the concept of an integer value is not meaningful SHALL return a value of -1 for this attribute.
.1.3.6.1.2.1.43.33.1.1.4,Finisher-MIB::finDeviceAttributeValueAsOctets,OCTET,read-write,,current,,Contains the octet string value of the attribute. The value of the attribute is represented as a string if the finAttributeTypeTC description for the attribute has the tag 'OCTETS:'. Depending upon the attribute enum definition, this object may be either a coded character set string (text) or a binary octet string. Attributes for which the concept of an octet string value is not meaningful SHALL contain a zero length string.
.1.3.6.1.2.1.44,MIP-MIB::mipMIB,,,,,,The MIB Module for the Mobile IP.
.1.3.6.1.2.1.44.1,MIP-MIB::mipMIBObjects,,,,,,
.1.3.6.1.2.1.44.1.1,MIP-MIB::mipSystem,,,,,,
.1.3.6.1.2.1.44.1.1.1,MIP-MIB::mipEntities,BITS,read-only,,current,mobileNode(0):foreignAgent(1):homeAgent(2),This object describes which Mobile IP entities are supported by this managed entity. The entity may support more than one Mobile IP entities. For example, the entity supports both Foreign Agent (FA) and Home Agent (HA). Therefore, bit 1 and bit 2 are set to 1 for this object.
.1.3.6.1.2.1.44.1.1.2,MIP-MIB::mipEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the Mobile IP protocol should be enabled for the managed entity. If it is disabled, the entity should disable both agent discovery and registration functions.
.1.3.6.1.2.1.44.1.1.3,MIP-MIB::mipEncapsulationSupported,BITS,read-only,,current,ipInIp(0):gre(1):minEnc(2):other(3),Encapsulation methods supported by the Mobile IP entity. The entity may support multiple encapsulation methods or none of them: ipInIp(0), -- IP Encapsulation within IP gre(1), -- Generic Routing Encapsulation, -- refers to RFC1701 minEnc(2), -- Minimal Encapsulation within IP.
.1.3.6.1.2.1.44.1.2,MIP-MIB::mipSecurity,,,,,,
.1.3.6.1.2.1.44.1.2.1,MIP-MIB::mipSecAssocTable,,not-accessible,,current,,A table containing Mobility Security Associations.
.1.3.6.1.2.1.44.1.2.1.1,MIP-MIB::mipSecAssocEntry,,not-accessible,mipSecPeerAddress:mipSecSPI,current,,One particular Mobility Security Association.
.1.3.6.1.2.1.44.1.2.1.1.1,MIP-MIB::mipSecPeerAddress,IpAddress,not-accessible,,current,,The IP address of the peer entity with which this node shares the mobility security association.
.1.3.6.1.2.1.44.1.2.1.1.2,MIP-MIB::mipSecSPI,Unsigned32,not-accessible,,current,,The SPI is the 4-byte opaque index within the Mobility Security Association which selects the specific security parameters to be used to authenticate the peer, i.e. the rest of the variables in this MipSecAssocEntry.
.1.3.6.1.2.1.44.1.2.1.1.3,MIP-MIB::mipSecAlgorithmType,INTEGER,read-create,,current,other(1):md5(2),Type of security algorithm.
.1.3.6.1.2.1.44.1.2.1.1.4,MIP-MIB::mipSecAlgorithmMode,INTEGER,read-create,,current,other(1):prefixSuffix(2),Security mode used by this algorithm.
.1.3.6.1.2.1.44.1.2.1.1.5,MIP-MIB::mipSecKey,OCTET,read-create,,current,,The shared secret key for the security associations. Reading this object will always return zero length value.
.1.3.6.1.2.1.44.1.2.1.1.6,MIP-MIB::mipSecReplayMethod,INTEGER,read-create,,current,other(1):timestamps(2):nonces(3),The replay-protection method supported for this SPI within this Mobility Security Association.
.1.3.6.1.2.1.44.1.2.2,MIP-MIB::mipSecTotalViolations,Counter32,read-only,,current,,Total number of security violations in the entity
.1.3.6.1.2.1.44.1.2.3,MIP-MIB::mipSecViolationTable,,not-accessible,,current,,A table containing information about security violations.
.1.3.6.1.2.1.44.1.2.3.1,MIP-MIB::mipSecViolationEntry,,not-accessible,mipSecViolatorAddress,current,,Information about one particular security violation.
.1.3.6.1.2.1.44.1.2.3.1.1,MIP-MIB::mipSecViolatorAddress,IpAddress,accessible-for-notify,,current,,Violator's IP address. The violator is not necessary in the mipSecAssocTable.
.1.3.6.1.2.1.44.1.2.3.1.2,MIP-MIB::mipSecViolationCounter,Counter32,read-only,,current,,Total number of security violations for this peer.
.1.3.6.1.2.1.44.1.2.3.1.3,MIP-MIB::mipSecRecentViolationSPI,Integer32,read-only,,current,,SPI of the most recent security violation for this peer. If the security violation is due to an identification mismatch, then this is the SPI from the Mobile-Home Authentication Extension. If the security violation is due to an invalid authenticator, then this is the SPI from the offending authentication extension. In all other cases, it should be set to zero.
.1.3.6.1.2.1.44.1.2.3.1.4,MIP-MIB::mipSecRecentViolationTime,TimeTicks,read-only,,current,,Time of the most recent security violation for this peer.
.1.3.6.1.2.1.44.1.2.3.1.5,MIP-MIB::mipSecRecentViolationIDLow,Integer32,read-only,,current,,Low-order 32 bits of identification used in request or reply of the most recent security violation for this peer.
.1.3.6.1.2.1.44.1.2.3.1.6,MIP-MIB::mipSecRecentViolationIDHigh,Integer32,read-only,,current,,High-order 32 bits of identification used in request or reply of the most recent security violation for this peer.
.1.3.6.1.2.1.44.1.2.3.1.7,MIP-MIB::mipSecRecentViolationReason,INTEGER,read-only,,current,noMobilitySecurityAssociation(1):badAuthenticator(2):badIdentifier(3):badSPI(4):missingSecurityExtension(5):other(6),Reason for the most recent security violation for this peer.
.1.3.6.1.2.1.44.1.3,MIP-MIB::mipMN,,,,,,
.1.3.6.1.2.1.44.1.3.1,MIP-MIB::mnSystem,,,,,,
.1.3.6.1.2.1.44.1.3.1.1,MIP-MIB::mnState,INTEGER,read-only,,current,home(1):registered(2):pending(3):isolated(4):unknown(5),Indicates mobile node's state of Mobile IP: home, -- MN is connected to home network. registered, -- MN has registered on foreign network pending, -- MN has sent registration request and is waiting for the reply isolated, -- MN is isolated from network unknown -- MN can not determine its state.
.1.3.6.1.2.1.44.1.3.1.2,MIP-MIB::mnHomeAddress,IpAddress,read-only,,current,,An IP address that is assigned for an extended period of time to the mobile node. It remains unchanged regardless of the mobile node's current point of attachment.
.1.3.6.1.2.1.44.1.3.1.3,MIP-MIB::mnHATable,,not-accessible,,current,,A table containing all of the mobile node's potential home agents.
.1.3.6.1.2.1.44.1.3.1.3.1,MIP-MIB::mnHAEntry,,not-accessible,mnHAAddress,current,,Information for a particular Home Agent.
.1.3.6.1.2.1.44.1.3.1.3.1.1,MIP-MIB::mnHAAddress,IpAddress,not-accessible,,current,,IP address of mobile node's Home Agent.
.1.3.6.1.2.1.44.1.3.1.3.1.2,MIP-MIB::mnCurrentHA,INTEGER,read-only,,current,true(1):false(2),Whether this home agent is the current home agent for the mobile node. If it is true, the mobile node is registered with that home agent.
.1.3.6.1.2.1.44.1.3.1.3.1.3,MIP-MIB::mnHAStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status for this home agent entry. If the status is set to 'createAndGo' or 'active', then the mobile node can use mnHAAddress as a valid candidate for a home agent. If the status is set to 'destroy', then the mobile node should delete this row, and deregister from that home agent.
.1.3.6.1.2.1.44.1.3.2,MIP-MIB::mnDiscovery,,,,,,
.1.3.6.1.2.1.44.1.3.2.1,MIP-MIB::mnFATable,,not-accessible,,current,,A table containing all foreign agents that the mobile node knows about and their corresponding COA (care-of address). This COA is an address of a foreign agent with which the mobile node is registered. The table is updated when advertisements are received by the mobile node. If an advertisement expires, its entry(s) should be deleted from the table. One foreign agent can provide more than one COA in its advertisements.
.1.3.6.1.2.1.44.1.3.2.1.1,MIP-MIB::mnFAEntry,,not-accessible,mnFAAddress:mnCOA,current,,One pair of foreign agent IP address and COA for that foreign agent.
.1.3.6.1.2.1.44.1.3.2.1.1.1,MIP-MIB::mnFAAddress,IpAddress,read-only,,current,,Foreign agent's IP address.
.1.3.6.1.2.1.44.1.3.2.1.1.2,MIP-MIB::mnCOA,IpAddress,read-only,,current,,A care-of address being offered by this foreign agent or a co-located care-of address which the mobile node has associated with one of its own network interfaces.
.1.3.6.1.2.1.44.1.3.2.2,MIP-MIB::mnRecentAdvReceived,,,,,,
.1.3.6.1.2.1.44.1.3.2.2.1,MIP-MIB::mnAdvSourceAddress,IpAddress,read-only,,current,,The source IP address of the most recently received Agent Advertisement. This address could be the address of a home agent or a foreign agent.
.1.3.6.1.2.1.44.1.3.2.2.2,MIP-MIB::mnAdvSequence,INTEGER,read-only,,current,,The sequence number of the most recently received advertisement. The sequence number ranges from 0 to 0xffff. After the sequence number attains the value 0xffff, it will roll over to 256.
.1.3.6.1.2.1.44.1.3.2.2.3,MIP-MIB::mnAdvFlags,BITS,read-only,,current,vjCompression(0):gre(1):minEnc(2):foreignAgent(3):homeAgent(4):busy(5):regRequired(6),The flags are contained in the 7th byte in the extension of the most recently received mobility agent advertisement: vjCompression -- Agent supports Van Jacobson compression gre -- Agent offers Generice Routing Encapsulation minEnc, -- Agent offers Minimal Encapsulation foreignAgent, -- Agent is a Foreign Agent homeAgent, -- Agent is a Home Agent busy, -- Foreign Agent is busy regRequired, -- FA registration is required.
.1.3.6.1.2.1.44.1.3.2.2.4,MIP-MIB::mnAdvMaxRegLifetime,INTEGER,read-only,,current,,The longest lifetime in seconds that the agent is willing to accept in any registration request.
.1.3.6.1.2.1.44.1.3.2.2.5,MIP-MIB::mnAdvMaxAdvLifetime,INTEGER,read-only,,current,,The maximum length of time that the Advertisement is considered valid in the absence of further Advertisements.
.1.3.6.1.2.1.44.1.3.2.2.6,MIP-MIB::mnAdvTimeReceived,TimeTicks,read-only,,current,,The time at which the most recently received advertisement was received.
.1.3.6.1.2.1.44.1.3.2.3,MIP-MIB::mnSolicitationsSent,Counter32,read-only,,current,,Total number of Solicitation sent by the mobile node.
.1.3.6.1.2.1.44.1.3.2.4,MIP-MIB::mnAdvertisementsReceived,Counter32,read-only,,current,,Total number of advertisements received by the mobile node.
.1.3.6.1.2.1.44.1.3.2.5,MIP-MIB::mnAdvsDroppedInvalidExtension,Counter32,read-only,,current,,Total number of advertisements dropped by the mobile node due to both poorly formed extensions and unrecognized extensions with extension number in the range 0-127.
.1.3.6.1.2.1.44.1.3.2.6,MIP-MIB::mnAdvsIgnoredUnknownExtension,Counter32,read-only,,current,,Total number of unrecognized extensions in the range 128-255 that were ignored by the mobile node.
.1.3.6.1.2.1.44.1.3.2.7,MIP-MIB::mnMoveFromHAToFA,Counter32,read-only,,current,,Number of times that the mobile node has decided to move from its home network to a foreign network.
.1.3.6.1.2.1.44.1.3.2.8,MIP-MIB::mnMoveFromFAToFA,Counter32,read-only,,current,,Number of times that the mobile node has decided to move from one foreign network to another foreign network.
.1.3.6.1.2.1.44.1.3.2.9,MIP-MIB::mnMoveFromFAToHA,Counter32,read-only,,current,,Number of times that the mobile node has decided to move from a foreign network to its home network.
.1.3.6.1.2.1.44.1.3.2.10,MIP-MIB::mnGratuitousARPsSend,Counter32,read-only,,current,,Total number of Gratuitous ARPs sent by mobile node in order to clear out any stale ARP entries in the ARP caches of nodes on the home network.
.1.3.6.1.2.1.44.1.3.2.11,MIP-MIB::mnAgentRebootsDectected,Counter32,read-only,,current,,Total number of agent reboots detected by the mobile node through sequence number of the advertisement.
.1.3.6.1.2.1.44.1.3.3,MIP-MIB::mnRegistration,,,,,,
.1.3.6.1.2.1.44.1.3.3.1,MIP-MIB::mnRegistrationTable,,not-accessible,,current,,A table containing information about the mobile node's attempted registration(s). The mobile node updates this table based upon Registration Requests sent and Registration Replies received in response to these requests. Certain variables within this table are also updated if when Registration Requests are retransmitted.
.1.3.6.1.2.1.44.1.3.3.1.1,MIP-MIB::mnRegistrationEntry,,not-accessible,mnRegAgentAddress:mnRegCOA,current,,Information about one registration attempt.
.1.3.6.1.2.1.44.1.3.3.1.1.1,MIP-MIB::mnRegAgentAddress,IpAddress,read-only,,current,,IP address of the agent as used in the destination IP address of the Registration Request. The agent may be a home agent or a foreign agent.
.1.3.6.1.2.1.44.1.3.3.1.1.2,MIP-MIB::mnRegCOA,IpAddress,read-only,,current,,Care-of address for the registration.
.1.3.6.1.2.1.44.1.3.3.1.1.3,MIP-MIB::mnRegFlags,BITS,read-only,,current,vjCompression(0):gre(1):minEnc(2):decapsulationbyMN(3):broadcastDatagram(4):simultaneousBindings(5),Registration flags sent by the mobile node. It is the second byte in the Mobile IP Registratation Request message.
.1.3.6.1.2.1.44.1.3.3.1.1.4,MIP-MIB::mnRegIDLow,Integer32,read-only,,current,,Low-order 32 bits of the Identification used in that registration by the mobile node.
.1.3.6.1.2.1.44.1.3.3.1.1.5,MIP-MIB::mnRegIDHigh,Integer32,read-only,,current,,High-order 32 bits of the Identification used in that registration by the mobile node.
.1.3.6.1.2.1.44.1.3.3.1.1.6,MIP-MIB::mnRegTimeRequested,Integer32,read-only,,current,,If the registration is pending, then this is the lifetime requested by the mobile node (in seconds). If the registration has been accepted, then this is the lifetime actually granted by the home agent in the reply.
.1.3.6.1.2.1.44.1.3.3.1.1.7,MIP-MIB::mnRegTimeRemaining,Gauge32,read-only,,current,,The number of seconds remaining until this registration expires. It has the same initial value as mnRegTimeRequested and is only valid if mnRegIsAccepted is TRUE.
.1.3.6.1.2.1.44.1.3.3.1.1.8,MIP-MIB::mnRegTimeSent,TimeTicks,read-only,,current,,The time when the last (re-)transmission occured.
.1.3.6.1.2.1.44.1.3.3.1.1.9,MIP-MIB::mnRegIsAccepted,INTEGER,read-only,,current,true(1):false(2),true(1) if the mobile node has received a Registration Reply indicating that service has been accepted; false(2) otherwise. false(2) implies that the registration is still pending.
.1.3.6.1.2.1.44.1.3.3.1.1.10,MIP-MIB::mnCOAIsLocal,INTEGER,read-only,,current,true(1):false(2),Whether the COA is local to (dynamically acquired by) the mobile node or not. If it is false(2), the COA is an address of the foreign agent.
.1.3.6.1.2.1.44.1.3.3.2,MIP-MIB::mnRegRequestsSent,Counter32,read-only,,current,,Total number of registration requests sent by the mobile node. This does not include deregistrations (those with Lifetime equal to zero).
.1.3.6.1.2.1.44.1.3.3.3,MIP-MIB::mnDeRegRequestsSent,Counter32,read-only,,current,,Total number of deregistration requests sent by the mobile node (those with Lifetime equal to zero).
.1.3.6.1.2.1.44.1.3.3.4,MIP-MIB::mnRegRepliesRecieved,Counter32,read-only,,current,,Total number of registration replies received by the mobile node in which the Lifetime is greater than zero.
.1.3.6.1.2.1.44.1.3.3.5,MIP-MIB::mnDeRegRepliesRecieved,Counter32,read-only,,current,,Total number of (de)registration replies received by the mobile node in which the Lifetime is equal to zero.
.1.3.6.1.2.1.44.1.3.3.6,MIP-MIB::mnRepliesInvalidHomeAddress,Counter32,read-only,,current,,Total number of replies with invalid home address for the mobile node.
.1.3.6.1.2.1.44.1.3.3.7,MIP-MIB::mnRepliesUnknownHA,Counter32,read-only,,current,,Total number of replies with unknown home agents (not in home agent table).
.1.3.6.1.2.1.44.1.3.3.8,MIP-MIB::mnRepliesUnknownFA,Counter32,read-only,,current,,Total number of replies with unknown foreign agents if replies relayed through foreign agent.
.1.3.6.1.2.1.44.1.3.3.9,MIP-MIB::mnRepliesInvalidID,Counter32,read-only,,current,,Total number of replies with invalid Identification fields.
.1.3.6.1.2.1.44.1.3.3.10,MIP-MIB::mnRepliesDroppedInvalidExtension,Counter32,read-only,,current,,Total number of Registration Replies dropped by the mobile node due to both poorly formed extensions and unrecognized extensions with extension number in the range 0-127.
.1.3.6.1.2.1.44.1.3.3.11,MIP-MIB::mnRepliesIgnoredUnknownExtension,Counter32,read-only,,current,,Total number of Registration Replies that contained one or more unrecognized extensions in the range 128-255 that were ignored by the mobile node.
.1.3.6.1.2.1.44.1.3.3.12,MIP-MIB::mnRepliesHAAuthenticationFailure,Counter32,read-only,,current,,Total number of replies without a valid Home Agent to Mobile Node authenticator.
.1.3.6.1.2.1.44.1.3.3.13,MIP-MIB::mnRepliesFAAuthenticationFailure,Counter32,read-only,,current,,Total number of replies without a valid Foreign Agent to Mobile Node authenticator.
.1.3.6.1.2.1.44.1.3.3.14,MIP-MIB::mnRegRequestsAccepted,Counter32,read-only,,current,,Total number of registration requests accepted by the mobile node's home agent (Code 0 and Code 1).
.1.3.6.1.2.1.44.1.3.3.15,MIP-MIB::mnRegRequestsDeniedByHA,Counter32,read-only,,current,,Total number of registration requests denied by mobile node's home agent (Sum of Code 128 through Code 191).
.1.3.6.1.2.1.44.1.3.3.16,MIP-MIB::mnRegRequestsDeniedByFA,Counter32,read-only,,current,,Total number of registration requests denied by the foreign agent (Sum of Codes 64 through Code 127).
.1.3.6.1.2.1.44.1.3.3.17,MIP-MIB::mnRegRequestsDeniedByHADueToID,Counter32,read-only,,current,,Total number of Registration Request denied by home agent due to identification mismatch.
.1.3.6.1.2.1.44.1.3.3.18,MIP-MIB::mnRegRequestsWithDirectedBroadcast,Counter32,read-only,,current,,Total number of Registration Requests sent by mobile node with a directed broadcast address in the home agent field.
.1.3.6.1.2.1.44.1.4,MIP-MIB::mipMA,,,,,,
.1.3.6.1.2.1.44.1.4.2,MIP-MIB::maAdvertisement,,,,,,
.1.3.6.1.2.1.44.1.4.2.1,MIP-MIB::maAdvConfigTable,,not-accessible,,current,,A table containing configurable advertisement parameters for all advertisement interfaces in the mobility agent.
.1.3.6.1.2.1.44.1.4.2.1.1,MIP-MIB::maAdvConfigEntry,,not-accessible,maInterfaceAddress,current,,Advertisement parameters for one advertisement interface.
.1.3.6.1.2.1.44.1.4.2.1.1.1,MIP-MIB::maInterfaceAddress,IpAddress,not-accessible,,current,,IP address for advertisement interface.
.1.3.6.1.2.1.44.1.4.2.1.1.2,MIP-MIB::maAdvMaxRegLifetime,Integer32,read-create,,current,,The longest lifetime in seconds that mobility agent is willing to accept in any Registration Request.
.1.3.6.1.2.1.44.1.4.2.1.1.3,MIP-MIB::maAdvPrefixLengthInclusion,INTEGER,read-create,,current,true(1):false(2),Whether the advertisement should include the Prefix- Lengths Extension. If it is true, all advertisements sent over this interface should include the Prefix-Lengths Extension.
.1.3.6.1.2.1.44.1.4.2.1.1.4,MIP-MIB::maAdvAddress,IpAddress,read-create,,current,,The IP destination address to be used for advertisements sent from the interface. The only permissible values are the all-systems multicast address (224.0.0.1) or the limited-broadcast address (255.255.255.255).
.1.3.6.1.2.1.44.1.4.2.1.1.5,MIP-MIB::maAdvMaxInterval,Integer32,read-create,,current,,The maximum time in seconds between successive transmissions of Agent Advertisements from this interface.
.1.3.6.1.2.1.44.1.4.2.1.1.6,MIP-MIB::maAdvMinInterval,Integer32,read-create,,current,,The minimum time in seconds between successive transmissions of Agent Advertisements from this interface.
.1.3.6.1.2.1.44.1.4.2.1.1.7,MIP-MIB::maAdvMaxAdvLifetime,Integer32,read-create,,current,,The time (in seconds) to be placed in the Lifetime field of the RFC 1256-portion of the Agent Advertisements sent over this interface.
.1.3.6.1.2.1.44.1.4.2.1.1.8,MIP-MIB::maAdvResponseSolicitationOnly,INTEGER,read-create,,current,true(1):false(2),The flag indicates whether the advertisement from that interface should be sent only in response to an Agent Solicitation message.
.1.3.6.1.2.1.44.1.4.2.1.1.9,MIP-MIB::maAdvStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status for the agent advertisement table. If this column status is 'active', the manager should not change any column in the row.
.1.3.6.1.2.1.44.1.4.2.2,MIP-MIB::maAdvertisementsSent,Counter32,read-only,,current,,Total number of advertisements sent by the mobility agent.
.1.3.6.1.2.1.44.1.4.2.3,MIP-MIB::maAdvsSentForSolicitation,Counter32,read-only,,current,,Total number of advertisements sent by mobility agent in response to mobile node solicitations.
.1.3.6.1.2.1.44.1.4.2.4,MIP-MIB::maSolicitationsReceived,Counter32,read-only,,current,,Total number of solicitations received by the mobility agent.
.1.3.6.1.2.1.44.1.5,MIP-MIB::mipFA,,,,,,
.1.3.6.1.2.1.44.1.5.1,MIP-MIB::faSystem,,,,,,
.1.3.6.1.2.1.44.1.5.1.1,MIP-MIB::faCOATable,,not-accessible,,current,,A table containing all of the care-of addresses (COAs) supported by the foreign agent. New entries can be added to the table. The order of entries in the faCOATAble is also the order in which the COAs are listed in the Agent Advertisement.
.1.3.6.1.2.1.44.1.5.1.1.1,MIP-MIB::faCOAEntry,,not-accessible,faSupportedCOA,current,,Entry of COA
.1.3.6.1.2.1.44.1.5.1.1.1.1,MIP-MIB::faSupportedCOA,IpAddress,not-accessible,,current,,Care-of-address supported by this foreign agent.
.1.3.6.1.2.1.44.1.5.1.1.1.2,MIP-MIB::faCOAStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status for COA entry.
.1.3.6.1.2.1.44.1.5.2,MIP-MIB::faAdvertisement,,,,,,
.1.3.6.1.2.1.44.1.5.2.1,MIP-MIB::faIsBusy,INTEGER,read-only,,current,true(1):false(2),Whether or not the foreign agent is too busy to accept additional registrations. If true(1), the agent is busy and any Agent advertisements sent from this agent should have the 'B' bit set to 1.
.1.3.6.1.2.1.44.1.5.2.2,MIP-MIB::faRegistrationRequired,INTEGER,read-write,,current,true(1):false(2),Whether or not this foreign agent requires registration even from those mobile nodes that have acquired their own, colocated care-of address. If true(1), registration is required and any Agent Advertisements sent from this agent should have the 'R' bit set to 1.
.1.3.6.1.2.1.44.1.5.3,MIP-MIB::faRegistration,,,,,,
.1.3.6.1.2.1.44.1.5.3.1,MIP-MIB::faVisitorTable,,not-accessible,,current,,A table containing the foreign agent's visitor list. The foreign agent updates this table in response to registration events from mobile nodes.
.1.3.6.1.2.1.44.1.5.3.1.1,MIP-MIB::faVisitorEntry,,not-accessible,faVisitorIPAddress,current,,Information for one visitor.
.1.3.6.1.2.1.44.1.5.3.1.1.1,MIP-MIB::faVisitorIPAddress,IpAddress,read-only,,current,,Source IP address of visitor's Registration Request.
.1.3.6.1.2.1.44.1.5.3.1.1.2,MIP-MIB::faVisitorHomeAddress,IpAddress,read-only,,current,,Home (IP) address of visiting mobile node.
.1.3.6.1.2.1.44.1.5.3.1.1.3,MIP-MIB::faVisitorHomeAgentAddress,IpAddress,read-only,,current,,Home agent IP address for that visiting mobile node.
.1.3.6.1.2.1.44.1.5.3.1.1.4,MIP-MIB::faVisitorTimeGranted,Integer32,read-only,,current,,The lifetime in seconds granted to the mobile node for this registration. Only valid if faVisitorRegIsAccepted is true(1).
.1.3.6.1.2.1.44.1.5.3.1.1.5,MIP-MIB::faVisitorTimeRemaining,Gauge32,read-only,,current,,The number of seconds remaining until the registration is expired. It has the same initial value as faVisitorTimeGranted, and is counted down by the foreign agent.
.1.3.6.1.2.1.44.1.5.3.1.1.6,MIP-MIB::faVisitorRegFlags,BITS,read-only,,current,vjCompression(0):gre(1):minEnc(2):decapsulationbyMN(3):broadcastDatagram(4):simultaneousBindings(5),Registration flags sent by mobile node.
.1.3.6.1.2.1.44.1.5.3.1.1.7,MIP-MIB::faVisitorRegIDLow,Integer32,read-only,,current,,Low 32 bits of Identification used in that registration by the mobile node.
.1.3.6.1.2.1.44.1.5.3.1.1.8,MIP-MIB::faVisitorRegIDHigh,Integer32,read-only,,current,,High 32 bits of Identification used in that registration by the mobile node.
.1.3.6.1.2.1.44.1.5.3.1.1.9,MIP-MIB::faVisitorRegIsAccepted,INTEGER,read-only,,current,true(1):false(2),Whether the registration has been accepted or not. If it is false(2), this registration is still pending for reply.
.1.3.6.1.2.1.44.1.5.3.2,MIP-MIB::faRegRequestsReceived,Counter32,read-only,,current,,Total number of valid Registration Requests received.
.1.3.6.1.2.1.44.1.5.3.3,MIP-MIB::faRegRequestsRelayed,Counter32,read-only,,current,,Total number of Registration Requests relayed to home agent by foreign agent.
.1.3.6.1.2.1.44.1.5.3.4,MIP-MIB::faReasonUnspecified,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- reason unspecified (Code 64).
.1.3.6.1.2.1.44.1.5.3.5,MIP-MIB::faAdmProhibited,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- administratively prohibited (Code 65).
.1.3.6.1.2.1.44.1.5.3.6,MIP-MIB::faInsufficientResource,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- insufficient resources (Code 66).
.1.3.6.1.2.1.44.1.5.3.7,MIP-MIB::faMNAuthenticationFailure,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- mobile node failed authentication (Code 67).
.1.3.6.1.2.1.44.1.5.3.8,MIP-MIB::faRegLifetimeTooLong,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- requested lifetime too long (Code 69).
.1.3.6.1.2.1.44.1.5.3.9,MIP-MIB::faPoorlyFormedRequests,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- poorly formed request (Code 70).
.1.3.6.1.2.1.44.1.5.3.10,MIP-MIB::faEncapsulationUnavailable,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- requested encapsulation unavailable (Code 72).
.1.3.6.1.2.1.44.1.5.3.11,MIP-MIB::faVJCompressionUnavailable,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- requested Van Jacobson header compression unavailable (Code 73).
.1.3.6.1.2.1.44.1.5.3.12,MIP-MIB::faHAUnreachable,Counter32,read-only,,current,,Total number of Registration Requests denied by foreign agent -- home agent unreachable (Codes 80-95).
.1.3.6.1.2.1.44.1.5.3.13,MIP-MIB::faRegRepliesRecieved,Counter32,read-only,,current,,Total number of well-formed Registration Replies received by foreign agent.
.1.3.6.1.2.1.44.1.5.3.14,MIP-MIB::faRegRepliesRelayed,Counter32,read-only,,current,,Total number of valid Registration Replies relayed to the mobile node by foreign agent.
.1.3.6.1.2.1.44.1.5.3.15,MIP-MIB::faHAAuthenticationFailure,Counter32,read-only,,current,,Total number of Registration Replies denied by foreign agent -- home agent failed authentication (Code 68).
.1.3.6.1.2.1.44.1.5.3.16,MIP-MIB::faPoorlyFormedReplies,Counter32,read-only,,current,,Total number of Registration Replies denied by foreign agent -- poorly formed reply (Code 71).
.1.3.6.1.2.1.44.1.6,MIP-MIB::mipHA,,,,,,
.1.3.6.1.2.1.44.1.6.3,MIP-MIB::haRegistration,,,,,,
.1.3.6.1.2.1.44.1.6.3.1,MIP-MIB::haMobilityBindingTable,,not-accessible,,current,,A table containing the home agent's mobility binding list. The home agent updates this table in response to registration events from mobile nodes.
.1.3.6.1.2.1.44.1.6.3.1.1,MIP-MIB::haMobilityBindingEntry,,not-accessible,haMobilityBindingMN:haMobilityBindingCOA,current,,An entry on the mobility binding list.
.1.3.6.1.2.1.44.1.6.3.1.1.1,MIP-MIB::haMobilityBindingMN,IpAddress,read-only,,current,,Mobile node's home (IP) address.
.1.3.6.1.2.1.44.1.6.3.1.1.2,MIP-MIB::haMobilityBindingCOA,IpAddress,read-only,,current,,Mobile node's care-of-address. One mobile node can have multiple bindings with different care-of-addresses.
.1.3.6.1.2.1.44.1.6.3.1.1.3,MIP-MIB::haMobilityBindingSourceAddress,IpAddress,read-only,,current,,IP source address of the Registration Request as received by the home agent. Will be either a mobile node's co-located care-of address or an address of the foreign agent.
.1.3.6.1.2.1.44.1.6.3.1.1.4,MIP-MIB::haMobilityBindingRegFlags,BITS,read-only,,current,vjCompression(0):gre(1):minEnc(2):decapsulationbyMN(3):broadcastDatagram(4):simultaneousBindings(5),Registration flags sent by mobile node.
.1.3.6.1.2.1.44.1.6.3.1.1.5,MIP-MIB::haMobilityBindingRegIDLow,Integer32,read-only,,current,,Low 32 bits of Identification used in that binding by the mobile node.
.1.3.6.1.2.1.44.1.6.3.1.1.6,MIP-MIB::haMobilityBindingRegIDHigh,Integer32,read-only,,current,,High 32 bits of Identification used in that binding by the mobile node.
.1.3.6.1.2.1.44.1.6.3.1.1.7,MIP-MIB::haMobilityBindingTimeGranted,Integer32,read-only,,current,,The lifetime in seconds granted to the mobile node for this registration.
.1.3.6.1.2.1.44.1.6.3.1.1.8,MIP-MIB::haMobilityBindingTimeRemaining,Gauge32,read-only,,current,,The number of seconds remaining until the registration is expired. It has the same initial value as haMobilityBindingTimeGranted, and is counted down by the home agent.
.1.3.6.1.2.1.44.1.6.3.2,MIP-MIB::haCounterTable,,not-accessible,,current,,A table containing registration statistics for all mobile nodes authorized to use this home agent.
.1.3.6.1.2.1.44.1.6.3.2.1,MIP-MIB::haCounterEntry,,not-accessible,haMobilityBindingMN,current,,Registration statistics for one mobile node.
.1.3.6.1.2.1.44.1.6.3.2.1.2,MIP-MIB::haServiceRequestsAccepted,Counter32,read-only,,current,,Total number of service requests for the mobile node accepted by the home agent (Code 0 + Code 1).
.1.3.6.1.2.1.44.1.6.3.2.1.3,MIP-MIB::haServiceRequestsDenied,Counter32,read-only,,current,,Total number of service requests for the mobile node denied by the home agent (sum of all registrations denied with Code 128 through Code 159).
.1.3.6.1.2.1.44.1.6.3.2.1.4,MIP-MIB::haOverallServiceTime,Gauge32,read-only,,current,,Overall service time (in seconds) that has accumulated for the mobile node since the home agent last rebooted.
.1.3.6.1.2.1.44.1.6.3.2.1.5,MIP-MIB::haRecentServiceAcceptedTime,TimeTicks,read-only,,current,,The time at which the most recent Registration Request was accepted by the home agent for this mobile node.
.1.3.6.1.2.1.44.1.6.3.2.1.6,MIP-MIB::haRecentServiceDeniedTime,TimeTicks,read-only,,current,,The time at which the most recent Registration Request was denied by the home agent for this mobile node.
.1.3.6.1.2.1.44.1.6.3.2.1.7,MIP-MIB::haRecentServiceDeniedCode,INTEGER,read-only,,current,reasonUnspecified(128):admProhibited(129):insufficientResource(130):mnAuthenticationFailure(131):faAuthenticationFailure(132):idMismatch(133):poorlyFormedRequest(134):tooManyBindings(135):unknownHA(136),The Code indicating the reason why the most recent Registration Request for this mobile node was rejected by the home agent.
.1.3.6.1.2.1.44.1.6.3.3,MIP-MIB::haRegistrationAccepted,Counter32,read-only,,current,,Total number of Registration Requests accepted by home agent (Code 0).
.1.3.6.1.2.1.44.1.6.3.4,MIP-MIB::haMultiBindingUnsupported,Counter32,read-only,,current,,Total number of Registration Requests accepted by home agent -- simultaneous mobility bindings unsupported (Code 1).
.1.3.6.1.2.1.44.1.6.3.5,MIP-MIB::haReasonUnspecified,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- reason unspecified (Code 128).
.1.3.6.1.2.1.44.1.6.3.6,MIP-MIB::haAdmProhibited,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- administratively prohibited (Code 129).
.1.3.6.1.2.1.44.1.6.3.7,MIP-MIB::haInsufficientResource,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- insufficient resources (Code 130).
.1.3.6.1.2.1.44.1.6.3.8,MIP-MIB::haMNAuthenticationFailure,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- mobile node failed authentication (Code 131).
.1.3.6.1.2.1.44.1.6.3.9,MIP-MIB::haFAAuthenticationFailure,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- foreign agent failed authentication (Code 132).
.1.3.6.1.2.1.44.1.6.3.10,MIP-MIB::haIDMismatch,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- Identification mismatch (Code 133).
.1.3.6.1.2.1.44.1.6.3.11,MIP-MIB::haPoorlyFormedRequest,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- poorly formed request (Code 134).
.1.3.6.1.2.1.44.1.6.3.12,MIP-MIB::haTooManyBindings,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- too many simultaneous mobility bindings (Code 135).
.1.3.6.1.2.1.44.1.6.3.13,MIP-MIB::haUnknownHA,Counter32,read-only,,current,,Total number of Registration Requests denied by home agent -- unknown home agent address (Code 136).
.1.3.6.1.2.1.44.1.6.3.14,MIP-MIB::haGratuitiousARPsSent,Counter32,read-only,,current,,Total number of gratuition ARPs sent by the home agent on behalf of mobile nodes.
.1.3.6.1.2.1.44.1.6.3.15,MIP-MIB::haProxyARPsSent,Counter32,read-only,,current,,Total number of proxy ARPs sent by the home agent on behalf of mobile nodes.
.1.3.6.1.2.1.44.1.6.3.16,MIP-MIB::haRegRequestsReceived,Counter32,read-only,,current,,Total number of Registration Requests received by home agent.
.1.3.6.1.2.1.44.1.6.3.17,MIP-MIB::haDeRegRequestsReceived,Counter32,read-only,,current,,Total number of Registration Requests received by the home agent with a Lifetime of zero (requests to deregister).
.1.3.6.1.2.1.44.1.6.3.18,MIP-MIB::haRegRepliesSent,Counter32,read-only,,current,,Total number of Registration Replies sent by the home agent.
.1.3.6.1.2.1.44.1.6.3.19,MIP-MIB::haDeRegRepliesSent,Counter32,read-only,,current,,Total number of Registration Replies sent by the home agent in response to requests to deregister.
.1.3.6.1.2.1.44.2,MIP-MIB::mipMIBNotificationPrefix,,,,,,
.1.3.6.1.2.1.44.2.0,MIP-MIB::mipMIBNotifications,,,,,,
.1.3.6.1.2.1.44.2.0.1,MIP-MIB::mipAuthFailure,,,,,,The mipAuthFailure indicates that the Mobile IP entity has an authentication failure when it validates the mobile Registration Request or Reply. Implementation of this trap is optional.
.1.3.6.1.2.1.44.3,MIP-MIB::mipMIBConformance,,,,,,
.1.3.6.1.2.1.44.3.1,MIP-MIB::mipGroups,,,,,,
.1.3.6.1.2.1.44.3.1.1,MIP-MIB::mipSystemGroup,,,,,,A collection of objects providing the basic Mobile IP entity's management information.
.1.3.6.1.2.1.44.3.1.2,MIP-MIB::mipSecAssociationGroup,,,,,,A collection of objects providing the management information for security associations of Mobile IP entities.
.1.3.6.1.2.1.44.3.1.3,MIP-MIB::mipSecViolationGroup,,,,,,A collection of objects providing the management information for security violation logging of Mobile IP entities.
.1.3.6.1.2.1.44.3.1.4,MIP-MIB::mnSystemGroup,,,,,,A collection of objects providing the basic management information for mobile nodes.
.1.3.6.1.2.1.44.3.1.5,MIP-MIB::mnDiscoveryGroup,,,,,,A collection of objects providing management information for the Agent Discovery function within a mobile node.
.1.3.6.1.2.1.44.3.1.6,MIP-MIB::mnRegistrationGroup,,,,,,A collection of objects providing management information for the registration function within a mobile node.
.1.3.6.1.2.1.44.3.1.7,MIP-MIB::maAdvertisementGroup,,,,,,A collection of objects providing management information for the Agent Advertisement function within mobility agents.
.1.3.6.1.2.1.44.3.1.8,MIP-MIB::faSystemGroup,,,,,,A collection of objects providing the basic management information for foreign agents.
.1.3.6.1.2.1.44.3.1.9,MIP-MIB::faAdvertisementGroup,,,,,,A collection of objects providing supplemental management information for the Agent Advertisement function within a foreign agent.
.1.3.6.1.2.1.44.3.1.10,MIP-MIB::faRegistrationGroup,,,,,,A collection of objects providing management information for the registration function within a foreign agent.
.1.3.6.1.2.1.44.3.1.11,MIP-MIB::haRegistrationGroup,,,,,,A collection of objects providing management information for the registration function within a home agent.
.1.3.6.1.2.1.44.3.1.12,MIP-MIB::haRegNodeCountersGroup,,,,,,A collection of objects providing management information for counters related to the registration function within a home agent.
.1.3.6.1.2.1.44.3.1.13,MIP-MIB::mipSecNotificationsGroup,,,,,,The notification related to security violations.
.1.3.6.1.2.1.44.3.2,MIP-MIB::mipCompliances,,,,,,
.1.3.6.1.2.1.44.3.2.1,MIP-MIB::mipCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the Mobile IP MIB.
.1.3.6.1.2.1.46,DLSW-MIB::dlsw,,,,,,This MIB module contains objects to manage Data Link Switches.
.1.3.6.1.2.1.46.1,DLSW-MIB::dlswMIB,,,,,,
.1.3.6.1.2.1.46.1.0,DLSW-MIB::dlswTraps,,,,,,
.1.3.6.1.2.1.46.1.0.1,DLSW-MIB::dlswTrapTConnPartnerReject,,,,,,This trap is sent each time a transport connection is rejected by a partner DLSw during Capabilities Exchanges. The emission of this trap is controlled by dlswTrapCntlTConnPartnerReject.
.1.3.6.1.2.1.46.1.0.2,DLSW-MIB::dlswTrapTConnProtViolation,,,,,,This trap is sent each time a protocol violation is detected for a transport connection. The emission of this trap is controlled by dlswTrapCntlTConnProtViolation.
.1.3.6.1.2.1.46.1.0.3,DLSW-MIB::dlswTrapTConnUp,,,,,,This trap is sent each time a transport connection enters `connected' state. The emission of this trap is controlled by dlswTrapCntlTConn.
.1.3.6.1.2.1.46.1.0.4,DLSW-MIB::dlswTrapTConnDown,,,,,,This trap is sent each time a transport connection enters `disconnected' state. The emission of this trap is controlled by dlswTrapCntlTConn.
.1.3.6.1.2.1.46.1.0.5,DLSW-MIB::dlswTrapCircuitUp,,,,,,This trap is sent each time a circuit enters `connected' state. The emission of this trap is controlled by dlswTrapCntlCircuit.
.1.3.6.1.2.1.46.1.0.6,DLSW-MIB::dlswTrapCircuitDown,,,,,,This trap is sent each time a circuit enters `disconnected' state. The emission of this trap is controlled by dlswTrapCntlCircuit.
.1.3.6.1.2.1.46.1.1,DLSW-MIB::dlswNode,,,,,,
.1.3.6.1.2.1.46.1.1.1,DLSW-MIB::dlswNodeVersion,OCTET,read-only,,current,,This value identifies the particular version of the DLSw standard supported by this DLSw. The first octet is a hexadecimal value representing the DLSw standard Version number of this DLSw, and the second is a hexadecimal value representing the DLSw standard Release number. This information is reported in DLSw Capabilities Exchange.
.1.3.6.1.2.1.46.1.1.2,DLSW-MIB::dlswNodeVendorID,OCTET,read-only,,current,,The value identifies the manufacturer's IEEE-assigned organizationally Unique Identifier (OUI) of this DLSw. This information is reported in DLSw Capabilities Exchange.
.1.3.6.1.2.1.46.1.1.3,DLSW-MIB::dlswNodeVersionString,OCTET,read-only,,current,,This string gives product-specific information about this DLSw (e.g., product name, code release and fix level). This flows in Capabilities Exchange messages.
.1.3.6.1.2.1.46.1.1.4,DLSW-MIB::dlswNodeStdPacingSupport,INTEGER,read-only,,current,none(1):adaptiveRcvWindow(2):fixedRcvWindow(3),Circuit pacing, as defined in the DLSw Standard, allows each of the two DLSw nodes on a circuit to control the amount of data the other is permitted to send to them. This object reflects the level of support the DLSw node has for this protocol. (1) means the node has no support for the standard circuit pacing flows; it may use RFC 1434+ methods only, or a proprietary flow control scheme. (2) means the node supports the standard scheme and can vary the window sizes it grants as a data receiver. (3) means the node supports the standard scheme but never varies its receive window size.
.1.3.6.1.2.1.46.1.1.5,DLSW-MIB::dlswNodeStatus,INTEGER,read-write,,current,active(1):inactive(2),The status of the DLSw part of the system. Changing the value from active to inactive causes DLSw to take the following actions - (1) it disconnects all circuits through all DLSw partners, (2) it disconnects all transport connections to all DLSw partners, (3) it disconnects all local DLC connections, and (4) it stops processing all DLC connection set-up traffic. Since these are destructive actions, the user should query the circuit and transport connection tables in advance to understand the effect this action will have. Changing the value from inactive to active causes DLSw to come up in its initial state, i.e., transport connections established and ready to bring up circuits.
.1.3.6.1.2.1.46.1.1.6,DLSW-MIB::dlswNodeUpTime,TimeTicks,read-only,,current,,The amount of time (in hundredths of a second) since the DLSw portion of the system was last re-initialized. That is, if dlswState is in the active state, the time the dlswState entered the active state. It will remain zero if dlswState is in the inactive state.
.1.3.6.1.2.1.46.1.1.7,DLSW-MIB::dlswNodeVirtualSegmentLFSize,INTEGER,read-write,,current,lfs516(516):lfs635(635):lfs754(754):lfs873(873):lfs993(993):lfs1112(1112):lfs1231(1231):lfs1350(1350):lfs1470(1470):lfs1542(1542):lfs1615(1615):lfs1688(1688):lfs1761(1761):lfs1833(1833):lfs1906(1906):lfs1979(1979):lfs2052(2052):lfs2345(2345):lfs2638(2638):lfs2932(2932):lfs3225(3225):lfs3518(3518):lfs3812(3812):lfs4105(4105):lfs4399(4399):lfs4865(4865):lfs5331(5331):lfs5798(5798):lfs6264(6264):lfs6730(6730):lfs7197(7197):lfs7663(7663):lfs8130(8130):lfs8539(8539):lfs8949(8949):lfs9358(9358):lfs9768(9768):lfs10178(10178):lfs10587(10587):lfs10997(10997):lfs11407(11407):lfs12199(12199):lfs12992(12992):lfs13785(13785):lfs14578(14578):lfs15370(15370):lfs16163(16163):lfs16956(16956):lfs17749(17749):lfs20730(20730):lfs23711(23711):lfs26693(26693):lfs29674(29674):lfs32655(32655):lfs38618(38618):lfs41600(41600):lfs44591(44591):lfs47583(47583):lfs50575(50575):lfs53567(53567):lfs56559(56559):lfs59551(59551):lfs65535(65535),The largest frame size (including DLC header and info field but not any MAC-level or framing octets) this DLSw can forward on any path through itself. This object can represent any box- level frame size forwarding restriction (e.g., from the use of fixed-size buffers). Some DLSw implementations will have no such restriction. This value will affect the LF size of circuits during circuit creation. The LF size of an existing circuit can be found in the RIF (Routing Information Field).
.1.3.6.1.2.1.46.1.1.8,DLSW-MIB::dlswNodeResourceNBExclusivity,INTEGER,read-write,,current,true(1):false(2),The value of true indicates that the NetBIOS Names configured in dlswDirNBTable are the only ones accessible via this DLSw. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. It is up to the implementation exactly when to start the run-time capabilities exchange.
.1.3.6.1.2.1.46.1.1.9,DLSW-MIB::dlswNodeResourceMacExclusivity,INTEGER,read-write,,current,true(1):false(2),The value of true indicates that the MAC addresses configured in the dlswDirMacTable are the only ones accessible via this DLSw. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. It is up to the implementation exactly when to start the run-time capabilities exchange.
.1.3.6.1.2.1.46.1.1.10,DLSW-MIB::dlswTrapControl,,,,,,
.1.3.6.1.2.1.46.1.1.10.1,DLSW-MIB::dlswTrapCntlTConnPartnerReject,INTEGER,read-write,,current,enabled(1):disabled(2):partial(3),Indicates whether the DLSw is permitted to emit partner reject related traps. With the value of `enabled' the DLSw will emit all partner reject related traps. With the value of `disabled' the DLSw will not emit any partner reject related traps. With the value of `partial' the DLSw will only emits partner reject traps for CapEx reject. The changes take effect immediately.
.1.3.6.1.2.1.46.1.1.10.2,DLSW-MIB::dlswTrapCntlTConnProtViolation,INTEGER,read-write,,current,true(1):false(2),Indicates whether the DLSw is permitted to generate protocol-violation traps on the events such as window size violation. The changes take effect immediately.
.1.3.6.1.2.1.46.1.1.10.3,DLSW-MIB::dlswTrapCntlTConn,INTEGER,read-write,,current,enabled(1):disabled(2):partial(3),Indicates whether the DLSw is permitted to emit transport connection up and down traps. With the value of `enabled' the DLSw will emit traps when connections enter `connected' and `disconnected' states. With the value of `disabled' the DLSw will not emit traps when connections enter of `connected' and `disconnected' states. With the value of `partial' the DLSw will only emits transport connection down traps when the connection is closed with busy. The changes take effect immediately.
.1.3.6.1.2.1.46.1.1.10.4,DLSW-MIB::dlswTrapCntlCircuit,INTEGER,read-write,,current,enabled(1):disabled(2):partial(3),Indicates whether the DLSw is permitted to generate circuit up and down traps. With the value of `enabled' the DLSw will emit traps when circuits enter `connected' and `disconnected' states. With the value of `disabled' the DLSw will not emit traps when circuits enter of `connected' and `disconnected' states. With the value of `partial' the DLSw will emit traps only for those circuits that are initiated by this DLSw, e.g., originating the CUR_CS message. The changes take effect immediately.
.1.3.6.1.2.1.46.1.2,DLSW-MIB::dlswTConn,,,,,,
.1.3.6.1.2.1.46.1.2.1,DLSW-MIB::dlswTConnStat,,,,,,
.1.3.6.1.2.1.46.1.2.1.1,DLSW-MIB::dlswTConnStatActiveConnections,Gauge32,read-only,,current,,The number of transport connections that are not in `disconnected' state.
.1.3.6.1.2.1.46.1.2.1.2,DLSW-MIB::dlswTConnStatCloseIdles,Counter32,read-only,,current,,The number of times transport connections in this node exited the connected state with zero active circuits on the transport connection.
.1.3.6.1.2.1.46.1.2.1.3,DLSW-MIB::dlswTConnStatCloseBusys,Counter32,read-only,,current,,The number of times transport connections in this node exited the connected state with some non-zero number of active circuits on the transport connection. Normally this means the transport connection failed unexpectedly.
.1.3.6.1.2.1.46.1.2.2,DLSW-MIB::dlswTConnConfigTable,,not-accessible,,current,,This table defines the transport connections that will be initiated or accepted by this DLSw. Structure of masks allows wildcard definition for a collection of transport connections by a conceptual row. For a specific transport connection, there may be multiple of conceptual rows match the transport address. The `best' match will the one to determine the characteristics of the transport connection.
.1.3.6.1.2.1.46.1.2.2.1,DLSW-MIB::dlswTConnConfigEntry,,not-accessible,dlswTConnConfigIndex,current,,Each conceptual row defines a collection of transport connections.
.1.3.6.1.2.1.46.1.2.2.1.1,DLSW-MIB::dlswTConnConfigIndex,INTEGER,not-accessible,,current,,The index to the conceptual row of the table. Negative numbers are not allowed. There are objects defined that point to conceptual rows of this table with this index value. Zero is used to denote that no corresponding row exists. Index values are assigned by the agent, and should not be reused but should continue to increase in value.
.1.3.6.1.2.1.46.1.2.2.1.2,DLSW-MIB::dlswTConnConfigTDomain,OBJECT,read-create,,current,,The object identifier which indicates the transport domain of this conceptual row.
.1.3.6.1.2.1.46.1.2.2.1.3,DLSW-MIB::dlswTConnConfigLocalTAddr,OCTET,read-create,,current,,The local transport address for this conceptual row of the transport connection definition.
.1.3.6.1.2.1.46.1.2.2.1.4,DLSW-MIB::dlswTConnConfigRemoteTAddr,OCTET,read-create,,current,,The remote transport address. Together with dlswTConnConfigEntryType and dlswTConnConfigGroupDefinition, the object instance of this conceptual row identifies a collection of the transport connections that will be either initiated by this DLSw or initiated by a partner DLSw and accepted by this DLSw.
.1.3.6.1.2.1.46.1.2.2.1.5,DLSW-MIB::dlswTConnConfigLastModifyTime,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the value of any object in this conceptual row except for dlswTConnConfigOpens was last changed. This value may be compared to dlswTConnOperConnectTime to determine whether values in this row are completely valid for a transport connection created using this row definition.
.1.3.6.1.2.1.46.1.2.2.1.6,DLSW-MIB::dlswTConnConfigEntryType,INTEGER,read-create,,current,individual(1):global(2):group(3),The object instance signifies the type of entry in the associated conceptual row. The value of `individual' means that the entry applies to a specific partner DLSw node as identified by dlswTConnConfigRemoteTAddr and dlswTConnConfigTDomain. The value of `global' means that the entry applies to all partner DLSw nodes of the TDomain. The value of 'group' means that the entry applies to a specific set of DLSw nodes in the TDomain. Any group definitions are enterprise-specific and are pointed to by dlswTConnConfigGroupDefinition. In the cases of `global' and `group', the value in dlswTConnConfigRemoteTAddr may not have any significance.
.1.3.6.1.2.1.46.1.2.2.1.7,DLSW-MIB::dlswTConnConfigGroupDefinition,OBJECT,read-create,,current,,For conceptual rows of `individual' and `global' as specified in dlswTConnConfigEntryType, the instance of this object is `0.0'. For conceptual rows of `group', the instance points to the specific group definition.
.1.3.6.1.2.1.46.1.2.2.1.8,DLSW-MIB::dlswTConnConfigSetupType,INTEGER,read-create,,current,other(1):activePersistent(2):activeOnDemand(3):passive(4):excluded(5),This value of the instance of a conceptual row identifies the behavior of the collection of transport connections that this conceptual row defines. The value of activePersistent, activeOnDemand and passive means this DLSw will accept any transport connections, initiated by partner DLSw nodes, which are defined by this conceptual row. The value of activePersistent means this DLSw will also initiate the transport connections of this conceptual row and retry periodically if necessary. The value of activeOnDemand means this DLSw will initiate a transport connection of this conceptual row, if there is a directory cache hits. The value of other is implementation specific. The value of exclude means that the specified node is not allowed to be a partner to this DLSw node. To take a certain conceptual row definition out of service, a value of notInService for dlswTConnConfigRowStatus should be used.
.1.3.6.1.2.1.46.1.2.2.1.9,DLSW-MIB::dlswTConnConfigSapList,OCTET,read-create,,current,,The SAP list indicates which SAPs are advertised to the transport connection defined by this conceptual row. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in dlswIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 4, 8, and C.
.1.3.6.1.2.1.46.1.2.2.1.10,DLSW-MIB::dlswTConnConfigAdvertiseMacNB,INTEGER,read-create,,current,true(1):false(2),The value of true indicates that any defined local MAC addresses and NetBIOS names will be advertised to a partner node via initial and (if supported) run-time capabilities exchange messages. The DLSw node should send the appropriate exclusivity control vector to accompany each list it sends, or to represent that the node is explicitly configured to have a null list. The value of false indicates that the DLSw node should not send a MAC address list or NetBIOS name list, and should also not send their corresponding exclusivity control vectors.
.1.3.6.1.2.1.46.1.2.2.1.11,DLSW-MIB::dlswTConnConfigInitCirRecvWndw,INTEGER,read-create,,current,,The initial circuit receive pacing window size, in the unit of SSP messages, to be used for future transport connections activated using this table row. The managed node sends this value as its initial receive pacing window in its initial capabilities exchange message. Changing this value does not affect the initial circuit receive pacing window size of currently active transport connections. If the standard window pacing scheme is not supported, the value is zero. A larger receive window value may be appropriate for partners that are reachable only via physical paths that have longer network delays.
.1.3.6.1.2.1.46.1.2.2.1.12,DLSW-MIB::dlswTConnConfigOpens,Counter32,read-only,,current,,Number of times transport connections entered connected state according to the definition of this conceptual row.
.1.3.6.1.2.1.46.1.2.2.1.13,DLSW-MIB::dlswTConnConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by the manager to create or delete the row entry in the dlswTConnConfigTable following the RowStatus textual convention. The value of notInService will be used to take a conceptual row definition out of use.
.1.3.6.1.2.1.46.1.2.3,DLSW-MIB::dlswTConnOperTable,,not-accessible,,current,,A list of transport connections. It is optional but desirable for the agent to keep an entry for some period of time after the transport connection is disconnected. This allows the manager to capture additional useful information about the connection, in particular, statistical information and the cause of the disconnection.
.1.3.6.1.2.1.46.1.2.3.1,DLSW-MIB::dlswTConnOperEntry,,not-accessible,dlswTConnOperTDomain:dlswTConnOperRemoteTAddr,current,,
.1.3.6.1.2.1.46.1.2.3.1.1,DLSW-MIB::dlswTConnOperTDomain,OBJECT,not-accessible,,current,,The object identifier indicates the transport domain of this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.2,DLSW-MIB::dlswTConnOperLocalTAddr,OCTET,read-only,,current,,The local transport address for this transport connection. This value could be different from dlswTConnConfigLocalAddr, if the value of the latter were changed after this transport connection was established.
.1.3.6.1.2.1.46.1.2.3.1.3,DLSW-MIB::dlswTConnOperRemoteTAddr,OCTET,not-accessible,,current,,The remote transport address of this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.4,DLSW-MIB::dlswTConnOperEntryTime,TimeTicks,read-only,,current,,The amount of time (in hundredths of a second) since this transport connection conceptual row was created.
.1.3.6.1.2.1.46.1.2.3.1.5,DLSW-MIB::dlswTConnOperConnectTime,TimeTicks,read-only,,current,,The amount of time (in hundredths of a second) since this transport connection last entered the 'connected' state. A value of zero means this transport connection has never been established.
.1.3.6.1.2.1.46.1.2.3.1.6,DLSW-MIB::dlswTConnOperState,INTEGER,read-write,,current,connecting(1):initCapExchange(2):connected(3):quiescing(4):disconnecting(5):disconnected(6),The state of this transport connection. The transport connection enters `connecting' state when DLSw makes a connection request to the transport layer. Once initial Capabilities Exchange is sent, the transport connection enters enters `initCapExchange' state. When partner capabilities have been determined and the transport connection is ready for sending CanUReach (CUR) messages, it moves to the `connected' state. When DLSw is in the process of bringing down the connection, it is in the `disconnecting' state. When the transport layer indicates one of its connections is disconnected, the transport connection moves to the `disconnected' state. Whereas all of the values will be returned in response to a management protocol retrieval operation, only two values may be specified in a management protocol set operation: `quiescing' and `disconnecting'. Changing the value to `quiescing' prevents new circuits from being established, and will cause a transport disconnect when the last circuit on the connection goes away. Changing the value to `disconnecting' will force off all circuits immediately and bring the connection to `disconnected' state.
.1.3.6.1.2.1.46.1.2.3.1.7,DLSW-MIB::dlswTConnOperConfigIndex,INTEGER,read-only,,current,,The value of dlswTConnConfigIndex of the dlswTConnConfigEntry that governs the configuration information used by this dlswTConnOperEntry. The manager can therefore normally examine both configured and operational information for this transport connection. This value is zero if the corresponding dlswTConnConfigEntry was deleted after the creation of this dlswTConnOperEntry. If some fields in the former were changed but the conceptual row was not deleted, some configuration information may not be valid for this operational transport connection. The manager can compare dlswTConnOperConnectTime and dlswTConnConfigLastModifyTime to determine if this condition exists.
.1.3.6.1.2.1.46.1.2.3.1.8,DLSW-MIB::dlswTConnOperFlowCntlMode,INTEGER,read-only,,current,undetermined(1):pacing(2):other(3),The flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from dlswTConnOperPartnerVersion.
.1.3.6.1.2.1.46.1.2.3.1.9,DLSW-MIB::dlswTConnOperPartnerVersion,OCTET,read-only,,current,,This value identifies which version (first octet) and release (second octet) of the DLSw standard is supported by this partner DLSw. This information is obtained from a DLSw capabilities exchange message received from the partner DLSw. A string of zero length is returned before a Capabilities Exchange message is received, or if one is never received. A conceptual row with a dlswTConnOperState of `connected' but a zero length partner version indicates that the partner is a non-standard DLSw partner. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.10,DLSW-MIB::dlswTConnOperPartnerVendorID,OCTET,read-only,,current,,This value identifies the IEEE-assigned organizationally Unique Identifier (OUI) of the maker of this partner DLSw. This information is obtained from a DLSw capabilities exchange message received from the partner DLSw. A string of zero length is returned before a Capabilities Exchange message is received, or if one is never received. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.11,DLSW-MIB::dlswTConnOperPartnerVersionStr,OCTET,read-only,,current,,This value identifies the particular product version (e.g., product name, code level, fix level) of this partner DLSw. The format of the actual version string is vendor-specific. This information is obtained from a DLSw capabilities exchange message received from the partner DLSw. A string of zero length is returned before a Capabilities Exchange message is received, if one is never received, or if one is received but it does not contain a version string. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.12,DLSW-MIB::dlswTConnOperPartnerInitPacingWndw,INTEGER,read-only,,current,,The value of the partner initial receive pacing window. This is our initial send pacing window for all new circuits on this transport connection, as modified and granted by the first flow control indication the partner sends on each circuit. This information is obtained from a DLSw capabilities exchange message received from the partner DLSw. A value of zero is returned before a Capabilities Exchange message is received, or if one is never received. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.13,DLSW-MIB::dlswTConnOperPartnerSapList,OCTET,read-only,,current,,The Supported SAP List received in the capabilities exchange message from the partner DLSw. This list has the same format described for dlswTConnConfigSapList. A string of zero length is returned before a Capabilities Exchange message is received, or if one is never received. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.14,DLSW-MIB::dlswTConnOperPartnerNBExcl,INTEGER,read-only,,current,true(1):false(2),The value of true signifies that the NetBIOS names received from this partner in the NetBIOS name list in its capabilities exchange message are the only NetBIOS names reachable by that partner. `False' indicates that other NetBIOS names may be reachable. `False' should be returned before a Capabilities Exchange message is received, if one is never received, or if one is received without a NB Name Exclusivity CV. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.15,DLSW-MIB::dlswTConnOperPartnerMacExcl,INTEGER,read-only,,current,true(1):false(2),The value of true signifies that the MAC addresses received from this partner in the MAC address list in its capabilities exchange message are the only MAC addresses reachable by that partner. `False' indicates that other MAC addresses may be reachable. `False' should be returned before a Capabilities Exchange message is received, if one is never received, or if one is received without a MAC Address Exclusivity CV. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.16,DLSW-MIB::dlswTConnOperPartnerNBInfo,INTEGER,read-only,,current,none(1):partial(2):complete(3):notApplicable(4),It is up to this DSLw whether to keep either none, some, or all of the NetBIOS name list that was received in the capabilities exchange message sent by this partner DLSw. This object identifies how much information was kept by this DLSw. These names are stored as userConfigured remote entries in dlswDirNBTable. A value of (4), notApplicable, should be returned before a Capabilities Exchange message is received, or if one is never received. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.17,DLSW-MIB::dlswTConnOperPartnerMacInfo,INTEGER,read-only,,current,none(1):partial(2):complete(3):notApplicable(4),It is up to this DLSw whether to keep either none, some, or all of the MAC address list that was received in the capabilities exchange message sent by this partner DLSw. This object identifies how much information was kept by this DLSw. These names are stored as userConfigured remote entries in dlswDirMACTable. A value of (4), notApplicable, should be returned before a Capabilities Exchange message is received, or if one is never received. If an implementation chooses to keep dlswTConnOperEntrys in the `disconnected' state, this value should remain unchanged.
.1.3.6.1.2.1.46.1.2.3.1.18,DLSW-MIB::dlswTConnOperDiscTime,TimeTicks,read-only,,current,,The amount of time (in hundredths of a second) since the dlswTConnOperState last entered `disconnected' state.
.1.3.6.1.2.1.46.1.2.3.1.19,DLSW-MIB::dlswTConnOperDiscReason,INTEGER,read-only,,current,other(1):capExFailed(2):transportLayerDisc(3):operatorCommand(4):lastCircuitDiscd(5):protocolError(6),This object signifies the reason that either prevented the transport connection from entering the connected state, or caused the transport connection to enter the disconnected state.
.1.3.6.1.2.1.46.1.2.3.1.20,DLSW-MIB::dlswTConnOperDiscActiveCir,INTEGER,read-only,,current,,The number of circuits active (not in DISCONNECTED state) at the time the transport connection was last disconnected. This value is zero if the transport connection has never been connected.
.1.3.6.1.2.1.46.1.2.3.1.21,DLSW-MIB::dlswTConnOperInDataPkts,Counter32,read-only,,current,,The number of Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.22,DLSW-MIB::dlswTConnOperOutDataPkts,Counter32,read-only,,current,,The number of Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.23,DLSW-MIB::dlswTConnOperInDataOctets,Counter32,read-only,,current,,The number octets in Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this transport connection. Each message is counted starting with the first octet following the SSP message header.
.1.3.6.1.2.1.46.1.2.3.1.24,DLSW-MIB::dlswTConnOperOutDataOctets,Counter32,read-only,,current,,The number octets in Switch-to-Switch Protocol (SSP) messages of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this transport connection. Each message is counted starting with the first octet following the SSP message header.
.1.3.6.1.2.1.46.1.2.3.1.25,DLSW-MIB::dlswTConnOperInCntlPkts,Counter32,read-only,,current,,The number of Switch-to-Switch Protocol (SSP) messages received on this transport connection which were not of type DGRMFRAME, DATAFRAME, or INFOFRAME.
.1.3.6.1.2.1.46.1.2.3.1.26,DLSW-MIB::dlswTConnOperOutCntlPkts,Counter32,read-only,,current,,The number of Switch-to-Switch Protocol (SSP) messages of transmitted on this transport connection which were not of type DGRMFRAME, DATAFRAME, or INFOFRAME.
.1.3.6.1.2.1.46.1.2.3.1.27,DLSW-MIB::dlswTConnOperCURexSents,Counter32,read-only,,current,,The number of CanUReach_ex messages sent on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.28,DLSW-MIB::dlswTConnOperICRexRcvds,Counter32,read-only,,current,,The number of ICanReach_ex messages received on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.29,DLSW-MIB::dlswTConnOperCURexRcvds,Counter32,read-only,,current,,The number of CanUReach_ex messages received on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.30,DLSW-MIB::dlswTConnOperICRexSents,Counter32,read-only,,current,,The number of ICanReach_ex messages sent on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.31,DLSW-MIB::dlswTConnOperNQexSents,Counter32,read-only,,current,,The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) messages sent on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.32,DLSW-MIB::dlswTConnOperNRexRcvds,Counter32,read-only,,current,,The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) messages received on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.33,DLSW-MIB::dlswTConnOperNQexRcvds,Counter32,read-only,,current,,The number of NETBIOS_NQ_ex messages received on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.34,DLSW-MIB::dlswTConnOperNRexSents,Counter32,read-only,,current,,The number of NETBIOS_NR_ex messages sent on this transport connection.
.1.3.6.1.2.1.46.1.2.3.1.35,DLSW-MIB::dlswTConnOperCirCreates,Counter32,read-only,,current,,The number of times that circuits entered `circuit_established' state (not counting transitions from `circuit_restart').
.1.3.6.1.2.1.46.1.2.3.1.36,DLSW-MIB::dlswTConnOperCircuits,Gauge32,read-only,,current,,The number of currently active circuits on this transport connection, where `active' means not in `disconnected' state.
.1.3.6.1.2.1.46.1.2.4,DLSW-MIB::dlswTConnSpecific,,,,,,
.1.3.6.1.2.1.46.1.2.4.1,DLSW-MIB::dlswTConnTcp,,,,,,
.1.3.6.1.2.1.46.1.2.4.1.1,DLSW-MIB::dlswTConnTcpConfigTable,,not-accessible,,current,,This table defines the TCP transport connections that will be either initiated by or accepted by this DSLw. It augments the entries in dlswTConnConfigTable whose domain is dlswTCPDomain.
.1.3.6.1.2.1.46.1.2.4.1.1.1,DLSW-MIB::dlswTConnTcpConfigEntry,,not-accessible,dlswTConnConfigIndex,current,,Each conceptual row defines parameters that are specific to dlswTCPDomain transport connections.
.1.3.6.1.2.1.46.1.2.4.1.1.1.1,DLSW-MIB::dlswTConnTcpConfigKeepAliveInt,INTEGER,read-create,,current,,The time in seconds between TCP keepAlive messages when no traffic is flowing. Zero signifies no keepAlive protocol. Changes take effect only for new TCP connections.
.1.3.6.1.2.1.46.1.2.4.1.1.1.2,DLSW-MIB::dlswTConnTcpConfigTcpConnections,INTEGER,read-create,,current,,This is our preferred number of TCP connections within a TCP transport connection. The actual number used is negotiated at capabilities exchange time. Changes take effect only for new transport connections.
.1.3.6.1.2.1.46.1.2.4.1.1.1.3,DLSW-MIB::dlswTConnTcpConfigMaxSegmentSize,INTEGER,read-create,,current,,This is the number of bytes that this node is willing to receive over the read TCP connection(s). Changes take effect for new transport connections.
.1.3.6.1.2.1.46.1.2.4.1.2,DLSW-MIB::dlswTConnTcpOperTable,,not-accessible,,current,,A list of TCP transport connections. It is optional but desirable for the agent to keep an entry for some period of time after the transport connection is disconnected. This allows the manager to capture additional useful information about the connection, in particular, statistical information and the cause of the disconnection.
.1.3.6.1.2.1.46.1.2.4.1.2.1,DLSW-MIB::dlswTConnTcpOperEntry,,not-accessible,dlswTConnOperTDomain:dlswTConnOperRemoteTAddr,current,,
.1.3.6.1.2.1.46.1.2.4.1.2.1.1,DLSW-MIB::dlswTConnTcpOperKeepAliveInt,INTEGER,read-only,,current,,The time in seconds between TCP keepAlive messages when no traffic is flowing. Zero signifies no keepAlive protocol is operating.
.1.3.6.1.2.1.46.1.2.4.1.2.1.2,DLSW-MIB::dlswTConnTcpOperPrefTcpConnections,INTEGER,read-only,,current,,This is the number of TCP connections preferred by this DLSw partner, as received in its capabilities exchange message.
.1.3.6.1.2.1.46.1.2.4.1.2.1.3,DLSW-MIB::dlswTConnTcpOperTcpConnections,INTEGER,read-only,,current,,This is the actual current number of TCP connections within this transport connection.
.1.3.6.1.2.1.46.1.3,DLSW-MIB::dlswInterface,,,,,,
.1.3.6.1.2.1.46.1.3.1,DLSW-MIB::dlswIfTable,,not-accessible,,current,,The list of interfaces on which DLSw is active.
.1.3.6.1.2.1.46.1.3.1.1,DLSW-MIB::dlswIfEntry,,not-accessible,ifIndex,current,,
.1.3.6.1.2.1.46.1.3.1.1.1,DLSW-MIB::dlswIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by the manager to create or delete the row entry in the dlswIfTable following the RowStatus textual convention.
.1.3.6.1.2.1.46.1.3.1.1.2,DLSW-MIB::dlswIfVirtualSegment,INTEGER,read-create,,current,,The segment number that uniquely identifies the virtual segment to which this DLSw interface is connected. Current source routing protocols limit this value to the range 0 - 4095. (The value 0 is used by some management applications for special test cases.) A value of 65535 signifies that no virtual segment is assigned to this interface. For instance, in a non-source routing environment, segment number assignment is not required.
.1.3.6.1.2.1.46.1.3.1.1.3,DLSW-MIB::dlswIfSapList,OCTET,read-create,,current,,The SAP list indicates which SAPs are allowed to be data link switched through this interface. This list has the same format described for dlswTConnConfigSapList. When changes to this object take effect is implementation- specific. Turning off a particular SAP can destroy active circuits that are using that SAP. An agent implementation may reject such changes until there are no active circuits if it so chooses. In this case, it is up to the manager to close the circuits first, using dlswCircuitState. The DEFVAL below indicates support for SAPs 0, 4, 8, and C.
.1.3.6.1.2.1.46.1.4,DLSW-MIB::dlswDirectory,,,,,,
.1.3.6.1.2.1.46.1.4.1,DLSW-MIB::dlswDirStat,,,,,,
.1.3.6.1.2.1.46.1.4.1.1,DLSW-MIB::dlswDirMacEntries,Gauge32,read-only,,current,,The current total number of entries in the dlswDirMacTable.
.1.3.6.1.2.1.46.1.4.1.2,DLSW-MIB::dlswDirMacCacheHits,Counter32,read-only,,current,,The number of times a cache search for a particular MAC address resulted in success.
.1.3.6.1.2.1.46.1.4.1.3,DLSW-MIB::dlswDirMacCacheMisses,Counter32,read-only,,current,,The number of times a cache search for a particular MAC address resulted in failure.
.1.3.6.1.2.1.46.1.4.1.4,DLSW-MIB::dlswDirMacCacheNextIndex,INTEGER,read-only,,current,,The next value of dlswDirMacIndex to be assigned by the agent. A retrieval of this object atomically reserves the returned value for use by the manager to create a row in dlswDirMacTable. This makes it possible for the agent to control the index space of the MAC address cache, yet allows the manager to administratively create new rows.
.1.3.6.1.2.1.46.1.4.1.5,DLSW-MIB::dlswDirNBEntries,Gauge32,read-only,,current,,The current total number of entries in the dlswDirNBTable.
.1.3.6.1.2.1.46.1.4.1.6,DLSW-MIB::dlswDirNBCacheHits,Counter32,read-only,,current,,The number of times a cache search for a particular NetBIOS name resulted in success.
.1.3.6.1.2.1.46.1.4.1.7,DLSW-MIB::dlswDirNBCacheMisses,Counter32,read-only,,current,,The number of times a cache search for a particular NetBIOS name resulted in failure.
.1.3.6.1.2.1.46.1.4.1.8,DLSW-MIB::dlswDirNBCacheNextIndex,INTEGER,read-only,,current,,The next value of dlswDirNBIndex to be assigned by the agent. A retrieval of this object atomically reserves the returned value for use by the manager to create a row in dlswDirNBTable. This makes it possible for the agent to control the index space for the NetBIOS name cache, yet allows the manager to administratively create new rows.
.1.3.6.1.2.1.46.1.4.2,DLSW-MIB::dlswDirCache,,,,,,
.1.3.6.1.2.1.46.1.4.2.1,DLSW-MIB::dlswDirMacTable,,not-accessible,,current,,This table contains locations of MAC addresses. They could be either verified or not verified, local or remote, and configured locally or learned from either Capabilities Exchange messages or directory searches.
.1.3.6.1.2.1.46.1.4.2.1.1,DLSW-MIB::dlswDirMacEntry,,not-accessible,dlswDirMacIndex,current,,Indexed by dlswDirMacIndex.
.1.3.6.1.2.1.46.1.4.2.1.1.1,DLSW-MIB::dlswDirMacIndex,INTEGER,not-accessible,,current,,Uniquely identifies a conceptual row of this table.
.1.3.6.1.2.1.46.1.4.2.1.1.2,DLSW-MIB::dlswDirMacMac,OCTET,read-create,,current,,The MAC address, together with the dlswDirMacMask, specifies a set of MAC addresses that are defined or discovered through an interface or partner DLSw nodes.
.1.3.6.1.2.1.46.1.4.2.1.1.3,DLSW-MIB::dlswDirMacMask,OCTET,read-create,,current,,The MAC address mask, together with the dlswDirMacMac, specifies a set of MAC addresses that are defined or discovered through an interface or partner DLSw nodes.
.1.3.6.1.2.1.46.1.4.2.1.1.4,DLSW-MIB::dlswDirMacEntryType,INTEGER,read-create,,current,other(1):userConfiguredPublic(2):userConfiguredPrivate(3):partnerCapExMsg(4):dynamic(5),The cause of the creation of this conceptual row. It could be one of the three methods: (1) user configured, including via management protocol set operations, configuration file, command line or equivalent methods; (2) learned from the partner DLSw Capabilities Exchange messages; and (3) dynamic, e.g., learned from ICanReach messages, or LAN explorer frames. Since only individual MAC addresses can be dynamically learned, dynamic entries will all have a mask of all FFs. The public versus private distinction for user- configured resources applies only to local resources (UC remote resources are private), and indicates whether that resource should be advertised in capabilities exchange messages sent by this node.
.1.3.6.1.2.1.46.1.4.2.1.1.5,DLSW-MIB::dlswDirMacLocationType,INTEGER,read-create,,current,other(1):local(2):remote(3),The location of the resource (or a collection of resources using a mask) of this conceptual row is either (1) local - the resource is reachable via an interface, or (2) remote - the resource is reachable via a partner DLSw node (or a set of partner DLSw nodes).
.1.3.6.1.2.1.46.1.4.2.1.1.6,DLSW-MIB::dlswDirMacLocation,OBJECT,read-create,,current,,Points to either the ifEntry, dlswTConnConfigEntry, dlswTConnOperEntry, 0.0, or something that is implementation specific. It identifies the location of the MAC address (or the collection of MAC addresses.)
.1.3.6.1.2.1.46.1.4.2.1.1.7,DLSW-MIB::dlswDirMacStatus,INTEGER,read-create,,current,unknown(1):reachable(2):notReachable(3),This object specifies whether DLSw currently believes the MAC address to be accessible at the specified location. The value `notReachable' allows a configured resource definition to be taken out of service when a search to that resource fails (avoiding a repeat of the search).
.1.3.6.1.2.1.46.1.4.2.1.1.8,DLSW-MIB::dlswDirMacLFSize,INTEGER,read-create,,current,lfs516(516):lfs635(635):lfs754(754):lfs873(873):lfs993(993):lfs1112(1112):lfs1231(1231):lfs1350(1350):lfs1470(1470):lfs1542(1542):lfs1615(1615):lfs1688(1688):lfs1761(1761):lfs1833(1833):lfs1906(1906):lfs1979(1979):lfs2052(2052):lfs2345(2345):lfs2638(2638):lfs2932(2932):lfs3225(3225):lfs3518(3518):lfs3812(3812):lfs4105(4105):lfs4399(4399):lfs4865(4865):lfs5331(5331):lfs5798(5798):lfs6264(6264):lfs6730(6730):lfs7197(7197):lfs7663(7663):lfs8130(8130):lfs8539(8539):lfs8949(8949):lfs9358(9358):lfs9768(9768):lfs10178(10178):lfs10587(10587):lfs10997(10997):lfs11407(11407):lfs12199(12199):lfs12992(12992):lfs13785(13785):lfs14578(14578):lfs15370(15370):lfs16163(16163):lfs16956(16956):lfs17749(17749):lfs20730(20730):lfs23711(23711):lfs26693(26693):lfs29674(29674):lfs32655(32655):lfs38618(38618):lfs41600(41600):lfs44591(44591):lfs47583(47583):lfs50575(50575):lfs53567(53567):lfs56559(56559):lfs59551(59551):lfs65535(65535),The largest size of the MAC INFO field (LLC header and data) that a circuit to the MAC address can carry through this path.
.1.3.6.1.2.1.46.1.4.2.1.1.9,DLSW-MIB::dlswDirMacRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by the manager to create or delete the row entry in the dlswDirMacTable following the RowStatus textual convention.
.1.3.6.1.2.1.46.1.4.2.2,DLSW-MIB::dlswDirNBTable,,not-accessible,,current,,This table contains locations of NetBIOS names. They could be either verified or not verified, local or remote, and configured locally or learned from either Capabilities Exchange messages or directory searches.
.1.3.6.1.2.1.46.1.4.2.2.1,DLSW-MIB::dlswDirNBEntry,,not-accessible,dlswDirNBIndex,current,,Indexed by dlswDirNBIndex.
.1.3.6.1.2.1.46.1.4.2.2.1.1,DLSW-MIB::dlswDirNBIndex,INTEGER,not-accessible,,current,,Uniquely identifies a conceptual row of this table.
.1.3.6.1.2.1.46.1.4.2.2.1.2,DLSW-MIB::dlswDirNBName,OCTET,read-create,,current,,The NetBIOS name (including `any char' and `wildcard' characters) specifies a set of NetBIOS names that are defined or discovered through an interface or partner DLSw nodes.
.1.3.6.1.2.1.46.1.4.2.2.1.3,DLSW-MIB::dlswDirNBNameType,INTEGER,read-create,,current,unknown(1):individual(2):group(3),Whether dlswDirNBName represents an (or a set of) individual or group NetBIOS name(s).
.1.3.6.1.2.1.46.1.4.2.2.1.4,DLSW-MIB::dlswDirNBEntryType,INTEGER,read-create,,current,other(1):userConfiguredPublic(2):userConfiguredPrivate(3):partnerCapExMsg(4):dynamic(5),The cause of the creation of this conceptual row. It could be one of the three methods: (1) user configured, including via management protocol set operations, configuration file, command line, or equivalent methods; (2) learned from the partner DLSw Capabilities Exchange messages; and (3) dynamic, e.g., learned from ICanReach messages, or test frames. Since only actual NetBIOS names can be dynamically learned, dynamic entries will not contain any char or wildcard characters. The public versus private distinction for user- configured resources applies only to local resources (UC remote resources are private), and indicates whether that resource should be advertised in capabilities exchange messages sent by this node.
.1.3.6.1.2.1.46.1.4.2.2.1.5,DLSW-MIB::dlswDirNBLocationType,INTEGER,read-create,,current,other(1):local(2):remote(3),The location of the resource (or a collection of resources using any char/wildcard characters) of this conceptual row is either (1) local - the resource is reachable via an interface, or (2) remote - the resource is reachable via a a partner DLSw node (or a set of partner DLSw nodes).
.1.3.6.1.2.1.46.1.4.2.2.1.6,DLSW-MIB::dlswDirNBLocation,OBJECT,read-create,,current,,Points to either the ifEntry, dlswTConnConfigEntry, dlswTConnOperEntry, 0.0, or something that is implementation specific. It identifies the location of the NetBIOS name or the set of NetBIOS names.
.1.3.6.1.2.1.46.1.4.2.2.1.7,DLSW-MIB::dlswDirNBStatus,INTEGER,read-create,,current,unknown(1):reachable(2):notReachable(3),This object specifies whether DLSw currently believes the NetBIOS name to be accessible at the specified location. The value `notReachable' allows a configured resource definition to be taken out of service when a search to that resource fails (avoiding a repeat of the search).
.1.3.6.1.2.1.46.1.4.2.2.1.8,DLSW-MIB::dlswDirNBLFSize,INTEGER,read-create,,current,lfs516(516):lfs635(635):lfs754(754):lfs873(873):lfs993(993):lfs1112(1112):lfs1231(1231):lfs1350(1350):lfs1470(1470):lfs1542(1542):lfs1615(1615):lfs1688(1688):lfs1761(1761):lfs1833(1833):lfs1906(1906):lfs1979(1979):lfs2052(2052):lfs2345(2345):lfs2638(2638):lfs2932(2932):lfs3225(3225):lfs3518(3518):lfs3812(3812):lfs4105(4105):lfs4399(4399):lfs4865(4865):lfs5331(5331):lfs5798(5798):lfs6264(6264):lfs6730(6730):lfs7197(7197):lfs7663(7663):lfs8130(8130):lfs8539(8539):lfs8949(8949):lfs9358(9358):lfs9768(9768):lfs10178(10178):lfs10587(10587):lfs10997(10997):lfs11407(11407):lfs12199(12199):lfs12992(12992):lfs13785(13785):lfs14578(14578):lfs15370(15370):lfs16163(16163):lfs16956(16956):lfs17749(17749):lfs20730(20730):lfs23711(23711):lfs26693(26693):lfs29674(29674):lfs32655(32655):lfs38618(38618):lfs41600(41600):lfs44591(44591):lfs47583(47583):lfs50575(50575):lfs53567(53567):lfs56559(56559):lfs59551(59551):lfs65535(65535),The largest size of the MAC INFO field (LLC header and data) that a circuit to the NB name can carry through this path.
.1.3.6.1.2.1.46.1.4.2.2.1.9,DLSW-MIB::dlswDirNBRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by manager to create or delete the row entry in the dlswDirNBTable following the RowStatus textual convention.
.1.3.6.1.2.1.46.1.4.3,DLSW-MIB::dlswDirLocate,,,,,,
.1.3.6.1.2.1.46.1.4.3.1,DLSW-MIB::dlswDirLocateMacTable,,not-accessible,,current,,This table is used to retrieve all entries in the dlswDirMacTable that match a given MAC address, in the order of the best matched first, the second best matched second, and so on, till no more entries match the given MAC address.
.1.3.6.1.2.1.46.1.4.3.1.1,DLSW-MIB::dlswDirLocateMacEntry,,not-accessible,dlswDirLocateMacMac:dlswDirLocateMacMatch,current,,Indexed by dlswDirLocateMacMac and dlswDirLocateMacMatch. The first object is the MAC address of interest, and the second object is the order in the list of all entries that match the MAC address.
.1.3.6.1.2.1.46.1.4.3.1.1.1,DLSW-MIB::dlswDirLocateMacMac,OCTET,not-accessible,,current,,The MAC address to be located.
.1.3.6.1.2.1.46.1.4.3.1.1.2,DLSW-MIB::dlswDirLocateMacMatch,INTEGER,not-accessible,,current,,The order of the entries of dlswDirMacTable that match dlswDirLocateMacMac. A value of one represents the entry that best matches the MAC address. A value of two represents the second best matched entry, and so on.
.1.3.6.1.2.1.46.1.4.3.1.1.3,DLSW-MIB::dlswDirLocateMacLocation,OBJECT,read-only,,current,,Points to the dlswDirMacEntry.
.1.3.6.1.2.1.46.1.4.3.2,DLSW-MIB::dlswDirLocateNBTable,,not-accessible,,current,,This table is used to retrieve all entries in the dlswDirNBTable that match a given NetBIOS name, in the order of the best matched first, the second best matched second, and so on, till no more entries match the given NetBIOS name.
.1.3.6.1.2.1.46.1.4.3.2.1,DLSW-MIB::dlswDirLocateNBEntry,,not-accessible,dlswDirLocateNBName:dlswDirLocateNBMatch,current,,Indexed by dlswDirLocateNBName and dlswDirLocateNBMatch. The first object is the NetBIOS name of interest, and the second object is the order in the list of all entries that match the NetBIOS name.
.1.3.6.1.2.1.46.1.4.3.2.1.1,DLSW-MIB::dlswDirLocateNBName,OCTET,not-accessible,,current,,The NetBIOS name to be located (no any char or wildcards).
.1.3.6.1.2.1.46.1.4.3.2.1.2,DLSW-MIB::dlswDirLocateNBMatch,INTEGER,not-accessible,,current,,The order of the entries of dlswDirNBTable that match dlswDirLocateNBName. A value of one represents the entry that best matches the NetBIOS name. A value of two represents the second best matched entry, and so on.
.1.3.6.1.2.1.46.1.4.3.2.1.3,DLSW-MIB::dlswDirLocateNBLocation,OBJECT,read-only,,current,,Points to the dlswDirNBEntry.
.1.3.6.1.2.1.46.1.5,DLSW-MIB::dlswCircuit,,,,,,
.1.3.6.1.2.1.46.1.5.1,DLSW-MIB::dlswCircuitStat,,,,,,
.1.3.6.1.2.1.46.1.5.1.1,DLSW-MIB::dlswCircuitStatActives,Gauge32,read-only,,current,,The current number of circuits in dlswCircuitTable that are not in the disconnected state.
.1.3.6.1.2.1.46.1.5.1.2,DLSW-MIB::dlswCircuitStatCreates,Counter32,read-only,,current,,The total number of entries ever added to dlswCircuitTable, or reactivated upon exiting `disconnected' state.
.1.3.6.1.2.1.46.1.5.2,DLSW-MIB::dlswCircuitTable,,not-accessible,,current,,This table is the circuit representation in the DLSw entity. Virtual data links are used to represent any internal end stations. There is a conceptual row associated with each data link. Thus, for circuits without an intervening transport connection, there are two conceptual rows for each circuit. The table consists of the circuits being established, established, and as an implementation option, circuits that have been disconnected. For circuits carried over transport connections, an entry is created after the CUR_cs was sent or received. For circuits between two locally attached devices, or internal virtual MAC addresses, an entry is created when the equivalent of CUR_cs sent/received status is reached. End station 1 (S1) and End station 2 (S2) are used to represent the two end stations of the circuit. S1 is always an end station which is locally attached. S2 may be locally attached or remote. If it is locally attached, the circuit will be represented by two rows indexed by (A, B) and (B, A) where A & B are the relevant MACs/SAPs. The table may be used to store the causes of disconnection of circuits. It is recommended that the oldest disconnected circuit entry be removed from this table when the memory space of disconnected circuits is needed.
.1.3.6.1.2.1.46.1.5.2.1,DLSW-MIB::dlswCircuitEntry,,not-accessible,dlswCircuitS1Mac:dlswCircuitS1Sap:dlswCircuitS2Mac:dlswCircuitS2Sap,current,,
.1.3.6.1.2.1.46.1.5.2.1.1,DLSW-MIB::dlswCircuitS1Mac,OCTET,not-accessible,,current,,The MAC Address of End Station 1 (S1) used for this circuit.
.1.3.6.1.2.1.46.1.5.2.1.2,DLSW-MIB::dlswCircuitS1Sap,OCTET,not-accessible,,current,,The SAP at End Station 1 (S1) used for this circuit.
.1.3.6.1.2.1.46.1.5.2.1.3,DLSW-MIB::dlswCircuitS1IfIndex,INTEGER,read-only,,current,,The ifEntry index of the local interface through which S1 can be reached.
.1.3.6.1.2.1.46.1.5.2.1.4,DLSW-MIB::dlswCircuitS1DlcType,INTEGER,read-only,,current,other(1):na(2):llc(3):sdlc(4):qllc(5),The DLC protocol in use between the DLSw node and S1.
.1.3.6.1.2.1.46.1.5.2.1.5,DLSW-MIB::dlswCircuitS1RouteInfo,OCTET,read-only,,current,,If source-route bridging is in use between the DLSw node and S1, this is the routing information field describing the path between the two devices. Otherwise the value will be an OCTET STRING of zero length.
.1.3.6.1.2.1.46.1.5.2.1.6,DLSW-MIB::dlswCircuitS1CircuitId,OCTET,read-only,,current,,The Circuit ID assigned by this DLSw node to this circuit. The first four octets are the DLC port Id, and the second four octets are the Data Link Correlator. If the DLSw SSP was not used to establish this circuit, the value will be a string of zero length.
.1.3.6.1.2.1.46.1.5.2.1.7,DLSW-MIB::dlswCircuitS1Dlc,OBJECT,read-only,,current,,Points to a conceptual row of the underlying DLC MIB, which could either be the standard MIBs (e.g., the SDLC), or an enterprise-specific DLC MIB.
.1.3.6.1.2.1.46.1.5.2.1.8,DLSW-MIB::dlswCircuitS2Mac,OCTET,not-accessible,,current,,The MAC Address of End Station 2 (S2) used for this circuit.
.1.3.6.1.2.1.46.1.5.2.1.9,DLSW-MIB::dlswCircuitS2Sap,OCTET,not-accessible,,current,,The SAP at End Station 2 (S2) used for this circuit.
.1.3.6.1.2.1.46.1.5.2.1.10,DLSW-MIB::dlswCircuitS2Location,INTEGER,read-only,,current,other(1):internal(2):remote(3):local(4),The location of End Station 2 (S2). If the location of End Station 2 is local, the interface information will be available in the conceptual row whose S1 and S2 are the S2 and the S1 of this conceptual row, respectively.
.1.3.6.1.2.1.46.1.5.2.1.11,DLSW-MIB::dlswCircuitS2TDomain,OBJECT,read-only,,current,,If the location of End Station 2 is remote, this value is the transport domain of the transport protocol the circuit is running over. Otherwise, the value is 0.0.
.1.3.6.1.2.1.46.1.5.2.1.12,DLSW-MIB::dlswCircuitS2TAddress,OCTET,read-only,,current,,If the location of End Station 2 is remote, this object contains the address of the partner DLSw, else it will be an OCTET STRING of zero length.
.1.3.6.1.2.1.46.1.5.2.1.13,DLSW-MIB::dlswCircuitS2CircuitId,OCTET,read-only,,current,,The Circuit ID assigned to this circuit by the partner DLSw node. The first four octets are the DLC port Id, and the second four octets are the Data Link Correlator. If the DLSw SSP was not used to establish this circuit, the value will be a string of zero length.
.1.3.6.1.2.1.46.1.5.2.1.14,DLSW-MIB::dlswCircuitOrigin,INTEGER,read-only,,current,s1(1):s2(2),This object specifies which of the two end stations initiated the establishment of this circuit.
.1.3.6.1.2.1.46.1.5.2.1.15,DLSW-MIB::dlswCircuitEntryTime,TimeTicks,read-only,,current,,The amount of time (in hundredths of a second) since this circuit table conceptual row was created.
.1.3.6.1.2.1.46.1.5.2.1.16,DLSW-MIB::dlswCircuitStateTime,TimeTicks,read-only,,current,,The amount of time (in hundredths of a second) since this circuit entered the current state.
.1.3.6.1.2.1.46.1.5.2.1.17,DLSW-MIB::dlswCircuitState,INTEGER,read-write,,current,disconnected(1):circuitStart(2):resolvePending(3):circuitPending(4):circuitEstablished(5):connectPending(6):contactPending(7):connected(8):disconnectPending(9):haltPending(10):haltPendingNoack(11):circuitRestart(12):restartPending(13),The current state of this circuit. The agent, implementation specific, may choose to keep entries for some period of time after circuit disconnect, so the manager can gather the time and cause of disconnection. While all of the specified values may be returned from a GET operation, the only SETable value is `disconnectPending'. When this value is set, DLSw should perform the appropriate action given its previous state (e.g., send HALT_DL if the state was `connected') to bring the circuit down to the `disconnected' state. Both the partner DLSw and local end station(s) should be notified as appropriate. This MIB provides no facility to re-establish a disconnected circuit, because in DLSw this should be an end station-driven function.
.1.3.6.1.2.1.46.1.5.2.1.18,DLSW-MIB::dlswCircuitPriority,INTEGER,read-only,,current,unsupported(1):low(2):medium(3):high(4):highest(5),The transmission priority of this circuit as understood by this DLSw node. This value is determined by the two DLSw nodes at circuit startup time. If this DLSw node does not support DLSw circuit priority, the value `unsupported' should be returned.
.1.3.6.1.2.1.46.1.5.2.1.19,DLSW-MIB::dlswCircuitFCSendGrantedUnits,INTEGER,read-only,,current,,The number of paced SSP messages that this DLSw is currently authorized to send on this circuit before it must stop and wait for an additional flow control indication from the partner DLSw. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.20,DLSW-MIB::dlswCircuitFCSendCurrentWndw,INTEGER,read-only,,current,,The current window size that this DLSw is using in its role as a data sender. This is the value by which this DLSw would increase the number of messages it is authorized to send, if it were to receive a flow control indication with the bits specifying `repeat window'. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.21,DLSW-MIB::dlswCircuitFCRecvGrantedUnits,INTEGER,read-only,,current,,The current number of paced SSP messages that this DLSw has authorized the partner DLSw to send on this circuit before the partner DLSw must stop and wait for an additional flow control indication from this DLSw. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.22,DLSW-MIB::dlswCircuitFCRecvCurrentWndw,INTEGER,read-only,,current,,The current window size that this DLSw is using in its role as a data receiver. This is the number of additional paced SSP messages that this DLSw would be authorizing its DLSw partner to send, if this DLSw were to send a flow control indication with the bits specifying `repeat window'. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.23,DLSW-MIB::dlswCircuitFCLargestRecvGranted,Gauge32,read-only,,current,,The largest receive window size granted by this DLSw during the current activation of this circuit. This is not the largest number of messages granted at any time, but the largest window size as represented by FCIND operator bits. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.24,DLSW-MIB::dlswCircuitFCLargestSendGranted,Gauge32,read-only,,current,,The largest send (with respect to this DLSw) window size granted by the partner DLSw during the current activation of this circuit. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.25,DLSW-MIB::dlswCircuitFCHalveWndwSents,Counter32,read-only,,current,,The number of Halve Window operations this DLSw has sent on this circuit, in its role as a data receiver. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.26,DLSW-MIB::dlswCircuitFCResetOpSents,Counter32,read-only,,current,,The number of Reset Window operations this DLSw has sent on this circuit, in its role as a data receiver. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.27,DLSW-MIB::dlswCircuitFCHalveWndwRcvds,Counter32,read-only,,current,,The number of Halve Window operations this DLSw has received on this circuit, in its role as a data sender. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.28,DLSW-MIB::dlswCircuitFCResetOpRcvds,Counter32,read-only,,current,,The number of Reset Window operations this DLSw has received on this circuit, in its role as a data sender. The value zero should be returned if this circuit is not running the DLSw pacing protocol.
.1.3.6.1.2.1.46.1.5.2.1.29,DLSW-MIB::dlswCircuitDiscReasonLocal,INTEGER,read-only,,current,endStationDiscRcvd(1):endStationDlcError(2):protocolError(3):operatorCommand(4):haltDlRcvd(5):haltDlNoAckRcvd(6):transportConnClosed(7),The reason why this circuit was last disconnected, as seen by this DLSw node. This object is present only if the agent keeps circuit table entries around for some period after circuit disconnect.
.1.3.6.1.2.1.46.1.5.2.1.30,DLSW-MIB::dlswCircuitDiscReasonRemote,INTEGER,read-only,,current,unknown(1):endStationDiscRcvd(2):endStationDlcError(3):protocolError(4):operatorCommand(5),The generic reason code why this circuit was last disconnected, as reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK. If the partner does not send a reason code in these messages, or the DLSw implementation does not report receiving one, the value `unknown' is returned. This object is present only if the agent keeps circuit table entries around for some period after circuit disconnect.
.1.3.6.1.2.1.46.1.5.2.1.31,DLSW-MIB::dlswCircuitDiscReasonRemoteData,OCTET,read-only,,current,,Implementation-specific data reported by the DLSw partner in a HALT_DL or HALT_DL_NOACK, to help specify how and why this circuit was last disconnected. If the partner does not send this data in these messages, or the DLSw implementation does not report receiving it, a string of zero length is returned. This object is present only if the agent keeps circuit table entries around for some period after circuit disconnect.
.1.3.6.1.2.1.46.1.6,DLSW-MIB::dlswSdlc,,,,,,
.1.3.6.1.2.1.46.1.6.1,DLSW-MIB::dlswSdlcLsEntries,Gauge32,read-only,,current,,The number of entries in dlswSdlcLsTable.
.1.3.6.1.2.1.46.1.6.2,DLSW-MIB::dlswSdlcLsTable,,not-accessible,,current,,The table defines the virtual MAC addresses for those SDLC link stations that participate in data link switching.
.1.3.6.1.2.1.46.1.6.2.1,DLSW-MIB::dlswSdlcLsEntry,,not-accessible,ifIndex:sdlcLSAddress,current,,The index of this table is the ifIndex value for the SDLC port which owns this link station and the poll address of the particular SDLC link station.
.1.3.6.1.2.1.46.1.6.2.1.1,DLSW-MIB::dlswSdlcLsLocalMac,OCTET,read-create,,current,,The virtual MAC address used to represent the SDLC-attached link station to the rest of the DLSw network.
.1.3.6.1.2.1.46.1.6.2.1.2,DLSW-MIB::dlswSdlcLsLocalSap,OCTET,read-create,,current,,The SAP used to represent this link station.
.1.3.6.1.2.1.46.1.6.2.1.3,DLSW-MIB::dlswSdlcLsLocalIdBlock,OCTET,read-create,,current,,The block number is the first three digits of the node_id, if available. These 3 hexadecimal digits identify the product.
.1.3.6.1.2.1.46.1.6.2.1.4,DLSW-MIB::dlswSdlcLsLocalIdNum,OCTET,read-create,,current,,The ID number is the last 5 digits of the node_id, if available. These 5 hexadecimal digits are administratively defined and combined with the 3 digit block number form the node_id. This node_id is used to identify the local node and is included in SNA XIDs.
.1.3.6.1.2.1.46.1.6.2.1.5,DLSW-MIB::dlswSdlcLsRemoteMac,OCTET,read-create,,current,,The MAC address to which DLSw should attempt to connect this link station. If this information is not available, a length of zero for this object should be returned.
.1.3.6.1.2.1.46.1.6.2.1.6,DLSW-MIB::dlswSdlcLsRemoteSap,OCTET,read-create,,current,,The SAP of the remote station to which this link station should be connected. If this information is not available, a length of zero for this object should be returned.
.1.3.6.1.2.1.46.1.6.2.1.7,DLSW-MIB::dlswSdlcLsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used by the manager to create or delete the row entry in the dlswSdlcLsTable following the RowStatus textual convention.
.1.3.6.1.2.1.46.2,DLSW-MIB::dlswDomains,,,,,,
.1.3.6.1.2.1.46.2.1,DLSW-MIB::dlswTCPDomain,,,,,,
.1.3.6.1.2.1.46.3,DLSW-MIB::dlswConformance,,,,,,
.1.3.6.1.2.1.46.3.1,DLSW-MIB::dlswCompliances,,,,,,
.1.3.6.1.2.1.46.3.1.1,DLSW-MIB::dlswCoreCompliance,,,,,,The core compliance statement for all DLSw nodes.
.1.3.6.1.2.1.46.3.1.2,DLSW-MIB::dlswTConnTcpCompliance,,,,,,Compliance for DLSw nodes that use TCP as a transport connection protocol.
.1.3.6.1.2.1.46.3.1.3,DLSW-MIB::dlswDirCompliance,,,,,,Compliance for DLSw nodes that provide a directory function.
.1.3.6.1.2.1.46.3.1.4,DLSW-MIB::dlswDirLocateCompliance,,,,,,Compliance for DLSw nodes that provide an ordered list of directory entries for a given resource.
.1.3.6.1.2.1.46.3.1.5,DLSW-MIB::dlswSdlcCompliance,,,,,,Compliance for DLSw nodes that support SDLC.
.1.3.6.1.2.1.46.3.2,DLSW-MIB::dlswGroups,,,,,,
.1.3.6.1.2.1.46.3.2.1,DLSW-MIB::dlswNodeGroup,,,,,,Conformance group for DLSw node general information.
.1.3.6.1.2.1.46.3.2.2,DLSW-MIB::dlswNodeNBGroup,,,,,,Conformance group for DLSw node general information specifically for nodes that support NetBIOS.
.1.3.6.1.2.1.46.3.2.3,DLSW-MIB::dlswTConnStatGroup,,,,,,Conformance group for statistics for transport connections.
.1.3.6.1.2.1.46.3.2.4,DLSW-MIB::dlswTConnConfigGroup,,,,,,Conformance group for the configuration of transport connections.
.1.3.6.1.2.1.46.3.2.5,DLSW-MIB::dlswTConnOperGroup,,,,,,Conformance group for operation information for transport connections.
.1.3.6.1.2.1.46.3.2.6,DLSW-MIB::dlswTConnNBGroup,,,,,,Conformance group for operation information for transport connections, specifically for nodes that support NetBIOS.
.1.3.6.1.2.1.46.3.2.7,DLSW-MIB::dlswTConnTcpConfigGroup,,,,,,Conformance group for configuration information for transport connections using TCP.
.1.3.6.1.2.1.46.3.2.8,DLSW-MIB::dlswTConnTcpOperGroup,,,,,,Conformance group for operation information for transport connections using TCP.
.1.3.6.1.2.1.46.3.2.9,DLSW-MIB::dlswInterfaceGroup,,,,,,Conformance group for DLSw interfaces.
.1.3.6.1.2.1.46.3.2.10,DLSW-MIB::dlswDirGroup,,,,,,Conformance group for DLSw directory using MAC addresses.
.1.3.6.1.2.1.46.3.2.11,DLSW-MIB::dlswDirNBGroup,,,,,,Conformance group for DLSw directory using NetBIOS names.
.1.3.6.1.2.1.46.3.2.12,DLSW-MIB::dlswDirLocateGroup,,,,,,Conformance group for a node that can return directory entry order for a given MAC address.
.1.3.6.1.2.1.46.3.2.13,DLSW-MIB::dlswDirLocateNBGroup,,,,,,Conformance group for a node that can return directory entry order for a given NetBIOS name.
.1.3.6.1.2.1.46.3.2.14,DLSW-MIB::dlswCircuitStatGroup,,,,,,Conformance group for statistics about circuits.
.1.3.6.1.2.1.46.3.2.15,DLSW-MIB::dlswCircuitGroup,,,,,,Conformance group for DLSw circuits.
.1.3.6.1.2.1.46.3.2.16,DLSW-MIB::dlswSdlcGroup,,,,,,Conformance group for DLSw SDLC support.
.1.3.6.1.2.1.46.3.2.17,DLSW-MIB::dlswNotificationGroup,,,,,,Conformance group for DLSw notifications.
.1.3.6.1.2.1.47,ENTITY-MIB::entityMIB,,,,,,The MIB module for representing multiple logical entities supported by a single SNMP agent. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.47.1,ENTITY-MIB::entityMIBObjects,,,,,,
.1.3.6.1.2.1.47.1.1,ENTITY-MIB::entityPhysical,,,,,,
.1.3.6.1.2.1.47.1.1.1,ENTITY-MIB::entPhysicalTable,,not-accessible,,current,,This table contains one row per physical entity. There is always at least one row for an 'overall' physical entity.
.1.3.6.1.2.1.47.1.1.1.1,ENTITY-MIB::entPhysicalEntry,,not-accessible,entPhysicalIndex,current,,Information about a particular physical entity. Each entry provides objects (entPhysicalDescr, entPhysicalVendorType, and entPhysicalClass) to help an NMS identify and characterize the entry and objects (entPhysicalContainedIn and entPhysicalParentRelPos) to help an NMS relate the particular entry to other entries in this table.
.1.3.6.1.2.1.47.1.1.1.1.1,ENTITY-MIB::entPhysicalIndex,Integer32,not-accessible,,current,,The index for this entry.
.1.3.6.1.2.1.47.1.1.1.1.2,ENTITY-MIB::entPhysicalDescr,OCTET,read-only,,current,,A textual description of physical entity. This object should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physical entity.
.1.3.6.1.2.1.47.1.1.1.1.3,ENTITY-MIB::entPhysicalVendorType,OBJECT,read-only,,current,,An indication of the vendor-specific hardware type of the physical entity. Note that this is different from the definition of MIB-II's sysObjectID. An agent should set this object to an enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device. If no vendor-specific registration identifier exists for this physical entity, or the value is unknown by this agent, then the value { 0 0 } is returned.
.1.3.6.1.2.1.47.1.1.1.1.4,ENTITY-MIB::entPhysicalContainedIn,Integer32,read-only,,current,,The value of entPhysicalIndex for the physical entity that 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity. Note that the set of 'containment' relationships define a strict hierarchy; that is, recursion is not allowed. In the event that a physical entity is contained by more than one physical entity (e.g., double-wide modules), this object should identify the containing entity with the lowest value of entPhysicalIndex.
.1.3.6.1.2.1.47.1.1.1.1.5,ENTITY-MIB::entPhysicalClass,INTEGER,read-only,,current,other(1):unknown(2):chassis(3):backplane(4):container(5):powerSupply(6):fan(7):sensor(8):module(9):port(10):stack(11):cpu(12):energyObject(13):battery(14):storageDrive(15),An indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one entity. If no appropriate standard registration identifier exists for this physical entity, then the value 'other(1)' is returned. If the value is unknown by this agent, then the value 'unknown(2)' is returned.
.1.3.6.1.2.1.47.1.1.1.1.6,ENTITY-MIB::entPhysicalParentRelPos,Integer32,read-only,,current,,An indication of the relative position of this 'child' component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects. An NMS can use this object to identify the relative ordering for all sibling components of a particular parent (identified by the entPhysicalContainedIn instance in each sibling entry). If possible, this value should match any external labeling of the physical component. For example, for a container (e.g., card slot) labeled as 'slot #3', entPhysicalParentRelPos should have the value '3'. Note that the entPhysicalEntry for the module plugged in slot 3 should have an entPhysicalParentRelPos value of '1'. If the physical position of this component does not match any external numbering or clearly visible ordering, then user documentation or other external reference material should be used to determine the parent-relative position. If this is not possible, then the agent should assign a consistent (but possibly arbitrary) ordering to a given set of 'sibling' components, perhaps based on internal representation of the components. If the agent cannot determine the parent-relative position for some reason, or if the associated value of entPhysicalContainedIn is '0', then the value '-1' is returned. Otherwise, a non-negative integer is returned, indicating the parent-relative position of this physical entity. Parent-relative ordering normally starts from '1' and continues to 'N', where 'N' represents the highest positioned child entity. However, if the physical entities (e.g., slots) are labeled from a starting position of zero, then the first sibling should be associated with an entPhysicalParentRelPos value of '0'. Note that this ordering may be sparse or dense, depending on agent implementation. The actual values returned are not globally meaningful, as each 'parent' component may use different numbering algorithms. The ordering is only meaningful among siblings of the same parent component. The agent should retain parent-relative position values across reboots, either through algorithmic assignment or use of non-volatile storage.
.1.3.6.1.2.1.47.1.1.1.1.7,ENTITY-MIB::entPhysicalName,OCTET,read-only,,current,,The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device's 'console'. This might be a text name (e.g., 'console') or a simple component number (e.g., port or module number, such as '1'), depending on the physical component naming syntax of the device. If there is no local name, or if this object is otherwise not applicable, then this object contains a zero-length string. Note that the value of entPhysicalName for two physical entities will be the same in the event that the console interface does not distinguish between them, e.g., slot-1 and the card in slot-1.
.1.3.6.1.2.1.47.1.1.1.1.8,ENTITY-MIB::entPhysicalHardwareRev,OCTET,read-only,,current,,The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present). Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific hardware revision string is associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.9,ENTITY-MIB::entPhysicalFirmwareRev,OCTET,read-only,,current,,The vendor-specific firmware revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific firmware programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.10,ENTITY-MIB::entPhysicalSoftwareRev,OCTET,read-only,,current,,The vendor-specific software revision string for the physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such information to a printable format in an implementation-specific manner. If no specific software programs are associated with the physical component, or if this information is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.11,ENTITY-MIB::entPhysicalSerialNum,OCTET,read-write,,current,,The vendor-specific serial number string for the physical entity. The preferred value is the serial number string actually printed on the component itself (if present). On the first instantiation of a physical entity, the value of entPhysicalSerialNum associated with that entity is set to the correct vendor-assigned serial number, if this information is available to the agent. If a serial number is unknown or non-existent, the entPhysicalSerialNum will be set to a zero-length string instead. Note that implementations that can correctly identify the serial numbers of all installed physical entities do not need to provide write access to the entPhysicalSerialNum object. Agents that cannot provide non-volatile storage for the entPhysicalSerialNum strings are not required to implement write access for this object. Not every physical component will have a serial number, or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique serial numbers. An agent does not have to provide write access for such entities and may return a zero-length string. If write access is implemented for an instance of entPhysicalSerialNum and a value is written into the instance, the agent must retain the supplied value in the entPhysicalSerialNum instance (associated with the same physical entity) for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the network management system, including those resulting in a change of the physical entity's entPhysicalIndex value.
.1.3.6.1.2.1.47.1.1.1.1.12,ENTITY-MIB::entPhysicalMfgName,OCTET,read-only,,current,,The name of the manufacturer of this physical component. The preferred value is the manufacturer name string actually printed on the component itself (if present). Note that comparisons between instances of the entPhysicalModelName, entPhysicalFirmwareRev, entPhysicalSoftwareRev, and the entPhysicalSerialNum objects are only meaningful amongst entPhysicalEntries with the same value of entPhysicalMfgName. If the manufacturer name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.13,ENTITY-MIB::entPhysicalModelName,OCTET,read-only,,current,,The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the model name string associated with the physical component is unknown to the agent, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.14,ENTITY-MIB::entPhysicalAlias,OCTET,read-write,,current,,This object is an 'alias' name for the physical entity, as specified by a network manager, and provides a non-volatile 'handle' for the physical entity. On the first instantiation of a physical entity, the value of entPhysicalAlias associated with that entity is set to the zero-length string. However, the agent may set the value to a locally unique default value, instead of a zero-length string. If write access is implemented for an instance of entPhysicalAlias and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAlias instance (associated with the same physical entity) for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the network management system, including those resulting in a change of the physical entity's entPhysicalIndex value.
.1.3.6.1.2.1.47.1.1.1.1.15,ENTITY-MIB::entPhysicalAssetID,OCTET,read-write,,current,,This object is a user-assigned asset tracking identifier (as specified by a network manager) for the physical entity and provides non-volatile storage of this information. On the first instantiation of a physical entity, the value of entPhysicalAssetID associated with that entity is set to the zero-length string. Not every physical component will have an asset tracking identifier or even need one. Physical entities for which the associated value of the entPhysicalIsFRU object is equal to 'false(2)' (e.g., the repeater ports within a repeater module) do not need their own unique asset tracking identifier. An agent does not have to provide write access for such entities and may instead return a zero-length string. If write access is implemented for an instance of entPhysicalAssetID and a value is written into the instance, the agent must retain the supplied value in the entPhysicalAssetID instance (associated with the same physical entity) for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the network management system, including those resulting in a change of the physical entity's entPhysicalIndex value. If no asset tracking information is associated with the physical component, then this object will contain a zero-length string.
.1.3.6.1.2.1.47.1.1.1.1.16,ENTITY-MIB::entPhysicalIsFRU,INTEGER,read-only,,current,true(1):false(2),This object indicates whether or not this physical entity is considered a 'field replaceable unit' by the vendor. If this object contains the value 'true(1)', then this entPhysicalEntry identifies a field replaceable unit. For all entPhysicalEntries that represent components permanently contained within a field replaceable unit, the value 'false(2)' should be returned for this object.
.1.3.6.1.2.1.47.1.1.1.1.17,ENTITY-MIB::entPhysicalMfgDate,OCTET,read-only,,current,,This object contains the date of manufacturing of the managed entity. If the manufacturing date is unknown or not supported, the object is not instantiated. The special value '0000000000000000'H may also be returned in this case.
.1.3.6.1.2.1.47.1.1.1.1.18,ENTITY-MIB::entPhysicalUris,OCTET,read-write,,current,,This object contains identification information about the physical entity. The object contains URIs; therefore, the syntax of this object must conform to RFC 3986, Section 3. Multiple URIs may be present and are separated by white space characters. Leading and trailing white space characters are ignored. If no URI identification information is known about the physical entity, the object is not instantiated. A zero-length octet string may also be returned in this case.
.1.3.6.1.2.1.47.1.1.1.1.19,ENTITY-MIB::entPhysicalUUID,OCTET,read-only,,current,,This object contains identification information about the physical entity. The object contains a Universally Unique Identifier, the syntax of this object must conform to RFC 4122, Section 4.1. A zero-length octet string is returned if no UUID information is known.
.1.3.6.1.2.1.47.1.2,ENTITY-MIB::entityLogical,,,,,,
.1.3.6.1.2.1.47.1.2.1,ENTITY-MIB::entLogicalTable,,not-accessible,,current,,This table contains one row per logical entity. For agents that implement more than one naming scope, at least one entry must exist. Agents that instantiate all MIB objects within a single naming scope are not required to implement this table.
.1.3.6.1.2.1.47.1.2.1.1,ENTITY-MIB::entLogicalEntry,,not-accessible,entLogicalIndex,current,,Information about a particular logical entity. Entities may be managed by this agent or other SNMP agents (possibly) in the same chassis.
.1.3.6.1.2.1.47.1.2.1.1.1,ENTITY-MIB::entLogicalIndex,Integer32,not-accessible,,current,,The value of this object uniquely identifies the logical entity. The value should be a small positive integer; index values for different logical entities are not necessarily contiguous.
.1.3.6.1.2.1.47.1.2.1.1.2,ENTITY-MIB::entLogicalDescr,OCTET,read-only,,current,,A textual description of the logical entity. This object should contain a string that identifies the manufacturer's name for the logical entity and should be set to a distinct value for each version of the logical entity.
.1.3.6.1.2.1.47.1.2.1.1.3,ENTITY-MIB::entLogicalType,OBJECT,read-only,,current,,An indication of the type of logical entity. This will typically be the OBJECT IDENTIFIER name of the node in the SMI's naming hierarchy that represents the major MIB module, or the majority of the MIB modules, supported by the logical entity. For example: a logical entity of a regular host/router -> mib-2 a logical entity of a 802.1d bridge -> dot1dBridge a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt If an appropriate node in the SMI's naming hierarchy cannot be identified, the value 'mib-2' should be used.
.1.3.6.1.2.1.47.1.2.1.1.4,ENTITY-MIB::entLogicalCommunity,OCTET,read-only,,deprecated,,An SNMPv1 or SNMPv2c community string, which can be used to access detailed management information for this logical entity. The agent should allow read access with this community string (to an appropriate subset of all managed objects) and may also return a community string based on the privileges of the request used to read this object. Note that an agent may return a community string with read-only privileges, even if this object is accessed with a read-write community string. However, the agent must take care not to return a community string that allows more privileges than the community string used to access this object. A compliant SNMP agent may wish to conserve naming scopes by representing multiple logical entities in a single 'default' naming scope. This is possible when the logical entities, represented by the same value of entLogicalCommunity, have no object instances in common. For example, 'bridge1' and 'repeater1' may be part of the main naming scope, but at least one additional community string is needed to represent 'bridge2' and 'repeater2'. Logical entities 'bridge1' and 'repeater1' would be represented by sysOREntries associated with the 'default' naming scope. For agents not accessible via SNMPv1 or SNMPv2c, the value of this object is the empty string. This object may also contain an empty string if a community string has not yet been assigned by the agent or if no community string with suitable access rights can be returned for a particular SNMP request. Note that this object is deprecated. Agents that implement SNMPv3 access should use the entLogicalContextEngineID and entLogicalContextName objects to identify the context associated with each logical entity. SNMPv3 agents may return a zero-length string for this object or may continue to return a community string (e.g., tri-lingual agent support).
.1.3.6.1.2.1.47.1.2.1.1.5,ENTITY-MIB::entLogicalTAddress,OCTET,read-only,,current,,The transport service address by which the logical entity receives network management traffic, formatted according to the corresponding value of entLogicalTDomain. For snmpUDPDomain, a TAddress is 6 octets long: the initial 4 octets contain the IP-address in network-byte order, and the last 2 contain the UDP port in network-byte order. Consult RFC 3417 for further information on snmpUDPDomain.
.1.3.6.1.2.1.47.1.2.1.1.6,ENTITY-MIB::entLogicalTDomain,OBJECT,read-only,,current,,Indicates the kind of transport service by which the logical entity receives network management traffic. Possible values for this object are presently found in RFC 3417.
.1.3.6.1.2.1.47.1.2.1.1.7,ENTITY-MIB::entLogicalContextEngineID,OCTET,read-only,,current,,The authoritative contextEngineID that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair. This object, together with the associated entLogicalContextName object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineID and contextName pair. If no value has been configured by the agent, a zero-length string is returned, or the agent may choose not to instantiate this object at all.
.1.3.6.1.2.1.47.1.2.1.1.8,ENTITY-MIB::entLogicalContextName,OCTET,read-only,,current,,The contextName that can be used to send an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair. This object, together with the associated entLogicalContextEngineID object, defines the context associated with a particular logical entity and allows access to SNMP engines identified by a contextEngineID and contextName pair. If no value has been configured by the agent, a zero-length string is returned, or the agent may choose not to instantiate this object at all.
.1.3.6.1.2.1.47.1.3,ENTITY-MIB::entityMapping,,,,,,
.1.3.6.1.2.1.47.1.3.1,ENTITY-MIB::entLPMappingTable,,not-accessible,,current,,This table contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources, which are used to realize that logical entity. An agent should limit the number and nature of entries in this table such that only meaningful and non-redundant information is returned. For example, in a system that contains a single power supply, mappings between logical entities and the power supply are not useful and should not be included. Also, only the most appropriate physical component, which is closest to the root of a particular containment tree, should be identified in an entLPMapping entry. For example, suppose a bridge is realized on a particular module, and all ports on that module are ports on this bridge. A mapping between the bridge and the module would be useful, but additional mappings between the bridge and each of the ports on that module would be redundant (because the entPhysicalContainedIn hierarchy can provide the same information). On the other hand, if more than one bridge were utilizing ports on this module, then mappings between each bridge and the ports it used would be appropriate. Also, in the case of a single backplane repeater, a mapping for the backplane to the single repeater entity is not necessary.
.1.3.6.1.2.1.47.1.3.1.1,ENTITY-MIB::entLPMappingEntry,,not-accessible,entLogicalIndex:entLPPhysicalIndex,current,,Information about a particular logical-entity-to-physical- equipment association. Note that the nature of the association is not specifically identified in this entry. It is expected that sufficient information exists in the MIB modules used to manage a particular logical entity to infer how physical component information is utilized.
.1.3.6.1.2.1.47.1.3.1.1.1,ENTITY-MIB::entLPPhysicalIndex,Integer32,read-only,,current,,The value of this object identifies the index value of a particular entPhysicalEntry associated with the indicated entLogicalEntity.
.1.3.6.1.2.1.47.1.3.2,ENTITY-MIB::entAliasMappingTable,,not-accessible,,current,,This table contains zero or more rows, representing mappings of logical entities and physical components to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical entity's naming scope. A 'wildcard' mechanism is provided to indicate that an identifier is associated with more than one logical entity.
.1.3.6.1.2.1.47.1.3.2.1,ENTITY-MIB::entAliasMappingEntry,,not-accessible,entPhysicalIndex:entAliasLogicalIndexOrZero,current,,Information about a particular binding between a logical entity/physical component pair and an external identifier. Each logical entity/physical component pair may be associated with one alias mapping. The logical entity index may also be used as a 'wildcard' (refer to the entAliasLogicalIndexOrZero objectclause for details.) Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
.1.3.6.1.2.1.47.1.3.2.1.1,ENTITY-MIB::entAliasLogicalIndexOrZero,Integer32,not-accessible,,current,,The value of this object identifies the logical entity that defines the naming scope for the associated instance of the entAliasMappingIdentifier object. If this object has a non-zero value, then it identifies the logical entity named by the same value of entLogicalIndex. If this object has a value of zero, then the mapping between the physical component and the alias identifier for this entAliasMapping entry is associated with all unspecified logical entities. That is, a value of zero (the default mapping) identifies any logical entity that does not have an explicit entry in this table for a particular entPhysicalIndex/entAliasMappingIdentifier pair. For example, to indicate that a particular interface (e.g., physical component 33) is identified by the same value of ifIndex for all logical entities, the following instance might exist: entAliasMappingIdentifier.33.0 = ifIndex.5 In the event an entPhysicalEntry is associated differently for some logical entities, additional entAliasMapping entries may exist, e.g.: entAliasMappingIdentifier.33.0 = ifIndex.6 entAliasMappingIdentifier.33.4 = ifIndex.1 entAliasMappingIdentifier.33.5 = ifIndex.1 entAliasMappingIdentifier.33.10 = ifIndex.12 Note that entries with non-zero entAliasLogicalIndexOrZero index values have precedence over zero-indexed entries. In this example, all logical entities except 4, 5, and 10 associate physical entity 33 with ifIndex.6.
.1.3.6.1.2.1.47.1.3.2.1.2,ENTITY-MIB::entAliasMappingIdentifier,OBJECT,read-only,,current,,The value of this object identifies a particular conceptual row associated with the indicated entPhysicalIndex and entLogicalIndex pair. Because only physical ports are modeled in this table, only entries that represent interfaces or ports are allowed. If an ifEntry exists on behalf of a particular physical port, then this object should identify the associated ifEntry. For repeater ports, the appropriate row in the 'rptrPortGroupTable' should be identified instead. For example, suppose a physical port was represented by entPhysicalEntry.3, entLogicalEntry.15 existed for a repeater, and entLogicalEntry.22 existed for a bridge. Then there might be two related instances of entAliasMappingIdentifier: entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2 entAliasMappingIdentifier.3.22 == ifIndex.17 It is possible that other mappings (besides interfaces and repeater ports) may be defined in the future, as required. Bridge ports are identified by examining the Bridge MIB and appropriate ifEntries associated with each 'dot1dBasePort' and are thus not represented in this table.
.1.3.6.1.2.1.47.1.3.3,ENTITY-MIB::entPhysicalContainsTable,,not-accessible,,current,,A table that exposes the container/'containee' relationships between physical entities. This table provides all the information found by constructing the virtual containment tree for a given entPhysicalTable, but in a more direct format. In the event a physical entity is contained by more than one other physical entity (e.g., double-wide modules), this table should include these additional mappings, which cannot be represented in the entPhysicalTable virtual containment tree.
.1.3.6.1.2.1.47.1.3.3.1,ENTITY-MIB::entPhysicalContainsEntry,,not-accessible,entPhysicalIndex:entPhysicalChildIndex,current,,A single container/'containee' relationship.
.1.3.6.1.2.1.47.1.3.3.1.1,ENTITY-MIB::entPhysicalChildIndex,Integer32,read-only,,current,,The value of entPhysicalIndex for the contained physical entity.
.1.3.6.1.2.1.47.1.4,ENTITY-MIB::entityGeneral,,,,,,
.1.3.6.1.2.1.47.1.4.1,ENTITY-MIB::entLastChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time a conceptual row is created, modified, or deleted in any of these tables: - entPhysicalTable - entLogicalTable - entLPMappingTable - entAliasMappingTable - entPhysicalContainsTable 
.1.3.6.1.2.1.47.2,ENTITY-MIB::entityMIBTraps,,,,,,
.1.3.6.1.2.1.47.2.0,ENTITY-MIB::entityMIBTrapPrefix,,,,,,
.1.3.6.1.2.1.47.2.0.1,ENTITY-MIB::entConfigChange,,,,,,An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than one entConfigChange 'notification-event' in a given time interval (five seconds is the suggested default). A 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If additional configuration changes occur within the throttling period, then notification-events for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notification-event should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notification-events, e.g., due to throttling or transmission loss.
.1.3.6.1.2.1.47.3,ENTITY-MIB::entityConformance,,,,,,
.1.3.6.1.2.1.47.3.1,ENTITY-MIB::entityCompliances,,,,,,
.1.3.6.1.2.1.47.3.1.1,ENTITY-MIB::entityCompliance,,,,,,The compliance statement for SNMP entities that implement version 1 of the Entity MIB.
.1.3.6.1.2.1.47.3.1.2,ENTITY-MIB::entity2Compliance,,,,,,The compliance statement for SNMP entities that implement version 2 of the Entity MIB.
.1.3.6.1.2.1.47.3.1.3,ENTITY-MIB::entity3Compliance,,,,,,The compliance statement for SNMP entities that implement version 3 of the Entity MIB.
.1.3.6.1.2.1.47.3.1.4,ENTITY-MIB::entity4Compliance,,,,,,The compliance statement for SNMP entities that implement the full version 4 (full compliance) of the Entity MIB.
.1.3.6.1.2.1.47.3.1.5,ENTITY-MIB::entity4CRCompliance,,,,,,The compliance statement for SNMP entities that implement version 4 of the Entity MIB on devices with constrained resources.
.1.3.6.1.2.1.47.3.2,ENTITY-MIB::entityGroups,,,,,,
.1.3.6.1.2.1.47.3.2.1,ENTITY-MIB::entityPhysicalGroup,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.2,ENTITY-MIB::entityLogicalGroup,,,,,,The collection of objects used to represent the list of logical entities for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.3,ENTITY-MIB::entityMappingGroup,,,,,,The collection of objects used to represent the associations between multiple logical entities, physical components, interfaces, and port identifiers for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.4,ENTITY-MIB::entityGeneralGroup,,,,,,The collection of objects used to represent general entity information for which a single agent provides management information.
.1.3.6.1.2.1.47.3.2.5,ENTITY-MIB::entityNotificationsGroup,,,,,,The collection of notifications used to indicate Entity MIB data consistency and general status information.
.1.3.6.1.2.1.47.3.2.6,ENTITY-MIB::entityPhysical2Group,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information. This group augments the objects contained in the entityPhysicalGroup.
.1.3.6.1.2.1.47.3.2.7,ENTITY-MIB::entityLogical2Group,,,,,,The collection of objects used to represent the list of logical entities for which a single SNMP entity provides management information.
.1.3.6.1.2.1.47.3.2.8,ENTITY-MIB::entityPhysical3Group,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information. This group augments the objects contained in the entityPhysicalGroup.
.1.3.6.1.2.1.47.3.2.9,ENTITY-MIB::entityPhysical4Group,,,,,,The collection of objects used to represent physical system components for which a single agent provides management information. This group augments the objects contained in the entityPhysicalGroup and entityPhysicalCRGroup.
.1.3.6.1.2.1.47.3.2.10,ENTITY-MIB::entityPhysicalCRGroup,,,,,,The collection of objects used to represent physical system components for constrained resourced devices, for which a single agent provides management information.
.1.3.6.1.2.1.48,IP-MIB::ipMIB,,,,,,The MIB module for managing IP and ICMP implementations, but excluding their management of IP routes. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4293; see the RFC itself for full legal notices.
.1.3.6.1.2.1.48.2,IP-MIB::ipMIBConformance,,,,,,
.1.3.6.1.2.1.48.2.1,IP-MIB::ipMIBCompliances,,,,,,
.1.3.6.1.2.1.48.2.1.1,IP-MIB::ipMIBCompliance,,,,,,The compliance statement for systems that implement only IPv4. For version-independence, this compliance statement is deprecated in favor of ipMIBCompliance2.
.1.3.6.1.2.1.48.2.1.2,IP-MIB::ipMIBCompliance2,,,,,,The compliance statement for systems that implement IP - either IPv4 or IPv6. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT ipSystemStatsIPVersion -- SYNTAX InetVersion {ipv4(1), ipv6(2)} -- DESCRIPTION -- This MIB requires support for only IPv4 and IPv6 -- versions. -- -- OBJECT ipIfStatsIPVersion -- SYNTAX InetVersion {ipv4(1), ipv6(2)} -- DESCRIPTION -- This MIB requires support for only IPv4 and IPv6 -- versions. -- -- OBJECT icmpStatsIPVersion -- SYNTAX InetVersion {ipv4(1), ipv6(2)} -- DESCRIPTION -- This MIB requires support for only IPv4 and IPv6 -- versions. -- -- OBJECT icmpMsgStatsIPVersion -- SYNTAX InetVersion {ipv4(1), ipv6(2)} -- DESCRIPTION -- This MIB requires support for only IPv4 and IPv6 -- versions. -- -- OBJECT ipAddressPrefixType -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} -- DESCRIPTION -- This MIB requires support for only global IPv4 and -- IPv6 address types. -- -- OBJECT ipAddressPrefixPrefix -- SYNTAX InetAddress (Size(4 | 16)) -- DESCRIPTION -- This MIB requires support for only global IPv4 and -- IPv6 addresses and so the size can be either 4 or -- 16 bytes. -- -- OBJECT ipAddressAddrType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This MIB requires support for only global and -- non-global IPv4 and IPv6 address types. -- -- OBJECT ipAddressAddr -- SYNTAX InetAddress (Size(4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for only global and -- non-global IPv4 and IPv6 addresses and so the size -- can be 4, 8, 16, or 20 bytes. -- -- OBJECT ipNetToPhysicalNetAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This MIB requires support for only global and -- non-global IPv4 and IPv6 address types. -- -- OBJECT ipNetToPhysicalNetAddress -- SYNTAX InetAddress (Size(4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for only global and -- non-global IPv4 and IPv6 addresses and so the size -- can be 4, 8, 16, or 20 bytes. -- -- OBJECT ipDefaultRouterAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This MIB requires support for only global and -- non-global IPv4 and IPv6 address types. -- -- OBJECT ipDefaultRouterAddress -- SYNTAX InetAddress (Size(4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for only global and -- non-global IPv4 and IPv6 addresses and so the size -- can be 4, 8, 16, or 20 bytes.
.1.3.6.1.2.1.48.2.2,IP-MIB::ipMIBGroups,,,,,,
.1.3.6.1.2.1.48.2.2.1,IP-MIB::ipGroup,,,,,,The ip group of objects providing for basic management of IP entities, exclusive of the management of IP routes. As part of the version independence, this group has been deprecated. 
.1.3.6.1.2.1.48.2.2.2,IP-MIB::icmpGroup,,,,,,The icmp group of objects providing ICMP statistics. As part of the version independence, this group has been deprecated. 
.1.3.6.1.2.1.48.2.2.3,IP-MIB::ipv4GeneralGroup,,,,,,The group of IPv4-specific objects for basic management of IPv4 entities.
.1.3.6.1.2.1.48.2.2.4,IP-MIB::ipv4IfGroup,,,,,,The group of IPv4-specific objects for basic management of IPv4 interfaces.
.1.3.6.1.2.1.48.2.2.5,IP-MIB::ipv6GeneralGroup2,,,,,,The IPv6 group of objects providing for basic management of IPv6 entities.
.1.3.6.1.2.1.48.2.2.6,IP-MIB::ipv6IfGroup,,,,,,The group of IPv6-specific objects for basic management of IPv6 interfaces.
.1.3.6.1.2.1.48.2.2.7,IP-MIB::ipLastChangeGroup,,,,,,The last change objects associated with this MIB. These objects are optional for all agents. They SHOULD be implemented on agents where it is possible to determine the proper values. Where it is not possible to determine the proper values, for example when the tables are split amongst several sub-agents using AgentX, the agent MUST NOT implement these objects to return an incorrect or static value.
.1.3.6.1.2.1.48.2.2.8,IP-MIB::ipSystemStatsGroup,,,,,,IP system wide statistics.
.1.3.6.1.2.1.48.2.2.9,IP-MIB::ipv4SystemStatsGroup,,,,,,IPv4 only system wide statistics.
.1.3.6.1.2.1.48.2.2.10,IP-MIB::ipSystemStatsHCOctetGroup,,,,,,IP system wide statistics for systems that may overflow the standard octet counters within 1 hour.
.1.3.6.1.2.1.48.2.2.11,IP-MIB::ipSystemStatsHCPacketGroup,,,,,,IP system wide statistics for systems that may overflow the standard packet counters within 1 hour.
.1.3.6.1.2.1.48.2.2.12,IP-MIB::ipv4SystemStatsHCPacketGroup,,,,,,IPv4 only system wide statistics for systems that may overflow the standard packet counters within 1 hour.
.1.3.6.1.2.1.48.2.2.13,IP-MIB::ipIfStatsGroup,,,,,,IP per-interface statistics.
.1.3.6.1.2.1.48.2.2.14,IP-MIB::ipv4IfStatsGroup,,,,,,IPv4 only per-interface statistics.
.1.3.6.1.2.1.48.2.2.15,IP-MIB::ipIfStatsHCOctetGroup,,,,,,IP per-interfaces statistics for systems that include interfaces that may overflow the standard octet counters within 1 hour.
.1.3.6.1.2.1.48.2.2.16,IP-MIB::ipIfStatsHCPacketGroup,,,,,,IP per-interfaces statistics for systems that include interfaces that may overflow the standard packet counters within 1 hour.
.1.3.6.1.2.1.48.2.2.17,IP-MIB::ipv4IfStatsHCPacketGroup,,,,,,IPv4 only per-interface statistics for systems that include interfaces that may overflow the standard packet counters within 1 hour.
.1.3.6.1.2.1.48.2.2.18,IP-MIB::ipAddressPrefixGroup,,,,,,The group of objects for providing information about address prefixes used by this node.
.1.3.6.1.2.1.48.2.2.19,IP-MIB::ipAddressGroup,,,,,,The group of objects for providing information about the addresses relevant to this entity's interfaces.
.1.3.6.1.2.1.48.2.2.20,IP-MIB::ipNetToPhysicalGroup,,,,,,The group of objects for providing information about the mappings of network address to physical address known to this node.
.1.3.6.1.2.1.48.2.2.21,IP-MIB::ipv6ScopeGroup,,,,,,The group of objects for managing IPv6 scope zones.
.1.3.6.1.2.1.48.2.2.22,IP-MIB::ipDefaultRouterGroup,,,,,,The group of objects for providing information about default routers known to this node.
.1.3.6.1.2.1.48.2.2.23,IP-MIB::ipv6RouterAdvertGroup,,,,,,The group of objects for controlling information advertised by IPv6 routers.
.1.3.6.1.2.1.48.2.2.24,IP-MIB::icmpStatsGroup,,,,,,The group of objects providing ICMP statistics.
.1.3.6.1.2.1.49,TCP-MIB::tcpMIB,,,,,,The MIB module for managing TCP implementations. Copyright (C) The Internet Society (2005). This version of this MIB module is a part of RFC 4022; see the RFC itself for full legal notices.
.1.3.6.1.2.1.49.2,TCP-MIB::tcpMIBConformance,,,,,,
.1.3.6.1.2.1.49.2.1,TCP-MIB::tcpMIBCompliances,,,,,,
.1.3.6.1.2.1.49.2.1.1,TCP-MIB::tcpMIBCompliance,,,,,,The compliance statement for IPv4-only systems that implement TCP. In order to be IP version independent, this compliance statement is deprecated in favor of tcpMIBCompliance2. However, agents are still encouraged to implement these objects in order to interoperate with the deployed base of managers.
.1.3.6.1.2.1.49.2.1.2,TCP-MIB::tcpMIBCompliance2,,,,,,The compliance statement for systems that implement TCP. A number of INDEX objects cannot be represented in the form of OBJECT clauses in SMIv2 but have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT tcpConnectionLocalAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. -- -- OBJECT tcpConnectionRemAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. -- -- OBJECT tcpListenerLocalAddressType -- SYNTAX InetAddressType { unknown(0), ipv4(1), -- ipv6(2) } -- DESCRIPTION -- This MIB requires support for only global IPv4 -- and IPv6 address types. The type unknown also -- needs to be supported to identify a special -- case in the listener table: a listen using -- both IPv4 and IPv6 addresses on the device. -- 
.1.3.6.1.2.1.49.2.2,TCP-MIB::tcpMIBGroups,,,,,,
.1.3.6.1.2.1.49.2.2.1,TCP-MIB::tcpGroup,,,,,,The tcp group of objects providing for management of TCP entities.
.1.3.6.1.2.1.49.2.2.2,TCP-MIB::tcpBaseGroup,,,,,,The group of counters common to TCP entities.
.1.3.6.1.2.1.49.2.2.3,TCP-MIB::tcpConnectionGroup,,,,,,The group provides general information about TCP connections.
.1.3.6.1.2.1.49.2.2.4,TCP-MIB::tcpListenerGroup,,,,,,This group has objects providing general information about TCP listeners.
.1.3.6.1.2.1.49.2.2.5,TCP-MIB::tcpHCGroup,,,,,,The group of objects providing for counters of high speed TCP implementations.
.1.3.6.1.2.1.50,UDP-MIB::udpMIB,,,,,,The MIB module for managing UDP implementations. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4113; see the RFC itself for full legal notices.
.1.3.6.1.2.1.50.2,UDP-MIB::udpMIBConformance,,,,,,
.1.3.6.1.2.1.50.2.1,UDP-MIB::udpMIBCompliances,,,,,,
.1.3.6.1.2.1.50.2.1.1,UDP-MIB::udpMIBCompliance,,,,,,The compliance statement for IPv4-only systems that implement UDP. For IP version independence, this compliance statement is deprecated in favor of udpMIBCompliance2. However, agents are still encouraged to implement these objects in order to interoperate with the deployed base of managers.
.1.3.6.1.2.1.50.2.1.2,UDP-MIB::udpMIBCompliance2,,,,,,The compliance statement for systems that implement UDP. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT udpEndpointLocalAddressType -- SYNTAX InetAddressType { unknown(0), ipv4(1), -- ipv6(2), ipv4z(3), -- ipv6z(4) } -- DESCRIPTION -- Support for dns(5) is not required. -- OBJECT udpEndpointLocalAddress -- SYNTAX InetAddress (SIZE(0|4|8|16|20)) -- DESCRIPTION -- Support is only required for zero-length -- octet-strings, and for scoped and unscoped -- IPv4 and IPv6 addresses. -- OBJECT udpEndpointRemoteAddressType -- SYNTAX InetAddressType { unknown(0), ipv4(1), -- ipv6(2), ipv4z(3), -- ipv6z(4) } -- DESCRIPTION -- Support for dns(5) is not required. -- OBJECT udpEndpointRemoteAddress -- SYNTAX InetAddress (SIZE(0|4|8|16|20)) -- DESCRIPTION -- Support is only required for zero-length -- octet-strings, and for scoped and unscoped -- IPv4 and IPv6 addresses. 
.1.3.6.1.2.1.50.2.2,UDP-MIB::udpMIBGroups,,,,,,
.1.3.6.1.2.1.50.2.2.1,UDP-MIB::udpGroup,,,,,,The deprecated group of objects providing for management of UDP over IPv4.
.1.3.6.1.2.1.50.2.2.2,UDP-MIB::udpBaseGroup,,,,,,The group of objects providing for counters of UDP statistics.
.1.3.6.1.2.1.50.2.2.3,UDP-MIB::udpHCGroup,,,,,,The group of objects providing for counters of high speed UDP implementations.
.1.3.6.1.2.1.50.2.2.4,UDP-MIB::udpEndpointGroup,,,,,,The group of objects providing for the IP version independent management of UDP 'endpoints'.
.1.3.6.1.2.1.51,RSVP-MIB::rsvp,,,,,,The MIB module to describe the RSVP Protocol
.1.3.6.1.2.1.51.1,RSVP-MIB::rsvpObjects,,,,,,
.1.3.6.1.2.1.51.1.1,RSVP-MIB::rsvpSessionTable,,not-accessible,,current,,A table of all sessions seen by a given sys- tem.
.1.3.6.1.2.1.51.1.1.1,RSVP-MIB::rsvpSessionEntry,,not-accessible,rsvpSessionNumber,current,,A single session seen by a given system.
.1.3.6.1.2.1.51.1.1.1.1,RSVP-MIB::rsvpSessionNumber,INTEGER,not-accessible,,current,,The number of this session. This is for SNMP Indexing purposes only and has no relation to any protocol value.
.1.3.6.1.2.1.51.1.1.1.2,RSVP-MIB::rsvpSessionType,INTEGER,read-only,,current,,The type of session (IP4, IP6, IP6 with flow information, etc).
.1.3.6.1.2.1.51.1.1.1.3,RSVP-MIB::rsvpSessionDestAddr,OCTET,read-only,,current,,The destination address used by all senders in this session. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.51.1.1.1.4,RSVP-MIB::rsvpSessionDestAddrLength,INTEGER,read-only,,current,,The CIDR prefix length of the session address, which is 32 for IP4 host and multicast ad- dresses, and 128 for IP6 addresses. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.1.1.5,RSVP-MIB::rsvpSessionProtocol,INTEGER,read-only,,current,,The IP Protocol used by this session. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.1.1.6,RSVP-MIB::rsvpSessionPort,OCTET,read-only,,current,,The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpSen- derProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.1.1.7,RSVP-MIB::rsvpSessionSenders,Gauge32,read-only,,current,,The number of distinct senders currently known to be part of this session.
.1.3.6.1.2.1.51.1.1.1.8,RSVP-MIB::rsvpSessionReceivers,Gauge32,read-only,,current,,The number of reservations being requested of this system for this session.
.1.3.6.1.2.1.51.1.1.1.9,RSVP-MIB::rsvpSessionRequests,Gauge32,read-only,,current,,The number of reservation requests this system is sending upstream for this session.
.1.3.6.1.2.1.51.1.2,RSVP-MIB::rsvpSenderTable,,not-accessible,,current,,Information describing the state information displayed by senders in PATH messages.
.1.3.6.1.2.1.51.1.2.1,RSVP-MIB::rsvpSenderEntry,,not-accessible,rsvpSessionNumber:rsvpSenderNumber,current,,Information describing the state information displayed by a single sender's PATH message.
.1.3.6.1.2.1.51.1.2.1.1,RSVP-MIB::rsvpSenderNumber,INTEGER,not-accessible,,current,,The number of this sender. This is for SNMP Indexing purposes only and has no relation to any protocol value.
.1.3.6.1.2.1.51.1.2.1.2,RSVP-MIB::rsvpSenderType,INTEGER,read-create,,current,,The type of session (IP4, IP6, IP6 with flow information, etc).
.1.3.6.1.2.1.51.1.2.1.3,RSVP-MIB::rsvpSenderDestAddr,OCTET,read-create,,current,,The destination address used by all senders in this session. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.51.1.2.1.4,RSVP-MIB::rsvpSenderAddr,OCTET,read-create,,current,,The source address used by this sender in this session. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.2.1.5,RSVP-MIB::rsvpSenderDestAddrLength,INTEGER,read-create,,current,,The length of the destination address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.2.1.6,RSVP-MIB::rsvpSenderAddrLength,INTEGER,read-create,,current,,The length of the sender's address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.2.1.7,RSVP-MIB::rsvpSenderProtocol,INTEGER,read-create,,current,,The IP Protocol used by this session. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.2.1.8,RSVP-MIB::rsvpSenderDestPort,OCTET,read-create,,current,,The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpSen- derProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.2.1.9,RSVP-MIB::rsvpSenderPort,OCTET,read-create,,current,,The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpSenderPro- tocol is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.51.1.2.1.10,RSVP-MIB::rsvpSenderFlowId,INTEGER,read-only,,current,,The flow ID that this sender is using, if this is an IPv6 session.
.1.3.6.1.2.1.51.1.2.1.11,RSVP-MIB::rsvpSenderHopAddr,OCTET,read-create,,current,,The address used by the previous RSVP hop (which may be the original sender).
.1.3.6.1.2.1.51.1.2.1.12,RSVP-MIB::rsvpSenderHopLih,Integer32,read-create,,current,,The Logical Interface Handle used by the pre- vious RSVP hop (which may be the original sender).
.1.3.6.1.2.1.51.1.2.1.13,RSVP-MIB::rsvpSenderInterface,Integer32,read-create,,current,,The ifIndex value of the interface on which this PATH message was most recently received.
.1.3.6.1.2.1.51.1.2.1.14,RSVP-MIB::rsvpSenderTSpecRate,INTEGER,read-create,,current,,The Average Bit Rate of the sender's data stream. Within a transmission burst, the ar- rival rate may be as fast as rsvpSenderTSpec- PeakRate (if supported by the service model); however, averaged across two or more burst in- tervals, the rate should not exceed rsvpSen- derTSpecRate. Note that this is a prediction, often based on the general capability of a type of codec or particular encoding; the measured average rate may be significantly lower.
.1.3.6.1.2.1.51.1.2.1.15,RSVP-MIB::rsvpSenderTSpecPeakRate,INTEGER,read-create,,current,,The Peak Bit Rate of the sender's data stream. Traffic arrival is not expected to exceed this rate at any time, apart from the effects of jitter in the network. If not specified in the TSpec, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.16,RSVP-MIB::rsvpSenderTSpecBurst,INTEGER,read-create,,current,,The size of the largest burst expected from the sender at a time.
.1.3.6.1.2.1.51.1.2.1.17,RSVP-MIB::rsvpSenderTSpecMinTU,INTEGER,read-create,,current,,The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size.
.1.3.6.1.2.1.51.1.2.1.18,RSVP-MIB::rsvpSenderTSpecMaxTU,INTEGER,read-create,,current,,The maximum message size for this flow. The admission algorithm will reject TSpecs whose Maximum Transmission Unit, plus the interface headers, exceed the interface MTU.
.1.3.6.1.2.1.51.1.2.1.19,RSVP-MIB::rsvpSenderInterval,INTEGER,read-create,,current,,The interval between refresh messages as ad- vertised by the Previous Hop.
.1.3.6.1.2.1.51.1.2.1.20,RSVP-MIB::rsvpSenderRSVPHop,INTEGER,read-create,,current,true(1):false(2),If TRUE, the node believes that the previous IP hop is an RSVP hop. If FALSE, the node be- lieves that the previous IP hop may not be an RSVP hop.
.1.3.6.1.2.1.51.1.2.1.21,RSVP-MIB::rsvpSenderLastChange,TimeTicks,read-only,,current,,The time of the last change in this PATH mes- sage; This is either the first time it was re- ceived or the time of the most recent change in parameters.
.1.3.6.1.2.1.51.1.2.1.22,RSVP-MIB::rsvpSenderPolicy,OCTET,read-create,,current,,The contents of the policy object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length.
.1.3.6.1.2.1.51.1.2.1.23,RSVP-MIB::rsvpSenderAdspecBreak,INTEGER,read-create,,current,true(1):false(2),The global break bit general characterization parameter from the ADSPEC. If TRUE, at least one non-IS hop was detected in the path. If FALSE, no non-IS hops were detected.
.1.3.6.1.2.1.51.1.2.1.24,RSVP-MIB::rsvpSenderAdspecHopCount,INTEGER,read-create,,current,,The hop count general characterization parame- ter from the ADSPEC. A return of zero or noSuchValue indicates one of the following con- ditions: the invalid bit was set the parameter was not present
.1.3.6.1.2.1.51.1.2.1.25,RSVP-MIB::rsvpSenderAdspecPathBw,INTEGER,read-create,,current,,The path bandwidth estimate general character- ization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present
.1.3.6.1.2.1.51.1.2.1.26,RSVP-MIB::rsvpSenderAdspecMinLatency,Integer32,read-create,,current,,The minimum path latency general characteriza- tion parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present
.1.3.6.1.2.1.51.1.2.1.27,RSVP-MIB::rsvpSenderAdspecMtu,INTEGER,read-create,,current,,The composed Maximum Transmission Unit general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present
.1.3.6.1.2.1.51.1.2.1.28,RSVP-MIB::rsvpSenderAdspecGuaranteedSvc,INTEGER,read-create,,current,true(1):false(2),If TRUE, the ADSPEC contains a Guaranteed Ser- vice fragment. If FALSE, the ADSPEC does not contain a Guaranteed Service fragment.
.1.3.6.1.2.1.51.1.2.1.29,RSVP-MIB::rsvpSenderAdspecGuaranteedBreak,INTEGER,read-create,,current,true(1):false(2),If TRUE, the Guaranteed Service fragment has its 'break' bit set, indicating that one or more nodes along the path do not support the guaranteed service. If FALSE, and rsvpSen- derAdspecGuaranteedSvc is TRUE, the 'break' bit is not set. If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns FALSE or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.30,RSVP-MIB::rsvpSenderAdspecGuaranteedCtot,Integer32,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the end-to-end composed value for the guaranteed service 'C' parameter. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.31,RSVP-MIB::rsvpSenderAdspecGuaranteedDtot,Integer32,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the end-to-end composed value for the guaranteed service 'D' parameter. A return of zero or noSuchValue indicates one of the fol- lowing conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.32,RSVP-MIB::rsvpSenderAdspecGuaranteedCsum,Integer32,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the composed value for the guaranteed ser- vice 'C' parameter since the last reshaping point. A return of zero or noSuchValue indi- cates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.33,RSVP-MIB::rsvpSenderAdspecGuaranteedDsum,Integer32,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the composed value for the guaranteed ser- vice 'D' parameter since the last reshaping point. A return of zero or noSuchValue indi- cates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.34,RSVP-MIB::rsvpSenderAdspecGuaranteedHopCount,INTEGER,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the hop count general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.35,RSVP-MIB::rsvpSenderAdspecGuaranteedPathBw,INTEGER,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the path bandwidth estimate general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following con- ditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.36,RSVP-MIB::rsvpSenderAdspecGuaranteedMinLatency,Integer32,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the minimum path latency general characterization parameter from the ADSPEC. A return of zero or noSuch- Value indicates one of the following condi- tions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.37,RSVP-MIB::rsvpSenderAdspecGuaranteedMtu,INTEGER,read-create,,current,,If rsvpSenderAdspecGuaranteedSvc is TRUE, this is the service-specific override of the com- posed Maximum Transmission Unit general charac- terization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecGuaranteedSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.38,RSVP-MIB::rsvpSenderAdspecCtrlLoadSvc,INTEGER,read-create,,current,true(1):false(2),If TRUE, the ADSPEC contains a Controlled Load Service fragment. If FALSE, the ADSPEC does not contain a Controlled Load Service frag- ment.
.1.3.6.1.2.1.51.1.2.1.39,RSVP-MIB::rsvpSenderAdspecCtrlLoadBreak,INTEGER,read-create,,current,true(1):false(2),If TRUE, the Controlled Load Service fragment has its 'break' bit set, indicating that one or more nodes along the path do not support the controlled load service. If FALSE, and rsvpSenderAdspecCtrlLoadSvc is TRUE, the 'break' bit is not set. If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns FALSE or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.40,RSVP-MIB::rsvpSenderAdspecCtrlLoadHopCount,INTEGER,read-create,,current,,If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the hop count general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.41,RSVP-MIB::rsvpSenderAdspecCtrlLoadPathBw,INTEGER,read-create,,current,,If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the path bandwidth estimate general characterization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following con- ditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.42,RSVP-MIB::rsvpSenderAdspecCtrlLoadMinLatency,Integer32,read-create,,current,,If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the minimum path latency general characterization parameter from the ADSPEC. A return of zero or noSuch- Value indicates one of the following condi- tions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.43,RSVP-MIB::rsvpSenderAdspecCtrlLoadMtu,INTEGER,read-create,,current,,If rsvpSenderAdspecCtrlLoadSvc is TRUE, this is the service-specific override of the com- posed Maximum Transmission Unit general charac- terization parameter from the ADSPEC. A return of zero or noSuchValue indicates one of the following conditions: the invalid bit was set the parameter was not present If rsvpSenderAdspecCtrlLoadSvc is FALSE, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.2.1.44,RSVP-MIB::rsvpSenderStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' for all active PATH messages. This object may be used to install static PATH in- formation or delete PATH information.
.1.3.6.1.2.1.51.1.2.1.45,RSVP-MIB::rsvpSenderTTL,INTEGER,read-only,,current,,The TTL value in the RSVP header that was last received.
.1.3.6.1.2.1.51.1.3,RSVP-MIB::rsvpSenderOutInterfaceTable,,not-accessible,,current,,List of outgoing interfaces that PATH messages use. The ifIndex is the ifIndex value of the egress interface.
.1.3.6.1.2.1.51.1.3.1,RSVP-MIB::rsvpSenderOutInterfaceEntry,,not-accessible,rsvpSessionNumber:rsvpSenderNumber:ifIndex,current,,List of outgoing interfaces that a particular PATH message has.
.1.3.6.1.2.1.51.1.3.1.1,RSVP-MIB::rsvpSenderOutInterfaceStatus,INTEGER,read-only,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' for all active PATH messages.
.1.3.6.1.2.1.51.1.4,RSVP-MIB::rsvpResvTable,,not-accessible,,current,,Information describing the state information displayed by receivers in RESV messages.
.1.3.6.1.2.1.51.1.4.1,RSVP-MIB::rsvpResvEntry,,not-accessible,rsvpSessionNumber:rsvpResvNumber,current,,Information describing the state information displayed by a single receiver's RESV message concerning a single sender.
.1.3.6.1.2.1.51.1.4.1.1,RSVP-MIB::rsvpResvNumber,INTEGER,not-accessible,,current,,The number of this reservation request. This is for SNMP Indexing purposes only and has no relation to any protocol value.
.1.3.6.1.2.1.51.1.4.1.2,RSVP-MIB::rsvpResvType,INTEGER,read-create,,current,,The type of session (IP4, IP6, IP6 with flow information, etc).
.1.3.6.1.2.1.51.1.4.1.3,RSVP-MIB::rsvpResvDestAddr,OCTET,read-create,,current,,The destination address used by all senders in this session. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.51.1.4.1.4,RSVP-MIB::rsvpResvSenderAddr,OCTET,read-create,,current,,The source address of the sender selected by this reservation. The value of all zeroes in- dicates 'all senders'. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.4.1.5,RSVP-MIB::rsvpResvDestAddrLength,INTEGER,read-create,,current,,The length of the destination address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.4.1.6,RSVP-MIB::rsvpResvSenderAddrLength,INTEGER,read-create,,current,,The length of the sender's address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.4.1.7,RSVP-MIB::rsvpResvProtocol,INTEGER,read-create,,current,,The IP Protocol used by this session. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.4.1.8,RSVP-MIB::rsvpResvDestPort,OCTET,read-create,,current,,The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpResvProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.4.1.9,RSVP-MIB::rsvpResvPort,OCTET,read-create,,current,,The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpResvProto- col is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.51.1.4.1.10,RSVP-MIB::rsvpResvHopAddr,OCTET,read-create,,current,,The address used by the next RSVP hop (which may be the ultimate receiver).
.1.3.6.1.2.1.51.1.4.1.11,RSVP-MIB::rsvpResvHopLih,Integer32,read-create,,current,,The Logical Interface Handle received from the previous RSVP hop (which may be the ultimate receiver).
.1.3.6.1.2.1.51.1.4.1.12,RSVP-MIB::rsvpResvInterface,Integer32,read-create,,current,,The ifIndex value of the interface on which this RESV message was most recently received.
.1.3.6.1.2.1.51.1.4.1.13,RSVP-MIB::rsvpResvService,INTEGER,read-create,,current,bestEffort(1):guaranteedDelay(2):controlledLoad(5),The QoS Service classification requested by the receiver.
.1.3.6.1.2.1.51.1.4.1.14,RSVP-MIB::rsvpResvTSpecRate,INTEGER,read-create,,current,,The Average Bit Rate of the sender's data stream. Within a transmission burst, the ar- rival rate may be as fast as rsvpResvTSpec- PeakRate (if supported by the service model); however, averaged across two or more burst in- tervals, the rate should not exceed rsvpResvTSpecRate. Note that this is a prediction, often based on the general capability of a type of codec or particular encoding; the measured average rate may be significantly lower.
.1.3.6.1.2.1.51.1.4.1.15,RSVP-MIB::rsvpResvTSpecPeakRate,INTEGER,read-create,,current,,The Peak Bit Rate of the sender's data stream. Traffic arrival is not expected to exceed this rate at any time, apart from the effects of jitter in the network. If not specified in the TSpec, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.4.1.16,RSVP-MIB::rsvpResvTSpecBurst,INTEGER,read-create,,current,,The size of the largest burst expected from the sender at a time. If this is less than the sender's advertised burst size, the receiver is asking the network to provide flow pacing beyond what would be provided under normal circumstances. Such pac- ing is at the network's option.
.1.3.6.1.2.1.51.1.4.1.17,RSVP-MIB::rsvpResvTSpecMinTU,INTEGER,read-create,,current,,The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size.
.1.3.6.1.2.1.51.1.4.1.18,RSVP-MIB::rsvpResvTSpecMaxTU,INTEGER,read-create,,current,,The maximum message size for this flow. The admission algorithm will reject TSpecs whose Maximum Transmission Unit, plus the interface headers, exceed the interface MTU.
.1.3.6.1.2.1.51.1.4.1.19,RSVP-MIB::rsvpResvRSpecRate,INTEGER,read-create,,current,,If the requested service is Guaranteed, as specified by rsvpResvService, this is the clearing rate that is being requested. Other- wise, it is zero, or the agent may return noSuchValue.
.1.3.6.1.2.1.51.1.4.1.20,RSVP-MIB::rsvpResvRSpecSlack,Integer32,read-create,,current,,If the requested service is Guaranteed, as specified by rsvpResvService, this is the delay slack. Otherwise, it is zero, or the agent may return noSuchValue.
.1.3.6.1.2.1.51.1.4.1.21,RSVP-MIB::rsvpResvInterval,INTEGER,read-create,,current,,The interval between refresh messages as ad- vertised by the Next Hop.
.1.3.6.1.2.1.51.1.4.1.22,RSVP-MIB::rsvpResvScope,OCTET,read-create,,current,,The contents of the scope object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length. If the length is non-zero, this contains a series of IP4 or IP6 addresses.
.1.3.6.1.2.1.51.1.4.1.23,RSVP-MIB::rsvpResvShared,INTEGER,read-create,,current,true(1):false(2),If TRUE, a reservation shared among senders is requested. If FALSE, a reservation specific to this sender is requested.
.1.3.6.1.2.1.51.1.4.1.24,RSVP-MIB::rsvpResvExplicit,INTEGER,read-create,,current,true(1):false(2),If TRUE, individual senders are listed using Filter Specifications. If FALSE, all senders are implicitly selected. The Scope Object will contain a list of senders that need to receive this reservation request for the purpose of routing the RESV message.
.1.3.6.1.2.1.51.1.4.1.25,RSVP-MIB::rsvpResvRSVPHop,INTEGER,read-create,,current,true(1):false(2),If TRUE, the node believes that the previous IP hop is an RSVP hop. If FALSE, the node be- lieves that the previous IP hop may not be an RSVP hop.
.1.3.6.1.2.1.51.1.4.1.26,RSVP-MIB::rsvpResvLastChange,TimeTicks,read-only,,current,,The time of the last change in this reserva- tion request; This is either the first time it was received or the time of the most recent change in parameters.
.1.3.6.1.2.1.51.1.4.1.27,RSVP-MIB::rsvpResvPolicy,OCTET,read-create,,current,,The contents of the policy object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length.
.1.3.6.1.2.1.51.1.4.1.28,RSVP-MIB::rsvpResvStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' for all active RESV messages. This object may be used to install static RESV in- formation or delete RESV information.
.1.3.6.1.2.1.51.1.4.1.29,RSVP-MIB::rsvpResvTTL,INTEGER,read-only,,current,,The TTL value in the RSVP header that was last received.
.1.3.6.1.2.1.51.1.4.1.30,RSVP-MIB::rsvpResvFlowId,INTEGER,read-only,,current,,The flow ID that this receiver is using, if this is an IPv6 session.
.1.3.6.1.2.1.51.1.5,RSVP-MIB::rsvpResvFwdTable,,not-accessible,,current,,Information describing the state information displayed upstream in RESV messages.
.1.3.6.1.2.1.51.1.5.1,RSVP-MIB::rsvpResvFwdEntry,,not-accessible,rsvpSessionNumber:rsvpResvFwdNumber,current,,Information describing the state information displayed upstream in an RESV message concern- ing a single sender.
.1.3.6.1.2.1.51.1.5.1.1,RSVP-MIB::rsvpResvFwdNumber,INTEGER,not-accessible,,current,,The number of this reservation request. This is for SNMP Indexing purposes only and has no relation to any protocol value.
.1.3.6.1.2.1.51.1.5.1.2,RSVP-MIB::rsvpResvFwdType,INTEGER,read-only,,current,,The type of session (IP4, IP6, IP6 with flow information, etc).
.1.3.6.1.2.1.51.1.5.1.3,RSVP-MIB::rsvpResvFwdDestAddr,OCTET,read-only,,current,,The destination address used by all senders in this session. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.51.1.5.1.4,RSVP-MIB::rsvpResvFwdSenderAddr,OCTET,read-only,,current,,The source address of the sender selected by this reservation. The value of all zeroes in- dicates 'all senders'. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.5.1.5,RSVP-MIB::rsvpResvFwdDestAddrLength,INTEGER,read-only,,current,,The length of the destination address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.5.1.6,RSVP-MIB::rsvpResvFwdSenderAddrLength,INTEGER,read-only,,current,,The length of the sender's address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.5.1.7,RSVP-MIB::rsvpResvFwdProtocol,INTEGER,read-only,,current,,The IP Protocol used by a session. for secure sessions, this indicates IP Security. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.5.1.8,RSVP-MIB::rsvpResvFwdDestPort,OCTET,read-only,,current,,The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.5.1.9,RSVP-MIB::rsvpResvFwdPort,OCTET,read-only,,current,,The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.5.1.10,RSVP-MIB::rsvpResvFwdHopAddr,OCTET,read-only,,current,,The address of the (previous) RSVP that will receive this message.
.1.3.6.1.2.1.51.1.5.1.11,RSVP-MIB::rsvpResvFwdHopLih,Integer32,read-only,,current,,The Logical Interface Handle sent to the (pre- vious) RSVP that will receive this message.
.1.3.6.1.2.1.51.1.5.1.12,RSVP-MIB::rsvpResvFwdInterface,Integer32,read-only,,current,,The ifIndex value of the interface on which this RESV message was most recently sent.
.1.3.6.1.2.1.51.1.5.1.13,RSVP-MIB::rsvpResvFwdService,INTEGER,read-only,,current,bestEffort(1):guaranteedDelay(2):controlledLoad(5),The QoS Service classification requested.
.1.3.6.1.2.1.51.1.5.1.14,RSVP-MIB::rsvpResvFwdTSpecRate,INTEGER,read-only,,current,,The Average Bit Rate of the sender's data stream. Within a transmission burst, the ar- rival rate may be as fast as rsvpResvFwdTSpec- PeakRate (if supported by the service model); however, averaged across two or more burst in- tervals, the rate should not exceed rsvpResvFwdTSpecRate. Note that this is a prediction, often based on the general capability of a type of codec or particular encoding; the measured average rate may be significantly lower.
.1.3.6.1.2.1.51.1.5.1.15,RSVP-MIB::rsvpResvFwdTSpecPeakRate,INTEGER,read-only,,current,,The Peak Bit Rate of the sender's data stream Traffic arrival is not expected to exceed this rate at any time, apart from the effects of jitter in the network. If not specified in the TSpec, this returns zero or noSuchValue.
.1.3.6.1.2.1.51.1.5.1.16,RSVP-MIB::rsvpResvFwdTSpecBurst,INTEGER,read-only,,current,,The size of the largest burst expected from the sender at a time. If this is less than the sender's advertised burst size, the receiver is asking the network to provide flow pacing beyond what would be provided under normal circumstances. Such pac- ing is at the network's option.
.1.3.6.1.2.1.51.1.5.1.17,RSVP-MIB::rsvpResvFwdTSpecMinTU,INTEGER,read-only,,current,,The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size.
.1.3.6.1.2.1.51.1.5.1.18,RSVP-MIB::rsvpResvFwdTSpecMaxTU,INTEGER,read-only,,current,,The maximum message size for this flow. The admission algorithm will reject TSpecs whose Maximum Transmission Unit, plus the interface headers, exceed the interface MTU.
.1.3.6.1.2.1.51.1.5.1.19,RSVP-MIB::rsvpResvFwdRSpecRate,INTEGER,read-only,,current,,If the requested service is Guaranteed, as specified by rsvpResvService, this is the clearing rate that is being requested. Other- wise, it is zero, or the agent may return noSuchValue.
.1.3.6.1.2.1.51.1.5.1.20,RSVP-MIB::rsvpResvFwdRSpecSlack,Integer32,read-only,,current,,If the requested service is Guaranteed, as specified by rsvpResvService, this is the delay slack. Otherwise, it is zero, or the agent may return noSuchValue.
.1.3.6.1.2.1.51.1.5.1.21,RSVP-MIB::rsvpResvFwdInterval,INTEGER,read-only,,current,,The interval between refresh messages adver- tised to the Previous Hop.
.1.3.6.1.2.1.51.1.5.1.22,RSVP-MIB::rsvpResvFwdScope,OCTET,read-only,,current,,The contents of the scope object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length.
.1.3.6.1.2.1.51.1.5.1.23,RSVP-MIB::rsvpResvFwdShared,INTEGER,read-only,,current,true(1):false(2),If TRUE, a reservation shared among senders is requested. If FALSE, a reservation specific to this sender is requested.
.1.3.6.1.2.1.51.1.5.1.24,RSVP-MIB::rsvpResvFwdExplicit,INTEGER,read-only,,current,true(1):false(2),If TRUE, individual senders are listed using Filter Specifications. If FALSE, all senders are implicitly selected. The Scope Object will contain a list of senders that need to receive this reservation request for the purpose of routing the RESV message.
.1.3.6.1.2.1.51.1.5.1.25,RSVP-MIB::rsvpResvFwdRSVPHop,INTEGER,read-only,,current,true(1):false(2),If TRUE, the node believes that the next IP hop is an RSVP hop. If FALSE, the node be- lieves that the next IP hop may not be an RSVP hop.
.1.3.6.1.2.1.51.1.5.1.26,RSVP-MIB::rsvpResvFwdLastChange,TimeTicks,read-only,,current,,The time of the last change in this request; This is either the first time it was sent or the time of the most recent change in parame- ters.
.1.3.6.1.2.1.51.1.5.1.27,RSVP-MIB::rsvpResvFwdPolicy,OCTET,read-only,,current,,The contents of the policy object, displayed as an uninterpreted string of octets, including the object header. In the absence of such an object, this should be of zero length.
.1.3.6.1.2.1.51.1.5.1.28,RSVP-MIB::rsvpResvFwdStatus,INTEGER,read-write,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' for all active RESV messages. This object may be used to delete RESV information.
.1.3.6.1.2.1.51.1.5.1.29,RSVP-MIB::rsvpResvFwdTTL,INTEGER,read-only,,current,,The TTL value in the RSVP header that was last received.
.1.3.6.1.2.1.51.1.5.1.30,RSVP-MIB::rsvpResvFwdFlowId,INTEGER,read-only,,current,,The flow ID that this receiver is using, if this is an IPv6 session.
.1.3.6.1.2.1.51.1.6,RSVP-MIB::rsvpIfTable,,not-accessible,,current,,The RSVP-specific attributes of the system's interfaces.
.1.3.6.1.2.1.51.1.6.1,RSVP-MIB::rsvpIfEntry,,not-accessible,ifIndex,current,,The RSVP-specific attributes of the a given interface.
.1.3.6.1.2.1.51.1.6.1.1,RSVP-MIB::rsvpIfUdpNbrs,Gauge32,read-only,,current,,The number of neighbors perceived to be using only the RSVP UDP Encapsulation.
.1.3.6.1.2.1.51.1.6.1.2,RSVP-MIB::rsvpIfIpNbrs,Gauge32,read-only,,current,,The number of neighbors perceived to be using only the RSVP IP Encapsulation.
.1.3.6.1.2.1.51.1.6.1.3,RSVP-MIB::rsvpIfNbrs,Gauge32,read-only,,current,,The number of neighbors currently perceived; this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs by the number of neighbors using both encapsu- lations.
.1.3.6.1.2.1.51.1.6.1.4,RSVP-MIB::rsvpIfRefreshBlockadeMultiple,INTEGER,read-create,,current,,The value of the RSVP value 'Kb', Which is the minimum number of refresh intervals that blockade state will last once entered.
.1.3.6.1.2.1.51.1.6.1.5,RSVP-MIB::rsvpIfRefreshMultiple,INTEGER,read-create,,current,,The value of the RSVP value 'K', which is the number of refresh intervals which must elapse (minimum) before a PATH or RESV message which is not being refreshed will be aged out.
.1.3.6.1.2.1.51.1.6.1.6,RSVP-MIB::rsvpIfTTL,INTEGER,read-create,,current,,The value of SEND_TTL used on this interface for messages this node originates. If set to zero, the node determines the TTL via other means.
.1.3.6.1.2.1.51.1.6.1.7,RSVP-MIB::rsvpIfRefreshInterval,INTEGER,read-create,,current,,The value of the RSVP value 'R', which is the minimum period between refresh transmissions of a given PATH or RESV message on an interface.
.1.3.6.1.2.1.51.1.6.1.8,RSVP-MIB::rsvpIfRouteDelay,INTEGER,read-create,,current,,The approximate period from the time a route is changed to the time a resulting message ap- pears on the interface.
.1.3.6.1.2.1.51.1.6.1.9,RSVP-MIB::rsvpIfEnabled,INTEGER,read-create,,current,true(1):false(2),If TRUE, RSVP is enabled on this Interface. If FALSE, RSVP is not enabled on this inter- face.
.1.3.6.1.2.1.51.1.6.1.10,RSVP-MIB::rsvpIfUdpRequired,INTEGER,read-create,,current,true(1):false(2),If TRUE, manual configuration forces the use of UDP encapsulation on the interface. If FALSE, UDP encapsulation is only used if rsvpI- fUdpNbrs is not zero.
.1.3.6.1.2.1.51.1.6.1.11,RSVP-MIB::rsvpIfStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' on interfaces that are configured for RSVP.
.1.3.6.1.2.1.51.1.7,RSVP-MIB::rsvpNbrTable,,not-accessible,,current,,Information describing the Neighbors of an RSVP system.
.1.3.6.1.2.1.51.1.7.1,RSVP-MIB::rsvpNbrEntry,,not-accessible,ifIndex:rsvpNbrAddress,current,,Information describing a single RSVP Neigh- bor.
.1.3.6.1.2.1.51.1.7.1.1,RSVP-MIB::rsvpNbrAddress,OCTET,not-accessible,,current,,The IP4 or IP6 Address used by this neighbor. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.51.1.7.1.2,RSVP-MIB::rsvpNbrProtocol,INTEGER,read-create,,current,ip(1):udp(2):both(3),The encapsulation being used by this neigh- bor.
.1.3.6.1.2.1.51.1.7.1.3,RSVP-MIB::rsvpNbrStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' for all neighbors. This object may be used to configure neighbors. In the pres- ence of configured neighbors, the implementa- tion may (but is not required to) limit the set of valid neighbors to those configured.
.1.3.6.1.2.1.51.2,RSVP-MIB::rsvpGenObjects,,,,,,
.1.3.6.1.2.1.51.2.1,RSVP-MIB::rsvpBadPackets,Gauge32,read-only,,current,,This object keeps a count of the number of bad RSVP packets received.
.1.3.6.1.2.1.51.2.2,RSVP-MIB::rsvpSenderNewIndex,INTEGER,read-write,,current,,This object is used to assign values to rsvpSenderNumber as described in 'Textual Con- ventions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpSenderEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the ob- ject is incremented, and the new instance is created according to the manager's directions.
.1.3.6.1.2.1.51.2.3,RSVP-MIB::rsvpResvNewIndex,INTEGER,read-write,,current,,This object is used to assign values to rsvpResvNumber as described in 'Textual Conven- tions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpResvEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the object is incremented, and the new instance is created according to the manager's directions.
.1.3.6.1.2.1.51.2.4,RSVP-MIB::rsvpResvFwdNewIndex,INTEGER,read-write,,current,,This object is used to assign values to rsvpResvFwdNumber as described in 'Textual Con- ventions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of rsvpResvFwdEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the ob- ject is incremented, and the new instance is created according to the manager's directions.
.1.3.6.1.2.1.51.3,RSVP-MIB::rsvpNotificationsPrefix,,,,,,
.1.3.6.1.2.1.51.3.0,RSVP-MIB::rsvpNotifications,,,,,,
.1.3.6.1.2.1.51.3.0.1,RSVP-MIB::newFlow,,,,,,The newFlow trap indicates that the originat- ing system has installed a new flow in its classifier, or (when reservation authorization is in view) is prepared to install such a flow in the classifier and is requesting authoriza- tion. The objects included with the Notifica- tion may be used to read further information using the Integrated Services and RSVP MIBs. Authorization or non-authorization may be enacted by a write to the variable intSrvFlowS- tatus.
.1.3.6.1.2.1.51.3.0.2,RSVP-MIB::lostFlow,,,,,,The lostFlow trap indicates that the originat- ing system has removed a flow from its classif- ier.
.1.3.6.1.2.1.51.4,RSVP-MIB::rsvpConformance,,,,,,
.1.3.6.1.2.1.51.4.1,RSVP-MIB::rsvpGroups,,,,,,
.1.3.6.1.2.1.51.4.1.1,RSVP-MIB::rsvpSessionGroup,,,,,,These objects are required for RSVP Systems.
.1.3.6.1.2.1.51.4.1.2,RSVP-MIB::rsvpSenderGroup,,,,,,These objects are required for RSVP Systems.
.1.3.6.1.2.1.51.4.1.3,RSVP-MIB::rsvpResvGroup,,,,,,These objects are required for RSVP Systems.
.1.3.6.1.2.1.51.4.1.4,RSVP-MIB::rsvpResvFwdGroup,,,,,,These objects are optional, used for some RSVP Systems.
.1.3.6.1.2.1.51.4.1.6,RSVP-MIB::rsvpIfGroup,,,,,,These objects are required for RSVP Systems.
.1.3.6.1.2.1.51.4.1.7,RSVP-MIB::rsvpNbrGroup,,,,,,These objects are required for RSVP Systems.
.1.3.6.1.2.1.51.4.1.8,RSVP-MIB::rsvpNotificationGroup,,,,,,This notification is required for Systems sup- porting the RSVP Policy Module using an SNMP interface to the Policy Manager.
.1.3.6.1.2.1.51.4.2,RSVP-MIB::rsvpCompliances,,,,,,
.1.3.6.1.2.1.51.4.2.1,RSVP-MIB::rsvpCompliance,,,,,,The compliance statement. Note that the im- plementation of this module requires implemen- tation of the Integrated Services MIB as well.
.1.3.6.1.2.1.52,INTEGRATED-SERVICES-MIB::intSrv,,,,,,The MIB module to describe the Integrated Services Protocol
.1.3.6.1.2.1.52.1,INTEGRATED-SERVICES-MIB::intSrvObjects,,,,,,
.1.3.6.1.2.1.52.1.1,INTEGRATED-SERVICES-MIB::intSrvIfAttribTable,,not-accessible,,current,,The reservable attributes of the system's in- terfaces.
.1.3.6.1.2.1.52.1.1.1,INTEGRATED-SERVICES-MIB::intSrvIfAttribEntry,,not-accessible,ifIndex,current,,The reservable attributes of a given inter- face.
.1.3.6.1.2.1.52.1.1.1.1,INTEGRATED-SERVICES-MIB::intSrvIfAttribAllocatedBits,INTEGER,read-only,,current,,The number of bits/second currently allocated to reserved sessions on the interface.
.1.3.6.1.2.1.52.1.1.1.2,INTEGRATED-SERVICES-MIB::intSrvIfAttribMaxAllocatedBits,INTEGER,read-create,,current,,The maximum number of bits/second that may be allocated to reserved sessions on the inter- face.
.1.3.6.1.2.1.52.1.1.1.3,INTEGRATED-SERVICES-MIB::intSrvIfAttribAllocatedBuffer,INTEGER,read-only,,current,,The amount of buffer space required to hold the simultaneous burst of all reserved flows on the interface.
.1.3.6.1.2.1.52.1.1.1.4,INTEGRATED-SERVICES-MIB::intSrvIfAttribFlows,Gauge32,read-only,,current,,The number of reserved flows currently active on this interface. A flow can be created ei- ther from a reservation protocol (such as RSVP or ST-II) or via configuration information.
.1.3.6.1.2.1.52.1.1.1.5,INTEGRATED-SERVICES-MIB::intSrvIfAttribPropagationDelay,Integer32,read-create,,current,,The amount of propagation delay that this in- terface introduces in addition to that intro- diced by bit propagation delays.
.1.3.6.1.2.1.52.1.1.1.6,INTEGRATED-SERVICES-MIB::intSrvIfAttribStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' on interfaces that are configured for RSVP.
.1.3.6.1.2.1.52.1.2,INTEGRATED-SERVICES-MIB::intSrvFlowTable,,not-accessible,,current,,Information describing the reserved flows us- ing the system's interfaces.
.1.3.6.1.2.1.52.1.2.1,INTEGRATED-SERVICES-MIB::intSrvFlowEntry,,not-accessible,intSrvFlowNumber,current,,Information describing the use of a given in- terface by a given flow. The counter intSrvFlowPoliced starts counting at the in- stallation of the flow.
.1.3.6.1.2.1.52.1.2.1.1,INTEGRATED-SERVICES-MIB::intSrvFlowNumber,INTEGER,not-accessible,,current,,The number of this flow. This is for SNMP In- dexing purposes only and has no relation to any protocol value.
.1.3.6.1.2.1.52.1.2.1.2,INTEGRATED-SERVICES-MIB::intSrvFlowType,INTEGER,read-create,,current,,The type of session (IP4, IP6, IP6 with flow information, etc).
.1.3.6.1.2.1.52.1.2.1.3,INTEGRATED-SERVICES-MIB::intSrvFlowOwner,INTEGER,read-create,,current,other(1):rsvp(2):management(3),The process that installed this flow in the queue policy database.
.1.3.6.1.2.1.52.1.2.1.4,INTEGRATED-SERVICES-MIB::intSrvFlowDestAddr,OCTET,read-create,,current,,The destination address used by all senders in this session. This object may not be changed when the value of the RowStatus object is 'ac- tive'.
.1.3.6.1.2.1.52.1.2.1.5,INTEGRATED-SERVICES-MIB::intSrvFlowSenderAddr,OCTET,read-create,,current,,The source address of the sender selected by this reservation. The value of all zeroes in- dicates 'all senders'. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.52.1.2.1.6,INTEGRATED-SERVICES-MIB::intSrvFlowDestAddrLength,INTEGER,read-create,,current,,The length of the destination address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.52.1.2.1.7,INTEGRATED-SERVICES-MIB::intSrvFlowSenderAddrLength,INTEGER,read-create,,current,,The length of the sender's address in bits. This is the CIDR Prefix Length, which for IP4 hosts and multicast addresses is 32 bits. This object may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.52.1.2.1.8,INTEGRATED-SERVICES-MIB::intSrvFlowProtocol,INTEGER,read-create,,current,,The IP Protocol used by a session. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.52.1.2.1.9,INTEGRATED-SERVICES-MIB::intSrvFlowDestPort,OCTET,read-create,,current,,The UDP or TCP port number used as a destina- tion port for all senders in this session. If the IP protocol in use, specified by intSrvResvFwdProtocol, is 50 (ESP) or 51 (AH), this represents a virtual destination port number. A value of zero indicates that the IP protocol in use does not have ports. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.52.1.2.1.10,INTEGRATED-SERVICES-MIB::intSrvFlowPort,OCTET,read-create,,current,,The UDP or TCP port number used as a source port for this sender in this session. If the IP protocol in use, specified by intSrvResvFwdProtocol is 50 (ESP) or 51 (AH), this represents a generalized port identifier (GPI). A value of zero indicates that the IP protocol in use does not have ports. This ob- ject may not be changed when the value of the RowStatus object is 'active'.
.1.3.6.1.2.1.52.1.2.1.11,INTEGRATED-SERVICES-MIB::intSrvFlowFlowId,INTEGER,read-only,,current,,The flow ID that this sender is using, if this is an IPv6 session.
.1.3.6.1.2.1.52.1.2.1.12,INTEGRATED-SERVICES-MIB::intSrvFlowInterface,Integer32,read-create,,current,,The ifIndex value of the interface on which this reservation exists.
.1.3.6.1.2.1.52.1.2.1.13,INTEGRATED-SERVICES-MIB::intSrvFlowIfAddr,OCTET,read-create,,current,,The IP Address on the ifEntry on which this reservation exists. This is present primarily to support those interfaces which layer multi- ple IP Addresses on the interface.
.1.3.6.1.2.1.52.1.2.1.14,INTEGRATED-SERVICES-MIB::intSrvFlowRate,INTEGER,read-create,,current,,The Reserved Rate of the sender's data stream. If this is a Controlled Load service flow, this rate is derived from the Tspec rate parameter (r). If this is a Guaranteed service flow, this rate is derived from the Rspec clearing rate parameter (R).
.1.3.6.1.2.1.52.1.2.1.15,INTEGRATED-SERVICES-MIB::intSrvFlowBurst,INTEGER,read-create,,current,,The size of the largest burst expected from the sender at a time. If this is less than the sender's advertised burst size, the receiver is asking the network to provide flow pacing beyond what would be provided under normal circumstances. Such pac- ing is at the network's option.
.1.3.6.1.2.1.52.1.2.1.16,INTEGRATED-SERVICES-MIB::intSrvFlowWeight,Integer32,read-create,,current,,The weight used to prioritize the traffic. Note that the interpretation of this object is implementation-specific, as implementations vary in their use of weighting procedures.
.1.3.6.1.2.1.52.1.2.1.17,INTEGRATED-SERVICES-MIB::intSrvFlowQueue,Integer32,read-create,,current,,The number of the queue used by this traffic. Note that the interpretation of this object is implementation-specific, as implementations vary in their use of queue identifiers.
.1.3.6.1.2.1.52.1.2.1.18,INTEGRATED-SERVICES-MIB::intSrvFlowMinTU,INTEGER,read-create,,current,,The minimum message size for this flow. The policing algorithm will treat smaller messages as though they are this size.
.1.3.6.1.2.1.52.1.2.1.19,INTEGRATED-SERVICES-MIB::intSrvFlowMaxTU,INTEGER,read-create,,current,,The maximum datagram size for this flow that will conform to the traffic specification. This value cannot exceed the MTU of the interface.
.1.3.6.1.2.1.52.1.2.1.20,INTEGRATED-SERVICES-MIB::intSrvFlowBestEffort,Counter32,read-only,,current,,The number of packets that were remanded to best effort service.
.1.3.6.1.2.1.52.1.2.1.21,INTEGRATED-SERVICES-MIB::intSrvFlowPoliced,Counter32,read-only,,current,,The number of packets policed since the incep- tion of the flow's service.
.1.3.6.1.2.1.52.1.2.1.22,INTEGRATED-SERVICES-MIB::intSrvFlowDiscard,INTEGER,read-create,,current,true(1):false(2),If 'true', the flow is to incur loss when traffic is policed. If 'false', policed traff- ic is treated as best effort traffic.
.1.3.6.1.2.1.52.1.2.1.23,INTEGRATED-SERVICES-MIB::intSrvFlowService,INTEGER,read-only,,current,bestEffort(1):guaranteedDelay(2):controlledLoad(5),The QoS service being applied to this flow.
.1.3.6.1.2.1.52.1.2.1.24,INTEGRATED-SERVICES-MIB::intSrvFlowOrder,INTEGER,read-create,,current,,In the event of ambiguity, the order in which the classifier should make its comparisons. The row with intSrvFlowOrder=0 is tried first, and comparisons proceed in the order of in- creasing value. Non-serial implementations of the classifier should emulate this behavior.
.1.3.6.1.2.1.52.1.2.1.25,INTEGRATED-SERVICES-MIB::intSrvFlowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'active' for all active flows. This object may be used to install static classifier infor- mation, delete classifier information, or au- thorize such.
.1.3.6.1.2.1.52.2,INTEGRATED-SERVICES-MIB::intSrvGenObjects,,,,,,
.1.3.6.1.2.1.52.2.1,INTEGRATED-SERVICES-MIB::intSrvFlowNewIndex,,read-write,,current,,This object is used to assign values to intSrvFlowNumber as described in 'Textual Con- ventions for SNMPv2'. The network manager reads the object, and then writes the value back in the SET that creates a new instance of intSrvFlowEntry. If the SET fails with the code 'inconsistentValue', then the process must be repeated; If the SET succeeds, then the ob- ject is incremented, and the new instance is created according to the manager's directions.
.1.3.6.1.2.1.52.3,INTEGRATED-SERVICES-MIB::intSrvNotifications,,,,,,
.1.3.6.1.2.1.52.4,INTEGRATED-SERVICES-MIB::intSrvConformance,,,,,,
.1.3.6.1.2.1.52.4.1,INTEGRATED-SERVICES-MIB::intSrvGroups,,,,,,
.1.3.6.1.2.1.52.4.1.1,INTEGRATED-SERVICES-MIB::intSrvIfAttribGroup,,,,,,These objects are required for Systems sup- porting the Integrated Services Architecture.
.1.3.6.1.2.1.52.4.1.1.1,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedIfEntry,,not-accessible,ifIndex,current,,The reservable attributes of a given inter- face.
.1.3.6.1.2.1.52.4.1.1.1.1,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedIfC,INTEGER,read-create,,current,,The parameter C is the data backlog resulting from the vagaries of how a specific implementa- tion deviates from a strict bit-by-bit service. So, for instance, for packetized weighted fair queueing, C is set to the Maximum Packet Size. The error term C is measured in units of bytes. An individual element can advertise a C value between 1 and 2**28 (a little over 250 mega- bytes) and the total added over all elements can range as high as (2**32)-1. Should the sum of the different elements delay exceed (2**32)-1, the end-to-end error term should be (2**32)-1.
.1.3.6.1.2.1.52.4.1.1.1.2,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedIfD,INTEGER,read-create,,current,,The parameter D at each service element should be set to the maximum packet transfer delay (independent of bucket size) through the ser- vice element. For instance, in a simple router, one might compute the worst case amount of time it make take for a datagram to get through the input interface to the processor, and how long it would take to get from the pro- cessor to the outbound interface (assuming the queueing schemes work correctly). For an Eth- ernet, it might represent the worst case delay if the maximum number of collisions is experi- enced. The error term D is measured in units of one microsecond. An individual element can adver- tise a delay value between 1 and 2**28 (some- what over two minutes) and the total delay ad- ded all elements can range as high as (2**32)- 1. Should the sum of the different elements delay exceed (2**32)-1, the end-to-end delay should be (2**32)-1.
.1.3.6.1.2.1.52.4.1.1.1.3,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedIfSlack,INTEGER,read-create,,current,,If a network element uses a certain amount of slack, Si, to reduce the amount of resources that it has reserved for a particular flow, i, the value Si should be stored at the network element. Subsequently, if reservation re- freshes are received for flow i, the network element must use the same slack Si without any further computation. This guarantees consisten- cy in the reservation process. As an example for the use of the slack term, consider the case where the required end-to-end delay, Dreq, is larger than the maximum delay of the fluid flow system. The latter is ob- tained by setting R=r in the fluid delay formu- la, and is given by b/r + Ctot/r + Dtot. In this case the slack term is S = Dreq - (b/r + Ctot/r + Dtot). The slack term may be used by the network ele- ments to adjust their local reservations, so that they can admit flows that would otherwise have been rejected. A service element at an in- termediate network element that can internally differentiate between delay and rate guarantees can now take advantage of this information to lower the amount of resources allocated to this flow. For example, by taking an amount of slack s <= S, an RCSD scheduler [5] can increase the local delay bound, d, assigned to the flow, to d+s. Given an RSpec, (Rin, Sin), it would do so by setting Rout = Rin and Sout = Sin - s. Similarly, a network element using a WFQ scheduler can decrease its local reservation from Rin to Rout by using some of the slack in the RSpec. This can be accomplished by using the transformation rules given in the previous section, that ensure that the reduced reserva- tion level will not increase the overall end- to-end delay.
.1.3.6.1.2.1.52.4.1.1.1.4,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedIfStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'valid' on interfaces that are configured for the Guaranteed Service.
.1.3.6.1.2.1.52.4.1.2,INTEGRATED-SERVICES-MIB::intSrvFlowsGroup,,,,,,These objects are required for Systems sup- porting the Integrated Services Architecture.
.1.3.6.1.2.1.52.4.1.3,INT-SERV-MIB::intSrvGenObjectsGroup,,,,,,These objects are required for Systems sup- porting the Integrated Services Architecture.
.1.3.6.1.2.1.52.4.2,INTEGRATED-SERVICES-MIB::intSrvCompliances,,,,,,
.1.3.6.1.2.1.52.4.2.1,INTEGRATED-SERVICES-MIB::intSrvCompliance,,,,,,The compliance statement 
.1.3.6.1.2.1.52.4.3,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedConformance,,,,,,
.1.3.6.1.2.1.52.4.3.1,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedGroups,,,,,,
.1.3.6.1.2.1.52.4.3.1.2,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedIfAttribGroup,,,,,,These objects are required for Systems sup- porting the Guaranteed Service of the Integrat- ed Services Architecture.
.1.3.6.1.2.1.52.4.3.2,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedCompliances,,,,,,
.1.3.6.1.2.1.52.4.3.2.1,INT-SERV-GUARANTEED-MIB::intSrvGuaranteedCompliance,,,,,,The compliance statement 
.1.3.6.1.2.1.52.5,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteed,,,,,,The MIB module to describe the Guaranteed Service of the Integrated Services Protocol
.1.3.6.1.2.1.52.5.1,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedObjects,,,,,,
.1.3.6.1.2.1.52.5.1.1,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfTable,,not-accessible,,current,,The attributes of the system's interfaces ex- ported by the Guaranteed Service.
.1.3.6.1.2.1.52.5.1.1.1,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfEntry,,not-accessible,ifIndex,current,,The reservable attributes of a given inter- face.
.1.3.6.1.2.1.52.5.1.1.1.1,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfBacklog,INTEGER,read-create,,current,,The Backlog parameter is the data backlog resulting from the vagaries of how a specific implementation deviates from a strict bit-by- bit service. So, for instance, for packetized weighted fair queueing, Backlog is set to the Maximum Packet Size. The Backlog term is measured in units of bytes. An individual element can advertise a Backlog value between 1 and 2**28 (a little over 250 megabytes) and the total added over all ele- ments can range as high as (2**32)-1. Should the sum of the different elements delay exceed (2**32)-1, the end-to-end error term should be (2**32)-1.
.1.3.6.1.2.1.52.5.1.1.1.2,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfDelay,INTEGER,read-create,,current,,The Delay parameter at each service element should be set to the maximum packet transfer delay (independent of bucket size) through the service element. For instance, in a simple router, one might compute the worst case amount of time it make take for a datagram to get through the input interface to the processor, and how long it would take to get from the pro- cessor to the outbound interface (assuming the queueing schemes work correctly). For an Eth- ernet, it might represent the worst case delay if the maximum number of collisions is experi- enced. The Delay term is measured in units of one mi- crosecond. An individual element can advertise a delay value between 1 and 2**28 (somewhat over two minutes) and the total delay added all elements can range as high as (2**32)-1. Should the sum of the different elements delay exceed (2**32)-1, the end-to-end delay should be (2**32)-1.
.1.3.6.1.2.1.52.5.1.1.1.3,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfSlack,INTEGER,read-create,,current,,If a network element uses a certain amount of slack, Si, to reduce the amount of resources that it has reserved for a particular flow, i, the value Si should be stored at the network element. Subsequently, if reservation re- freshes are received for flow i, the network element must use the same slack Si without any further computation. This guarantees consisten- cy in the reservation process. As an example for the use of the slack term, consider the case where the required end-to-end delay, Dreq, is larger than the maximum delay of the fluid flow system. In this, Ctot is the sum of the Backlog terms end to end, and Dtot is the sum of the delay terms end to end. Dreq is obtained by setting R=r in the fluid delay formula, and is given by b/r + Ctot/r + Dtot. In this case the slack term is S = Dreq - (b/r + Ctot/r + Dtot). The slack term may be used by the network ele- ments to adjust their local reservations, so that they can admit flows that would otherwise have been rejected. A service element at an in- termediate network element that can internally differentiate between delay and rate guarantees can now take advantage of this information to lower the amount of resources allocated to this flow. For example, by taking an amount of slack s <= S, an RCSD scheduler [5] can increase the local delay bound, d, assigned to the flow, to d+s. Given an RSpec, (Rin, Sin), it would do so by setting Rout = Rin and Sout = Sin - s. Similarly, a network element using a WFQ scheduler can decrease its local reservation from Rin to Rout by using some of the slack in the RSpec. This can be accomplished by using the transformation rules given in the previous section, that ensure that the reduced reserva- tion level will not increase the overall end- to-end delay.
.1.3.6.1.2.1.52.5.1.1.1.4,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),'valid' on interfaces that are configured for the Guaranteed Service.
.1.3.6.1.2.1.52.5.2,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedNotifications,,,,,,
.1.3.6.1.2.1.52.5.3,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedConformance,,,,,,
.1.3.6.1.2.1.52.5.3.1,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedGroups,,,,,,
.1.3.6.1.2.1.52.5.3.1.2,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedIfAttribGroup,,,,,,These objects are required for Systems sup- porting the Guaranteed Service of the Integrat- ed Services Architecture.
.1.3.6.1.2.1.52.5.3.2,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedCompliances,,,,,,
.1.3.6.1.2.1.52.5.3.2.1,INTEGRATED-SERVICES-GUARANTEED-MIB::intSrvGuaranteedCompliance,,,,,,The compliance statement 
.1.3.6.1.2.1.53,DOT12-RPTR-MIB::vgRptrMIB,,,,,,This MIB module describes objects for managing IEEE 802.12 repeaters.
.1.3.6.1.2.1.53.1,DOT12-RPTR-MIB::vgRptrObjects,,,,,,
.1.3.6.1.2.1.53.1.1,DOT12-RPTR-MIB::vgRptrBasic,,,,,,
.1.3.6.1.2.1.53.1.1.1,DOT12-RPTR-MIB::vgRptrBasicRptr,,,,,,
.1.3.6.1.2.1.53.1.1.1.1,DOT12-RPTR-MIB::vgRptrInfoTable,,not-accessible,,current,,A table of information about each 802.12 repeater in the managed system.
.1.3.6.1.2.1.53.1.1.1.1.1,DOT12-RPTR-MIB::vgRptrInfoEntry,,not-accessible,vgRptrInfoIndex,current,,An entry in the table, containing information about a single repeater.
.1.3.6.1.2.1.53.1.1.1.1.1.1,DOT12-RPTR-MIB::vgRptrInfoIndex,Integer32,not-accessible,,current,,A unique identifier for the repeater for which this entry contains information. The numbering scheme for repeaters is implementation specific.
.1.3.6.1.2.1.53.1.1.1.1.1.2,DOT12-RPTR-MIB::vgRptrInfoMACAddress,OCTET,read-only,,current,,The MAC address used by the repeater when it initiates training on the uplink port. Repeaters are allowed to train with an assigned MAC address or a null (all zeroes) MAC address.
.1.3.6.1.2.1.53.1.1.1.1.1.3,DOT12-RPTR-MIB::vgRptrInfoCurrentFramingType,INTEGER,read-only,,current,frameType88023(1):frameType88025(2),The type of framing (802.3 or 802.5) currently in use by the repeater.
.1.3.6.1.2.1.53.1.1.1.1.1.4,DOT12-RPTR-MIB::vgRptrInfoDesiredFramingType,INTEGER,read-write,,current,frameType88023(1):frameType88025(2),The type of framing which will be used by the repeater after the next time it is reset. The value of this object should be preserved across repeater resets and power failures.
.1.3.6.1.2.1.53.1.1.1.1.1.5,DOT12-RPTR-MIB::vgRptrInfoFramingCapability,INTEGER,read-only,,current,frameType88023(1):frameType88025(2):frameTypeEither(3),The type of framing this repeater is capable of supporting.
.1.3.6.1.2.1.53.1.1.1.1.1.6,DOT12-RPTR-MIB::vgRptrInfoTrainingVersion,INTEGER,read-only,,current,,The highest version bits (vvv bits) supported by the repeater during training.
.1.3.6.1.2.1.53.1.1.1.1.1.7,DOT12-RPTR-MIB::vgRptrInfoOperStatus,INTEGER,read-only,,current,other(1):ok(2):generalFailure(3),The vgRptrInfoOperStatus object indicates the operational state of the repeater.
.1.3.6.1.2.1.53.1.1.1.1.1.8,DOT12-RPTR-MIB::vgRptrInfoReset,INTEGER,read-write,,current,noReset(1):reset(2),Setting this object to reset(2) causes the repeater to transition to its initial state as specified in clause 12 [IEEE Std 802.12]. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. After receiving a request to set this variable to reset(2), the agent is allowed to delay the reset for a short period. For example, the implementor may choose to delay the reset long enough to allow the SNMP response to be transmitted. In any event, the SNMP response must be transmitted. This action does not reset the management counters defined in this document nor does it affect the vgRptrPortAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: 1) The nature of the tests is not specified. 2) The test resets the repeater but without affecting configurable management information about the repeater. 3) Packets received during the test may or may not be transferred. 4) The test does not interfere with management functions. After performing this self-test, the agent will update the repeater health information (including vgRptrInfoOperStatus), and send a vgRptrResetEvent.
.1.3.6.1.2.1.53.1.1.1.1.1.9,DOT12-RPTR-MIB::vgRptrInfoLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when any of the following conditions occurred: 1) agent cold- or warm-started; 2) this instance of repeater was created (such as when a device or module was added to the system); 3) a change in the value of vgRptrInfoOperStatus; 4) ports were added or removed as members of the repeater; or 5) any of the counters associated with this repeater had a discontinuity.
.1.3.6.1.2.1.53.1.1.2,DOT12-RPTR-MIB::vgRptrBasicGroup,,,,,,
.1.3.6.1.2.1.53.1.1.2.1,DOT12-RPTR-MIB::vgRptrBasicGroupTable,,not-accessible,,current,,A table containing information about groups of ports.
.1.3.6.1.2.1.53.1.1.2.1.1,DOT12-RPTR-MIB::vgRptrBasicGroupEntry,,not-accessible,vgRptrGroupIndex,current,,An entry in the vgRptrBasicGroupTable, containing information about a single group of ports.
.1.3.6.1.2.1.53.1.1.2.1.1.1,DOT12-RPTR-MIB::vgRptrGroupIndex,Integer32,not-accessible,,current,,This object identifies the group within the system for which this entry contains information. The numbering scheme for groups is implementation specific.
.1.3.6.1.2.1.53.1.1.2.1.1.2,DOT12-RPTR-MIB::vgRptrGroupObjectID,OBJECT,read-only,,current,,The vendor's authoritative identification of the group. This value may be allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of group is being managed. For example, this object could take the value 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, and had assigned the identifier 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 6-Port Plug-in Module.'
.1.3.6.1.2.1.53.1.1.2.1.1.3,DOT12-RPTR-MIB::vgRptrGroupOperStatus,INTEGER,read-only,,current,other(1):operational(2):malfunctioning(3):notPresent(4):underTest(5):resetInProgress(6),An object that indicates the operational status of the group. A status of notPresent(4) indicates that the group is temporarily or permanently physically and/or logically not a part of the system. It is an implementation-specific matter as to whether the agent effectively removes notPresent entries from the table. A status of operational(2) indicates that the group is functioning, and a status of malfunctioning(3) indicates that the group is malfunctioning in some way.
.1.3.6.1.2.1.53.1.1.2.1.1.4,DOT12-RPTR-MIB::vgRptrGroupPortCapacity,Integer32,read-only,,current,,The vgRptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-2147483647. Within each group, the ports are uniquely numbered in the range from 1 to vgRptrGroupPortCapacity. Some ports may not be present in the system, in which case the actual number of ports present will be less than the value of vgRptrGroupPortCapacity. The number of ports present is never greater than the value of vgRptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.
.1.3.6.1.2.1.53.1.1.2.1.1.5,DOT12-RPTR-MIB::vgRptrGroupCablesBundled,INTEGER,read-write,,current,someCablesBundled(1):noCablesBundled(2),This object is used to indicate whether there are any four-pair UTP links connected to this group that are contained in a cable bundle with multiple four-pair groups (e.g. a 25-pair bundle). Bundled cable may only be used for repeater-to-end node links where the end node is not in promiscuous mode. When a broadcast or multicast packet is received from a port on this group that is not a promiscuous or cascaded port, the packet will be buffered completely before being repeated if this object is set to 'someCablesBundled(1)'. When this object is equal to 'noCablesBundled(2)', all packets received from ports on this group will be repeated as the frame is being received. Note that the value 'someCablesBundled(1)' will work in the vast majority of all installations, regardless of whether or not any cables are physically in a bundle, since packets received from promiscuous and cascaded ports automatically avoid the store and forward. The main situation in which 'noCablesBundled(2)' is beneficial is when there is a large amount of multicast traffic and the cables are not in a bundle. The value of this object should be preserved across repeater resets and power failures.
.1.3.6.1.2.1.53.1.1.3,DOT12-RPTR-MIB::vgRptrBasicPort,,,,,,
.1.3.6.1.2.1.53.1.1.3.1,DOT12-RPTR-MIB::vgRptrBasicPortTable,,not-accessible,,current,,A table containing configuration and status information about 802.12 repeater ports in the system. The number of entries is independent of the number of repeaters in the managed system.
.1.3.6.1.2.1.53.1.1.3.1.1,DOT12-RPTR-MIB::vgRptrBasicPortEntry,,not-accessible,vgRptrGroupIndex:vgRptrPortIndex,current,,An entry in the vgRptrBasicPortTable, containing information about a single port.
.1.3.6.1.2.1.53.1.1.3.1.1.1,DOT12-RPTR-MIB::vgRptrPortIndex,Integer32,not-accessible,,current,,This object identifies the port within the group for which this entry contains information. This identifies the port independently from the repeater it may be attached to. The numbering scheme for ports is implementation specific; however, this value can never be greater than vgRptrGroupPortCapacity for the associated group.
.1.3.6.1.2.1.53.1.1.3.1.1.2,DOT12-RPTR-MIB::vgRptrPortType,INTEGER,read-only,,current,cascadeExternal(1):cascadeInternal(2):localExternal(3):localInternal(4),Describes the type of port. One of the following: cascadeExternal - Port is an uplink with physical connections which are externally visible cascadeInternal - Port is an uplink with physical connections which are not externally visible, such as a connection to an internal backplane in a chassis localExternal - Port is a downlink or local port with externally visible connections localInternal - Port is a downlink or local port with connections which are not externally visible, such as a connection to an internal agent 'internal' is used to identify ports which place traffic into the repeater, but do not have any external connections. Note that both DTE and cascaded repeater downlinks are considered 'local' ports.
.1.3.6.1.2.1.53.1.1.3.1.1.3,DOT12-RPTR-MIB::vgRptrPortAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),Port enable/disable function. Enabling a disabled port will cause training to be initiated by the training initiator (the slave mode device) on the link. Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The value of this object should be preserved across repeater resets and power failures.
.1.3.6.1.2.1.53.1.1.3.1.1.4,DOT12-RPTR-MIB::vgRptrPortOperStatus,INTEGER,read-only,,current,active(1):inactive(2):training(3),Current status for the port as specified by the PORT_META_STATE in the port process module of clause 12 [IEEE Std 802.12]. During initialization or any link warning conditions, vgRptrPortStatus will be 'inactive(2)'. When Training_Up is received by the repeater on a local port (or when Training_Down is received on a cascade port), vgRptrPortStatus will change to 'training(3)' and vgRptrTrainingResult can be monitored to see the detailed status regarding training. When 24 consecutive good FCS packets are exchanged and the configuration bits are OK, vgRptrPortStatus will change to 'active(1)'. A disabled port shall have a port status of 'inactive(2)'.
.1.3.6.1.2.1.53.1.1.3.1.1.5,DOT12-RPTR-MIB::vgRptrPortSupportedPromiscMode,INTEGER,read-only,,current,singleModeOnly(1):singleOrPromiscMode(2):promiscModeOnly(3),This object describes whether the port hardware is capable of supporting promiscuous mode, single address mode (i.e., repeater filters unicasts not addressed to the end station attached to this port), or both. A port for which vgRptrPortType is equal to 'cascadeInternal' or 'cascadeExternal' will always have a value of 'promiscModeOnly' for this object.
.1.3.6.1.2.1.53.1.1.3.1.1.6,DOT12-RPTR-MIB::vgRptrPortSupportedCascadeMode,INTEGER,read-only,,current,endNodesOnly(1):endNodesOrRepeaters(2):cascadePort(3),This object describes whether the port hardware is capable of supporting cascaded repeaters, end nodes, or both. A port for which vgRptrPortType is equal to 'cascadeInternal' or 'cascadeExternal' will always have a value of 'cascadePort' for this object.
.1.3.6.1.2.1.53.1.1.3.1.1.7,DOT12-RPTR-MIB::vgRptrPortAllowedTrainType,INTEGER,read-write,,current,allowEndNodesOnly(1):allowPromiscuousEndNodes(2):allowEndNodesOrRepeaters(3):allowAnything(4),This security object is set by the network manager to configure what type of device is permitted to connect to the port. One of the following values: allowEndNodesOnly - only non- promiscuous end nodes permitted. allowPromiscuousEndNodes - promiscuous or non-promiscuous end nodes permitted allowEndNodesOrRepeaters - repeaters or non- promiscuous end nodes permitted allowAnything - repeaters, promiscuous or non-promiscuous end nodes permitted For a port for which vgRptrPortType is equal to 'cascadeInternal' or 'cascadeExternal', the corresponding instance of this object may not be set to 'allowEndNodesOnly' or 'allowPromiscuousEndNodes'. The agent must reject a SET of this object if the value includes no capabilities that are supported by this port's hardware, as defined by the values of the corresponding instances of vgRptrPortSupportedPromiscMode and vgRptrPortSupportedCascadeMode. Note that vgRptrPortSupportPromiscMode and vgRptrPortSupportedCascadeMode represent what the port hardware is capable of supporting. vgRptrPortAllowedTrainType is used for setting an administrative policy for a port. The actual set of training configurations that will be allowed to succeed on a port is the intersection of what the hardware will support and what is administratively allowed. The above requirement on what values may be set to this object says that the intersection of what is supported and what is allowed must be non-empty. In other words, it must not result in a situation in which nothing would be allowed to train on that port. However, a value can be set to this object as long as the combination of this object and what is supported by the hardware would still leave at least one configuration that could successfully train on the port. The value of this object should be preserved across repeater resets and power failures.
.1.3.6.1.2.1.53.1.1.3.1.1.8,DOT12-RPTR-MIB::vgRptrPortLastTrainConfig,OCTET,read-only,,current,,This object is a 16 bit field. For local ports, this object contains the requested configuration field from the most recent error-free training request frame sent by the device connected to the port. For cascade ports, this object contains the responder's allowed configuration field from the most recent error-free training response frame received in response to training initiated by this repeater. The format of the current version of this field is described in section 3.2. Please refer to the most recent version of the IEEE 802.12 standard for the most up-to-date definition of the format of this object.
.1.3.6.1.2.1.53.1.1.3.1.1.9,DOT12-RPTR-MIB::vgRptrPortTrainingResult,OCTET,read-only,,current,,This 18 bit field is used to indicate the result of training. It contains two bits which indicate if error-free training frames have been received, and it also contains the 16 bits of the allowed configuration field from the most recent error-free training response frame on the port. First Octet: Second and Third Octets: 7 6 5 4 3 2 1 0 +-+-+-+-+-+-+-+-+-----------------------------+ |0|0|0|0|0|0|V|G| allowed configuration field | +-+-+-+-+-+-+-+-+-----------------------------+ V: Valid: set when at least one error-free training frame has been received. Indicates the 16 training configuration bits in vgRptrPortLastTrainConfig and vgRptrPortTrainingResult contain valid information. This bit is cleared when vgRptrPortStatus transitions to the 'inactive' or 'training' state. G: LinkGood: indicates the link hardware is OK. Set if 24 consecutive error-free training packets have been exchanged. Cleared when a training packet with errors is received, or when vgRptrPortStatus transitions to the 'inactive' or 'training' state. The format of the current version of the allowed configuration field is described in section 3.2. Please refer to the most recent version of the IEEE 802.12 standard for the most up-to-date definition of the format of this field. If the port is in training, a management station can examine this object to see if any training packets have been passed successfully. If there have been any good training packets, the Valid bit will be set and the management station can examine the allowed configuration field to see if there is a duplicate address, configuration, or security problem. Note that on a repeater local port, this repeater generates the training response bits, while on a cascade port, the device at the upper end of the link originated the training response bits.
.1.3.6.1.2.1.53.1.1.3.1.1.10,DOT12-RPTR-MIB::vgRptrPortPriorityEnable,INTEGER,read-write,,current,true(1):false(2),A configuration flag used to determine whether the repeater will service high priority requests received on the port as high priority or normal priority. When 'false', high priority requests on this port will be serviced as normal priority. The setting of this object has no effect on a cascade port. Also note that the setting of this object has no effect on a port connected to a cascaded repeater. In both of these cases, this setting is treated as always 'true'. The value 'false' only has an effect when the port is a localInternal or localExternal port connected to an end node. The value of this object should be preserved across repeater resets and power failures.
.1.3.6.1.2.1.53.1.1.3.1.1.11,DOT12-RPTR-MIB::vgRptrPortRptrInfoIndex,Integer32,read-only,,current,,This object identifies the repeater that this port is currently mapped to. The repeater identified by a particular value of this object is the same as that identified by the same value of vgRptrInfoIndex. A value of zero indicates that this port is not currently mapped to any repeater.
.1.3.6.1.2.1.53.1.2,DOT12-RPTR-MIB::vgRptrMonitor,,,,,,
.1.3.6.1.2.1.53.1.2.1,DOT12-RPTR-MIB::vgRptrMonRepeater,,,,,,
.1.3.6.1.2.1.53.1.2.1.1,DOT12-RPTR-MIB::vgRptrMonitorTable,,not-accessible,,current,,A table of performance and error statistics for each repeater in the system. The instance of the vgRptrInfoLastChange associated with a repeater is used to indicate possible discontinuities of the counters in this table that are associated with the same repeater.
.1.3.6.1.2.1.53.1.2.1.1.1,DOT12-RPTR-MIB::vgRptrMonitorEntry,,not-accessible,vgRptrInfoIndex,current,,An entry in the table, containing statistics for a single repeater.
.1.3.6.1.2.1.53.1.2.1.1.1.1,DOT12-RPTR-MIB::vgRptrMonTotalReadableFrames,Counter32,read-only,,current,,The total number of good frames of valid frame length that have been received on all ports in this repeater. If an implementation cannot obtain a count of frames as seen by the repeater itself, this counter may be implemented as the summation of the values of the vgRptrPortReadableFrames counters for all of the ports in this repeater. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrInfoLastChange changes.
.1.3.6.1.2.1.53.1.2.1.1.1.2,DOT12-RPTR-MIB::vgRptrMonTotalReadableOctets,Counter32,read-only,,current,,The total number of octets contained in good frames that have been received on all ports in this repeater. If an implementation cannot obtain a count of octets as seen by the repeater itself, this counter may be implemented as the summation of the values of the vgRptrPortReadableOctets counters for all of the ports in this repeater. Note that this counter can roll over very quickly. A management station is advised to also poll the vgRptrReadableOctetRollovers object, or to use the 64-bit counter defined by vgRptrMonHCTotalReadableOctets instead of the two 32-bit counters. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrInfoLastChange changes.
.1.3.6.1.2.1.53.1.2.1.1.1.3,DOT12-RPTR-MIB::vgRptrMonReadableOctetRollovers,Counter32,read-only,,current,,The total number of times that the associated instance of the vgRptrMonTotalReadableOctets counter has rolled over. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrInfoLastChange changes.
.1.3.6.1.2.1.53.1.2.1.1.1.4,DOT12-RPTR-MIB::vgRptrMonHCTotalReadableOctets,Counter64,read-only,,current,,The total number of octets contained in good frames that have been received on all ports in this repeater. If an implementation cannot obtain a count of octets as seen by the repeater itself, this counter may be implemented as the summation of the values of the vgRptrPortHCReadableOctets counters for all of the ports in this repeater. This counter is a 64 bit version of vgRptrMonTotalReadableOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2). This counter may experience a discontinuity when the value of the corresponding instance of vgRptrInfoLastChange changes.
.1.3.6.1.2.1.53.1.2.1.1.1.5,DOT12-RPTR-MIB::vgRptrMonTotalErrors,Counter32,read-only,,current,,The total number of errors which have occurred on all of the ports in this repeater. If an implementation cannot obtain a count of these errors as seen by the repeater itself, this counter may be implemented as the summation of the values of the vgRptrPortIPMFrames, vgRptrPortOversizeFrames, and vgRptrPortDataErrorFrames counters for all of the ports in this repeater. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrInfoLastChange changes.
.1.3.6.1.2.1.53.1.2.2,DOT12-RPTR-MIB::vgRptrMonGroup,,,,,,
.1.3.6.1.2.1.53.1.2.3,DOT12-RPTR-MIB::vgRptrMonPort,,,,,,
.1.3.6.1.2.1.53.1.2.3.1,DOT12-RPTR-MIB::vgRptrMonPortTable,,not-accessible,,current,,A table of performance and error statistics for the ports. The columnar object vgRptrPortLastChange is used to indicate possible discontinuities of counter type columnar objects in this table.
.1.3.6.1.2.1.53.1.2.3.1.1,DOT12-RPTR-MIB::vgRptrMonPortEntry,,not-accessible,vgRptrGroupIndex:vgRptrPortIndex,current,,An entry in the vgRptrMonPortTable, containing performance and error statistics for a single port.
.1.3.6.1.2.1.53.1.2.3.1.1.1,DOT12-RPTR-MIB::vgRptrPortReadableFrames,Counter32,read-only,,current,,This object is the number of good frames of valid frame length that have been received on this port. This counter is incremented by one for each frame received on the port which is not counted by any of the following error counters: vgRptrPortIPMFrames, vgRptrPortOversizeFrames, vgRptrPortNullAddressedFrames, or vgRptrPortDataErrorFrames. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.2,DOT12-RPTR-MIB::vgRptrPortReadableOctets,Counter32,read-only,,current,,This object is a count of the number of octets contained in good frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame (i.e. each frame counted by vgRptrPortReadableFrames). Note that this counter can roll over very quickly. A management station is advised to also poll the vgRptrPortReadOctetRollovers object, or to use the 64-bit counter defined by vgRptrPortHCReadableOctets instead of the two 32-bit counters. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.3,DOT12-RPTR-MIB::vgRptrPortReadOctetRollovers,Counter32,read-only,,current,,This object is a count of the number of times that the associated instance of the vgRptrPortReadableOctets counter has rolled over. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.4,DOT12-RPTR-MIB::vgRptrPortHCReadableOctets,Counter64,read-only,,current,,This object is a count of the number of octets contained in good frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which has been determined to be a readable frame (i.e. each frame counted by vgRptrPortReadableFrames). This counter is a 64 bit version of vgRptrPortReadableOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2). This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.5,DOT12-RPTR-MIB::vgRptrPortUnreadableOctets,Counter32,read-only,,current,,This object is a count of the number of octets contained in invalid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which is counted by vgRptrPortIPMFrames, vgRptrPortOversizeFrames, vgRptrPortNullAddressedFrames, or vgRptrPortDataErrorFrames. This counter can be combined with vgRptrPortReadableOctets to calculate network utilization. Note that this counter can roll over very quickly. A management station is advised to also poll the vgRptrPortUnreadOctetRollovers object, or to use the 64-bit counter defined by vgRptrPortHCUnreadableOctets instead of the two 32-bit counters. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.6,DOT12-RPTR-MIB::vgRptrPortUnreadOctetRollovers,Counter32,read-only,,current,,This object is a count of the number of times that the associated instance of the vgRptrPortUnreadableOctets counter has rolled over. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.7,DOT12-RPTR-MIB::vgRptrPortHCUnreadableOctets,Counter64,read-only,,current,,This object is a count of the number of octets contained in invalid frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which is counted by vgRptrPortIPMFrames, vgRptrPortOversizeFrames, vgRptrPortNullAddressedFrames, or vgRptrPortDataErrorFrames. This counter can be combined with vgRptrPortHCReadableOctets to calculate network utilization. This counter is a 64 bit version of vgRptrPortUnreadableOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2). This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.8,DOT12-RPTR-MIB::vgRptrPortHighPriorityFrames,Counter32,read-only,,current,,This object is a count of high priority frames that have been received on this port. This counter is incremented by one for each high priority frame received on this port. This counter includes both good and bad high priority frames, as well as high priority training frames. This counter does not include normal priority frames which were priority promoted. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.9,DOT12-RPTR-MIB::vgRptrPortHighPriorityOctets,Counter32,read-only,,current,,This object is a count of the number of octets contained in high priority frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which is counted by vgRptrPortHighPriorityFrames. Note that this counter can roll over very quickly. A management station is advised to also poll the vgRptrPortHighPriOctetRollovers object, or to use the 64-bit counter defined by vgRptrPortHCHighPriorityOctets instead of the two 32-bit counters. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.10,DOT12-RPTR-MIB::vgRptrPortHighPriOctetRollovers,Counter32,read-only,,current,,This object is a count of the number of times that the associated instance of the vgRptrPortHighPriorityOctets counter has rolled over. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.11,DOT12-RPTR-MIB::vgRptrPortHCHighPriorityOctets,Counter64,read-only,,current,,This object is a count of the number of octets contained in high priority frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which is counted by vgRptrPortHighPriorityFrames. This counter is a 64 bit version of vgRptrPortHighPriorityOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2). This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.12,DOT12-RPTR-MIB::vgRptrPortNormPriorityFrames,Counter32,read-only,,current,,This object is a count of normal priority frames that have been received on this port. This counter is incremented by one for each normal priority frame received on this port. This counter includes both good and bad normal priority frames, as well as normal priority training frames and normal priority frames which were priority promoted. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.13,DOT12-RPTR-MIB::vgRptrPortNormPriorityOctets,Counter32,read-only,,current,,This object is a count of the number of octets contained in normal priority frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which is counted by vgRptrPortNormPriorityFrames. Note that this counter can roll over very quickly. A management station is advised to also poll the vgRptrPortNormPriOctetRollovers object, or to use the 64-bit counter defined by vgRptrPortHCNormPriorityOctets instead of the two 32-bit counters. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.14,DOT12-RPTR-MIB::vgRptrPortNormPriOctetRollovers,Counter32,read-only,,current,,This object is a count of the number of times that the associated instance of the vgRptrPortNormPriorityOctets counter has rolled over. This two-counter mechanism is provided for those network management protocols that do not support 64-bit counters (e.g. SNMPv1). Note that retrieval of these two counters in the same PDU is NOT guaranteed to be atomic. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.15,DOT12-RPTR-MIB::vgRptrPortHCNormPriorityOctets,Counter64,read-only,,current,,This object is a count of the number of octets contained in normal priority frames that have been received on this port. This counter is incremented by OctetCount for each frame received on this port which is counted by vgRptrPortNormPriorityFrames. This counter is a 64 bit version of vgRptrPortNormPriorityOctets. It should be used by Network Management protocols which support 64 bit counters (e.g. SNMPv2). This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.16,DOT12-RPTR-MIB::vgRptrPortBroadcastFrames,Counter32,read-only,,current,,This object is a count of broadcast packets that have been received on this port. This counter is incremented by one for each readable frame received on this port whose destination MAC address is the broadcast address. Frames counted by this counter are also counted by vgRptrPortReadableFrames. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.17,DOT12-RPTR-MIB::vgRptrPortMulticastFrames,Counter32,read-only,,current,,This object is a count of multicast packets that have been received on this port. This counter is incremented by one for each readable frame received on this port whose destination MAC address has the group address bit set, but is not the broadcast address. Frames counted by this counter are also counted by vgRptrPortReadableFrames, but not by vgRptrPortBroadcastFrames. Note that when the value of the instance vgRptrInfoCurrentFramingType for the repeater that this port is associated with is equal to 'frameType88025', this count includes packets addressed to functional addresses. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.18,DOT12-RPTR-MIB::vgRptrPortNullAddressedFrames,Counter32,read-only,,current,,This object is a count of null addressed packets that have been received on this port. This counter is incremented by one for each frame received on this port with a destination MAC address consisting of all zero bits. Both void and training frames are included in this counter. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.19,DOT12-RPTR-MIB::vgRptrPortIPMFrames,Counter32,read-only,,current,,This object is a count of the number of frames that have been received on this port with an invalid packet marker and no PMI errors. A repeater will write an invalid packet marker to the end of a frame containing errors as it is forwarded through the repeater to the other ports. This counter is incremented by one for each frame received on this port which has had an invalid packet marker added to the end of the frame. This counter indicates problems occurring in the domain of other repeaters, as opposed to problems with cables or devices directly attached to this repeater. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.20,DOT12-RPTR-MIB::vgRptrPortOversizeFrames,Counter32,read-only,,current,,This object is a count of oversize frames received on this port. This counter is incremented by one for each frame received on this port whose OctetCount is larger than the maximum legal frame size. The frame size which causes this counter to increment is dependent on the current value of vgRptrInfoCurrentFramingType for the repeater that the port is associated with. When vgRptrInfoCurrentFramingType is equal to frameType88023 this counter will increment for frames that are 1519 octets or larger. When vgRptrInfoCurrentFramingType is equal to frameType88025 this counter will increment for frames that are 4521 octets or larger. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.21,DOT12-RPTR-MIB::vgRptrPortDataErrorFrames,Counter32,read-only,,current,,This object is a count of errored frames received on this port. This counter is incremented by one for each frame received on this port with any of the following errors: bad FCS (with no IPM), PMI errors (excluding frames with an IPM error as the only PMI error), or undersize (with no IPM). Does not include packets counted by vgRptrPortIPMFrames, vgRptrPortOversizeFrames, or vgRptrPortNullAddressedFrames. This counter indicates problems with cables or devices directly connected to this repeater, while vgRptrPortIPMFrames indicates problems occurring in the domain of other repeaters. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.22,DOT12-RPTR-MIB::vgRptrPortPriorityPromotions,Counter32,read-only,,current,,This counter is incremented by one each time the priority promotion timer has expired on this port and a normal priority frame is priority promoted. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.23,DOT12-RPTR-MIB::vgRptrPortTransitionToTrainings,Counter32,read-only,,current,,This counter is incremented by one each time the vgRptrPortStatus object for this port transitions into the 'training' state. This counter may experience a discontinuity when the value of the corresponding instance of vgRptrPortLastChange changes.
.1.3.6.1.2.1.53.1.2.3.1.1.24,DOT12-RPTR-MIB::vgRptrPortLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when the last of the following occurred: 1) the agent cold- or warm-started; 2) the row for the port was created (such as when a device or module was added to the system); or 3) any condition that would cause one of the counters for the row to experience a discontinuity.
.1.3.6.1.2.1.53.1.3,DOT12-RPTR-MIB::vgRptrAddrTrack,,,,,,
.1.3.6.1.2.1.53.1.3.1,DOT12-RPTR-MIB::vgRptrAddrTrackRptr,,,,,,
.1.3.6.1.2.1.53.1.3.2,DOT12-RPTR-MIB::vgRptrAddrTrackGroup,,,,,,
.1.3.6.1.2.1.53.1.3.3,DOT12-RPTR-MIB::vgRptrAddrTrackPort,,,,,,
.1.3.6.1.2.1.53.1.3.3.1,DOT12-RPTR-MIB::vgRptrAddrTrackTable,,not-accessible,,current,,Table of address mapping information about the ports.
.1.3.6.1.2.1.53.1.3.3.1.1,DOT12-RPTR-MIB::vgRptrAddrTrackEntry,,not-accessible,vgRptrGroupIndex:vgRptrPortIndex,current,,An entry in the table, containing address mapping information about a single port.
.1.3.6.1.2.1.53.1.3.3.1.1.1,DOT12-RPTR-MIB::vgRptrAddrLastTrainedAddress,OCTET,read-only,,current,,This object is the MAC address of the last station which succeeded in training on this port. A cascaded repeater may train using the null address. If no stations have succeeded in training on this port since the agent began monitoring the port activity, the agent shall return a string of length zero.
.1.3.6.1.2.1.53.1.3.3.1.1.2,DOT12-RPTR-MIB::vgRptrAddrTrainedAddrChanges,Counter32,read-only,,current,,This counter is incremented by one for each time that the vgRptrAddrLastTrainedAddress object for this port changes.
.1.3.6.1.2.1.53.1.3.3.1.1.3,DOT12-RPTR-MIB::vgRptrRptrDetectedDupAddress,INTEGER,read-only,,current,true(1):false(2),This object is used to indicate that the repeater detected an error-free training frame on this port with a non-null source MAC address which matches the value of vgRptrAddrLastTrainedAddress of another active port in the same repeater. This is reset to 'false' when an error-free training frame is received with a non-null source MAC address which does not match vgRptrAddrLastTrainedAddress of another port which is active in the same repeater. For the cascade port, this object will be 'true' if the 'D' bit in the most recently received error-free training response frame was set, indicating the device at the other end of the link believes that this repeater's cascade port is using a duplicate address. This may be because the device at the other end of the link detected a duplicate address itself, or, if the other device is also a repeater, it could be because vgRptrMgrDetectedDupAddress was set to 'true' on the port that this repeater's cascade port is connected to.
.1.3.6.1.2.1.53.1.3.3.1.1.4,DOT12-RPTR-MIB::vgRptrMgrDetectedDupAddress,INTEGER,read-write,,current,true(1):false(2),This object can be set by a management station when it detects that there is a duplicate MAC address. This object is OR'd with vgRptrRptrDetectedDupAddress to form the value of the 'D' bit in training response frames on this port. The purpose of this object is to provide a means for network management software to inform an end station that it is using a duplicate station address. Setting this object does not affect the current state of the link; the end station will not be informed of the duplicate address until it retrains for some reason. Note that regardless of its station address, the end station will not be able to train successfully until the network management software has set this object back to 'false'. Although this object exists on cascade ports, it does not perform any function since this repeater is the initiator of training on a cascade port.
.1.3.6.1.2.1.53.2,DOT12-RPTR-MIB::vgRptrTraps,,,,,,
.1.3.6.1.2.1.53.2.0,DOT12-RPTR-MIB::vgRptrTrapPrefix,,,,,,
.1.3.6.1.2.1.53.2.0.1,DOT12-RPTR-MIB::vgRptrHealth,,,,,,A vgRptrHealth trap conveys information related to the operational state of a repeater. This trap is sent when the value of an instance of vgRptrInfoOperStatus changes. The vgRptrHealth trap is not sent as a result of powering up a repeater. The vgRptrHealth trap must contain the instance of the vgRptrInfoOperStatus object associated with the affected repeater. The agent must throttle the generation of consecutive vgRptrHealth traps so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.)
.1.3.6.1.2.1.53.2.0.2,DOT12-RPTR-MIB::vgRptrResetEvent,,,,,,A vgRptrResetEvent trap conveys information related to the operational state of a repeater. This trap is sent on completion of a repeater reset action. A repeater reset action is defined as a transition to its initial state as specified in clause 12 [IEEE Std 802.12] when triggered by a management command. The vgRptrResetEvent trap is not sent when the agent restarts and sends an SNMP coldStart or warmStart trap. The vgRptrResetEvent trap must contain the instance of the vgRptrInfoOperStatus object associated with the affected repeater. The agent must throttle the generation of consecutive vgRptrResetEvent traps so that there is at least a five-second gap between traps of this type. When traps are throttled, they are dropped, not queued for sending at a future time. (Note that 'generating' a trap means sending to all configured recipients.)
.1.3.6.1.2.1.53.3,DOT12-RPTR-MIB::vgRptrConformance,,,,,,
.1.3.6.1.2.1.53.3.1,DOT12-RPTR-MIB::vgRptrCompliances,,,,,,
.1.3.6.1.2.1.53.3.1.1,DOT12-RPTR-MIB::vgRptrCompliance,,,,,,The compliance statement for managed 802.12 repeaters.
.1.3.6.1.2.1.53.3.2,DOT12-RPTR-MIB::vgRptrGroups,,,,,,
.1.3.6.1.2.1.53.3.2.1,DOT12-RPTR-MIB::vgRptrConfigGroup,,,,,,A collection of objects for managing the status and configuration of IEEE 802.12 repeaters.
.1.3.6.1.2.1.53.3.2.2,DOT12-RPTR-MIB::vgRptrStatsGroup,,,,,,A collection of objects for providing statistics for IEEE 802.12 repeaters. Systems which support Counter64 should also implement vgRptrStats64Group.
.1.3.6.1.2.1.53.3.2.3,DOT12-RPTR-MIB::vgRptrStats64Group,,,,,,A collection of objects for providing statistics for IEEE 802.12 repeaters in a system that supports Counter64.
.1.3.6.1.2.1.53.3.2.4,DOT12-RPTR-MIB::vgRptrAddrGroup,,,,,,A collection of objects for tracking addresses on IEEE 802.12 repeaters.
.1.3.6.1.2.1.53.3.2.5,DOT12-RPTR-MIB::vgRptrNotificationsGroup,,,,,,A collection of notifications used to indicate 802.12 repeater general status changes.
.1.3.6.1.2.1.54,SYSAPPL-MIB::sysApplMIB,,,,,,The MIB module defines management objects that model applications as collections of executables and files installed and executing on a host system. The MIB presents a system-level view of applications; i.e., objects in this MIB are limited to those attributes that can typically be obtained from the system itself without adding special instrumentation to the applications.
.1.3.6.1.2.1.54.1,SYSAPPL-MIB::sysApplOBJ,,,,,,
.1.3.6.1.2.1.54.1.1,SYSAPPL-MIB::sysApplInstalled,,,,,,
.1.3.6.1.2.1.54.1.1.1,SYSAPPL-MIB::sysApplInstallPkgTable,,not-accessible,,current,,The table listing the software application packages installed on a host computer. In order to appear in this table, it may be necessary for the application to be installed using some type of software installation mechanism or global registry so that its existence can be detected by the agent implementation.
.1.3.6.1.2.1.54.1.1.1.1,SYSAPPL-MIB::sysApplInstallPkgEntry,,not-accessible,sysApplInstallPkgIndex,current,,The logical row describing an installed application package.
.1.3.6.1.2.1.54.1.1.1.1.1,SYSAPPL-MIB::sysApplInstallPkgIndex,Unsigned32,not-accessible,,current,,An integer used only for indexing purposes. Generally monotonically increasing from 1 as new applications are installed. The value for each installed application must remain constant at least from one re-initialization of the network management entity which implements this MIB module to the next re-initialization. The specific value is meaningful only within a given SNMP entity. A sysApplInstallPkgIndex value must not be re-used until the next agent entity restart in the event the installed application entry is deleted.
.1.3.6.1.2.1.54.1.1.1.1.2,SYSAPPL-MIB::sysApplInstallPkgManufacturer,OCTET,read-only,,current,,The Manufacturer of the software application package.
.1.3.6.1.2.1.54.1.1.1.1.3,SYSAPPL-MIB::sysApplInstallPkgProductName,OCTET,read-only,,current,,The name assigned to the software application package by the Manufacturer.
.1.3.6.1.2.1.54.1.1.1.1.4,SYSAPPL-MIB::sysApplInstallPkgVersion,OCTET,read-only,,current,,The version number assigned to the application package by the manufacturer of the software.
.1.3.6.1.2.1.54.1.1.1.1.5,SYSAPPL-MIB::sysApplInstallPkgSerialNumber,OCTET,read-only,,current,,The serial number of the software assigned by the manufacturer.
.1.3.6.1.2.1.54.1.1.1.1.6,SYSAPPL-MIB::sysApplInstallPkgDate,OCTET,read-only,,current,,The date and time this software application was installed on the host.
.1.3.6.1.2.1.54.1.1.1.1.7,SYSAPPL-MIB::sysApplInstallPkgLocation,OCTET,read-only,,current,,The complete path name where the application package is installed. For example, the value would be '/opt/MyapplDir' if the application package was installed in the /opt/MyapplDir directory.
.1.3.6.1.2.1.54.1.1.2,SYSAPPL-MIB::sysApplInstallElmtTable,,not-accessible,,current,,This table details the individual application package elements (files and executables) which comprise the applications defined in the sysApplInstallPkg Table. Each entry in this table has an index to the sysApplInstallPkg table to identify the application package of which it is a part. As a result, there may be many entries in this table for each instance in the sysApplInstallPkg Table. Table entries are indexed by sysApplInstallPkgIndex, sysApplInstallElmtIndex to facilitate retrieval of all elements associated with a particular installed application package.
.1.3.6.1.2.1.54.1.1.2.1,SYSAPPL-MIB::sysApplInstallElmtEntry,,not-accessible,sysApplInstallPkgIndex:sysApplInstallElmtIndex,current,,The logical row describing an element of an installed application. The element may be an executable or non-executable file.
.1.3.6.1.2.1.54.1.1.2.1.1,SYSAPPL-MIB::sysApplInstallElmtIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used for indexing. The value of this index is unique among all rows in this table that exist or have existed since the last agent restart.
.1.3.6.1.2.1.54.1.1.2.1.2,SYSAPPL-MIB::sysApplInstallElmtName,OCTET,read-only,,current,,The name of this element which is contained in the application.
.1.3.6.1.2.1.54.1.1.2.1.3,SYSAPPL-MIB::sysApplInstallElmtType,INTEGER,read-only,,current,unknown(1):nonexecutable(2):operatingSystem(3):deviceDriver(4):application(5),The type of element that is part of the installed application.
.1.3.6.1.2.1.54.1.1.2.1.4,SYSAPPL-MIB::sysApplInstallElmtDate,OCTET,read-only,,current,,The date and time that this component was installed on the system.
.1.3.6.1.2.1.54.1.1.2.1.5,SYSAPPL-MIB::sysApplInstallElmtPath,OCTET,read-only,,current,,The full directory path where this element is installed. For example, the value would be '/opt/EMPuma/bin' for an element installed in the directory '/opt/EMPuma/bin'. Most application packages include information about the elements contained in the package. In addition, elements are typically installed in sub-directories under the package installation directory. In cases where the element path names are not included in the package information itself, the path can usually be determined by a simple search of the sub-directories. If the element is not installed in that location and there is no other information available to the agent implementation, then the path is unknown and null is returned.
.1.3.6.1.2.1.54.1.1.2.1.6,SYSAPPL-MIB::sysApplInstallElmtSizeHigh,Unsigned32,read-only,,current,,The installed file size in 2^32 byte blocks. This is the size of the file on disk immediately after installation. For example, for a file with a total size of 4,294,967,296 bytes, this variable would have a value of 1; for a file with a total size of 4,294,967,295 bytes this variable would be 0.
.1.3.6.1.2.1.54.1.1.2.1.7,SYSAPPL-MIB::sysApplInstallElmtSizeLow,Unsigned32,read-only,,current,,The installed file size modulo 2^32 bytes. This is the size of the file on disk immediately after installation. For example, for a file with a total size of 4,294,967,296 bytes this variable would have a value of 0; for a file with a total size of 4,294,967,295 bytes this variable would be 4,294,967,295.
.1.3.6.1.2.1.54.1.1.2.1.8,SYSAPPL-MIB::sysApplInstallElmtRole,OCTET,read-write,,current,,An operator assigned value used in the determination of application status. This value is used by the agent to determine both the mapping of started processes to the initiation of an application, as well as to allow for a determination of application health. The default value, unknown(5), is used when an operator has not yet assigned one of the other values. If unknown(5) is set, bits 1 - 4 have no meaning. The possible values are: executable(0), An application may have one or more executable elements. The rest of the bits have no meaning if the element is not executable. exclusive(1), Only one copy of an exclusive element may be running per invocation of the running application. primary(2), The primary executable. An application can have one, and only one element that is designated as the primary executable. The execution of this element constitutes an invocation of the application. This is used by the agent implementation to determine the initiation of an application. The primary executable must remain running long enough for the agent implementation to detect its presence. required(3), An application may have zero or more required elements. All required elements must be running in order for the application to be judged to be running and healthy. dependent(4), An application may have zero or more dependent elements. Dependent elements may not be running unless required elements are. unknown(5) Default value for the case when an operator has not yet assigned one of the other values. When set, bits 1, 2, 3, and 4 have no meaning. sysApplInstallElmtRole is used by the agent implementation in determining the initiation of an application, the current state of a running application (see sysApplRunCurrentState), when an application invocation is no longer running, and the exit status of a terminated application invocation (see sysApplPastRunExitState).
.1.3.6.1.2.1.54.1.1.2.1.9,SYSAPPL-MIB::sysApplInstallElmtModifyDate,OCTET,read-only,,current,,The date and time that this element was last modified. Modification of the sysApplInstallElmtRole columnar object does NOT constitute a modification of the element itself and should not affect the value of this object.
.1.3.6.1.2.1.54.1.1.2.1.10,SYSAPPL-MIB::sysApplInstallElmtCurSizeHigh,Unsigned32,read-only,,current,,The current file size in 2^32 byte blocks. For example, for a file with a total size of 4,294,967,296 bytes, this variable would have a value of 1; for a file with a total size of 4,294,967,295 bytes this variable would be 0.
.1.3.6.1.2.1.54.1.1.2.1.11,SYSAPPL-MIB::sysApplInstallElmtCurSizeLow,Unsigned32,read-only,,current,,The current file size modulo 2^32 bytes. For example, for a file with a total size of 4,294,967,296 bytes this variable would have a value of 0; for a file with a total size of 4,294,967,295 bytes this variable would be 4,294,967,295.
.1.3.6.1.2.1.54.1.2,SYSAPPL-MIB::sysApplRun,,,,,,
.1.3.6.1.2.1.54.1.2.1,SYSAPPL-MIB::sysApplRunTable,,not-accessible,,current,,The table describes the applications which are executing on the host. Each time an application is invoked, an entry is created in this table. When an application ends, the entry is removed from this table and a corresponding entry is created in the SysApplPastRunTable. A new entry is created in this table whenever the agent implementation detects a new running process that is an installed application element whose sysApplInstallElmtRole designates it as being the application's primary executable (sysApplInstallElmtRole = primary(2) ). The table is indexed by sysApplInstallPkgIndex, sysApplRunIndex to enable managers to easily locate all invocations of a particular application package.
.1.3.6.1.2.1.54.1.2.1.1,SYSAPPL-MIB::sysApplRunEntry,,not-accessible,sysApplInstallPkgIndex:sysApplRunIndex,current,,The logical row describing an application which is currently running on this host.
.1.3.6.1.2.1.54.1.2.1.1.1,SYSAPPL-MIB::sysApplRunIndex,Unsigned32,not-accessible,,current,,Part of the index for this table. An arbitrary integer used only for indexing purposes. Generally monotonically increasing from 1 as new applications are started on the host, it uniquely identifies application invocations. The numbering for this index increases by 1 for each INVOCATION of an application, regardless of which installed application package this entry represents a running instance of. An example of the indexing for a couple of entries is shown below. : sysApplRunStarted.17.14 sysApplRunStarted.17.63 sysApplRunStarted.18.13 : In this example, the agent has observed 12 application invocations when the application represented by entry 18 in the sysApplInstallPkgTable is invoked. The next invocation detected by the agent is an invocation of installed application package 17. Some time later, installed application 17 is invoked a second time. NOTE: this index is not intended to reflect a real-time (wall clock time) ordering of application invocations; it is merely intended to uniquely identify running instances of applications. Although the sysApplInstallPkgIndex is included in the INDEX clause for this table, it serves only to ease searching of this table by installed application and does not contribute to uniquely identifying table entries.
.1.3.6.1.2.1.54.1.2.1.1.2,SYSAPPL-MIB::sysApplRunStarted,OCTET,read-only,,current,,The date and time that the application was started.
.1.3.6.1.2.1.54.1.2.1.1.3,SYSAPPL-MIB::sysApplRunCurrentState,INTEGER,read-only,,current,running(1):runnable(2):waiting(3):exiting(4):other(5),The current state of the running application instance. The possible values are running(1), runnable(2) but waiting for a resource such as CPU, waiting(3) for an event, exiting(4), or other(5). This value is based on an evaluation of the running elements of this application instance (see sysApplElmRunState) and their Roles as defined by sysApplInstallElmtRole. An agent implementation may detect that an application instance is in the process of exiting if one or more of its REQUIRED elements are no longer running. Most agent implementations will wait until a second internal poll has been completed to give the system time to start REQUIRED elements before marking the application instance as exiting.
.1.3.6.1.2.1.54.1.2.2,SYSAPPL-MIB::sysApplPastRunTable,,not-accessible,,current,,A history of the applications that have previously run on the host computer. An entry's information is moved to this table from the sysApplRunTable when the invoked application represented by the entry ceases to be running. An agent implementation can determine that an application invocation is no longer running by evaluating the running elements of the application instance and their Roles as defined by sysApplInstallElmtRole. Obviously, if there are no running elements for the application instance, then the application invocation is no longer running. If any one of the REQUIRED elements is not running, the application instance may be in the process of exiting. Most agent implementations will wait until a second internal poll has been completed to give the system time to either restart partial failures or to give all elements time to exit. If, after the second poll, there are REQUIRED elements that are not running, then the application instance may be considered by the agent implementation to no longer be running. Entries remain in the sysApplPastRunTable until they are aged out when either the table size reaches a maximum as determined by the sysApplPastRunMaxRows, or when an entry has aged to exceed a time limit as set by sysApplPastRunTblTimeLimit. Entries in this table are indexed by sysApplInstallPkgIndex, sysApplPastRunIndex to facilitate retrieval of all past run invocations of a particular installed application.
.1.3.6.1.2.1.54.1.2.2.1,SYSAPPL-MIB::sysApplPastRunEntry,,not-accessible,sysApplInstallPkgIndex:sysApplPastRunIndex,current,,The logical row describing an invocation of an application which was previously run and has terminated. The entry is basically copied from the sysApplRunTable when the application instance terminates. Hence, the entry's value for sysApplPastRunIndex is the same as its value was for sysApplRunIndex.
.1.3.6.1.2.1.54.1.2.2.1.1,SYSAPPL-MIB::sysApplPastRunIndex,Unsigned32,not-accessible,,current,,Part of the index for this table. An integer matching the value of the removed sysApplRunIndex corresponding to this row.
.1.3.6.1.2.1.54.1.2.2.1.2,SYSAPPL-MIB::sysApplPastRunStarted,OCTET,read-only,,current,,The date and time that the application was started.
.1.3.6.1.2.1.54.1.2.2.1.3,SYSAPPL-MIB::sysApplPastRunExitState,INTEGER,read-only,,current,complete(1):failed(2):other(3),The state of the application instance when it terminated. This value is based on an evaluation of the running elements of an application and their Roles as defined by sysApplInstallElmtRole. An application instance is said to have exited in a COMPLETE state and its entry is removed from the sysApplRunTable and added to the sysApplPastRunTable when the agent detects that ALL elements of an application invocation are no longer running. Most agent implementations will wait until a second internal poll has been completed to give the system time to either restart partial failures or to give all elements time to exit. A failed state occurs if, after the second poll, any elements continue to run but one or more of the REQUIRED elements are no longer running. All other combinations MUST be defined as OTHER.
.1.3.6.1.2.1.54.1.2.2.1.4,SYSAPPL-MIB::sysApplPastRunTimeEnded,OCTET,read-only,,current,,The DateAndTime the application instance was determined to be no longer running.
.1.3.6.1.2.1.54.1.2.3,SYSAPPL-MIB::sysApplElmtRunTable,,not-accessible,,current,,The table describes the processes which are currently executing on the host system. Each entry represents a running process and is associated with the invoked application of which that process is a part, if possible. This table contains an entry for every process currently running on the system, regardless of whether its 'parent' application can be determined. So, for example, processes like 'ps' and 'grep' will have entries though they are not associated with an installed application package. Because a running application may involve more than one executable, it is possible to have multiple entries in this table for each application. Entries are removed from this table when the process terminates. The table is indexed by sysApplElmtRunInstallPkg, sysApplElmtRunInvocID, and sysApplElmtRunIndex to facilitate the retrieval of all running elements of a particular invoked application which has been installed on the system.
.1.3.6.1.2.1.54.1.2.3.1,SYSAPPL-MIB::sysApplElmtRunEntry,,not-accessible,sysApplElmtRunInstallPkg:sysApplElmtRunInvocID:sysApplElmtRunIndex,current,,The logical row describing a process currently running on this host. When possible, the entry is associated with the invoked application of which it is a part.
.1.3.6.1.2.1.54.1.2.3.1.1,SYSAPPL-MIB::sysApplElmtRunInstallPkg,Unsigned32,not-accessible,,current,,Part of the index for this table, this value identifies the installed software package for the application of which this process is a part. Provided that the process's 'parent' application can be determined, the value of this object is the same value as the sysApplInstallPkgIndex for the entry in the sysApplInstallPkgTable that corresponds to the installed application of which this process is a part. If, however, the 'parent' application cannot be determined, (for example the process is not part of a particular installed application), the value for this object is then '0', signifying that this process cannot be related back to an application, and in turn, an installed software package.
.1.3.6.1.2.1.54.1.2.3.1.2,SYSAPPL-MIB::sysApplElmtRunInvocID,Unsigned32,not-accessible,,current,,Part of the index for this table, this value identifies the invocation of an application of which this process is a part. Provided that the 'parent' application can be determined, the value of this object is the same value as the sysApplRunIndex for the corresponding application invocation in the sysApplRunTable. If, however, the 'parent' application cannot be determined, the value for this object is then '0', signifying that this process cannot be related back to an invocation of an application in the sysApplRunTable.
.1.3.6.1.2.1.54.1.2.3.1.3,SYSAPPL-MIB::sysApplElmtRunIndex,Unsigned32,not-accessible,,current,,Part of the index for this table. A unique value for each process running on the host. Wherever possible, this should be the system's native, unique identification number.
.1.3.6.1.2.1.54.1.2.3.1.4,SYSAPPL-MIB::sysApplElmtRunInstallID,Unsigned32,read-only,,current,,The index into the sysApplInstallElmtTable. The value of this object is the same value as the sysApplInstallElmtIndex for the application element of which this entry represents a running instance. If this process cannot be associated with an installed executable, the value should be '0'.
.1.3.6.1.2.1.54.1.2.3.1.5,SYSAPPL-MIB::sysApplElmtRunTimeStarted,OCTET,read-only,,current,,The time the process was started.
.1.3.6.1.2.1.54.1.2.3.1.6,SYSAPPL-MIB::sysApplElmtRunState,INTEGER,read-only,,current,running(1):runnable(2):waiting(3):exiting(4):other(5),The current state of the running process. The possible values are running(1), runnable(2) but waiting for a resource such as CPU, waiting(3) for an event, exiting(4), or other(5).
.1.3.6.1.2.1.54.1.2.3.1.7,SYSAPPL-MIB::sysApplElmtRunName,OCTET,read-only,,current,,The full path and filename of the process. For example, '/opt/MYYpkg/bin/myyproc' would be returned for process 'myyproc' whose execution path is '/opt/MYYpkg/bin/myyproc'.
.1.3.6.1.2.1.54.1.2.3.1.8,SYSAPPL-MIB::sysApplElmtRunParameters,OCTET,read-only,,current,,The starting parameters for the process.
.1.3.6.1.2.1.54.1.2.3.1.9,SYSAPPL-MIB::sysApplElmtRunCPU,TimeTicks,read-only,,current,,The number of centi-seconds of the total system's CPU resources consumed by this process. Note that on a multi-processor system, this value may have been incremented by more than one centi-second in one centi-second of real (wall clock) time.
.1.3.6.1.2.1.54.1.2.3.1.10,SYSAPPL-MIB::sysApplElmtRunMemory,Gauge32,read-only,,current,,The total amount of real system memory measured in Kbytes currently allocated to this process.
.1.3.6.1.2.1.54.1.2.3.1.11,SYSAPPL-MIB::sysApplElmtRunNumFiles,Gauge32,read-only,,current,,The number of regular files currently open by the process. Transport connections (sockets) should NOT be included in the calculation of this value, nor should operating system specific special file types.
.1.3.6.1.2.1.54.1.2.3.1.12,SYSAPPL-MIB::sysApplElmtRunUser,OCTET,read-only,,current,,The process owner's login name (e.g. root).
.1.3.6.1.2.1.54.1.2.4,SYSAPPL-MIB::sysApplElmtPastRunTable,,not-accessible,,current,,The table describes the processes which have previously executed on the host system as part of an application. Each entry represents a process which has previously executed and is associated with the invoked application of which it was a part. Because an invoked application may involve more than one executable, it is possible to have multiple entries in this table for each application invocation. Entries are added to this table when the corresponding process in the sysApplElmtRun Table terminates. Entries remain in this table until they are aged out when either the number of entries in the table reaches a maximum as determined by sysApplElmtPastRunMaxRows, or when an entry has aged to exceed a time limit as set by sysApplElmtPastRunTblTimeLimit. When aging out entries, the oldest entry, as determined by the value of sysApplElmtPastRunTimeEnded, will be removed first. The table is indexed by sysApplInstallPkgIndex (from the sysApplInstallPkgTable), sysApplElmtPastRunInvocID, and sysApplElmtPastRunIndex to make it easy to locate all previously executed processes of a particular invoked application that has been installed on the system.
.1.3.6.1.2.1.54.1.2.4.1,SYSAPPL-MIB::sysApplElmtPastRunEntry,,not-accessible,sysApplInstallPkgIndex:sysApplElmtPastRunInvocID:sysApplElmtPastRunIndex,current,,The logical row describing a process which was previously executed on this host as part of an installed application. The entry is basically copied from the sysApplElmtRunTable when the process terminates. Hence, the entry's value for sysApplElmtPastRunIndex is the same as its value was for sysApplElmtRunIndex. Note carefully: only those processes which could be associated with an identified application are included in this table.
.1.3.6.1.2.1.54.1.2.4.1.1,SYSAPPL-MIB::sysApplElmtPastRunInvocID,Unsigned32,not-accessible,,current,,Part of the index for this table, this value identifies the invocation of an application of which the process represented by this entry was a part. The value of this object is the same value as the sysApplRunIndex for the corresponding application invocation in the sysApplRunTable. If the invoked application as a whole has terminated, it will be the same as the sysApplPastRunIndex.
.1.3.6.1.2.1.54.1.2.4.1.2,SYSAPPL-MIB::sysApplElmtPastRunIndex,Unsigned32,not-accessible,,current,,Part of the index for this table. An integer assigned by the agent equal to the corresponding sysApplElmtRunIndex which was removed from the sysApplElmtRunTable and moved to this table when the element terminated. Note: entries in this table are indexed by sysApplElmtPastRunInvocID, sysApplElmtPastRunIndex. The possibility exists, though unlikely, of a collision occurring by a new entry which was run by the same invoked application (InvocID), and was assigned the same process identification number (ElmtRunIndex) as an element which was previously run by the same invoked application. Should this situation occur, the new entry replaces the old entry. See Section: 'Implementation Issues - sysApplElmtPastRunTable Entry Collisions' for the conditions that would have to occur in order for a collision to occur.
.1.3.6.1.2.1.54.1.2.4.1.3,SYSAPPL-MIB::sysApplElmtPastRunInstallID,Unsigned32,read-only,,current,,The index into the installed element table. The value of this object is the same value as the sysApplInstallElmtIndex for the application element of which this entry represents a previously executed process.
.1.3.6.1.2.1.54.1.2.4.1.4,SYSAPPL-MIB::sysApplElmtPastRunTimeStarted,OCTET,read-only,,current,,The time the process was started.
.1.3.6.1.2.1.54.1.2.4.1.5,SYSAPPL-MIB::sysApplElmtPastRunTimeEnded,OCTET,read-only,,current,,The time the process ended.
.1.3.6.1.2.1.54.1.2.4.1.6,SYSAPPL-MIB::sysApplElmtPastRunName,OCTET,read-only,,current,,The full path and filename of the process. For example, '/opt/MYYpkg/bin/myyproc' would be returned for process 'myyproc' whose execution path was '/opt/MYYpkg/bin/myyproc'.
.1.3.6.1.2.1.54.1.2.4.1.7,SYSAPPL-MIB::sysApplElmtPastRunParameters,OCTET,read-only,,current,,The starting parameters for the process.
.1.3.6.1.2.1.54.1.2.4.1.8,SYSAPPL-MIB::sysApplElmtPastRunCPU,TimeTicks,read-only,,current,,The last known number of centi-seconds of the total system's CPU resources consumed by this process. Note that on a multi-processor system, this value may increment by more than one centi-second in one centi-second of real (wall clock) time.
.1.3.6.1.2.1.54.1.2.4.1.9,SYSAPPL-MIB::sysApplElmtPastRunMemory,Unsigned32,read-only,,current,,The last known total amount of real system memory measured in Kbytes allocated to this process before it terminated.
.1.3.6.1.2.1.54.1.2.4.1.10,SYSAPPL-MIB::sysApplElmtPastRunNumFiles,Unsigned32,read-only,,current,,The last known number of files open by the process before it terminated. Transport connections (sockets) should NOT be included in the calculation of this value.
.1.3.6.1.2.1.54.1.2.4.1.11,SYSAPPL-MIB::sysApplElmtPastRunUser,OCTET,read-only,,current,,The process owner's login name (e.g. root).
.1.3.6.1.2.1.54.1.2.5,SYSAPPL-MIB::sysApplPastRunMaxRows,Unsigned32,read-write,,current,,The maximum number of entries allowed in the sysApplPastRunTable. Once the number of rows in the sysApplPastRunTable reaches this value, the management subsystem will remove the oldest entry in the table to make room for the new entry to be added. Entries will be removed on the basis of oldest sysApplPastRunTimeEnded value first. This object may be used to control the amount of system resources that can used for sysApplPastRunTable entries. A conforming implementation should attempt to support the default value, however, a lesser value may be necessary due to implementation-dependent issues and resource availability.
.1.3.6.1.2.1.54.1.2.6,SYSAPPL-MIB::sysApplPastRunTableRemItems,Counter32,read-only,,current,,A counter of the number of entries removed from the sysApplPastRunTable because of table size limitations as set in sysApplPastRunMaxRows. This counter is the number of entries the management subsystem has had to remove in order to make room for new entries (so as not to exceed the limit set by sysApplPastRunMaxRows) since the last initialization of the management subsystem.
.1.3.6.1.2.1.54.1.2.7,SYSAPPL-MIB::sysApplPastRunTblTimeLimit,Unsigned32,read-write,,current,,The maximum time in seconds which an entry in the sysApplPastRunTable may exist before it is removed. Any entry that is older than this value will be removed (aged out) from the table. Note that an entry may be aged out prior to reaching this time limit if it is the oldest entry in the table and must be removed to make space for a new entry so as to not exceed sysApplPastRunMaxRows.
.1.3.6.1.2.1.54.1.2.8,SYSAPPL-MIB::sysApplElemPastRunMaxRows,Unsigned32,read-write,,current,,The maximum number of entries allowed in the sysApplElmtPastRunTable. Once the number of rows in the sysApplElmtPastRunTable reaches this value, the management subsystem will remove the oldest entry to make room for the new entry to be added. Entries will be removed on the basis of oldest sysApplElmtPastRunTimeEnded value first. This object may be used to control the amount of system resources that can used for sysApplElemPastRunTable entries. A conforming implementation should attempt to support the default value, however, a lesser value may be necessary due to implementation-dependent issues and resource availability.
.1.3.6.1.2.1.54.1.2.9,SYSAPPL-MIB::sysApplElemPastRunTableRemItems,Counter32,read-only,,current,,A counter of the number of entries removed from the sysApplElemPastRunTable because of table size limitations as set in sysApplElemPastRunMaxRows. This counter is the number of entries the management subsystem has had to remove in order to make room for new entries (so as not to exceed the limit set by sysApplElemPastRunMaxRows) since the last initialization of the management subsystem.
.1.3.6.1.2.1.54.1.2.10,SYSAPPL-MIB::sysApplElemPastRunTblTimeLimit,Unsigned32,read-write,,current,,The maximum time in seconds which an entry in the sysApplElemPastRunTable may exist before it is removed. Any entry that is older than this value will be removed (aged out) from the table. Note that an entry may be aged out prior to reaching this time limit if it is the oldest entry in the table and must be removed to make space for a new entry so as to not exceed sysApplElemPastRunMaxRows.
.1.3.6.1.2.1.54.1.2.11,SYSAPPL-MIB::sysApplAgentPollInterval,Unsigned32,read-write,,current,,The minimum interval in seconds that the management subsystem implementing this MIB will poll the status of the managed resources. Because of the non-trivial effort involved in polling the managed resources, and because the method for obtaining the status of the managed resources is implementation-dependent, a conformant implementation may chose a lower bound greater than 0. A value of 0 indicates that there is no delay in the passing of information from the managed resources to the agent.
.1.3.6.1.2.1.54.1.3,SYSAPPL-MIB::sysApplMap,,,,,,
.1.3.6.1.2.1.54.1.3.1,SYSAPPL-MIB::sysApplMapTable,,not-accessible,,current,,The sole purpose of this table is to provide a 'backwards' mapping so that, given a known sysApplElmtRunIndex (process identification number), the corresponding invoked application (sysApplRunIndex), installed element (sysApplInstallElmtIndex), and installed application package (sysApplInstallPkgIndex) can be quickly determined. This table will contain one entry for each process that is currently executing on the system. It is expected that management applications will use this mapping table by doing a 'GetNext' operation with the known process ID number (sysApplElmtRunIndex) as the partial instance identifier. Assuming that there is an entry for the process, the result should return a single columnar value, the sysApplMapInstallPkgIndex, with the sysApplElmtRunIndex, sysApplRunIndex, and sysApplInstallElmtIndex contained in the instance identifier for the returned MIB object value. NOTE: if the process can not be associated back to an invoked application installed on the system, then the value returned for the columnar value sysApplMapInstallPkgIndex will be '0' and the instance portion of the object-identifier will be the process ID number (sysApplElmtRunIndex) followed by 0.0.
.1.3.6.1.2.1.54.1.3.1.1,SYSAPPL-MIB::sysApplMapEntry,,not-accessible,sysApplElmtRunIndex:sysApplElmtRunInvocID:sysApplMapInstallElmtIndex,current,,A logical row representing a process currently running on the system. This entry provides the index mapping from process identifier, back to the invoked application, installed element, and finally, the installed application package. The entry includes only one accessible columnar object, the sysApplMapInstallPkgIndex, but the invoked application and installed element can be determined from the instance identifier since they form part of the index clause.
.1.3.6.1.2.1.54.1.3.1.1.1,SYSAPPL-MIB::sysApplMapInstallElmtIndex,Unsigned32,not-accessible,,current,,The index into the sysApplInstallElmtTable. The value of this object is the same value as the sysApplInstallElmtIndex for the application element of which this entry represents a running instance. If this process cannot be associated to an installed executable, the value should be '0'.
.1.3.6.1.2.1.54.1.3.1.1.2,SYSAPPL-MIB::sysApplMapInstallPkgIndex,Unsigned32,read-only,,current,,The value of this object identifies the installed software package for the application of which this process is a part. Provided that the process's 'parent' application can be determined, the value of this object is the same value as the sysApplInstallPkgIndex for the entry in the sysApplInstallPkgTable that corresponds to the installed application of which this process is a part. If, however, the 'parent' application cannot be determined, (for example the process is not part of a particular installed application), the value for this object is then '0', signifying that this process cannot be related back to an application, and in turn, an installed software package.
.1.3.6.1.2.1.54.2,SYSAPPL-MIB::sysApplNotifications,,,,,,
.1.3.6.1.2.1.54.3,SYSAPPL-MIB::sysApplConformance,,,,,,
.1.3.6.1.2.1.54.3.1,SYSAPPL-MIB::sysApplMIBCompliances,,,,,,
.1.3.6.1.2.1.54.3.1.1,SYSAPPL-MIB::sysApplMIBCompliance,,,,,,Describes the requirements for conformance to the System Application MIB
.1.3.6.1.2.1.54.3.2,SYSAPPL-MIB::sysApplMIBGroups,,,,,,
.1.3.6.1.2.1.54.3.2.1,SYSAPPL-MIB::sysApplInstalledGroup,,,,,,The system application installed group contains information about applications and their constituent components which have been installed on the host system.
.1.3.6.1.2.1.54.3.2.2,SYSAPPL-MIB::sysApplRunGroup,,,,,,The system application run group contains information about applications and associated elements which have run or are currently running on the host system.
.1.3.6.1.2.1.54.3.2.3,SYSAPPL-MIB::sysApplMapGroup,,,,,,The Map Group contains a single table, sysApplMapTable, that provides a backwards mapping for determining the invoked application, installed element, and installed application package given a known process identification number.
.1.3.6.1.2.1.55,IPV6-MIB::ipv6MIB,,,,,,The obsolete MIB module for entities implementing the IPv6 protocol. Use the IP-MIB or IP-FORWARD-MIB instead. Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.55.1,IPV6-MIB::ipv6MIBObjects,,,,,,
.1.3.6.1.2.1.55.1.1,IPV6-MIB::ipv6Forwarding,INTEGER,read-write,,obsolete,forwarding(1):notForwarding(2),The indication of whether this entity is acting as an IPv6 router in respect to the forwarding of datagrams received by, but not addressed to, this entity. IPv6 routers forward datagrams. IPv6 hosts do not (except those source-routed via the host). Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `wrongValue' response if a management station attempts to change this object to an inappropriate value. This object is obsoleted by IP-MIB::ipv6IpForwarding.
.1.3.6.1.2.1.55.1.2,IPV6-MIB::ipv6DefaultHopLimit,INTEGER,read-write,,obsolete,,The default value inserted into the Hop Limit field of the IPv6 header of datagrams originated at this entity, whenever a Hop Limit value is not supplied by the transport layer protocol. This object is obsoleted by IP-MIB::ipv6IpDefaultHopLimit.
.1.3.6.1.2.1.55.1.3,IPV6-MIB::ipv6Interfaces,Unsigned32,read-only,,obsolete,,The number of IPv6 interfaces (regardless of their current state) present on this system. This object is obsolete; there is no direct replacement, but its value can be derived from the number of rows in the IP-MIB::ipv6InterfaceTable.
.1.3.6.1.2.1.55.1.4,IPV6-MIB::ipv6IfTableLastChange,TimeTicks,read-only,,obsolete,,The value of sysUpTime at the time of the last insertion or removal of an entry in the ipv6IfTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value. This object is obsoleted by IP-MIB::ipv6InterfaceTableLastChange.
.1.3.6.1.2.1.55.1.5,IPV6-MIB::ipv6IfTable,,not-accessible,,obsolete,,The IPv6 Interfaces table contains information on the entity's internetwork-layer interfaces. An IPv6 interface constitutes a logical network layer attachment to the layer immediately below IPv6 including internet layer 'tunnels', such as tunnels over IPv4 or IPv6 itself. This table is obsoleted by IP-MIB::ipv6InterfaceTable.
.1.3.6.1.2.1.55.1.5.1,IPV6-MIB::ipv6IfEntry,,not-accessible,ipv6IfIndex,obsolete,,An interface entry containing objects about a particular IPv6 interface. This object is obsoleted by IP-MIB::ipv6InterfaceEntry.
.1.3.6.1.2.1.55.1.5.1.1,IPV6-MIB::ipv6IfIndex,Integer32,not-accessible,,obsolete,,A unique non-zero value identifying the particular IPv6 interface. This object is obsoleted. In the IP-MIB, interfaces are simply identified by IfIndex.
.1.3.6.1.2.1.55.1.5.1.2,IPV6-MIB::ipv6IfDescr,OCTET,read-write,,obsolete,,A textual string containing information about the interface. This string may be set by the network management system. This object is obsoleted by IF-MIB::ifDescr.
.1.3.6.1.2.1.55.1.5.1.3,IPV6-MIB::ipv6IfLowerLayer,OBJECT,read-only,,obsolete,,This object identifies the protocol layer over which this network interface operates. If this network interface operates over the data-link layer, then the value of this object refers to an instance of ifIndex [RFC1573]. If this network interface operates over an IPv4 interface, the value of this object refers to an instance of ipAdEntAddr [RFC1213]. If this network interface operates over another IPv6 interface, the value of this object refers to an instance of ipv6IfIndex. If this network interface is not currently operating over an active protocol layer, then the value of this object should be set to the OBJECT ID { 0 0 }. This object is obsolete. The IF-STACK-TABLE may be used to express relationships between interfaces.
.1.3.6.1.2.1.55.1.5.1.4,IPV6-MIB::ipv6IfEffectiveMtu,Unsigned32,read-only,,obsolete,,The size of the largest IPv6 packet which can be sent/received on the interface, specified in octets. This object is obsolete. The value of IF-MIB::ifMtu for the corresponding value of ifIndex represents the MTU of the interface.
.1.3.6.1.2.1.55.1.5.1.5,IPV6-MIB::ipv6IfReasmMaxSize,Unsigned32,read-only,,obsolete,,The size of the largest IPv6 datagram which this entity can re-assemble from incoming IPv6 fragmented datagrams received on this interface. This object is obsoleted by IP-MIB::ipv6InterfaceReasmMaxSize.
.1.3.6.1.2.1.55.1.5.1.6,IPV6-MIB::ipv6IfIdentifier,OCTET,read-write,,obsolete,,The Interface Identifier for this interface that is (at least) unique on the link this interface is attached to. The Interface Identifier is combined with an address prefix to form an interface address. By default, the Interface Identifier is autoconfigured according to the rules of the link type this interface is attached to. This object is obsoleted by IP-MIB::ipv6InterfaceIdentifier.
.1.3.6.1.2.1.55.1.5.1.7,IPV6-MIB::ipv6IfIdentifierLength,INTEGER,read-write,,obsolete,,The length of the Interface Identifier in bits. This object is obsolete. It can be derived from the length of IP-MIB::ipv6InterfaceIdentifier; Interface Identifiers that are not an even number of octets are not supported.
.1.3.6.1.2.1.55.1.5.1.8,IPV6-MIB::ipv6IfPhysicalAddress,OCTET,read-only,,obsolete,,The interface's physical address. For example, for an IPv6 interface attached to an 802.x link, this object normally contains a MAC address. Note that in some cases this address may differ from the address of the interface's protocol sub-layer. The interface's media-specific MIB must define the bit and byte ordering and the format of the value of this object. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length. This object is obsoleted by IF-MIB::ifPhysAddress.
.1.3.6.1.2.1.55.1.5.1.9,IPV6-MIB::ipv6IfAdminStatus,INTEGER,read-write,,obsolete,up(1):down(2),The desired state of the interface. When a managed system initializes, all IPv6 interfaces start with ipv6IfAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ipv6IfAdminStatus is then changed to the up(1) state (or remains in the down(2) state). This object is obsolete. IPv6 does not have a separate admin status; the admin status of the interface is represented by IF-MIB::ifAdminStatus.
.1.3.6.1.2.1.55.1.5.1.10,IPV6-MIB::ipv6IfOperStatus,INTEGER,read-only,,obsolete,up(1):down(2):noIfIdentifier(3):unknown(4):notPresent(5),The current operational state of the interface. The noIfIdentifier(3) state indicates that no valid Interface Identifier is assigned to the interface. This state usually indicates that the link-local interface address failed Duplicate Address Detection. If ipv6IfAdminStatus is down(2) then ipv6IfOperStatus should be down(2). If ipv6IfAdminStatus is changed to up(1) then ipv6IfOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should remain in the down(2) or noIfIdentifier(3) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(5) state if the interface has missing (typically, lower layer) components. This object is obsolete. IPv6 does not have a separate operational status; the operational status of the interface is represented by IF-MIB::ifOperStatus.
.1.3.6.1.2.1.55.1.5.1.11,IPV6-MIB::ipv6IfLastChange,TimeTicks,read-only,,obsolete,,The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. This object is obsolete. The last change of IF-MIB::ifOperStatus is represented by IF-MIB::ifLastChange.
.1.3.6.1.2.1.55.1.6,IPV6-MIB::ipv6IfStatsTable,,not-accessible,,obsolete,,IPv6 interface traffic statistics. This table is obsoleted by the IP-MIB::ipIfStatsTable.
.1.3.6.1.2.1.55.1.6.1,IPV6-MIB::ipv6IfStatsEntry,,not-accessible,,obsolete,,An interface statistics entry containing objects at a particular IPv6 interface. This object is obsoleted by the IP-MIB::ipIfStatsEntry.
.1.3.6.1.2.1.55.1.6.1.1,IPV6-MIB::ipv6IfStatsInReceives,Counter32,read-only,,obsolete,,The total number of input datagrams received by the interface, including those received in error. This object is obsoleted by IP-MIB::ipIfStatsHCInReceives.
.1.3.6.1.2.1.55.1.6.1.2,IPV6-MIB::ipv6IfStatsInHdrErrors,Counter32,read-only,,obsolete,,The number of input datagrams discarded due to errors in their IPv6 headers, including version number mismatch, other format errors, hop count exceeded, errors discovered in processing their IPv6 options, etc. This object is obsoleted by IP-MIB::ipIfStatsInHdrErrors.
.1.3.6.1.2.1.55.1.6.1.3,IPV6-MIB::ipv6IfStatsInTooBigErrors,Counter32,read-only,,obsolete,,The number of input datagrams that could not be forwarded because their size exceeded the link MTU of outgoing interface. This object is obsoleted. It was not replicated in the IP-MIB due to feedback that systems did not retain the incoming interface of a packet that failed fragmentation.
.1.3.6.1.2.1.55.1.6.1.4,IPV6-MIB::ipv6IfStatsInNoRoutes,Counter32,read-only,,obsolete,,The number of input datagrams discarded because no route could be found to transmit them to their destination. This object is obsoleted by IP-MIB::ipIfStatsInNoRoutes.
.1.3.6.1.2.1.55.1.6.1.5,IPV6-MIB::ipv6IfStatsInAddrErrors,Counter32,read-only,,obsolete,,The number of input datagrams discarded because the IPv6 address in their IPv6 header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., ::0) and unsupported addresses (e.g., addresses with unallocated prefixes). For entities which are not IPv6 routers and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. This object is obsoleted by IP-MIB::ipIfStatsInAddrErrors.
.1.3.6.1.2.1.55.1.6.1.6,IPV6-MIB::ipv6IfStatsInUnknownProtos,Counter32,read-only,,obsolete,,The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol. This counter is incremented at the interface to which these datagrams were addressed which might not be necessarily the input interface for some of the datagrams. This object is obsoleted by IP-MIB::ipIfStatsInUnknownProtos.
.1.3.6.1.2.1.55.1.6.1.7,IPV6-MIB::ipv6IfStatsInTruncatedPkts,Counter32,read-only,,obsolete,,The number of input datagrams discarded because datagram frame didn't carry enough data. This object is obsoleted by IP-MIB::ipIfStatsInTruncatedPkts.
.1.3.6.1.2.1.55.1.6.1.8,IPV6-MIB::ipv6IfStatsInDiscards,Counter32,read-only,,obsolete,,The number of input IPv6 datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly. This object is obsoleted by IP-MIB::ipIfStatsInDiscards.
.1.3.6.1.2.1.55.1.6.1.9,IPV6-MIB::ipv6IfStatsInDelivers,Counter32,read-only,,obsolete,,The total number of datagrams successfully delivered to IPv6 user-protocols (including ICMP). This counter is incremented at the interface to which these datagrams were addressed which might not be necessarily the input interface for some of the datagrams. This object is obsoleted by IP-MIB::ipIfStatsHCInDelivers.
.1.3.6.1.2.1.55.1.6.1.10,IPV6-MIB::ipv6IfStatsOutForwDatagrams,Counter32,read-only,,obsolete,,The number of output datagrams which this entity received and forwarded to their final destinations. In entities which do not act as IPv6 routers, this counter will include only those packets which were Source-Routed via this entity, and the Source-Route processing was successful. Note that for a successfully forwarded datagram the counter of the outgoing interface is incremented. This object is obsoleted by IP-MIB::ipIfStatsHCOutForwDatagrams.
.1.3.6.1.2.1.55.1.6.1.11,IPV6-MIB::ipv6IfStatsOutRequests,Counter32,read-only,,obsolete,,The total number of IPv6 datagrams which local IPv6 user-protocols (including ICMP) supplied to IPv6 in requests for transmission. Note that this counter does not include any datagrams counted in ipv6IfStatsOutForwDatagrams. This object is obsoleted by IP-MIB::ipIfStatsHCOutRequests.
.1.3.6.1.2.1.55.1.6.1.12,IPV6-MIB::ipv6IfStatsOutDiscards,Counter32,read-only,,obsolete,,The number of output IPv6 datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipv6IfStatsOutForwDatagrams if any such packets met this (discretionary) discard criterion. This object is obsoleted by IP-MIB::ipIfStatsOutDiscards.
.1.3.6.1.2.1.55.1.6.1.13,IPV6-MIB::ipv6IfStatsOutFragOKs,Counter32,read-only,,obsolete,,The number of IPv6 datagrams that have been successfully fragmented at this output interface. This object is obsoleted by IP-MIB::ipIfStatsOutFragOKs.
.1.3.6.1.2.1.55.1.6.1.14,IPV6-MIB::ipv6IfStatsOutFragFails,Counter32,read-only,,obsolete,,The number of IPv6 datagrams that have been discarded because they needed to be fragmented at this output interface but could not be. This object is obsoleted by IP-MIB::ipIfStatsOutFragFails.
.1.3.6.1.2.1.55.1.6.1.15,IPV6-MIB::ipv6IfStatsOutFragCreates,Counter32,read-only,,obsolete,,The number of output datagram fragments that have been generated as a result of fragmentation at this output interface. This object is obsoleted by IP-MIB::ipIfStatsOutFragCreates.
.1.3.6.1.2.1.55.1.6.1.16,IPV6-MIB::ipv6IfStatsReasmReqds,Counter32,read-only,,obsolete,,The number of IPv6 fragments received which needed to be reassembled at this interface. Note that this counter is incremented at the interface to which these fragments were addressed which might not be necessarily the input interface for some of the fragments. This object is obsoleted by IP-MIB::ipIfStatsReasmReqds.
.1.3.6.1.2.1.55.1.6.1.17,IPV6-MIB::ipv6IfStatsReasmOKs,Counter32,read-only,,obsolete,,The number of IPv6 datagrams successfully reassembled. Note that this counter is incremented at the interface to which these datagrams were addressed which might not be necessarily the input interface for some of the fragments. This object is obsoleted by IP-MIB::ipIfStatsReasmOKs.
.1.3.6.1.2.1.55.1.6.1.18,IPV6-MIB::ipv6IfStatsReasmFails,Counter32,read-only,,obsolete,,The number of failures detected by the IPv6 re- assembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IPv6 fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received. This counter is incremented at the interface to which these fragments were addressed which might not be necessarily the input interface for some of the fragments. This object is obsoleted by IP-MIB::ipIfStatsReasmFails.
.1.3.6.1.2.1.55.1.6.1.19,IPV6-MIB::ipv6IfStatsInMcastPkts,Counter32,read-only,,obsolete,,The number of multicast packets received by the interface This object is obsoleted by IP-MIB::ipIfStatsHCInMcastPkts.
.1.3.6.1.2.1.55.1.6.1.20,IPV6-MIB::ipv6IfStatsOutMcastPkts,Counter32,read-only,,obsolete,,The number of multicast packets transmitted by the interface This object is obsoleted by IP-MIB::ipIfStatsHCOutMcastPkts.
.1.3.6.1.2.1.55.1.7,IPV6-MIB::ipv6AddrPrefixTable,,not-accessible,,obsolete,,The list of IPv6 address prefixes of IPv6 interfaces. This table is obsoleted by IP-MIB::ipAddressPrefixTable.
.1.3.6.1.2.1.55.1.7.1,IPV6-MIB::ipv6AddrPrefixEntry,,not-accessible,ipv6IfIndex:ipv6AddrPrefix:ipv6AddrPrefixLength,obsolete,,An interface entry containing objects of a particular IPv6 address prefix. This entry is obsoleted by IP-MIB::ipAddressPrefixEntry.
.1.3.6.1.2.1.55.1.7.1.1,IPV6-MIB::ipv6AddrPrefix,OCTET,not-accessible,,obsolete,,The prefix associated with the this interface. This object is obsoleted by IP-MIB::ipAddressPrefixPrefix.
.1.3.6.1.2.1.55.1.7.1.2,IPV6-MIB::ipv6AddrPrefixLength,INTEGER,not-accessible,,obsolete,,The length of the prefix (in bits). This object is obsoleted by IP-MIB::ipAddressPrefixLength.
.1.3.6.1.2.1.55.1.7.1.3,IPV6-MIB::ipv6AddrPrefixOnLinkFlag,INTEGER,read-only,,obsolete,true(1):false(2),This object has the value 'true(1)', if this prefix can be used for on-link determination and the value 'false(2)' otherwise. This object is obsoleted by IP-MIB::ipAddressPrefixOnLinkFlag.
.1.3.6.1.2.1.55.1.7.1.4,IPV6-MIB::ipv6AddrPrefixAutonomousFlag,INTEGER,read-only,,obsolete,true(1):false(2),Autonomous address configuration flag. When true(1), indicates that this prefix can be used for autonomous address configuration (i.e. can be used to form a local interface address). If false(2), it is not used to autoconfigure a local interface address. This object is obsoleted by IP-MIB::ipAddressPrefixAutonomousFlag.
.1.3.6.1.2.1.55.1.7.1.5,IPV6-MIB::ipv6AddrPrefixAdvPreferredLifetime,Unsigned32,read-only,,obsolete,,It is the length of time in seconds that this prefix will remain preferred, i.e. time until deprecation. A value of 4,294,967,295 represents infinity. The address generated from a deprecated prefix should no longer be used as a source address in new communications, but packets received on such an interface are processed as expected. This object is obsoleted by IP-MIB::ipAddressPrefixAdvPreferredLifetime.
.1.3.6.1.2.1.55.1.7.1.6,IPV6-MIB::ipv6AddrPrefixAdvValidLifetime,Unsigned32,read-only,,obsolete,,It is the length of time in seconds that this prefix will remain valid, i.e. time until invalidation. A value of 4,294,967,295 represents infinity. The address generated from an invalidated prefix should not appear as the destination or source address of a packet. This object is obsoleted by IP-MIB::ipAddressPrefixAdvValidLifetime.
.1.3.6.1.2.1.55.1.8,IPV6-MIB::ipv6AddrTable,,not-accessible,,obsolete,,The table of addressing information relevant to this node's interface addresses. This table is obsoleted by IP-MIB::ipAddressTable.
.1.3.6.1.2.1.55.1.8.1,IPV6-MIB::ipv6AddrEntry,,not-accessible,ipv6IfIndex:ipv6AddrAddress,obsolete,,The addressing information for one of this node's interface addresses. This entry is obsoleted by IP-MIB::ipAddressEntry.
.1.3.6.1.2.1.55.1.8.1.1,IPV6-MIB::ipv6AddrAddress,OCTET,not-accessible,,obsolete,,The IPv6 address to which this entry's addressing information pertains. This object is obsoleted by IP-MIB::ipAddressAddr.
.1.3.6.1.2.1.55.1.8.1.2,IPV6-MIB::ipv6AddrPfxLength,INTEGER,read-only,,obsolete,,The length of the prefix (in bits) associated with the IPv6 address of this entry. This object is obsoleted by the IP-MIB::ipAddressPrefixLength in the row of the IP-MIB::ipAddressPrefixTable to which the IP-MIB::ipAddressPrefix points.
.1.3.6.1.2.1.55.1.8.1.3,IPV6-MIB::ipv6AddrType,INTEGER,read-only,,obsolete,stateless(1):stateful(2):unknown(3),The type of address. Note that 'stateless(1)' refers to an address that was statelessly autoconfigured; 'stateful(2)' refers to a address which was acquired by via a stateful protocol (e.g. DHCPv6, manual configuration). This object is obsoleted by IP-MIB::ipAddressOrigin.
.1.3.6.1.2.1.55.1.8.1.4,IPV6-MIB::ipv6AddrAnycastFlag,INTEGER,read-only,,obsolete,true(1):false(2),This object has the value 'true(1)', if this address is an anycast address and the value 'false(2)' otherwise. This object is obsoleted by a value of 'anycast(2)' in IP-MIB::ipAddressType.
.1.3.6.1.2.1.55.1.8.1.5,IPV6-MIB::ipv6AddrStatus,INTEGER,read-only,,obsolete,preferred(1):deprecated(2):invalid(3):inaccessible(4):unknown(5),Address status. The preferred(1) state indicates that this is a valid address that can appear as the destination or source address of a packet. The deprecated(2) state indicates that this is a valid but deprecated address that should no longer be used as a source address in new communications, but packets addressed to such an address are processed as expected. The invalid(3) state indicates that this is not valid address which should not appear as the destination or source address of a packet. The inaccessible(4) state indicates that the address is not accessible because the interface to which this address is assigned is not operational. This object is obsoleted by IP-MIB::ipAddressStatus.
.1.3.6.1.2.1.55.1.9,IPV6-MIB::ipv6RouteNumber,Gauge32,read-only,,obsolete,,The number of current ipv6RouteTable entries. This is primarily to avoid having to read the table in order to determine this number. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteNumber.
.1.3.6.1.2.1.55.1.10,IPV6-MIB::ipv6DiscardedRoutes,Counter32,read-only,,obsolete,,The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteDiscards.
.1.3.6.1.2.1.55.1.11,IPV6-MIB::ipv6RouteTable,,not-accessible,,obsolete,,IPv6 Routing table. This table contains an entry for each valid IPv6 unicast route that can be used for packet forwarding determination. This table is obsoleted by IP-FORWARD-MIB::inetCidrRouteTable.
.1.3.6.1.2.1.55.1.11.1,IPV6-MIB::ipv6RouteEntry,,not-accessible,ipv6RouteDest:ipv6RoutePfxLength:ipv6RouteIndex,obsolete,,A routing entry. This entry is obsoleted by IP-FORWARD-MIB::inetCidrRouteEntry.
.1.3.6.1.2.1.55.1.11.1.1,IPV6-MIB::ipv6RouteDest,OCTET,not-accessible,,obsolete,,The destination IPv6 address of this route. This object may not take a Multicast address value. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteDest.
.1.3.6.1.2.1.55.1.11.1.2,IPV6-MIB::ipv6RoutePfxLength,INTEGER,not-accessible,,obsolete,,Indicates the prefix length of the destination address. This object is obsoleted by IP-FORWARD-MIB::inetCidrRoutePfxLen.
.1.3.6.1.2.1.55.1.11.1.3,IPV6-MIB::ipv6RouteIndex,Unsigned32,not-accessible,,obsolete,,The value which uniquely identifies the route among the routes to the same network layer destination. The way this value is chosen is implementation specific but it must be unique for ipv6RouteDest/ipv6RoutePfxLength pair and remain constant for the life of the route. This object is obsoleted by IP-FORWARD-MIB::inetCidrRoutePolicy.
.1.3.6.1.2.1.55.1.11.1.4,IPV6-MIB::ipv6RouteIfIndex,Integer32,read-only,,obsolete,,The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ipv6IfIndex. For routes of the discard type this value can be zero. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteIfIndex.
.1.3.6.1.2.1.55.1.11.1.5,IPV6-MIB::ipv6RouteNextHop,OCTET,read-only,,obsolete,,On remote routes, the address of the next system en route; otherwise, ::0 ('00000000000000000000000000000000'H in ASN.1 string representation). This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteNextHop.
.1.3.6.1.2.1.55.1.11.1.6,IPV6-MIB::ipv6RouteType,INTEGER,read-only,,obsolete,other(1):discard(2):local(3):remote(4),The type of route. Note that 'local(3)' refers to a route for which the next hop is the final destination; 'remote(4)' refers to a route for which the next hop is not the final destination; 'discard(2)' refers to a route indicating that packets to destinations matching this route are to be discarded (sometimes called black-hole route). This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteType.
.1.3.6.1.2.1.55.1.11.1.7,IPV6-MIB::ipv6RouteProtocol,INTEGER,read-only,,obsolete,other(1):local(2):netmgmt(3):ndisc(4):rip(5):ospf(6):bgp(7):idrp(8):igrp(9),The routing mechanism via which this route was learned. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteProto.
.1.3.6.1.2.1.55.1.11.1.8,IPV6-MIB::ipv6RoutePolicy,Integer32,read-only,,obsolete,,The general set of conditions that would cause the selection of one multipath route (set of next hops for a given destination) is referred to as 'policy'. Unless the mechanism indicated by ipv6RouteProtocol specified otherwise, the policy specifier is the 8-bit Traffic Class field of the IPv6 packet header that is zero extended at the left to a 32-bit value. Protocols defining 'policy' otherwise must either define a set of values which are valid for this object or must implement an integer- instanced policy table for which this object's value acts as an index. This object is obsoleted by IP-FORWARD-MIB::inetCidrRoutePolicy.
.1.3.6.1.2.1.55.1.11.1.9,IPV6-MIB::ipv6RouteAge,Unsigned32,read-only,,obsolete,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteAge.
.1.3.6.1.2.1.55.1.11.1.10,IPV6-MIB::ipv6RouteNextHopRDI,Unsigned32,read-only,,obsolete,,The Routing Domain ID of the Next Hop. The semantics of this object are determined by the routing-protocol specified in the route's ipv6RouteProtocol value. When this object is unknown or not relevant its value should be set to zero. This object is obsolete, and it has no replacement. The Routing Domain ID concept did not catch on.
.1.3.6.1.2.1.55.1.11.1.11,IPV6-MIB::ipv6RouteMetric,Unsigned32,read-only,,obsolete,,The routing metric for this route. The semantics of this metric are determined by the routing protocol specified in the route's ipv6RouteProtocol value. When this is unknown or not relevant to the protocol indicated by ipv6RouteProtocol, the object value should be set to its maximum value (4,294,967,295). This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteMetric1.
.1.3.6.1.2.1.55.1.11.1.12,IPV6-MIB::ipv6RouteWeight,Unsigned32,read-only,,obsolete,,The system internal weight value for this route. The semantics of this value are determined by the implementation specific rules. Generally, within routes with the same ipv6RoutePolicy value, the lower the weight value the more preferred is the route. This object is obsoleted, and it has not been replaced.
.1.3.6.1.2.1.55.1.11.1.13,IPV6-MIB::ipv6RouteInfo,OBJECT,read-only,,obsolete,,A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipv6RouteProto value. If this information is not present, its value should be set to the OBJECT ID { 0 0 }, which is a syntactically valid object identifier, and any implementation conforming to ASN.1 and the Basic Encoding Rules must be able to generate and recognize this value. This object is obsoleted, and it has not been replaced.
.1.3.6.1.2.1.55.1.11.1.14,IPV6-MIB::ipv6RouteValid,INTEGER,read-write,,obsolete,true(1):false(2),Setting this object to the value 'false(2)' has the effect of invalidating the corresponding entry in the ipv6RouteTable object. That is, it effectively disassociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipv6RouteValid object. This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteStatus.
.1.3.6.1.2.1.55.1.12,IPV6-MIB::ipv6NetToMediaTable,,not-accessible,,obsolete,,The IPv6 Address Translation table used for mapping from IPv6 addresses to physical addresses. The IPv6 address translation table contain the Ipv6Address to `physical' address equivalencies. Some interfaces do not use translation tables for determining address equivalencies; if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. This table is obsoleted by IP-MIB::ipNetToPhysicalTable.
.1.3.6.1.2.1.55.1.12.1,IPV6-MIB::ipv6NetToMediaEntry,,not-accessible,ipv6IfIndex:ipv6NetToMediaNetAddress,obsolete,,Each entry contains one IPv6 address to `physical' address equivalence. This entry is obsoleted by IP-MIB::ipNetToPhysicalEntry.
.1.3.6.1.2.1.55.1.12.1.1,IPV6-MIB::ipv6NetToMediaNetAddress,OCTET,not-accessible,,obsolete,,The IPv6 Address corresponding to the media-dependent `physical' address. This object is obsoleted by IP-MIB::ipNetToPhysicalNetAddress.
.1.3.6.1.2.1.55.1.12.1.2,IPV6-MIB::ipv6NetToMediaPhysAddress,OCTET,read-only,,obsolete,,The media-dependent `physical' address. This object is obsoleted by IP-MIB::ipNetToPhysicalPhysAddress.
.1.3.6.1.2.1.55.1.12.1.3,IPV6-MIB::ipv6NetToMediaType,INTEGER,read-only,,obsolete,other(1):dynamic(2):static(3):local(4),The type of the mapping. The 'dynamic(2)' type indicates that the IPv6 address to physical addresses mapping has been dynamically resolved using the IPv6 Neighbor Discovery protocol. The static(3)' types indicates that the mapping has been statically configured. The local(4) indicates that the mapping is provided for an entity's own interface address. This object is obsoleted by IP-MIB::ipNetToPhysicalType.
.1.3.6.1.2.1.55.1.12.1.4,IPV6-MIB::ipv6IfNetToMediaState,INTEGER,read-only,,obsolete,reachable(1):stale(2):delay(3):probe(4):invalid(5):unknown(6),The Neighbor Unreachability Detection [RFC2461] state for the interface when the address mapping in this entry is used. This object is obsoleted by IP-MIB::ipNetToPhysicalState.
.1.3.6.1.2.1.55.1.12.1.5,IPV6-MIB::ipv6IfNetToMediaLastUpdated,TimeTicks,read-only,,obsolete,,The value of sysUpTime at the time this entry was last updated. If this entry was updated prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. This object is obsoleted by IP-MIB::ipNetToPhysicalLastUpdated.
.1.3.6.1.2.1.55.1.12.1.6,IPV6-MIB::ipv6NetToMediaValid,INTEGER,read-write,,obsolete,true(1):false(2),Setting this object to the value 'false(2)' has the effect of invalidating the corresponding entry in the ipv6NetToMediaTable. That is, it effectively disassociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipv6NetToMediaValid object. This object is obsoleted by IP-MIB::ipNetToPhysicalRowStatus.
.1.3.6.1.2.1.55.2,IPV6-MIB::ipv6Notifications,,,,,,
.1.3.6.1.2.1.55.2.0,IPV6-MIB::ipv6NotificationPrefix,,,,,,
.1.3.6.1.2.1.55.2.0.1,IPV6-MIB::ipv6IfStateChange,,,,,,An ipv6IfStateChange notification signifies that there has been a change in the state of an ipv6 interface. This notification should be generated when the interface's operational status transitions to or from the up(1) state. This object is obsoleted by IF-MIB::linkUp and IF-MIB::linkDown notifications.
.1.3.6.1.2.1.55.3,IPV6-MIB::ipv6Conformance,,,,,,
.1.3.6.1.2.1.55.3.1,IPV6-MIB::ipv6Compliances,,,,,,
.1.3.6.1.2.1.55.3.1.1,IPV6-MIB::ipv6Compliance,,,,,,The compliance statement for SNMPv2 entities which implement ipv6 MIB. This compliance statement is obsoleted by IP-MIB::ipMIBCompliance2.
.1.3.6.1.2.1.55.3.2,IPV6-MIB::ipv6Groups,,,,,,
.1.3.6.1.2.1.55.3.2.1,IPV6-MIB::ipv6GeneralGroup,,,,,,The IPv6 group of objects providing for basic management of IPv6 entities. This group is obsoleted by various groups in IP-MIB.
.1.3.6.1.2.1.55.3.2.2,IPV6-MIB::ipv6NotificationGroup,,,,,,The notification that an IPv6 entity is required to implement. This group is obsoleted by IF-MIB::linkUpDownNotificationsGroup.
.1.3.6.1.2.1.56,IPV6-ICMP-MIB::ipv6IcmpMIB,,,,,,The obsolete MIB module for entities implementing the ICMPv6. Use the IP-MIB instead. Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.56.1,IPV6-ICMP-MIB::ipv6IcmpMIBObjects,,,,,,
.1.3.6.1.2.1.56.1.1,IPV6-ICMP-MIB::ipv6IfIcmpTable,,not-accessible,,obsolete,,IPv6 ICMP statistics. This table contains statistics of ICMPv6 messages that are received and sourced by the entity. This table is obsolete because systems were found not to maintain these statistics per-interface.
.1.3.6.1.2.1.56.1.1.1,IPV6-ICMP-MIB::ipv6IfIcmpEntry,,not-accessible,,obsolete,,An ICMPv6 statistics entry containing objects at a particular IPv6 interface. Note that a receiving interface is the interface to which a given ICMPv6 message is addressed which may not be necessarily the input interface for the message. Similarly, the sending interface is the interface that sources a given ICMP message which is usually but not necessarily the output interface for the message. This table is obsolete because systems were found not to maintain these statistics per-interface.
.1.3.6.1.2.1.56.1.1.1.1,IPV6-ICMP-MIB::ipv6IfIcmpInMsgs,Counter32,read-only,,obsolete,,The total number of ICMP messages received by the interface which includes all those counted by ipv6IfIcmpInErrors. Note that this interface is the interface to which the ICMP messages were addressed which may not be necessarily the input interface for the messages. This object has been obsoleted by IP-MIB::icmpStatsInMsgs.
.1.3.6.1.2.1.56.1.1.1.2,IPV6-ICMP-MIB::ipv6IfIcmpInErrors,Counter32,read-only,,obsolete,,The number of ICMP messages which the interface received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.). This object has been obsoleted by IP-MIB::icmpStatsInErrors.
.1.3.6.1.2.1.56.1.1.1.3,IPV6-ICMP-MIB::ipv6IfIcmpInDestUnreachs,Counter32,read-only,,obsolete,,The number of ICMP Destination Unreachable messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.4,IPV6-ICMP-MIB::ipv6IfIcmpInAdminProhibs,Counter32,read-only,,obsolete,,The number of ICMP destination unreachable/communication administratively prohibited messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.5,IPV6-ICMP-MIB::ipv6IfIcmpInTimeExcds,Counter32,read-only,,obsolete,,The number of ICMP Time Exceeded messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.6,IPV6-ICMP-MIB::ipv6IfIcmpInParmProblems,Counter32,read-only,,obsolete,,The number of ICMP Parameter Problem messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.7,IPV6-ICMP-MIB::ipv6IfIcmpInPktTooBigs,Counter32,read-only,,obsolete,,The number of ICMP Packet Too Big messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.8,IPV6-ICMP-MIB::ipv6IfIcmpInEchos,Counter32,read-only,,obsolete,,The number of ICMP Echo (request) messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.9,IPV6-ICMP-MIB::ipv6IfIcmpInEchoReplies,Counter32,read-only,,obsolete,,The number of ICMP Echo Reply messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.10,IPV6-ICMP-MIB::ipv6IfIcmpInRouterSolicits,Counter32,read-only,,obsolete,,The number of ICMP Router Solicit messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.11,IPV6-ICMP-MIB::ipv6IfIcmpInRouterAdvertisements,Counter32,read-only,,obsolete,,The number of ICMP Router Advertisement messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.12,IPV6-ICMP-MIB::ipv6IfIcmpInNeighborSolicits,Counter32,read-only,,obsolete,,The number of ICMP Neighbor Solicit messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.13,IPV6-ICMP-MIB::ipv6IfIcmpInNeighborAdvertisements,Counter32,read-only,,obsolete,,The number of ICMP Neighbor Advertisement messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.14,IPV6-ICMP-MIB::ipv6IfIcmpInRedirects,Counter32,read-only,,obsolete,,The number of Redirect messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.15,IPV6-ICMP-MIB::ipv6IfIcmpInGroupMembQueries,Counter32,read-only,,obsolete,,The number of ICMPv6 Group Membership Query messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.16,IPV6-ICMP-MIB::ipv6IfIcmpInGroupMembResponses,Counter32,read-only,,obsolete,,The number of ICMPv6 Group Membership Response messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.17,IPV6-ICMP-MIB::ipv6IfIcmpInGroupMembReductions,Counter32,read-only,,obsolete,,The number of ICMPv6 Group Membership Reduction messages received by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsInPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.18,IPV6-ICMP-MIB::ipv6IfIcmpOutMsgs,Counter32,read-only,,obsolete,,The total number of ICMP messages which this interface attempted to send. Note that this counter includes all those counted by icmpOutErrors. This object has been obsoleted by IP-MIB::icmpStatsOutMsgs.
.1.3.6.1.2.1.56.1.1.1.19,IPV6-ICMP-MIB::ipv6IfIcmpOutErrors,Counter32,read-only,,obsolete,,The number of ICMP messages which this interface did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IPv6 to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value. This object has been obsoleted by IP-MIB::icmpStatsOutErrors.
.1.3.6.1.2.1.56.1.1.1.20,IPV6-ICMP-MIB::ipv6IfIcmpOutDestUnreachs,Counter32,read-only,,obsolete,,The number of ICMP Destination Unreachable messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.21,IPV6-ICMP-MIB::ipv6IfIcmpOutAdminProhibs,Counter32,read-only,,obsolete,,Number of ICMP dest unreachable/communication administratively prohibited messages sent. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.22,IPV6-ICMP-MIB::ipv6IfIcmpOutTimeExcds,Counter32,read-only,,obsolete,,The number of ICMP Time Exceeded messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.23,IPV6-ICMP-MIB::ipv6IfIcmpOutParmProblems,Counter32,read-only,,obsolete,,The number of ICMP Parameter Problem messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.24,IPV6-ICMP-MIB::ipv6IfIcmpOutPktTooBigs,Counter32,read-only,,obsolete,,The number of ICMP Packet Too Big messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.25,IPV6-ICMP-MIB::ipv6IfIcmpOutEchos,Counter32,read-only,,obsolete,,The number of ICMP Echo (request) messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.26,IPV6-ICMP-MIB::ipv6IfIcmpOutEchoReplies,Counter32,read-only,,obsolete,,The number of ICMP Echo Reply messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.27,IPV6-ICMP-MIB::ipv6IfIcmpOutRouterSolicits,Counter32,read-only,,obsolete,,The number of ICMP Router Solicitation messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.28,IPV6-ICMP-MIB::ipv6IfIcmpOutRouterAdvertisements,Counter32,read-only,,obsolete,,The number of ICMP Router Advertisement messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.29,IPV6-ICMP-MIB::ipv6IfIcmpOutNeighborSolicits,Counter32,read-only,,obsolete,,The number of ICMP Neighbor Solicitation messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.30,IPV6-ICMP-MIB::ipv6IfIcmpOutNeighborAdvertisements,Counter32,read-only,,obsolete,,The number of ICMP Neighbor Advertisement messages sent by the interface. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.31,IPV6-ICMP-MIB::ipv6IfIcmpOutRedirects,Counter32,read-only,,obsolete,,The number of Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.32,IPV6-ICMP-MIB::ipv6IfIcmpOutGroupMembQueries,Counter32,read-only,,obsolete,,The number of ICMPv6 Group Membership Query messages sent. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.33,IPV6-ICMP-MIB::ipv6IfIcmpOutGroupMembResponses,Counter32,read-only,,obsolete,,The number of ICMPv6 Group Membership Response messages sent. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.1.1.1.34,IPV6-ICMP-MIB::ipv6IfIcmpOutGroupMembReductions,Counter32,read-only,,obsolete,,The number of ICMPv6 Group Membership Reduction messages sent. This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts in the row corresponding to this message type.
.1.3.6.1.2.1.56.2,IPV6-ICMP-MIB::ipv6IcmpConformance,,,,,,
.1.3.6.1.2.1.56.2.1,IPV6-ICMP-MIB::ipv6IcmpCompliances,,,,,,
.1.3.6.1.2.1.56.2.1.1,IPV6-ICMP-MIB::ipv6IcmpCompliance,,,,,,The compliance statement for SNMPv2 entities which implement ICMPv6. This compliance statement has been obsoleted by IP-MIB::ipMIBCompliance2.
.1.3.6.1.2.1.56.2.2,IPV6-ICMP-MIB::ipv6IcmpGroups,,,,,,
.1.3.6.1.2.1.56.2.2.1,IPV6-ICMP-MIB::ipv6IcmpGroup,,,,,,The ICMPv6 group of objects providing information specific to ICMPv6. This group has been obsoleted by IP-MIB::icmpStatsGroup.
.1.3.6.1.2.1.57,IPATM-IPMC-MIB::marsMIB,,,,,,This module defines a portion of the managed information base (MIB) for managing classical IP multicast address resolution server (MARS) and related entities as described in the RFC2022. This MIB is meant to be used in conjunction with the ATM-MIB (RFC1695), MIB-II (RFC1213), and optionally the IF-MIB (RFC1573). 
.1.3.6.1.2.1.57.0,IPATM-IPMC-MIB::marsTrapInfo,,,,,,
.1.3.6.1.2.1.57.0.1,IPATM-IPMC-MIB::marsFaultTrap,,,,,,This trap/inform is sent to the manager whenever there is a fault condition occurred on a MARS.
.1.3.6.1.2.1.57.1,IPATM-IPMC-MIB::marsClientObjects,,,,,,
.1.3.6.1.2.1.57.1.1,IPATM-IPMC-MIB::marsClientTable,,not-accessible,,current,,The objects defined in this table are used for the management of MARS clients, ATM attached endpoints.
.1.3.6.1.2.1.57.1.1.1,IPATM-IPMC-MIB::marsClientEntry,,not-accessible,ipAdEntAddr:marsClientIndex,current,,Each entry contains a MARS client and its associated attributes. An entry in the marsClientTable has a corresponding entry in the ipAddrTable defined in RFC1213. Association between the ipAddrTable and the marsClientTable is made through the index, ipAdEntAddr.
.1.3.6.1.2.1.57.1.1.1.1,IPATM-IPMC-MIB::marsClientIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the MARS MarsClientTable.
.1.3.6.1.2.1.57.1.1.1.2,IPATM-IPMC-MIB::marsClientAddr,OCTET,read-create,,current,,The ATM address associated with the ATM Client.
.1.3.6.1.2.1.57.1.1.1.3,IPATM-IPMC-MIB::marsClientDefaultMarsAddr,OCTET,read-create,,current,,The default MARS ATM address which is needed to setup the initial signalling path between a MARS client and its associated MARS.
.1.3.6.1.2.1.57.1.1.1.4,IPATM-IPMC-MIB::marsClientHsn,Unsigned32,read-create,,current,,The cluster membership own 32 bit Host Sequence Number. When a new cluster member starts up, it is initialized to zero. When the cluster member sends the MARS_JOIN to register, the HSN will be correctly set to the current cluster sequence number (CSN) when the Client receives the copy of its MARS_JOIN from the MARS. It is is used to track the MARS sequence number.
.1.3.6.1.2.1.57.1.1.1.5,IPATM-IPMC-MIB::marsClientRegistration,INTEGER,read-create,,current,notRegistered(1):registering(2):registered(3):reRegisteringFault(4):reRegisteringRedirMap(5),An indication with regards to the registration status of this client. The registration codes of 'notRegistered (1)', 'registered (2)', and registered (3) are self-explanatory. The 'reRegisteringFault (4)' indicates the client is in the process of re-registering with a MARS due to some fault conditions. The 'reRegisteringRedMap (5)' status code shows that client is re-registering because it has received a MARS_REDIRECT_MAP message and was told to register with a different MARS from the current MARS.
.1.3.6.1.2.1.57.1.1.1.6,IPATM-IPMC-MIB::marsClientCmi,INTEGER,read-create,,current,,16 bit Cluster member identifier (CMI) assigned by the MARS which uniquely identifies each endpoint attached to the cluster. The value becomes valid after the 'marsClientRegistration' is set to the value of 'registered (1)'.
.1.3.6.1.2.1.57.1.1.1.7,IPATM-IPMC-MIB::marsClientDefaultMtu,INTEGER,read-create,,current,,The default maximum transmission unit (MTU) used for this cluster. Note that the actual size used for a VC between two members of the cluster may be negotiated during connection setup and may be different than this value. Default value = 9180 bytes.
.1.3.6.1.2.1.57.1.1.1.8,IPATM-IPMC-MIB::marsClientFailureTimer,INTEGER,read-create,,current,,A timer used to flag the failure of last MARS_MULTI to arrive. Default value = 10 seconds (recommended).
.1.3.6.1.2.1.57.1.1.1.9,IPATM-IPMC-MIB::marsClientRetranDelayTimer,INTEGER,read-create,,current,,The delay timer for sending out new MARS_REQUEST for the group after the client learned that there is no other group in the cluster. The timer must be set between 5 and 10 seconds inclusive.
.1.3.6.1.2.1.57.1.1.1.10,IPATM-IPMC-MIB::marsClientRdmMulReqAddRetrTimer,INTEGER,read-create,,current,,The initial random L_MULTI_RQ/ADD retransmit timer which can be set between 5 and 10 seconds inclusive.
.1.3.6.1.2.1.57.1.1.1.11,IPATM-IPMC-MIB::marsClientRdmVcRevalidateTimer,INTEGER,read-create,,current,,The random time to set VC_revalidate flag. The timer value ranges between 1 and 10 seconds inclusive.
.1.3.6.1.2.1.57.1.1.1.12,IPATM-IPMC-MIB::marsClientJoinLeaveRetrInterval,INTEGER,read-create,,current,,MARS_JOIN/LEAVE retransmit interval. The minimum and recommended values are 5 and 10 seconds, respectively.
.1.3.6.1.2.1.57.1.1.1.13,IPATM-IPMC-MIB::marsClientJoinLeaveRetrLimit,INTEGER,read-create,,current,,MARS_JOIN/LEAVE retransmit limit. The maximum value is 5.
.1.3.6.1.2.1.57.1.1.1.14,IPATM-IPMC-MIB::marsClientRegWithMarsRdmTimer,INTEGER,read-create,,current,,Random time to register with MARS.
.1.3.6.1.2.1.57.1.1.1.15,IPATM-IPMC-MIB::marsClientForceWaitTimer,INTEGER,read-create,,current,,Force wait if MARS re-registration is looping. The minimum value is 1 minute.
.1.3.6.1.2.1.57.1.1.1.16,IPATM-IPMC-MIB::marsClientLmtToMissRedirMapTimer,INTEGER,read-create,,current,,Timer limit for client to miss MARS_REDIRECT_MAPS.
.1.3.6.1.2.1.57.1.1.1.17,IPATM-IPMC-MIB::marsClientIdleTimer,INTEGER,read-create,,current,,The configurable inactivity timer associated with a client. When a VC is created at this client, it gets the idle timer value from this configurable timer. The minimum suggested value is 1 minute and the recommended default value is 20 minutes.
.1.3.6.1.2.1.57.1.1.1.18,IPATM-IPMC-MIB::marsClientRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all corresponding columns in the row of this table are appropriately configured and until the agent has also created a corresponding row in the marsClientStatTable. When this object has a value of 'active', the following columnar objects can not be modified: marsClientDefaultMarsAddr, marsClientHsn, marsClientRegstration, marsClientCmi, marsClientDefaultMtu while other objects in this conceptual row can be modified irrespective of the value of this object. Deletion of this row is allowed regardless of whether or not a row in any associated tables (i.e., marsClientVcTable) still exists or is in use. Once this row is deleted, it is recommended that the agent or the SNMP management station (if possible) through the set command deletes any stale rows that are associated with this row.
.1.3.6.1.2.1.57.1.2,IPATM-IPMC-MIB::marsClientMcGrpTable,,not-accessible,,current,,This table contains a list of IP multicast group address blocks associated with a MARS client. Entries in this table are used by the client that needs to receive or transmit packets from/to the specified range of multicast addresses. Each row can be created or deleted via configuration.
.1.3.6.1.2.1.57.1.2.1,IPATM-IPMC-MIB::marsClientMcGrpEntry,,not-accessible,ipAdEntAddr:marsClientIndex:marsClientMcMinGrpAddr:marsClientMcMaxGrpAddr,current,,Each entry represents a consecutive block of multicast group addresses.
.1.3.6.1.2.1.57.1.2.1.1,IPATM-IPMC-MIB::marsClientMcMinGrpAddr,IpAddress,not-accessible,,current,,Minimum multicast group address - the min and max multicast forms multi-group block. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that this block contains a single group address.
.1.3.6.1.2.1.57.1.2.1.2,IPATM-IPMC-MIB::marsClientMcMaxGrpAddr,IpAddress,not-accessible,,current,,Maximum multicast group address - the min and max multicast forms a multi-group block. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that this block contains a single group address.
.1.3.6.1.2.1.57.1.2.1.3,IPATM-IPMC-MIB::marsClientMcGrpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create or delete a row in this table. Since other objects in this row are not-accessible 'index-objects', the value of this object has no effect on whether those objects in this conceptual row can be modified.
.1.3.6.1.2.1.57.1.3,IPATM-IPMC-MIB::marsClientBackupMarsTable,,not-accessible,,current,,This table contains a list of backup MARS addresses that a client can connect to in case of failure for connecting to the primary server. The list of addresses is in descending order of preference. It should be noted that the backup list provided by the MARS to the client via the MARS_REDIRECT_MAP message has a higher preference than addresses that are manually configured into the client. When such a list is received from the MARS, this information should be inserted at the top of the list. Each row can be created or deleted via configuration.
.1.3.6.1.2.1.57.1.3.1,IPATM-IPMC-MIB::marsClientBackupMarsEntry,,not-accessible,ipAdEntAddr:marsClientIndex:marsClientBackupMarsPriority:marsClientBackupMarsAddr,current,,Each entry represents an ATM address of a backup MARS.
.1.3.6.1.2.1.57.1.3.1.1,IPATM-IPMC-MIB::marsClientBackupMarsPriority,Unsigned32,not-accessible,,current,,The priority associated with a backup MARS. A lower priority value inidcates a higher preference.
.1.3.6.1.2.1.57.1.3.1.2,IPATM-IPMC-MIB::marsClientBackupMarsAddr,OCTET,not-accessible,,current,,The ATM address associated with a backup MARS.
.1.3.6.1.2.1.57.1.3.1.3,IPATM-IPMC-MIB::marsClientBackupMarsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create or delete a row in this table. Since other objects in this row are not-accessible 'index-objects', the value of this object has no effect on whether those objects in this conceptual row can be modified.
.1.3.6.1.2.1.57.1.4,IPATM-IPMC-MIB::marsClientVcTable,,not-accessible,,current,,This table contains information about open virtual circuits (VCs) that a client has. For point to point circuit, each entry represents a single VC connection between this client ATM address to another party ATM address. In the case of point to multipoint connection where a single source address is associated with multiple destinations, several entries are used to represent the relationship. An example of point to multi-point VC represented in a table is shown below. Client VPI/VCI Grp Addr1/Addr2 Part Addr 1 0,1 g1,g2 p1 1 0,1 g1,g2 p2 1 0,1 g1,g2 p3 Note: This table assumes the IP multicast address groups (min, max) defined in each entry are always consecutive. In the case of that a client receives a JOIN/LEAVE with mars$flag.punched set, each pair of the IP groups will first be broken into several pairs of consecutive IP groups before each entry row corresponding to a pair of IP group is created.
.1.3.6.1.2.1.57.1.4.1,IPATM-IPMC-MIB::marsClientVcEntry,,not-accessible,ipAdEntAddr:marsClientIndex:marsClientVcVpi:marsClientVcVci:marsClientVcMinGrpAddr:marsClientVcMaxGrpAddr:marsClientVcPartyAddr,current,,The objects contained in the entry are VC related attributes such as VC signalling type, control VC type, idle timer, negotiated MTU size, etc.
.1.3.6.1.2.1.57.1.4.1.1,IPATM-IPMC-MIB::marsClientVcVpi,INTEGER,not-accessible,,current,,The value of virtual path identifier (VPI). Since a VPI can be numbered 0, this sub-index can take a value of 0.
.1.3.6.1.2.1.57.1.4.1.2,IPATM-IPMC-MIB::marsClientVcVci,INTEGER,not-accessible,,current,,The value of virtual circuit identifier (VCI). Since a VCI can be numbered 0, this sub-index can take a value of 0.
.1.3.6.1.2.1.57.1.4.1.3,IPATM-IPMC-MIB::marsClientVcMinGrpAddr,IpAddress,not-accessible,,current,,Minimum IP multicast group address - the min and max multicast forms a multi-group consecutive block which is associated with a table entry. if the MinGrpAddr and MaxGrpAddr are the same, it indicates that the size of multi-group block is 1, a single IP group.
.1.3.6.1.2.1.57.1.4.1.4,IPATM-IPMC-MIB::marsClientVcMaxGrpAddr,IpAddress,not-accessible,,current,,Maximum IP multicast group address - the min and max multicast forms a multi-group consecutive block which is associated with a table entry. if the MinGrpAddr and MaxGrpAddr are the same, it indicates that the size of multi-group block is 1, a single IP group.
.1.3.6.1.2.1.57.1.4.1.5,IPATM-IPMC-MIB::marsClientVcPartyAddr,OCTET,not-accessible,,current,,An ATM party address in which this VC is linked. The party type is identified by the marsClientVcPartyAddrType.
.1.3.6.1.2.1.57.1.4.1.6,IPATM-IPMC-MIB::marsClientVcPartyAddrType,INTEGER,read-create,,current,called(1):calling(2),The party type is associated with the party address. The 'called (1)' indicates that the party address is a destination address which implies that VC is originated from this client. The 'calling (2)' indicates the VC was initiated externally to this client. In this case, the party address is the source address.
.1.3.6.1.2.1.57.1.4.1.7,IPATM-IPMC-MIB::marsClientVcType,INTEGER,read-create,,current,pvc(1):svc(2),Circuit Connection type: permanent virtual circuit or switched virtual circuit.
.1.3.6.1.2.1.57.1.4.1.8,IPATM-IPMC-MIB::marsClientVcCtrlType,INTEGER,read-create,,current,pointToPointVC(1):clusterControlVC(2):pointToMultiPointVC(3),Control VC type used to specify a particular connection. pointToPointVC (1): used by the ATM Clients for the registration and queries. This VC or the initial signalling path is set up from the source Client to a MARS. It is bi-directional. clusterControlVC (2): used by a MARS to issue asynchronous updates to an ATM Client. This VC is established from the MARS to the ATM Client. pointToMultiPointVC (3): used by the client to transfer multicast data packets from layer 3. This VC is established from the source ATM Client to a destination ATM endpoint which can be a multicast group member or an MCS. The destination endpoint was obtained from the MARS.
.1.3.6.1.2.1.57.1.4.1.9,IPATM-IPMC-MIB::marsClientVcIdleTimer,INTEGER,read-create,,current,,The idle timer associated with this VC. The minimum suggested value is 1 minute and the recommended default value is 20 minutes.
.1.3.6.1.2.1.57.1.4.1.10,IPATM-IPMC-MIB::marsClientVcRevalidate,INTEGER,read-create,,current,true(1):false(2),A flag associated with an open and active multipoint VC. It is checked every time a packet is queued for transmission on that VC. The object has the value of true (1) if revalidate is required and the value false (2) otherwise.
.1.3.6.1.2.1.57.1.4.1.11,IPATM-IPMC-MIB::marsClientVcEncapsType,INTEGER,read-create,,current,other(1):llcSnap(2),The encapsulation type used when communicating over this VC.
.1.3.6.1.2.1.57.1.4.1.12,IPATM-IPMC-MIB::marsClientVcNegotiatedMtu,INTEGER,read-create,,current,,The negotiated MTU when communicating over this VC.
.1.3.6.1.2.1.57.1.4.1.13,IPATM-IPMC-MIB::marsClientVcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all corresponding columns in the row of this table are appropriately configured. While objects: marsClientVcIdleTimer and marsClientVcRevalidate in this conceptual row can be modified irrespective of the value of this object, all other objects in the row can not be modified when this object has a value of 'active'. It is possible for an SNMP management station to set the row to 'notInService' and modify the entry and then set it back to 'active' with the following exception. That is, rows for which the corresponding instance of marsClientVcType has a value of 'svc' can not be modified or deleted.
.1.3.6.1.2.1.57.1.5,IPATM-IPMC-MIB::marsClientStatTable,,not-accessible,,current,,The table contains statistics collected at MARS clients.
.1.3.6.1.2.1.57.1.5.1,IPATM-IPMC-MIB::marsClientStatEntry,,not-accessible,ipAdEntAddr:marsClientIndex,current,,Each entry contains statistics collected at one MARS client.
.1.3.6.1.2.1.57.1.5.1.1,IPATM-IPMC-MIB::marsClientStatTxReqMsgs,Counter32,read-only,,current,,Total number of MARS_REQUEST messages transmitted from a client.
.1.3.6.1.2.1.57.1.5.1.2,IPATM-IPMC-MIB::marsClientStatTxJoinMsgs,Counter32,read-only,,current,,Total number of MARS_JOIN messages transmitted from a client.
.1.3.6.1.2.1.57.1.5.1.3,IPATM-IPMC-MIB::marsClientStatTxLeaveMsgs,Counter32,read-only,,current,,Total number of MARS_LEAVE messages transmitted from a client.
.1.3.6.1.2.1.57.1.5.1.4,IPATM-IPMC-MIB::marsClientStatTxGrpLstReqMsgs,Counter32,read-only,,current,,Total number of MARS_GROUPLIST_REQUEST messages transmitted from a client.
.1.3.6.1.2.1.57.1.5.1.5,IPATM-IPMC-MIB::marsClientStatRxJoinMsgs,Counter32,read-only,,current,,Total number of MARS_JOIN messages received by a client.
.1.3.6.1.2.1.57.1.5.1.6,IPATM-IPMC-MIB::marsClientStatRxLeaveMsgs,Counter32,read-only,,current,,Total number of MARS_LEAVE messages received by a client.
.1.3.6.1.2.1.57.1.5.1.7,IPATM-IPMC-MIB::marsClientStatRxMultiMsgs,Counter32,read-only,,current,,Total number of MARS_MULTI messages received by a client.
.1.3.6.1.2.1.57.1.5.1.8,IPATM-IPMC-MIB::marsClientStatRxNakMsgs,Counter32,read-only,,current,,Total number of MARS_NAK messages received by a client.
.1.3.6.1.2.1.57.1.5.1.9,IPATM-IPMC-MIB::marsClientStatRxMigrateMsgs,Counter32,read-only,,current,,Total number of MARS_MIGRATE messages received by a client.
.1.3.6.1.2.1.57.1.5.1.10,IPATM-IPMC-MIB::marsClientStatRxGrpLstRplyMsgs,Counter32,read-only,,current,,Total number of MARS_GROUPLIST_REPLY messages received by a client.
.1.3.6.1.2.1.57.1.5.1.11,IPATM-IPMC-MIB::marsClientStatFailMultiMsgs,Counter32,read-only,,current,,Total number of timeouts occurred indicating failure of the last MARS_MULTI to arrive.
.1.3.6.1.2.1.57.2,IPATM-IPMC-MIB::marsObjects,,,,,,
.1.3.6.1.2.1.57.2.1,IPATM-IPMC-MIB::marsTable,,not-accessible,,current,,The objects defined in this table are used for the management of MARS servers.
.1.3.6.1.2.1.57.2.1.1,IPATM-IPMC-MIB::marsEntry,,not-accessible,marsIndex:marsIfIndex,current,,Each entry contains a MARS and its associated attributes.
.1.3.6.1.2.1.57.2.1.1.1,IPATM-IPMC-MIB::marsIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the MARS table.
.1.3.6.1.2.1.57.2.1.1.2,IPATM-IPMC-MIB::marsIfIndex,Integer32,not-accessible,,current,,The ifIndex of the interface that the MARS is associated with.
.1.3.6.1.2.1.57.2.1.1.3,IPATM-IPMC-MIB::marsAddr,OCTET,read-create,,current,,The ATM address associated with the MARS.
.1.3.6.1.2.1.57.2.1.1.4,IPATM-IPMC-MIB::marsLocal,INTEGER,read-create,,current,true(1):false(2),A flag associated with a MARS entry. The object has the value of true (1) if the MARS whose interface is local to the machine that implements this MIB; otherwise the object has the value of false (2).
.1.3.6.1.2.1.57.2.1.1.5,IPATM-IPMC-MIB::marsServStatus,INTEGER,read-create,,current,active(1):inactive(2):faulted(3),The current status of MARS.
.1.3.6.1.2.1.57.2.1.1.6,IPATM-IPMC-MIB::marsServType,INTEGER,read-create,,current,primary(1):backup(2),Types of MARS servers: primary or backup.
.1.3.6.1.2.1.57.2.1.1.7,IPATM-IPMC-MIB::marsServPriority,Unsigned32,read-create,,current,,Priority associated with a backup MARS server. A backup MARS server with lower priority value indicates a higher preference than other backup MARS servers to be used as the MARS server when the primary server fails.
.1.3.6.1.2.1.57.2.1.1.8,IPATM-IPMC-MIB::marsRedirMapMsgTimer,INTEGER,read-create,,current,,Periodic interval on which a multi-part MARS_REDIRECT_MAP is sent from this MARS.
.1.3.6.1.2.1.57.2.1.1.9,IPATM-IPMC-MIB::marsCsn,Unsigned32,read-create,,current,,Current cluster sequence number (CSN) which is global within the context of a given protocol. The CSN is incremented by the MARS on every transmission of a message on ClusterControlVC. A cluster member uses the CSN to track the message loss on ClusterControlVC or to monitor a membership change.
.1.3.6.1.2.1.57.2.1.1.10,IPATM-IPMC-MIB::marsSsn,Unsigned32,read-create,,current,,Current server sequence number (SSN) which is global within the context of a given protocol. The SSN is incremented by the MARS on every transmission of a message on ServerControlVC. A MCS uses the SSN to track the message loss on ServerControlVC or to monitor a membership change.
.1.3.6.1.2.1.57.2.1.1.11,IPATM-IPMC-MIB::marsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all corresponding columns in the row of this table are appropriately configured and until the agent has also created a corresponding row in the marsStatTable. When this object has a value of 'active', the following columnar objects can not be modified: marsAddr, marsAddrLocal, marsServStatus, marsServType, marsCsn, marsSsn while other objects in this conceptual row can be modified irrespective of the value of this object. Deletion of this row is allowed regardless of whether or not a row in any associated tables (i.e., marsVcTable) still exists or is in use. Once this row is deleted, it is recommended that the agent or the SNMP management station (if possible) through the set command deletes any stale rows that are associated with this row.
.1.3.6.1.2.1.57.2.2,IPATM-IPMC-MIB::marsMcGrpTable,,not-accessible,,current,,This table contains a list of IP multicast address blocks associated with a MARS. Entries in this table are used by the MARS host map table and the server map table. They should be created prior to being referenced as indices by those tables. Each row can be created or deleted via configuration.
.1.3.6.1.2.1.57.2.2.1,IPATM-IPMC-MIB::marsMcGrpEntry,,not-accessible,marsIndex:marsIfIndex:marsMcMinGrpAddr:marsMcMaxGrpAddr,current,,Each entry represents a consecutive block of multicast group addresses.
.1.3.6.1.2.1.57.2.2.1.1,IPATM-IPMC-MIB::marsMcMinGrpAddr,IpAddress,not-accessible,,current,,Minimum multicast group address - the min and max multicast forms multi-group block. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that this block contains a single group address.
.1.3.6.1.2.1.57.2.2.1.2,IPATM-IPMC-MIB::marsMcMaxGrpAddr,IpAddress,not-accessible,,current,,Maximum multicast group address - the min and max multicast forms a multi-group block. If The MinGrpAddr and MaxGrpAddr are the same, it indicates that this block contains a single group address.
.1.3.6.1.2.1.57.2.2.1.3,IPATM-IPMC-MIB::marsMcGrpAddrUsage,INTEGER,read-create,,current,hostMap(1):serverMap(2):hostServerMap(3),Usage of the multicast address block. The hostMap (1) indicates that the address block is only used in the MARS host map table. The serverMap (2) indicates that the address block is only used in the MARS server map table. The hostServerMap (3) indicates that the address block is used in both the host map and the server map tables.
.1.3.6.1.2.1.57.2.2.1.4,IPATM-IPMC-MIB::marsMcGrpRxLayer3GrpSets,Counter32,read-only,,current,,Number of MARS_JOIN messages received with mars$flags.layer3grp flag set.
.1.3.6.1.2.1.57.2.2.1.5,IPATM-IPMC-MIB::marsMcGrpRxLayer3GrpResets,Counter32,read-only,,current,,Number of MARS_JOIN messages received with mars$flags.layer3grp flag reset.
.1.3.6.1.2.1.57.2.2.1.6,IPATM-IPMC-MIB::marsMcGrpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.57.2.3,IPATM-IPMC-MIB::marsHostMapTable,,not-accessible,,current,,This table caches mappings between IP multicast address to a list of ATM addresses that are configured or dynamically learned from the MARS. This address resolution is used for the host map. It supports the mapping of a block of multicast group addresses to a cluster member address. In the case where a group block is associated with multiple cluster members, several entries are used to representing the relationship.
.1.3.6.1.2.1.57.2.3.1,IPATM-IPMC-MIB::marsHostMapEntry,,not-accessible,marsIndex:marsIfIndex:marsMcMinGrpAddr:marsMcMaxGrpAddr:marsHostMapAtmAddr,current,,Each entry row contains attributes associated with the mapping between a multicast group block and an ATM address.
.1.3.6.1.2.1.57.2.3.1.1,IPATM-IPMC-MIB::marsHostMapAtmAddr,OCTET,not-accessible,,current,,The mapped cluster member ATM address.
.1.3.6.1.2.1.57.2.3.1.2,IPATM-IPMC-MIB::marsHostMapRowType,INTEGER,read-create,,current,static(1):dynamic(2),Method in which this entry row is created. The static (1) indicates that this row is created through configuration. The dynamic (2) indicates that the row is created as the result of group address updates received at this MARS.
.1.3.6.1.2.1.57.2.3.1.3,IPATM-IPMC-MIB::marsHostMapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. This object must not be set to 'active' until instances of all corresponding columns in the row of this table are appropriately configured. It is possible for an SNMP management station to set the row to 'notInService' and modify the entry and then set it back to 'active' with the following exception. That is, rows for which the corresponding instance of marsHostMapRowType has a value of 'dynamic' can not be modified or deleted.
.1.3.6.1.2.1.57.2.4,IPATM-IPMC-MIB::marsServerMapTable,,not-accessible,,current,,This table caches mappings between IP multicast address to a list of MCS ATM addresses that are configured or dynamically learned from the MARS. This address resolution is used for the server map. It supports the mapping of a block of multicast group addresses to a MCS address. In the case where a group block is associated with multiple MCSs, several entries are used to representing the relationship.
.1.3.6.1.2.1.57.2.4.1,IPATM-IPMC-MIB::marsServerMapEntry,,not-accessible,marsIndex:marsIfIndex:marsMcMinGrpAddr:marsMcMaxGrpAddr:marsServerMapAtmAddr,current,,Each entry row contains attributes associated with the mapping between a multicast group block and an MCS address.
.1.3.6.1.2.1.57.2.4.1.1,IPATM-IPMC-MIB::marsServerMapAtmAddr,OCTET,not-accessible,,current,,The mapped MCS ATM address.
.1.3.6.1.2.1.57.2.4.1.2,IPATM-IPMC-MIB::marsServerMapRowType,INTEGER,read-create,,current,static(1):dynamic(2),Method in which this entry row is created. The 'static (1)' indicates that this row is created through configuration. The 'dynamic (2)' indicates that the row is created as the result of group address updates received at this MARS.
.1.3.6.1.2.1.57.2.4.1.3,IPATM-IPMC-MIB::marsServerMapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. This object must not be set to 'active' until instances of all corresponding columns in the row of this table are appropriately configured. It is possible for an SNMP management station to set the row to 'notInService' and modify the entry and then set it back to 'active' with the following exception. That is, rows for which the corresponding instance of marsServerMapRowType has a value of 'dynamic' can not be modified or deleted.
.1.3.6.1.2.1.57.2.5,IPATM-IPMC-MIB::marsVcTable,,not-accessible,,current,,This table contains information about open virtual circuits (VCs) that a MARS has. For point to point circuit, each entry represents a single VC connection between this MARS ATM address to another party's ATM address. In the case of point to multipoint connection where a ControlVc is attached with multiple leaf nodes, several entries are used to represent the relationship. An example of point to multi-point VC represented in a table is shown below. MARS VPI/VCI MARS Addr Party Addr 1 0,1 m1 p1 1 0,1 m1 p2 1 0,1 m1 p3
.1.3.6.1.2.1.57.2.5.1,IPATM-IPMC-MIB::marsVcEntry,,not-accessible,marsIndex:marsIfIndex:marsVcVpi:marsVcVci:marsVcPartyAddr,current,,The objects contained in the entry are VC related attributes such as VC signalling type, control VC type, idle timer, negotiated MTU size, etc.
.1.3.6.1.2.1.57.2.5.1.1,IPATM-IPMC-MIB::marsVcVpi,INTEGER,not-accessible,,current,,The value of virtual path identifier (VPI). Since a VPI can be numbered 0, this sub-index can take a value of 0.
.1.3.6.1.2.1.57.2.5.1.2,IPATM-IPMC-MIB::marsVcVci,INTEGER,not-accessible,,current,,The value of virtual circuit identifier (VCI). Since a VCI can be numbered 0, this sub-index can take a value of 0.
.1.3.6.1.2.1.57.2.5.1.5,IPATM-IPMC-MIB::marsVcPartyAddr,OCTET,not-accessible,,current,,An ATM party address in which this VC is linked. The party type is identified by the marsVcPartyAddrType.
.1.3.6.1.2.1.57.2.5.1.6,IPATM-IPMC-MIB::marsVcPartyAddrType,INTEGER,read-create,,current,called(1):calling(2),The party type is associated with the party address. The 'called (1)' indicates that the party address is a destination address which implies that VC is originated from this MARS. The 'calling (2)' indicates the VC was initiated externally to this MARS. The party address is the source address.
.1.3.6.1.2.1.57.2.5.1.7,IPATM-IPMC-MIB::marsVcType,INTEGER,read-create,,current,pvc(1):svc(2),Circuit Connection type: permanent virtual circuit or switched virtual circuit.
.1.3.6.1.2.1.57.2.5.1.8,IPATM-IPMC-MIB::marsVcCtrlType,INTEGER,read-create,,current,pointToPointVC(1):clusterControlVC(2):serverControlVC(3),Control VC type used to specify a particular connection. pointToPointVC (1): used by the ATM endpoints (clients) or the MCS for registration and queries. This VC is set up from a MARS client and MCS to this MARS. It is a bi-directional VC. clusterControlVC (2): used by MARS to issue asynchronous updates to ATM an ATM client. This VC is established from the MARs to the ATM client. serverControlVC (3): used by MARS to issue asynchronous update to ATM multicast servers. This type of VC exists when at least a MCS is being used.
.1.3.6.1.2.1.57.2.5.1.9,IPATM-IPMC-MIB::marsVcIdleTimer,INTEGER,read-create,,current,,The idle timer associated with this VC. The minimum suggested value is 1 minute and the recommended default value is 20 minutes.
.1.3.6.1.2.1.57.2.5.1.10,IPATM-IPMC-MIB::marsVcCmi,INTEGER,read-create,,current,,Cluster member identifier (CMI) which uniquely identifies each endpoint attached to the cluster. This variable applies to each 'leaf node' of an outgoing control VC.
.1.3.6.1.2.1.57.2.5.1.11,IPATM-IPMC-MIB::marsVcEncapsType,INTEGER,read-create,,current,other(1):llcSnap(2),The encapsulation type used when communicating over this VC.
.1.3.6.1.2.1.57.2.5.1.12,IPATM-IPMC-MIB::marsVcNegotiatedMtu,INTEGER,read-create,,current,,The negotiated MTU when communicating over this VC.
.1.3.6.1.2.1.57.2.5.1.13,IPATM-IPMC-MIB::marsVcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all corresponding columns in the row of this table are appropriately configured. While the marsVcIdleTimer in this conceptual row can be modified irrespective of the value of this object, all other objects in the row can not be modified when this object has a value of 'active'. It is possible for an SNMP management station to set the row to 'notInService' and modify the entry and then set it back to 'active' with the following exception. That is, rows for which the corresponding instance of marsVcType has a value of 'svc' can not be modified or deleted.
.1.3.6.1.2.1.57.2.6,IPATM-IPMC-MIB::marsRegClientTable,,not-accessible,,current,,This table contains ATM identities of all the currently registered cluster members at a MARS. Each entry represents one set of ATM identities associated with one cluster member or the MARS client.
.1.3.6.1.2.1.57.2.6.1,IPATM-IPMC-MIB::marsRegClientEntry,,not-accessible,marsIndex:marsIfIndex:marsRegClientCmi,current,,Each entry row contains attributes associated with one register cluster member.
.1.3.6.1.2.1.57.2.6.1.1,IPATM-IPMC-MIB::marsRegClientCmi,INTEGER,not-accessible,,current,,This cluster member identifier is used as an auxiliary index for the entry in this table.
.1.3.6.1.2.1.57.2.6.1.2,IPATM-IPMC-MIB::marsRegClientAtmAddr,OCTET,read-only,,current,,The registered client's ATM address.
.1.3.6.1.2.1.57.2.7,IPATM-IPMC-MIB::marsRegMcsTable,,not-accessible,,current,,This table contains ATM identities of all the currently registered MCSs at a MARS. Each entry represents one set of ATM identities associated with one MCS.
.1.3.6.1.2.1.57.2.7.1,IPATM-IPMC-MIB::marsRegMcsEntry,,not-accessible,marsIndex:marsIfIndex:marsRegMcsAtmAddr,current,,Each entry row contains attributes associated with one registered MCS.
.1.3.6.1.2.1.57.2.7.1.1,IPATM-IPMC-MIB::marsRegMcsAtmAddr,OCTET,read-only,,current,,The registered MCS's ATM address.
.1.3.6.1.2.1.57.2.8,IPATM-IPMC-MIB::marsStatTable,,not-accessible,,current,,The table contains statistics collected at MARS.
.1.3.6.1.2.1.57.2.8.1,IPATM-IPMC-MIB::marsStatEntry,,not-accessible,marsIndex:marsIfIndex,current,,Each entry contains statistics collected at one MARS.
.1.3.6.1.2.1.57.2.8.1.1,IPATM-IPMC-MIB::marsStatTxMultiMsgs,Counter32,read-only,,current,,Total number of MARS_MULTI transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.2,IPATM-IPMC-MIB::marsStatTxGrpLstRplyMsgs,Counter32,read-only,,current,,Total number of MARS_GROUPLIST_REPLY messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.3,IPATM-IPMC-MIB::marsStatTxRedirectMapMsgs,Counter32,read-only,,current,,Total number of MARS_REDIRECT_MAP messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.4,IPATM-IPMC-MIB::marsStatTxMigrateMsgs,Counter32,read-only,,current,,Total number of MARS_MIGRATE messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.5,IPATM-IPMC-MIB::marsStatTxNakMsgs,Counter32,read-only,,current,,Total number of MARS_NAK messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.6,IPATM-IPMC-MIB::marsStatTxJoinMsgs,Counter32,read-only,,current,,Total number of MARS_JOIN messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.7,IPATM-IPMC-MIB::marsStatTxLeaveMsgs,Counter32,read-only,,current,,Total number of MARS_LEAVE messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.8,IPATM-IPMC-MIB::marsStatTxSjoinMsgs,Counter32,read-only,,current,,Total number of MARS_SJOIN messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.9,IPATM-IPMC-MIB::marsStatTxSleaveMsgs,Counter32,read-only,,current,,Total number of MARS_SLEAVE messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.10,IPATM-IPMC-MIB::marsStatTxMservMsgs,Counter32,read-only,,current,,Total number of MARS_MSERV messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.11,IPATM-IPMC-MIB::marsStatTxUnservMsgs,Counter32,read-only,,current,,Total number of MARS_UNSERV messages transmitted by this MARS.
.1.3.6.1.2.1.57.2.8.1.12,IPATM-IPMC-MIB::marsStatRxReqMsgs,Counter32,read-only,,current,,Total number of MARS_REQUEST messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.13,IPATM-IPMC-MIB::marsStatRxGrpLstReqMsgs,Counter32,read-only,,current,,Total number of MARS_GROUPLIST_REQUEST messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.14,IPATM-IPMC-MIB::marsStatRxJoinMsgs,Counter32,read-only,,current,,Total number of MARS_JOINS messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.15,IPATM-IPMC-MIB::marsStatRxLeaveMsgs,Counter32,read-only,,current,,Total number of MARS_LEAVES messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.16,IPATM-IPMC-MIB::marsStatRxMservMsgs,Counter32,read-only,,current,,Total number of MARS_MSERV messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.17,IPATM-IPMC-MIB::marsStatRxUnservMsgs,Counter32,read-only,,current,,Total number of MARS_UNSERV messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.18,IPATM-IPMC-MIB::marsStatRxBlkJoinMsgs,Counter32,read-only,,current,,Total number of block joins messages received by this MARS.
.1.3.6.1.2.1.57.2.8.1.19,IPATM-IPMC-MIB::marsStatRegMemGroups,Counter32,read-only,,current,,Total number of IP multicast groups with 1 or more joined cluster members.
.1.3.6.1.2.1.57.2.8.1.20,IPATM-IPMC-MIB::marsStatRegMcsGroups,Counter32,read-only,,current,,Total number of IP multicast groups with 1 or more joined MCSs.
.1.3.6.1.2.1.57.3,IPATM-IPMC-MIB::marsMcsObjects,,,,,,
.1.3.6.1.2.1.57.3.1,IPATM-IPMC-MIB::marsMcsTable,,not-accessible,,current,,The objects defined in this table are used for the management of a multicast server (MCS).
.1.3.6.1.2.1.57.3.1.1,IPATM-IPMC-MIB::marsMcsEntry,,not-accessible,marsMcsIndex:marsMcsIfIndex,current,,Each entry contains a MCS and its associated attributes.
.1.3.6.1.2.1.57.3.1.1.1,IPATM-IPMC-MIB::marsMcsIndex,Integer32,not-accessible,,current,,The auxiliary variable used to identify instances of the columnar objects in the MCS table.
.1.3.6.1.2.1.57.3.1.1.2,IPATM-IPMC-MIB::marsMcsIfIndex,Integer32,not-accessible,,current,,The ifIndex of the interface that the MCS is associated with.
.1.3.6.1.2.1.57.3.1.1.3,IPATM-IPMC-MIB::marsMcsAddr,OCTET,read-create,,current,,The ATM address associated with the MCS.
.1.3.6.1.2.1.57.3.1.1.4,IPATM-IPMC-MIB::marsMcsDefaultMarsAddr,OCTET,read-create,,current,,The default MARS ATM address which is needed to setup the initial signalling path between a MCS and its associated MARS.
.1.3.6.1.2.1.57.3.1.1.5,IPATM-IPMC-MIB::marsMcsRegistration,INTEGER,read-create,,of,notRegistered(1):registering(2):registered(3):reRegisteringFault(4):reRegisteringRedirMap(5),An indication with regards to the registration 'notRegistered (1)', 'registered (2)', and registered (3) are self-explanatory. The 'reRegisteringFault (4)' indicates the MCS is in the process of re-registering with a MARS due to some fault conditions. The 'reRegisteringRedMap (5)' status code shows that MCS is re-registering because it has received a MARS_REDIRECT_MAP message and was told to register with a shift MARS.
.1.3.6.1.2.1.57.3.1.1.6,IPATM-IPMC-MIB::marsMcsSsn,Unsigned32,read-create,,current,,The MCS own 32 bit Server Sequence Number. It is used to track the Mars sequence number.
.1.3.6.1.2.1.57.3.1.1.7,IPATM-IPMC-MIB::marsMcsDefaultMtu,INTEGER,read-create,,current,,The default maximum transmission unit (MTU) used for this cluster. Note that the actual size used for a VC between two members of the cluster may be negotiated during connection setup and may be different than this value. Default value = 9180 bytes.
.1.3.6.1.2.1.57.3.1.1.8,IPATM-IPMC-MIB::marsMcsFailureTimer,INTEGER,read-create,,current,,A timer used to flag the failure of last MARS_MULTI to arrive. Default value = 10 seconds (recommended).
.1.3.6.1.2.1.57.3.1.1.9,IPATM-IPMC-MIB::marsMcsRetranDelayTimer,INTEGER,read-create,,current,,The delay timer for sending out new MARS_REQUEST for the group after the MCS learned that there is no other group in the cluster. The timer must be set between 5 and 10 seconds inclusive.
.1.3.6.1.2.1.57.3.1.1.10,IPATM-IPMC-MIB::marsMcsRdmMulReqAddRetrTimer,INTEGER,read-create,,current,,The initial random L_MULTI_RQ/ADD retransmit timer which can be set between 5 and 10 seconds inclusive.
.1.3.6.1.2.1.57.3.1.1.11,IPATM-IPMC-MIB::marsMcsRdmVcRevalidateTimer,INTEGER,read-create,,current,,The random time to set VC_revalidate flag. The timer value ranges between 1 and 10 seconds inclusive.
.1.3.6.1.2.1.57.3.1.1.12,IPATM-IPMC-MIB::marsMcsRegisterRetrInterval,INTEGER,read-create,,current,,MARS_MSERV/UNSERV retransmit interval. The minimum and recommended values are 5 and 10 seconds, respectively.
.1.3.6.1.2.1.57.3.1.1.13,IPATM-IPMC-MIB::marsMcsRegisterRetrLimit,INTEGER,read-create,,current,,MARS_MSERV/UNSERV retransmit limit. The maximum value is 5.
.1.3.6.1.2.1.57.3.1.1.14,IPATM-IPMC-MIB::marsMcsRegWithMarsRdmTimer,INTEGER,read-create,,current,,Random time for a MCS to register with a MARS.
.1.3.6.1.2.1.57.3.1.1.15,IPATM-IPMC-MIB::marsMcsForceWaitTimer,INTEGER,read-create,,current,,Force wait if MARS re-registration is looping. The minimum value is 1 minute.
.1.3.6.1.2.1.57.3.1.1.16,IPATM-IPMC-MIB::marsMcsLmtToMissRedirMapTimer,INTEGER,read-create,,current,,Timer limit for MCS to miss MARS_REDIRECT_MAPS.
.1.3.6.1.2.1.57.3.1.1.17,IPATM-IPMC-MIB::marsMcsIdleTimer,INTEGER,read-create,,current,,The configurable inactivity timer associated with a MCS. When a VC is created at this MCS, it gets the idle timer value from this configurable timer. The minimum suggested value is 1 minute and the recommended default value is 20 minutes.
.1.3.6.1.2.1.57.3.1.1.18,IPATM-IPMC-MIB::marsMcsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all corresponding columns in the row of this table are appropriately configured and until the agent has also created a corresponding row in the marsMcsStatTable. When this object has a value of 'active', the following columnar objects can not be modified: marsMcsDefaultMarsAddr, marsMcsSsn, marsMcsRegstration, marsMcsDefaultMtu while other objects in this conceptual row can be modified irrespective of the value of this object. Deletion of this row is allowed regardless of whether or not a row in any associated tables (i.e., marsMcsVcTable) still exists or is in use. Once this row is deleted, it is recommended that the agent or the SNMP management station (if possible) through the set command deletes any stale rows that are associated with this row.
.1.3.6.1.2.1.57.3.2,IPATM-IPMC-MIB::marsMcsMcGrpTable,,not-accessible,,current,,This table contains a list of IP multicast group address blocks associated by a MARS MCS. The MCS uses the information contained in list to advertise its multicast group service to the MARS. Each row can be created or deleted via configuration.
.1.3.6.1.2.1.57.3.2.1,IPATM-IPMC-MIB::marsMcsMcGrpEntry,,not-accessible,marsMcsIndex:marsMcsIfIndex:marsMcsMcMinGrpAddr:marsMcsMcMaxGrpAddr,current,,Each entry represents a consecutive block of multicast group addresses.
.1.3.6.1.2.1.57.3.2.1.1,IPATM-IPMC-MIB::marsMcsMcMinGrpAddr,IpAddress,not-accessible,,current,,Minimum multicast group address - the min and max multicast forms multi-group block. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that this block contains a single group address. Since the block joins are no allowed by a MCS as implied in the RFC2022, the MinGrpAddr and MaxGrpAddress should be set to the same value at this time when an entry row is created.
.1.3.6.1.2.1.57.3.2.1.2,IPATM-IPMC-MIB::marsMcsMcMaxGrpAddr,IpAddress,not-accessible,,current,,Maximum multicast group address - the min and max multicast forms a multi-group block. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that this block contains a single group address. Since the block joins are no allowed by a MCS as implied in the RFC2022, the MinGrpAddr and MaxGrpAddress should be set to the same value at this time when an entry row is created.
.1.3.6.1.2.1.57.3.2.1.3,IPATM-IPMC-MIB::marsMcsMcGrpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create or delete a row in this table. Since other objects in this row are not-accessible 'index-objects', the value of this object has no effect on whether those objects in this conceptual row can be modified.
.1.3.6.1.2.1.57.3.3,IPATM-IPMC-MIB::marsMcsBackupMarsTable,,not-accessible,,current,,This table contains a list of backup MARS addresses that a MCS can make contact to in case of failure for connecting to the primary server. The list of addresses is in descending order of preference. It should be noted that the backup list provided by the MARS to the MCS via the MARS_REDIRECT_MAP message has a higher preference than addresses that are manually configured into the MCS. When such a list is received from the MARS, this information should be inserted at the top of the list. Each row can be created or deleted via configuration.
.1.3.6.1.2.1.57.3.3.1,IPATM-IPMC-MIB::marsMcsBackupMarsEntry,,not-accessible,marsMcsIndex:marsMcsIfIndex:marsMcsBackupMarsPriority:marsMcsBackupMarsAddr,current,,Each entry represents an ATM address of a backup MARS.
.1.3.6.1.2.1.57.3.3.1.1,IPATM-IPMC-MIB::marsMcsBackupMarsPriority,Unsigned32,not-accessible,,current,,The priority associated with a backup MARS. A lower priority value inidcates a higher preference.
.1.3.6.1.2.1.57.3.3.1.2,IPATM-IPMC-MIB::marsMcsBackupMarsAddr,OCTET,not-accessible,,current,,The ATM address associated with a backup MARS.
.1.3.6.1.2.1.57.3.3.1.3,IPATM-IPMC-MIB::marsMcsBackupMarsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create or delete a row in this table. Since other objects in this row are not-accessible 'index-objects', the value of this object has no effect on whether those objects in this conceptual row can be modified.
.1.3.6.1.2.1.57.3.4,IPATM-IPMC-MIB::marsMcsVcTable,,not-accessible,,current,,This table contains information about open virtual circuits (VCs) that a MCS has. For point to point circuit, each entry represents a single VC connection between this MCS ATM address to another party ATM address. In the case of point to multipoint connection where a single source address is associated with multiple destinations, several entries are used to represent the relationship. An example of point to multi-point VC represented in a table is shown below. MCS VPI/VCI Grp Addr1/Addr2 Part Addr 1 0,1 g1,g2 p1 1 0,1 g1,g2 p2 1 0,1 g1,g2 p3
.1.3.6.1.2.1.57.3.4.1,IPATM-IPMC-MIB::marsMcsVcEntry,,not-accessible,marsMcsIndex:marsMcsIfIndex:marsMcsVcVpi:marsMcsVcVci:marsMcsVcMinGrpAddr:marsMcsVcMaxGrpAddr:marsMcsVcPartyAddr,current,,The objects contained in the entry are VC related attributes such as VC signalling type, control VC type, idle timer, negotiated MTU size, etc.
.1.3.6.1.2.1.57.3.4.1.1,IPATM-IPMC-MIB::marsMcsVcVpi,INTEGER,not-accessible,,current,,The value of virtual path identifier (VPI). Since a VPI can be numbered 0, this sub-index can take a value of 0.
.1.3.6.1.2.1.57.3.4.1.2,IPATM-IPMC-MIB::marsMcsVcVci,INTEGER,not-accessible,,current,,The value of virtual circuit identifier (VCI). Since a VCI can be numbered 0, this sub-index can take a value of 0.
.1.3.6.1.2.1.57.3.4.1.3,IPATM-IPMC-MIB::marsMcsVcMinGrpAddr,IpAddress,not-accessible,,current,,Minimum IP multicast group address - the min and max multicast forms a multi-group block which is associated with a VC. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that the size of multi-group block is 1, a single IP group.
.1.3.6.1.2.1.57.3.4.1.4,IPATM-IPMC-MIB::marsMcsVcMaxGrpAddr,IpAddress,not-accessible,,current,,Maximum IP multicast group address - the min and max multicast forms a multi-group block which is associated with a VC. If the MinGrpAddr and MaxGrpAddr are the same, it indicates that the size of multi-group block is 1, a single IP group.
.1.3.6.1.2.1.57.3.4.1.5,IPATM-IPMC-MIB::marsMcsVcPartyAddr,OCTET,not-accessible,,current,,An ATM party address in which this VC is linked. The party type is identified by the marsMcsVcPartyAddrType.
.1.3.6.1.2.1.57.3.4.1.6,IPATM-IPMC-MIB::marsMcsVcPartyAddrType,INTEGER,read-create,,current,called(1):calling(2),The party type is associated with the party address. The called (1) indicates that the party address is a destination address which implies that VC is originated from this MCS. The calling (2) indicates the VC was initiated externally to this MCS. In this case, the party address is the source address.
.1.3.6.1.2.1.57.3.4.1.7,IPATM-IPMC-MIB::marsMcsVcType,INTEGER,read-create,,current,pvc(1):svc(2),Circuit Connection type: permanent virtual circuit or switched virtual circuit.
.1.3.6.1.2.1.57.3.4.1.8,IPATM-IPMC-MIB::marsMcsVcCtrlType,INTEGER,read-create,,current,pointToPointVC(1):serverControlVC(2):pointToMultiPointVC(3),Control VC type used to specify a particular connection. pointToPointVC (1): used by the ATM Clients for the registration and queries. This VC or the initial signalling path is set up from the source MCS to a MARS. It is bi-directional. serverControlVC (2): used by a MARS to issue asynchronous updates to an ATM Client. This VC is established from the MARS to the MCS. pointToMultiPointVC (3): used by the client to transfer multicast data packets from layer 3. This VC is established from this VC to a cluster member.
.1.3.6.1.2.1.57.3.4.1.9,IPATM-IPMC-MIB::marsMcsVcIdleTimer,INTEGER,read-create,,current,,The idle timer associated with this VC. The minimum suggested value is 1 minute and the recommended default value is 20 minutes.
.1.3.6.1.2.1.57.3.4.1.10,IPATM-IPMC-MIB::marsMcsVcRevalidate,INTEGER,read-create,,current,true(1):false(2),A flag associated with an open and active multipoint VC. It is checked every time a packet is queued for transmission on that VC. The object has the value of true (1) if revalidate is required and the value false (2) otherwise.
.1.3.6.1.2.1.57.3.4.1.11,IPATM-IPMC-MIB::marsMcsVcEncapsType,INTEGER,read-create,,current,other(1):llcSnap(2),The encapsulation type used when communicating over this VC.
.1.3.6.1.2.1.57.3.4.1.12,IPATM-IPMC-MIB::marsMcsVcNegotiatedMtu,INTEGER,read-create,,current,,The negotiated MTU when communicating over this VC.
.1.3.6.1.2.1.57.3.4.1.13,IPATM-IPMC-MIB::marsMcsVcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object is used to create, delete or modify a row in this table. A row cannot be made 'active' until instances of all corresponding columns in the row of this table are appropriately configured. While objects: marsMcsVcIdleTimer and marsMcsVcRevalidate in this conceptual row can be modified irrespective of the value of this object, all other objects in the row can not be modified when this object has a value of 'active'. It is possible for an SNMP management station to set the row to 'notInService' and modify the entry and then set it back to 'active' with the following exception. That is, rows for which the corresponding instance of marsMcsVcType has a value of 'svc' can not be modified or deleted.
.1.3.6.1.2.1.57.3.5,IPATM-IPMC-MIB::marsMcsStatTable,,not-accessible,,current,,The table contains statistics collected at MARS MCSs.
.1.3.6.1.2.1.57.3.5.1,IPATM-IPMC-MIB::marsMcsStatEntry,,not-accessible,marsMcsIndex:marsMcsIfIndex,current,,Each entry contains statistics collected at one MARS MCS.
.1.3.6.1.2.1.57.3.5.1.1,IPATM-IPMC-MIB::marsMcsStatTxReqMsgs,Counter32,read-only,,current,,Total number of MARS_REQUEST messages transmitted from this MCS.
.1.3.6.1.2.1.57.3.5.1.2,IPATM-IPMC-MIB::marsMcsStatTxMservMsgs,Counter32,read-only,,current,,Total number of MARS_MSERV messages transmitted from this MCS.
.1.3.6.1.2.1.57.3.5.1.3,IPATM-IPMC-MIB::marsMcsStatTxUnservMsgs,Counter32,read-only,,current,,Total number of MARS_UNSERV messages transmitted from this MCS.
.1.3.6.1.2.1.57.3.5.1.4,IPATM-IPMC-MIB::marsMcsStatRxMultiMsgs,Counter32,read-only,,current,,Total number of MARS_MULTI messages received by this MCS.
.1.3.6.1.2.1.57.3.5.1.5,IPATM-IPMC-MIB::marsMcsStatRxSjoinMsgs,Counter32,read-only,,current,,Total number of MARS_SJOIN messages received by this MCS.
.1.3.6.1.2.1.57.3.5.1.6,IPATM-IPMC-MIB::marsMcsStatRxSleaveMsgs,Counter32,read-only,,current,,Total number of MARS_SLEAVE messages received by this MCS.
.1.3.6.1.2.1.57.3.5.1.7,IPATM-IPMC-MIB::marsMcsStatRxNakMsgs,Counter32,read-only,,current,,Total number of MARS_NAK messages received by this MCS.
.1.3.6.1.2.1.57.3.5.1.8,IPATM-IPMC-MIB::marsMcsStatRxMigrateMsgs,Counter32,read-only,,current,,Total number of MARS_MIGRATE messages received by this MCS.
.1.3.6.1.2.1.57.3.5.1.9,IPATM-IPMC-MIB::marsMcsStatFailMultiMsgs,Counter32,read-only,,current,,Total number of timeouts occurred indicating failure of the last MARS_MULTI to arrive.
.1.3.6.1.2.1.57.4,IPATM-IPMC-MIB::marsConformance,,,,,,
.1.3.6.1.2.1.57.4.1,IPATM-IPMC-MIB::marsClientConformance,,,,,,
.1.3.6.1.2.1.57.4.1.1,IPATM-IPMC-MIB::marsClientCompliances,,,,,,
.1.3.6.1.2.1.57.4.1.1.1,IPATM-IPMC-MIB::marsClientCompliance,,,,,,The compliance statement for entities that are required for the management of MARS clients.
.1.3.6.1.2.1.57.4.1.2,IPATM-IPMC-MIB::marsClientGroups,,,,,,
.1.3.6.1.2.1.57.4.1.2.1,IPATM-IPMC-MIB::marsClientGroup,,,,,,A collection of objects to be implemented in a MIB for the management of MARS clients.
.1.3.6.1.2.1.57.4.2,IPATM-IPMC-MIB::marsServerConformance,,,,,,
.1.3.6.1.2.1.57.4.2.1,IPATM-IPMC-MIB::marsServerCompliances,,,,,,
.1.3.6.1.2.1.57.4.2.1.1,IPATM-IPMC-MIB::marsServerCompliance,,,,,,The compliance statement for entities that are required for the management of MARS servers.
.1.3.6.1.2.1.57.4.2.2,IPATM-IPMC-MIB::marsServerGroups,,,,,,
.1.3.6.1.2.1.57.4.2.2.1,IPATM-IPMC-MIB::marsServerGroup,,,,,,A collection of objects to be implemented in a MIB for the management of MARS servers.
.1.3.6.1.2.1.57.4.2.2.2,IPATM-IPMC-MIB::marsServerEventGroup,,,,,,A collection of events that can be generated from a MARS server.
.1.3.6.1.2.1.57.4.3,IPATM-IPMC-MIB::marsMcsConformance,,,,,,
.1.3.6.1.2.1.57.4.3.1,IPATM-IPMC-MIB::marsMcsCompliances,,,,,,
.1.3.6.1.2.1.57.4.3.1.1,IPATM-IPMC-MIB::marsMcsCompliance,,,,,,The compliance statement for entities that are required for the management of MARS multicast servers (MCS).
.1.3.6.1.2.1.57.4.3.2,IPATM-IPMC-MIB::marsMcsGroups,,,,,,
.1.3.6.1.2.1.57.4.3.2.1,IPATM-IPMC-MIB::marsMcsGroup,,,,,,A collection of objects to be implemented in a MIB for the management of MARS multicast servers (MCS).
.1.3.6.1.2.1.58,PerfHist-TC-MIB::perfHistTCMIB,,,,,,This MIB Module provides Textual Conventions to be used by systems supporting 15 minute based performance history counts. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3593; see the RFC itself for full legal notices.
.1.3.6.1.2.1.59,ATM-ACCOUNTING-INFORMATION-MIB::atmAccountingInformationMIB,,,,,,The MIB module for identifying items of accounting information which are applicable to ATM connections.
.1.3.6.1.2.1.59.1,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngMIBObjects,,,,,,
.1.3.6.1.2.1.59.1.1,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngDataObjects,,,,,,This identifier defines a subtree under which various objects are defined such that a set of objects to be collected as ATM accounting data can be specified as a (subtree, list) tuple using this identifier as the subtree.
.1.3.6.1.2.1.59.1.1.1,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngConnectionType,INTEGER,not-accessible,,current,pvc(1):pvp(2):svcIncoming(3):svcOutgoing(4):svpIncoming(5):svpOutgoing(6):spvcInitiator(7):spvcTarget(8):spvpInitiator(9):spvpTarget(10),The type of connection.
.1.3.6.1.2.1.59.1.1.2,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCastType,INTEGER,not-accessible,,current,p2p(1):p2mp(2),An indication of whether the connection is point-to-point or point-to-multipoint.
.1.3.6.1.2.1.59.1.1.3,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngIfName,OCTET,not-accessible,,current,,A textual name for the interface on which the data for the connection was collected. If the local SNMP agent supports the object ifName, the value of this object must be identical to that of ifName in the conceptual row of the ifTable corresponding to this interface.
.1.3.6.1.2.1.59.1.1.4,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngIfAlias,OCTET,not-accessible,,current,,The 'alias' name for the interface as specified by a network manager, e.g., via a management set operation to modify the relevant instance of the ifAlias object. Note that in contrast to ifIndex, ifAlias provides a non-volatile 'handle' for the interface, the value of which is retained across agent reboots.
.1.3.6.1.2.1.59.1.1.5,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngVpi,INTEGER,not-accessible,,current,,The VPI used for the connection.
.1.3.6.1.2.1.59.1.1.6,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngVci,INTEGER,not-accessible,,current,,The VCI used for the connection.
.1.3.6.1.2.1.59.1.1.7,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCallingParty,OCTET,not-accessible,,current,,The connection's calling party. If unknown (e.g., for a PVC), then the value of this object is the zero-length string.
.1.3.6.1.2.1.59.1.1.8,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCalledParty,OCTET,not-accessible,,current,,The connection's called party. If unknown (e.g., for a PVC), then the value of this object is the zero-length string.
.1.3.6.1.2.1.59.1.1.9,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCallReference,OCTET,not-accessible,,current,,The connection's call reference value (e.g., from Q.2931). If unknown (e.g., for a PVC), then the value of this object is the zero-length string.
.1.3.6.1.2.1.59.1.1.10,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngStartTime,OCTET,not-accessible,,current,,The time when the connection was established.
.1.3.6.1.2.1.59.1.1.11,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCollectionTime,OCTET,not-accessible,,current,,The time at which the data in this record was collected.
.1.3.6.1.2.1.59.1.1.12,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCollectMode,INTEGER,not-accessible,,current,onRelease(1):periodically(2):onCommand(3),The reason why this connection data was collected.
.1.3.6.1.2.1.59.1.1.13,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReleaseCause,Integer32,not-accessible,,current,,If the connection data was collected because of the release of an SVC, then this is the cause code in the Release message for the connection; otherwise, this object has the value zero.
.1.3.6.1.2.1.59.1.1.14,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngServiceCategory,INTEGER,not-accessible,,current,other(1):cbr(2):vbrRt(3):vbrNrt(4):abr(5):ubr(6):unknown(7),The connection's service category.
.1.3.6.1.2.1.59.1.1.15,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmittedCells,Counter64,not-accessible,,current,,The number of cells, including OAM cells, transmitted by this switch on this connection.
.1.3.6.1.2.1.59.1.1.16,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmittedClp0Cells,Counter64,not-accessible,,current,,The number of cells with CLP=0, including OAM cells, transmitted by this switch on this connection.
.1.3.6.1.2.1.59.1.1.17,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceivedCells,Counter64,not-accessible,,current,,The number of cells, including OAM cells, received by this switch on this connection.
.1.3.6.1.2.1.59.1.1.18,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceivedClp0Cells,Counter64,not-accessible,,current,,The number of cells with CLP=0, including OAM cells, received by this switch on this connection.
.1.3.6.1.2.1.59.1.1.19,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmitTrafficDescriptorType,OBJECT,not-accessible,,current,,The traffic descriptor type (as defined in RFC 1695 and its successors) in the direction in which the switch transmits cells on the connection.
.1.3.6.1.2.1.59.1.1.20,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmitTrafficDescriptorParam1,INTEGER,not-accessible,,current,,The first traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngTransmitTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.21,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmitTrafficDescriptorParam2,INTEGER,not-accessible,,current,,The second traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngTransmitTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.22,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmitTrafficDescriptorParam3,INTEGER,not-accessible,,current,,The third traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngTransmitTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.23,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmitTrafficDescriptorParam4,INTEGER,not-accessible,,current,,The fourth traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngTransmitTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.24,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngTransmitTrafficDescriptorParam5,INTEGER,not-accessible,,current,,The fifth traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngTransmitTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.25,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceiveTrafficDescriptorType,OBJECT,not-accessible,,current,,The traffic descriptor type (as defined in RFC 1695 and its successors) in the direction in which this switch receives cells on this connection.
.1.3.6.1.2.1.59.1.1.26,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceiveTrafficDescriptorParam1,INTEGER,not-accessible,,current,,The first traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngReceiveTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.27,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceiveTrafficDescriptorParam2,INTEGER,not-accessible,,current,,The second traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngReceiveTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.28,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceiveTrafficDescriptorParam3,INTEGER,not-accessible,,current,,The third traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngReceiveTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.29,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceiveTrafficDescriptorParam4,INTEGER,not-accessible,,current,,The fourth traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngReceiveTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.30,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngReceiveTrafficDescriptorParam5,INTEGER,not-accessible,,current,,The fifth traffic descriptor parameter in the direction in which this switch receives cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngReceiveTrafficDescriptorType.
.1.3.6.1.2.1.59.1.1.31,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCallingPartySubAddress,OCTET,not-accessible,,current,,The connection's calling party sub-address. If the connection has no calling party sub-address, or it's value is unknown, then the value of this object is the zero-length string.
.1.3.6.1.2.1.59.1.1.32,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngCalledPartySubAddress,OCTET,not-accessible,,current,,The connection's called party sub-address. If the connection has no called party sub-address, or it's value is unknown, then the value of this object is the zero-length string.
.1.3.6.1.2.1.59.1.1.33,ATM-ACCOUNTING-INFORMATION-MIB::atmAcctngRecordCrc16,OCTET,not-accessible,,current,,The value of the CRC-16 checksum (as defined by ISO 3309 (HDLC) and/or ITU X.25) calculated over the accounting record containing this object. While the mechanism for calculating/encoding the checksum value is specific to the method of encoding the accounting record, an accounting record containing this object is typically generated by initializing the value of this object to the all-zeros string ('0000'H), with the location of these zeros being saved. After generating the record, the checksum is calculated over the whole connection record and then the all-zeros value is overwritten (at the saved location) by the calculated value of the checksum.
.1.3.6.1.2.1.60,ACCOUNTING-CONTROL-MIB::accountingControlMIB,,,,,,The MIB module for managing the collection and storage of accounting information for connections in a connection- oriented network such as ATM.
.1.3.6.1.2.1.60.1,ACCOUNTING-CONTROL-MIB::acctngMIBObjects,,,,,,
.1.3.6.1.2.1.60.1.1,ACCOUNTING-CONTROL-MIB::acctngSelectionControl,,,,,,
.1.3.6.1.2.1.60.1.1.1,ACCOUNTING-CONTROL-MIB::acctngSelectionTable,,not-accessible,,current,,A list of accounting information selection entries. Note that additions, modifications and deletions of entries in this table can occur at any time, but such changes only take effect on the next occasion when collection begins into a new file. Thus, between modification and the next 'swap', the content of this table does not reflect the current selection.
.1.3.6.1.2.1.60.1.1.1.1,ACCOUNTING-CONTROL-MIB::acctngSelectionEntry,,not-accessible,acctngSelectionIndex,current,,An entry identifying an (subtree, list) tuple used to select a set of accounting information which is to be collected.
.1.3.6.1.2.1.60.1.1.1.1.1,ACCOUNTING-CONTROL-MIB::acctngSelectionIndex,Integer32,not-accessible,,current,,An arbitrary integer value which uniquely identifies a tuple stored in this table. This value is required to be the permanent 'handle' for an entry in this table for as long as that entry exists, including across restarts and power outages.
.1.3.6.1.2.1.60.1.1.1.1.2,ACCOUNTING-CONTROL-MIB::acctngSelectionSubtree,OBJECT,read-create,,current,,The combination of acctngSelectionSubtree and acctngSelectionList specifies one (subtree, list) tuple which is to be collected.
.1.3.6.1.2.1.60.1.1.1.1.3,ACCOUNTING-CONTROL-MIB::acctngSelectionList,OCTET,read-create,,current,,The combination of acctngSelectionSubtree and acctngSelectionList specifies one (subtree, list) tuple which is to be collected.
.1.3.6.1.2.1.60.1.1.1.1.4,ACCOUNTING-CONTROL-MIB::acctngSelectionFile,Integer32,read-create,,current,,An indication of the file into which the accounting information identified by this entry is to be stored. If there is no conceptual row in the acctngFileTable for which the value of acctngFileIndex has the same value as this object, then the information selected by this entry is not collected.
.1.3.6.1.2.1.60.1.1.1.1.5,ACCOUNTING-CONTROL-MIB::acctngSelectionType,BITS,read-create,,current,svcIncoming(0):svcOutgoing(1):svpIncoming(2):svpOutgoing(3):pvc(4):pvp(5):spvcOriginator(6):spvcTarget(7):spvpOriginator(8):spvpTarget(9),Indicates the types of connections for which the information selected by this entry are to be collected.
.1.3.6.1.2.1.60.1.1.1.1.6,ACCOUNTING-CONTROL-MIB::acctngSelectionRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. An agent may refuse to create new conceptual rows and/or modify existing conceptual rows, if such creation/modification would cause multiple rows to have the same values of acctngSelectionSubtree and acctngSelectionList. A conceptual row can not have the status of 'active' until values have been assigned to the acctngSelectionSubtree, acctngSelectionList and acctngSelectionFile columnar objects within that row. An agent must not refuse to change the values of the acctngSelectionSubtree, acctngSelectionList and acctngSelectionFile columnar objects within a conceptual row even while that row's status is 'active'. Similarly, an agent must not refuse to destroy an existing conceptual row while the file referenced by that row's instance of acctngSelectionFile is in active use, i.e., while the corresponding instance of acctngFileRowStatus has the value 'active'. However, such changes only take effect upon the next occasion when collection begins into a new (version of the) file.
.1.3.6.1.2.1.60.1.2,ACCOUNTING-CONTROL-MIB::acctngFileControl,,,,,,
.1.3.6.1.2.1.60.1.2.1,ACCOUNTING-CONTROL-MIB::acctngFileTable,,not-accessible,,current,,A list of files into which accounting information is to be stored.
.1.3.6.1.2.1.60.1.2.1.1,ACCOUNTING-CONTROL-MIB::acctngFileEntry,,not-accessible,acctngFileIndex,current,,An entry identifying a file into which accounting information is to be collected.
.1.3.6.1.2.1.60.1.2.1.1.1,ACCOUNTING-CONTROL-MIB::acctngFileIndex,Integer32,not-accessible,,current,,A unique value identifying a file into which accounting data is to be stored. This value is required to be the permanent 'handle' for an entry in this table for as long as that entry exists, including across restarts and power outages.
.1.3.6.1.2.1.60.1.2.1.1.2,ACCOUNTING-CONTROL-MIB::acctngFileName,OCTET,read-create,,current,,The name of the file into which accounting data is to be stored. If files are named using suffixes, then the name of the current file is the concatenation of acctngFileName and acctngFileNameSuffix. An agent will respond with an error (e.g., 'wrongValue') to a management set operation which attempts to modify the value of this object to the same value as already held by another instance of acctngFileName. An agent will also respond with an error (e.g., 'wrongValue') if the new value is invalid for use as a file name on the local file system (e.g., many file systems do not support white space embedded in file names). The value of this object can not be modified while the corresponding instance of acctngFileRowStatus is 'active'.
.1.3.6.1.2.1.60.1.2.1.1.3,ACCOUNTING-CONTROL-MIB::acctngFileNameSuffix,OCTET,read-only,,current,,The suffix, if any, of the name of a file into which accounting data is currently being stored. If suffixes are not used, then the value of this object is the zero-length string. Note that if a separator, such as a period, is used in appending the suffix to the file name, then that separator appears as the first character of this value.
.1.3.6.1.2.1.60.1.2.1.1.4,ACCOUNTING-CONTROL-MIB::acctngFileDescription,OCTET,read-create,,current,,The textual description of the accounting data which will be stored (on the next occasion) when header information is stored in the file. The value of this object may be modified at any time.
.1.3.6.1.2.1.60.1.2.1.1.5,ACCOUNTING-CONTROL-MIB::acctngFileCommand,INTEGER,read-create,,current,idle(1):cmdInProgress(2):swapToNewFile(3):collectNow(4),A control object for the collection of accounting data. When read the value is either 'idle' or 'cmdInProgress'. Writing a value is only allowed when the current value is 'idle'. When a value is successfully written, the value changes to 'cmdInProgress' until completion of the action, at which time the value reverts to 'idle'. Actions are invoked by writing the following values: 'swapToNewFile' - the collection of data into the current file is terminated, and collection continues into a new (version of the) file. 'collectNow' - the agent creates and stores a connection record into the current file for each active connection having a type matching acctngSelectionType and an age greater than acctngFileMinAge.
.1.3.6.1.2.1.60.1.2.1.1.6,ACCOUNTING-CONTROL-MIB::acctngFileMaximumSize,Integer32,read-create,,current,,The maximum size of the file (including header information). When the file of collected data reaches this size, either the agent automatically swaps to a new version (i.e., a new value acctngFileNameSuffix) of the file, or new records are discarded. Since a file must contain an integral number of connection records, the actual maximum size of the file may be just less OR Just greater than the value of this object. The value of this object can not be modified while the corresponding instance of acctngFileRowStatus is 'active'. The largest value of the maximum file size in some agents will be less than 2147483647 bytes.
.1.3.6.1.2.1.60.1.2.1.1.7,ACCOUNTING-CONTROL-MIB::acctngFileCurrentSize,Integer32,read-only,,current,,The current size of the file into which data is currently being collected, including header information.
.1.3.6.1.2.1.60.1.2.1.1.8,ACCOUNTING-CONTROL-MIB::acctngFileFormat,INTEGER,read-create,,current,other(1):ber(2),An indication of the format in which the accounting data is to be stored in the file. If the value is modified, the new value takes effect after the next 'swap' to a new file. The value ber(2) indicates the standard format.
.1.3.6.1.2.1.60.1.2.1.1.9,ACCOUNTING-CONTROL-MIB::acctngFileCollectMode,BITS,read-create,,current,onRelease(0):periodically(1),An indication of when accounting data is to be written into this file. Note that in addition to the occasions indicated by the value of this object, an agent always writes information on appropriate connections to the file when the corresponding instance of acctngFileCommand is set to 'collectNow'. - 'onRelease' - whenever a connection (or possibly, connection attempt) is terminated, either through a Release message or through management removal, information on that connection is written. - 'periodically' - information on appropriate connections is written on the expiry of a periodic timer, This value may be modified at any time.
.1.3.6.1.2.1.60.1.2.1.1.10,ACCOUNTING-CONTROL-MIB::acctngFileCollectFailedAttempts,BITS,read-create,,current,soft(0):regular(1),An indication of whether connection data is to be collected for failed connection attempts when the value of the corresponding instance of acctngFileCollectMode includes 'onRelease'. The individual values have the following meaning: 'soft' - indicates that connection data is to be collected for failed Soft PVCs/PVPs which originate or terminate at the relevant interface. 'regular' - indicates that connection data is to be collected for failed SVCs, including Soft PVCs/PVPs not originating or terminating at the relevant interface. This value may be modified at any time.
.1.3.6.1.2.1.60.1.2.1.1.11,ACCOUNTING-CONTROL-MIB::acctngFileInterval,Integer32,read-create,,current,,The number of seconds between the periodic collections of accounting data when the value of the corresponding instance of acctngFileCollectMode includes 'periodically'. Some agents may impose restrictions on the range of this interval. This value may be modified at any time.
.1.3.6.1.2.1.60.1.2.1.1.12,ACCOUNTING-CONTROL-MIB::acctngFileMinAge,Integer32,read-create,,current,,The minimum age of a connection, as used to determine the set of connections for which data is to be collected at the periodic intervals and/or when acctngFileCommand is set to 'collectNow'. The age of a connection is the elapsed time since it was last installed. When the periodic interval expires for a file or when acctngFileCommand is set to 'collectNow', accounting data is collected and stored in the file for each connection having a type matching acctngSelectionType and whose age at that time is greater than the value of acctngFileMinAge associated with the file. This value may be modified at any time.
.1.3.6.1.2.1.60.1.2.1.1.13,ACCOUNTING-CONTROL-MIB::acctngFileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object can not be set to 'active' until a value has been assigned to the corresponding instance of acctngFileName. Collection of data into the file does not begin until this object has the value 'active' and one or more (active) instances of acctngSelectionFile refer to it. If this value is modified after a collection has begun, collection into this file terminates and a new (or new version of the) file is immediately made ready for future collection (as if acctngFileCommand had been set to 'swapToNewFile'), but collection into the new (or new version of the) file does not begin until the value is subsequently set back to active.
.1.3.6.1.2.1.60.1.3,ACCOUNTING-CONTROL-MIB::acctngInterfaceControl,,,,,,
.1.3.6.1.2.1.60.1.3.1,ACCOUNTING-CONTROL-MIB::acctngAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),A control object to indicate the administratively desired state of the collection of accounting records across all interfaces. Modifying the value of acctngAdminStatus to 'disabled' does not remove or change the current configuration as represented by the active rows in the acctngSelectionTable, acctngFileTable and acctngInterfaceTable tables.
.1.3.6.1.2.1.60.1.3.2,ACCOUNTING-CONTROL-MIB::acctngOperStatus,INTEGER,read-only,,current,enabled(1):disabled(2),A status object to indicate the operational state of the collection of accounting records across all interfaces. When the value of acctngAdminStatus is modified to be 'enabled', the value of this object will change to 'enabled' providing it is possible to begin collecting accounting records. When the value of acctngAdminStatus is modified to be 'disabled', the value of this object will change to 'disabled' as soon as the collection of accounting records has terminated.
.1.3.6.1.2.1.60.1.3.3,ACCOUNTING-CONTROL-MIB::acctngProtection,INTEGER,read-write,,current,,A control object to protect against duplication of control commands. Over some transport/network protocols, it is possible for SNMP messages to get duplicated. Such duplication, if it occurred at just the wrong time could cause serious disruption to the collection and retrieval of accounting data, e.g., if a SNMP message setting acctngFileCommand to 'swapToNewFile' were to be duplicated, a whole file of accounting data could be lost. To protect against such duplication, a management application should retrieve the value of this object, and include in the Set operation needing protection, a variable binding which sets this object to the retrieved value.
.1.3.6.1.2.1.60.1.3.4,ACCOUNTING-CONTROL-MIB::acctngAgentMode,INTEGER,read-only,,current,swapOnCommand(1):swapOnFull(2),An indication of the behaviour mode of the agent when a file becomes full: 'swapOnCommand' - the agent does not automatically swap to a new file; rather, it discards newly collected data until a management application subsequently instructs it to swap to a new file. 'swapOnFull' - the agent terminates collection into the current file as and when that file becomes full.
.1.3.6.1.2.1.60.1.3.5,ACCOUNTING-CONTROL-MIB::acctngInterfaceTable,,not-accessible,,current,,A table controlling the collection of accounting data on specific interfaces of the switch.
.1.3.6.1.2.1.60.1.3.5.1,ACCOUNTING-CONTROL-MIB::acctngInterfaceEntry,,not-accessible,ifIndex,current,,An entry which controls whether accounting data is to be collected on an interface. The types of interfaces which are represented in this table is implementation-specific.
.1.3.6.1.2.1.60.1.3.5.1.1,ACCOUNTING-CONTROL-MIB::acctngInterfaceEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether the collection of accounting data is enabled on this interface.
.1.3.6.1.2.1.60.1.4,ACCOUNTING-CONTROL-MIB::acctngTrapControl,,,,,,
.1.3.6.1.2.1.60.1.4.1,ACCOUNTING-CONTROL-MIB::acctngControlTrapThreshold,INTEGER,read-write,,current,,A percentage of the maximum file size at which a 'nearly- full' trap is generated. The value of 0 indicates that no 'nearly-full' trap is to be generated.
.1.3.6.1.2.1.60.1.4.2,ACCOUNTING-CONTROL-MIB::acctngControlTrapEnable,INTEGER,read-write,,current,true(1):false(2),An indication of whether the acctngFileNearlyFull and acctngFileFull traps are enabled.
.1.3.6.1.2.1.60.2,ACCOUNTING-CONTROL-MIB::acctngNotifications,,,,,,
.1.3.6.1.2.1.60.2.0,ACCOUNTING-CONTROL-MIB::acctngNotifyPrefix,,,,,,
.1.3.6.1.2.1.60.2.0.1,ACCOUNTING-CONTROL-MIB::acctngFileNearlyFull,,,,,,An indication that the size of the file into which accounting information is currently being collected has exceeded the threshold percentage of its maximum file size. This notification is generated only at the time of the transition from not-exceeding to exceeding.
.1.3.6.1.2.1.60.2.0.2,ACCOUNTING-CONTROL-MIB::acctngFileFull,,,,,,An indication that the size of the file into which accounting information is currently being collected has transistioned to its maximum file size. This notification is generated (for all values of acctngAgentMode) at the time of the transition from not-full to full. If acctngAgentMode has the value 'swapOnCommand', it is also generated periodically thereafter until such time as collection of data is no longer inhibited by the file full condition.
.1.3.6.1.2.1.60.3,ACCOUNTING-CONTROL-MIB::acctngConformance,,,,,,
.1.3.6.1.2.1.60.3.1,ACCOUNTING-CONTROL-MIB::acctngGroups,,,,,,
.1.3.6.1.2.1.60.3.1.1,ACCOUNTING-CONTROL-MIB::acctngBasicGroup,,,,,,A collection of objects providing control of the basic collection of accounting data for connection-oriented networks.
.1.3.6.1.2.1.60.3.1.2,ACCOUNTING-CONTROL-MIB::acctngNotificationsGroup,,,,,,The notifications of events relating to controlling the collection of accounting data.
.1.3.6.1.2.1.60.3.2,ACCOUNTING-CONTROL-MIB::acctngCompliances,,,,,,
.1.3.6.1.2.1.60.3.2.1,ACCOUNTING-CONTROL-MIB::acctngCompliance,,,,,,The compliance statement for switches which implement the Accounting Control MIB.
.1.3.6.1.2.1.61,IANATn3270eTC-MIB::ianaTn3270eTcMib,,,,,,This module defines a set of textual conventions for use by the TN3270E-MIB and the TN3270E-RT-MIB. Any additions or changes to the contents of this MIB module must first be discussed on the tn3270e working group list at: tn3270e&list.nih.gov and approved by one of the following TN3270E working group contacts: Ed Bailey (co-chair) - elbailey&us.ibm.com Michael Boe (co-chair) - mboe&cisco.com Ken White - kennethw&vnet.ibm.com Robert Moore - remoore&us.ibm.com The above list of contacts can be altered with the approval of the two co-chairs. The Textual Conventions defined within this MIB have no security issues associated with them unless explicitly stated in their correspondingclause.
.1.3.6.1.2.1.62,APPLICATION-MIB::applicationMib,,,,,,This MIB defines objects representing generic aspects of applications that are of interest to management but typically require instrumentation within managed application elements. 
.1.3.6.1.2.1.62.1,APPLICATION-MIB::applicationMibObjects,,,,,,
.1.3.6.1.2.1.62.1.1,APPLICATION-MIB::applServiceGroup,,,,,,
.1.3.6.1.2.1.62.1.1.1,APPLICATION-MIB::applSrvNameToSrvInstTable,,not-accessible,,current,,The service name to service instance table uses service name as its primary key, and service instance identifier as its secondary key. It facilitates the identification and lookup of the instances of a given service in a system.
.1.3.6.1.2.1.62.1.1.1.1,APPLICATION-MIB::applSrvNameToSrvInstEntry,,not-accessible,applSrvName:applSrvIndex,current,,An applSrvNameToSrvInstEntry identifies an instance of a given service. The allocation and reservation of unique values for applSrvIndex is an administrative issue. An applSrvNameToSrvInstEntry exists for the lifetime of that instance of that service; the index values may not change during that lifetime. 
.1.3.6.1.2.1.62.1.1.1.1.1,APPLICATION-MIB::applSrvInstQual,OCTET,read-only,,current,,The value of applSrcInstQual provides additional information about this particular instance of this service. Although not used for indexing purposes, the value of this attribute should be sufficiently unique to be helpful to an administrator in distinguishing among service instances. 
.1.3.6.1.2.1.62.1.1.2,APPLICATION-MIB::applSrvInstToSrvNameTable,,not-accessible,,current,,The service instance to service name table uses service instance identifier as its primary key, and service name as its secondary key. Given a service instance identifier, it facilitates the lookup of the name of the service being provided.
.1.3.6.1.2.1.62.1.1.2.1,APPLICATION-MIB::applSrvInstToSrvNameEntry,,not-accessible,applSrvIndex:applSrvName,current,,An applSrvInstToSrvNameEntry maps a service instance identifier back to a service name.
.1.3.6.1.2.1.62.1.1.2.1.1,APPLICATION-MIB::applSrvName,OCTET,read-only,,current,,The human-readable name of a service. Where appropriate, as in the case where a service can be identified in terms of a single protocol, the strings should be established names such as those assigned by IANA and found in STD 2 [13], or defined by some other authority. In some cases private conventions apply and the string should in these cases be consistent with these non-standard conventions. An applicability statement may specify the service name(s) to be used. 
.1.3.6.1.2.1.62.1.1.3,APPLICATION-MIB::applSrvInstToRunApplElmtTable,,not-accessible,,current,,The service instance to running application element table uses the service instance identifier as its primary key, and the running application element index as its secondary key. This facilitates the identification of the set of running application elements providing a given instance of a service.
.1.3.6.1.2.1.62.1.1.3.1,APPLICATION-MIB::applSrvInstToRunApplElmtEntry,,not-accessible,applSrvIndex:sysApplElmtRunIndex,current,,An applSrvInstToRunApplElmtEntry identifies a running application element providing an instance of a service. Note that there may be multiple running application elements involved in the provision of an instance of a service.
.1.3.6.1.2.1.62.1.1.3.1.1,APPLICATION-MIB::applSrvIndex,Unsigned32,read-only,,current,,An applSrvIndex is the system-unique identifier of an instance of a service. The value is unique not only across all instances of a given service, but also across all services in a system. Re-use of values for this index should be avoided. No two service instances in a given system shall concurrently have the same value for this index. The value zero is excluded from the set of permitted values for this index. This allows other tables to potentially represent things which cannot be associated with a specific service instance. 
.1.3.6.1.2.1.62.1.1.4,APPLICATION-MIB::applRunApplElmtToSrvInstTable,,not-accessible,,current,,The running application element to service instance table uses the running application element index as its primary key and the service instance identifier as its secondary key. It identifies the set of services provided by a given running application element.
.1.3.6.1.2.1.62.1.1.4.1,APPLICATION-MIB::applRunApplElmtToSrvInstEntry,,not-accessible,sysApplElmtRunIndex:applSrvInstance,current,,An applRunApplElmtToSrvInstEntry serves to identify an instance of a service being provided by a given running application element. Note that a particular running application element may provide multiple services.
.1.3.6.1.2.1.62.1.1.4.1.1,APPLICATION-MIB::applSrvInstance,Unsigned32,read-only,,current,,An applSrvInstance is the system-unique identifier of an instance of a service. The value is unique not only across all instances of a given service, but also across all services. Re-use of values for this index should be avoided. No two service instances in a given system shall concurrently have the same value for this index. The value zero is excluded from the set of permitted values for this index. This allows other tables to potentially represent things which cannot be associated with a specific service instance. This attribute is semantically identical to applSrvIndex.
.1.3.6.1.2.1.62.1.2,APPLICATION-MIB::applChannelGroup,,,,,,
.1.3.6.1.2.1.62.1.2.1,APPLICATION-MIB::applOpenChannelTable,,not-accessible,,current,,The applOpenChannelTable reports information on open channels for running application elements and for service instances. This table is indexed by applElmtOrSvc, applElmtOrSvcId, and applOpenChannelIndex. This effectively groups all entries for a given running application element or service instance together. ApplChannelIndex uniquely identifies an open channel (and, consequently, a file or connection) within the context of a particular running application element or service instance. Some of the information in this table is available through both sixty-four and thirty-two bit counters. The sixty-four bit counters are not accessible in protocols that do not support this data type.
.1.3.6.1.2.1.62.1.2.1.1,APPLICATION-MIB::applOpenChannelEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applOpenChannelIndex,current,,An applOpenChannelEntry indicates that a channel has been opened by this running application element or service instance and is still open. Note that if a file has been opened multiple times, even by the same process, it will have multiple channel entries.
.1.3.6.1.2.1.62.1.2.1.1.1,APPLICATION-MIB::applElmtOrSvc,INTEGER,not-accessible,,current,service(1):element(2),The applElmtOrSvc attribute serves as an index for tables that can hold information both for individual running application elements as well as for service instances. If the value is service(1), the row contains information gathered at the level of a service. If the value is element(2), the row contains information for an individual running application element.
.1.3.6.1.2.1.62.1.2.1.1.2,APPLICATION-MIB::applElmtOrSvcId,Unsigned32,not-accessible,,current,,The applElmtOrSvcId attribute is used as an index in conjunction with the applElmtOrSvc attribute. When the value of applElmtOrSvc is service(1), this attribute's value corresponds to that of applSrvIndex, when the value of applElmtOrSvc is element(2), this attribute's value corresponds to sysApplElmtRunIndex.
.1.3.6.1.2.1.62.1.2.1.1.3,APPLICATION-MIB::applOpenChannelIndex,Unsigned32,not-accessible,,current,,This attribute serves to uniquely identify this open connection in the context of the running application element or service instance. Where suitable, the application's native descriptor number should be used.
.1.3.6.1.2.1.62.1.2.1.1.4,APPLICATION-MIB::applOpenChannelOpenTime,TimeTicks,read-only,,current,,This attribute records the value of sysUpTime.0 when this channel was opened and this entry was added to this table. This attribute serves as a discontinuity indicator for the counter attributes in this entry and for any corresponding entries in the applOpenConnectionTable, applOpenFileTable, and the applTransactionStreamTable.
.1.3.6.1.2.1.62.1.2.1.1.5,APPLICATION-MIB::applOpenChannelReadRequests,Counter64,read-only,,current,,This attribute reports the number of read requests for this channel. All read requests for this channel by this entity, regardless of completion status, are included in this count. Read requests are counted in terms of system calls, rather than API calls. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.6,APPLICATION-MIB::applOpenChannelReadRequestsLow,Counter32,read-only,,current,,This attribute reports the low thirty-two bits of applOpenChannelReadRequests. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.7,APPLICATION-MIB::applOpenChannelReadFailures,Counter32,read-only,,current,,This attribute reports the number of failed read requests. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.8,APPLICATION-MIB::applOpenChannelBytesRead,Counter64,read-only,,current,,This attribute reports the number of bytes read from this channel. Only bytes successfully read are included in this count. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.9,APPLICATION-MIB::applOpenChannelBytesReadLow,Counter32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applOpenChannelBytesRead. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.10,APPLICATION-MIB::applOpenChannelLastReadTime,OCTET,read-only,,current,,This attribute reports the time of the most recent read request made by this entity, regardless of completion status, for this open channel. If no read requests have been made the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.2.1.1.11,APPLICATION-MIB::applOpenChannelWriteRequests,Counter64,read-only,,current,,This attribute reports the number of write requests for this channel made by this entity. All write requests for this channel, regardless of completion status, are included in this count. Write requests are counted in terms of system calls, rather than API calls. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.12,APPLICATION-MIB::applOpenChannelWriteRequestsLow,Counter32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applOpenChannelWriteRequests. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.13,APPLICATION-MIB::applOpenChannelWriteFailures,Counter32,read-only,,current,,This attribute reports the number of failed write requests. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.14,APPLICATION-MIB::applOpenChannelBytesWritten,Counter64,read-only,,current,,This attribute reports the number of bytes written to this channel. Only bytes successfully written (without errors reported by the system to the API in use by the application) are included in this count. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.15,APPLICATION-MIB::applOpenChannelBytesWrittenLow,Counter32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applOpenChannelBytesWritten. Discontinuities in this counter can be detected by monitoring the applOpenChannelOpenTime value for this entry.
.1.3.6.1.2.1.62.1.2.1.1.16,APPLICATION-MIB::applOpenChannelLastWriteTime,OCTET,read-only,,current,,This attribute reports the time of the most recent write request made by this running application element or service instance, regardless of completion status, for this open channel. If no write requests have been made, the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.2.2,APPLICATION-MIB::applOpenFileTable,,not-accessible,,current,,The applOpenFileTable reports information on open files for service instances or application elements. This table is indexed by applElmtOrSvc and applElmtOrSvcId, effectively grouping all entries for a given running service instance or application element together, and by applOpenChannelIndex, uniquely identifying an open channel (and, consequently, a file) within the context of a particular service instance or application element. Elements in this table correspond to elements in the applOpenChannelTable that represent files. For rows in the applOpenChannelTable that do not represent files, corresponding rows in this table will not exist.
.1.3.6.1.2.1.62.1.2.2.1,APPLICATION-MIB::applOpenFileEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applOpenChannelIndex,current,,An applOpenFileEntry indicates that a file has been opened by this running application element and is still open. Note that if a file has been opened multiple times, even by the same process, it will have multiple entries.
.1.3.6.1.2.1.62.1.2.2.1.1,APPLICATION-MIB::applOpenFileName,OCTET,read-only,,current,,This attribute reports the name of this open file. Wherever practical, a fully qualified path name should be reported. The values 'stdin', 'stdout', and 'stderr' are reserved in accordance with common usage when the fully qualified path name cannot be determined.
.1.3.6.1.2.1.62.1.2.2.1.2,APPLICATION-MIB::applOpenFileSizeHigh,Unsigned32,read-only,,current,,This file's current size in 2^32 byte blocks. For example, for a file with a total size of 4,294,967,296 bytes, this attribute would have a value of 1; for a file with a total size of 4,294,967,295 bytes this attribute's value would be 0.
.1.3.6.1.2.1.62.1.2.2.1.3,APPLICATION-MIB::applOpenFileSizeLow,Unsigned32,read-only,,current,,This file's current size modulo 2^32 bytes. For example, for a file with a total size of 4,294,967,296 bytes this attribute would have a value of 0; for a file with a total size of 4,294,967,295 bytes this attribute's value would be 4,294,967,295.
.1.3.6.1.2.1.62.1.2.2.1.4,APPLICATION-MIB::applOpenFileMode,INTEGER,read-only,,current,read(1):write(2):readWrite(3),This attribute reports the current mode of this file from the perspective of this running application element. These values have the following meanings: read(1) - file opened for reading only write(2) - file opened for writing only readWrite(3) - file opened for read and write. These values correspond to the POSIX/ANSI C library function fopen() 'type' parameter, using the following mappings: r -> read(1) w -> write(2) a -> write(2) + -> readWrite(3) 
.1.3.6.1.2.1.62.1.2.3,APPLICATION-MIB::applOpenConnectionTable,,not-accessible,,current,,The applOpenConnectionTable provides information about open and listening connections from the perspective of a running application element or service instance. Entries in this table are indexed by applElmtOrSvc, applElmtOrSvcID, and by applOpenChannelIndex, which serves to uniquely identify each connection in the context of a service instance or running application element. For each row in this table, a corresponding row will exist in the applOpenChannel table. For rows in the applOpenChannelTable which do not represent open or listening connections, no corresponding rows will exist in this table.
.1.3.6.1.2.1.62.1.2.3.1,APPLICATION-MIB::applOpenConnectionEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applOpenChannelIndex,current,,An applOpenConnectionEntry indicates that a running application element or service instance has an open connection. The entry has information describing that connection. In the case of a TCP transport, the element applOpenConnectionNearEndAddr and that row's applOpenConnectionFarEndAddr would correspond to a tcpConnEntry. For a UDP transport, a similar relationship exists with respect to a udpEntry.
.1.3.6.1.2.1.62.1.2.3.1.1,APPLICATION-MIB::applOpenConnectionTransport,OBJECT,read-only,,current,,The applOpenConnectionTransport attribute identifies the transport protocol in use for this connection. If it is not practical to determine the underlying transport, this attribute's value shall have a value of {0 0}.
.1.3.6.1.2.1.62.1.2.3.1.2,APPLICATION-MIB::applOpenConnectionNearEndAddr,OCTET,read-only,,current,,The applOpenConnectionNearEndAddr attribute reports the transport address and port information for the near end of this connection. If the value is not known, the value has a length of zero.
.1.3.6.1.2.1.62.1.2.3.1.3,APPLICATION-MIB::applOpenConnectionNearEndpoint,OCTET,read-only,,current,,The applOpenConnectionNearEndpoint attribute reports the fully-qualified domain name and port information for the near end of this connection. The format of this attribute for TCP and UDP-based protocols is the fully-qualified domain name immediately followed by a colon which is immediately followed by the decimal representation of the port number. If the value is not known, the value has a length of zero.
.1.3.6.1.2.1.62.1.2.3.1.4,APPLICATION-MIB::applOpenConnectionFarEndAddr,OCTET,read-only,,current,,The applOpenConnectionFarEndAddr attribute reports the transport address and port information for the far end of this connection. If not known, as in the case of a connectionless transport, the value of this attribute shall be a zero-length string.
.1.3.6.1.2.1.62.1.2.3.1.5,APPLICATION-MIB::applOpenConnectionFarEndpoint,OCTET,read-only,,current,,The applOpenConnectionFarEndpoint attribute reports the fully-qualified domain name and port information for the far end of this connection. The format of this attribute for TCP and UDP-based protocols is the fully-qualified domain name immediately followed by a colon which is immediately followed by the decimal representation of the port number. If not known, as in the case of a connectionless transport, the value of this attribute shall be a zero-length string.
.1.3.6.1.2.1.62.1.2.3.1.6,APPLICATION-MIB::applOpenConnectionApplication,OCTET,read-only,,current,,The applOpenConnectionApplication attribute identifies the application layer protocol in use. If not known, the value of this attribute shall be a zero-length string. When possible, protocol names should be those used in the 'ASSIGNED NUMBERS' [13]. For example, an SMTP mail server would use 'SMTP'.
.1.3.6.1.2.1.62.1.2.4,APPLICATION-MIB::applTransactionStreamTable,,not-accessible,,current,,The applTransactionStreamTable contains common information for transaction statistic accumulation.
.1.3.6.1.2.1.62.1.2.4.1,APPLICATION-MIB::applTransactionStreamEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applOpenChannelIndex,current,,An applTransactionStreamEntry contains information for a single transaction stream. A transaction stream can be a network connection, file, or other source of transactions.
.1.3.6.1.2.1.62.1.2.4.1.1,APPLICATION-MIB::applTransactStreamDescr,OCTET,read-only,,current,,The applTransactStreamDescr attribute provides a human-readable description of this transaction stream. If no descriptive information is available, this attribute's value shall be a zero-length string.
.1.3.6.1.2.1.62.1.2.4.1.2,APPLICATION-MIB::applTransactStreamUnitOfWork,OCTET,read-only,,current,,The applTransactStreamUnitOfWork attribute provides a human-readable definition of what the unit of work is for this transaction stream. If no descriptive information is available, this attribute's value shall be a zero-length string.
.1.3.6.1.2.1.62.1.2.4.1.3,APPLICATION-MIB::applTransactStreamInvokes,Counter64,read-only,,current,,Cumulative count of requests / invocations issued. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.4,APPLICATION-MIB::applTransactStreamInvokesLow,Counter32,read-only,,current,,This counter corresponds to the low thirty-two bits of applTransactStreamInvokes. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.5,APPLICATION-MIB::applTransactStreamInvCumTimes,Counter32,read-only,,current,,The applTransactStreamInvCumTimes attribute reports the cumulative sum of the lengths of the intervals measured between the transmission of requests and the receipt of (the first of) the corresponding response(s). Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.6,APPLICATION-MIB::applTransactStreamInvRspTimes,Counter32,read-only,,current,,The applTransactStreamInvRspTimes attribute reports the cumulative sum of the lengths of the intervals measured between the receipt of the first and last of multiple responses to a request. For transaction streams which do not permit multiple responses to a single request, this attribute will be constant. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.7,APPLICATION-MIB::applTransactStreamPerforms,Counter64,read-only,,current,,Cumulative count of transactions performed. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.8,APPLICATION-MIB::applTransactStreamPerformsLow,Counter32,read-only,,current,,This counter reports the low thirty-two bits of applTransactStreamPerforms. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.9,APPLICATION-MIB::applTransactStreamPrfCumTimes,Counter32,read-only,,current,,The applTransactStreamPrfCumTimes attribute reports the cumulative sum of the interval lengths measured between receipt of requests and the transmission of the corresponding responses. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.4.1.10,APPLICATION-MIB::applTransactStreamPrfRspTimes,Counter32,read-only,,current,,For each transaction performed, the elapsed time between when the first response is enqueued and when the last response is enqueued is added to this cumulative sum. For single-response protocols, the value of applTransactStreamPrfRspTimes will be constant. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.5,APPLICATION-MIB::applTransactFlowTable,,not-accessible,,current,,The applTransactFlowTable contains entries, organized by application instance or running application element, direction of flow, and type (request/response) for each open transaction stream. The simple model of a transaction used here looks like this: invoker | Request | performer | - - - - - - > | | | | Response | | < - - - - - - | | | Since in some protocols it is possible for an entity to take on both the invoker and performer roles, information here is accumulated for transmitted and received requests, as well as for transmitted and received responses. Counts are maintained for both transactions and bytes transferred.
.1.3.6.1.2.1.62.1.2.5.1,APPLICATION-MIB::applTransactFlowEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applOpenChannelIndex:applTransactFlowDirection:applTransactFlowReqRsp,current,,An applTransactFlowEntry reports transaction throughput information for requests or response in a particular direction (transmit / receive) for a transaction stream. Entries in this table correspond to those in the applTransactionStreamTable with identical values for the applElmtOrSvc, applElmtOrSvcId, and applOpenChannelIndex. For all counter objects in one of these entries, the corresponding (same value for applElmtOrSvc, applElmtOrSvcId, and applOpenChannelIndex) applOpenChannelOpenTime object serves as a discontinuity indicator. 
.1.3.6.1.2.1.62.1.2.5.1.1,APPLICATION-MIB::applTransactFlowDirection,INTEGER,not-accessible,,current,transmit(1):receive(2),The applTransactFlowDirection index serves to identify an entry as containing information pertaining to the transmit (1) or receive (2) flow of a transaction stream.
.1.3.6.1.2.1.62.1.2.5.1.2,APPLICATION-MIB::applTransactFlowReqRsp,INTEGER,not-accessible,,current,request(1):response(2),The value of the applTransactFlowReqRsp index indicates whether this entry contains information on requests (1), or responses (2).
.1.3.6.1.2.1.62.1.2.5.1.3,APPLICATION-MIB::applTransactFlowTrans,Counter64,read-only,,current,,The applTransactFlowTrans attribute reports the number of request/response transactions (as indicated by the applTransactFlowReqRsp index) received/generated (as indicated by the applTransactFlowDirection index) that this service instance or running application element has processed for this transaction stream. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.5.1.4,APPLICATION-MIB::applTransactFlowTransLow,Counter32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applTransactFlowTrans. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.5.1.5,APPLICATION-MIB::applTransactFlowBytes,Counter64,read-only,,current,,The applTransactFlowBytes attribute reports the number of request/response (as indicated by the applTransactFlowReqRsp index) bytes received/generated (as indicated by the applTransactFlowDirection index) handled by this application element or service instance on this transaction stream. All application layer bytes are included in this count, including any application layer wrappers, headers, or other overhead. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.5.1.6,APPLICATION-MIB::applTransactFlowBytesLow,Counter32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applTransactFlowBytes. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.5.1.7,APPLICATION-MIB::applTransactFlowTime,OCTET,read-only,,current,,The applTransactFlowTime attribute records the time of the processing (receipt or transmission as indicated by the applTransactFlowDirection index) by this running application element or service instance of the most recent request/response (as indicated by the applTransactFlowReqRsp index) on this transaction stream. If no requests/responses been received/transmitted by this entity over this transaction stream, the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.2.6,APPLICATION-MIB::applTransactKindTable,,not-accessible,,current,,The applTransactKindTable provides transaction statistics broken down by kinds of transaction. The definition of the kinds of transactions is specific to the application protocol in use, and may be documented in the form of an applicability statement. 
.1.3.6.1.2.1.62.1.2.6.1,APPLICATION-MIB::applTransactKindEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applOpenChannelIndex:applTransactFlowDirection:applTransactFlowReqRsp:applTransactKind,current,,An applTransactKindEntry reports information for a specific service instance or running application element's use of a specific transaction stream in a particular direction in requests or responses (as indicated by the applTransactFlowReqRsp index) broken down by transaction kind, as indicated by the applTransactKind index. Discontinuities in any of the counters in an entry can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.6.1.1,APPLICATION-MIB::applTransactKind,OCTET,not-accessible,,current,,The applTransactKind index is the human-readable identifier for a particular transaction kind within the context of an application protocol. The values to be used for a particular protocol may be identified in an applicability statement.
.1.3.6.1.2.1.62.1.2.6.1.2,APPLICATION-MIB::applTransactKindTrans,Counter64,read-only,,current,,The applTransactKindTrans attribute reports the number of request/response (as indicated by the applTransactFlowReqRsp index) transactions received/generated (as indicated by the applTransactFlowDirection index) handled by this application instance or application element on this transaction stream for this transaction kind. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.6.1.3,APPLICATION-MIB::applTransactKindTransLow,Counter32,read-only,,current,,The applTransactKindTransLow attribute reports the low thirty-two bits of applTransactKindTrans. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.6.1.4,APPLICATION-MIB::applTransactKindBytes,Counter64,read-only,,current,,The applTransactKindBytes attribute reports the number of request/response (as indicated by the applTransactFlowReqRsp index) bytes received/generated (as indicated by the applTransactFlowDirection index) handled by this application element on this transaction stream for this transaction kind. All application layer bytes are included in this count, including any application layer wrappers, headers, or other overhead. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.6.1.5,APPLICATION-MIB::applTransactKindBytesLow,Counter32,read-only,,current,,The applTransactKindBytesLow attribute corresponds to the low thirty-two bits of applTransactKindBytes. Discontinuities in this counter can be detected by monitoring the corresponding instance of applOpenChannelOpenTime.
.1.3.6.1.2.1.62.1.2.6.1.6,APPLICATION-MIB::applTransactKindTime,OCTET,read-only,,current,,The applTransactKindTime attribute records the time of the processing (receipt or transmission as indicated by the applTransactFlowDirection index) by this running application element or service instance of the most recent request/response (as indicated by the applTransactFlowReqRsp index) of this kind of transaction on this transaction stream. If no requests/responses of this kind been received/transmitted by this running application element or service instance over this transaction stream, the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.3,APPLICATION-MIB::applPastChannelGroup,,,,,,
.1.3.6.1.2.1.62.1.3.1,APPLICATION-MIB::applPastChannelControlTable,,not-accessible,,current,,The applPastChannelControlTable controls the accumulation of history information about channels from the perspective of service instances and running application elements. Entries in this table are indexed by applElmtOrSvc and applElmtOrSvcId, giving control of channel history accumulation at the level of each service instance and running application element.
.1.3.6.1.2.1.62.1.3.1.1,APPLICATION-MIB::applPastChannelControlEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId,current,,An applPastChannelControlEntry provides the ability to control the retention of channel history information by service instances and running application elements.
.1.3.6.1.2.1.62.1.3.1.1.1,APPLICATION-MIB::applPastChannelControlCollect,INTEGER,read-write,,current,enabled(1):frozen(2):disabled(3),When the value of applPastChannelControlCollect is 'enabled', each time the corresponding running application element or service instance closes an open channel a new entry will be added to the applPastChannelTable. When the value of applPastChannelControlCollect is 'frozen', no new entries are added to the applPastChannelTable for this running application element or service instance, and old entries are not aged out. When the value of applPastChannelControlCollect is 'disabled', all entries are removed from applPastChannelTable for this running application or service instance, and no new entries are added.
.1.3.6.1.2.1.62.1.3.1.1.2,APPLICATION-MIB::applPastChannelControlMaxRows,Unsigned32,read-write,,current,,The maximum number of entries allowed in the applPastChannelTable for this running application element or service instance. Once the number of rows for this running application element or service instance in the applPastChannelTable reaches this value, when new entries are to be added the management subsystem will make room for them by removing the oldest entries. Entries will be removed on the basis of oldest applPastChannelCloseTime value first.
.1.3.6.1.2.1.62.1.3.1.1.3,APPLICATION-MIB::applPastChannelControlTimeLimit,Unsigned32,read-write,,current,,The maximum time in seconds which an entry for this running application element or service instance may exist in the applPastChannelTable before it is removed. Any entry that is older than this value will be removed (aged out) from the table, unless the applPastChannelControlCollect is set to 'frozen'. Note that an entry may be aged out prior to reaching this time limit if it is the oldest entry in the table and must be removed to make space for a new entry so as to not exceed applPastChannelControlMaxRows, or if the applPastChannelControlCollect is set to 'disabled'.
.1.3.6.1.2.1.62.1.3.1.1.4,APPLICATION-MIB::applPastChannelControlRemItems,Counter32,read-only,,current,,The applPastChannelControlRemItems attribute reports the number of applPastChannelControlTable entries for this running application element or service instance that were deleted in order to make room for new history entries. This count does NOT include entries deleted for the following reasons: - the corresponding applPastChannelControlCollect attribute has been set to 'disabled' - the entry has been in the table longer that the time limit indicated by the corresponding applPastChannelControlTimeLimit. 
.1.3.6.1.2.1.62.1.3.2,APPLICATION-MIB::applPastChannelTable,,not-accessible,,current,,The applPastChannelTable provides history information about channels from the perspective of running application elements and service instances. Entries in this table are indexed by applElmtOrSvc, applElmtOrSvcId, and by applPastChannelIndex, which serves to uniquely identify each former channel in the context of a running application element or service instance. Note that the value of applPastChannelIndex is independent of the value applOpenChannelIndex had when this channel was open. Entries for closed channels for a given running application element or service instance can be added to this table only if its entry in the applPastChannelControlTable has the value 'enabled' for the attribute applPastChannelControlCollect. Entries for closed channels are removed under the following circumstances: - the running application element or service instance no longer exists - the corresponding applPastChannelControlCollect attribute has been set to 'disabled' - the entry has been in the table longer that the time limit indicated by the corresponding applPastChannelControlTimeLimit and the value of applPastChannelControlCollect is not 'frozen' - this is the oldest entry for the running application element or service instance in question and the addition of a new element would otherwise cause applPastChannelControlMaxRows to be exceeded for this running application element or service instance. - a value of applPastChannelIndex has been re-used. Note that under normal circumstances, this is unlikely. Removal/replacement of an entry under the last two conditions causes the corresponding applPastChannelControlRemItems to be incremented.
.1.3.6.1.2.1.62.1.3.2.1,APPLICATION-MIB::applPastChannelEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applPastChannelIndex,current,,An applPastChannelEntry indicates that a running application element or service instance once had an open channel, which is now closed. The entry has information describing that channel.
.1.3.6.1.2.1.62.1.3.2.1.1,APPLICATION-MIB::applPastChannelIndex,Unsigned32,not-accessible,,current,,This attribute serves to uniquely identify this closed channel in the context of the running application element or service instance. This attribute has no other semantics. Note that the value of applPastChannelIndex is independent of the value applOpenChannelIndex had when this channel was active. In issuing this index value, the implementation must avoid re-issuing an index value which has already been assigned to an entry which has not yet been deleted due to age or space considerations. The value zero is excluded from the set of permitted values for this index in order to permit other tables to possibly represent information that cannot be associated with a specific entry in this table. 
.1.3.6.1.2.1.62.1.3.2.1.2,APPLICATION-MIB::applPastChannelOpenTime,OCTET,read-only,,current,,This attribute records the time when this channel was originally opened. Note that this information is quite different from applOpenChannelOpenTime, which is used for the detection of counter discontinuities.
.1.3.6.1.2.1.62.1.3.2.1.3,APPLICATION-MIB::applPastChannelCloseTime,OCTET,read-only,,current,,This attribute records the time when this channel was closed.
.1.3.6.1.2.1.62.1.3.2.1.4,APPLICATION-MIB::applPastChannelReadRequests,Counter64,read-only,,current,,This attribute records the number of read requests for this channel made by this running application element or service instance. All read requests for this channel by this running application element or service instance, regardless of completion status, are included in this count. Read requests are counted in terms of system calls, rather than API calls.
.1.3.6.1.2.1.62.1.3.2.1.5,APPLICATION-MIB::applPastChannelReadReqsLow,Unsigned32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applPastChannelReadRequests.
.1.3.6.1.2.1.62.1.3.2.1.6,APPLICATION-MIB::applPastChannelReadFailures,Unsigned32,read-only,,current,,This attribute reports the number of failed read requests.
.1.3.6.1.2.1.62.1.3.2.1.7,APPLICATION-MIB::applPastChannelBytesRead,Counter64,read-only,,current,,This attribute reports the number of bytes read from this channel by this running application element or service instance. Only bytes successfully read are included in this count. 
.1.3.6.1.2.1.62.1.3.2.1.8,APPLICATION-MIB::applPastChannelBytesReadLow,Unsigned32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applPastChannelBytesRead.
.1.3.6.1.2.1.62.1.3.2.1.9,APPLICATION-MIB::applPastChannelLastReadTime,OCTET,read-only,,current,,This attribute reports the time of the most recent read request made by this running application element or service instance regardless of completion status, for this former channel. If no read requests have been made , the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.3.2.1.10,APPLICATION-MIB::applPastChannelWriteRequests,Counter64,read-only,,current,,The applPastChannelWriteRequests attribute reports the number of write requests, regardless of completion status, made by this running application element or service instance for this former channel. Write requests are counted in terms of system calls, rather than API calls.
.1.3.6.1.2.1.62.1.3.2.1.11,APPLICATION-MIB::applPastChannelWriteReqsLow,Unsigned32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applPastChannelWriteRequests.
.1.3.6.1.2.1.62.1.3.2.1.12,APPLICATION-MIB::applPastChannelWriteFailures,Unsigned32,read-only,,current,,This attribute reports the number of failed write requests.
.1.3.6.1.2.1.62.1.3.2.1.13,APPLICATION-MIB::applPastChannelBytesWritten,Counter64,read-only,,current,,This attribute reports the number of bytes written to this former channel by this running application element or service instance. Only bytes successfully written (no errors reported by the API in use by the application) are included in this count.
.1.3.6.1.2.1.62.1.3.2.1.14,APPLICATION-MIB::applPastChannelBytesWritLow,Unsigned32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applPastChannelBytesWritten.
.1.3.6.1.2.1.62.1.3.2.1.15,APPLICATION-MIB::applPastChannelLastWriteTime,OCTET,read-only,,current,,The applPastChannelLastWriteTime attribute reports the time of the most recent write request made by this running application element or service instance, regardless of completion status, for this former channel. If no write requests have been made the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.3.3,APPLICATION-MIB::applPastFileTable,,not-accessible,,current,,The applPastFileTable supplements the applPastChannelTable for entries corresponding to channels which were files. The indexing structure is identical to applPastChannelTable. An entry exists in the applPastFileTable only if there is a corresponding (same index values) entry in the applPastChannelTable and if the channel was a file. Entries for closed files are removed when the corresponding entries are removed from the applPastChannelTable.
.1.3.6.1.2.1.62.1.3.3.1,APPLICATION-MIB::applPastFileEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applPastChannelIndex,current,,An applPastFileEntry provides additional, file-specific information to complement the corresponding applPastChannelEntry for a channel which was a file.
.1.3.6.1.2.1.62.1.3.3.1.1,APPLICATION-MIB::applPastFileName,OCTET,read-only,,current,,This attribute records the last known value of applOpenFileName before the channel was closed.
.1.3.6.1.2.1.62.1.3.3.1.2,APPLICATION-MIB::applPastFileSizeHigh,Unsigned32,read-only,,current,,This attribute records the value of applOpenFileSizeHigh at the time this channel was closed. For example, for a file with a total size of 4,294,967,296 bytes, this attribute would have a value of 1; for a file with a total size of 4,294,967,295 bytes this attribute's value would be 0.
.1.3.6.1.2.1.62.1.3.3.1.3,APPLICATION-MIB::applPastFileSizeLow,Unsigned32,read-only,,current,,This attribute records the value of applOpenFileSizeLow at the time this channel was closed. For example, for a file with a total size of 4,294,967,296 bytes this attribute would have a value of 0; for a file with a total size of 4,294,967,295 bytes this attribute's value would be 4,294,967,295.
.1.3.6.1.2.1.62.1.3.3.1.4,APPLICATION-MIB::applPastFileMode,INTEGER,read-only,,current,read(1):write(2):readWrite(3),This attribute records the value of applOpenFileMode at the time this channel was closed. 
.1.3.6.1.2.1.62.1.3.4,APPLICATION-MIB::applPastConTable,,not-accessible,,current,,The applPastConTable supplements the applPastChannelTable for entries corresponding to channels which were connections. The indexing structure is identical to applPastChannelTable. An entry exists in the applPastConTable only if there is a corresponding (same index values) entry in the applPastChannelTable and if the channel was a connection. Entries for closed connections are removed when the corresponding entries are removed from the applPastChannelTable.
.1.3.6.1.2.1.62.1.3.4.1,APPLICATION-MIB::applPastConEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applPastChannelIndex,current,,An applPastConEntry provides additional, connection-specific information to complement the corresponding applPastChannelEntry for a channel which was a connection.
.1.3.6.1.2.1.62.1.3.4.1.1,APPLICATION-MIB::applPastConTransport,OBJECT,read-only,,current,,The applPastConTransport attribute identifies the transport protocol that was in use for this former connection. If the transport protocol could not be determined, the value { 0 0 } shall be used.
.1.3.6.1.2.1.62.1.3.4.1.2,APPLICATION-MIB::applPastConNearEndAddr,OCTET,read-only,,current,,The applPastConNearEndAddr attribute reports the transport address and port information for the near end of this former connection. If the information could not be determined, the value shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.4.1.3,APPLICATION-MIB::applPastConNearEndpoint,OCTET,read-only,,current,,The applPastConNearEndpoint attribute reports the fully-qualified domain name and port information for the near end of this former connection. The format of this attribute for TCP and UDP-based protocols is the fully-qualified domain name immediately followed by a colon which is immediately followed by the decimal representation of the port number. If the information could not be determined, the value shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.4.1.4,APPLICATION-MIB::applPastConFarEndAddr,OCTET,read-only,,current,,The applPastConFarEnd attribute reports the transport address and port information for the far end of this former connection. If not known, as in the case of a connectionless transport, the value of this attribute shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.4.1.5,APPLICATION-MIB::applPastConFarEndpoint,OCTET,read-only,,current,,The applPastConFarEndpoint attribute reports the transport address and port information for the far end of this former connection. The format of this attribute for TCP and UDP-based protocols is the fully-qualified domain name immediately followed by a colon which is immediately followed by the decimal representation of the port number. If not known, as in the case of a connectionless transport, the value of this attribute shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.4.1.6,APPLICATION-MIB::applPastConApplication,OCTET,read-only,,current,,The applPastConApplication attribute identifies the application layer protocol that was in use. Where possible, the values defined in [13] shall be used. If not known, the value of this attribute shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.5,APPLICATION-MIB::applPastTransStreamTable,,not-accessible,,current,,The applPastTransStreamTable contains common information for historical transaction statistics.
.1.3.6.1.2.1.62.1.3.5.1,APPLICATION-MIB::applPastTransStreamEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applPastChannelIndex,current,,An applPastTransStreamEntry contains information for a single former transaction stream. A transaction stream could have been a network connection, file, or other source of transactions.
.1.3.6.1.2.1.62.1.3.5.1.1,APPLICATION-MIB::applPastTransStreamDescr,OCTET,read-only,,current,,The applPastTransStreamDescr attribute provides a human-readable description of this transaction stream. If no descriptive information is available, this attribute's value shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.5.1.2,APPLICATION-MIB::applPastTransStreamUnitOfWork,OCTET,read-only,,current,,The applPastTransStreamUnitOfWork attribute provides a human-readable definition of what the unit of work is for this transaction stream. If no descriptive information is available, this attribute's value shall be a zero-length string.
.1.3.6.1.2.1.62.1.3.5.1.3,APPLICATION-MIB::applPastTransStreamInvokes,Counter64,read-only,,current,,Cumulative count of requests / invocations issued for this transaction stream when it was active.
.1.3.6.1.2.1.62.1.3.5.1.4,APPLICATION-MIB::applPastTransStreamInvokesLow,Unsigned32,read-only,,current,,This object corresponds to the low thirty-two bits of applPastTransStreamInvokes.
.1.3.6.1.2.1.62.1.3.5.1.5,APPLICATION-MIB::applPastTransStreamInvCumTimes,Unsigned32,read-only,,current,,The applPastTransStreamInvCumTimes attribute reports the cumulative sum of the lengths of the intervals times measured between the transmission of requests and the receipt of (the first of) the corresponding response(s).
.1.3.6.1.2.1.62.1.3.5.1.6,APPLICATION-MIB::applPastTransStreamInvRspTimes,Unsigned32,read-only,,current,,The applPastTransStreamInvRspTimes attribute reports the cumulative sum of the lengths of the intervals measured between the receipt of the first and last of multiple responses to a request. For transaction streams which do not permit multiple responses to a single request, this attribute will be zero.
.1.3.6.1.2.1.62.1.3.5.1.7,APPLICATION-MIB::applPastTransStreamPerforms,Counter64,read-only,,current,,Total number of transactions performed.
.1.3.6.1.2.1.62.1.3.5.1.8,APPLICATION-MIB::applPastTransStreamPerformsLow,Unsigned32,read-only,,current,,This objecy reports the low thirty-two bits of applPastTransStreamPerforms.
.1.3.6.1.2.1.62.1.3.5.1.9,APPLICATION-MIB::applPastTransStreamPrfCumTimes,Unsigned32,read-only,,current,,The applPastTransStreamPrfCumTimes attribute reports the cumulative sum of the lengths of the intervals measured between receipt of requests and the transmission of the corresponding responses.
.1.3.6.1.2.1.62.1.3.5.1.10,APPLICATION-MIB::applPastTransStreamPrfRspTimes,Unsigned32,read-only,,current,,For each transaction performed, the elapsed time between when the first response is enqueued and when the last response is enqueued is added to this cumulative sum. For single-response protocols, the value of applPastTransStreamPrfRspTimes will be zero.
.1.3.6.1.2.1.62.1.3.6,APPLICATION-MIB::applPastTransFlowTable,,not-accessible,,current,,The applPastTransFlowTable contains entries, organized by application instance or running application element, direction of flow, and type (request/response) for each former transaction stream. The simple model of a transaction used here looks like this: invoker | Request | performer | - - - - - - > | | | | Response | | < - - - - - - | | | Since in some protocols it is possible for an entity to take on both the invoker and performer roles, information here is accumulated for transmitted and received requests, as well as for transmitted and received responses. Counts are maintained for both transactions and bytes transferred.
.1.3.6.1.2.1.62.1.3.6.1,APPLICATION-MIB::applPastTransFlowEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applPastChannelIndex:applPastTransFlowDirection:applPastTransFlowReqRsp,current,,An applPastTransFlowEntry records transaction throughput information for requests or response in a particular direction (transmit / receive) for a transaction stream. Entries in this table correspond to those in the applPastTransStreamTable with identical values for the applElmtOrSvc, applElmtOrSvcId, and the applPastChannelIndex.
.1.3.6.1.2.1.62.1.3.6.1.1,APPLICATION-MIB::applPastTransFlowDirection,INTEGER,not-accessible,,current,transmit(1):receive(2),The applPastTransFlowDirection index serves to identify an entry as containing information pertaining to the transmit (1) or receive (2) flow of a past transaction stream. This index corresponds to applTransactFlowDirection.
.1.3.6.1.2.1.62.1.3.6.1.2,APPLICATION-MIB::applPastTransFlowReqRsp,INTEGER,not-accessible,,current,request(1):response(2),The value of the applPastTransFlowReqRsp index indicates whether this entry contains information on requests (1), or responses (2). This index corresponds to applTransactFlowReqRsp.
.1.3.6.1.2.1.62.1.3.6.1.3,APPLICATION-MIB::applPastTransFlowTrans,Counter64,read-only,,current,,The applPastTransFlowTrans attribute reports the number of request/response (as indicated by the applPastTransFlowReqRsp index) transactions received/generated (as indicated by the applPastTransFlowDirection index) handled on this transaction stream.
.1.3.6.1.2.1.62.1.3.6.1.4,APPLICATION-MIB::applPastTransFlowTransLow,Unsigned32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applPastTransFlowTrans.
.1.3.6.1.2.1.62.1.3.6.1.5,APPLICATION-MIB::applPastTransFlowBytes,Counter64,read-only,,current,,The applPastTransFlowBytes attribute reports the number of request/response (as indicated by the applPastTransFlowReqRsp index) bytes received/generated (as indicated by the applPastTransFlowDirection index) handled on this transaction stream. All application layer bytes are included in this count, including any application layer wrappers, headers, or other overhead.
.1.3.6.1.2.1.62.1.3.6.1.6,APPLICATION-MIB::applPastTransFlowBytesLow,Unsigned32,read-only,,current,,This attribute corresponds to the low thirty-two bits of applPastTransFlowBytes.
.1.3.6.1.2.1.62.1.3.6.1.7,APPLICATION-MIB::applPastTransFlowTime,OCTET,read-only,,current,,The applPastTransFlowTime attribute records the time of the processing (receipt or transmission as indicated by the applPastTransFlowDirection index) of the last request/response (as indicated by the applPastTransFlowReqRsp index) on this transaction stream. If no requests/responses been received/transmitted by this entity over this transaction stream, the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.3.7,APPLICATION-MIB::applPastTransKindTable,,not-accessible,,current,,The applPastTransKindTable provides transaction statistics broken down by kinds of transaction. The definition of the kinds of transactions is specific to the application protocol in use, and may be documented in the form of an applicability statement. 
.1.3.6.1.2.1.62.1.3.7.1,APPLICATION-MIB::applPastTransKindEntry,,not-accessible,applElmtOrSvc:applElmtOrSvcId:applPastChannelIndex:applPastTransFlowDirection:applPastTransFlowReqRsp:applPastTransKind,current,,An applPastTransKindEntry reports historical data for a specific service instance or running application element's use of a specific transaction stream in a particular direction in requests or responses (as indicated by the applPastTransFlowReqRsp index) broken down by transaction kind, as indicated by the applPastTransKind index.
.1.3.6.1.2.1.62.1.3.7.1.1,APPLICATION-MIB::applPastTransKind,OCTET,not-accessible,,current,,The applPastTransKind index is the human-readable identifier for a particular transaction kind within the context of an application protocol. The values to be used for a particular protocol may be identified in an applicability statement. This index corresponds to applTransactKind.
.1.3.6.1.2.1.62.1.3.7.1.2,APPLICATION-MIB::applPastTransKindTrans,Counter64,read-only,,current,,For this transaction stream, this attribute records the total number of transactions of the type identified by the indexes. The type is characterized according to the receive/transmit direction (applPastTransFlowDirecton), whether it was a request or a response (applPastTransFlowReqRsp), and the protocol-specific transaction kind (applPastTransKind). stream for this transaction kind.
.1.3.6.1.2.1.62.1.3.7.1.3,APPLICATION-MIB::applPastTransKindTransLow,Unsigned32,read-only,,current,,The applPastTransKindTransLow attribute reports the low thirty-two bits of applPastTransKindTrans.
.1.3.6.1.2.1.62.1.3.7.1.4,APPLICATION-MIB::applPastTransKindBytes,Counter64,read-only,,current,,For this transaction stream and transaction kind, the applPastTransKindBytes attribute reports the number of bytes received or generated (as indicated by the applPastTransFlowDirection index) in requests or responses (as indicated by the applPastTransFlowReqRsp index). All application layer bytes are included in this count, including any application layer wrappers, headers, or other overhead.
.1.3.6.1.2.1.62.1.3.7.1.5,APPLICATION-MIB::applPastTransKindBytesLow,Unsigned32,read-only,,current,,The applPastTransKindBytesLow attribute corresponds to the low thirty-two bits of applPastTransKindBytes.
.1.3.6.1.2.1.62.1.3.7.1.6,APPLICATION-MIB::applPastTransKindTime,OCTET,read-only,,current,,The applPastTransKindTime attribute records the time of the processing (receipt or transmission as indicated by the applPastTransFlowDirection index) of the last request/response (as indicated by the applPastTransFlowReqRsp index) of this kind of transaction on this transaction stream. If no requests/responses of this kind were received/transmitted over this transaction stream, the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.4,APPLICATION-MIB::applElmtRunControlGroup,,,,,,
.1.3.6.1.2.1.62.1.4.1,APPLICATION-MIB::applElmtRunStatusTable,,not-accessible,,current,,This table provides information on running application elements, complementing information available in the correspondingly indexed sysApplElmtRunTable [31].
.1.3.6.1.2.1.62.1.4.1.1,APPLICATION-MIB::applElmtRunStatusEntry,,not-accessible,sysApplElmtRunIndex,current,,An applElmtRunStatusEntry contains information to support the control and monitoring of a single running application element.
.1.3.6.1.2.1.62.1.4.1.1.1,APPLICATION-MIB::applElmtRunStatusSuspended,INTEGER,read-only,,current,true(1):false(2),The applElmtRunStatusSuspended attribute reports whether processing by this running application element has been suspended, whether by management request or by other means.
.1.3.6.1.2.1.62.1.4.1.1.2,APPLICATION-MIB::applElmtRunStatusHeapUsage,Unsigned32,read-only,,current,,The applElmtRunStatusHeapUsage reports the current approximate heap usage by this running application element.
.1.3.6.1.2.1.62.1.4.1.1.3,APPLICATION-MIB::applElmtRunStatusOpenConnections,Unsigned32,read-only,,current,,The applElmtRunStatusOpenConnections attribute reports the current number of open connections in use by this running application element.
.1.3.6.1.2.1.62.1.4.1.1.4,APPLICATION-MIB::applElmtRunStatusOpenFiles,Gauge32,read-only,,current,,The applElmtRunStatusOpenFiles attribute reports the current number of open files in use by this running application element.
.1.3.6.1.2.1.62.1.4.1.1.5,APPLICATION-MIB::applElmtRunStatusLastErrorMsg,OCTET,read-only,,current,,The applElmtRunStatusLastErrorMessage attribute reports the most recent error message (typically written to stderr or a system error logging facility) from this running application element. If no such message has yet been generated, the value of this attribute shall be a zero-length string.
.1.3.6.1.2.1.62.1.4.1.1.6,APPLICATION-MIB::applElmtRunStatusLastErrorTime,OCTET,read-only,,current,,The applElmtRunStatusLastErrorTime attribute reports the time of the most recent error message in applElmtRunStatusLastErrorMsg. If no such message has yet been generated, the value of this attribute shall be '0000000000000000'H 
.1.3.6.1.2.1.62.1.4.2,APPLICATION-MIB::applElmtRunControlTable,,not-accessible,,current,,This table provides the ability to control application elements, complementing information available in the correspondingly indexed sysApplElmtRunTable [31].
.1.3.6.1.2.1.62.1.4.2.1,APPLICATION-MIB::applElmtRunControlEntry,,not-accessible,sysApplElmtRunIndex,current,,An applElmtRunControlEntry contains information to support the control of a single running application element.
.1.3.6.1.2.1.62.1.4.2.1.1,APPLICATION-MIB::applElmtRunControlSuspend,INTEGER,read-write,,current,true(1):false(2),Setting this variable to 'true' requests the suspension of processing by this running application element. Setting this variable to 'false' requests that processing be resumed. The effect, if any, will be reported by the applElmtRunStatusSuspended attribute.
.1.3.6.1.2.1.62.1.4.2.1.2,APPLICATION-MIB::applElmtRunControlReconfigure,INTEGER,read-write,,current,,Changing the value of this variable requests that the running application element re-load its configuration (like SIGHUP for many UNIX-based daemons). Note that completion of a SET on this object only implies that configuration reload was initiated, not necessarily that the reload has been completed.
.1.3.6.1.2.1.62.1.4.2.1.3,APPLICATION-MIB::applElmtRunControlTerminate,INTEGER,read-write,,current,true(1):false(2),Setting the value of applElmtRunControlTerminate to 'true' requests that the running application element terminate processing and exit in an orderly manner. This is a 'polite' shutdown request. When read, this object's value will be 'false' except when orderly termination is in progress. Note that completion of a SET on this object only implies that termination was initiated, not necessarily that the termination has been completed.
.1.3.6.1.2.1.62.2,APPLICATION-MIB::applicationMibConformance,,,,,,
.1.3.6.1.2.1.62.2.1,APPLICATION-MIB::applicationMibGroups,,,,,,
.1.3.6.1.2.1.62.2.1.1,APPLICATION-MIB::applicationMonitorGroup,,,,,,This group represents the basic capabilities of this MIB.
.1.3.6.1.2.1.62.2.1.2,APPLICATION-MIB::applicationFastMonitorGroup,,,,,,This group comprises 64-bit counters mandatory in high-throughput environments, where 32-bit counters could wrap in less than an hour.
.1.3.6.1.2.1.62.2.1.3,APPLICATION-MIB::applicationTransactGroup,,,,,,This group comprises objects appropriate from monitoring transaction-structured flows.
.1.3.6.1.2.1.62.2.1.4,APPLICATION-MIB::applicationFastTransactGroup,,,,,,This group comprises 64-bit transaction counters required in high-throughput environments, where 32-bit counters could wrap in less than an hour.
.1.3.6.1.2.1.62.2.1.5,APPLICATION-MIB::applicationHistoryGroup,,,,,,This group models basic historical data.
.1.3.6.1.2.1.62.2.1.6,APPLICATION-MIB::applicationFastHistoryGroup,,,,,,This group comprises additional 64-bit objects required for recording historical data in high-volume environments, where a 32-bit integer would be insufficient.
.1.3.6.1.2.1.62.2.1.7,APPLICATION-MIB::applicationTransHistoryGroup,,,,,,This group represents historical data for transaction- structured information streams.
.1.3.6.1.2.1.62.2.1.8,APPLICATION-MIB::applicationFastTransHistoryGroup,,,,,,This group contains 64-bit objects required for historical records on high-volume transaction-structured streams, where 32-bit integers would be insufficient.
.1.3.6.1.2.1.62.2.1.9,APPLICATION-MIB::applicationRunGroup,,,,,,This group represents extensions to the system application MIB.
.1.3.6.1.2.1.62.2.2,APPLICATION-MIB::applicationMibCompliance,,,,,,The compliance statement for the application MIB.
.1.3.6.1.2.1.63,DISMAN-SCHEDULE-MIB::schedMIB,,,,,,This MIB module defines a MIB which provides mechanisms to schedule SNMP set operations periodically or at specific points in time.
.1.3.6.1.2.1.63.1,DISMAN-SCHEDULE-MIB::schedObjects,,,,,,
.1.3.6.1.2.1.63.1.1,DISMAN-SCHEDULE-MIB::schedLocalTime,OCTET,read-only,,current,,The local time used by the scheduler. Schedules which refer to calendar time will use the local time indicated by this object. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time.
.1.3.6.1.2.1.63.1.2,DISMAN-SCHEDULE-MIB::schedTable,,not-accessible,,current,,This table defines scheduled actions triggered by SNMP set operations.
.1.3.6.1.2.1.63.1.2.1,DISMAN-SCHEDULE-MIB::schedEntry,,not-accessible,schedOwner:schedName,current,,An entry describing a particular scheduled action. Unless noted otherwise, writable objects of this row can be modified independent of the current value of schedRowStatus, schedAdminStatus and schedOperStatus. In particular, it is legal to modify schedInterval and the objects in the schedCalendarGroup when schedRowStatus is active and schedAdminStatus and schedOperStatus are both enabled.
.1.3.6.1.2.1.63.1.2.1.1,DISMAN-SCHEDULE-MIB::schedOwner,OCTET,not-accessible,,current,,The owner of this scheduling entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
.1.3.6.1.2.1.63.1.2.1.2,DISMAN-SCHEDULE-MIB::schedName,OCTET,not-accessible,,current,,The locally-unique, administratively assigned name for this scheduling entry. This object allows a schedOwner to have multiple entries in the schedTable.
.1.3.6.1.2.1.63.1.2.1.3,DISMAN-SCHEDULE-MIB::schedDescr,OCTET,read-create,,current,,The human readable description of the purpose of this scheduling entry.
.1.3.6.1.2.1.63.1.2.1.4,DISMAN-SCHEDULE-MIB::schedInterval,Unsigned32,read-create,,current,,The number of seconds between two action invocations of a periodic scheduler. Implementations must guarantee that action invocations will not occur before at least schedInterval seconds have passed. The scheduler must ignore all periodic schedules that have a schedInterval value of 0. A periodic schedule with a scheduling interval of 0 seconds will therefore never invoke an action. Implementations may be forced to delay invocations in the face of local constraints. A scheduled management function should therefore not rely on the accuracy provided by the scheduler implementation. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.5,DISMAN-SCHEDULE-MIB::schedWeekDay,BITS,read-create,,current,sunday(0):monday(1):tuesday(2):wednesday(3):thursday(4):friday(5):saturday(6),The set of weekdays on which the scheduled action should take place. Setting multiple bits will include several weekdays in the set of possible weekdays for this schedule. Setting all bits will cause the scheduler to ignore the weekday. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.6,DISMAN-SCHEDULE-MIB::schedMonth,BITS,read-create,,current,january(0):february(1):march(2):april(3):may(4):june(5):july(6):august(7):september(8):october(9):november(10):december(11),The set of months during which the scheduled action should take place. Setting multiple bits will include several months in the set of possible months for this schedule. Setting all bits will cause the scheduler to ignore the month. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.7,DISMAN-SCHEDULE-MIB::schedDay,BITS,read-create,,current,d1(0):d2(1):d3(2):d4(3):d5(4):d6(5):d7(6):d8(7):d9(8):d10(9):d11(10):d12(11):d13(12):d14(13):d15(14):d16(15):d17(16):d18(17):d19(18):d20(19):d21(20):d22(21):d23(22):d24(23):d25(24):d26(25):d27(26):d28(27):d29(28):d30(29):d31(30):r1(31):r2(32):r3(33):r4(34):r5(35):r6(36):r7(37):r8(38):r9(39):r10(40):r11(41):r12(42):r13(43):r14(44):r15(45):r16(46):r17(47):r18(48):r19(49):r20(50):r21(51):r22(52):r23(53):r24(54):r25(55):r26(56):r27(57):r28(58):r29(59):r30(60):r31(61),The set of days in a month on which a scheduled action should take place. There are two sets of bits one can use to define the day within a month: Enumerations starting with the letter 'd' indicate a day in a month relative to the first day of a month. The first day of the month can therefore be specified by setting the bit d1(0) and d31(30) means the last day of a month with 31 days. Enumerations starting with the letter 'r' indicate a day in a month in reverse order, relative to the last day of a month. The last day in the month can therefore be specified by setting the bit r1(31) and r31(61) means the first day of a month with 31 days. Setting multiple bits will include several days in the set of possible days for this schedule. Setting all bits will cause the scheduler to ignore the day within a month. Setting all bits starting with the letter 'd' or the letter 'r' will also cause the scheduler to ignore the day within a month. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.8,DISMAN-SCHEDULE-MIB::schedHour,BITS,read-create,,current,h0(0):h1(1):h2(2):h3(3):h4(4):h5(5):h6(6):h7(7):h8(8):h9(9):h10(10):h11(11):h12(12):h13(13):h14(14):h15(15):h16(16):h17(17):h18(18):h19(19):h20(20):h21(21):h22(22):h23(23),The set of hours within a day during which the scheduled action should take place. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.9,DISMAN-SCHEDULE-MIB::schedMinute,BITS,read-create,,current,m0(0):m1(1):m2(2):m3(3):m4(4):m5(5):m6(6):m7(7):m8(8):m9(9):m10(10):m11(11):m12(12):m13(13):m14(14):m15(15):m16(16):m17(17):m18(18):m19(19):m20(20):m21(21):m22(22):m23(23):m24(24):m25(25):m26(26):m27(27):m28(28):m29(29):m30(30):m31(31):m32(32):m33(33):m34(34):m35(35):m36(36):m37(37):m38(38):m39(39):m40(40):m41(41):m42(42):m43(43):m44(44):m45(45):m46(46):m47(47):m48(48):m49(49):m50(50):m51(51):m52(52):m53(53):m54(54):m55(55):m56(56):m57(57):m58(58):m59(59),The set of minutes within an hour when the scheduled action should take place. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.10,DISMAN-SCHEDULE-MIB::schedContextName,OCTET,read-create,,current,,The context which contains the local MIB variable pointed to by schedVariable.
.1.3.6.1.2.1.63.1.2.1.11,DISMAN-SCHEDULE-MIB::schedVariable,OBJECT,read-create,,current,,An object identifier pointing to a local MIB variable which resolves to an ASN.1 primitive type of INTEGER.
.1.3.6.1.2.1.63.1.2.1.12,DISMAN-SCHEDULE-MIB::schedValue,Integer32,read-create,,current,,The value which is written to the MIB object pointed to by schedVariable when the scheduler invokes an action. The implementation shall enforce the use of access control rules when performing the set operation on schedVariable. This is accomplished by calling the isAccessAllowed abstract service interface as defined in RFC 2571. Note that an implementation may choose to issue an SNMP Set message to the SNMP engine and leave the access control decision to the normal message processing procedure.
.1.3.6.1.2.1.63.1.2.1.13,DISMAN-SCHEDULE-MIB::schedType,INTEGER,read-create,,current,periodic(1):calendar(2):oneshot(3),The type of this schedule. The value periodic(1) indicates that this entry specifies a periodic schedule. A periodic schedule is defined by the value of schedInterval. The values of schedWeekDay, schedMonth, schedDay, schedHour and schedMinute are ignored. The value calendar(2) indicates that this entry describes a calendar schedule. A calendar schedule is defined by the values of schedWeekDay, schedMonth, schedDay, schedHour and schedMinute. The value of schedInterval is ignored. A calendar schedule will trigger on all local times that satisfy the bits set in schedWeekDay, schedMonth, schedDay, schedHour and schedMinute. The value oneshot(3) indicates that this entry describes a one-shot schedule. A one-shot schedule is similar to a calendar schedule with the additional feature that it disables itself by changing in the `finished' schedOperStatus once the schedule triggers an action. Note that implementations which maintain a list of pending activations must re-calculate them when this object is changed.
.1.3.6.1.2.1.63.1.2.1.14,DISMAN-SCHEDULE-MIB::schedAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),The desired state of the schedule.
.1.3.6.1.2.1.63.1.2.1.15,DISMAN-SCHEDULE-MIB::schedOperStatus,INTEGER,read-only,,current,enabled(1):disabled(2):finished(3),The current operational state of this schedule. The state enabled(1) indicates this entry is active and that the scheduler will invoke actions at appropriate times. The disabled(2) state indicates that this entry is currently inactive and ignored by the scheduler. The finished(3) state indicates that the schedule has ended. Schedules in the finished(3) state are ignored by the scheduler. A one-shot schedule enters the finished(3) state when it deactivates itself. Note that the operational state must not be enabled(1) when the schedRowStatus is not active.
.1.3.6.1.2.1.63.1.2.1.16,DISMAN-SCHEDULE-MIB::schedFailures,Counter32,read-only,,current,,This variable counts the number of failures while invoking the scheduled action. This counter at most increments once for a triggered action.
.1.3.6.1.2.1.63.1.2.1.17,DISMAN-SCHEDULE-MIB::schedLastFailure,INTEGER,read-only,,current,noResponse(-1):noError(0):tooBig(1):noSuchName(2):badValue(3):readOnly(4):genErr(5):noAccess(6):wrongType(7):wrongLength(8):wrongEncoding(9):wrongValue(10):noCreation(11):inconsistentValue(12):resourceUnavailable(13):commitFailed(14):undoFailed(15):authorizationError(16):notWritable(17):inconsistentName(18),The most recent error that occurred during the invocation of a scheduled action. The value noError(0) is returned if no errors have occurred yet.
.1.3.6.1.2.1.63.1.2.1.18,DISMAN-SCHEDULE-MIB::schedLastFailed,OCTET,read-only,,current,,The date and time when the most recent failure occurred. The value '0000000000000000'H is returned if no failure occurred since the last re-initialization of the scheduler.
.1.3.6.1.2.1.63.1.2.1.19,DISMAN-SCHEDULE-MIB::schedStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this scheduled action is kept in volatile storage and lost upon reboot or if this row is backed up by non-volatile or permanent storage. Conceptual rows having the value `permanent' must allow write access to the columnar objects schedDescr, schedInterval, schedContextName, schedVariable, schedValue, and schedAdminStatus. If an implementation supports the schedCalendarGroup, write access must be also allowed to the columnar objects schedWeekDay, schedMonth, schedDay, schedHour, schedMinute.
.1.3.6.1.2.1.63.1.2.1.20,DISMAN-SCHEDULE-MIB::schedRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this scheduled action. A control that allows entries to be added and removed from this table. Note that the operational state must change to enabled when the administrative state is enabled and the row status changes to active(1). Attempts to destroy(6) a row or to set a row notInService(2) while the operational state is enabled result in inconsistentValue errors. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.63.1.2.1.21,DISMAN-SCHEDULE-MIB::schedTriggers,Counter32,read-only,,current,,This variable counts the number of attempts (either successful or failed) to invoke the scheduled action.
.1.3.6.1.2.1.63.2,DISMAN-SCHEDULE-MIB::schedNotifications,,,,,,
.1.3.6.1.2.1.63.2.0,DISMAN-SCHEDULE-MIB::schedTraps,,,,,,
.1.3.6.1.2.1.63.2.0.1,DISMAN-SCHEDULE-MIB::schedActionFailure,,,,,,This notification is generated whenever the invocation of a scheduled action fails.
.1.3.6.1.2.1.63.3,DISMAN-SCHEDULE-MIB::schedConformance,,,,,,
.1.3.6.1.2.1.63.3.1,DISMAN-SCHEDULE-MIB::schedCompliances,,,,,,
.1.3.6.1.2.1.63.3.1.1,DISMAN-SCHEDULE-MIB::schedCompliance,,,,,,The compliance statement for SNMP entities which implement the scheduling MIB.
.1.3.6.1.2.1.63.3.1.2,DISMAN-SCHEDULE-MIB::schedCompliance2,,,,,,The compliance statement for SNMP entities which implement the scheduling MIB.
.1.3.6.1.2.1.63.3.2,DISMAN-SCHEDULE-MIB::schedGroups,,,,,,
.1.3.6.1.2.1.63.3.2.1,DISMAN-SCHEDULE-MIB::schedGroup,,,,,,A collection of objects providing scheduling capabilities.
.1.3.6.1.2.1.63.3.2.2,DISMAN-SCHEDULE-MIB::schedCalendarGroup,,,,,,A collection of objects providing calendar based schedules.
.1.3.6.1.2.1.63.3.2.3,DISMAN-SCHEDULE-MIB::schedNotificationsGroup,,,,,,The notifications emitted by the scheduler.
.1.3.6.1.2.1.63.3.2.4,DISMAN-SCHEDULE-MIB::schedGroup2,,,,,,A collection of objects providing scheduling capabilities.
.1.3.6.1.2.1.64,DISMAN-SCRIPT-MIB::scriptMIB,,,,,,This MIB module defines a set of objects that allow to delegate management scripts to distributed managers.
.1.3.6.1.2.1.64.1,DISMAN-SCRIPT-MIB::smObjects,,,,,,
.1.3.6.1.2.1.64.1.1,DISMAN-SCRIPT-MIB::smLangTable,,not-accessible,,current,,This table lists supported script languages.
.1.3.6.1.2.1.64.1.1.1,DISMAN-SCRIPT-MIB::smLangEntry,,not-accessible,smLangIndex,current,,An entry describing a particular language.
.1.3.6.1.2.1.64.1.1.1.1,DISMAN-SCRIPT-MIB::smLangIndex,Integer32,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this language entry. The value is expected to remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. Note that the data type and the range of this object must be consistent with the definition of smScriptLanguage.
.1.3.6.1.2.1.64.1.1.1.2,DISMAN-SCRIPT-MIB::smLangLanguage,OBJECT,read-only,,current,,The globally unique identification of the language.
.1.3.6.1.2.1.64.1.1.1.3,DISMAN-SCRIPT-MIB::smLangVersion,OCTET,read-only,,current,,The version number of the language. The zero-length string shall be used if the language does not have a version number. It is suggested that the version number consist of one or more decimal numbers separated by dots, where the first number is called the major version number.
.1.3.6.1.2.1.64.1.1.1.4,DISMAN-SCRIPT-MIB::smLangVendor,OBJECT,read-only,,current,,An object identifier which identifies the vendor who provides the implementation of the language. This object identifier SHALL point to the object identifier directly below the enterprise object identifier {1 3 6 1 4 1} allocated for the vendor. The value must be the object identifier {0 0} if the vendor is not known.
.1.3.6.1.2.1.64.1.1.1.5,DISMAN-SCRIPT-MIB::smLangRevision,OCTET,read-only,,current,,The version number of the language implementation. The value of this object must be an empty string if version number of the implementation is unknown. It is suggested that the value consist of one or more decimal numbers separated by dots, where the first number is called the major version number.
.1.3.6.1.2.1.64.1.1.1.6,DISMAN-SCRIPT-MIB::smLangDescr,OCTET,read-only,,current,,A textual description of the language.
.1.3.6.1.2.1.64.1.2,DISMAN-SCRIPT-MIB::smExtsnTable,,not-accessible,,current,,This table lists supported language extensions.
.1.3.6.1.2.1.64.1.2.1,DISMAN-SCRIPT-MIB::smExtsnEntry,,not-accessible,smLangIndex:smExtsnIndex,current,,An entry describing a particular language extension.
.1.3.6.1.2.1.64.1.2.1.1,DISMAN-SCRIPT-MIB::smExtsnIndex,Integer32,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this language extension entry. The value is expected to remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.2.1.64.1.2.1.2,DISMAN-SCRIPT-MIB::smExtsnExtension,OBJECT,read-only,,current,,The globally unique identification of the language extension.
.1.3.6.1.2.1.64.1.2.1.3,DISMAN-SCRIPT-MIB::smExtsnVersion,OCTET,read-only,,current,,The version number of the language extension. It is suggested that the version number consist of one or more decimal numbers separated by dots, where the first number is called the major version number.
.1.3.6.1.2.1.64.1.2.1.4,DISMAN-SCRIPT-MIB::smExtsnVendor,OBJECT,read-only,,current,,An object identifier which identifies the vendor who provides the implementation of the extension. The object identifier value should point to the OID node directly below the enterprise OID {1 3 6 1 4 1} allocated for the vendor. The value must by the object identifier {0 0} if the vendor is not known.
.1.3.6.1.2.1.64.1.2.1.5,DISMAN-SCRIPT-MIB::smExtsnRevision,OCTET,read-only,,current,,The version number of the extension implementation. The value of this object must be an empty string if version number of the implementation is unknown. It is suggested that the value consist of one or more decimal numbers separated by dots, where the first number is called the major version number.
.1.3.6.1.2.1.64.1.2.1.6,DISMAN-SCRIPT-MIB::smExtsnDescr,OCTET,read-only,,current,,A textual description of the language extension.
.1.3.6.1.2.1.64.1.3,DISMAN-SCRIPT-MIB::smScriptObjects,,,,,,
.1.3.6.1.2.1.64.1.3.1,DISMAN-SCRIPT-MIB::smScriptTable,,not-accessible,,current,,This table lists and describes locally known scripts.
.1.3.6.1.2.1.64.1.3.1.1,DISMAN-SCRIPT-MIB::smScriptEntry,,not-accessible,smScriptOwner:smScriptName,current,,An entry describing a particular script. Every script that is stored in non-volatile memory is required to appear in this script table.
.1.3.6.1.2.1.64.1.3.1.1.1,DISMAN-SCRIPT-MIB::smScriptOwner,OCTET,not-accessible,,current,,The manager who owns this row in the smScriptTable.
.1.3.6.1.2.1.64.1.3.1.1.2,DISMAN-SCRIPT-MIB::smScriptName,OCTET,not-accessible,,current,,The locally-unique, administratively assigned name for this script. This object allows an smScriptOwner to have multiple entries in the smScriptTable. This value of this object may be used to derive the name (e.g. a file name) which is used by the Script MIB implementation to access the script in non-volatile storage. The details of this mapping are implementation specific. However, the mapping needs to ensure that scripts created by different owners with the same script name do not map to the same name in non-volatile storage.
.1.3.6.1.2.1.64.1.3.1.1.3,DISMAN-SCRIPT-MIB::smScriptDescr,OCTET,read-create,,current,,A description of the purpose of the script.
.1.3.6.1.2.1.64.1.3.1.1.4,DISMAN-SCRIPT-MIB::smScriptLanguage,Integer32,read-create,,current,,The value of this object type identifies an entry in the smLangTable which is used to execute this script. The special value 0 may be used by hard-wired scripts that can not be modified and that are executed by internal functions. Set requests to change this object are invalid if the value of smScriptOperStatus is `enabled' or `compiling' and will result in an inconsistentValue error. Note that the data type and the range of this object must be consistent with the definition of smLangIndex.
.1.3.6.1.2.1.64.1.3.1.1.5,DISMAN-SCRIPT-MIB::smScriptSource,OCTET,read-create,,current,,This object either contains a reference to the script source or an empty string. A reference must be given in the form of a Uniform Resource Locator (URL) as defined in RFC 2396. The allowed character sets and the encoding rules defined in RFC 2396 section 2 apply. When the smScriptAdminStatus object is set to `enabled', the Script MIB implementation will `pull' the script source from the URL contained in this object if the URL is not empty. An empty URL indicates that the script source is loaded from local storage. The script is read from the smCodeTable if the value of smScriptStorageType is volatile. Otherwise, the script is read from non-volatile storage. Note: This document does not mandate implementation of any specific URL scheme. An attempt to load a script from a nonsupported URL scheme will cause the smScriptOperStatus to report an `unknownProtocol' error. Set requests to change this object are invalid if the value of smScriptOperStatus is `enabled', `editing', `retrieving' or `compiling' and will result in an inconsistentValue error.
.1.3.6.1.2.1.64.1.3.1.1.6,DISMAN-SCRIPT-MIB::smScriptAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2):editing(3),The value of this object indicates the desired status of the script. See the definition of smScriptOperStatus for a description of the values. When the smScriptAdminStatus object is set to `enabled' and the smScriptOperStatus is `disabled' or one of the error states, the Script MIB implementation will `pull' the script source from the URL contained in the smScriptSource object if the URL is not empty.
.1.3.6.1.2.1.64.1.3.1.1.7,DISMAN-SCRIPT-MIB::smScriptOperStatus,INTEGER,read-only,,current,enabled(1):disabled(2):editing(3):retrieving(4):compiling(5):noSuchScript(6):accessDenied(7):wrongLanguage(8):wrongVersion(9):compilationFailed(10):noResourcesLeft(11):unknownProtocol(12):protocolFailure(13):genericError(14),The actual status of the script in the runtime system. The value of this object is only meaningful when the value of the smScriptRowStatus object is `active'. The smScriptOperStatus object may have the following values: - `enabled' indicates that the script is available and can be started by a launch table entry. - `disabled' indicates that the script can not be used. - `editing' indicates that the script can be modified in the smCodeTable. - `retrieving' indicates that the script is currently being loaded from non-volatile storage or a remote system. - `compiling' indicates that the script is currently being compiled by the runtime system. - `noSuchScript' indicates that the script does not exist at the smScriptSource. - `accessDenied' indicates that the script can not be loaded from the smScriptSource due to a lack of permissions. - `wrongLanguage' indicates that the script can not be loaded from the smScriptSource because of a language mismatch. - `wrongVersion' indicates that the script can not be loaded from the smScriptSource because of a language version mismatch. - `compilationFailed' indicates that the compilation failed. - `noResourcesLeft' indicates that the runtime system does not have enough resources to load the script. - `unknownProtocol' indicates that the script could not be loaded from the smScriptSource because the requested protocol is not supported. - `protocolFailure' indicates that the script could not be loaded from the smScriptSource because of a protocol failure. - `genericError' indicates that the script could not be loaded due to an error condition not listed above. The `retrieving' and `compiling' states are transient states which will either lead to one of the error states or the `enabled' state. The `disabled' and `editing' states are administrative states which are only reached by explicit management operations. All launch table entries that refer to this script table entry shall have an smLaunchOperStatus value of `disabled' when the value of this object is not `enabled'.
.1.3.6.1.2.1.64.1.3.1.1.8,DISMAN-SCRIPT-MIB::smScriptStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this row and the script controlled by this row are kept in volatile storage and lost upon reboot or if this row is backed up by non-volatile or permanent storage. The storage type of this row always complies with the value of this entry if the value of the corresponding RowStatus object is `active'. However, the storage type of the script controlled by this row may be different, if the value of this entry is `non-volatile'. The script controlled by this row is written into local non-volatile storage if the following condition becomes true: (a) the URL contained in the smScriptSource object is empty and (b) the smScriptStorageType is `nonVolatile' and (c) the smScriptOperStatus is `enabled' Setting this object to `volatile' removes a script from non-volatile storage if the script controlled by this row has been in non-volatile storage before. Attempts to set this object to permanent will always fail with an inconsistentValue error. The value of smScriptStorageType is only meaningful if the value of the corresponding RowStatus object is `active'. If smScriptStorageType has the value permanent(4), then all objects whose MAX-ACCESS value is read-create must be writable, with the exception of the smScriptStorageType and smScriptRowStatus objects, which shall be read-only.
.1.3.6.1.2.1.64.1.3.1.1.9,DISMAN-SCRIPT-MIB::smScriptRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),A control that allows entries to be added and removed from this table. Changing the smScriptRowStatus from `active' to `notInService' will remove the associated script from the runtime system. Deleting conceptual rows from this table may affect the deletion of other resources associated with this row. For example, a script stored in non-volatile storage may be removed from non-volatile storage. An entry may not exist in the `active' state unless all required objects in the entry have appropriate values. Rows that are not complete or not in service are not known by the script runtime system. Attempts to `destroy' a row or to set a row `notInService' while the smScriptOperStatus is `enabled' will result in an inconsistentValue error. Attempts to `destroy' a row or to set a row `notInService' where the value of the smScriptStorageType object is `permanent' or `readOnly' will result in an inconsistentValue error. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.64.1.3.1.1.10,DISMAN-SCRIPT-MIB::smScriptError,OCTET,read-only,,current,,This object contains a descriptive error message if the transition into the operational status `enabled' failed. Implementations must reset the error message to a zero-length string when a new attempt to change the script status to `enabled' is started.
.1.3.6.1.2.1.64.1.3.1.1.11,DISMAN-SCRIPT-MIB::smScriptLastChange,OCTET,read-only,,current,,The date and time when this script table entry was last modified. The value '0000000000000000'H is returned if the script table entry has not yet been modified. Note that the resetting of smScriptError is not considered a change of the script table entry.
.1.3.6.1.2.1.64.1.3.2,DISMAN-SCRIPT-MIB::smCodeTable,,not-accessible,,current,,This table contains the script code for scripts that are written via SNMP write operations.
.1.3.6.1.2.1.64.1.3.2.1,DISMAN-SCRIPT-MIB::smCodeEntry,,not-accessible,smScriptOwner:smScriptName:smCodeIndex,current,,An entry describing a particular fragment of a script.
.1.3.6.1.2.1.64.1.3.2.1.1,DISMAN-SCRIPT-MIB::smCodeIndex,Unsigned32,not-accessible,,current,,The index value identifying this code fragment.
.1.3.6.1.2.1.64.1.3.2.1.2,DISMAN-SCRIPT-MIB::smCodeText,OCTET,read-create,,current,,The code that makes up a fragment of a script. The format of this code fragment depends on the script language which is identified by the associated smScriptLanguage object.
.1.3.6.1.2.1.64.1.3.2.1.3,DISMAN-SCRIPT-MIB::smCodeRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),A control that allows entries to be added and removed from this table. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.64.1.4,DISMAN-SCRIPT-MIB::smRunObjects,,,,,,
.1.3.6.1.2.1.64.1.4.1,DISMAN-SCRIPT-MIB::smLaunchTable,,not-accessible,,current,,This table lists and describes scripts that are ready to be executed together with their parameters.
.1.3.6.1.2.1.64.1.4.1.1,DISMAN-SCRIPT-MIB::smLaunchEntry,,not-accessible,smLaunchOwner:smLaunchName,current,,An entry describing a particular executable script.
.1.3.6.1.2.1.64.1.4.1.1.1,DISMAN-SCRIPT-MIB::smLaunchOwner,OCTET,not-accessible,,current,,The manager who owns this row in the smLaunchTable. Every instance of a running script started from a particular entry in the smLaunchTable (i.e. entries in the smRunTable) will be owned by the same smLaunchOwner used to index the entry in the smLaunchTable. This owner is not necessarily the same as the owner of the script itself (smLaunchScriptOwner).
.1.3.6.1.2.1.64.1.4.1.1.2,DISMAN-SCRIPT-MIB::smLaunchName,OCTET,not-accessible,,current,,The locally-unique, administratively assigned name for this launch table entry. This object allows an smLaunchOwner to have multiple entries in the smLaunchTable. The smLaunchName is an arbitrary name that must be different from any other smLaunchTable entries with the same smLaunchOwner but can be the same as other entries in the smLaunchTable with different smLaunchOwner values. Note that the value of smLaunchName is not related in any way to the name of the script being launched.
.1.3.6.1.2.1.64.1.4.1.1.3,DISMAN-SCRIPT-MIB::smLaunchScriptOwner,OCTET,read-create,,current,,The value of this object in combination with the value of smLaunchScriptName identifies the script that can be launched from this smLaunchTable entry. Attempts to write this object will fail with an inconsistentValue error if the value of smLaunchOperStatus is `enabled'.
.1.3.6.1.2.1.64.1.4.1.1.4,DISMAN-SCRIPT-MIB::smLaunchScriptName,OCTET,read-create,,current,,The value of this object in combination with the value of the smLaunchScriptOwner identifies the script that can be launched from this smLaunchTable entry. The zero-length string may be used to point to a non-existing script. Attempts to write this object will fail with an inconsistentValue error if the value of smLaunchOperStatus is `enabled'.
.1.3.6.1.2.1.64.1.4.1.1.5,DISMAN-SCRIPT-MIB::smLaunchArgument,OCTET,read-create,,current,,The argument supplied to the script. When a script is invoked, the value of this object is used to initialize the smRunArgument object.
.1.3.6.1.2.1.64.1.4.1.1.6,DISMAN-SCRIPT-MIB::smLaunchMaxRunning,Unsigned32,read-create,,current,,The maximum number of concurrently running scripts that may be invoked from this entry in the smLaunchTable. Lowering the current value of this object does not affect any scripts that are already executing.
.1.3.6.1.2.1.64.1.4.1.1.7,DISMAN-SCRIPT-MIB::smLaunchMaxCompleted,Unsigned32,read-create,,current,,The maximum number of finished scripts invoked from this entry in the smLaunchTable allowed to be retained in the smRunTable. Whenever the value of this object is changed and whenever a script terminates, entries in the smRunTable are deleted if necessary until the number of completed scripts is smaller than the value of this object. Scripts whose smRunEndTime value indicates the oldest completion time are deleted first.
.1.3.6.1.2.1.64.1.4.1.1.8,DISMAN-SCRIPT-MIB::smLaunchLifeTime,INTEGER,read-create,,current,,The default maximum amount of time a script launched from this entry may run. The value of this object is used to initialize the smRunLifeTime object when a script is launched. Changing the value of an smLaunchLifeTime instance does not affect scripts previously launched from this entry.
.1.3.6.1.2.1.64.1.4.1.1.9,DISMAN-SCRIPT-MIB::smLaunchExpireTime,INTEGER,read-create,,current,,The default maximum amount of time information about a script launched from this entry is kept in the smRunTable after the script has completed execution. The value of this object is used to initialize the smRunExpireTime object when a script is launched. Changing the value of an smLaunchExpireTime instance does not affect scripts previously launched from this entry.
.1.3.6.1.2.1.64.1.4.1.1.10,DISMAN-SCRIPT-MIB::smLaunchStart,Integer32,read-create,,current,,This object is used to start the execution of scripts. When retrieved, the value will be the value of smRunIndex for the last script that started execution by manipulating this object. The value will be zero if no script started execution yet. A script is started by setting this object to an unused smRunIndex value. A new row in the smRunTable will be created which is indexed by the value supplied by the set-request in addition to the value of smLaunchOwner and smLaunchName. An unused value can be obtained by reading the smLaunchRunIndexNext object. Setting this object to the special value 0 will start the script with a self-generated smRunIndex value. The consequence is that the script invoker has no reliable way to determine the smRunIndex value for this script invocation and that the invoker has therefore no way to obtain the results from this script invocation. The special value 0 is however useful for scheduled script invocations. If this object is set, the following checks must be performed: 1) The value of the smLaunchOperStatus object in this entry of the smLaunchTable must be `enabled'. 2) The values of smLaunchScriptOwner and smLaunchScriptName of this row must identify an existing entry in the smScriptTable. 3) The value of smScriptOperStatus of this entry must be `enabled'. 4) The principal performing the set operation must have read access to the script. This must be checked by calling the isAccessAllowed abstract service interface defined in RFC 2271 on the row in the smScriptTable identified by smLaunchScriptOwner and smLaunchScriptName. The isAccessAllowed abstract service interface must be called on all columnar objects in the smScriptTable with a MAX-ACCESS value different than `not-accessible'. The test fails as soon as a call indicates that access is not allowed. 5) If the value provided by the set operation is not 0, a check must be made that the value is currently not in use. Otherwise, if the value provided by the set operation is 0, a suitable unused value must be generated. 6) The number of currently executing scripts invoked from this smLaunchTable entry must be less than smLaunchMaxRunning. Attempts to start a script will fail with an inconsistentValue error if one of the checks described above fails. Otherwise, if all checks have been passed, a new entry in the smRunTable will be created indexed by smLaunchOwner, smLaunchName and the new value for smRunIndex. The value of smLaunchArgument will be copied into smRunArgument, the value of smLaunchLifeTime will be copied to smRunLifeTime, and the value of smLaunchExpireTime will be copied to smRunExpireTime. The smRunStartTime will be set to the current time and the smRunState will be set to `initializing' before the script execution is initiated in the appropriate runtime system. Note that the data type and the range of this object must be consistent with the smRunIndex object. Since this object might be written from the scheduling MIB, the data type Integer32 rather than Unsigned32 is used.
.1.3.6.1.2.1.64.1.4.1.1.11,DISMAN-SCRIPT-MIB::smLaunchControl,INTEGER,read-create,,current,abort(1):suspend(2):resume(3):nop(4),This object is used to request a state change for all running scripts in the smRunTable that were started from this row in the smLaunchTable. Setting this object to abort(1), suspend(2) or resume(3) will set the smRunControl object of all applicable rows in the smRunTable to abort(1), suspend(2) or resume(3) respectively. The phrase `applicable rows' means the set of rows which were created from this entry in the smLaunchTable and whose value of smRunState allows the corresponding state change as described in the definition of the smRunControl object. Setting this object to nop(4) has no effect. Attempts to set this object lead to an inconsistentValue error only if all implicated sets on all the applicable rows lead to inconsistentValue errors. It is not allowed to return an inconsistentValue error if at least one state change on one of the applicable rows was successful.
.1.3.6.1.2.1.64.1.4.1.1.12,DISMAN-SCRIPT-MIB::smLaunchAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2):autostart(3),The value of this object indicates the desired status of this launch table entry. The values enabled(1) and autostart(3) both indicate that the launch table entry should transition into the operational enabled(1) state as soon as the associated script table entry is enabled(1). The value autostart(3) further indicates that the script is started automatically by conceptually writing the value 0 into the associated smLaunchStart object during the transition from the `disabled' into the `enabled' operational state. This is useful for scripts that are to be launched on system start-up.
.1.3.6.1.2.1.64.1.4.1.1.13,DISMAN-SCRIPT-MIB::smLaunchOperStatus,INTEGER,read-only,,current,enabled(1):disabled(2):expired(3),The value of this object indicates the actual status of this launch table entry. The smLaunchOperStatus object may have the following values: - `enabled' indicates that the launch table entry is available and can be used to start scripts. - `disabled' indicates that the launch table entry can not be used to start scripts. - `expired' indicates that the launch table entry can not be used to start scripts and will disappear as soon as all smRunTable entries associated with this launch table entry have disappeared. The value `enabled' requires that the smLaunchRowStatus object is active. The value `disabled' requires that there are no entries in the smRunTable associated with this smLaunchTable entry.
.1.3.6.1.2.1.64.1.4.1.1.14,DISMAN-SCRIPT-MIB::smLaunchRunIndexNext,Integer32,read-only,,current,,This variable is used for creating rows in the smRunTable. The value of this variable is a currently unused value for smRunIndex, which can be written into the smLaunchStart object associated with this row to launch a script. The value returned when reading this variable must be unique for the smLaunchOwner and smLaunchName associated with this row. Subsequent attempts to read this variable must return different values. This variable will return the special value 0 if no new rows can be created. Note that the data type and the range of this object must be consistent with the definition of smRunIndex.
.1.3.6.1.2.1.64.1.4.1.1.15,DISMAN-SCRIPT-MIB::smLaunchStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines if this row is kept in volatile storage and lost upon reboot or if this row is backed up by stable storage. The value of smLaunchStorageType is only meaningful if the value of the corresponding RowStatus object is active. If smLaunchStorageType has the value permanent(4), then all objects whose MAX-ACCESS value is read-create must be writable, with the exception of the smLaunchStorageType and smLaunchRowStatus objects, which shall be read-only.
.1.3.6.1.2.1.64.1.4.1.1.16,DISMAN-SCRIPT-MIB::smLaunchRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),A control that allows entries to be added and removed from this table. Attempts to `destroy' a row or to set a row `notInService' while the smLaunchOperStatus is `enabled' will result in an inconsistentValue error. Attempts to `destroy' a row or to set a row `notInService' where the value of the smLaunchStorageType object is `permanent' or `readOnly' will result in an inconsistentValue error. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.64.1.4.1.1.17,DISMAN-SCRIPT-MIB::smLaunchError,OCTET,read-only,,current,,This object contains a descriptive error message if an attempt to launch a script fails. Implementations must reset the error message to a zero-length string when a new attempt to launch a script is started.
.1.3.6.1.2.1.64.1.4.1.1.18,DISMAN-SCRIPT-MIB::smLaunchLastChange,OCTET,read-only,,current,,The date and time when this launch table entry was last modified. The value '0000000000000000'H is returned if the launch table entry has not yet been modified. Note that a change of smLaunchStart, smLaunchControl, smLaunchRunIndexNext, smLaunchRowExpireTime, or the resetting of smLaunchError is not considered a change of this launch table entry.
.1.3.6.1.2.1.64.1.4.1.1.19,DISMAN-SCRIPT-MIB::smLaunchRowExpireTime,INTEGER,read-create,,current,,The value of this object specifies how long this row remains in the `enabled' or `disabled' operational state. The value reported by this object ticks backwards. When the value reaches 0, it stops ticking backward and the row is deleted if there are no smRunTable entries associated with this smLaunchTable entry. Otherwise, the smLaunchOperStatus changes to `expired' and the row deletion is deferred until there are no smRunTable entries associated with this smLaunchTable entry. The smLaunchRowExpireTime will not tick backwards if it is set to its maximum value (2147483647). In other words, setting this object to its maximum value turns the timer off. The value of this object may be set in order to increase or reduce the remaining time that the launch table entry may be used. Setting the value to 0 will cause an immediate row deletion or transition into the `expired' operational state. It is not possible to set this object while the operational status is `expired'. Attempts to modify this object while the operational status is `expired' leads to an inconsistentValue error. Note that the timer ticks backwards independent of the operational state of the launch table entry.
.1.3.6.1.2.1.64.1.4.2,DISMAN-SCRIPT-MIB::smRunTable,,not-accessible,,current,,This table lists and describes scripts that are currently running or have been running in the past.
.1.3.6.1.2.1.64.1.4.2.1,DISMAN-SCRIPT-MIB::smRunEntry,,not-accessible,smLaunchOwner:smLaunchName:smRunIndex,current,,An entry describing a particular running or finished script.
.1.3.6.1.2.1.64.1.4.2.1.1,DISMAN-SCRIPT-MIB::smRunIndex,Integer32,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this running or finished script. This value must be unique for all rows in the smRunTable with the same smLaunchOwner and smLaunchName. Note that the data type and the range of this object must be consistent with the definition of smLaunchRunIndexNext and smLaunchStart.
.1.3.6.1.2.1.64.1.4.2.1.2,DISMAN-SCRIPT-MIB::smRunArgument,OCTET,read-only,,current,,The argument supplied to the script when it started.
.1.3.6.1.2.1.64.1.4.2.1.3,DISMAN-SCRIPT-MIB::smRunStartTime,OCTET,read-only,,current,,The date and time when the execution started. The value '0000000000000000'H is returned if the script has not started yet.
.1.3.6.1.2.1.64.1.4.2.1.4,DISMAN-SCRIPT-MIB::smRunEndTime,OCTET,read-only,,current,,The date and time when the execution terminated. The value '0000000000000000'H is returned if the script has not terminated yet.
.1.3.6.1.2.1.64.1.4.2.1.5,DISMAN-SCRIPT-MIB::smRunLifeTime,INTEGER,read-write,,current,,This object specifies how long the script can execute. This object returns the remaining time that the script may run. The object is initialized with the value of the associated smLaunchLifeTime object and ticks backwards. The script is aborted immediately when the value reaches 0. The value of this object may be set in order to increase or reduce the remaining time that the script may run. Setting this value to 0 will abort script execution immediately, and, if the value of smRunExpireTime is also 0, will remove this entry from the smRunTable once it has terminated. If smRunLifeTime is set to its maximum value (2147483647), either by a set operation or by its initialization from the smLaunchLifeTime object, then it will not tick backwards. A running script with a maximum smRunLifeTime value will thus never be terminated with a `lifeTimeExceeded' exit code. The value of smRunLifeTime reflects the real-time execution time as seen by the outside world. The value of this object will always be 0 for a script that finished execution, that is smRunState has the value `terminated'. The value of smRunLifeTime does not change while a script is suspended, that is smRunState has the value `suspended'. Note that this does not affect set operations. It is legal to modify smRunLifeTime via set operations while a script is suspended.
.1.3.6.1.2.1.64.1.4.2.1.6,DISMAN-SCRIPT-MIB::smRunExpireTime,INTEGER,read-write,,current,,The value of this object specifies how long this row can exist in the smRunTable after the script has terminated. This object returns the remaining time that the row may exist before it is aged out. The object is initialized with the value of the associated smLaunchExpireTime object and ticks backwards. The entry in the smRunTable is destroyed when the value reaches 0 and the smRunState has the value `terminated'. The value of this object may be set in order to increase or reduce the remaining time that the row may exist. Setting the value to 0 will destroy this entry as soon as the smRunState has the value `terminated'.
.1.3.6.1.2.1.64.1.4.2.1.7,DISMAN-SCRIPT-MIB::smRunExitCode,INTEGER,read-only,,current,noError(1):halted(2):lifeTimeExceeded(3):noResourcesLeft(4):languageError(5):runtimeError(6):invalidArgument(7):securityViolation(8):genericError(9),The value of this object indicates the reason why a script finished execution. The smRunExitCode code may have one of the following values: - `noError', which indicates that the script completed successfully without errors; - `halted', which indicates that the script was halted by a request from an authorized manager; - `lifeTimeExceeded', which indicates that the script exited because a time limit was exceeded; - `noResourcesLeft', which indicates that the script exited because it ran out of resources (e.g. memory); - `languageError', which indicates that the script exited because of a language error (e.g. a syntax error in an interpreted language); - `runtimeError', which indicates that the script exited due to a runtime error (e.g. a division by zero); - `invalidArgument', which indicates that the script could not be run because of invalid script arguments; - `securityViolation', which indicates that the script exited due to a security violation; - `genericError', which indicates that the script exited for an unspecified reason. If the script has not yet begun running, or is currently running, the value will be `noError'.
.1.3.6.1.2.1.64.1.4.2.1.8,DISMAN-SCRIPT-MIB::smRunResult,OCTET,read-only,,current,,The result value produced by the running script. Note that the result may change while the script is executing.
.1.3.6.1.2.1.64.1.4.2.1.9,DISMAN-SCRIPT-MIB::smRunControl,INTEGER,read-write,,current,abort(1):suspend(2):resume(3):nop(4),The value of this object indicates the desired status of the script execution defined by this row. Setting this object to `abort' will abort execution if the value of smRunState is `initializing', `executing', `suspending', `suspended' or `resuming'. Setting this object to `abort' when the value of smRunState is `aborting' or `terminated', or if the implementation can determine that the attempt to abort the execution would fail, will result in an inconsistentValue error. Setting this object to `suspend' will suspend execution if the value of smRunState is `executing'. Setting this object to `suspend' will cause an inconsistentValue error if the value of smRunState is not `executing' or if the implementation can determine that the attempt to suspend the execution would fail. Setting this object to `resume' will resume execution if the value of smRunState is `suspending' or `suspended'. Setting this object to `resume' will cause an inconsistentValue error if the value of smRunState is not `suspended' or if the implementation can determine that the attempt to resume the execution would fail. Setting this object to nop(4) has no effect.
.1.3.6.1.2.1.64.1.4.2.1.10,DISMAN-SCRIPT-MIB::smRunState,INTEGER,read-only,,current,initializing(1):executing(2):suspending(3):suspended(4):resuming(5):aborting(6):terminated(7),The value of this object indicates the script's execution state. If the script has been invoked but has not yet begun execution, the value will be `initializing'. If the script is running, the value will be `executing'. A running script which received a request to suspend execution first transitions into a temporary `suspending' state. The temporary `suspending' state changes to `suspended' when the script has actually been suspended. The temporary `suspending' state changes back to `executing' if the attempt to suspend the running script fails. A suspended script which received a request to resume execution first transitions into a temporary `resuming' state. The temporary `resuming' state changes to `running' when the script has actually been resumed. The temporary `resuming' state changes back to `suspended' if the attempt to resume the suspended script fails. A script which received a request to abort execution but which is still running first transitions into a temporary `aborting' state. A script which has finished its execution is `terminated'.
.1.3.6.1.2.1.64.1.4.2.1.11,DISMAN-SCRIPT-MIB::smRunError,OCTET,read-only,,current,,This object contains a descriptive error message if the script startup or execution raised an abnormal condition. An implementation must store a descriptive error message in this object if the script exits with the smRunExitCode `genericError'.
.1.3.6.1.2.1.64.1.4.2.1.12,DISMAN-SCRIPT-MIB::smRunResultTime,OCTET,read-only,,current,,The date and time when the smRunResult was last updated. The value '0000000000000000'H is returned if smRunResult has not yet been updated after the creation of this smRunTable entry.
.1.3.6.1.2.1.64.1.4.2.1.13,DISMAN-SCRIPT-MIB::smRunErrorTime,OCTET,read-only,,current,,The date and time when the smRunError was last updated. The value '0000000000000000'H is returned if smRunError has not yet been updated after the creation of this smRunTable entry.
.1.3.6.1.2.1.64.2,DISMAN-SCRIPT-MIB::smNotifications,,,,,,
.1.3.6.1.2.1.64.2.0,DISMAN-SCRIPT-MIB::smTraps,,,,,,
.1.3.6.1.2.1.64.2.0.1,DISMAN-SCRIPT-MIB::smScriptAbort,,,,,,This notification is generated whenever a running script terminates with an smRunExitCode unequal to `noError'.
.1.3.6.1.2.1.64.2.0.2,DISMAN-SCRIPT-MIB::smScriptResult,,,,,,This notification can be used by scripts to notify other management applications about results produced by the script. This notification is not automatically generated by the Script MIB implementation. It is the responsibility of the executing script to emit this notification where it is appropriate to do so.
.1.3.6.1.2.1.64.2.0.3,DISMAN-SCRIPT-MIB::smScriptException,,,,,,This notification can be used by scripts to notify other management applications about script errors. This notification is not automatically generated by the Script MIB implementation. It is the responsibility of the executing script or the runtime system to emit this notification where it is appropriate to do so.
.1.3.6.1.2.1.64.3,DISMAN-SCRIPT-MIB::smConformance,,,,,,
.1.3.6.1.2.1.64.3.1,DISMAN-SCRIPT-MIB::smCompliances,,,,,,
.1.3.6.1.2.1.64.3.1.1,DISMAN-SCRIPT-MIB::smCompliance,,,,,,The compliance statement for SNMP entities which implement the Script MIB.
.1.3.6.1.2.1.64.3.1.2,DISMAN-SCRIPT-MIB::smCompliance2,,,,,,The compliance statement for SNMP entities which implement the Script MIB.
.1.3.6.1.2.1.64.3.2,DISMAN-SCRIPT-MIB::smGroups,,,,,,
.1.3.6.1.2.1.64.3.2.1,DISMAN-SCRIPT-MIB::smLanguageGroup,,,,,,A collection of objects providing information about the capabilities of the scripting engine.
.1.3.6.1.2.1.64.3.2.2,DISMAN-SCRIPT-MIB::smScriptGroup,,,,,,A collection of objects providing information about installed scripts.
.1.3.6.1.2.1.64.3.2.3,DISMAN-SCRIPT-MIB::smCodeGroup,,,,,,A collection of objects used to download or modify scripts by using SNMP set requests.
.1.3.6.1.2.1.64.3.2.4,DISMAN-SCRIPT-MIB::smLaunchGroup,,,,,,A collection of objects providing information about scripts that can be launched.
.1.3.6.1.2.1.64.3.2.5,DISMAN-SCRIPT-MIB::smRunGroup,,,,,,A collection of objects providing information about running scripts.
.1.3.6.1.2.1.64.3.2.6,DISMAN-SCRIPT-MIB::smNotificationsGroup,,,,,,The notifications emitted by the Script MIB.
.1.3.6.1.2.1.64.3.2.7,DISMAN-SCRIPT-MIB::smScriptGroup2,,,,,,A collection of objects providing information about installed scripts.
.1.3.6.1.2.1.64.3.2.8,DISMAN-SCRIPT-MIB::smLaunchGroup2,,,,,,A collection of objects providing information about scripts that can be launched.
.1.3.6.1.2.1.64.3.2.9,DISMAN-SCRIPT-MIB::smRunGroup2,,,,,,A collection of objects providing information about running scripts.
.1.3.6.1.2.1.64.3.2.10,DISMAN-SCRIPT-MIB::smNotificationsGroup2,,,,,,The notifications emitted by the Script MIB.
.1.3.6.1.2.1.65,WWW-MIB::wwwMIB,,,,,,This WWW service MIB module is applicable to services realized by a family of 'Document Transfer Protocols' (DTP). Examples of DTPs are HTTP and FTP.
.1.3.6.1.2.1.65.1,WWW-MIB::wwwMIBObjects,,,,,,
.1.3.6.1.2.1.65.1.1,WWW-MIB::wwwService,,,,,,
.1.3.6.1.2.1.65.1.1.1,WWW-MIB::wwwServiceTable,,not-accessible,,current,,The table of the WWW services known by the SNMP agent.
.1.3.6.1.2.1.65.1.1.1.1,WWW-MIB::wwwServiceEntry,,not-accessible,wwwServiceIndex,current,,Details about a particular WWW service.
.1.3.6.1.2.1.65.1.1.1.1.1,WWW-MIB::wwwServiceIndex,Unsigned32,not-accessible,,current,,An integer used to uniquely identify a WWW service. The value must be the same as the corresponding value of the applSrvIndex defined in the Application Management MIB (APPLICATION-MIB) if the applSrvIndex object is available. It might be necessary to manually configure sub-agents in order to meet this requirement.
.1.3.6.1.2.1.65.1.1.1.1.2,WWW-MIB::wwwServiceDescription,OCTET,read-only,,current,,Textual description of the WWW service. This shall include at least the vendor and version number of the application realizing the WWW service. In a minimal case, this might be the Product Token (see RFC 2068) for the application.
.1.3.6.1.2.1.65.1.1.1.1.3,WWW-MIB::wwwServiceContact,OCTET,read-only,,current,,The textual identification of the contact person for this service, together with information on how to contact this person. For instance, this might be a string containing an email address, e.g. '<webmaster@domain.name>'.
.1.3.6.1.2.1.65.1.1.1.1.4,WWW-MIB::wwwServiceProtocol,OBJECT,read-only,,current,,An identification of the primary protocol in use by this service. For Internet applications, the IANA maintains a registry of the OIDs which correspond to well-known application protocols. If the application protocol is not listed in the registry, an OID value of the form {applTCPProtoID port} or {applUDPProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol.
.1.3.6.1.2.1.65.1.1.1.1.5,WWW-MIB::wwwServiceName,OCTET,read-only,,current,,The fully qualified domain name by which this service is known. This object must contain the virtual host name if the service is realized for a virtual host.
.1.3.6.1.2.1.65.1.1.1.1.6,WWW-MIB::wwwServiceType,INTEGER,read-only,,current,wwwOther(1):wwwServer(2):wwwClient(3):wwwProxy(4):wwwCachingProxy(5),The application type using or realizing this WWW service.
.1.3.6.1.2.1.65.1.1.1.1.7,WWW-MIB::wwwServiceStartTime,OCTET,read-only,,current,,The date and time when this WWW service was last started. The value SHALL be '0000000000000000'H if the last start time of this WWW service is not known.
.1.3.6.1.2.1.65.1.1.1.1.8,WWW-MIB::wwwServiceOperStatus,INTEGER,read-only,,current,down(1):running(2):halted(3):congested(4):restarting(5),Indicates the operational status of the WWW service.
.1.3.6.1.2.1.65.1.1.1.1.9,WWW-MIB::wwwServiceLastChange,OCTET,read-only,,current,,The date and time when this WWW service entered its current operational state. The value SHALL be '0000000000000000'H if the time of the last state change is not known.
.1.3.6.1.2.1.65.1.2,WWW-MIB::wwwProtocolStatistics,,,,,,
.1.3.6.1.2.1.65.1.2.1,WWW-MIB::wwwSummaryTable,,not-accessible,,current,,The table providing overview statistics for the WWW services on this system.
.1.3.6.1.2.1.65.1.2.1.1,WWW-MIB::wwwSummaryEntry,,not-accessible,wwwServiceIndex,current,,Overview statistics for an individual service.
.1.3.6.1.2.1.65.1.2.1.1.1,WWW-MIB::wwwSummaryInRequests,Counter32,read-only,,current,,The number of requests successfully received.
.1.3.6.1.2.1.65.1.2.1.1.2,WWW-MIB::wwwSummaryOutRequests,Counter32,read-only,,current,,The number of requests generated.
.1.3.6.1.2.1.65.1.2.1.1.3,WWW-MIB::wwwSummaryInResponses,Counter32,read-only,,current,,The number of responses successfully received.
.1.3.6.1.2.1.65.1.2.1.1.4,WWW-MIB::wwwSummaryOutResponses,Counter32,read-only,,current,,The number of responses generated.
.1.3.6.1.2.1.65.1.2.1.1.5,WWW-MIB::wwwSummaryInBytes,Counter64,read-only,,current,,The number of content bytes received.
.1.3.6.1.2.1.65.1.2.1.1.6,WWW-MIB::wwwSummaryInLowBytes,Counter32,read-only,,current,,The lowest thirty-two bits of wwwSummaryInBytes.
.1.3.6.1.2.1.65.1.2.1.1.7,WWW-MIB::wwwSummaryOutBytes,Counter64,read-only,,current,,The number of content bytes transmitted.
.1.3.6.1.2.1.65.1.2.1.1.8,WWW-MIB::wwwSummaryOutLowBytes,Counter32,read-only,,current,,The lowest thirty-two bits of wwwSummaryOutBytes.
.1.3.6.1.2.1.65.1.2.2,WWW-MIB::wwwRequestInTable,,not-accessible,,current,,The table providing detailed statistics for requests received by WWW services on this system.
.1.3.6.1.2.1.65.1.2.2.1,WWW-MIB::wwwRequestInEntry,,not-accessible,wwwServiceIndex:wwwRequestInIndex,current,,Request statistics for an individual service.
.1.3.6.1.2.1.65.1.2.2.1.1,WWW-MIB::wwwRequestInIndex,OCTET,not-accessible,,current,,The particular request type the statistics apply to.
.1.3.6.1.2.1.65.1.2.2.1.2,WWW-MIB::wwwRequestInRequests,Counter32,read-only,,current,,The number of requests of this type received by this WWW service.
.1.3.6.1.2.1.65.1.2.2.1.3,WWW-MIB::wwwRequestInBytes,Counter32,read-only,,current,,The number of content bytes per request type received by this WWW service.
.1.3.6.1.2.1.65.1.2.2.1.4,WWW-MIB::wwwRequestInLastTime,OCTET,read-only,,current,,The date and time when the last byte of the last complete request of this type was received by this WWW service. The value SHALL be '0000000000000000'H if no request of this type has been received yet.
.1.3.6.1.2.1.65.1.2.3,WWW-MIB::wwwRequestOutTable,,not-accessible,,current,,The table providing detailed statistics for requests generated by the services on this system.
.1.3.6.1.2.1.65.1.2.3.1,WWW-MIB::wwwRequestOutEntry,,not-accessible,wwwServiceIndex:wwwRequestOutIndex,current,,Request statistics for an individual service.
.1.3.6.1.2.1.65.1.2.3.1.1,WWW-MIB::wwwRequestOutIndex,OCTET,not-accessible,,current,,The particular request type the statistics apply to.
.1.3.6.1.2.1.65.1.2.3.1.2,WWW-MIB::wwwRequestOutRequests,Counter32,read-only,,current,,The number of requests of this type generated by this WWW service.
.1.3.6.1.2.1.65.1.2.3.1.3,WWW-MIB::wwwRequestOutBytes,Counter32,read-only,,current,,The number of content bytes per requests type generated by this WWW service.
.1.3.6.1.2.1.65.1.2.3.1.4,WWW-MIB::wwwRequestOutLastTime,OCTET,read-only,,current,,The date and time when the first byte of the last request of this type was send by this WWW service. The value SHALL be '0000000000000000'H if no request of this type has been send yet.
.1.3.6.1.2.1.65.1.2.4,WWW-MIB::wwwResponseInTable,,not-accessible,,current,,The table providing detailed statistics for responses received by WWW services on this system.
.1.3.6.1.2.1.65.1.2.4.1,WWW-MIB::wwwResponseInEntry,,not-accessible,wwwServiceIndex:wwwResponseInIndex,current,,Response statistics for an individual service.
.1.3.6.1.2.1.65.1.2.4.1.1,WWW-MIB::wwwResponseInIndex,Integer32,not-accessible,,current,,The particular response type the statistics apply to.
.1.3.6.1.2.1.65.1.2.4.1.2,WWW-MIB::wwwResponseInResponses,Counter32,read-only,,current,,The number of responses of this type received by this WWW service.
.1.3.6.1.2.1.65.1.2.4.1.3,WWW-MIB::wwwResponseInBytes,Counter32,read-only,,current,,The number of content bytes per response type received by this WWW service.
.1.3.6.1.2.1.65.1.2.4.1.4,WWW-MIB::wwwResponseInLastTime,OCTET,read-only,,current,,The date and time when the last byte of the last complete response of this type was received by this WWW service. The value SHALL be '0000000000000000'H if no response of this type has been received yet.
.1.3.6.1.2.1.65.1.2.5,WWW-MIB::wwwResponseOutTable,,not-accessible,,current,,The table providing detailed statistics for responses generated by services on this system.
.1.3.6.1.2.1.65.1.2.5.1,WWW-MIB::wwwResponseOutEntry,,not-accessible,wwwServiceIndex:wwwResponseOutIndex,current,,Response statistics for an individual service.
.1.3.6.1.2.1.65.1.2.5.1.1,WWW-MIB::wwwResponseOutIndex,Integer32,not-accessible,,current,,The particular response type the statistics apply to.
.1.3.6.1.2.1.65.1.2.5.1.2,WWW-MIB::wwwResponseOutResponses,Counter32,read-only,,current,,The number of responses of this type generated by this WWW service.
.1.3.6.1.2.1.65.1.2.5.1.3,WWW-MIB::wwwResponseOutBytes,Counter32,read-only,,current,,The number of content bytes per response type generated by this WWW service.
.1.3.6.1.2.1.65.1.2.5.1.4,WWW-MIB::wwwResponseOutLastTime,OCTET,read-only,,current,,The date and time when the first byte of the last response of this type was sent by this WWW service. The value SHALL be '0000000000000000'H if response of this type has been send yet.
.1.3.6.1.2.1.65.1.3,WWW-MIB::wwwDocumentStatistics,,,,,,
.1.3.6.1.2.1.65.1.3.1,WWW-MIB::wwwDocCtrlTable,,not-accessible,,current,,A table which controls how the MIB implementation collects and maintains document statistics.
.1.3.6.1.2.1.65.1.3.1.1,WWW-MIB::wwwDocCtrlEntry,,not-accessible,wwwServiceIndex,current,,An entry used to configure the wwwDocLastNTable, the wwwDocBucketTable, the wwwDocAccessTopNTable, and the wwwDocBytesTopNTable.
.1.3.6.1.2.1.65.1.3.1.1.1,WWW-MIB::wwwDocCtrlLastNSize,Unsigned32,read-write,,current,,The maximum number of entries in the wwwDocLastNTable.
.1.3.6.1.2.1.65.1.3.1.1.2,WWW-MIB::wwwDocCtrlLastNLock,TimeTicks,read-write,,current,,This object allows a manager to lock the wwwDocLastNTable in order to retrieve the wwwDocLastNTable in a consistent state. The agent is expected to take a snapshot of the wwwDocLastNTable when it is locked and to continue updating the real wwwDocLastNTable table so that recent information is available as soon as the wwwDocLastNTable is unlocked again. Setting this object to a value greater than 0 will lock the table. The timer ticks backwards until it reaches 0. The table unlocks automatically once the timer reaches 0 and the timer stops ticking. A manager can increase the timer to request more time to read the table. However, any attempt to decrease the timer will fail with an inconsistentValue error. This rule ensures that multiple managers can simultaneously lock and retrieve the wwwDocLastNTable. Note that managers must cooperate in using wwwDocCtrlLastNLock. In particular, a manager MUST not keep the wwwDocLastNTable locked when it is not necessary to finish a retrieval operation.
.1.3.6.1.2.1.65.1.3.1.1.3,WWW-MIB::wwwDocCtrlBuckets,Unsigned32,read-write,,current,,The maximum number of buckets maintained by the agent before the oldest bucket is deleted. The buckets are used to populate the wwwDocAccessTopNTable and the wwwDocBytesTopNTable. The time interval captured in each bucket can be configured by setting the wwwDocCtrlBucketTimeInterval object.
.1.3.6.1.2.1.65.1.3.1.1.4,WWW-MIB::wwwDocCtrlBucketTimeInterval,INTEGER,read-write,,current,,The time interval after which a new bucket is created. Changing this object has no effect on existing buckets.
.1.3.6.1.2.1.65.1.3.1.1.5,WWW-MIB::wwwDocCtrlTopNSize,Unsigned32,read-write,,current,,The maximum number of entries shown in the wwwDocAccessTopNTable and the wwwDocBytesTopNTable. Changing this object has no effect on existing buckets.
.1.3.6.1.2.1.65.1.3.2,WWW-MIB::wwwDocLastNTable,,not-accessible,,current,,The table which logs the last N access attempts.
.1.3.6.1.2.1.65.1.3.2.1,WWW-MIB::wwwDocLastNEntry,,not-accessible,wwwServiceIndex:wwwDocLastNIndex,current,,An entry which describes a recent access attempt.
.1.3.6.1.2.1.65.1.3.2.1.1,WWW-MIB::wwwDocLastNIndex,Unsigned32,not-accessible,,current,,An arbitrary monotonically increasing integer number used for indexing the wwwDocLastNTable. The first document accessed appears in the table with this index value equal to one. Each subsequent document is indexed with the next sequential index value. The Nth document accessed will be indexed by N. This table presents a sliding window of the last wwwDocCtrlLastNSize documents accessed. Thus, entries in this table will be indexed by N-wwwDocCtrlLastNSize thru N if N > wwwDocCtrlLastNSize and 1 thru N if N <= wwwDocCtrlLastNSize. The wwwDocCtrlLastNLock attribute can be used to lock this table to allow the manager to read its contents.
.1.3.6.1.2.1.65.1.3.2.1.2,WWW-MIB::wwwDocLastNName,OCTET,read-only,,current,,The name of the document for which access was attempted.
.1.3.6.1.2.1.65.1.3.2.1.3,WWW-MIB::wwwDocLastNTimeStamp,OCTET,read-only,,current,,The date and time of the last attempt to access this document.
.1.3.6.1.2.1.65.1.3.2.1.4,WWW-MIB::wwwDocLastNRequestType,OCTET,read-only,,current,,The protocol request type which was received by the server when this document access was attempted.
.1.3.6.1.2.1.65.1.3.2.1.5,WWW-MIB::wwwDocLastNResponseType,Integer32,read-only,,current,,The protocol response type which was sent to the client as a result of this attempt to access a document. This object contains the type of the primary response if there were multiple responses to a single request.
.1.3.6.1.2.1.65.1.3.2.1.6,WWW-MIB::wwwDocLastNStatusMsg,OCTET,read-only,,current,,This object contains a human readable description of the reason why the wwwDocLastNResponseType was returned to the client. This object defines the implementation-specific reason if the value of wwwDocLastNResponseType indicates an error. For example, this object can indicate that the requested document could not be transferred due to a timeout condition or the document could not be transferred because a 'soft link' pointing to the document could not be resolved.
.1.3.6.1.2.1.65.1.3.2.1.7,WWW-MIB::wwwDocLastNBytes,Unsigned32,read-only,,current,,The number of content bytes that were returned as a result of this attempt to access a document.
.1.3.6.1.2.1.65.1.3.3,WWW-MIB::wwwDocBucketTable,,not-accessible,,current,,This table provides administrative summary information for the buckets maintained per WWW service.
.1.3.6.1.2.1.65.1.3.3.1,WWW-MIB::wwwDocBucketEntry,,not-accessible,wwwServiceIndex:wwwDocBucketIndex,current,,An entry which describes the parameters associated with a particular bucket.
.1.3.6.1.2.1.65.1.3.3.1.1,WWW-MIB::wwwDocBucketIndex,Unsigned32,not-accessible,,current,,An arbitrary monotonically increasing integer number used for indexing the wwwDocBucketTable. The index number wraps to 1 whenever the maximum value is reached.
.1.3.6.1.2.1.65.1.3.3.1.2,WWW-MIB::wwwDocBucketTimeStamp,OCTET,read-only,,current,,The date and time when the bucket was made available.
.1.3.6.1.2.1.65.1.3.3.1.3,WWW-MIB::wwwDocBucketAccesses,Unsigned32,read-only,,current,,The total number of access attempts for any document provided by this WWW service during the time interval over which this bucket was created.
.1.3.6.1.2.1.65.1.3.3.1.4,WWW-MIB::wwwDocBucketDocuments,Unsigned32,read-only,,current,,The total number of different documents for which access was attempted this this WWW service during the time interval over which this bucket was created.
.1.3.6.1.2.1.65.1.3.3.1.5,WWW-MIB::wwwDocBucketBytes,Unsigned32,read-only,,current,,The total number of content bytes which were transferred from this WWW service during the time interval over which this bucket was created.
.1.3.6.1.2.1.65.1.3.4,WWW-MIB::wwwDocAccessTopNTable,,not-accessible,,current,,The table of the most frequently accessed documents in a given bucket. This table is sorted by the column wwwDocAccessTopNAccesses. Entries having the same number of accesses are secondarily sorted by wwwDocAccessTopNBytes. Entries with the same number of accesses and the same number of bytes will have an arbitrary order.
.1.3.6.1.2.1.65.1.3.4.1,WWW-MIB::wwwDocAccessTopNEntry,,not-accessible,wwwServiceIndex:wwwDocBucketIndex:wwwDocAccessTopNIndex,current,,An entry in the top N table sorted by document accesses.
.1.3.6.1.2.1.65.1.3.4.1.1,WWW-MIB::wwwDocAccessTopNIndex,Unsigned32,not-accessible,,current,,An arbitrary monotonically increasing integer number used for indexing the wwwDocAccessTopNTable. The index is inversely correlated to the sorting order of the table. The document with the highest access count will get the index value 1.
.1.3.6.1.2.1.65.1.3.4.1.2,WWW-MIB::wwwDocAccessTopNName,OCTET,read-only,,current,,The name of the document for which access was attempted.
.1.3.6.1.2.1.65.1.3.4.1.3,WWW-MIB::wwwDocAccessTopNAccesses,Unsigned32,read-only,,current,,The total number of access attempts for this document.
.1.3.6.1.2.1.65.1.3.4.1.4,WWW-MIB::wwwDocAccessTopNBytes,Unsigned32,read-only,,current,,The total number of content bytes that were transmitted as a result of attempts to access this document.
.1.3.6.1.2.1.65.1.3.4.1.5,WWW-MIB::wwwDocAccessTopNLastResponseType,Integer32,read-only,,current,,The protocol response type which was sent to the client as a result of the last attempt to access this document. This object contains the type of the primary response if there were multiple responses to a single request.
.1.3.6.1.2.1.65.1.3.5,WWW-MIB::wwwDocBytesTopNTable,,not-accessible,,current,,The table of the documents which caused most network traffic in a given bucket. This table is sorted by the column wwwDocBytesTopNBytes. Entries having the same number bytes are secondarily sorted by wwwDocBytesTopNAccesses. Entries with the same number of accesses and the same number of bytes will have an arbitrary order.
.1.3.6.1.2.1.65.1.3.5.1,WWW-MIB::wwwDocBytesTopNEntry,,not-accessible,wwwServiceIndex:wwwDocBucketIndex:wwwDocBytesTopNIndex,current,,An entry in the top N table sorted by network traffic.
.1.3.6.1.2.1.65.1.3.5.1.1,WWW-MIB::wwwDocBytesTopNIndex,Unsigned32,not-accessible,,current,,An arbitrary monotonically increasing integer number used for indexing the wwwDocBytesTopNTable. The index is inversely correlated to the sorting order of the table. The document with the highest byte count will get the index value 1.
.1.3.6.1.2.1.65.1.3.5.1.2,WWW-MIB::wwwDocBytesTopNName,OCTET,read-only,,current,,The name of the document for which access was attempted.
.1.3.6.1.2.1.65.1.3.5.1.3,WWW-MIB::wwwDocBytesTopNAccesses,Unsigned32,read-only,,current,,The total number of access attempts for this document.
.1.3.6.1.2.1.65.1.3.5.1.4,WWW-MIB::wwwDocBytesTopNBytes,Unsigned32,read-only,,current,,The total number of content bytes that were transmitted as a result of attempts to access this document.
.1.3.6.1.2.1.65.1.3.5.1.5,WWW-MIB::wwwDocBytesTopNLastResponseType,Integer32,read-only,,current,,The protocol response type which was sent to the client as a result of the last attempt to access this document. This object contains the type of the primary response if there were multiple responses to a single request.
.1.3.6.1.2.1.65.2,WWW-MIB::wwwMIBConformance,,,,,,
.1.3.6.1.2.1.65.2.1,WWW-MIB::wwwMIBCompliances,,,,,,
.1.3.6.1.2.1.65.2.1.1,WWW-MIB::wwwMinimalCompliance,,,,,,The compliance statement for SNMP agents which implement the minimal subset of the WWW-MIB. Implementors might choose this subset for high-performance server where full compliance might be to expensive.
.1.3.6.1.2.1.65.2.1.2,WWW-MIB::wwwFullCompliance,,,,,,The compliance statement for SNMP agents which implement the full WWW-MIB.
.1.3.6.1.2.1.65.2.2,WWW-MIB::wwwMIBGroups,,,,,,
.1.3.6.1.2.1.65.2.2.1,WWW-MIB::wwwServiceGroup,,,,,,A collection of objects providing information about the WWW services known by the SNMP agent.
.1.3.6.1.2.1.65.2.2.2,WWW-MIB::wwwSummaryGroup,,,,,,A collection of objects providing summary statistics about requests and responses generated and received by a WWW service.
.1.3.6.1.2.1.65.2.2.3,WWW-MIB::wwwRequestInGroup,,,,,,A collection of objects providing detailed statistics about requests received by a WWW service.
.1.3.6.1.2.1.65.2.2.4,WWW-MIB::wwwRequestOutGroup,,,,,,A collection of objects providing detailed statistics about requests generated by a WWW service.
.1.3.6.1.2.1.65.2.2.5,WWW-MIB::wwwResponseInGroup,,,,,,A collection of objects providing detailed statistics about responses received by a WWW service.
.1.3.6.1.2.1.65.2.2.6,WWW-MIB::wwwResponseOutGroup,,,,,,A collection of objects providing detailed statistics about responses generated by a WWW service.
.1.3.6.1.2.1.65.2.2.7,WWW-MIB::wwwDocumentGroup,,,,,,A collection of objects providing information about accesses to documents.
.1.3.6.1.2.1.66,DIRECTORY-SERVER-MIB::dsMIB,,,,,, The MIB module for monitoring Directory Services.
.1.3.6.1.2.1.66.1,DIRECTORY-SERVER-MIB::dsTable,,not-accessible,,current,, The table holding information related to the Directory Servers.
.1.3.6.1.2.1.66.1.1,DIRECTORY-SERVER-MIB::dsTableEntry,,not-accessible,applIndex,current,, Entry containing summary description for a Directory Server.
.1.3.6.1.2.1.66.1.1.1,DIRECTORY-SERVER-MIB::dsServerType,BITS,read-only,,current,frontEndDirectoryServer(0):backEndDirectoryServer(1),This object indicates whether the server is a frontend or, a backend or, both. If the server is a frontend, then the frontEndDirectoryServer bit will be set. Similarly for the backend.
.1.3.6.1.2.1.66.1.1.2,DIRECTORY-SERVER-MIB::dsServerDescription,OCTET,read-only,,current,,A text description of the application. This information is intended to identify and briefly describe the application in a status display.
.1.3.6.1.2.1.66.1.1.3,DIRECTORY-SERVER-MIB::dsMasterEntries,Gauge32,read-only,,current,, Number of entries mastered in the Directory Server.
.1.3.6.1.2.1.66.1.1.4,DIRECTORY-SERVER-MIB::dsCopyEntries,Gauge32,read-only,,current,, Number of entries for which systematic (slave) copies are maintained in the Directory Server.
.1.3.6.1.2.1.66.1.1.5,DIRECTORY-SERVER-MIB::dsCacheEntries,Gauge32,read-only,,current,, Number of entries cached (non-systematic copies) in the Directory Server. This will include the entries that are cached partially. The negative cache is not counted.
.1.3.6.1.2.1.66.1.1.6,DIRECTORY-SERVER-MIB::dsCacheHits,Counter32,read-only,,current,, Number of operations that were serviced from the locally held cache.
.1.3.6.1.2.1.66.1.1.7,DIRECTORY-SERVER-MIB::dsSlaveHits,Counter32,read-only,,current,, Number of operations that were serviced from the locally held object replications ( copy- entries).
.1.3.6.1.2.1.66.2,DIRECTORY-SERVER-MIB::dsApplIfOpsTable,,not-accessible,,current,, The table holding information related to the Directory Server operations.
.1.3.6.1.2.1.66.2.1,DIRECTORY-SERVER-MIB::dsApplIfOpsEntry,,not-accessible,applIndex:dsApplIfProtocolIndex,current,, Entry containing operations related statistics for a Directory Server.
.1.3.6.1.2.1.66.2.1.1,DIRECTORY-SERVER-MIB::dsApplIfProtocolIndex,INTEGER,read-only,,current,,An index to uniquely identify an entry corresponding to a application-layer protocol interface. This index is used for lexicographic ordering of the table.
.1.3.6.1.2.1.66.2.1.2,DIRECTORY-SERVER-MIB::dsApplIfProtocol,OBJECT,read-only,,current,,An identification of the protocol being used by the application on this interface. For an OSI Application, this will be the Application Context. For Internet applications, the IANA maintains a registry[22] of the OIDs which correspond to well-known applications. If the application protocol is not listed in the registry, an OID value of the form {applTCPProtoID port} or {applUDProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol. The OIDs applTCPProtoID and applUDPProtoID are defined in NETWORK-SERVICES-MIB
.1.3.6.1.2.1.66.2.1.3,DIRECTORY-SERVER-MIB::dsApplIfUnauthBinds,Counter32,read-only,,current,, Number of unauthenticated/anonymous bind requests received.
.1.3.6.1.2.1.66.2.1.4,DIRECTORY-SERVER-MIB::dsApplIfSimpleAuthBinds,Counter32,read-only,,current,, Number of bind requests that were authenticated using simple authentication procedures like password checks. This includes the password authentication using SASL mechanisms like CRAM-MD5.
.1.3.6.1.2.1.66.2.1.5,DIRECTORY-SERVER-MIB::dsApplIfStrongAuthBinds,Counter32,read-only,,current,, Number of bind requests that were authenticated using TLS and X.500 strong authentication procedures. This includes the binds that were authenticated using external authentication procedures.
.1.3.6.1.2.1.66.2.1.6,DIRECTORY-SERVER-MIB::dsApplIfBindSecurityErrors,Counter32,read-only,,current,, Number of bind requests that have been rejected due to inappropriate authentication or invalid credentials.
.1.3.6.1.2.1.66.2.1.7,DIRECTORY-SERVER-MIB::dsApplIfInOps,Counter32,read-only,,current,, Number of requests received from DUAs or other Directory Servers.
.1.3.6.1.2.1.66.2.1.8,DIRECTORY-SERVER-MIB::dsApplIfReadOps,Counter32,read-only,,current,, Number of read requests received.
.1.3.6.1.2.1.66.2.1.9,DIRECTORY-SERVER-MIB::dsApplIfCompareOps,Counter32,read-only,,current,, Number of compare requests received.
.1.3.6.1.2.1.66.2.1.10,DIRECTORY-SERVER-MIB::dsApplIfAddEntryOps,Counter32,read-only,,current,, Number of addEntry requests received.
.1.3.6.1.2.1.66.2.1.11,DIRECTORY-SERVER-MIB::dsApplIfRemoveEntryOps,Counter32,read-only,,current,, Number of removeEntry requests received.
.1.3.6.1.2.1.66.2.1.12,DIRECTORY-SERVER-MIB::dsApplIfModifyEntryOps,Counter32,read-only,,current,, Number of modifyEntry requests received.
.1.3.6.1.2.1.66.2.1.13,DIRECTORY-SERVER-MIB::dsApplIfModifyRDNOps,Counter32,read-only,,current,, Number of modifyRDN requests received.
.1.3.6.1.2.1.66.2.1.14,DIRECTORY-SERVER-MIB::dsApplIfListOps,Counter32,read-only,,current,, Number of list requests received.
.1.3.6.1.2.1.66.2.1.15,DIRECTORY-SERVER-MIB::dsApplIfSearchOps,Counter32,read-only,,current,, Number of search requests- baseObject searches, oneLevel searches and whole subtree searches, received.
.1.3.6.1.2.1.66.2.1.16,DIRECTORY-SERVER-MIB::dsApplIfOneLevelSearchOps,Counter32,read-only,,current,, Number of oneLevel search requests received.
.1.3.6.1.2.1.66.2.1.17,DIRECTORY-SERVER-MIB::dsApplIfWholeSubtreeSearchOps,Counter32,read-only,,current,, Number of whole subtree search requests received.
.1.3.6.1.2.1.66.2.1.18,DIRECTORY-SERVER-MIB::dsApplIfReferrals,Counter32,read-only,,current,, Number of referrals returned in response to requests for operations.
.1.3.6.1.2.1.66.2.1.19,DIRECTORY-SERVER-MIB::dsApplIfChainings,Counter32,read-only,,current,, Number of operations forwarded by this Directory Server to other Directory Servers.
.1.3.6.1.2.1.66.2.1.20,DIRECTORY-SERVER-MIB::dsApplIfSecurityErrors,Counter32,read-only,,current,, Number of requests received which did not meet the security requirements. 
.1.3.6.1.2.1.66.2.1.21,DIRECTORY-SERVER-MIB::dsApplIfErrors,Counter32,read-only,,current,, Number of requests that could not be serviced due to errors other than security errors, and referrals. A partially serviced operation will not be counted as an error. The errors include naming-related, update-related, attribute-related and service-related errors.
.1.3.6.1.2.1.66.2.1.22,DIRECTORY-SERVER-MIB::dsApplIfReplicationUpdatesIn,Counter32,read-only,,current,, Number of replication updates fetched or received from supplier Directory Servers.
.1.3.6.1.2.1.66.2.1.23,DIRECTORY-SERVER-MIB::dsApplIfReplicationUpdatesOut,Counter32,read-only,,current,, Number of replication updates sent to or taken by consumer Directory Servers.
.1.3.6.1.2.1.66.2.1.24,DIRECTORY-SERVER-MIB::dsApplIfInBytes,Counter32,read-only,,current,, Incoming traffic, in bytes, on the interface. This will include requests from DUAs as well as responses from other Directory Servers.
.1.3.6.1.2.1.66.2.1.25,DIRECTORY-SERVER-MIB::dsApplIfOutBytes,Counter32,read-only,,current,, Outgoing traffic in bytes on the interface. This will include responses to DUAs and Directory Servers as well as requests to other Directory Servers.
.1.3.6.1.2.1.66.3,DIRECTORY-SERVER-MIB::dsIntTable,,not-accessible,,current,, Each row of this table contains some details related to the history of the interaction of the monitored Directory Server with its peer Directory Servers.
.1.3.6.1.2.1.66.3.1,DIRECTORY-SERVER-MIB::dsIntEntry,,not-accessible,applIndex:dsIntEntIndex:dsApplIfProtocolIndex,current,, Entry containing interaction details of a Directory Server with a peer Directory Server.
.1.3.6.1.2.1.66.3.1.1,DIRECTORY-SERVER-MIB::dsIntEntIndex,INTEGER,not-accessible,,current,, Together with applIndex and dsApplIfProtocolIndex, this object forms the unique key to identify the conceptual row which contains useful info on the (attempted) interaction between the Directory Server (referred to by applIndex) and a peer Directory Server using a particular protocol.
.1.3.6.1.2.1.66.3.1.2,DIRECTORY-SERVER-MIB::dsIntEntDirectoryName,OCTET,read-only,,current,, Distinguished Name of the peer Directory Server to which this entry pertains.
.1.3.6.1.2.1.66.3.1.3,DIRECTORY-SERVER-MIB::dsIntEntTimeOfCreation,TimeTicks,read-only,,current,, The value of sysUpTime when this row was created. If the entry was created before the network management subsystem was initialized, this object will contain a value of zero.
.1.3.6.1.2.1.66.3.1.4,DIRECTORY-SERVER-MIB::dsIntEntTimeOfLastAttempt,TimeTicks,read-only,,current,, The value of sysUpTime when the last attempt was made to contact the peer Directory Server. If the last attempt was made before the network management subsystem was initialized, this object will contain a value of zero.
.1.3.6.1.2.1.66.3.1.5,DIRECTORY-SERVER-MIB::dsIntEntTimeOfLastSuccess,TimeTicks,read-only,,current,, The value of sysUpTime when the last attempt made to contact the peer Directory Server was successful. If there have been no successful attempts this entry will have a value of zero. If the last successful attempt was made before the network management subsystem was initialized, this object will contain a value of zero.
.1.3.6.1.2.1.66.3.1.6,DIRECTORY-SERVER-MIB::dsIntEntFailuresSinceLastSuccess,Gauge32,read-only,,current,, The number of failures since the last time an attempt to contact the peer Directory Server was successful. If there have been no successful attempts, this counter will contain the number of failures since this entry was created.
.1.3.6.1.2.1.66.3.1.7,DIRECTORY-SERVER-MIB::dsIntEntFailures,Gauge32,read-only,,current,, Cumulative failures in contacting the peer Directory Server since the creation of this entry.
.1.3.6.1.2.1.66.3.1.8,DIRECTORY-SERVER-MIB::dsIntEntSuccesses,Gauge32,read-only,,current,, Cumulative successes in contacting the peer Directory Server since the creation of this entry.
.1.3.6.1.2.1.66.3.1.9,DIRECTORY-SERVER-MIB::dsIntEntURL,OCTET,read-only,,current,, URL of the peer Directory Server.
.1.3.6.1.2.1.66.4,DIRECTORY-SERVER-MIB::dsConformance,,,,,,
.1.3.6.1.2.1.66.4.1,DIRECTORY-SERVER-MIB::dsGroups,,,,,,
.1.3.6.1.2.1.66.4.1.1,DIRECTORY-SERVER-MIB::dsEntryGroup,,,,,, A collection of objects for a summary overview of the Directory Servers.
.1.3.6.1.2.1.66.4.1.2,DIRECTORY-SERVER-MIB::dsOpsGroup,,,,,, A collection of objects for monitoring the Directory Server operations.
.1.3.6.1.2.1.66.4.1.3,DIRECTORY-SERVER-MIB::dsIntGroup,,,,,, A collection of objects for monitoring the Directory Server's interaction with peer Directory Servers.
.1.3.6.1.2.1.66.4.2,DIRECTORY-SERVER-MIB::dsCompliances,,,,,,
.1.3.6.1.2.1.66.4.2.1,DIRECTORY-SERVER-MIB::dsEntryCompliance,,,,,,The compliance statement for SNMP entities which implement the DIRECTORY-SERVER-MIB for a summary overview of the Directory Servers .
.1.3.6.1.2.1.66.4.2.2,DIRECTORY-SERVER-MIB::dsOpsCompliance,,,,,,The compliance statement for SNMP entities which implement the DIRECTORY-SERVER-MIB for monitoring Directory Server operations, entry statistics and cache performance.
.1.3.6.1.2.1.66.4.2.3,DIRECTORY-SERVER-MIB::dsIntCompliance,,,,,, The compliance statement for SNMP entities which implement the DIRECTORY-SERVER-MIB for monitoring Directory Server operations and the interaction of the Directory Server with peer Directory Servers.
.1.3.6.1.2.1.66.4.2.4,DIRECTORY-SERVER-MIB::dsOpsIntCompliance,,,,,, The compliance statement for SNMP entities which implement the DIRECTORY-SERVER-MIB for monitoring Directory Server operations and the interaction of the Directory Server with peer Directory Servers.
.1.3.6.1.2.1.67,RADIUS-ACC-CLIENT-MIB::radiusMIB,,,,,,The OID assigned to RADIUS MIB work by the IANA.
.1.3.6.1.2.1.67.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthentication,,,,,,
.1.3.6.1.2.1.67.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIB,,,,,,The MIB module for entities implementing the server side of the Remote Authentication Dial-In User Service (RADIUS) authentication protocol. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4669; see the RFC itself for full legal notices.
.1.3.6.1.2.1.67.1.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBObjects,,,,,,
.1.3.6.1.2.1.67.1.1.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServ,,,,,,
.1.3.6.1.2.1.67.1.1.1.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServIdent,OCTET,read-only,,current,,The implementation identification string for the RADIUS authentication server software in use on the system, for example, 'FNS-2.1'.
.1.3.6.1.2.1.67.1.1.1.1.2,RADIUS-AUTH-SERVER-MIB::radiusAuthServUpTime,TimeTicks,read-only,,current,,If the server has a persistent state (e.g., a process), this value will be the time elapsed (in hundredths of a second) since the server process was started. For software without persistent state, this value will be zero.
.1.3.6.1.2.1.67.1.1.1.1.3,RADIUS-AUTH-SERVER-MIB::radiusAuthServResetTime,TimeTicks,read-only,,current,,If the server has a persistent state (e.g., a process) and supports a 'reset' operation (e.g., can be told to re-read configuration files), this value will be the time elapsed (in hundredths of a second) since the server was 'reset.' For software that does not have persistence or does not support a 'reset' operation, this value will be zero.
.1.3.6.1.2.1.67.1.1.1.1.4,RADIUS-AUTH-SERVER-MIB::radiusAuthServConfigReset,INTEGER,read-write,,current,other(1):reset(2):initializing(3):running(4),Status/action object to reinitialize any persistent server state. When set to reset(2), any persistent server state (such as a process) is reinitialized as if the server had just been started. This value will never be returned by a read operation. When read, one of the following values will be returned: other(1) - server in some unknown state; initializing(3) - server (re)initializing; running(4) - server currently running.
.1.3.6.1.2.1.67.1.1.1.1.5,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalAccessRequests,Counter32,read-only,,current,,The number of packets received on the authentication port.
.1.3.6.1.2.1.67.1.1.1.1.6,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalInvalidRequests,Counter32,read-only,,current,,The number of RADIUS Access-Request packets received from unknown addresses.
.1.3.6.1.2.1.67.1.1.1.1.7,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalDupAccessRequests,Counter32,read-only,,current,,The number of duplicate RADIUS Access-Request packets received.
.1.3.6.1.2.1.67.1.1.1.1.8,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalAccessAccepts,Counter32,read-only,,current,,The number of RADIUS Access-Accept packets sent.
.1.3.6.1.2.1.67.1.1.1.1.9,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalAccessRejects,Counter32,read-only,,current,,The number of RADIUS Access-Reject packets sent.
.1.3.6.1.2.1.67.1.1.1.1.10,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalAccessChallenges,Counter32,read-only,,current,,The number of RADIUS Access-Challenge packets sent.
.1.3.6.1.2.1.67.1.1.1.1.11,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalMalformedAccessRequests,Counter32,read-only,,current,,The number of malformed RADIUS Access-Request packets received. Bad authenticators and unknown types are not included as malformed Access-Requests.
.1.3.6.1.2.1.67.1.1.1.1.12,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Authentication-Request packets that contained invalid Message Authenticator attributes received.
.1.3.6.1.2.1.67.1.1.1.1.13,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalPacketsDropped,Counter32,read-only,,current,,The number of incoming packets silently discarded for some reason other than malformed, bad authenticators or unknown types.
.1.3.6.1.2.1.67.1.1.1.1.14,RADIUS-AUTH-SERVER-MIB::radiusAuthServTotalUnknownTypes,Counter32,read-only,,current,,The number of RADIUS packets of unknown type that were received.
.1.3.6.1.2.1.67.1.1.1.1.15,RADIUS-AUTH-SERVER-MIB::radiusAuthClientTable,,not-accessible,,deprecated,,The (conceptual) table listing the RADIUS authentication clients with which the server shares a secret.
.1.3.6.1.2.1.67.1.1.1.1.15.1,RADIUS-AUTH-SERVER-MIB::radiusAuthClientEntry,,not-accessible,radiusAuthClientIndex,deprecated,,An entry (conceptual row) representing a RADIUS authentication client with which the server shares a secret.
.1.3.6.1.2.1.67.1.1.1.1.15.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthClientIndex,Integer32,not-accessible,,deprecated,,A number uniquely identifying each RADIUS authentication client with which this server communicates.
.1.3.6.1.2.1.67.1.1.1.1.15.1.2,RADIUS-AUTH-SERVER-MIB::radiusAuthClientAddress,IpAddress,read-only,,deprecated,,The NAS-IP-Address of the RADIUS authentication client referred to in this table entry.
.1.3.6.1.2.1.67.1.1.1.1.15.1.3,RADIUS-AUTH-SERVER-MIB::radiusAuthClientID,OCTET,read-only,,deprecated,,The NAS-Identifier of the RADIUS authentication client referred to in this table entry. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.67.1.1.1.1.15.1.4,RADIUS-AUTH-SERVER-MIB::radiusAuthServAccessRequests,Counter32,read-only,,deprecated,,The number of packets received on the authentication port from this client.
.1.3.6.1.2.1.67.1.1.1.1.15.1.5,RADIUS-AUTH-SERVER-MIB::radiusAuthServDupAccessRequests,Counter32,read-only,,deprecated,,The number of duplicate RADIUS Access-Request packets received from this client.
.1.3.6.1.2.1.67.1.1.1.1.15.1.6,RADIUS-AUTH-SERVER-MIB::radiusAuthServAccessAccepts,Counter32,read-only,,deprecated,,The number of RADIUS Access-Accept packets sent to this client.
.1.3.6.1.2.1.67.1.1.1.1.15.1.7,RADIUS-AUTH-SERVER-MIB::radiusAuthServAccessRejects,Counter32,read-only,,deprecated,,The number of RADIUS Access-Reject packets sent to this client.
.1.3.6.1.2.1.67.1.1.1.1.15.1.8,RADIUS-AUTH-SERVER-MIB::radiusAuthServAccessChallenges,Counter32,read-only,,deprecated,,The number of RADIUS Access-Challenge packets sent to this client.
.1.3.6.1.2.1.67.1.1.1.1.15.1.9,RADIUS-AUTH-SERVER-MIB::radiusAuthServMalformedAccessRequests,Counter32,read-only,,deprecated,,The number of malformed RADIUS Access-Request packets received from this client. Bad authenticators and unknown types are not included as malformed Access-Requests.
.1.3.6.1.2.1.67.1.1.1.1.15.1.10,RADIUS-AUTH-SERVER-MIB::radiusAuthServBadAuthenticators,Counter32,read-only,,deprecated,,The number of RADIUS Authentication-Request packets that contained invalid Message Authenticator attributes received from this client.
.1.3.6.1.2.1.67.1.1.1.1.15.1.11,RADIUS-AUTH-SERVER-MIB::radiusAuthServPacketsDropped,Counter32,read-only,,deprecated,,The number of incoming packets from this client silently discarded for some reason other than malformed, bad authenticators or unknown types.
.1.3.6.1.2.1.67.1.1.1.1.15.1.12,RADIUS-AUTH-SERVER-MIB::radiusAuthServUnknownTypes,Counter32,read-only,,deprecated,,The number of RADIUS packets of unknown type that were received from this client.
.1.3.6.1.2.1.67.1.1.1.1.16,RADIUS-AUTH-SERVER-MIB::radiusAuthClientExtTable,,not-accessible,,current,,The (conceptual) table listing the RADIUS authentication clients with which the server shares a secret.
.1.3.6.1.2.1.67.1.1.1.1.16.1,RADIUS-AUTH-SERVER-MIB::radiusAuthClientExtEntry,,not-accessible,radiusAuthClientExtIndex,current,,An entry (conceptual row) representing a RADIUS authentication client with which the server shares a secret.
.1.3.6.1.2.1.67.1.1.1.1.16.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthClientExtIndex,Integer32,not-accessible,,current,,A number uniquely identifying each RADIUS authentication client with which this server communicates.
.1.3.6.1.2.1.67.1.1.1.1.16.1.2,RADIUS-AUTH-SERVER-MIB::radiusAuthClientInetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address format used for the radiusAuthClientInetAddress object.
.1.3.6.1.2.1.67.1.1.1.1.16.1.3,RADIUS-AUTH-SERVER-MIB::radiusAuthClientInetAddress,OCTET,read-only,,current,,The IP address of the RADIUS authentication client referred to in this table entry, using the version-neutral IP address format.
.1.3.6.1.2.1.67.1.1.1.1.16.1.4,RADIUS-AUTH-SERVER-MIB::radiusAuthClientExtID,OCTET,read-only,,current,,The NAS-Identifier of the RADIUS authentication client referred to in this table entry. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.67.1.1.1.1.16.1.5,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtAccessRequests,Counter32,read-only,,current,,The number of packets received on the authentication port from this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.6,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtDupAccessRequests,Counter32,read-only,,current,,The number of duplicate RADIUS Access-Request packets received from this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.7,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtAccessAccepts,Counter32,read-only,,current,,The number of RADIUS Access-Accept packets sent to this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.8,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtAccessRejects,Counter32,read-only,,current,,The number of RADIUS Access-Reject packets sent to this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.9,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtAccessChallenges,Counter32,read-only,,current,,The number of RADIUS Access-Challenge packets sent to this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.10,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtMalformedAccessRequests,Counter32,read-only,,current,,The number of malformed RADIUS Access-Request packets received from this client. Bad authenticators and unknown types are not included as malformed Access-Requests. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.11,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Authentication-Request packets that contained invalid Message Authenticator attributes received from this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.12,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtPacketsDropped,Counter32,read-only,,current,,The number of incoming packets from this client silently discarded for some reason other than malformed, bad authenticators or unknown types. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.13,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtUnknownTypes,Counter32,read-only,,current,,The number of RADIUS packets of unknown type that were received from this client. This counter may experience a discontinuity when the RADIUS Server module within the managed entity is reinitialized, as indicated by the current value of radiusAuthServCounterDiscontinuity.
.1.3.6.1.2.1.67.1.1.1.1.16.1.14,RADIUS-AUTH-SERVER-MIB::radiusAuthServCounterDiscontinuity,TimeTicks,read-only,,current,,The number of centiseconds since the last discontinuity in the RADIUS Server counters. A discontinuity may be the result of a reinitialization of the RADIUS Server module within the managed entity.
.1.3.6.1.2.1.67.1.1.2,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBConformance,,,,,,
.1.3.6.1.2.1.67.1.1.2.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBCompliances,,,,,,
.1.3.6.1.2.1.67.1.1.2.1.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBCompliance,,,,,,The compliance statement for authentication servers implementing the RADIUS Authentication Server MIB. Implementation of this module is for IPv4-only entities, or for backwards compatibility use with entities that support both IPv4 and IPv6.
.1.3.6.1.2.1.67.1.1.2.1.2,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBExtCompliance,,,,,,The compliance statement for authentication servers implementing the RADIUS Authentication Server IPv6 Extensions MIB. Implementation of this module is for entities that support IPv6, or support IPv4 and IPv6.
.1.3.6.1.2.1.67.1.1.2.2,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBGroups,,,,,,
.1.3.6.1.2.1.67.1.1.2.2.1,RADIUS-AUTH-SERVER-MIB::radiusAuthServMIBGroup,,,,,,The collection of objects providing management of a RADIUS Authentication Server.
.1.3.6.1.2.1.67.1.1.2.2.2,RADIUS-AUTH-SERVER-MIB::radiusAuthServExtMIBGroup,,,,,,The collection of objects providing management of a RADIUS Authentication Server.
.1.3.6.1.2.1.67.1.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIB,,,,,,The MIB module for entities implementing the client side of the Remote Authentication Dial-In User Service (RADIUS) authentication protocol. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4668; see the RFC itself for full legal notices.
.1.3.6.1.2.1.67.1.2.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIBObjects,,,,,,
.1.3.6.1.2.1.67.1.2.1.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthClient,,,,,,
.1.3.6.1.2.1.67.1.2.1.1.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientInvalidServerAddresses,Counter32,read-only,,current,,The number of RADIUS Access-Response packets received from unknown addresses.
.1.3.6.1.2.1.67.1.2.1.1.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientIdentifier,OCTET,read-only,,current,,The NAS-Identifier of the RADIUS authentication client. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.67.1.2.1.1.3,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerTable,,not-accessible,,deprecated,,The (conceptual) table listing the RADIUS authentication servers with which the client shares a secret.
.1.3.6.1.2.1.67.1.2.1.1.3.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerEntry,,not-accessible,radiusAuthServerIndex,deprecated,,An entry (conceptual row) representing a RADIUS authentication server with which the client shares a secret.
.1.3.6.1.2.1.67.1.2.1.1.3.1.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerIndex,Integer32,not-accessible,,deprecated,,A number uniquely identifying each RADIUS Authentication server with which this client communicates.
.1.3.6.1.2.1.67.1.2.1.1.3.1.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerAddress,IpAddress,read-only,,deprecated,,The IP address of the RADIUS authentication server referred to in this table entry.
.1.3.6.1.2.1.67.1.2.1.1.3.1.3,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientServerPortNumber,Integer32,read-only,,deprecated,,The UDP port the client is using to send requests to this server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.4,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientRoundTripTime,TimeTicks,read-only,,deprecated,,The time interval (in hundredths of a second) between the most recent Access-Reply/Access-Challenge and the Access-Request that matched it from this RADIUS authentication server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.5,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientAccessRequests,Counter32,read-only,,deprecated,,The number of RADIUS Access-Request packets sent to this server. This does not include retransmissions.
.1.3.6.1.2.1.67.1.2.1.1.3.1.6,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientAccessRetransmissions,Counter32,read-only,,deprecated,,The number of RADIUS Access-Request packets retransmitted to this RADIUS authentication server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.7,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientAccessAccepts,Counter32,read-only,,deprecated,,The number of RADIUS Access-Accept packets (valid or invalid) received from this server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.8,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientAccessRejects,Counter32,read-only,,deprecated,,The number of RADIUS Access-Reject packets (valid or invalid) received from this server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.9,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientAccessChallenges,Counter32,read-only,,deprecated,,The number of RADIUS Access-Challenge packets (valid or invalid) received from this server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.10,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMalformedAccessResponses,Counter32,read-only,,deprecated,,The number of malformed RADIUS Access-Response packets received from this server. Malformed packets include packets with an invalid length. Bad authenticators or Message Authenticator attributes or unknown types are not included as malformed access responses.
.1.3.6.1.2.1.67.1.2.1.1.3.1.11,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientBadAuthenticators,Counter32,read-only,,deprecated,,The number of RADIUS Access-Response packets containing invalid authenticators or Message Authenticator attributes received from this server.
.1.3.6.1.2.1.67.1.2.1.1.3.1.12,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientPendingRequests,Gauge32,read-only,,deprecated,,The number of RADIUS Access-Request packets destined for this server that have not yet timed out or received a response. This variable is incremented when an Access-Request is sent and decremented due to receipt of an Access-Accept, Access-Reject, Access-Challenge, timeout, or retransmission.
.1.3.6.1.2.1.67.1.2.1.1.3.1.13,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientTimeouts,Counter32,read-only,,deprecated,,The number of authentication timeouts to this server. After a timeout, the client may retry to the same server, send to a different server, or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to a different server is counted as a Request as well as a timeout.
.1.3.6.1.2.1.67.1.2.1.1.3.1.14,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientUnknownTypes,Counter32,read-only,,deprecated,,The number of RADIUS packets of unknown type that were received from this server on the authentication port.
.1.3.6.1.2.1.67.1.2.1.1.3.1.15,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientPacketsDropped,Counter32,read-only,,deprecated,,The number of RADIUS packets that were received from this server on the authentication port and dropped for some other reason.
.1.3.6.1.2.1.67.1.2.1.1.4,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerExtTable,,not-accessible,,current,,The (conceptual) table listing the RADIUS authentication servers with which the client shares a secret.
.1.3.6.1.2.1.67.1.2.1.1.4.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerExtEntry,,not-accessible,radiusAuthServerExtIndex,current,,An entry (conceptual row) representing a RADIUS authentication server with which the client shares a secret.
.1.3.6.1.2.1.67.1.2.1.1.4.1.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerExtIndex,Integer32,not-accessible,,current,,A number uniquely identifying each RADIUS Authentication server with which this client communicates.
.1.3.6.1.2.1.67.1.2.1.1.4.1.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerInetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address format used for the radiusAuthServerInetAddress object.
.1.3.6.1.2.1.67.1.2.1.1.4.1.3,RADIUS-AUTH-CLIENT-MIB::radiusAuthServerInetAddress,OCTET,read-only,,current,,The IP address of the RADIUS authentication server referred to in this table entry, using the version-neutral IP address format.
.1.3.6.1.2.1.67.1.2.1.1.4.1.4,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientServerInetPortNumber,Unsigned32,read-only,,current,,The UDP port the client is using to send requests to this server. The value of zero (0) is invalid.
.1.3.6.1.2.1.67.1.2.1.1.4.1.5,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtRoundTripTime,TimeTicks,read-only,,current,,The time interval (in hundredths of a second) between the most recent Access-Reply/Access-Challenge and the Access-Request that matched it from this RADIUS authentication server.
.1.3.6.1.2.1.67.1.2.1.1.4.1.6,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtAccessRequests,Counter32,read-only,,current,,The number of RADIUS Access-Request packets sent to this server. This does not include retransmissions. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.7,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtAccessRetransmissions,Counter32,read-only,,current,,The number of RADIUS Access-Request packets retransmitted to this RADIUS authentication server. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.8,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtAccessAccepts,Counter32,read-only,,current,,The number of RADIUS Access-Accept packets (valid or invalid) received from this server. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.9,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtAccessRejects,Counter32,read-only,,current,,The number of RADIUS Access-Reject packets (valid or invalid) received from this server. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.10,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtAccessChallenges,Counter32,read-only,,current,,The number of RADIUS Access-Challenge packets (valid or invalid) received from this server. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.11,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtMalformedAccessResponses,Counter32,read-only,,current,,The number of malformed RADIUS Access-Response packets received from this server. Malformed packets include packets with an invalid length. Bad authenticators or Message Authenticator attributes or unknown types are not included as malformed access responses. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.12,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Access-Response packets containing invalid authenticators or Message Authenticator attributes received from this server. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.13,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtPendingRequests,Gauge32,read-only,,current,,The number of RADIUS Access-Request packets destined for this server that have not yet timed out or received a response. This variable is incremented when an Access-Request is sent and decremented due to receipt of an Access-Accept, Access-Reject, Access-Challenge, timeout, or retransmission.
.1.3.6.1.2.1.67.1.2.1.1.4.1.14,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtTimeouts,Counter32,read-only,,current,,The number of authentication timeouts to this server. After a timeout, the client may retry to the same server, send to a different server, or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to a different server is counted as a Request as well as a timeout. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.15,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtUnknownTypes,Counter32,read-only,,current,,The number of RADIUS packets of unknown type that were received from this server on the authentication port. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.16,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtPacketsDropped,Counter32,read-only,,current,,The number of RADIUS packets that were received from this server on the authentication port and dropped for some other reason. This counter may experience a discontinuity when the RADIUS Client module within the managed entity is reinitialized, as indicated by the current value of radiusAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.67.1.2.1.1.4.1.17,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientCounterDiscontinuity,TimeTicks,read-only,,current,,The number of centiseconds since the last discontinuity in the RADIUS Client counters. A discontinuity may be the result of a reinitialization of the RADIUS Client module within the managed entity.
.1.3.6.1.2.1.67.1.2.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIBConformance,,,,,,
.1.3.6.1.2.1.67.1.2.2.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIBCompliances,,,,,,
.1.3.6.1.2.1.67.1.2.2.1.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIBCompliance,,,,,,The compliance statement for authentication clients implementing the RADIUS Authentication Client MIB. Implementation of this module is for IPv4-only entities, or for backwards compatibility use with entities that support both IPv4 and IPv6.
.1.3.6.1.2.1.67.1.2.2.1.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtMIBCompliance,,,,,,The compliance statement for authentication clients implementing the RADIUS Authentication Client IPv6 Extensions MIB. Implementation of this module is for entities that support IPv6, or support IPv4 and IPv6.
.1.3.6.1.2.1.67.1.2.2.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIBGroups,,,,,,
.1.3.6.1.2.1.67.1.2.2.2.1,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientMIBGroup,,,,,,The basic collection of objects providing management of RADIUS Authentication Clients.
.1.3.6.1.2.1.67.1.2.2.2.2,RADIUS-AUTH-CLIENT-MIB::radiusAuthClientExtMIBGroup,,,,,,The collection of extended objects providing management of RADIUS Authentication Clients using version-neutral IP address format.
.1.3.6.1.2.1.67.2,RADIUS-ACC-CLIENT-MIB::radiusAccounting,,,,,,
.1.3.6.1.2.1.67.2.1,RADIUS-ACC-SERVER-MIB::radiusAccServMIB,,,,,,The MIB module for entities implementing the server side of the Remote Authentication Dial-In User Service (RADIUS) accounting protocol. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4671; see the RFC itself for full legal notices.
.1.3.6.1.2.1.67.2.1.1,RADIUS-ACC-SERVER-MIB::radiusAccServMIBObjects,,,,,,
.1.3.6.1.2.1.67.2.1.1.1,RADIUS-ACC-SERVER-MIB::radiusAccServ,,,,,,
.1.3.6.1.2.1.67.2.1.1.1.1,RADIUS-ACC-SERVER-MIB::radiusAccServIdent,OCTET,read-only,,current,,The implementation identification string for the RADIUS accounting server software in use on the system, for example, 'FNS-2.1'.
.1.3.6.1.2.1.67.2.1.1.1.2,RADIUS-ACC-SERVER-MIB::radiusAccServUpTime,TimeTicks,read-only,,current,,If the server has a persistent state (e.g., a process), this value will be the time elapsed (in hundredths of a second) since the server process was started. For software without persistent state, this value will be zero.
.1.3.6.1.2.1.67.2.1.1.1.3,RADIUS-ACC-SERVER-MIB::radiusAccServResetTime,TimeTicks,read-only,,current,,If the server has a persistent state (e.g., a process) and supports a 'reset' operation (e.g., can be told to re-read configuration files), this value will be the time elapsed (in hundredths of a second) since the server was 'reset.' For software that does not have persistence or does not support a 'reset' operation, this value will be zero.
.1.3.6.1.2.1.67.2.1.1.1.4,RADIUS-ACC-SERVER-MIB::radiusAccServConfigReset,INTEGER,read-write,,current,other(1):reset(2):initializing(3):running(4),Status/action object to reinitialize any persistent server state. When set to reset(2), any persistent server state (such as a process) is reinitialized as if the server had just been started. This value will never be returned by a read operation. When read, one of the following values will be returned: other(1) - server in some unknown state; initializing(3) - server (re)initializing; running(4) - server currently running.
.1.3.6.1.2.1.67.2.1.1.1.5,RADIUS-ACC-SERVER-MIB::radiusAccServTotalRequests,Counter32,read-only,,current,,The number of packets received on the accounting port.
.1.3.6.1.2.1.67.2.1.1.1.6,RADIUS-ACC-SERVER-MIB::radiusAccServTotalInvalidRequests,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets received from unknown addresses.
.1.3.6.1.2.1.67.2.1.1.1.7,RADIUS-ACC-SERVER-MIB::radiusAccServTotalDupRequests,Counter32,read-only,,current,,The number of duplicate RADIUS Accounting-Request packets received.
.1.3.6.1.2.1.67.2.1.1.1.8,RADIUS-ACC-SERVER-MIB::radiusAccServTotalResponses,Counter32,read-only,,current,,The number of RADIUS Accounting-Response packets sent.
.1.3.6.1.2.1.67.2.1.1.1.9,RADIUS-ACC-SERVER-MIB::radiusAccServTotalMalformedRequests,Counter32,read-only,,current,,The number of malformed RADIUS Accounting-Request packets received. Bad authenticators or unknown types are not included as malformed Access-Requests.
.1.3.6.1.2.1.67.2.1.1.1.10,RADIUS-ACC-SERVER-MIB::radiusAccServTotalBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets that contained an invalid authenticator.
.1.3.6.1.2.1.67.2.1.1.1.11,RADIUS-ACC-SERVER-MIB::radiusAccServTotalPacketsDropped,Counter32,read-only,,current,,The number of incoming packets silently discarded for a reason other than malformed, bad authenticators, or unknown types.
.1.3.6.1.2.1.67.2.1.1.1.12,RADIUS-ACC-SERVER-MIB::radiusAccServTotalNoRecords,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets that were received and responded to but not recorded.
.1.3.6.1.2.1.67.2.1.1.1.13,RADIUS-ACC-SERVER-MIB::radiusAccServTotalUnknownTypes,Counter32,read-only,,current,,The number of RADIUS packets of unknown type that were received.
.1.3.6.1.2.1.67.2.1.1.1.14,RADIUS-ACC-SERVER-MIB::radiusAccClientTable,,not-accessible,,deprecated,,The (conceptual) table listing the RADIUS accounting clients with which the server shares a secret.
.1.3.6.1.2.1.67.2.1.1.1.14.1,RADIUS-ACC-SERVER-MIB::radiusAccClientEntry,,not-accessible,radiusAccClientIndex,deprecated,,An entry (conceptual row) representing a RADIUS accounting client with which the server shares a secret.
.1.3.6.1.2.1.67.2.1.1.1.14.1.1,RADIUS-ACC-SERVER-MIB::radiusAccClientIndex,Integer32,not-accessible,,deprecated,,A number uniquely identifying each RADIUS accounting client with which this server communicates.
.1.3.6.1.2.1.67.2.1.1.1.14.1.2,RADIUS-ACC-SERVER-MIB::radiusAccClientAddress,IpAddress,read-only,,deprecated,,The NAS-IP-Address of the RADIUS accounting client referred to in this table entry.
.1.3.6.1.2.1.67.2.1.1.1.14.1.3,RADIUS-ACC-SERVER-MIB::radiusAccClientID,OCTET,read-only,,deprecated,,The NAS-Identifier of the RADIUS accounting client referred to in this table entry. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.67.2.1.1.1.14.1.4,RADIUS-ACC-SERVER-MIB::radiusAccServPacketsDropped,Counter32,read-only,,deprecated,,The number of incoming packets received from this client and silently discarded for a reason other than malformed, bad authenticators, or unknown types.
.1.3.6.1.2.1.67.2.1.1.1.14.1.5,RADIUS-ACC-SERVER-MIB::radiusAccServRequests,Counter32,read-only,,deprecated,,The number of packets received from this client on the accounting port.
.1.3.6.1.2.1.67.2.1.1.1.14.1.6,RADIUS-ACC-SERVER-MIB::radiusAccServDupRequests,Counter32,read-only,,deprecated,,The number of duplicate RADIUS Accounting-Request packets received from this client.
.1.3.6.1.2.1.67.2.1.1.1.14.1.7,RADIUS-ACC-SERVER-MIB::radiusAccServResponses,Counter32,read-only,,deprecated,,The number of RADIUS Accounting-Response packets sent to this client.
.1.3.6.1.2.1.67.2.1.1.1.14.1.8,RADIUS-ACC-SERVER-MIB::radiusAccServBadAuthenticators,Counter32,read-only,,deprecated,,The number of RADIUS Accounting-Request packets that contained invalid authenticators received from this client.
.1.3.6.1.2.1.67.2.1.1.1.14.1.9,RADIUS-ACC-SERVER-MIB::radiusAccServMalformedRequests,Counter32,read-only,,deprecated,,The number of malformed RADIUS Accounting-Request packets that were received from this client. Bad authenticators and unknown types are not included as malformed Accounting-Requests.
.1.3.6.1.2.1.67.2.1.1.1.14.1.10,RADIUS-ACC-SERVER-MIB::radiusAccServNoRecords,Counter32,read-only,,deprecated,,The number of RADIUS Accounting-Request packets that were received and responded to but not recorded.
.1.3.6.1.2.1.67.2.1.1.1.14.1.11,RADIUS-ACC-SERVER-MIB::radiusAccServUnknownTypes,Counter32,read-only,,deprecated,,The number of RADIUS packets of unknown type that were received from this client.
.1.3.6.1.2.1.67.2.1.1.1.15,RADIUS-ACC-SERVER-MIB::radiusAccClientExtTable,,not-accessible,,current,,The (conceptual) table listing the RADIUS accounting clients with which the server shares a secret.
.1.3.6.1.2.1.67.2.1.1.1.15.1,RADIUS-ACC-SERVER-MIB::radiusAccClientExtEntry,,not-accessible,radiusAccClientExtIndex,current,,An entry (conceptual row) representing a RADIUS accounting client with which the server shares a secret.
.1.3.6.1.2.1.67.2.1.1.1.15.1.1,RADIUS-ACC-SERVER-MIB::radiusAccClientExtIndex,Integer32,not-accessible,,current,,A number uniquely identifying each RADIUS accounting client with which this server communicates.
.1.3.6.1.2.1.67.2.1.1.1.15.1.2,RADIUS-ACC-SERVER-MIB::radiusAccClientInetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address format used for the radiusAccClientInetAddress object.
.1.3.6.1.2.1.67.2.1.1.1.15.1.3,RADIUS-ACC-SERVER-MIB::radiusAccClientInetAddress,OCTET,read-only,,current,,The IP address of the RADIUS accounting client referred to in this table entry, using the IPv6 address format.
.1.3.6.1.2.1.67.2.1.1.1.15.1.4,RADIUS-ACC-SERVER-MIB::radiusAccClientExtID,OCTET,read-only,,current,,The NAS-Identifier of the RADIUS accounting client referred to in this table entry. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.67.2.1.1.1.15.1.5,RADIUS-ACC-SERVER-MIB::radiusAccServExtPacketsDropped,Counter32,read-only,,current,,The number of incoming packets received from this client and silently discarded for a reason other than malformed, bad authenticators, or unknown types. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.6,RADIUS-ACC-SERVER-MIB::radiusAccServExtRequests,Counter32,read-only,,current,,The number of packets received from this client on the accounting port. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.7,RADIUS-ACC-SERVER-MIB::radiusAccServExtDupRequests,Counter32,read-only,,current,,The number of duplicate RADIUS Accounting-Request packets received from this client. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.8,RADIUS-ACC-SERVER-MIB::radiusAccServExtResponses,Counter32,read-only,,current,,The number of RADIUS Accounting-Response packets sent to this client. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.9,RADIUS-ACC-SERVER-MIB::radiusAccServExtBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets that contained invalid authenticators received from this client. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.10,RADIUS-ACC-SERVER-MIB::radiusAccServExtMalformedRequests,Counter32,read-only,,current,,The number of malformed RADIUS Accounting-Request packets that were received from this client. Bad authenticators and unknown types are not included as malformed Accounting-Requests. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.11,RADIUS-ACC-SERVER-MIB::radiusAccServExtNoRecords,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets that were received and responded to but not recorded. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.12,RADIUS-ACC-SERVER-MIB::radiusAccServExtUnknownTypes,Counter32,read-only,,current,,The number of RADIUS packets of unknown type that were received from this client. This counter may experience a discontinuity when the RADIUS Accounting Server module within the managed entity is reinitialized, as indicated by the current value of radiusAccServerCounterDiscontinuity.
.1.3.6.1.2.1.67.2.1.1.1.15.1.13,RADIUS-ACC-SERVER-MIB::radiusAccServerCounterDiscontinuity,TimeTicks,read-only,,current,,The number of centiseconds since the last discontinuity in the RADIUS Accounting Server counters. A discontinuity may be the result of a reinitialization of the RADIUS Accounting Server module within the managed entity.
.1.3.6.1.2.1.67.2.1.2,RADIUS-ACC-SERVER-MIB::radiusAccServMIBConformance,,,,,,
.1.3.6.1.2.1.67.2.1.2.1,RADIUS-ACC-SERVER-MIB::radiusAccServMIBCompliances,,,,,,
.1.3.6.1.2.1.67.2.1.2.1.1,RADIUS-ACC-SERVER-MIB::radiusAccServMIBCompliance,,,,,,The compliance statement for accounting servers implementing the RADIUS Accounting Server MIB. Implementation of this module is for IPv4-only entities, or for backwards compatibility use with entities that support both IPv4 and IPv6.
.1.3.6.1.2.1.67.2.1.2.1.2,RADIUS-ACC-SERVER-MIB::radiusAccServExtMIBCompliance,,,,,,The compliance statement for accounting servers implementing the RADIUS Accounting Server IPv6 Extensions MIB. Implementation of this module is for entities that support IPv6, or support IPv4 and IPv6.
.1.3.6.1.2.1.67.2.1.2.2,RADIUS-ACC-SERVER-MIB::radiusAccServMIBGroups,,,,,,
.1.3.6.1.2.1.67.2.1.2.2.1,RADIUS-ACC-SERVER-MIB::radiusAccServMIBGroup,,,,,,The collection of objects providing management of a RADIUS Accounting Server.
.1.3.6.1.2.1.67.2.1.2.2.2,RADIUS-ACC-SERVER-MIB::radiusAccServExtMIBGroup,,,,,,The collection of objects providing management of a RADIUS Accounting Server.
.1.3.6.1.2.1.67.2.2,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIB,,,,,,The MIB module for entities implementing the client side of the Remote Authentication Dial-In User Service (RADIUS) accounting protocol. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4670; see the RFC itself for full legal notices.
.1.3.6.1.2.1.67.2.2.1,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIBObjects,,,,,,
.1.3.6.1.2.1.67.2.2.1.1,RADIUS-ACC-CLIENT-MIB::radiusAccClient,,,,,,
.1.3.6.1.2.1.67.2.2.1.1.1,RADIUS-ACC-CLIENT-MIB::radiusAccClientInvalidServerAddresses,Counter32,read-only,,current,,The number of RADIUS Accounting-Response packets received from unknown addresses.
.1.3.6.1.2.1.67.2.2.1.1.2,RADIUS-ACC-CLIENT-MIB::radiusAccClientIdentifier,OCTET,read-only,,current,,The NAS-Identifier of the RADIUS accounting client. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.67.2.2.1.1.3,RADIUS-ACC-CLIENT-MIB::radiusAccServerTable,,not-accessible,,deprecated,,The (conceptual) table listing the RADIUS accounting servers with which the client shares a secret.
.1.3.6.1.2.1.67.2.2.1.1.3.1,RADIUS-ACC-CLIENT-MIB::radiusAccServerEntry,,not-accessible,radiusAccServerIndex,deprecated,,An entry (conceptual row) representing a RADIUS accounting server with which the client shares a secret.
.1.3.6.1.2.1.67.2.2.1.1.3.1.1,RADIUS-ACC-CLIENT-MIB::radiusAccServerIndex,Integer32,not-accessible,,deprecated,,A number uniquely identifying each RADIUS Accounting server with which this client communicates.
.1.3.6.1.2.1.67.2.2.1.1.3.1.2,RADIUS-ACC-CLIENT-MIB::radiusAccServerAddress,IpAddress,read-only,,deprecated,,The IP address of the RADIUS accounting server referred to in this table entry.
.1.3.6.1.2.1.67.2.2.1.1.3.1.3,RADIUS-ACC-CLIENT-MIB::radiusAccClientServerPortNumber,Integer32,read-only,,deprecated,,The UDP port the client is using to send requests to this server.
.1.3.6.1.2.1.67.2.2.1.1.3.1.4,RADIUS-ACC-CLIENT-MIB::radiusAccClientRoundTripTime,TimeTicks,read-only,,deprecated,,The time interval between the most recent Accounting-Response and the Accounting-Request that matched it from this RADIUS accounting server.
.1.3.6.1.2.1.67.2.2.1.1.3.1.5,RADIUS-ACC-CLIENT-MIB::radiusAccClientRequests,Counter32,read-only,,deprecated,,The number of RADIUS Accounting-Request packets sent. This does not include retransmissions.
.1.3.6.1.2.1.67.2.2.1.1.3.1.6,RADIUS-ACC-CLIENT-MIB::radiusAccClientRetransmissions,Counter32,read-only,,deprecated,,The number of RADIUS Accounting-Request packets retransmitted to this RADIUS accounting server. Retransmissions include retries where the Identifier and Acct-Delay have been updated, as well as those in which they remain the same.
.1.3.6.1.2.1.67.2.2.1.1.3.1.7,RADIUS-ACC-CLIENT-MIB::radiusAccClientResponses,Counter32,read-only,,deprecated,,The number of RADIUS packets received on the accounting port from this server.
.1.3.6.1.2.1.67.2.2.1.1.3.1.8,RADIUS-ACC-CLIENT-MIB::radiusAccClientMalformedResponses,Counter32,read-only,,deprecated,,The number of malformed RADIUS Accounting-Response packets received from this server. Malformed packets include packets with an invalid length. Bad authenticators and unknown types are not included as malformed accounting responses.
.1.3.6.1.2.1.67.2.2.1.1.3.1.9,RADIUS-ACC-CLIENT-MIB::radiusAccClientBadAuthenticators,Counter32,read-only,,deprecated,,The number of RADIUS Accounting-Response packets that contained invalid authenticators received from this server.
.1.3.6.1.2.1.67.2.2.1.1.3.1.10,RADIUS-ACC-CLIENT-MIB::radiusAccClientPendingRequests,Gauge32,read-only,,deprecated,,The number of RADIUS Accounting-Request packets sent to this server that have not yet timed out or received a response. This variable is incremented when an Accounting-Request is sent and decremented due to receipt of an Accounting-Response, a timeout, or a retransmission.
.1.3.6.1.2.1.67.2.2.1.1.3.1.11,RADIUS-ACC-CLIENT-MIB::radiusAccClientTimeouts,Counter32,read-only,,deprecated,,The number of accounting timeouts to this server. After a timeout, the client may retry to the same server, send to a different server, or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to a different server is counted as an Accounting-Request as well as a timeout.
.1.3.6.1.2.1.67.2.2.1.1.3.1.12,RADIUS-ACC-CLIENT-MIB::radiusAccClientUnknownTypes,Counter32,read-only,,deprecated,,The number of RADIUS packets of unknown type that were received from this server on the accounting port.
.1.3.6.1.2.1.67.2.2.1.1.3.1.13,RADIUS-ACC-CLIENT-MIB::radiusAccClientPacketsDropped,Counter32,read-only,,deprecated,,The number of RADIUS packets that were received from this server on the accounting port and dropped for some other reason.
.1.3.6.1.2.1.67.2.2.1.1.4,RADIUS-ACC-CLIENT-MIB::radiusAccServerExtTable,,not-accessible,,current,,The (conceptual) table listing the RADIUS accounting servers with which the client shares a secret.
.1.3.6.1.2.1.67.2.2.1.1.4.1,RADIUS-ACC-CLIENT-MIB::radiusAccServerExtEntry,,not-accessible,radiusAccServerExtIndex,current,,An entry (conceptual row) representing a RADIUS accounting server with which the client shares a secret.
.1.3.6.1.2.1.67.2.2.1.1.4.1.1,RADIUS-ACC-CLIENT-MIB::radiusAccServerExtIndex,Integer32,not-accessible,,current,,A number uniquely identifying each RADIUS Accounting server with which this client communicates.
.1.3.6.1.2.1.67.2.2.1.1.4.1.2,RADIUS-ACC-CLIENT-MIB::radiusAccServerInetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address format used for the radiusAccServerInetAddress object.
.1.3.6.1.2.1.67.2.2.1.1.4.1.3,RADIUS-ACC-CLIENT-MIB::radiusAccServerInetAddress,OCTET,read-only,,current,,The IP address of the RADIUS accounting server referred to in this table entry, using the version-neutral IP address format.
.1.3.6.1.2.1.67.2.2.1.1.4.1.4,RADIUS-ACC-CLIENT-MIB::radiusAccClientServerInetPortNumber,Unsigned32,read-only,,current,,The UDP port the client is using to send requests to this accounting server. The value zero (0) is invalid.
.1.3.6.1.2.1.67.2.2.1.1.4.1.5,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtRoundTripTime,TimeTicks,read-only,,current,,The time interval between the most recent Accounting-Response and the Accounting-Request that matched it from this RADIUS accounting server.
.1.3.6.1.2.1.67.2.2.1.1.4.1.6,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtRequests,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets sent. This does not include retransmissions. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.7,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtRetransmissions,Counter32,read-only,,current,,The number of RADIUS Accounting-Request packets retransmitted to this RADIUS accounting server. Retransmissions include retries where the Identifier and Acct-Delay have been updated, as well as those in which they remain the same. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.8,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtResponses,Counter32,read-only,,current,,The number of RADIUS packets received on the accounting port from this server. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.9,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtMalformedResponses,Counter32,read-only,,current,,The number of malformed RADIUS Accounting-Response packets received from this server. Malformed packets include packets with an invalid length. Bad authenticators and unknown types are not included as malformed accounting responses. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.10,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Accounting-Response packets that contained invalid authenticators received from this server. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.11,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtPendingRequests,Gauge32,read-only,,current,,The number of RADIUS Accounting-Request packets sent to this server that have not yet timed out or received a response. This variable is incremented when an Accounting-Request is sent and decremented due to receipt of an Accounting-Response, a timeout, or a retransmission. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.12,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtTimeouts,Counter32,read-only,,current,,The number of accounting timeouts to this server. After a timeout, the client may retry to the same server, send to a different server, or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to a different server is counted as an Accounting-Request as well as a timeout. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.13,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtUnknownTypes,Counter32,read-only,,current,,The number of RADIUS packets of unknown type that were received from this server on the accounting port. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.14,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtPacketsDropped,Counter32,read-only,,current,,The number of RADIUS packets that were received from this server on the accounting port and dropped for some other reason. This counter may experience a discontinuity when the RADIUS Accounting Client module within the managed entity is reinitialized, as indicated by the current value of radiusAccClientCounterDiscontinuity.
.1.3.6.1.2.1.67.2.2.1.1.4.1.15,RADIUS-ACC-CLIENT-MIB::radiusAccClientCounterDiscontinuity,TimeTicks,read-only,,current,,The number of centiseconds since the last discontinuity in the RADIUS Accounting Client counters. A discontinuity may be the result of a reinitialization of the RADIUS Accounting Client module within the managed entity.
.1.3.6.1.2.1.67.2.2.2,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIBConformance,,,,,,
.1.3.6.1.2.1.67.2.2.2.1,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIBCompliances,,,,,,
.1.3.6.1.2.1.67.2.2.2.1.1,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIBCompliance,,,,,,The compliance statement for accounting clients implementing the RADIUS Accounting Client MIB. Implementation of this module is for IPv4-only entities, or for backwards compatibility use with entities that support both IPv4 and IPv6.
.1.3.6.1.2.1.67.2.2.2.1.2,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtMIBCompliance,,,,,,The compliance statement for accounting clients implementing the RADIUS Accounting Client IPv6 Extensions MIB. Implementation of this module is for entities that support IPv6, or support IPv4 and IPv6.
.1.3.6.1.2.1.67.2.2.2.2,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIBGroups,,,,,,
.1.3.6.1.2.1.67.2.2.2.2.1,RADIUS-ACC-CLIENT-MIB::radiusAccClientMIBGroup,,,,,,The basic collection of objects providing management of RADIUS Accounting Clients.
.1.3.6.1.2.1.67.2.2.2.2.2,RADIUS-ACC-CLIENT-MIB::radiusAccClientExtMIBGroup,,,,,,The basic collection of objects providing management of RADIUS Accounting Clients.
.1.3.6.1.2.1.68,VRRP-MIB::vrrpMIB,,,,,,This MIB describes objects used for managing Virtual  Router Redundancy Protocol (VRRP) over IPv4 and IPv6  protocols.  This MIB supports VRRP for IPv4 and IPv6 protocols  simultaneously running on a given interface of a  router.   Copyright (C) The IETF Trust (2006).
.1.3.6.1.2.1.68.0,VRRP-MIB::vrrpNotifications,,,,,,
.1.3.6.1.2.1.68.0.1,VRRP-MIB::vrrpTrapNewMaster,,,,,,The newMaster trap indicates that the sending agent  has transitioned to 'Master' state.
.1.3.6.1.2.1.68.0.2,VRRP-MIB::vrrpTrapAuthFailure,,,,,,A vrrpAuthFailure trap signifies that a packet has  been received from a router whose authentication key  or authentication type conflicts with this router's  authentication key or authentication type. Implementation  of this trap is optional.  This object is deprecated in the IP Version MIB. 
.1.3.6.1.2.1.68.0.3,VRRP-MIB::vrrpTrapProtoError,,,,,,The error trap indicates that the sending agent has  encountered the protocol error indicated by  vrrpTrapProtoErrorReason.
.1.3.6.1.2.1.68.1,VRRP-MIB::vrrpOperations,,,,,,
.1.3.6.1.2.1.68.1.1,VRRP-MIB::vrrpNodeVersion,Integer32,read-only,,deprecated,,This value identifies the particular version of the VRRP  supported by this node.  This object is deprecated in the IP Version Independent  MIB.
.1.3.6.1.2.1.68.1.2,VRRP-MIB::vrrpNotificationCntl,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the VRRP-enabled router will generate  SNMP notifications for events defined in this MIB.  'Enabled' results in SNMP notifications; 'disabled', no  notifications are sent.
.1.3.6.1.2.1.68.1.3,VRRP-MIB::vrrpOperTable,,not-accessible,,deprecated,,Operations table for a VRRP router which consists of a  sequence (i.e., one or more conceptual rows) of  'vrrpOperEntry' items.  This table has been deprecated as a new IP version  neutral 'vrrpOperationsTable' has been added. 
.1.3.6.1.2.1.68.1.3.1,VRRP-MIB::vrrpOperEntry,,not-accessible,ifIndex:vrrpOperVrId,deprecated,,An entry in the vrrpOperTable containing the operational  characteristics of a virtual router. On a VRRP router,  a given virtual router is identified by a combination  of the IF index and VRID.  Rows in the table cannot be modified unless the value  of `vrrpOperAdminState' is `disabled' and the  `vrrpOperState' has transitioned to `initialize'.  This object is deprecated in favor of the IP Version  independent object, vrrpOperationsEntry
.1.3.6.1.2.1.68.1.3.1.1,VRRP-MIB::vrrpOperVrId,Integer32,not-accessible,,deprecated,,This object contains the Virtual Router Identifier  (VRID).  This object is deprecated in favor of the IP Version  independent object, vrrpOperationsVrId 
.1.3.6.1.2.1.68.1.3.1.2,VRRP-MIB::vrrpOperVirtualMacAddr,OCTET,read-only,,deprecated,,The virtual MAC address of the virtual router. Although  this object can be derived from the 'vrrpOperVrId' object,  it is defined so that it is easily obtainable by a  management application and can be included in VRRP-related  SNMP traps.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsVirtualMacAddr.
.1.3.6.1.2.1.68.1.3.1.3,VRRP-MIB::vrrpOperState,INTEGER,read-only,,deprecated,initialize(1):backup(2):master(3),The current state of the virtual router. This object has  three defined values:  - `initialize', which indicates that all the  virtual router is waiting for a startup event.  - `backup', which indicates the virtual router is  monitoring the availability of the master router.  - `master', which indicates that the virtual router  is forwarding packets for IP addresses that are  associated with this router.  Setting the `vrrpOperAdminState' object (below) initiates  transitions in the value of this object.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsState.
.1.3.6.1.2.1.68.1.3.1.4,VRRP-MIB::vrrpOperAdminState,INTEGER,read-create,,deprecated,up(1):down(2),This object will enable/disable the virtual router  function.   Setting the value to `up', will transition the state of  the virtual router from `initialize' to `backup' or  `master', depending on the value of `vrrpOperPriority'.   Setting the value to `down', will transition the router  from `master' or `backup' to `initialize'. State  transitions may not be immediate; they sometimes depend on  other factors, such as the interface (IF) state.   The `vrrpOperAdminState' object must be set to `down' prior  to modifying the other read-create objects in the  conceptual row. The value of the `vrrpOperRowStatus'  object (below) must be `active', signifying that the  conceptual row is valid (i.e., the objects are correctly  set), in order for this object to be set to `up'.   This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsState.
.1.3.6.1.2.1.68.1.3.1.5,VRRP-MIB::vrrpOperPriority,Integer32,read-create,,deprecated,,This object specifies the priority to be used for the  virtual router master election process. Higher values  imply higher priority.  A priority of '0', although not settable, is sent by  the master router to indicate that this router has ceased  to participate in VRRP and a backup virtual router should  transition to become a new master.  A priority of 255 is used for the router that owns the  associated IP address(es).  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsPriority.
.1.3.6.1.2.1.68.1.3.1.6,VRRP-MIB::vrrpOperIpAddrCount,Integer32,read-only,,deprecated,,The number of IP addresses that are associated with this  virtual router. This number is equal to the number of  rows in the vrrpAssoIpAddrTable that correspond to a  given IF index/VRID pair.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsAddrCount.
.1.3.6.1.2.1.68.1.3.1.7,VRRP-MIB::vrrpOperMasterIpAddr,IpAddress,read-only,,deprecated,,The master router's real (primary) IP address. This is  the IP address listed as the source in VRRP advertisement  last received by this virtual router.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsMasterIpAddr.
.1.3.6.1.2.1.68.1.3.1.8,VRRP-MIB::vrrpOperPrimaryIpAddr,IpAddress,read-create,,deprecated,,In the case where there is more than one IP address for  a given `ifIndex', this object is used to specify the IP  address that will become the `vrrpOperMasterIpAddr',  should the virtual router transition from backup to  master. If this object is set to 0.0.0.0, the IP address  which is numerically lowest (of all the associated IP  address for the interface) will be selected.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsPrimaryIpAddr.
.1.3.6.1.2.1.68.1.3.1.9,VRRP-MIB::vrrpOperAuthType,INTEGER,read-create,,deprecated,noAuthentication(1):simpleTextPassword(2):ipAuthenticationHeader(3),Authentication type used for VRRP protocol exchanges  between virtual routers. This value of this object is the  same for a given ifIndex.  New enumerations to this list can only be added via a new  RFC on the standards track.  This object is deprecated in the IP Version MIB.
.1.3.6.1.2.1.68.1.3.1.10,VRRP-MIB::vrrpOperAuthKey,OCTET,read-create,,deprecated,,The Authentication Key. This object is set according to  the value of the 'vrrpOperAuthType' object  ('simpleTextPassword' or 'ipAuthenticationHeader'). If  the length of the value is less than 16 octets, the agent  will left adjust and zero fill to 16 octets. The value of  this object is the same for a given ifIndex.  When read, vrrpOperAuthKey always returns an Octet String  of length zero.  This object is deprecated in the IP Version MIB.
.1.3.6.1.2.1.68.1.3.1.11,VRRP-MIB::vrrpOperAdvertisementInterval,Integer32,read-create,,deprecated,,The time interval, in seconds, between sending  advertisement messages. Only the master router sends  VRRP advertisements.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsAdvInterval. 
.1.3.6.1.2.1.68.1.3.1.12,VRRP-MIB::vrrpOperPreemptMode,INTEGER,read-create,,deprecated,true(1):false(2),Controls whether a higher priority virtual router will  preempt a lower priority master.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsPreemptMode. 
.1.3.6.1.2.1.68.1.3.1.13,VRRP-MIB::vrrpOperVirtualRouterUpTime,TimeTicks,read-only,,deprecated,,This is the value of the `sysUpTime' object when this  virtual router (i.e., the `vrrpOperState') transitioned  out of `initialized'.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsUpTime.
.1.3.6.1.2.1.68.1.3.1.14,VRRP-MIB::vrrpOperProtocol,INTEGER,read-create,,deprecated,ip(1):bridge(2):decnet(3):other(4),The particular protocol being controlled by this Virtual  Router.  New enumerations to this list can only be added via a new  RFC on the standards track.  This object is deprecated in the IP Version Independent  MIB.
.1.3.6.1.2.1.68.1.3.1.15,VRRP-MIB::vrrpOperRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The RowStatus variable, used in accordance to  installation and removal conventions for conceptual rows.  The RowStatus of a currently active row in the  vrrpOperTable is constrained by the operational state of  the corresponding virtual router.  When `vrrpOperRowStatus' is set to active(1), no other  objects in the conceptual row, with the exception of  `vrrpOperAdminState', can be modified. Prior to setting  the `vrrpOperRowStatus' object from `active' to a  different value, the `vrrpOperAdminState' object must be  set to `down' and the `vrrpOperState' object be  transitioned to `initialize'.  To create a row in this table, a manager sets this object  to either createAndGo(4) or createAndWait(5). Until  instances of all corresponding columns are appropriately  configured, the value of the corresponding instance of the  `vrrpOperRowStatus' column will be read as notReady(3).  In particular, a newly created row cannot be made  active(1) until (minimally) the corresponding instance of  `vrrpOperVrId' has been set and there is at least one  active row in the `vrrpAssoIpAddrTable' defining an  associated IP address for the virtual router.  This object is deprecated in favor of the IP Version  Independent object, vrrpOperationsRowStatus. 
.1.3.6.1.2.1.68.1.4,VRRP-MIB::vrrpAssoIpAddrTable,,not-accessible,,deprecated,,The table of addresses associated with this virtual  router.  This object is deprecated in favor of the IP Version  Independent object, vrrpAssociatedIpAddrTable. 
.1.3.6.1.2.1.68.1.4.1,VRRP-MIB::vrrpAssoIpAddrEntry,,not-accessible,ifIndex:vrrpOperVrId:vrrpAssoIpAddr,deprecated,,An entry in the table contains an IP address that is  associated with a virtual router. The number of rows for  a given ifIndex and VrId will equal the number of IP  addresses associated (e.g., backed up) by the virtual  router (equivalent to 'vrrpOperIpAddrCount').  Rows in the table cannot be modified unless the value  of `vrrpOperAdminState' is `disabled' and the  `vrrpOperState' has transitioned to `initialize'.  This object is deprecated in favor of the IP Version  Independent object, vrrpAssociatedIpAddrEntry.
.1.3.6.1.2.1.68.1.4.1.1,VRRP-MIB::vrrpAssoIpAddr,IpAddress,not-accessible,,deprecated,,The assigned IP addresses that a virtual router is  responsible for backing up.  This object is deprecated in favor of the IP Version  Independent object, vrrpAssociatedIpAddr.
.1.3.6.1.2.1.68.1.4.1.2,VRRP-MIB::vrrpAssoIpAddrRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to installation  and removal conventions for conceptual rows. Setting this  object to active(1) or createAndGo(4) results in the  addition of an associated address for a virtual router.  Destroying the entry or setting it to notInService(2)  removes the associated address from the virtual router.  The use of other values is implementation-dependent.  This object is deprecated in favor of the IP Version  Independent object, vrrpAssociatedIpAddrRowStatus.
.1.3.6.1.2.1.68.1.5,VRRP-MIB::vrrpTrapPacketSrc,IpAddress,accessible-for-notify,,deprecated,,The IP address of an inbound VRRP packet. Used by  vrrpTrapAuthFailure trap.  This object is deprecated in the IP Version MIB. 
.1.3.6.1.2.1.68.1.6,VRRP-MIB::vrrpTrapAuthErrorType,INTEGER,accessible-for-notify,,deprecated,invalidAuthType(1):authTypeMismatch(2):authFailure(3),Potential types of configuration conflicts.  Used by vrrpAuthFailure trap.  This object is deprecated in the IP Version MIB. 
.1.3.6.1.2.1.68.1.7,VRRP-MIB::vrrpOperationsTable,,not-accessible,,current,,Unified Operations table for a VRRP router which  consists of a sequence (i.e., one or more conceptual  rows) of 'vrrpOperationsEntry' items which describe  the operational characteristics of a virtual router.
.1.3.6.1.2.1.68.1.7.1,VRRP-MIB::vrrpOperationsEntry,,not-accessible,vrrpOperationsInetAddrType:vrrpOperationsVrId:ifIndex,current,,An entry in the vrrpOperationsTable containing the  operational characteristics of a virtual router. On a  VRRP router, a given virtual router is identified by a  combination of the IP version, VRID and ifIndex.  ifIndex represents a physical interface of the router.   Note that rows in this table can be distinguished on a  multi-stacked device running VRRP over IPv4 and  IPv6 on the same physical interface.   Rows in the table cannot be modified unless the value  of 'vrrpOperationsState' has transitioned to  'initialize'
.1.3.6.1.2.1.68.1.7.1.1,VRRP-MIB::vrrpOperationsInetAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The IP address type of VrrpOperationsEntry. This value  applies to both vrrpOperationsMasterIpAddr and  vrrpOperationsPrimaryIpAddr.
.1.3.6.1.2.1.68.1.7.1.2,VRRP-MIB::vrrpOperationsVrId,Integer32,not-accessible,,current,,This object contains the Virtual Router Identifier  (VRID).
.1.3.6.1.2.1.68.1.7.1.3,VRRP-MIB::vrrpOperationsVirtualMacAddr,OCTET,read-only,,current,,The virtual MAC address of the virtual router.  Although this object can be derived from the  'vrrpOperationsVrId' object, it is defined so that it  is easily obtainable by a management application and  can be included in VRRP-related SNMP notifications.
.1.3.6.1.2.1.68.1.7.1.4,VRRP-MIB::vrrpOperationsState,INTEGER,read-only,,current,initialize(1):backup(2):master(3),The current state of the virtual router. This object  has three defined values:   - `initialize', which indicates that the  virtual router is waiting for a startup event.   - `backup', which indicates the virtual router is  monitoring the availability of the master router.   - `master', which indicates that the virtual router  is forwarding packets for IP addresses that are  associated with this router.
.1.3.6.1.2.1.68.1.7.1.5,VRRP-MIB::vrrpOperationsPriority,Unsigned32,read-create,,current,,This object specifies the priority to be used for the  virtual router master election process. Higher values  imply higher priority.   A priority of '0', although not settable, is sent by  the master router to indicate that this router has  ceased to participate in VRRP and a backup virtual  router should transition to become a new master.   A priority of 255 is used for the router that owns the  associated IP address(es) for VRRP over IPv4 and hence  not settable.  A 'badValue(3)' should be returned when a user tries to  set 0 or 255 for this object. 
.1.3.6.1.2.1.68.1.7.1.6,VRRP-MIB::vrrpOperationsAddrCount,Integer32,read-only,,current,,The number of IP addresses that are associated with  this virtual router. This number is equal to the  number of rows in the vrrpAssociatedAddrTable that  correspond to a given IP version/VRID/ifIndex.
.1.3.6.1.2.1.68.1.7.1.7,VRRP-MIB::vrrpOperationsMasterIpAddr,OCTET,read-only,,current,,The master router's real IP address. Master router  would set this address to vrrpOperationsPrimaryIpAddr  while transitioning to master state. For backup  routers, this is the IP address listed as the source in  VRRP advertisement last received by this virtual  router.
.1.3.6.1.2.1.68.1.7.1.8,VRRP-MIB::vrrpOperationsPrimaryIpAddr,OCTET,read-create,,current,,In the case where there are more than one IP  Address (associated IP addresses) for a given  `ifIndex', this object is used to specify the IP  address that will become the  vrrpOperationsMasterIpAddr', should the virtual router  transition from backup state to master.
.1.3.6.1.2.1.68.1.7.1.9,VRRP-MIB::vrrpOperationsAdvInterval,INTEGER,read-create,,current,,The time interval, in centiseconds, between sending  advertisement messages. Only the master router sends  VRRP advertisements.
.1.3.6.1.2.1.68.1.7.1.10,VRRP-MIB::vrrpOperationsPreemptMode,INTEGER,read-create,,current,true(1):false(2),Controls whether a higher priority virtual router will  preempt a lower priority master.
.1.3.6.1.2.1.68.1.7.1.11,VRRP-MIB::vrrpOperationsAcceptMode,INTEGER,read-create,,current,true(1):false(2),Controls whether a virtual router in Master state  will accept packets addressed to the address owner's  IPv6 address as its own if it is not the IPv6 address  owner. Default is False.  This object is not relevant for rows representing VRRP  over IPv4 and should be set to false.
.1.3.6.1.2.1.68.1.7.1.12,VRRP-MIB::vrrpOperationsUpTime,TimeTicks,read-only,,current,,This is the value of the `sysUpTime' object when this  virtual router (i.e., the `vrrpOperationsState')  transitioned out of `initialized'.
.1.3.6.1.2.1.68.1.7.1.13,VRRP-MIB::vrrpOperationsStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Write access  is not required. It is optional to support nonVolatile  StorageType enumeration.
.1.3.6.1.2.1.68.1.7.1.14,VRRP-MIB::vrrpOperationsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The RowStatus variable should be used in accordance to  installation and removal conventions for conceptual  rows. When `vrrpOperationsRowStatus' is set to  active(1), no other objects in the conceptual row can  be modified.   To create a row in this table, a manager sets this  object to either createAndGo(4) or createAndWait(5).  Until instances of all corresponding columns are  appropriately configured, the value of the  corresponding instance of the `vrrpOperationsRowStatus'  column will be read as notReady(3).  In particular, a newly created row cannot be made  active(1) until (minimally) the corresponding instance  of vrrpOperationsInetAddrType, vrrpOperationsVrId and  vrrpOperationsPrimaryIpAddr has been set and there is  at least one active row in the  `vrrpAssociatedIpAddrTable' defining an associated  IP address.  notInService(2) should be used to administratively  bring the row down.  A typical order of operation to add a row is:  1. Create a row in vrrpOperationsTable with  createAndWait(5).  2. Create one or more corresponding rows in  vrrpAssociatedIpAddrTable.  3. Populate the vrrpOperationsEntry.  4. set vrrpOperationsRowStatus to active(1).  A typical order of operation to delete an entry is:  1. Set vrrpOperationsRowStatus to notInService(2).  2. Set the corresponding rows in  vrrpAssociatedIpAddrTable to destroy(6) to delete the  entry.  3. set vrrpOperationsRowStatus to destroy(6) to delete  the entry.
.1.3.6.1.2.1.68.1.8,VRRP-MIB::vrrpAssociatedIpAddrTable,,not-accessible,,current,,The table of addresses associated with this virtual  router.
.1.3.6.1.2.1.68.1.8.1,VRRP-MIB::vrrpAssociatedIpAddrEntry,,not-accessible,vrrpOperationsInetAddrType:vrrpOperationsVrId:ifIndex:vrrpAssociatedIpAddr,current,,An entry in the table contains an IP address that is  associated with a virtual router. The number of rows  for a given IP version, VrID and ifIndex will equal the  number of IP addresses associated (e.g., backed up) by  the virtual router (equivalent to  'vrrpOperationsIpAddrCount').   Rows in the table cannot be modified unless the value  of `vrrpOperationsState' has transitioned to  `initialize'.
.1.3.6.1.2.1.68.1.8.1.1,VRRP-MIB::vrrpAssociatedIpAddr,OCTET,not-accessible,,current,,The assigned IP addresses that a virtual router is  responsible for backing up.  The size of this object is either 4 or 16 depending on  vrrpOperationsInetAddrType.
.1.3.6.1.2.1.68.1.8.1.2,VRRP-MIB::vrrpAssociatedStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Write access  is not required. It is optional to support nonVolatile  StorageType enumeration.
.1.3.6.1.2.1.68.1.8.1.3,VRRP-MIB::vrrpAssociatedIpAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The RowStatus variable, used according to  installation and removal conventions for conceptual  rows. To create a row in this table, a manager sets  this object to either createAndGo(4) or  createAndWait(5). Setting this object to active(1)  results in the addition of an associated address for a  virtual router. Setting this object to notInService(2)  results in administratively bringing down the row.  Destroying the entry or setting it to destroy(6)  removes the associated address from the virtual router.  The use of other values is implementation-dependent.  Only vrrpAssociatedStorageType can be modified when the  row is in active(1) state for Implementations  supporting write access to vrrpAssociatedStorageType  Implementations should not allow deletion of the last  row corresponding to an active row in  vrrpOperationsTable.  Refer to description of vrrpOperationsRowStatus for a  typical row creation and deletion scenarios.
.1.3.6.1.2.1.68.1.9,VRRP-MIB::vrrpNewMasterReason,INTEGER,read-only,,current,notmaster(0):priority(1):preempted(2):masterNoResponse(3),This indicates the reason for vrrpNewMaster trap.  Used by vrrpTrapNewMaster trap. The object can be  polled if the vrrpNewMaster trap is lost to identify  the reason for transmission. Backup router should  return notmaster(0) when pooled. 
.1.3.6.1.2.1.68.1.10,VRRP-MIB::vrrpTrapProtoErrReason,INTEGER,accessible-for-notify,,current,hopLimitError(0):versionError(1):checksumError(2):vridError(3),This indicates the reason for protocol error trap.  Used by vrrpTrapProtoError trap.
.1.3.6.1.2.1.68.2,VRRP-MIB::vrrpStatistics,,,,,,
.1.3.6.1.2.1.68.2.1,VRRP-MIB::vrrpRouterChecksumErrors,Counter32,read-only,,current,,The total number of VRRP packets received with an  invalid VRRP checksum value.
.1.3.6.1.2.1.68.2.2,VRRP-MIB::vrrpRouterVersionErrors,Counter32,read-only,,current,,The total number of VRRP packets received with an  unknown or unsupported version number.
.1.3.6.1.2.1.68.2.3,VRRP-MIB::vrrpRouterVrIdErrors,Counter32,read-only,,current,,The total number of VRRP packets received with an  invalid VRID for this virtual router.
.1.3.6.1.2.1.68.2.4,VRRP-MIB::vrrpRouterStatsTable,,not-accessible,,deprecated,,Table of virtual router statistics.  This object is deprecated in favor of the IP Version  Independent object, vrrpRouterStatisticsTable.
.1.3.6.1.2.1.68.2.4.1,VRRP-MIB::vrrpRouterStatsEntry,,not-accessible,,deprecated,,An entry in the table, containing statistics information  about a given virtual router.  This object is deprecated in favor of the IP Version  Independent object, vrrpRouterStatisticsEntry.
.1.3.6.1.2.1.68.2.4.1.1,VRRP-MIB::vrrpStatsBecomeMaster,Counter32,read-only,,deprecated,,The total number of times that this virtual router's  state has transitioned to MASTER.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsMasterTransitions.
.1.3.6.1.2.1.68.2.4.1.2,VRRP-MIB::vrrpStatsAdvertiseRcvd,Counter32,read-only,,deprecated,,The total number of VRRP advertisements received by this  virtual router.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsRcvdAdvertisements.
.1.3.6.1.2.1.68.2.4.1.3,VRRP-MIB::vrrpStatsAdvertiseIntervalErrors,Counter32,read-only,,deprecated,,The total number of VRRP advertisement packets received  for which the advertisement interval is different than the  one configured for the local virtual router.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsAdvIntervalErrors.
.1.3.6.1.2.1.68.2.4.1.4,VRRP-MIB::vrrpStatsAuthFailures,Counter32,read-only,,deprecated,,The total number of VRRP packets received that do not  pass the authentication check.  This object is deprecated in the IP Version MIB.
.1.3.6.1.2.1.68.2.4.1.5,VRRP-MIB::vrrpStatsIpTtlErrors,Counter32,read-only,,deprecated,,The total number of VRRP packets received by the virtual  router with IP TTL (Time-To-Live) not equal to 255.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsIpTtlErrors.
.1.3.6.1.2.1.68.2.4.1.6,VRRP-MIB::vrrpStatsPriorityZeroPktsRcvd,Counter32,read-only,,deprecated,,The total number of VRRP packets received by the virtual  router with a priority of '0'.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsRcvdPriZeroPackets.
.1.3.6.1.2.1.68.2.4.1.7,VRRP-MIB::vrrpStatsPriorityZeroPktsSent,Counter32,read-only,,deprecated,,The total number of VRRP packets sent by the virtual  router with a priority of '0'.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsSentPriZeroPackets. 
.1.3.6.1.2.1.68.2.4.1.8,VRRP-MIB::vrrpStatsInvalidTypePktsRcvd,Counter32,read-only,,deprecated,,The number of VRRP packets received by the virtual router  with an invalid value in the 'type' field.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsRcvdInvalidTypePkts. 
.1.3.6.1.2.1.68.2.4.1.9,VRRP-MIB::vrrpStatsAddressListErrors,Counter32,read-only,,deprecated,,The total number of packets received for which the  address list does not match the locally configured list  for the virtual router.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsAddressListErrors.
.1.3.6.1.2.1.68.2.4.1.10,VRRP-MIB::vrrpStatsInvalidAuthType,Counter32,read-only,,deprecated,,The total number of packets received with an unknown  authentication type.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsPacketLengthErrors.
.1.3.6.1.2.1.68.2.4.1.11,VRRP-MIB::vrrpStatsAuthTypeMismatch,Counter32,read-only,,deprecated,,The total number of packets received with 'Auth Type' not  equal to the locally configured authentication method  (`vrrpOperAuthType').  This object is deprecated in favor of the IP Version  Independent object,  vrrpStatisticsRcvdInvalidAuthentications.
.1.3.6.1.2.1.68.2.4.1.12,VRRP-MIB::vrrpStatsPacketLengthErrors,Counter32,read-only,,deprecated,,The total number of packets received with a packet length  less than the length of the VRRP header.  This object is deprecated in favor of the IP Version  Independent object, vrrpStatisticsPacketLengthErrors. 
.1.3.6.1.2.1.68.2.5,VRRP-MIB::vrrpRouterStatisticsTable,,not-accessible,,current,,Table of virtual router statistics.
.1.3.6.1.2.1.68.2.5.1,VRRP-MIB::vrrpRouterStatisticsEntry,,not-accessible,,current,,An entry in the table, containing statistics  information about a given virtual router.
.1.3.6.1.2.1.68.2.5.1.1,VRRP-MIB::vrrpStatisticsMasterTransitions,Counter32,read-only,,current,,The total number of times that this virtual router's  state has transitioned to MASTER.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.2,VRRP-MIB::vrrpStatisticsRcvdAdvertisements,Counter32,read-only,,current,,The total number of VRRP advertisements received by  this virtual router.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.3,VRRP-MIB::vrrpStatisticsAdvIntervalErrors,Counter32,read-only,,current,,The total number of VRRP advertisement packets  received for which the advertisement interval is  different than the one configured for the local virtual  router.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.4,VRRP-MIB::vrrpStatisticsIpTtlErrors,Counter32,read-only,,current,,The total number of VRRP packets received by the  Virtual router with IPv4 TTL (for VRRP over IPv4) or  IPv6 Hop Limit (for VRRP over IPv6) not equal to 255.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.5,VRRP-MIB::vrrpStatisticsRcvdPriZeroPackets,Counter32,read-only,,current,,The total number of VRRP packets received by the  virtual router with a priority of '0'.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.6,VRRP-MIB::vrrpStatisticsSentPriZeroPackets,Counter32,read-only,,current,,The total number of VRRP packets sent by the virtual  router with a priority of '0'.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.7,VRRP-MIB::vrrpStatisticsRcvdInvalidTypePkts,Counter32,read-only,,current,,The number of VRRP packets received by the virtual  router with an invalid value in the 'type' field.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.8,VRRP-MIB::vrrpStatisticsAddressListErrors,Counter32,read-only,,current,,The total number of packets received for which the  address list does not match the locally configured list  for the virtual router.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.9,VRRP-MIB::vrrpStatisticsPacketLengthErrors,Counter32,read-only,,current,,The total number of packets received with a packet  length less than the length of the VRRP header.   Discontinuities in the value of this counter can occur  at re-initialization of the management system, and at  other times as indicated by the value of  vrrpStatisticsDiscontinuityTime.
.1.3.6.1.2.1.68.2.5.1.10,VRRP-MIB::vrrpStatisticsRcvdInvalidAuthentications,Counter32,read-only,,current,,The total number of packets received with an unknown  authentication type.
.1.3.6.1.2.1.68.2.5.1.11,VRRP-MIB::vrrpStatisticsDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at  which any one or more of this entry's counters suffered  a discontinuity.   If no such discontinuities have occurred since the last  re-initialization of the local management subsystem,  then this object contains a zero value.
.1.3.6.1.2.1.68.2.5.1.12,VRRP-MIB::vrrpStatisticsRefreshRate,Unsigned32,read-only,,current,,The minimum reasonable polling interval for this entry.  This object provides an indication of the minimum  Amount of time required to update the counters in this  entry.
.1.3.6.1.2.1.68.3,VRRP-MIB::vrrpConformance,,,,,,
.1.3.6.1.2.1.68.3.1,VRRP-MIB::vrrpMIBCompliances,,,,,,
.1.3.6.1.2.1.68.3.1.1,VRRP-MIB::vrrpMIBCompliance,,,,,,This compliance is deprecated in favour of  vrrpModuleFullCompliance.
.1.3.6.1.2.1.68.3.1.2,VRRP-MIB::vrrpModuleFullCompliance,,,,,,The compliance statement for both VRRP for IPv4 and  VRRP for IPv6 implementations.
.1.3.6.1.2.1.68.3.1.3,VRRP-MIB::vrrpModuleReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-  create (i.e. in read-only mode), then such an  implementation can claim read-only compliance. Such a  device can then be monitored but can not be configured  with this MIB.
.1.3.6.1.2.1.68.3.2,VRRP-MIB::vrrpMIBGroups,,,,,,
.1.3.6.1.2.1.68.3.2.1,VRRP-MIB::vrrpOperGroup,,,,,,Conformance group for VRRP operations.
.1.3.6.1.2.1.68.3.2.2,VRRP-MIB::vrrpStatsGroup,,,,,,Conformance group for VRRP statistics.
.1.3.6.1.2.1.68.3.2.3,VRRP-MIB::vrrpTrapGroup,,,,,,Conformance group for objects contained in VRRP  notifications.
.1.3.6.1.2.1.68.3.2.4,VRRP-MIB::vrrpNotificationGroup,,,,,,The VRRP MIB Notification Group.
.1.3.6.1.2.1.68.3.2.5,VRRP-MIB::vrrpOperationsGroup,,,,,,Conformance group for VRRP over IPv4 and IPv6  operations.
.1.3.6.1.2.1.68.3.2.6,VRRP-MIB::vrrpStatisticsGroup,,,,,,Conformance group for VRRP over IPv4 and IPv6  statistics.
.1.3.6.1.2.1.68.3.2.7,VRRP-MIB::vrrpTrapInfoGroup,,,,,,Conformance group for objects contained in VRRP  notifications.
.1.3.6.1.2.1.68.3.2.8,VRRP-MIB::vrrpNotificationsGroup,,,,,,The VRRP MIB Notification Group.
.1.3.6.1.2.1.69,DOCS-CABLE-DEVICE-MIB::docsDev,,,,,,This is the MIB Module for DOCSIS-compliant cable modems and cable-modem termination systems. Copyright (C) The IETF Trust (2006). This version of this MIB module was published in RFC 4639; for full legal notices see the RFC itself.
.1.3.6.1.2.1.69.0,DOCS-CABLE-DEVICE-MIB::docsDevNotifications,,,,,,
.1.3.6.1.2.1.69.1,DOCS-CABLE-DEVICE-MIB::docsDevMIBObjects,,,,,,
.1.3.6.1.2.1.69.1.1,DOCS-CABLE-DEVICE-MIB::docsDevBase,,,,,,
.1.3.6.1.2.1.69.1.1.1,DOCS-CABLE-DEVICE-MIB::docsDevRole,INTEGER,read-only,,current,cm(1):cmtsActive(2):cmtsBackup(3),Defines the current role of this device. cm(1) is a Cable Modem, cmtsActive(2) is a Cable Modem Termination System that is controlling the system of cable modems, and cmtsBackup(3) is a CMTS that is currently connected but is not controlling the system (not currently used). In general, if this device is a 'cm', its role will not change during operation or between reboots. If the device is a 'cmts' it may change between cmtsActive and cmtsBackup and back again during normal operation. NB: At this time, the DOCSIS standards do not support the concept of a backup CMTS, but cmtsBackup is included for completeness.
.1.3.6.1.2.1.69.1.1.2,DOCS-CABLE-DEVICE-MIB::docsDevDateTime,OCTET,read-write,,current,,The current date and time, with time zone information (if known). If the real data and time cannot be determined, this shall represent elapsed time from boot relative to the standard epoch '1970-1-1,0:0:0.0'. In other words, if this agent has been up for 3 minutes and not been able to determine what the actual date and time are, this object will return the value '1970-1-1,0:03:0.0'.
.1.3.6.1.2.1.69.1.1.3,DOCS-CABLE-DEVICE-MIB::docsDevResetNow,INTEGER,read-write,,current,true(1):false(2),Setting this object to true(1) causes the device to reset. Reading this object always returns false(2).
.1.3.6.1.2.1.69.1.1.4,DOCS-CABLE-DEVICE-MIB::docsDevSerialNumber,OCTET,read-only,,current,,The manufacturer's serial number for this device.
.1.3.6.1.2.1.69.1.1.5,DOCS-CABLE-DEVICE-MIB::docsDevSTPControl,INTEGER,read-write,,current,stEnabled(1):noStFilterBpdu(2):noStPassBpdu(3),This object controls operation of the spanning tree protocol (as distinguished from transparent bridging). If set to stEnabled(1), then the spanning tree protocol is enabled, subject to bridging constraints. If noStFilterBpdu(2), then spanning tree is not active, and Bridge PDUs received are discarded. If noStPassBpdu(3), then spanning tree is not active, and Bridge PDUs are transparently forwarded. Note that a device need not implement all of these options, but that noStFilterBpdu(2) is required.
.1.3.6.1.2.1.69.1.1.6,DOCS-CABLE-DEVICE-MIB::docsDevIgmpModeControl,INTEGER,read-write,,current,passive(1):active(2),This object controls the IGMP mode of operation for the CM or CMTS. In passive mode, the device forwards IGMP between interfaces as based on knowledge of Multicast Session activity on the subscriber side interface and the rules defined in the DOCSIS RFI specification. In active mode, the device terminates at and initiates IGMP through its interfaces as based on the knowledge of Multicast Session activity on the subscriber side interface.
.1.3.6.1.2.1.69.1.1.7,DOCS-CABLE-DEVICE-MIB::docsDevMaxCpe,Unsigned32,read-only,,current,,The maximum number of CPEs that can be granted access through a CM during a CM epoch. This value can be obtained from the CM configuration file; however, it may be adjusted by the CM according to hardware or software limitations that have been imposed on the implementation.
.1.3.6.1.2.1.69.1.2,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessTable,,not-accessible,,deprecated,,This table controls access to SNMP objects by network management stations. If the table is empty, access to SNMP objects is unrestricted. The objects in this table MUST NOT persist across reboots. The objects in this table are only accessible from cable devices that are not capable of operating in SNMP Coexistence mode (RFC 3584) or in SNMPv3 mode (RFC 3410). See the conformance section for details. Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevNmAccess mode for backward compatibility. This table is deprecated. Instead, use the SNMP coexistence MIBs from RFC 3584, the TARGET and NOTIFICATION MIBs from RFC 3413, and the View-Based Access Control Model (VACM) MIBs for all SNMP protocol versions from RFC 3415.
.1.3.6.1.2.1.69.1.2.1,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessEntry,,not-accessible,docsDevNmAccessIndex,deprecated,,An entry describing access to SNMP objects by a particular network management station. An entry in this table is not readable unless the management station has read-write permission (either implicit if the table is empty, or explicit through an entry in this table). Entries are ordered by docsDevNmAccessIndex. The first matching entry (e.g., matching IP address and community string) is used to derive access.
.1.3.6.1.2.1.69.1.2.1.1,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessIndex,Integer32,not-accessible,,deprecated,,Index used to order the application of access entries.
.1.3.6.1.2.1.69.1.2.1.2,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessIp,IpAddress,read-create,,deprecated,,The IP address (or subnet) of the network management station. The address 0.0.0.0 is defined to mean any Network Management Station (NMS). If traps are enabled for this entry, then the value must be the address of a specific device. Implementations MAY recognize 255.255.255.255 as equivalent to 0.0.0.0.
.1.3.6.1.2.1.69.1.2.1.3,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessIpMask,IpAddress,read-create,,deprecated,,The IP subnet mask of the network management stations. If traps are enabled for this entry, then the value must be 0.0.0.0. Implementations MAY recognize 255.255.255.255 as equivalent to 0.0.0.0.
.1.3.6.1.2.1.69.1.2.1.4,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessCommunity,OCTET,read-create,,deprecated,,The community string to be matched for access by this entry. If set to a zero-length string, then any community string will match. When read, this object SHOULD return a zero-length string.
.1.3.6.1.2.1.69.1.2.1.5,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessControl,INTEGER,read-create,,deprecated,none(1):read(2):readWrite(3):roWithTraps(4):rwWithTraps(5):trapsOnly(6),Specifies the type of access allowed to this NMS. Setting this object to none(1) causes the table entry to be destroyed. Read(2) allows access by 'get' and 'get-next' PDUs. ReadWrite(3) allows access by 'set' as well. RoWithtraps(4), rwWithTraps(5), and trapsOnly(6) control distribution of Trap PDUs transmitted by this device.
.1.3.6.1.2.1.69.1.2.1.6,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessInterfaces,OCTET,read-create,,deprecated,,Specifies the set of interfaces from which requests from this NMS will be accepted. Each octet within the value of this object specifies a set of eight interfaces, the first octet specifying ports 1 through 8, the second octet specifying interfaces 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit represents the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in the set. Note that entries in this table apply only to link-layer interfaces (e.g., Ethernet and CATV MAC). Bits representing upstream and downstream channel interfaces MUST NOT be set to '1'. Note that if bits corresponding to non-existing interfaces are set, the result is implementation specific. Note that according to the DOCSIS OSSIv1.1 specification, when ifIndex '1' is included in the set, then this row applies to all CPE (customer-facing) interfaces. The size of this object is the minimum required to represent all configured interfaces for this device.
.1.3.6.1.2.1.69.1.2.1.7,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Controls and reflects the status of rows in this table. Rows in this table may be created by either the create-and-go or create-and-wait paradigm. There is no restriction on changing values in a row of this table while the row is active. The following objects MUST have valid values before this object can be set to active: docsDevNmAccessIp, docsDevNmAccessStatus, docsDevNmAccessIpMask, docsDevNmAccessCommunity, docsDevNmAccessControl, and docsDevNmAccessInterfaces.
.1.3.6.1.2.1.69.1.2.1.8,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessTrapVersion,INTEGER,read-create,,deprecated,disableSNMPv2trap(1):enableSNMPv2trap(2),Specifies the TRAP version that is sent to this NMS. Setting this object to disableSNMPv2trap (1) causes the trap in SNMPv1 format to be sent to a particular NMS. Setting this object to enableSNMPv2trap (2) causes the trap in SNMPv2 format be sent to a particular NMS.
.1.3.6.1.2.1.69.1.3,DOCS-CABLE-DEVICE-MIB::docsDevSoftware,,,,,,
.1.3.6.1.2.1.69.1.3.1,DOCS-CABLE-DEVICE-MIB::docsDevSwServer,IpAddress,read-write,,deprecated,,The address of the TFTP server used for software upgrades. If the TFTP server is unknown or is a non-IPv4 address, return 0.0.0.0. This object is deprecated. See docsDevSwServerAddress for its replacement. This object will have its value modified, given a valid SET to docsDevSwServerAddress.
.1.3.6.1.2.1.69.1.3.2,DOCS-CABLE-DEVICE-MIB::docsDevSwFilename,OCTET,read-write,,current,,The filename of the software image to be downloaded via TFTP, or the abs_path (as defined in RFC 2616) of the software image to be downloaded via HTTP. Unless set via SNMP, this is the filename or abs_path specified by the provisioning server during the boot process that corresponds to the software version that is desired for this device. If unknown, the value of this object is the zero-length string.
.1.3.6.1.2.1.69.1.3.3,DOCS-CABLE-DEVICE-MIB::docsDevSwAdminStatus,INTEGER,read-write,,current,upgradeFromMgt(1):allowProvisioningUpgrade(2):ignoreProvisioningUpgrade(3),If set to upgradeFromMgt(1), the device will initiate a TFTP or HTTP software image download. After successfully receiving an image, the device will set its state to ignoreProvisioningUpgrade(3) and reboot. If the download process is interrupted (e.g., by a reset or power failure), the device will load the previous image and, after re-initialization, continue to attempt loading the image specified in docsDevSwFilename. If set to allowProvisioningUpgrade(2), the device will use the software version information supplied by the provisioning server when next rebooting (this does not cause a reboot). When set to ignoreProvisioningUpgrade(3), the device will disregard software image upgrade information from the provisioning server. Note that reading this object can return upgradeFromMgt(1). This indicates that a software download is currently in progress, and that the device will reboot after successfully receiving an image.
.1.3.6.1.2.1.69.1.3.4,DOCS-CABLE-DEVICE-MIB::docsDevSwOperStatus,INTEGER,read-only,,current,inProgress(1):completeFromProvisioning(2):completeFromMgt(3):failed(4):other(5),InProgress(1) indicates that a TFTP or HTTP download is underway, either as a result of a version mismatch at provisioning or as a result of a upgradeFromMgt request. No other docsDevSw* objects can be modified in this state. CompleteFromProvisioning(2) indicates that the last software upgrade was a result of version mismatch at provisioning. CompleteFromMgt(3) indicates that the last software upgrade was a result of setting docsDevSwAdminStatus to upgradeFromMgt. Failed(4) indicates that the last attempted download failed, ordinarily due to TFTP or HTTP timeout.
.1.3.6.1.2.1.69.1.3.5,DOCS-CABLE-DEVICE-MIB::docsDevSwCurrentVers,OCTET,read-only,,current,,The software version currently operating in this device. This string's syntax is that used by the individual vendor to identify software versions. For a CM, this string will describe the current software load. For a CMTS, this object SHOULD contain a human-readable representation either of the vendor specific designation of the software for the chassis, or of the software for the control processor. If neither of these is applicable, the value MUST be a zero-length string.
.1.3.6.1.2.1.69.1.3.6,DOCS-CABLE-DEVICE-MIB::docsDevSwServerAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address of the TFTP or HTTP server used for software upgrades. If docsDevSwServerTransportProtocol is currently set to tftp(1), attempting to set this object to dns(16) MUST result in an error.
.1.3.6.1.2.1.69.1.3.7,DOCS-CABLE-DEVICE-MIB::docsDevSwServerAddress,OCTET,read-write,,current,,The address of the TFTP or HTTP server used for software upgrades. If the TFTP/HTTP server is unknown, return the zero- length address string (see the TextualConvention). If docsDevSwServer is also implemented in this agent, this object is tied to it. A set of this object to an IPv4 address will result in also setting the value of docsDevSwServer to that address. If this object is set to an IPv6 address, docsDevSwServer is set to 0.0.0.0. If docsDevSwServer is set, this object is also set to that value. Note that if both are set in the same action, the order of which one sets the other is undefined.
.1.3.6.1.2.1.69.1.3.8,DOCS-CABLE-DEVICE-MIB::docsDevSwServerTransportProtocol,INTEGER,read-write,,current,tftp(1):http(2),This object specifies the transport protocol (TFTP or HTTP) to be used for software upgrades. If the value of this object is tftp(1), then the cable device uses TFTP (RFC 1350) read request packets to download the docsDevSwFilename from the docsDevSwServerAddress in octet mode. If the value of this object is http(2), then the cable device uses HTTP 1.0 (RFC 1945) or HTTP 1.1 (RFC 2616) GET requests sent to host docsDevSwServerAddress to download the software image from path docsDevSwFilename. If docsDevSwServerAddressType is currently set to dns(16), attempting to set this object to tftp(1) MUST result in an error.
.1.3.6.1.2.1.69.1.4,DOCS-CABLE-DEVICE-MIB::docsDevServer,,,,,,
.1.3.6.1.2.1.69.1.4.1,DOCS-CABLE-DEVICE-MIB::docsDevServerBootState,INTEGER,read-only,,current,operational(1):disabled(2):waitingForDhcpOffer(3):waitingForDhcpResponse(4):waitingForTimeServer(5):waitingForTftp(6):refusedByCmts(7):forwardingDenied(8):other(9):unknown(10),If operational(1), the device has completed loading and processing of configuration parameters, and the CMTS has completed the Registration exchange. If disabled(2), then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3), then a Dynamic Host Configuration Protocol (DHCP) Discover has been transmitted, and no offer has yet been received. If waitingForDhcpResponse(4), then a DHCP Request has been transmitted, and no response has yet been received. If waitingForTimeServer(5), then a Time Request has been transmitted, and no response has yet been received. If waitingForTftp(6), then a request to the TFTP parameter server has been made, and no response received. If refusedByCmts(7), then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8), then the registration process was completed, but the network access option in the received configuration file prohibits forwarding. If other(9), then the registration process reached a point that does not fall into one of the above categories. If unknown(10), then the device has not yet begun the registration process or is in some other indeterminate state.
.1.3.6.1.2.1.69.1.4.2,DOCS-CABLE-DEVICE-MIB::docsDevServerDhcp,IpAddress,read-only,,deprecated,,The IP address of the DHCP server that assigned an IP address to this device. Returns 0.0.0.0 if DHCP is not used for IP address assignment, or if this agent is not assigned an IPv4 address. This object is deprecated and is replaced by docsDevServerDhcpAddress.
.1.3.6.1.2.1.69.1.4.3,DOCS-CABLE-DEVICE-MIB::docsDevServerTime,IpAddress,read-only,,deprecated,,The IP address of the Time server (RFC 0868). Returns 0.0.0.0 if the time server IP address is unknown, or if the time server is not an IPv4 server. This object is deprecated and is replaced by docsDevServerTimeAddress.
.1.3.6.1.2.1.69.1.4.4,DOCS-CABLE-DEVICE-MIB::docsDevServerTftp,IpAddress,read-only,,deprecated,,The IP address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns 0.0.0.0 if the TFTP server address is unknown or is not an IPv4 address. This object is deprecated and is replaced by docsDevServerConfigTftpAddress.
.1.3.6.1.2.1.69.1.4.5,DOCS-CABLE-DEVICE-MIB::docsDevServerConfigFile,OCTET,read-only,,current,,The name of the device configuration file read from the TFTP server. Returns a zero-length string if the configuration file name is unknown.
.1.3.6.1.2.1.69.1.4.6,DOCS-CABLE-DEVICE-MIB::docsDevServerDhcpAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address of docsDevServerDhcpAddress. If DHCP was not used, this value should return unknown(0).
.1.3.6.1.2.1.69.1.4.7,DOCS-CABLE-DEVICE-MIB::docsDevServerDhcpAddress,OCTET,read-only,,current,,The internet address of the DHCP server that assigned an IP address to this device. Returns the zero length octet string if DHCP was not used for IP address assignment.
.1.3.6.1.2.1.69.1.4.8,DOCS-CABLE-DEVICE-MIB::docsDevServerTimeAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address of docsDevServerTimeAddress. If no time server exists, this value should return unknown(0).
.1.3.6.1.2.1.69.1.4.9,DOCS-CABLE-DEVICE-MIB::docsDevServerTimeAddress,OCTET,read-only,,current,,The Internet address of the RFC 868 Time server, as provided by DHCP option 4. Note that if multiple values are provided to the CM in DHCP option 4, the value of this MIB object MUST be the Time server address from which the Time of Day reference was acquired as based on the DOCSIS RFI specification. During the period of time where the Time of Day have not been acquired, the Time server address reported by the CM may report the first address value in the DHCP option value or the last server address the CM attempted to get the Time of day value. Returns the zero-length octet string if the time server IP address is not provisioned.
.1.3.6.1.2.1.69.1.4.10,DOCS-CABLE-DEVICE-MIB::docsDevServerConfigTftpAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address of docsDevServerConfigTftpAddress. If no TFTP server exists, this value should return unknown(0).
.1.3.6.1.2.1.69.1.4.11,DOCS-CABLE-DEVICE-MIB::docsDevServerConfigTftpAddress,OCTET,read-only,,current,,The internet address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns the zero-length octet string if the config server address is unknown. There are certain security risks that are involved with using TFTP.
.1.3.6.1.2.1.69.1.5,DOCS-CABLE-DEVICE-MIB::docsDevEvent,,,,,,
.1.3.6.1.2.1.69.1.5.1,DOCS-CABLE-DEVICE-MIB::docsDevEvControl,INTEGER,read-write,,current,resetLog(1):useDefaultReporting(2),Setting this object to resetLog(1) empties the event log. All data is deleted. Setting it to useDefaultReporting(2) returns all event priorities to their factory-default reporting. Reading this object always returns useDefaultReporting(2).
.1.3.6.1.2.1.69.1.5.2,DOCS-CABLE-DEVICE-MIB::docsDevEvSyslog,IpAddress,read-write,,deprecated,,The IP address of the Syslog server. If 0.0.0.0, either syslog transmission is inhibited, or the Syslog server address is not an IPv4 address. This object is deprecated and is replaced by docsDevEvSyslogAddress.
.1.3.6.1.2.1.69.1.5.3,DOCS-CABLE-DEVICE-MIB::docsDevEvThrottleAdminStatus,INTEGER,read-write,,current,unconstrained(1):maintainBelowThreshold(2):stopAtThreshold(3):inhibited(4),Controls the transmission of traps and syslog messages with respect to the trap pacing threshold. unconstrained(1) causes traps and syslog messages to be transmitted without regard to the threshold settings. maintainBelowThreshold(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold. stopAtThreshold(3) causes trap transmission to cease at the threshold and not to resume until directed to do so. inhibited(4) causes all trap transmission and syslog messages to be suppressed. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. Writing to this object resets the thresholding state.
.1.3.6.1.2.1.69.1.5.4,DOCS-CABLE-DEVICE-MIB::docsDevEvThrottleInhibited,INTEGER,read-only,,deprecated,true(1):false(2),If true(1), trap and syslog transmission is currently inhibited due to thresholds and/or the current setting of docsDevEvThrottleAdminStatus. In addition, this is true(1) when transmission is inhibited because no syslog (docsDevEvSyslog) or trap (docsDevNmAccessEntry) destinations have been set. This object is deprecated and is replaced by docsDevEvThrottleThresholdExceeded.
.1.3.6.1.2.1.69.1.5.5,DOCS-CABLE-DEVICE-MIB::docsDevEvThrottleThreshold,Unsigned32,read-write,,current,,Number of events per docsDevEvThrottleInterval permitted before throttling is to occur. A single event, whether the notification could result in messages transmitted using syslog, SNMP, or both protocols, and regardless of the number of destinations, (including zero) is always treated as a single event for threshold counting. For example, an event causing both a trap and a syslog message is still treated as a single event. All system notifications that occur within the device should be taken into consideration when calculating and monitoring the threshold.
.1.3.6.1.2.1.69.1.5.6,DOCS-CABLE-DEVICE-MIB::docsDevEvThrottleInterval,Integer32,read-write,,current,,The interval over which docsDevEvThrottleThreshold applies.
.1.3.6.1.2.1.69.1.5.7,DOCS-CABLE-DEVICE-MIB::docsDevEvControlTable,,not-accessible,,current,,This table allows control of the reporting of event classes. For each event priority, a combination of logging and reporting mechanisms may be chosen. The mapping of event types to priorities is vendor dependent. Vendors may also choose to allow the user to control that mapping through proprietary means. Table entries MUST persist across reboots for CMTS devices and MUST NOT persist across reboots for CM devices.
.1.3.6.1.2.1.69.1.5.7.1,DOCS-CABLE-DEVICE-MIB::docsDevEvControlEntry,,not-accessible,docsDevEvPriority,current,,Allows configuration of the reporting mechanisms for a particular event priority.
.1.3.6.1.2.1.69.1.5.7.1.1,DOCS-CABLE-DEVICE-MIB::docsDevEvPriority,INTEGER,not-accessible,,current,emergency(1):alert(2):critical(3):error(4):warning(5):notice(6):information(7):debug(8),The priority level that is controlled by this entry. These are ordered from most (emergency) to least (debug) critical. Each event with a CM or CMTS has a particular priority level associated with it (as defined by the vendor). emergency(1) events indicate vendor-specific fatal hardware or software errors that prevent normal system operation. alert(2) events indicate a serious failure that causes the reporting system to reboot but is not caused by hardware or software malfunctioning. critical(3) events indicate a serious failure that requires attention and prevents the device from transmitting data but that could be recovered without rebooting the system. error(4) and warning(5) events indicate that a failure occurred that could interrupt the normal data flow but that does not cause the device to re-register. notice(6) and information(7) events indicate a milestone or checkpoint in normal operation that could be of particular importance for troubleshooting. debug(8) events are reserved for vendor-specific events. During normal operation, no event more critical than notice(6) should be generated. Events between warning and emergency should be generated at appropriate levels of problems (e.g., emergency when the box is about to crash).
.1.3.6.1.2.1.69.1.5.7.1.2,DOCS-CABLE-DEVICE-MIB::docsDevEvReporting,BITS,read-write,,current,local(0):traps(1):syslog(2):localVolatile(8):stdInterface(9),Defines the action to be taken on occurrence of this event class. Implementations may not necessarily support all options for all event classes but at minimum must allow traps and syslogging to be disabled. If the local(0) bit is set, then log to the internal log and update non-volatile store, for backward compatibility with the original RFC 2669 definition. If the traps(1) bit is set, then generate an SNMP trap; if the syslog(2) bit is set, then send a syslog message (assuming that the syslog address is set). If the localVolatile(8) bit is set, then log to the internal log without updating non-volatile store. If the stdInterface(9) bit is set, then the agent ignores all other bits except the local(0), syslog(2), and localVolatile(8) bits. Setting the stdInterface(9) bit indicates that RFC3413 and RFC3014 are being used to control event reporting mechanisms.
.1.3.6.1.2.1.69.1.5.8,DOCS-CABLE-DEVICE-MIB::docsDevEventTable,,not-accessible,,current,,Contains a log of network and device events that may be of interest in fault isolation and troubleshooting. If the local(0) bit is set in docsDevEvReporting, entries in this table MUST persist across reboots.
.1.3.6.1.2.1.69.1.5.8.1,DOCS-CABLE-DEVICE-MIB::docsDevEventEntry,,not-accessible,docsDevEvIndex,current,,Describes a network or device event that may be of interest in fault isolation and troubleshooting. Multiple sequential identical events are represented by incrementing docsDevEvCounts and setting docsDevEvLastTime to the current time rather than creating multiple rows. Entries are created with the first occurrence of an event. docsDevEvControl can be used to clear the table. Individual events cannot be deleted.
.1.3.6.1.2.1.69.1.5.8.1.1,DOCS-CABLE-DEVICE-MIB::docsDevEvIndex,Integer32,not-accessible,,current,,Provides relative ordering of the objects in the event log. This object will always increase except when (a) the log is reset via docsDevEvControl, (b) the device reboots and does not implement non-volatile storage for this log, or (c) it reaches the value 2^31. The next entry for all the above cases is 1.
.1.3.6.1.2.1.69.1.5.8.1.2,DOCS-CABLE-DEVICE-MIB::docsDevEvFirstTime,OCTET,read-only,,current,,The value of docsDevDateTime at the time this entry was created.
.1.3.6.1.2.1.69.1.5.8.1.3,DOCS-CABLE-DEVICE-MIB::docsDevEvLastTime,OCTET,read-only,,current,,When an entry reports only one event, this object will have the same value as the corresponding instance of docsDevEvFirstTime. When an entry reports multiple events, this object will record the value that docsDevDateTime had when the most recent event for this entry occurred.
.1.3.6.1.2.1.69.1.5.8.1.4,DOCS-CABLE-DEVICE-MIB::docsDevEvCounts,Counter32,read-only,,current,,The number of consecutive event instances reported by this entry. This starts at 1 with the creation of this row and increments by 1 for each subsequent duplicate event.
.1.3.6.1.2.1.69.1.5.8.1.5,DOCS-CABLE-DEVICE-MIB::docsDevEvLevel,INTEGER,read-only,,current,emergency(1):alert(2):critical(3):error(4):warning(5):notice(6):information(7):debug(8),The priority level of this event, as defined by the vendor. These are ordered from most serious (emergency) to least serious (debug). emergency(1) events indicate vendor-specific fatal hardware or software errors that prevent normal system operation. alert(2) events indicate a serious failure that causes the reporting system to reboot but that is not caused by hardware or software malfunctioning. critical(3) events indicate a serious failure that requires attention and prevents the device from transmitting data but that could be recovered without rebooting the system. error(4) and warning(5) events indicate that a failure occurred that could interrupt the normal data flow but that does not cause the device to re-register. notice(6) and information(7) events indicate a milestone or checkpoint in normal operation that could be of particular importance for troubleshooting. debug(8) events are reserved for vendor-specific events. During normal operation, no event more critical than notice(6) should be generated. Events between warning and emergency should be generated at appropriate levels of problems (e.g., emergency when the box is about to crash).
.1.3.6.1.2.1.69.1.5.8.1.6,DOCS-CABLE-DEVICE-MIB::docsDevEvId,Unsigned32,read-only,,current,,For this product, uniquely identifies the type of event that is reported by this entry.
.1.3.6.1.2.1.69.1.5.8.1.7,DOCS-CABLE-DEVICE-MIB::docsDevEvText,OCTET,read-only,,current,,Provides a human-readable description of the event, including all relevant context (interface numbers, etc.).
.1.3.6.1.2.1.69.1.5.9,DOCS-CABLE-DEVICE-MIB::docsDevEvSyslogAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address of docsDevEvSyslogAddress. If no syslog server exists, this value should return unknown(0).
.1.3.6.1.2.1.69.1.5.10,DOCS-CABLE-DEVICE-MIB::docsDevEvSyslogAddress,OCTET,read-write,,current,,The Internet address of the Syslog server, as provided by DHCP option 7 or set via SNMP management. If the address of the server is set to the zero-length string, the 0.0.0.0 IPv4 address, or the 0: IPv6 address, Syslog transmission is inhibited. Note that if multiple values are provided to the CM in DHCP option 7, the value of this MIB object MUST be the first Syslog server address received. By default at agent boot, this object returns the zero length string.
.1.3.6.1.2.1.69.1.5.11,DOCS-CABLE-DEVICE-MIB::docsDevEvThrottleThresholdExceeded,INTEGER,read-only,,current,true(1):false(2),If true(1), trap and syslog transmission is currently inhibited due to exceeding the trap/syslog event threshold in the current interval.
.1.3.6.1.2.1.69.1.6,DOCS-CABLE-DEVICE-MIB::docsDevFilter,,,,,,
.1.3.6.1.2.1.69.1.6.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCUnmatchedAction,INTEGER,read-write,,current,discard(1):accept(2),LLC (Link Level Control) filters can be defined on an inclusive or exclusive basis: CMs can be configured to forward only packets matching a set of layer three protocols, or to drop packets matching a set of layer three protocols. Typical use of these filters is to filter out possibly harmful (given the context of a large metropolitan LAN) protocols. If set to discard(1), any L2 packet that does not match at least one filter in the docsDevFilterLLCTable will be discarded. If set to accept(2), any L2 packet that does not match at least one filter in the docsDevFilterLLCTable will be accepted for further processing (e.g., bridging). In other words, if the packet does not match an entry in the table, it takes this action; if it does match an entry in the table, it takes the opposite of this action.
.1.3.6.1.2.1.69.1.6.2,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCTable,,not-accessible,,current,,A list of filters to apply to (bridged) LLC traffic. The filters in this table are applied to incoming traffic on the appropriate interface(s) prior to any further processing (e.g., before the packet is handed off for level 3 processing, or for bridging). The specific action taken when no filter is matched is controlled by docsDevFilterLLCUnmatchedAction. Table entries MUST NOT persist across reboots for any device.
.1.3.6.1.2.1.69.1.6.2.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCEntry,,not-accessible,docsDevFilterLLCIndex,current,,Describes a single filter to apply to (bridged) LLC traffic received on a specified interface. 
.1.3.6.1.2.1.69.1.6.2.1.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCIndex,Integer32,not-accessible,,current,,Index used for the identification of filters (note that LLC filter order is irrelevant).
.1.3.6.1.2.1.69.1.6.2.1.2,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Controls and reflects the status of rows in this table. There is no restriction on changing any of the associated columns for this row while this object is set to active. Specifying only this object (with the appropriate index) on a CM is sufficient to create a filter row that matches all inbound packets on the ethernet interface and results in the packets being discarded. docsDevFilterLLCIfIndex (at least) must be specified on a CMTS to create a row.
.1.3.6.1.2.1.69.1.6.2.1.3,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCIfIndex,Integer32,read-create,,current,,The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another network interface. If the value is zero, the filter applies to all interfaces. In Cable Modems, the default value is the customer side interface(s). In CMTSs, this object has to be specified to create a row in this table. Note that according to the DOCSIS OSSIv1.1 specification, ifIndex '1' in the CM means that this row applies to all Cable Modem-to-CPE Interfaces (CMCI).
.1.3.6.1.2.1.69.1.6.2.1.4,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCProtocolType,INTEGER,read-create,,current,ethertype(1):dsap(2),The format of the value in docsDevFilterLLCProtocol: either a two-byte Ethernet Ethertype, or a one-byte 802.2 Service Access Point (SAP) value. ethertype(1) also applies to Standard Network Access Protocol (SNAP) encapsulated frames.
.1.3.6.1.2.1.69.1.6.2.1.5,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCProtocol,Integer32,read-create,,current,,The layer-three protocol for which this filter applies. The protocol value format depends on docsDevFilterLLCProtocolType. Note that for SNAP frames, ethertype filtering is performed rather than Destination Service Access Point (DSAP) =0xAA.
.1.3.6.1.2.1.69.1.6.2.1.6,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCMatches,Counter32,read-only,,current,,Counts the number of times this filter was matched.
.1.3.6.1.2.1.69.1.6.3,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpDefault,INTEGER,read-write,,deprecated,discard(1):accept(2),The default behavior for (bridged) packets that do not match IP filters (or Internet filters, if implemented) is defined by docsDevFilterIpDefault. If set to discard(1), all packets not matching an IP filter in docsDevFilterIpTable will be discarded. If set to accept(2), all packets not matching an IP filter or an Internet filter will be accepted for further processing (e.g., bridging).
.1.3.6.1.2.1.69.1.6.4,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpTable,,not-accessible,,deprecated,,An ordered list of filters or classifiers to apply to IP traffic. Filter application is ordered by the filter index, rather than by a best match algorithm (note that this implies that the filter table may have gaps in the index values). Packets that match no filters will have policy 0 in the docsDevFilterPolicyTable applied to them, if it exists. Otherwise, Packets that match no filters are discarded or forwarded according to the setting of docsDevFilterIpDefault. Any IP packet can theoretically match multiple rows of this table. When considering a packet, the table is scanned in row index order (e.g., filter 10 is checked before filter 20). If the packet matches that filter (which means that it matches ALL criteria for that row), actions appropriate to docsDevFilterIpControl and docsDevFilterPolicyId are taken. If the packet was discarded processing is complete. If docsDevFilterIpContinue is set to true, the filter comparison continues with the next row in the table, looking for additional matches. If the packet matches no filter in the table, the packet is accepted or dropped for further processing according to the setting of docsDevFilterIpDefault. If the packet is accepted, the actions specified by policy group 0 (e.g., the rows in docsDevFilterPolicyTable that have a value of 0 for docsDevFilterPolicyId) are taken, if that policy group exists. Logically, this table is consulted twice during the processing of any IP packet: once upon its acceptance from the L2 entity, and once upon its transmission to the L2 entity. In actuality, for cable modems, IP filtering is generally the only IP processing done for transit traffic. This means that inbound and outbound filtering can generally be done at the same time with one pass through the filter table. The objects in this table are only accessible from cable devices that are not operating in DiffServ MIB mode (RFC 3289). See the conformance section for details. Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevFilter mode for backward compatibility. Table entries MUST NOT persist across reboots for any device. This table is deprecated. Instead, use the DiffServ MIB from RFC 3289.
.1.3.6.1.2.1.69.1.6.4.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpEntry,,not-accessible,docsDevFilterIpIndex,deprecated,,Describes a filter to apply to IP traffic received on a specified interface. All identity objects in this table (e.g., source and destination address/mask, protocol, source/dest port, TOS/mask, interface and direction) must match their respective fields in the packet for any given filter to match. To create an entry in this table, docsDevFilterIpIfIndex must be specified.
.1.3.6.1.2.1.69.1.6.4.1.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpIndex,Integer32,not-accessible,,deprecated,,Index used to order the application of filters. The filter with the lowest index is always applied first.
.1.3.6.1.2.1.69.1.6.4.1.2,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Controls and reflects the status of rows in this table. Specifying only this object (with the appropriate index) on a CM is sufficient to create a filter row that matches all inbound packets on the ethernet interface and results in the packets being discarded. docsDevFilterIpIfIndex (at least) must be specified on a CMTS to create a row. Creation of the rows may be done via either create-and-wait or create-and-go, but the filter is not applied until this object is set to (or changes to) active. There is no restriction in changing any object in a row while this object is set to active.
.1.3.6.1.2.1.69.1.6.4.1.3,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpControl,INTEGER,read-create,,deprecated,discard(1):accept(2):policy(3),If set to discard(1), all packets matching this filter will be discarded, and scanning of the remainder of the filter list will be aborted. If set to accept(2), all packets matching this filter will be accepted for further processing (e.g., bridging). If docsDevFilterIpContinue is set to true, see if there are other matches; otherwise, done. If set to policy (3), execute the policy entries matched by docsDevFilterIpPolicyId in docsDevFilterPolicyTable. If docsDevFilterIpContinue is set to true, continue scanning the table for other matches; otherwise, done.
.1.3.6.1.2.1.69.1.6.4.1.4,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpIfIndex,Integer32,read-create,,deprecated,,The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another interface. If the value is zero, the filter applies to all interfaces. Default value in CMs is the index of the customer-side (e.g., ethernet) interface(s). In CMTSes, this object MUST be specified to create a row in this table. Note that according to the DOCSIS OSSIv1.1 specification, ifIndex '1' in the Cable Modem means that this row applies to all CMCI (customer-facing) interfaces.
.1.3.6.1.2.1.69.1.6.4.1.5,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpDirection,INTEGER,read-create,,deprecated,inbound(1):outbound(2):both(3),Determines whether the filter is applied to inbound(1) traffic, outbound(2) traffic, or traffic in both(3) directions.
.1.3.6.1.2.1.69.1.6.4.1.6,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpBroadcast,INTEGER,read-create,,deprecated,true(1):false(2),If set to true(1), the filter only applies to multicast and broadcast traffic. If set to false(2), the filter applies to all traffic.
.1.3.6.1.2.1.69.1.6.4.1.7,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpSaddr,IpAddress,read-create,,deprecated,,The source IP address, or portion thereof, that is to be matched for this filter. The source address is first masked (ANDed) against docsDevFilterIpSmask before being compared to this value. A value of 0 for this object and 0 for the mask matches all IP addresses.
.1.3.6.1.2.1.69.1.6.4.1.8,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpSmask,IpAddress,read-create,,deprecated,,A bit mask that is to be applied to the source address prior to matching. This mask is not necessarily the same as a subnet mask, but 1s bits must be leftmost and contiguous.
.1.3.6.1.2.1.69.1.6.4.1.9,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpDaddr,IpAddress,read-create,,deprecated,,The destination IP address, or portion thereof, that is to be matched for this filter. The destination address is first masked (ANDed) against docsDevFilterIpDmask before being compared to this value. A value of 00000000 for this object and 00000000 for the mask matches all IP addresses.
.1.3.6.1.2.1.69.1.6.4.1.10,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpDmask,IpAddress,read-create,,deprecated,,A bit mask that is to be applied to the destination address prior to matching. This mask is not necessarily the same as a subnet mask, but 1s bits MUST be leftmost and contiguous.
.1.3.6.1.2.1.69.1.6.4.1.11,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpProtocol,Integer32,read-create,,deprecated,,The IP protocol value that is to be matched. For example, icmp is 1, tcp is 6, and udp is 17. A value of 256 matches ANY protocol.
.1.3.6.1.2.1.69.1.6.4.1.12,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpSourcePortLow,Integer32,read-create,,deprecated,,This is the inclusive lower bound of the transport-layer source port range that is to be matched. If the IP protocol of the packet is neither UDP nor TCP, this object is ignored during matching.
.1.3.6.1.2.1.69.1.6.4.1.13,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpSourcePortHigh,Integer32,read-create,,deprecated,,This is the inclusive upper bound of the transport-layer source port range that is to be matched. If the IP protocol of the packet is neither UDP nor TCP, this object is ignored during matching.
.1.3.6.1.2.1.69.1.6.4.1.14,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpDestPortLow,Integer32,read-create,,deprecated,,This is the inclusive lower bound of the transport-layer destination port range that is to be matched. If the IP protocol of the packet is neither UDP nor TCP, this object is ignored during matching.
.1.3.6.1.2.1.69.1.6.4.1.15,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpDestPortHigh,Integer32,read-create,,deprecated,,This is the inclusive upper bound of the transport-layer destination port range that is to be matched. If the IP protocol of the packet is neither UDP nor TCP, this object is ignored during matching.
.1.3.6.1.2.1.69.1.6.4.1.16,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpMatches,Gauge32,read-only,,deprecated,,Counts the number of times this filter was matched. This object is initialized to 0 at boot, or at row creation, and is reset only upon reboot.
.1.3.6.1.2.1.69.1.6.4.1.17,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpTos,OCTET,read-create,,deprecated,,This is the value to be matched to the packet's TOS (Type of Service) value (after the TOS value is ANDed with docsDevFilterIpTosMask). A value for this object of 0 and a mask of 0 matches all TOS values.
.1.3.6.1.2.1.69.1.6.4.1.18,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpTosMask,OCTET,read-create,,deprecated,,The mask to be applied to the packet's TOS value before matching.
.1.3.6.1.2.1.69.1.6.4.1.19,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpContinue,INTEGER,read-create,,deprecated,true(1):false(2),If this value is set to true and docsDevFilterIpControl is anything but discard (1), continue scanning and applying policies. See Section 3.3.3 for more details.
.1.3.6.1.2.1.69.1.6.4.1.20,DOCS-CABLE-DEVICE-MIB::docsDevFilterIpPolicyId,Integer32,read-create,,deprecated,,This object points to an entry in docsDevFilterPolicyTable. If docsDevFilterIpControl is set to policy (3), execute all matching policies in docsDevFilterPolicyTable. If no matching policy exists, treat as if docsDevFilterIpControl were set to accept (1). If this object is set to the value of 0, there is no matching policy, and docsDevFilterPolicyTable MUST NOT be consulted.
.1.3.6.1.2.1.69.1.6.5,DOCS-CABLE-DEVICE-MIB::docsDevFilterPolicyTable,,not-accessible,,deprecated,,A Table that maps between a policy group ID and a set of pointers to policies to be applied. All rows with the same docsDevFilterPolicyId are part of the same group of policy pointers and are applied in the order in this table. docsDevFilterPolicyTable exists to allow multiple policy actions (referenced by policy pointers) to be applied to any given classified packet. The policy actions are applied in index order. For example: Index ID Type Action 1 1 TOS 1 9 5 TOS 1 12 1 IPSEC 3 This says that a packet that matches a filter with policy id 1 first has TOS policy 1 applied (which might set the TOS bits to enable a higher priority) and next has the IPSEC policy 3 applied (which may result in the packets being dumped into a secure VPN to a remote encryptor). Policy ID 0 is reserved for default actions and is applied only to packets that match no filters in docsDevFilterIpTable. Table entries MUST NOT persist across reboots for any device. This table is deprecated. Instead, use the DiffServ MIB from RFC 3289.
.1.3.6.1.2.1.69.1.6.5.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterPolicyEntry,,not-accessible,docsDevFilterPolicyIndex,deprecated,,An entry in the docsDevFilterPolicyTable. Entries are created by Network Management. To create an entry, docsDevFilterPolicyId MUST be specified.
.1.3.6.1.2.1.69.1.6.5.1.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterPolicyIndex,Integer32,not-accessible,,deprecated,,Index value for the table.
.1.3.6.1.2.1.69.1.6.5.1.2,DOCS-CABLE-DEVICE-MIB::docsDevFilterPolicyId,Integer32,read-create,,deprecated,,Policy ID for this entry. If a policy ID can apply to multiple rows of this table, all relevant policies are executed. Policy 0 (if populated) is applied to all packets that do not match any of the filters. N.B. If docsDevFilterIpPolicyId is set to 0, it DOES NOT match policy 0 of this table.
.1.3.6.1.2.1.69.1.6.5.1.5,DOCS-CABLE-DEVICE-MIB::docsDevFilterPolicyStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Object used to create an entry in this table. There is no restriction in changing any object in a row while this object is set to active. The following object MUST have a valid value before this object can be set to active: docsDevFilterPolicyPtr.
.1.3.6.1.2.1.69.1.6.5.1.6,DOCS-CABLE-DEVICE-MIB::docsDevFilterPolicyPtr,OBJECT,read-create,,deprecated,,This object points to a row in an applicable filter policy table. Currently, the only standard policy table is docsDevFilterTosTable. Per the textual convention, this object points to the first accessible object in the row; e.g., to point to a row in docsDevFilterTosTable with an index of 21, the value of this object would be the object identifier docsDevTosStatus.21. Vendors are recommended to adhere to the same convention when adding vendor-specific policy table extensions. If this pointer references an empty or non-existent row, then no policy action is taken. The default upon row creation is a null pointer that results in no policy action being taken.
.1.3.6.1.2.1.69.1.6.6,DOCS-CABLE-DEVICE-MIB::docsDevFilterTosTable,,not-accessible,,deprecated,,Table used to describe Type of Service (TOS) bits processing. This table is an adjunct to the docsDevFilterIpTable and the docsDevFilterPolicy table. Entries in the latter table can point to specific rows in this (and other) tables and cause specific actions to be taken. This table permits the manipulation of the value of the Type of Service bits in the IP header of the matched packet as follows: Set the tosBits of the packet to (tosBits & docsDevFilterTosAndMask) | docsDevFilterTosOrMask This construct allows you to do a clear and set of all the TOS bits in a flexible manner. Table entries MUST NOT persist across reboots for any device. This table is deprecated. Instead, use the DiffServ MIB from RFC 3289.
.1.3.6.1.2.1.69.1.6.6.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterTosEntry,,not-accessible,docsDevFilterTosIndex,deprecated,,A TOS policy entry.
.1.3.6.1.2.1.69.1.6.6.1.1,DOCS-CABLE-DEVICE-MIB::docsDevFilterTosIndex,Integer32,not-accessible,,deprecated,,The unique index for this row. There are no ordering requirements for this table, and any valid index may be specified.
.1.3.6.1.2.1.69.1.6.6.1.2,DOCS-CABLE-DEVICE-MIB::docsDevFilterTosStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object used to create and delete entries in this table. A row created by specifying just this object results in a row that specifies no change to the TOS bits. A row may be created using either the create-and-go or create-and-wait paradigms. There is no restriction on the ability to change values in this row while the row is active.
.1.3.6.1.2.1.69.1.6.6.1.3,DOCS-CABLE-DEVICE-MIB::docsDevFilterTosAndMask,OCTET,read-create,,deprecated,,This value is bitwise ANDed with the matched packet's TOS bits.
.1.3.6.1.2.1.69.1.6.6.1.4,DOCS-CABLE-DEVICE-MIB::docsDevFilterTosOrMask,OCTET,read-create,,deprecated,,This value is bitwise ORed with the result from the AND procedure (tosBits & docsDevFilterTosAndMask). The result then replaces the packet's TOS bits.
.1.3.6.1.2.1.69.1.7,DOCS-CABLE-DEVICE-MIB::docsDevCpe,,,,,,
.1.3.6.1.2.1.69.1.7.1,DOCS-CABLE-DEVICE-MIB::docsDevCpeEnroll,INTEGER,read-write,,current,none(1):any(2),This object controls the population of docsDevFilterCpeTable. If set to none, the filters must be set manually by a network management action (either configuration or SNMP set). If set to any, the CM wiretaps the packets originating from the ethernet and enrolls up to docsDevCpeIpMax addresses as based on the source IPv4 or v6 addresses of those packets.
.1.3.6.1.2.1.69.1.7.2,DOCS-CABLE-DEVICE-MIB::docsDevCpeIpMax,Integer32,read-write,,current,,This object controls the maximum number of CPEs allowed to be learned behind this device. If set to zero, any number of CPEs may connect up to the maximum permitted for the device. If set to -1, no filtering is done on CPE source addresses, and no entries are made in the docsDevFilterCpeTable via learning. If an attempt is made to set this to a number greater than that permitted for the device, it is set to that maximum.
.1.3.6.1.2.1.69.1.7.3,DOCS-CABLE-DEVICE-MIB::docsDevCpeTable,,not-accessible,,deprecated,,This table lists the IPv4 addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. Table entries MUST NOT persist across reboots for any device. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to add learned addresses automatically. This table is deprecated and is replaced by docsDevCpeInetTable.
.1.3.6.1.2.1.69.1.7.3.1,DOCS-CABLE-DEVICE-MIB::docsDevCpeEntry,,not-accessible,docsDevCpeIp,deprecated,,An entry in the docsDevFilterCpeTable. There is one entry for each IPv4 CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored; otherwise, upon receipt of an IP packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table but docsDevCpeEnroll is set to any and the sum of the table sizes of docsDevCpeTable and docsDevCpeInetTable is less than docsDevCpeIpMax, the address is added to the table, and packet processing continues. Otherwise, the packet is dropped. The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable).
.1.3.6.1.2.1.69.1.7.3.1.1,DOCS-CABLE-DEVICE-MIB::docsDevCpeIp,IpAddress,not-accessible,,deprecated,,The IPv4 address to which this entry applies. N.B. Attempts to set all zeros or all ones address values MUST be rejected.
.1.3.6.1.2.1.69.1.7.3.1.2,DOCS-CABLE-DEVICE-MIB::docsDevCpeSource,INTEGER,read-only,,deprecated,other(1):manual(2):learned(3),This object describes how this entry was created. If the value is manual(2), this row was created by a network management action (either configuration or SNMP set). If set to learned(3), then it was found via looking at the source IPv4 address of a received packet. The value other(1) is used for any entries that do not meet manual(2) or learned(3) criteria.
.1.3.6.1.2.1.69.1.7.3.1.3,DOCS-CABLE-DEVICE-MIB::docsDevCpeStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Standard object to manipulate rows. To create a row in this table, one only needs to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table.
.1.3.6.1.2.1.69.1.7.4,DOCS-CABLE-DEVICE-MIB::docsDevCpeInetTable,,not-accessible,,current,,This table lists the IP addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to add learned addresses automatically. Table entries MUST NOT persist across reboots for any device. This table exactly mirrors docsDevCpeTable and applies to IPv4 and IPv6 addresses.
.1.3.6.1.2.1.69.1.7.4.1,DOCS-CABLE-DEVICE-MIB::docsDevCpeInetEntry,,not-accessible,docsDevCpeInetType:docsDevCpeInetAddr,current,,An entry in the docsDevFilterCpeInetTable. There is one entry for each IP CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored; otherwise, upon receipt of an IP packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table but docsDevCpeEnroll is set to any and the sum of the table sizes for docsDevCpeTable and docsDevCpeInetTable is less than docsDevCpeIpMax, the address is added to the table, and packet processing continues. Otherwise, the packet is dropped. The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable). When an agent (cable modem) restarts, then all dynamically created rows are lost.
.1.3.6.1.2.1.69.1.7.4.1.1,DOCS-CABLE-DEVICE-MIB::docsDevCpeInetType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of internet address of docsDevCpeInetAddr.
.1.3.6.1.2.1.69.1.7.4.1.2,DOCS-CABLE-DEVICE-MIB::docsDevCpeInetAddr,OCTET,not-accessible,,current,,The Internet address to which this entry applies. Implementors need to be aware that if the size of docsDevCpeInetAddr exceeds 114 octets OIDs of instances of columns in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. Only unicast address are allowed for this object.
.1.3.6.1.2.1.69.1.7.4.1.3,DOCS-CABLE-DEVICE-MIB::docsDevCpeInetSource,INTEGER,read-only,,current,manual(2):learned(3),This object describes how this entry was created. If the value is manual(2), this row was created by a network management action (either configuration or SNMP set). If set to learned(3), then it was found via looking at the source IP address of a received packet.
.1.3.6.1.2.1.69.1.7.4.1.4,DOCS-CABLE-DEVICE-MIB::docsDevCpeInetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Standard object to manipulate rows. To create a row in this table, one only needs to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table.
.1.3.6.1.2.1.69.2,DOCS-CABLE-DEVICE-MIB::docsDevNotification,,,,,,
.1.3.6.1.2.1.69.3,DOCS-CABLE-DEVICE-MIB::docsDevConformance,,,,,,
.1.3.6.1.2.1.69.3.1,DOCS-CABLE-DEVICE-MIB::docsDevGroups,,,,,,
.1.3.6.1.2.1.69.3.1.1,DOCS-CABLE-DEVICE-MIB::docsDevBaseGroup,,,,,,A collection of objects providing device status and control.
.1.3.6.1.2.1.69.3.1.2,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessGroup,,,,,,A collection of objects for controlling access to SNMP objects on cable devices. This group has been deprecated because all the objects have been deprecated in favor of SNMPv3 and Coexistence MIBs.
.1.3.6.1.2.1.69.3.1.3,DOCS-CABLE-DEVICE-MIB::docsDevSoftwareGroup,,,,,,A collection of objects for controlling software downloads. This group has been deprecated and replaced by docsDevSoftwareGroupV2. Object docsDevSwServer has been replaced by docsDevSwServerAddressType and docsDevSwServerAddress, and docsDevSwServerTransportProtocol has been added to support TFTP and HTTP firmware downloads.
.1.3.6.1.2.1.69.3.1.4,DOCS-CABLE-DEVICE-MIB::docsDevServerGroup,,,,,,A collection of objects providing status about server provisioning. This group has been deprecated and replaced by docsDevServerGroupV2. The objects docsDevServerDhcp, docsDevServerTime, and docsDevServerTftp have been replaced by docsDevServerDhcpAddressType, docsDevServerDhcpAddress, docsDevServerTimeAddressType, docsDevServerTimeAddress, docsDevServerConfigTftpAddressType, and docsDevServerConfigTftpAddress.
.1.3.6.1.2.1.69.3.1.5,DOCS-CABLE-DEVICE-MIB::docsDevEventGroup,,,,,,A collection of objects used to control and monitor events. This group has been deprecated and replaced by docsDevEventGroupV2. The object docsDevEvSyslog has been replaced by docsDevEvSyslogAddressType and docsDevEvSyslogAddress, and docsDevEvThrottleInhibited has been replaced by docsDevEvThrottleThresholdExceeded.
.1.3.6.1.2.1.69.3.1.6,DOCS-CABLE-DEVICE-MIB::docsDevFilterGroup,,,,,,A collection of objects to specify filters at the link layer and IPv4 layer. This group has been deprecated and replaced by various groups from the DiffServ MIB.
.1.3.6.1.2.1.69.3.1.7,DOCS-CABLE-DEVICE-MIB::docsDevCpeGroup,,,,,,A collection of objects used to control the number and specific values of IPv4 addresses allowed for associated Customer Premises Equipment (CPE). This group has been deprecated and replaced by docsDevInetCpeGroup. The object docsDevCpeSource has been replaced by docsDevCpeInetSource, and docsDevCpeStatus has been replaced by docsDevCpeInetRowStatus.
.1.3.6.1.2.1.69.3.2,DOCS-CABLE-DEVICE-MIB::docsDevCompliances,,,,,,
.1.3.6.1.2.1.69.3.2.1,DOCS-CABLE-DEVICE-MIB::docsDevBasicCompliance,,,,,,The RFC 2669 compliance statement for MCNS/DOCSIS Cable Modems and Cable Modem Termination Systems.
.1.3.6.1.2.1.69.3.3,DOCS-CABLE-DEVICE-MIB::docsDevGroupsV2,,,,,,
.1.3.6.1.2.1.69.3.3.1,DOCS-CABLE-DEVICE-MIB::docsDevBaseIgmpGroup,,,,,,An object providing cable device IGMP status and control.
.1.3.6.1.2.1.69.3.3.2,DOCS-CABLE-DEVICE-MIB::docsDevBaseMaxCpeGroup,,,,,,An object providing management of the maximum number of CPEs permitted access through a cable modem.
.1.3.6.1.2.1.69.3.3.3,DOCS-CABLE-DEVICE-MIB::docsDevNmAccessExtGroup,,,,,,An object, in addition to the objects in docsDevNmAccessGroup, for controlling access to SNMP objects on cable devices. This group is included in this MIB due to existing implementations of docsDevNmAccessTrapVersion in DOCSIS cable modems. This group has been deprecated because the object has been deprecated in favor of SNMPv3 and Coexistence MIBs.
.1.3.6.1.2.1.69.3.3.4,DOCS-CABLE-DEVICE-MIB::docsDevSoftwareGroupV2,,,,,,A collection of objects for controlling software downloads. This group replaces docsDevSoftwareGroup.
.1.3.6.1.2.1.69.3.3.5,DOCS-CABLE-DEVICE-MIB::docsDevServerGroupV2,,,,,,A collection of objects providing status about server provisioning. This group replaces docsDevServerGroup.
.1.3.6.1.2.1.69.3.3.6,DOCS-CABLE-DEVICE-MIB::docsDevEventGroupV2,,,,,,A collection of objects used to control and monitor events. This group replaces docsDevEventGroup. The event reporting mechanism, and more specifically docsDevEvReporting, can be used to take advantage of the event reporting features of RFC3413 and RFC3014.
.1.3.6.1.2.1.69.3.3.7,DOCS-CABLE-DEVICE-MIB::docsDevFilterLLCGroup,,,,,,A collection of objects to specify link layer filters.
.1.3.6.1.2.1.69.3.3.8,DOCS-CABLE-DEVICE-MIB::docsDevInetCpeGroup,,,,,,A collection of objects used to control the number and specific values of Internet (e.g., IPv4 and IPv6) addresses allowed for associated Customer Premises Equipment (CPE).
.1.3.6.1.2.1.69.3.4,DOCS-CABLE-DEVICE-MIB::docsDevCompliancesV2,,,,,,
.1.3.6.1.2.1.69.3.4.1,DOCS-CABLE-DEVICE-MIB::docsDevCmCompliance,,,,,,The compliance statement for DOCSIS Cable Modems. This compliance statement applies to implementations of DOCSIS versions that are not IPv6 capable.
.1.3.6.1.2.1.69.3.4.2,DOCS-CABLE-DEVICE-MIB::docsDevCmtsCompliance,,,,,,The compliance statement for DOCSIS Cable Modem Termination Systems. This compliance statement applies to implementations of DOCSIS versions that are not IPv6 capable.
.1.3.6.1.2.1.70,ETHER-CHIPSET-MIB::etherChipsetMIB,,,,,,This MIB module contains registered values for use by the dot3StatsEtherChipSet object in the EtherLike-MIB. This object is used to identify the MAC hardware used to communicate on an interface. Note that the dot3StatsEtherChipSet object has been deprecated. The primary purpose of this module is to capture historic assignments made by the various IETF working groups that have been responsible for maintaining the EtherLike-MIB. Implementations which support the dot3StatsEtherChipSet object for backwards compatability may continue to use these values. For those chipsets not represented in this module, registration is required in other documentation, e.g., assignment within that part of the registration tree delegated to individual enterprises (see RFC 1155 and RFC 1902).
.1.3.6.1.2.1.71,NHRP-MIB::nhrpMIB,,,,,,This MIB contains managed object definitions for the Next Hop Resolution Procol, NHRP, as defined in RFC 2332 [17].
.1.3.6.1.2.1.71.1,NHRP-MIB::nhrpObjects,,,,,,
.1.3.6.1.2.1.71.1.1,NHRP-MIB::nhrpGeneralObjects,,,,,,
.1.3.6.1.2.1.71.1.1.1,NHRP-MIB::nhrpNextIndex,Unsigned32,read-only,,current,,This scalar is used for creating rows in the nhrpClientTable and the nhrpServerTable. The value of this variable is a currently unused value for nhrpClientIndex and nhrpServerIndex. The value returned when reading this variable must be unique for the NHC's and NHS's indices associated with this row. Subsequent attempts to read this variable must return different values. NOTE: this object exists in the General Group because it is to be used in establishing rows in the nhrpClientTable and the nhrpServerTable. In other words, the value retrieved from this object could become the value of nhrpClientIndex and nhprServerIndex. In the situation of an agent re-initialization the value of this object must be saved in non-volatile storage. This variable will return the special value 0 if no new rows can be created.
.1.3.6.1.2.1.71.1.1.2,NHRP-MIB::nhrpCacheTable,,not-accessible,,current,,This table contains mappings between internetwork layer addresses and NBMA subnetwork layer addresses.
.1.3.6.1.2.1.71.1.1.2.1,NHRP-MIB::nhrpCacheEntry,,not-accessible,nhrpCacheInternetworkAddrType:nhrpCacheInternetworkAddr:ifIndex:nhrpCacheIndex,current,,A cached mapping between an internetwork layer address and an NBMA address. Entries can be created by the network administrator using the nhrpCacheRowStatus column, or they may be added dynamically based on protocol operation (including NHRP, SCSP, and others, such as ATMARP). When created based by NHRP protocol operations this entry is largely based on contents contained in the Client Information Entry (CIE). Zero or more Client Information Entries (CIEs) may be included in the NHRP Packet. For a complete description of the CIE, refer to Section 5.2.0.1 of RFC 2332 [17].
.1.3.6.1.2.1.71.1.1.2.1.1,NHRP-MIB::nhrpCacheInternetworkAddrType,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The internetwork layer address type of this Next Hop Resolution Cache entry. The value of this object indicates how to interpret the values of nhrpCacheInternetworkAddr and nhrpCacheNextHopInternetworkAddr.
.1.3.6.1.2.1.71.1.1.2.1.2,NHRP-MIB::nhrpCacheInternetworkAddr,OCTET,not-accessible,,current,,The value of the internetwork address of the destination.
.1.3.6.1.2.1.71.1.1.2.1.3,NHRP-MIB::nhrpCacheIndex,Unsigned32,not-accessible,,current,,An identifier for this entry that has local significance within the scope of the General Group. This identifier is used here to uniquely identify this row, and also used in the 'nhrpPurgeTable' for the value of the 'nhrpPurgeCacheIdentifier'.
.1.3.6.1.2.1.71.1.1.2.1.4,NHRP-MIB::nhrpCachePrefixLength,Integer32,read-only,,current,,The number of bits that define the internetwork layer prefix associated with the nhrpCacheInternetworkAddr.
.1.3.6.1.2.1.71.1.1.2.1.5,NHRP-MIB::nhrpCacheNextHopInternetworkAddr,OCTET,read-create,,current,,The value of the internetwork address of the next hop.
.1.3.6.1.2.1.71.1.1.2.1.6,NHRP-MIB::nhrpCacheNbmaAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The NBMA address type. The value of this object indicates how to interpret the values of nhrpCacheNbmaAddr and nhrpCacheNbmaSubaddr.
.1.3.6.1.2.1.71.1.1.2.1.7,NHRP-MIB::nhrpCacheNbmaAddr,OCTET,read-create,,current,,The value of the NBMA subnetwork address of the next hop.
.1.3.6.1.2.1.71.1.1.2.1.8,NHRP-MIB::nhrpCacheNbmaSubaddr,OCTET,read-create,,current,,The value of the NBMA subaddress of the next hop. If there is no subaddress concept for the NBMA address family, this value will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.1.2.1.9,NHRP-MIB::nhrpCacheType,INTEGER,read-create,,current,other(1):register(2):resolveAuthoritative(3):resoveNonauthoritative(4):transit(5):administrativelyAdded(6):atmarp(7):scsp(8),An indication of how this cache entry was created. The values are: 'other(1)' The entry was added by some other means. 'register(2)' In a server, added based on a client registration. 'resolveAuthoritative(3)' In a client, added based on receiving an Authoritative NHRP Resolution Reply. 'resolveNonauthoritative(4)' In a client, added based on receiving a Nonauthoritative NHRP Resolution Reply. 'transit(5)' In a transit server, added by examining a forwarded NHRP packet. 'administrativelyAdded(6)' In a client or server, manually added by the administrator. The StorageType of this entry is reflected in 'nhrpCacheStorageType'. 'atmarp(7)' The entry was added due to an ATMARP. 'scsp(8)' The entry was added due to SCSP. When the entry is under creation using the nhrpCacheRowStatus column, the only value that can be specified by the administrator is 'administrativelyAdded'. Attempting to set any other value will cause an 'inconsistentValue' error. The value cannot be modified once the entry is active.
.1.3.6.1.2.1.71.1.1.2.1.10,NHRP-MIB::nhrpCacheState,INTEGER,read-only,,current,incomplete(1):ackReply(2):nakReply(3),An indication of the state of this entry. The values are: 'incomplete(1)' The client has sent a NHRP Resolution Request but has not yet received the NHRP Resolution Reply. 'ackReply(2)' For a client or server, this is a cached valid mapping. 'nakReply(3)' For a client or server, this is a cached NAK mapping.
.1.3.6.1.2.1.71.1.1.2.1.11,NHRP-MIB::nhrpCacheHoldingTimeValid,INTEGER,read-only,,current,true(1):false(2),True(1) is returned if the value of 'nhrpCacheType' is not 'administrativelyAdded'. Since the value of 'nhrpCacheType' was not configured by a user, the value of 'nhrpCacheHoldingTime' is considered valid. In other words, the value of 'nhrpCacheHoldingTime' represents the Holding Time for the cache Entry. If 'nhrpCacheType has been configured by a user, (i.e. the value of 'nhrpCacheType' is 'administrativelyAdded') then false(2) will be returned. This indicates that the value of 'nhrpCacheHoldingTime' is undefined because this row could possibly be backed up in nonvolatile storage.
.1.3.6.1.2.1.71.1.1.2.1.12,NHRP-MIB::nhrpCacheHoldingTime,Unsigned32,read-only,,current,,If the value of 'nhrpCacheHoldingTimeValid is true(1) then this object represents the number of seconds that the cache entry will remain in this table. When this value reaches 0 (zero) the row should be deleted. If the value of 'nhrpCacheHoldingTimeValid is false(2) then this object is undefined.
.1.3.6.1.2.1.71.1.1.2.1.13,NHRP-MIB::nhrpCacheNegotiatedMtu,Integer32,read-only,,current,,The maximum transmission unit (MTU) that was negotiated or registered for this entity. In other words, this is the actual MTU being used.
.1.3.6.1.2.1.71.1.1.2.1.14,NHRP-MIB::nhrpCachePreference,Integer32,read-create,,current,,An object which reflects the Preference value of the Client Information Entry (CIE). Zero or more Client Information Entries (CIEs) may be included in the NHRP Packet. One of the fields in the CIE is the Preference. For a complete description of the CIE, refer to Section 5.2.0.1 of RFC 2332 [17].
.1.3.6.1.2.1.71.1.1.2.1.15,NHRP-MIB::nhrpCacheStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This value only has meaning when the 'nhrpCacheType' has the value of 'administrativelyAdded'. When the row is created due to being 'administrativelyAdded', this object reflects whether this row is kept in volatile storage and lost upon reboot or if this row is backed up by non-volatile or permanent storage. If the value of 'nhrpCacheType' has a value which is not 'administrativelyAdded, then the value of this object is 'other(1)'.
.1.3.6.1.2.1.71.1.1.2.1.16,NHRP-MIB::nhrpCacheRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.1.3,NHRP-MIB::nhrpPurgeReqTable,,not-accessible,,current,,This table will track Purge Request Information.
.1.3.6.1.2.1.71.1.1.3.1,NHRP-MIB::nhrpPurgeReqEntry,,not-accessible,nhrpPurgeIndex,current,,Information regarding a Purge Request.
.1.3.6.1.2.1.71.1.1.3.1.1,NHRP-MIB::nhrpPurgeIndex,Unsigned32,not-accessible,,current,,An index for this entry that has local significance within the scope of this table.
.1.3.6.1.2.1.71.1.1.3.1.2,NHRP-MIB::nhrpPurgeCacheIdentifier,Unsigned32,read-create,,current,,This object identifies which row in 'nhrpCacheTable' is being purged. This object should have the same value as the 'nhrpCacheIndex' in the 'nhrpCacheTable'.
.1.3.6.1.2.1.71.1.1.3.1.3,NHRP-MIB::nhrpPurgePrefixLength,Integer32,read-only,,current,,In the case of NHRP Purge Requests, this specifies the equivalence class of addresses which match the first 'Prefix Length' bit positions of the Client Protocol Address specified in the Client Information Entry (CIE).
.1.3.6.1.2.1.71.1.1.3.1.4,NHRP-MIB::nhrpPurgeRequestID,Unsigned32,read-create,,current,,The Request ID used in the purge request.
.1.3.6.1.2.1.71.1.1.3.1.5,NHRP-MIB::nhrpPurgeReplyExpected,INTEGER,read-create,,current,true(1):false(2),An indication of whether this Purge Request has the 'N' Bit cleared (off).
.1.3.6.1.2.1.71.1.1.3.1.6,NHRP-MIB::nhrpPurgeRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.2,NHRP-MIB::nhrpClientObjects,,,,,,
.1.3.6.1.2.1.71.1.2.1,NHRP-MIB::nhrpClientTable,,not-accessible,,current,,Information about NHRP clients (NHCs) managed by this agent.
.1.3.6.1.2.1.71.1.2.1.1,NHRP-MIB::nhrpClientEntry,,not-accessible,nhrpClientIndex,current,,Information about a single NHC.
.1.3.6.1.2.1.71.1.2.1.1.1,NHRP-MIB::nhrpClientIndex,Unsigned32,not-accessible,,current,,An identifier for the NHRP client that is unique within the scope of this agent. The 'nhrpNextIndex' value should be consulted (read), prior to creating a row in this table, and the value returned from reading 'nhrpNextIndex' should be used as this object's value.
.1.3.6.1.2.1.71.1.2.1.1.2,NHRP-MIB::nhrpClientInternetworkAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the internetwork layer address of this client. This object indicates how the value of nhrpClientInternetworkAddr is to be interpreted.
.1.3.6.1.2.1.71.1.2.1.1.3,NHRP-MIB::nhrpClientInternetworkAddr,OCTET,read-create,,current,,The value of the internetwork layer address of this client.
.1.3.6.1.2.1.71.1.2.1.1.4,NHRP-MIB::nhrpClientNbmaAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the NBMA subnetwork address of this client. This object indicates how the values of nhrpClientNbmaAddr and nhrpClientNbmaSubaddr are to be interpreted.
.1.3.6.1.2.1.71.1.2.1.1.5,NHRP-MIB::nhrpClientNbmaAddr,OCTET,read-create,,current,,The NBMA subnetwork address of this client.
.1.3.6.1.2.1.71.1.2.1.1.6,NHRP-MIB::nhrpClientNbmaSubaddr,OCTET,read-create,,current,,The NBMA subaddress of this client. For NBMA address families without a subaddress concept, this will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.2.1.1.7,NHRP-MIB::nhrpClientInitialRequestTimeout,Integer32,read-create,,current,,The number of seconds that the client will wait before timing out an NHRP initial request. This object only has meaning for the initial timeout period.
.1.3.6.1.2.1.71.1.2.1.1.8,NHRP-MIB::nhrpClientRegistrationRequestRetries,Integer32,read-create,,current,,The number of times the client will retry the registration request before failure. A value of 0 means don't retry. A value of 65535 means retry forever.
.1.3.6.1.2.1.71.1.2.1.1.9,NHRP-MIB::nhrpClientResolutionRequestRetries,Integer32,read-create,,current,,The number of times the client will retry the resolution request before failure. A value of 0 means don't retry. A value of 65535 means retry forever.
.1.3.6.1.2.1.71.1.2.1.1.10,NHRP-MIB::nhrpClientPurgeRequestRetries,Integer32,read-create,,current,,The number of times the client will retry a purge request before failure. A value of 0 means don't retry. A value of 65535 means retry forever.
.1.3.6.1.2.1.71.1.2.1.1.11,NHRP-MIB::nhrpClientDefaultMtu,Unsigned32,read-create,,current,,The default maximum transmission unit (MTU) of the LIS/LAG which this client should use. This object will be initialized by the agent to the default MTU of the LIS/LAG (which is 9180) unless a different MTU value is specified during creation of this Client.
.1.3.6.1.2.1.71.1.2.1.1.12,NHRP-MIB::nhrpClientHoldTime,Unsigned32,read-create,,current,,The hold time the client will register.
.1.3.6.1.2.1.71.1.2.1.1.13,NHRP-MIB::nhrpClientRequestID,Unsigned32,read-create,,current,,The Request ID used to register this client with its server. According to Section 5.2.3 of the NHRP Specification, RFC 2332 [17], the Request ID must be kept in non-volatile storage, so that if an NHC crashes and re-initializes, it will use a different Request ID during the registration process when reregistering with the same NHS.
.1.3.6.1.2.1.71.1.2.1.1.14,NHRP-MIB::nhrpClientStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this row is kept in volatile storage and lost upon a Client crash or reboot situation, or if this row is backed up by nonvolatile or permanent storage.
.1.3.6.1.2.1.71.1.2.1.1.15,NHRP-MIB::nhrpClientRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.2.2,NHRP-MIB::nhrpClientRegistrationTable,,not-accessible,,current,,A table of Registration Request Information that needs to be maintained by the NHCs (clients).
.1.3.6.1.2.1.71.1.2.2.1,NHRP-MIB::nhrpClientRegistrationEntry,,not-accessible,nhrpClientIndex:nhrpClientRegIndex,current,,An NHC needs to maintain registration request information between the NHC and the NHS. An entry in this table represents information for a single registration request.
.1.3.6.1.2.1.71.1.2.2.1.1,NHRP-MIB::nhrpClientRegIndex,Unsigned32,not-accessible,,current,,An identifier for this entry such that it identifies a specific Registration Request from the NHC represented by the nhrpClientIndex.
.1.3.6.1.2.1.71.1.2.2.1.2,NHRP-MIB::nhrpClientRegUniqueness,INTEGER,read-create,,current,requestUnique(1):requestNotUnique(2),The Uniqueness indicator for this Registration Request. If this object has the value of requestUnique(1), then the Uniqueness bit is set in the the NHRP Registration Request represented by this row. The value cannot be changed once the row is created.
.1.3.6.1.2.1.71.1.2.2.1.3,NHRP-MIB::nhrpClientRegState,INTEGER,read-only,,current,other(1):registering(2):ackRegisterReply(3):nakRegisterReply(4),The registration state of this client. The values are: 'other(1)' The state of the registration request is not one of 'registering', 'ackRegisterReply' or 'nakRegisterReply'. 'registering(2)' A registration request has been issued and a registration reply is expected. 'ackRegisterReply(3)' A positive registration reply has been received. 'nakRegisterReply(4)' The client has received a negative registration reply (NAK).
.1.3.6.1.2.1.71.1.2.2.1.4,NHRP-MIB::nhrpClientRegRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.2.3,NHRP-MIB::nhrpClientNhsTable,,not-accessible,,current,,A table of NHSes that are available for use by this NHC (client). By default, the agent will add an entry to this table that corresponds to the client's default router.
.1.3.6.1.2.1.71.1.2.3.1,NHRP-MIB::nhrpClientNhsEntry,,not-accessible,nhrpClientIndex:nhrpClientNhsIndex,current,,An NHS that may be used by an NHC.
.1.3.6.1.2.1.71.1.2.3.1.1,NHRP-MIB::nhrpClientNhsIndex,Unsigned32,not-accessible,,current,,An identifier for an NHS available to an NHC.
.1.3.6.1.2.1.71.1.2.3.1.2,NHRP-MIB::nhrpClientNhsInternetworkAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the internetwork layer address of the NHRP server represented in this entry. This object indicates how the value of nhrpClientNhsInternetworkAddr is to be interpreted.
.1.3.6.1.2.1.71.1.2.3.1.3,NHRP-MIB::nhrpClientNhsInternetworkAddr,OCTET,read-create,,current,,The value of the destination internetwork layer address of the NHRP server represented by this entry. If this value is not known, this will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.2.3.1.4,NHRP-MIB::nhrpClientNhsNbmaAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the NBMA subnetwork address of the NHRP Server represented by this entry. This object indicates how the values of nhrpClientNhsNbmaAddr and nhrpClientNhsNbmaSubaddr are to be interpreted.
.1.3.6.1.2.1.71.1.2.3.1.5,NHRP-MIB::nhrpClientNhsNbmaAddr,OCTET,read-create,,current,,The NBMA subnetwork address of the NHS. The type of the address is indicated by the corresponding value of nhrpClientNhsNbmaAddrType.
.1.3.6.1.2.1.71.1.2.3.1.6,NHRP-MIB::nhrpClientNhsNbmaSubaddr,OCTET,read-create,,current,,The NBMA subaddress of the NHS. For NMBA address families that do not have the concept of subaddress, this will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.2.3.1.7,NHRP-MIB::nhrpClientNhsInUse,INTEGER,read-only,,current,true(1):false(2),An indication of whether this NHS is in use by the NHC.
.1.3.6.1.2.1.71.1.2.3.1.8,NHRP-MIB::nhrpClientNhsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.2.4,NHRP-MIB::nhrpClientStatTable,,not-accessible,,current,,This table contains statistics collected by NHRP clients.
.1.3.6.1.2.1.71.1.2.4.1,NHRP-MIB::nhrpClientStatEntry,,not-accessible,nhrpClientIndex,current,,Statistics collected by a NHRP client.
.1.3.6.1.2.1.71.1.2.4.1.1,NHRP-MIB::nhrpClientStatTxResolveReq,Counter32,read-only,,current,,The number of NHRP Resolution Requests transmitted by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.2,NHRP-MIB::nhrpClientStatRxResolveReplyAck,Counter32,read-only,,current,,The number of positively acknowledged NHRP Resolution Replies received by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.3,NHRP-MIB::nhrpClientStatRxResolveReplyNakProhibited,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies received by this client that contained the code indicating 'Administratively Prohibited'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.4,NHRP-MIB::nhrpClientStatRxResolveReplyNakInsufResources,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies received by this client that contained the code indicating 'Insufficient Resources'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.5,NHRP-MIB::nhrpClientStatRxResolveReplyNakNoBinding,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies received by this client that contained the code indicating 'No Internetworking Layer Address to NBMA Address Binding Exists'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.6,NHRP-MIB::nhrpClientStatRxResolveReplyNakNotUnique,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies received by this client that contained the code indicating 'Binding Exists But Is Not Unique'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.7,NHRP-MIB::nhrpClientStatTxRegisterReq,Counter32,read-only,,current,,The number of NHRP Registration Requests transmitted by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.8,NHRP-MIB::nhrpClientStatRxRegisterAck,Counter32,read-only,,current,,The number of positively acknowledged NHRP Registration Replies received by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.9,NHRP-MIB::nhrpClientStatRxRegisterNakProhibited,Counter32,read-only,,current,,The number of NAKed NHRP Registration Replies received by this client that contained the code indicating 'Administratively Prohibited'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.10,NHRP-MIB::nhrpClientStatRxRegisterNakInsufResources,Counter32,read-only,,current,,The number of NAKed NHRP Registration Replies received by this client that contained the code indicating 'Insufficient Resources'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.11,NHRP-MIB::nhrpClientStatRxRegisterNakAlreadyReg,Counter32,read-only,,current,,The number of NAKed NHRP Registration Replies received by this client that contained the code indicating 'Unique Internetworking Layer Address Already Registered'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.12,NHRP-MIB::nhrpClientStatRxPurgeReq,Counter32,read-only,,current,,The number of NHRP Purge Requests received by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.13,NHRP-MIB::nhrpClientStatTxPurgeReq,Counter32,read-only,,current,,The number of NHRP Purge Requests transmitted by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.14,NHRP-MIB::nhrpClientStatRxPurgeReply,Counter32,read-only,,current,,The number of NHRP Purge Replies received by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.15,NHRP-MIB::nhrpClientStatTxPurgeReply,Counter32,read-only,,current,,The number of NHRP Purge Replies transmitted by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.16,NHRP-MIB::nhrpClientStatTxErrorIndication,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this client. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.17,NHRP-MIB::nhrpClientStatRxErrUnrecognizedExtension,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'Unrecognized Extension'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.18,NHRP-MIB::nhrpClientStatRxErrLoopDetected,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'NHRP Loop Detected'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.19,NHRP-MIB::nhrpClientStatRxErrProtoAddrUnreachable,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'Protocol Address Unreachable'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.20,NHRP-MIB::nhrpClientStatRxErrProtoError,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'Protocol Error'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.21,NHRP-MIB::nhrpClientStatRxErrSduSizeExceeded,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'NHRP SDU Size Exceeded'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.22,NHRP-MIB::nhrpClientStatRxErrInvalidExtension,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'Invalid Extension'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.23,NHRP-MIB::nhrpClientStatRxErrAuthenticationFailure,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'Authentication Failure'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.24,NHRP-MIB::nhrpClientStatRxErrHopCountExceeded,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this client with the error code 'Hop Count Exceeded'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Client re-initialization and at other times as indicated by the value of nhrpClientStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.2.4.1.25,NHRP-MIB::nhrpClientStatDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this Client's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem or the NHRP Client re-initialization associated with this entry, then this object contains a zero value.
.1.3.6.1.2.1.71.1.3,NHRP-MIB::nhrpServerObjects,,,,,,
.1.3.6.1.2.1.71.1.3.1,NHRP-MIB::nhrpServerTable,,not-accessible,,current,,This table contains information for a set of NHSes associated with this agent.
.1.3.6.1.2.1.71.1.3.1.1,NHRP-MIB::nhrpServerEntry,,not-accessible,nhrpServerIndex,current,,Information about a single NHS.
.1.3.6.1.2.1.71.1.3.1.1.1,NHRP-MIB::nhrpServerIndex,Unsigned32,not-accessible,,current,,An identifier for the server that is unique within the scope of this agent.
.1.3.6.1.2.1.71.1.3.1.1.2,NHRP-MIB::nhrpServerInternetworkAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the internetwork layer address of this server. This object is used to interpret the value of nhrpServerInternetworkAddr.
.1.3.6.1.2.1.71.1.3.1.1.3,NHRP-MIB::nhrpServerInternetworkAddr,OCTET,read-create,,current,,The value of the internetwork layer address of this server.
.1.3.6.1.2.1.71.1.3.1.1.4,NHRP-MIB::nhrpServerNbmaAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the NBMA subnetwork address of this server. This object is used to interpret the value of nhrpServerNbmaAddr.
.1.3.6.1.2.1.71.1.3.1.1.5,NHRP-MIB::nhrpServerNbmaAddr,OCTET,read-create,,current,,The value of the NBMA subnetwork address of this server.
.1.3.6.1.2.1.71.1.3.1.1.6,NHRP-MIB::nhrpServerNbmaSubaddr,OCTET,read-create,,current,,The value of the NBMA subaddress of this server. For NBMA address families without a subaddress concept, this will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.3.1.1.7,NHRP-MIB::nhrpServerStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this row is kept in volatile storage and lost upon a Server crash or reboot situation, or if this row is backed up by nonvolatile or permanent storage.
.1.3.6.1.2.1.71.1.3.1.1.8,NHRP-MIB::nhrpServerRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.3.2,NHRP-MIB::nhrpServerCacheTable,,not-accessible,,current,,This table extends the nhrpCacheTable for NHSes. If the nhrpCacheTable has a row added due to an NHS or based on information regarding an NHS then a row is also added in this table. The rows in this table will be created when rows in the nhrpCacheTable are created. However, there may be rows created in the nhrpCacheTable which do not have corresponding rows in this table. For example, if the nhrpCacheTable has a row added due to a Next Hop Client which is co-resident on the same device as the NHS, a row will not be added to this table.
.1.3.6.1.2.1.71.1.3.2.1,NHRP-MIB::nhrpServerCacheEntry,,not-accessible,nhrpCacheInternetworkAddrType:nhrpCacheInternetworkAddr:ifIndex:nhrpCacheIndex,current,,Additional information kept by a NHS for a relevant Next Hop Resolution Cache entry.
.1.3.6.1.2.1.71.1.3.2.1.1,NHRP-MIB::nhrpServerCacheAuthoritative,INTEGER,read-only,,current,true(1):false(2),An indication of whether this cache entry is authoritative, which means the entry was added because of a direct registration request with this server or by Server Cache Synchronization Protocol (SCSP) from an authoritative source.
.1.3.6.1.2.1.71.1.3.2.1.2,NHRP-MIB::nhrpServerCacheUniqueness,INTEGER,read-create,,current,true(1):false(2),The Uniqueness indicator for this cache entry used in duplicate address detection. This value cannot be changed after the entry is active.
.1.3.6.1.2.1.71.1.3.3,NHRP-MIB::nhrpServerNhcTable,,not-accessible,,current,,A table of NHCs that are available for use by this NHS (Server).
.1.3.6.1.2.1.71.1.3.3.1,NHRP-MIB::nhrpServerNhcEntry,,not-accessible,nhrpServerIndex:nhrpServerNhcIndex,current,,An NHC that may be used by an NHS.
.1.3.6.1.2.1.71.1.3.3.1.1,NHRP-MIB::nhrpServerNhcIndex,Unsigned32,not-accessible,,current,,An identifier for an NHC available to an NHS.
.1.3.6.1.2.1.71.1.3.3.1.2,NHRP-MIB::nhrpServerNhcPrefixLength,Integer32,read-create,,current,,The number of bits that define the internetwork layer prefix associated with the nhrpServerNhcInternetworkAddr.
.1.3.6.1.2.1.71.1.3.3.1.3,NHRP-MIB::nhrpServerNhcInternetworkAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the internetwork layer address of the NHRP Client represented in this entry. This object indicates how the value of nhrpServerNhcInternetworkAddr is to be interpreted.
.1.3.6.1.2.1.71.1.3.3.1.4,NHRP-MIB::nhrpServerNhcInternetworkAddr,OCTET,read-create,,current,,The value of the internetwork layer address of the NHRP Client represented by this entry. If this value is not known, this will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.3.3.1.5,NHRP-MIB::nhrpServerNhcNbmaAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of the NBMA subnetwork address of the NHRP Client represented by this entry. This object indicates how the values of nhrpServerNhcNbmaAddr and nhrpServerNhcNbmaSubaddr are to be interpreted.
.1.3.6.1.2.1.71.1.3.3.1.6,NHRP-MIB::nhrpServerNhcNbmaAddr,OCTET,read-create,,current,,The NBMA subnetwork address of the NHC. The type of the address is indicated by the corresponding value of nhrpServerNbmaAddrType.
.1.3.6.1.2.1.71.1.3.3.1.7,NHRP-MIB::nhrpServerNhcNbmaSubaddr,OCTET,read-create,,current,,The NBMA subaddress of the NHC. For NMBA address familes that do not have the concept of subaddress, this will be a zero-length OCTET STRING.
.1.3.6.1.2.1.71.1.3.3.1.8,NHRP-MIB::nhrpServerNhcInUse,INTEGER,read-only,,current,true(1):false(2),An indication of whether this NHC is in use by the NHS.
.1.3.6.1.2.1.71.1.3.3.1.9,NHRP-MIB::nhrpServerNhcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention.
.1.3.6.1.2.1.71.1.3.4,NHRP-MIB::nhrpServerStatTable,,not-accessible,,current,,Statistics collected by Next Hop Servers.
.1.3.6.1.2.1.71.1.3.4.1,NHRP-MIB::nhrpServerStatEntry,,not-accessible,nhrpServerIndex,current,,Statistics for a particular NHS. The statistics are broken into received (Rx), transmitted (Tx) and forwarded (Fw). Forwarded (Fw) would be done by a transit NHS.
.1.3.6.1.2.1.71.1.3.4.1.1,NHRP-MIB::nhrpServerStatRxResolveReq,Counter32,read-only,,current,,The number of NHRP Resolution Requests received by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.2,NHRP-MIB::nhrpServerStatTxResolveReplyAck,Counter32,read-only,,current,,The number of positively acknowledged NHRP Resolution Replies transmitted by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.3,NHRP-MIB::nhrpServerStatTxResolveReplyNakProhibited,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies transmitted by this server with the code 'Administratively Prohibited'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.4,NHRP-MIB::nhrpServerStatTxResolveReplyNakInsufResources,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies transmitted by this server with the code 'Insufficient Resources'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.5,NHRP-MIB::nhrpServerStatTxResolveReplyNakNoBinding,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies transmitted by this server with the code 'No Internetworking Layer Address to NBMA Address Binding Exists'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.6,NHRP-MIB::nhrpServerStatTxResolveReplyNakNotUnique,Counter32,read-only,,current,,The number of NAKed NHRP Resolution Replies transmitted by this server with the code 'Binding Exists But Is Not Unique'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.7,NHRP-MIB::nhrpServerStatRxRegisterReq,Counter32,read-only,,current,,The number of NHRP Registration Requests received by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.8,NHRP-MIB::nhrpServerStatTxRegisterAck,Counter32,read-only,,current,,The number of positively acknowledged NHRP Registration Replies transmitted by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.9,NHRP-MIB::nhrpServerStatTxRegisterNakProhibited,Counter32,read-only,,current,,The number of NAKed NHRP Registration Replies transmitted by this server with the code 'Administratively Prohibited'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.10,NHRP-MIB::nhrpServerStatTxRegisterNakInsufResources,Counter32,read-only,,current,,The number of NAKed NHRP Registration Replies transmitted by this server with the code 'Insufficient Resources'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.11,NHRP-MIB::nhrpServerStatTxRegisterNakAlreadyReg,Counter32,read-only,,current,,The number of NAKed NHRP Registration Replies transmitted by this server with the code 'Unique Internetworking Layer Address Already Registered'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.12,NHRP-MIB::nhrpServerStatRxPurgeReq,Counter32,read-only,,current,,The number of NHRP Purge Requests received by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.13,NHRP-MIB::nhrpServerStatTxPurgeReq,Counter32,read-only,,current,,The number of NHRP Purge Requests transmitted by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.14,NHRP-MIB::nhrpServerStatRxPurgeReply,Counter32,read-only,,current,,The number of NHRP Purge Replies received by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.15,NHRP-MIB::nhrpServerStatTxPurgeReply,Counter32,read-only,,current,,The number of NHRP Purge Replies transmitted by this server. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.16,NHRP-MIB::nhrpServerStatRxErrUnrecognizedExtension,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Unrecognized Extension'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.17,NHRP-MIB::nhrpServerStatRxErrLoopDetected,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'NHRP Loop Detected'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.18,NHRP-MIB::nhrpServerStatRxErrProtoAddrUnreachable,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Protocol Address Unreachable'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.19,NHRP-MIB::nhrpServerStatRxErrProtoError,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Protocol Error'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.20,NHRP-MIB::nhrpServerStatRxErrSduSizeExceeded,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'NHRP SDU Size Exceeded'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.21,NHRP-MIB::nhrpServerStatRxErrInvalidExtension,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Invalid Extension'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.22,NHRP-MIB::nhrpServerStatRxErrInvalidResReplyReceived,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Invalid Resolution Reply Received'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.23,NHRP-MIB::nhrpServerStatRxErrAuthenticationFailure,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Authentication Failure'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.24,NHRP-MIB::nhrpServerStatRxErrHopCountExceeded,Counter32,read-only,,current,,The number of NHRP Error Indication packets received by this server with the error code 'Hop Count Exceeded'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.25,NHRP-MIB::nhrpServerStatTxErrUnrecognizedExtension,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'Unrecognized Extension'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.26,NHRP-MIB::nhrpServerStatTxErrLoopDetected,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'NHRP Loop Detected'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.27,NHRP-MIB::nhrpServerStatTxErrProtoAddrUnreachable,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'Protocol Address Unreachable'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.28,NHRP-MIB::nhrpServerStatTxErrProtoError,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'Protocol Error'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.29,NHRP-MIB::nhrpServerStatTxErrSduSizeExceeded,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'NHRP SDU Size Exceeded'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.30,NHRP-MIB::nhrpServerStatTxErrInvalidExtension,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'Invalid Extension'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.31,NHRP-MIB::nhrpServerStatTxErrAuthenticationFailure,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'Authentication Failure'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.32,NHRP-MIB::nhrpServerStatTxErrHopCountExceeded,Counter32,read-only,,current,,The number of NHRP Error Indication packets transmitted by this server with the error code 'Hop Count Exceeded'. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.33,NHRP-MIB::nhrpServerStatFwResolveReq,Counter32,read-only,,current,,The number of NHRP Resolution Requests forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.34,NHRP-MIB::nhrpServerStatFwResolveReply,Counter32,read-only,,current,,The number of NHRP Resolution Replies forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.35,NHRP-MIB::nhrpServerStatFwRegisterReq,Counter32,read-only,,current,,The number of NHRP Registration Requests forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.36,NHRP-MIB::nhrpServerStatFwRegisterReply,Counter32,read-only,,current,,The number of NHRP Registration Replies forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.37,NHRP-MIB::nhrpServerStatFwPurgeReq,Counter32,read-only,,current,,The number of NHRP Purge Requests forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.38,NHRP-MIB::nhrpServerStatFwPurgeReply,Counter32,read-only,,current,,The number of NHRP Purge Replies forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.39,NHRP-MIB::nhrpServerStatFwErrorIndication,Counter32,read-only,,current,,The number of NHRP Error Indication packets forwarded by this server acting as a transit NHS. Discontinuities in the value of this counter can occur at re-initialization of the management system, at NHRP Server re-initialization and at other times as indicated by the value of nhrpServerStatDiscontinuityTime.
.1.3.6.1.2.1.71.1.3.4.1.40,NHRP-MIB::nhrpServerStatDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this Server's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem or the NHRP Server re-initialization associated with this entry, then this object contains a zero value.
.1.3.6.1.2.1.71.2,NHRP-MIB::nhrpConformance,,,,,,
.1.3.6.1.2.1.71.2.1,NHRP-MIB::nhrpCompliances,,,,,,
.1.3.6.1.2.1.71.2.1.1,NHRP-MIB::nhrpModuleCompliance,,,,,,The compliance statement for the NHRP MIB.
.1.3.6.1.2.1.71.2.2,NHRP-MIB::nhrpGroups,,,,,,
.1.3.6.1.2.1.71.2.2.1,NHRP-MIB::nhrpGeneralGroup,,,,,,Objects that apply to both NHRP clients and NHRP servers.
.1.3.6.1.2.1.71.2.2.2,NHRP-MIB::nhrpClientGroup,,,,,,Objects that apply only to NHRP clients.
.1.3.6.1.2.1.71.2.2.3,NHRP-MIB::nhrpServerGroup,,,,,,Objects that apply only to NHRP servers.
.1.3.6.1.2.1.72,IANA-ADDRESS-FAMILY-NUMBERS-MIB::ianaAddressFamilyNumbers,,,,,,The MIB module defines the AddressFamilyNumbers textual convention.
.1.3.6.1.2.1.73,IANA-LANGUAGE-MIB::ianaLanguages,,,,,,The MIB module registers object identifier values for well-known programming and scripting languages. Every language registration MUST describe the format used when transferring scripts written in this language. Any additions or changes to the contents of this MIB module require Designated Expert Review as defined in the Guidelines for Writing IANA Considerations Section document. The Designated Expert will be selected by the IESG Area Director of the OPS Area. Note, this module does not have to register all possible languages since languages are identified by object identifier values. It is therefore possible to registered  languages in private OID trees. The references given below are not normative with regard to the language version. Other references might be better suited to describe some newer  versions of this language. The references are only provided as `a pointer into the right direction'.
.1.3.6.1.2.1.73.1,IANA-LANGUAGE-MIB::ianaLangJavaByteCode,,,,,,Java byte code to be processed by a Java virtual machine. A script written in Java byte code is transferred by using the Java archive file format (JAR).
.1.3.6.1.2.1.73.2,IANA-LANGUAGE-MIB::ianaLangTcl,,,,,,The Tool Command Language (Tcl). A script written in the Tcl language is transferred in Tcl source code format.
.1.3.6.1.2.1.73.3,IANA-LANGUAGE-MIB::ianaLangPerl,,,,,,The Perl language. A script written in the Perl language is transferred in Perl source code format.
.1.3.6.1.2.1.73.4,IANA-LANGUAGE-MIB::ianaLangScheme,,,,,,The Scheme language. A script written in the Scheme language is transferred in Scheme source code format.
.1.3.6.1.2.1.73.5,IANA-LANGUAGE-MIB::ianaLangSRSL,,,,,,The SNMP Script Language defined by SNMP Research. A script written in the SNMP Script Language is transferred in the SNMP Script Language source code format.
.1.3.6.1.2.1.73.6,IANA-LANGUAGE-MIB::ianaLangPSL,,,,,,The Patrol Script Language defined by BMC Software. A script written in the Patrol Script Language is transferred in the Patrol Script Language source code format.
.1.3.6.1.2.1.73.7,IANA-LANGUAGE-MIB::ianaLangSMSL,,,,,,The Systems Management Scripting Language. A script written in the SMSL language is transferred in the SMSL source code format.
.1.3.6.1.2.1.74,AGENTX-MIB::agentxMIB,,,,,,This is the MIB module for the SNMP Agent Extensibility Protocol (AgentX). This MIB module will be implemented by the master agent. 
.1.3.6.1.2.1.74.1,AGENTX-MIB::agentxObjects,,,,,,
.1.3.6.1.2.1.74.1.1,AGENTX-MIB::agentxGeneral,,,,,,
.1.3.6.1.2.1.74.1.1.1,AGENTX-MIB::agentxDefaultTimeout,INTEGER,read-only,,current,,The default length of time, in seconds, that the master agent should allow to elapse after dispatching a message to a session before it regards the subagent as not responding. This is a system-wide value that may override the timeout value associated with a particular session (agentxSessionTimeout) or a particular registered MIB region (agentxRegTimeout). If the associated value of agentxSessionTimeout and agentxRegTimeout are zero, or impractical in accordance with implementation-specific procedure of the master agent, the value represented by this object will be the effective timeout value for the master agent to await a response to a dispatch from a given subagent. 
.1.3.6.1.2.1.74.1.1.2,AGENTX-MIB::agentxMasterAgentXVer,INTEGER,read-only,,current,,The AgentX protocol version supported by this master agent. The current protocol version is 1. Note that the master agent must also allow interaction with earlier version subagents. 
.1.3.6.1.2.1.74.1.2,AGENTX-MIB::agentxConnection,,,,,,
.1.3.6.1.2.1.74.1.2.1,AGENTX-MIB::agentxConnTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when the last row creation or deletion occurred in the agentxConnectionTable. 
.1.3.6.1.2.1.74.1.2.2,AGENTX-MIB::agentxConnectionTable,,not-accessible,,current,,The agentxConnectionTable tracks all current AgentX transport connections. There may be zero, one, or more AgentX sessions carried on a given AgentX connection. 
.1.3.6.1.2.1.74.1.2.2.1,AGENTX-MIB::agentxConnectionEntry,,not-accessible,agentxConnIndex,current,,An agentxConnectionEntry contains information describing a single AgentX transport connection. A connection may be used to support zero or more AgentX sessions. An entry is created when a new transport connection is established, and is destroyed when the transport connection is terminated. 
.1.3.6.1.2.1.74.1.2.2.1.1,AGENTX-MIB::agentxConnIndex,Unsigned32,not-accessible,,current,,agentxConnIndex contains the value that uniquely identifies an open transport connection used by this master agent to provide AgentX service. Values of this index should not be re-used. The value assigned to a given transport connection is constant for the lifetime of that connection. 
.1.3.6.1.2.1.74.1.2.2.1.2,AGENTX-MIB::agentxConnOpenTime,TimeTicks,read-only,,current,,The value of sysUpTime when this connection was established and, therefore, its value when this entry was added to the table. 
.1.3.6.1.2.1.74.1.2.2.1.3,AGENTX-MIB::agentxConnTransportDomain,OBJECT,read-only,,current,,The transport protocol in use for this connection to the subagent. 
.1.3.6.1.2.1.74.1.2.2.1.4,AGENTX-MIB::agentxConnTransportAddress,OCTET,read-only,,current,,The transport address of the remote (subagent) end of this connection to the master agent. This object may be zero-length for unix-domain sockets (and possibly other types of transport addresses) since the subagent need not bind a filename to its local socket. 
.1.3.6.1.2.1.74.1.3,AGENTX-MIB::agentxSession,,,,,,
.1.3.6.1.2.1.74.1.3.1,AGENTX-MIB::agentxSessionTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when the last row creation or deletion occurred in the agentxSessionTable. 
.1.3.6.1.2.1.74.1.3.2,AGENTX-MIB::agentxSessionTable,,not-accessible,,current,,A table of AgentX subagent sessions currently in effect. 
.1.3.6.1.2.1.74.1.3.2.1,AGENTX-MIB::agentxSessionEntry,,not-accessible,agentxConnIndex:agentxSessionIndex,current,,Information about a single open session between the AgentX master agent and a subagent is contained in this entry. An entry is created when a new session is successfully established and is destroyed either when the subagent transport connection has terminated or when the subagent session is closed. 
.1.3.6.1.2.1.74.1.3.2.1.1,AGENTX-MIB::agentxSessionIndex,Unsigned32,not-accessible,,current,,A unique index for the subagent session. It is the same as h.sessionID defined in the agentx header. Note that if a subagent's session with the master agent is closed for any reason its index should not be re-used. A value of zero(0) is specifically allowed in order to be compatible with the definition of h.sessionId. 
.1.3.6.1.2.1.74.1.3.2.1.2,AGENTX-MIB::agentxSessionObjectID,OBJECT,read-only,,current,,This is taken from the o.id field of the agentx-Open-PDU. This attribute will report a value of '0.0' for subagents not supporting the notion of an AgentX session object identifier. 
.1.3.6.1.2.1.74.1.3.2.1.3,AGENTX-MIB::agentxSessionDescr,OCTET,read-only,,current,,A textual description of the session. This is analogous to sysDescr defined in the SNMPv2-MIB in RFC 1907 [19] and is taken from the o.descr field of the agentx-Open-PDU. This attribute will report a zero-length string value for subagents not supporting the notion of a session description. 
.1.3.6.1.2.1.74.1.3.2.1.4,AGENTX-MIB::agentxSessionAdminStatus,INTEGER,read-write,,current,up(1):down(2),The administrative (desired) status of the session. Setting the value to 'down(2)' closes the subagent session (with c.reason set to 'reasonByManager'). 
.1.3.6.1.2.1.74.1.3.2.1.5,AGENTX-MIB::agentxSessionOpenTime,TimeTicks,read-only,,current,,The value of sysUpTime when this session was opened and, therefore, its value when this entry was added to the table. 
.1.3.6.1.2.1.74.1.3.2.1.6,AGENTX-MIB::agentxSessionAgentXVer,INTEGER,read-only,,current,,The version of the AgentX protocol supported by the session. This must be less than or equal to the value of agentxMasterAgentXVer. 
.1.3.6.1.2.1.74.1.3.2.1.7,AGENTX-MIB::agentxSessionTimeout,INTEGER,read-only,,current,,The length of time, in seconds, that a master agent should allow to elapse after dispatching a message to this session before it regards the subagent as not responding. This value is taken from the o.timeout field of the agentx-Open-PDU. This is a session-specific value that may be overridden by values associated with the specific registered MIB regions (see agentxRegTimeout). A value of zero(0) indicates that the master agent's default timeout value should be used (see agentxDefaultTimeout). 
.1.3.6.1.2.1.74.1.4,AGENTX-MIB::agentxRegistration,,,,,,
.1.3.6.1.2.1.74.1.4.1,AGENTX-MIB::agentxRegistrationTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime when the last row creation or deletion occurred in the agentxRegistrationTable. 
.1.3.6.1.2.1.74.1.4.2,AGENTX-MIB::agentxRegistrationTable,,not-accessible,,current,,A table of registered regions. 
.1.3.6.1.2.1.74.1.4.2.1,AGENTX-MIB::agentxRegistrationEntry,,not-accessible,agentxConnIndex:agentxSessionIndex:agentxRegIndex,current,,Contains information for a single registered region. An entry is created when a session successfully registers a region and is destroyed for any of three reasons: this region is unregistered by the session, the session is closed, or the subagent connection is closed. 
.1.3.6.1.2.1.74.1.4.2.1.1,AGENTX-MIB::agentxRegIndex,Unsigned32,not-accessible,,current,,agentxRegIndex uniquely identifies a registration entry. This value is constant for the lifetime of an entry. 
.1.3.6.1.2.1.74.1.4.2.1.2,AGENTX-MIB::agentxRegContext,OCTET,read-only,,current,,The context in which the session supports the objects in this region. A zero-length context indicates the default context. 
.1.3.6.1.2.1.74.1.4.2.1.3,AGENTX-MIB::agentxRegStart,OBJECT,read-only,,current,,The starting OBJECT IDENTIFIER of this registration entry. The session identified by agentxSessionIndex implements objects starting at this value (inclusive). Note that this value could identify an object type, an object instance, or a partial object instance. 
.1.3.6.1.2.1.74.1.4.2.1.4,AGENTX-MIB::agentxRegRangeSubId,Unsigned32,read-only,,current,,agentxRegRangeSubId is used to specify the range. This is taken from r.region_subid in the registration PDU. If the value of this object is zero, no range is specified. If it is non-zero, it identifies the `nth' sub-identifier in r.region for which this entry's agentxRegUpperBound value is substituted in the OID for purposes of defining the region's upper bound. 
.1.3.6.1.2.1.74.1.4.2.1.5,AGENTX-MIB::agentxRegUpperBound,Unsigned32,read-only,,current,,agentxRegUpperBound represents the upper-bound sub-identifier in a registration. This is taken from the r.upper_bound in the registration PDU. If agentxRegRangeSubid (r.region_subid) is zero, this value is also zero and is not used to define an upper bound for this registration. 
.1.3.6.1.2.1.74.1.4.2.1.6,AGENTX-MIB::agentxRegPriority,Unsigned32,read-only,,current,,The registration priority. Lower values have higher priority. This value is taken from r.priority in the register PDU. Sessions should use the value of 127 for r.priority if a default value is desired. 
.1.3.6.1.2.1.74.1.4.2.1.7,AGENTX-MIB::agentxRegTimeout,INTEGER,read-only,,current,,The timeout value, in seconds, for responses to requests associated with this registered MIB region. A value of zero(0) indicates the default value (indicated by by agentxSessionTimeout or agentxDefaultTimeout) is to be used. This value is taken from the r.timeout field of the agentx-Register-PDU. 
.1.3.6.1.2.1.74.1.4.2.1.8,AGENTX-MIB::agentxRegInstance,INTEGER,read-only,,current,true(1):false(2),The value of agentxRegInstance is `true' for registrations for which the INSTANCE_REGISTRATION was set, and is `false' for all other registrations. 
.1.3.6.1.2.1.74.2,AGENTX-MIB::agentxConformance,,,,,,
.1.3.6.1.2.1.74.2.1,AGENTX-MIB::agentxMIBGroups,,,,,,
.1.3.6.1.2.1.74.2.1.1,AGENTX-MIB::agentxMIBGroup,,,,,,All accessible objects in the AgentX MIB. 
.1.3.6.1.2.1.74.2.2,AGENTX-MIB::agentxMIBCompliances,,,,,,
.1.3.6.1.2.1.74.2.2.1,AGENTX-MIB::agentxMIBCompliance,,,,,,The compliance statement for SNMP entities that implement the AgentX protocol. Note that a compliant agent can implement all objects in this MIB module as read-only. 
.1.3.6.1.2.1.75,FIBRE-CHANNEL-FE-MIB::fcFeMIB,,,,,,The MIB module for Fibre Channel Fabric Element.
.1.3.6.1.2.1.75.1,FIBRE-CHANNEL-FE-MIB::fcFeMIBObjects,,,,,,
.1.3.6.1.2.1.75.1.1,FIBRE-CHANNEL-FE-MIB::fcFeConfig,,,,,,
.1.3.6.1.2.1.75.1.1.1,FIBRE-CHANNEL-FE-MIB::fcFeFabricName,OCTET,read-write,,current,,The Name_Identifier of the Fabric to which this Fabric Element belongs.
.1.3.6.1.2.1.75.1.1.2,FIBRE-CHANNEL-FE-MIB::fcFeElementName,OCTET,read-write,,current,,The Name_Identifier of the Fabric Element.
.1.3.6.1.2.1.75.1.1.3,FIBRE-CHANNEL-FE-MIB::fcFeModuleCapacity,Unsigned32,read-only,,current,,The maximum number of modules in the Fabric Element, regardless of their current state.
.1.3.6.1.2.1.75.1.1.4,FIBRE-CHANNEL-FE-MIB::fcFeModuleTable,,not-accessible,,current,,A table that contains, one entry for each module in the Fabric Element, information of the modules.
.1.3.6.1.2.1.75.1.1.4.1,FIBRE-CHANNEL-FE-MIB::fcFeModuleEntry,,not-accessible,fcFeModuleIndex,current,,An entry containing the configuration parameters of a module.
.1.3.6.1.2.1.75.1.1.4.1.1,FIBRE-CHANNEL-FE-MIB::fcFeModuleIndex,Unsigned32,not-accessible,,current,,This object identifies the module within the Fabric Element for which this entry contains information. This value is never greater than fcFeModuleCapacity.
.1.3.6.1.2.1.75.1.1.4.1.2,FIBRE-CHANNEL-FE-MIB::fcFeModuleDescr,OCTET,read-only,,current,,A textual description of the module. This value should include the full name and version identification of the module.
.1.3.6.1.2.1.75.1.1.4.1.3,FIBRE-CHANNEL-FE-MIB::fcFeModuleObjectID,OBJECT,read-only,,current,,The vendor's authoritative identification of the module. This value may be allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of module is being managed. For example, this object could take the value 1.3.6.1.4.1.99649.3.9 if vendor 'Neufe Inc.' was assigned the subtree 1.3.6.1.4.1.99649, and had assigned the identifier 1.3.6.1.4.1.99649.3.9 to its 'FeFiFo-16 PlugInCard.'
.1.3.6.1.2.1.75.1.1.4.1.4,FIBRE-CHANNEL-FE-MIB::fcFeModuleOperStatus,INTEGER,read-only,,current,online(1):offline(2):testing(3):faulty(4),This object indicates the operational status of the module: online(1) the module is functioning properly; offline(2) the module is not available; testing(3) the module is under testing; and faulty(4) the module is defective in some way.
.1.3.6.1.2.1.75.1.1.4.1.5,FIBRE-CHANNEL-FE-MIB::fcFeModuleLastChange,TimeTicks,read-only,,current,,This object contains the value of sysUpTime when the module entered its current operational status. A value of zero indicates that the operational status of the module has not changed since the agent last restarted.
.1.3.6.1.2.1.75.1.1.4.1.6,FIBRE-CHANNEL-FE-MIB::fcFeModuleFxPortCapacity,Unsigned32,read-only,,current,,The number of FxPort that can be contained within the module. Within each module, the ports are uniquely numbered in the range from 1 to fcFeModuleFxPortCapacity inclusive. However, the numbers are not required to be contiguous.
.1.3.6.1.2.1.75.1.1.4.1.7,FIBRE-CHANNEL-FE-MIB::fcFeModuleName,OCTET,read-write,,current,,The Name_Identifier of the module.
.1.3.6.1.2.1.75.1.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortTable,,not-accessible,,current,,A table that contains, one entry for each FxPort in the Fabric Element, configuration and service parameters of the FxPorts.
.1.3.6.1.2.1.75.1.1.5.1,FIBRE-CHANNEL-FE-MIB::fcFxPortEntry,,not-accessible,fcFeModuleIndex:fcFxPortIndex,current,,An entry containing the configuration and service parameters of a FxPort.
.1.3.6.1.2.1.75.1.1.5.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortIndex,Unsigned32,not-accessible,,current,,This object identifies the FxPort within the module. This number ranges from 1 to the value of fcFeModulePortCapacity for the associated module. The value remains constant for the identified FxPort until the module is re-initialized.
.1.3.6.1.2.1.75.1.1.5.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortName,OCTET,read-only,,current,,The World_wide Name of this FxPort. Each FxPort has a unique Port World_wide Name within the Fabric.
.1.3.6.1.2.1.75.1.1.5.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortFcphVersionHigh,Integer32,read-only,,current,,The highest or most recent version of FC-PH that the FxPort is configured to support.
.1.3.6.1.2.1.75.1.1.5.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortFcphVersionLow,Integer32,read-only,,current,,The lowest or earliest version of FC-PH that the FxPort is configured to support.
.1.3.6.1.2.1.75.1.1.5.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortBbCredit,Integer32,read-only,,current,,The total number of receive buffers available for holding Class 1 connect-request, Class 2 or 3 frames from the attached NxPort. It is for buffer-to-buffer flow control in the direction from the attached NxPort (if applicable) to FxPort.
.1.3.6.1.2.1.75.1.1.5.1.6,FIBRE-CHANNEL-FE-MIB::fcFxPortRxBufSize,Integer32,read-only,,current,,The largest Data_Field Size (in octets) for an FT_1 frame that can be received by the FxPort.
.1.3.6.1.2.1.75.1.1.5.1.7,FIBRE-CHANNEL-FE-MIB::fcFxPortRatov,Unsigned32,read-only,,current,,The Resource_Allocation_Timeout Value configured for the FxPort. This is used as the timeout value for determining when to reuse an NxPort resource such as a Recovery_Qualifier. It represents E_D_TOV (see next object) plus twice the maximum time that a frame may be delayed within the Fabric and still be delivered.
.1.3.6.1.2.1.75.1.1.5.1.8,FIBRE-CHANNEL-FE-MIB::fcFxPortEdtov,Unsigned32,read-only,,current,,The E_D_TOV value configured for the FxPort. The Error_Detect_Timeout Value is used as the timeout value for detecting an error condition.
.1.3.6.1.2.1.75.1.1.5.1.9,FIBRE-CHANNEL-FE-MIB::fcFxPortCosSupported,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),A value indicating the set of Classes of Service supported by the FxPort.
.1.3.6.1.2.1.75.1.1.5.1.10,FIBRE-CHANNEL-FE-MIB::fcFxPortIntermixSupported,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether or not the FxPort supports an Intermixed Dedicated Connection.
.1.3.6.1.2.1.75.1.1.5.1.11,FIBRE-CHANNEL-FE-MIB::fcFxPortStackedConnMode,INTEGER,read-only,,current,none(1):transparent(2):lockedDown(3),A value indicating the mode of Stacked Connect supported by the FxPort.
.1.3.6.1.2.1.75.1.1.5.1.12,FIBRE-CHANNEL-FE-MIB::fcFxPortClass2SeqDeliv,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether or not Class 2 Sequential Delivery is supported by the FxPort.
.1.3.6.1.2.1.75.1.1.5.1.13,FIBRE-CHANNEL-FE-MIB::fcFxPortClass3SeqDeliv,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether or not Class 3 Sequential Delivery is supported by the FxPort.
.1.3.6.1.2.1.75.1.1.5.1.14,FIBRE-CHANNEL-FE-MIB::fcFxPortHoldTime,Unsigned32,read-only,,current,,The maximum time (in microseconds) that the FxPort shall hold a frame before discarding the frame if it is unable to deliver the frame. The value 0 means that the FxPort does not support this parameter.
.1.3.6.1.2.1.75.1.2,FIBRE-CHANNEL-FE-MIB::fcFeStatus,,,,,,
.1.3.6.1.2.1.75.1.2.1,FIBRE-CHANNEL-FE-MIB::fcFxPortStatusTable,,not-accessible,,current,,A table that contains, one entry for each FxPort in the Fabric Element, operational status and parameters of the FxPorts.
.1.3.6.1.2.1.75.1.2.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortStatusEntry,,not-accessible,,current,,An entry containing operational status and parameters of a FxPort.
.1.3.6.1.2.1.75.1.2.1.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortID,OCTET,read-only,,current,,The address identifier by which this FxPort is identified within the Fabric. The FxPort may assign its address identifier to its attached NxPort(s) during Fabric Login.
.1.3.6.1.2.1.75.1.2.1.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortBbCreditAvailable,Gauge32,read-only,,current,,The number of buffers currently available for receiving frames from the attached port in the buffer-to-buffer flow control. The value should be less than or equal to fcFxPortBbCredit.
.1.3.6.1.2.1.75.1.2.1.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortOperMode,INTEGER,read-only,,current,unknown(1):fPort(2):flPort(3),The current operational mode of the FxPort.
.1.3.6.1.2.1.75.1.2.1.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortAdminMode,INTEGER,read-write,,current,fPort(2):flPort(3),The desired operational mode of the FxPort.
.1.3.6.1.2.1.75.1.2.2,FIBRE-CHANNEL-FE-MIB::fcFxPortPhysTable,,not-accessible,,current,,A table that contains, one entry for each FxPort in the Fabric Element, physical level status and parameters of the FxPorts.
.1.3.6.1.2.1.75.1.2.2.1,FIBRE-CHANNEL-FE-MIB::fcFxPortPhysEntry,,not-accessible,,current,,An entry containing physical level status and parameters of a FxPort.
.1.3.6.1.2.1.75.1.2.2.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortPhysAdminStatus,INTEGER,read-write,,current,online(1):offline(2):testing(3),The desired state of the FxPort. A management station may place the FxPort in a desired state by setting this object accordingly. The testing(3) state indicates that no operational frames can be passed. When a Fabric Element initializes, all FxPorts start with fcFxPortPhysAdminStatus in the offline(2) state. As the result of either explicit management action or per configuration information accessible by the Fabric Element, fcFxPortPhysAdminStatus is then changed to either the online(1) or testing(3) states, or remains in the offline state.
.1.3.6.1.2.1.75.1.2.2.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortPhysOperStatus,INTEGER,read-only,,current,online(1):offline(2):testing(3):linkFailure(4),The current operational status of the FxPort. The testing(3) indicates that no operational frames can be passed. If fcFxPortPhysAdminStatus is offline(2) then fcFxPortPhysOperStatus should be offline(2). If fcFxPortPhysAdminStatus is changed to online(1) then fcFxPortPhysOperStatus should change to online(1) if the FxPort is ready to accept Fabric Login request from the attached NxPort; it should proceed and remain in the link- failure(4) state if and only if there is a fault that prevents it from going to the online(1) state.
.1.3.6.1.2.1.75.1.2.2.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortPhysLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the FxPort entered its current operational status. A value of zero indicates that the FxPort's operational status has not changed since the agent last restarted.
.1.3.6.1.2.1.75.1.2.2.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortPhysRttov,Unsigned32,read-write,,current,,The Receiver_Transmitter_Timeout value of the FxPort. This is used by the receiver logic to detect Loss of Synchronization.
.1.3.6.1.2.1.75.1.2.3,FIBRE-CHANNEL-FE-MIB::fcFxLoginTable,,not-accessible,,current,,A table that contains, one entry for each NxPort attached to a particular FxPort in the Fabric Element, services parameters established from the most recent Fabric Login, explicit or implicit. Note that an FxPort may have one or more NxPort attached to it.
.1.3.6.1.2.1.75.1.2.3.1,FIBRE-CHANNEL-FE-MIB::fcFxLoginEntry,,not-accessible,fcFeModuleIndex:fcFxPortIndex:fcFxPortNxLoginIndex,current,,An entry containing service parameters established from a successful Fabric Login.
.1.3.6.1.2.1.75.1.2.3.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortNxLoginIndex,Integer32,not-accessible,,current,,The object identifies the associated NxPort in the attachment for which the entry contains information.
.1.3.6.1.2.1.75.1.2.3.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortFcphVersionAgreed,Integer32,read-only,,current,,The version of FC-PH that the FxPort has agreed to support from the Fabric Login
.1.3.6.1.2.1.75.1.2.3.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortNxPortBbCredit,Integer32,read-only,,current,,The total number of buffers available for holding Class 1 connect-request, Class 2 or Class 3 frames to be transmitted to the attached NxPort. It is for buffer-to- buffer flow control in the direction from FxPort to NxPort. The buffer-to-buffer flow control mechanism is indicated in the respective fcFxPortBbCreditModel.
.1.3.6.1.2.1.75.1.2.3.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortNxPortRxDataFieldSize,Integer32,read-only,,current,,The Receive Data Field Size of the attached NxPort. This object specifies the largest Data Field Size for an FT_1 frame that can be received by the NxPort.
.1.3.6.1.2.1.75.1.2.3.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortCosSuppAgreed,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),A variable indicating that the attached NxPort has requested the FxPort for the support of classes of services and the FxPort has granted the request.
.1.3.6.1.2.1.75.1.2.3.1.6,FIBRE-CHANNEL-FE-MIB::fcFxPortIntermixSuppAgreed,INTEGER,read-only,,current,true(1):false(2),A variable indicating that the attached NxPort has requested the FxPort for the support of Intermix and the FxPort has granted the request. This flag is only valid if Class 1 service is supported.
.1.3.6.1.2.1.75.1.2.3.1.7,FIBRE-CHANNEL-FE-MIB::fcFxPortStackedConnModeAgreed,INTEGER,read-only,,current,none(1):transparent(2):lockedDown(3),A variable indicating whether the FxPort has agreed to support stacked connect from the Fabric Login. This is only meaningful if Class 1 service has been agreed.
.1.3.6.1.2.1.75.1.2.3.1.8,FIBRE-CHANNEL-FE-MIB::fcFxPortClass2SeqDelivAgreed,INTEGER,read-only,,current,true(1):false(2),A variable indicating whether the FxPort has agreed to support Class 2 sequential delivery from the Fabric Login. This is only meaningful if Class 2 service has been agreed.
.1.3.6.1.2.1.75.1.2.3.1.9,FIBRE-CHANNEL-FE-MIB::fcFxPortClass3SeqDelivAgreed,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether the FxPort has agreed to support Class 3 sequential delivery from the Fabric Login. This is only meaningful if Class 3 service has been agreed.
.1.3.6.1.2.1.75.1.2.3.1.10,FIBRE-CHANNEL-FE-MIB::fcFxPortNxPortName,OCTET,read-only,,current,,The port name of the attached NxPort.
.1.3.6.1.2.1.75.1.2.3.1.11,FIBRE-CHANNEL-FE-MIB::fcFxPortConnectedNxPort,OCTET,read-only,,current,,The address identifier of the destination NxPort with which this FxPort is currently engaged in a either a Class 1 or loop connection. If this FxPort is not engaged in a connection, then the value of this object is '000000'H.
.1.3.6.1.2.1.75.1.2.3.1.12,FIBRE-CHANNEL-FE-MIB::fcFxPortBbCreditModel,INTEGER,read-write,,current,regular(1):alternate(2),This object identifies the BB_Credit model used by the FxPort.
.1.3.6.1.2.1.75.1.3,FIBRE-CHANNEL-FE-MIB::fcFeError,,,,,,
.1.3.6.1.2.1.75.1.3.1,FIBRE-CHANNEL-FE-MIB::fcFxPortErrorTable,,not-accessible,,current,,A table that contains, one entry for each FxPort, counters that record the numbers of errors detected.
.1.3.6.1.2.1.75.1.3.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortErrorEntry,,not-accessible,,current,,An entry containing error counters of a FxPort.
.1.3.6.1.2.1.75.1.3.1.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortLinkFailures,Counter32,read-only,,current,,The number of link failures detected by this FxPort.
.1.3.6.1.2.1.75.1.3.1.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortSyncLosses,Counter32,read-only,,current,,The number of loss of synchronization detected by the FxPort.
.1.3.6.1.2.1.75.1.3.1.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortSigLosses,Counter32,read-only,,current,,The number of loss of signal detected by the FxPort.
.1.3.6.1.2.1.75.1.3.1.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortPrimSeqProtoErrors,Counter32,read-only,,current,,The number of primitive sequence protocol errors detected by the FxPort.
.1.3.6.1.2.1.75.1.3.1.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortInvalidTxWords,Counter32,read-only,,current,,The number of invalid transmission word detected by the FxPort.
.1.3.6.1.2.1.75.1.3.1.1.6,FIBRE-CHANNEL-FE-MIB::fcFxPortInvalidCrcs,Counter32,read-only,,current,,The number of invalid CRC detected by this FxPort.
.1.3.6.1.2.1.75.1.3.1.1.7,FIBRE-CHANNEL-FE-MIB::fcFxPortDelimiterErrors,Counter32,read-only,,current,,The number of Delimiter Errors detected by this FxPort.
.1.3.6.1.2.1.75.1.3.1.1.8,FIBRE-CHANNEL-FE-MIB::fcFxPortAddressIdErrors,Counter32,read-only,,current,,The number of address identifier errors detected by this FxPort.
.1.3.6.1.2.1.75.1.3.1.1.9,FIBRE-CHANNEL-FE-MIB::fcFxPortLinkResetIns,Counter32,read-only,,current,,The number of Link Reset Protocol received by this FxPort from the attached NxPort.
.1.3.6.1.2.1.75.1.3.1.1.10,FIBRE-CHANNEL-FE-MIB::fcFxPortLinkResetOuts,Counter32,read-only,,current,,The number of Link Reset Protocol issued by this FxPort to the attached NxPort.
.1.3.6.1.2.1.75.1.3.1.1.11,FIBRE-CHANNEL-FE-MIB::fcFxPortOlsIns,Counter32,read-only,,current,,The number of Offline Sequence received by this FxPort.
.1.3.6.1.2.1.75.1.3.1.1.12,FIBRE-CHANNEL-FE-MIB::fcFxPortOlsOuts,Counter32,read-only,,current,,The number of Offline Sequence issued by this FxPort.
.1.3.6.1.2.1.75.1.4,FIBRE-CHANNEL-FE-MIB::fcFeAccounting,,,,,,
.1.3.6.1.2.1.75.1.4.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC1AccountingTable,,not-accessible,,current,,A table that contains, one entry for each FxPort in the Fabric Element, Class 1 accounting information recorded since the management agent has re-initialized.
.1.3.6.1.2.1.75.1.4.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC1AccountingEntry,,not-accessible,,current,,An entry containing Class 1 accounting information for each FxPort.
.1.3.6.1.2.1.75.1.4.1.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC1InFrames,Counter32,read-only,,current,,The number of Class 1 frames (other than Class 1 connect- request) received by this FxPort from its attached NxPort.
.1.3.6.1.2.1.75.1.4.1.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortC1OutFrames,Counter32,read-only,,current,,The number of Class 1 frames (other than Class 1 connect- request) delivered through this FxPort to its attached NxPort.
.1.3.6.1.2.1.75.1.4.1.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortC1InOctets,Counter32,read-only,,current,,The number of Class 1 frame octets, including the frame delimiters, received by this FxPort from its attached NxPort.
.1.3.6.1.2.1.75.1.4.1.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortC1OutOctets,Counter32,read-only,,current,,The number of Class 1 frame octets, including the frame delimiters, delivered through this FxPort its attached NxPort.
.1.3.6.1.2.1.75.1.4.1.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortC1Discards,Counter32,read-only,,current,,The number of Class 1 frames discarded by this FxPort.
.1.3.6.1.2.1.75.1.4.1.1.6,FIBRE-CHANNEL-FE-MIB::fcFxPortC1FbsyFrames,Counter32,read-only,,current,,The number of F_BSY frames generated by this FxPort against Class 1 connect-request.
.1.3.6.1.2.1.75.1.4.1.1.7,FIBRE-CHANNEL-FE-MIB::fcFxPortC1FrjtFrames,Counter32,read-only,,current,,The number of F_RJT frames generated by this FxPort against Class 1 connect-request.
.1.3.6.1.2.1.75.1.4.1.1.8,FIBRE-CHANNEL-FE-MIB::fcFxPortC1InConnections,Counter32,read-only,,current,,The number of Class 1 connections successfully established in which the attached NxPort is the source of the connect- request.
.1.3.6.1.2.1.75.1.4.1.1.9,FIBRE-CHANNEL-FE-MIB::fcFxPortC1OutConnections,Counter32,read-only,,current,,The number of Class 1 connections successfully established in which the attached NxPort is the destination of the connect-request.
.1.3.6.1.2.1.75.1.4.1.1.10,FIBRE-CHANNEL-FE-MIB::fcFxPortC1ConnTime,Unsigned32,read-only,,current,,The cumulative time that this FxPort has been engaged in Class 1 connection. The amount of time is counted from after a connect-request has been accepted until the connection is disengaged, either by an EOFdt or Link Reset.
.1.3.6.1.2.1.75.1.4.2,FIBRE-CHANNEL-FE-MIB::fcFxPortC2AccountingTable,,not-accessible,,current,,A table that contains, one entry for each FxPort in the Fabric Element, Class 2 accounting information recorded since the management agent has re-initialized.
.1.3.6.1.2.1.75.1.4.2.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC2AccountingEntry,,not-accessible,,current,,An entry containing Class 2 accounting information for each FxPort.
.1.3.6.1.2.1.75.1.4.2.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC2InFrames,Counter32,read-only,,current,,The number of Class 2 frames received by this FxPort from its attached NxPort.
.1.3.6.1.2.1.75.1.4.2.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortC2OutFrames,Counter32,read-only,,current,,The number of Class 2 frames delivered through this FxPort to its attached NxPort.
.1.3.6.1.2.1.75.1.4.2.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortC2InOctets,Counter32,read-only,,current,,The number of Class 2 frame octets, including the frame delimiters, received by this FxPort from its attached NxPort.
.1.3.6.1.2.1.75.1.4.2.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortC2OutOctets,Counter32,read-only,,current,,The number of Class 2 frame octets, including the frame delimiters, delivered through this FxPort to its attached NxPort.
.1.3.6.1.2.1.75.1.4.2.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortC2Discards,Counter32,read-only,,current,,The number of Class 2 frames discarded by this FxPort.
.1.3.6.1.2.1.75.1.4.2.1.6,FIBRE-CHANNEL-FE-MIB::fcFxPortC2FbsyFrames,Counter32,read-only,,current,,The number of F_BSY frames generated by this FxPort against Class 2 frames.
.1.3.6.1.2.1.75.1.4.2.1.7,FIBRE-CHANNEL-FE-MIB::fcFxPortC2FrjtFrames,Counter32,read-only,,current,,The number of F_RJT frames generated by this FxPort against Class 2 frames.
.1.3.6.1.2.1.75.1.4.3,FIBRE-CHANNEL-FE-MIB::fcFxPortC3AccountingTable,,not-accessible,,current,,A table that contains, one entry for each FxPort in the Fabric Element, Class 3 accounting information recorded since the management agent has re-initialized.
.1.3.6.1.2.1.75.1.4.3.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC3AccountingEntry,,not-accessible,,current,,An entry containing Class 3 accounting information for each FxPort.
.1.3.6.1.2.1.75.1.4.3.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortC3InFrames,Counter32,read-only,,current,,The number of Class 3 frames received by this FxPort from its attached NxPort.
.1.3.6.1.2.1.75.1.4.3.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortC3OutFrames,Counter32,read-only,,current,,The number of Class 3 frames delivered through this FxPort to its attached NxPort.
.1.3.6.1.2.1.75.1.4.3.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortC3InOctets,Counter32,read-only,,current,,The number of Class 3 frame octets, including the frame delimiters, received by this FxPort from its attached NxPort.
.1.3.6.1.2.1.75.1.4.3.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortC3OutOctets,Counter32,read-only,,current,,The number of Class 3 frame octets, including the frame delimiters, delivered through this FxPort to its attached NxPort.
.1.3.6.1.2.1.75.1.4.3.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortC3Discards,Counter32,read-only,,current,,The number of Class 3 frames discarded by this FxPort.
.1.3.6.1.2.1.75.1.5,FIBRE-CHANNEL-FE-MIB::fcFeCapabilities,,,,,,
.1.3.6.1.2.1.75.1.5.1,FIBRE-CHANNEL-FE-MIB::fcFxPortCapTable,,not-accessible,,current,,A table that contains, one entry for each FxPort, the capabilities of the port within the Fabric Element.
.1.3.6.1.2.1.75.1.5.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortCapEntry,,not-accessible,,current,,An entry containing the Cap of a FxPort.
.1.3.6.1.2.1.75.1.5.1.1.1,FIBRE-CHANNEL-FE-MIB::fcFxPortCapFcphVersionHigh,Integer32,read-only,,current,,The highest or most recent version of FC-PH that the FxPort is capable of supporting.
.1.3.6.1.2.1.75.1.5.1.1.2,FIBRE-CHANNEL-FE-MIB::fcFxPortCapFcphVersionLow,Integer32,read-only,,current,,The lowest or earliest version of FC-PH that the FxPort is capable of supporting.
.1.3.6.1.2.1.75.1.5.1.1.3,FIBRE-CHANNEL-FE-MIB::fcFxPortCapBbCreditMax,Integer32,read-only,,current,,The maximum number of receive buffers available for holding Class 1 connect-request, Class 2 or Class 3 frames from the attached NxPort.
.1.3.6.1.2.1.75.1.5.1.1.4,FIBRE-CHANNEL-FE-MIB::fcFxPortCapBbCreditMin,Integer32,read-only,,current,,The minimum number of receive buffers available for holding Class 1 connect-request, Class 2 or Class 3 frames from the attached NxPort.
.1.3.6.1.2.1.75.1.5.1.1.5,FIBRE-CHANNEL-FE-MIB::fcFxPortCapRxDataFieldSizeMax,Integer32,read-only,,current,,The maximum size in bytes of the Data Field in a frame that the FxPort is capable of receiving from its attached NxPort.
.1.3.6.1.2.1.75.1.5.1.1.6,FIBRE-CHANNEL-FE-MIB::fcFxPortCapRxDataFieldSizeMin,Integer32,read-only,,current,,The minimum size in bytes of the Data Field in a frame that the FxPort is capable of receiving from its attached NxPort.
.1.3.6.1.2.1.75.1.5.1.1.7,FIBRE-CHANNEL-FE-MIB::fcFxPortCapCos,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),A value indicating the set of Classes of Service that the FxPort is capable of supporting.
.1.3.6.1.2.1.75.1.5.1.1.8,FIBRE-CHANNEL-FE-MIB::fcFxPortCapIntermix,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether or not the FxPort is capable of supporting the intermixing of Class 2 and Class 3 frames during a Class 1 connection. This flag is only valid if the port is capable of supporting Class 1 service.
.1.3.6.1.2.1.75.1.5.1.1.9,FIBRE-CHANNEL-FE-MIB::fcFxPortCapStackedConnMode,INTEGER,read-only,,current,none(1):transparent(2):lockedDown(3),A value indicating the mode of Stacked Connect request that the FxPort is capable of supporting.
.1.3.6.1.2.1.75.1.5.1.1.10,FIBRE-CHANNEL-FE-MIB::fcFxPortCapClass2SeqDeliv,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether or not the FxPort is capable of supporting Class 2 Sequential Delivery.
.1.3.6.1.2.1.75.1.5.1.1.11,FIBRE-CHANNEL-FE-MIB::fcFxPortCapClass3SeqDeliv,INTEGER,read-only,,current,true(1):false(2),A flag indicating whether or not the FxPort is capable of supporting Class 3 Sequential Delivery.
.1.3.6.1.2.1.75.1.5.1.1.12,FIBRE-CHANNEL-FE-MIB::fcFxPortCapHoldTimeMax,Unsigned32,read-only,,current,,The maximum holding time (in microseconds) that the FxPort is capable of supporting.
.1.3.6.1.2.1.75.1.5.1.1.13,FIBRE-CHANNEL-FE-MIB::fcFxPortCapHoldTimeMin,Unsigned32,read-only,,current,,The minimum holding time (in microseconds) that the FxPort is capable of supporting.
.1.3.6.1.2.1.75.2,FIBRE-CHANNEL-FE-MIB::fcFeMIBConformance,,,,,,
.1.3.6.1.2.1.75.2.1,FIBRE-CHANNEL-FE-MIB::fcFeMIBCompliances,,,,,,
.1.3.6.1.2.1.75.2.1.1,FIBRE-CHANNEL-FE-MIB::fcFeMIBMinimumCompliance,,,,,,The minimum compliance statement for SNMP entities which implement the FIBRE-CHANNEL-FE-MIB.
.1.3.6.1.2.1.75.2.1.2,FIBRE-CHANNEL-FE-MIB::fcFeMIBFullCompliance,,,,,,The full compliance statement for SNMP entities which implement the FIBRE-CHANNEL-FE-MIB.
.1.3.6.1.2.1.75.2.2,FIBRE-CHANNEL-FE-MIB::fcFeMIBGroups,,,,,,
.1.3.6.1.2.1.75.2.2.1,FIBRE-CHANNEL-FE-MIB::fcFeConfigGroup,,,,,,A collection of objects providing the configuration and service parameters of the Fabric Element, the modules, and FxPorts.
.1.3.6.1.2.1.75.2.2.2,FIBRE-CHANNEL-FE-MIB::fcFeStatusGroup,,,,,,A collection of objects providing the operational status and established service parameters for the Fabric Element and the attached NxPorts.
.1.3.6.1.2.1.75.2.2.3,FIBRE-CHANNEL-FE-MIB::fcFeErrorGroup,,,,,,A collection of objects providing various error statistics detected by the FxPorts.
.1.3.6.1.2.1.75.2.2.4,FIBRE-CHANNEL-FE-MIB::fcFeClass1AccountingGroup,,,,,,A collection of objects providing various class 1
.1.3.6.1.2.1.75.2.2.5,FIBRE-CHANNEL-FE-MIB::fcFeClass2AccountingGroup,,,,,,A collection of objects providing various class 2
.1.3.6.1.2.1.75.2.2.6,FIBRE-CHANNEL-FE-MIB::fcFeClass3AccountingGroup,,,,,,A collection of objects providing various class 3 performance statistics detected by the FxPorts.
.1.3.6.1.2.1.75.2.2.7,FIBRE-CHANNEL-FE-MIB::fcFeCapabilitiesGroup,,,,,,A collection of objects providing the inherent capability of each FxPort within the Fabric Element.
.1.3.6.1.2.1.76,INET-ADDRESS-MIB::inetAddressMIB,,,,,,This MIB module defines textual conventions for representing Internet addresses. An Internet address can be an IPv4 address, an IPv6 address, or a DNS domain name. This module also defines textual conventions for Internet port numbers, autonomous system numbers, and the length of an Internet address prefix. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4001, see the RFC itself for full legal notices.
.1.3.6.1.2.1.77,IF-INVERTED-STACK-MIB::ifInvertedStackMIB,,,,,,The MIB module which provides the Inverted Stack Table for interface sub-layers.
.1.3.6.1.2.1.77.1,IF-INVERTED-STACK-MIB::ifInvMIBObjects,,,,,,
.1.3.6.1.2.1.77.1.1,IF-INVERTED-STACK-MIB::ifInvStackTable,,not-accessible,,current,,A table containing information on the relationships between the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'underneath' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x runs underneath the sub-layer with ifIndex value y, then this table contains: ifInvStackStatus.x.y=active For each ifIndex value, z, which identifies an active interface, there are always at least two instantiated rows in this table associated with z. For one of these rows, z is the value of ifStackHigherLayer; for the other, z is the value of ifStackLowerLayer. (If z is not involved in multiplexing, then these are the only two rows associated with z.) For example, two rows exist even for an interface which has no others stacked on top or below it: ifInvStackStatus.z.0=active ifInvStackStatus.0.z=active This table contains exactly the same number of rows as the ifStackTable, but the rows appear in a different order.
.1.3.6.1.2.1.77.1.1.1,IF-INVERTED-STACK-MIB::ifInvStackEntry,,not-accessible,ifStackLowerLayer:ifStackHigherLayer,current,,Information on a particular relationship between two sub- layers, specifying that one sub-layer runs underneath the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable.
.1.3.6.1.2.1.77.1.1.1.1,IF-INVERTED-STACK-MIB::ifInvStackStatus,INTEGER,read-only,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the relationship between two sub-layers. An instance of this object exists for each instance of the ifStackStatus object, and vice versa. For example, if the variable ifStackStatus.H.L exists, then the variable ifInvStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value. However, unlike ifStackStatus, the ifInvStackStatus object is NOT write-able. A network management application wishing to change a relationship between sub-layers H and L cannot do so by modifying the value of ifInvStackStatus.L.H, but must instead modify the value of ifStackStatus.H.L. After the ifStackTable is modified, the change will be reflected in this table.
.1.3.6.1.2.1.77.1.2,IF-INVERTED-STACK-MIB::ifInvConformance,,,,,,
.1.3.6.1.2.1.77.1.2.1,IF-INVERTED-STACK-MIB::ifInvGroups,,,,,,
.1.3.6.1.2.1.77.1.2.1.1,IF-INVERTED-STACK-MIB::ifInvStackGroup,,,,,,A collection of objects providing inverted information on the layering of MIB-II interfaces.
.1.3.6.1.2.1.77.1.2.2,IF-INVERTED-STACK-MIB::ifInvCompliances,,,,,,
.1.3.6.1.2.1.77.1.2.2.1,IF-INVERTED-STACK-MIB::ifInvCompliance,,,,,,The compliance statement for SNMP entities which provide inverted information on the layering of network interfaces.
.1.3.6.1.2.1.78,HCNUM-TC::hcnumTC,,,,,,A MIB module containing textual conventions for high capacity data types. This module addresses an immediate need for data types not directly supported in the SMIv2. This short-term solution is meant to be deprecated as a long-term solution is deployed.
.1.3.6.1.2.1.79,PTOPO-MIB::ptopoMIB,,,,,,The MIB module for physical topology information.
.1.3.6.1.2.1.79.1,PTOPO-MIB::ptopoMIBObjects,,,,,,
.1.3.6.1.2.1.79.1.1,PTOPO-MIB::ptopoData,,,,,,
.1.3.6.1.2.1.79.1.1.1,PTOPO-MIB::ptopoConnTable,,not-accessible,,current,,This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one ptopoConnEntry is present for each local port, or it may choose to maintain multiple ptopoConnEntries for the same local port. Entries based on lower numbered identifier types are preferred over higher numbered identifier types, i.e., lower values of the ptopoConnRemoteChassisType and ptopoConnRemotePortType objects.
.1.3.6.1.2.1.79.1.1.1.1,PTOPO-MIB::ptopoConnEntry,,not-accessible,ptopoConnTimeMark:ptopoConnLocalChassis:ptopoConnLocalPort:ptopoConnIndex,current,,Information about a particular physical network connection. Entries may be created and deleted in this table, either manually or by the agent, if a physical topology discovery process is active.
.1.3.6.1.2.1.79.1.1.1.1.1,PTOPO-MIB::ptopoConnTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention in RFC 2021 to see how this works.
.1.3.6.1.2.1.79.1.1.1.1.2,PTOPO-MIB::ptopoConnLocalChassis,Integer32,not-accessible,,current,,The entPhysicalIndex value used to identify the chassis component associated with the local connection endpoint.
.1.3.6.1.2.1.79.1.1.1.1.3,PTOPO-MIB::ptopoConnLocalPort,Integer32,not-accessible,,current,,The entPhysicalIndex value used to identify the port component associated with the local connection endpoint.
.1.3.6.1.2.1.79.1.1.1.1.4,PTOPO-MIB::ptopoConnIndex,Integer32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated local connection endpoint. A particular ptopoConnIndex value may be reused in the event an entry is aged out and later re-learned with the same (or different) remote chassis and port identifiers. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the ptopoConnIndex will wrap between reboots.
.1.3.6.1.2.1.79.1.1.1.1.5,PTOPO-MIB::ptopoConnRemoteChassisType,INTEGER,read-create,,current,chasIdEntPhysicalAlias(1):chasIdIfAlias(2):chasIdPortEntPhysicalAlias(3):chasIdMacAddress(4):chasIdPtopoGenAddr(5),The type of encoding used to identify the chassis associated with the remote connection endpoint. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.6,PTOPO-MIB::ptopoConnRemoteChassis,OCTET,read-create,,current,,The string value used to identify the chassis component associated with the remote connection endpoint. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.7,PTOPO-MIB::ptopoConnRemotePortType,INTEGER,read-create,,current,portIdIfAlias(1):portIdEntPhysicalAlias(2):portIdMacAddr(3):portIdPtopoGenAddr(4),The type of port identifier encoding used in the associated 'ptopoConnRemotePort' object. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.8,PTOPO-MIB::ptopoConnRemotePort,OCTET,read-create,,current,,The string value used to identify the port component associated with the remote connection endpoint. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.9,PTOPO-MIB::ptopoConnDiscAlgorithm,OBJECT,read-only,,current,,An indication of the algorithm used to discover the information contained in this conceptual row. A value of ptopoDiscoveryLocal indicates this entry was configured by the local agent, without use of a discovery protocol. A value of { 0 0 } indicates this entry was created manually by an NMS via the associated RowStatus object. 
.1.3.6.1.2.1.79.1.1.1.1.10,PTOPO-MIB::ptopoConnAgentNetAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),This network address type of the associated ptopoConnNetAddr object, unless that object contains a zero length string. In such a case, an NMS application should ignore any returned value for this object. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.11,PTOPO-MIB::ptopoConnAgentNetAddr,OCTET,read-create,,current,,This object identifies a network address which may be used to reach an SNMP agent entity containing information for the chassis and port components represented by the associated 'ptopoConnRemoteChassis' and 'ptopoConnRemotePort' objects. If no such address is known, then this object shall contain an empty string. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.12,PTOPO-MIB::ptopoConnMultiMacSASeen,INTEGER,read-only,,current,notUsed(1):unknown(2):oneAddr(3):multiAddr(4),This object indicates if multiple unicast source MAC addresses have been detected by the agent from the remote connection endpoint, since the creation of this entry. If this entry has an associated ptopoConnRemoteChassisType and/or ptopoConnRemotePortType value other than 'portIdMacAddr(3)', then the value 'notUsed(1)' is returned. Otherwise, one of the following conditions must be true: If the agent has not yet detected any unicast source MAC addresses from the remote port, then the value 'unknown(2)' is returned. If the agent has detected exactly one unicast source MAC address from the remote port, then the value 'oneAddr(3)' is returned. If the agent has detected more than one unicast source MAC address from the remote port, then the value 'multiAddr(4)' is returned.
.1.3.6.1.2.1.79.1.1.1.1.13,PTOPO-MIB::ptopoConnMultiNetSASeen,INTEGER,read-only,,current,notUsed(1):unknown(2):oneAddr(3):multiAddr(4),This object indicates if multiple network layer source addresses have been detected by the agent from the remote connection endpoint, since the creation of this entry. If this entry has an associated ptopoConnRemoteChassisType or ptopoConnRemotePortType value other than 'portIdGenAddr(4)' then the value 'notUsed(1)' is returned. Otherwise, one of the following conditions must be true: If the agent has not yet detected any network source addresses of the appropriate type from the remote port, then the value 'unknown(2)' is returned. If the agent has detected exactly one network source address of the appropriate type from the remote port, then the value 'oneAddr(3)' is returned. If the agent has detected more than one network source address (of the same appropriate type) from the remote port, this the value 'multiAddr(4)' is returned.
.1.3.6.1.2.1.79.1.1.1.1.14,PTOPO-MIB::ptopoConnIsStatic,INTEGER,read-create,,current,true(1):false(2),This object identifies static ptopoConnEntries. If this object has the value 'true(1)', then this entry is not subject to any age-out mechanisms implemented by the agent. If this object has the value 'false(2)', then this entry is subject to all age-out mechanisms implemented by the agent. This object may not be modified if the associated ptopoConnRowStatus object has a value of active(1).
.1.3.6.1.2.1.79.1.1.1.1.15,PTOPO-MIB::ptopoConnLastVerifyTime,TimeTicks,read-only,,current,,If the associated value of ptopoConnIsStatic is equal to 'false(2)', then this object contains the value of sysUpTime at the time the conceptual row was last verified by the agent, e.g., via reception of a topology protocol message, pertaining to the associated remote chassis and port. If the associated value of ptopoConnIsStatic is equal to 'true(1)', then this object shall contain the value of sysUpTime at the time this entry was last activated (i.e., ptopoConnRowStatus set to 'active(1)').
.1.3.6.1.2.1.79.1.1.1.1.16,PTOPO-MIB::ptopoConnRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row.
.1.3.6.1.2.1.79.1.2,PTOPO-MIB::ptopoGeneral,,,,,,
.1.3.6.1.2.1.79.1.2.1,PTOPO-MIB::ptopoLastChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time a conceptual row is created, modified, or deleted in the ptopoConnTable. An NMS can use this object to reduce polling of the ptopoData group objects.
.1.3.6.1.2.1.79.1.2.2,PTOPO-MIB::ptopoConnTabInserts,Counter32,read-only,,current,,The number of times an entry has been inserted into the ptopoConnTable.
.1.3.6.1.2.1.79.1.2.3,PTOPO-MIB::ptopoConnTabDeletes,Counter32,read-only,,current,,The number of times an entry has been deleted from the ptopoConnTable.
.1.3.6.1.2.1.79.1.2.4,PTOPO-MIB::ptopoConnTabDrops,Counter32,read-only,,current,,The number of times an entry would have been added to the ptopoConnTable, (e.g., via information learned from a topology protocol), but was not because of insufficient resources.
.1.3.6.1.2.1.79.1.2.5,PTOPO-MIB::ptopoConnTabAgeouts,Counter32,read-only,,current,,The number of times an entry has been deleted from the ptopoConnTable because the information timeliness interval for that entry has expired.
.1.3.6.1.2.1.79.1.3,PTOPO-MIB::ptopoConfig,,,,,,
.1.3.6.1.2.1.79.1.3.1,PTOPO-MIB::ptopoConfigTrapInterval,Integer32,read-write,,current,,This object controls the transmission of PTOPO notifications. If this object has a value of zero, then no ptopoConfigChange notifications will be transmitted by the agent. If this object has a non-zero value, then the agent must not generate more than one ptopoConfigChange trap-event in the indicated period, where a 'trap-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional configuration changes occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of ptopoLastChangeTime to detect any missed ptopoConfigChange trap-events, e.g. due to throttling or transmission loss. If notification transmission is enabled, the suggested default throttling period is 60 seconds, but transmission should be disabled by default. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a re-initialization of the management system.
.1.3.6.1.2.1.79.1.3.2,PTOPO-MIB::ptopoConfigMaxHoldTime,Integer32,read-write,,current,,This object specifies the desired time interval for which an agent will maintain dynamic ptopoConnEntries. After the specified number of seconds since the last time an entry was verified, in the absence of new verification (e.g., receipt of a topology protocol message), the agent shall remove the entry. Note that entries may not always be removed immediately, but may possibly be removed at periodic garbage collection intervals. This object only affects dynamic ptopoConnEntries, i.e. for which ptopoConnIsStatic equals 'false(2)'. Static entries are not aged out. Note that dynamic ptopoConnEntries may also be removed by the agent due to the expired timeliness of learned topology information (e.g., timeliness interval for a remote port expires). The actual age-out interval for a given entry is defined by the following formula: age-out-time = min(ptopoConfigMaxHoldTime, <entry-specific hold-time>) where <entry-specific hold-time> is determined by the discovery algorithm, and may be different for each entry.
.1.3.6.1.2.1.79.2,PTOPO-MIB::ptopoMIBNotifications,,,,,,
.1.3.6.1.2.1.79.2.0,PTOPO-MIB::ptopoMIBTrapPrefix,,,,,,
.1.3.6.1.2.1.79.2.0.1,PTOPO-MIB::ptopoConfigChange,,,,,,A ptopoConfigChange notification is sent when the value of ptopoLastChangeTime changes. It can be utilized by an NMS to trigger physical topology table maintenance polls. Note that transmission of ptopoConfigChange notifications are throttled by the agent, as specified by the 'ptopoConfigTrapInterval' object.
.1.3.6.1.2.1.79.3,PTOPO-MIB::ptopoRegistrationPoints,,,,,,
.1.3.6.1.2.1.79.3.1,PTOPO-MIB::ptopoDiscoveryMechanisms,,,,,,
.1.3.6.1.2.1.79.3.1.1,PTOPO-MIB::ptopoDiscoveryLocal,,,,,,
.1.3.6.1.2.1.79.4,PTOPO-MIB::ptopoConformance,,,,,,
.1.3.6.1.2.1.79.4.1,PTOPO-MIB::ptopoCompliances,,,,,,
.1.3.6.1.2.1.79.4.1.1,PTOPO-MIB::ptopoCompliance,,,,,,The compliance statement for SNMP entities which implement the PTOPO MIB.
.1.3.6.1.2.1.79.4.2,PTOPO-MIB::ptopoGroups,,,,,,
.1.3.6.1.2.1.79.4.2.1,PTOPO-MIB::ptopoDataGroup,,,,,,The collection of objects which are used to represent physical topology information for which a single agent provides management information. This group is mandatory for all implementations of the PTOPO MIB.
.1.3.6.1.2.1.79.4.2.2,PTOPO-MIB::ptopoGeneralGroup,,,,,,The collection of objects which are used to report the general status of the PTOPO MIB implementation. This group is mandatory for all agents which implement the PTOPO MIB.
.1.3.6.1.2.1.79.4.2.3,PTOPO-MIB::ptopoConfigGroup,,,,,,The collection of objects which are used to configure the PTOPO MIB implementation behavior. This group is mandatory for agents which implement the PTOPO MIB.
.1.3.6.1.2.1.79.4.2.4,PTOPO-MIB::ptopoNotificationsGroup,,,,,,The collection of notifications used to indicate PTOPO MIB data consistency and general status information. This group is mandatory for agents which implement the PTOPO MIB.
.1.3.6.1.2.1.80,DISMAN-PING-MIB::pingMIB,,,,,,The Ping MIB (DISMAN-PING-MIB) provides the capability of controlling the use of the ping function at a remote host. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices.
.1.3.6.1.2.1.80.0,DISMAN-PING-MIB::pingNotifications,,,,,,
.1.3.6.1.2.1.80.0.1,DISMAN-PING-MIB::pingProbeFailed,,,,,,Generated when a probe failure is detected, when the corresponding pingCtlTrapGeneration object is set to probeFailure(0), subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of consecutive probe failures that are required before this notification can be generated.
.1.3.6.1.2.1.80.0.2,DISMAN-PING-MIB::pingTestFailed,,,,,,Generated when a ping test is determined to have failed, when the corresponding pingCtlTrapGeneration object is set to testFailure(1). In this instance, pingCtlTrapTestFailureFilter should specify the number of probes in a test required to have failed in order to consider the test failed.
.1.3.6.1.2.1.80.0.3,DISMAN-PING-MIB::pingTestCompleted,,,,,,Generated at the completion of a ping test when the corresponding pingCtlTrapGeneration object has the testCompletion(2) bit set.
.1.3.6.1.2.1.80.1,DISMAN-PING-MIB::pingObjects,,,,,,
.1.3.6.1.2.1.80.1.1,DISMAN-PING-MIB::pingMaxConcurrentRequests,Unsigned32,read-write,,current,,The maximum number of concurrent active ping requests that are allowed within an agent implementation. A value of 0 for this object implies that there is no limit for the number of concurrent active requests in effect. The limit applies only to new requests being activated. When a new value is set, the agent will continue processing all the requests already active, even if their number exceeds the limit just imposed.
.1.3.6.1.2.1.80.1.2,DISMAN-PING-MIB::pingCtlTable,,not-accessible,,current,,Defines the ping Control Table for providing, via SNMP, the capability of performing ping operations at a remote host. The results of these operations are stored in the pingResultsTable and the pingProbeHistoryTable.
.1.3.6.1.2.1.80.1.2.1,DISMAN-PING-MIB::pingCtlEntry,,not-accessible,pingCtlOwnerIndex:pingCtlTestName,current,,Defines an entry in the pingCtlTable. The first index element, pingCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 3415, VACM) and that allows a management application to identify its entries. The second index, pingCtlTestName (also an SnmpAdminString), enables the same management application to have multiple outstanding requests.
.1.3.6.1.2.1.80.1.2.1.1,DISMAN-PING-MIB::pingCtlOwnerIndex,OCTET,not-accessible,,current,,To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to create or modify entries independently, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString and can thus be trivially mapped to a securityName or groupName defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy, all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible.
.1.3.6.1.2.1.80.1.2.1.2,DISMAN-PING-MIB::pingCtlTestName,OCTET,not-accessible,,current,,The name of the ping test. This is locally unique, within the scope of a pingCtlOwnerIndex.
.1.3.6.1.2.1.80.1.2.1.3,DISMAN-PING-MIB::pingCtlTargetAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Specifies the type of host address to be used at a remote host for performing a ping operation.
.1.3.6.1.2.1.80.1.2.1.4,DISMAN-PING-MIB::pingCtlTargetAddress,OCTET,read-create,,current,,Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the value of the corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus.
.1.3.6.1.2.1.80.1.2.1.5,DISMAN-PING-MIB::pingCtlDataSize,Unsigned32,read-create,,current,,Specifies the size of the data portion to be transmitted in a ping operation, in octets. Whether this value can be applied depends on the selected implementation method for performing a ping operation, indicated by pingCtlType in the same conceptual row. If the method used allows applying the value contained in this object, then it MUST be applied. If the specified size is not appropriate for the chosen ping method, the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).
.1.3.6.1.2.1.80.1.2.1.6,DISMAN-PING-MIB::pingCtlTimeOut,Unsigned32,read-create,,current,,Specifies the time-out value, in seconds, for a remote ping operation.
.1.3.6.1.2.1.80.1.2.1.7,DISMAN-PING-MIB::pingCtlProbeCount,Unsigned32,read-create,,current,,Specifies the number of times to perform a ping operation at a remote host as part of a single ping test.
.1.3.6.1.2.1.80.1.2.1.8,DISMAN-PING-MIB::pingCtlAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),Reflects the desired state that a pingCtlEntry should be in: enabled(1) - Attempt to activate the test as defined by this pingCtlEntry. disabled(2) - Deactivate the test as defined by this pingCtlEntry. Refer to the corresponding pingResultsOperStatus to determine the operational state of the test defined by this entry.
.1.3.6.1.2.1.80.1.2.1.9,DISMAN-PING-MIB::pingCtlDataFill,OCTET,read-create,,current,,The content of this object is used together with the corresponding pingCtlDataSize value to determine how to fill the data portion of a probe packet. The option of selecting a data fill pattern can be useful when links are compressed or have data pattern sensitivities. The contents of pingCtlDataFill should be repeated in a ping packet when the size of the data portion of the ping packet is greater than the size of pingCtlDataFill.
.1.3.6.1.2.1.80.1.2.1.10,DISMAN-PING-MIB::pingCtlFrequency,Unsigned32,read-create,,current,,The number of seconds to wait before repeating a ping test as defined by the value of the various objects in the corresponding row. A single ping test consists of a series of ping probes. The number of probes is determined by the value of the corresponding pingCtlProbeCount object. After a single test is completed the number of seconds as defined by the value of pingCtlFrequency MUST elapse before the next ping test is started. A value of 0 for this object implies that the test as defined by the corresponding entry will not be repeated.
.1.3.6.1.2.1.80.1.2.1.11,DISMAN-PING-MIB::pingCtlMaxRows,Unsigned32,read-create,,current,,The maximum number of corresponding entries allowed in the pingProbeHistoryTable. An implementation of this MIB will remove the oldest corresponding entry in the pingProbeHistoryTable to allow the addition of an new entry once the number of corresponding rows in the pingProbeHistoryTable reaches this value. Old entries are not removed when a new test is started. Entries are added to the pingProbeHistoryTable until pingCtlMaxRows is reached before entries begin to be removed. A value of 0 for this object disables creation of pingProbeHistoryTable entries.
.1.3.6.1.2.1.80.1.2.1.12,DISMAN-PING-MIB::pingCtlStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.80.1.2.1.13,DISMAN-PING-MIB::pingCtlTrapGeneration,BITS,read-create,,current,probeFailure(0):testFailure(1):testCompletion(2),The value of this object determines when and whether to generate a notification for this entry: probeFailure(0) - Generate a pingProbeFailed notification subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of consecutive probe failures that are required before a pingProbeFailed notification can be generated. testFailure(1) - Generate a pingTestFailed notification. In this instance the object pingCtlTrapTestFailureFilter can be used to determine the number of probe failures that signal when a test fails. testCompletion(2) - Generate a pingTestCompleted notification. By default, no bits are set, indicating that none of the above options is selected.
.1.3.6.1.2.1.80.1.2.1.14,DISMAN-PING-MIB::pingCtlTrapProbeFailureFilter,Unsigned32,read-create,,current,,The value of this object is used to determine when to generate a pingProbeFailed NOTIFICATION. Setting BIT probeFailure(0) of object pingCtlTrapGeneration to '1' implies that a pingProbeFailed NOTIFICATION is generated only when a number of consecutive ping probes equal to the value of pingCtlTrapProbeFailureFilter fail within a given ping test. After triggering the notification, the probe failure counter is reset to zero.
.1.3.6.1.2.1.80.1.2.1.15,DISMAN-PING-MIB::pingCtlTrapTestFailureFilter,Unsigned32,read-create,,current,,The value of this object is used to determine when to generate a pingTestFailed NOTIFICATION. Setting BIT testFailure(1) of object pingCtlTrapGeneration to '1' implies that a pingTestFailed NOTIFICATION is generated only when a number of consecutive ping tests equal to the value of pingCtlTrapProbeFailureFilter fail. After triggering the notification, the test failure counter is reset to zero.
.1.3.6.1.2.1.80.1.2.1.16,DISMAN-PING-MIB::pingCtlType,OBJECT,read-create,,current,,The value of this object is used either to report or to select the implementation method to be used for calculating a ping response time. The value of this object MAY be selected from pingImplementationTypeDomains. Additional implementation types SHOULD be allocated as required by implementers of the DISMAN-PING-MIB under their enterprise-specific registration point and not beneath pingImplementationTypeDomains.
.1.3.6.1.2.1.80.1.2.1.17,DISMAN-PING-MIB::pingCtlDescr,OCTET,read-create,,current,,The purpose of this object is to provide a descriptive name of the remote ping test.
.1.3.6.1.2.1.80.1.2.1.18,DISMAN-PING-MIB::pingCtlSourceAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Specifies the type of the source address, pingCtlSourceAddress, to be used at a remote host when a ping operation is performed.
.1.3.6.1.2.1.80.1.2.1.19,DISMAN-PING-MIB::pingCtlSourceAddress,OCTET,read-create,,current,,Use the specified IP address (which must be given in numeric form, not as a hostname) as the source address in outgoing probe packets. On hosts with more than one IP address, this option can be used to select the address to be used. If the IP address is not one of this machine's interface addresses, an error is returned and nothing is sent. A zero-length octet string value for this object disables source address specification. The address type (InetAddressType) that relates to this object is specified by the corresponding value of pingCtlSourceAddressType.
.1.3.6.1.2.1.80.1.2.1.20,DISMAN-PING-MIB::pingCtlIfIndex,Integer32,read-create,,current,,Setting this object to an interface's ifIndex prior to starting a remote ping operation directs the ping probes to be transmitted over the specified interface. A value of zero for this object means that this option is not enabled.
.1.3.6.1.2.1.80.1.2.1.21,DISMAN-PING-MIB::pingCtlByPassRouteTable,INTEGER,read-create,,current,true(1):false(2),The purpose of this object is to enable optional bypassing the route table. If enabled, the remote host will bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly attached network, an error is returned. This option can be used to perform the ping operation to a local host through an interface that has no route defined (e.g., after the interface was dropped by the routing daemon at the host).
.1.3.6.1.2.1.80.1.2.1.22,DISMAN-PING-MIB::pingCtlDSField,Unsigned32,read-create,,current,,Specifies the value to store in the Type of Service (TOS) octet in the IPv4 header or in the Traffic Class octet in the IPv6 header, respectively, of the IP packet used to encapsulate the ping probe. The octet to be set in the IP header contains the Differentiated Services (DS) Field in the six most significant bits. This option can be used to determine what effect an explicit DS Field setting has on a ping response. Not all values are legal or meaningful. A value of 0 means that the function represented by this option is not supported. DS Field usage is often not supported by IP implementations, and not all values are supported. Refer to RFC 2474 and RFC 3260 for guidance on usage of this field.
.1.3.6.1.2.1.80.1.2.1.23,DISMAN-PING-MIB::pingCtlRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the pingCtlTable. Deletion of an entry in this table results in the deletion of all corresponding (same pingCtlOwnerIndex and pingCtlTestName index values) pingResultsTable and pingProbeHistoryTable entries. A value MUST be specified for pingCtlTargetAddress prior to acceptance of a transition to active(1) state. When a value for pingCtlTargetAddress is set, the value of object pingCtlRowStatus changes from notReady(3) to notInService(2). Activation of a remote ping operation is controlled via pingCtlAdminStatus, not by changing this object's value to active(1). Transitions in and out of active(1) state are not allowed while an entry's pingResultsOperStatus is active(1), with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active ping operation. The operational state of a ping operation can be determined by examination of its pingResultsOperStatus object.
.1.3.6.1.2.1.80.1.3,DISMAN-PING-MIB::pingResultsTable,,not-accessible,,current,,Defines the Ping Results Table for providing the capability of performing ping operations at a remote host. The results of these operations are stored in the pingResultsTable and the pingProbeHistoryTable. An entry is added to the pingResultsTable when an pingCtlEntry is started by successful transition of its pingCtlAdminStatus object to enabled(1). If the object pingCtlAdminStatus already has the value enabled(1), and if the corresponding pingResultsOperStatus object has the value completed(3), then successfully writing enabled(1) to object pingCtlAdminStatus re-initializes the already existing entry in the pingResultsTable. The values of objects in the re-initialized entry are the same as the values of objects in a new entry would be. An entry is removed from the pingResultsTable when its corresponding pingCtlEntry is deleted.
.1.3.6.1.2.1.80.1.3.1,DISMAN-PING-MIB::pingResultsEntry,,not-accessible,pingCtlOwnerIndex:pingCtlTestName,current,,Defines an entry in the pingResultsTable. The pingResultsTable has the same indexing as the pingCtlTable so that a pingResultsEntry corresponds to the pingCtlEntry that caused it to be created.
.1.3.6.1.2.1.80.1.3.1.1,DISMAN-PING-MIB::pingResultsOperStatus,INTEGER,read-only,,current,enabled(1):disabled(2):completed(3),Reflects the operational state of a pingCtlEntry: enabled(1) - Test is active. disabled(2) - Test has stopped. completed(3) - Test is completed.
.1.3.6.1.2.1.80.1.3.1.2,DISMAN-PING-MIB::pingResultsIpTargetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the type of address stored in the corresponding pingResultsIpTargetAddress object.
.1.3.6.1.2.1.80.1.3.1.3,DISMAN-PING-MIB::pingResultsIpTargetAddress,OCTET,read-only,,current,,This object reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero-length octet string when a DNS name is not specified or when a specified DNS name fails to resolve. The address type (InetAddressType) that relates to this object is specified by the corresponding value of pingResultsIpTargetAddressType.
.1.3.6.1.2.1.80.1.3.1.4,DISMAN-PING-MIB::pingResultsMinRtt,Unsigned32,read-only,,current,,The minimum ping round-trip-time (RTT) received. A value of 0 for this object implies that no RTT has been received.
.1.3.6.1.2.1.80.1.3.1.5,DISMAN-PING-MIB::pingResultsMaxRtt,Unsigned32,read-only,,current,,The maximum ping round-trip-time (RTT) received. A value of 0 for this object implies that no RTT has been received.
.1.3.6.1.2.1.80.1.3.1.6,DISMAN-PING-MIB::pingResultsAverageRtt,Unsigned32,read-only,,current,,The current average ping round-trip-time (RTT).
.1.3.6.1.2.1.80.1.3.1.7,DISMAN-PING-MIB::pingResultsProbeResponses,Gauge32,read-only,,current,,Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received.
.1.3.6.1.2.1.80.1.3.1.8,DISMAN-PING-MIB::pingResultsSentProbes,Gauge32,read-only,,current,,The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent.
.1.3.6.1.2.1.80.1.3.1.9,DISMAN-PING-MIB::pingResultsRttSumOfSquares,Unsigned32,read-only,,current,,This object contains the sum of the squares for all ping responses received. Its purpose is to enable standard deviation calculation. The value of this object MUST be reported as 0 when no ping responses have been received.
.1.3.6.1.2.1.80.1.3.1.10,DISMAN-PING-MIB::pingResultsLastGoodProbe,OCTET,read-only,,current,,Date and time when the last response was received for a probe.
.1.3.6.1.2.1.80.1.4,DISMAN-PING-MIB::pingProbeHistoryTable,,not-accessible,,current,,Defines a table for storing the results of ping operations. The number of entries in this table is limited per entry in the pingCtlTable by the value of the corresponding pingCtlMaxRows object. An entry in this table is created when the result of a ping probe is determined. The initial 2 instance identifier index values identify the pingCtlEntry that a probe result (pingProbeHistoryEntry) belongs to. An entry is removed from this table when its corresponding pingCtlEntry is deleted. An implementation of this MIB will remove the oldest entry in the pingProbeHistoryTable of the corresponding entry in the pingCtlTable to allow the addition of an new entry once the number of rows in the pingProbeHistoryTable reaches the value specified by pingCtlMaxRows for the corresponding entry in the pingCtlTable.
.1.3.6.1.2.1.80.1.4.1,DISMAN-PING-MIB::pingProbeHistoryEntry,,not-accessible,pingCtlOwnerIndex:pingCtlTestName:pingProbeHistoryIndex,current,,Defines an entry in the pingProbeHistoryTable. The first two index elements identify the pingCtlEntry that a pingProbeHistoryEntry belongs to. The third index element selects a single probe result.
.1.3.6.1.2.1.80.1.4.1.1,DISMAN-PING-MIB::pingProbeHistoryIndex,Unsigned32,not-accessible,,current,,An entry in this table is created when the result of a ping probe is determined. The initial 2 instance identifier index values identify the pingCtlEntry that a probe result (pingProbeHistoryEntry) belongs to. An implementation MUST start assigning pingProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value as defined by the limit of this object ('ffffffff'h).
.1.3.6.1.2.1.80.1.4.1.2,DISMAN-PING-MIB::pingProbeHistoryResponse,Unsigned32,read-only,,current,,The amount of time measured in milliseconds from when a probe was sent to when its response was received or when it timed out. The value of this object is reported as 0 when it is not possible to transmit a probe.
.1.3.6.1.2.1.80.1.4.1.3,DISMAN-PING-MIB::pingProbeHistoryStatus,INTEGER,read-only,,current,responseReceived(1):unknown(2):internalError(3):requestTimedOut(4):unknownDestinationAddress(5):noRouteToTarget(6):interfaceInactiveToTarget(7):arpFailure(8):maxConcurrentLimitReached(9):unableToResolveDnsName(10):invalidHostAddress(11),The result of a particular probe done by a remote host.
.1.3.6.1.2.1.80.1.4.1.4,DISMAN-PING-MIB::pingProbeHistoryLastRC,Integer32,read-only,,current,,The last implementation-method-specific reply code received. If the ICMP Echo capability is being used, then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP codes are maintained by IANA. Standardized ICMP codes are listed at http://www.iana.org/assignments/icmp-parameters. The ICMPv6 codes are listed at http://www.iana.org/assignments/icmpv6-parameters.
.1.3.6.1.2.1.80.1.4.1.5,DISMAN-PING-MIB::pingProbeHistoryTime,OCTET,read-only,,current,,Timestamp for when this probe result was determined.
.1.3.6.1.2.1.80.2,DISMAN-PING-MIB::pingConformance,,,,,,
.1.3.6.1.2.1.80.2.1,DISMAN-PING-MIB::pingCompliances,,,,,,
.1.3.6.1.2.1.80.2.1.1,DISMAN-PING-MIB::pingCompliance,,,,,,The compliance statement for the DISMAN-PING-MIB. This compliance statement has been deprecated because the group pingGroup and the pingTimeStampGroup have been split and deprecated. The pingFullCompliance statement is semantically identical to the deprecated pingCompliance statement.
.1.3.6.1.2.1.80.2.1.2,DISMAN-PING-MIB::pingFullCompliance,,,,,,The compliance statement for SNMP entities that fully implement the DISMAN-PING-MIB.
.1.3.6.1.2.1.80.2.1.3,DISMAN-PING-MIB::pingMinimumCompliance,,,,,,The minimum compliance statement for SNMP entities that implement the minimal subset of the DISMAN-PING-MIB. Implementors might choose this subset for small devices with limited resources.
.1.3.6.1.2.1.80.2.2,DISMAN-PING-MIB::pingGroups,,,,,,
.1.3.6.1.2.1.80.2.2.1,DISMAN-PING-MIB::pingGroup,,,,,,The group of objects that constitute the remote ping capability.
.1.3.6.1.2.1.80.2.2.2,DISMAN-PING-MIB::pingTimeStampGroup,,,,,,The group of DateAndTime objects.
.1.3.6.1.2.1.80.2.2.3,DISMAN-PING-MIB::pingNotificationsGroup,,,,,,The notification that are required to be supported by implementations of this MIB.
.1.3.6.1.2.1.80.2.2.4,DISMAN-PING-MIB::pingMinimumGroup,,,,,,The group of objects that constitute the remote ping capability.
.1.3.6.1.2.1.80.2.2.5,DISMAN-PING-MIB::pingCtlRowStatusGroup,,,,,,The RowStatus object of the pingCtlTable.
.1.3.6.1.2.1.80.2.2.6,DISMAN-PING-MIB::pingHistoryGroup,,,,,,The group of objects that constitute the history capability.
.1.3.6.1.2.1.80.3,DISMAN-PING-MIB::pingImplementationTypeDomains,,,,,,
.1.3.6.1.2.1.80.3.1,DISMAN-PING-MIB::pingIcmpEcho,,,,,,Indicates that an implementation is using the Internet Control Message Protocol (ICMP) 'ECHO' facility.
.1.3.6.1.2.1.80.3.2,DISMAN-PING-MIB::pingUdpEcho,,,,,,Indicates that an implementation is using the UDP echo port (7).
.1.3.6.1.2.1.80.3.3,DISMAN-PING-MIB::pingSnmpQuery,,,,,,Indicates that an implementation is using an SNMP query to calculate a round trip time.
.1.3.6.1.2.1.80.3.4,DISMAN-PING-MIB::pingTcpConnectionAttempt,,,,,,Indicates that an implementation is attempting to connect to a TCP port in order to calculate a round trip time.
.1.3.6.1.2.1.81,DISMAN-TRACEROUTE-MIB::traceRouteMIB,,,,,,The Traceroute MIB (DISMAN-TRACEROUTE-MIB) provides access to the traceroute capability at a remote host. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices.
.1.3.6.1.2.1.81.0,DISMAN-TRACEROUTE-MIB::traceRouteNotifications,,,,,,
.1.3.6.1.2.1.81.0.1,DISMAN-TRACEROUTE-MIB::traceRoutePathChange,,,,,,The path to a target has changed.
.1.3.6.1.2.1.81.0.2,DISMAN-TRACEROUTE-MIB::traceRouteTestFailed,,,,,,Could not determine the path to a target.
.1.3.6.1.2.1.81.0.3,DISMAN-TRACEROUTE-MIB::traceRouteTestCompleted,,,,,,The path to a target has just been determined.
.1.3.6.1.2.1.81.1,DISMAN-TRACEROUTE-MIB::traceRouteObjects,,,,,,
.1.3.6.1.2.1.81.1.1,DISMAN-TRACEROUTE-MIB::traceRouteMaxConcurrentRequests,Unsigned32,read-write,,current,,The maximum number of concurrent active traceroute requests that are allowed within an agent implementation. A value of 0 for this object implies that there is no limit for the number of concurrent active requests in effect. The limit applies only to new requests being activated. When a new value is set, the agent will continue processing all the requests already active, even if their number exceeds the limit just imposed.
.1.3.6.1.2.1.81.1.2,DISMAN-TRACEROUTE-MIB::traceRouteCtlTable,,not-accessible,,current,,Defines the Remote Operations Traceroute Control Table for providing the capability of invoking traceroute from a remote host. The results of traceroute operations can be stored in the traceRouteResultsTable, traceRouteProbeHistoryTable, and the traceRouteHopsTable.
.1.3.6.1.2.1.81.1.2.1,DISMAN-TRACEROUTE-MIB::traceRouteCtlEntry,,not-accessible,traceRouteCtlOwnerIndex:traceRouteCtlTestName,current,,Defines an entry in the traceRouteCtlTable. The first index element, traceRouteCtlOwnerIndex, is of type SnmpAdminString, a textual convention that allows for use of the SNMPv3 View-Based Access Control Model (RFC 3415, VACM) and that allows a management application to identify its entries. The second index, traceRouteCtlTestName (also an SnmpAdminString), enables the same management application to have multiple requests outstanding.
.1.3.6.1.2.1.81.1.2.1.1,DISMAN-TRACEROUTE-MIB::traceRouteCtlOwnerIndex,OCTET,not-accessible,,current,,To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 3415, VACM) for tables in which multiple users may need to create or modify entries independently, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString and can thus be trivially mapped to a securityName or groupName defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy, all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible.
.1.3.6.1.2.1.81.1.2.1.2,DISMAN-TRACEROUTE-MIB::traceRouteCtlTestName,OCTET,not-accessible,,current,,The name of a traceroute test. This is locally unique, within the scope of a traceRouteCtlOwnerIndex.
.1.3.6.1.2.1.81.1.2.1.3,DISMAN-TRACEROUTE-MIB::traceRouteCtlTargetAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Specifies the type of host address to be used on the traceroute request at the remote host.
.1.3.6.1.2.1.81.1.2.1.4,DISMAN-TRACEROUTE-MIB::traceRouteCtlTargetAddress,OCTET,read-create,,current,,Specifies the host address used on the traceroute request at the remote host. The host address type can be determined by examining the value of the corresponding traceRouteCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding traceRouteCtlEntry to active(1) via traceRouteCtlRowStatus.
.1.3.6.1.2.1.81.1.2.1.5,DISMAN-TRACEROUTE-MIB::traceRouteCtlByPassRouteTable,INTEGER,read-create,,current,true(1):false(2),The purpose of this object is to enable optional bypassing the route table. If enabled, the remote host will bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly attached network, an error is returned. This option can be used to perform the traceroute operation to a local host through an interface that has no route defined (e.g., after the interface was dropped by the routing daemon at the host).
.1.3.6.1.2.1.81.1.2.1.6,DISMAN-TRACEROUTE-MIB::traceRouteCtlDataSize,Unsigned32,read-create,,current,,Specifies the size of the data portion of a traceroute request, in octets. If the RECOMMENDED traceroute method (UDP datagrams as probes) is used, then the value contained in this object MUST be applied. If another traceroute method is used for which the specified size is not appropriate, then the implementation SHOULD use whatever size (appropriate to the method) is closest to the specified size. The maximum value for this object was computed by subtracting the smallest possible IP header size of 20 octets (IPv4 header with no options) and the UDP header size of 8 octets from the maximum IP packet size. An IP packet has a maximum size of 65535 octets (excluding IPv6 Jumbograms).
.1.3.6.1.2.1.81.1.2.1.7,DISMAN-TRACEROUTE-MIB::traceRouteCtlTimeOut,Unsigned32,read-create,,current,,Specifies the time-out value, in seconds, for a traceroute request.
.1.3.6.1.2.1.81.1.2.1.8,DISMAN-TRACEROUTE-MIB::traceRouteCtlProbesPerHop,Unsigned32,read-create,,current,,Specifies the number of times to reissue a traceroute request with the same time-to-live (TTL) value.
.1.3.6.1.2.1.81.1.2.1.9,DISMAN-TRACEROUTE-MIB::traceRouteCtlPort,Unsigned32,read-create,,current,,Specifies the (initial) UDP port to send the traceroute request to. A port needs to be specified that is not in use at the destination (target) host. The default value for this object is the IANA assigned port, 33434, for the traceroute function.
.1.3.6.1.2.1.81.1.2.1.10,DISMAN-TRACEROUTE-MIB::traceRouteCtlMaxTtl,Unsigned32,read-create,,current,,Specifies the maximum time-to-live value.
.1.3.6.1.2.1.81.1.2.1.11,DISMAN-TRACEROUTE-MIB::traceRouteCtlDSField,Unsigned32,read-create,,current,,Specifies the value to store in the Type of Service (TOS) octet in the IPv4 header or in the Traffic Class octet in the IPv6 header, respectively, of the IP packet used to encapsulate the traceroute probe. The octet to be set in the IP header contains the Differentiated Services (DS) Field in the six most significant bits. This option can be used to determine what effect an explicit DS Field setting has on a traceroute response. Not all values are legal or meaningful. A value of 0 means that the function represented by this option is not supported. DS Field usage is often not supported by IP implementations, and not all values are supported. Refer to RFC 2474 and RFC 3260 for guidance on usage of this field.
.1.3.6.1.2.1.81.1.2.1.12,DISMAN-TRACEROUTE-MIB::traceRouteCtlSourceAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Specifies the type of the source address, traceRouteCtlSourceAddress, to be used at a remote host when a traceroute operation is performed.
.1.3.6.1.2.1.81.1.2.1.13,DISMAN-TRACEROUTE-MIB::traceRouteCtlSourceAddress,OCTET,read-create,,current,,Use the specified IP address (which must be given as an IP number, not a hostname) as the source address in outgoing probe packets. On hosts with more than one IP address, this option can be used to select the address to be used. If the IP address is not one of this machine's interface addresses, an error is returned, and nothing is sent. A zero-length octet string value for this object disables source address specification. The address type (InetAddressType) that relates to this object is specified by the corresponding value of traceRouteCtlSourceAddressType.
.1.3.6.1.2.1.81.1.2.1.14,DISMAN-TRACEROUTE-MIB::traceRouteCtlIfIndex,Integer32,read-create,,current,,Setting this object to an interface's ifIndex prior to starting a remote traceroute operation directs the traceroute probes to be transmitted over the specified interface. A value of zero for this object implies that this option is not enabled.
.1.3.6.1.2.1.81.1.2.1.15,DISMAN-TRACEROUTE-MIB::traceRouteCtlMiscOptions,OCTET,read-create,,current,,Enables an application to specify implementation-dependent options.
.1.3.6.1.2.1.81.1.2.1.16,DISMAN-TRACEROUTE-MIB::traceRouteCtlMaxFailures,Unsigned32,read-create,,current,,The value of this object indicates the maximum number of consecutive timeouts allowed before a remote traceroute request is terminated. A value of either 255 (maximum hop count/possible TTL value) or 0 indicates that the function of terminating a remote traceroute request when a specific number of consecutive timeouts are detected is disabled.
.1.3.6.1.2.1.81.1.2.1.17,DISMAN-TRACEROUTE-MIB::traceRouteCtlDontFragment,INTEGER,read-create,,current,true(1):false(2),This object enables setting of the don't fragment flag (DF) in the IP header for a probe. Use of this object enables a manual PATH MTU test is performed.
.1.3.6.1.2.1.81.1.2.1.18,DISMAN-TRACEROUTE-MIB::traceRouteCtlInitialTtl,Unsigned32,read-create,,current,,The value of this object specifies the initial TTL value to use. This enables bypassing the initial (often well known) portion of a path.
.1.3.6.1.2.1.81.1.2.1.19,DISMAN-TRACEROUTE-MIB::traceRouteCtlFrequency,Unsigned32,read-create,,current,,The number of seconds to wait before repeating a traceroute test, as defined by the value of the various objects in the corresponding row. After a single test is completed the number of seconds as defined by the value of traceRouteCtlFrequency MUST elapse before the next traceroute test is started. A value of 0 for this object implies that the test as defined by the corresponding entry will not be repeated.
.1.3.6.1.2.1.81.1.2.1.20,DISMAN-TRACEROUTE-MIB::traceRouteCtlStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.81.1.2.1.21,DISMAN-TRACEROUTE-MIB::traceRouteCtlAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),Reflects the desired state that an traceRouteCtlEntry should be in: enabled(1) - Attempt to activate the test as defined by this traceRouteCtlEntry. disabled(2) - Deactivate the test as defined by this traceRouteCtlEntry. Refer to the corresponding traceRouteResultsOperStatus to determine the operational state of the test defined by this entry.
.1.3.6.1.2.1.81.1.2.1.22,DISMAN-TRACEROUTE-MIB::traceRouteCtlDescr,OCTET,read-create,,current,,The purpose of this object is to provide a descriptive name of the remote traceroute test.
.1.3.6.1.2.1.81.1.2.1.23,DISMAN-TRACEROUTE-MIB::traceRouteCtlMaxRows,Unsigned32,read-create,,current,,The maximum number of corresponding entries allowed in the traceRouteProbeHistoryTable. An implementation of this MIB will remove the oldest corresponding entry in the traceRouteProbeHistoryTable to allow the addition of an new entry once the number of corresponding rows in the traceRouteProbeHistoryTable reaches this value. Old entries are not removed when a new test is started. Entries are added to the traceRouteProbeHistoryTable until traceRouteCtlMaxRows is reached before entries begin to be removed. A value of 0 for this object disables creation of traceRouteProbeHistoryTable entries.
.1.3.6.1.2.1.81.1.2.1.24,DISMAN-TRACEROUTE-MIB::traceRouteCtlTrapGeneration,BITS,read-create,,current,pathChange(0):testFailure(1):testCompletion(2),The value of this object determines when and whether to generate a notification for this entry: pathChange(0) - Generate a traceRoutePathChange notification when the current path varies from a previously determined path. testFailure(1) - Generate a traceRouteTestFailed notification when the full path to a target can't be determined. testCompletion(2) - Generate a traceRouteTestCompleted notification when the path to a target has been determined. The value of this object defaults to an empty set, indicating that none of the above options has been selected.
.1.3.6.1.2.1.81.1.2.1.25,DISMAN-TRACEROUTE-MIB::traceRouteCtlCreateHopsEntries,INTEGER,read-create,,current,true(1):false(2),The current path for a traceroute test is kept in the traceRouteHopsTable on a per-hop basis when the value of this object is true(1).
.1.3.6.1.2.1.81.1.2.1.26,DISMAN-TRACEROUTE-MIB::traceRouteCtlType,OBJECT,read-create,,current,,The value of this object is used either to report or to select the implementation method to be used for performing a traceroute operation. The value of this object may be selected from traceRouteImplementationTypeDomains. Additional implementation types should be allocated as required by implementers of the DISMAN-TRACEROUTE-MIB under their enterprise specific registration point, not beneath traceRouteImplementationTypeDomains.
.1.3.6.1.2.1.81.1.2.1.27,DISMAN-TRACEROUTE-MIB::traceRouteCtlRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the traceRouteCtlTable. Deletion of an entry in this table results in a deletion of all corresponding (same traceRouteCtlOwnerIndex and traceRouteCtlTestName index values) traceRouteResultsTable, traceRouteProbeHistoryTable, and traceRouteHopsTable entries. A value MUST be specified for traceRouteCtlTargetAddress prior to acceptance of a transition to active(1) state. When a value for pingCtlTargetAddress is set, the value of object pingCtlRowStatus changes from notReady(3) to notInService(2). Activation of a remote traceroute operation is controlled via traceRouteCtlAdminStatus, and not by transitioning of this object's value to active(1). Transitions in and out of active(1) state are not allowed while an entry's traceRouteResultsOperStatus is active(1), with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active traceroute operation. The operational state of an traceroute operation can be determined by examination of the corresponding traceRouteResultsOperStatus object.
.1.3.6.1.2.1.81.1.3,DISMAN-TRACEROUTE-MIB::traceRouteResultsTable,,not-accessible,,current,,Defines the Remote Operations Traceroute Results Table for keeping track of the status of a traceRouteCtlEntry. An entry is added to the traceRouteResultsTable when an traceRouteCtlEntry is started by successful transition of its traceRouteCtlAdminStatus object to enabled(1). If the object traceRouteCtlAdminStatus already has the value enabled(1), and if the corresponding traceRouteResultsOperStatus object has the value completed(3), then successfully writing enabled(1) to the object traceRouteCtlAdminStatus re-initializes the already existing entry in the traceRouteResultsTable. The values of objects in the re-initialized entry are the same as the values of objects in a new entry would be. An entry is removed from the traceRouteResultsTable when its corresponding traceRouteCtlEntry is deleted.
.1.3.6.1.2.1.81.1.3.1,DISMAN-TRACEROUTE-MIB::traceRouteResultsEntry,,not-accessible,traceRouteCtlOwnerIndex:traceRouteCtlTestName,current,,Defines an entry in the traceRouteResultsTable. The traceRouteResultsTable has the same indexing as the traceRouteCtlTable so that a traceRouteResultsEntry corresponds to the traceRouteCtlEntry that caused it to be created.
.1.3.6.1.2.1.81.1.3.1.1,DISMAN-TRACEROUTE-MIB::traceRouteResultsOperStatus,INTEGER,read-only,,current,enabled(1):disabled(2):completed(3),Reflects the operational state of an traceRouteCtlEntry: enabled(1) - Test is active. disabled(2) - Test has stopped. completed(3) - Test is completed.
.1.3.6.1.2.1.81.1.3.1.2,DISMAN-TRACEROUTE-MIB::traceRouteResultsCurHopCount,Gauge32,read-only,,current,,Reflects the current TTL value (from 1 to 255) for a remote traceroute operation. Maximum TTL value is determined by traceRouteCtlMaxTtl.
.1.3.6.1.2.1.81.1.3.1.3,DISMAN-TRACEROUTE-MIB::traceRouteResultsCurProbeCount,Gauge32,read-only,,current,,Reflects the current probe count (1..10) for a remote traceroute operation. The maximum probe count is determined by traceRouteCtlProbesPerHop.
.1.3.6.1.2.1.81.1.3.1.4,DISMAN-TRACEROUTE-MIB::traceRouteResultsIpTgtAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the type of address stored in the corresponding traceRouteResultsIpTgtAddr object.
.1.3.6.1.2.1.81.1.3.1.5,DISMAN-TRACEROUTE-MIB::traceRouteResultsIpTgtAddr,OCTET,read-only,,current,,This object reports the IP address associated with a traceRouteCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero-length octet string when a DNS name is not specified or when a specified DNS name fails to resolve.
.1.3.6.1.2.1.81.1.3.1.6,DISMAN-TRACEROUTE-MIB::traceRouteResultsTestAttempts,Gauge32,read-only,,current,,The current number of attempts to determine a path to a target. The value of this object MUST be started at 0.
.1.3.6.1.2.1.81.1.3.1.7,DISMAN-TRACEROUTE-MIB::traceRouteResultsTestSuccesses,Gauge32,read-only,,current,,The current number of attempts to determine a path to a target that have succeeded. The value of this object MUST be reported as 0 when no attempts have succeeded.
.1.3.6.1.2.1.81.1.3.1.8,DISMAN-TRACEROUTE-MIB::traceRouteResultsLastGoodPath,OCTET,read-only,,current,,The date and time when the last complete path was determined. A path is complete if responses were received or timeout occurred for each hop on the path; i.e., for each TTL value from the value of the corresponding traceRouteCtlInitialTtl object up to the end of the path or (if no reply from the target IP address was received) up to the value of the corresponding traceRouteCtlMaxTtl object.
.1.3.6.1.2.1.81.1.4,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryTable,,not-accessible,,current,,Defines the Remote Operations Traceroute Results Table for storing the results of a traceroute operation. An implementation of this MIB will remove the oldest entry in the traceRouteProbeHistoryTable of the corresponding entry in the traceRouteCtlTable to allow the addition of a new entry once the number of rows in the traceRouteProbeHistoryTable reaches the value specified by traceRouteCtlMaxRows for the corresponding entry in the traceRouteCtlTable.
.1.3.6.1.2.1.81.1.4.1,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryEntry,,not-accessible,traceRouteCtlOwnerIndex:traceRouteCtlTestName:traceRouteProbeHistoryIndex:traceRouteProbeHistoryHopIndex:traceRouteProbeHistoryProbeIndex,current,,Defines a table for storing the results of a traceroute operation. Entries in this table are limited by the value of the corresponding traceRouteCtlMaxRows object. The first two index elements identify the traceRouteCtlEntry that a traceRouteProbeHistoryEntry belongs to. The third index element selects a single traceroute operation result. The fourth and fifth indexes select the hop and the probe for a particular traceroute operation.
.1.3.6.1.2.1.81.1.4.1.1,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryIndex,Unsigned32,not-accessible,,current,,An entry in this table is created when the result of a traceroute probe is determined. The initial 2 instance identifier index values identify the traceRouteCtlEntry that a probe result (traceRouteProbeHistoryEntry) belongs to. An entry is removed from this table when its corresponding traceRouteCtlEntry is deleted. An implementation MUST start assigning traceRouteProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value, as defined by the limit of this object ('ffffffff'h).
.1.3.6.1.2.1.81.1.4.1.2,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryHopIndex,Unsigned32,not-accessible,,current,,Indicates which hop in a traceroute path the probe's results are for. The value of this object is initially determined by the value of traceRouteCtlInitialTtl.
.1.3.6.1.2.1.81.1.4.1.3,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryProbeIndex,Unsigned32,not-accessible,,current,,Indicates the index of a probe for a particular hop in a traceroute path. The number of probes per hop is determined by the value of the corresponding traceRouteCtlProbesPerHop object.
.1.3.6.1.2.1.81.1.4.1.4,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryHAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This objects indicates the type of address stored in the corresponding traceRouteProbeHistoryHAddr object.
.1.3.6.1.2.1.81.1.4.1.5,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryHAddr,OCTET,read-only,,current,,The address of a hop in a traceroute path. This object is not allowed to be a DNS name. The value of the corresponding object, traceRouteProbeHistoryHAddrType, indicates this object's IP address type.
.1.3.6.1.2.1.81.1.4.1.6,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryResponse,Unsigned32,read-only,,current,,The amount of time measured in milliseconds from when a probe was sent to when its response was received or when it timed out. The value of this object is reported as 0 when it is not possible to transmit a probe.
.1.3.6.1.2.1.81.1.4.1.7,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryStatus,INTEGER,read-only,,current,responseReceived(1):unknown(2):internalError(3):requestTimedOut(4):unknownDestinationAddress(5):noRouteToTarget(6):interfaceInactiveToTarget(7):arpFailure(8):maxConcurrentLimitReached(9):unableToResolveDnsName(10):invalidHostAddress(11),The result of a traceroute operation made by a remote host for a particular probe.
.1.3.6.1.2.1.81.1.4.1.8,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryLastRC,Integer32,read-only,,current,,The last implementation-method-specific reply code received. Traceroute is usually implemented by transmitting a series of probe packets with increasing time-to-live values. A probe packet is a UDP datagram encapsulated into an IP packet. Each hop in a path to the target (destination) host rejects the probe packets (probe's TTL too small, ICMP reply) until either the maximum TTL is exceeded or the target host is received.
.1.3.6.1.2.1.81.1.4.1.9,DISMAN-TRACEROUTE-MIB::traceRouteProbeHistoryTime,OCTET,read-only,,current,,Timestamp for when this probe's results were determined.
.1.3.6.1.2.1.81.1.5,DISMAN-TRACEROUTE-MIB::traceRouteHopsTable,,not-accessible,,current,,Defines the Remote Operations Traceroute Hop Table for keeping track of the results of traceroute tests on a per-hop basis.
.1.3.6.1.2.1.81.1.5.1,DISMAN-TRACEROUTE-MIB::traceRouteHopsEntry,,not-accessible,traceRouteCtlOwnerIndex:traceRouteCtlTestName:traceRouteHopsHopIndex,current,,Defines an entry in the traceRouteHopsTable. The first two index elements identify the traceRouteCtlEntry that a traceRouteHopsEntry belongs to. The third index element, traceRouteHopsHopIndex, selects a hop in a traceroute path.
.1.3.6.1.2.1.81.1.5.1.1,DISMAN-TRACEROUTE-MIB::traceRouteHopsHopIndex,Unsigned32,not-accessible,,current,,Specifies the hop index for a traceroute hop. Values for this object with respect to the same traceRouteCtlOwnerIndex and traceRouteCtlTestName MUST start at 1 and be given increasing values for subsequent hops. The value of traceRouteHopsHopIndex is not necessarily the number of the hop on the traced path. The traceRouteHopsTable keeps the current traceroute path per traceRouteCtlEntry if enabled by setting the corresponding traceRouteCtlCreateHopsEntries to true(1). All hops (traceRouteHopsTable entries) in a traceroute path MUST be updated at the same time when a traceroute operation is completed. Care needs to be applied when a path either changes or can't be determined. The initial portion of the path, up to the first hop change, MUST retain the same traceRouteHopsHopIndex values. The remaining portion of the path SHOULD be assigned new traceRouteHopsHopIndex values.
.1.3.6.1.2.1.81.1.5.1.2,DISMAN-TRACEROUTE-MIB::traceRouteHopsIpTgtAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the type of address stored in the corresponding traceRouteHopsIpTgtAddress object.
.1.3.6.1.2.1.81.1.5.1.3,DISMAN-TRACEROUTE-MIB::traceRouteHopsIpTgtAddress,OCTET,read-only,,current,,This object reports the IP address associated with the hop. A value for this object should be reported as a numeric IP address, not as a DNS name. The address type (InetAddressType) that relates to this object is specified by the corresponding value of pingCtlSourceAddressType.
.1.3.6.1.2.1.81.1.5.1.4,DISMAN-TRACEROUTE-MIB::traceRouteHopsMinRtt,Unsigned32,read-only,,current,,The minimum traceroute round-trip-time (RTT) received for this hop. A value of 0 for this object implies that no RTT has been received.
.1.3.6.1.2.1.81.1.5.1.5,DISMAN-TRACEROUTE-MIB::traceRouteHopsMaxRtt,Unsigned32,read-only,,current,,The maximum traceroute round-trip-time (RTT) received for this hop. A value of 0 for this object implies that no RTT has been received.
.1.3.6.1.2.1.81.1.5.1.6,DISMAN-TRACEROUTE-MIB::traceRouteHopsAverageRtt,Unsigned32,read-only,,current,,The current average traceroute round-trip-time (RTT) for this hop.
.1.3.6.1.2.1.81.1.5.1.7,DISMAN-TRACEROUTE-MIB::traceRouteHopsRttSumOfSquares,Unsigned32,read-only,,current,,This object contains the sum of the squares of all round-trip-times received for this hop. Its purpose is to enable standard deviation calculation.
.1.3.6.1.2.1.81.1.5.1.8,DISMAN-TRACEROUTE-MIB::traceRouteHopsSentProbes,Unsigned32,read-only,,current,,The value of this object reflects the number of probes sent for this hop during this traceroute test. The value of this object should start at 0.
.1.3.6.1.2.1.81.1.5.1.9,DISMAN-TRACEROUTE-MIB::traceRouteHopsProbeResponses,Unsigned32,read-only,,current,,Number of responses received for this hop during this traceroute test. This value of this object should start at 0.
.1.3.6.1.2.1.81.1.5.1.10,DISMAN-TRACEROUTE-MIB::traceRouteHopsLastGoodProbe,OCTET,read-only,,current,,Date and time at which the last response was received for a probe for this hop during this traceroute test.
.1.3.6.1.2.1.81.2,DISMAN-TRACEROUTE-MIB::traceRouteConformance,,,,,,
.1.3.6.1.2.1.81.2.1,DISMAN-TRACEROUTE-MIB::traceRouteCompliances,,,,,,
.1.3.6.1.2.1.81.2.1.1,DISMAN-TRACEROUTE-MIB::traceRouteCompliance,,,,,,The compliance statement for the DISMAN-TRACEROUTE-MIB. This compliance statement has been deprecated because the traceRouteGroup and the traceRouteTimeStampGroup have been split and deprecated. The traceRouteFullCompliance is semantically identical to the deprecated traceRouteCompliance statement.
.1.3.6.1.2.1.81.2.1.2,DISMAN-TRACEROUTE-MIB::traceRouteFullCompliance,,,,,,The compliance statement for SNMP entities that fully implement the DISMAN-TRACEROUTE-MIB.
.1.3.6.1.2.1.81.2.1.3,DISMAN-TRACEROUTE-MIB::traceRouteMinimumCompliance,,,,,,The minimum compliance statement for SNMP entities which implement the minimal subset of the DISMAN-TRACEROUTE-MIB. Implementors might choose this subset for small devices with limited resources.
.1.3.6.1.2.1.81.2.2,DISMAN-TRACEROUTE-MIB::traceRouteGroups,,,,,,
.1.3.6.1.2.1.81.2.2.1,DISMAN-TRACEROUTE-MIB::traceRouteGroup,,,,,,The group of objects that constitute the remote traceroute operation.
.1.3.6.1.2.1.81.2.2.2,DISMAN-TRACEROUTE-MIB::traceRouteTimeStampGroup,,,,,,The group of DateAndTime objects.
.1.3.6.1.2.1.81.2.2.3,DISMAN-TRACEROUTE-MIB::traceRouteNotificationsGroup,,,,,,The notifications that are required to be supported by implementations of this MIB.
.1.3.6.1.2.1.81.2.2.4,DISMAN-TRACEROUTE-MIB::traceRouteHopsTableGroup,,,,,,The group of objects that constitute the traceRouteHopsTable.
.1.3.6.1.2.1.81.2.2.5,DISMAN-TRACEROUTE-MIB::traceRouteMinimumGroup,,,,,,The group of objects that constitute the remote traceroute operation.
.1.3.6.1.2.1.81.2.2.6,DISMAN-TRACEROUTE-MIB::traceRouteCtlRowStatusGroup,,,,,,The RowStatus object of the traceRouteCtlTable.
.1.3.6.1.2.1.81.2.2.7,DISMAN-TRACEROUTE-MIB::traceRouteHistoryGroup,,,,,,The group of objects that constitute the history capability.
.1.3.6.1.2.1.81.3,DISMAN-TRACEROUTE-MIB::traceRouteImplementationTypeDomains,,,,,,
.1.3.6.1.2.1.81.3.1,DISMAN-TRACEROUTE-MIB::traceRouteUsingUdpProbes,,,,,,Indicates that an implementation is using UDP probes to perform the traceroute operation.
.1.3.6.1.2.1.82,DISMAN-NSLOOKUP-MIB::lookupMIB,,,,,,The Lookup MIB (DISMAN-NSLOOKUP-MIB) enables determination of either the name(s) corresponding to a host address or of the address(es) associated with a host name at a remote host. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4560; see the RFC itself for full legal notices.
.1.3.6.1.2.1.82.1,DISMAN-NSLOOKUP-MIB::lookupObjects,,,,,,
.1.3.6.1.2.1.82.1.1,DISMAN-NSLOOKUP-MIB::lookupMaxConcurrentRequests,Unsigned32,read-write,,current,,The maximum number of concurrent active lookup requests that are allowed within an agent implementation. A value of 0 for this object implies that there is no limit for the number of concurrent active requests in effect. The limit applies only to new requests being activated. When a new value is set, the agent will continue processing all the requests already active, even if their number exceed the limit just imposed.
.1.3.6.1.2.1.82.1.2,DISMAN-NSLOOKUP-MIB::lookupPurgeTime,Unsigned32,read-write,,current,,The amount of time to wait before automatically deleting an entry in the lookupCtlTable and any dependent lookupResultsTable entries after the lookup operation represented by a lookupCtlEntry has been completed. A lookupCtEntry is considered complete when its lookupCtlOperStatus object has a value of completed(3). A value of 0 indicates that automatic deletion of entries is disabled.
.1.3.6.1.2.1.82.1.3,DISMAN-NSLOOKUP-MIB::lookupCtlTable,,not-accessible,,current,,Defines the Lookup Control Table for providing the capability of performing a lookup operation for a symbolic host name or for a host address from a remote host.
.1.3.6.1.2.1.82.1.3.1,DISMAN-NSLOOKUP-MIB::lookupCtlEntry,,not-accessible,lookupCtlOwnerIndex:lookupCtlOperationName,current,,Defines an entry in the lookupCtlTable. A lookupCtlEntry is initially indexed by lookupCtlOwnerIndex, which is a type of SnmpAdminString, a textual convention that allows for the use of the SNMPv3 View-Based Access Control Model (RFC 3415, VACM) and that also allows a management application to identify its entries. The second index element, lookupCtlOperationName, enables the same lookupCtlOwnerIndex entity to have multiple outstanding requests. The value of lookupCtlTargetAddressType determines which lookup function to perform.
.1.3.6.1.2.1.82.1.3.1.1,DISMAN-NSLOOKUP-MIB::lookupCtlOwnerIndex,OCTET,not-accessible,,current,,To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to create or modify entries independently, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString and can thus be trivially mapped to a securityName or groupName defined in VACM, in accordance with a security policy. When used in conjunction with such a security policy all entries in the table belonging to a particular user (or group) will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible.
.1.3.6.1.2.1.82.1.3.1.2,DISMAN-NSLOOKUP-MIB::lookupCtlOperationName,OCTET,not-accessible,,current,,The name of a lookup operation. This is locally unique, within the scope of an lookupCtlOwnerIndex.
.1.3.6.1.2.1.82.1.3.1.3,DISMAN-NSLOOKUP-MIB::lookupCtlTargetAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Specifies the type of address for performing a lookup operation for a symbolic host name or for a host address from a remote host. Specification of dns(16) as the value for this object means that a function such as, for example, getaddrinfo() or gethostbyname() should be performed to return one or more numeric addresses. Use of a value of either ipv4(1) or ipv6(2) means that a functions such as, for example, getnameinfo() or gethostbyaddr() should be used to return the symbolic names associated with a host.
.1.3.6.1.2.1.82.1.3.1.4,DISMAN-NSLOOKUP-MIB::lookupCtlTargetAddress,OCTET,read-create,,current,,Specifies the address used for a resolver lookup at a remote host. The corresponding lookupCtlTargetAddressType objects determines its type, as well as the function that can be requested. A value for this object MUST be set prior to transitioning its corresponding lookupCtlEntry to active(1) via lookupCtlRowStatus.
.1.3.6.1.2.1.82.1.3.1.5,DISMAN-NSLOOKUP-MIB::lookupCtlOperStatus,INTEGER,read-only,,current,enabled(1):notStarted(2):completed(3),Reflects the operational state of an lookupCtlEntry: enabled(1) - Operation is active. notStarted(2) - Operation has not been enabled. completed(3) - Operation has been completed. An operation is automatically enabled(1) when its lookupCtlRowStatus object is transitioned to active(1) status. Until this occurs, lookupCtlOperStatus MUST report a value of notStarted(2). After the lookup operation is completed (success or failure), the value for lookupCtlOperStatus MUST be transitioned to completed(3).
.1.3.6.1.2.1.82.1.3.1.6,DISMAN-NSLOOKUP-MIB::lookupCtlTime,Unsigned32,read-only,,current,,Reports the number of milliseconds that a lookup operation required to be completed at a remote host. Completed means operation failure as well as success.
.1.3.6.1.2.1.82.1.3.1.7,DISMAN-NSLOOKUP-MIB::lookupCtlRc,Integer32,read-only,,current,,The system-specific return code from a lookup operation. All implementations MUST return a value of 0 for this object when the remote lookup operation succeeds. A non-zero value for this objects indicates failure. It is recommended that implementations return the error codes that are generated by the lookup function used.
.1.3.6.1.2.1.82.1.3.1.8,DISMAN-NSLOOKUP-MIB::lookupCtlRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the lookupCtlTable. A remote lookup operation is started when an entry in this table is created via an SNMP set request and the entry is activated. This occurs by setting the value of this object to CreateAndGo(4) during row creation or by setting this object to active(1) after the row is created. A value MUST be specified for lookupCtlTargetAddress prior to the acceptance of a transition to active(1) state. A remote lookup operation starts when its entry first becomes active(1). Transitions in and out of active(1) state have no effect on the operational behavior of a remote lookup operation, with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active remote lookup operation. The operational state of a remote lookup operation can be determined by examination of its lookupCtlOperStatus object.
.1.3.6.1.2.1.82.1.4,DISMAN-NSLOOKUP-MIB::lookupResultsTable,,not-accessible,,current,,Defines the Lookup Results Table for providing the capability of determining the results of a operation at a remote host. One or more entries are added to the lookupResultsTable when a lookup operation, as reflected by an lookupCtlEntry, is completed successfully. All entries related to a successful lookup operation MUST be added to the lookupResultsTable at the same time that the associating lookupCtlOperStatus object is transitioned to completed(2). The number of entries added depends on the results determined for a particular lookup operation. All entries associated with an lookupCtlEntry are removed when the lookupCtlEntry is deleted. A remote host can be multi-homed and have more than one IP address associated with it (returned by lookup function), or it can have more than one symbolic name (returned by lookup function). A function such as, for example, getnameinfo() or gethostbyaddr() is called with a host address as its parameter and is used primarily to determine a symbolic name to associate with the host address. Entries in the lookupResultsTable MUST be made for each host name returned. If the function identifies an 'official host name,' then this symbolic name MUST be assigned a lookupResultsIndex of 1. A function such as, for example, getaddrinfo() or gethostbyname() is called with a symbolic host name and is used primarily to retrieve a host address. The entries MUST be stored in the order that they are retrieved from the lookup function. lookupResultsIndex 1 MUST be assigned to the first entry.
.1.3.6.1.2.1.82.1.4.1,DISMAN-NSLOOKUP-MIB::lookupResultsEntry,,not-accessible,lookupCtlOwnerIndex:lookupCtlOperationName:lookupResultsIndex,current,,Defines an entry in the lookupResultsTable. The first two index elements identify the lookupCtlEntry that a lookupResultsEntry belongs to. The third index element selects a single lookup operation result.
.1.3.6.1.2.1.82.1.4.1.1,DISMAN-NSLOOKUP-MIB::lookupResultsIndex,Unsigned32,not-accessible,,current,,Entries in the lookupResultsTable are created when the result of a lookup operation is determined. Entries MUST be stored in the lookupResultsTable in the order that they are retrieved. Values assigned to lookupResultsIndex MUST start at 1 and increase consecutively.
.1.3.6.1.2.1.82.1.4.1.2,DISMAN-NSLOOKUP-MIB::lookupResultsAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Indicates the type of result of a remote lookup operation. A value of unknown(0) implies either that the operation hasn't been started or that it has failed.
.1.3.6.1.2.1.82.1.4.1.3,DISMAN-NSLOOKUP-MIB::lookupResultsAddress,OCTET,read-only,,current,,Reflects a result for a remote lookup operation as per the value of lookupResultsAddressType. The address type (InetAddressType) that relates to this object is specified by the corresponding value of lookupResultsAddress.
.1.3.6.1.2.1.82.2,DISMAN-NSLOOKUP-MIB::lookupConformance,,,,,,
.1.3.6.1.2.1.82.2.1,DISMAN-NSLOOKUP-MIB::lookupCompliances,,,,,,
.1.3.6.1.2.1.82.2.1.1,DISMAN-NSLOOKUP-MIB::lookupCompliance,,,,,,The compliance statement for SNMP entities that fully implement the DISMAN-NSLOOKUP-MIB.
.1.3.6.1.2.1.82.2.1.2,DISMAN-NSLOOKUP-MIB::lookupMinimumCompliance,,,,,,The minimum compliance statement for SNMP entities that implement the minimal subset of the DISMAN-NSLOOKUP-MIB. Implementors might choose this subset for small devices with limited resources.
.1.3.6.1.2.1.82.2.2,DISMAN-NSLOOKUP-MIB::lookupGroups,,,,,,
.1.3.6.1.2.1.82.2.2.1,DISMAN-NSLOOKUP-MIB::lookupGroup,,,,,,The group of objects that constitute the remote Lookup operation.
.1.3.6.1.2.1.83,IPMROUTE-STD-MIB::ipMRouteStdMIB,,,,,,The MIB module for management of IP Multicast routing, but independent of the specific multicast routing protocol in use.
.1.3.6.1.2.1.83.1,IPMROUTE-STD-MIB::ipMRouteMIBObjects,,,,,,
.1.3.6.1.2.1.83.1.1,IPMROUTE-STD-MIB::ipMRoute,,,,,,
.1.3.6.1.2.1.83.1.1.1,IPMROUTE-STD-MIB::ipMRouteEnable,INTEGER,read-write,,current,enabled(1):disabled(2),The enabled status of IP Multicast routing on this router.
.1.3.6.1.2.1.83.1.1.2,IPMROUTE-STD-MIB::ipMRouteTable,,not-accessible,,current,,The (conceptual) table containing multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to this router.
.1.3.6.1.2.1.83.1.1.2.1,IPMROUTE-STD-MIB::ipMRouteEntry,,not-accessible,ipMRouteGroup:ipMRouteSource:ipMRouteSourceMask,current,,An entry (conceptual row) containing the multicast routing information for IP datagrams from a particular source and addressed to a particular IP multicast group address. Discontinuities in counters in this entry can be detected by observing the value of ipMRouteUpTime.
.1.3.6.1.2.1.83.1.1.2.1.1,IPMROUTE-STD-MIB::ipMRouteGroup,IpAddress,not-accessible,,current,,The IP multicast group address for which this entry contains multicast routing information.
.1.3.6.1.2.1.83.1.1.2.1.2,IPMROUTE-STD-MIB::ipMRouteSource,IpAddress,not-accessible,,current,,The network address which when combined with the corresponding value of ipMRouteSourceMask identifies the sources for which this entry contains multicast routing information.
.1.3.6.1.2.1.83.1.1.2.1.3,IPMROUTE-STD-MIB::ipMRouteSourceMask,IpAddress,not-accessible,,current,,The network mask which when combined with the corresponding value of ipMRouteSource identifies the sources for which this entry contains multicast routing information.
.1.3.6.1.2.1.83.1.1.2.1.4,IPMROUTE-STD-MIB::ipMRouteUpstreamNeighbor,IpAddress,read-only,,current,,The address of the upstream neighbor (e.g., RPF neighbor) from which IP datagrams from these sources to this multicast address are received, or 0.0.0.0 if the upstream neighbor is unknown (e.g., in CBT).
.1.3.6.1.2.1.83.1.1.2.1.5,IPMROUTE-STD-MIB::ipMRouteInIfIndex,Integer32,read-only,,current,,The value of ifIndex for the interface on which IP datagrams sent by these sources to this multicast address are received. A value of 0 indicates that datagrams are not subject to an incoming interface check, but may be accepted on multiple interfaces (e.g., in CBT).
.1.3.6.1.2.1.83.1.1.2.1.6,IPMROUTE-STD-MIB::ipMRouteUpTime,TimeTicks,read-only,,current,,The time since the multicast routing information represented by this entry was learned by the router.
.1.3.6.1.2.1.83.1.1.2.1.7,IPMROUTE-STD-MIB::ipMRouteExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. The value 0 indicates that the entry is not subject to aging.
.1.3.6.1.2.1.83.1.1.2.1.8,IPMROUTE-STD-MIB::ipMRoutePkts,Counter32,read-only,,current,,The number of packets which this router has received from these sources and addressed to this multicast group address.
.1.3.6.1.2.1.83.1.1.2.1.9,IPMROUTE-STD-MIB::ipMRouteDifferentInIfPackets,Counter32,read-only,,current,,The number of packets which this router has received from these sources and addressed to this multicast group address, which were dropped because they were not received on the interface indicated by ipMRouteInIfIndex. Packets which are not subject to an incoming interface check (e.g., using CBT) are not counted.
.1.3.6.1.2.1.83.1.1.2.1.10,IPMROUTE-STD-MIB::ipMRouteOctets,Counter32,read-only,,current,,The number of octets contained in IP datagrams which were received from these sources and addressed to this multicast group address, and which were forwarded by this router.
.1.3.6.1.2.1.83.1.1.2.1.11,IPMROUTE-STD-MIB::ipMRouteProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The multicast routing protocol via which this multicast forwarding entry was learned.
.1.3.6.1.2.1.83.1.1.2.1.12,IPMROUTE-STD-MIB::ipMRouteRtProto,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing mechanism via which the route used to find the upstream or parent interface for this multicast forwarding entry was learned. Inclusion of values for routing protocols is not intended to imply that those protocols need be supported.
.1.3.6.1.2.1.83.1.1.2.1.13,IPMROUTE-STD-MIB::ipMRouteRtAddress,IpAddress,read-only,,current,,The address portion of the route used to find the upstream or parent interface for this multicast forwarding entry.
.1.3.6.1.2.1.83.1.1.2.1.14,IPMROUTE-STD-MIB::ipMRouteRtMask,IpAddress,read-only,,current,,The mask associated with the route used to find the upstream or parent interface for this multicast forwarding entry.
.1.3.6.1.2.1.83.1.1.2.1.15,IPMROUTE-STD-MIB::ipMRouteRtType,INTEGER,read-only,,current,unicast(1):multicast(2),The reason the given route was placed in the (logical) multicast Routing Information Base (RIB). A value of unicast means that the route would normally be placed only in the unicast RIB, but was placed in the multicast RIB (instead or in addition) due to local configuration, such as when running PIM over RIP. A value of multicast means that the route was explicitly added to the multicast RIB by the routing protocol, such as DVMRP or Multiprotocol BGP.
.1.3.6.1.2.1.83.1.1.2.1.16,IPMROUTE-STD-MIB::ipMRouteHCOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams which were received from these sources and addressed to this multicast group address, and which were forwarded by this router. This object is a 64-bit version of ipMRouteOctets.
.1.3.6.1.2.1.83.1.1.3,IPMROUTE-STD-MIB::ipMRouteNextHopTable,,not-accessible,,current,,The (conceptual) table containing information on the next- hops on outgoing interfaces for routing IP multicast datagrams. Each entry is one of a list of next-hops on outgoing interfaces for particular sources sending to a particular multicast group address.
.1.3.6.1.2.1.83.1.1.3.1,IPMROUTE-STD-MIB::ipMRouteNextHopEntry,,not-accessible,ipMRouteNextHopGroup:ipMRouteNextHopSource:ipMRouteNextHopSourceMask:ipMRouteNextHopIfIndex:ipMRouteNextHopAddress,current,,An entry (conceptual row) in the list of next-hops on outgoing interfaces to which IP multicast datagrams from particular sources to a IP multicast group address are routed. Discontinuities in counters in this entry can be detected by observing the value of ipMRouteUpTime.
.1.3.6.1.2.1.83.1.1.3.1.1,IPMROUTE-STD-MIB::ipMRouteNextHopGroup,IpAddress,not-accessible,,current,,The IP multicast group for which this entry specifies a next-hop on an outgoing interface.
.1.3.6.1.2.1.83.1.1.3.1.2,IPMROUTE-STD-MIB::ipMRouteNextHopSource,IpAddress,not-accessible,,current,,The network address which when combined with the corresponding value of ipMRouteNextHopSourceMask identifies the sources for which this entry specifies a next-hop on an outgoing interface.
.1.3.6.1.2.1.83.1.1.3.1.3,IPMROUTE-STD-MIB::ipMRouteNextHopSourceMask,IpAddress,not-accessible,,current,,The network mask which when combined with the corresponding value of ipMRouteNextHopSource identifies the sources for which this entry specifies a next-hop on an outgoing interface.
.1.3.6.1.2.1.83.1.1.3.1.4,IPMROUTE-STD-MIB::ipMRouteNextHopIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for the outgoing interface for this next-hop.
.1.3.6.1.2.1.83.1.1.3.1.5,IPMROUTE-STD-MIB::ipMRouteNextHopAddress,IpAddress,not-accessible,,current,,The address of the next-hop specific to this entry. For most interfaces, this is identical to ipMRouteNextHopGroup. NBMA interfaces, however, may have multiple next-hop addresses out a single outgoing interface.
.1.3.6.1.2.1.83.1.1.3.1.6,IPMROUTE-STD-MIB::ipMRouteNextHopState,INTEGER,read-only,,current,pruned(1):forwarding(2),An indication of whether the outgoing interface and next- hop represented by this entry is currently being used to forward IP datagrams. The value 'forwarding' indicates it is currently being used; the value 'pruned' indicates it is not.
.1.3.6.1.2.1.83.1.1.3.1.7,IPMROUTE-STD-MIB::ipMRouteNextHopUpTime,TimeTicks,read-only,,current,,The time since the multicast routing information represented by this entry was learned by the router.
.1.3.6.1.2.1.83.1.1.3.1.8,IPMROUTE-STD-MIB::ipMRouteNextHopExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. If ipMRouteNextHopState is pruned(1), the remaining time until the prune expires and the state reverts to forwarding(2). Otherwise, the remaining time until this entry is removed from the table. The time remaining may be copied from ipMRouteExpiryTime if the protocol in use for this entry does not specify next-hop timers. The value 0 indicates that the entry is not subject to aging.
.1.3.6.1.2.1.83.1.1.3.1.9,IPMROUTE-STD-MIB::ipMRouteNextHopClosestMemberHops,Integer32,read-only,,current,,The minimum number of hops between this router and any member of this IP multicast group reached via this next-hop on this outgoing interface. Any IP multicast datagrams for the group which have a TTL less than this number of hops will not be forwarded to this next-hop.
.1.3.6.1.2.1.83.1.1.3.1.10,IPMROUTE-STD-MIB::ipMRouteNextHopProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The routing mechanism via which this next-hop was learned.
.1.3.6.1.2.1.83.1.1.3.1.11,IPMROUTE-STD-MIB::ipMRouteNextHopPkts,Counter32,read-only,,current,,The number of packets which have been forwarded using this route.
.1.3.6.1.2.1.83.1.1.4,IPMROUTE-STD-MIB::ipMRouteInterfaceTable,,not-accessible,,current,,The (conceptual) table containing multicast routing information specific to interfaces.
.1.3.6.1.2.1.83.1.1.4.1,IPMROUTE-STD-MIB::ipMRouteInterfaceEntry,,not-accessible,ipMRouteInterfaceIfIndex,current,,An entry (conceptual row) containing the multicast routing information for a particular interface.
.1.3.6.1.2.1.83.1.1.4.1.1,IPMROUTE-STD-MIB::ipMRouteInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for which this entry contains information.
.1.3.6.1.2.1.83.1.1.4.1.2,IPMROUTE-STD-MIB::ipMRouteInterfaceTtl,Integer32,read-write,,current,,The datagram TTL threshold for the interface. Any IP multicast datagrams with a TTL less than this threshold will not be forwarded out the interface. The default value of 0 means all multicast packets are forwarded out the interface.
.1.3.6.1.2.1.83.1.1.4.1.3,IPMROUTE-STD-MIB::ipMRouteInterfaceProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The routing protocol running on this interface.
.1.3.6.1.2.1.83.1.1.4.1.4,IPMROUTE-STD-MIB::ipMRouteInterfaceRateLimit,Integer32,read-write,,current,,The rate-limit, in kilobits per second, of forwarded multicast traffic on the interface. A rate-limit of 0 indicates that no rate limiting is done.
.1.3.6.1.2.1.83.1.1.4.1.5,IPMROUTE-STD-MIB::ipMRouteInterfaceInMcastOctets,Counter32,read-only,,current,,The number of octets of multicast packets that have arrived on the interface, including framing characters. This object is similar to ifInOctets in the Interfaces MIB, except that only multicast packets are counted.
.1.3.6.1.2.1.83.1.1.4.1.6,IPMROUTE-STD-MIB::ipMRouteInterfaceOutMcastOctets,Counter32,read-only,,current,,The number of octets of multicast packets that have been sent on the interface.
.1.3.6.1.2.1.83.1.1.4.1.7,IPMROUTE-STD-MIB::ipMRouteInterfaceHCInMcastOctets,Counter64,read-only,,current,,The number of octets of multicast packets that have arrived on the interface, including framing characters. This object is a 64-bit version of ipMRouteInterfaceInMcastOctets. It is similar to ifHCInOctets in the Interfaces MIB, except that only multicast packets are counted.
.1.3.6.1.2.1.83.1.1.4.1.8,IPMROUTE-STD-MIB::ipMRouteInterfaceHCOutMcastOctets,Counter64,read-only,,current,,The number of octets of multicast packets that have been sent on the interface. This object is a 64-bit version of ipMRouteInterfaceOutMcastOctets.
.1.3.6.1.2.1.83.1.1.5,IPMROUTE-STD-MIB::ipMRouteBoundaryTable,,not-accessible,,current,,The (conceptual) table listing the router's scoped multicast address boundaries.
.1.3.6.1.2.1.83.1.1.5.1,IPMROUTE-STD-MIB::ipMRouteBoundaryEntry,,not-accessible,ipMRouteBoundaryIfIndex:ipMRouteBoundaryAddress:ipMRouteBoundaryAddressMask,current,,An entry (conceptual row) in the ipMRouteBoundaryTable representing a scoped boundary.
.1.3.6.1.2.1.83.1.1.5.1.1,IPMROUTE-STD-MIB::ipMRouteBoundaryIfIndex,Integer32,not-accessible,,current,,The IfIndex value for the interface to which this boundary applies. Packets with a destination address in the associated address/mask range will not be forwarded out this interface.
.1.3.6.1.2.1.83.1.1.5.1.2,IPMROUTE-STD-MIB::ipMRouteBoundaryAddress,IpAddress,not-accessible,,current,,The group address which when combined with the corresponding value of ipMRouteBoundaryAddressMask identifies the group range for which the scoped boundary exists. Scoped addresses must come from the range 239.x.x.x as specified in RFC 2365.
.1.3.6.1.2.1.83.1.1.5.1.3,IPMROUTE-STD-MIB::ipMRouteBoundaryAddressMask,IpAddress,not-accessible,,current,,The group address mask which when combined with the corresponding value of ipMRouteBoundaryAddress identifies the group range for which the scoped boundary exists.
.1.3.6.1.2.1.83.1.1.5.1.4,IPMROUTE-STD-MIB::ipMRouteBoundaryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.
.1.3.6.1.2.1.83.1.1.6,IPMROUTE-STD-MIB::ipMRouteScopeNameTable,,not-accessible,,current,,The (conceptual) table listing the multicast scope names.
.1.3.6.1.2.1.83.1.1.6.1,IPMROUTE-STD-MIB::ipMRouteScopeNameEntry,,not-accessible,ipMRouteScopeNameAddress:ipMRouteScopeNameAddressMask:IMPLIEDipMRouteScopeNameLanguage,current,,An entry (conceptual row) in the ipMRouteScopeNameTable representing a multicast scope name.
.1.3.6.1.2.1.83.1.1.6.1.1,IPMROUTE-STD-MIB::ipMRouteScopeNameAddress,IpAddress,not-accessible,,current,,The group address which when combined with the corresponding value of ipMRouteScopeNameAddressMask identifies the group range associated with the multicast scope. Scoped addresses must come from the range 239.x.x.x.
.1.3.6.1.2.1.83.1.1.6.1.2,IPMROUTE-STD-MIB::ipMRouteScopeNameAddressMask,IpAddress,not-accessible,,current,,The group address mask which when combined with the corresponding value of ipMRouteScopeNameAddress identifies the group range associated with the multicast scope.
.1.3.6.1.2.1.83.1.1.6.1.3,IPMROUTE-STD-MIB::ipMRouteScopeNameLanguage,OCTET,not-accessible,,current,,The RFC 1766-style language tag associated with the scope name.
.1.3.6.1.2.1.83.1.1.6.1.4,IPMROUTE-STD-MIB::ipMRouteScopeNameString,OCTET,read-create,,current,,The textual name associated with the multicast scope. The value of this object should be suitable for displaying to end-users, such as when allocating a multicast address in this scope. When no name is specified, the default value of this object should be the string 239.x.x.x/y with x and y replaced appropriately to describe the address and mask length associated with the scope.
.1.3.6.1.2.1.83.1.1.6.1.5,IPMROUTE-STD-MIB::ipMRouteScopeNameDefault,INTEGER,read-create,,current,true(1):false(2),If true, indicates a preference that the name in the following language should be used by applications if no name is available in a desired language.
.1.3.6.1.2.1.83.1.1.6.1.6,IPMROUTE-STD-MIB::ipMRouteScopeNameStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.
.1.3.6.1.2.1.83.1.1.7,IPMROUTE-STD-MIB::ipMRouteEntryCount,Gauge32,read-only,,current,,The number of rows in the ipMRouteTable. This can be used to monitor the multicast routing table size.
.1.3.6.1.2.1.83.2,IPMROUTE-STD-MIB::ipMRouteMIBConformance,,,,,,
.1.3.6.1.2.1.83.2.1,IPMROUTE-STD-MIB::ipMRouteMIBCompliances,,,,,,
.1.3.6.1.2.1.83.2.1.1,IPMROUTE-STD-MIB::ipMRouteMIBCompliance,,,,,,The compliance statement for the IP Multicast MIB.
.1.3.6.1.2.1.83.2.2,IPMROUTE-STD-MIB::ipMRouteMIBGroups,,,,,,
.1.3.6.1.2.1.83.2.2.1,IPMROUTE-STD-MIB::ipMRouteMIBBasicGroup,,,,,,A collection of objects to support basic management of IP Multicast routing.
.1.3.6.1.2.1.83.2.2.2,IPMROUTE-STD-MIB::ipMRouteMIBHopCountGroup,,,,,,A collection of objects to support management of the use of hop counts in IP Multicast routing.
.1.3.6.1.2.1.83.2.2.3,IPMROUTE-STD-MIB::ipMRouteMIBBoundaryGroup,,,,,,A collection of objects to support management of scoped multicast address boundaries.
.1.3.6.1.2.1.83.2.2.4,IPMROUTE-STD-MIB::ipMRouteMIBPktsOutGroup,,,,,,A collection of objects to support management of packet counters for each outgoing interface entry of a route.
.1.3.6.1.2.1.83.2.2.5,IPMROUTE-STD-MIB::ipMRouteMIBHCInterfaceGroup,,,,,,A collection of objects providing information specific to high speed (greater than 20,000,000 bits/second) network interfaces.
.1.3.6.1.2.1.83.2.2.6,IPMROUTE-STD-MIB::ipMRouteMIBRouteGroup,,,,,,A collection of objects providing information on the relationship between multicast routing information, and the IP Forwarding Table.
.1.3.6.1.2.1.83.2.2.7,IPMROUTE-STD-MIB::ipMRouteMIBPktsGroup,,,,,,A collection of objects to support management of packet counters for each forwarding entry.
.1.3.6.1.2.1.84,IANA-RTPROTO-MIB::ianaRtProtoMIB,,,,,,This MIB module defines the IANAipRouteProtocol and IANAipMRouteProtocol textual conventions for use in MIBs which need to identify unicast or multicast routing mechanisms. Any additions or changes to the contents of this MIB module require either publication of an RFC, or Designated Expert Review as defined in RFC 2434, Guidelines for Writing an IANA Considerations Section in RFCs. The Designated Expert will be selected by the IESG Area Director(s) of the Routing Area.
.1.3.6.1.2.1.85,IGMP-STD-MIB::igmpStdMIB,,,,,,The MIB module for IGMP Management.
.1.3.6.1.2.1.85.1,IGMP-STD-MIB::igmpMIBObjects,,,,,,
.1.3.6.1.2.1.85.1.1,IGMP-STD-MIB::igmpInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the interfaces on which IGMP is enabled.
.1.3.6.1.2.1.85.1.1.1,IGMP-STD-MIB::igmpInterfaceEntry,,not-accessible,igmpInterfaceIfIndex,current,,An entry (conceptual row) representing an interface on which IGMP is enabled.
.1.3.6.1.2.1.85.1.1.1.1,IGMP-STD-MIB::igmpInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for which IGMP is enabled.
.1.3.6.1.2.1.85.1.1.1.2,IGMP-STD-MIB::igmpInterfaceQueryInterval,Unsigned32,read-create,,current,,The frequency at which IGMP Host-Query packets are transmitted on this interface.
.1.3.6.1.2.1.85.1.1.1.3,IGMP-STD-MIB::igmpInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The activation of a row enables IGMP on the interface. The destruction of a row disables IGMP on the interface.
.1.3.6.1.2.1.85.1.1.1.4,IGMP-STD-MIB::igmpInterfaceVersion,Unsigned32,read-create,,current,,The version of IGMP which is running on this interface. This object can be used to configure a router capable of running either value. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP on that LAN.
.1.3.6.1.2.1.85.1.1.1.5,IGMP-STD-MIB::igmpInterfaceQuerier,IpAddress,read-only,,current,,The address of the IGMP Querier on the IP subnet to which this interface is attached.
.1.3.6.1.2.1.85.1.1.1.6,IGMP-STD-MIB::igmpInterfaceQueryMaxResponseTime,Unsigned32,read-create,,current,,The maximum query response time advertised in IGMPv2 queries on this interface.
.1.3.6.1.2.1.85.1.1.1.7,IGMP-STD-MIB::igmpInterfaceQuerierUpTime,TimeTicks,read-only,,current,,The time since igmpInterfaceQuerier was last changed.
.1.3.6.1.2.1.85.1.1.1.8,IGMP-STD-MIB::igmpInterfaceQuerierExpiryTime,TimeTicks,read-only,,current,,The amount of time remaining before the Other Querier Present Timer expires. If the local system is the querier, the value of this object is zero.
.1.3.6.1.2.1.85.1.1.1.9,IGMP-STD-MIB::igmpInterfaceVersion1QuerierTimer,TimeTicks,read-only,,current,,The time remaining until the host assumes that there are no IGMPv1 routers present on the interface. While this is non- zero, the host will reply to all queries with version 1 membership reports.
.1.3.6.1.2.1.85.1.1.1.10,IGMP-STD-MIB::igmpInterfaceWrongVersionQueries,Counter32,read-only,,current,,The number of queries received whose IGMP version does not match igmpInterfaceVersion, over the lifetime of the row entry. IGMP requires that all routers on a LAN be configured to run the same version of IGMP. Thus, if any queries are received with the wrong version, this indicates a configuration error.
.1.3.6.1.2.1.85.1.1.1.11,IGMP-STD-MIB::igmpInterfaceJoins,Counter32,read-only,,current,,The number of times a group membership has been added on this interface; that is, the number of times an entry for this interface has been added to the Cache Table. This object gives an indication of the amount of IGMP activity over the lifetime of the row entry.
.1.3.6.1.2.1.85.1.1.1.12,IGMP-STD-MIB::igmpInterfaceProxyIfIndex,Integer32,read-create,,current,,Some devices implement a form of IGMP proxying whereby memberships learned on the interface represented by this row, cause IGMP Host Membership Reports to be sent on the interface whose ifIndex value is given by this object. Such a device would implement the igmpV2RouterMIBGroup only on its router interfaces (those interfaces with non-zero igmpInterfaceProxyIfIndex). Typically, the value of this object is 0, indicating that no proxying is being done.
.1.3.6.1.2.1.85.1.1.1.13,IGMP-STD-MIB::igmpInterfaceGroups,Gauge32,read-only,,current,,The current number of entries for this interface in the Cache Table.
.1.3.6.1.2.1.85.1.1.1.14,IGMP-STD-MIB::igmpInterfaceRobustness,Unsigned32,read-create,,current,,The Robustness Variable allows tuning for the expected packet loss on a subnet. If a subnet is expected to be lossy, the Robustness Variable may be increased. IGMP is robust to (Robustness Variable-1) packet losses.
.1.3.6.1.2.1.85.1.1.1.15,IGMP-STD-MIB::igmpInterfaceLastMembQueryIntvl,Unsigned32,read-create,,current,,The Last Member Query Interval is the Max Response Time inserted into Group-Specific Queries sent in response to Leave Group messages, and is also the amount of time between Group-Specific Query messages. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group. The value of this object is irrelevant if igmpInterfaceVersion is 1.
.1.3.6.1.2.1.85.1.2,IGMP-STD-MIB::igmpCacheTable,,not-accessible,,current,,The (conceptual) table listing the IP multicast groups for which there are members on a particular interface.
.1.3.6.1.2.1.85.1.2.1,IGMP-STD-MIB::igmpCacheEntry,,not-accessible,igmpCacheAddress:igmpCacheIfIndex,current,,An entry (conceptual row) in the igmpCacheTable.
.1.3.6.1.2.1.85.1.2.1.1,IGMP-STD-MIB::igmpCacheAddress,IpAddress,not-accessible,,current,,The IP multicast group address for which this entry contains information.
.1.3.6.1.2.1.85.1.2.1.2,IGMP-STD-MIB::igmpCacheIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information for an IP multicast group address.
.1.3.6.1.2.1.85.1.2.1.3,IGMP-STD-MIB::igmpCacheSelf,INTEGER,read-create,,current,true(1):false(2),An indication of whether the local system is a member of this group address on this interface.
.1.3.6.1.2.1.85.1.2.1.4,IGMP-STD-MIB::igmpCacheLastReporter,IpAddress,read-only,,current,,The IP address of the source of the last membership report received for this IP Multicast group address on this interface. If no membership report has been received, this object has the value 0.0.0.0.
.1.3.6.1.2.1.85.1.2.1.5,IGMP-STD-MIB::igmpCacheUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.2.1.85.1.2.1.6,IGMP-STD-MIB::igmpCacheExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. A value of 0 indicates that the entry is only present because igmpCacheSelf is true and that if the router left the group, this entry would be aged out immediately. Note that some implementations may process membership reports from the local system in the same way as reports from other hosts, so a value of 0 is not required.
.1.3.6.1.2.1.85.1.2.1.7,IGMP-STD-MIB::igmpCacheStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry.
.1.3.6.1.2.1.85.1.2.1.8,IGMP-STD-MIB::igmpCacheVersion1HostTimer,TimeTicks,read-only,,current,,The time remaining until the local router will assume that there are no longer any IGMP version 1 members on the IP subnet attached to this interface. Upon hearing any IGMPv1 Membership Report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv2 Leave messages for this group that it receives on this interface.
.1.3.6.1.2.1.85.2,IGMP-STD-MIB::igmpMIBConformance,,,,,,
.1.3.6.1.2.1.85.2.1,IGMP-STD-MIB::igmpMIBCompliances,,,,,,
.1.3.6.1.2.1.85.2.1.1,IGMP-STD-MIB::igmpV1HostMIBCompliance,,,,,,The compliance statement for hosts running IGMPv1 and implementing the IGMP MIB.
.1.3.6.1.2.1.85.2.1.2,IGMP-STD-MIB::igmpV1RouterMIBCompliance,,,,,,The compliance statement for routers running IGMPv1 and implementing the IGMP MIB.
.1.3.6.1.2.1.85.2.1.3,IGMP-STD-MIB::igmpV2HostMIBCompliance,,,,,,The compliance statement for hosts running IGMPv2 and implementing the IGMP MIB.
.1.3.6.1.2.1.85.2.1.4,IGMP-STD-MIB::igmpV2RouterMIBCompliance,,,,,,The compliance statement for routers running IGMPv2 and implementing the IGMP MIB.
.1.3.6.1.2.1.85.2.2,IGMP-STD-MIB::igmpMIBGroups,,,,,,
.1.3.6.1.2.1.85.2.2.1,IGMP-STD-MIB::igmpBaseMIBGroup,,,,,,The basic collection of objects providing management of IGMP version 1 or 2.
.1.3.6.1.2.1.85.2.2.2,IGMP-STD-MIB::igmpRouterMIBGroup,,,,,,A collection of additional objects for management of IGMP version 1 or 2 in routers.
.1.3.6.1.2.1.85.2.2.3,IGMP-STD-MIB::igmpV2HostMIBGroup,,,,,,A collection of additional objects for management of IGMP version 2 in hosts.
.1.3.6.1.2.1.85.2.2.4,IGMP-STD-MIB::igmpHostOptMIBGroup,,,,,,A collection of optional objects for IGMP hosts. Supporting this group can be especially useful in an environment with a router which does not support the IGMP MIB.
.1.3.6.1.2.1.85.2.2.5,IGMP-STD-MIB::igmpV2RouterMIBGroup,,,,,,A collection of additional objects for management of IGMP version 2 in routers.
.1.3.6.1.2.1.85.2.2.6,IGMP-STD-MIB::igmpV2ProxyMIBGroup,,,,,,A collection of additional objects for management of IGMP proxy devices.
.1.3.6.1.2.1.86,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfMIB,,,,,,The MIB module for monitoring and controlling the Frame Relay/ATM PVC Service Interworking Function.
.1.3.6.1.2.1.86.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfMIBObjects,,,,,,
.1.3.6.1.2.1.86.1.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnIndexNext,Integer32,read-only,,current,,This object contains an appropriate value to be used for frAtmIwfConnIndex when creating entries in the frAtmIwfConnectionTable. The value 0 indicates that no unassigned entries are available. To obtain the frAtmIwfConnIndexNext value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index.
.1.3.6.1.2.1.86.1.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionTable,,not-accessible,,current,,A table in which each row represents a Frame Relay/ATM interworking connection.
.1.3.6.1.2.1.86.1.2.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionEntry,,not-accessible,frAtmIwfConnIndex:frAtmIwfConnAtmPort:frAtmIwfConnVpi:frAtmIwfConnVci:frAtmIwfConnFrPort:frAtmIwfConnDlci,current,,The FrAtmIwfConnectionEntry provides an entry for an interworking connection between a frame relay PVC and one or more ATM PVCs, or an ATM PVC and one or more frame relay PVCs. A single frame relay PVC connected to a single ATM PVC is referred to as a `point-to-point' connection and is represented by a single row in the FR/ATM IWF Connection Table. The case of a single frame relay PVC connected to multiple ATM PVCs (or single ATM PVC connected to multiple frame relay PVCs) is referred to as a `point-to-multipoint' connection and is represented by multiple rows in the FR/ATM IWF Connection Table. The object frAtmIwfConnIndex uniquely identifies each point-to-point or point-to-multipoint connection. The manager obtains the frAtmIwfConnIndex value by reading the frAtmIwfConnIndexNext object. After a frAtmIwfConnIndex is assigned for the connection, the manager creates one or more rows in the Cross Connect Table; one for each cross- connection between the frame relay PVC and an ATM PVC. In the case of `point-to-multipoint' connections, all rows are indexed by the same frAtmIwfConnIndex value and MUST refer to the same frame relay PVC or ATM PVC respectively. An entry can be created only when at least one pair of frame relay and ATM PVCs exist. A row can be established by one-step set-request with all required parameter values and frAtmIwfConnRowStatus set to createAndGo(4). The Agent should perform all error checking as needed. A pair of cross-connected PVCs, as identified by a particular value of the indexes, is released by setting frAtmIwfConnRowStatus to destroy(6). The Agent may release all associated resources. The manager may remove the related PVCs thereafter. Indexes are persistent across reboots of the system.
.1.3.6.1.2.1.86.1.2.1.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnIndex,Integer32,not-accessible,,current,,A unique value for each point-to-point or point- to-multipoint connection. The manager obtains the frAtmIwfConnIndex value by reading the frAtmIwfConnIndexNext object. A point-to- multipoint connection will be represented in the frAtmIwfConnectionTable with multiple entries that share the same frAtmIwfConnIndex value.
.1.3.6.1.2.1.86.1.2.1.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnAtmPort,Integer32,not-accessible,,current,,The index in the ifTable that identifies the ATM port for this interworking connection.
.1.3.6.1.2.1.86.1.2.1.3,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnVpi,INTEGER,not-accessible,,current,,The VPI of the ATM PVC end point for this interworking connection.
.1.3.6.1.2.1.86.1.2.1.4,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnVci,INTEGER,not-accessible,,current,,The VCI of the ATM PVC end point for this interworking connection.
.1.3.6.1.2.1.86.1.2.1.5,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnFrPort,Integer32,not-accessible,,current,,The index in the ifTable that identifies the frame relay port for this interworking connection.
.1.3.6.1.2.1.86.1.2.1.6,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnDlci,Integer32,not-accessible,,current,,The DLCI that identifies the frame relay PVC end point for this interworking connection.
.1.3.6.1.2.1.86.1.2.1.7,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The table row may be created with 'createAndWait(5)' or 'createAndGo(4)'. To activate a connection entry, a valid connection descriptor MUST be established in the frAtmIwfConnectionDescriptor object. This object is set to 'destroy(6)' to delete the table row. Before the table row is destroyed, the OperStatus/AdminStatus of the corresponding endpoints MUST be 'down(2)'. The deactivation of the ATM endpoint MAY occur as a side-effect of deleting the FR/ATM IWF cross-connection table row. Otherwise, 'destroy(6)' operation MUST fail (error code 'inconsistentValue').
.1.3.6.1.2.1.86.1.2.1.8,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired operational state for this FR/ATM interworked connection. up(1) = Activate the connection. Before the activation can be completed, the OperStatus/AdminStatus of the corresponding endpoints MUST be 'up(1)'. The activation of the corresponding endpoints MAY occur as a side-effect of activating the FR/ATM IWF cross-connection. down(2) = Deactivate the connection. Before the deactivation can be completed, the atmVclAdminStatus of the corresponding ATM endpoint MUST be 'down(2)'. The deactivation of the ATM endpoint MAY occur as a side-effect of deactivating the FR/ATM IWF cross-connection.
.1.3.6.1.2.1.86.1.2.1.9,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnAtm2FrOperStatus,INTEGER,read-only,,current,up(1):down(2),The current operational state of this interworking connection in the ATM to frame relay direction.
.1.3.6.1.2.1.86.1.2.1.10,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnAtm2FrLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this interworking connection entered its current operational state in the ATM to FR direction. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.86.1.2.1.11,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnFr2AtmOperStatus,INTEGER,read-only,,current,up(1):down(2),The current operational state of this interworking connection in the frame relay to ATM direction.
.1.3.6.1.2.1.86.1.2.1.12,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnFr2AtmLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this interworking connection entered its current operational state in the FR to ATM direction. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.86.1.2.1.13,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionDescriptor,Integer32,read-create,,current,,The value represents a pointer to the relevant descriptor in the IWF descriptor table. An attempt to set this value to an inactive or non- existent row in the Connection Descriptor Table MUST fail (error code 'inconsistentValue').
.1.3.6.1.2.1.86.1.2.1.14,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnFailedFrameTranslate,Counter32,read-only,,current,,This object counts the number of frames discarded by the IWF because, while operating in Translation Mode, the IWF is unable to decode the incoming frame payload header according to the mapping rules. (i.e., payload header not recognized by the IWF). Frame relay frames are received in the frame relay to ATM direction of the PVC. When operating in Transparent Mode, the IWF MUST return noSuchInstance.
.1.3.6.1.2.1.86.1.2.1.15,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnOverSizedFrames,Counter32,read-only,,current,,Count of frames discarded by the IWF because the frame is too large to be processed by the AAL5 segmentation procedure. Specifically, the frame does not conform to the size specified in the atmVccAal5CpcsTransmitSduSize object associated with the atmVclEntry at the ATM endpoint. Frame relay frames are received in the frame relay to ATM direction of the PVC.
.1.3.6.1.2.1.86.1.2.1.16,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnFailedAal5PduTranslate,Counter32,read-only,,current,,This attribute counts the number of AAL5 PDUs discarded by the IWF because, while operating in Translation Mode, the IWF is unable to decode the incoming AAL5 PDU payload header according to the mapping rules. (i.e., payload header not recognized by the IWF). AAL5 PDUs are received in the ATM to frame relay direction of the PVC. When operating in Transparent Mode, the IWF MUST return noSuchInstance.
.1.3.6.1.2.1.86.1.2.1.17,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnOverSizedSDUs,Counter32,read-only,,current,,Count of AAL5 SDUs discarded by the IWF because the SDU is too large to be forwarded on the frame relay segment of the connection. Specifically, the frame does not conform to the size specified in the frLportFragSize object of the FRS MIB [19]. AAL5 PDUs are received in the ATM to frame relay direction of the PVC.
.1.3.6.1.2.1.86.1.2.1.18,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnCrcErrors,Counter32,read-only,,current,,The number of AAL5 CPCS PDUs received with CRC-32 errors on this AAL5 VCC at the IWF. AAL5 PDUs are received in the ATM to frame relay direction of the PVC.
.1.3.6.1.2.1.86.1.2.1.19,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnSarTimeOuts,Counter32,read-only,,current,,The number of partially re-assembled AAL5 CPCS PDUs which were discarded on this AAL5 VCC at the IWF because they were not fully re-assembled within the required time period. If the re- assembly timer is not supported, then this object contains a zero value. AAL5 PDUs are received in the ATM to frame relay direction of the PVC.
.1.3.6.1.2.1.86.1.3,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionDescriptorIndexNext,Integer32,read-only,,current,,This object contains an appropriate value to be used for frAtmIwfConnectionDescriptorIndex when creating entries in the frAtmIwfConnectionDescriptorTable. The value 0 indicates that no unassigned entries are available. To obtain the frAtmIwfConnectionDescriptorIndexNext value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index.
.1.3.6.1.2.1.86.1.4,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionDescriptorTable,,not-accessible,,current,,A table in which each row represents a descriptor for one type of Frame Relay/ATM interworking connection. A descriptor may be assigned to zero or more FR/ATM PVC service IWF connections.
.1.3.6.1.2.1.86.1.4.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionDescriptorEntry,,not-accessible,frAtmIwfConnectionDescriptorIndex,current,,An entry for a descriptor in an interworking connection between a frame relay PVC and an ATM PVC.
.1.3.6.1.2.1.86.1.4.1.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionDescriptorIndex,Integer32,not-accessible,,current,,A unique value to identify a descriptor in the table 
.1.3.6.1.2.1.86.1.4.1.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnDescriptorRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this table row. This object is used to create or delete an entry in the descriptor table. Creation of the row requires a row index (see frAtmIwfConnectionDescriptorIndexNext). If not explicitly set or in existence, all other columns of the row will be created and initialized to the default value. During creation, this object MAY be set to 'createAndGo(4)' or 'createAndWait(5)'. The object MUST contain the value 'active(1)' before any connection table entry references the row. To destroy a row in this table, this object is set to the 'destroy(6)' action. Row destruction MUST fail (error code 'inconsistentValue') if any connection references the row.
.1.3.6.1.2.1.86.1.4.1.3,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnDeToClpMappingMode,INTEGER,read-create,,current,mode1(1):mode2Const0(2):mode2Const1(3),This object describes which mode of translation is in use for loss priority mapping in the frame relay to ATM direction. mode1(1) = the DE field in the Q.922 core frame shall be mapped to the ATM CLP field of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame. mode2Contst0(2) = the ATM CLP field of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame shall be set to constant 0. mode2Contst1(3) = the ATM CLP field of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame shall be set to constant 1.
.1.3.6.1.2.1.86.1.4.1.4,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnClpToDeMappingMode,INTEGER,read-create,,current,mode1(1):mode2Const0(2):mode2Const1(3),This object describes which mode of translation is in use for loss priority mapping in the ATM to frame relay direction. mode1(1) = if one or more cells in a frame has its CLP field set, the DE field of the Q.922 core frame should be set. mode2Const0(2) = the DE field of the Q.922 core frame should be set to the constant 0. mode2Const1(3) = the DE field of the Q.922 core frame should be set to the constant 1.
.1.3.6.1.2.1.86.1.4.1.5,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnCongestionMappingMode,INTEGER,read-create,,current,mode1(1):mode2(2),This object describes which mode of translation is in use for forward congestion indication mapping in the frame relay to ATM direction. mode1(1) = The FECN field in the Q.922 core frame shall be mapped to the ATM EFCI field of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame. mode2(2) = The FECN field in the Q.922 core frame shall not be mapped to the ATM EFCI field of cells generated by the segmentation process of the AAL5 PDU containing the information of that frame. The EFCI field is always set to 'congestion not experienced'. In both of the modes above, if there is congestion in the forward direction in the ATM layer within the IWF, then the IWF can set the EFCI field to 'congestion experienced'.
.1.3.6.1.2.1.86.1.4.1.6,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnEncapsulationMappingMode,INTEGER,read-create,,current,transparentMode(1):translationMode(2):translationModeAll(3),This object indicates whether the mapping of upper layer protocol encapsulation is enabled on this interworking connection. transparentMode(1) = Forward the encapsulations unaltered. translationMode(2) = Perform mapping between the two encapsulations due to the incompatibilities of the two methods. Mapping is provided for a subset of the potential encapsulations as itemized in frAtmIwfConnEncapsulationMapp ings. translationModeAll(3) = Perform mapping between the two encapsulations due to the incompatibilities of the two methods. All encapsulations are translated.
.1.3.6.1.2.1.86.1.4.1.7,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnEncapsulationMappings,BITS,read-create,,current,none(0):bridgedPdus(1):bridged802dot6(2):bPdus(3):routedIp(4):routedOsi(5):otherRouted(6):x25Iso8202(7):q933q2931(8),If upper layer protocol encapsulation mapping is enabled on this interworking connection, then this attribute enumerates which of the encapsulation mappings are supported. none(0) = Transparent mode operation bridgedPdus(1) = PID: 0x00-01,-07,-02 or -08 bridged802dot6(2) = PID: 0x00-0B bPdus(3) = PID: 0x00-0E or -0F routedIp(4) = NLPID: OxCC routedOsi(5) = NLPID: Ox81, 0x82 or 0x83 otherRouted(6) = Other routed protocols x25Iso8202(7) = X25 q933q2931(8) = Q.933 and Q.2931
.1.3.6.1.2.1.86.1.4.1.8,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnFragAndReassEnabled,INTEGER,read-create,,current,enabled(1):disabled(2),The attribute indicates whether fragmentation and reassembly is enabled for this connection.
.1.3.6.1.2.1.86.1.4.1.9,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnArpTranslationEnabled,INTEGER,read-create,,current,enabled(1):disabled(2),The attribute indicates whether ARP translation is enabled for this connection.
.1.3.6.1.2.1.86.1.5,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfVclTable,,not-accessible,,current,,The FR/ATM IWF VCL Table augments the ATM MIB VCL Endpoint table.
.1.3.6.1.2.1.86.1.5.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfVclEntry,,not-accessible,,current,,Entries in this table are created only by the agent. One entry exists for each ATM VCL managed by the agent.
.1.3.6.1.2.1.86.1.5.1.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfVclCrossConnectIdentifier,Integer32,read-only,,current,,This object contains the index value of the FR/ATM cross-connect table entry used to link the ATM VCL with a frame relay PVC. Each row of the atmVclTable that is not cross- connected with a frame relay PVC MUST return the value zero when this object is read. In the case of (frame relay) point to (ATM) multipoint, multiple ATM VCLs will have the same value of this object, and all their cross- connections are identified by entries that are indexed by the same value of frAtmIwfVclCrossConnectIdentifier in the frAtmIwfConnectionTable of this MIB module. The value of this object is initialized by the agent after the associated entries in the frAtmIwfConnectionTable have been created.
.1.3.6.1.2.1.86.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfTraps,,,,,,
.1.3.6.1.2.1.86.2.0,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfTrapsPrefix,,,,,,
.1.3.6.1.2.1.86.2.0.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnStatusChange,,,,,,An indication that the status of this interworking connection has changed.
.1.3.6.1.2.1.86.3,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConformance,,,,,,
.1.3.6.1.2.1.86.3.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfGroups,,,,,,
.1.3.6.1.2.1.86.3.1.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfBasicGroup,,,,,,The collection of basic objects for configuration and control of FR/ATM interworking connections.
.1.3.6.1.2.1.86.3.1.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfConnectionDescriptorGroup,,,,,,The collection of basic objects for specification of FR/ATM interworking connection descriptors.
.1.3.6.1.2.1.86.3.1.3,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfAtmVclTableAugmentGroup,,,,,,The ATM MIB VCL Endpoint Table AUGMENT object contained in the FR/ATM PVC Service Interworking MIB.
.1.3.6.1.2.1.86.3.1.4,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfNotificationsGroup,,,,,,The notification for FR/ATM interworking status change.
.1.3.6.1.2.1.86.3.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfCompliances,,,,,,
.1.3.6.1.2.1.86.3.2.1,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfEquipmentCompliance,,,,,,The compliance statement for equipment that implements the FR/ATM Interworking MIB.
.1.3.6.1.2.1.86.3.2.2,FR-ATM-PVC-SERVICE-IWF-MIB::frAtmIwfServiceCompliance,,,,,,The compliance statement for a CNM interface that implements the FR/ATM Interworking MIB.
.1.3.6.1.2.1.87,RTP-MIB::rtpMIB,,,,,,The managed objects of RTP systems. The MIB is structured around three types of information. 1. General information about RTP sessions such as the session address. 2. Information about RTP streams being sent to an RTP session by a particular sender. 3. Information about RTP streams received on an RTP session by a particular receiver from a particular sender. There are two types of RTP Systems, RTP hosts and RTP monitors. As described below, certain objects are unique to a particular type of RTP System. An RTP host may also function as an RTP monitor. Refer to RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' section 3.0, for definitions.
.1.3.6.1.2.1.87.1,RTP-MIB::rtpMIBObjects,,,,,,
.1.3.6.1.2.1.87.1.1,RTP-MIB::rtpSessionNewIndex,INTEGER,read-write,,current,,This object is used to assign values to rtpSessionIndex as described in 'Textual Conventions for SMIv2'. For an RTP system that supports the creation of rows, the network manager would read the object, and then write the value back in the Set that creates a new instance of rtpSessionEntry. If the Set fails with the code 'inconsistentValue,' then the process must be repeated; If the Set succeeds, then the object is incremented, and the new instance is created according to the manager's directions. However, if the RTP agent is not acting as a monitor, only the RTP agent may create conceptual rows in the RTP session table.
.1.3.6.1.2.1.87.1.2,RTP-MIB::rtpSessionInverseTable,,not-accessible,,current,,Maps rtpSessionDomain, rtpSessionRemAddr, and rtpSessionLocAddr TAddress pairs to one or more rtpSessionIndex values, each describing a row in the rtpSessionTable. This makes it possible to retrieve the row(s) in the rtpSessionTable corresponding to a given session without having to walk the entire (potentially large) table.
.1.3.6.1.2.1.87.1.2.1,RTP-MIB::rtpSessionInverseEntry,,not-accessible,rtpSessionDomain:rtpSessionRemAddr:rtpSessionLocAddr:rtpSessionIndex,current,,Each entry corresponds to exactly one entry in the rtpSessionTable - the entry containing the tuple, rtpSessionDomain, rtpSessionRemAddr, rtpSessionLocAddr and rtpSessionIndex.
.1.3.6.1.2.1.87.1.2.1.1,RTP-MIB::rtpSessionInverseStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created.
.1.3.6.1.2.1.87.1.3,RTP-MIB::rtpSessionTable,,not-accessible,,current,,There's one entry in rtpSessionTable for each RTP session on which packets are being sent, received, and/or monitored.
.1.3.6.1.2.1.87.1.3.1,RTP-MIB::rtpSessionEntry,,not-accessible,rtpSessionIndex,current,,Data in rtpSessionTable uniquely identify an RTP session. A host RTP agent MUST create a read-only row for each session to which packets are being sent or received. Rows MUST be created by the RTP Agent at the start of a session when one or more senders or receivers are observed. Rows created by an RTP agent MUST be deleted when the session is over and there are no rtpRcvrEntry and no rtpSenderEntry for this session. An RTP session SHOULD be monitored to create management information on all RTP streams being sent or received when the rtpSessionMonitor has the TruthValue of 'true(1)'. An RTP monitor SHOULD permit row creation with the side effect of causing the RTP System to join the multicast session for the purposes of gathering management information (additional conceptual rows are created in the rtpRcvrTable and rtpSenderTable). Thus, rtpSessionTable rows SHOULD be created for RTP session monitoring purposes. Rows created by a management application SHOULD be deleted via SNMP operations by management applications. Rows created by management operations are deleted by management operations by setting rtpSessionRowStatus to 'destroy(6)'.
.1.3.6.1.2.1.87.1.3.1.1,RTP-MIB::rtpSessionIndex,Integer32,not-accessible,,current,,The index of the conceptual row which is for SNMP purposes only and has no relation to any protocol value. There is no requirement that these rows are created or maintained sequentially.
.1.3.6.1.2.1.87.1.3.1.2,RTP-MIB::rtpSessionDomain,OBJECT,read-create,,current,,The transport-layer protocol used for sending or receiving the stream of RTP data packets on this session. Cannot be changed if rtpSessionRowStatus is 'active'.
.1.3.6.1.2.1.87.1.3.1.3,RTP-MIB::rtpSessionRemAddr,OCTET,read-create,,current,,The address to which RTP packets are sent by the RTP system. In an IP multicast RTP session, this is the single address used by all senders and receivers of RTP session data. In a unicast RTP session this is the unicast address of the remote RTP system. 'The destination address pair may be common for all participants, as in the case of IP multicast, or may be different for each, as in the case of individual unicast network address pairs.' See RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 3. The transport service is identified by rtpSessionDomain. For snmpUDPDomain, this is an IP address and even-numbered UDP Port with the RTCP being sent on the next higher odd-numbered port, see RFC 1889, sec. 5.
.1.3.6.1.2.1.87.1.3.1.4,RTP-MIB::rtpSessionLocAddr,OCTET,read-only,,current,,The local address used by the RTP system. In an IP multicast RTP session, rtpSessionRemAddr will be the same IP multicast address as rtpSessionLocAddr. In a unicast RTP session, rtpSessionRemAddr and rtpSessionLocAddr will have different unicast addresses. See RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 3. The transport service is identified by rtpSessionDomain. For snmpUDPDomain, this is an IP address and even-numbered UDP Port with the RTCP being sent on the next higher odd-numbered port, see RFC 1889, sec. 5.
.1.3.6.1.2.1.87.1.3.1.5,RTP-MIB::rtpSessionIfIndex,Integer32,read-create,,current,,The ifIndex value is set to the corresponding value from IF-MIB (See RFC 2233, 'The Interfaces Group MIB using SMIv2'). This is the interface that the RTP stream is being sent to or received from, or in the case of an RTP Monitor the interface that RTCP packets will be received on. Cannot be changed if rtpSessionRowStatus is 'active'.
.1.3.6.1.2.1.87.1.3.1.6,RTP-MIB::rtpSessionSenderJoins,Counter32,read-only,,current,,The number of senders that have been observed to have joined the session since this conceptual row was created (rtpSessionStartTime). A sender 'joins' an RTP session by sending to it. Senders that leave and then re-join following an RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) or session timeout may be counted twice. Every time a new RTP sender is detected either using RTP or RTCP, this counter is incremented.
.1.3.6.1.2.1.87.1.3.1.7,RTP-MIB::rtpSessionReceiverJoins,Counter32,read-only,,current,,The number of receivers that have been been observed to have joined this session since this conceptual row was created (rtpSessionStartTime). A receiver 'joins' an RTP session by sending RTCP Receiver Reports to the session. Receivers that leave and then re-join following an RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) or session timeout may be counted twice.
.1.3.6.1.2.1.87.1.3.1.8,RTP-MIB::rtpSessionByes,Counter32,read-only,,current,,A count of RTCP BYE (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,' sec. 6.6) messages received by this entity.
.1.3.6.1.2.1.87.1.3.1.9,RTP-MIB::rtpSessionStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created.
.1.3.6.1.2.1.87.1.3.1.10,RTP-MIB::rtpSessionMonitor,INTEGER,read-only,,current,true(1):false(2),Boolean, Set to 'true(1)' if remote senders or receivers in addition to the local RTP System are to be monitored using RTCP. RTP Monitors MUST initialize to 'true(1)' and RTP Hosts SHOULD initialize this 'false(2)'. Note that because 'host monitor' systems are receiving RTCP from their remote participants they MUST set this value to 'true(1)'.
.1.3.6.1.2.1.87.1.3.1.11,RTP-MIB::rtpSessionRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Value of 'active' when RTP or RTCP messages are being sent or received by an RTP System. A newly-created conceptual row must have the all read-create objects initialized before becoming 'active'. A conceptual row that is in the 'notReady' or 'notInService' state MAY be removed after 5 minutes.
.1.3.6.1.2.1.87.1.4,RTP-MIB::rtpSenderInverseTable,,not-accessible,,current,,Maps rtpSenderAddr, rtpSessionIndex, to the rtpSenderSSRC index of the rtpSenderTable. This table allows management applications to find entries sorted by rtpSenderAddr rather than sorted by rtpSessionIndex. Given the rtpSessionDomain and rtpSenderAddr, a set of rtpSessionIndex and rtpSenderSSRC values can be returned from a tree walk. When rtpSessionIndex is specified in the SNMP Get-Next operations, one or more rtpSenderSSRC values may be returned.
.1.3.6.1.2.1.87.1.4.1,RTP-MIB::rtpSenderInverseEntry,,not-accessible,rtpSessionDomain:rtpSenderAddr:rtpSessionIndex:rtpSenderSSRC,current,,Each entry corresponds to exactly one entry in the rtpSenderTable - the entry containing the index pair, rtpSessionIndex, rtpSenderSSRC.
.1.3.6.1.2.1.87.1.4.1.1,RTP-MIB::rtpSenderInverseStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created.
.1.3.6.1.2.1.87.1.5,RTP-MIB::rtpSenderTable,,not-accessible,,current,,Table of information about a sender or senders to an RTP Session. RTP sending hosts MUST have an entry in this table for each stream being sent. RTP receiving hosts MAY have an entry in this table for each sending stream being received by this host. RTP monitors MUST create an entry for each observed sender to a multicast RTP Session as a side-effect when a conceptual row in the rtpSessionTable is made 'active' by a manager.
.1.3.6.1.2.1.87.1.5.1,RTP-MIB::rtpSenderEntry,,not-accessible,rtpSessionIndex:rtpSenderSSRC,current,,Each entry contains information from a single RTP Sender Synchronization Source (SSRC, see RFC 1889 'RTP: A Transport Protocol for Real-Time Applications' sec.6). The session is identified to the the SNMP entity by rtpSessionIndex. Rows are removed by the RTP agent when a BYE is received from the sender or when the sender times out (see RFC 1889, Sec. 6.2.1) or when the rtpSessionEntry is deleted.
.1.3.6.1.2.1.87.1.5.1.1,RTP-MIB::rtpSenderSSRC,Unsigned32,not-accessible,,current,,The RTP SSRC, or synchronization source identifier of the sender. The RTP session address plus an SSRC uniquely identify a sender to an RTP session (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.3).
.1.3.6.1.2.1.87.1.5.1.2,RTP-MIB::rtpSenderCNAME,OCTET,read-only,,current,,The RTP canonical name of the sender.
.1.3.6.1.2.1.87.1.5.1.3,RTP-MIB::rtpSenderAddr,OCTET,read-only,,current,,The unicast transport source address of the sender. In the case of an RTP Monitor this address is the address that the sender is using to send its RTCP Sender Reports.
.1.3.6.1.2.1.87.1.5.1.4,RTP-MIB::rtpSenderPackets,Counter64,read-only,,current,,Count of RTP packets sent by this sender, or observed by an RTP monitor, since rtpSenderStartTime.
.1.3.6.1.2.1.87.1.5.1.5,RTP-MIB::rtpSenderOctets,Counter64,read-only,,current,,Count of non-header RTP octets sent by this sender, or observed by an RTP monitor, since rtpSenderStartTime.
.1.3.6.1.2.1.87.1.5.1.6,RTP-MIB::rtpSenderTool,OCTET,read-only,,current,,Name of the application program source of the stream.
.1.3.6.1.2.1.87.1.5.1.7,RTP-MIB::rtpSenderSRs,Counter32,read-only,,current,,A count of the number of RTCP Sender Reports that have been sent from this sender, or observed if the RTP entity is a monitor, since rtpSenderStartTime.
.1.3.6.1.2.1.87.1.5.1.8,RTP-MIB::rtpSenderSRTime,TimeTicks,read-only,,current,,rtpSenderSRTime is the value of SysUpTime at the time that the last SR was received from this sender, in the case of a monitor or receiving host. Or sent by this sender, in the case of a sending host.
.1.3.6.1.2.1.87.1.5.1.9,RTP-MIB::rtpSenderPT,INTEGER,read-only,,current,,Payload type from the RTP header of the most recently received RTP Packet (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec. 5).
.1.3.6.1.2.1.87.1.5.1.10,RTP-MIB::rtpSenderStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created.
.1.3.6.1.2.1.87.1.6,RTP-MIB::rtpRcvrInverseTable,,not-accessible,,current,,Maps rtpRcvrAddr and rtpSessionIndex to the rtpRcvrSRCSSRC and rtpRcvrSSRC indexes of the rtpRcvrTable. This table allows management applications to find entries sorted by rtpRcvrAddr rather than by rtpSessionIndex. Given rtpSessionDomain and rtpRcvrAddr, a set of rtpSessionIndex, rtpRcvrSRCSSRC, and rtpRcvrSSRC values can be returned from a tree walk. When rtpSessionIndex is specified in SNMP Get-Next operations, one or more rtpRcvrSRCSSRC and rtpRcvrSSRC pairs may be returned.
.1.3.6.1.2.1.87.1.6.1,RTP-MIB::rtpRcvrInverseEntry,,not-accessible,rtpSessionDomain:rtpRcvrAddr:rtpSessionIndex:rtpRcvrSRCSSRC:rtpRcvrSSRC,current,,Each entry corresponds to exactly one entry in the rtpRcvrTable - the entry containing the index pair, rtpSessionIndex, rtpRcvrSSRC.
.1.3.6.1.2.1.87.1.6.1.1,RTP-MIB::rtpRcvrInverseStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created.
.1.3.6.1.2.1.87.1.7,RTP-MIB::rtpRcvrTable,,not-accessible,,current,,Table of information about a receiver or receivers of RTP session data. RTP hosts that receive RTP session packets MUST create an entry in this table for that receiver/sender pair. RTP hosts that send RTP session packets MAY create an entry in this table for each receiver to their stream using RTCP feedback from the RTP group. RTP monitors create an entry for each observed RTP session receiver as a side effect when a conceptual row in the rtpSessionTable is made 'active' by a manager.
.1.3.6.1.2.1.87.1.7.1,RTP-MIB::rtpRcvrEntry,,not-accessible,rtpSessionIndex:rtpRcvrSRCSSRC:rtpRcvrSSRC,current,,Each entry contains information from a single RTP Synchronization Source that is receiving packets from the sender identified by rtpRcvrSRCSSRC (SSRC, see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.6). The session is identified to the the RTP Agent entity by rtpSessionIndex. Rows are removed by the RTP agent when a BYE is received from the sender or when the sender times out (see RFC 1889, Sec. 6.2.1) or when the rtpSessionEntry is deleted.
.1.3.6.1.2.1.87.1.7.1.1,RTP-MIB::rtpRcvrSRCSSRC,Unsigned32,not-accessible,,current,,The RTP SSRC, or synchronization source identifier of the sender. The RTP session address plus an SSRC uniquely identify a sender or receiver of an RTP stream (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.3).
.1.3.6.1.2.1.87.1.7.1.2,RTP-MIB::rtpRcvrSSRC,Unsigned32,not-accessible,,current,,The RTP SSRC, or synchronization source identifier of the receiver. The RTP session address plus an SSRC uniquely identify a receiver of an RTP stream (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.3).
.1.3.6.1.2.1.87.1.7.1.3,RTP-MIB::rtpRcvrCNAME,OCTET,read-only,,current,,The RTP canonical name of the receiver.
.1.3.6.1.2.1.87.1.7.1.4,RTP-MIB::rtpRcvrAddr,OCTET,read-only,,current,,The unicast transport address on which the receiver is receiving RTP packets and/or RTCP Receiver Reports.
.1.3.6.1.2.1.87.1.7.1.5,RTP-MIB::rtpRcvrRTT,Gauge32,read-only,,current,,The round trip time measurement taken by the source of the RTP stream based on the algorithm described on sec. 6 of RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications.' This algorithm can produce meaningful results when the RTP agent has the same clock as the stream sender (when the RTP monitor is also the sending host for the particular receiver). Otherwise, the entity should return 'noSuchInstance' in response to queries against rtpRcvrRTT.
.1.3.6.1.2.1.87.1.7.1.6,RTP-MIB::rtpRcvrLostPackets,Counter64,read-only,,current,,A count of RTP packets lost as observed by this receiver since rtpRcvrStartTime.
.1.3.6.1.2.1.87.1.7.1.7,RTP-MIB::rtpRcvrJitter,Gauge32,read-only,,current,,An estimate of delay variation as observed by this receiver. (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec.6.3.1 and A.8).
.1.3.6.1.2.1.87.1.7.1.8,RTP-MIB::rtpRcvrTool,OCTET,read-only,,current,,Name of the application program source of the stream.
.1.3.6.1.2.1.87.1.7.1.9,RTP-MIB::rtpRcvrRRs,Counter32,read-only,,current,,A count of the number of RTCP Receiver Reports that have been sent from this receiver, or observed if the RTP entity is a monitor, since rtpRcvrStartTime.
.1.3.6.1.2.1.87.1.7.1.10,RTP-MIB::rtpRcvrRRTime,TimeTicks,read-only,,current,,rtpRcvrRRTime is the value of SysUpTime at the time that the last RTCP Receiver Report was received from this receiver, in the case of a monitor or RR receiver (the RTP Sender). It is the value of SysUpTime at the time that the last RR was sent by this receiver in the case of an RTP receiver sending the RR.
.1.3.6.1.2.1.87.1.7.1.11,RTP-MIB::rtpRcvrPT,INTEGER,read-only,,current,,Static or dynamic payload type from the RTP header (see RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications' sec. 5).
.1.3.6.1.2.1.87.1.7.1.12,RTP-MIB::rtpRcvrPackets,Counter64,read-only,,current,,Count of RTP packets received by this RTP host receiver since rtpRcvrStartTime.
.1.3.6.1.2.1.87.1.7.1.13,RTP-MIB::rtpRcvrOctets,Counter64,read-only,,current,,Count of non-header RTP octets received by this receiving RTP host since rtpRcvrStartTime.
.1.3.6.1.2.1.87.1.7.1.14,RTP-MIB::rtpRcvrStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created.
.1.3.6.1.2.1.87.2,RTP-MIB::rtpConformance,,,,,,
.1.3.6.1.2.1.87.2.1,RTP-MIB::rtpGroups,,,,,,
.1.3.6.1.2.1.87.2.1.1,RTP-MIB::rtpSystemGroup,,,,,,Objects available to all RTP Systems.
.1.3.6.1.2.1.87.2.1.2,RTP-MIB::rtpHostGroup,,,,,,Objects that are available to RTP Host systems, but may not be available to RTP Monitor systems.
.1.3.6.1.2.1.87.2.1.3,RTP-MIB::rtpMonitorGroup,,,,,,Objects used to create rows in the RTP Session Table. These objects are not needed if the system does not create rows.
.1.3.6.1.2.1.87.2.1.4,RTP-MIB::rtpInverseGroup,,,,,,Objects used in the Inverse Lookup Tables.
.1.3.6.1.2.1.87.2.2,RTP-MIB::rtpCompliances,,,,,,
.1.3.6.1.2.1.87.2.2.1,RTP-MIB::rtpHostCompliance,,,,,,Host implementations MUST comply.
.1.3.6.1.2.1.87.2.2.2,RTP-MIB::rtpMonitorCompliance,,,,,,Monitor implementations must comply. RTP Monitors are not required to support creation or deletion.
.1.3.6.1.2.1.88,DISMAN-EVENT-MIB::dismanEventMIB,,,,,,The MIB module for defining event triggers and actions for network management purposes.
.1.3.6.1.2.1.88.1,DISMAN-EVENT-MIB::dismanEventMIBObjects,,,,,,
.1.3.6.1.2.1.88.1.1,DISMAN-EVENT-MIB::mteResource,,,,,,
.1.3.6.1.2.1.88.1.1.1,DISMAN-EVENT-MIB::mteResourceSampleMinimum,Integer32,read-write,,current,,The minimum mteTriggerFrequency this system will accept. A system may use the larger values of this minimum to lessen the impact of constant sampling. For larger sampling intervals the system samples less often and suffers less overhead. This object provides a way to enforce such lower overhead for all triggers created after it is set. Unless explicitly resource limited, a system's value for this object SHOULD be 1, allowing as small as a 1 second interval for ongoing trigger sampling. Changing this value will not invalidate an existing setting of mteTriggerFrequency.
.1.3.6.1.2.1.88.1.1.2,DISMAN-EVENT-MIB::mteResourceSampleInstanceMaximum,Unsigned32,read-write,,current,,The maximum number of instance entries this system will support for sampling. These are the entries that maintain state, one for each instance of each sampled object as selected by mteTriggerValueID. Note that wildcarded objects result in multiple instances of this state. A value of 0 indicates no preset limit, that is, the limit is dynamic based on system operation and resources. Unless explicitly resource limited, a system's value for this object SHOULD be 0. Changing this value will not eliminate or inhibit existing sample state but could prevent allocation of additional state information.
.1.3.6.1.2.1.88.1.1.3,DISMAN-EVENT-MIB::mteResourceSampleInstances,Gauge32,read-only,,current,,The number of currently active instance entries as defined for mteResourceSampleInstanceMaximum.
.1.3.6.1.2.1.88.1.1.4,DISMAN-EVENT-MIB::mteResourceSampleInstancesHigh,Gauge32,read-only,,current,,The highest value of mteResourceSampleInstances that has occurred since initialization of the management system.
.1.3.6.1.2.1.88.1.1.5,DISMAN-EVENT-MIB::mteResourceSampleInstanceLacks,Counter32,read-only,,current,,The number of times this system could not take a new sample because that allocation would have exceeded the limit set by mteResourceSampleInstanceMaximum.
.1.3.6.1.2.1.88.1.2,DISMAN-EVENT-MIB::mteTrigger,,,,,,
.1.3.6.1.2.1.88.1.2.1,DISMAN-EVENT-MIB::mteTriggerFailures,Counter32,read-only,,current,,The number of times an attempt to check for a trigger condition has failed. This counts individually for each attempt in a group of targets or each attempt for a wildcarded object.
.1.3.6.1.2.1.88.1.2.2,DISMAN-EVENT-MIB::mteTriggerTable,,not-accessible,,current,,A table of management event trigger information.
.1.3.6.1.2.1.88.1.2.2.1,DISMAN-EVENT-MIB::mteTriggerEntry,,not-accessible,mteOwner:IMPLIEDmteTriggerName,current,,Information about a single trigger. Applications create and delete entries using mteTriggerEntryStatus.
.1.3.6.1.2.1.88.1.2.2.1.1,DISMAN-EVENT-MIB::mteOwner,OCTET,not-accessible,,current,,The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
.1.3.6.1.2.1.88.1.2.2.1.2,DISMAN-EVENT-MIB::mteTriggerName,OCTET,not-accessible,,current,,A locally-unique, administratively assigned name for the trigger within the scope of mteOwner.
.1.3.6.1.2.1.88.1.2.2.1.3,DISMAN-EVENT-MIB::mteTriggerComment,OCTET,read-create,,current,,A description of the trigger's function and use.
.1.3.6.1.2.1.88.1.2.2.1.4,DISMAN-EVENT-MIB::mteTriggerTest,BITS,read-create,,current,existence(0):boolean(1):threshold(2),The type of trigger test to perform. For 'boolean' and 'threshold' tests, the object at mteTriggerValueID MUST evaluate to an integer, that is, anything that ends up encoded for transmission (that is, in BER, not ASN.1) as an integer. For 'existence', the specific test is as selected by mteTriggerExistenceTest. When an object appears, vanishes or changes value, the trigger fires. If the object's appearance caused the trigger firing, the object MUST vanish before the trigger can be fired again for it, and vice versa. If the trigger fired due to a change in the object's value, it will be fired again on every successive value change for that object. For 'boolean', the specific test is as selected by mteTriggerBooleanTest. If the test result is true the trigger fires. The trigger will not fire again until the value has become false and come back to true. For 'threshold' the test works as described below for mteTriggerThresholdStartup, mteTriggerThresholdRising, and mteTriggerThresholdFalling. Note that combining 'boolean' and 'threshold' tests on the same object may be somewhat redundant.
.1.3.6.1.2.1.88.1.2.2.1.5,DISMAN-EVENT-MIB::mteTriggerSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The type of sampling to perform. An 'absoluteValue' sample requires only a single sample to be meaningful, and is exactly the value of the object at mteTriggerValueID at the sample time. A 'deltaValue' requires two samples to be meaningful and is thus not available for testing until the second and subsequent samples after the object at mteTriggerValueID is first found to exist. It is the difference between the two samples. For unsigned values it is always positive, based on unsigned arithmetic. For signed values it can be positive or negative. For SNMP counters to be meaningful they should be sampled as a 'deltaValue'. For 'deltaValue' mteTriggerDeltaTable contains further parameters. If only 'existence' is set in mteTriggerTest this object has no meaning.
.1.3.6.1.2.1.88.1.2.2.1.6,DISMAN-EVENT-MIB::mteTriggerValueID,OBJECT,read-create,,current,,The object identifier of the MIB object to sample to see if the trigger should fire. This may be wildcarded by truncating all or part of the instance portion, in which case the value is obtained as if with a GetNext function, checking multiple values if they exist. If such wildcarding is applied, mteTriggerValueIDWildcard must be 'true' and if not it must be 'false'. Bad object identifiers or a mismatch between truncating the identifier and the value of mteTriggerValueIDWildcard result in operation as one would expect when providing the wrong identifier to a Get or GetNext operation. The Get will fail or get the wrong object. The GetNext will indeed get whatever is next, proceeding until it runs past the initial part of the identifier and perhaps many unintended objects for confusing results. If the value syntax of those objects is not usable, that results in a 'badType' error that terminates the scan. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
.1.3.6.1.2.1.88.1.2.2.1.7,DISMAN-EVENT-MIB::mteTriggerValueIDWildcard,INTEGER,read-create,,current,true(1):false(2),Control for whether mteTriggerValueID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard.
.1.3.6.1.2.1.88.1.2.2.1.8,DISMAN-EVENT-MIB::mteTriggerTargetTag,OCTET,read-create,,current,,The tag for the target(s) from which to obtain the condition for a trigger check. A length of 0 indicates the local system. In this case, access to the objects indicated by mteTriggerValueID is under the security credentials of the requester that set mteTriggerEntryStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. Otherwise access rights are checked according to the security parameters resulting from the tag.
.1.3.6.1.2.1.88.1.2.2.1.9,DISMAN-EVENT-MIB::mteTriggerContextName,OCTET,read-create,,current,,The management context from which to obtain mteTriggerValueID. This may be wildcarded by leaving characters off the end. For example use 'Repeater' to wildcard to 'Repeater1', 'Repeater2', 'Repeater-999.87b', and so on. To indicate such wildcarding is intended, mteTriggerContextNameWildcard must be 'true'. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time. Operation of this feature assumes that the local system has a list of available contexts against which to apply the wildcard. If the objects are being read from the local system, this is clearly the system's own list of contexts. For a remote system a local version of such a list is not defined by any current standard and may not be available, so this function MAY not be supported.
.1.3.6.1.2.1.88.1.2.2.1.10,DISMAN-EVENT-MIB::mteTriggerContextNameWildcard,INTEGER,read-create,,current,true(1):false(2),Control for whether mteTriggerContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard.
.1.3.6.1.2.1.88.1.2.2.1.11,DISMAN-EVENT-MIB::mteTriggerFrequency,Unsigned32,read-create,,current,,The number of seconds to wait between trigger samples. To encourage consistency in sampling, the interval is measured from the beginning of one check to the beginning of the next and the timer is restarted immediately when it expires, not when the check completes. If the next sample begins before the previous one completed the system may either attempt to make the check or treat this as an error condition with the error 'sampleOverrun'. A frequency of 0 indicates instantaneous recognition of the condition. This is not possible in many cases, but may be supported in cases where it makes sense and the system is able to do so. This feature allows the MIB to be used in implementations where such interrupt-driven behavior is possible and is not likely to be supported for all MIB objects even then since such sampling generally has to be tightly integrated into low-level code. Systems that can support this SHOULD document those cases where it can be used. In cases where it can not, setting this object to 0 should be disallowed.
.1.3.6.1.2.1.88.1.2.2.1.12,DISMAN-EVENT-MIB::mteTriggerObjectsOwner,OCTET,read-create,,current,,To go with mteTriggerObjects, the mteOwner of a group of objects from mteObjectsTable.
.1.3.6.1.2.1.88.1.2.2.1.13,DISMAN-EVENT-MIB::mteTriggerObjects,OCTET,read-create,,current,,The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger. A list of objects may also be added based on the event or on the value of mteTriggerTest. A length of 0 indicates no additional objects.
.1.3.6.1.2.1.88.1.2.2.1.14,DISMAN-EVENT-MIB::mteTriggerEnabled,INTEGER,read-create,,current,true(1):false(2),A control to allow a trigger to be configured but not used. When the value is 'false' the trigger is not sampled.
.1.3.6.1.2.1.88.1.2.2.1.15,DISMAN-EVENT-MIB::mteTriggerEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The control that allows creation and deletion of entries. Once made active an entry may not be modified except to delete it.
.1.3.6.1.2.1.88.1.2.3,DISMAN-EVENT-MIB::mteTriggerDeltaTable,,not-accessible,,current,,A table of management event trigger information for delta sampling.
.1.3.6.1.2.1.88.1.2.3.1,DISMAN-EVENT-MIB::mteTriggerDeltaEntry,,not-accessible,mteOwner:IMPLIEDmteTriggerName,current,,Information about a single trigger's delta sampling. Entries automatically exist in this this table for each mteTriggerEntry that has mteTriggerSampleType set to 'deltaValue'.
.1.3.6.1.2.1.88.1.2.3.1.1,DISMAN-EVENT-MIB::mteTriggerDeltaDiscontinuityID,OBJECT,read-write,,current,,The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or DateAndTime object that indicates a discontinuity in the value at mteTriggerValueID. The OID may be for a leaf object (e.g. sysUpTime.0) or may be wildcarded to match mteTriggerValueID. This object supports normal checking for a discontinuity in a counter. Note that if this object does not point to sysUpTime discontinuity checking MUST still check sysUpTime for an overall discontinuity. If the object identified is not accessible the sample attempt is in error, with the error code as from an SNMP request. Bad object identifiers or a mismatch between truncating the identifier and the value of mteDeltaDiscontinuityIDWildcard result in operation as one would expect when providing the wrong identifier to a Get operation. The Get will fail or get the wrong object. If the value syntax of those objects is not usable, that results in an error that terminates the sample with a 'badType' error code.
.1.3.6.1.2.1.88.1.2.3.1.2,DISMAN-EVENT-MIB::mteTriggerDeltaDiscontinuityIDWildcard,INTEGER,read-write,,current,true(1):false(2),Control for whether mteTriggerDeltaDiscontinuityID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. Note that the value of this object will be the same as that of the corresponding instance of mteTriggerValueIDWildcard when the corresponding mteTriggerSampleType is 'deltaValue'.
.1.3.6.1.2.1.88.1.2.3.1.3,DISMAN-EVENT-MIB::mteTriggerDeltaDiscontinuityIDType,INTEGER,read-write,,current,timeTicks(1):timeStamp(2):dateAndTime(3),The value 'timeTicks' indicates the mteTriggerDeltaDiscontinuityID of this row is of syntax TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. The value 'dateAndTime' indicates syntax DateAndTime.
.1.3.6.1.2.1.88.1.2.4,DISMAN-EVENT-MIB::mteTriggerExistenceTable,,not-accessible,,current,,A table of management event trigger information for existence triggers.
.1.3.6.1.2.1.88.1.2.4.1,DISMAN-EVENT-MIB::mteTriggerExistenceEntry,,not-accessible,mteOwner:IMPLIEDmteTriggerName,current,,Information about a single existence trigger. Entries automatically exist in this this table for each mteTriggerEntry that has 'existence' set in mteTriggerTest.
.1.3.6.1.2.1.88.1.2.4.1.1,DISMAN-EVENT-MIB::mteTriggerExistenceTest,BITS,read-write,,current,present(0):absent(1):changed(2),The type of existence test to perform. The trigger fires when the object at mteTriggerValueID is seen to go from present to absent, from absent to present, or to have it's value changed, depending on which tests are selected: present(0) - when this test is selected, the trigger fires when the mteTriggerValueID object goes from absent to present. absent(1) - when this test is selected, the trigger fires when the mteTriggerValueID object goes from present to absent. changed(2) - when this test is selected, the trigger fires the mteTriggerValueID object value changes. Once the trigger has fired for either presence or absence it will not fire again for that state until the object has been to the other state. 
.1.3.6.1.2.1.88.1.2.4.1.2,DISMAN-EVENT-MIB::mteTriggerExistenceStartup,BITS,read-write,,current,present(0):absent(1),Control for whether an event may be triggered when this entry is first set to 'active' and the test specified by mteTriggerExistenceTest is true. Setting an option causes that trigger to fire when its test is true.
.1.3.6.1.2.1.88.1.2.4.1.3,DISMAN-EVENT-MIB::mteTriggerExistenceObjectsOwner,OCTET,read-write,,current,,To go with mteTriggerExistenceObjects, the mteOwner of a group of objects from mteObjectsTable.
.1.3.6.1.2.1.88.1.2.4.1.4,DISMAN-EVENT-MIB::mteTriggerExistenceObjects,OCTET,read-write,,current,,The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test. A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest. A length of 0 indicates no additional objects.
.1.3.6.1.2.1.88.1.2.4.1.5,DISMAN-EVENT-MIB::mteTriggerExistenceEventOwner,OCTET,read-write,,current,,To go with mteTriggerExistenceEvent, the mteOwner of an event entry from the mteEventTable.
.1.3.6.1.2.1.88.1.2.4.1.6,DISMAN-EVENT-MIB::mteTriggerExistenceEvent,OCTET,read-write,,current,,The mteEventName of the event to invoke when mteTriggerType is 'existence' and this trigger fires. A length of 0 indicates no event.
.1.3.6.1.2.1.88.1.2.5,DISMAN-EVENT-MIB::mteTriggerBooleanTable,,not-accessible,,current,,A table of management event trigger information for boolean triggers.
.1.3.6.1.2.1.88.1.2.5.1,DISMAN-EVENT-MIB::mteTriggerBooleanEntry,,not-accessible,mteOwner:IMPLIEDmteTriggerName,current,,Information about a single boolean trigger. Entries automatically exist in this this table for each mteTriggerEntry that has 'boolean' set in mteTriggerTest.
.1.3.6.1.2.1.88.1.2.5.1.1,DISMAN-EVENT-MIB::mteTriggerBooleanComparison,INTEGER,read-write,,current,unequal(1):equal(2):less(3):lessOrEqual(4):greater(5):greaterOrEqual(6),The type of boolean comparison to perform. The value at mteTriggerValueID is compared to mteTriggerBooleanValue, so for example if mteTriggerBooleanComparison is 'less' the result would be true if the value at mteTriggerValueID is less than the value of mteTriggerBooleanValue.
.1.3.6.1.2.1.88.1.2.5.1.2,DISMAN-EVENT-MIB::mteTriggerBooleanValue,Integer32,read-write,,current,,The value to use for the test specified by mteTriggerBooleanTest.
.1.3.6.1.2.1.88.1.2.5.1.3,DISMAN-EVENT-MIB::mteTriggerBooleanStartup,INTEGER,read-write,,current,true(1):false(2),Control for whether an event may be triggered when this entry is first set to 'active' or a new instance of the object at mteTriggerValueID is found and the test specified by mteTriggerBooleanComparison is true. In that case an event is triggered if mteTriggerBooleanStartup is 'true'.
.1.3.6.1.2.1.88.1.2.5.1.4,DISMAN-EVENT-MIB::mteTriggerBooleanObjectsOwner,OCTET,read-write,,current,,To go with mteTriggerBooleanObjects, the mteOwner of a group of objects from mteObjectsTable.
.1.3.6.1.2.1.88.1.2.5.1.5,DISMAN-EVENT-MIB::mteTriggerBooleanObjects,OCTET,read-write,,current,,The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test. A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest. A length of 0 indicates no additional objects.
.1.3.6.1.2.1.88.1.2.5.1.6,DISMAN-EVENT-MIB::mteTriggerBooleanEventOwner,OCTET,read-write,,current,,To go with mteTriggerBooleanEvent, the mteOwner of an event entry from mteEventTable.
.1.3.6.1.2.1.88.1.2.5.1.7,DISMAN-EVENT-MIB::mteTriggerBooleanEvent,OCTET,read-write,,current,,The mteEventName of the event to invoke when mteTriggerType is 'boolean' and this trigger fires. A length of 0 indicates no event.
.1.3.6.1.2.1.88.1.2.6,DISMAN-EVENT-MIB::mteTriggerThresholdTable,,not-accessible,,current,,A table of management event trigger information for threshold triggers.
.1.3.6.1.2.1.88.1.2.6.1,DISMAN-EVENT-MIB::mteTriggerThresholdEntry,,not-accessible,mteOwner:IMPLIEDmteTriggerName,current,,Information about a single threshold trigger. Entries automatically exist in this table for each mteTriggerEntry that has 'threshold' set in mteTriggerTest.
.1.3.6.1.2.1.88.1.2.6.1.1,DISMAN-EVENT-MIB::mteTriggerThresholdStartup,INTEGER,read-write,,current,rising(1):falling(2):risingOrFalling(3),The event that may be triggered when this entry is first set to 'active' and a new instance of the object at mteTriggerValueID is found. If the first sample after this instance becomes active is greater than or equal to mteTriggerThresholdRising and mteTriggerThresholdStartup is equal to 'rising' or 'risingOrFalling', then one mteTriggerThresholdRisingEvent is triggered for that instance. If the first sample after this entry becomes active is less than or equal to mteTriggerThresholdFalling and mteTriggerThresholdStartup is equal to 'falling' or 'risingOrFalling', then one mteTriggerThresholdRisingEvent is triggered for that instance.
.1.3.6.1.2.1.88.1.2.6.1.2,DISMAN-EVENT-MIB::mteTriggerThresholdRising,Integer32,read-write,,current,,A threshold value to check against if mteTriggerType is 'threshold'. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, one mteTriggerThresholdRisingEvent is triggered. That event is also triggered if the first sample after this entry becomes active is greater than or equal to this threshold and mteTriggerThresholdStartup is equal to 'rising' or 'risingOrFalling'. After a rising event is generated, another such event is not triggered until the sampled value falls below this threshold and reaches mteTriggerThresholdFalling.
.1.3.6.1.2.1.88.1.2.6.1.3,DISMAN-EVENT-MIB::mteTriggerThresholdFalling,Integer32,read-write,,current,,A threshold value to check against if mteTriggerType is 'threshold'. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, one mteTriggerThresholdFallingEvent is triggered. That event is also triggered if the first sample after this entry becomes active is less than or equal to this threshold and mteTriggerThresholdStartup is equal to 'falling' or 'risingOrFalling'. After a falling event is generated, another such event is not triggered until the sampled value rises above this threshold and reaches mteTriggerThresholdRising.
.1.3.6.1.2.1.88.1.2.6.1.4,DISMAN-EVENT-MIB::mteTriggerThresholdDeltaRising,Integer32,read-write,,current,,A threshold value to check against if mteTriggerType is 'threshold'. When the delta value (difference) between the current sampled value (value(n)) and the previous sampled value (value(n-1)) is greater than or equal to this threshold, and the delta value calculated at the last sampling interval (i.e. value(n-1) - value(n-2)) was less than this threshold, one mteTriggerThresholdDeltaRisingEvent is triggered. That event is also triggered if the first delta value calculated after this entry becomes active, i.e. value(2) - value(1), where value(1) is the first sample taken of that instance, is greater than or equal to this threshold. After a rising event is generated, another such event is not triggered until the delta value falls below this threshold and reaches mteTriggerThresholdDeltaFalling.
.1.3.6.1.2.1.88.1.2.6.1.5,DISMAN-EVENT-MIB::mteTriggerThresholdDeltaFalling,Integer32,read-write,,current,,A threshold value to check against if mteTriggerType is 'threshold'. When the delta value (difference) between the current sampled value (value(n)) and the previous sampled value (value(n-1)) is less than or equal to this threshold, and the delta value calculated at the last sampling interval (i.e. value(n-1) - value(n-2)) was greater than this threshold, one mteTriggerThresholdDeltaFallingEvent is triggered. That event is also triggered if the first delta value calculated after this entry becomes active, i.e. value(2) - value(1), where value(1) is the first sample taken of that instance, is less than or equal to this threshold. After a falling event is generated, another such event is not triggered until the delta value falls below this threshold and reaches mteTriggerThresholdDeltaRising.
.1.3.6.1.2.1.88.1.2.6.1.6,DISMAN-EVENT-MIB::mteTriggerThresholdObjectsOwner,OCTET,read-write,,current,,To go with mteTriggerThresholdObjects, the mteOwner of a group of objects from mteObjectsTable.
.1.3.6.1.2.1.88.1.2.6.1.7,DISMAN-EVENT-MIB::mteTriggerThresholdObjects,OCTET,read-write,,current,,The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test. A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest. A length of 0 indicates no additional objects.
.1.3.6.1.2.1.88.1.2.6.1.8,DISMAN-EVENT-MIB::mteTriggerThresholdRisingEventOwner,OCTET,read-write,,current,,To go with mteTriggerThresholdRisingEvent, the mteOwner of an event entry from mteEventTable.
.1.3.6.1.2.1.88.1.2.6.1.9,DISMAN-EVENT-MIB::mteTriggerThresholdRisingEvent,OCTET,read-write,,current,,The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdRising. A length of 0 indicates no event.
.1.3.6.1.2.1.88.1.2.6.1.10,DISMAN-EVENT-MIB::mteTriggerThresholdFallingEventOwner,OCTET,read-write,,current,,To go with mteTriggerThresholdFallingEvent, the mteOwner of an event entry from mteEventTable.
.1.3.6.1.2.1.88.1.2.6.1.11,DISMAN-EVENT-MIB::mteTriggerThresholdFallingEvent,OCTET,read-write,,current,,The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdFalling. A length of 0 indicates no event.
.1.3.6.1.2.1.88.1.2.6.1.12,DISMAN-EVENT-MIB::mteTriggerThresholdDeltaRisingEventOwner,OCTET,read-write,,current,,To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner of an event entry from mteEventTable.
.1.3.6.1.2.1.88.1.2.6.1.13,DISMAN-EVENT-MIB::mteTriggerThresholdDeltaRisingEvent,OCTET,read-write,,current,,The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdDeltaRising. A length of 0 indicates no event.
.1.3.6.1.2.1.88.1.2.6.1.14,DISMAN-EVENT-MIB::mteTriggerThresholdDeltaFallingEventOwner,OCTET,read-write,,current,,To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner of an event entry from mteEventTable.
.1.3.6.1.2.1.88.1.2.6.1.15,DISMAN-EVENT-MIB::mteTriggerThresholdDeltaFallingEvent,OCTET,read-write,,current,,The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdDeltaFalling. A length of 0 indicates no event.
.1.3.6.1.2.1.88.1.3,DISMAN-EVENT-MIB::mteObjects,,,,,,
.1.3.6.1.2.1.88.1.3.1,DISMAN-EVENT-MIB::mteObjectsTable,,not-accessible,,current,,A table of objects that can be added to notifications based on the trigger, trigger test, or event, as pointed to by entries in those tables.
.1.3.6.1.2.1.88.1.3.1.1,DISMAN-EVENT-MIB::mteObjectsEntry,,not-accessible,mteOwner:mteObjectsName:mteObjectsIndex,current,,A group of objects. Applications create and delete entries using mteObjectsEntryStatus. When adding objects to a notification they are added in the lexical order of their index in this table. Those associated with a trigger come first, then trigger test, then event.
.1.3.6.1.2.1.88.1.3.1.1.1,DISMAN-EVENT-MIB::mteObjectsName,OCTET,not-accessible,,current,,A locally-unique, administratively assigned name for a group of objects.
.1.3.6.1.2.1.88.1.3.1.1.2,DISMAN-EVENT-MIB::mteObjectsIndex,Unsigned32,not-accessible,,current,,An arbitrary integer for the purpose of identifying individual objects within a mteObjectsName group. Objects within a group are placed in the notification in the numerical order of this index. Groups are placed in the notification in the order of the selections for overall trigger, trigger test, and event. Within trigger test they are in the same order as the numerical values of the bits defined for mteTriggerTest. Bad object identifiers or a mismatch between truncating the identifier and the value of mteDeltaDiscontinuityIDWildcard result in operation as one would expect when providing the wrong identifier to a Get operation. The Get will fail or get the wrong object. If the object is not available it is omitted from the notification.
.1.3.6.1.2.1.88.1.3.1.1.3,DISMAN-EVENT-MIB::mteObjectsID,OBJECT,read-create,,current,,The object identifier of a MIB object to add to a Notification that results from the firing of a trigger. This may be wildcarded by truncating all or part of the instance portion, in which case the instance portion of the OID for obtaining this object will be the same as that used in obtaining the mteTriggerValueID that fired. If such wildcarding is applied, mteObjectsIDWildcard must be 'true' and if not it must be 'false'. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
.1.3.6.1.2.1.88.1.3.1.1.4,DISMAN-EVENT-MIB::mteObjectsIDWildcard,INTEGER,read-create,,current,true(1):false(2),Control for whether mteObjectsID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard.
.1.3.6.1.2.1.88.1.3.1.1.5,DISMAN-EVENT-MIB::mteObjectsEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The control that allows creation and deletion of entries. Once made active an entry MAY not be modified except to delete it.
.1.3.6.1.2.1.88.1.4,DISMAN-EVENT-MIB::mteEvent,,,,,,
.1.3.6.1.2.1.88.1.4.1,DISMAN-EVENT-MIB::mteEventFailures,Counter32,read-only,,current,,The number of times an attempt to invoke an event has failed. This counts individually for each attempt in a group of targets or each attempt for a wildcarded trigger object.
.1.3.6.1.2.1.88.1.4.2,DISMAN-EVENT-MIB::mteEventTable,,not-accessible,,current,,A table of management event action information.
.1.3.6.1.2.1.88.1.4.2.1,DISMAN-EVENT-MIB::mteEventEntry,,not-accessible,mteOwner:IMPLIEDmteEventName,current,,Information about a single event. Applications create and delete entries using mteEventEntryStatus.
.1.3.6.1.2.1.88.1.4.2.1.1,DISMAN-EVENT-MIB::mteEventName,OCTET,not-accessible,,current,,A locally-unique, administratively assigned name for the event.
.1.3.6.1.2.1.88.1.4.2.1.2,DISMAN-EVENT-MIB::mteEventComment,OCTET,read-create,,current,,A description of the event's function and use.
.1.3.6.1.2.1.88.1.4.2.1.3,DISMAN-EVENT-MIB::mteEventActions,BITS,read-create,,current,notification(0):set(1),The actions to perform when this event occurs. For 'notification', Traps and/or Informs are sent according to the configuration in the SNMP Notification MIB. For 'set', an SNMP Set operation is performed according to control values in this entry.
.1.3.6.1.2.1.88.1.4.2.1.4,DISMAN-EVENT-MIB::mteEventEnabled,INTEGER,read-create,,current,true(1):false(2),A control to allow an event to be configured but not used. When the value is 'false' the event does not execute even if triggered.
.1.3.6.1.2.1.88.1.4.2.1.5,DISMAN-EVENT-MIB::mteEventEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The control that allows creation and deletion of entries. Once made active an entry MAY not be modified except to delete it.
.1.3.6.1.2.1.88.1.4.3,DISMAN-EVENT-MIB::mteEventNotificationTable,,not-accessible,,current,,A table of information about notifications to be sent as a consequence of management events.
.1.3.6.1.2.1.88.1.4.3.1,DISMAN-EVENT-MIB::mteEventNotificationEntry,,not-accessible,mteOwner:IMPLIEDmteEventName,current,,Information about a single event's notification. Entries automatically exist in this this table for each mteEventEntry that has 'notification' set in mteEventActions.
.1.3.6.1.2.1.88.1.4.3.1.1,DISMAN-EVENT-MIB::mteEventNotification,OBJECT,read-write,,current,,The object identifier from the NOTIFICATION-TYPE for the notification to use if metEventActions has 'notification' set.
.1.3.6.1.2.1.88.1.4.3.1.2,DISMAN-EVENT-MIB::mteEventNotificationObjectsOwner,OCTET,read-write,,current,,To go with mteEventNotificationObjects, the mteOwner of a group of objects from mteObjectsTable.
.1.3.6.1.2.1.88.1.4.3.1.3,DISMAN-EVENT-MIB::mteEventNotificationObjects,OCTET,read-write,,current,,The mteObjectsName of a group of objects from mteObjectsTable if mteEventActions has 'notification' set. These objects are to be added to any Notification generated by this event. Objects may also be added based on the trigger that stimulated the event. A length of 0 indicates no additional objects.
.1.3.6.1.2.1.88.1.4.4,DISMAN-EVENT-MIB::mteEventSetTable,,not-accessible,,current,,A table of management event action information.
.1.3.6.1.2.1.88.1.4.4.1,DISMAN-EVENT-MIB::mteEventSetEntry,,not-accessible,mteOwner:IMPLIEDmteEventName,current,,Information about a single event's set option. Entries automatically exist in this this table for each mteEventEntry that has 'set' set in mteEventActions.
.1.3.6.1.2.1.88.1.4.4.1.1,DISMAN-EVENT-MIB::mteEventSetObject,OBJECT,read-write,,current,,The object identifier from the MIB object to set if mteEventActions has 'set' set. This object identifier may be wildcarded by leaving sub-identifiers off the end, in which case nteEventSetObjectWildCard must be 'true'. If mteEventSetObject is wildcarded the instance used to set the object to which it points is the same as the instance from the value of mteTriggerValueID that triggered the event. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time. Bad object identifiers or a mismatch between truncating the identifier and the value of mteSetObjectWildcard result in operation as one would expect when providing the wrong identifier to a Set operation. The Set will fail or set the wrong object. If the value syntax of the destination object is not correct, the Set fails with the normal SNMP error code.
.1.3.6.1.2.1.88.1.4.4.1.2,DISMAN-EVENT-MIB::mteEventSetObjectWildcard,INTEGER,read-write,,current,true(1):false(2),Control over whether mteEventSetObject is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard if mteEventActions has 'set' set.
.1.3.6.1.2.1.88.1.4.4.1.3,DISMAN-EVENT-MIB::mteEventSetValue,Integer32,read-write,,current,,The value to which to set the object at mteEventSetObject if mteEventActions has 'set' set.
.1.3.6.1.2.1.88.1.4.4.1.4,DISMAN-EVENT-MIB::mteEventSetTargetTag,OCTET,read-write,,current,,The tag for the target(s) at which to set the object at mteEventSetObject to mteEventSetValue if mteEventActions has 'set' set. Systems limited to self management MAY reject a non-zero length for the value of this object. A length of 0 indicates the local system. In this case, access to the objects indicated by mteEventSetObject is under the security credentials of the requester that set mteTriggerEntryStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. Otherwise access rights are checked according to the security parameters resulting from the tag.
.1.3.6.1.2.1.88.1.4.4.1.5,DISMAN-EVENT-MIB::mteEventSetContextName,OCTET,read-write,,current,,The management context in which to set mteEventObjectID. if mteEventActions has 'set' set. This may be wildcarded by leaving characters off the end. To indicate such wildcarding mteEventSetContextNameWildcard must be 'true'. If this context name is wildcarded the value used to complete the wildcarding of mteTriggerContextName will be appended.
.1.3.6.1.2.1.88.1.4.4.1.6,DISMAN-EVENT-MIB::mteEventSetContextNameWildcard,INTEGER,read-write,,current,true(1):false(2),Control for whether mteEventSetContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard if mteEventActions has 'set' set.
.1.3.6.1.2.1.88.2,DISMAN-EVENT-MIB::dismanEventMIBNotificationPrefix,,,,,,
.1.3.6.1.2.1.88.2.0,DISMAN-EVENT-MIB::dismanEventMIBNotifications,,,,,,
.1.3.6.1.2.1.88.2.0.1,DISMAN-EVENT-MIB::mteTriggerFired,,,,,,Notification that the trigger indicated by the object instances has fired, for triggers with mteTriggerType 'boolean' or 'existence'.
.1.3.6.1.2.1.88.2.0.2,DISMAN-EVENT-MIB::mteTriggerRising,,,,,,Notification that the rising threshold was met for triggers with mteTriggerType 'threshold'.
.1.3.6.1.2.1.88.2.0.3,DISMAN-EVENT-MIB::mteTriggerFalling,,,,,,Notification that the falling threshold was met for triggers with mteTriggerType 'threshold'.
.1.3.6.1.2.1.88.2.0.4,DISMAN-EVENT-MIB::mteTriggerFailure,,,,,,Notification that an attempt to check a trigger has failed. The network manager must enable this notification only with a certain fear and trembling, as it can easily crowd out more important information. It should be used only to help diagnose a problem that has appeared in the error counters and can not be found otherwise.
.1.3.6.1.2.1.88.2.0.5,DISMAN-EVENT-MIB::mteEventSetFailure,,,,,,Notification that an attempt to do a set in response to an event has failed. The network manager must enable this notification only with a certain fear and trembling, as it can easily crowd out more important information. It should be used only to help diagnose a problem that has appeared in the error counters and can not be found otherwise.
.1.3.6.1.2.1.88.2.1,DISMAN-EVENT-MIB::dismanEventMIBNotificationObjects,,,,,,
.1.3.6.1.2.1.88.2.1.1,DISMAN-EVENT-MIB::mteHotTrigger,OCTET,accessible-for-notify,,current,,The name of the trigger causing the notification.
.1.3.6.1.2.1.88.2.1.2,DISMAN-EVENT-MIB::mteHotTargetName,OCTET,accessible-for-notify,,current,,The SNMP Target MIB's snmpTargetAddrName related to the notification.
.1.3.6.1.2.1.88.2.1.3,DISMAN-EVENT-MIB::mteHotContextName,OCTET,accessible-for-notify,,current,,The context name related to the notification. This MUST be as fully-qualified as possible, including filling in wildcard information determined in processing.
.1.3.6.1.2.1.88.2.1.4,DISMAN-EVENT-MIB::mteHotOID,OBJECT,accessible-for-notify,,current,,The object identifier of the destination object related to the notification. This MUST be as fully-qualified as possible, including filling in wildcard information determined in processing. For a trigger-related notification this is from mteTriggerValueID. For a set failure this is from mteEventSetObject.
.1.3.6.1.2.1.88.2.1.5,DISMAN-EVENT-MIB::mteHotValue,Integer32,accessible-for-notify,,current,,The value of the object at mteTriggerValueID when a trigger fired.
.1.3.6.1.2.1.88.2.1.6,DISMAN-EVENT-MIB::mteFailedReason,INTEGER,accessible-for-notify,,current,localResourceLack(-1):badDestination(-2):destinationUnreachable(-3):noResponse(-4):badType(-5):sampleOverrun(-6):noError(0):tooBig(1):noSuchName(2):badValue(3):readOnly(4):genErr(5):noAccess(6):wrongType(7):wrongLength(8):wrongEncoding(9):wrongValue(10):noCreation(11):inconsistentValue(12):resourceUnavailable(13):commitFailed(14):undoFailed(15):authorizationError(16):notWritable(17):inconsistentName(18),The reason for the failure of an attempt to check for a trigger condition or set an object in response to an event.
.1.3.6.1.2.1.88.3,DISMAN-EVENT-MIB::dismanEventMIBConformance,,,,,,
.1.3.6.1.2.1.88.3.1,DISMAN-EVENT-MIB::dismanEventMIBCompliances,,,,,,
.1.3.6.1.2.1.88.3.1.1,DISMAN-EVENT-MIB::dismanEventMIBCompliance,,,,,,The compliance statement for entities which implement the Event MIB.
.1.3.6.1.2.1.88.3.2,DISMAN-EVENT-MIB::dismanEventMIBGroups,,,,,,
.1.3.6.1.2.1.88.3.2.1,DISMAN-EVENT-MIB::dismanEventResourceGroup,,,,,,Event resource status and control objects.
.1.3.6.1.2.1.88.3.2.2,DISMAN-EVENT-MIB::dismanEventTriggerGroup,,,,,,Event triggers.
.1.3.6.1.2.1.88.3.2.3,DISMAN-EVENT-MIB::dismanEventObjectsGroup,,,,,,Supplemental objects.
.1.3.6.1.2.1.88.3.2.4,DISMAN-EVENT-MIB::dismanEventEventGroup,,,,,,Events.
.1.3.6.1.2.1.88.3.2.5,DISMAN-EVENT-MIB::dismanEventNotificationObjectGroup,,,,,,Notification objects.
.1.3.6.1.2.1.88.3.2.6,DISMAN-EVENT-MIB::dismanEventNotificationGroup,,,,,,Notifications.
.1.3.6.1.2.1.89,COPS-CLIENT-MIB::copsClientMIB,,,,,,The COPS Client MIB module
.1.3.6.1.2.1.89.1,COPS-CLIENT-MIB::copsClientMIBObjects,,,,,,
.1.3.6.1.2.1.89.1.1,COPS-CLIENT-MIB::copsClientCapabilitiesGroup,,,,,,
.1.3.6.1.2.1.89.1.1.1,COPS-CLIENT-MIB::copsClientCapabilities,BITS,read-only,,current,copsClientVersion1(0):copsClientAuthIpSecAh(1):copsClientAuthIpSecEsp(2):copsClientAuthTls(3):copsClientAuthInteg(4),A list of the optional capabilities that this COPS client supports.
.1.3.6.1.2.1.89.1.2,COPS-CLIENT-MIB::copsClientStatusGroup,,,,,,
.1.3.6.1.2.1.89.1.2.1,COPS-CLIENT-MIB::copsClientServerCurrentTable,,not-accessible,,current,,A table of information regarding COPS servers as seen from the point of view of a COPS client. This table contains entries for both statically-configured and dynamically-learned servers (from a PDP Redirect operation). One entry exists in this table for each COPS Client-Type served by the COPS server. In addition, an entry will exist with copsClientServerClientType 0 (zero) representing information about the underlying connection itself: this is consistent with the COPS specification which reserves this value for this purpose.
.1.3.6.1.2.1.89.1.2.1.1,COPS-CLIENT-MIB::copsClientServerCurrentEntry,,not-accessible,copsClientServerAddressType:copsClientServerAddress:copsClientServerClientType,current,,A set of information regarding a single COPS server serving a single COPS Client-Type from the point of view of a COPS client.
.1.3.6.1.2.1.89.1.2.1.1.1,COPS-CLIENT-MIB::copsClientServerAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address in copsClientServerAddress.
.1.3.6.1.2.1.89.1.2.1.1.2,COPS-CLIENT-MIB::copsClientServerAddress,OCTET,not-accessible,,current,,The IPv4, IPv6 or DNS address of a COPS Server. Note that, since this is an index to the table, the DNS name must be short enough to fit into the maximum length of indices allowed by the management protocol in use.
.1.3.6.1.2.1.89.1.2.1.1.3,COPS-CLIENT-MIB::copsClientServerClientType,INTEGER,not-accessible,,current,,The COPS protocol Client-Type for which this entry applies. Multiple Client-Types can be served by a single COPS server. The value 0 (zero) indicates that this entry contains information about the underlying connection itself.
.1.3.6.1.2.1.89.1.2.1.1.4,COPS-CLIENT-MIB::copsClientServerTcpPort,INTEGER,read-only,,current,,The TCP port number on the COPS server to which the client should connect/is connected.
.1.3.6.1.2.1.89.1.2.1.1.5,COPS-CLIENT-MIB::copsClientServerType,INTEGER,read-only,,current,copsServerStatic(1):copsServerRedirect(2),Indicator of the source of this COPS server information. COPS servers may be configured by network management into copsClientServerConfigTable and appear in this entry with type copsServerStatic(1). Alternatively, the may be notified from another COPS server by means of the COPS PDP-Redirect mechanism and appear as copsServerRedirect(2).
.1.3.6.1.2.1.89.1.2.1.1.6,COPS-CLIENT-MIB::copsClientServerAuthType,INTEGER,read-only,,current,authNone(0):authOther(1):authIpSecAh(2):authIpSecEsp(3):authTls(4):authCopsIntegrity(5),Indicator of the current security mode in use between client and this COPS server.
.1.3.6.1.2.1.89.1.2.1.1.7,COPS-CLIENT-MIB::copsClientServerLastConnAttempt,TimeTicks,read-only,,current,,Timestamp of the last time that this client attempted to connect to this COPS server.
.1.3.6.1.2.1.89.1.2.1.1.8,COPS-CLIENT-MIB::copsClientState,INTEGER,read-only,,current,copsClientInvalid(1):copsClientTcpconnected(2):copsClientAuthenticating(3):copsClientSecAccepted(4):copsClientAccepted(5):copsClientTimingout(6),The state of the connection and COPS protocol with respect to this COPS server.
.1.3.6.1.2.1.89.1.2.1.1.9,COPS-CLIENT-MIB::copsClientServerKeepaliveTime,INTEGER,read-only,,current,,The value of the COPS protocol Keepalive timeout, in centiseconds, currently in use by this client, as specified by this COPS server in the Client-Accept operation. A value of zero indicates no keepalive activity is expected.
.1.3.6.1.2.1.89.1.2.1.1.10,COPS-CLIENT-MIB::copsClientServerAccountingTime,INTEGER,read-only,,current,,The value of the COPS protocol Accounting timeout, in centiseconds, currently in use by this client, as specified by the COPS server in the Client-Accept operation. A value of zero indicates no accounting activity is to be performed.
.1.3.6.1.2.1.89.1.2.1.1.11,COPS-CLIENT-MIB::copsClientInPkts,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from this COPS server marked for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.12,COPS-CLIENT-MIB::copsClientOutPkts,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has sent to this COPS server marked for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.13,COPS-CLIENT-MIB::copsClientInErrs,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from this COPS server marked for this Client-Type that contained errors in syntax. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.14,COPS-CLIENT-MIB::copsClientLastError,INTEGER,read-only,,current,errorOther(0):errorBadHandle(1):errorInvalidHandleReference(2):errorBadMessageFormat(3):errorUnableToProcess(4):errorMandatoryClientSiMissing(5):errorUnsupportedClientType(6):errorMandatoryCopsObjectMissing(7):errorClientFailure(8):errorCommunicationFailure(9):errorUnspecified(10):errorShuttingDown(11):errorRedirectToPreferredServer(12):errorUnknownCopsObject(13):errorAuthenticationFailure(14):errorAuthenticationMissing(15),The code contained in the last COPS protocol Error Object received by this client from this COPS server marked for this Client-Type. This value is not zeroed on COPS Client-Open operations.
.1.3.6.1.2.1.89.1.2.1.1.15,COPS-CLIENT-MIB::copsClientTcpConnectAttempts,Counter32,read-only,,current,,A count of the number of times that this COPS client has tried (successfully or otherwise) to open an TCP connection to a COPS server. This value is cumulative since agent restart and is not zeroed on new connections. This value is not incremented for entries representing a non-zero Client-Type.
.1.3.6.1.2.1.89.1.2.1.1.16,COPS-CLIENT-MIB::copsClientTcpConnectFailures,Counter32,read-only,,current,,A count of the number of times that this COPS client has failed to open an TCP connection to a COPS server. This value is cumulative since agent restart and is not zeroed on new connections. This value is not incremented for entries representing a non-zero Client-Type.
.1.3.6.1.2.1.89.1.2.1.1.17,COPS-CLIENT-MIB::copsClientOpenAttempts,Counter32,read-only,,current,,A count of the number of times that this COPS client has tried to perform a COPS Client-Open to a COPS server for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.18,COPS-CLIENT-MIB::copsClientOpenFailures,Counter32,read-only,,current,,A count of the number of times that this COPS client has failed to perform a COPS Client-Open to a COPS server for this Client-Type. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.19,COPS-CLIENT-MIB::copsClientErrUnsupportClienttype,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers that referred to Client-Types that are unsupported by this client. This value is cumulative since agent restart and is not zeroed on new connections. This value is not incremented for entries representing a non-zero Client-Type.
.1.3.6.1.2.1.89.1.2.1.1.20,COPS-CLIENT-MIB::copsClientErrUnsupportedVersion,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Version number that is unsupported by this client. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.21,COPS-CLIENT-MIB::copsClientErrLengthMismatch,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Message Length that did not match the actual received message. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.22,COPS-CLIENT-MIB::copsClientErrUnknownOpcode,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Op Code that was unrecognised by this client. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.23,COPS-CLIENT-MIB::copsClientErrUnknownCnum,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that contained a COPS protocol object C-Num that was unrecognised by this client. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.24,COPS-CLIENT-MIB::copsClientErrBadCtype,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that contained a COPS protocol object C-Type that was not defined for the C-Nums known by this client. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.25,COPS-CLIENT-MIB::copsClientErrBadSends,Counter32,read-only,,current,,A count of the total number of COPS messages that this client attempted to send to COPS servers marked for this Client-Type that resulted in a transmit error. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.26,COPS-CLIENT-MIB::copsClientErrWrongObjects,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that did not contain a permitted set of COPS protocol objects. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.27,COPS-CLIENT-MIB::copsClientErrWrongOpcode,Counter32,read-only,,current,,A count of the total number of COPS messages that this client has received from COPS servers marked for this Client-Type that had a COPS protocol Op Code that should not have been sent to a COPS client e.g. Open-Requests. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.28,COPS-CLIENT-MIB::copsClientKaTimedoutClients,Counter32,read-only,,current,,A count of the total number of times that this client has been shut down for this Client-Type by COPS servers that had detected a COPS protocol Keepalive timeout. This value is cumulative since agent restart and is not zeroed on new connections.
.1.3.6.1.2.1.89.1.2.1.1.29,COPS-CLIENT-MIB::copsClientErrAuthFailures,Counter32,read-only,,current,,A count of the total number of times that this client has received a COPS message marked for this Client-Type which could not be authenticated using the authentication mechanism used by this client.
.1.3.6.1.2.1.89.1.2.1.1.30,COPS-CLIENT-MIB::copsClientErrAuthMissing,Counter32,read-only,,current,,A count of the total number of times that this client has received a COPS message marked for this Client-Type which did not contain authentication information.
.1.3.6.1.2.1.89.1.3,COPS-CLIENT-MIB::copsClientConfigGroup,,,,,,
.1.3.6.1.2.1.89.1.3.1,COPS-CLIENT-MIB::copsClientServerConfigTable,,not-accessible,,current,,Table of possible COPS servers to try to connect to in order of copsClientServerConfigPriority. There may be multiple entries in this table for the same server and client-type which specify different security mechanisms: these mechanisms will be attempted by the client in the priority order given. Note that a server learned by means of PDPRedirect always takes priority over any of these configured entries.
.1.3.6.1.2.1.89.1.3.1.1,COPS-CLIENT-MIB::copsClientServerConfigEntry,,not-accessible,copsClientServerConfigAddrType:copsClientServerConfigAddress:copsClientServerConfigClientType:copsClientServerConfigAuthType,current,,A set of configuration information regarding a single COPS server from the point of view of a COPS client.
.1.3.6.1.2.1.89.1.3.1.1.1,COPS-CLIENT-MIB::copsClientServerConfigAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address in copsClientServerConfigAddress.
.1.3.6.1.2.1.89.1.3.1.1.2,COPS-CLIENT-MIB::copsClientServerConfigAddress,OCTET,not-accessible,,current,,The IPv4, IPv6 or DNS address of a COPS Server. Note that, since this is an index to the table, the DNS name must be short enough to fit into the maximum length of indices allowed by the management protocol in use.
.1.3.6.1.2.1.89.1.3.1.1.3,COPS-CLIENT-MIB::copsClientServerConfigClientType,INTEGER,not-accessible,,current,,The COPS protocol Client-Type for which this entry applies and for which this COPS server is capable of serving. Multiple Client-Types can be served by a single COPS server.
.1.3.6.1.2.1.89.1.3.1.1.4,COPS-CLIENT-MIB::copsClientServerConfigAuthType,INTEGER,not-accessible,,current,authNone(0):authOther(1):authIpSecAh(2):authIpSecEsp(3):authTls(4):authCopsIntegrity(5),The type of authentication mechanism for this COPS client to request when negotiating security at the start of a connection to a COPS server.
.1.3.6.1.2.1.89.1.3.1.1.5,COPS-CLIENT-MIB::copsClientServerConfigTcpPort,INTEGER,read-create,,current,,The TCP port number on the COPS server to which the client should connect.
.1.3.6.1.2.1.89.1.3.1.1.6,COPS-CLIENT-MIB::copsClientServerConfigPriority,Integer32,read-create,,current,,The priority of this entry relative to other entries. COPS client will attempt to contact COPS servers for the appropriate Client-Type. Higher numbers are tried first. The order to be used amongst server entries with the same priority is undefined. COPS servers that are notified to the client using the COPS protocol PDP-Redirect mechanism are always used in preference to any entries in this table.
.1.3.6.1.2.1.89.1.3.1.1.7,COPS-CLIENT-MIB::copsClientServerConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),State of this entry in the table.
.1.3.6.1.2.1.89.1.3.2,COPS-CLIENT-MIB::copsClientServerConfigRetryAlgrm,INTEGER,read-write,,current,other(1):sequential(2):roundRobin(3),The algorithm by which the client should retry when it fails to connect to a COPS server.
.1.3.6.1.2.1.89.1.3.3,COPS-CLIENT-MIB::copsClientServerConfigRetryCount,Unsigned32,read-write,,current,,A retry count for use by the retry algorithm. Each retry algorithm needs to specify how it uses this value. For the 'sequential(2)' algorithm, this value is the number of times the client should retry to connect to one COPS server before moving on to another. For the 'roundRobin(3)' algorithm, this value is not used.
.1.3.6.1.2.1.89.1.3.4,COPS-CLIENT-MIB::copsClientServerConfigRetryIntvl,INTEGER,read-write,,current,,A retry interval for use by the retry algorithm. Each retry algorithm needs to specify how it uses this value. For the 'sequential(2)' algorithm, this value is the time to wait between retries of a connection to the same COPS server. For the 'roundRobin(3)' algorithm, the client always attempts to connect to each Server in turn, until one succeeds or they all fail; if they all fail, then the client waits for the value of this interval before restarting the algorithm.
.1.3.6.1.2.1.89.2,COPS-CLIENT-MIB::copsClientConformance,,,,,,
.1.3.6.1.2.1.89.2.1,COPS-CLIENT-MIB::copsClientGroups,,,,,,
.1.3.6.1.2.1.89.2.1.1,COPS-CLIENT-MIB::copsDeviceStatusGroup,,,,,,A collection of objects for monitoring the status of connections to COPS servers and statistics for a COPS client.
.1.3.6.1.2.1.89.2.1.2,COPS-CLIENT-MIB::copsDeviceConfigGroup,,,,,,A collection of objects for configuring COPS server information.
.1.3.6.1.2.1.89.2.2,COPS-CLIENT-MIB::copsClientCompliances,,,,,,
.1.3.6.1.2.1.89.2.2.1,COPS-CLIENT-MIB::copsClientCompliance,,,,,,The compliance statement for device support of management of the COPS client.
.1.3.6.1.2.1.90,DISMAN-EXPRESSION-MIB::dismanExpressionMIB,,,,,,The MIB module for defining expressions of MIB objects for management purposes.
.1.3.6.1.2.1.90.1,DISMAN-EXPRESSION-MIB::dismanExpressionMIBObjects,,,,,,
.1.3.6.1.2.1.90.1.1,DISMAN-EXPRESSION-MIB::expResource,,,,,,
.1.3.6.1.2.1.90.1.1.1,DISMAN-EXPRESSION-MIB::expResourceDeltaMinimum,Integer32,read-write,,current,,The minimum expExpressionDeltaInterval this system will accept. A system may use the larger values of this minimum to lessen the impact of constantly computing deltas. For larger delta sampling intervals the system samples less often and suffers less overhead. This object provides a way to enforce such lower overhead for all expressions created after it is set. The value -1 indicates that expResourceDeltaMinimum is irrelevant as the system will not accept 'deltaValue' as a value for expObjectSampleType. Unless explicitly resource limited, a system's value for this object should be 1, allowing as small as a 1 second interval for ongoing delta sampling. Changing this value will not invalidate an existing setting of expObjectSampleType.
.1.3.6.1.2.1.90.1.1.2,DISMAN-EXPRESSION-MIB::expResourceDeltaWildcardInstanceMaximum,Unsigned32,read-write,,current,,For every instance of a deltaValue object, one dynamic instance entry is needed for holding the instance value from the previous sample, i.e. to maintain state. This object limits maximum number of dynamic instance entries this system will support for wildcarded delta objects in expressions. For a given delta expression, the number of dynamic instances is the number of values that meet all criteria to exist times the number of delta values in the expression. A value of 0 indicates no preset limit, that is, the limit is dynamic based on system operation and resources. Unless explicitly resource limited, a system's value for this object should be 0. Changing this value will not eliminate or inhibit existing delta wildcard instance objects but will prevent the creation of more such objects. An attempt to allocate beyond the limit results in expErrorCode being tooManyWildcardValues for that evaluation attempt.
.1.3.6.1.2.1.90.1.1.3,DISMAN-EXPRESSION-MIB::expResourceDeltaWildcardInstances,Gauge32,read-only,,current,,The number of currently active instance entries as defined for expResourceDeltaWildcardInstanceMaximum.
.1.3.6.1.2.1.90.1.1.4,DISMAN-EXPRESSION-MIB::expResourceDeltaWildcardInstancesHigh,Gauge32,read-only,,current,,The highest value of expResourceDeltaWildcardInstances that has occurred since initialization of the managed system.
.1.3.6.1.2.1.90.1.1.5,DISMAN-EXPRESSION-MIB::expResourceDeltaWildcardInstanceResourceLacks,Counter32,read-only,,current,,The number of times this system could not evaluate an expression because that would have created a value instance in excess of expResourceDeltaWildcardInstanceMaximum.
.1.3.6.1.2.1.90.1.2,DISMAN-EXPRESSION-MIB::expDefine,,,,,,
.1.3.6.1.2.1.90.1.2.1,DISMAN-EXPRESSION-MIB::expExpressionTable,,not-accessible,,current,,A table of expression definitions.
.1.3.6.1.2.1.90.1.2.1.1,DISMAN-EXPRESSION-MIB::expExpressionEntry,,not-accessible,expExpressionOwner:expExpressionName,current,,Information about a single expression. New expressions can be created using expExpressionRowStatus. To create an expression first create the named entry in this table. Then use expExpressionName to populate expObjectTable. For expression evaluation to succeed all related entries in expExpressionTable and expObjectTable must be 'active'. If these conditions are not met the corresponding values in expValue simply are not instantiated. Deleting an entry deletes all related entries in expObjectTable and expErrorTable. Because of the relationships among the multiple tables for an expression (expExpressionTable, expObjectTable, and expValueTable) and the SNMP rules for independence in setting object values, it is necessary to do final error checking when an expression is evaluated, that is, when one of its instances in expValueTable is read or a delta interval expires. Earlier checking need not be done and an implementation may not impose any ordering on the creation of objects related to an expression. To maintain security of MIB information, when creating a new row in this table, the managed system must record the security credentials of the requester. These security credentials are the parameters necessary as inputs to isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. When obtaining the objects that make up the expression, the system must (conceptually) use isAccessAllowed to ensure that it does not violate security. The evaluation of the expression takes place under the security credentials of the creator of its expExpressionEntry. Values of read-write objects in this table may be changed at any time.
.1.3.6.1.2.1.90.1.2.1.1.1,DISMAN-EXPRESSION-MIB::expExpressionOwner,OCTET,not-accessible,,current,,The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
.1.3.6.1.2.1.90.1.2.1.1.2,DISMAN-EXPRESSION-MIB::expExpressionName,OCTET,not-accessible,,current,,The name of the expression. This is locally unique, within the scope of an expExpressionOwner.
.1.3.6.1.2.1.90.1.2.1.1.3,DISMAN-EXPRESSION-MIB::expExpression,OCTET,read-create,,current,,The expression to be evaluated. This object is the same as a DisplayString (RFC 1903) except for its maximum length. Except for the variable names the expression is in ANSI C syntax. Only the subset of ANSI C operators and functions listed here is allowed. Variables are expressed as a dollar sign ('$') and an integer that corresponds to an expObjectIndex. An example of a valid expression is: ($1-$5)*100 Expressions must not be recursive, that is although an expression may use the results of another expression, it must not contain any variable that is directly or indirectly a result of its own evaluation. The managed system must check for recursive expressions. The only allowed operators are: ( ) - (unary) + - * / % & | ^ << >> ~ ! && || == != > >= < <= Note the parentheses are included for parenthesizing the expression, not for casting data types. The only constant types defined are: int (32-bit signed) long (64-bit signed) unsigned int unsigned long hexadecimal character string oid The default type for a positive integer is int unless it is too large in which case it is long. All but oid are as defined for ANSI C. Note that a hexadecimal constant may end up as a scalar or an array of 8-bit integers. A string constant is enclosed in double quotes and may contain back-slashed individual characters as in ANSI C. An oid constant comprises 32-bit, unsigned integers and at least one period, for example: 0. .0 1.3.6.1 No additional leading or trailing subidentifiers are automatically added to an OID constant. The constant is taken as expressed. Integer-typed objects are treated as 32- or 64-bit, signed or unsigned integers, as appropriate. The results of mixing them are as for ANSI C, including the type of the result. Note that a 32-bit value is thus promoted to 64 bits only in an operation with a 64-bit value. There is no provision for larger values to handle overflow. Relative to SNMP data types, a resulting value becomes unsigned when calculating it uses any unsigned value, including a counter. To force the final value to be of data type counter the expression must explicitly use the counter32() or counter64() function (defined below). OCTET STRINGS and OBJECT IDENTIFIERs are treated as one-dimensioned arrays of unsigned 8-bit integers and unsigned 32-bit integers, respectively. IpAddresses are treated as 32-bit, unsigned integers in network byte order, that is, the hex version of 255.0.0.0 is 0xff000000. Conditional expressions result in a 32-bit, unsigned integer of value 0 for false or 1 for true. When an arbitrary value is used as a boolean 0 is false and non-zero is true. Rules for the resulting data type from an operation, based on the operator: For << and >> the result is the same as the left hand operand. For &&, ||, ==, !=, <, <=, >, and >= the result is always Unsigned32. For unary - the result is always Integer32. For +, -, *, /, %, &, |, and ^ the result is promoted according to the following rules, in order from most to least preferred: If left hand and right hand operands are the same type, use that. If either side is Counter64, use that. If either side is IpAddress, use that. If either side is TimeTicks, use that. If either side is Counter32, use that. Otherwise use Unsigned32. The following rules say what operators apply with what data types. Any combination not explicitly defined does not work. For all operators any of the following can be the left hand or right hand operand: Integer32, Counter32, Unsigned32, Counter64. The operator
.1.3.6.1.2.1.90.1.2.1.1.4,DISMAN-EXPRESSION-MIB::expExpressionValueType,INTEGER,read-create,,current,counter32(1):unsigned32(2):timeTicks(3):integer32(4):ipAddress(5):octetString(6):objectId(7):counter64(8),The type of the expression value. One and only one of the value objects in expValueTable will be instantiated to match this type. If the result of the expression can not be made into this type, an invalidOperandType error will occur.
.1.3.6.1.2.1.90.1.2.1.1.5,DISMAN-EXPRESSION-MIB::expExpressionComment,OCTET,read-create,,current,,A comment to explain the use or meaning of the expression.
.1.3.6.1.2.1.90.1.2.1.1.6,DISMAN-EXPRESSION-MIB::expExpressionDeltaInterval,Integer32,read-create,,current,,Sampling interval for objects in this expression with expObjectSampleType 'deltaValue'. This object has no effect if the the expression has no deltaValue objects. A value of 0 indicates no automated sampling. In this case the delta is the difference from the last time the expression was evaluated. Note that this is subject to unpredictable delta times in the face of retries or multiple managers. A value greater than zero is the number of seconds between automated samples. Until the delta interval has expired once the delta for the object is effectively not instantiated and evaluating the expression has results as if the object itself were not instantiated. Note that delta values potentially consume large amounts of system CPU and memory. Delta state and processing must continue constantly even if the expression is not being used. That is, the expression is being evaluated every delta interval, even if no application is reading those values. For wildcarded objects this can be substantial overhead. Note that delta intervals, external expression value sampling intervals and delta intervals for expressions within other expressions can have unusual interactions as they are impossible to synchronize accurately. In general one interval embedded below another must be enough shorter that the higher sample sees relatively smooth, predictable behavior. So, for example, to avoid the higher level getting the same sample twice, the lower level should sample at least twice as fast as the higher level does.
.1.3.6.1.2.1.90.1.2.1.1.7,DISMAN-EXPRESSION-MIB::expExpressionPrefix,OBJECT,read-only,,current,,An object prefix to assist an application in determining the instance indexing to use in expValueTable, relieving the application of the need to scan the expObjectTable to determine such a prefix. See expObjectTable for information on wildcarded objects. If the expValueInstance portion of the value OID may be treated as a scalar (that is, normally, 0) the value of expExpressionPrefix is zero length, that is, no OID at all. Note that zero length implies a null OID, not the OID 0.0. Otherwise, the value of expExpressionPrefix is the expObjectID value of any one of the wildcarded objects for the expression. This is sufficient, as the remainder, that is, the instance fragment relevant to instancing the values, must be the same for all wildcarded objects in the expression.
.1.3.6.1.2.1.90.1.2.1.1.8,DISMAN-EXPRESSION-MIB::expExpressionErrors,Counter32,read-only,,current,,The number of errors encountered while evaluating this expression. Note that an object in the expression not being accessible, is not considered an error. An example of an inaccessible object is when the object is excluded from the view of the user whose security credentials are used in the expression evaluation. In such cases, it is a legitimate condition that causes the corresponding expression value not to be instantiated.
.1.3.6.1.2.1.90.1.2.1.1.9,DISMAN-EXPRESSION-MIB::expExpressionEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The control that allows creation and deletion of entries.
.1.3.6.1.2.1.90.1.2.2,DISMAN-EXPRESSION-MIB::expErrorTable,,not-accessible,,current,,A table of expression errors.
.1.3.6.1.2.1.90.1.2.2.1,DISMAN-EXPRESSION-MIB::expErrorEntry,,not-accessible,expExpressionOwner:expExpressionName,current,,Information about errors in processing an expression. Entries appear in this table only when there is a matching expExpressionEntry and then only when there has been an error for that expression as reflected by the error codes defined for expErrorCode.
.1.3.6.1.2.1.90.1.2.2.1.1,DISMAN-EXPRESSION-MIB::expErrorTime,TimeTicks,read-only,,current,,The value of sysUpTime the last time an error caused a failure to evaluate this expression.
.1.3.6.1.2.1.90.1.2.2.1.2,DISMAN-EXPRESSION-MIB::expErrorIndex,Integer32,read-only,,current,,The one-dimensioned character array index into expExpression for where the error occurred. The value zero indicates irrelevance.
.1.3.6.1.2.1.90.1.2.2.1.3,DISMAN-EXPRESSION-MIB::expErrorCode,INTEGER,read-only,,current,invalidSyntax(1):undefinedObjectIndex(2):unrecognizedOperator(3):unrecognizedFunction(4):invalidOperandType(5):unmatchedParenthesis(6):tooManyWildcardValues(7):recursion(8):deltaTooShort(9):resourceUnavailable(10):divideByZero(11),The error that occurred. In the following explanations the expected timing of the error is in parentheses. 'S' means the error occurs on a Set request. 'E' means the error occurs on the attempt to evaluate the expression either due to Get from expValueTable or in ongoing delta processing. invalidSyntax the value sent for expExpression is not valid Expression MIB expression syntax (S) undefinedObjectIndex an object reference ($n) in expExpression does not have a matching instance in expObjectTable (E) unrecognizedOperator the value sent for expExpression held an unrecognized operator (S) unrecognizedFunction the value sent for expExpression held an unrecognized function name (S) invalidOperandType an operand in expExpression is not the right type for the associated operator or result (SE) unmatchedParenthesis the value sent for expExpression is not correctly parenthesized (S) tooManyWildcardValues evaluating the expression exceeded the limit set by expResourceDeltaWildcardInstanceMaximum (E) recursion through some chain of embedded expressions the expression invokes itself (E) deltaTooShort the delta for the next evaluation passed before the system could evaluate the present sample (E) resourceUnavailable some resource, typically dynamic memory, was unavailable (SE) divideByZero an attempt to divide by zero occurred (E) For the errors that occur when the attempt is made to set expExpression Set request fails with the SNMP error code 'wrongValue'. Such failures refer to the most recent failure to Set expExpression, not to the present value of expExpression which must be either unset or syntactically correct. Errors that occur during evaluation for a Get* operation return the SNMP error code 'genErr' except for 'tooManyWildcardValues' and 'resourceUnavailable' which return the SNMP error code 'resourceUnavailable'.
.1.3.6.1.2.1.90.1.2.2.1.4,DISMAN-EXPRESSION-MIB::expErrorInstance,OBJECT,read-only,,current,,The expValueInstance being evaluated when the error occurred. A zero-length indicates irrelevance.
.1.3.6.1.2.1.90.1.2.3,DISMAN-EXPRESSION-MIB::expObjectTable,,not-accessible,,current,,A table of object definitions for each expExpression. Wildcarding instance IDs: It is legal to omit all or part of the instance portion for some or all of the objects in an expression. (See theof expObjectID for details. However, note that if more than one object in the same expression is wildcarded in this way, they all must be objects where that portion of the instance is the same. In other words, all objects may be in the same SEQUENCE or in different SEQUENCEs but with the same semantic index value (e.g., a value of ifIndex) for the wildcarded portion.
.1.3.6.1.2.1.90.1.2.3.1,DISMAN-EXPRESSION-MIB::expObjectEntry,,not-accessible,expExpressionOwner:expExpressionName:expObjectIndex,current,,Information about an object. An application uses expObjectEntryStatus to create entries in this table while in the process of defining an expression. Values of read-create objects in this table may be changed at any time.
.1.3.6.1.2.1.90.1.2.3.1.1,DISMAN-EXPRESSION-MIB::expObjectIndex,Unsigned32,not-accessible,,current,,Within an expression, a unique, numeric identification for an object. Prefixed with a dollar sign ('$') this is used to reference the object in the corresponding expExpression.
.1.3.6.1.2.1.90.1.2.3.1.2,DISMAN-EXPRESSION-MIB::expObjectID,OBJECT,read-create,,current,,The OBJECT IDENTIFIER (OID) of this object. The OID may be fully qualified, meaning it includes a complete instance identifier part (e.g., ifInOctets.1 or sysUpTime.0), or it may not be fully qualified, meaning it may lack all or part of the instance identifier. If the expObjectID is not fully qualified, then expObjectWildcard must be set to true(1). The value of the expression will be multiple values, as if done for a GetNext sweep of the object. An object here may itself be the result of an expression but recursion is not allowed. NOTE: The simplest implementations of this MIB may not allow wildcards.
.1.3.6.1.2.1.90.1.2.3.1.3,DISMAN-EXPRESSION-MIB::expObjectIDWildcard,INTEGER,read-create,,current,true(1):false(2),A true value indicates the expObjecID of this row is a wildcard object. False indicates that expObjectID is fully instanced. If all expObjectWildcard values for a given expression are FALSE, expExpressionPrefix will reflect a scalar object (i.e. will be 0.0). NOTE: The simplest implementations of this MIB may not allow wildcards.
.1.3.6.1.2.1.90.1.2.3.1.4,DISMAN-EXPRESSION-MIB::expObjectSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2):changedValue(3),The method of sampling the selected variable. An 'absoluteValue' is simply the present value of the object. A 'deltaValue' is the present value minus the previous value, which was sampled expExpressionDeltaInterval seconds ago. This is intended primarily for use with SNMP counters, which are meaningless as an 'absoluteValue', but may be used with any integer-based value. A 'changedValue' is a boolean for whether the present value is different from the previous value. It is applicable to any data type and results in an Unsigned32 with value 1 if the object's value is changed and 0 if not. In all other respects it is as a 'deltaValue' and all statements and operation regarding delta values apply to changed values. When an expression contains both delta and absolute values the absolute values are obtained at the end of the delta period.
.1.3.6.1.2.1.90.1.2.3.1.5,DISMAN-EXPRESSION-MIB::expObjectDeltaDiscontinuityID,OBJECT,read-create,,current,,The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or DateAndTime object that indicates a discontinuity in the value at expObjectID. This object is instantiated only if expObjectSampleType is 'deltaValue' or 'changedValue'. The OID may be for a leaf object (e.g. sysUpTime.0) or may be wildcarded to match expObjectID. This object supports normal checking for a discontinuity in a counter. Note that if this object does not point to sysUpTime discontinuity checking must still check sysUpTime for an overall discontinuity. If the object identified is not accessible no discontinuity check will be made.
.1.3.6.1.2.1.90.1.2.3.1.6,DISMAN-EXPRESSION-MIB::expObjectDiscontinuityIDWildcard,INTEGER,read-create,,current,true(1):false(2),A true value indicates the expObjectDeltaDiscontinuityID of this row is a wildcard object. False indicates that expObjectDeltaDiscontinuityID is fully instanced. This object is instantiated only if expObjectSampleType is 'deltaValue' or 'changedValue'. NOTE: The simplest implementations of this MIB may not allow wildcards.
.1.3.6.1.2.1.90.1.2.3.1.7,DISMAN-EXPRESSION-MIB::expObjectDiscontinuityIDType,INTEGER,read-create,,current,timeTicks(1):timeStamp(2):dateAndTime(3),The value 'timeTicks' indicates the expObjectDeltaDiscontinuityID of this row is of syntax TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. The value 'dateAndTime indicates syntax DateAndTime. This object is instantiated only if expObjectSampleType is 'deltaValue' or 'changedValue'.
.1.3.6.1.2.1.90.1.2.3.1.8,DISMAN-EXPRESSION-MIB::expObjectConditional,OBJECT,read-create,,current,,The OBJECT IDENTIFIER (OID) of an object that overrides whether the instance of expObjectID is to be considered usable. If the value of the object at expObjectConditional is 0 or not instantiated, the object at expObjectID is treated as if it is not instantiated. In other words, expObjectConditional is a filter that controls whether or not to use the value at expObjectID. The OID may be for a leaf object (e.g. sysObjectID.0) or may be wildcarded to match expObjectID. If expObject is wildcarded and expObjectID in the same row is not, the wild portion of expObjectConditional must match the wildcarding of the rest of the expression. If no object in the expression is wildcarded but expObjectConditional is, use the lexically first instance (if any) of expObjectConditional. If the value of expObjectConditional is 0.0 operation is as if the value pointed to by expObjectConditional is a non-zero (true) value. Note that expObjectConditional can not trivially use an object of syntax TruthValue, since the underlying value is not 0 or 1.
.1.3.6.1.2.1.90.1.2.3.1.9,DISMAN-EXPRESSION-MIB::expObjectConditionalWildcard,INTEGER,read-create,,current,true(1):false(2),A true value indicates the expObjectConditional of this row is a wildcard object. False indicates that expObjectConditional is fully instanced. NOTE: The simplest implementations of this MIB may not allow wildcards.
.1.3.6.1.2.1.90.1.2.3.1.10,DISMAN-EXPRESSION-MIB::expObjectEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The control that allows creation/deletion of entries. Objects in this table may be changed while expObjectEntryStatus is in any state.
.1.3.6.1.2.1.90.1.3,DISMAN-EXPRESSION-MIB::expValue,,,,,,
.1.3.6.1.2.1.90.1.3.1,DISMAN-EXPRESSION-MIB::expValueTable,,not-accessible,,current,,A table of values from evaluated expressions.
.1.3.6.1.2.1.90.1.3.1.1,DISMAN-EXPRESSION-MIB::expValueEntry,,not-accessible,expExpressionOwner:expExpressionName:IMPLIEDexpValueInstance,current,,A single value from an evaluated expression. For a given instance, only one 'Val' object in the conceptual row will be instantiated, that is, the one with the appropriate type for the value. For values that contain no objects of expObjectSampleType 'deltaValue' or 'changedValue', reading a value from the table causes the evaluation of the expression for that value. For those that contain a 'deltaValue' or 'changedValue' the value read is as of the last sampling interval. If in the attempt to evaluate the expression one or more of the necessary objects is not available, the corresponding entry in this table is effectively not instantiated. To maintain security of MIB information, when creating a new row in this table, the managed system must record the security credentials of the requester. These security credentials are the parameters necessary as inputs to isAccessAllowed from [RFC2571]. When obtaining the objects that make up the expression, the system must (conceptually) use isAccessAllowed to ensure that it does not violate security. The evaluation of that expression takes place under the security credentials of the creator of its expExpressionEntry. To maintain security of MIB information, expression evaluation must take place using security credentials for the implied Gets of the objects in the expression as inputs (conceptually) to isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. These are the security credentials of the creator of the corresponding expExpressionEntry.
.1.3.6.1.2.1.90.1.3.1.1.1,DISMAN-EXPRESSION-MIB::expValueInstance,OBJECT,not-accessible,,current,,The final instance portion of a value's OID according to the wildcarding in instances of expObjectID for the expression. The prefix of this OID fragment is 0.0, leading to the following behavior. If there is no wildcarding, the value is 0.0.0. In other words, there is one value which standing alone would have been a scalar with a 0 at the end of its OID. If there is wildcarding, the value is 0.0 followed by a value that the wildcard can take, thus defining one value instance for each real, possible value of the wildcard. So, for example, if the wildcard worked out to be an ifIndex, there is an expValueInstance for each applicable ifIndex.
.1.3.6.1.2.1.90.1.3.1.1.2,DISMAN-EXPRESSION-MIB::expValueCounter32Val,Counter32,read-only,,current,,The value when expExpressionValueType is 'counter32'.
.1.3.6.1.2.1.90.1.3.1.1.3,DISMAN-EXPRESSION-MIB::expValueUnsigned32Val,Unsigned32,read-only,,current,,The value when expExpressionValueType is 'unsigned32'.
.1.3.6.1.2.1.90.1.3.1.1.4,DISMAN-EXPRESSION-MIB::expValueTimeTicksVal,TimeTicks,read-only,,current,,The value when expExpressionValueType is 'timeTicks'.
.1.3.6.1.2.1.90.1.3.1.1.5,DISMAN-EXPRESSION-MIB::expValueInteger32Val,Integer32,read-only,,current,,The value when expExpressionValueType is 'integer32'.
.1.3.6.1.2.1.90.1.3.1.1.6,DISMAN-EXPRESSION-MIB::expValueIpAddressVal,IpAddress,read-only,,current,,The value when expExpressionValueType is 'ipAddress'.
.1.3.6.1.2.1.90.1.3.1.1.7,DISMAN-EXPRESSION-MIB::expValueOctetStringVal,OCTET,read-only,,current,,The value when expExpressionValueType is 'octetString'.
.1.3.6.1.2.1.90.1.3.1.1.8,DISMAN-EXPRESSION-MIB::expValueOidVal,OBJECT,read-only,,current,,The value when expExpressionValueType is 'objectId'.
.1.3.6.1.2.1.90.1.3.1.1.9,DISMAN-EXPRESSION-MIB::expValueCounter64Val,Counter64,read-only,,current,,The value when expExpressionValueType is 'counter64'.
.1.3.6.1.2.1.90.3,DISMAN-EXPRESSION-MIB::dismanExpressionMIBConformance,,,,,,
.1.3.6.1.2.1.90.3.1,DISMAN-EXPRESSION-MIB::dismanExpressionMIBCompliances,,,,,,
.1.3.6.1.2.1.90.3.1.1,DISMAN-EXPRESSION-MIB::dismanExpressionMIBCompliance,,,,,,The compliance statement for entities which implement the Expression MIB.
.1.3.6.1.2.1.90.3.2,DISMAN-EXPRESSION-MIB::dismanExpressionMIBGroups,,,,,,
.1.3.6.1.2.1.90.3.2.1,DISMAN-EXPRESSION-MIB::dismanExpressionResourceGroup,,,,,,Expression definition resource management.
.1.3.6.1.2.1.90.3.2.2,DISMAN-EXPRESSION-MIB::dismanExpressionDefinitionGroup,,,,,,Expression definition.
.1.3.6.1.2.1.90.3.2.3,DISMAN-EXPRESSION-MIB::dismanExpressionValueGroup,,,,,,Expression value.
.1.3.6.1.2.1.91,IPV6-MLD-MIB::mldMIB,,,,,,The MIB module for MLD Management.
.1.3.6.1.2.1.91.1,IPV6-MLD-MIB::mldMIBObjects,,,,,,
.1.3.6.1.2.1.91.1.1,IPV6-MLD-MIB::mldInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the interfaces on which MLD is enabled.
.1.3.6.1.2.1.91.1.1.1,IPV6-MLD-MIB::mldInterfaceEntry,,not-accessible,mldInterfaceIfIndex,current,,An entry (conceptual row) representing an interface on which MLD is enabled.
.1.3.6.1.2.1.91.1.1.1.1,IPV6-MLD-MIB::mldInterfaceIfIndex,Integer32,not-accessible,,current,,The internetwork-layer interface value of the interface for which MLD is enabled.
.1.3.6.1.2.1.91.1.1.1.2,IPV6-MLD-MIB::mldInterfaceQueryInterval,Unsigned32,read-create,,current,,The frequency at which MLD Host-Query packets are transmitted on this interface.
.1.3.6.1.2.1.91.1.1.1.3,IPV6-MLD-MIB::mldInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The activation of a row enables MLD on the interface. The destruction of a row disables MLD on the interface.
.1.3.6.1.2.1.91.1.1.1.4,IPV6-MLD-MIB::mldInterfaceVersion,Unsigned32,read-create,,current,,The version of MLD which is running on this interface. This object is a place holder to allow for new versions of MLD to be introduced. Version 1 of MLD is defined in RFC 2710.
.1.3.6.1.2.1.91.1.1.1.5,IPV6-MLD-MIB::mldInterfaceQuerier,OCTET,read-only,,current,,The address of the MLD Querier on the IPv6 subnet to which this interface is attached.
.1.3.6.1.2.1.91.1.1.1.6,IPV6-MLD-MIB::mldInterfaceQueryMaxResponseDelay,Unsigned32,read-create,,current,,The maximum query response time advertised in MLD queries on this interface.
.1.3.6.1.2.1.91.1.1.1.7,IPV6-MLD-MIB::mldInterfaceJoins,Counter32,read-only,,current,,The number of times a group membership has been added on this interface; that is, the number of times an entry for this interface has been added to the Cache Table. This object gives an indication of the amount of MLD activity over time.
.1.3.6.1.2.1.91.1.1.1.8,IPV6-MLD-MIB::mldInterfaceGroups,Gauge32,read-only,,current,,The current number of entries for this interface in the Cache Table.
.1.3.6.1.2.1.91.1.1.1.9,IPV6-MLD-MIB::mldInterfaceRobustness,Unsigned32,read-create,,current,,The Robustness Variable allows tuning for the expected packet loss on a subnet. If a subnet is expected to be lossy, the Robustness Variable may be increased. MLD is robust to (Robustness Variable-1) packet losses. The discussion of the Robustness Variable is in Section 7.1 of RFC 2710.
.1.3.6.1.2.1.91.1.1.1.10,IPV6-MLD-MIB::mldInterfaceLastListenQueryIntvl,Unsigned32,read-create,,current,,The Last Member Query Interval is the Max Response Delay inserted into Group-Specific Queries sent in response to Leave Group messages, and is also the amount of time between Group-Specific Query messages. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group.
.1.3.6.1.2.1.91.1.1.1.11,IPV6-MLD-MIB::mldInterfaceProxyIfIndex,Integer32,read-create,,current,,Some devices implement a form of MLD proxying whereby memberships learned on the interface represented by this row, cause MLD Multicast Listener Reports to be sent on the internetwork-layer interface identified by this object. Such a device would implement mldRouterMIBGroup only on its router interfaces (those interfaces with non-zero mldInterfaceProxyIfIndex). Typically, the value of this object is 0, indicating that no proxying is being done.
.1.3.6.1.2.1.91.1.1.1.12,IPV6-MLD-MIB::mldInterfaceQuerierUpTime,TimeTicks,read-only,,current,,The time since mldInterfaceQuerier was last changed.
.1.3.6.1.2.1.91.1.1.1.13,IPV6-MLD-MIB::mldInterfaceQuerierExpiryTime,TimeTicks,read-only,,current,,The time remaining before the Other Querier Present Timer expires. If the local system is the querier, the value of this object is zero.
.1.3.6.1.2.1.91.1.2,IPV6-MLD-MIB::mldCacheTable,,not-accessible,,current,,The (conceptual) table listing the IPv6 multicast groups for which there are members on a particular interface.
.1.3.6.1.2.1.91.1.2.1,IPV6-MLD-MIB::mldCacheEntry,,not-accessible,mldCacheAddress:mldCacheIfIndex,current,,An entry (conceptual row) in the mldCacheTable.
.1.3.6.1.2.1.91.1.2.1.1,IPV6-MLD-MIB::mldCacheAddress,OCTET,not-accessible,,current,,The IPv6 multicast group address for which this entry contains information.
.1.3.6.1.2.1.91.1.2.1.2,IPV6-MLD-MIB::mldCacheIfIndex,Integer32,not-accessible,,current,,The internetwork-layer interface for which this entry contains information for an IPv6 multicast group address.
.1.3.6.1.2.1.91.1.2.1.3,IPV6-MLD-MIB::mldCacheSelf,INTEGER,read-create,,current,true(1):false(2),An indication of whether the local system is a member of this group address on this interface.
.1.3.6.1.2.1.91.1.2.1.4,IPV6-MLD-MIB::mldCacheLastReporter,OCTET,read-only,,current,,The IPv6 address of the source of the last membership report received for this IPv6 Multicast group address on this interface. If no membership report has been received, this object has the value 0::0.
.1.3.6.1.2.1.91.1.2.1.5,IPV6-MLD-MIB::mldCacheUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.2.1.91.1.2.1.6,IPV6-MLD-MIB::mldCacheExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. A value of 0 indicates that the entry is only present because mldCacheSelf is true and that if the router left the group, this entry would be aged out immediately. Note that some implementations may process Membership Reports from the local system in the same way as reports from other hosts, so a value of 0 is not required.
.1.3.6.1.2.1.91.1.2.1.7,IPV6-MLD-MIB::mldCacheStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or existing entries deleted from this table.
.1.3.6.1.2.1.91.2,IPV6-MLD-MIB::mldMIBConformance,,,,,,
.1.3.6.1.2.1.91.2.1,IPV6-MLD-MIB::mldMIBCompliances,,,,,,
.1.3.6.1.2.1.91.2.1.1,IPV6-MLD-MIB::mldHostMIBCompliance,,,,,,The compliance statement for hosts running MLD and implementing the MLD MIB.
.1.3.6.1.2.1.91.2.1.2,IPV6-MLD-MIB::mldRouterMIBCompliance,,,,,,The compliance statement for routers running MLD and implementing the MLD MIB.
.1.3.6.1.2.1.91.2.2,IPV6-MLD-MIB::mldMIBGroups,,,,,,
.1.3.6.1.2.1.91.2.2.1,IPV6-MLD-MIB::mldBaseMIBGroup,,,,,,The basic collection of objects providing management of MLD. The mldBaseMIBGroup is designed to allow for the manager creation and deletion of MLD cache entries.
.1.3.6.1.2.1.91.2.2.2,IPV6-MLD-MIB::mldRouterMIBGroup,,,,,,A collection of additional objects for management of MLD in routers.
.1.3.6.1.2.1.91.2.2.3,IPV6-MLD-MIB::mldHostMIBGroup,,,,,,A collection of additional objects for management of MLD in hosts.
.1.3.6.1.2.1.91.2.2.4,IPV6-MLD-MIB::mldProxyMIBGroup,,,,,,A collection of additional objects for management of MLD proxy devices.
.1.3.6.1.2.1.92,NOTIFICATION-LOG-MIB::notificationLogMIB,,,,,,The MIB module for logging SNMP Notifications, that is, Traps and Informs.
.1.3.6.1.2.1.92.1,NOTIFICATION-LOG-MIB::notificationLogMIBObjects,,,,,,
.1.3.6.1.2.1.92.1.1,NOTIFICATION-LOG-MIB::nlmConfig,,,,,,
.1.3.6.1.2.1.92.1.1.1,NOTIFICATION-LOG-MIB::nlmConfigGlobalEntryLimit,Unsigned32,read-write,,current,,The maximum number of notification entries that may be held in nlmLogTable for all nlmLogNames added together. A particular setting does not guarantee that much data can be held. If an application changes the limit while there are Notifications in the log, the oldest Notifications MUST be discarded to bring the log down to the new limit - thus the value of nlmConfigGlobalEntryLimit MUST take precedence over the values of nlmConfigGlobalAgeOut and nlmConfigLogEntryLimit, even if the Notification being discarded has been present for fewer minutes than the value of nlmConfigGlobalAgeOut, or if the named log has fewer entries than that specified in nlmConfigLogEntryLimit. A value of 0 means no limit. Please be aware that contention between multiple managers trying to set this object to different values MAY affect the reliability and completeness of data seen by each manager.
.1.3.6.1.2.1.92.1.1.2,NOTIFICATION-LOG-MIB::nlmConfigGlobalAgeOut,Unsigned32,read-write,,current,,The number of minutes a Notification SHOULD be kept in a log before it is automatically removed. If an application changes the value of nlmConfigGlobalAgeOut, Notifications older than the new time MAY be discarded to meet the new time. A value of 0 means no age out. Please be aware that contention between multiple managers trying to set this object to different values MAY affect the reliability and completeness of data seen by each manager.
.1.3.6.1.2.1.92.1.1.3,NOTIFICATION-LOG-MIB::nlmConfigLogTable,,not-accessible,,current,,A table of logging control entries.
.1.3.6.1.2.1.92.1.1.3.1,NOTIFICATION-LOG-MIB::nlmConfigLogEntry,,not-accessible,nlmLogName,current,,A logging control entry. Depending on the entry's storage type entries may be supplied by the system or created and deleted by applications using nlmConfigLogEntryStatus.
.1.3.6.1.2.1.92.1.1.3.1.1,NOTIFICATION-LOG-MIB::nlmLogName,OCTET,not-accessible,,current,,The name of the log. An implementation may allow multiple named logs, up to some implementation-specific limit (which may be none). A zero-length log name is reserved for creation and deletion by the managed system, and MUST be used as the default log name by systems that do not support named logs.
.1.3.6.1.2.1.92.1.1.3.1.2,NOTIFICATION-LOG-MIB::nlmConfigLogFilterName,OCTET,read-create,,current,,A value of snmpNotifyFilterProfileName as used as an index into the snmpNotifyFilterTable in the SNMP Notification MIB, specifying the locally or remotely originated Notifications to be filtered out and not logged in this log. A zero-length value or a name that does not identify an existing entry in snmpNotifyFilterTable indicate no Notifications are to be logged in this log.
.1.3.6.1.2.1.92.1.1.3.1.3,NOTIFICATION-LOG-MIB::nlmConfigLogEntryLimit,Unsigned32,read-create,,current,,The maximum number of notification entries that can be held in nlmLogTable for this named log. A particular setting does not guarantee that that much data can be held. If an application changes the limit while there are Notifications in the log, the oldest Notifications are discarded to bring the log down to the new limit. A value of 0 indicates no limit. Please be aware that contention between multiple managers trying to set this object to different values MAY affect the reliability and completeness of data seen by each manager.
.1.3.6.1.2.1.92.1.1.3.1.4,NOTIFICATION-LOG-MIB::nlmConfigLogAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),Control to enable or disable the log without otherwise disturbing the log's entry. Please be aware that contention between multiple managers trying to set this object to different values MAY affect the reliability and completeness of data seen by each manager.
.1.3.6.1.2.1.92.1.1.3.1.5,NOTIFICATION-LOG-MIB::nlmConfigLogOperStatus,INTEGER,read-only,,current,disabled(1):operational(2):noFilter(3),The operational status of this log: disabled administratively disabled operational administratively enabled and working noFilter administratively enabled but either nlmConfigLogFilterName is zero length or does not name an existing entry in snmpNotifyFilterTable
.1.3.6.1.2.1.92.1.1.3.1.6,NOTIFICATION-LOG-MIB::nlmConfigLogStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this conceptual row.
.1.3.6.1.2.1.92.1.1.3.1.7,NOTIFICATION-LOG-MIB::nlmConfigLogEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Control for creating and deleting entries. Entries may be modified while active. For non-null-named logs, the managed system records the security credentials from the request that sets nlmConfigLogStatus to 'active' and uses that identity to apply access control to the objects in the Notification to decide if that Notification may be logged.
.1.3.6.1.2.1.92.1.2,NOTIFICATION-LOG-MIB::nlmStats,,,,,,
.1.3.6.1.2.1.92.1.2.1,NOTIFICATION-LOG-MIB::nlmStatsGlobalNotificationsLogged,Counter32,read-only,,current,,The number of Notifications put into the nlmLogTable. This counts a Notification once for each log entry, so a Notification put into multiple logs is counted multiple times.
.1.3.6.1.2.1.92.1.2.2,NOTIFICATION-LOG-MIB::nlmStatsGlobalNotificationsBumped,Counter32,read-only,,current,,The number of log entries discarded to make room for a new entry due to lack of resources or the value of nlmConfigGlobalEntryLimit or nlmConfigLogEntryLimit. This does not include entries discarded due to the value of nlmConfigGlobalAgeOut.
.1.3.6.1.2.1.92.1.2.3,NOTIFICATION-LOG-MIB::nlmStatsLogTable,,not-accessible,,current,,A table of Notification log statistics entries.
.1.3.6.1.2.1.92.1.2.3.1,NOTIFICATION-LOG-MIB::nlmStatsLogEntry,,not-accessible,,current,,A Notification log statistics entry.
.1.3.6.1.2.1.92.1.2.3.1.1,NOTIFICATION-LOG-MIB::nlmStatsLogNotificationsLogged,Counter32,read-only,,current,,The number of Notifications put in this named log.
.1.3.6.1.2.1.92.1.2.3.1.2,NOTIFICATION-LOG-MIB::nlmStatsLogNotificationsBumped,Counter32,read-only,,current,,The number of log entries discarded from this named log to make room for a new entry due to lack of resources or the value of nlmConfigGlobalEntryLimit or nlmConfigLogEntryLimit. This does not include entries discarded due to the value of nlmConfigGlobalAgeOut.
.1.3.6.1.2.1.92.1.3,NOTIFICATION-LOG-MIB::nlmLog,,,,,,
.1.3.6.1.2.1.92.1.3.1,NOTIFICATION-LOG-MIB::nlmLogTable,,not-accessible,,current,,A table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0.
.1.3.6.1.2.1.92.1.3.1.1,NOTIFICATION-LOG-MIB::nlmLogEntry,,not-accessible,nlmLogName:nlmLogIndex,current,,A Notification log entry. Entries appear in this table when Notifications occur and pass filtering by nlmConfigLogFilterName and access control. They are removed to make way for new entries due to lack of resources or the values of nlmConfigGlobalEntryLimit, nlmConfigGlobalAgeOut, or nlmConfigLogEntryLimit. If adding an entry would exceed nlmConfigGlobalEntryLimit or system resources in general, the oldest entry in any log SHOULD be removed to make room for the new one. If adding an entry would exceed nlmConfigLogEntryLimit the oldest entry in that log SHOULD be removed to make room for the new one. Before the managed system puts a locally-generated Notification into a non-null-named log it assures that the creator of the log has access to the information in the Notification. If not it does not log that Notification in that log.
.1.3.6.1.2.1.92.1.3.1.1.1,NOTIFICATION-LOG-MIB::nlmLogIndex,Unsigned32,not-accessible,,current,,A monotonically increasing integer for the sole purpose of indexing entries within the named log. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1.
.1.3.6.1.2.1.92.1.3.1.1.2,NOTIFICATION-LOG-MIB::nlmLogTime,TimeTicks,read-only,,current,,The value of sysUpTime when the entry was placed in the log. If the entry occurred before the most recent management system initialization this object value MUST be set to zero.
.1.3.6.1.2.1.92.1.3.1.1.3,NOTIFICATION-LOG-MIB::nlmLogDateAndTime,OCTET,read-only,,current,,The local date and time when the entry was logged, instantiated only by systems that have date and time capability.
.1.3.6.1.2.1.92.1.3.1.1.4,NOTIFICATION-LOG-MIB::nlmLogEngineID,OCTET,read-only,,current,,The identification of the SNMP engine at which the Notification originated. If the log can contain Notifications from only one engine or the Trap is in SNMPv1 format, this object is a zero-length string.
.1.3.6.1.2.1.92.1.3.1.1.5,NOTIFICATION-LOG-MIB::nlmLogEngineTAddress,OCTET,read-only,,current,,The transport service address of the SNMP engine from which the Notification was received, formatted according to the corresponding value of nlmLogEngineTDomain. This is used to identify the source of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted from the SNMPv1 trap pdu. This object MUST always be instantiated, even if the log can contain Notifications from only one engine. Please be aware that the nlmLogEngineTAddress may not uniquely identify the SNMP engine from which the Notification was received. For example, if an SNMP engine uses DHCP or NAT to obtain ip addresses, the address it uses may be shared with other network devices, and hence will not uniquely identify the SNMP engine.
.1.3.6.1.2.1.92.1.3.1.1.6,NOTIFICATION-LOG-MIB::nlmLogEngineTDomain,OBJECT,read-only,,current,,Indicates the kind of transport service by which a Notification was received from an SNMP engine. nlmLogEngineTAddress contains the transport service address of the SNMP engine from which this Notification was received. Possible values for this object are presently found in the Transport Mappings for SNMPv2 document (RFC 1906 [8]).
.1.3.6.1.2.1.92.1.3.1.1.7,NOTIFICATION-LOG-MIB::nlmLogContextEngineID,OCTET,read-only,,current,,If the Notification was received in a protocol which has a contextEngineID element like SNMPv3, this object has that value. Otherwise its value is a zero-length string.
.1.3.6.1.2.1.92.1.3.1.1.8,NOTIFICATION-LOG-MIB::nlmLogContextName,OCTET,read-only,,current,,The name of the SNMP MIB context from which the Notification came. For SNMPv1 Traps this is the community string from the Trap.
.1.3.6.1.2.1.92.1.3.1.1.9,NOTIFICATION-LOG-MIB::nlmLogNotificationID,OBJECT,read-only,,current,,The NOTIFICATION-TYPE object identifier of the Notification that occurred.
.1.3.6.1.2.1.92.1.3.2,NOTIFICATION-LOG-MIB::nlmLogVariableTable,,not-accessible,,current,,A table of variables to go with Notification log entries.
.1.3.6.1.2.1.92.1.3.2.1,NOTIFICATION-LOG-MIB::nlmLogVariableEntry,,not-accessible,nlmLogName:nlmLogIndex:nlmLogVariableIndex,current,,A Notification log entry variable. Entries appear in this table when there are variables in the varbind list of a Notification in nlmLogTable.
.1.3.6.1.2.1.92.1.3.2.1.1,NOTIFICATION-LOG-MIB::nlmLogVariableIndex,Unsigned32,not-accessible,,current,,A monotonically increasing integer, starting at 1 for a given nlmLogIndex, for indexing variables within the logged Notification.
.1.3.6.1.2.1.92.1.3.2.1.2,NOTIFICATION-LOG-MIB::nlmLogVariableID,OBJECT,read-only,,current,,The variable's object identifier.
.1.3.6.1.2.1.92.1.3.2.1.3,NOTIFICATION-LOG-MIB::nlmLogVariableValueType,INTEGER,read-only,,current,counter32(1):unsigned32(2):timeTicks(3):integer32(4):ipAddress(5):octetString(6):objectId(7):counter64(8):opaque(9),The type of the value. One and only one of the value objects that follow must be instantiated, based on this type.
.1.3.6.1.2.1.92.1.3.2.1.4,NOTIFICATION-LOG-MIB::nlmLogVariableCounter32Val,Counter32,read-only,,current,,The value when nlmLogVariableType is 'counter32'.
.1.3.6.1.2.1.92.1.3.2.1.5,NOTIFICATION-LOG-MIB::nlmLogVariableUnsigned32Val,Unsigned32,read-only,,current,,The value when nlmLogVariableType is 'unsigned32'.
.1.3.6.1.2.1.92.1.3.2.1.6,NOTIFICATION-LOG-MIB::nlmLogVariableTimeTicksVal,TimeTicks,read-only,,current,,The value when nlmLogVariableType is 'timeTicks'.
.1.3.6.1.2.1.92.1.3.2.1.7,NOTIFICATION-LOG-MIB::nlmLogVariableInteger32Val,Integer32,read-only,,current,,The value when nlmLogVariableType is 'integer32'.
.1.3.6.1.2.1.92.1.3.2.1.8,NOTIFICATION-LOG-MIB::nlmLogVariableOctetStringVal,OCTET,read-only,,current,,The value when nlmLogVariableType is 'octetString'.
.1.3.6.1.2.1.92.1.3.2.1.9,NOTIFICATION-LOG-MIB::nlmLogVariableIpAddressVal,IpAddress,read-only,,current,,The value when nlmLogVariableType is 'ipAddress'. Although this seems to be unfriendly for IPv6, we have to recognize that there are a number of older MIBs that do contain an IPv4 format address, known as IpAddress. IPv6 addresses are represented using TAddress or InetAddress, and so the underlying datatype is OCTET STRING, and their value would be stored in the nlmLogVariableOctetStringVal column.
.1.3.6.1.2.1.92.1.3.2.1.10,NOTIFICATION-LOG-MIB::nlmLogVariableOidVal,OBJECT,read-only,,current,,The value when nlmLogVariableType is 'objectId'.
.1.3.6.1.2.1.92.1.3.2.1.11,NOTIFICATION-LOG-MIB::nlmLogVariableCounter64Val,Counter64,read-only,,current,,The value when nlmLogVariableType is 'counter64'.
.1.3.6.1.2.1.92.1.3.2.1.12,NOTIFICATION-LOG-MIB::nlmLogVariableOpaqueVal,Opaque,read-only,,current,,The value when nlmLogVariableType is 'opaque'.
.1.3.6.1.2.1.92.3,NOTIFICATION-LOG-MIB::notificationLogMIBConformance,,,,,,
.1.3.6.1.2.1.92.3.1,NOTIFICATION-LOG-MIB::notificationLogMIBCompliances,,,,,,
.1.3.6.1.2.1.92.3.1.1,NOTIFICATION-LOG-MIB::notificationLogMIBCompliance,,,,,,The compliance statement for entities which implement the Notification Log MIB.
.1.3.6.1.2.1.92.3.2,NOTIFICATION-LOG-MIB::notificationLogMIBGroups,,,,,,
.1.3.6.1.2.1.92.3.2.1,NOTIFICATION-LOG-MIB::notificationLogConfigGroup,,,,,,Notification log configuration management.
.1.3.6.1.2.1.92.3.2.2,NOTIFICATION-LOG-MIB::notificationLogStatsGroup,,,,,,Notification log statistics.
.1.3.6.1.2.1.92.3.2.3,NOTIFICATION-LOG-MIB::notificationLogLogGroup,,,,,,Notification log data.
.1.3.6.1.2.1.92.3.2.4,NOTIFICATION-LOG-MIB::notificationLogDateGroup,,,,,,Conditionally mandatory notification log data. This group is mandatory on systems that keep wall clock date and time and should not be implemented on systems that do not have a wall clock date.
.1.3.6.1.2.1.93,PINT-MIB::pintMib,,,,,,This MIB defines the objects necessary to monitor PINT Services
.1.3.6.1.2.1.93.1,PINT-MIB::pintServerConfig,,,,,,
.1.3.6.1.2.1.93.1.1,PINT-MIB::pintReleaseNumber,OCTET,read-only,,current,,An indication of version of the PINT protocol supported by this agent.
.1.3.6.1.2.1.93.1.2,PINT-MIB::pintSysContact,OCTET,read-write,,current,,Contact information related to the administration of the PINT services.
.1.3.6.1.2.1.93.1.3,PINT-MIB::pintApplInstallPkgTable,,not-accessible,,current,,Table describing the PINT applications that are installed.
.1.3.6.1.2.1.93.1.3.1,PINT-MIB::pintApplInstallPkgEntry,,not-accessible,,current,,Entries per PINT Application.
.1.3.6.1.2.1.93.1.3.1.1,PINT-MIB::pintApplInstallPkgDescription,OCTET,read-only,,current,,Textual description of the installed PINT application.
.1.3.6.1.2.1.93.1.4,PINT-MIB::pintRegisteredGatewayTable,,not-accessible,,current,,Table describing the registered gateway applications.
.1.3.6.1.2.1.93.1.4.1,PINT-MIB::pintRegisteredGatewayEntry,,not-accessible,,current,,Entries per Registered Gateway Application.
.1.3.6.1.2.1.93.1.4.1.1,PINT-MIB::pintRegisteredGatewayName,OCTET,read-only,,current,,Name of the registered gateway.
.1.3.6.1.2.1.93.1.4.1.2,PINT-MIB::pintRegisteredGatewayDescription,OCTET,read-only,,current,,Textual description of the registered gateway.
.1.3.6.1.2.1.93.2,PINT-MIB::pintServerMonitor,,,,,,
.1.3.6.1.2.1.93.2.1,PINT-MIB::pintServerGlobalPerf,,,,,,
.1.3.6.1.2.1.93.2.1.1,PINT-MIB::pintServerGlobalStatsTable,,not-accessible,,current,,Table displaying the monitored global server statistics.
.1.3.6.1.2.1.93.2.1.1.1,PINT-MIB::pintServerGlobalStatsEntry,,not-accessible,pintServerServiceTypeIndex:pintServerPerfStatPeriodIndex,current,,Entries in the global statistics table. One entry is defined for each monitored service type and performance statistics collection period.
.1.3.6.1.2.1.93.2.1.1.1.1,PINT-MIB::pintServerServiceTypeIndex,INTEGER,not-accessible,,current,r2C(1):r2F(2):r2FB(3):r2HC(4),The unique identifier of the monitored service.
.1.3.6.1.2.1.93.2.1.1.1.2,PINT-MIB::pintServerPerfStatPeriodIndex,INTEGER,not-accessible,,current,last30sec(1):last15min(2):last24Hr(3):sinceReboot(4),Time period for which the performance statistics are requested from the pint server.
.1.3.6.1.2.1.93.2.1.1.1.3,PINT-MIB::pintServerGlobalCallsReceived,Counter32,read-only,,current,,Number of received global calls.
.1.3.6.1.2.1.93.2.1.1.1.4,PINT-MIB::pintServerGlobalSuccessfulCalls,Counter32,read-only,,current,,Number of global successful calls.
.1.3.6.1.2.1.93.2.1.1.1.5,PINT-MIB::pintServerGlobalDisconnectedCalls,Counter32,read-only,,current,,Number of global disconnected (failed) calls.
.1.3.6.1.2.1.93.2.1.1.1.6,PINT-MIB::pintServerGlobalDisCUAutFCalls,Counter32,read-only,,current,,Number of global calls that were disconnected because of client or user authorization failure.
.1.3.6.1.2.1.93.2.1.1.1.7,PINT-MIB::pintServerGlobalDisServProbCalls,Counter32,read-only,,current,,Number of global calls that were disconnected because of server problems.
.1.3.6.1.2.1.93.2.1.1.1.8,PINT-MIB::pintServerGlobalDisGatProbCalls,Counter32,read-only,,current,,Number of global calls that were disconnected because of gateway problems.
.1.3.6.1.2.1.93.2.2,PINT-MIB::pintServerClientPerf,,,,,,
.1.3.6.1.2.1.93.2.2.1,PINT-MIB::pintServerClientStatsTable,,not-accessible,,current,,Table displaying the monitored server client statistics.
.1.3.6.1.2.1.93.2.2.1.1,PINT-MIB::pintServerClientStatsEntry,,not-accessible,pintServerClientAddress:pintServerServiceTypeIndex:pintServerPerfStatPeriodIndex,current,,Entries in the client server statistics table. One entry is defined for each client identified by name, monitored service type and performance statistics collection period.
.1.3.6.1.2.1.93.2.2.1.1.1,PINT-MIB::pintServerClientAddress,OCTET,not-accessible,,current,,The unique identifier of the monitored client identified by its address represented as as a string.
.1.3.6.1.2.1.93.2.2.1.1.2,PINT-MIB::pintServerClientCallsReceived,Counter32,read-only,,current,,Number of calls received from the specific client.
.1.3.6.1.2.1.93.2.2.1.1.3,PINT-MIB::pintServerClientSuccessfulCalls,Counter32,read-only,,current,,Number of calls from the client successfully completed.
.1.3.6.1.2.1.93.2.2.1.1.4,PINT-MIB::pintServerClientDisconnectedCalls,Counter32,read-only,,current,,Number of calls received from the client, and that were disconnected (failed).
.1.3.6.1.2.1.93.2.2.1.1.5,PINT-MIB::pintServerClientDisCAutFCalls,Counter32,read-only,,current,,Number of calls from the client that were disconnected because of client authorization failure.
.1.3.6.1.2.1.93.2.2.1.1.6,PINT-MIB::pintServerClientDisEFProbCalls,Counter32,read-only,,current,,Number of calls from the client that were disconnected because of egress facility problems.
.1.3.6.1.2.1.93.2.3,PINT-MIB::pintServerUserIdPerf,,,,,,
.1.3.6.1.2.1.93.2.3.1,PINT-MIB::pintServerUserIdStatsTable,,not-accessible,,current,,Table displaying the monitored Pint service user statistics.
.1.3.6.1.2.1.93.2.3.1.1,PINT-MIB::pintServerUserIdStatsEntry,,not-accessible,pintServerUserIdName:pintServerServiceTypeIndex:pintServerPerfStatPeriodIndex,current,,Entries in the user statistics table. One entry is defined for each user identified by name, each monitored service type and performance statistics collection period. It is assumed that the capabilities of the pint server are enough to accommodate the number of entries in this table. It is a local server implementation issue if an aging mechanism Is implemented in order to avoid scalability problems.
.1.3.6.1.2.1.93.2.3.1.1.1,PINT-MIB::pintServerUserIdName,OCTET,not-accessible,,current,,The unique identifier of the monitored user identified by its name.
.1.3.6.1.2.1.93.2.3.1.1.2,PINT-MIB::pintServerUserIdCallsReceived,Counter32,read-only,,current,,Number of calls received from the specific user.
.1.3.6.1.2.1.93.2.3.1.1.3,PINT-MIB::pintServerUserIdSuccessfulCalls,Counter32,read-only,,current,,Number of calls from the user successfully completed.
.1.3.6.1.2.1.93.2.3.1.1.4,PINT-MIB::pintServerUserIdDisconnectedCalls,Counter32,read-only,,current,,Number of calls received from the user that were disconnected (failed).
.1.3.6.1.2.1.93.2.3.1.1.5,PINT-MIB::pintServerUserIdDiscUIdAFailCalls,Counter32,read-only,,current,,Number of calls from the user that were disconnected because of user authorization failure.
.1.3.6.1.2.1.93.2.3.1.1.6,PINT-MIB::pintServerUserIdEFProbCalls,Counter32,read-only,,current,,Number of calls from the user that were disconnected because of egress facility problems.
.1.3.6.1.2.1.93.2.4,PINT-MIB::pintServerGatewayPerf,,,,,,
.1.3.6.1.2.1.93.2.4.1,PINT-MIB::pintServerGatewayStatsTable,,not-accessible,,current,,Table displaying the monitored gateway statistics.
.1.3.6.1.2.1.93.2.4.1.1,PINT-MIB::pintServerGatewayStatsEntry,,not-accessible,pintRegisteredGatewayName:pintServerServiceTypeIndex:pintServerPerfStatPeriodIndex,current,,Entries in the gateway table. One entry is defined for each gateway identified by name, each monitored service type and performance statistics collection period.
.1.3.6.1.2.1.93.2.4.1.1.1,PINT-MIB::pintServerGatewayCallsReceived,Counter32,read-only,,current,,Number of calls received at the specified gateway.
.1.3.6.1.2.1.93.2.4.1.1.2,PINT-MIB::pintServerGatewaySuccessfulCalls,Counter32,read-only,,current,,Number of calls successfully completed at the specified gateway.
.1.3.6.1.2.1.93.2.4.1.1.3,PINT-MIB::pintServerGatewayDisconnectedCalls,Counter32,read-only,,current,,Number of calls that were disconnected (failed) at the specified gateway.
.1.3.6.1.2.1.93.3,PINT-MIB::pintMibConformance,,,,,,
.1.3.6.1.2.1.93.3.1,PINT-MIB::pintMibCompliances,,,,,,
.1.3.6.1.2.1.93.3.1.1,PINT-MIB::pintMibCompliance,,,,,,Describes the requirements for conformance to the PINT MIB.
.1.3.6.1.2.1.93.3.2,PINT-MIB::pintMibGroups,,,,,,
.1.3.6.1.2.1.93.3.2.1,PINT-MIB::pintMibConfigGroup,,,,,,A collection of objects providing configuration information for a PINT Server.
.1.3.6.1.2.1.93.3.2.2,PINT-MIB::pintMibMonitorGroup,,,,,,A collection of objects providing monitoring information for a PINT Server.
.1.3.6.1.2.1.94,CIRCUIT-IF-MIB::circuitIfMIB,,,,,,The MIB module to allow insertion of selected circuit into the ifTable.
.1.3.6.1.2.1.94.1,CIRCUIT-IF-MIB::ciObjects,,,,,,
.1.3.6.1.2.1.94.1.1,CIRCUIT-IF-MIB::ciCircuitTable,,not-accessible,,current,,The Circuit Interface Circuit Table.
.1.3.6.1.2.1.94.1.1.1,CIRCUIT-IF-MIB::ciCircuitEntry,,not-accessible,ciCircuitObject:ciCircuitFlow,current,,An entry in the Circuit Interface Circuit Table.
.1.3.6.1.2.1.94.1.1.1.1,CIRCUIT-IF-MIB::ciCircuitObject,OBJECT,not-accessible,,current,,This value contains the RowPointer that uniquely describes the circuit that is to be added to this table. Any RowPointer that will force the size of OBJECT IDENTIFIER of the row to grow beyond the legal limit MUST be rejected. The purpose of this object is to point a network manager to the table in which the circuit was created as well as define the circuit on which the interface is defined. Valid tables for this object include the frCircuitTable from the Frame Relay DTE MIB(FRAME-RELAY-DTE-MIB), the frPVCEndptTable from the Frame Relay Service MIB (FRNETSERV-MIB), and the aal5VccTable from the ATM MIB (ATM MIB). However, including circuits from other MIB tables IS NOT prohibited.
.1.3.6.1.2.1.94.1.1.1.2,CIRCUIT-IF-MIB::ciCircuitFlow,INTEGER,not-accessible,,current,transmit(1):receive(2):both(3),The direction of data flow through the circuit for which the virtual interface is defined. The following define the information that the virtual interface will report. transmit(1) - Only transmitted frames receive(2) - Only received frames both(3) - Both transmitted and received frames. It is recommended that the ifDescr of the circuit interfaces that are not both(3) SHOULD have text warning the operators that the particular interface represents only half the traffic on the circuit.
.1.3.6.1.2.1.94.1.1.1.3,CIRCUIT-IF-MIB::ciCircuitStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the current row. This object is used to add, delete, and disable rows in this table. When the status changes to active(1), a row will also be added to the interface map table below and a row will be added to the ifTable. These rows SHOULD not be removed until the status is changed from active(1). The value of ifIndex for the row that is added to the ifTable is determined by the agent and MUST follow the rules of the ifTable. The value of ifType for that interface will be frDlciEndPt(193) for a frame relay circuit, atmVciEndPt(194) for an ATM circuit, or another ifType defining the circuit type for any other circuit. When this object is set to destroy(6), the associated row in the interface map table will be removed and the ifIndex will be removed from the ifTable. Removing the ifIndex MAY initiate a chain of events that causes changes to other tables as well. The rows added to this table MUST have a valid object identifier for ciCircuitObject. This means that the referenced object must exist and it must be in a table that supports circuits. The object referenced by ciCircuitObject MUST exist prior to transitioning a row to active(1). If at any point the object referenced by ciCircuitObject does not exist or the row containing it is not in the active(1) state, the status SHOULD either age out the row or report notReady(3). The effects transitioning from active(1) to notReady(3) are the same as those caused by setting the status to destroy(6). Each row in this table relies on information from other MIB modules. The rules persistence of data SHOULD follow the same rules as those of the underlying MIB module. For example, if the circuit defined by ciCircuitObject would normally be stored in non-volatile memory, then the row SHOULD also be non-volatile.
.1.3.6.1.2.1.94.1.1.1.4,CIRCUIT-IF-MIB::ciCircuitIfIndex,Integer32,read-only,,current,,The ifIndex that the agent assigns to this row.
.1.3.6.1.2.1.94.1.1.1.5,CIRCUIT-IF-MIB::ciCircuitCreateTime,TimeTicks,read-only,,current,,This object returns the value of sysUpTime at the time the value of ciCircuitStatus last transitioned to active(1). If ciCircuitStatus has never been active(1), this object SHOULD return 0.
.1.3.6.1.2.1.94.1.1.1.6,CIRCUIT-IF-MIB::ciCircuitStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type used for this row.
.1.3.6.1.2.1.94.1.2,CIRCUIT-IF-MIB::ciIfMapTable,,not-accessible,,current,,The Circuit Interface Map Table.
.1.3.6.1.2.1.94.1.2.1,CIRCUIT-IF-MIB::ciIfMapEntry,,not-accessible,ifIndex,current,,An entry in the Circuit Interface Map Table.
.1.3.6.1.2.1.94.1.2.1.1,CIRCUIT-IF-MIB::ciIfMapObject,OBJECT,read-only,,current,,This value contains the value of RowPointer that corresponds to the current ifIndex.
.1.3.6.1.2.1.94.1.2.1.2,CIRCUIT-IF-MIB::ciIfMapFlow,INTEGER,read-only,,current,transmit(1):receive(2):both(3),The value contains the value of ciCircuitFlow that corresponds to the current ifIndex.
.1.3.6.1.2.1.94.1.3,CIRCUIT-IF-MIB::ciIfLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent change to ciCircuitStatus for any row in ciCircuitTable.
.1.3.6.1.2.1.94.1.4,CIRCUIT-IF-MIB::ciIfNumActive,Gauge32,read-only,,current,,The number of active rows in ciCircuitTable.
.1.3.6.1.2.1.94.2,CIRCUIT-IF-MIB::ciCapabilities,,,,,,
.1.3.6.1.2.1.94.3,CIRCUIT-IF-MIB::ciConformance,,,,,,
.1.3.6.1.2.1.94.3.1,CIRCUIT-IF-MIB::ciMIBGroups,,,,,,
.1.3.6.1.2.1.94.3.1.1,CIRCUIT-IF-MIB::ciCircuitGroup,,,,,,A collection of required objects providing information from the circuit table.
.1.3.6.1.2.1.94.3.1.2,CIRCUIT-IF-MIB::ciIfMapGroup,,,,,,A collection of required objects providing information from the interface map table.
.1.3.6.1.2.1.94.3.1.3,CIRCUIT-IF-MIB::ciStatsGroup,,,,,,A collection of statistical metrics used to help manage the ciCircuitTable.
.1.3.6.1.2.1.94.3.2,CIRCUIT-IF-MIB::ciMIBCompliances,,,,,,
.1.3.6.1.2.1.94.3.2.1,CIRCUIT-IF-MIB::ciCompliance,,,,,,The compliance statement for SNMP entities which support of the Circuit Interfaces MIB module. This group defines the minimum level of support required for compliance.
.1.3.6.1.2.1.95,FRSLD-MIB::frsldMIB,,,,,,The MIB module to describe generic objects for FRF.13 Frame Relay Service Level Definitions.
.1.3.6.1.2.1.95.1,FRSLD-MIB::frsldObjects,,,,,,
.1.3.6.1.2.1.95.1.1,FRSLD-MIB::frsldPvcCtrlTable,,not-accessible,,current,,The Frame Relay Service Level Definitions PVC control table.
.1.3.6.1.2.1.95.1.1.1,FRSLD-MIB::frsldPvcCtrlEntry,,not-accessible,ifIndex:frsldPvcCtrlDlci:frsldPvcCtrlTransmitRP:frsldPvcCtrlReceiveRP,current,,An entry in the Frame Relay Service Level Definitions PVC control table.
.1.3.6.1.2.1.95.1.1.1.1,FRSLD-MIB::frsldPvcCtrlDlci,Integer32,not-accessible,,current,,The value of this object is equal to the DLCI value for this PVC.
.1.3.6.1.2.1.95.1.1.1.2,FRSLD-MIB::frsldPvcCtrlTransmitRP,INTEGER,not-accessible,,current,srcLocalRP(1):ingTxLocalRP(2):tpTxLocalRP(3):eqiTxLocalRP(4):eqoTxLocalRP(5):otherTxLocalRP(6):srcRemoteRP(7):ingTxRemoteRP(8):tpTxRemoteRP(9):eqiTxRemoteRP(10):eqoTxRemoteRP(11):otherTxRemoteRP(12),The reference point this PVC uses for calculation of transmitter related statistics. This object together with frsldPvcCtrlReceiveRP define the measurement domain.
.1.3.6.1.2.1.95.1.1.1.3,FRSLD-MIB::frsldPvcCtrlReceiveRP,INTEGER,not-accessible,,current,desLocalRP(1):ingRxLocalRP(2):tpRxLocalRP(3):eqiRxLocalRP(4):eqoRxLocalRP(5):otherRxLocalRP(6):desRemoteRP(7):ingRxRemoteRP(8):tpRxRemoteRP(9):eqiRxRemoteRP(10):eqoRxRemoteRP(11):otherRxRemoteRP(12),The reference point this PVC uses for calculation of receiver related statistics. This object together with frsldPvcCtrlTransmitRP define the measurement domain.
.1.3.6.1.2.1.95.1.1.1.4,FRSLD-MIB::frsldPvcCtrlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the current row. This object is used to add, delete, and disable rows in this table. When the status changes to active(1) for the first time, a row will also be added to the data table below. This row SHOULD not be removed until the status is changed to deleted. When this object is set to destroy(6), all associated sample and data table rows will also be deleted. When this object is changed from active(1) to any other valid value, the defined purge behavior will affect the data and sample tables. The rows added to this table MUST have a valid ifIndex and an ifType related to frame relay. Further, the reference points referred to by frsldPvcCtrlTransmitRP and frsldPvcCtrlReceiveRP MUST be supported (see the frsldRPCaps object). If at any point the row is not in the active(1) state and the DLCI no longer exists, the state SHOULD report notReady(3). The data in this table SHOULD persist through power cycles. The symantics of readiness for the rows still applies. This means that it is possible for a row to be reprovisioned as notReady(3) if the underlying DLCI does not persist.
.1.3.6.1.2.1.95.1.1.1.5,FRSLD-MIB::frsldPvcCtrlPacketFreq,Integer32,read-create,,current,,The frequency in seconds between initiation of specialized packets used to collect delay and / or delivery information as supported by the device. A value of zero indicates that no packets will be sent.
.1.3.6.1.2.1.95.1.1.1.6,FRSLD-MIB::frsldPvcCtrlDelayFrSize,Integer32,read-create,,current,,The size of the payload in the frame used for calculation of network delay.
.1.3.6.1.2.1.95.1.1.1.7,FRSLD-MIB::frsldPvcCtrlDelayType,INTEGER,read-create,,current,oneWay(1):roundTrip(2),The type of delay measurement performed.
.1.3.6.1.2.1.95.1.1.1.8,FRSLD-MIB::frsldPvcCtrlDelayTimeOut,Integer32,read-create,,current,,A delay frame will count as a missed poll if it is not updated in the time specified by frsldPvcCtrlDelayTimeOut.
.1.3.6.1.2.1.95.1.1.1.9,FRSLD-MIB::frsldPvcCtrlPurge,Integer32,read-create,,current,,This object defines the amount of time the device will wait, after discovering that a DLCI does not exist, the DLCI was deleted or the value of frsldPvcCtrlStatus changes from active(1) to either notInService(2) or notReady(3), prior to automatically purging the history in the sample tables and resetting the data in the data tables to all zeroes. If frsldPvcCtrlStatus is manually set to destroy(6), this object does not apply.
.1.3.6.1.2.1.95.1.1.1.10,FRSLD-MIB::frsldPvcCtrlDeleteOnPurge,INTEGER,read-create,,current,none(1):sampleContols(2):all(3),This object defines whether rows will automatically be deleted from the tables when the information is purged. - A value of none(1) indicates that no rows will deleted. The last known values will be preserved. - A value of sampleControls(2) indicates that all associated sample control rows will be deleted. - A value of all(3) indicates that all associated rows SHOULD be deleted.
.1.3.6.1.2.1.95.1.1.1.11,FRSLD-MIB::frsldPvcCtrlLastPurgeTime,TimeTicks,read-only,,current,,This object returns the value of sysUpTime at the time the information was last purged. This value SHOULD be set to the sysUpTime upon setting frsldPvcCtrlStatus to active(1) for the first time. Each time a discontinuity in the counters occurs, this value MUST be set to the sysUpTime. If frsldPvcCtrlStatus has never been active(1), this object SHOULD return 0. This object SHOULD be used as the discontinuity timer for the counters in frsldPvcDataTable.
.1.3.6.1.2.1.95.1.2,FRSLD-MIB::frsldSmplCtrlTable,,not-accessible,,current,,The Frame Relay Service Level Definitions sampling control table.
.1.3.6.1.2.1.95.1.2.1,FRSLD-MIB::frsldSmplCtrlEntry,,not-accessible,ifIndex:frsldPvcCtrlDlci:frsldPvcCtrlTransmitRP:frsldPvcCtrlReceiveRP:frsldSmplCtrlIdx,current,,An entry in the Frame Relay Service Level Definitions sample control table.
.1.3.6.1.2.1.95.1.2.1.1,FRSLD-MIB::frsldSmplCtrlIdx,Integer32,not-accessible,,current,,The unique index for this row in the sample control table.
.1.3.6.1.2.1.95.1.2.1.2,FRSLD-MIB::frsldSmplCtrlStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the current row. This object is used to add, delete, and disable rows in this table. This row SHOULD NOT be removed until the status is changed to destroy(6). When the status changes to active(1), the collection in the sample tables below will be activated. The rows added to this table MUST have a valid ifIndex, an ifType related to frame relay, frsldPvcCtrlDlci MUST exist for the specified ifIndex and frsldPvcCtrlStatus MUST have a value of active(1). The value of frsldPvcCtrlStatus MUST be active(1) to transition this object to active(1). If the value of frsldPvcCtrlStatus becomes anything other than active(1) when the state of this object is not active(1), this object SHOULD be set to notReady(3). The data in this table SHOULD persist through power cycles. The symantics of readiness for the rows still applies. This means that it is possible for a row to be reprovisioned as notReady(3) if the underlying DLCI does not persist.
.1.3.6.1.2.1.95.1.2.1.3,FRSLD-MIB::frsldSmplCtrlColPeriod,Integer32,read-create,,current,,The amount of time in seconds that defines a period of collection for the statistics. At the end of each period, the statistics will be sampled and a row is added to the sample table.
.1.3.6.1.2.1.95.1.2.1.4,FRSLD-MIB::frsldSmplCtrlBuckets,Integer32,read-create,,current,,The number of discrete buckets over which the data statistics are sampled. When this object is created or modified, the device SHOULD attempt to set the frsldSmplCtrlBuckets- Granted to a value as close as is possible depending upon the implementation and the available resources.
.1.3.6.1.2.1.95.1.2.1.5,FRSLD-MIB::frsldSmplCtrlBucketsGranted,Integer32,read-only,,current,,The number of discrete buckets granted. This object will return 0 until frsldSmplCtrlStatus is set to active(1). At that time the buckets will be allocated depending upon implementation and available resources.
.1.3.6.1.2.1.95.1.3,FRSLD-MIB::frsldPvcDataTable,,not-accessible,,current,,The Frame Relay Service Level Definitions data table. This table contains accumulated values of the collected data. It is the table that should be referenced by external polling mechanisms if time based polling be desired.
.1.3.6.1.2.1.95.1.3.1,FRSLD-MIB::frsldPvcDataEntry,,not-accessible,ifIndex:frsldPvcCtrlDlci:frsldPvcCtrlTransmitRP:frsldPvcCtrlReceiveRP,current,,An entry in the Frame Relay Service Level Definitions data table.
.1.3.6.1.2.1.95.1.3.1.1,FRSLD-MIB::frsldPvcDataMissedPolls,Counter32,read-only,,current,,The total number of polls that have been determined to be missed. These polls are typically associated with the calculation of delay but may also be used for the calculation of other statistics. If an anticipated poll is not received in a reasonable amount of time, it should be counted as missed. The value used to determine the reasonable amount of time is contained in frsldPvcCtrlDelayTimeOut. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.2,FRSLD-MIB::frsldPvcDataFrDeliveredC,Counter32,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.3,FRSLD-MIB::frsldPvcDataFrDeliveredE,Counter32,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.4,FRSLD-MIB::frsldPvcDataFrOfferedC,Counter32,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP within CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.5,FRSLD-MIB::frsldPvcDataFrOfferedE,Counter32,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP in excess of the CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.6,FRSLD-MIB::frsldPvcDataDataDeliveredC,Counter32,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.7,FRSLD-MIB::frsldPvcDataDataDeliveredE,Counter32,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.8,FRSLD-MIB::frsldPvcDataDataOfferedC,Counter32,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP within CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.9,FRSLD-MIB::frsldPvcDataDataOfferedE,Counter32,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP in excess of the CIR. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.10,FRSLD-MIB::frsldPvcDataHCFrDeliveredC,Counter64,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR. This object is a 64-bit version of frsldPvcDataFrDeliveredC. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.11,FRSLD-MIB::frsldPvcDataHCFrDeliveredE,Counter64,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR. This object is a 64-bit version of frsldPvcDataFrDeliveredE. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.12,FRSLD-MIB::frsldPvcDataHCFrOfferedC,Counter64,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP within CIR. This object is a 64-bit version of frsldPvcDataFrOfferedC. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.13,FRSLD-MIB::frsldPvcDataHCFrOfferedE,Counter64,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP in excess of the CIR. This object is a 64-bit version of frsldPvcDataFrOfferedE. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.14,FRSLD-MIB::frsldPvcDataHCDataDeliveredC,Counter64,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR. This object is a 64-bit version of frsldPvcDataDataDeliveredC. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.15,FRSLD-MIB::frsldPvcDataHCDataDeliveredE,Counter64,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR. This object is a 64-bit version of frsldPvcDataDataDeliveredE. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.16,FRSLD-MIB::frsldPvcDataHCDataOfferedC,Counter64,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP within CIR. This object is a 64-bit version of frsldPvcDataDataOfferedC. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.17,FRSLD-MIB::frsldPvcDataHCDataOfferedE,Counter64,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP in excess of the CIR. This object is a 64-bit version of frsldPvcDataDataOfferedE. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.3.1.18,FRSLD-MIB::frsldPvcDataUnavailableTime,TimeTicks,read-only,,current,,The amount of time this PVC was declared unavailable for any reason since this row was created.
.1.3.6.1.2.1.95.1.3.1.19,FRSLD-MIB::frsldPvcDataUnavailables,Counter32,read-only,,current,,The number of times this PVC was declared unavailable for any reason since this row was created. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by frsldPvcCtrlLastPurgeTime.
.1.3.6.1.2.1.95.1.4,FRSLD-MIB::frsldPvcSampleTable,,not-accessible,,current,,The Frame Relay Service Level Definitions sample table.
.1.3.6.1.2.1.95.1.4.1,FRSLD-MIB::frsldPvcSampleEntry,,not-accessible,ifIndex:frsldPvcCtrlDlci:frsldPvcCtrlTransmitRP:frsldPvcCtrlReceiveRP:frsldSmplCtrlIdx:frsldPvcSmplIdx,current,,An entry in the Frame Relay Service Level Definitions data sample table.
.1.3.6.1.2.1.95.1.4.1.1,FRSLD-MIB::frsldPvcSmplIdx,Integer32,not-accessible,,current,,The bucket index of the current sample. This increments once for each new bucket in the table.
.1.3.6.1.2.1.95.1.4.1.2,FRSLD-MIB::frsldPvcSmplDelayMin,Gauge32,read-only,,current,,The minimum delay reported in microseconds measured for any information packet that arrived during this interval. A value of zero means that no data is available.
.1.3.6.1.2.1.95.1.4.1.3,FRSLD-MIB::frsldPvcSmplDelayMax,Gauge32,read-only,,current,,The largest delay reported in microseconds measured for any information packet that arrived during this interval. A value of zero means that no data is available.
.1.3.6.1.2.1.95.1.4.1.4,FRSLD-MIB::frsldPvcSmplDelayAvg,Gauge32,read-only,,current,,The average delay reported in microseconds measured for all delay packets that arrived during this interval. A value of zero means that no data is available.
.1.3.6.1.2.1.95.1.4.1.5,FRSLD-MIB::frsldPvcSmplMissedPolls,Gauge32,read-only,,current,,The total number of polls that were missed during this interval.
.1.3.6.1.2.1.95.1.4.1.6,FRSLD-MIB::frsldPvcSmplFrDeliveredC,Gauge32,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCFrDeliveredC.
.1.3.6.1.2.1.95.1.4.1.7,FRSLD-MIB::frsldPvcSmplFrDeliveredE,Gauge32,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCFrDeliveredE.
.1.3.6.1.2.1.95.1.4.1.8,FRSLD-MIB::frsldPvcSmplFrOfferedC,Gauge32,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP within CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCFrOfferedC.
.1.3.6.1.2.1.95.1.4.1.9,FRSLD-MIB::frsldPvcSmplFrOfferedE,Gauge32,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP in excess of the CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCFrOfferedE.
.1.3.6.1.2.1.95.1.4.1.10,FRSLD-MIB::frsldPvcSmplDataDeliveredC,Gauge32,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCDataDeliveredC.
.1.3.6.1.2.1.95.1.4.1.11,FRSLD-MIB::frsldPvcSmplDataDeliveredE,Gauge32,read-only,,current,,The number of octets that were received at frsldPvcCtrlDeliveredRP and determined to have been sent in excess of the CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCDataDeliveredE.
.1.3.6.1.2.1.95.1.4.1.12,FRSLD-MIB::frsldPvcSmplDataOfferedC,Gauge32,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP within CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCDataOfferredC.
.1.3.6.1.2.1.95.1.4.1.13,FRSLD-MIB::frsldPvcSmplDataOfferedE,Gauge32,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP in excess of the CIR during this interval. If it is the case that the high capacity counters are also used, this MUST report the value of the lower 32 bits of the CounterBasedGauge64 value of frsldPvcSmplHCDataOfferedE.
.1.3.6.1.2.1.95.1.4.1.14,FRSLD-MIB::frsldPvcSmplHCFrDeliveredC,Counter64,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR during this interval. This object is a 64-bit version of frsldPvcSmplFrDeliveredC.
.1.3.6.1.2.1.95.1.4.1.15,FRSLD-MIB::frsldPvcSmplHCFrDeliveredE,Counter64,read-only,,current,,The number of frames that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR during this interval. This object is a 64-bit version of frsldPvcSmpl- FrDeliveredE.
.1.3.6.1.2.1.95.1.4.1.16,FRSLD-MIB::frsldPvcSmplHCFrOfferedC,Counter64,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP within CIR during this interval. This object is a 64-bit version of frsldPvcSmplFrOfferedC.
.1.3.6.1.2.1.95.1.4.1.17,FRSLD-MIB::frsldPvcSmplHCFrOfferedE,Counter64,read-only,,current,,The number of frames that were offered through frsldPvcCtrlTransmitRP in excess of the CIR during this interval. This object is a 64-bit version of frsldPvcSmplFrOfferedE.
.1.3.6.1.2.1.95.1.4.1.18,FRSLD-MIB::frsldPvcSmplHCDataDeliveredC,Counter64,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent within CIR during this interval. This value is a 64-bit version of frsldPvcSmplDataDeliveredC.
.1.3.6.1.2.1.95.1.4.1.19,FRSLD-MIB::frsldPvcSmplHCDataDeliveredE,Counter64,read-only,,current,,The number of octets that were received at frsldPvcCtrlReceiveRP and determined to have been sent in excess of the CIR during this interval. This value is a 64-bit version of frsldPvcSmplData- DeliveredE.
.1.3.6.1.2.1.95.1.4.1.20,FRSLD-MIB::frsldPvcSmplHCDataOfferedC,Counter64,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP within CIR during this interval. This value is a 64-bit version of frsldPvcSmplDataOfferedC.
.1.3.6.1.2.1.95.1.4.1.21,FRSLD-MIB::frsldPvcSmplHCDataOfferedE,Counter64,read-only,,current,,The number of octets that were offered through frsldPvcCtrlTransmitRP in excess of the CIR during this interval. This object is a 64-bit version of frsldPvcSmplDataOfferedE.
.1.3.6.1.2.1.95.1.4.1.22,FRSLD-MIB::frsldPvcSmplUnavailableTime,TimeTicks,read-only,,current,,The amount of time this PVC was declared unavailable for any reason during this interval.
.1.3.6.1.2.1.95.1.4.1.23,FRSLD-MIB::frsldPvcSmplUnavailables,Gauge32,read-only,,current,,The number of times this PVC was declared unavailable for any reason during this interval.
.1.3.6.1.2.1.95.1.4.1.24,FRSLD-MIB::frsldPvcSmplStartTime,TimeTicks,read-only,,current,,The value of sysUpTime when this sample interval started.
.1.3.6.1.2.1.95.1.4.1.25,FRSLD-MIB::frsldPvcSmplEndTime,TimeTicks,read-only,,current,,The value of sysUpTime when this sample interval ended. No data will be reported and the row will not appear in the table until the sample has been collected.
.1.3.6.1.2.1.95.2,FRSLD-MIB::frsldCapabilities,,,,,,
.1.3.6.1.2.1.95.2.1,FRSLD-MIB::frsldPvcCtrlWriteCaps,BITS,read-only,,current,frsldPvcCtrlStatus(0):frsldPvcCtrlPacketFreq(1):frsldPvcCtrlDelayFrSize(2):frsldPvcCtrlDelayType(3):frsldPvcCtrlDelayTimeOut(4):frsldPvcCtrlPurge(5):frsldPvcCtrlDeleteOnPurge(6),This object specifies the write capabilities for the read-create objects of the PVC Control table. If the corresponding bit is enabled (1), the agent supports writes to that object.
.1.3.6.1.2.1.95.2.2,FRSLD-MIB::frsldSmplCtrlWriteCaps,BITS,read-only,,current,frsldSmplCtrlStatus(0):frsldSmplCtrlBuckets(1),This object specifies the write capabilities for the read-create objects of the Sample Control table. If the corresponding bit is enabled (1), the agent supports writes to that object.
.1.3.6.1.2.1.95.2.3,FRSLD-MIB::frsldRPCaps,BITS,read-only,,current,srcLocalRP(0):ingTxLocalRP(1):tpTxLocalRP(2):eqiTxLocalRP(3):eqoTxLocalRP(4):otherTxLocalRP(5):srcRemoteRP(6):ingTxRemoteRP(7):tpTxRemoteRP(8):eqiTxRemoteRP(9):eqoTxRemoteRP(10):otherTxRemoteRP(11):desLocalRP(12):ingRxLocalRP(13):tpRxLocalRP(14):eqiRxLocalRP(15):eqoRxLocalRP(16):otherRxLocalRP(17):desRemoteRP(18):ingRxRemoteRP(19):tpRxRemoteRP(20):eqiRxRemoteRP(21):eqoRxRemoteRP(22):otherRxRemoteRP(23),This object specifies the reference points that the agent supports. This object allows the management application to discover which rows can be created on a specific device.
.1.3.6.1.2.1.95.2.4,FRSLD-MIB::frsldMaxPvcCtrls,Integer32,read-write,,current,,The maximum number of control rows that can be created in frsldPvcCtrlTable. Sets to this object lower than the current value of frsldNumPvcCtrls should result in inconsistentValue.
.1.3.6.1.2.1.95.2.5,FRSLD-MIB::frsldNumPvcCtrls,Gauge32,read-only,,current,,The current number of rows in frsldPvcCtrlTable.
.1.3.6.1.2.1.95.2.6,FRSLD-MIB::frsldMaxSmplCtrls,Integer32,read-write,,current,,The maximum number of control rows that can be created in frsldSmplCtrlTable. Sets to this object lower than the current value of frsldNumSmplCtrls should result in inconsistentValue.
.1.3.6.1.2.1.95.2.7,FRSLD-MIB::frsldNumSmplCtrls,Gauge32,read-only,,current,,The current number of rows in frsldSmplCtrlTable.
.1.3.6.1.2.1.95.3,FRSLD-MIB::frsldConformance,,,,,,
.1.3.6.1.2.1.95.3.1,FRSLD-MIB::frsldMIBGroups,,,,,,
.1.3.6.1.2.1.95.3.1.1,FRSLD-MIB::frsldPvcReqCtrlGroup,,,,,,A collection of required objects providing control information applicable to a PVC which implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.2,FRSLD-MIB::frsldPvcPacketGroup,,,,,,A collection of optional objects providing packet level control information applicable to a PVC which implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.3,FRSLD-MIB::frsldPvcDelayCtrlGroup,,,,,,A collection of optional objects providing delay control information applicable to a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcPacketGroup and frsldPvcDelayDataGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.4,FRSLD-MIB::frsldPvcSampleCtrlGroup,,,,,,A collection of optional objects providing sample control information applicable to a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcReqDataGroup and frsldPvcSampleGeneralGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.5,FRSLD-MIB::frsldPvcReqDataGroup,,,,,,A collection of required objects providing data collected on a PVC which implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.6,FRSLD-MIB::frsldPvcDelayDataGroup,,,,,,A collection of optional objects providing delay data collected on a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcDelayCtrlGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.7,FRSLD-MIB::frsldPvcHCFrameDataGroup,,,,,,A collection of optional objects providing high capacity frame data collected on a PVC which implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.8,FRSLD-MIB::frsldPvcHCOctetDataGroup,,,,,,A collection of optional objects providing high capacity octet data collected on a PVC which implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.9,FRSLD-MIB::frsldPvcSampleDelayGroup,,,,,,A collection of optional objects providing delay sample data collected on a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcDelayCtrlGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.10,FRSLD-MIB::frsldPvcSampleDataGroup,,,,,,A collection of optional objects providing data and frame delivery sample data collected on a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcReqDataGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.11,FRSLD-MIB::frsldPvcSampleHCFrameGroup,,,,,,A collection of optional objects providing high capacity frame delivery sample data collected on a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcHCFrameDataGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.12,FRSLD-MIB::frsldPvcSampleHCDataGroup,,,,,,A collection of optional objects providing high capacity data delivery sample data collected on a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcHCOctetDataGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.13,FRSLD-MIB::frsldPvcSampleAvailGroup,,,,,,A collection of optional objects providing availability sample data collected on a PVC which implements Service Level Definitions. If this group is implemented, frsldPvcReqDataGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.14,FRSLD-MIB::frsldPvcSampleGeneralGroup,,,,,,A collection of optional objects providing general sample data collected on a PVC which implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.15,FRSLD-MIB::frsldCapabilitiesGroup,,,,,,A collection of required objects providing capability information and control for this MIB module.
.1.3.6.1.2.1.95.3.2,FRSLD-MIB::frsldMIBCompliances,,,,,,
.1.3.6.1.2.1.95.3.2.1,FRSLD-MIB::frsldCompliance,,,,,,The compliance statement for SNMP entities which support with Frame Relay Service Level Definitions. This group defines the minimum level of support required for compliance.
.1.3.6.1.2.1.96,DIFFSERV-DSCP-TC::diffServDSCPTC,,,,,,The Textual Conventions defined in this module should be used whenever a Differentiated Services Code Point is used in a MIB.
.1.3.6.1.2.1.97,DIFFSERV-MIB::diffServMib,,,,,,This MIB defines the objects necessary to manage a device that uses the Differentiated Services Architecture described in RFC 2475. The Conceptual Model of a Differentiated Services Router provides supporting information on how such a router is modeled.
.1.3.6.1.2.1.97.1,DIFFSERV-MIB::diffServMIBObjects,,,,,,
.1.3.6.1.2.1.97.1.1,DIFFSERV-MIB::diffServDataPath,,,,,,
.1.3.6.1.2.1.97.1.1.1,DIFFSERV-MIB::diffServDataPathTable,,not-accessible,,current,,The data path table contains RowPointers indicating the start of the functional data path for each interface and traffic direction in this device. These may merge, or be separated into parallel data paths.
.1.3.6.1.2.1.97.1.1.1.1,DIFFSERV-MIB::diffServDataPathEntry,,not-accessible,ifIndex:diffServDataPathIfDirection,current,,An entry in the data path table indicates the start of a single Differentiated Services Functional Data Path in this device. These are associated with individual interfaces, logical or physical, and therefore are instantiated by ifIndex. Therefore, the interface index must have been assigned, according to the procedures applicable to that, before it can be meaningfully used. Generally, this means that the interface must exist. When diffServDataPathStorage is of type nonVolatile, however, this may reflect the configuration for an interface whose ifIndex has been assigned but for which the supporting implementation is not currently present.
.1.3.6.1.2.1.97.1.1.1.1.1,DIFFSERV-MIB::diffServDataPathIfDirection,INTEGER,not-accessible,,current,inbound(1):outbound(2),IfDirection specifies whether the reception or transmission path for this interface is in view.
.1.3.6.1.2.1.97.1.1.1.1.2,DIFFSERV-MIB::diffServDataPathStart,OBJECT,read-create,,current,,This selects the first Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry A value of zeroDotZero in this attribute indicates that no Differentiated Services treatment is performed on traffic of this data path. A pointer with the value zeroDotZero normally terminates a functional data path. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.1.1.1.3,DIFFSERV-MIB::diffServDataPathStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.1.1.1.4,DIFFSERV-MIB::diffServDataPathStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time.
.1.3.6.1.2.1.97.1.2,DIFFSERV-MIB::diffServClassifier,,,,,,
.1.3.6.1.2.1.97.1.2.1,DIFFSERV-MIB::diffServClfrNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServClfrId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.2.2,DIFFSERV-MIB::diffServClfrTable,,not-accessible,,current,,This table enumerates all the diffserv classifier functional data path elements of this device. The actual classification definitions are defined in diffServClfrElementTable entries belonging to each classifier. An entry in this table, pointed to by a RowPointer specifying an instance of diffServClfrStatus, is frequently used as the name for a set of classifier elements, which all use the index diffServClfrId. Per the semantics of the classifier element table, these entries constitute one or more unordered sets of tests which may be simultaneously applied to a message to classify it. The primary function of this table is to ensure that the value of diffServClfrId is unique before attempting to use it in creating a diffServClfrElementEntry. Therefore, the diffServClfrEntry must be created on the same SET as the diffServClfrElementEntry, or before the diffServClfrElementEntry is created.
.1.3.6.1.2.1.97.1.2.2.1,DIFFSERV-MIB::diffServClfrEntry,,not-accessible,diffServClfrId,current,,An entry in the classifier table describes a single classifier. All classifier elements belonging to the same classifier use the classifier's diffServClfrId as part of their index.
.1.3.6.1.2.1.97.1.2.2.1.1,DIFFSERV-MIB::diffServClfrId,Unsigned32,not-accessible,,current,,An index that enumerates the classifier entries. Managers should obtain new values for row creation in this table by reading diffServClfrNextFree.
.1.3.6.1.2.1.97.1.2.2.1.2,DIFFSERV-MIB::diffServClfrStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.2.2.1.3,DIFFSERV-MIB::diffServClfrStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.2.3,DIFFSERV-MIB::diffServClfrElementNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServClfrElementId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.2.4,DIFFSERV-MIB::diffServClfrElementTable,,not-accessible,,current,,The classifier element table enumerates the relationship between classification patterns and subsequent downstream Differentiated Services Functional Data Path elements. diffServClfrElementSpecific points to a filter that specifies the classification parameters. A classifier may use filter tables of different types together. One example of a filter table defined in this MIB is diffServMultiFieldClfrTable, for IP Multi-Field Classifiers (MFCs). Such an entry might identify anything from a single micro-flow (an identifiable sub-session packet stream directed from one sending transport to the receiving transport or transports), or aggregates of those such as the traffic from a host, traffic for an application, or traffic between two hosts using an application and a given DSCP. The standard Behavior Aggregate used in the Differentiated Services Architecture is encoded as a degenerate case of such an aggregate - the traffic using a particular DSCP value. Filter tables for other filter types may be defined elsewhere.
.1.3.6.1.2.1.97.1.2.4.1,DIFFSERV-MIB::diffServClfrElementEntry,,not-accessible,diffServClfrId:diffServClfrElementId,current,,An entry in the classifier element table describes a single element of the classifier.
.1.3.6.1.2.1.97.1.2.4.1.1,DIFFSERV-MIB::diffServClfrElementId,Unsigned32,not-accessible,,current,,An index that enumerates the Classifier Element entries. Managers obtain new values for row creation in this table by reading diffServClfrElementNextFree.
.1.3.6.1.2.1.97.1.2.4.1.2,DIFFSERV-MIB::diffServClfrElementPrecedence,Unsigned32,read-create,,current,,The relative order in which classifier elements are applied: higher numbers represent classifier element with higher precedence. Classifier elements with the same order must be unambiguous i.e. they must define non-overlapping patterns, and are considered to be applied simultaneously to the traffic stream. Classifier elements with different order may overlap in their filters: the classifier element with the highest order that matches is taken. On a given interface, there must be a complete classifier in place at all times in the ingress direction. This means one or more filters must match any possible pattern. There is no such requirement in the egress direction.
.1.3.6.1.2.1.97.1.2.4.1.3,DIFFSERV-MIB::diffServClfrElementNext,OBJECT,read-create,,current,,This attribute provides one branch of the fan-out functionality of a classifier described in the Informal Differentiated Services Model section 4.1. This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.2.4.1.4,DIFFSERV-MIB::diffServClfrElementSpecific,OBJECT,read-create,,current,,A pointer to a valid entry in another table, filter table, that describes the applicable classification parameters, e.g. an entry in diffServMultiFieldClfrTable. The value zeroDotZero is interpreted to match anything not matched by another classifier element - only one such entry may exist for each classifier. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the element is ignored.
.1.3.6.1.2.1.97.1.2.4.1.5,DIFFSERV-MIB::diffServClfrElementStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.2.4.1.6,DIFFSERV-MIB::diffServClfrElementStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.2.5,DIFFSERV-MIB::diffServMultiFieldClfrNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServMultiFieldClfrId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.2.6,DIFFSERV-MIB::diffServMultiFieldClfrTable,,not-accessible,,current,,A table of IP Multi-field Classifier filter entries that a system may use to identify IP traffic.
.1.3.6.1.2.1.97.1.2.6.1,DIFFSERV-MIB::diffServMultiFieldClfrEntry,,not-accessible,diffServMultiFieldClfrId,current,,An IP Multi-field Classifier entry describes a single filter.
.1.3.6.1.2.1.97.1.2.6.1.1,DIFFSERV-MIB::diffServMultiFieldClfrId,Unsigned32,not-accessible,,current,,An index that enumerates the MultiField Classifier filter entries. Managers obtain new values for row creation in this table by reading diffServMultiFieldClfrNextFree.
.1.3.6.1.2.1.97.1.2.6.1.2,DIFFSERV-MIB::diffServMultiFieldClfrAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of IP address used by this classifier entry. While other types of addresses are defined in the InetAddressType textual convention, and DNS names, a classifier can only look at packets on the wire. Therefore, this object is limited to IPv4 and IPv6 addresses.
.1.3.6.1.2.1.97.1.2.6.1.3,DIFFSERV-MIB::diffServMultiFieldClfrDstAddr,OCTET,read-create,,current,,The IP address to match against the packet's destination IP address. This may not be a DNS name, but may be an IPv4 or IPv6 prefix. diffServMultiFieldClfrDstPrefixLength indicates the number of bits that are relevant.
.1.3.6.1.2.1.97.1.2.6.1.4,DIFFSERV-MIB::diffServMultiFieldClfrDstPrefixLength,Unsigned32,read-create,,current,,The length of the CIDR Prefix carried in diffServMultiFieldClfrDstAddr. In IPv4 addresses, a length of 0 indicates a match of any address; a length of 32 indicates a match of a single host address, and a length between 0 and 32 indicates the use of a CIDR Prefix. IPv6 is similar, except that prefix lengths range from 0..128.
.1.3.6.1.2.1.97.1.2.6.1.5,DIFFSERV-MIB::diffServMultiFieldClfrSrcAddr,OCTET,read-create,,current,,The IP address to match against the packet's source IP address. This may not be a DNS name, but may be an IPv4 or IPv6 prefix. diffServMultiFieldClfrSrcPrefixLength indicates the number of bits that are relevant.
.1.3.6.1.2.1.97.1.2.6.1.6,DIFFSERV-MIB::diffServMultiFieldClfrSrcPrefixLength,Unsigned32,read-create,,current,,The length of the CIDR Prefix carried in diffServMultiFieldClfrSrcAddr. In IPv4 addresses, a length of 0 indicates a match of any address; a length of 32 indicates a match of a single host address, and a length between 0 and 32 indicates the use of a CIDR Prefix. IPv6 is similar, except that prefix lengths range from 0..128.
.1.3.6.1.2.1.97.1.2.6.1.7,DIFFSERV-MIB::diffServMultiFieldClfrDscp,Integer32,read-create,,current,,The value that the DSCP in the packet must have to match this entry. A value of -1 indicates that a specific DSCP value has not been defined and thus all DSCP values are considered a match.
.1.3.6.1.2.1.97.1.2.6.1.8,DIFFSERV-MIB::diffServMultiFieldClfrFlowId,Unsigned32,read-create,,current,,The flow identifier in an IPv6 header.
.1.3.6.1.2.1.97.1.2.6.1.9,DIFFSERV-MIB::diffServMultiFieldClfrProtocol,Unsigned32,read-create,,current,,The IP protocol to match against the IPv4 protocol number or the IPv6 Next- Header number in the packet. A value of 255 means match all. Note the protocol number of 255 is reserved by IANA, and Next-Header number of 0 is used in IPv6.
.1.3.6.1.2.1.97.1.2.6.1.10,DIFFSERV-MIB::diffServMultiFieldClfrDstL4PortMin,Unsigned32,read-create,,current,,The minimum value that the layer-4 destination port number in the packet must have in order to match this classifier entry.
.1.3.6.1.2.1.97.1.2.6.1.11,DIFFSERV-MIB::diffServMultiFieldClfrDstL4PortMax,Unsigned32,read-create,,current,,The maximum value that the layer-4 destination port number in the packet must have in order to match this classifier entry. This value must be equal to or greater than the value specified for this entry in diffServMultiFieldClfrDstL4PortMin.
.1.3.6.1.2.1.97.1.2.6.1.12,DIFFSERV-MIB::diffServMultiFieldClfrSrcL4PortMin,Unsigned32,read-create,,current,,The minimum value that the layer-4 source port number in the packet must have in order to match this classifier entry.
.1.3.6.1.2.1.97.1.2.6.1.13,DIFFSERV-MIB::diffServMultiFieldClfrSrcL4PortMax,Unsigned32,read-create,,current,,The maximum value that the layer-4 source port number in the packet must have in order to match this classifier entry. This value must be equal to or greater than the value specified for this entry in diffServMultiFieldClfrSrcL4PortMin.
.1.3.6.1.2.1.97.1.2.6.1.14,DIFFSERV-MIB::diffServMultiFieldClfrStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.2.6.1.15,DIFFSERV-MIB::diffServMultiFieldClfrStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.3,DIFFSERV-MIB::diffServMeter,,,,,,
.1.3.6.1.2.1.97.1.3.1,DIFFSERV-MIB::diffServMeterNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServMeterId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.3.2,DIFFSERV-MIB::diffServMeterTable,,not-accessible,,current,,This table enumerates specific meters that a system may use to police a stream of traffic. The traffic stream to be metered is determined by the Differentiated Services Functional Data Path Element(s) upstream of the meter i.e. by the object(s) that point to each entry in this table. This may include all traffic on an interface. Specific meter details are to be found in table entry referenced by diffServMeterSpecific.
.1.3.6.1.2.1.97.1.3.2.1,DIFFSERV-MIB::diffServMeterEntry,,not-accessible,diffServMeterId,current,,An entry in the meter table describes a single conformance level of a meter.
.1.3.6.1.2.1.97.1.3.2.1.1,DIFFSERV-MIB::diffServMeterId,Unsigned32,not-accessible,,current,,An index that enumerates the Meter entries. Managers obtain new values for row creation in this table by reading diffServMeterNextFree.
.1.3.6.1.2.1.97.1.3.2.1.2,DIFFSERV-MIB::diffServMeterSucceedNext,OBJECT,read-create,,current,,If the traffic does conform, this selects the next Differentiated Services Functional Data Path element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry A value of zeroDotZero in this attribute indicates that no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.3.2.1.3,DIFFSERV-MIB::diffServMeterFailNext,OBJECT,read-create,,current,,If the traffic does not conform, this selects the next Differentiated Services Functional Data Path element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.3.2.1.4,DIFFSERV-MIB::diffServMeterSpecific,OBJECT,read-create,,current,,This indicates the behavior of the meter by pointing to an entry containing detailed parameters. Note that entries in that specific table must be managed explicitly. For example, diffServMeterSpecific may point to an entry in diffServTBParamTable, which contains an instance of a single set of Token Bucket parameters. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the meter always succeeds.
.1.3.6.1.2.1.97.1.3.2.1.5,DIFFSERV-MIB::diffServMeterStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.3.2.1.6,DIFFSERV-MIB::diffServMeterStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.4,DIFFSERV-MIB::diffServTBParam,,,,,,
.1.3.6.1.2.1.97.1.4.1,DIFFSERV-MIB::diffServTBParamNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServTBParamId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.4.2,DIFFSERV-MIB::diffServTBParamTable,,not-accessible,,current,,This table enumerates a single set of token bucket meter parameters that a system may use to police a stream of traffic. Such meters are modeled here as having a single rate and a single burst size. Multiple entries are used when multiple rates/burst sizes are needed.
.1.3.6.1.2.1.97.1.4.2.1,DIFFSERV-MIB::diffServTBParamEntry,,not-accessible,diffServTBParamId,current,,An entry that describes a single set of token bucket parameters.
.1.3.6.1.2.1.97.1.4.2.1.1,DIFFSERV-MIB::diffServTBParamId,Unsigned32,not-accessible,,current,,An index that enumerates the Token Bucket Parameter entries. Managers obtain new values for row creation in this table by reading diffServTBParamNextFree.
.1.3.6.1.2.1.97.1.4.2.1.2,DIFFSERV-MIB::diffServTBParamType,OBJECT,read-create,,current,,The Metering algorithm associated with the Token Bucket parameters. zeroDotZero indicates this is unknown. Standard values for generic algorithms: diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, and diffServTBParamTswTCM are specified in this MIB as OBJECT- IDENTITYs; additional values may be further specified in other MIBs.
.1.3.6.1.2.1.97.1.4.2.1.3,DIFFSERV-MIB::diffServTBParamRate,Unsigned32,read-create,,current,,The token-bucket rate, in kilobits per second (kbps). This attribute is used for: 1. CIR in RFC 2697 for srTCM 2. CIR and PIR in RFC 2698 for trTCM 3. CTR and PTR in RFC 2859 for TSWTCM 4. AverageRate in RFC 3290.
.1.3.6.1.2.1.97.1.4.2.1.4,DIFFSERV-MIB::diffServTBParamBurstSize,INTEGER,read-create,,current,,The maximum number of bytes in a single transmission burst. This attribute is used for: 1. CBS and EBS in RFC 2697 for srTCM 2. CBS and PBS in RFC 2698 for trTCM 3. Burst Size in RFC 3290.
.1.3.6.1.2.1.97.1.4.2.1.5,DIFFSERV-MIB::diffServTBParamInterval,Unsigned32,read-create,,current,,The time interval used with the token bucket. For: 1. Average Rate Meter, the Informal Differentiated Services Model section 5.2.1, - Delta. 2. Simple Token Bucket Meter, the Informal Differentiated Services Model section 5.1, - time interval t. 3. RFC 2859 TSWTCM, - AVG_INTERVAL. 4. RFC 2697 srTCM, RFC 2698 trTCM, - token bucket update time interval.
.1.3.6.1.2.1.97.1.4.2.1.6,DIFFSERV-MIB::diffServTBParamStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.4.2.1.7,DIFFSERV-MIB::diffServTBParamStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.5,DIFFSERV-MIB::diffServAction,,,,,,
.1.3.6.1.2.1.97.1.5.1,DIFFSERV-MIB::diffServActionNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServActionId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.5.2,DIFFSERV-MIB::diffServActionTable,,not-accessible,,current,,The Action Table enumerates actions that can be performed to a stream of traffic. Multiple actions can be concatenated. For example, traffic exiting from a meter may be counted, marked, and potentially dropped before entering a queue. Specific actions are indicated by diffServActionSpecific which points to an entry of a specific action type parameterizing the action in detail.
.1.3.6.1.2.1.97.1.5.2.1,DIFFSERV-MIB::diffServActionEntry,,not-accessible,diffServActionId,current,,Each entry in the action table allows description of one specific action to be applied to traffic.
.1.3.6.1.2.1.97.1.5.2.1.1,DIFFSERV-MIB::diffServActionId,Unsigned32,not-accessible,,current,,An index that enumerates the Action entries. Managers obtain new values for row creation in this table by reading diffServActionNextFree.
.1.3.6.1.2.1.97.1.5.2.1.2,DIFFSERV-MIB::diffServActionInterface,Integer32,read-create,,current,,The interface index (value of ifIndex) that this action occurs on. This may be derived from the diffServDataPathStartEntry's index by extension through the various RowPointers. However, as this may be difficult for a network management station, it is placed here as well. If this is indeterminate, the value is zero. This is of especial relevance when reporting the counters which may apply to traffic crossing an interface: diffServCountActOctets, diffServCountActPkts, diffServAlgDropOctets, diffServAlgDropPkts, diffServAlgRandomDropOctets, and diffServAlgRandomDropPkts. It is also especially relevant to the queue and scheduler which may be subsequently applied.
.1.3.6.1.2.1.97.1.5.2.1.3,DIFFSERV-MIB::diffServActionNext,OBJECT,read-create,,current,,This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.5.2.1.4,DIFFSERV-MIB::diffServActionSpecific,OBJECT,read-create,,current,,A pointer to an object instance providing additional information for the type of action indicated by this action table entry. For the standard actions defined by this MIB module, this should point to either a diffServDscpMarkActEntry or a diffServCountActEntry. For other actions, it may point to an object instance defined in some other MIB. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the Meter should be treated as if it were not present. This may lead to incorrect policy behavior.
.1.3.6.1.2.1.97.1.5.2.1.5,DIFFSERV-MIB::diffServActionStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.5.2.1.6,DIFFSERV-MIB::diffServActionStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.5.3,DIFFSERV-MIB::diffServDscpMarkActTable,,not-accessible,,current,,This table enumerates specific DSCPs used for marking or remarking the DSCP field of IP packets. The entries of this table may be referenced by a diffServActionSpecific attribute.
.1.3.6.1.2.1.97.1.5.3.1,DIFFSERV-MIB::diffServDscpMarkActEntry,,not-accessible,diffServDscpMarkActDscp,current,,An entry in the DSCP mark action table that describes a single DSCP used for marking.
.1.3.6.1.2.1.97.1.5.3.1.1,DIFFSERV-MIB::diffServDscpMarkActDscp,Integer32,read-only,,current,,The DSCP that this Action will store into the DSCP field of the subject. It is quite possible that the only packets subject to this Action are already marked with this DSCP. Note also that Differentiated Services processing may result in packet being marked on both ingress to a network and on egress from it, and that ingress and egress can occur in the same router.
.1.3.6.1.2.1.97.1.5.4,DIFFSERV-MIB::diffServCountActNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServCountActId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.5.5,DIFFSERV-MIB::diffServCountActTable,,not-accessible,,current,,This table contains counters for all the traffic passing through an action element.
.1.3.6.1.2.1.97.1.5.5.1,DIFFSERV-MIB::diffServCountActEntry,,not-accessible,diffServCountActId,current,,An entry in the count action table describes a single set of traffic counters.
.1.3.6.1.2.1.97.1.5.5.1.1,DIFFSERV-MIB::diffServCountActId,Unsigned32,not-accessible,,current,,An index that enumerates the Count Action entries. Managers obtain new values for row creation in this table by reading diffServCountActNextFree.
.1.3.6.1.2.1.97.1.5.5.1.2,DIFFSERV-MIB::diffServCountActOctets,Counter64,read-only,,current,,The number of octets at the Action data path element. Discontinuities in the value of this counter can occur at re- initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface.
.1.3.6.1.2.1.97.1.5.5.1.3,DIFFSERV-MIB::diffServCountActPkts,Counter64,read-only,,current,,The number of packets at the Action data path element. Discontinuities in the value of this counter can occur at re- initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface.
.1.3.6.1.2.1.97.1.5.5.1.4,DIFFSERV-MIB::diffServCountActStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.5.5.1.5,DIFFSERV-MIB::diffServCountActStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.6,DIFFSERV-MIB::diffServAlgDrop,,,,,,
.1.3.6.1.2.1.97.1.6.1,DIFFSERV-MIB::diffServAlgDropNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServAlgDropId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.6.2,DIFFSERV-MIB::diffServAlgDropTable,,not-accessible,,current,,The algorithmic drop table contains entries describing an element that drops packets according to some algorithm.
.1.3.6.1.2.1.97.1.6.2.1,DIFFSERV-MIB::diffServAlgDropEntry,,not-accessible,diffServAlgDropId,current,,An entry describes a process that drops packets according to some algorithm. Further details of the algorithm type are to be found in diffServAlgDropType and with more detail parameter entry pointed to by diffServAlgDropSpecific when necessary.
.1.3.6.1.2.1.97.1.6.2.1.1,DIFFSERV-MIB::diffServAlgDropId,Unsigned32,not-accessible,,current,,An index that enumerates the Algorithmic Dropper entries. Managers obtain new values for row creation in this table by reading diffServAlgDropNextFree.
.1.3.6.1.2.1.97.1.6.2.1.2,DIFFSERV-MIB::diffServAlgDropType,INTEGER,read-create,,current,other(1):tailDrop(2):headDrop(3):randomDrop(4):alwaysDrop(5),The type of algorithm used by this dropper. The value other(1) requires further specification in some other MIB module. In the tailDrop(2) algorithm, diffServAlgDropQThreshold represents the maximum depth of the queue, pointed to by diffServAlgDropQMeasure, beyond which all newly arriving packets will be dropped. In the headDrop(3) algorithm, if a packet arrives when the current depth of the queue, pointed to by diffServAlgDropQMeasure, is at diffServAlgDropQThreshold, packets currently at the head of the queue are dropped to make room for the new packet to be enqueued at the tail of the queue. In the randomDrop(4) algorithm, on packet arrival, an Active Queue Management algorithm is executed which may randomly drop a packet. This algorithm may be proprietary, and it may drop either the arriving packet or another packet in the queue. diffServAlgDropSpecific points to a diffServRandomDropEntry that describes the algorithm. For this algorithm, diffServAlgDropQThreshold is understood to be the absolute maximum size of the queue and additional parameters are described in diffServRandomDropTable. The alwaysDrop(5) algorithm is as its name specifies; always drop. In this case, the other configuration values in this Entry are not meaningful; There is no useful 'next' processing step, there is no queue, and parameters describing the queue are not useful. Therefore, diffServAlgDropNext, diffServAlgDropMeasure, and diffServAlgDropSpecific are all zeroDotZero.
.1.3.6.1.2.1.97.1.6.2.1.3,DIFFSERV-MIB::diffServAlgDropNext,OBJECT,read-create,,current,,This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServQEntry A value of zeroDotZero in this attribute indicates no further Differentiated Services treatment is performed on traffic of this data path. The use of zeroDotZero is the normal usage for the last functional data path element of the current data path. When diffServAlgDropType is alwaysDrop(5), this object is ignored. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.6.2.1.4,DIFFSERV-MIB::diffServAlgDropQMeasure,OBJECT,read-create,,current,,Points to an entry in the diffServQTable to indicate the queue that a drop algorithm is to monitor when deciding whether to drop a packet. If the row pointed to does not exist, the algorithmic dropper element is considered inactive. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.6.2.1.5,DIFFSERV-MIB::diffServAlgDropQThreshold,Unsigned32,read-create,,current,,A threshold on the depth in bytes of the queue being measured at which a trigger is generated to the dropping algorithm, unless diffServAlgDropType is alwaysDrop(5) where this object is ignored. For the tailDrop(2) or headDrop(3) algorithms, this represents the depth of the queue, pointed to by diffServAlgDropQMeasure, at which the drop action will take place. Other algorithms will need to define their own semantics for this threshold.
.1.3.6.1.2.1.97.1.6.2.1.6,DIFFSERV-MIB::diffServAlgDropSpecific,OBJECT,read-create,,current,,Points to a table entry that provides further detail regarding a drop algorithm. Entries with diffServAlgDropType equal to other(1) may have this point to a table defined in another MIB module. Entries with diffServAlgDropType equal to randomDrop(4) must have this point to an entry in diffServRandomDropTable. For all other algorithms specified in this MIB, this should take the value zeroDotZero. The diffServAlgDropType is authoritative for the type of the drop algorithm and the specific parameters for the drop algorithm needs to be evaluated based on the diffServAlgDropType. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.6.2.1.7,DIFFSERV-MIB::diffServAlgDropOctets,Counter64,read-only,,current,,The number of octets that have been deterministically dropped by this drop process. Discontinuities in the value of this counter can occur at re- initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface.
.1.3.6.1.2.1.97.1.6.2.1.8,DIFFSERV-MIB::diffServAlgDropPkts,Counter64,read-only,,current,,The number of packets that have been deterministically dropped by this drop process. Discontinuities in the value of this counter can occur at re- initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface.
.1.3.6.1.2.1.97.1.6.2.1.9,DIFFSERV-MIB::diffServAlgRandomDropOctets,Counter64,read-only,,current,,The number of octets that have been randomly dropped by this drop process. This counter applies, therefore, only to random droppers. Discontinuities in the value of this counter can occur at re- initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface.
.1.3.6.1.2.1.97.1.6.2.1.10,DIFFSERV-MIB::diffServAlgRandomDropPkts,Counter64,read-only,,current,,The number of packets that have been randomly dropped by this drop process. This counter applies, therefore, only to random droppers. Discontinuities in the value of this counter can occur at re- initialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface.
.1.3.6.1.2.1.97.1.6.2.1.11,DIFFSERV-MIB::diffServAlgDropStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.6.2.1.12,DIFFSERV-MIB::diffServAlgDropStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.6.3,DIFFSERV-MIB::diffServRandomDropNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServRandomDropId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.6.4,DIFFSERV-MIB::diffServRandomDropTable,,not-accessible,,current,,The random drop table contains entries describing a process that drops packets randomly. Entries in this table are pointed to by diffServAlgDropSpecific.
.1.3.6.1.2.1.97.1.6.4.1,DIFFSERV-MIB::diffServRandomDropEntry,,not-accessible,diffServRandomDropId,current,,An entry describes a process that drops packets according to a random algorithm.
.1.3.6.1.2.1.97.1.6.4.1.1,DIFFSERV-MIB::diffServRandomDropId,Unsigned32,not-accessible,,current,,An index that enumerates the Random Drop entries. Managers obtain new values for row creation in this table by reading diffServRandomDropNextFree.
.1.3.6.1.2.1.97.1.6.4.1.2,DIFFSERV-MIB::diffServRandomDropMinThreshBytes,Unsigned32,read-create,,current,,The average queue depth in bytes, beyond which traffic has a non-zero probability of being dropped. Changes in this variable may or may not be reflected in the reported value of diffServRandomDropMinThreshPkts.
.1.3.6.1.2.1.97.1.6.4.1.3,DIFFSERV-MIB::diffServRandomDropMinThreshPkts,Unsigned32,read-create,,current,,The average queue depth in packets, beyond which traffic has a non-zero probability of being dropped. Changes in this variable may or may not be reflected in the reported value of diffServRandomDropMinThreshBytes.
.1.3.6.1.2.1.97.1.6.4.1.4,DIFFSERV-MIB::diffServRandomDropMaxThreshBytes,Unsigned32,read-create,,current,,The average queue depth beyond which traffic has a probability indicated by diffServRandomDropProbMax of being dropped or marked. Note that this differs from the physical queue limit, which is stored in diffServAlgDropQThreshold. Changes in this variable may or may not be reflected in the reported value of diffServRandomDropMaxThreshPkts.
.1.3.6.1.2.1.97.1.6.4.1.5,DIFFSERV-MIB::diffServRandomDropMaxThreshPkts,Unsigned32,read-create,,current,,The average queue depth beyond which traffic has a probability indicated by diffServRandomDropProbMax of being dropped or marked. Note that this differs from the physical queue limit, which is stored in diffServAlgDropQThreshold. Changes in this variable may or may not be reflected in the reported value of diffServRandomDropMaxThreshBytes.
.1.3.6.1.2.1.97.1.6.4.1.6,DIFFSERV-MIB::diffServRandomDropProbMax,Unsigned32,read-create,,current,,The worst case random drop probability, expressed in drops per thousand packets. For example, if in the worst case every arriving packet may be dropped (100%) for a period, this has the value 1000. Alternatively, if in the worst case only one percent (1%) of traffic may be dropped, it has the value 10.
.1.3.6.1.2.1.97.1.6.4.1.7,DIFFSERV-MIB::diffServRandomDropWeight,Unsigned32,read-create,,current,,The weighting of past history in affecting the Exponentially Weighted Moving Average function that calculates the current average queue depth. The equation uses diffServRandomDropWeight/65536 as the coefficient for the new sample in the equation, and (65536 - diffServRandomDropWeight)/65536 as the coefficient of the old value. Implementations may limit the values of diffServRandomDropWeight to a subset of the possible range of values, such as powers of two. Doing this would facilitate implementation of the Exponentially Weighted Moving Average using shift instructions or registers.
.1.3.6.1.2.1.97.1.6.4.1.8,DIFFSERV-MIB::diffServRandomDropSamplingRate,Unsigned32,read-create,,current,,The number of times per second the queue is sampled for queue average calculation. A value of zero is used to mean that the queue is sampled approximately each time a packet is enqueued (or dequeued).
.1.3.6.1.2.1.97.1.6.4.1.9,DIFFSERV-MIB::diffServRandomDropStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.6.4.1.10,DIFFSERV-MIB::diffServRandomDropStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.7,DIFFSERV-MIB::diffServQueue,,,,,,
.1.3.6.1.2.1.97.1.7.1,DIFFSERV-MIB::diffServQNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServQId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.7.2,DIFFSERV-MIB::diffServQTable,,not-accessible,,current,,The Queue Table enumerates the individual queues. Note that the MIB models queuing systems as composed of individual queues, one per class of traffic, even though they may in fact be structured as classes of traffic scheduled using a common calendar queue, or in other ways.
.1.3.6.1.2.1.97.1.7.2.1,DIFFSERV-MIB::diffServQEntry,,not-accessible,diffServQId,current,,An entry in the Queue Table describes a single queue or class of traffic.
.1.3.6.1.2.1.97.1.7.2.1.1,DIFFSERV-MIB::diffServQId,Unsigned32,not-accessible,,current,,An index that enumerates the Queue entries. Managers obtain new values for row creation in this table by reading diffServQNextFree.
.1.3.6.1.2.1.97.1.7.2.1.2,DIFFSERV-MIB::diffServQNext,OBJECT,read-create,,current,,This selects the next Differentiated Services Scheduler. The RowPointer must point to a diffServSchedulerEntry. A value of zeroDotZero in this attribute indicates an incomplete diffServQEntry instance. In such a case, the entry has no operational effect, since it has no parameters to give it meaning. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.7.2.1.3,DIFFSERV-MIB::diffServQMinRate,OBJECT,read-create,,current,,This RowPointer indicates the diffServMinRateEntry that the scheduler, pointed to by diffServQNext, should use to service this queue. If the row pointed to is zeroDotZero, the minimum rate and priority is unspecified. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.7.2.1.4,DIFFSERV-MIB::diffServQMaxRate,OBJECT,read-create,,current,,This RowPointer indicates the diffServMaxRateEntry that the scheduler, pointed to by diffServQNext, should use to service this queue. If the row pointed to is zeroDotZero, the maximum rate is the line speed of the interface. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.7.2.1.5,DIFFSERV-MIB::diffServQStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.7.2.1.6,DIFFSERV-MIB::diffServQStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.8,DIFFSERV-MIB::diffServScheduler,,,,,,
.1.3.6.1.2.1.97.1.8.1,DIFFSERV-MIB::diffServSchedulerNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServSchedulerId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.8.2,DIFFSERV-MIB::diffServSchedulerTable,,not-accessible,,current,,The Scheduler Table enumerates packet schedulers. Multiple scheduling algorithms can be used on a given data path, with each algorithm described by one diffServSchedulerEntry.
.1.3.6.1.2.1.97.1.8.2.1,DIFFSERV-MIB::diffServSchedulerEntry,,not-accessible,diffServSchedulerId,current,,An entry in the Scheduler Table describing a single instance of a scheduling algorithm.
.1.3.6.1.2.1.97.1.8.2.1.1,DIFFSERV-MIB::diffServSchedulerId,Unsigned32,not-accessible,,current,,An index that enumerates the Scheduler entries. Managers obtain new values for row creation in this table by reading diffServSchedulerNextFree.
.1.3.6.1.2.1.97.1.8.2.1.2,DIFFSERV-MIB::diffServSchedulerNext,OBJECT,read-create,,current,,This selects the next Differentiated Services Functional Data Path Element to handle traffic for this data path. This normally is null (zeroDotZero), or points to a diffServSchedulerEntry or a diffServQEntry. However, this RowPointer may also point to an instance of: diffServClfrEntry, diffServMeterEntry, diffServActionEntry, diffServAlgDropEntry. It would point another diffServSchedulerEntry when implementing multiple scheduler methods for the same data path, such as having one set of queues scheduled by WRR and that group participating in a priority scheduling system in which other queues compete with it in that way. It might also point to a second scheduler in a hierarchical scheduling system. If the row pointed to is zeroDotZero, no further Differentiated Services treatment is performed on traffic of this data path. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.8.2.1.3,DIFFSERV-MIB::diffServSchedulerMethod,OBJECT,read-create,,current,,The scheduling algorithm used by this Scheduler. zeroDotZero indicates that this is unknown. Standard values for generic algorithms: diffServSchedulerPriority, diffServSchedulerWRR, and diffServSchedulerWFQ are specified in this MIB; additional values may be further specified in other MIBs.
.1.3.6.1.2.1.97.1.8.2.1.4,DIFFSERV-MIB::diffServSchedulerMinRate,OBJECT,read-create,,current,,This RowPointer indicates the entry in diffServMinRateTable which indicates the priority or minimum output rate from this scheduler. This attribute is used only when there is more than one level of scheduler. When it has the value zeroDotZero, it indicates that no minimum rate or priority is imposed. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.8.2.1.5,DIFFSERV-MIB::diffServSchedulerMaxRate,OBJECT,read-create,,current,,This RowPointer indicates the entry in diffServMaxRateTable which indicates the maximum output rate from this scheduler. When more than one maximum rate applies (eg, when a multi-rate shaper is in view), it points to the first of those rate entries. This attribute is used only when there is more than one level of scheduler. When it has the value zeroDotZero, it indicates that no maximum rate is imposed. Setting this to point to a target that does not exist results in an inconsistentValue error. If the row pointed to is removed or becomes inactive by other means, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.97.1.8.2.1.6,DIFFSERV-MIB::diffServSchedulerStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.8.2.1.7,DIFFSERV-MIB::diffServSchedulerStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.8.3,DIFFSERV-MIB::diffServMinRateNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServMinRateId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.8.4,DIFFSERV-MIB::diffServMinRateTable,,not-accessible,,current,,The Minimum Rate Parameters Table enumerates individual sets of scheduling parameter that can be used/reused by Queues and Schedulers.
.1.3.6.1.2.1.97.1.8.4.1,DIFFSERV-MIB::diffServMinRateEntry,,not-accessible,diffServMinRateId,current,,An entry in the Minimum Rate Parameters Table describes a single set of scheduling parameters for use by one or more queues or schedulers.
.1.3.6.1.2.1.97.1.8.4.1.1,DIFFSERV-MIB::diffServMinRateId,Unsigned32,not-accessible,,current,,An index that enumerates the Scheduler Parameter entries. Managers obtain new values for row creation in this table by reading diffServMinRateNextFree.
.1.3.6.1.2.1.97.1.8.4.1.2,DIFFSERV-MIB::diffServMinRatePriority,Unsigned32,read-create,,current,,The priority of this input to the associated scheduler, relative to the scheduler's other inputs. A queue or scheduler with a larger numeric value will be served before another with a smaller numeric value.
.1.3.6.1.2.1.97.1.8.4.1.3,DIFFSERV-MIB::diffServMinRateAbsolute,Unsigned32,read-create,,current,,The minimum absolute rate, in kilobits/sec, that a downstream scheduler element should allocate to this queue. If the value is zero, then there is effectively no minimum rate guarantee. If the value is non-zero, the scheduler will assure the servicing of this queue to at least this rate. Note that this attribute value and that of diffServMinRateRelative are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other: diffServMinRateRelative = (diffServMinRateAbsolute*1000000)/ifSpeed or, if appropriate: diffServMinRateRelative = diffServMinRateAbsolute/ifHighSpeed
.1.3.6.1.2.1.97.1.8.4.1.4,DIFFSERV-MIB::diffServMinRateRelative,Unsigned32,read-create,,current,,The minimum rate that a downstream scheduler element should allocate to this queue, relative to the maximum rate of the interface as reported by ifSpeed or ifHighSpeed, in units of 1/1000 of 1. If the value is zero, then there is effectively no minimum rate guarantee. If the value is non-zero, the scheduler will assure the servicing of this queue to at least this rate. Note that this attribute value and that of diffServMinRateAbsolute are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other: diffServMinRateRelative = (diffServMinRateAbsolute*1000000)/ifSpeed or, if appropriate: diffServMinRateRelative = diffServMinRateAbsolute/ifHighSpeed
.1.3.6.1.2.1.97.1.8.4.1.5,DIFFSERV-MIB::diffServMinRateStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.8.4.1.6,DIFFSERV-MIB::diffServMinRateStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.1.8.5,DIFFSERV-MIB::diffServMaxRateNextFree,Unsigned32,read-only,,current,,This object contains an unused value for diffServMaxRateId, or a zero to indicate that none exist.
.1.3.6.1.2.1.97.1.8.6,DIFFSERV-MIB::diffServMaxRateTable,,not-accessible,,current,,The Maximum Rate Parameter Table enumerates individual sets of scheduling parameter that can be used/reused by Queues and Schedulers.
.1.3.6.1.2.1.97.1.8.6.1,DIFFSERV-MIB::diffServMaxRateEntry,,not-accessible,diffServMaxRateId:diffServMaxRateLevel,current,,An entry in the Maximum Rate Parameter Table describes a single set of scheduling parameters for use by one or more queues or schedulers.
.1.3.6.1.2.1.97.1.8.6.1.1,DIFFSERV-MIB::diffServMaxRateId,Unsigned32,not-accessible,,current,,An index that enumerates the Maximum Rate Parameter entries. Managers obtain new values for row creation in this table by reading diffServMaxRateNextFree.
.1.3.6.1.2.1.97.1.8.6.1.2,DIFFSERV-MIB::diffServMaxRateLevel,Unsigned32,not-accessible,,current,,An index that indicates which level of a multi-rate shaper is being given its parameters. A multi-rate shaper has some number of rate levels. Frame Relay's dual rate specification refers to a 'committed' and an 'excess' rate; ATM's dual rate specification refers to a 'mean' and a 'peak' rate. This table is generalized to support an arbitrary number of rates. The committed or mean rate is level 1, the peak rate (if any) is the highest level rate configured, and if there are other rates they are distributed in monotonically increasing order between them.
.1.3.6.1.2.1.97.1.8.6.1.3,DIFFSERV-MIB::diffServMaxRateAbsolute,Unsigned32,read-create,,current,,The maximum rate in kilobits/sec that a downstream scheduler element should allocate to this queue. If the value is zero, then there is effectively no maximum rate limit and that the scheduler should attempt to be work conserving for this queue. If the value is non-zero, the scheduler will limit the servicing of this queue to, at most, this rate in a non-work-conserving manner. Note that this attribute value and that of diffServMaxRateRelative are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other: diffServMaxRateRelative = (diffServMaxRateAbsolute*1000000)/ifSpeed or, if appropriate: diffServMaxRateRelative = diffServMaxRateAbsolute/ifHighSpeed
.1.3.6.1.2.1.97.1.8.6.1.4,DIFFSERV-MIB::diffServMaxRateRelative,Unsigned32,read-create,,current,,The maximum rate that a downstream scheduler element should allocate to this queue, relative to the maximum rate of the interface as reported by ifSpeed or ifHighSpeed, in units of 1/1000 of 1. If the value is zero, then there is effectively no maximum rate limit and the scheduler should attempt to be work conserving for this queue. If the value is non-zero, the scheduler will limit the servicing of this queue to, at most, this rate in a non-work-conserving manner. Note that this attribute value and that of diffServMaxRateAbsolute are coupled: changes to one will affect the value of the other. They are linked by the following equation, in that setting one will change the other: diffServMaxRateRelative = (diffServMaxRateAbsolute*1000000)/ifSpeed or, if appropriate: diffServMaxRateRelative = diffServMaxRateAbsolute/ifHighSpeed
.1.3.6.1.2.1.97.1.8.6.1.5,DIFFSERV-MIB::diffServMaxRateThreshold,INTEGER,read-create,,current,,The number of bytes of queue depth at which the rate of a multi-rate scheduler will increase to the next output rate. In the last conceptual row for such a shaper, this threshold is ignored and by convention is zero.
.1.3.6.1.2.1.97.1.8.6.1.6,DIFFSERV-MIB::diffServMaxRateStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.97.1.8.6.1.7,DIFFSERV-MIB::diffServMaxRateStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. All writable objects in this row may be modified at any time. Setting this variable to 'destroy' when the MIB contains one or more RowPointers pointing to it results in destruction being delayed until the row is no longer used.
.1.3.6.1.2.1.97.2,DIFFSERV-MIB::diffServMIBConformance,,,,,,
.1.3.6.1.2.1.97.2.1,DIFFSERV-MIB::diffServMIBCompliances,,,,,,
.1.3.6.1.2.1.97.2.1.1,DIFFSERV-MIB::diffServMIBFullCompliance,,,,,,When this MIB is implemented with support for read-create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB.
.1.3.6.1.2.1.97.2.1.2,DIFFSERV-MIB::diffServMIBReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-create (i.e. in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but can not be configured with this MIB.
.1.3.6.1.2.1.97.2.2,DIFFSERV-MIB::diffServMIBGroups,,,,,,
.1.3.6.1.2.1.97.2.2.1,DIFFSERV-MIB::diffServMIBDataPathGroup,,,,,,The Data Path Group defines the MIB Objects that describe a functional data path.
.1.3.6.1.2.1.97.2.2.2,DIFFSERV-MIB::diffServMIBClfrGroup,,,,,,The Classifier Group defines the MIB Objects that describe the list the starts of individual classifiers.
.1.3.6.1.2.1.97.2.2.3,DIFFSERV-MIB::diffServMIBClfrElementGroup,,,,,,The Classifier Element Group defines the MIB Objects that describe the classifier elements that make up a generic classifier.
.1.3.6.1.2.1.97.2.2.4,DIFFSERV-MIB::diffServMIBMultiFieldClfrGroup,,,,,,The Multi-field Classifier Group defines the MIB Objects that describe a classifier element for matching on various fields of an IP and upper-layer protocol header.
.1.3.6.1.2.1.97.2.2.5,DIFFSERV-MIB::diffServMIBMeterGroup,,,,,,The Meter Group defines the objects used in describing a generic meter element.
.1.3.6.1.2.1.97.2.2.6,DIFFSERV-MIB::diffServMIBTBParamGroup,,,,,,The Token-Bucket Meter Group defines the objects used in describing a token bucket meter element.
.1.3.6.1.2.1.97.2.2.7,DIFFSERV-MIB::diffServMIBActionGroup,,,,,,The Action Group defines the objects used in describing a generic action element.
.1.3.6.1.2.1.97.2.2.8,DIFFSERV-MIB::diffServMIBDscpMarkActGroup,,,,,,The DSCP Mark Action Group defines the objects used in describing a DSCP Marking Action element.
.1.3.6.1.2.1.97.2.2.9,DIFFSERV-MIB::diffServMIBCounterGroup,,,,,,A collection of objects providing information specific to packet-oriented network interfaces.
.1.3.6.1.2.1.97.2.2.10,DIFFSERV-MIB::diffServMIBAlgDropGroup,,,,,,The Algorithmic Drop Group contains the objects that describe algorithmic dropper operation and configuration.
.1.3.6.1.2.1.97.2.2.11,DIFFSERV-MIB::diffServMIBRandomDropGroup,,,,,,The Random Drop Group augments the Algorithmic Drop Group for random dropper operation and configuration.
.1.3.6.1.2.1.97.2.2.12,DIFFSERV-MIB::diffServMIBQGroup,,,,,,The Queue Group contains the objects that describe an interface's queues.
.1.3.6.1.2.1.97.2.2.13,DIFFSERV-MIB::diffServMIBSchedulerGroup,,,,,,The Scheduler Group contains the objects that describe packet schedulers on interfaces.
.1.3.6.1.2.1.97.2.2.14,DIFFSERV-MIB::diffServMIBMinRateGroup,,,,,,The Minimum Rate Parameter Group contains the objects that describe packet schedulers' minimum rate or priority guarantees.
.1.3.6.1.2.1.97.2.2.15,DIFFSERV-MIB::diffServMIBMaxRateGroup,,,,,,The Maximum Rate Parameter Group contains the objects that describe packet schedulers' maximum rate guarantees.
.1.3.6.1.2.1.97.3,DIFFSERV-MIB::diffServMIBAdmin,,,,,,
.1.3.6.1.2.1.97.3.1,DIFFSERV-MIB::diffServTBMeters,,,,,,
.1.3.6.1.2.1.97.3.1.1,DIFFSERV-MIB::diffServTBParamSimpleTokenBucket,,,,,,Two Parameter Token Bucket Meter as described in the Informal Differentiated Services Model section 5.2.3.
.1.3.6.1.2.1.97.3.1.2,DIFFSERV-MIB::diffServTBParamAvgRate,,,,,,Average Rate Meter as described in the Informal Differentiated Services Model section 5.2.1.
.1.3.6.1.2.1.97.3.1.3,DIFFSERV-MIB::diffServTBParamSrTCMBlind,,,,,,Single Rate Three Color Marker Metering as defined by RFC 2697, in the `Color Blind' mode as described by the RFC.
.1.3.6.1.2.1.97.3.1.4,DIFFSERV-MIB::diffServTBParamSrTCMAware,,,,,,Single Rate Three Color Marker Metering as defined by RFC 2697, in the `Color Aware' mode as described by the RFC.
.1.3.6.1.2.1.97.3.1.5,DIFFSERV-MIB::diffServTBParamTrTCMBlind,,,,,,Two Rate Three Color Marker Metering as defined by RFC 2698, in the `Color Blind' mode as described by the RFC.
.1.3.6.1.2.1.97.3.1.6,DIFFSERV-MIB::diffServTBParamTrTCMAware,,,,,,Two Rate Three Color Marker Metering as defined by RFC 2698, in the `Color Aware' mode as described by the RFC.
.1.3.6.1.2.1.97.3.1.7,DIFFSERV-MIB::diffServTBParamTswTCM,,,,,,Time Sliding Window Three Color Marker Metering as defined by RFC 2859.
.1.3.6.1.2.1.97.3.2,DIFFSERV-MIB::diffServSchedulers,,,,,,
.1.3.6.1.2.1.97.3.2.1,DIFFSERV-MIB::diffServSchedulerPriority,,,,,,For use with diffServSchedulerMethod to indicate the Priority scheduling method. This is defined as an algorithm in which the presence of data in a queue or set of queues absolutely precludes dequeue from another queue or set of queues of lower priority. Note that attributes from diffServMinRateEntry of the queues/schedulers feeding this scheduler are used when determining the next packet to schedule.
.1.3.6.1.2.1.97.3.2.2,DIFFSERV-MIB::diffServSchedulerWRR,,,,,,For use with diffServSchedulerMethod to indicate the Weighted Round Robin scheduling method, defined as any algorithm in which a set of queues are visited in a fixed order, and varying amounts of traffic are removed from each queue in turn to implement an average output rate by class. Notice attributes from diffServMinRateEntry of the queues/schedulers feeding this scheduler are used when determining the next packet to schedule.
.1.3.6.1.2.1.97.3.2.3,DIFFSERV-MIB::diffServSchedulerWFQ,,,,,,For use with diffServSchedulerMethod to indicate the Weighted Fair Queuing scheduling method, defined as any algorithm in which a set of queues are conceptually visited in some order, to implement an average output rate by class. Notice attributes from diffServMinRateEntry of the queues/schedulers feeding this scheduler are used when determining the next packet to schedule.
.1.3.6.1.2.1.98,GSMP-MIB::gsmpMIB,,,,,,This MIB contains managed object definitions for the General Switch Management Protocol, GSMP, version 3
.1.3.6.1.2.1.98.0,GSMP-MIB::gsmpNotifications,,,,,,
.1.3.6.1.2.1.98.0.1,GSMP-MIB::gsmpSessionDown,,,,,,When it has been enabled, this notification is generated whenever a session is taken down, regardless of whether the session went down normally or not. Its purpose is to allow a management application (primarily an accounting application) that is monitoring the session statistics to receive the final values of these counters, so that the application can properly account for the amounts the counters were incremented since the last time the application polled them. The gsmpSessionStartUptime object provides the total amount of time that the session was active. This notification is not a substitute for polling the session statistic counts. In particular, the count values reported in this notification cannot be assumed to be the complete totals for the life of the session, since they may have wrapped while the session was up. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifiers of the objects contained in the notification. An instance of this notification will contain exactly one instance of each of its objects, and these objects will all belong to the same conceptual row of the gsmpSessionTable.
.1.3.6.1.2.1.98.0.2,GSMP-MIB::gsmpSessionUp,,,,,,When it has been enabled, this notification is generated when new session is established. The new session is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionFarSideInstance object contained in the notification.
.1.3.6.1.2.1.98.0.3,GSMP-MIB::gsmpSentFailureInd,,,,,,When it has been enabled, this notification is generated when a message with a failure indication was sent. The notification indicates a change in the value of gsmpSessionStatFailureInds. The gsmpSessionLastFailureCode contains the failure reason. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifiers of the objects contained in the notification.
.1.3.6.1.2.1.98.0.4,GSMP-MIB::gsmpReceivedFailureInd,,,,,,When it has been enabled, this notification is generate when a message with a failure indication is received. The notification indicates a change in the value of gsmpSessionStatReceivedFailures. The gsmpSessionLastFailureCode contains the failure reason. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifiers of the objects contained in the notification.
.1.3.6.1.2.1.98.0.5,GSMP-MIB::gsmpPortUpEvent,,,,,,When it has been enabled, this notification is generated when a Port Up Event occurs. The notification indicates a change in the value of gsmpSessionStatPortUpEvents. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionStatPortUpEvents object contained in the notification.
.1.3.6.1.2.1.98.0.6,GSMP-MIB::gsmpPortDownEvent,,,,,,When it has been enabled, this notification is generated when a Port Down Event occurs. The notification indicates a change in the value of gsmpSessionStatPortDownEvents. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionStatPortDownEvents object contained in the notification.
.1.3.6.1.2.1.98.0.7,GSMP-MIB::gsmpInvalidLabelEvent,,,,,,When it has been enabled, this notification is generated when an Invalid Label Event occurs. The notification indicates a change in the value of gsmpSessionStatInvLabelEvents. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionStatInvLabelEvents object contained in the notification.
.1.3.6.1.2.1.98.0.8,GSMP-MIB::gsmpNewPortEvent,,,,,,When it has been enabled, this notification is generated when a New Port Event occurs. The notification indicates a change in the value of gsmpSessionStatNewPortEvents. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionStatNewPortEvents object contained in the notification.
.1.3.6.1.2.1.98.0.9,GSMP-MIB::gsmpDeadPortEvent,,,,,,When it has been enabled, this notification is generated when a Dead Port Event occurs. The notification indicates a change in the value of gsmpSessionStatDeadPortEvents. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionStatDeadPortEvents object contained in the notification.
.1.3.6.1.2.1.98.0.10,GSMP-MIB::gsmpAdjacencyUpdateEvent,,,,,,When it has been enabled, this notification is generated when an Adjacency Update Event occurs. The gsmpSessionAdjacencyCount contains the new value of the number of adjacencies that are established with controllers and the switch partition that is used for this session. The notification indicates a change in the value of gsmpSessionStatAdjUpdateEvents. The session to which this notification applies is identified by the gsmpSessionThisSideId and gsmpSessionFarSideId which could be inferred from the Object Identifier of the gsmpSessionAdjacencyCount or the gsmpSessionStatAdjUpdateEvents object contained in the notification.
.1.3.6.1.2.1.98.1,GSMP-MIB::gsmpObjects,,,,,,
.1.3.6.1.2.1.98.1.1,GSMP-MIB::gsmpControllerTable,,not-accessible,,current,,This table represents the Switch Controller Entities. An entry in this table needs to be configured (created) before a GSMP session might be started.
.1.3.6.1.2.1.98.1.1.1,GSMP-MIB::gsmpControllerEntry,,not-accessible,gsmpControllerEntityId,current,,An entry in the table showing the data for a specific Switch Controller Entity. If partitions are used, one entity corresponds to one specific switch partition. Depending of the encapsulation used, a corresponding row in the gsmpAtmEncapTable or the gsmpTcpIpEncapTable may have been created.
.1.3.6.1.2.1.98.1.1.1.1,GSMP-MIB::gsmpControllerEntityId,OCTET,not-accessible,,current,,The Switch Controller Entity Id is unique within the operational context of the device.
.1.3.6.1.2.1.98.1.1.1.2,GSMP-MIB::gsmpControllerMaxVersion,Unsigned32,read-create,,current,,The max version number of the GSMP protocol being used in this session. The version is negotiated by the adjacency protocol.
.1.3.6.1.2.1.98.1.1.1.3,GSMP-MIB::gsmpControllerTimer,Unsigned32,read-create,,current,,The timer specifies the nominal time between periodic adjacency protocol messages. It is a constant for the duration of a GSMP session. The timer is specified in units of 100ms.
.1.3.6.1.2.1.98.1.1.1.4,GSMP-MIB::gsmpControllerPort,Unsigned32,read-create,,current,,The local port number for the Switch Controller Entity.
.1.3.6.1.2.1.98.1.1.1.5,GSMP-MIB::gsmpControllerInstance,Unsigned32,read-only,,current,,The instance number for the Switch Controller Entity. The Instance number is a 24-bit number that should be guaranteed to be unique within the recent past and to change when the link or node comes back up after going down. Zero is not a valid instance number. 
.1.3.6.1.2.1.98.1.1.1.6,GSMP-MIB::gsmpControllerPartitionType,INTEGER,read-create,,current,noPartition(1):fixedPartitionRequest(2):fixedPartitionAssigned(3),A controller can request the specific partition identifier to the session by setting the Partition Type to fixedPartitionRequest(2). A controller can let the switch decide whether it wants to assign a fixed partition ID or not, by setting the Partition Type to noPartition(1).
.1.3.6.1.2.1.98.1.1.1.7,GSMP-MIB::gsmpControllerPartitionId,OCTET,read-create,,current,,The Id for the specific switch partition that this Switch Controller is concerned with. If partitions are not used or if the controller lets the switch assigns Partition ID, i.e Partition Type = noPartition(1), then this object is undefined.
.1.3.6.1.2.1.98.1.1.1.8,GSMP-MIB::gsmpControllerDoResync,INTEGER,read-create,,current,true(1):false(2),This object specifies whether the controller should resynchronise or reset in case of loss of synchronisation. If this object is set to true then the Controller should resync with PFLAG=2 (recovered adjacency).
.1.3.6.1.2.1.98.1.1.1.9,GSMP-MIB::gsmpControllerNotificationMap,BITS,read-create,,current,sessionDown(0):sessionUp(1):sendFailureIndication(2):receivedFailureIndication(3):portUpEvent(4):portDownEvent(5):invalidLabelEvent(6):newPortEvent(7):deadPortEvent(8):adjacencyUpdateEvent(9),This bitmap defines whether a corresponding SNMP notification should be sent if a GSMP event is received by the Switch Controller. If the bit is set to 1 a notification should be sent. The handling and filtering of the SNMP notifications are then further specified in the SNMP notification originator application. 
.1.3.6.1.2.1.98.1.1.1.10,GSMP-MIB::gsmpControllerSessionState,INTEGER,read-only,,current,null(1):synsent(2):synrcvd(3):estab(4),The state for the existing or potential session that this entity is concerned with. The NULL state is returned if the proper encapsulation data is not yet configured, if the row is not in active status or if the session is in NULL state as defined in the GSMP specification.
.1.3.6.1.2.1.98.1.1.1.11,GSMP-MIB::gsmpControllerStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this controller entity. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.98.1.1.1.12,GSMP-MIB::gsmpControllerRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention. While the row is in active state it's not possible to modify the value of any object for that row except the gsmpControllerNotificationMap and the gsmpControllerRowStatus objects.
.1.3.6.1.2.1.98.1.2,GSMP-MIB::gsmpSwitchTable,,not-accessible,,current,,This table represents the Switch Entities. An entry in this table needs to be configured (created) before a GSMP session might be started.
.1.3.6.1.2.1.98.1.2.1,GSMP-MIB::gsmpSwitchEntry,,not-accessible,gsmpSwitchEntityId,current,,An entry in the table showing the data for a specific Switch Entity. If partitions are used, one entity corresponds to one specific switch partition. Depending of the encapsulation used, a corresponding row in the gsmpAtmEncapTable or the gsmpTcpIpEncapTable may have been created.
.1.3.6.1.2.1.98.1.2.1.1,GSMP-MIB::gsmpSwitchEntityId,OCTET,not-accessible,,current,,The Switch Entity Id is unique within the operational context of the device. 
.1.3.6.1.2.1.98.1.2.1.2,GSMP-MIB::gsmpSwitchMaxVersion,Unsigned32,read-create,,current,,The max version number of the GSMP protocol being supported by this Switch. The version is negotiated by the adjacency protocol.
.1.3.6.1.2.1.98.1.2.1.3,GSMP-MIB::gsmpSwitchTimer,Unsigned32,read-create,,current,,The timer specifies the nominal time between periodic adjacency protocol messages. It is a constant for the duration of a GSMP session. The timer is specified in units of 100ms.
.1.3.6.1.2.1.98.1.2.1.4,GSMP-MIB::gsmpSwitchName,OCTET,read-create,,current,,The name of the Switch. The first three octets must be an Organisationally Unique Identifier (OUI) that identifies the manufacturer of the Switch. This is by default set to the same value as the gsmpSwitchId object if not separately specified. 
.1.3.6.1.2.1.98.1.2.1.5,GSMP-MIB::gsmpSwitchPort,Unsigned32,read-create,,current,,The local port number for this Switch Entity.
.1.3.6.1.2.1.98.1.2.1.6,GSMP-MIB::gsmpSwitchInstance,Unsigned32,read-only,,current,,The instance number for the Switch Entity. The Instance number is a 24-bit number that should be guaranteed to be unique within the recent past and to change when the link or node comes back up after going down. Zero is not a valid instance number.
.1.3.6.1.2.1.98.1.2.1.7,GSMP-MIB::gsmpSwitchPartitionType,INTEGER,read-create,,current,noPartition(1):fixedPartitionRequest(2):fixedPartitionAssigned(3),A switch can assign the specific partition identifier to the session by setting the Partition Type to fixedPartitionAssigned(3). A switch can specify that no partitions are handled in the session by setting the Partition Type to noPartition(1).
.1.3.6.1.2.1.98.1.2.1.8,GSMP-MIB::gsmpSwitchPartitionId,OCTET,read-create,,current,,The Id for this specific switch partition that the switch entity represents. If partitions are not used, i.e. Partition Type = noPartition(1), then this object is undefined.
.1.3.6.1.2.1.98.1.2.1.9,GSMP-MIB::gsmpSwitchNotificationMap,BITS,read-create,,current,sessionDown(0):sessionUp(1):sendFailureIndication(2):receivedFailureIndication(3):portUpEvent(4):portDownEvent(5):invalidLabelEvent(6):newPortEvent(7):deadPortEvent(8):adjacencyUpdateEvent(9),This bitmap defines whether a corresponding SNMP notification should be sent if an GSMP event is sent by the Switch Entity. If the bit is set to 1 a notification should be sent. The handling and filtering of the SNMP notifications are then further specified in the SNMP notification originator application. 
.1.3.6.1.2.1.98.1.2.1.10,GSMP-MIB::gsmpSwitchSwitchType,OCTET,read-create,,current,,A 16-bit field allocated by the manufacturer of the switch. The Switch Type identifies the product. When the Switch Type is combined with the OUI from the Switch Name the product is uniquely identified. 
.1.3.6.1.2.1.98.1.2.1.11,GSMP-MIB::gsmpSwitchWindowSize,Unsigned32,read-create,,current,,The maximum number of unacknowledged request messages that may be transmitted by the controller without the possibility of loss. This field is used to prevent request messages from being lost in the switch because of overflow in the receive buffer. The field is a hint to the controller.
.1.3.6.1.2.1.98.1.2.1.12,GSMP-MIB::gsmpSwitchSessionState,INTEGER,read-only,,current,null(1):synsent(2):synrcvd(3):estab(4),The state for the existing or potential session that this entity is concerned with. The NULL state is returned if the proper encapsulation data is not yet configured, if the row is not in active status or if the session is in NULL state as defined in the GSMP specification.
.1.3.6.1.2.1.98.1.2.1.13,GSMP-MIB::gsmpSwitchStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this switch entity. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.98.1.2.1.14,GSMP-MIB::gsmpSwitchRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention. While the row is in active state it's not possible to modify the value of any object for that row except the gsmpSwitchNotificationMap and the gsmpSwitchRowStatus objects.
.1.3.6.1.2.1.98.1.3,GSMP-MIB::gsmpAtmEncapTable,,not-accessible,,current,,This table contains the atm encapsulation data for the Controller or Switch that uses atm aal5 as encapsulation. 
.1.3.6.1.2.1.98.1.3.1,GSMP-MIB::gsmpAtmEncapEntry,,not-accessible,gsmpAtmEncapEntityId,current,,An entry in the table showing the encapsulation data for a specific Switch Controller entity or Switch entity.
.1.3.6.1.2.1.98.1.3.1.1,GSMP-MIB::gsmpAtmEncapEntityId,OCTET,not-accessible,,current,,The Controller Id or Switch Id that is unique within the operational context of the device. 
.1.3.6.1.2.1.98.1.3.1.2,GSMP-MIB::gsmpAtmEncapIfIndex,Integer32,read-create,,current,,The interface index for the virtual channel over which the GSMP session is established, i.e., the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer.
.1.3.6.1.2.1.98.1.3.1.3,GSMP-MIB::gsmpAtmEncapVpi,INTEGER,read-create,,current,, The VPI value for the virtual channel over which the GSMP session is established, i.e., the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer.
.1.3.6.1.2.1.98.1.3.1.4,GSMP-MIB::gsmpAtmEncapVci,INTEGER,read-create,,current,, The VCI value for the virtual channel over which the GSMP session is established, i.e., the GSMP control channel for LLC/SNAP encapsulated GSMP messages on an ATM data link layer.
.1.3.6.1.2.1.98.1.3.1.5,GSMP-MIB::gsmpAtmEncapStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this entry. It should have the same value as the StorageType in the referring Switch Controller entity or Switch entity.
.1.3.6.1.2.1.98.1.3.1.6,GSMP-MIB::gsmpAtmEncapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention. While the row is in active state it's not possible to modify the value of any object for that row except the gsmpAtmEncapRowStatus object.
.1.3.6.1.2.1.98.1.4,GSMP-MIB::gsmpTcpIpEncapTable,,not-accessible,,current,,This table contains the encapsulation data for the Controller or Switch that uses TCP/IP as encapsulation.
.1.3.6.1.2.1.98.1.4.1,GSMP-MIB::gsmpTcpIpEncapEntry,,not-accessible,gsmpTcpIpEncapEntityId,current,,An entry in the table showing the encapsulation data for a specific Switch Controller entity or Switch entity.
.1.3.6.1.2.1.98.1.4.1.1,GSMP-MIB::gsmpTcpIpEncapEntityId,OCTET,not-accessible,,current,,The Controller or Switch Id is unique within the operational context of the device. 
.1.3.6.1.2.1.98.1.4.1.2,GSMP-MIB::gsmpTcpIpEncapAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of address in gsmpTcpIpEncapAddress.
.1.3.6.1.2.1.98.1.4.1.3,GSMP-MIB::gsmpTcpIpEncapAddress,OCTET,read-create,,current,,The IPv4 or IPv6 address used for the GSMP session peer.
.1.3.6.1.2.1.98.1.4.1.4,GSMP-MIB::gsmpTcpIpEncapPortNumber,Unsigned32,read-create,,current,,The TCP port number used for the TCP session establishment to the GSMP peer.
.1.3.6.1.2.1.98.1.4.1.5,GSMP-MIB::gsmpTcpIpEncapStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this entry. It should have the same value as the StorageType in the referring Switch Controller entity or Switch entity.
.1.3.6.1.2.1.98.1.4.1.6,GSMP-MIB::gsmpTcpIpEncapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),An object that allows entries in this table to be created and deleted using the RowStatus convention. While the row is in active state it's not possible to modify the value of any object for that row except the gsmpTcpIpEncapRowStatus object.
.1.3.6.1.2.1.98.1.5,GSMP-MIB::gsmpSessionTable,,not-accessible,,current,,This table represents the sessions between Controller and Switch pairs. 
.1.3.6.1.2.1.98.1.5.1,GSMP-MIB::gsmpSessionEntry,,not-accessible,gsmpSessionThisSideId:gsmpSessionFarSideId,current,,An entry in the table showing the session data for a specific Controller and Switch pair. Also, statistics for this specific session is shown.
.1.3.6.1.2.1.98.1.5.1.1,GSMP-MIB::gsmpSessionThisSideId,OCTET,not-accessible,,current,,This side ID uniquely identifies the entity that this session relates to within the operational context of the device. 
.1.3.6.1.2.1.98.1.5.1.2,GSMP-MIB::gsmpSessionFarSideId,OCTET,not-accessible,,current,,The Far side ID uniquely identifies the entity that this session is established against. 
.1.3.6.1.2.1.98.1.5.1.3,GSMP-MIB::gsmpSessionVersion,Unsigned32,read-only,,current,,The version number of the GSMP protocol being used in this session. The version is the result of the negotiation by the adjacency protocol.
.1.3.6.1.2.1.98.1.5.1.4,GSMP-MIB::gsmpSessionTimer,Integer32,read-only,,current,,The timer specifies the time remaining until the adjacency timer expires. The object could take negative values since if no valid GSMP messages are received in any period of time in excess of three times the value of the Timer negotiated by the adjacency protocol loss of synchronisation may be declared. The timer is specified in units of 100ms.
.1.3.6.1.2.1.98.1.5.1.5,GSMP-MIB::gsmpSessionPartitionId,OCTET,read-only,,current,,The Partition Id for the specific switch partition that this session is concerned with.
.1.3.6.1.2.1.98.1.5.1.6,GSMP-MIB::gsmpSessionAdjacencyCount,Unsigned32,read-only,,current,,This object specifies the current number of adjacencies that are established with controllers and the switch partition that is used for this session. The value includes this session.
.1.3.6.1.2.1.98.1.5.1.7,GSMP-MIB::gsmpSessionFarSideName,OCTET,read-only,,current,,The name of the far side as advertised in the adjacency message.
.1.3.6.1.2.1.98.1.5.1.8,GSMP-MIB::gsmpSessionFarSidePort,Unsigned32,read-only,,current,,The local port number of the link across which the message is being sent.
.1.3.6.1.2.1.98.1.5.1.9,GSMP-MIB::gsmpSessionFarSideInstance,Unsigned32,read-only,,current,,The instance number used for the link during this session. The Instance number is a 24-bit number that should be guaranteed to be unique within the recent past and to change when the link or node comes back up after going down. Zero is not a valid instance number.
.1.3.6.1.2.1.98.1.5.1.10,GSMP-MIB::gsmpSessionLastFailureCode,Unsigned32,read-only,,current,,This is the last failure code that was received over this session. If no failure code have been received, the value is zero.
.1.3.6.1.2.1.98.1.5.1.11,GSMP-MIB::gsmpSessionDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one or more of this session's counters suffered a discontinuity. If no such discontinuities have occurred since then, this object contains the same timestamp as gsmpSessionStartUptime .
.1.3.6.1.2.1.98.1.5.1.12,GSMP-MIB::gsmpSessionStartUptime,TimeTicks,read-only,,current,, The value of sysUpTime when the session came to established state.
.1.3.6.1.2.1.98.1.5.1.13,GSMP-MIB::gsmpSessionStatSentMessages,Gauge32,read-only,,current,,The number of messages that have been sent in this session. All GSMP messages pertaining to this session after the session came to established state SHALL be counted, also including adjacency protocol messages and failure response messages. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.14,GSMP-MIB::gsmpSessionStatFailureInds,Gauge32,read-only,,current,,The number of messages that have been sent with a failure indication in this session. Warning messages SHALL NOT be counted. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.15,GSMP-MIB::gsmpSessionStatReceivedMessages,Gauge32,read-only,,current,,The number of messages that have been received in this session. All legal GSMP messages pertaining to this session after the session came to established state SHALL be counted, also including adjacency protocol messages and failure response messages. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.16,GSMP-MIB::gsmpSessionStatReceivedFailures,Gauge32,read-only,,current,,The number of messages that have been received in this session with a failure indication. Warning messages SHALL NOT be counted. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.17,GSMP-MIB::gsmpSessionStatPortUpEvents,Gauge32,read-only,,current,,The number of Port Up events that have been sent or received on this session. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.18,GSMP-MIB::gsmpSessionStatPortDownEvents,Gauge32,read-only,,current,,The number of Port Down events that have been sent or received on this session. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.19,GSMP-MIB::gsmpSessionStatInvLabelEvents,Gauge32,read-only,,current,,The number of Invalid label events that have been sent or received on this session. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.20,GSMP-MIB::gsmpSessionStatNewPortEvents,Gauge32,read-only,,current,,The number of New Port events that have been sent or received on this session. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.21,GSMP-MIB::gsmpSessionStatDeadPortEvents,Gauge32,read-only,,current,,The number of Dead Port events that have been sent or received on this session. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.1.5.1.22,GSMP-MIB::gsmpSessionStatAdjUpdateEvents,Gauge32,read-only,,current,,The number of Adjacency Update events that have been sent or received on this session. When the counter suffers any discontinuity, then the gsmpSessionDiscontinuityTime object indicates when it happened.
.1.3.6.1.2.1.98.2,GSMP-MIB::gsmpNotificationsObjects,,,,,,
.1.3.6.1.2.1.98.2.1,GSMP-MIB::gsmpEventPort,Unsigned32,accessible-for-notify,,current,,This object specifies the Port Number that is carried in this event.
.1.3.6.1.2.1.98.2.2,GSMP-MIB::gsmpEventPortSessionNumber,Unsigned32,accessible-for-notify,,current,,This object specifies the Port Session Number that is carried in this event.
.1.3.6.1.2.1.98.2.3,GSMP-MIB::gsmpEventSequenceNumber,Unsigned32,accessible-for-notify,,current,,This object specifies the Event Sequence Number that is carried in this event.
.1.3.6.1.2.1.98.2.4,GSMP-MIB::gsmpEventLabel,OCTET,accessible-for-notify,,current,,This object specifies the Label that is carried in this event.
.1.3.6.1.2.1.98.3,GSMP-MIB::gsmpConformance,,,,,,
.1.3.6.1.2.1.98.3.1,GSMP-MIB::gsmpGroups,,,,,,
.1.3.6.1.2.1.98.3.1.1,GSMP-MIB::gsmpGeneralGroup,,,,,,Objects that apply to all GSMP implementations.
.1.3.6.1.2.1.98.3.1.2,GSMP-MIB::gsmpControllerGroup,,,,,,Objects that apply GSMP implementations of Switch Controllers.
.1.3.6.1.2.1.98.3.1.3,GSMP-MIB::gsmpSwitchGroup,,,,,,Objects that apply GSMP implementations of Switches.
.1.3.6.1.2.1.98.3.1.4,GSMP-MIB::gsmpAtmEncapGroup,,,,,,Objects that apply to GSMP implementations that supports ATM for GSMP encapsulation.
.1.3.6.1.2.1.98.3.1.5,GSMP-MIB::gsmpTcpIpEncapGroup,,,,,,Objects that apply to GSMP implementations that supports TCP/IP for GSMP encapsulation.
.1.3.6.1.2.1.98.3.1.6,GSMP-MIB::gsmpNotificationObjectsGroup,,,,,,Objects that are contained in the notifications.
.1.3.6.1.2.1.98.3.1.7,GSMP-MIB::gsmpNotificationsGroup,,,,,,The notifications which indicate specific changes in the value of objects gsmpSessionTable
.1.3.6.1.2.1.98.3.2,GSMP-MIB::gsmpCompliances,,,,,,
.1.3.6.1.2.1.98.3.2.1,GSMP-MIB::gsmpModuleCompliance,,,,,,The compliance statement for agents that support the GSMP MIB.
.1.3.6.1.2.1.99,ENTITY-SENSOR-MIB::entitySensorMIB,,,,,,This module defines Entity MIB extensions for physical sensors. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3433; see the RFC itself for full legal notices.
.1.3.6.1.2.1.99.1,ENTITY-SENSOR-MIB::entitySensorObjects,,,,,,
.1.3.6.1.2.1.99.1.1,ENTITY-SENSOR-MIB::entPhySensorTable,,not-accessible,,current,,This table contains one row per physical sensor represented by an associated row in the entPhysicalTable.
.1.3.6.1.2.1.99.1.1.1,ENTITY-SENSOR-MIB::entPhySensorEntry,,not-accessible,entPhysicalIndex,current,,Information about a particular physical sensor. An entry in this table describes the present reading of a sensor, the measurement units and scale, and sensor operational status. Entries are created in this table by the agent. An entry for each physical sensor SHOULD be created at the same time as the associated entPhysicalEntry. An entry SHOULD be destroyed if the associated entPhysicalEntry is destroyed.
.1.3.6.1.2.1.99.1.1.1.1,ENTITY-SENSOR-MIB::entPhySensorType,INTEGER,read-only,,current,other(1):unknown(2):voltsAC(3):voltsDC(4):amperes(5):watts(6):hertz(7):celsius(8):percentRH(9):rpm(10):cmm(11):truthvalue(12),The type of data returned by the associated entPhySensorValue object. This object SHOULD be set by the agent during entry creation, and the value SHOULD NOT change during operation.
.1.3.6.1.2.1.99.1.1.1.2,ENTITY-SENSOR-MIB::entPhySensorScale,INTEGER,read-only,,current,yocto(1):zepto(2):atto(3):femto(4):pico(5):nano(6):micro(7):milli(8):units(9):kilo(10):mega(11):giga(12):tera(13):exa(14):peta(15):zetta(16):yotta(17),The exponent to apply to values returned by the associated entPhySensorValue object. This object SHOULD be set by the agent during entry creation, and the value SHOULD NOT change during operation.
.1.3.6.1.2.1.99.1.1.1.3,ENTITY-SENSOR-MIB::entPhySensorPrecision,Integer32,read-only,,current,,The number of decimal places of precision in fixed-point sensor values returned by the associated entPhySensorValue object. This object SHOULD be set to '0' when the associated entPhySensorType value is not a fixed-point type: e.g., 'percentRH(9)', 'rpm(10)', 'cmm(11)', or 'truthvalue(12)'. This object SHOULD be set by the agent during entry creation, and the value SHOULD NOT change during operation.
.1.3.6.1.2.1.99.1.1.1.4,ENTITY-SENSOR-MIB::entPhySensorValue,Integer32,read-only,,current,,The most recent measurement obtained by the agent for this sensor. To correctly interpret the value of this object, the associated entPhySensorType, entPhySensorScale, and entPhySensorPrecision objects must also be examined.
.1.3.6.1.2.1.99.1.1.1.5,ENTITY-SENSOR-MIB::entPhySensorOperStatus,INTEGER,read-only,,current,ok(1):unavailable(2):nonoperational(3),The operational status of the sensor.
.1.3.6.1.2.1.99.1.1.1.6,ENTITY-SENSOR-MIB::entPhySensorUnitsDisplay,OCTET,read-only,,current,,A textual description of the data units that should be used in the display of entPhySensorValue.
.1.3.6.1.2.1.99.1.1.1.7,ENTITY-SENSOR-MIB::entPhySensorValueTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at the time the status and/or value of this sensor was last obtained by the agent.
.1.3.6.1.2.1.99.1.1.1.8,ENTITY-SENSOR-MIB::entPhySensorValueUpdateRate,Unsigned32,read-only,,current,,An indication of the frequency that the agent updates the associated entPhySensorValue object, representing in milliseconds. The value zero indicates: - the sensor value is updated on demand (e.g., when polled by the agent for a get-request), - the sensor value is updated when the sensor value changes (event-driven), - the agent does not know the update rate. 
.1.3.6.1.2.1.99.3,ENTITY-SENSOR-MIB::entitySensorConformance,,,,,,
.1.3.6.1.2.1.99.3.1,ENTITY-SENSOR-MIB::entitySensorCompliances,,,,,,
.1.3.6.1.2.1.99.3.1.1,ENTITY-SENSOR-MIB::entitySensorCompliance,,,,,,Describes the requirements for conformance to the Entity Sensor MIB module.
.1.3.6.1.2.1.99.3.2,ENTITY-SENSOR-MIB::entitySensorGroups,,,,,,
.1.3.6.1.2.1.99.3.2.1,ENTITY-SENSOR-MIB::entitySensorValueGroup,,,,,,A collection of objects representing physical entity sensor information.
.1.3.6.1.2.1.100,TRANSPORT-ADDRESS-MIB::transportAddressMIB,,,,,,This MIB module provides commonly used transport address definitions. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3419; see the RFC itself for full legal notices.
.1.3.6.1.2.1.100.1,TRANSPORT-ADDRESS-MIB::transportDomains,,,,,,
.1.3.6.1.2.1.100.1.1,TRANSPORT-ADDRESS-MIB::transportDomainUdpIpv4,,,,,,The UDP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4 for global IPv4 addresses.
.1.3.6.1.2.1.100.1.2,TRANSPORT-ADDRESS-MIB::transportDomainUdpIpv6,,,,,,The UDP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6 for global IPv6 addresses.
.1.3.6.1.2.1.100.1.3,TRANSPORT-ADDRESS-MIB::transportDomainUdpIpv4z,,,,,,The UDP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4z for scoped IPv4 addresses with a zone index.
.1.3.6.1.2.1.100.1.4,TRANSPORT-ADDRESS-MIB::transportDomainUdpIpv6z,,,,,,The UDP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6z for scoped IPv6 addresses with a zone index.
.1.3.6.1.2.1.100.1.5,TRANSPORT-ADDRESS-MIB::transportDomainTcpIpv4,,,,,,The TCP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4 for global IPv4 addresses.
.1.3.6.1.2.1.100.1.6,TRANSPORT-ADDRESS-MIB::transportDomainTcpIpv6,,,,,,The TCP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6 for global IPv6 addresses.
.1.3.6.1.2.1.100.1.7,TRANSPORT-ADDRESS-MIB::transportDomainTcpIpv4z,,,,,,The TCP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4z for scoped IPv4 addresses with a zone index.
.1.3.6.1.2.1.100.1.8,TRANSPORT-ADDRESS-MIB::transportDomainTcpIpv6z,,,,,,The TCP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6z for scoped IPv6 addresses with a zone index.
.1.3.6.1.2.1.100.1.9,TRANSPORT-ADDRESS-MIB::transportDomainSctpIpv4,,,,,,The SCTP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4 for global IPv4 addresses. This transport domain usually represents the primary address on multihomed SCTP endpoints.
.1.3.6.1.2.1.100.1.10,TRANSPORT-ADDRESS-MIB::transportDomainSctpIpv6,,,,,,The SCTP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6 for global IPv6 addresses. This transport domain usually represents the primary address on multihomed SCTP endpoints.
.1.3.6.1.2.1.100.1.11,TRANSPORT-ADDRESS-MIB::transportDomainSctpIpv4z,,,,,,The SCTP over IPv4 transport domain. The corresponding transport address is of type TransportAddressIPv4z for scoped IPv4 addresses with a zone index. This transport domain usually represents the primary address on multihomed SCTP endpoints.
.1.3.6.1.2.1.100.1.12,TRANSPORT-ADDRESS-MIB::transportDomainSctpIpv6z,,,,,,The SCTP over IPv6 transport domain. The corresponding transport address is of type TransportAddressIPv6z for scoped IPv6 addresses with a zone index. This transport domain usually represents the primary address on multihomed SCTP endpoints.
.1.3.6.1.2.1.100.1.13,TRANSPORT-ADDRESS-MIB::transportDomainLocal,,,,,,The Posix Local IPC transport domain. The corresponding transport address is of type TransportAddressLocal. The Posix Local IPC transport domain incorporates the well-known UNIX domain sockets.
.1.3.6.1.2.1.100.1.14,TRANSPORT-ADDRESS-MIB::transportDomainUdpDns,,,,,,The UDP transport domain using fully qualified domain names. The corresponding transport address is of type TransportAddressDns.
.1.3.6.1.2.1.100.1.15,TRANSPORT-ADDRESS-MIB::transportDomainTcpDns,,,,,,The TCP transport domain using fully qualified domain names. The corresponding transport address is of type TransportAddressDns.
.1.3.6.1.2.1.100.1.16,TRANSPORT-ADDRESS-MIB::transportDomainSctpDns,,,,,,The SCTP transport domain using fully qualified domain names. The corresponding transport address is of type TransportAddressDns.
.1.3.6.1.2.1.101,MALLOC-MIB::mallocMIB,,,,,,The MIB module for management of multicast address allocation. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3559; see the RFC itself for full legal notices.
.1.3.6.1.2.1.101.1,MALLOC-MIB::mallocMIBObjects,,,,,,
.1.3.6.1.2.1.101.1.1,MALLOC-MIB::malloc,,,,,,
.1.3.6.1.2.1.101.1.1.1,MALLOC-MIB::mallocCapabilities,BITS,read-only,,current,startTime(0):serverMobility(1):retryAfter(2),This object describes the capabilities which a client or server supports. The startTime bit indicates that allocations with a future start time are supported. The serverMobility bit indicates that allocations can be renewed or released from a server other than the one granting the original allocation. The retryAfter bit indicates support for a waiting state where the client may check back at a later time to get the status of its request.
.1.3.6.1.2.1.101.1.1.2,MALLOC-MIB::mallocScopeTable,,not-accessible,,current,,The (conceptual) table containing information on multicast scopes from which addresses may be allocated. Entries in this table may be dynamically discovered via some other protocol, such as MZAP, or may be statically configured, such as in an isolated network environment. Each scope is associated with a range of multicast addresses, and ranges for different rows must be disjoint.
.1.3.6.1.2.1.101.1.1.2.1,MALLOC-MIB::mallocScopeEntry,,not-accessible,mallocScopeAddressType:mallocScopeFirstAddress,current,,An entry (conceptual row) containing the information on a particular multicast scope.
.1.3.6.1.2.1.101.1.1.2.1.1,MALLOC-MIB::mallocScopeAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the addresses in the multicast scope range. Legal values correspond to the subset of address families for which multicast address allocation is supported.
.1.3.6.1.2.1.101.1.1.2.1.2,MALLOC-MIB::mallocScopeFirstAddress,OCTET,not-accessible,,current,,The first address in the multicast scope range. The type of this address is determined by the value of the mallocScopeAddressType object.
.1.3.6.1.2.1.101.1.1.2.1.3,MALLOC-MIB::mallocScopeLastAddress,OCTET,read-create,,current,,The last address in the multicast scope range. The type of this address is determined by the value of the mallocScopeAddressType object.
.1.3.6.1.2.1.101.1.1.2.1.4,MALLOC-MIB::mallocScopeHopLimit,Unsigned32,read-create,,current,,The default IPv4 TTL or IPv6 hop limit which applications should use for groups within the scope.
.1.3.6.1.2.1.101.1.1.2.1.5,MALLOC-MIB::mallocScopeStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table. If write access is supported, the other writable objects in this table may be modified even while the status is `active'.
.1.3.6.1.2.1.101.1.1.2.1.6,MALLOC-MIB::mallocScopeSource,INTEGER,read-only,,current,other(1):manual(2):local(3):mzap(4):madcap(5),The method by which this entry was learned.
.1.3.6.1.2.1.101.1.1.2.1.7,MALLOC-MIB::mallocScopeDivisible,INTEGER,read-create,,current,true(1):false(2),If false, the server may allocate addresses out of the entire range. If true, the server must not allocate addresses out of the entire range, but may only allocate addresses out of a subrange learned via another method. Creating or deleting a scope which is not divisible has the side effect of creating or deleting the corresponding entry in the mallocAllocRangeTable. Deleting a scope which is divisible has the side effect of deleting any corresponding entries in the mallocAllocRangeTable, and the mallocRequestTable.
.1.3.6.1.2.1.101.1.1.2.1.8,MALLOC-MIB::mallocScopeServerAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the address of a multicast address allocation server to which a request may be sent.
.1.3.6.1.2.1.101.1.1.2.1.9,MALLOC-MIB::mallocScopeServerAddress,OCTET,read-create,,current,,The address of a multicast address allocation server to which a request may be sent. The default value is an zero- length address, indicating that no server is known. The type of this address is determined by the value of the mallocScopeServerAddressType object.
.1.3.6.1.2.1.101.1.1.2.1.10,MALLOC-MIB::mallocScopeSSM,INTEGER,read-create,,current,true(1):false(2),Indicates whether the scope is a Source-Specific Multicast (SSM) range.
.1.3.6.1.2.1.101.1.1.2.1.11,MALLOC-MIB::mallocScopeStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.101.1.1.3,MALLOC-MIB::mallocScopeNameTable,,not-accessible,,current,,The (conceptual) table containing information on multicast scope names. Entries in this table may be dynamically discovered via some other protocol, such as MZAP, or may be statically configured, such as in an isolated network environment.
.1.3.6.1.2.1.101.1.1.3.1,MALLOC-MIB::mallocScopeNameEntry,,not-accessible,mallocScopeAddressType:mallocScopeFirstAddress:IMPLIEDmallocScopeNameLangName,current,,An entry (conceptual row) containing the information on a particular multicast scope name.
.1.3.6.1.2.1.101.1.1.3.1.1,MALLOC-MIB::mallocScopeNameLangName,OCTET,not-accessible,,current,,The RFC 3066 language tag for the language of the scope name.
.1.3.6.1.2.1.101.1.1.3.1.2,MALLOC-MIB::mallocScopeNameScopeName,OCTET,read-create,,current,,The textual name associated with the multicast scope. The value of this object should be suitable for displaying to end-users, such as when allocating a multicast address in this scope. If the scope is an IPv4 scope, and no name is specified, the default value of this object should be the string 239.x.x.x/y with x and y replaced appropriately to describe the address and mask length associated with the scope. If the scope is an IPv6 scope, and no name is specified, the default value of this object should generically describe the scope level (e.g., site).
.1.3.6.1.2.1.101.1.1.3.1.3,MALLOC-MIB::mallocScopeNameDefault,INTEGER,read-create,,current,true(1):false(2),If true, indicates a preference that the name in the associated language should be used by applications if no name is available in a desired language.
.1.3.6.1.2.1.101.1.1.3.1.4,MALLOC-MIB::mallocScopeNameStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table. If write access is supported, the other writable objects in this table may be modified even while the status is `active'.
.1.3.6.1.2.1.101.1.1.3.1.5,MALLOC-MIB::mallocScopeNameStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.101.1.1.4,MALLOC-MIB::mallocAllocRangeTable,,not-accessible,,current,,The (conceptual) table containing information on subranges of addresses from which the device may allocate addresses, if it is a MAAS. If the device is a Prefix Coordinator, any ranges which the device is advertising to MAAS's will be in this table. Note that the device may be both a MAAS and a Prefix Coordinator. Address ranges for different rows must be disjoint, and must be contained with the address range of the corresponding row of the mallocScopeTable. Deleting an allocation range has the side effect of deleting any entries within that range from the mallocAddressTable.
.1.3.6.1.2.1.101.1.1.4.1,MALLOC-MIB::mallocAllocRangeEntry,,not-accessible,mallocScopeAddressType:mallocScopeFirstAddress:mallocAllocRangeFirstAddress,current,,An entry (conceptual row) containing the information on a particular allocation range.
.1.3.6.1.2.1.101.1.1.4.1.1,MALLOC-MIB::mallocAllocRangeFirstAddress,OCTET,not-accessible,,current,,The first address in the allocation range. The type of this address is determined by the value of the mallocScopeAddressType object.
.1.3.6.1.2.1.101.1.1.4.1.2,MALLOC-MIB::mallocAllocRangeLastAddress,OCTET,read-create,,current,,The last address in the allocation range. The type of this address is determined by the value of the mallocScopeAddressType object.
.1.3.6.1.2.1.101.1.1.4.1.3,MALLOC-MIB::mallocAllocRangeStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table. If write access is supported, the other writable objects in this table may be modified even while the status is `active'.
.1.3.6.1.2.1.101.1.1.4.1.4,MALLOC-MIB::mallocAllocRangeSource,INTEGER,read-only,,current,other(1):manual(2):local(3),The means by which this entry was learned.
.1.3.6.1.2.1.101.1.1.4.1.5,MALLOC-MIB::mallocAllocRangeLifetime,Unsigned32,read-create,,current,,The number of seconds remaining in the lifetime of the (sub)range out of which addresses are being allocated. A value of 0 indicates that the range is not subject to aging.
.1.3.6.1.2.1.101.1.1.4.1.6,MALLOC-MIB::mallocAllocRangeMaxLeaseAddrs,Unsigned32,read-create,,current,,The maximum number of addresses which the server is willing to grant for each future request in this range. A value of 0 means that no specific limit is enforced, as long as the server has valid addresses to allocate.
.1.3.6.1.2.1.101.1.1.4.1.7,MALLOC-MIB::mallocAllocRangeMaxLeaseTime,Unsigned32,read-create,,current,,The maximum lifetime which the server will grant for future requests in this range. A value of 0 means that no additional limit is enforced beyond that of mallocAllocRangeLifetime.
.1.3.6.1.2.1.101.1.1.4.1.8,MALLOC-MIB::mallocAllocRangeNumAllocatedAddrs,Gauge32,read-only,,current,,The number of addresses in the range which have been allocated. This value can be used to determine the current address space utilization within the scoped range. This should match the total number of addresses for this scope covered by entries in the mallocAddressTable.
.1.3.6.1.2.1.101.1.1.4.1.9,MALLOC-MIB::mallocAllocRangeNumOfferedAddrs,Gauge32,read-only,,current,,The number of addresses in the range which have been offered. This number should match the sum of mallocRequestNumAddrs for all entries in the mallocRequestTable in the offered state. Together with mallocAllocRangeNumAllocatedAddrs and mallocAllocRangeNumTryingAddrs, this can be used to determine the address space utilization within the scoped range in the immediate future.
.1.3.6.1.2.1.101.1.1.4.1.10,MALLOC-MIB::mallocAllocRangeNumWaitingAddrs,Gauge32,read-only,,current,,The number of addresses in the range which have been requested, but whose state is waiting, while the server attempts to acquire more address space.
.1.3.6.1.2.1.101.1.1.4.1.11,MALLOC-MIB::mallocAllocRangeNumTryingAddrs,Gauge32,read-only,,current,,The number of addresses in the scope covered by entries in the mallocRequestTable in the trying state.
.1.3.6.1.2.1.101.1.1.4.1.12,MALLOC-MIB::mallocAllocRangeAdvertisable,INTEGER,read-create,,current,true(1):false(2),The value of this object is true if the range is eligible to be advertised to other MAASs. When the row is first created, the default value of this object is true if the scope is divisible, and is false otherwise.
.1.3.6.1.2.1.101.1.1.4.1.13,MALLOC-MIB::mallocAllocRangeTotalAllocatedAddrs,Gauge32,read-only,,current,,The approximate number of addresses in the range which have been allocated by any MAAS, as determined by a Prefix Coordinator. This object need only be present if mallocAllocRangeAdvertisable is true. If the number is unknown, a value of 0 may be reported.
.1.3.6.1.2.1.101.1.1.4.1.14,MALLOC-MIB::mallocAllocRangeTotalRequestedAddrs,Gauge32,read-only,,current,,The approximate number of addresses in the range for which there is potential demand among MAASs, as determined by a Prefix Coordinator. This object need only be present if mallocAllocRangeAdvertisable is true. If the number is unknown, a value of 0 may be reported.
.1.3.6.1.2.1.101.1.1.4.1.15,MALLOC-MIB::mallocAllocRangeStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.101.1.1.5,MALLOC-MIB::mallocRequestTable,,not-accessible,,current,,The (conceptual) table containing information on allocation requests, whether allocated or in progress. This table may also be used to determine which clients are responsible for high address space utilization within a given scope. Entries in this table reflect requests dynamically received by an address allocation protocol.
.1.3.6.1.2.1.101.1.1.5.1,MALLOC-MIB::mallocRequestEntry,,not-accessible,mallocRequestId,current,,An entry (conceptual row) containing the information on a particular allocation request.
.1.3.6.1.2.1.101.1.1.5.1.1,MALLOC-MIB::mallocRequestId,Unsigned32,not-accessible,,current,,An arbitrary value identifying this row.
.1.3.6.1.2.1.101.1.1.5.1.2,MALLOC-MIB::mallocRequestScopeAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the first address of the scope to which the request applies. Legal values correspond to the subset of address families for which multicast address allocation is supported.
.1.3.6.1.2.1.101.1.1.5.1.3,MALLOC-MIB::mallocRequestScopeFirstAddress,OCTET,read-only,,current,,The first address of the scope to which the request applies. This must match mallocScopeFirstAddress for some row in the mallocScopeTable. The type of this address is determined by the value of the mallocRequestScopeAddressType object.
.1.3.6.1.2.1.101.1.1.5.1.4,MALLOC-MIB::mallocRequestStartTime,Unsigned32,read-only,,current,,The number of seconds remaining before the start time of the request. A value of 0 means that the allocation is currently in effect.
.1.3.6.1.2.1.101.1.1.5.1.5,MALLOC-MIB::mallocRequestEndTime,Unsigned32,read-only,,current,,The number of seconds remaining before the end time of the request.
.1.3.6.1.2.1.101.1.1.5.1.6,MALLOC-MIB::mallocRequestNumAddrs,Unsigned32,read-only,,current,,The number of addresses requested. If the addresses have been allocated, this number should match the total number of addresses for this request covered by entries in the mallocAddressTable.
.1.3.6.1.2.1.101.1.1.5.1.7,MALLOC-MIB::mallocRequestState,INTEGER,read-only,,current,allocated(1):offered(2):waiting(3):trying(4),The state of the request. A value of allocated(1) indicates that one or more entries for this request are present in the mallocAddressTable. A value of offered(2) indicates that addresses have been offered to the client (e.g. via a MADCAP OFFER message), but the allocation has not been committed. A value of waiting(3) indicates that the allocation is blocked while the server attempts to acquire more space from which it can allocate addresses. A value of trying(4) means that no addresses have been offered to the client, but that an attempt to allocate is in progress.
.1.3.6.1.2.1.101.1.1.5.1.8,MALLOC-MIB::mallocRequestClientAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the address of the client that (last) requested this allocation.
.1.3.6.1.2.1.101.1.1.5.1.9,MALLOC-MIB::mallocRequestClientAddress,OCTET,read-only,,current,,The address of the client that (last) requested this allocation. The type of this address is determined by the value of the mallocRequestClientAddressType object.
.1.3.6.1.2.1.101.1.1.5.1.10,MALLOC-MIB::mallocRequestServerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the address of the server to which the request was (last) sent.
.1.3.6.1.2.1.101.1.1.5.1.11,MALLOC-MIB::mallocRequestServerAddress,OCTET,read-only,,current,,The address of the server to which the request was (last) sent. The type of this address is determined by the value of the mallocRequestServerAddressType object.
.1.3.6.1.2.1.101.1.1.5.1.12,MALLOC-MIB::mallocRequestLeaseIdentifier,OCTET,read-only,,current,,The Lease Identifier of this request. If the allocation mechanism in use does not use Lease Identifiers, then the value is a 0-length string.
.1.3.6.1.2.1.101.1.1.6,MALLOC-MIB::mallocAddressTable,,not-accessible,,current,,The (conceptual) table containing information on blocks of allocated addresses. This table may be used to map a given multicast group address to the associated request.
.1.3.6.1.2.1.101.1.1.6.1,MALLOC-MIB::mallocAddressEntry,,not-accessible,mallocAddressAddressType:mallocAddressFirstAddress,current,,An entry (conceptual row) containing the information on a particular block of allocated addresses. The block of addresses covered by each entry in this table must fall within a range corresponding to an entry in the mallocAllocRangeTable.
.1.3.6.1.2.1.101.1.1.6.1.1,MALLOC-MIB::mallocAddressAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the first address in the allocated block. Legal values correspond to the subset of address families for which multicast address allocation is supported.
.1.3.6.1.2.1.101.1.1.6.1.2,MALLOC-MIB::mallocAddressFirstAddress,OCTET,not-accessible,,current,,The first address in the allocated block. The type of this address is determined by the value of the mallocAddressAddressType object.
.1.3.6.1.2.1.101.1.1.6.1.3,MALLOC-MIB::mallocAddressNumAddrs,Unsigned32,read-only,,current,,The number of addresses in the allocated block.
.1.3.6.1.2.1.101.1.1.6.1.4,MALLOC-MIB::mallocAddressRequestId,Unsigned32,read-only,,current,,The index of the request which caused this block of addresses to be allocated. This value must match the value of mallocRequestId for some entry in the mallocRequestTable.
.1.3.6.1.2.1.101.1.2,MALLOC-MIB::madcap,,,,,,
.1.3.6.1.2.1.101.1.2.1,MALLOC-MIB::madcapConfig,,,,,,Group of objects that count various MADCAP events.
.1.3.6.1.2.1.101.1.2.1.1,MALLOC-MIB::madcapConfigExtraAllocationTime,Unsigned32,read-write,,current,,The amount of extra time on either side of a lease which the MADCAP server allocates to allow for clock skew among clients.
.1.3.6.1.2.1.101.1.2.1.2,MALLOC-MIB::madcapConfigNoResponseDelay,Unsigned32,read-write,,current,,The amount of time the MADCAP client allows for receiving a response from a MADCAP server.
.1.3.6.1.2.1.101.1.2.1.3,MALLOC-MIB::madcapConfigOfferHold,Unsigned32,read-write,,current,,The amount of time the MADCAP server will reserve an address for after sending an OFFER message in anticipation of receiving a REQUEST message.
.1.3.6.1.2.1.101.1.2.1.4,MALLOC-MIB::madcapConfigResponseCacheInterval,Unsigned32,read-write,,current,,The amount of time the MADCAP server uses to detect duplicate messages.
.1.3.6.1.2.1.101.1.2.1.5,MALLOC-MIB::madcapConfigClockSkewAllowance,Unsigned32,read-write,,current,,The clock skew threshold used by the MADCAP server to generate Excessive Clock Skew errors.
.1.3.6.1.2.1.101.1.2.2,MALLOC-MIB::madcapCounters,,,,,,A group of objects that count various MADCAP events.
.1.3.6.1.2.1.101.1.2.2.1,MALLOC-MIB::madcapTotalErrors,Counter32,read-only,,current,,The total number of transactions for which the MADCAP server has detected an error of any type, regardless of whether the server ignored the request or generated a NAK.
.1.3.6.1.2.1.101.1.2.2.2,MALLOC-MIB::madcapRequestsDenied,Counter32,read-only,,current,,The number of valid requests for which the MADCAP server could not complete an allocation, regardless of whether NAKs were sent. This corresponds to the Valid Request Could Not Be Completed error code in MADCAP.
.1.3.6.1.2.1.101.1.2.2.3,MALLOC-MIB::madcapInvalidRequests,Counter32,read-only,,current,,The number of invalid requests received by the MADCAP server, regardless of whether NAKs were sent. This corresponds to the Invalid Request error code in MADCAP.
.1.3.6.1.2.1.101.1.2.2.4,MALLOC-MIB::madcapExcessiveClockSkews,Counter32,read-only,,current,,The number of requests received by the MADCAP server with an excessive clock skew, regardless of whether NAKs were sent. This corresponds to the Excessive Clock Skew error code in MADCAP.
.1.3.6.1.2.1.101.1.2.2.5,MALLOC-MIB::madcapBadLeaseIds,Counter32,read-only,,current,,The number of requests received by the MADCAP server with an unrecognized Lease Identifier, regardless of whether NAKs were sent. This corresponds to the Lease Identifier Not Recognized error code in MADCAP.
.1.3.6.1.2.1.101.1.2.2.6,MALLOC-MIB::madcapDiscovers,Counter32,read-only,,current,,The number of DISCOVER messages received by the MADCAP server.
.1.3.6.1.2.1.101.1.2.2.7,MALLOC-MIB::madcapInforms,Counter32,read-only,,current,,The number of INFORM messages received by the MADCAP server.
.1.3.6.1.2.1.101.1.2.2.8,MALLOC-MIB::madcapRequests,Counter32,read-only,,current,,The number of REQUEST messages received by the MADCAP server.
.1.3.6.1.2.1.101.1.2.2.9,MALLOC-MIB::madcapRenews,Counter32,read-only,,current,,The number of RENEW messages received by the MADCAP server.
.1.3.6.1.2.1.101.1.2.2.10,MALLOC-MIB::madcapReleases,Counter32,read-only,,current,,The number of RELEASE messages received by the MADCAP server.
.1.3.6.1.2.1.101.2,MALLOC-MIB::mallocConformance,,,,,,
.1.3.6.1.2.1.101.2.1,MALLOC-MIB::mallocCompliances,,,,,,
.1.3.6.1.2.1.101.2.1.1,MALLOC-MIB::mallocServerReadOnlyCompliance,,,,,,The compliance statement for multicast address allocation servers implementing the MALLOC MIB without support for read-create (i.e., in read-only mode). Such a server can then be monitored but can not be configured with this MIB.
.1.3.6.1.2.1.101.2.1.2,MALLOC-MIB::mallocClientReadOnlyCompliance,,,,,,The compliance statement for clients implementing the MALLOC MIB without support for read-create (i.e., in read- only mode). Such clients can then be monitored but can not be configured with this MIB.
.1.3.6.1.2.1.101.2.1.3,MALLOC-MIB::mallocPrefixCoordinatorReadOnlyCompliance,,,,,,The compliance statement for prefix coordinators implementing the MALLOC MIB without support for read-create (i.e., in read-only mode). Such devices can then be monitored but can not be configured with this MIB.
.1.3.6.1.2.1.101.2.1.4,MALLOC-MIB::mallocServerFullCompliance,,,,,,The compliance statement for multicast address allocation servers implementing the MALLOC MIB with support for read- create. Such servers can then be both monitored and configured with this MIB.
.1.3.6.1.2.1.101.2.1.5,MALLOC-MIB::mallocClientFullCompliance,,,,,,The compliance statement for hosts implementing the MALLOC MIB with support for read-create. Such clients can then be both monitored and configured with this MIB.
.1.3.6.1.2.1.101.2.1.6,MALLOC-MIB::mallocPrefixCoordinatorFullCompliance,,,,,,The compliance statement for prefix coordinators implementing the MALLOC MIB with support for read-create. Such devices can then be both monitored and configured with this MIB.
.1.3.6.1.2.1.101.2.2,MALLOC-MIB::mallocGroups,,,,,,
.1.3.6.1.2.1.101.2.2.1,MALLOC-MIB::mallocBasicGroup,,,,,,The basic collection of objects providing management of IP multicast address allocation.
.1.3.6.1.2.1.101.2.2.2,MALLOC-MIB::mallocServerGroup,,,,,,A collection of objects providing management of multicast address allocation in servers.
.1.3.6.1.2.1.101.2.2.3,MALLOC-MIB::mallocClientGroup,,,,,,A collection of objects providing management of multicast address allocation in clients.
.1.3.6.1.2.1.101.2.2.4,MALLOC-MIB::madcapServerGroup,,,,,,A collection of objects providing management of MADCAP servers.
.1.3.6.1.2.1.101.2.2.5,MALLOC-MIB::madcapClientGroup,,,,,,A collection of objects providing management of MADCAP clients.
.1.3.6.1.2.1.101.2.2.6,MALLOC-MIB::mallocClientScopeGroup,,,,,,A collection of objects providing management of multicast scope information in clients.
.1.3.6.1.2.1.101.2.2.7,MALLOC-MIB::mallocPrefixCoordinatorGroup,,,,,,A collection of objects for managing Prefix Coordinators.
.1.3.6.1.2.1.102,IANA-MALLOC-MIB::ianaMallocMIB,,,,,,This MIB module defines the IANAscopeSource and IANAmallocRangeSource textual conventions for use in MIBs which need to identify ways of learning multicast scope and range information. Any additions or changes to the contents of this MIB module require either publication of an RFC, or Designated Expert Review as defined in the Guidelines for Writing IANA Considerations Section document. The Designated Expert will be selected by the IESG Area Director(s) of the Transport Area.
.1.3.6.1.2.1.103,IPV6-FLOW-LABEL-MIB::ipv6FlowLabelMIB,,,,,,This MIB module provides commonly used textual conventions for IPv6 Flow Labels. Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3595, see the RFC itself for full legal notices. 
.1.3.6.1.2.1.104,SCTP-MIB::sctpMIB,,,,,,The MIB module for managing SCTP implementations. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3873; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.104.1,SCTP-MIB::sctpObjects,,,,,,
.1.3.6.1.2.1.104.1.1,SCTP-MIB::sctpStats,,,,,,
.1.3.6.1.2.1.104.1.1.1,SCTP-MIB::sctpCurrEstab,Gauge32,read-only,,current,,The number of associations for which the current state is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING.
.1.3.6.1.2.1.104.1.1.2,SCTP-MIB::sctpActiveEstabs,Counter32,read-only,,current,,The number of times that associations have made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state: COOKIE-ECHOED -> ESTABLISHED. The upper layer initiated the association attempt.
.1.3.6.1.2.1.104.1.1.3,SCTP-MIB::sctpPassiveEstabs,Counter32,read-only,,current,,The number of times that associations have made a direct transition to the ESTABLISHED state from the CLOSED state: CLOSED -> ESTABLISHED. The remote endpoint initiated the association attempt.
.1.3.6.1.2.1.104.1.1.4,SCTP-MIB::sctpAborteds,Counter32,read-only,,current,,The number of times that associations have made a direct transition to the CLOSED state from any state using the primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful termination of the association.
.1.3.6.1.2.1.104.1.1.5,SCTP-MIB::sctpShutdowns,Counter32,read-only,,current,,The number of times that associations have made a direct transition to the CLOSED state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state. Graceful termination of the association.
.1.3.6.1.2.1.104.1.1.6,SCTP-MIB::sctpOutOfBlues,Counter32,read-only,,current,,The number of out of the blue packets received by the host. An out of the blue packet is an SCTP packet correctly formed, including the proper checksum, but for which the receiver was unable to identify an appropriate association.
.1.3.6.1.2.1.104.1.1.7,SCTP-MIB::sctpChecksumErrors,Counter32,read-only,,current,,The number of SCTP packets received with an invalid checksum.
.1.3.6.1.2.1.104.1.1.8,SCTP-MIB::sctpOutCtrlChunks,Counter64,read-only,,current,,The number of SCTP control chunks sent (retransmissions are not included). Control chunks are those chunks different from DATA.
.1.3.6.1.2.1.104.1.1.9,SCTP-MIB::sctpOutOrderChunks,Counter64,read-only,,current,,The number of SCTP ordered data chunks sent (retransmissions are not included).
.1.3.6.1.2.1.104.1.1.10,SCTP-MIB::sctpOutUnorderChunks,Counter64,read-only,,current,,The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included).
.1.3.6.1.2.1.104.1.1.11,SCTP-MIB::sctpInCtrlChunks,Counter64,read-only,,current,,The number of SCTP control chunks received (no duplicate chunks included).
.1.3.6.1.2.1.104.1.1.12,SCTP-MIB::sctpInOrderChunks,Counter64,read-only,,current,,The number of SCTP ordered data chunks received (no duplicate chunks included).
.1.3.6.1.2.1.104.1.1.13,SCTP-MIB::sctpInUnorderChunks,Counter64,read-only,,current,,The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included).
.1.3.6.1.2.1.104.1.1.14,SCTP-MIB::sctpFragUsrMsgs,Counter64,read-only,,current,,The number of user messages that have to be fragmented because of the MTU.
.1.3.6.1.2.1.104.1.1.15,SCTP-MIB::sctpReasmUsrMsgs,Counter64,read-only,,current,,The number of user messages reassembled, after conversion into DATA chunks.
.1.3.6.1.2.1.104.1.1.16,SCTP-MIB::sctpOutSCTPPacks,Counter64,read-only,,current,,The number of SCTP packets sent. Retransmitted DATA chunks are included.
.1.3.6.1.2.1.104.1.1.17,SCTP-MIB::sctpInSCTPPacks,Counter64,read-only,,current,,The number of SCTP packets received. Duplicates are included.
.1.3.6.1.2.1.104.1.1.18,SCTP-MIB::sctpDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this general statistics counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the SCTP layer statistics (defined below sctpStats branch). If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.104.1.2,SCTP-MIB::sctpParams,,,,,,
.1.3.6.1.2.1.104.1.2.1,SCTP-MIB::sctpRtoAlgorithm,INTEGER,read-only,,current,other(1):vanj(2),The algorithm used to determine the timeout value (T3-rtx) used for re-transmitting unacknowledged chunks.
.1.3.6.1.2.1.104.1.2.2,SCTP-MIB::sctpRtoMin,Unsigned32,read-only,,current,,The minimum value permitted by a SCTP implementation for the retransmission timeout value, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout value. A retransmission time value of zero means immediate retransmission. The value of this object has to be lower than or equal to stcpRtoMax's value.
.1.3.6.1.2.1.104.1.2.3,SCTP-MIB::sctpRtoMax,Unsigned32,read-only,,current,,The maximum value permitted by a SCTP implementation for the retransmission timeout value, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout value. A retransmission time value of zero means immediate re- transmission. The value of this object has to be greater than or equal to stcpRtoMin's value.
.1.3.6.1.2.1.104.1.2.4,SCTP-MIB::sctpRtoInitial,Unsigned32,read-only,,current,,The initial value for the retransmission timer. A retransmission time value of zero means immediate re- transmission.
.1.3.6.1.2.1.104.1.2.5,SCTP-MIB::sctpMaxAssocs,Integer32,read-only,,current,,The limit on the total number of associations the entity can support. In entities where the maximum number of associations is dynamic, this object should contain the value -1.
.1.3.6.1.2.1.104.1.2.6,SCTP-MIB::sctpValCookieLife,Unsigned32,read-only,,current,,Valid cookie life in the 4-way start-up handshake procedure.
.1.3.6.1.2.1.104.1.2.7,SCTP-MIB::sctpMaxInitRetr,Unsigned32,read-only,,current,,The maximum number of retransmissions at the start-up phase (INIT and COOKIE ECHO chunks). 
.1.3.6.1.2.1.104.1.3,SCTP-MIB::sctpAssocTable,,not-accessible,,current,,A table containing SCTP association-specific information.
.1.3.6.1.2.1.104.1.3.1,SCTP-MIB::sctpAssocEntry,,not-accessible,sctpAssocId,current,,General common variables and statistics for the whole association.
.1.3.6.1.2.1.104.1.3.1.1,SCTP-MIB::sctpAssocId,Unsigned32,not-accessible,,current,,Association Identification. Value identifying the association. 
.1.3.6.1.2.1.104.1.3.1.2,SCTP-MIB::sctpAssocRemHostName,OCTET,read-only,,current,,The peer's DNS name. This object needs to have the same format as the encoding in the DNS protocol. This implies that the domain name can be up to 255 octets long, each octet being 0<=x<=255 as value with US-ASCII A-Z having a case insensitive matching. If no DNS domain name was received from the peer at init time (embedded in the INIT or INIT-ACK chunk), this object is meaningless. In such cases the object MUST contain a zero- length string value. Otherwise, it contains the remote host name received at init time.
.1.3.6.1.2.1.104.1.3.1.3,SCTP-MIB::sctpAssocLocalPort,Unsigned32,read-only,,current,,The local SCTP port number used for this association.
.1.3.6.1.2.1.104.1.3.1.4,SCTP-MIB::sctpAssocRemPort,Unsigned32,read-only,,current,,The remote SCTP port number used for this association.
.1.3.6.1.2.1.104.1.3.1.5,SCTP-MIB::sctpAssocRemPrimAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The internet type of primary remote IP address. 
.1.3.6.1.2.1.104.1.3.1.6,SCTP-MIB::sctpAssocRemPrimAddr,OCTET,read-only,,current,,The primary remote IP address. The type of this address is determined by the value of sctpAssocRemPrimAddrType. The client side will know this value after INIT_ACK message reception, the server side will know this value when sending INIT_ACK message. However, values will be filled in at established(4) state.
.1.3.6.1.2.1.104.1.3.1.7,SCTP-MIB::sctpAssocHeartBeatInterval,Unsigned32,read-only,,current,,The current heartbeat interval.. Zero value means no HeartBeat, even when the concerned sctpAssocRemAddrHBFlag object is true.
.1.3.6.1.2.1.104.1.3.1.8,SCTP-MIB::sctpAssocState,INTEGER,read-write,,current,closed(1):cookieWait(2):cookieEchoed(3):established(4):shutdownPending(5):shutdownSent(6):shutdownReceived(7):shutdownAckSent(8):deleteTCB(9),The state of this SCTP association. As in TCP, deleteTCB(9) is the only value that may be set by a management station. If any other value is received, then the agent must return a wrongValue error. If a management station sets this object to the value deleteTCB(9), then this has the effect of deleting the TCB (as defined in SCTP) of the corresponding association on the managed node, resulting in immediate termination of the association. As an implementation-specific option, an ABORT chunk may be sent from the managed node to the other SCTP endpoint as a result of setting the deleteTCB(9) value. The ABORT chunk implies an ungraceful association shutdown.
.1.3.6.1.2.1.104.1.3.1.9,SCTP-MIB::sctpAssocInStreams,Unsigned32,read-only,,current,,Inbound Streams according to the negotiation at association start up.
.1.3.6.1.2.1.104.1.3.1.10,SCTP-MIB::sctpAssocOutStreams,Unsigned32,read-only,,current,,Outbound Streams according to the negotiation at association start up. 
.1.3.6.1.2.1.104.1.3.1.11,SCTP-MIB::sctpAssocMaxRetr,Unsigned32,read-only,,current,,The maximum number of data retransmissions in the association context. This value is specific for each association and the upper layer can change it by calling the appropriate primitives. This value has to be smaller than the addition of all the maximum number for all the paths (sctpAssocRemAddrMaxPathRtx). A value of zero value means no retransmissions.
.1.3.6.1.2.1.104.1.3.1.12,SCTP-MIB::sctpAssocPrimProcess,Unsigned32,read-only,,current,,This object identifies the system level process which holds primary responsibility for the SCTP association. Wherever possible, this should be the system's native unique identification number. The special value 0 can be used to indicate that no primary process is known. Note that the value of this object can be used as a pointer into the swRunTable of the HOST-RESOURCES-MIB(if the value is smaller than 2147483647) or into the sysApplElmtRunTable of the SYSAPPL-MIB.
.1.3.6.1.2.1.104.1.3.1.13,SCTP-MIB::sctpAssocT1expireds,Counter32,read-only,,current,,The T1 timer determines how long to wait for an acknowledgement after sending an INIT or COOKIE-ECHO chunk. This object reflects the number of times the T1 timer expires without having received the acknowledgement. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of sctpAssocDiscontinuityTime.
.1.3.6.1.2.1.104.1.3.1.14,SCTP-MIB::sctpAssocT2expireds,Counter32,read-only,,current,,The T2 timer determines how long to wait for an acknowledgement after sending a SHUTDOWN or SHUTDOWN-ACK chunk. This object reflects the number of times that T2- timer expired. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of sctpAssocDiscontinuityTime.
.1.3.6.1.2.1.104.1.3.1.15,SCTP-MIB::sctpAssocRtxChunks,Counter32,read-only,,current,,When T3-rtx expires, the DATA chunks that triggered the T3 timer will be re-sent according with the retransmissions rules. Every DATA chunk that was included in the SCTP packet that triggered the T3-rtx timer must be added to the value of this counter. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of sctpAssocDiscontinuityTime.
.1.3.6.1.2.1.104.1.3.1.16,SCTP-MIB::sctpAssocStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that the association represented by this row enters the ESTABLISHED state, i.e., the sctpAssocState object is set to established(4). The value of this object will be zero: - before the association enters the established(4) state, or - if the established(4) state was entered prior to the last re-initialization of the local network management subsystem.
.1.3.6.1.2.1.104.1.3.1.17,SCTP-MIB::sctpAssocDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this SCTP association counters suffered a discontinuity. The relevant counters are the specific instances associated with this interface of any Counter32 or Counter64 object contained in the sctpAssocTable or sctpLocalAddrTable or sctpRemAddrTable. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value. 
.1.3.6.1.2.1.104.1.4,SCTP-MIB::sctpAssocLocalAddrTable,,not-accessible,,current,,Expanded table of sctpAssocTable based on the AssocId index. This table shows data related to each local IP address which is used by this association.
.1.3.6.1.2.1.104.1.4.1,SCTP-MIB::sctpAssocLocalAddrEntry,,not-accessible,sctpAssocId:sctpAssocLocalAddrType:sctpAssocLocalAddr,current,,Local information about the available addresses. There will be an entry for every local IP address defined for this association. Implementors need to be aware that if the size of sctpAssocLocalAddr exceeds 114 octets then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.104.1.4.1.1,SCTP-MIB::sctpAssocLocalAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Internet type of local IP address used for this association.
.1.3.6.1.2.1.104.1.4.1.2,SCTP-MIB::sctpAssocLocalAddr,OCTET,not-accessible,,current,,The value of a local IP address available for this association. The type of this address is determined by the value of sctpAssocLocalAddrType.
.1.3.6.1.2.1.104.1.4.1.3,SCTP-MIB::sctpAssocLocalAddrStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that this row was created.
.1.3.6.1.2.1.104.1.5,SCTP-MIB::sctpAssocRemAddrTable,,not-accessible,,current,,Expanded table of sctpAssocTable based on the AssocId index. This table shows data related to each remote peer IP address which is used by this association.
.1.3.6.1.2.1.104.1.5.1,SCTP-MIB::sctpAssocRemAddrEntry,,not-accessible,sctpAssocId:sctpAssocRemAddrType:sctpAssocRemAddr,current,,Information about the most important variables for every remote IP address. There will be an entry for every remote IP address defined for this association. Implementors need to be aware that if the size of sctpAssocRemAddr exceeds 114 octets then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.104.1.5.1.1,SCTP-MIB::sctpAssocRemAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Internet type of a remote IP address available for this association.
.1.3.6.1.2.1.104.1.5.1.2,SCTP-MIB::sctpAssocRemAddr,OCTET,not-accessible,,current,,The value of a remote IP address available for this association. The type of this address is determined by the value of sctpAssocLocalAddrType.
.1.3.6.1.2.1.104.1.5.1.3,SCTP-MIB::sctpAssocRemAddrActive,INTEGER,read-only,,current,true(1):false(2),This object gives information about the reachability of this specific remote IP address. When the object is set to 'true' (1), the remote IP address is understood as Active. Active means that the threshold of no answers received from this IP address has not been reached. When the object is set to 'false' (2), the remote IP address is understood as Inactive. Inactive means that either no heartbeat or any other message was received from this address, reaching the threshold defined by the protocol.
.1.3.6.1.2.1.104.1.5.1.4,SCTP-MIB::sctpAssocRemAddrHBActive,INTEGER,read-only,,current,true(1):false(2),This object indicates whether the optional Heartbeat check associated to one destination transport address is activated or not (value equal to true or false, respectively). 
.1.3.6.1.2.1.104.1.5.1.5,SCTP-MIB::sctpAssocRemAddrRTO,Unsigned32,read-only,,current,,The current Retransmission Timeout. T3-rtx timer as defined in the protocol SCTP.
.1.3.6.1.2.1.104.1.5.1.6,SCTP-MIB::sctpAssocRemAddrMaxPathRtx,Unsigned32,read-only,,current,,Maximum number of DATA chunks retransmissions allowed to a remote IP address before it is considered inactive, as defined in RFC2960.
.1.3.6.1.2.1.104.1.5.1.7,SCTP-MIB::sctpAssocRemAddrRtx,Counter32,read-only,,current,,Number of DATA chunks retransmissions to this specific IP address. When T3-rtx expires, the DATA chunk that triggered the T3 timer will be re-sent according to the retransmissions rules. Every DATA chunk that is included in a SCTP packet and was transmitted to this specific IP address before, will be included in this counter. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of sctpAssocDiscontinuityTime.
.1.3.6.1.2.1.104.1.5.1.8,SCTP-MIB::sctpAssocRemAddrStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that this row was created.
.1.3.6.1.2.1.104.1.6,SCTP-MIB::sctpLookupLocalPortTable,,not-accessible,,current,,With the use of this table, a list of associations which are using the specified local port can be retrieved.
.1.3.6.1.2.1.104.1.6.1,SCTP-MIB::sctpLookupLocalPortEntry,,not-accessible,sctpAssocLocalPort:sctpAssocId,current,,This table is indexed by local port and association ID. Specifying a local port, we would get a list of the associations whose local port is the one specified.
.1.3.6.1.2.1.104.1.6.1.1,SCTP-MIB::sctpLookupLocalPortStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that this row was created. As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table.
.1.3.6.1.2.1.104.1.7,SCTP-MIB::sctpLookupRemPortTable,,not-accessible,,current,,With the use of this table, a list of associations which are using the specified remote port can be got
.1.3.6.1.2.1.104.1.7.1,SCTP-MIB::sctpLookupRemPortEntry,,not-accessible,sctpAssocRemPort:sctpAssocId,current,,This table is indexed by remote port and association ID. Specifying a remote port we would get a list of the associations whose local port is the one specified 
.1.3.6.1.2.1.104.1.7.1.1,SCTP-MIB::sctpLookupRemPortStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that this row was created. As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table.
.1.3.6.1.2.1.104.1.8,SCTP-MIB::sctpLookupRemHostNameTable,,not-accessible,,current,,With the use of this table, a list of associations with that particular host can be retrieved.
.1.3.6.1.2.1.104.1.8.1,SCTP-MIB::sctpLookupRemHostNameEntry,,not-accessible,sctpAssocRemHostName:sctpAssocId,current,,This table is indexed by remote host name and association ID. Specifying a host name we would get a list of the associations specifying that host name as the remote one. Implementors need to be aware that if the size of sctpAssocRemHostName exceeds 115 octets then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.104.1.8.1.1,SCTP-MIB::sctpLookupRemHostNameStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that this row was created. As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table.
.1.3.6.1.2.1.104.1.9,SCTP-MIB::sctpLookupRemPrimIPAddrTable,,not-accessible,,current,,With the use of this table, a list of associations that have the specified IP address as primary within the remote set of active addresses can be retrieved.
.1.3.6.1.2.1.104.1.9.1,SCTP-MIB::sctpLookupRemPrimIPAddrEntry,,not-accessible,sctpAssocRemPrimAddrType:sctpAssocRemPrimAddr:sctpAssocId,current,,This table is indexed by primary address and association ID. Specifying a primary address, we would get a list of the associations that have the specified remote IP address marked as primary. Implementors need to be aware that if the size of sctpAssocRemPrimAddr exceeds 114 octets then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.104.1.9.1.1,SCTP-MIB::sctpLookupRemPrimIPAddrStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created. As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table.
.1.3.6.1.2.1.104.1.10,SCTP-MIB::sctpLookupRemIPAddrTable,,not-accessible,,current,,With the use of this table, a list of associations that have the specified IP address as one of the remote ones can be retrieved. 
.1.3.6.1.2.1.104.1.10.1,SCTP-MIB::sctpLookupRemIPAddrEntry,,not-accessible,sctpAssocRemAddrType:sctpAssocRemAddr:sctpAssocId,current,,This table is indexed by a remote IP address and association ID. Specifying an IP address we would get a list of the associations that have the specified IP address included within the set of remote IP addresses.
.1.3.6.1.2.1.104.1.10.1.1,SCTP-MIB::sctpLookupRemIPAddrStartTime,TimeTicks,read-only,,current,,The value of SysUpTime at the time that this row was created. As the table will be created after the sctpAssocTable creation, this value could be equal to the sctpAssocStartTime object from the main table.
.1.3.6.1.2.1.104.2,SCTP-MIB::sctpMibConformance,,,,,,
.1.3.6.1.2.1.104.2.1,SCTP-MIB::sctpMibCompliances,,,,,,
.1.3.6.1.2.1.104.2.1.1,SCTP-MIB::--,,,,,,The compliance statement for SNMP entities which implement this SCTP MIB Module. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: 
.1.3.6.1.2.1.104.2.2,SCTP-MIB::sctpMibGroups,,,,,,
.1.3.6.1.2.1.104.2.2.1,SCTP-MIB::sctpLayerParamsGroup,,,,,,Common parameters for the SCTP layer, i.e., for all the associations. They can usually be referred to as configuration parameters.
.1.3.6.1.2.1.104.2.2.2,SCTP-MIB::sctpStatsGroup,,,,,,Statistics group. It includes the objects to collect state changes in the SCTP protocol local layer and flow control statistics.
.1.3.6.1.2.1.104.2.2.3,SCTP-MIB::sctpPerAssocParamsGroup,,,,,,The SCTP group of objects to manage per-association parameters. These variables include all the SCTP basic features.
.1.3.6.1.2.1.104.2.2.4,SCTP-MIB::sctpPerAssocStatsGroup,,,,,,Per Association Statistics group. It includes the objects to collect flow control statistics per association.
.1.3.6.1.2.1.104.2.2.5,SCTP-MIB::sctpInverseGroup,,,,,,Objects used in the inverse lookup tables.
.1.3.6.1.2.1.105,POWER-ETHERNET-MIB::powerEthernetMIB,,,,,,The MIB module for managing Power Source Equipment (PSE) working according to the IEEE 802.af Powered Ethernet (DTE Power via MDI) standard. The following terms are used throughout this MIB module. For complete formal definitions, the IEEE 802.3 standards should be consulted wherever possible: Group - A recommended, but optional, entity defined by the IEEE 802.3 management standard, in order to support a modular numbering scheme. The classical example allows an implementor to represent field-replaceable units as groups of ports, with the port numbering matching the modular hardware implementation. Port - This entity identifies the port within the group for which this entry contains information. The numbering scheme for ports is implementation specific. Copyright (c) The Internet Society (2003). This version of this MIB module is part of RFC 3621; See the RFC itself for full legal notices.
.1.3.6.1.2.1.105.0,POWER-ETHERNET-MIB::pethNotifications,,,,,,
.1.3.6.1.2.1.105.0.1,POWER-ETHERNET-MIB::pethPsePortOnOffNotification,,,,,, This Notification indicates if Pse Port is delivering or not power to the PD. This Notification SHOULD be sent on every status change except in the searching mode. At least 500 msec must elapse between notifications being emitted by the same object instance.
.1.3.6.1.2.1.105.0.2,POWER-ETHERNET-MIB::pethMainPowerUsageOnNotification,,,,,, This Notification indicate PSE Threshold usage indication is on, the usage power is above the threshold. At least 500 msec must elapse between notifications being emitted by the same object instance.
.1.3.6.1.2.1.105.0.3,POWER-ETHERNET-MIB::pethMainPowerUsageOffNotification,,,,,, This Notification indicates PSE Threshold usage indication off, the usage power is below the threshold. At least 500 msec must elapse between notifications being emitted by the same object instance.
.1.3.6.1.2.1.105.1,POWER-ETHERNET-MIB::pethObjects,,,,,,
.1.3.6.1.2.1.105.1.1,POWER-ETHERNET-MIB::pethPsePortTable,,not-accessible,,current,,A table of objects that display and control the power characteristics of power Ethernet ports on a Power Source Entity (PSE) device. This group will be implemented in managed power Ethernet switches and mid-span devices. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.105.1.1.1,POWER-ETHERNET-MIB::pethPsePortEntry,,not-accessible,pethPsePortGroupIndex:pethPsePortIndex,current,,A set of objects that display and control the power characteristics of a power Ethernet PSE port.
.1.3.6.1.2.1.105.1.1.1.1,POWER-ETHERNET-MIB::pethPsePortGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group containing the port to which a power Ethernet PSE is connected. Group means box in the stack, module in a rack and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used in this variable, pethMainPseGroupIndex, and pethNotificationControlGroupIndex to refer to a given box in a stack or module in the rack.
.1.3.6.1.2.1.105.1.1.1.2,POWER-ETHERNET-MIB::pethPsePortIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the power Ethernet PSE port within group pethPsePortGroupIndex to which the power Ethernet PSE entry is connected.
.1.3.6.1.2.1.105.1.1.1.3,POWER-ETHERNET-MIB::pethPsePortAdminEnable,INTEGER,read-write,,current,true(1):false(2),true (1) An interface which can provide the PSE functions. false(2) The interface will act as it would if it had no PSE function.
.1.3.6.1.2.1.105.1.1.1.4,POWER-ETHERNET-MIB::pethPsePortPowerPairsControlAbility,INTEGER,read-only,,current,true(1):false(2),Describes the capability of controlling the power pairs functionality to switch pins for sourcing power. The value true indicate that the device has the capability to control the power pairs. When false the PSE Pinout Alternative used cannot be controlled through the PethPsePortAdminEnable attribute.
.1.3.6.1.2.1.105.1.1.1.5,POWER-ETHERNET-MIB::pethPsePortPowerPairs,INTEGER,read-write,,current,signal(1):spare(2),Describes or controls the pairs in use. If the value of pethPsePortPowerPairsControl is true, this object is writable. A value of signal(1) means that the signal pairs only are in use. A value of spare(2) means that the spare pairs only are in use.
.1.3.6.1.2.1.105.1.1.1.6,POWER-ETHERNET-MIB::pethPsePortDetectionStatus,INTEGER,read-only,,current,disabled(1):searching(2):deliveringPower(3):fault(4):test(5):otherFault(6),Describes the operational status of the port PD detection. A value of disabled(1)- indicates that the PSE State diagram is in the state DISABLED. A value of deliveringPower(3) - indicates that the PSE State diagram is in the state POWER_ON for a duration greater than tlim max (see IEEE Std 802.3af Table 33-5 tlim). A value of fault(4) - indicates that the PSE State diagram is in the state TEST_ERROR. A value of test(5) - indicates that the PSE State diagram is in the state TEST_MODE. A value of otherFault(6) - indicates that the PSE State diagram is in the state IDLE due to the variable error_conditions. A value of searching(2)- indicates the PSE State diagram is in a state other than those listed above.
.1.3.6.1.2.1.105.1.1.1.7,POWER-ETHERNET-MIB::pethPsePortPowerPriority,INTEGER,read-write,,current,critical(1):high(2):low(3),This object controls the priority of the port from the point of view of a power management algorithm. The priority that is set by this variable could be used by a control mechanism that prevents over current situations by disconnecting first ports with lower power priority. Ports that connect devices critical to the operation of the network - like the E911 telephones ports - should be set to higher priority.
.1.3.6.1.2.1.105.1.1.1.8,POWER-ETHERNET-MIB::pethPsePortMPSAbsentCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram transitions directly from the state POWER_ON to the state IDLE due to tmpdo_timer_done being asserted.
.1.3.6.1.2.1.105.1.1.1.9,POWER-ETHERNET-MIB::pethPsePortType,OCTET,read-write,,current,,A manager will set the value of this variable to indicate the type of powered device that is connected to the port. The default value supplied by the agent if no value has ever been set should be a zero-length octet string.
.1.3.6.1.2.1.105.1.1.1.10,POWER-ETHERNET-MIB::pethPsePortPowerClassifications,INTEGER,read-only,,current,class0(1):class1(2):class2(3):class3(4):class4(5),Classification is a way to tag different terminals on the Power over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to their power requirements. The meaning of the classification labels is defined in the IEEE specification. This variable is valid only while a PD is being powered, that is, while the attribute pethPsePortDetectionStatus is reporting the enumeration deliveringPower.
.1.3.6.1.2.1.105.1.1.1.11,POWER-ETHERNET-MIB::pethPsePortInvalidSignatureCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state SIGNATURE_INVALID.
.1.3.6.1.2.1.105.1.1.1.12,POWER-ETHERNET-MIB::pethPsePortPowerDeniedCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state POWER_DENIED.
.1.3.6.1.2.1.105.1.1.1.13,POWER-ETHERNET-MIB::pethPsePortOverLoadCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state ERROR_DELAY_OVER.
.1.3.6.1.2.1.105.1.1.1.14,POWER-ETHERNET-MIB::pethPsePortShortCounter,Counter32,read-only,,current,,This counter is incremented when the PSE state diagram enters the state ERROR_DELAY_SHORT.
.1.3.6.1.2.1.105.1.3,POWER-ETHERNET-MIB::pethMainPseObjects,,,,,,
.1.3.6.1.2.1.105.1.3.1,POWER-ETHERNET-MIB::pethMainPseTable,,not-accessible,,current,,A table of objects that display and control attributes of the main power source in a PSE device. Ethernet switches are one example of boxes that would support these objects. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.105.1.3.1.1,POWER-ETHERNET-MIB::pethMainPseEntry,,not-accessible,pethMainPseGroupIndex,current,,A set of objects that display and control the Main power of a PSE. 
.1.3.6.1.2.1.105.1.3.1.1.1,POWER-ETHERNET-MIB::pethMainPseGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group to which power Ethernet PSE is connected. Group means (box in the stack, module in a rack) and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used in this variable, pethPsePortGroupIndex, and pethNotificationControlGroupIndex to refer to a given box in a stack or module in a rack.
.1.3.6.1.2.1.105.1.3.1.1.2,POWER-ETHERNET-MIB::pethMainPsePower,Gauge32,read-only,,current,,The nominal power of the PSE expressed in Watts.
.1.3.6.1.2.1.105.1.3.1.1.3,POWER-ETHERNET-MIB::pethMainPseOperStatus,INTEGER,read-only,,current,on(1):off(2):faulty(3),The operational status of the main PSE.
.1.3.6.1.2.1.105.1.3.1.1.4,POWER-ETHERNET-MIB::pethMainPseConsumptionPower,Gauge32,read-only,,current,,Measured usage power expressed in Watts.
.1.3.6.1.2.1.105.1.3.1.1.5,POWER-ETHERNET-MIB::pethMainPseUsageThreshold,Integer32,read-write,,current,,The usage threshold expressed in percents for comparing the measured power and initiating an alarm if the threshold is exceeded.
.1.3.6.1.2.1.105.1.4,POWER-ETHERNET-MIB::pethNotificationControl,,,,,,
.1.3.6.1.2.1.105.1.4.1,POWER-ETHERNET-MIB::pethNotificationControlTable,,not-accessible,,current,,A table of objects that display and control the Notification on a PSE device. Values of all read-write objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.105.1.4.1.1,POWER-ETHERNET-MIB::pethNotificationControlEntry,,not-accessible,pethNotificationControlGroupIndex,current,,A set of objects that control the Notification events.
.1.3.6.1.2.1.105.1.4.1.1.1,POWER-ETHERNET-MIB::pethNotificationControlGroupIndex,Integer32,not-accessible,,current,,This variable uniquely identifies the group. Group means box in the stack, module in a rack and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used in this variable, pethPsePortGroupIndex, and pethMainPseGroupIndex to refer to a given box in a stack or module in a rack. 
.1.3.6.1.2.1.105.1.4.1.1.2,POWER-ETHERNET-MIB::pethNotificationControlEnable,INTEGER,read-write,,current,true(1):false(2),This object controls, on a per-group basis, whether or not notifications from the agent are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
.1.3.6.1.2.1.105.2,POWER-ETHERNET-MIB::pethConformance,,,,,,
.1.3.6.1.2.1.105.2.1,POWER-ETHERNET-MIB::pethCompliances,,,,,,
.1.3.6.1.2.1.105.2.1.1,POWER-ETHERNET-MIB::pethCompliance,,,,,,Describes the requirements for conformance to the Power Ethernet MIB.
.1.3.6.1.2.1.105.2.2,POWER-ETHERNET-MIB::pethGroups,,,,,,
.1.3.6.1.2.1.105.2.2.1,POWER-ETHERNET-MIB::pethPsePortGroup,,,,,,PSE Port objects.
.1.3.6.1.2.1.105.2.2.2,POWER-ETHERNET-MIB::pethMainPseGroup,,,,,,Main PSE Objects. 
.1.3.6.1.2.1.105.2.2.3,POWER-ETHERNET-MIB::pethNotificationControlGroup,,,,,,Notification Control Objects. 
.1.3.6.1.2.1.105.2.2.4,POWER-ETHERNET-MIB::pethPsePortNotificationGroup,,,,,,Pse Port Notifications.
.1.3.6.1.2.1.105.2.2.5,POWER-ETHERNET-MIB::pethMainPowerNotificationGroup,,,,,,Main PSE Notifications.
.1.3.6.1.2.1.106,IANA-CHARSET-MIB::ianaCharsetMIB,,,,,,This MIB module defines the IANACharset TEXTUAL-CONVENTION. The IANACharset TC is used to specify the encoding of string objects defined in a MIB. Each version of this MIB will be released based on the IANA Charset Registry file (see RFC 2978) at http://www.iana.org/assignments/character-sets. Note: The IANACharset TC, originally defined in RFC 1759, was inaccurately named CodedCharSet. Note: Best practice is to define new MIB string objects with invariant UTF-8 (RFC 3629) syntax using the SnmpAdminString TC (defined in RFC 3411) in accordance with IETF Policy on Character Sets and Languages (RFC 2277). Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3808; for full legal notices see the RFC itself. Supplementary information may be available on http://www.ietf.org/copyrights/ianamib.html.
.1.3.6.1.2.1.107,HC-PerfHist-TC-MIB::hcPerfHistTCMIB,,,,,,This MIB Module provides Textual Conventions to be used by systems supporting 15 minute based performance history counts that require high-capacity counts. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3705: see the RFC itself for full legal notices.
.1.3.6.1.2.1.108,DIFFSERV-CONFIG-MIB::diffServConfigMib,,,,,,This MIB module contains differentiated services specific managed objects to perform higher-level configuration management. This MIB allows policies to use 'templates' to instantiate Differentiated Services functional datapath configurations to be assigned (associated with an interface and direction) when a policy is activated. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3747; see the RFC itself for full legal notices.
.1.3.6.1.2.1.108.1,DIFFSERV-CONFIG-MIB::diffServConfigMIBObjects,,,,,,
.1.3.6.1.2.1.108.1.2,DIFFSERV-CONFIG-MIB::diffServConfigTable,,not-accessible,,current,,A table which defines the various per-hop-behaviors for which the system has default 'templates'.
.1.3.6.1.2.1.108.1.2.1,DIFFSERV-CONFIG-MIB::diffServConfigEntry,,not-accessible,diffServConfigId,current,,An entry defining a per-hop-behavior. Each entry in this table combines the various parameters (entries) into a specific per-hop-behavior. Entries in this table might be defined by a vendor (pre-configured) or defined by a management application.
.1.3.6.1.2.1.108.1.2.1.1,DIFFSERV-CONFIG-MIB::diffServConfigId,OCTET,not-accessible,,current,,A unique id for the per-hop-behavior policy for at least the SNMP agent. For ease of administration the value may be unique within an administrative domain, but this is not required. The range of up to 116 octets is chosen to stay within the SMI limit of 128 sub-identifiers in an object identifier.
.1.3.6.1.2.1.108.1.2.1.2,DIFFSERV-CONFIG-MIB::diffServConfigDescr,OCTET,read-create,,current,,A human-readable description to identify this defined per-hop-behavior. Note that this is an SnmpAdminString, which permits UTF-8 strings. An administratively assigned identifier for a template that would be unique within an administrative domain. It is up to the management applications to agree how these are assigned within the administrative domain. Once a description, such as 'EF' is assigned, that has a certain set of parameters that achieve 'EF' from box to box. Management application code or script code can then scan the table to find the proper template and then assign it.
.1.3.6.1.2.1.108.1.2.1.3,DIFFSERV-CONFIG-MIB::diffServConfigOwner,OCTET,read-create,,current,,The owner who created this entry.
.1.3.6.1.2.1.108.1.2.1.4,DIFFSERV-CONFIG-MIB::diffServConfigLastChange,OCTET,read-only,,current,,The date and time when this entry was last changed.
.1.3.6.1.2.1.108.1.2.1.5,DIFFSERV-CONFIG-MIB::diffServConfigStart,OBJECT,read-create,,current,,The pointer to a functional datapath configuration template as set up in the DIFFSERV-MIB. This RowPointer should point to an instance of one of: diffServClfrEntry diffServMeterEntry diffServActionEntry diffServAlgDropEntry diffServQEntry A value of zeroDotZero in this attribute indicates no further Diffserv treatment is performed on traffic of this functional datapath. This also means that the template described by this row is not defined. If the row pointed to does not exist, the treatment is as if this attribute contains a value of zeroDotZero.
.1.3.6.1.2.1.108.1.2.1.6,DIFFSERV-CONFIG-MIB::diffServConfigStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The type of storage used for this row. Since an entry in this table serves as a starting point for a configuration, it is recommended that all entries comprising the configuration started by diffServConfigStart follow the storage type of this entry. Otherwise, after agent reboots a configuration may differ. It may very well be that the agent is not capable of detecting such changes and therefore, the management application should verify the correct configuration after a reboot. Rows with a StorageType of 'permanent' do not need to allow write access to any of the columnar objects in that row.
.1.3.6.1.2.1.108.1.2.1.7,DIFFSERV-CONFIG-MIB::diffServConfigStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),RowStatus object used for creation and deletion of rows in this table. All writable objects in this row may be modified at any time.
.1.3.6.1.2.1.108.2,DIFFSERV-CONFIG-MIB::diffServConfigMIBConformance,,,,,,
.1.3.6.1.2.1.108.2.1,DIFFSERV-CONFIG-MIB::diffServConfigMIBCompliances,,,,,,
.1.3.6.1.2.1.108.2.1.1,DIFFSERV-CONFIG-MIB::diffServConfigMIBFullCompliance,,,,,,The full compliance for this MIB module. For this compliance level the 'diffServMIBFullCompliance' must be met, since this MIB module depends on it in order to provide the configuration entries. 
.1.3.6.1.2.1.108.2.2,DIFFSERV-CONFIG-MIB::diffServConfigMIBGroups,,,,,,
.1.3.6.1.2.1.108.2.2.1,DIFFSERV-CONFIG-MIB::diffServConfigMIBConfigGroup,,,,,,The per-hop-behavior Group defines the MIB objects that describe the configuration template for the per-hop-behavior.
.1.3.6.1.2.1.109,IANA-PRINTER-MIB::ianaPrinterMIB,,,,,,This MIB module defines a set of printing-related TEXTUAL-CONVENTIONs for use in Printer MIB (RFC 3805), Finisher MIB (RFC 3806), and other MIBs which need to specify printing mechanism details. Any additions or changes to the contents of this MIB module require either publication of an RFC, or Designated Expert Review as defined in RFC 2434, Guidelines for Writing an IANA Considerations Section in RFCs. The Designated Expert will be selected by the IESG Area Director(s) of the Applications Area. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3805. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.110,IANA-FINISHER-MIB::ianafinisherMIB,,,,,,This MIB module defines a set of finishing-related TEXTUAL-CONVENTIONs for use in Finisher MIB (RFC 3806) and other MIBs which need to specify finishing mechanism details. Any additions or changes to the contents of this MIB module require either publication of an RFC, or Designated Expert Review as defined in RFC 2434, Guidelines for Writing an IANA Considerations Section in RFCs. The Designated Expert will be selected by the IESG Area Director(s) of the Applications Area. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3806. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.111,Finisher-MIB::finisherMIB,,,,,,The MIB module for management of printers. Copyright (C) The Internet Society (2004). This version of this MIB module was published in RFC 3806. For full legal notices see the RFC itself.
.1.3.6.1.2.1.112,ROHC-MIB::rohcMIB,,,,,,This MIB module defines a set of basic objects for monitoring and configuring robust header compression. The module covers information about running instances of ROHC (compressors or decompressors) at IP interfaces. Information about compressor contexts and decompressor contexts has different structure for different profiles. Therefore it is not provided by this MIB module, but by individual modules for different profiles. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3816. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.112.1,ROHC-MIB::rohcObjects,,,,,,
.1.3.6.1.2.1.112.1.1,ROHC-MIB::rohcInstanceObjects,,,,,,
.1.3.6.1.2.1.112.1.1.1,ROHC-MIB::rohcChannelTable,,not-accessible,,current,,This table lists and describes all ROHC channels per interface.
.1.3.6.1.2.1.112.1.1.1.1,ROHC-MIB::rohcChannelEntry,,not-accessible,ifIndex:rohcChannelID,current,,An entry describing a particular script. Every script that is stored in non-volatile memory is required to appear in this script table. Note, that the rohcChannelID identifies the channel uniquely. The ifIndex is part of the index of this table just in order to allow addressing channels per interface.
.1.3.6.1.2.1.112.1.1.1.1.2,ROHC-MIB::rohcChannelID,Unsigned32,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this channel. The value is REQUIRED to be unique per ROHC MIB implementation independent of the associated interface. The value is REQUIRED to remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. It is RECOMMENDED that the value persist across such re-initializations.
.1.3.6.1.2.1.112.1.1.1.1.3,ROHC-MIB::rohcChannelType,INTEGER,read-only,,current,notInUse(1):rohc(2):dedicatedFeedback(3),Type of usage of the channel. A channel might be currently not in use for ROHC or feedback, it might be in use as a ROHC channel carrying packets and optional piggy-backed feedback, or it might be used as a dedicated feedback channel exclusively carrying feedback.
.1.3.6.1.2.1.112.1.1.1.1.4,ROHC-MIB::rohcChannelFeedbackFor,Unsigned32,read-only,,current,,The index of another channel of this interface for which the channel serves as feedback channel. If no feedback information is transferred on this channel, then the value of this ID is 0. If the channel type is set to notInUse(1), then the value of this object must be 0. If the channel type is rohc(2) and the value of this object is a valid channel ID, then feedback information is piggy-backed on the ROHC channel. If the channel type is dedicatedFeedback(3), then feedback is transferred on this channel and the value of this object MUST be different from 0 and MUST identify an existing ROHC channel.
.1.3.6.1.2.1.112.1.1.1.1.5,ROHC-MIB::rohcChannelDescr,OCTET,read-only,,current,,A textual description of the channel.
.1.3.6.1.2.1.112.1.1.1.1.6,ROHC-MIB::rohcChannelStatus,INTEGER,read-only,,current,enabled(1):disabled(2),Status of the channel.
.1.3.6.1.2.1.112.1.1.2,ROHC-MIB::rohcInstanceTable,,not-accessible,,current,,This table lists properties of running instances of robust header compressors and decompressors at IP interfaces. It is indexed by interface number, the type of instance (compressor or decompressor), and the ID of the channel used by the instance as ROHC channel. Note that the rohcChannelID uniquely identifies an instance. The ifIndex and rohcInstanceType are part of the index, because it simplifies accessing instances per interface and for addressing either compressors or decompressors only.
.1.3.6.1.2.1.112.1.1.2.1,ROHC-MIB::rohcInstanceEntry,,not-accessible,ifIndex:rohcInstanceType:rohcChannelID,current,,An entry describing a particular instance of a robust header compressor or decompressor.
.1.3.6.1.2.1.112.1.1.2.1.2,ROHC-MIB::rohcInstanceType,INTEGER,not-accessible,,current,compressor(1):decompressor(2),Type of the instance of ROHC. It is either a compressor instance or a decompressor instance.
.1.3.6.1.2.1.112.1.1.2.1.4,ROHC-MIB::rohcInstanceFBChannelID,Unsigned32,read-only,,current,,Identifier of the channel used for feedback. If no feedback channel is used, the value of this object is 0 .
.1.3.6.1.2.1.112.1.1.2.1.5,ROHC-MIB::rohcInstanceVendor,OBJECT,read-only,,current,,An object identifier that identifies the vendor who provides the implementation of robust header description. This object identifier SHALL point to the object identifier directly below the enterprise object identifier {1 3 6 1 4 1} allocated for the vendor. The value must be the object identifier {0 0} if the vendor is not known.
.1.3.6.1.2.1.112.1.1.2.1.6,ROHC-MIB::rohcInstanceVersion,OCTET,read-only,,current,,The version number of the implementation of robust header compression. The zero-length string shall be used if the implementation does not have a version number. It is suggested that the version number consist of one or more decimal numbers separated by dots, where the first number is called the major version number.
.1.3.6.1.2.1.112.1.1.2.1.7,ROHC-MIB::rohcInstanceDescr,OCTET,read-only,,current,,A textual description of the implementation.
.1.3.6.1.2.1.112.1.1.2.1.8,ROHC-MIB::rohcInstanceClockRes,Unsigned32,read-only,,current,,This object indicates the system clock resolution in units of milliseconds. A zero (0) value means that there is no clock available.
.1.3.6.1.2.1.112.1.1.2.1.9,ROHC-MIB::rohcInstanceMaxCID,Unsigned32,read-only,,current,,The highest context ID number to be used by the compressor. Note that this parameter is not coupled to, but in effect further constrained by, rohcChannelLargeCIDs.
.1.3.6.1.2.1.112.1.1.2.1.10,ROHC-MIB::rohcInstanceLargeCIDs,INTEGER,read-only,,current,true(1):false(2),When retrieved, this boolean object returns false if the short CID representation (0 bytes or 1 prefix byte, covering CID 0 to 15) is used; it returns true, if the embedded CID representation (1 or 2 embedded CID bytes covering CID 0 to 16383) is used.
.1.3.6.1.2.1.112.1.1.2.1.11,ROHC-MIB::rohcInstanceMRRU,Unsigned32,read-only,,current,,Maximum reconstructed reception unit. This is the size of the largest reconstructed unit in octets that the decompressor is expected to reassemble from segments (see RFC 3095, Section 5.2.5). Note that this size includes the CRC. If MRRU is negotiated to be 0, no segment headers are allowed on the channel.
.1.3.6.1.2.1.112.1.1.2.1.12,ROHC-MIB::rohcInstanceContextStorageTime,INTEGER,read-write,,current,,This object indicates the default maximum amount of time information on a context belonging to this instance is kept as entry in the rohcContextTable after the context is expired or terminated. The value of this object is used to initialize rohcContexStorageTime object when a new context is created. Changing the value of an rohcInstanceContextStorageTime instance does not affect any entry of the rohcContextTable created previously. ROHC-MIB implementations SHOULD store the set value of this object persistently.
.1.3.6.1.2.1.112.1.1.2.1.13,ROHC-MIB::rohcInstanceStatus,INTEGER,read-only,,current,enabled(1):disabled(2),Status of the instance of ROHC.
.1.3.6.1.2.1.112.1.1.2.1.14,ROHC-MIB::rohcInstanceContextsTotal,Counter32,read-only,,current,,Counter of all contexts created by this instance. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.112.1.1.2.1.15,ROHC-MIB::rohcInstanceContextsCurrent,Unsigned32,read-only,,current,,Number of currently active contexts created by this instance.
.1.3.6.1.2.1.112.1.1.2.1.16,ROHC-MIB::rohcInstancePackets,Counter32,read-only,,current,,Counter of all packets passing this instance. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.112.1.1.2.1.17,ROHC-MIB::rohcInstanceIRs,Counter32,read-only,,current,,The number of all IR packets that are either sent or received by this instance. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.112.1.1.2.1.18,ROHC-MIB::rohcInstanceIRDYNs,Counter32,read-only,,current,,The number of all IR-DYN packets that are either sent or received by this instance. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.112.1.1.2.1.19,ROHC-MIB::rohcInstanceFeedbacks,Counter32,read-only,,current,,The number of all feedbacks that are either sent or received by this instance. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.112.1.1.2.1.20,ROHC-MIB::rohcInstanceCompressionRatio,Unsigned32,read-only,,current,,This object indicates the compression ratio so far over all packets on the channel served by this instance. The compression is computed over all bytes of the IP packets including the IP header but excluding all lower layer headers.
.1.3.6.1.2.1.112.1.1.3,ROHC-MIB::rohcProfileTable,,not-accessible,,current,,This table lists a set of profiles supported by the instance.
.1.3.6.1.2.1.112.1.1.3.1,ROHC-MIB::rohcProfileEntry,,not-accessible,rohcChannelID:rohcProfile,current,,An entry describing a particular profile supported by the instance. It is indexed by the rohcChannelID identifying the instance and by the rohcProfile.
.1.3.6.1.2.1.112.1.1.3.1.2,ROHC-MIB::rohcProfile,Unsigned32,not-accessible,,current,,Identifier of a profile supported. For a listing of possible profile values, see the IANA registry for 'RObust Header Compression (ROHC) Profile Identifiers' at http://www.iana.org/assignments/rohc-pro-ids
.1.3.6.1.2.1.112.1.1.3.1.3,ROHC-MIB::rohcProfileVendor,OBJECT,read-only,,current,,An object identifier that identifies the vendor who provides the implementation of robust header description. This object identifier SHALL point to the object identifier directly below the enterprise object identifier {1 3 6 1 4 1} allocated for the vendor. The value must be the object identifier {0 0} if the vendor is not known.
.1.3.6.1.2.1.112.1.1.3.1.4,ROHC-MIB::rohcProfileVersion,OCTET,read-only,,current,,The version number of the implementation of robust header compression. The zero-length string shall be used if the implementation does not have a version number. It is suggested that the version number consist of one or more decimal numbers separated by dots, where the first number is called the major version number.
.1.3.6.1.2.1.112.1.1.3.1.5,ROHC-MIB::rohcProfileDescr,OCTET,read-only,,current,,A textual description of the implementation.
.1.3.6.1.2.1.112.1.1.3.1.6,ROHC-MIB::rohcProfileNegotiated,INTEGER,read-only,,current,true(1):false(2),When retrieved, this boolean object returns true if the profile has been negotiated to be used at the instance, i.e., is supported also be the corresponding compressor/decompressor.
.1.3.6.1.2.1.112.1.2,ROHC-MIB::rohcContextTable,,not-accessible,,current,,This table lists and describes all compressor contexts per instance.
.1.3.6.1.2.1.112.1.2.1,ROHC-MIB::rohcContextEntry,,not-accessible,rohcChannelID:rohcContextCID,current,,An entry describing a particular compressor context.
.1.3.6.1.2.1.112.1.2.1.2,ROHC-MIB::rohcContextCID,Unsigned32,not-accessible,,current,,The context identifier (CID) of this context.
.1.3.6.1.2.1.112.1.2.1.3,ROHC-MIB::rohcContextCIDState,INTEGER,read-only,,current,unused(1):active(2):expired(3):terminated(4),State of the CID. When a CID is assigned to a context, its state changes from `unused' to `active'. The active context may stop operation due to some explicit signalling or after observing no packet for some specified time. In the first case then the CID state changes to `terminated', in the latter case it changes to `expired'. If the CID is re-used again for another context, the state changes back to `active'.
.1.3.6.1.2.1.112.1.2.1.4,ROHC-MIB::rohcContextProfile,Unsigned32,read-only,,current,,Identifier of the profile for this context. The profile is identified by its index in the rohcProfileTable for this instance. There MUST exist a corresponding entry in the rohcProfileTable using the value of rohcContextProfile as second part of the index (and using the same rohcChannelID as first part of the index).
.1.3.6.1.2.1.112.1.2.1.5,ROHC-MIB::rohcContextDecompressorDepth,Unsigned32,read-only,,current,,This object indicates whether reverse decompression, for example as described in RFC 3095, Section 6.1, is used on this channel or not, and if used, to what extent. Its value is only valid for decompressor contexts, i.e., if rohcInstanceType has the value decompressor(2). For compressor contexts where rohcInstanceType has the value compressor(1), the value of this object is irrelevant and MUST be set to zero (0). The value of the reverse decompression depth indicates the maximum number of packets that are buffered, and thus possibly be reverse decompressed by the decompressor. A zero (0) value means that reverse decompression is not used.
.1.3.6.1.2.1.112.1.2.1.6,ROHC-MIB::rohcContextStorageTime,INTEGER,read-write,,current,,The value of this object specifies how long this row can exist in the rohcContextTable after the rohcContextCIDState switched to expired(3) or terminated(4). This object returns the remaining time that the row may exist before it is aged out. The object is initialized with the value of the associated rohcContextStorageTime object. After expiration or termination of the context, the value of this object ticks backwards. The entry in the rohcContextTable is destroyed when the value reaches 0. The value of this object may be set in order to increase or reduce the remaining time that the row may exist. Setting the value to 0 will destroy this entry as soon as the rochContextCIDState has the value expired(3) or terminated(4). Note that there is no guarantee that the row is stored as long as this object indicates. In case of limited CID space, the instance may re-use a CID before the storage time of the corresponding row in rohcContextTable reaches the value of 0. In this case the information stored in this row is not anymore available.
.1.3.6.1.2.1.112.1.2.1.7,ROHC-MIB::rohcContextActivationTime,OCTET,read-only,,current,,The date and time when the context started to be able to compress packets or decompress packets, respectively. The value '0000000000000000'H is returned if the context has not been activated yet.
.1.3.6.1.2.1.112.1.2.1.8,ROHC-MIB::rohcContextDeactivationTime,OCTET,read-only,,current,,The date and time when the context stopped being able to compress packets or decompress packets, respectively, because it expired or was terminated for other reasons. The value '0000000000000000'H is returned if the context has not been deactivated yet.
.1.3.6.1.2.1.112.1.2.1.9,ROHC-MIB::rohcContextPackets,Counter32,read-only,,current,,The number of all packets passing this context. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable.
.1.3.6.1.2.1.112.1.2.1.10,ROHC-MIB::rohcContextIRs,Counter32,read-only,,current,,The number of all IR packets sent or received, respectively, by this context. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable.
.1.3.6.1.2.1.112.1.2.1.11,ROHC-MIB::rohcContextIRDYNs,Counter32,read-only,,current,,The number of all IR-DYN packets sent or received, respectively, by this context. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable.
.1.3.6.1.2.1.112.1.2.1.12,ROHC-MIB::rohcContextFeedbacks,Counter32,read-only,,current,,The number of all feedbacks sent or received, respectively, by this context. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable.
.1.3.6.1.2.1.112.1.2.1.13,ROHC-MIB::rohcContextDecompressorFailures,Counter32,read-only,,current,,The number of all decompressor failures so far in this context. The number is only valid for decompressor contexts, i.e., if rohcInstanceType has the value decompressor(2). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable.
.1.3.6.1.2.1.112.1.2.1.14,ROHC-MIB::rohcContextDecompressorRepairs,Counter32,read-only,,current,,The number of all context repairs so far in this context. The number is only valid for decompressor contexts, i.e., if rohcInstanceType has the value decompressor(2). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable.
.1.3.6.1.2.1.112.1.2.1.15,ROHC-MIB::rohcContextAllPacketsRatio,Unsigned32,read-only,,current,,This object indicates the compression ratio so far over all packets passing this context. The compression is computed over all bytes of the IP packets including the IP header but excluding all lower layer headers.
.1.3.6.1.2.1.112.1.2.1.16,ROHC-MIB::rohcContextAllHeadersRatio,Unsigned32,read-only,,current,,This object indicates the compression ratio so far over all packet headers passing this context. The compression is computed over all bytes of all headers that are subject to compression for the used profile.
.1.3.6.1.2.1.112.1.2.1.17,ROHC-MIB::rohcContextAllPacketsMeanSize,Unsigned32,read-only,,current,,This object indicates the mean compressed packet size of all packets passing this context. The packet size includes the IP header and payload but excludes all lower layer headers. The mean value is given in byte rounded to the next integer value.
.1.3.6.1.2.1.112.1.2.1.18,ROHC-MIB::rohcContextAllHeadersMeanSize,Unsigned32,read-only,,current,,This object indicates the mean compressed packet header size of all packets passing this context. The packet header size is the sum of the size of all headers of a packet that are subject to compression for the used profile. The mean value is given in byte rounded to the next integer value.
.1.3.6.1.2.1.112.1.2.1.19,ROHC-MIB::rohcContextLastPacketsRatio,Unsigned32,read-only,,current,,This object indicates the compression ratio concerning the last 16 packets passing this context or concerning all packets passing this context if they are less than 16, so far. The compression is computed over all bytes of the IP packets including the IP header but excluding all lower layer headers.
.1.3.6.1.2.1.112.1.2.1.20,ROHC-MIB::rohcContextLastHeadersRatio,Unsigned32,read-only,,current,,This object indicates the compression ratio concerning the headers of the last 16 packets passing this context or concerning the headers of all packets passing this context if they are less than 16, so far. The compression is computed over all bytes of all headers that are subject to compression for the used profile.
.1.3.6.1.2.1.112.1.2.1.21,ROHC-MIB::rohcContextLastPacketsMeanSize,Unsigned32,read-only,,current,,This object indicates the mean compressed packet size concerning the last 16 packets passing this context or concerning all packets passing this context if they are less than 16, so far. The packet size includes the IP header and payload but excludes all lower layer headers. The mean value is given in byte rounded to the next integer value.
.1.3.6.1.2.1.112.1.2.1.22,ROHC-MIB::rohcContextLastHeadersMeanSize,Unsigned32,read-only,,current,,This object indicates the mean compressed packet header size concerning the last 16 packets passing this context or concerning all packets passing this context if they are less than 16, so far. The packet header size is the sum of the size of all headers of a packet that are subject to compression for the used profile. The mean value is given in byte rounded to the next integer value.
.1.3.6.1.2.1.112.2,ROHC-MIB::rohcConformance,,,,,,
.1.3.6.1.2.1.112.2.1,ROHC-MIB::rohcCompliances,,,,,,
.1.3.6.1.2.1.112.2.1.1,ROHC-MIB::rohcCompliance,,,,,,The compliance statement for SNMP entities that implement the ROHC-MIB. Note that compliance with this compliance statement requires compliance with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB (RFC2863).
.1.3.6.1.2.1.112.2.2,ROHC-MIB::rohcGroups,,,,,,
.1.3.6.1.2.1.112.2.2.2,ROHC-MIB::rohcInstanceGroup,,,,,,A collection of objects providing information about ROHC instances, used channels and available profiles.
.1.3.6.1.2.1.112.2.2.4,ROHC-MIB::rohcStatisticsGroup,,,,,,A collection of objects providing ROHC statistics.
.1.3.6.1.2.1.112.2.2.5,ROHC-MIB::rohcContextGroup,,,,,,A collection of objects providing information about ROHC compressor contexts and decompressor contexts.
.1.3.6.1.2.1.112.2.2.6,ROHC-MIB::rohcTimerGroup,,,,,,A collection of objects providing statistical information about ROHC compressor contexts and decompressor contexts.
.1.3.6.1.2.1.112.2.2.7,ROHC-MIB::rohcContextStatisticsGroup,,,,,,A collection of objects providing statistical information about ROHC compressor contexts and decompressor contexts.
.1.3.6.1.2.1.113,ROHC-UNCOMPRESSED-MIB::rohcUncmprMIB,,,,,,This MIB module defines a set of objects for monitoring and configuring RObust Header Compression (ROHC). The objects are specific to ROHC uncompressed (profile 0x0000). Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3816. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.113.1,ROHC-UNCOMPRESSED-MIB::rohcUncmprObjects,,,,,,
.1.3.6.1.2.1.113.1.1,ROHC-UNCOMPRESSED-MIB::rohcUncmprContextTable,,not-accessible,,current,,This table lists and describes ROHC uncompressed profile specific properties of compressor contexts and decompressor contexts. It extends the rohcContextTable of the ROHC-MIB module.
.1.3.6.1.2.1.113.1.1.1,ROHC-UNCOMPRESSED-MIB::rohcUncmprContextEntry,,not-accessible,rohcChannelID:rohcContextCID,current,,An entry describing a particular context.
.1.3.6.1.2.1.113.1.1.1.3,ROHC-UNCOMPRESSED-MIB::rohcUncmprContextState,INTEGER,read-only,,current,initAndRefresh(1):normal(2):noContext(3):fullContext(4),State of the context. States initAndRefresh(1) and normal(2) are states of compressor contexts, states noContext(3) and fullContext(4) are states of decompressor contexts.
.1.3.6.1.2.1.113.1.1.1.4,ROHC-UNCOMPRESSED-MIB::rohcUncmprContextMode,INTEGER,read-only,,current,unidirectional(1):bidirectional(2),Mode of the context.
.1.3.6.1.2.1.113.1.1.1.5,ROHC-UNCOMPRESSED-MIB::rohcUncmprContextACKs,Counter32,read-only,,current,,The number of all positive feedbacks (ACK) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB.
.1.3.6.1.2.1.113.2,ROHC-UNCOMPRESSED-MIB::rohcUncmprConformance,,,,,,
.1.3.6.1.2.1.113.2.1,ROHC-UNCOMPRESSED-MIB::rohcUncmprCompliances,,,,,,
.1.3.6.1.2.1.113.2.1.1,ROHC-UNCOMPRESSED-MIB::rohcUncmprCompliance,,,,,,The compliance statement for SNMP entities that implement the ROHC-UNCOMPRESSED-MIB. Note that compliance with this compliance statement requires compliance with the rohcCompliance MODULE-COMPLIANCE statement of the ROHC-MIB and with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB (RFC2863).
.1.3.6.1.2.1.113.2.2,ROHC-UNCOMPRESSED-MIB::rohcUncmprGroups,,,,,,
.1.3.6.1.2.1.113.2.2.1,ROHC-UNCOMPRESSED-MIB::rohcUncmprContextGroup,,,,,,A collection of objects providing information about ROHC uncompressed compressors and decompressors.
.1.3.6.1.2.1.113.2.2.2,ROHC-UNCOMPRESSED-MIB::rohcUncmprStatisticsGroup,,,,,,An object providing context statistics.
.1.3.6.1.2.1.114,ROHC-RTP-MIB::rohcRtpMIB,,,,,,This MIB module defines a set of objects for monitoring and configuring RObust Header Compression (ROHC). The objects are specific to ROHC RTP (profile 0x0001), ROHC UDP (profile 0x0002), and ROHC ESP (profile 0x0003) defined in RFC 3095 and for the ROHC LLA profile (profile 0x0005) defined in RFC 3242. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3816. For full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.114.1,ROHC-RTP-MIB::rohcRtpObjects,,,,,,
.1.3.6.1.2.1.114.1.1,ROHC-RTP-MIB::rohcRtpContextTable,,not-accessible,,current,,This table lists and describes RTP profile specific properties of compressor contexts and decompressor contexts. It extends the rohcContextTable of the ROHC-MIB module.
.1.3.6.1.2.1.114.1.1.1,ROHC-RTP-MIB::rohcRtpContextEntry,,not-accessible,rohcChannelID:rohcContextCID,current,,An entry describing a particular context.
.1.3.6.1.2.1.114.1.1.1.3,ROHC-RTP-MIB::rohcRtpContextState,INTEGER,read-only,,current,initAndRefresh(1):firstOrder(2):secondOrder(3):noContext(4):staticContext(5):fullContext(6),State of the context as defined in RFC 3095. States initAndRefresh(1), firstOrder(2), and secondOrder(3) are states of compressor contexts, states noContext(4), staticContext(5) and fullContext(6) are states of decompressor contexts.
.1.3.6.1.2.1.114.1.1.1.4,ROHC-RTP-MIB::rohcRtpContextMode,INTEGER,read-only,,current,unidirectional(1):optimistic(2):reliable(3),Mode of the context.
.1.3.6.1.2.1.114.1.1.1.5,ROHC-RTP-MIB::rohcRtpContextAlwaysPad,INTEGER,read-only,,current,true(1):false(2),Boolean, only applicable to compressor contexts using the LLA profile. If its value is true, the compressor must pad every RHP packet with a minimum of one octet ROHC padding. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.6,ROHC-RTP-MIB::rohcRtpContextLargePktsAllowed,INTEGER,read-only,,current,true(1):false(2),Boolean, only applicable to compressor contexts using the LLA profile. It specifies how to handle packets that do not fit any of the preferred packet sizes specified. If its value is true, the compressor must deliver the larger packet as-is and must not use segmentation. If it is set to false, the ROHC segmentation scheme must be used to split the packet into two or more segments, and each segment must further be padded to fit one of the preferred packet sizes. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.7,ROHC-RTP-MIB::rohcRtpContextVerifyPeriod,Unsigned32,read-only,,current,,This object is only applicable to compressor contexts using the LLA profile. It specifies the minimum frequency with which a packet validating the context must be sent. This tells the compressor that a packet containing a CRC field must be sent at least once every N packets, where N is the value of the object. A value of 0 indicates that periodical verifications are disabled. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.8,ROHC-RTP-MIB::rohcRtpContextSizesAllowed,Unsigned32,read-only,,current,,The value of this object is only valid for decompressor contexts, i.e., if rohcInstanceType of the corresponding rohcContextEntry has the value decompressor(2). For compressor contexts where rohcInstanceType has the value compressor(1), this object MUST NOT be instantiated. This object contains the number of different packet sizes that may be used in the context.
.1.3.6.1.2.1.114.1.1.1.9,ROHC-RTP-MIB::rohcRtpContextSizesUsed,Unsigned32,read-only,,current,,The value of this object is only valid for decompressor contexts, i.e., if rohcInstanceType of the corresponding rohcContextEntry has the value decompressor(2). For compressor contexts where rohcInstanceType has the value compressor(1), this object MUST NOT be instantiated. This object contains the number of different packet sizes that are used in the context.
.1.3.6.1.2.1.114.1.1.1.10,ROHC-RTP-MIB::rohcRtpContextACKs,Counter32,read-only,,current,,The number of all positive feedbacks (ACK) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB.
.1.3.6.1.2.1.114.1.1.1.11,ROHC-RTP-MIB::rohcRtpContextNACKs,Counter32,read-only,,current,,The number of all dynamic negative feedbacks (ACK) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB.
.1.3.6.1.2.1.114.1.1.1.12,ROHC-RTP-MIB::rohcRtpContextSNACKs,Counter32,read-only,,current,,The number of all static negative feedbacks (ACK) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB.
.1.3.6.1.2.1.114.1.1.1.13,ROHC-RTP-MIB::rohcRtpContextNHPs,Counter32,read-only,,current,,This object is only applicable to contexts using the LLA profile. It contains the number of all no-header packets (NHP) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.14,ROHC-RTP-MIB::rohcRtpContextCSPs,Counter32,read-only,,current,,This object is only applicable to contexts using the LLA profile. It contains the number of all context synchronization packets (CSP) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.15,ROHC-RTP-MIB::rohcRtpContextCCPs,Counter32,read-only,,current,,This object is only applicable to contexts using the LLA profile. It contains the number of all context check packets (CCP) sent or received in this context, respectively. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.16,ROHC-RTP-MIB::rohcRtpContextPktsLostPhysical,Counter32,read-only,,current,,This object is only applicable to decompressor contexts using the LLA profile. It contains the number of physical packet losses on the link between compressor and decompressor, that have been indicated to the decompressor. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.1.1.17,ROHC-RTP-MIB::rohcRtpContextPktsLostPreLink,Counter32,read-only,,current,,This object is only applicable to decompressor contexts using the LLA profile. It contains the number of pre-link packet losses on the link between compressor and decompressor, that have been indicated to the decompressor. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. For checking ifCounterDiscontinuityTime, the interface index is required. It can be determined by reading the rohcChannelTable of the ROHC-MIB. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.2,ROHC-RTP-MIB::rohcRtpPacketSizeTable,,not-accessible,,current,,This table lists all allowed, preferred, and used packet sizes per compressor context and channel. Note, that the sizes table represents implementation parameters that are suggested by RFC 3095 and/or RFC 3242, but that are not mandatory.
.1.3.6.1.2.1.114.1.2.1,ROHC-RTP-MIB::rohcRtpPacketSizeEntry,,not-accessible,rohcChannelID:rohcContextCID:rohcRtpPacketSize,current,,An entry of a particular packet size.
.1.3.6.1.2.1.114.1.2.1.3,ROHC-RTP-MIB::rohcRtpPacketSize,Unsigned32,not-accessible,,current,,A packet size used as index.
.1.3.6.1.2.1.114.1.2.1.4,ROHC-RTP-MIB::rohcRtpPacketSizePreferred,INTEGER,read-only,,current,true(1):false(2),This object is only applicable to compressor contexts using the LLA profile. When retrieved, it will have the value true(1) if the packet size is preferred. Otherwise, its value will be false(2). The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.2.1.5,ROHC-RTP-MIB::rohcRtpPacketSizeUsed,INTEGER,read-only,,current,true(1):false(2),This object is only applicable to compressor contexts using the UDP, RTP, or ESP profile. When retrieved, it will have the value true(1) if the packet size is used. Otherwise, its value will be false(2). The value of this object is only valid for UDP, RTP, and ESP profiles, i.e., if the corresponding rohcProfile has a value of either 0x0001, 0x0002 or 0x0003. If the corresponding rohcProfile has a value other than 0x0001, 0x0002 or 0x0003, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.1.2.1.6,ROHC-RTP-MIB::rohcRtpPacketSizeRestrictedType,INTEGER,read-only,,current,nhpOnly(1):rhpOnly(2):noRestrictions(3),This object is only applicable to preferred packet sizes of compressor contexts using the LLA profile. When retrieved, it will indicate whether the packet size is preferred for NHP only, for RHP only, or for both of them. The value of this object is only valid for LLA profiles, i.e., if the corresponding rohcProfile has a value of 0x0005. If the corresponding rohcProfile has a value other than 0x0005, then this object MUST NOT be instantiated.
.1.3.6.1.2.1.114.2,ROHC-RTP-MIB::rohcRtpConformance,,,,,,
.1.3.6.1.2.1.114.2.1,ROHC-RTP-MIB::rohcRtpCompliances,,,,,,
.1.3.6.1.2.1.114.2.1.1,ROHC-RTP-MIB::rohcRtpCompliance,,,,,,The compliance statement for SNMP entities that implement the ROHC-RTP-MIB. Note that compliance with this compliance statement requires compliance with the rohcCompliance MODULE-COMPLIANCE statement of the ROHC-MIB and with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB (RFC2863).
.1.3.6.1.2.1.114.2.2,ROHC-RTP-MIB::rohcRtpGroups,,,,,,
.1.3.6.1.2.1.114.2.2.1,ROHC-RTP-MIB::rohcRtpContextGroup,,,,,,A collection of objects providing information about ROHC RTP compressors and decompressors.
.1.3.6.1.2.1.114.2.2.2,ROHC-RTP-MIB::rohcRtpPacketSizesGroup,,,,,,A collection of objects providing information about allowed and used packet sizes at a ROHC RTP compressor.
.1.3.6.1.2.1.114.2.2.3,ROHC-RTP-MIB::rohcRtpStatisticsGroup,,,,,,A collection of objects providing ROHC compressor and decompressor statistics.
.1.3.6.1.2.1.115,TRIP-TC-MIB::tripTC,,,,,,Initial version of TRIP (Telephony Routing Over IP) MIB Textual Conventions module used by other TRIP-related MIB Modules. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3872, see the RFC itself for full legal notices.
.1.3.6.1.2.1.116,TRIP-MIB::tripMIB,,,,,,The MIB module describing Telephony Routing over IP (TRIP). TRIP is a policy driven inter-administrative domain protocol for advertising the reachability of telephony destinations between location servers (LS), and for advertising attributes of the routes to those destinations. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3872, see the RFC itself for full legal notices.
.1.3.6.1.2.1.116.0,TRIP-MIB::tripMIBNotifications,,,,,,
.1.3.6.1.2.1.116.0.1,TRIP-MIB::tripConnectionEstablished,,,,,,The TRIP Connection Established event is generated when the TRIP finite state machine enters the ESTABLISHED state.
.1.3.6.1.2.1.116.0.2,TRIP-MIB::tripConnectionDropped,,,,,,The TRIP Connection Dropped event is generated when the TRIP finite state machine leaves the ESTABLISHED state.
.1.3.6.1.2.1.116.0.3,TRIP-MIB::tripFSM,,,,,,The trip FSM Event is generated when any error is detected by the TRIP Finite State Machine.
.1.3.6.1.2.1.116.0.4,TRIP-MIB::tripOpenMessageError,,,,,,Errors detected while processing the OPEN message.
.1.3.6.1.2.1.116.0.5,TRIP-MIB::tripUpdateMessageError,,,,,,Errors detected while processing the UPDATE message.
.1.3.6.1.2.1.116.0.6,TRIP-MIB::tripHoldTimerExpired,,,,,,The system does not receive successive messages within the period specified by the negotiated Hold Time.
.1.3.6.1.2.1.116.0.7,TRIP-MIB::tripConnectionCollision,,,,,,A pair of LSs tried to simultaneously to establish a transport connection to each other.
.1.3.6.1.2.1.116.0.8,TRIP-MIB::tripCease,,,,,,A TRIP peer MAY choose at any given time to close its TRIP connection by sending this notification message. However, the Cease notification message MUST NOT be used when a fatal error occurs.
.1.3.6.1.2.1.116.0.9,TRIP-MIB::tripNotificationErr,,,,,,Generated if there is an error detected in a TRIP notification message sent with another cause. Note that the TRIP notification referred to in this object is not an SNMP notification, it is a specific message described in the TRIP specification.
.1.3.6.1.2.1.116.1,TRIP-MIB::tripMIBObjects,,,,,,
.1.3.6.1.2.1.116.1.1,TRIP-MIB::tripCfgTable,,not-accessible,,current,,This table contains the common configuration objects applicable to all TRIP applications referenced by the applIndex. Each row represents those objects for a particular TRIP LS present in this system. The instances of TRIP LS's are uniquely identified by the applIndex. The objects in this table SHOULD be nonVolatile and survive a reboot.
.1.3.6.1.2.1.116.1.1.1,TRIP-MIB::tripCfgEntry,,not-accessible,applIndex,current,,A row of common configuration.
.1.3.6.1.2.1.116.1.1.1.1,TRIP-MIB::tripCfgProtocolVersion,Integer32,read-only,,current,,This object will reflect the version of TRIP supported by this system. It follows the same format as TRIP version information contained in the TRIP messages generated by this TRIP entity.
.1.3.6.1.2.1.116.1.1.1.2,TRIP-MIB::tripCfgItad,Unsigned32,read-write,,current,,The Internet Telephony Administrative domain (ITAD) of this LS.
.1.3.6.1.2.1.116.1.1.1.3,TRIP-MIB::tripCfgIdentifier,Unsigned32,read-only,,current,,The object that identifies this TRIP Client.
.1.3.6.1.2.1.116.1.1.1.4,TRIP-MIB::tripCfgAdminStatus,INTEGER,read-write,,current,up(1):down(2),The desired TRIP state. up(1) : Set the application to normal operation. down(2): Set the application to a state where it will not process TRIP messages. Setting this object should be reflected in tripCfgOperStatus. If an unknown error occurs tripCfgOperStatus will return unknown(0).
.1.3.6.1.2.1.116.1.1.1.5,TRIP-MIB::tripCfgOperStatus,INTEGER,read-only,,current,unknown(0):up(1):down(2):faulty(3),The current operational state of the TRIP protocol. unknown(0): The operating status of the application is unknown. up(1): The application is operating normally, and is ready to process (receive and issue) TRIP requests and responses. down(2): The application is currently not processing TRIP messages. This occurs if the TRIP application is in an initialization state or if tripCfgAdminStatus is set to down(2). faulty(3): The application is not operating normally due to a fault in the system. If tripCfgAdminStatus is down(2) then tripOperStatus SHOULD be down(2). If tripAdminStatus is changed to up(1) then tripOperStatus SHOULD change to up(1) if there is no fault that prevents the TRIP protocol from moving to the up(1) state.
.1.3.6.1.2.1.116.1.1.1.6,TRIP-MIB::tripCfgAddrIAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet Address of the tripAddr.
.1.3.6.1.2.1.116.1.1.1.7,TRIP-MIB::tripCfgAddr,OCTET,read-only,,current,,The network address of the local LS that the peer connects to. The type of address depends on the object tripCfgAddrIAddrType. The type of this address is determined by the value of the tripCfgAddrIAddrType object.
.1.3.6.1.2.1.116.1.1.1.8,TRIP-MIB::tripCfgPort,Unsigned32,read-write,,current,,The local tcp/udp port on the local LS that the peer connects to.
.1.3.6.1.2.1.116.1.1.1.9,TRIP-MIB::tripCfgMinItadOriginationInterval,Unsigned32,read-write,,current,,The minimum amount of time that MUST elapse between advertisement of the update message that reports changes within the LS's own ITAD.
.1.3.6.1.2.1.116.1.1.1.10,TRIP-MIB::tripCfgMinRouteAdvertisementInterval,Unsigned32,read-write,,current,,Specifies minimal interval between successive advertisements to a particular destination from an LS.
.1.3.6.1.2.1.116.1.1.1.11,TRIP-MIB::tripCfgMaxPurgeTime,Unsigned32,read-write,,current,,Indicates the interval that the LS MUST maintain routes marked as withdrawn in its database.
.1.3.6.1.2.1.116.1.1.1.12,TRIP-MIB::tripCfgDisableTime,Unsigned32,read-write,,current,,Indicates the interval that the TRIP module of the LS MUST be disabled while routes originated by this LS with high sequence numbers can be removed.
.1.3.6.1.2.1.116.1.1.1.13,TRIP-MIB::tripCfgSendReceiveMode,INTEGER,read-only,,current,sendReceive(1):sendOnly(2):receiveOnly(3),The operational mode of the TRIP entity running on this system.
.1.3.6.1.2.1.116.1.1.1.14,TRIP-MIB::tripCfgStorage,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.116.1.2,TRIP-MIB::tripRouteTypeTable,,not-accessible,,current,,The TRIP peer Route Type table contains one entry per supported protocol - address family pair. The objects in this table are volatile and are refreshed after a reboot.
.1.3.6.1.2.1.116.1.2.1,TRIP-MIB::tripRouteTypeEntry,,not-accessible,applIndex:tripRouteTypeAddrInetType:tripRouteTypeAddr:tripRouteTypePort:tripRouteTypeProtocolId:tripRouteTypeAddrFamilyId,current,,An entry containing information about the route type that a particular TRIP entity supports. Each entry represents information about either the local or a remote LS peer. The object tripRouteTypePeer is used to distinguish this. In the case of a local LS, the address/port information will reflect the values configured in tripCfgTable. In the case of a remote peer, the address/port information will reflect the values of an entry in the tripPeerTable. Implementation need to be aware that if the size of tripRouteTypeAddr exceeds 111 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3.
.1.3.6.1.2.1.116.1.2.1.1,TRIP-MIB::tripRouteTypeAddrInetType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet Address of the tripRouteTypeAddr.
.1.3.6.1.2.1.116.1.2.1.2,TRIP-MIB::tripRouteTypeAddr,OCTET,not-accessible,,current,,The network address of this entry's TRIP peer LS. The type of this address is determined by the value of the tripRouteTypeAddrInetType object.
.1.3.6.1.2.1.116.1.2.1.3,TRIP-MIB::tripRouteTypePort,Unsigned32,not-accessible,,current,,The port for the TCP connection between this and an associated TRIP peer.
.1.3.6.1.2.1.116.1.2.1.4,TRIP-MIB::tripRouteTypeProtocolId,INTEGER,not-accessible,,current,sip(1):q931(2):ras(3):annexG(4):other(255),The object identifier of a protocol that the associated peer is using.
.1.3.6.1.2.1.116.1.2.1.5,TRIP-MIB::tripRouteTypeAddrFamilyId,INTEGER,not-accessible,,current,decimal(1):pentadecimal(2):e164(3):other(255),The object identifier of an address family that the associated peer belongs to.
.1.3.6.1.2.1.116.1.2.1.6,TRIP-MIB::tripRouteTypePeer,INTEGER,read-only,,current,local(1):remote(2),This object identifies whether this entry is associated with a 'local' or 'remote' LS peer.
.1.3.6.1.2.1.116.1.3,TRIP-MIB::tripSupportedCommunityTable,,not-accessible,,current,,The list of TRIP communities that this LS supports. A TRIP community is a group of destinations that share common properties. The TRIP Supported Communities entry is used to group destinations so that the routing decision can be based on the identity of the group.
.1.3.6.1.2.1.116.1.3.1,TRIP-MIB::tripSupportedCommunityEntry,,not-accessible,applIndex:tripSupportedCommunityId,current,,Entry containing information about a community. A TRIP community is a group of destinations that share some common property. This attribute is used so that routing decisions can be based on the identity of the group.
.1.3.6.1.2.1.116.1.3.1.1,TRIP-MIB::tripSupportedCommunityId,Unsigned32,not-accessible,,current,,The identifier of the supported Community.
.1.3.6.1.2.1.116.1.3.1.2,TRIP-MIB::tripSupportedCommunityItad,Unsigned32,read-create,,current,,The ITAD of the community.
.1.3.6.1.2.1.116.1.3.1.3,TRIP-MIB::tripSupportedCommunityStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write- access to any columnar objects in the row. It is not a requirement that this storage be non volatile.
.1.3.6.1.2.1.116.1.3.1.4,TRIP-MIB::tripSupportedCommunityRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status of the entry. This object is REQUIRED to create or delete rows by a manager. A value for tripSupportedCommunityItad MUST be set for row creation to be successful. If the instance already exists for a particular applIndex, the row create operation will fail. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.116.1.4,TRIP-MIB::tripPeerTable,,not-accessible,,current,,The TRIP peer table. This table contains one entry per TRIP peer, and information about the connection with the peer.
.1.3.6.1.2.1.116.1.4.1,TRIP-MIB::tripPeerEntry,,not-accessible,applIndex:tripPeerRemoteAddrInetType:tripPeerRemoteAddr:tripPeerRemotePort,current,,Entry containing information about the connection with a TRIP peer. Implementation need to be aware that if the size of tripPeerRemoteAddr exceeds 113 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be accessed using SNMPv1, SNMPv2c, or snmpv3.
.1.3.6.1.2.1.116.1.4.1.1,TRIP-MIB::tripPeerRemoteAddrInetType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet Address of the tripPeerRemoteAddr.
.1.3.6.1.2.1.116.1.4.1.2,TRIP-MIB::tripPeerRemoteAddr,OCTET,not-accessible,,current,,The IP address of this entry's TRIP peer LS. The type of this address is determined by the value of the tripPeerRemoteAddrInetType object.
.1.3.6.1.2.1.116.1.4.1.3,TRIP-MIB::tripPeerRemotePort,Unsigned32,not-accessible,,current,,The remote port for the TCP connection between the TRIP peers.
.1.3.6.1.2.1.116.1.4.1.4,TRIP-MIB::tripPeerIdentifier,Unsigned32,read-only,,current,,TRIP identifier of the peer.
.1.3.6.1.2.1.116.1.4.1.5,TRIP-MIB::tripPeerState,INTEGER,read-only,,current,idle(1):connect(2):active(3):openSent(4):openConfirm(5):established(6),TRIP Peer Finite State Machine state. idle(1) : The initial state. Local LS refuses all incoming connections. No application resources are allocated to processing information about the remote peer. connect(2) : Local LS waiting for a transport protocol connection to be completed to the peer, and is listening for inbound transport connections from the peer. active(3) : Local LS is listening for an inbound connection from the peer, but is not in the process of initiating a connection to the remote peer. openSent(4) : Local LS has sent an OPEN message to its peer and is waiting for an OPEN message from the remote peer. openConfirm(5): Local LS has sent an OPEN message to the remote peer, received an OPEN message from the remote peer, and sent a KEEPALIVE message in response to the OPEN. The local LS is now waiting for a KEEPALIVE message or a NOTIFICATION message in response to its OPEN message. established(6): LS can exchange UPDATE, NOTIFICATION, and KEEPALIVE messages with its peer.
.1.3.6.1.2.1.116.1.4.1.6,TRIP-MIB::tripPeerAdminStatus,INTEGER,read-create,,current,up(1):down(2),This object is used to affect the TRIP connection state. up(1) : Allow a connection with the peer LS. down(2) : disconnect the connection from the peer LS and do not allow any further connections to this peer. If this value is set to down(2) then tripPeerState will have the value of idle(1).
.1.3.6.1.2.1.116.1.4.1.7,TRIP-MIB::tripPeerNegotiatedVersion,Integer32,read-only,,current,,The negotiated version of TRIP running between this local entity and this peer.
.1.3.6.1.2.1.116.1.4.1.8,TRIP-MIB::tripPeerSendReceiveMode,INTEGER,read-only,,current,sendReceive(1):sendOnly(2):receiveOnly(3),The operational mode of this peer.
.1.3.6.1.2.1.116.1.4.1.9,TRIP-MIB::tripPeerRemoteItad,Unsigned32,read-only,,current,,The Internet Telephony Administrative domain of this peer.
.1.3.6.1.2.1.116.1.4.1.10,TRIP-MIB::tripPeerConnectRetryInterval,Unsigned32,read-create,,current,,Specifies the initial amount of time that will elapse between connection retry. This value SHOULD double after each attempt up to the value of tripPeerMaxRetryInterval. This value MUST always be less than or equal to the value of tripPeerMaxRetryInterval. Attempts to set this value higher than the max retry will not be allowed.
.1.3.6.1.2.1.116.1.4.1.11,TRIP-MIB::tripPeerMaxRetryInterval,Unsigned32,read-create,,current,,Specifies the maximum amount of time that will elapse between connection retries. Once the value of tripPeerConnectRetryInterval has reached this value, no more retries will be attempted. Attempts to set this value lower than the retry interval SHOULD not be allowed.
.1.3.6.1.2.1.116.1.4.1.12,TRIP-MIB::tripPeerHoldTime,Unsigned32,read-only,,current,,The time interval in seconds for the hold timer that is established with the peer. The value of this object is the smaller of the values in tripPeerHoldTimeConfigured and the hold time received in the open message.
.1.3.6.1.2.1.116.1.4.1.13,TRIP-MIB::tripPeerKeepAlive,Unsigned32,read-only,,current,,Specifies the amount of time that MUST elapse between keep alive messages. This value is negotiated with the remote when a connection is established.
.1.3.6.1.2.1.116.1.4.1.14,TRIP-MIB::tripPeerHoldTimeConfigured,Unsigned32,read-create,,current,,Specifies the maximum time that MAY elapse between the receipt of successive keepalive or update message. A value of 0 means that keepalive or update messages will not be sent.
.1.3.6.1.2.1.116.1.4.1.15,TRIP-MIB::tripPeerKeepAliveConfigured,Unsigned32,read-create,,current,,Specifies the amount of time that MUST elapse between keep alive messages.
.1.3.6.1.2.1.116.1.4.1.16,TRIP-MIB::tripPeerMaxPurgeTime,Unsigned32,read-create,,current,,Indicates the interval that the LS MUST maintain routes marked as withdrawn in its database.
.1.3.6.1.2.1.116.1.4.1.17,TRIP-MIB::tripPeerDisableTime,Unsigned32,read-create,,current,,Indicate the interval that the TRIP module of the remote peer LS MUST be disabled while routes originated by the local LS with high sequence numbers can be removed.
.1.3.6.1.2.1.116.1.4.1.18,TRIP-MIB::tripPeerLearned,INTEGER,read-only,,current,true(1):false(2),Indicates whether this entry was learned or configured.
.1.3.6.1.2.1.116.1.4.1.19,TRIP-MIB::tripPeerStorage,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write- access to any columnar objects in the row. It is not a requirement that this storage be non volatile.
.1.3.6.1.2.1.116.1.4.1.20,TRIP-MIB::tripPeerRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status of the entry. This object is REQUIRED to create or delete rows remotely by a manager. If the instance already exists for a particular applIndex, the row create operation will fail. The value of this object has no effect on whether other objects in this conceptual row can be modified. Entries in this table can be learned by the TRIP application, or provisioned through this table.
.1.3.6.1.2.1.116.1.5,TRIP-MIB::tripPeerStatisticsTable,,not-accessible,,current,,The TRIP peer stats table. This table contains one entry per remote TRIP peer, and statistics related to the connection with the remote peer. The objects in this table are volatile.
.1.3.6.1.2.1.116.1.5.1,TRIP-MIB::tripPeerStatisticsEntry,,not-accessible,,current,,Entry containing information about the connection with a TRIP peer.
.1.3.6.1.2.1.116.1.5.1.1,TRIP-MIB::tripPeerInUpdates,Counter32,read-only,,current,,The number of TRIP update messages received from this remote peer since the last restart of this location server.
.1.3.6.1.2.1.116.1.5.1.2,TRIP-MIB::tripPeerOutUpdates,Counter32,read-only,,current,,The number of TRIP update messages sent to this remote peer since the last restart of this LS.
.1.3.6.1.2.1.116.1.5.1.3,TRIP-MIB::tripPeerInTotalMessages,Counter32,read-only,,current,,The total number of TRIP messages received from the remote peer on this connection since the last restart of this LS.
.1.3.6.1.2.1.116.1.5.1.4,TRIP-MIB::tripPeerOutTotalMessages,Counter32,read-only,,current,,The total number of outgoing TRIP messages sent to the remote peer since the last restart of this LS.
.1.3.6.1.2.1.116.1.5.1.5,TRIP-MIB::tripPeerFsmEstablishedTransitions,Counter32,read-only,,current,,The number of times the remote peer has transitioned into the established state since the last restart of this LS.
.1.3.6.1.2.1.116.1.5.1.6,TRIP-MIB::tripPeerFsmEstablishedTime,OCTET,read-only,,current,,Indicates the time and date that this remote peer entered the 'established' state.
.1.3.6.1.2.1.116.1.5.1.7,TRIP-MIB::tripPeerInUpdateElapsedTime,INTEGER,read-only,,current,,Elapsed time in hundredths of seconds since the last TRIP update message was received from this remote peer.
.1.3.6.1.2.1.116.1.5.1.8,TRIP-MIB::tripPeerStateChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime when the last state change of tripPeerState took place.
.1.3.6.1.2.1.116.1.6,TRIP-MIB::tripRouteTable,,not-accessible,,current,,The TRIP route table containing information about reachable routes that are to be added to service by the receiving LS. The objects in this table are volatile and are refreshed when this LS rediscovers its route table.
.1.3.6.1.2.1.116.1.6.1,TRIP-MIB::tripRouteEntry,,not-accessible,applIndex:tripRouteAppProtocol:tripRouteAddressFamily:tripRouteAddress:tripRoutePeer,current,,Information about a route to a called destination.
.1.3.6.1.2.1.116.1.6.1.1,TRIP-MIB::tripRouteAppProtocol,INTEGER,not-accessible,,current,sip(1):q931(2):ras(3):annexG(4):other(255),The protocol for which this entry of the routing table is maintained.
.1.3.6.1.2.1.116.1.6.1.2,TRIP-MIB::tripRouteAddressFamily,INTEGER,not-accessible,,current,decimal(1):pentadecimal(2):e164(3):other(255),Specifies the type of address for the destination route.
.1.3.6.1.2.1.116.1.6.1.3,TRIP-MIB::tripRouteAddress,OCTET,not-accessible,,current,,This is the address (prefix) of the family type given by Address Family of the destination. It is the prefix of addresses reachable from this gateway via the next hop server. The SIZE value of 105 has been assigned due to the sub identifier of object types length limitation as defined in SMIv2.
.1.3.6.1.2.1.116.1.6.1.4,TRIP-MIB::tripRoutePeer,Unsigned32,not-accessible,,current,,The identifier of the peer where the route information was learned.
.1.3.6.1.2.1.116.1.6.1.5,TRIP-MIB::tripRouteTRIBMask,BITS,read-only,,current,adjTribIns(0):extTrib(1):locTrib(2):adjTribOut(3),Indicates which Telephony Routing Information Base (TRIB) this entry belongs to. This is a bit-map of possible types. If the bit has a value of 1, then the entry is a member of the corresponding TRIB type. If the bit has a value of 0 then the entry is not a member of the TRIP type. The various bit positions are: 0 adjTribIns The entry is of type adj-TRIBs-ins, stores routing information that has been learned from inbound UPDATE messages. 1 extTrib The entry is of type ext-TRIB, the best route for a given destination. 2 locTrib The entry is of type loc-TRIB contains the local TRIP routing information that the LS has selected. 3 adjTribOut The entry is of type adj-TRIBs-out, stores the information that the local LS has selected for advertisement to its external peers.
.1.3.6.1.2.1.116.1.6.1.6,TRIP-MIB::tripRouteAddressSequenceNumber,Unsigned32,read-only,,current,,Indicates the version of the destination route originated by the LS identified by tripRouteAddressOriginatorId intra-domain attribute.
.1.3.6.1.2.1.116.1.6.1.7,TRIP-MIB::tripRouteAddressOriginatorId,Unsigned32,read-only,,current,,This is an intra-domain attribute indicating the internal LS that originated the route into the ITAD.
.1.3.6.1.2.1.116.1.6.1.8,TRIP-MIB::tripRouteNextHopServerIAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet Address of the tripRouteNextHopServer.
.1.3.6.1.2.1.116.1.6.1.9,TRIP-MIB::tripRouteNextHopServer,OCTET,read-only,,current,,Indicates the next hop that messages of a given protocol destined for tripRouteAddress SHOULD be sent to. The type of this address is determined by the value of the tripRouteNextHopServerIAddrType object.
.1.3.6.1.2.1.116.1.6.1.10,TRIP-MIB::tripRouteNextHopServerPort,Unsigned32,read-only,,current,,The port of the next hop server that this route will use.
.1.3.6.1.2.1.116.1.6.1.11,TRIP-MIB::tripRouteNextHopServerItad,Unsigned32,read-only,,current,,Indicates the domain of the next hop.
.1.3.6.1.2.1.116.1.6.1.12,TRIP-MIB::tripRouteMultiExitDisc,Unsigned32,read-only,,current,,The Multiple Exit Discriminator allows an LS to discriminate between, and indicate preference for, otherwise similar routes to a neighbouring domain. A higher value represents a more preferred routing object.
.1.3.6.1.2.1.116.1.6.1.13,TRIP-MIB::tripRouteLocalPref,Unsigned32,read-only,,current,,Indicated the local LS's degree of preference for an advertised route destination.
.1.3.6.1.2.1.116.1.6.1.14,TRIP-MIB::tripRouteAdvertisementPath,OCTET,read-only,,current,,Identifies the sequence of domains through which this advertisement has passed. This object is probably best represented as sequence of TripItads. For SMI compatibility, though, it is represented as an OCTET STRING. This object is a sequence of ITADs where each set of 4 octets corresponds to a TRIP ITAD in network byte order.
.1.3.6.1.2.1.116.1.6.1.15,TRIP-MIB::tripRouteRoutedPath,OCTET,read-only,,current,,Identifies the ITADs through which messages sent using this route would pass. These are a subset of tripRouteAdvertisementPath. This object is probably best represented as sequence of TripItads. For SMI compatibility, though, it is represented as OCTET STRING. This object is a sequence of ITADs where each set of 4 octets corresponds to a TRIP ITAD in network byte order.
.1.3.6.1.2.1.116.1.6.1.16,TRIP-MIB::tripRouteAtomicAggregate,INTEGER,read-only,,current,true(1):false(2),Indicates that a route MAY traverse domains not listed in tripRouteRoutedPath. If an LS selects the less specific route from a set of overlapping routes, then this value returns TRUE.
.1.3.6.1.2.1.116.1.6.1.17,TRIP-MIB::tripRouteUnknown,OCTET,read-only,,current,,This object contains one or more attributes that were not understood, and because they were transitive, were dropped during aggregation. They take the format of a triple <attribute type, attribute length, attribute value>, of variable length. If no attributes were dropped, this returns an OCTET STRING of size 0.
.1.3.6.1.2.1.116.1.6.1.18,TRIP-MIB::tripRouteWithdrawn,INTEGER,read-only,,current,true(1):false(2),Indicates if this route is to be removed from service by the receiving LS.
.1.3.6.1.2.1.116.1.6.1.19,TRIP-MIB::tripRouteConverted,INTEGER,read-only,,current,true(1):false(2),Indicates if this route has been converted to a different application protocol than it had originally.
.1.3.6.1.2.1.116.1.6.1.20,TRIP-MIB::tripRouteReceivedTime,TimeTicks,read-only,,current,,The value of sysUpTime when this route was received.
.1.3.6.1.2.1.116.1.7,TRIP-MIB::tripRouteCommunityTable,,not-accessible,,current,,A table containing a list of TRIP communities associated with a route. Each instance of tripRouteTypeEntry that has the tripRouteTypePeer object set to remote(2) has an instance in the tripRouteTable as a parent. The objects in this table are volatile and are refreshed after a reboot.
.1.3.6.1.2.1.116.1.7.1,TRIP-MIB::tripRouteCommunityEntry,,not-accessible,applIndex:tripRouteAppProtocol:tripRouteAddressFamily:tripRouteAddress:tripRoutePeer:tripRouteCommunityId,current,,Information about communities associated with a route. An entry with a tripRouteAddress of 00 and a tripRoutePeer of 0 refers to the local LS.
.1.3.6.1.2.1.116.1.7.1.1,TRIP-MIB::tripRouteCommunityId,Unsigned32,not-accessible,,current,,The community identifier.
.1.3.6.1.2.1.116.1.7.1.2,TRIP-MIB::tripRouteCommunityItad,Unsigned32,read-only,,current,,The ITAD associated with this community.
.1.3.6.1.2.1.116.1.8,TRIP-MIB::tripItadTopologyTable,,not-accessible,,current,,The sequence of link connections between peers within an ITAD. The objects in this table are volatile and are refreshed after a reboot.
.1.3.6.1.2.1.116.1.8.1,TRIP-MIB::tripItadTopologyEntry,,not-accessible,applIndex:tripItadTopologyOrigId,current,,Information about a peer of the LS identified by tripItadTopologyOrigId.
.1.3.6.1.2.1.116.1.8.1.1,TRIP-MIB::tripItadTopologyOrigId,Unsigned32,not-accessible,,current,,Indicates the internal LS that originated the ITAD topology information into the ITAD.
.1.3.6.1.2.1.116.1.8.1.2,TRIP-MIB::tripItadTopologySeqNum,Unsigned32,read-only,,current,,Indicates the version of the ITAD topology originated by the LS identified by tripItadTopologyOrigId.
.1.3.6.1.2.1.116.1.9,TRIP-MIB::tripItadTopologyIdTable,,not-accessible,,current,,The list of other LS's within the ITAD domain that the LS identified by tripItadTopologyOrigId is currently peering. Each instance of tripItadTopologyIdEntry has an instance in the tripItadTopologyTable as a parent. The objects in this table are volatile and are refreshed after a reboot.
.1.3.6.1.2.1.116.1.9.1,TRIP-MIB::tripItadTopologyIdEntry,,not-accessible,applIndex:tripItadTopologyOrigId:tripItadTopologyId,current,,Information about a peer to the LS identified by tripItadTopologyOrigId.
.1.3.6.1.2.1.116.1.9.1.1,TRIP-MIB::tripItadTopologyId,Unsigned32,read-only,,current,,The index into this entry. Indicates the other location servers within the ITAD domain that this LS identified by tripItadTopologyOrigId is currently peering.
.1.3.6.1.2.1.116.2,TRIP-MIB::tripMIBConformance,,,,,,
.1.3.6.1.2.1.116.2.1,TRIP-MIB::tripMIBCompliances,,,,,,
.1.3.6.1.2.1.116.2.1.1,TRIP-MIB::tripMIBFullCompliance,,,,,,The compliance statement for TRIP entities that implement this MIB module in read-write mode, such that it can be used for both monitoring and configuring the TRIP entity. There is one INDEX object that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there is a compliance requirement, expressed in OBJECT clause form in this description: -- OBJECT tripRouteTypeAddrInetType -- SYNTAX InetAddressType (ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)) -- DESCRIPTION -- This MIB requires support for global and -- non-global ipv4 and ipv6 addresses. -- -- OBJECT tripRouteTypeAddr -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for global and -- non-global IPv4 and IPv6 addresses. -- 
.1.3.6.1.2.1.116.2.1.2,TRIP-MIB::tripMIBReadOnlyCompliance,,,,,,The compliance statement for TRIP entities that implement this MIB module in read only mode. Such TRIP entities can then only be monitored, but not be configured via this MIB module. In read-only mode, the manager will not be able to add, remove or modify rows to any table, however the TRIP application may modify, remove or add rows to a table. There is one INDEX object that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there is a compliance requirement, expressed in OBJECT clause form in this description: -- OBJECT tripRouteTypeAddrInetType -- SYNTAX InetAddressType (ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)) -- DESCRIPTION -- This MIB requires support for global and -- non-global ipv4 and ipv6 addresses. -- -- OBJECT tripRouteTypeAddr -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) -- DESCRIPTION -- This MIB requires support for global and -- non-global IPv4 and IPv6 addresses. -- 
.1.3.6.1.2.1.116.2.2,TRIP-MIB::tripMIBGroups,,,,,,
.1.3.6.1.2.1.116.2.2.1,TRIP-MIB::tripConfigGroup,,,,,,The global objects for configuring trip.
.1.3.6.1.2.1.116.2.2.2,TRIP-MIB::tripPeerTableConfigGroup,,,,,,The global objects for configuring the TRIP peer table.
.1.3.6.1.2.1.116.2.2.3,TRIP-MIB::tripPeerTableStatsGroup,,,,,,The global statistics the TRIP peer table.
.1.3.6.1.2.1.116.2.2.4,TRIP-MIB::tripRouteGroup,,,,,,The global objects for configuring route attribute.
.1.3.6.1.2.1.116.2.2.5,TRIP-MIB::tripItadTopologyGroup,,,,,,The objects that define the TRIP ITAD topology.
.1.3.6.1.2.1.116.2.2.6,TRIP-MIB::tripNotificationGroup,,,,,,A collection of notifications defined for TRIP.
.1.3.6.1.2.1.116.2.2.7,TRIP-MIB::tripNotifObjectGroup,,,,,,The collection of objects that specify information for TRIP notifications.
.1.3.6.1.2.1.116.3,TRIP-MIB::tripMIBNotifObjects,,,,,,
.1.3.6.1.2.1.116.3.1,TRIP-MIB::tripNotifApplIndex,Integer32,accessible-for-notify,,current,,This object contains the application Index. It is used to bind this notification with a specific instance of TRIP entity.
.1.3.6.1.2.1.116.3.2,TRIP-MIB::tripNotifPeerAddrInetType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet Address of the tripNotifPeerAddr.
.1.3.6.1.2.1.116.3.3,TRIP-MIB::tripNotifPeerAddr,OCTET,accessible-for-notify,,current,,The IP address of this entry's TRIP peer LS. This object contains the value of tripPeerRemoteAddr. The type of this address is determined by the value of the tripNotifPeerAddrInetType object.
.1.3.6.1.2.1.116.3.4,TRIP-MIB::tripNotifPeerErrCode,INTEGER,accessible-for-notify,,current,messageHeader(1):openMessage(2):updateMessage(3):holdTimerExpired(4):finiteStateMachine(5):cease(6):tripNotification(7),Notification message of TRIP error. The meaning of this value is applicable to the following functions: messageHeader(1) - All errors detected while processing the TRIP message header. openMessage(2) - All errors detected while processing the OPEN message. updateMessage(3) - All errors detected while processing the UPDATE message. holdTimerExpired(4) - A notification generated when the hold timer expires. finiteStateMachine(5) - All errors detected by the TRIP Finite State Machine. cease(6) - Any fatal error condition that the rest of the values do not cover. tripNotification(7) - Any error encountered while sending a notification message.
.1.3.6.1.2.1.116.3.5,TRIP-MIB::tripNotifPeerErrSubcode,Unsigned32,accessible-for-notify,,current,,The sub error code associated with error code. The meaning of this value is dependent on the value of tripNotifPeerErrCode. Message Header (1) Error Subcodes: 1 - Bad Message Length. 2 - Bad Message Type. OPEN Message (2) Error Subcodes: 1 - Unsupported Version Number. 2 - Bad Peer ITAD. 3 - Bad TRIP Identifier. 4 - Unsupported Optional Parameter. 5 - Unacceptable Hold Time. 6 - Unsupported Capability. 7 - Capability Mismatch. UPDATE Message (3) Error Subcodes: 1 - Malformed Attribute List. 2 - Unrecognized Well-known Attribute. 3 - Missing Well-known Mandatory Attribute. 4 - Attribute Flags Error. 5 - Attribute Length Error. 6 - Invalid Attribute.
.1.3.6.1.2.1.117,ARC-MIB::arcMibModule,,,,,,The MIB module describes the objects for controlling a resource in reporting alarm conditions that it detects. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3878; see the RFC itself for full legal notices.
.1.3.6.1.2.1.117.1,ARC-MIB::arcTimeIntervals,,,,,,
.1.3.6.1.2.1.117.1.1,ARC-MIB::arcTITimeInterval,Unsigned32,read-write,,current,,This variable indicates the time interval used for the nalmTI state, in units of second. It is a pre-defined length of time in which the resource will stay in the nalmTI state before transition into the alm state. Instances of this object SHOULD persist across agent restarts.
.1.3.6.1.2.1.117.1.2,ARC-MIB::arcCDTimeInterval,Unsigned32,read-write,,current,,This variable indicates the time interval used for the nalmQICD state, in units of second. It is a pre-defined length of time in which the resource will stay in the nalmQICD state before transition into the alm state after it is problem-free. Instances of this object SHOULD persist across agent restarts.
.1.3.6.1.2.1.117.2,ARC-MIB::arcObjects,,,,,,
.1.3.6.1.2.1.117.2.1,ARC-MIB::arcTable,,not-accessible,,current,,A table of Alarm Reporting Control (ARC) settings on the system. Alarm Reporting Control is a feature that provides an automatic in-service provisioning capability. Alarm reporting is turned off on a per-resource basis for a selective set of potential alarm conditions to allow sufficient time for customer testing and other maintenance activities in an 'alarm free' state. Once a resource is ready for service, alarm reporting is automatically or manually turned on. Functional description and requirements of Alarm Reporting Control are defined in ITU-T Recommendation M.3100 Amendment 3 [M.3100 Amd3].
.1.3.6.1.2.1.117.2.1.1,ARC-MIB::arcEntry,,not-accessible,arcIndex:arcAlarmType:arcNotificationId,current,,A conceptual row that contains information about an ARC setting of a resource in the system. Implementation need to be aware that if the total size of arcIndex and arcNotificationId exceeds 114 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be access using SNMPv1, SNMPv2c, or snmpv3.
.1.3.6.1.2.1.117.2.1.1.1,ARC-MIB::arcIndex,OBJECT,not-accessible,,current,,This object uniquely identifies a resource, which is under the arcState's control for the associated arcAlarmType. For example, if the resource is an interface, this object will point to an instance of interface, e.g., ifIndex.1.
.1.3.6.1.2.1.117.2.1.1.2,ARC-MIB::arcAlarmType,INTEGER,not-accessible,,current,,This object identifies the alarm condition type controlled by the arcState. It specifies the value 0 or a value of IANAItuProbableCause that is applicable to the resource. IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC module in the Alarm MIB document. The value of zero (0) implies any probable causes that are applicable to the resource. Usually, the applicable probable causes of a resource are specified in the resource-specific mib.
.1.3.6.1.2.1.117.2.1.1.3,ARC-MIB::arcNotificationId,OBJECT,not-accessible,,current,,This object identifies the type of notification to be suppressed. The notification type identified should be the one normally used by the resource for reporting its alarms. When the value of 0.0 is specified for this object, it implies all applicable notification types.
.1.3.6.1.2.1.117.2.1.1.4,ARC-MIB::arcState,INTEGER,read-create,,current,nalm(1):nalmQI(2):nalmTI(3):nalmQICD(4),Defined in M.3100 Amendment 3 [M.3100 Amd3], there are five ARC states: alm, nalm, nalmQI, nalmQICD, and nalmTI. alm: Alarm reporting is turned on (i.e., is allowed). nalm: Alarm reporting is turned off (i.e., not allowed). nalmQI: nalm - Qualified Inhibit. Alarm reporting is turned off until the managed entity is qualified problem-free for an optional persistence interval. Problem-free means that the condition corresponding to the specified alarm type is cleared. nalmQICD: nalmQI - Count down. This is a substate of nalmQI and performs the persistence timing countdown function after the managed entity is qualified problem-free. nalmTI: nalm - Timed Inhibit. Alarm reporting is turned off for a specified time interval. alm may transition to nalm, nalmQI or nalmTI by management request. nalm may transition to alm, nalmQI or nalmTI by management request. nalmQI may transition to nalm or alm by management request. nalmQI may transition to alm automatically if qualified problem-free (if nalmQICD is not supported) or if the CD timer expired (if nalmQICD is supported) nalmTI may transition to alm or nalm by management request. nalmTI may transition to alm automatically if the TI timer expired. Further details of ARC state transitions are defined in Figure 3 of M.3100 Amd3 [M.3100 Amd3]. According to the requirements in M.3100 Amd3, a resource supporting the ARC feature shall support the alm state and at least one of the nalm, nalmTI, and nalmQI states. The nalmQICD state is an optional substate of nalmQI. The arcState object controls the alarm reporting state of a resource. Note that the state alm (alarm reporting is allowed) is not listed in the enumeration of the value of this object. However, this state is implicitly supported by the mib. Once a resource enters the normal reporting mode (i.e., in the alm state) for the specified alarm type, the corresponding row will be automatically deleted from the arc table. Also the manual setting of arcState to alm can be achieved through setting the RowStatus object to 'destroy'. The nalamQICD state is a transitional state from nalmQI to alm. It is optional depending on the resource type and the implementation of the resource. If it is supported, before the state transitions from nalmQI to alm, a count down period is activated for a duration set by the object arcNalmCDTimeInterval. When the time is up, the arcState transitions to alm.
.1.3.6.1.2.1.117.2.1.1.5,ARC-MIB::arcNalmTimeRemaining,Unsigned32,read-create,,current,,This variable indicates the time remaining in the nalmTI state or the nalmQICD state, in units of second. At the moment the resource enters the nalmTI state, this variable will have the initial value equal to the value of arcNalmTITimeInterval and then starts decrementing as time goes by. Similarly at the moment the resource enters the nalmQICD state, this variable will have the initial value equal to the value of arcNalmCDTimeInterval and then starts decrementing as time goes by. This variable is read-create and thus will allow the manager to write (extend or shorten), as needed, the remaining time when the resource is in the nalmTI or nalmQICD state. If this variable is supported and the resource is currently not in the nalmTI nor nalmQICD state, the value of this variable shall equal to zero.
.1.3.6.1.2.1.117.2.1.1.6,ARC-MIB::arcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This columnar object is used for creating and deleting a conceptual row of the arcTable. It is used to create and delete an arc setting. Setting RowStatus to createAndGo or createAndWait implies creating a new ARC setting for the specified resource and alarm type. Setting RowStatus to destroy implies removing the ARC setting and thus has the effect of resuming normal reporting behaviour of the resource for the alarm type. Only the objects arcState, arcNalmTimeRemaining, and arcRowStatus can be updated when a row is active. All the objects, except arcNalmTimeRemaining, must be set before the row can be activated.
.1.3.6.1.2.1.117.2.1.1.7,ARC-MIB::arcStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' must allow write-access at a minimum to arcState. Note that arcState must allow change by management request. Therefore, no row can be created with 'readOnly'. If a set operation tries to set the value to 'readOnly', then an 'inconsistentValue' error must be returned.
.1.3.6.1.2.1.117.3,ARC-MIB::arcConformance,,,,,,
.1.3.6.1.2.1.117.3.1,ARC-MIB::arcCompliances,,,,,,
.1.3.6.1.2.1.117.3.1.1,ARC-MIB::arcCompliance,,,,,,The compliance statement for systems supporting the ARC MIB module.
.1.3.6.1.2.1.117.3.2,ARC-MIB::arcGroups,,,,,,
.1.3.6.1.2.1.117.3.2.1,ARC-MIB::arcSettingGroup,,,,,,A collection of objects applicable to basic ARC setting.
.1.3.6.1.2.1.117.3.2.2,ARC-MIB::arcTIGroup,,,,,,A collection of objects applicable to ARC setting that support the Time Inhibit (TI) function.
.1.3.6.1.2.1.117.3.2.3,ARC-MIB::arcQICDGroup,,,,,,A collection of objects applicable to ARC setting that support the Quality Inhibit (QI) Count Down (CD) function.
.1.3.6.1.2.1.118,ALARM-MIB::alarmMIB,,,,,,The MIB module describes a generic solution to model alarms and to store the current list of active alarms. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.118.0,ALARM-MIB::alarmNotifications,,,,,,
.1.3.6.1.2.1.118.0.2,ALARM-MIB::alarmActiveState,,,,,,An instance of the alarm indicated by alarmActiveModelPointer has been raised against the entity indicated by alarmActiveResourceId. The agent must throttle the generation of consecutive alarmActiveState traps so that there is at least a two-second gap between traps of this type against the same alarmActiveModelPointer and alarmActiveResourceId. When traps are throttled, they are dropped, not queued for sending at a future time. A management application should periodically check the value of alarmActiveLastChanged to detect any missed alarmActiveState notification-events, e.g., due to throttling or transmission loss.
.1.3.6.1.2.1.118.0.3,ALARM-MIB::alarmClearState,,,,,,An instance of the alarm indicated by alarmActiveModelPointer has been cleared against the entity indicated by alarmActiveResourceId. The agent must throttle the generation of consecutive alarmActiveClear traps so that there is at least a two-second gap between traps of this type against the same alarmActiveModelPointer and alarmActiveResourceId. When traps are throttled, they are dropped, not queued for sending at a future time. A management application should periodically check the value of alarmActiveLastChanged to detect any missed alarmClearState notification-events, e.g., due to throttling or transmission loss.
.1.3.6.1.2.1.118.1,ALARM-MIB::alarmObjects,,,,,,
.1.3.6.1.2.1.118.1.1,ALARM-MIB::alarmModel,,,,,,
.1.3.6.1.2.1.118.1.1.1,ALARM-MIB::alarmModelLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last creation, deletion or modification of an entry in the alarmModelTable. If the number and content of entries has been unchanged since the last re-initialization of the local network management subsystem, then the value of this object MUST be zero.
.1.3.6.1.2.1.118.1.1.2,ALARM-MIB::alarmModelTable,,not-accessible,,current,,A table of information about possible alarms on the system, and how they have been modelled.
.1.3.6.1.2.1.118.1.1.2.1,ALARM-MIB::alarmModelEntry,,not-accessible,alarmListName:alarmModelIndex:alarmModelState,current,,Entries appear in this table for each possible alarm state. This table MUST be persistent across system reboots.
.1.3.6.1.2.1.118.1.1.2.1.1,ALARM-MIB::alarmModelIndex,Unsigned32,not-accessible,,current,,An integer that acts as an alarm Id to uniquely identify each alarm within the named alarm list. 
.1.3.6.1.2.1.118.1.1.2.1.2,ALARM-MIB::alarmModelState,Unsigned32,not-accessible,,current,,A value of 1 MUST indicate a clear alarm state. The value of this object MUST be less than the alarmModelState of more severe alarm states for this alarm. The value of this object MUST be more than the alarmModelState of less severe alarm states for this alarm.
.1.3.6.1.2.1.118.1.1.2.1.3,ALARM-MIB::alarmModelNotificationId,OBJECT,read-create,,current,,The NOTIFICATION-TYPE object identifier of this alarm state transition. If there is no notification associated with this alarm state, the value of this object MUST be '0.0'
.1.3.6.1.2.1.118.1.1.2.1.4,ALARM-MIB::alarmModelVarbindIndex,Unsigned32,read-create,,current,,The index into the varbind listing of the notification indicated by alarmModelNotificationId which helps signal that the given alarm has changed state. If there is no applicable varbind, the value of this object MUST be zero. Note that the value of alarmModelVarbindIndex acknowledges the existence of the first two obligatory varbinds in the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0 and snmpTrapOID.0). That is, a value of 2 refers to the snmpTrapOID.0. If the incoming notification is instead an SNMPv1 Trap-PDU, then an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be determined by using the rules in section 3.1 of [RFC3584]
.1.3.6.1.2.1.118.1.1.2.1.5,ALARM-MIB::alarmModelVarbindValue,Integer32,read-create,,current,,The value that the varbind indicated by alarmModelVarbindIndex takes to indicate that the alarm has entered this state. If alarmModelVarbindIndex has a value of 0, so MUST alarmModelVarbindValue. 
.1.3.6.1.2.1.118.1.1.2.1.6,ALARM-MIB::alarmModelDescription,OCTET,read-create,,current,,A brief description of this alarm and state suitable to display to operators.
.1.3.6.1.2.1.118.1.1.2.1.7,ALARM-MIB::alarmModelSpecificPointer,OBJECT,read-create,,current,,If no additional, model-specific Alarm MIB is supported by the system the value of this object is `0.0'and attempts to set it to any other value MUST be rejected appropriately. When a model-specific Alarm MIB is supported, this object MUST refer to the first accessible object in a corresponding row of the model definition in one of these model-specific MIB and attempts to set this object to { 0 0 } or any other value MUST be rejected appropriately.
.1.3.6.1.2.1.118.1.1.2.1.8,ALARM-MIB::alarmModelVarbindSubtree,OBJECT,read-create,,current,,The name portion of each VarBind in the notification, in order, is compared to the value of this object. If the name is equal to or a subtree of the value of this object, for purposes of computing the value of AlarmActiveResourceID the 'prefix' will be the matching portion, and the 'indexes' will be any remainder. The examination of varbinds ends with the first match. If the value of this object is 0.0, then the first varbind, or in the case of v2, the first varbind after the timestamp and the trap OID, will always be matched. 
.1.3.6.1.2.1.118.1.1.2.1.9,ALARM-MIB::alarmModelResourcePrefix,OBJECT,read-create,,current,,The value of AlarmActiveResourceId is computed by appending any indexes extracted in accordance with the description of alarmModelVarbindSubtree onto the value of this object. If this object's value is 0.0, then the 'prefix' extracted is used instead. 
.1.3.6.1.2.1.118.1.1.2.1.10,ALARM-MIB::alarmModelRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Control for creating and deleting entries. Entries may be modified while active. Alarms whose alarmModelRowStatus is not active will not appear in either the alarmActiveTable or the alarmClearTable. Setting this object to notInService cannot be used as an alarm suppression mechanism. Entries that are notInService will disappear as described in RFC2579. This row can not be modified while it is being referenced by a value of alarmActiveModelPointer. In these cases, an error of `inconsistentValue' will be returned to the manager. This entry may be deleted while it is being referenced by a value of alarmActiveModelPointer. This results in the deletion of this entry and entries in the active alarms referencing this entry via an alarmActiveModelPointer. As all read-create objects in this table have a DEFVAL clause, there is no requirement that any object be explicitly set before this row can become active. Note that a row consisting only of default values is not very meaningful.
.1.3.6.1.2.1.118.1.2,ALARM-MIB::alarmActive,,,,,,
.1.3.6.1.2.1.118.1.2.1,ALARM-MIB::alarmActiveLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last creation or deletion of an entry in the alarmActiveTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.118.1.2.2,ALARM-MIB::alarmActiveTable,,not-accessible,,current,,A table of Active Alarms entries.
.1.3.6.1.2.1.118.1.2.2.1,ALARM-MIB::alarmActiveEntry,,not-accessible,alarmListName:alarmActiveDateAndTime:alarmActiveIndex,current,,Entries appear in this table when alarms are raised. They are removed when the alarm is cleared. If under extreme resource constraint the system is unable to add any more entries into this table, then the alarmActiveOverflow statistic will be increased by one.
.1.3.6.1.2.1.118.1.2.2.1.1,ALARM-MIB::alarmListName,OCTET,not-accessible,,current,,The name of the list of alarms. This SHOULD be the same as nlmLogName if the Notification Log MIB [RFC3014] is supported. This SHOULD be the same as, or contain as a prefix, the applicable snmpNotifyFilterProfileName if the SNMP-NOTIFICATION-MIB DEFINITIONS [RFC3413] is supported. An implementation may allow multiple named alarm lists, up to some implementation-specific limit (which may be none). A zero-length list name is reserved for creation and deletion by the managed system, and MUST be used as the default log name by systems that do not support named alarm lists.
.1.3.6.1.2.1.118.1.2.2.1.2,ALARM-MIB::alarmActiveDateAndTime,OCTET,not-accessible,,current,,The local date and time when the error occurred. This object facilitates retrieving all instances of alarms that have been raised or have changed state since a given point in time. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
.1.3.6.1.2.1.118.1.2.2.1.3,ALARM-MIB::alarmActiveIndex,Unsigned32,not-accessible,,current,,A strictly monotonically increasing integer which acts as the index of entries within the named alarm list. It wraps back to 1 after it reaches its maximum value.
.1.3.6.1.2.1.118.1.2.2.1.4,ALARM-MIB::alarmActiveEngineID,OCTET,read-only,,current,,The identification of the SNMP engine at which the alarm originated. If the alarm is from an SNMPv1 system this object is a zero length string.
.1.3.6.1.2.1.118.1.2.2.1.5,ALARM-MIB::alarmActiveEngineAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates what type of address is stored in the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc.
.1.3.6.1.2.1.118.1.2.2.1.6,ALARM-MIB::alarmActiveEngineAddress,OCTET,read-only,,current,,The address of the SNMP engine on which the alarm is occurring. This object MUST always be instantiated, even if the list can contain alarms from only one engine.
.1.3.6.1.2.1.118.1.2.2.1.7,ALARM-MIB::alarmActiveContextName,OCTET,read-only,,current,,The name of the SNMP MIB context from which the alarm came. For SNMPv1 alarms this is the community string from the Trap. Note that care MUST be taken when selecting community strings to ensure that these can be represented as a well-formed SnmpAdminString. Community or Context names that are not well-formed SnmpAdminStrings will be mapped to zero length strings. If the alarm's source SNMP engine is known not to support multiple contexts, this object is a zero length string.
.1.3.6.1.2.1.118.1.2.2.1.8,ALARM-MIB::alarmActiveVariables,Unsigned32,read-only,,current,,The number of variables in alarmActiveVariableTable for this alarm.
.1.3.6.1.2.1.118.1.2.2.1.9,ALARM-MIB::alarmActiveNotificationID,OBJECT,read-only,,current,,The NOTIFICATION-TYPE object identifier of the alarm state transition that is occurring.
.1.3.6.1.2.1.118.1.2.2.1.10,ALARM-MIB::alarmActiveResourceId,OBJECT,read-only,,current,,This object identifies the resource under alarm. If there is no corresponding resource, then the value of this object MUST be 0.0.
.1.3.6.1.2.1.118.1.2.2.1.11,ALARM-MIB::alarmActiveDescription,OCTET,read-only,,current,,This object provides a textual description of the active alarm. This text is generated dynamically by the notification generator to provide useful information to the human operator. This information SHOULD provide information allowing the operator to locate the resource for which this alarm is being generated. This information is not intended for consumption by automated tools.
.1.3.6.1.2.1.118.1.2.2.1.12,ALARM-MIB::alarmActiveLogPointer,OBJECT,read-only,,current,,A pointer to the corresponding row in a notification logging MIB where the state change notification for this active alarm is logged. If no log entry applies to this active alarm, then this object MUST have the value of 0.0
.1.3.6.1.2.1.118.1.2.2.1.13,ALARM-MIB::alarmActiveModelPointer,OBJECT,read-only,,current,,A pointer to the corresponding row in the alarmModelTable for this active alarm. This points not only to the alarm model being instantiated, but also to the specific alarm state that is active.
.1.3.6.1.2.1.118.1.2.2.1.14,ALARM-MIB::alarmActiveSpecificPointer,OBJECT,read-only,,current,,If no additional, model-specific, Alarm MIB is supported by the system this object is `0.0'. When a model-specific Alarm MIB is supported, this object is the instance pointer to the specific model-specific active alarm list.
.1.3.6.1.2.1.118.1.2.3,ALARM-MIB::alarmActiveVariableTable,,not-accessible,,current,,A table of variables to go with active alarm entries.
.1.3.6.1.2.1.118.1.2.3.1,ALARM-MIB::alarmActiveVariableEntry,,not-accessible,alarmListName:alarmActiveIndex:alarmActiveVariableIndex,current,,Entries appear in this table when there are variables in the varbind list of a corresponding alarm in alarmActiveTable. Entries appear in this table as though the trap/notification had been transported using a SNMPv2-Trap-PDU, as defined in [RFC3416] - i.e., the alarmActiveVariableIndex 1 will always be sysUpTime and alarmActiveVariableIndex 2 will always be snmpTrapOID. If the incoming notification is instead an SNMPv1 Trap-PDU and the value of alarmModelVarbindIndex is 1 or 2, an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be determined by using the rules in section 3.1 of [RFC3584].
.1.3.6.1.2.1.118.1.2.3.1.1,ALARM-MIB::alarmActiveVariableIndex,Unsigned32,not-accessible,,current,,A strictly monotonically increasing integer, starting at 1 for a given alarmActiveIndex, for indexing variables within the active alarm variable list. 
.1.3.6.1.2.1.118.1.2.3.1.2,ALARM-MIB::alarmActiveVariableID,OBJECT,read-only,,current,,The alarm variable's object identifier.
.1.3.6.1.2.1.118.1.2.3.1.3,ALARM-MIB::alarmActiveVariableValueType,INTEGER,read-only,,current,counter32(1):unsigned32(2):timeTicks(3):integer32(4):ipAddress(5):octetString(6):objectId(7):counter64(8):opaque(9),The type of the value. One and only one of the value objects that follow is used for a given row in this table, based on this type.
.1.3.6.1.2.1.118.1.2.3.1.4,ALARM-MIB::alarmActiveVariableCounter32Val,Counter32,read-only,,current,,The value when alarmActiveVariableType is 'counter32'.
.1.3.6.1.2.1.118.1.2.3.1.5,ALARM-MIB::alarmActiveVariableUnsigned32Val,Unsigned32,read-only,,current,,The value when alarmActiveVariableType is 'unsigned32'.
.1.3.6.1.2.1.118.1.2.3.1.6,ALARM-MIB::alarmActiveVariableTimeTicksVal,TimeTicks,read-only,,current,,The value when alarmActiveVariableType is 'timeTicks'.
.1.3.6.1.2.1.118.1.2.3.1.7,ALARM-MIB::alarmActiveVariableInteger32Val,Integer32,read-only,,current,,The value when alarmActiveVariableType is 'integer32'.
.1.3.6.1.2.1.118.1.2.3.1.8,ALARM-MIB::alarmActiveVariableOctetStringVal,OCTET,read-only,,current,,The value when alarmActiveVariableType is 'octetString'.
.1.3.6.1.2.1.118.1.2.3.1.9,ALARM-MIB::alarmActiveVariableIpAddressVal,IpAddress,read-only,,current,,The value when alarmActiveVariableType is 'ipAddress'.
.1.3.6.1.2.1.118.1.2.3.1.10,ALARM-MIB::alarmActiveVariableOidVal,OBJECT,read-only,,current,,The value when alarmActiveVariableType is 'objectId'.
.1.3.6.1.2.1.118.1.2.3.1.11,ALARM-MIB::alarmActiveVariableCounter64Val,Counter64,read-only,,current,,The value when alarmActiveVariableType is 'counter64'.
.1.3.6.1.2.1.118.1.2.3.1.12,ALARM-MIB::alarmActiveVariableOpaqueVal,Opaque,read-only,,current,,The value when alarmActiveVariableType is 'opaque'. Note that although RFC2578 [RFC2578] forbids the use of Opaque in 'standard' MIB modules, this particular usage is driven by the need to be able to accurately represent any well-formed notification, and justified by the need for backward compatibility.
.1.3.6.1.2.1.118.1.2.4,ALARM-MIB::alarmActiveStatsTable,,not-accessible,,current,,This table represents the alarm statistics information.
.1.3.6.1.2.1.118.1.2.4.1,ALARM-MIB::alarmActiveStatsEntry,,not-accessible,alarmListName,current,,Statistics on the current active alarms.
.1.3.6.1.2.1.118.1.2.4.1.1,ALARM-MIB::alarmActiveStatsActiveCurrent,Gauge32,read-only,,current,,The total number of currently active alarms on the system.
.1.3.6.1.2.1.118.1.2.4.1.2,ALARM-MIB::alarmActiveStatsActives,Gauge32,read-only,,current,,The total number of active alarms since system restarted.
.1.3.6.1.2.1.118.1.2.4.1.3,ALARM-MIB::alarmActiveStatsLastRaise,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last alarm raise for this alarm list. If no alarm raises have occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.118.1.2.4.1.4,ALARM-MIB::alarmActiveStatsLastClear,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last alarm clear for this alarm list. If no alarm clears have occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.118.1.2.5,ALARM-MIB::alarmActiveOverflow,Counter32,read-only,,current,,The number of active alarms that have not been put into the alarmActiveTable since system restart as a result of extreme resource constraints.
.1.3.6.1.2.1.118.1.3,ALARM-MIB::alarmClear,,,,,,
.1.3.6.1.2.1.118.1.3.1,ALARM-MIB::alarmClearMaximum,Unsigned32,read-write,,current,,This object specifies the maximum number of cleared
.1.3.6.1.2.1.118.1.3.2,ALARM-MIB::alarmClearTable,,not-accessible,,current,,This table contains information on cleared alarms.
.1.3.6.1.2.1.118.1.3.2.1,ALARM-MIB::alarmClearEntry,,not-accessible,alarmListName:alarmClearDateAndTime:alarmClearIndex,current,,Information on a cleared alarm.
.1.3.6.1.2.1.118.1.3.2.1.1,ALARM-MIB::alarmClearIndex,Unsigned32,not-accessible,,current,,An integer which acts as the index of entries within the named alarm list. It wraps back to 1 after it reaches its maximum value. This object has the same value as the alarmActiveIndex that this alarm instance had when it was active.
.1.3.6.1.2.1.118.1.3.2.1.2,ALARM-MIB::alarmClearDateAndTime,OCTET,not-accessible,,current,,The local date and time when the alarm cleared. This object facilitates retrieving all instances of alarms that have been cleared since a given point in time. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
.1.3.6.1.2.1.118.1.3.2.1.3,ALARM-MIB::alarmClearEngineID,OCTET,read-only,,current,,The identification of the SNMP engine at which the alarm originated. If the alarm is from an SNMPv1 system this object is a zero length string.
.1.3.6.1.2.1.118.1.3.2.1.4,ALARM-MIB::alarmClearEngineAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates what type of address is stored in the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc.
.1.3.6.1.2.1.118.1.3.2.1.5,ALARM-MIB::alarmClearEngineAddress,OCTET,read-only,,current,,The Address of the SNMP engine on which the alarm was occurring. This is used to identify the source of an SNMPv1 trap, since an alarmActiveEngineId cannot be extracted from the SNMPv1 trap PDU. This object MUST always be instantiated, even if the list can contain alarms from only one engine.
.1.3.6.1.2.1.118.1.3.2.1.6,ALARM-MIB::alarmClearContextName,OCTET,read-only,,current,,The name of the SNMP MIB context from which the alarm came. For SNMPv1 traps this is the community string from the Trap. Note that care needs to be taken when selecting community strings to ensure that these can be represented as a well-formed SnmpAdminString. Community or Context names that are not well-formed SnmpAdminStrings will be mapped to zero length strings. If the alarm's source SNMP engine is known not to support multiple contexts, this object is a zero length string.
.1.3.6.1.2.1.118.1.3.2.1.7,ALARM-MIB::alarmClearNotificationID,OBJECT,read-only,,current,,The NOTIFICATION-TYPE object identifier of the alarm clear.
.1.3.6.1.2.1.118.1.3.2.1.8,ALARM-MIB::alarmClearResourceId,OBJECT,read-only,,current,,This object identifies the resource that was under alarm. If there is no corresponding resource, then the value of this object MUST be 0.0.
.1.3.6.1.2.1.118.1.3.2.1.9,ALARM-MIB::alarmClearLogIndex,Unsigned32,read-only,,current,,This number MUST be the same as the log index of the applicable row in the notification log MIB, if it exists. If no log index applies to the trap, then this object MUST have the value of 0.
.1.3.6.1.2.1.118.1.3.2.1.10,ALARM-MIB::alarmClearModelPointer,OBJECT,read-only,,current,,A pointer to the corresponding row in the alarmModelTable for this cleared alarm.
.1.3.6.1.2.1.118.2,ALARM-MIB::alarmConformance,,,,,,
.1.3.6.1.2.1.118.2.1,ALARM-MIB::alarmCompliances,,,,,,
.1.3.6.1.2.1.118.2.1.1,ALARM-MIB::alarmCompliance,,,,,,The compliance statement for systems supporting the Alarm MIB.
.1.3.6.1.2.1.118.2.2,ALARM-MIB::alarmGroups,,,,,,
.1.3.6.1.2.1.118.2.2.1,ALARM-MIB::alarmModelGroup,,,,,,Alarm model group.
.1.3.6.1.2.1.118.2.2.2,ALARM-MIB::alarmActiveGroup,,,,,,Active Alarm list group.
.1.3.6.1.2.1.118.2.2.3,ALARM-MIB::alarmActiveStatsGroup,,,,,,Active alarm summary group.
.1.3.6.1.2.1.118.2.2.4,ALARM-MIB::alarmClearGroup,,,,,,Cleared alarm group.
.1.3.6.1.2.1.118.2.2.6,ALARM-MIB::alarmNotificationsGroup,,,,,,The collection of notifications that can be used to model alarms for faults lacking pre-existing notification definitions.
.1.3.6.1.2.1.119,IANA-ITU-ALARM-TC-MIB::ianaItuAlarmNumbers,,,,,,The MIB module defines the ITU Alarm textual convention for objects expected to require regular extension. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.120,ITU-ALARM-TC-MIB::ituAlarmTc,,,,,,This MIB module defines the ITU Alarm textual convention for objects not expected to require regular extension. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.121,ITU-ALARM-MIB::ituAlarmMIB,,,,,,The MIB module describes ITU Alarm information as defined in ITU Recommendation M.3100 [M.3100], X.733 [X.733] and X.736 [X.736]. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.121.1,ITU-ALARM-MIB::ituAlarmObjects,,,,,,
.1.3.6.1.2.1.121.1.1,ITU-ALARM-MIB::ituAlarmModel,,,,,,
.1.3.6.1.2.1.121.1.1.1,ITU-ALARM-MIB::ituAlarmTable,,not-accessible,,current,,A table of ITU Alarm information for possible alarms on the system.
.1.3.6.1.2.1.121.1.1.1.1,ITU-ALARM-MIB::ituAlarmEntry,,not-accessible,alarmListName:alarmModelIndex:ituAlarmPerceivedSeverity,current,,Entries appear in this table whenever an entry is created in the alarmModelTable with a value of alarmModelState in the range from 1 to 6. Entries disappear from this table whenever the corresponding entries are deleted from the alarmModelTable, including in cases where those entries have been deleted due to local system action. The value of alarmModelSpecificPointer has no effect on the creation or deletion of entries in this table. Values of alarmModelState map to values of ituAlarmPerceivedSeverity as follows: alarmModelState -> ituAlarmPerceivedSeverity 1 -> clear (1) 2 -> indeterminate (2) 3 -> warning (6) 4 -> minor (5) 5 -> major (4) 6 -> critical (3) All other values of alarmModelState MUST NOT appear in this table. This table MUST be persistent across system reboots.
.1.3.6.1.2.1.121.1.1.1.1.1,ITU-ALARM-MIB::ituAlarmPerceivedSeverity,INTEGER,not-accessible,,current,cleared(1):indeterminate(2):critical(3):major(4):minor(5):warning(6),ITU perceived severity values.
.1.3.6.1.2.1.121.1.1.1.1.2,ITU-ALARM-MIB::ituAlarmEventType,INTEGER,read-write,,current,other(1):communicationsAlarm(2):qualityOfServiceAlarm(3):processingErrorAlarm(4):equipmentAlarm(5):environmentalAlarm(6):integrityViolation(7):operationalViolation(8):physicalViolation(9):securityServiceOrMechanismViolation(10):timeDomainViolation(11),Represents the event type values for the alarms
.1.3.6.1.2.1.121.1.1.1.1.3,ITU-ALARM-MIB::ituAlarmProbableCause,INTEGER,read-write,,current,aIS(1):callSetUpFailure(2):degradedSignal(3):farEndReceiverFailure(4):framingError(5):lossOfFrame(6):lossOfPointer(7):lossOfSignal(8):payloadTypeMismatch(9):transmissionError(10):remoteAlarmInterface(11):excessiveBER(12):pathTraceMismatch(13):unavailable(14):signalLabelMismatch(15):lossOfMultiFrame(16):receiveFailure(17):transmitFailure(18):modulationFailure(19):demodulationFailure(20):broadcastChannelFailure(21):connectionEstablishmentError(22):invalidMessageReceived(23):localNodeTransmissionError(24):remoteNodeTransmissionError(25):routingFailure(26):backplaneFailure(51):dataSetProblem(52):equipmentIdentifierDuplication(53):externalIFDeviceProblem(54):lineCardProblem(55):multiplexerProblem(56):nEIdentifierDuplication(57):powerProblem(58):processorProblem(59):protectionPathFailure(60):receiverFailure(61):replaceableUnitMissing(62):replaceableUnitTypeMismatch(63):synchronizationSourceMismatch(64):terminalProblem(65):timingProblem(66):transmitterFailure(67):trunkCardProblem(68):replaceableUnitProblem(69):realTimeClockFailure(70):antennaFailure(71):batteryChargingFailure(72):diskFailure(73):frequencyHoppingFailure(74):iODeviceError(75):lossOfSynchronisation(76):lossOfRedundancy(77):powerSupplyFailure(78):signalQualityEvaluationFailure(79):tranceiverFailure(80):protectionMechanismFailure(81):protectingResourceFailure(82):airCompressorFailure(101):airConditioningFailure(102):airDryerFailure(103):batteryDischarging(104):batteryFailure(105):commercialPowerFailure(106):coolingFanFailure(107):engineFailure(108):fireDetectorFailure(109):fuseFailure(110):generatorFailure(111):lowBatteryThreshold(112):pumpFailure(113):rectifierFailure(114):rectifierHighVoltage(115):rectifierLowFVoltage(116):ventilationsSystemFailure(117):enclosureDoorOpen(118):explosiveGas(119):fire(120):flood(121):highHumidity(122):highTemperature(123):highWind(124):iceBuildUp(125):intrusionDetection(126):lowFuel(127):lowHumidity(128):lowCablePressure(129):lowTemperatue(130):lowWater(131):smoke(132):toxicGas(133):coolingSystemFailure(134):externalEquipmentFailure(135):externalPointFailure(136):storageCapacityProblem(151):memoryMismatch(152):corruptData(153):outOfCPUCycles(154):sfwrEnvironmentProblem(155):sfwrDownloadFailure(156):lossOfRealTimel(157):applicationSubsystemFailure(158):configurationOrCustomisationError(159):databaseInconsistency(160):fileError(161):outOfMemory(162):softwareError(163):timeoutExpired(164):underlayingResourceUnavailable(165):versionMismatch(166):bandwidthReduced(201):congestion(202):excessiveErrorRate(203):excessiveResponseTime(204):excessiveRetransmissionRate(205):reducedLoggingCapability(206):systemResourcesOverload(207):adapterError(500):applicationSubsystemFailture(501):bandwidthReducedX733(502):callEstablishmentError(503):communicationsProtocolError(504):communicationsSubsystemFailure(505):configurationOrCustomizationError(506):congestionX733(507):coruptData(508):cpuCyclesLimitExceeded(509):dataSetOrModemError(510):degradedSignalX733(511):dteDceInterfaceError(512):enclosureDoorOpenX733(513):equipmentMalfunction(514):excessiveVibration(515):fileErrorX733(516):fireDetected(517):framingErrorX733(518):heatingVentCoolingSystemProblem(519):humidityUnacceptable(520):inputOutputDeviceError(521):inputDeviceError(522):lanError(523):leakDetected(524):localNodeTransmissionErrorX733(525):lossOfFrameX733(526):lossOfSignalX733(527):materialSupplyExhausted(528):multiplexerProblemX733(529):outOfMemoryX733(530):ouputDeviceError(531):performanceDegraded(532):powerProblems(533):pressureUnacceptable(534):processorProblems(535):pumpFailureX733(536):queueSizeExceeded(537):receiveFailureX733(538):receiverFailureX733(539):remoteNodeTransmissionErrorX733(540):resourceAtOrNearingCapacity(541):responseTimeExecessive(542):retransmissionRateExcessive(543):softwareErrorX733(544):softwareProgramAbnormallyTerminated(545):softwareProgramError(546):storageCapacityProblemX733(547):temperatureUnacceptable(548):thresholdCrossed(549):timingProblemX733(550):toxicLeakDetected(551):transmitFailureX733(552):transmiterFailure(553):underlyingResourceUnavailable(554):versionMismatchX733(555):authenticationFailure(600):breachOfConfidentiality(601):cableTamper(602):delayedInformation(603):denialOfService(604):duplicateInformation(605):informationMissing(606):informationModificationDetected(607):informationOutOfSequence(608):keyExpired(609):nonRepudiationFailure(610):outOfHoursActivity(611):outOfService(612):proceduralError(613):unauthorizedAccessAttempt(614):unexpectedInformation(615):other(1024),ITU probable cause values.
.1.3.6.1.2.1.121.1.1.1.1.4,ITU-ALARM-MIB::ituAlarmAdditionalText,OCTET,read-write,,current,,Represents the additional text field for the alarm.
.1.3.6.1.2.1.121.1.1.1.1.5,ITU-ALARM-MIB::ituAlarmGenericModel,OBJECT,read-write,,current,,This object points to the corresponding row in the alarmModelTable for this alarm severity. This corresponding entry to alarmModelTable could also be derived by performing the reverse of the mapping from alarmModelState to ituAlarmPerceivedSeverity defined in the description of ituAlarmEntry to determine the appropriate { alarmListName, alarmModelIndex, alarmModelState } for this { alarmListName, alarmModelIndex, ituAlarmPerceivedSeverity }.
.1.3.6.1.2.1.121.1.2,ITU-ALARM-MIB::ituAlarmActive,,,,,,
.1.3.6.1.2.1.121.1.2.1,ITU-ALARM-MIB::ituAlarmActiveTable,,not-accessible,,current,,A table of ITU information for active alarms entries.
.1.3.6.1.2.1.121.1.2.1.1,ITU-ALARM-MIB::ituAlarmActiveEntry,,not-accessible,alarmListName:alarmActiveDateAndTime:alarmActiveIndex,current,,Entries appear in this table when alarms are active. They are removed when the alarm is no longer occurring.
.1.3.6.1.2.1.121.1.2.1.1.1,ITU-ALARM-MIB::ituAlarmActiveTrendIndication,INTEGER,read-only,,current,moreSevere(1):noChange(2):lessSevere(3),Represents the trend indication values for the alarms.
.1.3.6.1.2.1.121.1.2.1.1.2,ITU-ALARM-MIB::ituAlarmActiveDetector,OBJECT,read-only,,current,,Represents the SecurityAlarmDetector object.
.1.3.6.1.2.1.121.1.2.1.1.3,ITU-ALARM-MIB::ituAlarmActiveServiceProvider,OBJECT,read-only,,current,,Represents the ServiceProvider object.
.1.3.6.1.2.1.121.1.2.1.1.4,ITU-ALARM-MIB::ituAlarmActiveServiceUser,OBJECT,read-only,,current,,Represents the ServiceUser object.
.1.3.6.1.2.1.121.1.2.2,ITU-ALARM-MIB::ituAlarmActiveStatsTable,,not-accessible,,current,,This table represents the ITU alarm statistics information.
.1.3.6.1.2.1.121.1.2.2.1,ITU-ALARM-MIB::ituAlarmActiveStatsEntry,,not-accessible,alarmListName,current,,Statistics on the current active ITU alarms.
.1.3.6.1.2.1.121.1.2.2.1.1,ITU-ALARM-MIB::ituAlarmActiveStatsIndeterminateCurrent,Gauge32,read-only,,current,,A count of the current number of active alarms with a ituAlarmPerceivedSeverity of indeterminate.
.1.3.6.1.2.1.121.1.2.2.1.2,ITU-ALARM-MIB::ituAlarmActiveStatsCriticalCurrent,Gauge32,read-only,,current,,A count of the current number of active alarms with a ituAlarmPerceivedSeverity of critical.
.1.3.6.1.2.1.121.1.2.2.1.3,ITU-ALARM-MIB::ituAlarmActiveStatsMajorCurrent,Gauge32,read-only,,current,,A count of the current number of active alarms with a ituAlarmPerceivedSeverity of major.
.1.3.6.1.2.1.121.1.2.2.1.4,ITU-ALARM-MIB::ituAlarmActiveStatsMinorCurrent,Gauge32,read-only,,current,,A count of the current number of active alarms with a ituAlarmPerceivedSeverity of minor.
.1.3.6.1.2.1.121.1.2.2.1.5,ITU-ALARM-MIB::ituAlarmActiveStatsWarningCurrent,Gauge32,read-only,,current,,A count of the current number of active alarms with a ituAlarmPerceivedSeverity of warning.
.1.3.6.1.2.1.121.1.2.2.1.6,ITU-ALARM-MIB::ituAlarmActiveStatsIndeterminates,Gauge32,read-only,,current,,A count of the total number of active alarms with a ituAlarmPerceivedSeverity of indeterminate since system restart.
.1.3.6.1.2.1.121.1.2.2.1.7,ITU-ALARM-MIB::ituAlarmActiveStatsCriticals,Gauge32,read-only,,current,,A count of the total number of active alarms with a ituAlarmPerceivedSeverity of critical since system restart.
.1.3.6.1.2.1.121.1.2.2.1.8,ITU-ALARM-MIB::ituAlarmActiveStatsMajors,Gauge32,read-only,,current,,A count of the total number of active alarms with a ituAlarmPerceivedSeverity of major since system restart.
.1.3.6.1.2.1.121.1.2.2.1.9,ITU-ALARM-MIB::ituAlarmActiveStatsMinors,Gauge32,read-only,,current,,A count of the total number of active alarms with a ituAlarmPerceivedSeverity of minor since system restart.
.1.3.6.1.2.1.121.1.2.2.1.10,ITU-ALARM-MIB::ituAlarmActiveStatsWarnings,Gauge32,read-only,,current,,A count of the total number of active alarms with a ituAlarmPerceivedSeverity of warning since system restart.
.1.3.6.1.2.1.121.2,ITU-ALARM-MIB::ituAlarmConformance,,,,,,
.1.3.6.1.2.1.121.2.1,ITU-ALARM-MIB::ituAlarmCompliances,,,,,,
.1.3.6.1.2.1.121.2.1.1,ITU-ALARM-MIB::ituAlarmCompliance,,,,,,The compliance statement for systems supporting the ITU Alarm MIB.
.1.3.6.1.2.1.121.2.2,ITU-ALARM-MIB::ituAlarmGroups,,,,,,
.1.3.6.1.2.1.121.2.2.1,ITU-ALARM-MIB::ituAlarmGroup,,,,,,ITU alarm details list group.
.1.3.6.1.2.1.121.2.2.2,ITU-ALARM-MIB::ituAlarmServiceUserGroup,,,,,,The use of these parameters is a service-user option.
.1.3.6.1.2.1.121.2.2.3,ITU-ALARM-MIB::ituAlarmSecurityGroup,,,,,,Security Alarm Reporting Function
.1.3.6.1.2.1.121.2.2.4,ITU-ALARM-MIB::ituAlarmStatisticsGroup,,,,,,ITU Active Alarm Statistics.
.1.3.6.1.2.1.122,TE-MIB::teMIB,,,,,,The Traffic Engineering MIB module. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 3970; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.122.0,TE-MIB::teMIBNotifications,,,,,,
.1.3.6.1.2.1.122.0.1,TE-MIB::teTunnelUp,,,,,,A teTunnelUp notification is generated when the Tunnel indexed by teTunnelName transitions to the 'up' state. A tunnel is up when at least one of its paths is up. The tePathName is the name of the path whose transition to up made the tunnel go up. This notification MUST be limited to at most one every minute, in case the tunnel flaps up and down. 
.1.3.6.1.2.1.122.0.2,TE-MIB::teTunnelDown,,,,,,A teTunnelDown notification is generated when the Tunnel indexed by teTunnelName transitions to the 'down' state. A tunnel is up when at least one of its paths is up. The tePathName is the name of the path whose transition to down made the tunnel go down. This notification MUST be limited to at most one every minute, in case the tunnel flaps up and down. 
.1.3.6.1.2.1.122.0.3,TE-MIB::teTunnelChanged,,,,,,A teTunnelChanged notification is generated when an active path on the Tunnel indexed by teTunnelName changes or a new path becomes active. The value of tePathName is the new active path. This notification MUST be limited to at most one every minute, in case the tunnel changes quickly. 
.1.3.6.1.2.1.122.0.4,TE-MIB::teTunnelRerouted,,,,,,A teTunnelRerouted notification is generated when an active path for the Tunnel indexed by teTunnelName stays the same, but its route changes. This notification MUST be limited to at most one every minute, in case the tunnel reroutes quickly. 
.1.3.6.1.2.1.122.1,TE-MIB::teMIBObjects,,,,,,
.1.3.6.1.2.1.122.1.1,TE-MIB::teInfo,,,,,,
.1.3.6.1.2.1.122.1.1.1,TE-MIB::teDistProtocol,BITS,read-only,,current,other(0):isis(1):ospf(2),IGP used to distribute Traffic Engineering information and topology to each device for the purpose of automatic path computation. More than one IGP may be used to distribute TE information. 
.1.3.6.1.2.1.122.1.1.2,TE-MIB::teSignalingProto,BITS,read-only,,current,other(0):rsvpte(1):crldp(2):static(3),Traffic Engineering signaling protocols supported by this device. More than one protocol may be supported. 
.1.3.6.1.2.1.122.1.1.3,TE-MIB::teNotificationEnable,INTEGER,read-write,,current,true(1):false(2),If this object is true, then it enables the generation of notifications from this MIB module. Otherwise notifications are not generated. 
.1.3.6.1.2.1.122.1.1.4,TE-MIB::teNextTunnelIndex,Unsigned32,read-only,,current,,An integer that may be used as a new Index in the teTunnelTable. The special value of 0 indicates that no more new entries can be created in that table. When this MIB module is used for configuration, this object always contains a legal value (if non-zero) for an index that is not currently used in that table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds, and the Command Responder (agent) changes the value of this object according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. 
.1.3.6.1.2.1.122.1.1.5,TE-MIB::teNextPathHopIndex,Unsigned32,read-only,,current,,An integer that may be used as a new Index in the tePathHopTable. The special value of 0 indicates that no more new entries can be created in that table. When this MIB module is used for configuration, this object always contains a legal value (if non-zero) for an index that is not currently used in that table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds, and the Command Responder (agent) changes the value of this object according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. 
.1.3.6.1.2.1.122.1.1.6,TE-MIB::teConfiguredTunnels,Gauge32,read-only,,current,,Number of currently configured Tunnels.
.1.3.6.1.2.1.122.1.1.7,TE-MIB::teActiveTunnels,Gauge32,read-only,,current,,Number of currently active Tunnels.
.1.3.6.1.2.1.122.1.1.8,TE-MIB::tePrimaryTunnels,Gauge32,read-only,,current,,Number of currently active Tunnels running on their primary paths. 
.1.3.6.1.2.1.122.1.1.9,TE-MIB::teAdminGroupTable,,not-accessible,,current,,A mapping of configured administrative groups. Each entry represents an Administrative Group and provides a name and index for the group. Administrative groups are used to label links in the Traffic Engineering topology in order to place constraints (include and exclude) on Tunnel paths. A groupName can only be linked to one group number. The groupNumber is the number assigned to the administrative group used in constraints, such as tePathIncludeAny or tePathIncludeAll. 
.1.3.6.1.2.1.122.1.1.9.1,TE-MIB::teAdminGroupEntry,,not-accessible,teAdminGroupNumber,current,,A mapping between a configured group number and its human-readable name. The group number should be between 1 and 32, inclusive. Group number n represents bit number (n-1) in the bit vector for Include/Exclude constraints. All entries in this table MUST be kept in stable storage so that they will re-appear in case of a restart/reboot. 
.1.3.6.1.2.1.122.1.1.9.1.1,TE-MIB::teAdminGroupNumber,Integer32,not-accessible,,current,,Index of the administrative group.
.1.3.6.1.2.1.122.1.1.9.1.2,TE-MIB::teAdminGroupName,OCTET,read-create,,current,,Name of the administrative group.
.1.3.6.1.2.1.122.1.1.9.1.3,TE-MIB::teAdminGroupRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The value of this object has no effect on whether other objects in this conceptual row can be modified. 
.1.3.6.1.2.1.122.1.2,TE-MIB::teTunnelTable,,not-accessible,,current,,Table of Configured Traffic Tunnels.
.1.3.6.1.2.1.122.1.2.1,TE-MIB::teTunnelEntry,,not-accessible,teTunnelIndex,current,,Entry containing information about a particular Traffic Tunnel. 
.1.3.6.1.2.1.122.1.2.1.1,TE-MIB::teTunnelIndex,Unsigned32,not-accessible,,current,,A unique index that identifies a Tunnel. If the TE Tunnel is considered an interface, then this index must match the interface index of the corresponding interface. Otherwise, this index must be at least 2^24, so that it does not overlap with any existing interface index. 
.1.3.6.1.2.1.122.1.2.1.2,TE-MIB::teTunnelName,OCTET,read-create,,current,,Name of the Traffic Tunnel. Note that the name of a Tunnel MUST be unique. When a SET request contains a name that is already in use for another entry, then the implementation must return an inconsistentValue error. The value of this object cannot be changed if the if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.2.1.3,TE-MIB::teTunnelNextPathIndex,Unsigned32,read-only,,current,,An integer that may be used as a new Index for the next Path in this Tunnel. The special value of 0 indicates that no more Paths can be created for this Tunnel, or that no more new entries can be created in tePathTable. When this MIB module is used for configuration, this object always contains a legal value (if non-zero) for an index that is not currently used in that table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds, and the Command Responder (agent) changes the value of this object according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value. 
.1.3.6.1.2.1.122.1.2.1.4,TE-MIB::teTunnelRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. When the value of this object is 'active', then the values for the corresponding objects teTunnelName, teTunnelSourceAddressType, teTunnelSourceAddress, teTunnelDestinationAddressType, and teTunnelDestinationAddress cannot be changed. 
.1.3.6.1.2.1.122.1.2.1.5,TE-MIB::teTunnelStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.2.1.122.1.2.1.6,TE-MIB::teTunnelSourceAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):asnumber(3):unnum(4):lspid(5),The type of Traffic Engineered Tunnel hop address for the source of this Tunnel. Typically, this address type is IPv4 or IPv6, with a prefix length of 32 or 128, respectively. If the TE Tunnel path is being computed by a path computation server, however, it is possible to use more flexible source address types, such as AS numbers or prefix lengths less than host address lengths. The value of this object cannot be changed if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.2.1.7,TE-MIB::teTunnelSourceAddress,OCTET,read-create,,current,,The Source Traffic Engineered Tunnel hop address of this Tunnel. The type of this address is determined by the value of the corresponding teTunnelSourceAddressType. Note that the source and destination addresses of a Tunnel can be different address types. The value of this object cannot be changed if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.2.1.8,TE-MIB::teTunnelDestinationAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):asnumber(3):unnum(4):lspid(5),The type of Traffic Engineered Tunnel hop address for the destination of this Tunnel. The value of this object cannot be changed if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.2.1.9,TE-MIB::teTunnelDestinationAddress,OCTET,read-create,,current,,The Destination Traffic Engineered Tunnel hop address of this Tunnel. The type of this address is determined by the value of the corresponding teTunnelDestinationAddressType. Note that source and destination addresses of a Tunnel can be different address types. The value of this object cannot be changed if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.2.1.10,TE-MIB::teTunnelState,INTEGER,read-only,,current,unknown(1):up(2):down(3):testing(4),The operational state of the Tunnel.
.1.3.6.1.2.1.122.1.2.1.11,TE-MIB::teTunnelDiscontinuityTimer,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this tunnel's counters suffered a discontinuity. The relevant counters are teTunnelOctets, teTunnelPackets, teTunnelLPOctets, and teTunnelLPPackets. If no such discontinuities have occurred since the last re-initialization of the local management subsystem then this object contains a zero value. 
.1.3.6.1.2.1.122.1.2.1.12,TE-MIB::teTunnelOctets,Counter64,read-only,,current,,The number of octets that have been forwarded over the Tunnel. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times, as indicated by the value of teTunnelDiscontinuityTimer. 
.1.3.6.1.2.1.122.1.2.1.13,TE-MIB::teTunnelPackets,Counter64,read-only,,current,,The number of packets that have been forwarded over the Tunnel. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of teTunnelDiscontinuityTimer. 
.1.3.6.1.2.1.122.1.2.1.14,TE-MIB::teTunnelLPOctets,Counter32,read-only,,current,,The number of octets that have been forwarded over the Tunnel. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of teTunnelDiscontinuityTimer. 
.1.3.6.1.2.1.122.1.2.1.15,TE-MIB::teTunnelLPPackets,Counter32,read-only,,current,,The number of packets that have been forwarded over the Tunnel. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of teTunnelDiscontinuityTimer. 
.1.3.6.1.2.1.122.1.2.1.16,TE-MIB::teTunnelAge,TimeTicks,read-only,,current,,The age (i.e., time from creation of this conceptual row till now) of this Tunnel in hundredths of a second. Note that because TimeTicks wrap in about 16 months, this value is best used in interval measurements. 
.1.3.6.1.2.1.122.1.2.1.17,TE-MIB::teTunnelTimeUp,TimeTicks,read-only,,current,,The total time in hundredths of a second that this Tunnel has been operational. Note that because TimeTicks wrap in about 16 months, this value is best used in interval measurements. An example of usage of this object would be to compute the percentage up time over a period of time by obtaining values of teTunnelAge and teTunnelTimeUp at two points in time and computing the following ratio: ((teTunnelTimeUp2 - teTunnelTimeUp1)/ (teTunnelAge2 - teTunnelAge1)) * 100 %. In doing so, the management station must account for wrapping of the values of teTunnelAge and teTunnelTimeUp between the two measurements. 
.1.3.6.1.2.1.122.1.2.1.18,TE-MIB::teTunnelPrimaryTimeUp,TimeTicks,read-only,,current,,The total time in hundredths of a second that this Tunnel's primary path has been operational. Note that because TimeTicks wrap in about 16 months, this value is best used in interval measurements. An example of usage of this field would be to compute what percentage of time that a TE Tunnel was on the primary path over a period of time by computing ((teTunnelPrimaryTimeUp2 - teTunnelPrimaryTimeUp1)/ (teTunnelTimeUp2 - teTunnelTimeUp1))*100 %. In doing so, the management station must account for wrapping of the values of teTunnelPrimaryTimeUp and teTunnelTimeUp between the two measurements. 
.1.3.6.1.2.1.122.1.2.1.19,TE-MIB::teTunnelTransitions,Counter32,read-only,,current,,The number of operational state transitions (up -> down and down -> up) this Tunnel has undergone. 
.1.3.6.1.2.1.122.1.2.1.20,TE-MIB::teTunnelLastTransition,TimeTicks,read-only,,current,,The time in hundredths of a second since the last operational state transition occurred on this Tunnel. Note that if the last transition was over 16 months ago, this value will be inaccurate. 
.1.3.6.1.2.1.122.1.2.1.21,TE-MIB::teTunnelPathChanges,Counter32,read-only,,current,,The number of path changes this Tunnel has had.
.1.3.6.1.2.1.122.1.2.1.22,TE-MIB::teTunnelLastPathChange,TimeTicks,read-only,,current,,The time in hundredths of a second since the last path change occurred on this Tunnel. Note that if the last transition was over 16 months ago, this value will be inaccurate. Path changes may be caused by network events or by reconfiguration that affects the path. 
.1.3.6.1.2.1.122.1.2.1.23,TE-MIB::teTunnelConfiguredPaths,Gauge32,read-only,,current,,The number of paths configured for this Tunnel.
.1.3.6.1.2.1.122.1.2.1.24,TE-MIB::teTunnelStandbyPaths,Gauge32,read-only,,current,,The number of standby paths configured for this Tunnel. 
.1.3.6.1.2.1.122.1.2.1.25,TE-MIB::teTunnelOperationalPaths,Gauge32,read-only,,current,,The number of operational paths for this Tunnel. This includes the path currently active, as well as operational standby paths. 
.1.3.6.1.2.1.122.1.3,TE-MIB::tePathTable,,not-accessible,,current,,Table of Configured Traffic Tunnels.
.1.3.6.1.2.1.122.1.3.1,TE-MIB::tePathEntry,,not-accessible,teTunnelIndex:tePathIndex,current,,Entry containing information about a particular Traffic Tunnel. Each Traffic Tunnel can have zero or more Traffic Paths. As a Traffic Path can only exist over an existing Traffic Tunnel, all tePathEntries with a value of n for teTunnelIndex MUST be removed by the implementation when the corresponding teTunnelEntry with a value of n for teTunnelIndex is removed. 
.1.3.6.1.2.1.122.1.3.1.1,TE-MIB::tePathIndex,Unsigned32,not-accessible,,current,,An index that uniquely identifies a path within a Tunnel. The combination of <teTunnelIndex, tePathIndex> thus uniquely identifies a path among all paths on this router. 
.1.3.6.1.2.1.122.1.3.1.2,TE-MIB::tePathName,OCTET,read-create,,current,,The name of this path. A pathName must be unique within the set of paths over a single tunnel. If a SET request is received with a duplicate name, then the implementation MUST return an inconsistentValue error. The value of this object cannot be changed if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.3.1.3,TE-MIB::tePathRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. When the value of this object is 'active', then the value of tePathName cannot be changed. All other writable objects may be changed; however, these changes may affect traffic going over the TE tunnel or require the path to be computed and/or re-signaled. 
.1.3.6.1.2.1.122.1.3.1.4,TE-MIB::tePathStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.2.1.122.1.3.1.5,TE-MIB::tePathType,INTEGER,read-create,,current,other(1):primary(2):standby(3):secondary(4),The type for this PathEntry; i.e., whether this path is a primary path, a standby path, or a secondary path. 
.1.3.6.1.2.1.122.1.3.1.6,TE-MIB::tePathConfiguredRoute,Unsigned32,read-create,,current,,The route that this TE path is configured to follow; i.e., an ordered list of hops. The value of this object gives the primary index into the Hop Table. The secondary index is the hop count in the path, so to get the route, one could get the first hop with index <tePathConfiguredRoute, 1> in the Hop Table and do a getnext to get subsequent hops. 
.1.3.6.1.2.1.122.1.3.1.7,TE-MIB::tePathBandwidth,Unsigned32,read-create,,current,,The configured bandwidth for this Tunnel, in units of thousands of bits per second (Kbps). 
.1.3.6.1.2.1.122.1.3.1.8,TE-MIB::tePathIncludeAny,Unsigned32,read-create,,current,,This is a configured set of administrative groups specified as a bit vector (i.e., bit n is 1 if group n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link must have at least one of the groups specified in IncludeAny to be acceptable. If IncludeAny is zero, all links are acceptable. 
.1.3.6.1.2.1.122.1.3.1.9,TE-MIB::tePathIncludeAll,Unsigned32,read-create,,current,,This is a configured set of administrative groups specified as a bit vector (i.e., bit n is 1 if group n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link must have all of the groups specified in IncludeAll to be acceptable. If IncludeAll is zero, all links are acceptable. 
.1.3.6.1.2.1.122.1.3.1.10,TE-MIB::tePathExclude,Unsigned32,read-create,,current,,This is a configured set of administrative groups specified as a bit vector (i.e., bit n is 1 if group n is in the set, where n = 0 is the LSB). For each link that this path goes through, the link MUST have groups associated with it, and the intersection of the link's groups and the 'exclude' set MUST be null. 
.1.3.6.1.2.1.122.1.3.1.11,TE-MIB::tePathSetupPriority,Integer32,read-create,,current,,The setup priority configured for this path, with 0 as the highest priority and 7 as the lowest. 
.1.3.6.1.2.1.122.1.3.1.12,TE-MIB::tePathHoldPriority,Integer32,read-create,,current,,The hold priority configured for this path, with 0 as the highest priority and 7 as the lowest. 
.1.3.6.1.2.1.122.1.3.1.13,TE-MIB::tePathProperties,BITS,read-create,,current,recordRoute(0):cspf(1):makeBeforeBreak(2):mergeable(3):fastReroute(4):protected(5),The set of configured properties for this path, expressed as a bit map. For example, if the path supports 'make before break', then bit 2 is set. 
.1.3.6.1.2.1.122.1.3.1.14,TE-MIB::tePathOperStatus,INTEGER,read-only,,current,unknown(0):down(1):testing(2):dormant(3):ready(4):operational(5),The operational status of the path: unknown: down: Signaling failed. testing: Administratively set aside for testing. dormant: Not signaled (for a backup tunnel). ready: Signaled but not yet carrying traffic. operational: Signaled and carrying traffic. 
.1.3.6.1.2.1.122.1.3.1.15,TE-MIB::tePathAdminStatus,INTEGER,read-create,,current,normal(1):testing(2),The operational status of the path: normal: Used normally for forwarding. testing: Administratively set aside for testing. 
.1.3.6.1.2.1.122.1.3.1.16,TE-MIB::tePathComputedRoute,Unsigned32,read-only,,current,,The route computed for this path, perhaps using some form of Constraint-based Routing. The algorithm is implementation dependent. This object returns the computed route as an ordered list of hops. The value of this object gives the primary index into the Hop Table. The secondary index is the hop count in the path, so to get the route, one could get the first hop with index <tePathComputedRoute, 1> in the Hop Table and do a getnext to get subsequent hops. A value of zero (0) means there is no computedRoute. 
.1.3.6.1.2.1.122.1.3.1.17,TE-MIB::tePathRecordedRoute,Unsigned32,read-only,,current,,The route actually used for this path, as recorded by the signaling protocol. This is again an ordered list of hops; each hop is expected to be strict. The value of this object gives the primary index into the Hop Table. The secondary index is the hop count in the path, so to get the route, one can get the first hop with index <tePathRecordedRoute, 1> in the Hop Table and do a getnext to get subsequent hops. A value of zero (0) means there is no recordedRoute. 
.1.3.6.1.2.1.122.1.4,TE-MIB::tePathHopTable,,not-accessible,,current,,Table of Tunnel Path Hops.
.1.3.6.1.2.1.122.1.4.1,TE-MIB::tePathHopEntry,,not-accessible,teHopListIndex:tePathHopIndex,current,,Entry containing information about a particular hop. 
.1.3.6.1.2.1.122.1.4.1.1,TE-MIB::teHopListIndex,Unsigned32,not-accessible,,current,,An index that identifies a list of hops. This is the primary index to access hops. 
.1.3.6.1.2.1.122.1.4.1.2,TE-MIB::tePathHopIndex,Unsigned32,not-accessible,,current,,An index that identifies a particular hop among the list of hops for a path. An index of i identifies the ith hop. This is the secondary index for a hop entry. 
.1.3.6.1.2.1.122.1.4.1.3,TE-MIB::tePathHopRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. Any field in this table can be changed, even if the value of this object is 'active'. However, such a change may cause traffic to be rerouted or even disrupted. 
.1.3.6.1.2.1.122.1.4.1.4,TE-MIB::tePathHopStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.2.1.122.1.4.1.5,TE-MIB::tePathHopAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):asnumber(3):unnum(4):lspid(5),The type of Traffic Engineered Tunnel hop Address of this hop. The value of this object cannot be changed if the value of the corresponding tePathRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.4.1.6,TE-MIB::tePathHopAddress,OCTET,read-create,,current,,The Traffic Engineered Tunnel hop Address of this hop. The type of this address is determined by the value of the corresponding tePathHopAddressType. The value of this object cannot be changed if the value of the corresponding teTunnelRowStatus object is 'active'. 
.1.3.6.1.2.1.122.1.4.1.7,TE-MIB::tePathHopType,INTEGER,read-only,,current,unknown(0):loose(1):strict(2),The type of hop: unknown: loose: This hop is a LOOSE hop. strict: This hop is a STRICT hop. 
.1.3.6.1.2.1.122.2,TE-MIB::teMIBConformance,,,,,,
.1.3.6.1.2.1.122.2.1,TE-MIB::teGroups,,,,,,
.1.3.6.1.2.1.122.2.1.1,TE-MIB::teTrafficEngineeringGroup,,,,,,Objects for Traffic Engineering in this MIB module.
.1.3.6.1.2.1.122.2.1.2,TE-MIB::teNotificationGroup,,,,,,Notifications specified in this MIB module.
.1.3.6.1.2.1.122.2.2,TE-MIB::teModuleCompliance,,,,,,
.1.3.6.1.2.1.122.2.2.1,TE-MIB::teModuleReadOnlyCompliance,,,,,,When this MIB module is implemented without support for read-create (i.e., in read-only mode), then such an implementation can claim read-only compliance. Such a device can be monitored but cannot be configured with this MIB module. 
.1.3.6.1.2.1.122.2.2.2,TE-MIB::teModuleFullCompliance,,,,,,When this MIB module is implemented with support for read-create, then the implementation can claim full compliance. Such devices can be both monitored and configured with this MIB module. 
.1.3.6.1.2.1.122.2.2.3,TE-MIB::teModuleServerReadOnlyCompliance,,,,,,When this MIB module is implemented by a path computation server without support for read-create (i.e., in read-only mode), then the implementation can claim read-only compliance. Such a device can be monitored but cannot be configured with this MIB module. 
.1.3.6.1.2.1.122.2.2.4,TE-MIB::teModuleServerFullCompliance,,,,,,When this MIB module is implemented by a path computation server with support for read-create, then the implementation can claim full compliance. 
.1.3.6.1.2.1.123,NAT-MIB::natMIB,,,,,,This MIB module defines the generic managed objects for NAT. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 7658; see the RFC itself for full legal notices.
.1.3.6.1.2.1.123.0,NAT-MIB::natMIBNotifications,,,,,,
.1.3.6.1.2.1.123.0.1,NAT-MIB::natPacketDiscard,,,,,,This notification is generated when IP packets are discarded by the NAT function; e.g., due to lack of mapping space when NAT is out of addresses or ports. Note that the generation of natPacketDiscard notifications is throttled by the agent, as specified by the 'natNotifThrottlingInterval' object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1,NAT-MIB::natMIBObjects,,,,,,
.1.3.6.1.2.1.123.1.1,NAT-MIB::natDefTimeouts,,,,,,
.1.3.6.1.2.1.123.1.1.1,NAT-MIB::natBindDefIdleTimeout,Unsigned32,read-write,,deprecated,,The default Bind (Address Bind or Port Bind) idle timeout parameter. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.1.2,NAT-MIB::natUdpDefIdleTimeout,Unsigned32,read-write,,deprecated,,The default UDP idle timeout parameter. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.1.3,NAT-MIB::natIcmpDefIdleTimeout,Unsigned32,read-write,,deprecated,,The default ICMP idle timeout parameter. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.1.4,NAT-MIB::natOtherDefIdleTimeout,Unsigned32,read-write,,deprecated,,The default idle timeout parameter for protocols represented by the value other (2) in NatProtocolType. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.1.5,NAT-MIB::natTcpDefIdleTimeout,Unsigned32,read-write,,deprecated,,The default time interval that a NAT session for an established TCP connection is allowed to remain valid without any activity on the TCP connection. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.1.6,NAT-MIB::natTcpDefNegTimeout,Unsigned32,read-write,,deprecated,,The default time interval that a NAT session for a TCP connection that is not in the established state is allowed to remain valid without any activity on the TCP connection. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.2,NAT-MIB::natNotifCtrl,,,,,,
.1.3.6.1.2.1.123.1.2.1,NAT-MIB::natNotifThrottlingInterval,Integer32,read-write,,deprecated,,This object controls the generation of the natPacketDiscard notification. If this object has a value of zero, then no natPacketDiscard notifications will be transmitted by the agent. If this object has a non-zero value, then the agent must not generate more than one natPacketDiscard 'notification-event' in the indicated period, where a 'notification-event' is the generation of a single notification PDU type to a list of notification destinations. If additional NAT packets are discarded within the throttling period, then notification-events for these changes must be suppressed by the agent until the current throttling period expires. If natNotifThrottlingInterval notification generation is enabled, the suggested default throttling period is 60 seconds, but generation of the natPacketDiscard notification should be disabled by default. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a reinitialization of the management system. The actual transmission of notifications is controlled via the MIB modules in RFC 3413. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3,NAT-MIB::natInterfaceTable,,not-accessible,,deprecated,,This table specifies the attributes for interfaces on a device supporting NAT function. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1,NAT-MIB::natInterfaceEntry,,not-accessible,ifIndex,deprecated,,Each entry in the natInterfaceTable holds a set of parameters for an interface, instantiated by ifIndex. Therefore, the interface index must have been assigned, according to the applicable procedures, before it can be meaningfully used. Generally, this means that the interface must exist. When natStorageType is of type nonVolatile, however, this may reflect the configuration for an interface whose ifIndex has been assigned but for which the supporting implementation is not currently present. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.1,NAT-MIB::natInterfaceRealm,INTEGER,read-create,,deprecated,private(1):public(2),This object identifies whether this interface is connected to the private or the public realm. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.2,NAT-MIB::natInterfaceServiceType,BITS,read-create,,deprecated,basicNat(0):napt(1):bidirectionalNat(2):twiceNat(3),An indication of the direction in which new sessions are permitted and the extent of translation done within the IP and transport headers. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.3,NAT-MIB::natInterfaceInTranslates,Counter64,read-only,,deprecated,,Number of packets received on this interface that were translated. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.4,NAT-MIB::natInterfaceOutTranslates,Counter64,read-only,,deprecated,,Number of translated packets that were sent out this interface. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.5,NAT-MIB::natInterfaceDiscards,Counter64,read-only,,deprecated,,Number of packets that had to be rejected/dropped due to a lack of resources for this interface. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.6,NAT-MIB::natInterfaceStorageType,INTEGER,read-create,,deprecated,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.3.1.7,NAT-MIB::natInterfaceRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the natInterfaceRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding instance of natInterfaceServiceType has been set. None of the objects in this row may be modified while the value of this object is active(1). Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4,NAT-MIB::natAddrMapTable,,not-accessible,,deprecated,,This table lists address map parameters for NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1,NAT-MIB::natAddrMapEntry,,not-accessible,ifIndex:natAddrMapIndex,deprecated,,This entry represents an address map to be used for NAT and contributes to the dynamic and/or static address mapping tables of the NAT device. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.1,NAT-MIB::natAddrMapIndex,Unsigned32,not-accessible,,deprecated,,Along with ifIndex, this object uniquely identifies an entry in the natAddrMapTable. Address map entries are applied in the order specified by natAddrMapIndex. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.2,NAT-MIB::natAddrMapName,OCTET,read-create,,deprecated,,Name identifying all map entries in the table associated with the same interface. All map entries with the same ifIndex MUST have the same map name. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.3,NAT-MIB::natAddrMapEntryType,INTEGER,read-create,,deprecated,static(1):dynamic(2),This parameter can be used to set up static or dynamic address maps. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.4,NAT-MIB::natAddrMapTranslationEntity,BITS,read-create,,deprecated,inboundSrcEndPoint(0):outboundDstEndPoint(1):inboundDstEndPoint(2):outboundSrcEndPoint(3),The endpoint entity (source or destination) in inbound or outbound sessions (i.e., first packets) that may be translated by an address map entry. Session direction (inbound or outbound) is derived from the direction of the first packet of a session traversing a NAT interface. NAT address (and Transport-ID) maps may be defined to effect inbound or outbound sessions. Traditionally, address maps for Basic NAT and NAPT are configured on a public interface for outbound sessions, effecting translation of source endpoint. The value of this object must be set to outboundSrcEndPoint for those interfaces. Alternately, if address maps for Basic NAT and NAPT were to be configured on a private interface, the desired value for this object for the map entries would be inboundSrcEndPoint (i.e., effecting translation of source endpoint for inbound sessions). If twiceNAT were to be configured on a private interface, the desired value for this object for the map entries would be a bitmask of inboundSrcEndPoint and inboundDstEndPoint. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.5,NAT-MIB::natAddrMapLocalAddrType,INTEGER,read-create,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natAddrMapLocalAddrFrom and natAddrMapLocalAddrTo. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.6,NAT-MIB::natAddrMapLocalAddrFrom,OCTET,read-create,,deprecated,,This object specifies the first IP address of the range of IP addresses mapped by this translation entry. The value of this object must be less than or equal to the value of the natAddrMapLocalAddrTo object. The type of this address is determined by the value of the natAddrMapLocalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.7,NAT-MIB::natAddrMapLocalAddrTo,OCTET,read-create,,deprecated,,This object specifies the last IP address of the range of IP addresses mapped by this translation entry. If only a single address is being mapped, the value of this object is equal to the value of natAddrMapLocalAddrFrom. For a static NAT, the number of addresses in the range defined by natAddrMapLocalAddrFrom and natAddrMapLocalAddrTo must be equal to the number of addresses in the range defined by natAddrMapGlobalAddrFrom and natAddrMapGlobalAddrTo. The value of this object must be greater than or equal to the value of the natAddrMapLocalAddrFrom object. The type of this address is determined by the value of the natAddrMapLocalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.8,NAT-MIB::natAddrMapLocalPortFrom,Unsigned32,read-create,,deprecated,,If this conceptual row describes a Basic NAT address mapping, then the value of this object must be zero. If this conceptual row describes NAPT, then the value of this object specifies the first port number in the range of ports being mapped. The value of this object must be less than or equal to the value of the natAddrMapLocalPortTo object. If the translation specifies a single port, then the value of this object is equal to the value of natAddrMapLocalPortTo. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.9,NAT-MIB::natAddrMapLocalPortTo,Unsigned32,read-create,,deprecated,,If this conceptual row describes a Basic NAT address mapping, then the value of this object must be zero. If this conceptual row describes NAPT, then the value of this object specifies the last port number in the range of ports being mapped. The value of this object must be greater than or equal to the value of the natAddrMapLocalPortFrom object. If the translation specifies a single port, then the value of this object is equal to the value of natAddrMapLocalPortFrom. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.10,NAT-MIB::natAddrMapGlobalAddrType,INTEGER,read-create,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natAddrMapGlobalAddrFrom and natAddrMapGlobalAddrTo. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.11,NAT-MIB::natAddrMapGlobalAddrFrom,OCTET,read-create,,deprecated,,This object specifies the first IP address of the range of IP addresses being mapped to. The value of this object must be less than or equal to the value of the natAddrMapGlobalAddrTo object. The type of this address is determined by the value of the natAddrMapGlobalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.12,NAT-MIB::natAddrMapGlobalAddrTo,OCTET,read-create,,deprecated,,This object specifies the last IP address of the range of IP addresses being mapped to. If only a single address is being mapped to, the value of this object is equal to the value of natAddrMapGlobalAddrFrom. For a static NAT, the number of addresses in the range defined by natAddrMapGlobalAddrFrom and natAddrMapGlobalAddrTo must be equal to the number of addresses in the range defined by natAddrMapLocalAddrFrom and natAddrMapLocalAddrTo. The value of this object must be greater than or equal to the value of the natAddrMapGlobalAddrFrom object. The type of this address is determined by the value of the natAddrMapGlobalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.13,NAT-MIB::natAddrMapGlobalPortFrom,Unsigned32,read-create,,deprecated,,If this conceptual row describes a Basic NAT address mapping, then the value of this object must be zero. If this conceptual row describes NAPT, then the value of this object specifies the first port number in the range of ports being mapped to. The value of this object must be less than or equal to the value of the natAddrMapGlobalPortTo object. If the translation specifies a single port, then the value of this object is equal to the value natAddrMapGlobalPortTo. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.14,NAT-MIB::natAddrMapGlobalPortTo,Unsigned32,read-create,,deprecated,,If this conceptual row describes a Basic NAT address mapping, then the value of this object must be zero. If this conceptual row describes NAPT, then the value of this object specifies the last port number in the range of ports being mapped to. The value of this object must be greater than or equal to the value of the natAddrMapGlobalPortFrom object. If the translation specifies a single port, then the value of this object is equal to the value of natAddrMapGlobalPortFrom. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.15,NAT-MIB::natAddrMapProtocol,BITS,read-create,,deprecated,other(0):icmp(1):udp(2):tcp(3),This object specifies a bitmap of protocol identifiers. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.16,NAT-MIB::natAddrMapInTranslates,Counter64,read-only,,deprecated,,The number of inbound packets pertaining to this address map entry that were translated. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.17,NAT-MIB::natAddrMapOutTranslates,Counter64,read-only,,deprecated,,The number of outbound packets pertaining to this address map entry that were translated. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.18,NAT-MIB::natAddrMapDiscards,Counter64,read-only,,deprecated,,The number of packets pertaining to this address map entry that were dropped due to lack of addresses in the address pool identified by this address map. The value of this object must always be zero in case of a static address map. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.19,NAT-MIB::natAddrMapAddrUsed,Gauge32,read-only,,deprecated,,The number of addresses pertaining to this address map that are currently being used from the NAT pool. The value of this object must always be zero in the case of a static address map. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.20,NAT-MIB::natAddrMapStorageType,INTEGER,read-create,,deprecated,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.4.1.21,NAT-MIB::natAddrMapRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the natAddrMapRowStatus column is 'notReady'. None of the objects in this row may be modified while the value of this object is active(1). Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.5,NAT-MIB::natAddrBindNumberOfEntries,Gauge32,read-only,,deprecated,,This object maintains a count of the number of entries that currently exist in the natAddrBindTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6,NAT-MIB::natAddrBindTable,,not-accessible,,deprecated,,This table holds information about the currently active NAT BINDs. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1,NAT-MIB::natAddrBindEntry,,not-accessible,ifIndex:natAddrBindLocalAddrType:natAddrBindLocalAddr,deprecated,,Each entry in this table holds information about an active address BIND. These entries are lost upon agent restart. This row has indexing that may create variables with more than 128 subidentifiers. Implementers of this table must be careful not to create entries that would result in OIDs that exceed the 128 subidentifier limit. Otherwise, the information cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.1,NAT-MIB::natAddrBindLocalAddrType,INTEGER,not-accessible,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natAddrBindLocalAddr. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.2,NAT-MIB::natAddrBindLocalAddr,OCTET,not-accessible,,deprecated,,This object represents the private-realm-specific network-layer address, which maps to the public-realm address represented by natAddrBindGlobalAddr. The type of this address is determined by the value of the natAddrBindLocalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.3,NAT-MIB::natAddrBindGlobalAddrType,INTEGER,read-only,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natAddrBindGlobalAddr. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.4,NAT-MIB::natAddrBindGlobalAddr,OCTET,read-only,,deprecated,,This object represents the public-realm network-layer address that maps to the private-realm network-layer address represented by natAddrBindLocalAddr. The type of this address is determined by the value of the natAddrBindGlobalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.5,NAT-MIB::natAddrBindId,Unsigned32,read-only,,deprecated,,This object represents a bind ID that is dynamically assigned to each bind by a NAT-enabled device. Each bind is represented by a bind ID that is unique across both the natAddrBindTable and the natAddrPortBindTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.6,NAT-MIB::natAddrBindTranslationEntity,BITS,read-only,,deprecated,inboundSrcEndPoint(0):outboundDstEndPoint(1):inboundDstEndPoint(2):outboundSrcEndPoint(3),This object represents the direction of sessions for which this bind is applicable and the endpoint entity (source or destination) within the sessions that is subject to translation using the BIND. Orientation of the bind can be a superset of translationEntity of the address map entry that forms the basis for this bind. For example, if the translationEntity of an address map entry is outboundSrcEndPoint, the translationEntity of a bind derived from this map entry may either be outboundSrcEndPoint or it may be bidirectional (a bitmask of outboundSrcEndPoint and inboundDstEndPoint). Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.7,NAT-MIB::natAddrBindType,INTEGER,read-only,,deprecated,static(1):dynamic(2),This object indicates whether the bind is static or dynamic. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.8,NAT-MIB::natAddrBindMapIndex,Unsigned32,read-only,,deprecated,,This object is a pointer to the natAddrMapTable entry (and the parameters of that entry) that was used in creating this BIND. This object, in conjunction with the ifIndex (which identifies a unique addrMapName) points to a unique entry in the natAddrMapTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.9,NAT-MIB::natAddrBindSessions,Gauge32,read-only,,deprecated,,Number of sessions currently using this BIND. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.10,NAT-MIB::natAddrBindMaxIdleTime,TimeTicks,read-only,,deprecated,,This object indicates the maximum time for which this bind can be idle with no sessions attached to it. The value of this object is of relevance only for dynamic NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.11,NAT-MIB::natAddrBindCurrentIdleTime,TimeTicks,read-only,,deprecated,,At any given instance, this object indicates the time that this bind has been idle without any sessions attached to it. The value of this object is of relevance only for dynamic NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.12,NAT-MIB::natAddrBindInTranslates,Counter64,read-only,,deprecated,,The number of inbound packets that were successfully translated by using this bind entry. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.6.1.13,NAT-MIB::natAddrBindOutTranslates,Counter64,read-only,,deprecated,,The number of outbound packets that were successfully translated using this bind entry. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.7,NAT-MIB::natAddrPortBindNumberOfEntries,Gauge32,read-only,,deprecated,,This object maintains a count of the number of entries that currently exist in the natAddrPortBindTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8,NAT-MIB::natAddrPortBindTable,,not-accessible,,deprecated,,This table holds information about the currently active NAPT BINDs. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1,NAT-MIB::natAddrPortBindEntry,,not-accessible,ifIndex:natAddrPortBindLocalAddrType:natAddrPortBindLocalAddr:natAddrPortBindLocalPort:natAddrPortBindProtocol,deprecated,,Each entry in the this table holds information about a NAPT bind that is currently active. These entries are lost upon agent restart. This row has indexing that may create variables with more than 128 subidentifiers. Implementers of this table must be careful not to create entries that would result in OIDs that exceed the 128 subidentifier limit. Otherwise, the information cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.1,NAT-MIB::natAddrPortBindLocalAddrType,INTEGER,not-accessible,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natAddrPortBindLocalAddr. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.2,NAT-MIB::natAddrPortBindLocalAddr,OCTET,not-accessible,,deprecated,,This object represents the private-realm-specific network-layer address that, in conjunction with natAddrPortBindLocalPort, maps to the public-realm network-layer address and transport ID represented by natAddrPortBindGlobalAddr and natAddrPortBindGlobalPort, respectively. The type of this address is determined by the value of the natAddrPortBindLocalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.3,NAT-MIB::natAddrPortBindLocalPort,Unsigned32,not-accessible,,deprecated,,For a protocol value TCP or UDP, this object represents the private-realm-specific port number. On the other hand, for ICMP a bind is created only for query/response- type ICMP messages such as ICMP echo, Timestamp, and Information request messages, and this object represents the private-realm-specific identifier in the ICMP message, as defined in RFC 792 for ICMPv4 and in RFC 4443 for ICMPv6. This object, together with natAddrPortBindProtocol, natAddrPortBindLocalAddrType, and natAddrPortBindLocalAddr, constitutes a session endpoint in the private realm. A bind entry binds a private- realm-specific endpoint to a public-realm-specific endpoint, as represented by the tuple of (natAddrPortBindGlobalPort, natAddrPortBindProtocol, natAddrPortBindGlobalAddrType, and natAddrPortBindGlobalAddr). Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.4,NAT-MIB::natAddrPortBindProtocol,INTEGER,not-accessible,,deprecated,none(1):other(2):icmp(3):udp(4):tcp(5),This object specifies a protocol identifier. If the value of this object is none(1), then this bind entry applies to all IP traffic. Any other value of this object specifies the class of IP traffic to which this BIND applies. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.5,NAT-MIB::natAddrPortBindGlobalAddrType,INTEGER,read-only,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natAddrPortBindGlobalAddr. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.6,NAT-MIB::natAddrPortBindGlobalAddr,OCTET,read-only,,deprecated,,This object represents the public-realm-specific network- layer address that, in conjunction with natAddrPortBindGlobalPort, maps to the private-realm network-layer address and transport ID represented by natAddrPortBindLocalAddr and natAddrPortBindLocalPort, respectively. The type of this address is determined by the value of the natAddrPortBindGlobalAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.7,NAT-MIB::natAddrPortBindGlobalPort,Unsigned32,read-only,,deprecated,,For a protocol value TCP or UDP, this object represents the public-realm-specific port number. On the other hand, for ICMP a bind is created only for query/response- type ICMP messages such as ICMP echo, Timestamp, and Information request messages, and this object represents the public-realm-specific identifier in the ICMP message, as defined in RFC 792 for ICMPv4 and in RFC 4443 for ICMPv6. This object, together with natAddrPortBindProtocol, natAddrPortBindGlobalAddrType, and natAddrPortBindGlobalAddr, constitutes a session endpoint in the public realm. A bind entry binds a public-realm-specific endpoint to a private-realm- specific endpoint, as represented by the tuple of (natAddrPortBindLocalPort, natAddrPortBindProtocol, natAddrPortBindLocalAddrType, and natAddrPortBindLocalAddr). Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.8,NAT-MIB::natAddrPortBindId,Unsigned32,read-only,,deprecated,,This object represents a bind ID that is dynamically assigned to each bind by a NAT-enabled device. Each bind is represented by a unique bind ID across both the natAddrBindTable and the natAddrPortBindTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.9,NAT-MIB::natAddrPortBindTranslationEntity,BITS,read-only,,deprecated,inboundSrcEndPoint(0):outboundDstEndPoint(1):inboundDstEndPoint(2):outboundSrcEndPoint(3),This object represents the direction of sessions for which this bind is applicable and the entity (source or destination) within the sessions that is subject to translation with the BIND. Orientation of the bind can be a superset of the translationEntity of the address map entry that forms the basis for this bind. For example, if the translationEntity of an address map entry is outboundSrcEndPoint, the translationEntity of a bind derived from this map entry may either be outboundSrcEndPoint or may be bidirectional (a bitmask of outboundSrcEndPoint and inboundDstEndPoint). Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.10,NAT-MIB::natAddrPortBindType,INTEGER,read-only,,deprecated,static(1):dynamic(2),This object indicates whether the bind is static or dynamic. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.11,NAT-MIB::natAddrPortBindMapIndex,Unsigned32,read-only,,deprecated,,This object is a pointer to the natAddrMapTable entry (and the parameters of that entry) used in creating this BIND. This object, in conjunction with the ifIndex (which identifies a unique addrMapName), points to a unique entry in the natAddrMapTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.12,NAT-MIB::natAddrPortBindSessions,Gauge32,read-only,,deprecated,,Number of sessions currently using this BIND. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.13,NAT-MIB::natAddrPortBindMaxIdleTime,TimeTicks,read-only,,deprecated,,This object indicates the maximum time for which this bind can be idle without any sessions attached to it. The value of this object is of relevance only for dynamic NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.14,NAT-MIB::natAddrPortBindCurrentIdleTime,TimeTicks,read-only,,deprecated,,At any given instance, this object indicates the time that this bind has been idle without any sessions attached to it. The value of this object is of relevance only for dynamic NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.15,NAT-MIB::natAddrPortBindInTranslates,Counter64,read-only,,deprecated,,The number of inbound packets that were translated as per this bind entry. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.8.1.16,NAT-MIB::natAddrPortBindOutTranslates,Counter64,read-only,,deprecated,,The number of outbound packets that were translated as per this bind entry. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9,NAT-MIB::natSessionTable,,not-accessible,,deprecated,,The (conceptual) table containing one entry for each NAT session currently active on this NAT device. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1,NAT-MIB::natSessionEntry,,not-accessible,ifIndex:natSessionIndex,deprecated,,An entry (conceptual row) containing information about an active NAT session on this NAT device. These entries are lost upon agent restart. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.1,NAT-MIB::natSessionIndex,Unsigned32,not-accessible,,deprecated,,The session ID for this NAT session. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.2,NAT-MIB::natSessionPrivateSrcEPBindId,Unsigned32,read-only,,deprecated,,The bind ID associated between private and public source endpoints. In the case of Symmetric-NAT, this should be set to zero. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.3,NAT-MIB::natSessionPrivateSrcEPBindMode,INTEGER,read-only,,deprecated,addressBind(1):addressPortBind(2),This object indicates whether the bind indicated by the object natSessionPrivateSrcEPBindId is an address bind or an address port bind. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.4,NAT-MIB::natSessionPrivateDstEPBindId,Unsigned32,read-only,,deprecated,,The bind ID associated between private and public destination endpoints. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.5,NAT-MIB::natSessionPrivateDstEPBindMode,INTEGER,read-only,,deprecated,addressBind(1):addressPortBind(2),This object indicates whether the bind indicated by the object natSessionPrivateDstEPBindId is an address bind or an address port bind. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.6,NAT-MIB::natSessionDirection,INTEGER,read-only,,deprecated,inbound(1):outbound(2),The direction of this session with respect to the local network. 'inbound' indicates that this session was initiated from the public network into the private network. 'outbound' indicates that this session was initiated from the private network into the public network. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.7,NAT-MIB::natSessionUpTime,TimeTicks,read-only,,deprecated,,The uptime of this session in hundredths of a second. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.8,NAT-MIB::natSessionAddrMapIndex,Unsigned32,read-only,,deprecated,,This object is a pointer to the natAddrMapTable entry (and the parameters of that entry) used in creating this session. This object, in conjunction with the ifIndex (which identifies a unique addrMapName), points to a unique entry in the natAddrMapTable. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.9,NAT-MIB::natSessionProtocolType,INTEGER,read-only,,deprecated,none(1):other(2):icmp(3):udp(4):tcp(5),The protocol type of this session. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.10,NAT-MIB::natSessionPrivateAddrType,INTEGER,read-only,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natSessionPrivateSrcAddr and natSessionPrivateDstAddr. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.11,NAT-MIB::natSessionPrivateSrcAddr,OCTET,read-only,,deprecated,,The source IP address of the session endpoint that lies in the private network. The value of this object must be zero only when the natSessionPrivateSrcEPBindId object has a zero value. When the value of this object is zero, the NAT session lookup will match any IP address to this field. The type of this address is determined by the value of the natSessionPrivateAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.12,NAT-MIB::natSessionPrivateSrcPort,Unsigned32,read-only,,deprecated,,For a protocol value of TCP or UDP, this object represents the source port in the first packet of a session while in a private realm. On the other hand, when the protocol is ICMP, a NAT session is created only for query/response-type ICMP messages such as ICMP echo, Timestamp, and Information request messages, and this object represents the private-realm specific identifier in the ICMP message, as defined in RFC 792 for ICMPv4 and in RFC 4443 for ICMPv6. The value of this object must be zero when the natSessionPrivateSrcEPBindId object has zero value and value of natSessionPrivateSrcEPBindMode is addressPortBind(2). In such a case, the NAT session lookup will match any port number to this field. The value of this object must be zero when the object is not a representative field (SrcPort, DstPort, or ICMP identifier) of the session tuple in either the public realm or the private realm. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.13,NAT-MIB::natSessionPrivateDstAddr,OCTET,read-only,,deprecated,,The destination IP address of the session endpoint that lies in the private network. The value of this object must be zero when the natSessionPrivateDstEPBindId object has a zero value. In such a scenario, the NAT session lookup will match any IP address to this field. The type of this address is determined by the value of the natSessionPrivateAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.14,NAT-MIB::natSessionPrivateDstPort,Unsigned32,read-only,,deprecated,,When the value of protocol is TCP or UDP, this object represents the destination port in the first packet of session while in private-realm. On the other hand, when the protocol is ICMP, this object is not relevant and should be set to zero. The value of this object must be zero when the natSessionPrivateDstEPBindId object has a zero value and natSessionPrivateDstEPBindMode is set to addressPortBind(2). In such a case, the NAT session lookup will match any port number to this field. The value of this object must be zero when the object is not a representative field (SrcPort, DstPort, or ICMP identifier) of the session tuple in either the public realm or the private realm. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.15,NAT-MIB::natSessionPublicAddrType,INTEGER,read-only,,deprecated,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for natSessionPublicSrcAddr and natSessionPublicDstAddr. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.16,NAT-MIB::natSessionPublicSrcAddr,OCTET,read-only,,deprecated,,The source IP address of the session endpoint that lies in the public network. The value of this object must be zero when the natSessionPrivateSrcEPBindId object has a zero value. In such a scenario, the NAT session lookup will match any IP address to this field. The type of this address is determined by the value of the natSessionPublicAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.17,NAT-MIB::natSessionPublicSrcPort,Unsigned32,read-only,,deprecated,,When the protocol value is TCP or UDP, this object represents the source port in the first packet of session while in public-realm. On the other hand, when protocol is ICMP, a NAT session is created only for query/response-type ICMP messages such as ICMP echo, Timestamp, and Information request messages, and this object represents the public-realm-specific identifier in the ICMP message, as defined in RFC 792 for ICMPv4 and in RFC 4443 for ICMPv6. The value of this object must be zero when the natSessionPrivateSrcEPBindId object has a zero value and natSessionPrivateSrcEPBindMode is set to addressPortBind(2). In such a scenario, the NAT session lookup will match any port number to this field. The value of this object must be zero when the object is not a representative field (SrcPort, DstPort, or ICMP identifier) of the session tuple in either the public realm or the private realm. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.18,NAT-MIB::natSessionPublicDstAddr,OCTET,read-only,,deprecated,,The destination IP address of the session endpoint that lies in the public network. The value of this object must be non-zero when the natSessionPrivateDstEPBindId object has a non-zero value. If the value of this object and the corresponding natSessionPrivateDstEPBindId object value are zero, then the NAT session lookup will match any IP address to this field. The type of this address is determined by the value of the natSessionPublicAddrType object. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.19,NAT-MIB::natSessionPublicDstPort,Unsigned32,read-only,,deprecated,,When the protocol value is TCP or UDP, this object represents the destination port in the first packet of session while in the public realm. On the other hand, when the protocol is ICMP, this object is not relevant for translation and should be zero. The value of this object must be zero when the natSessionPrivateDstEPBindId object has a zero value and natSessionPrivateDstEPBindMode is addressPortBind(2). In such a scenario, the NAT session lookup will match any port number to this field. The value of this object must be zero when the object is not a representative field (SrcPort, DstPort, or ICMP identifier) of the session tuple in either the public realm or the private realm. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.20,NAT-MIB::natSessionMaxIdleTime,TimeTicks,read-only,,deprecated,,The max time for which this session can be idle without detecting a packet. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.21,NAT-MIB::natSessionCurrentIdleTime,TimeTicks,read-only,,deprecated,,The time since a packet belonging to this session was last detected. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.22,NAT-MIB::natSessionInTranslates,Counter64,read-only,,deprecated,,The number of inbound packets that were translated for this session. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.9.1.23,NAT-MIB::natSessionOutTranslates,Counter64,read-only,,deprecated,,The number of outbound packets that were translated for this session. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.10,NAT-MIB::natProtocolTable,,not-accessible,,deprecated,,The (conceptual) table containing per-protocol NAT statistics. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.10.1,NAT-MIB::natProtocolEntry,,not-accessible,natProtocol,deprecated,,An entry (conceptual row) containing NAT statistics pertaining to a particular protocol. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.10.1.1,NAT-MIB::natProtocol,INTEGER,not-accessible,,deprecated,none(1):other(2):icmp(3):udp(4):tcp(5),This object represents the protocol pertaining to which parameters are reported. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.10.1.2,NAT-MIB::natProtocolInTranslates,Counter64,read-only,,deprecated,,The number of inbound packets pertaining to the protocol identified by natProtocol that underwent NAT. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.10.1.3,NAT-MIB::natProtocolOutTranslates,Counter64,read-only,,deprecated,,The number of outbound packets pertaining to the protocol identified by natProtocol that underwent NAT. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.1.10.1.4,NAT-MIB::natProtocolDiscards,Counter64,read-only,,deprecated,,The number of packets pertaining to the protocol identified by natProtocol that had to be rejected/dropped due to lack of resources. These rejections could be due to session timeout, resource unavailability, lack of address space, etc. Discontinuities in the value of this counter can occur at reinitialization of the management system and at other times, as indicated by the value of ifCounterDiscontinuityTime on the relevant interface. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2,NAT-MIB::natMIBConformance,,,,,,
.1.3.6.1.2.1.123.2.1,NAT-MIB::natMIBGroups,,,,,,
.1.3.6.1.2.1.123.2.1.1,NAT-MIB::natConfigGroup,,,,,,A collection of configuration-related information required to support management of devices supporting NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.1.2,NAT-MIB::natTranslationGroup,,,,,,A collection of BIND-related objects required to support management of devices supporting NAT. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.1.3,NAT-MIB::natStatsInterfaceGroup,,,,,,A collection of NAT statistics associated with the interface on which NAT is configured, to aid troubleshooting/monitoring of the NAT operation. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.1.4,NAT-MIB::natStatsProtocolGroup,,,,,,A collection of protocol-specific NAT statistics, to aid troubleshooting/monitoring of NAT operation. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.1.5,NAT-MIB::natStatsAddrMapGroup,,,,,,A collection of address-map-specific NAT statistics, to aid troubleshooting/monitoring of NAT operation. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.1.6,NAT-MIB::natMIBNotificationGroup,,,,,,A collection of notifications generated by devices supporting this MIB. Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.2,NAT-MIB::natMIBCompliances,,,,,,
.1.3.6.1.2.1.123.2.2.1,NAT-MIB::natMIBFullCompliance,,,,,,When this MIB is implemented with support for read-create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB. The following index objects cannot be added as OBJECT clauses but nevertheless have the compliance requirements: Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.123.2.2.2,NAT-MIB::natMIBReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-create (i.e., in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but cannot be configured with this MIB. The following index objects cannot be added as OBJECT clauses but nevertheless have the compliance requirements: Deprecated in favor of NATV2-MIB.
.1.3.6.1.2.1.124,POLICY-BASED-MANAGEMENT-MIB::pmMib,,,,,,The MIB module for policy-based configuration of SNMP infrastructures. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4011; see the RFC itself for full legal notices.
.1.3.6.1.2.1.124.0,POLICY-BASED-MANAGEMENT-MIB::pmNotifications,,,,,,
.1.3.6.1.2.1.124.0.1,POLICY-BASED-MANAGEMENT-MIB::pmNewRoleNotification,,,,,,The pmNewRoleNotification is sent when an agent is configured with its first instance of a previously unused role string (not every time a new element is given a particular role). An instance of the pmRoleStatus object is sent containing the new roleString in its index. In the event that two or more elements are given the same role simultaneously, it is an implementation-dependent matter as to which pmRoleTable instance will be included in the notification.
.1.3.6.1.2.1.124.0.2,POLICY-BASED-MANAGEMENT-MIB::pmNewCapabilityNotification,,,,,,The pmNewCapabilityNotification is sent when an agent gains a new capability that did not previously exist in any element on the system (not every time an element gains a particular capability). An instance of the pmCapabilitiesType object is sent containing the identity of the new capability. In the event that two or more elements gain the same capability simultaneously, it is an implementation-dependent matter as to which pmCapabilitiesType instance will be included in the notification.
.1.3.6.1.2.1.124.0.3,POLICY-BASED-MANAGEMENT-MIB::pmAbnormalTermNotification,,,,,,The pmAbnormalTermNotification is sent when a policy's pmPolicyAbnormalTerminations gauge value changes from zero to any value greater than zero and no such notification has been sent for that policy in the last 5 minutes. The notification contains an instance of the pmTrackingPEInfo object where the pmPolicyIndex component of the index identifies the associated policy and the rest of the index identifies an element on which the policy failed.
.1.3.6.1.2.1.124.1,POLICY-BASED-MANAGEMENT-MIB::pmPolicyTable,,not-accessible,,current,,The policy table. A policy is a pairing of a policyCondition and a policyAction that is used to apply the action to a selected set of elements.
.1.3.6.1.2.1.124.1.1,POLICY-BASED-MANAGEMENT-MIB::pmPolicyEntry,,not-accessible,pmPolicyAdminGroup:pmPolicyIndex,current,,An entry in the policy table representing one policy.
.1.3.6.1.2.1.124.1.1.1,POLICY-BASED-MANAGEMENT-MIB::pmPolicyAdminGroup,OCTET,not-accessible,,current,,An administratively assigned string that can be used to group policies for convenience, for readability, or to simplify configuration of access control. The value of this string does not affect policy processing in any way. If grouping is not desired or necessary, this object may be set to a zero-length string.
.1.3.6.1.2.1.124.1.1.2,POLICY-BASED-MANAGEMENT-MIB::pmPolicyIndex,Unsigned32,not-accessible,,current,,A unique index for this policy entry, unique among all policies regardless of administrative group.
.1.3.6.1.2.1.124.1.1.3,POLICY-BASED-MANAGEMENT-MIB::pmPolicyPrecedenceGroup,OCTET,read-create,,current,,An administratively assigned string that is used to group policies. For each element, only one policy in the same precedence group may be active on that element. If multiple policies would be active on an element (because their conditions return non-zero), the execution environment will only allow the policy with the highest value of pmPolicyPrecedence to be active. All values of this object must have been successfully transformed by Stringprep RFC 3454. Management stations must perform this translation and must only set this object to string values that have been transformed.
.1.3.6.1.2.1.124.1.1.4,POLICY-BASED-MANAGEMENT-MIB::pmPolicyPrecedence,Unsigned32,read-create,,current,,If, while checking to see which policy conditions match an element, 2 or more ready policies in the same precedence group match the same element, the pmPolicyPrecedence object provides the rule to arbitrate which single policy will be active on 'this element'. Of policies in the same precedence group, only the ready and matching policy with the highest precedence value (e.g., 2 is higher than 1) will have its policy action periodically executed on 'this element'. When a policy is active on an element but the condition ceases to match the element, its action (if currently running) will be allowed to finish and then the condition-matching ready policy with the next-highest precedence will immediately become active (and have its action run immediately). If the condition of a higher-precedence ready policy suddenly begins matching an element, the previously-active policy's action (if currently running) will be allowed to finish and then the higher precedence policy will immediately become active. Its action will run immediately, and any lower-precedence matching policy will not be active anymore. In the case where multiple ready policies share the highest value, it is an implementation-dependent matter as to which single policy action will be chosen. Note that if it is necessary to take certain actions after a policy is no longer active on an element, these actions should be included in a lower-precedence policy that is in the same precedence group.
.1.3.6.1.2.1.124.1.1.5,POLICY-BASED-MANAGEMENT-MIB::pmPolicySchedule,Unsigned32,read-create,,current,,This policy will be ready if any of the associated schedule entries are active. If the value of this object is 0, this policy is always ready. If the value of this object is non-zero but doesn't refer to a schedule group that includes an active schedule, then the policy will not be ready, even if this is due to a misconfiguration of this object or the pmSchedTable.
.1.3.6.1.2.1.124.1.1.6,POLICY-BASED-MANAGEMENT-MIB::pmPolicyElementTypeFilter,OCTET,read-create,,current,,This object specifies the element types for which this policy can be executed. The format of this object will be a sequence of pmElementTypeRegOIDPrefix values, encoded in the following BNF form: elementTypeFilter: oid [ ';' oid ]* oid: subid [ '.' subid ]* subid: '0' | decimal_constant For example, to register for the policy to be run on all interface elements, the 'ifEntry' element type will be registered as '1.3.6.1.2.1.2.2.1'. If a value is included that does not represent a registered pmElementTypeRegOIDPrefix, then that value will be ignored.
.1.3.6.1.2.1.124.1.1.7,POLICY-BASED-MANAGEMENT-MIB::pmPolicyConditionScriptIndex,Unsigned32,read-only,,current,,A pointer to the row or rows in the pmPolicyCodeTable that contain the condition code for this policy. When a policy entry is created, a pmPolicyCodeIndex value unused by this policy's adminGroup will be assigned to this object. A policy condition is one or more PolicyScript statements that result(s) in a boolean value that represents whether an element is a member of a set of elements upon which an action is to be performed. If a policy is ready and the condition returns true for an element of a proper element type, and if no higher-precedence policy should be active, then the policy is active on that element. Condition evaluation stops immediately when any run-time exception is detected, and the policyAction is not executed. The policyCondition is evaluated for various elements. Any element for which the policyCondition returns any nonzero value will match the condition and will have the associated policyAction executed on that element unless a higher-precedence policy in the same precedence group also matches 'this element'. If the condition object is empty (contains no code) or otherwise does not return a value, the element will not be matched. When this condition is executed, if SNMP requests are made to the local system and secModel/secName/secLevel aren't specified, access to objects is under the security credentials of the requester who most recently modified the associated pmPolicyAdminStatus object. If SNMP requests are made in which secModel/secName/secLevel are specified, then the specified credentials are retrieved from the local configuration datastore only if VACM is configured to allow access to the requester who most recently modified the associated pmPolicyAdminStatus object. See the Security Considerations section for more information.
.1.3.6.1.2.1.124.1.1.8,POLICY-BASED-MANAGEMENT-MIB::pmPolicyActionScriptIndex,Unsigned32,read-only,,current,,A pointer to the row or rows in the pmPolicyCodeTable that contain the action code for this policy. When a policy entry is created, a pmPolicyCodeIndex value unused by this policy's adminGroup will be assigned to this object. A PolicyAction is an operation performed on a set of elements for which the policy is active. Action evaluation stops immediately when any run-time exception is detected. When this condition is executed, if SNMP requests are made to the local system and secModel/secName/secLevel aren't specified, access to objects is under the security credentials of the requester who most recently modified the associated pmPolicyAdminStatus object. If SNMP requests are made in which secModel/secName/secLevel are specified, then the specified credentials are retrieved from the local configuration datastore only if VACM is configured to allow access to the requester who most recently modified the associated pmPolicyAdminStatus object. See the Security Considerations section for more information.
.1.3.6.1.2.1.124.1.1.9,POLICY-BASED-MANAGEMENT-MIB::pmPolicyParameters,OCTET,read-create,,current,,From time to time, policy scripts may seek one or more parameters (e.g., site-specific constants). These parameters may be installed with the script in this object and are accessible to the script via the getParameters() function. If it is necessary for multiple parameters to be passed to the script, the script can choose whatever encoding/delimiting mechanism is most appropriate.
.1.3.6.1.2.1.124.1.1.10,POLICY-BASED-MANAGEMENT-MIB::pmPolicyConditionMaxLatency,Unsigned32,read-create,,current,,Every element under the control of this agent is re-checked periodically to see whether it is under control of this policy by re-running the condition for this policy. This object lets the manager control the maximum amount of time that may pass before an element is re-checked. In other words, in any given interval of this duration, all elements must be re-checked. Note that how the policy agent schedules the checking of various elements within this interval is an implementation-dependent matter. Implementations may wish to re-run a condition more quickly if they note a change to the role strings for an element.
.1.3.6.1.2.1.124.1.1.11,POLICY-BASED-MANAGEMENT-MIB::pmPolicyActionMaxLatency,Unsigned32,read-create,,current,,Every element that matches this policy's condition and is therefore under control of this policy will have this policy's action executed periodically to ensure that the element remains in the state dictated by the policy. This object lets the manager control the maximum amount of time that may pass before an element has the action run on it. In other words, in any given interval of this duration, all elements under control of this policy must have the action run on them. Note that how the policy agent schedules the policy action on various elements within this interval is an implementation-dependent matter.
.1.3.6.1.2.1.124.1.1.12,POLICY-BASED-MANAGEMENT-MIB::pmPolicyMaxIterations,Unsigned32,read-create,,current,,If a condition or action script iterates in loops too many times in one invocation, the execution environment may consider it in an infinite loop or otherwise not acting as intended and may be terminated by the execution environment. The execution environment will count the cumulative number of times all 'for' or 'while' loops iterated and will apply a threshold to determine when to terminate the script. What threshold the execution environment uses is an implementation-dependent manner, but the value of this object SHOULD be the basis for choosing the threshold for each script. The value of this object represents a policy-specific threshold and can be tuned for policies of varying workloads. If this value is zero, no threshold will be enforced except for any implementation-dependent maximum. Regardless of this value, the agent is allowed to terminate any script invocation that exceeds a local CPU or memory limitation. Note that the condition and action invocations are tracked separately.
.1.3.6.1.2.1.124.1.1.13,POLICY-BASED-MANAGEMENT-MIB::pmPolicyDescription,OCTET,read-create,,current,,A description of this rule and its significance, typically provided by a human.
.1.3.6.1.2.1.124.1.1.14,POLICY-BASED-MANAGEMENT-MIB::pmPolicyMatches,Gauge32,read-only,,current,,The number of elements that, in their most recent execution of the associated condition, were matched by the condition.
.1.3.6.1.2.1.124.1.1.15,POLICY-BASED-MANAGEMENT-MIB::pmPolicyAbnormalTerminations,Gauge32,read-only,,current,,The number of elements that, in their most recent execution of the associated condition or action, have experienced a run-time exception and terminated abnormally. Note that if a policy was experiencing a run-time exception while processing a particular element but runs normally on a subsequent invocation, this number can decline.
.1.3.6.1.2.1.124.1.1.16,POLICY-BASED-MANAGEMENT-MIB::pmPolicyExecutionErrors,Counter32,read-only,,current,,The total number of times that execution of this policy's condition or action has been terminated due to run-time exceptions.
.1.3.6.1.2.1.124.1.1.17,POLICY-BASED-MANAGEMENT-MIB::pmPolicyDebugging,INTEGER,read-create,,current,off(1):on(2),The status of debugging for this policy. If this is turned on(2), log entries will be created in the pmDebuggingTable for each run-time exception that is experienced by this policy.
.1.3.6.1.2.1.124.1.1.18,POLICY-BASED-MANAGEMENT-MIB::pmPolicyAdminStatus,INTEGER,read-create,,current,disabled(1):enabled(2):enabledAutoRemove(3),The administrative status of this policy. The policy will be valid only if the associated pmPolicyRowStatus is set to active(1) and this object is set to enabled(2) or enabledAutoRemove(3). If this object is set to enabledAutoRemove(3), the next time the associated schedule moves from the active state to the inactive state, this policy will immediately be deleted, including any associated entries in the pmPolicyCodeTable. The following related objects may not be changed unless this object is set to disabled(1): pmPolicyPrecedenceGroup, pmPolicyPrecedence, pmPolicySchedule, pmPolicyElementTypeFilter, pmPolicyConditionScriptIndex, pmPolicyActionScriptIndex, pmPolicyParameters, and any pmPolicyCodeTable row referenced by this policy. In order to change any of these parameters, the policy must be moved to the disabled(1) state, changed, and then re-enabled. When this policy moves to either enabled state from the disabled state, any cached values of policy condition must be erased, and any Policy or PolicyElement scratchpad values for this policy should be removed. Policy execution will begin by testing the policy condition on all appropriate elements.
.1.3.6.1.2.1.124.1.1.19,POLICY-BASED-MANAGEMENT-MIB::pmPolicyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this policy and any associated entries in the pmPolicyCodeTable are kept in volatile storage and lost upon reboot or if this row is backed up by non-volatile or permanent storage. If the value of this object is 'permanent', the values for the associated pmPolicyAdminStatus object must remain writable.
.1.3.6.1.2.1.124.1.1.20,POLICY-BASED-MANAGEMENT-MIB::pmPolicyRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status of this pmPolicyEntry. The status may not be set to active if any of the related entries in the pmPolicyCode table do not have a status of active or if any of the objects in this row are not set to valid values. Only the following objects may be modified while in the active state: pmPolicyParameters pmPolicyConditionMaxLatency pmPolicyActionMaxLatency pmPolicyDebugging pmPolicyAdminStatus If this row is deleted, any associated entries in the pmPolicyCodeTable will be deleted as well.
.1.3.6.1.2.1.124.2,POLICY-BASED-MANAGEMENT-MIB::pmPolicyCodeTable,,not-accessible,,current,,The pmPolicyCodeTable stores the code for policy conditions and actions. An example of the relationships between the code table and the policy table follows: pmPolicyTable AdminGroup Index ConditionScriptIndex ActionScriptIndex A '' 1 1 2 B 'oper' 1 1 2 C 'oper' 2 3 4 pmPolicyCodeTable AdminGroup ScriptIndex Segment Note '' 1 1 Filter for policy A '' 2 1 Action for policy A 'oper' 1 1 Filter for policy B 'oper' 2 1 Action 1/2 for policy B 'oper' 2 2 Action 2/2 for policy B 'oper' 3 1 Filter for policy C 'oper' 4 1 Action for policy C In this example, there are 3 policies: 1 in the '' adminGroup, and 2 in the 'oper' adminGroup. Policy A has been assigned script indexes 1 and 2 (these script indexes are assigned out of a separate pool per adminGroup), with 1 code segment each for the filter and the action. Policy B has been assigned script indexes 1 and 2 (out of the pool for the 'oper' adminGroup). While the filter has 1 segment, the action is longer and is loaded into 2 segments. Finally, Policy C has been assigned script indexes 3 and 4, with 1 code segment each for the filter and the action.
.1.3.6.1.2.1.124.2.1,POLICY-BASED-MANAGEMENT-MIB::pmPolicyCodeEntry,,not-accessible,pmPolicyAdminGroup:pmPolicyCodeScriptIndex:pmPolicyCodeSegment,current,,An entry in the policy code table representing one code segment. Entries that share a common AdminGroup/ScriptIndex pair make up a single script. Valid values of ScriptIndex are retrieved from pmPolicyConditionScriptIndex and pmPolicyActionScriptIndex after a pmPolicyEntry is created. Segments of code can then be written to this table with the learned ScriptIndex values. The StorageType of this entry is determined by the value of the associated pmPolicyStorageType. The pmPolicyAdminGroup element of the index represents the administrative group of the policy of which this code entry is a part.
.1.3.6.1.2.1.124.2.1.1,POLICY-BASED-MANAGEMENT-MIB::pmPolicyCodeScriptIndex,Unsigned32,not-accessible,,current,,A unique index for each policy condition or action. The code for each such condition or action may be composed of multiple entries in this table if the code cannot fit in one entry. Values of pmPolicyCodeScriptIndex may not be used unless they have previously been assigned in the pmPolicyConditionScriptIndex or pmPolicyActionScriptIndex objects.
.1.3.6.1.2.1.124.2.1.2,POLICY-BASED-MANAGEMENT-MIB::pmPolicyCodeSegment,Unsigned32,not-accessible,,current,,A unique index for each segment of a policy condition or action. When a policy condition or action spans multiple entries in this table, the code of that policy starts from the lowest-numbered segment and continues with increasing segment values until it ends with the highest-numbered segment.
.1.3.6.1.2.1.124.2.1.3,POLICY-BASED-MANAGEMENT-MIB::pmPolicyCodeText,OCTET,read-create,,current,,A segment of policy code (condition or action). Lengthy Policy conditions or actions may be stored in multiple segments in this table that share the same value of pmPolicyCodeScriptIndex. When multiple segments are used, it is recommended that each segment be as large as is practical. Entries in this table are associated with policies by values of the pmPolicyConditionScriptIndex and pmPolicyActionScriptIndex objects. If the status of the related policy is active, then this object may not be modified.
.1.3.6.1.2.1.124.2.1.4,POLICY-BASED-MANAGEMENT-MIB::pmPolicyCodeStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this code entry. Entries in this table are associated with policies by values of the pmPolicyConditionScriptIndex and pmPolicyActionScriptIndex objects. If the status of the related policy is active, then this object can not be modified (i.e., deleted or set to notInService), nor may new entries be created. If the status of this object is active, no objects in this row may be modified.
.1.3.6.1.2.1.124.3,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegTable,,not-accessible,,current,,A registration table for element types managed by this system. The Element Type Registration table allows the manager to learn what element types are being managed by the system and to register new types, if necessary. An element type is registered by providing the OID of an SNMP object (i.e., without the instance). Each SNMP instance that exists under that object is a distinct element. The index of the element is the index part of the discovered OID. This index will be supplied to policy conditions and actions so that this code can inspect and configure the element. For example, this table might contain the following entries. The first three are agent-installed, and the 4th was downloaded by a management station: Note that agents may automatically configure elements in this table for frequently used element types (interfaces, circuits, etc.). In particular, it may configure elements for whom discovery is optimized in one or both of the following ways: 1. The agent may discover elements by scanning internal data structures as opposed to issuing local SNMP requests. It is possible to recreate the exact semantics described in this table even if local SNMP requests are not issued. 2. The agent may receive asynchronous notification of new elements (for example, 'card inserted') and use that information to instantly create elements rather than through polling. A similar feature might be available for the deletion of elements. Note that the disposition of agent-installed entries is described by the pmPolicyStorageType object.
.1.3.6.1.2.1.124.3.1,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegEntry,,not-accessible,pmElementTypeRegOIDPrefix,current,,A registration of an element type. Note that some values of this table's index may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such values.
.1.3.6.1.2.1.124.3.1.2,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegOIDPrefix,OBJECT,not-accessible,,current,,This OBJECT IDENTIFIER value identifies a table in which all elements of this type will be found. Every row in the referenced table will be treated as an element for the period of time that it remains in the table. The agent will then execute policy conditions and actions as appropriate on each of these elements. This object identifier value is specified down to the 'entry' component (e.g., ifEntry) of the identifier. The index of each discovered row will be passed to each invocation of the policy condition and policy action. The actual mechanism by which instances are discovered is implementation dependent. Periodic walks of the table to discover the rows in the table is one such mechanism. This mechanism has the advantage that it can be performed by an agent with no knowledge of the names, syntax, or semantics of the MIB objects in the table. This mechanism also serves as the reference design. Other implementation-dependent mechanisms may be implemented that are more efficient (perhaps because they are hard coded) or that don't require polling. These mechanisms must discover the same elements as would the table-walking reference design. This object can contain a OBJECT IDENTIFIER, '0.0'. '0.0' represents the single instance of the system itself and provides an execution context for policies to operate on the 'system element' and on MIB objects modeled as scalars. For example, '0.0' gives an execution context for policy-based selection of the operating system code version (likely modeled as a scalar MIB object). The element type '0.0' always exists; as a consequence, no actual discovery will take place, and the pmElementTypeRegMaxLatency object will have no effect for the '0.0' element type. However, if the '0.0' element type is not registered in the table, policies will not be executed on the '0.0' element. When a policy is invoked on behalf of a '0.0' entry in this table, the element name will be '0.0', and there is no index of 'this element' (in other words, it has zero length). As this object is used in the index for the pmElementTypeRegTable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.3.1.3,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegMaxLatency,Unsigned32,read-create,,current,,The PM agent is responsible for discovering new elements of types that are registered. This object lets the manager control the maximum amount of time that may pass between the time an element is created and when it is discovered. In other words, in any given interval of this duration, all new elements must be discovered. Note that how the policy agent schedules the checking of various elements within this interval is an implementation-dependent matter.
.1.3.6.1.2.1.124.3.1.4,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegDescription,OCTET,read-create,,current,,A descriptive label for this registered type.
.1.3.6.1.2.1.124.3.1.5,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this row is kept in volatile storage and lost upon reboot or backed up by non-volatile or permanent storage. If the value of this object is 'permanent', no values in the associated row have to be writable.
.1.3.6.1.2.1.124.3.1.6,POLICY-BASED-MANAGEMENT-MIB::pmElementTypeRegRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this registration entry. If the value of this object is active, no objects in this row may be modified.
.1.3.6.1.2.1.124.4,POLICY-BASED-MANAGEMENT-MIB::pmRoleTable,,not-accessible,,current,,The pmRoleTable is a read-create table that organizes role strings sorted by element. This table is used to create and modify role strings and their associations, as well as to allow a management station to learn about the existence of roles and their associations. It is the responsibility of the agent to keep track of any re-indexing of the underlying SNMP elements and to continue to associate role strings with the element with which they were initially configured. Policy MIB agents that have elements in multiple local SNMP contexts have to allow some roles to be assigned to elements in particular contexts. This is particularly true when some elements have the same names in different contexts and the context is required to disambiguate them. In those situations, a value for the pmRoleContextName may be provided. When a pmRoleContextName value is not provided, the assignment is to the element in the default context. Policy MIB agents that discover elements on other systems and execute policies on their behalf need to have access to role information for these remote elements. In such situations, role assignments for other systems can be stored in this table by providing values for the pmRoleContextEngineID parameters. For example: Example: element role context ctxEngineID #comment ifindex.1 gold local, default context ifindex.2 gold local, default context repeaterid.1 foo rptr1 local, rptr1 context repeaterid.1 bar rptr2 local, rptr2 context ifindex.1 gold '' A different system ifindex.1 gold '' B different system The agent must store role string associations in non-volatile storage.
.1.3.6.1.2.1.124.4.1,POLICY-BASED-MANAGEMENT-MIB::pmRoleEntry,,not-accessible,pmRoleElement:pmRoleContextName:pmRoleContextEngineID:pmRoleString,current,,A role string entry associates a role string with an individual element. Note that some combinations of index values may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.124.4.1.1,POLICY-BASED-MANAGEMENT-MIB::pmRoleElement,OBJECT,not-accessible,,current,,The element with which this role string is associated. For example, if the element is interface 3, then this object will contain the OID for 'ifIndex.3'. If the agent assigns new indexes in the MIB table to represent the same underlying element (re-indexing), the agent will modify this value to contain the new index for the underlying element. As this object is used in the index for the pmRoleTable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.4.1.2,POLICY-BASED-MANAGEMENT-MIB::pmRoleContextName,OCTET,not-accessible,,current,,If the associated element is not in the default SNMP context for the target system, this object is used to identify the context. If the element is in the default context, this object is equal to the empty string.
.1.3.6.1.2.1.124.4.1.3,POLICY-BASED-MANAGEMENT-MIB::pmRoleContextEngineID,OCTET,not-accessible,,current,,If the associated element is on a remote system, this object is used to identify the remote system. This object contains the contextEngineID of the system for which this role string assignment is valid. If the element is on the local system this object will be the empty string.
.1.3.6.1.2.1.124.4.1.4,POLICY-BASED-MANAGEMENT-MIB::pmRoleString,OCTET,not-accessible,,current,,The role string that is associated with an element through this table. All role strings must have been successfully transformed by Stringprep RFC 3454. Management stations must perform this translation and must only set this object to string values that have been transformed. A role string is an administratively specified characteristic of a managed element (for example, an interface). It is a selector for policy rules, that determines the applicability of the rule to a particular managed element.
.1.3.6.1.2.1.124.4.1.5,POLICY-BASED-MANAGEMENT-MIB::pmRoleStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this role string. If the value of this object is active, no object in this row may be modified.
.1.3.6.1.2.1.124.5,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesTable,,not-accessible,,current,,The pmCapabilitiesTable contains a description of the inherent capabilities of the system so that management stations can learn of an agent's capabilities and differentially install policies based on the capabilities. Capabilities are expressed at the system level. There can be variation in how capabilities are realized from one vendor or model to the next. Management systems should consider these differences before selecting which policy to install in a system.
.1.3.6.1.2.1.124.5.1,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesEntry,,not-accessible,pmCapabilitiesType,current,,A capabilities entry holds an OID indicating support for a particular capability. Capabilities may include hardware and software functions and the implementation of MIB Modules. The semantics of the OID are defined in the description of pmCapabilitiesType. Entries appear in this table if any element in the system has a specific capability. A capability should appear in this table only once, regardless of the number of elements in the system with that capability. An entry is removed from this table when the last element in the system that has the capability is removed. In some cases, capabilities are dynamic and exist only in software. This table should have an entry for the capability even if there are no current instances. Examples include systems with database or WEB services. While the system has the ability to create new databases or WEB services, the entry should exist. In these cases, the ability to create these services could come from other processes that are running in the system, even though there are no currently open databases or WEB servers running. Capabilities may include the implementation of MIB Modules but need not be limited to those that represent MIB Modules with one or more configurable objects. It may also be valuable to include entries for capabilities that do not include configuration objects, as that information, in combination with other entries in this table, might be used by the management software to determine whether to install a policy. Vendor software may also add entries in this table to express capabilities from their private branch. Note that some values of this table's index may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such values.
.1.3.6.1.2.1.124.5.1.1,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesType,OBJECT,read-only,,current,,There are three types of OIDs that may be present in the pmCapabilitiesType object: 1) The OID of a MODULE-COMPLIANCE macro that represents the highest level of compliance realized by the agent for that MIB Module. For example, an agent that implements the OSPF MIB Module at the highest level of compliance would have the value of '1.3.6.1.2.1.14.15.2' in the pmCapabilitiesType object. For software that realizes standard MIB Modules that do not have compliance statements, the base OID of the MIB Module should be used instead. If the OSPF MIB Module had not been created with a compliance statement, then the correct value of the pmCapabilitiesType would be '1.3.6.1.2.1.14'. In the cases where multiple compliance statements in a MIB Module are supported by the agent, and where one compliance statement does not by definition include the other, each of the compliance OIDs would have entries in this table. MIB Documents can contain more than one MIB Module. In the case of OSPF, there is a second MIB Module that describes notifications for the OSPF Version 2 Protocol. If the agent also realizes these functions, an entry will also exist for those capabilities in this table. 2) Vendors should install OIDs in this table that represent vendor-specific capabilities. These capabilities can be expressed just as those described above for MIB Modules on the standards track. In addition, vendors may install any OID they desire from their registered branch. The OIDs may be at any level of granularity, from the root of their entire branch to an instance of a single OID. There is no restriction on the number of registrations they may make, though care should be taken to avoid unnecessary entries. 3) OIDs that represent one capability or a collection of capabilities that could be any collection of MIB Objects or hardware or software functions may be created in working groups and registered in a MIB Module. Other entities (e.g., vendors) may also make registrations. Software will register these standard capability OIDs, as well as vendor specific OIDs. If the OID for a known capability is not present in the table, then it should be assumed that the capability is not implemented. As this object is used in the index for the pmCapabilitiesTable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.6,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesOverrideTable,,not-accessible,,current,,The pmCapabilitiesOverrideTable allows management stations to override pmCapabilitiesTable entries that have been registered by the agent. This facility can be used to avoid situations in which managers in the network send policies to a system that has advertised a capability in the pmCapabilitiesTable but that should not be installed on this particular system. One example could be newly deployed equipment that is still in a trial state in a trial state or resources reserved for some other administrative reason. This table can also be used to override entries in the pmCapabilitiesTable through the use of the pmCapabilitiesOverrideState object. Capabilities can also be declared available in this table that were not registered in the pmCapabilitiesTable. A management application can make an entry in this table for any valid OID and declare the capability available by setting the pmCapabilitiesOverrideState for that row to valid(1).
.1.3.6.1.2.1.124.6.1,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesOverrideEntry,,not-accessible,pmCapabilitiesOverrideType,current,,An entry in this table indicates whether a particular capability is valid or invalid. Note that some values of this table's index may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such values.
.1.3.6.1.2.1.124.6.1.1,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesOverrideType,OBJECT,not-accessible,,current,,This is the OID of the capability that is declared valid or invalid by the pmCapabilitiesOverrideState value for this row. Any valid OID, as described in the pmCapabilitiesTable, is permitted in the pmCapabilitiesOverrideType object. This means that capabilities can be expressed at any level, from a specific instance of an object to a table or entire module. There are no restrictions on whether these objects are from standards track MIB documents or in the private branch of the MIB. If an entry exists in this table for which there is a corresponding entry in the pmCapabilitiesTable, then this entry shall have precedence over the entry in the pmCapabilitiesTable. All entries in this table must be preserved across reboots. As this object is used in the index for the pmCapabilitiesOverrideTable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.6.1.2,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesOverrideState,INTEGER,read-create,,current,invalid(1):valid(2),A pmCapabilitiesOverrideState of invalid indicates that management software should not send policies to this system for the capability identified in the pmCapabilitiesOverrideType for this row of the table. This behavior is the same whether the capability represented by the pmCapabilitiesOverrideType exists only in this table (that is, it was installed by an external management application) or exists in this table as well as the pmCapabilitiesTable. This would be the case when a manager wanted to disable a capability that the native management system found and registered in the pmCapabilitiesTable. An entry in this table that has a pmCapabilitiesOverrideState of valid should be treated as though it appeared in the pmCapabilitiesTable. If the entry also exists in the pmCapabilitiesTable in the pmCapabilitiesType object, and if the value of this object is valid, then the system shall operate as though this entry did not exist and policy installations and executions will continue in a normal fashion.
.1.3.6.1.2.1.124.6.1.3,POLICY-BASED-MANAGEMENT-MIB::pmCapabilitiesOverrideRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status of this pmCapabilitiesOverrideEntry. If the value of this object is active, no object in this row may be modified.
.1.3.6.1.2.1.124.7,POLICY-BASED-MANAGEMENT-MIB::pmSchedLocalTime,OCTET,read-only,,current,,The local time used by the scheduler. Schedules that refer to calendar time will use the local time indicated by this object. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time.
.1.3.6.1.2.1.124.8,POLICY-BASED-MANAGEMENT-MIB::pmSchedTable,,not-accessible,,current,,This table defines schedules for policies.
.1.3.6.1.2.1.124.8.1,POLICY-BASED-MANAGEMENT-MIB::pmSchedEntry,,not-accessible,pmSchedIndex,current,,An entry describing a particular schedule. Unless noted otherwise, writable objects of this row can be modified independently of the current value of pmSchedRowStatus, pmSchedAdminStatus and pmSchedOperStatus. In particular, it is legal to modify pmSchedWeekDay, pmSchedMonth, and pmSchedDay when pmSchedRowStatus is active.
.1.3.6.1.2.1.124.8.1.1,POLICY-BASED-MANAGEMENT-MIB::pmSchedIndex,Unsigned32,not-accessible,,current,,The locally unique, administratively assigned index for this scheduling entry.
.1.3.6.1.2.1.124.8.1.2,POLICY-BASED-MANAGEMENT-MIB::pmSchedGroupIndex,Unsigned32,read-create,,current,,The locally unique, administratively assigned index for the schedule group this scheduling entry belongs to. To assign multiple schedule entries to the same group, the pmSchedGroupIndex of each entry in the group will be set to the same value. This pmSchedGroupIndex value must be equal to the pmSchedIndex of one of the entries in the group. If the entry whose pmSchedIndex equals the pmSchedGroupIndex for the group is deleted, the agent will assign a new pmSchedGroupIndex to all remaining members of the group. If an entry is not a member of a group, its pmSchedGroupIndex must be assigned to the value of its pmSchedIndex. Policies that are controlled by a group of schedule entries are active when any schedule in the group is active.
.1.3.6.1.2.1.124.8.1.3,POLICY-BASED-MANAGEMENT-MIB::pmSchedDescr,OCTET,read-create,,current,,The human-readable description of the purpose of this scheduling entry.
.1.3.6.1.2.1.124.8.1.4,POLICY-BASED-MANAGEMENT-MIB::pmSchedTimePeriod,OCTET,read-create,,current,,The overall range of calendar dates and times over which this schedule is active. It is stored in a slightly extended version of the format for a 'period-explicit' defined in RFC 2445. This format is expressed as a string representing the starting date and time, in which the character 'T' indicates the beginning of the time portion, followed by the solidus character, '/', followed by a similar string representing an end date and time. The start of the period MUST be before the end of the period. Date-Time values are expressed as substrings of the form 'yyyymmddThhmmss'. For example: 20000101T080000/20000131T130000 January 1, 2000, 0800 through January 31, 2000, 1PM The 'Date with UTC time' format defined in RFC 2445 in which the Date-Time string ends with the character 'Z' is not allowed. This 'period-explicit' format is also extended to allow two special cases in which one of the Date-Time strings is replaced with a special string defined in RFC 2445: 1. If the first Date-Time value is replaced with the string 'THISANDPRIOR', then the value indicates that the schedule is active at any time prior to the Date-Time that appears after the '/'. 2. If the second Date-Time is replaced with the string 'THISANDFUTURE', then the value indicates that the schedule is active at any time after the Date-Time that appears before the '/'. Note that although RFC 2445 defines these two strings, they are not specified for use in the 'period-explicit' format. The use of these strings represents an extension to the 'period-explicit' format.
.1.3.6.1.2.1.124.8.1.5,POLICY-BASED-MANAGEMENT-MIB::pmSchedMonth,BITS,read-create,,current,january(0):february(1):march(2):april(3):may(4):june(5):july(6):august(7):september(8):october(9):november(10):december(11),Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the specific months within that time period when the schedule is active. Setting all bits will cause the schedule to act independently of the month.
.1.3.6.1.2.1.124.8.1.6,POLICY-BASED-MANAGEMENT-MIB::pmSchedDay,BITS,read-create,,current,d1(0):d2(1):d3(2):d4(3):d5(4):d6(5):d7(6):d8(7):d9(8):d10(9):d11(10):d12(11):d13(12):d14(13):d15(14):d16(15):d17(16):d18(17):d19(18):d20(19):d21(20):d22(21):d23(22):d24(23):d25(24):d26(25):d27(26):d28(27):d29(28):d30(29):d31(30):r1(31):r2(32):r3(33):r4(34):r5(35):r6(36):r7(37):r8(38):r9(39):r10(40):r11(41):r12(42):r13(43):r14(44):r15(45):r16(46):r17(47):r18(48):r19(49):r20(50):r21(51):r22(52):r23(53):r24(54):r25(55):r26(56):r27(57):r28(58):r29(59):r30(60):r31(61),Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the specific days of the month within that time period when the schedule is active. There are two sets of bits one can use to define the day within a month: Enumerations starting with the letter 'd' indicate a day in a month relative to the first day of a month. The first day of the month can therefore be specified by setting the bit d1(0), and d31(30) means the last day of a month with 31 days. Enumerations starting with the letter 'r' indicate a day in a month in reverse order, relative to the last day of a month. The last day in the month can therefore be specified by setting the bit r1(31), and r31(61) means the first day of a month with 31 days. Setting multiple bits will include several days in the set of possible days for this schedule. Setting all bits starting with the letter 'd' or all bits starting with the letter 'r' will cause the schedule to act independently of the day of the month.
.1.3.6.1.2.1.124.8.1.7,POLICY-BASED-MANAGEMENT-MIB::pmSchedWeekDay,BITS,read-create,,current,sunday(0):monday(1):tuesday(2):wednesday(3):thursday(4):friday(5):saturday(6),Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the specific days of the week within that time period when the schedule is active. Setting all bits will cause the schedule to act independently of the day of the week.
.1.3.6.1.2.1.124.8.1.8,POLICY-BASED-MANAGEMENT-MIB::pmSchedTimeOfDay,OCTET,read-create,,current,,Within the overall time period specified in the pmSchedTimePeriod object, the value of this object specifies the range of times in a day when the schedule is active. This value is stored in a format based on the RFC 2445 format for 'time': The character 'T' followed by a 'time' string, followed by the solidus character, '/', followed by the character 'T', followed by a second time string. The first time indicates the beginning of the range, and the second time indicates the end. Thus, this value takes the following form: 'Thhmmss/Thhmmss'. The second substring always identifies a later time than the first substring. To allow for ranges that span midnight, however, the value of the second string may be smaller than the value of the first substring. Thus, 'T080000/T210000' identifies the range from 0800 until 2100, whereas 'T210000/T080000' identifies the range from 2100 until 0800 of the following day. When a range spans midnight, by definition it includes parts of two successive days. When one of these days is also selected by either the MonthOfYearMask, DayOfMonthMask, and/or DayOfWeekMask, but the other day is not, then the policy is active only during the portion of the range that falls on the selected day. For example, if the range extends from 2100 until 0800, and the day of week mask selects Monday and Tuesday, then the policy is active during the following three intervals: From midnight Sunday until 0800 Monday From 2100 Monday until 0800 Tuesday From 2100 Tuesday until 23:59:59 Tuesday Setting this value to 'T000000/T235959' will cause the schedule to act independently of the time of day.
.1.3.6.1.2.1.124.8.1.9,POLICY-BASED-MANAGEMENT-MIB::pmSchedLocalOrUtc,INTEGER,read-create,,current,localTime(1):utcTime(2),This object indicates whether the times represented in the TimePeriod object and in the various Mask objects represent local times or UTC times.
.1.3.6.1.2.1.124.8.1.10,POLICY-BASED-MANAGEMENT-MIB::pmSchedStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this schedule entry is kept in volatile storage and lost upon reboot or backed up by non-volatile or permanent storage. Conceptual rows having the value 'permanent' must allow write access to the columnar objects pmSchedDescr, pmSchedWeekDay, pmSchedMonth, and pmSchedDay. If the value of this object is 'permanent', no values in the associated row have to be writable.
.1.3.6.1.2.1.124.8.1.11,POLICY-BASED-MANAGEMENT-MIB::pmSchedRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this schedule entry. If the value of this object is active, no object in this row may be modified.
.1.3.6.1.2.1.124.9,POLICY-BASED-MANAGEMENT-MIB::pmTrackingPETable,,not-accessible,,current,,The pmTrackingPETable describes what elements are active (under control of) a policy. This table is indexed in order to optimize retrieval of the entire status for a given policy.
.1.3.6.1.2.1.124.9.1,POLICY-BASED-MANAGEMENT-MIB::pmTrackingPEEntry,,not-accessible,pmPolicyIndex:pmTrackingPEElement:pmTrackingPEContextName:pmTrackingPEContextEngineID,current,,An entry in the pmTrackingPETable. The pmPolicyIndex in the index specifies the policy tracked by this entry. Note that some combinations of index values may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.124.9.1.1,POLICY-BASED-MANAGEMENT-MIB::pmTrackingPEElement,OBJECT,not-accessible,,current,,The element that is acted upon by the associated policy. As this object is used in the index for the pmTrackingPETable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.9.1.2,POLICY-BASED-MANAGEMENT-MIB::pmTrackingPEContextName,OCTET,not-accessible,,current,,If the associated element is not in the default SNMP context for the target system, this object is used to identify the context. If the element is in the default context, this object is equal to the empty string.
.1.3.6.1.2.1.124.9.1.3,POLICY-BASED-MANAGEMENT-MIB::pmTrackingPEContextEngineID,OCTET,not-accessible,,current,,If the associated element is on a remote system, this object is used to identify the remote system. This object contains the contextEngineID of the system on which the associated element resides. If the element is on the local system, this object will be the empty string.
.1.3.6.1.2.1.124.9.1.4,POLICY-BASED-MANAGEMENT-MIB::pmTrackingPEInfo,BITS,read-only,,current,actionSkippedDueToPrecedence(0):conditionRunTimeException(1):conditionUserSignal(2):actionRunTimeException(3):actionUserSignal(4),This object returns information about the previous policy script executions. If the actionSkippedDueToPrecedence(1) bit is set, the last execution of the associated policy condition returned non-zero, but the action is not active, because it was trumped by a matching policy condition in the same precedence group with a higher precedence value. If the conditionRunTimeException(2) bit is set, the last execution of the associated policy condition encountered a run-time exception and aborted. If the conditionUserSignal(3) bit is set, the last execution of the associated policy condition called the signalError() function. If the actionRunTimeException(4) bit is set, the last execution of the associated policy action encountered a run-time exception and aborted. If the actionUserSignal(5) bit is set, the last execution of the associated policy action called the signalError() function. Entries will only exist in this table of one or more bits are set. In particular, if an entry does not exist for a particular policy/element combination, it can be assumed that the policy's condition did not match 'this element'.
.1.3.6.1.2.1.124.10,POLICY-BASED-MANAGEMENT-MIB::pmTrackingEPTable,,not-accessible,,current,,The pmTrackingEPTable describes what policies are controlling an element. This table is indexed in order to optimize retrieval of the status of all policies active for a given element.
.1.3.6.1.2.1.124.10.1,POLICY-BASED-MANAGEMENT-MIB::pmTrackingEPEntry,,not-accessible,pmTrackingEPElement:pmTrackingEPContextName:pmTrackingEPContextEngineID:pmPolicyIndex,current,,An entry in the pmTrackingEPTable. Entries exist for all element/policy combinations for which the policy's condition matches and only if the schedule for the policy is active. The pmPolicyIndex in the index specifies the policy tracked by this entry. Note that some combinations of index values may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.124.10.1.1,POLICY-BASED-MANAGEMENT-MIB::pmTrackingEPElement,OBJECT,not-accessible,,current,,The element acted upon by the associated policy. As this object is used in the index for the pmTrackingEPTable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.10.1.2,POLICY-BASED-MANAGEMENT-MIB::pmTrackingEPContextName,OCTET,not-accessible,,current,,If the associated element is not in the default SNMP context for the target system, this object is used to identify the context. If the element is in the default context, this object is equal to the empty string.
.1.3.6.1.2.1.124.10.1.3,POLICY-BASED-MANAGEMENT-MIB::pmTrackingEPContextEngineID,OCTET,not-accessible,,current,,If the associated element is on a remote system, this object is used to identify the remote system. This object contains the contextEngineID of the system on which the associated element resides. If the element is on the local system, this object will be the empty string.
.1.3.6.1.2.1.124.10.1.4,POLICY-BASED-MANAGEMENT-MIB::pmTrackingEPStatus,INTEGER,read-write,,current,on(1):forceOff(2),This entry will only exist if the calendar for the policy is active and if the associated policyCondition returned 1 for 'this element'. A policy can be forcibly disabled on a particular element by setting this value to forceOff(2). The agent should then act as though the policyCondition failed for 'this element'. The forceOff(2) state will persist (even across reboots) until this value is set to on(1) by a management request. The forceOff(2) state may be set even if the entry does not previously exist so that future policy invocations can be avoided. Unless forcibly disabled, if this entry exists, its value will be on(1).
.1.3.6.1.2.1.124.11,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingTable,,not-accessible,,current,,Policies that have debugging turned on will generate a log entry in the policy debugging table for every runtime exception that occurs in either the condition or action code. The pmDebuggingTable logs debugging messages when policies experience run-time exceptions in either the condition or action code and the associated pmPolicyDebugging object has been turned on. The maximum number of debugging entries that will be stored and the maximum length of time an entry will be kept are an implementation-dependent manner. If entries must be discarded to make room for new entries, the oldest entries must be discarded first. If the system restarts, all debugging entries may be deleted.
.1.3.6.1.2.1.124.11.1,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingEntry,,not-accessible,pmPolicyIndex:pmDebuggingElement:pmDebuggingContextName:pmDebuggingContextEngineID:pmDebuggingLogIndex,current,,An entry in the pmDebuggingTable. The pmPolicyIndex in the index specifies the policy that encountered the exception that led to this log entry. Note that some combinations of index values may result in an instance name that exceeds a length of 128 sub-identifiers, which exceeds the maximum for the SNMP protocol. Implementations should take care to avoid such combinations.
.1.3.6.1.2.1.124.11.1.1,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingElement,OBJECT,not-accessible,,current,,The element the policy was executing on when it encountered the error that led to this log entry. For example, if the element is interface 3, then this object will contain the OID for 'ifIndex.3'. As this object is used in the index for the pmDebuggingTable, users of this table should be careful not to create entries that would result in instance names with more than 128 sub-identifiers.
.1.3.6.1.2.1.124.11.1.2,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingContextName,OCTET,not-accessible,,current,,If the associated element is not in the default SNMP context for the target system, this object is used to identify the context. If the element is in the default context, this object is equal to the empty string.
.1.3.6.1.2.1.124.11.1.3,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingContextEngineID,OCTET,not-accessible,,current,,If the associated element is on a remote system, this object is used to identify the remote system. This object contains the contextEngineID of the system on which the associated element resides. If the element is on the local system, this object will be the empty string.
.1.3.6.1.2.1.124.11.1.4,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingLogIndex,Unsigned32,not-accessible,,current,,A unique index for this log entry among other log entries for this policy/element combination.
.1.3.6.1.2.1.124.11.1.5,POLICY-BASED-MANAGEMENT-MIB::pmDebuggingMessage,OCTET,read-only,,current,,An error message generated by the policy execution environment. It is recommended that this message include the time of day when the message was generated, if known.
.1.3.6.1.2.1.124.12,POLICY-BASED-MANAGEMENT-MIB::pmConformance,,,,,,
.1.3.6.1.2.1.124.12.1,POLICY-BASED-MANAGEMENT-MIB::pmCompliances,,,,,,
.1.3.6.1.2.1.124.12.1.1,POLICY-BASED-MANAGEMENT-MIB::pmCompliance,,,,,,Describes the requirements for conformance to the Policy-Based Management MIB
.1.3.6.1.2.1.124.12.2,POLICY-BASED-MANAGEMENT-MIB::pmGroups,,,,,,
.1.3.6.1.2.1.124.12.2.1,POLICY-BASED-MANAGEMENT-MIB::pmPolicyManagementGroup,,,,,,Objects that allow for the creation and management of configuration policies.
.1.3.6.1.2.1.124.12.2.2,POLICY-BASED-MANAGEMENT-MIB::pmSchedGroup,,,,,,Objects that allow for the scheduling of policies.
.1.3.6.1.2.1.124.12.2.3,POLICY-BASED-MANAGEMENT-MIB::pmNotificationGroup,,,,,,Notifications sent by an Policy MIB agent.
.1.3.6.1.2.1.124.12.2.4,POLICY-BASED-MANAGEMENT-MIB::pmBaseFunctionLibrary,,,,,,
.1.3.6.1.2.1.125,DOCS-IETF-SUBMGT-MIB::docsSubMgt,,,,,,This is the CMTS centric subscriber management MIB for DOCSIS-compliant CMTS. It provides the objects to allow a Cable Modem Termination operator to control the IP addresses and protocols associated with subscribers' cable modems. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4036; see the RFC itself for full legal notices.
.1.3.6.1.2.1.125.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtObjects,,,,,,
.1.3.6.1.2.1.125.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlTable,,not-accessible,,current,,This table AUGMENTs the docsIfCmtsCmStatusTable, adding four WRITEable objects, as well as a read-only object, all of which reflect the state of subscriber management on a particular CM.
.1.3.6.1.2.1.125.1.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlEntry,,not-accessible,,current,,A row in the docsSubMgtCpeControlTable. All values are set at successful modem registration, either from the system default, or from objects included in the DOCSIS registration request sent upstream to the CMTS from the CM. The contents of this entry are meaningless unless the corresponding docsIfCmtsCmStatusValue (see reference) is registrationComplete(6). The persistence of this row is determined solely by the lifespan of the corresponding docsIfCmtsCmStatusEntry (normally StorageType=volatile).
.1.3.6.1.2.1.125.1.1.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlMaxCpeIp,Integer32,read-write,,current,,The number of simultaneous IP addresses permitted behind the CM. If this is set to zero, all CPE traffic from the CM is dropped. If the provisioning object corresponding to docsSubMgtCpeIpTable includes more CPE IP address entries for this modem than the value of this object, then this object is set to the count of the number of rows in docsSubMgtCpeIpTable that have the same docsIfCmtsCmStatusIndex value. (For example, if the CM has 5 IP addresses specified for it, this value is 5.) This limit applies to learned and DOCSIS-provisioned entries but not to entries added through some administrative process at the CMTS. If not set through DOCSIS provisioning, this object defaults to docsSubMgtCpeMaxIpDefault. Note that this object is only meaningful if docsSubMgtCpeControlActive is true.
.1.3.6.1.2.1.125.1.1.1.2,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlActive,INTEGER,read-write,,current,true(1):false(2),Controls the application of subscriber management to this cable modem. If this is set to true, CMTS-based CPE control is active, and all the actions required by the various filter tables and controls apply at the CMTS. If this is set to false, no subscriber management filtering is done at the CMTS (but other filters may apply). If not set through DOCSIS provisioning, this object defaults to docsSubMgtCpeActiveDefault.
.1.3.6.1.2.1.125.1.1.1.3,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlLearnable,INTEGER,read-write,,current,true(1):false(2),Controls whether the CMTS may learn (and pass traffic for) CPE IP addresses associated with a cable modem. If this is set to true, the CMTS may learn up to docsSubMgtMaxCpeIp addresses (less any DOCSIS-provisioned entries) related to this CM. Those IP addresses are added (by internal process) to the docsSubMgtCpeIpTable. The nature of the learning mechanism is not specified here. If not set through DOCSIS provisioning, this object defaults to docsSubMgtCpeLearnableDefault. Note that this object is only meaningful if docsSubMgtCpeControlActive is true.
.1.3.6.1.2.1.125.1.1.1.4,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlReset,INTEGER,read-write,,current,true(1):false(2),This object always returns false on read. If this object is set to true, the rows with 'learned' addresses in docsSubMgtCpeIpTable for this CM are deleted from that table.
.1.3.6.1.2.1.125.1.1.1.5,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeControlLastReset,TimeTicks,read-only,,current,,The value of sysUpTime when docsSubMgtCpeControlReset was last set true. Zero if never reset.
.1.3.6.1.2.1.125.1.2,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeMaxIpDefault,Integer32,read-write,,current,,The default value for docsSubMgtCpeControlMaxCpeIp if not signaled in the DOCSIS Registration request. This value should be treated as nonvolatile; if set, its value should persist across device resets.
.1.3.6.1.2.1.125.1.3,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeActiveDefault,INTEGER,read-write,,current,true(1):false(2),The default value for docsSubMgtCpeControlActive if not signaled in the DOCSIS Registration request. This value should be treated as nonvolatile; if set, its value should persist across device resets.
.1.3.6.1.2.1.125.1.4,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeLearnableDefault,INTEGER,read-write,,current,true(1):false(2),The default value for docsSubMgtCpeControlLearnable if not signaled in the DOCSIS Registration request. This value should be treated as nonvolatile; if set, its value should persist across device resets.
.1.3.6.1.2.1.125.1.5,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeIpTable,,not-accessible,,current,,A table of CPE IP addresses known on a per-CM basis.
.1.3.6.1.2.1.125.1.5.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeIpEntry,,not-accessible,docsIfCmtsCmStatusIndex:docsSubMgtCpeIpIndex,current,,An entry in the docsSubMgtCpeIpTable. The first index is the specific modem we're referring to, and the second index is the specific CPE IP entry.
.1.3.6.1.2.1.125.1.5.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeIpIndex,Integer32,not-accessible,,current,,The index of this CPE IP address relative to the indexed CM. An entry is created either through the included CPE IP addresses in the provisioning object, or via learning. If docsSubMgtCpeControlActive is true and a CMTS receives an IP packet from a CM that contains a source IP address that does not match one of the docsSubMgtCpeIpAddr entries for this CM, one of two things occurs. If the number of entries is less than docsSubMgtCpeControlMaxCpeIp, the source address is added to the table and the packet is forwarded. If the number of entries equals the docsSubMgtCpeControlMaxCpeIp, then the packet is dropped.
.1.3.6.1.2.1.125.1.5.1.2,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeIpAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of internet address of docsSubMgtCpeIpAddr.
.1.3.6.1.2.1.125.1.5.1.3,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeIpAddr,OCTET,read-only,,current,,The IP address either set from provisioning or learned via address gleaning or other forwarding means. See docsSubMgtCpeIpIndex for the mechanism. The type of this address is determined by the value of docsSubMgtCpeIpAddressType.
.1.3.6.1.2.1.125.1.5.1.4,DOCS-IETF-SUBMGT-MIB::docsSubMgtCpeIpLearned,INTEGER,read-only,,current,true(1):false(2),If true, this entry was learned from IP packets sent upstream rather than from the provisioning objects.
.1.3.6.1.2.1.125.1.6,DOCS-IETF-SUBMGT-MIB::docsSubMgtCmFilterTable,,not-accessible,,current,,Binds filter groups to modems, identifying for each modem the upstream and downstream filter groups that apply to packets for that modem. Normally, this table reflects the filter group values signaled by DOCSIS Registration, although values may be overridden by management action. For each of the columns in this table, zero is a distinguished value, indicating that the default filtering action is to be taken rather than that associated with a filter group number. Zero is used if the filter group is not signaled by DOCSIS registration.
.1.3.6.1.2.1.125.1.6.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCmFilterEntry,,not-accessible,,current,,Binds a filter group to each direction of traffic for a modem. The filters in this entry apply if docsSubMgtCpeControlActive is true. The contents of this entry are meaningless unless the corresponding docsIfCmtsCmStatusValue (see reference) is registrationComplete(6). The persistence of this row is determined solely by the lifespan of the corresponding docsIfCmtsCmStatusEntry (normally StorageType=volatile).
.1.3.6.1.2.1.125.1.6.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCmFilterSubDownstream,Integer32,read-write,,current,,The filter group applied to traffic destined for subscribers attached to the referenced CM. Upon row creation, this is set either to zero (use default classification, the diffServClfrElementSpecific=zeroDotZero row of diffServClfrElementTable) or to the value in the provisioning object sent upstream from the CM to the CMTS during registration. The value of this object is the same as that of the filter group index appearing as docsSubMgtFilterGroupIndex.
.1.3.6.1.2.1.125.1.6.1.2,DOCS-IETF-SUBMGT-MIB::docsSubMgtCmFilterSubUpstream,Integer32,read-write,,current,,The filter group applied to traffic originating from subscribers attached to the referenced CM. Upon row creation this is set to either zero (use default classification, the diffServClfrElementSpecific=zeroDotZero row of diffServClfrElementTable), or to the value in the provisioning object sent upstream from the CM to the CMTS. The value of this object is the same as that of the filter group index appearing as docsSubMgtFilterGroupIndex.
.1.3.6.1.2.1.125.1.6.1.3,DOCS-IETF-SUBMGT-MIB::docsSubMgtCmFilterCmDownstream,Integer32,read-write,,current,,The filter group applied to traffic destined for the referenced CM itself. Upon row creation this is set either to zero (use default classification, the diffServClfrElementSpecific=zeroDotZero row of diffServClfrElementTable), or to the value in the provisioning object sent upstream from the CM to the CMTS during registration. The value of this object is the same as that of the filter group index appearing as docsSubMgtFilterGroupIndex.
.1.3.6.1.2.1.125.1.6.1.4,DOCS-IETF-SUBMGT-MIB::docsSubMgtCmFilterCmUpstream,Integer32,read-write,,current,,The filter group applied to traffic originating from the referenced CM itself. This is set upon row creation to either zero (use default classification, the diffServClfrElementSpecific=zeroDotZero row of diffServClfrElementTable), or to the value in the provisioning object sent upstream from the CM to the CMTS during registration. The value of this object is the same as the filter group index appearing as docsSubMgtFilterGroupIndex.
.1.3.6.1.2.1.125.1.7,DOCS-IETF-SUBMGT-MIB::docsSubMgtFilterGroupTable,,not-accessible,,current,,Provides a collection of referenceable entries to which diffServClfrElementSpecific refers. This table provides filter group indices that can be compared with those signaled during DOCSIS registration. A packet matches an entry from this table if the packet originated from or is destined to a cable modem that registered this index as one of its four filter groups (see docsSubMgtCmFilterTable), and if the packet direction and MAC address select the use of this index among the four.
.1.3.6.1.2.1.125.1.7.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtFilterGroupEntry,,not-accessible,docsSubMgtFilterGroupIndex,current,,An entry only exists if needed by the diffServClfrElementEntry. A packet matches this entry if the packet's cable modem registered this index as one of its four filter groups (see docsSubMgtCmFilterTable) and if the packet direction and MAC address select the use of this index among the four.
.1.3.6.1.2.1.125.1.7.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtFilterGroupIndex,Integer32,read-only,,current,,The filter group index, from the set signaled at DOCSIS Registration. Provides a referenceable entry to which diffServClfrElementSpecific points. A packet matches this classifier entry if the packet's cable modem registered this index value as one of its four filter groups, and if the packet direction and MAC address select the use of this index among the four. Because this is the only field in this table, it is read-only, contrary to the usual SMI custom of making indices not-accessible. Note that although zero may be signaled (or defaulted) at DOCSIS Registration to indicate a default filtering group, no such entry appears in this table, as diffServClfrElementSpecific will use a zeroDotZero pointer for that classification.
.1.3.6.1.2.1.125.2,DOCS-IETF-SUBMGT-MIB::docsSubMgtConformance,,,,,,
.1.3.6.1.2.1.125.2.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtCompliances,,,,,,
.1.3.6.1.2.1.125.2.1.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtBasicCompliance,,,,,,The compliance statement for CMTS devices that implement CMTS centric subscriber management. This compliance statement applies to implementations that support DOCSIS 1.0/1.1/2.0, which are not IPv6 capable.
.1.3.6.1.2.1.125.2.2,DOCS-IETF-SUBMGT-MIB::docsSubMgtGroups,,,,,,
.1.3.6.1.2.1.125.2.2.1,DOCS-IETF-SUBMGT-MIB::docsSubMgtGroup,,,,,,The objects used to manage host-based cable modems via a set of CMTS enforced controls.
.1.3.6.1.2.1.126,DOCS-IETF-BPI2-MIB::docsBpi2MIB,,,,,,This is the MIB module for the DOCSIS Baseline Privacy Plus Interface (BPI+) at cable modems (CMs) and cable modem termination systems (CMTSs). Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4131; see the RFC itself for full legal notices.
.1.3.6.1.2.1.126.0,DOCS-IETF-BPI2-MIB::docsBpi2Notification,,,,,,
.1.3.6.1.2.1.126.1,DOCS-IETF-BPI2-MIB::docsBpi2MIBObjects,,,,,,
.1.3.6.1.2.1.126.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmObjects,,,,,,
.1.3.6.1.2.1.126.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmBaseTable,,not-accessible,,current,,This table describes the basic and authorization- related Baseline Privacy Plus attributes of each CM MAC interface.
.1.3.6.1.2.1.126.1.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmBaseEntry,,not-accessible,ifIndex,current,,Each entry contains objects describing attributes of one CM MAC interface. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.126.1.1.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmPrivacyEnable,INTEGER,read-only,,current,true(1):false(2),This object identifies whether this CM is provisioned to run Baseline Privacy Plus.
.1.3.6.1.2.1.126.1.1.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmPublicKey,OCTET,read-only,,current,,The value of this object is a DER-encoded RSAPublicKey ASN.1 type string, as defined in the RSA Encryption Standard (PKCS #1), corresponding to the public key of the CM.
.1.3.6.1.2.1.126.1.1.1.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthState,INTEGER,read-only,,current,start(1):authWait(2):authorized(3):reauthWait(4):authRejectWait(5):silent(6),The value of this object is the state of the CM authorization FSM. The start state indicates that FSM is in its initial state.
.1.3.6.1.2.1.126.1.1.1.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthKeySequenceNumber,Integer32,read-only,,current,,The value of this object is the most recent authorization key sequence number for this FSM.
.1.3.6.1.2.1.126.1.1.1.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthExpiresOld,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the immediate predecessor of the most recent authorization key for this FSM. If this FSM has only one authorization key, then the value is the time of activation of this FSM.
.1.3.6.1.2.1.126.1.1.1.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthExpiresNew,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the most recent authorization key for this FSM.
.1.3.6.1.2.1.126.1.1.1.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthReset,INTEGER,read-write,,current,true(1):false(2),Setting this object to 'true' generates a Reauthorize event in the authorization FSM. Reading this object always returns FALSE. This object is for testing purposes only, and therefore it is not required to be associated with a last reset object.
.1.3.6.1.2.1.126.1.1.1.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthGraceTime,Integer32,read-only,,current,,The value of this object is the grace time for an authorization key in seconds. A CM is expected to start trying to get a new authorization key beginning AuthGraceTime seconds before the most recent authorization key actually expires.
.1.3.6.1.2.1.126.1.1.1.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKGraceTime,Integer32,read-only,,current,,The value of this object is the grace time for the TEK in seconds. The CM is expected to start trying to acquire a new TEK beginning TEK GraceTime seconds before the expiration of the most recent TEK.
.1.3.6.1.2.1.126.1.1.1.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthWaitTimeout,Integer32,read-only,,current,,The value of this object is the Authorize Wait Timeout in seconds.
.1.3.6.1.2.1.126.1.1.1.1.11,DOCS-IETF-BPI2-MIB::docsBpi2CmReauthWaitTimeout,Integer32,read-only,,current,,The value of this object is the Reauthorize Wait Timeout in seconds.
.1.3.6.1.2.1.126.1.1.1.1.12,DOCS-IETF-BPI2-MIB::docsBpi2CmOpWaitTimeout,Integer32,read-only,,current,,The value of this object is the Operational Wait Timeout in seconds.
.1.3.6.1.2.1.126.1.1.1.1.13,DOCS-IETF-BPI2-MIB::docsBpi2CmRekeyWaitTimeout,Integer32,read-only,,current,,The value of this object is the Rekey Wait Timeout in seconds.
.1.3.6.1.2.1.126.1.1.1.1.14,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthRejectWaitTimeout,Integer32,read-only,,current,,The value of this object is the Authorization Reject Wait Timeout in seconds.
.1.3.6.1.2.1.126.1.1.1.1.15,DOCS-IETF-BPI2-MIB::docsBpi2CmSAMapWaitTimeout,Integer32,read-only,,current,,The value of this object is the retransmission interval, in seconds, of SA Map Requests from the MAP Wait state.
.1.3.6.1.2.1.126.1.1.1.1.16,DOCS-IETF-BPI2-MIB::docsBpi2CmSAMapMaxRetries,Integer32,read-only,,current,,The value of this object is the maximum number of Map Request retries allowed.
.1.3.6.1.2.1.126.1.1.1.1.17,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthentInfos,Counter32,read-only,,current,,The value of this object is the number of times the CM has transmitted an Authentication Information message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.1.1.18,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthRequests,Counter32,read-only,,current,,The value of this object is the number of times the CM has transmitted an Authorization Request message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.1.1.19,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthReplies,Counter32,read-only,,current,,The value of this object is the number of times the CM has received an Authorization Reply message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.1.1.20,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthRejects,Counter32,read-only,,current,,The value of this object is the number of times the CM has received an Authorization Reject message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.1.1.21,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthInvalids,Counter32,read-only,,current,,The value of this object is the count of times the CM has received an Authorization Invalid message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.1.1.22,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthRejectErrorCode,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unauthorizedSaid(4):permanentAuthorizationFailure(8):timeOfDayNotAcquired(11),The value of this object is the enumerated description of the Error-Code in the most recent Authorization Reject message received by the CM. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no Authorization Reject message has been received since reboot.
.1.3.6.1.2.1.126.1.1.1.1.23,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthRejectErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent Authorization Reject message received by the CM. This is a zero length string if no Authorization Reject message has been received since reboot.
.1.3.6.1.2.1.126.1.1.1.1.24,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthInvalidErrorCode,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unsolicited(5):invalidKeySequence(6):keyRequestAuthenticationFailure(7),The value of this object is the enumerated description of the Error-Code in the most recent Authorization Invalid message received by the CM. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no Authorization Invalid message has been received since reboot.
.1.3.6.1.2.1.126.1.1.1.1.25,DOCS-IETF-BPI2-MIB::docsBpi2CmAuthInvalidErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent Authorization Invalid message received by the CM. This is a zero length string if no Authorization Invalid message has been received since reboot.
.1.3.6.1.2.1.126.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKTable,,not-accessible,,current,,This table describes the attributes of each CM Traffic Encryption Key (TEK) association. The CM maintains (no more than) one TEK association per SAID per CM MAC interface.
.1.3.6.1.2.1.126.1.1.2.1,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKEntry,,not-accessible,ifIndex:docsBpi2CmTEKSAId,current,,Each entry contains objects describing the TEK association attributes of one SAID. The CM MUST create one entry per SAID, regardless of whether the SAID was obtained from a Registration Response message, from an Authorization Reply message, or from any dynamic SAID establishment mechanisms.
.1.3.6.1.2.1.126.1.1.2.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKSAId,Integer32,not-accessible,,current,,The value of this object is the DOCSIS Security Association ID (SAID).
.1.3.6.1.2.1.126.1.1.2.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKSAType,INTEGER,read-only,,current,none(0):primary(1):static(2):dynamic(3),The value of this object is the type of security association.
.1.3.6.1.2.1.126.1.1.2.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKDataEncryptAlg,INTEGER,read-only,,current,none(0):des56CbcMode(1):des40CbcMode(2):t3Des128CbcMode(3):aes128CbcMode(4):aes256CbcMode(5),The value of this object is the data encryption algorithm for this SAID.
.1.3.6.1.2.1.126.1.1.2.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKDataAuthentAlg,INTEGER,read-only,,current,none(0):hmacSha196(1),The value of this object is the data authentication algorithm for this SAID.
.1.3.6.1.2.1.126.1.1.2.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKState,INTEGER,read-only,,current,start(1):opWait(2):opReauthWait(3):operational(4):rekeyWait(5):rekeyReauthWait(6),The value of this object is the state of the indicated TEK FSM. The start(1) state indicates that the FSM is in its initial state.
.1.3.6.1.2.1.126.1.1.2.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKKeySequenceNumber,Integer32,read-only,,current,,The value of this object is the most recent TEK key sequence number for this TEK FSM.
.1.3.6.1.2.1.126.1.1.2.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKExpiresOld,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the immediate predecessor of the most recent TEK for this FSM. If this FSM has only one TEK, then the value is the time of activation of this FSM.
.1.3.6.1.2.1.126.1.1.2.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKExpiresNew,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the most recent TEK for this FSM.
.1.3.6.1.2.1.126.1.1.2.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKKeyRequests,Counter32,read-only,,current,,The value of this object is the number of times the CM has transmitted a Key Request message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.2.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKKeyReplies,Counter32,read-only,,current,,The value of this object is the number of times the CM has received a Key Reply message, including a message whose authentication failed. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.2.1.11,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKKeyRejects,Counter32,read-only,,current,,The value of this object is the number of times the CM has received a Key Reject message, including a message whose authentication failed. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.2.1.12,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKInvalids,Counter32,read-only,,current,,The value of this object is the number of times the CM has received a TEK Invalid message, including a message whose authentication failed. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.2.1.13,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKAuthPends,Counter32,read-only,,current,,The value of this object is the count of times an Authorization Pending (Auth Pend) event occurred in this FSM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.2.1.14,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKKeyRejectErrorCode,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedSaid(4),The value of this object is the enumerated description of the Error-Code in the most recent Key Reject message received by the CM. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no Key Reject message has been received since registration.
.1.3.6.1.2.1.126.1.1.2.1.15,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKKeyRejectErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent Key Reject message received by the CM. This is a zero length string if no Key Reject message has been received since registration.
.1.3.6.1.2.1.126.1.1.2.1.16,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKInvalidErrorCode,INTEGER,read-only,,current,none(1):unknown(2):invalidKeySequence(6),The value of this object is the enumerated description of the Error-Code in the most recent TEK Invalid message received by the CM. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no TEK Invalid message has been received since registration.
.1.3.6.1.2.1.126.1.1.2.1.17,DOCS-IETF-BPI2-MIB::docsBpi2CmTEKInvalidErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent TEK Invalid message received by the CM. This is a zero length string if no TEK Invalid message has been received since registration.
.1.3.6.1.2.1.126.1.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmMulticastObjects,,,,,,
.1.3.6.1.2.1.126.1.1.3.1,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastMapTable,,not-accessible,,current,,This table maps multicast IP addresses to SAIDs per CM MAC Interface. It is intended to map multicast IP addresses associated with SA MAP Request messages.
.1.3.6.1.2.1.126.1.1.3.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastMapEntry,,not-accessible,ifIndex:docsBpi2CmIpMulticastIndex,current,,Each entry contains objects describing the mapping of one multicast IP address to one SAID, as well as associated state, message counters, and error information. An entry may be removed from this table upon the reception of an SA Map Reject.
.1.3.6.1.2.1.126.1.1.3.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastIndex,Unsigned32,not-accessible,,current,,The index of this row.
.1.3.6.1.2.1.126.1.1.3.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address for docsBpi2CmIpMulticastAddress.
.1.3.6.1.2.1.126.1.1.3.1.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastAddress,OCTET,read-only,,current,,This object represents the IP multicast address to be mapped. The type of this address is determined by the value of the docsBpi2CmIpMulticastAddressType object.
.1.3.6.1.2.1.126.1.1.3.1.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAId,Unsigned32,read-only,,current,,This object represents the SAID to which the IP multicast address has been mapped. If no SA Map Reply has been received for the IP address, this object should have the value 0.
.1.3.6.1.2.1.126.1.1.3.1.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAMapState,INTEGER,read-only,,current,start(1):mapWait(2):mapped(3),The value of this object is the state of the SA Mapping FSM for this IP.
.1.3.6.1.2.1.126.1.1.3.1.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAMapRequests,Counter32,read-only,,current,,The value of this object is the number of times the CM has transmitted an SA Map Request message for this IP. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.3.1.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAMapReplies,Counter32,read-only,,current,,The value of this object is the number of times the CM has received an SA Map Reply message for this IP. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.3.1.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAMapRejects,Counter32,read-only,,current,,The value of this object is the number of times the CM has received an SA MAP Reject message for this IP. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.1.3.1.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAMapRejectErrorCode,INTEGER,read-only,,current,none(1):unknown(2):noAuthForRequestedDSFlow(9):dsFlowNotMappedToSA(10),The value of this object is the enumerated description of the Error-Code in the most recent SA Map Reject message sent in response to an SA Map Request for This IP. It has the value none(1) if no SA MAP Reject message has been received since entry creation.
.1.3.6.1.2.1.126.1.1.3.1.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmIpMulticastSAMapRejectErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent SA Map Reject message sent in response to an SA Map Request for this IP. It is a zero length string if no SA Map Reject message has been received since entry creation.
.1.3.6.1.2.1.126.1.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmCertObjects,,,,,,
.1.3.6.1.2.1.126.1.1.4.1,DOCS-IETF-BPI2-MIB::docsBpi2CmDeviceCertTable,,not-accessible,,current,,This table describes the Baseline Privacy Plus device certificates for each CM MAC interface.
.1.3.6.1.2.1.126.1.1.4.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmDeviceCertEntry,,not-accessible,ifIndex,current,,Each entry contains the device certificates of one CM MAC interface. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.126.1.1.4.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmDeviceCmCert,OCTET,read-write,,current,,The X509 DER-encoded cable modem certificate. Note: This object can be set only when the value is the zero-length OCTET STRING; otherwise, an error of 'inconsistentValue' is returned. Once the object contains the certificate, its access MUST be read-only and persists after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.1.4.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmDeviceManufCert,OCTET,read-only,,current,,The X509 DER-encoded manufacturer certificate that signed the cable modem certificate.
.1.3.6.1.2.1.126.1.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmCryptoSuiteTable,,not-accessible,,current,,This table describes the Baseline Privacy Plus cryptographic suite capabilities for each CM MAC interface.
.1.3.6.1.2.1.126.1.1.5.1,DOCS-IETF-BPI2-MIB::docsBpi2CmCryptoSuiteEntry,,not-accessible,ifIndex:docsBpi2CmCryptoSuiteIndex,current,,Each entry contains a cryptographic suite pair that this CM MAC supports.
.1.3.6.1.2.1.126.1.1.5.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmCryptoSuiteIndex,Unsigned32,not-accessible,,current,,The index for a cryptographic suite row.
.1.3.6.1.2.1.126.1.1.5.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmCryptoSuiteDataEncryptAlg,INTEGER,read-only,,current,none(0):des56CbcMode(1):des40CbcMode(2):t3Des128CbcMode(3):aes128CbcMode(4):aes256CbcMode(5),The value of this object is the data encryption algorithm for this cryptographic suite capability.
.1.3.6.1.2.1.126.1.1.5.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmCryptoSuiteDataAuthentAlg,INTEGER,read-only,,current,none(0):hmacSha196(1),The value of this object is the data authentication algorithm for this cryptographic suite capability.
.1.3.6.1.2.1.126.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsObjects,,,,,,
.1.3.6.1.2.1.126.1.2.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsBaseTable,,not-accessible,,current,,This table describes the basic Baseline Privacy attributes of each CMTS MAC interface.
.1.3.6.1.2.1.126.1.2.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsBaseEntry,,not-accessible,ifIndex,current,,Each entry contains objects describing attributes of one CMTS MAC interface. An entry in this table exists for each ifEntry with an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.126.1.2.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsDefaultAuthLifetime,Integer32,read-write,,current,,The value of this object is the default lifetime, in seconds, that the CMTS assigns to a new authorization key. This object value persists after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsDefaultTEKLifetime,Integer32,read-write,,current,,The value of this object is the default lifetime, in seconds, that the CMTS assigns to a new Traffic Encryption Key (TEK). This object value persists after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.1.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsDefaultSelfSignedManufCertTrust,INTEGER,read-write,,current,trusted(1):untrusted(2),This object determines the default trust of self-signed manufacturer certificate entries, contained in docsBpi2CmtsCACertTable, and created after this object is set. This object need not persist after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.1.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCheckCertValidityPeriods,INTEGER,read-write,,current,true(1):false(2),Setting this object to 'true' causes all chained and root certificates in the chain to have their validity periods checked against the current time of day, when the CMTS receives an Authorization Request from the CM. A 'false' setting causes all certificates in the chain not to have their validity periods checked against the current time of day. This object need not persist after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.1.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthentInfos,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received an Authentication Information message from any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthRequests,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received an Authorization Request message from any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthReplies,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an Authorization Reply message to any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthRejects,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an Authorization Reject message to any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthInvalids,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an Authorization Invalid message to any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmtsSAMapRequests,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received an SA Map Request message from any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.11,DOCS-IETF-BPI2-MIB::docsBpi2CmtsSAMapReplies,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an SA Map Reply message to any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.1.1.12,DOCS-IETF-BPI2-MIB::docsBpi2CmtsSAMapRejects,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an SA Map Reject message to any CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthTable,,not-accessible,,current,,This table describes the attributes of each CM authorization association. The CMTS maintains one authorization association with each Baseline Privacy- enabled CM, registered on each CMTS MAC interface, regardless of whether the CM is authorized or rejected.
.1.3.6.1.2.1.126.1.2.2.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthEntry,,not-accessible,ifIndex:docsBpi2CmtsAuthCmMacAddress,current,,Each entry contains objects describing attributes of one authorization association. The CMTS MUST create one entry per CM per MAC interface, based on the receipt of an Authorization Request message, and MUST not delete the entry until the CM loses registration.
.1.3.6.1.2.1.126.1.2.2.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmMacAddress,OCTET,not-accessible,,current,,The value of this object is the physical address of the CM to which the authorization association applies.
.1.3.6.1.2.1.126.1.2.2.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmBpiVersion,INTEGER,read-only,,current,bpi(0):bpiPlus(1),The value of this object is the version of Baseline Privacy for which this CM has registered. The value 'bpiplus' represents the value of BPI-Version Attribute of the Baseline Privacy Key Management BPKM attribute BPI-Version (1). The value 'bpi' is used to represent the CM registered using DOCSIS 1.0 Baseline Privacy.
.1.3.6.1.2.1.126.1.2.2.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmPublicKey,OCTET,read-only,,current,,The value of this object is a DER-encoded RSAPublicKey ASN.1 type string, as defined in the RSA Encryption Standard (PKCS #1), corresponding to the public key of the CM. This is the zero-length OCTET STRING if the CMTS does not retain the public key.
.1.3.6.1.2.1.126.1.2.2.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmKeySequenceNumber,Integer32,read-only,,current,,The value of this object is the most recent authorization key sequence number for this CM.
.1.3.6.1.2.1.126.1.2.2.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmExpiresOld,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the immediate predecessor of the most recent authorization key for this FSM. If this FSM has only one authorization key, then the value is the time of activation of this FSM. Note: This object has no meaning for CMs running in BPI mode; therefore, this object is not instantiated for entries associated to those CMs.
.1.3.6.1.2.1.126.1.2.2.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmExpiresNew,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the most recent authorization key for this FSM.
.1.3.6.1.2.1.126.1.2.2.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmLifetime,Integer32,read-write,,current,,The value of this object is the lifetime, in seconds, that the CMTS assigns to an authorization key for this CM.
.1.3.6.1.2.1.126.1.2.2.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmReset,INTEGER,read-write,,current,noResetRequested(1):invalidateAuth(2):sendAuthInvalid(3):invalidateTeks(4),Setting this object to invalidateAuth(2) causes the CMTS to invalidate the current CM authorization key(s), but not to transmit an Authorization Invalid message nor to invalidate the primary SAID's TEKs. Setting this object to sendAuthInvalid(3) causes the CMTS to invalidate the current CM authorization key(s), and to transmit an Authorization Invalid message to the CM, but not to invalidate the primary SAID's TEKs. Setting this object to invalidateTeks(4) causes the CMTS to invalidate the current CM authorization key(s), to transmit an Authorization Invalid message to the CM, and to invalidate the TEKs associated with this CM's primary SAID. For BPI mode, substitute all of the CM's unicast TEKs for the primary SAID's TEKs in the previous paragraph. Reading this object returns the most recently set value of this object or, if the object has not been set since entry creation, returns noResetRequested(1).
.1.3.6.1.2.1.126.1.2.2.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmInfos,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received an Authentication Information message from this CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.2.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmRequests,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received an Authorization Request message from this CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.2.1.11,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmReplies,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an Authorization Reply message to this CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.2.1.12,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmRejects,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an Authorization Reject message to this CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.2.1.13,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCmInvalids,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an Authorization Invalid message to this CM. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.2.1.14,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthRejectErrorCode,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unauthorizedSaid(4):permanentAuthorizationFailure(8):timeOfDayNotAcquired(11),The value of this object is the enumerated description of the Error-Code in the most recent Authorization Reject message transmitted to the CM. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no Authorization Reject message has been transmitted to the CM since entry creation.
.1.3.6.1.2.1.126.1.2.2.1.15,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthRejectErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent Authorization Reject message transmitted to the CM. This is a zero length string if no Authorization Reject message has been transmitted to the CM since entry creation.
.1.3.6.1.2.1.126.1.2.2.1.16,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthInvalidErrorCode,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedCm(3):unsolicited(5):invalidKeySequence(6):keyRequestAuthenticationFailure(7),The value of this object is the enumerated description of the Error-Code in the most recent Authorization Invalid message transmitted to the CM. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no Authorization Invalid message has been transmitted to the CM since entry creation.
.1.3.6.1.2.1.126.1.2.2.1.17,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthInvalidErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent Authorization Invalid message transmitted to the CM. This is a zero length string if no Authorization Invalid message has been transmitted to the CM since entry creation.
.1.3.6.1.2.1.126.1.2.2.1.18,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthPrimarySAId,Unsigned32,read-only,,current,,The value of this object is the Primary Security Association identifier. For BPI mode, the value must be any unicast SID.
.1.3.6.1.2.1.126.1.2.2.1.19,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthBpkmCmCertValid,INTEGER,read-only,,current,unknown(0):validCmChained(1):validCmTrusted(2):invalidCmUntrusted(3):invalidCAUntrusted(4):invalidCmOther(5):invalidCAOther(6),Contains the reason why a CM's certificate is deemed valid or invalid. Return unknown(0) if the CM is running BPI mode. ValidCmChained(1) means the certificate is valid because it chains to a valid certificate. ValidCmTrusted(2) means the certificate is valid because it has been provisioned (in the docsBpi2CmtsProvisionedCmCert table) to be trusted. InvalidCmUntrusted(3) means the certificate is invalid because it has been provisioned (in the docsBpi2CmtsProvisionedCmCert table) to be untrusted. InvalidCAUntrusted(4) means the certificate is invalid because it chains to an untrusted certificate. InvalidCmOther(5) and InvalidCAOther(6) refer to errors in parsing, validity periods, etc., which are attributable to the CM certificate or its chain, respectively; additional information may be found in docsBpi2AuthRejectErrorString for these types of errors.
.1.3.6.1.2.1.126.1.2.2.1.20,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthBpkmCmCert,OCTET,read-only,,current,,The X509 CM Certificate sent as part of a BPKM Authorization Request. Note: The zero-length OCTET STRING must be returned if the Entire certificate is not retained in the CMTS.
.1.3.6.1.2.1.126.1.2.2.1.21,DOCS-IETF-BPI2-MIB::docsBpi2CmtsAuthCACertIndexPtr,Unsigned32,read-only,,current,,A row index into docsBpi2CmtsCACertTable. Returns the index in docsBpi2CmtsCACertTable to which CA certificate this CM is chained to. A value of 0 means it could not be found or not applicable.
.1.3.6.1.2.1.126.1.2.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKTable,,not-accessible,,current,,This table describes the attributes of each Traffic Encryption Key (TEK) association. The CMTS Maintains one TEK association per SAID on each CMTS MAC interface.
.1.3.6.1.2.1.126.1.2.3.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKEntry,,not-accessible,ifIndex:docsBpi2CmtsTEKSAId,current,,Each entry contains objects describing attributes of one TEK association on a particular CMTS MAC interface. The CMTS MUST create one entry per SAID per MAC interface, based on the receipt of a Key Request message, and MUST not delete the entry before the CM authorization for the SAID permanently expires.
.1.3.6.1.2.1.126.1.2.3.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKSAId,Integer32,not-accessible,,current,,The value of this object is the DOCSIS Security Association ID (SAID).
.1.3.6.1.2.1.126.1.2.3.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKSAType,INTEGER,read-only,,current,none(0):primary(1):static(2):dynamic(3),The value of this object is the type of security association. 'dynamic' does not apply to CMs running in BPI mode. Unicast BPI TEKs must utilize the 'primary' encoding, and multicast BPI TEKs must utilize the 'static' encoding.
.1.3.6.1.2.1.126.1.2.3.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKDataEncryptAlg,INTEGER,read-only,,current,none(0):des56CbcMode(1):des40CbcMode(2):t3Des128CbcMode(3):aes128CbcMode(4):aes256CbcMode(5),The value of this object is the data encryption algorithm for this SAID.
.1.3.6.1.2.1.126.1.2.3.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKDataAuthentAlg,INTEGER,read-only,,current,none(0):hmacSha196(1),The value of this object is the data authentication algorithm for this SAID.
.1.3.6.1.2.1.126.1.2.3.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKLifetime,Integer32,read-write,,current,,The value of this object is the lifetime, in seconds, that the CMTS assigns to keys for this TEK association.
.1.3.6.1.2.1.126.1.2.3.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKKeySequenceNumber,Integer32,read-only,,current,,The value of this object is the most recent TEK key sequence number for this SAID.
.1.3.6.1.2.1.126.1.2.3.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKExpiresOld,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the immediate predecessor of the most recent TEK for this FSM. If this FSM has only one TEK, then the value is the time of activation of this FSM.
.1.3.6.1.2.1.126.1.2.3.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKExpiresNew,OCTET,read-only,,current,,The value of this object is the actual clock time for expiration of the most recent TEK for this FSM.
.1.3.6.1.2.1.126.1.2.3.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKReset,INTEGER,read-write,,current,true(1):false(2),Setting this object to 'true' causes the CMTS to invalidate all currently active TEKs and to generate new TEKs for the associated SAID; the CMTS MAY also generate unsolicited TEK Invalid messages, to optimize the TEK synchronization between the CMTS and the CM(s). Reading this object always returns FALSE.
.1.3.6.1.2.1.126.1.2.3.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmtsKeyRequests,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received a Key Request message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.3.1.11,DOCS-IETF-BPI2-MIB::docsBpi2CmtsKeyReplies,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted a Key Reply message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.3.1.12,DOCS-IETF-BPI2-MIB::docsBpi2CmtsKeyRejects,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted a Key Reject message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.3.1.13,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKInvalids,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted a TEK Invalid message. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.3.1.14,DOCS-IETF-BPI2-MIB::docsBpi2CmtsKeyRejectErrorCode,INTEGER,read-only,,current,none(1):unknown(2):unauthorizedSaid(4),The value of this object is the enumerated description of the Error-Code in the most recent Key Reject message sent in response to a Key Request for this SAID. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no Key Reject message has been received since registration.
.1.3.6.1.2.1.126.1.2.3.1.15,DOCS-IETF-BPI2-MIB::docsBpi2CmtsKeyRejectErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent Key Reject message sent in response to a Key Request for this SAID. This is a zero length string if no Key Reject message has been received since registration.
.1.3.6.1.2.1.126.1.2.3.1.16,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKInvalidErrorCode,INTEGER,read-only,,current,none(1):unknown(2):invalidKeySequence(6),The value of this object is the enumerated description of the Error-Code in the most recent TEK Invalid message sent in association with this SAID. This has the value unknown(2) if the last Error-Code value was 0 and none(1) if no TEK Invalid message has been received since registration.
.1.3.6.1.2.1.126.1.2.3.1.17,DOCS-IETF-BPI2-MIB::docsBpi2CmtsTEKInvalidErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent TEK Invalid message sent in association with this SAID. This is a zero length string if no TEK Invalid message has been received since registration.
.1.3.6.1.2.1.126.1.2.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsMulticastObjects,,,,,,
.1.3.6.1.2.1.126.1.2.4.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastMapTable,,not-accessible,,current,,This table maps multicast IP addresses to SAIDs. If a multicast IP address is mapped by multiple rows in the table, the row with the lowest docsBpi2CmtsIpMulticastIndex must be utilized for the mapping.
.1.3.6.1.2.1.126.1.2.4.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastMapEntry,,not-accessible,ifIndex:docsBpi2CmtsIpMulticastIndex,current,,Each entry contains objects describing the mapping of a set of multicast IP address and the mask to one SAID associated to a CMTS MAC Interface, as well as associated message counters and error information.
.1.3.6.1.2.1.126.1.2.4.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastIndex,Unsigned32,not-accessible,,current,,The index of this row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.126.1.2.4.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address for docsBpi2CmtsIpMulticastAddress and docsBpi2CmtsIpMulticastMask.
.1.3.6.1.2.1.126.1.2.4.1.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastAddress,OCTET,read-create,,current,,This object represents the IP multicast address to be mapped, in conjunction with docsBpi2CmtsIpMulticastMask. The type of this address is determined by the value of the object docsBpi2CmtsIpMulticastAddressType.
.1.3.6.1.2.1.126.1.2.4.1.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastMask,OCTET,read-create,,current,,This object represents the IP multicast address mask for this row. An IP multicast address matches this row if the logical AND of the address with docsBpi2CmtsIpMulticastMask is identical to the logical AND of docsBpi2CmtsIpMulticastAddr with docsBpi2CmtsIpMulticastMask. The type of this address is determined by the value of the object docsBpi2CmtsIpMulticastAddressType. Note: For IPv6, this object need not represent a contiguous netmask; e.g., to associate a SAID to a multicast group matching 'any' multicast scope. The TC InetAddressPrefixLength is not used, as it only represents contiguous netmask.
.1.3.6.1.2.1.126.1.2.4.1.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAId,Unsigned32,read-create,,current,,This object represents the multicast SAID to be used in this IP multicast address mapping entry.
.1.3.6.1.2.1.126.1.2.4.1.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAType,INTEGER,read-create,,current,none(0):primary(1):static(2):dynamic(3),The value of this object is the type of security association. 'dynamic' does not apply to CMs running in BPI mode. Unicast BPI TEKs must utilize the 'primary' encoding, and multicast BPI TEKs must utilize the 'static' encoding. By default, SNMP created entries set this object to 'static' if not set at row creation.
.1.3.6.1.2.1.126.1.2.4.1.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastDataEncryptAlg,INTEGER,read-create,,current,none(0):des56CbcMode(1):des40CbcMode(2):t3Des128CbcMode(3):aes128CbcMode(4):aes256CbcMode(5),The value of this object is the data encryption algorithm for this IP.
.1.3.6.1.2.1.126.1.2.4.1.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastDataAuthentAlg,INTEGER,read-create,,current,none(0):hmacSha196(1),The value of this object is the data authentication algorithm for this IP.
.1.3.6.1.2.1.126.1.2.4.1.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAMapRequests,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has received an SA Map Request message for this IP. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.4.1.1.10,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAMapReplies,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an SA Map Reply message for this IP. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.4.1.1.11,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAMapRejects,Counter32,read-only,,current,,The value of this object is the number of times the CMTS has transmitted an SA Map Reject message for this IP. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.6.1.2.1.126.1.2.4.1.1.12,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAMapRejectErrorCode,INTEGER,read-only,,current,none(1):unknown(2):noAuthForRequestedDSFlow(9):dsFlowNotMappedToSA(10),The value of this object is the enumerated description of the Error-Code in the most recent SA Map Reject message sent in response to an SA Map Request for this IP. It has the value unknown(2) if the last Error-Code Value was 0 and none(1) if no SA MAP Reject message has been received since entry creation.
.1.3.6.1.2.1.126.1.2.4.1.1.13,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastSAMapRejectErrorString,OCTET,read-only,,current,,The value of this object is the text string in the most recent SA Map Reject message sent in response to an SA Map Request for this IP. It is a zero length string if no SA Map Reject message has been received since entry creation.
.1.3.6.1.2.1.126.1.2.4.1.1.14,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastMapControl,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls and reflects the IP multicast address mapping entry. There is no restriction on the ability to change values in this row while the row is active. A created row can be set to active only after the Corresponding instances of docsBpi2CmtsIpMulticastAddress, docsBpi2CmtsIpMulticastMask, docsBpi2CmtsIpMulticastSAId, and docsBpi2CmtsIpMulticastSAType have all been set.
.1.3.6.1.2.1.126.1.2.4.1.1.15,DOCS-IETF-BPI2-MIB::docsBpi2CmtsIpMulticastMapStorageType,INTEGER,read-only,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.126.1.2.4.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsMulticastAuthTable,,not-accessible,,current,,This table describes the multicast SAID authorization for each CM on each CMTS MAC interface.
.1.3.6.1.2.1.126.1.2.4.2.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsMulticastAuthEntry,,not-accessible,ifIndex:docsBpi2CmtsMulticastAuthSAId:docsBpi2CmtsMulticastAuthCmMacAddress,current,,Each entry contains objects describing the key authorization of one cable modem for one multicast SAID for one CMTS MAC interface. Row entries persist after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.4.2.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsMulticastAuthSAId,Integer32,not-accessible,,current,,This object represents the multicast SAID for authorization.
.1.3.6.1.2.1.126.1.2.4.2.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsMulticastAuthCmMacAddress,OCTET,not-accessible,,current,,This object represents the MAC address of the CM to which the multicast SAID authorization applies.
.1.3.6.1.2.1.126.1.2.4.2.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsMulticastAuthControl,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row for the authorization of multicast SAIDs to CMs.
.1.3.6.1.2.1.126.1.2.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCertObjects,,,,,,
.1.3.6.1.2.1.126.1.2.5.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCertTable,,not-accessible,,current,,A table of CM certificate trust entries provisioned to the CMTS. The trust object for a certificate in this table has an overriding effect on the validity object of a certificate in the authorization table, as long as the entire contents of the two certificates are identical.
.1.3.6.1.2.1.126.1.2.5.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCertEntry,,not-accessible,docsBpi2CmtsProvisionedCmCertMacAddress,current,,An entry in the CMTS's provisioned CM certificate table. Row entries persist after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.5.1.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCertMacAddress,OCTET,not-accessible,,current,,The index of this row.
.1.3.6.1.2.1.126.1.2.5.1.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCertTrust,INTEGER,read-create,,current,trusted(1):untrusted(2),Trust state for the provisioned CM certificate entry. Note: Setting this object need only override the validity of CM certificates sent in future authorization requests; instantaneous effect need not occur.
.1.3.6.1.2.1.126.1.2.5.1.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCertSource,INTEGER,read-only,,current,snmp(1):configurationFile(2):externalDatabase(3):other(4),This object indicates how the certificate reached the CMTS. Other(4) means that it originated from a source not identified above.
.1.3.6.1.2.1.126.1.2.5.1.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCertStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. Values in this row cannot be changed while the row is 'active'.
.1.3.6.1.2.1.126.1.2.5.1.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsProvisionedCmCert,OCTET,read-create,,current,,An X509 DER-encoded Certificate Authority certificate. Note: The zero-length OCTET STRING must be returned, on reads, if the entire certificate is not retained in the CMTS.
.1.3.6.1.2.1.126.1.2.5.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertTable,,not-accessible,,current,,The table of known Certificate Authority certificates acquired by this device.
.1.3.6.1.2.1.126.1.2.5.2.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertEntry,,not-accessible,docsBpi2CmtsCACertIndex,current,,A row in the Certificate Authority certificate table. Row entries with the trust status 'trusted', 'untrusted', or 'root' persist after re-initialization of the managed system.
.1.3.6.1.2.1.126.1.2.5.2.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertIndex,Unsigned32,not-accessible,,current,,The index for this row.
.1.3.6.1.2.1.126.1.2.5.2.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertSubject,OCTET,read-only,,current,,The subject name exactly as it is encoded in the X509 certificate. The organizationName portion of the certificate's subject name must be present. All other fields are optional. Any optional field present must be prepended with <CR> (carriage return, U+000D) <LF> (line feed, U+000A). Ordering of fields present must conform to the following: organizationName <CR> <LF> countryName <CR> <LF> stateOrProvinceName <CR> <LF> localityName <CR> <LF> organizationalUnitName <CR> <LF> organizationalUnitName=<Manufacturing Location> <CR> <LF> commonName
.1.3.6.1.2.1.126.1.2.5.2.1.3,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertIssuer,OCTET,read-only,,current,,The issuer name exactly as it is encoded in the X509 certificate. The commonName portion of the certificate's issuer name must be present. All other fields are optional. Any optional field present must be prepended with <CR> (carriage return, U+000D) <LF> (line feed, U+000A). Ordering of fields present must conform to the following: CommonName <CR><LF> countryName <CR><LF> stateOrProvinceName <CR><LF> localityName <CR><LF> organizationName <CR><LF> organizationalUnitName <CR><LF> organizationalUnitName=<Manufacturing Location>
.1.3.6.1.2.1.126.1.2.5.2.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertSerialNumber,OCTET,read-only,,current,,This CA certificate's serial number, represented as an octet string.
.1.3.6.1.2.1.126.1.2.5.2.1.5,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertTrust,INTEGER,read-create,,current,trusted(1):untrusted(2):chained(3):root(4),This object controls the trust status of this certificate. Root certificates must be given root(4) trust; manufacturer certificates must not be given root(4) trust. Trust on root certificates must not change. Note: Setting this object need only affect the validity of CM certificates sent in future authorization requests; instantaneous effect need not occur.
.1.3.6.1.2.1.126.1.2.5.2.1.6,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertSource,INTEGER,read-only,,current,snmp(1):configurationFile(2):externalDatabase(3):other(4):authentInfo(5):compiledIntoCode(6),This object indicates how the certificate reached the CMTS. Other(4) means that it originated from a source not identified above.
.1.3.6.1.2.1.126.1.2.5.2.1.7,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. An attempt to set writable columnar values while this row is active behaves as follows: - Sets to the object docsBpi2CmtsCACertTrust are allowed. - Sets to the object docsBpi2CmtsCACert will return an error of 'inconsistentValue'. A newly created entry cannot be set to active until the value of docsBpi2CmtsCACert is being set.
.1.3.6.1.2.1.126.1.2.5.2.1.8,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACert,OCTET,read-create,,current,,An X509 DER-encoded Certificate Authority certificate. To help identify certificates, either this object or docsBpi2CmtsCACertThumbprint must be returned by a CMTS for self-signed CA certificates. Note: The zero-length OCTET STRING must be returned, on reads, if the entire certificate is not retained in the CMTS.
.1.3.6.1.2.1.126.1.2.5.2.1.9,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCACertThumbprint,OCTET,read-only,,current,,The SHA-1 hash of a CA certificate. To help identify certificates, either this object or docsBpi2CmtsCACert must be returned by a CMTS for self-signed CA certificates. Note: The zero-length OCTET STRING must be returned, on reads, if the CA certificate thumb print is not retained in the CMTS.
.1.3.6.1.2.1.126.1.4,DOCS-IETF-BPI2-MIB::docsBpi2CodeDownloadControl,,,,,,
.1.3.6.1.2.1.126.1.4.1,DOCS-IETF-BPI2-MIB::docsBpi2CodeDownloadStatusCode,INTEGER,read-only,,current,configFileCvcVerified(1):configFileCvcRejected(2):snmpCvcVerified(3):snmpCvcRejected(4):codeFileVerified(5):codeFileRejected(6):other(7),The value indicates the result of the latest config file CVC verification, SNMP CVC verification, or code file verification.
.1.3.6.1.2.1.126.1.4.2,DOCS-IETF-BPI2-MIB::docsBpi2CodeDownloadStatusString,OCTET,read-only,,current,,The value of this object indicates the additional information to the status code. The value will include the error code and error description, which will be defined separately.
.1.3.6.1.2.1.126.1.4.3,DOCS-IETF-BPI2-MIB::docsBpi2CodeMfgOrgName,OCTET,read-only,,current,,The value of this object is the device manufacturer's organizationName.
.1.3.6.1.2.1.126.1.4.4,DOCS-IETF-BPI2-MIB::docsBpi2CodeMfgCodeAccessStart,OCTET,read-only,,current,,The value of this object is the device manufacturer's current codeAccessStart value. This value will always refer to Greenwich Mean Time (GMT), and the value format must contain TimeZone information (fields 8-10).
.1.3.6.1.2.1.126.1.4.5,DOCS-IETF-BPI2-MIB::docsBpi2CodeMfgCvcAccessStart,OCTET,read-only,,current,,The value of this object is the device manufacturer's current cvcAccessStart value. This value will always refer to Greenwich Mean Time (GMT), and the value format must contain TimeZone information (fields 8-10).
.1.3.6.1.2.1.126.1.4.6,DOCS-IETF-BPI2-MIB::docsBpi2CodeCoSignerOrgName,OCTET,read-only,,current,,The value of this object is the co-signer's organizationName. The value is a zero length string if the co-signer is not specified.
.1.3.6.1.2.1.126.1.4.7,DOCS-IETF-BPI2-MIB::docsBpi2CodeCoSignerCodeAccessStart,OCTET,read-only,,current,,The value of this object is the co-signer's current codeAccessStart value. This value will always refer to Greenwich Mean Time (GMT), and the value format must contain TimeZone information (fields 8-10). If docsBpi2CodeCoSignerOrgName is a zero length string, the value of this object is meaningless.
.1.3.6.1.2.1.126.1.4.8,DOCS-IETF-BPI2-MIB::docsBpi2CodeCoSignerCvcAccessStart,OCTET,read-only,,current,,The value of this object is the co-signer's current cvcAccessStart value. This value will always refer to Greenwich Mean Time (GMT), and the value format must contain TimeZone information (fields 8-10). If docsBpi2CodeCoSignerOrgName is a zero length string, the value of this object is meaningless.
.1.3.6.1.2.1.126.1.4.9,DOCS-IETF-BPI2-MIB::docsBpi2CodeCvcUpdate,OCTET,read-write,,current,,Setting a CVC to this object triggers the device to verify the CVC and update the cvcAccessStart values. The content of this object is then discarded. If the device is not enabled to upgrade codefiles, or if the CVC verification fails, the CVC will be rejected. Reading this object always returns the zero-length OCTET STRING.
.1.3.6.1.2.1.126.2,DOCS-IETF-BPI2-MIB::docsBpi2Conformance,,,,,,
.1.3.6.1.2.1.126.2.1,DOCS-IETF-BPI2-MIB::docsBpi2Compliances,,,,,,
.1.3.6.1.2.1.126.2.1.1,DOCS-IETF-BPI2-MIB::docsBpi2CmCompliance,,,,,,This is the compliance statement for CMs that implement the DOCSIS Baseline Privacy Interface Plus.
.1.3.6.1.2.1.126.2.1.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsCompliance,,,,,,This is the compliance statement for CMTSs that implement the DOCSIS Baseline Privacy Interface Plus.
.1.3.6.1.2.1.126.2.2,DOCS-IETF-BPI2-MIB::docsBpi2Groups,,,,,,
.1.3.6.1.2.1.126.2.2.1,DOCS-IETF-BPI2-MIB::docsBpi2CmGroup,,,,,,This collection of objects provides CM BPI+ status and control.
.1.3.6.1.2.1.126.2.2.2,DOCS-IETF-BPI2-MIB::docsBpi2CmtsGroup,,,,,,This collection of objects provides CMTS BPI+ status and control.
.1.3.6.1.2.1.126.2.2.3,DOCS-IETF-BPI2-MIB::docsBpi2CodeDownloadGroup,,,,,,This collection of objects provides authenticated software download support.
.1.3.6.1.2.1.127,DOCS-IETF-QOS-MIB::docsIetfQosMIB,,,,,,This is the management information for Quality Of Service (QOS) for DOCSIS 1.1 and 2.0. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4323; see the RFC itself for full legal notices.
.1.3.6.1.2.1.127.0,DOCS-IETF-QOS-MIB::docsIetfQosNotifications,,,,,,
.1.3.6.1.2.1.127.1,DOCS-IETF-QOS-MIB::docsIetfQosMIBObjects,,,,,,
.1.3.6.1.2.1.127.1.1,DOCS-IETF-QOS-MIB::docsIetfQosPktClassTable,,not-accessible,,current,,This table describes the packet classification configured on the CM or CMTS. The model is that a packet either received as input from an interface or transmitted for output on an interface may be compared against an ordered list of rules pertaining to the packet contents. Each rule is a row of this table. A matching rule provides a Service Flow ID to which the packet is classified. All rules need to match for a packet to match a classifier. The objects in this row correspond to a set of Classifier Encoding parameters in a DOCSIS MAC management message. The docsIetfQosPktClassBitMap indicates which particular parameters were present in the classifier as signaled in the DOCSIS message. If the referenced parameter was not present in the signaled DOCSIS 1.1 and 2.0 Classifier, the corresponding object in this row reports a value as specified in the DESCRIPTION section.
.1.3.6.1.2.1.127.1.1.1,DOCS-IETF-QOS-MIB::docsIetfQosPktClassEntry,,not-accessible,ifIndex:docsIetfQosServiceFlowId:docsIetfQosPktClassId,current,,An entry in this table provides a single packet classifier rule. The index ifIndex is an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.127.1.1.1.1,DOCS-IETF-QOS-MIB::docsIetfQosPktClassId,Unsigned32,not-accessible,,current,,Index assigned to packet classifier entry by the CMTS, which is unique per Service Flow.
.1.3.6.1.2.1.127.1.1.1.2,DOCS-IETF-QOS-MIB::docsIetfQosPktClassDirection,INTEGER,read-only,,current,downstream(1):upstream(2),Indicates the direction to which the classifier is applied.
.1.3.6.1.2.1.127.1.1.1.3,DOCS-IETF-QOS-MIB::docsIetfQosPktClassPriority,Integer32,read-only,,current,,The value specifies the order of evaluation of the classifiers. The higher the value, the higher the priority. The value of 0 is used as default in provisioned Service Flows Classifiers. The default value of 64 is used for dynamic Service Flow Classifiers. If the referenced parameter is not present in a classifier, this object reports the default value as defined above.
.1.3.6.1.2.1.127.1.1.1.4,DOCS-IETF-QOS-MIB::docsIetfQosPktClassIpTosLow,OCTET,read-only,,current,,The low value of a range of TOS byte values. If the referenced parameter is not present in a classifier, this object reports the value of 0. The IP TOS octet, as originally defined in RFC 791, has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). This object is defined as an 8-bit octet as per the DOCSIS Specification for packet classification.
.1.3.6.1.2.1.127.1.1.1.5,DOCS-IETF-QOS-MIB::docsIetfQosPktClassIpTosHigh,OCTET,read-only,,current,,The 8-bit high value of a range of TOS byte values. If the referenced parameter is not present in a classifier, this object reports the value of 0. The IP TOS octet as originally defined in RFC 791 has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). This object is defined as an 8-bit octet as defined by the DOCSIS Specification for packet classification.
.1.3.6.1.2.1.127.1.1.1.6,DOCS-IETF-QOS-MIB::docsIetfQosPktClassIpTosMask,OCTET,read-only,,current,,The mask value is bitwise ANDed with TOS byte in an IP packet, and this value is used for range checking of TosLow and TosHigh. If the referenced parameter is not present in a classifier, this object reports the value of 0. The IP TOS octet as originally defined in RFC 791 has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). This object is defined as an 8-bit octet per the DOCSIS Specification for packet classification.
.1.3.6.1.2.1.127.1.1.1.7,DOCS-IETF-QOS-MIB::docsIetfQosPktClassIpProtocol,Integer32,read-only,,current,,This object indicates the value of the IP Protocol field required for IP packets to match this rule. The value 256 matches traffic with any IP Protocol value. The value 257 by convention matches both TCP and UDP. If the referenced parameter is not present in a classifier, this object reports the value of 258.
.1.3.6.1.2.1.127.1.1.1.8,DOCS-IETF-QOS-MIB::docsIetfQosPktClassInetAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the Internet address for docsIetfQosPktClassInetSourceAddr, docsIetfQosPktClassInetSourceMask, docsIetfQosPktClassInetDestAddr, and docsIetfQosPktClassInetDestMask. If the referenced parameter is not present in a classifier, this object reports the value of ipv4(1).
.1.3.6.1.2.1.127.1.1.1.9,DOCS-IETF-QOS-MIB::docsIetfQosPktClassInetSourceAddr,OCTET,read-only,,current,,This object specifies the value of the IP Source Address required for packets to match this rule. An IP packet matches the rule when the packet IP Source Address bitwise ANDed with the docsIetfQosPktClassInetSourceMask value equals the docsIetfQosPktClassInetSourceAddr value. The address type of this object is specified by docsIetfQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of '00000000'H.
.1.3.6.1.2.1.127.1.1.1.10,DOCS-IETF-QOS-MIB::docsIetfQosPktClassInetSourceMask,OCTET,read-only,,current,,This object specifies which bits of a packet's IP Source Address are compared to match this rule. An IP packet matches the rule when the packet source address bitwise ANDed with the docsIetfQosPktClassInetSourceMask value equals the docsIetfQosIpPktClassInetSourceAddr value. The address type of this object is specified by docsIetfQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of 'FFFFFFFF'H.
.1.3.6.1.2.1.127.1.1.1.11,DOCS-IETF-QOS-MIB::docsIetfQosPktClassInetDestAddr,OCTET,read-only,,current,,This object specifies the value of the IP Destination Address required for packets to match this rule. An IP packet matches the rule when the packet IP Destination Address bitwise ANDed with the docsIetfQosPktClassInetDestMask value equals the docsIetfQosPktClassInetDestAddr value. The address type of this object is specified by docsIetfQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of '00000000'H.
.1.3.6.1.2.1.127.1.1.1.12,DOCS-IETF-QOS-MIB::docsIetfQosPktClassInetDestMask,OCTET,read-only,,current,,This object specifies which bits of a packet's IP Destination Address are compared to match this rule. An IP packet matches the rule when the packet destination address bitwise ANDed with the docsIetfQosPktClassInetDestMask value equals the docsIetfQosIpPktClassInetDestAddr value. The address type of this object is specified by docsIetfQosPktClassInetAddressType. If the referenced parameter is not present in a classifier, this object reports the value of 'FFFFFFFF'H.
.1.3.6.1.2.1.127.1.1.1.13,DOCS-IETF-QOS-MIB::docsIetfQosPktClassSourcePortStart,Unsigned32,read-only,,current,,This object specifies the low-end inclusive range of TCP/UDP source port numbers to which a packet is compared. This object is irrelevant for non-TCP/UDP IP packets. If the referenced parameter is not present in a classifier, this object reports the value of 0.
.1.3.6.1.2.1.127.1.1.1.14,DOCS-IETF-QOS-MIB::docsIetfQosPktClassSourcePortEnd,Unsigned32,read-only,,current,,This object specifies the high-end inclusive range of TCP/UDP source port numbers to which a packet is compared. This object is irrelevant for non-TCP/UDP IP packets. If the referenced parameter is not present in a classifier, this object reports the value of 65535.
.1.3.6.1.2.1.127.1.1.1.15,DOCS-IETF-QOS-MIB::docsIetfQosPktClassDestPortStart,Unsigned32,read-only,,current,,This object specifies the low-end inclusive range of TCP/UDP destination port numbers to which a packet is compared. If the referenced parameter is not present in a classifier, this object reports the value of 0.
.1.3.6.1.2.1.127.1.1.1.16,DOCS-IETF-QOS-MIB::docsIetfQosPktClassDestPortEnd,Unsigned32,read-only,,current,,This object specifies the high-end inclusive range of TCP/UDP destination port numbers to which a packet is compared. If the referenced parameter is not present in a classifier, this object reports the value of 65535.
.1.3.6.1.2.1.127.1.1.1.17,DOCS-IETF-QOS-MIB::docsIetfQosPktClassDestMacAddr,OCTET,read-only,,current,,An Ethernet packet matches an entry when its destination MAC address bitwise ANDed with docsIetfQosPktClassDestMacMask equals the value of docsIetfQosPktClassDestMacAddr. If the referenced parameter is not present in a classifier, this object reports the value of '000000000000'H.
.1.3.6.1.2.1.127.1.1.1.18,DOCS-IETF-QOS-MIB::docsIetfQosPktClassDestMacMask,OCTET,read-only,,current,,An Ethernet packet matches an entry when its destination MAC address bitwise ANDed with docsIetfQosPktClassDestMacMask equals the value of docsIetfQosPktClassDestMacAddr. If the referenced parameter is not present in a classifier, this object reports the value of '000000000000'H.
.1.3.6.1.2.1.127.1.1.1.19,DOCS-IETF-QOS-MIB::docsIetfQosPktClassSourceMacAddr,OCTET,read-only,,current,,An Ethernet packet matches this entry when its source MAC address equals the value of this object. If the referenced parameter is not present in a classifier, this object reports the value of 'FFFFFFFFFFFF'H.
.1.3.6.1.2.1.127.1.1.1.20,DOCS-IETF-QOS-MIB::docsIetfQosPktClassEnetProtocolType,INTEGER,read-only,,current,none(0):ethertype(1):dsap(2):mac(3):all(4),This object indicates the format of the layer 3 protocol ID in the Ethernet packet. A value of none(0) means that the rule does not use the layer 3 protocol type as a matching criteria. A value of ethertype(1) means that the rule applies only to frames that contain an EtherType value. Ethertype values are contained in packets using the Dec-Intel-Xerox (DIX) encapsulation or the RFC1042 Sub-Network Access Protocol (SNAP) encapsulation formats. A value of dsap(2) means that the rule applies only to frames using the IEEE802.3 encapsulation format with a Destination Service Access Point (DSAP) other than 0xAA (which is reserved for SNAP). A value of mac(3) means that the rule applies only to MAC management messages for MAC management messages. A value of all(4) means that the rule matches all Ethernet packets. If the Ethernet frame contains an 802.1P/Q Tag header (i.e., EtherType 0x8100), this object applies to the embedded EtherType field within the 802.1P/Q header. If the referenced parameter is not present in a classifier, this object reports the value of 0.
.1.3.6.1.2.1.127.1.1.1.21,DOCS-IETF-QOS-MIB::docsIetfQosPktClassEnetProtocol,Integer32,read-only,,current,,If docsIetfQosEthPktClassProtocolType is none(0), this object is ignored when considering whether a packet matches the current rule. If dosQosPktClassEnetProtocolType is ethertype(1), this object gives the 16-bit value of the EtherType that the packet must match in order to match the rule. If docsIetfQosPktClassEnetProtocolType is dsap(2), the lower 8 bits of this object's value must match the DSAP byte of the packet in order to match the rule. If docsIetfQosPktClassEnetProtocolType is mac(3), the lower 8 bits of this object's value represent a lower bound (inclusive) of MAC management message type codes matched, and the upper 8 bits represent the upper bound (inclusive) of matched MAC message type codes. Certain message type codes are excluded from matching, as specified in the reference. If the Ethernet frame contains an 802.1P/Q Tag header (i.e., EtherType 0x8100), this object applies to the embedded EtherType field within the 802.1P/Q header. If the referenced parameter is not present in the classifier, the value of this object is reported as 0.
.1.3.6.1.2.1.127.1.1.1.22,DOCS-IETF-QOS-MIB::docsIetfQosPktClassUserPriLow,Integer32,read-only,,current,,This object applies only to Ethernet frames using the 802.1P/Q tag header (indicated with EtherType 0x8100). Such frames include a 16-bit Tag that contains a 3-bit Priority field and a 12-bit VLAN number. Tagged Ethernet packets must have a 3-bit Priority field within the range of docsIetfQosPktClassPriLow to docsIetfQosPktClassPriHigh in order to match this rule. If the referenced parameter is not present in the classifier, the value of this object is reported as 0.
.1.3.6.1.2.1.127.1.1.1.23,DOCS-IETF-QOS-MIB::docsIetfQosPktClassUserPriHigh,Integer32,read-only,,current,,This object applies only to Ethernet frames using the 802.1P/Qtag header (indicated with EtherType 0x8100). Such frames include a 16-bit Tag that contains a 3-bit Priority field and a 12-bit VLAN number. Tagged Ethernet packets must have a 3-bit Priority field within the range of docsIetfQosPktClassPriLow to docsIetfQosPktClassPriHigh in order to match this rule. If the referenced parameter is not present in the classifier, the value of this object is reported as 7.
.1.3.6.1.2.1.127.1.1.1.24,DOCS-IETF-QOS-MIB::docsIetfQosPktClassVlanId,Integer32,read-only,,current,,This object applies only to Ethernet frames using the 802.1P/Q tag header. Tagged packets must have a VLAN Identifier that matches the value in order to match the rule. If the referenced parameter is not present in the classifier, the value of this object is reported as 0.
.1.3.6.1.2.1.127.1.1.1.25,DOCS-IETF-QOS-MIB::docsIetfQosPktClassStateActive,INTEGER,read-only,,current,true(1):false(2),This object indicates whether or not the classifier is enabled to classify packets to a Service Flow. If the referenced parameter is not present in the classifier, the value of this object is reported as true(1).
.1.3.6.1.2.1.127.1.1.1.26,DOCS-IETF-QOS-MIB::docsIetfQosPktClassPkts,Counter64,read-only,,current,,This object counts the number of packets that have been classified using this entry. This includes all packets delivered to a Service Flow maximum rate policing function, whether or not that function drops the packets. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.1.1.27,DOCS-IETF-QOS-MIB::docsIetfQosPktClassBitMap,BITS,read-only,,current,rulePriority(0):activationState(1):ipTos(2):ipProtocol(3):ipSourceAddr(4):ipSourceMask(5):ipDestAddr(6):ipDestMask(7):sourcePortStart(8):sourcePortEnd(9):destPortStart(10):destPortEnd(11):destMac(12):sourceMac(13):ethertype(14):userPri(15):vlanId(16),This object indicates which parameter encodings were actually present in the DOCSIS packet classifier encoding signaled in the DOCSIS message that created or modified the classifier. Note that Dynamic Service Change messages have replace semantics, so that all non-default parameters must be present whether the classifier is being created or changed. A bit of this object is set to 1 if the parameter indicated by the comment was present in the classifier encoding, and to 0 otherwise. Note that BITS are encoded most significant bit first, so that if, for example, bits 6 and 7 are set, this object is encoded as the octet string '030000'H.
.1.3.6.1.2.1.127.1.2,DOCS-IETF-QOS-MIB::docsIetfQosParamSetTable,,not-accessible,,current,,This table describes the set of DOCSIS 1.1 and 2.0 QOS parameters defined in a managed device. The ifIndex index specifies a DOCSIS MAC Domain. The docsIetfQosServiceFlowId index specifies a particular Service Flow. The docsIetfQosParamSetType index indicates whether the active, admitted, or provisioned QOS Parameter Set is being described by the row. Only the QOS Parameter Sets of DOCSIS 1.1 and 2.0 Service Flows are represented in this table. DOCSIS 1.0 QOS service profiles are not represented in this table. Each row corresponds to a DOCSIS QOS Parameter Set as signaled via DOCSIS MAC management messages. Each object in the row corresponds to one or part of one DOCSIS 1.1 Service Flow Encoding. The docsIetfQosParamSetBitMap object in the row indicates which particular parameters were signaled in the original registration or dynamic service request message that created the QOS Parameter Set. In many cases, even if a QOS Parameter Set parameter was not signaled, the DOCSIS specification calls for a default value to be used. That default value is reported as the value of the corresponding object in this row. Many objects are not applicable, depending on the Service Flow direction or upstream scheduling type. The object value reported in this case is specified in the DESCRIPTION clause.
.1.3.6.1.2.1.127.1.2.1,DOCS-IETF-QOS-MIB::docsIetfQosParamSetEntry,,not-accessible,ifIndex:docsIetfQosServiceFlowId:docsIetfQosParamSetType,current,,A unique set of QOS parameters.
.1.3.6.1.2.1.127.1.2.1.1,DOCS-IETF-QOS-MIB::docsIetfQosParamSetServiceClassName,OCTET,read-only,,current,,Refers to the Service Class Name from which the parameter set values were derived. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is a zero-length string.
.1.3.6.1.2.1.127.1.2.1.2,DOCS-IETF-QOS-MIB::docsIetfQosParamSetPriority,Integer32,read-only,,current,,The relative priority of a Service Flow. Higher numbers indicate higher priority. This priority should only be used to differentiate Service Flow from identical parameter sets. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0. If the parameter is not applicable, the reported value is 0.
.1.3.6.1.2.1.127.1.2.1.3,DOCS-IETF-QOS-MIB::docsIetfQosParamSetMaxTrafficRate,Unsigned32,read-only,,current,,Maximum sustained traffic rate allowed for this Service Flow in bits/sec. Must count all MAC frame data PDU from the bytes following the MAC header HCS to the end of the CRC. The number of bytes forwarded is limited during any time interval. The value 0 means no maximum traffic rate is enforced. This object applies to both upstream and downstream Service Flows. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0. If the parameter is not applicable, it is reported as 0.
.1.3.6.1.2.1.127.1.2.1.4,DOCS-IETF-QOS-MIB::docsIetfQosParamSetMaxTrafficBurst,Unsigned32,read-only,,current,,Specifies the token bucket size in bytes for this parameter set. The value is calculated from the byte following the MAC header HCS to the end of the CRC. This object is applied in conjunction with docsIetfQosParamSetMaxTrafficRate to calculate maximum sustained traffic rate. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object for scheduling types bestEffort (2), nonRealTimePollingService(3), and realTimePollingService(4) is 3044. If this parameter is not applicable, it is reported as 0. 
.1.3.6.1.2.1.127.1.2.1.5,DOCS-IETF-QOS-MIB::docsIetfQosParamSetMinReservedRate,Unsigned32,read-only,,current,,Specifies the guaranteed minimum rate in bits/sec for this parameter set. The value is calculated from the byte following the MAC header HCS to the end of the CRC. The default value of 0 means that no bandwidth is reserved. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0. If the parameter is not applicable, it is reported as 0.
.1.3.6.1.2.1.127.1.2.1.6,DOCS-IETF-QOS-MIB::docsIetfQosParamSetMinReservedPkt,Integer32,read-only,,current,,Specifies an assumed minimum packet size in bytes for which the docsIetfQosParamSetMinReservedRate will be provided. The value is calculated from the byte following the MAC header HCS to the end of the CRC. If the referenced parameter is omitted from a DOCSIS QOS parameter set, the default value is CMTS implementation dependent. In this case, the CMTS reports the default value it is using, and the CM reports a value of 0. If the referenced parameter is not applicable to the direction or scheduling type of the Service Flow, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.7,DOCS-IETF-QOS-MIB::docsIetfQosParamSetActiveTimeout,Integer32,read-only,,current,,Specifies the maximum duration in seconds that resources remain unused on an active service flow before CMTS signals that both active and admitted parameters set are null. The default value of 0 signifies an infinite amount of time. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 0.
.1.3.6.1.2.1.127.1.2.1.8,DOCS-IETF-QOS-MIB::docsIetfQosParamSetAdmittedTimeout,Integer32,read-only,,current,,Specifies the maximum duration in seconds that resources remain in admitted state before resources must be released. The value of 0 signifies an infinite amount of time. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object is 200. 
.1.3.6.1.2.1.127.1.2.1.9,DOCS-IETF-QOS-MIB::docsIetfQosParamSetMaxConcatBurst,Integer32,read-only,,current,,Specifies the maximum concatenated burst in bytes that an upstream Service Flow is allowed. The value is calculated from the FC byte of the Concatenation MAC Header to the last CRC byte in of the last concatenated MAC frame, inclusive. The value of 0 specifies no maximum burst. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set, the default value of this object for scheduling types bestEffort(2), nonRealTimePollingService(3), and realTimePollingService(4) is 1522. If the parameter is not applicable, this object's value is reported as 0.
.1.3.6.1.2.1.127.1.2.1.10,DOCS-IETF-QOS-MIB::docsIetfQosParamSetSchedulingType,INTEGER,read-only,,current,undefined(1):bestEffort(2):nonRealTimePollingService(3):realTimePollingService(4):unsolictedGrantServiceWithAD(5):unsolictedGrantService(6),Specifies the upstream scheduling service used for upstream Service Flow. If the referenced parameter is not present in the corresponding DOCSIS QOS Parameter Set of an upstream Service Flow, the default value of this object is bestEffort(2). For QOS parameter sets of downstream Service Flows, this object's value is reported as undefined(1).
.1.3.6.1.2.1.127.1.2.1.11,DOCS-IETF-QOS-MIB::docsIetfQosParamSetNomPollInterval,Unsigned32,read-only,,current,,Specifies the nominal interval in microseconds between successive unicast request opportunities on an upstream Service Flow. This object applies only to upstream Service Flows with DocsIetfQosSchedulingType of value nonRealTimePollingService(3), realTimePollingService(4), and unsolictedGrantServiceWithAD(5). The parameter is mandatory for realTimePollingService(4). If the parameter is omitted with nonRealTimePollingService(3), the CMTS uses an implementation-dependent value. If the parameter is omitted with unsolictedGrantServiceWithAD(5), the CMTS uses as a default value the value of the Nominal Grant Interval parameter. In all cases, the CMTS reports the value it is using when the parameter is applicable. The CM reports the signaled parameter value if it was signaled, and 0 otherwise. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.12,DOCS-IETF-QOS-MIB::docsIetfQosParamSetTolPollJitter,Unsigned32,read-only,,current,,Specifies the maximum amount of time in microseconds that the unicast request interval may be delayed from the nominal periodic schedule on an upstream Service Flow. This parameter is applicable only to upstream Service Flows with a DocsIetfQosSchedulingType of realTimePollingService(4) or unsolictedGrantServiceWithAD(5). If the referenced parameter is applicable but not present in the corresponding DOCSIS QOS Parameter Set, the CMTS uses an implementation-dependent value and reports the value it is using. The CM reports a value of 0 in this case. If the parameter is not applicable to the direction or upstream scheduling type of the Service Flow, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.13,DOCS-IETF-QOS-MIB::docsIetfQosParamSetUnsolicitGrantSize,Integer32,read-only,,current,,Specifies the unsolicited grant size in bytes. The grant size includes the entire MAC frame data PDU from the Frame Control byte to the end of the MAC frame. The referenced parameter is applicable only for upstream flows with a DocsIetfQosSchedulingType of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and it is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.14,DOCS-IETF-QOS-MIB::docsIetfQosParamSetNomGrantInterval,Unsigned32,read-only,,current,,Specifies the nominal interval in microseconds between successive data grant opportunities on an upstream Service Flow. The referenced parameter is applicable only for upstream flows with a DocsIetfQosSchedulingType of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and it is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.15,DOCS-IETF-QOS-MIB::docsIetfQosParamSetTolGrantJitter,Unsigned32,read-only,,current,,Specifies the maximum amount of time in microseconds that the transmission opportunities may be delayed from the nominal periodic schedule. The referenced parameter is applicable only for upstream flows with a DocsIetfQosSchedulingType of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and it is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.16,DOCS-IETF-QOS-MIB::docsIetfQosParamSetGrantsPerInterval,Integer32,read-only,,current,,Specifies the number of data grants per Nominal Grant Interval (docsIetfQosParamSetNomGrantInterval). The referenced parameter is applicable only for upstream flows with a DocsIetfQosSchedulingType of unsolicitedGrantServicewithAD(5) or unsolicitedGrantService(6), and it is mandatory when applicable. Both CMTS and CM report the signaled value of the parameter in this case. If the referenced parameter is not applicable to the direction or scheduling type of the corresponding DOCSIS QOS Parameter Set, both CMTS and CM report this object's value as 0.
.1.3.6.1.2.1.127.1.2.1.17,DOCS-IETF-QOS-MIB::docsIetfQosParamSetTosAndMask,OCTET,read-only,,current,,Specifies the AND mask for the IP TOS byte for overwriting IP packet's TOS value. The IP packet TOS byte is bitwise ANDed with docsIetfQosParamSetTosAndMask, and the result is bitwise ORed with docsIetfQosParamSetTosORMask and the result is written to the IP packet TOS byte. A value of 'FF'H for docsIetfQosParamSetTosAndMask and a value of '00'H for docsIetfQosParamSetTosOrMask means that the IP Packet TOS byte is not overwritten. This combination is reported if the referenced parameter is not present in a QOS Parameter Set. The IP TOS octet as originally defined in RFC 791 has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). Network operators SHOULD avoid specifying values of docsIetfQosParamSetTosAndMask and docsIetfQosParamSetTosORMask that would result in the modification of the ECN bits. In particular, operators should not use values of docsIetfQosParamSetTosAndMask that have either of the least-significant two bits set to 0. Similarly, operators should not use values of docsIetfQosParamSetTosORMask that have either of the least-significant two bits set to 1. Even though this object is only enforced by the Cable Modem Termination System (CMTS), Cable Modems MUST report the value as signaled in the referenced parameter.
.1.3.6.1.2.1.127.1.2.1.18,DOCS-IETF-QOS-MIB::docsIetfQosParamSetTosOrMask,OCTET,read-only,,current,,Specifies the OR mask for the IP TOS byte. See the description of docsIetfQosParamSetTosAndMask for further details. The IP TOS octet as originally defined in RFC 791 has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). Network operators SHOULD avoid specifying values of docsIetfQosParamSetTosAndMask and docsIetfQosParamSetTosORMask that would result in the modification of the ECN bits.
.1.3.6.1.2.1.127.1.2.1.19,DOCS-IETF-QOS-MIB::docsIetfQosParamSetMaxLatency,Unsigned32,read-only,,current,,Specifies the maximum latency between the reception of a packet by the CMTS on its NSI and the forwarding of the packet to the RF interface. A value of 0 signifies no maximum latency is enforced. This object only applies to downstream Service Flows. If the referenced parameter is not present in the corresponding downstream DOCSIS QOS Parameter Set, the default value is 0. This parameter is not applicable to upstream DOCSIS QOS Parameter Sets, and its value is reported as 0 in this case.
.1.3.6.1.2.1.127.1.2.1.20,DOCS-IETF-QOS-MIB::docsIetfQosParamSetType,INTEGER,not-accessible,,current,active(1):admitted(2):provisioned(3),Defines the type of the QOS parameter set defined by this row. active(1) indicates the Active QOS parameter set, describing the service currently being provided by the DOCSIS MAC domain to the Service Flow. admitted(2) indicates the Admitted QOS Parameter Set, describing services reserved by the DOCSIS MAC domain for use by the service flow. provisioned (3) describes the QOS Parameter Set defined in the DOCSIS CM Configuration file for the Service Flow.
.1.3.6.1.2.1.127.1.2.1.21,DOCS-IETF-QOS-MIB::docsIetfQosParamSetRequestPolicyOct,OCTET,read-only,,current,,Specifies which transmit interval opportunities the CM omits for upstream transmission requests and packet transmissions. This object takes its default value for downstream Service Flows. Unless otherwise indicated, a bit value of 1 means that a CM must not use that opportunity for upstream transmission. If bit 0 is the least significant bit of the least significant (4th) octet, and if bit number is increased with significance, the bit definitions are defined as follows: broadcastReqOpp(0): all CMs broadcast request opportunities priorityReqMulticastReq(1): priority request multicast request opportunities reqDataForReq(2): request/data opportunities for requests reqDataForData(3): request/data opportunities for data piggybackReqWithData(4): piggyback requests with data concatenateData(5): concatenate data fragmentData(6): fragment data suppresspayloadheaders(7): suppress payload headers dropPktsExceedUGSize(8): A value of 1 means that the Service Flow must drop packets that do not fit in the Unsolicited Grant size. If the referenced parameter is not present in a QOS Parameter Set, the value of this object is reported as '00000000'H.
.1.3.6.1.2.1.127.1.2.1.22,DOCS-IETF-QOS-MIB::docsIetfQosParamSetBitMap,BITS,read-only,,current,trafficPriority(0):maxTrafficRate(1):maxTrafficBurst(2):minReservedRate(3):minReservedPkt(4):activeTimeout(5):admittedTimeout(6):maxConcatBurst(7):schedulingType(8):requestPolicy(9):nomPollInterval(10):tolPollJitter(11):unsolicitGrantSize(12):nomGrantInterval(13):tolGrantJitter(14):grantsPerInterval(15):tosOverwrite(16):maxLatency(17),This object indicates the set of QOS Parameter Set parameters actually signaled in the DOCSIS registration or dynamic service request message that created or modified the QOS Parameter Set. A bit is set to 1 when the parameter described by the indicated reference section is present in the original request. Note that when Service Class names are expanded, the registration or dynamic response message may contain parameters as expanded by the CMTS based on a stored service class. These expanded parameters are not indicated by a 1 bit in this object. Note that even though some QOS Parameter Set parameters may not be signaled in a message (so that the paramater's bit in this object is 0), the DOCSIS specification requires that default values be used. These default values are reported as the corresponding object's value in the row. Note that BITS objects are encoded most significant bit first. For example, if bits 1 and 16 are set, the value of this object is the octet string '400080'H.
.1.3.6.1.2.1.127.1.3,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowTable,,not-accessible,,current,,This table describes the set of DOCSIS-QOS Service Flows in a managed device.
.1.3.6.1.2.1.127.1.3.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowEntry,,not-accessible,ifIndex:docsIetfQosServiceFlowId,current,,Describes a Service Flow. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.127.1.3.1.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowId,Unsigned32,not-accessible,,current,,An index assigned to a Service Flow by CMTS.
.1.3.6.1.2.1.127.1.3.1.2,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowSID,Unsigned32,read-only,,current,,Service Identifier (SID) assigned to an admitted or active Service Flow. This object reports a value of 0 if a Service ID is not associated with the Service Flow. Only active or admitted upstream Service Flows will have a Service ID (SID).
.1.3.6.1.2.1.127.1.3.1.3,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowDirection,INTEGER,read-only,,current,downstream(1):upstream(2),The direction of the Service Flow.
.1.3.6.1.2.1.127.1.3.1.4,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPrimary,INTEGER,read-only,,current,true(1):false(2),Object reflects whether Service Flow is the primary or a secondary Service Flow. A primary Service Flow is the default Service Flow for otherwise unclassified traffic and all MAC messages.
.1.3.6.1.2.1.127.1.4,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowStatsTable,,not-accessible,,current,,This table describes statistics associated with the Service Flows in a managed device.
.1.3.6.1.2.1.127.1.4.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowStatsEntry,,not-accessible,ifIndex:docsIetfQosServiceFlowId,current,,Describes a set of Service Flow statistics. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.127.1.4.1.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPkts,Counter64,read-only,,current,,For outgoing Service Flows, this object counts the number of Packet Data PDUs forwarded to this Service Flow. For incoming upstream CMTS service flows, this object counts the number of Packet Data PDUs actually received on the Service Flow identified by the SID for which the packet was scheduled. CMs not classifying downstream packets may report this object's value as 0 for downstream Service Flows. This object does not count MAC-specific management messages. Particularly for UGS flows, packets sent on the primary Service Flow in violation of the UGS grant size should be counted only by the instance of this object that is associated with the primary service flow. Unclassified upstream user data packets (i.e., non- MAC-management) forwarded to the primary upstream Service Flow should be counted by the instance of this object that is associated with the primary service flow. This object does include packets counted by docsIetfQosServiceFlowPolicedDelayPkts, but does not include packets counted by docsIetfQosServiceFlowPolicedDropPkts and docsIetfQosServiceFlowPHSUnknowns. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.4.1.2,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowOctets,Counter64,read-only,,current,,The number of octets from the byte after the MAC header HCS to the end of the CRC for all packets counted in the docsIetfQosServiceFlowPkts object for this row. Note that this counts the octets after payload header suppression and before payload header expansion have been applied. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.4.1.3,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowTimeCreated,TimeTicks,read-only,,current,,The value of sysUpTime when the service flow was created.
.1.3.6.1.2.1.127.1.4.1.4,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowTimeActive,Counter32,read-only,,current,,The number of seconds that the service flow has been active. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.4.1.5,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPHSUnknowns,Counter32,read-only,,current,,For incoming upstream CMTS service flows, this object counts the number of packets received with an unknown payload header suppression index. The service flow is identified by the SID for which the packet was scheduled. On a CM, only this object's instance for the primary downstream service flow counts packets received with an unknown payload header suppression index. All other downstream service flows on CM report this objects value as 0. All outgoing service flows report this object's value as 0. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.4.1.6,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPolicedDropPkts,Counter32,read-only,,current,,For outgoing service flows, this object counts the number of Packet Data PDUs classified to this service flow dropped due to: (1) implementation-dependent excessive delay while enforcing the Maximum Sustained Traffic Rate; or (2) UGS packets dropped due to exceeding the Unsolicited Grant Size with a Request/Transmission policy that requires such packets to be dropped. Classified packets dropped due to other reasons must be counted in ifOutDiscards for the interface of this service flow. This object reports 0 for incoming service flows. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.4.1.7,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowPolicedDelayPkts,Counter32,read-only,,current,,This object counts only outgoing packets delayed in order to maintain the Maximum Sustained Traffic Rate. This object will always report a value of 0 for UGS flows because the Maximum Sustained Traffic Rate does not apply. This object is 0 for incoming service flows. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.5,DOCS-IETF-QOS-MIB::docsIetfQosUpstreamStatsTable,,not-accessible,,current,,This table describes statistics associated with upstream service flows. All counted frames must be received without a Frame Check Sequence (FCS) error.
.1.3.6.1.2.1.127.1.5.1,DOCS-IETF-QOS-MIB::docsIetfQosUpstreamStatsEntry,,not-accessible,ifIndex:docsIetfQosSID,current,,Describes a set of upstream service flow statistics. An entry in the table exists for each upstream Service Flow in a managed device. The ifIndex is an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.127.1.5.1.1,DOCS-IETF-QOS-MIB::docsIetfQosSID,Unsigned32,not-accessible,,current,,Identifies a service ID for an admitted or active upstream service flow.
.1.3.6.1.2.1.127.1.5.1.2,DOCS-IETF-QOS-MIB::docsIetfQosUpstreamFragments,Counter32,read-only,,current,,The number of fragmentation headers received on an upstream service flow, regardless of whether the fragment was correctly reassembled into a valid packet. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.5.1.3,DOCS-IETF-QOS-MIB::docsIetfQosUpstreamFragDiscards,Counter32,read-only,,current,,The number of upstream fragments discarded and not assembled into a valid upstream packet. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.5.1.4,DOCS-IETF-QOS-MIB::docsIetfQosUpstreamConcatBursts,Counter32,read-only,,current,,The number of concatenation headers received on an upstream service flow. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6,DOCS-IETF-QOS-MIB::docsIetfQosDynamicServiceStatsTable,,not-accessible,,current,,This table describes statistics associated with the Dynamic Service Flows in a managed device.
.1.3.6.1.2.1.127.1.6.1,DOCS-IETF-QOS-MIB::docsIetfQosDynamicServiceStatsEntry,,not-accessible,ifIndex:docsIetfQosIfDirection,current,,Describes a set of dynamic service flow statistics. Two entries exist for each DOCSIS MAC layer interface for the upstream and downstream direction. On the CMTS, the downstream direction row indicates messages transmitted or transactions originated by the CMTS. The upstream direction row indicates messages received or transaction originated by the CM. On the CM, the downstream direction row indicates messages received or transactions originated by the CMTS. The upstream direction row indicates messages transmitted by the CM or transactions originated by the CM. The ifIndex is an ifType of docsCableMaclayer(127).
.1.3.6.1.2.1.127.1.6.1.1,DOCS-IETF-QOS-MIB::docsIetfQosIfDirection,INTEGER,not-accessible,,current,downstream(1):upstream(2),The direction of interface.
.1.3.6.1.2.1.127.1.6.1.2,DOCS-IETF-QOS-MIB::docsIetfQosDSAReqs,Counter32,read-only,,current,,The number of Dynamic Service Addition Requests, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.3,DOCS-IETF-QOS-MIB::docsIetfQosDSARsps,Counter32,read-only,,current,,The number of Dynamic Service Addition Responses, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.4,DOCS-IETF-QOS-MIB::docsIetfQosDSAAcks,Counter32,read-only,,current,,The number of Dynamic Service Addition Acknowledgements, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.5,DOCS-IETF-QOS-MIB::docsIetfQosDSCReqs,Counter32,read-only,,current,,The number of Dynamic Service Change Requests, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.6,DOCS-IETF-QOS-MIB::docsIetfQosDSCRsps,Counter32,read-only,,current,,The number of Dynamic Service Change Responses, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.7,DOCS-IETF-QOS-MIB::docsIetfQosDSCAcks,Counter32,read-only,,current,,The number of Dynamic Service Change Acknowledgements, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.8,DOCS-IETF-QOS-MIB::docsIetfQosDSDReqs,Counter32,read-only,,current,,The number of Dynamic Service Delete Requests, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.9,DOCS-IETF-QOS-MIB::docsIetfQosDSDRsps,Counter32,read-only,,current,,The number of Dynamic Service Delete Responses, including retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.10,DOCS-IETF-QOS-MIB::docsIetfQosDynamicAdds,Counter32,read-only,,current,,The number of successful Dynamic Service Addition transactions. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.11,DOCS-IETF-QOS-MIB::docsIetfQosDynamicAddFails,Counter32,read-only,,current,,The number of failed Dynamic Service Addition transactions. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.12,DOCS-IETF-QOS-MIB::docsIetfQosDynamicChanges,Counter32,read-only,,current,,The number of successful Dynamic Service Change transactions. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.13,DOCS-IETF-QOS-MIB::docsIetfQosDynamicChangeFails,Counter32,read-only,,current,,The number of failed Dynamic Service Change transactions. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.14,DOCS-IETF-QOS-MIB::docsIetfQosDynamicDeletes,Counter32,read-only,,current,,The number of successful Dynamic Service Delete transactions. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.15,DOCS-IETF-QOS-MIB::docsIetfQosDynamicDeleteFails,Counter32,read-only,,current,,The number of failed Dynamic Service Delete transactions. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.16,DOCS-IETF-QOS-MIB::docsIetfQosDCCReqs,Counter32,read-only,,current,,The number of Dynamic Channel Change Request messages traversing an interface. This count is nonzero only on downstream direction rows. This count should include the number of retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.17,DOCS-IETF-QOS-MIB::docsIetfQosDCCRsps,Counter32,read-only,,current,,The number of Dynamic Channel Change Response messages traversing an interface. This count is nonzero only on upstream direction rows. This count should include the number of retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.18,DOCS-IETF-QOS-MIB::docsIetfQosDCCAcks,Counter32,read-only,,current,,The number of Dynamic Channel Change Acknowledgement messages traversing an interface. This count is nonzero only on downstream direction rows. This count should include the number of retries. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.19,DOCS-IETF-QOS-MIB::docsIetfQosDCCs,Counter32,read-only,,current,,The number of successful Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.6.1.20,DOCS-IETF-QOS-MIB::docsIetfQosDCCFails,Counter32,read-only,,current,,The number of failed Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows. This counter's last discontinuity is the ifCounterDiscontinuityTime for the same ifIndex that indexes this object.
.1.3.6.1.2.1.127.1.7,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogTable,,not-accessible,,current,,This table contains a log of the disconnected Service Flows in a managed device.
.1.3.6.1.2.1.127.1.7.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogEntry,,not-accessible,docsIetfQosServiceFlowLogIndex,current,,The information regarding a single disconnected service flow.
.1.3.6.1.2.1.127.1.7.1.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogIndex,Unsigned32,not-accessible,,current,,Unique index for a logged service flow.
.1.3.6.1.2.1.127.1.7.1.2,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogIfIndex,Integer32,read-only,,current,,The ifIndex of ifType docsCableMaclayer(127) on the CMTS where the service flow was present.
.1.3.6.1.2.1.127.1.7.1.3,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogSFID,Unsigned32,read-only,,current,,The index assigned to the service flow by the CMTS.
.1.3.6.1.2.1.127.1.7.1.4,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogCmMac,OCTET,read-only,,current,,The MAC address for the cable modem associated with the service flow.
.1.3.6.1.2.1.127.1.7.1.5,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogPkts,Counter64,read-only,,current,,The number of packets counted on this service flow after payload header suppression.
.1.3.6.1.2.1.127.1.7.1.6,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogOctets,Counter64,read-only,,current,,The number of octets counted on this service flow after payload header suppression.
.1.3.6.1.2.1.127.1.7.1.7,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogTimeDeleted,TimeTicks,read-only,,current,,The value of sysUpTime when the service flow was deleted.
.1.3.6.1.2.1.127.1.7.1.8,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogTimeCreated,TimeTicks,read-only,,current,,The value of sysUpTime when the service flow was created.
.1.3.6.1.2.1.127.1.7.1.9,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogTimeActive,Counter32,read-only,,current,,The total time that the service flow was active.
.1.3.6.1.2.1.127.1.7.1.10,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogDirection,INTEGER,read-only,,current,downstream(1):upstream(2),The value of docsIetfQosServiceFlowDirection for the service flow.
.1.3.6.1.2.1.127.1.7.1.11,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogPrimary,INTEGER,read-only,,current,true(1):false(2),The value of docsIetfQosServiceFlowPrimary for the service flow.
.1.3.6.1.2.1.127.1.7.1.12,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogServiceClassName,OCTET,read-only,,current,,The value of docsIetfQosParamSetServiceClassName for the provisioned QOS Parameter Set of the service flow.
.1.3.6.1.2.1.127.1.7.1.13,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogPolicedDropPkts,Counter32,read-only,,current,,The final value of docsIetfQosServiceFlowPolicedDropPkts for the service flow.
.1.3.6.1.2.1.127.1.7.1.14,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogPolicedDelayPkts,Counter32,read-only,,current,,The final value of docsIetfQosServiceFlowPolicedDelayPkts for the service flow.
.1.3.6.1.2.1.127.1.7.1.15,DOCS-IETF-QOS-MIB::docsIetfQosServiceFlowLogControl,INTEGER,read-write,,current,active(1):destroy(6),Setting this object to the value destroy(6) removes this entry from the table. Reading this object returns the value active(1).
.1.3.6.1.2.1.127.1.8,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassTable,,not-accessible,,current,,This table describes the set of DOCSIS-QOS Service Classes in a CMTS.
.1.3.6.1.2.1.127.1.8.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassEntry,,not-accessible,docsIetfQosServiceClassName,current,,A provisioned service class on a CMTS. Each entry defines a template for certain DOCSIS QOS Parameter Set values. When a CM creates or modifies an Admitted QOS Parameter Set for a Service Flow, it may reference a Service Class Name instead of providing explicit QOS Parameter Set values. In this case, the CMTS populates the QOS Parameter Set with the applicable corresponding values from the named Service Class. Subsequent changes to a Service Class row do not affect the QOS Parameter Set values of any service flows already admitted. A service class template applies to only a single direction, as indicated in the docsIetfQosServiceClassDirection object.
.1.3.6.1.2.1.127.1.8.1.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassName,OCTET,not-accessible,,current,,Service Class Name. DOCSIS specifies that the maximum size is 16 ASCII characters including a terminating zero. The terminating zero is not represented in this SnmpAdminString syntax object.
.1.3.6.1.2.1.127.1.8.1.2,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create or delete rows in this table. There is no restriction on the ability to change values in this row while the row is active. Inactive rows need not be timed out.
.1.3.6.1.2.1.127.1.8.1.3,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPriority,Integer32,read-create,,current,,Template for docsIetfQosParamSetPriority.
.1.3.6.1.2.1.127.1.8.1.4,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassMaxTrafficRate,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetMaxTrafficRate.
.1.3.6.1.2.1.127.1.8.1.5,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassMaxTrafficBurst,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetMaxTrafficBurst.
.1.3.6.1.2.1.127.1.8.1.6,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassMinReservedRate,Unsigned32,read-create,,current,,Template for docsIetfQosParamSEtMinReservedRate.
.1.3.6.1.2.1.127.1.8.1.7,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassMinReservedPkt,Integer32,read-create,,current,,Template for docsIetfQosParamSetMinReservedPkt.
.1.3.6.1.2.1.127.1.8.1.8,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassMaxConcatBurst,Integer32,read-create,,current,,Template for docsIetfQosParamSetMaxConcatBurst.
.1.3.6.1.2.1.127.1.8.1.9,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassNomPollInterval,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetNomPollInterval.
.1.3.6.1.2.1.127.1.8.1.10,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassTolPollJitter,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetTolPollJitter.
.1.3.6.1.2.1.127.1.8.1.11,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassUnsolicitGrantSize,Integer32,read-create,,current,,Template for docsIetfQosParamSetUnsolicitGrantSize.
.1.3.6.1.2.1.127.1.8.1.12,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassNomGrantInterval,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetNomGrantInterval.
.1.3.6.1.2.1.127.1.8.1.13,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassTolGrantJitter,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetTolGrantJitter.
.1.3.6.1.2.1.127.1.8.1.14,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassGrantsPerInterval,Integer32,read-create,,current,,Template for docsIetfQosParamSetGrantsPerInterval.
.1.3.6.1.2.1.127.1.8.1.15,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassMaxLatency,Unsigned32,read-create,,current,,Template for docsIetfQosParamSetClassMaxLatency.
.1.3.6.1.2.1.127.1.8.1.16,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassActiveTimeout,Integer32,read-create,,current,,Template for docsIetfQosParamSetActiveTimeout.
.1.3.6.1.2.1.127.1.8.1.17,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassAdmittedTimeout,Integer32,read-create,,current,,Template for docsIetfQosParamSetAdmittedTimeout.
.1.3.6.1.2.1.127.1.8.1.18,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassSchedulingType,INTEGER,read-create,,current,undefined(1):bestEffort(2):nonRealTimePollingService(3):realTimePollingService(4):unsolictedGrantServiceWithAD(5):unsolictedGrantService(6),Template for docsIetfQosParamSetSchedulingType.
.1.3.6.1.2.1.127.1.8.1.19,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassRequestPolicy,OCTET,read-create,,current,,Template for docsIetfQosParamSetRequestPolicyOct.
.1.3.6.1.2.1.127.1.8.1.20,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassTosAndMask,OCTET,read-only,,current,,Template for docsIetfQosParamSetTosAndMask. The IP TOS octet as originally defined in RFC 791 has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). Network operators SHOULD avoid specifying values of docsIetfQosServiceClassTosAndMask and docsIetfQosServiceClassTosOrMask that would result in the modification of the ECN bits. In particular, operators should not use values of docsIetfQosServiceClassTosAndMask that have either of the least-significant two bits set to 0. Similarly,operators should not use values of docsIetfQosServiceClassTosOrMask that have either of the least-significant two bits set to 1.
.1.3.6.1.2.1.127.1.8.1.21,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassTosOrMask,OCTET,read-only,,current,,Template for docsIetfQosParamSetTosOrMask. The IP TOS octet as originally defined in RFC 791 has been superseded by the 6-bit Differentiated Services Field (DSField, RFC 3260) and the 2-bit Explicit Congestion Notification Field (ECN field, RFC 3168). Network operators SHOULD avoid specifying values of docsIetfQosServiceClassTosAndMask and docsIetfQosServiceClassTosOrMask that would result in the modification of the ECN bits. In particular, operators should not use values of docsIetfQosServiceClassTosAndMask that have either of the least-significant two bits set to 0. Similarly, operators should not use values of docsIetfQosServiceClassTosOrMask that have either of the least-significant two bits set to 1.
.1.3.6.1.2.1.127.1.8.1.22,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassDirection,INTEGER,read-create,,current,downstream(1):upstream(2),Specifies whether the service class template applies to upstream or downstream service flows.
.1.3.6.1.2.1.127.1.8.1.23,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this row is kept in volatile storage and lost upon reboot or whether it is backed up by non-volatile or permanent storage. 'permanent' entries need not allow writable access to any object.
.1.3.6.1.2.1.127.1.8.1.24,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassDSCPOverwrite,Integer32,read-create,,current,,This object allows the overwrite of the DSCP field per RFC 3260. If this object is -1, then the corresponding entry's docsIetfQosServiceClassTosAndMask value MUST be 'FF'H and docsIetfQosServiceClassTosOrMask MUST be '00'H. Otherwise, this object is in the range of 0..63, and the corresponding entry's docsIetfQosServiceClassTosAndMask value MUST be '03'H and the docsIetfQosServiceClassTosOrMask MUST be this object's value shifted left by two bit positions.
.1.3.6.1.2.1.127.1.9,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyTable,,not-accessible,,current,,This table describes the set of DOCSIS-QOS Service Class Policies. This table is an adjunct to the docsDevFilterPolicy table. Entries in the docsDevFilterPolicy table can point to specific rows in this table. This table permits mapping a packet to a service class name of an active service flow so long as a classifier does not exist at a higher priority.
.1.3.6.1.2.1.127.1.9.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyEntry,,not-accessible,docsIetfQosServiceClassPolicyIndex,current,,A service class name policy entry.
.1.3.6.1.2.1.127.1.9.1.1,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyIndex,Unsigned32,not-accessible,,current,,Index value to identify an entry in this table uniquely.
.1.3.6.1.2.1.127.1.9.1.2,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyName,OCTET,read-create,,current,,Service Class Name to identify the name of the service class flow to which the packet should be directed.
.1.3.6.1.2.1.127.1.9.1.3,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyRulePriority,Integer32,read-create,,current,,Service Class Policy rule priority for the entry.
.1.3.6.1.2.1.127.1.9.1.4,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create or delete rows in this table. This object should not be deleted if it is referenced by an entry in docsDevFilterPolicy. The reference should be deleted first. There is no restriction on the ability to change values in this row while the row is active. Inactive rows need not be timed out.
.1.3.6.1.2.1.127.1.9.1.5,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassPolicyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether this row is kept in volatile storage and lost upon reboot or whether it is backed up by non-volatile or permanent storage. 'permanent' entries need not allow writable access to any object.
.1.3.6.1.2.1.127.1.10,DOCS-IETF-QOS-MIB::docsIetfQosPHSTable,,not-accessible,,current,,This table describes the set of payload header suppression entries.
.1.3.6.1.2.1.127.1.10.1,DOCS-IETF-QOS-MIB::docsIetfQosPHSEntry,,not-accessible,ifIndex:docsIetfQosServiceFlowId:docsIetfQosPktClassId,current,,A payload header suppression entry. The ifIndex is an ifType of docsCableMaclayer(127). The index docsIetfQosServiceFlowId selects one service flow from the cable MAC layer interface. The docsIetfQosPktClassId index matches an index of the docsIetfQosPktClassTable.
.1.3.6.1.2.1.127.1.10.1.1,DOCS-IETF-QOS-MIB::docsIetfQosPHSField,OCTET,read-only,,current,,Payload header suppression field defines the bytes of the header that must be suppressed/restored by the sending/receiving device. The number of octets in this object should be the same as the value of docsIetfQosPHSSize.
.1.3.6.1.2.1.127.1.10.1.2,DOCS-IETF-QOS-MIB::docsIetfQosPHSMask,OCTET,read-only,,current,,Payload header suppression mask defines the bit mask that is used in combination with the docsIetfQosPHSField. It defines which bytes in the header must be suppressed/restored by the sending or receiving device. Each bit of this bit mask corresponds to a byte in the docsIetfQosPHSField, with the least significant bit corresponding to the first byte of the docsIetfQosPHSField. Each bit of the bit mask specifies whether the corresponding byte should be suppressed in the packet. A bit value of '1' indicates that the byte should be suppressed by the sending device and restored by the receiving device. A bit value of '0' indicates that the byte should not be suppressed by the sending device or restored by the receiving device. If the bit mask does not contain a bit for each byte in the docsIetfQosPHSField, then the bit mask is extended with bit values of '1' to be the necessary length.
.1.3.6.1.2.1.127.1.10.1.3,DOCS-IETF-QOS-MIB::docsIetfQosPHSSize,Integer32,read-only,,current,,Payload header suppression size specifies the number of bytes in the header to be suppressed and restored. The value of this object must match the number of bytes in the docsIetfQosPHSField.
.1.3.6.1.2.1.127.1.10.1.4,DOCS-IETF-QOS-MIB::docsIetfQosPHSVerify,INTEGER,read-only,,current,true(1):false(2),Payload header suppression verification value. If 'true', the sender must verify docsIetfQosPHSField is the same as what is contained in the packet to be suppressed.
.1.3.6.1.2.1.127.1.10.1.5,DOCS-IETF-QOS-MIB::docsIetfQosPHSIndex,Integer32,read-only,,current,,Payload header suppression index uniquely references the PHS rule for a given service flow.
.1.3.6.1.2.1.127.1.11,DOCS-IETF-QOS-MIB::docsIetfQosCmtsMacToSrvFlowTable,,not-accessible,,current,,This table provides for referencing the service flows associated with a particular cable modem. This allows indexing into other docsIetfQos tables that are indexed by docsIetfQosServiceFlowId and ifIndex.
.1.3.6.1.2.1.127.1.11.1,DOCS-IETF-QOS-MIB::docsIetfQosCmtsMacToSrvFlowEntry,,not-accessible,docsIetfQosCmtsCmMac:docsIetfQosCmtsServiceFlowId,current,,An entry is created by CMTS for each service flow connected to this CMTS.
.1.3.6.1.2.1.127.1.11.1.1,DOCS-IETF-QOS-MIB::docsIetfQosCmtsCmMac,OCTET,not-accessible,,current,,The MAC address for the referenced CM.
.1.3.6.1.2.1.127.1.11.1.2,DOCS-IETF-QOS-MIB::docsIetfQosCmtsServiceFlowId,Unsigned32,not-accessible,,current,,An index assigned to a service flow by CMTS.
.1.3.6.1.2.1.127.1.11.1.3,DOCS-IETF-QOS-MIB::docsIetfQosCmtsIfIndex,Integer32,read-only,,current,,The ifIndex of ifType docsCableMacLayer(127) on the CMTS that is connected to the Cable Modem.
.1.3.6.1.2.1.127.2,DOCS-IETF-QOS-MIB::docsIetfQosConformance,,,,,,
.1.3.6.1.2.1.127.2.1,DOCS-IETF-QOS-MIB::docsIetfQosGroups,,,,,,
.1.3.6.1.2.1.127.2.1.1,DOCS-IETF-QOS-MIB::docsIetfQosBaseGroup,,,,,,Group of objects implemented in both Cable Modems and Cable Modem Termination Systems.
.1.3.6.1.2.1.127.2.1.2,DOCS-IETF-QOS-MIB::docsIetfQosParamSetGroup,,,,,,Group of objects implemented in both Cable Modems and Cable Modem Termination Systems for QOS Parameter Sets.
.1.3.6.1.2.1.127.2.1.3,DOCS-IETF-QOS-MIB::docsIetfQosCmtsGroup,,,,,,Group of objects implemented only in the CMTS.
.1.3.6.1.2.1.127.2.1.4,DOCS-IETF-QOS-MIB::docsIetfQosSrvClassPolicyGroup,,,,,,Group of objects implemented in both Cable Modems and Cable Modem Termination Systems when supporting policy-based service flows.
.1.3.6.1.2.1.127.2.1.5,DOCS-IETF-QOS-MIB::docsIetfQosServiceClassGroup,,,,,,Group of objects implemented only in Cable Modem Termination Systems when supporting expansion of Service Class Names in a QOS Parameter Set
.1.3.6.1.2.1.127.2.2,DOCS-IETF-QOS-MIB::docsIetfQosCompliances,,,,,,
.1.3.6.1.2.1.127.2.2.1,DOCS-IETF-QOS-MIB::docsIetfQosCompliance,,,,,,The compliance statement for MCNS Cable Modems and Cable Modem Termination Systems that implement DOCSIS Service Flows.
.1.3.6.1.2.1.128,IANA-IPPM-METRICS-REGISTRY-MIB::ianaIppmMetricsRegistry,,,,,,With the approval and publication of RFC6248, this module is designated Obsolete. The registry will no longer be updated, and the current contents will be maintained as-is on the day that RFC6248 was published. The original Description text follows below: This module defines a registry for IP Performance Metrics. Registrations are done sequentially by IANA in the ianaIppmMetrics subtree on the bases of 'Specification Required' as defined in [RFC2434]. The reference of the specification must point to a stable document including a title, a revision and a date. The name always starts with the name of the organization and must respect the SMIv2 rules for descriptors defined in the section 3.1 of [RFC2578]; A document that creates new metrics would have an IANA considerations section in which it would describe new metrics to register. An OBJECT IDENTITY assigned to a metric is definitive and cannot be reused. If a new version of a metric is produced then it is assigned with a new name and a new identifier. Copyright (C) The Internet Society (2005). The initial version of this MIB module was published in RFC 4148; for full legal notices see the RFC itself or see: http://www.ietf.org/copyrights/ianamib.html. 
.1.3.6.1.2.1.128.1,IANA-IPPM-METRICS-REGISTRY-MIB::ianaIppmMetrics,,,,,,Registration point for IP Performance Metrics.
.1.3.6.1.2.1.128.1.1,IANA-IPPM-METRICS-REGISTRY-MIB::ietfInstantUnidirConnectivity,,,,,,Type-P-Instantaneous-Unidirectional-Connectivity
.1.3.6.1.2.1.128.1.2,IANA-IPPM-METRICS-REGISTRY-MIB::ietfInstantBidirConnectivity,,,,,,Type-P-Instantaneous-Bidirectional-Connectivity
.1.3.6.1.2.1.128.1.3,IANA-IPPM-METRICS-REGISTRY-MIB::ietfIntervalUnidirConnectivity,,,,,,Type-P-Interval-Unidirectional-Connectivity
.1.3.6.1.2.1.128.1.4,IANA-IPPM-METRICS-REGISTRY-MIB::ietfIntervalBidirConnectivity,,,,,,Type-P-Interval-Bidirectional-Connectivity
.1.3.6.1.2.1.128.1.5,IANA-IPPM-METRICS-REGISTRY-MIB::ietfIntervalTemporalConnectivity,,,,,,Type-P1-P2-Interval-Temporal-Connectivity
.1.3.6.1.2.1.128.1.6,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelay,,,,,,Type-P-One-way-Delay
.1.3.6.1.2.1.128.1.7,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelayPoissonStream,,,,,,Type-P-One-way-Delay-Poisson-Stream
.1.3.6.1.2.1.128.1.8,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelayPercentile,,,,,,Type-P-One-way-Delay-Percentile
.1.3.6.1.2.1.128.1.9,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelayMedian,,,,,,Type-P-One-way-Delay-Median
.1.3.6.1.2.1.128.1.10,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelayMinimum,,,,,,Type-P-One-way-Delay-Minimum
.1.3.6.1.2.1.128.1.11,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelayInversePercentile,,,,,,Type-P-One-way-Delay-Inverse-Percentile
.1.3.6.1.2.1.128.1.12,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPktLoss,,,,,,Type-P-One-way-Packet-Loss
.1.3.6.1.2.1.128.1.13,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPktLossPoissonStream,,,,,,Type-P-One-way-Packet-Loss-Poisson-Stream
.1.3.6.1.2.1.128.1.14,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPktLossAverage,,,,,,Type-P-One-way-Packet-Loss-Average
.1.3.6.1.2.1.128.1.15,IANA-IPPM-METRICS-REGISTRY-MIB::ietfRoundTripDelay,,,,,,Type-P-Round-trip-Delay
.1.3.6.1.2.1.128.1.16,IANA-IPPM-METRICS-REGISTRY-MIB::ietfRoundTripDelayPoissonStream,,,,,,Type-P-Round-trip-Delay-Poisson-Stream
.1.3.6.1.2.1.128.1.17,IANA-IPPM-METRICS-REGISTRY-MIB::ietfRoundTripDelayPercentile,,,,,,Type-P-Round-trip-Delay-Percentile
.1.3.6.1.2.1.128.1.18,IANA-IPPM-METRICS-REGISTRY-MIB::ietfRoundTripDelayMedian,,,,,,Type-P-Round-trip-Delay-Median
.1.3.6.1.2.1.128.1.19,IANA-IPPM-METRICS-REGISTRY-MIB::ietfRoundTripDelayMinimum,,,,,,Type-P-Round-trip-Delay-Minimum
.1.3.6.1.2.1.128.1.20,IANA-IPPM-METRICS-REGISTRY-MIB::ietfRoundTripDelayInvPercentile,,,,,,Type-P-Round-trip-Inverse-Percentile
.1.3.6.1.2.1.128.1.21,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayLossDistanceStream,,,,,,Type-P-One-Way-Loss-Distance-Stream
.1.3.6.1.2.1.128.1.22,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayLossPeriodStream,,,,,,Type-P-One-Way-Loss-Period-Stream
.1.3.6.1.2.1.128.1.23,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayLossNoticeableRate,,,,,,Type-P-One-Way-Loss-Noticeable-Rate
.1.3.6.1.2.1.128.1.24,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayLossPeriodTotal,,,,,,Type-P-One-Way-Loss-Period-Total
.1.3.6.1.2.1.128.1.25,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayLossPeriodLengths,,,,,,Type-P-One-Way-Loss-Period-Lengths
.1.3.6.1.2.1.128.1.26,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayInterLossPeriodLengths,,,,,,Type-P-One-Way-Inter-Loss-Period-Lengths
.1.3.6.1.2.1.128.1.27,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayIpdv,,,,,,Type-P-One-way-ipdv
.1.3.6.1.2.1.128.1.28,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayIpdvPoissonStream,,,,,,Type-P-One-way-ipdv-Poisson-stream
.1.3.6.1.2.1.128.1.29,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayIpdvPercentile,,,,,,Type-P-One-way-ipdv-percentile
.1.3.6.1.2.1.128.1.30,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayIpdvInversePercentile,,,,,,Type-P-One-way-ipdv-inverse-percentile
.1.3.6.1.2.1.128.1.31,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayIpdvJitter,,,,,,Type-P-One-way-ipdv-jitter
.1.3.6.1.2.1.128.1.32,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPeakToPeakIpdv,,,,,,Type-P-One-way-peak-to-peak-ipdv
.1.3.6.1.2.1.128.1.33,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayDelayPeriodicStream,,,,,,Type-P-One-way-Delay-Periodic-Stream
.1.3.6.1.2.1.128.1.34,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderedSingleton,,,,,,Type-P-Reordered
.1.3.6.1.2.1.128.1.35,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderedPacketRatio,,,,,,Type-P-Reordered-Ratio-Stream
.1.3.6.1.2.1.128.1.36,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingExtent,,,,,,Type-P-Packet-Reordering-Extent-Stream
.1.3.6.1.2.1.128.1.37,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingLateTimeOffset,,,,,,Type-P-Packet-Late-Time-Stream
.1.3.6.1.2.1.128.1.38,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingByteOffset,,,,,,Type-P-Packet-Byte-Offset-Stream
.1.3.6.1.2.1.128.1.39,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingGap,,,,,,Type-P-Packet-Reordering-Gap-Stream
.1.3.6.1.2.1.128.1.40,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingGapTime,,,,,,Type-P-Packet-Reordering-GapTime-Stream
.1.3.6.1.2.1.128.1.41,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingFreeRunx,,,,,,Type-P-Packet-Reordering-Free-Run-x-numruns-Stream
.1.3.6.1.2.1.128.1.42,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingFreeRunq,,,,,,Type-P-Packet-Reordering-Free-Run-q-squruns-Stream
.1.3.6.1.2.1.128.1.43,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingFreeRunp,,,,,,Type-P-Packet-Reordering-Free-Run-p-numpkts-Stream
.1.3.6.1.2.1.128.1.44,IANA-IPPM-METRICS-REGISTRY-MIB::ietfReorderingFreeRuna,,,,,,Type-P-Packet-Reordering-Free-Run-a-accpkts-Stream
.1.3.6.1.2.1.128.1.45,IANA-IPPM-METRICS-REGISTRY-MIB::ietfnReordering,,,,,,Type-P-Packet-n-Reordering-Stream
.1.3.6.1.2.1.128.1.46,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPacketArrivalCount,,,,,,Type-P-one-way-packet-arrival-count
.1.3.6.1.2.1.128.1.47,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPacketDuplication,,,,,,Type-P-one-way-packet-duplication
.1.3.6.1.2.1.128.1.48,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPacketDuplicationPoissonStream,,,,,,Type-P-one-way-Packet-Duplication-Poisson-Stream
.1.3.6.1.2.1.128.1.49,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPacketDuplicationPeriodicStream,,,,,,Type-P-one-way-Duplication-Periodic-Stream
.1.3.6.1.2.1.128.1.50,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPacketDuplicationFraction,,,,,,Type-P-one-way-packet-duplication-fraction
.1.3.6.1.2.1.128.1.51,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayReplicatedPacketRate,,,,,,Type-P-one-way-replicated-packet-rate
.1.3.6.1.2.1.128.1.52,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSpatialOneWayDelayVector,,,,,,Type-P-Spatial-One-way-Delay-Vector
.1.3.6.1.2.1.128.1.53,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSpatialPacketLossVector,,,,,,Type-P-Spatial-Packet-Loss-Vector
.1.3.6.1.2.1.128.1.54,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSpatialOneWayIpdvVector,,,,,,Type-P-Spatial-One-way-ipdv-Vector
.1.3.6.1.2.1.128.1.55,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSegmentOneWayDelayStream,,,,,,Type-P-Segment-One-way-Delay-Stream
.1.3.6.1.2.1.128.1.56,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSegmentPacketLossStream,,,,,,Type-P-Segment-Packet-Loss-Stream
.1.3.6.1.2.1.128.1.57,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSegmentIpdvPrevStream,,,,,,Type-P-Segment-ipdv-prev-Stream
.1.3.6.1.2.1.128.1.58,IANA-IPPM-METRICS-REGISTRY-MIB::ietfSegmentIpdvMinStream,,,,,,Type-P-Segment-ipdv-min-Stream
.1.3.6.1.2.1.128.1.59,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupDelayVector,,,,,,Type-P-One-to-group-Delay-Vector
.1.3.6.1.2.1.128.1.60,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupPacketLossVector,,,,,,Type-P-One-to-group-Packet-Loss-Vector
.1.3.6.1.2.1.128.1.61,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupIpdvVector,,,,,,Type-P-One-to-group-ipdv-Vector
.1.3.6.1.2.1.128.1.62,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOnetoGroupReceiverNMeanDelay,,,,,,Type-P-One-to-group-Receiver-n-Mean-Delay
.1.3.6.1.2.1.128.1.63,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupMeanDelay,,,,,,Type-P-One-to-group-Mean-Delay
.1.3.6.1.2.1.128.1.64,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupRangeMeanDelay,,,,,,Type-P-One-to-group-Range-Mean-Delay
.1.3.6.1.2.1.128.1.65,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupMaxMeanDelay,,,,,,Type-P-One-to-group-Max-Mean-Delay
.1.3.6.1.2.1.128.1.66,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupReceiverNLossRatio,,,,,,Type-P-One-to-group-Receiver-n-Loss-Ratio
.1.3.6.1.2.1.128.1.67,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupReceiverNCompLossRatio,,,,,,Type-P-One-to-group-Receiver-n-Comp-Loss-Ratio
.1.3.6.1.2.1.128.1.68,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupLossRatio,,,,,,Type-P-One-to-group-Loss-Ratio
.1.3.6.1.2.1.128.1.69,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupRangeLossRatio,,,,,,Type-P-One-to-group-Range-Loss-Ratio
.1.3.6.1.2.1.128.1.70,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneToGroupRangeDelayVariation,,,,,,Type-P-One-to-group-Range-Delay-Variation
.1.3.6.1.2.1.128.1.71,IANA-IPPM-METRICS-REGISTRY-MIB::ietfFiniteOneWayDelayStream,,,,,,Type-P-Finite-One-way-Delay-Stream
.1.3.6.1.2.1.128.1.72,IANA-IPPM-METRICS-REGISTRY-MIB::ietfFiniteOneWayDelayMean,,,,,,Type-P-Finite-One-way-Delay-Mean
.1.3.6.1.2.1.128.1.73,IANA-IPPM-METRICS-REGISTRY-MIB::ietfCompositeOneWayDelayMean,,,,,,Type-P-Finite-Composite-One-way-Delay-Mean
.1.3.6.1.2.1.128.1.74,IANA-IPPM-METRICS-REGISTRY-MIB::ietfFiniteOneWayDelayMinimum,,,,,,Type-P-Finite-One-way-Delay-Minimum
.1.3.6.1.2.1.128.1.75,IANA-IPPM-METRICS-REGISTRY-MIB::ietfCompositeOneWayDelayMinimum,,,,,,Type-P-Finite-Composite-One-way-Delay-Minimum
.1.3.6.1.2.1.128.1.76,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPktLossEmpiricProb,,,,,,Type-P-One-way-Packet-Loss-Empirical-Probability
.1.3.6.1.2.1.128.1.77,IANA-IPPM-METRICS-REGISTRY-MIB::ietfCompositeOneWayPktLossEmpiricProb,,,,,,Type-P-Composite-One-way-Packet-Loss-Empirical-Probability
.1.3.6.1.2.1.128.1.78,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPdvRefminStream,,,,,,Type-P-One-way-pdv-refmin-Stream
.1.3.6.1.2.1.128.1.79,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPdvRefminMean,,,,,,Type-P-One-way-pdv-refmin-Mean
.1.3.6.1.2.1.128.1.80,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPdvRefminVariance,,,,,,Type-P-One-way-pdv-refmin-Variance
.1.3.6.1.2.1.128.1.81,IANA-IPPM-METRICS-REGISTRY-MIB::ietfOneWayPdvRefminSkewness,,,,,,Type-P-One-way-pdv-refmin-Skewness
.1.3.6.1.2.1.128.1.82,IANA-IPPM-METRICS-REGISTRY-MIB::ietfCompositeOneWayPdvRefminQtil,,,,,,Type-P-Composite-One-way-pdv-refmin-quantile-a
.1.3.6.1.2.1.128.1.83,IANA-IPPM-METRICS-REGISTRY-MIB::ietfCompositeOneWayPdvRefminNPA,,,,,,Type-P-One-way-Composite-pdv-refmin-NPA
.1.3.6.1.2.1.129,VPN-TC-STD-MIB::vpnTcMIB,,,,,,This MIB contains TCs for VPNs. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4265; see the RFC itself for full legal notices.
.1.3.6.1.2.1.130,ENTITY-STATE-TC-MIB::entityStateTc,,,,,,This MIB defines state textual conventions. Copyright (C) The Internet Society 2005. This version of this MIB module is part of RFC 4268; see the RFC itself for full legal notices.
.1.3.6.1.2.1.131,ENTITY-STATE-MIB::entityStateMIB,,,,,,This MIB defines a state extension to the Entity MIB.  Copyright at The Internet Society 2005. This version of this MIB module is part of RFC 4268; see the RFC itself for full legal notices.
.1.3.6.1.2.1.131.0,ENTITY-STATE-MIB::entStateNotifications,,,,,,
.1.3.6.1.2.1.131.0.1,ENTITY-STATE-MIB::entStateOperEnabled,,,,,,An entStateOperEnabled notification signifies that the SNMP entity, acting in an agent role, has detected that the entStateOper object for one of its entities has transitioned into the 'enabled' state. The entity this notification refers can be identified by extracting the entPhysicalIndex from one of the variable bindings. The entStateAdmin and entStateAlarm varbinds may be examined to find out additional information on the administrative state at the time of the operation state change as well as to find out whether there were any known alarms against the entity at that time that may explain why the physical entity has become operationally disabled.
.1.3.6.1.2.1.131.0.2,ENTITY-STATE-MIB::entStateOperDisabled,,,,,,An entStateOperDisabled notification signifies that the SNMP entity, acting in an agent role, has detected that the entStateOper object for one of its entities has transitioned into the 'disabled' state. The entity this notification refers can be identified by extracting the entPhysicalIndex from one of the variable bindings. The entStateAdmin and entStateAlarm varbinds may be examined to find out additional information on the administrative state at the time of the operation state change as well as to find out whether there were any known alarms against the entity at that time that may affect the physical entity's ability to stay operationally enabled.
.1.3.6.1.2.1.131.1,ENTITY-STATE-MIB::entStateObjects,,,,,,
.1.3.6.1.2.1.131.1.1,ENTITY-STATE-MIB::entStateTable,,not-accessible,,current,,A table of information about state/status of entities. This is a sparse augment of the entPhysicalTable. Entries appear in this table for values of entPhysicalClass [RFC 4133] that in this implementation are able to report any of the state or status stored in this table. 
.1.3.6.1.2.1.131.1.1.1,ENTITY-STATE-MIB::entStateEntry,,not-accessible,entPhysicalIndex,current,,State information about this physical entity.
.1.3.6.1.2.1.131.1.1.1.1,ENTITY-STATE-MIB::entStateLastChanged,OCTET,read-only,,current,,The value of this object is the date and time when the value of any of entStateAdmin, entStateOper, entStateUsage, entStateAlarm, or entStateStandby changed for this entity. If there has been no change since the last re-initialization of the local system, this object contains the date and time of local system initialization. If there has been no change since the entity was added to the local system, this object contains the date and time of the insertion.
.1.3.6.1.2.1.131.1.1.1.2,ENTITY-STATE-MIB::entStateAdmin,INTEGER,read-write,,current,unknown(1):locked(2):shuttingDown(3):unlocked(4),The administrative state for this entity. This object refers to an entities administrative permission to service both other entities within its containment hierarchy as well other users of its services defined by means outside the scope of this MIB. Setting this object to 'notSupported' will result in an 'inconsistentValue' error. For entities that do not support administrative state, all set operations will result in an 'inconsistentValue' error. Some physical entities exhibit only a subset of the remaining administrative state values. Some entities cannot be locked, and hence this object exhibits only the 'unlocked' state. Other entities cannot be shutdown gracefully, and hence this object does not exhibit the 'shuttingDown' state. A value of 'inconsistentValue' will be returned if attempts are made to set this object to values not supported by its administrative model.
.1.3.6.1.2.1.131.1.1.1.3,ENTITY-STATE-MIB::entStateOper,INTEGER,read-only,,current,unknown(1):disabled(2):enabled(3):testing(4),The operational state for this entity. Note that unlike the state model used within the Interfaces MIB [RFC 2863], this object does not follow the administrative state. An administrative state of down does not predict an operational state of disabled. A value of 'testing' means that entity currently being tested and cannot therefore report whether it is operational or not. A value of 'disabled' means that an entity is totally inoperable and unable to provide service both to entities within its containment hierarchy, or to other receivers of its service as defined in ways outside the scope of this MIB. A value of 'enabled' means that an entity is fully or partially operable and able to provide service both to entities within its containment hierarchy, or to other receivers of its service as defined in ways outside the scope of this MIB. Note that some implementations may not be able to accurately report entStateOper while the entStateAdmin object has a value other than 'unlocked'. In these cases, this object MUST have a value of 'unknown'.
.1.3.6.1.2.1.131.1.1.1.4,ENTITY-STATE-MIB::entStateUsage,INTEGER,read-only,,current,unknown(1):idle(2):active(3):busy(4),The usage state for this entity. This object refers to an entity's ability to service more physical entities in a containment hierarchy. A value of 'idle' means this entity is able to contain other entities but that no other entity is currently contained within this entity. A value of 'active' means that at least one entity is contained within this entity, but that it could handle more. A value of 'busy' means that the entity is unable to handle any additional entities being contained in it. Some entities will exhibit only a subset of the usage state values. Entities that are unable to ever service any entities within a containment hierarchy will always have a usage state of 'busy'. Some entities will only ever be able to support one entity within its containment hierarchy and will therefore only exhibit values of 'idle' and 'busy'.
.1.3.6.1.2.1.131.1.1.1.5,ENTITY-STATE-MIB::entStateAlarm,BITS,read-only,,current,unknown(0):underRepair(1):critical(2):major(3):minor(4):warning(5):indeterminate(6),The alarm status for this entity. It does not include the alarms raised on child components within its containment hierarchy. A value of 'unknown' means that this entity is unable to report alarm state. Note that this differs from 'indeterminate', which means that alarm state is supported and there are alarms against this entity, but the severity of some of the alarms is not known. If no bits are set, then this entity supports reporting of alarms, but there are currently no active alarms against this entity.
.1.3.6.1.2.1.131.1.1.1.6,ENTITY-STATE-MIB::entStateStandby,INTEGER,read-only,,current,unknown(1):hotStandby(2):coldStandby(3):providingService(4),The standby status for this entity. Some entities will exhibit only a subset of the remaining standby state values. If this entity cannot operate in a standby role, the value of this object will always be 'providingService'.
.1.3.6.1.2.1.131.2,ENTITY-STATE-MIB::entStateConformance,,,,,,
.1.3.6.1.2.1.131.2.1,ENTITY-STATE-MIB::entStateCompliances,,,,,,
.1.3.6.1.2.1.131.2.1.1,ENTITY-STATE-MIB::entStateCompliance,,,,,,The compliance statement for systems supporting the Entity State MIB.
.1.3.6.1.2.1.131.2.2,ENTITY-STATE-MIB::entStateGroups,,,,,,
.1.3.6.1.2.1.131.2.2.1,ENTITY-STATE-MIB::entStateGroup,,,,,,Standard Entity State group.
.1.3.6.1.2.1.131.2.2.2,ENTITY-STATE-MIB::entStateNotificationsGroup,,,,,,Standard Entity State Notification group.
.1.3.6.1.2.1.132,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevNotifMIB,,,,,,The Event Notification MIB is an extension of the CABLE DEVICE MIB. It defines various notification objects for both cable modem and cable modem termination systems. Two groups of SNMP notification objects are defined. One group is for notifying cable modem events, and one group is for notifying cable modem termination system events. DOCSIS defines numerous events, and each event is assigned to a functional category. This MIB defines a notification object for each functional category. The varbinding list of each notification includes information about the event that occurred on the device. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4547; see the RFC itself for full legal notices.
.1.3.6.1.2.1.132.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevNotifControl,,,,,,
.1.3.6.1.2.1.132.1.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmNotifControl,BITS,read-write,,current,cmInitTLVUnknownNotif(0):cmDynServReqFailNotif(1):cmDynServRspFailNotif(2):cmDynServAckFailNotif(3):cmBpiInitNotif(4):cmBPKMNotif(5):cmDynamicSANotif(6):cmDHCPFailNotif(7):cmSwUpgradeInitNotif(8):cmSwUpgradeFailNotif(9):cmSwUpgradeSuccessNotif(10):cmSwUpgradeCVCNotif(11):cmTODFailNotif(12):cmDCCReqFailNotif(13):cmDCCRspFailNotif(14):cmDCCAckFailNotif(15),The object is used to enable specific CM notifications. For example, if the first bit is set, then docsDevCmInitTLVUnknownNotif is enabled. If it is not set, the notification is disabled. Note that notifications are also under the control of the MIB modules defined in RFC3413. If the device is rebooted,the value of this object SHOULD revert to the default value. 
.1.3.6.1.2.1.132.1.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsNotifControl,BITS,read-write,,current,cmtsInitRegReqFailNotif(0):cmtsInitRegRspFailNotif(1):cmtsInitRegAckFailNotif(2):cmtsDynServReqFailNotif(3):cmtsDynServRspFailNotif(4):cmtsDynServAckFailNotif(5):cmtsBpiInitNotif(6):cmtsBPKMNotif(7):cmtsDynamicSANotif(8):cmtsDCCReqFailNotif(9):cmtsDCCRspFailNotif(10):cmtsDCCAckFailNotif(11),The object is used to enable specific CMTS notifications. For example, if the first bit is set, then docsDevCmtsInitRegRspFailNotif is enabled. If it is not set, the notification is disabled. Note that notifications are also under the control of the MIB modules defined in RFC3413. If the device is rebooted,the value of this object SHOULD revert to the default value. 
.1.3.6.1.2.1.132.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::anonymous#0,,,,,,
.1.3.6.1.2.1.132.2.0,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmNotifs,,,,,,
.1.3.6.1.2.1.132.2.0.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmInitTLVUnknownNotif,,,,,,Notification to indicate that an unknown TLV was encountered during the TLV parsing process. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDynServReqFailNotif,,,,,,A notification to report the failure of a dynamic service request during the dynamic services process. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected to (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.3,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDynServRspFailNotif,,,,,, A notification to report the failure of a dynamic service response during the dynamic services process. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.4,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDynServAckFailNotif,,,,,,A notification to report the failure of a dynamic service acknowledgement during the dynamic services process. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.5,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmBpiInitNotif,,,,,,A notification to report the failure of a BPI initialization attempt during the registration process. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.6,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmBPKMNotif,,,,,,A notification to report the failure of a Baseline Privacy Key Management (BPKM) operation. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.7,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDynamicSANotif,,,,,,A notification to report the failure of a dynamic security association operation. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.8,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDHCPFailNotif,,,,,,A notification to report the failure of a DHCP operation. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsDevServerDhcp: the IP address of the DHCP server. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.9,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmSwUpgradeInitNotif,,,,,,A notification to indicate that a software upgrade has been initiated on the device. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.10,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmSwUpgradeFailNotif,,,,,,A notification to report the failure of a software upgrade attempt. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsDevSwFilename: the software image file name - docsDevSwServer: the IP address of the server that the image is retrieved from. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.11,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmSwUpgradeSuccessNotif,,,,,,A notification to report the software upgrade success status. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsDevSwFilename: the software image file name - docsDevSwServer: the IP address of the server that the image is retrieved from. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.12,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmSwUpgradeCVCFailNotif,,,,,,A notification to report that the verification of the code file has failed during a secure software upgrade attempt. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.13,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmTODFailNotif,,,,,,A notification to report the failure of a time of day operation. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsDevServerTime: the IP address of the time server. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.14,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDCCReqFailNotif,,,,,, A notification to report the failure of a dynamic channel change request during the dynamic channel change process on the CM. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.15,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDCCRspFailNotif,,,,,,A notification to report the failure of a dynamic channel change response during the dynamic channel change process on the CM. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.2.0.16,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmDCCAckFailNotif,,,,,,A notification to report the failure of a dynamic channel change acknowledgement during the dynamic channel change process on the CM. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - ifPhysAddress: the MAC address of the cable interface of this cable modem. - docsIfCmCmtsAddress: the MAC address of the CMTS to which the CM is connected (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface to which it is connected). - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmStatusDocsisOperMode: the QOS level (1.0, 1.1) that the CM is operating in. - docsIfCmtsCmStatusModulationType the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::anonymous#1,,,,,,
.1.3.6.1.2.1.132.3.0,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsNotifs,,,,,,
.1.3.6.1.2.1.132.3.0.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsInitRegReqFailNotif,,,,,,A notification to report the failure of a registration request from a CM during the CM initialization process that was detected on the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsInitRegRspFailNotif,,,,,,A notification to report the failure of a registration response during the CM initialization process that was detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.3,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsInitRegAckFailNotif,,,,,,A notification to report the failure of a registration acknowledgement from the CM during the CM initialization process that was detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.4,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDynServReqFailNotif,,,,,,A notification to report the failure of a dynamic service request during the dynamic services process that was detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.5,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDynServRspFailNotif,,,,,,A notification to report the failure of a dynamic service response during the dynamic services process that was detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.6,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDynServAckFailNotif,,,,,,A notification to report the failure of a dynamic service acknowledgement during the dynamic services process that was detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.7,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsBpiInitNotif,,,,,,A notification to report the failure of a BPI initialization attempt during the CM registration process that was detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.8,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsBPKMNotif,,,,,,A notification to report the failure of a BPKM operation that is detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.9,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDynamicSANotif,,,,,,A notification to report the failure of a dynamic security association operation that is detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.10,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDCCReqFailNotif,,,,,,A notification to report the failure of a dynamic channel change request during the dynamic channel change process and is detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.11,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDCCRspFailNotif,,,,,,A notification to report the failure of a dynamic channel change response during the dynamic channel change process and is detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.3.0.12,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsDCCAckFailNotif,,,,,,A notification to report the failure of a dynamic channel change acknowledgement during the dynamic channel change process and is detected by the CMTS. This notification sends additional information about the event by including the following objects in its varbinding list. - docsDevEvLevel: the priority level associated with the event. - docsDevEvId: the unique identifier of the event that occurred. - docsDevEvText: a textual description of the event. - docsIfCmtsCmStatusMacAddress: the MAC address of the CM with which this notification is associated. - ifPhysAddress: the MAC address of the CMTS (if there is a cable card/interface in the CMTS, then it is actually the MAC address of the cable interface that connected to the CM) cable interface connected to the CM. - docsIfCmtsCmStatusDocsisRegMode: the QOS level (1.0, 1.1) that the reporting CM is operating in. - docsIfDocsisBaseCapability: the highest version of the DOCSIS specification (1.0, 1.1, 2.0) that the device is capable of supporting. - docsIfCmtsCmStatusModulationType: the upstream modulation methodology used by the CM. 
.1.3.6.1.2.1.132.4,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevNotifConformance,,,,,,
.1.3.6.1.2.1.132.4.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevNotifGroups,,,,,,
.1.3.6.1.2.1.132.4.1.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmNotifControlGroup,,,,,,This group represents objects that allow control over CM Notifications.
.1.3.6.1.2.1.132.4.1.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmNotificationGroup,,,,,,A collection of CM notifications providing device status
.1.3.6.1.2.1.132.4.1.3,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsNotifControlGroup,,,,,,This group represents objects that allow control over CMTS Notifications.
.1.3.6.1.2.1.132.4.1.4,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsNotificationGroup,,,,,,A collection of CMTS notifications providing device status and control.
.1.3.6.1.2.1.132.4.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevNotifCompliances,,,,,,
.1.3.6.1.2.1.132.4.2.1,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmNotifCompliance,,,,,,The compliance statement for CM Notifications and Control.
.1.3.6.1.2.1.132.4.2.2,DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB::docsDevCmtsNotifCompliance,,,,,,The compliance statement for DOCSIS CMTS Notification and Control.
.1.3.6.1.2.1.133,MOBILEIPV6-MIB::mip6MIB,,,,,,The MIB module for monitoring Mobile-IPv6 entities. Copyright (C) The Internet Society 2006. This version of this MIB module is part of RFC 4295; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.133.0,MOBILEIPV6-MIB::mip6Notifications,,,,,,
.1.3.6.1.2.1.133.0.1,MOBILEIPV6-MIB::mip6MnRegistered,,,,,,This notification is sent by a home agent when a mobile node registers with the home agent for the first time. Notifications will not be sent for subsequent updates and/or refreshes. The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable. 
.1.3.6.1.2.1.133.0.2,MOBILEIPV6-MIB::mip6MnDeRegistered,,,,,,This notification is sent by a home agent every time a mobile node de-registers with the home agent by sending a Binding Update that requests the home agent to delete a binding. The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable. 
.1.3.6.1.2.1.133.0.3,MOBILEIPV6-MIB::mip6MnCOAChanged,,,,,,This notification is sent by a home agent every time a mobile node sends a Binding Update with a new care-of address (for an existing Binding Cache entry). Notifications will not be sent for subsequent updates and/or refreshes for the same Care-of address. The registration of a new care-of address may indicate that the mobile node has moved or that the primary care-of address of the mobile node has become deprecated. The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable. 
.1.3.6.1.2.1.133.0.4,MOBILEIPV6-MIB::mip6MnBindingExpiredAtHA,,,,,,This notification is sent by a home agent when a binding for the mobile node at the home agent expired (no timely Binding Updates were received). The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable. 
.1.3.6.1.2.1.133.0.5,MOBILEIPV6-MIB::mip6MnBindingExpiredAtCN,,,,,,This notification is sent by a correspondent node when a binding for the mobile node at the correspondent node expired (no timely Binding Updates were received). The MO instances in the notifications will be identified by the mip6BindingHomeAddressType and mip6BindingHomeAddress for the mobile node in the mip6BindingCacheTable. 
.1.3.6.1.2.1.133.1,MOBILEIPV6-MIB::mip6Objects,,,,,,
.1.3.6.1.2.1.133.1.1,MOBILEIPV6-MIB::mip6Core,,,,,,
.1.3.6.1.2.1.133.1.1.1,MOBILEIPV6-MIB::mip6System,,,,,,
.1.3.6.1.2.1.133.1.1.1.1,MOBILEIPV6-MIB::mip6Capabilities,BITS,read-only,,current,mobileNode(0):homeAgent(1):correspondentNode(2),This object indicates the Mobile IPv6 functions that are supported by this managed entity. Multiple Mobile IPv6 functions may be supported by a single entity. 
.1.3.6.1.2.1.133.1.1.1.2,MOBILEIPV6-MIB::mip6Status,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether the Mobile IPv6 function is enabled for the managed entity. If it is enabled, the agent discovery and registration functions will be operational. Changing the status from enabled(1) to disabled(2) will terminate the agent discovery and registration functions. On the other hand, changing the status from disabled(2) to enabled(1) will start the agent discovery and registration functions. The value of this object SHOULD remain unchanged across reboots of the managed entity. 
.1.3.6.1.2.1.133.1.1.2,MOBILEIPV6-MIB::mip6Bindings,,,,,,
.1.3.6.1.2.1.133.1.1.2.1,MOBILEIPV6-MIB::mip6BindingCacheTable,,not-accessible,,current,,This table models the Binding Cache on the managed entity. The cache is maintained by home agents and correspondent nodes. It contains both correspondent registration entries and home registration entries. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.133.1.1.2.1.1,MOBILEIPV6-MIB::mip6BindingCacheEntry,,not-accessible,mip6BindingHomeAddressType:mip6BindingHomeAddress,current,,This entry represents a conceptual row in the binding cache table. It represents a single Binding Update. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.1.2.1.1.1,MOBILEIPV6-MIB::mip6BindingHomeAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6BindingHomeAddress that follows. 
.1.3.6.1.2.1.133.1.1.2.1.1.2,MOBILEIPV6-MIB::mip6BindingHomeAddress,OCTET,not-accessible,,current,,The home address of the mobile node corresponding to the Binding Cache entry. This field is used as the key for searching the mobile node's current care-of address in the Binding Cache. The type of the address represented by this object is specified by the corresponding mip6BindingHomeAddressType object. 
.1.3.6.1.2.1.133.1.1.2.1.1.3,MOBILEIPV6-MIB::mip6BindingCOAType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6BindingCOA that follows. 
.1.3.6.1.2.1.133.1.1.2.1.1.4,MOBILEIPV6-MIB::mip6BindingCOA,OCTET,read-only,,current,,The care-of address of the mobile node indicated by the home address field (mip6BindingHomeAddress) in this Binding Cache entry. The type of the address represented by this object is specified by the corresponding mip6BindingCOAType object. 
.1.3.6.1.2.1.133.1.1.2.1.1.5,MOBILEIPV6-MIB::mip6BindingTimeRegistered,OCTET,read-only,,current,,The timestamp when this Binding Cache entry was created. 
.1.3.6.1.2.1.133.1.1.2.1.1.6,MOBILEIPV6-MIB::mip6BindingTimeGranted,Gauge32,read-only,,current,,The lifetime in seconds granted to the mobile node for this registration. 
.1.3.6.1.2.1.133.1.1.2.1.1.7,MOBILEIPV6-MIB::mip6BindingTimeRemaining,Gauge32,read-only,,current,,The lifetime in seconds remaining for this registration. 
.1.3.6.1.2.1.133.1.1.2.1.1.8,MOBILEIPV6-MIB::mip6BindingHomeRegn,INTEGER,read-only,,current,true(1):false(2),This object indicates whether or not this Binding Cache entry is a home registration entry (applicable only on nodes that support home agent functionality). 
.1.3.6.1.2.1.133.1.1.2.1.1.9,MOBILEIPV6-MIB::mip6BindingMaxSeq,Unsigned32,read-only,,current,,The maximum value of the Sequence Number field received in previous Binding Updates for this home address (mip6BindingHomeAddress). 
.1.3.6.1.2.1.133.1.1.2.1.1.10,MOBILEIPV6-MIB::mip6BindingUsageTS,OCTET,read-only,,current,,The timestamp when this entry was last looked up. 
.1.3.6.1.2.1.133.1.1.2.1.1.11,MOBILEIPV6-MIB::mip6BindingUsageCount,Gauge32,read-only,,current,,The number of times this entry was looked up. 
.1.3.6.1.2.1.133.1.1.2.1.1.12,MOBILEIPV6-MIB::mip6BindingAdminStatus,INTEGER,read-write,,current,active(1):inactive(2),This is an administrative object used to control the status of a binding cache entry. By default the value will be 'active'(1). A value of 'inactive'(2) will indicate that the validity of the entry is suspended. It does not exist in the binding cache for all practical purposes. The state can be changed from 'active' to 'inactive' by operator intervention. Causing the state to change to 'inactive' results in the entry being deleted from the cache. Attempts to change the status from 'inactive' to 'active' will be rejected. 
.1.3.6.1.2.1.133.1.1.2.2,MOBILEIPV6-MIB::mip6BindingHistoryTable,,not-accessible,,current,,A table containing a record of the bindings. 
.1.3.6.1.2.1.133.1.1.2.2.1,MOBILEIPV6-MIB::mip6BindingHistoryEntry,,not-accessible,mip6BindingHstHomeAddressType:mip6BindingHstHomeAddress:mip6BindingHstIndex,current,,The record of a binding. Implementors need to be aware that if the total number of octets in mip6BindingHstHomeAddress exceeds 112, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.1.2.2.1.1,MOBILEIPV6-MIB::mip6BindingHstHomeAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6BindingHstHomeAddress that follows. 
.1.3.6.1.2.1.133.1.1.2.2.1.2,MOBILEIPV6-MIB::mip6BindingHstHomeAddress,OCTET,not-accessible,,current,,Mobile node's home address. The type of the address represented by this object is specified by the corresponding mip6BindingHstHomeAddressType object. 
.1.3.6.1.2.1.133.1.1.2.2.1.3,MOBILEIPV6-MIB::mip6BindingHstIndex,Unsigned32,not-accessible,,current,,The index to uniquely identify this record along with the mobile node's HomeAddress type and HomeAddress. It should be monotonically increasing. It may wrap after reaching its max value.
.1.3.6.1.2.1.133.1.1.2.2.1.4,MOBILEIPV6-MIB::mip6BindingHstCOAType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6BindingHstCOA that follows. 
.1.3.6.1.2.1.133.1.1.2.2.1.5,MOBILEIPV6-MIB::mip6BindingHstCOA,OCTET,read-only,,current,,Mobile node's care-of address. One mobile node can have multiple bindings with different care-of addresses. The type of the address represented by this object is specified by the corresponding mip6BindingHstCOAType object. 
.1.3.6.1.2.1.133.1.1.2.2.1.6,MOBILEIPV6-MIB::mip6BindingHstTimeRegistered,OCTET,read-only,,current,,The timestamp when this Binding Cache entry was created. 
.1.3.6.1.2.1.133.1.1.2.2.1.7,MOBILEIPV6-MIB::mip6BindingHstTimeExpired,OCTET,read-only,,current,,The timestamp when this Binding Cache entry expired. 
.1.3.6.1.2.1.133.1.1.2.2.1.8,MOBILEIPV6-MIB::mip6BindingHstHomeRegn,INTEGER,read-only,,current,true(1):false(2),This object indicates whether or not this Binding Cache entry is a home registration entry (applicable only on nodes that support home agent functionality). 
.1.3.6.1.2.1.133.1.1.2.2.1.9,MOBILEIPV6-MIB::mip6BindingHstUsageTS,OCTET,read-only,,current,,The timestamp when this entry was last looked up. 
.1.3.6.1.2.1.133.1.1.2.2.1.10,MOBILEIPV6-MIB::mip6BindingHstUsageCount,Gauge32,read-only,,current,,The number of times this entry was looked up. 
.1.3.6.1.2.1.133.1.1.3,MOBILEIPV6-MIB::mip6Stats,,,,,,
.1.3.6.1.2.1.133.1.1.3.1,MOBILEIPV6-MIB::mip6TotalTraffic,,,,,,
.1.3.6.1.2.1.133.1.1.3.1.1,MOBILEIPV6-MIB::mip6InOctets,Counter32,read-only,,current,,The total number of octets in the MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.2,MOBILEIPV6-MIB::mip6HCInOctets,Counter64,read-only,,current,,The total number of octets in the MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6InOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.3,MOBILEIPV6-MIB::mip6InPkts,Counter32,read-only,,current,,The number of MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.4,MOBILEIPV6-MIB::mip6HCInPkts,Counter64,read-only,,current,,The number of MIPv6 datagrams received by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6InPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.5,MOBILEIPV6-MIB::mip6OutOctets,Counter32,read-only,,current,,The total number of octets in the MIPv6 datagrams sent by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.6,MOBILEIPV6-MIB::mip6HCOutOctets,Counter64,read-only,,current,,The total number of octets in the MIPv6 datagrams sent by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6OutOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.7,MOBILEIPV6-MIB::mip6OutPkts,Counter32,read-only,,current,,The number of MIPv6 datagrams sent by the MIPv6 entity. This will include the datagrams with Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.8,MOBILEIPV6-MIB::mip6HCOutPkts,Counter64,read-only,,current,,The number of MIPv6 datagrams sent by the MIPv6 entity. This will include datagrams with the Mobility Header, the Home Address option in the Destination Option extension header (Next Header value = 60), or the type 2 Routing Header. It will also include the IPv6 datagrams that are reverse tunneled to a home agent from a mobile node's home address. This object is a 64-bit version of mip6OutPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.1.9,MOBILEIPV6-MIB::mip6CounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this MIPv6 entities global counters, viz., counters with OID prefix 'mip6TotalTraffic' or 'mip6CnGlobalStats' or 'mip6HaGlobalStats' suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. 
.1.3.6.1.2.1.133.1.1.3.2,MOBILEIPV6-MIB::mip6NodeTrafficTable,,not-accessible,,current,,A table containing MIPv6 traffic counters per mobile node. 
.1.3.6.1.2.1.133.1.1.3.2.1,MOBILEIPV6-MIB::mip6NodeTrafficEntry,,not-accessible,mip6BindingHomeAddressType:mip6BindingHomeAddress,current,,The MIPv6 traffic statistics for a mobile node. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.1.3.2.1.1,MOBILEIPV6-MIB::mip6NodeInOctets,Counter32,read-only,,current,,The total number of octets in the MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.2,MOBILEIPV6-MIB::mip6HCNodeInOctets,Counter64,read-only,,current,,The total number of octets in the MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. This object is a 64-bit version of mip6NodeInOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.3,MOBILEIPV6-MIB::mip6NodeInPkts,Counter32,read-only,,current,,The number of MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include the datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.4,MOBILEIPV6-MIB::mip6HCNodeInPkts,Counter64,read-only,,current,,The number of MIPv6 datagrams received from the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the Home Address option in the Destination Option extension header (Next Header value = 60). It will also include the IPv6 datagrams that are reverse tunneled to a home agent from the mobile node's home address. This object is a 64-bit version of mip6NodeInPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.5,MOBILEIPV6-MIB::mip6NodeOutOctets,Counter32,read-only,,current,,The total number of octets in the MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.6,MOBILEIPV6-MIB::mip6HCNodeOutOctets,Counter64,read-only,,current,,The total number of octets in the MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. This object is a 64-bit version of mip6NodeOutOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.7,MOBILEIPV6-MIB::mip6NodeOutPkts,Counter32,read-only,,current,,The number of MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.8,MOBILEIPV6-MIB::mip6HCNodeOutPkts,Counter64,read-only,,current,,The number of MIPv6 datagrams sent to the mobile node by the MIPv6 entity. This will include datagrams with the Mobility Header or the type 2 Routing Header. It will also include the IPv6 datagrams that are tunneled by a home agent to the mobile node. This object is a 64-bit version of mip6NodeOutOctets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6NodeCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.1.3.2.1.9,MOBILEIPV6-MIB::mip6NodeCtrDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of the counters in this row suffered a discontinuity. The relevant counters are the specific instances of any Counter32 or Counter64 objects in this row. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value. 
.1.3.6.1.2.1.133.1.2,MOBILEIPV6-MIB::mip6Mn,,,,,,
.1.3.6.1.2.1.133.1.2.1,MOBILEIPV6-MIB::mip6MnSystem,,,,,,
.1.3.6.1.2.1.133.1.2.1.1,MOBILEIPV6-MIB::mip6MnHomeAddressTable,,not-accessible,,current,,A table containing registration status for all the home addresses pertaining to the mobile node. 
.1.3.6.1.2.1.133.1.2.1.1.1,MOBILEIPV6-MIB::mip6MnHomeAddressEntry,,not-accessible,mip6MnHomeAddressType:mip6MnHomeAddress,current,,The registration status for a home address. Implementors need to be aware that if the total number of octets in mip6MnHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.2.1.1.1.1,MOBILEIPV6-MIB::mip6MnHomeAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6MnHomeAddress that follows. 
.1.3.6.1.2.1.133.1.2.1.1.1.2,MOBILEIPV6-MIB::mip6MnHomeAddress,OCTET,not-accessible,,current,,A unicast routable address assigned to the mobile node. This is used as the 'permanent address' of the mobile node in the sense that it remains unchanged regardless of the mobile node's current point of attachment. If mobile node doesn't have a home address assigned yet, then this object will take the default 'unspecified' value ::0. The type of the address represented by this object is specified by the corresponding mip6MnHomeAddressType object. 
.1.3.6.1.2.1.133.1.2.1.1.1.3,MOBILEIPV6-MIB::mip6MnHomeAddressState,INTEGER,read-only,,current,unknown(1):home(2):registered(3):pending(4):isolated(5),This object indicates the state of the mobile node: unknown -- The state of the mobile node cannot be determined. home -- mobile node is on the home network. registered -- mobile node is on a foreign network and is registered with the home agent. pending -- mobile node has sent registration request to the home agent and is waiting for the reply. isolated -- mobile node is isolated from network, i.e., it is not in its home network, it is not registered, and no registration ack is pending. 
.1.3.6.1.2.1.133.1.2.2,MOBILEIPV6-MIB::mip6MnConf,,,,,,
.1.3.6.1.2.1.133.1.2.2.1,MOBILEIPV6-MIB::mip6MnDiscoveryRequests,Counter32,read-only,,current,,Total number of ICMP Dynamic Home Agent Address Discovery Requests sent by the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.2,MOBILEIPV6-MIB::mip6MnDiscoveryReplies,Counter32,read-only,,current,,Total number of ICMP Dynamic Home Agent Address Discovery Replies received by the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.3,MOBILEIPV6-MIB::mip6MnDiscoveryTimeouts,Counter32,read-only,,current,,Total number of ICMP Dynamic Home Agent Address Discovery Requests that timed out. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.4,MOBILEIPV6-MIB::mip6MnPrefixSolicitationsSent,Counter32,read-only,,current,,Total number of ICMP Mobile Prefix Solicitations sent by the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.5,MOBILEIPV6-MIB::mip6MnPrefixAdvsRecd,Counter32,read-only,,current,,Total number of ICMP Mobile Prefix Advertisements received by the mobile node. This will include the ICMP Mobile Prefix Advertisements that failed the validity checks. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.6,MOBILEIPV6-MIB::mip6MnPrefixAdvsIgnored,Counter32,read-only,,current,,Total number of Mobile Prefix Advertisements discarded by the validity check. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.7,MOBILEIPV6-MIB::mip6MnMovedToFN,Counter32,read-only,,current,,Number of times the mobile node has detected movement to a foreign network from another foreign network or from the home network, has reconstructed its care-of address and has initiated the care-of address registration process. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.2.8,MOBILEIPV6-MIB::mip6MnMovedToHN,Counter32,read-only,,current,,Number of times the mobile node has detected movement from a foreign network to its home network. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3,MOBILEIPV6-MIB::mip6MnRegistration,,,,,,
.1.3.6.1.2.1.133.1.2.3.1,MOBILEIPV6-MIB::mip6MnBLTable,,not-accessible,,current,,This table corresponds to the Binding Update List (BL) that is maintained by the mobile node. The list holds an item for every binding that the mobile node has established or is trying to establish. Both correspondent and home registrations are included in this table. Entries from the table are deleted as the lifetime of the binding expires. 
.1.3.6.1.2.1.133.1.2.3.1.1,MOBILEIPV6-MIB::mip6MnBLEntry,,not-accessible,mip6MnHomeAddressType:mip6MnHomeAddress:mip6MnBLNodeAddressType:mip6MnBLNodeAddress,current,,Information about a Binding Update sent by the mobile node either to its home agent or to one of its correspondent nodes. Implementors need to be aware that if the total number of octets in mip6MnHomeAddress and mip6MnBLNodeAddress exceeds 111, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.2.3.1.1.1,MOBILEIPV6-MIB::mip6MnBLNodeAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6MnBLNodeAddress that follows. 
.1.3.6.1.2.1.133.1.2.3.1.1.2,MOBILEIPV6-MIB::mip6MnBLNodeAddress,OCTET,not-accessible,,current,,The address of the agent as used in the destination address of the Binding Update. The agent may be a home agent or a correspondent node. The type of the address represented by this object is specified by the corresponding mip6MnBLNodeAddressType object. 
.1.3.6.1.2.1.133.1.2.3.1.1.3,MOBILEIPV6-MIB::mip6MnBLCOAType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mip6MnBLCOA that follows. 
.1.3.6.1.2.1.133.1.2.3.1.1.4,MOBILEIPV6-MIB::mip6MnBLCOA,OCTET,read-only,,current,,Care-of address that the mobile node intends to register in the Binding Update request. The type of the address represented by this object is specified by the corresponding mip6MnBLCOAType object. 
.1.3.6.1.2.1.133.1.2.3.1.1.5,MOBILEIPV6-MIB::mip6MnBLLifeTimeRequested,Unsigned32,read-only,,current,,The lifetime requested by the mobile node (in seconds) in the Binding Update. 
.1.3.6.1.2.1.133.1.2.3.1.1.6,MOBILEIPV6-MIB::mip6MnBLLifeTimeGranted,Unsigned32,read-only,,current,,The lifetime granted to the mobile node for this binding. This field will be inaccessible if the Binding Update request has not been accepted. The lifetime remaining (lR) can be calculated using the current time (cT), mip6MnBLAcceptedTime (aT) and mip6MnBLLifeTimeGranted (lG) as follows: lR = lG - (cT - aT). When lR is zero, this entry will be deleted from the Binding Update List and consequently from this table. 
.1.3.6.1.2.1.133.1.2.3.1.1.7,MOBILEIPV6-MIB::mip6MnBLMaxSeq,Unsigned32,read-only,,current,,The maximum value of the Sequence Number field sent in previous Binding Updates to this destination. 
.1.3.6.1.2.1.133.1.2.3.1.1.8,MOBILEIPV6-MIB::mip6MnBLTimeSent,OCTET,read-only,,current,,The time when the last (re-)transmission occurred.
.1.3.6.1.2.1.133.1.2.3.1.1.9,MOBILEIPV6-MIB::mip6MnBLAccepted,INTEGER,read-only,,current,true(1):false(2),true(1) if the mobile node has received a binding acknowledgment indicating that service has been accepted (status code 0 or 1); false(2) otherwise. false(2) implies that the registration is still pending. 
.1.3.6.1.2.1.133.1.2.3.1.1.10,MOBILEIPV6-MIB::mip6MnBLAcceptedTime,OCTET,read-only,,current,,The time at which the mobile node receives a binding acknowledgment indicating that Binding Update has been accepted (status code 0 or 1); This object will be inaccessible if the Binding Update request is still pending. 
.1.3.6.1.2.1.133.1.2.3.1.1.11,MOBILEIPV6-MIB::mip6MnBLRetransmissions,Gauge32,read-only,,current,,The number of Binding Update retransmissions. 
.1.3.6.1.2.1.133.1.2.3.1.1.12,MOBILEIPV6-MIB::mip6MnBLDontSendBUFlag,INTEGER,read-only,,current,true(1):false(2),true(1) indicates that future binding updates will not be sent to mip6MnBLNodeAddress. false(2) implies that binding updates will be sent to mip6MnBLNodeAddress. The mobile node sets this flag in the when it receives an ICMP Parameter Problem, Code 1, error message in response to a return routability message or Binding Update sent to mip6MnBLNodeAddress. 
.1.3.6.1.2.1.133.1.2.3.2,MOBILEIPV6-MIB::mip6MnRegnCounters,,,,,,
.1.3.6.1.2.1.133.1.2.3.2.1,MOBILEIPV6-MIB::mip6MnMobilityMessagesSent,Counter32,read-only,,current,,The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, sent by the mobile node. There are 3 types of mobility messages, viz., Home Test Init, Care-of Test Init, and Binding Updates, that are sent by mobile nodes. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.2,MOBILEIPV6-MIB::mip6MnMobilityMessagesRecd,Counter32,read-only,,current,,The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, received by the mobile node. There are 5 types of mobility messages, viz., Home Test, Care-of Test, Binding Acknowledgment, Binding Refresh Request, and Binding Error, that are sent to mobile nodes. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.3,MOBILEIPV6-MIB::mip6MnBUsToHA,Counter32,read-only,,current,,Total number of Binding Updates sent to the mobile node's home agent(s). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.4,MOBILEIPV6-MIB::mip6MnBUAcksFromHA,Counter32,read-only,,current,,Total number of valid binding acknowledgments received from the mobile node's home agent(s). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.5,MOBILEIPV6-MIB::mip6MnBUsToCN,Counter32,read-only,,current,,Total number of Binding Updates sent to correspondent nodes by the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.6,MOBILEIPV6-MIB::mip6MnBUAcksFromCN,Counter32,read-only,,current,,Total number of valid Binding Update acks received from all the correspondent nodes. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.7,MOBILEIPV6-MIB::mip6MnBindingErrorsFromCN,Counter32,read-only,,current,,Total number of Binding Error messages received by mobile node from CN. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.8,MOBILEIPV6-MIB::mip6MnICMPErrorsRecd,Counter32,read-only,,current,,Total number of ICMP Error messages of type ICMP Parameter Problem, Code 1 or Code 2, received by the mobile node from a correspondent node in response to a return routability procedure, a Binding Update, or a packet with the Home Address option. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.2.3.2.9,MOBILEIPV6-MIB::mip6MnBRRequestsRecd,Counter32,read-only,,current,,The total number of Binding Refresh requests received by the mobile node from correspondent nodes. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3,MOBILEIPV6-MIB::mip6Cn,,,,,,
.1.3.6.1.2.1.133.1.3.1,MOBILEIPV6-MIB::mip6CnSystem,,,,,,
.1.3.6.1.2.1.133.1.3.2,MOBILEIPV6-MIB::mip6CnStats,,,,,,
.1.3.6.1.2.1.133.1.3.2.1,MOBILEIPV6-MIB::mip6CnGlobalStats,,,,,,
.1.3.6.1.2.1.133.1.3.2.1.1,MOBILEIPV6-MIB::mip6CnHomeTestInitsRecd,Counter32,read-only,,current,,Total number of Home Test Init messages received. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.2,MOBILEIPV6-MIB::mip6CnHomeTestsSent,Counter32,read-only,,current,,Total number of Home Test messages sent. If a Home Test Init message is found to be valid, a Home Test message will be generated and sent. Otherwise the Home Test message is silently discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.3,MOBILEIPV6-MIB::mip6CnCareOfTestInitsRecd,Counter32,read-only,,current,,Total number of Care-of Test Init messages received. 
.1.3.6.1.2.1.133.1.3.2.1.4,MOBILEIPV6-MIB::mip6CnCareOfTestsSent,Counter32,read-only,,current,,Total number of Care-of Test messages sent. If a Care-of Test Init message is found to be valid, a Care-of Test message will be generated and sent. Otherwise the Care-of Test message is silently discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.5,MOBILEIPV6-MIB::mip6CnBUsRecd,Counter32,read-only,,current,,Total number of Binding Updates received by the correspondent node from mobile nodes. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.6,MOBILEIPV6-MIB::mip6CnBUAcksSent,Counter32,read-only,,current,,Total number of acknowledgments sent by the correspondent node for the Binding Updates received. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.7,MOBILEIPV6-MIB::mip6CnBRsSent,Counter32,read-only,,current,,Total number of Binding Refresh Request messages sent by the correspondent node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.8,MOBILEIPV6-MIB::mip6CnBindingErrors,Counter32,read-only,,current,,Total number of Binding Error messages sent by the correspondent node to the mobile node. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.9,MOBILEIPV6-MIB::mip6CnBUsAccepted,Counter32,read-only,,current,,Total number of Binding Updates accepted by the correspondent node. If a Binding Acknowledgment message is sent for the Binding Update request, the Status code field in the message will have a value less than 128. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.10,MOBILEIPV6-MIB::mip6CnBUsRejected,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the correspondent node. If a Binding Acknowledgment message has been sent for the Binding Update request, the Status code field in the message will have a value greater than or equal to 128. Otherwise the Binding Update request will be silently discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.11,MOBILEIPV6-MIB::mip6CnReasonUnspecified,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the correspondent node with status code in the Binding Acknowledgment message indicating 'reason unspecified' (Code 128). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.12,MOBILEIPV6-MIB::mip6CnInsufficientResource,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the correspondent node with status code in the Binding Acknowledgment message indicating 'insufficient resources' (Code 130). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.13,MOBILEIPV6-MIB::mip6CnHomeRegnNotSupported,Counter32,read-only,,current,,Total number of Binding Update requests rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'home registration not supported' (Code 131). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.14,MOBILEIPV6-MIB::mip6CnSeqNumberOutOfWindow,Counter32,read-only,,current,,Total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'sequence number out of window' (Code 135). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.15,MOBILEIPV6-MIB::mip6CnExpiredHomeNonceIndex,Counter32,read-only,,current,,The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'expired home nonce index' (Code 136). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.16,MOBILEIPV6-MIB::mip6CnExpiredCareOfNonceIndex,Counter32,read-only,,current,,The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'expired care-of nonce index' (Code 137). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.17,MOBILEIPV6-MIB::mip6CnExpiredNonce,Counter32,read-only,,current,,The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'expired nonces' (Code 138), i.e., the correspondent node no longer recognizes the Home Nonce Index value and the Care-of Nonce Index value. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.1.18,MOBILEIPV6-MIB::mip6CnRegTypeChangeDisallowed,Counter32,read-only,,current,,The total number of Binding Updates rejected by correspondent node with status code in the Binding Acknowledgment message indicating 'registration type change disallowed' (Code 139), i.e., a binding already exists for the given home address and the home registration flag has a different value than the Home Registration (H) bit in the Binding Update. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.2,MOBILEIPV6-MIB::mip6CnCounterTable,,not-accessible,,current,,A table containing each mobile .
.1.3.6.1.2.1.133.1.3.2.2.1,MOBILEIPV6-MIB::mip6CnCounterEntry,,not-accessible,mip6BindingHomeAddressType:mip6BindingHomeAddress,current,,The set of correspondent node counters for a mobile node. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.3.2.2.1.1,MOBILEIPV6-MIB::mip6CnBURequestsAccepted,Counter32,read-only,,current,,Total number of Binding Update requests from the mobile node accepted by the correspondent node. If Binding Acknowledgment messages are sent, then the status code in the message will have a value less than 128. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CnCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.2.1.2,MOBILEIPV6-MIB::mip6CnBURequestsRejected,Counter32,read-only,,current,,Total number of Binding Update requests from the mobile node that have been rejected by the correspondent node. This includes the Binding Update requests for which a Binding Acknowledgment message has been sent with status code value greater than or equal to 128 and the Binding Acknowledgment requests that have been silently discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CnCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.3.2.2.1.3,MOBILEIPV6-MIB::mip6CnBCEntryCreationTime,OCTET,read-only,,current,,The time when the current Binding Cache entry was created for the mobile node. 
.1.3.6.1.2.1.133.1.3.2.2.1.4,MOBILEIPV6-MIB::mip6CnBUAcceptedTime,OCTET,read-only,,current,,The time at which the last Binding Update was accepted by the correspondent node and the corresponding Binding Cache entry was updated. 
.1.3.6.1.2.1.133.1.3.2.2.1.5,MOBILEIPV6-MIB::mip6CnBURejectionTime,OCTET,read-only,,current,,The time at which the last Binding Update message was rejected by the correspondent node. If there have been no rejections, then this object will be inaccessible. 
.1.3.6.1.2.1.133.1.3.2.2.1.6,MOBILEIPV6-MIB::mip6CnBURejectionCode,INTEGER,read-only,,current,reasonUnspecified(1):admProhibited(2):insufficientResource(3):homeRegistrationNotSupported(4):notHomeSubnet(5):notHomeAgentForThisMobileNode(6):duplicateAddressDetectionFailed(7):sequenceNumberOutOfWindow(8):expiredHomeNonceIndex(9):expiredCareofNonceIndex(10):expiredNonces(11):registrationTypeChangeDisallowed(12),If a Binding Acknowledgment is sent to the mobile node, this is the status code (> 128) that is returned in the Binding Acknowledgment. In case a Binding Acknowledgment is not sent to the mobile node, then this will be the value of the Status code that corresponds to the reason of the rejection. If there have been no rejections, then this object will be inaccessible. 
.1.3.6.1.2.1.133.1.3.2.2.1.7,MOBILEIPV6-MIB::mip6CnCtrDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of counters in this row, viz., instances of 'mip6CnBURequestsAccepted' and 'mip6CnBURequestsRejected', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. 
.1.3.6.1.2.1.133.1.4,MOBILEIPV6-MIB::mip6Ha,,,,,,
.1.3.6.1.2.1.133.1.4.1,MOBILEIPV6-MIB::mip6HaAdvertisement,,,,,,
.1.3.6.1.2.1.133.1.4.1.1,MOBILEIPV6-MIB::mip6HaAdvsRecd,Counter32,read-only,,current,,Total number of valid Router Advertisements received with the Home Agent (H) bit set, on all the links on which it is serving as a Home Agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.1.2,MOBILEIPV6-MIB::mip6HaAdvsSent,Counter32,read-only,,current,,Total number of unsolicited multicast Router Advertisements sent with the Home Agent (H) bit set, on all the links on which the router is serving as a Home Agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.1.3,MOBILEIPV6-MIB::mip6HaConfTable,,not-accessible,,current,,A table containing configurable advertisement parameters for all interfaces on which the home agent service is advertised. It is RECOMMENDED that the last written values of the objects in the conceptual rows of this table will remain unchanged across reboots of the managed entity provided that the interfaces have not been renumbered after the reboot. 
.1.3.6.1.2.1.133.1.4.1.3.1,MOBILEIPV6-MIB::mip6HaConfEntry,,not-accessible,ipv6InterfaceIfIndex,current,,Advertisement parameters for an interface. The instances of the columnar objects in this entry pertain to the interface that is uniquely identified by the ipv6InterfaceIfIndex of the interface. The same ipv6InterfaceIfIndex object is used to uniquely identify instances of the columnar objects of this conceptual row. 
.1.3.6.1.2.1.133.1.4.1.3.1.1,MOBILEIPV6-MIB::mip6HaAdvPreference,Integer32,read-write,,current,,The preference value for the home agent to be used in the Router Advertisements. Higher value denotes greater preference. 
.1.3.6.1.2.1.133.1.4.1.3.1.2,MOBILEIPV6-MIB::mip6HaAdvLifetime,Integer32,read-write,,current,,The lifetime value for the home agent to be used in the Router Advertisements. 
.1.3.6.1.2.1.133.1.4.1.3.1.3,MOBILEIPV6-MIB::mip6HaPrefixAdv,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the home agent should support sending of the ICMP Mobile Prefix Advertisements. If it is disabled(2), the home agent will not send ICMP Mobile Prefix Advertisements to the mobile nodes. The state can be changed from enabled(1) to disabled(2) and vice versa by operator intervention. Causing the state to change from enabled(1) to disabled(2) will result in the home agent disabling the Prefix advertisement function. On the other hand, changing the status from disabled(2) to enabled(1) will start the prefix advertisement function. 
.1.3.6.1.2.1.133.1.4.1.3.1.4,MOBILEIPV6-MIB::mip6HaPrefixSolicitation,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the home agent should respond to ICMP Mobile Prefix Solicitation messages it receives from the mobile nodes. By default, the value will be set to enabled(1). If it is disabled(2), the home agent will not respond to any ICMP Mobile Prefix Solicitation messages. The state can be changed from enabled(1) to disabled(2), by operator intervention. Causing the state to change from enabled(1) to disabled(2) will result in the home agent not responding to any ICMP Mobile Prefix Solicitation messages it receives from the mobile nodes. 
.1.3.6.1.2.1.133.1.4.1.3.1.5,MOBILEIPV6-MIB::mip6HaMCastCtlMsgSupport,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether the home agent should enable support for the processing of the multicast group membership control messages it receives from the mobile nodes. By default, the value will be set to enabled(1). If it is disabled(2), the home agent will not process any multicast group control messages it receives from the mobile nodes. The state can be changed from enabled(1) to disabled(2), by operator intervention. Causing the state to change from enabled(1) to disabled(2) will result in the home agent disabling the processing of the multicast group control messages it received from the mobile nodes. 
.1.3.6.1.2.1.133.1.4.1.4,MOBILEIPV6-MIB::mip6HaListTable,,not-accessible,,current,,This table models the Home Agents List that contains the list of all routers that are acting as home agents on each of the interfaces on which the home agent service is offered by this router. 
.1.3.6.1.2.1.133.1.4.1.4.1,MOBILEIPV6-MIB::mip6HaListEntry,,not-accessible,ipv6InterfaceIfIndex:mip6HaLinkLocalAddressType:mip6HaLinkLocalAddress,current,,Information about a router that is offering home agent service. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6HaLinkLocalAddressType and mip6HaLinkLocalAddress. The interface is uniquely identified by its ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex object is used in conjunction with the mip6HaLinkLocalAddressType and mip6HaLinkLocalAddress to uniquely identify instances of the columnar objects of this row. Implementors need to be aware that if the total number of octets in mip6HaLinkLocalAddress exceeds 112, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.4.1.4.1.1,MOBILEIPV6-MIB::mip6HaLinkLocalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type for the link-local address of the home agent that follows. 
.1.3.6.1.2.1.133.1.4.1.4.1.2,MOBILEIPV6-MIB::mip6HaLinkLocalAddress,OCTET,not-accessible,,current,,The link local address of the home agent. The type of the address represented by this object is specified by the corresponding mip6HaLinkLocalAddressType object. 
.1.3.6.1.2.1.133.1.4.1.4.1.3,MOBILEIPV6-MIB::mip6HaPreference,Integer32,read-only,,current,,The preference value of this home agent. Higher values indicate a more preferable home agent. The preference value is obtained from the preference field of the received Router Advertisement. 
.1.3.6.1.2.1.133.1.4.1.4.1.4,MOBILEIPV6-MIB::mip6HaRecvLifeTime,Gauge32,read-only,,current,,The lifetime for this home agent. 
.1.3.6.1.2.1.133.1.4.1.4.1.5,MOBILEIPV6-MIB::mip6HaRecvTimeStamp,OCTET,read-only,,current,,The time when the home agent advertisement was received. 
.1.3.6.1.2.1.133.1.4.1.5,MOBILEIPV6-MIB::mip6HaGlAddrTable,,not-accessible,,current,,This table contains the global addresses of the home agents in the Home Agents List. 
.1.3.6.1.2.1.133.1.4.1.5.1,MOBILEIPV6-MIB::mip6HaGlAddrEntry,,not-accessible,ipv6InterfaceIfIndex:mip6HaLinkLocalAddressType:mip6HaLinkLocalAddress:mip6HaGaAddrSeqNo,current,,A global address for a home agent in the Home Agents List. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress and mip6HaGaAddrSeqNo. The mip6HaGaAddrSeqNo object is used to distinguish between multiple instances of the home agent global addresses on the same interface for the same set of mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress, values. There is no upper-bound on the maximum number of global addresses on an interface but, for practical purposes, the upper-bound of the value mip6HaGaAddrSeqNo is set to 1024. The interface is uniquely identified by its ipv6InterfaceIfIndex. The same ipv6InterfaceIfIndex object is used in conjunction with the mip6HaLinkLocalAddressType, mip6HaLinkLocalAddress, and mip6HaGaAddrSeqNo to uniquely identify instances of the columnar objects of this row. Implementors need to be aware that if the total number of octets in mip6HaLinkLocalAddress exceeds 111, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.4.1.5.1.1,MOBILEIPV6-MIB::mip6HaGaAddrSeqNo,Integer32,not-accessible,,current,,The index that along with ipv6InterfaceIfIndex, mip6HaLinkLocalAddressType, and mip6HaLinkLocalAddress uniquely identifies this row. 
.1.3.6.1.2.1.133.1.4.1.5.1.2,MOBILEIPV6-MIB::mip6HaGaGlobalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type for the global address of the home agent that follows. 
.1.3.6.1.2.1.133.1.4.1.5.1.3,MOBILEIPV6-MIB::mip6HaGaGlobalAddress,OCTET,read-only,,current,,A global address of the home agent. The type of the address represented by this object is specified by the corresponding mip6HaGaGlobalAddressType object. 
.1.3.6.1.2.1.133.1.4.2,MOBILEIPV6-MIB::mip6HaStats,,,,,,
.1.3.6.1.2.1.133.1.4.2.1,MOBILEIPV6-MIB::mip6HaGlobalStats,,,,,,
.1.3.6.1.2.1.133.1.4.2.1.1,MOBILEIPV6-MIB::mip6HaHomeTestInitsRecd,Counter32,read-only,,current,,Total number of Home Test Init messages received by the home agent. This will include Home Test Init messages that failed the validity checks. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.2,MOBILEIPV6-MIB::mip6HaHomeTestsSent,Counter32,read-only,,current,,Total number of Home Test messages sent by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.3,MOBILEIPV6-MIB::mip6HaBUsRecd,Counter32,read-only,,current,,Total number of Binding Updates received by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.4,MOBILEIPV6-MIB::mip6HaBUAcksSent,Counter32,read-only,,current,,Total number of Binding Acknowledgments sent by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.5,MOBILEIPV6-MIB::mip6HaBRAdviceSent,Counter32,read-only,,current,,Total number of Binding Acknowledgments sent by the home agent with Binding Refresh Advice mobility option included. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.6,MOBILEIPV6-MIB::mip6HaBUsAccepted,Counter32,read-only,,current,,Total number of Binding Updates accepted by this HA. Binding Acknowledgment with status code of 0 or 1. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.7,MOBILEIPV6-MIB::mip6HaPrefDiscoverReqd,Counter32,read-only,,current,,The total number of Binding Acknowledgments sent by the home agent with status code indicating 'accepted but prefix discovery necessary' (Code 1). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.8,MOBILEIPV6-MIB::mip6HaReasonUnspecified,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'reason unspecified' (Code 128). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.9,MOBILEIPV6-MIB::mip6HaAdmProhibited,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'administratively prohibited' (Code 129). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.10,MOBILEIPV6-MIB::mip6HaInsufficientResource,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'insufficient resources' (Code 130). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.11,MOBILEIPV6-MIB::mip6HaHomeRegnNotSupported,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'home registration not supported' (Code 131). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.12,MOBILEIPV6-MIB::mip6HaNotHomeSubnet,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'not home subnet' (Code 132). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.13,MOBILEIPV6-MIB::mip6HaNotHomeAgentForThisMN,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'not home agent for this mobile node' (Code 133). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.14,MOBILEIPV6-MIB::mip6HaDupAddrDetectionFailed,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'Duplicate Address Detection failed' (Code 134). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.15,MOBILEIPV6-MIB::mip6HaSeqNumberOutOfWindow,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'sequence number out of window' (Code 135). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.16,MOBILEIPV6-MIB::mip6HaExpiredHomeNonceIndex,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'expired home nonce index' (Code 136). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.1.17,MOBILEIPV6-MIB::mip6HaRegTypeChangeDisallowed,Counter32,read-only,,current,,Total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgment message indicating 'registration type change disallowed' (Code 139), i.e., a binding already exists for the given home address and the home registration flag has a different value than the Home Registration (H) bit in the Binding Update. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.2,MOBILEIPV6-MIB::mip6HaCounterTable,,not-accessible,,current,,A table containing registration statistics for all mobile nodes registered with the home agent. 
.1.3.6.1.2.1.133.1.4.2.2.1,MOBILEIPV6-MIB::mip6HaCounterEntry,,not-accessible,mip6BindingHomeAddressType:mip6BindingHomeAddress,current,,Home agent registration statistics for a mobile node. Implementors need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.133.1.4.2.2.1.1,MOBILEIPV6-MIB::mip6HaBURequestsAccepted,Counter32,read-only,,current,,Total number of service requests for the mobile node accepted by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6HaCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.2.1.2,MOBILEIPV6-MIB::mip6HaBURequestsDenied,Counter32,read-only,,current,,Total number of service requests for the mobile node rejected by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mip6HaCtrDiscontinuityTime. 
.1.3.6.1.2.1.133.1.4.2.2.1.3,MOBILEIPV6-MIB::mip6HaBCEntryCreationTime,OCTET,read-only,,current,,The time when the current Binding Cache entry was created for the mobile node. 
.1.3.6.1.2.1.133.1.4.2.2.1.4,MOBILEIPV6-MIB::mip6HaBUAcceptedTime,OCTET,read-only,,current,,The time at which the last Binding Update was accepted by the home agent for this mobile node. 
.1.3.6.1.2.1.133.1.4.2.2.1.5,MOBILEIPV6-MIB::mip6HaBURejectionTime,OCTET,read-only,,current,,The time at which the last Binding Update was rejected by the home agent for this mobile node. If there have been no rejections, then this object will be inaccessible. 
.1.3.6.1.2.1.133.1.4.2.2.1.6,MOBILEIPV6-MIB::mip6HaRecentBURejectionCode,INTEGER,read-only,,current,reasonUnspecified(1):admProhibited(2):insufficientResource(3):homeRegistrationNotSupported(4):notHomeSubnet(5):notHomeAgentForThisMobileNode(6):duplicateAddressDetectionFailed(7):sequenceNumberOutOfWindow(8):expiredHomeNonceIndex(9):expiredCareofNonceIndex(10):expiredNonces(11):registrationTypeChangeDisallowed(12),If a Binding Acknowledgment is sent to the mobile node, this is the status code (> 128) that is returned in the Binding Acknowledgment. In case a Binding Acknowledgment is not sent to the mobile node, then this will be the value of the status code that corresponds to the reason of the rejection. If there have been no rejections, then this object will be inaccessible. 
.1.3.6.1.2.1.133.1.4.2.2.1.7,MOBILEIPV6-MIB::mip6HaCtrDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of counters in this row, viz., instances of 'mip6HaBURequestsAccepted' and 'mip6HaBURequestsRejected', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. 
.1.3.6.1.2.1.133.2,MOBILEIPV6-MIB::mip6Conformance,,,,,,
.1.3.6.1.2.1.133.2.1,MOBILEIPV6-MIB::mip6Groups,,,,,,
.1.3.6.1.2.1.133.2.1.1,MOBILEIPV6-MIB::mip6SystemGroup,,,,,, A collection of objects for basic MIPv6 monitoring.
.1.3.6.1.2.1.133.2.1.2,MOBILEIPV6-MIB::mip6BindingCacheGroup,,,,,, A collection of objects for monitoring the Binding Cache. 
.1.3.6.1.2.1.133.2.1.3,MOBILEIPV6-MIB::mip6BindingHstGroup,,,,,, A collection of objects for monitoring the Binding History. This can be used to monitor the movement of the mobile node. 
.1.3.6.1.2.1.133.2.1.4,MOBILEIPV6-MIB::mip6TotalTrafficGroup,,,,,, A collection of objects for monitoring the total MIPv6 traffic. 
.1.3.6.1.2.1.133.2.1.5,MOBILEIPV6-MIB::mip6NodeTrafficGroup,,,,,, A collection of objects for monitoring the MIPv6 traffic due to a mobile node. 
.1.3.6.1.2.1.133.2.1.6,MOBILEIPV6-MIB::mip6MnSystemGroup,,,,,, A collection of objects for basic monitoring of the mobile node. 
.1.3.6.1.2.1.133.2.1.7,MOBILEIPV6-MIB::mip6MnConfGroup,,,,,, A collection of objects for monitoring the advertisement-related info on the mobile node. 
.1.3.6.1.2.1.133.2.1.8,MOBILEIPV6-MIB::mip6MnRegistrationGroup,,,,,, A collection of objects for monitoring the registration statistics for the mobile node. 
.1.3.6.1.2.1.133.2.1.9,MOBILEIPV6-MIB::mip6CnStatsGroup,,,,,, A collection of objects for monitoring the control messages and corresponding statistics for each mobile node communicating with the correspondent node. 
.1.3.6.1.2.1.133.2.1.10,MOBILEIPV6-MIB::mip6HaSystemGroup,,,,,, A collection of objects for monitoring the advertisement-related parameters and statistics for the home agent. 
.1.3.6.1.2.1.133.2.1.11,MOBILEIPV6-MIB::mip6HaListGroup,,,,,, A collection of objects for monitoring the Home Agent List on the home agent. 
.1.3.6.1.2.1.133.2.1.12,MOBILEIPV6-MIB::mip6HaStatsGroup,,,,,, A collection of objects for monitoring registration-related statistics on the home agent. 
.1.3.6.1.2.1.133.2.1.13,MOBILEIPV6-MIB::mip6CnGlobalStatsGroup,,,,,, A collection of objects for monitoring advertisement and registration statistics on a correspondent node. 
.1.3.6.1.2.1.133.2.1.14,MOBILEIPV6-MIB::mip6HaGlobalStatsGroup,,,,,, A collection of objects for monitoring advertisement and registration statistics on a home agent. 
.1.3.6.1.2.1.133.2.1.15,MOBILEIPV6-MIB::mip6BindingCacheCtlGroup,,,,,,A collection of objects for controlling the Binding Cache. 
.1.3.6.1.2.1.133.2.1.16,MOBILEIPV6-MIB::mip6NotificationGroup,,,,,,A collection of notifications from a home agent or correspondent node to the Manager about the status of a mobile node. 
.1.3.6.1.2.1.133.2.2,MOBILEIPV6-MIB::mip6Compliances,,,,,,
.1.3.6.1.2.1.133.2.2.1,MOBILEIPV6-MIB::mip6CoreCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB. 
.1.3.6.1.2.1.133.2.2.2,MOBILEIPV6-MIB::mip6Compliance2,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the Binding Cache and the Total Traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.3,MOBILEIPV6-MIB::mip6Compliance3,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the Binding Cache, the Binding History, the total traffic, and the mobile node-wide traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHstHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- -- OBJECT mip6BindingHstHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- 
.1.3.6.1.2.1.133.2.2.4,MOBILEIPV6-MIB::mip6CoreReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode). 
.1.3.6.1.2.1.133.2.2.5,MOBILEIPV6-MIB::mip6ReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the Binding Cache and Total Traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.6,MOBILEIPV6-MIB::mip6ReadOnlyCompliance3,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the Binding Cache, the Binding History, the total traffic, and the mobile node-wide traffic. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHstHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- -- OBJECT mip6BindingHstHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the -- mip6BindingHstHomeAddress object. -- 
.1.3.6.1.2.1.133.2.2.7,MOBILEIPV6-MIB::mip6MnCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic mobile node functionality. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.8,MOBILEIPV6-MIB::mip6MnCompliance2,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the mobile node functionality specifically the Discovery- and Registration-related statistics, There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6MnBLNodeAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.9,MOBILEIPV6-MIB::mip6CnCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic correspondent node functionality. 
.1.3.6.1.2.1.133.2.2.10,MOBILEIPV6-MIB::mip6CnCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic correspondent node functionality. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. 
.1.3.6.1.2.1.133.2.2.11,MOBILEIPV6-MIB::mip6HaCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the basic home agent functionality. 
.1.3.6.1.2.1.133.2.2.12,MOBILEIPV6-MIB::mip6HaCompliance2,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.13,MOBILEIPV6-MIB::mip6HaCompliance3,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring and control of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.14,MOBILEIPV6-MIB::mip6HaCoreReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the basic home agent functionality. 
.1.3.6.1.2.1.133.2.2.15,MOBILEIPV6-MIB::mip6HaReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.16,MOBILEIPV6-MIB::mip6HaReadOnlyCompliance3,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring and control of the home agent functionality specifically the Home Agent List and the home-agent-registration-related statistics, There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6HaLinkLocalAddressType -- SYNTAX InetAddressType { ipv6z(4) } -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- -- OBJECT mip6HaLinkLocalAddress -- SYNTAX InetAddress (SIZE(20)) -- DESCRIPTION -- This MIB module requires support for local -- ipv6 addresses for the mip6HaLinkLocalAddress -- object. -- 
.1.3.6.1.2.1.133.2.2.17,MOBILEIPV6-MIB::mip6NotificationCompliance,,,,,,The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support Notification from home agent or correspondent node to management stations about the mobile node status. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the mip6BindingHomeAddress -- object. 
.1.3.6.1.2.1.134,RSTP-MIB::rstpMIB,,,,,,The Bridge MIB Extension module for managing devices that support the Rapid Spanning Tree Protocol defined by IEEE 802.1w. Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4318; See the RFC itself for full legal notices.
.1.3.6.1.2.1.134.0,RSTP-MIB::rstpNotifications,,,,,,
.1.3.6.1.2.1.134.1,RSTP-MIB::rstpObjects,,,,,,
.1.3.6.1.2.1.134.2,RSTP-MIB::rstpConformance,,,,,,
.1.3.6.1.2.1.134.2.1,RSTP-MIB::rstpGroups,,,,,,
.1.3.6.1.2.1.134.2.1.1,RSTP-MIB::rstpBridgeGroup,,,,,,Rapid Spanning Tree information for the bridge.
.1.3.6.1.2.1.134.2.1.2,RSTP-MIB::rstpPortGroup,,,,,,Rapid Spanning Tree information for individual ports.
.1.3.6.1.2.1.134.2.2,RSTP-MIB::rstpCompliances,,,,,,
.1.3.6.1.2.1.134.2.2.1,RSTP-MIB::rstpCompliance,,,,,,The compliance statement for device support of Rapid Spanning Tree Protocol (RSTP) bridging services.
.1.3.6.1.2.1.135,T11-FC-NAME-SERVER-MIB::t11FcNameServerMIB,,,,,,The MIB module for the management of the functionality, which realizes the FC-GS-4 requirements for Name Server (NS). Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4438; see the RFC itself for full legal notices.
.1.3.6.1.2.1.135.0,T11-FC-NAME-SERVER-MIB::t11NsNotifications,,,,,,
.1.3.6.1.2.1.135.0.1,T11-FC-NAME-SERVER-MIB::t11NsRejectRegNotify,,,,,,This notification is generated whenever a request to register information in a Name Server Information Subset (for which the corresponding instance of t11NsInfoSubsetRejReqNotfyEnable is 'true') is rejected on a particular Fabric for a particular Nx_Port. The value of t11FamLocalSwitchWwn indicates the WWN of the switch that received the request. (If the WWN is unavailable, the value is set to the zero-length string.) The value of t11NsRejectCtCommandString indicates the rejected request, and the values of t11NsRejectReasonCode, t11NsRejReasonCodeExp, and t11NsRejReasonVendorCode indicate the reason for the rejection. The value of t11NsRegPortName represents the Port Name if it is able to be extracted out of the Registration Request, or otherwise the value as currently registered on the port.
.1.3.6.1.2.1.135.1,T11-FC-NAME-SERVER-MIB::t11NsMIBObjects,,,,,,
.1.3.6.1.2.1.135.1.1,T11-FC-NAME-SERVER-MIB::t11NsStatus,,,,,,
.1.3.6.1.2.1.135.1.1.1,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetTable,,not-accessible,,current,,This table contains one entry for each Name Server Information Subset within each Fibre Channel management instance.
.1.3.6.1.2.1.135.1.1.1.1,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetEntry,,not-accessible,fcmInstanceIndex:t11NsInfoSubsetIndex,current,,This entry contains information about operations on a particular Name Server Information Subset within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.135.1.1.1.1.1,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetIndex,Unsigned32,not-accessible,,current,,An arbitrary integer value that uniquely identifies this Name Server Information Subset amongst all others within the same Fibre Channel management instance. It is mandatory to keep this value constant between restarts of the agent and to make every possible effort to keep it constant across such restarts.
.1.3.6.1.2.1.135.1.1.1.1.2,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetSwitchIndex,Unsigned32,read-only,,current,,The value of this object is zero when operations upon this Name Server Information Subset do not occur at a local Fibre Channel switch; otherwise, it is non-zero and identifies the local switch. The switch identified by a non-zero value of this object is the same switch as is identified by the same value of fcmSwitchIndex.
.1.3.6.1.2.1.135.1.1.1.1.3,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last update to any entry in the t11NsRegTable with the same values of fcmInstanceIndex and t11NsInfoSubsetIndex. This includes creation of an entry, deletion of an entry, or modification of an existing entry. If no such update has taken place since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.135.1.1.1.1.4,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetNumRows,Integer32,read-only,,current,,The number of Nx_Ports currently registered in this Name Server Information Subset, i.e., the number of rows in the t11NsRegTable with the same values of fcmInstanceIndex and t11NsInfoSubsetIndex.
.1.3.6.1.2.1.135.1.1.1.1.5,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetTotalRejects,Counter32,read-only,,current,,The total number of (CT_IU) Requests for Name Server functions that were rejected for inclusion in this Name Server Information Subset, across all Fabrics for which it contains information. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.1.1.1.6,T11-FC-NAME-SERVER-MIB::t11NsInfoSubsetRejReqNotfyEnable,INTEGER,read-write,,current,true(1):false(2),This object indicates whether 't11NsRejectRegNotify' notifications are generated by rejections of requests to register information in this Name Server Information Subset. If value of this object is 'true', then the notification is generated when a request is rejected. If it is 'false', the notification is not generated. The persistence of values of this object across an agent reboot is implementation-dependent.
.1.3.6.1.2.1.135.1.1.2,T11-FC-NAME-SERVER-MIB::t11NsRegTable,,not-accessible,,current,,This table contains entries for all Nx_Ports registered in the identified Name Server Information Subsets across all Fabrics for which such subsets contain information.
.1.3.6.1.2.1.135.1.1.2.1,T11-FC-NAME-SERVER-MIB::t11NsRegEntry,,not-accessible,fcmInstanceIndex:t11NsInfoSubsetIndex:t11NsRegFabricIndex:t11NsRegPortIdentifier,current,,An entry containing information about an Nx_Port represented by t11NsRegPortIdentifier that is registered with a Name Server Information Subset (identified by t11NsInfoSubsetIndex) within the Fibre Channel management instance (identified by fcmInstanceIndex) on the Fabric (identified by t11NsRegFabricIndex).
.1.3.6.1.2.1.135.1.1.2.1.1,T11-FC-NAME-SERVER-MIB::t11NsRegFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric. In a Fabric conformant to SW-3, only a single Fabric can operate within a single physical infrastructure, and thus, the value of this Fabric Index will always be 1. However, it is possible that future standards will define how multiple Fabrics, each with its own management instrumentation, could operate within one (or more) physical infrastructures. To allow for this future possibility, this index value is used to uniquely identify a particular Fabric within a physical infrastructure.
.1.3.6.1.2.1.135.1.1.2.1.2,T11-FC-NAME-SERVER-MIB::t11NsRegPortIdentifier,OCTET,not-accessible,,current,,The Fibre Channel Address Identifier of this Nx_Port. If no Port Identifier has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.3,T11-FC-NAME-SERVER-MIB::t11NsRegPortName,OCTET,read-only,,current,,The Port_Name (WWN) of this Nx_Port. If this object has not been registered, then its value is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.4,T11-FC-NAME-SERVER-MIB::t11NsRegNodeName,OCTET,read-only,,current,,The Node_Name (WWN) of this Nx_Port. If this object has not been registered, then its value is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.5,T11-FC-NAME-SERVER-MIB::t11NsRegClassOfSvc,BITS,read-only,,current,classF(0):class1(1):class2(2):class3(3):class4(4):class5(5):class6(6),The class of service indicator. This object is an array of bits that contain a bit map of the classes of service supported by the associated port. If a bit in this object is 1, it indicates that the class of service is supported by the associated port. When a bit is set to 0, it indicates that no class of service is supported by this Nx_Port. If this object has not been not registered for a port, then the instance for that port is not instantiated.
.1.3.6.1.2.1.135.1.1.2.1.6,T11-FC-NAME-SERVER-MIB::t11NsRegNodeIpAddress,OCTET,read-only,,current,,The IP address of the node of this Nx_Port, in network-byte order, either as a 32-bit IPv4 address or a 128-bit IPv6 address. For the former, the leftmost 96 bits (12 bytes) should contain x'00 00 00 00 00 00 00 00 00 00 FF FF', and the IPv4 address should be present in the rightmost 32 bits. Note that the value of this object is the IP address value that is received in the FC-GS-4 message Register IP address (Node) RIP_NN. It is not validated against any IP address format. If no 'IP address (Node)' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.7,T11-FC-NAME-SERVER-MIB::t11NsRegProcAssoc,OCTET,read-only,,current,,The Fibre Channel Initial Process Associator (IPA). If no 'Initial Process Associator' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.8,T11-FC-NAME-SERVER-MIB::t11NsRegFc4Type,OCTET,read-only,,current,,The FC-4 protocol types supported by this Nx_Port. This is an array of 256 bits. Each bit in the array corresponds to a Type value as defined by Fibre Channel standards and contained in the Type field of the frame header. The order of the bits in the 256-bit (32-byte) value is the same as defined in FC-GS-4, section 5.2.3.8, and represented in network-byte order. If no 'FC-4 TYPEs' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.9,T11-FC-NAME-SERVER-MIB::t11NsRegPortType,Unsigned32,read-only,,current,,The port type of this port. If no 'Port Type' has been registered, then the value of this object is unidentified and is represented by the value 'unknown'.
.1.3.6.1.2.1.135.1.1.2.1.10,T11-FC-NAME-SERVER-MIB::t11NsRegPortIpAddress,OCTET,read-only,,current,,The value that Fibre Channel calls an 'IP Address (Port)' that represents the IP address of the associated port. The value is either in 32-bit IPv4 format or 128-bit IPv6 format, in network-byte order. When this object contains an IPv4 address, the leftmost 96 bits (12 bytes) should contain x'00 00 00 00 00 00 00 00 00 00 FF FF'. The IPv4 address should be present in the rightmost 32 bits. Note that the value of this object is the IP address value that is received in the FC-GS-4 message Register IP address (Port) RIPP_ID. It is not validated against any IP address format. If no 'IP address (Port)' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.11,T11-FC-NAME-SERVER-MIB::t11NsRegFabricPortName,OCTET,read-only,,current,,The Fabric Port Name (WWN) of the Fx_Port to which this Nx_Port is attached. If no 'Fabric Port Name' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.12,T11-FC-NAME-SERVER-MIB::t11NsRegHardAddress,OCTET,read-only,,current,,The format of this object is identical to the format of Hard Address defined in the Discover Address (ADISC) Extended Link Service (FC-FS). Hard Address is the 24-bit NL_Port identifier that consists of: - the 8-bit Domain_ID in the most significant byte - the 8-bit Area_ID in the next most significant byte - the 8-bit AL-PA (Arbitrated Loop Physical Address) which an NL_Port attempts acquire during FC-AL initialization in the least significant byte. If the port is not an NL_Port, or if it is an NL_Port but does not have a hard address, then all bits are reported as zeros. If no 'Hard Address' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.13,T11-FC-NAME-SERVER-MIB::t11NsRegSymbolicPortName,OCTET,read-only,,current,,The user-defined name of this port. If no 'Symbolic Port Name' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.14,T11-FC-NAME-SERVER-MIB::t11NsRegSymbolicNodeName,OCTET,read-only,,current,,The user-defined name of the node of this port. If no 'Symbolic Node Name' has been registered, then the value of this object is the zero-length string.
.1.3.6.1.2.1.135.1.1.2.1.15,T11-FC-NAME-SERVER-MIB::t11NsRegFc4Features,OCTET,read-only,,current,,The FC-4 Features associated with FC-4 Types on this port encoded as a 128-byte value in network-byte order, or the zero-length string if no 'FC-4 Features' have been registered. Section 5.2.3.15 of FC-GS-4 is the authoritative definition of the format of the 128-byte value, i.e., if different, FC-GS-4 takes precedence over the following description: The 128-byte value is an array of 4-bit values, one for each FC-4 Type value, positioned as follows: the 5 most significant bits of a Type value identify where it appears within the 128-byte value, specifically, within which word: - Word 0 (of the 128-byte value) contains information related to Types '00' through '07'; - Word 1 contains information related to Types '08' through 0F'; - and so forth, up to Word 31, which contains information related to Types 'F8' through 'FF'. The least significant of the eight 4-bit values in each Word represents an FC-4 Type with 000 as its 3 least significant bits, and most significant 4-bit value in each Word represents an FC-4 Type with 111 as its 3 least significant bits.
.1.3.6.1.2.1.135.1.1.3,T11-FC-NAME-SERVER-MIB::t11NsRegFc4DescriptorTable,,not-accessible,,current,,This table contains entries for all FC-4 Descriptors registered in the identified Name Server Information Subsets across all Fabrics for which such subsets contain information.
.1.3.6.1.2.1.135.1.1.3.1,T11-FC-NAME-SERVER-MIB::t11NsRegFc4DescriptorEntry,,not-accessible,fcmInstanceIndex:t11NsInfoSubsetIndex:t11NsRegFabricIndex:t11NsRegPortIdentifier:t11NsRegFc4TypeValue,current,,An entry in the t11NsRegFc4DescriptorTable, containing information about an FC-4 Descriptor that is associated with a particular FC-4 Type value. The particular FC-4 Descriptor was registered by an Nx_Port (identified by t11NsRegPortIdentifier) in a Name Server Information Subset (identified by t11NsInfoSubsetIndex) within the Fibre Channel management instance (identified by fcmInstanceIndex) on the Fabric (identified by t11NsRegFabricIndex). If no FC-4 Descriptors have been registered for a particular port, then there will be no entries in this table for that port.
.1.3.6.1.2.1.135.1.1.3.1.1,T11-FC-NAME-SERVER-MIB::t11NsRegFc4TypeValue,Unsigned32,not-accessible,,current,,An integer value that identifies an FC-4 Type value (representing a particular protocol type, as specified in FC-FS) for which an FC-4 Descriptor has been registered. An instance of this object contains a 'Type value' that corresponds to a '1' bit in the value of the t11NsRegFc4Type registered for the same port; this correspondence is as specified in FC-GS-4.
.1.3.6.1.2.1.135.1.1.3.1.2,T11-FC-NAME-SERVER-MIB::t11NsRegFc4Descriptor,OCTET,read-only,,current,,The FC-4 Descriptor value that has been registered for the particular port on the particular Fabric, and for the FC-4 Type represented by the corresponding value of t11NsRegFc4TypeIndex. The format of an FC-4 Descriptor is dependent on the corresponding FC-4 Type value, but is represented in network-byte order.
.1.3.6.1.2.1.135.1.1.4,T11-FC-NAME-SERVER-MIB::t11NsRejectTable,,not-accessible,,current,,This table contains information about the most recent Name Server Registration Request failures for various ports on various Fabrics. If no information is available about the most recent rejection of a Registration Request on a particular port on a particular Fabric, then there will no entry in this table for that port and Fabric. When a t11NsRejectRegNotify notification is sent for such a Registration Request failure, the values of the objects in the relevant entry of this table are updated immediately prior to generating the notification.
.1.3.6.1.2.1.135.1.1.4.1,T11-FC-NAME-SERVER-MIB::t11NsRejectEntry,,not-accessible,fcmInstanceIndex:t11NsInfoSubsetIndex:t11NsRegFabricIndex:t11NsRegPortIdentifier,current,,An entry containing information about the most recent rejection of a request to register information in the Name Server Information Subset (identified by t11NsInfoSubsetIndex) within the Fibre Channel management instance (identified by fcmInstanceIndex) for a particular port (identified by t11NsRegPortIdentifier) on a particular Fabric (identified by t11NsRegFabricIndex).
.1.3.6.1.2.1.135.1.1.4.1.1,T11-FC-NAME-SERVER-MIB::t11NsRejectCtCommandString,OCTET,read-only,,current,,The binary content of the Registration Request, formatted as an octet string (in network byte order) containing the CT_IU, as described in Table 2 of [FC-GS-4] (including the preamble), which was most recently rejected for the particular Name Server Information Subset on the particular port on the particular Fabric. This object contains the zero-length string if and when the CT-IU's content is unavailable. When the length of this object is 255 octets, it contains the first 255 octets of the CT-IU (in network-byte order).
.1.3.6.1.2.1.135.1.1.4.1.2,T11-FC-NAME-SERVER-MIB::t11NsRejectReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),A registration reject reason code. This object contains the reason code of the most recent Name Server Registration Request failure for the particular port on the particular Fabric.
.1.3.6.1.2.1.135.1.1.4.1.3,T11-FC-NAME-SERVER-MIB::t11NsRejReasonCodeExp,INTEGER,read-only,,current,noAdditionalExplanation(1):portIdentifierNotRegistered(2):portNameNotRegistered(3):nodeNameNotRegistered(4):classOfServiceNotRegistered(5):nodeIpAddressNotRegistered(6):ipaNotRegistered(7):fc4TypeNotRegistered(8):symbolicPortNameNotRegistered(9):symbolicNodeNameNotRegistered(10):portTypeNotRegistered(11):portIpAddressNotRegistered(12):fabricPortNameNotRegistered(13):hardAddressNotRegistered(14):fc4DescriptorNotRegistered(15):fc4FeaturesNotRegistered(16):accessDenied(17):unacceptablePortIdentifier(18):databaseEmpty(19):noObjectRegInSpecifiedScope(20):domainIdNotPresent(21):portIdNotPresent(22):noDeviceAttached(23):authorizationException(24):authenticationException(25):databaseFull(26),A registration reject reason code explanation. This object contains the reason code explanation of the most recent Name Server Registration Request failure for the particular port on the particular Fabric.
.1.3.6.1.2.1.135.1.1.4.1.4,T11-FC-NAME-SERVER-MIB::t11NsRejReasonVendorCode,OCTET,read-only,,current,,A registration reject vendor-specific code. This object contains the vendor-specific code of the most recent Name Server Registration Request failure for the particular port on the particular Fabric.
.1.3.6.1.2.1.135.1.2,T11-FC-NAME-SERVER-MIB::t11NsStatistics,,,,,,
.1.3.6.1.2.1.135.1.2.1,T11-FC-NAME-SERVER-MIB::t11NsStatsTable,,not-accessible,,current,,This table contains per-Fabric state and statistics for operations upon the identified Name Server Information Subsets.
.1.3.6.1.2.1.135.1.2.1.1,T11-FC-NAME-SERVER-MIB::t11NsStatsEntry,,not-accessible,fcmInstanceIndex:t11NsInfoSubsetIndex:t11NsRegFabricIndex,current,,An entry in this table contains state and statistics for operations upon a Name Server Information Subset (identified by t11NsInfoSubsetIndex) within the Fibre Channel management instance (identified by fcmInstanceIndex) on the Fabric (identified by t11NsRegFabricIndex).
.1.3.6.1.2.1.135.1.2.1.1.1,T11-FC-NAME-SERVER-MIB::t11NsInGetReqs,Counter32,read-only,,current,,The total number of (CT_IU) Get Requests received requesting information from this Name Server Information Subset on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.2,T11-FC-NAME-SERVER-MIB::t11NsOutGetReqs,Counter32,read-only,,current,,The total number of (CT_IU) Get Requests sent in order to obtain information needed in this Name Server Information Subset on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.3,T11-FC-NAME-SERVER-MIB::t11NsInRegReqs,Counter32,read-only,,current,,The total number of (CT_IU) Registration Requests received to register information in the Name Server Information Subset on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.4,T11-FC-NAME-SERVER-MIB::t11NsInDeRegReqs,Counter32,read-only,,current,,The total number of (CT_IU) De-registration Requests received to de-register information from this Name Server Information Subset on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.5,T11-FC-NAME-SERVER-MIB::t11NsInRscns,Counter32,read-only,,current,,The total number of received RSCNs, indicating Name Server-related changes relating to this Name Server Information Subset on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.6,T11-FC-NAME-SERVER-MIB::t11NsOutRscns,Counter32,read-only,,current,,The total number of transmitted RSCNs, indicating Name Server-related changes relating to this Name Server Information Subset on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.7,T11-FC-NAME-SERVER-MIB::t11NsRejects,Counter32,read-only,,current,,The total number of CT_IU Requests for Name Server functions on this Name Server Information Subset on this Fabric that were rejected. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.135.1.2.1.1.8,T11-FC-NAME-SERVER-MIB::t11NsDatabaseFull,INTEGER,read-only,,current,true(1):false(2),An indication of whether the database containing this Name Server Information Subset is full. This object is set to 'true' only if the Name Server is unable to allocate space for a new entry for the corresponding Fabric, and it is set to 'false' whenever an existing entry is deleted for the corresponding Fabric.
.1.3.6.1.2.1.135.2,T11-FC-NAME-SERVER-MIB::t11NsMIBConformance,,,,,,
.1.3.6.1.2.1.135.2.1,T11-FC-NAME-SERVER-MIB::t11NsMIBCompliances,,,,,,
.1.3.6.1.2.1.135.2.1.1,T11-FC-NAME-SERVER-MIB::t11NsMIBCompliance,,,,,,The compliance statement for entities that implement the Fibre Channel Name Server.
.1.3.6.1.2.1.135.2.2,T11-FC-NAME-SERVER-MIB::t11NsMIBGroups,,,,,,
.1.3.6.1.2.1.135.2.2.1,T11-FC-NAME-SERVER-MIB::t11NsDBGroup,,,,,,A collection of objects for monitoring the information registered in a Name Server Information Subset.
.1.3.6.1.2.1.135.2.2.2,T11-FC-NAME-SERVER-MIB::t11NsRequestStatsGroup,,,,,,A collection of objects for displaying Name Server statistics and state for Name Server requests.
.1.3.6.1.2.1.135.2.2.3,T11-FC-NAME-SERVER-MIB::t11NsRscnStatsGroup,,,,,,A collection of objects for displaying Name Server statistics for Name Server-related RSCNs.
.1.3.6.1.2.1.135.2.2.4,T11-FC-NAME-SERVER-MIB::t11NsRejectStatsGroup,,,,,,A collection of objects for displaying Name Server statistics for rejects.
.1.3.6.1.2.1.135.2.2.5,T11-FC-NAME-SERVER-MIB::t11NsNotifyControlGroup,,,,,,A collection of notification control and notification information objects for monitoring rejections of Name Server registrations.
.1.3.6.1.2.1.135.2.2.6,T11-FC-NAME-SERVER-MIB::t11NsNotifyGroup,,,,,,A collection of notifications for monitoring rejections of Name Server registrations.
.1.3.6.1.2.1.136,T11-TC-MIB::t11TcMIB,,,,,,This module defines textual conventions used in T11 MIBs. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4439; see the RFC itself for full legal notices.
.1.3.6.1.2.1.137,T11-FC-FABRIC-ADDR-MGR-MIB::t11FcFabricAddrMgrMIB,,,,,,The MIB module for the Fabric Address management functionality defined by the Fibre Channel standards. For the purposes of this MIB, Fabric Address Manager refers to the functionality of acquiring DomainID(s) as specified in FC-SW-3, and managing Fibre Channel Identifiers as specified in FC-FS. An instance of 'Fabric Address Manager' software functionality executes in the Principal Switch, and in each other switch. After an agent reboot, the values of read-write objects defined in this MIB module are implementation-dependent. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4439; see the RFC itself for full legal notices.
.1.3.6.1.2.1.137.0,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamNotifications,,,,,,
.1.3.6.1.2.1.137.0.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDomainIdNotAssignedNotify,,,,,,This notification indicates that a Domain_ID has not been configured or assigned for a particular Fabric, identified by t11FamNotifyFabricIndex, on a particular switch identified by t11FamLocalSwitchWwn. This could happen under the following conditions, and results in the switch isolating E_Ports on the Fabric: - if the switch's request for a configured static Domain_ID is rejected or no other Domain_ID is assigned, then the E_Ports are isolated.
.1.3.6.1.2.1.137.0.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamNewPrincipalSwitchNotify,,,,,,This notification indicates that a particular switch, identified by t11FamLocalSwitchWwn, has become the new Principal Switch on the Fabric identified by t11FamNotifyFabricIndex. This notification is sent soon after its election as the new Principal Switch, i.e., upon expiration of a Principal Switch selection timer that is equal to twice the Fabric Stability Timeout value (F_S_TOV).
.1.3.6.1.2.1.137.0.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFabricChangeNotify,,,,,,This notification is sent whenever a particular switch, identified by t11FamLocalSwitchWwn, sends or receives a Build Fabric (BF) or a ReConfigure Fabric (RCF) message on the Fabric identified by t11FamNotifyFabricIndex. This notification is not sent if a 't11FamNewPrincipalSwitchNotify' notification is sent for the same event.
.1.3.6.1.2.1.137.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamMIBObjects,,,,,,
.1.3.6.1.2.1.137.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamConfiguration,,,,,,
.1.3.6.1.2.1.137.1.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamTable,,not-accessible,,current,,This table contains Fabric Address Manager related parameters that are able to be configured and monitored in a Fibre Channel switch. For each of the switches (identified by fcmSwitchIndex) managed by a Fibre Channel management instance (identified by fcmInstanceIndex), there is any entry for each Fabric known to that switch. Entries are implicitly created/removed if and when additional Fabrics are created/deleted.
.1.3.6.1.2.1.137.1.1.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FamFabricIndex,current,,An entry provides information on the local Fabric Address Manager functionality for a Fabric known to a particular switch.
.1.3.6.1.2.1.137.1.1.1.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric known to a particular switch. In a Fabric conformant to FC-SW-3, only a single Fabric can operate within a physical infrastructure, and thus, the value of this Fabric Index will always be 1. However, the current standard, FC-SW-4, defines how multiple Fabrics, each with its own management instrumentation, could operate within one (or more) physical infrastructures. When such multiple Fabrics are in use, this index value is used to uniquely identify a particular Fabric within a physical infrastructure.
.1.3.6.1.2.1.137.1.1.1.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamConfigDomainId,Integer32,read-write,,current,,The configured Domain_ID of the particular switch on this Fabric, or zero if no Domain_ID has been configured. The meaning of this object depends on t11FamConfigDomainIdType object. If t11FamConfigDomainIdType is 'preferred', then the configured Domain_ID is called the 'preferred Domain_ID'. Valid values are between 0 and 239. In a situation where this Domain_ID cannot be assigned, any other Domain_ID will be acceptable. A value of zero means any Domain_ID. If t11FamConfigDomainIdType is 'insistent', then the configured Domain_ID is called the 'insistent Domain_ID' and valid values are between 1 and 239. In a situation where this Domain_ID cannot be assigned, no other Domain_ID is acceptable. In both of the above cases, the switch sends an RDI (Request Domain_ID) to request this Domain_ID to the Principal Switch. If no Domain_ID is able to be granted in the case of 'preferred', or if an 'insistent' Domain_ID is configured but not able to be granted, then it is an error condition. When this error occurs, the switch will continue as if it receives a SW_RJT with a reason/explanation of 'Unable to perform command request'/'Domain_ID not available'. That is, its E_Ports on that Fabric will be isolated and the administrator informed via a 't11FamDomainIdNotAssigned' notification. If t11FamConfigDomainIdType is 'static', then the configured Domain_ID is called the 'static Domain_ID' and valid values are between 1 and 239. In this situation, there is no Principal Switch in the Fabric and the Domain_ID is simply assigned by configuration, together with the Fabric_Name. A switch configured with a static Domain_ID, on receiving an EFP, BF, RCF, DIA, or RDI SW_ILS, shall reply with an SW_RJT having Reason Code Explanation 'E_Port is Isolated' and shall isolate the receiving E_Port. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamConfigDomainIdType,INTEGER,read-write,,current,preferred(1):insistent(2):static(3),Type of configured Domain_ID contained in t11FamConfigDomainId. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.4,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAutoReconfigure,INTEGER,read-write,,current,true(1):false(2),This object determines how a particular switch responds to certain error conditions. The condition that might cause these errors is the merging of two disjoint Fabrics that have overlapping Domain_ID lists. If value of this object is 'true', the switch will send an RCF (ReConfigureFabric) to rebuild the Fabric. If 'false', the switch will isolate the E_Ports on which the errors happened. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.5,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamContiguousAllocation,INTEGER,read-write,,current,true(1):false(2),Determines how a particular switch behaves when elected as the Principal Switch. If true, the switch will only accept RDIs with a contiguous allocation; specifically, it will reject RDIs with non-contiguous Domain_IDs, and if an RDI for a contiguous Domain_ID is not able to be fulfilled, it will try to replace all the Domain_IDs in the list with contiguous Domain_IDs, and if that fails, the RDI will be rejected. If false, then the switch acts normally in granting the Domain_IDs even if they are not contiguous. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.6,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamPriority,Unsigned32,read-write,,current,,The initial or configured priority of a particular switch to be used in Principal Switch selection process. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.7,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamPrincipalSwitchWwn,OCTET,read-only,,current,,The WWN of the Principal Switch on this Fabric, or zero-length string if the identity of the principal switch is unknown.
.1.3.6.1.2.1.137.1.1.1.1.8,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamLocalSwitchWwn,OCTET,read-only,,current,,The WWN of the particular switch on this Fabric.
.1.3.6.1.2.1.137.1.1.1.1.9,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAssignedAreaIdList,OCTET,read-only,,current,,The list of (zero or more) Area_IDs that have been assigned by a particular switch in this Fabric, formatted as an array of octets in ascending order. Each octet represents one Area_ID. So, the list containing Area_IDs 23, 45, 235, and 56 would be formatted as the 4-octet string x'172d38eb'. A particular area's Area_ID is used as the index into the t11FamAreaTable to get the statistics on that area.
.1.3.6.1.2.1.137.1.1.1.1.10,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamGrantedFcIds,Counter32,read-only,,current,,The total number of Fibre Channel Address Identifiers granted (for local use, i.e., with a particular switch's Domain_ID) by the Fabric Address Manager on that switch. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.137.1.1.1.1.11,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamRecoveredFcIds,Counter32,read-only,,current,,The total number of Fibre Channel Address Identifiers that have been recovered by the Fabric Address Manager on a particular switch since the switch has been initialized. A recovered Fibre Channel Address Identifier is one that is explicitly returned after previously being used. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.137.1.1.1.1.12,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFreeFcIds,Gauge32,read-only,,current,,The number of Fibre Channel Address Identifiers that are currently unassigned on this Fabric and could be available for assignment either immediately or at some later time. The sum of the instances of FreeFcIds and AssignedFcIds corresponding to a particular Fabric is the total number of Fibre Channel Address Identifiers that the local Fabric Address Management is capable of assigning on that Fabric.
.1.3.6.1.2.1.137.1.1.1.1.13,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAssignedFcIds,Gauge32,read-only,,current,,The number of Fibre Channel Address Identifiers that are currently assigned on this Fabric. The sum of the instances of FreeFcIds and AssignedFcIds corresponding to a particular Fabric is the total number of Fibre Channel Address Identifiers that the local Fabric Address Management is capable of assigning on that Fabric.
.1.3.6.1.2.1.137.1.1.1.1.14,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAvailableFcIds,Gauge32,read-only,,current,,The number of Fibre Channel Address Identifiers that are unassigned and currently available for immediate assignment on the Fabric, e.g., with the 'Clean Address' bit set to 1.
.1.3.6.1.2.1.137.1.1.1.1.15,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamRunningPriority,Unsigned32,read-only,,current,,The running priority of a particular switch on this Fabric. This value is initialized to the value of t11FamPriority, and subsequently altered as specified by the procedures defined in FC-SW-3.
.1.3.6.1.2.1.137.1.1.1.1.16,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamPrincSwRunningPriority,Unsigned32,read-only,,current,,The running priority of the Principal Switch on this Fabric.
.1.3.6.1.2.1.137.1.1.1.1.17,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamState,INTEGER,read-only,,current,other(1):starting(2):unconfigured(3):principalSwitchSelection(4):domainIdDistribution(5):buildFabricPhase(6):reconfigureFabricPhase(7):stable(8):stableWithNoEports(9):noDomains(10):disabled(11):unknown(12),The state of the Fabric Address Manager on a particular switch on this Fabric.
.1.3.6.1.2.1.137.1.1.1.1.18,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamLocalPrincipalSwitchSlctns,Counter32,read-only,,current,,The number of times a particular switch became the Principal Switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.137.1.1.1.1.19,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamPrincipalSwitchSelections,Counter32,read-only,,current,,The number of Principal Switch selections on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.137.1.1.1.1.20,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamBuildFabrics,Counter32,read-only,,current,,The number of non-disruptive fabric reconfigurations (BFs) that have occurred on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.137.1.1.1.1.21,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFabricReconfigures,Counter32,read-only,,current,,The number of disruptive fabric reconfigurations (RCFs) that have occurred on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.137.1.1.1.1.22,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDomainId,Integer32,read-only,,current,,The Domain_ID of a particular switch on this Fabric or zero if no Domain_ID has been assigned.
.1.3.6.1.2.1.137.1.1.1.1.23,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamSticky,INTEGER,read-only,,current,true(1):false(2),An indication of whether a particular switch is supporting the concept of Preferred Domain_IDs via a best-effort attempt to re-assign the same Fibre Channel Address Identifier value to a port on the next occasion when a port requests an assignment on this Fabric. If the value of this object is 'true', then the switch is maintaining rows in the t11FamFcIdCacheTable for this Fabric.
.1.3.6.1.2.1.137.1.1.1.1.24,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamRestart,INTEGER,read-write,,current,nonDisruptive(1):disruptive(2):noOp(3),This object tells the Fabric Address Manager to request a Fabric reconfiguration. If this object is set to 'disruptive', then an RCF (ReConfigure Fabric) is generated in the Fabric in order for the Fabric to recover from the errors. If this object is set to 'nonDisruptive', then a BF (Build Fabric) is generated in the Fabric. No action is taken if this object is set to 'noOp'. The value of the object when read is always 'noOp'. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.25,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamRcFabricNotifyEnable,INTEGER,read-write,,current,true(1):false(2),An indication of whether or not a particular switch should issue a t11FamFabricChangeNotify notification on sending or receiving ReConfigureFabric (RCF) on a Fabric. If the value of the object is 'true', then the notification is generated. If the value is 'false', notification is not generated. If an implementation requires all Fabrics to have the same value, then setting one instance of this object to a new object will result in all corresponding instances being set to that same new value. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.26,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamEnable,INTEGER,read-write,,current,true(1):false(2),Enables the Fabric Address Manager on this switch on this Fabric. If enabled on a Fabric, the switch will participate in Principal Switch selection, and Domain_IDs are assigned dynamically. If disabled, the switch will not participate in Principal Switch selection, and Domain_IDs are assigned statically. Thus, the corresponding value of t11FamConfigDomainIdType needs to be 'static'. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.1.1.27,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFabricName,OCTET,read-write,,current,,The WWN that is configured on this switch to be used as the name of this Fabric when the value of t11FamEnable is 'false'. If the value of t11FamEnable is 'true', this value is not used. Fibre Channel requires that: a) all switches in an operational Fabric be configured with the same Fabric name; and b) each Fabric have a unique Fabric name. If either of these is violated, either by switches within a single Fabric being configured with different Fabric names, or by multiple Fabrics that share management applications or interact in other ways having the same Fabric name, then the behavior of the switches and associated management functions is not specified by Fibre Channel or Internet standards. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.
.1.3.6.1.2.1.137.1.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamIfTable,,not-accessible,,current,,This table contains those Fabric Address Manager parameters and status values that are per-interface (identified by an ifIndex value), per-Fabric (identified by a t11FamFabricIndex value), and per-switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). An entry in this table is automatically created when an E_Port becomes non-isolated on a particular Fabric. An entry is deleted automatically from this table if: a) the corresponding interface is no longer an E_Port (e.g., a G_Port that is dynamically determined to be an F_Port), and all configuration parameter(s) have default values; or b) the interface identified by ifIndex no longer exists (e.g., because a line-card is physically removed); or c) the row in the t11FamTable corresponding the fabric identified by t11FamFabricID no longer exists. Creating an entry in this table via t11FamIfRowStatus provides the means to specify non-default parameter value(s) for an interface at a time when the relevant row in this table does not exist, i.e., because the interface is either down or it is not an E_Port.
.1.3.6.1.2.1.137.1.1.2.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamIfEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FamFabricIndex:ifIndex,current,,An entry containing information on the interface configuration on the Fabric identified by t11FamFabricIndex.
.1.3.6.1.2.1.137.1.1.2.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamIfRcfReject,INTEGER,read-create,,current,true(1):false(2),This object determines if the incoming ReConfigure Fabric (RCF) messages on this interface on this Fabric is accepted or not. If this object is 'true', then the incoming RCF is rejected. If 'false', incoming RCF is accepted. Note that this object does not apply to the outgoing RCFs generated by this interface. Implementations that support write-access to this object can do so under whatever conditions they choose.
.1.3.6.1.2.1.137.1.1.2.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamIfRole,INTEGER,read-only,,current,nonPrincipal(1):principalUpstream(2):principalDownsteam(3):isolated(4):down(5):unknown(6),The role of this interface.
.1.3.6.1.2.1.137.1.1.2.1.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row.
.1.3.6.1.2.1.137.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamInfo,,,,,,
.1.3.6.1.2.1.137.1.2.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAreaTable,,not-accessible,,current,,This table contains area assignments per-Fabric by a switch's Fabric Address Manager. Each octet in t11FamAssignedAreaList is able to be used to index into this table to find information on each area.
.1.3.6.1.2.1.137.1.2.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAreaEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FamFabricIndex:t11FamAreaAreaId,current,,An entry gives information on the Area_ID and all Port_IDs that have been assigned within an area for the Fabric identified by t11FamFabricIndex, by the Fabric Address Manager in the switch identified by fcmInstanceIndex and fcmSwitchIndex.
.1.3.6.1.2.1.137.1.2.1.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAreaAreaId,Unsigned32,not-accessible,,current,,The Area_ID of this area.
.1.3.6.1.2.1.137.1.2.1.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAreaAssignedPortIdList,OCTET,read-only,,current,,The list of Port_IDs which have been assigned in this area and Fabric, formatted as an array of octets in ascending order. There could be zero or more Port_IDs assigned on this area and Fabric. Each octet represents one Port_ID. So, the list containing the Port_IDs 23, 45, 235, and 56 would be formatted as the 4-octet string x'172d38eb'.
.1.3.6.1.2.1.137.1.2.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDatabaseTable,,not-accessible,,current,,This table contains all information known by a switch about all the domains that have been assigned in each Fabric.
.1.3.6.1.2.1.137.1.2.2.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDatabaseEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FamFabricIndex:t11FamDatabaseDomainId,current,,An entry (conceptual row) in the t11FamDatabaseTable containing information about one Domain_ID in the Fabric identified by t11FamFabricIndex, and known by the switch identified by t11FamFabricIndex and t11FamDatabaseDomainId.
.1.3.6.1.2.1.137.1.2.2.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDatabaseDomainId,Integer32,not-accessible,,current,,The Domain_ID for which this row contains information. The value must be non-zero.
.1.3.6.1.2.1.137.1.2.2.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDatabaseSwitchWwn,OCTET,read-only,,current,,The node name (WWN) of the switch to which the corresponding value of t11FamDatabaseDomainId is currently assigned for the particular Fabric.
.1.3.6.1.2.1.137.1.2.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamMaxFcIdCacheSize,Unsigned32,read-only,,current,,The maximum number of Fibre Channel Address Identifiers that are able to be cached in the t11FamFcIdCacheTable. If the number is unknown, the value of this object is zero.
.1.3.6.1.2.1.137.1.2.4,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFcIdCacheTable,,not-accessible,,current,,This table contains all the Fibre Channel Address Identifiers that have recently been released by the Fabric Address Manager in a switch. So, it lists all the Fibre Channel Address Identifiers that have valid WWN-to-Fibre Channel Address Identifier mappings and are currently not assigned to any ports. These Fibre Channel Address Identifiers were assigned to ports but have since been released. These cached Fibre Channel Address Identifiers contain only Area_ID and Port_ID information. This cache is kept to provide best-effort re-assignment of same Fibre Channel Address Identifiers; i.e., when an Nx_Port asks for a Fibre Channel Address Identifier, soon after releasing one, the same value is re-assigned, if possible.
.1.3.6.1.2.1.137.1.2.4.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFcIdCacheEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FamFabricIndex:t11FamFcIdCacheWwn,current,,An entry (conceptual row) in the t11FamFcIdCacheTable containing information about one Fibre Channel Address Identifier that was released from a WWN, corresponding to a range of one or more ports connected to the switch (identified by t11FamFabricIndex and t11FamFcIdCacheWwn) in the Fabric (identified by t11FamFabricIndex). An entry is created when a Fibre Channel Address Identifier is released by the last port in the range. The oldest entry is deleted if the number of rows in this table reaches t11FamMaxFcIdCacheSize, and its space is required for a new entry. An entry is also deleted when its Fibre Channel Address Identifier is assigned to a port.
.1.3.6.1.2.1.137.1.2.4.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFcIdCacheWwn,OCTET,not-accessible,,current,,The N_Port_Name (WWN) of the port associated with this entry.
.1.3.6.1.2.1.137.1.2.4.1.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFcIdCacheAreaIdPortId,OCTET,read-only,,current,,The combination of this object and t11FamFcIdCachePortIds represent one range of Fibre Channel Address Identifiers, which were assigned and later released. This object contains the Area_ID and Port_ID of the first Fibre Channel Address Identifier in the range. Note that this object is only 2 bytes.
.1.3.6.1.2.1.137.1.2.4.1.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamFcIdCachePortIds,Unsigned32,read-only,,current,,The combination of t11FamFcIdCacheAreaIdPortId and this object represent one range of Fibre Channel Address Identifiers, which were assigned and later released. This object contains the number of (consecutive) Fibre Channel Address Identifiers in the range.
.1.3.6.1.2.1.137.1.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamNotifyControl,,,,,,
.1.3.6.1.2.1.137.1.3.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamNotifyFabricIndex,Unsigned32,accessible-for-notify,,current,,A unique index value that identifies a particular Fabric for which a particular notification is generated. In a Fabric conformant to SW-3, only a single Fabric can operate within a physical infrastructure, and thus, the value of this Fabric Index will always be 1. However, the current standard, FC-SW-4, defines how multiple Fabrics, each with its own management instrumentation, could operate within one (or more) physical infrastructures. In order to accommodate this scenario, this index value is used to uniquely identify a particular Fabric within a physical infrastructure.
.1.3.6.1.2.1.137.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamMIBConformance,,,,,,
.1.3.6.1.2.1.137.2.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamMIBCompliances,,,,,,
.1.3.6.1.2.1.137.2.1.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamMIBCompliance,,,,,,The compliance statement for Fibre Channel switches that implement Fabric Address Manager functionality.
.1.3.6.1.2.1.137.2.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamMIBGroups,,,,,,
.1.3.6.1.2.1.137.2.2.1,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamGroup,,,,,,A collection of general objects for displaying and configuring Fabric Address management.
.1.3.6.1.2.1.137.2.2.2,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamCommandGroup,,,,,,A collection of objects used for initiating an operation on the Fabric.
.1.3.6.1.2.1.137.2.2.3,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamDatabaseGroup,,,,,,A collection of objects containing information about Domain-IDs assignments.
.1.3.6.1.2.1.137.2.2.4,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamAreaGroup,,,,,,A collection of objects containing information about currently assigned addresses within a domain.
.1.3.6.1.2.1.137.2.2.5,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamCacheGroup,,,,,,A collection of objects containing information about recently-released Fibre Channel Address Identifiers.
.1.3.6.1.2.1.137.2.2.6,T11-FC-FABRIC-ADDR-MGR-MIB::t11FamNotificationGroup,,,,,,A collection of notifications for status monitoring and notification.
.1.3.6.1.2.1.138,ISIS-MIB::isisMIB,,,,,,This document describes a management information base for the IS-IS Routing protocol, as described in ISO 10589, when it is used to construct routing tables for IP networks, as described in RFC 1195. This document is based on a 1994 IETF document by Chris Gunner. This version has been modified to include current syntax, to exclude portions of the protocol that are not relevant to IP, and to add management support for current practice. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4444; see the RFC itself for full legal notices.
.1.3.6.1.2.1.138.0,ISIS-MIB::isisNotifications,,,,,,
.1.3.6.1.2.1.138.0.1,ISIS-MIB::isisDatabaseOverload,,,,,,This notification is generated when the system enters or leaves the Overload state. The number of times this has been generated and cleared is kept track of by isisSysStatLSPDbaseOloads.
.1.3.6.1.2.1.138.0.2,ISIS-MIB::isisManualAddressDrops,,,,,,This notification is generated when one of the manual areaAddresses assigned to this system is ignored when computing routes. The object isisNotificationAreaAddress describes the area that has been dropped. The number of times this event has been generated is counted by isisSysStatManAddrDropFromAreas. The agent must throttle the generation of consecutive isisManualAddressDrops notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.3,ISIS-MIB::isisCorruptedLSPDetected,,,,,,This notification is generated when we find that an LSP that was stored in memory has become corrupted. The number of times this has been generated is counted by isisSysCorrLSPs. We forward an LSP ID. We may have independent knowledge of the ID, but in some implementations there is a chance that the ID itself will be corrupted.
.1.3.6.1.2.1.138.0.4,ISIS-MIB::isisAttemptToExceedMaxSequence,,,,,,When the sequence number on an LSP we generate wraps the 32-bit sequence counter, we purge and wait to re-announce this information. This notification describes that event. Since these should not be generated rapidly, we generate an event each time this happens. While the first 6 bytes of the LSPID are ours, the other two contain useful information.
.1.3.6.1.2.1.138.0.5,ISIS-MIB::isisIDLenMismatch,,,,,,A notification sent when we receive a PDU with a different value for the System ID Length. This notification includes an index to identify the circuit where we saw the PDU and the header of the PDU, which may help a network manager identify the source of the confusion. The agent must throttle the generation of consecutive isisIDLenMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.6,ISIS-MIB::isisMaxAreaAddressesMismatch,,,,,,A notification sent when we receive a PDU with a different value for the Maximum Area Addresses. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. The agent must throttle the generation of consecutive isisMaxAreaAddressesMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.7,ISIS-MIB::isisOwnLSPPurge,,,,,,A notification sent when we receive a PDU with our systemID and zero age. This notification includes the circuit Index and router ID from the LSP, if available, which may help a network manager identify the source of the confusion.
.1.3.6.1.2.1.138.0.8,ISIS-MIB::isisSequenceNumberSkip,,,,,,When we receive an LSP with our System ID and different contents, we may need to reissue the LSP with a higher sequence number. We send this notification if we need to increase the sequence number by more than one. If two Intermediate Systems are configured with the same System ID, this notification will fire.
.1.3.6.1.2.1.138.0.9,ISIS-MIB::isisAuthenticationTypeFailure,,,,,,A notification sent when we receive a PDU with the wrong authentication type field. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. The agent must throttle the generation of consecutive isisAuthenticationTypeFailure notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.10,ISIS-MIB::isisAuthenticationFailure,,,,,,A notification sent when we receive a PDU with an incorrect authentication information field. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. The agent must throttle the generation of consecutive isisAuthenticationFailure notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.11,ISIS-MIB::isisVersionSkew,,,,,,A notification sent when we receive a Hello PDU from an IS running a different version of the protocol. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. The agent must throttle the generation of consecutive isisVersionSkew notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.12,ISIS-MIB::isisAreaMismatch,,,,,,A notification sent when we receive a Hello PDU from an IS that does not share any area address. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. The agent must throttle the generation of consecutive isisAreaMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.13,ISIS-MIB::isisRejectedAdjacency,,,,,,A notification sent when we receive a Hello PDU from an IS but do not establish an adjacency for some reason. The agent must throttle the generation of consecutive isisRejectedAdjacency notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.14,ISIS-MIB::isisLSPTooLargeToPropagate,,,,,,A notification sent when we attempt to propagate an LSP that is larger than the dataLinkBlockSize for the circuit. The agent must throttle the generation of consecutive isisLSPTooLargeToPropagate notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.15,ISIS-MIB::isisOrigLSPBuffSizeMismatch,,,,,,A notification sent when a Level 1 LSP or Level 2 LSP is received that is larger than the local value for isisSysLevelOrigLSPBuffSize, or when an LSP is received that contains the supported Buffer Size option and the value in the PDU option field does not match the local value for isisSysLevelOrigLSPBuffSize. We pass up the size from the option field and the size of the LSP when one of them exceeds our configuration. The agent must throttle the generation of consecutive isisOrigLSPBuffSizeMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.16,ISIS-MIB::isisProtocolsSupportedMismatch,,,,,,A notification sent when a non-pseudonode segment 0 LSP is received that has no matching protocols supported. This may be because the system does not generate the field, or because there are no common elements. The list of protocols supported should be included in the notification: it may be empty if the TLV is not supported, or if the TLV is empty. The agent must throttle the generation of consecutive isisProtocolsSupportedMismatch notifications so that there is at least a 5-second gap between notifications of this type. When notifications are throttled, they are dropped, not queued for sending at a future time.
.1.3.6.1.2.1.138.0.17,ISIS-MIB::isisAdjacencyChange,,,,,,A notification sent when an adjacency changes state, entering or leaving state up. The first 6 bytes of the isisPduLspId are the SystemID of the adjacent IS. The isisAdjState is the new state of the adjacency.
.1.3.6.1.2.1.138.0.18,ISIS-MIB::isisLSPErrorDetected,,,,,,This notification is generated when we receive an LSP with a parse error. The isisCircIfIndex holds an index of the circuit on which the PDU arrived. The isisPduFragment holds the start of the LSP, and the isisErrorOffset points to the problem. If the problem is a malformed TLV, isisErrorOffset points to the start of the TLV, and isisErrorTLVType holds the value of the type. If the problem is with the LSP header, isisErrorOffset points to the suspicious byte. The number of such LSPs is accumulated in isisSysStatLSPErrors.
.1.3.6.1.2.1.138.1,ISIS-MIB::isisObjects,,,,,,
.1.3.6.1.2.1.138.1.1,ISIS-MIB::isisSystem,,,,,,
.1.3.6.1.2.1.138.1.1.1,ISIS-MIB::isisSysObject,,,,,,
.1.3.6.1.2.1.138.1.1.1.1,ISIS-MIB::isisSysVersion,INTEGER,read-only,,current,unknown(0):one(1),The version number of the IS-IS protocol that is implemented.
.1.3.6.1.2.1.138.1.1.1.2,ISIS-MIB::isisSysLevelType,INTEGER,read-write,,current,level1(1):level2(2):level1and2(3),At which levels is the Intermediate System running? This object may not be modified when the isisSysAdminState variable is in state 'on' for this Intermediate System. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.3,ISIS-MIB::isisSysID,OCTET,read-write,,current,,The ID for this Intermediate System. This value is appended to each of the area addresses to form the Network Entity Titles. The derivation of a value for this object is implementation specific. Some implementations may automatically assign values and not permit an SNMP write, while others may require the value to be set manually. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.4,ISIS-MIB::isisSysMaxPathSplits,Unsigned32,read-write,,current,,Maximum number of paths with equal routing metric value which it is permitted to split between. This object may not be modified when the isisSysAdminState variable is in state 'on' for this Intermediate System. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.5,ISIS-MIB::isisSysMaxLSPGenInt,Unsigned32,read-write,,current,,Maximum interval, in seconds, between generated LSPs by this Intermediate System. This object follows the ResettingTimer behavior. The value must be greater than any value configured for isisSysLevelMinLSPGenInt, and should be at least 300 seconds less than isisSysMaxAge. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.6,ISIS-MIB::isisSysPollESHelloRate,Unsigned32,read-write,,current,,The value, in seconds, to be used for the suggested ES configuration timer in ISH PDUs when soliciting the ES configuration. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.7,ISIS-MIB::isisSysWaitTime,Unsigned32,read-write,,current,,Number of seconds to delay in state 'waiting' before entering the state 'on'. This object follows the ResettingTimer behavior. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.8,ISIS-MIB::isisSysAdminState,INTEGER,read-write,,current,on(1):off(2),The administrative state of this Intermediate System. Setting this object to the value 'on' when its current value is 'off' enables the Intermediate System. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.9,ISIS-MIB::isisSysL2toL1Leaking,INTEGER,read-write,,current,true(1):false(2),If true, allow the router to leak L2 routes into L1. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.10,ISIS-MIB::isisSysMaxAge,Unsigned32,read-write,,current,,Value to place in RemainingLifeTime field of the LSPs we generate. This should be at least 300 seconds greater than isisSysMaxLSPGenInt. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.11,ISIS-MIB::isisSysReceiveLSPBufferSize,Unsigned32,read-write,,current,,Size of the largest buffer we are designed or configured to store. This should be at least as big as the maximum isisSysLevelOrigLSPBuffSize supported by the system. If resources allow, we will store and flood LSPs larger than isisSysReceiveLSPBufferSize, as this can help avoid problems in networks with different values for isisSysLevelOrigLSPBuffSize. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.1.12,ISIS-MIB::isisSysProtSupported,BITS,read-only,,current,iso8473(0):ipv4(1):ipv6(2),This attribute contains the set of protocols supported by this Intermediate System.
.1.3.6.1.2.1.138.1.1.1.13,ISIS-MIB::isisSysNotificationEnable,INTEGER,read-write,,current,true(1):false(2),If this object is set to true(1), then it enables the emission of IS-IS Notifications. If it is set to false(2), these notifications are not sent. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.2,ISIS-MIB::isisManAreaAddrTable,,not-accessible,,current,,The set of manual area addresses configured on this Intermediate System. At least one row in which the value of isisManAreaAddrExistState is active must be present. The maximum number of rows in this table for which the object isisManAreaAddrExistState has the value active is 3. An attempt to create more than 3 rows of isisManAreaAddrEntry with state 'active' in one instance of the IS-IS protocol should return inconsistentValue.
.1.3.6.1.2.1.138.1.1.2.1,ISIS-MIB::isisManAreaAddrEntry,,not-accessible,isisManAreaAddr,current,,Each entry contains one area address manually configured on this system. Dynamically created rows MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.1.2.1.1,ISIS-MIB::isisManAreaAddr,OCTET,not-accessible,,current,,A manually configured area address for this system. Note: An index for the entry {1, {49.0001} active} in this table would be the ordered pair (1, (0x03 0x49 0x00 0x01)), as the length of an octet string is part of the OID.
.1.3.6.1.2.1.138.1.1.2.1.2,ISIS-MIB::isisManAreaAddrExistState,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The state of the isisManAreaAddrEntry. If the isisSysAdminState for this Intermediate System is 'on' and an attempt is made to set this object to the value 'destroy' or 'notInService' when this is the only isisManAreaAddrEntry in state 'active' for this Intermediate System should return inconsistentValue. A row entry cannot be modified when the value of this object is 'active'.
.1.3.6.1.2.1.138.1.1.3,ISIS-MIB::isisAreaAddrTable,,not-accessible,,current,,The union of the sets of area addresses reported in all Level 1 LSPs with fragment number zero generated by this Intermediate System, or received from other Intermediate Systems that are reachable via Level 1 routing.
.1.3.6.1.2.1.138.1.1.3.1,ISIS-MIB::isisAreaAddrEntry,,not-accessible,isisAreaAddr,current,,Each entry contains one area address reported in a Level 1 LSP generated or received by this Intermediate System. Dynamically learned rows do not survive an agent reboot.
.1.3.6.1.2.1.138.1.1.3.1.1,ISIS-MIB::isisAreaAddr,OCTET,read-only,,current,,An area address reported in a Level 1 LSP.
.1.3.6.1.2.1.138.1.1.4,ISIS-MIB::isisSummAddrTable,,not-accessible,,current,,The set of IP summary addresses to use in forming summary TLVs originated by this Intermediate System. An administrator may use a summary address to combine and modify IP Reachability announcements. If the Intermediate system can reach any subset of the summary address, the summary address MUST be announced instead, at the configured metric.
.1.3.6.1.2.1.138.1.1.4.1,ISIS-MIB::isisSummAddrEntry,,not-accessible,isisSummAddressType:isisSummAddress:isisSummAddrPrefixLen,current,,Each entry contains one IP summary address. Dynamically created rows MUST survive an agent reboot. Implementers need to be aware that if the total number of elements (octets or sub-identifiers) in isisSummAddress and isisSummAddrPrefixLen is too great, then OIDs of column instances in this table will have more than 128 subidentifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.138.1.1.4.1.1,ISIS-MIB::isisSummAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The Type of IP address for this summary address.
.1.3.6.1.2.1.138.1.1.4.1.2,ISIS-MIB::isisSummAddress,OCTET,not-accessible,,current,,The IP Address value for this summary address. The address must not contain any set host bits (bits set after the address prefix determined by isisSummAddrPrefixLen). The type of this address is determined by the value of the isisSummAddressType object.
.1.3.6.1.2.1.138.1.1.4.1.3,ISIS-MIB::isisSummAddrPrefixLen,Unsigned32,not-accessible,,current,,The Length of the IP NetMask for this summary address. The values for the index objects isisSummAddress and isisSummAddrPrefixLen must be consistent. When the value of isisSummAddress (excluding the zone index, if one is present) is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object isisSummAddrPrefixLen MUST be equal to x. If not, then the index pair is not consistent, and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.138.1.1.4.1.4,ISIS-MIB::isisSummAddrExistState,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The existence state of this summary address. Support for 'createAndWait' and 'notInService' is not required. A row entry cannot be modified when the value of this object is 'active'.
.1.3.6.1.2.1.138.1.1.4.1.5,ISIS-MIB::isisSummAddrMetric,Unsigned32,read-create,,current,,The metric value to announce this summary address within LSPs generated by this system.
.1.3.6.1.2.1.138.1.1.4.1.6,ISIS-MIB::isisSummAddrFullMetric,Unsigned32,read-create,,current,,The wide metric value to announce this summary address within LSPs generated by this system.
.1.3.6.1.2.1.138.1.1.5,ISIS-MIB::isisRedistributeAddrTable,,not-accessible,,current,,This table provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table MUST be announced at L1 by routers when isisSysL2toL1Leaking is enabled. Routes that fall into the ranges specified are announced as is, without being summarized. Routes that do not match a summary mask are not announced.
.1.3.6.1.2.1.138.1.1.5.1,ISIS-MIB::isisRedistributeAddrEntry,,not-accessible,isisRedistributeAddrType:isisRedistributeAddrAddress:isisRedistributeAddrPrefixLen,current,,Each entry contains one configured IP summary address to manage leaking L2 addresses into L1. Dynamically created rows MUST survive an agent reboot. Implementers need to be aware that if the total number of elements (octets or sub-identifiers) in isisRedistributeAddrAddress and isisRedistributeAddrPrefixLen is too great, then OIDs of column instances in this table will have more than 128 subidentifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.138.1.1.5.1.1,ISIS-MIB::isisRedistributeAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The Type of IP address for this summary address.
.1.3.6.1.2.1.138.1.1.5.1.2,ISIS-MIB::isisRedistributeAddrAddress,OCTET,not-accessible,,current,,The IP Address value for this summary address. The type of this address is determined by the value of the isisRedistributeAddrType object. The address must not contain any set host bits - bits set after the address prefix determined by isisRedistributeAddrPrefixLen.
.1.3.6.1.2.1.138.1.1.5.1.3,ISIS-MIB::isisRedistributeAddrPrefixLen,Unsigned32,not-accessible,,current,,The Length of the IP NetMask for this summary address. The values for the index objects isisRedistributeAddrAddress and isisRedistributeAddrPrefixLen must be consistent. When the value of isisRedistributeAddrAddress (excluding the zone index, if one is present) is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object isisRedistributeAddrPrefixLen MUST be equal to x. If not, then the index pair is not consistent, and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.138.1.1.5.1.4,ISIS-MIB::isisRedistributeAddrExistState,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The existence state of this summary address. Support for createAndWait and notInService is not required. A row entry cannot be modified when the value of this object is 'active'.
.1.3.6.1.2.1.138.1.1.6,ISIS-MIB::isisRouterTable,,not-accessible,,current,,The set of hostnames and router ID.
.1.3.6.1.2.1.138.1.1.6.1,ISIS-MIB::isisRouterEntry,,not-accessible,isisRouterSysID:isisRouterLevel,current,,Each entry tracks information about one Intermediate System at one level. Dynamically learned rows do not survive an agent reboot.
.1.3.6.1.2.1.138.1.1.6.1.1,ISIS-MIB::isisRouterSysID,OCTET,not-accessible,,current,,The System ID of the Intermediate System.
.1.3.6.1.2.1.138.1.1.6.1.2,ISIS-MIB::isisRouterLevel,INTEGER,not-accessible,,current,area(1):domain(2),The level at which the information about this Intermediate System was received.
.1.3.6.1.2.1.138.1.1.6.1.3,ISIS-MIB::isisRouterHostName,OCTET,read-only,,current,,The hostname listed in the LSP, or a zero-length string if none.
.1.3.6.1.2.1.138.1.1.6.1.4,ISIS-MIB::isisRouterID,Unsigned32,read-only,,current,,The Router ID found in the LSP, or zero if none.
.1.3.6.1.2.1.138.1.2,ISIS-MIB::isisSysLevel,,,,,,
.1.3.6.1.2.1.138.1.2.1,ISIS-MIB::isisSysLevelTable,,not-accessible,,current,,Level specific information about the System.
.1.3.6.1.2.1.138.1.2.1.1,ISIS-MIB::isisSysLevelEntry,,not-accessible,isisSysLevelIndex,current,,Each row describes variables configured for Area or Domain. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.2.1.1.1,ISIS-MIB::isisSysLevelIndex,INTEGER,not-accessible,,current,area(1):domain(2),The level that this entry describes.
.1.3.6.1.2.1.138.1.2.1.1.2,ISIS-MIB::isisSysLevelOrigLSPBuffSize,Unsigned32,read-write,,current,,The maximum size of LSPs and SNPs originated by this Intermediate System at this level. This object may not be modified when the isisSysAdminState variable is in state 'on' for this Intermediate System.
.1.3.6.1.2.1.138.1.2.1.1.3,ISIS-MIB::isisSysLevelMinLSPGenInt,Unsigned32,read-write,,current,,Minimum interval, in seconds, between successive generation of LSPs with the same LSPID at this level by this Intermediate System.
.1.3.6.1.2.1.138.1.2.1.1.4,ISIS-MIB::isisSysLevelState,INTEGER,read-only,,current,off(1):on(2):waiting(3):overloaded(4),The state of the database at this level. The value 'off' indicates that IS-IS is not active at this level. The value 'on' indicates that IS-IS is active at this level and is not overloaded. The value 'waiting' indicates a database that is low on an essential resource, such as memory. The administrator may force the state to 'overloaded' by setting the object isisSysLevelSetOverload. If the state is 'waiting' or 'overloaded', we originate LSPs with the overload bit set.
.1.3.6.1.2.1.138.1.2.1.1.5,ISIS-MIB::isisSysLevelSetOverload,INTEGER,read-write,,current,true(1):false(2),Administratively set the overload bit for the level. The overload bit MUST continue to be set if the implementation runs out of memory, independent of this variable. It may also be set manually independent of this variable, using the isisSysLevelSetOverloadUntil object.
.1.3.6.1.2.1.138.1.2.1.1.6,ISIS-MIB::isisSysLevelSetOverloadUntil,Unsigned32,read-write,,current,,If this object is non-zero, the overload bit is set at this level when the isisSysAdminState variable goes to state 'on' for this Intermediate System. The overload bit remains set for isisSysLevelSetOverloadUntil seconds. When isisSysLevelSetOverloadUntil seconds have elapsed, the overload flag remains set if the implementation has run out of memory, or if it is set manually using the isisSysLevelSetOverload object. If isisSysLevelSetOverload is false, the system clears the overload bit when isisSysLevelSetOverloadUntil seconds have elapsed, if the system has not run out of memory.
.1.3.6.1.2.1.138.1.2.1.1.7,ISIS-MIB::isisSysLevelMetricStyle,INTEGER,read-write,,current,narrow(1):wide(2):both(3),Which style of metric do we generate in our LSPs at this level?
.1.3.6.1.2.1.138.1.2.1.1.8,ISIS-MIB::isisSysLevelSPFConsiders,INTEGER,read-write,,current,narrow(1):wide(2):both(3),Which style of metric do we consider in our SPF computation at this level?
.1.3.6.1.2.1.138.1.2.1.1.9,ISIS-MIB::isisSysLevelTEEnabled,INTEGER,read-write,,current,true(1):false(2),Do we do Traffic Engineering at this level?
.1.3.6.1.2.1.138.1.3,ISIS-MIB::isisCirc,,,,,,
.1.3.6.1.2.1.138.1.3.1,ISIS-MIB::isisNextCircIndex,Unsigned32,read-only,,current,,This object is used to assist a management application in creating new rows in the isisCircTable. If it is possible to create a new instance of isisCircEntry, then this object will contain a non-zero value that is not in use as the index of any row in the isisCircTable. The network manager reads the value of this object and then (if the value read is non-zero) attempts to create the corresponding instance of isisCircEntry. If the set request fails with the code 'inconsistentValue', then the process must be repeated; if the set request succeeds, then the agent will change the value of this object according to an implementation-specific algorithm.
.1.3.6.1.2.1.138.1.3.2,ISIS-MIB::isisCircTable,,not-accessible,,current,,The table of circuits used by this Intermediate System.
.1.3.6.1.2.1.138.1.3.2.1,ISIS-MIB::isisCircEntry,,not-accessible,isisCircIndex,current,,An isisCircEntry exists for each circuit configured for Integrated IS-IS on this system. Dynamically created rows MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.3.2.1.1,ISIS-MIB::isisCircIndex,Unsigned32,not-accessible,,current,,An index used to uniquely identify this circuit. When creating a row in this table, the isisNextCircIndex object should be retrieved, and its value should be specified as the value of this index using a SET operation. A retrieved value of zero(0) indicates that no rows can be created at this time.
.1.3.6.1.2.1.138.1.3.2.1.2,ISIS-MIB::isisCircIfIndex,Integer32,read-create,,current,,The value of ifIndex for the interface to which this circuit corresponds. This object cannot be modified after creation.
.1.3.6.1.2.1.138.1.3.2.1.3,ISIS-MIB::isisCircAdminState,INTEGER,read-create,,current,on(1):off(2),The administrative state of the circuit.
.1.3.6.1.2.1.138.1.3.2.1.4,ISIS-MIB::isisCircExistState,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The existence state of this circuit. Setting the state to 'notInService' halts the generation and processing of IS-IS protocol PDUs on this circuit. Setting the state to destroy will also erase any configuration associated with the circuit. Support for 'createAndWait' and 'notInService' is not required. A row entry cannot be modified when the value of this object is 'active'.
.1.3.6.1.2.1.138.1.3.2.1.5,ISIS-MIB::isisCircType,INTEGER,read-create,,current,broadcast(1):ptToPt(2):staticIn(3):staticOut(4):dA(5),The type of the circuit. This object follows the ReplaceOnlyWhileDisabled behavior. The type specified must be compatible with the type of the interface defined by the value of isisCircIfIndex.
.1.3.6.1.2.1.138.1.3.2.1.6,ISIS-MIB::isisCircExtDomain,INTEGER,read-create,,current,true(1):false(2),If true, suppress normal transmission of and interpretation of Intra-domain IS-IS PDUs on this circuit.
.1.3.6.1.2.1.138.1.3.2.1.7,ISIS-MIB::isisCircLevelType,INTEGER,read-create,,current,level1(1):level2(2):level1and2(3),Indicates which type of packets will be sent and accepted on this circuit. The values set will be saved, but the values used will be modified by the settings of isisSysLevelType. Thus, if the isisSysTpe is level2 and the isisCircLevelType for a circuit is level1, the circuit will not send or receive IS-IS packets. This object follows the ReplaceOnlyWhileDisabled behavior.
.1.3.6.1.2.1.138.1.3.2.1.8,ISIS-MIB::isisCircPassiveCircuit,INTEGER,read-create,,current,true(1):false(2),Should we include this interface in LSPs, even if it is not running the IS-IS Protocol?
.1.3.6.1.2.1.138.1.3.2.1.9,ISIS-MIB::isisCircMeshGroupEnabled,INTEGER,read-create,,current,inactive(1):blocked(2):set(3),Is this port a member of a mesh group, or is it blocked? Circuits in the same mesh group act as a virtual multiaccess network. LSPs seen on one circuit in a mesh group will not be flooded to another circuit in the same mesh group.
.1.3.6.1.2.1.138.1.3.2.1.10,ISIS-MIB::isisCircMeshGroup,Unsigned32,read-create,,current,,Circuits in the same mesh group act as a virtual multiaccess network. LSPs seen on one circuit in a mesh group will not be flooded to another circuit in the same mesh group. If isisCircMeshGroupEnabled is inactive or blocked, this value is ignored.
.1.3.6.1.2.1.138.1.3.2.1.11,ISIS-MIB::isisCircSmallHellos,INTEGER,read-create,,current,true(1):false(2),Can we send unpadded hellos on LAN circuits? False means the LAN Hellos must be padded. Implementations should allow the administrator to read this value. An implementation need not be able to support unpadded hellos to be conformant.
.1.3.6.1.2.1.138.1.3.2.1.12,ISIS-MIB::isisCircLastUpTime,TimeTicks,read-only,,current,,How long the circuit has been enabled, measured in hundredths of seconds since the last re-initialization of the network management subsystem; 0 if the circuit has never been 'on'.
.1.3.6.1.2.1.138.1.3.2.1.13,ISIS-MIB::isisCirc3WayEnabled,INTEGER,read-create,,current,true(1):false(2),Is this circuit enabled to run 3Way handshake?
.1.3.6.1.2.1.138.1.3.2.1.14,ISIS-MIB::isisCircExtendedCircID,Unsigned32,read-create,,current,,The value to be used as the extended circuit ID in 3Way handshake. This value is only used if isisCirc3WayEnabled is true, and it must be unique across all circuits on this IS.
.1.3.6.1.2.1.138.1.4,ISIS-MIB::isisCircLevelValues,,,,,,
.1.3.6.1.2.1.138.1.4.1,ISIS-MIB::isisCircLevelTable,,not-accessible,,current,,Level specific information about circuits used by IS-IS.
.1.3.6.1.2.1.138.1.4.1.1,ISIS-MIB::isisCircLevelEntry,,not-accessible,isisCircIndex:isisCircLevelIndex,current,,An isisCircLevelEntry exists for each level on each circuit configured for Integrated IS-IS on this system. Configured values MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.4.1.1.1,ISIS-MIB::isisCircLevelIndex,INTEGER,not-accessible,,current,area(1):domain(2),The level that this entry describes.
.1.3.6.1.2.1.138.1.4.1.1.2,ISIS-MIB::isisCircLevelMetric,Unsigned32,read-write,,current,,The metric value of this circuit for this level.
.1.3.6.1.2.1.138.1.4.1.1.3,ISIS-MIB::isisCircLevelWideMetric,Unsigned32,read-write,,current,,The wide metric value of this circuit for this level.
.1.3.6.1.2.1.138.1.4.1.1.4,ISIS-MIB::isisCircLevelISPriority,Unsigned32,read-write,,current,,The priority for becoming the LAN-Designated Intermediate System at this level.
.1.3.6.1.2.1.138.1.4.1.1.5,ISIS-MIB::isisCircLevelIDOctet,Unsigned32,read-only,,current,,A one-byte identifier for the circuit selected by the Intermediate System. On point-to-point circuits, the value is used as the Local Circuit ID in point-to-point IIH PDUs transmitted on this circuit. In this case, values of isisCircLevelIDOctet do not need to be unique. For broadcast circuits, the value is used to generate the LAN ID that will be used if this Intermediate System is elected as the Designated IS on this circuit. The value is required to differ on LANs where the Intermediate System is the Designated Intermediate System.
.1.3.6.1.2.1.138.1.4.1.1.6,ISIS-MIB::isisCircLevelID,OCTET,read-only,,current,,On a point-to-point circuit with a fully initialized adjacency to a peer IS, the value of this object is the circuit ID negotiated during adjacency initialization. On a point to point circuit without such an adjacency, the value is the concatenation of the local system ID and the one-byte isisCircLevelIDOctet for this circuit, i.e., the value that would be proposed for the circuit ID. On other circuit types, the value returned is the zero- length OCTET STRING.
.1.3.6.1.2.1.138.1.4.1.1.7,ISIS-MIB::isisCircLevelDesIS,OCTET,read-only,,current,,The ID of the LAN-Designated Intermediate System on this circuit at this level. If, for any reason, this system is not partaking in the relevant Designated Intermediate System election process, then the value returned is the zero-length OCTET STRING.
.1.3.6.1.2.1.138.1.4.1.1.8,ISIS-MIB::isisCircLevelHelloMultiplier,Unsigned32,read-write,,current,,This value is multiplied by the corresponding HelloTimer, and the result in seconds (rounded up) is used as the holding time in transmitted hellos, to be used by receivers of hello packets from this IS.
.1.3.6.1.2.1.138.1.4.1.1.9,ISIS-MIB::isisCircLevelHelloTimer,Unsigned32,read-write,,current,,Maximum period, in milliseconds, between IIH PDUs on multiaccess networks at this level for LANs. The value at L1 is used as the period between Hellos on L1L2 point-to-point circuits. Setting this value at level 2 on an L1L2 point-to-point circuit will result in an error of InconsistentValue. This object follows the ResettingTimer behavior.
.1.3.6.1.2.1.138.1.4.1.1.10,ISIS-MIB::isisCircLevelDRHelloTimer,Unsigned32,read-write,,current,,Period, in milliseconds, between Hello PDUs on multiaccess networks when this IS is the Designated Intermediate System. This object follows the ResettingTimer behavior.
.1.3.6.1.2.1.138.1.4.1.1.11,ISIS-MIB::isisCircLevelLSPThrottle,Unsigned32,read-write,,current,,Minimal interval of time, in milliseconds, between transmissions of LSPs on an interface at this level.
.1.3.6.1.2.1.138.1.4.1.1.12,ISIS-MIB::isisCircLevelMinLSPRetransInt,Unsigned32,read-write,,current,,Minimum interval, in seconds, between re-transmission of an LSP at this level. This object follows the ResettingTimer behavior. Note that isisCircLevelLSPThrottle controls how fast we send back-to-back LSPs. This variable controls how fast we re-send the same LSP.
.1.3.6.1.2.1.138.1.4.1.1.13,ISIS-MIB::isisCircLevelCSNPInterval,Unsigned32,read-write,,current,,Interval of time, in seconds, between periodic transmission of a complete set of CSNPs on multiaccess networks if this router is the designated router at this level. This object follows the ResettingTimer behavior.
.1.3.6.1.2.1.138.1.4.1.1.14,ISIS-MIB::isisCircLevelPartSNPInterval,Unsigned32,read-write,,current,,Minimum interval, in seconds, between sending Partial Sequence Number PDUs at this level. This object follows the ResettingTimer behavior.
.1.3.6.1.2.1.138.1.5,ISIS-MIB::isisCounters,,,,,,
.1.3.6.1.2.1.138.1.5.1,ISIS-MIB::isisSystemCounterTable,,not-accessible,,current,,System-wide counters for this Intermediate System.
.1.3.6.1.2.1.138.1.5.1.1,ISIS-MIB::isisSystemCounterEntry,,not-accessible,isisSysStatLevel,current,,System-wide IS-IS counters.
.1.3.6.1.2.1.138.1.5.1.1.1,ISIS-MIB::isisSysStatLevel,INTEGER,not-accessible,,current,area(1):domain(2),The level that this entry describes.
.1.3.6.1.2.1.138.1.5.1.1.2,ISIS-MIB::isisSysStatCorrLSPs,Counter32,read-only,,current,,Number of corrupted in-memory LSPs detected. LSPs received from the wire with a bad checksum are silently dropped and are not counted. LSPs received from the wire with parse errors are counted by isisSysStatLSPErrors.
.1.3.6.1.2.1.138.1.5.1.1.3,ISIS-MIB::isisSysStatAuthTypeFails,Counter32,read-only,,current,,The number of authentication type mismatches recognized by this Intermediate System.
.1.3.6.1.2.1.138.1.5.1.1.4,ISIS-MIB::isisSysStatAuthFails,Counter32,read-only,,current,,The number of authentication key failures recognized by this Intermediate System.
.1.3.6.1.2.1.138.1.5.1.1.5,ISIS-MIB::isisSysStatLSPDbaseOloads,Counter32,read-only,,current,,Number of times the LSP database has become overloaded.
.1.3.6.1.2.1.138.1.5.1.1.6,ISIS-MIB::isisSysStatManAddrDropFromAreas,Counter32,read-only,,current,,Number of times a manual address has been dropped from the area.
.1.3.6.1.2.1.138.1.5.1.1.7,ISIS-MIB::isisSysStatAttmptToExMaxSeqNums,Counter32,read-only,,current,,Number of times the IS has attempted to exceed the maximum sequence number.
.1.3.6.1.2.1.138.1.5.1.1.8,ISIS-MIB::isisSysStatSeqNumSkips,Counter32,read-only,,current,,Number of times a sequence number skip has occurred.
.1.3.6.1.2.1.138.1.5.1.1.9,ISIS-MIB::isisSysStatOwnLSPPurges,Counter32,read-only,,current,,Number of times a zero-aged copy of the system's own LSP is received from some other node.
.1.3.6.1.2.1.138.1.5.1.1.10,ISIS-MIB::isisSysStatIDFieldLenMismatches,Counter32,read-only,,current,,Number of times a PDU is received with a different value for ID field length from that of the receiving system.
.1.3.6.1.2.1.138.1.5.1.1.11,ISIS-MIB::isisSysStatPartChanges,Counter32,read-only,,current,,Partition changes.
.1.3.6.1.2.1.138.1.5.1.1.12,ISIS-MIB::isisSysStatSPFRuns,Counter32,read-only,,current,,Number of times we ran SPF at this level.
.1.3.6.1.2.1.138.1.5.1.1.13,ISIS-MIB::isisSysStatLSPErrors,Counter32,read-only,,current,,Number of LSPs with errors we have received.
.1.3.6.1.2.1.138.1.5.2,ISIS-MIB::isisCircuitCounterTable,,not-accessible,,current,,Circuit specific counters for this Intermediate System.
.1.3.6.1.2.1.138.1.5.2.1,ISIS-MIB::isisCircuitCounterEntry,,not-accessible,isisCircIndex:isisCircuitType,current,,An isisCircuitCounterEntry exists for each circuit used by Integrated IS-IS on this system.
.1.3.6.1.2.1.138.1.5.2.1.1,ISIS-MIB::isisCircuitType,INTEGER,not-accessible,,current,lanlevel1(1):lanlevel2(2):p2pcircuit(3),What type of circuit saw these counts? The point-to-point Hello PDU includes both L1 and L2, and ISs form a single adjacency on point-to-point links. Thus, we combine counts on point-to-point links into one group.
.1.3.6.1.2.1.138.1.5.2.1.2,ISIS-MIB::isisCircAdjChanges,Counter32,read-only,,current,,The number of times an adjacency state change has occurred on this circuit.
.1.3.6.1.2.1.138.1.5.2.1.3,ISIS-MIB::isisCircNumAdj,Unsigned32,read-only,,current,,The number of adjacencies on this circuit.
.1.3.6.1.2.1.138.1.5.2.1.4,ISIS-MIB::isisCircInitFails,Counter32,read-only,,current,,The number of times initialization of this circuit has failed. This counts events such as PPP NCP failures. Failures to form an adjacency are counted by isisCircRejAdjs.
.1.3.6.1.2.1.138.1.5.2.1.5,ISIS-MIB::isisCircRejAdjs,Counter32,read-only,,current,,The number of times an adjacency has been rejected on this circuit.
.1.3.6.1.2.1.138.1.5.2.1.6,ISIS-MIB::isisCircIDFieldLenMismatches,Counter32,read-only,,current,,The number of times an IS-IS control PDU with an ID field length different from that for this system has been received.
.1.3.6.1.2.1.138.1.5.2.1.7,ISIS-MIB::isisCircMaxAreaAddrMismatches,Counter32,read-only,,current,,The number of times an IS-IS control PDU with a max area address field different from that for this system has been received.
.1.3.6.1.2.1.138.1.5.2.1.8,ISIS-MIB::isisCircAuthTypeFails,Counter32,read-only,,current,,The number of times an IS-IS control PDU with an auth type field different from that for this system has been received.
.1.3.6.1.2.1.138.1.5.2.1.9,ISIS-MIB::isisCircAuthFails,Counter32,read-only,,current,,The number of times an IS-IS control PDU with the correct auth type has failed to pass authentication validation.
.1.3.6.1.2.1.138.1.5.2.1.10,ISIS-MIB::isisCircLANDesISChanges,Counter32,read-only,,current,,The number of times the Designated IS has changed on this circuit at this level. If the circuit is point to point, this count is zero.
.1.3.6.1.2.1.138.1.5.3,ISIS-MIB::isisPacketCounterTable,,not-accessible,,current,,Information about IS-IS protocol traffic at one level, on one circuit, in one direction.
.1.3.6.1.2.1.138.1.5.3.1,ISIS-MIB::isisPacketCounterEntry,,not-accessible,isisCircIndex:isisPacketCountLevel:isisPacketCountDirection,current,,Information about IS-IS protocol traffic at one level, on one circuit, in one direction.
.1.3.6.1.2.1.138.1.5.3.1.1,ISIS-MIB::isisPacketCountLevel,INTEGER,not-accessible,,current,area(1):domain(2),The level at which these PDU counts have been collected.
.1.3.6.1.2.1.138.1.5.3.1.2,ISIS-MIB::isisPacketCountDirection,INTEGER,not-accessible,,current,sending(1):receiving(2),Were we sending or receiving these PDUs?
.1.3.6.1.2.1.138.1.5.3.1.3,ISIS-MIB::isisPacketCountIIHello,Counter32,read-only,,current,, at this levelThe number of IS-IS Hello PDUs seen in this direction at this level. Point-to-Point IIH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.
.1.3.6.1.2.1.138.1.5.3.1.4,ISIS-MIB::isisPacketCountISHello,Counter32,read-only,,current,, this level.The number of ES-IS Hello PDUs seen in this direction. ISH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.
.1.3.6.1.2.1.138.1.5.3.1.5,ISIS-MIB::isisPacketCountESHello,Counter32,read-only,,current,, this levelThe number of ES Hello PDUs seen in this direction. ESH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.
.1.3.6.1.2.1.138.1.5.3.1.6,ISIS-MIB::isisPacketCountLSP,Counter32,read-only,,current,, this levelThe number of IS-IS LSPs seen in this direction at this level.
.1.3.6.1.2.1.138.1.5.3.1.7,ISIS-MIB::isisPacketCountCSNP,Counter32,read-only,,current,, this levelThe number of IS-IS CSNPs seen in this direction at this level.
.1.3.6.1.2.1.138.1.5.3.1.8,ISIS-MIB::isisPacketCountPSNP,Counter32,read-only,,current,, this levelThe number of IS-IS PSNPs seen in this direction at this level.
.1.3.6.1.2.1.138.1.5.3.1.9,ISIS-MIB::isisPacketCountUnknown,Counter32,read-only,,current,,The number of unknown IS-IS PDUs seen at this level.
.1.3.6.1.2.1.138.1.6,ISIS-MIB::isisISAdj,,,,,,
.1.3.6.1.2.1.138.1.6.1,ISIS-MIB::isisISAdjTable,,not-accessible,,current,,The table of adjacencies to Intermediate Systems.
.1.3.6.1.2.1.138.1.6.1.1,ISIS-MIB::isisISAdjEntry,,not-accessible,isisCircIndex:isisISAdjIndex,current,,Each entry corresponds to one adjacency to an Intermediate System on this system. Dynamically learned rows do not survive an agent reboot.
.1.3.6.1.2.1.138.1.6.1.1.1,ISIS-MIB::isisISAdjIndex,Unsigned32,not-accessible,,current,,A unique value identifying the IS adjacency from all other such adjacencies on this circuit. This value is automatically assigned by the system when the adjacency is created.
.1.3.6.1.2.1.138.1.6.1.1.2,ISIS-MIB::isisISAdjState,INTEGER,read-only,,current,down(1):initializing(2):up(3):failed(4),The state of the adjacency.
.1.3.6.1.2.1.138.1.6.1.1.3,ISIS-MIB::isisISAdj3WayState,INTEGER,read-only,,current,up(0):initializing(1):down(2):failed(3),The 3Way state of the adjacency. These are picked to match the historical on-the-wire representation of the 3Way state and are not intended to match isisISAdjState.
.1.3.6.1.2.1.138.1.6.1.1.4,ISIS-MIB::isisISAdjNeighSNPAAddress,OCTET,read-only,,current,,The SNPA address of the neighboring system.
.1.3.6.1.2.1.138.1.6.1.1.5,ISIS-MIB::isisISAdjNeighSysType,INTEGER,read-only,,current,l1IntermediateSystem(1):l2IntermediateSystem(2):l1L2IntermediateSystem(3):unknown(4),The type of the neighboring system.
.1.3.6.1.2.1.138.1.6.1.1.6,ISIS-MIB::isisISAdjNeighSysID,OCTET,read-only,,current,,The system ID of the neighboring Intermediate System.
.1.3.6.1.2.1.138.1.6.1.1.7,ISIS-MIB::isisISAdjNbrExtendedCircID,Unsigned32,read-only,,current,,The 4-byte Extended Circuit ID learned from the Neighbor during 3-way handshake, or 0.
.1.3.6.1.2.1.138.1.6.1.1.8,ISIS-MIB::isisISAdjUsage,INTEGER,read-only,,current,level1(1):level2(2):level1and2(3),How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at L1, and level2 for the adjacency between peers at L2.
.1.3.6.1.2.1.138.1.6.1.1.9,ISIS-MIB::isisISAdjHoldTimer,Unsigned32,read-only,,current,,The holding time, in seconds, for this adjacency. This value is based on received IIH PDUs and the elapsed time since receipt.
.1.3.6.1.2.1.138.1.6.1.1.10,ISIS-MIB::isisISAdjNeighPriority,Unsigned32,read-only,,current,,Priority of the neighboring Intermediate System for becoming the Designated Intermediate System.
.1.3.6.1.2.1.138.1.6.1.1.11,ISIS-MIB::isisISAdjLastUpTime,TimeTicks,read-only,,current,,When the adjacency most recently entered the state 'up', measured in hundredths of a second since the last re-initialization of the network management subsystem. Holds 0 if the adjacency has never been in state 'up'.
.1.3.6.1.2.1.138.1.6.2,ISIS-MIB::isisISAdjAreaAddrTable,,not-accessible,,current,,This table contains the set of Area Addresses of neighboring Intermediate Systems as reported in received IIH PDUs.
.1.3.6.1.2.1.138.1.6.2.1,ISIS-MIB::isisISAdjAreaAddrEntry,,not-accessible,isisCircIndex:isisISAdjIndex:isisISAdjAreaAddrIndex,current,,Each entry contains one Area Address reported by a neighboring Intermediate System in its IIH PDUs. Dynamically learned rows do not survive an agent reboot.
.1.3.6.1.2.1.138.1.6.2.1.1,ISIS-MIB::isisISAdjAreaAddrIndex,Unsigned32,not-accessible,,current,,An index for the areas associated with one neighbor. This provides a simple way to walk the table.
.1.3.6.1.2.1.138.1.6.2.1.2,ISIS-MIB::isisISAdjAreaAddress,OCTET,read-only,,current,,One Area Address as reported in IIH PDUs received from the neighbor.
.1.3.6.1.2.1.138.1.6.3,ISIS-MIB::isisISAdjIPAddrTable,,not-accessible,,current,,This table contains the set of IP Addresses of neighboring Intermediate Systems as reported in received IIH PDUs.
.1.3.6.1.2.1.138.1.6.3.1,ISIS-MIB::isisISAdjIPAddrEntry,,not-accessible,isisCircIndex:isisISAdjIndex:isisISAdjIPAddrIndex,current,,Each entry contains one IP Address reported by a neighboring Intermediate System in its IIH PDUs. Dynamically learned rows do not survive an agent reboot.
.1.3.6.1.2.1.138.1.6.3.1.1,ISIS-MIB::isisISAdjIPAddrIndex,Unsigned32,not-accessible,,current,,An index to this table that identifies the IP addresses to which this entry belongs.
.1.3.6.1.2.1.138.1.6.3.1.2,ISIS-MIB::isisISAdjIPAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of one IP Address as reported in IIH PDUs received from the neighbor.
.1.3.6.1.2.1.138.1.6.3.1.3,ISIS-MIB::isisISAdjIPAddrAddress,OCTET,read-only,,current,,One IP Address as reported in IIH PDUs received from the neighbor. The type of this address is determined by the value of the isisISAdjIPAddrType object.
.1.3.6.1.2.1.138.1.6.4,ISIS-MIB::isisISAdjProtSuppTable,,not-accessible,,current,,This table contains the set of protocols supported by neighboring Intermediate Systems as reported in received IIH PDUs.
.1.3.6.1.2.1.138.1.6.4.1,ISIS-MIB::isisISAdjProtSuppEntry,,not-accessible,isisCircIndex:isisISAdjIndex:isisISAdjProtSuppProtocol,current,,Each entry contains one protocol supported by a neighboring Intermediate System as reported in its IIH PDUs. Dynamically learned rows do not survive an agent reboot.
.1.3.6.1.2.1.138.1.6.4.1.1,ISIS-MIB::isisISAdjProtSuppProtocol,INTEGER,read-only,,current,iso8473(129):ipV6(142):ip(204),One supported protocol as reported in IIH PDUs received from the neighbor.
.1.3.6.1.2.1.138.1.7,ISIS-MIB::isisReachAddr,,,,,,
.1.3.6.1.2.1.138.1.7.1,ISIS-MIB::isisRATable,,not-accessible,,current,,The table of Reachable Addresses to NSAPs or Address Prefixes.
.1.3.6.1.2.1.138.1.7.1.1,ISIS-MIB::isisRAEntry,,not-accessible,isisCircIndex:isisRAIndex,current,,Each entry defines a configured Reachable Address to an NSAP or Address Prefix. Dynamically created rows MUST survive an agent reboot.
.1.3.6.1.2.1.138.1.7.1.1.1,ISIS-MIB::isisRAIndex,Unsigned32,not-accessible,,current,,The identifier for this isisRAEntry. This value must be unique amongst all Reachable Addresses on the same parent Circuit.
.1.3.6.1.2.1.138.1.7.1.1.2,ISIS-MIB::isisRAExistState,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The existence state of this Reachable Address. This object follows the ManualOrAutomatic behaviors. Support for 'createAndWait' and 'notInService' is not required. A row entry cannot be modified when the value of this object is 'active'.
.1.3.6.1.2.1.138.1.7.1.1.3,ISIS-MIB::isisRAAdminState,INTEGER,read-create,,current,on(1):off(2),The administrative state of the Reachable Address. This object follows the ManualOrAutomatic behaviors.
.1.3.6.1.2.1.138.1.7.1.1.4,ISIS-MIB::isisRAAddrPrefix,OCTET,read-create,,current,,The destination of this Reachable Address. This is an Address Prefix. This object follows the ReplaceOnlyWhileDisabled and ManualOrAutomatic behaviors.
.1.3.6.1.2.1.138.1.7.1.1.5,ISIS-MIB::isisRAMapType,INTEGER,read-create,,current,none(1):explicit(2):extractIDI(3):extractDSP(4),The type of mapping to be employed to ascertain the SNPA Address that should be used in forwarding PDUs for this Reachable Address prefix. This object follows the ManualOrAutomatic behavior. The following values of mapping type are defined: none: The mapping is null because the neighbor SNPA is implicit by nature of the subnetwork (e.g., a point-to-point linkage). explicit: The subnetwork addresses in the object isisRASNPAAddress are to be used. extractIDI: The SNPA is embedded in the IDI of the destination NSAP Address. The mapping algorithm extracts the SNPA to be used according to the format and encoding rules of ISO8473/Add2. This SNPA extraction algorithm can be used in conjunction with Reachable Address prefixes from the X.121, F.69, E.163, and E.164 addressing subdomains. extractDSP: All, or a suffix, of the SNPA is embedded in the DSP of the destination address. This SNPA extraction algorithm extracts the embedded subnetwork addressing information by performing a logical AND of the isisRASNPAMask object value with the destination address. The part of the SNPA extracted from the destination NSAP is appended to the isisRASNPAPrefix object value to form the next hop subnetwork addressing information.
.1.3.6.1.2.1.138.1.7.1.1.6,ISIS-MIB::isisRAMetric,Unsigned32,read-create,,current,,The metric value for reaching the specified prefix over this circuit. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.7.1.1.7,ISIS-MIB::isisRAMetricType,INTEGER,read-create,,current,internal(1):external(2),Indicates whether the metric is internal or external. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.7.1.1.8,ISIS-MIB::isisRASNPAAddress,OCTET,read-create,,current,,The SNPA Address to which a PDU may be forwarded in order to reach a destination that matches the address prefix of the Reachable Address. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.7.1.1.9,ISIS-MIB::isisRASNPAMask,OCTET,read-create,,current,,A bit mask with 1 bit indicating the positions in the effective destination address from which embedded SNPA information is to be extracted. For the extraction, the first octet of the isisRASNPAMask object value is aligned with the first octet (AFI) of the NSAP Address. If the isisRASNPAMask object value and NSAP Address are of different lengths, the shorter of the two is logically padded with zeros before performing the extraction. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.7.1.1.10,ISIS-MIB::isisRASNPAPrefix,OCTET,read-create,,current,,A fixed SNPA prefix for use when the isisRAMapType is extractDSP. The SNPA Address to use is formed by concatenating the fixed SNPA prefix with a variable SNPA part that is extracted from the effective destination address. For Reachable Address prefixes in which the entire SNPA is embedded in the DSP, the SNPA Prefix shall be null. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.7.1.1.11,ISIS-MIB::isisRAType,INTEGER,read-create,,current,manual(1):automatic(2),The type of Reachable address. Those of type manual are created by the network manager. Those of type automatic are created through propagation of routing information from another routing protocol (e.g., IDRP). 
.1.3.6.1.2.1.138.1.8,ISIS-MIB::isisIPReachAddr,,,,,,
.1.3.6.1.2.1.138.1.8.1,ISIS-MIB::isisIPRATable,,not-accessible,,current,,The table of IP Reachable Addresses to networks, subnetworks, or hosts either manually configured or learned from another protocol.
.1.3.6.1.2.1.138.1.8.1.1,ISIS-MIB::isisIPRAEntry,,not-accessible,isisSysLevelIndex:isisIPRADestType:isisIPRADest:isisIPRADestPrefixLen:isisIPRANextHopIndex,current,,Each entry defines an IP Reachable Address to a network, subnetwork, or host. Each IP Reachable Address may have multiple entries in the table, one for each equal cost path to the reachable address. Dynamically created rows MUST survive an agent reboot. Implementers need to be aware that if the total number of elements (octets or sub-identifiers) in isisIPRADestr, isisIPRADestPrefixLen, and isisIPRANextHopIndex is too great, then OIDs of column instances in this table will have more than 128 subidentifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.138.1.8.1.1.1,ISIS-MIB::isisIPRADestType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of this IP Reachable Address.
.1.3.6.1.2.1.138.1.8.1.1.2,ISIS-MIB::isisIPRADest,OCTET,not-accessible,,current,,The destination of this IP Reachable Address. This is a network address, subnetwork address, or host address. The type of this address is determined by the value of the isisIPRADestType object.
.1.3.6.1.2.1.138.1.8.1.1.3,ISIS-MIB::isisIPRADestPrefixLen,Unsigned32,not-accessible,,current,,The length of the IP Netmask for Reachability Address. The values for the index objects isisIPRADest and isisIPRADestPrefixLen must be consistent. When the value of isisIPRADest (excluding the zone index, if one is present) is x, then the bitwise logical-AND of x with the value of the mask formed from the corresponding index object isisIPRADestPrefixLen MUST be equal to x. If not, then the index pair is not consistent, and an inconsistentName error must be returned on SET or CREATE requests.
.1.3.6.1.2.1.138.1.8.1.1.4,ISIS-MIB::isisIPRANextHopIndex,Unsigned32,not-accessible,,current,,Index of next hop. Used when there are multiple Equal Cost Multipath alternatives for the same destination.
.1.3.6.1.2.1.138.1.8.1.1.5,ISIS-MIB::isisIPRANextHopType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the IP next hop address.
.1.3.6.1.2.1.138.1.8.1.1.6,ISIS-MIB::isisIPRANextHop,OCTET,read-create,,current,,The IP next hop to this destination. The type of this address is determined by the value of the isisIPRANextHopType object.
.1.3.6.1.2.1.138.1.8.1.1.7,ISIS-MIB::isisIPRAType,INTEGER,read-create,,current,manual(1):automatic(2),The type of this IP Reachable Address. Those of type manual are created by the network manager. Those of type automatic are created through propagation of routing information from another routing protocol. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.8.1.1.8,ISIS-MIB::isisIPRAExistState,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The state of this IP Reachable Address. This object follows the ExistenceState and ManualOrAutomatic behaviors. Support for 'createAndWait' and 'notInService' is not required. A row entry cannot be modified when the value of this object is 'active'.
.1.3.6.1.2.1.138.1.8.1.1.9,ISIS-MIB::isisIPRAAdminState,INTEGER,read-create,,current,on(1):off(2),The administrative state of the IP Reachable Address. This object follows the IsisAdminState and ManualOrAutomatic behaviors.
.1.3.6.1.2.1.138.1.8.1.1.10,ISIS-MIB::isisIPRAMetric,Unsigned32,read-create,,current,,The metric value for reaching the specified destination over this circuit. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.8.1.1.11,ISIS-MIB::isisIPRAMetricType,INTEGER,read-create,,current,internal(1):external(2),Indicates whether the metric is internal or external. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.8.1.1.12,ISIS-MIB::isisIPRAFullMetric,Unsigned32,read-create,,current,,The wide metric value for reaching the specified destination over this circuit. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.8.1.1.13,ISIS-MIB::isisIPRASNPAAddress,OCTET,read-create,,current,,The SNPA Address to which a PDU may be forwarded in order to reach a destination that matches this IP Reachable Address. This object follows the ManualOrAutomatic behavior.
.1.3.6.1.2.1.138.1.8.1.1.14,ISIS-MIB::isisIPRASourceType,INTEGER,read-only,,current,static(1):direct(2):ospfv2(3):ospfv3(4):isis(5):rip(6):igrp(7):eigrp(8):bgp(9):other(10),The origin of this route.
.1.3.6.1.2.1.138.1.9,ISIS-MIB::isisLSPDataBase,,,,,,
.1.3.6.1.2.1.138.1.9.1,ISIS-MIB::isisLSPSummaryTable,,not-accessible,,current,,The table of LSP Headers.
.1.3.6.1.2.1.138.1.9.1.1,ISIS-MIB::isisLSPSummaryEntry,,not-accessible,isisLSPLevel:isisLSPID,current,,Each entry provides a summary describing an LSP currently stored in the system. Dynamically learned rows will not survive an agent reboot.
.1.3.6.1.2.1.138.1.9.1.1.1,ISIS-MIB::isisLSPLevel,INTEGER,not-accessible,,current,area(1):domain(2),At which level does this LSP appear?
.1.3.6.1.2.1.138.1.9.1.1.2,ISIS-MIB::isisLSPID,OCTET,not-accessible,,current,,The 8-byte LSP ID for this Link State PDU.
.1.3.6.1.2.1.138.1.9.1.1.3,ISIS-MIB::isisLSPSeq,Unsigned32,read-only,,current,,The sequence number for this LSP.
.1.3.6.1.2.1.138.1.9.1.1.4,ISIS-MIB::isisLSPZeroLife,INTEGER,read-only,,current,true(1):false(2),Is this LSP being purged by this system?
.1.3.6.1.2.1.138.1.9.1.1.5,ISIS-MIB::isisLSPChecksum,Unsigned32,read-only,,current,,The 16-bit Fletcher Checksum for this LSP.
.1.3.6.1.2.1.138.1.9.1.1.6,ISIS-MIB::isisLSPLifetimeRemain,Unsigned32,read-only,,current,,The remaining lifetime, in seconds, for this LSP.
.1.3.6.1.2.1.138.1.9.1.1.7,ISIS-MIB::isisLSPPDULength,Unsigned32,read-only,,current,,The length of this LSP.
.1.3.6.1.2.1.138.1.9.1.1.8,ISIS-MIB::isisLSPAttributes,Unsigned32,read-only,,current,,Flags carried by the LSP.
.1.3.6.1.2.1.138.1.9.2,ISIS-MIB::isisLSPTLVTable,,not-accessible,,current,,The table of LSPs in the database.
.1.3.6.1.2.1.138.1.9.2.1,ISIS-MIB::isisLSPTLVEntry,,not-accessible,isisLSPLevel:isisLSPID:isisLSPTLVIndex,current,,Each entry describes a TLV within an LSP currently stored in the system. Dynamically learned rows will not survive an agent reboot.
.1.3.6.1.2.1.138.1.9.2.1.1,ISIS-MIB::isisLSPTLVIndex,Unsigned32,not-accessible,,current,,The index of this TLV in the LSP. The first TLV has index 1, and the Nth TLV has an index of N.
.1.3.6.1.2.1.138.1.9.2.1.2,ISIS-MIB::isisLSPTLVSeq,Unsigned32,read-only,,current,,The sequence number for this LSP.
.1.3.6.1.2.1.138.1.9.2.1.3,ISIS-MIB::isisLSPTLVChecksum,Unsigned32,read-only,,current,,The 16-bit Fletcher Checksum for this LSP.
.1.3.6.1.2.1.138.1.9.2.1.4,ISIS-MIB::isisLSPTLVType,Unsigned32,read-only,,current,,The type of this TLV.
.1.3.6.1.2.1.138.1.9.2.1.5,ISIS-MIB::isisLSPTLVLen,Unsigned32,read-only,,current,,The length of this TLV.
.1.3.6.1.2.1.138.1.9.2.1.6,ISIS-MIB::isisLSPTLVValue,OCTET,read-only,,current,,The value of this TLV.
.1.3.6.1.2.1.138.1.10,ISIS-MIB::isisNotification,,,,,,
.1.3.6.1.2.1.138.1.10.1,ISIS-MIB::isisNotificationEntry,,,,,,
.1.3.6.1.2.1.138.1.10.1.1,ISIS-MIB::isisNotificationSysLevelIndex,INTEGER,accessible-for-notify,,current,level1(1):level2(2):level1and2(3),The system level for this notification.
.1.3.6.1.2.1.138.1.10.1.2,ISIS-MIB::isisNotificationCircIfIndex,Unsigned32,accessible-for-notify,,current,,The identifier of this circuit relevant to this notification.
.1.3.6.1.2.1.138.1.10.1.3,ISIS-MIB::isisPduLspId,OCTET,accessible-for-notify,,current,,An Octet String that uniquely identifies a Link State PDU.
.1.3.6.1.2.1.138.1.10.1.4,ISIS-MIB::isisPduFragment,OCTET,accessible-for-notify,,current,,Holds up to 64 initial bytes of a PDU that triggered the notification.
.1.3.6.1.2.1.138.1.10.1.5,ISIS-MIB::isisPduFieldLen,Unsigned32,accessible-for-notify,,current,,Holds the System ID length reported in PDU we received.
.1.3.6.1.2.1.138.1.10.1.6,ISIS-MIB::isisPduMaxAreaAddress,Unsigned32,accessible-for-notify,,current,,Holds the Max Area Addresses reported in a PDU we received.
.1.3.6.1.2.1.138.1.10.1.7,ISIS-MIB::isisPduProtocolVersion,Unsigned32,accessible-for-notify,,current,,Holds the Protocol version reported in PDU we received.
.1.3.6.1.2.1.138.1.10.1.8,ISIS-MIB::isisPduLspSize,Unsigned32,accessible-for-notify,,current,,Holds the size of LSP we received that is too big to forward.
.1.3.6.1.2.1.138.1.10.1.9,ISIS-MIB::isisPduOriginatingBufferSize,Unsigned32,accessible-for-notify,,current,,Holds the size of isisSysLevelOrigLSPBuffSize advertised by the peer in the originatingLSPBufferSize TLV. If the peer does not advertise this TLV, this value is set to 0.
.1.3.6.1.2.1.138.1.10.1.10,ISIS-MIB::isisPduBufferSize,Unsigned32,accessible-for-notify,,current,,Holds the size of LSP received from peer.
.1.3.6.1.2.1.138.1.10.1.11,ISIS-MIB::isisPduProtocolsSupported,OCTET,accessible-for-notify,,current,,The list of protocols supported by an adjacent system. This may be empty.
.1.3.6.1.2.1.138.1.10.1.12,ISIS-MIB::isisAdjState,INTEGER,accessible-for-notify,,current,down(1):initializing(2):up(3):failed(4),The current state of an adjacency.
.1.3.6.1.2.1.138.1.10.1.13,ISIS-MIB::isisErrorOffset,Unsigned32,accessible-for-notify,,current,,An offset to a problem in a PDU. If the problem is a malformed TLV, this points to the beginning of the TLV. If the problem is in the header, this points to the byte that is suspicious.
.1.3.6.1.2.1.138.1.10.1.14,ISIS-MIB::isisErrorTLVType,Unsigned32,accessible-for-notify,,current,,The type for a malformed TLV.
.1.3.6.1.2.1.138.1.10.1.15,ISIS-MIB::isisNotificationAreaAddress,OCTET,accessible-for-notify,,current,,An Area Address.
.1.3.6.1.2.1.138.2,ISIS-MIB::isisConformance,,,,,,
.1.3.6.1.2.1.138.2.1,ISIS-MIB::isisCompliances,,,,,,
.1.3.6.1.2.1.138.2.1.1,ISIS-MIB::isisCompliance,,,,,,The compliance statement for agents that support the IS-IS MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements. Those requirements and similar requirements for related objects are expressed below, in pseudo-OBJECT clause form, in this description: -- OBJECT isisSummAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- -- DESCRIPTION -- The MIB requires support for IPv4 Summary -- Addresses and anticipates the support of -- IPv6 addresses. -- -- -- OBJECT isisRedistributeAddrType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- -- DESCRIPTION -- The MIB requires support for IPv4 -- Redistribution Addresses and anticipates -- the support of IPv6 addresses.
.1.3.6.1.2.1.138.2.1.2,ISIS-MIB::isisAdvancedCompliance,,,,,,The compliance statement for agents that fully support the IS-IS MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements. Those requirements and similar requirements for related objects are expressed below, in pseudo-OBJECT clause form, in this description: -- OBJECT isisSummAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- -- DESCRIPTION -- The MIB requires support for IPv4 Summary -- Addresses and anticipates the support of -- IPv6 addresses. -- -- -- OBJECT isisRedistributeAddrType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- -- DESCRIPTION -- The MIB requires support for IPv4 -- Redistribution Addresses and anticipates -- the support of IPv6 addresses.
.1.3.6.1.2.1.138.2.1.3,ISIS-MIB::isisReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-create (i.e., in read-only mode), the implementation can claim read-only compliance. Such a device can then be monitored but cannot be configured with this MIB.
.1.3.6.1.2.1.138.2.2,ISIS-MIB::isisGroups,,,,,,
.1.3.6.1.2.1.138.2.2.1,ISIS-MIB::isisSystemGroup,,,,,,The collections of objects used to manage an IS-IS router.
.1.3.6.1.2.1.138.2.2.2,ISIS-MIB::isisCircuitGroup,,,,,,The collections of objects used to describe an IS-IS Circuit.
.1.3.6.1.2.1.138.2.2.3,ISIS-MIB::isisISAdjGroup,,,,,,The collections of objects used to manage an IS-IS Adjacency.
.1.3.6.1.2.1.138.2.2.4,ISIS-MIB::isisNotificationObjectGroup,,,,,,The objects used to record notification parameters.
.1.3.6.1.2.1.138.2.2.5,ISIS-MIB::isisNotificationGroup,,,,,,The collections of notifications sent by an IS.
.1.3.6.1.2.1.138.2.2.6,ISIS-MIB::isisISPDUCounterGroup,,,,,,The collections of objects used to count protocol PDUs.
.1.3.6.1.2.1.138.2.2.7,ISIS-MIB::isisRATableGroup,,,,,,The collections of objects used to manage the reachable NSAP prefixes.
.1.3.6.1.2.1.138.2.2.8,ISIS-MIB::isisISIPRADestGroup,,,,,,The collections of objects used to manage configured IP addresses.
.1.3.6.1.2.1.138.2.2.9,ISIS-MIB::isisLSPGroup,,,,,,The collections of objects used to observe the LSP Database.
.1.3.6.1.2.1.139,SCSI-MIB::scsiMIB,,,,,,The SCSI MIB Module. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4455; see the RFC itself for full legal notices.
.1.3.6.1.2.1.139.0,SCSI-MIB::scsiNotifications,,,,,,
.1.3.6.1.2.1.139.0.0,SCSI-MIB::scsiNotificationsPrefix,,,,,,
.1.3.6.1.2.1.139.0.0.1,SCSI-MIB::scsiTgtDeviceStatusChanged,,,,,,This notification will be generated for each occurrence of the abnormal status (e.g., if the SCSI target device's current status is abnormal) providing that the SCSI instance's value of scsiInstScsiNotificationsEnable is enabled. An SNMP agent implementing the SCSI MIB module should not send more than three SCSI identical notifications in any 10-second period.
.1.3.6.1.2.1.139.0.0.2,SCSI-MIB::scsiLuStatusChanged,,,,,,This notification will be generated each time that scsiLuStatus changes providing that the SCSI instance's value of scsiInstScsiNotificationsEnable is enabled. An SNMP agent implementing the SCSI MIB module should not send more than three SCSI identical notifications in any 10-second period.
.1.3.6.1.2.1.139.1,SCSI-MIB::scsiAdmin,,,,,,
.1.3.6.1.2.1.139.1.1,SCSI-MIB::scsiTransportTypes,,,,,,
.1.3.6.1.2.1.139.1.1.1,SCSI-MIB::scsiTransportOther,,,,,,This identity identifies a transport that has no identity; it might happen because the transport is unknown or might not have been defined when this MIB module was created.
.1.3.6.1.2.1.139.1.1.2,SCSI-MIB::scsiTransportSPI,,,,,,This identity identifies a parallel SCSI transport.
.1.3.6.1.2.1.139.1.1.3,SCSI-MIB::scsiTransportFCP,,,,,,This identity identifies a Fibre Channel Protocol for SCSI, Second Version.
.1.3.6.1.2.1.139.1.1.4,SCSI-MIB::scsiTransportSRP,,,,,,This identity identifies a protocol for transporting SCSI over Remote Direct Memory Access (RDMA) interfaces, e.g., InfiniBand (tm).
.1.3.6.1.2.1.139.1.1.5,SCSI-MIB::scsiTransportISCSI,,,,,,This identity identifies an iSCSI transport.
.1.3.6.1.2.1.139.1.1.6,SCSI-MIB::scsiTransportSBP,,,,,,This identity identifies the Serial Bus Protocol 3.
.1.3.6.1.2.1.139.1.1.7,SCSI-MIB::scsiTransportSAS,,,,,,This identity identifies the Serial Attach SCSI Protocol.
.1.3.6.1.2.1.139.2,SCSI-MIB::scsiObjects,,,,,,
.1.3.6.1.2.1.139.2.1,SCSI-MIB::scsiGeneral,,,,,,
.1.3.6.1.2.1.139.2.1.1,SCSI-MIB::scsiInstanceTable,,not-accessible,,current,,A list of SCSI instances present on the system. The SCSI instance is the top-level entity, to which everything else belongs. An SNMP agent could represent more than one instance if it represents either a stack of devices, or virtual partitions of a larger device, or a host running multiple SCSI implementations from different vendors.
.1.3.6.1.2.1.139.2.1.1.1,SCSI-MIB::scsiInstanceEntry,,not-accessible,scsiInstIndex,current,,An entry (row) containing management information applicable to a particular SCSI instance.
.1.3.6.1.2.1.139.2.1.1.1.1,SCSI-MIB::scsiInstIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary integer used to uniquely identify a particular SCSI instance.
.1.3.6.1.2.1.139.2.1.1.1.2,SCSI-MIB::scsiInstAlias,OCTET,read-write,,current,,This object represents an administrative string, configured by the administrator. It can be a zero-length string.
.1.3.6.1.2.1.139.2.1.1.1.3,SCSI-MIB::scsiInstSoftwareIndex,Integer32,read-only,,current,,If this management instance corresponds to an installed software module, then this object's value is the value of the hrSWInstalledIndex of that module. If there is no correspondence to an installed software module (or no module that has an hrSWInstalledIndex value), then the value of this object is zero.
.1.3.6.1.2.1.139.2.1.1.1.4,SCSI-MIB::scsiInstVendorVersion,OCTET,read-only,,current,,This object represents a text string set by the manufacturer describing the version of this instance. The format of this string is determined solely by the manufacturer and is for informational purposes only. It is unrelated to the SCSI specification version numbers.
.1.3.6.1.2.1.139.2.1.1.1.5,SCSI-MIB::scsiInstScsiNotificationsEnable,INTEGER,read-write,,current,true(1):false(2),This object indicates whether notifications defined in this MIB module will be generated.
.1.3.6.1.2.1.139.2.1.1.1.6,SCSI-MIB::scsiInstStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization for this SCSI entity. Specifically, each row in the following tables: scsiIntrDevTable scsiDscTgtTable scsiAuthorizedIntrTable scsiLunMapTable has a StorageType as specified by the instance of this object that is INDEXed by the same value of scsiInstIndex. This value of this object is also used to indicate the persistence across reboots of writable values in its row of the scsiInstanceTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row, nor to any object belonging to a table whose entry is INDEXed by the same value of scsiInstIndex.
.1.3.6.1.2.1.139.2.1.2,SCSI-MIB::scsiDeviceTable,,not-accessible,,current,,A list of SCSI devices contained in each of the SCSI manageable instances that this agent is reporting.
.1.3.6.1.2.1.139.2.1.2.1,SCSI-MIB::scsiDeviceEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex,current,,An entry (row) containing management information applicable to a particular SCSI device included in this SCSI manageable instance identifiable by the value of scsiInstIndex.
.1.3.6.1.2.1.139.2.1.2.1.1,SCSI-MIB::scsiDeviceIndex,Unsigned32,not-accessible,,current,,This object is an arbitrary integer used to uniquely identify a particular device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.1.2.1.2,SCSI-MIB::scsiDeviceAlias,OCTET,read-write,,current,,This object contains an administrative name for this device. If no name is assigned, the value of this object is the zero-length string. The StorageType of this object is specified by the instance of scsiInstStorageType that is INDEXed by the same value of scsiInstIndex.
.1.3.6.1.2.1.139.2.1.2.1.3,SCSI-MIB::scsiDeviceRole,BITS,read-only,,current,target(0):initiator(1),This object determines whether this device is acting as a SCSI initiator device, or as a SCSI target device, or as both.
.1.3.6.1.2.1.139.2.1.2.1.4,SCSI-MIB::scsiDevicePortNumber,Unsigned32,read-only,,current,,This object represents the number of ports contained in this device.
.1.3.6.1.2.1.139.2.1.3,SCSI-MIB::scsiPortTable,,not-accessible,,current,,A list of SCSI ports for each SCSI device in each instance.
.1.3.6.1.2.1.139.2.1.3.1,SCSI-MIB::scsiPortEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiPortIndex,current,,An entry (row) containing management information applicable to a particular SCSI port of a particular SCSI device in a particular SCSI instance.
.1.3.6.1.2.1.139.2.1.3.1.1,SCSI-MIB::scsiPortIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular port of a given device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.1.3.1.2,SCSI-MIB::scsiPortRole,BITS,read-only,,current,target(0):initiator(1),This object indicates whether this port is acting as a SCSI initiator port, or as a SCSI target port or as both.
.1.3.6.1.2.1.139.2.1.3.1.3,SCSI-MIB::scsiPortTransportPtr,OBJECT,read-only,,current,,This object is a pointer to the corresponding row in the scsiTransportTable. This row contains information on the transport such as transport type and port name.
.1.3.6.1.2.1.139.2.1.3.1.4,SCSI-MIB::scsiPortBusyStatuses,Counter32,read-only,,current,,This object represents the number of port busy statuses sent or received by this port. Note: Initiator ports only receive busy status and SCSI target ports only send busy status. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.1.5,SCSI-MIB::scsiTransportTable,,not-accessible,,current,,This table contains the device transport-specific information for each transport connected to each device in scsiDeviceTable.
.1.3.6.1.2.1.139.2.1.5.1,SCSI-MIB::scsiTransportEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiTransportIndex,current,,An entry (row) containing parameters applicable to a transport used by a particular device of a particular SCSI manageable instance.
.1.3.6.1.2.1.139.2.1.5.1.1,SCSI-MIB::scsiTransportIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular transport within a given device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.1.5.1.2,SCSI-MIB::scsiTransportType,OBJECT,read-only,,current,,This object identifies the transport type of this row of the transport table. For example, if this object has the value scsiTransportFCP, then the identified transport is FCP.
.1.3.6.1.2.1.139.2.1.5.1.3,SCSI-MIB::scsiTransportPointer,OBJECT,read-only,,current,,This object represents a pointer to a conceptual row in a 'transport' MIB module allowing a manager to get useful information for the transport described by this entry. For example, if the transport of this device is iSCSI, this object will point to the iSCSI Instance of the iSCSI MIB module. If there is no MIB for this transport, this object has the value 0.0.
.1.3.6.1.2.1.139.2.1.5.1.4,SCSI-MIB::scsiTransportDevName,OCTET,read-only,,current,,This object represents the name of this device in one of the format(s) appropriate for this type of transport.
.1.3.6.1.2.1.139.2.2,SCSI-MIB::scsiInitiatorDevice,,,,,,
.1.3.6.1.2.1.139.2.2.1,SCSI-MIB::scsiIntrDevTable,,not-accessible,,current,,This table contains information for each local SCSI initiator device in each instance.
.1.3.6.1.2.1.139.2.2.1.1,SCSI-MIB::scsiIntrDevEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex,current,,An entry (row) containing information applicable to a SCSI initiator device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.2.1.1.1,SCSI-MIB::scsiIntrDevTgtAccessMode,INTEGER,read-write,,current,unknown(1):autoEnable(2):manualEnable(3),This object controls whether or not a discovered SCSI target device is immediately authorized: - autoEnable (2) means that when a SCSI initiator device discovers a SCSI target device, it can use it immediately. - manualEnable (3) means that the SCSI initiator device must wait for an operator to set scsiIntrDscTgtConfigured = true before it is authorized. The StorageType of this object is specified by the instance of scsiInstStorageType that is INDEXed by the same value of scsiInstIndex.
.1.3.6.1.2.1.139.2.2.1.1.2,SCSI-MIB::scsiIntrDevOutResets,Counter32,read-only,,current,,This object represents the total number of times that this SCSI initiator device has issued - a LOGICAL UNIT RESET or TARGET RESET task management request, or - any other SCSI transport protocol-specific action or event that causes a Logical Unit Reset or a Hard Reset at one or more SCSI target ports ([SAM2] chapters 5.9.6, 5.9.7). Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.2.2,SCSI-MIB::scsiIntrPortTable,,not-accessible,,current,,This table contains all the SCSI initiator ports for each local SCSI initiator or target/initiator devices in each SCSI instance.
.1.3.6.1.2.1.139.2.2.2.1,SCSI-MIB::scsiIntrPortEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiPortIndex,current,,An entry (row) containing information applicable to a particular SCSI initiator port of a particular SCSI device within a SCSI instance.
.1.3.6.1.2.1.139.2.2.2.1.1,SCSI-MIB::scsiIntrPortName,OCTET,read-only,,current,,This object represents the name of the port assigned for use by the SCSI protocol. The format will depend on the type of transport this port is using.
.1.3.6.1.2.1.139.2.2.2.1.2,SCSI-MIB::scsiIntrPortIdentifier,OCTET,read-only,,current,,This object represents the identifier of the port in one of the format(s) appropriate for the type of transport in use.
.1.3.6.1.2.1.139.2.2.2.1.3,SCSI-MIB::scsiIntrPortOutCommands,Counter32,read-only,,current,,This object represents the number of commands sent by this SCSI initiator port. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.2.2.1.4,SCSI-MIB::scsiIntrPortWrittenMegaBytes,Counter32,read-only,,current,,This object represents the amount of data in megabytes sent by this SCSI initiator port. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.2.2.1.5,SCSI-MIB::scsiIntrPortReadMegaBytes,Counter32,read-only,,current,,This object represents the amount of data in megabytes received by this SCSI initiator port. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.2.2.1.6,SCSI-MIB::scsiIntrPortHSOutCommands,Counter64,read-only,,current,,This object represents the number of commands sent by this SCSI initiator port. This object provides support for systems that can quickly generate a large number of commands because they run at high speed. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.2.3,SCSI-MIB::scsiRemoteTgtDev,,,,,,
.1.3.6.1.2.1.139.2.2.3.1,SCSI-MIB::scsiDscTgtTable,,not-accessible,,current,,This table includes all the remote (not in the local system) SCSI target ports that are authorized to attach to each local SCSI initiator port of this SCSI instance.
.1.3.6.1.2.1.139.2.2.3.1.1,SCSI-MIB::scsiDscTgtEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiDscTgtIntrPortIndex:scsiDscTgtIndex,current,,Each entry (row) contains information about the SCSI target device or port to which this SCSI initiator port (or all SCSI initiator ports in the SCSI initiator entry indexed by scsiInstIndex, scsiDeviceIndex) will attempt to attach. The entry is either for all local ports (if scsiDscTgtIntrPortIndex is zero) or only for the specific SCSI initiator port identified by scsiDscTgtIntrPortIndex. Note that if an entry in this table is deleted, any corresponding entries in the scsiDscLunsTable must be deleted as well. The StorageType of a row in this table is specified by the instance of scsiInstStorageType that is INDEXed by the same value of scsiInstIndex.
.1.3.6.1.2.1.139.2.2.3.1.1.1,SCSI-MIB::scsiDscTgtIntrPortIndex,Unsigned32,not-accessible,,current,,This object relates to a particular local device within a particular SCSI instance and specifies - the index of the local SCSI initiator port, - or zero, if this entry refers to the local device and therefore refers to all the local SCSI initiator ports.
.1.3.6.1.2.1.139.2.2.3.1.1.2,SCSI-MIB::scsiDscTgtIndex,Unsigned32,not-accessible,,current,,This object is an arbitrary integer used to uniquely identify a particular SCSI target device either discovered by, or configured for use with, one or more ports scsiDscTgtName of a particular device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.2.3.1.1.3,SCSI-MIB::scsiDscTgtDevOrPort,INTEGER,read-create,,current,device(1):port(2):other(3),This object indicates whether this entry describes a configured SCSI target device name (and applies to all ports on the identified SCSI target device) or an individual SCSI target port.
.1.3.6.1.2.1.139.2.2.3.1.1.4,SCSI-MIB::scsiDscTgtName,OCTET,read-create,,current,,This object represents the name of this configured or discovered SCSI target device or port depending on the value of scsiDscTgtDevOrPort.
.1.3.6.1.2.1.139.2.2.3.1.1.5,SCSI-MIB::scsiDscTgtConfigured,INTEGER,read-create,,current,true(1):false(2),This object means -true(1): this entry has been configured by an administrator. -false(2): this entry has been added from a discovery mechanism (e.g., SendTargets, SLP, iSNS). An administrator can modify this value from false to true.
.1.3.6.1.2.1.139.2.2.3.1.1.6,SCSI-MIB::scsiDscTgtDiscovered,INTEGER,read-only,,current,true(1):false(2),This object means -true(1): this entry has been discovered by the SCSI instance as result of an automatic discovery process. -false(2):this entry has been added by manual configuration. This entry is read-only because an administrator cannot change it. Note that it is an implementation decision to determine how long to retain a row with configured=false, such as when the SCSI target device is no longer visible/accessible to the local SCSI initiator device.
.1.3.6.1.2.1.139.2.2.3.1.1.7,SCSI-MIB::scsiDscTgtInCommands,Counter32,read-only,,current,,This object represents the number of commands received from this SCSI target port or device. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiDscTgtLastCreation.
.1.3.6.1.2.1.139.2.2.3.1.1.8,SCSI-MIB::scsiDscTgtWrittenMegaBytes,Counter32,read-only,,current,,This object represents the amount of megabytes of data sent as the result of WRITE commands to this SCSI target port or device. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiDscTgtLastCreation.
.1.3.6.1.2.1.139.2.2.3.1.1.9,SCSI-MIB::scsiDscTgtReadMegaBytes,Counter32,read-only,,current,,This object represents the amount of megabytes received as the result of READ commands to this SCSI target port or device. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiDscTgtLastCreation.
.1.3.6.1.2.1.139.2.2.3.1.1.10,SCSI-MIB::scsiDscTgtHSInCommands,Counter64,read-only,,current,,This object represents the number of commands received by this SCSI target port or device. This object provides support for system that can quickly generate a large number of commands because they run at high speed. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiDscTgtLastCreation.
.1.3.6.1.2.1.139.2.2.3.1.1.11,SCSI-MIB::scsiDscTgtLastCreation,TimeTicks,read-only,,current,,This object represents the value of sysUpTime when this row was created.
.1.3.6.1.2.1.139.2.2.3.1.1.12,SCSI-MIB::scsiDscTgtRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows an administrator to configure dynamically a new entry in this table via SNMP or eventually delete it. An administrator is not allowed to delete an entry for which the value of the object scsiIntrDscTgtDiscovered is equal to true. Note that when an entry in this table is deleted, then any corresponding entries in the scsiDscLunsTable must also be automatically deleted. A newly created row cannot be made active until a value has been set for scsiDscTgtName. In this case, the value of the corresponding instance of the scsiDscTgtRowStatus column will stay 'notReady'. The RowStatus TC [RFC2579] requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified: The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.139.2.2.3.2,SCSI-MIB::scsiDscLunTable,,not-accessible,,current,,This table includes all the remote (not in the local system) logical unit numbers (LUNs) discovered via each local SCSI initiator port of each local device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.2.3.2.1,SCSI-MIB::scsiDscLunEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiDscTgtIntrPortIndex:scsiDscTgtIndex:scsiDscLunIndex,current,,An entry (row) represents a discovered LUN at a particular SCSI target device (scsiDscTgtIndex), where the LUN was discovered by a particular local SCSI initiator device within a particular SCSI instance, possibly via a particular local SCSI initiator port. Note that when an entry in the scsiDscTgtTable is deleted, all corresponding entries in this table should automatically be deleted.
.1.3.6.1.2.1.139.2.2.3.2.1.1,SCSI-MIB::scsiDscLunIndex,Unsigned32,not-accessible,,current,,This object is an arbitrary integer used to uniquely identify a particular LUN discovered by a particular SCSI initiator port or a particular SCSI initiator device within a particular SCSI instance. Entries in the scsiDscLunIdTable are associated with a LUN by having the value of this object in their INDEX.
.1.3.6.1.2.1.139.2.2.3.2.1.2,SCSI-MIB::scsiDscLunLun,OCTET,read-only,,current,,This object contains the Logical Unit Number (LUN) of the discovered logical unit.
.1.3.6.1.2.1.139.2.2.3.3,SCSI-MIB::scsiDscLunIdTable,,not-accessible,,current,,This table includes all the known LU identifiers of the remote (not in the local system) logical units discovered via each local SCSI initiator port or device of this SCSI instance.
.1.3.6.1.2.1.139.2.2.3.3.1,SCSI-MIB::scsiDscLunIdEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiDscTgtIntrPortIndex:scsiDscTgtIndex:scsiDscLunIndex:scsiDscLunIdIndex,current,,An entry (row) represents the LU identifier of a discovered LUN at a particular SCSI target device (scsiDscTgtIndex), where the LUN was discovered by a particular local SCSI initiator device within a particular SCSI instance, possibly via a particular local SCSI initiator port.
.1.3.6.1.2.1.139.2.2.3.3.1.1,SCSI-MIB::scsiDscLunIdIndex,Unsigned32,not-accessible,,current,,This object is an arbitrary integer used to uniquely identify a particular LUN identifier discovered by each SCSI initiator device or particular SCSI initiator port within a particular SCSI instance.
.1.3.6.1.2.1.139.2.2.3.3.1.2,SCSI-MIB::scsiDscLunIdCodeSet,Unsigned32,read-only,,current,,This object specifies the code set in use with this identifier. The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.2.3.3.1.3,SCSI-MIB::scsiDscLunIdAssociation,Unsigned32,read-only,,current,,This object specifies what the identifier is associated with (e.g., with the addressed physical/logical device or with a particular port). The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.2.3.3.1.4,SCSI-MIB::scsiDscLunIdType,Unsigned32,read-only,,current,,This object specifies the type of the identifier. The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.2.3.3.1.5,SCSI-MIB::scsiDscLunIdValue,OCTET,read-only,,current,,This object represents the actual value of this identifier. The format is defined by the objects scsiDscLunIdCodeSet, scsiDscLunIdAssociation, scsiDscLunIdType. The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.2.3.4,SCSI-MIB::scsiAttTgtPortTable,,not-accessible,,current,,This table includes all the remote (not in the local system) SCSI target ports that are currently attached to each local SCSI initiator port of this SCSI instance.
.1.3.6.1.2.1.139.2.2.3.4.1,SCSI-MIB::scsiAttTgtPortEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiPortIndex:scsiAttTgtPortIndex,current,,An entry (row) represents a remote SCSI target port (scsiAttTgtPortIndex) currently attached to a particular SCSI initiator port (scsiPortIndex) of a particular SCSI initiator device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.2.3.4.1.1,SCSI-MIB::scsiAttTgtPortIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular SCSI target currently attached to a particular SCSI initiator port of a particular SCSI initiator device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.2.3.4.1.2,SCSI-MIB::scsiAttTgtPortDscTgtIdx,Unsigned32,read-only,,current,,This object contains the value of the scsiDscTgtIntrPortIndex index variable for the row in the scsiDscTgtTable representing this currently attached SCSI target port. If the currently attached SCSI target port is not represented in the scsiDscTgtTable, then the value of this object is zero.
.1.3.6.1.2.1.139.2.2.3.4.1.3,SCSI-MIB::scsiAttTgtPortName,OCTET,read-only,,current,,This object contains the name of the attached SCSI target port.
.1.3.6.1.2.1.139.2.2.3.4.1.4,SCSI-MIB::scsiAttTgtPortIdentifier,OCTET,read-only,,current,,This object contains the identifier of the attached SCSI target port.
.1.3.6.1.2.1.139.2.3,SCSI-MIB::scsiTargetDevice,,,,,,
.1.3.6.1.2.1.139.2.3.1,SCSI-MIB::scsiTgtDevTable,,not-accessible,,current,,This table contains information about each local SCSI target device.
.1.3.6.1.2.1.139.2.3.1.1,SCSI-MIB::scsiTgtDevEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex,current,,An entry (row) containing information applicable to a particular local SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.3.1.1.1,SCSI-MIB::scsiTgtDevNumberOfLUs,Gauge32,read-only,,current,,This object is the number of logical units accessible via this local SCSI target device.
.1.3.6.1.2.1.139.2.3.1.1.2,SCSI-MIB::scsiTgtDeviceStatus,INTEGER,read-only,,current,unknown(1):available(2):broken(3):readying(4):abnormal(5):nonAddrFailure(6):nonAddrFailReadying(7):nonAddrFailAbnormal(8),This object represents the status of this SCSI device, summarizing the state of both the addressable devices (i.e., the logical units) and the non-addressable devices within this SCSI device: - unknown(1): This value is used when the status cannot be determined - available(2): All addressable and non-addressable devices within the SCSI device are fully operational (i.e., no logical units have an abnormal status). - broken(3): The SCSI device is not operational and cannot be made operational without external intervention. - readying(4): One or more logical units within the SCSI device are being initialized and access to the SCSI device is temporarily limited (i.e., one or more of the logical units have a readying status). - abnormal(5): One or more addressable devices within the SCSI device are indicating a status other than available; nevertheless, the SCSI device is operational (i.e., one or more of the logical units have an abnormal status). - nonAddrFailure(6): One or more non-addressable devices within the SCSI device have failed; nevertheless, the SCSI device is operational (i.e., no logical units have an abnormal or readying status). - nonAddrFailReadying(7): One or more non-addressable devices within the SCSI device have failed; nevertheless, one or more logical units within the SCSI device are being initialized and access to the SCSI device is temporarily limited. - nonAddrFailAbnormal(8): One or more non-addressable devices within the SCSI device have failed and one or more addressable devices within the SCSI device are indicating a status other than available; however, the SCSI device is operational. 
.1.3.6.1.2.1.139.2.3.1.1.3,SCSI-MIB::scsiTgtDevNonAccessibleLUs,Gauge32,read-only,,current,,This object is the number of logical units existing but not currently accessible via this local SCSI target device.
.1.3.6.1.2.1.139.2.3.1.1.4,SCSI-MIB::scsiTgtDevResets,Counter32,read-only,,current,,This object counts the number of hard resets encountered by this SCSI target device. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.3.2,SCSI-MIB::scsiTgtPortTable,,not-accessible,,current,,This table includes all the local SCSI target ports of all the local SCSI target devices.
.1.3.6.1.2.1.139.2.3.2.1,SCSI-MIB::scsiTgtPortEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiPortIndex,current,,An entry (row) containing information applicable to a particular local SCSI target port of a particular local SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.3.2.1.1,SCSI-MIB::scsiTgtPortName,OCTET,read-only,,current,,This object represents the name of the port assigned for use in the SCSI protocol.
.1.3.6.1.2.1.139.2.3.2.1.2,SCSI-MIB::scsiTgtPortIdentifier,OCTET,read-only,,current,,This object represents the identifier of the port in one of the format(s) appropriate for the type of transport.
.1.3.6.1.2.1.139.2.3.2.1.3,SCSI-MIB::scsiTgtPortInCommands,Counter32,read-only,,current,,This object represents the number of commands received by this SCSI target port. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.3.2.1.4,SCSI-MIB::scsiTgtPortWrittenMegaBytes,Counter32,read-only,,current,,This object represents the amount of data written in megabytes by this SCSI target port. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.3.2.1.5,SCSI-MIB::scsiTgtPortReadMegaBytes,Counter32,read-only,,current,,This object represents the amount of data read in megabytes by this SCSI target port. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.3.2.1.6,SCSI-MIB::scsiTgtPortHSInCommands,Counter64,read-only,,current,,This object represents the number of commands received. This object provides support for systems that can quickly generate a large number of commands because they run at high speed. Discontinuities in the value of this counter can occur at re- initialization of the management system.
.1.3.6.1.2.1.139.2.3.3,SCSI-MIB::scsiRemoteIntrDev,,,,,,
.1.3.6.1.2.1.139.2.3.3.1,SCSI-MIB::scsiAuthorizedIntrTable,,not-accessible,,current,,This table includes all the authorized SCSI initiator devices or ports that may attach a SCSI target device (ScsiAuthIntrTgtPortIndex = 0) or port (ScsiAuthIntrTgtPortIndex different than 0) of the local SCSI instance. Statistics are kept for each such authorization; thus, the authorizations should be configured in the manner that will cause the desired set of statistics to be collected and that will determine the correct LUN map.
.1.3.6.1.2.1.139.2.3.3.1.1,SCSI-MIB::scsiAuthorizedIntrEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiAuthIntrTgtPortIndex:scsiAuthIntrIndex,current,,An entry (row) represents a remote SCSI initiator port or remote SCSI initiator device that may attach to the local SCSI target port or device within a particular SCSI instance. The StorageType of a row in this table is specified by the instance of scsiInstStorageType that is INDEXed by the same value of scsiInstIndex.
.1.3.6.1.2.1.139.2.3.3.1.1.1,SCSI-MIB::scsiAuthIntrTgtPortIndex,Unsigned32,not-accessible,,current,,This object contains either the index of the port or zero, to indicate any port, on the particular local SCSI target device.
.1.3.6.1.2.1.139.2.3.3.1.1.2,SCSI-MIB::scsiAuthIntrIndex,Unsigned32,not-accessible,,current,,This object is an arbitrary integer used to uniquely identify a SCSI initiator device or port that is authorized to attach to a particular local SCSI target device or port of a particular SCSI instance.
.1.3.6.1.2.1.139.2.3.3.1.1.3,SCSI-MIB::scsiAuthIntrDevOrPort,INTEGER,read-create,,current,device(1):port(2):other(3),This object specifies whether this entry refers to a remote SCSI initiator port or to a SCSI initiator device. A value of device(1) means that the authorized remote initiator is a SCSI initiator device and includes all of its ports. A value of port(2) means that the authorized remote initiator is a SCSI initiator port.
.1.3.6.1.2.1.139.2.3.3.1.1.4,SCSI-MIB::scsiAuthIntrName,OCTET,read-create,,current,,This object represents the name of the remote SCSI initiator device or port authorized by this row.
.1.3.6.1.2.1.139.2.3.3.1.1.5,SCSI-MIB::scsiAuthIntrLunMapIndex,Unsigned32,read-create,,current,,This object identifies the set of entries in the scsiLunMapTable for which scsiLunMapIndex has the same value as the value of this object. The identified set of entries constitutes the LUN map to be used for accessing logical units when the remote SCSI initiator port or device corresponding to this entry is attached to any local SCSI target port or device corresponding to this entry. Note that this object has a value of zero if this entry should use the default LUN map.
.1.3.6.1.2.1.139.2.3.3.1.1.6,SCSI-MIB::scsiAuthIntrAttachedTimes,Counter32,read-only,,current,,This object indicates the number of times that this remote SCSI initiator device or port has transitioned from unattached to attached to this local SCSI target device or port. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiAuthIntrLastCreation.
.1.3.6.1.2.1.139.2.3.3.1.1.7,SCSI-MIB::scsiAuthIntrOutCommands,Counter32,read-only,,current,,This object indicates the number of commands that the remote SCSI initiator device or port corresponding to this entry has sent to the local SCSI target device or port corresponding to this entry. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiAuthIntrLastCreation.
.1.3.6.1.2.1.139.2.3.3.1.1.8,SCSI-MIB::scsiAuthIntrReadMegaBytes,Counter32,read-only,,current,,This object indicates the amount of data in megabytes that the remote SCSI initiator device or port corresponding to this entry has read from the local SCSI target device or port corresponding to this entry. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiAuthIntrLastCreation.
.1.3.6.1.2.1.139.2.3.3.1.1.9,SCSI-MIB::scsiAuthIntrWrittenMegaBytes,Counter32,read-only,,current,,This object indicates the amount of data in megabytes that the remote SCSI initiator device or port corresponding to this entry has written to the local SCSI target device or port corresponding to this entry. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiAuthIntrLastCreation.
.1.3.6.1.2.1.139.2.3.3.1.1.10,SCSI-MIB::scsiAuthIntrHSOutCommands,Counter64,read-only,,current,,This object represents the number of commands sent by the remote SCSI initiator device or port corresponding to this entry to the local SCSI target device or port corresponding to this entry. This object provides support for systems that can quickly generate a large number of commands because they run at high speed. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiAuthIntrLastCreation.
.1.3.6.1.2.1.139.2.3.3.1.1.11,SCSI-MIB::scsiAuthIntrLastCreation,TimeTicks,read-only,,current,,This object indicates the value of sysUpTime when this row was last created.
.1.3.6.1.2.1.139.2.3.3.1.1.12,SCSI-MIB::scsiAuthIntrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows an administrator to create or delete this entry. A newly created row cannot be made active until a value has been set for scsiAuthIntrName. In this case, the value of the corresponding instance of the scsiAuthIntrRowStatus column will stay 'notReady'. The RowStatus TC [RFC2579] requires that this DESCRIPTION clause states under which circumstances other objects in this row can be modified: The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.139.2.3.3.2,SCSI-MIB::scsiAttIntrPortTable,,not-accessible,,current,,This table includes all the remote SCSI initiator ports that are currently attached to a local SCSI target port of all local devices within all SCSI instances.
.1.3.6.1.2.1.139.2.3.3.2.1,SCSI-MIB::scsiAttIntrPortEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiPortIndex:scsiAttIntrPortIndex,current,,An entry (row) represents a remote SCSI initiator port currently attached to a particular local SCSI target port of a particular SCSI target device of a particular SCSI instance.
.1.3.6.1.2.1.139.2.3.3.2.1.1,SCSI-MIB::scsiAttIntrPortIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary integer used to uniquely identify a particular attached remote initiator port to a particular SCSI target port within a particular SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.3.3.2.1.2,SCSI-MIB::scsiAttIntrPortAuthIntrIdx,Unsigned32,read-only,,current,,This object is the corresponding index in the scsiAuthorizedIntrTable for this current attached remote SCSI initiator device or zero if this remote attached SCSI initiator device is not configured in that table.
.1.3.6.1.2.1.139.2.3.3.2.1.3,SCSI-MIB::scsiAttIntrPortName,OCTET,read-only,,current,,This object represents the name of the remote SCSI initiator device attached to this local SCSI target port.
.1.3.6.1.2.1.139.2.3.3.2.1.4,SCSI-MIB::scsiAttIntrPortIdentifier,OCTET,read-only,,current,,This object represents the identifier of the remote SCSI initiator device attached to this local SCSI target port.
.1.3.6.1.2.1.139.2.4,SCSI-MIB::scsiLogicalUnit,,,,,,
.1.3.6.1.2.1.139.2.4.1,SCSI-MIB::scsiLuTable,,not-accessible,,current,,This table contains the logical units exposed by local SCSI target devices. It includes attributes for the World Wide Name (WWN), scsiLuVendorId, scsiLuProductId, and scsiLuRevisionId, which may also appear in the scsiLuIdTable. If an implementation exposes a WWN as a LuIdTable entry, it must match the scsiLuWwnName in this table. If an implementation exposes a (vendor, product, revision) identifier as an LuIdTable entry, each of these fields must match the scsiLuVendorId, scsiLuProductId, and scsiLuRevisionId attributes in this table.
.1.3.6.1.2.1.139.2.4.1.1,SCSI-MIB::scsiLuEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiLuIndex,current,,An entry (row) contains information applicable to a particular logical unit of a particular local SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.4.1.1.1,SCSI-MIB::scsiLuIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary integer used to uniquely identify a particular logical unit within a particular SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.4.1.1.2,SCSI-MIB::scsiLuDefaultLun,OCTET,read-only,,current,,This object represents the default Logical Unit Number (LUN) for this logical unit; if a SCSI initiator device has not been configured to view this logical unit via an entry in the ScsiLunMapTable, the LU will be visible as scsiLuDefaultLun. If this logical unit does not have a default LUN, it will only be visible if specified via the ScsiLunMapTable, and this object will contain a zero-length string.
.1.3.6.1.2.1.139.2.4.1.1.3,SCSI-MIB::scsiLuWwnName,OCTET,read-only,,current,,This object represents the World Wide Name of this LU that is the device identifier of the Vital Product Data (VPD) page name; if there is no WWN for this LU, this object will contain a zero-length string. If there is more than one identifier, they will be listed in the scsiLuIdTable and this object will contain a zero-length string.
.1.3.6.1.2.1.139.2.4.1.1.4,SCSI-MIB::scsiLuVendorId,OCTET,read-only,,current,,This object represents a string identifying the vendor of this LU as reported in the Standard INQUIRY data.
.1.3.6.1.2.1.139.2.4.1.1.5,SCSI-MIB::scsiLuProductId,OCTET,read-only,,current,,This object represents a string identifying the product for this LU as reported in the Standard INQUIRY data.
.1.3.6.1.2.1.139.2.4.1.1.6,SCSI-MIB::scsiLuRevisionId,OCTET,read-only,,current,,This object represents a string defining the product revision of this LU as reported in the Standard INQUIRY data.
.1.3.6.1.2.1.139.2.4.1.1.7,SCSI-MIB::scsiLuPeripheralType,Unsigned32,read-only,,current,,This object is the value returned by SCSI Standard INQUIRY data. It can be: direct-access device, sequential-access device, printer, communication device and so on. The values that can be returned here are defined in SCSI Primary Commands -2.
.1.3.6.1.2.1.139.2.4.1.1.8,SCSI-MIB::scsiLuStatus,INTEGER,read-only,,current,unknown(1):available(2):notAvailable(3):broken(4):readying(5):abnormal(6),This object represents the status of this logical unit: - unknown(1): The status of this logical unit cannot be determined. - available(2): The logical unit is fully operational (i.e., accepts media access SCSI commands and has no state information to report). - notAvailable(3): The logical unit is capable of being supported but is not available (i.e., no logical unit is currently present or the logical unit is present but not configured for use). - broken(4): The logical unit has failed and cannot respond to SCSI commands. - readying(5): The logical unit is being initialized and access is temporarily limited. - abnormal(6): The logical unit has state information available that indicates it is operating with limits. The scsiLuState indicates what those limits are. 
.1.3.6.1.2.1.139.2.4.1.1.9,SCSI-MIB::scsiLuState,BITS,read-only,,current,dataLost(0):dynamicReconfigurationInProgress(1):exposed(2):fractionallyExposed(3):partiallyExposed(4):protectedRebuild(5):protectionDisabled(6):rebuild(7):recalculate(8):spareInUse(9):verifyInProgress(10),This object represents the state of a logical unit and its meaning according to the bit position: 0 Data lost: Within the logical unit data has been lost. 1 Dynamic reconfiguration in progress: The logical unit is being reconfigured. In this state all data is still protected. 2 Exposed: Within the logical unit data is not protected. In this state all data is still valid; however, loss of data or data availability is unavoidable in the event of a failure. 3 Fractionally exposed: Within the logical unit part of the data is not protected. In this state all data is still valid; however, a failure may cause a loss of data or a loss of data availability. 4 Partially exposed: Within the logical unit one or more underlying storage devices have failed. In this state all data is still protected. 5 Protected rebuild: The logical unit is in the process of a rebuild operation. In this state all data is protected. 6 Protection disabled: Within the logical unit the data protection method has been disabled. In this state all data is still valid; however, loss of data or data availability is unavoidable in the event of a failure. 7 Rebuild: The data protection method is in the process of rebuilding data. In this state data is not protected. 8 Recalculate: The logical unit is in the process of a recalculate operation. 9 Spare in use: Within the logical unit a storage device in full or part is being used to store data. In this state all data is still protected. 10 Verify in progress: Within the logical unit data is being verified.
.1.3.6.1.2.1.139.2.4.1.1.10,SCSI-MIB::scsiLuInCommands,Counter32,read-only,,current,,This object represents the number of commands received by this logical unit. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiLuLastCreation.
.1.3.6.1.2.1.139.2.4.1.1.11,SCSI-MIB::scsiLuReadMegaBytes,Counter32,read-only,,current,,This object represents the amount of data in megabytes read from this logical unit. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiLuLastCreation.
.1.3.6.1.2.1.139.2.4.1.1.12,SCSI-MIB::scsiLuWrittenMegaBytes,Counter32,read-only,,current,,This object represents the amount of data in megabytes written to this logical unit. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiLuLastCreation.
.1.3.6.1.2.1.139.2.4.1.1.13,SCSI-MIB::scsiLuInResets,Counter32,read-only,,current,,This object represents the number of times that this logical unit received - a LOGICAL UNIT RESET or TARGET RESET task management request, or - any other SCSI transport protocol-specific action or event that causes a Logical Unit Reset or a Hard Reset at a SCSI target port of the containing device ([SAM2] Chapters 5.9.6, 5.9.7). Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiLuLastCreation.
.1.3.6.1.2.1.139.2.4.1.1.14,SCSI-MIB::scsiLuOutTaskSetFullStatus,Counter32,read-only,,current,,This object represents the number of Task Set full statuses issued for this logical unit. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiLuLastCreation.
.1.3.6.1.2.1.139.2.4.1.1.15,SCSI-MIB::scsiLuHSInCommands,Counter64,read-only,,current,,This object represents the number of commands received by this logical unit. This object provides support for systems that can quickly generate a large number of commands because they run at high speed. Discontinuities in the value of this counter can occur at re- initialization of the management system, and at other times as indicated by the value of scsiLuLastCreation.
.1.3.6.1.2.1.139.2.4.1.1.16,SCSI-MIB::scsiLuLastCreation,TimeTicks,read-only,,current,,This object indicates the value of sysUpTime when this row was last created.
.1.3.6.1.2.1.139.2.4.2,SCSI-MIB::scsiLuIdTable,,not-accessible,,current,,A table of identifiers for all logical units exposed by the local SCSI target device.
.1.3.6.1.2.1.139.2.4.2.1,SCSI-MIB::scsiLuIdEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiLuIndex:scsiLuIdIndex,current,,An entry (row) containing information applicable to a particular identifier for a particular logical unit of a particular SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.4.2.1.1,SCSI-MIB::scsiLuIdIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary integer used to uniquely identify a particular LU identifier within a particular logical unit within a particular SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.4.2.1.2,SCSI-MIB::scsiLuIdCodeSet,Unsigned32,read-only,,current,,This object specifies the code set in use with this identifier. The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.4.2.1.3,SCSI-MIB::scsiLuIdAssociation,Unsigned32,read-only,,current,,This object specifies what the identifier is associated with (e.g., with the addressed physical/logical device or with a particular port). The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.4.2.1.4,SCSI-MIB::scsiLuIdType,Unsigned32,read-only,,current,,This object specifies the type of the identifier. The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.4.2.1.5,SCSI-MIB::scsiLuIdValue,OCTET,read-only,,current,,This object represents the actual value of this identifier. The format is defined by the objects scsiLuIdCodeSet, scsiLuIdAssociation, scsiLuIdType. The value is represented in the same format as is contained in the identifier's Identification Descriptor within the logical unit's Device Identification Page.
.1.3.6.1.2.1.139.2.4.3,SCSI-MIB::scsiLunMapTable,,not-accessible,,current,,This table provides the ability to present a logical unit using different Logical Unit Numbers for different SCSI initiator devices. This table provides a mapping between a logical unit and a Logical Unit Number, and can be referenced by a ScsiAuthorizedIntrEntry to specify the LUN map for that initiator.
.1.3.6.1.2.1.139.2.4.3.1,SCSI-MIB::scsiLunMapEntry,,not-accessible,scsiInstIndex:scsiDeviceIndex:scsiLunMapIndex:scsiLunMapLun,current,,An entry containing information about the mapping of a particular logical unit to a particular LUN. The set of entries that all have the same values of scsiInstIndex, scsiDeviceIndex and scsiLunMapIndex constitutes a LUN map within a particular SCSI instance. The StorageType of a row in this table is specified by the instance of scsiInstStorageType that is INDEX-ed by the same value of scsiInstIndex.
.1.3.6.1.2.1.139.2.4.3.1.1,SCSI-MIB::scsiLunMapIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary integer used to uniquely identify a particular LunMap within a particular SCSI target device within a particular SCSI instance.
.1.3.6.1.2.1.139.2.4.3.1.2,SCSI-MIB::scsiLunMapLun,OCTET,not-accessible,,current,,This object specifies the Logical Unit Number, to which a logical unit is mapped by this row.
.1.3.6.1.2.1.139.2.4.3.1.3,SCSI-MIB::scsiLunMapLuIndex,Unsigned32,read-create,,current,,This object identifies the logical unit for which the value of scsiLuIndex is the same as the value of this object. The identified logical unit is the one mapped to a LUN by this row.
.1.3.6.1.2.1.139.2.4.3.1.4,SCSI-MIB::scsiLunMapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows an administrator to create and delete this entry.
.1.3.6.1.2.1.139.3,SCSI-MIB::scsiConformance,,,,,,
.1.3.6.1.2.1.139.3.1,SCSI-MIB::scsiCompliances,,,,,,
.1.3.6.1.2.1.139.3.1.1,SCSI-MIB::scsiCompliance,,,,,,Describes the requirements for compliance to this SCSI MIB module. If an implementation can be both a SCSI target device and a SCSI initiator device, all groups are mandatory.
.1.3.6.1.2.1.139.3.2,SCSI-MIB::scsiGroups,,,,,,
.1.3.6.1.2.1.139.3.2.1,SCSI-MIB::scsiDeviceGroup,,,,,,A collection of objects providing information about SCSI instances, devices, and ports.
.1.3.6.1.2.1.139.3.2.2,SCSI-MIB::scsiInitiatorDeviceGroup,,,,,,This group is relevant for s SCSI initiator device and port.
.1.3.6.1.2.1.139.3.2.3,SCSI-MIB::scsiDiscoveryGroup,,,,,,This group is relevant for the discovered SCSI target devices by a SCSI initiator port.
.1.3.6.1.2.1.139.3.2.4,SCSI-MIB::scsiTargetDeviceGroup,,,,,,This group is relevant for a SCSI target device and port.
.1.3.6.1.2.1.139.3.2.5,SCSI-MIB::scsiLunMapGroup,,,,,,This group is a collection of attributes regarding the mapping between Logical Unit Number, logical unit, and target device.
.1.3.6.1.2.1.139.3.2.6,SCSI-MIB::scsiTargetDevStatsGroup,,,,,,This group is a collection of statistics for all implementations of the SCSI MIB module that contain SCSI target devices.
.1.3.6.1.2.1.139.3.2.7,SCSI-MIB::scsiTargetDevHSStatsGroup,,,,,,This group is a collection of high speed statistics for all implementations of the SCSI MIB module that contain SCSI target devices.
.1.3.6.1.2.1.139.3.2.8,SCSI-MIB::scsiLunMapStatsGroup,,,,,,This group is a collection of statistics regarding SCSI initiator devices authorized to attach local logical unit and SCSI target device.
.1.3.6.1.2.1.139.3.2.9,SCSI-MIB::scsiLunMapHSStatsGroup,,,,,,This group is a collection of high speed statistics regarding SCSI initiator devices authorized to attach local logical unit and SCSI target device.
.1.3.6.1.2.1.139.3.2.10,SCSI-MIB::scsiInitiatorDevStatsGroup,,,,,,This group is a collection of statistics for all implementations of the SCSI MIB module that contain SCSI initiator devices.
.1.3.6.1.2.1.139.3.2.11,SCSI-MIB::scsiInitiatorDevHSStatsGroup,,,,,,This group is a collection of high speed statistics for all implementations of the SCSI MIB module that contain SCSI initiator devices.
.1.3.6.1.2.1.139.3.2.12,SCSI-MIB::scsiDiscoveryStatsGroup,,,,,,This group is a collection of statistics for all implementations of the SCSI MIB module that contain discovered SCSI initiator devices.
.1.3.6.1.2.1.139.3.2.13,SCSI-MIB::scsiDiscoveryHSStatsGroup,,,,,,This group is a collection of high speed statistics for all implementations of the SCSI MIB module that contain discovered SCSI initiator devices.
.1.3.6.1.2.1.139.3.2.14,SCSI-MIB::scsiDeviceStatGroup,,,,,,A collection of statistics regarding SCSI devices and ports.
.1.3.6.1.2.1.139.3.2.15,SCSI-MIB::scsiTgtDevLuNotificationsGroup,,,,,,A collection of notifications regarding status change of SCSI target devices and logical units.
.1.3.6.1.2.1.140,PKTC-IETF-MTA-MIB::pktcIetfMtaMib,,,,,,This MIB module defines the basic management object for the Multimedia Terminal Adapter devices compliant with PacketCable and IPCablecom requirements. Copyright (C) The IETF Trust (2006). This version of this MIB module is part of RFC 4682; see the RFC itself for full legal notices.
.1.3.6.1.2.1.140.0,PKTC-IETF-MTA-MIB::pktcMtaNotification,,,,,,
.1.3.6.1.2.1.140.0.1,PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningEnrollment,,,,,, This INFORM notification is issued by the MTA to initiate the PacketCable provisioning process when the MTA SNMP enrollment mechanism is used. It contains the system description, the current software version, the MTA device type identifier, the MTA MAC address (obtained in the MTA ifTable in the ifPhysAddress object that corresponds to the ifIndex 1), and a correlation ID.
.1.3.6.1.2.1.140.0.2,PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningStatus,,,,,, This INFORM notification may be issued by the MTA to confirm the completion of the PacketCable provisioning process, and to report its provisioning completion status. It contains the MTA MAC address (obtained in the MTA ifTable in the ifPhysAddress object that corresponds to the ifIndex 1), a correlation ID and the MTA provisioning state as defined in pktcMtaDevProvisioningState.
.1.3.6.1.2.1.140.1,PKTC-IETF-MTA-MIB::pktcMtaMibObjects,,,,,,
.1.3.6.1.2.1.140.1.1,PKTC-IETF-MTA-MIB::pktcMtaDevBase,,,,,,
.1.3.6.1.2.1.140.1.1.1,PKTC-IETF-MTA-MIB::pktcMtaDevResetNow,INTEGER,read-write,,current,true(1):false(2), This object controls the MTA software reset. Reading this object always returns 'false'. Setting this object to 'true' causes the device to reset immediately and the following actions to occur: 1. All connections (if present) are flushed locally. 2. All current actions such as ringing immediately terminate. 3. Requests for signaling notifications, such as notification based on digit map recognition, are flushed. 4. All endpoints are disabled. 5. The provisioning flow is started at step MTA-1. If a value is written into an instance of pktcMtaDevResetNow, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.1.2,PKTC-IETF-MTA-MIB::pktcMtaDevSerialNumber,OCTET,read-only,,current,, This object specifies the manufacturer's serial number of this MTA. The value of this object MUST be identical to the value specified in DHCP option 43, sub-option 4. The list of sub-options for DHCP option 43 are defined in the PacketCable MTA Device Provisioning Specification.
.1.3.6.1.2.1.140.1.1.3,PKTC-IETF-MTA-MIB::pktcMtaDevSwCurrentVers,OCTET,read-only,,current,, This object identifies the software version currently operating in the MTA. The MTA MUST return a string descriptive of the current software load. This object should use the syntax defined by the individual vendor to identify the software version. The data presented in this object MUST be identical to the software version information contained in the 'sysDescr' MIB object of the MTA. The value of this object MUST be identical to the value specified in DHCP option 43, sub-option 6. The list of sub-options for DHCP option 43 are defined in the PacketCable MTA Device Provisioning Specification.
.1.3.6.1.2.1.140.1.1.4,PKTC-IETF-MTA-MIB::pktcMtaDevFQDN,OCTET,read-only,,current,, This object contains the Fully Qualified Domain Name for this MTA. The MTA FQDN is used to uniquely identify the device to the PacketCable back office elements.
.1.3.6.1.2.1.140.1.1.5,PKTC-IETF-MTA-MIB::pktcMtaDevEndPntCount,Unsigned32,read-only,,current,, This object contains the number of physical endpoints for this MTA.
.1.3.6.1.2.1.140.1.1.6,PKTC-IETF-MTA-MIB::pktcMtaDevEnabled,INTEGER,read-write,,current,true(1):false(2), This object contains the MTA Admin Status of this device. If this object is set to 'true', the MTA is administratively enabled, and the MTA MUST be able to interact with the PacketCable entities, such as CMS, Provisioning Server, KDC, and other MTAs and MGs on all PacketCable interfaces. If this object is set to 'false', the MTA is administratively disabled, and the MTA MUST perform the following actions for all endpoints: - Shut down all media sessions, if present. - Shut down Network Control Signaling (NCS) signaling by following the Restart in Progress procedures in the PacketCable NCS specification. The MTA must execute all actions required to enable or disable the telephony services for all endpoints immediately upon receipt of an SNMP SET operation. Additionally, the MTA MUST maintain the SNMP Interface for management and also the SNMP Key management interface. Also, the MTA MUST NOT continue Kerberized key management with CMSes until this object is set to 'true'. Note: MTAs MUST renew the CMS Kerberos tickets according to the PacketCable Security or IPCablecom Specification. If a value is written into an instance of pktcMtaDevEnabled, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.1.7,PKTC-IETF-MTA-MIB::pktcMtaDevTypeIdentifier,OCTET,read-only,,current,, This object provides the MTA device type identifier. The value of this object must be a copy of the DHCP option 60 value exchanged between the MTA and the DHCP server. The DHCP option 60 value contains an ASCII-encoded string identifying capabilities of the MTA as defined in the PacketCable MTA Device Provisioning Specification.
.1.3.6.1.2.1.140.1.1.8,PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningState,INTEGER,read-only,,current,pass(1):inProgress(2):failConfigFileError(3):passWithWarnings(4):passWithIncompleteParsing(5):failureInternalError(6):failureOtherReason(7), This object indicates the completion state of the MTA device provisioning process. pass: If the configuration file could be parsed successfully and the MTA is able to reflect the same in its MIB, the MTA MUST return the value 'pass'. inProgress: If the MTA is in the process of being provisioned, the MTA MUST return the value 'inProgress'. failConfigFileError: If the configuration file was in error due to incorrect values in the mandatory parameters, the MTA MUST reject the configuration file, and the MTA MUST return the value 'failConfigFileError'. passWithWarnings: If the configuration file had proper values for all the mandatory parameters but has errors in any of the optional parameters (this includes any vendor-specific Object Identifiers (OIDs) that are incorrect or not known to the MTA), the MTA MUST return the value 'passWithWarnings'. passWithIncompleteParsing: If the configuration file is valid but the MTA cannot reflect the same in its configuration (for example, too many entries caused memory exhaustion), it must accept the CMS configuration entries related, and the MTA MUST return the value 'passWithIncompleteParsing'. failureInternalError: If the configuration file cannot be parsed due to an Internal error, the MTA MUST return the value 'failureInternalError'. failureOtherReason: If the MTA cannot accept the configuration file for any other reason than the ones stated above, the MTA MUST return the value 'failureOtherReason'. When a final SNMP INFORM is sent as part of Step 25 of the MTA Provisioning process, this parameter is also included in the final INFORM message.
.1.3.6.1.2.1.140.1.1.9,PKTC-IETF-MTA-MIB::pktcMtaDevHttpAccess,INTEGER,read-only,,current,true(1):false(2), This object indicates whether the HTTP protocol is supported for the MTA configuration file transfer.
.1.3.6.1.2.1.140.1.1.10,PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningTimer,Unsigned32,read-write,,current,, This object defines the time interval for the provisioning flow to complete. The MTA MUST finish all provisioning operations starting from the moment when an MTA receives its DHCP ACK and ending at the moment when the MTA downloads its configuration file (e.g., MTA5 to MTA23) within the period of time set by this object. Failure to comply with this condition constitutes a provisioning flow failure. If the object is set to 0, the MTA MUST ignore the provisioning timer condition. If a value is written into an instance of pktcMtaDevProvisioningTimer, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.1.11,PKTC-IETF-MTA-MIB::pktcMtaDevProvisioningCounter,Counter32,read-only,,current,,This object counts the number of times the provisioning cycle has looped through step MTA-1.
.1.3.6.1.2.1.140.1.1.12,PKTC-IETF-MTA-MIB::pktcMtaDevErrorOidsTable,,not-accessible,,current,, This table contains the list of configuration errors or warnings the MTA encountered when parsing the configuration file it received from the Provisioning Server. For each error, an entry is created in this table, containing the configuration parameters the MTA rejected and the associated reason (e.g., wrong or unknown OID, inappropriate object values). If the MTA did not report a provisioning state of 'pass(1)' in the pktcMtaDevProvisioningState object, this table MUST be populated for each error or warning instance. Even if different parameters share the same error type (e.g., all realm name configuration parameters are invalid), all observed errors or warnings must be reported as different instances. Errors are placed into the table in no particular order. The table MUST be cleared each time the MTA reboots.
.1.3.6.1.2.1.140.1.1.12.1,PKTC-IETF-MTA-MIB::pktcMtaDevErrorOidsEntry,,not-accessible,pktcMtaDevErrorOidIndex,current,, This entry contains the necessary information the MTA MUST attempt to provide in case of configuration file errors or warnings.
.1.3.6.1.2.1.140.1.1.12.1.1,PKTC-IETF-MTA-MIB::pktcMtaDevErrorOidIndex,Unsigned32,not-accessible,,current,, This object is the index of the MTA configuration error table. It is an integer value that starts at value '1' and is incremented for each encountered configuration file error or warning. The maximum number of errors or warnings that can be recorded in the pktcMtaDevErrorOidsTable is set to 1024 as a configuration file is usually validated by operators before deployment. Given the possible number of configuration parameter assignments in the MTA configuration file, 1024 is perceived as a sufficient limit even with future extensions. If the number of the errors in the configuration file exceeds 1024, all errors beyond the 1024th one MUST be ignored and not be reflected in the pktcMtaDevErrorOidsTable.
.1.3.6.1.2.1.140.1.1.12.1.2,PKTC-IETF-MTA-MIB::pktcMtaDevErrorOid,OCTET,read-only,,current,, This object contains a human readable representation (character string) of the OID corresponding to the configuration file parameter that caused the particular error. For example, if the value of the pktcMtaDevEnabled object in the configuration file caused an error, then this object instance will contain the human-readable string of '1.3.6.1.2.1.140.1.1.6.0'. If the MTA generated an error because it was not able to recognize a particular OID, then this object instance would contain an empty value (zero-length string). For example, if the value of an OID in the configuration file was interpreted by the MTA as being 1.2.3.4.5, and if the MTA was not able to recognize this OID as a valid one, this object instance will contain a zero-length string. If the number of errors in the configuration file exceeds 1024, then for all subsequent errors, the pktcMtaDevErrorOid of the table's 1024th entry MUST contain a human-readable representation of the pktcMtaDevErrorsTooManyErrors object; i.e., the string '1.3.6.1.2.1.140.1.1.4.1.0'. Note that the syntax of this object is SnmpAdminString instead of OBJECT IDENTIFIER because the object value may not be a valid OID due to human or configuration tool encoding errors.
.1.3.6.1.2.1.140.1.1.12.1.3,PKTC-IETF-MTA-MIB::pktcMtaDevErrorValue,OCTET,read-only,,current,, This object contains the value of the OID corresponding to the configuration file parameter that caused the error. If the MTA cannot recognize the OID of the configuration parameter causing the error, then this object instance contains the OID itself as interpreted by the MTA in human-readable representation. If the MTA can recognize the OID but generate an error due to a wrong value of the parameter, then the object instance contains the erroneous value of the parameter as read from the configuration file. In both cases, the value of this object must be represented in human-readable form as a character string. For example, if the value of the pktcMtaDevEnabled object in the configuration file was 3 (invalid value), then the pktcMtaDevErrorValue object instance will contain the human-readable (string) representation of value '3'. Similarly, if the OID in the configuration file has been interpreted by the MTA as being 1.2.3.4.5 and the MTA cannot recognize this OID as a valid one, then this pktcMtaDevErrorValue object instance will contain human readable (string) representation of value '1.2.3.4.5'. If the number of errors in the configuration file exceeds 1024, then for all subsequent errors, the pktcMtaDevErrorValue of the table's 1024th entry MUST contain a human-readable representation of the pktcMtaDevErrorsTooManyErrors object; i.e., the string '1.3.6.1.2.1.140.1.1.4.1.0'.
.1.3.6.1.2.1.140.1.1.12.1.4,PKTC-IETF-MTA-MIB::pktcMtaDevErrorReason,OCTET,read-only,,current,, This object indicates the reason for the error or warning, as per the MTA's interpretation, in human-readable form. For example: 'VALUE NOT IN RANGE', 'VALUE DOES NOT MATCH TYPE', 'UNSUPPORTED VALUE', 'LAST 4 BITS MUST BE SET TO ZERO', 'OUT OF MEMORY - CANNOT STORE'. This object may also contain vendor specific errors for private vendor OIDs and any proprietary error codes or messages that can help diagnose configuration errors. If the number of errors in the configuration file exceeds 1024, then for all subsequent errors, the pktcMtaDevErrorReason of the table's 1024th entry MUST contain a human-readable string indicating the reason for an error; for example, 'Too many errors in the configuration file'.
.1.3.6.1.2.1.140.1.2,PKTC-IETF-MTA-MIB::pktcMtaDevServer,,,,,,
.1.3.6.1.2.1.140.1.2.1,PKTC-IETF-MTA-MIB::pktcMtaDevDhcpServerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16), This object contains the Internet address type for the PacketCable DHCP servers specified in MTA MIB.
.1.3.6.1.2.1.140.1.2.2,PKTC-IETF-MTA-MIB::pktcMtaDevServerDhcp1,OCTET,read-only,,current,, This object contains the Internet Address of the primary DHCP server the MTA uses during provisioning. The type of this address is determined by the value of the pktcMtaDevDhcpServerAddressType object. When the latter has the value 'ipv4(1)', this object contains the IP address of the primary DHCP server. It is provided by the CM to the MTA via the DHCP option code 122, sub-option 1, as defined in RFC 3495. The behavior of this object when the value of pktcMtaDevDhcpServerAddressType is other than 'ipv4(1)' is not presently specified, but it may be specified in future versions of this MIB module. If this object is of value 0.0.0.0, the MTA MUST stop all provisioning attempts, as well as all other activities. If this object is of value 255.255.255.255, it means that there was no preference given for the primary DHCP server, and, the MTA must follow the logic of RFC2131, and the value of DHCP option 122, sub-option 2, must be ignored.
.1.3.6.1.2.1.140.1.2.3,PKTC-IETF-MTA-MIB::pktcMtaDevServerDhcp2,OCTET,read-only,,current,, This object contains the Internet Address of the secondary DHCP server the MTA uses during provisioning. The type of this address is determined by the value of the pktcMtaDevDhcpServerAddressType object. When the latter has the value 'ipv4(1)', this object contains the IP address of the secondary DHCP server. It is provided by the CM to the MTA via the DHCP option code 122, sub-option 2, as defined in RFC 3495. The behavior of this object when the value of pktcMtaDevDhcpServerAddressType is other than 'ipv4(1)' is not presently specified, but it may be specified in future versions of this MIB module. If there was no secondary DHCP server provided in DHCP Option 122, sub-option 2, this object must return the value 0.0.0.0.
.1.3.6.1.2.1.140.1.2.4,PKTC-IETF-MTA-MIB::pktcMtaDevDnsServerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16), This object contains the Internet address type for the PacketCable DNS servers specified in MTA MIB.
.1.3.6.1.2.1.140.1.2.5,PKTC-IETF-MTA-MIB::pktcMtaDevServerDns1,OCTET,read-write,,current,, This object contains the IP Address of the primary DNS server to be used by the MTA. The type of this address is determined by the value of the pktcMtaDevDnsServerAddressType object. When the latter has the value 'ipv4(1)', this object contains the IP address of the primary DNS server. As defined in RFC 2132, PacketCable-compliant MTAs receive the IP addresses of the DNS Servers in DHCP option 6. The behavior of this object when the value of pktcMtaDevDnsServerAddressType is other than 'ipv4(1)' is not presently specified, but it may be specified in future versions of this MIB module. If a value is written into an instance of pktcMtaDevServerDns1, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.6,PKTC-IETF-MTA-MIB::pktcMtaDevServerDns2,OCTET,read-write,,current,, This object contains the IP Address of the secondary DNS server to be used by the MTA. The type of this address is determined by the value of the pktcMtaDevDnsServerAddressType object. When the latter has the value 'ipv4(1)', this object contains the IP address of the secondary DNS server. As defined in RFC 2132, PacketCable-compliant MTAs receive the IP addresses of the DNS Servers in DHCP option 6. The behavior of this object when the value of pktcMtaDevDnsServerAddressType is other than 'ipv4(1)' is not presently specified, but it may be specified in future versions of this MIB module. If a value is written into an instance of pktcMtaDevServerDns2, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.7,PKTC-IETF-MTA-MIB::pktcMtaDevTimeServerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16), This object contains the Internet address type for the PacketCable Time servers specified in MTA MIB.
.1.3.6.1.2.1.140.1.2.8,PKTC-IETF-MTA-MIB::pktcMtaDevTimeServer,OCTET,read-write,,current,, This object contains the Internet Address of the Time Server used by an S-MTA for Time Synchronization. The type of this address is determined by the value of the pktcMtaDevTimeServerAddressType object. When the latter has the value 'ipv4(1)', this object contains the IP address of the Time Server used for Time Synchronization. In the case of an S-MTA, this object must be populated with a value other than 0.0.0.0 as obtained from DHCP option 4. The protocol by which the time of day MUST be retrieved is defined in RFC 868. In the case of an E-MTA, this object must contain a value of 0.0.0.0 if the address type is 'ipv4(1)' since an E-MTA does not use the Time Protocol for time synchronization (an E-MTA uses the time retrieved by the DOCSIS cable modem). The behavior of this object when the value of pktcMtaDevTimeServerAddressType is other than 'ipv4(1)' is not presently specified, but it may be specified in future versions of this MIB module. If a value is written into an instance of pktcMtaDevTimeServer, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.9,PKTC-IETF-MTA-MIB::pktcMtaDevConfigFile,OCTET,read-write,,current,, This object specifies the MTA device configuration file information, including the access method, the server name, and the configuration file name. The value of this object is the Uniform Resource Locator (URL) of the configuration file for TFTP or HTTP download. If this object value is a TFTP URL, it must be formatted as defined in RFC 3617. If this object value is an HTTP URL, it must be formatted as defined in RFC 2616. If the MTA SNMP Enrollment mechanism is used, then the MTA must download the file provided by the Provisioning Server during provisioning via an SNMP SET on this object. If the MTA SNMP Enrollment mechanism is not used, this object MUST contain the URL value corresponding to the 'siaddr' and 'file' fields received in the DHCP ACK to locate the configuration file: the 'siaddr' and 'file' fields represent the host and file of the TFTP URL, respectively. In this case, the MTA MUST return an 'inconsistentValue' error in response to SNMP SET operations. The MTA MUST return a zero-length string if the server address (host part of the URL) is unknown. If a value is written into an instance of pktcMtaDevConfigFile, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.10,PKTC-IETF-MTA-MIB::pktcMtaDevSnmpEntity,OCTET,read-only,,current,, This object contains the FQDN of the SNMP entity of the Provisioning Server. When the MTA SNMP Enrollment Mechanism is used, this object represents the server that the MTA communicates with, that it receives the configuration file URL from, and that it sends the enrollment notification to. The SNMP entity is also the destination entity for all the provisioning notifications. It may be used for post-provisioning SNMP operations. During the provisioning phase, this SNMP entity FQDN is supplied to the MTA via DHCP option 122, sub-option 3, as defined in RFC 3495. The MTA must resolve the FQDN value before its very first network interaction with the SNMP entity during the provisioning phase.
.1.3.6.1.2.1.140.1.2.11,PKTC-IETF-MTA-MIB::pktcMtaDevProvConfigHash,OCTET,read-write,,current,, This object contains the hash value of the contents of the configuration file. The authentication algorithm is Secure Hashing Algorithm 1 (SHA-1), and the length is 160 bits. The hash calculation MUST follow the requirements defined in the PacketCable Security Specification. When the MTA SNMP Enrollment mechanism is used, this hash value is calculated and sent to the MTA prior to sending the config file. This object value is then provided by the Provisioning server via an SNMP SET operation. When the MTA SNMP Enrollment mechanism is not in use, the hash value is provided in the configuration file itself, and it is also calculated by the MTA. This object value MUST represent the hash value calculated by the MTA. When the MTA SNMP Enrollment mechanism is not in use, the MTA must reject all SNMP SET operations on this object and return an 'inconsistentValue' error. If a value is written into an instance of pktcMtaDevProvConfigHash, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.12,PKTC-IETF-MTA-MIB::pktcMtaDevProvConfigKey,OCTET,read-write,,current,, This object contains the key used to encrypt/decrypt the configuration file when secure SNMPv3 provisioning is used. The value of this object is provided along with the configuration file information (pktcMtaDevConfigFile) and hash (pktcMtaDevProvConfigHash) by the Provisioning Server via SNMP SET once the configuration file has been created, as defined by the PacketCable Security specification. The privacy algorithm is defined by the pktcMtaDevProvConfigEncryptAlg MIB object. The MTA requirements related to the privacy algorithm are defined in the PacketCable Security Specification. If this object is set at any other provisioning step than that allowed by the PacketCable MTA Device Provisioning Specification, the MTA SHOULD return an 'inconsistentValue' error. This object must not be used in non secure provisioning mode. In non-secure provisioning modes, the MTA SHOULD return an 'inconsistentValue' in response to SNMP SET operations, and the MTA SHOULD return a zero-length string in response to SNMP GET operations. If a value is written into an instance of pktcMtaDevProvConfigKey, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.13,PKTC-IETF-MTA-MIB::pktcMtaDevProvConfigEncryptAlg,INTEGER,read-write,,current,none(0):des64CbcMode(1):t3Des192CbcMode(2):aes128CbcMode(3):aes256CbcMode(4), This object defines the encryption algorithm used for privacy protection of the MTA Configuration File content.
.1.3.6.1.2.1.140.1.2.14,PKTC-IETF-MTA-MIB::pktcMtaDevProvSolicitedKeyTimeout,Unsigned32,read-write,,current,, This object defines a Kerberos Key Management timer on the MTA. It is the time period during which the MTA saves the nonce and Server Kerberos Principal Identifier to match an AP Request and its associated AP Reply response from the Provisioning Server. After the timeout has been exceeded, the client discards this (nonce, Server Kerberos Principal Identifier) pair, after which it will no longer accept a matching AP Reply. This timer only applies when the Provisioning Server initiated key management for SNMPv3 (with a Wake Up message). If this object is set to a zero value, the MTA MUST return an 'inconsistentValue' in response to SNMP SET operations. This object should not be used in non-secure provisioning modes. In non-secure provisioning modes, the MTA MUST return an 'inconsistentValue' in response to SNMP SET operations, and the MTA MUST return a zero value in response to SNMP GET operations. If a value is written into an instance of pktcMtaDevProvSolicitedKeyTimeout, the agent MUST NOT retain the supplied value across MTA re-initializations or reboots.
.1.3.6.1.2.1.140.1.2.15,PKTC-IETF-MTA-MIB::pktcMtaDevProvUnsolicitedKeyMaxTimeout,Unsigned32,read-only,,current,, This object defines the timeout value that applies to an MTA-initiated AP-REQ/REP key management exchange with the Provisioning Server in SNMPv3 provisioning. It is the maximum timeout value, and it may not be exceeded in the exponential back-off algorithm. If the DHCP option code 122, sub-option 5, is provided to the MTA, it overwrites this value. In non-secure provisioning modes, the MTA MUST return a zero value in response to SNMP GET operations.
.1.3.6.1.2.1.140.1.2.16,PKTC-IETF-MTA-MIB::pktcMtaDevProvUnsolicitedKeyNomTimeout,Unsigned32,read-only,,current,, This object defines the starting value of the timeout for the AP-REQ/REP Backoff and Retry mechanism with exponential timeout in SNMPv3 provisioning. If the DHCP option code 122, sub-option 5, is provided the MTA, it overwrites this value. In non-secure provisioning modes, the MTA MUST return a zero value in response to SNMP GET operations.
.1.3.6.1.2.1.140.1.2.17,PKTC-IETF-MTA-MIB::pktcMtaDevProvUnsolicitedKeyMaxRetries,Unsigned32,read-only,,current,, This object contains a retry counter that applies to an MTA-initiated AP-REQ/REP key management exchange with the Provisioning Server in secure SNMPv3 provisioning. It is the maximum number of retries before the MTA stops attempting to establish a Security Association with Provisioning Server. If the DHCP option code 122, sub-option 5, is provided to the MTA, it overwrites this value. If this object is set to a zero value, the MTA MUST return an 'inconsistentValue' in response to SNMP SET operations. In non-secure provisioning modes, the MTA MUST return a zero value in response to SNMP GET operations.
.1.3.6.1.2.1.140.1.2.18,PKTC-IETF-MTA-MIB::pktcMtaDevProvKerbRealmName,OCTET,read-only,,current,, This object contains the name of the associated provisioning Kerberos realm acquired during the MTA4 provisioning step (DHCP Ack) for SNMPv3 provisioning. The uppercase ASCII representation of the associated Kerberos realm name MUST be used by both the Manager (SNMP entity) and the MTA. The Kerberos realm name for the Provisioning Server is supplied to the MTA via DHCP option code 122, sub-option 6, as defined in RFC 3495. In secure SNMP provisioning mode, the value of the Kerberos realm name for the Provisioning Server supplied in the MTA configuration file must match the value supplied in the DHCP option code 122, sub-option 6. Otherwise, the value of this object must contain the value supplied in DHCP Option 122, sub-option 6.
.1.3.6.1.2.1.140.1.2.19,PKTC-IETF-MTA-MIB::pktcMtaDevProvState,INTEGER,read-only,,current,operational(1):waitingForSnmpSetInfo(2):waitingForTftpAddrResponse(3):waitingForConfigFile(4), This object defines the MTA provisioning state. If the state is: 'operational(1)', the device has completed the loading and processing of the initialization parameters. 'waitingForSnmpSetInfo(2)', the device is waiting on its configuration file download access information. Note that this state is only reported when the MTA SNMP enrollment mechanism is used. 'waitingForTftpAddrResponse(3)', the device has sent a DNS request to resolve the server providing the configuration file, and it is awaiting for a response. Note that this state is only reported when the MTA SNMP enrollment mechanism is used. 'waitingForConfigFile(4)', the device has sent a request via TFTP or HTTP for the download of its configuration file, and it is awaiting for a response or the file download is in progress.
.1.3.6.1.2.1.140.1.3,PKTC-IETF-MTA-MIB::pktcMtaDevSecurity,,,,,,
.1.3.6.1.2.1.140.1.3.1,PKTC-IETF-MTA-MIB::pktcMtaDevManufacturerCertificate,OCTET,read-only,,current,, This object contains the MTA Manufacturer Certificate. The object value must be the ASN.1 DER encoding of the MTA manufacturer's X.509 public key certificate. The MTA Manufacturer Certificate is issued to each MTA manufacturer and is installed into each MTA at the time of manufacture or with a secure code download. The specific requirements related to this certificate are defined in the PacketCable or IPCablecom Security specifications.
.1.3.6.1.2.1.140.1.3.2,PKTC-IETF-MTA-MIB::pktcMtaDevCertificate,OCTET,read-only,,current,, This object contains the MTA Device Certificate. The object value must be the ASN.1 DER encoding of the MTA's X.509 public-key certificate issued by the manufacturer and installed into the MTA at the time of manufacture or with a secure code download. This certificate contains the MTA MAC address. The specific requirements related to this certificate are defined in the PacketCable or IPCablecom Security specifications.
.1.3.6.1.2.1.140.1.3.3,PKTC-IETF-MTA-MIB::pktcMtaDevCorrelationId,Unsigned32,read-only,,current,, This object contains a correlation ID, an arbitrary value generated by the MTA that will be exchanged as part of the device capability data to the Provisioning Application. This random value is used as an identifier to correlate related events in the MTA provisioning sequence. This value is intended for use only during the MTA initialization and configuration file download.
.1.3.6.1.2.1.140.1.3.4,PKTC-IETF-MTA-MIB::pktcMtaDevTelephonyRootCertificate,OCTET,read-only,,current,, This object contains the telephony Service Provider Root certificate. The object value is the ASN.1 DER encoding of the IP Telephony Service Provider Root X.509 public key certificate. This certification is stored in the MTA non-volatile memory and can be updated with a secure code download. This certificate is used to validate the initial AS Reply received by the MTA from the Key Distribution Center (KDC) during the MTA initialization. The specific requirements related to this certificate are defined in the PacketCable or IPCablecom Security specifications.
.1.3.6.1.2.1.140.1.3.5,PKTC-IETF-MTA-MIB::pktcMtaDevRealmAvailSlot,Unsigned32,read-only,,current,, This object contains the index number of the first available entry in the realm table (pktcMtaDevRealmTable). If all the entries in the realm table have been assigned, this object contains the value of zero. A management station should create new entries in the realm table, using the following procedure: First, issue a management protocol retrieval operation to determine the value of the first available index in the realm table (pktcMtaDevRealmAvailSlot). Second, issue a management protocol SET operation to create an instance of the pktcMtaDevRealmStatus object by setting its value to 'createAndWait(5)'. Third, if the SET operation succeeded, continue modifying the object instances corresponding to the newly created conceptual row, without fear of collision with other management stations. When all necessary conceptual columns of the row are properly populated (via SET operations or default values), the management station may SET the pktcMtaDevRealmStatus object to 'active(1)'.
.1.3.6.1.2.1.140.1.3.6,PKTC-IETF-MTA-MIB::pktcMtaDevRealmTable,,not-accessible,,current,, This object contains the realm table. The CMS table (pktcMtaDevCmsTable) and the realm table (pktcMtaDevRealmTable) are used for managing the MTA-CMS Security Associations. The realm table defines the Kerberos realms for the Application Servers (CMSes and the Provisioning Server).
.1.3.6.1.2.1.140.1.3.6.1,PKTC-IETF-MTA-MIB::pktcMtaDevRealmEntry,,not-accessible,pktcMtaDevRealmIndex,current,, This table entry object lists the MTA security parameters for a single Kerberos realm. The conceptual rows MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.140.1.3.6.1.1,PKTC-IETF-MTA-MIB::pktcMtaDevRealmIndex,Unsigned32,not-accessible,,current,, This object defines the realm table index.
.1.3.6.1.2.1.140.1.3.6.1.2,PKTC-IETF-MTA-MIB::pktcMtaDevRealmName,OCTET,read-create,,current,, This object identifies the Kerberos realm name in all capitals. The MTA MUST prohibit the instantiation of any two rows with identical Kerberos realm names. The MTA MUST also verify that any search operation involving Kerberos realm names is done using the uppercase ASCII representation of the characters.
.1.3.6.1.2.1.140.1.3.6.1.3,PKTC-IETF-MTA-MIB::pktcMtaDevRealmPkinitGracePeriod,Unsigned32,read-create,,current,, This object contains the PKINIT Grace Period. For the purpose of key management with Application Servers (CMSes or the Provisioning Server), the MTA must utilize the PKINIT exchange to obtain Application Server tickets. The MTA may utilize the PKINIT exchange to obtain Ticket Granting Tickets (TGTs), which are then used to obtain Application Server tickets in a TGS exchange. The PKINIT exchange occurs according to the current Ticket Expiration Time (TicketEXP) and on the PKINIT Grace Period (PKINITGP). The MTA MUST initiate the PKINIT exchange at the time: TicketEXP - PKINITGP.
.1.3.6.1.2.1.140.1.3.6.1.4,PKTC-IETF-MTA-MIB::pktcMtaDevRealmTgsGracePeriod,Unsigned32,read-create,,current,, This object contains the Ticket Granting Server Grace Period (TGSGP). The Ticket Granting Server (TGS) Request/Reply exchange may be performed by the MTA on demand whenever an Application Server ticket is needed to establish security parameters. If the MTA possesses a ticket that corresponds to the Provisioning Server or a CMS that currently exists in the CMS table, the MTA MUST initiate the TGS Request/Reply exchange at the time: TicketEXP - TGSGP.
.1.3.6.1.2.1.140.1.3.6.1.5,PKTC-IETF-MTA-MIB::pktcMtaDevRealmOrgName,OCTET,read-create,,current,, This object contains the X.500 organization name attribute as defined in the subject name of the service provider certificate.
.1.3.6.1.2.1.140.1.3.6.1.6,PKTC-IETF-MTA-MIB::pktcMtaDevRealmUnsolicitedKeyMaxTimeout,Unsigned32,read-create,,current,, This object specifies the maximum time the MTA will attempt to perform the exponential back-off algorithm. This timer only applies when the MTA initiated key management. If the DHCP option code 122, sub-option 4, is provided to the MTA, it overwrites this value. Unsolicited key updates are retransmitted according to an exponential back-off mechanism using two timers and a maximum retry counter for AS replies. The initial retransmission timer value is the nominal timer value (pktcMtaDevRealmUnsolicitedKeyNomTimeout). The retransmissions occur with an exponentially increasing interval that caps at the maximum timeout value (pktcMtaDevRealmUnsolicitedKeyMaxTimeout). Retransmissions stop when the maximum retry counter is reached (pktcMatDevRealmUnsolicitedMaxRetries). For example, with values of 3 seconds for the nominal timer, 20 seconds for the maximum timeout, and 5 retries max, retransmission intervals will be 3 s, 6 s, 12 s, 20 s, and 20 s, and retransmissions then stop because the maximum number of retries has been reached.
.1.3.6.1.2.1.140.1.3.6.1.7,PKTC-IETF-MTA-MIB::pktcMtaDevRealmUnsolicitedKeyNomTimeout,Unsigned32,read-create,,current,, This object specifies the initial timeout value for the AS-REQ/AS-REP exponential back-off and retry mechanism. If the DHCP option code 122, sub-option 4, is provided to the MTA, it overwrites this value. This value should account for the average roundtrip time between the MTA and the KDC, as well as the processing delay on the KDC. Unsolicited key updates are retransmitted according to an exponential back-off mechanism using two timers and a maximum retry counter for AS replies. The initial retransmission timer value is the nominal timer value (pktcMtaDevRealmUnsolicitedKeyNomTimeout). The retransmissions occur with an exponentially increasing interval that caps at the maximum timeout value (pktcMtaDevRealmUnsolicitedKeyMaxTimeout). Retransmissions stop when the maximum retry counter is reached (pktcMatDevRealmUnsolicitedMaxRetries). For example, with values of 3 seconds for the nominal timer, 20 seconds for the maximum timeout, and 5 retries max, in retransmission intervals will be 3 s, 6 s, 12 s, 20 s, and 20 s; retransmissions then stop because the maximum number of retries has been reached.
.1.3.6.1.2.1.140.1.3.6.1.8,PKTC-IETF-MTA-MIB::pktcMtaDevRealmUnsolicitedKeyMaxRetries,Unsigned32,read-create,,current,, This object specifies the maximum number of retries the MTA attempts to obtain a ticket from the KDC. Unsolicited key updates are retransmitted according to an exponential back-off mechanism using two timers and a maximum retry counter for AS replies. The initial retransmission timer value is the nominal timer value (pktcMtaDevRealmUnsolicitedKeyNomTimeout). The retransmissions occur with an exponentially increasing interval that caps at the maximum timeout value (pktcMtaDevRealmUnsolicitedKeyMaxTimeout). Retransmissions stop when the maximum retry counter is reached (pktcMatDevRealmUnsolicitedMaxRetries). For example, with values of 3 seconds for the nominal timer, 20 seconds for the maximum timeout, and 5 retries max, retransmission intervals will be 3 s, 6 s, 12 s, 20 s, and 20 s; retransmissions then stop because the maximum number of retries has been reached.
.1.3.6.1.2.1.140.1.3.6.1.9,PKTC-IETF-MTA-MIB::pktcMtaDevRealmStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6), This object defines the row status of this realm in the realm table (pktcMtaDevRealmTable). An entry in this table is not qualified for activation until the object instances of all corresponding columns have been initialized, either by default values, or via explicit SET operations. Until all object instances in this row are initialized, the status value for this realm must be 'notReady(3)'. In particular, two columnar objects must be explicitly SET: the realm name (pktcMtaDevRealmName) and the organization name (pktcMtaDevRealmOrgName). Once these 2 objects have been set and the row status is SET to 'active(1)', the MTA MUST NOT allow any modification of these 2 object values. The value of this object has no effect on whether other columnar objects in this row can be modified.
.1.3.6.1.2.1.140.1.3.7,PKTC-IETF-MTA-MIB::pktcMtaDevCmsAvailSlot,Unsigned32,read-only,,current,, This object contains the index number of the first available entry in the CMS table (pktcMtaDevCmsTable). If all the entries in the CMS table have been assigned, this object contains the value of zero. A management station should create new entries in the CMS table, using the following procedure: First, issue a management protocol retrieval operation to determine the value of the first available index in the CMS table (pktcMtaDevCmsAvailSlot). Second, issue a management protocol SET operation to create an instance of the pktcMtaDevCmsStatus object by setting its value to 'createAndWait(5)'. Third, if the SET operation succeeded, continue modifying the object instances corresponding to the newly created conceptual row, without fear of collision with other management stations. When all necessary conceptual columns of the row are properly populated (via SET operations or default values), the management station may SET the pktcMtaDevCmsStatus object to 'active(1)'.
.1.3.6.1.2.1.140.1.3.8,PKTC-IETF-MTA-MIB::pktcMtaDevCmsTable,,not-accessible,,current,, This object defines the CMS table. The CMS table (pktcMtaDevCmsTable) and the realm table (pktcMtaDevRealmTable) are used for managing security between the MTA and CMSes. Each CMS table entry defines a CMS the managed MTA is allowed to communicate with and contains security parameters for key management with that CMS.
.1.3.6.1.2.1.140.1.3.8.1,PKTC-IETF-MTA-MIB::pktcMtaDevCmsEntry,,not-accessible,pktcMtaDevCmsIndex,current,, This table entry object lists the MTA key management parameters used when establishing Security Associations with a CMS. The conceptual rows MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.140.1.3.8.1.1,PKTC-IETF-MTA-MIB::pktcMtaDevCmsIndex,Unsigned32,not-accessible,,current,, This object defines the CMS table index.
.1.3.6.1.2.1.140.1.3.8.1.2,PKTC-IETF-MTA-MIB::pktcMtaDevCmsFqdn,OCTET,read-create,,current,, This object specifies the CMS FQDN. The MTA must prohibit the instantiation of any two rows with identical FQDNs. The MTA must also verify that any search and/or comparison operation involving a CMS FQDN is case insensitive. The MTA must resolve the CMS FQDN as required by the corresponding PacketCable Specifications.
.1.3.6.1.2.1.140.1.3.8.1.3,PKTC-IETF-MTA-MIB::pktcMtaDevCmsKerbRealmName,OCTET,read-create,,current,, This object identifies the Kerberos realm name in uppercase characters associated with the CMS defined in this conceptual row. The object value is a reference point to the corresponding Kerberos realm name in the realm table (pktcMtaDevRealmTable).
.1.3.6.1.2.1.140.1.3.8.1.4,PKTC-IETF-MTA-MIB::pktcMtaDevCmsMaxClockSkew,Unsigned32,read-create,,current,, This object specifies the maximum allowable clock skew between the MTA and the CMS defined in this row.
.1.3.6.1.2.1.140.1.3.8.1.5,PKTC-IETF-MTA-MIB::pktcMtaDevCmsSolicitedKeyTimeout,Unsigned32,read-create,,current,, This object defines a Kerberos Key Management timer on the MTA. It is the time period during which the MTA saves the nonce and Server Kerberos Principal Identifier to match an AP Request and its associated AP Reply response from the CMS. This timer only applies when the CMS initiated key management (with a Wake Up message or a Rekey message).
.1.3.6.1.2.1.140.1.3.8.1.6,PKTC-IETF-MTA-MIB::pktcMtaDevCmsUnsolicitedKeyMaxTimeout,Unsigned32,read-create,,current,, This object defines the timeout value that only applies to an MTA-initiated key management exchange. It is the maximum timeout, and it may not be exceeded in the exponential back-off algorithm.
.1.3.6.1.2.1.140.1.3.8.1.7,PKTC-IETF-MTA-MIB::pktcMtaDevCmsUnsolicitedKeyNomTimeout,Unsigned32,read-create,,current,, This object defines the starting value of the timeout for an MTA-initiated key management. It should account for the average roundtrip time between the MTA and the CMS and the processing time on the CMS.
.1.3.6.1.2.1.140.1.3.8.1.8,PKTC-IETF-MTA-MIB::pktcMtaDevCmsUnsolicitedKeyMaxRetries,Unsigned32,read-create,,current,, This object contains the maximum number of retries before the MTA stops attempting to establish a Security Association with the CMS.
.1.3.6.1.2.1.140.1.3.8.1.9,PKTC-IETF-MTA-MIB::pktcMtaDevCmsIpsecCtrl,INTEGER,read-only,,current,true(1):false(2), This object specifies the MTA IPSec control flag. If the object value is 'true', the MTA must use Kerberos Key Management and IPsec to communicate with this CMS. If it is 'false', IPSec Signaling Security and Kerberos key management are disabled for this specific CMS.
.1.3.6.1.2.1.140.1.3.8.1.10,PKTC-IETF-MTA-MIB::pktcMtaDevCmsStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6), This object defines the row status associated with this particular CMS in the CMS table (pktcMtaDevCmsTable). An entry in this table is not qualified for activation until the object instances of all corresponding columns have been initialized, either by default values or via explicit SET operations. Until all object instances in this row are initialized, the status value for this realm must be 'notReady(3)'. In particular, two columnar objects must be SET: the CMS FQDN (pktcMtaDevCmsFqdn) and the Kerberos realm name (pktcMtaDevCmsKerbRealmName). Once these 2 objects have been set and the row status is SET to 'active(1)', the MTA MUST NOT allow any modification of these 2 object values. The value of this object has no effect on whether other columnar objects in this row can be modified.
.1.3.6.1.2.1.140.1.3.9,PKTC-IETF-MTA-MIB::pktcMtaDevResetKrbTickets,BITS,read-write,,current,invalidateProvOnReboot(0):invalidateAllCmsOnReboot(1), This object defines a Kerberos Ticket Control Mask that instructs the MTA to invalidate the specific Application Server Kerberos ticket(s) that are stored locally in the MTA NVRAM (non-volatile or persistent memory). If the MTA does not store Kerberos tickets in NVRAM, it MUST ignore setting of this object and MUST report a BITS value of zero when the object is read. If the MTA supports Kerberos tickets storage in NVRAM, the object value is encoded as follows: - Setting the invalidateProvOnReboot bit (bit 0) to 1 means that the MTA MUST invalidate the Kerberos Application Ticket(s) for the Provisioning Application at the next MTA reboot if secure SNMP provisioning mode is used. In non-secure provisioning modes, the MTA MUST return an 'inconsistentValue' in response to SNMP SET operations with a bit 0 set to 1. - Setting the invalidateAllCmsOnReboot bit (bit 1) to 1 means that the MTA MUST invalidate the Kerberos Application Ticket(s) for all CMSes currently assigned to the MTA endpoints. If a value is written into an instance of pktcMtaDevResetKrbTickets, the agent MUST retain the supplied value across an MTA re-initialization or reboot.
.1.3.6.1.2.1.140.1.4,PKTC-IETF-MTA-MIB::pktcMtaDevErrors,,,,,,
.1.3.6.1.2.1.140.1.4.1,PKTC-IETF-MTA-MIB::pktcMtaDevErrorsTooManyErrors,,,,,,This object defines the OID corresponding to the error condition when too many errors are encountered in the MTA configuration file during provisioning.
.1.3.6.1.2.1.140.2,PKTC-IETF-MTA-MIB::pktcMtaConformance,,,,,,
.1.3.6.1.2.1.140.2.1,PKTC-IETF-MTA-MIB::pktcMtaCompliances,,,,,,
.1.3.6.1.2.1.140.2.1.1,PKTC-IETF-MTA-MIB::pktcMtaBasicCompliance,,,,,, The compliance statement for MTA devices that implement PacketCable or IPCablecom requirements. This compliance statement applies to MTA implementations that support PacketCable 1.0 or IPCablecom requirements, which are not IPv6-capable at the time of this RFC publication.
.1.3.6.1.2.1.140.2.1.2,PKTC-IETF-MTA-MIB::pktcMtaBasicSmtaCompliance,,,,,, The compliance statement for S-MTA devices that implement PacketCable or IPCablecom requirements. This compliance statement applies to S-MTA implementations that support PacketCable or IPCablecom requirements, which are not IPv6-capable at the time of this RFC publication.
.1.3.6.1.2.1.140.2.2,PKTC-IETF-MTA-MIB::pktcMtaGroups,,,,,,
.1.3.6.1.2.1.140.2.2.1,PKTC-IETF-MTA-MIB::pktcMtaGroup,,,,,, A collection of objects for managing PacketCable or IPCablecom MTA implementations.
.1.3.6.1.2.1.140.2.2.2,PKTC-IETF-MTA-MIB::pktcMtaNotificationGroup,,,,,, A collection of notifications dealing with the change of MTA provisioning status.
.1.3.6.1.2.1.141,IPS-AUTH-MIB::ipsAuthMibModule,,,,,,The IP Storage Authorization MIB module. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4545; see the RFC itself for full legal notices.
.1.3.6.1.2.1.141.0,IPS-AUTH-MIB::ipsAuthNotifications,,,,,,
.1.3.6.1.2.1.141.1,IPS-AUTH-MIB::ipsAuthObjects,,,,,,
.1.3.6.1.2.1.141.1.1,IPS-AUTH-MIB::ipsAuthDescriptors,,,,,,
.1.3.6.1.2.1.141.1.1.1,IPS-AUTH-MIB::ipsAuthMethodTypes,,,,,,Registration point for Authentication Method Types.
.1.3.6.1.2.1.141.1.1.1.1,IPS-AUTH-MIB::ipsAuthMethodNone,,,,,,The authoritative identifier when no authentication method is used.
.1.3.6.1.2.1.141.1.1.1.2,IPS-AUTH-MIB::ipsAuthMethodSrp,,,,,,The authoritative identifier when the authentication method is SRP.
.1.3.6.1.2.1.141.1.1.1.3,IPS-AUTH-MIB::ipsAuthMethodChap,,,,,,The authoritative identifier when the authentication method is CHAP.
.1.3.6.1.2.1.141.1.1.1.4,IPS-AUTH-MIB::ipsAuthMethodKerberos,,,,,,The authoritative identifier when the authentication method is Kerberos.
.1.3.6.1.2.1.141.1.2,IPS-AUTH-MIB::ipsAuthInstance,,,,,,
.1.3.6.1.2.1.141.1.2.2,IPS-AUTH-MIB::ipsAuthInstanceAttributesTable,,not-accessible,,current,,A list of Authorization instances present on the system.
.1.3.6.1.2.1.141.1.2.2.1,IPS-AUTH-MIB::ipsAuthInstanceAttributesEntry,,not-accessible,ipsAuthInstIndex,current,,An entry (row) containing management information applicable to a particular Authorization instance.
.1.3.6.1.2.1.141.1.2.2.1.1,IPS-AUTH-MIB::ipsAuthInstIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular authorization instance. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.141.1.2.2.1.2,IPS-AUTH-MIB::ipsAuthInstDescr,OCTET,read-write,,current,,A character string, determined by the implementation to describe the authorization instance. When only a single instance is present, this object may be set to the zero-length string; with multiple authorization instances, it must be set to a unique value in an implementation-dependent manner to describe the purpose of the respective instance. If this is deployed in a master agent with more than one subagent implementing this MIB module, the master agent is responsible for ensuring that this object is unique across all subagents.
.1.3.6.1.2.1.141.1.2.2.1.3,IPS-AUTH-MIB::ipsAuthInstStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-write objects within this row. Rows in this table are always created via an external process, and may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row. If this object has the value 'volatile', modifications to read-write objects in this row are not persistent across reboots. If this object has the value 'nonVolatile', modifications to objects in this row are persistent. An implementation may choose to allow this object to be set to either 'nonVolatile' or 'volatile', allowing the management application to choose this behavior.
.1.3.6.1.2.1.141.1.3,IPS-AUTH-MIB::ipsAuthIdentity,,,,,,
.1.3.6.1.2.1.141.1.3.1,IPS-AUTH-MIB::ipsAuthIdentAttributesTable,,not-accessible,,current,,A list of user identities, each belonging to a particular ipsAuthInstance.
.1.3.6.1.2.1.141.1.3.1.1,IPS-AUTH-MIB::ipsAuthIdentAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex,current,,An entry (row) containing management information describing a user identity within an authorization instance on this node.
.1.3.6.1.2.1.141.1.3.1.1.1,IPS-AUTH-MIB::ipsAuthIdentIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular identity instance within an authorization instance present on the node. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.141.1.3.1.1.2,IPS-AUTH-MIB::ipsAuthIdentDescription,OCTET,read-create,,current,,A character string describing this particular identity.
.1.3.6.1.2.1.141.1.3.1.1.3,IPS-AUTH-MIB::ipsAuthIdentRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The value of ipsAuthIdentDescription may be set while ipsAuthIdentRowStatus is 'active'.
.1.3.6.1.2.1.141.1.3.1.1.4,IPS-AUTH-MIB::ipsAuthIdentStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.1.4,IPS-AUTH-MIB::ipsAuthIdentityName,,,,,,
.1.3.6.1.2.1.141.1.4.1,IPS-AUTH-MIB::ipsAuthIdentNameAttributesTable,,not-accessible,,current,,A list of unique names that can be used to positively identify a particular user identity.
.1.3.6.1.2.1.141.1.4.1.1,IPS-AUTH-MIB::ipsAuthIdentNameAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex:ipsAuthIdentNameIndex,current,,An entry (row) containing management information applicable to a unique identity name, which can be used to identify a user identity within a particular authorization instance.
.1.3.6.1.2.1.141.1.4.1.1.1,IPS-AUTH-MIB::ipsAuthIdentNameIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular identity name instance within an ipsAuthIdentity within an authorization instance. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.141.1.4.1.1.2,IPS-AUTH-MIB::ipsAuthIdentName,OCTET,read-create,,current,,A character string that is the unique name of an identity that may be used to identify this ipsAuthIdent entry.
.1.3.6.1.2.1.141.1.4.1.1.3,IPS-AUTH-MIB::ipsAuthIdentNameRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The value of ipsAuthIdentName may be set when this value is 'active'.
.1.3.6.1.2.1.141.1.4.1.1.4,IPS-AUTH-MIB::ipsAuthIdentNameStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.1.5,IPS-AUTH-MIB::ipsAuthIdentityAddress,,,,,,
.1.3.6.1.2.1.141.1.5.1,IPS-AUTH-MIB::ipsAuthIdentAddrAttributesTable,,not-accessible,,current,,A list of address ranges that are allowed to serve as the endpoint addresses of a particular identity. An address range includes a starting and ending address and an optional netmask, and an address type indicator, which can specify whether the address is IPv4, IPv6, FC-WWPN, or FC-WWNN.
.1.3.6.1.2.1.141.1.5.1.1,IPS-AUTH-MIB::ipsAuthIdentAddrAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex:ipsAuthIdentAddrIndex,current,,An entry (row) containing management information applicable to an address range that is used as part of the authorization of an identity within an authorization instance on this node.
.1.3.6.1.2.1.141.1.5.1.1.1,IPS-AUTH-MIB::ipsAuthIdentAddrIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular ipsAuthIdentAddress instance within an ipsAuthIdentity within an authorization instance present on the node. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.141.1.5.1.1.2,IPS-AUTH-MIB::ipsAuthIdentAddrType,INTEGER,read-create,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The address types used in the ipsAuthIdentAddrStart and ipsAuthAddrEnd objects. This type is taken from the IANA address family types.
.1.3.6.1.2.1.141.1.5.1.1.3,IPS-AUTH-MIB::ipsAuthIdentAddrStart,OCTET,read-create,,current,,The starting address of the allowed address range. The format of this object is determined by ipsAuthIdentAddrType.
.1.3.6.1.2.1.141.1.5.1.1.4,IPS-AUTH-MIB::ipsAuthIdentAddrEnd,OCTET,read-create,,current,,The ending address of the allowed address range. If the ipsAuthIdentAddrEntry specifies a single address, this shall match the ipsAuthIdentAddrStart. The format of this object is determined by ipsAuthIdentAddrType.
.1.3.6.1.2.1.141.1.5.1.1.5,IPS-AUTH-MIB::ipsAuthIdentAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The values of ipsAuthIdentAddrStart and ipsAuthIdentAddrEnd may be set when this value is 'active'. The value of ipsAuthIdentAddrType may not be set when this value is 'active'.
.1.3.6.1.2.1.141.1.5.1.1.6,IPS-AUTH-MIB::ipsAuthIdentAddrStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.1.6,IPS-AUTH-MIB::ipsAuthCredential,,,,,,
.1.3.6.1.2.1.141.1.6.1,IPS-AUTH-MIB::ipsAuthCredentialAttributesTable,,not-accessible,,current,,A list of credentials related to user identities that are allowed as valid authenticators of the particular identity.
.1.3.6.1.2.1.141.1.6.1.1,IPS-AUTH-MIB::ipsAuthCredentialAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex:ipsAuthCredIndex,current,,An entry (row) containing management information applicable to a credential that verifies a user identity within an authorization instance. To provide complete information in this MIB for a credential, the management station must not only create the row in this table but must also create a row in another table, where the other table is determined by the value of ipsAuthCredAuthMethod, e.g., if ipsAuthCredAuthMethod has the value ipsAuthMethodChap, a row must be created in the ipsAuthCredChapAttributesTable.
.1.3.6.1.2.1.141.1.6.1.1.1,IPS-AUTH-MIB::ipsAuthCredIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular Credential instance within an instance present on the node. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.141.1.6.1.1.2,IPS-AUTH-MIB::ipsAuthCredAuthMethod,OBJECT,read-create,,current,,This object contains an OBJECT IDENTIFIER that identifies the authentication method used with this credential. When a row is created in this table, a corresponding row must be created by the management station in a corresponding table specified by this value. When a row is deleted from this table, the corresponding row must be automatically deleted by the agent in the corresponding table specified by this value. If the value of this object is ipsAuthMethodNone, no corresponding rows are created or deleted from other tables. Some standardized values for this object are defined within the ipsAuthMethodTypes subtree.
.1.3.6.1.2.1.141.1.6.1.1.3,IPS-AUTH-MIB::ipsAuthCredRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The value of ipsAuthCredAuthMethod must not be changed while this row is 'active'.
.1.3.6.1.2.1.141.1.6.1.1.4,IPS-AUTH-MIB::ipsAuthCredStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.1.7,IPS-AUTH-MIB::ipsAuthCredChap,,,,,,
.1.3.6.1.2.1.141.1.7.1,IPS-AUTH-MIB::ipsAuthCredChapAttributesTable,,not-accessible,,current,,A list of CHAP attributes for credentials that use ipsAuthMethodChap as their ipsAuthCredAuthMethod. A row in this table can only exist when an instance of the ipsAuthCredAuthMethod object exists (or is created simultaneously) having the same instance identifiers and a value of 'ipsAuthMethodChap'.
.1.3.6.1.2.1.141.1.7.1.1,IPS-AUTH-MIB::ipsAuthCredChapAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex:ipsAuthCredIndex,current,,An entry (row) containing management information applicable to a credential that uses ipsAuthMethodChap as their ipsAuthCredAuthMethod. When a row is created in ipsAuthCredentialAttributesTable with ipsAuthCredAuthMethod = ipsAuthCredChap, the management station must create a corresponding row in this table. When a row is deleted from ipsAuthCredentialAttributesTable with ipsAuthCredAuthMethod = ipsAuthCredChap, the agent must delete the corresponding row (if any) in this table.
.1.3.6.1.2.1.141.1.7.1.1.1,IPS-AUTH-MIB::ipsAuthCredChapUserName,OCTET,read-create,,current,,A character string containing the CHAP user name for this credential.
.1.3.6.1.2.1.141.1.7.1.1.2,IPS-AUTH-MIB::ipsAuthCredChapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The value of ipsAuthCredChapUserName may be changed while this row is 'active'.
.1.3.6.1.2.1.141.1.7.1.1.3,IPS-AUTH-MIB::ipsAuthCredChapStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.1.8,IPS-AUTH-MIB::ipsAuthCredSrp,,,,,,
.1.3.6.1.2.1.141.1.8.1,IPS-AUTH-MIB::ipsAuthCredSrpAttributesTable,,not-accessible,,current,,A list of SRP attributes for credentials that use ipsAuthMethodSrp as its ipsAuthCredAuthMethod. A row in this table can only exist when an instance of the ipsAuthCredAuthMethod object exists (or is created simultaneously) having the same instance identifiers and a value of 'ipsAuthMethodSrp'.
.1.3.6.1.2.1.141.1.8.1.1,IPS-AUTH-MIB::ipsAuthCredSrpAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex:ipsAuthCredIndex,current,,An entry (row) containing management information applicable to a credential that uses ipsAuthMethodSrp as their ipsAuthCredAuthMethod. When a row is created in ipsAuthCredentialAttributesTable with ipsAuthCredAuthMethod = ipsAuthCredSrp, the management station must create a corresponding row in this table. When a row is deleted from ipsAuthCredentialAttributesTable with ipsAuthCredAuthMethod = ipsAuthCredSrp, the agent must delete the corresponding row (if any) in this table.
.1.3.6.1.2.1.141.1.8.1.1.1,IPS-AUTH-MIB::ipsAuthCredSrpUserName,OCTET,read-create,,current,,A character string containing the SRP user name for this credential.
.1.3.6.1.2.1.141.1.8.1.1.2,IPS-AUTH-MIB::ipsAuthCredSrpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The value of ipsAuthCredSrpUserName may be changed while the status of this row is 'active'.
.1.3.6.1.2.1.141.1.8.1.1.3,IPS-AUTH-MIB::ipsAuthCredSrpStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.1.9,IPS-AUTH-MIB::ipsAuthCredKerberos,,,,,,
.1.3.6.1.2.1.141.1.9.1,IPS-AUTH-MIB::ipsAuthCredKerbAttributesTable,,not-accessible,,current,,A list of Kerberos attributes for credentials that use ipsAuthMethodKerberos as their ipsAuthCredAuthMethod. A row in this table can only exist when an instance of the ipsAuthCredAuthMethod object exists (or is created simultaneously) having the same instance identifiers and a value of 'ipsAuthMethodKerb'.
.1.3.6.1.2.1.141.1.9.1.1,IPS-AUTH-MIB::ipsAuthCredKerbAttributesEntry,,not-accessible,ipsAuthInstIndex:ipsAuthIdentIndex:ipsAuthCredIndex,current,,An entry (row) containing management information applicable to a credential that uses ipsAuthMethodKerberos as its ipsAuthCredAuthMethod. When a row is created in ipsAuthCredentialAttributesTable with ipsAuthCredAuthMethod = ipsAuthCredKerberos, the management station must create a corresponding row in this table. When a row is deleted from ipsAuthCredentialAttributesTable with ipsAuthCredAuthMethod = ipsAuthCredKerberos, the agent must delete the corresponding row (if any) in this table.
.1.3.6.1.2.1.141.1.9.1.1.1,IPS-AUTH-MIB::ipsAuthCredKerbPrincipal,OCTET,read-create,,current,,A character string containing a Kerberos principal for this credential.
.1.3.6.1.2.1.141.1.9.1.1.2,IPS-AUTH-MIB::ipsAuthCredKerbRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. Rows may be discarded using RowStatus. The value of ipsAuthCredKerbPrincipal may be changed while this row is 'active'.
.1.3.6.1.2.1.141.1.9.1.1.3,IPS-AUTH-MIB::ipsAuthCredKerbStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-create objects in this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.141.2,IPS-AUTH-MIB::ipsAuthConformance,,,,,,
.1.3.6.1.2.1.141.2.1,IPS-AUTH-MIB::ipsAuthCompliances,,,,,,
.1.3.6.1.2.1.141.2.1.1,IPS-AUTH-MIB::ipsAuthComplianceV1,,,,,,Initial version of compliance statement based on initial version of this MIB module. The Instance and Identity groups are mandatory; at least one of the other groups (Name, Address, Credential, Certificate) is also mandatory for any given implementation.
.1.3.6.1.2.1.141.2.2,IPS-AUTH-MIB::ipsAuthGroups,,,,,,
.1.3.6.1.2.1.141.2.2.1,IPS-AUTH-MIB::ipsAuthInstanceAttributesGroup,,,,,,A collection of objects providing information about authorization instances.
.1.3.6.1.2.1.141.2.2.2,IPS-AUTH-MIB::ipsAuthIdentAttributesGroup,,,,,,A collection of objects providing information about user identities within an authorization instance.
.1.3.6.1.2.1.141.2.2.3,IPS-AUTH-MIB::ipsAuthIdentNameAttributesGroup,,,,,,A collection of objects providing information about user names within user identities within an authorization instance.
.1.3.6.1.2.1.141.2.2.4,IPS-AUTH-MIB::ipsAuthIdentAddrAttributesGroup,,,,,,A collection of objects providing information about address ranges within user identities within an authorization instance.
.1.3.6.1.2.1.141.2.2.5,IPS-AUTH-MIB::ipsAuthIdentCredAttributesGroup,,,,,,A collection of objects providing information about credentials within user identities within an authorization instance.
.1.3.6.1.2.1.141.2.2.6,IPS-AUTH-MIB::ipsAuthIdentChapAttrGroup,,,,,,A collection of objects providing information about CHAP credentials within user identities within an authorization instance.
.1.3.6.1.2.1.141.2.2.7,IPS-AUTH-MIB::ipsAuthIdentSrpAttrGroup,,,,,,A collection of objects providing information about SRP credentials within user identities within an authorization instance.
.1.3.6.1.2.1.141.2.2.8,IPS-AUTH-MIB::ipsAuthIdentKerberosAttrGroup,,,,,,A collection of objects providing information about Kerberos credentials within user identities within an authorization instance.
.1.3.6.1.2.1.142,ISCSI-MIB::iscsiMibModule,,,,,,This module defines management information specific to the iSCSI protocol. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.142.0,ISCSI-MIB::iscsiNotifications,,,,,,
.1.3.6.1.2.1.142.0.1,ISCSI-MIB::iscsiTgtLoginFailure,,,,,,Sent when a login is failed by a target. To avoid sending an excessive number of notifications due to multiple errors counted, an SNMP agent implementing this notification SHOULD NOT send more than 3 notifications of this type in any 10-second time period.
.1.3.6.1.2.1.142.0.2,ISCSI-MIB::iscsiIntrLoginFailure,,,,,,Sent when a login is failed by an initiator. To avoid sending an excessive number of notifications due to multiple errors counted, an SNMP agent implementing this notification SHOULD NOT send more than 3 notifications of this type in any 10-second time period.
.1.3.6.1.2.1.142.0.3,ISCSI-MIB::iscsiInstSessionFailure,,,,,,Sent when an active session is failed by either the initiator or the target. To avoid sending an excessive number of notifications due to multiple errors counted, an SNMP agent implementing this notification SHOULD NOT send more than 3 notifications of this type in any 10-second time period.
.1.3.6.1.2.1.142.1,ISCSI-MIB::iscsiObjects,,,,,,
.1.3.6.1.2.1.142.1.1,ISCSI-MIB::iscsiInstance,,,,,,
.1.3.6.1.2.1.142.1.1.1,ISCSI-MIB::iscsiInstanceAttributesTable,,not-accessible,,current,,A list of iSCSI instances present on the system.
.1.3.6.1.2.1.142.1.1.1.1,ISCSI-MIB::iscsiInstanceAttributesEntry,,not-accessible,iscsiInstIndex,current,,An entry (row) containing management information applicable to a particular iSCSI instance.
.1.3.6.1.2.1.142.1.1.1.1.1,ISCSI-MIB::iscsiInstIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular iSCSI instance. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.142.1.1.1.1.2,ISCSI-MIB::iscsiInstDescr,OCTET,read-only,,current,,A UTF-8 string, determined by the implementation to describe the iSCSI instance. When only a single instance is present, this object may be set to the zero-length string; with multiple iSCSI instances, it may be used in an implementation-dependent manner to describe the purpose of the respective instance.
.1.3.6.1.2.1.142.1.1.1.1.3,ISCSI-MIB::iscsiInstVersionMin,Unsigned32,read-only,,current,,The minimum version number of the iSCSI specification such that this iSCSI instance supports this minimum value, the maximum value indicated by the corresponding instance in iscsiInstVersionMax, and all versions in between.
.1.3.6.1.2.1.142.1.1.1.1.4,ISCSI-MIB::iscsiInstVersionMax,Unsigned32,read-only,,current,,The maximum version number of the iSCSI specification such that this iSCSI instance supports this maximum value, the minimum value indicated by the corresponding instance in iscsiInstVersionMin, and all versions in between.
.1.3.6.1.2.1.142.1.1.1.1.5,ISCSI-MIB::iscsiInstVendorID,OCTET,read-only,,current,,A UTF-8 string describing the manufacturer of the implementation of this instance.
.1.3.6.1.2.1.142.1.1.1.1.6,ISCSI-MIB::iscsiInstVendorVersion,OCTET,read-only,,current,,A UTF-8 string set by the manufacturer describing the version of the implementation of this instance. The format of this string is determined solely by the manufacturer; the string is for informational purposes only. It is unrelated to the iSCSI specification version numbers.
.1.3.6.1.2.1.142.1.1.1.1.7,ISCSI-MIB::iscsiInstPortalNumber,Unsigned32,read-only,,current,,The number of rows in the iscsiPortalAttributesTable that are currently associated with this iSCSI instance.
.1.3.6.1.2.1.142.1.1.1.1.8,ISCSI-MIB::iscsiInstNodeNumber,Unsigned32,read-only,,current,,The number of rows in the iscsiNodeAttributesTable that are currently associated with this iSCSI instance.
.1.3.6.1.2.1.142.1.1.1.1.9,ISCSI-MIB::iscsiInstSessionNumber,Unsigned32,read-only,,current,,The number of rows in the iscsiSessionAttributesTable that are currently associated with this iSCSI instance.
.1.3.6.1.2.1.142.1.1.1.1.10,ISCSI-MIB::iscsiInstSsnFailures,Counter32,read-only,,current,,This object counts the number of times a session belonging to this instance has failed. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiInstDiscontinuityTime.
.1.3.6.1.2.1.142.1.1.1.1.11,ISCSI-MIB::iscsiInstLastSsnFailureType,OBJECT,read-only,,current,,The counter object in the iscsiInstanceSsnErrorStatsTable that was incremented when the last session failure occurred. If the reason for failure is not found in the iscsiInstanceSsnErrorStatsTable, the value { 0.0 } is used instead.
.1.3.6.1.2.1.142.1.1.1.1.12,ISCSI-MIB::iscsiInstLastSsnRmtNodeName,OCTET,read-only,,current,,The iSCSI name of the remote node from the failed session.
.1.3.6.1.2.1.142.1.1.1.1.13,ISCSI-MIB::iscsiInstDiscontinuityTime,TimeTicks,read-only,,current,,The value of SysUpTime on the most recent occasion at which any one or more of this instance's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.142.1.1.1.1.14,ISCSI-MIB::iscsiInstXNodeArchitecture,OCTET,read-only,,current,,A UTF-8 string set by the manufacturer declaring the details of its iSCSI node architecture to the remote endpoint. These details may include, but are not limited to, iSCSI vendor software, firmware, or hardware versions, the OS version, or hardware architecture. The format of this string is determined solely by the manufacturer; the string is for informational purposes only. It is unrelated to the iSCSI specification version numbers.
.1.3.6.1.2.1.142.1.1.2,ISCSI-MIB::iscsiInstanceSsnErrorStatsTable,,not-accessible,,current,,Statistics regarding the occurrences of error types that result in a session failure.
.1.3.6.1.2.1.142.1.1.2.1,ISCSI-MIB::iscsiInstanceSsnErrorStatsEntry,,not-accessible,,current,,An entry (row) containing management information applicable to a particular iSCSI instance.
.1.3.6.1.2.1.142.1.1.2.1.1,ISCSI-MIB::iscsiInstSsnDigestErrors,Counter32,read-only,,current,,The count of sessions that failed due to receipt of a PDU containing header or data digest errors. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiInstDiscontinuityTime.
.1.3.6.1.2.1.142.1.1.2.1.2,ISCSI-MIB::iscsiInstSsnCxnTimeoutErrors,Counter32,read-only,,current,,The count of sessions that failed due to a sequence exceeding a time limit. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiInstDiscontinuityTime.
.1.3.6.1.2.1.142.1.1.2.1.3,ISCSI-MIB::iscsiInstSsnFormatErrors,Counter32,read-only,,current,,The count of sessions that failed due to receipt of a PDU that contained a format error. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiInstDiscontinuityTime.
.1.3.6.1.2.1.142.1.1.2.1.4,ISCSI-MIB::iscsiInstSsnTgtUnmappedErrors,Counter32,read-only,,current,,The count of sessions that failed due to the target becoming unmapped. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiInstDiscontinuityTime.
.1.3.6.1.2.1.142.1.2,ISCSI-MIB::iscsiPortal,,,,,,
.1.3.6.1.2.1.142.1.2.1,ISCSI-MIB::iscsiPortalAttributesTable,,not-accessible,,current,,A list of transport endpoints (using TCP or another transport protocol) used by this iSCSI instance. An iSCSI instance may use a portal to listen for incoming connections to its targets, to initiate connections to other targets, or both.
.1.3.6.1.2.1.142.1.2.1.1,ISCSI-MIB::iscsiPortalAttributesEntry,,not-accessible,iscsiInstIndex:iscsiPortalIndex,current,,An entry (row) containing management information applicable to a particular portal instance.
.1.3.6.1.2.1.142.1.2.1.1.1,ISCSI-MIB::iscsiPortalIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular transport endpoint within this iSCSI instance. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.142.1.2.1.1.2,ISCSI-MIB::iscsiPortalRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. When the value of this object is 'active', the values of the other objects in this table cannot be changed. Rows may be discarded using RowStatus. Note that creating a row in this table will typically cause the agent to create one or more rows in the iscsiTgtPortalAttributesTable and/or the iscsiIntrPortalAttributesTable.
.1.3.6.1.2.1.142.1.2.1.1.3,ISCSI-MIB::iscsiPortalRoles,BITS,read-create,,current,targetTypePortal(0):initiatorTypePortal(1),A portal can operate in one or both of two roles: as a target portal and/or an initiator portal. If the portal will operate in both roles, both bits must be set. This object will define a corresponding row that will exist or must be created in the iscsiTgtPortalAttributesTable, the iscsiIntrPortalAttributesTable, or both. If the targetTypePortal bit is set, one or more corresponding iscsiTgtPortalAttributesEntry rows will be found or created. If the initiatorTypePortal bit is set, one or more corresponding iscsiIntrPortalAttributesEntry rows will be found or created. If both bits are set, one or more corresponding rows will be found or created in one of the above tables.
.1.3.6.1.2.1.142.1.2.1.1.4,ISCSI-MIB::iscsiPortalAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet Network Address contained in the corresponding instance of the iscsiPortalAddr.
.1.3.6.1.2.1.142.1.2.1.1.5,ISCSI-MIB::iscsiPortalAddr,OCTET,read-create,,current,,The portal's Internet Network Address, of the type specified by the object iscsiPortalAddrType. If iscsiPortalAddrType has the value 'dns', this address gets resolved to an IP address whenever a new iSCSI connection is established using this portal.
.1.3.6.1.2.1.142.1.2.1.1.6,ISCSI-MIB::iscsiPortalProtocol,Unsigned32,read-create,,current,,The portal's transport protocol.
.1.3.6.1.2.1.142.1.2.1.1.7,ISCSI-MIB::iscsiPortalMaxRecvDataSegLength,Unsigned32,read-create,,current,,The maximum PDU length this portal can receive. This may be constrained by hardware characteristics, and individual implementations may choose not to allow this object to be changed.
.1.3.6.1.2.1.142.1.2.1.1.8,ISCSI-MIB::iscsiPortalPrimaryHdrDigest,INTEGER,read-create,,current,none(1):other(2):noDigest(3):crc32c(4),The preferred header digest for this portal.
.1.3.6.1.2.1.142.1.2.1.1.9,ISCSI-MIB::iscsiPortalPrimaryDataDigest,INTEGER,read-create,,current,none(1):other(2):noDigest(3):crc32c(4),The preferred data digest method for this portal.
.1.3.6.1.2.1.142.1.2.1.1.10,ISCSI-MIB::iscsiPortalSecondaryHdrDigest,INTEGER,read-create,,current,none(1):other(2):noDigest(3):crc32c(4),An alternate header digest preference for this portal.
.1.3.6.1.2.1.142.1.2.1.1.11,ISCSI-MIB::iscsiPortalSecondaryDataDigest,INTEGER,read-create,,current,none(1):other(2):noDigest(3):crc32c(4),An alternate data digest preference for this portal.
.1.3.6.1.2.1.142.1.2.1.1.12,ISCSI-MIB::iscsiPortalRecvMarker,INTEGER,read-create,,deprecated,true(1):false(2),This object indicates whether or not this portal will request markers in its incoming data stream.
.1.3.6.1.2.1.142.1.2.1.1.13,ISCSI-MIB::iscsiPortalStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process (e.g., not created via this MIB) may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.142.1.2.1.1.14,ISCSI-MIB::iscsiPortalDescr,OCTET,read-only,,current,,A UTF-8 string, determined by the implementation to describe the iSCSI portal. When only a single instance is present, this object may be set to the zero-length string; with multiple iSCSI portals, it may be used in an implementation-dependent manner to describe the respective portal, and could include information such as Host Bus Adapter (HBA) model, description, and version, or software driver and version.
.1.3.6.1.2.1.142.1.3,ISCSI-MIB::iscsiTargetPortal,,,,,,
.1.3.6.1.2.1.142.1.3.1,ISCSI-MIB::iscsiTgtPortalAttributesTable,,not-accessible,,current,,A list of transport endpoints (using TCP or another transport protocol) on which this iSCSI instance listens for incoming connections to its targets.
.1.3.6.1.2.1.142.1.3.1.1,ISCSI-MIB::iscsiTgtPortalAttributesEntry,,not-accessible,iscsiInstIndex:iscsiPortalIndex:iscsiTgtPortalNodeIndexOrZero,current,,An entry (row) containing management information applicable to a particular portal instance that is used to listen for incoming connections to local targets. One or more rows in this table is populated by the agent for each iscsiPortalAttributesEntry row that has the bit targetTypePortal set in its iscsiPortalRoles column.
.1.3.6.1.2.1.142.1.3.1.1.1,ISCSI-MIB::iscsiTgtPortalNodeIndexOrZero,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular node within an iSCSI instance present on the local system. For implementations where each {portal, node} tuple can have a different portal tag, this value will map to the iscsiNodeIndex. For implementations where the portal tag is the same for a given portal regardless of which node is using the portal, the value 0 (zero) is used.
.1.3.6.1.2.1.142.1.3.1.1.2,ISCSI-MIB::iscsiTgtPortalPort,Unsigned32,read-write,,current,,The portal's transport protocol port number on which the portal listens for incoming iSCSI connections when the portal is used as a target portal. This object's storage type is specified in iscsiPortalStorageType.
.1.3.6.1.2.1.142.1.3.1.1.3,ISCSI-MIB::iscsiTgtPortalTag,Unsigned32,read-write,,current,,The portal's aggregation tag when the portal is used as a target portal. Multiple-connection sessions may be aggregated over portals sharing an identical aggregation tag. This object's storage type is specified in iscsiPortalStorageType.
.1.3.6.1.2.1.142.1.4,ISCSI-MIB::iscsiInitiatorPortal,,,,,,
.1.3.6.1.2.1.142.1.4.1,ISCSI-MIB::iscsiIntrPortalAttributesTable,,not-accessible,,current,,A list of Internet Network Addresses (using TCP or another transport protocol) from which this iSCSI instance may initiate connections to other targets.
.1.3.6.1.2.1.142.1.4.1.1,ISCSI-MIB::iscsiIntrPortalAttributesEntry,,not-accessible,iscsiInstIndex:iscsiPortalIndex:iscsiIntrPortalNodeIndexOrZero,current,,An entry (row) containing management information applicable to a particular portal instance that is used to initiate connections to iSCSI targets. One or more rows in this table is populated by the agent for each iscsiPortalAttributesEntry row that has the bit initiatorTypePortal set in its iscsiPortalRoles column.
.1.3.6.1.2.1.142.1.4.1.1.1,ISCSI-MIB::iscsiIntrPortalNodeIndexOrZero,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular node within an iSCSI instance present on the local system. For implementations where each {portal, node} tuple can have a different portal tag, this value will map to the iscsiNodeIndex. For implementations where the portal tag is the same for a given portal regardless of which node is using the portal, the value 0 (zero) is used.
.1.3.6.1.2.1.142.1.4.1.1.2,ISCSI-MIB::iscsiIntrPortalTag,Unsigned32,read-write,,current,,The portal's aggregation tag when the portal is used as an initiator portal. Multiple-connection sessions may be aggregated over portals sharing an identical aggregation tag. This object's storage type is specified in iscsiPortalStorageType.
.1.3.6.1.2.1.142.1.5,ISCSI-MIB::iscsiNode,,,,,,
.1.3.6.1.2.1.142.1.5.1,ISCSI-MIB::iscsiNodeAttributesTable,,not-accessible,,current,,A list of iSCSI nodes belonging to each iSCSI instance present on the local system. An iSCSI node can act as an initiator, a target, or both.
.1.3.6.1.2.1.142.1.5.1.1,ISCSI-MIB::iscsiNodeAttributesEntry,,not-accessible,iscsiInstIndex:iscsiNodeIndex,current,,A conceptual row containing management information applicable to a particular iSCSI node.
.1.3.6.1.2.1.142.1.5.1.1.1,ISCSI-MIB::iscsiNodeIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular node within an iSCSI instance. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.142.1.5.1.1.2,ISCSI-MIB::iscsiNodeName,OCTET,read-only,,current,,This node's iSCSI name, which is independent of the location of the node, and can be resolved into a set of addresses through various discovery services.
.1.3.6.1.2.1.142.1.5.1.1.3,ISCSI-MIB::iscsiNodeAlias,OCTET,read-only,,current,,A character string that is a human-readable name or description of the iSCSI node. If configured, this alias may be communicated to the initiator or target node at the remote end of the connection during a Login Request or Response message. This string is not used as an identifier, but it can be displayed by the system's user interface in a list of initiators and/or targets to which it is connected. If no alias exists, the value is a zero-length string.
.1.3.6.1.2.1.142.1.5.1.1.4,ISCSI-MIB::iscsiNodeRoles,BITS,read-only,,current,targetTypeNode(0):initiatorTypeNode(1),A node can operate in one or both of two roles: a target role and/or an initiator role. If the node will operate in both roles, both bits must be set. This object will also define the corresponding rows that will exist in the iscsiTargetAttributesTable, the iscsiInitiatorAttributesTable, or both. If the targetTypeNode bit is set, there will be a corresponding iscsiTargetAttributesEntry. If the initiatorTypeNode bit is set, there will be a corresponding iscsiInitiatorAttributesEntry. If both bits are set, there will be a corresponding iscsiTgtPortalAttributesEntry and iscsiPortalAttributesEntry.
.1.3.6.1.2.1.142.1.5.1.1.5,ISCSI-MIB::iscsiNodeTransportType,OBJECT,read-only,,current,,A pointer to the corresponding row in the appropriate table for this SCSI transport, thereby allowing management stations to locate the SCSI-level device that is represented by this iscsiNode. For example, it will usually point to the corresponding scsiTrnspt object in the SCSI MIB module. If no corresponding row exists, the value 0.0 must be used to indicate this.
.1.3.6.1.2.1.142.1.5.1.1.6,ISCSI-MIB::iscsiNodeInitialR2T,INTEGER,read-only,,current,true(1):false(2),This object indicates the InitialR2T preference for this node: true = YES, false = will try to negotiate NO, will accept YES 
.1.3.6.1.2.1.142.1.5.1.1.7,ISCSI-MIB::iscsiNodeImmediateData,INTEGER,read-write,,current,true(1):false(2),This object indicates ImmediateData preference for this node: true = YES (but will accept NO), false = NO 
.1.3.6.1.2.1.142.1.5.1.1.8,ISCSI-MIB::iscsiNodeMaxOutstandingR2T,Unsigned32,read-write,,current,,Maximum number of outstanding requests-to-transmit (R2Ts) allowed per iSCSI task.
.1.3.6.1.2.1.142.1.5.1.1.9,ISCSI-MIB::iscsiNodeFirstBurstLength,Unsigned32,read-write,,current,,The maximum length (bytes) supported for unsolicited data to/from this node.
.1.3.6.1.2.1.142.1.5.1.1.10,ISCSI-MIB::iscsiNodeMaxBurstLength,Unsigned32,read-write,,current,,The maximum number of bytes that can be sent within a single sequence of Data-In or Data-Out PDUs.
.1.3.6.1.2.1.142.1.5.1.1.11,ISCSI-MIB::iscsiNodeMaxConnections,Unsigned32,read-write,,current,,The maximum number of connections allowed in each session to and/or from this node.
.1.3.6.1.2.1.142.1.5.1.1.12,ISCSI-MIB::iscsiNodeDataSequenceInOrder,INTEGER,read-write,,current,true(1):false(2),The DataSequenceInOrder preference of this node. False (=No) indicates that iSCSI data PDU sequences may be transferred in any order. True (=Yes) indicates that data PDU sequences must be transferred using continuously increasing offsets, except during error recovery.
.1.3.6.1.2.1.142.1.5.1.1.13,ISCSI-MIB::iscsiNodeDataPDUInOrder,INTEGER,read-write,,current,true(1):false(2),The DataPDUInOrder preference of this node. False (=No) indicates that iSCSI data PDUs within sequences may be in any order. True (=Yes) indicates that data PDUs within sequences must be at continuously increasing addresses, with no gaps or overlay between PDUs.
.1.3.6.1.2.1.142.1.5.1.1.14,ISCSI-MIB::iscsiNodeDefaultTime2Wait,Unsigned32,read-write,,current,,The DefaultTime2Wait preference of this node. This is the minimum time, in seconds, to wait before attempting an explicit/implicit logout or active iSCSI task reassignment after an unexpected connection termination or a connection reset.
.1.3.6.1.2.1.142.1.5.1.1.15,ISCSI-MIB::iscsiNodeDefaultTime2Retain,Unsigned32,read-write,,current,,The DefaultTime2Retain preference of this node. This is the maximum time, in seconds after an initial wait (Time2Wait), before which an active iSCSI task reassignment is still possible after an unexpected connection termination or a connection reset.
.1.3.6.1.2.1.142.1.5.1.1.16,ISCSI-MIB::iscsiNodeErrorRecoveryLevel,Unsigned32,read-write,,current,,The ErrorRecoveryLevel preference of this node. Currently, only 0-2 are valid. This object is designed to accommodate future error-recovery levels. Higher error-recovery levels imply support in addition to support for the lower error level functions. In other words, error level 2 implies support for levels 0-1, since those functions are subsets of error level 2.
.1.3.6.1.2.1.142.1.5.1.1.17,ISCSI-MIB::iscsiNodeDiscontinuityTime,TimeTicks,read-only,,current,,The value of SysUpTime on the most recent occasion at which any one or more of this node's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.142.1.5.1.1.18,ISCSI-MIB::iscsiNodeStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-write objects within this row. Rows in this table are always created via an external process (e.g., not created via this MIB module). Conceptual rows having the value 'permanent' need not allow Write access to any columnar objects in the row. If this object has the value 'volatile', modifications to read-write objects in this row are not persistent across reboots. If this object has the value 'nonVolatile', modifications to objects in this row are persistent. An implementation may choose to allow this object to be set to either 'nonVolatile' or 'volatile', allowing the management application to choose this behavior.
.1.3.6.1.2.1.142.1.6,ISCSI-MIB::iscsiTarget,,,,,,
.1.3.6.1.2.1.142.1.6.1,ISCSI-MIB::iscsiTargetAttributesTable,,not-accessible,,current,,A list of iSCSI nodes that can take on a target role, belonging to each iSCSI instance present on the local system.
.1.3.6.1.2.1.142.1.6.1.1,ISCSI-MIB::iscsiTargetAttributesEntry,,not-accessible,iscsiInstIndex:iscsiNodeIndex,current,,An entry (row) containing management information applicable to a particular node that can take on a target role.
.1.3.6.1.2.1.142.1.6.1.1.1,ISCSI-MIB::iscsiTgtLoginFailures,Counter32,read-only,,current,,This object counts the number of times a login attempt to this local target has failed. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.1.1.2,ISCSI-MIB::iscsiTgtLastFailureTime,TimeTicks,read-only,,current,,The timestamp of the most recent failure of a login attempt to this target. A value of zero indicates that no such failures have occurred since the last system boot.
.1.3.6.1.2.1.142.1.6.1.1.3,ISCSI-MIB::iscsiTgtLastFailureType,OBJECT,read-only,,current,,The type of the most recent failure of a login attempt to this target, represented as the OID of the counter object in iscsiTargetLoginStatsTable for which the relevant instance was incremented. If no such failures have occurred since the last system boot, this attribute will have the value 0.0. A value of 0.0 may also be used to indicate a type that is not represented by any of the counters in iscsiTargetLoginStatsTable.
.1.3.6.1.2.1.142.1.6.1.1.4,ISCSI-MIB::iscsiTgtLastIntrFailureName,OCTET,read-only,,current,,The iSCSI name of the initiator that failed the last login attempt. If no such failures have occurred since the last system boot, this value is a zero-length string.
.1.3.6.1.2.1.142.1.6.1.1.5,ISCSI-MIB::iscsiTgtLastIntrFailureAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet Network Address contained in the corresponding instance of the iscsiTgtLastIntrFailureAddr. The value 'dns' is not allowed. If no such failures have occurred since the last system boot, this value is zero.
.1.3.6.1.2.1.142.1.6.1.1.6,ISCSI-MIB::iscsiTgtLastIntrFailureAddr,OCTET,read-only,,current,,An Internet Network Address, of the type specified by the object iscsiTgtLastIntrFailureAddrType, giving the host address of the initiator that failed the last login attempt. If no such failures have occurred since the last system boot, this value is a zero-length string.
.1.3.6.1.2.1.142.1.6.1.1.7,ISCSI-MIB::iscsiTgtLastIntrFailurePort,Unsigned32,read-only,,current,,The transport protocol port number used by the initiator that failed the last login attempt. If no such failures have occurred since the last system boot, this value is a zero-length string.
.1.3.6.1.2.1.142.1.6.2,ISCSI-MIB::iscsiTargetLoginStatsTable,,not-accessible,,current,,A table of counters that keep a record of the results of initiators' login attempts to this target.
.1.3.6.1.2.1.142.1.6.2.1,ISCSI-MIB::iscsiTargetLoginStatsEntry,,not-accessible,,current,,An entry (row) containing counters for each result of a login attempt to this target.
.1.3.6.1.2.1.142.1.6.2.1.1,ISCSI-MIB::iscsiTgtLoginAccepts,Counter32,read-only,,current,,The count of Login Response PDUs with status 0x0000, Accept Login, transmitted by this target. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.2.1.2,ISCSI-MIB::iscsiTgtLoginOtherFails,Counter32,read-only,,current,,The number of Login Response PDUs that were transmitted by this target and that were not counted by any other object in the row. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.2.1.3,ISCSI-MIB::iscsiTgtLoginRedirects,Counter32,read-only,,current,,The count of Login Response PDUs with status class 0x01, Redirection, transmitted by this target. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.2.1.4,ISCSI-MIB::iscsiTgtLoginAuthorizeFails,Counter32,read-only,,current,,The count of Login Response PDUs with status 0x0202, Forbidden Target, transmitted by this target. If this counter is incremented, an iscsiTgtLoginFailure notification should be generated. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.2.1.5,ISCSI-MIB::iscsiTgtLoginAuthenticateFails,Counter32,read-only,,current,,The count of Login Response PDUs with status 0x0201, Authentication Failed, transmitted by this target. If this counter is incremented, an iscsiTgtLoginFailure notification should be generated. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.2.1.6,ISCSI-MIB::iscsiTgtLoginNegotiateFails,Counter32,read-only,,current,,The number of times a target has effectively refused a login because the parameter negotiation failed. If this counter is incremented, an iscsiTgtLoginFailure notification should be generated. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.3,ISCSI-MIB::iscsiTargetLogoutStatsTable,,not-accessible,,current,,When a target receives a Logout command, it responds with a Logout Response that carries a status code. This table contains counters for both normal and abnormal Logout Requests received by this target.
.1.3.6.1.2.1.142.1.6.3.1,ISCSI-MIB::iscsiTargetLogoutStatsEntry,,not-accessible,,current,,An entry (row) containing counters of Logout Response PDUs that were received by this target.
.1.3.6.1.2.1.142.1.6.3.1.1,ISCSI-MIB::iscsiTgtLogoutNormals,Counter32,read-only,,current,,The count of Logout Command PDUs received by this target, with reason code 0 (closes the session). If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.3.1.2,ISCSI-MIB::iscsiTgtLogoutOthers,Counter32,read-only,,current,,The count of Logout Command PDUs received by this target, with any reason code other than 0. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.3.1.3,ISCSI-MIB::iscsiTgtLogoutCxnClosed,Counter32,read-only,,current,,The count of Logout Command PDUs received by this target, with reason code 1 (closes the connection). If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.6.3.1.4,ISCSI-MIB::iscsiTgtLogoutCxnRemoved,Counter32,read-only,,current,,The count of Logout Command PDUs received by this target, with reason code 2 (removes the connection). If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.7,ISCSI-MIB::iscsiTgtAuthorization,,,,,,
.1.3.6.1.2.1.142.1.7.1,ISCSI-MIB::iscsiTgtAuthAttributesTable,,not-accessible,,current,,A list of initiator identities that are authorized to access each target node within each iSCSI instance present on the local system.
.1.3.6.1.2.1.142.1.7.1.1,ISCSI-MIB::iscsiTgtAuthAttributesEntry,,not-accessible,iscsiInstIndex:iscsiNodeIndex:iscsiTgtAuthIndex,current,,An entry (row) containing management information applicable to a particular target node's authorized initiator identity.
.1.3.6.1.2.1.142.1.7.1.1.1,ISCSI-MIB::iscsiTgtAuthIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular target's authorized initiator identity within an iSCSI instance present on the local system. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.142.1.7.1.1.2,ISCSI-MIB::iscsiTgtAuthRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. When the value of this object is 'active', the values of the other objects in this table cannot be changed. Rows may be discarded using RowStatus.
.1.3.6.1.2.1.142.1.7.1.1.3,ISCSI-MIB::iscsiTgtAuthIdentity,OBJECT,read-create,,current,,A pointer to the corresponding user entry in the IPS-AUTH MIB module that will be allowed to access this iSCSI target.
.1.3.6.1.2.1.142.1.7.1.1.4,ISCSI-MIB::iscsiTgtAuthStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process (e.g., not created via this MIB) may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.142.1.8,ISCSI-MIB::iscsiInitiator,,,,,,
.1.3.6.1.2.1.142.1.8.1,ISCSI-MIB::iscsiInitiatorAttributesTable,,not-accessible,,current,,A list of iSCSI nodes that can take on an initiator role, belonging to each iSCSI instance present on the local system.
.1.3.6.1.2.1.142.1.8.1.1,ISCSI-MIB::iscsiInitiatorAttributesEntry,,not-accessible,iscsiInstIndex:iscsiNodeIndex,current,,An entry (row) containing management information applicable to a particular iSCSI node that has initiator capabilities.
.1.3.6.1.2.1.142.1.8.1.1.1,ISCSI-MIB::iscsiIntrLoginFailures,Counter32,read-only,,current,,This object counts the number of times a login attempt from this local initiator has failed. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.1.1.2,ISCSI-MIB::iscsiIntrLastFailureTime,TimeTicks,read-only,,current,,The timestamp of the most recent failure of a login attempt from this initiator. A value of zero indicates that no such failures have occurred since the last system boot.
.1.3.6.1.2.1.142.1.8.1.1.3,ISCSI-MIB::iscsiIntrLastFailureType,OBJECT,read-only,,current,,The type of the most recent failure of a login attempt from this initiator, represented as the OID of the counter object in iscsiInitiatorLoginStatsTable for which the relevant instance was incremented. If no such failures have occurred since the last system boot, this attribute will have the value 0.0. A value of 0.0 may also be used to indicate a type that is not represented by any of the counters in iscsiInitiatorLoginStatsTable.
.1.3.6.1.2.1.142.1.8.1.1.4,ISCSI-MIB::iscsiIntrLastTgtFailureName,OCTET,read-only,,current,,A UTF-8 string giving the name of the target that failed the last login attempt. If no such failures have occurred since the last system boot, this value is a zero-length string.
.1.3.6.1.2.1.142.1.8.1.1.5,ISCSI-MIB::iscsiIntrLastTgtFailureAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet Network Address contained in the corresponding instance of the iscsiIntrLastTgtFailureAddr. The value 'dns' is not allowed. If no such failures have occurred since the last system boot, this value is zero.
.1.3.6.1.2.1.142.1.8.1.1.6,ISCSI-MIB::iscsiIntrLastTgtFailureAddr,OCTET,read-only,,current,,An Internet Network Address, of the type specified by the object iscsiIntrLastTgtFailureAddrType, giving the host address of the target that failed the last login attempt. If no such failures have occurred since the last system boot, this value is a zero-length string.
.1.3.6.1.2.1.142.1.8.1.1.7,ISCSI-MIB::iscsiIntrLastTgtFailurePort,Unsigned32,read-only,,current,,The transport protocol port number used by the target that failed the last login attempt. If no such failures have occurred since the last system boot, this value is a zero-length string.
.1.3.6.1.2.1.142.1.8.2,ISCSI-MIB::iscsiInitiatorLoginStatsTable,,not-accessible,,current,,A table of counters that keep track of the results of this initiator's login attempts.
.1.3.6.1.2.1.142.1.8.2.1,ISCSI-MIB::iscsiInitiatorLoginStatsEntry,,not-accessible,,current,,An entry (row) containing counters of each result of this initiator's login attempts.
.1.3.6.1.2.1.142.1.8.2.1.1,ISCSI-MIB::iscsiIntrLoginAcceptRsps,Counter32,read-only,,current,,The count of Login Response PDUs with status 0x0000, Accept Login, received by this initiator. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.2.1.2,ISCSI-MIB::iscsiIntrLoginOtherFailRsps,Counter32,read-only,,current,,The count of Login Response PDUs received by this initiator with any status code not counted in the objects below. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.2.1.3,ISCSI-MIB::iscsiIntrLoginRedirectRsps,Counter32,read-only,,current,,The count of Login Response PDUs with status class 0x01, Redirection, received by this initiator. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.2.1.4,ISCSI-MIB::iscsiIntrLoginAuthFailRsps,Counter32,read-only,,current,,The count of Login Response PDUs with status class 0x201, Authentication Failed, received by this initiator. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.2.1.5,ISCSI-MIB::iscsiIntrLoginAuthenticateFails,Counter32,read-only,,current,,The number of times the initiator has aborted a login because the target could not be authenticated. No response is generated. If this counter is incremented, an iscsiIntrLoginFailure notification should be generated. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.2.1.6,ISCSI-MIB::iscsiIntrLoginNegotiateFails,Counter32,read-only,,current,,The number of times the initiator has aborted a login because parameter negotiation with the target failed. No response is generated. If this counter is incremented, an iscsiIntrLoginFailure notification should be generated. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.2.1.7,ISCSI-MIB::iscsiIntrLoginAuthorizeFails,Counter32,read-only,,current,,The count of Login Response PDUs with status 0x0202, Forbidden Target, received by this initiator. If this counter is incremented, an iscsiIntrLoginFailure notification should be generated. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.3,ISCSI-MIB::iscsiInitiatorLogoutStatsTable,,not-accessible,,current,,When an initiator attempts to send a Logout command, the target responds with a Logout Response that carries a status code. This table contains a list of counters of Logout Response PDUs of each status code that was received by each initiator belonging to this iSCSI instance present on this system.
.1.3.6.1.2.1.142.1.8.3.1,ISCSI-MIB::iscsiInitiatorLogoutStatsEntry,,not-accessible,,current,,An entry (row) containing counters of Logout Response PDUs of each status code that was generated by this initiator.
.1.3.6.1.2.1.142.1.8.3.1.1,ISCSI-MIB::iscsiIntrLogoutNormals,Counter32,read-only,,current,,The count of Logout Command PDUs generated by this initiator with reason code 0 (closes the session). If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.8.3.1.2,ISCSI-MIB::iscsiIntrLogoutOthers,Counter32,read-only,,current,,The count of Logout Command PDUs generated by this initiator with any status code other than 0. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiNodeDiscontinuityTime.
.1.3.6.1.2.1.142.1.9,ISCSI-MIB::iscsiIntrAuthorization,,,,,,
.1.3.6.1.2.1.142.1.9.1,ISCSI-MIB::iscsiIntrAuthAttributesTable,,not-accessible,,current,,A list of target identities that each initiator on the local system may access.
.1.3.6.1.2.1.142.1.9.1.1,ISCSI-MIB::iscsiIntrAuthAttributesEntry,,not-accessible,iscsiInstIndex:iscsiNodeIndex:iscsiIntrAuthIndex,current,,An entry (row) containing management information applicable to a particular initiator node's authorized target identity.
.1.3.6.1.2.1.142.1.9.1.1.1,ISCSI-MIB::iscsiIntrAuthIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular initiator node's authorized target identity within an iSCSI instance present on the local system. This index value must not be modified or reused by an agent unless a reboot has occurred. An agent should attempt to keep this value persistent across reboots.
.1.3.6.1.2.1.142.1.9.1.1.2,ISCSI-MIB::iscsiIntrAuthRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This field allows entries to be dynamically added and removed from this table via SNMP. When adding a row to this table, all non-Index/RowStatus objects must be set. When the value of this object is 'active', the values of the other objects in this table cannot be changed. Rows may be discarded using RowStatus.
.1.3.6.1.2.1.142.1.9.1.1.3,ISCSI-MIB::iscsiIntrAuthIdentity,OBJECT,read-create,,current,,A pointer to the corresponding user entry in the IPS-AUTH MIB module to which this initiator node should attempt to establish an iSCSI session.
.1.3.6.1.2.1.142.1.9.1.1.4,ISCSI-MIB::iscsiIntrAuthStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process (e.g., not created via this MIB) may have a storage type of readOnly or permanent. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.142.1.10,ISCSI-MIB::iscsiSession,,,,,,
.1.3.6.1.2.1.142.1.10.1,ISCSI-MIB::iscsiSessionAttributesTable,,not-accessible,,current,,A list of sessions belonging to each iSCSI instance present on the system.
.1.3.6.1.2.1.142.1.10.1.1,ISCSI-MIB::iscsiSessionAttributesEntry,,not-accessible,iscsiInstIndex:iscsiSsnNodeIndex:iscsiSsnIndex,current,,An entry (row) containing management information applicable to a particular session. If this session is a discovery session that is not attached to any particular node, the iscsiSsnNodeIndex will be zero. Otherwise, the iscsiSsnNodeIndex will have the same value as iscsiNodeIndex.
.1.3.6.1.2.1.142.1.10.1.1.1,ISCSI-MIB::iscsiSsnNodeIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular node within an iSCSI instance present on the local system. For normal, non-discovery sessions, this value will map to the iscsiNodeIndex. For discovery sessions that do not have a node associated, the value 0 (zero) is used.
.1.3.6.1.2.1.142.1.10.1.1.2,ISCSI-MIB::iscsiSsnIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular session within an iSCSI instance present on the local system. An agent should attempt to not reuse index values unless a reboot has occurred. iSCSI sessions are destroyed during a reboot; rows in this table are not persistent across reboots.
.1.3.6.1.2.1.142.1.10.1.1.3,ISCSI-MIB::iscsiSsnDirection,INTEGER,read-only,,current,inboundSession(1):outboundSession(2),Direction of iSCSI session: inboundSession - session is established from an external initiator to a target within this iSCSI instance. outboundSession - session is established from an initiator within this iSCSI instance to an external target.
.1.3.6.1.2.1.142.1.10.1.1.4,ISCSI-MIB::iscsiSsnInitiatorName,OCTET,read-only,,current,,If iscsiSsnDirection is Inbound, this object is a UTF-8 string that will contain the name of the remote initiator. If this session is a discovery session that does not specify a particular initiator, this object will contain a zero-length string. If iscsiSsnDirection is Outbound, this object will contain a zero-length string.
.1.3.6.1.2.1.142.1.10.1.1.5,ISCSI-MIB::iscsiSsnTargetName,OCTET,read-only,,current,,If iscsiSsnDirection is Outbound, this object is a UTF-8 string that will contain the name of the remote target. If this session is a discovery session that does not specify a particular target, this object will contain a zero-length string. If iscsiSsnDirection is Inbound, this object will contain a zero-length string.
.1.3.6.1.2.1.142.1.10.1.1.6,ISCSI-MIB::iscsiSsnTSIH,Unsigned32,read-only,,current,,The target-defined identification handle for this session.
.1.3.6.1.2.1.142.1.10.1.1.7,ISCSI-MIB::iscsiSsnISID,OCTET,read-only,,current,,The initiator-defined portion of the iSCSI Session ID.
.1.3.6.1.2.1.142.1.10.1.1.8,ISCSI-MIB::iscsiSsnInitiatorAlias,OCTET,read-only,,current,,A UTF-8 string that gives the alias communicated by the initiator end of the session during the login phase. If no alias exists, the value is a zero-length string.
.1.3.6.1.2.1.142.1.10.1.1.9,ISCSI-MIB::iscsiSsnTargetAlias,OCTET,read-only,,current,,A UTF-8 string that gives the alias communicated by the target end of the session during the login phase. If no alias exists, the value is a zero-length string.
.1.3.6.1.2.1.142.1.10.1.1.10,ISCSI-MIB::iscsiSsnInitialR2T,INTEGER,read-only,,current,true(1):false(2),If set to true, indicates that the initiator must wait for an R2T before sending to the target. If set to false, the initiator may send data immediately, within limits set by iscsiSsnFirstBurstLength and the expected data transfer length of the request.
.1.3.6.1.2.1.142.1.10.1.1.11,ISCSI-MIB::iscsiSsnImmediateData,INTEGER,read-only,,current,true(1):false(2),Indicates whether the initiator and target have agreed to support immediate data on this session.
.1.3.6.1.2.1.142.1.10.1.1.12,ISCSI-MIB::iscsiSsnType,INTEGER,read-only,,current,normalSession(1):discoverySession(2),Type of iSCSI session: normalSession - session is a normal iSCSI session discoverySession - session is being used only for discovery.
.1.3.6.1.2.1.142.1.10.1.1.13,ISCSI-MIB::iscsiSsnMaxOutstandingR2T,Unsigned32,read-only,,current,,The maximum number of outstanding requests-to-transmit (R2Ts) per iSCSI task within this session.
.1.3.6.1.2.1.142.1.10.1.1.14,ISCSI-MIB::iscsiSsnFirstBurstLength,Unsigned32,read-only,,current,,The maximum length supported for unsolicited data sent within this session.
.1.3.6.1.2.1.142.1.10.1.1.15,ISCSI-MIB::iscsiSsnMaxBurstLength,Unsigned32,read-only,,current,,The maximum number of bytes that can be sent within a single sequence of Data-In or Data-Out PDUs.
.1.3.6.1.2.1.142.1.10.1.1.16,ISCSI-MIB::iscsiSsnConnectionNumber,Gauge32,read-only,,current,,The number of transport protocol connections that currently belong to this session.
.1.3.6.1.2.1.142.1.10.1.1.17,ISCSI-MIB::iscsiSsnAuthIdentity,OBJECT,read-only,,current,,This object contains a pointer to a row in the IPS-AUTH MIB module that identifies the authentication identity being used on this session, as communicated during the login phase.
.1.3.6.1.2.1.142.1.10.1.1.18,ISCSI-MIB::iscsiSsnDataSequenceInOrder,INTEGER,read-only,,current,true(1):false(2),False indicates that iSCSI data PDU sequences may be transferred in any order. True indicates that data PDU sequences must be transferred using continuously increasing offsets, except during error recovery.
.1.3.6.1.2.1.142.1.10.1.1.19,ISCSI-MIB::iscsiSsnDataPDUInOrder,INTEGER,read-only,,current,true(1):false(2),False indicates that iSCSI data PDUs within sequences may be in any order. True indicates that data PDUs within sequences must be at continuously increasing addresses, with no gaps or overlay between PDUs. Default is true.
.1.3.6.1.2.1.142.1.10.1.1.20,ISCSI-MIB::iscsiSsnErrorRecoveryLevel,Unsigned32,read-only,,current,,The level of error recovery negotiated between the initiator and the target. Higher numbers represent more detailed recovery schemes.
.1.3.6.1.2.1.142.1.10.1.1.21,ISCSI-MIB::iscsiSsnDiscontinuityTime,TimeTicks,read-only,,current,,The value of SysUpTime on the most recent occasion at which any one or more of this session's counters suffered a discontinuity. When a session is established, and this object is created, it is initialized to the current value of SysUpTime.
.1.3.6.1.2.1.142.1.10.1.1.22,ISCSI-MIB::iscsiSsnProtocolLevel,Unsigned32,read-only,,current,,The iSCSI protocol level negotiated for this session.
.1.3.6.1.2.1.142.1.10.1.1.23,ISCSI-MIB::iscsiSsnTaskReporting,BITS,read-only,,current,taskReportingRfc3720(0):taskReportingResponseFence(1):taskReportingFastAbort(2),This key is used to negotiate the task completion reporting semantics from the SCSI target. Default value is taskReportingRfc3720.
.1.3.6.1.2.1.142.1.10.2,ISCSI-MIB::iscsiSessionStatsTable,,not-accessible,,current,,A list of general iSCSI traffic counters for each of the sessions present on the system.
.1.3.6.1.2.1.142.1.10.2.1,ISCSI-MIB::iscsiSessionStatsEntry,,not-accessible,,current,,An entry (row) containing general iSCSI traffic counters for a particular session.
.1.3.6.1.2.1.142.1.10.2.1.1,ISCSI-MIB::iscsiSsnCmdPDUs,Counter32,read-only,,current,,The count of Command PDUs transferred on this session. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.2,ISCSI-MIB::iscsiSsnRspPDUs,Counter32,read-only,,current,,The count of Response PDUs transferred on this session. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.3,ISCSI-MIB::iscsiSsnTxDataOctets,Counter64,read-only,,current,,The count of data octets that were transmitted by the local iSCSI node on this session. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.4,ISCSI-MIB::iscsiSsnRxDataOctets,Counter64,read-only,,current,,The count of data octets that were received by the local iSCSI node on this session. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.5,ISCSI-MIB::iscsiSsnLCTxDataOctets,Counter32,read-only,,current,,A Low-Capacity shadow object of iscsiSsnTxDataOctets for those systems that are accessible via SNMPv1 only. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.6,ISCSI-MIB::iscsiSsnLCRxDataOctets,Counter32,read-only,,current,,A Low-Capacity shadow object of iscsiSsnRxDataOctets for those systems which are accessible via SNMPv1 only. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.7,ISCSI-MIB::iscsiSsnNopReceivedPDUs,Counter32,read-only,,current,,The count of NOP-In or NOP-Out PDUs received on this session. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.2.1.8,ISCSI-MIB::iscsiSsnNopSentPDUs,Counter32,read-only,,current,,The count of NOP-In or NOP-Out PDUs sent on this session. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime.
.1.3.6.1.2.1.142.1.10.3,ISCSI-MIB::iscsiSessionCxnErrorStatsTable,,not-accessible,,current,,A list of error counters for each of the sessions present on this system.
.1.3.6.1.2.1.142.1.10.3.1,ISCSI-MIB::iscsiSessionCxnErrorStatsEntry,,not-accessible,,current,,An entry (row) containing error counters for a particular session.
.1.3.6.1.2.1.142.1.10.3.1.1,ISCSI-MIB::iscsiSsnCxnDigestErrors,Counter32,read-only,,current,,The count of PDUs that were received on the session and contained header or data digest errors. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime. This counter is most likely provided when the error-recovery level is 1 or 2
.1.3.6.1.2.1.142.1.10.3.1.2,ISCSI-MIB::iscsiSsnCxnTimeoutErrors,Counter32,read-only,,current,,The count of connections within this session that have been terminated due to timeout. If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime. This counter is most likely provided when the error-recovery level is 2
.1.3.6.1.2.1.142.1.11,ISCSI-MIB::iscsiConnection,,,,,,
.1.3.6.1.2.1.142.1.11.1,ISCSI-MIB::iscsiConnectionAttributesTable,,not-accessible,,current,,A list of connections belonging to each iSCSI instance present on the system.
.1.3.6.1.2.1.142.1.11.1.1,ISCSI-MIB::iscsiConnectionAttributesEntry,,not-accessible,iscsiInstIndex:iscsiSsnNodeIndex:iscsiSsnIndex:iscsiCxnIndex,current,,An entry (row) containing management information applicable to a particular connection.
.1.3.6.1.2.1.142.1.11.1.1.1,ISCSI-MIB::iscsiCxnIndex,Unsigned32,not-accessible,,current,,An arbitrary integer used to uniquely identify a particular connection of a particular session within an iSCSI instance present on the local system. An agent should attempt to not reuse index values unless a reboot has occurred. iSCSI connections are destroyed during a reboot; rows in this table are not persistent across reboots.
.1.3.6.1.2.1.142.1.11.1.1.2,ISCSI-MIB::iscsiCxnCid,Unsigned32,read-only,,current,,The iSCSI Connection ID for this connection.
.1.3.6.1.2.1.142.1.11.1.1.3,ISCSI-MIB::iscsiCxnState,INTEGER,read-only,,current,login(1):full(2):logout(3),The current state of this connection, from an iSCSI negotiation point of view. Here are the states: login - The transport protocol connection has been established, but a valid iSCSI login response with the final bit set has not been sent or received. full - A valid iSCSI login response with the final bit set has been sent or received. logout - A valid iSCSI logout command has been sent or received, but the transport protocol connection has not yet been closed.
.1.3.6.1.2.1.142.1.11.1.1.4,ISCSI-MIB::iscsiCxnAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet Network Addresses contained in the corresponding instances of iscsiCxnLocalAddr and iscsiCxnRemoteAddr. The value 'dns' is not allowed.
.1.3.6.1.2.1.142.1.11.1.1.5,ISCSI-MIB::iscsiCxnLocalAddr,OCTET,read-only,,current,,The local Internet Network Address, of the type specified by iscsiCxnAddrType, used by this connection.
.1.3.6.1.2.1.142.1.11.1.1.6,ISCSI-MIB::iscsiCxnProtocol,Unsigned32,read-only,,current,,The transport protocol over which this connection is running.
.1.3.6.1.2.1.142.1.11.1.1.7,ISCSI-MIB::iscsiCxnLocalPort,Unsigned32,read-only,,current,,The local transport protocol port used by this connection. This object cannot have the value zero, since it represents an established connection.
.1.3.6.1.2.1.142.1.11.1.1.8,ISCSI-MIB::iscsiCxnRemoteAddr,OCTET,read-only,,current,,The remote Internet Network Address, of the type specified by iscsiCxnAddrType, used by this connection.
.1.3.6.1.2.1.142.1.11.1.1.9,ISCSI-MIB::iscsiCxnRemotePort,Unsigned32,read-only,,current,,The remote transport protocol port used by this connection. This object cannot have the value zero, since it represents an established connection.
.1.3.6.1.2.1.142.1.11.1.1.10,ISCSI-MIB::iscsiCxnMaxRecvDataSegLength,Unsigned32,read-only,,current,,The maximum data payload size supported for command or data PDUs able to be received on this connection.
.1.3.6.1.2.1.142.1.11.1.1.11,ISCSI-MIB::iscsiCxnMaxXmitDataSegLength,Unsigned32,read-only,,current,,The maximum data payload size supported for command or data PDUs to be sent on this connection.
.1.3.6.1.2.1.142.1.11.1.1.12,ISCSI-MIB::iscsiCxnHeaderIntegrity,INTEGER,read-only,,current,none(1):other(2):noDigest(3):crc32c(4),This object identifies the iSCSI header digest scheme in use within this connection.
.1.3.6.1.2.1.142.1.11.1.1.13,ISCSI-MIB::iscsiCxnDataIntegrity,INTEGER,read-only,,current,none(1):other(2):noDigest(3):crc32c(4),This object identifies the iSCSI data digest scheme in use within this connection.
.1.3.6.1.2.1.142.1.11.1.1.14,ISCSI-MIB::iscsiCxnRecvMarker,INTEGER,read-only,,deprecated,true(1):false(2),This object indicates whether or not this connection is receiving markers in its incoming data stream.
.1.3.6.1.2.1.142.1.11.1.1.15,ISCSI-MIB::iscsiCxnSendMarker,INTEGER,read-only,,deprecated,true(1):false(2),This object indicates whether or not this connection is inserting markers in its outgoing data stream.
.1.3.6.1.2.1.142.1.11.1.1.16,ISCSI-MIB::iscsiCxnVersionActive,Unsigned32,read-only,,current,,Active version number of the iSCSI specification negotiated on this connection.
.1.3.6.1.2.1.142.2,ISCSI-MIB::iscsiConformance,,,,,,
.1.3.6.1.2.1.142.2.1,ISCSI-MIB::iscsiCompliances,,,,,,
.1.3.6.1.2.1.142.2.1.1,ISCSI-MIB::iscsiComplianceV1,,,,,,Initial version of compliance statement. If an implementation can be both a target and an initiator, all groups are mandatory. This module compliance is deprecated because the marker keys are obsolete.
.1.3.6.1.2.1.142.2.1.2,ISCSI-MIB::iscsiComplianceV2,,,,,,Version 2 of compliance statement based on this revised version of the MIB module. If an implementation can be both a target and an initiator, all groups are mandatory.
.1.3.6.1.2.1.142.2.2,ISCSI-MIB::iscsiGroups,,,,,,
.1.3.6.1.2.1.142.2.2.1,ISCSI-MIB::iscsiInstanceAttributesGroup,,,,,,A collection of objects providing information about iSCSI instances.
.1.3.6.1.2.1.142.2.2.2,ISCSI-MIB::iscsiInstanceSsnErrorStatsGroup,,,,,,A collection of objects providing information about errors that have caused a session failure for an iSCSI instance.
.1.3.6.1.2.1.142.2.2.3,ISCSI-MIB::iscsiPortalAttributesGroup,,,,,,A collection of objects providing information about the transport protocol endpoints of the local targets. This object group is deprecated because the marker key is obsolete.
.1.3.6.1.2.1.142.2.2.4,ISCSI-MIB::iscsiTgtPortalAttributesGroup,,,,,,A collection of objects providing information about the transport protocol endpoints of the local targets.
.1.3.6.1.2.1.142.2.2.5,ISCSI-MIB::iscsiIntrPortalAttributesGroup,,,,,,An object providing information about the portal tags used by the local initiators.
.1.3.6.1.2.1.142.2.2.6,ISCSI-MIB::iscsiNodeAttributesGroup,,,,,,A collection of objects providing information about all local targets.
.1.3.6.1.2.1.142.2.2.7,ISCSI-MIB::iscsiTargetAttributesGroup,,,,,,A collection of objects providing information about all local targets.
.1.3.6.1.2.1.142.2.2.8,ISCSI-MIB::iscsiTargetLoginStatsGroup,,,,,,A collection of objects providing information about all login attempts by remote initiators to local targets.
.1.3.6.1.2.1.142.2.2.9,ISCSI-MIB::iscsiTargetLogoutStatsGroup,,,,,,A collection of objects providing information about all logout events between remote initiators and local targets.
.1.3.6.1.2.1.142.2.2.10,ISCSI-MIB::iscsiTargetAuthGroup,,,,,,A collection of objects providing information about all remote initiators that are authorized to connect to local targets.
.1.3.6.1.2.1.142.2.2.11,ISCSI-MIB::iscsiInitiatorAttributesGroup,,,,,,A collection of objects providing information about all local initiators.
.1.3.6.1.2.1.142.2.2.12,ISCSI-MIB::iscsiInitiatorLoginStatsGroup,,,,,,A collection of objects providing information about all login attempts by local initiators to remote targets.
.1.3.6.1.2.1.142.2.2.13,ISCSI-MIB::iscsiInitiatorLogoutStatsGroup,,,,,,A collection of objects providing information about all logout events between local initiators and remote targets.
.1.3.6.1.2.1.142.2.2.14,ISCSI-MIB::iscsiInitiatorAuthGroup,,,,,,A collection of objects providing information about all remote targets that are initiators of the local system that they are authorized to access.
.1.3.6.1.2.1.142.2.2.15,ISCSI-MIB::iscsiSessionAttributesGroup,,,,,,A collection of objects providing information applicable to all sessions.
.1.3.6.1.2.1.142.2.2.16,ISCSI-MIB::iscsiSessionPDUStatsGroup,,,,,,A collection of objects providing information about PDU traffic for each session.
.1.3.6.1.2.1.142.2.2.17,ISCSI-MIB::iscsiSessionOctetStatsGroup,,,,,,A collection of objects providing information about octet traffic for each session using a Counter64 data type.
.1.3.6.1.2.1.142.2.2.18,ISCSI-MIB::iscsiSessionLCOctetStatsGroup,,,,,,A collection of objects providing information about octet traffic for each session using a Counter32 data type.
.1.3.6.1.2.1.142.2.2.19,ISCSI-MIB::iscsiSessionCxnErrorStatsGroup,,,,,,A collection of objects providing information about connection errors for all sessions.
.1.3.6.1.2.1.142.2.2.20,ISCSI-MIB::iscsiConnectionAttributesGroup,,,,,,A collection of objects providing information about all connections used by all sessions. This object group is deprecated because the marker key is obsolete.
.1.3.6.1.2.1.142.2.2.21,ISCSI-MIB::iscsiTgtLgnNotificationsGroup,,,,,,A collection of notifications that indicate a login failure from a remote initiator to a local target.
.1.3.6.1.2.1.142.2.2.22,ISCSI-MIB::iscsiIntrLgnNotificationsGroup,,,,,,A collection of notifications that indicate a login failure from a local initiator to a remote target.
.1.3.6.1.2.1.142.2.2.23,ISCSI-MIB::iscsiSsnFlrNotificationsGroup,,,,,,A collection of notifications that indicate session failures occurring after login.
.1.3.6.1.2.1.142.2.2.24,ISCSI-MIB::iscsiPortalAttributesGroupV2,,,,,,A collection of objects providing information about the transport protocol endpoints of the local targets.
.1.3.6.1.2.1.142.2.2.25,ISCSI-MIB::iscsiConnectionAttributesGroupV2,,,,,,A collection of objects providing information about all connections used by all sessions.
.1.3.6.1.2.1.142.2.2.26,ISCSI-MIB::iscsiNewObjectsV2,,,,,,A collection of objects added in the second version of the iSCSI MIB.
.1.3.6.1.2.1.142.3,ISCSI-MIB::iscsiAdmin,,,,,,
.1.3.6.1.2.1.142.3.1,ISCSI-MIB::iscsiDescriptors,,,,,,
.1.3.6.1.2.1.142.3.1.1,ISCSI-MIB::iscsiHeaderIntegrityTypes,,,,,,
.1.3.6.1.2.1.142.3.1.1.1,ISCSI-MIB::iscsiHdrIntegrityNone,,,,,,The authoritative identifier when no integrity scheme for the header is being used.
.1.3.6.1.2.1.142.3.1.1.2,ISCSI-MIB::iscsiHdrIntegrityCrc32c,,,,,,The authoritative identifier when the integrity scheme for the header is CRC32c.
.1.3.6.1.2.1.142.3.1.2,ISCSI-MIB::iscsiDataIntegrityTypes,,,,,,
.1.3.6.1.2.1.142.3.1.2.1,ISCSI-MIB::iscsiDataIntegrityNone,,,,,,The authoritative identifier when no integrity scheme for the data is being used.
.1.3.6.1.2.1.142.3.1.2.2,ISCSI-MIB::iscsiDataIntegrityCrc32c,,,,,,The authoritative identifier when the integrity scheme for the data is CRC32c.
.1.3.6.1.2.1.143,T11-FC-FSPF-MIB::t11FcFspfMIB,,,,,,The MIB module for managing the Fabric Shortest Path First (FSPF) protocol. FSPF is specified in FC-SW-4. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4626; see the RFC itself for full legal notices.
.1.3.6.1.2.1.143.0,T11-FC-FSPF-MIB::t11FspfNotifications,,,,,,
.1.3.6.1.2.1.143.0.1,T11-FC-FSPF-MIB::t11FspfNbrStateChangNotify,,,,,,This notification signifies that there has been a change in the state of an FSPF neighbor. This is generated when the FSPF state changes to a terminal state, through either regression (i.e., goes from Full to Init or Down) or progression (i.e., from any state to Full). The value of 't11FspfIfNbrState' is the state of the neighbor after the change.
.1.3.6.1.2.1.143.1,T11-FC-FSPF-MIB::t11FspfObjects,,,,,,
.1.3.6.1.2.1.143.1.1,T11-FC-FSPF-MIB::t11FspfConfiguration,,,,,,
.1.3.6.1.2.1.143.1.1.1,T11-FC-FSPF-MIB::t11FspfTable,,not-accessible,,current,,This table allows the users to configure and monitor FSPF's per-Fabric parameters and statistics on all Fabrics known to locally managed switches. Entries are created/removed by the agent if and when (Virtual) Fabrics are created/deleted.
.1.3.6.1.2.1.143.1.1.1.1,T11-FC-FSPF-MIB::t11FspfEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FspfFabricIndex,current,,An entry containing FSPF variables, parameters, and statistics on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex) for a particular Fabric (identified by a t11FspfFabricIndex value). (Note that the local switch's per-fabric Domain-ID is available in t11FamConfigDomainId, which is defined in T11-FC-FABRIC-ADDR-MGR-MIB.)
.1.3.6.1.2.1.143.1.1.1.1.1,T11-FC-FSPF-MIB::t11FspfFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures. In such a case, index value is used to uniquely identify a particular Fabric within a physical infrastructure. In a Fabric that has (can have) only a single Fabric operating within the physical infrastructure, the value of this Fabric Index will always be 1.
.1.3.6.1.2.1.143.1.1.1.1.2,T11-FC-FSPF-MIB::t11FspfMinLsArrival,Unsigned32,read-write,,current,,The minimum time after accepting a Link State Record (LSR) on this Fabric before accepting another update of the same LSR on the same Fabric. An LSR update that is not accepted because of this time interval is discarded.
.1.3.6.1.2.1.143.1.1.1.1.3,T11-FC-FSPF-MIB::t11FspfMinLsInterval,Unsigned32,read-write,,current,,The minimum time after this switch sends an LSR on this Fabric before it will send another update of the same LSR on the same Fabric.
.1.3.6.1.2.1.143.1.1.1.1.4,T11-FC-FSPF-MIB::t11FspfLsRefreshTime,Unsigned32,read-only,,current,,The interval between transmission of refresh LSRs on this Fabric.
.1.3.6.1.2.1.143.1.1.1.1.5,T11-FC-FSPF-MIB::t11FspfMaxAge,Unsigned32,read-only,,current,,The maximum age an LSR will be retained in the FSPF database on this Fabric. An LSR is removed from the database after MaxAge is reached.
.1.3.6.1.2.1.143.1.1.1.1.6,T11-FC-FSPF-MIB::t11FspfMaxAgeDiscards,Counter32,read-only,,current,,The number of LSRs discarded due to their age reaching t11FspfMaxAge in this Fabric. The last discontinuity of this counter is indicated by t11FspfCreateTime.
.1.3.6.1.2.1.143.1.1.1.1.7,T11-FC-FSPF-MIB::t11FspfPathComputations,Counter32,read-only,,current,,The number of times that the path computation algorithm has been invoked by this Switch on this Fabric to compute a set of minimum cost paths for this Fabric. The last discontinuity of this counter is indicated by t11FspfCreateTime.
.1.3.6.1.2.1.143.1.1.1.1.8,T11-FC-FSPF-MIB::t11FspfChecksumErrors,Counter32,read-only,,current,,The number of FSPF checksum errors that were detected locally (and therefore discarded) on this Fabric. The last discontinuity of this counter is indicated by t11FspfCreateTime.
.1.3.6.1.2.1.143.1.1.1.1.9,T11-FC-FSPF-MIB::t11FspfLsrs,Gauge32,read-only,,current,,The current number of entries for this Fabric in the t11FspfLsrTable.
.1.3.6.1.2.1.143.1.1.1.1.10,T11-FC-FSPF-MIB::t11FspfCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last created.
.1.3.6.1.2.1.143.1.1.1.1.11,T11-FC-FSPF-MIB::t11FspfAdminStatus,INTEGER,read-write,,current,up(1):down(2),The desired state of FSPF in this Fabric. If value of this object is set to 'up', then FSPF is enabled in this Fabric. If set to 'down', then FSPF is disabled in this Fabric -- when FSPF is disabled, FSPF provides no routes to be included in the T11-FC-ROUTE-MIB module. (see the T11-FC-ROUTE-MIB).
.1.3.6.1.2.1.143.1.1.1.1.12,T11-FC-FSPF-MIB::t11FspfOperStatus,INTEGER,read-only,,current,up(1):down(2),State of FSPF in this Fabric. If 't11FspfAdminStatus' is 'down', then the 't11FspfOperStatus' should be 'down'. If 't11FspfAdminStatus' is changed to 'up', then 't11FspfOperStatus' should change to 'up' as and when FSPF is active in this Fabric.
.1.3.6.1.2.1.143.1.1.1.1.13,T11-FC-FSPF-MIB::t11FspfNbrStateChangNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Specifies whether or not the local agent should issue the notification 't11FspfNbrStateChangNotify' when the local switch learns of a change of state in the FSPF Neighbor Finite State Machine on an interface in this Fabric. If the value of the object is 'true, then the notification is generated. If the value is 'false', notification is not generated.
.1.3.6.1.2.1.143.1.1.1.1.14,T11-FC-FSPF-MIB::t11FspfSetToDefault,INTEGER,read-write,,current,default(1):noOp(2),Setting this value to 'default' changes the value of each and every writable object in this row to its default value. No action is taken if this object is set to 'noOp'. The value of the object, when read, is always 'noOp'.
.1.3.6.1.2.1.143.1.1.1.1.15,T11-FC-FSPF-MIB::t11FspfStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for read-write objects in this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.143.1.1.2,T11-FC-FSPF-MIB::t11FspfIfTable,,not-accessible,,current,,This table allows the users to configure and monitor the FSPF parameters that are per-interface (identified by a t11FspfIfIndex value), per-Fabric (identified by a t11FspfFabricIndex value), and per-switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). Creating a row in this table via t11FspfIfRowStatus provides the means to specify non-default parameter value(s) for an interface at a time when the relevant row in this table would not otherwise exist because the interface is either down or it is not an E_Port, but the corresponding row in the t11FspfTable must already exist. After the non-default values have been specified for a port's parameters, they need to be retained in this table, even when the port becomes 'isolated'. However, having unnecessary rows in this table clutters it up and makes those rows that are useful harder for an NMS to find. Therefore, when an E_Port becomes isolated, its row gets deleted if and only if all of its parameter values are the default values; also, when an E_Port becomes non-isolated in a particular Fabric, a row in this table needs to exist and is automatically created, if necessary. The specific conditions for an automated/implicit deletion of a row are: a) if the corresponding interface is no longer an E_Port (e.g., a G_Port which is dynamically determined to be an F_Port), and all configurable parameters have default values; or b) if the interface identified by t11FspfIfIndex no longer exists (e.g., because a line-card is physically removed); or c) if the corresponding row in the t11FspfTable is deleted. 
.1.3.6.1.2.1.143.1.1.2.1,T11-FC-FSPF-MIB::t11FspfIfEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FspfFabricIndex:t11FspfIfIndex,current,,An entry containing FSPF information for the interface identified by t11FspfIfIndex, on the fabric identified by t11FspfFabricIndex, on the switch identified by fcmSwitchIndex.
.1.3.6.1.2.1.143.1.1.2.1.1,T11-FC-FSPF-MIB::t11FspfIfIndex,Integer32,not-accessible,,current,,The value of ifIndex that identifies the local Fibre Channel interface for which this entry contains FSPF information.
.1.3.6.1.2.1.143.1.1.2.1.2,T11-FC-FSPF-MIB::t11FspfIfHelloInterval,Unsigned32,read-create,,current,,Interval between the periodic HELLO messages sent on this interface in this Fabric to verify the link health. Note that this value must be same at both ends of a link in this Fabric.
.1.3.6.1.2.1.143.1.1.2.1.3,T11-FC-FSPF-MIB::t11FspfIfDeadInterval,Unsigned32,read-create,,current,,Maximum time for which no HELLO messages can be received on this interface in this Fabric. After this time, the interface is assumed to be broken and removed from the database. Note that this value must be greater than the HELLO interval specified on this interface in this Fabric.
.1.3.6.1.2.1.143.1.1.2.1.4,T11-FC-FSPF-MIB::t11FspfIfRetransmitInterval,Unsigned32,read-create,,current,,The time after which an unacknowledged LSR is retransmitted on this interface in this Fabric.
.1.3.6.1.2.1.143.1.1.2.1.5,T11-FC-FSPF-MIB::t11FspfIfInLsuPkts,Counter32,read-only,,current,,Number of Link State Update (LSU) packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.6,T11-FC-FSPF-MIB::t11FspfIfInLsaPkts,Counter32,read-only,,current,,Number of Link State Acknowledgement (LSA) packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.7,T11-FC-FSPF-MIB::t11FspfIfOutLsuPkts,Counter32,read-only,,current,,Number of Link State Update (LSU) packets transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.8,T11-FC-FSPF-MIB::t11FspfIfOutLsaPkts,Counter32,read-only,,current,,Number of Link State Acknowledgement (LSA) packets transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.9,T11-FC-FSPF-MIB::t11FspfIfOutHelloPkts,Counter32,read-only,,current,,Number of HELLO packets transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.10,T11-FC-FSPF-MIB::t11FspfIfInHelloPkts,Counter32,read-only,,current,,Number of HELLO packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.11,T11-FC-FSPF-MIB::t11FspfIfRetransmittedLsuPkts,Counter32,read-only,,current,,The number of LSU packets that contained one or more retransmitted LSRs, and that were transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.12,T11-FC-FSPF-MIB::t11FspfIfInErrorPkts,Counter32,read-only,,current,,Number of invalid FSPF control packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.
.1.3.6.1.2.1.143.1.1.2.1.13,T11-FC-FSPF-MIB::t11FspfIfNbrState,INTEGER,read-only,,current,down(1):init(2):dbExchange(3):dbAckwait(4):dbWait(5):full(6),The state of FSPF's 'neighbor state machine', which is the operational state of the interaction with the neighbor's interface that is connected to this interface. If the 't11FspfIfAdminStatus' is 'down', then this object should be 'down'. If the 't11FspfIfAdminStatus' is 'up', then this object's value depends on the state of FSPF's 'neighbor state machine' on this interface in this Fabric.
.1.3.6.1.2.1.143.1.1.2.1.14,T11-FC-FSPF-MIB::t11FspfIfNbrDomainId,Integer32,read-only,,current,,The Domain Id of the neighbor in this Fabric.
.1.3.6.1.2.1.143.1.1.2.1.15,T11-FC-FSPF-MIB::t11FspfIfNbrPortIndex,Unsigned32,read-only,,current,,The index, as known by the neighbor, of the neighbor's interface that is connected to this interface in this Fabric.
.1.3.6.1.2.1.143.1.1.2.1.16,T11-FC-FSPF-MIB::t11FspfIfAdminStatus,INTEGER,read-create,,current,up(1):down(2),The desired state of FSPF on this interface in this Fabric, whenever 't11FspfAdminStatus' is 'up'. If the value of this object is set to 'up', then FSPF is enabled on this interface in this Fabric. If set to 'down', then FSPF is disabled on this interface in this Fabric. Note that the operational state of FSPF on an interface is given by t11FspfIfNbrState.
.1.3.6.1.2.1.143.1.1.2.1.17,T11-FC-FSPF-MIB::t11FspfIfCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last created.
.1.3.6.1.2.1.143.1.1.2.1.18,T11-FC-FSPF-MIB::t11FspfIfSetToDefault,INTEGER,read-create,,current,default(1):noOp(2),Setting this value to 'default' changes the value of each and every writable object in this row to its default value. If all the configuration parameters have their default values, and if the interface is down, then the row is deleted automatically. No action is taken if this object is set to 'noOp'. The value of the object, when read, is always 'noOp'.
.1.3.6.1.2.1.143.1.1.2.1.19,T11-FC-FSPF-MIB::t11FspfIfLinkCostFactor,Unsigned32,read-create,,current,,The administrative factor used in calculating the cost of sending a frame on this interface in this Fabric. The formula used to calculate the link cost is: Link Cost = S * (1.0625e12 / ifSpeed) where: S = (the value of this object / 100) ifSpeed = interface speed (as defined in the IF-MIB). 
.1.3.6.1.2.1.143.1.1.2.1.20,T11-FC-FSPF-MIB::t11FspfIfStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.143.1.1.2.1.21,T11-FC-FSPF-MIB::t11FspfIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the conceptual row. This object can be used to create an entry only if there is an entry in the t11FspfTable for the corresponding Fabric, and if the interface is either isolated or is a non-E_port. Setting this object to 'destroy' will typically fail; to reverse the creation process, set the corresponding instance of t11FspfIfSetToDefault to 'default'.
.1.3.6.1.2.1.143.1.1.3,T11-FC-FSPF-MIB::t11FspfIfPrevNbrState,INTEGER,accessible-for-notify,,current,down(1):init(2):dbExchange(3):dbAckwait(4):dbWait(5):full(6),The previous state of FSPF's Neighbor Finite State Machine on an interface. This object is only used in the 't11FspfNbrStateChangNotify' notification.
.1.3.6.1.2.1.143.1.2,T11-FC-FSPF-MIB::t11FspfDatabase,,,,,,
.1.3.6.1.2.1.143.1.2.1,T11-FC-FSPF-MIB::t11FspfLsrTable,,not-accessible,,current,,This table is the database of all the latest incarnations of the Link State Records (LSRs) that are currently contained in the topology database, for all interfaces on all Fabrics known to locally managed switches. A Fabric's topology database contains the LSRs that have been either issued or received by a local switch on that Fabric, and that have not reached t11FspfMaxAge.
.1.3.6.1.2.1.143.1.2.1.1,T11-FC-FSPF-MIB::t11FspfLsrEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FspfFabricIndex:t11FspfLsrDomainId:t11FspfLsrType,current,,This gives information for the most recent update of an LSR. There is one entry for every LSR issued or received by a locally managed switch (identified by fcmInstanceIndex and fcmSwitchIndex) in a Fabric (identified by t11FspfFabricIndex).
.1.3.6.1.2.1.143.1.2.1.1.1,T11-FC-FSPF-MIB::t11FspfLsrDomainId,Integer32,not-accessible,,current,,Domain Id of the LSR owner in this Fabric. It is the Link State Id of this LSR.
.1.3.6.1.2.1.143.1.2.1.1.2,T11-FC-FSPF-MIB::t11FspfLsrType,Integer32,not-accessible,,current,,Type of this LSR.
.1.3.6.1.2.1.143.1.2.1.1.3,T11-FC-FSPF-MIB::t11FspfLsrAdvDomainId,Integer32,read-only,,current,,Domain Id of the switch that is advertising the LSR on the behalf of the switch owning it.
.1.3.6.1.2.1.143.1.2.1.1.4,T11-FC-FSPF-MIB::t11FspfLsrAge,Unsigned32,read-only,,current,,The time since this LSR was inserted into the database.
.1.3.6.1.2.1.143.1.2.1.1.5,T11-FC-FSPF-MIB::t11FspfLsrIncarnationNumber,Unsigned32,read-only,,current,,The link state incarnation number of this LSR. This is used to identify most recent instance of an LSR while updating the topology database when an LSR is received. The updating of an LSR includes incrementing its incarnation number prior to transmission of the updated LSR. So, the most recent LSR is the one with the largest incarnation number.
.1.3.6.1.2.1.143.1.2.1.1.6,T11-FC-FSPF-MIB::t11FspfLsrCheckSum,Unsigned32,read-only,,current,,The checksum of the LSR.
.1.3.6.1.2.1.143.1.2.1.1.7,T11-FC-FSPF-MIB::t11FspfLsrLinks,Unsigned32,read-only,,current,,Number of entries in the t11FspfLinkTable associated with this LSR.
.1.3.6.1.2.1.143.1.2.3,T11-FC-FSPF-MIB::t11FspfLinkNumber,Unsigned32,read-only,,current,,The number of rows in the t11FspfLinkTable.
.1.3.6.1.2.1.143.1.2.4,T11-FC-FSPF-MIB::t11FspfLinkTable,,not-accessible,,current,,This table contains the list of Inter-Switch Links and their information that is part of an LSR, either received or transmitted.
.1.3.6.1.2.1.143.1.2.4.1,T11-FC-FSPF-MIB::t11FspfLinkEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FspfFabricIndex:t11FspfLsrDomainId:t11FspfLsrType:t11FspfLinkIndex,current,,An entry that contains information about a link contained in an LSR in this Fabric. An entry is created whenever a new link appears in an (issued or received) LSR. An entry is deleted when a link no longer appears in an (issued or received) LSR.
.1.3.6.1.2.1.143.1.2.4.1.1,T11-FC-FSPF-MIB::t11FspfLinkIndex,Unsigned32,not-accessible,,current,,An arbitrary index of this link.
.1.3.6.1.2.1.143.1.2.4.1.2,T11-FC-FSPF-MIB::t11FspfLinkNbrDomainId,Integer32,read-only,,current,,The Domain Id of the neighbor on the other end of this link in this Fabric.
.1.3.6.1.2.1.143.1.2.4.1.3,T11-FC-FSPF-MIB::t11FspfLinkPortIndex,Unsigned32,read-only,,current,,The source E_port of this link, as indicated by the index value in the LSR received from the switch identified by 't11FspfLsrDomainId'.
.1.3.6.1.2.1.143.1.2.4.1.4,T11-FC-FSPF-MIB::t11FspfLinkNbrPortIndex,Unsigned32,read-only,,current,,The destination E_port of this link, as indicated by the index value in the LSR received from the switch identified by 't11FspfLinkNbrDomainId'.
.1.3.6.1.2.1.143.1.2.4.1.5,T11-FC-FSPF-MIB::t11FspfLinkType,Integer32,read-only,,current,,The type of this link.
.1.3.6.1.2.1.143.1.2.4.1.6,T11-FC-FSPF-MIB::t11FspfLinkCost,Integer32,read-only,,current,,The cost of sending a frame on this link in this Fabric. Link cost is calculated using the formula: link cost = S * (1.0625e12 / Signalling Rate) For issued LSRs, S is determined by the value of t11FspfIfLinkCostFactor for the corresponding interface and Fabric.
.1.3.6.1.2.1.143.2,T11-FC-FSPF-MIB::t11FspfConformance,,,,,,
.1.3.6.1.2.1.143.2.1,T11-FC-FSPF-MIB::t11FspfMIBCompliances,,,,,,
.1.3.6.1.2.1.143.2.1.1,T11-FC-FSPF-MIB::t11FspfMIBCompliance,,,,,,The compliance statement for entities that implement the FSPF.
.1.3.6.1.2.1.143.2.2,T11-FC-FSPF-MIB::t11FspfMIBGroups,,,,,,
.1.3.6.1.2.1.143.2.2.1,T11-FC-FSPF-MIB::t11FspfGeneralGroup,,,,,,A collection of objects for displaying and configuring FSPF parameters.
.1.3.6.1.2.1.143.2.2.2,T11-FC-FSPF-MIB::t11FspfIfGroup,,,,,,A collection of objects for displaying the FSPF interface information.
.1.3.6.1.2.1.143.2.2.3,T11-FC-FSPF-MIB::t11FspfIfCounterGroup,,,,,,A collection of objects for counting particular FSPF-packet occurrences on an interface.
.1.3.6.1.2.1.143.2.2.4,T11-FC-FSPF-MIB::t11FspfDatabaseGroup,,,,,,A collection of objects for displaying the FSPF topology database information.
.1.3.6.1.2.1.143.2.2.5,T11-FC-FSPF-MIB::t11FspfNotificationGroup,,,,,,A collection of notifications for FSPF.
.1.3.6.1.2.1.144,T11-FC-ROUTE-MIB::t11FcRouteMIB,,,,,,The MIB module for configuring and displaying Fibre Channel Route Information. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4625; see the RFC itself for full legal notices.
.1.3.6.1.2.1.144.0,T11-FC-ROUTE-MIB::t11FcRouteNotifications,,,,,,
.1.3.6.1.2.1.144.1,T11-FC-ROUTE-MIB::t11FcRouteObjects,,,,,,
.1.3.6.1.2.1.144.1.1,T11-FC-ROUTE-MIB::t11FcRouteFabricTable,,not-accessible,,current,,The table containing Fibre Channel Routing information that is specific to a Fabric.
.1.3.6.1.2.1.144.1.1.1,T11-FC-ROUTE-MIB::t11FcRouteFabricEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcRouteFabricIndex,current,,Each entry contains routing information specific to a particular Fabric on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.144.1.1.1.1,T11-FC-ROUTE-MIB::t11FcRouteFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric. In a Fabric conformant to FC-SW-3, only a single Fabric can operate within a physical infrastructure, and thus the value of this Fabric Index will always be 1. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures. In such a case, index value is used to uniquely identify a particular Fabric within a physical infrastructure.
.1.3.6.1.2.1.144.1.1.1.2,T11-FC-ROUTE-MIB::t11FcRouteFabricLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent time when any corresponding row in the t11FcRouteTable was created, modified, or deleted. A corresponding row in the t11FcRouteTable is for the same management instance, the same switch, and same Fabric as the row in this table. If no change has occurred since the last restart of the management system, then the value of this object is 0.
.1.3.6.1.2.1.144.1.2,T11-FC-ROUTE-MIB::t11FcRouteTable,,not-accessible,,current,,The Fibre Channel Routing tables for the locally managed switches. This table lists all the routes that are configured in and/or computed by any local switch for any Fabric. Such routes are used by a switch to forward frames (of user data) on a Fabric. The conceptual process is based on extracting the Destination Fibre Channel Address Identifier (D_ID) out of a received frame (of user data) and comparing it to each entry of this table that is applicable to the given switch and Fabric. Such comparison consists of first performing a logical-AND of the extracted D_ID with a mask (the value of t11FcRouteDestMask) and second comparing the result of that 'AND' operation to the value of t11FcRouteDestAddrId. A similar comparison is made of the Source Fibre Channel Address Identifier (S_ID) of a frame against the t11FcRouteSrcAddrId and t11FcRouteSrcMask values of an entry. If an entry's value of t11FcRouteInInterface is non-zero, then a further comparison determines if the frame was received on the appropriate interface. If all of these comparisons for a particular entry are successful, then that entry represents a potential route for forwarding the received frame. For entries configured by a user, t11FcRouteProto has the value 'netmgmt'; only entries of this type can be deleted by the user.
.1.3.6.1.2.1.144.1.2.1,T11-FC-ROUTE-MIB::t11FcRouteEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcRouteFabricIndex:t11FcRouteDestAddrId:t11FcRouteDestMask:t11FcRouteSrcAddrId:t11FcRouteSrcMask:t11FcRouteInInterface:t11FcRouteProto:t11FcRouteOutInterface,current,,Each entry contains a route to a particular destination, possibly from a particular subset of source addresses, on a particular Fabric via a particular output interface and learned in a particular manner.
.1.3.6.1.2.1.144.1.2.1.1,T11-FC-ROUTE-MIB::t11FcRouteDestAddrId,OCTET,not-accessible,,current,,The destination Fibre Channel Address Identifier of this route. A zero-length string for this field is not allowed.
.1.3.6.1.2.1.144.1.2.1.2,T11-FC-ROUTE-MIB::t11FcRouteDestMask,OCTET,not-accessible,,current,,The mask to be logical-ANDed with a destination Fibre Channel Address Identifier before it is compared to the value in the t11FcRouteDestAddrId field. Allowed values are 255.255.255, 255.255.0, or 255.0.0. FSPF's definition generates routes to a Domain_ID, so the mask for all FSPF-generated routes is 255.0.0. The zero-length value has the same meaning as 0.0.0.
.1.3.6.1.2.1.144.1.2.1.3,T11-FC-ROUTE-MIB::t11FcRouteSrcAddrId,OCTET,not-accessible,,current,,The source Fibre Channel Address Identifier of this route. Note that if this object and the corresponding instance of t11FcRouteSrcMask both have a value of 0.0.0, then this route matches all source addresses. The zero-length value has the same meaning as 0.0.0.
.1.3.6.1.2.1.144.1.2.1.4,T11-FC-ROUTE-MIB::t11FcRouteSrcMask,OCTET,not-accessible,,current,,The mask to be logical-ANDed with a source Fibre Channel Address Identifier before it is compared to the value in the t11FcRouteSrcAddrId field. Allowed values are 255.255.255, 255.255.0, 255.0.0, or 0.0.0. The zero-length value has the same meaning as 0.0.0.
.1.3.6.1.2.1.144.1.2.1.5,T11-FC-ROUTE-MIB::t11FcRouteInInterface,Integer32,not-accessible,,current,,If the value of this object is non-zero, it is the value of ifIndex that identifies the local Fibre Channel interface through which a frame must have been received in order to match with this entry. If the value of this object is zero, the matching does not require that the frame be received on any specific interface.
.1.3.6.1.2.1.144.1.2.1.6,T11-FC-ROUTE-MIB::t11FcRouteProto,INTEGER,not-accessible,,current,other(1):local(2):netmgmt(3):fspf(4),The mechanism via which this route was learned: other(1) - not specified local(2) - local interface netmgmt(3)- static route fspf(4) - Fibre Shortest Path First 
.1.3.6.1.2.1.144.1.2.1.7,T11-FC-ROUTE-MIB::t11FcRouteOutInterface,Integer32,not-accessible,,current,,The value of ifIndex that identifies the local Fibre Channel interface through which the next hop of this route is to be reached.
.1.3.6.1.2.1.144.1.2.1.8,T11-FC-ROUTE-MIB::t11FcRouteDomainId,Integer32,read-create,,current,,The domain_ID of next hop switch. This object can have a value of zero if the value of t11FcRouteProto is 'local'.
.1.3.6.1.2.1.144.1.2.1.9,T11-FC-ROUTE-MIB::t11FcRouteMetric,Unsigned32,read-create,,current,,The routing metric for this route. The use of this object is dependent on t11FcRouteProto.
.1.3.6.1.2.1.144.1.2.1.10,T11-FC-ROUTE-MIB::t11FcRouteType,INTEGER,read-create,,current,local(1):remote(2),The type of route. local(1) - a route for which the next Fibre Channel port is the final destination; remote(2) - a route for which the next Fibre Channel port is not the final destination.
.1.3.6.1.2.1.144.1.2.1.11,T11-FC-ROUTE-MIB::t11FcRouteIfDown,INTEGER,read-create,,current,remove(1):retain(2),The value of this object indicates what happens to this route when the output interface (given by the corresponding value of t11FcRouteOutInterface) is operationally 'down'. If this object's value is 'retain', the route is to be retained in this table. If this object's value is 'remove', the route is to be removed from this table.
.1.3.6.1.2.1.144.1.2.1.12,T11-FC-ROUTE-MIB::t11FcRouteStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.144.1.2.1.13,T11-FC-ROUTE-MIB::t11FcRouteRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The only rows that can be deleted by setting this object to 'destroy' are those for which t11FcRouteProto has the value 'netmgmt'.
.1.3.6.1.2.1.144.2,T11-FC-ROUTE-MIB::t11FcRouteConformance,,,,,,
.1.3.6.1.2.1.144.2.1,T11-FC-ROUTE-MIB::t11FcRouteCompliances,,,,,,
.1.3.6.1.2.1.144.2.1.1,T11-FC-ROUTE-MIB::--,,,,,,The compliance statement for entities that implement the T11-FC-ROUTE-MIB. 
.1.3.6.1.2.1.144.2.2,T11-FC-ROUTE-MIB::t11FcRouteGroups,,,,,,
.1.3.6.1.2.1.144.2.2.1,T11-FC-ROUTE-MIB::t11FcRouteGroup,,,,,,A collection of objects for displaying and configuring routes.
.1.3.6.1.2.1.145,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIB,,,,,,The MIB module for entities implementing the client side of the Dynamic Authorization Extensions to the Remote Authentication Dial-In User Service (RADIUS) protocol. Copyright (C) The Internet Society (2006). Initial version as published in RFC 4672; for full legal notices see the RFC itself.
.1.3.6.1.2.1.145.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIBObjects,,,,,,
.1.3.6.1.2.1.145.1.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientScalars,,,,,,
.1.3.6.1.2.1.145.1.1.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconInvalidServerAddresses,Counter32,read-only,,current,,The number of Disconnect-Ack and Disconnect-NAK packets received from unknown addresses. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.1.2,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoAInvalidServerAddresses,Counter32,read-only,,current,,The number of CoA-Ack and CoA-NAK packets received from unknown addresses. Disconnect-NAK packets received from unknown addresses. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerTable,,not-accessible,,current,,The (conceptual) table listing the RADIUS Dynamic Authorization Servers with which the client shares a secret.
.1.3.6.1.2.1.145.1.2.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerEntry,,not-accessible,radiusDynAuthServerIndex,current,,An entry (conceptual row) representing one Dynamic Authorization Server with which the client shares a secret.
.1.3.6.1.2.1.145.1.2.1.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerIndex,Integer32,not-accessible,,current,,A number uniquely identifying each RADIUS Dynamic Authorization Server with which this Dynamic Authorization Client communicates. This number is allocated by the agent implementing this MIB module and is unique in this context.
.1.3.6.1.2.1.145.1.2.1.2,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of IP address of the RADIUS Dynamic Authorization Server referred to in this table entry.
.1.3.6.1.2.1.145.1.2.1.3,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerAddress,OCTET,read-only,,current,,The IP address value of the RADIUS Dynamic Authorization Server referred to in this table entry using the version neutral IP address format. The type of this address is determined by the value of the radiusDynAuthServerAddressType object.
.1.3.6.1.2.1.145.1.2.1.4,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerClientPortNumber,Unsigned32,read-only,,current,,The UDP destination port that the RADIUS Dynamic Authorization Client is using to send requests to this server. The value zero is invalid.
.1.3.6.1.2.1.145.1.2.1.5,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthServerID,OCTET,read-only,,current,,The NAS-Identifier of the RADIUS Dynamic Authorization Server referred to in this table entry. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.145.1.2.1.6,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientRoundTripTime,TimeTicks,read-only,,current,,The time interval (in hundredths of a second) between the most recent Disconnect or CoA request and the receipt of the corresponding Disconnect or CoA reply. A value of zero is returned if no reply has been received yet from this server.
.1.3.6.1.2.1.145.1.2.1.7,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconRequests,Counter32,read-only,,current,,The number of RADIUS Disconnect-Requests sent to this Dynamic Authorization Server. This also includes the RADIUS Disconnect-Requests that have a Service-Type attribute with value 'Authorize Only'. Disconnect-NAK packets received from unknown addresses. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.8,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconAuthOnlyRequests,Counter32,read-only,,current,,The number of RADIUS Disconnect-Requests that include a Service-Type attribute with value 'Authorize Only' sent to this Dynamic Authorization Server. Disconnect-NAK packets received from unknown addresses. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.9,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconRetransmissions,Counter32,read-only,,current,,The number of RADIUS Disconnect-request packets retransmitted to this RADIUS Dynamic Authorization Server. Disconnect-NAK packets received from unknown addresses. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.10,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconAcks,Counter32,read-only,,current,,The number of RADIUS Disconnect-ACK packets received from this Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.11,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconNaks,Counter32,read-only,,current,,The number of RADIUS Disconnect-NAK packets received from this Dynamic Authorization Server. This includes the RADIUS Disconnect-NAK packets received with a Service-Type attribute with value 'Authorize Only' and the RADIUS Disconnect-NAK packets received if no session context was found. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.12,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconNakAuthOnlyRequest,Counter32,read-only,,current,,The number of RADIUS Disconnect-NAK packets that include a Service-Type attribute with value 'Authorize Only' received from this Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.13,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconNakSessNoContext,Counter32,read-only,,current,,The number of RADIUS Disconnect-NAK packets received from this Dynamic Authorization Server because no session context was found; i.e., it includes an Error-Cause attribute with value 503 ('Session Context Not Found'). This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.14,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMalformedDisconResponses,Counter32,read-only,,current,,The number of malformed RADIUS Disconnect-Ack and Disconnect-NAK packets received from this Dynamic Authorization Server. Bad authenticators and unknown types are not included as malformed Disconnect-Ack and Disconnect-NAK packets. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.15,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Disconnect-Ack and Disconnect-NAK packets that contained invalid Authenticator field received from this Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.16,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconPendingRequests,Gauge32,read-only,,current,,The number of RADIUS Disconnect-request packets destined for this server that have not yet timed out or received a response. This variable is incremented when an Disconnect-Request is sent and decremented due to receipt of a Disconnect-Ack, a Disconnect-NAK, a timeout, or a retransmission.
.1.3.6.1.2.1.145.1.2.1.17,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconTimeouts,Counter32,read-only,,current,,The number of Disconnect request timeouts to this server. After a timeout, the client may retry to the same server or give up. A retry to the same server is counted as a retransmit and as a timeout. A send to a different server is counted as a Disconnect-Request and as a timeout. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.18,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientDisconPacketsDropped,Counter32,read-only,,current,,The number of incoming Disconnect-Ack and Disconnect-NAK packets from this Dynamic Authorization Server silently discarded by the client application for some reason other than malformed, bad authenticators, or unknown types. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.19,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoARequests,Counter32,read-only,,current,,The number of RADIUS CoA-Requests sent to this Dynamic Authorization Server. This also includes CoA requests that have a Service-Type attribute with value 'Authorize Only'. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.20,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoAAuthOnlyRequest,Counter32,read-only,,current,,The number of RADIUS CoA-requests that include a Service-Type attribute with value 'Authorize Only' sent to this Dynamic Authorization Client. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.21,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoARetransmissions,Counter32,read-only,,current,,The number of RADIUS CoA-request packets retransmitted to this RADIUS Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.22,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoAAcks,Counter32,read-only,,current,,The number of RADIUS CoA-ACK packets received from this Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.23,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoANaks,Counter32,read-only,,current,,The number of RADIUS CoA-NAK packets received from this Dynamic Authorization Server. This includes the RADIUS CoA-NAK packets received with a Service-Type attribute with value 'Authorize Only' and the RADIUS CoA-NAK packets received because no session context was found. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.24,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoANakAuthOnlyRequest,Counter32,read-only,,current,,The number of RADIUS CoA-NAK packets that include a Service-Type attribute with value 'Authorize Only' received from this Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.25,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoANakSessNoContext,Counter32,read-only,,current,,The number of RADIUS CoA-NAK packets received from this Dynamic Authorization Server because no session context was found; i.e., it includes an Error-Cause attribute with value 503 ('Session Context Not Found'). This counter may experience a discontinuity when the DAC module (re)starts as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.26,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMalformedCoAResponses,Counter32,read-only,,current,,The number of malformed RADIUS CoA-Ack and CoA-NAK packets received from this Dynamic Authorization Server. Bad authenticators and unknown types are not included as malformed CoA-Ack and CoA-NAK packets. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.27,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoABadAuthenticators,Counter32,read-only,,current,,The number of RADIUS CoA-Ack and CoA-NAK packets that contained invalid Authenticator field received from this Dynamic Authorization Server. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.28,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoAPendingRequests,Gauge32,read-only,,current,,The number of RADIUS CoA-request packets destined for this server that have not yet timed out or received a response. This variable is incremented when an CoA-Request is sent and decremented due to receipt of a CoA-Ack, a CoA-NAK, or a timeout, or a retransmission.
.1.3.6.1.2.1.145.1.2.1.29,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoATimeouts,Counter32,read-only,,current,,The number of CoA request timeouts to this server. After a timeout, the client may retry to the same server or give up. A retry to the same server is counted as a retransmit and as a timeout. A send to a different server is counted as a CoA-Request and as a timeout. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.30,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCoAPacketsDropped,Counter32,read-only,,current,,The number of incoming CoA-Ack and CoA-NAK from this Dynamic Authorization Server silently discarded by the client application for some reason other than malformed, bad authenticators, or unknown types. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.31,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientUnknownTypes,Counter32,read-only,,current,,The number of incoming packets of unknown types that were received on the Dynamic Authorization port. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity.
.1.3.6.1.2.1.145.1.2.1.32,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientCounterDiscontinuity,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last counter discontinuity. A discontinuity may be the result of a reinitialization of the DAC module within the managed entity.
.1.3.6.1.2.1.145.2,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIBConformance,,,,,,
.1.3.6.1.2.1.145.2.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIBCompliances,,,,,,
.1.3.6.1.2.1.145.2.1.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIBCompliance,,,,,,The compliance statement for entities implementing the RADIUS Dynamic Authorization Client. Implementation of this module is for entities that support IPv4 and/or IPv6.
.1.3.6.1.2.1.145.2.2,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIBGroups,,,,,,
.1.3.6.1.2.1.145.2.2.1,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientMIBGroup,,,,,,The collection of objects providing management of a RADIUS Dynamic Authorization Client.
.1.3.6.1.2.1.145.2.2.2,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientAuthOnlyGroup,,,,,,The collection of objects supporting the RADIUS messages including Service-Type attribute with value 'Authorize Only'.
.1.3.6.1.2.1.145.2.2.3,RADIUS-DYNAUTH-CLIENT-MIB::radiusDynAuthClientNoSessGroup,,,,,,The collection of objects supporting the RADIUS messages that are referring to non-existing sessions.
.1.3.6.1.2.1.146,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerMIB,,,,,,The MIB module for entities implementing the server side of the Dynamic Authorization Extensions to the Remote Authentication Dial-In User Service (RADIUS) protocol. Copyright (C) The Internet Society (2006). Initial version as published in RFC 4673; for full legal notices see the RFC itself.
.1.3.6.1.2.1.146.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerMIBObjects,,,,,,
.1.3.6.1.2.1.146.1.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerScalars,,,,,,
.1.3.6.1.2.1.146.1.1.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerDisconInvalidClientAddresses,Counter32,read-only,,current,,The number of Disconnect-Request packets received from unknown addresses. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.1.2,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerCoAInvalidClientAddresses,Counter32,read-only,,current,,The number of CoA-Request packets received from unknown addresses. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.1.3,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerIdentifier,OCTET,read-only,,current,,The NAS-Identifier of the RADIUS Dynamic Authorization Server. This is not necessarily the same as sysName in MIB II.
.1.3.6.1.2.1.146.1.2,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthClientTable,,not-accessible,,current,,The (conceptual) table listing the RADIUS Dynamic Authorization Clients with which the server shares a secret.
.1.3.6.1.2.1.146.1.2.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthClientEntry,,not-accessible,radiusDynAuthClientIndex,current,,An entry (conceptual row) representing one Dynamic Authorization Client with which the server shares a secret.
.1.3.6.1.2.1.146.1.2.1.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthClientIndex,Integer32,not-accessible,,current,,A number uniquely identifying each RADIUS Dynamic Authorization Client with which this Dynamic Authorization Server communicates. This number is allocated by the agent implementing this MIB module and is unique in this context.
.1.3.6.1.2.1.146.1.2.1.2,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthClientAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of IP address of the RADIUS Dynamic Authorization Client referred to in this table entry.
.1.3.6.1.2.1.146.1.2.1.3,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthClientAddress,OCTET,read-only,,current,,The IP address value of the RADIUS Dynamic Authorization Client referred to in this table entry, using the version neutral IP address format. The type of this address is determined by the value of the radiusDynAuthClientAddressType object.
.1.3.6.1.2.1.146.1.2.1.4,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconRequests,Counter32,read-only,,current,,The number of RADIUS Disconnect-Requests received from this Dynamic Authorization Client. This also includes the RADIUS Disconnect-Requests that have a Service-Type attribute with value 'Authorize Only'. This counter may experience a discontinuity when the DAS module (re)starts as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.5,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconAuthOnlyRequests,Counter32,read-only,,current,,The number of RADIUS Disconnect-Requests that include a Service-Type attribute with value 'Authorize Only' received from this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.6,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDupDisconRequests,Counter32,read-only,,current,,The number of duplicate RADIUS Disconnect-Request packets received from this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.7,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconAcks,Counter32,read-only,,current,,The number of RADIUS Disconnect-ACK packets sent to this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.8,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconNaks,Counter32,read-only,,current,,The number of RADIUS Disconnect-NAK packets sent to this Dynamic Authorization Client. This includes the RADIUS Disconnect-NAK packets sent with a Service-Type attribute with value 'Authorize Only' and the RADIUS Disconnect-NAK packets sent because no session context was found. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.9,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconNakAuthOnlyRequests,Counter32,read-only,,current,,The number of RADIUS Disconnect-NAK packets that include a Service-Type attribute with value 'Authorize Only' sent to this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.10,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconNakSessNoContext,Counter32,read-only,,current,,The number of RADIUS Disconnect-NAK packets sent to this Dynamic Authorization Client because no session context was found. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.11,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconUserSessRemoved,Counter32,read-only,,current,,The number of user sessions removed for the Disconnect-Requests received from this Dynamic Authorization Client. Depending on site- specific policies, a single Disconnect request can remove multiple user sessions. In cases where this Dynamic Authorization Server has no knowledge of the number of user sessions that are affected by a single request, each such Disconnect-Request will count as a single affected user session only. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.12,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServMalformedDisconRequests,Counter32,read-only,,current,,The number of malformed RADIUS Disconnect-Request packets received from this Dynamic Authorization Client. Bad authenticators and unknown types are not included as malformed Disconnect-Requests. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.13,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconBadAuthenticators,Counter32,read-only,,current,,The number of RADIUS Disconnect-Request packets that contained an invalid Authenticator field received from this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.14,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDisconPacketsDropped,Counter32,read-only,,current,,The number of incoming Disconnect-Requests from this Dynamic Authorization Client silently discarded by the server application for some reason other than malformed, bad authenticators, or unknown types. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.15,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoARequests,Counter32,read-only,,current,,The number of RADIUS CoA-requests received from this Dynamic Authorization Client. This also includes the CoA requests that have a Service-Type attribute with value 'Authorize Only'. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.16,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoAAuthOnlyRequests,Counter32,read-only,,current,,The number of RADIUS CoA-requests that include a Service-Type attribute with value 'Authorize Only' received from this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.17,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServDupCoARequests,Counter32,read-only,,current,,The number of duplicate RADIUS CoA-Request packets received from this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.18,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoAAcks,Counter32,read-only,,current,,The number of RADIUS CoA-ACK packets sent to this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.19,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoANaks,Counter32,read-only,,current,,The number of RADIUS CoA-NAK packets sent to this Dynamic Authorization Client. This includes the RADIUS CoA-NAK packets sent with a Service-Type attribute with value 'Authorize Only' and the RADIUS CoA-NAK packets sent because no session context was found. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.20,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoANakAuthOnlyRequests,Counter32,read-only,,current,,The number of RADIUS CoA-NAK packets that include a Service-Type attribute with value 'Authorize Only' sent to this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.21,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoANakSessNoContext,Counter32,read-only,,current,,The number of RADIUS CoA-NAK packets sent to this Dynamic Authorization Client because no session context was found. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.22,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoAUserSessChanged,Counter32,read-only,,current,,The number of user sessions authorization changed for the CoA-Requests received from this Dynamic Authorization Client. Depending on site- specific policies, a single CoA request can change multiple user sessions' authorization. In cases where this Dynamic Authorization Server has no knowledge of the number of user sessions that are affected by a single request, each such CoA-Request will count as a single affected user session only. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.23,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServMalformedCoARequests,Counter32,read-only,,current,,The number of malformed RADIUS CoA-Request packets received from this Dynamic Authorization Client. Bad authenticators and unknown types are not included as malformed CoA-Requests. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.24,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoABadAuthenticators,Counter32,read-only,,current,,The number of RADIUS CoA-Request packets that contained an invalid Authenticator field received from this Dynamic Authorization Client. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.25,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServCoAPacketsDropped,Counter32,read-only,,current,,The number of incoming CoA packets from this Dynamic Authorization Client silently discarded by the server application for some reason other than malformed, bad authenticators, or unknown types. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.26,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServUnknownTypes,Counter32,read-only,,current,,The number of incoming packets of unknown types that were received on the Dynamic Authorization port. This counter may experience a discontinuity when the DAS module (re)starts, as indicated by the value of radiusDynAuthServerCounterDiscontinuity.
.1.3.6.1.2.1.146.1.2.1.27,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerCounterDiscontinuity,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last counter discontinuity. A discontinuity may be the result of a reinitialization of the DAS module within the managed entity.
.1.3.6.1.2.1.146.2,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerMIBConformance,,,,,,
.1.3.6.1.2.1.146.2.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerMIBCompliances,,,,,,
.1.3.6.1.2.1.146.2.1.1,RADIUS-DYNAUTH-SERVER-MIB::radiusAuthServerMIBCompliance,,,,,,The compliance statement for entities implementing the RADIUS Dynamic Authorization Server. Implementation of this module is for entities that support IPv4 and/or IPv6.
.1.3.6.1.2.1.146.2.2,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerMIBGroups,,,,,,
.1.3.6.1.2.1.146.2.2.1,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerMIBGroup,,,,,,The collection of objects providing management of a RADIUS Dynamic Authorization Server.
.1.3.6.1.2.1.146.2.2.2,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerAuthOnlyGroup,,,,,,The collection of objects supporting the RADIUS messages including Service-Type attribute with value 'Authorize Only'.
.1.3.6.1.2.1.146.2.2.3,RADIUS-DYNAUTH-SERVER-MIB::radiusDynAuthServerNoSessGroup,,,,,,The collection of objects supporting the RADIUS messages that are referring to non-existing sessions.
.1.3.6.1.2.1.147,T11-FC-VIRTUAL-FABRIC-MIB::t11FcVirtualFabricMIB,,,,,,This module defines management information specific to Fibre Channel Virtual Fabrics. A Virtual Fabric is a Fabric composed of partitions of switches, links and N_Ports with a single Fabric management domain, Fabric Services and independence from other Virtual Fabrics. Copyright (C) The IETF Trust (2006). This version of this MIB module is part of RFC 4747; see the RFC itself for full legal notices.
.1.3.6.1.2.1.147.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfObjects,,,,,,
.1.3.6.1.2.1.147.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfCoreSwitchTable,,not-accessible,,current,,A table of core switches supported by the current management entity.
.1.3.6.1.2.1.147.1.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfCoreSwitchEntry,,not-accessible,fcmInstanceIndex:t11vfCoreSwitchSwitchName,current,,Each entry represents one core switch.
.1.3.6.1.2.1.147.1.1.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfCoreSwitchSwitchName,OCTET,not-accessible,,current,,The Core Switch_Name (WWN) of this Core Switch.
.1.3.6.1.2.1.147.1.1.1.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfCoreSwitchMaxSupported,Unsigned32,read-write,,current,,In switches that do not support Virtual Fabrics, this object has the value of 1. If Virtual Fabrics are supported, this object is the maximum number of Virtual Fabrics supported by the Core Switch. For the purpose of this count, the Control VF_ID is ignored.
.1.3.6.1.2.1.147.1.1.1.3,T11-FC-VIRTUAL-FABRIC-MIB::t11vfCoreSwitchStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.147.1.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfVirtualSwitchTable,,not-accessible,,current,,A table of Virtual Switches. When one Core Switch provides switching functions for multiple Virtual Fabrics, that Core Switch is modeled as containing multiple Virtual Switches, one for each Virtual Fabric. This table contains one row for every Virtual Switch on every Core Switch. This table augments the basic switch information in the fcmSwitchTable Table in the FC-MGMT-MIB.
.1.3.6.1.2.1.147.1.2.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfVirtualSwitchEntry,,not-accessible,,current,,An entry of the Virtual Switch table. Each row is for a Virtual Switch. This table augments the fcmSwitchTable, i.e., every entry in this table has a one-to-one correspondence with an entry in the fcmSwitchTable. At the time when the fcmSwitchTable was defined, it applied to physical switches. With the definition and usage of virtual switches, fcmSwitchTable now applies to virtual switches as well as physical switches, and (in contrast to physical switches) it is appropriate to provide the capability for virtual switches to be created via remote management applications, e.g., via SNMP. So, this entry contains a RowStatus object (to allow the creation of a virtual switch), as well as a StorageType object. Obviously, if a row is created/deleted in this table, the corresponding row in the fcmSwitchTable will be created/deleted.
.1.3.6.1.2.1.147.1.2.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfVirtualSwitchVfId,Unsigned32,read-create,,current,,The VF_ID of the Virtual Fabric for which this virtual switch performs its switching function. The Control VF_ID is implicitly enabled and is not set. Communication with the Control VF_ID is required.
.1.3.6.1.2.1.147.1.2.1.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfVirtualSwitchCoreSwitchName,OCTET,read-only,,current,,The Core Switch_Name (WWN) of the Core Switch that contains this Virtual Switch.
.1.3.6.1.2.1.147.1.2.1.3,T11-FC-VIRTUAL-FABRIC-MIB::t11vfVirtualSwitchRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row.
.1.3.6.1.2.1.147.1.2.1.4,T11-FC-VIRTUAL-FABRIC-MIB::t11vfVirtualSwitchStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.147.1.3,T11-FC-VIRTUAL-FABRIC-MIB::t11vfPortTable,,not-accessible,,current,,A table of Port attributes related to Virtual Fabrics.
.1.3.6.1.2.1.147.1.3.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfPortEntry,,not-accessible,,current,,Each entry represents a physical Port on a switch. Switches that support Virtual Fabrics would add these four additional columns to the fcmPortEntry row.
.1.3.6.1.2.1.147.1.3.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfPortVfId,Unsigned32,read-write,,current,,The Port VF_ID assigned to this Port. The Port VF_ID is the default Virtual Fabric that is assigned to untagged frames arriving at this Port. The Control VF_ID is implicitly enabled and is not set. Communication with the Control VF_ID is required.
.1.3.6.1.2.1.147.1.3.1.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfPortTaggingAdminStatus,INTEGER,read-write,,current,off(1):on(2):auto(3),This object is used to configure the administrative status of Virtual Fabric tagging on this Port. SET operation Description -------------- ------------------------------------------- off(1) To disable Virtual Fabric tagging on this Port. on(2) To enable Virtual Fabric tagging on this Port if the attached Port doesn't prohibit it. auto(3) To enable Virtual Fabric tagging if the peer requests it.
.1.3.6.1.2.1.147.1.3.1.3,T11-FC-VIRTUAL-FABRIC-MIB::t11vfPortTaggingOperStatus,INTEGER,read-only,,current,off(1):on(2),This object is used to report the operational status of Virtual Fabric tagging on this Port. SET operation Description -------------- ------------------------------------------- off(1) Virtual Fabric tagging is disabled on this Port. on(2) Virtual Fabric tagging is enabled on this Port.
.1.3.6.1.2.1.147.1.3.1.4,T11-FC-VIRTUAL-FABRIC-MIB::t11vfPortStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row, and for the corresponding row in the augmented fcmPortTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.147.1.4,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledTable,,not-accessible,,current,,A table for assigning and reporting operational status of locally-enabled Virtual Fabric IDs to Ports. The set of Virtual Fabrics operational on the Port is the bit-wise 'AND' of the set of locally-enabled VF_IDs of this Port and the locally-enabled VF_IDs of the attached Port.
.1.3.6.1.2.1.147.1.4.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledEntry,,not-accessible,t11vfLocallyEnabledPortIfIndex:t11vfLocallyEnabledVfId,current,,An entry for each locally-enabled VF_ID on each Port.
.1.3.6.1.2.1.147.1.4.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledPortIfIndex,Integer32,not-accessible,,current,,The value of the ifIndex that identifies the Port.
.1.3.6.1.2.1.147.1.4.1.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledVfId,Unsigned32,not-accessible,,current,,A locally-enabled VF_ID on this Port.
.1.3.6.1.2.1.147.1.4.1.3,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledOperStatus,INTEGER,read-only,,current,off(1):on(2),This object is used to report the operational status of Virtual Fabric tagging on this Port. SET operation Description -------------- ------------------------------------------- off(1) Virtual Fabric tagging is disabled on this Port. on(2) Virtual Fabric tagging is enabled on this Port.
.1.3.6.1.2.1.147.1.4.1.4,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. When a row in this table is in 'active(1)' state, no object in that row can be modified except t11vfLocallyEnabledRowStatus and t11vfLocallyEnabledStorageType.
.1.3.6.1.2.1.147.1.4.1.5,T11-FC-VIRTUAL-FABRIC-MIB::t11vfLocallyEnabledStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.147.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfConformance,,,,,,
.1.3.6.1.2.1.147.2.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfMIBCompliances,,,,,,
.1.3.6.1.2.1.147.2.1.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfMIBCompliance,,,,,,Describes the requirements for compliance to the Fibre Channel Virtual Fabric MIB.
.1.3.6.1.2.1.147.2.2,T11-FC-VIRTUAL-FABRIC-MIB::t11vfMIBGroups,,,,,,
.1.3.6.1.2.1.147.2.2.1,T11-FC-VIRTUAL-FABRIC-MIB::t11vfGeneralGroup,,,,,,A collection of objects for monitoring and configuring Virtual Fabrics in a Fibre Channel switch.
.1.3.6.1.2.1.148,SIP-TC-MIB::sipTC,,,,,,Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION module used by other SIP-related MIB Modules. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4780; see the RFC itself for full legal notices.
.1.3.6.1.2.1.149,SIP-COMMON-MIB::sipCommonMIB,,,,,,Session Initiation Protocol (SIP) Common MIB module. This module defines objects that may be common to all SIP entities. SIP is an application-layer signaling protocol for creating, modifying and terminating multimedia sessions with one or more participants. These sessions include Internet multimedia conferences and Internet telephone calls. SIP is defined in RFC 3261 (June 2002). This MIB is defined for managing objects that are common to SIP User Agents (UAs), Proxy, Redirect, and Registrar servers. Objects specific to each of these entities MAY be managed using entity specific MIBs defined in other modules. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4780; see the RFC itself for full legal notices.
.1.3.6.1.2.1.149.0,SIP-COMMON-MIB::sipCommonMIBNotifications,,,,,,
.1.3.6.1.2.1.149.0.1,SIP-COMMON-MIB::sipCommonStatusCodeNotif,,,,,,Signifies that a specific status code has been sent or received by the system.
.1.3.6.1.2.1.149.0.2,SIP-COMMON-MIB::sipCommonStatusCodeThreshExceededInNotif,,,,,,Signifies that a specific status code was found to have been received by the system frequently enough to exceed the configured threshold. This notification can be used as an early warning mechanism in lieu of using sipCommonStatusCodeNotif.
.1.3.6.1.2.1.149.0.3,SIP-COMMON-MIB::sipCommonStatusCodeThreshExceededOutNotif,,,,,,Signifies that a specific status code was found to have been sent by the system enough to exceed the configured threshold. This notification can be used as an early warning mechanism in lieu of using sipCommonStatusCodeNotif.
.1.3.6.1.2.1.149.0.4,SIP-COMMON-MIB::sipCommonServiceColdStart,,,,,,Signifies that the SIP service has reinitialized itself or started for the first time. This SHOULD result from a hard 'down' to 'up' administrative status change. The configuration or behavior of the service MAY be altered.
.1.3.6.1.2.1.149.0.5,SIP-COMMON-MIB::sipCommonServiceWarmStart,,,,,,Signifies that the SIP service has reinitialized itself and is restarting after an administrative 'reset'. The configuration or behavior of the service MAY be altered.
.1.3.6.1.2.1.149.0.6,SIP-COMMON-MIB::sipCommonServiceStatusChanged,,,,,,Signifies that the SIP service operational status has changed.
.1.3.6.1.2.1.149.1,SIP-COMMON-MIB::sipCommonMIBObjects,,,,,,
.1.3.6.1.2.1.149.1.1,SIP-COMMON-MIB::sipCommonCfgBase,,,,,,
.1.3.6.1.2.1.149.1.1.1,SIP-COMMON-MIB::sipCommonCfgTable,,not-accessible,,current,,This table contains the common configuration objects applicable to all SIP entities.
.1.3.6.1.2.1.149.1.1.1.1,SIP-COMMON-MIB::sipCommonCfgEntry,,not-accessible,applIndex,current,,A row of common configuration. Each row represents objects for a particular SIP entity instance present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.1.1.1.1,SIP-COMMON-MIB::sipCommonCfgProtocolVersion,OCTET,read-only,,current,,This object will reflect the version of SIP supported by this SIP entity. It will follow the same format as SIP version information contained in the SIP messages generated by this SIP entity. For example, entities supporting SIP version 2 will return 'SIP/2.0' as dictated by the standard.
.1.3.6.1.2.1.149.1.1.1.1.2,SIP-COMMON-MIB::sipCommonCfgServiceOperStatus,INTEGER,read-only,,current,unknown(1):up(2):down(3):congested(4):restarting(5):quiescing(6):testing(7),This object contains the current operational state of the SIP application. unknown : The operational status cannot be determined for some reason. up : The application is operating normally and is processing (receiving and possibly issuing) SIP requests and responses. down : The application is currently unable to process SIP messages. congested : The application is operational but no additional inbound transactions can be accommodated at the moment. restarting : The application is currently unavailable, but it is in the process of restarting and will presumably, soon be able to process SIP messages. quiescing : The application is currently operational but has been administratively put into quiescence mode. Additional inbound transactions MAY be rejected. testing : The application is currently in test mode and MAY not be able to process SIP messages. The operational status values defined for this object are not based on any specific information contained in the SIP standard.
.1.3.6.1.2.1.149.1.1.1.1.3,SIP-COMMON-MIB::sipCommonCfgServiceStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time the SIP entity was last started. If started prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.149.1.1.1.1.4,SIP-COMMON-MIB::sipCommonCfgServiceLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time the SIP entity entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.149.1.1.1.1.5,SIP-COMMON-MIB::sipCommonCfgOrganization,OCTET,read-only,,current,,This object contains the organization name that the SIP entity inserts into Organization headers of SIP messages processed by this system. If the string is empty, no Organization header is to be generated.
.1.3.6.1.2.1.149.1.1.1.1.6,SIP-COMMON-MIB::sipCommonCfgMaxTransactions,Unsigned32,read-only,,current,,This object indicates the maximum number of simultaneous transactions per second that the SIP entity can manage. In general, the value of this object SHOULD reflect a level of transaction processing per second that is considered high enough to impact the system's CPU and/or memory resources to the point of deteriorating SIP call processing but not high enough to cause catastrophic system failure.
.1.3.6.1.2.1.149.1.1.1.1.7,SIP-COMMON-MIB::sipCommonCfgServiceNotifEnable,BITS,read-write,,current,sipCommonServiceColdStart(0):sipCommonServiceWarmStart(1):sipCommonServiceStatusChanged(2),This object specifies which SIP service related notifications are enabled. Each bit represents a specific notification. If a bit has a value 1, the associated notification is enabled and will be generated by the SIP entity at the appropriate time. Support for these notifications is OPTIONAL: either none or all notification values are supported. If an implementation does not support this object, it should return a 'noSuchObject' exception to an SNMP GET operation. If notifications are supported, this object's default value SHOULD reflect sipCommonServiceColdStart and sipCommonServiceWarmStart enabled and sipCommonServiceStatusChanged disabled. This object value SHOULD persist across reboots.
.1.3.6.1.2.1.149.1.1.1.1.8,SIP-COMMON-MIB::sipCommonCfgEntityType,BITS,read-only,,current,other(0):userAgent(1):proxyServer(2):redirectServer(3):registrarServer(4),This object identifies the list of SIP entities to which this row is related. It is defined as a bit map. Each bit represents a type of SIP entity. If a bit has value 1, the SIP entity represented by this row plays the role of this entity type. If a bit has value 0, the SIP entity represented by this row does not act as this entity type. Combinations of bits can be set when the SIP entity plays multiple SIP roles.
.1.3.6.1.2.1.149.1.1.2,SIP-COMMON-MIB::sipCommonPortTable,,not-accessible,,current,,This table contains the list of ports that each SIP entity in this system is allowed to use. These ports can be advertised using the Contact header in a REGISTER request or response.
.1.3.6.1.2.1.149.1.1.2.1,SIP-COMMON-MIB::sipCommonPortEntry,,not-accessible,applIndex:sipCommonPort,current,,Specification of a particular port. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.1.2.1.1,SIP-COMMON-MIB::sipCommonPort,Unsigned32,not-accessible,,current,,This object reflects a particular port that can be used by the SIP application.
.1.3.6.1.2.1.149.1.1.2.1.2,SIP-COMMON-MIB::sipCommonPortTransportRcv,BITS,read-only,,current,other(0):udp(1):tcp(2):sctp(3):tlsTcp(4):tlsSctp(5),This object will specify the transport protocol the SIP entity will use to receive SIP messages. This object is a bit map. Each bit represents a transport protocol. If a bit has value 1, then that transport protocol is currently being used. If a bit has value 0, then that transport protocol is currently not being used.
.1.3.6.1.2.1.149.1.1.3,SIP-COMMON-MIB::sipCommonOptionTagTable,,not-accessible,,current,,This table contains a list of the SIP option tags (SIP extensions) that are either required, supported, or unsupported by the SIP entity. These option tags are used in the Require, Proxy-Require, Supported, and Unsupported header fields. Example: If a user agent client supports, and requires the server to support, reliability of provisional responses (RFC 3262), this table contains a row with the option tag string '100rel' in sipCommonOptionTag and the OCTET STRING value of '1010 0000' or '0xA0' in sipCommonOptionTagHeaderField. If a server does not support the required feature (indicated in a Require header to a UAS, or in a Proxy-Require to a Proxy Server), the server returns a 420 Bad Extension listing the feature in an Unsupported header. Normally, the list of such features supported by an entity is static (i.e., will not change over time).
.1.3.6.1.2.1.149.1.1.3.1,SIP-COMMON-MIB::sipCommonOptionTagEntry,,not-accessible,applIndex:sipCommonOptionTagIndex,current,,A particular SIP option tag (extension) supported or unsupported by the SIP entity, and which may be supported or required by a peer. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.1.3.1.1,SIP-COMMON-MIB::sipCommonOptionTagIndex,Unsigned32,not-accessible,,current,,This object uniquely identifies a conceptual row in the table.
.1.3.6.1.2.1.149.1.1.3.1.2,SIP-COMMON-MIB::sipCommonOptionTag,OCTET,read-only,,current,,This object indicates the SIP option tag. The option tag names are registered with IANA and available at http://www.iana.org.
.1.3.6.1.2.1.149.1.1.3.1.3,SIP-COMMON-MIB::sipCommonOptionTagHeaderField,BITS,read-only,,current,require(0):proxyRequire(1):supported(2):unsupported(3),This object indicates whether the SIP option tag is supported (Supported header), unsupported (Unsupported header), or required (Require or Proxy-Require header) by the SIP entity. A SIP option tag may be both supported and required.
.1.3.6.1.2.1.149.1.1.4,SIP-COMMON-MIB::sipCommonMethodSupportedTable,,not-accessible,,current,,This table contains a list of methods supported by each SIP entity in this system (see the standard set of SIP methods in Section 7.1 of RFC 3261). Any additional methods that may be incorporated into the SIP protocol can be represented by this table without any requirement to update this MIB module. The table is informational in nature and conveys capabilities of the managed system to the SNMP Manager. From a protocol point of view, the list of methods advertised by the SIP entity in the Allow header (Section 20.5 of RFC 3261) MUST be consistent with the methods reflected in this table.
.1.3.6.1.2.1.149.1.1.4.1,SIP-COMMON-MIB::sipCommonMethodSupportedEntry,,not-accessible,applIndex:sipCommonMethodSupportedIndex,current,,A particular method supported by the SIP entity. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.1.4.1.1,SIP-COMMON-MIB::sipCommonMethodSupportedIndex,Unsigned32,not-accessible,,current,,This object uniquely identifies a conceptual row in the table and reflects an assigned number used to identify a specific SIP method. This identifier is suitable for referencing the associated method throughout this and other MIBs supported by this managed system.
.1.3.6.1.2.1.149.1.1.4.1.2,SIP-COMMON-MIB::sipCommonMethodSupportedName,OCTET,read-only,,current,,This object reflects the supported method's name. The method name MUST be all upper case (e.g., 'INVITE').
.1.3.6.1.2.1.149.1.2,SIP-COMMON-MIB::sipCommonCfgTimer,,,,,,
.1.3.6.1.2.1.149.1.2.1,SIP-COMMON-MIB::sipCommonCfgTimerTable,,not-accessible,,current,,This table contains timer configuration objects applicable to SIP user agent and SIP stateful Proxy Server entities.
.1.3.6.1.2.1.149.1.2.1.1,SIP-COMMON-MIB::sipCommonCfgTimerEntry,,not-accessible,applIndex,current,,A row of timer configuration. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The objects in this table entry SHOULD be non-volatile and their value SHOULD be kept at reboot.
.1.3.6.1.2.1.149.1.2.1.1.1,SIP-COMMON-MIB::sipCommonCfgTimerA,Unsigned32,read-only,,current,,This object reflects the initial value for the retransmit timer for the INVITE method. The retransmit timer doubles after each retransmission, ensuring an exponential backoff in network traffic. This object represents the initial time a SIP entity will wait to receive a provisional response to an INVITE before resending the INVITE request.
.1.3.6.1.2.1.149.1.2.1.1.2,SIP-COMMON-MIB::sipCommonCfgTimerB,Unsigned32,read-only,,current,,This object reflects the maximum time a SIP entity will wait to receive a final response to an INVITE. The timer is started upon transmission of the initial INVITE request.
.1.3.6.1.2.1.149.1.2.1.1.3,SIP-COMMON-MIB::sipCommonCfgTimerC,Unsigned32,read-only,,current,,This object reflects the maximum time a SIP Proxy Server will wait to receive a provisional response to an INVITE. The Timer C MUST be set for each client transaction when an INVITE request is proxied.
.1.3.6.1.2.1.149.1.2.1.1.4,SIP-COMMON-MIB::sipCommonCfgTimerD,Unsigned32,read-only,,current,,This object reflects the amount of time that the server transaction can remain in the 'Completed' state when unreliable transports are used. The default value MUST be equal to or greater than 32000 for UDP transport, and its value MUST be 0 for TCP/SCTP transport.
.1.3.6.1.2.1.149.1.2.1.1.5,SIP-COMMON-MIB::sipCommonCfgTimerE,Unsigned32,read-only,,current,,This object reflects the initial value for the retransmit timer for a non-INVITE method while in 'Trying' state. The retransmit timer doubles after each retransmission until it reaches T2 to ensure an exponential backoff in network traffic. This object represents the initial time a SIP entity will wait to receive a provisional response to the request before resending the non-INVITE request.
.1.3.6.1.2.1.149.1.2.1.1.6,SIP-COMMON-MIB::sipCommonCfgTimerF,Unsigned32,read-only,,current,,This object reflects the maximum time a SIP entity will wait to receive a final response to a non-INVITE request. The timer is started upon transmission of the initial request.
.1.3.6.1.2.1.149.1.2.1.1.7,SIP-COMMON-MIB::sipCommonCfgTimerG,Unsigned32,read-only,,current,,This object reflects the initial value for the retransmit timer for final responses to INVITE requests. If timer G fires, the response is passed to the transport layer again for retransmission, and timer G is set to fire in MIN(2*T1, T2) seconds. From then on, when timer G fires, the response is passed to the transport again for transmission, and timer G is reset with a value that doubles, unless that value exceeds T2, in which case, it is reset with the value of T2. The default value MUST be T1 for UDP transport, and its value MUST be 0 for reliable transport like TCP/SCTP.
.1.3.6.1.2.1.149.1.2.1.1.8,SIP-COMMON-MIB::sipCommonCfgTimerH,Unsigned32,read-only,,current,,This object reflects the maximum time a server will wait to receive an ACK before it abandons retransmitting the response. The timer is started upon entering the 'Completed' state.
.1.3.6.1.2.1.149.1.2.1.1.9,SIP-COMMON-MIB::sipCommonCfgTimerI,Unsigned32,read-only,,current,,This object reflects the maximum time a SIP entity will wait to receive additional ACK message retransmissions. The timer is started upon entering the 'Confirmed' state. The default value MUST be T4 for UDP transport and its value MUST be 0 for reliable transport like TCP/SCTP.
.1.3.6.1.2.1.149.1.2.1.1.10,SIP-COMMON-MIB::sipCommonCfgTimerJ,Unsigned32,read-only,,current,,This object reflects the maximum time a SIP server will wait to receive retransmissions of non-INVITE requests. The timer is started upon entering the 'Completed' state for non-INVITE transactions. When timer J fires, the server MUST transition to the 'Terminated' state.
.1.3.6.1.2.1.149.1.2.1.1.11,SIP-COMMON-MIB::sipCommonCfgTimerK,Unsigned32,read-only,,current,,This object reflects the maximum time a SIP client will wait to receive retransmissions of responses to non-INVITE requests. The timer is started upon entering the 'Completed' state for non-INVITE transactions. When timer K fires, the server MUST transition to the 'Terminated' state. The default value MUST be T4 for UDP transport, and its value MUST be 0 for reliable transport like TCP/SCTP.
.1.3.6.1.2.1.149.1.2.1.1.12,SIP-COMMON-MIB::sipCommonCfgTimerT1,Unsigned32,read-only,,current,,This object reflects the T1 timer for a SIP entity. T1 is an estimate of the round-trip time (RTT) between the client and server transactions.
.1.3.6.1.2.1.149.1.2.1.1.13,SIP-COMMON-MIB::sipCommonCfgTimerT2,Unsigned32,read-only,,current,,This object reflects the T2 timer for a SIP entity. T2 is the maximum retransmit interval for non-INVITE requests and INVITE responses. It's used in various parts of the protocol to reset other Timer* objects to this value.
.1.3.6.1.2.1.149.1.2.1.1.14,SIP-COMMON-MIB::sipCommonCfgTimerT4,Unsigned32,read-only,,current,,This object reflects the T4 timer for a SIP entity. T4 is the maximum duration a message will remain in the network. It represents the amount of time the network will take to clear messages between client and server transactions. It's used in various parts of the protocol to reset other Timer* objects to this value.
.1.3.6.1.2.1.149.1.3,SIP-COMMON-MIB::sipCommonSummaryStats,,,,,,
.1.3.6.1.2.1.149.1.3.1,SIP-COMMON-MIB::sipCommonSummaryStatsTable,,not-accessible,,current,,This table contains the summary statistics objects applicable to all SIP entities. Each row represents those objects for a particular SIP entity present in this system.
.1.3.6.1.2.1.149.1.3.1.1,SIP-COMMON-MIB::sipCommonSummaryStatsEntry,,not-accessible,applIndex,current,,A row of summary statistics. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.3.1.1.1,SIP-COMMON-MIB::sipCommonSummaryInRequests,Counter32,read-only,,current,,This object indicates the total number of SIP request messages received by the SIP entity, including retransmissions. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonSummaryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.3.1.1.2,SIP-COMMON-MIB::sipCommonSummaryOutRequests,Counter32,read-only,,current,,This object contains the total number of SIP request messages sent out (originated and relayed) by the SIP entity. Where a particular message is sent more than once, for example as a retransmission or as a result of forking, each transmission is counted separately. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonSummaryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.3.1.1.3,SIP-COMMON-MIB::sipCommonSummaryInResponses,Counter32,read-only,,current,,This object contains the total number of SIP response messages received by the SIP entity, including retransmissions. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonSummaryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.3.1.1.4,SIP-COMMON-MIB::sipCommonSummaryOutResponses,Counter32,read-only,,current,,This object contains the total number of SIP response messages sent (originated and relayed) by the SIP entity including retransmissions. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonSummaryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.3.1.1.5,SIP-COMMON-MIB::sipCommonSummaryTotalTransactions,Counter32,read-only,,current,,This object contains a count of the number of transactions that are in progress and transactions that have reached the 'Terminated' state. It is not applicable to stateless SIP Proxy Servers. A SIP transaction occurs between a client and a server, and comprises all messages from the first request sent from the client to the server, up to a final (non-1xx) response sent from the server to the client. If the request is INVITE and the final response is a non-2xx, the transaction also include an ACK to the response. The ACK for a 2xx response to an INVITE request is a separate transaction. The branch ID parameter in the Via header field values serves as a transaction identifier. A transaction is identified by the CSeq sequence number within a single call leg. The ACK request has the same CSeq number as the corresponding INVITE request, but comprises a transaction of its own. In the case of a forked request, each branch counts as a single transaction. For a transaction stateless Proxy Server, this counter is always 0. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonSummaryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.3.1.1.6,SIP-COMMON-MIB::sipCommonSummaryDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the summary statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.149.1.4,SIP-COMMON-MIB::sipCommonMethodStats,,,,,,
.1.3.6.1.2.1.149.1.4.1,SIP-COMMON-MIB::sipCommonMethodStatsTable,,not-accessible,,current,,This table contains the method statistics objects for SIP entities. Each row represents those objects for a particular SIP entity present in this system.
.1.3.6.1.2.1.149.1.4.1.1,SIP-COMMON-MIB::sipCommonMethodStatsEntry,,not-accessible,applIndex:sipCommonMethodStatsName,current,,A row of per entity method statistics. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.4.1.1.1,SIP-COMMON-MIB::sipCommonMethodStatsName,OCTET,not-accessible,,current,,This object uniquely identifies the SIP method related to the objects in a particular row.
.1.3.6.1.2.1.149.1.4.1.1.2,SIP-COMMON-MIB::sipCommonMethodStatsOutbounds,Counter32,read-only,,current,,This object reflects the total number of requests sent by the SIP entity, excluding retransmissions. Retransmissions are counted separately and are not reflected in this counter. A Management Station can detect discontinuities in this counter by monitoring the sipCommonMethodStatsDisconTime object in the same row.
.1.3.6.1.2.1.149.1.4.1.1.3,SIP-COMMON-MIB::sipCommonMethodStatsInbounds,Counter32,read-only,,current,,This object reflects the total number of requests received by the SIP entity. Retransmissions are counted separately and are not reflected in this counter. A Management Station can detect discontinuities in this counter by monitoring the sipCommonMethodStatsDisconTime object in the same row.
.1.3.6.1.2.1.149.1.4.1.1.4,SIP-COMMON-MIB::sipCommonMethodStatsDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the method statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.149.1.5,SIP-COMMON-MIB::sipCommonStatusCode,,,,,,
.1.3.6.1.2.1.149.1.5.1,SIP-COMMON-MIB::sipCommonStatusCodeTable,,not-accessible,,current,,This table contains the list of SIP status codes that each SIP entity in this system has been requested to monitor. It is the mechanism by which specific status codes are monitored. Entries created in this table must not persist across reboots.
.1.3.6.1.2.1.149.1.5.1.1,SIP-COMMON-MIB::sipCommonStatusCodeEntry,,not-accessible,applIndex:sipCommonStatusCodeMethod:sipCommonStatusCodeValue,current,,This row contains information on a particular SIP status code that the SIP entity has been requested to monitor. Entries created in this table must not persist across reboots. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.5.1.1.1,SIP-COMMON-MIB::sipCommonStatusCodeMethod,OCTET,not-accessible,,current,,This object uniquely identifies a conceptual row in the table.
.1.3.6.1.2.1.149.1.5.1.1.2,SIP-COMMON-MIB::sipCommonStatusCodeValue,Unsigned32,not-accessible,,current,,This object contains a SIP status code value that the SIP entity has been requested to monitor. All of the other information in the row is related to this value.
.1.3.6.1.2.1.149.1.5.1.1.3,SIP-COMMON-MIB::sipCommonStatusCodeIns,Counter32,read-only,,current,,This object reflects the total number of response messages received by the SIP entity with the status code value contained in the sipCommonStatusCodeValue column. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service, or when the monitoring of the status code is temporarily disabled. A Management Station can detect discontinuities in this counter by monitoring the sipCommonStatusCodeDisconTime object in the same row.
.1.3.6.1.2.1.149.1.5.1.1.4,SIP-COMMON-MIB::sipCommonStatusCodeOuts,Counter32,read-only,,current,,This object reflects the total number of response messages sent by the SIP entity with the status code value contained in the sipCommonStatusCodeValue column. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service, or when the monitoring of the Status code is temporarily disabled. A Management Station can detect discontinuities in this counter by monitoring the sipCommonStatusCodeDisconTime object in the same row.
.1.3.6.1.2.1.149.1.5.1.1.5,SIP-COMMON-MIB::sipCommonStatusCodeRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row augmentation in sipCommonStatusCodeNotifTable will be governed by the value of this RowStatus. The values 'createAndGo' and 'destroy' are the only valid values allowed for this object. If a row exists, it will reflect a status of 'active' when queried.
.1.3.6.1.2.1.149.1.5.1.1.6,SIP-COMMON-MIB::sipCommonStatusCodeDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the status code statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.149.1.5.2,SIP-COMMON-MIB::sipCommonStatusCodeNotifTable,,not-accessible,,current,,This table contains objects to control notifications related to particular status codes that each SIP entity in this system has been requested to monitor. There is an entry in this table corresponding to each entry in sipCommonStatusCodeTable. Therefore, this table augments sipCommonStatusCodeTable and utilizes the same index methodology. The objects in this table are not included directly in the sipCommonStatusCodeTable simply to keep the status code notification control objects separate from the actual status code statistics.
.1.3.6.1.2.1.149.1.5.2.1,SIP-COMMON-MIB::sipCommonStatusCodeNotifEntry,,not-accessible,,current,,This row contains information controlling notifications for a particular SIP status code that the SIP entity has been requested to monitor.
.1.3.6.1.2.1.149.1.5.2.1.1,SIP-COMMON-MIB::sipCommonStatusCodeNotifSend,INTEGER,read-write,,current,true(1):false(2),This object controls whether a sipCommonStatusCodeNotif is emitted when the status code value specified by sipCommonStatusCodeValue is sent or received. If the value of this object is 'true', then a notification is sent. If it is 'false', no notification is sent. Note well that a notification MAY be emitted for every message sent or received that contains the particular status code. Depending on the status code involved, this can cause a significant number of notification emissions that could be detrimental to network performance. Managers are forewarned to be prudent in the use of this object to enable notifications. Look to sipCommonStatusCodeNotifEmitMode for alternative controls for sipCommonStatusCodeNotif emissions.
.1.3.6.1.2.1.149.1.5.2.1.2,SIP-COMMON-MIB::sipCommonStatusCodeNotifEmitMode,INTEGER,read-write,,current,normal(1):oneShot(2):triggered(3),The object sipCommonStatusCodeNotifSend MUST be set to 'true' for the values of this object to have any effect. It is RECOMMENDED that the desired emit mode be established by this object prior to setting sipCommonStatusCodeNotifSend to 'true'. This object and the sipCommonStatusCodeNotifSend object can obviously be set independently, but their respective values will have a dependency on each other and the resulting notifications. This object specifies the mode for emissions of sipCommonStatusCodeNotif notifications. normal : sipCommonStatusCodeNotif notifications will be emitted by the system for each SIP response message sent or received that contains the desired status code. oneShot : Only one sipCommonStatusCodeNotif notification will be emitted. It will be the next SIP response message sent or received that contains the desired status code. No more notifications are emitted until this object is set to 'oneShot' again or set to 'normal'. This option is provided as a means of quelling the potential promiscuous behavior that can be associated with the sipCommonStatusCodeNotif. triggered : This value is only readable and cannot be set. It reflects that the 'oneShot' case has occurred, and indicates that the mode needs to be reset to get further notifications. The mode is reset by setting this object to 'oneShot' or 'normal'.
.1.3.6.1.2.1.149.1.5.2.1.3,SIP-COMMON-MIB::sipCommonStatusCodeNotifThresh,Unsigned32,read-write,,current,,This object specifies the number of response messages sent or received by this system that are considered excessive. Based on crossing that threshold, a sipCommonStatusCodeThreshExceededInNotif notification or a sipCommonStatusCodeThreshExceededOutNotif will be sent. The sipCommonStatusCodeThreshExceededInNotif and sipCommonStatusCodeThreshExceededOutNotif notifications can be used as an early warning mechanism in lieu of using sipCommonStatusCodeNotif. Note that the configuration applied by this object will be applied equally to inbound and outbound response messages.
.1.3.6.1.2.1.149.1.5.2.1.4,SIP-COMMON-MIB::sipCommonStatusCodeNotifInterval,Unsigned32,read-write,,current,,This object specifies the time interval over which, if sipCommonStatusCodeThresh is exceeded with respect to sent or received messages, a sipCommonStatusCodeThreshExceededInNotif or sipCommonStatusCodeThreshExceededOutNotif notification will be sent. Note that the configuration applied by this object will be applied equally to inbound and outbound response messages.
.1.3.6.1.2.1.149.1.6,SIP-COMMON-MIB::sipCommonStatsTrans,,,,,,
.1.3.6.1.2.1.149.1.6.1,SIP-COMMON-MIB::sipCommonTransCurrentTable,,not-accessible,,current,,This table contains information on the transactions currently awaiting definitive responses by each SIP entity in this system. This table does not apply to transaction stateless Proxy Servers.
.1.3.6.1.2.1.149.1.6.1.1,SIP-COMMON-MIB::sipCommonTransCurrentEntry,,not-accessible,applIndex,current,,Information on a particular SIP entity's current transactions. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.6.1.1.1,SIP-COMMON-MIB::sipCommonTransCurrentactions,Gauge32,read-only,,current,,This object contains the number of transactions awaiting definitive (non-1xx) response. In the case of a forked request, each branch counts as a single transaction corresponding to the entity identified by applIndex.
.1.3.6.1.2.1.149.1.7,SIP-COMMON-MIB::sipCommonStatsRetry,,,,,,
.1.3.6.1.2.1.149.1.7.1,SIP-COMMON-MIB::sipCommonStatsRetryTable,,not-accessible,,current,,This table contains retry statistics objects applicable to each SIP entity in this system.
.1.3.6.1.2.1.149.1.7.1.1,SIP-COMMON-MIB::sipCommonStatsRetryEntry,,not-accessible,applIndex:sipCommonStatsRetryMethod,current,,A row of retry statistics. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.7.1.1.1,SIP-COMMON-MIB::sipCommonStatsRetryMethod,OCTET,not-accessible,,current,,This object uniquely identifies the SIP method related to the objects in a row.
.1.3.6.1.2.1.149.1.7.1.1.2,SIP-COMMON-MIB::sipCommonStatsRetries,Counter32,read-only,,current,,This object reflects the total number of request retransmissions that have been sent by the SIP entity. Note that there could be multiple retransmissions per request. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonStatsRetryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.7.1.1.3,SIP-COMMON-MIB::sipCommonStatsRetryFinalResponses,Counter32,read-only,,current,,This object reflects the total number of Final Response retries that have been sent by the SIP entity. Note that there could be multiple retransmissions per request. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonStatsRetryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.7.1.1.4,SIP-COMMON-MIB::sipCommonStatsRetryNonFinalResponses,Counter32,read-only,,current,,This object reflects the total number of non-Final Response retries that have been sent by the SIP entity. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonStatsRetryDisconTime object in the same row.
.1.3.6.1.2.1.149.1.7.1.1.5,SIP-COMMON-MIB::sipCommonStatsRetryDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the retry statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.149.1.8,SIP-COMMON-MIB::sipCommonOtherStats,,,,,,
.1.3.6.1.2.1.149.1.8.1,SIP-COMMON-MIB::sipCommonOtherStatsTable,,not-accessible,,current,,This table contains other common statistics supported by each SIP entity in this system.
.1.3.6.1.2.1.149.1.8.1.1,SIP-COMMON-MIB::sipCommonOtherStatsEntry,,not-accessible,applIndex,current,,Information on a particular SIP entity's other common statistics. Each row represents those objects for a particular SIP entity present in this system. applIndex is used to uniquely identify these instances of SIP entities and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788).
.1.3.6.1.2.1.149.1.8.1.1.1,SIP-COMMON-MIB::sipCommonOtherStatsNumUnsupportedUris,Counter32,read-only,,current,,Number of RequestURIs received with an unsupported scheme. A server normally responds to such requests with a 400 Bad Request status code. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonOtherStatsDisconTime object in the same row.
.1.3.6.1.2.1.149.1.8.1.1.2,SIP-COMMON-MIB::sipCommonOtherStatsNumUnsupportedMethods,Counter32,read-only,,current,,Number of SIP requests received with unsupported methods. A server normally responds to such requests with a 501 (Not Implemented) or 405 (Method Not Allowed). Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonOtherStatsDisconTime object in the same row.
.1.3.6.1.2.1.149.1.8.1.1.3,SIP-COMMON-MIB::sipCommonOtherStatsOtherwiseDiscardedMsgs,Counter32,read-only,,current,,Number of SIP messages received that, for any number of reasons, was discarded without a response. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipCommonOtherStatsDisconTime object in the same row.
.1.3.6.1.2.1.149.1.8.1.1.4,SIP-COMMON-MIB::sipCommonOtherStatsDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.149.1.9,SIP-COMMON-MIB::sipCommonNotifObjects,,,,,,
.1.3.6.1.2.1.149.1.9.1,SIP-COMMON-MIB::sipCommonStatusCodeNotifTo,OCTET,accessible-for-notify,,current,,This object contains the value of the To header in the message containing the status code that caused the notification. The header name will be part of this object value. For example, 'To: Watson '.
.1.3.6.1.2.1.149.1.9.2,SIP-COMMON-MIB::sipCommonStatusCodeNotifFrom,OCTET,accessible-for-notify,,current,,This object contains the value of the From header in the message containing the status code that caused the notification. The header name will be part of this object value. For example, 'From: Watson '.
.1.3.6.1.2.1.149.1.9.3,SIP-COMMON-MIB::sipCommonStatusCodeNotifCallId,OCTET,accessible-for-notify,,current,,This object contains the value of the Call-ID in the message containing the status code that caused the notification. The header name will be part of this object value. For example, 'Call-ID: 5551212@example.com'.
.1.3.6.1.2.1.149.1.9.4,SIP-COMMON-MIB::sipCommonStatusCodeNotifCSeq,Unsigned32,accessible-for-notify,,current,,This object contains the CSeq value in the message containing the status code that caused the notification. The header name will be part of this object value. For example, 'CSeq: 1722 INVITE'.
.1.3.6.1.2.1.149.1.9.5,SIP-COMMON-MIB::sipCommonNotifApplIndex,Unsigned32,accessible-for-notify,,current,,This object contains the applIndex as described in RFC 2788. This object is created in order to allow a variable binding containing a value of applIndex in a notification.
.1.3.6.1.2.1.149.1.9.6,SIP-COMMON-MIB::sipCommonNotifSequenceNumber,Unsigned32,accessible-for-notify,,current,,This object contains a sequence number for each notification generated by this SIP entity. Each notification SHOULD have a unique sequence number. A network manager can use this information to determine whether notifications from a particular SIP entity have been missed. The value of this object MUST start at 1 and increase by 1 with each generated notification. If a system restarts, the sequence number MAY start again from 1.
.1.3.6.1.2.1.149.2,SIP-COMMON-MIB::sipCommonMIBConformance,,,,,,
.1.3.6.1.2.1.149.2.1,SIP-COMMON-MIB::sipCommonMIBCompliances,,,,,,
.1.3.6.1.2.1.149.2.1.1,SIP-COMMON-MIB::sipCommonCompliance,,,,,,The compliance statement for SIP entities.
.1.3.6.1.2.1.149.2.2,SIP-COMMON-MIB::sipCommonMIBGroups,,,,,,
.1.3.6.1.2.1.149.2.2.1,SIP-COMMON-MIB::sipCommonConfigGroup,,,,,,A collection of objects providing configuration common to all SIP entities.
.1.3.6.1.2.1.149.2.2.2,SIP-COMMON-MIB::sipCommonInformationalGroup,,,,,,A collection of objects providing configuration common to all SIP entities.
.1.3.6.1.2.1.149.2.2.3,SIP-COMMON-MIB::sipCommonConfigTimerGroup,,,,,,A collection of objects providing timer configuration common to all SIP entities.
.1.3.6.1.2.1.149.2.2.4,SIP-COMMON-MIB::sipCommonStatsGroup,,,,,,A collection of objects providing statistics common to all SIP entities.
.1.3.6.1.2.1.149.2.2.5,SIP-COMMON-MIB::sipCommonStatsRetryGroup,,,,,,A collection of objects providing retry statistics.
.1.3.6.1.2.1.149.2.2.6,SIP-COMMON-MIB::sipCommonNotifGroup,,,,,,A collection of notifications common to all SIP entities.
.1.3.6.1.2.1.149.2.2.7,SIP-COMMON-MIB::sipCommonStatusCodeNotifGroup,,,,,,A collection of objects related to the control and attribution of notifications common to all SIP entities.
.1.3.6.1.2.1.149.2.2.8,SIP-COMMON-MIB::sipCommonNotifObjectsGroup,,,,,,A collection of accessible-for-notify objects related to the notification defined in this MIB module.
.1.3.6.1.2.1.150,SIP-UA-MIB::sipUAMIB,,,,,,Session Initiation Protocol (SIP) User Agent (UA) MIB module. SIP is an application-layer signaling protocol for creating, modifying, and terminating multimedia sessions with one or more participants. These sessions include Internet multimedia conferences and Internet telephone calls. SIP is defined in RFC 3261 (June 2002). A User Agent is an application that contains both a User Agent Client (UAC) and a User Agent Server (UAS). A UAC is an application that initiates a SIP request. A UAS is an application that contacts the user when a SIP request is received and that returns a response on behalf of the user. The response accepts, rejects, or redirects the request. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4780; see the RFC itself for full legal notices.
.1.3.6.1.2.1.150.1,SIP-UA-MIB::sipUAMIBObjects,,,,,,
.1.3.6.1.2.1.150.1.1,SIP-UA-MIB::sipUACfgServer,,,,,,
.1.3.6.1.2.1.150.1.1.1,SIP-UA-MIB::sipUACfgServerTable,,not-accessible,,current,,This table contains SIP server configuration objects applicable to each SIP user agent in this system.
.1.3.6.1.2.1.150.1.1.1.1,SIP-UA-MIB::sipUACfgServerEntry,,not-accessible,applIndex:sipUACfgServerIndex,current,,A row of server configuration. Each row represents those objects for a particular SIP user agent present in this system. applIndex is used to uniquely identify these instances of SIP user agents and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.150.1.1.1.1.1,SIP-UA-MIB::sipUACfgServerIndex,Unsigned32,not-accessible,,current,,A unique identifier of a server address when multiple addresses are configured by the SIP entity. If one address isn't reachable, then another can be tried.
.1.3.6.1.2.1.150.1.1.1.1.2,SIP-UA-MIB::sipUACfgServerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object reflects the type of address contained in the associated instance of sipUACfgServerAddress.
.1.3.6.1.2.1.150.1.1.1.1.3,SIP-UA-MIB::sipUACfgServerAddress,OCTET,read-only,,current,,This object reflects the address of a SIP server this user agent will use to proxy/redirect calls. The type of this address is determined by the value of the sipUACfgServerAddressType object.
.1.3.6.1.2.1.150.1.1.1.1.4,SIP-UA-MIB::sipUACfgServerRole,BITS,read-only,,current,other(0):userAgent(1):proxyServer(2):redirectServer(3):registrarServer(4),This object reflects the function of the SIP server this user agent should communicate with: registrar, proxy (outbound proxy), etc.
.1.3.6.1.2.1.150.2,SIP-UA-MIB::sipUAMIBConformance,,,,,,
.1.3.6.1.2.1.150.2.1,SIP-UA-MIB::sipUAMIBCompliances,,,,,,
.1.3.6.1.2.1.150.2.1.1,SIP-UA-MIB::sipUACompliance,,,,,,The compliance statement for SIP entities that implement the SIP-UA-MIB module.
.1.3.6.1.2.1.150.2.2,SIP-UA-MIB::sipUAMIBGroups,,,,,,
.1.3.6.1.2.1.150.2.2.1,SIP-UA-MIB::sipUAConfigGroup,,,,,,A collection of objects providing information about the configuration of SIP User Agents.
.1.3.6.1.2.1.151,SIP-SERVER-MIB::sipServerMIB,,,,,,Session Initiation Protocol (SIP) Server MIB module. SIP is an application-layer signaling protocol for creating, modifying, and terminating multimedia sessions with one or more participants. These sessions include Internet multimedia conferences and Internet telephone calls. SIP is defined in RFC 3261 (June 2002). This MIB is defined for the management of SIP Proxy, Redirect, and Registrar Servers. A Proxy Server acts as both a client and a server. It accepts requests from other clients, either responding to them or passing them on to other servers, possibly after modification. A Redirect Server accepts requests from clients and returns zero or more addresses to that client. Unlike a User Agent Server, it does not accept calls. A Registrar is a server that accepts REGISTER requests. A Registrar is typically co-located with a Proxy or Redirect Server. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4780; see the RFC itself for full legal notices.
.1.3.6.1.2.1.151.1,SIP-SERVER-MIB::sipServerMIBObjects,,,,,,
.1.3.6.1.2.1.151.1.1,SIP-SERVER-MIB::sipServerCfg,,,,,,
.1.3.6.1.2.1.151.1.1.1,SIP-SERVER-MIB::sipServerCfgTable,,not-accessible,,current,,This table contains configuration objects applicable to SIP Redirect and Proxy Servers.
.1.3.6.1.2.1.151.1.1.1.1,SIP-SERVER-MIB::sipServerCfgEntry,,not-accessible,applIndex,current,,A row of common configuration. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.1.1.1.1,SIP-SERVER-MIB::sipServerCfgHostAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address by which the SIP server is reachable.
.1.3.6.1.2.1.151.1.1.1.1.2,SIP-SERVER-MIB::sipServerCfgHostAddress,OCTET,read-only,,current,,This is the host portion of a SIP URI that is assigned to the SIP server. It MAY contain a fully qualified domain name or an IP address. The length of the value will depend on the type of address specified. The type of address given by this object is controlled by sipServerCfgHostAddressType.
.1.3.6.1.2.1.151.1.3,SIP-SERVER-MIB::sipServerProxyCfg,,,,,,
.1.3.6.1.2.1.151.1.3.1,SIP-SERVER-MIB::sipServerProxyCfgTable,,not-accessible,,current,,This table contains configuration objects applicable to SIP Proxy Servers.
.1.3.6.1.2.1.151.1.3.1.1,SIP-SERVER-MIB::sipServerProxyCfgEntry,,not-accessible,applIndex,current,,A row of common proxy configuration. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.3.1.1.1,SIP-SERVER-MIB::sipServerCfgProxyStatefulness,INTEGER,read-only,,current,stateless(1):transactionStateful(2):callStateful(3),This object reflects the default mode of operation for the Proxy Server entity. A stateless proxy is a logical entity that does not maintain the client or server transaction state machines when it processes requests. A stateless proxy forwards every request it receives downstream and every response it receives upstream. If the value of this object is stateless(1), the proxy defaults to stateless operations. A transaction stateful proxy, or simply a 'stateful proxy', is a logical entity that maintains the client and server transaction state machines during the processing of a request. A (transaction) stateful proxy is not the same as a call stateful proxy. If the value of this object is transactionStateful(2), the proxy is stateful on a transaction basis. A call stateful proxy is a logical entity if it retains state for a dialog from the initiating INVITE to the terminating BYE request. A call stateful proxy is always transaction stateful, but the converse is not necessarily true. If the value of this object is callStateful(3), the proxy is call stateful.
.1.3.6.1.2.1.151.1.3.1.1.2,SIP-SERVER-MIB::sipServerCfgProxyRecursion,INTEGER,read-only,,current,true(1):false(2),This object reflects whether or not the Proxy performs a recursive search on the Contacts provided in 3xx redirects. If the value of this object is 'true', a recursive search is performed. If the value is 'false', no search is performed, and the 3xx response is sent upstream towards the source of the request.
.1.3.6.1.2.1.151.1.3.1.1.3,SIP-SERVER-MIB::sipServerCfgProxyRecordRoute,INTEGER,read-only,,current,true(1):false(2),This object reflects whether or not the proxy adds itself to the Record-Route header as a default action. This header is used to list the proxies that insist on being in the signaling path for subsequent requests related to the call leg. If the value of this object is 'true', the proxy adds itself to the end of the Record-Route header, creating the header if required. If the value is 'false', the proxy does not add itself to the Record-Route header.
.1.3.6.1.2.1.151.1.3.1.1.4,SIP-SERVER-MIB::sipServerCfgProxyAuthMethod,BITS,read-only,,current,none(0):tls(1):digest(2),This object reflects the authentication methods that MAY be used to authenticate request originators. bit 0 no authentication is performed bit 1 TLS is used bit 2 HTTP Digest is used.
.1.3.6.1.2.1.151.1.3.1.1.5,SIP-SERVER-MIB::sipServerCfgProxyAuthDefaultRealm,OCTET,read-only,,current,,This object reflects the default realm value used in Proxy-Authenticate headers. Note that this MAY need to be stored per user, in which case, this default value is ignored. 
.1.3.6.1.2.1.151.1.4,SIP-SERVER-MIB::sipServerProxyStats,,,,,,
.1.3.6.1.2.1.151.1.4.1,SIP-SERVER-MIB::sipServerProxyStatsTable,,not-accessible,,current,,This table contains the statistics objects applicable to all SIP Proxy Servers in this system.
.1.3.6.1.2.1.151.1.4.1.1,SIP-SERVER-MIB::sipServerProxyStatsEntry,,not-accessible,applIndex,current,,A row of summary statistics. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.4.1.1.1,SIP-SERVER-MIB::sipServerProxyStatProxyReqFailures,Counter32,read-only,,current,,This object contains the number of occurrences of unsupported options being specified in received Proxy-Require headers. Such occurrences result in a 420 Bad Extension status code being returned. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerProxyStatsDisconTime object in the same row.
.1.3.6.1.2.1.151.1.4.1.1.2,SIP-SERVER-MIB::sipServerProxyStatsDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the server statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.151.1.5,SIP-SERVER-MIB::sipServerRegCfg,,,,,,
.1.3.6.1.2.1.151.1.5.1,SIP-SERVER-MIB::sipServerRegCfgTable,,not-accessible,,current,,This table contains configuration objects applicable to SIP Registrars.
.1.3.6.1.2.1.151.1.5.1.1,SIP-SERVER-MIB::sipServerRegCfgEntry,,not-accessible,applIndex,current,,A row of common Registrar configuration. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.5.1.1.1,SIP-SERVER-MIB::sipServerRegMaxContactExpiryDuration,Unsigned32,read-only,,current,,This object reflects the maximum expiry that may be requested by a User Agent for a particular Contact. User Agents can specify expiry using either an Expiry header in a REGISTER request, or using an Expires parameter in a Contact header in a REGISTER request. If the value requested by the User Agent is greater than the value of this object, then the contact information is given the duration specified by this object, and that duration is indicated to the User Agent in the response.
.1.3.6.1.2.1.151.1.5.1.1.2,SIP-SERVER-MIB::sipServerRegMaxUsers,Unsigned32,read-only,,current,,This object reflects the maximum number of users that the Registrar supports. The current number of users is reflected by sipServerRegCurrentUsers.
.1.3.6.1.2.1.151.1.5.1.1.3,SIP-SERVER-MIB::sipServerRegCurrentUsers,Gauge32,read-only,,current,,This object reflects the number of users currently registered with the Registrar.
.1.3.6.1.2.1.151.1.5.1.1.4,SIP-SERVER-MIB::sipServerRegDfltRegActiveInterval,Unsigned32,read-only,,current,,This object reflects the default time interval the Registrar considers registrations to be active. The value is used to compute the Expires header in the REGISTER response. If a user agent requests a time interval shorter than specified by this object, the Registrar SHOULD honor that request. If a Contact entry does not have an 'expires' parameter, the value of the Expires header field is used instead. If a Contact entry has no 'expires' parameter and no Expires header field is present, the value of this object is used as the default value.
.1.3.6.1.2.1.151.1.5.2,SIP-SERVER-MIB::sipServerRegUserTable,,not-accessible,,current,,This table contains information on all users registered to each Registrar in this system.
.1.3.6.1.2.1.151.1.5.2.1,SIP-SERVER-MIB::sipServerRegUserEntry,,not-accessible,applIndex:sipServerRegUserIndex,current,,This entry contains information for a single user registered to this Registrar. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.5.2.1.1,SIP-SERVER-MIB::sipServerRegUserIndex,Unsigned32,not-accessible,,current,,This object uniquely identifies a conceptual row in the table.
.1.3.6.1.2.1.151.1.5.2.1.2,SIP-SERVER-MIB::sipServerRegUserUri,OCTET,read-only,,current,,This object contains the user's address-of-record. It is the main form by which the Registrar knows the user. The format is typically 'user@domain'. It is contained in the To header for all REGISTER requests.
.1.3.6.1.2.1.151.1.5.2.1.3,SIP-SERVER-MIB::sipServerRegUserAuthenticationFailures,Counter32,read-only,,current,,This object contains a count of the number of times the user has failed authentication. Discontinuities in the value of this counter can occur due to successful user authentications and at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerRegUserDisconTime object in the same row.
.1.3.6.1.2.1.151.1.5.2.1.4,SIP-SERVER-MIB::sipServerRegUserDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the user registration statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.151.1.5.3,SIP-SERVER-MIB::sipServerRegContactTable,,not-accessible,,current,,This table contains information on every location where a registered user (specified by sipServerRegUserIndex) wishes to be found (i.e., the user has provided contact information to each SIP Registrar in this system).
.1.3.6.1.2.1.151.1.5.3.1,SIP-SERVER-MIB::sipServerRegContactEntry,,not-accessible,applIndex:sipServerRegUserIndex:sipServerRegContactIndex,current,,This entry contains information for a single Contact. Multiple contacts may exist for a single user. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.5.3.1.1,SIP-SERVER-MIB::sipServerRegContactIndex,Unsigned32,not-accessible,,current,,Along with the sipServerRegUserIndex, this object uniquely identifies a conceptual row in the table.
.1.3.6.1.2.1.151.1.5.3.1.2,SIP-SERVER-MIB::sipServerRegContactDisplayName,OCTET,read-only,,current,,This object contains the display name for the Contact. For example, 'Santa at Home', or 'Santa on his Sled', corresponding to contact URIs of sip:BigGuy@example.com or sip:sclaus817@example.com, respectively.
.1.3.6.1.2.1.151.1.5.3.1.3,SIP-SERVER-MIB::sipServerRegContactURI,OCTET,read-only,,current,,This object contains either a SIP URI where the user can be contacted. This URI is normally returned to a client from a Redirect Server, or is used as the RequestURI in a SIP request line for requests forwarded by a proxy.
.1.3.6.1.2.1.151.1.5.3.1.4,SIP-SERVER-MIB::sipServerRegContactLastUpdated,TimeTicks,read-only,,current,,This object indicates the time when this contact information was accepted. If the contact information is updated via a subsequent REGISTER of the same information, this object is also updated.
.1.3.6.1.2.1.151.1.5.3.1.5,SIP-SERVER-MIB::sipServerRegContactExpiry,OCTET,read-only,,current,,This object contains the date and time when the contact information will no longer be valid. Such times may be specified by the user at registration (i.e., Expires header or expiry parameter in the Contact information), or a system default can be applied.
.1.3.6.1.2.1.151.1.5.3.1.6,SIP-SERVER-MIB::sipServerRegContactPreference,OCTET,read-only,,current,,This object indicates a relative preference for the particular Contact header field value compared to other bindings for this address-of-record. A registering user may provide this preference as a 'qvalue' parameter in the Contact header. The format of this item is a decimal number between 0 and 1 (for example 0.9). Higher values indicate locations preferred by the user.
.1.3.6.1.2.1.151.1.6,SIP-SERVER-MIB::sipServerRegStats,,,,,,
.1.3.6.1.2.1.151.1.6.1,SIP-SERVER-MIB::sipServerRegStatsTable,,not-accessible,,current,,This table contains the summary statistics objects applicable to all SIP Registrars in this system.
.1.3.6.1.2.1.151.1.6.1.1,SIP-SERVER-MIB::sipServerRegStatsEntry,,not-accessible,applIndex,current,,A row of summary statistics. Each row represents those objects for a particular SIP server present in this system. applIndex is used to uniquely identify these instances of SIP servers and correlate them through the common framework of the NETWORK-SERVICES-MIB (RFC 2788). The same value of applIndex used in the corresponding SIP-COMMON-MIB is used here.
.1.3.6.1.2.1.151.1.6.1.1.1,SIP-SERVER-MIB::sipServerRegStatsAcceptedRegs,Counter32,read-only,,current,,This object contains a count of the number of REGISTER requests that have been accepted (status code 200) by the Registrar. This includes additions of new contact information, refreshing contact information, as well as requests for deletion of contact information. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerRegStatsDisconTime object in the same row.
.1.3.6.1.2.1.151.1.6.1.1.2,SIP-SERVER-MIB::sipServerRegStatsRejectedRegs,Counter32,read-only,,current,,This object contains a count of the number REGISTER requests that have been rejected by the Registrar. Discontinuities in the value of this counter can occur at re-initialization of the SIP entity or service. A Management Station can detect discontinuities in this counter by monitoring the sipServerRegStatsDisconTime object in the same row.
.1.3.6.1.2.1.151.1.6.1.1.3,SIP-SERVER-MIB::sipServerRegStatsDisconTime,TimeTicks,read-only,,current,,The value of the sysUpTime object when the counters for the registrar statistics objects in this row last experienced a discontinuity.
.1.3.6.1.2.1.151.2,SIP-SERVER-MIB::sipServerMIBConformance,,,,,,
.1.3.6.1.2.1.151.2.1,SIP-SERVER-MIB::sipServerMIBCompliances,,,,,,
.1.3.6.1.2.1.151.2.1.1,SIP-SERVER-MIB::sipServerProxyServerCompliance,,,,,,The compliance statement for SIP entities acting as Proxy Servers.
.1.3.6.1.2.1.151.2.1.2,SIP-SERVER-MIB::sipRedirectServerCompliance,,,,,,The compliance statement for SIP entities acting as Redirect Servers.
.1.3.6.1.2.1.151.2.1.3,SIP-SERVER-MIB::sipServerRegistrarServerCompliance,,,,,,The compliance statement for SIP entities acting as Registrars.
.1.3.6.1.2.1.151.2.2,SIP-SERVER-MIB::sipServerMIBGroups,,,,,,
.1.3.6.1.2.1.151.2.2.1,SIP-SERVER-MIB::sipServerConfigGroup,,,,,,A collection of objects providing configuration common to SIP Proxy and Redirect servers.
.1.3.6.1.2.1.151.2.2.2,SIP-SERVER-MIB::sipServerProxyConfigGroup,,,,,,A collection of objects providing configuration for SIP Proxy servers.
.1.3.6.1.2.1.151.2.2.3,SIP-SERVER-MIB::sipServerProxyStatsGroup,,,,,,A collection of objects providing statistics for SIP Proxy servers.
.1.3.6.1.2.1.151.2.2.4,SIP-SERVER-MIB::sipServerRegistrarConfigGroup,,,,,,A collection of objects providing configuration for SIP Registrars.
.1.3.6.1.2.1.151.2.2.5,SIP-SERVER-MIB::sipServerRegistrarStatsGroup,,,,,,A collection of objects providing statistics for SIP Registrars.
.1.3.6.1.2.1.151.2.2.6,SIP-SERVER-MIB::sipServerRegistrarUsersGroup,,,,,,A collection of objects related to registered users.
.1.3.6.1.2.1.152,IANA-GMPLS-TC-MIB::ianaGmpls,,,,,,Copyright (C) The IETF Trust (2007). The initial version of this MIB module was published in RFC 4802. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.153,IPSEC-SPD-MIB::spdMIB,,,,,,This MIB module defines configuration objects for managing IPsec Security Policies. In general, this MIB can be implemented anywhere IPsec security services exist (e.g., bump-in-the-wire, host, gateway, firewall, router, etc.). Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4807; see the RFC itself for full legal notices.
.1.3.6.1.2.1.153.1,IPSEC-SPD-MIB::spdConfigObjects,,,,,,
.1.3.6.1.2.1.153.1.1,IPSEC-SPD-MIB::spdLocalConfigObjects,,,,,,
.1.3.6.1.2.1.153.1.1.1,IPSEC-SPD-MIB::spdIngressPolicyGroupName,OCTET,read-write,,current,,This object indicates the global system policy group that is to be applied on ingress packets (i.e., arriving at an interface from a network) when a given endpoint does not contain a policy definition in the spdEndpointToGroupTable. Its value can be used as an index into the spdGroupContentsTable to retrieve a list of policies. A zero length string indicates that no system-wide policy exists and the default policy of 'drop' SHOULD be executed for ingress packets until one is imposed by either this object or by the endpoint processing a given packet. This object MUST be persistent
.1.3.6.1.2.1.153.1.1.2,IPSEC-SPD-MIB::spdEgressPolicyGroupName,OCTET,read-write,,current,,This object indicates the policy group containing the global system policy that is to be applied on egress packets (i.e., packets leaving an interface and entering a network) when a given endpoint does not contain a policy definition in the spdEndpointToGroupTable. Its value can be used as an index into the spdGroupContentsTable to retrieve a list of policies. A zero length string indicates that no system-wide policy exists and the default policy of 'drop' SHOULD be executed for egress packets until one is imposed by either this object or by the endpoint processing a given packet. This object MUST be persistent
.1.3.6.1.2.1.153.1.2,IPSEC-SPD-MIB::spdEndpointToGroupTable,,not-accessible,,current,,This table maps policies (groupings) onto an endpoint (interface). A policy group assigned to an endpoint is then used to control access to the network traffic passing through that endpoint. If an endpoint has been configured with a policy group and no rule within that policy group matches that packet, the default action in this case SHALL be to drop the packet. If no policy group has been assigned to an endpoint, then the policy group specified by spdIngressPolicyGroupName MUST be used on traffic inbound from the network through that endpoint, and the policy group specified by spdEgressPolicyGroupName MUST be used for traffic outbound to the network through that endpoint.
.1.3.6.1.2.1.153.1.2.1,IPSEC-SPD-MIB::spdEndpointToGroupEntry,,not-accessible,spdEndGroupDirection:spdEndGroupInterface,current,,A mapping assigning a policy group to an endpoint.
.1.3.6.1.2.1.153.1.2.1.1,IPSEC-SPD-MIB::spdEndGroupDirection,INTEGER,not-accessible,,current,inbound(1):outbound(2),This object indicates which direction of packets crossing the interface are associated with which spdEndGroupName object. Ingress packets, or packets into the device match when this value is inbound(1). Egress packets or packets out of the device match when this value is outbound(2).
.1.3.6.1.2.1.153.1.2.1.2,IPSEC-SPD-MIB::spdEndGroupInterface,Integer32,not-accessible,,current,,This value matches the IF-MIB's ifTable's ifIndex column and indicates the interface associated with a given endpoint. This object can be used to uniquely identify an endpoint that a set of policy groups are applied to.
.1.3.6.1.2.1.153.1.2.1.3,IPSEC-SPD-MIB::spdEndGroupName,OCTET,read-create,,current,,The policy group name to apply at this endpoint. The value of the spdEndGroupName object is then used as an index into the spdGroupContentsTable to come up with a list of rules that MUST be applied at this endpoint.
.1.3.6.1.2.1.153.1.2.1.4,IPSEC-SPD-MIB::spdEndGroupLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.2.1.5,IPSEC-SPD-MIB::spdEndGroupStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.2.1.6,IPSEC-SPD-MIB::spdEndGroupRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. This object is considered 'notReady' and MUST NOT be set to active until one or more active rows exist within the spdGroupContentsTable for the group referenced by the spdEndGroupName object.
.1.3.6.1.2.1.153.1.3,IPSEC-SPD-MIB::spdGroupContentsTable,,not-accessible,,current,,This table contains a list of rules and/or subgroups contained within a given policy group. For a given value of spdGroupContName, the set of rows sharing that value forms a 'group'. The rows in a group MUST be processed according to the value of the spdGroupContPriority object in each row. The processing MUST be executed starting with the lowest value of spdGroupContPriority and in ascending order thereafter. If an action is executed as the result of the processing of a row in a group, the processing of further rows in that group MUST stop. Iterating to the next policy group row by finding the next largest spdGroupContPriority object SHALL only be done if no actions were run while processing the current row for a given packet.
.1.3.6.1.2.1.153.1.3.1,IPSEC-SPD-MIB::spdGroupContentsEntry,,not-accessible,spdGroupContName:spdGroupContPriority,current,,Defines a given sub-component within a policy group. A sub-component is either a rule or another group as indicated by spdGroupContComponentType and referenced by spdGroupContComponentName.
.1.3.6.1.2.1.153.1.3.1.1,IPSEC-SPD-MIB::spdGroupContName,OCTET,not-accessible,,current,,The administrative name of the group associated with this row. A 'group' is formed by all the rows in this table that have the same value of this object.
.1.3.6.1.2.1.153.1.3.1.2,IPSEC-SPD-MIB::spdGroupContPriority,Integer32,not-accessible,,current,,The priority (sequence number) of the sub-component in a group that this row represents. This value indicates the order that each row of this table MUST be processed from low to high. For example, a row with a priority of 0 is processed before a row with a priority of 1, a 1 before a 2, etc.
.1.3.6.1.2.1.153.1.3.1.3,IPSEC-SPD-MIB::spdGroupContFilter,OBJECT,read-create,,current,,spdGroupContFilter points to a filter that is evaluated to determine whether the spdGroupContComponentName within this row is exercised. Managers can use this object to classify groups of rules, or subgroups, together in order to achieve a greater degree of control and optimization over the execution order of the items within the group. If the filter evaluates to false, the rule or subgroup will be skipped and the next rule or subgroup will be evaluated instead. This value can be used to indicate a scalar or row in a table. When indicating a row in a table, this value MUST point to the first column instance in that row. An example usage of this object would be to limit a group of rules to executing only when the IP packet being processed is designated to be processed by IKE. This effectively creates a group of IKE-specific rules. The following tables and scalars can be pointed to by this column. All but diffServMultiFieldClfrTable are defined in this MIB: diffServMultiFieldClfrTable spdIpOffsetFilterTable spdTimeFilterTable spdCompoundFilterTable spdTrueFilter spdIpsoHeaderFilterTable Implementations MAY choose to provide support for other filter tables or scalars. If this column is set to a VariablePointer value, which references a non-existent row in an otherwise supported table, the inconsistentName exception MUST be returned. If the table or scalar pointed to by the VariablePointer is not supported at all, then an inconsistentValue exception MUST be returned. If, during packet processing, a row in this table is applied to a packet and the value of this column in that row references a non-existent or non-supported object, the packet MUST be dropped.
.1.3.6.1.2.1.153.1.3.1.4,IPSEC-SPD-MIB::spdGroupContComponentType,INTEGER,read-create,,current,group(1):rule(2),Indicates whether the spdGroupContComponentName object is the name of another group defined within the spdGroupContentsTable or is the name of a rule defined within the spdRuleDefinitionTable.
.1.3.6.1.2.1.153.1.3.1.5,IPSEC-SPD-MIB::spdGroupContComponentName,OCTET,read-create,,current,,The name of the policy rule or subgroup contained within this row, as indicated by the spdGroupContComponentType object.
.1.3.6.1.2.1.153.1.3.1.6,IPSEC-SPD-MIB::spdGroupContLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.3.1.7,IPSEC-SPD-MIB::spdGroupContStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.3.1.8,IPSEC-SPD-MIB::spdGroupContRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. This object MUST NOT be set to active until the row to which the spdGroupContComponentName points to exists and is active. If active, this object MUST remain active unless one of the following two conditions are met: I. No active row in spdEndpointToGroupTable exists that references this row's group (i.e., indicate this row's spdGroupContName). II. Or at least one other active row in this table has a matching spdGroupContName. If neither condition is met, an attempt to set this row to something other than active MUST result in an inconsistentValue error.
.1.3.6.1.2.1.153.1.4,IPSEC-SPD-MIB::spdRuleDefinitionTable,,not-accessible,,current,,This table defines a rule by associating a filter or a set of filters to an action to be executed.
.1.3.6.1.2.1.153.1.4.1,IPSEC-SPD-MIB::spdRuleDefinitionEntry,,not-accessible,spdRuleDefName,current,,A row defining a particular rule definition. A rule definition binds a filter pointer to an action pointer.
.1.3.6.1.2.1.153.1.4.1.1,IPSEC-SPD-MIB::spdRuleDefName,OCTET,not-accessible,,current,,spdRuleDefName is the administratively assigned name of the rule referred to by the spdGroupContComponentName object.
.1.3.6.1.2.1.153.1.4.1.2,IPSEC-SPD-MIB::spdRuleDefDescription,OCTET,read-create,,current,,A user defined string. This field MAY be used for administrative tracking purposes.
.1.3.6.1.2.1.153.1.4.1.3,IPSEC-SPD-MIB::spdRuleDefFilter,OBJECT,read-create,,current,,spdRuleDefFilter points to a filter that is used to evaluate whether the action associated with this row is executed or not. The action will only execute if the filter referenced by this object evaluates to TRUE after first applying any negation required by the spdRuleDefFilterNegated object. The following tables and scalars can be pointed to by this column. All but diffServMultiFieldClfrTable are defined in this MIB. Implementations MAY choose to provide support for other filter tables or scalars as well: diffServMultiFieldClfrTable spdIpOffsetFilterTable spdTimeFilterTable spdCompoundFilterTable spdTrueFilter If this column is set to a VariablePointer value, which references a non-existent row in an otherwise supported table, the inconsistentName exception MUST be returned. If the table or scalar pointed to by the VariablePointer is not supported at all, then an inconsistentValue exception MUST be returned. If, during packet processing, this column has a value that references a non-existent or non-supported object, the packet MUST be dropped.
.1.3.6.1.2.1.153.1.4.1.4,IPSEC-SPD-MIB::spdRuleDefFilterNegated,INTEGER,read-create,,current,true(1):false(2),spdRuleDefFilterNegated specifies whether or not the results of the filter referenced by the spdRuleDefFilter object is negated.
.1.3.6.1.2.1.153.1.4.1.5,IPSEC-SPD-MIB::spdRuleDefAction,OBJECT,read-create,,current,,This column points to the action to be taken. It MAY, but is not limited to, point to a row in one of the following tables: spdCompoundActionTable ipsaSaPreconfiguredActionTable ipiaIkeActionTable ipiaIpsecActionTable It MAY also point to one of the scalar objects beneath spdStaticActions. If this object is set to a pointer to a row in an unsupported (or unknown) table, an inconsistentValue error MUST be returned. If this object is set to point to a non-existent row in an otherwise supported table, an inconsistentName error MUST be returned. If, during packet processing, this column has a value that references a non-existent or non-supported object, the packet MUST be dropped.
.1.3.6.1.2.1.153.1.4.1.6,IPSEC-SPD-MIB::spdRuleDefAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),Indicates whether the current rule definition is considered active. If the value is enabled, the rule MUST be evaluated when processing packets. If the value is disabled, the packet processing MUST continue as if this rule's filter had effectively failed.
.1.3.6.1.2.1.153.1.4.1.7,IPSEC-SPD-MIB::spdRuleDefLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.4.1.8,IPSEC-SPD-MIB::spdRuleDefStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.4.1.9,IPSEC-SPD-MIB::spdRuleDefRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. This object MUST NOT be set to active until the containing conditions, filters, and actions have been defined. Once active, it MUST remain active until no active policyGroupContents entries are referencing it. A failed attempt to do so MUST return an inconsistentValue error.
.1.3.6.1.2.1.153.1.5,IPSEC-SPD-MIB::spdCompoundFilterTable,,not-accessible,,current,,A table defining compound filters and their associated parameters. A row in this table can be pointed to by a spdRuleDefFilter object.
.1.3.6.1.2.1.153.1.5.1,IPSEC-SPD-MIB::spdCompoundFilterEntry,,not-accessible,spdCompFiltName,current,,An entry in the spdCompoundFilterTable. Each entry in this table represents a compound filter. A filter defined by this table is considered to have a TRUE return value if and only if: spdCompFiltLogicType is AND and all of the sub-filters associated with it, as defined in the spdSubfiltersTable, are all true themselves (after applying any required negation, as defined by the ficFilterIsNegated object). spdCompFiltLogicType is OR and at least one of the sub-filters associated with it, as defined in the spdSubfiltersTable, is true itself (after applying any required negation, as defined by the ficFilterIsNegated object.
.1.3.6.1.2.1.153.1.5.1.1,IPSEC-SPD-MIB::spdCompFiltName,OCTET,not-accessible,,current,,A user definable string. This value is used as an index into this table.
.1.3.6.1.2.1.153.1.5.1.2,IPSEC-SPD-MIB::spdCompFiltDescription,OCTET,read-create,,current,,A user definable string. This field MAY be used for your administrative tracking purposes.
.1.3.6.1.2.1.153.1.5.1.3,IPSEC-SPD-MIB::spdCompFiltLogicType,INTEGER,read-create,,current,or(1):and(2),Indicates whether the sub-component filters of this compound filter are functionally ANDed or ORed together.
.1.3.6.1.2.1.153.1.5.1.4,IPSEC-SPD-MIB::spdCompFiltLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.5.1.5,IPSEC-SPD-MIB::spdCompFiltStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.5.1.6,IPSEC-SPD-MIB::spdCompFiltRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. Once active, it MUST NOT have its value changed if any active rows in the spdRuleDefinitionTable are currently pointing at this row.
.1.3.6.1.2.1.153.1.6,IPSEC-SPD-MIB::spdSubfiltersTable,,not-accessible,,current,,This table defines a list of filters contained within a given compound filter defined in the spdCompoundFilterTable.
.1.3.6.1.2.1.153.1.6.1,IPSEC-SPD-MIB::spdSubfiltersEntry,,not-accessible,spdCompFiltName:spdSubFiltPriority,current,,An entry in the spdSubfiltersTable. There is an entry in this table for each sub-filter of all compound filters present in the spdCompoundFilterTable.
.1.3.6.1.2.1.153.1.6.1.1,IPSEC-SPD-MIB::spdSubFiltPriority,Integer32,not-accessible,,current,,The priority of a given filter within a compound filter. The order of execution is from lowest to highest priority value (i.e., priority 0 before priority 1, 1 before 2, etc.). Implementations MAY choose to follow this ordering, as set by the manager that created the rows. This can allow a manager to intelligently construct filter lists such that faster filters are evaluated first.
.1.3.6.1.2.1.153.1.6.1.2,IPSEC-SPD-MIB::spdSubFiltSubfilter,OBJECT,read-create,,current,,The OID of the contained filter. The value of this object is a VariablePointer that references the filter to be included in this compound filter. The following tables and scalars can be pointed to by this column. All but diffServMultiFieldClfrTable are defined in this MIB. Implementations MAY choose to provide support for other filter tables or scalars as well: diffServMultiFieldClfrTable spdIpsoHeaderFilterTable spdIpOffsetFilterTable spdTimeFilterTable spdCompoundFilterTable spdTrueFilter If this column is set to a VariablePointer value that references a non-existent row in an otherwise supported table, the inconsistentName exception MUST be returned. If the table or scalar pointed to by the VariablePointer is not supported at all, then an inconsistentValue exception MUST be returned. If, during packet processing, this column has a value that references a non-existent or non-supported object, the packet MUST be dropped.
.1.3.6.1.2.1.153.1.6.1.3,IPSEC-SPD-MIB::spdSubFiltSubfilterIsNegated,INTEGER,read-create,,current,true(1):false(2),Indicates whether or not the result of applying this sub-filter is negated.
.1.3.6.1.2.1.153.1.6.1.4,IPSEC-SPD-MIB::spdSubFiltLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.6.1.5,IPSEC-SPD-MIB::spdSubFiltStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.6.1.6,IPSEC-SPD-MIB::spdSubFiltRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. This object cannot be made active until a filter referenced by the spdSubFiltSubfilter object is both defined and active. An attempt to do so MUST result in an inconsistentValue error. If active, this object MUST remain active unless one of the following two conditions are met: I. No active row in the SpdCompoundFilterTable exists that has a matching spdCompFiltName. II. Or, at least one other active row in this table has a matching spdCompFiltName. If neither condition is met, an attempt to set this row to something other than active MUST result in an inconsistentValue error.
.1.3.6.1.2.1.153.1.7,IPSEC-SPD-MIB::spdStaticFilters,,,,,,
.1.3.6.1.2.1.153.1.7.1,IPSEC-SPD-MIB::spdTrueFilter,Integer32,read-only,,current,,This scalar indicates a (automatic) true result for a filter. That is, this is a filter that is always true; it is useful for adding as a default filter for a default action or a set of actions.
.1.3.6.1.2.1.153.1.7.1.0,IPSEC-SPD-MIB::spdTrueFilterInstance,,,,,,
.1.3.6.1.2.1.153.1.8,IPSEC-SPD-MIB::spdIpOffsetFilterTable,,not-accessible,,current,,This table contains a list of filter definitions to be used within the spdRuleDefinitionTable or the spdSubfiltersTable. This type of filter is used to compare an administrator specified octet string to the octets at a particular location in a packet.
.1.3.6.1.2.1.153.1.8.1,IPSEC-SPD-MIB::spdIpOffsetFilterEntry,,not-accessible,spdIpOffFiltName,current,,A definition of a particular filter.
.1.3.6.1.2.1.153.1.8.1.1,IPSEC-SPD-MIB::spdIpOffFiltName,OCTET,not-accessible,,current,,The administrative name for this filter.
.1.3.6.1.2.1.153.1.8.1.2,IPSEC-SPD-MIB::spdIpOffFiltOffset,Unsigned32,read-create,,current,,This is the byte offset from the front of the entire IP packet where the value or arithmetic comparison is done. A value of '0' indicates the first byte of the packet header. If this value is greater than the length of the packet, the filter represented by this row should be considered to fail.
.1.3.6.1.2.1.153.1.8.1.3,IPSEC-SPD-MIB::spdIpOffFiltType,INTEGER,read-create,,current,equal(1):notEqual(2):arithmeticLess(3):arithmeticGreaterOrEqual(4):arithmeticGreater(5):arithmeticLessOrEqual(6),This defines the various tests that are used when evaluating a given filter. The various tests definable in this table are as follows: equal: - Tests if the OCTET STRING, 'spdIpOffFiltValue', matches a value in the packet starting at the given offset in the packet and comparing the entire OCTET STRING of 'spdIpOffFiltValue'. Any values compared this way are assumed to be unsigned integer values in network byte order of the same length as 'spdIpOffFiltValue'. notEqual: - Tests if the OCTET STRING, 'spdIpOffFiltValue', does not match a value in the packet starting at the given offset in the packet and comparing to the entire OCTET STRING of 'spdIpOffFiltValue'. Any values compared this way are assumed to be unsigned integer values in network byte order of the same length as 'spdIpOffFiltValue'. arithmeticLess: - Tests if the OCTET STRING, 'spdIpOffFiltValue', is arithmetically less than ('<') the value starting at the given offset within the packet. The value in the packet is assumed to be an unsigned integer in network byte order of the same length as 'spdIpOffFiltValue'. arithmeticGreaterOrEqual: - Tests if the OCTET STRING, 'spdIpOffFiltValue', is arithmetically greater than or equal to ('>=') the value starting at the given offset within the packet. The value in the packet is assumed to be an unsigned integer in network byte order of the same length as 'spdIpOffFiltValue'. arithmeticGreater: - Tests if the OCTET STRING, 'spdIpOffFiltValue', is arithmetically greater than ('>') the value starting at the given offset within the packet. The value in the packet is assumed to be an unsigned integer in network byte order of the same length as 'spdIpOffFiltValue'. arithmeticLessOrEqual: - Tests if the OCTET STRING, 'spdIpOffFiltValue', is arithmetically less than or equal to ('<=') the value starting at the given offset within the packet. The value in the packet is assumed to be an unsigned integer in network byte order of the same length as 'spdIpOffFiltValue'.
.1.3.6.1.2.1.153.1.8.1.4,IPSEC-SPD-MIB::spdIpOffFiltValue,OCTET,read-create,,current,,spdIpOffFiltValue is used for match comparisons of a packet at spdIpOffFiltOffset.
.1.3.6.1.2.1.153.1.8.1.5,IPSEC-SPD-MIB::spdIpOffFiltLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.8.1.6,IPSEC-SPD-MIB::spdIpOffFiltStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.8.1.7,IPSEC-SPD-MIB::spdIpOffFiltRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object MUST remain active if it is referenced by an active row in another table. An attempt to set it to anything other than active while it is referenced by an active row in another table MUST result in an inconsistentValue error.
.1.3.6.1.2.1.153.1.9,IPSEC-SPD-MIB::spdTimeFilterTable,,not-accessible,,current,,Defines a table of filters that can be used to effectively enable or disable policies based on a valid time range.
.1.3.6.1.2.1.153.1.9.1,IPSEC-SPD-MIB::spdTimeFilterEntry,,not-accessible,spdTimeFiltName,current,,A row describing a given time frame for which a policy is filtered on to activate or deactivate the rule. If all the column objects in a row are true for the current time, the row evaluates as 'true'. More explicitly, the time matching column objects in a row MUST be logically ANDed together to form the boolean true/false for the row.
.1.3.6.1.2.1.153.1.9.1.1,IPSEC-SPD-MIB::spdTimeFiltName,OCTET,not-accessible,,current,,An administratively assigned name for this filter.
.1.3.6.1.2.1.153.1.9.1.2,IPSEC-SPD-MIB::spdTimeFiltPeriod,OCTET,read-create,,current,,The valid time period for this filter. This column is considered 'true' if the current time is within the range of this object.
.1.3.6.1.2.1.153.1.9.1.3,IPSEC-SPD-MIB::spdTimeFiltMonthOfYearMask,BITS,read-create,,current,january(0):february(1):march(2):april(3):may(4):june(5):july(6):august(7):september(8):october(9):november(10):december(11),A bit mask that indicates acceptable months of the year. This column evaluates to 'true' if the current month's bit is set.
.1.3.6.1.2.1.153.1.9.1.4,IPSEC-SPD-MIB::spdTimeFiltDayOfMonthMask,OCTET,read-create,,current,,Defines which days of the month the current time is valid for. It is a sequence of 64 BITS, where each BIT represents a corresponding day of the month in forward or reverse order. Starting from the left-most bit, the first 31 bits identify the day of the month, counting from the beginning of the month. The following 31 bits (bits 32-62) indicate the day of the month, counting from the end of the month. For months with fewer than 31 days, the bits that correspond to the non-existent days of that month are ignored (e.g., for non-leap year Februarys, bits 29-31 and 60-62 are ignored). This column evaluates to 'true' if the current day of the month's bit is set. For example, a value of 0X'80 00 00 01 00 00 00 00' indicates that this column evaluates to true on the first and last days of the month. The last two bits in the string MUST be zero.
.1.3.6.1.2.1.153.1.9.1.5,IPSEC-SPD-MIB::spdTimeFiltDayOfWeekMask,BITS,read-create,,current,sunday(0):monday(1):tuesday(2):wednesday(3):thursday(4):friday(5):saturday(6),A bit mask that defines which days of the week that the current time is valid for. This column evaluates to 'true' if the current day of the week's bit is set.
.1.3.6.1.2.1.153.1.9.1.6,IPSEC-SPD-MIB::spdTimeFiltTimeOfDayMask,OCTET,read-create,,current,,Indicates the start and end time of the day for which this filter evaluates to true. The date portions of the spdTimePeriod TC are ignored for purposes of evaluating this mask, and only the time-specific portions are used. This column evaluates to 'true' if the current time of day is within the range of the start and end times of the day indicated by this object.
.1.3.6.1.2.1.153.1.9.1.7,IPSEC-SPD-MIB::spdTimeFiltLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.9.1.8,IPSEC-SPD-MIB::spdTimeFiltStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.9.1.9,IPSEC-SPD-MIB::spdTimeFiltRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object MUST remain active if it is referenced by an active row in another table. An attempt to set it to anything other than active while it is referenced by an active row in another table MUST result in an inconsistentValue error.
.1.3.6.1.2.1.153.1.10,IPSEC-SPD-MIB::spdIpsoHeaderFilterTable,,not-accessible,,current,,This table contains a list of IPSO header filter definitions to be used within the spdRuleDefinitionTable or the spdSubfiltersTable. IPSO headers and their values are described in RFC 1108.
.1.3.6.1.2.1.153.1.10.1,IPSEC-SPD-MIB::spdIpsoHeaderFilterEntry,,not-accessible,spdIpsoHeadFiltName,current,,A definition of a particular filter.
.1.3.6.1.2.1.153.1.10.1.1,IPSEC-SPD-MIB::spdIpsoHeadFiltName,OCTET,not-accessible,,current,,The administrative name for this filter.
.1.3.6.1.2.1.153.1.10.1.2,IPSEC-SPD-MIB::spdIpsoHeadFiltType,BITS,read-create,,current,classificationLevel(0):protectionAuthority(1),This object indicates which of the IPSO header field a packet is filtered on for this row. If this object is set to classification(0), the spdIpsoHeadFiltClassification object indicates how the packet is filtered. If this object is set to protectionAuthority(1), the spdIpsoHeadFiltProtectionAuth object indicates how the packet is filtered.
.1.3.6.1.2.1.153.1.10.1.3,IPSEC-SPD-MIB::spdIpsoHeadFiltClassification,INTEGER,read-create,,current,topSecret(61):secret(90):confidential(150):unclassified(171),This object indicates the IPSO classification header field value that the packet MUST have for this row to evaluate to 'true'. The values of these enumerations are defined by RFC 1108.
.1.3.6.1.2.1.153.1.10.1.4,IPSEC-SPD-MIB::spdIpsoHeadFiltProtectionAuth,INTEGER,read-create,,current,genser(0):siopesi(1):sci(2):nsa(3):doe(4),This object indicates the IPSO protection authority header field value that the packet MUST have for this row to evaluate to 'true'. The values of these enumerations are defined by RFC 1108. Hence the reason the SMIv2 convention of not using 0 in enumerated lists is violated here.
.1.3.6.1.2.1.153.1.10.1.5,IPSEC-SPD-MIB::spdIpsoHeadFiltLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.10.1.6,IPSEC-SPD-MIB::spdIpsoHeadFiltStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.10.1.7,IPSEC-SPD-MIB::spdIpsoHeadFiltRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. However, this object MUST NOT be set to active if the requirements of the spdIpsoHeadFiltType object are not met. Specifically, if the spdIpsoHeadFiltType bit for classification(0) is set, the spdIpsoHeadFiltClassification column MUST have a valid value for the row status to be set to active. If the spdIpsoHeadFiltType bit for protectionAuthority(1) is set, the spdIpsoHeadFiltProtectionAuth column MUST have a valid value for the row status to be set to active. If active, this object MUST remain active if it is referenced by an active row in another table. An attempt to set it to anything other than active while it is referenced by an active row in another table MUST result in an inconsistentValue error.
.1.3.6.1.2.1.153.1.11,IPSEC-SPD-MIB::spdCompoundActionTable,,not-accessible,,current,,Table used to allow multiple actions to be associated with a rule. It uses the spdSubactionsTable to do this. The rows from spdSubactionsTable that are partially indexed by spdCompActName form the set of compound actions to be performed. The spdCompActExecutionStrategy column in this table indicates how those actions are processed.
.1.3.6.1.2.1.153.1.11.1,IPSEC-SPD-MIB::spdCompoundActionEntry,,not-accessible,spdCompActName,current,,A row in the spdCompoundActionTable.
.1.3.6.1.2.1.153.1.11.1.1,IPSEC-SPD-MIB::spdCompActName,OCTET,not-accessible,,current,,This is an administratively assigned name of this compound action.
.1.3.6.1.2.1.153.1.11.1.2,IPSEC-SPD-MIB::spdCompActExecutionStrategy,INTEGER,read-create,,current,doAll(1):doUntilSuccess(2):doUntilFailure(3),This object indicates how the sub-actions are executed based on the success of the actions as they finish executing. doAll - run each sub-action regardless of the exit status of the previous action. This parent action is always considered to have acted successfully. doUntilSuccess - run each sub-action until one succeeds, at which point stop processing the sub-actions within this parent compound action. If one of the sub-actions did execute successfully, this parent action is also considered to have executed successfully. doUntilFailure - run each sub-action until one fails, at which point stop processing the sub-actions within this compound action. If any sub-action fails, the result of this parent action is considered to have failed.
.1.3.6.1.2.1.153.1.11.1.3,IPSEC-SPD-MIB::spdCompActLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.11.1.4,IPSEC-SPD-MIB::spdCompActStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.11.1.5,IPSEC-SPD-MIB::spdCompActRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. Once a row in the spdCompoundActionTable has been made active, this object MUST NOT be set to destroy without first destroying all the contained rows listed in the spdSubactionsTable.
.1.3.6.1.2.1.153.1.12,IPSEC-SPD-MIB::spdSubactionsTable,,not-accessible,,current,,This table contains a list of the sub-actions within a given compound action. Compound actions executing these actions MUST execute them in series based on the spdSubActPriority value, with the lowest value executing first.
.1.3.6.1.2.1.153.1.12.1,IPSEC-SPD-MIB::spdSubactionsEntry,,not-accessible,spdCompActName:spdSubActPriority,current,,A row containing a reference to a given compound-action sub-action.
.1.3.6.1.2.1.153.1.12.1.1,IPSEC-SPD-MIB::spdSubActPriority,Integer32,not-accessible,,current,,The priority of a given sub-action within a compound action. The order in which sub-actions MUST be executed are based on the value from this column, with the lowest numeric value executing first (i.e., priority 0 before priority 1, 1 before 2, etc.).
.1.3.6.1.2.1.153.1.12.1.2,IPSEC-SPD-MIB::spdSubActSubActionName,OBJECT,read-create,,current,,This column points to the action to be taken. It MAY, but is not limited to, point to a row in one of the following tables: spdCompoundActionTable - Allowing recursion ipsaSaPreconfiguredActionTable ipiaIkeActionTable ipiaIpsecActionTable It MAY also point to one of the scalar objects beneath spdStaticActions. If this object is set to a pointer to a row in an unsupported (or unknown) table, an inconsistentValue error MUST be returned. If this object is set to point to a non-existent row in an otherwise supported table, an inconsistentName error MUST be returned. If, during packet processing, this column has a value that references a non-existent or non-supported object, the packet MUST be dropped.
.1.3.6.1.2.1.153.1.12.1.3,IPSEC-SPD-MIB::spdSubActLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime when this row was last modified or created either through SNMP SETs or by some other external means. If this row has not been modified since the last re-initialization of the network management subsystem, this object SHOULD have a zero value.
.1.3.6.1.2.1.153.1.12.1.4,IPSEC-SPD-MIB::spdSubActStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process MAY have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.6.1.2.1.153.1.12.1.5,IPSEC-SPD-MIB::spdSubActRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the conceptual status of this row. The value of this object has no effect on whether other objects in this conceptual row can be modified. If active, this object MUST remain active unless one of the following two conditions are met. An attempt to set it to anything other than active while the following conditions are not met MUST result in an inconsistentValue error. The two conditions are: I. No active row in the spdCompoundActionTable exists which has a matching spdCompActName. II. Or, at least one other active row in this table has a matching spdCompActName.
.1.3.6.1.2.1.153.1.13,IPSEC-SPD-MIB::spdStaticActions,,,,,,
.1.3.6.1.2.1.153.1.13.1,IPSEC-SPD-MIB::spdDropAction,Integer32,read-only,,current,,This scalar indicates that a packet MUST be dropped and SHOULD NOT have action/packet logging.
.1.3.6.1.2.1.153.1.13.2,IPSEC-SPD-MIB::spdDropActionLog,Integer32,read-only,,current,,This scalar indicates that a packet MUST be dropped and SHOULD have action/packet logging.
.1.3.6.1.2.1.153.1.13.3,IPSEC-SPD-MIB::spdAcceptAction,Integer32,read-only,,current,,This Scalar indicates that a packet MUST be accepted (pass-through) and SHOULD NOT have action/packet logging.
.1.3.6.1.2.1.153.1.13.4,IPSEC-SPD-MIB::spdAcceptActionLog,Integer32,read-only,,current,,This scalar indicates that a packet MUST be accepted (pass-through) and SHOULD have action/packet logging.
.1.3.6.1.2.1.153.2,IPSEC-SPD-MIB::spdNotificationObjects,,,,,,
.1.3.6.1.2.1.153.2.0,IPSEC-SPD-MIB::spdNotifications,,,,,,
.1.3.6.1.2.1.153.2.0.1,IPSEC-SPD-MIB::spdActionNotification,,,,,,Notification that an action was executed by a rule. Only actions with logging enabled will result in this notification getting sent. The object includes the spdActionExecuted object, which will indicate which action was executed within the scope of the rule. Additionally, the spdIPSourceType, spdIPSourceAddress, spdIPDestinationType, and spdIPDestinationAddress objects are included to indicate the packet source and destination of the packet that triggered the action. Finally, the spdIPEndpointAddType, spdIPEndpointAddress, and spdPacketDirection objects indicate which interface the executed action was associated with, and if the packet was ingress or egress through the endpoint. A spdActionNotification SHOULD be limited to a maximum of one notification sent per minute for any action notifications that do not have any other configuration controlling their send rate. Note that compound actions with multiple executed sub-actions may result in multiple notifications being sent from a single rule execution.
.1.3.6.1.2.1.153.2.0.2,IPSEC-SPD-MIB::spdPacketNotification,,,,,,Notification that a packet passed through a Security Association (SA). Only SAs created by actions with packet logging enabled will result in this notification getting sent. The objects sent MUST include the spdActionExecuted, which will indicate which action was executed within the scope of the rule. Additionally, the spdIPSourceType, spdIPSourceAddress, spdIPDestinationType, and spdIPDestinationAddress objects MUST be included to indicate the packet source and destination of the packet that triggered the action. The spdIPEndpointAddType, spdIPEndpointAddress, and spdPacketDirection objects are included to indicate which endpoint the packet was associated with. Finally, spdPacketPart is included to enable sending a variable sized part of the front of the packet with the size dependent on the value of the object of TC syntax 'SpdIPPacketLogging', which indicated that logging should be done. A spdPacketNotification SHOULD be limited to a maximum of one notification sent per minute for any action notifications that do not have any other configuration controlling their send rate. An action notification SHOULD be limited to a maximum of one notification sent per minute for any action notifications that do not have any other configuration controlling their send rate.
.1.3.6.1.2.1.153.2.1,IPSEC-SPD-MIB::spdNotificationVariables,,,,,,
.1.3.6.1.2.1.153.2.1.1,IPSEC-SPD-MIB::spdActionExecuted,OBJECT,accessible-for-notify,,current,,Points to the action instance that was executed that resulted in the notification being sent.
.1.3.6.1.2.1.153.2.1.2,IPSEC-SPD-MIB::spdIPEndpointAddType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Contains the address type for the interface that the notification triggering packet is passing through.
.1.3.6.1.2.1.153.2.1.3,IPSEC-SPD-MIB::spdIPEndpointAddress,OCTET,accessible-for-notify,,current,,Contains the interface address for the interface that the notification triggering packet is passing through. The format of this object is specified by the spdIPEndpointAddType object.
.1.3.6.1.2.1.153.2.1.4,IPSEC-SPD-MIB::spdIPSourceType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Contains the source address type of the packet that triggered the notification.
.1.3.6.1.2.1.153.2.1.5,IPSEC-SPD-MIB::spdIPSourceAddress,OCTET,accessible-for-notify,,current,,Contains the source address of the packet that triggered the notification. The format of this object is specified by the spdIPSourceType object.
.1.3.6.1.2.1.153.2.1.6,IPSEC-SPD-MIB::spdIPDestinationType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Contains the destination address type of the packet that triggered the notification.
.1.3.6.1.2.1.153.2.1.7,IPSEC-SPD-MIB::spdIPDestinationAddress,OCTET,accessible-for-notify,,current,,Contains the destination address of the packet that triggered the notification. The format of this object is specified by the spdIPDestinationType object.
.1.3.6.1.2.1.153.2.1.8,IPSEC-SPD-MIB::spdPacketDirection,INTEGER,accessible-for-notify,,current,inbound(1):outbound(2),Indicates if the packet that triggered the action in questions was ingress (inbound) or egress (outbound).
.1.3.6.1.2.1.153.2.1.9,IPSEC-SPD-MIB::spdPacketPart,OCTET,accessible-for-notify,,current,,spdPacketPart is the front part of the full IP packet that triggered this notification. The initial size limit is determined by the smaller of the size, indicated by: I. The value of the object with the TC syntax 'SpdIPPacketLogging' that indicated the packet SHOULD be logged and II. The size of the triggering packet. The final limit is determined by the SNMP packet size when sending the notification. The maximum size that can be included will be the smaller of the initial size, given the above, and the length that will fit in a single SNMP notification packet after the rest of the notification's objects and any other necessary packet data (headers encoding, etc.) have been included in the packet.
.1.3.6.1.2.1.153.3,IPSEC-SPD-MIB::spdConformanceObjects,,,,,,
.1.3.6.1.2.1.153.3.1,IPSEC-SPD-MIB::spdCompliances,,,,,,
.1.3.6.1.2.1.153.3.1.1,IPSEC-SPD-MIB::spdRuleFilterFullCompliance,,,,,,The compliance statement for SNMP entities that include an IPsec MIB implementation with Endpoint, Rules, and filters support. When this MIB is implemented with support for read-create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB.
.1.3.6.1.2.1.153.3.1.2,IPSEC-SPD-MIB::spdLoggingCompliance,,,,,,The compliance statement for SNMP entities that support sending notifications when actions are invoked.
.1.3.6.1.2.1.153.3.1.3,IPSEC-SPD-MIB::spdRuleFilterReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that include an IPsec MIB implementation with Endpoint, Rules, and filters support. If this MIB is implemented without support for read-create (i.e., in read-only), it is not in full compliance, but it can claim read-only compliance. Such a device can then be monitored, but cannot be configured with this MIB.
.1.3.6.1.2.1.153.3.2,IPSEC-SPD-MIB::spdGroups,,,,,,
.1.3.6.1.2.1.153.3.2.1,IPSEC-SPD-MIB::spdEndpointGroup,,,,,,This group is made up of objects from the IPsec Policy Endpoint Table.
.1.3.6.1.2.1.153.3.2.2,IPSEC-SPD-MIB::spdGroupContentsGroup,,,,,,This group is made up of objects from the IPsec Policy Group Contents Table.
.1.3.6.1.2.1.153.3.2.3,IPSEC-SPD-MIB::spdIpsecSystemPolicyNameGroup,,,,,,This group is made up of objects represent the System Policy Group Names.
.1.3.6.1.2.1.153.3.2.4,IPSEC-SPD-MIB::spdRuleDefinitionGroup,,,,,,This group is made up of objects from the IPsec Policy Rule Definition Table.
.1.3.6.1.2.1.153.3.2.5,IPSEC-SPD-MIB::spdCompoundFilterGroup,,,,,,This group is made up of objects from the IPsec Policy Compound Filter Table and Sub-Filter Table Group.
.1.3.6.1.2.1.153.3.2.6,IPSEC-SPD-MIB::spdStaticFilterGroup,,,,,,The static filter group. Currently this is just a true filter.
.1.3.6.1.2.1.153.3.2.7,IPSEC-SPD-MIB::spdIPOffsetFilterGroup,,,,,,This group is made up of objects from the IPsec Policy IP Offset Filter Table.
.1.3.6.1.2.1.153.3.2.8,IPSEC-SPD-MIB::spdTimeFilterGroup,,,,,,This group is made up of objects from the IPsec Policy Time Filter Table.
.1.3.6.1.2.1.153.3.2.9,IPSEC-SPD-MIB::spdIpsoHeaderFilterGroup,,,,,,This group is made up of objects from the IPsec Policy IPSO Header Filter Table.
.1.3.6.1.2.1.153.3.2.10,IPSEC-SPD-MIB::spdStaticActionGroup,,,,,,This group is made up of objects from the IPsec Policy Static Actions.
.1.3.6.1.2.1.153.3.2.11,IPSEC-SPD-MIB::spdCompoundActionGroup,,,,,,The IPsec Policy Compound Action Table and Actions In Compound Action Table Group.
.1.3.6.1.2.1.153.3.2.12,IPSEC-SPD-MIB::spdActionLoggingObjectGroup,,,,,,This group is made up of all the Notification objects for this MIB.
.1.3.6.1.2.1.153.3.2.13,IPSEC-SPD-MIB::spdActionNotificationGroup,,,,,,This group is made up of all the Notifications for this MIB.
.1.3.6.1.2.1.153.4,IPSEC-SPD-MIB::spdActions,,,,,,
.1.3.6.1.2.1.154,IANA-MAU-MIB::ianaMauMIB,,,,,,This MIB module defines dot3MauType OBJECT-IDENTITIES and IANAifMauListBits, IANAifMauMediaAvailable, IANAifMauAutoNegCapBits, and IANAifJackType TEXTUAL-CONVENTIONs, specifying enumerated values of the ifMauTypeListBits, ifMauMediaAvailable / rpMauMediaAvailable, ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits / ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects respectively, defined in the MAU-MIB. It is intended that each new MAU type, Media Availability state, Auto Negotiation capability and/or Jack type defined by the IEEE 802.3 working group and approved for publication in a revision of IEEE Std 802.3 will be added to this MIB module, provided that it is suitable for being managed by the base objects in the MAU-MIB. An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for such additions. The following reference is used throughout this MIB module: [IEEE802.3] refers to: IEEE Std 802.3, 2005 Edition: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications'. This reference should be updated as appropriate when new MAU types, Media Availability states, Auto Negotiation capabilities, and/or Jack types are added to this MIB module. Copyright (C) The IETF Trust (2007). The initial version of this MIB module was published in RFC 4836; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html
.1.3.6.1.2.1.155,DOT3-EPON-MIB::dot3EponMIB,,,,,,The objects in this MIB module are used to manage the Ethernet in the First Mile (EFM) Ethernet Passive Optical Network (EPON) Interfaces as defined in IEEE P802.3ah clauses 60, 64, and 65. The following reference is used throughout this MIB module: [802.3ah] refers to: Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks. IEEE Std 802.3ah-2004, October 2004. Of particular interest are clause 64 (Multi-Point Control Protocol - MPCP), clause 65 (Point-to-Multipoint Reconciliation Sublayer - P2MP RS), clause 60 (Ethernet Passive Optical Network Physical Medium Dependent - EPON PMDs), clause 30, 'Management', and clause 45, 'Management Data Input/Output (MDIO) Interface'. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of 4837; see the RFC itself for full legal notices. Key abbreviations: BER - Bit Error Rate BW - bandwidth CRC - Cyclic Redundancy Check EFM - Ethernet First Mile EPON - Ethernet Passive Optical Network FEC - Forward Error Correction LLID - Logical Link Identifier MAC - Media Access Control Mbps - Megabit per second MDIO - Management Data Input/Output MPCP - Multi-Point Control Protocol OLT - Optical Line Terminal (Server unit of the EPON) OMP - Optical Multi-Point ONU - Optical Network Unit (Client unit of the EPON) P2MP - Point-to-Multipoint PHY - Physical Layer PMD - Physical Medium Dependent PON - Passive Optical Network RTT - Round Trip Time SLD - Start of LLID Delimiter TQ - Time Quanta 
.1.3.6.1.2.1.155.1,DOT3-EPON-MIB::dot3EponObjects,,,,,,
.1.3.6.1.2.1.155.1.1,DOT3-EPON-MIB::dot3EponMpcpObjects,,,,,,
.1.3.6.1.2.1.155.1.1.1,DOT3-EPON-MIB::dot3MpcpControlTable,,not-accessible,,current,,A Table of dot3 Multi-Point Control Protocol (MPCP) MIB objects. The entries in the table are control and status objects of the MPCP. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff).
.1.3.6.1.2.1.155.1.1.1.1,DOT3-EPON-MIB::dot3MpcpControlEntry,,not-accessible,ifIndex,current,,An entry in the dot3 MPCP Control table. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual links is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.1.1.1.1,DOT3-EPON-MIB::dot3MpcpOperStatus,INTEGER,read-only,,current,true(1):false(2),This object reflects the operational state of the Multi-Point MAC Control sublayer as defined in [802.3ah], clause 64. When the value is true(1), the interface will act as if the Multi-Point Control Protocol is enabled. When the value is false(2), the interface will act as if the Multi-Point Control Protocol is disabled. The operational state can be changed using the dot3MpcpAdminState object. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU.
.1.3.6.1.2.1.155.1.1.1.1.2,DOT3-EPON-MIB::dot3MpcpAdminState,INTEGER,read-write,,current,true(1):false(2),This object is used to define the admin state of the Multi-Point MAC Control sublayer, as defined in [802.3ah], clause 64, and to reflect its state. When selecting the value as true(1), the Multi-Point Control Protocol of the interface is enabled. When selecting the value as false(2), the Multi-Point Control Protocol of the interface is disabled. This object reflects the administrative state of the Multi-Point Control Protocol of the interface. The write operation is not restricted in this document and can be done at any time. Changing dot3MpcpAdminState state can lead to disabling the Multi-Point Control Protocol on the respective interface, leading to the interruption of service for the users connected to the respective EPON interface. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU.
.1.3.6.1.2.1.155.1.1.1.1.3,DOT3-EPON-MIB::dot3MpcpMode,INTEGER,read-only,,current,olt(1):onu(2),This object is used to identify the operational state of the Multi-Point MAC Control sublayer as defined in [802.3ah], clause 64. Reading olt(1) for an OLT (server) mode and onu(2) for an ONU (client) mode. This object is used to identify the operational mode for the MPCP tables. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU.
.1.3.6.1.2.1.155.1.1.1.1.4,DOT3-EPON-MIB::dot3MpcpSyncTime,Unsigned32,read-only,,current,,An object that reports the 'sync lock time' of the OLT receiver in increments of Time Quanta (TQ)-16ns as defined in [802.3ah], clauses 60, 64, and 65. The value returned shall be (sync lock time ns)/16. If this value exceeds (2^32-1), the value (2^32-1) shall be returned. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU.
.1.3.6.1.2.1.155.1.1.1.1.5,DOT3-EPON-MIB::dot3MpcpLinkID,Unsigned32,read-only,,current,,An object that identifies the Logical Link Identifier (LLID) associated with the MAC of the virtual link as specified in [802.3ah], clause 65.1.3.2.2. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. The ONU and the corresponding virtual MAC of the OLT, for the same virtual link, have the same value. Value is assigned when the ONU registers. Value is freed when the ONU deregisters.
.1.3.6.1.2.1.155.1.1.1.1.6,DOT3-EPON-MIB::dot3MpcpRemoteMACAddress,OCTET,read-only,,current,,An object that identifies the source_address parameter of the last MPCPDUs passed to the MAC Control. This value is updated on reception of a valid frame with 1) a destination Field equal to the reserved multicast address for MAC Control as specified in [802.3], Annex 31A; 2) the lengthOrType field value equal to the reserved Type for MAC Control as specified in [802.3], Annex 31A; 3) an MPCP subtype value equal to the subtype reserved for MPCP as specified in [802.3ah], Annex 31A. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. The value reflects the MAC address of the remote entity and therefore the OLT holds a value for each LLID, which is the MAC address of the ONU; the ONU has a single value that is the OLT MAC address.
.1.3.6.1.2.1.155.1.1.1.1.7,DOT3-EPON-MIB::dot3MpcpRegistrationState,INTEGER,read-only,,current,unregistered(1):registering(2):registered(3),An object that identifies the registration state of the Multi-Point MAC Control sublayer as defined in [802.3ah], clause 64. When this object has the enumeration unregistered(1), the interface is unregistered and may be used for registering a link partner. When this object has the enumeration registering(2), the interface is in the process of registering a link-partner. When this object has the enumeration registered(3), the interface has an established link-partner. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.1.1.1.8,DOT3-EPON-MIB::dot3MpcpTransmitElapsed,Unsigned32,read-only,,current,,An object that reports the interval from the last MPCP frame transmission in increments of Time Quanta (TQ)-16ns. The value returned shall be (interval from last MPCP frame transmission in ns)/16. If this value exceeds (2^32-1), the value (2^32-1) shall be returned. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.1.1.1.9,DOT3-EPON-MIB::dot3MpcpReceiveElapsed,Unsigned32,read-only,,current,,An object that reports the interval from last MPCP frame reception in increments of Time Quanta (TQ)-16ns. The value returned shall be (interval from last MPCP frame reception in ns)/16. If this value exceeds (2^32-1), the value (2^32-1) shall be returned. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.1.1.1.10,DOT3-EPON-MIB::dot3MpcpRoundTripTime,Unsigned32,read-only,,current,,An object that reports the MPCP round trip time in increments of Time Quanta (TQ)-16ns. The value returned shall be (round trip time in ns)/16. If this value exceeds (2^16-1), the value (2^16-1) shall be returned. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.1.1.1.11,DOT3-EPON-MIB::dot3MpcpMaximumPendingGrants,Unsigned32,read-only,,current,,An object that reports the maximum number of grants that an ONU can store for handling. The maximum number of grants that an ONU can store for handling has a range of 0 to 255. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero.
.1.3.6.1.2.1.155.1.1.2,DOT3-EPON-MIB::dot3MpcpStatTable,,not-accessible,,current,,This table defines the list of statistics counters of an interface implementing the [802.3ah], clause 64 MPCP. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff).
.1.3.6.1.2.1.155.1.1.2.1,DOT3-EPON-MIB::dot3MpcpStatEntry,,not-accessible,ifIndex,current,,An entry in the table of statistics counters of the [802.3ah], clause 64, MPCP interface. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual link is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.1.2.1.1,DOT3-EPON-MIB::dot3MpcpMACCtrlFramesTransmitted,Counter64,read-only,,current,,A count of MPCP frames passed to the MAC sublayer for transmission. This counter is incremented when a MA_CONTROL.request service primitive is generated within the MAC control sublayer with an opcode indicating an MPCP frame. This object is applicable for an OLT and an ONU. At the OLT it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.2,DOT3-EPON-MIB::dot3MpcpMACCtrlFramesReceived,Counter64,read-only,,current,,A count of MPCP frames passed by the MAC sublayer to the MAC Control sublayer. This counter is incremented when a ReceiveFrame function call returns a valid frame with 1) a lengthOrType field value equal to the reserved Type for 802.3_MAC_Control as specified in clause 31.4.1.3, and 2) an opcode indicating an MPCP frame. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.3,DOT3-EPON-MIB::dot3MpcpDiscoveryWindowsSent,Counter32,read-only,,current,,A count of discovery windows generated. The counter is incremented by one for each generated discovery window. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.4,DOT3-EPON-MIB::dot3MpcpDiscoveryTimeout,Counter32,read-only,,current,,A count of the number of times a discovery timeout occurs. Increment the counter by one for each discovery processing state-machine reset resulting from timeout waiting for message arrival. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.5,DOT3-EPON-MIB::dot3MpcpTxRegRequest,Counter64,read-only,,current,,A count of the number of times a REGISTER_REQ MPCP frame transmission occurs. Increment the counter by one for each REGISTER_REQ MPCP frame transmitted as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.6,DOT3-EPON-MIB::dot3MpcpRxRegRequest,Counter64,read-only,,current,,A count of the number of times a REGISTER_REQ MPCP frame reception occurs. Increment the counter by one for each REGISTER_REQ MPCP frame received as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.7,DOT3-EPON-MIB::dot3MpcpTxRegAck,Counter64,read-only,,current,,A count of the number of times a REGISTER_ACK MPCP frame transmission occurs. Increment the counter by one for each REGISTER_ACK MPCP frame transmitted as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.8,DOT3-EPON-MIB::dot3MpcpRxRegAck,Counter64,read-only,,current,,A count of the number of times a REGISTER_ACK MPCP frame reception occurs. Increment the counter by one for each REGISTER_ACK MPCP frame received as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.9,DOT3-EPON-MIB::dot3MpcpTxReport,Counter64,read-only,,current,,A count of the number of times a REPORT MPCP frame transmission occurs. Increment the counter by one for each REPORT MPCP frame transmitted as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.10,DOT3-EPON-MIB::dot3MpcpRxReport,Counter64,read-only,,current,,A count of the number of times a REPORT MPCP frame reception occurs. Increment the counter by one for each REPORT MPCP frame received as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.11,DOT3-EPON-MIB::dot3MpcpTxGate,Counter64,read-only,,current,,A count of the number of times a GATE MPCP frame transmission occurs. Increment the counter by one for each GATE MPCP frame transmitted as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.12,DOT3-EPON-MIB::dot3MpcpRxGate,Counter64,read-only,,current,,A count of the number of times a GATE MPCP frame reception occurs. Increment the counter by one for each GATE MPCP frame received as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.13,DOT3-EPON-MIB::dot3MpcpTxRegister,Counter64,read-only,,current,,A count of the number of times a REGISTER MPCP frame transmission occurs. Increment the counter by one for each REGISTER MPCP frame transmitted as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.1.2.1.14,DOT3-EPON-MIB::dot3MpcpRxRegister,Counter64,read-only,,current,,A count of the number of times a REGISTER MPCP frame reception occurs. Increment the counter by one for each REGISTER MPCP frame received as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2,DOT3-EPON-MIB::dot3OmpEmulationObjects,,,,,,
.1.3.6.1.2.1.155.1.2.1,DOT3-EPON-MIB::dot3OmpEmulationTable,,not-accessible,,current,,A table of dot3 OmpEmulation MIB objects. The table contain objects for the management of the OMPEmulation sublayer. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff).
.1.3.6.1.2.1.155.1.2.1.1,DOT3-EPON-MIB::dot3OmpEmulationEntry,,not-accessible,ifIndex,current,,An entry in the dot3 OmpEmulation table. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual links is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.2.1.1.1,DOT3-EPON-MIB::dot3OmpEmulationType,INTEGER,read-only,,current,unknown(1):olt(2):onu(3),An object that indicates the mode of operation of the Reconciliation Sublayer for Point-to-Point Emulation (see [802.3ah], clause 65.1). unknown(1) value is assigned in initialization; true state or type is not yet known. olt(2) value is assigned when the sublayer is operating in OLT mode. onu(3) value is assigned when the sublayer is operating in ONU mode. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU.
.1.3.6.1.2.1.155.1.2.2,DOT3-EPON-MIB::dot3OmpEmulationStatTable,,not-accessible,,current,,This table defines the list of statistics counters of [802.3ah], clause 65, OMPEmulation sublayer. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff).
.1.3.6.1.2.1.155.1.2.2.1,DOT3-EPON-MIB::dot3OmpEmulationStatEntry,,not-accessible,ifIndex,current,,An entry in the table of statistics counters of [802.3ah], clause 65, OMPEmulation sublayer. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual links is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.2.2.1.1,DOT3-EPON-MIB::dot3OmpEmulationSLDErrors,Counter64,read-only,,current,,A count of frames received that do not contain a valid SLD field as defined in [802.3ah], clause 65.1.3.3.1. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.2,DOT3-EPON-MIB::dot3OmpEmulationCRC8Errors,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, but do not pass the CRC-8 check as defined in [802.3ah], clause 65.1.3.3.3. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.3,DOT3-EPON-MIB::dot3OmpEmulationBadLLID,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, and pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, but are discarded due to the LLID check as defined in [802.3ah], clause 65.1.3.3.2. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.4,DOT3-EPON-MIB::dot3OmpEmulationGoodLLID,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, and pass the CRC-8 check as defined in [802.3ah], clause 65.1.3.3.3. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.5,DOT3-EPON-MIB::dot3OmpEmulationOnuPonCastLLID,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, and meet the rules of acceptance for an ONU defined in [802.3ah], clause 65.1.3.3.2. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.6,DOT3-EPON-MIB::dot3OmpEmulationOltPonCastLLID,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, and meet the rules of acceptance for an OLT defined in [802.3ah], 65.1.3.3.2. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the ONU, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.7,DOT3-EPON-MIB::dot3OmpEmulationBroadcastBitNotOnuLlid,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, and contain the broadcast bit in the LLID and not the ONU's LLID (frame accepted) as defined in [802.3ah], clause 65. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.8,DOT3-EPON-MIB::dot3OmpEmulationOnuLLIDNotBroadcast,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, and contain the ONU's LLID as defined in [802.3ah], clause 65. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.9,DOT3-EPON-MIB::dot3OmpEmulationBroadcastBitPlusOnuLlid,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, and contain the broadcast bit in the LLID and match the ONU's LLID (frame reflected) as defined in [802.3ah], clause 65. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.2.2.1.10,DOT3-EPON-MIB::dot3OmpEmulationNotBroadcastBitNotOnuLlid,Counter64,read-only,,current,,A count of frames received that contain a valid SLD field, as defined in [802.3ah], clause 65.1.3.3.1, pass the CRC-8 check, as defined in [802.3ah], clause 65.1.3.3.3, and do not contain the ONU's LLID as defined in [802.3ah], clause 65. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.3,DOT3-EPON-MIB::dot3EponFecObjects,,,,,,
.1.3.6.1.2.1.155.1.3.1,DOT3-EPON-MIB::dot3EponFecTable,,not-accessible,,current,,A table of dot3 EPON FEC management objects. The entries in the table are control and status objects and statistic counters for the FEC layer. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff).
.1.3.6.1.2.1.155.1.3.1.1,DOT3-EPON-MIB::dot3EponFecEntry,,not-accessible,ifIndex,current,,An entry in the dot3 EPON FEC table. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual links is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.3.1.1.1,DOT3-EPON-MIB::dot3EponFecPCSCodingViolation,Counter64,read-only,,current,,For a 100 Mbps operation, it is a count of the number of times an invalid code-group is received, other than the /H/ code-group. For a 1000 Mbps operation, it is a count of the number of times an invalid codegroup is received, other than the /V/ code-group. /H/ denotes a special 4b5b codeword of [802.3] 100 Mbps PCS layer (clause 24), and /V/ denotes a special 8b10b codeword of the [802.3] 1000 Mbps PCS layer (clause 36). This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.3.1.1.2,DOT3-EPON-MIB::dot3EponFecAbility,INTEGER,read-only,,current,unknown(1):supported(2):unsupported(3),An object that indicates the support of operation of the optional FEC sublayer of the 1000BASE-PX PHY specified in [802.3ah], clause 65.2. unknown(1) value is assigned in the initialization, for non FEC support state or type not yet known. unsupported(3) value is assigned when the sublayer is not supported. supported(2) value is assigned when the sublayer is supported. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU. The FEC counters will have a zero value when the interface is not supporting FEC. The counters: dot3EponFecPCSCodingViolation - not affected by FEC ability. dot3EponFecCorrectedBlocks - has a zero value when dot3EponFecAbility is unknown(1) and unsupported(3). dot3EponFecUncorrectableBlocks - has a zero value when dot3EponFecAbility is unknown(1) and unsupported(3). dot3EponFecBufferHeadCodingViolation - has a zero value when dot3EponFecAbility is unknown(1) and unsupported(3).
.1.3.6.1.2.1.155.1.3.1.1.3,DOT3-EPON-MIB::dot3EponFecMode,INTEGER,read-write,,current,unknown(1):disabled(2):enabled(3),An object that defines the mode of operation of the optional FEC sublayer of the 1000BASE-PX PHY, specified in [802.3ah], clause 65.2, and reflects its state. A GET operation returns the current mode of operation of the PHY. A SET operation changes the mode of operation of the PHY to the indicated value. unknown(1) value is assigned in the initialization for non FEC support state or type not yet known. disabled(2) value is assigned when the FEC sublayer is operating in disabled mode. enabled(3) value is assigned when the FEC sublayer is operating in FEC mode. The write operation is not restricted in this document and can be done at any time. Changing dot3EponFecMode state can lead to disabling the Forward Error Correction on the respective interface, which can lead to a degradation of the optical link, and therefore may lead to an interruption of service for the users connected to the respective EPON interface. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. The counting of the FEC counters will stop when the FEC of the interface is disabled. The counters: dot3EponFecPCSCodingViolation - not affected by FEC mode. dot3EponFecCorrectedBlocks - stops counting when Rx_FEC is not enabled. (unknown(1) and disabled(2)). dot3EponFecUncorrectableBlocks - stops counting when Rx_FEC is not enabled (unknown(1) and disabled(2)). dot3EponFecBufferHeadCodingViolation - stops counting when Rx_FEC is not enabled (unknown(1) and disabled(2)). The object: dot3EponFecAbility - indicates the FEC ability and is not affected by the dot3EponFecMode object.
.1.3.6.1.2.1.155.1.3.1.1.4,DOT3-EPON-MIB::dot3EponFecCorrectedBlocks,Counter64,read-only,,current,,For 10PASS-TS, 2BASE-TL, and 1000BASE-PX PHYs, it is a count of corrected FEC blocks. This counter will not increment for other PHY Types. Increment the counter by one for each received block that is corrected by the FEC function in the PHY. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.3.1.1.5,DOT3-EPON-MIB::dot3EponFecUncorrectableBlocks,Counter64,read-only,,current,,For 10PASS-TS, 2BASE-TL, and 1000BASE-PX PHYs, it is a count of uncorrectable FEC blocks. This counter will not increment for other PHY Types. Increment the counter by one for each FEC block that is determined to be uncorrectable by the FEC function in the PHY. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.3.1.1.6,DOT3-EPON-MIB::dot3EponFecBufferHeadCodingViolation,Counter64,read-only,,current,,For a 1000 Mbps operation, it is a count of the number of invalid code-group received directly from the link. The value has a meaning only in 1000 Mbps mode and it is zero otherwise. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.4,DOT3-EPON-MIB::dot3ExtPkgObjects,,,,,,
.1.3.6.1.2.1.155.1.4.1,DOT3-EPON-MIB::dot3ExtPkgControlObjects,,,,,,
.1.3.6.1.2.1.155.1.4.1.1,DOT3-EPON-MIB::dot3ExtPkgControlTable,,not-accessible,,current,,A table of Extended package Control management objects. Entries in the table are control and status indication objects of an EPON interface, which are gathered in an extended package as an addition to the objects based on the [802.3ah], clause 30, attributes. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff).
.1.3.6.1.2.1.155.1.4.1.1.1,DOT3-EPON-MIB::dot3ExtPkgControlEntry,,not-accessible,ifIndex,current,,An entry in the Extended package Control table. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual links is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.4.1.1.1.1,DOT3-EPON-MIB::dot3ExtPkgObjectReset,INTEGER,read-write,,current,running(1):reset(2),This object is used to reset the EPON interface. The interface may be unavailable while the reset occurs and data may be lost. Setting this object to running(1) will cause the interface to enter into running mode. Setting this object to reset(2) will cause the interface to go into reset mode. When getting running(1), the interface is in running mode. When getting reset(2), the interface is in reset mode. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgObjectReset state can lead to a reset of the respective interface, leading to an interruption of service for the users connected to the respective EPON interface. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. A reset for a specific virtual interface resets only this virtual interface and not the physical interface. Thus, a virtual link that is malfunctioning can be reset without affecting the operation of other virtual interfaces. The reset can cause Discontinuities in the values of the counters of the interface, similar to re-initialization of the management system. Discontinuity should be indicated by the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.4.1.1.1.2,DOT3-EPON-MIB::dot3ExtPkgObjectPowerDown,INTEGER,read-write,,current,true(1):false(2),This object is used to power down the EPON interface. The interface may be unavailable while the power down occurs and data may be lost. Setting this object to true(1) will cause the interface to enter into power down mode. Setting this object to false(2) will cause the interface to go out of power down mode. When getting true(1), the interface is in power down mode. When getting false(2), the interface is not in power down mode. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgObjectPowerDown state can lead to a power down of the respective interface, leading to an interruption of service of the users connected to the respective EPON interface. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. A power down/up of a specific virtual interface affects only the virtual interface and not the physical interface. Hence a virtual link, which needs a certain handling, can be powered down and then powered up without disrupting the operation of other virtual interfaces. The object is relevant when the admin state of the interface is active as set by the dot3MpcpAdminState.
.1.3.6.1.2.1.155.1.4.1.1.1.3,DOT3-EPON-MIB::dot3ExtPkgObjectNumberOfLLIDs,Unsigned32,read-only,,current,,A read only object that indicates the number of registered LLIDs. The initialization value is 0. This object is applicable for an OLT with the same value for all virtual interfaces and for an ONU. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff). At the ONU the number of LLIDs for an interface is one.
.1.3.6.1.2.1.155.1.4.1.1.1.4,DOT3-EPON-MIB::dot3ExtPkgObjectFecEnabled,INTEGER,read-write,,current,noFecEnabled(1):fecTxEnabled(2):fecRxEnabled(3):fecTxRxEnabled(4),An object defining the FEC mode of operation of the interface, and indicating its state. The modes defined in this object are extensions to the FEC modes defined in the dot3EponFecMode object. When noFECEnabled(1), the interface does not enable FEC mode. When fecTxEnabled(2), the interface enables the FEC transmit mode. When fecRxEnabled(3), the interface enables the FEC receive mode. When fecTxRxEnabled(4), the interface enables the FEC transmit and receive mode. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. The FEC counters are referring to the receive path. The FEC counters will stop when the FEC receive mode of the interface is disabled, as defined by fecRxEnabled(3) and fecTxRxEnabled(4) values. The counters: dot3EponFecPCSCodingViolation - not affected by FEC mode. dot3EponFecCorrectedBlocks - stops counting when Rx_FEC is not enabled (noFecEnabled(1) and fecTxEnabled(2)). dot3EponFecUncorrectableBlocks - stops counting when Rx_FEC is not enabled (noFecEnabled(1) and fecTxEnabled(2)). dot3EponFecBufferHeadCodingViolation - stops counting when Rx_FEC is not enabled (noFecEnabled(1) and fecTxEnabled(2)). The objects: dot3EponFecAbility - indicates the FEC ability and is not affected by the FEC mode. dot3EponFecMode - indicates the FEC mode for combined RX and TX. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgObjectFecEnabled state can lead to disabling the Forward Error Correction on the respective interface, which can lead to a degradation of the optical link, and therefore may lead to an interruption of service for the users connected to the respective EPON interface.
.1.3.6.1.2.1.155.1.4.1.1.1.5,DOT3-EPON-MIB::dot3ExtPkgObjectReportMaximumNumQueues,Unsigned32,read-only,,current,,An object, that defines the maximal number of queues in the REPORT message as defined in [802.3ah], clause 64. For further information please see the description of the queue table. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.1.1.6,DOT3-EPON-MIB::dot3ExtPkgObjectRegisterAction,INTEGER,read-write,,current,none(1):register(2):deregister(3):reregister(4),An object configuring the registration state of an interface, and indicating its registration state. Write operation changes the registration state to its new value. Read operation returns the value of the state. The registration state is reflected in this object and in the dot3MpcpRegistrationState object. none(1) indicates an unknown state, register(2) indicates a registered LLID, deregister(3) indicates a deregistered LLID, reregister(4) indicates an LLID that is reregistering. The following list describes the operation of the interface, as specified in the [802.3ah], when a write operation is setting a value. none(1) - not doing any action. register(2) - registering an LLID that has been requested for registration (The LLID is in registering mode. dot3MpcpRegistrationState - registering(2) ). deregister(3) - deregisters an LLID that is registered (dot3MpcpRegistrationState - registered(3) ). reregister(4) - reregister an LLID that is registered (dot3MpcpRegistrationState - registered(3) ). The behavior of an ONU and OLT interfaces, at each one of the detailed operation at each state, is described in the registration state machine of figure 64-22, [802.3ah]. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgObjectRegisterAction state can lead to a change in the registration state of the respective interface leading to a deregistration and an interruption of service of the users connected to the respective EPON interface.
.1.3.6.1.2.1.155.1.4.1.2,DOT3-EPON-MIB::dot3ExtPkgQueueTable,,not-accessible,,current,,A table of the extended package objects for queue management. The [802.3ah] MPCP defines a report message of the occupancy of the transmit queues for the feedback BW request from the ONUs. These queues serve the uplink transmission of the ONU and data is gathered there until the ONU is granted for transmission. The management table of the queues is added here mainly to control the reporting and to gather some statistics of their operation. This table is not duplicating existing management objects of bridging queues, specified in [802.1d], since the existence of a dedicated transmit queuing mechanism is implied in the [802.3ah], and the ONU may be a device that is not a bridge with embedded bridging queues. The format of the REPORT message, as specified in [802.3], is presented below: +-----------------------------------+ | Destination Address | +-----------------------------------+ | Source Address | +-----------------------------------+ | Length/Type | +-----------------------------------+ | OpCode | +-----------------------------------+ | TimeStamp | +-----------------------------------+ | Number of queue Sets | +-----------------------------------+ /|\ | Report bitmap | | +-----------------------------------+ | | Queue 0 report | | +-----------------------------------+ | repeated for | Queue 1 report | | every +-----------------------------------+ | queue_set | Queue 2 report | | +-----------------------------------+ | | Queue 3 report | | +-----------------------------------+ | | Queue 4 report | | +-----------------------------------+ | | Queue 5 report | | +-----------------------------------+ | | Queue 6 report | | +-----------------------------------+ | | Queue 7 report | | +-----------------------------------+ \|/ | Pad/reserved | +-----------------------------------+ | FCS | +-----------------------------------+ The 'Queue report' field reports the occupancy of each uplink transmission queue. The number of queue sets defines the number of the reported sets, as would be explained in the description of the dot3ExtPkgQueueSetsTable table. For each set the report bitmap defines which queue is present in the report, meaning that although the MPCP REPORT message can report up to 8 queues in a REPORT message, the actual number is flexible. The Queue table has a variable size that is limited by the dot3ExtPkgObjectReportMaximumNumQueues object, as an ONU can have fewer queues to report. The entries in the table are control and status indication objects for managing the queues of an EPON interface that are gathered in an extended package as an addition to the objects that are based on the [802.3ah] attributes. Each object 
.1.3.6.1.2.1.155.1.4.1.2.1,DOT3-EPON-MIB::dot3ExtPkgQueueEntry,,not-accessible,ifIndex:dot3QueueIndex,current,,An entry in the Extended package Queue table. At the OLT, the rows exist for each ifIndex and dot3QueueIndex. At the ONU, rows exist for the single ifIndex for each dot3QueueIndex. Rows in the table are created when the ifIndex of the link is created. A set of rows per queue are added for each ifIndex, denoted by the dot3QueueIndex. A set of rows per queue in the table, for an ONU interface, are created at the system initialization. A set of rows per queue in the table, corresponding to the OLT ifIndex and a set of rows per queue corresponding to the broadcast virtual link, are created at the system initialization. A set of rows per queue in the table, corresponding to the ifIndex of a virtual link, are created when the virtual link is established (ONU registers), and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.4.1.2.1.1,DOT3-EPON-MIB::dot3QueueIndex,Unsigned32,not-accessible,,current,,An object that identifies an index for the queue table reflecting the queue index of the queues that are reported in the MPCP REPORT message as defined in [802.3ah], clause 64. The number of queues is between 0 and 7, and limited by dot3ExtPkgObjectReportMaximumNumQueues.
.1.3.6.1.2.1.155.1.4.1.2.1.2,DOT3-EPON-MIB::dot3ExtPkgObjectReportNumThreshold,Unsigned32,read-write,,current,,An object that defines the number of thresholds for each queue in the REPORT message as defined in [802.3ah], clause 64. Each queue_set reporting will provide information on the queue occupancy of frames below the matching Threshold. Read operation reflects the number of thresholds. Write operation sets the number of thresholds for each queue. The write operation is not restricted in this document and can be done at any time. Value cannot exceed the maximal value defined by the dot3ExtPkgObjectReportMaximumNumThreshold object. Changing dot3ExtPkgObjectReportNumThreshold can lead to a change in the reporting of the ONU interface and therefore to a change in the bandwidth allocation of the respective interface. This change may lead a degradation or an interruption of service of the users connected to the respective EPON interface. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface and for each queue. At the ONU, it has a distinct value for each queue.
.1.3.6.1.2.1.155.1.4.1.2.1.3,DOT3-EPON-MIB::dot3ExtPkgObjectReportMaximumNumThreshold,Unsigned32,read-only,,current,,An object, that defines the maximal number of thresholds for each queue in the REPORT message as defined in [802.3ah], clause 64. Each queue_set reporting will provide information on the queue occupancy of frames below the matching Threshold. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface and for each queue. At the ONU, it has a distinct value for each queue.
.1.3.6.1.2.1.155.1.4.1.2.1.4,DOT3-EPON-MIB::dot3ExtPkgStatTxFramesQueue,Counter64,read-only,,current,,A count of the number of times a frame transmission occurs from the corresponding 'Queue'. Increment the counter by one for each frame transmitted, which is an output of the 'Queue'. The 'Queue' marking matches the REPORT MPCP message Queue field as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface and for each queue. At the ONU, it has a distinct value for each queue. At the OLT the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.4.1.2.1.5,DOT3-EPON-MIB::dot3ExtPkgStatRxFramesQueue,Counter64,read-only,,current,,A count of the number of times a frame reception occurs from the corresponding 'Queue'. Increment the counter by one for each frame received, which is an input to the corresponding 'Queue'. The 'Queue' marking matches the REPORT MPCP message Queue field as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface and for each queue. At the ONU, it has a distinct value for each queue. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.4.1.2.1.6,DOT3-EPON-MIB::dot3ExtPkgStatDroppedFramesQueue,Counter64,read-only,,current,,A count of the number of times a frame drop occurs from the corresponding 'Queue'. Increment the counter by one for each frame dropped from the corresponding 'Queue'. The 'Queue' marking matches the REPORT MPCP message Queue field as defined in [802.3ah], clause 64. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface and for each queue. At the ONU, it has a distinct value for each queue. At the OLT, the value should be zero. Discontinuities of this counter can occur at re-initialization of the management system and at other times, as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
.1.3.6.1.2.1.155.1.4.1.3,DOT3-EPON-MIB::dot3ExtPkgQueueSetsTable,,not-accessible,,current,,A table of Extended package objects used for the management of the queue_sets. Entries are control and status indication objects of an EPON interface, which are gathered in an extended package as an addition to the objects based on the [802.3ah] attributes. The objects in this table are specific for the queue_sets, which are reported in the MPCP REPORT message as defined in [802.3ah], clause 64. The [802.3ah] MPCP defines a report message of the occupancy of the transmit queues for the feedback BW request from the ONUs. These queues serve the uplink transmission of the ONU and data is gathered there until the ONU is granted for transmission. The management table of the queues_sets is added here mainly to control the reporting and to gather some statistics of their operation. This table is not duplicating existing management objects of bridging queues, specified in [802.1d], since the existence of a dedicated transmit queuing mechanism is implied in the [802.3ah], and the ONU may be a device that is not a bridge with embedded bridging queues. The format of the REPORT message, as specified in [802.3], is presented below: +-----------------------------------+ | Destination Address | +-----------------------------------+ | Source Address | +-----------------------------------+ | Length/Type | +-----------------------------------+ | OpCode | +-----------------------------------+ | TimeStamp | +-----------------------------------+ | Number of queue Sets | +-----------------------------------+ /|\ | Report bitmap | | +-----------------------------------+ | | Queue 0 report | | +-----------------------------------+ | repeated for | Queue 1 report | | every +-----------------------------------+ | queue_set | Queue 2 report | | +-----------------------------------+ | | Queue 3 report | | +-----------------------------------+ | | Queue 4 report | | +-----------------------------------+ | | Queue 5 report | | +-----------------------------------+ | | Queue 6 report | | +-----------------------------------+ | | Queue 7 report | | +-----------------------------------+ \|/ | Pad/reserved | +-----------------------------------+ | FCS | +-----------------------------------+ As can be seen from the message format, the ONU interface reports of the status of up to 8 queues and it can report in a single MPCP REPORT message of a few sets of queues. The number of queue_sets defines the number of the reported sets, and it can reach a value of up to 8. It means that an ONU can hold a variable number of sets between 0 and 7. The dot3ExtPkgQueueSetsTable table has a variable queue_set size that is limited by the dot3ExtPkgObjectReportMaximumNumThresh
.1.3.6.1.2.1.155.1.4.1.3.1,DOT3-EPON-MIB::dot3ExtPkgQueueSetsEntry,,not-accessible,ifIndex:dot3QueueSetQueueIndex:dot3QueueSetIndex,current,,An entry in the Extended package queue_set table. At the OLT, the rows exist for each ifIndex, dot3QueueSetQueueIndex and dot3QueueSetIndex. At the ONU, rows exist for the single ifIndex, for each dot3QueueSetQueueIndex and dot3QueueSetIndex. Rows in the table are created when the ifIndex of the link is created. A set of rows per queue and per queue_set are added for each ifIndex, denoted by dot3QueueSetIndex and dot3QueueSetQueueIndex. A set of rows per queue and per queue_set in the table, for an ONU interface are created at system initialization. A set of rows per queue and per queue_Set in the table, corresponding to the OLT ifIndex and a set of rows per queue and per queue_set, corresponding to the broadcast virtual link, are created at system initialization. A set of rows per queue and per queue_set in the table, corresponding to the ifIndex of a virtual link are created when the virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.4.1.3.1.1,DOT3-EPON-MIB::dot3QueueSetQueueIndex,Unsigned32,not-accessible,,current,,An object that identifies the queue index for the dot3ExtPkgQueueSetsTable table. The queues are reported in the MPCP REPORT message as defined in [802.3ah], clause 64. The number of queues is between 0 and 7, and limited by dot3ExtPkgObjectReportMaximumNumQueues. Value corresponds to the dot3QueueIndex of the queue table.
.1.3.6.1.2.1.155.1.4.1.3.1.2,DOT3-EPON-MIB::dot3QueueSetIndex,Unsigned32,not-accessible,,current,,An object that identifies the queue_set index for the dot3ExtPkgQueueSetsTable table. The queues are reported in the MPCP REPORT message as defined in [802.3ah], clause 64. The number of queues_sets is between 0 and 7, and limited by dot3ExtPkgObjectReportMaximumNumThreshold.
.1.3.6.1.2.1.155.1.4.1.3.1.3,DOT3-EPON-MIB::dot3ExtPkgObjectReportThreshold,Unsigned32,read-write,,current,,An object that defines the value of a threshold report for each queue_set in the REPORT message as defined in [802.3ah], clause 64. The number of sets for each queue is dot3ExtPkgObjectReportNumThreshold. In the REPORT message, each queue_set reporting will provide information on the occupancy of the queues for frames below the matching Threshold. The value returned shall be in Time quanta (TQ), which is 16nsec or 2 octets increments. Read operation provides the threshold value. Write operation sets the value of the threshold. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgObjectReportThreshold can lead to a change in the reporting of the ONU interface and therefore to a change in the bandwidth allocation of the respective interface. This change may lead a degradation or an interruption of service for the users connected to the respective EPON interface. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface, for each queue and for each queue_set. At the ONU, it has a distinct value for each queue and for each queue_set.
.1.3.6.1.2.1.155.1.4.1.5,DOT3-EPON-MIB::dot3ExtPkgOptIfTable,,not-accessible,,current,,This table defines the control and status indication objects for the optical interface of the EPON interface. Each object has a row for every virtual link denoted by the corresponding ifIndex. The LLID field, as defined in the [802.3ah], is a 2-byte register (15-bit field and a broadcast bit) limiting the number of virtual links to 32768. Typically the number of expected virtual links in a PON is like the number of ONUs, which is 32-64, plus an additional entry for broadcast LLID (with a value of 0xffff). Although the optical interface is a physical interface, there is a row in the table for each virtual interface. The reason for having a separate row for each virtual link is that the OLT has a separate link for each one of the ONUs. For instance, ONUs could be in different distances with different link budgets and different receive powers, therefore having different power alarms. It is quite similar to a case of different physical interfaces.
.1.3.6.1.2.1.155.1.4.1.5.1,DOT3-EPON-MIB::dot3ExtPkgOptIfEntry,,not-accessible,ifIndex,current,,An entry in the optical interface table of the EPON interface. Rows exist for an OLT interface and an ONU interface. A row in the table is denoted by the ifIndex of the link and it is created when the ifIndex is created. The rows in the table for an ONU interface are created at system initialization. The row in the table corresponding to the OLT ifIndex and the row corresponding to the broadcast virtual link are created at system initialization. A row in the table corresponding to the ifIndex of a virtual links is created when a virtual link is established (ONU registers) and deleted when the virtual link is deleted (ONU deregisters).
.1.3.6.1.2.1.155.1.4.1.5.1.1,DOT3-EPON-MIB::dot3ExtPkgOptIfSuspectedFlag,INTEGER,read-only,,current,true(1):false(2),This object is a reliability indication. If true, the data in this entry may be unreliable. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.2,DOT3-EPON-MIB::dot3ExtPkgOptIfInputPower,Integer32,read-only,,current,,The optical power monitored at the input. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.3,DOT3-EPON-MIB::dot3ExtPkgOptIfLowInputPower,Integer32,read-only,,current,,The lowest optical power monitored at the input during the current 15-minute interval. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.4,DOT3-EPON-MIB::dot3ExtPkgOptIfHighInputPower,Integer32,read-only,,current,,The highest optical power monitored at the input during the current 15-minute interval. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.5,DOT3-EPON-MIB::dot3ExtPkgOptIfLowerInputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on input power. If dot3ExtPkgOptIfInputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent. Reading will present the threshold value. Writing will set the value of the threshold. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgOptIfLowerInputPowerThreshold can lead to a Threshold Crossing Alert (TCA) being sent for the respective interface. This alert may be leading to an interruption of service for the users connected to the respective EPON interface, depending on the system action on such an alert. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.6,DOT3-EPON-MIB::dot3ExtPkgOptIfUpperInputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on input power. If dot3ExtPkgOptIfInputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent. Reading will present the threshold value. Writing will set the value of the threshold. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgOptIfUpperInputPowerThreshold can lead to a Threshold Crossing Alert (TCA) being sent for the respective interface. This alert may be leading to an interruption of service for the users connected to the respective EPON interface, depending on the system action on such an alert. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.7,DOT3-EPON-MIB::dot3ExtPkgOptIfOutputPower,Integer32,read-only,,current,,The optical power monitored at the output. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.8,DOT3-EPON-MIB::dot3ExtPkgOptIfLowOutputPower,Integer32,read-only,,current,,The lowest optical power monitored at the output during the current 15-minute interval. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.9,DOT3-EPON-MIB::dot3ExtPkgOptIfHighOutputPower,Integer32,read-only,,current,,The highest optical power monitored at the output during the current 15-minute interval. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.10,DOT3-EPON-MIB::dot3ExtPkgOptIfLowerOutputPowerThreshold,Integer32,read-write,,current,,The lower limit threshold on output power. If dot3ExtPkgOptIfOutputPower drops to this value or below, a Threshold Crossing Alert (TCA) should be sent. Reading will present the threshold value. Writing will set the value of the threshold. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgOptIfLowerOutputPowerThreshold can lead to a Threshold Crossing Alert (TCA) being sent for the respective interface. This alert may be leading to an interruption of service for the users connected to the respective EPON interface, depending on the system action on such an alert. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.11,DOT3-EPON-MIB::dot3ExtPkgOptIfUpperOutputPowerThreshold,Integer32,read-write,,current,,The upper limit threshold on output power. If dot3ExtPkgOptIfOutputPower reaches or exceeds this value, a Threshold Crossing Alert (TCA) should be sent. Reading will present the threshold value. Writing will set the value of the threshold. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgOptIfUpperOutputPowerThreshold can lead to a Threshold Crossing Alert (TCA) being sent for the respective interface. This alert may be leading to an interruption of service of the users connected to the respective EPON interface, depending on the system action on such an alert. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.12,DOT3-EPON-MIB::dot3ExtPkgOptIfSignalDetect,INTEGER,read-only,,current,true(1):false(2),When getting true(1), there is a valid optical signal at the receive that is above the optical power level for signal detection. When getting false(2) the optical signal at the receive is below the optical power level for signal detection. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.13,DOT3-EPON-MIB::dot3ExtPkgOptIfTransmitAlarm,INTEGER,read-only,,current,true(1):false(2),When getting true(1) there is a non-valid optical signal at the transmit of the interface, either a higher level or lower level than expected. When getting false(2) the optical signal at the transmit is valid and in the required range. This object is applicable for an OLT and an ONU. At the OLT, it has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.1.4.1.5.1.14,DOT3-EPON-MIB::dot3ExtPkgOptIfTransmitEnable,INTEGER,read-write,,current,true(1):false(2),Setting this object to true(1) will cause the optical interface to start transmission (according to the control protocol specified for the logical interface). Setting this object to false(2) will cause the interface to stop the optical transmission. When getting true(1), the optical interface is in transmitting mode (obeying to the logical control protocol). When getting false(2), the optical interface is not in transmitting mode. The write operation is not restricted in this document and can be done at any time. Changing dot3ExtPkgOptIfTransmitEnable state can lead to a halt in the optical transmission of the respective interface leading to an interruption of service of the users connected to the respective EPON interface. The object is relevant when the admin state of the interface is active as set by the dot3MpcpAdminState. This object is applicable for an OLT and an ONU. At the OLT it, has a distinct value for each virtual interface.
.1.3.6.1.2.1.155.2,DOT3-EPON-MIB::dot3EponConformance,,,,,,
.1.3.6.1.2.1.155.2.1,DOT3-EPON-MIB::dot3EponGroups,,,,,,
.1.3.6.1.2.1.155.2.1.1,DOT3-EPON-MIB::dot3MpcpGroupBase,,,,,,A collection of objects of dot3 Mpcp Control entity state definition. Objects are per LLID.
.1.3.6.1.2.1.155.2.1.2,DOT3-EPON-MIB::dot3MpcpGroupStat,,,,,,A collection of objects of dot3 Mpcp Statistics. Objects are per LLID.
.1.3.6.1.2.1.155.2.1.3,DOT3-EPON-MIB::dot3OmpeGroupID,,,,,,A collection of objects of dot3 OMP emulation entity state definition. Objects are per LLID.
.1.3.6.1.2.1.155.2.1.4,DOT3-EPON-MIB::dot3OmpeGroupStat,,,,,,A collection of objects of dot3 OMP emulation Statistics. Objects are per LLID.
.1.3.6.1.2.1.155.2.1.5,DOT3-EPON-MIB::dot3EponFecGroupAll,,,,,,A collection of objects of dot3 FEC group control and statistics. Objects are per LLID.
.1.3.6.1.2.1.155.2.1.6,DOT3-EPON-MIB::dot3ExtPkgGroupControl,,,,,,A collection of objects of dot3ExtPkg control definition. Objects are per LLID.
.1.3.6.1.2.1.155.2.1.7,DOT3-EPON-MIB::dot3ExtPkgGroupQueue,,,,,,A collection of objects of dot3ExtPkg Queue control. Objects are per LLID, per queue.
.1.3.6.1.2.1.155.2.1.8,DOT3-EPON-MIB::dot3ExtPkgGroupQueueSets,,,,,,A collection of objects of dot3ExtPkg queue_set control. Objects are per LLID, per queue, per queue_set.
.1.3.6.1.2.1.155.2.1.9,DOT3-EPON-MIB::dot3ExtPkgGroupOptIf,,,,,,A collection of objects of control and status indication of the optical interface. Objects are per LLID.
.1.3.6.1.2.1.155.2.2,DOT3-EPON-MIB::dot3EponCompliances,,,,,,
.1.3.6.1.2.1.155.2.2.1,DOT3-EPON-MIB::dot3MPCPCompliance,,,,,,The compliance statement for Multi-Point Control Protocol interfaces.
.1.3.6.1.2.1.155.2.2.2,DOT3-EPON-MIB::dot3OmpeCompliance,,,,,,The compliance statement for OMPEmulation interfaces.
.1.3.6.1.2.1.155.2.2.3,DOT3-EPON-MIB::dot3EponFecCompliance,,,,,,The compliance statement for FEC EPON interfaces. This group is mandatory for all FEC supporting interfaces for control and statistics collection.
.1.3.6.1.2.1.155.2.2.4,DOT3-EPON-MIB::dot3ExtPkgCompliance,,,,,,The compliance statement for EPON Interfaces using the extended package.
.1.3.6.1.2.1.156,TCP-ESTATS-MIB::tcpEStatsMIB,,,,,,Documentation of TCP Extended Performance Instrumentation variables from the Web100 project. [Web100] All of the objects in this MIB MUST have the same persistence properties as the underlying TCP implementation. On a reboot, all zero-based counters MUST be cleared, all dynamically created table rows MUST be deleted, and all read-write objects MUST be restored to their default values. It is assumed that all TCP implementation have some initialization code (if nothing else to set IP addresses) that has the opportunity to adjust tcpEStatsConnTableLatency and other read-write scalars controlling the creation of the various tables, before establishing the first TCP connection. Implementations MAY also choose to make these control scalars persist across reboots. Copyright (C) The IETF Trust (2007). This version of this MIB module is a part of RFC 4898; see the RFC itself for full legal notices.
.1.3.6.1.2.1.156.0,TCP-ESTATS-MIB::tcpEStatsNotifications,,,,,,
.1.3.6.1.2.1.156.0.1,TCP-ESTATS-MIB::tcpEStatsEstablishNotification,,,,,,The indicated connection has been accepted (or alternatively entered the established state).
.1.3.6.1.2.1.156.0.2,TCP-ESTATS-MIB::tcpEStatsCloseNotification,,,,,,The indicated connection has left the established state
.1.3.6.1.2.1.156.1,TCP-ESTATS-MIB::tcpEStatsMIBObjects,,,,,,
.1.3.6.1.2.1.156.1.1,TCP-ESTATS-MIB::tcpEStats,,,,,,
.1.3.6.1.2.1.156.1.1.1,TCP-ESTATS-MIB::tcpEStatsListenerTable,,not-accessible,,current,,This table contains information about TCP Listeners, in addition to the information maintained by the tcpListenerTable RFC 4022.
.1.3.6.1.2.1.156.1.1.1.1,TCP-ESTATS-MIB::tcpEStatsListenerEntry,,not-accessible,,current,,Each entry in the table contains information about a specific TCP Listener.
.1.3.6.1.2.1.156.1.1.1.1.1,TCP-ESTATS-MIB::tcpEStatsListenerStartTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time this listener was established. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.156.1.1.1.1.2,TCP-ESTATS-MIB::tcpEStatsListenerSynRcvd,Gauge32,read-only,,current,,The number of SYNs which have been received for this listener. The total number of failed connections for all reasons can be estimated to be tcpEStatsListenerSynRcvd minus tcpEStatsListenerAccepted and tcpEStatsListenerCurBacklog.
.1.3.6.1.2.1.156.1.1.1.1.3,TCP-ESTATS-MIB::tcpEStatsListenerInitial,Gauge32,read-only,,current,,The total number of connections for which the Listener has allocated initial state and placed the connection in the backlog. This may happen in the SYN-RCVD or ESTABLISHED states, depending on the implementation.
.1.3.6.1.2.1.156.1.1.1.1.4,TCP-ESTATS-MIB::tcpEStatsListenerEstablished,Gauge32,read-only,,current,,The number of connections that have been established to this endpoint (e.g., the number of first ACKs that have been received for this listener).
.1.3.6.1.2.1.156.1.1.1.1.5,TCP-ESTATS-MIB::tcpEStatsListenerAccepted,Gauge32,read-only,,current,,The total number of connections for which the Listener has successfully issued an accept, removing the connection from the backlog.
.1.3.6.1.2.1.156.1.1.1.1.6,TCP-ESTATS-MIB::tcpEStatsListenerExceedBacklog,Gauge32,read-only,,current,,The total number of connections dropped from the backlog by this listener due to all reasons. This includes all connections that are allocated initial resources, but are not accepted for some reason.
.1.3.6.1.2.1.156.1.1.1.1.7,TCP-ESTATS-MIB::tcpEStatsListenerHCSynRcvd,Counter64,read-only,,current,,The number of SYNs that have been received for this listener on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerSynRcvd.
.1.3.6.1.2.1.156.1.1.1.1.8,TCP-ESTATS-MIB::tcpEStatsListenerHCInitial,Counter64,read-only,,current,,The total number of connections for which the Listener has allocated initial state and placed the connection in the backlog on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerInitial.
.1.3.6.1.2.1.156.1.1.1.1.9,TCP-ESTATS-MIB::tcpEStatsListenerHCEstablished,Counter64,read-only,,current,,The number of connections that have been established to this endpoint on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerEstablished.
.1.3.6.1.2.1.156.1.1.1.1.10,TCP-ESTATS-MIB::tcpEStatsListenerHCAccepted,Counter64,read-only,,current,,The total number of connections for which the Listener has successfully issued an accept, removing the connection from the backlog on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerAccepted.
.1.3.6.1.2.1.156.1.1.1.1.11,TCP-ESTATS-MIB::tcpEStatsListenerHCExceedBacklog,Counter64,read-only,,current,,The total number of connections dropped from the backlog by this listener due to all reasons on systems that can process (or reject) more than 1 million connections per second. See tcpEStatsListenerExceedBacklog.
.1.3.6.1.2.1.156.1.1.1.1.12,TCP-ESTATS-MIB::tcpEStatsListenerCurConns,Gauge32,read-only,,current,,The current number of connections in the ESTABLISHED state, which have also been accepted. It excludes connections that have been established but not accepted because they are still subject to being discarded to shed load without explicit action by either endpoint.
.1.3.6.1.2.1.156.1.1.1.1.13,TCP-ESTATS-MIB::tcpEStatsListenerMaxBacklog,Unsigned32,read-only,,current,,The maximum number of connections allowed in the backlog at one time.
.1.3.6.1.2.1.156.1.1.1.1.14,TCP-ESTATS-MIB::tcpEStatsListenerCurBacklog,Gauge32,read-only,,current,,The current number of connections that are in the backlog. This gauge includes connections in ESTABLISHED or SYN-RECEIVED states for which the Listener has not yet issued an accept. If this listener is using some technique to implicitly represent the SYN-RECEIVED states (e.g., by cryptographically encoding the state information in the initial sequence number, ISS), it MAY elect to exclude connections in the SYN-RECEIVED state from the backlog.
.1.3.6.1.2.1.156.1.1.1.1.15,TCP-ESTATS-MIB::tcpEStatsListenerCurEstabBacklog,Gauge32,read-only,,current,,The current number of connections in the backlog that are in the ESTABLISHED state, but for which the Listener has not yet issued an accept.
.1.3.6.1.2.1.156.1.1.2,TCP-ESTATS-MIB::tcpEStatsConnectIdTable,,not-accessible,,current,,This table maps information that uniquely identifies each active TCP connection to the connection ID used by other tables in this MIB Module. It is an extension of tcpConnectionTable in RFC 4022. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
.1.3.6.1.2.1.156.1.1.2.1,TCP-ESTATS-MIB::tcpEStatsConnectIdEntry,,not-accessible,,current,,Each entry in this table maps a TCP connection 4-tuple to a connection index.
.1.3.6.1.2.1.156.1.1.2.1.1,TCP-ESTATS-MIB::tcpEStatsConnectIndex,Unsigned32,read-only,,current,,A unique integer value assigned to each TCP Connection entry. The RECOMMENDED algorithm is to begin at 1 and increase to some implementation-specific maximum value and then start again at 1 skipping values already in use.
.1.3.6.1.2.1.156.1.1.3,TCP-ESTATS-MIB::tcpEStatsPerfTable,,not-accessible,,current,,This table contains objects that are useful for measuring TCP performance and first line problem diagnosis. Most objects in this table directly expose some TCP state variable or are easily implemented as simple functions (e.g., the maximum value) of TCP state variables. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
.1.3.6.1.2.1.156.1.1.3.1,TCP-ESTATS-MIB::tcpEStatsPerfEntry,,not-accessible,tcpEStatsConnectIndex,current,,Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
.1.3.6.1.2.1.156.1.1.3.1.1,TCP-ESTATS-MIB::tcpEStatsPerfSegsOut,Gauge32,read-only,,current,,The total number of segments sent.
.1.3.6.1.2.1.156.1.1.3.1.2,TCP-ESTATS-MIB::tcpEStatsPerfDataSegsOut,Gauge32,read-only,,current,,The number of segments sent containing a positive length data segment.
.1.3.6.1.2.1.156.1.1.3.1.3,TCP-ESTATS-MIB::tcpEStatsPerfDataOctetsOut,Gauge32,read-only,,current,,The number of octets of data contained in transmitted segments, including retransmitted data. Note that this does not include TCP headers.
.1.3.6.1.2.1.156.1.1.3.1.4,TCP-ESTATS-MIB::tcpEStatsPerfHCDataOctetsOut,Counter64,read-only,,current,,The number of octets of data contained in transmitted segments, including retransmitted data, on systems that can transmit more than 10 million bits per second. Note that this does not include TCP headers.
.1.3.6.1.2.1.156.1.1.3.1.5,TCP-ESTATS-MIB::tcpEStatsPerfSegsRetrans,Gauge32,read-only,,current,,The number of segments transmitted containing at least some retransmitted data.
.1.3.6.1.2.1.156.1.1.3.1.6,TCP-ESTATS-MIB::tcpEStatsPerfOctetsRetrans,Gauge32,read-only,,current,,The number of octets retransmitted.
.1.3.6.1.2.1.156.1.1.3.1.7,TCP-ESTATS-MIB::tcpEStatsPerfSegsIn,Gauge32,read-only,,current,,The total number of segments received.
.1.3.6.1.2.1.156.1.1.3.1.8,TCP-ESTATS-MIB::tcpEStatsPerfDataSegsIn,Gauge32,read-only,,current,,The number of segments received containing a positive length data segment.
.1.3.6.1.2.1.156.1.1.3.1.9,TCP-ESTATS-MIB::tcpEStatsPerfDataOctetsIn,Gauge32,read-only,,current,,The number of octets contained in received data segments, including retransmitted data. Note that this does not include TCP headers.
.1.3.6.1.2.1.156.1.1.3.1.10,TCP-ESTATS-MIB::tcpEStatsPerfHCDataOctetsIn,Counter64,read-only,,current,,The number of octets contained in received data segments, including retransmitted data, on systems that can receive more than 10 million bits per second. Note that this does not include TCP headers.
.1.3.6.1.2.1.156.1.1.3.1.11,TCP-ESTATS-MIB::tcpEStatsPerfElapsedSecs,Gauge32,read-only,,current,,The seconds part of the time elapsed between tcpEStatsPerfStartTimeStamp and the most recent protocol event (segment sent or received).
.1.3.6.1.2.1.156.1.1.3.1.12,TCP-ESTATS-MIB::tcpEStatsPerfElapsedMicroSecs,Gauge32,read-only,,current,,The micro-second part of time elapsed between tcpEStatsPerfStartTimeStamp to the most recent protocol event (segment sent or received). This may be updated in whatever time granularity is the system supports.
.1.3.6.1.2.1.156.1.1.3.1.13,TCP-ESTATS-MIB::tcpEStatsPerfStartTimeStamp,OCTET,read-only,,current,,Time at which this row was created and all ZeroBasedCounters in the row were initialized to zero.
.1.3.6.1.2.1.156.1.1.3.1.14,TCP-ESTATS-MIB::tcpEStatsPerfCurMSS,Gauge32,read-only,,current,,The current maximum segment size (MSS), in octets.
.1.3.6.1.2.1.156.1.1.3.1.15,TCP-ESTATS-MIB::tcpEStatsPerfPipeSize,Gauge32,read-only,,current,,The TCP senders current estimate of the number of unacknowledged data octets in the network. While not in recovery (e.g., while the receiver is not reporting missing data to the sender), this is precisely the same as 'Flight size' as defined in RFC 2581, which can be computed as SND.NXT minus SND.UNA. [RFC793] During recovery, the TCP sender has incomplete information about the state of the network (e.g., which segments are lost vs reordered, especially if the return path is also dropping TCP acknowledgments). Current TCP standards do not mandate any specific algorithm for estimating the number of unacknowledged data octets in the network. RFC 3517 describes a conservative algorithm to use SACK information to estimate the number of unacknowledged data octets in the network. tcpEStatsPerfPipeSize object SHOULD be the same as 'pipe' as defined in RFC 3517 if it is implemented. (Note that while not in recovery the pipe algorithm yields the same values as flight size). If RFC 3517 is not implemented, the data octets in flight SHOULD be estimated as SND.NXT minus SND.UNA adjusted by some measure of the data that has left the network and retransmitted data. For example, with Reno or NewReno style TCP, the number of duplicate acknowledgment is used to count the number of segments that have left the network. That is, PipeSize=SND.NXT-SND.UNA+(retransmits-dupacks)*CurMSS
.1.3.6.1.2.1.156.1.1.3.1.16,TCP-ESTATS-MIB::tcpEStatsPerfMaxPipeSize,Gauge32,read-only,,current,,The maximum value of tcpEStatsPerfPipeSize, for this connection.
.1.3.6.1.2.1.156.1.1.3.1.17,TCP-ESTATS-MIB::tcpEStatsPerfSmoothedRTT,Gauge32,read-only,,current,,The smoothed round trip time used in calculation of the RTO. See SRTT in [RFC2988].
.1.3.6.1.2.1.156.1.1.3.1.18,TCP-ESTATS-MIB::tcpEStatsPerfCurRTO,Gauge32,read-only,,current,,The current value of the retransmit timer RTO.
.1.3.6.1.2.1.156.1.1.3.1.19,TCP-ESTATS-MIB::tcpEStatsPerfCongSignals,Gauge32,read-only,,current,,The number of multiplicative downward congestion window adjustments due to all forms of congestion signals, including Fast Retransmit, Explicit Congestion Notification (ECN), and timeouts. This object summarizes all events that invoke the MD portion of Additive Increase Multiplicative Decrease (AIMD) congestion control, and as such is the best indicator of how a cwnd is being affected by congestion. Note that retransmission timeouts multiplicatively reduce the window implicitly by setting ssthresh, and SHOULD be included in tcpEStatsPerfCongSignals. In order to minimize spurious congestion indications due to out-of-order segments, tcpEStatsPerfCongSignals SHOULD be incremented in association with the Fast Retransmit algorithm.
.1.3.6.1.2.1.156.1.1.3.1.20,TCP-ESTATS-MIB::tcpEStatsPerfCurCwnd,Gauge32,read-only,,current,,The current congestion window, in octets.
.1.3.6.1.2.1.156.1.1.3.1.21,TCP-ESTATS-MIB::tcpEStatsPerfCurSsthresh,Gauge32,read-only,,current,,The current slow start threshold in octets.
.1.3.6.1.2.1.156.1.1.3.1.22,TCP-ESTATS-MIB::tcpEStatsPerfTimeouts,Gauge32,read-only,,current,,The number of times the retransmit timeout has expired when the RTO backoff multiplier is equal to one.
.1.3.6.1.2.1.156.1.1.3.1.23,TCP-ESTATS-MIB::tcpEStatsPerfCurRwinSent,Gauge32,read-only,,current,,The most recent window advertisement sent, in octets.
.1.3.6.1.2.1.156.1.1.3.1.24,TCP-ESTATS-MIB::tcpEStatsPerfMaxRwinSent,Gauge32,read-only,,current,,The maximum window advertisement sent, in octets.
.1.3.6.1.2.1.156.1.1.3.1.25,TCP-ESTATS-MIB::tcpEStatsPerfZeroRwinSent,Gauge32,read-only,,current,,The number of acknowledgments sent announcing a zero receive window, when the previously announced window was not zero.
.1.3.6.1.2.1.156.1.1.3.1.26,TCP-ESTATS-MIB::tcpEStatsPerfCurRwinRcvd,Gauge32,read-only,,current,,The most recent window advertisement received, in octets.
.1.3.6.1.2.1.156.1.1.3.1.27,TCP-ESTATS-MIB::tcpEStatsPerfMaxRwinRcvd,Gauge32,read-only,,current,,The maximum window advertisement received, in octets.
.1.3.6.1.2.1.156.1.1.3.1.28,TCP-ESTATS-MIB::tcpEStatsPerfZeroRwinRcvd,Gauge32,read-only,,current,,The number of acknowledgments received announcing a zero receive window, when the previously announced window was not zero.
.1.3.6.1.2.1.156.1.1.3.1.31,TCP-ESTATS-MIB::tcpEStatsPerfSndLimTransRwin,Gauge32,read-only,,current,,The number of transitions into the 'Receiver Limited' state from either the 'Congestion Limited' or 'Sender Limited' states. This state is entered whenever TCP transmission stops because the sender has filled the announced receiver window, i.e., when SND.NXT has advanced to SND.UNA + SND.WND - 1 as described in RFC 793.
.1.3.6.1.2.1.156.1.1.3.1.32,TCP-ESTATS-MIB::tcpEStatsPerfSndLimTransCwnd,Gauge32,read-only,,current,,The number of transitions into the 'Congestion Limited' state from either the 'Receiver Limited' or 'Sender Limited' states. This state is entered whenever TCP transmission stops because the sender has reached some limit defined by congestion control (e.g., cwnd) or other algorithms (retransmission timeouts) designed to control network traffic. See the definition of 'CONGESTION WINDOW' in RFC 2581.
.1.3.6.1.2.1.156.1.1.3.1.33,TCP-ESTATS-MIB::tcpEStatsPerfSndLimTransSnd,Gauge32,read-only,,current,,The number of transitions into the 'Sender Limited' state from either the 'Receiver Limited' or 'Congestion Limited' states. This state is entered whenever TCP transmission stops due to some sender limit such as running out of application data or other resources and the Karn algorithm. When TCP stops sending data for any reason, which cannot be classified as Receiver Limited or Congestion Limited, it MUST be treated as Sender Limited.
.1.3.6.1.2.1.156.1.1.3.1.34,TCP-ESTATS-MIB::tcpEStatsPerfSndLimTimeRwin,Gauge32,read-only,,current,,The cumulative time spent in the 'Receiver Limited' state. See tcpEStatsPerfSndLimTransRwin.
.1.3.6.1.2.1.156.1.1.3.1.35,TCP-ESTATS-MIB::tcpEStatsPerfSndLimTimeCwnd,Gauge32,read-only,,current,,The cumulative time spent in the 'Congestion Limited' state. See tcpEStatsPerfSndLimTransCwnd. When there is a retransmission timeout, it SHOULD be counted in tcpEStatsPerfSndLimTimeCwnd (and not the cumulative time for some other state.)
.1.3.6.1.2.1.156.1.1.3.1.36,TCP-ESTATS-MIB::tcpEStatsPerfSndLimTimeSnd,Gauge32,read-only,,current,,The cumulative time spent in the 'Sender Limited' state. See tcpEStatsPerfSndLimTransSnd.
.1.3.6.1.2.1.156.1.1.4,TCP-ESTATS-MIB::tcpEStatsPathTable,,not-accessible,,current,,This table contains objects that can be used to infer detailed behavior of the Internet path, such as the extent that there is reordering, ECN bits, and if RTT fluctuations are correlated to losses. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
.1.3.6.1.2.1.156.1.1.4.1,TCP-ESTATS-MIB::tcpEStatsPathEntry,,not-accessible,tcpEStatsConnectIndex,current,,Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
.1.3.6.1.2.1.156.1.1.4.1.1,TCP-ESTATS-MIB::tcpEStatsPathRetranThresh,Gauge32,read-only,,current,,The number of duplicate acknowledgments required to trigger Fast Retransmit. Note that although this is constant in traditional Reno TCP implementations, it is adaptive in many newer TCPs.
.1.3.6.1.2.1.156.1.1.4.1.2,TCP-ESTATS-MIB::tcpEStatsPathNonRecovDAEpisodes,Gauge32,read-only,,current,,The number of duplicate acknowledgment episodes that did not trigger a Fast Retransmit because ACK advanced prior to the number of duplicate acknowledgments reaching RetranThresh. In many implementations this is the number of times the 'dupacks' counter is set to zero when it is non-zero but less than RetranThresh. Note that the change in tcpEStatsPathNonRecovDAEpisodes divided by the change in tcpEStatsPerfDataSegsOut is an estimate of the frequency of data reordering on the forward path over some interval.
.1.3.6.1.2.1.156.1.1.4.1.3,TCP-ESTATS-MIB::tcpEStatsPathSumOctetsReordered,Gauge32,read-only,,current,,The sum of the amounts SND.UNA advances on the acknowledgment which ends a dup-ack episode without a retransmission. Note the change in tcpEStatsPathSumOctetsReordered divided by the change in tcpEStatsPathNonRecovDAEpisodes is an estimates of the average reordering distance, over some interval.
.1.3.6.1.2.1.156.1.1.4.1.4,TCP-ESTATS-MIB::tcpEStatsPathNonRecovDA,Gauge32,read-only,,current,,Duplicate acks (or SACKS) that did not trigger a Fast Retransmit because ACK advanced prior to the number of duplicate acknowledgments reaching RetranThresh. In many implementations, this is the sum of the 'dupacks' counter, just before it is set to zero because ACK advanced without a Fast Retransmit. Note that the change in tcpEStatsPathNonRecovDA divided by the change in tcpEStatsPathNonRecovDAEpisodes is an estimate of the average reordering distance in segments over some interval.
.1.3.6.1.2.1.156.1.1.4.1.11,TCP-ESTATS-MIB::tcpEStatsPathSampleRTT,Gauge32,read-only,,current,,The most recent raw round trip time measurement used in calculation of the RTO.
.1.3.6.1.2.1.156.1.1.4.1.12,TCP-ESTATS-MIB::tcpEStatsPathRTTVar,Gauge32,read-only,,current,,The round trip time variation used in calculation of the RTO. See RTTVAR in [RFC2988].
.1.3.6.1.2.1.156.1.1.4.1.13,TCP-ESTATS-MIB::tcpEStatsPathMaxRTT,Gauge32,read-only,,current,,The maximum sampled round trip time.
.1.3.6.1.2.1.156.1.1.4.1.14,TCP-ESTATS-MIB::tcpEStatsPathMinRTT,Gauge32,read-only,,current,,The minimum sampled round trip time.
.1.3.6.1.2.1.156.1.1.4.1.15,TCP-ESTATS-MIB::tcpEStatsPathSumRTT,Gauge32,read-only,,current,,The sum of all sampled round trip times. Note that the change in tcpEStatsPathSumRTT divided by the change in tcpEStatsPathCountRTT is the mean RTT, uniformly averaged over an enter interval.
.1.3.6.1.2.1.156.1.1.4.1.16,TCP-ESTATS-MIB::tcpEStatsPathHCSumRTT,Counter64,read-only,,current,,The sum of all sampled round trip times, on all systems that implement multiple concurrent RTT measurements. Note that the change in tcpEStatsPathHCSumRTT divided by the change in tcpEStatsPathCountRTT is the mean RTT, uniformly averaged over an enter interval.
.1.3.6.1.2.1.156.1.1.4.1.17,TCP-ESTATS-MIB::tcpEStatsPathCountRTT,Gauge32,read-only,,current,,The number of round trip time samples included in tcpEStatsPathSumRTT and tcpEStatsPathHCSumRTT.
.1.3.6.1.2.1.156.1.1.4.1.18,TCP-ESTATS-MIB::tcpEStatsPathMaxRTO,Gauge32,read-only,,current,,The maximum value of the retransmit timer RTO.
.1.3.6.1.2.1.156.1.1.4.1.19,TCP-ESTATS-MIB::tcpEStatsPathMinRTO,Gauge32,read-only,,current,,The minimum value of the retransmit timer RTO.
.1.3.6.1.2.1.156.1.1.4.1.20,TCP-ESTATS-MIB::tcpEStatsPathIpTtl,Unsigned32,read-only,,current,,The value of the TTL field carried in the most recently received IP header. This is sometimes useful to detect changing or unstable routes.
.1.3.6.1.2.1.156.1.1.4.1.21,TCP-ESTATS-MIB::tcpEStatsPathIpTosIn,OCTET,read-only,,current,,The value of the IPv4 Type of Service octet, or the IPv6 traffic class octet, carried in the most recently received IP header. This is useful to diagnose interactions between TCP and any IP layer packet scheduling and delivery policy, which might be in effect to implement Diffserv.
.1.3.6.1.2.1.156.1.1.4.1.22,TCP-ESTATS-MIB::tcpEStatsPathIpTosOut,OCTET,read-only,,current,,The value of the IPv4 Type Of Service octet, or the IPv6 traffic class octet, carried in the most recently transmitted IP header. This is useful to diagnose interactions between TCP and any IP layer packet scheduling and delivery policy, which might be in effect to implement Diffserv.
.1.3.6.1.2.1.156.1.1.4.1.23,TCP-ESTATS-MIB::tcpEStatsPathPreCongSumCwnd,Gauge32,read-only,,current,,The sum of the values of the congestion window, in octets, captured each time a congestion signal is received. This MUST be updated each time tcpEStatsPerfCongSignals is incremented, such that the change in tcpEStatsPathPreCongSumCwnd divided by the change in tcpEStatsPerfCongSignals is the average window (over some interval) just prior to a congestion signal.
.1.3.6.1.2.1.156.1.1.4.1.24,TCP-ESTATS-MIB::tcpEStatsPathPreCongSumRTT,Gauge32,read-only,,current,,Sum of the last sample of the RTT (tcpEStatsPathSampleRTT) prior to the received congestion signals. This MUST be updated each time tcpEStatsPerfCongSignals is incremented, such that the change in tcpEStatsPathPreCongSumRTT divided by the change in tcpEStatsPerfCongSignals is the average RTT (over some interval) just prior to a congestion signal.
.1.3.6.1.2.1.156.1.1.4.1.25,TCP-ESTATS-MIB::tcpEStatsPathPostCongSumRTT,Gauge32,read-only,,current,,Sum of the first sample of the RTT (tcpEStatsPathSampleRTT) following each congestion signal. Such that the change in tcpEStatsPathPostCongSumRTT divided by the change in tcpEStatsPathPostCongCountRTT is the average RTT (over some interval) just after a congestion signal.
.1.3.6.1.2.1.156.1.1.4.1.26,TCP-ESTATS-MIB::tcpEStatsPathPostCongCountRTT,Gauge32,read-only,,current,,The number of RTT samples included in tcpEStatsPathPostCongSumRTT such that the change in tcpEStatsPathPostCongSumRTT divided by the change in tcpEStatsPathPostCongCountRTT is the average RTT (over some interval) just after a congestion signal.
.1.3.6.1.2.1.156.1.1.4.1.27,TCP-ESTATS-MIB::tcpEStatsPathECNsignals,Gauge32,read-only,,current,,The number of congestion signals delivered to the TCP sender via explicit congestion notification (ECN). This is typically the number of segments bearing Echo Congestion Experienced (ECE) bits, but should also include segments failing the ECN nonce check or other explicit congestion signals.
.1.3.6.1.2.1.156.1.1.4.1.28,TCP-ESTATS-MIB::tcpEStatsPathDupAckEpisodes,Gauge32,read-only,,current,,The number of Duplicate Acks Sent when prior Ack was not duplicate. This is the number of times that a contiguous series of duplicate acknowledgments have been sent. This is an indication of the number of data segments lost or reordered on the path from the remote TCP endpoint to the near TCP endpoint.
.1.3.6.1.2.1.156.1.1.4.1.29,TCP-ESTATS-MIB::tcpEStatsPathRcvRTT,Gauge32,read-only,,current,,The receiver's estimate of the Path RTT. Adaptive receiver window algorithms depend on the receiver to having a good estimate of the path RTT.
.1.3.6.1.2.1.156.1.1.4.1.30,TCP-ESTATS-MIB::tcpEStatsPathDupAcksOut,Gauge32,read-only,,current,,The number of duplicate ACKs sent. The ratio of the change in tcpEStatsPathDupAcksOut to the change in tcpEStatsPathDupAckEpisodes is an indication of reorder or recovery distance over some interval.
.1.3.6.1.2.1.156.1.1.4.1.31,TCP-ESTATS-MIB::tcpEStatsPathCERcvd,Gauge32,read-only,,current,,The number of segments received with IP headers bearing Congestion Experienced (CE) markings.
.1.3.6.1.2.1.156.1.1.4.1.32,TCP-ESTATS-MIB::tcpEStatsPathECESent,Gauge32,read-only,,current,,Number of times the Echo Congestion Experienced (ECE) bit in the TCP header has been set (transitioned from 0 to 1), due to a Congestion Experienced (CE) marking on an IP header. Note that ECE can be set and reset only once per RTT, while CE can be set on many segments per RTT.
.1.3.6.1.2.1.156.1.1.5,TCP-ESTATS-MIB::tcpEStatsStackTable,,not-accessible,,current,,This table contains objects that are most useful for determining how well some of the TCP control algorithms are coping with this particular path. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
.1.3.6.1.2.1.156.1.1.5.1,TCP-ESTATS-MIB::tcpEStatsStackEntry,,not-accessible,tcpEStatsConnectIndex,current,,Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
.1.3.6.1.2.1.156.1.1.5.1.1,TCP-ESTATS-MIB::tcpEStatsStackActiveOpen,INTEGER,read-only,,current,true(1):false(2),True(1) if the local connection traversed the SYN-SENT state, else false(2).
.1.3.6.1.2.1.156.1.1.5.1.2,TCP-ESTATS-MIB::tcpEStatsStackMSSSent,Unsigned32,read-only,,current,,The value sent in an MSS option, or zero if none.
.1.3.6.1.2.1.156.1.1.5.1.3,TCP-ESTATS-MIB::tcpEStatsStackMSSRcvd,Unsigned32,read-only,,current,,The value received in an MSS option, or zero if none.
.1.3.6.1.2.1.156.1.1.5.1.4,TCP-ESTATS-MIB::tcpEStatsStackWinScaleSent,Integer32,read-only,,current,,The value of the transmitted window scale option if one was sent; otherwise, a value of -1. Note that if both tcpEStatsStackWinScaleSent and tcpEStatsStackWinScaleRcvd are not -1, then Rcv.Wind.Scale will be the same as this value and used to scale receiver window announcements from the local host to the remote host.
.1.3.6.1.2.1.156.1.1.5.1.5,TCP-ESTATS-MIB::tcpEStatsStackWinScaleRcvd,Integer32,read-only,,current,,The value of the received window scale option if one was received; otherwise, a value of -1. Note that if both tcpEStatsStackWinScaleSent and tcpEStatsStackWinScaleRcvd are not -1, then Snd.Wind.Scale will be the same as this value and used to scale receiver window announcements from the remote host to the local host.
.1.3.6.1.2.1.156.1.1.5.1.6,TCP-ESTATS-MIB::tcpEStatsStackTimeStamps,INTEGER,read-only,,current,enabled(1):selfDisabled(2):peerDisabled(3),Enabled(1) if TCP timestamps have been negotiated on, selfDisabled(2) if they are disabled or not implemented on the local host, or peerDisabled(3) if not negotiated by the remote hosts.
.1.3.6.1.2.1.156.1.1.5.1.7,TCP-ESTATS-MIB::tcpEStatsStackECN,INTEGER,read-only,,current,enabled(1):selfDisabled(2):peerDisabled(3),Enabled(1) if Explicit Congestion Notification (ECN) has been negotiated on, selfDisabled(2) if it is disabled or not implemented on the local host, or peerDisabled(3) if not negotiated by the remote hosts.
.1.3.6.1.2.1.156.1.1.5.1.8,TCP-ESTATS-MIB::tcpEStatsStackWillSendSACK,INTEGER,read-only,,current,enabled(1):selfDisabled(2):peerDisabled(3),Enabled(1) if the local host will send SACK options, selfDisabled(2) if SACK is disabled or not implemented on the local host, or peerDisabled(3) if the remote host did not send the SACK-permitted option. Note that SACK negotiation is not symmetrical. SACK can enabled on one side of the connection and not the other.
.1.3.6.1.2.1.156.1.1.5.1.9,TCP-ESTATS-MIB::tcpEStatsStackWillUseSACK,INTEGER,read-only,,current,enabled(1):selfDisabled(2):peerDisabled(3),Enabled(1) if the local host will process SACK options, selfDisabled(2) if SACK is disabled or not implemented on the local host, or peerDisabled(3) if the remote host sends duplicate ACKs without SACK options, or the local host otherwise decides not to process received SACK options. Unlike other TCP options, the remote data receiver cannot explicitly indicate if it is able to generate SACK options. When sending data, the local host has to deduce if the remote receiver is sending SACK options. This object can transition from Enabled(1) to peerDisabled(3) after the SYN exchange. Note that SACK negotiation is not symmetrical. SACK can enabled on one side of the connection and not the other.
.1.3.6.1.2.1.156.1.1.5.1.10,TCP-ESTATS-MIB::tcpEStatsStackState,INTEGER,read-only,,current,tcpESStateClosed(1):tcpESStateListen(2):tcpESStateSynSent(3):tcpESStateSynReceived(4):tcpESStateEstablished(5):tcpESStateFinWait1(6):tcpESStateFinWait2(7):tcpESStateCloseWait(8):tcpESStateLastAck(9):tcpESStateClosing(10):tcpESStateTimeWait(11):tcpESStateDeleteTcb(12),An integer value representing the connection state from the TCP State Transition Diagram. The value listen(2) is included only for parallelism to the old tcpConnTable, and SHOULD NOT be used because the listen state in managed by the tcpListenerTable. The value DeleteTcb(12) is included only for parallelism to the tcpConnTable mechanism for terminating connections, although this table does not permit writing.
.1.3.6.1.2.1.156.1.1.5.1.11,TCP-ESTATS-MIB::tcpEStatsStackNagle,INTEGER,read-only,,current,true(1):false(2),True(1) if the Nagle algorithm is being used, else false(2).
.1.3.6.1.2.1.156.1.1.5.1.12,TCP-ESTATS-MIB::tcpEStatsStackMaxSsCwnd,Gauge32,read-only,,current,,The maximum congestion window used during Slow Start, in octets.
.1.3.6.1.2.1.156.1.1.5.1.13,TCP-ESTATS-MIB::tcpEStatsStackMaxCaCwnd,Gauge32,read-only,,current,,The maximum congestion window used during Congestion Avoidance, in octets.
.1.3.6.1.2.1.156.1.1.5.1.14,TCP-ESTATS-MIB::tcpEStatsStackMaxSsthresh,Gauge32,read-only,,current,,The maximum slow start threshold, excluding the initial value.
.1.3.6.1.2.1.156.1.1.5.1.15,TCP-ESTATS-MIB::tcpEStatsStackMinSsthresh,Gauge32,read-only,,current,,The minimum slow start threshold.
.1.3.6.1.2.1.156.1.1.5.1.16,TCP-ESTATS-MIB::tcpEStatsStackInRecovery,INTEGER,read-only,,current,tcpESDataContiguous(1):tcpESDataUnordered(2):tcpESDataRecovery(3),An integer value representing the state of the loss recovery for this connection. tcpESDataContiguous(1) indicates that the remote receiver is reporting contiguous data (no duplicate acknowledgments or SACK options) and that there are no unacknowledged retransmissions. tcpESDataUnordered(2) indicates that the remote receiver is reporting missing or out-of-order data (e.g., sending duplicate acknowledgments or SACK options) and that there are no unacknowledged retransmissions (because the missing data has not yet been retransmitted). tcpESDataRecovery(3) indicates that the sender has outstanding retransmitted data that is still unacknowledged.
.1.3.6.1.2.1.156.1.1.5.1.17,TCP-ESTATS-MIB::tcpEStatsStackDupAcksIn,Gauge32,read-only,,current,,The number of duplicate ACKs received.
.1.3.6.1.2.1.156.1.1.5.1.18,TCP-ESTATS-MIB::tcpEStatsStackSpuriousFrDetected,Gauge32,read-only,,current,,The number of acknowledgments reporting out-of-order segments after the Fast Retransmit algorithm has already retransmitted the segments. (For example as detected by the Eifel algorithm).'
.1.3.6.1.2.1.156.1.1.5.1.19,TCP-ESTATS-MIB::tcpEStatsStackSpuriousRtoDetected,Gauge32,read-only,,current,,The number of acknowledgments reporting segments that have already been retransmitted due to a Retransmission Timeout.
.1.3.6.1.2.1.156.1.1.5.1.21,TCP-ESTATS-MIB::tcpEStatsStackSoftErrors,Gauge32,read-only,,current,,The number of segments that fail various consistency tests during TCP input processing. Soft errors might cause the segment to be discarded but some do not. Some of these soft errors cause the generation of a TCP acknowledgment, while others are silently discarded.
.1.3.6.1.2.1.156.1.1.5.1.22,TCP-ESTATS-MIB::tcpEStatsStackSoftErrorReason,INTEGER,read-only,,current,belowDataWindow(1):aboveDataWindow(2):belowAckWindow(3):aboveAckWindow(4):belowTSWindow(5):aboveTSWindow(6):dataCheckSum(7):otherSoftError(8),This object identifies which consistency test most recently failed during TCP input processing. This object SHOULD be set every time tcpEStatsStackSoftErrors is incremented. The codes are as follows: belowDataWindow(1) - All data in the segment is below SND.UNA. (Normal for keep-alives and zero window probes). aboveDataWindow(2) - Some data in the segment is above SND.WND. (Indicates an implementation bug or possible attack). belowAckWindow(3) - ACK below SND.UNA. (Indicates that the return path is reordering ACKs) aboveAckWindow(4) - An ACK for data that we have not sent. (Indicates an implementation bug or possible attack). belowTSWindow(5) - TSecr on the segment is older than the current TS.Recent (Normal for the rare case where PAWS detects data reordered by the network). aboveTSWindow(6) - TSecr on the segment is newer than the current TS.Recent. (Indicates an implementation bug or possible attack). dataCheckSum(7) - Incorrect checksum. Note that this value is intrinsically fragile, because the header fields used to identify the connection may have been corrupted. otherSoftError(8) - All other soft errors not listed above.
.1.3.6.1.2.1.156.1.1.5.1.23,TCP-ESTATS-MIB::tcpEStatsStackSlowStart,Gauge32,read-only,,current,,The number of times the congestion window has been increased by the Slow Start algorithm.
.1.3.6.1.2.1.156.1.1.5.1.24,TCP-ESTATS-MIB::tcpEStatsStackCongAvoid,Gauge32,read-only,,current,,The number of times the congestion window has been increased by the Congestion Avoidance algorithm.
.1.3.6.1.2.1.156.1.1.5.1.25,TCP-ESTATS-MIB::tcpEStatsStackOtherReductions,Gauge32,read-only,,current,,The number of congestion window reductions made as a result of anything other than AIMD congestion control algorithms. Examples of non-multiplicative window reductions include Congestion Window Validation [RFC2861] and experimental algorithms such as Vegas [Bra94]. All window reductions MUST be counted as either tcpEStatsPerfCongSignals or tcpEStatsStackOtherReductions.
.1.3.6.1.2.1.156.1.1.5.1.26,TCP-ESTATS-MIB::tcpEStatsStackCongOverCount,Gauge32,read-only,,current,,The number of congestion events that were 'backed out' of the congestion control state machine such that the congestion window was restored to a prior value. This can happen due to the Eifel algorithm [RFC3522] or other algorithms that can be used to detect and cancel spurious invocations of the Fast Retransmit Algorithm. Although it may be feasible to undo the effects of spurious invocation of the Fast Retransmit congestion events cannot easily be backed out of tcpEStatsPerfCongSignals and tcpEStatsPathPreCongSumCwnd, etc.
.1.3.6.1.2.1.156.1.1.5.1.27,TCP-ESTATS-MIB::tcpEStatsStackFastRetran,Gauge32,read-only,,current,,The number of invocations of the Fast Retransmit algorithm.
.1.3.6.1.2.1.156.1.1.5.1.28,TCP-ESTATS-MIB::tcpEStatsStackSubsequentTimeouts,Gauge32,read-only,,current,,The number of times the retransmit timeout has expired after the RTO has been doubled. See Section 5.5 of RFC 2988.
.1.3.6.1.2.1.156.1.1.5.1.29,TCP-ESTATS-MIB::tcpEStatsStackCurTimeoutCount,Gauge32,read-only,,current,,The current number of times the retransmit timeout has expired without receiving an acknowledgment for new data. tcpEStatsStackCurTimeoutCount is reset to zero when new data is acknowledged and incremented for each invocation of Section 5.5 of RFC 2988.
.1.3.6.1.2.1.156.1.1.5.1.30,TCP-ESTATS-MIB::tcpEStatsStackAbruptTimeouts,Gauge32,read-only,,current,,The number of timeouts that occurred without any immediately preceding duplicate acknowledgments or other indications of congestion. Abrupt Timeouts indicate that the path lost an entire window of data or acknowledgments. Timeouts that are preceded by duplicate acknowledgments or other congestion signals (e.g., ECN) are not counted as abrupt, and might have been avoided by a more sophisticated Fast Retransmit algorithm.
.1.3.6.1.2.1.156.1.1.5.1.31,TCP-ESTATS-MIB::tcpEStatsStackSACKsRcvd,Gauge32,read-only,,current,,The number of SACK options received.
.1.3.6.1.2.1.156.1.1.5.1.32,TCP-ESTATS-MIB::tcpEStatsStackSACKBlocksRcvd,Gauge32,read-only,,current,,The number of SACK blocks received (within SACK options).
.1.3.6.1.2.1.156.1.1.5.1.33,TCP-ESTATS-MIB::tcpEStatsStackSendStall,Gauge32,read-only,,current,,The number of interface stalls or other sender local resource limitations that are treated as congestion signals.
.1.3.6.1.2.1.156.1.1.5.1.34,TCP-ESTATS-MIB::tcpEStatsStackDSACKDups,Gauge32,read-only,,current,,The number of duplicate segments reported to the local host by D-SACK blocks.
.1.3.6.1.2.1.156.1.1.5.1.35,TCP-ESTATS-MIB::tcpEStatsStackMaxMSS,Gauge32,read-only,,current,,The maximum MSS, in octets.
.1.3.6.1.2.1.156.1.1.5.1.36,TCP-ESTATS-MIB::tcpEStatsStackMinMSS,Gauge32,read-only,,current,,The minimum MSS, in octets.
.1.3.6.1.2.1.156.1.1.5.1.37,TCP-ESTATS-MIB::tcpEStatsStackSndInitial,Unsigned32,read-only,,current,,Initial send sequence number. Note that by definition tcpEStatsStackSndInitial never changes for a given connection.
.1.3.6.1.2.1.156.1.1.5.1.38,TCP-ESTATS-MIB::tcpEStatsStackRecInitial,Unsigned32,read-only,,current,,Initial receive sequence number. Note that by definition tcpEStatsStackRecInitial never changes for a given connection.
.1.3.6.1.2.1.156.1.1.5.1.39,TCP-ESTATS-MIB::tcpEStatsStackCurRetxQueue,Gauge32,read-only,,current,,The current number of octets of data occupying the retransmit queue.
.1.3.6.1.2.1.156.1.1.5.1.40,TCP-ESTATS-MIB::tcpEStatsStackMaxRetxQueue,Gauge32,read-only,,current,,The maximum number of octets of data occupying the retransmit queue.
.1.3.6.1.2.1.156.1.1.5.1.41,TCP-ESTATS-MIB::tcpEStatsStackCurReasmQueue,Gauge32,read-only,,current,,The current number of octets of sequence space spanned by the reassembly queue. This is generally the difference between rcv.nxt and the sequence number of the right most edge of the reassembly queue.
.1.3.6.1.2.1.156.1.1.5.1.42,TCP-ESTATS-MIB::tcpEStatsStackMaxReasmQueue,Gauge32,read-only,,current,,The maximum value of tcpEStatsStackCurReasmQueue
.1.3.6.1.2.1.156.1.1.6,TCP-ESTATS-MIB::tcpEStatsAppTable,,not-accessible,,current,,This table contains objects that are useful for determining if the application using TCP is limiting TCP performance. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
.1.3.6.1.2.1.156.1.1.6.1,TCP-ESTATS-MIB::tcpEStatsAppEntry,,not-accessible,tcpEStatsConnectIndex,current,,Each entry in this table has information about the characteristics of each active and recently closed TCP connection.
.1.3.6.1.2.1.156.1.1.6.1.1,TCP-ESTATS-MIB::tcpEStatsAppSndUna,Counter32,read-only,,current,,The value of SND.UNA, the oldest unacknowledged sequence number. Note that SND.UNA is a TCP state variable that is congruent to Counter32 semantics.
.1.3.6.1.2.1.156.1.1.6.1.2,TCP-ESTATS-MIB::tcpEStatsAppSndNxt,Unsigned32,read-only,,current,,The value of SND.NXT, the next sequence number to be sent. Note that tcpEStatsAppSndNxt is not monotonic (and thus not a counter) because TCP sometimes retransmits lost data by pulling tcpEStatsAppSndNxt back to the missing data.
.1.3.6.1.2.1.156.1.1.6.1.3,TCP-ESTATS-MIB::tcpEStatsAppSndMax,Counter32,read-only,,current,,The farthest forward (right most or largest) SND.NXT value. Note that this will be equal to tcpEStatsAppSndNxt except when tcpEStatsAppSndNxt is pulled back during recovery.
.1.3.6.1.2.1.156.1.1.6.1.4,TCP-ESTATS-MIB::tcpEStatsAppThruOctetsAcked,Gauge32,read-only,,current,,The number of octets for which cumulative acknowledgments have been received. Note that this will be the sum of changes to tcpEStatsAppSndUna.
.1.3.6.1.2.1.156.1.1.6.1.5,TCP-ESTATS-MIB::tcpEStatsAppHCThruOctetsAcked,Counter64,read-only,,current,,The number of octets for which cumulative acknowledgments have been received, on systems that can receive more than 10 million bits per second. Note that this will be the sum of changes in tcpEStatsAppSndUna.
.1.3.6.1.2.1.156.1.1.6.1.6,TCP-ESTATS-MIB::tcpEStatsAppRcvNxt,Counter32,read-only,,current,,The value of RCV.NXT. The next sequence number expected on an incoming segment, and the left or lower edge of the receive window. Note that RCV.NXT is a TCP state variable that is congruent to Counter32 semantics.
.1.3.6.1.2.1.156.1.1.6.1.7,TCP-ESTATS-MIB::tcpEStatsAppThruOctetsReceived,Gauge32,read-only,,current,,The number of octets for which cumulative acknowledgments have been sent. Note that this will be the sum of changes to tcpEStatsAppRcvNxt.
.1.3.6.1.2.1.156.1.1.6.1.8,TCP-ESTATS-MIB::tcpEStatsAppHCThruOctetsReceived,Counter64,read-only,,current,,The number of octets for which cumulative acknowledgments have been sent, on systems that can transmit more than 10 million bits per second. Note that this will be the sum of changes in tcpEStatsAppRcvNxt.
.1.3.6.1.2.1.156.1.1.6.1.11,TCP-ESTATS-MIB::tcpEStatsAppCurAppWQueue,Gauge32,read-only,,current,,The current number of octets of application data buffered by TCP, pending first transmission, i.e., to the left of SND.NXT or SndMax. This data will generally be transmitted (and SND.NXT advanced to the left) as soon as there is an available congestion window (cwnd) or receiver window (rwin). This is the amount of data readily available for transmission, without scheduling the application. TCP performance may suffer if there is insufficient queued write data.
.1.3.6.1.2.1.156.1.1.6.1.12,TCP-ESTATS-MIB::tcpEStatsAppMaxAppWQueue,Gauge32,read-only,,current,,The maximum number of octets of application data buffered by TCP, pending first transmission. This is the maximum value of tcpEStatsAppCurAppWQueue. This pair of objects can be used to determine if insufficient queued data is steady state (suggesting insufficient queue space) or transient (suggesting insufficient application performance or excessive CPU load or scheduler latency).
.1.3.6.1.2.1.156.1.1.6.1.13,TCP-ESTATS-MIB::tcpEStatsAppCurAppRQueue,Gauge32,read-only,,current,,The current number of octets of application data that has been acknowledged by TCP but not yet delivered to the application.
.1.3.6.1.2.1.156.1.1.6.1.14,TCP-ESTATS-MIB::tcpEStatsAppMaxAppRQueue,Gauge32,read-only,,current,,The maximum number of octets of application data that has been acknowledged by TCP but not yet delivered to the application.
.1.3.6.1.2.1.156.1.1.7,TCP-ESTATS-MIB::tcpEStatsTuneTable,,not-accessible,,current,,This table contains per-connection controls that can be used to work around a number of common problems that plague TCP over some paths. All can be characterized as limiting the growth of the congestion window so as to prevent TCP from overwhelming some component in the path. Entries are retained in this table for the number of seconds indicated by the tcpEStatsConnTableLatency object, after the TCP connection first enters the closed state.
.1.3.6.1.2.1.156.1.1.7.1,TCP-ESTATS-MIB::tcpEStatsTuneEntry,,not-accessible,tcpEStatsConnectIndex,current,,Each entry in this table is a control that can be used to place limits on each active TCP connection.
.1.3.6.1.2.1.156.1.1.7.1.1,TCP-ESTATS-MIB::tcpEStatsTuneLimCwnd,Unsigned32,read-write,,current,,A control to set the maximum congestion window that may be used, in octets.
.1.3.6.1.2.1.156.1.1.7.1.2,TCP-ESTATS-MIB::tcpEStatsTuneLimSsthresh,Unsigned32,read-write,,current,,A control to limit the maximum queue space (in octets) that this TCP connection is likely to occupy during slowstart. It can be implemented with the algorithm described in RFC 3742 by setting the max_ssthresh parameter to twice tcpEStatsTuneLimSsthresh. This algorithm can be used to overcome some TCP performance problems over network paths that do not have sufficient buffering to withstand the bursts normally present during slowstart.
.1.3.6.1.2.1.156.1.1.7.1.3,TCP-ESTATS-MIB::tcpEStatsTuneLimRwin,Unsigned32,read-write,,current,,A control to set the maximum window advertisement that may be sent, in octets.
.1.3.6.1.2.1.156.1.1.7.1.4,TCP-ESTATS-MIB::tcpEStatsTuneLimMSS,Unsigned32,read-write,,current,,A control to limit the maximum segment size in octets, that this TCP connection can use.
.1.3.6.1.2.1.156.1.2,TCP-ESTATS-MIB::tcpEStatsControl,,,,,,
.1.3.6.1.2.1.156.1.2.1,TCP-ESTATS-MIB::tcpEStatsControlPath,INTEGER,read-write,,current,true(1):false(2),Controls the activation of the TCP Path Statistics table. A value 'true' indicates that the TCP Path Statistics table is active, while 'false' indicates that the table is inactive.
.1.3.6.1.2.1.156.1.2.2,TCP-ESTATS-MIB::tcpEStatsControlStack,INTEGER,read-write,,current,true(1):false(2),Controls the activation of the TCP Stack Statistics table. A value 'true' indicates that the TCP Stack Statistics table is active, while 'false' indicates that the table is inactive.
.1.3.6.1.2.1.156.1.2.3,TCP-ESTATS-MIB::tcpEStatsControlApp,INTEGER,read-write,,current,true(1):false(2),Controls the activation of the TCP Application Statistics table. A value 'true' indicates that the TCP Application Statistics table is active, while 'false' indicates that the table is inactive.
.1.3.6.1.2.1.156.1.2.4,TCP-ESTATS-MIB::tcpEStatsControlTune,INTEGER,read-write,,current,true(1):false(2),Controls the activation of the TCP Tuning table. A value 'true' indicates that the TCP Tuning table is active, while 'false' indicates that the table is inactive.
.1.3.6.1.2.1.156.1.2.5,TCP-ESTATS-MIB::tcpEStatsControlNotify,INTEGER,read-write,,current,true(1):false(2),Controls the generation of all notifications defined in this MIB. A value 'true' indicates that the notifications are active, while 'false' indicates that the notifications are inactive.
.1.3.6.1.2.1.156.1.2.6,TCP-ESTATS-MIB::tcpEStatsConnTableLatency,Unsigned32,read-write,,current,,Specifies the number of seconds that the entity will retain entries in the TCP connection tables, after the connection first enters the closed state. The entity SHOULD provide a configuration option to enable customization of this value. A value of 0 results in entries being removed from the tables as soon as the connection enters the closed state. The value of this object pertains to the following tables: tcpEStatsConnectIdTable tcpEStatsPerfTable tcpEStatsPathTable tcpEStatsStackTable tcpEStatsAppTable tcpEStatsTuneTable
.1.3.6.1.2.1.156.1.3,TCP-ESTATS-MIB::tcpEStatsScalar,,,,,,
.1.3.6.1.2.1.156.1.3.3,TCP-ESTATS-MIB::tcpEStatsListenerTableLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last creation or deletion of an entry in the tcpListenerTable. If the number of entries has been unchanged since the last re-initialization of the local network management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.156.2,TCP-ESTATS-MIB::tcpEStatsConformance,,,,,,
.1.3.6.1.2.1.156.2.1,TCP-ESTATS-MIB::tcpEStatsCompliances,,,,,,
.1.3.6.1.2.1.156.2.1.1,TCP-ESTATS-MIB::tcpEStatsCompliance,,,,,,Compliance statement for all systems that implement TCP extended statistics.
.1.3.6.1.2.1.156.2.2,TCP-ESTATS-MIB::tcpEStatsGroups,,,,,,
.1.3.6.1.2.1.156.2.2.1,TCP-ESTATS-MIB::tcpEStatsListenerGroup,,,,,,The tcpEStatsListener group includes objects that provide valuable statistics and debugging information for TCP Listeners.
.1.3.6.1.2.1.156.2.2.2,TCP-ESTATS-MIB::tcpEStatsListenerHCGroup,,,,,,The tcpEStatsListenerHC group includes 64-bit counters in tcpEStatsListenerTable.
.1.3.6.1.2.1.156.2.2.3,TCP-ESTATS-MIB::tcpEStatsConnectIdGroup,,,,,,The tcpEStatsConnectId group includes objects that identify TCP connections and control how long TCP connection entries are retained in the tables.
.1.3.6.1.2.1.156.2.2.4,TCP-ESTATS-MIB::tcpEStatsPerfGroup,,,,,,The tcpEStatsPerf group includes those objects that provide basic performance data for a TCP connection.
.1.3.6.1.2.1.156.2.2.5,TCP-ESTATS-MIB::tcpEStatsPerfOptionalGroup,,,,,,The tcpEStatsPerf group includes those objects that provide basic performance data for a TCP connection.
.1.3.6.1.2.1.156.2.2.6,TCP-ESTATS-MIB::tcpEStatsPerfHCGroup,,,,,,The tcpEStatsPerfHC group includes 64-bit counters in the tcpEStatsPerfTable.
.1.3.6.1.2.1.156.2.2.7,TCP-ESTATS-MIB::tcpEStatsPathGroup,,,,,,The tcpEStatsPath group includes objects that control the creation of the tcpEStatsPathTable, and provide information about the path for each TCP connection.
.1.3.6.1.2.1.156.2.2.8,TCP-ESTATS-MIB::tcpEStatsPathOptionalGroup,,,,,,The tcpEStatsPath group includes objects that provide additional information about the path for each TCP connection.
.1.3.6.1.2.1.156.2.2.9,TCP-ESTATS-MIB::tcpEStatsPathHCGroup,,,,,,The tcpEStatsPathHC group includes 64-bit counters in the tcpEStatsPathTable.
.1.3.6.1.2.1.156.2.2.10,TCP-ESTATS-MIB::tcpEStatsStackGroup,,,,,,The tcpEStatsConnState group includes objects that control the creation of the tcpEStatsStackTable, and provide information about the operation of algorithms used within TCP.
.1.3.6.1.2.1.156.2.2.11,TCP-ESTATS-MIB::tcpEStatsStackOptionalGroup,,,,,,The tcpEStatsConnState group includes objects that provide additional information about the operation of algorithms used within TCP.
.1.3.6.1.2.1.156.2.2.12,TCP-ESTATS-MIB::tcpEStatsAppGroup,,,,,,The tcpEStatsConnState group includes objects that control the creation of the tcpEStatsAppTable, and provide information about the operation of algorithms used within TCP.
.1.3.6.1.2.1.156.2.2.13,TCP-ESTATS-MIB::tcpEStatsAppHCGroup,,,,,,The tcpEStatsStackHC group includes 64-bit counters in the tcpEStatsStackTable.
.1.3.6.1.2.1.156.2.2.14,TCP-ESTATS-MIB::tcpEStatsAppOptionalGroup,,,,,,The tcpEStatsConnState group includes objects that provide additional information about how applications are interacting with each TCP connection.
.1.3.6.1.2.1.156.2.2.15,TCP-ESTATS-MIB::tcpEStatsTuneOptionalGroup,,,,,,The tcpEStatsConnState group includes objects that control the creation of the tcpEStatsConnectionTable, which can be used to set tuning parameters for each TCP connection.
.1.3.6.1.2.1.156.2.2.16,TCP-ESTATS-MIB::tcpEStatsNotificationsGroup,,,,,,Notifications sent by a TCP extended statistics agent.
.1.3.6.1.2.1.156.2.2.17,TCP-ESTATS-MIB::tcpEStatsNotificationsCtlGroup,,,,,,The tcpEStatsNotificationsCtl group includes the object that controls the creation of the events in the tcpEStatsNotificationsGroup.
.1.3.6.1.2.1.157,PIM-STD-MIB::pimStdMIB,,,,,,The MIB module for management of PIM routers. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5060; see the RFC itself for full legal notices.
.1.3.6.1.2.1.157.0,PIM-STD-MIB::pimNotifications,,,,,,
.1.3.6.1.2.1.157.0.1,PIM-STD-MIB::pimNeighborLoss,,,,,,A pimNeighborLoss notification signifies the loss of an adjacency with a neighbor. This notification should be generated when the neighbor timer expires, and the router has no other neighbors on the same interface with the same IP version and a lower IP address than itself. This notification is generated whenever the counter pimNeighborLossCount is incremented, subject to the rate limit specified by pimNeighborLossNotificationPeriod.
.1.3.6.1.2.1.157.0.2,PIM-STD-MIB::pimInvalidRegister,,,,,,A pimInvalidRegister notification signifies that an invalid PIM Register message was received by this device. This notification is generated whenever the counter pimInvalidRegisterMsgsRcvd is incremented, subject to the rate limit specified by pimInvalidRegisterNotificationPeriod.
.1.3.6.1.2.1.157.0.3,PIM-STD-MIB::pimInvalidJoinPrune,,,,,,A pimInvalidJoinPrune notification signifies that an invalid PIM Join/Prune message was received by this device. This notification is generated whenever the counter pimInvalidJoinPruneMsgsRcvd is incremented, subject to the rate limit specified by pimInvalidJoinPruneNotificationPeriod.
.1.3.6.1.2.1.157.0.4,PIM-STD-MIB::pimRPMappingChange,,,,,,A pimRPMappingChange notification signifies a change to the active RP mapping on this device. This notification is generated whenever the counter pimRPMappingChangeCount is incremented, subject to the rate limit specified by pimRPMappingChangeNotificationPeriod.
.1.3.6.1.2.1.157.0.5,PIM-STD-MIB::pimInterfaceElection,,,,,,A pimInterfaceElection notification signifies that a new DR or DF has been elected on a network. This notification is generated whenever the counter pimInterfaceElectionWinCount is incremented, subject to the rate limit specified by pimInterfaceElectionNotificationPeriod.
.1.3.6.1.2.1.157.1,PIM-STD-MIB::pim,,,,,,
.1.3.6.1.2.1.157.1.1,PIM-STD-MIB::pimInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the router's PIM interfaces. PIM is enabled on all interfaces listed in this table.
.1.3.6.1.2.1.157.1.1.1,PIM-STD-MIB::pimInterfaceEntry,,not-accessible,pimInterfaceIfIndex:pimInterfaceIPVersion,current,,An entry (conceptual row) in the pimInterfaceTable. This entry is preserved on agent restart.
.1.3.6.1.2.1.157.1.1.1.1,PIM-STD-MIB::pimInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of this PIM interface.
.1.3.6.1.2.1.157.1.1.1.2,PIM-STD-MIB::pimInterfaceIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version of this PIM interface. A physical interface may be configured in multiple modes concurrently, e.g., IPv4 and IPv6; however, the traffic is considered to be logically separate.
.1.3.6.1.2.1.157.1.1.1.3,PIM-STD-MIB::pimInterfaceAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of this PIM interface.
.1.3.6.1.2.1.157.1.1.1.4,PIM-STD-MIB::pimInterfaceAddress,OCTET,read-only,,current,,The primary IP address of this router on this PIM interface. The InetAddressType is given by the pimInterfaceAddressType object.
.1.3.6.1.2.1.157.1.1.1.5,PIM-STD-MIB::pimInterfaceGenerationIDValue,Unsigned32,read-only,,current,,The value of the Generation ID this router inserted in the last PIM Hello message it sent on this interface.
.1.3.6.1.2.1.157.1.1.1.6,PIM-STD-MIB::pimInterfaceDR,OCTET,read-only,,current,,The primary IP address of the Designated Router on this PIM interface. The InetAddressType is given by the pimInterfaceAddressType object.
.1.3.6.1.2.1.157.1.1.1.7,PIM-STD-MIB::pimInterfaceDRPriority,Unsigned32,read-create,,current,,The Designated Router Priority value inserted into the DR Priority option in PIM Hello messages transmitted on this interface. Numerically higher values for this object indicate higher priorities.
.1.3.6.1.2.1.157.1.1.1.8,PIM-STD-MIB::pimInterfaceDRPriorityEnabled,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if all routers on this interface are using the DR Priority option.
.1.3.6.1.2.1.157.1.1.1.9,PIM-STD-MIB::pimInterfaceHelloInterval,Unsigned32,read-create,,current,,The frequency at which PIM Hello messages are transmitted on this interface. This object corresponds to the 'Hello_Period' timer value defined in the PIM-SM specification. A value of zero represents an 'infinite' interval, and indicates that periodic PIM Hello messages should not be sent on this interface.
.1.3.6.1.2.1.157.1.1.1.10,PIM-STD-MIB::pimInterfaceTrigHelloInterval,Unsigned32,read-create,,current,,The maximum time before this router sends a triggered PIM Hello message on this interface. This object corresponds to the 'Trigered_Hello_Delay' timer value defined in the PIM-SM specification. A value of zero has no special meaning and indicates that triggered PIM Hello messages should always be sent immediately.
.1.3.6.1.2.1.157.1.1.1.11,PIM-STD-MIB::pimInterfaceHelloHoldtime,Unsigned32,read-create,,current,,The value set in the Holdtime field of PIM Hello messages transmitted on this interface. A value of 65535 represents an 'infinite' holdtime. Implementations are recommended to use a holdtime that is 3.5 times the value of pimInterfaceHelloInterval, or 65535 if pimInterfaceHelloInterval is set to zero.
.1.3.6.1.2.1.157.1.1.1.12,PIM-STD-MIB::pimInterfaceJoinPruneInterval,Unsigned32,read-create,,current,,The frequency at which this router sends PIM Join/Prune messages on this PIM interface. This object corresponds to the 't_periodic' timer value defined in the PIM-SM specification. A value of zero represents an 'infinite' interval, and indicates that periodic PIM Join/Prune messages should not be sent on this interface.
.1.3.6.1.2.1.157.1.1.1.13,PIM-STD-MIB::pimInterfaceJoinPruneHoldtime,Unsigned32,read-create,,current,,The value inserted into the Holdtime field of a PIM Join/Prune message sent on this interface. A value of 65535 represents an 'infinite' holdtime. Implementations are recommended to use a holdtime that is 3.5 times the value of pimInterfaceJoinPruneInterval, or 65535 if pimInterfaceJoinPruneInterval is set to zero. PIM-DM implementations are recommended to use the value of pimInterfacePruneLimitInterval.
.1.3.6.1.2.1.157.1.1.1.14,PIM-STD-MIB::pimInterfaceDFElectionRobustness,Unsigned32,read-create,,current,,The minimum number of PIM DF-Election messages that must be lost in order for DF election on this interface to fail.
.1.3.6.1.2.1.157.1.1.1.15,PIM-STD-MIB::pimInterfaceLanDelayEnabled,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if all routers on this interface are using the LAN Prune Delay option.
.1.3.6.1.2.1.157.1.1.1.16,PIM-STD-MIB::pimInterfacePropagationDelay,Unsigned32,read-create,,current,,The expected propagation delay between PIM routers on this network or link. This router inserts this value into the Propagation_Delay field of the LAN Prune Delay option in the PIM Hello messages sent on this interface. Implementations SHOULD enforce a lower bound on the permitted values for this object to allow for scheduling and processing delays within the local router.
.1.3.6.1.2.1.157.1.1.1.17,PIM-STD-MIB::pimInterfaceOverrideInterval,Unsigned32,read-create,,current,,The value this router inserts into the Override_Interval field of the LAN Prune Delay option in the PIM Hello messages it sends on this interface. When overriding a prune, PIM routers pick a random timer duration up to the value of this object. The more PIM routers that are active on a network, the more likely it is that the prune will be overridden after a small proportion of this time has elapsed. The more PIM routers are active on this network, the larger this object should be to obtain an optimal spread of prune override latencies.
.1.3.6.1.2.1.157.1.1.1.18,PIM-STD-MIB::pimInterfaceEffectPropagDelay,Unsigned32,read-only,,current,,The Effective Propagation Delay on this interface. This object is always 500 if pimInterfaceLanDelayEnabled is FALSE.
.1.3.6.1.2.1.157.1.1.1.19,PIM-STD-MIB::pimInterfaceEffectOverrideIvl,Unsigned32,read-only,,current,,The Effective Override Interval on this interface. This object is always 2500 if pimInterfaceLanDelayEnabled is FALSE.
.1.3.6.1.2.1.157.1.1.1.20,PIM-STD-MIB::pimInterfaceSuppressionEnabled,INTEGER,read-only,,current,true(1):false(2),Whether join suppression is enabled on this interface. This object is always TRUE if pimInterfaceLanDelayEnabled is FALSE.
.1.3.6.1.2.1.157.1.1.1.21,PIM-STD-MIB::pimInterfaceBidirCapable,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if all routers on this interface are using the Bidirectional-PIM Capable option.
.1.3.6.1.2.1.157.1.1.1.22,PIM-STD-MIB::pimInterfaceDomainBorder,INTEGER,read-create,,current,true(1):false(2),Whether or not this interface is a PIM domain border. This includes acting as a border for PIM Bootstrap Router (BSR) messages, if the BSR mechanism is in use.
.1.3.6.1.2.1.157.1.1.1.23,PIM-STD-MIB::pimInterfaceStubInterface,INTEGER,read-create,,current,true(1):false(2),Whether this interface is a 'stub interface'. If this object is set to TRUE, then no PIM packets are sent out this interface, and any received PIM packets are ignored. Setting this object to TRUE is a security measure for interfaces towards untrusted hosts. This allows an interface to be configured for use with IGMP (Internet Group Management Protocol) or MLD (Multicast Listener Discovery) only, which protects the PIM router from forged PIM messages on the interface. To communicate with other PIM routers using this interface, this object must remain set to FALSE. Changing the value of this object while the interface is operational causes PIM to be disabled and then re-enabled on this interface.
.1.3.6.1.2.1.157.1.1.1.24,PIM-STD-MIB::pimInterfacePruneLimitInterval,Unsigned32,read-create,,current,,The minimum interval that must transpire between two successive Prunes sent by a router. This object corresponds to the 't_limit' timer value defined in the PIM-DM specification. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.1.1.25,PIM-STD-MIB::pimInterfaceGraftRetryInterval,Unsigned32,read-create,,current,,The minimum interval that must transpire between two successive Grafts sent by a router. This object corresponds to the 'Graft_Retry_Period' timer value defined in the PIM-DM specification. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.1.1.26,PIM-STD-MIB::pimInterfaceSRPriorityEnabled,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if all routers on this interface are using the State Refresh option. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.1.1.27,PIM-STD-MIB::pimInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry. Creating the entry enables PIM on the interface; destroying the entry disables PIM on the interface. This status object can be set to active(1) without setting any other columnar objects in this entry. All writeable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.157.1.1.1.28,PIM-STD-MIB::pimInterfaceStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.157.1.2,PIM-STD-MIB::pimNeighborTable,,not-accessible,,current,,The (conceptual) table listing the router's PIM neighbors.
.1.3.6.1.2.1.157.1.2.1,PIM-STD-MIB::pimNeighborEntry,,not-accessible,pimNeighborIfIndex:pimNeighborAddressType:pimNeighborAddress,current,,An entry (conceptual row) in the pimNeighborTable.
.1.3.6.1.2.1.157.1.2.1.1,PIM-STD-MIB::pimNeighborIfIndex,Integer32,not-accessible,,current,,The value of ifIndex for the interface used to reach this PIM neighbor.
.1.3.6.1.2.1.157.1.2.1.2,PIM-STD-MIB::pimNeighborAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of this PIM neighbor.
.1.3.6.1.2.1.157.1.2.1.3,PIM-STD-MIB::pimNeighborAddress,OCTET,not-accessible,,current,,The primary IP address of this PIM neighbor. The InetAddressType is given by the pimNeighborAddressType object.
.1.3.6.1.2.1.157.1.2.1.4,PIM-STD-MIB::pimNeighborGenerationIDPresent,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if this neighbor is using the Generation ID option.
.1.3.6.1.2.1.157.1.2.1.5,PIM-STD-MIB::pimNeighborGenerationIDValue,Unsigned32,read-only,,current,,The value of the Generation ID from the last PIM Hello message received from this neighbor. This object is always zero if pimNeighborGenerationIDPresent is FALSE.
.1.3.6.1.2.1.157.1.2.1.6,PIM-STD-MIB::pimNeighborUpTime,TimeTicks,read-only,,current,,The time since this PIM neighbor (last) became a neighbor of the local router.
.1.3.6.1.2.1.157.1.2.1.7,PIM-STD-MIB::pimNeighborExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before this PIM neighbor will time out. The value zero indicates that this PIM neighbor will never time out.
.1.3.6.1.2.1.157.1.2.1.8,PIM-STD-MIB::pimNeighborDRPriorityPresent,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if this neighbor is using the DR Priority option.
.1.3.6.1.2.1.157.1.2.1.9,PIM-STD-MIB::pimNeighborDRPriority,Unsigned32,read-only,,current,,The value of the Designated Router Priority from the last PIM Hello message received from this neighbor. This object is always zero if pimNeighborDRPriorityPresent is FALSE.
.1.3.6.1.2.1.157.1.2.1.10,PIM-STD-MIB::pimNeighborLanPruneDelayPresent,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if this neighbor is using the LAN Prune Delay option.
.1.3.6.1.2.1.157.1.2.1.11,PIM-STD-MIB::pimNeighborTBit,INTEGER,read-only,,current,true(1):false(2),Whether the T bit was set in the LAN Prune Delay option received from this neighbor. The T bit specifies the ability of the neighbor to disable join suppression. This object is always TRUE if pimNeighborLanPruneDelayPresent is FALSE.
.1.3.6.1.2.1.157.1.2.1.12,PIM-STD-MIB::pimNeighborPropagationDelay,Unsigned32,read-only,,current,,The value of the Propagation_Delay field of the LAN Prune Delay option received from this neighbor. This object is always zero if pimNeighborLanPruneDelayPresent is FALSE.
.1.3.6.1.2.1.157.1.2.1.13,PIM-STD-MIB::pimNeighborOverrideInterval,Unsigned32,read-only,,current,,The value of the Override_Interval field of the LAN Prune Delay option received from this neighbor. This object is always zero if pimNeighborLanPruneDelayPresent is FALSE.
.1.3.6.1.2.1.157.1.2.1.14,PIM-STD-MIB::pimNeighborBidirCapable,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if this neighbor is using the Bidirectional-PIM Capable option.
.1.3.6.1.2.1.157.1.2.1.15,PIM-STD-MIB::pimNeighborSRCapable,INTEGER,read-only,,current,true(1):false(2),Evaluates to TRUE if this neighbor is using the State Refresh Capable option. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.3,PIM-STD-MIB::pimNbrSecAddressTable,,not-accessible,,current,,The (conceptual) table listing the secondary addresses advertised by each PIM neighbor (on a subset of the rows of the pimNeighborTable defined above).
.1.3.6.1.2.1.157.1.3.1,PIM-STD-MIB::pimNbrSecAddressEntry,,not-accessible,pimNbrSecAddressIfIndex:pimNbrSecAddressType:pimNbrSecAddressPrimary:pimNbrSecAddress,current,,An entry (conceptual row) in the pimNbrSecAddressTable.
.1.3.6.1.2.1.157.1.3.1.1,PIM-STD-MIB::pimNbrSecAddressIfIndex,Integer32,not-accessible,,current,,The value of ifIndex for the interface used to reach this PIM neighbor.
.1.3.6.1.2.1.157.1.3.1.2,PIM-STD-MIB::pimNbrSecAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of this PIM neighbor.
.1.3.6.1.2.1.157.1.3.1.3,PIM-STD-MIB::pimNbrSecAddressPrimary,OCTET,not-accessible,,current,,The primary IP address of this PIM neighbor. The InetAddressType is given by the pimNbrSecAddressType object.
.1.3.6.1.2.1.157.1.3.1.4,PIM-STD-MIB::pimNbrSecAddress,OCTET,read-only,,current,,The secondary IP address of this PIM neighbor. The InetAddressType is given by the pimNbrSecAddressType object.
.1.3.6.1.2.1.157.1.4,PIM-STD-MIB::pimStarGTable,,not-accessible,,current,,The (conceptual) table listing the non-interface specific (*,G) state that PIM has.
.1.3.6.1.2.1.157.1.4.1,PIM-STD-MIB::pimStarGEntry,,not-accessible,pimStarGAddressType:pimStarGGrpAddress,current,,An entry (conceptual row) in the pimStarGTable.
.1.3.6.1.2.1.157.1.4.1.1,PIM-STD-MIB::pimStarGAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of this multicast group.
.1.3.6.1.2.1.157.1.4.1.2,PIM-STD-MIB::pimStarGGrpAddress,OCTET,not-accessible,,current,,The multicast group address. The InetAddressType is given by the pimStarGAddressType object.
.1.3.6.1.2.1.157.1.4.1.3,PIM-STD-MIB::pimStarGUpTime,TimeTicks,read-only,,current,,The time since this entry was created by the local router.
.1.3.6.1.2.1.157.1.4.1.4,PIM-STD-MIB::pimStarGPimMode,INTEGER,read-only,,current,asm(3):bidir(4),Whether this entry represents an ASM (Any Source Multicast, used with PIM-SM) or BIDIR-PIM group.
.1.3.6.1.2.1.157.1.4.1.5,PIM-STD-MIB::pimStarGRPAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the Rendezvous Point (RP), or unknown(0) if the RP address is unknown.
.1.3.6.1.2.1.157.1.4.1.6,PIM-STD-MIB::pimStarGRPAddress,OCTET,read-only,,current,,The address of the Rendezvous Point (RP) for the group. The InetAddressType is given by the pimStarGRPAddressType.
.1.3.6.1.2.1.157.1.4.1.7,PIM-STD-MIB::pimStarGPimModeOrigin,INTEGER,read-only,,current,fixed(1):configRp(2):configSsm(3):bsr(4):autoRP(5):embedded(6):other(7),The mechanism by which the PIM mode and RP for the group were learned.
.1.3.6.1.2.1.157.1.4.1.8,PIM-STD-MIB::pimStarGRPIsLocal,INTEGER,read-only,,current,true(1):false(2),Whether the local router is the RP for the group.
.1.3.6.1.2.1.157.1.4.1.9,PIM-STD-MIB::pimStarGUpstreamJoinState,INTEGER,read-only,,current,notJoined(1):joined(2),Whether the local router should join the RP tree for the group. This corresponds to the state of the upstream (*,G) state machine in the PIM-SM specification.
.1.3.6.1.2.1.157.1.4.1.10,PIM-STD-MIB::pimStarGUpstreamJoinTimer,TimeTicks,read-only,,current,,The time remaining before the local router next sends a periodic (*,G) Join message on pimStarGRPFIfIndex. This timer is called the (*,G) Upstream Join Timer in the PIM-SM specification. This object is zero if the timer is not running.
.1.3.6.1.2.1.157.1.4.1.11,PIM-STD-MIB::pimStarGUpstreamNeighborType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The primary address type of the upstream neighbor, or unknown(0) if the upstream neighbor address is unknown or is not a PIM neighbor.
.1.3.6.1.2.1.157.1.4.1.12,PIM-STD-MIB::pimStarGUpstreamNeighbor,OCTET,read-only,,current,,The primary address of the neighbor on pimStarGRPFIfIndex that the local router is sending periodic (*,G) Join messages to. The InetAddressType is given by the pimStarGUpstreamNeighborType object. This address is called RPF'(*,G) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.4.1.13,PIM-STD-MIB::pimStarGRPFIfIndex,Integer32,read-only,,current,,The value of ifIndex for the Reverse Path Forwarding (RPF) interface towards the RP, or zero if the RPF interface is unknown.
.1.3.6.1.2.1.157.1.4.1.14,PIM-STD-MIB::pimStarGRPFNextHopType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the RPF next hop towards the RP, or unknown(0) if the RPF next hop is unknown.
.1.3.6.1.2.1.157.1.4.1.15,PIM-STD-MIB::pimStarGRPFNextHop,OCTET,read-only,,current,,The address of the RPF next hop towards the RP. The InetAddressType is given by the pimStarGRPFNextHopType object. This address is called MRIB.next_hop(RP(G)) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.4.1.16,PIM-STD-MIB::pimStarGRPFRouteProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing mechanism via which the route used to find the RPF interface towards the RP was learned.
.1.3.6.1.2.1.157.1.4.1.17,PIM-STD-MIB::pimStarGRPFRouteAddress,OCTET,read-only,,current,,The IP address that, when combined with the corresponding value of pimStarGRPFRoutePrefixLength, identifies the route used to find the RPF interface towards the RP. The InetAddressType is given by the pimStarGRPFNextHopType object. This address object is only significant up to pimStarGRPFRoutePrefixLength bits. The remainder of the address bits are zero.
.1.3.6.1.2.1.157.1.4.1.18,PIM-STD-MIB::pimStarGRPFRoutePrefixLength,Unsigned32,read-only,,current,,The prefix length that, when combined with the corresponding value of pimStarGRPFRouteAddress, identifies the route used to find the RPF interface towards the RP. The InetAddressType is given by the pimStarGRPFNextHopType object.
.1.3.6.1.2.1.157.1.4.1.19,PIM-STD-MIB::pimStarGRPFRouteMetricPref,Unsigned32,read-only,,current,,The metric preference of the route used to find the RPF interface towards the RP.
.1.3.6.1.2.1.157.1.4.1.20,PIM-STD-MIB::pimStarGRPFRouteMetric,Unsigned32,read-only,,current,,The routing metric of the route used to find the RPF interface towards the RP.
.1.3.6.1.2.1.157.1.5,PIM-STD-MIB::pimStarGITable,,not-accessible,,current,,The (conceptual) table listing the interface-specific (*,G) state that PIM has.
.1.3.6.1.2.1.157.1.5.1,PIM-STD-MIB::pimStarGIEntry,,not-accessible,pimStarGAddressType:pimStarGGrpAddress:pimStarGIIfIndex,current,,An entry (conceptual row) in the pimStarGITable.
.1.3.6.1.2.1.157.1.5.1.1,PIM-STD-MIB::pimStarGIIfIndex,Integer32,not-accessible,,current,,The ifIndex of the interface that this entry corresponds to.
.1.3.6.1.2.1.157.1.5.1.2,PIM-STD-MIB::pimStarGIUpTime,TimeTicks,read-only,,current,,The time since this entry was created by the local router.
.1.3.6.1.2.1.157.1.5.1.3,PIM-STD-MIB::pimStarGILocalMembership,INTEGER,read-only,,current,true(1):false(2),Whether the local router has (*,G) local membership on this interface (resulting from a mechanism such as IGMP or MLD). This corresponds to local_receiver_include(*,G,I) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.5.1.4,PIM-STD-MIB::pimStarGIJoinPruneState,INTEGER,read-only,,current,noInfo(1):join(2):prunePending(3),The state resulting from (*,G) Join/Prune messages received on this interface. This corresponds to the state of the downstream per-interface (*,G) state machine in the PIM-SM specification.
.1.3.6.1.2.1.157.1.5.1.5,PIM-STD-MIB::pimStarGIPrunePendingTimer,TimeTicks,read-only,,current,,The time remaining before the local router acts on a (*,G) Prune message received on this interface, during which the router is waiting to see whether another downstream router will override the Prune message. This timer is called the (*,G) Prune-Pending Timer in the PIM-SM specification. This object is zero if the timer is not running.
.1.3.6.1.2.1.157.1.5.1.6,PIM-STD-MIB::pimStarGIJoinExpiryTimer,TimeTicks,read-only,,current,,The time remaining before (*,G) Join state for this interface expires. This timer is called the (*,G) Join Expiry Timer in the PIM-SM specification. This object is zero if the timer is not running. A value of 'FFFFFFFF'h indicates an infinite expiry time.
.1.3.6.1.2.1.157.1.5.1.7,PIM-STD-MIB::pimStarGIAssertState,INTEGER,read-only,,current,noInfo(1):iAmAssertWinner(2):iAmAssertLoser(3),The (*,G) Assert state for this interface. This corresponds to the state of the per-interface (*,G) Assert state machine in the PIM-SM specification. If pimStarGPimMode is 'bidir', this object must be 'noInfo'.
.1.3.6.1.2.1.157.1.5.1.8,PIM-STD-MIB::pimStarGIAssertTimer,TimeTicks,read-only,,current,,If pimStarGIAssertState is 'iAmAssertWinner', this is the time remaining before the local router next sends a (*,G) Assert message on this interface. If pimStarGIAssertState is 'iAmAssertLoser', this is the time remaining before the (*,G) Assert state expires. If pimStarGIAssertState is 'noInfo', this is zero. This timer is called the (*,G) Assert Timer in the PIM-SM specification.
.1.3.6.1.2.1.157.1.5.1.9,PIM-STD-MIB::pimStarGIAssertWinnerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),If pimStarGIAssertState is 'iAmAssertLoser', this is the address type of the assert winner; otherwise, this object is unknown(0).
.1.3.6.1.2.1.157.1.5.1.10,PIM-STD-MIB::pimStarGIAssertWinnerAddress,OCTET,read-only,,current,,If pimStarGIAssertState is 'iAmAssertLoser', this is the address of the assert winner. The InetAddressType is given by the pimStarGIAssertWinnerAddressType object.
.1.3.6.1.2.1.157.1.5.1.11,PIM-STD-MIB::pimStarGIAssertWinnerMetricPref,Unsigned32,read-only,,current,,If pimStarGIAssertState is 'iAmAssertLoser', this is the metric preference of the route to the RP advertised by the assert winner; otherwise, this object is zero.
.1.3.6.1.2.1.157.1.5.1.12,PIM-STD-MIB::pimStarGIAssertWinnerMetric,Unsigned32,read-only,,current,,If pimStarGIAssertState is 'iAmAssertLoser', this is the routing metric of the route to the RP advertised by the assert winner; otherwise, this object is zero.
.1.3.6.1.2.1.157.1.6,PIM-STD-MIB::pimSGTable,,not-accessible,,current,,The (conceptual) table listing the non-interface specific (S,G) state that PIM has.
.1.3.6.1.2.1.157.1.6.1,PIM-STD-MIB::pimSGEntry,,not-accessible,pimSGAddressType:pimSGGrpAddress:pimSGSrcAddress,current,,An entry (conceptual row) in the pimSGTable.
.1.3.6.1.2.1.157.1.6.1.1,PIM-STD-MIB::pimSGAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the source and multicast group for this entry.
.1.3.6.1.2.1.157.1.6.1.2,PIM-STD-MIB::pimSGGrpAddress,OCTET,not-accessible,,current,,The multicast group address for this entry. The InetAddressType is given by the pimSGAddressType object.
.1.3.6.1.2.1.157.1.6.1.3,PIM-STD-MIB::pimSGSrcAddress,OCTET,not-accessible,,current,,The source address for this entry. The InetAddressType is given by the pimSGAddressType object.
.1.3.6.1.2.1.157.1.6.1.4,PIM-STD-MIB::pimSGUpTime,TimeTicks,read-only,,current,,The time since this entry was created by the local router.
.1.3.6.1.2.1.157.1.6.1.5,PIM-STD-MIB::pimSGPimMode,INTEGER,read-only,,current,ssm(2):asm(3),Whether pimSGGrpAddress is an SSM (Source Specific Multicast, used with PIM-SM) or ASM (Any Source Multicast, used with PIM-SM) group.
.1.3.6.1.2.1.157.1.6.1.6,PIM-STD-MIB::pimSGUpstreamJoinState,INTEGER,read-only,,current,notJoined(1):joined(2),Whether the local router should join the shortest-path tree for the source and group represented by this entry. This corresponds to the state of the upstream (S,G) state machine in the PIM-SM specification.
.1.3.6.1.2.1.157.1.6.1.7,PIM-STD-MIB::pimSGUpstreamJoinTimer,TimeTicks,read-only,,current,,The time remaining before the local router next sends a periodic (S,G) Join message on pimSGRPFIfIndex. This timer is called the (S,G) Upstream Join Timer in the PIM-SM specification. This object is zero if the timer is not running.
.1.3.6.1.2.1.157.1.6.1.8,PIM-STD-MIB::pimSGUpstreamNeighbor,OCTET,read-only,,current,,The primary address of the neighbor on pimSGRPFIfIndex that the local router is sending periodic (S,G) Join messages to. This is zero if the RPF next hop is unknown or is not a PIM neighbor. The InetAddressType is given by the pimSGAddressType object. This address is called RPF'(S,G) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.6.1.9,PIM-STD-MIB::pimSGRPFIfIndex,Integer32,read-only,,current,,The value of ifIndex for the RPF interface towards the source, or zero if the RPF interface is unknown.
.1.3.6.1.2.1.157.1.6.1.10,PIM-STD-MIB::pimSGRPFNextHopType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the RPF next hop towards the source, or unknown(0) if the RPF next hop is unknown.
.1.3.6.1.2.1.157.1.6.1.11,PIM-STD-MIB::pimSGRPFNextHop,OCTET,read-only,,current,,The address of the RPF next hop towards the source. The InetAddressType is given by the pimSGRPFNextHopType. This address is called MRIB.next_hop(S) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.6.1.12,PIM-STD-MIB::pimSGRPFRouteProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing mechanism via which the route used to find the RPF interface towards the source was learned.
.1.3.6.1.2.1.157.1.6.1.13,PIM-STD-MIB::pimSGRPFRouteAddress,OCTET,read-only,,current,,The IP address that, when combined with the corresponding value of pimSGRPFRoutePrefixLength, identifies the route used to find the RPF interface towards the source. The InetAddressType is given by the pimSGRPFNextHopType object. This address object is only significant up to pimSGRPFRoutePrefixLength bits. The remainder of the address bits are zero.
.1.3.6.1.2.1.157.1.6.1.14,PIM-STD-MIB::pimSGRPFRoutePrefixLength,Unsigned32,read-only,,current,,The prefix length that, when combined with the corresponding value of pimSGRPFRouteAddress, identifies the route used to find the RPF interface towards the source. The InetAddressType is given by the pimSGRPFNextHopType object.
.1.3.6.1.2.1.157.1.6.1.15,PIM-STD-MIB::pimSGRPFRouteMetricPref,Unsigned32,read-only,,current,,The metric preference of the route used to find the RPF interface towards the source.
.1.3.6.1.2.1.157.1.6.1.16,PIM-STD-MIB::pimSGRPFRouteMetric,Unsigned32,read-only,,current,,The routing metric of the route used to find the RPF interface towards the source.
.1.3.6.1.2.1.157.1.6.1.17,PIM-STD-MIB::pimSGSPTBit,INTEGER,read-only,,current,true(1):false(2),Whether the SPT bit is set; and therefore whether forwarding is taking place on the shortest-path tree.
.1.3.6.1.2.1.157.1.6.1.18,PIM-STD-MIB::pimSGKeepaliveTimer,TimeTicks,read-only,,current,,The time remaining before this (S,G) state expires, in the absence of explicit (S,G) local membership or (S,G) Join messages received to maintain it. This timer is called the (S,G) Keepalive Timer in the PIM-SM specification.
.1.3.6.1.2.1.157.1.6.1.19,PIM-STD-MIB::pimSGDRRegisterState,INTEGER,read-only,,current,noInfo(1):join(2):joinPending(3):prune(4),Whether the local router should encapsulate (S,G) data packets in Register messages and send them to the RP. This corresponds to the state of the per-(S,G) Register state machine in the PIM-SM specification. This object is always 'noInfo' unless pimSGPimMode is 'asm'.
.1.3.6.1.2.1.157.1.6.1.20,PIM-STD-MIB::pimSGDRRegisterStopTimer,TimeTicks,read-only,,current,,If pimSGDRRegisterState is 'prune', this is the time remaining before the local router sends a Null-Register message to the RP. If pimSGDRRegisterState is 'joinPending', this is the time remaining before the local router resumes encapsulating data packets and sending them to the RP. Otherwise, this is zero. This timer is called the Register-Stop Timer in the PIM-SM specification.
.1.3.6.1.2.1.157.1.6.1.21,PIM-STD-MIB::pimSGRPRegisterPMBRAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the first PIM Multicast Border Router to send a Register message with the Border bit set. This object is unknown(0) if the local router is not the RP for the group.
.1.3.6.1.2.1.157.1.6.1.22,PIM-STD-MIB::pimSGRPRegisterPMBRAddress,OCTET,read-only,,current,,The IP address of the first PIM Multicast Border Router to send a Register message with the Border bit set. The InetAddressType is given by the pimSGRPRegisterPMBRAddressType object.
.1.3.6.1.2.1.157.1.6.1.23,PIM-STD-MIB::pimSGUpstreamPruneState,INTEGER,read-only,,current,forwarding(1):ackpending(2):pruned(3),Whether the local router has pruned itself from the tree. This corresponds to the state of the upstream prune (S,G) state machine in the PIM-DM specification. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.6.1.24,PIM-STD-MIB::pimSGUpstreamPruneLimitTimer,TimeTicks,read-only,,current,,The time remaining before the local router may send a (S,G) Prune message on pimSGRPFIfIndex. This timer is called the (S,G) Prune Limit Timer in the PIM-DM specification. This object is zero if the timer is not running. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.6.1.25,PIM-STD-MIB::pimSGOriginatorState,INTEGER,read-only,,current,notOriginator(1):originator(2),Whether the router is an originator for an (S,G) message flow. This corresponds to the state of the per-(S,G) Originator state machine in the PIM-DM specification. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.6.1.26,PIM-STD-MIB::pimSGSourceActiveTimer,TimeTicks,read-only,,current,,If pimSGOriginatorState is 'originator', this is the time remaining before the local router reverts to a notOriginator state. Otherwise, this is zero. This timer is called the Source Active Timer in the PIM-DM specification. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.6.1.27,PIM-STD-MIB::pimSGStateRefreshTimer,TimeTicks,read-only,,current,,If pimSGOriginatorState is 'originator', this is the time remaining before the local router sends a State Refresh message. Otherwise, this is zero. This timer is called the State Refresh Timer in the PIM-DM specification. This object is used only by PIM-DM.
.1.3.6.1.2.1.157.1.7,PIM-STD-MIB::pimSGITable,,not-accessible,,current,,The (conceptual) table listing the interface-specific (S,G) state that PIM has.
.1.3.6.1.2.1.157.1.7.1,PIM-STD-MIB::pimSGIEntry,,not-accessible,pimSGAddressType:pimSGGrpAddress:pimSGSrcAddress:pimSGIIfIndex,current,,An entry (conceptual row) in the pimSGITable.
.1.3.6.1.2.1.157.1.7.1.1,PIM-STD-MIB::pimSGIIfIndex,Integer32,not-accessible,,current,,The ifIndex of the interface that this entry corresponds to.
.1.3.6.1.2.1.157.1.7.1.2,PIM-STD-MIB::pimSGIUpTime,TimeTicks,read-only,,current,,The time since this entry was created by the local router.
.1.3.6.1.2.1.157.1.7.1.3,PIM-STD-MIB::pimSGILocalMembership,INTEGER,read-only,,current,true(1):false(2),Whether the local router has (S,G) local membership on this interface (resulting from a mechanism such as IGMP or MLD). This corresponds to local_receiver_include(S,G,I) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.7.1.4,PIM-STD-MIB::pimSGIJoinPruneState,INTEGER,read-only,,current,noInfo(1):join(2):prunePending(3),The state resulting from (S,G) Join/Prune messages received on this interface. This corresponds to the state of the downstream per-interface (S,G) state machine in the PIM-SM and PIM-DM specification.
.1.3.6.1.2.1.157.1.7.1.5,PIM-STD-MIB::pimSGIPrunePendingTimer,TimeTicks,read-only,,current,,The time remaining before the local router acts on an (S,G) Prune message received on this interface, during which the router is waiting to see whether another downstream router will override the Prune message. This timer is called the (S,G) Prune-Pending Timer in the PIM-SM specification. This object is zero if the timer is not running.
.1.3.6.1.2.1.157.1.7.1.6,PIM-STD-MIB::pimSGIJoinExpiryTimer,TimeTicks,read-only,,current,,The time remaining before (S,G) Join state for this interface expires. This timer is called the (S,G) Join Expiry Timer in the PIM-SM specification. This object is zero if the timer is not running. A value of 'FFFFFFFF'h indicates an infinite expiry time. This timer is called the (S,G) Prune Timer in the PIM-DM specification.
.1.3.6.1.2.1.157.1.7.1.7,PIM-STD-MIB::pimSGIAssertState,INTEGER,read-only,,current,noInfo(1):iAmAssertWinner(2):iAmAssertLoser(3),The (S,G) Assert state for this interface. This corresponds to the state of the per-interface (S,G) Assert state machine in the PIM-SM specification.
.1.3.6.1.2.1.157.1.7.1.8,PIM-STD-MIB::pimSGIAssertTimer,TimeTicks,read-only,,current,,If pimSGIAssertState is 'iAmAssertWinner', this is the time remaining before the local router next sends a (S,G) Assert message on this interface. If pimSGIAssertState is 'iAmAssertLoser', this is the time remaining before the (S,G) Assert state expires. If pimSGIAssertState is 'noInfo', this is zero. This timer is called the (S,G) Assert Timer in the PIM-SM specification.
.1.3.6.1.2.1.157.1.7.1.9,PIM-STD-MIB::pimSGIAssertWinnerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),If pimSGIAssertState is 'iAmAssertLoser', this is the address type of the assert winner; otherwise, this object is unknown(0).
.1.3.6.1.2.1.157.1.7.1.10,PIM-STD-MIB::pimSGIAssertWinnerAddress,OCTET,read-only,,current,,If pimSGIAssertState is 'iAmAssertLoser', this is the address of the assert winner. The InetAddressType is given by the pimSGIAssertWinnerAddressType object.
.1.3.6.1.2.1.157.1.7.1.11,PIM-STD-MIB::pimSGIAssertWinnerMetricPref,Unsigned32,read-only,,current,,If pimSGIAssertState is 'iAmAssertLoser', this is the metric preference of the route to the source advertised by the assert winner; otherwise, this object is zero.
.1.3.6.1.2.1.157.1.7.1.12,PIM-STD-MIB::pimSGIAssertWinnerMetric,Unsigned32,read-only,,current,,If pimSGIAssertState is 'iAmAssertLoser', this is the routing metric of the route to the source advertised by the assert winner; otherwise, this object is zero.
.1.3.6.1.2.1.157.1.8,PIM-STD-MIB::pimSGRptTable,,not-accessible,,current,,The (conceptual) table listing the non-interface specific (S,G,rpt) state that PIM has.
.1.3.6.1.2.1.157.1.8.1,PIM-STD-MIB::pimSGRptEntry,,not-accessible,pimStarGAddressType:pimStarGGrpAddress:pimSGRptSrcAddress,current,,An entry (conceptual row) in the pimSGRptTable.
.1.3.6.1.2.1.157.1.8.1.1,PIM-STD-MIB::pimSGRptSrcAddress,OCTET,not-accessible,,current,,The source address for this entry. The InetAddressType is given by the pimStarGAddressType object.
.1.3.6.1.2.1.157.1.8.1.2,PIM-STD-MIB::pimSGRptUpTime,TimeTicks,read-only,,current,,The time since this entry was created by the local router.
.1.3.6.1.2.1.157.1.8.1.3,PIM-STD-MIB::pimSGRptUpstreamPruneState,INTEGER,read-only,,current,rptNotJoined(1):pruned(2):notPruned(3),Whether the local router should prune the source off the RP tree. This corresponds to the state of the upstream (S,G,rpt) state machine for triggered messages in the PIM-SM specification.
.1.3.6.1.2.1.157.1.8.1.4,PIM-STD-MIB::pimSGRptUpstreamOverrideTimer,TimeTicks,read-only,,current,,The time remaining before the local router sends a triggered (S,G,rpt) Join message on pimStarGRPFIfIndex. This timer is called the (S,G,rpt) Upstream Override Timer in the PIM-SM specification. This object is zero if the timer is not running.
.1.3.6.1.2.1.157.1.9,PIM-STD-MIB::pimSGRptITable,,not-accessible,,current,,The (conceptual) table listing the interface-specific (S,G,rpt) state that PIM has.
.1.3.6.1.2.1.157.1.9.1,PIM-STD-MIB::pimSGRptIEntry,,not-accessible,pimStarGAddressType:pimStarGGrpAddress:pimSGRptSrcAddress:pimSGRptIIfIndex,current,,An entry (conceptual row) in the pimSGRptITable.
.1.3.6.1.2.1.157.1.9.1.1,PIM-STD-MIB::pimSGRptIIfIndex,Integer32,not-accessible,,current,,The ifIndex of the interface that this entry corresponds to.
.1.3.6.1.2.1.157.1.9.1.2,PIM-STD-MIB::pimSGRptIUpTime,TimeTicks,read-only,,current,,The time since this entry was created by the local router.
.1.3.6.1.2.1.157.1.9.1.3,PIM-STD-MIB::pimSGRptILocalMembership,INTEGER,read-only,,current,true(1):false(2),Whether the local router has both (*,G) include local membership and (S,G) exclude local membership on this interface (resulting from a mechanism such as IGMP or MLD). This corresponds to local_receiver_exclude(S,G,I) in the PIM-SM specification.
.1.3.6.1.2.1.157.1.9.1.4,PIM-STD-MIB::pimSGRptIJoinPruneState,INTEGER,read-only,,current,noInfo(1):prune(2):prunePending(3),The state resulting from (S,G,rpt) Join/Prune messages received on this interface. This corresponds to the state of the downstream per-interface (S,G,rpt) state machine in the PIM-SM specification.
.1.3.6.1.2.1.157.1.9.1.5,PIM-STD-MIB::pimSGRptIPrunePendingTimer,TimeTicks,read-only,,current,,The time remaining before the local router starts pruning this source off the RP tree. This timer is called the (S,G,rpt) Prune-Pending Timer in the PIM-SM specification. This object is zero if the timer is not running.
.1.3.6.1.2.1.157.1.9.1.6,PIM-STD-MIB::pimSGRptIPruneExpiryTimer,TimeTicks,read-only,,current,,The time remaining before (S,G,rpt) Prune state for this interface expires. This timer is called the (S,G,rpt) Prune Expiry Timer in the PIM-SM specification. This object is zero if the timer is not running. A value of 'FFFFFFFF'h indicates an infinite expiry time.
.1.3.6.1.2.1.157.1.10,PIM-STD-MIB::pimBidirDFElectionTable,,not-accessible,,current,,The (conceptual) table listing the per-RP Designated Forwarder (DF) Election state for each interface for all the RPs in BIDIR mode.
.1.3.6.1.2.1.157.1.10.1,PIM-STD-MIB::pimBidirDFElectionEntry,,not-accessible,pimBidirDFElectionAddressType:pimBidirDFElectionRPAddress:pimBidirDFElectionIfIndex,current,,An entry (conceptual row) in the pimBidirDFElectionTable.
.1.3.6.1.2.1.157.1.10.1.1,PIM-STD-MIB::pimBidirDFElectionAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the RP for which the DF state is being maintained.
.1.3.6.1.2.1.157.1.10.1.2,PIM-STD-MIB::pimBidirDFElectionRPAddress,OCTET,not-accessible,,current,,The IP address of the RP for which the DF state is being maintained. The InetAddressType is given by the pimBidirDFElectionAddressType object.
.1.3.6.1.2.1.157.1.10.1.3,PIM-STD-MIB::pimBidirDFElectionIfIndex,Integer32,not-accessible,,current,,The value of ifIndex for the interface for which the DF state is being maintained.
.1.3.6.1.2.1.157.1.10.1.4,PIM-STD-MIB::pimBidirDFElectionWinnerAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The primary address type of the winner of the DF Election process. A value of unknown(0) indicates there is currently no DF.
.1.3.6.1.2.1.157.1.10.1.5,PIM-STD-MIB::pimBidirDFElectionWinnerAddress,OCTET,read-only,,current,,The primary IP address of the winner of the DF Election process. The InetAddressType is given by the pimBidirDFElectionWinnerAddressType object.
.1.3.6.1.2.1.157.1.10.1.6,PIM-STD-MIB::pimBidirDFElectionWinnerUpTime,TimeTicks,read-only,,current,,The time since the current winner (last) became elected as the DF for this RP.
.1.3.6.1.2.1.157.1.10.1.7,PIM-STD-MIB::pimBidirDFElectionWinnerMetricPref,Unsigned32,read-only,,current,,The metric preference advertised by the DF Winner, or zero if there is currently no DF.
.1.3.6.1.2.1.157.1.10.1.8,PIM-STD-MIB::pimBidirDFElectionWinnerMetric,Unsigned32,read-only,,current,,The metric advertised by the DF Winner, or zero if there is currently no DF.
.1.3.6.1.2.1.157.1.10.1.9,PIM-STD-MIB::pimBidirDFElectionState,INTEGER,read-only,,current,dfOffer(1):dfLose(2):dfWinner(3):dfBackoff(4),The state of this interface with respect to DF-Election for this RP. The states correspond to the ones defined in the BIDIR-PIM specification.
.1.3.6.1.2.1.157.1.10.1.10,PIM-STD-MIB::pimBidirDFElectionStateTimer,TimeTicks,read-only,,current,,The minimum time remaining after which the local router will expire the current DF state represented by pimBidirDFElectionState.
.1.3.6.1.2.1.157.1.11,PIM-STD-MIB::pimStaticRPTable,,not-accessible,,current,,This table is used to manage static configuration of RPs. If the group prefixes configured for two or more rows in this table overlap, the row with the greatest value of pimStaticRPGrpPrefixLength is used for the overlapping range.
.1.3.6.1.2.1.157.1.11.1,PIM-STD-MIB::pimStaticRPEntry,,not-accessible,pimStaticRPAddressType:pimStaticRPGrpAddress:pimStaticRPGrpPrefixLength,current,,An entry (conceptual row) in the pimStaticRPTable. This entry is preserved on agent restart.
.1.3.6.1.2.1.157.1.11.1.1,PIM-STD-MIB::pimStaticRPAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of this entry.
.1.3.6.1.2.1.157.1.11.1.2,PIM-STD-MIB::pimStaticRPGrpAddress,OCTET,not-accessible,,current,,The multicast group address that, when combined with pimStaticRPGrpPrefixLength, gives the group prefix for this entry. The InetAddressType is given by the pimStaticRPAddressType object. This address object is only significant up to pimStaticRPGrpPrefixLength bits. The remainder of the address bits are zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry.
.1.3.6.1.2.1.157.1.11.1.3,PIM-STD-MIB::pimStaticRPGrpPrefixLength,Unsigned32,not-accessible,,current,,The multicast group prefix length that, when combined with pimStaticRPGrpAddress, gives the group prefix for this entry. The InetAddressType is given by the pimStaticRPAddressType object. If pimStaticRPAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If pimStaticRPGrpAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.157.1.11.1.4,PIM-STD-MIB::pimStaticRPRPAddress,OCTET,read-create,,current,,The IP address of the RP to be used for groups within this group prefix. The InetAddressType is given by the pimStaticRPAddressType object.
.1.3.6.1.2.1.157.1.11.1.5,PIM-STD-MIB::pimStaticRPPimMode,INTEGER,read-create,,current,ssm(2):asm(3):bidir(4),The PIM mode to be used for groups in this group prefix. If this object is set to ssm(2), then pimStaticRPRPAddress must be set to zero. No RP operations are ever possible for PIM Mode SSM.
.1.3.6.1.2.1.157.1.11.1.6,PIM-STD-MIB::pimStaticRPOverrideDynamic,INTEGER,read-create,,current,true(1):false(2),Whether this static RP configuration will override other group mappings in this group prefix. If this object is TRUE, then it will override: - RP information learned dynamically for groups in this group prefix. - RP information configured in pimStaticRPTable with pimStaticRPOverrideDynamic set to FALSE. See pimGroupMappingTable for details.
.1.3.6.1.2.1.157.1.11.1.7,PIM-STD-MIB::pimStaticRPPrecedence,Unsigned32,read-create,,current,,The value for pimGroupMappingPrecedence to be used for this static RP configuration. This allows fine control over which configuration is overridden by this static configuration. If pimStaticRPOverrideDynamic is set to TRUE, all dynamic RP configuration is overridden by this static configuration, whatever the value of this object. The absolute values of this object have a significance only on the local router and do not need to be coordinated with other routers. A setting of this object may have different effects when applied to other routers. Do not use this object unless fine control of static RP behavior on the local router is required.
.1.3.6.1.2.1.157.1.11.1.8,PIM-STD-MIB::pimStaticRPRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which rows in this table can be created and destroyed. This status object cannot be set to active(1) before a valid value has been written to pimStaticRPRPAddress. All writeable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.157.1.11.1.9,PIM-STD-MIB::pimStaticRPStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.157.1.12,PIM-STD-MIB::pimAnycastRPSetTable,,not-accessible,,current,,This table is used to manage Anycast-RP via PIM Register messages, as opposed to via other protocols such as MSDP (Multicast Source Discovery Protocol). Entries must be configured in this table if and only if the local router is a member of one or more Anycast-RP sets, that is, one or more Anycast-RP addresses are assigned to the local router. Note that if using static RP configuration, this is in addition to, not instead of, the pimStaticRPTable entries that must be configured for the Anycast-RPs. The set of rows with the same values of both pimAnycastRPSetAddressType and pimAnycastRPSetAnycastAddress corresponds to the Anycast-RP set for that Anycast-RP address. When an Anycast-RP set configuration is active, one entry per pimAnycastRPSetAnycastAddress corresponds to the local router. The local router is identified by the pimAnycastRpSetLocalRouter object. That entry determines the source address used by the local router when forwarding PIM Register messages within the Anycast-RP set.
.1.3.6.1.2.1.157.1.12.1,PIM-STD-MIB::pimAnycastRPSetEntry,,not-accessible,pimAnycastRPSetAddressType:pimAnycastRPSetAnycastAddress:pimAnycastRPSetRouterAddress,current,,An entry corresponds to a single router within a particular Anycast-RP set. This entry is preserved on agent restart.
.1.3.6.1.2.1.157.1.12.1.1,PIM-STD-MIB::pimAnycastRPSetAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the Anycast-RP address and router address.
.1.3.6.1.2.1.157.1.12.1.2,PIM-STD-MIB::pimAnycastRPSetAnycastAddress,OCTET,not-accessible,,current,,The Anycast-RP address. The InetAddressType is given by the pimAnycastRPSetAddressType object.
.1.3.6.1.2.1.157.1.12.1.3,PIM-STD-MIB::pimAnycastRPSetRouterAddress,OCTET,not-accessible,,current,,The address of a router that is a member of the Anycast-RP set. The InetAddressType is given by the pimAnycastRPSetAddressType object. This address differs from pimAnycastRPSetAnycastAddress. Equal values for these two addresses in a single entry are not permitted. That would cause a Register loop.
.1.3.6.1.2.1.157.1.12.1.4,PIM-STD-MIB::pimAnycastRPSetLocalRouter,INTEGER,read-only,,current,true(1):false(2),Whether this entry corresponds to the local router.
.1.3.6.1.2.1.157.1.12.1.5,PIM-STD-MIB::pimAnycastRPSetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which rows in this table can be created and destroyed. This status object can be set to active(1) without setting any other columnar objects in this entry. All writeable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.157.1.12.1.6,PIM-STD-MIB::pimAnycastRPSetStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.157.1.13,PIM-STD-MIB::pimGroupMappingTable,,not-accessible,,current,,The (conceptual) table listing mappings from multicast group prefixes to the PIM mode and RP address to use for groups within that group prefix. Rows in this table are created for a variety of reasons, indicated by the value of the pimGroupMappingOrigin object. - Rows with a pimGroupMappingOrigin value of 'fixed' are created automatically by the router at startup, to correspond to the well-defined prefixes of link-local and unroutable group addresses. These rows are never destroyed. - Rows with a pimGroupMappingOrigin value of 'embedded' are created by the router to correspond to group prefixes that are to be treated as being in Embedded-RP format. - Rows with a pimGroupMappingOrigin value of 'configRp' are created and destroyed as a result of rows in the pimStaticRPTable being created and destroyed. - Rows with a pimGroupMappingOrigin value of 'configSsm' are created and destroyed as a result of configuration of SSM address ranges to the local router. - Rows with a pimGroupMappingOrigin value of 'bsr' are created as a result of running the PIM Bootstrap Router (BSR) mechanism. If the local router is not the elected BSR, these rows are created to correspond to group prefixes in the PIM Bootstrap messages received from the elected BSR. If the local router is the elected BSR, these rows are created to correspond to group prefixes in the PIM Bootstrap messages that the local router sends. In either case, these rows are destroyed when the group prefixes are timed out by the BSR mechanism. - Rows with a pimGroupMappingOrigin value of 'other' are created and destroyed according to some other mechanism not specified here. Given the collection of rows in this table at any point in time, the PIM mode and RP address to use for a particular group is determined using the following algorithm. 1. From the set of all rows, the subset whose group prefix contains the group in question are selected. 2. If there are no such rows, then the group mapping is undefined. 3. If there are multiple selected rows, and a subset is defined by pimStaticRPTable (pimGroupMappingOrigin value of 'configRp') with pimStaticRPOverrideDynamic set to TRUE, then this subset is selected. 4. From the selected subset of rows, the subset that have the greatest value of pimGroupMappingGrpPrefixLength are selected. 5. If there are still multiple selected rows, the subset that has the highest precedence (the lowest numerical value for pimGroupMappingPrecedence) is selected. 6. If there are still multiple selected rows, the row selected is implementation dependent; the implementation might or might not apply the PIM hash function to select the row. 7. The group mode to use is given by the value of pimGroupMappingPimMode from the single selected row; the RP to use is given by the value of pimGroupMappingRPAddress, unless pimGroupMappingOrigin is 'embedded', in which case, the RP is extracted from the group address in question.
.1.3.6.1.2.1.157.1.13.1,PIM-STD-MIB::pimGroupMappingEntry,,not-accessible,pimGroupMappingOrigin:pimGroupMappingAddressType:pimGroupMappingGrpAddress:pimGroupMappingGrpPrefixLength:pimGroupMappingRPAddressType:pimGroupMappingRPAddress,current,,An entry (conceptual row) in the pimGroupMappingTable.
.1.3.6.1.2.1.157.1.13.1.1,PIM-STD-MIB::pimGroupMappingOrigin,INTEGER,not-accessible,,current,fixed(1):configRp(2):configSsm(3):bsr(4):autoRP(5):embedded(6):other(7),The mechanism by which this group mapping was learned.
.1.3.6.1.2.1.157.1.13.1.2,PIM-STD-MIB::pimGroupMappingAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the IP multicast group prefix.
.1.3.6.1.2.1.157.1.13.1.3,PIM-STD-MIB::pimGroupMappingGrpAddress,OCTET,not-accessible,,current,,The IP multicast group address that, when combined with pimGroupMappingGrpPrefixLength, gives the group prefix for this mapping. The InetAddressType is given by the pimGroupMappingAddressType object. This address object is only significant up to pimGroupMappingGrpPrefixLength bits. The remainder of the address bits are zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry.
.1.3.6.1.2.1.157.1.13.1.4,PIM-STD-MIB::pimGroupMappingGrpPrefixLength,Unsigned32,not-accessible,,current,,The multicast group prefix length that, when combined with pimGroupMappingGrpAddress, gives the group prefix for this mapping. The InetAddressType is given by the pimGroupMappingAddressType object. If pimGroupMappingAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If pimGroupMappingAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.157.1.13.1.5,PIM-STD-MIB::pimGroupMappingRPAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the RP to be used for groups within this group prefix, or unknown(0) if no RP is to be used or if the RP address is unknown. This object must be unknown(0) if pimGroupMappingPimMode is ssm(2), or if pimGroupMappingOrigin is embedded(6).
.1.3.6.1.2.1.157.1.13.1.6,PIM-STD-MIB::pimGroupMappingRPAddress,OCTET,not-accessible,,current,,The IP address of the RP to be used for groups within this group prefix. The InetAddressType is given by the pimGroupMappingRPAddressType object.
.1.3.6.1.2.1.157.1.13.1.7,PIM-STD-MIB::pimGroupMappingPimMode,INTEGER,read-only,,current,none(1):ssm(2):asm(3):bidir(4):dm(5):other(6),The PIM mode to be used for groups in this group prefix.
.1.3.6.1.2.1.157.1.13.1.8,PIM-STD-MIB::pimGroupMappingPrecedence,Unsigned32,read-only,,current,,The precedence of this row, used in the algorithm that determines which row applies to a given group address (described above). Numerically higher values for this object indicate lower precedences, with the value zero denoting the highest precedence. The absolute values of this object have a significance only on the local router and do not need to be coordinated with other routers.
.1.3.6.1.2.1.157.1.14,PIM-STD-MIB::pimKeepalivePeriod,Unsigned32,read-write,,current,,The duration of the Keepalive Timer. This is the period during which the PIM router will maintain (S,G) state in the absence of explicit (S,G) local membership or (S,G) join messages received to maintain it. This timer period is called the Keepalive_Period in the PIM-SM specification. It is called the SourceLifetime in the PIM-DM specification. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.15,PIM-STD-MIB::pimRegisterSuppressionTime,Unsigned32,read-write,,current,,The duration of the Register Suppression Timer. This is the period during which a PIM Designated Router (DR) stops sending Register-encapsulated data to the Rendezvous Point (RP) after receiving a Register-Stop message. This object is used to run timers both at the DR and at the RP. This timer period is called the Register_Suppression_Time in the PIM-SM specification. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.16,PIM-STD-MIB::pimStarGEntries,Gauge32,read-only,,current,,The number of entries in the pimStarGTable.
.1.3.6.1.2.1.157.1.17,PIM-STD-MIB::pimStarGIEntries,Gauge32,read-only,,current,,The number of entries in the pimStarGITable.
.1.3.6.1.2.1.157.1.18,PIM-STD-MIB::pimSGEntries,Gauge32,read-only,,current,,The number of entries in the pimSGTable.
.1.3.6.1.2.1.157.1.19,PIM-STD-MIB::pimSGIEntries,Gauge32,read-only,,current,,The number of entries in the pimSGITable.
.1.3.6.1.2.1.157.1.20,PIM-STD-MIB::pimSGRptEntries,Gauge32,read-only,,current,,The number of entries in the pimSGRptTable.
.1.3.6.1.2.1.157.1.21,PIM-STD-MIB::pimSGRptIEntries,Gauge32,read-only,,current,,The number of entries in the pimSGRptITable.
.1.3.6.1.2.1.157.1.22,PIM-STD-MIB::pimOutAsserts,Counter64,read-only,,current,,The number of Asserts sent by this router. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.23,PIM-STD-MIB::pimInAsserts,Counter64,read-only,,current,,The number of Asserts received by this router. Asserts are multicast to all routers on a network. This counter is incremented by all routers that receive an assert, not only those routers that are contesting the assert. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.24,PIM-STD-MIB::pimLastAssertInterface,Integer32,read-only,,current,,The interface on which this router most recently sent or received an assert, or zero if this router has not sent or received an assert.
.1.3.6.1.2.1.157.1.25,PIM-STD-MIB::pimLastAssertGroupAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the multicast group address in the most recently sent or received assert. If this router has not sent or received an assert, then this object is set to unknown(0).
.1.3.6.1.2.1.157.1.26,PIM-STD-MIB::pimLastAssertGroupAddress,OCTET,read-only,,current,,The multicast group address in the most recently sent or received assert. The InetAddressType is given by the pimLastAssertGroupAddressType object.
.1.3.6.1.2.1.157.1.27,PIM-STD-MIB::pimLastAssertSourceAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the source address in the most recently sent or received assert. If the most recent assert was (*,G), or if this router has not sent or received an assert, then this object is set to unknown(0).
.1.3.6.1.2.1.157.1.28,PIM-STD-MIB::pimLastAssertSourceAddress,OCTET,read-only,,current,,The source address in the most recently sent or received assert. The InetAddressType is given by the pimLastAssertSourceAddressType object.
.1.3.6.1.2.1.157.1.29,PIM-STD-MIB::pimNeighborLossNotificationPeriod,Unsigned32,read-write,,current,,The minimum time that must elapse between pimNeighborLoss notifications originated by this router. The maximum value 65535 represents an 'infinite' time, in which case, no pimNeighborLoss notifications are ever sent. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.30,PIM-STD-MIB::pimNeighborLossCount,Counter32,read-only,,current,,The number of neighbor loss events that have occurred. This counter is incremented when the neighbor timer expires, and the router has no other neighbors on the same interface with the same IP version and a lower IP address than itself. This counter is incremented whenever a pimNeighborLoss notification would be generated. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.31,PIM-STD-MIB::pimInvalidRegisterNotificationPeriod,Unsigned32,read-write,,current,,The minimum time that must elapse between pimInvalidRegister notifications originated by this router. The default value of 65535 represents an 'infinite' time, in which case, no pimInvalidRegister notifications are ever sent. The non-zero minimum allowed value provides resilience against propagation of denial-of-service attacks from the data and control planes to the network management plane. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.32,PIM-STD-MIB::pimInvalidRegisterMsgsRcvd,Counter32,read-only,,current,,The number of invalid PIM Register messages that have been received by this device. A PIM Register message is invalid if either o the destination address of the Register message does not match the Group to RP mapping on this device, or o this device believes the group address to be within an SSM address range, but this Register implies ASM usage. These conditions can occur transiently while RP mapping changes propagate through the network. If this counter is incremented repeatedly over several minutes, then there is a persisting configuration error that requires correction. The active Group to RP mapping on this device is specified by the object pimGroupMappingPimMode. If there is no such mapping, then the object pimGroupMappingPimMode is absent. The RP address contained in the invalid Register is pimInvalidRegisterRp. Multicast data carried by invalid Register messages is discarded. The discarded data is from a source directly connected to pimInvalidRegisterOrigin, and is addressed to pimInvalidRegisterGroup. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.33,PIM-STD-MIB::pimInvalidRegisterAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type stored in pimInvalidRegisterOrigin, pimInvalidRegisterGroup, and pimInvalidRegisterRp. If no invalid Register messages have been received, then this object is set to unknown(0).
.1.3.6.1.2.1.157.1.34,PIM-STD-MIB::pimInvalidRegisterOrigin,OCTET,read-only,,current,,The source address of the last invalid Register message received by this device.
.1.3.6.1.2.1.157.1.35,PIM-STD-MIB::pimInvalidRegisterGroup,OCTET,read-only,,current,,The IP multicast group address to which the last invalid Register message received by this device was addressed.
.1.3.6.1.2.1.157.1.36,PIM-STD-MIB::pimInvalidRegisterRp,OCTET,read-only,,current,,The RP address to which the last invalid Register message received by this device was delivered.
.1.3.6.1.2.1.157.1.37,PIM-STD-MIB::pimInvalidJoinPruneNotificationPeriod,Unsigned32,read-write,,current,,The minimum time that must elapse between pimInvalidJoinPrune notifications originated by this router. The default value of 65535 represents an 'infinite' time, in which case, no pimInvalidJoinPrune notifications are ever sent. The non-zero minimum allowed value provides resilience against propagation of denial-of-service attacks from the control plane to the network management plane. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.38,PIM-STD-MIB::pimInvalidJoinPruneMsgsRcvd,Counter32,read-only,,current,,The number of invalid PIM Join/Prune messages that have been received by this device. A PIM Join/Prune message is invalid if either o the Group to RP mapping specified by this message does not match the Group to RP mapping on this device, or o this device believes the group address to be within an SSM address range, but this Join/Prune (*,G) or (S,G,rpt) implies ASM usage. These conditions can occur transiently while RP mapping changes propagate through the network. If this counter is incremented repeatedly over several minutes, then there is a persisting configuration error that requires correction. The active Group to RP mapping on this device is specified by the object pimGroupMappingPimMode. If there is no such mapping, then the object pimGroupMappingPimMode is absent. The RP address contained in the invalid Join/Prune is pimInvalidJoinPruneRp. Invalid Join/Prune messages are discarded. This may result in loss of multicast data affecting listeners downstream of pimInvalidJoinPruneOrigin, for multicast data addressed to pimInvalidJoinPruneGroup. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.39,PIM-STD-MIB::pimInvalidJoinPruneAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type stored in pimInvalidJoinPruneOrigin, pimInvalidJoinPruneGroup, and pimInvalidJoinPruneRp. If no invalid Join/Prune messages have been received, this object is set to unknown(0).
.1.3.6.1.2.1.157.1.40,PIM-STD-MIB::pimInvalidJoinPruneOrigin,OCTET,read-only,,current,,The source address of the last invalid Join/Prune message received by this device.
.1.3.6.1.2.1.157.1.41,PIM-STD-MIB::pimInvalidJoinPruneGroup,OCTET,read-only,,current,,The IP multicast group address carried in the last invalid Join/Prune message received by this device.
.1.3.6.1.2.1.157.1.42,PIM-STD-MIB::pimInvalidJoinPruneRp,OCTET,read-only,,current,,The RP address carried in the last invalid Join/Prune message received by this device.
.1.3.6.1.2.1.157.1.43,PIM-STD-MIB::pimRPMappingNotificationPeriod,Unsigned32,read-write,,current,,The minimum time that must elapse between pimRPMappingChange notifications originated by this router. The default value of 65535 represents an 'infinite' time, in which case, no pimRPMappingChange notifications are ever sent. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.44,PIM-STD-MIB::pimRPMappingChangeCount,Counter32,read-only,,current,,The number of changes to active RP mappings on this device. Information about active RP mappings is available in pimGroupMappingTable. Only changes to active mappings cause this counter to be incremented. That is, changes that modify the pimGroupMappingEntry with the highest precedence for a group (lowest value of pimGroupMappingPrecedence). Such changes may result from manual configuration of this device, or from automatic RP mapping discovery methods including the PIM Bootstrap Router (BSR) mechanism. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.45,PIM-STD-MIB::pimInterfaceElectionNotificationPeriod,Unsigned32,read-write,,current,,The minimum time that must elapse between pimInterfaceElection notifications originated by this router. The default value of 65535 represents an 'infinite' time, in which case, no pimInterfaceElection notifications are ever sent. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.46,PIM-STD-MIB::pimInterfaceElectionWinCount,Counter32,read-only,,current,,The number of times this device has been elected DR or DF on any interface. Elections occur frequently on newly-active interfaces, as triggered Hellos establish adjacencies. This counter is not incremented for elections on an interface until the first periodic Hello has been sent. If this router is the DR or DF at the time of sending the first periodic Hello after interface activation, then this counter is incremented (once) at that time. Discontinuities in the value of this counter can occur at re-initialization of the management system, for example, when the device is rebooted.
.1.3.6.1.2.1.157.1.47,PIM-STD-MIB::pimRefreshInterval,Unsigned32,read-write,,current,,The interval between successive State Refresh messages sent by an Originator. This timer period is called the RefreshInterval in the PIM-DM specification. This object is used only by PIM-DM. The storage type of this object is determined by pimDeviceConfigStorageType.
.1.3.6.1.2.1.157.1.48,PIM-STD-MIB::pimDeviceConfigStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type used for the global PIM configuration of this device, comprised of the objects listed below. If this storage type takes the value 'permanent', write-access to the listed objects need not be allowed. The objects described by this storage type are: pimKeepalivePeriod, pimRegisterSuppressionTime, pimNeighborLossNotificationPeriod, pimInvalidRegisterNotificationPeriod, pimInvalidJoinPruneNotificationPeriod, pimRPMappingNotificationPeriod, pimInterfaceElectionNotificationPeriod, and pimRefreshInterval.
.1.3.6.1.2.1.157.2,PIM-STD-MIB::pimMIBConformance,,,,,,
.1.3.6.1.2.1.157.2.1,PIM-STD-MIB::pimMIBCompliances,,,,,,
.1.3.6.1.2.1.157.2.1.1,PIM-STD-MIB::pimMIBComplianceAsm,,,,,,The compliance statement for routers which are running PIM-SM (Sparse Mode).
.1.3.6.1.2.1.157.2.1.2,PIM-STD-MIB::pimMIBComplianceBidir,,,,,,The compliance statement for routers which are running Bidir-PIM.
.1.3.6.1.2.1.157.2.1.3,PIM-STD-MIB::pimMIBComplianceSsm,,,,,,The compliance statement for routers which are running PIM SSM (Source Specific Multicast).
.1.3.6.1.2.1.157.2.1.4,PIM-STD-MIB::pimMIBComplianceDm,,,,,,The compliance statement for routers which are running PIM-DM (Dense Mode).
.1.3.6.1.2.1.157.2.2,PIM-STD-MIB::pimMIBGroups,,,,,,
.1.3.6.1.2.1.157.2.2.1,PIM-STD-MIB::pimTopologyGroup,,,,,,A collection of read-only objects used to report local PIM topology.
.1.3.6.1.2.1.157.2.2.2,PIM-STD-MIB::pimNotificationGroup,,,,,,A collection of notifications for signaling important PIM events.
.1.3.6.1.2.1.157.2.2.3,PIM-STD-MIB::pimTuningParametersGroup,,,,,,A collection of writeable objects used to configure PIM behavior and to tune performance.
.1.3.6.1.2.1.157.2.2.4,PIM-STD-MIB::pimRouterStatisticsGroup,,,,,,A collection of statistics global to the PIM router.
.1.3.6.1.2.1.157.2.2.5,PIM-STD-MIB::pimSsmGroup,,,,,,A collection of objects to support management of PIM routers running the PIM SSM (Source Specific Multicast) protocol, in PIM mode SM (Sparse Mode).
.1.3.6.1.2.1.157.2.2.6,PIM-STD-MIB::pimRPConfigGroup,,,,,,A collection of objects to support configuration of RPs (Rendezvous Points) and Group Mappings.
.1.3.6.1.2.1.157.2.2.7,PIM-STD-MIB::pimSmGroup,,,,,,A collection of objects to support management of PIM routers running PIM-SM (Sparse Mode). The groups pimSsmGroup and pimRPConfigGroup are also required.
.1.3.6.1.2.1.157.2.2.8,PIM-STD-MIB::pimBidirGroup,,,,,,A collection of objects to support management of PIM routers running BIDIR mode. The groups pimSsmGroup, pimSmGroup and pimRPConfigGroup are also required.
.1.3.6.1.2.1.157.2.2.9,PIM-STD-MIB::pimAnycastRpGroup,,,,,,A collection of objects to support management of the PIM Anycast-RP mechanism.
.1.3.6.1.2.1.157.2.2.10,PIM-STD-MIB::pimStaticRPPrecedenceGroup,,,,,,A collection of objects to allow fine control of interactions between static RP configuration and dynamically acquired group to RP mappings.
.1.3.6.1.2.1.157.2.2.11,PIM-STD-MIB::pimNetMgmtNotificationObjects,,,,,,A collection of objects to support notification of PIM network management events.
.1.3.6.1.2.1.157.2.2.12,PIM-STD-MIB::pimNetMgmtNotificationGroup,,,,,,A collection of notifications for signaling PIM network management events.
.1.3.6.1.2.1.157.2.2.13,PIM-STD-MIB::pimDiagnosticsGroup,,,,,,Objects providing additional diagnostics related to a PIM router.
.1.3.6.1.2.1.157.2.2.14,PIM-STD-MIB::pimDmGroup,,,,,,A collection of objects required for management of PIM Dense Mode (PIM-DM) function. The groups pimSsmGroup and pimSmGroup are also required.
.1.3.6.1.2.1.157.2.2.15,PIM-STD-MIB::pimDeviceStorageGroup,,,,,,An object that specifies the volatility of global PIM configuration settings on this device.
.1.3.6.1.2.1.158,DOT3-OAM-MIB::dot3OamMIB,,,,,,The MIB module for managing the new Ethernet OAM features introduced by the Ethernet in the First Mile taskforce (IEEE 802.3ah). The functionality presented here is based on IEEE 802.3ah [802.3ah], released in October, 2004. [802.3ah] was prepared as an addendum to the standing version of IEEE 802.3 [802.3-2002]. Since then, [802.3ah] has been merged into the base IEEE 802.3 specification in [802.3-2005]. In particular, this MIB focuses on the new OAM functions introduced in Clause 57 of [802.3ah]. The OAM functionality of Clause 57 is controlled by new management attributes introduced in Clause 30 of [802.3ah]. The OAM functions are not specific to any particular Ethernet physical layer, and can be generically applied to any Ethernet interface of [802.3-2002]. An Ethernet OAM protocol data unit is a valid Ethernet frame with a destination MAC address equal to the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), a lengthOrType field equal to the reserved type for Slow Protocols, and a Slow Protocols subtype equal to that of the subtype reserved for Ethernet OAM. OAMPDU is used throughout this document as an abbreviation for Ethernet OAM protocol data unit. The following reference is used throughout this MIB module: [802.3ah] refers to: IEEE Std 802.3ah-2004: 'Draft amendment to - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', October 2004. [802.3-2002] refers to: IEEE Std 802.3-2002: 'Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', March 2002. [802.3-2005] refers to: IEEE Std 802.3-2005: 'Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', December 2005. [802-2001] refers to: 'IEEE Standard for LAN/MAN (Local Area Network/Metropolitan Area Network): Overview and Architecture', IEEE 802, June 2001. Copyright (c) The IETF Trust (2007). This version of this MIB module is part of RFC 4878; See the RFC itself for full legal notices. 
.1.3.6.1.2.1.158.0,DOT3-OAM-MIB::dot3OamNotifications,,,,,,
.1.3.6.1.2.1.158.0.1,DOT3-OAM-MIB::dot3OamThresholdEvent,,,,,,A dot3OamThresholdEvent notification is sent when a local or remote threshold crossing event is detected. A local threshold crossing event is detected by the local entity, while a remote threshold crossing event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates a threshold event. This notification should not be sent more than once per second. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance in the dot3OamEventLogTable. The management entity should periodically check dot3OamEventLogTable to detect any missed events.
.1.3.6.1.2.1.158.0.2,DOT3-OAM-MIB::dot3OamNonThresholdEvent,,,,,,A dot3OamNonThresholdEvent notification is sent when a local or remote non-threshold crossing event is detected. A local event is detected by the local entity, while a remote event is detected by the reception of an Ethernet OAM Event Notification OAMPDU that indicates a non-threshold crossing event. This notification should not be sent more than once per second. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance of the dot3OamEventLogTable. The management entity should periodically check dot3OamEventLogTable to detect any missed events.
.1.3.6.1.2.1.158.1,DOT3-OAM-MIB::dot3OamObjects,,,,,,
.1.3.6.1.2.1.158.1.1,DOT3-OAM-MIB::dot3OamTable,,not-accessible,,current,,This table contains the primary controls and status for the OAM capabilities of an Ethernet-like interface. There will be one row in this table for each Ethernet-like interface in the system that supports the OAM functions defined in [802.3ah]. 
.1.3.6.1.2.1.158.1.1.1,DOT3-OAM-MIB::dot3OamEntry,,not-accessible,ifIndex,current,,An entry in the table that contains information on the Ethernet OAM function for a single Ethernet like interface. Entries in the table are created automatically for each interface supporting Ethernet OAM. The status of the row entry can be determined from dot3OamOperStatus. A dot3OamEntry is indexed in the dot3OamTable by the ifIndex object of the Interfaces MIB. 
.1.3.6.1.2.1.158.1.1.1.1,DOT3-OAM-MIB::dot3OamAdminState,INTEGER,read-write,,current,enabled(1):disabled(2),This object is used to provision the default administrative OAM mode for this interface. This object represents the desired state of OAM for this interface. The dot3OamAdminState always starts in the disabled(2) state until an explicit management action or configuration information retained by the system causes a transition to the enabled(1) state. When enabled(1), Ethernet OAM will attempt to operate over this interface. 
.1.3.6.1.2.1.158.1.1.1.2,DOT3-OAM-MIB::dot3OamOperStatus,INTEGER,read-only,,current,disabled(1):linkFault(2):passiveWait(3):activeSendLocal(4):sendLocalAndRemote(5):sendLocalAndRemoteOk(6):oamPeeringLocallyRejected(7):oamPeeringRemotelyRejected(8):operational(9):nonOperHalfDuplex(10),At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OA sublayer. This value is always disabled(1) if OAM is disabled on this interface via the dot3OamAdminState. If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is linkFault(2). Also, if the interface is not operational (ifOperStatus is not up(1)), linkFault(2) is returned. Note that the object ifOperStatus may not be up(1) as a result of link failure or administrative action (ifAdminState being down(2) or testing(3)). The passiveWait(3) state is returned only by OAM entities in passive mode (dot3OamMode) and reflects the state in which the OAM entity is waiting to see if the peer device is OA capable. The activeSendLocal(4) value is used by active mode devices (dot3OamMode) and reflects the OAM entity actively trying to discover whether the peer has OAM capability but has not yet made that determination. The state sendLocalAndRemote(5) reflects that the local OA entity has discovered the peer but has not yet accepted or rejected the configuration of the peer. The local device can, for whatever reason, decide that the peer device is unacceptable and decline OAM peering. If the local OAM entity rejects the peer OAM entity, the state becomes oamPeeringLocallyRejected(7). If the OAM peering is allowed by the local device, the state moves to sendLocalAndRemoteOk(6). Note that both the sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the local OAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10). If the remote OAM entity rejects the peering, the state becomes oamPeeringRemotelyRejected(8). Note that both the sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8) states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the remote OAM client has rejected the peering or has just not yet decided. This is indicated via the remote flags field in the OAMPDU (reflected in the aOAMRemoteFlagsField of 30.3.6.1.11). When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to operational(9) corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57-5]. Since Ethernet OAM functions are not designed to work completely over half-duplex interfaces, the value nonOperHalfDuplex(10) is returned whenever Ethernet OAM is enabled (dot3OamAdminState is enabled(1)), but the interface is in half-duplex operation. 
.1.3.6.1.2.1.158.1.1.1.3,DOT3-OAM-MIB::dot3OamMode,INTEGER,read-write,,current,passive(1):active(2),This object configures the mode of OAM operation for this Ethernet-like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode generally waits for the peer to initiate OA actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OA entity cannot. The default value of dot3OamMode is dependent on the type of system on which this Ethernet-like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface. Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9). 
.1.3.6.1.2.1.158.1.1.1.4,DOT3-OAM-MIB::dot3OamMaxOamPduSize,Unsigned32,read-only,,current,,The largest OAMPDU that the OAM entity supports. OA entities exchange maximum OAMPDU sizes and negotiate to use the smaller of the two maximum OAMPDU sizes between the peers. This value is determined by the local implementation. 
.1.3.6.1.2.1.158.1.1.1.5,DOT3-OAM-MIB::dot3OamConfigRevision,Unsigned32,read-only,,current,,The configuration revision of the OAM entity as reflected in the latest OAMPDU sent by the OAM entity. The config revision is used by OAM entities to indicate that configuration changes have occurred, which might require the peer OAM entity to re-evaluate whether OAM peering is allowed. 
.1.3.6.1.2.1.158.1.1.1.6,DOT3-OAM-MIB::dot3OamFunctionsSupported,BITS,read-only,,current,unidirectionalSupport(0):loopbackSupport(1):eventSupport(2):variableSupport(3),The OAM functions supported on this Ethernet-like interface. OAM consists of separate functional sets beyond the basic discovery process that is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs. Setting 'unidirectionalSupport(0)' indicates that the OA entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport(1)' indicates that the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport(2)' indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting 'variableSupport(3)' indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs. 
.1.3.6.1.2.1.158.1.2,DOT3-OAM-MIB::dot3OamPeerTable,,not-accessible,,current,,This table contains information about the OAM peer for a particular Ethernet-like interface. OAM entities communicate with a single OAM peer entity on Ethernet links on which OA is enabled and operating properly. There is one entry in this table for each entry in the dot3OamTable for which information on the peer OAM entity is available. 
.1.3.6.1.2.1.158.1.2.1,DOT3-OAM-MIB::dot3OamPeerEntry,,not-accessible,ifIndex,current,,An entry in the table containing information on the peer OA entity for a single Ethernet-like interface. Note that there is at most one OAM peer for each Ethernet-like interface. Entries are automatically created when information about the OAM peer entity becomes available, and automatically deleted when the OAM peer entity is no longer in communication. Peer information is not available when dot3OamOperStatus is disabled(1), linkFault(2), passiveWait(3), activeSendLocal(4), or nonOperHalfDuplex(10). 
.1.3.6.1.2.1.158.1.2.1.1,DOT3-OAM-MIB::dot3OamPeerMacAddress,OCTET,read-only,,current,,The MAC address of the peer OAM entity. The MAC address is derived from the most recently received OAMPDU. 
.1.3.6.1.2.1.158.1.2.1.2,DOT3-OAM-MIB::dot3OamPeerVendorOui,OCTET,read-only,,current,,The OUI of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The OUI can be used to identify the vendor of the remote OA entity. This value is initialized to three octets of zero before any Local Information TLV is received. 
.1.3.6.1.2.1.158.1.2.1.3,DOT3-OAM-MIB::dot3OamPeerVendorInfo,Unsigned32,read-only,,current,,The Vendor Info of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The semantics of the Vendor Information field is proprietary and specific to the vendor (identified by the dot3OamPeerVendorOui). This information could, for example, be used to identify a specific product or product family. This value is initialized to zero before any Local Information TLV is received. 
.1.3.6.1.2.1.158.1.2.1.4,DOT3-OAM-MIB::dot3OamPeerMode,INTEGER,read-only,,current,passive(1):active(2):unknown(3),The mode of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The mode of the peer can be determined from the Configuration field in the Local Information TLV of the last Information OAMPDU received from the peer. The value is unknown(3) whenever no Local Information TLV has been received. The values of active(2) and passive(1) are returned when a Local Information TLV has been received indicating that the peer is in active or passive mode, respectively. 
.1.3.6.1.2.1.158.1.2.1.5,DOT3-OAM-MIB::dot3OamPeerMaxOamPduSize,Unsigned32,read-only,,current,,The maximum size of OAMPDU supported by the peer as reflected in the latest Information OAMPDU received with a Local Information TLV. Ethernet OAM on this interface must not use OAMPDUs that exceed this size. The maximum OAMPDU size can be determined from the PDU Configuration field of the Local Information TLV of the last Information OAMPDU received from the peer. A value of zero is returned if no Local Information TLV has been received. Otherwise, the value of the OAM peer's maximum OAMPDU size is returned in this value. 
.1.3.6.1.2.1.158.1.2.1.6,DOT3-OAM-MIB::dot3OamPeerConfigRevision,Unsigned32,read-only,,current,,The configuration revision of the OAM peer as reflected in the latest OAMPDU. This attribute is changed by the peer whenever it has a local configuration change for Ethernet OA on this interface. The configuration revision can be determined from the Revision field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. A value of zero is returned if no Local Information TLV has been received. 
.1.3.6.1.2.1.158.1.2.1.7,DOT3-OAM-MIB::dot3OamPeerFunctionsSupported,BITS,read-only,,current,unidirectionalSupport(0):loopbackSupport(1):eventSupport(2):variableSupport(3),The OAM functions supported on this Ethernet-like interface. OAM consists of separate functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear. If unidirectionalSupport(0) is set, then the peer OAM entity supports sending OAM frames on Ethernet interfaces when the receive path is known to be inoperable. If loopbackSupport(1) is set, then the peer OAM entity can send and receive OAM loopback commands. If eventSupport(2) is set, then the peer OAM entity can send and receive event OAMPDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor the attribute value as described in Clause 57 of [802.3ah]. The capabilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. All zeros are returned if no Local Information TLV has yet been received. 
.1.3.6.1.2.1.158.1.3,DOT3-OAM-MIB::dot3OamLoopbackTable,,not-accessible,,current,,This table contains controls for the loopback state of the local link as well as indicates the status of the loopback function. There is one entry in this table for each entry in dot3OamTable that supports loopback functionality (where dot3OamFunctionsSupported includes the loopbackSupport bit set). Loopback can be used to place the remote OAM entity in a state where every received frame (except OAMPDUs) is echoed back over the same interface on which they were received. In this state, at the remote entity, 'normal' traffic is disabled as only the looped back frames are transmitted on the interface. Loopback is thus an intrusive operation that prohibits normal data flow and should be used accordingly. 
.1.3.6.1.2.1.158.1.3.1,DOT3-OAM-MIB::dot3OamLoopbackEntry,,not-accessible,ifIndex,current,,An entry in the table, containing information on the loopback status for a single Ethernet-like interface. Entries in the table are automatically created whenever the local OAM entity supports loopback capabilities. The loopback status on the interface can be determined from the dot3OamLoopbackStatus object. 
.1.3.6.1.2.1.158.1.3.1.1,DOT3-OAM-MIB::dot3OamLoopbackStatus,INTEGER,read-write,,current,noLoopback(1):initiatingLoopback(2):remoteLoopback(3):terminatingLoopback(4):localLoopback(5):unknown(6),The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1). The values initiatingLoopback(2) and terminatingLoopback(4) can be read or written. The other values can only be read - they can never be written. Writing initiatingLoopback causes the local OAM entity to start the loopback process with its peer. This value can only be written when the status is noLoopback(1). Writing the value initiatingLoopback(2) in any other state has no effect. When in remoteLoopback(3), writing terminatingLoopback(4) causes the local OAM entity to initiate the termination of the loopback state. Writing terminatingLoopack(4) in any other state has no effect. If the OAM client initiates a loopback and has sent a Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgment that the remote OAM entity has received its loopback command request. If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14] with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5). The unknown(6) status indicates that the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist. The values of this attribute correspond to the following values of the local and remote parser and multiplexer states. value LclPrsr LclMux RmtPrsr RmtMux noLoopback FWD FWD FWD FWD initLoopback DISCARD DISCARD FWD FWD rmtLoopback DISCARD FWD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD lclLoopback LPBK DISCARD DISCARD FWD unknown *** any other combination *** 
.1.3.6.1.2.1.158.1.3.1.2,DOT3-OAM-MIB::dot3OamLoopbackIgnoreRx,INTEGER,read-write,,current,ignore(1):process(2),Since OAM loopback is a disruptive operation (user traffic does not pass), this attribute provides a mechanism to provide controls over whether received OAM loopback commands are processed or ignored. When the value is ignore(1), received loopback commands are ignored. When the value is process(2), OAM loopback commands are processed. The default value is to ignore loopback commands (ignore(1)). 
.1.3.6.1.2.1.158.1.4,DOT3-OAM-MIB::dot3OamStatsTable,,not-accessible,,current,,This table contains statistics for the OAM function on a particular Ethernet-like interface. There is an entry in the table for every entry in the dot3OamTable. The counters in this table are defined as 32-bit entries to match the counter size as defined in [802.3ah]. Given that the OA protocol is a slow protocol, the counters increment at a slow rate. 
.1.3.6.1.2.1.158.1.4.1,DOT3-OAM-MIB::dot3OamStatsEntry,,not-accessible,ifIndex,current,,An entry in the table containing statistics information on the Ethernet OAM function for a single Ethernet-like interface. Entries are automatically created for every entry in the dot3OamTable. Counters are maintained across transitions in dot3OamOperStatus. 
.1.3.6.1.2.1.158.1.4.1.1,DOT3-OAM-MIB::dot3OamInformationTx,Counter32,read-only,,current,,A count of the number of Information OAMPDUs transmitted on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.2,DOT3-OAM-MIB::dot3OamInformationRx,Counter32,read-only,,current,,A count of the number of Information OAMPDUs received on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.3,DOT3-OAM-MIB::dot3OamUniqueEventNotificationTx,Counter32,read-only,,current,,A count of the number of unique Event OAMPDUs transmitted on this interface. Event Notifications may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit. Duplicate Event Notification transmissions are counted by dot3OamDuplicateEventNotificationTx. A unique Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is distinct from the previously transmitted Event Notification OAMPDU Sequence Number. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.4,DOT3-OAM-MIB::dot3OamUniqueEventNotificationRx,Counter32,read-only,,current,,A count of the number of unique Event OAMPDUs received on this interface. Event Notification OAMPDUs may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit. Duplicate Event Notification receptions are counted by dot3OamDuplicateEventNotificationRx. A unique Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is distinct from the previously received Event Notification OAMPDU Sequence Number. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.5,DOT3-OAM-MIB::dot3OamDuplicateEventNotificationTx,Counter32,read-only,,current,,A count of the number of duplicate Event OAMPDUs transmitted on this interface. Event Notification OAMPDUs may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit. A duplicate Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is identical to the previously transmitted Event Notification OAMPDU Sequence Number. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.6,DOT3-OAM-MIB::dot3OamDuplicateEventNotificationRx,Counter32,read-only,,current,,A count of the number of duplicate Event OAMPDUs received on this interface. Event Notification OAMPDUs may be sent in duplicate to increase the probability of successfully being received, given the possibility that a frame may be lost in transit. A duplicate Event Notification OAMPDU is indicated as an Event Notification OAMPDU with a Sequence Number field that is identical to the previously received Event Notification OAMPDU Sequence Number. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.7,DOT3-OAM-MIB::dot3OamLoopbackControlTx,Counter32,read-only,,current,,A count of the number of Loopback Control OAMPDUs transmitted on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.8,DOT3-OAM-MIB::dot3OamLoopbackControlRx,Counter32,read-only,,current,,A count of the number of Loopback Control OAMPDUs received on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.9,DOT3-OAM-MIB::dot3OamVariableRequestTx,Counter32,read-only,,current,,A count of the number of Variable Request OAMPDUs transmitted on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.10,DOT3-OAM-MIB::dot3OamVariableRequestRx,Counter32,read-only,,current,,A count of the number of Variable Request OAMPDUs received on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.11,DOT3-OAM-MIB::dot3OamVariableResponseTx,Counter32,read-only,,current,,A count of the number of Variable Response OAMPDUs transmitted on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.12,DOT3-OAM-MIB::dot3OamVariableResponseRx,Counter32,read-only,,current,,A count of the number of Variable Response OAMPDUs received on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.13,DOT3-OAM-MIB::dot3OamOrgSpecificTx,Counter32,read-only,,current,,A count of the number of Organization Specific OAMPDUs transmitted on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.14,DOT3-OAM-MIB::dot3OamOrgSpecificRx,Counter32,read-only,,current,,A count of the number of Organization Specific OAMPDUs received on this interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.15,DOT3-OAM-MIB::dot3OamUnsupportedCodesTx,Counter32,read-only,,current,,A count of the number of OAMPDUs transmitted on this interface with an unsupported op-code. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.16,DOT3-OAM-MIB::dot3OamUnsupportedCodesRx,Counter32,read-only,,current,,A count of the number of OAMPDUs received on this interface with an unsupported op-code. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.4.1.17,DOT3-OAM-MIB::dot3OamFramesLostDueToOam,Counter32,read-only,,current,,A count of the number of frames that were dropped by the OA multiplexer. Since the OAM multiplexer has multiple inputs and a single output, there may be cases where frames are dropped due to transmit resource contention. This counter is incremented whenever a frame is dropped by the OAM layer. Note that any Ethernet frame, not just OAMPDUs, may be dropped by the OAM layer. This can occur when an OAMPDU takes precedence over a 'normal' frame resulting in the 'normal' frame being dropped. When this counter is incremented, no other counters in this MIB are incremented. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime. 
.1.3.6.1.2.1.158.1.5,DOT3-OAM-MIB::dot3OamEventConfigTable,,not-accessible,,current,,Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in dot3OamTable that supports OAM events (where dot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to dot3OamOperStatus. The standard threshold crossing events are: - Errored Symbol Period Event. Generated when the number of symbol errors exceeds a threshold within a given window defined by a number of symbols (for example, 1,000 symbols out of 1,000,000 had errors). - Errored Frame Period Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a number of frames (for example, 10 frames out of 1000 had errors). - Errored Frame Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a period of time (for example, 10 frames in 1 second had errors). - Errored Frame Seconds Summary Event. Generated when the number of errored frame seconds exceeds a threshold within a given time period (for example, 10 errored frame seconds within the last 100 seconds). An errored frame second is defined as a 1 second interval which had >0 frame errors. There are other events (dying gasp, critical events) that are not threshold crossing events but which can be enabled/disabled via this table. 
.1.3.6.1.2.1.158.1.5.1,DOT3-OAM-MIB::dot3OamEventConfigEntry,,not-accessible,ifIndex,current,,Entries are automatically created and deleted from this table, and exist whenever the OAM entity supports Ethernet OA events (as indicated by the eventSupport bit in dot3OamFunctionsSuppported). Values in the table are maintained across changes to the value of dot3OamOperStatus. Event configuration controls when the local management entity sends Event Notification OAMPDUs to its OAM peer, and when certain event flags are set or cleared in OAMPDUs. 
.1.3.6.1.2.1.158.1.5.1.1,DOT3-OAM-MIB::dot3OamErrSymPeriodWindowHi,Unsigned32,read-write,,current,,The two objects dot3OamErrSymPeriodWindowHi and dot3OamErrSymPeriodLo together form an unsigned 64-bit integer representing the number of symbols over which this threshold event is defined. This is defined as dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi) + dot3OamErrSymPeriodWindowLo If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodWindow is the number of symbols in one second for the underlying physical layer. 
.1.3.6.1.2.1.158.1.5.1.2,DOT3-OAM-MIB::dot3OamErrSymPeriodWindowLo,Unsigned32,read-write,,current,,The two objects dot3OamErrSymPeriodWindowHi and dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit integer representing the number of symbols over which this threshold event is defined. This is defined as dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi) + dot3OamErrSymPeriodWindowLo If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodWindow is the number of symbols in one second for the underlying physical layer. 
.1.3.6.1.2.1.158.1.5.1.3,DOT3-OAM-MIB::dot3OamErrSymPeriodThresholdHi,Unsigned32,read-write,,current,,The two objects dot3OamErrSymPeriodThresholdHi and dot3OamErrSymPeriodThresholdLo together form an unsigned 64-bit integer representing the number of symbol errors that must occur within a given window to cause this event. This is defined as dot3OamErrSymPeriodThreshold = ((2^32) * dot3OamErrSymPeriodThresholdHi) + dot3OamErrSymPeriodThresholdLo If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodThreshold is one symbol errors. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. 
.1.3.6.1.2.1.158.1.5.1.4,DOT3-OAM-MIB::dot3OamErrSymPeriodThresholdLo,Unsigned32,read-write,,current,,The two objects dot3OamErrSymPeriodThresholdHi and dot3OamErrSymPeriodThresholdLo together form an unsigned 64-bit integer representing the number of symbol errors that must occur within a given window to cause this event. This is defined as dot3OamErrSymPeriodThreshold = ((2^32) * dot3OamErrSymPeriodThresholdHi) + dot3OamErrSymPeriodThresholdLo If dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored Symbol Period Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodThreshold is one symbol error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. 
.1.3.6.1.2.1.158.1.5.1.5,DOT3-OAM-MIB::dot3OamErrSymPeriodEvNotifEnable,INTEGER,read-write,,current,true(1):false(2),If true, the OAM entity should send an Event Notification OAMPDU when an Errored Symbol Period Event occurs. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. 
.1.3.6.1.2.1.158.1.5.1.6,DOT3-OAM-MIB::dot3OamErrFramePeriodWindow,Unsigned32,read-write,,current,,The number of frames over which the threshold is defined. The default value of the window is the number of minimum size Ethernet frames that can be received over the physical layer in one second. If dot3OamErrFramePeriodThreshold frame errors occur within a window of dot3OamErrFramePeriodWindow frames, an Event Notification OAMPDU should be generated with an Errored Frame Period Event TLV indicating that the threshold has been crossed in this window. 
.1.3.6.1.2.1.158.1.5.1.7,DOT3-OAM-MIB::dot3OamErrFramePeriodThreshold,Unsigned32,read-write,,current,,The number of frame errors that must occur for this event to be triggered. The default value is one frame error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. If dot3OamErrFramePeriodThreshold frame errors occur within a window of dot3OamErrFramePeriodWindow frames, an Event Notification OAMPDU should be generated with an Errored Frame Period Event TLV indicating that the threshold has been crossed in this window. 
.1.3.6.1.2.1.158.1.5.1.8,DOT3-OAM-MIB::dot3OamErrFramePeriodEvNotifEnable,INTEGER,read-write,,current,true(1):false(2),If true, the OAM entity should send an Event Notification OAMPDU when an Errored Frame Period Event occurs. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. 
.1.3.6.1.2.1.158.1.5.1.9,DOT3-OAM-MIB::dot3OamErrFrameWindow,Unsigned32,read-write,,current,,The amount of time (in 100ms increments) over which the threshold is defined. The default value is 10 (1 second). If dot3OamErrFrameThreshold frame errors occur within a window of dot3OamErrFrameWindow seconds (measured in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Event TLV indicating that the threshold has been crossed in this window. 
.1.3.6.1.2.1.158.1.5.1.10,DOT3-OAM-MIB::dot3OamErrFrameThreshold,Unsigned32,read-write,,current,,The number of frame errors that must occur for this event to be triggered. The default value is one frame error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. If dot3OamErrFrameThreshold frame errors occur within a window of dot3OamErrFrameWindow (in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Event TLV indicating the threshold has been crossed in this window. 
.1.3.6.1.2.1.158.1.5.1.11,DOT3-OAM-MIB::dot3OamErrFrameEvNotifEnable,INTEGER,read-write,,current,true(1):false(2),If true, the OAM entity should send an Event Notification OAMPDU when an Errored Frame Event occurs. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. 
.1.3.6.1.2.1.158.1.5.1.12,DOT3-OAM-MIB::dot3OamErrFrameSecsSummaryWindow,Integer32,read-write,,current,,The amount of time (in 100 ms intervals) over which the threshold is defined. The default value is 100 (10 seconds). If dot3OamErrFrameSecsSummaryThreshold frame errors occur within a window of dot3OamErrFrameSecsSummaryWindow (in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Seconds Summary Event TLV indicating that the threshold has been crossed in this window. 
.1.3.6.1.2.1.158.1.5.1.13,DOT3-OAM-MIB::dot3OamErrFrameSecsSummaryThreshold,Integer32,read-write,,current,,The number of errored frame seconds that must occur for this event to be triggered. The default value is one errored frame second. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. If dot3OamErrFrameSecsSummaryThreshold frame errors occur within a window of dot3OamErrFrameSecsSummaryWindow (in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Seconds Summary Event TLV indicating that the threshold has been crossed in this window. 
.1.3.6.1.2.1.158.1.5.1.14,DOT3-OAM-MIB::dot3OamErrFrameSecsEvNotifEnable,INTEGER,read-write,,current,true(1):false(2),If true, the local OAM entity should send an Event Notification OAMPDU when an Errored Frame Seconds Event occurs. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. 
.1.3.6.1.2.1.158.1.5.1.15,DOT3-OAM-MIB::dot3OamDyingGaspEnable,INTEGER,read-write,,current,true(1):false(2),If true, the local OAM entity should attempt to indicate a dying gasp via the OAMPDU flags field to its peer OAM entity when a dying gasp event occurs. The exact definition of a dying gasp event is implementation dependent. If the system does not support dying gasp capability, setting this object has no effect, and reading the object should always result in 'false'. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. 
.1.3.6.1.2.1.158.1.5.1.16,DOT3-OAM-MIB::dot3OamCriticalEventEnable,INTEGER,read-write,,current,true(1):false(2),If true, the local OAM entity should attempt to indicate a critical event via the OAMPDU flags to its peer OAM entity when a critical event occurs. The exact definition of a critical event is implementation dependent. If the system does not support critical event capability, setting this object has no effect, and reading the object should always result in 'false'. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. 
.1.3.6.1.2.1.158.1.6,DOT3-OAM-MIB::dot3OamEventLogTable,,not-accessible,,current,,This table records a history of the events that have occurred at the Ethernet OAM level. These events can include locally detected events, which may result in locally generated OAMPDUs, and remotely detected events, which are detected by the OAM peer entity and signaled to the local entity via Ethernet OAM. Ethernet OAM events can be signaled by Event Notification OAMPDUs or by the flags field in any OAMPDU. This table contains both threshold crossing events and non-threshold crossing events. The parameters for the threshold window, threshold value, and actual value (dot3OamEventLogWindowXX, dot3OamEventLogThresholdXX, dot3OamEventLogValue) are only applicable to threshold crossing events, and are returned as all F's (2^32 - 1) for non-threshold crossing events. Entries in the table are automatically created when such events are detected. The size of the table is implementation dependent. When the table reaches its maximum size, older entries are automatically deleted to make room for newer entries. 
.1.3.6.1.2.1.158.1.6.1,DOT3-OAM-MIB::dot3OamEventLogEntry,,not-accessible,ifIndex:dot3OamEventLogIndex,current,,An entry in the dot3OamEventLogTable. Entries are automatically created whenever Ethernet OAM events occur at the local OAM entity, and when Event Notification OAMPDUs are received at the local OAM entity (indicating that events have occurred at the peer OAM entity). The size of the table is implementation dependent, but when the table becomes full, older events are automatically deleted to make room for newer events. The table index dot3OamEventLogIndex increments for each new entry, and when the maximum value is reached, the value restarts at zero. 
.1.3.6.1.2.1.158.1.6.1.1,DOT3-OAM-MIB::dot3OamEventLogIndex,Unsigned32,not-accessible,,current,,An arbitrary integer for identifying individual events within the event log. 
.1.3.6.1.2.1.158.1.6.1.2,DOT3-OAM-MIB::dot3OamEventLogTimestamp,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the logged event. For locally generated events, the time of the event can be accurately retrieved from sysUpTime. For remotely generated events, the time of the event is indicated by the reception of the Event Notification OAMPDU indicating that the event occurred on the peer. A system may attempt to adjust the timestamp value to more accurately reflect the time of the event at the peer OAM entity by using other information, such as that found in the timestamp found of the Event Notification TLVs, which provides an indication of the relative time between events at the peer entity. 
.1.3.6.1.2.1.158.1.6.1.3,DOT3-OAM-MIB::dot3OamEventLogOui,OCTET,read-only,,current,,The OUI of the entity defining the object type. All IEEE 802.3 defined events (as appearing in [802.3ah] except for the Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of 0x0180C2. Organizations defining their own Event Notification TLVs include their OUI in the Event Notification TLV that gets reflected here. 
.1.3.6.1.2.1.158.1.6.1.4,DOT3-OAM-MIB::dot3OamEventLogType,Unsigned32,read-only,,current,,The type of event that generated this entry in the event log. When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following event types are defined: erroredSymbolEvent(1), erroredFramePeriodEvent(2), erroredFrameEvent(3), erroredFrameSecondsEvent(4), linkFault(256), dyingGaspEvent(257), criticalLinkEvent(258) The first four are considered threshold crossing events, as they are generated when a metric exceeds a given value within a specified window. The other three are not threshold crossing events. When the OUI is not 71874 (0x0180C2 in hex), then some other organization has defined the event space. If event subtyping is known to the implementation, it may be reflected here. Otherwise, this value should return all F's (2^32 - 1). 
.1.3.6.1.2.1.158.1.6.1.5,DOT3-OAM-MIB::dot3OamEventLogLocation,INTEGER,read-only,,current,local(1):remote(2),Whether this event occurred locally (local(1)), or was received from the OAM peer via Ethernet OAM (remote(2)). 
.1.3.6.1.2.1.158.1.6.1.6,DOT3-OAM-MIB::dot3OamEventLogWindowHi,Unsigned32,read-only,,current,,If the event represents a threshold crossing event, the two objects dot3OamEventWindowHi and dot3OamEventWindowLo, form an unsigned 64-bit integer yielding the window over which the value was measured for the threshold crossing event (for example, 5, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as: dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi) + dot3OamEventLogWindowLo Otherwise, this value is returned as all F's (2^32 - 1) and adds no useful information. 
.1.3.6.1.2.1.158.1.6.1.7,DOT3-OAM-MIB::dot3OamEventLogWindowLo,Unsigned32,read-only,,current,,If the event represents a threshold crossing event, the two objects dot3OamEventWindowHi and dot3OamEventWindowLo form an unsigned 64-bit integer yielding the window over which the value was measured for the threshold crossing event (for example, 5, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as: dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi) + dot3OamEventLogWindowLo Otherwise, this value is returned as all F's (2^32 - 1) and adds no useful information. 
.1.3.6.1.2.1.158.1.6.1.8,DOT3-OAM-MIB::dot3OamEventLogThresholdHi,Unsigned32,read-only,,current,,If the event represents a threshold crossing event, the two objects dot3OamEventThresholdHi and dot3OamEventThresholdLo form an unsigned 64-bit integer yielding the value that was crossed for the threshold crossing event (for example, 10, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as: dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi) + dot3OamEventLogThresholdLo Otherwise, this value is returned as all F's (2^32 -1) and adds no useful information. 
.1.3.6.1.2.1.158.1.6.1.9,DOT3-OAM-MIB::dot3OamEventLogThresholdLo,Unsigned32,read-only,,current,,If the event represents a threshold crossing event, the two objects dot3OamEventThresholdHi and dot3OamEventThresholdLo form an unsigned 64-bit integer yielding the value that was crossed for the threshold crossing event (for example, 10, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as: dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi) + dot3OamEventLogThresholdLo Otherwise, this value is returned as all F's (2^32 - 1) and adds no useful information. 
.1.3.6.1.2.1.158.1.6.1.10,DOT3-OAM-MIB::dot3OamEventLogValue,Counter64,read-only,,current,,If the event represents a threshold crossing event, this value indicates the value of the parameter within the given window that generated this event (for example, 11, when 11 occurrences happened in 5 seconds while the threshold was 10). Otherwise, this value is returned as all F's (2^64 - 1) and adds no useful information. 
.1.3.6.1.2.1.158.1.6.1.11,DOT3-OAM-MIB::dot3OamEventLogRunningTotal,Counter64,read-only,,current,,Each Event Notification TLV contains a running total of the number of times an event has occurred, as well as the number of times an Event Notification for the event has been transmitted. For non-threshold crossing events, the number of events (dot3OamLogRunningTotal) and the number of resultant Event Notifications (dot3OamLogEventTotal) should be identical. For threshold crossing events, since multiple occurrences may be required to cross the threshold, these values are likely different. This value represents the total number of times this event has happened since the last reset (for example, 3253, when 3253 symbol errors have occurred since the last reset, which has resulted in 51 symbol error threshold crossing events since the last reset). 
.1.3.6.1.2.1.158.1.6.1.12,DOT3-OAM-MIB::dot3OamEventLogEventTotal,Unsigned32,read-only,,current,,Each Event Notification TLV contains a running total of the number of times an event has occurred, as well as the number of times an Event Notification for the event has been transmitted. For non-threshold crossing events, the number of events (dot3OamLogRunningTotal) and the number of resultant Event Notifications (dot3OamLogEventTotal) should be identical. For threshold crossing events, since multiple occurrences may be required to cross the threshold, these values are likely different. This value represents the total number of times one or more of these occurrences have resulted in an Event Notification (for example, 51 when 3253 symbol errors have occurred since the last reset, which has resulted in 51 symbol error threshold crossing events since the last reset). 
.1.3.6.1.2.1.158.2,DOT3-OAM-MIB::dot3OamConformance,,,,,,
.1.3.6.1.2.1.158.2.1,DOT3-OAM-MIB::dot3OamGroups,,,,,,
.1.3.6.1.2.1.158.2.1.1,DOT3-OAM-MIB::dot3OamControlGroup,,,,,,A collection of objects providing the abilities, configuration, and status of an Ethernet OAM entity. 
.1.3.6.1.2.1.158.2.1.2,DOT3-OAM-MIB::dot3OamPeerGroup,,,,,,A collection of objects providing the abilities, configuration, and status of a peer Ethernet OAM entity. 
.1.3.6.1.2.1.158.2.1.3,DOT3-OAM-MIB::dot3OamStatsBaseGroup,,,,,,A collection of objects providing the statistics for the number of various transmit and receive events for OAM on an Ethernet-like interface. Note that all of these counters must be supported even if the related function (as described in dot3OamFunctionsSupported) is not supported. 
.1.3.6.1.2.1.158.2.1.4,DOT3-OAM-MIB::dot3OamLoopbackGroup,,,,,,A collection of objects for controlling the OAM remote loopback function. 
.1.3.6.1.2.1.158.2.1.5,DOT3-OAM-MIB::dot3OamErrSymbolPeriodEventGroup,,,,,,A collection of objects for configuring the thresholds for an Errored Symbol Period Event. Each [802.3ah] defined Event Notification TLV has its own conformance group because each event can be implemented independently of any other. 
.1.3.6.1.2.1.158.2.1.6,DOT3-OAM-MIB::dot3OamErrFramePeriodEventGroup,,,,,,A collection of objects for configuring the thresholds for an Errored Frame Period Event. Each [802.3ah] defined Event Notification TLV has its own conformance group because each event can be implemented independently of any other. 
.1.3.6.1.2.1.158.2.1.7,DOT3-OAM-MIB::dot3OamErrFrameEventGroup,,,,,,A collection of objects for configuring the thresholds for an Errored Frame Event. Each [802.3ah] defined Event Notification TLV has its own conformance group because each event can be implemented independently of any other. 
.1.3.6.1.2.1.158.2.1.8,DOT3-OAM-MIB::dot3OamErrFrameSecsSummaryEventGroup,,,,,,A collection of objects for configuring the thresholds for an Errored Frame Seconds Summary Event. Each [802.3ah] defined Event Notification TLV has its own conformance group because each event can be implemented independently of any other. 
.1.3.6.1.2.1.158.2.1.9,DOT3-OAM-MIB::dot3OamFlagEventGroup,,,,,,A collection of objects for configuring the sending OAMPDUs with the critical event flag or dying gasp flag enabled. 
.1.3.6.1.2.1.158.2.1.10,DOT3-OAM-MIB::dot3OamEventLogGroup,,,,,,A collection of objects for configuring the thresholds for an Errored Frame Seconds Summary Event and maintaining the event information. 
.1.3.6.1.2.1.158.2.1.11,DOT3-OAM-MIB::dot3OamNotificationGroup,,,,,,A collection of notifications used by Ethernet OAM to signal to a management entity that local or remote events have occurred on a specified Ethernet link. 
.1.3.6.1.2.1.158.2.2,DOT3-OAM-MIB::dot3OamCompliances,,,,,,
.1.3.6.1.2.1.158.2.2.1,DOT3-OAM-MIB::dot3OamCompliance,,,,,,The compliance statement for managed entities supporting OAM on Ethernet-like interfaces. 
.1.3.6.1.2.1.159,T11-FC-FABRIC-LOCK-MIB::t11FabricLockMIB,,,,,,The MIB module for the management of locks on a Fibre Channel Fabric. A Fibre Channel Fabric lock is used to ensure serialized access to some types of management data related to a Fabric, e.g., the Fabric's Zoning Database. Some (managing) applications generate Fabric locks by initiating server sessions. Server sessions are defined generically in FC-GS-5 to represent a collection of one or more requests to the session's server, e.g., to the Zone Server. Such a session is started by a Server Session Begin (SSB) request, and terminated by a Server Session End (SSE) request. The switch receiving the SSB is called the 'managing' switch. Some applications require the 'managing' switch to lock the Fabric for the particular application, e.g., for Enhanced Zoning, before it can respond successfully to the SSB. On receipt of the subsequent SSE, the lock is released. For this usage, the managing switch sends an Acquire Change Authorization (ACA) request to other switches to lock the Fabric. For some other applications, a managing switch locks the Fabric using an Enhanced Acquire Change Authorization (EACA) request, which identifies the application on whose behalf the Fabric is being locked with an Application_ID. Fabric locks can also be requested more directly, e.g., through the use of this MIB. In these situations, the term 'managing' switch is used to indicate the switch that receives such a request and executes it by issuing either ACA or EACA requests to other switches in the Fabric. This MIB module defines information about the 'managing' switch for currently-active Fabric locks. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4936; see the RFC itself for full legal notices.
.1.3.6.1.2.1.159.0,T11-FC-FABRIC-LOCK-MIB::t11FLockMIBNotifications,,,,,,
.1.3.6.1.2.1.159.1,T11-FC-FABRIC-LOCK-MIB::t11FLockMIBObjects,,,,,,
.1.3.6.1.2.1.159.1.1,T11-FC-FABRIC-LOCK-MIB::t11FLockConfiguration,,,,,,
.1.3.6.1.2.1.159.1.1.1,T11-FC-FABRIC-LOCK-MIB::t11FLockTable,,not-accessible,,current,,A table containing information about the 'managing' switch of each current Fabric lock, e.g., for the types of Servers defined in FC-GS-5. Each entry in this table represents either: 1) a current Fabric lock, 2) an in-progress attempt, requested via SNMP, to set up a lock, or 3) a failed attempt, requested via SNMP, to set up a lock. If an entry is created via t11FLockRowStatus, but the attempt to obtain the lock fails, then the entry continues to exist until it is deleted via t11FLockRowStatus, or it is overwritten by the lock being established via a means other than SNMP. However, rows created via t11FLockRowStatus are not retained over restarts.
.1.3.6.1.2.1.159.1.1.1.1,T11-FC-FABRIC-LOCK-MIB::t11FLockEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FLockFabricIndex:t11FLockApplicationID,current,,Each entry contains information specific to a current Fabric lock set up by a particular 'managing' switch on a particular Fabric. The 'managing switch' is identified by values of fcmInstanceIndex and fcmSwitchIndex. Server sessions for several different types of servers are defined in FC-GS-5. The behavior of a server with respect to commands received within a server session is specified for each type of server. For some types, parameter changes can only be made within the context of a session, and the setting up of a session requires that the Fabric be locked. A Fabric is locked by one switch, called the 'managing' switch, sending Acquire Change Authorization (ACA) requests to all other switches in the Fabric. For other applications, a Fabric lock is established by the 'managing' switch sending Enhanced Acquire Change Authorization (EACA) requests to other switches in the Fabric. Each EACA request includes an Application_ID value to identify the application requesting the lock. For the benefit of this MIB module, a distinct value of Application_ID has also been assigned/reserved (see ANSI INCITS T11/06-679v0, titled 'FC-SW-5 Letter to T11.5') as a means of distinguishing locks established via Acquire Change Authorization (ACA) requests. This additional assignment allows an Application_ID to be used to uniquely identify any active lock amongst all those established by either an EACA or an ACA. Whenever a Fabric is locked, by the sending of either an ACA or an EACA, a row gets created in the representation of this table for the 'managing' switch. In order to process SNMP SetRequests that make parameter changes for the relevant types of servers (e.g., to the Zoning Database), the SNMP agent must get serialized access to the Fabric (for the relevant type of management data), i.e., the Fabric must be locked by creating an entry in this table via an SNMP SetRequest. Creating an entry in this table via an SNMP SetRequest causes an ACA or an EACA to be sent to all other switches in the Fabric. The value of t11FLockApplicationID for such an entry determines whether an ACA or an EACA is sent. If an entry in this table is created by an SNMP SetRequest, the value of the t11FLockInitiatorType object in that entry will normally be 'snmp'. A row for which the value of t11FLockInitiatorType is not 'snmp' cannot be modified via SNMP. In particular, it cannot be deleted via t11FLockRowStatus. Note that it's possible for a row to be created by an SNMP SetRequest, but for the setup of the lock to fail, and immediately thereafter be replaced by a lock successfully set up by some other means; in such a case, the value of t11FLockInitiatorType would change as and when the lock was set up by the other means, and so the row could not thereafter be deleted via t11FLockRowStatus. FC-GS-5 mentions various error situations in which a Fabric lock is released so as to avoid a deadlock. In such situations, the agent removes the corresponding row in this table as and when the lock is released. This can happen for all values of t11FLockInitiatorType.
.1.3.6.1.2.1.159.1.1.1.1.1,T11-FC-FABRIC-LOCK-MIB::t11FLockFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures, and this index value is used to uniquely identify a particular (physical or virtual) Fabric within a physical infrastructure. In a Fabric conformant to versions earlier than FC-SW-4, only a single Fabric could operate within a physical infrastructure, and thus, the value of this Fabric Index was defined to always be 1.
.1.3.6.1.2.1.159.1.1.1.1.2,T11-FC-FABRIC-LOCK-MIB::t11FLockApplicationID,OCTET,not-accessible,,current,,The Application_ID value that identifies the type of application for which the Fabric is locked. A lock established via Acquire Change Authorization (ACA) does not, strictly speaking, have an Application_ID value. However, the value 'FF'h (255 decimal) has been reserved by T11 to be used as the value of this MIB object as and when a lock is established by an ACA. This value was initially documented in a letter from the FC-SW-5 Editor to T11.5, which was approved by the T11 and T11.5 plenary meetings on October 5, 2006.
.1.3.6.1.2.1.159.1.1.1.1.3,T11-FC-FABRIC-LOCK-MIB::t11FLockInitiatorType,INTEGER,read-only,,current,other(1):ssb(2):cli(3):snmp(4),This object specifies what type of initiator generated the request that caused this lock to be established: other - none of the following. ssb - this lock was established due to the receipt of an SSB, e.g., from a GS-5 client. cli - this lock was established in order to process a Command Line Interface (CLI) command. snmp - this lock was established as a result of an SNMP SetRequest. 
.1.3.6.1.2.1.159.1.1.1.1.4,T11-FC-FABRIC-LOCK-MIB::t11FLockInitiator,OCTET,read-only,,current,,This object specifies the initiator whose request caused this lock to be established. If the value of the corresponding instance of t11FLockInitiatorType is 'ssb', this object will contain the FC_ID of the client that issued the Server Session Begin (SSB) that required the lock to be established. If the value of the corresponding instance of t11FLockInitiatorType object is 'cli', this object will contain the user name of the CLI (Command Line Interface) user on whose behalf the lock was established. If the value of the corresponding instance of t11FLockInitiatorType is 'snmp', this object will contain the SNMP securityName used by the SNMPv3 message containing the SetRequest that created this row. (If the row was created via SNMPv1 or SNMPv2c, then the appropriate value of the snmpCommunitySecurityName is used.)
.1.3.6.1.2.1.159.1.1.1.1.5,T11-FC-FABRIC-LOCK-MIB::t11FLockInitiatorIpAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the type of IP address contained in the corresponding instance of t11FLockInitiatorIpAddr. If the IP address of the location of the initiator is unknown or not applicable, this object has the value: 'unknown'.
.1.3.6.1.2.1.159.1.1.1.1.6,T11-FC-FABRIC-LOCK-MIB::t11FLockInitiatorIpAddr,OCTET,read-only,,current,,This object specifies the IP address of the location of the initiator that established this lock via a request of the type given by the corresponding instance of t11FLockInitiatorType. In cases where the corresponding instance of t11FLockInitiatorIpAddrType has the value: 'unknown', the value of this object is the zero-length string.
.1.3.6.1.2.1.159.1.1.1.1.7,T11-FC-FABRIC-LOCK-MIB::t11FLockStatus,INTEGER,read-only,,current,active(1):settingUp(2):rejectFailure(3):otherFailure(4),This object gives the current status of the lock: 'active' -- the lock is currently established. 'settingUp' -- the 'managing' switch is currently attempting to set up the lock, e.g., it is waiting to receive Accepts for ACAs from every switch in the Fabric. 'rejectFailure' -- the 'managing' switch's attempt to set up the lock was rejected with the reason codes given by: t11FLockRejectReasonCode, t11FLockRejectReasonCodeExp and t11FLockRejectReasonVendorCode. 'otherFailure' -- the 'managing' switch's attempt to set up the lock failed (but no reason codes are available). For values of t11FLockInitiatorType other than 'snmp', a row is only required to be instantiated in this table when the value of this object is 'active'. If the value of the corresponding instance of t11FLockInitiatorType is 'snmp', the initial value of this object when the row is first created is 'settingUp'. As and when the setup succeeds, the value transitions to 'active'. If the setup fails, the value transitions to either 'rejectFailure' or 'otherFailure'. Note that such a failure value is overwritten on the next attempt to obtain the lock, which could be immediately after the failure, e.g., by a GS-5 client. When the value of this object is 'rejectFailure', the rejection's reason codes are given by the corresponding values of t11FLockRejectReasonCode, t11FLockRejectReasonCodeExp and t11FLockRejectReasonVendorCode.
.1.3.6.1.2.1.159.1.1.1.1.8,T11-FC-FABRIC-LOCK-MIB::t11FLockRejectReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),When the value of the corresponding instance of t11FLockStatus is 'rejectFailure', this object contains the rejection's reason code.
.1.3.6.1.2.1.159.1.1.1.1.9,T11-FC-FABRIC-LOCK-MIB::t11FLockRejectReasonCodeExp,OCTET,read-only,,current,,When the value of the corresponding instance of t11FLockStatus is 'rejectFailure', this object contains the rejection's reason code explanation.
.1.3.6.1.2.1.159.1.1.1.1.10,T11-FC-FABRIC-LOCK-MIB::t11FLockRejectReasonVendorCode,OCTET,read-only,,current,,When the value of the corresponding instance of t11FLockStatus is 'rejectFailure', this object contains the rejection's vendor-specific code.
.1.3.6.1.2.1.159.1.1.1.1.11,T11-FC-FABRIC-LOCK-MIB::t11FLockRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. A row in this table can be modified or deleted via this object only when the row's value of t11FLockInitiatorType is 'snmp'.
.1.3.6.1.2.1.159.2,T11-FC-FABRIC-LOCK-MIB::t11FLockMIBConformance,,,,,,
.1.3.6.1.2.1.159.2.1,T11-FC-FABRIC-LOCK-MIB::t11FLockMIBCompliances,,,,,,
.1.3.6.1.2.1.159.2.1.1,T11-FC-FABRIC-LOCK-MIB::t11FLockMIBCompliance,,,,,,The compliance statement for entities that support Fabric locks in support of GS-5 Server applications.
.1.3.6.1.2.1.159.2.2,T11-FC-FABRIC-LOCK-MIB::t11FLockMIBGroups,,,,,,
.1.3.6.1.2.1.159.2.2.1,T11-FC-FABRIC-LOCK-MIB::t11FLockActiveGroup,,,,,,A collection of objects containing information about current Fabric locks.
.1.3.6.1.2.1.160,T11-FC-ZONE-SERVER-MIB::t11ZoneServerMIB,,,,,,The MIB module for the management of Fibre Channel Zoning Servers, both for Basic Zoning Management and for Enhanced Zoning Management, as defined in the FC-GS-5 specification. FC-GS-5 defines (in-band) management operations for manipulating the Zone Set Database, some for use in Basic mode (e.g., 'Add Zone Set (AZS)', etc.), and some for use in Enhanced mode (e.g., Create Zone Set (CZS)', etc.). When Enhanced Zoning Management is in use, FC-GS-5 requires that these in-band management operations be rejected unless they are issued within the context of a GS-5 server session. The use of a server session ensures serialized access to the Zoning Database since the Fabric lock for the Zone Server must be obtained as a part of establishing the server session to the Zone Server. Thus, if and when this MIB is used for Enhanced Zoning Management, SNMP SetRequests that request the modification of zoning definitions must be serialized with respect to the GS-5 requests to modify the Zoning Database. This is achieved by requiring that an SNMP management application must first obtain the Fabric lock for the Zone Server before attempting to modify any zoning definitions. The companion T11-FC-FABRIC-LOCK-MIB module is defined as a means of obtaining the Fabric lock for the Zone Server (or any other server). In Enhanced Zoning Management, a Zone Server keeps track of changes requested in the zoning definitions, but does not update its Zone Set Database unless there is (and until there is) a 'commit' operation. To model this behavior, this MIB module assumes that a Zone Server (in Enhanced mode) takes a snapshot of its Zone Set Database as and when the Fabric lock (for the Zone Server application) is obtained; this snapshot is used to create what is herein called the 'copy' database. It is this 'copy' database that is then updated by SNMP SetRequests (while the Fabric is locked). If and when a 'commit' operation is requested (while the Fabric is still locked), the 'copy' database is then used to overwrite the previously committed contents of the Zone Set Database, and the new Zone Set Database is distributed to all other switches in the Fabric. When the lock is released, any changes made that were not 'committed' are discarded. When this MIB is used for Basic Zoning Management, the same set of MIB objects as used for Enhanced mode are used to make changes to the Database of a Zone Server on a particular switch, but the changes take immediate effect at that switch without an explicit commit. The distribution of those changes to Zone Servers on other switches in the Fabric is subsequently requested through the use of a separate set of MIB objects. The management information specified in this MIB module includes the Zoning Database for each of one or more Fibre Channel Fabrics. A Zoning Database is a combination of the Fabric's Zone Set Database and its Active Zone Set. The Active Zone Set is the Zone Set currently enforced by the Fabric; a Zone Set Database is a database of the Zone Sets available to be activated within a Fabric. All the MIB objects representing a Zone Set Database are modifiable at any time (irrespective of the value of any RowStatus object), whereas all objects representing the Active Zone Set are always read-only (except to deactivate it and/or activate a different one). Copyright (C) The IETF Trust (2007). This version of this MIB
.1.3.6.1.2.1.160.0,T11-FC-ZONE-SERVER-MIB::t11ZsMIBNotifications,,,,,,
.1.3.6.1.2.1.160.0.1,T11-FC-ZONE-SERVER-MIB::t11ZsRequestRejectNotify,,,,,,This notification is generated whenever a Zone Server (indicated by the value of t11FamLocalSwitchWwn) rejects a request. The value of t11ZsRejectCtCommandString indicates the rejected request, and the values of t11ZsRejectReasonCode, t11ZsRejectReasonCodeExp and t11ZsRejectReasonVendorCode indicate the reason for the rejection. The value of t11ZsRequestClient indicates the source of the request.
.1.3.6.1.2.1.160.0.2,T11-FC-ZONE-SERVER-MIB::t11ZsMergeFailureNotify,,,,,,This notification indicates that a Zone merge failure has occurred on the Fabric indicated by the value of t11ZsFabricIndex, on the interface indicated by the value of ifIndex. If multiple Virtual Fabrics are configured on an interface, and all have a Zone merge failure at the same time, then just one notification is generated and t11ZsFabricIndex has the value 4096.
.1.3.6.1.2.1.160.0.3,T11-FC-ZONE-SERVER-MIB::t11ZsMergeSuccessNotify,,,,,,This notification indicates that a successful Zone merge has occurred on the Fabric indicated by the value of t11ZsFabricIndex, on the interface indicated by the value of ifIndex. If multiple Virtual Fabrics are configured on an interface, and all have a successful Zone Merge at the same time, then just one notification is generated and t11ZsFabricIndex has the value 4096.
.1.3.6.1.2.1.160.0.4,T11-FC-ZONE-SERVER-MIB::t11ZsDefZoneChangeNotify,,,,,,This notification indicates that the value of a Default Zone Setting has changed. The value of t11ZsServerDefaultZoneSetting contains the value after the change.
.1.3.6.1.2.1.160.0.5,T11-FC-ZONE-SERVER-MIB::t11ZsActivateNotify,,,,,,This notification is generated whenever a switch (indicated by the value of t11FamLocalSwitchWwn) activates/deactivates a Zone Set on a Fabric. The t11ZsActivateResult object denotes the outcome of the activation/deactivation.
.1.3.6.1.2.1.160.1,T11-FC-ZONE-SERVER-MIB::t11ZsMIBObjects,,,,,,
.1.3.6.1.2.1.160.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsConfiguration,,,,,,
.1.3.6.1.2.1.160.1.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsServerTable,,not-accessible,,current,,A table containing information about the Zone Servers on each Fabric in one or more switches, and providing the capability to perform operations on their Zone Server databases.
.1.3.6.1.2.1.160.1.1.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsServerEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex,current,,Each entry contains information specific to a Zone Server for a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). The persistence across reboots of writable values in a row of this table is given by the instance of t11ZsServerDatabaseStorageType in that row.
.1.3.6.1.2.1.160.1.1.1.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsServerFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric.
.1.3.6.1.2.1.160.1.1.1.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsServerCapabilityObject,BITS,read-only,,current,enhancedMode(0):zoneSetDb(1):activateDirect(2):hardZoning(3),This bitmap represents the capability of the switch on this Fabric: 'enhancedMode' - able to support enhanced Zoning mode of operation. 'zoneSetDb' - able to support maintaining of a Zone Set Database. 'activateDirect' - able to support the Activate Direct command. 'hardZoning' - able to support Hard Zoning.
.1.3.6.1.2.1.160.1.1.1.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsServerDatabaseStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization, on a particular switch, of the Zone Set database for a particular Fabric. Specifically, each row in the following tables: t11ZsSetTable t11ZsZoneTable t11ZsSetZoneTable t11ZsAliasTable t11ZsZoneMemberTable t11ZsAttribBlockTable t11ZsAttribTable has a StorageType as specified by the instance of this object that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex. The value of this object is also used to indicate the persistence across reboots of writable values in its row of the t11ZsServerTable, as well as the corresponding row in the t11ZsNotifyControlTable. If an instance of this object has the value 'permanent(4)', the Zone Set database for the given Fabric on the given switch is not required to be writeable.
.1.3.6.1.2.1.160.1.1.1.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsServerDistribute,INTEGER,read-write,,current,noop(1):zoneSetDb(2),This object can be set only in Basic mode. When set to the value 'zoneSetDb', it requests that the Zone Set database of a particular switch for a particular Fabric be distributed to every other switch in that Fabric, e.g., by using Stage Fabric Configuration Update (SFC) and Update Fabric Configuration (UFC) requests. Setting this object to 'noop' has no effect. When read, the value of this object is always 'noop'. When the corresponding instance of t11ZsServerOperationMode has the value 'enhanced', or when the corresponding instance of t11ZsZoneSetResult has the value 'inProgress', it is inconsistent to try to set the value of this object.
.1.3.6.1.2.1.160.1.1.1.1.5,T11-FC-ZONE-SERVER-MIB::t11ZsServerCommit,INTEGER,read-write,,current,commitZoneChanges(1):noop(2),This object is only used in Enhanced mode. In Enhanced mode, it can only be modified when the Fabric lock for the Zone Server on the particular Fabric has been obtained for use by SNMP SetRequests, and even then, only by the SNMP entity identified by the value of corresponding instance of t11FLockInitiator. Setting the object requests an action: commitZoneChanges - requests that the changes made within this session to the Zone Set Database be committed. noop - requests nothing. When read, the value is always 'noop'.
.1.3.6.1.2.1.160.1.1.1.1.6,T11-FC-ZONE-SERVER-MIB::t11ZsServerResult,INTEGER,read-only,,current,none(1):inProgress(2):success(3):rejectFailure(4):otherFailure(5),In Basic mode, this object indicates the status/result of the last distribution of the Zone Set database that was invoked via the corresponding instance of t11ZsZoneSetDistribute, e.g., the status/result of Stage Fabric Configuration Update (SFC) request(s) used to implement the setting of t11ZsZoneSetDistribute. In Enhanced mode, this object indicates the status/result of the last commit of changes to the Zone Set database that was invoked via the corresponding instance of t11ZsServerCommit. 'none' - no distribution/commit invoked via the corresponding instance of t11ZsZoneSetDistribute (Basic mode) or t11ZsServerCommit (Enhanced mode). 'inProgress' - distribution/commit is still in progress. 'success' - distribution/commit completed successfully. 'rejectFailure' - distribution/commit failed due to an SW_RJT. 'otherFailure' - distribution/commit failed for some other reason. When the value is 'rejectFailure', the corresponding instances of t11ZsServerReasonCode, t11ZsServerReasonCodeExp and t11ZsServerReasonVendorCode contain the reason codes. 
.1.3.6.1.2.1.160.1.1.1.1.7,T11-FC-ZONE-SERVER-MIB::t11ZsServerReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),When the corresponding instance of t11ZsZoneSetResult has the value 'rejectFailure', this object contains the rejection's reason code. When the corresponding instance of t11ZsServerResult has a value other than 'rejectFailure', this object should contain the value 'none'.
.1.3.6.1.2.1.160.1.1.1.1.8,T11-FC-ZONE-SERVER-MIB::t11ZsServerReasonCodeExp,OCTET,read-only,,current,,When the corresponding instance of t11ZsZoneSetResult has the value 'rejectFailure', this object contains the rejection's reason code explanation. When the corresponding instance of t11ZsServerResult has a value other than 'rejectFailure', this object should contain the zero-length string.
.1.3.6.1.2.1.160.1.1.1.1.9,T11-FC-ZONE-SERVER-MIB::t11ZsServerReasonVendorCode,OCTET,read-only,,current,,When the corresponding instance of t11ZsZoneSetResult has the value 'rejectFailure', this object contains the rejection's reason vendor-specific code. When the corresponding instance of t11ZsServerResult has a value other than 'rejectFailure', this object should contain the zero-length string.
.1.3.6.1.2.1.160.1.1.1.1.10,T11-FC-ZONE-SERVER-MIB::t11ZsServerLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time of the last change (creation, modification, or deletion) to the Zone Set database for the Zone Server for a particular Fabric. If said Zone Set database has not changed since the last re-initialization of the local network management system, then this object will contain a zero value.
.1.3.6.1.2.1.160.1.1.1.1.11,T11-FC-ZONE-SERVER-MIB::t11ZsServerHardZoning,INTEGER,read-only,,current,true(1):false(2),This object indicates whether this switch, if and when it is in Basic mode, enforces Hard Zoning on this Fabric.
.1.3.6.1.2.1.160.1.1.1.1.12,T11-FC-ZONE-SERVER-MIB::t11ZsServerReadFromDatabase,INTEGER,read-write,,current,committedDB(1):copyDB(2),In Enhanced mode, this object specifies whether subsequent SNMP Responses (generated by the local SNMP agent) to operations that read the configuration of Zone Sets, Zones, Members, Aliases and Attributes will reflect the values stored in the current (committed) Zone Set database, or those stored in the 'copy' database. In Basic mode, the value of this object is always 'committedDB' (since there is no 'copy' database in Basic mode). In SNMP agents that don't support write access to the Zone Set database, this object is always 'committedDB' (since the copy database, if it were to exist, would be identical).
.1.3.6.1.2.1.160.1.1.1.1.13,T11-FC-ZONE-SERVER-MIB::t11ZsServerOperationMode,INTEGER,read-write,,current,basic(1):enhanced(2),The operational mode of the Zone Server. Setting this object to 'enhanced' is a request that the mode of operation of the Zone Server be Enhanced mode, which is only possible if all devices in the Fibre Channel Fabric are capable of working in Enhanced mode. If not, the request will fail and the corresponding value of t11ZsServerChangeModeResult will so indicate. Setting this object to 'basic' is a request that the mode of operation of the Zone Server be Basic mode. However, such a set may fail while operating in Enhanced mode, since FC-GS-5 makes no provision for changing (back) to Basic mode. Note that setting this object does not cause or require that the Fabric lock for the Zone Server be obtained. However, when this object has the value 'enhanced', any SNMP SetRequests that attempt to modify the copy database cannot be successful if the Fabric lock has not been obtained or has since been released.
.1.3.6.1.2.1.160.1.1.1.1.14,T11-FC-ZONE-SERVER-MIB::t11ZsServerChangeModeResult,INTEGER,read-only,,current,success(1):failure(2):inProgress(3):none(4),When this object has the value of 'success' or 'failure', the value indicates the outcome of the most recent request, invoked via t11ZsServerOperationMode, to change the mode of operation of the Zone Server. When such a request is in progress, this object has the value 'inProgress'. Prior to the first such request, the value of this object is 'none'.
.1.3.6.1.2.1.160.1.1.1.1.15,T11-FC-ZONE-SERVER-MIB::t11ZsServerDefaultZoneSetting,INTEGER,read-write,,current,permit(1):deny(2),This object controls the Enhanced Zoning flag that governs the behavior of the Default Zone on this Fabric. If this object is set to 'permit', then the members of the Default Zone on this Fabric can communicate with each other. If this object is set to 'deny', then the members of the Default Zone on this Fabric cannot communicate with each other.
.1.3.6.1.2.1.160.1.1.1.1.16,T11-FC-ZONE-SERVER-MIB::t11ZsServerMergeControlSetting,INTEGER,read-write,,current,allow(1):restrict(2),This object controls the Enhanced Zoning flag that indicates the Merge Control Setting for this Fabric: 'allow' - a switch may join the Fabric only if its Zoning Database is able to merge with the Fabric's Zoning Database. 'restrict' - a switch may join the Fabric only if its Zoning Database is equal to the Fabric's Zoning Database.
.1.3.6.1.2.1.160.1.1.1.1.17,T11-FC-ZONE-SERVER-MIB::t11ZsServerDefZoneBroadcast,INTEGER,read-write,,current,true(1):false(2),This object controls an Enhanced Zoning capability: it indicates whether Broadcast Zoning is enabled on the Default Zone on this Fabric. If this object is set to 'true', then it is enabled. If this object is set to 'false', then it is disabled. If broadcast Zoning is enabled on a Default Zone, then broadcast frames generated by a member in that Default Zone will be restricted to members in that Default Zone.
.1.3.6.1.2.1.160.1.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsSetTable,,not-accessible,,current,,A table containing information on every Zone Set in the Zone Set database of the Zone Servers on each Fabric in one or more switches. In Enhanced mode, changes to a database made via this table are always made to the 'copy' database, but values read from this table reflect the contents of either the 'copy' database or the current (committed) database as indicated by the corresponding value of t11ZsServerReadFromDatabase.
.1.3.6.1.2.1.160.1.1.2.1,T11-FC-ZONE-SERVER-MIB::t11ZsSetEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsSetIndex,current,,Each entry contains information about a Zone Set in the Zone Set database of a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). A Zone Set can be created in an existing Zone Set database, and can contain zero or more existing Zones. As and when new Zones are created (as rows in the t11ZsZoneTable), they can be added to a Zone Set by creating an entry for each in the t11ZsSetZoneTable. Deleting a row from this table deletes the Zone Set from the Zone Set database maintained by the Zone Server, but does not otherwise affect the Zone Server. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.2.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsSetIndex,Unsigned32,not-accessible,,current,,The index of a Zone Set. This object uniquely identifies a Zone Set in the Zone Set database for a particular Fabric on a particular switch.
.1.3.6.1.2.1.160.1.1.2.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsSetName,OCTET,read-create,,current,,The name of this Zone Set. The t11ZsSetName should be unique within a Fabric. The Zone Set can be renamed at any time (i.e., even when the row in an active state) by setting this object to a new value.
.1.3.6.1.2.1.160.1.1.2.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsSetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object cannot be set to 'active' unless the corresponding value of t11ZsSetName is unique within the Fabric's Zone Server database on this switch.
.1.3.6.1.2.1.160.1.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsZoneTable,,not-accessible,,current,,This table gives information on all the Zones in the Zone Set database of the Zone Servers on each Fabric in one or more switches. In Enhanced mode, changes to a database made via this table are always made to the 'copy' database, but values read from this table reflect the contents of either the 'copy' database or the current (committed) database as indicated by the corresponding value of t11ZsServerReadFromDatabase.
.1.3.6.1.2.1.160.1.1.3.1,T11-FC-ZONE-SERVER-MIB::t11ZsZoneEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsZoneIndex,current,,Each entry contains information about a Zone in the Zone Set database of a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). A Zone can be created in an existing Zone Set database, by first creating an entry in this table, and then adding members to it by creating entries in the t11ZsZoneMemberTable. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.3.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsZoneIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this Zone within a particular Fabric's Zone Set database on a particular switch.
.1.3.6.1.2.1.160.1.1.3.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsZoneName,OCTET,read-create,,current,,The name of this Zone. The t11ZsZoneName should be unique within a Fabric. The Zone can be renamed by setting this object to a new value.
.1.3.6.1.2.1.160.1.1.3.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsZoneAttribBlock,Unsigned32,read-create,,current,,This object specifies the index value of the Zone Attribute Block that contains the Attributes of this Zone. In Enhanced mode, a value of zero indicates this Zone has no Zone Attributes. In Basic mode, this object always has the value of zero.
.1.3.6.1.2.1.160.1.1.3.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsZoneRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object cannot be set to 'active' unless the corresponding value of t11ZsZoneName is unique within the Fabric's Zone Server database on this switch.
.1.3.6.1.2.1.160.1.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsSetZoneTable,,not-accessible,,current,,This table specifies which Zones belong to which Zone Sets in the Zone Set database of the Zone Servers on each Fabric in one or more switches.
.1.3.6.1.2.1.160.1.1.4.1,T11-FC-ZONE-SERVER-MIB::t11ZsSetZoneEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsSetIndex:t11ZsZoneIndex,current,,Each entry specifies that a particular Zone (identified by the value of t11ZsZoneIndex) is one of the Zones that form a particular Zone Set (identified by the value of t11ZsSetIndex) in the Zone Set database of a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). When a row in this table exists, it references one row in the t11ZsSetTable and one row in the t11ZsZoneTable. The agent must ensure that both such rows when referenced by an active row in this table, do exist and have a status of 'active', either by refusing to create new rows in this table, or by automatically deleting rows in this table. An 'active' row in this table references one row in the t11ZsSetTable and one in the t11ZsZoneTable. The agent must ensure that all such referenced rows exist with a status of 'active', either by refusing to create new active rows in this table, or by automatically deleting any rows in this table that reference a deleted row. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.4.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsSetZoneRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row.
.1.3.6.1.2.1.160.1.1.5,T11-FC-ZONE-SERVER-MIB::t11ZsAliasTable,,not-accessible,,current,,This table contains information about the Zone Aliases in the Zone Set database of the Zone Servers on each Fabric in one or more switches. In Enhanced mode, changes to a database made via this table are always made to the 'copy' database, but values read from this table reflect the contents of either the 'copy' database or the current (committed) database as indicated by the corresponding value of t11ZsServerReadFromDatabase.
.1.3.6.1.2.1.160.1.1.5.1,T11-FC-ZONE-SERVER-MIB::t11ZsAliasEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsAliasIndex,current,,Each entry contains information about a Zone Alias in the Zone Set database of a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). A Zone Member is added to a Zone Alias by creating an entry in the t11ZsZoneMemberTable pointing to a row of this table via t11ZsAliasIndex, i.e.,: - t11ZsZoneMemberParentType = 'alias', - t11ZsZoneMemberParentIndex = Alias's t11ZsAliasIndex, - t11ZsZoneMemberFormat != '05 - Alias Name', and - t11ZsZoneMemberID = Member's identifier. A Zone Alias is added to a Zone by creating an entry in the t11ZsZoneMemberTable pointing to a row of this table via t11ZsAliasName, i.e.,: - t11ZsZoneMemberParentType = 'zone', and - t11ZsZoneMemberParentIndex = Zone's t11ZsZoneIndex, - t11ZsZoneMemberFormat = '05 - Alias Name', - t11ZsZoneMemberID = Alias's t11ZsAliasName. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.5.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsAliasIndex,Unsigned32,not-accessible,,current,,An index value which uniquely identifies this Zone Alias within the Zone Set database of a particular Fabric on a particular switch.
.1.3.6.1.2.1.160.1.1.5.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsAliasName,OCTET,read-create,,current,,The name of this Zone Alias. The name of the Zone Alias should be unique within a Fabric. The Zone Alias can be renamed by setting this object to a new value if and when it is not in a Zone, i.e., if and only if the current name is not the value of any t11ZsZoneMemberID in the same Zone Set database.
.1.3.6.1.2.1.160.1.1.5.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsAliasRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object cannot be set to 'active' unless the corresponding value of t11ZsAliasName is unique within the Fabric's Zone Server database on this switch.
.1.3.6.1.2.1.160.1.1.6,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberTable,,not-accessible,,current,,This table contains all members of a Zone/Zone Alias and information about those members in the Zone Set database of the Zone Servers on each Fabric in one or more switches. In Enhanced mode, changes to a database made via this table are always made to the 'copy' database, but values read from this table reflect the contents of either the 'copy' database or the current (committed) database as indicated by the corresponding value of t11ZsServerReadFromDatabase.
.1.3.6.1.2.1.160.1.1.6.1,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsZoneMemberParentType:t11ZsZoneMemberParentIndex:t11ZsZoneMemberIndex,current,,Each entry represents the relationship between a member and (one of) its 'parent(s)', i.e., a Zone or Zone Alias to which the member belongs, within a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). A Zone member (other than an alias) is added to a Zone by creating an entry in this table having: - t11ZsZoneMemberParentType = 'zone', and - t11ZsZoneMemberParentIndex = Zone's t11ZsZoneIndex, - t11ZsZoneMemberFormat != '05 - Alias Name', - t11ZsZoneMemberID = Member's identifier. An 'active' row in this table references rows in other tables. The agent must ensure that all such referenced rows exist with a status of 'active', either by refusing to create new active rows in this table, or by automatically deleting any rows in this table that reference a deleted row. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.6.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberParentType,INTEGER,not-accessible,,current,zone(1):alias(2),This object determines whether this member belongs to a Zone or Zone Alias.
.1.3.6.1.2.1.160.1.1.6.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberParentIndex,Unsigned32,not-accessible,,current,,This object contains the index value of the Zone or Zone Alias to which this member belongs. If the value of the corresponding instance of t11ZsZoneMemberParentType is 'zone', then this object will contain the value of the t11ZsZoneIndex object of the Zone to which this member belongs. If the value of the corresponding instance of t11ZsZoneMemberParentType is 'alias', then this object will contain the value of the t11ZsAliasIndex object of the Zone Alias to which this member belongs.
.1.3.6.1.2.1.160.1.1.6.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this Zone Member amongst all Zone Members in the Zone Set database of a particular Fabric on a particular switch.
.1.3.6.1.2.1.160.1.1.6.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberFormat,Unsigned32,read-create,,current,,This object identifies the format of the Zone/Zone Alias member's identifier contained in t11ZsZoneMemberID. This object cannot be modified while the corresponding value of t11ZsZoneMemberRowStatus object is 'active'.
.1.3.6.1.2.1.160.1.1.6.1.5,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberID,OCTET,read-create,,current,,This object contains the Member Identifier of the Zone or Alias. The interpretation of this object depends on the value of the corresponding instance of t11ZsZoneMemberFormat: - if t11ZsZoneMemberFormat is 'N_Port_Name', then this object contains an N_Port_Name. - if t11ZsZoneMemberFormat is 'Domain_ID and physical port', then this object contains a 4-octet value in network byte order. The first octet is zero, the second octet contains the Domain_ID, and the last 2 octets contain the physical port number. - if t11ZsZoneMemberFormat is 'N_Port_ID', then this object contains the 3-octet Nx_Port FC_ID. - if t11ZsZoneMemberFormat is 'Alias Name', then this object contains the value of t11ZsAliasName for some Alias in the same Zone Set database. - if t11ZsZoneMemberFormat is 'Node_Name', then this object contains an 8-octet Node_Name. - if t11ZsZoneMemberFormat is 'F_Port_Name', then this object contains an 8-octet F_Port_Name. - if t11ZsZoneMemberFormat is one of the 'Vendor Specific' values, then this object contains a value of 1 to 255 octets in a format defined by the relevant vendor. This object cannot be modified while the corresponding value of t11ZsZoneMemberRowStatus object is 'active'.
.1.3.6.1.2.1.160.1.1.6.1.6,T11-FC-ZONE-SERVER-MIB::t11ZsZoneMemberRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The corresponding instances of t11ZsZoneMemberID and t11ZsZoneMemberFormat objects must be set before or concurrently with setting this object to 'active'.
.1.3.6.1.2.1.160.1.1.7,T11-FC-ZONE-SERVER-MIB::t11ZsAttribBlockTable,,not-accessible,,current,,This table gives information on all the Zone Attributes in the Zone Set database of the Zone Servers on each Fabric in one or more switches. In Enhanced mode, changes to a database made via this table are always made to the 'copy' database, but values read from this table reflect the contents of either the 'copy' database or the current (committed) database as indicated by the corresponding value of t11ZsServerReadFromDatabase.
.1.3.6.1.2.1.160.1.1.7.1,T11-FC-ZONE-SERVER-MIB::t11ZsAttribBlockEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsAttribBlockIndex,current,,Each entry contains information about a Zone Attribute Block (of Zone Attributes) in the Zone Set database of a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). An 'active' row in this table references a row in the t11ZsAttribBlockTable. The agent must ensure that the referenced rows exists with a status of 'active', either by refusing to create new active rows in this table, or by automatically deleting any rows in this table that reference a deleted row. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.7.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsAttribBlockIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this Zone Attribute within the Zone Set database of a particular Fabric on a particular switch.
.1.3.6.1.2.1.160.1.1.7.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsAttribBlockName,OCTET,read-create,,current,,The name of this Zone Attribute Block, which should be unique within the Fabric.
.1.3.6.1.2.1.160.1.1.7.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsAttribBlockRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row.
.1.3.6.1.2.1.160.1.1.8,T11-FC-ZONE-SERVER-MIB::t11ZsAttribTable,,not-accessible,,current,,This table gives information on the Zone Attributes within the Zone Attribute Blocks in the Zone Set database of the Zone Servers on each Fabric in one or more switches. In Enhanced mode, changes to a database made via this table are always made to the 'copy' database, but values read from this table reflect the contents of either the 'copy' database or the current (committed) database as indicated by the corresponding value of t11ZsServerReadFromDatabase.
.1.3.6.1.2.1.160.1.1.8.1,T11-FC-ZONE-SERVER-MIB::t11ZsAttribEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsAttribBlockIndex:t11ZsAttribIndex,current,,Each entry contains information about a Zone Attribute in a Zone Attribute Block (identified by t11ZsAttribBlockIndex) in the Zone Set database of a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). An entry in this table cannot be created prior to its associated entry in the t11ZsAttribBlockTable. The StorageType of a row in this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.8.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsAttribIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this Zone Attribute within its Zone Attribute Block in the Zone Set database of a particular Fabric on a particular switch.
.1.3.6.1.2.1.160.1.1.8.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsAttribType,Unsigned32,read-create,,current,,The type of attribute: 0001 - Protocol 0002 - Broadcast Zone 0003 - Hard Zone 00E0 (hex) - Vendor Specific.
.1.3.6.1.2.1.160.1.1.8.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsAttribValue,OCTET,read-create,,current,,The value of the attribute, formatted as specified in FC-GS-5 for the type given by the corresponding instance of t11ZsAttribType. Note that FC-GS-5 requires that the length of this value is a multiple of 4 bytes.
.1.3.6.1.2.1.160.1.1.8.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsAttribRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row.
.1.3.6.1.2.1.160.1.1.9,T11-FC-ZONE-SERVER-MIB::t11ZsActivateTable,,not-accessible,,current,,This table provides a mechanism to allow a Zone Set to be activated on a Fabric.
.1.3.6.1.2.1.160.1.1.9.1,T11-FC-ZONE-SERVER-MIB::t11ZsActivateEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex,current,,Each entry reflects the state of the activation of a Zone Set by a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex) on a particular Fabric (identified by the value of t11ZsServerFabricIndex).
.1.3.6.1.2.1.160.1.1.9.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsActivateRequest,Unsigned32,read-write,,current,,Setting this object to a value is a request for a Zone Set to be activated on the Fabric that is represented by this row. The Zone Set to be activated is the one for which t11ZsSetIndex has the same value. If a Zone Set is already active on a Fabric when a request is made to activate a different one on that Fabric, then the existing Zone Set is automatically deactivated and the specified Zone Set is activated in its place. The value of this object when read is always 0.
.1.3.6.1.2.1.160.1.1.9.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsActivateDeactivate,INTEGER,read-write,,current,deactivate(1):noop(2),Setting this object to 'deactivate' is a request to deactivate the currently active Zone Set on a Fabric. Note that the deactivation of the active Zone Set allows all ports to communicate or no ports to communicate, depending on the current Default Zone behavior. No action is taken if this object is set to 'noop'. When read, the value of this object is always 'noop'.
.1.3.6.1.2.1.160.1.1.9.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsActivateResult,INTEGER,read-only,,current,activateSuccess(1):activateFailure(2):deactivateSuccess(3):deactivateFailure(4):inProgress(5):none(6),This object indicates the outcome of the most recent activation/deactivation using this entry. When the value of this object is 'inProgress', the values of the corresponding instances of t11ZsActivateRequest and t11ZsActivateDeactivate cannot be modified. The value 'none' indicates activation/deactivation has not been attempted since the last restart of the management system.
.1.3.6.1.2.1.160.1.1.9.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsActivateFailCause,OCTET,read-only,,current,,A textual message indicating the reason for the most recent failure of a Zone Set activation or deactivation, or the zero-length string if no information is available (e.g., because the corresponding instance of t11ZsActivateResult has the value 'none'). When the corresponding instance of t11ZsActivateResult is either 'activateFailure' or 'deactivateFailure', the value of this object indicates the reason for that failure.
.1.3.6.1.2.1.160.1.1.9.1.5,T11-FC-ZONE-SERVER-MIB::t11ZsActivateFailDomainId,Integer32,read-only,,current,,If the failure cause (as indicated by t11ZsSetFailCause) was specific to a particular device, this object contains the Domain_ID of that device. Otherwise, this object contains zero.
.1.3.6.1.2.1.160.1.1.10,T11-FC-ZONE-SERVER-MIB::t11ZsActiveTable,,not-accessible,,current,,A table containing information on the currently enforced/active Zone Set on each Fabric. An active Zone Set cannot be modified. This table will be empty when no Zone Set is activated.
.1.3.6.1.2.1.160.1.1.10.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex,current,,Each entry represents an active Zone Set of a particular Fabric (identified by the value of t11ZsServerFabricIndex), according to a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.160.1.1.10.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneSetName,OCTET,read-only,,current,,The name of this Zone Set on this Fabric.
.1.3.6.1.2.1.160.1.1.10.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsActiveActivateTime,TimeTicks,read-only,,current,,The value of sysUpTime at which this entry was most recently activated. If this row was activated prior to the last re-initialization of the local network management system, then this object will contain a zero value.
.1.3.6.1.2.1.160.1.1.11,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneTable,,not-accessible,,current,,This table contains all the Zones that are present in the active Zone Sets on all Fabrics.
.1.3.6.1.2.1.160.1.1.11.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsActiveZoneIndex,current,,Each entry represents a Zone in the active Zone Set of a particular Fabric (identified by the value of t11ZsServerFabricIndex), according to a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.160.1.1.11.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this Zone within the active Zone Set on a particular Fabric.
.1.3.6.1.2.1.160.1.1.11.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneName,OCTET,read-only,,current,,The name of this Zone.
.1.3.6.1.2.1.160.1.1.11.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneBroadcastZoning,INTEGER,read-only,,current,true(1):false(2),This object indicates whether broadcast Zoning is enabled on this Zone. If broadcast Zoning is enabled, then broadcast frames generated by a member in this Zone will be restricted to members in this Zone. This object is only instantiated in Enhanced mode.
.1.3.6.1.2.1.160.1.1.11.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneHardZoning,INTEGER,read-only,,current,true(1):false(2),This object indicates whether hard Zoning is enabled on this Zone. This object is only instantiated in Enhanced mode.
.1.3.6.1.2.1.160.1.1.12,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneMemberTable,,not-accessible,,current,,This table contains all members of all Zones within the active Zone Set on any Fabric.
.1.3.6.1.2.1.160.1.1.12.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneMemberEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsActiveZoneIndex:t11ZsActiveZoneMemberIndex,current,,Each entry represents a member of a Zone in the active Zone Set of a particular Fabric (identified by the value t11ZsServerFabricIndex), according to a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.160.1.1.12.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneMemberIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this member amongst the members of a particular Zone in the active Zone Set on a particular Fabric.
.1.3.6.1.2.1.160.1.1.12.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneMemberFormat,Unsigned32,read-only,,current,,This object identifies the identifier format of the corresponding instance of t11ZsActiveZoneMemberID.
.1.3.6.1.2.1.160.1.1.12.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsActiveZoneMemberID,OCTET,read-only,,current,,This value of this object identifies the member using the format specified in the corresponding instance of t11ZsActiveZoneMemberFormat.
.1.3.6.1.2.1.160.1.1.13,T11-FC-ZONE-SERVER-MIB::t11ZsActiveAttribTable,,not-accessible,,current,,This table contains information about some of the Attributes of the Zones within the active Zone Set on each Fabric. This table contains all the types of attributes that might apply zero, one, or more times to a Zone. Attributes that apply once and only to a Zone are specified in the t11ZsActiveZoneTable. This table will always be empty in Basic mode. It will also be empty if there are no Zones in any active Zone Set having any of the applicable types of attributes.
.1.3.6.1.2.1.160.1.1.13.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveAttribEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex:t11ZsActiveZoneIndex:t11ZsActiveAttribIndex,current,,Each entry contains an Attribute of a particular Zone in the active Zone Set of a particular Fabric (identified by the value of t11ZsServerFabricIndex), according to a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.160.1.1.13.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsActiveAttribIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies this attribute amongst the other attributes for a particular Zone in the active Zone Set on a particular Fabric.
.1.3.6.1.2.1.160.1.1.13.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsActiveAttribType,Unsigned32,read-only,,current,,The type of attribute: 0001 - Protocol 00E0 (hex) - Vendor Specific Note that type 2 (Hard) and type 3 (Broadcast) do not need to be represented here, because they are represented by t11ZsActiveZoneBroadcastZoning and t11ZsActiveZoneHardZoning.
.1.3.6.1.2.1.160.1.1.13.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsActiveAttribValue,OCTET,read-only,,current,,The value of the attribute, formatted according to its type as indicated by the corresponding instance of t11ZsActiveAttribType. As specified in FC-GS-5, the length of an attribute value is at least 4 bytes, and if necessary, the value is appended with zero bytes so that the length is a multiple of 4. For a Vendor-Specific attribute value, the first 8 bytes contain the T10 Vendor ID as described in FC-GS-5.
.1.3.6.1.2.1.160.1.1.14,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyControlTable,,not-accessible,,current,,A table of control information for notifications generated due to Zone Server events.
.1.3.6.1.2.1.160.1.1.14.1,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyControlEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex,current,,Each entry contains notification control information specific to a Zone Server for a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex). The persistence across reboots of writable values in a row of this table is specified by the instance of t11ZsServerDatabaseStorageType that is INDEXed by the same values of fcmInstanceIndex, fcmSwitchIndex, and t11ZsServerFabricIndex.
.1.3.6.1.2.1.160.1.1.14.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyRequestRejectEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11ZsRequestRejectNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.160.1.1.14.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyMergeFailureEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11ZsMergeFailureNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.160.1.1.14.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyMergeSuccessEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11ZsMergeSuccessNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.160.1.1.14.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyDefZoneChangeEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11ZsDefZoneChangeNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.160.1.1.14.1.5,T11-FC-ZONE-SERVER-MIB::t11ZsNotifyActivateEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11ZsActivateNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.160.1.1.14.1.6,T11-FC-ZONE-SERVER-MIB::t11ZsRejectCtCommandString,OCTET,read-only,,current,,The binary content of the Zone Server request, formatted as an octet string (in network byte order) containing the Common Transport Information Unit (CT_IU), as described in Table 2 of FC-GS-5 (including the preamble), which was most recently rejected by the Fabric Configuration Server for this Fabric. This object contains the zero-length string if and when the CT-IU's content is unavailable. When the length of this object is 255 octets, it contains the first 255 octets of the CT-IU (in network byte order).
.1.3.6.1.2.1.160.1.1.14.1.7,T11-FC-ZONE-SERVER-MIB::t11ZsRejectRequestSource,OCTET,read-only,,current,,The WWN that was the source of the CT_IU contained in the corresponding instance of t11ZsRejectCtCommandString.
.1.3.6.1.2.1.160.1.1.14.1.8,T11-FC-ZONE-SERVER-MIB::t11ZsRejectReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),The reason code corresponding to the most recent rejection of a request by the Zone Server for this Fabric.
.1.3.6.1.2.1.160.1.1.14.1.9,T11-FC-ZONE-SERVER-MIB::t11ZsRejectReasonCodeExp,INTEGER,read-only,,current,other(1):noAdditionalExplanation(2):zonesNotSupported(3):zoneSetNameUnknown(4):noZoneSetActive(5):zoneNameUnknown(6):zoneStateUnknown(7):incorrectPayloadLen(8):tooLargeZoneSet(9):deactivateZoneSetFailed(10):reqNotSupported(11):capabilityNotSupported(12):zoneMemberIDTypeNotSupp(13):invalidZoneSetDefinition(14):enhancedZoningCmdsNotSupported(15):zoneSetExists(16):zoneExists(17):aliasExists(18):zoneSetUnknown(19):zoneUnknown(20):aliasUnknown(21):zoneAliasTypeUnknown(22):unableEnhancedMode(23):basicZoningCmdsNotSupported(24):zoneAttribObjectExists(25):zoneAttribObjectUnknown(26):requestInProcess(27):cmitInProcess(28):hardEnforcementFailed(29):unresolvedReferences(30):consistencyChecksFailed(31),When the value of t11ZsRejectReasonCode is 'Unable to perform command request', this object contains the corresponding reason code explanation.
.1.3.6.1.2.1.160.1.1.14.1.10,T11-FC-ZONE-SERVER-MIB::t11ZsRejectReasonVendorCode,OCTET,read-only,,current,,When the value of t11ZsRejectReasonCode is 'Vendor Specific Error', this object contains the corresponding vendor-specific reason code.
.1.3.6.1.2.1.160.1.1.15,T11-FC-ZONE-SERVER-MIB::t11ZsFabricIndex,Unsigned32,accessible-for-notify,,current,,This object contains either a value of T11FabricIndex to identify the Fabric on which some occurrence has caused a notification to be generated, or it has the value 4096 to indicate all applicable Fabrics.
.1.3.6.1.2.1.160.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsStatistics,,,,,,
.1.3.6.1.2.1.160.1.2.1,T11-FC-ZONE-SERVER-MIB::t11ZsStatsTable,,not-accessible,,current,,A table of statistics maintained by Zone Servers.
.1.3.6.1.2.1.160.1.2.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsStatsEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11ZsServerFabricIndex,current,,A set of statistics for a Zone Server on a particular Fabric (identified by the value of t11ZsServerFabricIndex) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.160.1.2.1.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsOutMergeRequests,Counter32,read-only,,current,,The number of Merge Request Frames sent by this Zone Server to other Zone Servers in the same Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.2,T11-FC-ZONE-SERVER-MIB::t11ZsInMergeAccepts,Counter32,read-only,,current,,The number of Merge Accept Frames received by this Zone Server from other Zone Servers in the same Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.3,T11-FC-ZONE-SERVER-MIB::t11ZsInMergeRequests,Counter32,read-only,,current,,The number of Merge Request Frames received by this Zone Server from other Zone Servers in the same Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.4,T11-FC-ZONE-SERVER-MIB::t11ZsOutMergeAccepts,Counter32,read-only,,current,,The number of Merge Accept Frames sent by this Zone Server to other Zone Servers in the same Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.5,T11-FC-ZONE-SERVER-MIB::t11ZsOutChangeRequests,Counter32,read-only,,current,,The number of change requests sent (via the Fabric Management Session Protocol) by this Zone Server to other Zone Servers in the same Fabric. This includes Acquire Change Authorization requests, Stage Fabric Config Update requests, Update Fabric Config requests and Release Change Authorization requests. It also includes the corresponding types of requests defined by the Enhanced Commit Service. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.6,T11-FC-ZONE-SERVER-MIB::t11ZsInChangeAccepts,Counter32,read-only,,current,,The number of SW_ACC messages received from other Zone Servers in the same Fabric (according to the Fabric Management Session Protocol) in response to change requests by this Zone Server. This includes SW_ACC messages received in response to Acquire Change Authorization requests, to Stage Fabric Config Update requests, to Update Fabric Config requests, and to Release Change Authorization requests. It also includes responses to the corresponding types of requests defined for the Enhanced Commit Service. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.7,T11-FC-ZONE-SERVER-MIB::t11ZsInChangeRequests,Counter32,read-only,,current,,The number of change requests received (via the Fabric Management Session Protocol) by this Zone Server from other Zone Servers in the same Fabric. This includes Acquire Change Authorization requests, Stage Fabric Config Update requests, Update Fabric Config requests and Release Change Authorization requests. It also includes the corresponding types of requests defined by the Enhanced Commit Service. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.8,T11-FC-ZONE-SERVER-MIB::t11ZsOutChangeAccepts,Counter32,read-only,,current,,The number of SW_ACC messages sent by this Zone Server (according to the Fabric Management Session Protocol) in response to change requests from other Zone Servers in the same Fabric. This includes SW_ACC messages sent in response to Acquire Change Authorization requests, to Stage Fabric Config Update requests, to Update Fabric Config requests and to Release Change Authorization requests. It also includes responses to the corresponding types of requests defined for the Enhanced Commit Service. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.9,T11-FC-ZONE-SERVER-MIB::t11ZsInZsRequests,Counter32,read-only,,current,,The number of Zone Server requests received by this Zone Server on this Fabric, both those received in Basic mode and in Enhanced mode. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.1.2.1.1.10,T11-FC-ZONE-SERVER-MIB::t11ZsOutZsRejects,Counter32,read-only,,current,,The number of Zone Server requests rejected by this Zone Server on this Fabric, both those rejected in Basic mode and in Enhanced mode. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.160.2,T11-FC-ZONE-SERVER-MIB::t11ZsMIBConformance,,,,,,
.1.3.6.1.2.1.160.2.1,T11-FC-ZONE-SERVER-MIB::t11ZsMIBCompliances,,,,,,
.1.3.6.1.2.1.160.2.1.1,T11-FC-ZONE-SERVER-MIB::t11ZsMIBCompliance,,,,,,The compliance statement for entities that implement the Zone Server.
.1.3.6.1.2.1.160.2.2,T11-FC-ZONE-SERVER-MIB::t11ZsMIBGroups,,,,,,
.1.3.6.1.2.1.160.2.2.1,T11-FC-ZONE-SERVER-MIB::t11ZsBasicGroup,,,,,,A collection of objects for displaying and updating the Zone configuration of a Zone Server capable of operating in Basic mode.
.1.3.6.1.2.1.160.2.2.2,T11-FC-ZONE-SERVER-MIB::t11ZsEnhancedModeGroup,,,,,,A collection of additional objects for displaying and updating the Zone configuration of a Zone Server capable of operating in Enhanced mode.
.1.3.6.1.2.1.160.2.2.3,T11-FC-ZONE-SERVER-MIB::t11ZsStatisticsGroup,,,,,,A collection of objects for collecting Zone Server statistics information.
.1.3.6.1.2.1.160.2.2.4,T11-FC-ZONE-SERVER-MIB::t11ZsNotificationControlGroup,,,,,,A collection of notification control and notification information objects for monitoring Zone Server request rejection and Zone merge failures.
.1.3.6.1.2.1.160.2.2.5,T11-FC-ZONE-SERVER-MIB::t11ZsActivateGroup,,,,,,A collection of objects that allow a Zone Set to be activated via SNMP SetRequests and provide the status and result of such an activation.
.1.3.6.1.2.1.160.2.2.6,T11-FC-ZONE-SERVER-MIB::t11ZsNotificationGroup,,,,,,A collection of notification(s) for monitoring Zone Server request rejection, Zone merge failures and successes, and Default Zoning behavioral changes.
.1.3.6.1.2.1.161,T11-FC-RSCN-MIB::t11FcRscnMIB,,,,,,The MIB module for the management of registrations by Nx_Ports to receive RSCNs (Registered State Change Notifications) on a Fibre Channel Fabric, as defined in FC-LS, and for the monitoring of RSCNs sent/received or rejected in a Fibre Channel Fabric. Copyright (C) The Internet Society (2007). This version of this MIB module is part of RFC 4983; see the RFC itself for full legal notices.
.1.3.6.1.2.1.161.0,T11-FC-RSCN-MIB::t11FcRscnNotifications,,,,,,
.1.3.6.1.2.1.161.0.1,T11-FC-RSCN-MIB::t11FcRscnElsRejectReqNotify,,,,,,This notification is generated when a switch rejects an SCR or RSCN. The value of t11FcRscnRejectedRequestString indicates the binary content of the rejected request if available, or the zero-length string otherwise. The source of the rejected request is given by t11FcRscnRejectedRequestSource, and the reason for rejection is given by the values of t11FcRscnRejectReasonCode, t11FcRscnRejectReasonCodeExp and t11FcRscnRejectReasonVendorCode.
.1.3.6.1.2.1.161.0.2,T11-FC-RSCN-MIB::t11FcRscnIlsRejectReqNotify,,,,,,This notification is generated when a switch rejects an SW_RSCN. The value of t11FcRscnRejectedRequestString indicates the binary content of the rejected request if available, or the zero-length string otherwise. The source of the rejected request is given by t11FcRscnRejectedRequestSource, and the reason for rejection is given by the values of t11FcRscnRejectReasonCode, t11FcRscnRejectReasonCodeExp and t11FcRscnRejectReasonVendorCode.
.1.3.6.1.2.1.161.1,T11-FC-RSCN-MIB::t11FcRscnObjects,,,,,,
.1.3.6.1.2.1.161.1.1,T11-FC-RSCN-MIB::t11FcRscnRegistrations,,,,,,
.1.3.6.1.2.1.161.1.1.1,T11-FC-RSCN-MIB::t11FcRscnRegTable,,not-accessible,,current,,A table of Nx_Ports that have registered to receive RSCNs on all Fabrics configured on one or more Fibre Channel switches.
.1.3.6.1.2.1.161.1.1.1.1,T11-FC-RSCN-MIB::t11FcRscnRegEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcRscnFabricIndex:t11FcRscnRegFcId,current,,An entry containing information about one Nx_Port that has registered with a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex) for a particular Fabric (identified by a t11FcRscnFabricIndex value).
.1.3.6.1.2.1.161.1.1.1.1.1,T11-FC-RSCN-MIB::t11FcRscnFabricIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Fabric. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures. In such a case, this index value is used to uniquely identify a particular Fabric within a physical infrastructure. In a Fabric that has (or can have) only a single Fabric operating within the physical infrastructure, the value of this Fabric Index will always be 1.
.1.3.6.1.2.1.161.1.1.1.1.2,T11-FC-RSCN-MIB::t11FcRscnRegFcId,OCTET,not-accessible,,current,,The Fibre Channel Address Identifier of the registering Nx_Port.
.1.3.6.1.2.1.161.1.1.1.1.3,T11-FC-RSCN-MIB::t11FcRscnRegType,BITS,read-only,,current,fromFabricController(0):fromNxPort(1),This object indicates the type of registration desired by the registering Nx_Port, one bit per type: 'fromFabricController' -- RSCNs generated for events detected by the Fabric Controller. 'fromNxPorts' -- RSCNs generated for events detected by the affected Nx_Port.
.1.3.6.1.2.1.161.1.2,T11-FC-RSCN-MIB::t11FcRscnStats,,,,,,
.1.3.6.1.2.1.161.1.2.1,T11-FC-RSCN-MIB::t11FcRscnStatsTable,,not-accessible,,current,,The RSCN-related statistics on all Fabrics configured on one or more Fibre Channel switches. Two levels of statistics are included: 1) counters at the message-type level, for: - the number of SCRs received/rejected, - the number of RSCNs sent/received/rejected, - the number of SW_RSCNs sent/received/rejected. 2) counters of sent/received RSCNs per 'Event Qualifier' value. Note that if and when several RSCN events are coalesced into a single RSCN message, then that message may be counted in more than one of these counters.
.1.3.6.1.2.1.161.1.2.1.1,T11-FC-RSCN-MIB::t11FcRscnStatsEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcRscnFabricIndex,current,,An entry containing statistics for a particular Fabric (identified by a t11FcRscnFabricIndex value) on a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.161.1.2.1.1.1,T11-FC-RSCN-MIB::t11FcRscnInScrs,Counter32,read-only,,current,,The number of SCRs received from Nx_Ports by this switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.2,T11-FC-RSCN-MIB::t11FcRscnInRscns,Counter32,read-only,,current,,The number of RSCNs received from Nx_Ports by this switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.3,T11-FC-RSCN-MIB::t11FcRscnOutRscns,Counter32,read-only,,current,,The number of RSCNs transmitted to Nx_Ports by this switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.4,T11-FC-RSCN-MIB::t11FcRscnInSwRscns,Counter32,read-only,,current,,The number of SW_RSCNs received by this switch from other switches on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.5,T11-FC-RSCN-MIB::t11FcRscnOutSwRscns,Counter32,read-only,,current,,The number of SW_RSCNs transmitted by this switch from other switches on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.6,T11-FC-RSCN-MIB::t11FcRscnScrRejects,Counter32,read-only,,current,,The number of SCRs rejected by this switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.7,T11-FC-RSCN-MIB::t11FcRscnRscnRejects,Counter32,read-only,,current,,The number of RSCNs rejected by this switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.8,T11-FC-RSCN-MIB::t11FcRscnSwRscnRejects,Counter32,read-only,,current,,The number of SW_RSCN rejected by this switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.9,T11-FC-RSCN-MIB::t11FcRscnInUnspecifiedRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) received by this switch on this Fabric which contained an RSCN Event Qualifier value of '0000'b meaning 'Event is not specified'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.10,T11-FC-RSCN-MIB::t11FcRscnOutUnspecifiedRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) sent by this switch on this Fabric which contained an RSCN Event Qualifier value of '0000'b meaning 'Event is not specified'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.11,T11-FC-RSCN-MIB::t11FcRscnInChangedAttribRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) received by this switch on this Fabric which contained an RSCN Event Qualifier value of '0002'b meaning 'Changed Port Attribute'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.12,T11-FC-RSCN-MIB::t11FcRscnOutChangedAttribRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) sent by this switch on this Fabric which contained an RSCN Event Qualifier value of '0002'b meaning 'Changed Port Attribute'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.13,T11-FC-RSCN-MIB::t11FcRscnInChangedServiceRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) received by this switch on this Fabric which contained an RSCN Event Qualifier value of '0003'b meaning 'Changed Service Object'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.14,T11-FC-RSCN-MIB::t11FcRscnOutChangedServiceRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) sent by this switch on this Fabric which contained an RSCN Event Qualifier value of '0003'b meaning 'Changed Service Object'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.15,T11-FC-RSCN-MIB::t11FcRscnInChangedSwitchRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) received by this switch on this Fabric which contained an RSCN Event Qualifier value of '0004'b meaning 'Changed Switch Configuration'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.16,T11-FC-RSCN-MIB::t11FcRscnOutChangedSwitchRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) sent by this switch on this Fabric which contained an RSCN Event Qualifier value of '0004'b meaning 'Changed Switch Configuration'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.17,T11-FC-RSCN-MIB::t11FcRscnInRemovedRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) received by this switch on this Fabric which contained an RSCN Event Qualifier value of '0005'b meaning 'Removed Object'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.2.1.1.18,T11-FC-RSCN-MIB::t11FcRscnOutRemovedRscns,Counter32,read-only,,current,,The number of Registered State Change Notifications (RSCNs) sent by this switch on this Fabric which contained an RSCN Event Qualifier value of '0005'b meaning 'Removed Object'. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.161.1.3,T11-FC-RSCN-MIB::t11FcRscnInformation,,,,,,
.1.3.6.1.2.1.161.1.3.1,T11-FC-RSCN-MIB::t11FcRscnNotifyControlTable,,not-accessible,,current,,A table of control information for notifications generated due to the rejection of an SCR or RSCN.
.1.3.6.1.2.1.161.1.3.1.1,T11-FC-RSCN-MIB::t11FcRscnNotifyControlEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcRscnFabricIndex,current,,Each entry contains notification control information concerning the rejection of RSCN/SCRs for a particular Fabric (identified by the value of t11FcRscnFabricIndex) by a particular switch (identified by values of fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.161.1.3.1.1.1,T11-FC-RSCN-MIB::t11FcRscnIlsRejectNotifyEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies if a t11FcRscnIlsRejectReqNotify notification should be generated when this switch rejects an SW_RSCN on this Fabric. Values written to this object should be retained over agent reboots.
.1.3.6.1.2.1.161.1.3.1.1.2,T11-FC-RSCN-MIB::t11FcRscnElsRejectNotifyEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies if a t11FcRscnElsRejectReqNotify notification should be generated when this switch rejects an RSCN or SCR on this Fabric. Values written to this object should be retained over agent reboots.
.1.3.6.1.2.1.161.1.3.1.1.3,T11-FC-RSCN-MIB::t11FcRscnRejectedRequestString,OCTET,read-only,,current,,The binary content of the RSCN, SCR, or SW_RSCN that was most recently rejected by this switch on this Fabric. The value is formatted as an octet string (in network byte order) as described in the relevant Fibre Channel standard, containing the payload (which is typically a list of affected ports and error codes) of the rejected RSCN or SCR as described in FC-LS, or the rejected SW_RSCN as described in FC-SW-4. This object contains the zero-length string if and when the RSCN/SCR/SW_RSCN payload is unavailable. When the length of this object is 255 octets, it contains the first 255 octets of the payload (in network byte order).
.1.3.6.1.2.1.161.1.3.1.1.4,T11-FC-RSCN-MIB::t11FcRscnRejectedRequestSource,OCTET,read-only,,current,,The WWN that was the source of the RSCN, SCR, or SW_RSCN that was most recently rejected by this switch on this Fabric.
.1.3.6.1.2.1.161.1.3.1.1.5,T11-FC-RSCN-MIB::t11FcRscnRejectReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),This object contains the Reason Code of the most recent rejection by this switch of an RSCN, SCR or SW_RSCN on this Fabric.
.1.3.6.1.2.1.161.1.3.1.1.6,T11-FC-RSCN-MIB::t11FcRscnRejectReasonCodeExp,OCTET,read-only,,current,,This object contains the Reason Code Explanation of the most recent rejection by this switch of an RSCN, SCR or SW_RSCN on this Fabric.
.1.3.6.1.2.1.161.1.3.1.1.7,T11-FC-RSCN-MIB::t11FcRscnRejectReasonVendorCode,OCTET,read-only,,current,,This object contains the Reason Vendor Specific Code of the most recent rejection by this switch of an RSCN, SCR or SW_RSCN on this Fabric.
.1.3.6.1.2.1.161.2,T11-FC-RSCN-MIB::t11FcRscnConformance,,,,,,
.1.3.6.1.2.1.161.2.1,T11-FC-RSCN-MIB::t11FcRscnCompliances,,,,,,
.1.3.6.1.2.1.161.2.1.1,T11-FC-RSCN-MIB::t11FcRscnCompliance,,,,,,The compliance statement for entities that implement this MIB.
.1.3.6.1.2.1.161.2.2,T11-FC-RSCN-MIB::t11FcRscnGroups,,,,,,
.1.3.6.1.2.1.161.2.2.1,T11-FC-RSCN-MIB::t11FcRscnRegistrationGroup,,,,,,A collection of objects for monitoring RSCN registrations.
.1.3.6.1.2.1.161.2.2.2,T11-FC-RSCN-MIB::t11FcRscnStatsGroup,,,,,,A collection of objects for collecting RSCN-related statistics.
.1.3.6.1.2.1.161.2.2.3,T11-FC-RSCN-MIB::t11FcRscnNotifyControlGroup,,,,,,A collection of notification control and notification information objects.
.1.3.6.1.2.1.161.2.2.4,T11-FC-RSCN-MIB::t11FcRscnNotifyGroup,,,,,,A collection of notifications for monitoring ILS and ELS rejections by the RSCN module.
.1.3.6.1.2.1.162,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcFabricConfigServerMIB,,,,,,The MIB module for the management of a Fabric Configuration Server (FCS) in a Fibre Channel (FC) network. An FCS is defined by the FC-GS-5 standard. This MIB provides the capabilities to trigger a discovery of the configuration of one or more Fabrics, to retrieve the results of such a discovery, as well as to control and monitor the operation of an FCS. The discovered configuration contains information about: - Interconnect Elements (IEs), i.e., switches, hubs, bridges, etc., - Ports on IEs, and - Platforms that consist of one or more FC nodes. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4935; see the RFC itself for full legal notices.
.1.3.6.1.2.1.162.0,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNotifications,,,,,,
.1.3.6.1.2.1.162.0.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRqRejectNotification,,,,,,This notification is generated whenever the Fabric Configuration Server on a switch (indicated by the value of t11FamLocalSwitchWwn) rejects a Fabric Configuration Server request. The Fabric Configuration Server should update the t11FcsRejectReasonCode, t11FcsRejectReasonCodeExp and t11FcsRejectReasonVendorCode objects with the corresponding reason code, explanation and vendor specific code before sending the notification.
.1.3.6.1.2.1.162.0.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryCompleteNotify,,,,,,This notification is generated by the Fabric Configuration Server on the completion of the discovery of Fabrics in the range that has t11FcsFabricDiscoveryRangeLow at its low end.
.1.3.6.1.2.1.162.0.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrChangeNotify,,,,,,This notification is generated by the Fabric Configuration Server whenever the management address of an IE changes, i.e., whenever an entry in the t11FcsMgmtAddrListTable changes.
.1.3.6.1.2.1.162.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMIBObjects,,,,,,
.1.3.6.1.2.1.162.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscovery,,,,,,
.1.3.6.1.2.1.162.1.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricDiscoveryTable,,not-accessible,,current,,This table contains control information for discovery of Fabric configuration by switches. Values written to objects in this table are not retained over agent reboots.
.1.3.6.1.2.1.162.1.1.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricDiscoveryEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex,current,,Control information for discovery by the switch identified by fcmInstanceIndex and fcmSwitchIndex.
.1.3.6.1.2.1.162.1.1.1.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricDiscoveryRangeLow,Unsigned32,read-write,,current,,The discovery by a particular switch operates within all existing Fabrics that have a Fabric Index within a specific inclusive range. This object specifies the minimum Fabric Index value within that range. This value just represents the lower end of the range and does not necessarily represent any existing Fabric.
.1.3.6.1.2.1.162.1.1.1.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricDiscoveryRangeHigh,Unsigned32,read-write,,current,,The discovery by a particular switch operates within all existing Fabrics that have a Fabric Index within a specific inclusive range. This object specifies the maximum Fabric Index value within that range. This value just represents the higher end of the range and does not necessarily represent any existing Fabric.
.1.3.6.1.2.1.162.1.1.1.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricDiscoveryStart,INTEGER,read-write,,current,start(1):noOp(2),This object provides the capability to trigger the start of a discovery by a Fabric Configuration Server. If this object is set to 'start', then the discovery is started on those Fabrics that have their Fabric Index value in the range specified by t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh. It is recommended that whenever an instance of this object is set to 'start', that the desired range be specified at the same time by setting the corresponding instances of t11FcsFabricDiscoveryRangeLow and t11FcsFabricDiscoveryRangeHigh. Setting this object to 'start' will be rejected if a discovery is already/still in progress on any Fabrics in the specified range. No action is taken if this object is set to 'noOp'. The value of this object when read is always 'noOp'.
.1.3.6.1.2.1.162.1.1.1.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricDiscoveryTimeOut,Unsigned32,read-write,,current,,The minimum interval of time for which the discovered Fabric information is cached by a Fabric Configuration Server.
.1.3.6.1.2.1.162.1.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryStateTable,,not-accessible,,current,,This table contains the status of discovery of locally known Fabrics.
.1.3.6.1.2.1.162.1.1.2.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryStateEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsFabricIndex,current,,The discovery status for a particular Fabric on the switch identified by fcmInstanceIndex and fcmSwitchIndex.
.1.3.6.1.2.1.162.1.1.2.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsFabricIndex,Unsigned32,not-accessible,,current,,A unique index value that uniquely identifies a particular Fabric. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures, and this index value is used to uniquely identify a particular (physical or virtual) Fabric within a physical infrastructure. In a Fabric conformant to versions earlier than FC-SW-4, only a single Fabric could operate within a physical infrastructure, and thus, the value of this Fabric Index was defined to always be 1.
.1.3.6.1.2.1.162.1.1.2.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryStatus,INTEGER,read-write,,current,inProgress(1):completed(2):localOnly(3),The status of the discovery for the particular Fabric. Initially when the switch comes up, all instances of this object have the value: 'localOnly', and the database contains only local information, i.e., no information discovered via the Fabric Configuration Server protocol specified in FC-GS-5. If t11FcsFabricDiscoveryStart is set to 'start' for a range of Fabrics that includes this Fabric, then the value of this object transitions to 'inProgress'. When the discovery completes, this object transitions to 'completed', and the data is cached for the minimum interval of time specified by t11FcsFabricDiscoveryTimeOut. After this interval has been exceeded, the data may be lost, in which case, the value of this object changes to 'localOnly'. This object cannot be set via SNMP to any value other than 'localOnly'. If this object is set (via SNMP) to 'localOnly', the cached data for the Fabric is discarded immediately, and if a discovery initiated from this switch was in progress for this Fabric, then that discovery is aborted.
.1.3.6.1.2.1.162.1.1.2.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryCompleteTime,TimeTicks,read-only,,current,,This object contains the value of sysUpTime at which discovery was most recently completed or aborted on this Fabric. This object contains the value of zero before the first discovery on this Fabric.
.1.3.6.1.2.1.162.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveredConfig,,,,,,
.1.3.6.1.2.1.162.1.2.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeTable,,not-accessible,,current,,A table of Interconnect Elements. Interconnect Elements (IEs) are switches, hubs, bridges etc. By default, the Fabric Configuration Server will maintain detailed information pertaining only to local resources. As far as discovered topology is concerned, only the IE name, type, and Domain ID information will be maintained. If a discovery cycle is triggered on a set of Fabrics, this table along with the Port and Platform tables will be populated with the discovered information. The discovered data will be retained in this table for at least t11FcsFabricDiscoveryTimeOut seconds after the completion of its discovery or until the discovered data is invalidated.
.1.3.6.1.2.1.162.1.2.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsFabricIndex:t11FcsIeName,current,,Information about an Interconnect Element that was discovered on a Fabric (identified by t11FcsFabricIndex), by a switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.2.1.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeName,OCTET,not-accessible,,current,,The WWN of an Interconnect Element. This object uniquely identifies an Interconnect Element on a Fabric. If the IE is a switch, then this object is the Switch_Name (WWN) of the switch.
.1.3.6.1.2.1.162.1.2.1.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeType,INTEGER,read-only,,current,unknown(1):other(2):switch(3):hub(4):bridge(5),The type of this Interconnect Element.
.1.3.6.1.2.1.162.1.2.1.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeDomainId,Integer32,read-only,,current,,The Domain ID of this Interconnect Element.
.1.3.6.1.2.1.162.1.2.1.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeMgmtId,OCTET,read-only,,current,,The management identifier of this Interconnect Element. If the Interconnect Element is a switch, this object will be the Domain Controller identifier of the switch. When the value of the identifier is unknown, this object contains the all-zeros value: x'00 00 00'.
.1.3.6.1.2.1.162.1.2.1.1.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeFabricName,OCTET,read-only,,current,,The Fabric_Name (WWN) of this Interconnect Element. When the Fabric_Name is unknown, this object contains the all-zeros value: x'00 00 00 00 00 00 00 00'.
.1.3.6.1.2.1.162.1.2.1.1.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeLogicalName,OCTET,read-only,,current,,The logical name of this Interconnect Element. When the logical name is unknown, this object contains the zero-length string.
.1.3.6.1.2.1.162.1.2.1.1.7,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeMgmtAddrListIndex,Unsigned32,read-only,,current,,The management address list for this Interconnect Element. This object points to an entry in the t11FcsMgmtAddrListTable.
.1.3.6.1.2.1.162.1.2.1.1.8,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsIeInfoList,OCTET,read-only,,current,,The information list for this Interconnect Element. The value of this object is formatted as specified in FC-GS-5, i.e., it has the following substrings in order: vendor name, model name/number, and release code/level, followed by zero or more substrings of vendor-specific information. Each substring is terminated with a byte containing a null value (x'00').
.1.3.6.1.2.1.162.1.2.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrListTable,,not-accessible,,current,,This table contains the set of management address lists that are currently referenced by any instance of the t11FcsIeMgmtAddrListIndex or t11FcsPlatformMgmtAddrListIndex objects.
.1.3.6.1.2.1.162.1.2.2.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrListEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsMgmtAddrListIndex:t11FcsMgmtAddrIndex,current,,Information about one management address in a management address list, which is known to a switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.2.2.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrListIndex,Unsigned32,not-accessible,,current,,The index value of the management address list.
.1.3.6.1.2.1.162.1.2.2.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrIndex,Unsigned32,not-accessible,,current,,An integer value to distinguish different management addresses in the same list.
.1.3.6.1.2.1.162.1.2.2.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddr,OCTET,read-only,,current,,The management address of this entry. The format of this object is a Uniform Resource Locator (URL), e.g., for SNMP, see RFC 4088.
.1.3.6.1.2.1.162.1.2.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortTable,,not-accessible,,current,,This table contains information about the ports of IEs.
.1.3.6.1.2.1.162.1.2.4.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsFabricIndex:t11FcsIeName:t11FcsPortName,current,,Information about a particular port of an Interconnect Element (identified by t11FcsIeName). The port is connected to a Fabric (identified by t11FcsFabricIndex) and known to a switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.2.4.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortName,OCTET,not-accessible,,current,,The Port_Name (WWN) of the port for which this row contains information.
.1.3.6.1.2.1.162.1.2.4.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortType,Unsigned32,read-only,,current,,The Port Type of this port.
.1.3.6.1.2.1.162.1.2.4.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortTxType,INTEGER,read-only,,current,unknown(1):other(2):shortwave850nm(3):longwave1550nm(4):longwave1310nm(5):electrical(6):tenGbaseSr850(7):tenGbaseLr1310(8):tenGbaseEr1550(9):tenGbaseLx1300(10):tenGbaseSw850(11):tenGbaseLw1310(12):tenGbaseEw1550(13),The Port TX Type of this port.
.1.3.6.1.2.1.162.1.2.4.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortModuleType,Unsigned32,read-only,,current,,The port module type of this port.
.1.3.6.1.2.1.162.1.2.4.1.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortPhyPortNum,Unsigned32,read-only,,current,,The physical number for this port. FC-GS-5 says that the contents of this field, which are carried in a field with a size of 4 bytes, are not to be restricted due to vendor-specific methods for numbering physical ports.
.1.3.6.1.2.1.162.1.2.4.1.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortAttachPortNameIndex,Unsigned32,read-only,,current,,The attached port name list for this port. This object points to an entry in the t11FcsAttachPortNameListTable.
.1.3.6.1.2.1.162.1.2.4.1.7,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortState,INTEGER,read-only,,current,unknown(1):other(2):online(3):offline(4):testing(5):fault(6),The state of this port.
.1.3.6.1.2.1.162.1.2.4.1.8,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortSpeedCapab,OCTET,read-only,,current,,The port speed capabilities of this port. The two octets of the value are formatted as described in FC-GS-5.
.1.3.6.1.2.1.162.1.2.4.1.9,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortOperSpeed,OCTET,read-only,,current,,The operating speed of this port. The two octets of the value are formatted as described in FC-GS-5.
.1.3.6.1.2.1.162.1.2.4.1.10,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPortZoningEnfStatus,OCTET,read-only,,current,,The zoning enforcement status of this port. The 12 octets of the value are formatted as described in FC-GS-5.
.1.3.6.1.2.1.162.1.2.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsAttachPortNameListTable,,not-accessible,,current,,This table contains all the lists of attach port names.
.1.3.6.1.2.1.162.1.2.5.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsAttachPortNameListEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsAttachPortNameListIndex:t11FcsAttachPortName,current,,Information about the name of a particular attached port, which is known to a switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.2.5.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsAttachPortNameListIndex,Unsigned32,not-accessible,,current,,The index value of the attach port name list.
.1.3.6.1.2.1.162.1.2.5.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsAttachPortName,OCTET,read-only,,current,,The attached port name. Zero or more of these names may be associated with a port object. The first 8 bytes of this object contain the WWN of the port followed by 2 reserved bytes. Following this is one byte of Port flags and one byte of Port type, as described in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformTable,,not-accessible,,current,,This table contains information on platforms. By default, this table only contains local (e.g., for a local switch) information. If a discovery is triggered, this table will also contain information gathered by the discovery process. The discovered information is retained in this table for at least t11FcsFabricDiscoveryTimeOut seconds after the completion of its discovery or until the discovered cache is invalidated.
.1.3.6.1.2.1.162.1.2.6.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsFabricIndex:t11FcsPlatformIndex,current,,Information about a particular platform, which is known to a switch (identified by fcmInstanceIndex and fcmSwitchIndex). A platform can contain multiple nodes. Information on nodes is contained in the t11FcsNodeNameListTable. The t11FcsPlatformNodeNameListIndex object in this table points to the list of nodes contained in this platform. Similarly, the t11FcsPlatformMgmtAddrListIndex object in this table points to the list of management addresses associated with this platform.
.1.3.6.1.2.1.162.1.2.6.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformIndex,Unsigned32,not-accessible,,current,,An integer value to distinguish one platform from other platforms in the same Fabric.
.1.3.6.1.2.1.162.1.2.6.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformName,OCTET,read-only,,current,,The name of this platform. The last byte of the value indicates the format of the name (even if the name itself is the zero-length string) as specified in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformType,OCTET,read-only,,current,,The type(s) of this platform, encoded in 4 bytes as specified in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformNodeNameListIndex,Unsigned32,read-only,,current,,The list of nodes for this platform. This object points to an entry in the t11FcsNodeNameListTable.
.1.3.6.1.2.1.162.1.2.6.1.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformMgmtAddrListIndex,Unsigned32,read-only,,current,,The list of management addresses for this platform. This object points to an entry in the t11FcsMgmtAddrListTable.
.1.3.6.1.2.1.162.1.2.6.1.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformVendorId,OCTET,read-only,,current,,The identifier of the vendor of this platform, in the format specified in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6.1.7,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformProductId,OCTET,read-only,,current,,The vendor's product and/or model identifier for this platform, in the format specified in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6.1.8,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformProductRevLevel,OCTET,read-only,,current,,The product revision level for this platform, in the format specified in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6.1.9,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformDescription,OCTET,read-only,,current,,The description of this platform, in the format specified in FC-GS-5. This value should include the full name and version identification of the platform's hardware type and software operating system.
.1.3.6.1.2.1.162.1.2.6.1.10,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformLabel,OCTET,read-only,,current,,An administratively assigned symbolic name for the platform, in the format specified in FC-GS-5.
.1.3.6.1.2.1.162.1.2.6.1.11,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformLocation,OCTET,read-only,,current,,The physical location of the platform, in the format specified in FC-GS-5 (e.g., 'telephone closet, 3rd floor').
.1.3.6.1.2.1.162.1.2.6.1.12,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformSystemID,OCTET,read-only,,current,,An identifier for a hosting system that this platform is associated with. This identifier is used to associate platforms of logical types (e.g., logical partitions) with a physical system.
.1.3.6.1.2.1.162.1.2.6.1.13,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformSysMgmtAddr,Unsigned32,read-only,,current,,A list of management addresses for the platform.
.1.3.6.1.2.1.162.1.2.6.1.14,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformClusterId,OCTET,read-only,,current,,An identifier for a cluster that this platform is associated with, where a cluster is a set of independent platforms that are managed together to provide increased performance capabilities, failover, etc.
.1.3.6.1.2.1.162.1.2.6.1.15,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformClusterMgmtAddr,Unsigned32,read-only,,current,,A list of management addresses for the cluster identified in the corresponding instance of t11FcsPlatformClusterId.
.1.3.6.1.2.1.162.1.2.6.1.16,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsPlatformFC4Types,OCTET,read-only,,current,,The FC-4 types supported by this platform, formatted as a bit mask as specified in FC-GS-5. If this object contains the zero-length string, the types are unknown.
.1.3.6.1.2.1.162.1.2.7,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNodeNameListTable,,not-accessible,,current,,This table contains all the lists of nodes.
.1.3.6.1.2.1.162.1.2.7.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNodeNameListEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsNodeNameListIndex:t11FcsNodeName,current,,Information about a node, which is known to a switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.2.7.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNodeNameListIndex,Unsigned32,not-accessible,,current,,The index value of the node name list.
.1.3.6.1.2.1.162.1.2.7.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNodeName,OCTET,read-only,,current,,The name of this node.
.1.3.6.1.2.1.162.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsStats,,,,,,
.1.3.6.1.2.1.162.1.3.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsStatsTable,,not-accessible,,current,,This table contains all the statistics related to the Fabric Configuration Server.
.1.3.6.1.2.1.162.1.3.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsStatsEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsFabricIndex,current,,A set of statistics for a particular Fabric (identified by t11FcsFabricIndex) on a switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.3.1.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsInGetReqs,Counter32,read-only,,current,,The number of Get Requests received by the Fabric Configuration Server on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.3.1.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsOutGetReqs,Counter32,read-only,,current,,The number of Get Requests sent by the Fabric Configuration Server on this Fabric to other servers in the Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.3.1.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsInRegReqs,Counter32,read-only,,current,,The number of Registration Requests received by the Fabric Configuration Server on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.3.1.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsOutRegReqs,Counter32,read-only,,current,,The number of Registration Requests sent by the Fabric Configuration Server on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.3.1.1.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsInDeregReqs,Counter32,read-only,,current,,The number of Deregistration Requests received by the Fabric Configuration Server on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.3.1.1.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsOutDeregReqs,Counter32,read-only,,current,,The number of Deregistration Requests sent by the Fabric Configuration Server on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.3.1.1.7,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRejects,Counter32,read-only,,current,,The total number of requests rejected by the Fabric Configuration Server on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.
.1.3.6.1.2.1.162.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNotificationInfo,,,,,,
.1.3.6.1.2.1.162.1.4.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNotifyControlTable,,not-accessible,,current,,A table of control information for notifications generated due to Fabric Configuration Server events. Values written to objects in this table should be persistent/retained over agent reboots.
.1.3.6.1.2.1.162.1.4.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNotifyControlEntry,,not-accessible,fcmInstanceIndex:fcmSwitchIndex:t11FcsFabricIndex,current,,Each entry contains notification control information for a Fabric Configuration Server on a particular Fabric (identified by t11FcsFabricIndex) on a particular switch (identified by fcmInstanceIndex and fcmSwitchIndex).
.1.3.6.1.2.1.162.1.4.1.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsReqRejectNotifyEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies if the Fabric Configuration Server should generate 't11FcsRqRejectNotification' notifications. If the value of this object is 'true', then the notification is issued. If the value of this object is 'false', then the notification is not issued.
.1.3.6.1.2.1.162.1.4.1.1.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryCompNotifyEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies if the Fabric Configuration Server should generate 't11FcsDiscoveryCompleteNotify' notifications. If the value of this object is 'true', then the notification is issued. If the value of this object is 'false', then the notification is not issued.
.1.3.6.1.2.1.162.1.4.1.1.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrChangeNotifyEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies if the Fabric Configuration Server should generate 't11FcsMgmtAddrChangeNotify' notifications. If the value of this object is 'true', then the notification is issued. If the value of this object is 'false', then the notification is not issued.
.1.3.6.1.2.1.162.1.4.1.1.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRejectCtCommandString,OCTET,read-only,,current,,The binary content of the Fabric Configuration Server request, formatted as an octet string (in network byte order) containing the Common Transport Information Unit (CT_IU), as described in Table 2 of FC-GS-5 (including the preamble), which was most recently rejected by the Fabric Configuration Server for this Fabric. This object contains the zero-length string if and when the CT-IU's content is unavailable. When the length of this object is 255 octets, it contains the first 255 octets of the CT-IU (in network byte order).
.1.3.6.1.2.1.162.1.4.1.1.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRejectRequestSource,OCTET,read-only,,current,,The WWN that was the source of the CT_IU contained in the corresponding instance of t11FcsRejectCtCommandString.
.1.3.6.1.2.1.162.1.4.1.1.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRejectReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),This object contains the reason code corresponding to the latest Fabric Configuration Server request rejected by the local system.
.1.3.6.1.2.1.162.1.4.1.1.7,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRejectReasonCodeExp,INTEGER,read-only,,current,noAdditionalExplanation(1):invNameIdForIEOrPort(2):ieListNotAvailable(3):ieTypeNotAvailable(4):domainIdNotAvailable(5):mgmtIdNotAvailable(6):fabNameNotAvailable(7):ielogNameNotAvailable(8):mgmtAddrListNotAvailable(9):ieInfoListNotAvailable(10):portListNotAvailable(11):portTypeNotAvailable(12):phyPortNumNotAvailable(13):attPortNameListNotAvailable(14):portStateNotAvailable(15):unableToRegIELogName(16):platformNameNoExist(17):platformNameAlreadyExists(18):platformNodeNameNoExists(19):platformNodeNameAlreadyExists(20):resourceUnavailable(21):noEntriesInLunMap(22):invalidDeviceNameLength(23):multipleAttributes(24):invalidAttribBlockLength(25):attributesMissing(26),When the corresponding instance of t11FcsRejectReasonCode has the value: 'unable to perform command request', this object contains the corresponding reason code explanation.
.1.3.6.1.2.1.162.1.4.1.1.8,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsRejectReasonVendorCode,OCTET,read-only,,current,,A registration reject vendor-specific code. This object contains the vendor-specific code of the most recently rejected Fabric Configuration Server Registration request for the particular port on the particular Fabric.
.1.3.6.1.2.1.162.1.4.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrChangeFabricIndex,Unsigned32,accessible-for-notify,,current,,The index value that identifies the Fabric on which a management address change has been detected.
.1.3.6.1.2.1.162.1.4.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMgmtAddrChangeIeName,OCTET,accessible-for-notify,,current,,The IE for which a management address change has been detected.
.1.3.6.1.2.1.162.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMIBConformance,,,,,,
.1.3.6.1.2.1.162.2.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMIBCompliances,,,,,,
.1.3.6.1.2.1.162.2.1.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMIBCompliance,,,,,,The compliance statement for entities that implement the Fabric Configuration Server.
.1.3.6.1.2.1.162.2.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsMIBGroups,,,,,,
.1.3.6.1.2.1.162.2.2.1,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryControlGroup,,,,,,A collection of objects for requesting a Fabric Configuration Server to discover the configuration of one or more Fabrics.
.1.3.6.1.2.1.162.2.2.2,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveryStatusGroup,,,,,,A collection of objects with which to monitor the status of discovery (of Fabric configurations) by Fabric Configuration Servers.
.1.3.6.1.2.1.162.2.2.3,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsDiscoveredConfigGroup,,,,,,A collection of objects to contain the Fabric configuration information discovered by Fabric Configuration Servers.
.1.3.6.1.2.1.162.2.2.4,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsStatisticsGroup,,,,,,A collection of objects for Fabric Configuration Server statistics information.
.1.3.6.1.2.1.162.2.2.5,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNotificationInfoGroup,,,,,,A collection of notification control and notification information objects for monitoring Fabric Configuration Servers.
.1.3.6.1.2.1.162.2.2.6,T11-FC-FABRIC-CONFIG-SERVER-MIB::t11FcsNotificationGroup,,,,,,A collection of notifications for monitoring Fabric Configuration Servers.
.1.3.6.1.2.1.163,ISNS-MIB::isnsMIB,,,,,,This module defines management information specific to internet Storage Name Service (iSNS) management. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4939; see the RFC itself for full legal notices.
.1.3.6.1.2.1.163.0,ISNS-MIB::isnsNotifications,,,,,,
.1.3.6.1.2.1.163.0.1,ISNS-MIB::isnsServerStart,,,,,,This notification is sent when an iSNS Server begins operation. The notification provides the following: isnsInstanceInfo : iSNS Server textual information isnsAddressTypeNotification : iSNS Server address type isnsAddressNotification : iSNS Server address isnsTcpPortNotification : iSNS Server TCP Port isnsUdpPortNotification : iSNS Server UDP Port
.1.3.6.1.2.1.163.0.2,ISNS-MIB::isnsServerShutdown,,,,,,This notification is sent when an iSNS Server is shutdown. The notification provides the following: isnsInstanceInfo : iSNS Server textual information isnsAddressTypeNotification : iSNS Server address type isnsAddressNotification : iSNS Server address isnsTcpPortNotification : iSNS Server TCP Port isnsUdpPortNotification : iSNS Server UDP Port
.1.3.6.1.2.1.163.1,ISNS-MIB::isnsObjects,,,,,,
.1.3.6.1.2.1.163.1.1,ISNS-MIB::isnsServerInfo,,,,,,
.1.3.6.1.2.1.163.1.1.1,ISNS-MIB::isnsServerTable,,not-accessible,,current,,This table provides a list of the iSNS Server instances that are managed through the same SNMP context.
.1.3.6.1.2.1.163.1.1.1.1,ISNS-MIB::isnsServerEntry,,not-accessible,isnsServerIndex,current,,This is a row in the iSNS Server instance table. The number of rows is dependent on the number of iSNS Server instances that are being managed through the same SNMP context.
.1.3.6.1.2.1.163.1.1.1.1.1,ISNS-MIB::isnsServerIndex,Unsigned32,not-accessible,,current,,This object uniquely identifies the iSNS Server being managed by the SNMP context and is the key for this table. This is an instance index for each iSNS Server being managed. The value of this object is used elsewhere in the MIB to reference specific iSNS Servers.
.1.3.6.1.2.1.163.1.1.1.1.2,ISNS-MIB::isnsServerName,OCTET,read-only,,current,,A non-unique name that can be assigned to the iSNS Server instance. If not configured, then the string SHALL be zero-length.
.1.3.6.1.2.1.163.1.1.1.1.3,ISNS-MIB::isnsServerIsnsVersion,Unsigned32,read-only,,current,,The iSNS version value as contained in messages received from the current primary server. The header of each iSNSP message contains the iSNS version of the sender. If unknown, the reported value is 0.
.1.3.6.1.2.1.163.1.1.1.1.4,ISNS-MIB::isnsServerVendorInfo,OCTET,read-only,,current,,If this server instance is utilizing the product of a particular 'vendor', then this managed object contains that vendor's name and version. Otherwise, the string SHALL be zero-length. The format of the string is as follows: Vendor Name, Vendor Version, Vendor Defined Information. Field Description --------- ---------------- Vendor Name The name of the vendor (if one exists) Vendor Version The version of the vendor product Vendor Defined This follows the second comma in the string, if one exists, and is vendor defined
.1.3.6.1.2.1.163.1.1.1.1.5,ISNS-MIB::isnsServerPhysicalIndex,Integer32,read-only,,current,,An index identifying the network interface for this iSNS Server within a network entity. This index maps to the entPhysicalIndex of entPhysicalTable table in RFC 4133. The entPhysicalClass value for the table row must be 'port', as the interface must be able to send and receive data.
.1.3.6.1.2.1.163.1.1.1.1.6,ISNS-MIB::isnsServerTcpPort,Unsigned32,read-only,,current,,Indicates the TCP port this iSNS instance is accepting iSNSP messages on, generally the iSNS well-known port. The well-known TCP port for iSNSP is 3205. If TCP is not supported by this server instance, then the value is 0.
.1.3.6.1.2.1.163.1.1.1.1.7,ISNS-MIB::isnsServerUdpPort,Unsigned32,read-only,,current,,Indicates the UDP port this iSNS instance is accepting iSNSP messages on; generally, the iSNS well-known port. The well-known UDP port for iSNSP is 3205. If UDP is not supported by this server instance, then the value is 0.
.1.3.6.1.2.1.163.1.1.1.1.8,ISNS-MIB::isnsServerDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion that this iSNS server became active or suffered a discontinuity.
.1.3.6.1.2.1.163.1.1.1.1.9,ISNS-MIB::isnsServerRole,INTEGER,read-only,,current,notSet(1):server(2):backupServer(3),The current operational mode of this iSNS Server instance. Value Description --------- ---------------- notSet The iSNS Server role is not configured. server The iSNS Server instance is an operational iSNS Server. backupServer The iSNS Server instance is currently acting as a backup.
.1.3.6.1.2.1.163.1.1.1.1.10,ISNS-MIB::isnsServerDiscoveryMethodsEnabled,BITS,read-only,,current,dhcp(0):slp(1):multicastGroupHb(2):broadcastHb(3):cfgdServerList(4):other(5),Indicates the discovery methods currently enabled for this iSNS Server instance. This allows a client to determine what discovery methods can be used for this iSNS Server. Additional methods of discovery may also be supported.
.1.3.6.1.2.1.163.1.1.1.1.11,ISNS-MIB::isnsServerDiscoveryMcGroupType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address in isnsServerDiscoveryMcGroupAddress. If the address is specified, then it must be a valid multicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsServerDiscoveryMcGroupAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.1.1.12,ISNS-MIB::isnsServerDiscoveryMcGroupAddress,OCTET,read-only,,current,,The multicast group that iSNS Heartbeat messages are sent to if multicast-based discovery has been enabled for this server instance. If not configured, then the string SHALL be zero-length. The format of this object is specified by isnsServerDiscoveryMcGroupType.
.1.3.6.1.2.1.163.1.1.1.1.13,ISNS-MIB::isnsServerEsiNonResponseThreshold,Unsigned32,read-only,,current,,Entity Status Inquiry (ESI) Non-Response Threshold - the number of ESI messages that will be sent without receiving a response before an entity is deregistered from the iSNS database. A value of 0 indicates Entities will never be deregistered due to non-receipt of ESI messages.
.1.3.6.1.2.1.163.1.1.1.1.14,ISNS-MIB::isnsServerEnableControlNodeMgtScn,INTEGER,read-only,,current,true(1):false(2),Indicates if the iSNS Server administrative option to send Management SCNs to Control Nodes is enabled. Management SCNs are used by Control Nodes to monitor and control an iSNS Server. If enabled, Control Nodes can register to receive Management SCNs.
.1.3.6.1.2.1.163.1.1.1.1.15,ISNS-MIB::isnsServerDefaultDdDdsStatus,INTEGER,read-only,,current,inNoDomain(1):inDefaultDdAndDds(2),This indicates the Discovery Domain (DD) and Discovery Domain Set (DDS) membership status for a new device when registered in the iSNS Server instance. Either the new device will not be in a DD/DDS, or will be placed into a default DD and default DDS. The default setting is inNoDomain.
.1.3.6.1.2.1.163.1.1.1.1.16,ISNS-MIB::isnsServerUpdateDdDdsSupported,BITS,read-only,,current,controlNode(0):targetIscsiNode(1):initiatorIscsiNode(2):targetIfcpNode(3):initiatorIfcpNode(4),The methods that this iSNS Server instance supports to modify Discovery Domains and Discovery Domain Sets.
.1.3.6.1.2.1.163.1.1.1.1.17,ISNS-MIB::isnsServerUpdateDdDdsEnabled,BITS,read-only,,current,controlNode(0):targetIscsiNode(1):initiatorIscsiNode(2):targetIfcpNode(3):initiatorIfcpNode(4),This indicates the methods this server instance currently allows for modifying Discovery Domains and Discovery Domain Sets.
.1.3.6.1.2.1.163.1.1.2,ISNS-MIB::isnsNumObjectsTable,,not-accessible,,current,,Table providing the number of registered objects of each type in the iSNS Server instance. The number of entries is dependent upon the number of iSNS Server instances being managed.
.1.3.6.1.2.1.163.1.1.2.1,ISNS-MIB::isnsNumObjectsEntry,,not-accessible,,current,,Entry of an iSNS Server instance.
.1.3.6.1.2.1.163.1.1.2.1.1,ISNS-MIB::isnsNumDds,Gauge32,read-only,,current,,The current total number of Discovery Domain Sets in this iSNS instance. This is the number of rows in the isnsDdsTable.
.1.3.6.1.2.1.163.1.1.2.1.2,ISNS-MIB::isnsNumDd,Gauge32,read-only,,current,,The current total number of Discovery Domains in this iSNS instance. This is the number of rows in the isnsDdTable.
.1.3.6.1.2.1.163.1.1.2.1.3,ISNS-MIB::isnsNumEntities,Gauge32,read-only,,current,,The current number of Entities registered in this iSNS Server instance. This is the number of rows in the isnsRegEntityTable for this instance.
.1.3.6.1.2.1.163.1.1.2.1.4,ISNS-MIB::isnsNumPortals,Gauge32,read-only,,current,,The current total number of Portals registered in iSNS. This is the number of rows in isnsRegPortalTable.
.1.3.6.1.2.1.163.1.1.2.1.5,ISNS-MIB::isnsNumPortalGroups,Gauge32,read-only,,current,,The current total number of Portal Groups registered in iSNS. This is the number of rows in isnsRegPgTable.
.1.3.6.1.2.1.163.1.1.2.1.6,ISNS-MIB::isnsNumIscsiNodes,Gauge32,read-only,,current,,The current total number of iSCSI node entries registered in the iSNS. This is the number rows in isnsRegIscsiNodeTable.
.1.3.6.1.2.1.163.1.1.2.1.7,ISNS-MIB::isnsNumFcPorts,Gauge32,read-only,,current,,The current total number of FC Port entries registered in the iSNS. This is the number of rows in isnsRegFcPortTable.
.1.3.6.1.2.1.163.1.1.2.1.8,ISNS-MIB::isnsNumFcNodes,Gauge32,read-only,,current,,The current total number of FC node entries registered in the iSNS. This is the number of rows in isnsRegFcNodeTable.
.1.3.6.1.2.1.163.1.1.3,ISNS-MIB::isnsControlNodeInfo,,,,,,
.1.3.6.1.2.1.163.1.1.3.1,ISNS-MIB::isnsControlNodeIscsiTable,,not-accessible,,current,,Specified iSCSI Nodes that can register or are registered as control nodes. The number of rows is dependent on the number of iSCSI Control Nodes.
.1.3.6.1.2.1.163.1.1.3.1.1,ISNS-MIB::isnsControlNodeIscsiEntry,,not-accessible,isnsServerIndex:isnsControlNodeIscsiNodeIndex,current,,This is an iSCSI Control Node entry for a specific iSNS server instance.
.1.3.6.1.2.1.163.1.1.3.1.1.1,ISNS-MIB::isnsControlNodeIscsiNodeIndex,Unsigned32,not-accessible,,current,,The index for the iSCSI storage node authorized to act as a control node.
.1.3.6.1.2.1.163.1.1.3.1.1.2,ISNS-MIB::isnsControlNodeIscsiNodeName,OCTET,read-only,,current,,The iSCSI Name of the initiator or target associated with the storage node. The iSCSI Name cannot be longer than 223 bytes. The iSNS Server internal maximum size is 224 bytes to provide NULL termination. This is the iSCSI Node Name for the storage node authorized and/or acting as a control node.
.1.3.6.1.2.1.163.1.1.3.1.1.3,ISNS-MIB::isnsControlNodeIscsiIsRegistered,INTEGER,read-only,,current,true(1):false(2),Indicates whether the control node is currently registered in the iSNS Server instance.
.1.3.6.1.2.1.163.1.1.3.1.1.4,ISNS-MIB::isnsControlNodeIscsiRcvMgtSCN,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Control Node has registered to receive Management SCNs. Management SCNs are sent to a Control Node if they are enabled, as indicated by isnsServerEnableControlNodeMgtScn, and the Control Node has registered for them.
.1.3.6.1.2.1.163.1.1.3.2,ISNS-MIB::isnsControlNodeFcPortTable,,not-accessible,,current,,Specified FC Ports that can register or are registered as control nodes. The number of rows is dependent on the number of FC Port Control Nodes.
.1.3.6.1.2.1.163.1.1.3.2.1,ISNS-MIB::isnsControlNodeFcPortEntry,,not-accessible,isnsServerIndex:isnsControlNodeFcPortWwpn,current,,FC Port control node entry.
.1.3.6.1.2.1.163.1.1.3.2.1.1,ISNS-MIB::isnsControlNodeFcPortWwpn,OCTET,not-accessible,,current,,The FC Port World Wide Port Name that can and/or is acting as a Control Node for the specified iSNS Server. A zero- length string is not valid for this managed object. This managed object, combined with the isnsServerIndex, is the key for this table.
.1.3.6.1.2.1.163.1.1.3.2.1.2,ISNS-MIB::isnsControlNodeFcPortIsRegistered,INTEGER,read-only,,current,true(1):false(2),Indicates whether the control node is currently registered in the iSNS Server instance.
.1.3.6.1.2.1.163.1.1.3.2.1.3,ISNS-MIB::isnsControlNodeFcPortRcvMgtSCN,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Control Node has registered to receive Management SCNs. Management SCNs are sent to a Control Node if they are enabled, as indicated by isnsServerEnableControlNodeMgtScn, and the Control Node has registered for them.
.1.3.6.1.2.1.163.1.1.4,ISNS-MIB::isnsDdsInfo,,,,,,
.1.3.6.1.2.1.163.1.1.4.1,ISNS-MIB::isnsDdsTable,,not-accessible,,current,,A table containing configuration information for each Discovery Domain Set (DDS) registered in the iSNS Server instance. The number of rows in the table is dependent on the number of DDSs registered in the specified iSNS server instance.
.1.3.6.1.2.1.163.1.1.4.1.1,ISNS-MIB::isnsDdsEntry,,not-accessible,isnsServerIndex:isnsDdsId,current,,Information on one Discovery Domain Set (DDS) registered in the iSNS Server instance.
.1.3.6.1.2.1.163.1.1.4.1.1.1,ISNS-MIB::isnsDdsId,Unsigned32,not-accessible,,current,,The ID that refers to this Discovery Domain Set and index to the table.
.1.3.6.1.2.1.163.1.1.4.1.1.2,ISNS-MIB::isnsDdsSymbolicName,OCTET,read-only,,current,,The Discovery Domain Set Symbolic Name field contains a unique variable-length description (up to 255 bytes) that is associated with the DDS. If a Symbolic Name is not provided, then one will be generated by the iSNS server.
.1.3.6.1.2.1.163.1.1.4.1.1.3,ISNS-MIB::isnsDdsStatus,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):reserved24(24):reserved25(25):reserved26(26):reserved27(27):reserved28(28):reserved29(29):reserved30(30):ddsEnabled(31),The status of this Discovery Domain Set (DDS).
.1.3.6.1.2.1.163.1.1.4.2,ISNS-MIB::isnsDdsMemberTable,,not-accessible,,current,,A table containing Discovery Domains (DDs) that have been assigned to specific Discovery Domain Sets (DDSs). The number of rows in the table is dependent on the number of DD to DDS relationships in the iSNS instance.
.1.3.6.1.2.1.163.1.1.4.2.1,ISNS-MIB::isnsDdsMemberEntry,,not-accessible,isnsServerIndex:isnsDdsId:isnsDdsMemberDdId,current,,The mapping of one Discovery Domain (DD) to a Discovery Domain Set (DDS). This indicates the DD is a member of the DDS.
.1.3.6.1.2.1.163.1.1.4.2.1.1,ISNS-MIB::isnsDdsMemberDdId,Unsigned32,not-accessible,,current,,The ID that identifies the Discovery Domain that is a member of the Discovery Domain Set.
.1.3.6.1.2.1.163.1.1.4.2.1.2,ISNS-MIB::isnsDdsMemberSymbolicName,OCTET,read-only,,current,,The Symbolic Name of the Discovery Domain that is a member of this DDS. This value SHALL be identical to the object isnsDdSymbolicName for the associated DD ID.
.1.3.6.1.2.1.163.1.1.5,ISNS-MIB::isnsDdInfo,,,,,,
.1.3.6.1.2.1.163.1.1.5.1,ISNS-MIB::isnsDdTable,,not-accessible,,current,,A table containing configuration information for each Discovery Domain (DD) registered in the iSNS. The number of rows in the table is dependent on the number of DDs registered in the iSNS instance.
.1.3.6.1.2.1.163.1.1.5.1.1,ISNS-MIB::isnsDdEntry,,not-accessible,isnsServerIndex:isnsDdId,current,,Information on a Discovery Domain (DD) registered in the iSNS Server instance.
.1.3.6.1.2.1.163.1.1.5.1.1.1,ISNS-MIB::isnsDdId,Unsigned32,not-accessible,,current,,The ID that refers to this Discovery Domain, and the index to the table.
.1.3.6.1.2.1.163.1.1.5.1.1.2,ISNS-MIB::isnsDdSymbolicName,OCTET,read-only,,current,,The Discovery Domain Symbolic Name field contains a unique variable-length description (up to 255 bytes) that is associated with the DD.
.1.3.6.1.2.1.163.1.1.5.1.1.3,ISNS-MIB::isnsDdFeatures,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):reserved24(24):reserved25(25):reserved26(26):reserved27(27):reserved28(28):reserved29(29):reserved30(30):bootlist(31),This defines the features the Discovery Domain has.
.1.3.6.1.2.1.163.1.1.5.2,ISNS-MIB::isnsDdIscsiMemberTable,,not-accessible,,current,,A table containing iSCSI node indexes that have been assigned to specific DDs in this iSNS Server instance. The number of rows in the table is dependent on the number of relationships between iSCSI Nodes and DDs registered in the iSNS instance.
.1.3.6.1.2.1.163.1.1.5.2.1,ISNS-MIB::isnsDdIscsiMemberEntry,,not-accessible,isnsServerIndex:isnsDdId:isnsDdIscsiMemberIndex,current,,The mapping of one iSCSI Node to a Discovery Domain to indicate membership in the DD. The indexes are the iSNS server instance, the DD ID of the Discovery Domain, and the iSCSI Node Index of the iSCSI Node.
.1.3.6.1.2.1.163.1.1.5.2.1.1,ISNS-MIB::isnsDdIscsiMemberIndex,Unsigned32,not-accessible,,current,,The index for this member iSCSI node entry.
.1.3.6.1.2.1.163.1.1.5.2.1.2,ISNS-MIB::isnsDdIscsiMemberName,OCTET,read-only,,current,,The iSCSI Name associated with the storage node. The iSCSI Name cannot be longer than 223 bytes. The iSNS server internal maximum size is 224 bytes to provide NULL termination. This is the iSCSI Name for the storage node that is a member of the DD. This value maps 1 to 1 to the isnsDdIscsiMemberIndex node index. The iSCSI Name field is too long to be easily used for an index directly. The node index used for a specific node name is only persistent across iSNS Server reinitializations for nodes that are in a Discovery Domain (DD) or are registered control nodes. This value is only required during row creation if the storage node is not yet registered in the iSNS Server instance. If the storage node is not yet registered, then the iSCSI Name MUST be provided with the iSCSI node index during row creation in order to create the 1-to-1 mapping.
.1.3.6.1.2.1.163.1.1.5.2.1.3,ISNS-MIB::isnsDdIscsiMemberIsRegistered,INTEGER,read-only,,current,true(1):false(2),This indicates whether this member of the DD is currently registered in the iSNS Server instance. iSCSI Storage Node members do not need to be currently registered in order for their iSCSI Name and Index to be added to a DD.
.1.3.6.1.2.1.163.1.1.5.3,ISNS-MIB::isnsDdPortalMemberTable,,not-accessible,,current,,A table containing currently registered and unregistered portal objects that have been explicitly assigned to specific DDs. Explicit assignment of a portal to a DD is only done when a specific set of portals are preferred for use within a DD. Otherwise, for iSCSI, the Portal Group Object should be used for identifying which portals provide access to which storage nodes. The number of rows in the table is dependent on the number of explicit relationships between portals and DDs registered in the iSNS.
.1.3.6.1.2.1.163.1.1.5.3.1,ISNS-MIB::isnsDdPortalMemberEntry,,not-accessible,isnsServerIndex:isnsDdId:isnsDdPortalMemberIndex,current,,Each entry indicates an explicit addition of a portal to a discovery domain. The explicit addition of an entity portal to a discovery domain indicates the portal is preferred for access to nodes of the entity for this discovery domain. Registered Portal Group objects are used in iSCSI to indicate mapping of portals to nodes across all discovery domains. Portals that have been explicitly mapped to a discovery domain will be returned as part of a query that is scoped to that discovery domain. If no portal of an entity has been explicitly mapped to a discovery domain, then all portals of the entity that provide access to a storage node are returned as part of a query. The table indexes are the server instance, the DD ID of the Discovery Domain, and the Portal Index of the portal.
.1.3.6.1.2.1.163.1.1.5.3.1.1,ISNS-MIB::isnsDdPortalMemberIndex,Unsigned32,not-accessible,,current,,The index for a portal explicitly contained in the discovery domain. This managed object, combined with isnsServerIndex and isnsDdId, is the key for this table.
.1.3.6.1.2.1.163.1.1.5.3.1.2,ISNS-MIB::isnsDdPortalMemberAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsDdPortalMemberAddress. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsDdPortalMemberAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.5.3.1.3,ISNS-MIB::isnsDdPortalMemberAddress,OCTET,read-only,,current,,The Inet Address for the portal. The format of this object is specified by isnsDdPortalMemberAddressType.
.1.3.6.1.2.1.163.1.1.5.3.1.4,ISNS-MIB::isnsDdPortalMemberPortType,INTEGER,read-only,,current,udp(1):tcp(2),The port type for the portal, either UDP or TCP.
.1.3.6.1.2.1.163.1.1.5.3.1.5,ISNS-MIB::isnsDdPortalMemberPort,Unsigned32,read-only,,current,,The port number for the portal. Whether the portal type is TCP or UDP is indicated by isnsDdPortalMemberPortType.
.1.3.6.1.2.1.163.1.1.5.3.1.6,ISNS-MIB::isnsDdPortalMemberIsRegistered,INTEGER,read-only,,current,true(1):false(2),This indicates whether this member of the DD is currently registered in the iSNS Server instance. Portals that are DD members do not need to be currently registered in order for them to be added to a DD.
.1.3.6.1.2.1.163.1.1.5.4,ISNS-MIB::isnsDdFcPortMemberTable,,not-accessible,,current,,A table containing FC Port World Wide Names (WWN) that have been assigned to specific DDs. The number of rows in the table is dependent on the number of relationships between FC Ports and DDs registered in the iSNS.
.1.3.6.1.2.1.163.1.1.5.4.1,ISNS-MIB::isnsDdFcPortMemberEntry,,not-accessible,isnsServerIndex:isnsDdId:isnsDdFcPortMemberPortName,current,,The association of one FC Port with a Discovery Domain. Membership of an FC Port in a Discovery Domain is indicated by creating a row for the appropriate DD ID and FC Port WWN.
.1.3.6.1.2.1.163.1.1.5.4.1.1,ISNS-MIB::isnsDdFcPortMemberPortName,OCTET,not-accessible,,current,,The Port WWN of the FC Port that is a member of the DD. The value MUST be a valid FC WWN, as per the FC-GS (Fibre Channel - Generic Services) standard. This managed object, combined with the isnsServerIndex and isnsDdId are the key for this table. A zero-length string is not a valid value for this managed object.
.1.3.6.1.2.1.163.1.1.5.4.1.2,ISNS-MIB::isnsDdFcPortMemberIsRegistered,INTEGER,read-only,,current,true(1):false(2),This indicates whether this member of the DD is currently registered in the iSNS Server instance.
.1.3.6.1.2.1.163.1.1.6,ISNS-MIB::isnsReg,,,,,,
.1.3.6.1.2.1.163.1.1.6.1,ISNS-MIB::isnsRegEntityInfo,,,,,,
.1.3.6.1.2.1.163.1.1.6.1.1,ISNS-MIB::isnsRegEntityTable,,not-accessible,,current,,A table containing registered Entity objects in each iSNS server instance. The number of entries in the table is dependent on the number of Entity objects registered in the iSNS Server instances. All Entity objects are registered in the iSNS using the iSNS protocol.
.1.3.6.1.2.1.163.1.1.6.1.1.1,ISNS-MIB::isnsRegEntityEntry,,not-accessible,isnsServerIndex:isnsRegEntityIndex,current,,Information on one registered Entity object in an iSNS server instance.
.1.3.6.1.2.1.163.1.1.6.1.1.1.1,ISNS-MIB::isnsRegEntityIndex,Unsigned32,not-accessible,,current,,The Entity Index for this entity. This index is assigned by the iSNS Server when an Entity is initially registered. The Entity Index can be used to represent a registered Entity object in situations where the Entity EID would be too long/unwieldy. Zero is not a valid value for this object.
.1.3.6.1.2.1.163.1.1.6.1.1.1.2,ISNS-MIB::isnsRegEntityEID,OCTET,read-only,,current,,The EID is a unique registered Entity object identifier, as specified in the iSNS Specification. This is the iSNS Entity Identifier for the registered Entity object.
.1.3.6.1.2.1.163.1.1.6.1.1.1.3,ISNS-MIB::isnsRegEntityProtocol,Unsigned32,read-only,,current,,The block storage protocol supported by this entity, as defined in the iSNS Specification, Section 6.2.2. The following values are initially assigned. Type Value Entity Type ---------- ----------- 1 No Protocol 2 iSCSI 3 iFCP All Others As assigned by IANA The full set of current Block Storage Protocols are specified in the IANA-maintained registry of assigned iSNS parameters. Please refer to RFC 4171 and the iSNS parameters maintained at IANA.
.1.3.6.1.2.1.163.1.1.6.1.1.1.4,ISNS-MIB::isnsRegEntityManagementAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsRegEntityManagementAddress. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsRegEntityManagementAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.6.1.1.1.5,ISNS-MIB::isnsRegEntityManagementAddress,OCTET,read-only,,current,,The iSNS Management IP Address for the registered Entity object. The format of this object is specified by isnsRegEntityManagementAddressType.
.1.3.6.1.2.1.163.1.1.6.1.1.1.6,ISNS-MIB::isnsRegEntityTimestamp,TimeTicks,read-only,,current,,The iSNS Entity Registration Timestamp for the registered Entity object. This is the most recent date and time that the registered Entity object, and associated registered objects contained in the Entity, were registered or updated.
.1.3.6.1.2.1.163.1.1.6.1.1.1.7,ISNS-MIB::isnsRegEntityVersionMin,Unsigned32,read-only,,current,,The minimum version supported for the block storage protocol specified by isnsRegEntityProtocol. The protocol version specified can be from 1 to 254. A value of 255 is a wildcard value, indicating no minimum version value has been specified for this Entity. Entity registrations with an isnsRegEntityProtocol of 'No Protocol' SHALL have an isnsRegEntityVersionMin value of 0.
.1.3.6.1.2.1.163.1.1.6.1.1.1.8,ISNS-MIB::isnsRegEntityVersionMax,Unsigned32,read-only,,current,,The maximum version supported for the block storage protocol specified by isnsRegEntityProtocol. The protocol version specified can be from 1 to 254. A value of 255 is a wildcard value, indicating no maximum version value has been specified for this Entity. Entity registrations with an isnsRegEntityProtocol of 'No Protocol' SHALL have an isnsRegEntityVersionMax value of 0.
.1.3.6.1.2.1.163.1.1.6.1.1.1.9,ISNS-MIB::isnsRegEntityRegistrationPeriod,Unsigned32,read-only,,current,,The iSNS Entity Status Inquiry (ESI) registration period, which indicates the maximum time, in seconds, that the registration will be maintained without receipt of an iSNSP message from the entity. If the Registration Period is set to 0, then the Entity SHALL NOT be deregistered due to no contact with the entity.
.1.3.6.1.2.1.163.1.1.6.1.2,ISNS-MIB::isnsRegEntityNumObjectsTable,,not-accessible,,current,,A table containing information on the number of registered objects associated with a registered Entity in the iSNS server instance. The number of entries in the table is dependent on the number of registered Entity objects in the iSNS.
.1.3.6.1.2.1.163.1.1.6.1.2.1,ISNS-MIB::isnsRegEntityNumObjectsEntry,,not-accessible,isnsServerIndex:isnsRegEntityIndex,current,,Information on the number of registered objects associated with a registered Entity object in an iSNS Server instance.
.1.3.6.1.2.1.163.1.1.6.1.2.1.1,ISNS-MIB::isnsRegEntityInfoNumPortals,Gauge32,read-only,,current,,The number of Portals associated with this Entity.
.1.3.6.1.2.1.163.1.1.6.1.2.1.2,ISNS-MIB::isnsRegEntityInfoNumPortalGroups,Gauge32,read-only,,current,,The number of Portal Groups associated with this Entity.
.1.3.6.1.2.1.163.1.1.6.1.2.1.3,ISNS-MIB::isnsRegEntityInfoNumIscsiNodes,Gauge32,read-only,,current,,The number of iSCSI Storage Nodes associated with this Entity.
.1.3.6.1.2.1.163.1.1.6.1.2.1.4,ISNS-MIB::isnsRegEntityInfoNumFcPorts,Gauge32,read-only,,current,,The number of FC Ports associated with this Entity.
.1.3.6.1.2.1.163.1.1.6.1.2.1.5,ISNS-MIB::isnsRegEntityInfoNumFcNodes,Gauge32,read-only,,current,,The number of FC Nodes associated with this Entity.
.1.3.6.1.2.1.163.1.1.6.2,ISNS-MIB::isnsRegPortalInfo,,,,,,
.1.3.6.1.2.1.163.1.1.6.2.1,ISNS-MIB::isnsRegPortalTable,,not-accessible,,current,,A table containing the registered Portals in the iSNS. The number of entries is dependent on the number of Portals registered in the iSNS.
.1.3.6.1.2.1.163.1.1.6.2.1.1,ISNS-MIB::isnsRegPortalEntry,,not-accessible,isnsServerIndex:isnsRegEntityIndex:isnsRegPortalPortalIndex,current,,Information on one registered Entity Portal in the iSNS. The Entity Index is part of the table index to quickly find Portals that support a specific Entity.
.1.3.6.1.2.1.163.1.1.6.2.1.1.1,ISNS-MIB::isnsRegPortalPortalIndex,Unsigned32,not-accessible,,current,,The index for this Entity Portal.
.1.3.6.1.2.1.163.1.1.6.2.1.1.2,ISNS-MIB::isnsRegPortalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsRegPortalAddress. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsRegPortalAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.6.2.1.1.3,ISNS-MIB::isnsRegPortalAddress,OCTET,read-only,,current,,The Inet Address for this Portal as defined in the iSNS Specification, RFC 4171. The format of this object is specified by isnsRegPortalAddressType.
.1.3.6.1.2.1.163.1.1.6.2.1.1.4,ISNS-MIB::isnsRegPortalPortType,INTEGER,read-only,,current,udp(1):tcp(2),The port type for this Portal, either UDP or TCP, as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.2.1.1.5,ISNS-MIB::isnsRegPortalPort,Unsigned32,read-only,,current,,The port number for this Portal as defined in the iSNS Specification, RFC 4171. Whether the Portal type is TCP or UDP is indicated by isnsRegPortalPortType.
.1.3.6.1.2.1.163.1.1.6.2.1.1.6,ISNS-MIB::isnsRegPortalSymbolicName,OCTET,read-only,,current,,The Symbolic Name for this Portal as defined in the iSNS Specification, RFC 4171. If not provided, then the string SHALL be zero-length.
.1.3.6.1.2.1.163.1.1.6.2.1.1.7,ISNS-MIB::isnsRegPortalEsiInterval,Unsigned32,read-only,,current,,The Entity Status Inquiry (ESI) Interval for this Portal as defined in the iSNS Specification, RFC 4171. A value of 0 indicates that ESI monitoring has not been configured for this Portal.
.1.3.6.1.2.1.163.1.1.6.2.1.1.8,ISNS-MIB::isnsRegPortalEsiPortType,INTEGER,read-only,,current,udp(1):tcp(2),The port type for the ESI Port, either UDP or TCP, as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.2.1.1.9,ISNS-MIB::isnsRegPortalEsiPort,Unsigned32,read-only,,current,,The TCP or UDP port number used for ESI monitoring. Whether the port type is TCP or UDP is indicated by isnsRegPortalEsiPortType. A value of 0 indicates that ESI monitoring is not enabled for this Portal.
.1.3.6.1.2.1.163.1.1.6.2.1.1.10,ISNS-MIB::isnsRegPortalScnPortType,INTEGER,read-only,,current,udp(1):tcp(2),The port type for the SCN Port, either UDP or TCP, as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.2.1.1.11,ISNS-MIB::isnsRegPortalScnPort,Unsigned32,read-only,,current,,The TCP or UDP port used to receive SCN messages from the iSNS Server. Whether the port type is TCP or UDP is indicated by isnsRegPortalScnPortType. A value of 0 indicates that SCN message receipt is not enabled for this Portal.
.1.3.6.1.2.1.163.1.1.6.2.1.1.12,ISNS-MIB::isnsRegPortalSecurityInfo,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):reserved24(24):tunnelModePreferred(25):transportModePreferred(26):pfsEnabled(27):agressiveModeEnabled(28):mainModeEnabled(29):ikeIPsecEnabled(30):bitmapVALID(31),Indicates security attribute settings for the Portal as registered in the iSNS server. The bit for bitmapVALID must be set in order for this attribute to contain valid information. Setting a bit to 1 indicates the feature is enabled.
.1.3.6.1.2.1.163.1.1.6.3,ISNS-MIB::isnsRegPortalGroupInfo,,,,,,
.1.3.6.1.2.1.163.1.1.6.3.1,ISNS-MIB::isnsRegPgTable,,not-accessible,,current,,A table containing the registered Portal Groups (PGs) in the iSNS Server instance. The number of entries is dependent on the number of Portal Groups registered in the iSNS.
.1.3.6.1.2.1.163.1.1.6.3.1.1,ISNS-MIB::isnsRegPgEntry,,not-accessible,isnsServerIndex:isnsRegEntityIndex:isnsRegPgIndex,current,,Information on one registered Portal Group in the iSNS server instance. The Entity Index is part of the table index to quickly find Portal Groups that support Portals and iSCSI Storage Nodes in a specific Entity.
.1.3.6.1.2.1.163.1.1.6.3.1.1.1,ISNS-MIB::isnsRegPgIndex,Unsigned32,not-accessible,,current,,The PG Index for this node. The index is created by the iSNS Server instance for uniquely identifying registered objects. The PG object is registered at the same time a Portal or Storage Node is registered using the iSNS protocol.
.1.3.6.1.2.1.163.1.1.6.3.1.1.2,ISNS-MIB::isnsRegPgIscsiNodeIndex,Unsigned32,read-only,,current,,The index for the iSCSI Node associated with this PG. This index can be used to reference the isnsRegIscsiNodeTable.
.1.3.6.1.2.1.163.1.1.6.3.1.1.3,ISNS-MIB::isnsRegPgIscsiName,OCTET,read-only,,current,,The iSCSI Name of the initiator or target associated with the storage node. The iSCSI Name cannot be longer than 223 bytes. The iSNS Server internal maximum size is 224 bytes to provide NULL termination. This is the PG iSCSI Name that uniquely identifies the iSCSI Storage Node that is associated with this PG.
.1.3.6.1.2.1.163.1.1.6.3.1.1.4,ISNS-MIB::isnsRegPgPortalPortalIndex,Unsigned32,read-only,,current,,The Portal Index for the Portal associated with this PG. This index can be used to reference the isnsRegPortalTable.
.1.3.6.1.2.1.163.1.1.6.3.1.1.5,ISNS-MIB::isnsRegPgPortalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsRegPgPortalAddress. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsRegPgPortalAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.6.3.1.1.6,ISNS-MIB::isnsRegPgPortalAddress,OCTET,read-only,,current,,The Inet Address for the Portal that is associated with the PG. The format of this object is specified by isnsRegPgPortalAddressType.
.1.3.6.1.2.1.163.1.1.6.3.1.1.7,ISNS-MIB::isnsRegPgPortalPortType,INTEGER,read-only,,current,udp(1):tcp(2),The port type, either UDP or TCP, for the Portal that is associated with this registered PG object.
.1.3.6.1.2.1.163.1.1.6.3.1.1.8,ISNS-MIB::isnsRegPgPortalPort,Unsigned32,read-only,,current,,The port number for the Portal that is associated with this registered PG object. Whether the Portal type is TCP or UDP is indicated by isnsRegPgPortalPortType.
.1.3.6.1.2.1.163.1.1.6.3.1.1.9,ISNS-MIB::isnsRegPgPGT,Integer32,read-only,,current,,The Portal Group Tag (PGT) for the registered iSCSI Portal Group object in an iSNS Server instance. This indicates the tag value that the Portal uses for access to the iSCSI Storage Node. The PGT is used for coordinated access between multiple Portals, as described in the iSCSI Specification, RFC 3720. A PGT with no association is a NULL value. The value of -1 indicates a NULL value.
.1.3.6.1.2.1.163.1.1.6.4,ISNS-MIB::isnsRegIscsiNodeInfo,,,,,,
.1.3.6.1.2.1.163.1.1.6.4.1,ISNS-MIB::isnsRegIscsiNodeTable,,not-accessible,,current,,A table containing the registered iSCSI Nodes in the iSNS server instance. Storage devices register using the iSNS protocol. While a device cannot be registered in an iSNS server using SNMP, an entry can be deleted in order to remove 'stale' entries. The number of entries is related to the number of iSCSI nodes registered in the iSNS.
.1.3.6.1.2.1.163.1.1.6.4.1.1,ISNS-MIB::isnsRegIscsiNodeEntry,,not-accessible,isnsServerIndex:isnsRegEntityIndex:isnsRegIscsiNodeIndex,current,,Information on one iSCSI node that has been registered in the iSNS Server instance. New rows cannot be added using SNMP.
.1.3.6.1.2.1.163.1.1.6.4.1.1.1,ISNS-MIB::isnsRegIscsiNodeIndex,Unsigned32,not-accessible,,current,,The index for this iSCSI node.
.1.3.6.1.2.1.163.1.1.6.4.1.1.2,ISNS-MIB::isnsRegIscsiNodeName,OCTET,read-only,,current,,The iSCSI Name of the initiator or target associated with the storage node. The iSCSI Name cannot be longer than 223 bytes. The iSNS Server internal maximum size is 224 bytes to provide NULL termination. This is the iSCSI Name that uniquely identifies the initiator, initiator/target, target, or control node in the network.
.1.3.6.1.2.1.163.1.1.6.4.1.1.3,ISNS-MIB::isnsRegIscsiNodeType,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):reserved24(24):reserved25(25):reserved26(26):reserved27(27):reserved28(28):control(29):initiator(30):target(31),The Node Type defining the functions of this iSCSI node.
.1.3.6.1.2.1.163.1.1.6.4.1.1.4,ISNS-MIB::isnsRegIscsiNodeAlias,OCTET,read-only,,current,,The Alias name of the iSCSI node. This is a variable-length text-based description of up to 255 bytes.
.1.3.6.1.2.1.163.1.1.6.4.1.1.5,ISNS-MIB::isnsRegIscsiNodeScnTypes,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):initiatorAndSelfOnly(24):targetAndSelfOnly(25):managementRegistrationScn(26):objectRemoved(27):objectAdded(28):objectUpdated(29):ddOrDdsMemberRemoved(30):ddOrDdsMemberAdded(31),The State Change Notification (SCN) types enabled for this iSCSI node.
.1.3.6.1.2.1.163.1.1.6.4.1.1.6,ISNS-MIB::isnsRegIscsiNodeWwnToken,OCTET,read-only,,current,,This contains a globally unique 64-bit integer value that can be used to represent the World Wide Node Name of the iSCSI device in a Fibre Channel fabric. This identifier is used during the device registration process, and MUST conform to the requirements in RFC 4171. A zero-length string for this managed object indicates that a Node WWN token has not been assigned.
.1.3.6.1.2.1.163.1.1.6.4.1.1.7,ISNS-MIB::isnsRegIscsiNodeAuthMethod,OCTET,read-only,,current,,This attribute contains a null-terminated string containing UTF-8 text listing the iSCSI authentication methods enabled for this iSCSI Node, in order of preference. The text values used to identify iSCSI authentication methods are embedded in this string attribute and delineated by a comma. The text values are identical to those found in RFC 3720 - iSCSI. Additional vendor-specific text values are also possible.
.1.3.6.1.2.1.163.1.1.6.5,ISNS-MIB::isnsRegFcNodeInfo,,,,,,
.1.3.6.1.2.1.163.1.1.6.5.1,ISNS-MIB::isnsRegFcNodeTable,,not-accessible,,current,,A table containing the registered FC Nodes in the iSNS. This supports iFCP as defined in RFC 4172.
.1.3.6.1.2.1.163.1.1.6.5.1.1,ISNS-MIB::isnsRegFcNodeEntry,,not-accessible,isnsServerIndex:isnsRegFcNodeWwnn,current,,Information on one registered FC node that has been registered in the iSNS.
.1.3.6.1.2.1.163.1.1.6.5.1.1.1,ISNS-MIB::isnsRegFcNodeWwnn,OCTET,not-accessible,,current,,The FC Node World Wide Node Name as defined in the iSNS Specification, RFC 4171. A zero-length string is not valid for this managed object.
.1.3.6.1.2.1.163.1.1.6.5.1.1.2,ISNS-MIB::isnsRegFcNodeSymbolicName,OCTET,read-only,,current,,The FC Node Symbolic Name of the node as defined in the iSNS Specification, RFC 4171. This is a variable-length text-based description. If not provided, then the string SHALL be zero-length.
.1.3.6.1.2.1.163.1.1.6.5.1.1.3,ISNS-MIB::isnsRegFcNodeAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsRegFcNodeAddress. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsRegFcNodeAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.6.5.1.1.4,ISNS-MIB::isnsRegFcNodeAddress,OCTET,read-only,,current,,The FC Node Inet address of the node as defined in the iSNS Specification, RFC 4171. The format of this object is specified by isnsRegFcNodeAddressType.
.1.3.6.1.2.1.163.1.1.6.5.1.1.5,ISNS-MIB::isnsRegFcNodeIPA,OCTET,read-only,,current,,This managed object identifies the FC Initial Process Associator of the node as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.1.1.6,ISNS-MIB::isnsRegFcNodeProxyIscsiName,OCTET,read-only,,current,,The iSCSI Name used to represent the FC Node in the IP network. It is used as a pointer to the matching iSCSI Name entry in the iSNS Server. Its value is usually registered by an FC-iSCSI gateway connecting the IP network to the fabric containing the FC device.
.1.3.6.1.2.1.163.1.1.6.5.1.1.7,ISNS-MIB::isnsRegFcNodeNumFcPorts,Gauge32,read-only,,current,,The number of FC Ports associated with this FC Node.
.1.3.6.1.2.1.163.1.1.6.5.2,ISNS-MIB::isnsRegFcPortTable,,not-accessible,,current,,Information on registered FC N_Ports in the iSNS. FC Ports are associated with registered FC Nodes. This supports iFCP as defined in RFC 4172.
.1.3.6.1.2.1.163.1.1.6.5.2.1,ISNS-MIB::isnsRegFcPortEntry,,not-accessible,isnsServerIndex:isnsRegEntityIndex:isnsRegFcPortWwpn,current,,Information on one FC Port that has been registered in iSNS.
.1.3.6.1.2.1.163.1.1.6.5.2.1.1,ISNS-MIB::isnsRegFcPortWwpn,OCTET,not-accessible,,current,,The FC Port's World Wide Port Name as defined in the iSNS Specification, RFC 4171. A zero-length string is not valid for this managed object.
.1.3.6.1.2.1.163.1.1.6.5.2.1.2,ISNS-MIB::isnsRegFcPortID,OCTET,read-only,,current,,The FC Port's Port ID as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.2.1.3,ISNS-MIB::isnsRegFcPortType,Unsigned32,read-only,,current,,The FC Port Type as defined in the iSNS Specification, RFC 4171, and the Fibre Channel Generic Services Specification. Current values are as shown below: unknown (0), nPort (1), nlPort (2), fNlPort (3), fPort (129), -- x'81' flPort (130), -- x'82' ePort (132), -- x'84' bPort (133), -- x'85' mFcpPort (65297), -- x'FF11' iFcpPort (65298), -- x'FF12' unknownEnd (65535) The future assignment of any additional values will be documented in a revision of RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.2.1.4,ISNS-MIB::isnsRegFcPortSymbolicName,OCTET,read-only,,current,,The FC Port Symbolic Name as defined in the iSNS Specification, RFC 4171. If not provided, then the string SHALL be zero-length.
.1.3.6.1.2.1.163.1.1.6.5.2.1.5,ISNS-MIB::isnsRegFcPortFabricPortWwn,OCTET,read-only,,current,,The Fabric Port WWN for this entry as defined in the iSNS Specification, RFC 4171. A zero-length string for this managed object indicates that the Fabric Port WWN is not known, or has not yet been registered with the iSNS Server.
.1.3.6.1.2.1.163.1.1.6.5.2.1.6,ISNS-MIB::isnsRegFcPortHA,OCTET,read-only,,current,,The FC Port Hard Address as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.2.1.7,ISNS-MIB::isnsRegFcPortAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsRegFcPortAddress. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsRegFcPortAddress is the zero-length string.
.1.3.6.1.2.1.163.1.1.6.5.2.1.8,ISNS-MIB::isnsRegFcPortAddress,OCTET,read-only,,current,,The FC Port Inet Address as defined in the iSNS Specification, RFC 4171. The format of this object is specified by isnsRegFcPortAddressType.
.1.3.6.1.2.1.163.1.1.6.5.2.1.9,ISNS-MIB::isnsRegFcPortFcCos,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):reserved24(24):reserved25(25):reserved26(26):reserved27(27):class3(28):class2(29),The FC Port Class of Service as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.2.1.10,ISNS-MIB::isnsRegFcPortFc4Types,OCTET,read-only,,current,,The FC Port FC-4 Types as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.2.1.11,ISNS-MIB::isnsRegFcPortFc4Descr,OCTET,read-only,,current,,The FC Port FC-4 Descriptor as defined in the iSNS Specification, RFC 4171. The FC-4 Descriptor cannot be longer than 255 bytes. The iSNS Server internal maximum size is 256 bytes to provide NULL termination.
.1.3.6.1.2.1.163.1.1.6.5.2.1.12,ISNS-MIB::isnsRegFcPortFc4Features,OCTET,read-only,,current,,The FC Port FC-4 Features as defined in the iSNS Specification, RFC 4171.
.1.3.6.1.2.1.163.1.1.6.5.2.1.13,ISNS-MIB::isnsRegFcPortScnTypes,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):initiatorAndSelfOnly(24):targetAndSelfOnly(25):managementRegistrationScn(26):objectRemoved(27):objectAdded(28):objectUpdated(29):ddOrDdsMemberRemoved(30):ddOrDdsMemberAdded(31),The iFCP State Change Notification (SCN) types enabled for the registered object.
.1.3.6.1.2.1.163.1.1.6.5.2.1.14,ISNS-MIB::isnsRegFcPortRole,BITS,read-only,,current,reserved0(0):reserved1(1):reserved2(2):reserved3(3):reserved4(4):reserved5(5):reserved6(6):reserved7(7):reserved8(8):reserved9(9):reserved10(10):reserved11(11):reserved12(12):reserved13(13):reserved14(14):reserved15(15):reserved16(16):reserved17(17):reserved18(18):reserved19(19):reserved20(20):reserved21(21):reserved22(22):reserved23(23):reserved24(24):reserved25(25):reserved26(26):reserved27(27):reserved28(28):control(29):initiator(30):target(31),The FC Port Role defines the role of the registered object.
.1.3.6.1.2.1.163.1.1.6.5.2.1.15,ISNS-MIB::isnsRegFcPortFcNodeWwnn,OCTET,read-only,,current,,The FC Node World Wide Node Name that is associated with this FC Port as defined in the iSNS Specification, RFC 4171. This managed object may contain a zero-length string prior to a device registering this value with the iSNS Server.
.1.3.6.1.2.1.163.1.1.6.5.2.1.16,ISNS-MIB::isnsRegFcPortPpnWwn,OCTET,read-only,,current,,The Permanent Port Name (PPN) attribute is the FC Port Name WWPN of the first Storage Node registered in the iSNS Database that is associated with a particular FC Device (FC Node). The PPN of all subsequent Storage Node registrations that are associated with that FC Device (FC Node) SHALL be set to the FC Port Name WWPN of the first Storage Node, as defined in the iSNS Specification, RFC 4171. This managed object may contain a zero-length string prior to a device registering this value with the iSNS Server.
.1.3.6.1.2.1.163.1.1.6.5.3,ISNS-MIB::isnsRegFcNodePortTable,,not-accessible,,current,,A table containing the mapping of a registered FC Node and associated registered iFCP Port to the supporting registered Entity object in an iSNS Server instance.
.1.3.6.1.2.1.163.1.1.6.5.3.1,ISNS-MIB::isnsRegFcNodePortEntry,,not-accessible,isnsServerIndex:isnsRegFcNodeWwnn:isnsRegFcPortWwpn,current,,Information on one mapping from an FC Node and iFCP Port to an Entity object registered in an iSNS.
.1.3.6.1.2.1.163.1.1.6.5.3.1.1,ISNS-MIB::isnsRegFcNodePortEntityIndex,Unsigned32,read-only,,current,,The Entity Index for the registered Entity object associated with the FC Port and FC Node. This managed object may contain the value of zero prior to a device registering this value with the iSNS Server.
.1.3.6.1.2.1.163.1.2,ISNS-MIB::isnsNotificationsInfo,,,,,,
.1.3.6.1.2.1.163.1.2.1,ISNS-MIB::isnsInstanceInfo,OCTET,accessible-for-notify,,current,,Textual information about the notification event and the iSNS Server generating the notification. An example is: iSNS Server Started.
.1.3.6.1.2.1.163.1.2.2,ISNS-MIB::isnsAddressNotificationType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Inet address in isnsAddressNotification. If the address is specified, then it must be a valid unicast address and the value of this object must be ipv4(1), ipv6(2), ipv4z(3), or ipv6z(4); otherwise, the value of this object is unknown(0), and the value of isnsAddressNotification is the zero-length string.
.1.3.6.1.2.1.163.1.2.3,ISNS-MIB::isnsAddressNotification,OCTET,accessible-for-notify,,current,,Identifies the IP address of the iSNS Server. The format of this object is specified by isnsAddressNotificationType. The IP address will always be specified in the notification unless an error causes the IP address to not be known.
.1.3.6.1.2.1.163.1.2.4,ISNS-MIB::isnsTcpPortNotification,Unsigned32,accessible-for-notify,,current,,Indicates the TCP port the iSNS Server is using, or 0 if TCP-based registrations are not supported.
.1.3.6.1.2.1.163.1.2.5,ISNS-MIB::isnsUdpPortNotification,Unsigned32,accessible-for-notify,,current,,Indicates the UDP port the iSNS Server is using, or 0 if UDP-based registrations are not supported.
.1.3.6.1.2.1.163.2,ISNS-MIB::isnsConformance,,,,,,
.1.3.6.1.2.1.163.2.1,ISNS-MIB::isnsCompliances,,,,,,
.1.3.6.1.2.1.163.2.1.1,ISNS-MIB::isnsIscsiServerCompliance,,,,,,Initial compliance statement for an iSNS Server providing support to iSCSI clients.
.1.3.6.1.2.1.163.2.1.2,ISNS-MIB::isnsIfcpServerCompliance,,,,,,Initial compliance statement for an iSNS Server providing support to iFCP Clients.
.1.3.6.1.2.1.163.2.2,ISNS-MIB::isnsGroups,,,,,,
.1.3.6.1.2.1.163.2.2.1,ISNS-MIB::isnsServerAttributesGroup,,,,,,iSNS Server attributes.
.1.3.6.1.2.1.163.2.2.2,ISNS-MIB::isnsServerNumObjectsGroup,,,,,,Managed objects indicating the number of registered objects in an iSNS Server or the number of registered objects associated with a registered Entity. These managed objects are optional to implement.
.1.3.6.1.2.1.163.2.2.3,ISNS-MIB::isnsServerIscsiControlNodeGroup,,,,,,iSNS Server iSCSI control node managed objects.
.1.3.6.1.2.1.163.2.2.4,ISNS-MIB::isnsServerIfcpPortControlNodeGroup,,,,,,iSNS Server iFCP Port control node managed objects.
.1.3.6.1.2.1.163.2.2.5,ISNS-MIB::isnsServerIscsiDdsDdObjGroup,,,,,,iSNS Server DDS and DD managed objects for iSCSI.
.1.3.6.1.2.1.163.2.2.6,ISNS-MIB::isnsServerIfcpDdsDdObjGroup,,,,,,iSNS Server DDS and DD managed objects for iFCP.
.1.3.6.1.2.1.163.2.2.7,ISNS-MIB::isnsServerRegIscsiObjGroup,,,,,,iSNS Server registered iSCSI managed objects.
.1.3.6.1.2.1.163.2.2.8,ISNS-MIB::isnsServerRegIfcpObjGroup,,,,,,iSNS Server registered iFCP managed objects.
.1.3.6.1.2.1.163.2.2.9,ISNS-MIB::isnsNotificationsObjGroup,,,,,,iSNS Notification managed objects.
.1.3.6.1.2.1.163.2.2.10,ISNS-MIB::isnsServerNotificationGroup,,,,,,iSNS Server Notification managed objects.
.1.3.6.1.2.1.164,URI-TC-MIB::uriTcMIB,,,,,,This MIB module defines textual conventions for representing URIs, as defined by RFC 3986 STD 66.
.1.3.6.1.2.1.165,LANGTAG-TC-MIB::langTagTcMIB,,,,,,This MIB module defines a textual convention for representing BCP 47 language tags.
.1.3.6.1.2.1.166,IF-CAP-STACK-MIB::ifCapStackMIB,,,,,,The objects in this MIB module are used to describe cross-connect capabilities of stacked (layered) interfaces, complementing ifStackTable and ifInvStackTable defined in IF-MIB and IF-INVERTED-STACK-MIB, respectively. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5066; see the RFC itself for full legal notices.
.1.3.6.1.2.1.166.1,IF-CAP-STACK-MIB::ifCapStackObjects,,,,,,
.1.3.6.1.2.1.166.1.1,IF-CAP-STACK-MIB::ifCapStackTable,,not-accessible,,current,,This table, modeled after ifStackTable from IF-MIB, contains information on the possible 'on-top-of' relationships between the multiple sub-layers of network interfaces (as opposed to actual relationships described in ifStackTable). In particular, it contains information on which sub-layers MAY possibly run 'on top of' which other sub-layers, as determined by cross-connect capability of the device, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x can be connected to run on top of the sub-layer with ifIndex value y, then this table contains: ifCapStackStatus.x.y=true The ifCapStackStatus.x.y row does not exist if it is impossible to connect between the sub-layers x and y. Note that for most stacked interfaces (e.g., 2BASE-TL) there's always at least one higher-level interface (e.g., PCS port) for each lower-level interface (e.g., PME) and at least one lower-level interface for each higher-level interface, that is, there is at least a single row with a 'true' status for any such existing value of x or y. This table is read-only as it describes device capabilities.
.1.3.6.1.2.1.166.1.1.1,IF-CAP-STACK-MIB::ifCapStackEntry,,not-accessible,ifStackHigherLayer:ifStackLowerLayer,current,,Information on a particular relationship between two sub-layers, specifying that one sub-layer MAY possibly run on 'top' of the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable (interface index for lower and higher layer, respectively).
.1.3.6.1.2.1.166.1.1.1.1,IF-CAP-STACK-MIB::ifCapStackStatus,INTEGER,read-only,,current,true(1):false(2),The status of the 'cross-connect capability' relationship between two sub-layers. The following values can be returned: true(1) - indicates that the sub-layer interface, identified by the ifStackLowerLayer MAY be connected to run 'below' the sub-layer interface, identified by the ifStackHigherLayer index. false(2) - the sub-layer interfaces cannot be connected temporarily due to unavailability of the interface(s), e.g., one of the interfaces is located on an absent pluggable module. Note that lower-layer interface availability per higher-layer, indicated by the value of 'true', can be constrained by other parameters, for example, by the aggregation capacity of a higher-layer interface or by the lower-layer interface in question being already connected to another higher-layer interface. In order to ensure that a particular sub-layer can be connected to another sub-layer, all respective objects (e.g., ifCapStackTable, ifStackTable, and efmCuPAFCapacity for EFMCu interfaces) SHALL be inspected. This object is read-only, unlike ifStackStatus, as it describes a cross-connect capability.
.1.3.6.1.2.1.166.1.2,IF-CAP-STACK-MIB::ifInvCapStackTable,,not-accessible,,current,,A table containing information on the possible relationships between the multiple sub-layers of network interfaces. This table, modeled after ifInvStackTable from IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable defined in this MIB module. In particular, this table contains information on which sub-layers MAY run 'underneath' which other sub-layers, where each sub-layer corresponds to a conceptual row in the ifTable. For example, when the sub-layer with ifIndex value x MAY be connected to run underneath the sub-layer with ifIndex value y, then this table contains: ifInvCapStackStatus.x.y=true This table contains exactly the same number of rows as the ifCapStackTable, but the rows appear in a different order. This table is read-only as it describes a cross-connect capability.
.1.3.6.1.2.1.166.1.2.1,IF-CAP-STACK-MIB::ifInvCapStackEntry,,not-accessible,ifStackLowerLayer:ifStackHigherLayer,current,,Information on a particular relationship between two sub- layers, specifying that one sub-layer MAY run underneath the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable.
.1.3.6.1.2.1.166.1.2.1.1,IF-CAP-STACK-MIB::ifInvCapStackStatus,INTEGER,read-only,,current,true(1):false(2),The status of the possible 'cross-connect capability' relationship between two sub-layers. An instance of this object exists for each instance of the ifCapStackStatus object, and vice versa. For example, if the variable ifCapStackStatus.H.L exists, then the variable ifInvCapStackStatus.L.H must also exist, and vice versa. In addition, the two variables always have the same value. The ifInvCapStackStatus object is read-only, as it describes a cross-connect capability.
.1.3.6.1.2.1.166.2,IF-CAP-STACK-MIB::ifCapStackConformance,,,,,,
.1.3.6.1.2.1.166.2.1,IF-CAP-STACK-MIB::ifCapStackGroups,,,,,,
.1.3.6.1.2.1.166.2.1.1,IF-CAP-STACK-MIB::ifCapStackGroup,,,,,,A collection of objects providing information on the cross-connect capability of multi-layer (stacked) network interfaces.
.1.3.6.1.2.1.166.2.2,IF-CAP-STACK-MIB::ifCapStackCompliances,,,,,,
.1.3.6.1.2.1.166.2.2.1,IF-CAP-STACK-MIB::ifCapStackCompliance,,,,,,The compliance statement for SNMP entities, which provide information on the cross-connect capability of multi-layer (stacked) network interfaces, with flexible cross-connect between the sub-layers.
.1.3.6.1.2.1.167,EFM-CU-MIB::efmCuMIB,,,,,,The objects in this MIB module are used to manage the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004, which is now a part of IEEE Std. 802.3-2005. The following references are used throughout this MIB module: [802.3ah] refers to: IEEE Std 802.3ah-2004: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Amendment: Media Access Control Parameters, Physical Layers and Management Parameters for Subscriber Access Networks', 07 September 2004. Of particular interest are Clause 61, 'Physical Coding Sublayer (PCS) and common specifications, type 10PASS-TS and type 2BASE-TL', Clause 30, 'Management', Clause 45, 'Management Data Input/Output (MDIO) Interface', Annex 62A, 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 2BASE-TL'. [G.991.2] refers to: ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital Subscriber Line (SHDSL) transceivers', December 2003. [ANFP] refers to: NICC Document ND1602:2005/08: 'Specification of the Access Network Frequency Plan (ANFP) applicable to transmission systems used on the BT Access Network,' August 2005. The following normative documents are quoted by the DESCRIPTION clauses in this MIB module: [G.993.1] refers to: ITU-T Recommendation G.993.1: 'Very High speed Digital Subscriber Line transceivers', June 2004. [T1.424] refers to: ANSI T1.424-2004: 'Interface Between Networks and Customer Installation Very-high-bit-rate Digital Subscriber Lines (VDSL) Metallic Interface (DMT Based)', June 2004. [TS 101 270-1] refers to: ETSI TS 101 270-1: 'Transmission and Multiplexing (TM); Access transmission systems on metallic access cables; Very high speed Digital Subscriber Line (VDSL); Part 1: Functional requirements', October 2005. Naming Conventions: Atn - Attenuation CO - Central Office CPE - Customer Premises Equipment EFM - Ethernet in the First Mile EFMCu - EFM Copper MDIO - Management Data Input/Output Mgn - Margin PAF - PME Aggregation Function PBO - Power Back-Off PCS - Physical Coding Sublayer PMD - Physical Medium Dependent PME - Physical Medium Entity PSD - Power Spectral Density SNR - Signal to Noise Ratio TCPAM - Trellis Coded Pulse Amplitude Modulation Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5066; see the RFC itself for full legal notices.
.1.3.6.1.2.1.167.1,EFM-CU-MIB::efmCuObjects,,,,,,
.1.3.6.1.2.1.167.1.1,EFM-CU-MIB::efmCuPort,,,,,,
.1.3.6.1.2.1.167.1.1.0,EFM-CU-MIB::efmCuPortNotifications,,,,,,
.1.3.6.1.2.1.167.1.1.0.1,EFM-CU-MIB::efmCuLowRateCrossing,,,,,,This notification indicates that the EFMCu port's data rate has reached/dropped below or exceeded the low rate threshold, specified by efmCuThreshLowRate. This notification MAY be sent for the -O subtype ports (2BaseTL-O/10PassTS-O) while the port is Up, on the crossing event in both directions: from normal (rate is above the threshold) to low (rate equals the threshold or below it) and from low to normal. This notification is not applicable to the -R subtypes. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent simultaneous LinkUp/LinkDown and efmCuLowRateCrossing notifications to be sent. The adaptive nature of the EFMCu technology allows the port to adapt itself to the changes in the copper environment, e.g., an impulse noise, alien crosstalk, or a micro-interruption may temporarily drop one or more PMEs in the aggregation group, causing a rate degradation of the aggregated EFMCu link. The dropped PMEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide required target SNR margin. Generation of this notification is controlled by the efmCuLowRateCrossingEnable object.
.1.3.6.1.2.1.167.1.1.1,EFM-CU-MIB::efmCuPortConfTable,,not-accessible,,current,,Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) Ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1,EFM-CU-MIB::efmCuPortConfEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu Port Configuration table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex.
.1.3.6.1.2.1.167.1.1.1.1.1,EFM-CU-MIB::efmCuPAFAdminState,INTEGER,read-write,,current,enabled(1):disabled(2),Administrative (desired) state of the PAF of the EFMCu port (PCS). When 'disabled', PME aggregation will not be performed by the PCS. No more than a single PME can be assigned to this PCS in this case. When 'enabled', PAF will be performed by the PCS when the link is Up, even on a single attached PME, if PAF is supported. PCS ports incapable of supporting PAF SHALL return a value of 'disabled'. Attempts to 'enable' such ports SHALL be rejected. A PAF 'enabled' port with multiple PMEs assigned cannot be 'disabled'. Attempts to 'disable' such port SHALL be rejected, until at most one PME is left assigned. Changing PAFAdminState is a traffic-disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be rejected if the link is Up or Initializing. This object maps to the Clause 30 attribute aPAFAdminState. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the PAF enable bit in the 10P/2B PCS control register. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1.2,EFM-CU-MIB::efmCuPAFDiscoveryCode,OCTET,read-write,,current,,PAF Discovery Code of the EFMCu port (PCS). A unique 6-octet code used by the Discovery function, when PAF is supported. PCS ports incapable of supporting PAF SHALL return a zero-length octet string on an attempt to read this object. An attempt to write to this object SHALL be rejected for such ports. This object MUST be instantiated for the -O subtype PCS before writing operations on the efmCuPAFRemoteDiscoveryCode (Set_if_Clear and Clear_if_Same) are performed by PMEs associated with the PCS. The initial value of this object for -R subtype ports after reset is all zeroes. For -R subtype ports, the value of this object cannot be changed directly. This value may be changed as a result of writing operation on the efmCuPAFRemoteDiscoveryCode object of remote PME of -O subtype, connected to one of the local PMEs associated with the PCS. Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. The PAF Discovery Code maps to the local Discovery code variable in PAF (note that it does not have a corresponding Clause 45 register).
.1.3.6.1.2.1.167.1.1.1.1.3,EFM-CU-MIB::efmCuAdminProfile,OCTET,read-write,,current,,Desired configuration profile(s), common for all PMEs in the EFMCu port. This object is a list of pointers to entries in either efmCuPme2BProfileTable or efmCuPme10PProfileTable, depending on the current operating SubType of the EFMCu port as indicated by efmCuPortSide. The value of this object is a list of up to 6 indices of profiles. If this list consists of a single profile index, then all PMEs assigned to this EFMCu port SHALL be configured according to the profile referenced by that index, unless it is overwritten by a corresponding non-zero efmCuPmeAdminProfile instance, which takes precedence over efmCuAdminProfile. A list consisting of more than one index allows each PME in the port to be configured according to any profile specified in the list. By default, this object has a value of 0x01, referencing the 1st entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. This object is writable and readable for the -O subtype (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for the -R subtype (2BaseTL-R or 10PassTS-R) ports -- a zero-length octet string SHALL be returned on an attempt to read this object and an attempt to change this object MUST be rejected in this case. Note that the current operational profile value is available via the efmCuPmeOperProfile object. Any modification of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected, if the link is Up or Initializing. Attempts to set this object to a list with a member value that is not the value of the index for an active entry in the corresponding profile table MUST be rejected. This object maps to the Clause 30 attribute aProfileSelect. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1.4,EFM-CU-MIB::efmCuTargetDataRate,Unsigned32,read-write,,current,,Desired EFMCu port 'net' (as seen across MII) Data Rate in Kbps, to be achieved during initialization, under spectral restrictions placed on each PME via efmCuAdminProfile or efmCuPmeAdminProfile, with the desired SNR margin specified by efmCuTargetSnrMgn. In case of PAF, this object represents a sum of individual PME data rates, modified to compensate for fragmentation and 64/65-octet encapsulation overhead (e.g., target data rate of 10 Mbps SHALL allow lossless transmission of a full-duplex 10 Mbps Ethernet frame stream with minimal inter-frame gap). The value is limited above by 100 Mbps as this is the max burst rate across MII for EFMCu ports. The value between 1 and 100000 indicates that the total data rate (ifSpeed) of the EFMCu port after initialization SHALL be equal to the target data rate or less, if the target data rate cannot be achieved under spectral restrictions specified by efmCuAdminProfile/efmCuPmeAdminProfile and with the desired SNR margin. In case the copper environment allows a higher total data rate to be achieved than that specified by the target, the excess capability SHALL be either converted to additional SNR margin or reclaimed by minimizing transmit power as controlled by efmCuAdaptiveSpectra. The value of 999999 means that the target data rate is not fixed and SHALL be set to the maximum attainable rate during initialization (Best Effort), under specified spectral restrictions and with the desired SNR margin. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of the Target Data Rate MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. Note that the current Data Rate of the EFMCu port is represented by the ifSpeed object of IF-MIB. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1.5,EFM-CU-MIB::efmCuTargetSnrMgn,Unsigned32,read-write,,current,,Desired EFMCu port SNR margin to be achieved on all PMEs assigned to the port, during initialization. (The SNR margin is the difference between the desired SNR and the actual SNR). Note that 802.3ah recommends using a default target SNR margin of 5 dB for 2BASE-TL ports and 6 dB for 10PASS-TS ports in order to achieve a mean Bit Error Rate (BER) of 10^-7 at the PMA service interface. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of the target SNR margin MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. Note that the current SNR margin of the PMEs comprising the EFMCu port is represented by efmCuPmeSnrMgn. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1.6,EFM-CU-MIB::efmCuAdaptiveSpectra,INTEGER,read-write,,current,true(1):false(2),Indicates how to utilize excess capacity when the copper environment allows a higher total data rate to be achieved than that specified by the efmCuTargetDataRate. A value of true(1) indicates that the excess capability SHALL be reclaimed by minimizing transmit power, e.g., using higher constellations and Power Back-Off, in order to reduce interference to other copper pairs in the binder and the adverse impact to link/system performance. A value of false(2) indicates that the excess capability SHALL be converted to additional SNR margin and spread evenly across all active PMEs assigned to the (PCS) port, to increase link robustness. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1.7,EFM-CU-MIB::efmCuThreshLowRate,Unsigned32,read-write,,current,,This object configures the EFMCu port low-rate crossing alarm threshold. When the current value of ifSpeed for this port reaches/drops below or exceeds this threshold, an efmCuLowRateCrossing notification MAY be generated if enabled by efmCuLowRateCrossingEnable. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.1.1.8,EFM-CU-MIB::efmCuLowRateCrossingEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether efmCuLowRateCrossing notifications should be generated for this interface. A value of true(1) indicates that efmCuLowRateCrossing notification is enabled. A value of false(2) indicates that the notification is disabled. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.1.2,EFM-CU-MIB::efmCuPortCapabilityTable,,not-accessible,,current,,Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) Ports. Entries in this table MUST be maintained in a persistent manner
.1.3.6.1.2.1.167.1.1.2.1,EFM-CU-MIB::efmCuPortCapabilityEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu Port Capability table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex.
.1.3.6.1.2.1.167.1.1.2.1.1,EFM-CU-MIB::efmCuPAFSupported,INTEGER,read-only,,current,true(1):false(2),PME Aggregation Function (PAF) capability of the EFMCu port (PCS). This object has a value of true(1) when the PCS can perform PME aggregation on the available PMEs. Ports incapable of PAF SHALL return a value of false(2). This object maps to the Clause 30 attribute aPAFSupported. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the PAF available bit in the 10P/2B capability register.
.1.3.6.1.2.1.167.1.1.2.1.2,EFM-CU-MIB::efmCuPeerPAFSupported,INTEGER,read-only,,current,unknown(0):true(1):false(2),PME Aggregation Function (PAF) capability of the EFMCu port (PCS) link partner. This object has a value of true(1) when the remote PCS can perform PME aggregation on its available PMEs. Ports whose peers are incapable of PAF SHALL return a value of false(2). Ports whose peers cannot be reached because of the link state SHALL return a value of unknown(0). This object maps to the Clause 30 attribute aRemotePAFSupported. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the Remote PAF supported bit in the 10P/2B capability register.
.1.3.6.1.2.1.167.1.1.2.1.3,EFM-CU-MIB::efmCuPAFCapacity,Unsigned32,read-only,,current,,Number of PMEs that can be aggregated by the local PAF. The number of PMEs currently assigned to a particular EFMCu port (efmCuNumPMEs) is never greater than efmCuPAFCapacity. This object maps to the Clause 30 attribute aLocalPAFCapacity.
.1.3.6.1.2.1.167.1.1.2.1.4,EFM-CU-MIB::efmCuPeerPAFCapacity,Unsigned32,read-only,,current,,Number of PMEs that can be aggregated by the PAF of the peer PHY (PCS port). A value of 0 is returned when peer PAF capacity is unknown (peer cannot be reached). This object maps to the Clause 30 attribute aRemotePAFCapacity.
.1.3.6.1.2.1.167.1.1.3,EFM-CU-MIB::efmCuPortStatusTable,,not-accessible,,current,,This table provides overall status information of EFMCu 2BASE-TL/10PASS-TS ports, complementing the generic status information from the ifTable of IF-MIB and ifMauTable of MAU-MIB. Additional status information about connected PMEs is available from the efmCuPmeStatusTable. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.167.1.1.3.1,EFM-CU-MIB::efmCuPortStatusEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu Port Status table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex.
.1.3.6.1.2.1.167.1.1.3.1.1,EFM-CU-MIB::efmCuFltStatus,BITS,read-only,,current,noPeer(0):peerPowerLoss(1):pmeSubTypeMismatch(2):lowRate(3),EFMCu (PCS) port Fault Status. This is a bitmap of possible conditions. The various bit positions are: noPeer - the peer PHY cannot be reached (e.g., no PMEs attached, all PMEs are Down, etc.). More info is available in efmCuPmeFltStatus. peerPowerLoss - the peer PHY has indicated impending unit failure due to loss of local power ('Dying Gasp'). pmeSubTypeMismatch - local PMEs in the aggregation group are not of the same subtype, e.g., some PMEs in the local device are -O while others are -R subtype. lowRate - ifSpeed of the port reached or dropped below efmCuThreshLowRate. This object is intended to supplement the ifOperStatus object in IF-MIB and ifMauMediaAvailable in MAU-MIB. Additional information is available via the efmCuPmeFltStatus object for each PME in the aggregation group (single PME if PAF is disabled).
.1.3.6.1.2.1.167.1.1.3.1.2,EFM-CU-MIB::efmCuPortSide,INTEGER,read-only,,current,subscriber(1):office(2):unknown(3),EFM port mode of operation (subtype). The value of 'subscriber' indicates that the port is designated as '-R' subtype (all PMEs assigned to this port are of subtype '-R'). The value of the 'office' indicates that the port is designated as '-O' subtype (all PMEs assigned to this port are of subtype '-O'). The value of 'unknown' indicates that the port has no assigned PMEs yet or that the assigned PMEs are not of the same side (subTypePMEMismatch). This object partially maps to the Clause 30 attribute aPhyEnd.
.1.3.6.1.2.1.167.1.1.3.1.3,EFM-CU-MIB::efmCuNumPMEs,Unsigned32,read-only,,current,,The number of PMEs that is currently aggregated by the local PAF (assigned to the EFMCu port using the ifStackTable). This number is never greater than efmCuPAFCapacity. This object SHALL be automatically incremented or decremented when a PME is added or deleted to/from the EFMCu port using the ifStackTable.
.1.3.6.1.2.1.167.1.1.3.1.4,EFM-CU-MIB::efmCuPAFInErrors,Counter32,read-only,,current,,The number of fragments that have been received across the gamma interface with RxErr asserted and discarded. This read-only counter is inactive (not incremented) when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF RX error register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.5,EFM-CU-MIB::efmCuPAFInSmallFragments,Counter32,read-only,,current,,The number of fragments smaller than minFragmentSize (64 bytes) that have been received across the gamma interface and discarded. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF small fragments register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.6,EFM-CU-MIB::efmCuPAFInLargeFragments,Counter32,read-only,,current,,The number of fragments larger than maxFragmentSize (512 bytes) that have been received across the gamma interface and discarded. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF large fragments register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.7,EFM-CU-MIB::efmCuPAFInBadFragments,Counter32,read-only,,current,,The number of fragments that do not fit into the sequence expected by the frame assembly function and that have been received across the gamma interface and discarded (the frame buffer is flushed to the next valid frame start). This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF bad fragments register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.8,EFM-CU-MIB::efmCuPAFInLostFragments,Counter32,read-only,,current,,The number of gaps in the sequence of fragments that have been received across the gamma interface (the frame buffer is flushed to the next valid frame start, when fragment/fragments expected by the frame assembly function is/are not received). This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost fragment register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.9,EFM-CU-MIB::efmCuPAFInLostStarts,Counter32,read-only,,current,,The number of missing StartOfPacket indicators expected by the frame assembly function. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost start of fragment register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.10,EFM-CU-MIB::efmCuPAFInLostEnds,Counter32,read-only,,current,,The number of missing EndOfPacket indicators expected by the frame assembly function. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost start of fragment register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.1.3.1.11,EFM-CU-MIB::efmCuPAFInOverflows,Counter32,read-only,,current,,The number of fragments, received across the gamma interface and discarded, which would have caused the frame assembly buffer to overflow. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF overflow register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.2,EFM-CU-MIB::efmCuPme,,,,,,
.1.3.6.1.2.1.167.1.2.0,EFM-CU-MIB::efmCuPmeNotifications,,,,,,
.1.3.6.1.2.1.167.1.2.0.1,EFM-CU-MIB::efmCuPmeLineAtnCrossing,,,,,,This notification indicates that the loop attenuation threshold (as per the efmCuPmeThreshLineAtn value) has been reached/exceeded for the 2BASE-TL/10PASS-TS PME. This notification MAY be sent on the crossing event in both directions: from normal to exceeded and from exceeded to normal. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent intermittent notifications from being sent. Generation of this notification is controlled by the efmCuPmeLineAtnCrossingEnable object.
.1.3.6.1.2.1.167.1.2.0.2,EFM-CU-MIB::efmCuPmeSnrMgnCrossing,,,,,,This notification indicates that the SNR margin threshold (as per the efmCuPmeThreshSnrMgn value) has been reached/exceeded for the 2BASE-TL/10PASS-TS PME. This notification MAY be sent on the crossing event in both directions: from normal to exceeded and from exceeded to normal. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent intermittent notifications from being sent. Generation of this notification is controlled by the efmCuPmeSnrMgnCrossingEnable object.
.1.3.6.1.2.1.167.1.2.0.3,EFM-CU-MIB::efmCuPmeDeviceFault,,,,,,This notification indicates that a fault in the PME has been detected by a vendor-specific diagnostic or a self-test. Generation of this notification is controlled by the efmCuPmeDeviceFaultEnable object.
.1.3.6.1.2.1.167.1.2.0.4,EFM-CU-MIB::efmCuPmeConfigInitFailure,,,,,,This notification indicates that PME initialization has failed, due to inability of the PME link to achieve the requested configuration profile. Generation of this notification is controlled by the efmCuPmeConfigInitFailEnable object.
.1.3.6.1.2.1.167.1.2.0.5,EFM-CU-MIB::efmCuPmeProtocolInitFailure,,,,,,This notification indicates that the peer PME was using an incompatible protocol during initialization. Generation of this notification is controlled by the efmCuPmeProtocolInitFailEnable object.
.1.3.6.1.2.1.167.1.2.1,EFM-CU-MIB::efmCuPmeConfTable,,not-accessible,,current,,Table for Configuration of common aspects for EFMCu 2BASE-TL/10PASS-TS PME ports (modems). Configuration of aspects specific to 2BASE-TL or 10PASS-TS PME types is represented in efmCuPme2BConfTable and efmCuPme10PConfTable, respectively. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.1.1,EFM-CU-MIB::efmCuPmeConfEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu PME Configuration table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled.
.1.3.6.1.2.1.167.1.2.1.1.1,EFM-CU-MIB::efmCuPmeAdminSubType,INTEGER,read-write,,current,ieee2BaseTLO(1):ieee2BaseTLR(2):ieee10PassTSO(3):ieee10PassTSR(4):ieee2BaseTLor10PassTSR(5):ieee2BaseTLor10PassTSO(6):ieee10PassTSor2BaseTLO(7),Administrative (desired) subtype of the PME. Possible values are: ieee2BaseTLO - PME SHALL operate as 2BaseTL-O ieee2BaseTLR - PME SHALL operate as 2BaseTL-R ieee10PassTSO - PME SHALL operate as 10PassTS-O ieee10PassTSR - PME SHALL operate as 10PassTS-R ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or 10PassTS-R. The actual value will be set by the -O link partner during initialization (handshake). ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O (preferred) or 10PassTS-O. The actual value will be set during initialization depending on the -R link partner capability (i.e., if -R is incapable of the preferred 2BaseTL mode, 10PassTS will be used). ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O (preferred) or 2BaseTL-O. The actual value will be set during initialization depending on the -R link partner capability (i.e., if -R is incapable of the preferred 10PassTS mode, 2BaseTL will be used). Changing efmCuPmeAdminSubType is a traffic-disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be rejected if the link is Up or Initializing. Attempts to change this object to an unsupported subtype (see efmCuPmeSubTypesSupported) SHALL be rejected. The current operational subtype is indicated by the efmCuPmeOperSubType variable. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object combines values of the Port subtype select bits and the PMA/PMD type selection bits in the 10P/2B PMA/PMD control register.
.1.3.6.1.2.1.167.1.2.1.1.2,EFM-CU-MIB::efmCuPmeAdminProfile,Unsigned32,read-write,,current,,Desired PME configuration profile. This object is a pointer to an entry in either the efmCuPme2BProfileTable or the efmCuPme10PProfileTable, depending on the current operating SubType of the PME. The value of this object is the index of the referenced profile. The value of zero (default) indicates that the PME is configured via the efmCuAdminProfile object for the PCS port to which this PME is assigned. That is, the profile referenced by efmCuPmeAdminProfile takes precedence over the profile(s) referenced by efmCuAdminProfile. This object is writable and readable for the CO subtype PMEs (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE subtype (2BaseTL-R or 10PassTS-R) -- a zero value SHALL be returned on an attempt to read this object and any attempt to change this object MUST be rejected in this case. Note that the current operational profile value is available via efmCuPmeOperProfile object. Any modification of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected, if the link is Up or Initializing. Attempts to set this object to a value that is not the value of the index for an active entry in the corresponding profile table MUST be rejected. This object maps to the Clause 30 attribute aProfileSelect. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.1.1.3,EFM-CU-MIB::efmCuPAFRemoteDiscoveryCode,OCTET,read-write,,current,,PAF Remote Discovery Code of the PME port at the CO. The 6-octet Discovery Code of the peer PCS connected via the PME. Reading this object results in a Discovery Get operation. Setting this object to all zeroes results in a Discovery Clear_if_Same operation (the value of efmCuPAFDiscoveryCode at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of the local PCS associated with the PME for the operation to succeed). Writing a non-zero value to this object results in a Discovery Set_if_Clear operation. A zero-length octet string SHALL be returned on an attempt to read this object when PAF aggregation is not enabled. This object is irrelevant in CPE port (-R) subtypes: in this case, a zero-length octet string SHALL be returned on an attempt to read this object; writing to this object SHALL be rejected. Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object is a function of 10P/2B aggregation discovery control register, Discovery operation result bits in 10P/2B aggregation and discovery status register and 10P/2B aggregation discovery code register.
.1.3.6.1.2.1.167.1.2.1.1.4,EFM-CU-MIB::efmCuPmeThreshLineAtn,Integer32,read-write,,current,,Desired Line Attenuation threshold for the 2B/10P PME. This object configures the line attenuation alarm threshold. When the current value of Line Attenuation reaches or exceeds this threshold, an efmCuPmeLineAtnCrossing notification MAY be generated, if enabled by efmCuPmeLineAtnCrossingEnable. This object is writable for the CO subtype PMEs (-O). It is read-only for the CPE subtype (-R). Changing of the Line Attenuation threshold MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the loop attenuation threshold bits in the 2B PMD line quality thresholds register.
.1.3.6.1.2.1.167.1.2.1.1.5,EFM-CU-MIB::efmCuPmeThreshSnrMgn,Integer32,read-write,,current,,Desired SNR margin threshold for the 2B/10P PME. This object configures the SNR margin alarm threshold. When the current value of SNR margin reaches or exceeds this threshold, an efmCuPmeSnrMgnCrossing notification MAY be generated, if enabled by efmCuPmeSnrMgnCrossingEnable. This object is writable for the CO subtype PMEs (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype (2BaseTL-R/10PassTS-R). Changing of the SNR margin threshold MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the SNR margin threshold bits in the 2B PMD line quality thresholds register.
.1.3.6.1.2.1.167.1.2.1.1.6,EFM-CU-MIB::efmCuPmeLineAtnCrossingEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether efmCuPmeLineAtnCrossing notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeLineAtnCrossing notification is enabled. A value of false(2) indicates that the notification is disabled.
.1.3.6.1.2.1.167.1.2.1.1.7,EFM-CU-MIB::efmCuPmeSnrMgnCrossingEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether efmCuPmeSnrMgnCrossing notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeSnrMgnCrossing notification is enabled. A value of false(2) indicates that the notification is disabled.
.1.3.6.1.2.1.167.1.2.1.1.8,EFM-CU-MIB::efmCuPmeDeviceFaultEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether efmCuPmeDeviceFault notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeDeviceFault notification is enabled. A value of false(2) indicates that the notification is disabled.
.1.3.6.1.2.1.167.1.2.1.1.9,EFM-CU-MIB::efmCuPmeConfigInitFailEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether efmCuPmeConfigInitFailure notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeConfigInitFailure notification is enabled. A value of false(2) indicates that the notification is disabled.
.1.3.6.1.2.1.167.1.2.1.1.10,EFM-CU-MIB::efmCuPmeProtocolInitFailEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether efmCuPmeProtocolInitFailure notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeProtocolInitFailure notification is enabled. A value of false(2) indicates that the notification is disabled.
.1.3.6.1.2.1.167.1.2.2,EFM-CU-MIB::efmCuPmeCapabilityTable,,not-accessible,,current,,Table for the configuration of common aspects for EFMCu 2BASE-TL/10PASS-TS PME ports (modems). The configuration of aspects specific to 2BASE-TL or 10PASS-TS PME types is represented in the efmCuPme2BConfTable and the efmCuPme10PConfTable, respectively. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.2.1,EFM-CU-MIB::efmCuPmeCapabilityEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu PME Capability table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled.
.1.3.6.1.2.1.167.1.2.2.1.1,EFM-CU-MIB::efmCuPmeSubTypesSupported,BITS,read-only,,current,ieee2BaseTLO(0):ieee2BaseTLR(1):ieee10PassTSO(2):ieee10PassTSR(3),PME supported subtypes. This is a bitmap of possible subtypes. The various bit positions are: ieee2BaseTLO - PME is capable of operating as 2BaseTL-O ieee2BaseTLR - PME is capable of operating as 2BaseTL-R ieee10PassTSO - PME is capable of operating as 10PassTS-O ieee10PassTSR - PME is capable of operating as 10PassTS-R The desired mode of operation is determined by efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the current operating mode. If a Clause 45 MDIO Interface to the PCS is present, then this object combines the 10PASS-TS capable and 2BASE-TL capable bits in the 10P/2B PMA/PMD speed ability register and the CO supported and CPE supported bits in the 10P/2B PMA/PMD status register.
.1.3.6.1.2.1.167.1.2.3,EFM-CU-MIB::efmCuPmeStatusTable,,not-accessible,,current,,This table provides common status information of EFMCu 2BASE-TL/10PASS-TS PME ports. Status information specific to 10PASS-TS PME is represented in efmCuPme10PStatusTable. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.167.1.2.3.1,EFM-CU-MIB::efmCuPmeStatusEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu PME Status table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled.
.1.3.6.1.2.1.167.1.2.3.1.1,EFM-CU-MIB::efmCuPmeOperStatus,INTEGER,read-only,,current,up(1):downNotReady(2):downReady(3):init(4),Current PME link Operational Status. Possible values are: up(1) - The link is Up and ready to pass 64/65-octet encoded frames or fragments. downNotReady(2) - The link is Down and the PME does not detect Handshake tones from its peer. This value may indicate a possible problem with the peer PME. downReady(3) - The link is Down and the PME detects Handshake tones from its peer. init(4) - The link is Initializing, as a result of ifAdminStatus being set to 'up' for a particular PME or a PCS to which the PME is connected. This object is intended to supplement the Down(2) state of ifOperStatus. This object partially maps to the Clause 30 attribute aPMEStatus. If a Clause 45 MDIO Interface to the PME is present, then this object partially maps to PMA/PMD link status bits in 10P/2B PMA/PMD status register.
.1.3.6.1.2.1.167.1.2.3.1.2,EFM-CU-MIB::efmCuPmeFltStatus,BITS,read-only,,current,lossOfFraming(0):snrMgnDefect(1):lineAtnDefect(2):deviceFault(3):configInitFailure(4):protocolInitFailure(5),Current/Last PME link Fault Status. This is a bitmap of possible conditions. The various bit positions are: lossOfFraming - Loss of Framing for 10P or Loss of Sync word for 2B PMD or Loss of 64/65-octet framing. snrMgnDefect - SNR margin dropped below the threshold. lineAtnDefect - Line Attenuation exceeds the threshold. deviceFault - Indicates a vendor-dependent diagnostic or self-test fault has been detected. configInitFailure - Configuration initialization failure, due to inability of the PME link to support the configuration profile, requested during initialization. protocolInitFailure - Protocol initialization failure, due to an incompatible protocol used by the peer PME during init (that could happen if a peer PMD is a regular G.SDHSL/VDSL modem instead of a 2BASE-TL/10PASS-TS PME). This object is intended to supplement ifOperStatus in IF-MIB. This object holds information about the last fault. efmCuPmeFltStatus is cleared by the device restart. In addition, lossOfFraming, configInitFailure, and protocolInitFailure are cleared by PME init; deviceFault is cleared by successful diagnostics/test; snrMgnDefect and lineAtnDefect are cleared by SNR margin and Line attenuation, respectively, returning to norm and by PME init. This object partially maps to the Clause 30 attribute aPMEStatus. If a Clause 45 MDIO Interface to the PME is present, then this object consolidates information from various PMA/PMD registers, namely: Fault bit in PMA/PMD status 1 register, 10P/2B PMA/PMD link loss register, 10P outgoing indicator bits status register, 10P incoming indicator bits status register, 2B state defects register.
.1.3.6.1.2.1.167.1.2.3.1.3,EFM-CU-MIB::efmCuPmeOperSubType,INTEGER,read-only,,current,ieee2BaseTLO(1):ieee2BaseTLR(2):ieee10PassTSO(3):ieee10PassTSR(4),Current operational subtype of the PME. Possible values are: ieee2BaseTLO - PME operates as 2BaseTL-O ieee2BaseTLR - PME operates as 2BaseTL-R ieee10PassTSO - PME operates as 10PassTS-O ieee10PassTSR - PME operates as 10PassTS-R The desired operational subtype of the PME can be configured via the efmCuPmeAdminSubType variable. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object combines values of the Port subtype select bits, the PMA/PMD type selection bits in the 10P/2B PMA/PMD control register, and the PMA/PMD link status bits in the 10P/2B PMA/PMD status register.
.1.3.6.1.2.1.167.1.2.3.1.4,EFM-CU-MIB::efmCuPmeOperProfile,Unsigned32,read-only,,current,,PME current operating profile. This object is a pointer to an entry in either the efmCuPme2BProfileTable or the efmCuPme10PProfileTable, depending on the current operating SubType of the PME as indicated by efmCuPmeOperSubType. Note that a profile entry to which efmCuPmeOperProfile is pointing can be created automatically to reflect achieved parameters in adaptive (not fixed) initialization, i.e., values of efmCuPmeOperProfile and efmCuAdminProfile or efmCuPmeAdminProfile may differ. The value of zero indicates that the PME is Down or Initializing. This object partially maps to the aOperatingProfile attribute in Clause 30.
.1.3.6.1.2.1.167.1.2.3.1.5,EFM-CU-MIB::efmCuPmeSnrMgn,Integer32,read-only,,current,,The current Signal to Noise Ratio (SNR) margin with respect to the received signal as perceived by the local PME. The value of 65535 is returned when the PME is Down or Initializing. This object maps to the aPMESNRMgn attribute in Clause 30. If a Clause 45 MDIO Interface is present, then this object maps to the 10P/2B RX SNR margin register.
.1.3.6.1.2.1.167.1.2.3.1.6,EFM-CU-MIB::efmCuPmePeerSnrMgn,Integer32,read-only,,current,,The current SNR margin in dB with respect to the received signal, as perceived by the remote (link partner) PME. The value of 65535 is returned when the PME is Down or Initializing. This object is irrelevant for the -R PME subtypes. The value of 65535 SHALL be returned in this case. If a Clause 45 MDIO Interface is present, then this object maps to the 10P/2B link partner RX SNR margin register.
.1.3.6.1.2.1.167.1.2.3.1.7,EFM-CU-MIB::efmCuPmeLineAtn,Integer32,read-only,,current,,The current Line Attenuation in dB as perceived by the local PME. The value of 65535 is returned when the PME is Down or Initializing. If a Clause 45 MDIO Interface is present, then this object maps to the Line Attenuation register.
.1.3.6.1.2.1.167.1.2.3.1.8,EFM-CU-MIB::efmCuPmePeerLineAtn,Integer32,read-only,,current,,The current Line Attenuation in dB as perceived by the remote (link partner) PME. The value of 65535 is returned when the PME is Down or Initializing. This object is irrelevant for the -R PME subtypes. The value of 65535 SHALL be returned in this case. If a Clause 45 MDIO Interface is present, then this object maps to the 20P/2B link partner Line Attenuation register.
.1.3.6.1.2.1.167.1.2.3.1.9,EFM-CU-MIB::efmCuPmeEquivalentLength,Unsigned32,read-only,,current,,An estimate of the equivalent loop's physical length in meters, as perceived by the PME after the link is established. An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a perfect square root attenuation characteristic, without any bridged taps. The value of 65535 is returned if the link is Down or Initializing or the PME is unable to estimate the equivalent length. For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is present, then this object maps to the 10P Electrical Length register.
.1.3.6.1.2.1.167.1.2.3.1.10,EFM-CU-MIB::efmCuPmeTCCodingErrors,Counter32,read-only,,current,,The number of 64/65-octet encapsulation errors. This counter is incremented for each 64/65-octet encapsulation error detected by the 64/65-octet receive function. This object maps to aTCCodingViolations attribute in Clause 30. If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC coding violations register (see 45.2.6.12). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.2.3.1.11,EFM-CU-MIB::efmCuPmeTCCrcErrors,Counter32,read-only,,current,,The number of TC-CRC errors. This counter is incremented for each TC-CRC error detected by the 64/65-octet receive function (see 61.3.3.3 and Figure 61-19). This object maps to aTCCRCErrors attribute in Clause 30. If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC CRC error register (see 45.2.6.11). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.2.5,EFM-CU-MIB::efmCuPme2B,,,,,,
.1.3.6.1.2.1.167.1.2.5.2,EFM-CU-MIB::efmCuPme2BProfileTable,,not-accessible,,current,,This table supports definitions of administrative and operating profiles for 2BASE-TL PMEs. The first 14 entries in this table SHALL always be defined as follows (see 802.3ah Annex 63A): -------+-------+-------+-----+------+-------------+----------- Profile MinRate MaxRate Power Region Constellation Comment index (Kbps) (Kbps) (dBm) -------+-------+-------+-----+------+-------------+----------- 1 5696 5696 13.5 1 32-TCPAM default 2 3072 3072 13.5 1 32-TCPAM 3 2048 2048 13.5 1 16-TCPAM 4 1024 1024 13.5 1 16-TCPAM 5 704 704 13.5 1 16-TCPAM 6 512 512 13.5 1 16-TCPAM 7 5696 5696 14.5 2 32-TCPAM 8 3072 3072 14.5 2 32-TCPAM 9 2048 2048 14.5 2 16-TCPAM 10 1024 1024 13.5 2 16-TCPAM 11 704 704 13.5 2 16-TCPAM 12 512 512 13.5 2 16-TCPAM 13 192 5696 0 1 0 best effort 14 192 5696 0 2 0 best effort -------+-------+-------+-----+------+-------------+----------- These default entries SHALL be created during agent initialization and MUST NOT be deleted. Entries following the first 14 can be dynamically created and deleted to provide custom administrative (configuration) profiles and automatic operating profiles. This table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.5.2.1,EFM-CU-MIB::efmCuPme2BProfileEntry,,not-accessible,efmCuPme2BProfileIndex,current,,Each entry corresponds to a single 2BASE-TL PME profile. Each profile contains a set of parameters, used either for configuration or representation of a 2BASE-TL PME. In case a particular profile is referenced via the efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile is zero), it represents the desired parameters for the 2BaseTL-O PME initialization. If a profile is referenced via an efmCuPmeOperProfile object, it represents the current operating parameters of an operational PME. Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BProfileRowStatus. If an active entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST NOT be removed.
.1.3.6.1.2.1.167.1.2.5.2.1.1,EFM-CU-MIB::efmCuPme2BProfileIndex,Unsigned32,not-accessible,,current,,2BASE-TL PME profile index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile objects.
.1.3.6.1.2.1.167.1.2.5.2.1.2,EFM-CU-MIB::efmCuPme2BProfileDescr,OCTET,read-create,,current,,A textual string containing information about a 2BASE-TL PME profile. The string may include information about the data rate and spectral limitations of this particular profile.
.1.3.6.1.2.1.167.1.2.5.2.1.3,EFM-CU-MIB::efmCuPme2BRegion,INTEGER,read-create,,current,region1(1):region2(2),Regional settings for a 2BASE-TL PME, as specified in the relevant Regional Annex of [G.991.2]. Regional settings specify the Power Spectral Density (PSD) mask and the Power Back-Off (PBO) values, and place limitations on the max allowed data rate, power, and constellation. Possible values for this object are: region1 - Annexes A and F (e.g., North America) region2 - Annexes B and G (e.g., Europe) Annex A/B specify regional settings for data rates 192-2304 Kbps using 16-TCPAM encoding. Annex F/G specify regional settings for rates 2320-3840 Kbps using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM encoding. If a Clause 45 MDIO Interface to the PME is present, then this object partially maps to the Region bits in the 2B general parameter register.
.1.3.6.1.2.1.167.1.2.5.2.1.4,EFM-CU-MIB::efmCuPme2BsMode,Unsigned32,read-create,,current,,Desired custom Spectral Mode for a 2BASE-TL PME. This object is a pointer to an entry in efmCuPme2BsModeTable and a block of entries in efmCuPme2BRateReachTable, which together define (country-specific) reach-dependent rate limitations in addition to those defined by efmCuPme2BRegion. The value of this object is the index of the referenced spectral mode. The value of zero (default) indicates that no specific spectral mode is applicable. Attempts to set this object to a value that is not the value of the index for an active entry in the corresponding spectral mode table MUST be rejected.
.1.3.6.1.2.1.167.1.2.5.2.1.5,EFM-CU-MIB::efmCuPme2BMinDataRate,Unsigned32,read-create,,current,,Minimum Data Rate for the 2BASE-TL PME. This object can take values of (n x 64)Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding. The data rate of the 2BASE-TL PME is considered 'fixed' when the value of this object equals that of efmCuPme2BMaxDataRate. If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative profile, the data rate is considered 'adaptive', and SHALL be set to the maximum attainable rate not exceeding efmCuPme2BMaxDataRate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. Note that the current operational data rate of the PME is represented by the ifSpeed object of IF-MIB. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Min Data Rate1 bits in the 2B PMD parameters register. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.5.2.1.6,EFM-CU-MIB::efmCuPme2BMaxDataRate,Unsigned32,read-create,,current,,Maximum Data Rate for the 2BASE-TL PME. This object can take values of (n x 64)Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding. The data rate of the 2BASE-TL PME is considered 'fixed' when the value of this object equals that of efmCuPme2BMinDataRate. If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative profile, the data rate is considered 'adaptive', and SHALL be set to the maximum attainable rate not exceeding efmCuPme2BMaxDataRate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. Note that the current operational data rate of the PME is represented by the ifSpeed object of IF-MIB. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Max Data Rate1 bits in the 2B PMD parameters register. This object MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.5.2.1.7,EFM-CU-MIB::efmCuPme2BPower,Unsigned32,read-create,,current,,Signal Transmit Power. Multiple of 0.5 dBm. The value of 0 in the administrative profile means that the signal transmit power is not fixed and SHALL be set to maximize the attainable rate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Power1 bits in the 2B PMD parameters register.
.1.3.6.1.2.1.167.1.2.5.2.1.8,EFM-CU-MIB::efmCuPme2BConstellation,INTEGER,read-create,,current,adaptive(0):tcpam16(1):tcpam32(2),TCPAM Constellation of the 2BASE-TL PME. The possible values are: adaptive(0) - either 16- or 32-TCPAM tcpam16(1) - 16-TCPAM tcpam32(2) - 32-TCPAM The value of adaptive(0) in the administrative profile means that the constellation is not fixed and SHALL be set to maximize the attainable rate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Constellation1 bits in the 2B general parameter register.
.1.3.6.1.2.1.167.1.2.5.2.1.9,EFM-CU-MIB::efmCuPme2BProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls the creation, modification, or deletion of the associated entry in the efmCuPme2BProfileTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
.1.3.6.1.2.1.167.1.2.5.3,EFM-CU-MIB::efmCuPme2BsModeTable,,not-accessible,,current,,This table, together with efmCu2BReachRateTable, supports definition of administrative custom spectral modes for 2BASE-TL PMEs, describing spectral limitations in addition to those specified by efmCuPme2BRegion. In some countries, spectral regulations (e.g., UK ANFP) limit the length of the loops for certain data rates. This table allows these country-specific limitations to be specified. Entries in this table referenced by the efmCuPme2BsMode MUST NOT be deleted until all the active references are removed. This table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.5.3.1,EFM-CU-MIB::efmCuPme2BsModeEntry,,not-accessible,efmCuPme2BsModeIndex,current,,Each entry specifies a spectral mode description and its index, which is used to reference corresponding entries in the efmCu2BReachRateTable. Entries may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BsModeRowStatus.
.1.3.6.1.2.1.167.1.2.5.3.1.1,EFM-CU-MIB::efmCuPme2BsModeIndex,Unsigned32,not-accessible,,current,,2BASE-TL PME Spectral Mode index. This object is the unique index associated with this spectral mode. Entries in this table are referenced via the efmCuPme2BsMode object.
.1.3.6.1.2.1.167.1.2.5.3.1.2,EFM-CU-MIB::efmCuPme2BsModeDescr,OCTET,read-create,,current,,A textual string containing information about a 2BASE-TL PME spectral mode. The string may include information about corresponding (country-specific) spectral regulations and rate/reach limitations of this particular spectral mode.
.1.3.6.1.2.1.167.1.2.5.3.1.3,EFM-CU-MIB::efmCuPme2BsModeRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls creation, modification, or deletion of the associated entry in efmCuPme2BsModeTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuPme2BsMode instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
.1.3.6.1.2.1.167.1.2.5.4,EFM-CU-MIB::efmCuPme2BReachRateTable,,not-accessible,,current,,This table supports the definition of administrative custom spectral modes for 2BASE-TL PMEs, providing spectral limitations in addition to those specified by efmCuPme2BRegion. The spectral regulations in some countries (e.g., UK ANFP) limit the length of the loops for certain data rates. This table allows these country-specific limitations to be specified. Below is an example of this table for [ANFP]: ----------+-------+------- Equivalent MaxRate MaxRate Length PAM16 PAM32 (m) (Kbps) (Kbps) ----------+-------+------- 975 2304 5696 1125 2304 5504 1275 2304 5120 1350 2304 4864 1425 2304 4544 1500 2304 4288 1575 2304 3968 1650 2304 3776 1725 2304 3520 1800 2304 3264 1875 2304 3072 1950 2048 2688 2100 1792 2368 2250 1536 0 2400 1408 0 2550 1280 0 2775 1152 0 2925 1152 0 3150 1088 0 3375 1024 0 ----------+-------+------- Entries in this table referenced by an efmCuPme2BsMode instance MUST NOT be deleted. This table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.5.4.1,EFM-CU-MIB::efmCuPme2BReachRateEntry,,not-accessible,efmCuPme2BsModeIndex:efmCuPme2BReachRateIndex,current,,Each entry specifies maximum 2BASE-TL PME data rates allowed for a certain equivalent loop length, when using 16-TCPAM or 32-TCPAM encoding. When a 2BASE-TL PME is initialized, its data rate MUST NOT exceed one of the following limitations: - the value of efmCuPme2BMaxDataRate - maximum data rate allowed by efmCuPme2BRegion and efmCuPme2BPower - maximum data rate for a given encoding specified in the efmCuPme2BsModeEntry, corresponding to the equivalent loop length, estimated by the PME It is RECOMMENDED that the efmCuPme2BEquivalentLength values are assigned in increasing order, starting from the minimum value. Entries may be created/deleted using the row creation/ deletion mechanism via efmCuPme2ReachRateRowStatus.
.1.3.6.1.2.1.167.1.2.5.4.1.1,EFM-CU-MIB::efmCuPme2BReachRateIndex,Unsigned32,not-accessible,,current,,2BASE-TL custom spectral mode Reach-Rate table index. This object is the unique index associated with each entry.
.1.3.6.1.2.1.167.1.2.5.4.1.2,EFM-CU-MIB::efmCuPme2BEquivalentLength,Unsigned32,read-create,,current,,Maximum allowed equivalent loop's physical length in meters for the specified data rates. An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a perfect square root attenuation characteristic, without any bridged taps.
.1.3.6.1.2.1.167.1.2.5.4.1.3,EFM-CU-MIB::efmCuPme2BMaxDataRatePam16,Unsigned32,read-create,,current,,Maximum data rate for a 2BASE-TL PME at the specified equivalent loop's length using TC-PAM16 encoding. The value of zero means that TC-PAM16 encoding should not be used at this distance.
.1.3.6.1.2.1.167.1.2.5.4.1.4,EFM-CU-MIB::efmCuPme2BMaxDataRatePam32,Unsigned32,read-create,,current,,Maximum data rate for a 2BASE-TL PME at the specified equivalent loop's length using TC-PAM32 encoding. The value of zero means that TC-PAM32 encoding should not be used at this distance.
.1.3.6.1.2.1.167.1.2.5.4.1.5,EFM-CU-MIB::efmCuPme2BReachRateRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls the creation, modification, or deletion of the associated entry in the efmCuPme2BReachRateTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuPme2BsMode instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
.1.3.6.1.2.1.167.1.2.6,EFM-CU-MIB::efmCuPme10P,,,,,,
.1.3.6.1.2.1.167.1.2.6.1,EFM-CU-MIB::efmCuPme10PProfileTable,,not-accessible,,current,,This table supports definitions of configuration profiles for 10PASS-TS PMEs. The first 22 entries in this table SHALL always be defined as follows (see 802.3ah Annex 62B.3, table 62B-1): -------+--------+----+---------+-----+-----+--------------- Profile Bandplan UPBO BandNotch DRate URate Comment Index PSDMask# p# p# p# p# -------+--------+----+---------+-----+-----+--------------- 1 1 3 2,6,10,11 20 20 default profile 2 13 5 0 20 20 3 1 1 0 20 20 4 16 0 0 100 100 5 16 0 0 70 50 6 6 0 0 50 10 7 17 0 0 30 30 8 8 0 0 30 5 9 4 0 0 25 25 10 4 0 0 15 15 11 23 0 0 10 10 12 23 0 0 5 5 13 16 0 2,5,9,11 100 100 14 16 0 2,5,9,11 70 50 15 6 0 2,6,10,11 50 10 16 17 0 2,5,9,11 30 30 17 8 0 2,6,10,11 30 5 18 4 0 2,6,10,11 25 25 19 4 0 2,6,10,11 15 15 20 23 0 2,5,9,11 10 10 21 23 0 2,5,9,11 5 5 22 30 0 0 200 50 -------+--------+----+---------+-----+-----+--------------- These default entries SHALL be created during agent initialization and MUST NOT be deleted. Entries following the first 22 can be dynamically created and deleted to provide custom administrative (configuration) profiles and automatic operating profiles. This table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.167.1.2.6.1.1,EFM-CU-MIB::efmCuPme10PProfileEntry,,not-accessible,efmCuPme10PProfileIndex,current,,Each entry corresponds to a single 10PASS-TS PME profile. Each profile contains a set of parameters, used either for configuration or representation of a 10PASS-TS PME. In case a particular profile is referenced via the efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile is zero), it represents the desired parameters for the 10PassTS-O PME initialization. If a profile is referenced via an efmCuPmeOperProfile object, it represents the current operating parameters of the PME. Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme10PProfileRowStatus. If an 'active' entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST NOT be removed.
.1.3.6.1.2.1.167.1.2.6.1.1.1,EFM-CU-MIB::efmCuPme10PProfileIndex,Unsigned32,not-accessible,,current,,10PASS-TS PME profile index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile.
.1.3.6.1.2.1.167.1.2.6.1.1.2,EFM-CU-MIB::efmCuPme10PProfileDescr,OCTET,read-create,,current,,A textual string containing information about a 10PASS-TS PME profile. The string may include information about data rate and spectral limitations of this particular profile.
.1.3.6.1.2.1.167.1.2.6.1.1.3,EFM-CU-MIB::efmCuPme10PBandplanPSDMskProfile,INTEGER,read-create,,current,profile1(1):profile2(2):profile3(3):profile4(4):profile5(5):profile6(6):profile7(7):profile8(8):profile9(9):profile10(10):profile11(11):profile12(12):profile13(13):profile14(14):profile15(15):profile16(16):profile17(17):profile18(18):profile19(19):profile20(20):profile21(21):profile22(22):profile23(23):profile24(24):profile25(25):profile26(26):profile27(27):profile28(28):profile29(29):profile30(30),The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified in 802.3ah Annex 62A, table 62A-1. Possible values are: --------------+------------------------+------------+-------- Profile Name PSD Mask Bands G.993.1 0/1/2/3/4/5 Bandplan --------------+------------------------+------------+-------- profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F profile28(28) G.993.1 F.1.2.2 x/D/U/D/U Annex F profile29(29) G.993.1 F.1.2.3 x/D/U/D/U Annex F profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A --------------+------------------------+------------+-------- 
.1.3.6.1.2.1.167.1.2.6.1.1.4,EFM-CU-MIB::efmCuPme10PUPBOReferenceProfile,INTEGER,read-create,,current,profile0(0):profile1(1):profile2(2):profile3(3):profile4(4):profile5(5):profile6(6):profile7(7):profile8(8):profile9(9),The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD Profile, as specified in 802.3 Annex 62A, table 62A-3. Possible values are: ------------+----------------------------- Profile Name Reference PSD ------------+----------------------------- profile0(0) no profile profile1(1) T1.424 Noise A M1 profile2(2) T1.424 Noise A M2 profile3(3) T1.424 Noise F M1 profile4(4) T1.424 Noise F M2 profile5(5) TS 101 270-1 Noise A&B profile6(6) TS 101 270-1 Noise C profile7(7) TS 101 270-1 Noise D profile8(8) TS 101 270-1 Noise E profile9(9) TS 101 270-1 Noise F ------------+----------------------------- 
.1.3.6.1.2.1.167.1.2.6.1.1.5,EFM-CU-MIB::efmCuPme10PBandNotchProfiles,BITS,read-create,,current,profile0(0):profile1(1):profile2(2):profile3(3):profile4(4):profile5(5):profile6(6):profile7(7):profile8(8):profile9(9):profile10(10):profile11(11),The 10PASS-TS PME Egress Control Band Notch Profile bitmap, as specified in 802.3 Annex 62A, table 62A-4. Possible values are: --------------+--------+------+------------+------+------ Profile Name G.991.3 T1.424 TS 101 270-1 StartF EndF table table table (MHz) (MHz) --------------+--------+------+------------+------+------ profile0(0) no profile profile1(1) F-5 #01 - - 1.810 1.825 profile2(2) 6-2 15-1 17 1.810 2.000 profile3(3) F-5 #02 - - 1.907 1.912 profile4(4) F-5 #03 - - 3.500 3.575 profile5(5) 6-2 - 17 3.500 3.800 profile6(6) - 15-1 - 3.500 4.000 profile7(7) F-5 #04 - - 3.747 3.754 profile8(8) F-5 #05 - - 3.791 3.805 profile9(9) 6-2 - 17 7.000 7.100 profile10(10) F-5 #06 15-1 - 7.000 7.300 profile11(11) 6-2 15-1 1 10.100 10.150 --------------+--------+------+------------+------+------ Any combination of profiles can be specified by ORing individual profiles, for example, a value of 0x2230 selects profiles 2, 6, 10, and 11.
.1.3.6.1.2.1.167.1.2.6.1.1.6,EFM-CU-MIB::efmCuPme10PPayloadDRateProfile,INTEGER,read-create,,current,profile5(5):profile10(10):profile15(15):profile20(20):profile25(25):profile30(30):profile50(50):profile70(70):profile100(100):profile140(140):profile200(200),The 10PASS-TS PME Downstream Payload Rate Profile, as specified in 802.3 Annex 62A. Possible values are: profile5(5) - 2.5 Mbps profile10(10) - 5 Mbps profile15(15) - 7.5 Mbps profile20(20) - 10 Mbps profile25(25) - 12.5 Mbps profile30(30) - 15 Mbps profile50(50) - 25 Mbps profile70(70) - 35 Mbps profile100(100) - 50 Mbps profile140(140) - 70 Mbps profile200(200) - 100 Mbps Each value represents a target for the PME's Downstream Payload Bitrate as seen at the MII. If the payload rate of the selected profile cannot be achieved based on the loop environment, bandplan, and PSD mask, the PME initialization SHALL fail.
.1.3.6.1.2.1.167.1.2.6.1.1.7,EFM-CU-MIB::efmCuPme10PPayloadURateProfile,INTEGER,read-create,,current,profile5(5):profile10(10):profile15(15):profile20(20):profile25(25):profile30(30):profile50(50):profile70(70):profile100(100),The 10PASS-TS PME Upstream Payload Rate Profile, as specified in 802.3 Annex 62A. Possible values are: profile5(5) - 2.5 Mbps profile10(10) - 5 Mbps profile15(15) - 7.5 Mbps profile20(20) - 10 Mbps profile25(25) - 12.5 Mbps profile30(30) - 15 Mbps profile50(50) - 25 Mbps profile70(70) - 35 Mbps profile100(100) - 50 Mbps Each value represents a target for the PME's Upstream Payload Bitrate as seen at the MII. If the payload rate of the selected profile cannot be achieved based on the loop environment, bandplan, and PSD mask, the PME initialization SHALL fail.
.1.3.6.1.2.1.167.1.2.6.1.1.8,EFM-CU-MIB::efmCuPme10PProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls creation, modification, or deletion of the associated entry in efmCuPme10PProfileTable per the semantics of RowStatus. If an active entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile, the entry MUST remain 'active' until all references are removed. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
.1.3.6.1.2.1.167.1.2.6.2,EFM-CU-MIB::efmCuPme10PStatusTable,,not-accessible,,current,,This table provides status information of EFMCu 10PASS-TS PMEs (modems). This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.167.1.2.6.2.1,EFM-CU-MIB::efmCuPme10PStatusEntry,,not-accessible,ifIndex,current,,An entry in the EFMCu 10PASS-TS PME Status table.
.1.3.6.1.2.1.167.1.2.6.2.1.1,EFM-CU-MIB::efmCuPme10PFECCorrectedBlocks,Counter32,read-only,,current,,The number of received and corrected Forward Error Correction (FEC) codewords in this 10PASS-TS PME. This object maps to the aPMEFECCorrectedBlocks attribute in Clause 30. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC correctable errors register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.1.2.6.2.1.2,EFM-CU-MIB::efmCuPme10PFECUncorrectedBlocks,Counter32,read-only,,current,,The number of received uncorrectable FEC codewords in this 10PASS-TS PME. This object maps to the aPMEFECUncorrectableBlocks attribute in Clause 30. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC uncorrectable errors register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
.1.3.6.1.2.1.167.2,EFM-CU-MIB::efmCuConformance,,,,,,
.1.3.6.1.2.1.167.2.1,EFM-CU-MIB::efmCuGroups,,,,,,
.1.3.6.1.2.1.167.2.1.1,EFM-CU-MIB::efmCuBasicGroup,,,,,,A collection of objects representing management information common for all types of EFMCu ports.
.1.3.6.1.2.1.167.2.1.2,EFM-CU-MIB::efmCuPAFGroup,,,,,,A collection of objects supporting OPTIONAL PME Aggregation Function (PAF) and PAF discovery in EFMCu ports.
.1.3.6.1.2.1.167.2.1.3,EFM-CU-MIB::efmCuPAFErrorsGroup,,,,,,A collection of objects supporting OPTIONAL error counters of PAF on EFMCu ports.
.1.3.6.1.2.1.167.2.1.4,EFM-CU-MIB::efmCuPmeGroup,,,,,,A collection of objects providing information about a 2BASE-TL/10PASS-TS PME.
.1.3.6.1.2.1.167.2.1.5,EFM-CU-MIB::efmCuAlarmConfGroup,,,,,,A collection of objects supporting configuration of alarm thresholds and notifications in EFMCu ports.
.1.3.6.1.2.1.167.2.1.6,EFM-CU-MIB::efmCuNotificationGroup,,,,,,This group supports notifications of significant conditions associated with EFMCu ports.
.1.3.6.1.2.1.167.2.1.7,EFM-CU-MIB::efmCuPme2BProfileGroup,,,,,,A collection of objects that constitute a configuration profile for configuration of 2BASE-TL ports.
.1.3.6.1.2.1.167.2.1.8,EFM-CU-MIB::efmCuPme10PProfileGroup,,,,,,A collection of objects that constitute a configuration profile for configuration of 10PASS-TS ports.
.1.3.6.1.2.1.167.2.1.9,EFM-CU-MIB::efmCuPme10PStatusGroup,,,,,,A collection of objects providing status information specific to 10PASS-TS PMEs.
.1.3.6.1.2.1.167.2.2,EFM-CU-MIB::efmCuCompliances,,,,,,
.1.3.6.1.2.1.167.2.2.1,EFM-CU-MIB::efmCuCompliance,,,,,,The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3 Compliance with the following external compliance statements is OPTIONAL for implementations supporting PME Aggregation Function (PAF) with flexible cross-connect between the PCS and PME ports: MIB Module Compliance Statement ---------- -------------------- IF-INVERTED-STACK-MIB ifInvCompliance IF-CAP-STACK-MIB ifCapStackCompliance
.1.3.6.1.2.1.168,IPMCAST-MIB::ipMcastMIB,,,,,,The MIB module for management of IP Multicast, including multicast routing, data forwarding, and data reception. Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5132; see the RFC itself for full legal notices.
.1.3.6.1.2.1.168.1,IPMCAST-MIB::ipMcast,,,,,,
.1.3.6.1.2.1.168.1.1,IPMCAST-MIB::ipMcastEnabled,INTEGER,read-write,,current,true(1):false(2),The enabled status of IP Multicast function on this system. The storage type of this object is determined by ipMcastDeviceConfigStorageType.
.1.3.6.1.2.1.168.1.2,IPMCAST-MIB::ipMcastRouteEntryCount,Gauge32,read-only,,current,,The number of rows in the ipMcastRouteTable. This can be used to check for multicast routing activity, and to monitor the multicast routing table size.
.1.3.6.1.2.1.168.1.3,IPMCAST-MIB::ipMcastInterfaceTable,,not-accessible,,current,,The (conceptual) table used to manage the multicast protocol active on an interface.
.1.3.6.1.2.1.168.1.3.1,IPMCAST-MIB::ipMcastInterfaceEntry,,not-accessible,ipMcastInterfaceIPVersion:ipMcastInterfaceIfIndex,current,,An entry (conceptual row) containing the multicast protocol information for a particular interface. Per-interface multicast forwarding statistics are also available in ipIfStatsTable.
.1.3.6.1.2.1.168.1.3.1.1,IPMCAST-MIB::ipMcastInterfaceIPVersion,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2),The IP version of this row.
.1.3.6.1.2.1.168.1.3.1.2,IPMCAST-MIB::ipMcastInterfaceIfIndex,Integer32,not-accessible,,current,,The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex.
.1.3.6.1.2.1.168.1.3.1.3,IPMCAST-MIB::ipMcastInterfaceTtl,Unsigned32,read-write,,current,,The datagram Time to Live (TTL) threshold for the interface. Any IP multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) less than this threshold will not be forwarded out the interface. The default value of 0 means all multicast packets are forwarded out the interface. A value of 256 means that no multicast packets are forwarded out the interface.
.1.3.6.1.2.1.168.1.3.1.4,IPMCAST-MIB::ipMcastInterfaceRateLimit,Unsigned32,read-write,,current,,The rate-limit, in kilobits per second, of forwarded multicast traffic on the interface. A rate-limit of 0 indicates that no rate limiting is done.
.1.3.6.1.2.1.168.1.3.1.5,IPMCAST-MIB::ipMcastInterfaceStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.168.1.4,IPMCAST-MIB::ipMcastSsmRangeTable,,not-accessible,,current,,This table is used to create and manage the range(s) of group addresses to which SSM semantics should be applied.
.1.3.6.1.2.1.168.1.4.1,IPMCAST-MIB::ipMcastSsmRangeEntry,,not-accessible,ipMcastSsmRangeAddressType:ipMcastSsmRangeAddress:ipMcastSsmRangePrefixLength,current,,An entry (conceptual row) containing a range of group addresses to which SSM semantics should be applied. Object Identifiers (OIDs) are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit.
.1.3.6.1.2.1.168.1.4.1.1,IPMCAST-MIB::ipMcastSsmRangeAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the multicast group prefix.
.1.3.6.1.2.1.168.1.4.1.2,IPMCAST-MIB::ipMcastSsmRangeAddress,OCTET,not-accessible,,current,,The multicast group address which, when combined with ipMcastSsmRangePrefixLength, gives the group prefix for this SSM range. The InetAddressType is given by ipMcastSsmRangeAddressType. This address object is only significant up to ipMcastSsmRangePrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For IPv6 SSM address ranges, only ranges prefixed by FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291 multicast address scope. The syntax of the address range is given by RFC 3306, Sections 4 and 7. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this SSM range entry applies only within the given zone. Zone index zero is not valid in this table. If non-global scope SSM range entries are present, then consistent ipMcastBoundaryTable entries are required on routers at the zone boundary.
.1.3.6.1.2.1.168.1.4.1.3,IPMCAST-MIB::ipMcastSsmRangePrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with ipMcastSsmRangeAddress, gives the group prefix for this SSM range. The InetAddressType is given by ipMcastSsmRangeAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.4.1.4,IPMCAST-MIB::ipMcastSsmRangeRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which rows in this table can be created and destroyed. This status object can be set to active(1) without setting any other columnar objects in this entry. All writeable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.168.1.4.1.5,IPMCAST-MIB::ipMcastSsmRangeStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.168.1.5,IPMCAST-MIB::ipMcastRouteTable,,not-accessible,,current,,The (conceptual) table containing multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to this router.
.1.3.6.1.2.1.168.1.5.1,IPMCAST-MIB::ipMcastRouteEntry,,not-accessible,ipMcastRouteGroupAddressType:ipMcastRouteGroup:ipMcastRouteGroupPrefixLength:ipMcastRouteSourceAddressType:ipMcastRouteSource:ipMcastRouteSourcePrefixLength,current,,An entry (conceptual row) containing the multicast routing information for IP datagrams from a particular source and addressed to a particular IP multicast group address. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit.
.1.3.6.1.2.1.168.1.5.1.1,IPMCAST-MIB::ipMcastRouteGroupAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteGroup. Legal values correspond to the subset of address families for which multicast forwarding is supported.
.1.3.6.1.2.1.168.1.5.1.2,IPMCAST-MIB::ipMcastRouteGroup,OCTET,not-accessible,,current,,The IP multicast group address which, when combined with the corresponding value specified in ipMcastRouteGroupPrefixLength, identifies the groups for which this entry contains multicast routing information. This address object is only significant up to ipMcastRouteGroupPrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this forwarding state applies only within the given zone. Zone index zero is not valid in this table.
.1.3.6.1.2.1.168.1.5.1.3,IPMCAST-MIB::ipMcastRouteGroupPrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with the corresponding value of ipMcastRouteGroup, identifies the groups for which this entry contains multicast routing information. The InetAddressType is given by ipMcastRouteGroupAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.5.1.4,IPMCAST-MIB::ipMcastRouteSourceAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteSource. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of ipMcastRouteGroupType.
.1.3.6.1.2.1.168.1.5.1.5,IPMCAST-MIB::ipMcastRouteSource,OCTET,not-accessible,,current,,The network address which, when combined with the corresponding value of ipMcastRouteSourcePrefixLength, identifies the sources for which this entry contains multicast routing information. This address object is only significant up to ipMcastRouteSourcePrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this source address applies only within the given zone. Zone index zero is not valid in this table.
.1.3.6.1.2.1.168.1.5.1.6,IPMCAST-MIB::ipMcastRouteSourcePrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with the corresponding value of ipMcastRouteSource, identifies the sources for which this entry contains multicast routing information. The InetAddressType is given by ipMcastRouteSourceAddressType. For the value 'unknown', this object must be zero. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.5.1.7,IPMCAST-MIB::ipMcastRouteUpstreamNeighborType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteUpstreamNeighbor. An address type of unknown(0) indicates that the upstream neighbor is unknown, for example in BIDIR-PIM.
.1.3.6.1.2.1.168.1.5.1.8,IPMCAST-MIB::ipMcastRouteUpstreamNeighbor,OCTET,read-only,,current,,The address of the upstream neighbor (for example, RPF neighbor) from which IP datagrams from these sources to this multicast address are received.
.1.3.6.1.2.1.168.1.5.1.9,IPMCAST-MIB::ipMcastRouteInIfIndex,Integer32,read-only,,current,,The value of ifIndex for the interface on which IP datagrams sent by these sources to this multicast address are received. A value of 0 indicates that datagrams are not subject to an incoming interface check, but may be accepted on multiple interfaces (for example, in BIDIR-PIM).
.1.3.6.1.2.1.168.1.5.1.10,IPMCAST-MIB::ipMcastRouteTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the multicast routing information represented by this entry was learned by the router. If this information was present at the most recent re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.168.1.5.1.11,IPMCAST-MIB::ipMcastRouteExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. The value 0 indicates that the entry is not subject to aging. If ipMcastRouteNextHopState is pruned(1), this object represents the remaining time until the prune expires. If this timer expires, state reverts to forwarding(2). Otherwise, this object represents the time until this entry is removed from the table.
.1.3.6.1.2.1.168.1.5.1.12,IPMCAST-MIB::ipMcastRouteProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The multicast routing protocol via which this multicast forwarding entry was learned.
.1.3.6.1.2.1.168.1.5.1.13,IPMCAST-MIB::ipMcastRouteRtProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing mechanism via which the route used to find the upstream or parent interface for this multicast forwarding entry was learned.
.1.3.6.1.2.1.168.1.5.1.14,IPMCAST-MIB::ipMcastRouteRtAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteRtAddress.
.1.3.6.1.2.1.168.1.5.1.15,IPMCAST-MIB::ipMcastRouteRtAddress,OCTET,read-only,,current,,The address portion of the route used to find the upstream or parent interface for this multicast forwarding entry. This address object is only significant up to ipMcastRouteRtPrefixLength bits. The remaining address bits are set to zero. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this forwarding state applies only within the given zone. Zone index zero is not valid in this table.
.1.3.6.1.2.1.168.1.5.1.16,IPMCAST-MIB::ipMcastRouteRtPrefixLength,Unsigned32,read-only,,current,,The length in bits of the mask associated with the route used to find the upstream or parent interface for this multicast forwarding entry. The InetAddressType is given by ipMcastRouteRtAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.5.1.17,IPMCAST-MIB::ipMcastRouteRtType,INTEGER,read-only,,current,unicast(1):multicast(2),The reason the given route was placed in the (logical) multicast Routing Information Base (RIB). A value of unicast means that the route would normally be placed only in the unicast RIB, but was placed in the multicast RIB due (instead or in addition) to local configuration, such as when running PIM over RIP. A value of multicast means that the route was explicitly added to the multicast RIB by the routing protocol, such as the Distance Vector Multicast Routing Protocol (DVMRP) or Multiprotocol BGP.
.1.3.6.1.2.1.168.1.5.1.18,IPMCAST-MIB::ipMcastRouteOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams that were received from these sources and addressed to this multicast group address, and which were forwarded by this router. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
.1.3.6.1.2.1.168.1.5.1.19,IPMCAST-MIB::ipMcastRoutePkts,Counter64,read-only,,current,,The number of packets routed using this multicast route entry. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
.1.3.6.1.2.1.168.1.5.1.20,IPMCAST-MIB::ipMcastRouteTtlDropOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams that this router has received from these sources and addressed to this multicast group address, which were dropped because the TTL (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a value less than ipMcastInterfaceTtl for all next hops. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
.1.3.6.1.2.1.168.1.5.1.21,IPMCAST-MIB::ipMcastRouteTtlDropPackets,Counter64,read-only,,current,,The number of packets that this router has received from these sources and addressed to this multicast group address, which were dropped because the TTL (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a value less than ipMcastInterfaceTtl for all next hops. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
.1.3.6.1.2.1.168.1.5.1.22,IPMCAST-MIB::ipMcastRouteDifferentInIfOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams that this router has received from these sources and addressed to this multicast group address, which were dropped because they were received on an unexpected interface. For RPF checking protocols (such as PIM-SM), these packets arrived on interfaces other than ipMcastRouteInIfIndex, and were dropped because of this failed RPF check. (RPF paths are 'Reverse Path Forwarding' paths; the unicast routes to the expected origin of multicast data flows). Other protocols may drop packets on an incoming interface check for different reasons (for example, BIDIR-PIM performs a DF check on receipt of packets). All packets dropped as a result of an incoming interface check are counted here. If this counter increases rapidly, this indicates a problem. A significant quantity of multicast data is arriving at this router on unexpected interfaces, and is not being forwarded. For guidance, if the rate of increase of this counter exceeds 1% of the rate of increase of ipMcastRouteOctets, then there are multicast routing problems that require investigation. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
.1.3.6.1.2.1.168.1.5.1.23,IPMCAST-MIB::ipMcastRouteDifferentInIfPackets,Counter64,read-only,,current,,The number of packets which this router has received from these sources and addressed to this multicast group address, which were dropped because they were received on an unexpected interface. For RPF checking protocols (such as PIM-SM), these packets arrived on interfaces other than ipMcastRouteInIfIndex, and were dropped because of this failed RPF check. (RPF paths are 'Reverse Path Forwarding' path; the unicast routes to the expected origin of multicast data flows). Other protocols may drop packets on an incoming interface check for different reasons (for example, BIDIR-PIM performs a DF check on receipt of packets). All packets dropped as a result of an incoming interface check are counted here. If this counter increases rapidly, this indicates a problem. A significant quantity of multicast data is arriving at this router on unexpected interfaces, and is not being forwarded. For guidance, if the rate of increase of this counter exceeds 1% of the rate of increase of ipMcastRoutePkts, then there are multicast routing problems that require investigation. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteTimeStamp.
.1.3.6.1.2.1.168.1.5.1.24,IPMCAST-MIB::ipMcastRouteBps,Counter64,read-only,,current,,Bits per second forwarded by this router using this multicast routing entry. This value is a sample; it is the number of bits forwarded during the last whole 1 second sampling period. The value during the current 1 second sampling period is not made available until the period is completed. The quantity being sampled is the same as that measured by ipMcastRouteOctets. The units and the sampling method are different.
.1.3.6.1.2.1.168.1.6,IPMCAST-MIB::ipMcastRouteNextHopTable,,not-accessible,,current,,The (conceptual) table containing information on the next-hops on outgoing interfaces for routing IP multicast datagrams. Each entry is one of a list of next-hops on outgoing interfaces for particular sources sending to a particular multicast group address.
.1.3.6.1.2.1.168.1.6.1,IPMCAST-MIB::ipMcastRouteNextHopEntry,,not-accessible,ipMcastRouteNextHopGroupAddressType:ipMcastRouteNextHopGroup:ipMcastRouteNextHopGroupPrefixLength:ipMcastRouteNextHopSourceAddressType:ipMcastRouteNextHopSource:ipMcastRouteNextHopSourcePrefixLength:ipMcastRouteNextHopIfIndex:ipMcastRouteNextHopAddressType:ipMcastRouteNextHopAddress,current,,An entry (conceptual row) in the list of next-hops on outgoing interfaces to which IP multicast datagrams from particular sources to an IP multicast group address are routed. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit.
.1.3.6.1.2.1.168.1.6.1.1,IPMCAST-MIB::ipMcastRouteNextHopGroupAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteNextHopGroup. Legal values correspond to the subset of address families for which multicast forwarding is supported.
.1.3.6.1.2.1.168.1.6.1.2,IPMCAST-MIB::ipMcastRouteNextHopGroup,OCTET,not-accessible,,current,,The IP multicast group address which, when combined with the corresponding value specified in ipMcastRouteNextHopGroupPrefixLength, identifies the groups for which this entry contains multicast forwarding information. This address object is only significant up to ipMcastRouteNextHopGroupPrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this forwarding state applies only within the given zone. Zone index zero is not valid in this table.
.1.3.6.1.2.1.168.1.6.1.3,IPMCAST-MIB::ipMcastRouteNextHopGroupPrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with the corresponding value of ipMcastRouteGroup, identifies the groups for which this entry contains multicast routing information. The InetAddressType is given by ipMcastRouteNextHopGroupAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.6.1.4,IPMCAST-MIB::ipMcastRouteNextHopSourceAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteNextHopSource. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of ipMcastRouteNextHopGroupType.
.1.3.6.1.2.1.168.1.6.1.5,IPMCAST-MIB::ipMcastRouteNextHopSource,OCTET,not-accessible,,current,,The network address which, when combined with the corresponding value of the mask specified in ipMcastRouteNextHopSourcePrefixLength, identifies the sources for which this entry specifies a next-hop on an outgoing interface. This address object is only significant up to ipMcastRouteNextHopSourcePrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this source address applies only within the given zone. Zone index zero is not valid in this table.
.1.3.6.1.2.1.168.1.6.1.6,IPMCAST-MIB::ipMcastRouteNextHopSourcePrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with the corresponding value specified in ipMcastRouteNextHopSource, identifies the sources for which this entry specifies a next-hop on an outgoing interface. The InetAddressType is given by ipMcastRouteNextHopSourceAddressType. For the value 'unknown', this object must be zero. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.6.1.7,IPMCAST-MIB::ipMcastRouteNextHopIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for the outgoing interface for this next-hop.
.1.3.6.1.2.1.168.1.6.1.8,IPMCAST-MIB::ipMcastRouteNextHopAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastRouteNextHopAddress.
.1.3.6.1.2.1.168.1.6.1.9,IPMCAST-MIB::ipMcastRouteNextHopAddress,OCTET,not-accessible,,current,,The address of the next-hop specific to this entry. For most interfaces, this is identical to ipMcastRouteNextHopGroup. Non-Broadcast Multi-Access (NBMA) interfaces, however, may have multiple next-hop addresses out a single outgoing interface.
.1.3.6.1.2.1.168.1.6.1.10,IPMCAST-MIB::ipMcastRouteNextHopState,INTEGER,read-only,,current,pruned(1):forwarding(2),An indication of whether the outgoing interface and next- hop represented by this entry is currently being used to forward IP datagrams. The value 'forwarding' indicates it is currently being used; the value 'pruned' indicates it is not.
.1.3.6.1.2.1.168.1.6.1.11,IPMCAST-MIB::ipMcastRouteNextHopTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the multicast routing information represented by this entry was learned by the router. If this information was present at the most recent re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.168.1.6.1.12,IPMCAST-MIB::ipMcastRouteNextHopExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. If ipMcastRouteNextHopState is pruned(1), the remaining time until the prune expires and the state reverts to forwarding(2). Otherwise, the remaining time until this entry is removed from the table. The time remaining may be copied from ipMcastRouteExpiryTime if the protocol in use for this entry does not specify next-hop timers. The value 0 indicates that the entry is not subject to aging.
.1.3.6.1.2.1.168.1.6.1.13,IPMCAST-MIB::ipMcastRouteNextHopClosestMemberHops,Unsigned32,read-only,,current,,The minimum number of hops between this router and any member of this IP multicast group reached via this next-hop on this outgoing interface. Any IP multicast datagrams for the group that have a TTL (IPv4) or Hop Count (IPv6) less than this number of hops will not be forwarded to this next-hop. A value of 0 means all multicast datagrams are forwarded out the interface. A value of 256 means that no multicast datagrams are forwarded out the interface. This is an optimization applied by multicast routing protocols that explicitly track hop counts to downstream listeners. Multicast protocols that are not aware of hop counts to downstream listeners set this object to 0.
.1.3.6.1.2.1.168.1.6.1.14,IPMCAST-MIB::ipMcastRouteNextHopProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The routing mechanism via which this next-hop was learned.
.1.3.6.1.2.1.168.1.6.1.15,IPMCAST-MIB::ipMcastRouteNextHopOctets,Counter64,read-only,,current,,The number of octets of multicast packets that have been forwarded using this route. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteNextHopTimeStamp.
.1.3.6.1.2.1.168.1.6.1.16,IPMCAST-MIB::ipMcastRouteNextHopPkts,Counter64,read-only,,current,,The number of packets which have been forwarded using this route. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of ipMcastRouteNextHopTimeStamp.
.1.3.6.1.2.1.168.1.7,IPMCAST-MIB::ipMcastBoundaryTable,,not-accessible,,current,,The (conceptual) table listing the system's multicast scope zone boundaries.
.1.3.6.1.2.1.168.1.7.1,IPMCAST-MIB::ipMcastBoundaryEntry,,not-accessible,ipMcastBoundaryIfIndex:ipMcastBoundaryAddressType:ipMcastBoundaryAddress:ipMcastBoundaryAddressPrefixLength,current,,An entry (conceptual row) describing one of this device's multicast scope zone boundaries. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit.
.1.3.6.1.2.1.168.1.7.1.1,IPMCAST-MIB::ipMcastBoundaryIfIndex,Integer32,not-accessible,,current,,The IfIndex value for the interface to which this boundary applies. Packets with a destination address in the associated address/mask range will not be forwarded over this interface. For IPv4, zone boundaries cut through links. Therefore, this is an external interface. This may be either a physical or virtual interface (tunnel, encapsulation, and so forth.) For IPv6, zone boundaries cut through nodes. Therefore, this is a virtual interface within the node. This is not an external interface, either real or virtual. Packets crossing this interface neither arrive at nor leave the node, but only move between zones within the node.
.1.3.6.1.2.1.168.1.7.1.2,IPMCAST-MIB::ipMcastBoundaryAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastBoundaryAddress. Legal values correspond to the subset of address families for which multicast forwarding is supported.
.1.3.6.1.2.1.168.1.7.1.3,IPMCAST-MIB::ipMcastBoundaryAddress,OCTET,not-accessible,,current,,The group address which, when combined with the corresponding value of ipMcastBoundaryAddressPrefixLength, identifies the group range for which the scoped boundary exists. Scoped IPv4 multicast address ranges must be prefixed by 239.0.0.0/8. Scoped IPv6 multicast address ranges are FF0x::/16, where x is a valid RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A zone boundary for FF0x::/16 implies an identical boundary for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table. This address object is only significant up to ipMcastBoundaryAddressPrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry.
.1.3.6.1.2.1.168.1.7.1.4,IPMCAST-MIB::ipMcastBoundaryAddressPrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which when, combined with the corresponding value of ipMcastBoundaryAddress, identifies the group range for which the scoped boundary exists. The InetAddressType is given by ipMcastBoundaryAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be set to 16.
.1.3.6.1.2.1.168.1.7.1.5,IPMCAST-MIB::ipMcastBoundaryTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the multicast boundary information represented by this entry was learned by the router. If this information was present at the most recent re- initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.168.1.7.1.6,IPMCAST-MIB::ipMcastBoundaryDroppedMcastOctets,Counter64,read-only,,current,,The number of octets of multicast packets that have been dropped as a result of this zone boundary configuration. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of boundary configuration being removed and replaced, which can be detected by observing the value of ipMcastBoundaryTimeStamp.
.1.3.6.1.2.1.168.1.7.1.7,IPMCAST-MIB::ipMcastBoundaryDroppedMcastPkts,Counter64,read-only,,current,,The number of multicast packets that have been dropped as a result of this zone boundary configuration. Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of boundary configuration being removed and replaced, which can be detected by observing the value of ipMcastBoundaryTimeStamp.
.1.3.6.1.2.1.168.1.7.1.8,IPMCAST-MIB::ipMcastBoundaryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which rows in this table can be created and destroyed. This status object can be set to active(1) without setting any other columnar objects in this entry. All writeable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.168.1.7.1.9,IPMCAST-MIB::ipMcastBoundaryStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.168.1.8,IPMCAST-MIB::ipMcastScopeNameTable,,not-accessible,,current,,The (conceptual) table listing multicast scope names.
.1.3.6.1.2.1.168.1.8.1,IPMCAST-MIB::ipMcastScopeNameEntry,,not-accessible,ipMcastScopeNameAddressType:ipMcastScopeNameAddress:ipMcastScopeNameAddressPrefixLength:ipMcastScopeNameLanguage,current,,An entry (conceptual row) that names a multicast address scope. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit.
.1.3.6.1.2.1.168.1.8.1.1,IPMCAST-MIB::ipMcastScopeNameAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastScopeNameAddress. Legal values correspond to the subset of address families for which multicast forwarding is supported.
.1.3.6.1.2.1.168.1.8.1.2,IPMCAST-MIB::ipMcastScopeNameAddress,OCTET,not-accessible,,current,,The group address which, when combined with the corresponding value of ipMcastScopeNameAddressPrefixLength, identifies the group range associated with the multicast scope. Scoped IPv4 multicast address ranges must be prefixed by 239.0.0.0/8. Scoped IPv6 multicast address ranges are FF0x::/16, where x is a valid RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A scope FF0x::/16 implies an identical scope name for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table. This address object is only significant up to ipMcastScopeNameAddressPrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry.
.1.3.6.1.2.1.168.1.8.1.3,IPMCAST-MIB::ipMcastScopeNameAddressPrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with the corresponding value of ipMcastScopeNameAddress, identifies the group range associated with the multicast scope. The InetAddressType is given by ipMcastScopeNameAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be set to 16.
.1.3.6.1.2.1.168.1.8.1.4,IPMCAST-MIB::ipMcastScopeNameLanguage,OCTET,not-accessible,,current,,Language tag associated with the scope name.
.1.3.6.1.2.1.168.1.8.1.5,IPMCAST-MIB::ipMcastScopeNameString,OCTET,read-create,,current,,The textual name associated with the multicast scope. The value of this object should be suitable for displaying to end-users, such as when allocating a multicast address in this scope. When no name is specified, the default value of this object for IPv4 should be the string 239.x.x.x/y with x and y replaced with decimal values to describe the address and mask length associated with the scope. When no name is specified, the default value of this object for IPv6 should be the string FF0x::/16, with x replaced by the hexadecimal value for the RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A scope FF0x::/16 implies an identical scope name for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table.
.1.3.6.1.2.1.168.1.8.1.6,IPMCAST-MIB::ipMcastScopeNameDefault,INTEGER,read-create,,current,true(1):false(2),If true, indicates a preference that the name in the following language should be used by applications if no name is available in a desired language.
.1.3.6.1.2.1.168.1.8.1.7,IPMCAST-MIB::ipMcastScopeNameStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which rows in this table can be created and destroyed. Before the row can be activated, the object ipMcastScopeNameString must be set to a valid value. All writeable objects in this entry can be modified when the status is active(1).
.1.3.6.1.2.1.168.1.8.1.8,IPMCAST-MIB::ipMcastScopeNameStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.168.1.9,IPMCAST-MIB::ipMcastLocalListenerTable,,not-accessible,,current,,The (conceptual) table listing local applications or services that have joined multicast groups as listeners. Entries exist for all addresses in the multicast range for all applications and services as they are classified on this device.
.1.3.6.1.2.1.168.1.9.1,IPMCAST-MIB::ipMcastLocalListenerEntry,,not-accessible,ipMcastLocalListenerGroupAddressType:ipMcastLocalListenerGroupAddress:ipMcastLocalListenerSourceAddressType:ipMcastLocalListenerSourceAddress:ipMcastLocalListenerSourcePrefixLength:ipMcastLocalListenerIfIndex:ipMcastLocalListenerRunIndex,current,,An entry (conceptual row) identifying a local application or service that has joined a multicast group as a listener. OIDs are limited to 128 sub-identifiers, but this limit is not enforced by the syntax of this entry. In practice, this does not present a problem, because IP address types allowed by conformance statements do not exceed this limit.
.1.3.6.1.2.1.168.1.9.1.1,IPMCAST-MIB::ipMcastLocalListenerGroupAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastLocalListenerGroupAddress. Legal values correspond to the subset of address families for which multicast is supported.
.1.3.6.1.2.1.168.1.9.1.2,IPMCAST-MIB::ipMcastLocalListenerGroupAddress,OCTET,not-accessible,,current,,The IP multicast group for which this entry specifies locally joined applications or services.
.1.3.6.1.2.1.168.1.9.1.3,IPMCAST-MIB::ipMcastLocalListenerSourceAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),A value indicating the address family of the address contained in ipMcastLocalListenerSource. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of ipMcastLocalListenerGroupAddressType.
.1.3.6.1.2.1.168.1.9.1.4,IPMCAST-MIB::ipMcastLocalListenerSourceAddress,OCTET,not-accessible,,current,,The network address which, when combined with the corresponding value of the mask specified in ipMcastLocalListenerSourcePrefixLength, identifies the sources for which this entry specifies a local listener. This address object is only significant up to ipMcastLocalListenerSourcePrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For addresses of type ipv4z or ipv6z, the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicate that this listener address applies only within the given zone. Zone index zero is not valid in this table.
.1.3.6.1.2.1.168.1.9.1.5,IPMCAST-MIB::ipMcastLocalListenerSourcePrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask which, when combined with the corresponding value specified in ipMcastLocalListenerSource, identifies the sources for which this entry specifies a local listener. The InetAddressType is given by ipMcastLocalListenerSourceAddressType. For the value 'unknown', this object must be zero. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.168.1.9.1.6,IPMCAST-MIB::ipMcastLocalListenerIfIndex,Integer32,not-accessible,,current,,The IfIndex value of the interface for which this entry specifies a local listener.
.1.3.6.1.2.1.168.1.9.1.7,IPMCAST-MIB::ipMcastLocalListenerRunIndex,Unsigned32,read-only,,current,,A unique value corresponding to a piece of software running on this router or host system. Where possible, this should be the system's native, unique identification number. This identifier is platform-specific. It may correspond to a process ID or application instance number. A value of zero indicates that the application instance(s) cannot be identified. A value of zero indicates that one or more unidentified applications have joined the specified multicast groups (for the specified sources) as listeners.
.1.3.6.1.2.1.168.1.10,IPMCAST-MIB::ipMcastZoneTable,,not-accessible,,current,,The (conceptual) table listing scope zones on this device.
.1.3.6.1.2.1.168.1.10.1,IPMCAST-MIB::ipMcastZoneEntry,,not-accessible,ipMcastZoneIndex,current,,An entry (conceptual row) describing a scope zone on this device.
.1.3.6.1.2.1.168.1.10.1.1,IPMCAST-MIB::ipMcastZoneIndex,Unsigned32,not-accessible,,current,,This zone index uniquely identifies a zone on a device. Each zone is for a given scope. Scope-level information in this table is for the unique scope that corresponds to this zone. Zero is a special value used to request the default zone for a given scope. Zero is not a valid value for this object. To test whether ipMcastZoneIndex is the default zone for this scope, test whether ipMcastZoneIndex is equal to ipMcastZoneScopeDefaultZoneIndex.
.1.3.6.1.2.1.168.1.10.1.2,IPMCAST-MIB::ipMcastZoneScopeDefaultZoneIndex,Unsigned32,read-only,,current,,The default zone index for this scope. This is the zone that this device will use if the default (zero) zone is requested for this scope. Zero is not a valid value for this object.
.1.3.6.1.2.1.168.1.10.1.3,IPMCAST-MIB::ipMcastZoneScopeAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The IP address type for which this scope zone exists.
.1.3.6.1.2.1.168.1.10.1.4,IPMCAST-MIB::ipMcastZoneScopeAddress,OCTET,read-only,,current,,The multicast group address which, when combined with ipMcastZoneScopeAddressPrefixLength, gives the multicast address range for this scope. The InetAddressType is given by ipMcastZoneScopeAddressType. Scoped IPv4 multicast address ranges are prefixed by 239.0.0.0/8. Scoped IPv6 multicast address ranges are FF0x::/16, where x is a valid RFC 4291 multicast scope. An IPv6 address prefixed by FF1x::/16 is a non-permanently- assigned address. An IPv6 address prefixed by FF3x::/16 is a unicast-prefix-based multicast addresses. A scope FF0x::/16 implies an identical scope for these other prefixes. No separate FF1x::/16 or FF3x::/16 entries exist in this table. This address object is only significant up to ipMcastZoneScopeAddressPrefixLength bits. The remaining address bits are set to zero.
.1.3.6.1.2.1.168.1.10.1.5,IPMCAST-MIB::ipMcastZoneScopeAddressPrefixLength,Unsigned32,read-only,,current,,The length in bits of the mask which, when combined with ipMcastZoneScopeAddress, gives the multicast address prefix for this scope. The InetAddressType is given by ipMcastZoneScopeAddressType. For values 'ipv4' and 'ipv4z', this object must be in the range 4..32. For values 'ipv6' and 'ipv6z', this object must be set to 16.
.1.3.6.1.2.1.168.1.11,IPMCAST-MIB::ipMcastDeviceConfigStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type used for the global IP multicast configuration of this device, comprised of the objects listed below. If this storage type takes the value 'permanent', write-access to the listed objects need not be allowed. The objects described by this storage type are: ipMcastEnabled.
.1.3.6.1.2.1.168.2,IPMCAST-MIB::ipMcastMIBConformance,,,,,,
.1.3.6.1.2.1.168.2.1,IPMCAST-MIB::ipMcastMIBCompliances,,,,,,
.1.3.6.1.2.1.168.2.1.1,IPMCAST-MIB::ipMcastMIBComplianceHost,,,,,,The compliance statement for hosts supporting IPMCAST-MIB. Support for either InetAddressType ipv4 or ipv6 is mandatory; support for both InetAddressTypes ipv4 and ipv6 is optional. Support for types ipv4z and ipv6z is optional. -- OBJECT ipMcastLocalListenerGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastLocalListenerGroupAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastLocalListenerSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastLocalListenerSourceAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6.
.1.3.6.1.2.1.168.2.1.2,IPMCAST-MIB::ipMcastMIBComplianceRouter,,,,,,The compliance statement for routers supporting IPMCAST-MIB. Support for either InetAddressType ipv4 or ipv6 is mandatory; support for both InetAddressTypes ipv4 and ipv6 is optional. Support for types ipv4z and ipv6z is optional. -- OBJECT ipMcastSsmRangeAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), ipv4z(3), -- ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastSsmRangeAddress -- SYNTAX InetAddress (SIZE (4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteNextHopAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6.
.1.3.6.1.2.1.168.2.1.3,IPMCAST-MIB::ipMcastMIBComplianceBorderRouter,,,,,,The compliance statement for routers on scope boundaries supporting IPMCAST-MIB. Support for either InetAddressType ipv4z or ipv6z is mandatory; support for both InetAddressTypes ipv4z and ipv6z is optional. -- OBJECT ipMcastSsmRangeAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2), ipv4z(3), -- ipv6z(4)} -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastSsmRangeAddress -- SYNTAX InetAddress (SIZE (4|8|16|20)) -- DESCRIPTION -- This compliance requires support for ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 or ipv6. -- -- OBJECT ipMcastRouteGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopGroupAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopGroup -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopSourceAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopSource -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopAddressType -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), -- ipv4z(3), ipv6z(4)} -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastRouteNextHopAddress -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) -- DESCRIPTION -- This compliance requires support for unknown and -- either ipv4 and ipv4z or ipv6 and ipv6z. -- -- OBJECT ipMcastBoundaryAddressType -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} -- DESCRI
.1.3.6.1.2.1.168.2.2,IPMCAST-MIB::ipMcastMIBGroups,,,,,,
.1.3.6.1.2.1.168.2.2.1,IPMCAST-MIB::ipMcastMIBBasicGroup,,,,,,A collection of objects to support basic management of IP Multicast protocols.
.1.3.6.1.2.1.168.2.2.2,IPMCAST-MIB::ipMcastMIBSsmGroup,,,,,,A collection of objects to support management of Source- Specific Multicast routing.
.1.3.6.1.2.1.168.2.2.3,IPMCAST-MIB::ipMcastMIBRouteGroup,,,,,,A collection of objects to support basic management of IP Multicast routing.
.1.3.6.1.2.1.168.2.2.4,IPMCAST-MIB::ipMcastMIBRouteDiagnosticsGroup,,,,,,A collection of routing diagnostic packet counters.
.1.3.6.1.2.1.168.2.2.5,IPMCAST-MIB::ipMcastMIBPktsOutGroup,,,,,,A collection of objects to support management of packet counters for each outgoing interface entry of a route.
.1.3.6.1.2.1.168.2.2.6,IPMCAST-MIB::ipMcastMIBHopCountGroup,,,,,,A collection of objects to support management of the use of hop counts in IP Multicast routing.
.1.3.6.1.2.1.168.2.2.7,IPMCAST-MIB::ipMcastMIBRouteOctetsGroup,,,,,,A collection of objects to support management of octet counters for each forwarding entry.
.1.3.6.1.2.1.168.2.2.8,IPMCAST-MIB::ipMcastMIBRouteBpsGroup,,,,,,A collection of objects to support sampling of data rate in bits per second for each forwarding entry.
.1.3.6.1.2.1.168.2.2.9,IPMCAST-MIB::ipMcastMIBRouteProtoGroup,,,,,,A collection of objects providing information on the relationship between multicast routing information and the IP Forwarding Table.
.1.3.6.1.2.1.168.2.2.10,IPMCAST-MIB::ipMcastMIBLocalListenerGroup,,,,,,A collection of objects to support management of local listeners on hosts or routers.
.1.3.6.1.2.1.168.2.2.11,IPMCAST-MIB::ipMcastMIBBoundaryIfGroup,,,,,,A collection of objects to support management of multicast scope zone boundaries.
.1.3.6.1.2.1.168.2.2.12,IPMCAST-MIB::ipMcastMIBScopeNameGroup,,,,,,A collection of objects to support management of multicast address scope names.
.1.3.6.1.2.1.169,PKTC-IETF-SIG-MIB::pktcIetfSigMib,,,,,,This MIB module supplies the basic management objects for the PacketCable and IPCablecom Signaling protocols. This version of the MIB includes common signaling and Network Call Signaling (NCS)-related signaling objects. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5098; see the RFC itself for full legal notices.
.1.3.6.1.2.1.169.0,PKTC-IETF-SIG-MIB::pktcSigNotification,,,,,,
.1.3.6.1.2.1.169.1,PKTC-IETF-SIG-MIB::pktcSigMibObjects,,,,,,
.1.3.6.1.2.1.169.1.1,PKTC-IETF-SIG-MIB::pktcSigDevObjects,,,,,,
.1.3.6.1.2.1.169.1.1.1,PKTC-IETF-SIG-MIB::pktcSigDevCodecTable,,not-accessible,,current,, This table describes the MTA-supported codec types. An MTA MUST populate this table with all possible combinations of codecs it supports for simultaneous operation. For example, an MTA with two endpoints may be designed with a particular Digital Signal Processing (DSP) and memory architecture that allows it to support the following fixed combinations of codecs for simultaneous operation: Codec Type Maximum Number of Simultaneous Codecs PCMA 3 PCMA 2 PCMU 1 PCMA 1 PCMU 2 PCMU 3 PCMA 1 G729 1 G729 2 PCMU 1 G729 1 Based on this example, the entries in the codec table would be: pktcSigDev pktcSigDev pktcSigDev CodecComboIndex CodecType CodecMax 1 pcma 3 2 pcma 2 2 pcmu 1 3 pcma 1 3 pcmu 2 4 pcmu 3 5 pcma 1 5 g729 1 6 g729 2 7 pcmu 1 7 g729 1 An operator querying this table is able to determine all possible codec combinations the MTA is capable of simultaneously supporting. This table MUST NOT include non-voice codecs.
.1.3.6.1.2.1.169.1.1.1.1,PKTC-IETF-SIG-MIB::pktcSigDevCodecEntry,,not-accessible,pktcSigDevCodecComboIndex:pktcSigDevCodecType,current,,Each entry represents the maximum number of active connections with a particular codec the MTA is capable of supporting. Each row is indexed by a composite key consisting of a number enumerating the particular codec combination and the codec type.
.1.3.6.1.2.1.169.1.1.1.1.1,PKTC-IETF-SIG-MIB::pktcSigDevCodecComboIndex,Unsigned32,not-accessible,,current,, The index value that enumerates a particular codec combination in the pktcSigDevCodecTable.
.1.3.6.1.2.1.169.1.1.1.1.2,PKTC-IETF-SIG-MIB::pktcSigDevCodecType,INTEGER,not-accessible,,current,other(1):unknown(2):g729(3):reserved(4):g729E(5):pcmu(6):g726at32(7):g728(8):pcma(9):g726at16(10):g726at24(11):g726at40(12):ilbc(13):bv16(14), A codec type supported by this MTA.
.1.3.6.1.2.1.169.1.1.1.1.3,PKTC-IETF-SIG-MIB::pktcSigDevCodecMax,Unsigned32,read-only,,current,, The maximum number of simultaneous sessions of a particular codec that the MTA can support.
.1.3.6.1.2.1.169.1.1.2,PKTC-IETF-SIG-MIB::pktcSigDevEchoCancellation,INTEGER,read-only,,current,true(1):false(2), This object specifies if the device is capable of echo cancellation. The MTA MUST set this MIB object to a value of true(1) if it is capable of echo cancellation, and a value of false(2) if not.
.1.3.6.1.2.1.169.1.1.3,PKTC-IETF-SIG-MIB::pktcSigDevSilenceSuppression,INTEGER,read-only,,current,true(1):false(2), This object specifies if the device is capable of silence suppression (as a result of Voice Activity Detection). The MTA MUST set this MIB object to a value of true(1) if it is capable of silence suppression, and a value of false(2) if not.
.1.3.6.1.2.1.169.1.1.4,PKTC-IETF-SIG-MIB::pktcSigDevCidSigProtocol,INTEGER,read-write,,current,fsk(1):dtmf(2),This object is used to configure the subscriber-line protocol used for signaling on-hook caller id information. Different countries define different caller id signaling protocols to support caller identification. Setting this object at a value fsk(1) sets the subscriber line protocol to be Frequency Shift Keying (FSK). Setting this object at a value dtmf(2) sets the subscriber line protocol to be Dual-Tone Multi-Frequency (DTMF). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.5,PKTC-IETF-SIG-MIB::pktcSigDevR0Cadence,OCTET,read-write,,current,, This object specifies ring cadence 0 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.6,PKTC-IETF-SIG-MIB::pktcSigDevR1Cadence,OCTET,read-write,,current,, This object specifies ring cadence 1 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.7,PKTC-IETF-SIG-MIB::pktcSigDevR2Cadence,OCTET,read-write,,current,, This object specifies ring cadence 2 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.8,PKTC-IETF-SIG-MIB::pktcSigDevR3Cadence,OCTET,read-write,,current,, This object specifies ring cadence 3 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.9,PKTC-IETF-SIG-MIB::pktcSigDevR4Cadence,OCTET,read-write,,current,, This object specifies ring cadence 4 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.10,PKTC-IETF-SIG-MIB::pktcSigDevR5Cadence,OCTET,read-write,,current,, This object specifies ring cadence 5 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.11,PKTC-IETF-SIG-MIB::pktcSigDevR6Cadence,OCTET,read-write,,current,, This object specifies ring cadence 6 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.12,PKTC-IETF-SIG-MIB::pktcSigDevR7Cadence,OCTET,read-write,,current,, This object specifies ring cadence 7 (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.13,PKTC-IETF-SIG-MIB::pktcSigDevRgCadence,OCTET,read-write,,current,, This object specifies ring cadence rg (a user-defined field). The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.14,PKTC-IETF-SIG-MIB::pktcSigDevRsCadence,OCTET,read-write,,current,, This object specifies ring cadence rs (a user-defined field). The MTA MUST reject any attempt to make this object repeatable. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.15,PKTC-IETF-SIG-MIB::pktcSigDefCallSigDscp,Integer32,read-write,,current,, The default value used in the IP header for setting the Differentiated Services Code Point (DSCP) value for call signaling. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.16,PKTC-IETF-SIG-MIB::pktcSigDefMediaStreamDscp,Integer32,read-write,,current,, This object contains the default value used in the IP header for setting the Differentiated Services Code Point (DSCP) value for media stream packets. The MTA MUST NOT update this object with the value supplied by the CMS in the NCS messages (if present). Any currently active connections are not affected by updates to this object. When the value of this object is updated by SNMP, the MTA MUST use the new value as a default starting only from new connections. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.17,PKTC-IETF-SIG-MIB::pktcSigCapabilityTable,,not-accessible,,current,, This table describes the signaling types supported by this MTA.
.1.3.6.1.2.1.169.1.1.17.1,PKTC-IETF-SIG-MIB::pktcSigCapabilityEntry,,not-accessible,pktcSigCapabilityIndex,current,, Entries in pktcMtaDevSigCapabilityTable - list of supported signaling types, versions, and vendor extensions for this MTA. Each entry in the list provides for one signaling type and version combination. If the device supports multiple versions of the same signaling type, it will require multiple entries.
.1.3.6.1.2.1.169.1.1.17.1.1,PKTC-IETF-SIG-MIB::pktcSigCapabilityIndex,Unsigned32,not-accessible,,current,, The index value that uniquely identifies an entry in the pktcSigCapabilityTable.
.1.3.6.1.2.1.169.1.1.17.1.2,PKTC-IETF-SIG-MIB::pktcSigCapabilityType,INTEGER,read-only,,current,other(1):ncs(2), This object identifies the type of signaling used. This value has to be associated with a single signaling version.
.1.3.6.1.2.1.169.1.1.17.1.3,PKTC-IETF-SIG-MIB::pktcSigCapabilityVersion,OCTET,read-only,,current,, Provides the version of the signaling type - reference pktcSigCapabilityType. Examples would be 1.0 or 2.33 etc.
.1.3.6.1.2.1.169.1.1.17.1.4,PKTC-IETF-SIG-MIB::pktcSigCapabilityVendorExt,OCTET,read-only,,current,, The vendor extension allows vendors to provide a list of additional capabilities. The syntax for this MIB object in ABNF ([RFC5234]) is specified to be zero or more occurrences of vendor extensions, as follows: pktcSigCapabilityVendorExt = *(vendor-extension) vendor-extension = (ext symbol alphanum) DQUOTE ; DQUOTE ext = DQUOTE %x58 DQUOTE symbol = (DQUOTE %x2D DQUOTE)/(DQUOTE %x2D DQUOTE) alphanum = 1*6(ALPHA/DIGIT) 
.1.3.6.1.2.1.169.1.1.18,PKTC-IETF-SIG-MIB::pktcSigDefNcsReceiveUdpPort,Unsigned32,read-only,,current,, This object contains the MTA User Datagram Protocol (UDP) receive port that is being used for NCS call signaling. This object should only be changed by the configuration file. Unless changed via configuration, this MIB object MUST reflect a value of '2427'.
.1.3.6.1.2.1.169.1.1.19,PKTC-IETF-SIG-MIB::pktcSigPowerRingFrequency,INTEGER,read-only,,current,f20Hz(1):f25Hz(2):f33Point33Hz(3):f50Hz(4):f15Hz(5):f16Hz(6):f22Hz(7):f23Hz(8):f45Hz(9), This object must only be provided via the configuration file during the provisioning process. The power ring frequency is the frequency at which the sinusoidal voltage must travel down the twisted pair to make terminal equipment ring. Different countries define different electrical characteristics to make terminal equipment ring. The f20Hz setting corresponds to a power ring frequency of 20 Hertz. The f25Hz setting corresponds to a power ring frequency of 25 Hertz. The f33Point33Hz setting corresponds to a power ring frequency of 33.33 Hertz. The f50Hz setting corresponds to a power ring frequency of 50 Hertz. The f15Hz setting corresponds to a power ring frequency of 15 Hertz. The f16Hz setting corresponds to a power ring frequency of 16 Hertz. The f22Hz setting corresponds to a power ring frequency of 22 Hertz. The f23Hz setting corresponds to a power ring frequency of 23 Hertz. The f45Hz setting corresponds to a power ring frequency of 45 Hertz.
.1.3.6.1.2.1.169.1.1.20,PKTC-IETF-SIG-MIB::pktcSigPulseSignalTable,,not-accessible,,current,, The Pulse signal table defines the pulse signal operation. There are nine types of international pulse signals, with each signal having a set of provisionable parameters. The values of the MIB objects in this table take effect only if these parameters are not defined via signaling, in which case, the latter determines the values of the parameters. The MIB objects in this table do not persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.20.1,PKTC-IETF-SIG-MIB::pktcSigPulseSignalEntry,,not-accessible,pktcSigPulseSignalType,current,, This object defines the set of parameters associated with each particular value of pktcSigPulseSignalType. Each entry in the pktcSigPulseSignalTable is indexed by the pktcSigPulseSignalType object. The conceptual rows MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.20.1.1,PKTC-IETF-SIG-MIB::pktcSigPulseSignalType,INTEGER,not-accessible,,current,initialRing(1):pulseLoopClose(2):pulseLoopOpen(3):enableMeterPulse(4):meterPulseBurst(5):pulseNoBattery(6):pulseNormalPolarity(7):pulseReducedBattery(8):pulseReversePolarity(9),There are nine types of international pulse signals. These signals are defined as follows: initial ring pulse loop close pulse loop open enable meter pulse meter pulse burst pulse no battery pulse normal polarity pulse reduced battery pulse reverse polarity
.1.3.6.1.2.1.169.1.1.20.1.2,PKTC-IETF-SIG-MIB::pktcSigPulseSignalFrequency,INTEGER,read-write,,current,twentyfive(1):twelvethousand(2):sixteenthousand(3), This object is only applicable to the initialRing, enableMeterPulse, and meterPulseBurst signal types. This object identifies the frequency of the generated signal. The following table defines the default values for this object depending on signal type: pktcSigPulseSignalType Default initialRing 25 enableMeterPulse 16000 meterPulseBurst 16000 The value of twentyfive MUST only be used for the initialRing signal type. The values of twelvethousand and sixteenthousand MUST only be used for enableMeterPulse and meterPulseBurst signal types. An attempt to set this object while the value of pktcSigPulseSignalType is not initialRing, enableMeterPulse, or meterPulseBurst will result in an 'inconsistentValue' error.
.1.3.6.1.2.1.169.1.1.20.1.3,PKTC-IETF-SIG-MIB::pktcSigPulseSignalDbLevel,Integer32,read-write,,current,, This object is only applicable to the enableMeterPulse and meterPulseBurst signal types. This is the decibel level for each frequency at which tones could be generated at the a and b terminals (TE connection point). An attempt to set this object while the value of pktcSigPulseSignalType is not enableMeterPulse or meterPulseBurst will result in an 'inconsistentValue' error.
.1.3.6.1.2.1.169.1.1.20.1.4,PKTC-IETF-SIG-MIB::pktcSigPulseSignalDuration,Unsigned32,read-write,,current,, This object specifies the pulse duration for each signal type. In addition, the MTA must accept the values in the incremental steps specific for each signal type. The following table defines the default values and the incremental steps for this object depending on the signal type: pktcSigPulseSignaltype Default (ms) Increment (ms) initialRing 200 50 pulseLoopClose 200 10 pulseLoopOpen 200 10 enableMeterPulse 150 10 meterPulseBurst 150 10 pulseNoBattery 200 10 pulseNormalPolarity 200 10 pulseReducedBattery 200 10 pulseReversePolarity 200 10 An attempt to set this object to a value that does not fall on one of the increment boundaries, or on the wrong increment boundary for the specific signal type, will result in an 'inconsistentValue' error.
.1.3.6.1.2.1.169.1.1.20.1.5,PKTC-IETF-SIG-MIB::pktcSigPulseSignalPulseInterval,Unsigned32,read-write,,current,, This object specifies the repeat interval, or the period, for each signal type. In addition, the MTA must accept the values in the incremental steps specific for each signal type. The following table defines the default values and the incremental steps for this object, depending on the signal type: pktcSigPulseSignaltype Default (ms) Increment (ms) initialRing 200 50 pulseLoopClose 1000 10 pulseLoopOpen 1000 10 enableMeterPulse 1000 10 meterPulseBurst 1000 10 pulseNoBattery 1000 10 pulseNormalPolarity 1000 10 pulseReducedBattery 1000 10 pulseReversePolarity 1000 10 An attempt to set this object to a value that does not fall on one of the increment boundaries, or on the wrong increment boundary for the specific signal type, will result in an 'inconsistentValue' error.
.1.3.6.1.2.1.169.1.1.20.1.6,PKTC-IETF-SIG-MIB::pktcSigPulseSignalRepeatCount,Unsigned32,read-write,,current,, This object specifies how many times to repeat a pulse. This object is not used by the enableMeterPulse signal type, and in that case, the value is irrelevant. The following table defines the default values and the valid ranges for this object, depending on the signal type: pktcSigPulseSignaltype Default Range initialRing 1 1-5 pulseLoopClose 1 1-50 pulseLoopOpen 1 1-50 enableMeterPulse (any value)(but not used) meterPulseBurst 1 1-50 pulseNoBattery 1 1-50 pulseNormalPolarity 1 1-50 pulseReducedBattery 1 1-50 pulseReversePolarity 1 1-50 An attempt to set this object to a value that does not fall within the range for the specific signal type will result in an 'inconsistentValue' error.
.1.3.6.1.2.1.169.1.1.21,PKTC-IETF-SIG-MIB::pktcSigDevCidMode,INTEGER,read-write,,current,duringRingingETS(1):dtAsETS(2):rpAsETS(3):lrAsETS(4):lrETS(5), For on-hook caller id, pktcSigDevCidMode selects the method for representing and signaling caller identification. For the duringRingingETS method, the Frequency Shift Keying (FSK) or the Dual-Tone Multi-Frequency (DTMF) containing the caller identification information is sent between the first and second ring pattern. For the dtAsETS,rpAsETS, lrAsETS and lrETS methods, the FSK or DTMF containing the caller id information is sent before the first ring pattern. For the dtAsETS method, the FSK or DTMF is sent after the Dual Tone Alert Signal. For the rpAsETS method, the FSK or DTMF is sent after a Ring Pulse. For the lrAsETS method, the Line Reversal occurs first, then the Dual Tone Alert Signal, and, finally, the FSK or DTMF is sent. For the lrETS method, the Line Reversal occurs first, then the FSK or DTMF is sent. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.22,PKTC-IETF-SIG-MIB::pktcSigDevCidAfterRing,Unsigned32,read-write,,current,, This object specifies the delay between the end of first ringing pattern and the start of the transmission of the FSK or DTMF containing the caller id information. It is only used when pktcSigDevCidMode is set to a value of 'duringRingingETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS 550 ms dtAsETS any value (not used) rpAsETS any value (not used) lrAsETS any value (not used) lrETS any value (not used) An attempt to set this object while the value of pktcSigDevCidMode is not duringringingETS will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.23,PKTC-IETF-SIG-MIB::pktcSigDevCidAfterDTAS,Unsigned32,read-write,,current,, This object specifies the delay between the end of the Dual Tone Alert Signal (DT-AS) and the start of the transmission of the FSK or DTMF containing the caller id information. This object is only used when pktcSigDevCidMode is set to a value of 'dtAsETS' or 'lrAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS any value (not used) dtAsETS 50 ms rpAsETS any value (not used) lrAsETS 50 ms lrETS any value (not used) An attempt to set this object while the value of pktcSigDevCidMode is not 'dtAsETS' or 'lrAsETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.24,PKTC-IETF-SIG-MIB::pktcSigDevCidAfterRPAS,Unsigned32,read-write,,current,, This object specifies the delay between the end of the Ring Pulse Alert Signal (RP-AS) and the start of the transmission of the FSK or DTMF containing the caller id information. This MIB object is only used when pktcSigDevCidMode is set to a value of 'rpAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS any value (not used) dtAsETS any value (not used) rpAsETS 650 ms lrAsETS any value (not used) lrETS any value (not used) An attempt to set this object while the value of pktcSigDevCidMode is not 'rpAsETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.25,PKTC-IETF-SIG-MIB::pktcSigDevRingAfterCID,Unsigned32,read-write,,current,, This object specifies the delay between the end of the complete transmission of the FSK or DTMF containing the caller id information and the start of the first ring pattern. It is only used when pktcSigDevCidMode is set to a value of 'dtAsETS', 'rpAsETS', 'lrAsETS' or 'lrETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS any value (not used) dtAsETS 250 ms rpAsETS 250 ms lrAsETS 250 ms lrETS 250 ms An attempt to set this object while the value of pktcSigDevCidMode is not 'dtAsETS', 'rpAsETS', 'lrAsETS', or 'lrETS' will result in an 'inconsistent value' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.26,PKTC-IETF-SIG-MIB::pktcSigDevCidDTASAfterLR,Unsigned32,read-write,,current,, This object specifies the delay between the end of the Line Reversal and the start of the Dual Tone Alert Signal (DT-AS). This object is only used when pktcSigDevCidMode is set to a value of 'lrAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS any value (not used) dtAsETS any value (not used) rpAsETS any value (not used) lrAsETS 250 ms lrETS any value (not used) An attempt to set this object while the value of pktcSigDevCidMode is not lrAsETS will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.27,PKTC-IETF-SIG-MIB::pktcSigDevVmwiMode,INTEGER,read-write,,current,dtAsETS(1):rpAsETS(2):lrAsETS(3):osi(4):lrETS(5), For visual message waiting indicator (VMWI), pktcSigDevVmwiMode selects the alerting signal method. For the dtAsETS, rpAsETS, lrAsETS, osi, and lrETS methods, the FSK containing the VMWI information is sent after an alerting signal. For the dtAsETS method, the FSK, or DTMF is sent after the Dual Tone Alert Signal. For the rpAsETS method, the FSK or DTMF is sent after a Ring Pulse. For the lrAsETS method, the Line Reversal occurs first, then the Dual Tone Alert Signal, and, finally, the FSK or DTMF is sent. For the OSI method, the FSK or DTMF is sent after the Open Switching Interval. For the lrETS method, the Line Reversal occurs first, then the FSK or DTMF is sent. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.28,PKTC-IETF-SIG-MIB::pktcSigDevVmwiAfterDTAS,Unsigned32,read-write,,current,, This object specifies the delay between the end of the Dual Tone Alert Signal (DT-AS) and the start of the transmission of the FSK or DTMF containing the VMWI information. This object is only used when pktcSigDevVmwiMode is set to a value of 'dtAsETS' or 'lrAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevVmwiMode), and MUST be followed: Value of pktcSigDevVmwiMode Default value dtAsETS 50 ms rpAsETS any value (not used) lrAsETS 50 ms lrETS any value (not used) An attempt to set this object while the value of pktcSigDevVmwiMode is not 'dtAsETS' or 'lrAsETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.29,PKTC-IETF-SIG-MIB::pktcSigDevVmwiAfterRPAS,Unsigned32,read-write,,current,, This object specifies the delay between the end of the Ring Pulse Alert Signal (RP-AS) and the start of the transmission of the FSK or DTMF containing the VMWI information. This object is only used when pktcSigDevVmwiMode is set to a value of 'rpAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevVmwiMode), and MUST be followed: Value of pktcSigDevVmwiMode Default value dtAsETS any value (not used) rpAsETS 650 ms lrAsETS any value (not used) lrETS any value (not used) An attempt to set this object while the value of pktcSigDevVmwiMode is not 'rpAsETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.30,PKTC-IETF-SIG-MIB::pktcSigDevVmwiDTASAfterLR,Unsigned32,read-write,,current,, This object specifies the delay between the end of the Line Reversal and the start of the Dual Tone Alert Signal (DT-AS) for VMWI information. This object is only used when pktcSigDevVmwiMode is set to a value of 'lrAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevVmwiMode), and MUST be followed: Value of pktcSigDevVmwiMode Default value dtAsETS any value (not used) rpAsETS any value (not used) lrAsETS 250 ms lrETS any value (not used) An attempt to set this object while the value of pktcSigDevVmwiMode is not 'lrAsETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.31,PKTC-IETF-SIG-MIB::pktcSigDevRingCadenceTable,,not-accessible,,current,,Cadence rings are defined by the telco governing body for each country. The MTA must be able to support various ranges of cadence patterns and cadence periods. The MTA will be able to support country-specific provisioning of the cadence and idle period. Each cadence pattern will be assigned a unique value ranging from 0-127 (inclusive) corresponding to the value of x, where x is the value sent in the cadence ringing (cr) signal cr(x), requested per the appropriate NCS message, and defined in the E package. The MTA will derive the cadence periods from the ring cadence table entry, as provisioned by the customer. The MTA is allowed to provide appropriate default values for each of the ring cadences. This table only needs to be supported when the MTA implements the E package.
.1.3.6.1.2.1.169.1.1.31.1,PKTC-IETF-SIG-MIB::pktcSigDevRingCadenceEntry,,not-accessible,pktcSigDevRingCadenceIndex,current,, Each entry in this row corresponds to a ring cadence that is being supported by the device. The conceptual rows MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.31.1.1,PKTC-IETF-SIG-MIB::pktcSigDevRingCadenceIndex,Unsigned32,not-accessible,,current,, A unique value ranging from 0 to 127 that corresponds to the value sent by the LE based on country-specific cadences, one row per cadence cycle. In any given system implementation for a particular country, it is anticipated that a small number of ring cadences will be in use. Thus, this table most likely will not be populated to its full size.
.1.3.6.1.2.1.169.1.1.31.1.2,PKTC-IETF-SIG-MIB::pktcSigDevRingCadence,OCTET,read-write,,current,,This is the Ring Cadence.
.1.3.6.1.2.1.169.1.1.32,PKTC-IETF-SIG-MIB::pktcSigDevToneTable,,not-accessible,,current,, The Tone Table defines the composition of tones and various tone operations. The definition of the tones callWaiting1 through callWaiting4 in this table MUST only contain the audible tone itself; the delay between tones or the value of the tone repeat count are not applicable for the call waiting tones. The delay between tones or the repeat count is controlled by the objects pktcSigEndPntConfigCallWaitingDelay and pktcSigEndPntConfigCallWaitingMaxRep. If the pktcSigDevToneType is set to either of the values callWaiting1, callWaiting2, callWaiting3, or callWaiting4, then the value of the pktcSigDevToneWholeToneRepeatCount object indicates that the particular frequency group is applicable, as a repeatable part of the tone, based on the value of the MIB object pktcSigDevToneWholeToneRepeatCount. The MTA MUST make sure that, after the provisioning cycle, the table is fully populated (i.e., for each possible index, an entry MUST be defined) using reasonable defaults for each row that was not defined by the provisioning information delivered via MTA Configuration. The frequency composition of each tone is defined by the pktcSigDevMultiFreqToneTable. For each tone type defined in pktcSigDevToneTable, the MTA MUST populate at least one entry in the pktcSigDevMultiFreqToneTable. For each particular value of pktcSigDevToneType, the pktcSigDevToneTable table can define non-repeating and repeating groups of the frequencies defined by the pktcSigDevMultiFreqToneTable, such that each group is represented by the set of the consecutive rows (frequency group) in the pktcSigDevMultiFreqToneTable. Objects in this table do not persist across MTA reboots. For tones with multiple frequencies refer to the MIB table pktcSigDevMultiFreqToneTable.
.1.3.6.1.2.1.169.1.1.32.1,PKTC-IETF-SIG-MIB::pktcSigDevToneEntry,,not-accessible,pktcSigDevToneType:pktcSigDevToneFreqGroup,current,, The different tone types that can be provisioned based on country-specific needs. Each entry contains the tone generation parameters for a specific frequency group of the specific Tone Type. The different parameters can be provisioned via MTA configuration based on country specific needs. An MTA MUST populate all entries of this table for each tone type.
.1.3.6.1.2.1.169.1.1.32.1.1,PKTC-IETF-SIG-MIB::pktcSigDevToneType,INTEGER,not-accessible,,current,busy(1):confirmation(2):dial(3):messageWaiting(4):offHookWarning(5):ringBack(6):reOrder(7):stutterdial(8):callWaiting1(9):callWaiting2(10):callWaiting3(11):callWaiting4(12):alertingSignal(13):specialDial(14):specialInfo(15):release(16):congestion(17):userDefined1(18):userDefined2(19):userDefined3(20):userDefined4(21),A unique value that will correspond to the different tone types. These tones can be provisioned based on country-specific needs. This object defines the type of tone being accessed. The alertingSignal, specialDial, specialInfo, release, congestion, userDefined1, userDefined2, userDefined3, and userDefined4 tone types are used in the E line package.
.1.3.6.1.2.1.169.1.1.32.1.2,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqGroup,Unsigned32,not-accessible,,current,,This MIB object represents the Tone Sequence reference of a multi-sequence tone.
.1.3.6.1.2.1.169.1.1.32.1.3,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqCounter,Unsigned32,read-only,,current,,This MIB object represents the number of consecutive multi-frequency tones for the particular tone type in the multi-frequency table (pktcSigDevMultiFreqToneTable). Such a sequence of the consecutive multi-frequency tones forms the tone group for the particular tone type in the pktcSigDevToneTable.
.1.3.6.1.2.1.169.1.1.32.1.4,PKTC-IETF-SIG-MIB::pktcSigDevToneWholeToneRepeatCount,Unsigned32,read-only,,current,,This is the repeat count, which signifies how many times to repeat the entire on-off cadence sequence. Setting this object may result in a cadence duration longer or shorter than the overall signal duration specified by the time out (TO) object for a particular signal. If the repeat count results in a longer tone duration than the signal duration specified by the TO, the tone duration defined by the TO object for a particular signal always represents the overall signal duration for a tone. In this case, the tone duration repeat count will not be fully exercised, and the desired tone duration will be truncated per the TO setting. If the repeat count results in a shorter tone duration than the signal duration specified by the TO, the tone duration defined by the repeat count takes precedence over the TO and will end the signal event. In this case, the TO represents a time not to be exceeded for the signal. It is recommended to ensure proper telephony signaling so that the TO duration setting should always be longer than the desired repeat count-time duration.
.1.3.6.1.2.1.169.1.1.32.1.5,PKTC-IETF-SIG-MIB::pktcSigDevToneSteady,INTEGER,read-only,,current,true(1):false(2),This MIB object represents the steady tone status. A value of 'true(1)' indicates that the steady tone is applied, and a value of 'false(2)' indicates otherwise. Devices must play out the on-off cadence sequence for the number of times indicated by the MIB object 'pktcSigDevToneWholeToneRepeatCount' prior to applying the last tone steadily, indefinitely. If the MIB table 'pktcSigDevToneTable' contains multiple rows with this Object set to a value of 'true(1)', the steady tone is applied to the last repeating frequency group of the tone. Setting this MIB object may result in a tone duration that is longer or shorter than the overall signal duration specified by the time out (TO) MIB object for a particular signal. If the repeat count results in a longer tone duration than the signal duration specified by the TO, the tone duration defined by the TO object for a particular signal always represents the overall signal duration for a tone. In this case, the tone duration repeat count will not be fully exercised, and the desired tone duration will be truncated per the TO setting. If the repeat count results in a shorter tone duration than the signal duration specified by the TO, the tone duration defined by the repeat count takes precedence over the TO and will end the signal event. In this case, the TO represents a time not to be exceeded for the signal. It is recommended to ensure proper telephony signaling that The TO duration setting should always be longer than the desired repeat count-time duration, plus the desired maximum steady tone period.
.1.3.6.1.2.1.169.1.1.33,PKTC-IETF-SIG-MIB::pktcSigDevMultiFreqToneTable,,not-accessible,,current,, This MIB table defines the characteristics of tones with multiple frequencies. The constraints imposed on the tones by the MIB table pktcSigDevToneTable need to be considered for MIB objects in this table as well. The MTA MUST populate the corresponding row(s) of the pktcSigDevMultiFreqToneTable for each tone defined in the pktcSigDevToneTable. The contents of the table may be provisioned via MTA configuration.
.1.3.6.1.2.1.169.1.1.33.1,PKTC-IETF-SIG-MIB::pktcSigDevMultiFreqToneEntry,,not-accessible,pktcSigDevToneType:pktcSigDevToneNumber,current,, The different tone types with multiple frequencies that can be provisioned based on country-specific needs.
.1.3.6.1.2.1.169.1.1.33.1.1,PKTC-IETF-SIG-MIB::pktcSigDevToneNumber,Unsigned32,not-accessible,,current,,This MIB object represents the frequency reference of a multi-frequency tone.
.1.3.6.1.2.1.169.1.1.33.1.2,PKTC-IETF-SIG-MIB::pktcSigDevToneFirstFreqValue,Unsigned32,read-only,,current,,This MIB object represents the value of the first frequency of a tone type. A value of zero implies absence of the referenced frequency.
.1.3.6.1.2.1.169.1.1.33.1.3,PKTC-IETF-SIG-MIB::pktcSigDevToneSecondFreqValue,Unsigned32,read-only,,current,,This MIB object represents the value of the second frequency of a tone type. A value of zero implies absence of the referenced frequency.
.1.3.6.1.2.1.169.1.1.33.1.4,PKTC-IETF-SIG-MIB::pktcSigDevToneThirdFreqValue,Unsigned32,read-only,,current,,This MIB object represents the value of the third frequency of a tone type. A value of zero implies absence of the referenced frequency.
.1.3.6.1.2.1.169.1.1.33.1.5,PKTC-IETF-SIG-MIB::pktcSigDevToneFourthFreqValue,Unsigned32,read-only,,current,,This MIB object represents the value of the fourth frequency of a tone type. A value of zero implies absence of the referenced frequency.
.1.3.6.1.2.1.169.1.1.33.1.6,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqMode,INTEGER,read-only,,current,firstModulatedBySecond(1):summation(2),This MIB object provides directive on the modulation or summation of the frequencies involved in the tone. It is to be noted that while summation can be done without any constraint on the number of frequencies, the modulation (amplitude) holds good only when there are two frequencies (first and second). Thus: - If the mode is set to a value of 'firstModulatedBySecond(1)', the first frequency MUST be modulated by the second, and the remaining frequencies (third and fourth) ignored. The percentage of amplitude modulation to be applied is defined by the MIB object pktcSigDevToneFreqAmpModePrtg. - If the mode is set to a value of 'summation(2)', all the frequencies MUST be summed without any modulation. 
.1.3.6.1.2.1.169.1.1.33.1.7,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqAmpModePrtg,Unsigned32,read-only,,current,,This MIB object represents the percentage of amplitude modulation applied to the second frequency when the MIB object pktcSigDevToneFreqMode is set to a value of 'firstModulatedBySecond (1)'. If the MIB object pktcSigDevToneFreqMode is set to value of 'summation (2)', then this MIB object MUST be ignored.
.1.3.6.1.2.1.169.1.1.33.1.8,PKTC-IETF-SIG-MIB::pktcSigDevToneDbLevel,Integer32,read-only,,current,,This MIB object contains the decibel level for each analog signal (tone) that is locally generated (versus in-band supervisory tones) and sourced to the a-b terminals (TE connection point). Each tone in itself may consist of multiple frequencies, as defined by the MIB table pktcSigDevMultiFreqToneTable. This MIB object reflects the desired level at the Telco (POTS) a-b (T/R) terminals, including the effect of any MTA receiver gain (loss). This is required so that locally generated tones are consistent with remotely generated in-band tones at the a-b terminals, consistent with user expectations. This MIB object must be set for each tone. When tones are formed by combining multi-frequencies, the level of each frequency shall be set so as to result in the tone level specified in this object at the a-b (T/R) terminals. The wide range of levels for this Object is required to provide signal-generator levels across the wide range of gains (losses) -- but does not imply the entire range is to be achievable given the range of gains (losses) in the MTA.
.1.3.6.1.2.1.169.1.1.33.1.9,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqOnDuration,Unsigned32,read-only,,current,,This MIB object represents the duration for which the frequency reference corresponding to the tone type is turned on.
.1.3.6.1.2.1.169.1.1.33.1.10,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqOffDuration,Unsigned32,read-only,,current,,This MIB object represents the duration for which the frequency reference corresponding to the tone type is turned off.
.1.3.6.1.2.1.169.1.1.33.1.11,PKTC-IETF-SIG-MIB::pktcSigDevToneFreqRepeatCount,Unsigned32,read-only,,current,,This MIB object indicates the number of times to repeat the cadence cycle represented by the on/off durations (refer to the MIB objects pktcSigDevToneFreqOnDuration and pktcSigDevToneFreqOffDuration). Setting this object may result in a tone duration that is longer or shorter than the overall signal duration specified by the time out (TO) object for the corresponding tone type. If the value of this MIB Object indicates a longer duration than that specified by the TO, the latter overrules the former, and the desired tone duration will be truncated according to the TO. However, if the repeat count results in a shorter tone duration than the signal duration specified by the TO, the tone duration defined by the repeat count takes precedence over the TO and will end the signal event. In this case, the TO represents a time not to be exceeded for the signal. It is recommended, to ensure proper telephony signaling, that the TO duration setting should always be longer than the desired repeat count-time duration. A value of zero means the tone sequence is to be played once but not repeated.
.1.3.6.1.2.1.169.1.1.34,PKTC-IETF-SIG-MIB::pktcSigDevCidDelayAfterLR,Unsigned32,read-write,,current,,This object specifies the delay between the end of the Line Reversal and the start of the FSK or DTMF signal. This MIB object is used only when pktcSigDevCidMode is set to a value of 'lrETS'. This timing has a range of 300 to 800 ms. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS any value (not used) dtAsETS any value (not used) rpAsETS any value (not used) lrAsETS any value (not used) lrETS 400 An attempt to set this object while the value of pktcSigDevCidMode is not set to a value of 'lrETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.35,PKTC-IETF-SIG-MIB::pktcSigDevCidDtmfStartCode,INTEGER,read-write,,current,dtmfcode0(0):dtmfcode1(1):dtmfcode2(2):dtmfcode3(3):dtmfcode4(4):dtmfcode5(5):dtmfcode6(6):dtmfcode7(7):dtmfcode8(8):dtmfcode9(9):dtmfcodeStar(10):dtmfcodeHash(11):dtmfcodeA(12):dtmfcodeB(13):dtmfcodeC(14):dtmfcodeD(15),This object identifies optional start codes used when the MIB object pktcSigDevCidSigProtocol is set to a value of 'dtmf(2)'. Different countries define different caller id signaling codes to support caller identification. When Dual-Tone Multi-Frequency (DTMF) is used, the caller id digits are preceded by a 'start code' digit, followed by the digit transmission sequence <S1>...<Sn> (where Sx represents the digits 0-9), and terminated by the 'end code' digit. For example, <A><S1>...<Sn> <D><S1>...<Sn> <B><S1>...<Sn> <C>. The start code for calling number delivery may be DTMF 'A' or 'D'. The start code for redirecting a number may be DTMF 'D'. The DTMF code 'B' may be sent by the network as a start code for the transfer of information values, through which special events can be indicated to the user. In some countries, the '*' or '#' may be used instead of 'A', 'B', 'C', or 'D'. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.36,PKTC-IETF-SIG-MIB::pktcSigDevCidDtmfEndCode,INTEGER,read-write,,current,dtmfcode0(0):dtmfcode1(1):dtmfcode2(2):dtmfcode3(3):dtmfcode4(4):dtmfcode5(5):dtmfcode6(6):dtmfcode7(7):dtmfcode8(8):dtmfcode9(9):dtmfcodeStar(10):dtmfcodeHash(11):dtmfcodeA(12):dtmfcodeB(13):dtmfcodeC(14):dtmfcodeD(15),This object identifies optional end codes used when the pktcSigDevCidSigProtocol is set to a value of 'dtmf(2)'. Different countries define different caller id signaling protocols to support caller identification. When Dual-Tone Multi-Frequency (DTMF) is used, the caller id digits are preceded by a 'start code' digit, followed by the digit transmission sequence <S1>...<Sn> (where Sx represents the digits 0-9), and terminated by the 'end code' digit. For example, <A><S1>...<Sn> <D><S1>...<Sn> <B><S1>...<Sn> <C>. The DTMF code 'C' may be sent by the network as an end code for the transfer of information values, through which special events can be indicated to the user. In some countries, the '*' or '#' may be used instead of 'A', 'B', 'C', or 'D'. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.37,PKTC-IETF-SIG-MIB::pktcSigDevVmwiSigProtocol,INTEGER,read-write,,current,fsk(1):dtmf(2),This object identifies the subscriber line protocol used for signaling the information on Visual Message Waiting Indicator (VMWI). Different countries define different VMWI signaling protocols to support VMWI service. Frequency shift keying (FSK) is most commonly used. DTMF is an alternative. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.38,PKTC-IETF-SIG-MIB::pktcSigDevVmwiDelayAfterLR,Unsigned32,read-write,,current,,This object specifies the delay between the end of the Line Reversal and the start of the FSK or DTMF signal. This object is only used when pktcSigDevVmwiMode is set to a value of 'lrETS'. This timing has a range of 300 to 800 ms. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevVmwiMode), and MUST be followed: Value of pktcSigDevVmwiMode Default value duringringingETS any value (not used) dtAsETS any value (not used) rpAsETS any value (not used) lrAsETS any value (not used) lrETS 400 An attempt to set this object while the value of pktcSigDevVmwiMode is not 'lrETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.39,PKTC-IETF-SIG-MIB::pktcSigDevVmwiDtmfStartCode,INTEGER,read-write,,current,dtmfcode0(0):dtmfcode1(1):dtmfcode2(2):dtmfcode3(3):dtmfcode4(4):dtmfcode5(5):dtmfcode6(6):dtmfcode7(7):dtmfcode8(8):dtmfcode9(9):dtmfcodeStar(10):dtmfcodeHash(11):dtmfcodeA(12):dtmfcodeB(13):dtmfcodeC(14):dtmfcodeD(15),This object identifies optional start codes used when the pktcSigDevVmwiSigProtocol is set to a value of 'dtmf(2)'. Different countries define different On Hook Data Transmission Protocol signaling codes to support VMWI. When Dual-Tone Multi-Frequency (DTMF) is used, the VMWI digits are preceded by a 'start code' digit, followed by the digit transmission sequence <S1>...<Sn> (where Sx represents the digits 0-9), and terminated by the 'end code' digit. For example, <A><S1>...<Sn> <D><S1>...<Sn> <B><S1>...<Sn> <C>. The start code for redirecting VMWI may be DTMF 'D' The DTMF code 'B' may be sent by the network as a start code for the transfer of information values, through which special events can be indicated to the user. In some countries, the '*' or '#' may be used instead of 'A', 'B', 'C', or 'D'. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.40,PKTC-IETF-SIG-MIB::pktcSigDevVmwiDtmfEndCode,INTEGER,read-write,,current,dtmfcode0(0):dtmfcode1(1):dtmfcode2(2):dtmfcode3(3):dtmfcode4(4):dtmfcode5(5):dtmfcode6(6):dtmfcode7(7):dtmfcode8(8):dtmfcode9(9):dtmfcodeStar(10):dtmfcodeHash(11):dtmfcodeA(12):dtmfcodeB(13):dtmfcodeC(14):dtmfcodeD(15),This object identifies an optional end code used when the pktcSigDevVmwiSigProtocol is set to a value of 'dtmf(2)'. Different countries define different on-hook Data Transmission Protocol signaling codes to support VMWI. When Dual-Tone Multi-Frequency (DTMF) is used, the VMWI digits are preceded by a 'start code' digit, followed by the digit transmission sequence <S1>...<Sn> (where Sx represents the digits 0-9), and terminated by the 'end code' digit. For example, <A><S1>...<Sn> <D><S1>...<Sn> <B><S1>...<Sn> <C>. The DTMF code 'C' may be sent by the network as an end code for the transfer of information values, through which special events can be indicated to the user. In some countries, the '*' or '#' may be used instead of 'A', 'B', 'C', or 'D'. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.1.41,PKTC-IETF-SIG-MIB::pktcSigDevrpAsDtsDuration,Unsigned32,read-write,,current,, This object specifies the duration of the rpASDTS ring pulse prior to the start of the transmission of the FSK or DTMF containing the caller id information. It is only used when pktcSigDevCidMode is set to a value of 'rpAsETS'. The following table defines the default values for this MIB object, depending on the signal type (pktcSigDevCidMode), and MUST be followed: Value of pktcSigDevCidMode Default value duringringingETS any value (not used) dtAsETS any value (not used) rpAsETS 250 lrAsETS any value (not used) lrETS any value (not used) An attempt to set this object while the value of pktcSigDevCidMode is not 'rpAsETS' will result in an 'inconsistentValue' error. The value of this MIB object MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.2,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigObjects,,,,,,
.1.3.6.1.2.1.169.1.2.1,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigTable,,not-accessible,,current,, This table describes the information pertaining to each endpoint of the MTA. All entries in this table represent the provisioned endpoints provisioned with the information required by the MTA to maintain the NCS protocol communication with the CMS. Each endpoint can be assigned to its own CMS. If the specific endpoint does not have the corresponding CMS information in this table, the endpoint is considered as not provisioned with voice services. Objects in this table do not persist across MTA reboots.
.1.3.6.1.2.1.169.1.2.1.1,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigEntry,,not-accessible,ifIndex,current,,Each entry in the pktcSigEndPntConfigTable represents required signaling parameters for the specific endpoint provisioned with voice services. The conceptual rows MUST NOT persist across MTA reboots.
.1.3.6.1.2.1.169.1.2.1.1.1,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigCallAgentId,OCTET,read-create,,current,, This object contains a string indicating the call agent name (e.g., ca@example.com). The call agent name, after the character '@', MUST be a fully qualified domain name (FQDN) and MUST have a corresponding pktcMtaDevCmsFqdn entry in the pktcMtaDevCmsTable. The object pktcMtaDevCmsFqdn is defined in the PacketCable MIBMTA Specification. For each particular endpoint, the MTA MUST use the current value of this object to communicate with the corresponding CMS. The MTA MUST update this object with the value of the 'Notified Entity' parameter of the NCS message. Because of the high importance of this object to the ability of the MTA to maintain reliable NCS communication with the CMS, it is highly recommended not to change this object's value using SNMP during normal operation.
.1.3.6.1.2.1.169.1.2.1.1.2,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigCallAgentUdpPort,Unsigned32,read-create,,current,, This object contains the current value of the User Datagram Protocol (UDP) receive port on which the call agent will receive NCS from the endpoint. For each particular endpoint, the MTA MUST use the current value of this object to communicate with the corresponding CMS. The MTA MUST update this object with the value of the 'Notified Entity' parameter of the NCS message. If the Notified Entity parameter does not contain a CallAgent port, the MTA MUST update this object with the default value of 2727. Because of the high importance of this object to the ability of the MTA to maintain reliable NCS communication with the CMS, it is highly recommended not to change this object's value using SNMP during normal operation.
.1.3.6.1.2.1.169.1.2.1.1.3,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigPartialDialTO,Unsigned32,read-create,,current,,This object contains the value of the partial dial time out. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.4,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigCriticalDialTO,Unsigned32,read-create,,current,,This object contains the value of the critical dial time out. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.5,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigBusyToneTO,Unsigned32,read-create,,current,, This object contains the default time out value for busy tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.6,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigDialToneTO,Unsigned32,read-create,,current,, This object contains the default time out value for dial tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.7,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMessageWaitingTO,Unsigned32,read-create,,current,, This object contains the default time out value for message waiting indicator. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.8,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigOffHookWarnToneTO,Unsigned32,read-create,,current,, This object contains the default time out value for the off-hook warning tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.9,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigRingingTO,Unsigned32,read-create,,current,, This object contains the default time out value for ringing. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.10,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigRingBackTO,Unsigned32,read-create,,current,, This object contains the default time out value for ring back. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.11,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigReorderToneTO,Unsigned32,read-create,,current,, This object contains the default time out value for reorder tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.12,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigStutterDialToneTO,Unsigned32,read-create,,current,, This object contains the default time out value for stutter dial tone. The MTA MUST NOT update this object with the value provided in the NCS message (if present). If the value of the object is modified by the SNMP Management Station, the MTA MUST use the new value as a default only for a new signal requested by the NCS message. The time out (TO) elements are intended to limit the time a tone or frequency is generated. When this MIB object is set to a value of '0', the MTA MUST NOT generate the corresponding frequency or tone, regardless of the definitions pertaining to frequency, tone duration, or cadence.
.1.3.6.1.2.1.169.1.2.1.1.13,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigTSMax,Unsigned32,read-create,,current,,This MIB object is used as part of an NCS retransmission algorithm. Prior to any retransmission, the MTA must check to make sure that the time elapsed since the sending of the initial datagram does not exceed the value specified by this MIB object. If more than Tsmax time has elapsed, then the retransmissions MUST cease. Refer to the MIB object pktcSigEndPntConfigThist for information on when the endpoint becomes disconnected.
.1.3.6.1.2.1.169.1.2.1.1.14,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMax1,Unsigned32,read-create,,current,,This object contains the suspicious error threshold for signaling messages. The pktcSigEndPntConfigMax1 object indicates the retransmission threshold at which the MTA MAY actively query the domain name server (DNS) in order to detect the possible change of call agent interfaces.
.1.3.6.1.2.1.169.1.2.1.1.15,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMax2,Unsigned32,read-create,,current,,This object contains the disconnect error threshold for signaling messages. The pktcSigEndPntConfigMax2 object indicates the retransmission threshold at which the MTA SHOULD contact the DNS one more time to see if any other interfaces to the call agent have become available.
.1.3.6.1.2.1.169.1.2.1.1.16,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMax1QEnable,INTEGER,read-create,,current,true(1):false(2),This object enables/disables the Max1 domain name server (DNS) query operation when the pktcSigEndPntConfigMax1 threshold has been reached. A value of true(1) indicates enabling, and a value of false(2) indicates disabling.
.1.3.6.1.2.1.169.1.2.1.1.17,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMax2QEnable,INTEGER,read-create,,current,true(1):false(2),This object enables/disables the Max2 domain name server (DNS) query operation when the pktcSigEndPntConfigMax2 threshold has been reached. A value of true(1) indicates enabling, and a value of false(2) indicates disabling.
.1.3.6.1.2.1.169.1.2.1.1.18,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMWD,Unsigned32,read-create,,current,,Maximum Waiting Delay (MWD) contains the maximum number of seconds an MTA waits, after powering on, before initiating the restart procedure with the call agent.
.1.3.6.1.2.1.169.1.2.1.1.19,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigTdinit,Unsigned32,read-create,,current,,This MIB object represents the 'disconnected' initial waiting delay within the context of an MTA's 'disconnected procedure'. The 'disconnected procedure' is initiated when an endpoint becomes 'disconnected' while attempting to communicate with a call agent. The 'disconnected timer' associated with the 'disconnected Procedure' is initialized to a random value, uniformly distributed between zero and the value contained in this MIB object. For more information on the usage of this timer, please refer to the PacketCable NCS Specification.
.1.3.6.1.2.1.169.1.2.1.1.20,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigTdmin,Unsigned32,read-create,,current,,This MIB object represents the 'disconnected' minimum waiting delay within the context of an MTA's 'disconnected procedure', specifically when local user activity is detected. The 'disconnected procedure' is initiated when an endpoint becomes 'disconnected' while attempting to communicate with a call agent. For more information on the usage of this timer, please refer to the PacketCable NCS Specification.
.1.3.6.1.2.1.169.1.2.1.1.21,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigTdmax,Unsigned32,read-create,,current,, This object contains the maximum number of seconds the MTA waits, after a disconnect, before initiating the disconnected procedure with the call agent. 
.1.3.6.1.2.1.169.1.2.1.1.22,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigRtoMax,Unsigned32,read-create,,current,,This object specifies the maximum number of seconds the MTA waits for a response to an NCS message before initiating a retransmission.
.1.3.6.1.2.1.169.1.2.1.1.23,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigRtoInit,Unsigned32,read-create,,current,, This object contains the initial number of seconds for the retransmission timer.
.1.3.6.1.2.1.169.1.2.1.1.24,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigLongDurationKeepAlive,Unsigned32,read-create,,current,, Specifies a time out value, in minutes, for sending long duration call notification messages.
.1.3.6.1.2.1.169.1.2.1.1.25,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigThist,Unsigned32,read-create,,current,, Time out period, in seconds, before no response is declared.
.1.3.6.1.2.1.169.1.2.1.1.26,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6), This object contains the Row Status associated with the pktcSigEndPntConfigTable. There are no restrictions or dependencies amidst the columnar objects before this row can be activated or for modifications of the columnar objects when this object is set to a value of 'active(1).
.1.3.6.1.2.1.169.1.2.1.1.27,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigCallWaitingMaxRep,Unsigned32,read-create,,current,, This object contains the default value of the maximum number of repetitions of the Call Waiting tone that the MTA will play from a single CMS request. The MTA MUST NOT update this object with the information provided in the NCS message (if present). If the value of the object is modified by the SNMP Manager application, the MTA MUST use the new value as a default only for a new signal requested by the NCS message.
.1.3.6.1.2.1.169.1.2.1.1.28,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigCallWaitingDelay,Unsigned32,read-create,,current,, This object contains the delay between repetitions of the Call Waiting tone that the MTA will play from a single CMS request.
.1.3.6.1.2.1.169.1.2.1.1.29,PKTC-IETF-SIG-MIB::pktcSigEndPntStatusCallIpAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16), This object contains the type of Internet address contained in the MIB object 'pktcSigEndPntStatusCallIpAddress'. Since pktcSigEndPntStatusCallIpAddress is expected to contain an IP address, a value of dns(16) is disallowed.
.1.3.6.1.2.1.169.1.2.1.1.30,PKTC-IETF-SIG-MIB::pktcSigEndPntStatusCallIpAddress,OCTET,read-only,,current,, This MIB object contains the chosen IP address of the CMS currently being used for the corresponding endpoint. The device determines the IP address by using DNS to resolve the IP address of the CMS from the FQDN stored in the MIB object 'pktcSigEndPntConfigCallAgentId'. The processes are outlined in the PacketCable NCS and Security specifications, and MUST be followed by the MTA. The IP address type contained in this MIB object is indicated by pktcSigEndPntStatusCallIpAddressType.
.1.3.6.1.2.1.169.1.2.1.1.31,PKTC-IETF-SIG-MIB::pktcSigEndPntStatusError,INTEGER,read-only,,current,operational(1):noSecurityAssociation(2):disconnected(3), This object contains the error status for this interface. The operational status indicates that all operations necessary to put the line in service have occurred, and the CMS has acknowledged the Restart In Progress (RSIP) message successfully. If pktcMtaDevCmsIpsecCtrl is enabled for the associated call agent, the noSecurityAssociation status indicates that no Security Association (SA) yet exists for this endpoint. If pktcMtaDevCmsIpsecCtrl is disabled for the associated call agent, the noSecurityAssociation status is not applicable and should not be used by the MTA. The disconnected status indicates one of the following two: If pktcMtaDevCmsIpsecCtrl is disabled, then no security association is involved with this endpoint. The NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange. Otherwise, when pktcMtaDevCmsIpsecCtrl is enabled, security Association has been established, and the NCS signaling software is in process of establishing the NCS signaling link via an RSIP exchange.
.1.3.6.1.2.1.169.1.2.1.1.32,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMinHookFlash,Unsigned32,read-only,,current,, This is the minimum time a line needs to be on-hook for a valid hook flash. The value of this object MUST be greater than the value of pktcSigEndPntConfigPulseDialMaxBreakTime. The value of pktcSigEndPntConfigMinHookFlash MUST be less than pktcSigEndPntConfigMaxHookFlash. This object MUST only be set via the MTA configuration during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be greater than the value contained by the MIB Object 'pktcSigEndPntConfigPulseDialMaxMakeTime'.
.1.3.6.1.2.1.169.1.2.1.1.33,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigMaxHookFlash,Unsigned32,read-only,,current,, This is the maximum time a line needs to be on-hook for a valid hook flash. The value of pktcSigEndPntConfigMaxHookFlash MUST be greater than pktcSigEndPntConfigMinHookFlash. This object MUST only be set via the MTA configuration during the provisioning process.
.1.3.6.1.2.1.169.1.2.1.1.34,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigPulseDialInterdigitTime,Unsigned32,read-only,,current,, This is the pulse dial inter-digit time out. This object MUST only be set via the MTA configuration during the provisioning process.
.1.3.6.1.2.1.169.1.2.1.1.35,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigPulseDialMinMakeTime,Unsigned32,read-only,,current,, This is the minimum make pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMinMakeTime MUST be less than pktcSigEndPntConfigPulseDialMaxMakeTime. This object MUST only be set via the MTA configuration during the provisioning process.
.1.3.6.1.2.1.169.1.2.1.1.36,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigPulseDialMaxMakeTime,Unsigned32,read-only,,current,, This is the maximum make pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMaxMakeTime MUST be greater than pktcSigEndPntConfigPulseDialMinMakeTime. This object MUST only be provided via the configuration file during the provisioning process. Furthermore, given the possibility for the 'pulse dial' and 'hook flash' to overlap, the value of this object MUST be less than the value contained by the MIB object pktcSigEndPntConfigMinHookFlash.
.1.3.6.1.2.1.169.1.2.1.1.37,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigPulseDialMinBreakTime,Unsigned32,read-only,,current,, This is the minimum break pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMinBreakTime MUST be less than pktcSigEndPntConfigPulseDialMaxBreakTime. This object must only be provided via the configuration file during the provisioning process.
.1.3.6.1.2.1.169.1.2.1.1.38,PKTC-IETF-SIG-MIB::pktcSigEndPntConfigPulseDialMaxBreakTime,Unsigned32,read-only,,current,, This is the maximum break pulse width for the dial pulse. The value of pktcSigEndPntConfigPulseDialMaxBreakTime MUST be greater than pktcSigEndPntConfigPulseDialMinBreakTime. This object MUST only be provided via the configuration file during the provisioning process.
.1.3.6.1.2.1.169.2,PKTC-IETF-SIG-MIB::pktcSigConformance,,,,,,
.1.3.6.1.2.1.169.2.1,PKTC-IETF-SIG-MIB::pktcSigCompliances,,,,,,
.1.3.6.1.2.1.169.2.1.1,PKTC-IETF-SIG-MIB::pktcSigBasicCompliance,,,,,, The compliance statement for MTAs that implement NCS signaling.
.1.3.6.1.2.1.169.2.2,PKTC-IETF-SIG-MIB::pktcSigGroups,,,,,,
.1.3.6.1.2.1.169.2.2.1,PKTC-IETF-SIG-MIB::pktcSigDeviceGroup,,,,,,Group of MIB objects containing signaling configuration information that is applicable per-device.
.1.3.6.1.2.1.169.2.2.2,PKTC-IETF-SIG-MIB::pktcSigEndpointGroup,,,,,,Group of MIB objects containing signaling configuration information that is applicable per-endpoint.
.1.3.6.1.2.1.169.2.2.3,PKTC-IETF-SIG-MIB::pktcInternationalGroup,,,,,, Group of objects that extend the behavior of existing objects to support operations in the widest possible set of international marketplaces. Note that many of these objects represent a superset of behaviors described in other objects within this MIB module.
.1.3.6.1.2.1.169.2.2.4,PKTC-IETF-SIG-MIB::pktcLLinePackageGroup,,,,,,Group of Objects to support the L line package.
.1.3.6.1.2.1.169.2.2.5,PKTC-IETF-SIG-MIB::pktcELinePackageGroup,,,,,,Group of Objects to support the E line package.
.1.3.6.1.2.1.170,UDPLITE-MIB::udpliteMIB,,,,,,The MIB module for managing UDP-Lite implementations. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5097; see the RFC itself for full legal notices.
.1.3.6.1.2.1.170.1,UDPLITE-MIB::udplite,,,,,,
.1.3.6.1.2.1.170.1.1,UDPLITE-MIB::udpliteInDatagrams,Counter64,read-only,,current,,The total number of UDP-Lite datagrams that were delivered to UDP-Lite users. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.2,UDPLITE-MIB::udpliteInPartialCov,Counter64,read-only,,current,,The total number of UDP-Lite datagrams that were delivered to UDP-Lite users (applications) and whose checksum coverage was strictly less than the datagram length. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.3,UDPLITE-MIB::udpliteNoPorts,Counter32,read-only,,current,,The total number of received UDP-Lite datagrams for which there was no listener at the destination port. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.4,UDPLITE-MIB::udpliteInErrors,Counter32,read-only,,current,,The number of received UDP-Lite datagrams that could not be delivered for reasons other than the lack of an application at the destination port. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.5,UDPLITE-MIB::udpliteInBadChecksum,Counter32,read-only,,current,,The number of received UDP-Lite datagrams whose checksum could not be validated. This includes illegal checksum coverage values, as their use would lead to incorrect checksums. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.6,UDPLITE-MIB::udpliteOutDatagrams,Counter64,read-only,,current,,The total number of UDP-Lite datagrams sent from this entity. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.7,UDPLITE-MIB::udpliteOutPartialCov,Counter64,read-only,,current,,The total number of udpliteOutDatagrams whose checksum coverage was strictly less than the datagram length. Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.8,UDPLITE-MIB::udpliteEndpointTable,,not-accessible,,current,,A table containing information about this entity's UDP-Lite endpoints on which a local application is currently accepting or sending datagrams. The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 'sockets' to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1). Like the udpTable in RFC 4113, this table also allows the representation of an application that completely specifies both local and remote addresses and ports. A listening application is represented in three possible ways: 1) An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a udpliteEndpointLocalAddressType of unknown(0) and a udpliteEndpointLocalAddress of ''h (a zero-length octet-string). 2) An application that is willing to accept only IPv4 or only IPv6 datagrams is represented by a udpliteEndpointLocalAddressType of the appropriate address type and a udpliteEndpointLocalAddress of '0.0.0.0' or '::' respectively. 3) An application that is listening for datagrams only for a specific IP address but from any remote system is represented by a udpliteEndpointLocalAddressType of the appropriate address type, with udpliteEndpointLocalAddress specifying the local address. In all cases where the remote address is a wildcard, the udpliteEndpointRemoteAddressType is unknown(0), the udpliteEndpointRemoteAddress is ''h (a zero-length octet-string), and the udpliteEndpointRemotePort is 0. If the operating system is demultiplexing UDP-Lite packets by remote address/port, or if the application has 'connected' the socket specifying a default remote address/port, the udpliteEndpointRemote* values should be used to reflect this.
.1.3.6.1.2.1.170.1.8.1,UDPLITE-MIB::udpliteEndpointEntry,,not-accessible,udpliteEndpointLocalAddressType:udpliteEndpointLocalAddress:udpliteEndpointLocalPort:udpliteEndpointRemoteAddressType:udpliteEndpointRemoteAddress:udpliteEndpointRemotePort:udpliteEndpointInstance,current,,Information about a particular current UDP-Lite endpoint. Implementers need to pay attention to the sizes of udpliteEndpointLocalAddress/RemoteAddress, as Object Identifiers (OIDs) of column instances in this table must have no more than 128 sub-identifiers in order to remain accessible with SNMPv1, SNMPv2c, and SNMPv3.
.1.3.6.1.2.1.170.1.8.1.1,UDPLITE-MIB::udpliteEndpointLocalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of udpliteEndpointLocalAddress. Only IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or unknown(0) if datagrams for all local IP addresses are accepted.
.1.3.6.1.2.1.170.1.8.1.2,UDPLITE-MIB::udpliteEndpointLocalAddress,OCTET,not-accessible,,current,,The local IP address for this UDP-Lite endpoint. The value of this object can be represented in three possible ways, depending on the characteristics of the listening application: 1. For an application that is willing to accept both IPv4 and IPv6 datagrams, the value of this object must be ''h (a zero-length octet-string), with the value of the corresponding instance of the EndpointLocalAddressType object being unknown(0). 2. For an application that is willing to accept only IPv4 or only IPv6 datagrams, the value of this object must be '0.0.0.0' or '::', respectively, while the corresponding instance of the EndpointLocalAddressType object represents the appropriate address type. 3. For an application that is listening for data destined only to a specific IP address, the value of this object is the specific IP address for which this node is receiving packets, with the corresponding instance of the EndpointLocalAddressType object representing the appropriate address type. As this object is used in the index for the udpliteEndpointTable, implementors should be careful not to create entries that would result in OIDs with more than 128 sub-identifiers; this is because of SNMP and SMI limitations.
.1.3.6.1.2.1.170.1.8.1.3,UDPLITE-MIB::udpliteEndpointLocalPort,Unsigned32,not-accessible,,current,,The local port number for this UDP-Lite endpoint.
.1.3.6.1.2.1.170.1.8.1.4,UDPLITE-MIB::udpliteEndpointRemoteAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of udpliteEndpointRemoteAddress. Only IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or unknown(0) if datagrams for all remote IP addresses are accepted. Also, note that some combinations of udpliteEndpointLocalAdressType and udpliteEndpointRemoteAddressType are not supported. In particular, if the value of this object is not unknown(0), it is expected to always refer to the same IP version as udpliteEndpointLocalAddressType.
.1.3.6.1.2.1.170.1.8.1.5,UDPLITE-MIB::udpliteEndpointRemoteAddress,OCTET,not-accessible,,current,,The remote IP address for this UDP-Lite endpoint. If datagrams from any remote system are to be accepted, this value is ''h (a zero-length octet-string). Otherwise, it has the type described by udpliteEndpointRemoteAddressType and is the address of the remote system from which datagrams are to be accepted (or to which all datagrams will be sent). As this object is used in the index for the udpliteEndpointTable, implementors should be careful not to create entries that would result in OIDs with more than 128 sub-identifiers; this is because of SNMP and SMI limitations.
.1.3.6.1.2.1.170.1.8.1.6,UDPLITE-MIB::udpliteEndpointRemotePort,Unsigned32,not-accessible,,current,,The remote port number for this UDP-Lite endpoint. If datagrams from any remote system are to be accepted, this value is zero.
.1.3.6.1.2.1.170.1.8.1.7,UDPLITE-MIB::udpliteEndpointInstance,Unsigned32,not-accessible,,current,,The instance of this tuple. This object is used to distinguish among multiple processes 'connected' to the same UDP-Lite endpoint. For example, on a system implementing the BSD sockets interface, this would be used to support the SO_REUSEADDR and SO_REUSEPORT socket options.
.1.3.6.1.2.1.170.1.8.1.8,UDPLITE-MIB::udpliteEndpointProcess,Unsigned32,read-only,,current,,A unique value corresponding to a piece of software running on this endpoint. If this endpoint is associated with more than one piece of software, the agent should choose one of these. As long as the representative piece of software is running and still associated with the endpoint, subsequent reads will consistently return the same value. The implementation may use any algorithm satisfying these constraints (e.g., choosing the entity with the oldest start time). This identifier is platform-specific. Wherever possible, it should use the system's native, unique identification number as the value. If the SYSAPPL-MIB module is available, the value should be the same as sysApplElmtRunIndex. If not available, an alternative should be used (e.g., the hrSWRunIndex of the HOST-RESOURCES-MIB module). If it is not possible to uniquely identify the pieces of software associated with this endpoint, then the value zero should be used. (Note that zero is otherwise a valid value for sysApplElmtRunIndex.)
.1.3.6.1.2.1.170.1.8.1.9,UDPLITE-MIB::udpliteEndpointMinCoverage,Unsigned32,read-only,,current,,The minimum checksum coverage expected by this endpoint. A value of 0 indicates that only fully covered datagrams are accepted.
.1.3.6.1.2.1.170.1.8.1.10,UDPLITE-MIB::udpliteEndpointViolCoverage,Counter32,read-only,,current,,The number of datagrams received by this endpoint whose checksum coverage violated the minimum coverage threshold set for this connection (i.e., all valid datagrams whose checksum coverage was strictly smaller than the minimum, as defined in RFC 3828). Discontinuities in the value of this counter can occur at re-initialisation of the management system, and at other times as indicated by the value of udpliteStatsDiscontinuityTime.
.1.3.6.1.2.1.170.1.9,UDPLITE-MIB::udpliteStatsDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent occasion at which one or more of the UDP-Lite counters suffered a discontinuity. A value of zero indicates no such discontinuity has occurred since the last re-initialisation of the local management subsystem.
.1.3.6.1.2.1.170.2,UDPLITE-MIB::udpliteMIBConformance,,,,,,
.1.3.6.1.2.1.170.2.1,UDPLITE-MIB::udpliteMIBCompliance,,,,,,The compliance statement for systems that implement UDP-Lite. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which we have the following compliance requirements, expressed in OBJECT clause form in this description clause: -- OBJECT udpliteEndpointLocalAddressType -- SYNTAX InetAddressType { unknown(0), ipv4(1), -- ipv6(2), ipv4z(3), -- ipv6z(4) } -- DESCRIPTION -- Support for dns(16) is not required. -- OBJECT udpliteEndpointLocalAddress -- SYNTAX InetAddress (SIZE(0|4|8|16|20)) -- DESCRIPTION -- Support is only required for zero-length -- octet-strings, and for scoped and unscoped -- IPv4 and IPv6 addresses. -- OBJECT udpliteEndpointRemoteAddressType -- SYNTAX InetAddressType { unknown(0), ipv4(1), -- ipv6(2), ipv4z(3), -- ipv6z(4) } -- DESCRIPTION -- Support for dns(16) is not required. -- OBJECT udpliteEndpointRemoteAddress -- SYNTAX InetAddress (SIZE(0|4|8|16|20)) -- DESCRIPTION -- Support is only required for zero-length -- octet-strings, and for scoped and unscoped -- IPv4 and IPv6 addresses. 
.1.3.6.1.2.1.170.2.2,UDPLITE-MIB::udpliteMIBGroups,,,,,,
.1.3.6.1.2.1.170.2.2.1,UDPLITE-MIB::udpliteBaseGroup,,,,,,The group of objects providing for counters of basic UDP-like statistics.
.1.3.6.1.2.1.170.2.2.2,UDPLITE-MIB::udplitePartialCsumGroup,,,,,,The group of objects providing for counters of transport layer statistics exclusive to UDP-Lite.
.1.3.6.1.2.1.170.2.2.3,UDPLITE-MIB::udpliteEndpointGroup,,,,,,The group of objects providing for the IP version independent management of UDP-Lite 'endpoints'.
.1.3.6.1.2.1.170.2.2.4,UDPLITE-MIB::udpliteAppGroup,,,,,,The group of objects that provide application-level information for the configuration management of UDP-Lite 'endpoints'.
.1.3.6.1.2.1.171,MIDCOM-MIB::midcomMIB,,,,,,This MIB module defines a set of basic objects for configuring middleboxes, such as firewalls and network address translators, in order to enable communication across these devices. Managed objects defined in this MIB module are structured in three kinds of objects: - transaction objects required according to the MIDCOM protocol requirements defined in RFC 3304 and according to the MIDCOM protocol semantics defined in RFC 3989, - configuration objects that can be used for retrieving or setting parameters of the implementation of transaction objects, - optional monitoring objects that provide information about used resource and statistics The transaction objects are organized in two subtrees: - objects modeling MIDCOM policy rules in the midcomRuleTable - objects modeling MIDCOM policy rule groups in the midcomGroupTable Note that typically, configuration objects are not intended to be written by MIDCOM clients. In general, write access to these objects needs to be restricted more strictly than write access to objects in the transaction subtrees. Copyright (C) The Internet Society (2008). This version of this MIB module is part of RFC 5190; see the RFC itself for full legal notices.
.1.3.6.1.2.1.171.0,MIDCOM-MIB::midcomNotifications,,,,,,
.1.3.6.1.2.1.171.0.1,MIDCOM-MIB::midcomUnsolicitedRuleEvent,,,,,,This notification is generated whenever the value of midcomRuleOperStatus enters any error state or any termination state without an explicit trigger by a MIDCOM client.
.1.3.6.1.2.1.171.0.2,MIDCOM-MIB::midcomSolicitedRuleEvent,,,,,,This notification is generated whenever the value of midcomRuleOperStatus enters one of the states {reserved, enabled, any error state, any termination state} as a result of a MIDCOM agent writing successfully to object midcomRuleAdminStatus. In addition, it is generated when the lifetime of a rule was changed by successfully writing to object midcomRuleLifetime.
.1.3.6.1.2.1.171.0.3,MIDCOM-MIB::midcomSolicitedGroupEvent,,,,,,This notification is generated for indicating that the lifetime of all member rules of the group was changed by successfully writing to object midcomGroupLifetime. Note that this notification is only sent if the lifetime of a group was changed by successfully writing to object midcomGroupLifetime. No notification is sent - if a group's lifetime is changed by writing to object midcomRuleLifetime of any of its member policies, - if a group's lifetime expires (in this case, notifications are sent for all member policies), or - if the group is terminated by terminating the last of its member policies without writing to object midcomGroupLifetime.
.1.3.6.1.2.1.171.1,MIDCOM-MIB::midcomObjects,,,,,,
.1.3.6.1.2.1.171.1.1,MIDCOM-MIB::midcomTransaction,,,,,,
.1.3.6.1.2.1.171.1.1.3,MIDCOM-MIB::midcomRuleTable,,not-accessible,,current,,This table lists policy rules. It is indexed by the midcomRuleOwner, the midcomGroupIndex, and the midcomRuleIndex. This implies that a rule is a member of exactly one group and that group membership cannot be changed. Entries can be deleted by writing to midcomGroupLifetime or midcomRuleLifetime and potentially also to midcomRuleStorageTime.
.1.3.6.1.2.1.171.1.1.3.1,MIDCOM-MIB::midcomRuleEntry,,not-accessible,midcomRuleOwner:midcomGroupIndex:midcomRuleIndex,current,,An entry describing a particular MIDCOM policy rule.
.1.3.6.1.2.1.171.1.1.3.1.1,MIDCOM-MIB::midcomRuleOwner,OCTET,not-accessible,,current,,The manager who owns this row in the midcomRuleTable. This object SHOULD uniquely identify an authenticated MIDCOM client. This object is part of the table index to allow for the use of the SNMPv3 View-based Access Control Model (VACM, RFC 3415).
.1.3.6.1.2.1.171.1.1.3.1.3,MIDCOM-MIB::midcomRuleIndex,Unsigned32,not-accessible,,current,,The value of this object must be unique in combination with the values of the objects midcomRuleOwner and midcomGroupIndex in this row.
.1.3.6.1.2.1.171.1.1.3.1.4,MIDCOM-MIB::midcomRuleAdminStatus,INTEGER,read-create,,current,reserve(1):enable(2):notSet(3),The value of this object indicates the desired status of the policy rule. See the definition of midcomRuleOperStatus for a description of the values. When a midcomRuleEntry is created without explicitly setting this object, its value will be notSet(3). However, a SET request can only set this object to either reserve(1) or enable(2). Attempts to set this object to notSet(3) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. When the midcomRuleAdminStatus object is set, then the MIDCOM-MIB implementation will try to read the respective relevant objects of the entry and try to achieve the corresponding midcomRuleOperStatus. Setting midcomRuleAdminStatus to value reserve(1) when object midcomRuleOperStatus has a value of reserved(7) does not have any effect on the policy rule. Setting midcomRuleAdminStatus to value enable(2) when object midcomRuleOperStatus has a value of enabled(8) does not have any effect on the policy rule. Depending on whether the midcomRuleAdminStatus is set to reserve(1) or enable(2), several objects must be set in advance. They serve as parameters of the policy rule to be established. When object midcomRuleAdminStatus is set to reserve(1), then the following objects in the same entry are of relevance: - midcomRuleInterface - midcomRuleTransportProtocol - midcomRulePortRange - midcomRuleInternalIpVersion - midcomRuleExternalIpVersion - midcomRuleInternalIpAddr - midcomRuleInternalIpPrefixLength - midcomRuleInternalPort - midcomRuleLifetime MIDCOM-MIB implementation may also consider the value of object midcomRuleMaxIdleTime when establishing a reserve rule. When object midcomRuleAdminStatus is set to enable(2), then the following objects in the same entry are of relevance: - midcomRuleInterface - midcomRuleFlowDirection - midcomRuleMaxIdleTime - midcomRuleTransportProtocol - midcomRulePortRange - midcomRuleInternalIpVersion - midcomRuleExternalIpVersion - midcomRuleInternalIpAddr - midcomRuleInternalIpPrefixLength - midcomRuleInternalPort - midcomRuleExternalIpAddr - midcomRuleExternalIpPrefixLength - midcomRuleExternalPort - midcomRuleLifetime When retrieved, the object returns the last set value. If no value has been set, it returns the default value notSet(3).
.1.3.6.1.2.1.171.1.1.3.1.5,MIDCOM-MIB::midcomRuleOperStatus,INTEGER,read-only,,current,newEntry(1):setting(2):checkingRequest(3):incorrectRequest(4):processingRequest(5):requestRejected(6):reserved(7):enabled(8):timedOut(9):terminatedOnRequest(10):terminated(11):genericError(12),The actual status of the policy rule. The midcomRuleOperStatus object may have the following values: - newEntry(1) indicates that the entry in the midcomRuleTable was created, but not modified yet. Such an entry needs to be filled with values specifying a request first. - setting(2) indicates that the entry has been already modified after generating it, but no request was made yet. - checkingRequest(3) indicates that midcomRuleAdminStatus has recently been set and that the MIDCOM-MIB implementation is currently checking the parameters of the request. This is a transient state. The value of this object will change to either incorrectRequest(4) or processingRequest(5) without any external interaction. A MIDCOM-MIB implementation MAY return this value while checking request parameters. - incorrectRequest(4) indicates that checking a request resulted in detecting an incorrect value in one of the objects containing request parameters. The failure reason is indicated by the value of midcomRuleError. - processingRequest(5) indicates that midcomRuleAdminStatus has recently been set and that the MIDCOM-MIB implementation is currently processing the request and trying to configure the middlebox accordingly. This is a transient state. The value of this object will change to either requestRejected(6), reserved(7), or enabled(8) without any external interaction. A MIDCOM-MIB implementation MAY return this value while processing a request. - requestRejected(6) indicates that a request to establish a policy rule specified by the entry was rejected. The reason for rejection is indicated by the value of midcomRuleError. - reserved(7) indicates that the entry describes an established policy reserve rule. These values of MidcomRuleEntry are meaningful for a reserved policy rule: - midcomRuleMaxIdleTime - midcomRuleInterface - midcomRuleTransportProtocol - midcomRulePortRange - midcomRuleInternalIpVersion - midcomRuleExternalIpVersion - midcomRuleInternalIpAddr - midcomRuleInternalIpPrefixLength - midcomRuleInternalPort - midcomRuleOutsideIpAddr - midcomRuleOutsidePort - midcomRuleLifetime - enabled(8) indicates that the entry describes an established policy enable rule. These values of MidcomRuleEntry are meaningful for an enabled policy rule: - midcomRuleFlowDirection - midcomRuleInterface - midcomRuleMaxIdleTime - midcomRuleTransportProtocol - midcomRulePortRange - midcomRuleInternalIpVersion - midcomRuleExternalIpVersion - midcomRuleInternalIpAddr - midcomRuleInternalIpPrefixLength - midcomRuleInternalPort - midcomRuleExternalIpAddr - midcomRuleExternalIpPrefixLength - midcomRuleExternalPort - midcomRuleInsideIpAddr - midcomRuleInsidePort - midcomRuleOutsideIpAddr - midcomRuleOutsidePort - midcomRuleLifetime - timedOut(9) indicates that the lifetime of a previously established policy rule has expired and that the policy rule is terminated for this reason. - terminatedOnRequest(10) indicates that a previously established policy rule was terminated by an SNMP manager setting the midcomRuleLifetime to 0 or setting midcomGroupLifetime to 0. - terminated(11) indicates that
.1.3.6.1.2.1.171.1.1.3.1.6,MIDCOM-MIB::midcomRuleStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),When retrieved, this object returns the storage type of the policy rule. Writing to this object can change the storage type of the particular row from volatile(2) to nonVolatile(3) or vice versa. Attempts to set this object to permanent will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If midcomRuleStorageType has the value permanent(4), then all objects in this row whose MAX-ACCESS value is read-create must be read-only.
.1.3.6.1.2.1.171.1.1.3.1.7,MIDCOM-MIB::midcomRuleStorageTime,Unsigned32,read-create,,current,,The value of this object specifies how long this row can exist in the midcomRuleTable after the midcomRuleOperStatus switched to a termination state or to an error state. This object returns the remaining time that the row may exist before it is aged out. After expiration or termination of the context, the value of this object ticks backwards. The entry in the midcomRuleTable is destroyed when the value reaches 0. The value of this object may be set in order to increase or reduce the remaining time that the row may exist. Setting the value to 0 will destroy this entry as soon as the midcomRuleOperStatus switched to a termination state or to an error state. Note that there is no guarantee that the row is stored as long as this object indicates. At any time, the MIDCOM- MIB implementation may decide to remove a row describing a terminated policy rule before the storage time of the corresponding row in the midcomRuleTable reaches the value of 0. In this case, the information stored in this row is not available anymore. If object midcomRuleStorageType indicates that the policy rule has the storage type permanent(4), then this object has a constant value of 4294967295.
.1.3.6.1.2.1.171.1.1.3.1.8,MIDCOM-MIB::midcomRuleError,OCTET,read-only,,current,,This object contains a descriptive error message if the transition into the operational status reserved(7) or enabled(8) failed. Implementations must reset the error message to a zero-length string when a new attempt to change the policy rule status to reserved(7) or enabled(8) is started. RECOMMENDED values to be returned in particular cases include - 'lack of IP addresses' - 'lack of port numbers' - 'lack of resources' - 'specified NAT interface does not exist' - 'specified NAT interface does not support NAT' - 'conflict with already existing policy rule' - 'no internal IP wildcarding allowed' - 'no external IP wildcarding allowed' The semantics of these error messages and the corresponding behavior of the MIDCOM-MIB implementation are specified in sections 2.3.9 and 2.3.10 of RFC 3989.
.1.3.6.1.2.1.171.1.1.3.1.9,MIDCOM-MIB::midcomRuleInterface,Integer32,read-create,,current,,This object indicates the IP interface for which enforcement of a policy rule is requested or performed, respectively. The interface is identified by its index in the ifTable (see IF-MIB in RFC 2863). If the object has a value of 0, then no particular interface is indicated. This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to request its preference concerning the interface at which it requests NAT service. The default value of 0 indicates that the manager does not have a preferred interface or does not have sufficient topology information for specifying one. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object indicates the interface at which NAT service for this rule is performed. If NAT service is not required for enforcing the policy rule, then the value of this object is 0. Also, if the MIDCOM-MIB implementation cannot indicate an interface, because it does not have this information or because NAT service is not offered at a particular single interface, then the value of the object is 0. Note that the index of a particular interface in the ifTable may change after a re-initialization of the middlebox, for example, after adding another interface to it. In such a case, the value of this object may change, but the interface referred to by the MIDCOM-MIB MUST still be the same. If, after a re-initialization of the middlebox, the interface referred to before re-initialization cannot be uniquely mapped anymore to a particular entry in the ifTable, then the value of object midcomRuleOperStatus of the same entry MUST be changed to terminated(11). If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.10,MIDCOM-MIB::midcomRuleFlowDirection,INTEGER,read-create,,current,inbound(1):outbound(2):biDirectional(3),This parameter specifies the direction of enabled communication, either inbound(1), outbound(2), or biDirectional(3). The semantics of this object depends on the protocol the rule relates to. If the rule is independent of the transport protocol (midcomRuleTransportProtocol has a value of 0) or if the transport protocol is UDP, then the value of midcomRuleFlowDirection indicates the direction of packets traversing the middlebox. In this case, value inbound(1) indicates that packets are traversing from outside to inside, value outbound(2) indicates that packets are traversing from inside to outside. For both values, inbound(1) and outbound(2) packets can traverse the middlebox only unidirectional. A bidirectional flow is indicated by value biDirectional(3). If the transport protocol is TCP, the packet flow is always bidirectional, but the value of midcomRuleFlowDirection indicates that: - inbound(1): bidirectional TCP packet flow. First packet, with TCP SYN flag set, must arrive at an outside interface of the middlebox. - outbound(2): bidirectional TCP packet flow. First packet, with TCP SYN flag set, must arrive at an inside interface of the middlebox. - biDirectional(3): bidirectional TCP packet flow. First packet, with TCP SYN flag set, may arrive at an inside or an outside interface of the middlebox. This object is used as input to a request for establishing a policy enable rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has a value of either newEntry(1), setting(2), or reserved(7), then this object can be written by a manager in order to specify a requested direction to be enabled by a policy rule. Writing to this object in any state other than newEntry(1), setting(2), or reserved(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value enabled(8), then this object indicates the enabled flow direction. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.11,MIDCOM-MIB::midcomRuleMaxIdleTime,Unsigned32,read-create,,current,,Maximum idle time of the policy rule in seconds. If no packet to which the policy rule applies passes the middlebox for the specified midcomRuleMaxIdleTime, then the policy rule enters the termination state timedOut(9). A value of 0 indicates that the policy does not require an individual idle time and that instead, a default idle time chosen by the middlebox is used. A value of 4294967295 ( = 2^32 - 1 ) indicates that the policy does not time out if it is idle. This object is used as input to a request for establishing a policy enable rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has a value of either newEntry(1), setting(2), or reserved(7), then this object can be written by a manager in order to specify a maximum idle time for the policy rule to be requested. Writing to this object in any state others than newEntry(1), setting(2), or reserved(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value enabled(8), then this object indicates the maximum idle time of the policy rule. Note that even if a maximum idle time greater than zero was requested, the middlebox may not be able to support maximum idle times and set the value of this object to zero when entering state enabled(8). If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.12,MIDCOM-MIB::midcomRuleTransportProtocol,Unsigned32,read-create,,current,,The transport protocol. Valid values for midcomRuleTransportProtocol other than zero are defined at: http://www.iana.org/assignments/protocol-numbers This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has a value of either newEntry(1) or setting(2), then this object can be written by a manager in order to specify a requested transport protocol. If translation of an IP address only is requested, then this object must have the default value 0. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object indicates which transport protocol is enforced by this policy rule. A value of 0 indicates a rule acting on IP addresses only. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.13,MIDCOM-MIB::midcomRulePortRange,INTEGER,read-create,,current,single(1):pair(2),The range of port numbers. This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. It is relevant to the operation of the MIDCOM-MIB implementation only if the value of object midcomTransportProtocol in the same entry has a value other than 0. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the requested size of the port range. With single(1) just a single port number is requested, with pair(2) a consecutive pair of port numbers is requested with the lower number being even. Requesting a consecutive pair of port numbers may be used by RTP [RFC3550] and may even be required to support older RTP applications. Writing to this object in any state other than newEntry(1), setting(2) or reserved(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8), then this object will have the value that it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.14,MIDCOM-MIB::midcomRuleInternalIpVersion,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),IP version of the internal address (A0) and the inside address (A1). Allowed values are ipv4(1), ipv6(2), ipv4z(3), and ipv6z(4). This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the IP version required at the inside of the middlebox. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object indicates the internal/inside IP version. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.15,MIDCOM-MIB::midcomRuleExternalIpVersion,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),IP version of the external address (A3) and the outside address (A2). Allowed values are ipv4(1) and ipv6(2). This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the IP version required at the outside of the middlebox. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object indicates the external/outside IP version. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7) or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.16,MIDCOM-MIB::midcomRuleInternalIpAddr,OCTET,read-create,,current,,The internal IP address (A0). This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the internal IP address for which a reserve policy rule or a enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object will have the value which it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7) or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.17,MIDCOM-MIB::midcomRuleInternalIpPrefixLength,Unsigned32,read-create,,current,,The prefix length of the internal IP address used for wildcarding. A value of 0 indicates a full wildcard; in this case, the value of midcomRuleInternalIpAddr is irrelevant. If midcomRuleInternalIpVersion has a value of ipv4(1), then a value > 31 indicates no wildcarding at all. If midcomRuleInternalIpVersion has a value of ipv4(2), then a value > 127 indicates no wildcarding at all. A MIDCOM-MIB implementation that does not support IP address wildcarding MUST implement this object as read-only with a value of 128. A MIDCOM that does not support wildcarding based on prefix length MAY restrict allowed values for this object to 0 and 128. This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the prefix length of the internal IP address for which a reserve policy rule or an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object will have the value which it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.18,MIDCOM-MIB::midcomRuleInternalPort,Unsigned32,read-create,,current,,The internal port number. A value of 0 is a wildcard. This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. It is relevant to the operation of the MIDCOM-MIB implementation only if the value of object midcomTransportProtocol in the same entry has a value other than 0. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the internal port number for which a reserve policy rule or an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1) or setting(2) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value reserved(7) or enabled(8), then this object will have the value that it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.19,MIDCOM-MIB::midcomRuleExternalIpAddr,OCTET,read-create,,current,,The external IP address (A3). This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1), setting(2), or reserved(7), then this object can be written by a manager in order to specify the external IP address for which an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1), setting(2), or reserved(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value enabled(8), then this object will have the value that it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.20,MIDCOM-MIB::midcomRuleExternalIpPrefixLength,Unsigned32,read-create,,current,,The prefix length of the external IP address used for wildcarding. A value of 0 indicates a full wildcard; in this case, the value of midcomRuleExternalIpAddr is irrelevant. If midcomRuleExternalIpVersion has a value of ipv4(1), then a value > 31 indicates no wildcarding at all. If midcomRuleExternalIpVersion has a value of ipv4(2), then a value > 127 indicates no wildcarding at all. A MIDCOM-MIB implementation that does not support IP address wildcarding MUST implement this object as read-only with a value of 128. A MIDCOM that does not support wildcarding based on prefix length MAY restrict allowed values for this object to 0 and 128. This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has the value newEntry(1), setting(2), or reserved(7), then this object can be written by a manager in order to specify the prefix length of the external IP address for which an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1), setting(2), or reserved(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value enabled(8), then this object will have the value that it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.21,MIDCOM-MIB::midcomRuleExternalPort,Unsigned32,read-create,,current,,The external port number. A value of 0 is a wildcard. This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. It is relevant to the operation of the MIDCOM-MIB implementation only if the value of object midcomTransportProtocol in the same entry has a value other than 0. If object midcomRuleOperStatus of the same entry has the value newEntry(1), setting(2) or reserved(7), then this object can be written by a manager in order to specify the external port number for which an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1), setting(2) or reserved(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has the value enabled(8), then this object will have the value which it had before the transition to this state. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7) or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.22,MIDCOM-MIB::midcomRuleInsideIpAddr,OCTET,read-only,,current,,The inside IP address at the middlebox (A1). The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
.1.3.6.1.2.1.171.1.1.3.1.23,MIDCOM-MIB::midcomRuleInsidePort,Unsigned32,read-only,,current,,The inside port number at the middlebox. A value of 0 is a wildcard. The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
.1.3.6.1.2.1.171.1.1.3.1.24,MIDCOM-MIB::midcomRuleOutsideIpAddr,OCTET,read-only,,current,,The outside IP address at the middlebox (A2). The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
.1.3.6.1.2.1.171.1.1.3.1.25,MIDCOM-MIB::midcomRuleOutsidePort,Unsigned32,read-only,,current,,The outside port number at the middlebox. A value of 0 is a wildcard. The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
.1.3.6.1.2.1.171.1.1.3.1.26,MIDCOM-MIB::midcomRuleLifetime,Unsigned32,read-create,,current,,The remaining lifetime in seconds of this policy rule. Lifetime of a policy rule starts when object midcomRuleOperStatus in the same entry enters either state reserved(7) or state enabled(8). This object is used as input to a request for establishing a policy rule as well as for indicating the properties of an established policy rule. If object midcomRuleOperStatus of the same entry has a value of either newEntry(1) or setting(2), then this object can be written by a manager in order to specify the requested lifetime of a policy rule to be established. If object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8), then this object indicates the (continuously decreasing) remaining lifetime of the established policy rule. Note that when entering state reserved(7) or enabled(8), the MIDCOM-MIB implementation can choose a lifetime shorter than the one requested. Unlike other parameters of the policy rule, this parameter can still be written in state reserved(7) and enabled(8). Writing to this object is processed by the MIDCOM-MIB implementation by choosing a lifetime value that is greater than 0 and less than or equal to the minimum of the requested value and the value specified by object midcomConfigMaxLifetime: 0 <= lt_granted <= MINIMUM(lt_requested, lt_maximum) where: - lt_granted is the actually granted lifetime by the MIDCOM-MIB implementation - lt_requested is the requested lifetime of the MIDCOM client - lt_maximum is the value of object midcomConfigMaxLifetime SNMP SET requests to this object may be rejected or the value of the object after an accepted SET operation may be less than the value that was contained in the SNMP SET request. Successfully writing a value of 0 terminates the policy rule. Note that after a policy rule is terminated, still the entry will exist as long as indicated by the value of midcomRuleStorageTime. Writing to this object in any state other than newEntry(1), setting(2), reserved(7), or enabled(7) will always fail with an 'inconsistentValue' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. If object midcomRuleOperStatus of the same entry has a value other than newEntry(1), setting(2), reserved(7), or enabled(8), then the value of this object is irrelevant.
.1.3.6.1.2.1.171.1.1.3.1.27,MIDCOM-MIB::midcomRuleRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),A control that allows entries to be added and removed from this table. Entries can also be removed from this table by setting objects midcomRuleLifetime and midcomRuleStorageTime of an entry to 0. Attempts to set a row notInService(2) where the value of the midcomRuleStorageType object is permanent(4) or readOnly(5) will result in an 'notWritable' error. Note that this error code is SNMP specific. If the MIB module is used with other protocols than SNMP, errors with similar semantics specific to those protocols should be returned. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.171.1.1.4,MIDCOM-MIB::midcomGroupTable,,not-accessible,,current,,This table lists all current policy rule groups. Entries in this table are created or removed implicitly when entries in the midcomRuleTable are created or removed, respectively. A group entry in this table only exists as long as there are member rules of this group in the midcomRuleTable. The table serves for listing the existing groups and their remaining lifetimes and for changing lifetimes of groups and implicitly of all group members. Groups and all their member policy rules can only be deleted by deleting all member policies in the midcomRuleTable. Setting midcomGroupLifetime will result in setting the lifetime of all policy members to the same value.
.1.3.6.1.2.1.171.1.1.4.1,MIDCOM-MIB::midcomGroupEntry,,not-accessible,midcomRuleOwner:midcomGroupIndex,current,,An entry describing properties of a particular MIDCOM policy rule group.
.1.3.6.1.2.1.171.1.1.4.1.2,MIDCOM-MIB::midcomGroupIndex,Unsigned32,not-accessible,,current,,The index of this group for the midcomRuleOwner. A group is identified by the combination of midcomRuleOwner and midcomGroupIndex. The value of this index must be unique per midcomRuleOwner.
.1.3.6.1.2.1.171.1.1.4.1.3,MIDCOM-MIB::midcomGroupLifetime,Unsigned32,read-write,,current,,When retrieved, this object delivers the maximum lifetime in seconds of all member rules of this group, i.e., of all rows in the midcomRuleTable that have the same values for midcomRuleOwner and midcomGroupIndex. Successfully writing to this object modifies the lifetime of all member policies. Successfully writing a value of 0 terminates all member policies and implicitly deletes the group as soon as all member entries are removed from the midcomRuleTable. Note that after a group's lifetime is expired or is set to 0, still the corresponding entry in the midcomGroupTable will exist as long as terminated member policy rules are stored as entries in the midcomRuleTable. Writing to this object is processed by the MIDCOM-MIB implementation by choosing a lifetime value that is greater than 0 and less than or equal to the minimum of the requested value and the value specified by object midcomConfigMaxLifetime: 0 <= lt_granted <= MINIMUM(lt_requested, lt_maximum) where: - lt_granted is the actually granted lifetime by the MIDCOM-MIB implementation - lt_requested is the requested lifetime of the MIDCOM client - lt_maximum is the value of object midcomConfigMaxLifetime SNMP SET requests to this object may be rejected or the value of the object after an accepted SET operation may be less than the value that was contained in the SNMP SET request.
.1.3.6.1.2.1.171.1.2,MIDCOM-MIB::midcomConfig,,,,,,
.1.3.6.1.2.1.171.1.2.1,MIDCOM-MIB::midcomConfigMaxLifetime,Unsigned32,read-write,,current,,When retrieved, this object returns the maximum lifetime, in seconds, that this middlebox allows policy rules to have.
.1.3.6.1.2.1.171.1.2.2,MIDCOM-MIB::midcomConfigPersistentRules,INTEGER,read-write,,current,true(1):false(2),When retrieved, this object returns true(1) if the MIDCOM-MIB implementation can store policy rules persistently. Otherwise, it returns false(2). A value of true(1) indicates that there may be entries in the midcomRuleTable with object midcomRuleStorageType set to value nonVolatile(3).
.1.3.6.1.2.1.171.1.2.3,MIDCOM-MIB::midcomConfigIfTable,,not-accessible,,current,,This table indicates capabilities of the MIDCOM-MIB implementation per IP interface. The table is indexed by the object midcomConfigIfIndex. For indexing a single interface, this object contains the value of the ifIndex object that is associated with the interface. If an entry with midcomConfigIfIndex = 0 occurs, then bits set in objects of this entry apply to all interfaces for which there is no entry in this table with the interface's index.
.1.3.6.1.2.1.171.1.2.3.1,MIDCOM-MIB::midcomConfigIfEntry,,not-accessible,midcomConfigIfIndex,current,,An entry describing the capabilities of a middlebox with respect to the indexed IP interface.
.1.3.6.1.2.1.171.1.2.3.1.1,MIDCOM-MIB::midcomConfigIfIndex,Integer32,not-accessible,,current,,The index of an entry in the midcomConfigIfTable. For values different from zero, this object identifies an IP interface by containing the same value as the ifIndex object associated with the interface. Note that the index of a particular interface in the ifTable may change after a re-initialization of the middlebox, for example, after adding another interface to it. In such a case, the value of this object may change, but the interface referred to by the MIDCOM-MIB MUST still be the same. If, after a re-initialization of the middlebox, the interface referred to before re-initialization cannot be uniquely mapped anymore to a particular entry in the ifTable, then the value of object midcomConfigIfEnabled of the same entry MUST be changed to false(2). If the object has a value of 0, then values specified by further objects of the same entry apply to all interfaces for which there is no explicit entry in the midcomConfigIfTable.
.1.3.6.1.2.1.171.1.2.3.1.2,MIDCOM-MIB::midcomConfigIfBits,BITS,read-only,,current,ipv4(0):ipv6(1):addressWildcards(2):portWildcards(3):firewall(4):nat(5):portTranslation(6):protocolTranslation(7):twiceNat(8):inside(9),When retrieved, this object returns a set of bits indicating the capabilities (or configuration) of the middlebox with respect to the referenced IP interface. If the index equals 0, then all set bits apply to all interfaces. If the ipv4(0) bit is set, then the middlebox supports IPv4 at the indexed IP interface. If the ipv6(1) bit is set, then the middlebox supports IPv6 at the indexed IP interface. If the addressWildcards(2) bit is set, then the middlebox supports IP address wildcarding at the indexed IP interface. If the portWildcards(3) bit is set, then the middlebox supports port wildcarding at the indexed IP interface. If the firewall(4) bit is set, then the middlebox offers firewall functionality at the indexed interface. If the nat(5) bit is set, then the middlebox offers network address translation service at the indexed interface. If the portTranslation(6) bit is set, then the middlebox offers port translation service at the indexed interface. This bit is only relevant if nat(5) is set. If the protocolTranslation(7) bit is set, then the middlebox offers protocol translation service between IPv4 and IPv6 at the indexed interface. This bit is only relevant if nat(5) is set. If the twiceNat(8) bit is set, then the middlebox offers twice network address translation service at the indexed interface. This bit is only relevant if nat(5) is set. If the inside(9) bit is set, then the indexed interface is an inside interface with respect to NAT functionality. Otherwise, it is an outside interface. This bit is only relevant if nat(5) is set. An SNMP agent supporting both the MIDCOM-MIB module and the NAT-MIB module SHOULD ensure that the value of this object is consistent with the values of corresponding objects in the NAT-MIB module.
.1.3.6.1.2.1.171.1.2.3.1.3,MIDCOM-MIB::midcomConfigIfEnabled,INTEGER,read-write,,current,true(1):false(2),The value of this object indicates the availability of the middlebox service described by midcomConfigIfBits at the indexed IP interface. By writing to this object, the MIDCOM support for the entire IP interface can be switched on or off. Setting this object to false(2) immediately stops middlebox support at the indexed IP interface. This implies that all policy rules that use NAT or firewall resources at the indexed IP interface are terminated immediately. In this case, the MIDCOM agent MUST send midcomUnsolicitedRuleEvent to all MIDCOM clients that have access to one of the terminated rules.
.1.3.6.1.2.1.171.1.2.4,MIDCOM-MIB::midcomConfigFirewallTable,,not-accessible,,current,,This table lists the firewall configuration per IP interface. It can be used for configuring how policy rules created by MIDCOM clients are realized as firewall rules of a firewall implementation. Particularly, the priority used for MIDCOM policy rules can be configured. For a single firewall implementation at a particular IP interface, all MIDCOM policy rules are realized as firewall rules with the same priority. Also, a firewall rule group name can be configured. The table is indexed by the object midcomConfigFirewallIndex. For indexing a single interface, this object contains the value of the ifIndex object that is associated with the interface. If an entry with midcomConfigFirewallIndex = 0 occurs, then bits set in objects of this entry apply to all interfaces for which there is no entry in this table for the interface's index.
.1.3.6.1.2.1.171.1.2.4.1,MIDCOM-MIB::midcomConfigFirewallEntry,,not-accessible,midcomConfigFirewallIndex,current,,An entry describing a particular set of firewall resources.
.1.3.6.1.2.1.171.1.2.4.1.1,MIDCOM-MIB::midcomConfigFirewallIndex,Integer32,not-accessible,,current,,The index of an entry in the midcomConfigFirewallTable. For values different from 0, this object identifies an IP interface by containing the same value as the ifIndex object associated with the interface. Note that the index of a particular interface in the ifTable may change after a re-initialization of the middlebox, for example, after adding another interface to it. In such a case, the value of this object may change, but the interface referred to by the MIDCOM-MIB MUST still be the same. If, after a re-initialization of the middlebox, the interface referred to before re-initialization cannot be uniquely mapped anymore to a particular entry in the ifTable, then the entry in the midcomConfigFirewallTable MUST be deleted. If the object has a value of 0, then values specified by further objects of the same entry apply to all interfaces for which there is no explicit entry in the midcomConfigFirewallTable.
.1.3.6.1.2.1.171.1.2.4.1.2,MIDCOM-MIB::midcomConfigFirewallGroupId,OCTET,read-write,,current,,The firewall rule group to which all firewall rules are assigned that the MIDCOM server creates for the interface indicated by object midcomConfigFirewallIndex. If the value of object midcomConfigFirewallIndex is 0, then all firewall rules of the MIDCOM server that are created for interfaces with no specific entry in the midcomConfigFirewallTable are assigned to the firewall rule group indicated by the value of this object.
.1.3.6.1.2.1.171.1.2.4.1.3,MIDCOM-MIB::midcomConfigFirewallPriority,Unsigned32,read-write,,current,,The priority assigned to all firewall rules that the MIDCOM server creates for the interface indicated by object midcomConfigFirewallIndex. If the value of object midcomConfigFirewallIndex is 0, then this priority is assigned to all firewall rules of the MIDCOM server that are created for interfaces for which there is no specific entry in the midcomConfigFirewallTable.
.1.3.6.1.2.1.171.1.3,MIDCOM-MIB::midcomMonitoring,,,,,,
.1.3.6.1.2.1.171.1.3.1,MIDCOM-MIB::midcomResourceTable,,not-accessible,,current,,This table lists all used middlebox resources per MIDCOM policy rule. The midcomResourceTable augments the midcomRuleTable.
.1.3.6.1.2.1.171.1.3.1.1,MIDCOM-MIB::midcomResourceEntry,,not-accessible,,current,,An entry describing a particular set of middlebox resources.
.1.3.6.1.2.1.171.1.3.1.1.4,MIDCOM-MIB::midcomRscNatInternalAddrBindMode,INTEGER,read-only,,current,addressBind(1):addressPortBind(2):none(3),An indication of whether this policy rule uses an address NAT bind or an address-port NAT bind for binding the internal address. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008) then object midcomRscNatInternalAddrBindMode contains the same value as the corresponding object natSessionPrivateSrcEPBindMode of the NAT-MIB module.
.1.3.6.1.2.1.171.1.3.1.1.5,MIDCOM-MIB::midcomRscNatInternalAddrBindId,Unsigned32,read-only,,current,,This object references to the allocated internal NAT bind that is used by this policy rule. A NAT bind describes the mapping of internal addresses to outside addresses. MIDCOM-MIB implementations can read this object to learn the corresponding NAT bind resource for this particular policy rule. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008) then object midcomRscNatInternalAddrBindId contains the same value as the corresponding object natSessionPrivateSrcEPBindId of the NAT-MIB module.
.1.3.6.1.2.1.171.1.3.1.1.6,MIDCOM-MIB::midcomRscNatInsideAddrBindMode,INTEGER,read-only,,current,addressBind(1):addressPortBind(2):none(3),An indication of whether this policy rule uses an address NAT bind or an address-port NAT bind for binding the external address. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008), then object midcomRscNatInsideAddrBindMode contains the same value as the corresponding object natSessionPrivateDstEPBindMode of the NAT-MIB module.
.1.3.6.1.2.1.171.1.3.1.1.7,MIDCOM-MIB::midcomRscNatInsideAddrBindId,Unsigned32,read-only,,current,,This object refers to the allocated external NAT bind that is used by this policy rule. A NAT bind describes the mapping of external addresses to inside addresses. MIDCOM-MIB implementations can read this object to learn the corresponding NAT bind resource for this particular policy rule. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008), then object midcomRscNatInsideAddrBindId contains the same value as the corresponding object natSessionPrivateDstEPBindId of the NAT-MIB module.
.1.3.6.1.2.1.171.1.3.1.1.8,MIDCOM-MIB::midcomRscNatSessionId1,Unsigned32,read-only,,current,,This object refers to the first allocated NAT session for this policy rule. MIDCOM-MIB implementations can read this object to learn whether or not a NAT session for a particular policy rule is used. A value of 0 means that no NAT session is allocated for this policy rule. A value other than 0 refers to the NAT session.
.1.3.6.1.2.1.171.1.3.1.1.9,MIDCOM-MIB::midcomRscNatSessionId2,Unsigned32,read-only,,current,,This object refers to the second allocated NAT session for this policy rule. MIDCOM-MIB implementations can read this object to learn whether or not a NAT session for a particular policy rule is used. A value of 0 means that no NAT session is allocated for this policy rule. A value other than 0 refers to the NAT session.
.1.3.6.1.2.1.171.1.3.1.1.10,MIDCOM-MIB::midcomRscFirewallRuleId,Unsigned32,read-only,,current,,This object refers to the allocated firewall rule in the firewall engine for this policy rule. MIDCOM-MIB implementations can read this value to learn whether a firewall rule for this particular policy rule is used or not. A value of 0 means that no firewall rule is allocated for this policy rule. A value other than 0 refers to the firewall rule number within the firewall engine.
.1.3.6.1.2.1.171.1.3.2,MIDCOM-MIB::midcomStatistics,,,,,,
.1.3.6.1.2.1.171.1.3.2.1,MIDCOM-MIB::midcomCurrentOwners,Gauge32,read-only,,current,,The number of different values for midcomRuleOwner for all current entries in the midcomRuleTable.
.1.3.6.1.2.1.171.1.3.2.2,MIDCOM-MIB::midcomTotalRejectedRuleEntries,Counter32,read-only,,current,,The total number of failed attempts to create an entry in the midcomRuleTable.
.1.3.6.1.2.1.171.1.3.2.3,MIDCOM-MIB::midcomCurrentRulesIncomplete,Gauge32,read-only,,current,,The current number of policy rules that are incomplete. Policy rules are loaded via row entries in the midcomRuleTable. This object counts policy rules that are loaded but not fully specified, i.e., they are in state newEntry(1) or setting(2).
.1.3.6.1.2.1.171.1.3.2.4,MIDCOM-MIB::midcomTotalIncorrectReserveRules,Counter32,read-only,,current,,The total number of policy reserve rules that failed parameter check and entered state incorrectRequest(4).
.1.3.6.1.2.1.171.1.3.2.5,MIDCOM-MIB::midcomTotalRejectedReserveRules,Counter32,read-only,,current,,The total number of policy reserve rules that failed while being processed and entered state requestRejected(6).
.1.3.6.1.2.1.171.1.3.2.6,MIDCOM-MIB::midcomCurrentActiveReserveRules,Gauge32,read-only,,current,,The number of currently active policy reserve rules.
.1.3.6.1.2.1.171.1.3.2.7,MIDCOM-MIB::midcomTotalExpiredReserveRules,Counter32,read-only,,current,,The total number of expired policy reserve rules (entered termination state timedOut(9)).
.1.3.6.1.2.1.171.1.3.2.8,MIDCOM-MIB::midcomTotalTerminatedOnRqReserveRules,Counter32,read-only,,current,,The total number of policy reserve rules that were terminated on request (entered termination state terminatedOnRequest(10)).
.1.3.6.1.2.1.171.1.3.2.9,MIDCOM-MIB::midcomTotalTerminatedReserveRules,Counter32,read-only,,current,,The total number of policy reserve rules that were terminated, but not on request (entered termination state terminated(11)).
.1.3.6.1.2.1.171.1.3.2.10,MIDCOM-MIB::midcomTotalIncorrectEnableRules,Counter32,read-only,,current,,The total number of policy enable rules that failed parameter check and entered state incorrectRequest(4).
.1.3.6.1.2.1.171.1.3.2.11,MIDCOM-MIB::midcomTotalRejectedEnableRules,Counter32,read-only,,current,,The total number of policy enable rules that failed while being processed and entered state requestRejected(6).
.1.3.6.1.2.1.171.1.3.2.12,MIDCOM-MIB::midcomCurrentActiveEnableRules,Gauge32,read-only,,current,,The number of currently active policy enable rules.
.1.3.6.1.2.1.171.1.3.2.13,MIDCOM-MIB::midcomTotalExpiredEnableRules,Counter32,read-only,,current,,The total number of expired policy enable rules (entered termination state timedOut(9)).
.1.3.6.1.2.1.171.1.3.2.14,MIDCOM-MIB::midcomTotalTerminatedOnRqEnableRules,Counter32,read-only,,current,,The total number of policy enable rules that were terminated on request (entered termination state terminatedOnRequest(10)).
.1.3.6.1.2.1.171.1.3.2.15,MIDCOM-MIB::midcomTotalTerminatedEnableRules,Counter32,read-only,,current,,The total number of policy enable rules that were terminated, but not on request (entered termination state terminated(11)).
.1.3.6.1.2.1.171.2,MIDCOM-MIB::midcomConformance,,,,,,
.1.3.6.1.2.1.171.2.1,MIDCOM-MIB::midcomCompliances,,,,,,
.1.3.6.1.2.1.171.2.1.1,MIDCOM-MIB::midcomCompliance,,,,,,The compliance statement for implementations of the MIDCOM-MIB module. Note that compliance with this compliance statement requires compliance with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB [RFC2863].
.1.3.6.1.2.1.171.2.2,MIDCOM-MIB::midcomGroups,,,,,,
.1.3.6.1.2.1.171.2.2.1,MIDCOM-MIB::midcomRuleGroup,,,,,,A collection of objects providing information about policy rules and policy rule groups.
.1.3.6.1.2.1.171.2.2.2,MIDCOM-MIB::midcomCapabilitiesGroup,,,,,,A collection of objects providing information about the capabilities of a middlebox.
.1.3.6.1.2.1.171.2.2.3,MIDCOM-MIB::midcomConfigFirewallGroup,,,,,,A collection of objects providing information about the firewall rule group and firewall rule priority to be used by firewalls loaded through MIDCOM.
.1.3.6.1.2.1.171.2.2.4,MIDCOM-MIB::midcomResourceGroup,,,,,,A collection of objects providing information about the used NAT and firewall resources.
.1.3.6.1.2.1.171.2.2.5,MIDCOM-MIB::midcomStatisticsGroup,,,,,,A collection of objects providing statistical information about the MIDCOM server.
.1.3.6.1.2.1.171.2.2.6,MIDCOM-MIB::midcomNotificationsGroup,,,,,,The notifications emitted by the midcomMIB.
.1.3.6.1.2.1.172,PIM-BSR-MIB::pimBsrMIB,,,,,,The MIB module for management of the Bootstrap Router (BSR) mechanism for PIM routers. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5240; see the RFC itself for full legal notices.
.1.3.6.1.2.1.172.0,PIM-BSR-MIB::pimBsrNotifications,,,,,,
.1.3.6.1.2.1.172.0.1,PIM-BSR-MIB::pimBsrElectedBSRLostElection,,,,,,A pimBsrElectedBSRLostElection notification should be generated when current E-BSR lost election to a new Candidate-BSR. Only an E-BSR should generate this notification. This notification is generated when pimBsrCandidateBSRElectedBSR becomes FALSE.
.1.3.6.1.2.1.172.0.2,PIM-BSR-MIB::pimBsrCandidateBSRWinElection,,,,,,A pimBsrCandidateBSRWinElection notification should be generated when a C-BSR wins BSR Election. Only an E-BSR should generate this notification. This notification is generated when pimBsrCandidateBSRElectedBSR becomes TRUE.
.1.3.6.1.2.1.172.1,PIM-BSR-MIB::pimBsrObjects,,,,,,
.1.3.6.1.2.1.172.1.1,PIM-BSR-MIB::pimBsrCandidateRPTable,,not-accessible,,current,,The (conceptual) table listing the IP multicast group prefixes for which the local router is to advertise itself as a Candidate-RP.
.1.3.6.1.2.1.172.1.1.1,PIM-BSR-MIB::pimBsrCandidateRPEntry,,not-accessible,pimBsrCandidateRPAddressType:pimBsrCandidateRPAddress:pimBsrCandidateRPGroupAddress:pimBsrCandidateRPGroupPrefixLength,current,,An entry (conceptual row) in the pimBsrCandidateRPTable.
.1.3.6.1.2.1.172.1.1.1.1,PIM-BSR-MIB::pimBsrCandidateRPAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The Inet address type of the Candidate-RP.
.1.3.6.1.2.1.172.1.1.1.2,PIM-BSR-MIB::pimBsrCandidateRPAddress,OCTET,not-accessible,,current,,The (unicast) address that will be advertised as a Candidate-RP. The InetAddressType is given by the pimBsrCandidateRPAddressType object.
.1.3.6.1.2.1.172.1.1.1.3,PIM-BSR-MIB::pimBsrCandidateRPGroupAddress,OCTET,not-accessible,,current,,The IP multicast group address that, when combined with the corresponding value of pimBsrCandidateRPGroupPrefixLength, identifies a group prefix for which the local router will advertise itself as a Candidate-RP. The InetAddressType is given by the pimBsrCandidateRPAddressType object. This address object is only significant up to pimBsrCandidateRPGroupPrefixLength bits. The remainder of the address bits are zero. This is especially important for this field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry.
.1.3.6.1.2.1.172.1.1.1.4,PIM-BSR-MIB::pimBsrCandidateRPGroupPrefixLength,Unsigned32,not-accessible,,current,,The multicast group address mask that, when combined with the corresponding value of pimBsrCandidateRPGroupAddress, identifies a group prefix for which the local router will advertise itself as a Candidate-RP. The InetAddressType is given by the pimBsrCandidateRPAddressType object.
.1.3.6.1.2.1.172.1.1.1.5,PIM-BSR-MIB::pimBsrCandidateRPBidir,INTEGER,read-create,,current,true(1):false(2),If this object is set to TRUE, this group range is advertised with this RP as a BIDIR-PIM group range. If it is set to FALSE, it is advertised as a PIM-SM group range.
.1.3.6.1.2.1.172.1.1.1.6,PIM-BSR-MIB::pimBsrCandidateRPAdvTimer,TimeTicks,read-only,,current,,The time remaining before the local router next sends a Candidate-RP-Advertisement to the elected BSR for this zone.
.1.3.6.1.2.1.172.1.1.1.7,PIM-BSR-MIB::pimBsrCandidateRPPriority,Unsigned32,read-create,,current,,The priority for this Candidate-RP advertised in Candidate-RP-Advertisements.
.1.3.6.1.2.1.172.1.1.1.8,PIM-BSR-MIB::pimBsrCandidateRPAdvInterval,Unsigned32,read-create,,current,,A Candidate-RP generates Candidate-RP-Advertisements periodically. This object represents the time interval in seconds between two consecutive advertisements.
.1.3.6.1.2.1.172.1.1.1.9,PIM-BSR-MIB::pimBsrCandidateRPHoldtime,Unsigned32,read-create,,current,,Holdtime for this Candidate-RP. The amount of time (in seconds) this Candidate-RP entry is valid. This object's value can be zero only when this C-RP is shutting down.
.1.3.6.1.2.1.172.1.1.1.10,PIM-BSR-MIB::pimBsrCandidateRPStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table. This status object can be set to active(1) without setting any other columnar objects in this entry. All writable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.172.1.1.1.11,PIM-BSR-MIB::pimBsrCandidateRPStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.172.1.2,PIM-BSR-MIB::pimBsrElectedBSRRPSetTable,,not-accessible,,current,,The (conceptual) table listing BSR-specific information about PIM group mappings learned via C-RP advertisements or created locally using configurations. This table is maintained only on the Elected BSR. An Elected BSR uses this table to create Bootstrap messages after applying a local policy to include some or all of the group mappings in this table.
.1.3.6.1.2.1.172.1.2.1,PIM-BSR-MIB::pimBsrElectedBSRRPSetEntry,,not-accessible,pimBsrElectedBSRGrpMappingAddrType:pimBsrElectedBSRGrpMappingGrpAddr:pimBsrElectedBSRGrpMappingGrpPrefixLen:pimBsrElectedBSRGrpMappingRPAddr,current,,An entry (conceptual row) in the pimBsrElectedBSRRPSetTable.
.1.3.6.1.2.1.172.1.2.1.2,PIM-BSR-MIB::pimBsrElectedBSRGrpMappingAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The Inet address type of the IP multicast group prefix.
.1.3.6.1.2.1.172.1.2.1.3,PIM-BSR-MIB::pimBsrElectedBSRGrpMappingGrpAddr,OCTET,not-accessible,,current,,The IP multicast group address that, when combined with pimBsrElectedBSRGrpMappingGrpPrefixLen, gives the group prefix for this mapping. The InetAddressType is given by the pimBsrElectedBSRGrpMappingAddrType object. This address object is only significant up to pimBsrElectedBSRGrpMappingGrpPrefixLen bits. The remainder of the address bits are zero. This is especially important for this field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry.
.1.3.6.1.2.1.172.1.2.1.4,PIM-BSR-MIB::pimBsrElectedBSRGrpMappingGrpPrefixLen,Unsigned32,not-accessible,,current,,The multicast group prefix length that, when combined with pimBsrElectedBSRGrpMappingGrpAddr, gives the group prefix for this mapping. The InetAddressType is given by the pimBsrElectedBSRGrpMappingAddrType object. If pimBsrElectedBSRGrpMappingAddrType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If pimBsrElectedBSRGrpMappingAddrType is 'ipv6' or 'ipv6z', this object must be in the range 8..128.
.1.3.6.1.2.1.172.1.2.1.5,PIM-BSR-MIB::pimBsrElectedBSRGrpMappingRPAddr,OCTET,not-accessible,,current,,The IP address of the RP to be used for groups within this group prefix. The InetAddressType is given by the pimBsrElectedBSRGrpMappingAddrType object.
.1.3.6.1.2.1.172.1.2.1.6,PIM-BSR-MIB::pimBsrElectedBSRRPSetPriority,Unsigned32,read-only,,current,,The priority for RP. Numerically higher values for this object indicate lower priorities, with the value zero denoting the highest priority.
.1.3.6.1.2.1.172.1.2.1.7,PIM-BSR-MIB::pimBsrElectedBSRRPSetHoldtime,Unsigned32,read-only,,current,,The holdtime for RP
.1.3.6.1.2.1.172.1.2.1.8,PIM-BSR-MIB::pimBsrElectedBSRRPSetExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before this entry will be aged out. The value zero indicates that this entry will never be aged out.
.1.3.6.1.2.1.172.1.2.1.9,PIM-BSR-MIB::pimBsrElectedBSRRPSetGrpBidir,INTEGER,read-only,,current,true(1):false(2),If this object is TRUE, this group range with this RP is a BIDIR-PIM group range. If it is set to FALSE, it is a PIM-SM group range.
.1.3.6.1.2.1.172.1.3,PIM-BSR-MIB::pimBsrCandidateBSRTable,,not-accessible,,current,,The (conceptual) table containing Candidate-BSR configuration for the local router. The table contains one row for each zone for which the local router is to advertise itself as a Candidate-BSR.
.1.3.6.1.2.1.172.1.3.1,PIM-BSR-MIB::pimBsrCandidateBSREntry,,not-accessible,pimBsrCandidateBSRZoneIndex,current,,An entry (conceptual row) in the pimBsrCandidateBSRTable.
.1.3.6.1.2.1.172.1.3.1.1,PIM-BSR-MIB::pimBsrCandidateBSRZoneIndex,Unsigned32,not-accessible,,current,,The zone index uniquely identifies the zone on a device to which this Candidate-BSR is attached. There is one entry for each zone in ipMcastZoneTable. Scope-level information for this zone can be extracted from ipMcastZoneTable in IP Multicast MIB [RFC5132]. Zero is a special value used to request the default zone for a given scope. Zero is not a valid value for this object.
.1.3.6.1.2.1.172.1.3.1.2,PIM-BSR-MIB::pimBsrCandidateBSRAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the Candidate-BSR.
.1.3.6.1.2.1.172.1.3.1.3,PIM-BSR-MIB::pimBsrCandidateBSRAddress,OCTET,read-create,,current,,The (unicast) address that the local router will use to advertise itself as a Candidate-BSR. The InetAddressType is given by the pimBsrCandidateBSRAddressType object.
.1.3.6.1.2.1.172.1.3.1.4,PIM-BSR-MIB::pimBsrCandidateBSRPriority,Unsigned32,read-create,,current,,The priority value for the local router as a Candidate-BSR for this zone. Numerically higher values for this object indicate higher priorities.
.1.3.6.1.2.1.172.1.3.1.5,PIM-BSR-MIB::pimBsrCandidateBSRHashMaskLength,Unsigned32,read-create,,current,,The hash mask length (used in the RP hash function) that the local router will advertise in its Bootstrap messages for this zone. This object defaults to 30 if pimBsrCandidateBSRAddressType is 'ipv4' or 'ipv4z' , and defaults to 126 if pimBsrCandidateBSRAddressType is 'ipv6' or 'ipv6z'.
.1.3.6.1.2.1.172.1.3.1.6,PIM-BSR-MIB::pimBsrCandidateBSRElectedBSR,INTEGER,read-only,,current,true(1):false(2),Whether the local router is the elected BSR for this zone.
.1.3.6.1.2.1.172.1.3.1.7,PIM-BSR-MIB::pimBsrCandidateBSRBootstrapTimer,TimeTicks,read-only,,current,,The time remaining before the local router next originates a Bootstrap message for this zone. Value of this object is zero if pimBsrCandidateBSRElectedBSR is 'FALSE'.
.1.3.6.1.2.1.172.1.3.1.8,PIM-BSR-MIB::pimBsrCandidateBSRStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created or old entries deleted from this table. This status object can be set to active(1) without setting any other columnar objects in this entry. All writable objects in this entry can be modified when the status of this entry is active(1).
.1.3.6.1.2.1.172.1.3.1.9,PIM-BSR-MIB::pimBsrCandidateBSRStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.172.1.4,PIM-BSR-MIB::pimBsrElectedBSRTable,,not-accessible,,current,,The (conceptual) table containing information about elected BSRs. The table contains one row for each zone for which there is an elected BSR.
.1.3.6.1.2.1.172.1.4.1,PIM-BSR-MIB::pimBsrElectedBSREntry,,not-accessible,pimBsrElectedBSRZoneIndex,current,,An entry (conceptual row) in the pimBsrElectedBSRTable.
.1.3.6.1.2.1.172.1.4.1.1,PIM-BSR-MIB::pimBsrElectedBSRZoneIndex,Unsigned32,not-accessible,,current,,The zone index uniquely identifies the zone on a device to which this Elected BSR is attached. There is one entry for each zone in ipMcastZoneTable. Scope-level information for this zone can be extracted from ipMcastZoneTable in IP Multicast MIB [RFC5132]. Zero is a special value used to request the default zone for a given scope. Zero is not a valid value for this object.
.1.3.6.1.2.1.172.1.4.1.2,PIM-BSR-MIB::pimBsrElectedBSRAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the elected BSR.
.1.3.6.1.2.1.172.1.4.1.3,PIM-BSR-MIB::pimBsrElectedBSRAddress,OCTET,read-only,,current,,The (unicast) address of the elected BSR. The InetAddressType is given by the pimBsrElectedBSRAddressType object.
.1.3.6.1.2.1.172.1.4.1.4,PIM-BSR-MIB::pimBsrElectedBSRPriority,Unsigned32,read-only,,current,,The priority value for the elected BSR for this address type. Numerically higher values for this object indicate higher priorities.
.1.3.6.1.2.1.172.1.4.1.5,PIM-BSR-MIB::pimBsrElectedBSRHashMaskLength,Unsigned32,read-only,,current,,The hash mask length (used in the RP hash function) advertised by the elected BSR for this zone.
.1.3.6.1.2.1.172.1.4.1.6,PIM-BSR-MIB::pimBsrElectedBSRExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before the elected BSR for this zone will be declared down.
.1.3.6.1.2.1.172.2,PIM-BSR-MIB::pimBsrConformance,,,,,,
.1.3.6.1.2.1.172.2.1,PIM-BSR-MIB::pimBsrCompliances,,,,,,
.1.3.6.1.2.1.172.2.1.1,PIM-BSR-MIB::pimBsrCompliance,,,,,,The compliance statement for PIM routers that implement the Bootstrap Router (BSR) mechanism.
.1.3.6.1.2.1.172.2.2,PIM-BSR-MIB::pimBsrGroups,,,,,,
.1.3.6.1.2.1.172.2.2.1,PIM-BSR-MIB::pimBsrObjectGroup,,,,,,A collection of objects for managing the Bootstrap Router (BSR) mechanism for PIM routers.
.1.3.6.1.2.1.172.2.2.2,PIM-BSR-MIB::pimBsrDiagnosticsGroup,,,,,,Objects providing additional diagnostics related to the Bootstrap Router (BSR) mechanism for PIM routers.
.1.3.6.1.2.1.173,SYSLOG-TC-MIB::syslogTCMIB,,,,,,The MIB module containing textual conventions for syslog messages. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5427; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.174,IANA-PWE3-MIB::ianaPwe3MIB,,,,,,This MIB module defines the IANAPwTypeTC and IANAPwPsnTypeTC textual conventions for use in PWE3 MIB modules. Any additions or changes to the contents of this MIB module require either publication of an RFC, Designated Expert Review as defined in RFC 5226, Guidelines for Writing an IANA Considerations Section in RFCs, and should be based on the procedures defined in [RFC4446]. The Designated Expert will be selected by the IESG Area Director(s) of the internet Area. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 
.1.3.6.1.2.1.175,T11-FC-SP-TC-MIB::t11FcTcMIB,,,,,,This MIB module defines Textual Conventions for use in the multiple MIB modules, which together define the instrumentation for an implementation of the Fibre Channel Security Protocols (FC-SP) specification. This MIB module also defines Object Identities (for use as possible values of MIB objects with syntax AutonomousType), including OIDs for the Cryptographic Algorithms defined in FC-SP. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5324; see the RFC itself for full legal notices.
.1.3.6.1.2.1.175.1,T11-FC-SP-TC-MIB::t11FcSpIdentities,,,,,,
.1.3.6.1.2.1.175.1.1,T11-FC-SP-TC-MIB::t11FcSpAlgorithms,,,,,,
.1.3.6.1.2.1.175.1.1.1,T11-FC-SP-TC-MIB::t11FcSpEncryptAlgorithms,,,,,,
.1.3.6.1.2.1.175.1.1.1.1,T11-FC-SP-TC-MIB::t11FcSpEncrNull,,,,,,The ENCR_NULL algorithm.
.1.3.6.1.2.1.175.1.1.1.2,T11-FC-SP-TC-MIB::t11FcSpEncrAesCbc,,,,,,The ENCR_AES_CBC algorithm.
.1.3.6.1.2.1.175.1.1.1.3,T11-FC-SP-TC-MIB::t11FcSpEncrAesCtr,,,,,,The ENCR_AES_CTR algorithm.
.1.3.6.1.2.1.175.1.1.1.4,T11-FC-SP-TC-MIB::t11FcSpEncrAesGcm,,,,,,The ENCR_AES_GCM algorithm.
.1.3.6.1.2.1.175.1.1.1.5,T11-FC-SP-TC-MIB::t11FcSpEncr3Des,,,,,,The ENCR_3DES algorithm.
.1.3.6.1.2.1.175.1.1.1.6,T11-FC-SP-TC-MIB::t11FcSpEncrNullAuthAesGmac,,,,,,The ENCR_NULL_AUTH_AES_GMAC algorithm.
.1.3.6.1.2.1.175.1.1.2,T11-FC-SP-TC-MIB::t11FcSpAuthAlgorithms,,,,,,
.1.3.6.1.2.1.175.1.1.2.1,T11-FC-SP-TC-MIB::t11FcSpAuthNull,,,,,,The AUTH_NONE algorithm.
.1.3.6.1.2.1.175.1.1.2.2,T11-FC-SP-TC-MIB::t11FcSpAuthHmacMd5L96,,,,,,The AUTH_HMAC_MD5_96 algorithm.
.1.3.6.1.2.1.175.1.1.2.3,T11-FC-SP-TC-MIB::t11FcSpAuthHmacSha1L96,,,,,,The AUTH_HMAC_SHA1_96 algorithm.
.1.3.6.1.2.1.175.1.1.2.4,T11-FC-SP-TC-MIB::t11FcSpAuthHmacMd5L128,,,,,,The AUTH_HMAC_MD5_128 algorithm.
.1.3.6.1.2.1.175.1.1.2.5,T11-FC-SP-TC-MIB::t11FcSpAuthHmacSha1L160,,,,,,The AUTH_HMAC_SHA1_160 algorithm.
.1.3.6.1.2.1.176,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuthenticationMIB,,,,,,This MIB module specifies the management information required to manage the Authentication Protocols defined by Fibre Channel's FC-SP specification. This MIB module defines three tables: - t11FcSpAuEntityTable is a table of Fibre Channel entities that can be authenticated using FC-SP's Authentication Protocols. - t11FcSpAuIfStatTable is a table with one row for each mapping of an Authentication entity onto an interface, containing statistics information. - t11FcSpAuRejectTable is a table of volatile information about FC-SP Authentication Protocol transactions that were most recently rejected. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5324; see the RFC itself for full legal notices.
.1.3.6.1.2.1.176.0,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBNotifications,,,,,,
.1.3.6.1.2.1.176.0.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejectSentNotify,,,,,,This notification indicates that a Switch (identified by the value of t11FamLocalSwitchWwn) has sent a reject message of the type indicated by t11FcSpAuRejType in response to an AUTH message. The content of the rejected AUTH message is given by the value of t11FcSpAuRejAuthMsgString. The values of the Reason Code and Reason Code Explanation in the AUTH_Reject/SW_RJT/LS_RJT are indicated by the values of t11FcSpAuRejReasonCode and t11FcSpAuRejReasonCodeExp.
.1.3.6.1.2.1.176.0.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejectReceivedNotify,,,,,,This notification indicates that a Switch (identified by the value of t11FamLocalSwitchWwn) has received a reject message of the type indicated by t11FcSpAuRejType in response to an AUTH message. The content of the rejected AUTH message is given by the value of t11FcSpAuRejAuthMsgString. The values of the Reason Code and Reason Code Explanation in the AUTH_Reject/SW_RJT/LS_RJT are indicated by the values of t11FcSpAuRejReasonCode and t11FcSpAuRejReasonCodeExp.
.1.3.6.1.2.1.176.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBObjects,,,,,,
.1.3.6.1.2.1.176.1.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuEntityTable,,not-accessible,,current,,A table of Fibre Channel entities that can be authenticated using FC-SP's Authentication Protocols. The purpose of an FC-SP Authentication Protocol is to verify that a claimed name is associated with the claiming entity. The Authentication Protocols can be used to authenticate Nx_Ports, B_Ports, or Switches.
.1.3.6.1.2.1.176.1.1.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuEntityEntry,,not-accessible,fcmInstanceIndex:t11FcSpAuEntityName:t11FcSpAuFabricIndex,current,,Information about the configuration and capabilities of an FC-SP entity (which is managed within the Fibre Channel management instance identified by fcmInstanceIndex) on a particular Fabric with respect to FC-SP's Authentication Protocols.
.1.3.6.1.2.1.176.1.1.1.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuEntityName,OCTET,not-accessible,,current,,The name used to identify the FC-SP entity. For entities that are Fibre Channel Switches, this value corresponds to the Switch's value of fcmSwitchWWN. For entities other than Fibre Channel Switches, this value corresponds to the value of fcmInstanceWwn for the corresponding Fibre Channel management instance.
.1.3.6.1.2.1.176.1.1.1.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuFabricIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Fabric to which the entity is attached.
.1.3.6.1.2.1.176.1.1.1.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuServerProtocol,OBJECT,read-only,,current,,The protocol, if any, used by the entity to communicate with a third party (i.e., an External Server) as part of the process by which it verifies DH-CHAP responses. For example, if the entity is using an external RADIUS server to verify DH-CHAP responses, then this object will have the value t11FcSpAuServerProtocolRadius. The value, zeroDotZero, is used to indicate that no protocol is being used to communicate with a third party to verify DH-CHAP responses. When no protocol is being used, or if the third party is unreachable via the specified protocol, then locally configured information (if any) may be used instead.
.1.3.6.1.2.1.176.1.1.1.4,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization of configuration information related to an FC-SP Entity on a particular Fabric: specifically, for MIB objects in the row containing this object. Even if an instance of this object has the value 'permanent(4)', none of the information in the corresponding row of this table needs to be writable.
.1.3.6.1.2.1.176.1.1.1.5,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuSendRejNotifyEnable,INTEGER,read-write,,current,true(1):false(2),An indication of whether or not the entity should issue t11FcSpAuRejectSentNotify notifications when sending AUTH_Reject/SW_RJT/LS_RJT to reject an AUTH message. If the value of the object is 'true', then this type of notification is generated. If the value is 'false', this type of notification is not generated.
.1.3.6.1.2.1.176.1.1.1.6,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRcvRejNotifyEnable,INTEGER,read-write,,current,true(1):false(2),An indication of whether or not the entity should issue t11FcSpAuRejectReceivedNotify notifications on the receipt of AUTH_Reject/SW_RJT/LS_RJT messages. If the value of the object is 'true', then this type of notification is generated. If the value is 'false', this type of notification is not generated.
.1.3.6.1.2.1.176.1.1.1.7,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuDefaultLifetime,Unsigned32,read-write,,current,,When the value of this object is non-zero, it specifies the default value of a lifetime, specified in units given by the corresponding instance of t11FcSpAuDefaultLifetimeUnits. This default lifetime is to be used for any Security Association that has no explicitly specified value for its lifetime. An SA's lifetime is either the time interval or the number of passed bytes, after which the SA has to be terminated and (if necessary) replaced with a new SA. If this object is zero, then there is no default value for lifetime.
.1.3.6.1.2.1.176.1.1.1.8,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuDefaultLifetimeUnits,INTEGER,read-write,,current,seconds(1):kiloBytes(2):megaBytes(3):gigaBytes(4):teraBytes(5):petaBytes(6):exaBytes(7):zettaBytes(8):yottaBytes(9),The units in which the value of the corresponding instance of t11FcSpAuDefaultLifetime specifies a default lifetime for a Security Association that has no explicitly-specified value for its lifetime.
.1.3.6.1.2.1.176.1.1.1.9,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejectMaxRows,Unsigned32,read-write,,current,,The maximum number of rows in the t11FcSpAuRejectTable for this entity on this Fabric. If and when an AUTH message is rejected, and the t11FcSpAuRejectTable already contains this maximum number of rows for the specific entity and Fabric, the row containing the oldest information is discarded and replaced by a row containing information about the new rejection. There will be less than this maximum number of rows in the t11FcSpAuRejectTable in exceptional circumstances, e.g., after an agent restart. In an implementation that does not support the t11FcSpAuRejectTable, this object will always be zero.
.1.3.6.1.2.1.176.1.1.1.10,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuDhChapHashFunctions,BITS,read-only,,current,md5(0):sha1(1),The hash functions that the entity supports when using the DH-CHAP algorithm.
.1.3.6.1.2.1.176.1.1.1.11,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuDhChapDhGroups,BITS,read-only,,current,null(0):group1024(1):group1280(2):group1536(3):group2048(4):group3072(5):group4096(6):group6144(7):group8192(8),The DH Groups that the entity supports when using the DH-CHAP algorithm in FC-SP.
.1.3.6.1.2.1.176.1.1.1.12,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuFcapHashFunctions,BITS,read-only,,current,md5(0):sha1(1),The hash functions that the entity supports when specified as Protocol Parameters in the AUTH_Negotiate message for FCAP in FC-SP.
.1.3.6.1.2.1.176.1.1.1.13,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuFcapCertsSignFunctions,BITS,read-only,,current,rsaSha1(0),The signature functions used within certificates that the entity supports when using FCAP in FC-SP.
.1.3.6.1.2.1.176.1.1.1.14,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuFcapDhGroups,BITS,read-only,,current,null(0):group1024(1):group1280(2):group1536(3):group2048(4):group3072(5):group4096(6):group6144(7):group8192(8),The DH Groups that the entity supports when using the FCAP algorithm in FC-SP.
.1.3.6.1.2.1.176.1.1.1.15,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuFcpapHashFunctions,BITS,read-only,,current,md5(0):sha1(1),The hash functions that the entity supports when using the FCPAP algorithm in FC-SP.
.1.3.6.1.2.1.176.1.1.1.16,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuFcpapDhGroups,BITS,read-only,,current,null(0):group1024(1):group1280(2):group1536(3):group2048(4):group3072(5):group4096(6):group6144(7):group8192(8),The DH Groups that the entity supports when using the FCPAP algorithm in FC-SP.
.1.3.6.1.2.1.176.1.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatTable,,not-accessible,,current,,Each FC-SP Authentication entity can operate on one or more interfaces, but at most one of them can operate on each interface. A row in this table exists for each interface to each Fabric on which each Authentication entity operates. The objects within this table contain statistics information related to FC-SP's Authentication Protocols.
.1.3.6.1.2.1.176.1.2.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatEntry,,not-accessible,fcmInstanceIndex:t11FcSpAuEntityName:t11FcSpAuIfStatInterfaceIndex:t11FcSpAuIfStatFabricIndex,current,,A set of Authentication Protocols statistics for an FC-SP Authentication entity (identified by t11FcSpAuEntityName) on one of its interfaces to a particular Fabric, which is managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.176.1.2.1.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatInterfaceIndex,Integer32,not-accessible,,current,,The interface on which the FC-SP Authentication entity operates and for which the statistics are collected.
.1.3.6.1.2.1.176.1.2.1.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatFabricIndex,Unsigned32,not-accessible,,current,,An index value identifying the particular Fabric for which the statistics are collected.
.1.3.6.1.2.1.176.1.2.1.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatTimeouts,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages sent by the particular entity on the particular Fabric on the particular interface, for which no response was received within a timeout period. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.2.1.4,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatInAcceptedMsgs,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages received and accepted by the particular entity on the particular Fabric on the particular interface. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.2.1.5,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatInLsSwRejectedMsgs,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages received by the particular entity on the particular Fabric on the particular interface, and rejected by a lower-level (SW_RJT or LS_RJT) reject. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.2.1.6,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatInAuthRejectedMsgs,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages received by the particular entity on the particular Fabric on the particular interface, and rejected by an AUTH_Reject message. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.2.1.7,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatOutAcceptedMsgs,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages sent by the particular entity on the particular Fabric on the particular interface, which were accepted by the neighboring entity, i.e., not rejected by an AUTH_Reject message, nor by a lower-level (SW_RJT or LS_RJT) reject. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.2.1.8,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatOutLsSwRejectedMsgs,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages sent by the particular entity on the particular Fabric on the particular interface, which were rejected by a lower-level (SW_RJT or LS_RJT) reject. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.2.1.9,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatOutAuthRejectedMsgs,Counter32,read-only,,current,,The number of FC-SP Authentication Protocol messages sent by the particular entity on the particular Fabric on the particular interface, which were rejected by an AUTH_Reject message. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.176.1.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejectTable,,not-accessible,,current,,A table of volatile information about FC-SP Authentication Protocol transactions that were recently rejected with an AUTH_Reject message, or with an SW_RJT/LS_RJT. The maximum number of rows in this table for a specific entity on a specific Fabric is given by the value of the corresponding instance of t11FcSpAuRejectMaxRows. The syntax of t11FcSpAuRejTimestamp is TimeStamp, and thus its value rolls over to zero after approximately 497 days. To avoid any confusion due to such a rollover, rows should be deleted from this table before they are 497 days old. This table will be empty if no AUTH_Reject messages, nor any SW_RJT/LS_RJT's rejecting an AUTH message, have been sent or received since the last re-initialization of the agent.
.1.3.6.1.2.1.176.1.3.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejectEntry,,not-accessible,fcmInstanceIndex:t11FcSpAuEntityName:t11FcSpAuRejInterfaceIndex:t11FcSpAuRejFabricIndex:t11FcSpAuRejTimestamp,current,,Information about one AUTH message (either an AUTH_ELS or an AUTH_ILS) that was rejected with an AUTH_Reject, SW_RJT or LS_RJT message, sent/received by the entity identified by values of fcmInstanceIndex and t11FcSpAuEntityName, on an interface to a particular Fabric.
.1.3.6.1.2.1.176.1.3.1.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejInterfaceIndex,Integer32,not-accessible,,current,,The interface on which the rejected AUTH message was sent or received.
.1.3.6.1.2.1.176.1.3.1.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejFabricIndex,Unsigned32,not-accessible,,current,,An index value identifying the particular Fabric on which the rejected AUTH message was sent or received.
.1.3.6.1.2.1.176.1.3.1.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejTimestamp,TimeTicks,not-accessible,,current,,The time at which the AUTH message was rejected. If two rows have the same value of this object for the same entity on the same interface and Fabric, the value of this object for the later one is incremented by one.
.1.3.6.1.2.1.176.1.3.1.4,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejDirection,INTEGER,read-only,,current,sent(1):received(2),An indication of whether the rejection was sent or received by the identified entity. The value 'sent(1)' corresponds to a notification of type t11FcSpAuRejectSentNotify; the value 'received(2)' corresponds to t11FcSpAuRejectReceivedNotify.
.1.3.6.1.2.1.176.1.3.1.5,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejType,INTEGER,read-only,,current,authReject(1):swRjt(2):lsRjt(3),An indication of whether the rejection was an AUTH_Reject, an SW_RJT or an LS_RJT.
.1.3.6.1.2.1.176.1.3.1.6,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejAuthMsgString,OCTET,read-only,,current,,The binary content of the AUTH message that was rejected, formatted as an octet string (in network byte order) containing the content of the message. If the binary content is unavailable, then the length is zero. Otherwise, the first octet of the message identifies the type of message: '90'h - an AUTH_ELS, see Table 6 in FC-SP, '40'h - an AUTH_ILS, see Table 3 in FC-SP, or '41'h - an B_AUTH_ILS, see Table 5 in FC-SP. and the remainder of the message may be truncated.
.1.3.6.1.2.1.176.1.3.1.7,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejReasonCode,INTEGER,read-only,,current,authFailure(1):logicalError(2):logicalBusy(3):authILSNotSupported(4):authELSNotSupported(5):notLoggedIn(6),The reason code with which this AUTH message was rejected.
.1.3.6.1.2.1.176.1.3.1.8,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejReasonCodeExp,INTEGER,read-only,,current,authMechanismNotUsable(1):dhGroupNotUsable(2):hashFunctionNotUsable(3):authTransactionAlreadyStarted(4):authenticationFailed(5):incorrectPayload(6):incorrectAuthProtocolMessage(7):restartAuthProtocol(8):authConcatNotSupported(9):unsupportedProtocolVersion(10):logicalBusy(11):authILSNotSupported(12):authELSNotSupported(13):notLoggedIn(14),The reason code explanation with which this AUTH message was rejected.
.1.3.6.1.2.1.176.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBConformance,,,,,,
.1.3.6.1.2.1.176.2.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBCompliances,,,,,,
.1.3.6.1.2.1.176.2.1.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBCompliance,,,,,,The compliance statement for entities that implement one or more of the Authentication Protocols defined in FC-SP.
.1.3.6.1.2.1.176.2.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBGroups,,,,,,
.1.3.6.1.2.1.176.2.2.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuGeneralGroup,,,,,,A collection of objects for the capabilities and configuration parameters of FC-SP's Authentication Protocols. The inclusion of t11FcSpAuIfStatTimeouts in this group provides information on mappings of Authentication entities onto interfaces.
.1.3.6.1.2.1.176.2.2.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuIfStatsGroup,,,,,,A collection of objects for monitoring the operations of FC-SP's Authentication Protocols.
.1.3.6.1.2.1.176.2.2.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuRejectedGroup,,,,,,A collection of objects holding information concerning FC-SP Authentication Protocol transactions that were recently rejected with an AUTH_Reject, with an SW_RJT, or with an LS_RJT.
.1.3.6.1.2.1.176.2.2.4,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuNotificationGroup,,,,,,A collection of notifications for use in the management of FC-SP's Authentication Protocols.
.1.3.6.1.2.1.176.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuMIBIdentities,,,,,,
.1.3.6.1.2.1.176.3.1,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuServerProtocolRadius,,,,,,This OID identifies RADIUS as the protocol used to communicate with an External Server as part of the process by which identities are verified. In this case, information about the RADIUS Servers is likely to be provided in radiusAuthServerExtTable defined in the RADIUS-AUTH-CLIENT-MIB.
.1.3.6.1.2.1.176.3.2,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuServerProtocolDiameter,,,,,,This OID identifies Diameter as the protocol used to communicate with an External Server as part of the process by which identities are verified.
.1.3.6.1.2.1.176.3.3,T11-FC-SP-AUTHENTICATION-MIB::t11FcSpAuServerProtocolTacacs,,,,,,This OID identifies TACACS as the protocol used to communicate with an External Server as part of the process by which identities are verified.
.1.3.6.1.2.1.177,T11-FC-SP-ZONING-MIB::t11FcSpZoningMIB,,,,,,This MIB module specifies the extensions to the T11-FC-ZONE-SERVER-MIB module that are necessary for the management of Fibre Channel's FC-SP Zoning Servers, as defined in the FC-SP specification. The persistence of values written to these MIB objects is the same as the persistence of the objects they extend, i.e., it is given by the value of the relevant instance of t11ZsServerDatabaseStorageType (defined in the T11-FC-ZONE-SERVER-MIB module). Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5324; see the RFC itself for full legal notices.
.1.3.6.1.2.1.177.0,T11-FC-SP-ZONING-MIB::t11FcSpZsMIBNotifications,,,,,,
.1.3.6.1.2.1.177.0.1,T11-FC-SP-ZONING-MIB::t11FcSpZsFabricJoinSuccessNotify,,,,,,This notification indicates that a Switch that is part of one Fabric (indicated by the value of t11ZsFabricIndex) has successfully joined (on the interface indicated by the value of ifIndex) with a Switch that is part of another Fabric. If multiple Virtual Fabrics are configured on an interface, and all are successfully joined at the same time, and if the agent so chooses, then it can generate just one notification in which t11ZsFabricIndex has the value 4096.
.1.3.6.1.2.1.177.0.2,T11-FC-SP-ZONING-MIB::t11FcSpZsFabricJoinFailureNotify,,,,,,This notification indicates that an E_Port on the local Switch has entered the Isolated state because a join between two Fabrics failed. The failure occurred on the local Fabric indicated by the value of t11ZsFabricIndex, on the interface indicated by the value of ifIndex. If multiple Virtual Fabrics are configured on an interface, and all have a failure to join at the same time, and if the agent so chooses, then it can generate just one notification in which t11ZsFabricIndex has the value 4096.
.1.3.6.1.2.1.177.1,T11-FC-SP-ZONING-MIB::t11FcSpZsMIBObjects,,,,,,
.1.3.6.1.2.1.177.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsConfiguration,,,,,,
.1.3.6.1.2.1.177.1.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsServerTable,,not-accessible,,current,,A table which provides FC-SP-specific information about the Zone Servers on each Fabric in one or more Switches.
.1.3.6.1.2.1.177.1.1.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsServerEntry,,not-accessible,,current,,Each entry contains information relevant to FC-SP for a particular Zone Server for a particular Fabric on a particular Switch. The Fabric and Switch are identified in the same manner as in t11ZsServerEntry.
.1.3.6.1.2.1.177.1.1.1.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsServerCapabilityObject,BITS,read-only,,current,fcSpZoning(0),Capabilities of the Zone Server for the particular Fabric on the particular Switch, with respect to FC-SP Zoning: fcSpZoning -- set to 1 to indicate the Switch is capable of supporting FC-SP Zoning. 
.1.3.6.1.2.1.177.1.1.1.1.2,T11-FC-SP-ZONING-MIB::t11FcSpZsServerEnabled,INTEGER,read-write,,current,true(1):false(2),This object indicates whether the Zone Server for the particular Fabric on the particular Switch, is operating in FC-SP Zoning mode.
.1.3.6.1.2.1.177.1.1.1.1.3,T11-FC-SP-ZONING-MIB::t11FcSpZoneSetHashStatus,INTEGER,read-write,,current,calculate(1):correct(2):stale(3),When read, the value of this object is either: correct -- the corresponding instances of both t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash contain the correct hash values; or stale -- the corresponding instances of t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash contain stale (possibly incorrect) values; Writing a value of 'calculate' is a request to re-calculate and update the values of the corresponding instances of both t11FcSpActiveZoneSetHash and t11FcSpZoneSetDatabaseHash. Writing a value of 'correct' or 'stale' to this object is an error (e.g., 'wrongValue'). When the Active Zone Set and/or the Zone Set Database are updated, it is common that multiple changes need to be made at the same time. In such circumstances, the use of this object allows the hash values to be updated only once after all changes, rather than repeatedly/after each individual change. If and when the corresponding instance of t11ZsServerDatabaseStorageType has the value 'permanent(4)', then if write access is supported to any instance of a read-write object in any row of any table governed by the 'permanent' value of t11ZsServerDatabaseStorageType, then write access to the corresponding instance of this object must also be supported.
.1.3.6.1.2.1.177.1.1.1.1.4,T11-FC-SP-ZONING-MIB::t11FcSpActiveZoneSetHashType,OCTET,read-only,,current,,The format used for the hash value contained in the corresponding instance of t11FcSpActiveZoneSetHash.
.1.3.6.1.2.1.177.1.1.1.1.5,T11-FC-SP-ZONING-MIB::t11FcSpActiveZoneSetHash,OCTET,read-only,,current,,The value of the hash for the current Active Zone Set. The format of this value is given by the corresponding instance of t11FcSpActiveZoneSetHashType.
.1.3.6.1.2.1.177.1.1.1.1.6,T11-FC-SP-ZONING-MIB::t11FcSpZoneSetDatabaseHashType,OCTET,read-only,,current,,The format used for the hash value contained in the corresponding instance of t11FcSpZoneSetDatabaseHash.
.1.3.6.1.2.1.177.1.1.1.1.7,T11-FC-SP-ZONING-MIB::t11FcSpZoneSetDatabaseHash,OCTET,read-only,,current,,The value of the hash for the current Zone Set Database. The format of this value is given by the corresponding instance of t11FcSpZoneSetDatabaseHashType.
.1.3.6.1.2.1.177.1.1.2,T11-FC-SP-ZONING-MIB::t11FcSpZsNotifyControlTable,,not-accessible,,current,,A table of control information for notifications generated due to Zone Server events related to FC-SP Zoning.
.1.3.6.1.2.1.177.1.1.2.1,T11-FC-SP-ZONING-MIB::t11FcSpZsNotifyControlEntry,,not-accessible,,current,,Each entry is an augmentation of the notification control information for a Zone Server for a particular Fabric on a particular Switch. The Fabric and Switch are identified in the same manner as in t11ZsNotifyControlEntry.
.1.3.6.1.2.1.177.1.1.2.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsNotifyJoinSuccessEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11FcSpZsFabricJoinFailureNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.177.1.1.2.1.2,T11-FC-SP-ZONING-MIB::t11FcSpZsNotifyJoinFailureEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11FcSpZsFabricJoinSuccessNotify notifications should be generated by the Zone Server for this Fabric.
.1.3.6.1.2.1.177.1.2,T11-FC-SP-ZONING-MIB::t11FcSpZsStatistics,,,,,,
.1.3.6.1.2.1.177.1.2.1,T11-FC-SP-ZONING-MIB::t11FcSpZsStatsTable,,not-accessible,,current,,A table of statistics specific to FC-SP that are maintained by Zone Servers.
.1.3.6.1.2.1.177.1.2.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsStatsEntry,,not-accessible,,current,,A set of statistics specific to FC-SP for a particular Zone Server for a particular Fabric on a particular Switch. The Fabric and Switch are identified in the same manner as in t11ZsStatsEntry.
.1.3.6.1.2.1.177.1.2.1.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsSPCMITrequestsSent,Counter32,read-only,,current,,The number of SP Commit Zone Changes (SPCMIT) operation requests sent by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.2,T11-FC-SP-ZONING-MIB::t11FcSpZsSPCMITrequestsAccepted,Counter32,read-only,,current,,The number of SP Commit Zone Changes (SPCMIT) operation requests received and accepted by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.3,T11-FC-SP-ZONING-MIB::t11FcSpZsSPCMITrequestsRejected,Counter32,read-only,,current,,The number of SP Commit Zone Changes (SPCMIT) operation requests received but rejected by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.4,T11-FC-SP-ZONING-MIB::t11FcSpZsZcpRequestsSent,Counter32,read-only,,current,,The number of Zoning Check Protocol (ZCP) requests sent by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.5,T11-FC-SP-ZONING-MIB::t11FcSpZsZcpRequestsAccepted,Counter32,read-only,,current,,The number of Zoning Check Protocol (ZCP) requests received and accepted by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.6,T11-FC-SP-ZONING-MIB::t11FcSpZsZcpRequestsRejected,Counter32,read-only,,current,,The number of Zoning Check Protocol (ZCP) requests received but rejected by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.7,T11-FC-SP-ZONING-MIB::t11FcSpZsZirRequestsAccepted,Counter32,read-only,,current,,The number of Zoning Information Request (ZIR) requests received and accepted by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.1.2.1.1.8,T11-FC-SP-ZONING-MIB::t11FcSpZsZirRequestsRejected,Counter32,read-only,,current,,The number of Zoning Information Request (ZIR) requests received but rejected by the Zone Server. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.177.2,T11-FC-SP-ZONING-MIB::t11FcSpZsMIBConformance,,,,,,
.1.3.6.1.2.1.177.2.1,T11-FC-SP-ZONING-MIB::t11FcSpZsMIBCompliances,,,,,,
.1.3.6.1.2.1.177.2.1.1,T11-FC-SP-ZONING-MIB::t11FcSpZsMIBCompliance,,,,,,The compliance statement for entities that implement the extensions specified in FC-SP for Fibre Channel's Zone Server.
.1.3.6.1.2.1.177.2.2,T11-FC-SP-ZONING-MIB::t11FcSpZsMIBGroups,,,,,,
.1.3.6.1.2.1.177.2.2.1,T11-FC-SP-ZONING-MIB::t11FcSpZsObjectsGroup,,,,,,A collection of objects for Zone configuration information of a Zone Server capable of operating in FC-SP Zoning mode.
.1.3.6.1.2.1.177.2.2.2,T11-FC-SP-ZONING-MIB::t11FcSpZsNotificationControlGroup,,,,,,A collection of notification control objects for monitoring Zone Server failures specific to FC-SP.
.1.3.6.1.2.1.177.2.2.3,T11-FC-SP-ZONING-MIB::t11FcSpZsStatisticsGroup,,,,,,A collection of objects for collecting Zone Server statistics which are specific to FC-SP.
.1.3.6.1.2.1.177.2.2.4,T11-FC-SP-ZONING-MIB::t11FcSpZsNotificationGroup,,,,,,A collection of notification(s) for monitoring Zone Server events that are specific to FC-SP.
.1.3.6.1.2.1.178,T11-FC-SP-POLICY-MIB::t11FcSpPolicyMIB,,,,,,This MIB module specifies the management information required to manage Fabric Policies as defined by Fibre Channel's FC-SP specification. FC-SP uses the term 'Policy Objects', sometimes abbreviated to just 'Objects', to refer to containers used to hold the data by which Fabric Policies are specified/stored. This obviously has the potential to cause confusion between 'Policy Objects' and 'MIB objects'. The DESCRIPTIONs in this MIB module attempt to avoid such confusion by the use of different adjectives and capitalization, even though such mechanisms are less effective when used in descriptors. Some types of Policy Objects contain multiple items of information, each of which are held in the same format within the Policy Object. In such cases, FC-SP uses the term 'Entry' to describe each instance of the common format. For example, FC-SP defines an Attribute Policy Object as containing one or more 'Attribute Entries'. Again, this MIB module attempts to avoid confusion by the use of adjectives and capitalization to distinguish an Entry within a Policy Object from an entry within a MIB table. A Fabric's database of Policy Objects consists of a set of active Objects that are to be enforced by that Fabric, as well as non-active Objects that are not enforced. Operations defined (in FC-SP) for Policy Management are: - Add/Get/Remove operations on individual non-active Policy Objects, - Activate/Deactivate operations on a Policy Summary Object, and - Get operations on the active Policy Summary Object and/or on individual active Policy Objects. This MIB module has five parts: 1) Active Policy Objects - read-only MIB objects representing the set of active Policy Objects for each Fabric, 2) Activate/Deactivate Operations - a read-write MIB object to invoke an Activate operation of the policies specified via a non-active Policy Summary Object, and - a read-write MIB object to invoke a Deactivate operation. 3) Non-active Policy Objects - read-create MIB objects to allow the creation of non-active Policy Summary Objects (which reference non-active Policy Objects), and - read-create MIB objects representing non-active Policy Objects. 4) Statistics 5) Control information and Notifications Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5324; see the RFC itself for full legal notices.
.1.3.6.1.2.1.178.0,T11-FC-SP-POLICY-MIB::t11FcSpPoMIBNotifications,,,,,,
.1.3.6.1.2.1.178.0.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNotifyActivation,,,,,,This notification is generated whenever a Security Policy Server (indicated by the value of t11FcSpPoServerAddress) successfully completes the execution of an Activate Policy Summary request. The value of t11FcSpPoRequestSource indicates the source of the APS request. The value of t11FcSpPoPolicySummaryObjName indicates the name of the activated Policy Summary Object.
.1.3.6.1.2.1.178.0.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNotifyActivateFail,,,,,,This notification is generated whenever a Security Policy Server (indicated by the value of t11FcSpPoServerAddress) fails to complete the execution of an Activate Policy Summary request. The value of t11FcSpPoCtCommandString indicates the rejected request, and the values of t11FcSpPoReasonCode, t11FcSpPoReasonCodeExp, and t11FcSpPoReasonVendorCode indicate the reason for the rejection. The value of t11FcSpPoRequestSource indicates the source of the request.
.1.3.6.1.2.1.178.0.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNotifyDeactivation,,,,,,This notification is generated whenever a Security Policy Server (indicated by the value of t11FcSpPoServerAddress) successfully completes the execution of a Deactivate Policy Summary request. The value of t11FcSpPoRequestSource indicates the source of the DPS request.
.1.3.6.1.2.1.178.0.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNotifyDeactivateFail,,,,,,This notification is generated whenever a Security Policy Server (indicated by the value of t11FcSpPoServerAddress) fails to complete the execution of a Deactivate Policy Summary request. The value of t11FcSpPoCtCommandString indicates the rejected request, and the values of t11FcSpPoReasonCode, t11FcSpPoReasonCodeExp, and t11FcSpPoReasonVendorCode indicate the reason for the rejection. The value of t11FcSpPoRequestSource indicates the source of the request.
.1.3.6.1.2.1.178.1,T11-FC-SP-POLICY-MIB::t11FcSpPoMIBObjects,,,,,,
.1.3.6.1.2.1.178.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoActive,,,,,,
.1.3.6.1.2.1.178.1.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoTable,,not-accessible,,current,,A table containing top-level information about active FC-SP policies on various Fabrics.
.1.3.6.1.2.1.178.1.1.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex,current,,Each entry contains information about active FC-SP policies for a particular Fabric, managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.1.1.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoFabricIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Fabric.
.1.3.6.1.2.1.178.1.1.1.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoPolicySummaryObjName,OCTET,read-only,,current,,The name of this Fabric's (active) Policy Summary Object.
.1.3.6.1.2.1.178.1.1.1.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoAdminFabricName,OCTET,read-only,,current,,The administratively-specified name for this Fabric, as specified in the active Switch Membership List Object. This value is meaningful only when Static Domain_IDs are in use in a Fabric (see FC-SW-4). Static Domain_IDs are administratively enabled by a setting of the Switch Flags in each Switch Entry in the Switch Membership List Object. If Static Domain_IDs are not in use, this value might be '0000000000000000'h. The t11FamEnable, t11FamFabricName, and t11FamConfigDomainIdType objects defined in the T11-FC-FABRIC-ADDR-MGR-MIB module are also concerned with the use of an administratively-specified name for a Fabric and Static Domain_IDs. When FC-SP Policy is in use in a Fabric, the values of t11FamEnable, t11FamFabricName, and t11FamConfigDomainIdType must be read-only and reflect the active Policy Objects. For example, the value of t11FamFabricName must reflect the value of t11FcSpPoAdminFabricName.
.1.3.6.1.2.1.178.1.1.1.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoActivatedTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which this Fabric's Policy Summary Object was last activated, or zero if the same Policy Summary Object has been active since the last restart of the management system.
.1.3.6.1.2.1.178.1.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryTable,,not-accessible,,current,,A table of information about active Policy Objects listed within FC-SP Policy Summary Objects.
.1.3.6.1.2.1.178.1.1.2.1,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoSummaryPolicyNameType:t11FcSpPoSummaryPolicyName,current,,Each entry contains information about one of the active Policy Objects listed within the Policy Summary Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. How many Policy Objects of a given type can be active at any one time for a given Fabric depends on the type, as specified in FC-SP. For some types, it is one per Fabric; for other types, more than one can be active per Fabric. In both of these cases, the absence of any entries in this table for a particular type is equivalent to there being one Policy Object of that type that is empty, e.g., a Switch Membership List Object that identifies zero Switches.
.1.3.6.1.2.1.178.1.1.2.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryPolicyNameType,INTEGER,not-accessible,,current,nodeName(1):alphaNumericName(7),The combination of t11FcSpPoSummaryPolicyNameType and t11FcSpPoSummaryPolicyName specify the name of the Policy Object contained in the Policy Summary Object. The type of name is 'nodeName' if the value of the corresponding instance of t11FcSpPoSummaryPolicyType is 'switchConnectivity', or 'alphaNumericName' otherwise.
.1.3.6.1.2.1.178.1.1.2.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryPolicyName,OCTET,not-accessible,,current,,The combination of t11FcSpPoSummaryPolicyNameType and t11FcSpPoSummaryPolicyName specify the name of the Policy Object contained in the Policy Summary Object.
.1.3.6.1.2.1.178.1.1.2.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryPolicyType,INTEGER,read-only,,current,summary(1):switchMemberList(2):nodeMemberList(3):switchConnectivity(4):ipMgmtList(5):attribute(6),The 'Identifier' that specifies the type of this Policy Object.
.1.3.6.1.2.1.178.1.1.2.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryHashFormat,OCTET,read-only,,current,,The format of this Policy Object's hash value as contained in the corresponding instance of the t11FcSpPoSummaryHashValue object.
.1.3.6.1.2.1.178.1.1.2.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoSummaryHashValue,OCTET,read-only,,current,,The hash value of this Policy Object, in the format identified by the corresponding instance of the t11FcSpPoSummaryHashFormat object.
.1.3.6.1.2.1.178.1.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembTable,,not-accessible,,current,,A table of Switch Entries in active Switch Membership List Objects. One Switch Membership List Object is represented by all of the rows of this table that have the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.1.3.1,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoSwMembSwitchNameType:t11FcSpPoSwMembSwitchName,current,,Each entry contains information about one Switch Entry within the active Switch Membership List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.1.3.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembSwitchNameType,INTEGER,not-accessible,,current,nodeName(1):restrictedNodeName(2):wildcard(5):restrictedWildcard(6),If the value of this object is 'nodeName' or 'restrictedNodeName', then the combination of this object and t11FcSpPoSwMembSwitchName specify the Switch Name of this Switch Entry. The membership is restricted or unrestricted based on the name type. Restricted membership means that the Switch is not allowed to be part of the Fabric unless allowed by a specific Switch Connectivity Object. Unrestricted membership means that the Switch is allowed to be part of the Fabric unless disallowed by a specific Switch Connectivity Object. The values of 'wildcard' and 'restrictedWildcard' provide the means to specify whether to allow/deny membership for Switches not explicitly named in the Switch Membership List Object.
.1.3.6.1.2.1.178.1.1.3.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembSwitchName,OCTET,not-accessible,,current,,When the value of t11FcSpPoSwMembSwitchNameType is 'wildcard' or 'restrictedWildcard', this object has the value '0000000000000000'h. Otherwise, the combination of t11FcSpPoSwMembSwitchNameType and this object specify the Switch Name of this Switch Entry.
.1.3.6.1.2.1.178.1.1.3.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembSwitchFlags,BITS,read-only,,current,staticDomainID(0):insistentDomainID(1):serialPortsAccess(2):physicalPortsAccess(3):managerRole(4),Configurable options in respect to the administration of Policy Objects at this Switch: 'staticDomainID' - if this bit is set, the Switch uses the 'Static Domain_IDs behavior' (as defined in FC-SW-4). This bit needs to have the same setting for all Switches in a Fabric's Switch Membership List Object, or else the Fabric will partition. If this bit is set, the Domain_ID for the Switch is given by the corresponding instance of t11FcSpPoSwMembDomainID. 'insistentDomainID' - if this bit is set, the Switch uses the 'Insistent Domain_ID behavior' (see t11FamConfigDomainId of T11-FC-FABRIC-ADDR-MGR-MIB), the Domain_ID for the Switch is given by the corresponding instance of t11FcSpPoSwMembDomainID. 'serialPortsAccess' - the Switch allows management through serial ports when and only when this bit is set. 'physicalPortsAccess' - the Switch allows management through the physical panel when and only when this bit is set. 'managerRole' - the Switch is allowed to change the Fabric Policy configuration (on receipt of any of the EACA, Enhanced Stage Fabric Configuration (ESFC), Enhanced Update Fabric Configuration (EUFC), ACA, SFC, or UFC SW_ILSs) if and only if this bit is set. Whenever a Fabric has Active Policy Objects, the value of the t11FamConfigDomainIdType object defined in the T11-FC-FABRIC-ADDR-MGR-MIB module must be read-only and reflect the values of the 'staticDomainID' and 'insistentDomainID' bits of this object.
.1.3.6.1.2.1.178.1.1.3.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembDomainID,Integer32,read-only,,current,,The specified Domain_ID value when either of the 'staticDomainID' or 'insistentDomainID' bits are set in the corresponding instance of t11FcSpPoSwMembSwitchFlags. Whenever a Fabric has Active Policy Objects, the value of the t11FamConfigDomainId object defined in the T11-FC-FABRIC-ADDR-MGR-MIB module must be read-only and reflect the value of this object.
.1.3.6.1.2.1.178.1.1.3.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembPolicyDataRole,INTEGER,read-only,,current,client(1):autonomous(2):server(3),The role of the Switch in terms of which Policy data it retains/maintains: 'client' - the Switch operates as a Client Switch. A Client Switch maintains its own Switch Connectivity Object and all Fabric-wide List Objects. If FC-SP Zoning is used, a Client Switch maintains only the subset of the Active Zone Set that it requires to enforce the current Fabric Zoning configuration. 'autonomous' - the Switch operates as an Autonomous Switch. An Autonomous Switch maintains its own Switch Connectivity Object and all Fabric-wide List Objects. This is the same as 'client' except that if FC-SP Zoning is used, an Autonomous Switch maintains a complete copy of the Fabric Zoning Database. 'server' - the Switch operates as a Server Switch. A Server Switch maintains all Fabric-wide List Objects and the Switch Connectivity Objects of each Switch in the Fabric. If FC-SP Zoning is used, a Server Switch maintains a complete copy of the Fabric Zoning Database.
.1.3.6.1.2.1.178.1.1.3.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembAuthBehaviour,BITS,read-only,,current,mustAuthenticate(0):rejectIsFailure(1),The authentication behaviour of the Switch: 'mustAuthenticate' - if this bit is set, all connections between this Switch and neighbor Switches must be authenticated. 'rejectIsFailure' - if this bit is set, the rejection of an AUTH_Negotiate message must be considered as an authentication failure by this Switch.
.1.3.6.1.2.1.178.1.1.3.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoSwMembAttribute,OCTET,read-only,,current,,The name of an active Attribute Policy Object that is defined for this Switch, or the zero-length string. The zero-length string indicates that no Attribute Policy Object is defined for this Switch.
.1.3.6.1.2.1.178.1.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembTable,,not-accessible,,current,,A table of Node Entries in active Node Membership List Objects. One Node Membership List Object is represented by all of the rows of this table that have the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.1.4.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNoMembNodeNameType:t11FcSpPoNoMembNodeName,current,,Each entry contains information about one Node Entry within the active Node Membership List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.1.4.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembNodeNameType,INTEGER,not-accessible,,current,nodeName(1):restrictedNodeName(2):portName(3):restrictedPortName(4):wildcard(5):restrictedWildcard(6),If the value of this object is 'wildcard' or 'restrictedWildcard', this Node Entry applies to Nodes not explicitly named in the Node Membership List Object. Otherwise, the combination of this object and t11FcSpPoNoMembNodeName specify the name of this Node Entry in the active Node Membership List Object. A Node is identified by its Node Name or by one or more of its Port Names. Restricted membership means that a Node is not allowed to be connected to the Fabric unless allowed by a specific Switch Connectivity Object. Unrestricted membership means that a Node is allowed to be connected to the Fabric unless disallowed by a specific Switch Connectivity Object.
.1.3.6.1.2.1.178.1.1.4.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembNodeName,OCTET,not-accessible,,current,,If the value of t11FcSpPoNoMembNodeNameType is 'wildcard' or 'restrictedWildcard', this object has the value '0000000000000000'h. Otherwise, the combination of t11FcSpPoNoMembNodeNameType and this object specify the name of this Node Entry is the active Node Membership List Object.
.1.3.6.1.2.1.178.1.1.4.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembFlags,BITS,read-only,,current,scsiEnclosureAccess(0):authenticationRequired(1),Configurable options in respect to the administration of Policy Objects at this Node: 'scsiEnclosureAccess' - the Node is allowed to control any Switch through SCSI Enclosure Services if this bit is set. If a Switch does not support SCSI Enclosure Services, this bit is ignored. 'authenticationRequired' - the Node is required to authenticate itself to any Switch to which it is connected if and only if this bit is set.
.1.3.6.1.2.1.178.1.1.4.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembCtAccessIndex,Unsigned32,read-only,,current,,If the value of this object is zero, then access by this Node to Generic Services is not limited by a Common Transport Access Specifier. Otherwise, the limits are specified by the set of Common Transport Access Descriptors contained in those rows of the t11FcSpPoCtDescrTable for the same Fabric and for which the value of t11FcSpPoCtDescrSpecifierIndex is the same as the value of this object.
.1.3.6.1.2.1.178.1.1.4.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNoMembAttribute,OCTET,read-only,,current,,The name of an active Attribute Policy Object that is defined for this Node, or the zero-length string. The zero-length string indicates that no Attribute Policy Object is defined for this Node.
.1.3.6.1.2.1.178.1.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrTable,,not-accessible,,current,,A table of Common Transport Access Descriptors being used within active Policy Objects. A Common Transport Access Specifier is a list of Common Transport Access Descriptors that specify whether a Node is allowed to access a Generic Service or Sub-Server. An active Common Transport Access Specifier is represented by all rows of this table that have the same values of fcmInstanceIndex, t11FcSpPoFabricIndex, and t11FcSpPoCtDescrSpecifierIndex.
.1.3.6.1.2.1.178.1.1.5.1,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoCtDescrSpecifierIndex:t11FcSpPoCtDescrIndex,current,,Each entry contains information about one Common Transport Access Descriptor of an active Common Transport Access Specifier used within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.1.5.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrSpecifierIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Common Transport Access Specifier within a Fabric.
.1.3.6.1.2.1.178.1.1.5.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Common Transport Access Descriptor within a Common Transport Access Specifier.
.1.3.6.1.2.1.178.1.1.5.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrFlags,BITS,read-only,,current,allow(0):gsTypeWildcard(1):gsSubTypeWildcard(2):readOnly(3),The flag bits that specify how access is to be limited by this Common Transport Access Descriptor: - allow -- access to the specified Generic Service and Server is allowed if this bit is set, and is to be denied if this bit is not set. - gsTypeWildcard -- if this bit is set, the Generic Service to be allowed/denied is specified by the value of t11FcSpPoCtDescrGsType. If this bit is set, then the gsSubTypeWildcard bit must not be set. - gsSubTypeWildcard -- if this bit is set, the Generic Service to be allowed/denied is specified by the value of t11FcSpPoCtDescrGsSubType. If this bit is set, then the gsTypeWildcard bit must not be set. - readOnly -- if this bit is set, then access is to be granted only for reading.
.1.3.6.1.2.1.178.1.1.5.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrGsType,OCTET,read-only,,current,,The GS_Type of the Generic Service (e.g., the FC-GS-5 Management Service) that is subject to access control. This value is ignored if the gsTypeWildcard bit is not set in the corresponding value of t11FcSpPoCtDescrFlags.
.1.3.6.1.2.1.178.1.1.5.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoCtDescrGsSubType,OCTET,read-only,,current,,The GS_Subtype of the Generic Server (e.g., the Fabric Zone Server) that is subject to access control. This value is ignored if the gsSubTypeWildcard bit is not set in the corresponding value of t11FcSpPoCtDescrFlags.
.1.3.6.1.2.1.178.1.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnTable,,not-accessible,,current,,A table of active Switch Connectivity Objects. A Switch Connectivity Object defines to which other Switches or Nodes a particular Switch may/may not be connected at the Node level and/or at the Port level.
.1.3.6.1.2.1.178.1.1.6.1,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoSwConnSwitchName:t11FcSpPoSwConnAllowedType:t11FcSpPoSwConnPortNameOrAll:t11FcSpPoSwConnAllowedIndex,current,,Each entry contains the name of either a Switch or a Node with which any port of a particular Switch, or a particular port of that Switch, is allowed or not allowed to be connected. The particular Switch is on the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.1.6.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnSwitchName,OCTET,not-accessible,,current,,The name of the particular Switch for which this Switch Connectivity Object specifies topology restrictions.
.1.3.6.1.2.1.178.1.1.6.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnAllowedType,INTEGER,not-accessible,,current,switch(1):node(2),This object specifies whether this row refers to Switch-to-Switch or Switch-to-Node connectivity, i.e., whether the corresponding instance of t11FcSpPoSwConnAllowedName specifies the name of a Switch or the name of a Node.
.1.3.6.1.2.1.178.1.1.6.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnPortNameOrAll,OCTET,not-accessible,,current,,This object specifies either the particular port to which this topology restriction applies, or if the value is the zero-length string, that the topology restriction applies to all ports on the particular Switch. In the FC-SP Policy Database, restrictions for a particular port are formatted within a Port Connectivity Entry of a Switch Connectivity Object, whereas restrictions for all ports on the Switch are specified in the main part of a Switch Connectivity Object, i.e., not in a Port Connectivity Entry.
.1.3.6.1.2.1.178.1.1.6.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnAllowedIndex,Unsigned32,not-accessible,,current,,When multiple rows in this table apply to the same port(s) in the same Switch's Switch Connectivity Object, this object provides a unique index value to distinguish between such rows.
.1.3.6.1.2.1.178.1.1.6.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnAllowedNameType,INTEGER,read-only,,current,nodeName(1):restrictedNodeName(2):portName(3):restrictedPortName(4):wildcard(5):restrictedWildcard(6),If the value of this object is 'wildcard' or 'restrictedWildcard', this row specifies whether connectivity is allowed/not allowed with entities not explicitly named by other rows. Otherwise, the combination of t11FcSpPoSwConnAllowedNameType and t11FcSpPoSwConnAllowedName specify the name of: - a Switch (if t11FcSpPoSwConnAllowedType = 'switch'), or - a Node (if t11FcSpPoSwConnAllowedType = 'node') to which connectivity is: - allowed by 'nodeName' and 'portName', - not allowed by 'restrictedNodeName' and 'restrictedPortName'.
.1.3.6.1.2.1.178.1.1.6.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoSwConnAllowedName,OCTET,read-only,,current,,If the value of t11FcSpPoSwConnAllowedNameType is 'wildcard' or 'restrictedWildcard', this object has the value '0000000000000000'h. Otherwise, the combination of t11FcSpPoSwConnAllowedNameType and t11FcSpPoSwConnAllowedName specify the name of: - a Switch (if t11FcSpPoSwConnAllowedType = 'switch'), or - a Node (if t11FcSpPoSwConnAllowedType = 'node') to which connectivity is allowed/restricted.
.1.3.6.1.2.1.178.1.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtTable,,not-accessible,,current,,A table of IP Management Entries in active IP Management List Objects. An IP Management List Object is a Fabric-wide Policy Object that describes which IP hosts are allowed to manage a Fabric. One IP Management List Object is represented by all of the rows of this table that have the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.1.7.1,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoIpMgmtEntryNameType:t11FcSpPoIpMgmtEntryNameLow:t11FcSpPoIpMgmtEntryNameHigh,current,,Each entry contains information about one IP Management Entry within the active IP Management List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The Policy Object Name of an IP Management Entry Policy Object is either an IPv6 Address Range or an IPv4 Address Range, where in each case, the range is specified as two addresses: the low and high ends of the range. In particular, since the Policy Object Name in this situation can only be an IPv6 Address Range or an IPv4 Address Range, it is represented here by three MIB objects defined as a (InetAddressType, InetAddress, InetAddress) tuple, in which the first address is the low end of the range, the second address is the high end of the range, and both addresses are of the type designated by InetAddressType. In theory, the use of t11FcSpPoIpMgmtEntryNameLow and t11FcSpPoIpMgmtEntryNameHigh (which both have the syntax of InetAddress) in the INDEX could cause the need for excessively long OIDs. In practice, this can't happen because FC-SP doesn't allow these objects to be specified as DNS names.
.1.3.6.1.2.1.178.1.1.7.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtEntryNameType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The combination of t11FcSpPoIpMgmtNameType, t11FcSpPoIpMgmtNameLow, and t11FcSpPoIpMgmtNameHigh specify the Internet address range of this IP Management Entry in the IP Management List Object. The FC-SP specification does not allow the use of a DNS domain name to specify the address at the lower end or at the higher end of the Internet address range, nor does it allow the specification of a zone index. Therefore, the type of address must be one of: 'ipv4', or 'ipv6'.
.1.3.6.1.2.1.178.1.1.7.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtEntryNameLow,OCTET,not-accessible,,current,,The lower end of an Internet address range. The type of this address is given by the corresponding instance of t11FcSpPoIpMgmtEntryNameType. The combination of t11FcSpPoIpMgmtNameType, t11FcSpPoIpMgmtNameLow, and t11FcSpPoIpMgmtNameHigh specify the Internet address range of this IP Management Entry in the IP Management List Object.
.1.3.6.1.2.1.178.1.1.7.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtEntryNameHigh,OCTET,not-accessible,,current,,The higher end of an Internet address range. The type of this address is given by the corresponding instance of t11FcSpPoIpMgmtEntryNameType. The combination of t11FcSpPoIpMgmtNameType, t11FcSpPoIpMgmtNameLow, and t11FcSpPoIpMgmtNameHigh specify the Internet address range of this IP Management Entry in the IP Management List Object.
.1.3.6.1.2.1.178.1.1.7.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtWkpIndex,Unsigned32,read-only,,current,,This object identifies the restrictions for IP management access by IP hosts in this range of IP addresses, specified as the set of Well-Known Protocols Access Descriptors contained in those rows of the t11FcSpPoWkpDescrTable for which the value of t11FcSpPoWkpDescrSpecifierIndex is the same as the value of this object. A value of zero indicates that this IP Management Entry does not identify a Well-Known Protocols Access Specifier.
.1.3.6.1.2.1.178.1.1.7.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoIpMgmtAttribute,OCTET,read-only,,current,,The name of an active Attribute Policy Object that is defined for this IP Management entry or the zero-length string. The zero-length string indicates that no Attribute Policy Object is defined for this IP Management entry.
.1.3.6.1.2.1.178.1.1.8,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrTable,,not-accessible,,current,,A table of the Well-Known Protocol Access Descriptors being used within active Policy Objects. A Well-Known Protocol Access Specifier is a list of Well-Known Protocol Access Descriptors each of which specifies a protocol number, a port number, and/or various flags specifying how IP management access is restricted. A Well-Known Protocol Transport Access Specifier is represented by all rows of this table that have the same values of fcmInstanceIndex, t11FcSpPoFabricIndex, and t11FcSpPoWkpDescrSpecifierIndex.
.1.3.6.1.2.1.178.1.1.8.1,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoWkpDescrSpecifierIndex:t11FcSpPoWkpDescrIndex,current,,Each entry contains information about one Well-Known Protocol Access Descriptor of a Well-Known Protocol Access Specifier used within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.1.8.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrSpecifierIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Well-Known Protocol Access Specifier within a Fabric.
.1.3.6.1.2.1.178.1.1.8.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Well-Known Protocol Access Descriptor within a Well-Known Protocol Access Specifier.
.1.3.6.1.2.1.178.1.1.8.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrFlags,BITS,read-only,,current,allow(0):wkpWildcard(1):destPortWildcard(2):readOnly(3),The flag bits that specify how access is to be limited by this Well-Known Protocol Access Descriptor: - allow -- IP management access using this protocol/port is allowed if this bit is set, and to be denied if this bit is not set. - wkpWildcard -- if this bit is set, the IP Protocol number of the Well-Known Protocol to be allowed/denied is specified by the value of t11FcSpPoWkpDescrWkpNumber. - destPortWildcard -- if this bit is set, the Destination (TCP/UDP) Port number of the Well-Known Protocol to be allowed/denied is specified by the value of t11FcSpPoWkpDescrDestPort. - readOnly -- if this bit is set, then access is to be granted only for reading.
.1.3.6.1.2.1.178.1.1.8.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrWkpNumber,Unsigned32,read-only,,current,,When the 'wkpWildcard' bit is set in the corresponding instance of t11FcSpPoWkpDescrFlags, this object specifies the IP protocol number of the Well-Known Protocol.
.1.3.6.1.2.1.178.1.1.8.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoWkpDescrDestPort,Unsigned32,read-only,,current,,When the 'destPortWildcard' bit is set in the corresponding instance of t11FcSpPoWkpDescrFlags, this object specifies the Destination (TCP/UDP) Port number of the Well-Known Protocol. When the 'destPortWildcard' bit is reset, this object is ignored (and can have the value zero).
.1.3.6.1.2.1.178.1.1.9,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribTable,,not-accessible,,current,,A table of the Attribute Policy Objects being used within active Policy Objects. In the FC-SP Policy Database, each Attribute Policy Object consists of an Attribute Object Name and a set of Attribute Entries. An active Attribute Policy Object is represented by all the Attribute Entries in this table that have the same value of t11FcSpPoAttribName.
.1.3.6.1.2.1.178.1.1.9.1,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoAttribName:t11FcSpPoAttribEntryIndex:t11FcSpPoAttribPartIndex,current,,Each row contains information specific to an Attribute Entry contained within an Attribute Policy Object that is active within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. For some types of Attribute Policy Objects, it is valuable to break out some semantically significant parts of the Policy Object's value into their own individual MIB objects; for example, to extract the one or more individual Authentication Protocol Identifiers and associated Authentication Protocol Parameters out of an Attribute Object containing a 'AUTH_Negotiate Message Payload'. For such types, another MIB table is defined to hold the extracted values in MIB objects specific to the Attribute Policy Object's type. In such cases, the t11FcSpPoAttribExtension object in this table points to the other MIB table. If the value of one Attribute Entry is too large (more than 256 bytes) to be contained within the value of one instance of t11FcSpPoAttribValue, then one row in this table contains the first 256 bytes, and one (or more) other row(s) in this table contain the rest of the value.
.1.3.6.1.2.1.178.1.1.9.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribName,OCTET,not-accessible,,current,,The name of the Attribute Policy Object containing one or more Attribute Entries.
.1.3.6.1.2.1.178.1.1.9.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribEntryIndex,Unsigned32,not-accessible,,current,,A unique value to distinguish this Attribute Entry from other Attribute Entries contained in the same Attribute Policy Object.
.1.3.6.1.2.1.178.1.1.9.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribPartIndex,Unsigned32,not-accessible,,current,,When the value of an Attribute Entry is shorter than 257 bytes, the whole value is contained in one instance of t11FcSpPoAttribValue, and the value of this object is 1. If the value of an Attribute Entry is longer than 256 bytes, then that value is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, with each such part contained in a separate row of this table, and the value of this object is set to the part number. That is, this object has the value of 1 for bytes 0-255, the value of 2 for bytes 256-511, etc.
.1.3.6.1.2.1.178.1.1.9.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribType,Unsigned32,read-only,,current,,The type of attribute. The first type to be defined is: t11FcSpPoAttribType t11FcSpPoAttribValue =================== ==================== '00000001'h The AUTH_Negotiate Message Payload 
.1.3.6.1.2.1.178.1.1.9.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribValue,OCTET,read-only,,current,,The value of an Attribute Entry is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, and each such part is contained in a separate instance of this object. The value of this object is independent of whether some parts of its value are broken out into separate MIB objects pointed to by the corresponding instance of t11FcSpPoAttribExtension.
.1.3.6.1.2.1.178.1.1.9.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoAttribExtension,OBJECT,read-only,,current,,For some types of Attribute Policy Object, the value of this MIB object points to type-specific MIB objects that contain individual/broken-out parts of the Attribute Policy Object's value. If this object doesn't point to such type-specific MIB objects, then it contains the value: zeroDotZero. In particular, when the value of t11FcSpPoAttribType indicates 'AUTH_Negotiate Message Payload', one or more Authentication Protocol Identifiers and their associated Authentication Protocol Parameters are embedded within the value of the corresponding instance of t11FcSpPoAttribValue; MIB objects to contain these individual values are defined in the t11FcSpPoAuthProtTable. Thus, for an 'AUTH_Negotiate Message Payload' Attribute, the value of this object contains an OID within the t11FcSpPoAuthProtTable, e.g., of the whole table, of an individual row, or of an individual instance within the table.
.1.3.6.1.2.1.178.1.1.10,T11-FC-SP-POLICY-MIB::t11FcSpPoAuthProtTable,,not-accessible,,current,,A table of Authentication Protocol Identifier and Authentication Protocol Parameters that are embedded in Attribute Policy Objects being used within active Policy Objects. This table is used for Attribute Entries of Attribute Policy Objects for which the value of t11FcSpPoAttribType indicates 'AUTH_Negotiate Message Payload' and the value of t11FcSpPoAttribExtension contains the OID of this table.
.1.3.6.1.2.1.178.1.1.10.1,T11-FC-SP-POLICY-MIB::t11FcSpPoAuthProtEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoAttribName:t11FcSpPoAttribEntryIndex:t11FcSpPoAuthProtIdentifier:t11FcSpPoAuthProtPartIndex,current,,Each entry contains information about an Authentication Protocol that is extracted out of the Attribute Entry (identified by t11FcSpPoAttribEntryIndex) of the Policy Attribute Object (identified by t11FcSpPoAttribName), which is active within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. If the value of one Attribute Protocol Parameters string is too large (more than 256 bytes) to be contained within the value of one instance of t11FcSpPoAuthProtParams, then one row in this table contains the first 256 bytes, and one (or more) other row(s) in this table contain the rest of the value.
.1.3.6.1.2.1.178.1.1.10.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoAuthProtIdentifier,Unsigned32,not-accessible,,current,,The Authentication Protocol Identifier: 1 = DH-CHAP 2 = FCAP 3 = FCPAP 4 = IKEv2 5 = IKEv2-AUTH 240 thru 255 = Vendor Specific Protocols all other values are 'Reserved' (by T11).
.1.3.6.1.2.1.178.1.1.10.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoAuthProtPartIndex,Unsigned32,not-accessible,,current,,When the value of an Attribute Protocol Parameters string is shorter than 257 bytes, the whole value is contained in one instance of t11FcSpPoAuthProtParams, and the value of this object is 1. (This includes the case when the Attribute Protocol Parameters string is zero bytes in length.) If the value of an Authentication Protocol Parameters string is longer than 256 bytes, then that value is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, with each such part contained in a separate row of this table, and the value of this object is set to the part number. That is, this object has the value of 1 for bytes 0-255, the value of 2 for bytes 256-511, etc.
.1.3.6.1.2.1.178.1.1.10.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoAuthProtParams,OCTET,read-only,,current,,The value of an Authentication Protocol Parameters string is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, and each such part is contained in a separate instance of this object.
.1.3.6.1.2.1.178.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoOperations,,,,,,
.1.3.6.1.2.1.178.1.2.1,T11-FC-SP-POLICY-MIB::t11FcSpPoOperTable,,not-accessible,,current,,A table that allows Activate and Deactivate operations to be invoked for FC-SP Policies on various Fabrics. Activating a new policy configuration is a two-step process: 1) create a single Policy Summary Object as a set of rows in the t11FcSpPoNaSummaryTable specifying a set of Policy Objects that describe the new configuration; and 2) activate that Policy Summary Object using the t11FcSpPoOperActivate object defined in this table. Deactivating the current policy configuration is a one-step process: the current Policy Summary Object is deactivated using the t11FcSpPoOperDeActivate object.
.1.3.6.1.2.1.178.1.2.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoOperEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex,current,,Each entry allows an Activate and/or Deactivate operation to be invoked on a particular Fabric, which is managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.2.1.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoOperActivate,OCTET,read-write,,current,,Writing the name of a Policy Summary Object into this object is a request to activate the policy configuration described by the combination of all rows in t11FcSpPoNaSummaryTable that have that name as their value of t11FcSpPoNaSummaryName and are for the same Fabric. Before issuing such a request, the relevant rows in the t11FcSpPoNaSummaryTable must exist and represent a complete and consistent Policy Summary Object. If they do not, the request will fail, with t11FcSpPoOperResult having the 'badSummaryObject' value. When read, the value of this object is always the zero- length string. Writing to this object does not delete (or in any way affect) any rows in the MIB tables for non-active Policy Objects.
.1.3.6.1.2.1.178.1.2.1.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoOperDeActivate,OCTET,read-write,,current,,Writing the current value of t11FcSpPoPolicySummaryObjName into this object (for a particular Fabric) is a request to deactivate that Fabric's current policy configuration. Writing any other value into this object is an error (e.g., 'wrongValue'). When read, the value of this object is always the zero- length string.
.1.3.6.1.2.1.178.1.2.1.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoOperResult,INTEGER,read-only,,current,activateSuccess(1):badSummaryObject(2):activateFailure(3):deactivateSuccess(4):deactivateFailure(5):inProgress(6):none(7),This object indicates the status/result of the last activation/deactivation that was invoked via the corresponding instance of t11FcSpPoOperActivate or t11FcSpPoOperDeActivate. When the value of this object is 'inProgress', the values of the corresponding instances of t11FcSpPoOperActivate and t11FcSpPoOperDeActivate cannot be modified. The value 'badSummaryObject' indicates an activation request that did not name a complete and consistent Policy Summary Object. The value 'none' indicates activation/deactivation has not been attempted since the last restart of the management system.
.1.3.6.1.2.1.178.1.2.1.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoOperFailCause,OCTET,read-only,,current,,A textual message indicating the reason for the most recent activation/deactivation failure, or the zero-length string if no information is available (e.g., because the corresponding instance of t11FcSpPoOperResult has the value 'none'). When the corresponding instance of t11FcSpPoOperResult is either 'activateFailure' or 'deactivateFailure', the value of this object indicates the reason for that failure.
.1.3.6.1.2.1.178.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNonActive,,,,,,
.1.3.6.1.2.1.178.1.3.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryTable,,not-accessible,,current,,A table of non-active Policy Summary Objects available to be activated. The functionality of this table deviates slightly from FC-SP in that FC-SP specifies that the only Policy Summary Object is the Active one, i.e., FC-SP does not store non-active Policy Summary Objects in the Policy Database. Instead, FC-SP requires a new Policy Summary Object to be created for, and embedded within, every Activate (APS) request. Thus, the newly created Policy Summary Object outlasts the APS request only as the new active Policy Summary Object and only if the APS succeeds. In contrast, the Activate operation provided by this MIB module consists of two steps: 1) create a non-active Policy Summary Object as a set of entries in this table describing a new configuration; 2) activate a Policy Summary Object (stored as a set of entries in this table) using t11FcSpPoOperActivate. These two steps are only loosely connected, i.e., the result of the first operation is a non-active Policy Summary Object that is retained (in this table) even if it isn't immediately activated. Even after an attempt to activate it succeeds or fails, a non-active Policy Summary Object is not deleted, but is retained and still available for subsequent modification/re-use.
.1.3.6.1.2.1.178.1.3.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaSummaryName:t11FcSpPoNaSummaryPolicyType:t11FcSpPoNaSummaryPolicyIndex,current,,Each entry contains information about one non-active Policy Object within a non-active Policy Summary Object defined for potential use on the Fabric identified by t11FcSpPoFabricIndex, and managed within the Fibre Channel management instance identified by fcmInstanceIndex. A non-active Policy Summary Object is described by a set of entries in this table that have the same value of t11FcSpPoNaSummaryName. As and when a Policy Summary Object is activated using the t11FcSpPoOperActivate object, if the activation is successful, existing rows (if any) in MIB tables for active Policy Objects are deleted and replaced by the appropriate new set of rows. Existing rows in this table and/or in other tables for non-active Policy Objects are not affected by the activate operation. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.1.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryName,OCTET,not-accessible,,current,,The name of the non-active Policy Summary Object that contains this Policy Object.
.1.3.6.1.2.1.178.1.3.1.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryPolicyType,INTEGER,not-accessible,,current,summary(1):switchMemberList(2):nodeMemberList(3):switchConnectivity(4):ipMgmtList(5):attribute(6),The 'Identifier' (i.e., the type) of this Policy Object.
.1.3.6.1.2.1.178.1.3.1.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryPolicyIndex,Unsigned32,not-accessible,,current,,A unique integer value to distinguish this Policy Object from any others that have the same type and that are contained in the same Policy Summary Object.
.1.3.6.1.2.1.178.1.3.1.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryPolicyNameType,INTEGER,read-create,,current,nodeName(1):alphaNumericName(7),The combination of t11FcSpPoNaSummaryPolicyNameType and t11FcSpPoNaSummaryPolicyName specify the name of the non-active Policy Object identified by this row. The type of name must be 'nodeName' if the value of the corresponding instance of t11FcSpPoNaSummaryPolicyType is 'switchConnectivity', or 'alphaNumericName' otherwise.
.1.3.6.1.2.1.178.1.3.1.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryPolicyName,OCTET,read-create,,current,,The combination of t11FcSpPoNaSummaryPolicyNameType and t11FcSpPoNaSummaryPolicyName specify the name of the non-active Policy Object identified by this row.
.1.3.6.1.2.1.178.1.3.1.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryHashStatus,INTEGER,read-create,,current,calculate(1):correct(2):stale(3),When read, the value of this object is either: correct -- the corresponding instance of t11FcSpPoNaSummaryHashValue contains the correct value; or stale -- the corresponding instance of t11FcSpPoNaSummaryHashValue contains a stale (possibly incorrect) value; Writing a value of 'calculate' is a request to re-calculate and update the value of the corresponding instance of t11FcSpPoNaSummaryHashValue. Writing a value of 'correct' or 'stale' to this object is an error (e.g., 'wrongValue').
.1.3.6.1.2.1.178.1.3.1.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryHashFormat,OCTET,read-only,,current,,The format of this Policy Object's hash value as contained in the corresponding instance of the t11FcSpPoNaSummaryHashValue object.
.1.3.6.1.2.1.178.1.3.1.1.8,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryHashValue,OCTET,read-only,,current,,The hash value of this Policy Object, in the format identified by the corresponding instance of the t11FcSpPoNaSummaryHashFormat object.
.1.3.6.1.2.1.178.1.3.1.1.9,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSummaryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Before a row in this table can have 'active' status, a non-Active Policy Object must already be represented in the table corresponding to the value of t11FcSpPoNaSummaryPolicyType with the name given by the combination of t11FcSpPoNaSummaryPolicyNameType and t11FcSpPoNaSummaryPolicyName. If such a Policy Object gets deleted from the relevant table, the row in this table must also get deleted. When a row has 'active' status, the only write-able MIB objects in this table are t11FcSpPoNaSummaryHashStatus and t11FcSpPoNaSummaryRowStatus.
.1.3.6.1.2.1.178.1.3.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwListTable,,not-accessible,,current,,A table of non-active Switch Membership List Objects.
.1.3.6.1.2.1.178.1.3.2.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwListEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaSwListName,current,,Each entry contains information about one non-active Switch Membership List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.2.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwListName,OCTET,not-accessible,,current,,The name of the Switch Membership List Object.
.1.3.6.1.2.1.178.1.3.2.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwListFabricName,OCTET,read-create,,current,,The administratively specified Fabric_Name. This value is meaningful only when static Domain_IDs are used in a Fabric. If Static Domain_IDs are not used, the Fabric_Name is dynamically determined, in which case the value of this object can be '0000000000000000'h or the zero-length string.
.1.3.6.1.2.1.178.1.3.2.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwListRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time. If a row in this table is deleted, any row in the t11FcSpPoNaSwMembTable for the same Switch Membership List Object will also get deleted.
.1.3.6.1.2.1.178.1.3.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembTable,,not-accessible,,current,,A table of Switch Entries in non-active Switch Membership List Objects.
.1.3.6.1.2.1.178.1.3.3.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaSwListName:t11FcSpPoNaSwMembSwitchNameType:t11FcSpPoNaSwMembSwitchName,current,,Each entry contains information about one Switch that is listed in a Switch Entry of a non-active Switch Membership List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. A row cannot exist unless there is a row in t11FcSpPoNaSwListTable for the given Switch Membership List Object, i.e., the row in t11FcSpPoNaSwListTable for a Switch Membership List Object must be created before (or simultaneously with) a row in this table for a Switch Entry in that Switch Membership List Object, and when a row in t11FcSpPoNaSwListTable is deleted, all rows in this table for Switch Entries in that Switch Membership List Object also get deleted. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.3.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembSwitchNameType,INTEGER,not-accessible,,current,nodeName(1):restrictedNodeName(2):wildcard(5):restrictedWildcard(6),If the value of this object is 'nodeName' or 'restrictedNodeName', then the combination of this object and t11FcSpPoNaSwMembSwitchName specify the Switch Name of this Switch Entry. The membership is restricted or unrestricted based on the name type. Restricted membership means that the Switch is not allowed to be part of the Fabric unless allowed by a specific Switch Connectivity Object. Unrestricted membership means that the Switch is allowed to be part of the Fabric unless disallowed by a specific Switch Connectivity Object. The values of 'wildcard' and 'restrictedWildcard' provide the means to specify whether to allow/deny membership for Switches not explicitly named in the Switch Membership List Object.
.1.3.6.1.2.1.178.1.3.3.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembSwitchName,OCTET,not-accessible,,current,,If the value of t11FcSpPoSwMembSwitchNameType is 'wildcard' or 'restrictedWildcard', this object has the value '0000000000000000'h. Otherwise, the combination of t11FcSpPoNaSwMembSwitchNameType and this object specify the Switch Name of this Switch Entry.
.1.3.6.1.2.1.178.1.3.3.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembFlags,BITS,read-create,,current,staticDomainID(0):insistentDomainID(1):serialPortsAccess(2):physicalPortsAccess(3):managerRole(4),Configurable options in respect to the administration of Policy Objects at this Switch: 'staticDomainID' - the Switch uses the 'Static Domain_IDs behavior' (as defined in FC-SW-4) when this bit is set. This bit should have the same setting for all Switches in a Fabric's Switch Membership List Object, or else the Fabric will partition. If this bit is set, the 'insistentDomainID' bit must not be set. 'insistentDomainID' - if this bit is set, the Switch uses the 'Insistent Domain_IDs behavior' (as defined in FC-SW-4), and the 'staticDomainID' bit must not be set. 'serialPortsAccess' - the Switch allows management through serial ports when and only when this bit is set. 'physicalPortsAccess' - the Switch allows management through the physical panel when and only when this bit is set. 'managerRole' - the Switch is allowed to change the Fabric Policy configuration (on receipt of any of the EACA, ESFC, EUFC, ACA, SFC, or UFC SW_ILSs) if this bit is set.
.1.3.6.1.2.1.178.1.3.3.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembDomainID,Integer32,read-create,,current,,The Domain_ID to be used when either the 'staticDomainID' bit or the 'insistentDomainID' bit is set in the corresponding value of t11FcSpPoNaSwMembFlags.
.1.3.6.1.2.1.178.1.3.3.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembPolicyDataRole,INTEGER,read-create,,current,client(1):autonomous(2):server(3),The role of the Switch in terms of which Policy data it retains/maintains: 'client' - the Switch operates as a Client Switch. A Client Switch maintains its own Switch Connectivity Object and all Fabric-wide List Objects. If FC-SP Zoning is used, a Client Switch maintains only the subset of the Active Zone Set that it requires to enforce the current Fabric Zoning configuration. 'autonomous' - the Switch operates as an Autonomous Switch. An Autonomous Switch maintains its own Switch Connectivity Object and all Fabric-wide List Objects. This is the same as 'client' except that if FC-SP Zoning is used, an Autonomous Switch maintains a complete copy of the Fabric Zoning Database. 'server' - the Switch operates as a Server Switch. A Server Switch maintains all Fabric-wide List Objects and the Switch Connectivity Objects of each Switch in the Fabric. If FC-SP Zoning is used, a Server Switch maintains a complete copy of the Fabric Zoning Database.
.1.3.6.1.2.1.178.1.3.3.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembAuthBehaviour,BITS,read-create,,current,mustAuthenticate(0):rejectIsFailure(1),The authentication behaviour of the Switch: 'mustAuthenticate' - if this bit is set, all connections between this Switch and neighbor Switches must be authenticated. 'rejectIsFailure' - if this bit is set, the rejection of an AUTH_Negotiate message must be considered as an authentication failure by this Switch.
.1.3.6.1.2.1.178.1.3.3.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembAttribute,OCTET,read-create,,current,,The name of a non-active Attribute Policy Object that is defined for this Switch. The zero-length string indicates that no non-active Attribute Policy Object is defined for this Switch. The effect of having no rows in the t11FcSpPoNaAttribTable for which the value of t11FcSpPoNaAttribName is the same as the value of this object, is the same as this object's value being the zero-length string.
.1.3.6.1.2.1.178.1.3.3.1.8,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwMembRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time. A row cannot exist unless there is a row in the t11FcSpPoNaSwListTable for the Switch Membership List Object containing the Switch Entry for this Switch, i.e., the row in t11FcSpPoNaSwListTable for a Switch Membership List Object must be created before (or simultaneously) with a row in this table for a Switch Entry in that Switch Membership List Object; and when a row in t11FcSpPoNaSwListTable is deleted, any row in this table for a Switch Entry in that Switch Membership List Object also gets deleted.
.1.3.6.1.2.1.178.1.3.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembTable,,not-accessible,,current,,A table of Node Entries in non-active Node Membership List Objects. One Node Membership List Object is represented by all the rows in this table that have the same value of t11FcSpPoNaNoMembListName.
.1.3.6.1.2.1.178.1.3.4.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaNoMembListName:t11FcSpPoNaNoMembNodeNameType:t11FcSpPoNaNoMembNodeName,current,,Each entry contains information about one Node Entry of a non-active Node Membership List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.4.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembListName,OCTET,not-accessible,,current,,The name of the non-active Node Membership List Object.
.1.3.6.1.2.1.178.1.3.4.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembNodeNameType,INTEGER,not-accessible,,current,nodeName(1):restrictedNodeName(2):portName(3):restrictedPortName(4):wildcard(5):restrictedWildcard(6),If the value of this object is 'wildcard' or 'restrictedWildcard', this Node Entry applies to Nodes not explicitly named in the Node Membership List Object. Otherwise, the combination of this object and t11FcSpPoNaNoMembNodeName specify the name of this Node Entry in the active Node Membership List Object. A Node is identified by its Node Name or by one or more of its Port Names. Restricted membership means that a Node is not allowed to be connected to the Fabric unless allowed by a specific Switch Connectivity Object. Unrestricted membership means that a Node is allowed to be connected to the Fabric unless disallowed by a specific Switch Connectivity Object.
.1.3.6.1.2.1.178.1.3.4.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembNodeName,OCTET,not-accessible,,current,,If the value of t11FcSpPoNaNoMembNodeNameType is 'wildcard' or 'restrictedWildcard', this object has the value '0000000000000000'h. Otherwise, the combination of t11FcSpPoNaNoMembNodeNameType and this object specify the name of this Node Entry is the active Node Membership List Object.
.1.3.6.1.2.1.178.1.3.4.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembFlags,BITS,read-create,,current,scsiEnclosureAccess(0):authenticationRequired(1),Configurable options in respect to the administration of Policy Objects at this Node: 'scsiEnclosureAccess' - the Node is allowed to control any Switch through SCSI Enclosure Services if this bit is set. If a Switch does not support SCSI Enclosure Services, this bit is ignored. 'authenticationRequired' - the Node is required to authenticate itself to any Switch to which it is connected if and only if this bit is set.
.1.3.6.1.2.1.178.1.3.4.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembCtAccessIndex,Unsigned32,read-create,,current,,If the value of this object is zero, then access by this Node to Generic Services is not limited by a Common Transport Access Specifier. Otherwise, the limits are specified by the set of Common Transport Access Descriptors contained in those rows of the t11FcSpPoNaCtDescrTable for which the value of t11FcSpPoNaCtDescrSpecifierIndex is the same as the value of this object. No such rows in t11FcSpPoNaCtDescrTable have the same effect as this object's value being zero.
.1.3.6.1.2.1.178.1.3.4.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembAttribute,OCTET,read-create,,current,,The name of a non-active Attribute Policy Object that is defined for this Node. The zero-length string indicates that no non-active Attribute Policy Object is defined for this Node. The effect of having no rows in the t11FcSpPoNaAttribTable for which the value of t11FcSpPoNaAttribName is the same as the value of this object, is the same as this object's value being the zero-length string.
.1.3.6.1.2.1.178.1.3.4.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaNoMembRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.3.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrTable,,not-accessible,,current,,A table of Common Transport Access Descriptors referenced by non-active Policy Objects. A Common Transport Access Specifier is a list of Common Transport Access Descriptors that specify whether a Node is allowed to access a Generic Service or Sub-Server. A non-active Common Transport Access Specifier is represented by all rows of this table that have the same values of fcmInstanceIndex, t11FcSpPoFabricIndex, and t11FcSpPoNaCtDescrSpecifierIndex.
.1.3.6.1.2.1.178.1.3.5.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaCtDescrSpecifierIndex:t11FcSpPoNaCtDescrIndex,current,,Each entry contains information about one Common Transport Access Descriptor of an non-active Common Transport Access Specifier used within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.5.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrSpecifierIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Common Transport Access Specifier within a Fabric.
.1.3.6.1.2.1.178.1.3.5.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Common Transport Access Descriptor within a Common Transport Access Specifier.
.1.3.6.1.2.1.178.1.3.5.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrFlags,BITS,read-create,,current,allow(0):gsTypeWildcard(1):gsSubTypeWildcard(2):readOnly(3),The flag bits that specify how access is to be limited by this Common Transport Access Descriptor: - allow -- access to the specified Generic Service and Server is allowed if this bit is set, and is to be denied if this bit is not set. - gsTypeWildcard -- if this bit is set, the Generic Service to be allowed/denied is specified by the value of t11FcSpPoNaCtDescrGsType, and the gsSubTypeWildcard bit must not also be set. - gsSubTypeWildcard -- if this bit is set, the Generic Service to be allowed/denied is specified by the value of t11FcSpPoNaCtDescrGsSubType, and the gsTypeWildcard bit must not also be set. - readOnly -- if this bit is set, then access is to be granted only for reading.
.1.3.6.1.2.1.178.1.3.5.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrGsType,OCTET,read-create,,current,,The GS_Type of the Generic Service (e.g., the FC-GS-5 Management Service) that is subject to access control. This value is ignored if the gsTypeWildcard bit is not set in the corresponding value of t11FcSpPoNaCtDescrFlags.
.1.3.6.1.2.1.178.1.3.5.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrGsSubType,OCTET,read-create,,current,,The GS_Subtype of the Generic Server (e.g., the Fabric Zone Server) that is subject to access control. This value is ignored if the gsSubTypeWildcard bit is not set in the corresponding value of t11FcSpPoNaCtDescrFlags.
.1.3.6.1.2.1.178.1.3.5.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaCtDescrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.3.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnTable,,not-accessible,,current,,A table of non-active Switch Connectivity Objects. A Switch Connectivity Object defines to which other Switches or Nodes a particular Switch may/may not be connected at the Node level and/or at the Port level.
.1.3.6.1.2.1.178.1.3.6.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaSwConnSwitchName:t11FcSpPoNaSwConnAllowedType:t11FcSpPoNaSwConnPortNameOrAll:t11FcSpPoNaSwConnAllowedIndex,current,,Each entry contains the name of a Switch/Node with which any port of a particular Switch on a particular Fabric, or a particular port on that Switch, is allowed or not allowed to be connected. The particular Fabric is identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.6.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnSwitchName,OCTET,not-accessible,,current,,The name of the Switch for which this Switch Connectivity Object specifies topology restrictions.
.1.3.6.1.2.1.178.1.3.6.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnAllowedType,INTEGER,not-accessible,,current,switch(1):node(2),This object specifies whether this row refers to an 'Allowed Switch' that concerns Switch-to-Switch connectivity or an 'Allowed Node' that concerns Switch-to-Node connectivity. Consequently, this object's value indicates whether the corresponding instance of t11FcSpPoNaSwConnAllowedName specifies the name of a Switch or the name of a Node.
.1.3.6.1.2.1.178.1.3.6.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnPortNameOrAll,OCTET,not-accessible,,current,,This object specifies either the particular port on which this topology restriction applies, or if the value is the zero-length string, that the topology restriction applies to all ports of the Switch. In other words, if this object's value contains the name of a port, then this row represents a 'Port Connectivity Entry' (as described in FC-SP) within a Switch Connectivity Object.
.1.3.6.1.2.1.178.1.3.6.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnAllowedIndex,Unsigned32,not-accessible,,current,,When multiple rows in this table refer to different 'Allowed Switches' or to different 'Allowed Nodes' for the same port(s) in the same Switch Connectivity Object, this object provides a unique index value to distinguish between such rows.
.1.3.6.1.2.1.178.1.3.6.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnAllowedNameType,INTEGER,read-create,,current,nodeName(1):restrictedNodeName(2):portName(3):restrictedPortName(4):wildcard(5):restrictedWildcard(6),If the value of this object is 'wildcard' or 'restrictedWildcard', this row specifies whether connectivity is allowed/not allowed with entities not explicitly named by other rows. Otherwise, the combination of t11FcSpPoNaSwConnAllowedNameType and t11FcSpPoNaSwConnAllowedName specify the name of: - a Switch (if t11FcSpPoNaSwConnAllowedType = 'switch'), or - a Node (if t11FcSpPoNaSwConnAllowedType = 'node') to which connectivity is allowed/not allowed.
.1.3.6.1.2.1.178.1.3.6.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnAllowedName,OCTET,read-create,,current,,If t11FcSpPoNaSwConnAllowedNameType has the value 'wildcard' or 'restrictedWildcard', this object has the value '0000000000000000'h. Otherwise, the combination of t11FcSpPoNaSwConnAllowedNameType and t11FcSpPoNaSwConnAllowedName specify the name of: - a Switch (if t11FcSpPoNaSwConnAllowedType = 'switch'), or - a Node (if t11FcSpPoNaSwConnAllowedType = 'node') to which connectivity is allowed/not allowed.
.1.3.6.1.2.1.178.1.3.6.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaSwConnRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.3.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtTable,,not-accessible,,current,,A table of IP Management Entries in non-active IP Management List Objects. The IP Management List Object is a Fabric-wide Policy Object that describes which IP hosts are allowed to manage a Fabric. One non-active IP Management List Object is represented by all rows of this table that have the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.7.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaIpMgmtListName:t11FcSpPoNaIpMgmtEntryNameType:t11FcSpPoNaIpMgmtEntryNameLow:t11FcSpPoNaIpMgmtEntryNameHigh,current,,Each entry contains information about one IP Management entry within a non-active IP Management List Object for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The Policy Object Name of an IP Management Entry Policy Object is either an IPv6 Address Range or an IPv4 Address Range. In a Fabric's database of Policy Objects, every Policy Object Name, including these Internet address ranges, is represented as a (T11FcSpPolicyNameType, T11FcSpPolicyName) tuple. In contrast, this MIB module uses the conventional MIB syntax for IP addresses, and therefore represents the Policy Object Name of an IP Management Entry Policy Object as a (InetAddressType, InetAddress, InetAddress) tuple. In theory, the use of t11FcSpPoNaIpMgmtEntryNameLow and t11FcSpPoNaIpMgmtEntryNameHigh, which have the syntax of InetAddress, in the INDEX could cause the need for excessively long OIDs. In practice, this can't happen because FC-SP doesn't allow these objects to be specified as DNS names. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.7.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtListName,OCTET,not-accessible,,current,,The name of a non-active Node Membership List Object.
.1.3.6.1.2.1.178.1.3.7.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtEntryNameType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The combination of t11FcSpPoNaIpMgmtEntryNameType, t11FcSpPoNaIpMgmtNameLow, and t11FcSpPoNaIpMgmtNameHigh specify the Internet address range of this IP Management Entry in the IP Management List Object. The FC-SP specification does not allow this address to be specified using a DNS domain name, nor does it allow the specification of zone indexes. Therefore, the type of address must be one of: 'ipv4' or 'ipv6'.
.1.3.6.1.2.1.178.1.3.7.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtEntryNameLow,OCTET,not-accessible,,current,,The lower end of an Internet address range. The type of this address is given by the corresponding instance of t11FcSpPoNaIpMgmtEntryNameType. The combination of t11FcSpPoNaIpMgmtEntryNameType, t11FcSpPoNaIpMgmtNameLow, and t11FcSpPoIpMgmtNameHigh specify the Internet address range of this IP Management Entry in the IP Management List Object.
.1.3.6.1.2.1.178.1.3.7.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtEntryNameHigh,OCTET,not-accessible,,current,,The higher end of an Internet address range. The type of this address is given by the corresponding instance of t11FcSpPoNaIpMgmtEntryNameType. The combination of t11FcSpPoNaIpMgmtEntryNameType, t11FcSpPoNaIpMgmtNameLow, and t11FcSpPoNaIpMgmtNameHigh specify the Internet address range of this IP Management Entry in the IP Management List Object.
.1.3.6.1.2.1.178.1.3.7.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtWkpIndex,Unsigned32,read-create,,current,,This object identifies the restrictions for IP management access by IP hosts in this range of IP addresses. The restrictions are specified as the set of Well-Known Protocols Access Descriptors contained in those rows of the t11FcSpPoNaWkpDescrTable for which the value of t11FcSpPoNaWkpDescrSpecifierIndx is the same as the value of this object. If there are no such rows or if the value of this object is zero, then this IP Management Entry does not identify any Well-Known Protocols Access restrictions.
.1.3.6.1.2.1.178.1.3.7.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtAttribute,OCTET,read-create,,current,,The name of a non-active Attribute Policy Object that is defined for this IP Management entry. The zero-length string indicates that no non-active Attribute Policy Object is defined for it. The effect of having no rows in the t11FcSpPoNaAttribTable for which the value of t11FcSpPoNaAttribName is the same as the value of this object, is the same as this object's value being the zero-length string.
.1.3.6.1.2.1.178.1.3.7.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaIpMgmtRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.3.8,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrTable,,not-accessible,,current,,A table of the Well-Known Protocol Access Descriptors referenced from non-active Policy Objects. A Well-Known Protocol Access Specifier is a list of Well-Known Protocol Access Descriptors each of which specifies a protocol number, a port number, and/or various flags specifying how IP management access is restricted. A non-active Well-Known Protocol Transport Access Specifier is represented by all rows of this table that have the same values of fcmInstanceIndex, t11FcSpPoFabricIndex, and t11FcSpPoNaWkpDescrSpecifierIndx.
.1.3.6.1.2.1.178.1.3.8.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaWkpDescrSpecifierIndx:t11FcSpPoNaWkpDescrIndex,current,,Each entry contains information about one Well-Known Protocol Access Descriptor of a non-active Well-Known Protocol Access Specifier used within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.8.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrSpecifierIndx,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular non-active Well-Known Protocol Access Specifier within a Fabric.
.1.3.6.1.2.1.178.1.3.8.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Well-Known Protocol Access Descriptor within a non-active Well-Known Protocol Access Specifier.
.1.3.6.1.2.1.178.1.3.8.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrFlags,BITS,read-create,,current,allow(0):wkpWildcard(1):destPortWildcard(2):readOnly(3),The flag bits that specify how access is to be limited by this Well-Known Protocol Access Descriptor: - allow -- IP management access using this protocol/port is allowed if this bit is set, and to be denied if this bit is not set. - wkpWildcard -- if this bit is set, the IP Protocol number of the Well-Known Protocol to be allowed/denied is specified by the value of t11FcSpPoNaWkpDescrWkpNumber. - destPortWildcard -- if this bit is set, the Destination (TCP/UDP) Port number of the Well-Known Protocol to be allowed/denied is specified by the value of t11FcSpPoNaWkpDescrDestPort. - readOnly -- if this bit is set, then access is to be granted only for reading.
.1.3.6.1.2.1.178.1.3.8.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrWkpNumber,Unsigned32,read-create,,current,,When the 'wkpWildcard' bit is set in the corresponding instance of t11FcSpPoNaWkpDescrFlags, this object specifies the IP protocol number of the Well-Known Protocol.
.1.3.6.1.2.1.178.1.3.8.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrDestPort,Unsigned32,read-create,,current,,When the 'destPortWildcard' bit is set in the corresponding instance of t11FcSpPoNaWkpDescrFlags, this object specifies the Destination (TCP/UDP) Port number of the Well-Known Protocol. When the 'destPortWildcard' bit is reset, this object is ignored (and can have the value zero).
.1.3.6.1.2.1.178.1.3.8.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaWkpDescrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.3.9,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribTable,,not-accessible,,current,,A table of the Attribute Policy Objects being used within non-active Policy Objects. A non-active Attribute Policy Object is represented by all the Attribute Entries in this table that have the same value of t11FcSpPoNaAttribName.
.1.3.6.1.2.1.178.1.3.9.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaAttribName:t11FcSpPoNaAttribEntryIndex:t11FcSpPoNaAttribPartIndex,current,,Each entry contains information about one Attribute Entry contained within an Attribute Policy Object that is non-active within the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. For some types of Attribute Policy Objects, it is valuable to break out some semantically significant parts of the Policy Object's value into their own individual MIB objects; for example, to extract the one or more individual Authentication Protocol Identifiers and associated Authentication Protocol Parameters out of an Attribute containing a 'AUTH_Negotiate Message Payload'. For such types, another MIB table is defined to hold the extracted values in MIB objects specific to the Attribute Policy Object's type. In such cases, the t11FcSpPoNaAttribExtension object in this table points to the other MIB table. If the value of one Attribute Entry is too large (more than 256 bytes) to be contained within the value of one instance of t11FcSpPoNaAttribValue, then one row in this table contains the first 256 bytes, and one (or more) other row(s) in this table contain the rest of the value. The StorageType of a row in this table is specified by the instance of t11FcSpPoStorageType that is INDEX-ed by the same values of fcmInstanceIndex and t11FcSpPoFabricIndex.
.1.3.6.1.2.1.178.1.3.9.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribName,OCTET,not-accessible,,current,,The name of the Attribute Policy Object containing one or more Attribute Entries.
.1.3.6.1.2.1.178.1.3.9.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribEntryIndex,Unsigned32,not-accessible,,current,,A unique value to distinguish this Attribute Entry from other Attribute Entries contained in the same Attribute Policy Object.
.1.3.6.1.2.1.178.1.3.9.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribPartIndex,Unsigned32,not-accessible,,current,,When the value of an Attribute Entry is shorter than 257 bytes, the whole value is contained in one instance of t11FcSpPoNaAttribValue, and the value of this object is 1. If the value of an Attribute Entry is longer than 256 bytes, then that value is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part which is shorter if necessary, with each such part contained in a separate row of this table, and the value of this object is set to the part number. That is, this object has the value of 1 for bytes 0-255, the value of 2 for bytes 256-511, etc.
.1.3.6.1.2.1.178.1.3.9.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribType,Unsigned32,read-create,,current,,The type of attribute. The first type to be defined is: t11FcSpPoNaAttribType t11FcSpPoNaAttribValue ===================== ====================== '00000001'h The AUTH_Negotiate Message Payload 
.1.3.6.1.2.1.178.1.3.9.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribValue,OCTET,read-create,,current,,The value of an Attribute Entry is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, and each such part is contained in a separate instance of this object. When the value of the corresponding instance of t11FcSpPoNaAttribExtension is not zeroDotZero, then the same underlying management data has its value contained both in this object and in the individual/broken-out parts pointed to by t11FcSpPoNaAttribExtension. Thus, after any modification of the underlying management data, e.g., after a Set operation to the value of either MIB representation, then that modification is reflected in the values of both MIB representations.
.1.3.6.1.2.1.178.1.3.9.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribExtension,OBJECT,read-only,,current,,For some types of Attribute Policy Object, the value of this MIB object points to type-specific MIB objects that contain individual/broken-out parts of the Attribute Policy Object's value. If this object doesn't point to such type-specific MIB objects, then it contains the value: zeroDotZero. In particular, when the value of t11FcSpPoNaAttribType indicates 'AUTH_Negotiate Message Payload', one or more Authentication Protocol Identifiers and their associated Authentication Protocol Parameters are embedded within the value of the corresponding instance of t11FcSpPoNaAttribValue; MIB objects to contain these individual values are defined in the t11FcSpPoAuthProtTable. Thus, for an 'AUTH_Negotiate Message Payload' Attribute, the value of this object would contain the OID of t11FcSpPoNaAuthProtTable. When the value of this object is not zeroDotZero, then the same underlying management data has its value contained in both the individual/broken-out parts pointed to by this object and in the corresponding instance of t11FcSpPoNaAttribValue. Thus, after any modification of the underlying management data, e.g., after a Set operation to the value of either MIB representation, then that modification is reflected in the values of both MIB representations.
.1.3.6.1.2.1.178.1.3.9.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAttribRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.3.10,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAuthProtTable,,not-accessible,,current,,A table of Authentication Protocol Identifier and Authentication Protocol Parameters that are embedded in Attribute Policy Objects being used within non-active Policy Objects. This table is used for Attribute Entries of Attribute Policy Objects for which the value of t11FcSpPoNaAttribType indicates 'AUTH_Negotiate Message Payload' and the value of t11FcSpPoNaAttribExtension contains the OID of this table.
.1.3.6.1.2.1.178.1.3.10.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAuthProtEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex:t11FcSpPoNaAttribName:t11FcSpPoNaAttribEntryIndex:t11FcSpPoNaAuthProtIdentifier:t11FcSpPoNaAuthProtPartIndex,current,,Each row contains information about an Authentication Protocol that is extracted out of the Attribute Entry (identified by t11FcSpPoNaAttribEntryIndex) of the non-active Policy Attribute Object (identified by t11FcSpPoNaAttribName) for the Fabric identified by t11FcSpPoFabricIndex and managed within the Fibre Channel management instance identified by fcmInstanceIndex. If the value of one Attribute Protocol Parameters string is too large (more than 256 bytes) to be contained within the value of one instance of t11FcSpPoNaAuthProtParams, then one row in this table contains the first 256 bytes, and one (or more) other row(s) in this table contain the rest of the value. The same underlying management data that is represented in rows of this table is also represented by the corresponding instances of t11FcSpPoNaAttribValue. Thus, after any modification of the underlying management data, e.g., after a Set operation to the value of either MIB representation, then that modification is reflected in the values of both MIB representations.
.1.3.6.1.2.1.178.1.3.10.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAuthProtIdentifier,Unsigned32,not-accessible,,current,,The Authentication Protocol Identifier: 1 = DH-CHAP 3 = FCPAP 4 = IKEv2 5 = IKEv2-AUTH 240 thru 255 = Vendor Specific Protocols all other values are 'Reserved' (by T11).
.1.3.6.1.2.1.178.1.3.10.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAuthProtPartIndex,Unsigned32,not-accessible,,current,,When the value of an Attribute Protocol Parameters string is shorter than 257 bytes, the whole value is contained in one instance of t11FcSpPoNaAuthProtParams, and the value of this object is 1. (This includes the case when the Attribute Protocol Parameters string is zero bytes in length.) If the value of an Authentication Protocol Parameters string is longer than 256 bytes, then that value is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, with each such part contained in a separate row of this table, and the value of this object is set to the part number. That is, this object has the value of 1 for bytes 0-255, the value of 2 for bytes 256-511, etc.
.1.3.6.1.2.1.178.1.3.10.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAuthProtParams,OCTET,read-create,,current,,The value of an Authentication Protocol Parameters string is divided up on 256-byte boundaries such that all parts are 256 bytes long except the last part, which is shorter if necessary, and each such part is contained in a separate instance of this object.
.1.3.6.1.2.1.178.1.3.10.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoNaAuthProtRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.178.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoStatistics,,,,,,
.1.3.6.1.2.1.178.1.4.1,T11-FC-SP-POLICY-MIB::t11FcSpPoStatsTable,,not-accessible,,current,,A table of statistics maintained by FC-SP Security Policy Servers.
.1.3.6.1.2.1.178.1.4.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoStatsEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex,current,,A set of statistics for the FC-SP Security Policy Server on the Fabric identified by the value of t11FcSpPoFabricIndex, and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.4.1.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoInRequests,Counter32,read-only,,current,,The number of FC-SP Policy Management Requests (e.g., GPS, APS, etc.) received by this FC-SP Security Policy Server on this Fabric. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.178.1.4.1.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoInAccepts,Counter32,read-only,,current,,The number of times that this FC-SP Security Policy Server sent an Accept CT_IU on this Fabric in response to a received FC-SP Policy Management Request (e.g., GPS, APS, etc.). This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.178.1.4.1.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoInRejects,Counter32,read-only,,current,,The number of times that this FC-SP Security Policy Server sent a Reject CT_IU on this Fabric in response to a received FC-SP Policy Management Request (e.g., GPS, APS, etc.). This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.178.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoControl,,,,,,
.1.3.6.1.2.1.178.1.5.1,T11-FC-SP-POLICY-MIB::t11FcSpPoServerAddress,OCTET,accessible-for-notify,,current,,The WWN of the FC-SP Security Policy Server that received a request that is referenced in a notification.
.1.3.6.1.2.1.178.1.5.2,T11-FC-SP-POLICY-MIB::t11FcSpPoControlTable,,not-accessible,,current,,A table of control information, including the memory realization of FC-SP Policy Databases, and concerning the generation of notifications due to FC-SP Policy-related events.
.1.3.6.1.2.1.178.1.5.2.1,T11-FC-SP-POLICY-MIB::t11FcSpPoControlEntry,,not-accessible,fcmInstanceIndex:t11FcSpPoFabricIndex,current,,Each entry contains control information specific to FC-SP Policy and Policy-related events for the Fabric identified by the value of t11FcSpPoFabricIndex, and managed within the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.178.1.5.2.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization of FC-SP Policy Objects and related information for a particular Fabric; specifically, for: - rows created and/or modified for the particular Fabric in these tables: t11FcSpPoNaSummaryTable t11FcSpPoNaSwListTable t11FcSpPoNaSwMembTable t11FcSpPoNaNoMembTable t11FcSpPoNaCtDescrTable t11FcSpPoNaSwConnTable t11FcSpPoNaIpMgmtTable t11FcSpPoNaWkpDescrTable t11FcSpPoNaAttribTable - the activate and deactivate actions invoked through the t11FcSpPoOperActivate and t11FcSpPoOperDeActivate objects for the particular Fabric; and - modified information contained in the same row as an instance of this object. Even if an instance of this object has the value 'permanent(4)', none of the information defined in this MIB module for the given Fabric needs to be writable.
.1.3.6.1.2.1.178.1.5.2.1.2,T11-FC-SP-POLICY-MIB::t11FcSpPoNotificationEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether the following types of notifications: t11FcSpPoNotifyActivation, t11FcSpPoNotifyActivateFail, t11FcSpPoNotifyDeactivation and t11FcSpPoNotifyDeactivateFail should be generated for this Fabric.
.1.3.6.1.2.1.178.1.5.2.1.3,T11-FC-SP-POLICY-MIB::t11FcSpPoLastNotifyType,INTEGER,read-only,,current,none(1):activation(2):activateFail(3):deactivation(4):deactivateFail(5),An indication of which of the following types of notification is currently being/was most recently generated for the Fabric: 'activation' -- t11FcSpPoNotifyActivation 'activateFail' -- t11FcSpPoNotifyActivateFail 'deactivation' -- t11FcSpPoNotifyDeactivation 'deactivateFail' -- t11FcSpPoNotifyDeactivateFail The value 'none' indicates that none of these types of notifications have been generated since the last restart of the network management system, and therefore that the corresponding instances of: t11FcSpPoRequestSource, t11FcSpPoReasonCode, t11FcSpPoCtCommandString, t11FcSpPoReasonCodeExp, and t11FcSpPoReasonVendorCode are irrelevant.
.1.3.6.1.2.1.178.1.5.2.1.4,T11-FC-SP-POLICY-MIB::t11FcSpPoRequestSource,OCTET,read-only,,current,,The WWN of the source of the (Activate Policy Summary or Deactivate Policy Summary) request for which the current/most recent notification of the type indicated by the corresponding instance of t11FcSpPoLastNotifyType is being/was generated. If no source is available, the value of this object is the zero-length string.
.1.3.6.1.2.1.178.1.5.2.1.5,T11-FC-SP-POLICY-MIB::t11FcSpPoReasonCode,INTEGER,read-only,,current,none(1):invalidCmdCode(2):invalidVerLevel(3):logicalError(4):invalidIUSize(5):logicalBusy(6):protocolError(7):unableToPerformCmdReq(8):cmdNotSupported(9):serverNotAvailable(10):couldNotEstabSession(11):vendorError(12),The reason code associated with the failure that is indicated when the value of the corresponding instance of t11FcSpPoLastNotifyType is 'activateFail' or 'deactivateFail'. For other values of t11FcSpPoLastNotifyType, the value of this object is 'none(1)'.
.1.3.6.1.2.1.178.1.5.2.1.6,T11-FC-SP-POLICY-MIB::t11FcSpPoCtCommandString,OCTET,read-only,,current,,The binary content of the failed request that is indicated when the value of the corresponding instance of t11FcSpPoLastNotifyType is 'activateFail' or 'deactivateFail'. The content of the request is formatted as an octet string (in network byte order) containing the CT_IU, as described in Table 2 of [FC-GS-5] (including the preamble). For other values of t11FcSpPoLastNotifyType, or if the CT_IU's content is unavailable, the value of this object is the zero-length string. When the length of this object is 255 octets, it contains the first 255 octets of the CT_IU (in network-byte order).
.1.3.6.1.2.1.178.1.5.2.1.7,T11-FC-SP-POLICY-MIB::t11FcSpPoReasonCodeExp,Unsigned32,read-only,,current,,The reason code explanation associated with the failure that is indicated when the value of the corresponding instance of t11FcSpPoLastNotifyType is 'activateFail' or 'deactivateFail'. For other values of t11FcSpPoLastNotifyType, the value of this object is zero.
.1.3.6.1.2.1.178.1.5.2.1.8,T11-FC-SP-POLICY-MIB::t11FcSpPoReasonVendorCode,OCTET,read-only,,current,,The vendor-specific reason code associated with the failure that is indicated when the value of the corresponding instance of t11FcSpPoLastNotifyType is 'activateFail' or 'deactivateFail'. For other values of t11FcSpPoLastNotifyType, or if no vendor-specific reason code is available, the value of this object is the zero-length string.
.1.3.6.1.2.1.178.2,T11-FC-SP-POLICY-MIB::t11FcSpPoMIBConformance,,,,,,
.1.3.6.1.2.1.178.2.1,T11-FC-SP-POLICY-MIB::t11FcSpPoMIBCompliances,,,,,,
.1.3.6.1.2.1.178.2.1.1,T11-FC-SP-POLICY-MIB::t11FcSpPoMIBCompliance,,,,,,The compliance statement for entities that support the Fabric Policies defined in FC-SP,
.1.3.6.1.2.1.178.2.2,T11-FC-SP-POLICY-MIB::t11FcSpPoMIBGroups,,,,,,
.1.3.6.1.2.1.178.2.2.1,T11-FC-SP-POLICY-MIB::t11FcSpPoActiveObjectsGroup,,,,,,A collection of MIB objects that contain information about active Policy Objects that express Fibre Channel Security (FC-SP) policy.
.1.3.6.1.2.1.178.2.2.2,T11-FC-SP-POLICY-MIB::t11FcSpPoOperationsObjectsGroup,,,,,,A collection of MIB objects that allow a new set of Fibre Channel Security (FC-SP) policies to be activated or an existing set to be deactivated.
.1.3.6.1.2.1.178.2.2.3,T11-FC-SP-POLICY-MIB::t11FcSpPoNonActiveObjectsGroup,,,,,,A collection of MIB objects that contain information about non-active Policy Objects available for activation in order to change Fibre Channel Security (FC-SP) policy.
.1.3.6.1.2.1.178.2.2.4,T11-FC-SP-POLICY-MIB::t11FcSpPoStatsObjectsGroup,,,,,,A collection of MIB objects that contain statistics that can be maintained by FC-SP Security Policy Servers.
.1.3.6.1.2.1.178.2.2.5,T11-FC-SP-POLICY-MIB::t11FcSpPoNotifyObjectsGroup,,,,,,A collection of MIB objects to control the generation of notifications concerning Fibre Channel Security (FC-SP) policy, and to hold information contained in such notifications.
.1.3.6.1.2.1.178.2.2.6,T11-FC-SP-POLICY-MIB::t11FcSpPoNotificationGroup,,,,,,A collection of notifications of events concerning Fibre Channel Security (FC-SP) policy.
.1.3.6.1.2.1.179,T11-FC-SP-SA-MIB::t11FcSpSaMIB,,,,,,This MIB module specifies the management information required to manage Security Associations established via Fibre Channel's FC-SP specification. The MIB module consists of six parts: - a per-Fabric table, t11FcSpSaIfTable, of capabilities, parameters, status information, and counters; the counters include non-transient aggregates of per-SA transient counters; - three tables, t11FcSpSaPropTable, t11FcSpSaTSelPropTable, and t11FcSpSaTransTable, specifying the proposals for an FC-SP entity acting as an SA_Initiator to present to the SA_Responder during the negotiation of Security Associations. The same information is also used by an FC-SP entity acting as an SA_Responder to decide what to accept during the negotiation of Security Associations. One of these tables, t11FcSpSaTransTable, is used not only for information about security transforms to propose and to accept, but also as agreed upon during the negotiation of Security Associations; - a table, t11FcSpSaTSelDrByTable, of Traffic Selectors having the security action of 'drop' or 'bypass' to be applied either to ingress traffic that is unprotected by FC-SP, or to all egress traffic; - four tables, t11FcSpSaPairTable, t11FcSpSaTSelNegInTable, t11FcSpSaTSelNegOutTable, and t11FcSpSaTSelSpiTable, containing information about active bidirectional pairs of Security Associations; in particular, t11FcSpSaPairTable has one row per active bidirectional SA pair, t11FcSpSaTSelNegInTable and t11FcSpSaTSelNegOutTable contain information on the Traffic Selectors negotiated on the SAs, and the t11FcSpSaTSelSpiTable is an alternate lookup table such that the Traffic Selector(s) in use on a particular Security Association can be quickly determined based on the (ingress) SPI value; - a table, t11FcSpSaControlTable, of control and other information concerning the generation of notifications for events related to FC-SP Security Associations; - one notification, t11FcSpSaNotifyAuthFailure, generated on the occurrence of an Authentication failure for a received FC-2 or CT_IU frame. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFC 5324; see the RFC itself for full legal notices.
.1.3.6.1.2.1.179.0,T11-FC-SP-SA-MIB::t11FcSpSaMIBNotifications,,,,,,
.1.3.6.1.2.1.179.0.1,T11-FC-SP-SA-MIB::t11FcSpSaNotifyAuthFailure,,,,,,When this notification is generated, it indicates the occurrence of an Authentication failure for a received FC-2 or CT_IU frame. The t11FcSpSaControlInboundSpi, t11FcSpSaControlSource, and t11FcSpSaControlDestination objects in the varbindlist are the frame's SPI, source and destination addresses, respectively. t11FcSpSaControlFrame provides the (beginning of the) frame's content if such is available. This notification is generated only for the first occurrence of an Authentication failure on a Fabric within a time window. Subsequent occurrences of an Authentication Failure on the same Fabric within the same time window are counted but suppressed. The value of t11FcSpSaControlElapsed contains (a lower bound on) the elapsed time since the last generation of this notification for the same Fabric. The value of t11FcSpSaControlSuppressed contains the number of generations which were suppressed in the time window after that last generation, or zero if unknown.
.1.3.6.1.2.1.179.0.2,T11-FC-SP-SA-MIB::t11FcSpSaNotifyLifeExceeded,,,,,,This notification is generated when the lifetime (in seconds or in passed bytes) of an SA is exceeded, and the SA is either immediately terminated or is terminated because an attempt to renew the SA fails. The values of t11FcSpSaControlLifeExcdSpi and t11FcSpSaControlLifeExcdDir contain the SPI and direction of the terminated SA.
.1.3.6.1.2.1.179.1,T11-FC-SP-SA-MIB::t11FcSpSaMIBObjects,,,,,,
.1.3.6.1.2.1.179.1.1,T11-FC-SP-SA-MIB::t11FcSpSaBase,,,,,,
.1.3.6.1.2.1.179.1.1.1,T11-FC-SP-SA-MIB::t11FcSpSaIfTable,,not-accessible,,current,,A table containing per-Fabric information related to FC-SP Security Associations.
.1.3.6.1.2.1.179.1.1.1.1,T11-FC-SP-SA-MIB::t11FcSpSaIfEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaIfIndex:t11FcSpSaIfFabricIndex,current,,Each entry contains information related to Security Associations on a particular Fabric, and managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.179.1.1.1.1.1,T11-FC-SP-SA-MIB::t11FcSpSaIfIndex,Integer32,not-accessible,,current,,This object has a non-zero value to identify a particular interface, or the value zero to indicate that the information in this row applies to all (of the management instance's) interfaces to the particular Fabric. If any row has a non-zero value of t11FcSpSaIfIndex, then all rows for the same Fibre Channel management instance must also have a non-zero value of t11FcSpSaIfIndex and thereby be specific to a particular interface. As and when zero values of t11FcSpSaIfIndex are used in this table, then they must also be used in each other table that has t11FcSpSaIfIndex in its INDEX clause.
.1.3.6.1.2.1.179.1.1.1.1.2,T11-FC-SP-SA-MIB::t11FcSpSaIfFabricIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular Fabric.
.1.3.6.1.2.1.179.1.1.1.1.3,T11-FC-SP-SA-MIB::t11FcSpSaIfEspHeaderCapab,BITS,read-only,,current,encrNull(0):encrAesCbc(1):encrAesCtr(2):encrAesGcm(3):encr3Des(4):prfHmacMd5(5):prfHmacSha1(6):prfAesCbc(7):authHmacMd5L96(8):authHmacSha1L96(9):authHmacMd5L128(10):authHmacSha1L160(11):encrNullAuthAesGmac(12):dhGroups1024bit(13):dhGroups2048bit(14),A list of the standardized transforms supported by this entity on this interface for ESP_Header protection.
.1.3.6.1.2.1.179.1.1.1.1.4,T11-FC-SP-SA-MIB::t11FcSpSaIfCTAuthCapab,BITS,read-only,,current,encrNull(0):encrAesCbc(1):encrAesCtr(2):encrAesGcm(3):encr3Des(4):prfHmacMd5(5):prfHmacSha1(6):prfAesCbc(7):authHmacMd5L96(8):authHmacSha1L96(9):authHmacMd5L128(10):authHmacSha1L160(11):encrNullAuthAesGmac(12):dhGroups1024bit(13):dhGroups2048bit(14),A list of the standardized transforms supported by this entity on this interface for CT_Authentication protection.
.1.3.6.1.2.1.179.1.1.1.1.5,T11-FC-SP-SA-MIB::t11FcSpSaIfIKEv2Capab,BITS,read-only,,current,encrNull(0):encrAesCbc(1):encrAesCtr(2):encrAesGcm(3):encr3Des(4):prfHmacMd5(5):prfHmacSha1(6):prfAesCbc(7):authHmacMd5L96(8):authHmacSha1L96(9):authHmacMd5L128(10):authHmacSha1L160(11):encrNullAuthAesGmac(12):dhGroups1024bit(13):dhGroups2048bit(14),A list of the standardized transforms supported by this entity on this interface with IKEv2 protection.
.1.3.6.1.2.1.179.1.1.1.1.6,T11-FC-SP-SA-MIB::t11FcSpSaIfIkev2AuthCapab,INTEGER,read-only,,current,true(1):false(2),An indication of whether the entity is capable of supporting the IKEv2-AUTH protocol on this interface, i.e., concatenation of Authentication and SA Management Transactions, such that an SA Management Transaction is used to perform both the authentication function and SA management.
.1.3.6.1.2.1.179.1.1.1.1.7,T11-FC-SP-SA-MIB::t11FcSpSaIfStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization of information related to FC-SP Security Associations for interface(s) to a particular Fabric; specifically, for rows created and/or modified in these tables: t11FcSpSaPropTable t11FcSpSaTSelDrByTable t11FcSpSaControlTable and, for modified information contained in the same row as an instance of this object. Even if an instance of this object has the value 'permanent(4)', none of the information defined in this MIB module for interface(s) to the given Fabric need to be writable.
.1.3.6.1.2.1.179.1.1.1.1.8,T11-FC-SP-SA-MIB::t11FcSpSaIfReplayPrevention,INTEGER,read-write,,current,true(1):false(2),This object indicates whether anti-replay protection is enabled for frame reception on this interface. Note that the replay-protection mechanism in FC-SP is conceptually similar to the corresponding mechanism in IPsec ESP.
.1.3.6.1.2.1.179.1.1.1.1.9,T11-FC-SP-SA-MIB::t11FcSpSaIfReplayWindowSize,Unsigned32,read-write,,current,,The size of the replay window to be used when anti-replay protection is enabled for frame reception on this interface. Note that the replay-protection mechanism in FC-SP is conceptually similar to the corresponding mechanism in IPsec ESP.
.1.3.6.1.2.1.179.1.1.1.1.10,T11-FC-SP-SA-MIB::t11FcSpSaIfDeadPeerDetections,Counter32,read-only,,current,,The number of times that a dead peer condition has been detected on this interface. This counter has no discontinuities other than those that all Counter32's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.11,T11-FC-SP-SA-MIB::t11FcSpSaIfTerminateAllSas,INTEGER,read-write,,current,noop(1):terminate(2),Setting this object to 'terminate' is a request to terminate all outstanding Security Associations on this interface. When read, the value of this object is always 'noop'. Setting this object to 'noop' has no effect.
.1.3.6.1.2.1.179.1.1.1.1.12,T11-FC-SP-SA-MIB::t11FcSpSaIfOutDrops,Counter64,read-only,,current,,The number of output frames that were dropped, instead of being transmitted on this interface, because they matched an active (at that time) Traffic Selector with an action of 'Drop'. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.13,T11-FC-SP-SA-MIB::t11FcSpSaIfOutBypasses,Counter64,read-only,,current,,The number of output frames that were transmitted unchanged by FC-SP on this interface because they matched an active (at that time) Traffic Selector with an action of 'Bypass'. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.14,T11-FC-SP-SA-MIB::t11FcSpSaIfOutProcesses,Counter64,read-only,,current,,The number of output frames that were protected by FC-SP before being transmitted on this interface because they matched an active (at that time) Traffic Selector with an action of 'Process'. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.15,T11-FC-SP-SA-MIB::t11FcSpSaIfOutUnMatcheds,Counter64,read-only,,current,,The number of frames that were transmitted unchanged by FC-SP on this interface because they did not match any Traffic Selector active at that time. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.16,T11-FC-SP-SA-MIB::t11FcSpSaIfInUnprotUnmtchDrops,Counter64,read-only,,current,,The number of frames received on this interface that were dropped because they were unprotected and did not match any Traffic Selector active at that time. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.17,T11-FC-SP-SA-MIB::t11FcSpSaIfInDetReplays,Counter64,read-only,,current,,The number of times that a replay has been detected on a Security Association that is currently active or was previously active on this interface. Note that a frame that is discarded because it is 'behind' the window, i.e., too old, is counted as a replay. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.18,T11-FC-SP-SA-MIB::t11FcSpSaIfInUnprotMtchDrops,Counter64,read-only,,current,,The number of times that a frame received on this interface was dropped because it matched with a Traffic Selector for a Security Association that was active at the time of receipt but the frame was not protected as negotiated for that Security Association. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.19,T11-FC-SP-SA-MIB::t11FcSpSaIfInBadXforms,Counter64,read-only,,current,,The number of times that a frame received on this interface was dropped because of a failure of one of the transforms negotiated for the Security Association on which it was received. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.20,T11-FC-SP-SA-MIB::t11FcSpSaIfInGoodXforms,Counter64,read-only,,current,,The number of frames received on this interface on a Security Association for which the transforms negotiated for that Security Association were successfully applied, and that matched a Traffic Selector for that Security Association. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.1.1.1.21,T11-FC-SP-SA-MIB::t11FcSpSaIfInProtUnmtchs,Counter64,read-only,,current,,The number of frames received on this interface that were dropped because they did not match any of the Traffic Selectors negotiated for the Security Association on which they were received, even though the Security Association's transforms were successfully applied. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.2,T11-FC-SP-SA-MIB::t11FcSpSaConfig,,,,,,
.1.3.6.1.2.1.179.1.2.1,T11-FC-SP-SA-MIB::t11FcSpSaPropTable,,not-accessible,,current,,A table of proposals for an FC-SP entity acting as an SA_Initiator to present to the SA_Responder during the negotiation of Security Associations. This information is also used by an FC-SP entity acting as an SA_Responder to decide what to accept during the negotiation of Security Associations.
.1.3.6.1.2.1.179.1.2.1.1,T11-FC-SP-SA-MIB::t11FcSpSaPropEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaIfIndex:t11FcSpSaIfFabricIndex:t11FcSpSaPropIndex,current,,Each entry contains information about one proposal for the FC-SP entity to present, or what to accept, during the negotiation of Security Associations on one or more interfaces (identified by t11FcSpSaIfIndex) to a particular Fabric (identified by t11FcSpSaIfFabricIndex), and managed as part of the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpSaIfStorageType that is INDEX-ed by the same values of fcmInstanceIndex, t11FcSpSaIfIndex and t11FcSpSaIfFabricIndex.
.1.3.6.1.2.1.179.1.2.1.1.1,T11-FC-SP-SA-MIB::t11FcSpSaPropIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular proposal for use on one or more interfaces to a Fabric.
.1.3.6.1.2.1.179.1.2.1.1.2,T11-FC-SP-SA-MIB::t11FcSpSaPropSecurityProt,INTEGER,read-create,,current,espHeader(1):ctAuth(2),The Security Protocol identifier for this proposal, i.e., whether the proposal is for traffic to be protected using ESP_Header or CT_Authentication.
.1.3.6.1.2.1.179.1.2.1.1.3,T11-FC-SP-SA-MIB::t11FcSpSaPropTSelListIndex,Unsigned32,read-create,,current,,When the value of this object is non-zero, it points to the proposal's list of Traffic Selectors. The value must be non-zero in an active row of this table. The identified list is represented by all rows in the t11FcSpSaTSelPropTable for which t11FcSpSaTSelPropListIndex has the same value as this object (and with corresponding values of t11FcSpSaIfIndex and fcmInstanceIndex).
.1.3.6.1.2.1.179.1.2.1.1.4,T11-FC-SP-SA-MIB::t11FcSpSaPropTransListIndex,Unsigned32,read-create,,current,,When the value of this object is non-zero, it points to the proposal's list of Transforms. The value must be non-zero in an active row of this table. The identified list is represented by all rows in the t11FcSpSaTransTable for which t11FcSpSaTransListIndex has the same value as this object (and with corresponding values of t11FcSpSaIfIndex and fcmInstanceIndex).
.1.3.6.1.2.1.179.1.2.1.1.5,T11-FC-SP-SA-MIB::t11FcSpSaPropAcceptAlgorithm,INTEGER,read-create,,current,intersection(1):union(2):other(3),The algorithm by which an SA_Responder in an SA negotiation decides on which Traffic Selectors to specify in a response to an IKE_Create_Child_SA request. This algorithm is used when the Traffic Selectors specified by an SA_Initiator in an IKE_Create_Child_SA request overlap with this proposal's list of Traffic Selectors: intersection(1) - the SA_Responder specifies the largest subset of what the SA_Initiator proposed, which is also a subset of this proposal's Traffic Selectors. union(2) - the SA_Responder specifies the smallest superset of what the SA_Initiator proposed, which is also a superset of this proposal's Traffic Selectors. other(3) - the SA_Responder uses some other algorithm. 
.1.3.6.1.2.1.179.1.2.1.1.6,T11-FC-SP-SA-MIB::t11FcSpSaPropOutMatchSucceeds,Counter64,read-only,,current,,The number of egress frames that have matched a Traffic Selector that was negotiated to select traffic for an SA based on this proposal being accepted. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.2.1.1.7,T11-FC-SP-SA-MIB::t11FcSpSaPropRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of a row. Values of object instances within an active row can be modified at any time. The status cannot be set to 'active' unless and until the instances of t11FcSpSaPropTSelListIndex and t11FcSpSaPropTransListIndex in the row have been set to point to active rows in the t11FcSpSaTSelPropTable and t11FcSpSaTransTable tables, respectively. A row in this table is deleted if the active rows it points to are deleted.
.1.3.6.1.2.1.179.1.2.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropTable,,not-accessible,,current,,A table containing information about Traffic Selectors to propose and/or to accept during the negotiation of Security Associations.
.1.3.6.1.2.1.179.1.2.2.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaIfIndex:t11FcSpSaTSelPropListIndex:t11FcSpSaTSelPropPrecedence,current,,Each entry contains information about one Traffic Selector within a list of Traffic Selectors to propose, or for use in determining what to accept during Security Association negotiation. One such list is configured for use on a Fabric by configuring the list's value of t11FcSpSaTSelPropListIndex as the value of an instance of t11FcSpSaPropTSelListIndex, for corresponding values of t11FcSpSaIfIndex and fcmInstanceIndex. Further, the proposing and accepting of Traffic Selectors is only done as a part of a proposal specified by a row of the t11FcSpSaPropTable, i.e., in combination with the proposing and accepting of security transforms as specified by the combination of t11FcSpSaPropTSelListIndex and t11FcSpSaPropTransListIndex in one row of the t11FcSpSaPropTable. The StorageType of a row in this table is specified by the instance of t11FcSpSaTSelPropStorageType in that row.
.1.3.6.1.2.1.179.1.2.2.1.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropListIndex,Unsigned32,not-accessible,,current,,An index value that identifies a particular list of Traffic Selectors.
.1.3.6.1.2.1.179.1.2.2.1.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropPrecedence,Unsigned32,not-accessible,,current,,The precedence of this Traffic Selector. Each Traffic Selector within a particular list of Traffic Selectors must have a different precedence. If an egress frame matches multiple Traffic Selectors, it should be transmitted on the SA associated with the Traffic Selector having the numerically smallest precedence value.
.1.3.6.1.2.1.179.1.2.2.1.3,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropDirection,INTEGER,read-create,,current,ingress(1):egress(2),An indication of whether this Traffic Selector is to be proposed for ingress or egress traffic.
.1.3.6.1.2.1.179.1.2.2.1.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropStartSrcAddr,OCTET,read-create,,current,,The numerically smallest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.5,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropEndSrcAddr,OCTET,read-create,,current,,The numerically largest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.6,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropStartDstAddr,OCTET,read-create,,current,,The numerically smallest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.7,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropEndDstAddr,OCTET,read-create,,current,,The numerically largest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.8,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropStartRCtl,OCTET,read-create,,current,,The numerically smallest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.9,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropEndRCtl,OCTET,read-create,,current,,The numerically largest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.10,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropStartType,OCTET,read-create,,current,,The numerically smallest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.11,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropEndType,OCTET,read-create,,current,,The numerically largest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.2.1.12,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization of the information in this row. Even if an instance of this object has the value 'permanent(4)', none of the information in its row needs to be writable.
.1.3.6.1.2.1.179.1.2.2.1.13,T11-FC-SP-SA-MIB::t11FcSpSaTSelPropRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.179.1.2.3,T11-FC-SP-SA-MIB::t11FcSpSaTransTable,,not-accessible,,current,,A table containing information about security transforms to propose, to accept and/or agreed upon during the negotiation of Security Associations.
.1.3.6.1.2.1.179.1.2.3.1,T11-FC-SP-SA-MIB::t11FcSpSaTransEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaIfIndex:t11FcSpSaTransListIndex:t11FcSpSaTransIndex,current,,Each entry contains information about one proposal within a list of security transforms to be proposed, to be accepted, or already agreed upon, for use on a pair of Security Associations on one or more interfaces (identified by t11FcSpSaIfIndex), managed as part of the Fibre Channel management instance identified by fcmInstanceIndex. One such list is configured to be proposed or accepted for use on a Fabric, by having the list's value of t11FcSpSaTransListIndex be the value of an instance of t11FcSpSaPropTransListIndex for that Fabric. Further, the proposing and accepting of security transforms is only done as a part of a proposal specified by a row of the t11FcSpSaPropTable, i.e., in combination with the proposing and accepting of Traffic Selectors as specified by the combination of t11FcSpSaPropTSelListIndex and t11FcSpSaPropTransListIndex in one row of the t11FcSpSaPropTable. The security (encryption and integrity) transform in use on an SA pair is indicated by having the pair's values of t11FcSpSaPairTransListIndex and t11FcSpSaPairTransIndex contain the values of t11FcSpSaTransListIndex and t11FcSpSaTransIndex for the transform's row in this table. The StorageType of a row in this table is specified by the instance of t11FcSpSaTransStorageType in that row.
.1.3.6.1.2.1.179.1.2.3.1.1,T11-FC-SP-SA-MIB::t11FcSpSaTransListIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies a particular list of security transforms to be proposed, to be accepted, or already agreed upon.
.1.3.6.1.2.1.179.1.2.3.1.2,T11-FC-SP-SA-MIB::t11FcSpSaTransIndex,Unsigned32,not-accessible,,current,,An index value that uniquely identifies one security transform within a list identified by t11FcSpSaTransListIndex.
.1.3.6.1.2.1.179.1.2.3.1.3,T11-FC-SP-SA-MIB::t11FcSpSaTransSecurityProt,INTEGER,read-create,,current,espHeader(1):ctAuth(2),The Security Protocol identifier that indicates whether this transform is for traffic to be protected using ESP_Header or using CT_Authentication.
.1.3.6.1.2.1.179.1.2.3.1.4,T11-FC-SP-SA-MIB::t11FcSpSaTransEncryptAlg,OBJECT,read-create,,current,,The Encryption Algorithm for this transform.
.1.3.6.1.2.1.179.1.2.3.1.5,T11-FC-SP-SA-MIB::t11FcSpSaTransEncryptKeyLen,Unsigned32,read-create,,current,,The key length in bits to be used with an encryption algorithm that has a variable length key. This object is ignored when the corresponding instance of t11FcSpSaTransEncryptAlg specifies an algorithm with a fixed length key.
.1.3.6.1.2.1.179.1.2.3.1.6,T11-FC-SP-SA-MIB::t11FcSpSaTransIntegrityAlg,OBJECT,read-create,,current,,The Integrity Algorithm for this transform.
.1.3.6.1.2.1.179.1.2.3.1.7,T11-FC-SP-SA-MIB::t11FcSpSaTransStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object specifies the memory realization of the information in this row. Even if an instance of this object has the value 'permanent(4)', none of the information in its row needs to be writable.
.1.3.6.1.2.1.179.1.2.3.1.8,T11-FC-SP-SA-MIB::t11FcSpSaTransRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. When an instance of t11FcSpSaPairTransListIndex points to a row in this table, values of object instances in the row cannot be modified nor can the row be deleted. Otherwise, a row can be modified or deleted at any time.
.1.3.6.1.2.1.179.1.2.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByTable,,not-accessible,,current,,A table containing Traffic Selectors to select which traffic is to be dropped or is to bypass further security processing.
.1.3.6.1.2.1.179.1.2.4.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaIfIndex:t11FcSpSaIfFabricIndex:t11FcSpSaTSelDrByDirection:t11FcSpSaTSelDrByPrecedence,current,,Each entry represents one Traffic Selector having the security action of 'drop' or 'bypass', which is applied based on a precedence value, either to ingress traffic that is unprotected by FC-SP, or to all egress traffic on one or more interfaces (identified by t11FcSpSaIfIndex) to a particular Fabric (identified by t11FcSpSaIfFabricIndex), and managed as part of the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpSaIfStorageType that is INDEX-ed by the same values of fcmInstanceIndex, t11FcSpSaIfIndex and t11FcSpSaIfFabricIndex.
.1.3.6.1.2.1.179.1.2.4.1.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByDirection,INTEGER,not-accessible,,current,ingress(1):egress(2),An indication of whether this Traffic Selector is for ingress or egress traffic.
.1.3.6.1.2.1.179.1.2.4.1.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByPrecedence,Unsigned32,not-accessible,,current,,The precedence of this Traffic Selector. If and when a frame is compared against multiple Traffic Selectors, and multiple of them have a match with the frame, the security action to be taken for the frame is that specified for the matching Traffic Selector having the numerically smallest precedence value.
.1.3.6.1.2.1.179.1.2.4.1.3,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByAction,INTEGER,read-create,,current,drop(1):bypass(2),The security action to be taken for a frame that matches this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByStartSrcAddr,OCTET,read-create,,current,,The numerically smallest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.5,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByEndSrcAddr,OCTET,read-create,,current,,The numerically largest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.6,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByStartDstAddr,OCTET,read-create,,current,,The numerically smallest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.7,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByEndDstAddr,OCTET,read-create,,current,,The numerically largest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.8,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByStartRCtl,OCTET,read-create,,current,,The numerically smallest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.9,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByEndRCtl,OCTET,read-create,,current,,The numerically largest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.10,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByStartType,OCTET,read-create,,current,,The numerically smallest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.11,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByEndType,OCTET,read-create,,current,,The numerically largest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.2.4.1.12,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByMatches,Counter64,read-only,,current,,The number of frames for which the action specified by the corresponding instance of t11FcSpSaTSelDrByAction was taken because of a match with this Traffic Selector. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.2.4.1.13,T11-FC-SP-SA-MIB::t11FcSpSaTSelDrByRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. Values of object instances within the row can be modified at any time.
.1.3.6.1.2.1.179.1.3,T11-FC-SP-SA-MIB::t11FcSpSaActive,,,,,,
.1.3.6.1.2.1.179.1.3.1,T11-FC-SP-SA-MIB::t11FcSpSaPairTable,,not-accessible,,current,,A table containing information about active bidirectional pairs of Security Associations.
.1.3.6.1.2.1.179.1.3.1.1,T11-FC-SP-SA-MIB::t11FcSpSaPairEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaPairIfIndex:t11FcSpSaIfFabricIndex:t11FcSpSaPairInboundSpi,current,,Each entry contains information about one active bidirectional pair of Security Associations on an interface to a particular Fabric (identified by t11FcSpSaIfFabricIndex), managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.179.1.3.1.1.1,T11-FC-SP-SA-MIB::t11FcSpSaPairIfIndex,Integer32,not-accessible,,current,,This object identifies the interface to the particular Fabric on which this SA pair is active.
.1.3.6.1.2.1.179.1.3.1.1.2,T11-FC-SP-SA-MIB::t11FcSpSaPairInboundSpi,Unsigned32,not-accessible,,current,,The SPI value that is used to indicate that an incoming frame was received on the ingress SA of this SA pair.
.1.3.6.1.2.1.179.1.3.1.1.3,T11-FC-SP-SA-MIB::t11FcSpSaPairSecurityProt,INTEGER,read-only,,current,espHeader(1):ctAuth(2),The object indicates whether this SA uses ESP_Header to protect FC-2 frames, or CT_Authentication to protect Common Transport Information Units (CT_IUs).
.1.3.6.1.2.1.179.1.3.1.1.4,T11-FC-SP-SA-MIB::t11FcSpSaPairTransListIndex,Unsigned32,read-only,,current,,The combination of this value and the value of the corresponding instance of t11FcSpSaPairTransIndex identify the row in the t11FcSpSaTransTable that contains the transforms that are in use on this SA pair.
.1.3.6.1.2.1.179.1.3.1.1.5,T11-FC-SP-SA-MIB::t11FcSpSaPairTransIndex,Unsigned32,read-only,,current,,The combination of this value and the value of the corresponding instance of t11FcSpSaPairTransListIndex identify the row in the t11FcSpSaTransTable that contains the transforms that are in use on this SA pair.
.1.3.6.1.2.1.179.1.3.1.1.6,T11-FC-SP-SA-MIB::t11FcSpSaPairLifetimeLeft,Unsigned32,read-only,,current,,The remaining lifetime of this SA pair, given in the units specified by the value of the corresponding instance of t11FcSpSaPairLifetimeLeft.
.1.3.6.1.2.1.179.1.3.1.1.7,T11-FC-SP-SA-MIB::t11FcSpSaPairLifetimeLeftUnits,INTEGER,read-only,,current,seconds(1):kiloBytes(2):megaBytes(3):gigaBytes(4):teraBytes(5):petaBytes(6):exaBytes(7):zettaBytes(8):yottaBytes(9),The units in which the value of the corresponding instance of t11FcSpSaPairLifetimeLeft specifies the remaining lifetime of this SA pair.
.1.3.6.1.2.1.179.1.3.1.1.8,T11-FC-SP-SA-MIB::t11FcSpSaPairTerminate,INTEGER,read-write,,current,noop(1):terminate(2),Setting this object to 'terminate' is a request to terminate this pair of Security Associations. When read, the value of this object is always 'noop'. Setting this object to 'noop' has no effect.
.1.3.6.1.2.1.179.1.3.1.1.9,T11-FC-SP-SA-MIB::t11FcSpSaPairInProtUnMatchs,Counter64,read-only,,current,,The number of frames received on this SA for which the SA's transforms were successfully applied to the frame, but the frame was still dropped because it did not match any of the SA's ingress Traffic Selectors. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.3.1.1.10,T11-FC-SP-SA-MIB::t11FcSpSaPairInDetReplays,Counter64,read-only,,current,,The number of times that a replay has been detected on this Security Association. Note that a frame that is discarded because it is 'behind' the window, i.e., too old, is counted as a replay. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.3.1.1.11,T11-FC-SP-SA-MIB::t11FcSpSaPairInBadXforms,Counter64,read-only,,current,,The number of times that a received frame was dropped because one of the transforms negotiated for this Security Association failed. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.3.1.1.12,T11-FC-SP-SA-MIB::t11FcSpSaPairInGoodXforms,Counter64,read-only,,current,,The number of received frames for which the transforms negotiated for this Security Association, were successfully applied. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.3.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInTable,,not-accessible,,current,,A table containing information about ingress Traffic Selectors that are in use on active Security Associations.
.1.3.6.1.2.1.179.1.3.2.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaPairIfIndex:t11FcSpSaIfFabricIndex:t11FcSpSaTSelNegInIndex,current,,Each entry contains information about one ingress Traffic Selector that is in use on an active Security Association on an interface (identified by t11FcSpSaPairIfIndex) to a particular Fabric (identified by t11FcSpSaIfFabricIndex), managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.179.1.3.2.1.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInIndex,Unsigned32,not-accessible,,current,,An index value to distinguish an ingress Traffic Selector from all others currently in use by Security Associations on the same interface to a particular Fabric.
.1.3.6.1.2.1.179.1.3.2.1.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInInboundSpi,Unsigned32,read-only,,current,,The SPI of the ingress SA on which this Traffic Selector is in use. This value can be used to find the SA pair's row in the t11FcSpSaPairTable.
.1.3.6.1.2.1.179.1.3.2.1.3,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInStartSrcAddr,OCTET,read-only,,current,,The numerically smallest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInEndSrcAddr,OCTET,read-only,,current,,The numerically largest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.5,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInStartDstAddr,OCTET,read-only,,current,,The numerically smallest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.6,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInEndDstAddr,OCTET,read-only,,current,,The numerically largest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.7,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInStartRCtl,OCTET,read-only,,current,,The numerically smallest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.8,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInEndRCtl,OCTET,read-only,,current,,The numerically largest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.9,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInStartType,OCTET,read-only,,current,,The numerically smallest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.10,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInEndType,OCTET,read-only,,current,,The numerically largest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.2.1.11,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegInUnpMtchDrops,Counter64,read-only,,current,,The number of times that a received frame was dropped because it matched with this Traffic Selector but the frame was not protected as negotiated for the Security Association identified by t11FcSpSaTSelNegInInboundSpi. This counter has no discontinuities other than those that all Counter64's have when sysUpTime=0.
.1.3.6.1.2.1.179.1.3.3,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutTable,,not-accessible,,current,,A table containing information about egress Traffic Selectors that are in use on active Security Associations.
.1.3.6.1.2.1.179.1.3.3.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaPairIfIndex:t11FcSpSaIfFabricIndex:t11FcSpSaTSelNegOutPrecedence,current,,Each entry contains information about one egress Traffic Selector that is in use on an active Security Association on an interface (identified by t11FcSpSaPairIfIndex) to a particular Fabric (identified by t11FcSpSaIfFabricIndex), managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.179.1.3.3.1.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutPrecedence,Unsigned32,not-accessible,,current,,The precedence of this Traffic Selector. If and when a frame is compared against multiple Traffic Selectors, and multiple of them have a match with the frame, the security action to be taken for the frame is that specified for the matching Traffic Selector having the numerically smallest precedence value.
.1.3.6.1.2.1.179.1.3.3.1.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutInboundSpi,Unsigned32,read-only,,current,,The SPI of the ingress SA of the SA pair for which this Traffic Selector is in use on the egress SA. This value can be used to find the SA pair's row in the t11FcSpSaPairTable.
.1.3.6.1.2.1.179.1.3.3.1.3,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutStartSrcAddr,OCTET,read-only,,current,,The numerically smallest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutEndSrcAddr,OCTET,read-only,,current,,The numerically largest 24-bit value of a source address (S_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.5,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutStartDstAddr,OCTET,read-only,,current,,The numerically smallest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.6,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutEndDstAddr,OCTET,read-only,,current,,The numerically largest 24-bit value of a destination address (D_ID) of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.7,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutStartRCtl,OCTET,read-only,,current,,The numerically smallest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.8,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutEndRCtl,OCTET,read-only,,current,,The numerically largest 8-bit value contained within a Routing Control (R_CTL) field of a frame that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.9,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutStartType,OCTET,read-only,,current,,The numerically smallest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.3.1.10,T11-FC-SP-SA-MIB::t11FcSpSaTSelNegOutEndType,OCTET,read-only,,current,,The numerically largest of a range of possible 'type' values of frames that will match with this Traffic Selector.
.1.3.6.1.2.1.179.1.3.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelSpiTable,,not-accessible,,current,,A table identifying the Traffic Selectors in use on particular Security Associations, INDEX-ed by their (ingress) SPI values.
.1.3.6.1.2.1.179.1.3.4.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelSpiEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaPairIfIndex:t11FcSpSaIfFabricIndex:t11FcSpSaTSelSpiInboundSpi:t11FcSpSaTSelSpiTrafSelIndex,current,,Each entry identifies one Traffic Selector in use on an SA pair on the interface (identified by t11FcSpSaPairIfIndex) to a particular Fabric (identified by t11FcSpSaIfFabricIndex), and managed as part of the Fibre Channel management instance identified by fcmInstanceIndex.
.1.3.6.1.2.1.179.1.3.4.1.1,T11-FC-SP-SA-MIB::t11FcSpSaTSelSpiInboundSpi,Unsigned32,not-accessible,,current,,An SPI value that identifies the ingress Security Association of a particular SA pair.
.1.3.6.1.2.1.179.1.3.4.1.2,T11-FC-SP-SA-MIB::t11FcSpSaTSelSpiTrafSelIndex,Unsigned32,not-accessible,,current,,An index value that distinguishes between the (potentially multiple) Traffic Selectors in use on this Security Association pair.
.1.3.6.1.2.1.179.1.3.4.1.3,T11-FC-SP-SA-MIB::t11FcSpSaTSelSpiDirection,INTEGER,read-only,,current,ingress(1):egress(2),This object indicates whether this Traffic Selector is being used for ingress or for egress traffic.
.1.3.6.1.2.1.179.1.3.4.1.4,T11-FC-SP-SA-MIB::t11FcSpSaTSelSpiTrafSelPtr,Unsigned32,read-only,,current,,This object contains a pointer into another table that can be used to obtain more information about this Traffic Selector. If the corresponding instance of t11FcSpSaTSelSpiDirection has the value 'egress', then this object contains the value of t11FcSpSaTSelNegOutPrecedence in the row of t11FcSpSaTSelNegOutTable, which contains more information. If the corresponding instance of t11FcSpSaTSelSpiDirection has the value 'ingress', then this object contains the value of t11FcSpSaTSelNegInIndex that identifies the row in t11FcSpSaTSelNegInTable containing more information.
.1.3.6.1.2.1.179.1.4,T11-FC-SP-SA-MIB::t11FcSpSaControl,,,,,,
.1.3.6.1.2.1.179.1.4.1,T11-FC-SP-SA-MIB::t11FcSpSaControlTable,,not-accessible,,current,,A table of control and other information concerning the generation of notifications for events related to FC-SP Security Associations.
.1.3.6.1.2.1.179.1.4.1.1,T11-FC-SP-SA-MIB::t11FcSpSaControlEntry,,not-accessible,fcmInstanceIndex:t11FcSpSaIfIndex:t11FcSpSaIfFabricIndex,current,,Each entry identifies information for the one or more interfaces (identified by t11FcSpSaIfIndex) to a particular Fabric (identified by t11FcSpSaIfFabricIndex), and managed as part of the Fibre Channel management instance identified by fcmInstanceIndex. The StorageType of a row in this table is specified by the instance of t11FcSpSaIfStorageType that is INDEX-ed by the same values of fcmInstanceIndex, t11FcSpSaIfIndex, and t11FcSpSaIfFabricIndex.
.1.3.6.1.2.1.179.1.4.1.1.1,T11-FC-SP-SA-MIB::t11FcSpSaControlAuthFailEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether a t11FcSpSaNotifyAuthFailure notification should be generated for the first occurrence of an Authentication failure within a time window for this Fabric.
.1.3.6.1.2.1.179.1.4.1.1.2,T11-FC-SP-SA-MIB::t11FcSpSaControlInboundSpi,Unsigned32,read-only,,current,,The SPI value of the ingress Security Association on which was received the last frame for which a t11FcSpSaNotifyAuthFailure was generated. If no t11FcSpSaNotifyAuthFailure notifications have been generated, the value of this object is zero.
.1.3.6.1.2.1.179.1.4.1.1.3,T11-FC-SP-SA-MIB::t11FcSpSaControlSource,OCTET,read-only,,current,,The S_ID contained in the last frame for which a t11FcSpSaNotifyAuthFailure was generated. If no t11FcSpSaNotifyAuthFailure notifications have been generated, the value of this object is the zero-length string.
.1.3.6.1.2.1.179.1.4.1.1.4,T11-FC-SP-SA-MIB::t11FcSpSaControlDestination,OCTET,read-only,,current,,The D_ID contained in the last frame for which a t11FcSpSaNotifyAuthFailure was generated. If no t11FcSpSaNotifyAuthFailure notifications have been generated, the value of this object is the zero-length string.
.1.3.6.1.2.1.179.1.4.1.1.5,T11-FC-SP-SA-MIB::t11FcSpSaControlFrame,OCTET,read-only,,current,,The binary content of the last frame for which a t11FcSpSaNotifyAuthFailure was generated. If more than 256 bytes of the frame are available, then this object contains the first 256 bytes. If less than 256 bytes of the frame are available, then this object contains the first N bytes, where N is greater or equal to zero. If no t11FcSpSaNotifyAuthFailure notifications have been generated, the value of this object is the zero-length string.
.1.3.6.1.2.1.179.1.4.1.1.6,T11-FC-SP-SA-MIB::t11FcSpSaControlElapsed,TimeTicks,read-only,,current,,The elapsed time since the last generation of a t11FcSpSaNotifyAuthFailure notification on the same Fabric, or the value of sysUpTime if no t11FcSpSaNotifyAuthFailure notifications have been generated since the last restart.
.1.3.6.1.2.1.179.1.4.1.1.7,T11-FC-SP-SA-MIB::t11FcSpSaControlSuppressed,Gauge32,read-only,,current,,The number of occurrences of an Authentication failure on a Fabric that were suppressed because they occurred on the same Fabric within the same time window as a previous Authentication failure for which a t11FcSpSaNotifyAuthFailure notification was generated. The value of this object is reset to zero on a restart of the network management subsystem, and whenever a t11FcSpSaNotifyAuthFailure notification is generated. In the event that the value of this object reaches its maximum value, it remains at that value until it is reset on the generation of the next t11FcSpSaNotifyAuthFailure notification.
.1.3.6.1.2.1.179.1.4.1.1.8,T11-FC-SP-SA-MIB::t11FcSpSaControlWindow,Unsigned32,read-write,,current,,The length of a time window that begins when a t11FcSpSaNotifyAuthFailure notification is generated for any Security Association on a particular Fabric. For the duration of the time window, further Authentication failures occurring for the same Security Association are counted but no t11FcSpSaNotifyAuthFailure notification is generated. When this object is modified before the end of a time window, that time window is immediately terminated, i.e., the next Authentication failure on the relevant Fabric after the modification will cause a new time window to begin with the new length.
.1.3.6.1.2.1.179.1.4.1.1.9,T11-FC-SP-SA-MIB::t11FcSpSaControlMaxNotifs,Unsigned32,read-write,,current,,The maximum number of t11FcSpSaNotifyAuthFailure notifications to be generated per Fabric within a t11FcSpSaControlWindow time window. Subsequent Authentication failures occurring on the same Fabric in the same time window are counted, but no t11FcSpSaNotifyAuthFailure notification is generated. When this object is modified before the end of a time window, that time window is immediately terminated, i.e., the next Authentication failure on the relevant Fabric after the modification will cause a new time window to begin with the new length.
.1.3.6.1.2.1.179.1.4.1.1.10,T11-FC-SP-SA-MIB::t11FcSpSaControlLifeExcdEnable,INTEGER,read-write,,current,true(1):false(2),This object specifies whether t11FcSpSaNotifyLifeExceeded notifications should be generated for this Fabric.
.1.3.6.1.2.1.179.1.4.1.1.11,T11-FC-SP-SA-MIB::t11FcSpSaControlLifeExcdSpi,Unsigned32,read-only,,current,,The SPI of the SA that was most recently terminated because its lifetime (in seconds or in passed bytes) was exceeded. Such terminations include those due to a failed attempt to renew an SA after its lifetime was exceeded.
.1.3.6.1.2.1.179.1.4.1.1.12,T11-FC-SP-SA-MIB::t11FcSpSaControlLifeExcdDir,INTEGER,read-only,,current,ingress(1):egress(2),The direction of frame transmission on the SA that was most recently terminated because its lifetime (in seconds or in passed bytes) was exceeded.
.1.3.6.1.2.1.179.1.4.1.1.13,T11-FC-SP-SA-MIB::t11FcSpSaControlLifeExcdTime,TimeTicks,read-only,,current,,The time of the most recent termination of an SA due to its lifetime (in seconds or in passed bytes) being exceeded. Such terminations include those due to a failed attempt to renew an SA after its lifetime was exceeded.
.1.3.6.1.2.1.179.2,T11-FC-SP-SA-MIB::t11FcSpSaMIBConformance,,,,,,
.1.3.6.1.2.1.179.2.1,T11-FC-SP-SA-MIB::t11FcSpSaMIBCompliances,,,,,,
.1.3.6.1.2.1.179.2.1.1,T11-FC-SP-SA-MIB::t11FcSpSaMIBCompliance,,,,,,The compliance statement for entities that implement FC-SP Security Associations.
.1.3.6.1.2.1.179.2.2,T11-FC-SP-SA-MIB::t11FcSpSaMIBGroups,,,,,,
.1.3.6.1.2.1.179.2.2.1,T11-FC-SP-SA-MIB::t11FcSpSaCapabilityGroup,,,,,,A collection of objects containing information related to capabilities of FC-SP entities.
.1.3.6.1.2.1.179.2.2.2,T11-FC-SP-SA-MIB::t11FcSpSaParamStatusGroup,,,,,,A collection of objects containing parameters and status information related to FC-SP entities.
.1.3.6.1.2.1.179.2.2.3,T11-FC-SP-SA-MIB::t11FcSpSaSummaryCountGroup,,,,,,A collection of objects containing summary counters for FC-SP Security Associations.
.1.3.6.1.2.1.179.2.2.4,T11-FC-SP-SA-MIB::t11FcSpSaProposalGroup,,,,,,A collection of objects containing information related to making and accepting proposals for FC-SP Security Associations.
.1.3.6.1.2.1.179.2.2.5,T11-FC-SP-SA-MIB::t11FcSpSaDropBypassGroup,,,,,,A collection of objects containing information about Traffic Selectors of traffic to drop or bypass for FC-SP Security.
.1.3.6.1.2.1.179.2.2.6,T11-FC-SP-SA-MIB::t11FcSpSaActiveGroup,,,,,,A collection of objects containing information related to currently active FC-SP Security Associations.
.1.3.6.1.2.1.179.2.2.7,T11-FC-SP-SA-MIB::t11FcSpSaNotifInfoGroup,,,,,,A collection of objects containing information related to notifications of events concerning FC-SP Security Associations.
.1.3.6.1.2.1.179.2.2.8,T11-FC-SP-SA-MIB::t11FcSpSaNotificationGroup,,,,,,A collection of notifications of events concerning FC-SP Security Associations.
.1.3.6.1.2.1.180,PW-ENET-STD-MIB::pwEnetStdMIB,,,,,,This MIB module describes a model for managing Ethernet point-to-point pseudowire services over a Packet Switched Network (PSN). Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5603; see the RFC itself for full legal notices.
.1.3.6.1.2.1.180.1,PW-ENET-STD-MIB::pwEnetObjects,,,,,,
.1.3.6.1.2.1.180.1.1,PW-ENET-STD-MIB::pwEnetTable,,not-accessible,,current,,This table contains the index to the Ethernet tables associated with this Ethernet PW, the VLAN configuration, and the VLAN mode.
.1.3.6.1.2.1.180.1.1.1,PW-ENET-STD-MIB::pwEnetEntry,,not-accessible,pwIndex:pwEnetPwInstance,current,,This table is indexed by the same index that was created for the associated entry in the PW generic table in the PW-STD-MIB module. The pwIndex and the pwEnetPwInstance are used as indexes to allow multiple VLANs to exist on the same PW. An entry is created in this table by the agent for every entry in the pwTable with a pwType of 'ethernetTagged' or 'ethernet'. Additional rows may be created by the operator or the agent if multiple entries are required for the same PW. The value of pwEnetPwInstance can be arbitrarily selected to make the row unique; however, implementations that know the VLAN field value when the row is created MAY use the value of the VLAN itself for better readability and backward compatibility with older versions of this MIB module. This table provides Ethernet port mapping and VLAN configuration for each Ethernet PW. All read-create objects in this table MAY be changed at any time; however, change of some objects (for example, pwEnetVlanMode) during the PW forwarding state MAY cause traffic disruption. Manual entries in this table SHOULD be preserved after a reboot, and the agent MUST ensure the integrity of those entries. If the set of entries of a specific row is found to be inconsistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5). 
.1.3.6.1.2.1.180.1.1.1.1,PW-ENET-STD-MIB::pwEnetPwInstance,Unsigned32,not-accessible,,current,,If multiple rows are mapped to the same PW, this index is used to uniquely identify the individual row. If the value of the VLAN field is known at the time of row creation, the value of pwEnetPwVlan MAY be used for better readability and backward compatibility with older versions of this MIB module. Otherwise, the value 1 SHOULD be set to the first row for each pwIndex for better readability and in order that the management application will know in advance how to access the first row when it was created by the agent. 
.1.3.6.1.2.1.180.1.1.1.2,PW-ENET-STD-MIB::pwEnetPwVlan,Integer32,read-create,,current,,This object defines the (service-delimiting) VLAN field value on the PW. The value 4095 MUST be used if the object is not applicable, for example, when mapping all packets from an Ethernet port to this PW (raw mode). The value 0 MUST be set to indicate untagged frames (from the PW point of view), i.e., when pwEnetVlanMode equals 'noChange' and pwEnetPortVlan equals 0.
.1.3.6.1.2.1.180.1.1.1.3,PW-ENET-STD-MIB::pwEnetVlanMode,INTEGER,read-create,,current,other(0):portBased(1):noChange(2):changeVlan(3):addVlan(4):removeVlan(5),This object indicates the mode of VLAN handling between the port or the virtual port associated with the PW and the PW encapsulation. - 'other' indicates an operation that is not defined by this MIB module. - 'portBased' indicates that the forwarder will forward packets between the port and the PW independent of their structure (i.e., there are no service-delimiting VLAN tags from the PE standpoint). - 'noChange' indicates that the PW contains the original user VLAN, as specified in pwEnetPortVlan; i.e., the VLAN on the PE-CE link is the service-delimiting tag and is kept 'as is' on the PW. - 'changeVlan' indicates that the VLAN field on the PW may be different than the VLAN field on the user's port. The VLAN on the PE-CE link is the service-delimiting tag but has a different value on the PW. - 'addVlan' indicates that a VLAN field will be added on the PSN-bound direction (i.e., on the PW). pwEnetPwVlan indicates the value that will be added. - 'removeVlan' indicates that the encapsulation on the PW does not include the service-delimiting VLAN field. Note that PRI bits transparency is lost in this case. - Implementation of 'portsbased', 'removeVlan', 'addVlan' 'other', and 'changeVlan' is OPTIONAL. 
.1.3.6.1.2.1.180.1.1.1.4,PW-ENET-STD-MIB::pwEnetPortVlan,Integer32,read-create,,current,,This object defines if the mapping between the original port (physical port or VPLS virtual port) to the PW is VLAN based or not. In case of VLAN mapping, this object indicates the VLAN value on the original port. The value of '4095' MUST be used if the whole original port traffic is mapped to the same PW. Note that a pwType of 'ethernetTagged' can still be used if service-delimiting tag is added on the PW (pwEnetVlanMode equals 'addVlan'). This object MUST be equal to pwEnetPwVlan if pwEnetVlanMode equals 'noChange'. The value 0 indicates that packets without a VLAN field (i.e., untagged frames) on the port are associated to this PW. This allows the same behavior as assigning 'Default VLAN' to untagged frames. 
.1.3.6.1.2.1.180.1.1.1.5,PW-ENET-STD-MIB::pwEnetPortIfIndex,Integer32,read-create,,current,,This object is used to specify the ifIndex of the Ethernet port associated with this PW for point-to-point Ethernet service, or the ifIndex of the virtual interface of the VPLS instance associated with the PW if the service is VPLS. Two rows in this table can point to the same ifIndex only if there is no overlap of VLAN values specified in pwEnetPortVlan that are associated with this port. A value of zero indicates that association to an ifIndex is not yet known.
.1.3.6.1.2.1.180.1.1.1.6,PW-ENET-STD-MIB::pwEnetPwIfIndex,Integer32,read-create,,current,,If the PW is modeled as an ifIndex in the ifTable, this object indicates the value of the ifIndex representing the Ethernet PW on the PSN side in the Etherlike-MIB. Note that this value may be different from the value of pwIfIndex that represents the ifIndex of the PW for ifType 'pw'.
.1.3.6.1.2.1.180.1.1.1.7,PW-ENET-STD-MIB::pwEnetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object enables creating, deleting, and modifying this row.
.1.3.6.1.2.1.180.1.1.1.8,PW-ENET-STD-MIB::pwEnetStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the storage type of this row.
.1.3.6.1.2.1.180.1.2,PW-ENET-STD-MIB::pwEnetStatsTable,,not-accessible,,current,,This table contains statistical counters specific for Ethernet PW.
.1.3.6.1.2.1.180.1.2.1,PW-ENET-STD-MIB::pwEnetStatsEntry,,not-accessible,pwIndex,current,,Each entry represents the statistics gathered for the PW carrying the Ethernet.
.1.3.6.1.2.1.180.1.2.1.1,PW-ENET-STD-MIB::pwEnetStatsIllegalVlan,Gauge32,read-only,,current,,The number of packets received (from the PSN) on this PW with either an illegal VLAN field, a missing VLAN field when one was expected, or an excessive VLAN field when it was not expected. This counter may not be applicable in some cases, and MUST return the value of zero in such a case.
.1.3.6.1.2.1.180.1.2.1.2,PW-ENET-STD-MIB::pwEnetStatsIllegalLength,Gauge32,read-only,,current,,The number of packets that were received with an illegal Ethernet packet length on this PW. An illegal length is defined as being greater than the value in the advertised MTU supported, or shorter than the allowed Ethernet packet size.
.1.3.6.1.2.1.180.2,PW-ENET-STD-MIB::pwEnetConformance,,,,,,
.1.3.6.1.2.1.180.2.1,PW-ENET-STD-MIB::pwEnetGroups,,,,,,
.1.3.6.1.2.1.180.2.1.1,PW-ENET-STD-MIB::pwEnetGroup,,,,,,Collection of objects for basic Ethernet PW configuration.
.1.3.6.1.2.1.180.2.1.2,PW-ENET-STD-MIB::pwEnetStatsGroup,,,,,,Collection of objects counting various PW level errors.
.1.3.6.1.2.1.180.2.2,PW-ENET-STD-MIB::pwEnetCompliances,,,,,,
.1.3.6.1.2.1.180.2.2.1,PW-ENET-STD-MIB::pwEnetModuleFullCompliance,,,,,,The compliance statement for agents that provides full support for the PW-ENET-STD-MIB module. Such devices can then be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.180.2.2.2,PW-ENET-STD-MIB::pwEnetModuleReadOnlyCompliance,,,,,,The compliance statement for agents that provide read- only support for the PW-ENET-STD-MIB module. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.181,PW-MPLS-STD-MIB::pwMplsStdMIB,,,,,,This MIB module complements the PW-STD-MIB module for PW operation over MPLS. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5602; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.181.0,PW-MPLS-STD-MIB::pwMplsNotifications,,,,,,
.1.3.6.1.2.1.181.1,PW-MPLS-STD-MIB::pwMplsObjects,,,,,,
.1.3.6.1.2.1.181.1.1,PW-MPLS-STD-MIB::pwMplsTable,,not-accessible,,current,,This table controls MPLS-specific parameters when the PW is going to be carried over MPLS PSN.
.1.3.6.1.2.1.181.1.1.1,PW-MPLS-STD-MIB::pwMplsEntry,,not-accessible,pwIndex,current,,A row in this table represents parameters specific to MPLS PSN for a pseudowire (PW). The row is created automatically by the local agent if the pwPsnType is mpls(1). It is indexed by pwIndex, which uniquely identifies a singular PW. Manual entries in this table SHOULD be preserved after a reboot, and the agent MUST ensure the integrity of those entries. If the set of entries of a specific row were found to be nonconsistent after reboot, the PW pwOperStatus MUST be declared as down(2). Any read-write object in this table MAY be changed at any time; however, change of some objects (for example, pwMplsMplsType) during PW forwarding state MAY cause traffic disruption.
.1.3.6.1.2.1.181.1.1.1.1,PW-MPLS-STD-MIB::pwMplsMplsType,BITS,read-write,,current,mplsTe(0):mplsNonTe(1):pwOnly(2),This object is set by the operator to indicate the outer tunnel types, if existing. mplsTe(0) is used if the outer tunnel is set up by MPLS-TE, and mplsNonTe(1) is used if the outer tunnel is set up by LDP or manually. A combination of mplsTe(0) and mplsNonTe(1) MAY exist. pwOnly(2) is used if there is no outer tunnel label, i.e., in static provisioning without an MPLS tunnel. pwOnly(2) cannot be combined with mplsNonTe(1) or mplsTe(0). An implementation that can identify automatically that the peer node is directly connected MAY support the bit pwOnly(2) as read-only. 
.1.3.6.1.2.1.181.1.1.1.2,PW-MPLS-STD-MIB::pwMplsExpBitsMode,INTEGER,read-write,,current,outerTunnel(1):specifiedValue(2):serviceDependant(3),This object is set by the operator to determine the PW shim label EXP bits. The value of outerTunnel(1) is used where there is an outer tunnel -- pwMplsMplsType equals to mplsTe(0) or mplsNonTe(1). Note that in this case, there is no need to mark the PW label with the EXP bits, since the PW label is not visible to the intermediate nodes. If there is no outer tunnel, specifiedValue(2) SHOULD be used to indicate that the value is specified by pwMplsExpBits. Setting serviceDependant(3) indicates that the EXP bits are set based on a rule that is implementation specific.
.1.3.6.1.2.1.181.1.1.1.3,PW-MPLS-STD-MIB::pwMplsExpBits,Unsigned32,read-write,,current,,This object is set by the operator if pwMplsExpBitsMode is set to specifiedValue(2) to indicate the MPLS EXP bits to be used on the PW shim label. Otherwise, it SHOULD be set to zero.
.1.3.6.1.2.1.181.1.1.1.4,PW-MPLS-STD-MIB::pwMplsTtl,Unsigned32,read-write,,current,,This object is set by the operator to indicate the PW TTL value to be used on the PW shim label.
.1.3.6.1.2.1.181.1.1.1.5,PW-MPLS-STD-MIB::pwMplsLocalLdpID,OCTET,read-write,,current,,The LDP identifier of the LDP entity that creates this PW in the local node. As the PW labels are always set from the per-platform label space, the last two octets in the LDP ID MUST always both be zeros.
.1.3.6.1.2.1.181.1.1.1.6,PW-MPLS-STD-MIB::pwMplsLocalLdpEntityIndex,Unsigned32,read-write,,current,,The local node LDP Entity Index of the LDP entity creating this PW.
.1.3.6.1.2.1.181.1.1.1.7,PW-MPLS-STD-MIB::pwMplsPeerLdpID,OCTET,read-only,,current,,The peer LDP identifier of the LDP session. This object SHOULD return the value zero if LDP is not used or if the value is not yet known.
.1.3.6.1.2.1.181.1.1.1.8,PW-MPLS-STD-MIB::pwMplsStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.181.1.2,PW-MPLS-STD-MIB::pwMplsOutboundTable,,not-accessible,,current,,This table reports and configures the current outbound MPLS tunnels (i.e., toward the PSN) or the physical interface in the case of a PW label only that carries the PW traffic. It also reports the current outer tunnel and LSP that forward the PW traffic.
.1.3.6.1.2.1.181.1.2.1,PW-MPLS-STD-MIB::pwMplsOutboundEntry,,not-accessible,,current,,A row in this table configures the outer tunnel used for carrying the PW traffic toward the PSN. In the case of PW label only, it configures the interface that will carry the PW traffic. An entry in this table augments the pwMplsEntry, and is created automatically when the corresponding row has been created by the agent in the pwMplsEntry. This table points to the appropriate MPLS MIB module: In the MPLS-TE case, the three objects relevant to the indexing of a TE tunnel head-end (as used in the MPLS-TE-STD-MIB) are to be configured, and the tunnel instance indicates the LSP that is currently in use for forwarding the traffic. In the case of signaled non-TE MPLS (an outer tunnel label assigned by LDP), the table points to the XC entry in the LSR-STD-MIB. If the non-TE MPLS tunnel is manually configured, the operator configures the XC pointer to this tunnel. In the case of PW label only (no outer tunnel), the ifIndex of the port to carry the PW is configured here. It is possible to associate a PW to one TE tunnel head-end and a non-TE tunnel together. An indication in this table will report the currently active one. In addition, in the TE case, the table reports the active tunnel instance (i.e., the specific LSP in use). Any read-write object in this table MAY be changed at any time; however, change of some objects (for example, MPLS-TE indexes) during PW forwarding state MAY cause traffic disruption.
.1.3.6.1.2.1.181.1.2.1.1,PW-MPLS-STD-MIB::pwMplsOutboundLsrXcIndex,OCTET,read-write,,current,,This object is applicable if the pwMplsMplsType mplsNonTe(1) bit is set, and MUST return a value of zero otherwise. If the outer tunnel is signaled, the object is read-only and indicates the XC index in the MPLS-LSR-STD-MIB of the outer tunnel toward the peer. Otherwise (tunnel is set up manually), the operator defines the XC index of the manually created outer tunnel through this object. 
.1.3.6.1.2.1.181.1.2.1.2,PW-MPLS-STD-MIB::pwMplsOutboundTunnelIndex,Unsigned32,read-write,,current,,This object is applicable if the pwMplsMplsType mplsTe(0) bit is set, and MUST return a value of zero otherwise. It is part of the set of indexes for the outbound tunnel. The operator sets this object to represent the desired tunnel head-end toward the peer for carrying the PW traffic. 
.1.3.6.1.2.1.181.1.2.1.3,PW-MPLS-STD-MIB::pwMplsOutboundTunnelInstance,Unsigned32,read-only,,current,,This object is applicable if the pwMplsMplsType mplsTe(0) bit is set, and MUST return a value of zero otherwise. It indicates the actual tunnel instance that is currently active and carrying the PW traffic. It SHOULD return the value zero if the information from the MPLS-TE application is not yet known. 
.1.3.6.1.2.1.181.1.2.1.4,PW-MPLS-STD-MIB::pwMplsOutboundTunnelLclLSR,OCTET,read-write,,current,,This object is applicable if the pwMplsMplsType mplsTe(0) bit is set, and MUST return a value of all zeros otherwise. It is part of the set of indexes for the outbound tunnel. The operator sets this object to represent the desired tunnel head-end toward the peer for carrying the PW traffic. 
.1.3.6.1.2.1.181.1.2.1.5,PW-MPLS-STD-MIB::pwMplsOutboundTunnelPeerLSR,OCTET,read-write,,current,,This object is applicable if the pwMplsMplsType mplsTe(0) bit is set, and MUST return a value of zero otherwise. It is part of the set of indexes for the outbound tunnel. Note that in most cases, it equals to pwPeerAddr. 
.1.3.6.1.2.1.181.1.2.1.6,PW-MPLS-STD-MIB::pwMplsOutboundIfIndex,Integer32,read-write,,current,,This object is applicable if the pwMplsMplsType pwOnly(0) bit is set, and MUST return a value of zero otherwise. The operator configures the ifIndex of the outbound port in this case. 
.1.3.6.1.2.1.181.1.2.1.7,PW-MPLS-STD-MIB::pwMplsOutboundTunnelTypeInUse,INTEGER,read-only,,current,notYetKnown(1):mplsTe(2):mplsNonTe(3):pwOnly(4),This object indicates the current tunnel that is carrying the PW traffic. The value of notYetKnown(1) should be used if the agent is currently unable to determine which tunnel or interface is carrying the PW, for example, because both tunnels are in operational status down. 
.1.3.6.1.2.1.181.1.3,PW-MPLS-STD-MIB::pwMplsInboundTable,,not-accessible,,current,,This table indicates the PW LDP XC entry in the MPLS-LSR-STD-MIB for signaled PWs. 
.1.3.6.1.2.1.181.1.3.1,PW-MPLS-STD-MIB::pwMplsInboundEntry,,not-accessible,pwIndex,current,,A row in this table is created by the agent for each signaled PW, and shows the XC index related to the PW signaling in the inbound direction in the MPLS-LSR-STD-MIB that controls and display the information for all the LDP signaling processes in the local node. 
.1.3.6.1.2.1.181.1.3.1.1,PW-MPLS-STD-MIB::pwMplsInboundXcIndex,OCTET,read-only,,current,,The XC index representing this PW in the inbound direction. It MUST return the value zero if the information is not yet known.
.1.3.6.1.2.1.181.1.4,PW-MPLS-STD-MIB::pwMplsNonTeMappingTable,,not-accessible,,current,,This table indicates the PW association to the outbound tunnel in non-TE applications, maps the PW to its (inbound) XC entry, and indicates the PW-to-physical interface mapping for a PW without an outer tunnel. 
.1.3.6.1.2.1.181.1.4.1,PW-MPLS-STD-MIB::pwMplsNonTeMappingEntry,,not-accessible,pwMplsNonTeMappingDirection:pwMplsNonTeMappingXcIndex:pwMplsNonTeMappingIfIndex:pwMplsNonTeMappingPwIndex,current,,A row in this table displays the association between the PW and - its non-TE MPLS outbound outer tunnel, - its XC entry in the MPLS-LSR-STD-MIB, or - its physical interface if there is no outer tunnel (PW label only) and manual configuration. Rows are created in this table by the agent depending on the setting of pwMplsMplsType: - If the pwMplsMplsType mplsNonTe(1) bit is set, the agent creates a row for the outbound direction (pwMplsNonTeMappingDirection set to psnBound(1)). The pwMplsNonTeMappingXcIndex holds the XC index in the MPLS-LSR-STD-MIB of the PSN-bound outer tunnel. pwMplsNonTeMappingIfIndex MUST be zero for this row. - If the pwMplsMplsType pwOnly(2) bit is set, the agent creates a row for the outbound direction (pwMplsNonTeMappingDirection set to psnBound(1)). The pwMplsNonTeMappingIfIndex holds the ifIndex of the physical port this PW will use in the outbound direction. pwMplsNonTeMappingXcIndex MUST be zero for this row. - If the PW has been set up by a signaling protocol (i.e., pwOwner equal pwIdFecSignaling(2) or genFecSignaling(3)), the agent creates a row for the inbound direction (pwMplsNonTeMappingDirection set to fromPsn(2)). The pwMplsNonTeMappingXcIndex holds the XC index in the MPLS-LSR-STD-MIB of the PW LDP-generated XC entry. pwMplsNonTeMappingIfIndex MUST be zero for this row. An application can use this table to quickly retrieve the PW carried over specific non-TE MPLS outer tunnel or physical interface. 
.1.3.6.1.2.1.181.1.4.1.1,PW-MPLS-STD-MIB::pwMplsNonTeMappingDirection,INTEGER,not-accessible,,current,psnBound(1):fromPsn(2),Index for the conceptual XC row identifying the tunnel-to-PW mappings, indicating the direction of the packet flow for this entry. psnBound(1) indicates that the entry is related to packets toward the PSN. fromPsn(2) indicates that the entry is related to packets coming from the PSN. 
.1.3.6.1.2.1.181.1.4.1.2,PW-MPLS-STD-MIB::pwMplsNonTeMappingXcIndex,OCTET,not-accessible,,current,,See the description clause of pwMplsNonTeMappingEntry for the usage guidelines of this object.
.1.3.6.1.2.1.181.1.4.1.3,PW-MPLS-STD-MIB::pwMplsNonTeMappingIfIndex,Integer32,not-accessible,,current,,See the description clause of pwMplsNonTeMappingEntry for the usage guidelines of this object.
.1.3.6.1.2.1.181.1.4.1.4,PW-MPLS-STD-MIB::pwMplsNonTeMappingPwIndex,Unsigned32,read-only,,current,,The value that represents the PW in the pwTable.
.1.3.6.1.2.1.181.1.5,PW-MPLS-STD-MIB::pwMplsTeMappingTable,,not-accessible,,current,,This table reports the PW association to the outbound MPLS tunnel for MPLS-TE applications.
.1.3.6.1.2.1.181.1.5.1,PW-MPLS-STD-MIB::pwMplsTeMappingEntry,,not-accessible,pwMplsTeMappingTunnelIndex:pwMplsTeMappingTunnelInstance:pwMplsTeMappingTunnelPeerLsrID:pwMplsTeMappingTunnelLocalLsrID:pwMplsTeMappingPwIndex,current,,A row in this table represents the association between a PW and its MPLS-TE outer (head-end) tunnel. An application can use this table to quickly retrieve the list of the PWs that are configured on a specific MPLS-TE outer tunnel. The pwMplsTeMappingTunnelInstance reports the actual LSP out of the tunnel head-end that is currently forwarding the traffic. The table is indexed by the head-end indexes of a TE tunnel and the PW index. 
.1.3.6.1.2.1.181.1.5.1.1,PW-MPLS-STD-MIB::pwMplsTeMappingTunnelIndex,Unsigned32,not-accessible,,current,,Primary index for the conceptual row identifying the MPLS-TE tunnel that is carrying the PW traffic.
.1.3.6.1.2.1.181.1.5.1.2,PW-MPLS-STD-MIB::pwMplsTeMappingTunnelInstance,Unsigned32,not-accessible,,current,,This object identifies the MPLS-TE LSP that is carrying the PW traffic. It MUST return the value zero if the information of the specific LSP is not yet known. Note that based on the recommendation in the MPLS-TC-STD-MIB, instance index 0 should refer to the configured tunnel interface.
.1.3.6.1.2.1.181.1.5.1.3,PW-MPLS-STD-MIB::pwMplsTeMappingTunnelPeerLsrID,OCTET,not-accessible,,current,,This object identifies the peer LSR when the outer tunnel is MPLS-TE.
.1.3.6.1.2.1.181.1.5.1.4,PW-MPLS-STD-MIB::pwMplsTeMappingTunnelLocalLsrID,OCTET,not-accessible,,current,,This object identifies the local LSR.
.1.3.6.1.2.1.181.1.5.1.5,PW-MPLS-STD-MIB::pwMplsTeMappingPwIndex,Unsigned32,read-only,,current,,This object returns the value that represents the PW in the pwTable.
.1.3.6.1.2.1.181.2,PW-MPLS-STD-MIB::pwMplsConformance,,,,,,
.1.3.6.1.2.1.181.2.1,PW-MPLS-STD-MIB::pwMplsGroups,,,,,,
.1.3.6.1.2.1.181.2.1.1,PW-MPLS-STD-MIB::pwMplsGroup,,,,,,Collection of objects needed for PW over MPLS PSN configuration.
.1.3.6.1.2.1.181.2.1.2,PW-MPLS-STD-MIB::pwMplsOutboundMainGroup,,,,,,Collection of objects needed for outbound association of PW and MPLS tunnel.
.1.3.6.1.2.1.181.2.1.3,PW-MPLS-STD-MIB::pwMplsOutboundTeGroup,,,,,,Collection of objects needed for outbound association of PW and MPLS-TE tunnel.
.1.3.6.1.2.1.181.2.1.4,PW-MPLS-STD-MIB::pwMplsInboundGroup,,,,,,Collection of objects needed for inbound PW presentation. This group MUST be supported if PW signaling through LDP is used.
.1.3.6.1.2.1.181.2.1.5,PW-MPLS-STD-MIB::pwMplsMappingGroup,,,,,,Collection of objects needed for mapping association of PW and MPLS tunnel.
.1.3.6.1.2.1.181.2.2,PW-MPLS-STD-MIB::pwMplsCompliances,,,,,,
.1.3.6.1.2.1.181.2.2.1,PW-MPLS-STD-MIB::pwMplsModuleFullCompliance,,,,,,The compliance statement for agents that provide full support for the PW-MPLS-STD-MIB module. Such devices can then be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.181.2.2.2,PW-MPLS-STD-MIB::pwMplsModuleReadOnlyCompliance,,,,,,The compliance statement for agents that provide read- only support for the PW-MPLS-STD-MIB module. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.182,PKTC-IETF-EVENT-MIB::pktcIetfEventMib,,,,,,This MIB module specifies the basic management objects for managing events generated by the Multimedia Terminal Adapter devices compliant with the PacketCable and IPCablecom requirements. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5428; see the RFC itself for full legal notices.
.1.3.6.1.2.1.182.0,PKTC-IETF-EVENT-MIB::pktcEventNotifications,,,,,,
.1.3.6.1.2.1.182.0.1,PKTC-IETF-EVENT-MIB::pktcEventNotification,,,,,,This Notification MIB object contains the contents for event reporting. It contains the event log time, the organization ID, the event identifier, the endpoint identifier, the correlation ID, and the MTA's MAC address.
.1.3.6.1.2.1.182.1,PKTC-IETF-EVENT-MIB::pktcEventMibObjects,,,,,,
.1.3.6.1.2.1.182.1.1,PKTC-IETF-EVENT-MIB::pktcEventControl,,,,,,
.1.3.6.1.2.1.182.1.1.1,PKTC-IETF-EVENT-MIB::pktcEventReset,BITS,read-write,,current,resetEventLogTable(0):resetEventTable(1),This MIB object allows a management station to clear the local log of generated events, reset the management event descriptions, or both. MTAs generate management events. These events are stored in the MIB table pktcEventLogTable. If a management station needs to clear all the current entries (e.g., after a troubleshooting operation is complete), it can do so by setting the resetEventLogTable(0) bit to a value of '1'. The MTA is pre-configured with the events that it can generate. This is stored in the MIB table pktcEventTable. This table also contains the descriptions associated with these events. These descriptions can be modified by a management station. However, if the management station wishes to reset the descriptions to factory defaults, it can do so by setting the resetEventTable(1) bit to a value of '1'. The MTA actions are summarized below: Bit resetEventLogTable(0) set to a value of '1' - delete all entries in pktcEventLogTable; - reset the value of pktcEventLogIndex to '0'. Bit resetEventTable(1) set to a value of '1' - reset the pktcEventTable to the factory default values. Bits resetEventLogTable(0) and resetEventTable(1) set to a value of '1' - perform the above actions as though they were performed individually (in any order). Setting a reset bit to a value of '0' MUST NOT result in any action. The MTA MUST perform the above actions regardless of persistence (i.e., storage in non-volatile memory). The MTA MUST always return a value of '00' when this MIB object is read. A management station that resets tables using this MIB object needs to be careful about the impact to other management stations that may be reliant on the information contained in the table(s) being reset. For example, say management station A creates a specific set of event descriptions in the event table (pktcEventTable) for debugging purposes and expects any generated events to report the modified descriptions. In such a case, if another management station resets the event table to factory defaults, any subsequent events will not contain the modified descriptions expected by management station A. Such multi-manager contentions are not addressed within this MIB module. Thus, management stations are RECOMMENDED to use this MIB object with care and caution, and only when absolutely required.
.1.3.6.1.2.1.182.1.1.2,PKTC-IETF-EVENT-MIB::pktcEventSyslog,,,,,,
.1.3.6.1.2.1.182.1.1.2.1,PKTC-IETF-EVENT-MIB::pktcEventSyslogCapabilities,BITS,read-only,,current,formatBSDSyslog(0):formatSyslogProtocol(1):transportUDP(2):transportTLS(3):transportBEEP(4),This MIB object contains the MTA capabilities for supporting the syslog protocol, specifically the message formats and the transport protocols. The BSD syslog message format is specified in [RFC3164] (formatBSDSyslog), and the IETF syslog protocol is specified in [RFC5424] (formatSyslogProtocol). The MTA MUST set the appropriate protocol and transport bits, based on implementation.
.1.3.6.1.2.1.182.1.1.2.2,PKTC-IETF-EVENT-MIB::pktcEventSyslogAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This MIB object defines the Internet address type of the syslog server specified by the MIB object pktcEventSyslogAddress. A value of dns(16) is disallowed since a non-resolvable DNS domain name will leave the device without a syslog server to which it can report events.
.1.3.6.1.2.1.182.1.1.2.3,PKTC-IETF-EVENT-MIB::pktcEventSyslogAddress,OCTET,read-write,,current,,This MIB object contains the IP address of the syslog server to which the MTA can transmit a syslog message upon the generation of a management event. The type of address this object represents is defined by the MIB object pktDevEventSyslogAddressType. The format of the syslog message is specified by the MIB object pktcEventSyslogMessageFormat.
.1.3.6.1.2.1.182.1.1.2.4,PKTC-IETF-EVENT-MIB::pktcEventSyslogMessageFormat,INTEGER,read-write,,current,formatBSDSyslog(1):formatSyslogProtocol(2),This MIB object contains the syslog message format to be used for transmitting syslog messages to the server contained in the MIB object pktcEventSyslogServer.
.1.3.6.1.2.1.182.1.1.2.5,PKTC-IETF-EVENT-MIB::pktcEventSyslogTransport,INTEGER,read-write,,current,udp(1):tls(2):beep(3),This MIB object specifies the transport to be used to transmit syslog messages to the syslog server contained in the MIB object pktcEventSyslogAddress. If the MTA does not support the transport specified in a SET operation, then the MTA MUST return an appropriate error response, such as 'inconsistentValue'.
.1.3.6.1.2.1.182.1.1.2.6,PKTC-IETF-EVENT-MIB::pktcEventSyslogPort,Unsigned32,read-write,,current,,This MIB object contains the port number of the syslog server to which the syslog messages are to be transmitted.
.1.3.6.1.2.1.182.1.1.3,PKTC-IETF-EVENT-MIB::pktcEventClassTable,,not-accessible,,current,,This MIB table allows for management events that can be generated by an MTA to be classified into categories, or 'event classes'. For example, all the configuration- related events can be associated with an event class titled 'configuration'. Such a classification allows for a management station to affect changes on a common group of events at once. Two operations are specified on an event class: enabling or disabling of all the events in an event class, and selective enabling or disabling based on the severity level.
.1.3.6.1.2.1.182.1.1.3.1,PKTC-IETF-EVENT-MIB::pktcEventClassEntry,,not-accessible,pktcEventClassIndex,current,,Each entry in this table specifies an event class, a grouping of events, as identified by the MTA manufacturer. Any event associated with an event class in this table MUST be specified in the pktcEventTable. The MTA MUST create one entry (index=100) for the event class titled 'generic'. This event class MUST contain all the events that are not contained in any other vendor-specified event classes. A management station SHOULD NOT associate an event with multiple event classes. However, if an event is associated with multiple event classes, the MTA MUST give precedence to the event class with the lowest index. Thus, at a given point in time, only one event class is applicable for an event. The event table (pktcEventTable) provides the event class that affects the event. Whenever an event is generated, the MTA MUST verify the applicable event class entry to take any specified actions. Entries in this table persist across resets and reboots.
.1.3.6.1.2.1.182.1.1.3.1.1,PKTC-IETF-EVENT-MIB::pktcEventClassIndex,Unsigned32,not-accessible,,current,,This MIB object is an index into the event class table. It is a locally meaningful value.
.1.3.6.1.2.1.182.1.1.3.1.2,PKTC-IETF-EVENT-MIB::pktcEventClassName,OCTET,read-only,,current,,This MIB object contains the name of the event class. Vendors MAY define different event classes (e.g., DHCP, SNMP, DEBUG) to group together management events of a particular category. Event class names need to take into consideration the SnmpAdminString definition requirements, such as the use of control code sequence CR LF to represent a newline.
.1.3.6.1.2.1.182.1.1.3.1.3,PKTC-IETF-EVENT-MIB::pktcEventClassStatus,INTEGER,read-write,,current,true(1):false(2),This MIB object indicates if events belonging to the corresponding event class are enabled or disabled, for event reporting. Setting this object to a value of 'true' enables reporting of all the events in the event class. When enabled, the means of reporting events is specified by the MIB object pktcEventReporting. Setting this object to a value of 'false' disables any event reporting, irrespective of the value of the MIB object pktcEventReporting for a specific event. The default value of this MIB object is vendor- specific. However, the vendor SHOULD enable all event categories defined by PacketCable or IPCablecom by default.
.1.3.6.1.2.1.182.1.1.3.1.4,PKTC-IETF-EVENT-MIB::pktcEventClassSeverity,BITS,read-write,,current,emerg(0):alert(1):crit(2):err(3):warning(4):notice(5):info(6):debug(7),This MIB object defines the severity level of events belonging to a specific event class that are enabled for event reporting. This MIB object has no effect on the event reporting unless the MIB object pktcEventClassStatus is set to a value of 'true' (enabled), for the corresponding event class. Setting a bit within the mask to a value of '1' implies that events corresponding to that severity level MUST be reported as defined by the corresponding value of 'pktcEventReporting' for events in the event class. Setting a bit to a value of '0' implies that events corresponding to that level MUST NOT be reported, irrespective of the corresponding value of 'pktcEventReporting' for events in the event class. It is recommended that the bits corresponding to emerg(0), alert(1), crit(2), and err(3) be set to a value of '1' to ensure reporting of events requiring immediate attention.
.1.3.6.1.2.1.182.1.2,PKTC-IETF-EVENT-MIB::pktcEventThrottle,,,,,,
.1.3.6.1.2.1.182.1.2.1,PKTC-IETF-EVENT-MIB::pktcEventThrottleAdminStatus,INTEGER,read-write,,current,unconstrained(1):maintainBelowThreshold(2):stopAtThreshold(3):inhibited(4),This MIB object controls the throttling of the transmitted messages upon generation of an event (SNMP/syslog). It does not affect local logging of events. A value of unconstrained(1) causes event messages to be transmitted without regard to the threshold settings. A value of maintainBelowThreshold(2) causes event messages to be suppressed if the number of transmissions would otherwise exceed the threshold specified by pktcEventThrottleThreshold over the interval specified by pktcEventThrottleInterval. A value of stopAtThreshold(3) causes event message transmission to cease once the threshold specified by pktcEventThrottleThreshold (over the interval specified by pktcEventThrottleInterval) is reached. Event generation is resumed when the value of this MIB object is modified by a management station or when the device resets or reboots. A value of inhibited(4) causes all event message transmissions to be suppressed. An event causing both an SNMP and a syslog message is still treated as a single event. Refer to MIB objects pktcEventThrottleThreshold and pktcEventThrottleInterval for information on throttling.
.1.3.6.1.2.1.182.1.2.2,PKTC-IETF-EVENT-MIB::pktcEventThrottleThreshold,Unsigned32,read-write,,current,,This MIB object contains the number of events per pktcEventThrottleInterval to be transmitted before throttling. An event resulting in multiple actions (e.g., SNMP and syslog) is still treated as a single event.
.1.3.6.1.2.1.182.1.2.3,PKTC-IETF-EVENT-MIB::pktcEventThrottleInterval,Unsigned32,read-write,,current,,This MIB object contains the interval over which the throttle threshold applies.
.1.3.6.1.2.1.182.1.3,PKTC-IETF-EVENT-MIB::pktcEventStatus,,,,,,
.1.3.6.1.2.1.182.1.3.1,PKTC-IETF-EVENT-MIB::pktcEventTransmissionStatus,BITS,read-only,,current,syslogThrottled(0):snmpThrottled(1):validsyslogServerAbsent(2):validSnmpManagerAbsent(3):syslogTransmitError(4):snmpTransmitError(5),This MIB object reflects the status of the event transmissions using syslog, SNMP, or both. If a bit corresponding to a state is set to a value of: '1', it indicates that the state is true '0', it indicates that the state is false If the MTA is not configured with a syslog server or an SNMP Manager, the corresponding 'throttling' and 'transmit error' bits MUST be set to a value of '0'. For example, if an SNMP Manager is not configured on the MTA, the bit corresponding to validSnmpManagerAbsent(3) is set to a value of '1', and the values of the bits corresponding to snmpThrottled(1) and snmpTransmitError(5) are set to a value of '0'. 'Event throttling' is based on thresholds and the current setting of the MIB object pktcEventThrottleAdminStatus. 'Server/Manager' indicators are based on the availability of valid syslog server/SNMP Managers. Transmit errors are reported when detected. If an MTA cannot detect an error situation, the value of the BIT will be set '0'. It is to be noted that not all the conditions that are indicated by this MIB object are detectable by all devices, and when detected may not be accurate. It is meant to provide a report of the status as determined by the device during event transmissions.
.1.3.6.1.2.1.182.1.4,PKTC-IETF-EVENT-MIB::pktcEvents,,,,,,
.1.3.6.1.2.1.182.1.4.1,PKTC-IETF-EVENT-MIB::pktcEventTable,,not-accessible,,current,,This MIB table contains all possible management events that can be generated by the device. This includes PacketCable- and IPCablecom-defined events and vendor-specific events.
.1.3.6.1.2.1.182.1.4.1.1,PKTC-IETF-EVENT-MIB::pktcEventEntry,,not-accessible,pktcEventOrganization:pktcEventIdentifier,current,,An entry in this table is created for each event the MTA implementing this MIB is capable of reporting. Entries in this table are persisted across resets and reboots.
.1.3.6.1.2.1.182.1.4.1.1.1,PKTC-IETF-EVENT-MIB::pktcEventOrganization,Unsigned32,not-accessible,,current,,This MIB object provides the IANA enterprise number of the organization defining the event. Thus, all PacketCable- or IPCablecom-defined events will contain the PacketCable or IPCablecom IANA enterprise number, and all vendor-specific events will contain the IANA enterprise number of the defining organization.
.1.3.6.1.2.1.182.1.4.1.1.2,PKTC-IETF-EVENT-MIB::pktcEventIdentifier,Unsigned32,not-accessible,,current,,This MIB object contains the event identifier for the corresponding event.
.1.3.6.1.2.1.182.1.4.1.1.3,PKTC-IETF-EVENT-MIB::pktcEventFacility,INTEGER,read-only,,current,kern(0):user(1):mail(2):daemon(3):auth(4):syslog(5):lpr(6):news(7):uucp(8):cron(9):authpriv(10):ftp(11):ntp(12):audit(13):console(14):cron2(15):local0(16):local1(17):local2(18):local3(19):local4(20):local5(21):local6(22):local7(23),This MIB object contains the facility for the event. For PacketCable, IPCablecom, or ETSI events, this MUST be set to a value of local0(16).
.1.3.6.1.2.1.182.1.4.1.1.4,PKTC-IETF-EVENT-MIB::pktcEventSeverityLevel,INTEGER,read-write,,current,emerg(0):alert(1):crit(2):err(3):warning(4):notice(5):info(6):debug(7),This MIB object contains the severity level that is applicable to the specified event.
.1.3.6.1.2.1.182.1.4.1.1.5,PKTC-IETF-EVENT-MIB::pktcEventReporting,BITS,read-write,,current,local(0):syslog(1):snmpTrap(2):snmpInform(3),This MIB object defines the action to be taken on occurrence of this event. Bit local(0) refers to local logging of events; bit sylog(1) refers to the transmission of events using syslog; bit snmpTrap(2) refers to the transmission of events using SNMP Traps (SNMPv2-Trap-PDU); and bit snmpInform(3) refers to the transmission of events using SNMP INFORMs. Setting a bit to a value of '1' indicates that the corresponding action will be taken upon occurrence of this event. If none of the bits are set, then no action is taken upon occurrence of the event. The success of transmission using syslog and SNMP depends on the MTA configuration. For example, a valid syslog server address is required for syslog message transmission. Specification of a management event does not necessarily include the actions to be taken upon its generation, i.e., it does not need to specify if a generated event needs to be transmitted via SNMP or syslog, or stored locally. Thus, certain default values are specified, based on the event's severity level specified by the MIB object pktcEventSeverityLevel, as follows: - If the severity level of an event is emerg(0), alert(1), crit(2), or err(3), set the bits for local(0), syslog(1), and snmpInform(3) to a value of '1' and set the remaining bits to a value of '0'. - For an event with any other severity level, set the bits for local(0) and syslog(1) to a value of '1' and set the rest of the bits to a value of '0'.
.1.3.6.1.2.1.182.1.4.1.1.6,PKTC-IETF-EVENT-MIB::pktcEventText,OCTET,read-write,,current,,This MIB object provides a human-readable description of the event. Descriptions need to take into consideration the SnmpAdminString definition requirements such as the use of control code sequence CR LF to represent a newline.
.1.3.6.1.2.1.182.1.4.1.1.7,PKTC-IETF-EVENT-MIB::pktcEventClass,OCTET,read-only,,current,,This MIB object represents the event class that affects the event. If an event is associated with only one event class, then its name (pktcEventClassName) is reported. If an event is associated with more than one event class, then the name of the event class with the lowest index in the event class table (pktcEventClassTable) is reported. See the MIB table pktcEventClassTable for a description of event classes and usage. Descriptions need to take into consideration the SnmpAdminString definition requirements, such as the use of control code sequence CR LF to represent a newline.
.1.3.6.1.2.1.182.1.5,PKTC-IETF-EVENT-MIB::pktcEventLog,,,,,,
.1.3.6.1.2.1.182.1.5.1,PKTC-IETF-EVENT-MIB::pktcEventLogTable,,not-accessible,,current,,This MIB table contains a log of the events generated by the MTA. A description of all the events that can be generated by the device can be obtained from the MIB table pktcEventTable. An MTA is not required to persist the contents of this table across resets.
.1.3.6.1.2.1.182.1.5.1.1,PKTC-IETF-EVENT-MIB::pktcEventLogEntry,,not-accessible,pktcEventLogIndex,current,,Each entry in this table describes an event that has occurred, indexed in the chronological order of generation. The details of the event are borrowed from the parameters associated with the corresponding event entry in pktcEventTable at the time of the event generation. While all entries created as such can be cleared using the MIB object pktcEventReset, the event entries themselves cannot be individually deleted.
.1.3.6.1.2.1.182.1.5.1.1.1,PKTC-IETF-EVENT-MIB::pktcEventLogIndex,Unsigned32,not-accessible,,current,,This MIB object provides relative ordering of the objects in the event log. If the MTA implements non-volatile storage, then this object will always increase except when the MIB object reaches a value of 2^32-1. If the MTA does not implement non-volatile storage, then this object will always increase except when the MIB object reaches a value of 2^32-1 or the MTA is reset. When the value reaches 2^32-1, or an MTA that does not implement non-volatile storage is reset, newer events will be stored starting with an index value of '1' (cyclic rotation).
.1.3.6.1.2.1.182.1.5.1.1.2,PKTC-IETF-EVENT-MIB::pktcEventLogTime,OCTET,read-only,,current,,This MIB object provides a human-readable description of the date and time at which the event occurred. The value of the date and time contained in this MIB object SHOULD reflect the date and time used in the syslog message resulting from the associated event, if such a syslog message was transmitted.
.1.3.6.1.2.1.182.1.5.1.1.3,PKTC-IETF-EVENT-MIB::pktcEventLogOrganization,Unsigned32,read-only,,current,,This MIB object provides the IANA enterprise number of the organization defining the event. Thus, all PacketCable- or IPCablecom-defined events will contain the CableLabs or IPCablecom IANA enterprise number, and all vendor-specific events will contain the IANA enterprise number of the defining organization.
.1.3.6.1.2.1.182.1.5.1.1.4,PKTC-IETF-EVENT-MIB::pktcEventLogIdentifier,Unsigned32,read-only,,current,,This MIB object contains the event identifier for the corresponding event.
.1.3.6.1.2.1.182.1.5.1.1.5,PKTC-IETF-EVENT-MIB::pktcEventLogText,OCTET,read-only,,current,,This MIB object contains the contents of the MIB object pktcEventText, corresponding to the event, at the moment of generation.
.1.3.6.1.2.1.182.1.5.1.1.6,PKTC-IETF-EVENT-MIB::pktcEventLogEndpointName,OCTET,read-only,,current,,This MIB object contains the unique identifier of the MTA endpoint that generated the corresponding event. If the generated event was not associated with any specific endpoint on the MTA, then this MIB object contains the MTA identifier. An MTA endpoint can be uniquely identified using a combination of the MTA identifier and the endpoint number. The MTA is identified via its Fully-Qualified Domain Name (FQDN) and the associated IP address at the given point in time. The format of the value contained by this MIB object is as follows: aaln/n:<FQDN>/<IP>, when it identifies an endpoint, 'n' being the endpoint number; or, <FQDN>/<IP>, when it identifies an MTA. The value contained by this MIB object needs to observe the SnmpAdminString definition requirements.
.1.3.6.1.2.1.182.1.5.1.1.7,PKTC-IETF-EVENT-MIB::pktcEventLogType,BITS,read-only,,current,local(0):syslog(1):snmpTrap(2):snmpInform(3),This MIB object contains the type of actions taken by the MTA when the event indicated by the MIB object pktcEventLogIdentifier occurred. A bit with a value of '1' indicates the corresponding action was taken. Setting it to a value of '0' indicates that the corresponding action was not taken. An event may trigger one or more actions (e.g., syslog and SNMP) or result only in a local log. An action may also be prevented due to throttling, in which case it is not reported by this MIB object.
.1.3.6.1.2.1.182.1.5.1.1.8,PKTC-IETF-EVENT-MIB::pktcEventLogTargetInfo,OCTET,read-only,,current,,This MIB object contains a comma-separated list of the actions taken for external notifications, along with the target IP address for the generated events. Locally stored events MUST NOT be recorded in this MIB object. The syntax is as: <action-1/IP>,<action-2/IP>,<action-3/IP> Where <action-n/IP> is to be denoted as follows: For syslog events: syslog/<IP address of the syslog server> For SNMP traps: snmpTrap/<IP address of the SNMP server> For SNMP INFORMS: snmpInform/<IP address of the SNMP server> If there are multiple targets for the same type (SNMP traps sent to multiple IP addresses) or if there are multiple message types sent to the same IP (syslog and SNMP sent to the same IP address), they need to be reported individually. It is to be noted that this MIB object may not be able to store all the data in some cases (e.g., multiple IPv6 addresses), in which case some actions may not be reported. In such cases, the MTA MUST present a value of '...' at the end of the value. Values contained by this MIB object need to observe the SnmpAdminString definition requirements.
.1.3.6.1.2.1.182.1.5.1.1.9,PKTC-IETF-EVENT-MIB::pktcEventLogCorrelationId,Unsigned32,read-only,,current,,This MIB object contains the correlation ID generated by the MTA during the initiation of the last provisioning flow, within or following which the event occurred. Although a correlation ID once generated after MTA reset does not change until next MTA reset, the value of this object will differ for the events preserved across MTA resets in case of a persistent pktcEventLogTable. For more information on the generation of correlation IDs, refer to the corresponding PacketCable/IPCablecom Device Provisioning specifications.
.1.3.6.1.2.1.182.1.5.1.1.10,PKTC-IETF-EVENT-MIB::pktcEventLogAdditionalInfo,OCTET,read-only,,current,,This MIB object contains additional information in relation to the corresponding event that an MTA might wish to report, such as parameterized data or debugging information. The format is vendor-specific. If the MTA cannot provide any additional information for the particular event generated, it MUST populate this MIB object with a zero-length OCTET-STRING. Vendors providing this information need to observe the SnmpAdminString definition requirements, such as the use of control code sequence CR LF for newline.
.1.3.6.1.2.1.182.2,PKTC-IETF-EVENT-MIB::pktcEventConformance,,,,,,
.1.3.6.1.2.1.182.2.1,PKTC-IETF-EVENT-MIB::pktcEventCompliances,,,,,,
.1.3.6.1.2.1.182.2.1.3,PKTC-IETF-EVENT-MIB::pktcEventBasicCompliance,,,,,,The compliance statement for devices that implement the event-reporting feature.
.1.3.6.1.2.1.182.2.2,PKTC-IETF-EVENT-MIB::pktcEventGroups,,,,,,
.1.3.6.1.2.1.182.2.2.1,PKTC-IETF-EVENT-MIB::pktcEventGroup,,,,,,Group of MIB objects for PacketCable Management Event MIB.
.1.3.6.1.2.1.182.2.2.2,PKTC-IETF-EVENT-MIB::pktcEventNotificationGroup,,,,,,Group of MIB objects for notifications related to change in status of the MTA Device.
.1.3.6.1.2.1.183,PW-ATM-MIB::pwAtmMIB,,,,,,This MIB contains managed object definitions for pseudowire emulation of ATM over Packet Switched Networks (PSNs). This MIB supplements the PW-STD-MIB module. The PW-STD-MIB contains structures and MIB associations generic to pseudowire (PW) emulation. PW-specific MIBs (such as this) contain config and stats for specific PW types. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5605; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.183.0,PW-ATM-MIB::pwAtmNotifications,,,,,,
.1.3.6.1.2.1.183.1,PW-ATM-MIB::pwAtmObjects,,,,,,
.1.3.6.1.2.1.183.1.1,PW-ATM-MIB::pwAtmOutboundTable,,not-accessible,,current,,This table specifies the information for an ATM PW to be carried over the PSN in the outbound direction. An entry is created in this table for every entry in the pwTable with a pwType equal to one of the following: atmAal5SduVcc(2), atmCell1to1Vcc(12), atmCell1to1Vpc(13) or atmAal5PduVcc(14), or atmTransparent(3).
.1.3.6.1.2.1.183.1.1.1,PW-ATM-MIB::pwAtmOutboundEntry,,not-accessible,pwIndex,current,,A row in this table represents an ATM PW that needs to be adapted and carried over the PSN. This table is indexed by pwIndex from pwTable. Unless otherwise specified, all writeable objects in this table MUST NOT be changed after row activation in the generic pwTable, and values must persist after reboot.
.1.3.6.1.2.1.183.1.1.1.1,PW-ATM-MIB::pwAtmOutboundAtmIf,Integer32,read-create,,current,,The ATM Interface that receives cells from the ATM network.
.1.3.6.1.2.1.183.1.1.1.2,PW-ATM-MIB::pwAtmOutboundVpi,INTEGER,read-create,,current,,VPI value of this ATM PW. The value may indicate the translated value when egress generates new VPI.
.1.3.6.1.2.1.183.1.1.1.3,PW-ATM-MIB::pwAtmOutboundVci,INTEGER,read-create,,current,,VCI value of this ATM PW. The value may indicate the translated value when egress generates new VCI.
.1.3.6.1.2.1.183.1.1.1.4,PW-ATM-MIB::pwAtmOutboundTrafficParamDescr,OBJECT,read-create,,current,,This object represents a pointer to an ATM traffic-parameter-specific row in either a private or standard table that will be employed while receiving cells from the ATM network. This row should contain a set of self-consistent ATM traffic parameters including the ATM traffic service category. A value of 0.0 indicates Best Effort.
.1.3.6.1.2.1.183.1.1.1.5,PW-ATM-MIB::pwAtmOutboundRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, or delete a row in this table. Unless otherwise specified, all writeable objects in this table MUST NOT be changed after row activation as explained in the pwAtmOutboundEntry. 
.1.3.6.1.2.1.183.1.3,PW-ATM-MIB::pwAtmInboundTable,,not-accessible,,current,,This table specifies the information for an ATM PW in the inbound direction.
.1.3.6.1.2.1.183.1.3.1,PW-ATM-MIB::pwAtmInboundEntry,,not-accessible,pwIndex,current,,A row in this table represents an ATM PW that needs to be sent into the ATM network after reconstructing cells from packets received from a PSN. This table is indexed by pwIndex from pwTable. An entry is created in this table for every entry in the pwTable with a pwType equal to one of the following: atmAal5SduVcc(2), atmCell1to1Vcc(12), atmCell1to1Vpc(13), atmAal5PduVcc(14), or atmTransparent(3). Unless otherwise specified, all writeable objects in this table MUST NOT be changed after row activation in the generic pwTable, and values must persist after reboot.
.1.3.6.1.2.1.183.1.3.1.1,PW-ATM-MIB::pwAtmInboundAtmIf,Integer32,read-create,,current,,The ATM Interface that sends cells into the ATM network after reconstructing cells from packets received from a PSN.
.1.3.6.1.2.1.183.1.3.1.2,PW-ATM-MIB::pwAtmInboundVpi,INTEGER,read-create,,current,,VPI value of this ATM PW. If the pwType is atmTransparent, then the value will be set to zero.
.1.3.6.1.2.1.183.1.3.1.3,PW-ATM-MIB::pwAtmInboundVci,INTEGER,read-create,,current,,VCI value of this ATM PW. If the pwType is atmTransparent, atmCell1to1Vpc, or atmCellNto1Vpc, then the value will be set to zero.
.1.3.6.1.2.1.183.1.3.1.4,PW-ATM-MIB::pwAtmInboundTrafficParamDescr,OBJECT,read-create,,current,,This object represents a pointer to an ATM traffic-parameter- specific row in either a private or standard table that will be employed while transmitting into the ATM network. This table contains a set of self-consistent ATM traffic parameters including the ATM traffic service category. A value of 0.0 indicates Best Effort.
.1.3.6.1.2.1.183.1.3.1.5,PW-ATM-MIB::pwAtmInboundRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, or delete a row in this table. Unless otherwise specified, all writeable objects in this table MUST NOT be changed after row activation as explained in the pwAtmInboundEntry. 
.1.3.6.1.2.1.183.1.5,PW-ATM-MIB::pwAtmCfgTable,,not-accessible,,current,,This table specifies generic information for an ATM PW to be carried over PSN in any mode.
.1.3.6.1.2.1.183.1.5.1,PW-ATM-MIB::pwAtmCfgEntry,,not-accessible,pwIndex,current,,This table contains a set of parameters for the ATM PW that needs to be adapted and carried over the PSN. This table is indexed by pwIndex from pwTable. An entry is created for every new ATM type associated pwIndex in the pwTable. Unless otherwise specified, all read-write objects in this table MAY be changed when the PW is defined as not active, and all RW objects values must persist after reboot.
.1.3.6.1.2.1.183.1.5.1.1,PW-ATM-MIB::pwAtmCfgMaxCellConcatenation,Unsigned32,read-write,,current,,The maximum number of ATM cells that can be concatenated into one PW packet towards the PSN. In a non-LDP or other signaling protocol environment, this object MAY be changed at anytime, but traffic might be interrupted; otherwise, it may be changed when PW is not active.
.1.3.6.1.2.1.183.1.5.1.2,PW-ATM-MIB::pwAtmCfgFarEndMaxCellConcatenation,Unsigned32,read-write,,current,,The maximum number of ATM cells that can be concatenated into one PW packet towards PSN as reported by the far end. If there is no LDP in use, the object will either return a value of 0 or allow setting it for calculating protocol overhead.
.1.3.6.1.2.1.183.1.5.1.3,PW-ATM-MIB::pwAtmCfgTimeoutMode,INTEGER,read-write,,current,notApplicable(1):disabled(2):enabled(3),This object determines whether or not a packet can be transmitted to the PSN based on timeout expiration for collecting cells. The actual handling of the timeout is implementation-specific; as such, this object may be changed at any time under proper consideration of the traffic interruption effect.
.1.3.6.1.2.1.183.1.5.1.4,PW-ATM-MIB::pwAtmClpQosMapping,INTEGER,read-write,,current,true(1):false(2),This object indicates whether the Cell Loss Priority (CLP) bits should be considered when setting the value in the Quality-of-Service fields of the encapsulating protocol (e.g., EXP fields of the MPLS Label Stack). Selecting True allows the drop precedence to be preserved across the PSN. In transparent cell transport, the value of this object MUST be false(2); in other cases, it can be changed at any time.
.1.3.6.1.2.1.183.1.6,PW-ATM-MIB::pwAtmOutboundNto1Table,,not-accessible,,current,,This table specifies the information for an ATM PW to be carried over the PSN in the outbound direction. Up to N entries can be created in this table for every entry in the pwTable with a pwType equal to: atmCellNto1Vcc(9) or atmCellNto1Vpc(10). An entry can be created only when the VP/VC are known. A single entry will be created in this table for every entry in the pwTable with a pwType equal to one of the following: atmCell1to1Vcc(12), atmCell1to1Vpc(13), atmAal5PduVcc(14), atmAal5SduVcc(2), or atmTransparent(3). 
.1.3.6.1.2.1.183.1.6.1,PW-ATM-MIB::pwAtmOutboundNto1Entry,,not-accessible,pwIndex:pwAtmOutboundNto1AtmIf:pwAtmOutboundNto1Vpi:pwAtmOutboundNto1Vci,current,,A row in this table represents an ATM PW that needs to be adapted and carried over PSN. This table is indexed by pwIndex from pwTable and the ATM interface with VPL/VCLs. In atmTransparent(3), Vpi and VCi will be 0xFFFF during set operation. Unless otherwise specified, all read-create objects in this table MUST NOT be changed after row activation and SHOULD remain unchanged after reboot.
.1.3.6.1.2.1.183.1.6.1.1,PW-ATM-MIB::pwAtmOutboundNto1AtmIf,Integer32,not-accessible,,current,,The ATM Interface that receives cells from the ATM network.
.1.3.6.1.2.1.183.1.6.1.2,PW-ATM-MIB::pwAtmOutboundNto1Vpi,INTEGER,not-accessible,,current,,VPI value of this ATM PW. In atmTransparent(3), Vpi will be the equivalent of 0xFFFF.
.1.3.6.1.2.1.183.1.6.1.3,PW-ATM-MIB::pwAtmOutboundNto1Vci,INTEGER,not-accessible,,current,,VCI value of this ATM PW. In atmTransparent(3), or the VP case, the value will be the equivalent of 0xFFFF.
.1.3.6.1.2.1.183.1.6.1.4,PW-ATM-MIB::pwAtmOutboundNto1RowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify or delete a row in this table.
.1.3.6.1.2.1.183.1.6.1.5,PW-ATM-MIB::pwAtmOutboundNto1TrafficParamDescr,OBJECT,read-create,,current,,This object represents a pointer to an ATM traffic-parameter- specific row in either private or standard table that will be employed while receiving cells from the ATM network. This table should contain a set of self-consistent ATM traffic parameters including the ATM traffic service category. A value of 0.0 indicates Best Effort.
.1.3.6.1.2.1.183.1.6.1.6,PW-ATM-MIB::pwAtmOutboundNto1MappedVpi,INTEGER,read-create,,current,,The egress-generated VPI value of this ATM PW. The entry is valid for PW type of atmCellNto1Vcc(9), atmCellNto1Vpc(10), atmCell1to1Vcc(12), or atmCell1to1Vpc(13). In other types, the value will be the equivalent of 0xFFFF. Value MAY be changed when the PW is defined as not active. 
.1.3.6.1.2.1.183.1.6.1.7,PW-ATM-MIB::pwAtmOutboundNto1MappedVci,INTEGER,read-create,,current,,The egress-generated VCI value of this ATM PW. The entry is valid for PW type of atmCellNto1Vcc(9), atmCellNto1Vpc(10), atmCell1to1Vcc(12), or atmCell1to1Vpc(13. In the VP case or other types, the value will be the equivalent of 0xFFFF. Value MAY be changed when the PW is defined as not active.
.1.3.6.1.2.1.183.1.7,PW-ATM-MIB::pwAtmInboundNto1Table,,not-accessible,,current,,This table specifies the information for an ATM PW to be carried over PSN in the Inbound direction. Up to N entries can be created in this table for every entry in the pwTable with a pwType equal to: atmCellNto1Vcc(9) or atmCellNto1Vpc(10). An entry can be created only when the VP/VC are known. A single entry will be created in this table for every entry in the pwTable with a pwType equal to one of the following: atmCell1to1Vcc(12), atmCell1to1Vpc(13), atmAal5PduVcc(14), atmAal5SduVcc(2), or atmTransparent(3).
.1.3.6.1.2.1.183.1.7.1,PW-ATM-MIB::pwAtmInboundNto1Entry,,not-accessible,pwIndex:pwAtmInboundNto1AtmIf:pwAtmInboundNto1Vpi:pwAtmInboundNto1Vci,current,,A row in this table represents an ATM PW that needs to be adapted and carried over PSN. This table is indexed by pwIndex from pwTable and the ATM interface with VPL/VCLs. In atmTransparent(3), Vpi and VCi will be 0xFFFF during set operation. Unless otherwise specified, all Read-Create objects in this table MUST NOT be changed after row activation and SHOULD remain unchanged after reboot.
.1.3.6.1.2.1.183.1.7.1.1,PW-ATM-MIB::pwAtmInboundNto1AtmIf,Integer32,not-accessible,,current,,The ATM Interface that receives cells from the ATM network.
.1.3.6.1.2.1.183.1.7.1.2,PW-ATM-MIB::pwAtmInboundNto1Vpi,INTEGER,not-accessible,,current,,VPI value of this ATM PW. In atmTransparent(3), Vpi will be the equivalent of 0xFFFF.
.1.3.6.1.2.1.183.1.7.1.3,PW-ATM-MIB::pwAtmInboundNto1Vci,INTEGER,not-accessible,,current,,VCI value of this ATM PW. In atmTransparent(3), or the VP case, the value will be the equivalent of 0xFFFF.
.1.3.6.1.2.1.183.1.7.1.4,PW-ATM-MIB::pwAtmInboundNto1RowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, or delete a row in this table.
.1.3.6.1.2.1.183.1.7.1.5,PW-ATM-MIB::pwAtmInboundNto1TrafficParamDescr,OBJECT,read-create,,current,,This object represents a pointer to an ATM traffic-parameter- specific row in either a private or standard table that will be employed while receiving cells from the ATM network. This table should contain a set of self-consistent ATM traffic parameters including the ATM traffic service category. A value of 0.0 indicates Best Effort.
.1.3.6.1.2.1.183.1.7.1.6,PW-ATM-MIB::pwAtmInboundNto1MappedVpi,INTEGER,read-create,,current,,The generated VPI value of this ATM PW. The entry is valid for PW type of atmCellNto1Vcc(9), atmCellNto1Vpc(10), atmCell1to1Vcc(12), or atmCell1to1Vpc(13). In other types, the value will be the equivalent of 0xFFFF. Value MAY be changed when the PW is defined as not active.
.1.3.6.1.2.1.183.1.7.1.7,PW-ATM-MIB::pwAtmInboundNto1MappedVci,INTEGER,read-create,,current,,The generated VCI value of this ATM PW. The entry is valid for PW type of atmCellNto1Vcc(9), atmCellNto1Vpc(10), atmCell1to1Vcc(12), or atmCell1to1Vpc(13. In the VP case or other types, the value will be the equivalent of 0xFFFF. Value MAY be changed when the PW is defined as not active.
.1.3.6.1.2.1.183.1.8,PW-ATM-MIB::pwAtmPerfCurrentTable,,not-accessible,,current,,The current 15-minute interval counts are in this table. This table provides performance information per ATM PW.
.1.3.6.1.2.1.183.1.8.1,PW-ATM-MIB::pwAtmPerfCurrentEntry,,not-accessible,pwIndex,current,,An entry in this table is created by the agent for every pwAtmCfgTable entry. After 15 minutes, the contents of this table entry are copied to a new entry in the pwAtmPerfInterval table and the counts in this entry are reset to zero.
.1.3.6.1.2.1.183.1.8.1.1,PW-ATM-MIB::pwAtmPerfCurrentMissingPkts,Gauge32,read-only,,current,,Number of missing packets (as detected via control word sequence number gaps).
.1.3.6.1.2.1.183.1.8.1.2,PW-ATM-MIB::pwAtmPerfCurrentPktsReOrder,Gauge32,read-only,,current,,Number of packets detected out of sequence (via control word sequence number), but successfully re-ordered. Note: some implementations may not support this feature.
.1.3.6.1.2.1.183.1.8.1.3,PW-ATM-MIB::pwAtmPerfCurrentPktsMisOrder,Gauge32,read-only,,current,,Number of packets detected out of order (via control word sequence numbers).
.1.3.6.1.2.1.183.1.8.1.4,PW-ATM-MIB::pwAtmPerfCurrentPktsTimeout,Gauge32,read-only,,current,,Number of packets transmitted due to timeout expiration while attempting to collect cells.
.1.3.6.1.2.1.183.1.8.1.5,PW-ATM-MIB::pwAtmPerfCurrentCellsXmit,Gauge32,read-only,,current,,Number of transmitted cells.
.1.3.6.1.2.1.183.1.8.1.6,PW-ATM-MIB::pwAtmPerfCurrentCellsDropped,Gauge32,read-only,,current,,Number of dropped cells.
.1.3.6.1.2.1.183.1.8.1.7,PW-ATM-MIB::pwAtmPerfCurrentCellsReceived,Gauge32,read-only,,current,,Number of received cells.
.1.3.6.1.2.1.183.1.8.1.8,PW-ATM-MIB::pwAtmPerfCurrentUnknownCells,Gauge32,read-only,,current,,Number of cells received from the PSN with unknown VPI or VCI values. This object is relevant only in N:1 mode.
.1.3.6.1.2.1.183.1.9,PW-ATM-MIB::pwAtmPerfIntervalTable,,not-accessible,,current,,This table provides performance information per ATM PW similar to the pwAtmPerfCurrentTable above. However, these counts represent historical 15 minute intervals. Typically, this table will have a maximum of 96 entries for a 24 hour period. 
.1.3.6.1.2.1.183.1.9.1,PW-ATM-MIB::pwAtmPerfIntervalEntry,,not-accessible,pwIndex:pwAtmPerfIntervalNumber,current,,An entry in this table is created by the agent for every pwAtmPerfCurrentEntry that is 15 minutes old. The contents of the Current entry are copied to the new entry here. The Current entry then resets its counts to zero for the next current 15 minute interval. 
.1.3.6.1.2.1.183.1.9.1.1,PW-ATM-MIB::pwAtmPerfIntervalNumber,Unsigned32,not-accessible,,current,,A number (normally between 1 and 96 to cover a 24 hour period) that identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1. The minimum range of N is 1 through 4. The default range is 1 through 32. The maximum value of N is 96.
.1.3.6.1.2.1.183.1.9.1.2,PW-ATM-MIB::pwAtmPerfIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.183.1.9.1.3,PW-ATM-MIB::pwAtmPerfIntervalDuration,Unsigned32,read-only,,current,,The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock, may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
.1.3.6.1.2.1.183.1.9.1.4,PW-ATM-MIB::pwAtmPerfIntervalMissingPkts,Gauge32,read-only,,current,,Number of missing packets (as detected via control word sequence number gaps).
.1.3.6.1.2.1.183.1.9.1.5,PW-ATM-MIB::pwAtmPerfIntervalPktsReOrder,Gauge32,read-only,,current,,Number of packets detected out of sequence (via control word sequence number), but successfully re-ordered. Note: some implementations may not support this feature.
.1.3.6.1.2.1.183.1.9.1.6,PW-ATM-MIB::pwAtmPerfIntervalPktsMisOrder,Gauge32,read-only,,current,,Number of packets detected out of order (via control word sequence numbers).
.1.3.6.1.2.1.183.1.9.1.7,PW-ATM-MIB::pwAtmPerfIntervalPktsTimeout,Gauge32,read-only,,current,,Number of packets transmitted due to timeout expiration.
.1.3.6.1.2.1.183.1.9.1.8,PW-ATM-MIB::pwAtmPerfIntervalCellsXmit,Gauge32,read-only,,current,,Number of transmitted cells.
.1.3.6.1.2.1.183.1.9.1.9,PW-ATM-MIB::pwAtmPerfIntervalCellsDropped,Gauge32,read-only,,current,,Number of dropped cells.
.1.3.6.1.2.1.183.1.9.1.10,PW-ATM-MIB::pwAtmPerfIntervalCellsReceived,Gauge32,read-only,,current,,Number of received cells.
.1.3.6.1.2.1.183.1.9.1.11,PW-ATM-MIB::pwAtmPerfIntervalUnknownCells,Gauge32,read-only,,current,,Number of cells received from the PSN with unknown VPI or VCI values. This object is relevant only in N:1 mode.
.1.3.6.1.2.1.183.1.10,PW-ATM-MIB::pwAtmPerf1DayIntervalTable,,not-accessible,,current,,This table provides performance information per ATM PW similar to the pwAtmPerfIntervalTable above. However, these counters represent historical one-day intervals up to one full month.
.1.3.6.1.2.1.183.1.10.1,PW-ATM-MIB::pwAtmPerf1DayIntervalEntry,,not-accessible,pwIndex:pwAtmPerf1DayIntervalNumber,current,,An entry is created in this table by the agent for every entry in the pwAtmCfgTable table.
.1.3.6.1.2.1.183.1.10.1.1,PW-ATM-MIB::pwAtmPerf1DayIntervalNumber,Unsigned32,not-accessible,,current,,The number of intervals, where 1 indicates current day measured period and 2 and above indicate previous days, respectively.
.1.3.6.1.2.1.183.1.10.1.2,PW-ATM-MIB::pwAtmPerf1DayIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This object indicates if the data for this interval is valid.
.1.3.6.1.2.1.183.1.10.1.3,PW-ATM-MIB::pwAtmPerf1DayIntervalDuration,Unsigned32,read-only,,current,,The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
.1.3.6.1.2.1.183.1.10.1.4,PW-ATM-MIB::pwAtmPerf1DayIntervalMissingPkts,Counter32,read-only,,current,,Number of missing packets (as detected via control word sequence number gaps).
.1.3.6.1.2.1.183.1.10.1.5,PW-ATM-MIB::pwAtmPerf1DayIntervalPktsReOrder,Counter32,read-only,,current,,Number of packets detected out of sequence (via control word sequence number), but successfully re-ordered. Note: some implementations may not support this feature.
.1.3.6.1.2.1.183.1.10.1.6,PW-ATM-MIB::pwAtmPerf1DayIntervalPktsMisOrder,Counter32,read-only,,current,,Number of packets detected out of order (via control word sequence numbers) and that could not be re-ordered.
.1.3.6.1.2.1.183.1.10.1.7,PW-ATM-MIB::pwAtmPerf1DayIntervalPktsTimeout,Counter32,read-only,,current,,Number of packets transmitted due to timeout expiration.
.1.3.6.1.2.1.183.1.10.1.8,PW-ATM-MIB::pwAtmPerf1DayIntervalCellsXmit,Counter32,read-only,,current,,Number of transmitted cells.
.1.3.6.1.2.1.183.1.10.1.9,PW-ATM-MIB::pwAtmPerf1DayIntervalCellsDropped,Counter32,read-only,,current,,Number of dropped cells.
.1.3.6.1.2.1.183.1.10.1.10,PW-ATM-MIB::pwAtmPerf1DayIntervalCellsReceived,Counter32,read-only,,current,,Number of received cells.
.1.3.6.1.2.1.183.1.10.1.11,PW-ATM-MIB::pwAtmPerf1DayIntervalUnknownCells,Counter32,read-only,,current,,Number of cells received from the PSN with unknown VPI or VCI values. This object is relevant only in N:1 mode.
.1.3.6.1.2.1.183.2,PW-ATM-MIB::pwAtmConformance,,,,,,
.1.3.6.1.2.1.183.2.1,PW-ATM-MIB::pwAtmCompliances,,,,,,
.1.3.6.1.2.1.183.2.1.2,PW-ATM-MIB::pwAtmCompliance,,,,,,The compliance statement for agents that support ATM PW.
.1.3.6.1.2.1.183.2.2,PW-ATM-MIB::pwAtmGroups,,,,,,
.1.3.6.1.2.1.183.2.2.5,PW-ATM-MIB::pwAtmCfgGroup,,,,,,Collection of objects for basic ATM PW configuration.
.1.3.6.1.2.1.183.2.2.6,PW-ATM-MIB::pwAtmPerfGroup,,,,,,Collection of objects for basic ATM PW Performance.
.1.3.6.1.2.1.183.2.2.7,PW-ATM-MIB::pwAtmOutbound1to1Group,,,,,,Collection of objects for basic 1:1 ATM PW outbound configuration.
.1.3.6.1.2.1.183.2.2.8,PW-ATM-MIB::pwAtmInbound1to1Group,,,,,,Collection of objects for basic 1:1 ATM PW inbound configuration.
.1.3.6.1.2.1.183.2.2.9,PW-ATM-MIB::pwAtmOutboundNto1Group,,,,,,Collection of objects for N:1, 1:1, or transparent ATM PW outbound configuration.
.1.3.6.1.2.1.183.2.2.10,PW-ATM-MIB::pwAtmInboundNto1Group,,,,,,Collection of objects for N:1, 1:1, or transparent ATM PW inbound configuration.
.1.3.6.1.2.1.184,NEMO-MIB::nemoMIB,,,,,,Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5488; see the RFC itself for full legal notices.
.1.3.6.1.2.1.184.0,NEMO-MIB::nemoNotifications,,,,,,
.1.3.6.1.2.1.184.0.1,NEMO-MIB::nemoHomeTunnelEstablished,,,,,,This notification is sent by the mobile router every time the tunnel is established between the home agent and the mobile router. 
.1.3.6.1.2.1.184.0.2,NEMO-MIB::nemoHomeTunnelReleased,,,,,,This notification is sent by the mobile router every time the tunnel is deleted between the home agent and the mobile router. 
.1.3.6.1.2.1.184.1,NEMO-MIB::nemoObjects,,,,,,
.1.3.6.1.2.1.184.1.1,NEMO-MIB::nemoCore,,,,,,
.1.3.6.1.2.1.184.1.1.1,NEMO-MIB::nemoSystem,,,,,,
.1.3.6.1.2.1.184.1.1.1.1,NEMO-MIB::nemoCapabilities,BITS,read-only,,current,mobileRouter(0):homeAgentSupport(1),This object indicates the NEMO functions that are supported by this managed entity. Multiple NEMO functions may be supported by a single entity. 
.1.3.6.1.2.1.184.1.1.1.2,NEMO-MIB::nemoStatus,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether the NEMO function is enabled for the managed entity. If it is enabled, the agent discovery and registration functions will be operational. Changing the status from enabled(1) to disabled(2) will terminate the agent discovery and registration functions. On the other hand, changing the status from disabled(2) to enabled(1) will start the agent discovery and registration functions. The value of this object MUST remain unchanged across reboots of the managed entity. 
.1.3.6.1.2.1.184.1.1.2,NEMO-MIB::nemoBindings,,,,,,
.1.3.6.1.2.1.184.1.1.2.1,NEMO-MIB::nemoBindingCacheTable,,not-accessible,,current,,This table models the Binding Cache that includes NEMO-related information and that is maintained by the home agent. Entries in this table are not required to survive a reboot of the home agent. 
.1.3.6.1.2.1.184.1.1.2.1.1,NEMO-MIB::nemoBindingCacheEntry,,not-accessible,,current,,An entry containing additional information related to NEMO-enabled entries in the Binding Cache table of the home agent. 
.1.3.6.1.2.1.184.1.1.2.1.1.1,NEMO-MIB::nemoBindingMrFlag,INTEGER,read-only,,current,true(1):false(2),true(1): indicates that the Binding Cache entry is from an entity acting as a mobile router. false(2): implies that the Binding Cache entry is from an entity acting as a mobile node. 
.1.3.6.1.2.1.184.1.1.2.1.1.2,NEMO-MIB::nemoBindingMrMode,INTEGER,read-only,,current,implicitMode(1):explicitMode(2),implicitMode(1): the Mobile Network Prefix Option is not included in the Binding Update by the mobile router. explicitMode(2): the mobile router included one or more Mobile Network Prefix Options in the Binding Update. 
.1.3.6.1.2.1.184.1.1.3,NEMO-MIB::nemoConfiguration,,,,,,
.1.3.6.1.2.1.184.1.1.4,NEMO-MIB::nemoStats,,,,,,
.1.3.6.1.2.1.184.1.1.4.1,NEMO-MIB::nemoCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this NEMO entity's counters, viz., counters with OID prefix 'nemoMrConf', 'nemoMrRegnCounters', 'nemoMrGlobalStats', or 'nemoHaGlobalStats', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. 
.1.3.6.1.2.1.184.1.2,NEMO-MIB::nemoMr,,,,,,
.1.3.6.1.2.1.184.1.2.1,NEMO-MIB::nemoMrSystem,,,,,,
.1.3.6.1.2.1.184.1.2.1.1,NEMO-MIB::nemoMrEgressIfTable,,not-accessible,,current,,A table representing the egress interfaces that will be used by the mobile router for roaming to foreign networks. Each entry in this table represents a configured egress interface. 
.1.3.6.1.2.1.184.1.2.1.1.1,NEMO-MIB::nemoMrEgressIfEntry,,not-accessible,nemoMrEgressIfIndex,current,,An entry in the egress interface table. It represents a single egress interface entry. 
.1.3.6.1.2.1.184.1.2.1.1.1.1,NEMO-MIB::nemoMrEgressIfIndex,Integer32,not-accessible,,current,,The index of the interface on the mobile router. 
.1.3.6.1.2.1.184.1.2.1.1.1.2,NEMO-MIB::nemoMrEgressIfPriority,Unsigned32,read-only,,current,,The priority configured to the egress interface. This value will be configured to a value between 0 and 255. 
.1.3.6.1.2.1.184.1.2.1.1.1.3,NEMO-MIB::nemoMrEgressIfDescription,OCTET,read-only,,current,,A human-readable textual description of the egress interface on the mobile router. 
.1.3.6.1.2.1.184.1.2.1.1.1.4,NEMO-MIB::nemoMrEgressIfRoamHoldDownTime,Gauge32,read-only,,current,,This object indicates the time for which the egress interface will be held down during roaming to avoid interface flapping. 
.1.3.6.1.2.1.184.1.2.2,NEMO-MIB::nemoMrConf,,,,,,
.1.3.6.1.2.1.184.1.2.2.1,NEMO-MIB::nemoMrDiscoveryRequests,Counter32,read-only,,current,,Total number of Modified Dynamic Home Agent Address Discovery Requests, with Mobile Router Support Flag set, sent by the mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.2.2,NEMO-MIB::nemoMrDiscoveryReplies,Counter32,read-only,,current,,Total number of Modified Dynamic Home Agent Address Discovery Replies, with Mobile Router Support Flag set, received by the mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.2.3,NEMO-MIB::nemoMrDiscoveryRepliesRouterFlagZero,Counter32,read-only,,current,,Total number of Modified Dynamic Home Agent Address Discovery Replies, with Mobile Router Support Flag set to 0 although the flag in the corresponding request is set to 1. It implies that there is no home agent that supports mobile router functionality in the home network. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.2.4,NEMO-MIB::nemoMrMovedHome,Counter32,read-only,,current,,Number of times the mobile router has detected movement from a foreign network to its home network. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.2.5,NEMO-MIB::nemoMrMovedOutofHome,Counter32,read-only,,current,,Number of times the mobile router has detected movement to a foreign network from the home network, has acquired a care-of address, and has initiated the care-of address registration process. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.2.6,NEMO-MIB::nemoMrMovedFNtoFN,Counter32,read-only,,current,,Number of times the mobile router has detected movement to/from a foreign network from/to another foreign network. Note that 'movement' implies movement in layer 3, i.e., the mobile router's care-of address changed, and it initiated the care-of address registration process. If there are multiple egress interfaces, this counter counts the total number of movements. The movement as a mobile node of the mobile entity is not counted. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.2.7,NEMO-MIB::nemoMrBetterIfDetected,Counter32,read-only,,current,,Number of times the NEMO entity has found an egress interface with better priority. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.3,NEMO-MIB::nemoMrRegistration,,,,,,
.1.3.6.1.2.1.184.1.2.3.1,NEMO-MIB::nemoMrBLTable,,not-accessible,,current,,This table corresponds to the Binding Update List (BL) that includes NEMO-related information and that is maintained by the mobile router. The table holds a row for every binding that the mobile router has established or is trying to establish. Entries from the table are deleted as the lifetime of the binding expires. 
.1.3.6.1.2.1.184.1.2.3.1.1,NEMO-MIB::nemoMrBLEntry,,not-accessible,,current,,An entry pertaining to NEMO-related information contained in a Binding Update sent by a NEMO-enabled mobile router to its home agent. 
.1.3.6.1.2.1.184.1.2.3.1.1.1,NEMO-MIB::nemoMrBLMode,INTEGER,read-only,,current,implicitMode(1):explicitMode(2),implicitMode(1): the Mobile Network Prefix Option is not included in the Binding Update by the mobile router. explicitMode(2): the mobile router included one or more Mobile Network Prefix Options in the Binding Update. 
.1.3.6.1.2.1.184.1.2.3.1.1.2,NEMO-MIB::nemoMrBLMrFlag,INTEGER,read-only,,current,true(1):false(2),true(1): the mobile router sent the Binding Update with Mobile Router Flag set. false(2): the mobile router did not send the Binding Update with Mobile Router Flag set. This implies that the mobile router is acting as a mobile node. 
.1.3.6.1.2.1.184.1.2.3.1.1.3,NEMO-MIB::nemoMrBLHomeAddressPrefixLength,Unsigned32,read-only,,current,,The prefix length of the mobile router's home network. 
.1.3.6.1.2.1.184.1.2.3.1.1.4,NEMO-MIB::nemoMrBLCareofAddressPrefixLength,Unsigned32,read-only,,current,,The prefix length of the care-of address of the mobile router. 
.1.3.6.1.2.1.184.1.2.3.1.1.5,NEMO-MIB::nemoMrBLActiveEgressIfIndex,Integer32,read-only,,current,,The interface index of the currently active egress interface. 
.1.3.6.1.2.1.184.1.2.3.1.1.6,NEMO-MIB::nemoMrBLEstablishedHomeTunnelIfIndex,Integer32,read-only,,current,,The interface index of the tunnel established between the mobile router and the home agent for NEMO traffic. 
.1.3.6.1.2.1.184.1.2.3.2,NEMO-MIB::nemoMrRegnCounters,,,,,,
.1.3.6.1.2.1.184.1.2.3.2.1,NEMO-MIB::nemoMrMobilityMessagesSent,Counter32,read-only,,current,,The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, sent by the mobile node. This will include Binding Updates sent by a mobile router with the Mobile Router Flag set. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.3.2.2,NEMO-MIB::nemoMrMobilityMessagesRecd,Counter32,read-only,,current,,The total number of mobility messages, i.e., IPv6 datagrams with Mobility Header, received by the mobile node. This will include Binding Acknowledgements with Mobile Router Flag set that are sent to a mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.3.3,NEMO-MIB::nemoMrPrefixRegMode,INTEGER,read-write,,current,implicitMode(1):explicitMode(2),This object indicates the mode in which the mobile network prefixes will be registered with the home agent. implicitMode(1): the Mobile Network Prefix Option will not be included in the Binding Update by the mobile router. explicitMode(2): the mobile router will include one or more Mobile Network Prefix Options in the Binding Update. The value of this object MUST remain unchanged across reboots of the managed entity. 
.1.3.6.1.2.1.184.1.2.4,NEMO-MIB::nemoMrGlobalStats,,,,,,
.1.3.6.1.2.1.184.1.2.4.1,NEMO-MIB::nemoMrBindingAcksWONemoSupport,Counter32,read-only,,current,,The total number of Binding Acknowledgements without NEMO support received by the mobile router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.4.2,NEMO-MIB::nemoMrBindingAcksRegTypeChangeDisallowed,Counter32,read-only,,current,,The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Registration type change disallowed' (Code 139). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.4.3,NEMO-MIB::nemoMrBindingAcksOperationNotPermitted,Counter32,read-only,,current,,The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Mobile Router Operation not permitted' (Code 140). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.4.4,NEMO-MIB::nemoMrBindingAcksInvalidPrefix,Counter32,read-only,,current,,The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Invalid Prefix' (Code 141). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.4.5,NEMO-MIB::nemoMrBindingAcksNotAuthorizedForPrefix,Counter32,read-only,,current,,The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Not Authorized for Prefix' (Code 142). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.4.6,NEMO-MIB::nemoMrBindingAcksForwardingSetupFailed,Counter32,read-only,,current,,The total number of Binding Acknowledgements received by the mobile router with status code indicating 'Forwarding Setup failed' (Code 143). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.2.4.7,NEMO-MIB::nemoMrBindingAcksOtherError,Counter32,read-only,,current,,The total number of Binding Acknowledgements received by the mobile router (Mobile Router Flag is set) with status code other than: successfully processed --(Code 0 ) mobileRouterOperationNotPermitted (140) --(Code 140) invalidPrefix (141) --(Code 141) notAuthorizedForPrefix (142) --(Code 142) forwardingSetupFailed (143) --(Code 143) Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.3,NEMO-MIB::nemoCn,,,,,,
.1.3.6.1.2.1.184.1.4,NEMO-MIB::nemoHa,,,,,,
.1.3.6.1.2.1.184.1.4.1,NEMO-MIB::nemoHaAdvertisement,,,,,,
.1.3.6.1.2.1.184.1.4.2,NEMO-MIB::nemoHaStats,,,,,,
.1.3.6.1.2.1.184.1.4.2.1,NEMO-MIB::nemoHaGlobalStats,,,,,,
.1.3.6.1.2.1.184.1.4.2.1.1,NEMO-MIB::nemoHaBUAcksWONemoSupport,Counter32,read-only,,current,,The total number of Binding Acknowledgements without NEMO support sent by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.1.2,NEMO-MIB::nemoHaBUAcksRegTypeChangeDisallowed,Counter32,read-only,,current,,The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Registration type change disallowed' (Code 139). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.1.3,NEMO-MIB::nemoHaBUAcksOperationNotPermitted,Counter32,read-only,,current,,The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Mobile Router Operation not permitted' (Code 140). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.1.4,NEMO-MIB::nemoHaBUAcksInvalidPrefix,Counter32,read-only,,current,,The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Invalid Prefix' (Code 141). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.1.5,NEMO-MIB::nemoHaBUAcksNotAuthorizedForPrefix,Counter32,read-only,,current,,The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Not Authorized for Prefix' (Code 142). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.1.6,NEMO-MIB::nemoHaBUAcksForwardingSetupFailed,Counter32,read-only,,current,,The total number of Binding Update requests rejected by the home agent with status code in the Binding Acknowledgement indicating 'Forwarding Setup failed' (Code 143). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.1.7,NEMO-MIB::nemoHaBUAcksOtherError,Counter32,read-only,,current,,The total number of Binding Update requests from mobile routers (Mobile Router Flag is set) rejected by the home agent with status code other than: mobileRouterOperationNotPermitted (140) invalidPrefix (141) notAuthorizedForPrefix (142) forwardingSetupFailed (143) Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoCounterDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.2,NEMO-MIB::nemoHaCounterTable,,not-accessible,,current,,A table containing registration statistics for all mobile routers registered with the home agent. 
.1.3.6.1.2.1.184.1.4.2.2.1,NEMO-MIB::nemoHaCounterEntry,,not-accessible,mip6BindingHomeAddressType:mip6BindingHomeAddress,current,,Home agent registration statistics for a mobile router. Implementers need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.184.1.4.2.2.1.1,NEMO-MIB::nemoHaBURequestsAccepted,Counter32,read-only,,current,,Total number of Binding Update requests from the mobile router accepted by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoHaCtrDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.2.1.2,NEMO-MIB::nemoHaBURequestsDenied,Counter32,read-only,,current,,Total number of Binding Update requests from the mobile router rejected by the home agent. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of nemoHaCtrDiscontinuityTime. 
.1.3.6.1.2.1.184.1.4.2.2.1.3,NEMO-MIB::nemoHaBCEntryCreationTime,OCTET,read-only,,current,,The time when the current Binding Cache entry was created for the mobile router. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time. 
.1.3.6.1.2.1.184.1.4.2.2.1.4,NEMO-MIB::nemoHaBUAcceptedTime,OCTET,read-only,,current,,The time at which the last Binding Update was accepted by the home agent for this mobile router. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time. 
.1.3.6.1.2.1.184.1.4.2.2.1.5,NEMO-MIB::nemoHaBURejectionTime,OCTET,read-only,,current,,The time at which the last Binding Update was rejected by the home agent for this mobile router. If there have been no rejections, then this object will be inaccessible. An implementation MUST return all 11 bytes of the DateAndTime textual-convention so that a manager may retrieve the offset from GMT time. 
.1.3.6.1.2.1.184.1.4.2.2.1.6,NEMO-MIB::nemoHaRecentBURejectionCode,INTEGER,read-only,,current,mobileRouterOperationNotPermitted(140):invalidPrefix(141):notAuthorizedForPrefix(142):forwardingSetupFailed(143),The Status code (>= 128) in the latest Binding Acknowledgment indicating a rejection, sent to this mobile router. If a Binding Update request is rejected and a Binding Acknowledgment is not sent to this mobile router, then this will be the value of the Status code that corresponds to the reason of the rejection. If there have been no Binding Update request rejections, then this object will be inaccessible. 
.1.3.6.1.2.1.184.1.4.2.2.1.7,NEMO-MIB::nemoHaCtrDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of the counters in this row, viz., instances of 'nemoHaBURequestsAccepted' and 'nemoHaBURequestsDenied', suffered a discontinuity. If no such discontinuity has occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. 
.1.3.6.1.2.1.184.1.4.3,NEMO-MIB::nemoHaRegistration,,,,,,
.1.3.6.1.2.1.184.1.4.3.1,NEMO-MIB::nemoHaMobileNetworkPrefixTable,,not-accessible,,current,,This table contains the mobile network prefixes that the home agent maintains for the mobile router. The mobile network prefixes in this table are registered by Binding Updates or are manually pre-configured. 
.1.3.6.1.2.1.184.1.4.3.1.1,NEMO-MIB::nemoHaMobileNetworkPrefixEntry,,not-accessible,mip6BindingHomeAddressType:mip6BindingHomeAddress:nemoHaMobileNetworkPrefixSeqNo,current,,An entry for a mobile network prefix. The instances of the columnar objects in this entry pertain to an interface for a particular value of mip6BindingHomeAddressType, mip6BindingHomeAddress, and nemoHaMobileNetworkPrefixSeqNo. The nemoHaMobileNetworkPrefixSeqNo object is used to distinguish between multiple instances of the mobile network prefix in the same Binding Update for the same set of mip6BindingHomeAddressType and mip6BindingHomeAddress. There is no upper-bound on the maximum number of mobile network prefixes in a Binding Update but, for practical purposes, the upper bound of the value nemoHaMobileNetworkPrefixSeqNo is set to 1024. Implementers need to be aware that if the total number of octets in mip6BindingHomeAddress exceeds 112, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.184.1.4.3.1.1.1,NEMO-MIB::nemoHaMobileNetworkPrefixSeqNo,Unsigned32,not-accessible,,current,,A Binding Update may have multiple mobile network prefixes. This object, along with mip6BindingHomeAddressType and mip6BindingHomeAddress, uniquely identifies a row containing a single mobile network prefix for a mobile router in this table. 
.1.3.6.1.2.1.184.1.4.3.1.1.2,NEMO-MIB::nemoHaMobileNetworkPrefixType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type for the mobile network prefix that follows. 
.1.3.6.1.2.1.184.1.4.3.1.1.3,NEMO-MIB::nemoHaMobileNetworkPrefix,OCTET,read-only,,current,,A mobile network prefix related to the corresponding Binding Update. The type of the address represented by this object is specified by the corresponding nemoHaMobileNetworkPrefixType object. 
.1.3.6.1.2.1.184.1.4.3.1.1.4,NEMO-MIB::nemoHaMobileNetworkPrefixLength,Unsigned32,read-only,,current,,The length of the prefix specified by the corresponding nemoHaMobileNetworkPrefix object. 
.1.3.6.1.2.1.184.1.4.3.1.1.5,NEMO-MIB::nemoHaMobileNetworkPrefixSource,INTEGER,read-only,,current,configured(1):bindingUpdate(2),The information source of the mobile network prefix configured with the Binding Update. configured(1): indicates that the mobile network prefix has been manually pre-configured. bindingUpdate(2): indicates that the information is introduced to the home agent by the Mobile Network Prefix Option in the Binding Updates received by the home agent. 
.1.3.6.1.2.1.184.2,NEMO-MIB::nemoConformance,,,,,,
.1.3.6.1.2.1.184.2.1,NEMO-MIB::nemoGroups,,,,,,
.1.3.6.1.2.1.184.2.1.1,NEMO-MIB::nemoSystemGroup,,,,,,A collection of objects for basic NEMO monitoring. 
.1.3.6.1.2.1.184.2.1.2,NEMO-MIB::nemoBindingCacheGroup,,,,,,A collection of objects for monitoring the NEMO extensions of the Binding Cache. 
.1.3.6.1.2.1.184.2.1.3,NEMO-MIB::nemoStatsGroup,,,,,,A collection of objects for monitoring NEMO statistics. 
.1.3.6.1.2.1.184.2.1.4,NEMO-MIB::nemoMrConfGroup,,,,,,A collection of objects for monitoring the configuration-related information on the mobile router. 
.1.3.6.1.2.1.184.2.1.5,NEMO-MIB::nemoMrRegistrationGroup,,,,,,A collection of objects for monitoring the registration details and statistics for the mobile router. 
.1.3.6.1.2.1.184.2.1.6,NEMO-MIB::nemoHaSystemGroup,,,,,,A collection of objects for basic NEMO configuration monitoring at the home agent. 
.1.3.6.1.2.1.184.2.1.7,NEMO-MIB::nemoHaStatsGroup,,,,,,A collection of objects for monitoring NEMO registration-related statistics pertaining to the mobile routers registered with the home agent. 
.1.3.6.1.2.1.184.2.1.8,NEMO-MIB::nemoHaGlobalStatsGroup,,,,,,A collection of objects for monitoring basic NEMO advertisement and registration statistics on a home agent. 
.1.3.6.1.2.1.184.2.1.9,NEMO-MIB::nemoNotificationGroup,,,,,,A collection of notifications from a home agent or correspondent node to the manager about the tunnel status of the mobile router. 
.1.3.6.1.2.1.184.2.2,NEMO-MIB::nemoCompliances,,,,,,
.1.3.6.1.2.1.184.2.2.1,NEMO-MIB::nemoCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB. 
.1.3.6.1.2.1.184.2.2.2,NEMO-MIB::nemoCompliance2,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB and support monitoring of the Binding Cache. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.184.2.2.3,NEMO-MIB::nemoCoreReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB without support for read-write (i.e., in read-only mode). 
.1.3.6.1.2.1.184.2.2.4,NEMO-MIB::nemoReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB without support for read-write (i.e., in read-only mode) and with support for monitoring of the Binding Cache. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.184.2.2.5,NEMO-MIB::nemoMrCompliance,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB for monitoring configuration- related information, registration details, and statistics on a mobile router. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. 
.1.3.6.1.2.1.184.2.2.6,NEMO-MIB::nemoMrReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB without support for read- write (i.e., in read-only mode) and with support for monitoring of configuration-related information, registration details, and statistics on a mobile router. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6MnHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnHomeAddress -- object. -- -- OBJECT mip6MnBLNodeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. -- -- OBJECT mip6MnBLNodeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6MnBLNodeAddress -- object. 
.1.3.6.1.2.1.184.2.2.7,NEMO-MIB::nemoHaCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB for configuration monitoring at the home agent. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.184.2.2.8,NEMO-MIB::nemoHaCompliance2,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB with support for monitoring of the home agent functionality, specifically the home-agent-registration-related statistics. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT-clause form in this description: -- OBJECT mip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- -- OBJECT mip6BindingHomeAddress -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the mip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.184.2.2.9,NEMO-MIB::nemoNotificationCompliance,,,,,,The compliance statement for SNMP entities that implement the NEMO-MIB and support Notification from the home agent. 
.1.3.6.1.2.1.185,MGMD-STD-MIB::mgmdStdMIB,,,,,,The MIB module for MGMD management. A new version of MGMD combining RFC 2933 and RFC 3019. Includes IGMPv3 and MLDv2 source filtering changes. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5519; see the RFC itself for full legal notices.
.1.3.6.1.2.1.185.1,MGMD-STD-MIB::mgmdMIBObjects,,,,,,
.1.3.6.1.2.1.185.1.1,MGMD-STD-MIB::mgmdHostInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the interfaces on which IGMP or MLD is enabled.
.1.3.6.1.2.1.185.1.1.1,MGMD-STD-MIB::mgmdHostInterfaceEntry,,not-accessible,mgmdHostInterfaceIfIndex:mgmdHostInterfaceQuerierType,current,,An entry (conceptual row) representing an interface on which IGMP or MLD is enabled.
.1.3.6.1.2.1.185.1.1.1.1,MGMD-STD-MIB::mgmdHostInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for which IGMP or MLD is enabled. The table is indexed by the ifIndex value and the InetAddressType to allow for interfaces that may be configured in both IPv4 and IPv6 modes.
.1.3.6.1.2.1.185.1.1.1.2,MGMD-STD-MIB::mgmdHostInterfaceQuerierType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of this interface. This entry along with the ifIndex value acts as an index to the mgmdHostInterface table. A physical interface may be configured in multiple modes concurrently, e.g., in IPv4 and IPv6 modes connected to the same interface; however, the traffic is considered to be logically separate.
.1.3.6.1.2.1.185.1.1.1.3,MGMD-STD-MIB::mgmdHostInterfaceQuerier,OCTET,read-only,,current,,The address of the IGMP or MLD Querier on the IP subnet to which this interface is attached. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdHostInterfaceQuerierType variable in the mgmdHostInterface table.
.1.3.6.1.2.1.185.1.1.1.4,MGMD-STD-MIB::mgmdHostInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The activation of a row enables the host side of IGMP or MLD on the interface. The destruction of a row disables the host side of IGMP or MLD on the interface.
.1.3.6.1.2.1.185.1.1.1.5,MGMD-STD-MIB::mgmdHostInterfaceVersion,Unsigned32,read-create,,current,,The maximum version of MGMD that the host can run on this interface. A value of 1 is only applicable for IPv4, and indicates that the host only supports IGMPv1 on the interface. A value of 2 indicates that the host also supports IGMPv2 (for IPv4) or MLDv1 (for IPv6). A value of 3 indicates that the host also supports IGMPv3 (for IPv4) or MLDv2 (for IPv6).
.1.3.6.1.2.1.185.1.1.1.6,MGMD-STD-MIB::mgmdHostInterfaceVersion1QuerierTimer,TimeTicks,read-only,,current,,The time remaining until the host assumes that there are no IGMPv1 routers present on the interface. While this is non-zero, the host will reply to all queries with version 1 membership reports. This variable applies to IGMPv2 or 3 hosts that are forced to run in v1 for compatibility with v1 routers present on the interface. This object may only be present when the corresponding value of mgmdHostInterfaceQuerierType is ipv4.
.1.3.6.1.2.1.185.1.1.1.7,MGMD-STD-MIB::mgmdHostInterfaceVersion2QuerierTimer,TimeTicks,read-only,,current,,The time remaining until the host assumes that there are no MGMDv2 routers present on the interface. While this is non-zero, the host will reply to all queries with version 1 or 2 membership reports. This variable applies to MGMDv3 hosts that are forced to run in v2 for compatibility with v2 hosts or routers present on the interface.
.1.3.6.1.2.1.185.1.1.1.8,MGMD-STD-MIB::mgmdHostInterfaceVersion3Robustness,Unsigned32,read-create,,current,,The robustness variable utilised by an MGMDv3 host in sending state-change reports for multicast routers. To ensure the state-change report is not missed, the host retransmits the state-change report [mgmdHostInterfaceVersion3Robustness - 1] times. The variable must be a non-zero value.
.1.3.6.1.2.1.185.1.2,MGMD-STD-MIB::mgmdRouterInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the interfaces on which IGMP or MLD is enabled.
.1.3.6.1.2.1.185.1.2.1,MGMD-STD-MIB::mgmdRouterInterfaceEntry,,not-accessible,mgmdRouterInterfaceIfIndex:mgmdRouterInterfaceQuerierType,current,,An entry (conceptual row) representing an interface on which IGMP or MLD is enabled.
.1.3.6.1.2.1.185.1.2.1.1,MGMD-STD-MIB::mgmdRouterInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for which IGMP or MLD is enabled. The table is indexed by the ifIndex value and the InetAddressType to allow for interfaces that may be configured in both IPv4 and IPv6 modes.
.1.3.6.1.2.1.185.1.2.1.2,MGMD-STD-MIB::mgmdRouterInterfaceQuerierType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of this interface. This entry along with the ifIndex value acts as the index to the mgmdRouterInterface table. A physical interface may be configured in multiple modes concurrently, e.g., in IPv4 and IPv6 modes connected to the same interface; however, the traffic is considered to be logically separate.
.1.3.6.1.2.1.185.1.2.1.3,MGMD-STD-MIB::mgmdRouterInterfaceQuerier,OCTET,read-only,,current,,The address of the IGMP or MLD Querier on the IP subnet to which this interface is attached. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdRouterInterfaceQuerierType variable in the mgmdRouterInterface table.
.1.3.6.1.2.1.185.1.2.1.4,MGMD-STD-MIB::mgmdRouterInterfaceQueryInterval,Unsigned32,read-create,,current,,The frequency at which IGMP or MLD Host-Query packets are transmitted on this interface.
.1.3.6.1.2.1.185.1.2.1.5,MGMD-STD-MIB::mgmdRouterInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The activation of a row enables the router side of IGMP or MLD on the interface. The destruction of a row disables the router side of IGMP or MLD on the interface.
.1.3.6.1.2.1.185.1.2.1.6,MGMD-STD-MIB::mgmdRouterInterfaceVersion,Unsigned32,read-create,,current,,The version of MGMD that is running on this interface. Value 1 applies to IGMPv1 routers only. Value 2 applies to IGMPv2 and MLDv1 routers, and value 3 applies to IGMPv3 and MLDv2 routers. This object can be used to configure a router capable of running either version. For IGMP and MLD to function correctly, all routers on a LAN must be configured to run the same version on that LAN.
.1.3.6.1.2.1.185.1.2.1.7,MGMD-STD-MIB::mgmdRouterInterfaceQueryMaxResponseTime,Unsigned32,read-create,,current,,The maximum query response interval advertised in MGMDv2 or IGMPv3 queries on this interface.
.1.3.6.1.2.1.185.1.2.1.8,MGMD-STD-MIB::mgmdRouterInterfaceQuerierUpTime,TimeTicks,read-only,,current,,The time since mgmdRouterInterfaceQuerier was last changed.
.1.3.6.1.2.1.185.1.2.1.9,MGMD-STD-MIB::mgmdRouterInterfaceQuerierExpiryTime,TimeTicks,read-only,,current,,The amount of time remaining before the Other Querier Present Timer expires. If the local system is the querier, the value of this object is zero.
.1.3.6.1.2.1.185.1.2.1.10,MGMD-STD-MIB::mgmdRouterInterfaceWrongVersionQueries,Counter32,read-only,,current,,The number of general queries received whose IGMP or MLD version does not match the equivalent mgmdRouterInterfaceVersion, over the lifetime of the row entry. Both IGMP and MLD require that all routers on a LAN be configured to run the same version. Thus, if any general queries are received with the wrong version, this indicates a configuration error.
.1.3.6.1.2.1.185.1.2.1.11,MGMD-STD-MIB::mgmdRouterInterfaceJoins,Counter32,read-only,,current,,The number of times a group membership has been added on this interface, that is, the number of times an entry for this interface has been added to the Cache Table. This object can give an indication of the amount of activity between samples over time.
.1.3.6.1.2.1.185.1.2.1.12,MGMD-STD-MIB::mgmdRouterInterfaceProxyIfIndex,Integer32,read-create,,current,,Some devices implement a form of IGMP or MLD proxying whereby memberships learned on the interface represented by this row cause Host Membership Reports to be sent on the interface whose ifIndex value is given by this object. Such a device would implement the mgmdV2RouterBaseMIBGroup only on its router interfaces (those interfaces with non-zero mgmdRouterInterfaceProxyIfIndex). Typically, the value of this object is 0, indicating that no proxying is being done.
.1.3.6.1.2.1.185.1.2.1.13,MGMD-STD-MIB::mgmdRouterInterfaceGroups,Gauge32,read-only,,current,,The current number of entries for this interface in the mgmdRouterCacheTable.
.1.3.6.1.2.1.185.1.2.1.14,MGMD-STD-MIB::mgmdRouterInterfaceRobustness,Unsigned32,read-create,,current,,The Robustness Variable allows tuning for the expected packet loss on a subnet. If a subnet is expected to be lossy, the Robustness Variable may be increased. IGMP and MLD are robust to (Robustness Variable-1) packet losses.
.1.3.6.1.2.1.185.1.2.1.15,MGMD-STD-MIB::mgmdRouterInterfaceLastMemberQueryInterval,Unsigned32,read-create,,current,,The Last Member Query Interval is the Max Query Response Interval inserted into group-specific queries sent in response to leave group messages, and is also the amount of time between group-specific query messages. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group. The value of this object is irrelevant if mgmdRouterInterfaceVersion is 1.
.1.3.6.1.2.1.185.1.2.1.16,MGMD-STD-MIB::mgmdRouterInterfaceLastMemberQueryCount,Unsigned32,read-only,,current,,Represents the number of group-specific and group-and- source-specific queries sent by the router before it assumes there are no local members.
.1.3.6.1.2.1.185.1.2.1.17,MGMD-STD-MIB::mgmdRouterInterfaceStartupQueryCount,Unsigned32,read-only,,current,,Represents the number of Queries sent out on startup, separated by the Startup Query Interval.
.1.3.6.1.2.1.185.1.2.1.18,MGMD-STD-MIB::mgmdRouterInterfaceStartupQueryInterval,Unsigned32,read-only,,current,,This variable represents the interval between General Queries sent by a Querier on startup.
.1.3.6.1.2.1.185.1.3,MGMD-STD-MIB::mgmdHostCacheTable,,not-accessible,,current,,The (conceptual) table listing the IP multicast groups for which the host is a member on a particular interface.
.1.3.6.1.2.1.185.1.3.1,MGMD-STD-MIB::mgmdHostCacheEntry,,not-accessible,mgmdHostCacheAddressType:mgmdHostCacheAddress:mgmdHostCacheIfIndex,current,,An entry (conceptual row) in the mgmdHostCacheTable.
.1.3.6.1.2.1.185.1.3.1.1,MGMD-STD-MIB::mgmdHostCacheAddressType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of the mgmdHostCacheTable entry. This value applies to both the mgmdHostCacheAddress and the mgmdHostCacheLastReporter entries.
.1.3.6.1.2.1.185.1.3.1.2,MGMD-STD-MIB::mgmdHostCacheAddress,OCTET,not-accessible,,current,,The IP multicast group address for which this entry contains information. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdHostCacheAddressType variable in the mgmdHostCache table.
.1.3.6.1.2.1.185.1.3.1.3,MGMD-STD-MIB::mgmdHostCacheIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information for an IP multicast group address.
.1.3.6.1.2.1.185.1.3.1.4,MGMD-STD-MIB::mgmdHostCacheUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.2.1.185.1.3.1.5,MGMD-STD-MIB::mgmdHostCacheLastReporter,OCTET,read-only,,current,,The IP address of the source of the last membership report received for this IP multicast group address on this interface. If no membership report has been received, this object has a value of 0. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdHostCacheAddressType variable in the mgmdHostCache table.
.1.3.6.1.2.1.185.1.3.1.6,MGMD-STD-MIB::mgmdHostCacheSourceFilterMode,INTEGER,read-only,,current,include(1):exclude(2),The state in which the interface is currently set. The value indicates the relevance of the corresponding source list entries in the mgmdHostSecListTable for MGMDv3 interfaces.
.1.3.6.1.2.1.185.1.4,MGMD-STD-MIB::mgmdRouterCacheTable,,not-accessible,,current,,The (conceptual) table listing the IP multicast groups for which there are members on a particular router interface.
.1.3.6.1.2.1.185.1.4.1,MGMD-STD-MIB::mgmdRouterCacheEntry,,not-accessible,mgmdRouterCacheAddressType:mgmdRouterCacheAddress:mgmdRouterCacheIfIndex,current,,An entry (conceptual row) in the mgmdRouterCacheTable.
.1.3.6.1.2.1.185.1.4.1.1,MGMD-STD-MIB::mgmdRouterCacheAddressType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of the mgmdRouterCacheTable entry. This value applies to both the mgmdRouterCacheAddress and the mgmdRouterCacheLastReporter entries.
.1.3.6.1.2.1.185.1.4.1.2,MGMD-STD-MIB::mgmdRouterCacheAddress,OCTET,not-accessible,,current,,The IP multicast group address for which this entry contains information. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdRouterCacheAddressType variable in the mgmdRouterCache table.
.1.3.6.1.2.1.185.1.4.1.3,MGMD-STD-MIB::mgmdRouterCacheIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information for an IP multicast group address.
.1.3.6.1.2.1.185.1.4.1.4,MGMD-STD-MIB::mgmdRouterCacheLastReporter,OCTET,read-only,,current,,The IP address of the source of the last membership report received for this IP multicast group address on this interface. If no membership report has been received, this object has the value 0. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdRouterCacheAddressType variable in the mgmdRouterCache table.
.1.3.6.1.2.1.185.1.4.1.5,MGMD-STD-MIB::mgmdRouterCacheUpTime,TimeTicks,read-only,,current,,The time elapsed since this entry was created.
.1.3.6.1.2.1.185.1.4.1.6,MGMD-STD-MIB::mgmdRouterCacheExpiryTime,TimeTicks,read-only,,current,,This value represents the time remaining before the Group Membership Interval state expires. The value must always be greater than or equal to 1.
.1.3.6.1.2.1.185.1.4.1.7,MGMD-STD-MIB::mgmdRouterCacheExcludeModeExpiryTimer,TimeTicks,read-only,,current,,This value is applicable only to MGMDv3-compatible nodes and represents the time remaining before the interface EXCLUDE state expires and the interface state transitions to INCLUDE mode. This value can never be greater than mgmdRouterCacheExpiryTime.
.1.3.6.1.2.1.185.1.4.1.8,MGMD-STD-MIB::mgmdRouterCacheVersion1HostTimer,TimeTicks,read-only,,current,,The time remaining until the local router will assume that there are no longer any MGMD version 1 members on the IP subnet attached to this interface. This entry only applies to IGMPv1 hosts, and is not implemented for MLD. Upon hearing any MGMDv1 Membership Report (IGMPv1 only), this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any MGMDv2 Leave messages (IGMPv2 only) for this group that it receives on this interface.
.1.3.6.1.2.1.185.1.4.1.9,MGMD-STD-MIB::mgmdRouterCacheVersion2HostTimer,TimeTicks,read-only,,current,,The time remaining until the local router will assume that there are no longer any MGMD version 2 members on the IP subnet attached to this interface. This entry applies to both IGMP and MLD hosts. Upon hearing any MGMDv2 Membership Report, this value is reset to the group membership timer. Assuming no MGMDv1 hosts have been detected, the local router does not ignore any MGMDv2 Leave messages for this group that it receives on this interface.
.1.3.6.1.2.1.185.1.4.1.10,MGMD-STD-MIB::mgmdRouterCacheSourceFilterMode,INTEGER,read-only,,current,include(1):exclude(2),The current cache state, applicable to MGMDv3-compatible nodes. The value indicates whether the state is INCLUDE or EXCLUDE.
.1.3.6.1.2.1.185.1.5,MGMD-STD-MIB::mgmdInverseHostCacheTable,,not-accessible,,current,,The (conceptual) table listing the interfaces that are members of a particular group. This is an inverse lookup table for entries in the mgmdHostCacheTable.
.1.3.6.1.2.1.185.1.5.1,MGMD-STD-MIB::mgmdInverseHostCacheEntry,,not-accessible,mgmdInverseHostCacheIfIndex:mgmdInverseHostCacheAddressType:mgmdInverseHostCacheAddress,current,,An entry (conceptual row) in the mgmdInverseHostCacheTable.
.1.3.6.1.2.1.185.1.5.1.1,MGMD-STD-MIB::mgmdInverseHostCacheIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information.
.1.3.6.1.2.1.185.1.5.1.2,MGMD-STD-MIB::mgmdInverseHostCacheAddressType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of the mgmdInverseHostCacheTable entry.
.1.3.6.1.2.1.185.1.5.1.3,MGMD-STD-MIB::mgmdInverseHostCacheAddress,OCTET,read-only,,current,,The IP multicast group address for which this entry contains information about an interface. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdInverseHostCacheAddressType variable in the mgmdInverseHostCache table.
.1.3.6.1.2.1.185.1.6,MGMD-STD-MIB::mgmdInverseRouterCacheTable,,not-accessible,,current,,The (conceptual) table listing the interfaces that are members of a particular group. This is an inverse lookup table for entries in the mgmdRouterCacheTable.
.1.3.6.1.2.1.185.1.6.1,MGMD-STD-MIB::mgmdInverseRouterCacheEntry,,not-accessible,mgmdInverseRouterCacheIfIndex:mgmdInverseRouterCacheAddressType:mgmdInverseRouterCacheAddress,current,,An entry (conceptual row) in the mgmdInverseRouterCacheTable.
.1.3.6.1.2.1.185.1.6.1.1,MGMD-STD-MIB::mgmdInverseRouterCacheIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information for an IP multicast group address.
.1.3.6.1.2.1.185.1.6.1.2,MGMD-STD-MIB::mgmdInverseRouterCacheAddressType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of the mgmdInverseRouterCacheTable entry.
.1.3.6.1.2.1.185.1.6.1.3,MGMD-STD-MIB::mgmdInverseRouterCacheAddress,OCTET,read-only,,current,,The IP multicast group address for which this entry contains information. The InetAddressType, e.g., IPv4 or IPv6, is identified by the mgmdInverseRouterCacheAddressType variable in the mgmdInverseRouterCache table.
.1.3.6.1.2.1.185.1.7,MGMD-STD-MIB::mgmdHostSrcListTable,,not-accessible,,current,,The (conceptual) table listing the Source List entries corresponding to each interface and multicast group pair on a host.
.1.3.6.1.2.1.185.1.7.1,MGMD-STD-MIB::mgmdHostSrcListEntry,,not-accessible,mgmdHostSrcListAddressType:mgmdHostSrcListAddress:mgmdHostSrcListIfIndex:mgmdHostSrcListHostAddress,current,,An entry (conceptual row) in the mgmdHostSrcListTable.
.1.3.6.1.2.1.185.1.7.1.1,MGMD-STD-MIB::mgmdHostSrcListAddressType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of the InetAddress variables in this table. This value applies to the mgmdHostSrcListHostAddress and mgmdHostSrcListAddress entries.
.1.3.6.1.2.1.185.1.7.1.2,MGMD-STD-MIB::mgmdHostSrcListAddress,OCTET,not-accessible,,current,,The IP multicast group address for which this entry contains information.
.1.3.6.1.2.1.185.1.7.1.3,MGMD-STD-MIB::mgmdHostSrcListIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information for an IP multicast group address.
.1.3.6.1.2.1.185.1.7.1.4,MGMD-STD-MIB::mgmdHostSrcListHostAddress,OCTET,not-accessible,,current,,The host address to which this entry corresponds. The mgmdHostCacheSourceFilterMode value for this group address and interface indicates whether this host address is included or excluded.
.1.3.6.1.2.1.185.1.7.1.5,MGMD-STD-MIB::mgmdHostSrcListExpire,TimeTicks,read-only,,current,,This value indicates the relevance of the SrcList entry, whereby a non-zero value indicates this is an INCLUDE state value, and a zero value indicates this to be an EXCLUDE state value.
.1.3.6.1.2.1.185.1.8,MGMD-STD-MIB::mgmdRouterSrcListTable,,not-accessible,,current,,The (conceptual) table listing the Source List entries corresponding to each interface and multicast group pair on a Router.
.1.3.6.1.2.1.185.1.8.1,MGMD-STD-MIB::mgmdRouterSrcListEntry,,not-accessible,mgmdRouterSrcListAddressType:mgmdRouterSrcListAddress:mgmdRouterSrcListIfIndex:mgmdRouterSrcListHostAddress,current,,An entry (conceptual row) in the mgmdRouterSrcListTable.
.1.3.6.1.2.1.185.1.8.1.1,MGMD-STD-MIB::mgmdRouterSrcListAddressType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The address type of the InetAddress variables in this table. This value applies to the mgmdRouterSrcListHostAddress and mgmdRouterSrcListAddress entries.
.1.3.6.1.2.1.185.1.8.1.2,MGMD-STD-MIB::mgmdRouterSrcListAddress,OCTET,not-accessible,,current,,The IP multicast group address for which this entry contains information.
.1.3.6.1.2.1.185.1.8.1.3,MGMD-STD-MIB::mgmdRouterSrcListIfIndex,Integer32,not-accessible,,current,,The interface for which this entry contains information for an IP multicast group address.
.1.3.6.1.2.1.185.1.8.1.4,MGMD-STD-MIB::mgmdRouterSrcListHostAddress,OCTET,not-accessible,,current,,The host address to which this entry corresponds. The mgmdRouterCacheSourceFilterMode value for this group address and interface indicates whether this host address is included or excluded.
.1.3.6.1.2.1.185.1.8.1.5,MGMD-STD-MIB::mgmdRouterSrcListExpire,TimeTicks,read-only,,current,,This value indicates the relevance of the SrcList entry, whereby a non-zero value indicates this is an INCLUDE state value, and a zero value indicates this to be an EXCLUDE state value.
.1.3.6.1.2.1.185.2,MGMD-STD-MIB::mgmdMIBConformance,,,,,,
.1.3.6.1.2.1.185.2.1,MGMD-STD-MIB::mgmdMIBCompliance,,,,,,
.1.3.6.1.2.1.185.2.1.1,MGMD-STD-MIB::mgmdIgmpV1HostReadMIBCompliance,,,,,,A read-only compliance statement for hosts running IGMPv1 [RFC1112] and implementing the MGMD MIB. IGMPv1 hosts must support the IPv4 address type.
.1.3.6.1.2.1.185.2.1.2,MGMD-STD-MIB::mgmdIgmpV1RouterReadMIBCompliance,InetAddressType,,,,ipv4(1),A read-only compliance statement for routers running IGMPv1 [RFC1112] and implementing the MGMD MIB. IGMPv1 routers only support the IPv4 address type. Non-accessible index objects that only need IPv4 support are: OBJECT mgmdRouterCacheAddressType OBJECT mgmdRouterCacheAddress OBJECT mgmdRouterInterfaceQuerierType OBJECT mgmdInverseRouterCacheAddressType 
.1.3.6.1.2.1.185.2.1.3,MGMD-STD-MIB::mgmdIgmpV1RouterWriteMIBCompliance,InetAddressType,,,,ipv4(1),A read-create compliance statement for routers running IGMPv1 [RFC1112] and implementing the MGMD MIB. IGMPv1 routers only support the IPv4 address type. Non-accessible index objects that only need IPv4 support are: OBJECT mgmdRouterCacheAddressType OBJECT mgmdRouterCacheAddress OBJECT mgmdRouterInterfaceQuerierType OBJECT mgmdInverseRouterCacheAddressType 
.1.3.6.1.2.1.185.2.1.4,MGMD-STD-MIB::mgmdIgmpV2MldV1HostReadMIBCompliance,,,,,,A read-only compliance statement for hosts running IGMPv2 [RFC2236] or MLDv1 [RFC2710] and implementing the MGMD MIB. IGMPv2 hosts only support the IPv4 address type and MLDv1 hosts only support the IPv6 address type.
.1.3.6.1.2.1.185.2.1.5,MGMD-STD-MIB::mgmdIgmpV2MldV1HostWriteMIBCompliance,,,,,,A read-create compliance statement for hosts running IGMPv2 [RFC2236] or MLDv1 [RFC2710] and implementing the MGMD MIB. IGMPv2 hosts only support the IPv4 address type and MLDv1 hosts only support the IPv6 address type.
.1.3.6.1.2.1.185.2.1.6,MGMD-STD-MIB::mgmdIgmpV2MldV1RouterReadMIBCompliance,,,,,,A read-only compliance statement for routers running IGMPv2 [RFC2236] or MLDv1 [RFC2710] and implementing the MGMD MIB. IGMPv2 routers only support the IPv4 address type and MLDv1 routers only support the IPv6 address type.
.1.3.6.1.2.1.185.2.1.7,MGMD-STD-MIB::mgmdIgmpV2V3MldV1V2RouterWriteMIBCompliance,,,,,,A read-create compliance statement for routers running IGMPv2 [RFC2236], IGMPv3 [RFC3376], MLDv1 [RFC2710], or MLDv2 [RFC3810] and implementing the MGMD MIB. IGMPv2 and IGMPv3 routers only support the IPv4 address type, while MLDv1 and MLDv2 routers only support the IPv6 address type.
.1.3.6.1.2.1.185.2.1.8,MGMD-STD-MIB::mgmdIgmpV3MldV2HostReadMIBCompliance,,,,,,The compliance statement for hosts running IGMPv3 [RFC3376] or MLDv2 [RFC3810] and implementing the MGMD MIB. IGMPv3 hosts only support the IPv4 address type and MLDv2 hosts only support the IPv6 address type.
.1.3.6.1.2.1.185.2.1.9,MGMD-STD-MIB::mgmdIgmpV3MldV2HostWriteMIBCompliance,,,,,,The compliance statement for hosts running IGMPv3 [RFC3376] or MLDv2 [RFC3810] and implementing the MGMD MIB. IGMPv3 hosts only support the IPv4 address type and MLDv2 hosts only support the IPv6 address type.
.1.3.6.1.2.1.185.2.1.10,MGMD-STD-MIB::mgmdIgmpV3MldV2RouterReadMIBCompliance,,,,,,A read-only compliance statement for routers running IGMPv3 [RFC3376] or MLDv2 [RFC3810] and implementing the MGMD MIB. IGMPv3 routers only support the IPv4 address type and MLDv2 routers only support the IPv6 address type.
.1.3.6.1.2.1.185.2.2,MGMD-STD-MIB::mgmdMIBGroups,,,,,,
.1.3.6.1.2.1.185.2.2.1,MGMD-STD-MIB::mgmdHostBaseMIBGroup,,,,,,The basic collection of objects providing management of MGMD version 1, 2, or 3 for hosts.
.1.3.6.1.2.1.185.2.2.2,MGMD-STD-MIB::mgmdRouterBaseMIBGroup,,,,,,The basic collection of objects providing management of MGMD version 1, 2, or 3 for routers.
.1.3.6.1.2.1.185.2.2.3,MGMD-STD-MIB::mgmdV2HostMIBGroup,,,,,,A collection of additional read-only objects for management of IGMP version 2 in hosts for MGMD version 2 compliance.
.1.3.6.1.2.1.185.2.2.4,MGMD-STD-MIB::mgmdHostExtendedMIBGroup,,,,,,A collection of optional objects for MGMD hosts.
.1.3.6.1.2.1.185.2.2.5,MGMD-STD-MIB::mgmdV2RouterBaseMIBGroup,,,,,,A collection of additional read-only objects for management of MGMD version 2 in routers.
.1.3.6.1.2.1.185.2.2.6,MGMD-STD-MIB::mgmdV2ProxyMIBGroup,,,,,,A collection of additional read-create objects for management of MGMD proxy devices.
.1.3.6.1.2.1.185.2.2.7,MGMD-STD-MIB::mgmdV3HostMIBGroup,,,,,,A collection of additional objects for management of MGMD version 3 in hosts.
.1.3.6.1.2.1.185.2.2.8,MGMD-STD-MIB::mgmdV3RouterMIBGroup,,,,,,A collection of additional read-only objects for management of MGMD version 3 in routers.
.1.3.6.1.2.1.186,PW-TDM-MIB::pwTDMMIB,,,,,,This MIB contains managed object definitions for encapsulating TDM (T1,E1, T3, E3, NxDS0) as pseudo-wires over packet-switching networks (PSN). This MIB supplements the PW-STD-MIB as in: Zelig, D., Nadeau, T. 'Pseudowire (PW) Management Information Base'. The PW-STD-MIB contains structures and MIB associations generic to pseudowire (PW) emulation. PW-specific MIBs (such as this) contain config and stats for specific PW types. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5604; see the RFC itself for full legal notices. 
.1.3.6.1.2.1.186.0,PW-TDM-MIB::pwTDMNotifications,,,,,,
.1.3.6.1.2.1.186.1,PW-TDM-MIB::pwTDMObjects,,,,,,
.1.3.6.1.2.1.186.1.1,PW-TDM-MIB::pwTDMTable,,not-accessible,,current,,This table contains basic information including the ifIndex and pointers to entries in the relevant TDM config tables for this TDM PW.
.1.3.6.1.2.1.186.1.1.1,PW-TDM-MIB::pwTDMEntry,,not-accessible,pwIndex,current,,This table is indexed by the same index that was created for the associated entry in the PW Table (in the PW-STD-MIB). - The PwIndex. An entry is created in this table by the agent for every entry in the pwTable with a pwType equal to one of the following: e1Satop(17), t1Satop(18), e3Satop(19), t3Satop(20), basicCesPsn(21), basicTdmIp(22), tdmCasCesPsn(23), or tdmCasTdmIp(24). Unless otherwise specified, all writeable objects in this table MUST NOT be changed after row activation in the generic pwTable (see [PWMIB]) and values must persist after reboot.
.1.3.6.1.2.1.186.1.1.1.1,PW-TDM-MIB::pwTDMRate,Integer32,read-write,,current,,The parameter represents the bit-rate of the TDM service in multiples of the 'basic' 64 Kbit/s rate [TDMCP-EXT]. It complements the definition of pwType used in PW-STD-MIB. For structure-agnostic mode, the following should be used: a) (Structure-Agnostic TDM over Packet) Satop E1 - 32 b) Satop T1 emulation: i) MUST be set to 24 in the basic emulation mode ii) MUST be set to 25 for the 'Octet-aligned T1' emulation mode c) Satop E3 - 535 d) Satop T3 - 699 For all kinds of structure-aware emulation, this parameter MUST be set to N where N is the number of DS0 channels in the corresponding attachment circuit.
.1.3.6.1.2.1.186.1.1.1.2,PW-TDM-MIB::pwTDMIfIndex,Integer32,read-write,,current,,This is a unique index within the ifTable. It represents the interface index of the full link or the interface index for the bundle holding the group of time slots to be transmitted via this PW connection. A value of zero indicates an interface index that has yet to be determined. Once set, if the TDM ifIndex is (for some reason) later removed, the agent SHOULD delete the associated PW rows (e.g., this pwTDMTable entry). If the agent does not delete the rows, the agent MUST set this object to zero.
.1.3.6.1.2.1.186.1.1.1.3,PW-TDM-MIB::pwGenTDMCfgIndex,Unsigned32,read-write,,current,,Index to the generic parameters in the TDM configuration table that appears in this MIB module. It is likely that multiple TDM PWs of the same characteristic will share a single TDM Cfg entry.
.1.3.6.1.2.1.186.1.1.1.4,PW-TDM-MIB::pwRelTDMCfgIndex,Unsigned32,read-write,,current,,Index to the relevant TDM configuration table entry that appears in one of the related MIB modules such as TDMoIP or CESoPSN. It is likely that multiple TDM PWs of the same characteristic will share a single configuration entry of the relevant type. The value 0 implies no entry in other related MIBs.
.1.3.6.1.2.1.186.1.1.1.5,PW-TDM-MIB::pwTDMConfigError,BITS,read-only,,current,notApplicable(0):tdmTypeIncompatible(1):peerRtpIncompatible(2):peerPayloadSizeIncompatible(3),Any of the bits are set if the local configuration is not compatible with the peer configuration as available from the various parameters options. Setting is done based on signaling, or else value (0) will be set. -tdmTypeIncompatible bit is set if the local configuration is not carrying the same TDM type as the peer configuration. -peerRtpIncompatible bit is set if the local configuration is configured to send RTP packets for this PW, and the remote is not capable of accepting RTP packets. -peerPayloadSizeIncompatible bit is set if the local configuration is not carrying the same Payload Size as the peer configuration.
.1.3.6.1.2.1.186.1.1.1.6,PW-TDM-MIB::pwTDMTimeElapsed,Integer32,read-only,,current,,The number of seconds, including partial seconds, that have elapsed since the beginning of the current measurement period. If, for some reason, such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.186.1.1.1.7,PW-TDM-MIB::pwTDMValidIntervals,Integer32,read-only,,current,,The number of previous 15-minute intervals for which data was collected. An agent with TDM capability must be capable of supporting at least n intervals. The minimum value of n is 4. The default of n is 32 and the maximum value of n is 96. The value will be n unless the measurement was (re-) started within the last (n*15) minutes, in which case, the value will be the number of complete 15-minute intervals for which the agent has at least some data. In certain cases (e.g., in the case where the agent is a proxy), it is possible that some intervals are unavailable. In this case, this interval is the maximum interval number for which data is available.
.1.3.6.1.2.1.186.1.1.1.8,PW-TDM-MIB::pwTDMValidDayIntervals,Integer32,read-only,,current,,The number of previous days for which data was collected. An agent with TDM capability must be capable of supporting at least n intervals. The minimum value of n is 1. The default of n is 1 and the maximum value of n is 30.
.1.3.6.1.2.1.186.1.1.1.11,PW-TDM-MIB::pwTDMLastEsTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent occasion at which the TDM PW entered the ES or SES state.
.1.3.6.1.2.1.186.1.2,PW-TDM-MIB::pwTDMCfgIndexNext,Unsigned32,read-only,,current,,This object contains the value to be used for pwTDMCfgIndex when creating entries in the pwTDMCfgTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwTDMCfgIndexNext for a new entry in the pwTDMCfgTable, the manager issues a management protocol retrieval operation. The agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.186.1.3,PW-TDM-MIB::pwTDMCfgTable,,not-accessible,,current,,This table contains a set of parameters that may be referenced by one or more TDM PWs in pwTDMTable.
.1.3.6.1.2.1.186.1.3.1,PW-TDM-MIB::pwTDMCfgEntry,,not-accessible,pwTDMCfgIndex,current,,These parameters define the characteristics of a TDM PW. They are grouped here to ease NMS burden. Once an entry is created here it may be re-used by many PWs. Unless otherwise specified, all objects in this table MUST NOT be changed after row activation (see [PWMIB]).
.1.3.6.1.2.1.186.1.3.1.1,PW-TDM-MIB::pwTDMCfgIndex,Unsigned32,not-accessible,,current,,Index to an entry in this table. When an NMS creates a new entry/row in this table, it best makes use of the value of the pwTDMCfgIndexNext object in order to find a free or available index value.
.1.3.6.1.2.1.186.1.3.1.2,PW-TDM-MIB::pwTDMCfgRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Object used for creating, modifying, and deleting a row from this table. The following objects cannot be modified if the entry is in use and the status is active: pwTDMCfgPayloadSize, pwTDMCfgRtpHdrUsed, pwTDMCfgJtrBfrDepth, and pwTDMCfgPayloadSuppression. The row cannot be deleted if the entry is in use.
.1.3.6.1.2.1.186.1.3.1.4,PW-TDM-MIB::pwTDMCfgPayloadSize,Unsigned32,read-create,,current,,The value of this object indicates the PayLoad Size (in bytes) to be defined during the PW setUp. Upon TX, implementation must be capable of carrying that amount of bytes. Upon RX, when the Low Entry Networking (LEN) field is set to 0, the payload of packet MUST assume this size, and if the actual packet size is inconsistent with this length, the packet MUST be considered to be malformed.
.1.3.6.1.2.1.186.1.3.1.5,PW-TDM-MIB::pwTDMCfgPktReorder,INTEGER,read-create,,current,true(1):false(2),If set to True: as CE-bound packets are queued in the jitter buffer, out of order packets are re-ordered. The maximum sequence number differential (i.e., the range in which re-sequencing can occur) is dependant on the depth of the jitter buffer. See pwTDMCfgJtrBfrDepth. NOTE: Some implementations may not support this feature. The agent should then reject a SET request for true.
.1.3.6.1.2.1.186.1.3.1.6,PW-TDM-MIB::pwTDMCfgRtpHdrUsed,INTEGER,read-create,,current,true(1):false(2),If set to False: an RTP header is not pre-pended to the TDM packet.
.1.3.6.1.2.1.186.1.3.1.7,PW-TDM-MIB::pwTDMCfgJtrBfrDepth,Unsigned32,read-create,,current,,The size of this buffer SHOULD be locally configured to allow accommodation to the PSN-specific packet delay variation. If configured to a value not supported by the implementation, the agent MUST return an error code 'jtrBfrDepth' in 'pwTDMConfigError'. NOTE: jitter buffers are a limited resource to be managed. The actual size should be at least twice as big as the value of pwTDMCfgJtrBfrDepth.
.1.3.6.1.2.1.186.1.3.1.8,PW-TDM-MIB::pwTDMCfgPayloadSuppression,INTEGER,read-create,,current,enable(1):disable(2),Selecting 'enable' means: Payload suppression is allowed. Payload MAY be omitted in order to conserve bandwidth. Selecting 'disable' means: No suppression under any condition. Object MAY be changed at any time.
.1.3.6.1.2.1.186.1.3.1.9,PW-TDM-MIB::pwTDMCfgConsecPktsInSynch,Unsigned32,read-create,,current,,The number of consecutive packets with sequential sequence numbers that are required to exit the LOPS. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.10,PW-TDM-MIB::pwTDMCfgConsecMissPktsOutSynch,Unsigned32,read-create,,current,,The number of consecutive missing packets that are required to enter the LOPS. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.11,PW-TDM-MIB::pwTDMCfgSetUp2SynchTimeOut,Unsigned32,read-create,,current,,The amount of time the host should wait before declaring the pseudowire in a down state, if the number of consecutive TDM packets that have been received after changing the administrative status to up and after finalization of signaling (if supported) between the two PEs is smaller than pwTDMCfgConsecPktsInSynch. Once the PW has OperStatus of 'up', this parameter is no longer valid. This parameter is defined to ensure that the host does not prematurely inform failure of the PW. In particular, PW 'down' notifications should not be sent before expiration of this timer. This parameter is valid only after administrative changes of the status of the PW. If the PW fails due to network impairments, a 'down' notification should be sent. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.12,PW-TDM-MIB::pwTDMCfgPktReplacePolicy,INTEGER,read-create,,current,allOnes(1):implementationSpecific(2):filler(3),This parameter determines the value to be played when CE bound packets over/underflow the jitter buffer, or are missing for any reason. This byte pattern is sent (played) on the TDM line. Selecting implementationSpecific(2) implies an agent-specific algorithm. Selecting filler(3) requires the setting of pwTDMCfgPktFiller. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.13,PW-TDM-MIB::pwTDMCfgAvePktLossTimeWindow,Integer32,read-create,,current,,The length of time over which the average packet loss rate should be computed to detect excessive packet loss rate. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.14,PW-TDM-MIB::pwTDMCfgExcessivePktLossThreshold,Unsigned32,read-create,,current,,Excessive packet loss rate is detected by computing the average packet-loss rate over a pwTDMCfgAvePktLossTimeWindow amount of time and comparing it with this threshold value. The rate is expressed in percentage. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.15,PW-TDM-MIB::pwTDMCfgAlarmThreshold,Unsigned32,read-create,,current,,Alarms are only reported when the defect state persists for the length of time specified by this object. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.16,PW-TDM-MIB::pwTDMCfgClearAlarmThreshold,Unsigned32,read-create,,current,,Alarm MUST be cleared after the corresponding defect is undetected for the amount of time specified by this object. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.17,PW-TDM-MIB::pwTDMCfgMissingPktsToSes,Unsigned32,read-create,,current,,Percent of missing packets detected (consecutive or not) within a 1-second window to cause a Severely Error Second (SES) to be counted. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.18,PW-TDM-MIB::pwTDMCfgTimestampMode,INTEGER,read-create,,current,notApplicable(1):absolute(2):differential(3),Timestamp generation MAY be used in one of the following modes: 1. Absolute mode: The PSN-bound IWF sets timestamps using the clock recovered from the incoming TDM attachment circuit. As a consequence, the timestamps are closely correlated with the sequence numbers. All TDM implementations that support usage of the RTP header MUST support this mode. 2. Differential mode: Both IWFs have access to a common high- quality timing source, and this source is used for timestamp generation. Support of this mode is OPTIONAL. Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.19,PW-TDM-MIB::pwTDMCfgStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row. Conceptual rows having the value permanent(4) must allow write-access to all columnar objects.
.1.3.6.1.2.1.186.1.3.1.20,PW-TDM-MIB::pwTDMCfgPktFiller,Unsigned32,read-create,,current,,Filler byte pattern played out on the TDM interface if pwTDMCfgPktReplacePolicy was set to filler(3). Object MAY be changed only when the related PW is defined as not active.
.1.3.6.1.2.1.186.1.3.1.21,PW-TDM-MIB::pwTDMCfgName,OCTET,read-create,,current,,A descriptive string, preferably a unique name, to an entry in this table. Object MAY be changed at any time.
.1.3.6.1.2.1.186.1.5,PW-TDM-MIB::pwTDMPerfCurrentTable,,not-accessible,,current,,The current 15-minute interval counts are in this table. This table provides per TDM PW performance information.
.1.3.6.1.2.1.186.1.5.1,PW-TDM-MIB::pwTDMPerfCurrentEntry,,not-accessible,pwIndex,current,,An entry in this table is created by the agent for every pwTDMTable entry. After 15 minutes, the contents of this table entry are copied to a new entry in the pwTDMPerfInterval table, and the counts in this entry are reset to zero.
.1.3.6.1.2.1.186.1.5.1.1,PW-TDM-MIB::pwTDMPerfCurrentMissingPkts,Gauge32,read-only,,current,,Number of missing packets (as detected via control word sequence number gaps).
.1.3.6.1.2.1.186.1.5.1.2,PW-TDM-MIB::pwTDMPerfCurrentPktsReOrder,Gauge32,read-only,,current,,Number of packets detected out of sequence (via control word sequence number) but successfully re-ordered. Note: some implementations may not support this feature.
.1.3.6.1.2.1.186.1.5.1.3,PW-TDM-MIB::pwTDMPerfCurrentJtrBfrUnderruns,Gauge32,read-only,,current,,Number of times a packet needed to be played out and the jitter buffer was empty.
.1.3.6.1.2.1.186.1.5.1.4,PW-TDM-MIB::pwTDMPerfCurrentMisOrderDropped,Gauge32,read-only,,current,,Number of packets detected out of order (via control word sequence numbers) that could not be re-ordered or could not fit in the jitter buffer.
.1.3.6.1.2.1.186.1.5.1.5,PW-TDM-MIB::pwTDMPerfCurrentMalformedPkt,Gauge32,read-only,,current,,Number of packets detected with unexpected size or bad headers' stack.
.1.3.6.1.2.1.186.1.5.1.6,PW-TDM-MIB::pwTDMPerfCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Error Seconds encountered. Any malformed packet, sequence error, LOPS, and the like are considered as Error Seconds.
.1.3.6.1.2.1.186.1.5.1.7,PW-TDM-MIB::pwTDMPerfCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Error Seconds encountered.
.1.3.6.1.2.1.186.1.5.1.8,PW-TDM-MIB::pwTDMPerfCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered. Any consecutive ten seconds of SES are counted as one Unavailable Seconds (UAS).
.1.3.6.1.2.1.186.1.5.1.9,PW-TDM-MIB::pwTDMPerfCurrentFC,Gauge32,read-only,,current,,TDM Failure Counts (FC-TDM). The number of TDM failure events. A failure event begins when the LOPS failure is declared, and it ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.
.1.3.6.1.2.1.186.1.6,PW-TDM-MIB::pwTDMPerfIntervalTable,,not-accessible,,current,,This table provides performance information per TDM PW similar to the pwTDMPerfCurrentTable above. However, these counts represent historical 15-minute intervals. Typically, this table will have a maximum of 96 entries for a 24 hour period, but is not limited to this.
.1.3.6.1.2.1.186.1.6.1,PW-TDM-MIB::pwTDMPerfIntervalEntry,,not-accessible,pwIndex:pwTDMPerfIntervalNumber,current,,An entry in this table is created by the agent for every pwTDMPerfCurrentEntry that is 15 minutes old. The contents of the Current entry are copied to the new entry here. The Current entry then resets its counts to zero for the next current 15-minute interval.
.1.3.6.1.2.1.186.1.6.1.1,PW-TDM-MIB::pwTDMPerfIntervalNumber,Unsigned32,not-accessible,,current,,A number (normally between 1 and 96 to cover a 24 hour period) that identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15-minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1. The minimum range of N is 1 through 4. The default range is 1 through 32. The maximum value of N is 1 through 96.
.1.3.6.1.2.1.186.1.6.1.2,PW-TDM-MIB::pwTDMPerfIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.186.1.6.1.3,PW-TDM-MIB::pwTDMPerfIntervalDuration,Unsigned32,read-only,,current,,The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
.1.3.6.1.2.1.186.1.6.1.4,PW-TDM-MIB::pwTDMPerfIntervalMissingPkts,Gauge32,read-only,,current,,Number of missing packets (as detected via control word sequence number gaps).
.1.3.6.1.2.1.186.1.6.1.5,PW-TDM-MIB::pwTDMPerfIntervalPktsReOrder,Gauge32,read-only,,current,,Number of packets detected out of sequence (via control word sequence number) but successfully re-ordered. Note: some implementations may not support this feature.
.1.3.6.1.2.1.186.1.6.1.6,PW-TDM-MIB::pwTDMPerfIntervalJtrBfrUnderruns,Gauge32,read-only,,current,,Number of times a packet needed to be played out and the jitter buffer was empty.
.1.3.6.1.2.1.186.1.6.1.7,PW-TDM-MIB::pwTDMPerfIntervalMisOrderDropped,Gauge32,read-only,,current,,Number of packets detected out of order (via control word sequence numbers) that could not be re-ordered or could not fit in the jitter buffer.
.1.3.6.1.2.1.186.1.6.1.8,PW-TDM-MIB::pwTDMPerfIntervalMalformedPkt,Gauge32,read-only,,current,,Number of packets detected with unexpected size, or bad headers' stack
.1.3.6.1.2.1.186.1.6.1.9,PW-TDM-MIB::pwTDMPerfIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Error Seconds encountered.
.1.3.6.1.2.1.186.1.6.1.10,PW-TDM-MIB::pwTDMPerfIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Error Seconds encountered.
.1.3.6.1.2.1.186.1.6.1.11,PW-TDM-MIB::pwTDMPerfIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered.
.1.3.6.1.2.1.186.1.6.1.12,PW-TDM-MIB::pwTDMPerfIntervalFC,Gauge32,read-only,,current,,TDM Failure Counts (FC-TDM). The number of TDM failure events. A failure event begins when the LOPS failure is declared, and it ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.
.1.3.6.1.2.1.186.1.7,PW-TDM-MIB::pwTDMPerf1DayIntervalTable,,not-accessible,,current,,This table provides performance information per TDM PW similar to the pwTDMPerfIntervalTable above. However, these counters represent historical one-day intervals up to one full month. The table consists of real-time data, as such it is not persistence across re-boot.
.1.3.6.1.2.1.186.1.7.1,PW-TDM-MIB::pwTDMPerf1DayIntervalEntry,,not-accessible,pwIndex:pwTDMPerf1DayIntervalNumber,current,,An entry is created in this table by the agent for every entry in the pwTDMTable table.
.1.3.6.1.2.1.186.1.7.1.1,PW-TDM-MIB::pwTDMPerf1DayIntervalNumber,Unsigned32,not-accessible,,current,,The number of intervals where 1 indicates the current day measured period and 2 and above indicate previous days, respectively.
.1.3.6.1.2.1.186.1.7.1.2,PW-TDM-MIB::pwTDMPerf1DayIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.186.1.7.1.3,PW-TDM-MIB::pwTDMPerf1DayIntervalDuration,Unsigned32,read-only,,current,,The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
.1.3.6.1.2.1.186.1.7.1.4,PW-TDM-MIB::pwTDMPerf1DayIntervalMissingPkts,Counter32,read-only,,current,,Number of missing packets (as detected via control word sequence number gaps).
.1.3.6.1.2.1.186.1.7.1.5,PW-TDM-MIB::pwTDMPerf1DayIntervalPktsReOrder,Counter32,read-only,,current,,Number of packets detected out of sequence (via control word sequence number) but successfully re-ordered. Note: some implementations may not support this feature.
.1.3.6.1.2.1.186.1.7.1.6,PW-TDM-MIB::pwTDMPerf1DayIntervalJtrBfrUnderruns,Counter32,read-only,,current,,Number of times a packet needed to be played out and the jitter buffer was empty.
.1.3.6.1.2.1.186.1.7.1.7,PW-TDM-MIB::pwTDMPerf1DayIntervalMisOrderDropped,Counter32,read-only,,current,,Number of packets detected out of order (via control word sequence numbers) that could not be re-ordered or could not fit in the jitter buffer.
.1.3.6.1.2.1.186.1.7.1.8,PW-TDM-MIB::pwTDMPerf1DayIntervalMalformedPkt,Counter32,read-only,,current,,Number of packets detected with unexpected size or bad headers' stack.
.1.3.6.1.2.1.186.1.7.1.9,PW-TDM-MIB::pwTDMPerf1DayIntervalESs,Counter32,read-only,,current,,The counter associated with the number of Error Seconds encountered.
.1.3.6.1.2.1.186.1.7.1.10,PW-TDM-MIB::pwTDMPerf1DayIntervalSESs,Counter32,read-only,,current,,The counter associated with the number of Severely Error Seconds.
.1.3.6.1.2.1.186.1.7.1.11,PW-TDM-MIB::pwTDMPerf1DayIntervalUASs,Counter32,read-only,,current,,The counter associated with the number of UnAvailable Seconds. NOTE: When first entering the UAS state, the number of SES to UAS is added to this object, then as each additional UAS occurs, this object increments by one.
.1.3.6.1.2.1.186.1.7.1.12,PW-TDM-MIB::pwTDMPerf1DayIntervalFC,Counter32,read-only,,current,,TDM Failure Counts (FC-TDM). The number of TDM failure events. A failure event begins when the LOPS failure is declared, and it ends when the failure is cleared.
.1.3.6.1.2.1.186.2,PW-TDM-MIB::pwTDMConformance,,,,,,
.1.3.6.1.2.1.186.2.1,PW-TDM-MIB::pwTDMCompliances,,,,,,
.1.3.6.1.2.1.186.2.1.1,PW-TDM-MIB::pwTDMModuleCompliance,,,,,,The compliance statement for agent that support TDM PW over PSN operation.
.1.3.6.1.2.1.186.2.2,PW-TDM-MIB::pwTDMGroups,,,,,,
.1.3.6.1.2.1.186.2.2.1,PW-TDM-MIB::pwTDMGroup,,,,,,Collection of objects for basic TDM PW config and status.
.1.3.6.1.2.1.186.2.2.2,PW-TDM-MIB::pwTDMPerfCurrentGroup,,,,,,Collection of current statistics objects for TDM PWs.
.1.3.6.1.2.1.186.2.2.3,PW-TDM-MIB::pwTDMPerfIntervalGroup,,,,,,Collection of Interval statistics objects for TDM PWs.
.1.3.6.1.2.1.186.2.2.4,PW-TDM-MIB::pwTDMPerf1DayIntervalGroup,,,,,,Collection of Daily statistics objects for TDM PWs.
.1.3.6.1.2.1.187,FORCES-MIB::forcesMib,,,,,,This MIB module contains managed object definitions for the ForCES Protocol. Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 5813; see the RFC itself for full legal notices.
.1.3.6.1.2.1.187.0,FORCES-MIB::forcesMibNotifications,,,,,,
.1.3.6.1.2.1.187.0.1,FORCES-MIB::forcesAssociationEntryUp,,,,,,This notification is generated as soon as an association enters the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations.
.1.3.6.1.2.1.187.0.2,FORCES-MIB::forcesAssociationEntryDown,,,,,,This notification is generated as soon as an association leaves the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations.
.1.3.6.1.2.1.187.0.3,FORCES-MIB::forcesAssociationEntryUpStats,,,,,,This notification is generated as soon as an association enters the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations.
.1.3.6.1.2.1.187.0.4,FORCES-MIB::forcesAssociationEntryDownStats,,,,,,This notification is generated as soon as an association leaves the UP state. Note that these notifications are not throttled as the CE itself should throttle the setup of associations.
.1.3.6.1.2.1.187.1,FORCES-MIB::forcesMibObjects,,,,,,
.1.3.6.1.2.1.187.1.1,FORCES-MIB::forcesLatestProtocolVersionSupported,Integer32,read-only,,current,,The ForCES protocol version supported by the CE. The current protocol version is 1. Note that the CE must also allow interaction with FEs supporting earlier versions.
.1.3.6.1.2.1.187.1.2,FORCES-MIB::forcesAssociations,,,,,,
.1.3.6.1.2.1.187.1.2.1,FORCES-MIB::forcesAssociationTable,,not-accessible,,current,,The (conceptual) table of associations.
.1.3.6.1.2.1.187.1.2.1.1,FORCES-MIB::forcesAssociationEntry,,not-accessible,forcesAssociationCEID:forcesAssociationFEID,current,,A (conceptual) entry for one association.
.1.3.6.1.2.1.187.1.2.1.1.1,FORCES-MIB::forcesAssociationCEID,OCTET,not-accessible,,current,,The ForCES ID of the CE.
.1.3.6.1.2.1.187.1.2.1.1.2,FORCES-MIB::forcesAssociationFEID,OCTET,not-accessible,,current,,The ForCES ID of the FE.
.1.3.6.1.2.1.187.1.2.1.1.3,FORCES-MIB::forcesAssociationRunningProtocolVersion,Integer32,read-only,,current,,The current ForCES protocol version used in this association. The current protocol version is 1.
.1.3.6.1.2.1.187.1.2.1.1.4,FORCES-MIB::forcesAssociationTimeUp,TimeTicks,read-only,,current,,The value of sysUpTime at the time this association entered the UP state. If this association started prior to the last initialization of the network subsystem, then this object contains a zero value. This object allows to uniquely identify associations with the same CE and FE IDs.
.1.3.6.1.2.1.187.1.2.1.1.5,FORCES-MIB::forcesAssociationTimeDown,TimeTicks,accessible-for-notify,,current,,The value of sysUpTime at the time this association left the UP state.
.1.3.6.1.2.1.187.1.2.1.1.6,FORCES-MIB::forcesAssociationHBMsgSent,Gauge32,read-only,,current,,A counter of how many Heartbeat messages have been sent by the CE on this association since the association entered the UP state. Discontinuities in the value of this counter can occur at reinitialization of the management system, and at other times as indicated by the value of forcesAssociationCounterDiscontinuityTime.
.1.3.6.1.2.1.187.1.2.1.1.7,FORCES-MIB::forcesAssociationHBMsgReceived,Gauge32,read-only,,current,,A counter of how many Heartbeat messages have been received by the CE on this association since the association entered the UP state. Discontinuities in the value of this counter can occur at reinitialization of the management system, and at other times as indicated by the value of forcesAssociationCounterDiscontinuityTime.
.1.3.6.1.2.1.187.1.2.1.1.8,FORCES-MIB::forcesAssociationOperMsgSent,Gauge32,read-only,,current,,A counter of how many messages other than Heartbeat (i.e., Config and Query) have been sent by the CE on this association since the association entered the UP state. Discontinuities in the value of this counter can occur at reinitialization of the management system, and at other times as indicated by the value of forcesAssociationCounterDiscontinuityTime.
.1.3.6.1.2.1.187.1.2.1.1.9,FORCES-MIB::forcesAssociationOperMsgReceived,Gauge32,read-only,,current,,A counter of how many messages other than Heartbeat (i.e., Config response, Query response, event notification, and packet redirect) have been received by the CE on this association since the association entered the UP state. Discontinuities in the value of this counter can occur at reinitialization of the management system, and at other times as indicated by the value of forcesAssociationCounterDiscontinuityTime.
.1.3.6.1.2.1.187.1.2.1.1.10,FORCES-MIB::forcesAssociationCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this association's counters suffered a discontinuity. The relevant counters are the specific instances associated with this association of any ZeroBasedCounter32 object contained in the forcesAssociationTable. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.187.2,FORCES-MIB::forcesMibConformance,,,,,,
.1.3.6.1.2.1.187.2.1,FORCES-MIB::forcesMibCompliances,,,,,,
.1.3.6.1.2.1.187.2.1.1,FORCES-MIB::forcesMibCompliance,,,,,,The compliance statement for routers running ForCES and implementing the ForCES MIB.
.1.3.6.1.2.1.187.2.2,FORCES-MIB::forcesMibGroups,,,,,,
.1.3.6.1.2.1.187.2.2.1,FORCES-MIB::forcesNotificationGroup,,,,,,A collection of notifications for signaling important ForCES events.
.1.3.6.1.2.1.187.2.2.2,FORCES-MIB::forcesMibGroup,,,,,,A collection of objects to support management of ForCES routers.
.1.3.6.1.2.1.187.2.2.3,FORCES-MIB::forcesNotificationStatsGroup,,,,,,A collection of optional notifications for signaling important ForCES events including statistics.
.1.3.6.1.2.1.187.2.2.4,FORCES-MIB::forcesStatsGroup,,,,,,A collection of optional objects to provide extra information about the associations. There is no protocol reason to keep such information, but these objects can be very useful in debugging connectivity problems.
.1.3.6.1.2.1.188,PW-TC-STD-MIB::pwTcStdMIB,,,,,,This MIB module defines TEXTUAL-CONVENTIONS for concepts used in pseudowire edge-to-edge networks. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5542; see the RFC itself for full legal notices.
.1.3.6.1.2.1.190,SNMP-TSM-MIB::snmpTsmMIB,,,,,,The Transport Security Model MIB. In keeping with the RFC 3411 design decisions to use self-contained documents, the RFC that contains the definition of this MIB module also includes the elements of procedure that are needed for processing the Transport Security Model for SNMP. These MIB objects SHOULD NOT be modified via other subsystems or models defined in other documents. This allows the Transport Security Model for SNMP to be designed and documented as independent and self-contained, having no direct impact on other modules, and this allows this module to be upgraded and supplemented as the need arises, and to move along the standards track on different time-lines from other modules. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5591; see the RFC itself for full legal notices.
.1.3.6.1.2.1.190.0,SNMP-TSM-MIB::snmpTsmNotifications,,,,,,
.1.3.6.1.2.1.190.1,SNMP-TSM-MIB::snmpTsmMIBObjects,,,,,,
.1.3.6.1.2.1.190.1.1,SNMP-TSM-MIB::snmpTsmStats,,,,,,
.1.3.6.1.2.1.190.1.1.1,SNMP-TSM-MIB::snmpTsmInvalidCaches,Counter32,read-only,,current,,The number of incoming messages dropped because the tmStateReference referred to an invalid cache. 
.1.3.6.1.2.1.190.1.1.2,SNMP-TSM-MIB::snmpTsmInadequateSecurityLevels,Counter32,read-only,,current,,The number of incoming messages dropped because the securityLevel asserted by the Transport Model was less than the securityLevel requested by the application. 
.1.3.6.1.2.1.190.1.1.3,SNMP-TSM-MIB::snmpTsmUnknownPrefixes,Counter32,read-only,,current,,The number of messages dropped because snmpTsmConfigurationUsePrefix was set to true and there is no known prefix for the specified transport domain. 
.1.3.6.1.2.1.190.1.1.4,SNMP-TSM-MIB::snmpTsmInvalidPrefixes,Counter32,read-only,,current,,The number of messages dropped because the securityName associated with an outgoing message did not contain a valid transport domain prefix. 
.1.3.6.1.2.1.190.1.2,SNMP-TSM-MIB::snmpTsmConfiguration,,,,,,
.1.3.6.1.2.1.190.1.2.1,SNMP-TSM-MIB::snmpTsmConfigurationUsePrefix,INTEGER,read-write,,current,true(1):false(2),If this object is set to true, then securityNames passing to and from the application are expected to contain a transport-domain-specific prefix. If this object is set to true, then a domain-specific prefix will be added by the TSM to the securityName for incoming messages and removed from the securityName when processing outgoing messages. Transport domains and prefixes are maintained in a registry by IANA. This object SHOULD persist across system reboots. 
.1.3.6.1.2.1.190.2,SNMP-TSM-MIB::snmpTsmConformance,,,,,,
.1.3.6.1.2.1.190.2.1,SNMP-TSM-MIB::snmpTsmCompliances,,,,,,
.1.3.6.1.2.1.190.2.1.1,SNMP-TSM-MIB::snmpTsmCompliance,,,,,,The compliance statement for SNMP engines that support the SNMP-TSM-MIB. 
.1.3.6.1.2.1.190.2.2,SNMP-TSM-MIB::snmpTsmGroups,,,,,,
.1.3.6.1.2.1.190.2.2.2,SNMP-TSM-MIB::snmpTsmGroup,,,,,,A collection of objects for maintaining information of an SNMP engine that implements the SNMP Transport Security Model. 
.1.3.6.1.2.1.191,OSPFV3-MIB::ospfv3MIB,,,,,,The MIB module for OSPF version 3. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5643; see the RFC itself for full legal notices.
.1.3.6.1.2.1.191.0,OSPFV3-MIB::ospfv3Notifications,,,,,,
.1.3.6.1.2.1.191.0.1,OSPFV3-MIB::ospfv3VirtIfStateChange,,,,,,An ospfv3VirtIfStateChange notification signifies that there has been a change in the state of an OSPFv3 virtual interface. This notification should be generated when the interface state regresses (e.g., goes from Point-to-Point to Down) or progresses to a terminal state (i.e., Point-to-Point).
.1.3.6.1.2.1.191.0.2,OSPFV3-MIB::ospfv3NbrStateChange,,,,,,An ospfv3NbrStateChange notification signifies that there has been a change in the state of a non-virtual OSPFv3 neighbor. This notification should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., 2-Way or Full). When a neighbor transitions from or to Full on non-broadcast multi-access and broadcast networks, the notification should be generated by the Designated Router. A Designated Router transitioning to Down will be noted by ospfIfStateChange.
.1.3.6.1.2.1.191.0.3,OSPFV3-MIB::ospfv3VirtNbrStateChange,,,,,,An ospfv3VirtNbrStateChange notification signifies that there has been a change in the state of an OSPFv3 virtual neighbor. This notification should be generated when the neighbor state regresses (e.g., goes from Attempt or Full to 1-Way or Down) or progresses to a terminal state (e.g., Full).
.1.3.6.1.2.1.191.0.4,OSPFV3-MIB::ospfv3IfConfigError,,,,,,An ospfv3IfConfigError notification signifies that a packet has been received on a non-virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a notification only if it prevents an adjacency from forming.
.1.3.6.1.2.1.191.0.5,OSPFV3-MIB::ospfv3VirtIfConfigError,,,,,,An ospfv3VirtIfConfigError notification signifies that a packet has been received on a virtual interface from a router whose configuration parameters conflict with this router's configuration parameters. Note that the event optionMismatch should cause a notification only if it prevents an adjacency from forming.
.1.3.6.1.2.1.191.0.6,OSPFV3-MIB::ospfv3IfRxBadPacket,,,,,,An ospfv3IfRxBadPacket notification signifies that an OSPFv3 packet that cannot be parsed has been received on a non-virtual interface.
.1.3.6.1.2.1.191.0.7,OSPFV3-MIB::ospfv3VirtIfRxBadPacket,,,,,,An ospfv3VirtIfRxBadPacket notification signifies that an OSPFv3 packet that cannot be parsed has been received on a virtual interface.
.1.3.6.1.2.1.191.0.8,OSPFV3-MIB::ospfv3LsdbOverflow,,,,,,An ospfv3LsdbOverflow notification signifies that the number of LSAs in the router's link state database has exceeded ospfv3ExtAreaLsdbLimit.
.1.3.6.1.2.1.191.0.9,OSPFV3-MIB::ospfv3LsdbApproachingOverflow,,,,,,An ospfv3LsdbApproachingOverflow notification signifies that the number of LSAs in the router's link state database has exceeded ninety percent of ospfv3ExtAreaLsdbLimit.
.1.3.6.1.2.1.191.0.10,OSPFV3-MIB::ospfv3IfStateChange,,,,,,An ospfv3IfStateChange notification signifies that there has been a change in the state of a non-virtual OSPFv3 interface. This notification should be generated when the interface state regresses (e.g., goes from DR to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, DR, or Backup).
.1.3.6.1.2.1.191.0.11,OSPFV3-MIB::ospfv3NssaTranslatorStatusChange,,,,,,An ospfv3NssaTranslatorStatusChange notification indicates that there has been a change in the router's ability to translate OSPFv3 NSSA LSAs into OSPFv3 External LSAs. This notification should be generated when the Translator Status transitions from or to any defined status on a per-area basis.
.1.3.6.1.2.1.191.0.12,OSPFV3-MIB::ospfv3RestartStatusChange,,,,,,An ospfv3RestartStatusChange notification signifies that there has been a change in the graceful restart state for the router. This notification should be generated when the router restart status changes.
.1.3.6.1.2.1.191.0.13,OSPFV3-MIB::ospfv3NbrRestartHelperStatusChange,,,,,,An ospfv3NbrRestartHelperStatusChange notification signifies that there has been a change in the graceful restart helper state for the neighbor. This notification should be generated when the neighbor restart helper status transitions for a neighbor.
.1.3.6.1.2.1.191.0.14,OSPFV3-MIB::ospfv3VirtNbrRestartHelperStatusChange,,,,,,An ospfv3VirtNbrRestartHelperStatusChange notification signifies that there has been a change in the graceful restart helper state for the virtual neighbor. This notification should be generated when the virtual neighbor restart helper status transitions for a virtual neighbor.
.1.3.6.1.2.1.191.1,OSPFV3-MIB::ospfv3Objects,,,,,,
.1.3.6.1.2.1.191.1.1,OSPFV3-MIB::ospfv3GeneralGroup,,,,,,
.1.3.6.1.2.1.191.1.1.1,OSPFV3-MIB::ospfv3RouterId,Unsigned32,read-write,,current,,A 32-bit unsigned integer uniquely identifying the router in the Autonomous System. To ensure uniqueness, this may default to the 32-bit unsigned integer representation of one of the router's IPv4 interface addresses (if IPv4 is configured on the router). This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.2,OSPFV3-MIB::ospfv3AdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative status of OSPFv3 in the router. The value 'enabled' denotes that the OSPFv3 Process is active on at least one interface; 'disabled' disables it on all interfaces. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.3,OSPFV3-MIB::ospfv3VersionNumber,INTEGER,read-only,,current,version3(3),The version number of OSPF for IPv6 is 3.
.1.3.6.1.2.1.191.1.1.4,OSPFV3-MIB::ospfv3AreaBdrRtrStatus,INTEGER,read-only,,current,true(1):false(2),A flag to denote whether this router is an area border router. The value of this object is true (1) when the router is an area border router.
.1.3.6.1.2.1.191.1.1.5,OSPFV3-MIB::ospfv3ASBdrRtrStatus,INTEGER,read-write,,current,true(1):false(2),A flag to note whether this router is configured as an Autonomous System border router. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.6,OSPFV3-MIB::ospfv3AsScopeLsaCount,Gauge32,read-only,,current,,The number of AS-scope (e.g., AS-External) link state advertisements in the link state database.
.1.3.6.1.2.1.191.1.1.7,OSPFV3-MIB::ospfv3AsScopeLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the LS checksums of the AS-scoped link state advertisements contained in the link state database. This sum can be used to determine if there has been a change in a router's link state database or to compare the link state database of two routers.
.1.3.6.1.2.1.191.1.1.8,OSPFV3-MIB::ospfv3OriginateNewLsas,Counter32,read-only,,current,,The number of new link state advertisements that have been originated. This number is incremented each time the router originates a new LSA. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.1.9,OSPFV3-MIB::ospfv3RxNewLsas,Counter32,read-only,,current,,The number of link state advertisements received that are determined to be new instantiations. This number does not include newer instantiations of self-originated link state advertisements. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.1.10,OSPFV3-MIB::ospfv3ExtLsaCount,Gauge32,read-only,,current,,The number of External (LS type 0x4005) in the link state database.
.1.3.6.1.2.1.191.1.1.11,OSPFV3-MIB::ospfv3ExtAreaLsdbLimit,Integer32,read-write,,current,,The maximum number of non-default AS-external-LSA entries that can be stored in the link state database. If the value is -1, then there is no limit. When the number of non-default AS-external-LSAs in a router's link state database reaches ospfv3ExtAreaLsdbLimit, the router enters Overflow state. The router never holds more than ospfv3ExtAreaLsdbLimit non-default AS-external-LSAs in its database. ospfv3ExtAreaLsdbLimit MUST be set identically in all routers attached to the OSPFv3 backbone and/or any regular OSPFv3 area (i.e., OSPFv3 stub areas and not-so-stubby-areas (NSSAs) are excluded). This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.12,OSPFV3-MIB::ospfv3ExitOverflowInterval,Unsigned32,read-write,,current,,The number of seconds that, after entering Overflow state, a router will attempt to leave Overflow state. This allows the router to again originate non-default, AS-External-LSAs. When set to 0, the router will not leave Overflow state until restarted. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.13,OSPFV3-MIB::ospfv3DemandExtensions,INTEGER,read-write,,current,true(1):false(2),The router's support for demand circuits. The value of this object is true (1) when demand circuits are supported. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.14,OSPFV3-MIB::ospfv3ReferenceBandwidth,Unsigned32,read-write,,current,,Reference bandwidth in kilobits per second for calculating default interface metrics. The default value is 100,000 KBPS (100 MBPS). This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.15,OSPFV3-MIB::ospfv3RestartSupport,INTEGER,read-write,,current,none(1):plannedOnly(2):plannedAndUnplanned(3),The router's support for OSPF graceful restart. Options include no restart support, only planned restarts, or both planned and unplanned restarts. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.16,OSPFV3-MIB::ospfv3RestartInterval,Unsigned32,read-write,,current,,Configured OSPF graceful restart timeout interval. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.17,OSPFV3-MIB::ospfv3RestartStrictLsaChecking,INTEGER,read-write,,current,true(1):false(2),Indicates if strict LSA checking is enabled for graceful restart. A value of true (1) indicates that strict LSA checking is enabled. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.18,OSPFV3-MIB::ospfv3RestartStatus,INTEGER,read-only,,current,notRestarting(1):plannedRestart(2):unplannedRestart(3),The current status of OSPF graceful restart capability.
.1.3.6.1.2.1.191.1.1.19,OSPFV3-MIB::ospfv3RestartAge,Unsigned32,read-only,,current,,Remaining time in the current OSPF graceful restart interval.
.1.3.6.1.2.1.191.1.1.20,OSPFV3-MIB::ospfv3RestartExitReason,INTEGER,read-only,,current,none(1):inProgress(2):completed(3):timedOut(4):topologyChanged(5),Describes the outcome of the last attempt at a graceful restart. none: no restart has yet been attempted. inProgress: a restart attempt is currently underway. completed: the last restart completed successfully. timedOut: the last restart timed out. topologyChanged: the last restart was aborted due to a topology change.
.1.3.6.1.2.1.191.1.1.21,OSPFV3-MIB::ospfv3NotificationEnable,INTEGER,read-write,,current,true(1):false(2),This object provides a coarse level of control over the generation of OSPFv3 notifications. If this object is set to true (1), then it enables the generation of OSPFv3 notifications. If it is set to false (2), these notifications are not generated. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.22,OSPFV3-MIB::ospfv3StubRouterSupport,INTEGER,read-only,,current,true(1):false(2),The router's support for stub router functionality. An object value of true (1) indicates that stub router functionality is supported.
.1.3.6.1.2.1.191.1.1.23,OSPFV3-MIB::ospfv3StubRouterAdvertisement,INTEGER,read-write,,current,doNotAdvertise(1):advertise(2),This object controls the advertisement of stub LSAs by the router. The value doNotAdvertise (1) will result in the advertisement of standard LSAs and is the default value. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.1.24,OSPFV3-MIB::ospfv3DiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one of this MIB's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.191.1.1.25,OSPFV3-MIB::ospfv3RestartTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which the ospfv3RestartExitReason was updated.
.1.3.6.1.2.1.191.1.2,OSPFV3-MIB::ospfv3AreaTable,,not-accessible,,current,,Information describing the configured parameters and cumulative statistics of the router's attached areas. The interfaces and virtual links are configured as part of these areas. Area 0, by definition, is the backbone area.
.1.3.6.1.2.1.191.1.2.1,OSPFV3-MIB::ospfv3AreaEntry,,not-accessible,ospfv3AreaId,current,,Information describing the configured parameters and cumulative statistics of one of the router's attached areas. The information in this table is persistent, and when written, the entity SHOULD save the a change to non-volatile storage.
.1.3.6.1.2.1.191.1.2.1.1,OSPFV3-MIB::ospfv3AreaId,Unsigned32,not-accessible,,current,,A 32-bit unsigned integer uniquely identifying an area. Area ID 0 is used for the OSPFv3 backbone.
.1.3.6.1.2.1.191.1.2.1.2,OSPFV3-MIB::ospfv3AreaImportAsExtern,INTEGER,read-create,,current,importExternal(1):importNoExternal(2):importNssa(3),Indicates whether an area is a stub area, NSSA, or standard area. AS-scope LSAs are not imported into stub areas or NSSAs. NSSAs import AS-External data as NSSA LSAs that have Area-scope.
.1.3.6.1.2.1.191.1.2.1.3,OSPFV3-MIB::ospfv3AreaSpfRuns,Counter32,read-only,,current,,The number of times that the intra-area route table has been calculated using this area's link state database. This is typically done using Dijkstra's algorithm. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.2.1.4,OSPFV3-MIB::ospfv3AreaBdrRtrCount,Gauge32,read-only,,current,,The total number of area border routers reachable within this area. This is initially zero, and is calculated in each Shortest Path First (SPF) pass.
.1.3.6.1.2.1.191.1.2.1.5,OSPFV3-MIB::ospfv3AreaAsBdrRtrCount,Gauge32,read-only,,current,,The total number of Autonomous System border routers reachable within this area. This is initially zero, and is calculated in each SPF pass.
.1.3.6.1.2.1.191.1.2.1.6,OSPFV3-MIB::ospfv3AreaScopeLsaCount,Gauge32,read-only,,current,,The total number of Area-scope link state advertisements in this area's link state database.
.1.3.6.1.2.1.191.1.2.1.7,OSPFV3-MIB::ospfv3AreaScopeLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the Area-scope link state advertisements' LS checksums contained in this area's link state database. The sum can be used to determine if there has been a change in a router's link state database or to compare the link state database of two routers.
.1.3.6.1.2.1.191.1.2.1.8,OSPFV3-MIB::ospfv3AreaSummary,INTEGER,read-create,,current,noAreaSummary(1):sendAreaSummary(2),The variable ospfv3AreaSummary controls the import of Inter-Area LSAs into stub and NSSA areas. It has no effect on other areas. If it is noAreaSummary, the router will neither originate nor propagate Inter-Area LSAs into the stub or NSSA area. It will only advertise a default route. If it is sendAreaSummary, the router will both summarize and propagate Inter-Area LSAs.
.1.3.6.1.2.1.191.1.2.1.9,OSPFV3-MIB::ospfv3AreaRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.191.1.2.1.10,OSPFV3-MIB::ospfv3AreaStubMetric,Integer32,read-create,,current,,The metric value advertised for the default route into stub and NSSA areas. By default, this equals the least metric among the interfaces to other areas.
.1.3.6.1.2.1.191.1.2.1.11,OSPFV3-MIB::ospfv3AreaNssaTranslatorRole,INTEGER,read-create,,current,always(1):candidate(2),Indicates an NSSA border router's policy to perform NSSA translation of NSSA-LSAs into AS-External-LSAs.
.1.3.6.1.2.1.191.1.2.1.12,OSPFV3-MIB::ospfv3AreaNssaTranslatorState,INTEGER,read-only,,current,enabled(1):elected(2):disabled(3),Indicates if and how an NSSA border router is performing NSSA translation of NSSA-LSAs into AS-External-LSAs. When this object is set to 'enabled', the NSSA border router's ospfv3AreaNssaTranslatorRole has been set to 'always'. When this object is set to 'elected', a candidate NSSA border router is translating NSSA-LSAs into AS-External-LSAs. When this object is set to 'disabled', a candidate NSSA Border router is NOT translating NSSA-LSAs into AS-External-LSAs.
.1.3.6.1.2.1.191.1.2.1.13,OSPFV3-MIB::ospfv3AreaNssaTranslatorStabInterval,Unsigned32,read-create,,current,,The stability interval defined as the number of seconds after an elected translator determines its services are no longer required that it should continue to perform its translation duties.
.1.3.6.1.2.1.191.1.2.1.14,OSPFV3-MIB::ospfv3AreaNssaTranslatorEvents,Counter32,read-only,,current,,Indicates the number of Translator state changes that have occurred since the last start-up of the OSPFv3 routing process. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.2.1.15,OSPFV3-MIB::ospfv3AreaStubMetricType,INTEGER,read-create,,current,ospfv3Metric(1):comparableCost(2):nonComparable(3),This variable assigns the type of metric advertised as a default route.
.1.3.6.1.2.1.191.1.2.1.16,OSPFV3-MIB::ospfv3AreaTEEnabled,INTEGER,read-create,,current,true(1):false(2),Indicates whether or not traffic engineering is enabled in the area. The object is set to the value true (1) to enable traffic engineering. Traffic engineering is disabled by default.
.1.3.6.1.2.1.191.1.3,OSPFV3-MIB::ospfv3AsLsdbTable,,not-accessible,,current,,The OSPFv3 Process's AS-scope link state database (LSDB). The LSDB contains the AS-scope link state advertisements from throughout the areas that the device is attached to.
.1.3.6.1.2.1.191.1.3.1,OSPFV3-MIB::ospfv3AsLsdbEntry,,not-accessible,ospfv3AsLsdbType:ospfv3AsLsdbRouterId:ospfv3AsLsdbLsid,current,,A single AS-scope link state advertisement.
.1.3.6.1.2.1.191.1.3.1.1,OSPFV3-MIB::ospfv3AsLsdbType,Unsigned32,not-accessible,,current,,The type of the link state advertisement. Each link state type has a separate advertisement format. AS-scope LSAs not recognized by the router may be stored in the database.
.1.3.6.1.2.1.191.1.3.1.2,OSPFV3-MIB::ospfv3AsLsdbRouterId,Unsigned32,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.191.1.3.1.3,OSPFV3-MIB::ospfv3AsLsdbLsid,Unsigned32,not-accessible,,current,,The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.
.1.3.6.1.2.1.191.1.3.1.4,OSPFV3-MIB::ospfv3AsLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.191.1.3.1.5,OSPFV3-MIB::ospfv3AsLsdbAge,Unsigned32,read-only,,current,,This field is the age of the link state advertisement in seconds. The high-order bit of the LS age field is considered the DoNotAge bit for support of on-demand circuits.
.1.3.6.1.2.1.191.1.3.1.6,OSPFV3-MIB::ospfv3AsLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.191.1.3.1.7,OSPFV3-MIB::ospfv3AsLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.191.1.3.1.8,OSPFV3-MIB::ospfv3AsLsdbTypeKnown,INTEGER,read-only,,current,true(1):false(2),The value true (1) indicates that the LSA type is recognized by this router.
.1.3.6.1.2.1.191.1.4,OSPFV3-MIB::ospfv3AreaLsdbTable,,not-accessible,,current,,The OSPFv3 Process's Area-scope LSDB. The LSDB contains the Area-scope link state advertisements from throughout the area that the device is attached to.
.1.3.6.1.2.1.191.1.4.1,OSPFV3-MIB::ospfv3AreaLsdbEntry,,not-accessible,ospfv3AreaLsdbAreaId:ospfv3AreaLsdbType:ospfv3AreaLsdbRouterId:ospfv3AreaLsdbLsid,current,,A single Area-scope link state advertisement.
.1.3.6.1.2.1.191.1.4.1.1,OSPFV3-MIB::ospfv3AreaLsdbAreaId,Unsigned32,not-accessible,,current,,The 32-bit identifier of the Area from which the LSA was received.
.1.3.6.1.2.1.191.1.4.1.2,OSPFV3-MIB::ospfv3AreaLsdbType,Unsigned32,not-accessible,,current,,The type of the link state advertisement. Each link state type has a separate advertisement format. Area-scope LSAs unrecognized by the router are also stored in this database.
.1.3.6.1.2.1.191.1.4.1.3,OSPFV3-MIB::ospfv3AreaLsdbRouterId,Unsigned32,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.191.1.4.1.4,OSPFV3-MIB::ospfv3AreaLsdbLsid,Unsigned32,not-accessible,,current,,The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.
.1.3.6.1.2.1.191.1.4.1.5,OSPFV3-MIB::ospfv3AreaLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.191.1.4.1.6,OSPFV3-MIB::ospfv3AreaLsdbAge,Unsigned32,read-only,,current,,This field is the age of the link state advertisement in seconds. The high-order bit of the LS age field is considered the DoNotAge bit for support of on-demand circuits.
.1.3.6.1.2.1.191.1.4.1.7,OSPFV3-MIB::ospfv3AreaLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.191.1.4.1.8,OSPFV3-MIB::ospfv3AreaLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.191.1.4.1.9,OSPFV3-MIB::ospfv3AreaLsdbTypeKnown,INTEGER,read-only,,current,true(1):false(2),The value true (1) indicates that the LSA type is recognized by this router.
.1.3.6.1.2.1.191.1.5,OSPFV3-MIB::ospfv3LinkLsdbTable,,not-accessible,,current,,The OSPFv3 Process's Link-scope LSDB for non-virtual interfaces. The LSDB contains the Link-scope link state advertisements from the interfaces that the device is attached to.
.1.3.6.1.2.1.191.1.5.1,OSPFV3-MIB::ospfv3LinkLsdbEntry,,not-accessible,ospfv3LinkLsdbIfIndex:ospfv3LinkLsdbIfInstId:ospfv3LinkLsdbType:ospfv3LinkLsdbRouterId:ospfv3LinkLsdbLsid,current,,A single Link-scope link state advertisement.
.1.3.6.1.2.1.191.1.5.1.1,OSPFV3-MIB::ospfv3LinkLsdbIfIndex,Integer32,not-accessible,,current,,The identifier of the link from which the LSA was received.
.1.3.6.1.2.1.191.1.5.1.2,OSPFV3-MIB::ospfv3LinkLsdbIfInstId,Unsigned32,not-accessible,,current,,The identifier of the interface instance from which the LSA was received.
.1.3.6.1.2.1.191.1.5.1.3,OSPFV3-MIB::ospfv3LinkLsdbType,Unsigned32,not-accessible,,current,,The type of the link state advertisement. Each link state type has a separate advertisement format. Link-scope LSAs unrecognized by the router are also stored in this database.
.1.3.6.1.2.1.191.1.5.1.4,OSPFV3-MIB::ospfv3LinkLsdbRouterId,Unsigned32,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.191.1.5.1.5,OSPFV3-MIB::ospfv3LinkLsdbLsid,Unsigned32,not-accessible,,current,,The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics. However, in OSPFv3 the Link State ID always contains the flooding scope of the LSA.
.1.3.6.1.2.1.191.1.5.1.6,OSPFV3-MIB::ospfv3LinkLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.191.1.5.1.7,OSPFV3-MIB::ospfv3LinkLsdbAge,Unsigned32,read-only,,current,,This field is the age of the link state advertisement in seconds. The high-order bit of the LS age field is considered the DoNotAge bit for support of on-demand circuits.
.1.3.6.1.2.1.191.1.5.1.8,OSPFV3-MIB::ospfv3LinkLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.191.1.5.1.9,OSPFV3-MIB::ospfv3LinkLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.191.1.5.1.10,OSPFV3-MIB::ospfv3LinkLsdbTypeKnown,INTEGER,read-only,,current,true(1):false(2),The value true (1) indicates that the LSA type is recognized by this router.
.1.3.6.1.2.1.191.1.6,OSPFV3-MIB::ospfv3HostTable,,not-accessible,,current,,The Host/Metric Table indicates what hosts are directly attached to the router and their corresponding metrics.
.1.3.6.1.2.1.191.1.6.1,OSPFV3-MIB::ospfv3HostEntry,,not-accessible,ospfv3HostAddressType:ospfv3HostAddress,current,,A metric to be advertised when a given host is reachable. The information in this table is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.6.1.1,OSPFV3-MIB::ospfv3HostAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of ospfv3HostAddress. Only IPv6 global address type is expected.
.1.3.6.1.2.1.191.1.6.1.2,OSPFV3-MIB::ospfv3HostAddress,OCTET,not-accessible,,current,,The IPv6 address of the host. Must be an IPv6 global address.
.1.3.6.1.2.1.191.1.6.1.3,OSPFV3-MIB::ospfv3HostMetric,Integer32,read-create,,current,,The metric to be advertised.
.1.3.6.1.2.1.191.1.6.1.4,OSPFV3-MIB::ospfv3HostRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.191.1.6.1.5,OSPFV3-MIB::ospfv3HostAreaID,Unsigned32,read-create,,current,,The Area the host entry is to be found within. By default, the area for the subsuming OSPFv3 interface, or Area 0 if there is no subsuming interface.
.1.3.6.1.2.1.191.1.7,OSPFV3-MIB::ospfv3IfTable,,not-accessible,,current,,The OSPFv3 Interface Table describes the interfaces from the viewpoint of OSPFv3.
.1.3.6.1.2.1.191.1.7.1,OSPFV3-MIB::ospfv3IfEntry,,not-accessible,ospfv3IfIndex:ospfv3IfInstId,current,,The OSPFv3 Interface Entry describes one interface from the viewpoint of OSPFv3. The information in this table is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.7.1.1,OSPFV3-MIB::ospfv3IfIndex,Integer32,not-accessible,,current,,The interface index of this OSPFv3 interface. It corresponds to the interface index of the IPv6 interface on which OSPFv3 is configured.
.1.3.6.1.2.1.191.1.7.1.2,OSPFV3-MIB::ospfv3IfInstId,Unsigned32,not-accessible,,current,,Enables multiple interface instances of OSPFv3 to be run over a single link. Each interface instance would be assigned a separate ID. This ID has local link significance only.
.1.3.6.1.2.1.191.1.7.1.3,OSPFV3-MIB::ospfv3IfAreaId,Unsigned32,read-create,,current,,A 32-bit integer uniquely identifying the area to which the interface connects. Area ID 0 is used for the OSPFv3 backbone.
.1.3.6.1.2.1.191.1.7.1.4,OSPFV3-MIB::ospfv3IfType,INTEGER,read-create,,current,broadcast(1):nbma(2):pointToPoint(3):pointToMultipoint(5),The OSPFv3 interface type.
.1.3.6.1.2.1.191.1.7.1.5,OSPFV3-MIB::ospfv3IfAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),The OSPFv3 interface's administrative status. The value formed on the interface; the interface will be advertised as an internal route to some area. The value 'disabled' denotes that the interface is external to OSPFv3. Note that a value of 'disabled' for the object ospfv3AdminStatus will override a value of 'enabled' for the interface.
.1.3.6.1.2.1.191.1.7.1.6,OSPFV3-MIB::ospfv3IfRtrPriority,Integer32,read-create,,current,,The priority of this interface. Used in multi-access networks, this field is used in the designated-router election algorithm. The value 0 signifies that the router is not eligible to become the Designated Router on this particular network. In the event of a tie in this value, routers will use their Router ID as a tie breaker.
.1.3.6.1.2.1.191.1.7.1.7,OSPFV3-MIB::ospfv3IfTransitDelay,Unsigned32,read-create,,current,,The estimated number of seconds it takes to transmit a Link State Update packet over this interface. LSAs contained in the update packet must have their age incremented by this amount before transmission. This value should take into account the transmission and propagation delays of the interface.
.1.3.6.1.2.1.191.1.7.1.8,OSPFV3-MIB::ospfv3IfRetransInterval,Unsigned32,read-create,,current,,The number of seconds between link state advertisement retransmissions for adjacencies belonging to this interface. This value is also used when retransmitting database description and Link State Request packets.
.1.3.6.1.2.1.191.1.7.1.9,OSPFV3-MIB::ospfv3IfHelloInterval,Integer32,read-create,,current,,The length of time, in seconds, between the Hello packets that the router sends on the interface. This value must be the same for all routers attached to a common network.
.1.3.6.1.2.1.191.1.7.1.10,OSPFV3-MIB::ospfv3IfRtrDeadInterval,Unsigned32,read-create,,current,,The number of seconds that a router's Hello packets have not been seen before its neighbors declare the router down on the interface. This should be some multiple of the Hello interval. This value must be the same for all routers attached to a common network.
.1.3.6.1.2.1.191.1.7.1.11,OSPFV3-MIB::ospfv3IfPollInterval,Unsigned32,read-create,,current,,The larger time interval, in seconds, between the Hello packets sent to an inactive, non-broadcast multi-access neighbor.
.1.3.6.1.2.1.191.1.7.1.12,OSPFV3-MIB::ospfv3IfState,INTEGER,read-only,,current,down(1):loopback(2):waiting(3):pointToPoint(4):designatedRouter(5):backupDesignatedRouter(6):otherDesignatedRouter(7):standby(8),The OSPFv3 interface state. An interface may be in standby state if there are multiple interfaces on the link and another interface is active. The interface may be in Down state if the underlying IPv6 interface is down or if the admin status is 'disabled' either globally or for the interface.
.1.3.6.1.2.1.191.1.7.1.13,OSPFV3-MIB::ospfv3IfDesignatedRouter,Unsigned32,read-only,,current,,The Router ID of the Designated Router.
.1.3.6.1.2.1.191.1.7.1.14,OSPFV3-MIB::ospfv3IfBackupDesignatedRouter,Unsigned32,read-only,,current,,The Router ID of the Backup Designated Router.
.1.3.6.1.2.1.191.1.7.1.15,OSPFV3-MIB::ospfv3IfEvents,Counter32,read-only,,current,,The number of times this OSPFv3 interface has changed its state or an error has occurred. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.7.1.16,OSPFV3-MIB::ospfv3IfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.191.1.7.1.17,OSPFV3-MIB::ospfv3IfDemand,INTEGER,read-create,,current,true(1):false(2),Indicates whether Demand OSPFv3 procedures (Hello suppression to FULL neighbors and setting the DoNotAge flag on propagated LSAs) should be performed on this interface.
.1.3.6.1.2.1.191.1.7.1.18,OSPFV3-MIB::ospfv3IfMetricValue,Integer32,read-create,,current,,The metric assigned to this interface. The default value of the metric is 'Reference Bandwidth / ifSpeed'. The value of the reference bandwidth can be set in the ospfv3ReferenceBandwidth object.
.1.3.6.1.2.1.191.1.7.1.19,OSPFV3-MIB::ospfv3IfLinkScopeLsaCount,Gauge32,read-only,,current,,The total number of Link-scope link state advertisements in this link's link state database.
.1.3.6.1.2.1.191.1.7.1.20,OSPFV3-MIB::ospfv3IfLinkLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the Link-scope link state advertisements' LS checksums contained in this link's link state database. The sum can be used to determine if there has been a change in a router's link state database or to compare the link state database of two routers.
.1.3.6.1.2.1.191.1.7.1.21,OSPFV3-MIB::ospfv3IfDemandNbrProbe,INTEGER,read-create,,current,true(1):false(2),Indicates whether or not neighbor probing is enabled to determine whether or not the neighbor is inactive. Neighbor probing is disabled by default.
.1.3.6.1.2.1.191.1.7.1.22,OSPFV3-MIB::ospfv3IfDemandNbrProbeRetransLimit,Unsigned32,read-create,,current,,The number of consecutive LSA retransmissions before the neighbor is deemed inactive and the neighbor adjacency is brought down.
.1.3.6.1.2.1.191.1.7.1.23,OSPFV3-MIB::ospfv3IfDemandNbrProbeInterval,Unsigned32,read-create,,current,,Defines how often the neighbor will be probed.
.1.3.6.1.2.1.191.1.7.1.24,OSPFV3-MIB::ospfv3IfTEDisabled,INTEGER,read-create,,current,true(1):false(2),Indicates whether or not traffic engineering is disabled on the interface when traffic engineering is enabled in the area where the interface is attached. The object is set to the value true (1) to disable traffic engineering on the interface. Traffic engineering is enabled by default on the interface when traffic engineering is enabled in the area where the interface is attached.
.1.3.6.1.2.1.191.1.7.1.25,OSPFV3-MIB::ospfv3IfLinkLSASuppression,INTEGER,read-create,,current,true(1):false(2),Specifies whether or not link LSA origination is suppressed for broadcast or NBMA interface types. The object is set to value true (1) to suppress the origination.
.1.3.6.1.2.1.191.1.8,OSPFV3-MIB::ospfv3VirtIfTable,,not-accessible,,current,,Information about this router's virtual interfaces that the OSPFv3 Process is configured to carry on.
.1.3.6.1.2.1.191.1.8.1,OSPFV3-MIB::ospfv3VirtIfEntry,,not-accessible,ospfv3VirtIfAreaId:ospfv3VirtIfNeighbor,current,,Information about a single virtual interface. The information in this table is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.8.1.1,OSPFV3-MIB::ospfv3VirtIfAreaId,Unsigned32,not-accessible,,current,,The transit area that the virtual link traverses. By definition, this is not Area 0.
.1.3.6.1.2.1.191.1.8.1.2,OSPFV3-MIB::ospfv3VirtIfNeighbor,Unsigned32,not-accessible,,current,,The Router ID of the virtual neighbor.
.1.3.6.1.2.1.191.1.8.1.3,OSPFV3-MIB::ospfv3VirtIfIndex,Integer32,read-only,,current,,The local interface index assigned by the OSPFv3 Process to this OSPFv3 virtual interface. It is advertised in Hellos sent over the virtual link and in the router's router-LSAs.
.1.3.6.1.2.1.191.1.8.1.4,OSPFV3-MIB::ospfv3VirtIfInstId,Unsigned32,read-only,,current,,The local Interface Instance ID assigned by the OSPFv3 Process to this OSPFv3 virtual interface.
.1.3.6.1.2.1.191.1.8.1.5,OSPFV3-MIB::ospfv3VirtIfTransitDelay,Unsigned32,read-create,,current,,The estimated number of seconds it takes to transmit a Link State Update packet over this interface.
.1.3.6.1.2.1.191.1.8.1.6,OSPFV3-MIB::ospfv3VirtIfRetransInterval,Unsigned32,read-create,,current,,The number of seconds between link state advertisement retransmissions for adjacencies belonging to this interface. This value is also used when retransmitting database description and Link State Request packets. This value should be well over the expected round-trip time.
.1.3.6.1.2.1.191.1.8.1.7,OSPFV3-MIB::ospfv3VirtIfHelloInterval,Integer32,read-create,,current,,The length of time, in seconds, between the Hello packets that the router sends on the interface. This value must be the same for the virtual neighbor.
.1.3.6.1.2.1.191.1.8.1.8,OSPFV3-MIB::ospfv3VirtIfRtrDeadInterval,Unsigned32,read-create,,current,,The number of seconds that a router's Hello packets have not been seen before its neighbors declare the router down. This should be some multiple of the Hello interval. This value must be the same for the virtual neighbor.
.1.3.6.1.2.1.191.1.8.1.9,OSPFV3-MIB::ospfv3VirtIfState,INTEGER,read-only,,current,down(1):pointToPoint(4),OSPF virtual interface states. The same encoding as the ospfV3IfTable is used.
.1.3.6.1.2.1.191.1.8.1.10,OSPFV3-MIB::ospfv3VirtIfEvents,Counter32,read-only,,current,,The number of state changes or error events on this virtual link. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.8.1.11,OSPFV3-MIB::ospfv3VirtIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.191.1.8.1.12,OSPFV3-MIB::ospfv3VirtIfLinkScopeLsaCount,Gauge32,read-only,,current,,The total number of Link-scope link state advertisements in this virtual link's link state database.
.1.3.6.1.2.1.191.1.8.1.13,OSPFV3-MIB::ospfv3VirtIfLinkLsaCksumSum,Unsigned32,read-only,,current,,The 32-bit unsigned sum of the Link-scope link state advertisements' LS checksums contained in this virtual link's link state database. The sum can be used to determine if there has been a change in a router's link state database or to compare the link state database of two routers.
.1.3.6.1.2.1.191.1.9,OSPFV3-MIB::ospfv3NbrTable,,not-accessible,,current,,A table describing all neighbors in the locality of the OSPFv3 router.
.1.3.6.1.2.1.191.1.9.1,OSPFV3-MIB::ospfv3NbrEntry,,not-accessible,ospfv3NbrIfIndex:ospfv3NbrIfInstId:ospfv3NbrRtrId,current,,The information regarding a single neighbor.
.1.3.6.1.2.1.191.1.9.1.1,OSPFV3-MIB::ospfv3NbrIfIndex,Integer32,not-accessible,,current,,The Local Link ID of the link over which the neighbor can be reached.
.1.3.6.1.2.1.191.1.9.1.2,OSPFV3-MIB::ospfv3NbrIfInstId,Unsigned32,not-accessible,,current,,Interface instance over which the neighbor can be reached. This ID has local link significance only.
.1.3.6.1.2.1.191.1.9.1.3,OSPFV3-MIB::ospfv3NbrRtrId,Unsigned32,not-accessible,,current,,A 32-bit unsigned integer uniquely identifying the neighboring router in the Autonomous System.
.1.3.6.1.2.1.191.1.9.1.4,OSPFV3-MIB::ospfv3NbrAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of ospfv3NbrAddress. Only IPv6 addresses without zone index are expected.
.1.3.6.1.2.1.191.1.9.1.5,OSPFV3-MIB::ospfv3NbrAddress,OCTET,read-only,,current,,The IPv6 address of the neighbor associated with the local link.
.1.3.6.1.2.1.191.1.9.1.6,OSPFV3-MIB::ospfv3NbrOptions,Integer32,read-only,,current,,A bit mask corresponding to the neighbor's options field.
.1.3.6.1.2.1.191.1.9.1.7,OSPFV3-MIB::ospfv3NbrPriority,Integer32,read-only,,current,,The priority of this neighbor in the designated- router election algorithm. The value 0 signifies that the neighbor is not eligible to become the Designated Router on this particular network.
.1.3.6.1.2.1.191.1.9.1.8,OSPFV3-MIB::ospfv3NbrState,INTEGER,read-only,,current,down(1):attempt(2):init(3):twoWay(4):exchangeStart(5):exchange(6):loading(7):full(8),The state of the relationship with this neighbor.
.1.3.6.1.2.1.191.1.9.1.9,OSPFV3-MIB::ospfv3NbrEvents,Counter32,read-only,,current,,The number of times this neighbor relationship has changed state or an error has occurred. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.9.1.10,OSPFV3-MIB::ospfv3NbrLsRetransQLen,Gauge32,read-only,,current,,The current length of the retransmission queue.
.1.3.6.1.2.1.191.1.9.1.11,OSPFV3-MIB::ospfv3NbrHelloSuppressed,INTEGER,read-only,,current,true(1):false(2),Indicates whether Hellos are being suppressed to the neighbor.
.1.3.6.1.2.1.191.1.9.1.12,OSPFV3-MIB::ospfv3NbrIfId,Integer32,read-only,,current,,The Interface ID that the neighbor advertises in its Hello packets on this link, that is, the neighbor's local interface index.
.1.3.6.1.2.1.191.1.9.1.13,OSPFV3-MIB::ospfv3NbrRestartHelperStatus,INTEGER,read-only,,current,notHelping(1):helping(2),Indicates whether the router is acting as a graceful restart helper for the neighbor.
.1.3.6.1.2.1.191.1.9.1.14,OSPFV3-MIB::ospfv3NbrRestartHelperAge,Unsigned32,read-only,,current,,Remaining time in current OSPF graceful restart interval, if the router is acting as a restart helper for the neighbor.
.1.3.6.1.2.1.191.1.9.1.15,OSPFV3-MIB::ospfv3NbrRestartHelperExitReason,INTEGER,read-only,,current,none(1):inProgress(2):completed(3):timedOut(4):topologyChanged(5),Describes the outcome of the last attempt at acting as a graceful restart helper for the neighbor. none: no restart has yet been attempted. inProgress: a restart attempt is currently underway. completed: the last restart completed successfully. timedOut: the last restart timed out. topologyChanged: the last restart was aborted due to a topology change.
.1.3.6.1.2.1.191.1.10,OSPFV3-MIB::ospfv3CfgNbrTable,,not-accessible,,current,,A table describing all configured neighbors. The Configured Neighbors table just gives OSPFv3 information for sending OSPFv3 packets to potential neighbors and is typically used on NBMA and Point-to-Multipoint networks. Once a Hello is received from a neighbor in the Configured Neighbor table, an entry for that neighbor is created in the Neighbor table and adjacency state is maintained there. Neighbors on multi-access or Point-to-Point networks can use multicast addressing, so only Neighbor table entries are created for them.
.1.3.6.1.2.1.191.1.10.1,OSPFV3-MIB::ospfv3CfgNbrEntry,,not-accessible,ospfv3CfgNbrIfIndex:ospfv3CfgNbrIfInstId:ospfv3CfgNbrAddressType:ospfv3CfgNbrAddress,current,,The information regarding a single configured neighbor. The information in this table is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.10.1.1,OSPFV3-MIB::ospfv3CfgNbrIfIndex,Integer32,not-accessible,,current,,The Local Link ID of the link over which the neighbor can be reached.
.1.3.6.1.2.1.191.1.10.1.2,OSPFV3-MIB::ospfv3CfgNbrIfInstId,Unsigned32,not-accessible,,current,,Interface instance over which the neighbor can be reached. This ID has local link significance only.
.1.3.6.1.2.1.191.1.10.1.3,OSPFV3-MIB::ospfv3CfgNbrAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of ospfv3NbrAddress. Only IPv6 addresses without zone index are expected.
.1.3.6.1.2.1.191.1.10.1.4,OSPFV3-MIB::ospfv3CfgNbrAddress,OCTET,not-accessible,,current,,The IPv6 address of the neighbor associated with the local link.
.1.3.6.1.2.1.191.1.10.1.5,OSPFV3-MIB::ospfv3CfgNbrPriority,Integer32,read-create,,current,,The priority of this neighbor in the designated- router election algorithm. The value 0 signifies that the neighbor is not eligible to become the Designated Router on this particular network.
.1.3.6.1.2.1.191.1.10.1.6,OSPFV3-MIB::ospfv3CfgNbrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.191.1.11,OSPFV3-MIB::ospfv3VirtNbrTable,,not-accessible,,current,,A table describing all virtual neighbors.
.1.3.6.1.2.1.191.1.11.1,OSPFV3-MIB::ospfv3VirtNbrEntry,,not-accessible,ospfv3VirtNbrArea:ospfv3VirtNbrRtrId,current,,Virtual neighbor information.
.1.3.6.1.2.1.191.1.11.1.1,OSPFV3-MIB::ospfv3VirtNbrArea,Unsigned32,not-accessible,,current,,The transit area Identifier.
.1.3.6.1.2.1.191.1.11.1.2,OSPFV3-MIB::ospfv3VirtNbrRtrId,Unsigned32,not-accessible,,current,,A 32-bit integer uniquely identifying the neighboring router in the Autonomous System.
.1.3.6.1.2.1.191.1.11.1.3,OSPFV3-MIB::ospfv3VirtNbrIfIndex,Integer32,read-only,,current,,The local Interface ID for the virtual link over which the neighbor can be reached.
.1.3.6.1.2.1.191.1.11.1.4,OSPFV3-MIB::ospfv3VirtNbrIfInstId,Unsigned32,read-only,,current,,The interface instance for the virtual link over which the neighbor can be reached.
.1.3.6.1.2.1.191.1.11.1.5,OSPFV3-MIB::ospfv3VirtNbrAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of ospfv3VirtNbrAddress. Only IPv6 addresses without zone index are expected.
.1.3.6.1.2.1.191.1.11.1.6,OSPFV3-MIB::ospfv3VirtNbrAddress,OCTET,read-only,,current,,The IPv6 address advertised by this virtual neighbor. It must be a global scope address.
.1.3.6.1.2.1.191.1.11.1.7,OSPFV3-MIB::ospfv3VirtNbrOptions,Integer32,read-only,,current,,A bit mask corresponding to the neighbor's options field.
.1.3.6.1.2.1.191.1.11.1.8,OSPFV3-MIB::ospfv3VirtNbrState,INTEGER,read-only,,current,down(1):attempt(2):init(3):twoWay(4):exchangeStart(5):exchange(6):loading(7):full(8),The state of the virtual neighbor relationship.
.1.3.6.1.2.1.191.1.11.1.9,OSPFV3-MIB::ospfv3VirtNbrEvents,Counter32,read-only,,current,,The number of times this virtual link has changed its state or an error has occurred. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ospfv3DiscontinuityTime.
.1.3.6.1.2.1.191.1.11.1.10,OSPFV3-MIB::ospfv3VirtNbrLsRetransQLen,Gauge32,read-only,,current,,The current length of the retransmission queue.
.1.3.6.1.2.1.191.1.11.1.11,OSPFV3-MIB::ospfv3VirtNbrHelloSuppressed,INTEGER,read-only,,current,true(1):false(2),Indicates whether Hellos are being suppressed to the neighbor.
.1.3.6.1.2.1.191.1.11.1.12,OSPFV3-MIB::ospfv3VirtNbrIfId,Integer32,read-only,,current,,The Interface ID that the neighbor advertises in its Hello packets on this virtual link, that is, the neighbor's local Interface ID.
.1.3.6.1.2.1.191.1.11.1.13,OSPFV3-MIB::ospfv3VirtNbrRestartHelperStatus,INTEGER,read-only,,current,notHelping(1):helping(2),Indicates whether the router is acting as a graceful restart helper for the neighbor.
.1.3.6.1.2.1.191.1.11.1.14,OSPFV3-MIB::ospfv3VirtNbrRestartHelperAge,Unsigned32,read-only,,current,,Remaining time in the current OSPF graceful restart interval, if the router is acting as a restart helper for the neighbor.
.1.3.6.1.2.1.191.1.11.1.15,OSPFV3-MIB::ospfv3VirtNbrRestartHelperExitReason,INTEGER,read-only,,current,none(1):inProgress(2):completed(3):timedOut(4):topologyChanged(5),Describes the outcome of the last attempt at acting as a graceful restart helper for the neighbor. none: no restart has yet been attempted. inProgress: a restart attempt is currently underway. completed: the last restart completed successfully. timedOut: the last restart timed out. topologyChanged: the last restart was aborted due to a topology change.
.1.3.6.1.2.1.191.1.12,OSPFV3-MIB::ospfv3AreaAggregateTable,,not-accessible,,current,,The Area Aggregate Table acts as an adjunct to the Area Table. It describes those address aggregates that are configured to be propagated from an area. Its purpose is to reduce the amount of information that is known beyond an area's borders. A range of IPv6 prefixes specified by a prefix / prefix length pair. Note that if ranges are configured such that one range subsumes another range, the most specific match is the preferred one.
.1.3.6.1.2.1.191.1.12.1,OSPFV3-MIB::ospfv3AreaAggregateEntry,,not-accessible,ospfv3AreaAggregateAreaID:ospfv3AreaAggregateAreaLsdbType:ospfv3AreaAggregatePrefixType:ospfv3AreaAggregatePrefix:ospfv3AreaAggregatePrefixLength,current,,A single area aggregate entry. Information in this table is persistent, and when this object is written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.191.1.12.1.1,OSPFV3-MIB::ospfv3AreaAggregateAreaID,Unsigned32,not-accessible,,current,,The area the Address Aggregate is to be found within.
.1.3.6.1.2.1.191.1.12.1.2,OSPFV3-MIB::ospfv3AreaAggregateAreaLsdbType,INTEGER,not-accessible,,current,interAreaPrefixLsa(8195):nssaExternalLsa(8199),The type of the Address Aggregate. This field specifies the Area LSDB type that this Address Aggregate applies to.
.1.3.6.1.2.1.191.1.12.1.3,OSPFV3-MIB::ospfv3AreaAggregatePrefixType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The prefix type of ospfv3AreaAggregatePrefix. Only IPv6 addresses are expected.
.1.3.6.1.2.1.191.1.12.1.4,OSPFV3-MIB::ospfv3AreaAggregatePrefix,OCTET,not-accessible,,current,,The IPv6 prefix.
.1.3.6.1.2.1.191.1.12.1.5,OSPFV3-MIB::ospfv3AreaAggregatePrefixLength,Unsigned32,not-accessible,,current,,The length of the prefix (in bits). A prefix can not be shorter than 3 bits.
.1.3.6.1.2.1.191.1.12.1.6,OSPFV3-MIB::ospfv3AreaAggregateRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified.
.1.3.6.1.2.1.191.1.12.1.7,OSPFV3-MIB::ospfv3AreaAggregateEffect,INTEGER,read-create,,current,advertiseMatching(1):doNotAdvertiseMatching(2),Prefixes subsumed by ranges will either trigger the advertisement of the indicated aggregate (advertiseMatching) or result in the prefix not being advertised at all outside the area.
.1.3.6.1.2.1.191.1.12.1.8,OSPFV3-MIB::ospfv3AreaAggregateRouteTag,Unsigned32,read-create,,current,,This tag is advertised only in the summarized As-External LSA when summarizing from NSSA-LSAs to AS-External-LSAs.
.1.3.6.1.2.1.191.1.13,OSPFV3-MIB::ospfv3VirtLinkLsdbTable,,not-accessible,,current,,The OSPFv3 Process's Link-scope LSDB for virtual interfaces. The LSDB contains the Link-scope link state advertisements from virtual interfaces.
.1.3.6.1.2.1.191.1.13.1,OSPFV3-MIB::ospfv3VirtLinkLsdbEntry,,not-accessible,ospfv3VirtLinkLsdbIfAreaId:ospfv3VirtLinkLsdbIfNeighbor:ospfv3VirtLinkLsdbType:ospfv3VirtLinkLsdbRouterId:ospfv3VirtLinkLsdbLsid,current,,A single Link-scope link state advertisement for a virtual interface.
.1.3.6.1.2.1.191.1.13.1.1,OSPFV3-MIB::ospfv3VirtLinkLsdbIfAreaId,Unsigned32,not-accessible,,current,,The transit area that the virtual link traverses. By definition, this is not Area 0.
.1.3.6.1.2.1.191.1.13.1.2,OSPFV3-MIB::ospfv3VirtLinkLsdbIfNeighbor,Unsigned32,not-accessible,,current,,The Router ID of the virtual neighbor.
.1.3.6.1.2.1.191.1.13.1.3,OSPFV3-MIB::ospfv3VirtLinkLsdbType,Unsigned32,not-accessible,,current,,The type of the link state advertisement. Each link state type has a separate advertisement format. Link-scope LSAs unrecognized by the router are also stored in this database.
.1.3.6.1.2.1.191.1.13.1.4,OSPFV3-MIB::ospfv3VirtLinkLsdbRouterId,Unsigned32,not-accessible,,current,,The 32-bit number that uniquely identifies the originating router in the Autonomous System.
.1.3.6.1.2.1.191.1.13.1.5,OSPFV3-MIB::ospfv3VirtLinkLsdbLsid,Unsigned32,not-accessible,,current,,The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.
.1.3.6.1.2.1.191.1.13.1.6,OSPFV3-MIB::ospfv3VirtLinkLsdbSequence,Integer32,read-only,,current,,The sequence number field is a signed 32-bit integer. It is used to detect old and duplicate link state advertisements. The space of sequence numbers is linearly ordered. The larger the sequence number, the more recent the advertisement.
.1.3.6.1.2.1.191.1.13.1.7,OSPFV3-MIB::ospfv3VirtLinkLsdbAge,Unsigned32,read-only,,current,,This field is the age of the link state advertisement in seconds. The high-order bit of the LS age field is considered the DoNotAge bit for support of on-demand circuits.
.1.3.6.1.2.1.191.1.13.1.8,OSPFV3-MIB::ospfv3VirtLinkLsdbChecksum,Integer32,read-only,,current,,This field is the checksum of the complete contents of the advertisement, excepting the age field. The age field is excepted so that an advertisement's age can be incremented without updating the checksum. The checksum used is the same that is used for ISO connectionless datagrams; it is commonly referred to as the Fletcher checksum.
.1.3.6.1.2.1.191.1.13.1.9,OSPFV3-MIB::ospfv3VirtLinkLsdbAdvertisement,OCTET,read-only,,current,,The entire link state advertisement, including its header.
.1.3.6.1.2.1.191.1.13.1.10,OSPFV3-MIB::ospfv3VirtLinkLsdbTypeKnown,INTEGER,read-only,,current,true(1):false(2),The value true (1) indicates that the LSA type is recognized by this router.
.1.3.6.1.2.1.191.1.14,OSPFV3-MIB::ospfv3NotificationEntry,,,,,,
.1.3.6.1.2.1.191.1.14.1,OSPFV3-MIB::ospfv3ConfigErrorType,INTEGER,accessible-for-notify,,current,badVersion(1):areaMismatch(2):unknownNbmaNbr(3):unknownVirtualNbr(4):helloIntervalMismatch(5):deadIntervalMismatch(6):optionMismatch(7):mtuMismatch(8):duplicateRouterId(9):noError(10),Potential types of configuration conflicts. Used by the ospfv3ConfigError and ospfv3ConfigVirtError notifications.
.1.3.6.1.2.1.191.1.14.2,OSPFV3-MIB::ospfv3PacketType,INTEGER,accessible-for-notify,,current,hello(1):dbDescript(2):lsReq(3):lsUpdate(4):lsAck(5):nullPacket(6),OSPFv3 packet types.
.1.3.6.1.2.1.191.1.14.3,OSPFV3-MIB::ospfv3PacketSrc,OCTET,accessible-for-notify,,current,,The IPv6 address of an inbound packet that cannot be identified by a neighbor instance. Only IPv6 addresses without zone index are expected.
.1.3.6.1.2.1.191.2,OSPFV3-MIB::ospfv3Conformance,,,,,,
.1.3.6.1.2.1.191.2.1,OSPFV3-MIB::ospfv3Groups,,,,,,
.1.3.6.1.2.1.191.2.1.1,OSPFV3-MIB::ospfv3BasicGroup,,,,,,These objects are used for managing/monitoring OSPFv3 global parameters.
.1.3.6.1.2.1.191.2.1.2,OSPFV3-MIB::ospfv3AreaGroup,,,,,,These objects are used for OSPFv3 systems supporting areas.
.1.3.6.1.2.1.191.2.1.3,OSPFV3-MIB::ospfv3AsLsdbGroup,,,,,,These objects are used for OSPFv3 systems that display their AS-scope link state database.
.1.3.6.1.2.1.191.2.1.4,OSPFV3-MIB::ospfv3AreaLsdbGroup,,,,,,These objects are used for OSPFv3 systems that display their Area-scope link state database.
.1.3.6.1.2.1.191.2.1.5,OSPFV3-MIB::ospfv3LinkLsdbGroup,,,,,,These objects are used for OSPFv3 systems that display their Link-scope link state database for non-virtual interfaces.
.1.3.6.1.2.1.191.2.1.6,OSPFV3-MIB::ospfv3HostGroup,,,,,,These objects are used for OSPFv3 systems that support attached hosts.
.1.3.6.1.2.1.191.2.1.7,OSPFV3-MIB::ospfv3IfGroup,,,,,,These interface objects are used for managing/monitoring OSPFv3 interfaces.
.1.3.6.1.2.1.191.2.1.8,OSPFV3-MIB::ospfv3VirtIfGroup,,,,,,These virtual interface objects are used for managing/monitoring OSPFv3 virtual interfaces.
.1.3.6.1.2.1.191.2.1.9,OSPFV3-MIB::ospfv3NbrGroup,,,,,,These neighbor objects are used for managing/monitoring OSPFv3 neighbors.
.1.3.6.1.2.1.191.2.1.10,OSPFV3-MIB::ospfv3CfgNbrGroup,,,,,,These configured neighbor objects are used for managing/monitoring OSPFv3-configured neighbors.
.1.3.6.1.2.1.191.2.1.11,OSPFV3-MIB::ospfv3VirtNbrGroup,,,,,,These virtual neighbor objects are used for managing/monitoring OSPFv3 virtual neighbors.
.1.3.6.1.2.1.191.2.1.12,OSPFV3-MIB::ospfv3AreaAggregateGroup,,,,,,These area aggregate objects are required for aggregating OSPFv3 prefixes for summarization across areas.
.1.3.6.1.2.1.191.2.1.13,OSPFV3-MIB::ospfv3VirtLinkLsdbGroup,,,,,,These objects are used for OSPFv3 systems that display their Link-scope link state database for virtual interfaces.
.1.3.6.1.2.1.191.2.1.14,OSPFV3-MIB::ospfv3NotificationObjectGroup,,,,,,These objects are used to record notification parameters.
.1.3.6.1.2.1.191.2.1.15,OSPFV3-MIB::ospfv3NotificationGroup,,,,,,This group is used for OSPFv3 notifications.
.1.3.6.1.2.1.191.2.2,OSPFV3-MIB::ospfv3Compliances,,,,,,
.1.3.6.1.2.1.191.2.2.1,OSPFV3-MIB::ospfv3FullCompliance,,,,,,The compliance statement
.1.3.6.1.2.1.191.2.2.2,OSPFV3-MIB::ospfv3ReadOnlyCompliance,,,,,,When this MIB module is implemented without support for read-create (i.e., in read-only mode), the implementation can claim read-only compliance. Such a device can then be monitored, but cannot be configured with this MIB.
.1.3.6.1.2.1.192,SYSLOG-MSG-MIB::syslogMsgMib,,,,,,This MIB module represents SYSLOG messages as SNMP objects. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 5676; see the RFC itself for full legal notices.
.1.3.6.1.2.1.192.0,SYSLOG-MSG-MIB::syslogMsgNotifications,,,,,,
.1.3.6.1.2.1.192.0.1,SYSLOG-MSG-MIB::syslogMsgNotification,,,,,,The syslogMsgNotification is generated when a new SYSLOG message is received and the value of syslogMsgGenerateNotifications is true. Implementations may add syslogMsgSDParamValue objects as long as the resulting notification fits into the size constraints imposed by the implementation environment and the notification message size constraints imposed by maxMessageSize [RFC3412] and SNMP transport mappings.
.1.3.6.1.2.1.192.1,SYSLOG-MSG-MIB::syslogMsgObjects,,,,,,
.1.3.6.1.2.1.192.1.1,SYSLOG-MSG-MIB::syslogMsgControl,,,,,,
.1.3.6.1.2.1.192.1.1.1,SYSLOG-MSG-MIB::syslogMsgTableMaxSize,Unsigned32,read-write,,current,,The maximum number of SYSLOG messages that may be held in syslogMsgTable. A particular setting does not guarantee that there is sufficient memory available for the maximum number of table entries indicated by this object. A value of 0 means no fixed limit. If an application reduces the limit while there are SYSLOG messages in the syslogMsgTable, the SYSLOG messages that are in the syslogMsgTable for the longest time MUST be discarded to bring the table down to the new limit. The value of this object should be kept in nonvolatile memory.
.1.3.6.1.2.1.192.1.1.2,SYSLOG-MSG-MIB::syslogMsgEnableNotifications,INTEGER,read-write,,current,true(1):false(2),Indicates whether syslogMsgNotification notifications are generated. The value of this object should be kept in nonvolatile memory.
.1.3.6.1.2.1.192.1.2,SYSLOG-MSG-MIB::syslogMsgTable,,not-accessible,,current,,A table containing recent SYSLOG messages. The size of the table is controlled by the syslogMsgTableMaxSize object.
.1.3.6.1.2.1.192.1.2.1,SYSLOG-MSG-MIB::syslogMsgEntry,,not-accessible,syslogMsgIndex,current,,An entry of the syslogMsgTable.
.1.3.6.1.2.1.192.1.2.1.1,SYSLOG-MSG-MIB::syslogMsgIndex,Unsigned32,not-accessible,,current,,A monotonically increasing number used to identify entries in the syslogMsgTable. When syslogMsgIndex reaches the maximum value (4294967295), the value wraps back to 1. Applications periodically polling the syslogMsgTable for new entries should take into account that a complete rollover of syslogMsgIndex will happen if more than 4294967294 messages are received during a poll interval.
.1.3.6.1.2.1.192.1.2.1.2,SYSLOG-MSG-MIB::syslogMsgFacility,INTEGER,read-only,,current,kern(0):user(1):mail(2):daemon(3):auth(4):syslog(5):lpr(6):news(7):uucp(8):cron(9):authpriv(10):ftp(11):ntp(12):audit(13):console(14):cron2(15):local0(16):local1(17):local2(18):local3(19):local4(20):local5(21):local6(22):local7(23),The facility of the SYSLOG message.
.1.3.6.1.2.1.192.1.2.1.3,SYSLOG-MSG-MIB::syslogMsgSeverity,INTEGER,read-only,,current,emerg(0):alert(1):crit(2):err(3):warning(4):notice(5):info(6):debug(7),The severity of the SYSLOG message
.1.3.6.1.2.1.192.1.2.1.4,SYSLOG-MSG-MIB::syslogMsgVersion,Unsigned32,read-only,,current,,The version of the SYSLOG message. A value of 0 indicates that the version is unknown.
.1.3.6.1.2.1.192.1.2.1.5,SYSLOG-MSG-MIB::syslogMsgTimeStamp,OCTET,read-only,,current,,The timestamp of the SYSLOG message. A zero-length string is returned if the timestamp is unknown.
.1.3.6.1.2.1.192.1.2.1.6,SYSLOG-MSG-MIB::syslogMsgHostName,OCTET,read-only,,current,,The hostname and the (optional) domain name of the SYSLOG message. A zero-length string indicates an unknown hostname. The SYSLOG protocol specification constrains this string to printable US-ASCII code points.
.1.3.6.1.2.1.192.1.2.1.7,SYSLOG-MSG-MIB::syslogMsgAppName,OCTET,read-only,,current,,The app-name of the SYSLOG message. A zero-length string indicates an unknown app-name. The SYSLOG protocol specification constrains this string to printable US-ASCII code points.
.1.3.6.1.2.1.192.1.2.1.8,SYSLOG-MSG-MIB::syslogMsgProcID,OCTET,read-only,,current,,The procid of the SYSLOG message. A zero-length string indicates an unknown procid. The SYSLOG protocol specification constrains this string to printable US-ASCII code points.
.1.3.6.1.2.1.192.1.2.1.9,SYSLOG-MSG-MIB::syslogMsgMsgID,OCTET,read-only,,current,,The msgid of the SYSLOG message. A zero-length string indicates an unknown msgid. The SYSLOG protocol specification constrains this string to printable US-ASCII code points.
.1.3.6.1.2.1.192.1.2.1.10,SYSLOG-MSG-MIB::syslogMsgSDParams,Unsigned32,read-only,,current,,The total number of structured data element parameters carried in the SYSLOG message. This number effectively indicates the number of entries in the syslogMsgSDTable. It can be used, for example, by a notification receiver to determine whether a notification carried all structured data element parameters of a SYSLOG message.
.1.3.6.1.2.1.192.1.2.1.11,SYSLOG-MSG-MIB::syslogMsgMsg,OCTET,read-only,,current,,The message part of the SYSLOG message. The syntax does not impose a size restriction. Implementations of this MIB module may truncate the message part of the SYSLOG message such that it fits into the size constraints imposed by the implementation environment. Such truncations can also happen elsewhere in the SYSLOG forwarding chain. If the first octets contain the value 'EFBBBF'h, then the rest of the message is a UTF-8 string. Since SYSLOG messages may be truncated at arbitrary octet boundaries during forwarding, the message may contain invalid UTF-8 encodings at the end.
.1.3.6.1.2.1.192.1.3,SYSLOG-MSG-MIB::syslogMsgSDTable,,not-accessible,,current,,A table containing structured data elements of SYSLOG messages.
.1.3.6.1.2.1.192.1.3.1,SYSLOG-MSG-MIB::syslogMsgSDEntry,,not-accessible,syslogMsgIndex:syslogMsgSDParamIndex:syslogMsgSDID:syslogMsgSDParamName,current,,An entry of the syslogMsgSDTable.
.1.3.6.1.2.1.192.1.3.1.1,SYSLOG-MSG-MIB::syslogMsgSDParamIndex,Unsigned32,not-accessible,,current,,This object indexes the structured data element parameters contained in a SYSLOG message. The first structured data element parameter has the index value 1, and subsequent parameters are indexed by incrementing the index of the previous parameter. The index increases across structured data element boundaries so that the value reflects the position of a structured data element parameter in a SYSLOG message.
.1.3.6.1.2.1.192.1.3.1.2,SYSLOG-MSG-MIB::syslogMsgSDID,OCTET,not-accessible,,current,,The name (SD-ID) of a structured data element. The SYSLOG protocol specification constrains this string to printable US-ASCII code points.
.1.3.6.1.2.1.192.1.3.1.3,SYSLOG-MSG-MIB::syslogMsgSDParamName,OCTET,not-accessible,,current,,The name of a parameter of the structured data element. The SYSLOG protocol specification constrains this string to printable US-ASCII code points.
.1.3.6.1.2.1.192.1.3.1.4,SYSLOG-MSG-MIB::syslogMsgSDParamValue,OCTET,read-only,,current,,The value of the parameter of a SYSLOG message identified by the index of this table. The value is stored in the unescaped format.
.1.3.6.1.2.1.192.2,SYSLOG-MSG-MIB::syslogMsgConformance,,,,,,
.1.3.6.1.2.1.192.2.1,SYSLOG-MSG-MIB::syslogMsgGroups,,,,,,
.1.3.6.1.2.1.192.2.1.1,SYSLOG-MSG-MIB::syslogMsgNotificationGroup,,,,,,The notifications emitted by this MIB module.
.1.3.6.1.2.1.192.2.1.2,SYSLOG-MSG-MIB::syslogMsgGroup,,,,,,A collection of objects representing a SYSLOG message, excluding structured data elements.
.1.3.6.1.2.1.192.2.1.3,SYSLOG-MSG-MIB::syslogMsgSDGroup,,,,,,A collection of objects representing the structured data elements of a SYSLOG message.
.1.3.6.1.2.1.192.2.1.4,SYSLOG-MSG-MIB::syslogMsgControlGroup,,,,,,A collection of control objects to control the size of the syslogMsgTable and to enable/disable notifications.
.1.3.6.1.2.1.192.2.2,SYSLOG-MSG-MIB::syslogMsgCompliances,,,,,,
.1.3.6.1.2.1.192.2.2.1,SYSLOG-MSG-MIB::syslogMsgFullCompliance,,,,,,The compliance statement for implementations of the SYSLOG-MSG-MIB.
.1.3.6.1.2.1.192.2.2.2,SYSLOG-MSG-MIB::syslogMsgReadOnlyCompliance,,,,,,The compliance statement for implementations of the SYSLOG-MSG-MIB that do not support read-write access.
.1.3.6.1.2.1.192.2.2.3,SYSLOG-MSG-MIB::syslogMsgNotificationCompliance,,,,,,The compliance statement for implementations of the SYSLOG-MSG-MIB that do only generate notifications and do not provide a table to allow read access to SYSLOG message details.
.1.3.6.1.2.1.193,IPFIX-MIB::ipfixMIB,,,,,,The IPFIX MIB defines managed objects for IP Flow Information eXport. These objects provide information about managed nodes supporting the IPFIX protocol, for Exporters as well as for Collectors. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.193.1,IPFIX-MIB::ipfixObjects,,,,,,
.1.3.6.1.2.1.193.1.1,IPFIX-MIB::ipfixMainObjects,,,,,,
.1.3.6.1.2.1.193.1.1.1,IPFIX-MIB::ipfixTransportSessionTable,,not-accessible,,current,,This table lists the currently established Transport Sessions between an Exporting Process and a Collecting Process.
.1.3.6.1.2.1.193.1.1.1.1,IPFIX-MIB::ipfixTransportSessionEntry,,not-accessible,ipfixTransportSessionIndex,current,,Defines an entry in the ipfixTransportSessionTable.
.1.3.6.1.2.1.193.1.1.1.1.1,IPFIX-MIB::ipfixTransportSessionIndex,Unsigned32,not-accessible,,current,,Locally arbitrary, but unique identifier of an entry in the ipfixTransportSessionTable. The value is expected to remain constant from a re-initialization of the entity's network management agent to the next re-initialization.
.1.3.6.1.2.1.193.1.1.1.1.2,IPFIX-MIB::ipfixTransportSessionProtocol,Unsigned32,read-only,,current,,The transport protocol used for receiving or transmitting IPFIX Messages. Protocol numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/assignments/protocol-numbers/>.
.1.3.6.1.2.1.193.1.1.1.1.3,IPFIX-MIB::ipfixTransportSessionSourceAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2),The type of address used for the source address, as specified in RFC 4001. The InetAddressType supported values are ipv4(1) and ipv6(2). This object is used with protocols (specified in ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that have the notion of addresses. SCTP (132) should use the ipfixTransportSessionSctpAssocId instead. If SCTP (132) or any other protocol without the notion of addresses is used, the object MUST be set to unknown(0).
.1.3.6.1.2.1.193.1.1.1.1.4,IPFIX-MIB::ipfixTransportSessionSourceAddress,OCTET,read-only,,current,,The source address of the Exporter of the IPFIX Transport Session. This value is interpreted according to the value of ipfixTransportSessionAddressType, as specified in RFC 4001. This object is used with protocols (specified in ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that have the notion of addresses. SCTP (132) should use the ipfixTransportSessionSctpAssocId instead. If SCTP (132) or any other protocol without the notion of addresses is used, the object MUST be set to a zero-length string.
.1.3.6.1.2.1.193.1.1.1.1.5,IPFIX-MIB::ipfixTransportSessionDestinationAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2),The type of address used for the destination address, as specified in RFC 4001. The InetAddressType supported values are ipv4(1) and ipv6(2). This object is used with protocols (specified in ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that have the notion of addresses. SCTP (132) should use the ipfixTransportSessionSctpAssocId instead. If SCTP (132) or any other protocol without the notion of addresses is used, the object MUST be set to unknown(0).
.1.3.6.1.2.1.193.1.1.1.1.6,IPFIX-MIB::ipfixTransportSessionDestinationAddress,OCTET,read-only,,current,,The destination address of the Collector of the IPFIX Transport Session. This value is interpreted according to the value of ipfixTransportSessionAddressType, as specified in RFC 4001. This object is used with protocols (specified in ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that have the notion of addresses. SCTP (132) should use the ipfixTransportSessionSctpAssocId instead. If SCTP (132) or any other protocol without the notion of addresses is used, the object MUST be set to a zero-length string.
.1.3.6.1.2.1.193.1.1.1.1.7,IPFIX-MIB::ipfixTransportSessionSourcePort,Unsigned32,read-only,,current,,The transport protocol port number of the Exporter. This object is used with protocols (specified in ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that have the notion of ports. SCTP (132) should copy the value of sctpAssocLocalPort if the Transport Session is in collecting mode or sctpAssocRemPort if the Transport Session is in exporting mode. The association is referenced by the ipfixTransportSessionSctpAssocId. If any other protocol without the notion of ports is used, the object MUST be set to zero.
.1.3.6.1.2.1.193.1.1.1.1.8,IPFIX-MIB::ipfixTransportSessionDestinationPort,Unsigned32,read-only,,current,,The transport protocol port number of the Collector. The default value is 4739 for all currently defined transport protocol types. This object is used with protocols (specified in ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that have the notion of ports. SCTP (132) should copy the value of sctpAssocRemPort if the Transport Session is in collecting mode or sctpAssocLocalPort if the Transport Session is in exporting mode. The association is referenced by the ipfixTransportSessionSctpAssocId. If any other protocol without the notion of ports is used, the object MUST be set to zero.
.1.3.6.1.2.1.193.1.1.1.1.9,IPFIX-MIB::ipfixTransportSessionSctpAssocId,Unsigned32,read-only,,current,,The association ID used for the SCTP session between the Exporter and the Collector of the IPFIX Transport Session. It is equal to the sctpAssocId entry in the sctpAssocTable defined in the SCTP MIB. This object is only valid if ipfixTransportSessionProtocol has the value 132 (SCTP). In all other cases, the value MUST be zero.
.1.3.6.1.2.1.193.1.1.1.1.10,IPFIX-MIB::ipfixTransportSessionDeviceMode,INTEGER,read-only,,current,exporting(1):collecting(2),The mode of operation of the device for the given Transport Session. This object can have the following values: exporting(1) This value MUST be used if the Transport Session is used for exporting Records to other IPFIX Devices; i.e., this device acts as Exporter. collecting(2) This value MUST be used if the Transport Session is used for collecting Records from other IPFIX Devices; i.e., this device acts as Collector.
.1.3.6.1.2.1.193.1.1.1.1.11,IPFIX-MIB::ipfixTransportSessionTemplateRefreshTimeout,Unsigned32,read-only,,current,,On Exporters, this object contains the time in seconds after which IPFIX Templates are resent by the Exporter. On Collectors, this object contains the lifetime in seconds after which a Template becomes invalid when it is not received again within this lifetime. This object is only valid if ipfixTransportSessionProtocol has the value 17 (UDP). In all other cases, the value MUST be zero.
.1.3.6.1.2.1.193.1.1.1.1.12,IPFIX-MIB::ipfixTransportSessionOptionsTemplateRefreshTimeout,Unsigned32,read-only,,current,,On Exporters, this object contains the time in seconds after which IPFIX Options Templates are resent by the Exporter. On Collectors, this object contains the lifetime in seconds after which an Options Template becomes invalid when it is not received again within this lifetime. This object is only valid if ipfixTransportSessionProtocol has the value 17 (UDP). In all other cases, the value MUST be zero.
.1.3.6.1.2.1.193.1.1.1.1.13,IPFIX-MIB::ipfixTransportSessionTemplateRefreshPacket,Unsigned32,read-only,,current,,On Exporters, this object contains the number of exported IPFIX Messages after which IPFIX Templates are resent by the Exporter. On Collectors, this object contains the lifetime in number of exported IPFIX Messages after which a Template becomes invalid when it is not received again within this lifetime. This object is only valid if ipfixTransportSessionProtocol has the value 17 (UDP). In all other cases, the value MUST be zero.
.1.3.6.1.2.1.193.1.1.1.1.14,IPFIX-MIB::ipfixTransportSessionOptionsTemplateRefreshPacket,Unsigned32,read-only,,current,,On Exporters, this object contains the number of exported IPFIX Messages after which IPFIX Options Templates are resent by the Exporter. On Collectors, this object contains the lifetime in number of exported IPFIX Messages after which an Options Template becomes invalid when it is not received again within this lifetime. This object is only valid if ipfixTransportSessionProtocol has the value 17 (UDP). In all other cases, the value MUST be zero.
.1.3.6.1.2.1.193.1.1.1.1.15,IPFIX-MIB::ipfixTransportSessionIpfixVersion,Unsigned32,read-only,,current,,On Exporters, the object contains the version number of the IPFIX protocol that the Exporter uses to export its data in this Transport Session. On Collectors, the object contains the version number of the IPFIX protocol it receives for this Transport Session. If IPFIX Messages of different IPFIX protocol versions are transmitted or received in this Transport Session, this object contains the maximum version number.
.1.3.6.1.2.1.193.1.1.1.1.16,IPFIX-MIB::ipfixTransportSessionStatus,INTEGER,read-only,,current,unknown(0):inactive(1):active(2),The status of a Transport Session. This object can have the following values: unknown(0) This value MUST be used if the status of the Transport Session cannot be detected by the equipment. This value should be avoided as far as possible. inactive(1) This value MUST be used for Transport Sessions that are specified in the system but are not currently active. The value can be used, for example, for Transport Sessions that are backup (secondary) sessions in a Transport Session group. active(2) This value MUST be used for Transport Sessions that are currently active and transmitting or receiving data.
.1.3.6.1.2.1.193.1.1.2,IPFIX-MIB::ipfixTemplateTable,,not-accessible,,current,,This table lists the Templates and Options Templates that are transmitted by the Exporting Process or received by the Collecting Process. The table contains the Templates and Options Templates that are received or used for exporting data for a given Transport Session group and Observation Domain. Withdrawn or invalidated (Options) Templates MUST be removed from this table.
.1.3.6.1.2.1.193.1.1.2.1,IPFIX-MIB::ipfixTemplateEntry,,not-accessible,ipfixTransportSessionIndex:ipfixTemplateObservationDomainId:ipfixTemplateId,current,,Defines an entry in the ipfixTemplateTable.
.1.3.6.1.2.1.193.1.1.2.1.1,IPFIX-MIB::ipfixTemplateObservationDomainId,Unsigned32,not-accessible,,current,,The ID of the Observation Domain for which this Template is defined. This value is used when sending IPFIX Messages. The special value of 0 indicates that the Data Records exported with this (Options Template) cannot be applied to a single Observation Domain.
.1.3.6.1.2.1.193.1.1.2.1.2,IPFIX-MIB::ipfixTemplateId,Unsigned32,not-accessible,,current,,This number indicates the Template ID in the IPFIX Message. Values from 0 to 255 are not allowed for Template IDs.
.1.3.6.1.2.1.193.1.1.2.1.3,IPFIX-MIB::ipfixTemplateSetId,Unsigned32,read-only,,current,,This number indicates the Set ID of the Template. This object allows the Template type to be easily retrieved. Currently, there are two values defined. The value 2 is used for Sets containing Template definitions. The value 3 is used for Sets containing Options Template definitions.
.1.3.6.1.2.1.193.1.1.2.1.4,IPFIX-MIB::ipfixTemplateAccessTime,OCTET,read-only,,current,,If the Transport Session is in exporting mode (ipfixTransportSessionDeviceMode) the time when this (Options) Template was last sent to the Collector(s). In the specific case of UDP as transport protocol, this time is used to know when a retransmission of the (Options) Template is needed. If the Transport Session is in collecting mode, this object contains the time when this (Options) Template was last received from the Exporter. In the specific case of UDP as transport protocol, this time is used to know when this (Options) Template times out and thus is no longer valid.
.1.3.6.1.2.1.193.1.1.3,IPFIX-MIB::ipfixTemplateDefinitionTable,,not-accessible,,current,,On Exporters, this table lists the (Options) Template fields of which a (Options) Template is defined. It defines the (Options) Template given in the ipfixTemplateId specified in the ipfixTemplateTable. On Collectors, this table lists the (Options) Template fields of which a (Options) Template is defined. It defines the (Options) Template given in the ipfixTemplateId specified in the ipfixTemplateTable.
.1.3.6.1.2.1.193.1.1.3.1,IPFIX-MIB::ipfixTemplateDefinitionEntry,,not-accessible,ipfixTransportSessionIndex:ipfixTemplateObservationDomainId:ipfixTemplateId:ipfixTemplateDefinitionIndex,current,,Defines an entry in the ipfixTemplateDefinitionTable.
.1.3.6.1.2.1.193.1.1.3.1.1,IPFIX-MIB::ipfixTemplateDefinitionIndex,Unsigned32,not-accessible,,current,,The ipfixTemplateDefinitionIndex specifies the order in which the Information Elements are used in the (Options) Template Record. Since a Template Record can contain a maximum of 65535 Information Elements, the index is limited to this value.
.1.3.6.1.2.1.193.1.1.3.1.2,IPFIX-MIB::ipfixTemplateDefinitionIeId,Unsigned32,read-only,,current,,This indicates the Information Element ID at position ipfixTemplateDefinitionIndex in the (Options) Template ipfixTemplateId. This implicitly specifies the data type of the Information Element. The elements are registered at IANA. A current list of assignments can be found at <http://www.iana.org/assignments/ipfix/>.
.1.3.6.1.2.1.193.1.1.3.1.3,IPFIX-MIB::ipfixTemplateDefinitionIeLength,Unsigned32,read-only,,current,,This indicates the length of the Information Element ID at position ipfixTemplateDefinitionIndex in the (Options) Template ipfixTemplateId.
.1.3.6.1.2.1.193.1.1.3.1.4,IPFIX-MIB::ipfixTemplateDefinitionEnterpriseNumber,Unsigned32,read-only,,current,,IANA enterprise number of the authority defining the Information Element identifier in this Template Record. Enterprise numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/assignments/enterprise-numbers/>. This object must be zero(0) for all standard Information Elements registered with IANA. A current list of these elements is available from <http://www.iana.org/assignments/ipfix/>.
.1.3.6.1.2.1.193.1.1.3.1.5,IPFIX-MIB::ipfixTemplateDefinitionFlags,BITS,read-only,,current,scope(0):flowKey(1),This bitmask indicates special attributes for the Information Element: scope(0) This Information Element is used for scope. flowKey(1) This Information Element is a Flow Key. Thus, we get the following values for an Information Element: If neither bit scope(0) nor bit flowKey(1) is set The Information Element is neither used for scoping nor as Flow Key. If only bit scope(0) is set The Information Element is used for scoping. If only bit flowKey(1) is set The Information Element is used as Flow Key. Both bit scope(0) and flowKey(1) MUST NOT be set at the same time. This combination is not allowed.
.1.3.6.1.2.1.193.1.1.4,IPFIX-MIB::ipfixExportTable,,not-accessible,,current,,This table lists all exports of an IPFIX Device. On Exporters, this table contains all exports grouped by Transport Session, Observation Domain ID, Template ID, and Metering Process represented by the ipfixMeteringProcessCacheId. Thanks to the ipfixExportIndex, the exports can group one or more Transport Sessions to achieve a special functionality like failover management, load-balancing, etc. The entries with the same ipfixExportIndex, ipfixObservationDomainId, and ipfixMeteringProcessCacheId define a Transport Session group. If the Exporter does not use Transport Session grouping, then each ipfixExportIndex contains a single ipfixMeteringProcessCacheId, and thus a single Transport Session; this session MUST have a member type value of primary(1). Transport Sessions referenced in this table MUST have a ipfixTransportSessionDeviceMode value of exporting(1). On Collectors, this table is not needed.
.1.3.6.1.2.1.193.1.1.4.1,IPFIX-MIB::ipfixExportEntry,,not-accessible,ipfixExportIndex:ipfixMeteringProcessCacheId:ipfixTransportSessionIndex,current,,Defines an entry in the ipfixExportTable.
.1.3.6.1.2.1.193.1.1.4.1.1,IPFIX-MIB::ipfixExportIndex,Unsigned32,not-accessible,,current,,Locally arbitrary, but unique identifier of an entry in the ipfixExportTable. The value is expected to remain constant from a re-initialization of the entity's network management agent to the next re-initialization. A common ipfixExportIndex between two entries from this table indicates that there is a relationship between the Transport Sessions in ipfixTransportSessionIndex. The type of relationship is expressed by the value of ipfixExportMemberType.
.1.3.6.1.2.1.193.1.1.4.1.2,IPFIX-MIB::ipfixExportMemberType,INTEGER,read-only,,current,unknown(0):primary(1):secondary(2):parallel(3):loadBalancing(4),The type of member Transport Session in a Transport Session group (identified by the value of ipfixExportIndex, ipfixObservationDomainId, and ipfixMeteringProcessCacheId). The following values are valid: unknown(0) This value MUST be used if the status of the group membership cannot be detected by the equipment. This value should be avoided as far as possible. primary(1) This value is used for a group member that is used as the primary target of an Exporter. Other group members (with the same ipfixExportIndex and ipfixMeteringProcessCacheId) MUST NOT have the value primary(1) but MUST have the value secondary(2). This value MUST also be specified if the Exporter does not support Transport Session grouping. In this case, the group contains only one Transport Session. secondary(2) This value is used for a group member that is used as a secondary target of an Exporter. The Exporter will use one of the targets specified as secondary(2) within the same Transport Session group when the primary target is not reachable. parallel(3) This value is used for a group member that is used for duplicate exporting (i.e., all group members identified by the ipfixExportIndex are exporting the same Records in parallel). This implies that all group members MUST have the same member type (i.e., parallel(3)). loadBalancing(4) This value is used for a group member that is used as one target for load-balancing. This means that a Record is sent to one of the group members in this group identified by ipfixExportIndex. This implies that all group members MUST have the same member type (i.e., loadBalancing(4)).
.1.3.6.1.2.1.193.1.1.5,IPFIX-MIB::ipfixMeteringProcessTable,,not-accessible,,current,,This table lists so-called caches used at the Metering Process to store the metering data of Flows observed at the Observation Points given in the ipfixObservationPointGroupReference. The table lists the timeouts that specify when the cached metering data is expired. On Collectors, the table is not needed.
.1.3.6.1.2.1.193.1.1.5.1,IPFIX-MIB::ipfixMeteringProcessEntry,,not-accessible,ipfixMeteringProcessCacheId,current,,Defines an entry in the ipfixMeteringProcessTable.
.1.3.6.1.2.1.193.1.1.5.1.1,IPFIX-MIB::ipfixMeteringProcessCacheId,Unsigned32,not-accessible,,current,,Locally arbitrary, but unique identifier of an entry in the ipfixMeteringProcessTable. The value is expected to remain constant from a re-initialization of the entity's network management agent to the next re-initialization.
.1.3.6.1.2.1.193.1.1.5.1.2,IPFIX-MIB::ipfixMeteringProcessObservationPointGroupRef,Unsigned32,read-only,,current,,The Observation Point Group ID that links this table entry to the ipfixObservationPointTable. The matching ipfixObservationPointGroupId in that table gives the Observation Points used in that cache. If the Observation Points are unknown, the ipfixMeteringProcessObservationPointGroupRef MUST be zero.
.1.3.6.1.2.1.193.1.1.5.1.3,IPFIX-MIB::ipfixMeteringProcessCacheActiveTimeout,Unsigned32,read-only,,current,,On the Exporter, this object contains the time after which a Flow is expired (and a Data Record for the Template is sent), even though packets matching this Flow are still received by the Metering Process. If this value is 0, the Flow is not prematurely expired.
.1.3.6.1.2.1.193.1.1.5.1.4,IPFIX-MIB::ipfixMeteringProcessCacheIdleTimeout,Unsigned32,read-only,,current,,On the Exporter, this object contains the time after which a Flow is expired (and a Data Record for the Template is sent) when no packets matching this Flow are received by the Metering Process for the given number of seconds. If this value is zero, the Flow is expired immediately; i.e., a Data Record is sent for every packet received by the Metering Process.
.1.3.6.1.2.1.193.1.1.6,IPFIX-MIB::ipfixObservationPointTable,,not-accessible,,current,,This table lists the Observation Points used within an Exporter by the Metering Process. The index ipfixObservationPointGroupId groups Observation Points and is referenced in the Metering Process table. On Collectors, this table is not needed.
.1.3.6.1.2.1.193.1.1.6.1,IPFIX-MIB::ipfixObservationPointEntry,,not-accessible,ipfixObservationPointGroupId:ipfixObservationPointIndex,current,,Defines an entry in the ipfixObservationPointTable.
.1.3.6.1.2.1.193.1.1.6.1.1,IPFIX-MIB::ipfixObservationPointGroupId,Unsigned32,not-accessible,,current,,Locally arbitrary, but unique identifier of an entry in the ipfixObservationPointTable. The value is expected to remain constant from a re-initialization of the entity's network management agent to the next re-initialization. This index represents a group of Observation Points. The special value of 0 MUST NOT be used within this table but is reserved for usage in the ipfixMeteringProcessTable. An index of 0 for the ipfixObservationPointGroupReference index in that table indicates that an Observation Point is unknown or unspecified for a Metering Process cache.
.1.3.6.1.2.1.193.1.1.6.1.2,IPFIX-MIB::ipfixObservationPointIndex,Unsigned32,not-accessible,,current,,Locally arbitrary, but unique identifier of an entry in the ipfixObservationPointTable. The value is expected to remain constant from a re-initialization of the entity's network management agent to the next re-initialization. This index represents a single Observation Point in an Observation Point group.
.1.3.6.1.2.1.193.1.1.6.1.3,IPFIX-MIB::ipfixObservationPointObservationDomainId,Unsigned32,read-only,,current,,The ID of the Observation Domain in which this Observation Point is included. The special value of 0 indicates that the Observation Points within this group cannot be applied to a single Observation Domain.
.1.3.6.1.2.1.193.1.1.6.1.4,IPFIX-MIB::ipfixObservationPointPhysicalEntity,Integer32,read-only,,current,,This object contains the index of a physical entity in the ENTITY MIB. This physical entity is the given Observation Point. If such a physical entity cannot be specified or is not known, then the object is zero.
.1.3.6.1.2.1.193.1.1.6.1.5,IPFIX-MIB::ipfixObservationPointPhysicalInterface,Integer32,read-only,,current,,This object contains the index of a physical interface in the Interfaces MIB. This physical interface is the given Observation Point. If such a physical interface cannot be specified or is not known, then the object is zero. This object MAY be used alone or in addition to ipfixObservationPointPhysicalEntity. If ipfixObservationPointPhysicalEntity is not zero, this object MUST point to the same physical interface that is referenced in ipfixObservationPointPhysicalEntity. Otherwise, it may reference any interface in the Interfaces MIB.
.1.3.6.1.2.1.193.1.1.6.1.6,IPFIX-MIB::ipfixObservationPointPhysicalEntityDirection,INTEGER,read-only,,current,unknown(0):ingress(1):egress(2):both(3),The direction of the Flow that is monitored on the given physical entity. The following values are valid: unknown(0) This value MUST be used if a direction is not known for the given physical entity. ingress(1) This value is used for monitoring incoming Flows on the given physical entity. egress(2) This value is used for monitoring outgoing Flows on the given physical entity. both(3) This value is used for monitoring incoming and outgoing Flows on the given physical entity.
.1.3.6.1.2.1.193.1.1.7,IPFIX-MIB::ipfixSelectionProcessTable,,not-accessible,,current,,This table contains Selector Functions connected to a Metering Process by the index ipfixMeteringProcessCacheId. The Selector Functions are grouped into Selection Processes by the ipfixSelectionProcessIndex. The Selector Functions are applied within the Selection Process to the packets observed for the given Metering Process cache in increasing order as indicated by the ipfixSelectionProcessSelectorIndex. This means Selector Functions with a lower ipfixSelectionProcessSelectorIndex are applied first. The remaining packets are accounted for in Flow Records. Since IPFIX does not define any Selector Function (except selecting every packet), this is a placeholder for future use and a guideline for implementing enterprise-specific Selector Function objects. The following object tree should help the reader visualize how the Selector Function objects should be implemented: ipfixSelectorFunctions | +- ipfixFuncSelectAll | | | +- ipfixFuncSelectAllAvail (is the function available?) | +- ipfixFuncF2 | | | +- ipfixFuncF2Avail (is the function F2 available?) | | | +- ipfixFuncF2Parameters (a table with parameters) ... | +- ipfixFuncFn... If a Selector Function takes parameters, the MIB should contain a table with an entry for each set of parameters used at the Exporter.
.1.3.6.1.2.1.193.1.1.7.1,IPFIX-MIB::ipfixSelectionProcessEntry,,not-accessible,ipfixMeteringProcessCacheId:ipfixSelectionProcessIndex:ipfixSelectionProcessSelectorIndex,current,,Defines an entry in the ipfixSelectionProcessTable.
.1.3.6.1.2.1.193.1.1.7.1.1,IPFIX-MIB::ipfixSelectionProcessIndex,Unsigned32,not-accessible,,current,,Locally arbitrary, but unique identifier of an entry in the ipfixSelectionProcessTable. The value is expected to remain constant from a re-initialization of the entity's network management agent to the next re-initialization.
.1.3.6.1.2.1.193.1.1.7.1.2,IPFIX-MIB::ipfixSelectionProcessSelectorIndex,Unsigned32,not-accessible,,current,,Index specifying the order in which the referenced ipfixSelectionProcessSelectorFunctions are applied to the observed packet stream within the given Selection Process (identified by the ipfixSelectionProcessIndex). The Selector Functions are applied in increasing order; i.e., Selector Functions with a lower index are applied first.
.1.3.6.1.2.1.193.1.1.7.1.3,IPFIX-MIB::ipfixSelectionProcessSelectorFunction,OBJECT,read-only,,current,,The pointer to the Selector Function used at position ipfixSelectionProcessSelectorIndex in the list of Selector Functions for the Metering Process cache specified by the index ipfixMeteringProcessCacheId and for the given Selection Process (identified by the ipfixSelectionProcessIndex). This usually points to an object in the IPFIX SELECTOR MIB. If the Selector Function does not take parameters, then it MUST point to the root of the function subtree. If the function takes parameters, then it MUST point to an entry in the parameter table of the Selector Function.
.1.3.6.1.2.1.193.1.2,IPFIX-MIB::ipfixStatistics,,,,,,
.1.3.6.1.2.1.193.1.2.1,IPFIX-MIB::ipfixTransportSessionStatsTable,,not-accessible,,current,,This table lists Transport Session statistics between Exporting Processes and Collecting Processes.
.1.3.6.1.2.1.193.1.2.1.1,IPFIX-MIB::ipfixTransportSessionStatsEntry,,not-accessible,,current,,Defines an entry in the ipfixTransportSessionStatsTable.
.1.3.6.1.2.1.193.1.2.1.1.1,IPFIX-MIB::ipfixTransportSessionRate,Gauge32,read-only,,current,,The number of bytes per second received by the Collector or transmitted by the Exporter. A value of zero (0) means that no packets were sent or received yet. This object is updated every second.
.1.3.6.1.2.1.193.1.2.1.1.2,IPFIX-MIB::ipfixTransportSessionPackets,Counter64,read-only,,current,,The number of packets received by the Collector or transmitted by the Exporter. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.3,IPFIX-MIB::ipfixTransportSessionBytes,Counter64,read-only,,current,,The number of bytes received by the Collector or transmitted by the Exporter. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.4,IPFIX-MIB::ipfixTransportSessionMessages,Counter64,read-only,,current,,The number of IPFIX Messages received by the Collector or transmitted by the Exporter. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.5,IPFIX-MIB::ipfixTransportSessionDiscardedMessages,Counter64,read-only,,current,,The number of received IPFIX Messages that are malformed, cannot be decoded, are received in the wrong order, or are missing according to the sequence number. If used at the Exporter, the number of messages that could not be sent due to, for example, internal buffer overflows, network congestion, or routing issues. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.6,IPFIX-MIB::ipfixTransportSessionRecords,Counter64,read-only,,current,,The number of Data Records received by the Collector or transmitted by the Exporter. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.7,IPFIX-MIB::ipfixTransportSessionTemplates,Counter64,read-only,,current,,The number of Templates received or transmitted. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.8,IPFIX-MIB::ipfixTransportSessionOptionsTemplates,Counter64,read-only,,current,,The number of Options Templates received or transmitted. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTransportSessionDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.1.1.9,IPFIX-MIB::ipfixTransportSessionDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent occasion at which one or more of the Transport Session counters suffered a discontinuity. A value of zero indicates that no such discontinuity has occurred since the last re-initialization of the local management subsystem.
.1.3.6.1.2.1.193.1.2.2,IPFIX-MIB::ipfixTemplateStatsTable,,not-accessible,,current,,This table lists statistics objects per Template.
.1.3.6.1.2.1.193.1.2.2.1,IPFIX-MIB::ipfixTemplateStatsEntry,,not-accessible,,current,,Defines an entry in the ipfixTemplateStatsTable.
.1.3.6.1.2.1.193.1.2.2.1.1,IPFIX-MIB::ipfixTemplateDataRecords,Counter64,read-only,,current,,The number of Data Records that are transmitted or received per Template. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixTemplateDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.2.1.2,IPFIX-MIB::ipfixTemplateDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent occasion at which the Template counter suffered a discontinuity. A value of zero indicates that no such discontinuity has occurred since the last re-initialization of the local management subsystem.
.1.3.6.1.2.1.193.1.2.3,IPFIX-MIB::ipfixMeteringProcessStatsTable,,not-accessible,,current,,This table lists statistics objects that have data per Metering Process cache. On Collectors, this table is not needed.
.1.3.6.1.2.1.193.1.2.3.1,IPFIX-MIB::ipfixMeteringProcessStatsEntry,,not-accessible,,current,,Defines an entry in the ipfixMeteringProcessStatsTable.
.1.3.6.1.2.1.193.1.2.3.1.1,IPFIX-MIB::ipfixMeteringProcessCacheActiveFlows,Gauge32,read-only,,current,,The number of Flows currently active at this cache.
.1.3.6.1.2.1.193.1.2.3.1.2,IPFIX-MIB::ipfixMeteringProcessCacheUnusedCacheEntries,Gauge32,read-only,,current,,The number of unused cache entries.
.1.3.6.1.2.1.193.1.2.3.1.3,IPFIX-MIB::ipfixMeteringProcessCacheDataRecords,Counter64,read-only,,current,,The number of Data Records generated. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixMeteringProcessCacheDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.3.1.4,IPFIX-MIB::ipfixMeteringProcessCacheDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent occasion at which the Metering Process counter suffered a discontinuity. A value of zero indicates that no such discontinuity has occurred since the last re-initialization of the local management subsystem.
.1.3.6.1.2.1.193.1.2.4,IPFIX-MIB::ipfixSelectionProcessStatsTable,,not-accessible,,current,,This table contains statistics for the Selector Functions connected to a Metering Process by the index ipfixMeteringProcessCacheId. The indexes MUST match an entry in the ipfixSelectionProcessTable.
.1.3.6.1.2.1.193.1.2.4.1,IPFIX-MIB::ipfixSelectionProcessStatsEntry,,not-accessible,,current,,Defines an entry in the ipfixSelectionProcessStatsTable.
.1.3.6.1.2.1.193.1.2.4.1.1,IPFIX-MIB::ipfixSelectionProcessStatsPacketsObserved,Counter64,read-only,,current,,The number of packets observed at the entry point of the function. The entry point may be the Observation Point or the exit point of another Selector Function. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixSelectionProcessStatsDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.4.1.2,IPFIX-MIB::ipfixSelectionProcessStatsPacketsDropped,Counter64,read-only,,current,,The number of packets dropped while selecting packets. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of ipfixSelectionProcessStatsDiscontinuityTime.
.1.3.6.1.2.1.193.1.2.4.1.3,IPFIX-MIB::ipfixSelectionProcessStatsDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the most recent occasion at which one or more of the Selector counters suffered a discontinuity. A value of zero indicates that no such discontinuity has occurred since the last re-initialization of the local management subsystem.
.1.3.6.1.2.1.193.2,IPFIX-MIB::ipfixConformance,,,,,,
.1.3.6.1.2.1.193.2.1,IPFIX-MIB::ipfixCompliances,,,,,,
.1.3.6.1.2.1.193.2.1.1,IPFIX-MIB::ipfixCollectorCompliance,,,,,,An implementation that builds an IPFIX Collector that complies with this module MUST implement the objects defined in the mandatory group ipfixCommonGroup. The implementation of all objects in the other groups is optional and depends on the corresponding functionality implemented in the equipment. An implementation that is compliant with this MIB module is limited to using only the values TCP (6), UDP (17), and SCTP (132) in the ipfixTransportSessionProtocol object because these are the only protocols currently specified for usage within IPFIX (see RFC 5101).
.1.3.6.1.2.1.193.2.1.2,IPFIX-MIB::ipfixExporterCompliance,,,,,,An implementation that builds an IPFIX Exporter that complies with this module MUST implement the objects defined in the mandatory group ipfixCommonGroup. The implementation of all other objects depends on the implementation of the corresponding functionality in the equipment.
.1.3.6.1.2.1.193.2.2,IPFIX-MIB::ipfixGroups,,,,,,
.1.3.6.1.2.1.193.2.2.1,IPFIX-MIB::ipfixCommonGroup,,,,,,The main IPFIX objects.
.1.3.6.1.2.1.193.2.2.2,IPFIX-MIB::ipfixCommonStatsGroup,,,,,,Common statistical objects.
.1.3.6.1.2.1.193.2.2.3,IPFIX-MIB::ipfixExporterGroup,,,,,,The main objects for Exporters.
.1.3.6.1.2.1.193.2.2.4,IPFIX-MIB::ipfixExporterStatsGroup,,,,,,The statistical objects for Exporters.
.1.3.6.1.2.1.194,IPFIX-SELECTOR-MIB::ipfixSelectorMIB,,,,,,The IPFIX SELECTOR MIB module defined in this section provides the standard Filtering and Sampling functions that can be referenced in the ipfixSelectionProcessTable. All standard Filtering and Sampling functions MUST be registered in the subtree under object ipfixSelectorFunctions (1.3.6.1.2.1.194.1.1). The top-level OIDs in the subtree under object ipfixSelectorFunctions MUST be registered in a sub-registry maintained by IANA at <http://www.iana.org/assignments/smi-numbers/>. New Selector Functions MUST be registered at IANA and are subject to Expert Review [RFC5226], i.e., review by one of a group of experts designated by an IETF Area Director. The group of experts MUST check the requested MIB objects for completeness and accuracy of the description. Requests for MIB objects that duplicate the functionality of existing objects SHOULD be declined. The smallest available OID SHOULD be assigned to new MIB objects. The specification of new MIB objects SHOULD follow the structure specified in [RFC6615] and MUST be published using a well- established and persistent publication medium. The experts will initially be drawn from the Working Group Chairs and document editors of the IPFIX and PSAMP Working Groups. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.194.1,IPFIX-SELECTOR-MIB::ipfixSelectorObjects,,,,,,
.1.3.6.1.2.1.194.1.1,IPFIX-SELECTOR-MIB::ipfixSelectorFunctions,,,,,,
.1.3.6.1.2.1.194.1.1.1,IPFIX-SELECTOR-MIB::ipfixFuncSelectAll,,,,,,
.1.3.6.1.2.1.194.1.1.1.1,IPFIX-SELECTOR-MIB::ipfixFuncSelectAllAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of the trivial function of selecting all packets. This function is always available.
.1.3.6.1.2.1.194.1.1.2,PSAMP-MIB::psampSampCountBased,,,,,,
.1.3.6.1.2.1.194.1.1.2.1,PSAMP-MIB::psampSampCountBasedAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of systematic count-based sampling at the managed node. A Selector may be unavailable if it is implemented but currently disabled due to, e.g., administrative reasons, lack of resources, or similar.
.1.3.6.1.2.1.194.1.1.2.2,PSAMP-MIB::psampSampCountBasedParamSetTable,,not-accessible,,current,,This table lists configurations of systematic count-based packet sampling. A parameter set describing a configuration contains two parameters: the sampling interval length and space.
.1.3.6.1.2.1.194.1.1.2.2.1,PSAMP-MIB::psampSampCountBasedParamSetEntry,,not-accessible,psampSampCountBasedIndex,current,,Defines an entry in the psampSampCountBasedParamSetTable.
.1.3.6.1.2.1.194.1.1.2.2.1.1,PSAMP-MIB::psampSampCountBasedIndex,Integer32,not-accessible,,current,,The index of this parameter set in the psampSampCountBasedParamSetTable. It is used in the object ipfixSelectionProcessSelectorFunction entries of the ipfixSelectionProcessTable in the IPFIX-MIB as reference to this parameter set.
.1.3.6.1.2.1.194.1.1.2.2.1.2,PSAMP-MIB::psampSampCountBasedInterval,Unsigned32,read-only,,current,,This object specifies the number of packets that are consecutively sampled. A value of 100 means that 100 consecutive packets are sampled.
.1.3.6.1.2.1.194.1.1.2.2.1.3,PSAMP-MIB::psampSampCountBasedSpace,Unsigned32,read-only,,current,,This object specifies the number of packets between two intervals specified by the object psampSampCountBasedInterval. A value of 100 means that the next interval starts 100 packets (which are not sampled) after the current psampSampCountBasedInterval is over.
.1.3.6.1.2.1.194.1.1.3,PSAMP-MIB::psampSampTimeBased,,,,,,
.1.3.6.1.2.1.194.1.1.3.1,PSAMP-MIB::psampSampTimeBasedAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of systematic time-based sampling at the managed node. A Selector may be unavailable if it is implemented but currently disabled due to, e.g., administrative reasons, lack of resources, or similar.
.1.3.6.1.2.1.194.1.1.3.2,PSAMP-MIB::psampSampTimeBasedParamSetTable,,not-accessible,,current,,This table lists configurations of systematic time-based packet sampling. A parameter set describing a configuration contains two parameters: the sampling interval length and the space.
.1.3.6.1.2.1.194.1.1.3.2.1,PSAMP-MIB::psampSampTimeBasedParamSetEntry,,not-accessible,psampSampTimeBasedIndex,current,,Defines an entry in the psampSampTimeBasedParamSetTable.
.1.3.6.1.2.1.194.1.1.3.2.1.1,PSAMP-MIB::psampSampTimeBasedIndex,Integer32,not-accessible,,current,,The index of this parameter set in the psampSampTimeBasedParamSetTable. It is used in the object ipfixSelectionProcessSelectorFunction entries of the ipfixSelectionProcessTable in the IPFIX-MIB as reference to this parameter set.
.1.3.6.1.2.1.194.1.1.3.2.1.2,PSAMP-MIB::psampSampTimeBasedInterval,Unsigned32,read-only,,current,,This object specifies the time interval in microseconds during which all arriving packets are sampled.
.1.3.6.1.2.1.194.1.1.3.2.1.3,PSAMP-MIB::psampSampTimeBasedSpace,Unsigned32,read-only,,current,,This object specifies the time interval in microseconds between two intervals specified by the object psampSampTimeBasedInterval. A value of 100 means that the next interval starts 100 microseconds (during which no packets are sampled) after the current psampSampTimeBasedInterval is over.
.1.3.6.1.2.1.194.1.1.4,PSAMP-MIB::psampSampRandOutOfN,,,,,,
.1.3.6.1.2.1.194.1.1.4.1,PSAMP-MIB::psampSampRandOutOfNAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of random n-out-of-N sampling at the managed node. A Selector may be unavailable if it is implemented but currently disabled due to, e.g., administrative reasons, lack of resources, or similar.
.1.3.6.1.2.1.194.1.1.4.2,PSAMP-MIB::psampSampRandOutOfNParamSetTable,,not-accessible,,current,,This table lists configurations of random n-out-of-N sampling. A parameter set describing a configuration contains two parameters: the sampling size and the parent population.
.1.3.6.1.2.1.194.1.1.4.2.1,PSAMP-MIB::psampSampRandOutOfNParamSetEntry,,not-accessible,psampSampRandOutOfNIndex,current,,Defines an entry in the psampSampRandOutOfNParamSetTable.
.1.3.6.1.2.1.194.1.1.4.2.1.1,PSAMP-MIB::psampSampRandOutOfNIndex,Integer32,not-accessible,,current,,The index of this parameter set in the psampSampRandOutOfNParamSetTable. It is used in the object ipfixSelectionProcessSelectorFunction entries of the ipfixSelectionProcessTable in the IPFIX-MIB as reference to this parameter set.
.1.3.6.1.2.1.194.1.1.4.2.1.2,PSAMP-MIB::psampSampRandOutOfNSize,Unsigned32,read-only,,current,,This object specifies the number of elements taken from the parent Population specified in psampSampRandOutOfNPopulation.
.1.3.6.1.2.1.194.1.1.4.2.1.3,PSAMP-MIB::psampSampRandOutOfNPopulation,Unsigned32,read-only,,current,,This object specifies the number of elements in the parent Population.
.1.3.6.1.2.1.194.1.1.5,PSAMP-MIB::psampSampUniProb,,,,,,
.1.3.6.1.2.1.194.1.1.5.1,PSAMP-MIB::psampSampUniProbAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of random uniform probabilistic sampling at the managed node. A Selector may be unavailable if it is implemented but currently disabled due to, e.g., administrative reasons, lack of resources, or similar.
.1.3.6.1.2.1.194.1.1.5.2,PSAMP-MIB::psampSampUniProbParamSetTable,,not-accessible,,current,,This table lists configurations of random probabilistic sampling. A parameter set describing a configuration contains a single parameter only: the sampling probability.
.1.3.6.1.2.1.194.1.1.5.2.1,PSAMP-MIB::psampSampUniProbParamSetEntry,,not-accessible,psampSampUniProbIndex,current,,Defines an entry in the psampSampUniProbParamSetTable.
.1.3.6.1.2.1.194.1.1.5.2.1.1,PSAMP-MIB::psampSampUniProbIndex,Integer32,not-accessible,,current,,The index of this parameter set in the psampSampUniProbParamSetTable. It is used in the object ipfixSelectionProcessSelectorFunction entries of the ipfixSelectionProcessTable in the IPFIX-MIB as reference to this parameter set.
.1.3.6.1.2.1.194.1.1.5.2.1.2,PSAMP-MIB::psampSampUniProbProbability,OCTET,read-only,,current,,This object specifies the probability that a packet is sampled, expressed as a value between 0 and 1. The probability is equal for every packet. A value of 0 means no packet is sampled since the probability is 0. A value of 1 means all packets are sampled since the probability is 1. NaN (not a number) and infinity MUST NOT be used.
.1.3.6.1.2.1.194.1.1.6,PSAMP-MIB::psampFiltPropMatch,,,,,,
.1.3.6.1.2.1.194.1.1.6.1,PSAMP-MIB::psampFiltPropMatchAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of property match filtering at the managed node. A Selector may be unavailable if it is implemented but currently disabled due to, e.g., administrative reasons, lack of resources, or similar.
.1.3.6.1.2.1.194.1.1.7,PSAMP-MIB::psampFiltHash,,,,,,
.1.3.6.1.2.1.194.1.1.7.1,PSAMP-MIB::psampFiltHashAvail,INTEGER,read-only,,current,true(1):false(2),This object indicates the availability of hash filtering at the managed node. A Selector may be unavailable if it is implemented but currently disabled due to, e.g., administrative reasons, lack of resources, or similar.
.1.3.6.1.2.1.194.1.1.7.2,PSAMP-MIB::psampFiltHashCapabilities,,,,,,
.1.3.6.1.2.1.194.1.1.7.3,PSAMP-MIB::psampFiltHashParamSetTable,,not-accessible,,current,,This table lists configurations of hash filtering. A parameter set describing a configuration contains eight parameters describing the hash function.
.1.3.6.1.2.1.194.1.1.7.3.1,PSAMP-MIB::psampFiltHashParamSetEntry,,not-accessible,psampFiltHashIndex,current,,Defines an entry in the psampFiltHashParamSetTable.
.1.3.6.1.2.1.194.1.1.7.3.1.1,PSAMP-MIB::psampFiltHashIndex,Integer32,not-accessible,,current,,The index of this parameter set in the psampFiltHashParamSetTable. It is used in the object ipfixSelectionProcessSelectorFunction entries of the ipfixSelectionProcessTable in the IPFIX-MIB as reference to this parameter set.
.1.3.6.1.2.1.194.1.1.7.3.1.2,PSAMP-MIB::psampFiltHashFunction,INTEGER,read-only,,current,crc32(1):ipsx(2):bob(3),The hash function used by this filter. The PSAMP-MIB defines the following hash functions: crc32(1): The CRC-32 Hash Function as defined in RFC 1141. ipsx(2): The IPSX Hash Function as described in RFC 5475, Appendix A.1. bob(3): The BOB Hash Function as described in RFC 5475, Appendix A.2. 
.1.3.6.1.2.1.194.1.1.7.3.1.3,PSAMP-MIB::psampFiltHashInitializerValue,Counter64,read-only,,current,,This object specifies the initializer value to the hash function.
.1.3.6.1.2.1.194.1.1.7.3.1.4,PSAMP-MIB::psampFiltHashIpPayloadOffset,Counter64,read-only,,current,,This object specifies the IP payload offset used by a Hash-based Selection Selector.
.1.3.6.1.2.1.194.1.1.7.3.1.5,PSAMP-MIB::psampFiltHashIpPayloadSize,Counter64,read-only,,current,,This object specifies the IP payload size used by a Hash-based Selection Selector.
.1.3.6.1.2.1.194.1.1.7.3.1.6,PSAMP-MIB::psampFiltHashSelectedRangeMin,Counter64,read-only,,current,,This object specifies the value for the beginning of a hash function's selected range.
.1.3.6.1.2.1.194.1.1.7.3.1.7,PSAMP-MIB::psampFiltHashSelectedRangeMax,Counter64,read-only,,current,,This object specifies the value for the end of a hash function's selected range.
.1.3.6.1.2.1.194.1.1.7.3.1.8,PSAMP-MIB::psampFiltHashOutputRangeMin,Counter64,read-only,,current,,This object specifies the value for the beginning of a hash function's potential output range.
.1.3.6.1.2.1.194.1.1.7.3.1.9,PSAMP-MIB::psampFiltHashOutputRangeMax,Counter64,read-only,,current,,This object specifies the value for the end of a hash function's potential output range.
.1.3.6.1.2.1.194.2,IPFIX-SELECTOR-MIB::ipfixSelectorConformance,,,,,,
.1.3.6.1.2.1.194.2.1,IPFIX-SELECTOR-MIB::ipfixSelectorCompliances,,,,,,
.1.3.6.1.2.1.194.2.1.1,IPFIX-SELECTOR-MIB::ipfixSelectorBasicCompliance,,,,,,An implementation that builds an IPFIX Exporter that complies with this module MUST implement the objects defined in the mandatory group ipfixBasicGroup. The implementation of all other objects depends on the implementation of the corresponding functionality in the equipment.
.1.3.6.1.2.1.194.2.2,IPFIX-SELECTOR-MIB::ipfixSelectorGroups,,,,,,
.1.3.6.1.2.1.194.2.2.1,IPFIX-SELECTOR-MIB::ipfixSelectorBasicGroup,,,,,,The main IPFIX objects.
.1.3.6.1.2.1.195,CAPWAP-DOT11-MIB::capwapDot11MIB,,,,,,Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 5834; see the RFC itself for full legal notices. This MIB module contains managed object definitions for CAPWAP Protocol binding for IEEE 802.11.
.1.3.6.1.2.1.195.1,CAPWAP-DOT11-MIB::capwapDot11Objects,,,,,,
.1.3.6.1.2.1.195.1.1,CAPWAP-DOT11-MIB::capwapDot11WlanTable,,not-accessible,,current,,A table that allows the operator to display and configure WLAN profiles, such as specifying the MAC type and tunnel mode for a WLAN. Also, it helps the AC to configure a WLAN through the IEEE 802.11 MIB module. Values of all objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.195.1.1.1,CAPWAP-DOT11-MIB::capwapDot11WlanEntry,,not-accessible,capwapDot11WlanProfileId,current,,A set of objects that stores the settings of a WLAN profile.
.1.3.6.1.2.1.195.1.1.1.1,CAPWAP-DOT11-MIB::capwapDot11WlanProfileId,Unsigned32,not-accessible,,current,,Represents the identifier of a WLAN profile that has a corresponding capwapDot11WlanProfileIfIndex.
.1.3.6.1.2.1.195.1.1.1.2,CAPWAP-DOT11-MIB::capwapDot11WlanProfileIfIndex,Integer32,read-only,,current,,Represents the index value that uniquely identifies a WLAN Profile Interface. The interface identified by a particular value of this index is the same interface as identified by the same value of the ifIndex. The creation of a row object in the capwapDot11WlanTable triggers the AC to automatically create an WLAN Profile Interface identified by an ifIndex without manual intervention. Most MIB tables in the IEEE 802.11 MIB module [IEEE.802-11.2007] use an ifIndex to identify an interface to facilitate the configuration and maintenance, for example, dot11AuthenticationAlgorithmsTable. Using the ifIndex of a WLAN Profile Interface, the Operator could configure a WLAN through the IEEE 802.11 MIB module.
.1.3.6.1.2.1.195.1.1.1.3,CAPWAP-DOT11-MIB::capwapDot11WlanMacType,INTEGER,read-create,,current,localMAC(0):splitMAC(1):both(2),Represents whether the WTP SHOULD support the WLAN in Local or Split MAC modes.
.1.3.6.1.2.1.195.1.1.1.4,CAPWAP-DOT11-MIB::capwapDot11WlanTunnelMode,BITS,read-create,,current,localBridging(0):dot3Tunnel(1):nativeTunnel(2),Represents the frame tunneling mode to be used for IEEE 802.11 data frames from all stations associated with the WLAN. Bits are exclusive with each other for a specific WLAN profile, and only one tunnel mode could be configured. If the operator set more than one bit, the value of the Response-PDU's error-status field is set to 'wrongValue', and the value of its error-index field is set to the index of the failed variable binding.
.1.3.6.1.2.1.195.1.1.1.5,CAPWAP-DOT11-MIB::capwapDot11WlanRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. All the objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row: a. change the row status to 'notInService', b. change the values of the row c. change the row status to 'active' The capwapDot11WlanRowStatus may be changed to 'active' if all the managed objects in the conceptual row with When the operator deletes a WLAN profile, the AC SHOULD check whether the WLAN profile is bound with a radio. If yes, the value of the Response-PDU's error-status field is set to 'inconsistentValue', and the value of its error-index field is set to the index of the failed variable binding. If not, the row object could be deleted.
.1.3.6.1.2.1.195.1.2,CAPWAP-DOT11-MIB::capwapDot11WlanBindTable,,not-accessible,,current,,A table that stores bindings between WLAN profiles (identified by capwapDot11WlanProfileId) and WTP Virtual Radio Interfaces. The WTP Virtual Radio Interfaces on the AC correspond to physical layer (PHY) radios on the WTPs. It also stores the mappings between WLAN IDs and WLAN Basic Service Set (BSS) Interfaces. Values of all objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.195.1.2.1,CAPWAP-DOT11-MIB::capwapDot11WlanBindEntry,,not-accessible,ifIndex:capwapDot11WlanProfileId,current,,A set of objects that stores the binding of a WLAN profile to a WTP Virtual Radio Interface. It also stores the mapping between WLAN ID and WLAN BSS Interface. The INDEX object ifIndex is the ifIndex of a WTP Virtual Radio Interface.
.1.3.6.1.2.1.195.1.2.1.1,CAPWAP-DOT11-MIB::capwapDot11WlanBindWlanId,Unsigned32,read-only,,current,,Represents the WLAN ID of a WLAN. During a binding operation, the AC MUST select an unused WLAN ID from between 1 and 16 [RFC5416]. For example, to bind another WLAN profile to a radio that has been bound with a WLAN profile, WLAN ID 2 should be assigned.
.1.3.6.1.2.1.195.1.2.1.2,CAPWAP-DOT11-MIB::capwapDot11WlanBindBssIfIndex,Integer32,read-only,,current,,Represents the index value that uniquely identifies a WLAN BSS Interface. The interface identified by a particular value of this index is the same interface as identified by the same value of the ifIndex. The ifIndex here is for a WLAN BSS Interface. The creation of a row object in the capwapDot11WlanBindTable triggers the AC to automatically create a WLAN BSS Interface identified by an ifIndex without manual intervention. The PHY address of the capwapDot11WlanBindBssIfIndex is the BSSID. While manufacturers are free to assign BSSIDs by using any arbitrary mechanism, it is advised that where possible the BSSIDs are assigned as a contiguous block. When assigned as a block, implementations can still assign any of the available BSSIDs to any WLAN. One possible method is for the WTP to assign the address using the following algorithm: base BSSID address + WLAN ID.
.1.3.6.1.2.1.195.1.2.1.3,CAPWAP-DOT11-MIB::capwapDot11WlanBindRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. All the objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row: a. change the row status to 'notInService', b. change the values of the row c. change the row status to 'active'
.1.3.6.1.2.1.195.2,CAPWAP-DOT11-MIB::capwapDot11Conformance,,,,,,
.1.3.6.1.2.1.195.2.1,CAPWAP-DOT11-MIB::capwapDot11Groups,,,,,,
.1.3.6.1.2.1.195.2.1.1,CAPWAP-DOT11-MIB::capwapDot11WlanGroup,,,,,,A collection of objects that is used to configure the properties of a WLAN profile.
.1.3.6.1.2.1.195.2.1.2,CAPWAP-DOT11-MIB::capwapDot11WlanBindGroup,,,,,,A collection of objects that is used to bind the WLAN profiles with a radio.
.1.3.6.1.2.1.195.2.2,CAPWAP-DOT11-MIB::capwapDot11Compliances,,,,,,
.1.3.6.1.2.1.195.2.2.1,CAPWAP-DOT11-MIB::capwapDot11Compliance,,,,,,Describes the requirements for conformance to the CAPWAP-DOT11-MIB module.
.1.3.6.1.2.1.196,CAPWAP-BASE-MIB::capwapBaseMIB,,,,,,Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 5833; see the RFC itself for full legal notices. This MIB module contains managed object definitions for the CAPWAP Protocol.
.1.3.6.1.2.1.196.0,CAPWAP-BASE-MIB::capwapBaseNotifications,,,,,,
.1.3.6.1.2.1.196.0.1,CAPWAP-BASE-MIB::capwapBaseChannelUp,,,,,,This notification is sent by the AC when a CAPWAP channel is established. The notification is separated for data or control channel.
.1.3.6.1.2.1.196.0.2,CAPWAP-BASE-MIB::capwapBaseChannelDown,,,,,,This notification is sent by the AC when a CAPWAP channel is down. The notification is separated for data or control channel.
.1.3.6.1.2.1.196.0.3,CAPWAP-BASE-MIB::capwapBaseDecryptErrorReport,,,,,,This notification is generated when a WTP has had a decryption error since the last report.
.1.3.6.1.2.1.196.0.4,CAPWAP-BASE-MIB::capwapBaseJoinFailure,,,,,,This notification is generated when a WTP fails to join.
.1.3.6.1.2.1.196.0.5,CAPWAP-BASE-MIB::capwapBaseImageUpgradeFailure,,,,,,This notification is generated when a WTP fails to update the firmware image.
.1.3.6.1.2.1.196.0.6,CAPWAP-BASE-MIB::capwapBaseConfigMsgError,,,,,,This notification is generated when a WTP receives message elements in the configuration management messages that it is unable to apply locally.
.1.3.6.1.2.1.196.0.7,CAPWAP-BASE-MIB::capwapBaseRadioOperableStatus,,,,,,The notification is generated when a radio's operational state has changed.
.1.3.6.1.2.1.196.0.8,CAPWAP-BASE-MIB::capwapBaseAuthenFailure,,,,,,This is notification of an authentication failure event and provides the reason for it.
.1.3.6.1.2.1.196.1,CAPWAP-BASE-MIB::capwapBaseObjects,,,,,,
.1.3.6.1.2.1.196.1.1,CAPWAP-BASE-MIB::capwapBaseAc,,,,,,
.1.3.6.1.2.1.196.1.1.1,CAPWAP-BASE-MIB::capwapBaseWtpSessions,Gauge32,read-only,,current,,Represents the total number of WTPs that are connecting to the AC.
.1.3.6.1.2.1.196.1.1.2,CAPWAP-BASE-MIB::capwapBaseWtpSessionsLimit,Unsigned32,read-write,,current,,Represents the maximum number of WTP sessions configured on the AC. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.1.3,CAPWAP-BASE-MIB::capwapBaseStationSessions,Gauge32,read-only,,current,,Represents the total number of stations that are accessing the wireless service provided by the AC.
.1.3.6.1.2.1.196.1.1.4,CAPWAP-BASE-MIB::capwapBaseStationSessionsLimit,Unsigned32,read-write,,current,,Represents the maximum number of station sessions configured on the AC. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.1.5,CAPWAP-BASE-MIB::capwapBaseDataChannelDTLSPolicyOptions,BITS,read-only,,current,other(0):clear(1):dtls(2),The AC communicates its policy on the use of DTLS for the CAPWAP data channel. The AC MAY support more than one option, represented by the bit field below: other(0) - Other method, for example, vendor specific clear(1) - Clear text dtls(2) - DTLS
.1.3.6.1.2.1.196.1.1.6,CAPWAP-BASE-MIB::capwapBaseControlChannelAuthenOptions,BITS,read-only,,current,x509(0):psk(1),Represents the authentication credential type supported by the AC for CAPWAP control channel. The AC MAY support more than one option, represented by the bit field below: x509(0) - X.509 certificate based psk(1) - Pre-Shared secret
.1.3.6.1.2.1.196.1.1.9,CAPWAP-BASE-MIB::capwapBaseAcNameListTable,,not-accessible,,current,,A table of objects that configure the AC name list. Values of all read-create objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.196.1.1.9.1,CAPWAP-BASE-MIB::capwapBaseAcNameListEntry,,not-accessible,capwapBaseAcNameListId,current,,A set of objects that configures the AC name list.
.1.3.6.1.2.1.196.1.1.9.1.1,CAPWAP-BASE-MIB::capwapBaseAcNameListId,Unsigned32,not-accessible,,current,,Represents the unique identifier of an AC Name list.
.1.3.6.1.2.1.196.1.1.9.1.2,CAPWAP-BASE-MIB::capwapBaseAcNameListName,OCTET,read-create,,current,,Represents the name of an AC, and it is expected to be an UTF-8 encoded string.
.1.3.6.1.2.1.196.1.1.9.1.3,CAPWAP-BASE-MIB::capwapBaseAcNameListPriority,Unsigned32,read-create,,current,,Represents the priority order of the preferred AC. For instance, the value of one (1) is used to set the primary AC, the value of two (2) is used to set the secondary AC, etc.
.1.3.6.1.2.1.196.1.1.9.1.4,CAPWAP-BASE-MIB::capwapBaseAcNameListRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, and/or delete a row in this table. The value of capwapBaseAcNameListName and capwapBaseAcNameListPriority can be changed when this object is in state 'active' or in 'notInService'. The capwapBaseAcNameListRowStatus may be changed to 'active' if all the managed objects in the conceptual row with
.1.3.6.1.2.1.196.1.1.10,CAPWAP-BASE-MIB::capwapBaseMacAclTable,,not-accessible,,current,,A table of objects that configure station Access Control Lists (ACLs). The WTP will not provide service to the MAC addresses configured in this table. Values of all read-create objects in this table are persistent at AC restart/reboot.
.1.3.6.1.2.1.196.1.1.10.1,CAPWAP-BASE-MIB::capwapBaseMacAclEntry,,not-accessible,capwapBaseMacAclId,current,,A set of objects that configures station Access Control Lists (ACLs).
.1.3.6.1.2.1.196.1.1.10.1.1,CAPWAP-BASE-MIB::capwapBaseMacAclId,Unsigned32,not-accessible,,current,,Represents the unique identifier of an ACL.
.1.3.6.1.2.1.196.1.1.10.1.2,CAPWAP-BASE-MIB::capwapBaseMacAclStationId,OCTET,read-create,,current,,Represents the MAC address of a station to which WTPs will no longer provides service.
.1.3.6.1.2.1.196.1.1.10.1.3,CAPWAP-BASE-MIB::capwapBaseMacAclRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, and/or delete a row in this table. The value of capwapBaseMacAclStationId can be changed when this object is in state 'active' or in 'notInService'. The capwapBaseMacAclRowStatus may be changed to 'active' if all the managed objects in the conceptual row with
.1.3.6.1.2.1.196.1.2,CAPWAP-BASE-MIB::capwapBaseWtps,,,,,,
.1.3.6.1.2.1.196.1.2.1,CAPWAP-BASE-MIB::capwapBaseWtpProfileTable,,not-accessible,,current,,A table of objects that configure WTP profiles for WTPs to be managed before they connect to the AC. An operator could change a WTP's configuration by changing the values of parameters in the corresponding WTP profile, then the WTP could get the new configuration through the CAPWAP control channel. Values of all read-create objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.196.1.2.1.1,CAPWAP-BASE-MIB::capwapBaseWtpProfileEntry,,not-accessible,capwapBaseWtpProfileId,current,,A set of objects that configures and displays a WTP profile.
.1.3.6.1.2.1.196.1.2.1.1.1,CAPWAP-BASE-MIB::capwapBaseWtpProfileId,Unsigned32,not-accessible,,current,,Represents the unique identifier of a WTP profile.
.1.3.6.1.2.1.196.1.2.1.1.2,CAPWAP-BASE-MIB::capwapBaseWtpProfileName,OCTET,read-create,,current,,Represents the name of a WTP profile.
.1.3.6.1.2.1.196.1.2.1.1.3,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpMacAddress,OCTET,read-create,,current,,Represents the Base MAC address of a WTP. A WTP profile MUST contain the Base MAC address of the WTP because the CAPWAP message received from the WTP contains its Base MAC address and the AC uses the Base MAC address to find the corresponding WTP profile. Section 4.6.40 of [RFC5415] omits indicating that the WTP's Base MAC address must be included in the WTP Board Data message element. This is a known errata item and should be fixed in any future revision of the RFC 5415.
.1.3.6.1.2.1.196.1.2.1.1.4,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpModelNumber,OCTET,read-create,,current,,Represents the model number of a WTP. A WTP profile MUST include the WTP's model number, which reflects the number of Physical Layer (PHY) radios on the WTP. In this way, the creation of a WTP profile triggers the AC to automatically create the same number of WTP Virtual Radio Interfaces corresponding to the WTP's PHY radios without manual intervention. With the ifIndexes of WTP Virtual Radio Interfaces, the operator could configure and manage the WTP's PHY radios through the wireless binding MIB modules.
.1.3.6.1.2.1.196.1.2.1.1.5,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpName,OCTET,read-create,,current,,Represents the name of the WTP.
.1.3.6.1.2.1.196.1.2.1.1.6,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpLocation,OCTET,read-create,,current,,Represents the location of the WTP.
.1.3.6.1.2.1.196.1.2.1.1.7,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpStaticIpEnable,INTEGER,read-create,,current,true(1):false(2),Represents whether the WTP SHOULD use a static IP address or not. A value of false disables the static IP address, while a value of true enables it.
.1.3.6.1.2.1.196.1.2.1.1.8,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpStaticIpType,INTEGER,read-create,,current,ipv4(1),Represents the static IP address type used by the WTP. Only ipv4(1) is supported by the object. Although the CAPWAP protocol [RFC5415] supports both IPv4 and IPv6, note that the CAPWAP field modeled by this object does not support IPv6, so the object does not support ipv6(2).
.1.3.6.1.2.1.196.1.2.1.1.9,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpStaticIpAddress,OCTET,read-create,,current,,When capwapBaseWtpProfileWtpStaticIpEnable is true, it represents the static IP address to be assigned to the WTP. The format of this IP address is determined by the corresponding instance of object capwapBaseWtpProfileWtpStaticIpType.
.1.3.6.1.2.1.196.1.2.1.1.10,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpNetmask,OCTET,read-create,,current,,When capwapBaseWtpProfileWtpStaticIpEnable is true, it represents the netmask to be assigned to the WTP. The format of this netmask is determined by the corresponding instance of object capwapBaseWtpProfileWtpStaticIpType.
.1.3.6.1.2.1.196.1.2.1.1.11,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpGateway,OCTET,read-create,,current,,When capwapBaseWtpProfileWtpStaticIpEnable is true, it represents the gateway to be assigned to the WTP. The format of this IP address is determined by the corresponding instance of object capwapBaseWtpProfileWtpStaticIpType.
.1.3.6.1.2.1.196.1.2.1.1.12,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpFallbackEnable,INTEGER,read-create,,current,enabled(1):disabled(2),Represents whether to enable or disable automatic CAPWAP fallback in the event that a WTP detects its preferred AC and is not currently connected to it. The following enumerated values are supported: enabled(1) - The fallback mode is enabled disabled(2) - The fallback mode is disabled
.1.3.6.1.2.1.196.1.2.1.1.13,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpEchoInterval,Unsigned32,read-create,,current,,Represents the minimum time, in seconds, between sending Echo Request messages to the AC that the WTP has joined.
.1.3.6.1.2.1.196.1.2.1.1.14,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpIdleTimeout,Unsigned32,read-create,,current,,Represents the idle timeout value that the WTP SHOULD enforce for its active stations.
.1.3.6.1.2.1.196.1.2.1.1.15,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpMaxDiscoveryInterval,Unsigned32,read-create,,current,,Represents the maximum time allowed between sending Discovery Request messages, in seconds.
.1.3.6.1.2.1.196.1.2.1.1.16,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpReportInterval,Unsigned32,read-create,,current,,Represents the interval for WTP to send the Decryption Error report.
.1.3.6.1.2.1.196.1.2.1.1.17,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpStatisticsTimer,Unsigned32,read-create,,current,,Represents the interval the WTP uses between the WTP Event Requests it transmits to the AC to communicate its statistics, in seconds.
.1.3.6.1.2.1.196.1.2.1.1.18,CAPWAP-BASE-MIB::capwapBaseWtpProfileWtpEcnSupport,INTEGER,read-create,,current,limited(0):fullAndLimited(1),Represents the support for the Explicit Congestion Notification (ECN) bits, as defined in [RFC3168]. The following enumerated values are supported: limited(0) - Limited ECN support fullAndLimited(1) - Full and limited ECN support Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.2.1.1.19,CAPWAP-BASE-MIB::capwapBaseWtpProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, and/or delete a row in this table. The value of capwapBaseWtpProfileName, capwapBaseWtpProfileWtpName and capwapBaseWtpProfileWtpLocation can be changed when this object is in state 'active' or in 'notInService'. The other objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row: a. change the row status to 'notInService' b. change the values of the row c. change the row status to 'active' The capwapBaseWtpProfileRowStatus may be changed to 'active' if the managed objects capwapBaseWtpProfileName, capwapBaseWtpProfileWtpMacAddress, capwapBaseWtpProfileWtpModelNumber, capwapBaseWtpProfileWtpName, and capwapBaseWtpProfileWtpLocation in the conceptual row have been assigned valid values. Deleting a WTP profile in use will disconnect the WTP from the AC. So the network management system SHOULD ask the operator to confirm such an operation. When a WTP profile entry is removed from the table, the corresponding WTP Virtual Radio Interfaces are also removed from the capwapBaseWirelessBindingTable and ifTable [RFC2863]. Also, the related object instances SHOULD be removed from the wireless binding MIB modules such as the IEEE 802.11 MIB module [IEEE.802-11.2007].
.1.3.6.1.2.1.196.1.2.2,CAPWAP-BASE-MIB::capwapBaseWtpStateTable,,not-accessible,,current,,A table of objects that indicate the AC's CAPWAP FSM state for each WTP, and helps the operator to query a WTP's current configuration.
.1.3.6.1.2.1.196.1.2.2.1,CAPWAP-BASE-MIB::capwapBaseWtpStateEntry,,not-accessible,capwapBaseWtpStateWtpId,current,,A set of objects that displays the AC's CAPWAP FSM state for each WTP. Also, the operator could query the current configuration of a WTP by using the identifier of the corresponding WTP profile.
.1.3.6.1.2.1.196.1.2.2.1.1,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpId,OCTET,not-accessible,,current,,Represents the unique identifier of a WTP.
.1.3.6.1.2.1.196.1.2.2.1.2,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpIpAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Represents the IP address type of a WTP. Only ipv4(1) and ipv6(2) are supported by the object.
.1.3.6.1.2.1.196.1.2.2.1.3,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpIpAddress,OCTET,read-only,,current,,Represents the IP address of a WTP that corresponds to the IP address in the IP packet header. The format of this IP address is determined by the corresponding instance of object capwapBaseWtpStateWtpIpAddressType.
.1.3.6.1.2.1.196.1.2.2.1.4,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpLocalIpAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Represents the local IP address type of a WTP. Only ipv4(1) and ipv6(2) are supported by the object.
.1.3.6.1.2.1.196.1.2.2.1.5,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpLocalIpAddress,OCTET,read-only,,current,,Represents the local IP address of a WTP and models the CAPWAP Local IPv4 Address or CAPWAP Local IPv6 Address fields [RFC5415]. If a Network Address Translation (NAT) device is present between WTP and AC, the value of capwapBaseWtpStateWtpLocalIpAddress will be different from the value of capwapBaseWtpStateWtpIpAddress. The format of this IP address is determined by the corresponding instance of object capwapBaseWtpStateWtpLocalIpAddressType.
.1.3.6.1.2.1.196.1.2.2.1.6,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpBaseMacAddress,OCTET,read-only,,current,,Represents the WTP's Base MAC Address, which MAY be assigned to the primary Ethernet interface. The instance of the object corresponds to the Base MAC Address sub-element in the CAPWAP protocol [RFC5415].
.1.3.6.1.2.1.196.1.2.2.1.7,CAPWAP-BASE-MIB::capwapBaseWtpState,INTEGER,read-only,,current,dtls(1):join(2):image(3):configure(4):dataCheck(5):run(6):reset(7):dtlsTeardown(8):unknown(9),Represents the various possibilities of the AC's CAPWAP FSM state for each WTP. The following enumerated values are supported: dtls(1) - DTLS negotiation states, which include DTLS setup, authorize, DTLS connect join(2) - The WTP is joining with the AC image(3) - The WTP is downloading software configure(4) - The WTP is getting configuration from the AC dataCheck(5) - The AC is waiting for the Data Channel Keep Alive Packet run(6) - The WTP enters the running state reset(7) - The AC transmits a reset request message to the WTP dtlsTeardown(8) - DTLS session is torn down unknown(9) - Operator already prepared configuration for the WTP, while the WTP has not contacted the AC until now
.1.3.6.1.2.1.196.1.2.2.1.8,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpUpTime,TimeTicks,read-only,,current,,Represents the time (in hundredths of a second) since the WTP has been in the running state (corresponding to the value run(6) of capwapBaseWtpState).
.1.3.6.1.2.1.196.1.2.2.1.9,CAPWAP-BASE-MIB::capwapBaseWtpStateWtpCurrWtpProfileId,Unsigned32,read-only,,current,,Represents the current identifier of a WTP profile. The operator could query a WTP's current configuration with the identifier of a WTP profile.
.1.3.6.1.2.1.196.1.2.3,CAPWAP-BASE-MIB::capwapBaseWtpTable,,not-accessible,,current,,A table of objects that display properties of the WTPs in running state.
.1.3.6.1.2.1.196.1.2.3.1,CAPWAP-BASE-MIB::capwapBaseWtpEntry,,not-accessible,capwapBaseWtpCurrId,current,,A set of objects that displays properties of the WTPs in running state.
.1.3.6.1.2.1.196.1.2.3.1.1,CAPWAP-BASE-MIB::capwapBaseWtpCurrId,OCTET,not-accessible,,current,,Represents the unique identifier of a WTP in running state.
.1.3.6.1.2.1.196.1.2.3.1.2,CAPWAP-BASE-MIB::capwapBaseWtpPhyIndex,Integer32,read-only,,current,,Represents the unique physical index of a physical entity in the ENTITY-MIB module [RFC4133]. Information about a specific WTP such as its software version could be accessed through this index.
.1.3.6.1.2.1.196.1.2.3.1.3,CAPWAP-BASE-MIB::capwapBaseWtpBaseMacAddress,OCTET,read-only,,current,,Represents the WTP's Base MAC Address, which MAY be assigned to the primary Ethernet interface. The instance of the object corresponds to the Base MAC Address sub-element in the CAPWAP protocol [RFC5415].
.1.3.6.1.2.1.196.1.2.3.1.4,CAPWAP-BASE-MIB::capwapBaseWtpTunnelModeOptions,BITS,read-only,,current,localBridging(0):dot3Tunnel(1):nativeTunnel(2),Represents the tunneling modes of operation supported by the WTP.
.1.3.6.1.2.1.196.1.2.3.1.5,CAPWAP-BASE-MIB::capwapBaseWtpMacTypeOptions,INTEGER,read-only,,current,localMAC(0):splitMAC(1):both(2),Represents the MAC mode of operation supported by the WTP.
.1.3.6.1.2.1.196.1.2.3.1.6,CAPWAP-BASE-MIB::capwapBaseWtpDiscoveryType,INTEGER,read-only,,current,unknown(0):staticConfig(1):dhcp(2):dns(3):acRef(4),Represents how the WTP discovers the AC. The following enumerated values are supported: unknown(0) - Unknown staticConfig(1) - Static configuration dhcp(2) - DHCP dns(3) - DNS acRef(4) - AC referral Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.2.3.1.7,CAPWAP-BASE-MIB::capwapBaseWtpRadiosInUseNum,Gauge32,read-only,,current,,Represents the number of radios in use on the WTP.
.1.3.6.1.2.1.196.1.2.3.1.8,CAPWAP-BASE-MIB::capwapBaseWtpRadioNumLimit,Unsigned32,read-only,,current,,Represents the maximum radio number supported by the WTP.
.1.3.6.1.2.1.196.1.2.3.1.9,CAPWAP-BASE-MIB::capwapBaseWtpRetransmitCount,Counter32,read-only,,current,,Represents the number of retransmissions for a given CAPWAP packet.
.1.3.6.1.2.1.196.1.2.4,CAPWAP-BASE-MIB::capwapBaseWirelessBindingTable,,not-accessible,,current,,A table of objects that display the mappings between WTP Virtual Radio Interfaces and PHY radios, and the wireless binding type for each PHY radio. As capwapBaseWirelessBindingTable stores the mappings between PHY radios (Radio IDs) and the ifIndexes of WTP Virtual Radio Interfaces, the operator can get the ifIndex information by querying this table. Such a query operation SHOULD run from radio ID 1 to radio ID 31 according to [RFC5415], and stop when an invalid ifIndex value (0) is returned. Values of all objects in this table are persistent at restart/reboot.
.1.3.6.1.2.1.196.1.2.4.1,CAPWAP-BASE-MIB::capwapBaseWirelessBindingEntry,,not-accessible,capwapBaseWtpProfileId:capwapBaseWirelessBindingRadioId,current,,A set of objects that displays the mapping between a specific WTP Virtual Radio Interface and a PHY radio, and the wireless binding type for the PHY radio.
.1.3.6.1.2.1.196.1.2.4.1.1,CAPWAP-BASE-MIB::capwapBaseWirelessBindingRadioId,Unsigned32,not-accessible,,current,,Represents the identifier of a PHY radio on a WTP, which is required to be unique on a WTP. For example, WTP A and WTP B use a same value of capwapBaseWirelessBindingRadioId for their first radio.
.1.3.6.1.2.1.196.1.2.4.1.2,CAPWAP-BASE-MIB::capwapBaseWirelessBindingVirtualRadioIfIndex,Integer32,read-only,,current,,Represents the index value that uniquely identifies a WLAN Virtual Radio Interface. The interface identified by a particular value of this index is the same interface as identified by the same value of the ifIndex. Before WTPs contact the AC to get configuration, the operator configures WTP profiles for them. The creation of a WTP profile triggers the system to automatically create a specific number of WTP Virtual Radio Interfaces and add a new row object in the capwapBaseWirelessBindingTable without manual intervention. As most MIB modules use the ifIndex to identify an interface for configuration and statistical data (for example, the IEEE 802.11 MIB module [IEEE.802-11.2007]), it will be easy to reuse other wireless binding MIB modules through the WTP Virtual Radio Interface in the Centralized WLAN Architecture.
.1.3.6.1.2.1.196.1.2.4.1.3,CAPWAP-BASE-MIB::capwapBaseWirelessBindingType,INTEGER,read-only,,current,dot11(1):epc(3),Represents the wireless binding type for the radio. The following enumerated values are supported: dot11(1) - IEEE 802.11 epc(3) - EPCGlobal
.1.3.6.1.2.1.196.1.2.5,CAPWAP-BASE-MIB::capwapBaseStationTable,,not-accessible,,current,,A table of objects that display stations that are accessing the wireless service provided by the AC.
.1.3.6.1.2.1.196.1.2.5.1,CAPWAP-BASE-MIB::capwapBaseStationEntry,,not-accessible,capwapBaseStationId,current,,A set of objects that displays a station that is associated with the specific radio on the WTP. Note that in some cases such as roaming that a station may simultaneously associate with two WTPs for some (short) time. The MIB implementation MUST ensure there is only one valid and meaningful entry for a specific station.
.1.3.6.1.2.1.196.1.2.5.1.1,CAPWAP-BASE-MIB::capwapBaseStationId,OCTET,not-accessible,,current,,Represents the unique identifier of the station.
.1.3.6.1.2.1.196.1.2.5.1.2,CAPWAP-BASE-MIB::capwapBaseStationWtpId,OCTET,read-only,,current,,Represents the unique identifier of a WTP in running state.
.1.3.6.1.2.1.196.1.2.5.1.3,CAPWAP-BASE-MIB::capwapBaseStationWtpRadioId,Unsigned32,read-only,,current,,Represents the identifier of a PHY radio on a WTP, which is required to be unique on a WTP. For example, WTP A and WTP B use a same value of capwapBaseStationWtpRadioId for their first radio.
.1.3.6.1.2.1.196.1.2.5.1.4,CAPWAP-BASE-MIB::capwapBaseStationAddedTime,OCTET,read-only,,current,,Represents the time when the station is added.
.1.3.6.1.2.1.196.1.2.5.1.5,CAPWAP-BASE-MIB::capwapBaseStationVlanName,OCTET,read-only,,current,,Represents VLAN name to which the station is associated.
.1.3.6.1.2.1.196.1.2.6,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsTable,,not-accessible,,current,,A table of objects that display the WTPs' events statistics.
.1.3.6.1.2.1.196.1.2.6.1,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsEntry,,not-accessible,capwapBaseWtpCurrId,current,,A set of objects that displays the events statistics of a WTP.
.1.3.6.1.2.1.196.1.2.6.1.1,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsRebootCount,Counter32,read-only,,current,,Represents the number of reboots that have occurred due to a WTP crash. Note that the CAPWAP field [RFC5415] modeled by this counter takes the value 65535 to indicate that the information is not available on the WTP. This MIB object does not follow this behavior, which would not be standard in SMIv2. If the WTP does not have the information, the agent will not instantiate the object.
.1.3.6.1.2.1.196.1.2.6.1.2,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsInitCount,Counter32,read-only,,current,,Represents the number of reboots that have occurred at the request of a CAPWAP protocol message, such as a change in configuration that requires a reboot or an explicit CAPWAP protocol reset request. Note that the CAPWAP field [RFC5415] modeled by this counter takes the value 65535 to indicate that the information is not available on the WTP. This MIB object does not follow this behavior, which would not be standard in SMIv2. If the WTP does not have the information, the agent will not instantiate the object.
.1.3.6.1.2.1.196.1.2.6.1.3,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsLinkFailureCount,Counter32,read-only,,current,,Represents the number of times that a CAPWAP protocol connection with an AC has failed due to link failures.
.1.3.6.1.2.1.196.1.2.6.1.4,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsSwFailureCount,Counter32,read-only,,current,,Represents the number of times that a CAPWAP protocol connection with an AC has failed due to software-related reasons.
.1.3.6.1.2.1.196.1.2.6.1.5,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsHwFailureCount,Counter32,read-only,,current,,Represents the number of times that a CAPWAP protocol connection with an AC has failed due to hardware-related reasons.
.1.3.6.1.2.1.196.1.2.6.1.6,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsOtherFailureCount,Counter32,read-only,,current,,Represents the number of times that a CAPWAP protocol connection with an AC has failed due to known reasons, other than the AC-initiated, link, software or hardware failures.
.1.3.6.1.2.1.196.1.2.6.1.7,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsUnknownFailureCount,Counter32,read-only,,current,,Represents the number of times that a CAPWAP protocol connection with an AC has failed for unknown reasons.
.1.3.6.1.2.1.196.1.2.6.1.8,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsLastFailureType,INTEGER,read-only,,current,unsupported(0):acInit(1):linkFailure(2):swFailure(3):hwFailure(4):otherFailure(5):unknown(255),Represents the failure type of the most recent WTP failure. The following enumerated values are supported: unsupported(0) - Not supported acInit(1) - The AC initiated linkFailure(2) - Link failure swFailure(3) - Software failure hwFailure(4) - Hardware failure otherFailure(5) - Other failure unknown(255) - Unknown (e.g., WTP doesn't keep track of info) Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.2.7,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsTable,,not-accessible,,current,,A table of objects that display statistics on the radios' behaviors and reasons why the WTP radio has been reset. To get the events statistics of all radios on a specific WTP (identified by the capwapBaseWtpCurrId), a query operation SHOULD run from radio ID 1 to radio ID 31 until there is no data returned. The radio ID here corresponds to the object capwapBaseRadioEventsWtpRadioId. If the previous MIB operations such as query on the capwapBaseWirelessBindingTable know the exact value of each radio ID, the query operation on the capwapBaseRadioEventsStatsTable could use that value of Radio IDs.
.1.3.6.1.2.1.196.1.2.7.1,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsEntry,,not-accessible,capwapBaseWtpCurrId:capwapBaseRadioEventsWtpRadioId,current,,A set of objects that displays the statistical data of events that happened on a specific radio of a WTP.
.1.3.6.1.2.1.196.1.2.7.1.1,CAPWAP-BASE-MIB::capwapBaseRadioEventsWtpRadioId,Unsigned32,not-accessible,,current,,Represents the identifier of a PHY radio on a WTP, which is required to be unique on a WTP. For example, WTP A and WTP B use the same value of capwapBaseRadioEventsWtpRadioId for their first radio.
.1.3.6.1.2.1.196.1.2.7.1.2,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsResetCount,Counter32,read-only,,current,,Represents the number of times that the radio has been reset.
.1.3.6.1.2.1.196.1.2.7.1.3,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsSwFailureCount,Counter32,read-only,,current,,Represents the number of times that the radio has failed due to software-related reasons.
.1.3.6.1.2.1.196.1.2.7.1.4,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsHwFailureCount,Counter32,read-only,,current,,Represents the number of times that the radio has failed due to hardware-related reasons.
.1.3.6.1.2.1.196.1.2.7.1.5,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsOtherFailureCount,Counter32,read-only,,current,,Represents the number of times that the radio has failed due to known reasons, other than software or hardware failure.
.1.3.6.1.2.1.196.1.2.7.1.6,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsUnknownFailureCount,Counter32,read-only,,current,,Represents the number of times that the radio has failed for unknown reasons.
.1.3.6.1.2.1.196.1.2.7.1.7,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsConfigUpdateCount,Counter32,read-only,,current,,Represents the number of times that the radio configuration has been updated.
.1.3.6.1.2.1.196.1.2.7.1.8,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsChannelChangeCount,Counter32,read-only,,current,,Represents the number of times that the radio channel has been changed.
.1.3.6.1.2.1.196.1.2.7.1.9,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsBandChangeCount,Counter32,read-only,,current,,Represents the number of times that the radio has changed frequency bands.
.1.3.6.1.2.1.196.1.2.7.1.10,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsCurrNoiseFloor,Integer32,read-only,,current,,Represents the noise floor of the radio receiver in units of dBm.
.1.3.6.1.2.1.196.1.2.7.1.11,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsDecryptErrorCount,Counter32,read-only,,current,,Represents the number of decryption errors that have occurred on the WTP. Note that this field is only valid in cases where the WTP provides encryption/decryption services.
.1.3.6.1.2.1.196.1.2.7.1.12,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsLastFailureType,INTEGER,read-only,,current,unsupported(0):swFailure(1):hwFailure(2):otherFailure(3):unknown(255),Represents the failure type of the most recent radio failure. The following enumerated values are supported: unsupported(0) - Not supported swFailure(1) - Software failure hwFailure(2) - Hardware failure otherFailure(3) - Other failure unknown(255) - Unknown Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.3,CAPWAP-BASE-MIB::capwapBaseParameters,,,,,,
.1.3.6.1.2.1.196.1.3.1,CAPWAP-BASE-MIB::capwapBaseAcMaxRetransmit,Unsigned32,read-write,,current,,Represents the maximum number of retransmissions for a given CAPWAP packet before the link layer considers the peer dead. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.2,CAPWAP-BASE-MIB::capwapBaseAcChangeStatePendingTimer,Unsigned32,read-write,,current,,Represents the maximum time, in seconds, the AC will wait for the Change State Event Request from the WTP after having transmitted a successful Configuration Status Response message. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.3,CAPWAP-BASE-MIB::capwapBaseAcDataCheckTimer,Unsigned32,read-write,,current,,Represents The number of seconds the AC will wait for the Data Channel Keep Alive, which is required by the CAPWAP state machine's Data Check state. The AC resets the state machine if this timer expires prior to transitioning to the next state. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.4,CAPWAP-BASE-MIB::capwapBaseAcDTLSSessionDeleteTimer,Unsigned32,read-write,,current,,Represents the minimum time, in seconds, the AC MUST wait for DTLS session deletion. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.5,CAPWAP-BASE-MIB::capwapBaseAcEchoInterval,Unsigned32,read-write,,current,,Represents the minimum time, in seconds, between sending Echo Request messages to the AC with which the WTP has joined. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.6,CAPWAP-BASE-MIB::capwapBaseAcRetransmitInterval,Unsigned32,read-write,,current,,Represents the minimum time, in seconds, in which a non-acknowledged CAPWAP packet will be retransmitted. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.7,CAPWAP-BASE-MIB::capwapBaseAcSilentInterval,Unsigned32,read-write,,current,,Represents the minimum time, in seconds, during which the AC SHOULD ignore all CAPWAP and DTLS packets received from the WTP that is in the Sulking state. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.8,CAPWAP-BASE-MIB::capwapBaseAcWaitDTLSTimer,Unsigned32,read-write,,current,,Represents the maximum time, in seconds, the AC MUST wait without having received a DTLS Handshake message from an AC. This timer MUST be greater than 30 seconds. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.9,CAPWAP-BASE-MIB::capwapBaseAcWaitJoinTimer,Unsigned32,read-write,,current,,Represents the maximum time, in seconds, the AC will wait after the DTLS session has been established until it receives the Join Request from the WTP. This timer MUST be greater than 20 seconds. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.3.10,CAPWAP-BASE-MIB::capwapBaseAcEcnSupport,INTEGER,read-write,,current,limited(0):fullAndLimited(1),Represents the support for the Explicit Congestion Notification (ECN) bits, as defined in [RFC3168]. The value of the object is persistent at restart/reboot. The following enumerated values are supported: limited(0) - Limited ECN support fullAndLimited(1) - Full and limited ECN support Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.4,CAPWAP-BASE-MIB::capwapBaseStats,,,,,,
.1.3.6.1.2.1.196.1.4.1,CAPWAP-BASE-MIB::capwapBaseFailedDTLSAuthFailureCount,Counter32,read-only,,current,,Represents the number of failed DTLS session establishment attempts due to authentication failures.
.1.3.6.1.2.1.196.1.4.2,CAPWAP-BASE-MIB::capwapBaseFailedDTLSSessionCount,Counter32,read-only,,current,,Represents the number of failed DTLS session establishment attempts.
.1.3.6.1.2.1.196.1.5,CAPWAP-BASE-MIB::capwapBaseNotifyVarObjects,,,,,,
.1.3.6.1.2.1.196.1.5.1,CAPWAP-BASE-MIB::capwapBaseNtfWtpId,OCTET,accessible-for-notify,,current,,Represents the unique identifier of a WTP.
.1.3.6.1.2.1.196.1.5.2,CAPWAP-BASE-MIB::capwapBaseNtfRadioId,Unsigned32,accessible-for-notify,,current,,Represents the identifier of a PHY radio on a WTP, which is only required to be unique on a WTP. For example, WTP A and WTP B can use the same value of capwapBaseNtfRadioId for their first radio.
.1.3.6.1.2.1.196.1.5.3,CAPWAP-BASE-MIB::capwapBaseNtfChannelType,INTEGER,accessible-for-notify,,current,data(1):control(2),Represents the channel type for the CAPWAP protocol.
.1.3.6.1.2.1.196.1.5.4,CAPWAP-BASE-MIB::capwapBaseNtfAuthenMethod,INTEGER,accessible-for-notify,,current,other(1):clear(2):x509(3):psk(4),Represents the authentication method for the CAPWAP Channel.
.1.3.6.1.2.1.196.1.5.5,CAPWAP-BASE-MIB::capwapBaseNtfChannelDownReason,INTEGER,accessible-for-notify,,current,timeout(1):rekeyFailure(2):acRebootWtp(3):dtlsError(4):maxRetransmit(5),Represents the reason the channel is down. The following enumerated values are supported: timeout(1) - The keepalive timed out rekeyFailure(2) - Rekey process failed; channel will be broken acRebootWtp(3) - The AC rebooted the WTP dtlsError(4) - DTLS notifications: DTLSAborted, DTLSReassemblyFailure, DTLSPeerDisconnect, or frequent DTLSDecapFailure maxRetransmit(5) - The underlying reliable transport's RetransmitCount counter has reached the MaxRetransmit variable
.1.3.6.1.2.1.196.1.5.6,CAPWAP-BASE-MIB::capwapBaseNtfStationIdList,OCTET,accessible-for-notify,,current,,Represents a list of station MAC addresses separated by semicolons.
.1.3.6.1.2.1.196.1.5.7,CAPWAP-BASE-MIB::capwapBaseNtfAuthenFailureReason,INTEGER,accessible-for-notify,,current,keyMismatch(1):invalidCert(2):reassemblyFailure(3):decapFailure(4):encapFailure(5):timeout(6):unknown(8),Represents the reason for WTP authorization failure. The following enumerated values are supported: keyMismatch(1) - WTP's and AC's keys did not match invalidCert(2) - Certification is not valid reassemblyFailure(3) - Fragment reassembly failure decapFailure(4) - Decapsulation error encapFailure(5) - Encapsulation error timeout(6) - WaitDTLS timer timeout unknown(8) - Unknown reason
.1.3.6.1.2.1.196.1.5.8,CAPWAP-BASE-MIB::capwapBaseNtfRadioOperStatusFlag,INTEGER,accessible-for-notify,,current,operable(0):inoperable(1),Represents the operation status of a radio. The following enumerated values are supported: operable(0) - The radio is operable inoperable(1) - The radio is inoperable, and the capwapBaseNtfRadioStatusCause object gives the reason in detail Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.5.9,CAPWAP-BASE-MIB::capwapBaseNtfRadioStatusCause,INTEGER,accessible-for-notify,,current,normal(0):hwError(1):swError(2):adminSet(3),Represents the reason why the radio is out of service. The following enumerated values are supported: normal(0) - Normal status hwError(1) - Radio failure swError(2) - Software failure adminSet(3) - Administratively set Note that the CAPWAP field [RFC5415] modeled by this object takes zero as starting value; this MIB object follows that rule.
.1.3.6.1.2.1.196.1.5.10,CAPWAP-BASE-MIB::capwapBaseNtfJoinFailureReason,INTEGER,accessible-for-notify,,current,unspecified(1):resDepletion(2):unknownSource(3):incorrectData(4):sessionIdInUse(5):unsupportedHw(6):unsupportedBinding(7),Represents the reason of join failure. The following enumerated values are supported: unspecified(1) - Unspecified failure resDepletion(2) - Resource depletion unknownSource(3) - Unknown source incorrectData(4) - Incorrect data sessionIdInUse(5) - Session ID already in use unsupportedHw(6) - WTP hardware not supported unsupportedBinding(7) - Binding not supported
.1.3.6.1.2.1.196.1.5.11,CAPWAP-BASE-MIB::capwapBaseNtfImageFailureReason,INTEGER,accessible-for-notify,,current,invalidChecksum(1):invalidLength(2):other(3):inStorage(4),Represents the reason of image failure. The following enumerated values are supported: invalidChecksum(1) - Invalid checksum invalidLength(2) - Invalid data length other(3) - Other error inStorage(4) - Image already present
.1.3.6.1.2.1.196.1.5.12,CAPWAP-BASE-MIB::capwapBaseNtfConfigMsgErrorType,INTEGER,accessible-for-notify,,current,unknownElement(1):unsupportedElement(2):unknownValue(3):unsupportedValue(4),Represents the type of configuration message error. The following enumerated values are supported: unknownElement(1) - Unknown message element unsupportedElement(2) - Unsupported message element unknownValue(3) - Unknown message element value unsupportedValue(4) - Unsupported message element value
.1.3.6.1.2.1.196.1.5.13,CAPWAP-BASE-MIB::capwapBaseNtfMsgErrorElements,OCTET,accessible-for-notify,,current,,Represents the message elements sent by the AC in the Configuration Status Response message that caused the error.
.1.3.6.1.2.1.196.1.6,CAPWAP-BASE-MIB::capwapBaseNotifyControlObjects,,,,,,
.1.3.6.1.2.1.196.1.6.1,CAPWAP-BASE-MIB::capwapBaseChannelUpDownNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the Channel Up / Channel Down notification should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.6.2,CAPWAP-BASE-MIB::capwapBaseDecryptErrorNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the decryption error notification should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.6.3,CAPWAP-BASE-MIB::capwapBaseJoinFailureNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the notification of a WTP join failure should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.6.4,CAPWAP-BASE-MIB::capwapBaseImageUpgradeFailureNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the notification of a WTP image upgrade failure should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.6.5,CAPWAP-BASE-MIB::capwapBaseConfigMsgErrorNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the notification of configuration message error should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.6.6,CAPWAP-BASE-MIB::capwapBaseRadioOperableStatusNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the notification of a radio's operational state change should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.1.6.7,CAPWAP-BASE-MIB::capwapBaseAuthenFailureNotifyEnable,INTEGER,read-write,,current,true(1):false(2),Represents whether the notification of authentication failure should be generated. A value of true(1) means that the notification is enabled. A value of false(2) means that the notification is disabled. The value of the object is persistent at restart/reboot.
.1.3.6.1.2.1.196.2,CAPWAP-BASE-MIB::capwapBaseConformance,,,,,,
.1.3.6.1.2.1.196.2.1,CAPWAP-BASE-MIB::capwapBaseCompliances,,,,,,
.1.3.6.1.2.1.196.2.1.1,CAPWAP-BASE-MIB::capwapBaseCompliance,,,,,,Describes the requirements for conformance to the CAPWAP-BASE-MIB module.
.1.3.6.1.2.1.196.2.2,CAPWAP-BASE-MIB::capwapBaseGroups,,,,,,
.1.3.6.1.2.1.196.2.2.1,CAPWAP-BASE-MIB::capwapBaseAcNodeGroup,,,,,,A collection of objects that is used to represent the basic properties of the AC from the CAPWAP protocol perspective.
.1.3.6.1.2.1.196.2.2.2,CAPWAP-BASE-MIB::capwapBaseAcNodeGroup2,,,,,,A collection of objects that is used to represent the other properties (such as security) of the AC from the CAPWAP protocol perspective.
.1.3.6.1.2.1.196.2.2.3,CAPWAP-BASE-MIB::capwapBaseAcNameListGroup,,,,,,A collection of objects that is used to configure the AC name list.
.1.3.6.1.2.1.196.2.2.4,CAPWAP-BASE-MIB::capwapBaseMacAclsGroup,,,,,,A collection of objects that is used to configure the stations ACL.
.1.3.6.1.2.1.196.2.2.5,CAPWAP-BASE-MIB::capwapBaseWtpProfileGroup,,,,,,A collection of objects that is used to configure the WTP profile.
.1.3.6.1.2.1.196.2.2.6,CAPWAP-BASE-MIB::capwapBaseWtpProfileGroup2,,,,,,A collection of optional objects that is used to configure the WTP profile.
.1.3.6.1.2.1.196.2.2.7,CAPWAP-BASE-MIB::capwapBaseWtpStateGroup,,,,,,A collection of objects that is used to represent the WTP's state information.
.1.3.6.1.2.1.196.2.2.8,CAPWAP-BASE-MIB::capwapBaseWtpGroup,,,,,,A collection of objects that is used to represent the properties information for the WTPs in running state.
.1.3.6.1.2.1.196.2.2.9,CAPWAP-BASE-MIB::capwapBaseWtpGroup2,,,,,,A collection of optional objects that is used to represent the properties of the WTPs in running state.
.1.3.6.1.2.1.196.2.2.10,CAPWAP-BASE-MIB::capwapBaseRadioGroup,,,,,,A collection of objects that is used to represent the wireless binding type and the mappings between the ifIndexes of WLAN Virtual Radio Interfaces and PHY radios.
.1.3.6.1.2.1.196.2.2.11,CAPWAP-BASE-MIB::capwapBaseStationGroup,,,,,,A collection of objects that is used to represent the stations' basic properties.
.1.3.6.1.2.1.196.2.2.12,CAPWAP-BASE-MIB::capwapBaseWtpEventsStatsGroup,,,,,,A collection of objects that is used for collecting WTP reboot count, link failure count, hardware failure count, and so on.
.1.3.6.1.2.1.196.2.2.13,CAPWAP-BASE-MIB::capwapBaseRadioEventsStatsGroup,,,,,,A collection of objects that is used for collecting radio reset count, channel change count, hardware failure count, and so on
.1.3.6.1.2.1.196.2.2.14,CAPWAP-BASE-MIB::capwapBaseParametersGroup,,,,,,Objects used for the CAPWAP protocol's parameters.
.1.3.6.1.2.1.196.2.2.15,CAPWAP-BASE-MIB::capwapBaseStatsGroup,,,,,,Objects used for collecting the CAPWAP protocol's statistics.
.1.3.6.1.2.1.196.2.2.16,CAPWAP-BASE-MIB::capwapBaseNotificationsGroup,,,,,,A collection of notifications in this MIB module.
.1.3.6.1.2.1.196.2.2.17,CAPWAP-BASE-MIB::capwapBaseNotifyVarsGroup,,,,,,Objects used for notifications.
.1.3.6.1.2.1.196.2.2.18,CAPWAP-BASE-MIB::capwapBaseNotifyControlGroup,,,,,,Objects used to enable or disable notifications.
.1.3.6.1.2.1.197,NTPv4-MIB::ntpSnmpMIB,,,,,,The Management Information Base for NTP time entities. Copyright (c) 2010 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.197.0,NTPv4-MIB::ntpEntNotifications,,,,,,
.1.3.6.1.2.1.197.0.1,NTPv4-MIB::ntpEntNotifModeChange,,,,,,The notification to be sent when the NTP entity changes mode, including starting and stopping (if possible).
.1.3.6.1.2.1.197.0.2,NTPv4-MIB::ntpEntNotifStratumChange,,,,,,The notification to be sent when stratum level of NTP changes.
.1.3.6.1.2.1.197.0.3,NTPv4-MIB::ntpEntNotifSyspeerChanged,,,,,,The notification to be sent when a (new) syspeer has been selected.
.1.3.6.1.2.1.197.0.4,NTPv4-MIB::ntpEntNotifAddAssociation,,,,,,The notification to be sent when a new association is mobilized.
.1.3.6.1.2.1.197.0.5,NTPv4-MIB::ntpEntNotifRemoveAssociation,,,,,,The notification to be sent when an association is demobilized.
.1.3.6.1.2.1.197.0.6,NTPv4-MIB::ntpEntNotifConfigChanged,,,,,,The notification to be sent when the NTP configuration has changed, e.g., when the system connected to the Internet and was assigned a new IP address by the ISPs DHCP server.
.1.3.6.1.2.1.197.0.7,NTPv4-MIB::ntpEntNotifLeapSecondAnnounced,,,,,,The notification to be sent when a leap second has been announced.
.1.3.6.1.2.1.197.0.8,NTPv4-MIB::ntpEntNotifHeartbeat,,,,,,The notification to be sent periodically (as defined by ntpEntHeartbeatInterval) to indicate that the NTP entity is still alive.
.1.3.6.1.2.1.197.1,NTPv4-MIB::ntpSnmpMIBObjects,,,,,,
.1.3.6.1.2.1.197.1.1,NTPv4-MIB::ntpEntInfo,,,,,,
.1.3.6.1.2.1.197.1.1.1,NTPv4-MIB::ntpEntSoftwareName,OCTET,read-only,,current,,The product name of the running NTP version, e.g., 'ntpd'.
.1.3.6.1.2.1.197.1.1.2,NTPv4-MIB::ntpEntSoftwareVersion,OCTET,read-only,,current,,The software version of the installed NTP implementation as a full version string, e.g., 'ntpd-4.2.0b@1.1433 ...'
.1.3.6.1.2.1.197.1.1.3,NTPv4-MIB::ntpEntSoftwareVendor,OCTET,read-only,,current,,The vendor/author of the installed NTP version.
.1.3.6.1.2.1.197.1.1.4,NTPv4-MIB::ntpEntSystemType,OCTET,read-only,,current,,General hardware/os platform information, e.g., 'Linux 2.6.12 / x86'.
.1.3.6.1.2.1.197.1.1.5,NTPv4-MIB::ntpEntTimeResolution,Unsigned32,read-only,,current,,The time resolution in integer format, where the resolution is represented as divisions of a second, e.g., a value of 1000 translates to 1.0 ms.
.1.3.6.1.2.1.197.1.1.6,NTPv4-MIB::ntpEntTimePrecision,Integer32,read-only,,current,,The entity's precision in integer format, shows the precision. A value of -5 would mean 2^-5 = 31.25 ms.
.1.3.6.1.2.1.197.1.1.7,NTPv4-MIB::ntpEntTimeDistance,OCTET,read-only,,current,,The distance from this NTP entity to the root time reference (stratum 0) source including the unit, e.g., '13.243 ms'.
.1.3.6.1.2.1.197.1.2,NTPv4-MIB::ntpEntStatus,,,,,,
.1.3.6.1.2.1.197.1.2.1,NTPv4-MIB::ntpEntStatusCurrentMode,INTEGER,read-only,,current,notRunning(1):notSynchronized(2):noneConfigured(3):syncToLocal(4):syncToRefclock(5):syncToRemoteServer(6):unknown(99),The current mode of the NTP. The definition of each possible value is: notRunning(1) - NTP is not running. notSynchronized(2) - NTP is not synchronized to any time source (stratum = 16). noneConfigured(3) - NTP is not synchronized and does not have a reference configured (stratum = 16). syncToLocal(4) - NTP is distributing time based on its local clock (degraded accuracy and/or reliability). syncToRefclock(5) - NTP is synchronized to a local hardware refclock (e.g., GPS). syncToRemoteServer(6) - NTP is synchronized to a remote NTP server ('upstream' server). unknown(99) - The state of NTP is unknown.
.1.3.6.1.2.1.197.1.2.2,NTPv4-MIB::ntpEntStatusStratum,Unsigned32,read-only,,current,,The NTP entity's own stratum value. Should be a stratum of syspeer + 1 (or 16 if no syspeer).
.1.3.6.1.2.1.197.1.2.3,NTPv4-MIB::ntpEntStatusActiveRefSourceId,Unsigned32,read-only,,current,,The association ID of the current syspeer.
.1.3.6.1.2.1.197.1.2.4,NTPv4-MIB::ntpEntStatusActiveRefSourceName,OCTET,read-only,,current,,The hostname/descriptive name of the current reference source selected as syspeer, e.g., 'ntp1.ptb.de' or 'GPS' or 'DCFi', ...
.1.3.6.1.2.1.197.1.2.5,NTPv4-MIB::ntpEntStatusActiveOffset,OCTET,read-only,,current,,The time offset to the current selected reference time source as a string including unit, e.g., '0.032 ms' or '1.232 s'.
.1.3.6.1.2.1.197.1.2.6,NTPv4-MIB::ntpEntStatusNumberOfRefSources,Unsigned32,read-only,,current,,The number of reference sources configured for NTP.
.1.3.6.1.2.1.197.1.2.7,NTPv4-MIB::ntpEntStatusDispersion,OCTET,read-only,,current,,The root dispersion of the running NTP entity, e.g., '6.927'.
.1.3.6.1.2.1.197.1.2.8,NTPv4-MIB::ntpEntStatusEntityUptime,TimeTicks,read-only,,current,,The uptime of the NTP entity, (i.e., the time since ntpd was (re-)initialized not sysUptime!). The time is represented in hundreds of seconds since Jan 1, 1970 (00:00:00.000) UTC.
.1.3.6.1.2.1.197.1.2.9,NTPv4-MIB::ntpEntStatusDateTime,OCTET,read-only,,current,,The current NTP date/time on the device, in 128-bit NTP date format. If time is not syncronized, this field shall be a zero-length string. This object can be used to timestamp events on this node and allow a management station to correlate different time objects. For example, a management station could query this object and sysUpTime in the same operation to be able to relate sysUpTime to NTP time. This object is not to be used to set the time of the node querying this object. NTP should be used for this -- or at least SNTP.
.1.3.6.1.2.1.197.1.2.10,NTPv4-MIB::ntpEntStatusLeapSecond,OCTET,read-only,,current,,Date the next known leap second will occur. If there is no leap second announced, then this object should be 0.
.1.3.6.1.2.1.197.1.2.11,NTPv4-MIB::ntpEntStatusLeapSecDirection,Integer32,read-only,,current,,Direction of next known leap second. If there is no leap second announced, then this object should be 0.
.1.3.6.1.2.1.197.1.2.12,NTPv4-MIB::ntpEntStatusInPkts,Counter32,read-only,,current,,The total number of NTP messages delivered to the NTP entity from the transport service. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.2.13,NTPv4-MIB::ntpEntStatusOutPkts,Counter32,read-only,,current,,The total number of NTP messages delivered to the transport service by this NTP entity. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.2.14,NTPv4-MIB::ntpEntStatusBadVersion,Counter32,read-only,,current,,The total number of NTP messages that were delivered to this NTP entity and were for an unsupported NTP version. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.2.15,NTPv4-MIB::ntpEntStatusProtocolError,Counter32,read-only,,current,,The total number of NTP messages that were delivered to this NTP entity and this entity was not able to process due to an NTP protocol error. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.2.16,NTPv4-MIB::ntpEntStatusNotifications,Counter32,read-only,,current,,The total number of SNMP notifications that this NTP entity has generated. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.2.17,NTPv4-MIB::ntpEntStatPktModeTable,,not-accessible,,current,,The number of packets sent and received by packet mode. One entry per packet mode.
.1.3.6.1.2.1.197.1.2.17.1,NTPv4-MIB::ntpEntStatPktModeEntry,,not-accessible,ntpEntStatPktMode,current,,A statistical record of the number of packets sent and received for each packet mode.
.1.3.6.1.2.1.197.1.2.17.1.1,NTPv4-MIB::ntpEntStatPktMode,INTEGER,not-accessible,,current,symetricactive(1):symetricpassive(2):client(3):server(4):broadcastserver(5):broadcastclient(6),The NTP packet mode.
.1.3.6.1.2.1.197.1.2.17.1.2,NTPv4-MIB::ntpEntStatPktSent,Counter32,read-only,,current,,The number of NTP packets sent with this packet mode. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.2.17.1.3,NTPv4-MIB::ntpEntStatPktReceived,Counter32,read-only,,current,,The number of NTP packets received with this packet mode. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.3,NTPv4-MIB::ntpAssociation,,,,,,
.1.3.6.1.2.1.197.1.3.1,NTPv4-MIB::ntpAssociationTable,,not-accessible,,current,,The table of currently mobilized associations.
.1.3.6.1.2.1.197.1.3.1.1,NTPv4-MIB::ntpAssociationEntry,,not-accessible,ntpAssocId,current,,The table entry of currently mobilized associations.
.1.3.6.1.2.1.197.1.3.1.1.1,NTPv4-MIB::ntpAssocId,Unsigned32,not-accessible,,current,,The association ID. This is an internal, unique ID.
.1.3.6.1.2.1.197.1.3.1.1.2,NTPv4-MIB::ntpAssocName,OCTET,read-only,,current,,The hostname or other descriptive name for the association.
.1.3.6.1.2.1.197.1.3.1.1.3,NTPv4-MIB::ntpAssocRefId,OCTET,read-only,,current,,The refclock driver ID, if available.
.1.3.6.1.2.1.197.1.3.1.1.4,NTPv4-MIB::ntpAssocAddressType,INTEGER,read-only,,current,ipv4(1):ipv6(2):ipv4z(3):ipv6z(4),The type of address of the association. Can be either IPv4 or IPv6 (both with or without zone index) and contains the type of address for unicast, multicast, and broadcast associations.
.1.3.6.1.2.1.197.1.3.1.1.5,NTPv4-MIB::ntpAssocAddress,OCTET,read-only,,current,,The IP address (IPv4 or IPv6, with or without zone index) of the association. The type and size depends on the ntpAssocAddressType object. Represents the IP address of a uni/multi/broadcast association.
.1.3.6.1.2.1.197.1.3.1.1.6,NTPv4-MIB::ntpAssocOffset,OCTET,read-only,,current,,The time offset to the association as a string.
.1.3.6.1.2.1.197.1.3.1.1.7,NTPv4-MIB::ntpAssocStratum,Unsigned32,read-only,,current,,The association stratum value.
.1.3.6.1.2.1.197.1.3.1.1.8,NTPv4-MIB::ntpAssocStatusJitter,OCTET,read-only,,current,,The jitter in milliseconds as a string.
.1.3.6.1.2.1.197.1.3.1.1.9,NTPv4-MIB::ntpAssocStatusDelay,OCTET,read-only,,current,,The network delay in milliseconds as a string.
.1.3.6.1.2.1.197.1.3.1.1.10,NTPv4-MIB::ntpAssocStatusDispersion,OCTET,read-only,,current,,The root dispersion of the association.
.1.3.6.1.2.1.197.1.3.2,NTPv4-MIB::ntpAssociationStatisticsTable,,not-accessible,,current,,The table of statistics for current associations.
.1.3.6.1.2.1.197.1.3.2.1,NTPv4-MIB::ntpAssociationStatisticsEntry,,not-accessible,ntpAssocId,current,,The table entry of statistics for current associations.
.1.3.6.1.2.1.197.1.3.2.1.1,NTPv4-MIB::ntpAssocStatInPkts,Counter32,read-only,,current,,The total number of NTP messages delivered to the NTP entity from this association. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.3.2.1.2,NTPv4-MIB::ntpAssocStatOutPkts,Counter32,read-only,,current,,The total number of NTP messages delivered to the transport service by this NTP entity for this association. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.3.2.1.3,NTPv4-MIB::ntpAssocStatProtocolError,Counter32,read-only,,current,,The total number of NTP messages that were delivered to this NTP entity from this association and this entity was not able to process due to an NTP protocol error. Discountinuities in the value of this counter can occur upon cold start or reinitialization of the NTP entity, the management system and at other times as indicated by discontinuities in the value of sysUpTime.
.1.3.6.1.2.1.197.1.4,NTPv4-MIB::ntpEntControl,,,,,,
.1.3.6.1.2.1.197.1.4.1,NTPv4-MIB::ntpEntHeartbeatInterval,Unsigned32,read-write,,current,,The interval at which the ntpEntNotifHeartbeat notification should be sent, in seconds. If set to 0 and the entNotifHeartbeat bit in ntpEntNotifBits is 1, then ntpEntNotifHeartbeat is sent once. This value is stored persistently and will be restored to its last set value upon cold start or restart.
.1.3.6.1.2.1.197.1.4.2,NTPv4-MIB::ntpEntNotifBits,BITS,read-write,,current,notUsed(0):entNotifModeChange(1):entNotifStratumChange(2):entNotifSyspeerChanged(3):entNotifAddAssociation(4):entNotifRemoveAssociation(5):entNotifConfigChanged(6):entNotifLeapSecondAnnounced(7):entNotifHeartbeat(8),A bit for each notification. A 1 for a particular bit enables that particular notification, a 0 disables it. This value is stored persistently and will be restored to its last set value upon cold start or restart.
.1.3.6.1.2.1.197.1.5,NTPv4-MIB::ntpEntNotifObjects,,,,,,
.1.3.6.1.2.1.197.1.5.1,NTPv4-MIB::ntpEntNotifMessage,OCTET,accessible-for-notify,,current,,Used as a payload object for all notifications. Holds a cleartext event message.
.1.3.6.1.2.1.197.2,NTPv4-MIB::ntpEntConformance,,,,,,
.1.3.6.1.2.1.197.2.1,NTPv4-MIB::ntpEntCompliances,,,,,,
.1.3.6.1.2.1.197.2.1.1,NTPv4-MIB::ntpEntNTPCompliance,,,,,,The compliance statement for SNMP entities that use NTP and implement the NTP MIB.
.1.3.6.1.2.1.197.2.1.2,NTPv4-MIB::ntpEntSNTPCompliance,,,,,,The compliance statement for SNMP entities that use SNTP and implement the NTP MIB.
.1.3.6.1.2.1.197.2.2,NTPv4-MIB::ntpEntGroups,,,,,,
.1.3.6.1.2.1.197.2.2.1,NTPv4-MIB::ntpEntObjectsGroup1,,,,,,A collection of objects for the NTP MIB.
.1.3.6.1.2.1.197.2.2.2,NTPv4-MIB::ntpEntObjectsGroup2,,,,,,A collection of objects for the NTP MIB.
.1.3.6.1.2.1.197.2.2.3,NTPv4-MIB::ntpEntNotifGroup,,,,,,A collection of notifications for the NTP MIB
.1.3.6.1.2.1.198,SNMP-TLS-TM-MIB::snmpTlstmMIB,,,,,, The TLS Transport Model MIB Copyright (c) 2010-2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.198.0,SNMP-TLS-TM-MIB::snmpTlstmNotifications,,,,,,
.1.3.6.1.2.1.198.0.1,SNMP-TLS-TM-MIB::snmpTlstmServerCertificateUnknown,,,,,,Notification that the server certificate presented by an SNMP over (D)TLS server was invalid because no configured fingerprint or CA was acceptable to validate it. This may be because there was no entry in the snmpTlstmAddrTable or because no path could be found to known Certification Authority. To avoid notification loops, this notification MUST NOT be sent to servers that themselves have triggered the notification.
.1.3.6.1.2.1.198.0.2,SNMP-TLS-TM-MIB::snmpTlstmServerInvalidCertificate,,,,,,Notification that the server certificate presented by an SNMP over (D)TLS server could not be validated even if the fingerprint or expected validation path was known. That is, a cryptographic validation error occurred during certificate validation processing. To avoid notification loops, this notification MUST NOT be sent to servers that themselves have triggered the notification.
.1.3.6.1.2.1.198.1,SNMP-TLS-TM-MIB::snmpTlstmIdentities,,,,,,
.1.3.6.1.2.1.198.1.1,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNMIdentities,,,,,,
.1.3.6.1.2.1.198.1.1.1,SNMP-TLS-TM-MIB::snmpTlstmCertSpecified,,,,,,Directly specifies the tmSecurityName to be used for this certificate. The value of the tmSecurityName to use is specified in the snmpTlstmCertToTSNData column. The snmpTlstmCertToTSNData column must contain a non-zero length SnmpAdminString compliant value or the mapping described in this row must be considered a failure.
.1.3.6.1.2.1.198.1.1.2,SNMP-TLS-TM-MIB::snmpTlstmCertSANRFC822Name,,,,,,Maps a subjectAltName's rfc822Name to a tmSecurityName. The local part of the rfc822Name is passed unaltered but the host-part of the name must be passed in lowercase. This mapping results in a 1:1 correspondence between equivalent subjectAltName rfc822Name values and tmSecurityName values except that the host-part of the name MUST be passed in lowercase. Example rfc822Name Field: FooBar@Example.COM is mapped to tmSecurityName: FooBar@example.com.
.1.3.6.1.2.1.198.1.1.3,SNMP-TLS-TM-MIB::snmpTlstmCertSANDNSName,,,,,,Maps a subjectAltName's dNSName to a tmSecurityName after first converting it to all lowercase (RFC 5280 does not specify converting to lowercase so this involves an extra step). This mapping results in a 1:1 correspondence between subjectAltName dNSName values and the tmSecurityName values.
.1.3.6.1.2.1.198.1.1.4,SNMP-TLS-TM-MIB::snmpTlstmCertSANIpAddress,,,,,,Maps a subjectAltName's iPAddress to a tmSecurityName by transforming the binary encoded address as follows: 1) for IPv4, the value is converted into a decimal-dotted quad address (e.g., '192.0.2.1'). 2) for IPv6 addresses, the value is converted into a 32-character all lowercase hexadecimal string without any colon separators. This mapping results in a 1:1 correspondence between subjectAltName iPAddress values and the tmSecurityName values. The resulting length of an encoded IPv6 address is the maximum length supported by the View-Based Access Control Model (VACM). Using both the Transport Security Model's support for transport prefixes (see the SNMP-TSM-MIB's snmpTsmConfigurationUsePrefix object for details) will result in securityName lengths that exceed what VACM can handle.
.1.3.6.1.2.1.198.1.1.5,SNMP-TLS-TM-MIB::snmpTlstmCertSANAny,,,,,,Maps any of the following fields using the corresponding mapping algorithms: |------------+----------------------------| | Type | Algorithm | |------------+----------------------------| | rfc822Name | snmpTlstmCertSANRFC822Name | | dNSName | snmpTlstmCertSANDNSName | | iPAddress | snmpTlstmCertSANIpAddress | |------------+----------------------------| The first matching subjectAltName value found in the certificate of the above types MUST be used when deriving the tmSecurityName. The mapping algorithm specified in the 'Algorithm' column MUST be used to derive the tmSecurityName. This mapping results in a 1:1 correspondence between subjectAltName values and tmSecurityName values. The three sub-mapping algorithms produced by this combined algorithm cannot produce conflicting results between themselves.
.1.3.6.1.2.1.198.1.1.6,SNMP-TLS-TM-MIB::snmpTlstmCertCommonName,,,,,,Maps a certificate's CommonName to a tmSecurityName after converting it to a UTF-8 encoding. The usage of CommonNames is deprecated and users are encouraged to use subjectAltName mapping methods instead. This mapping results in a 1:1 correspondence between certificate CommonName values and tmSecurityName values.
.1.3.6.1.2.1.198.2,SNMP-TLS-TM-MIB::snmpTlstmObjects,,,,,,
.1.3.6.1.2.1.198.2.1,SNMP-TLS-TM-MIB::snmpTlstmSession,,,,,,
.1.3.6.1.2.1.198.2.1.1,SNMP-TLS-TM-MIB::snmpTlstmSessionOpens,Counter32,read-only,,current,,The number of times an openSession() request has been executed as a (D)TLS client, regardless of whether it succeeded or failed.
.1.3.6.1.2.1.198.2.1.2,SNMP-TLS-TM-MIB::snmpTlstmSessionClientCloses,Counter32,read-only,,current,,The number of times a closeSession() request has been executed as a (D)TLS client, regardless of whether it succeeded or failed.
.1.3.6.1.2.1.198.2.1.3,SNMP-TLS-TM-MIB::snmpTlstmSessionOpenErrors,Counter32,read-only,,current,,The number of times an openSession() request failed to open a session as a (D)TLS client, for any reason.
.1.3.6.1.2.1.198.2.1.4,SNMP-TLS-TM-MIB::snmpTlstmSessionAccepts,Counter32,read-only,,current,,The number of times a (D)TLS server has accepted a new connection from a client and has received at least one SNMP message through it.
.1.3.6.1.2.1.198.2.1.5,SNMP-TLS-TM-MIB::snmpTlstmSessionServerCloses,Counter32,read-only,,current,,The number of times a closeSession() request has been executed as a (D)TLS server, regardless of whether it succeeded or failed.
.1.3.6.1.2.1.198.2.1.6,SNMP-TLS-TM-MIB::snmpTlstmSessionNoSessions,Counter32,read-only,,current,,The number of times an outgoing message was dropped because the session associated with the passed tmStateReference was no longer (or was never) available.
.1.3.6.1.2.1.198.2.1.7,SNMP-TLS-TM-MIB::snmpTlstmSessionInvalidClientCertificates,Counter32,read-only,,current,,The number of times an incoming session was not established on a (D)TLS server because the presented client certificate was invalid. Reasons for invalidation include, but are not limited to, cryptographic validation failures or lack of a suitable mapping row in the snmpTlstmCertToTSNTable.
.1.3.6.1.2.1.198.2.1.8,SNMP-TLS-TM-MIB::snmpTlstmSessionUnknownServerCertificate,Counter32,read-only,,current,,The number of times an outgoing session was not established on a (D)TLS client because the server certificate presented by an SNMP over (D)TLS server was invalid because no configured fingerprint or Certification Authority (CA) was acceptable to validate it. This may result because there was no entry in the snmpTlstmAddrTable or because no path could be found to a known CA.
.1.3.6.1.2.1.198.2.1.9,SNMP-TLS-TM-MIB::snmpTlstmSessionInvalidServerCertificates,Counter32,read-only,,current,,The number of times an outgoing session was not established on a (D)TLS client because the server certificate presented by an SNMP over (D)TLS server could not be validated even if the fingerprint or expected validation path was known. That is, a cryptographic validation error occurred during certificate validation processing. Reasons for invalidation include, but are not limited to, cryptographic validation failures.
.1.3.6.1.2.1.198.2.1.10,SNMP-TLS-TM-MIB::snmpTlstmSessionInvalidCaches,Counter32,read-only,,current,,The number of outgoing messages dropped because the tmStateReference referred to an invalid cache.
.1.3.6.1.2.1.198.2.2,SNMP-TLS-TM-MIB::snmpTlstmConfig,,,,,,
.1.3.6.1.2.1.198.2.2.1,SNMP-TLS-TM-MIB::snmpTlstmCertificateMapping,,,,,,
.1.3.6.1.2.1.198.2.2.1.1,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNCount,Gauge32,read-only,,current,,A count of the number of entries in the snmpTlstmCertToTSNTable.
.1.3.6.1.2.1.198.2.2.1.2,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNTableLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime.0 when the snmpTlstmCertToTSNTable was last modified through any means, or 0 if it has not been modified since the command responder was started.
.1.3.6.1.2.1.198.2.2.1.3,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNTable,,not-accessible,,current,,This table is used by a (D)TLS server to map the (D)TLS client's presented X.509 certificate to a tmSecurityName. On an incoming (D)TLS/SNMP connection, the client's presented certificate must either be validated based on an established trust anchor, or it must directly match a fingerprint in this table. This table does not provide any mechanisms for configuring the trust anchors; the transfer of any needed trusted certificates for path validation is expected to occur through an out-of-band transfer. Once the certificate has been found acceptable (either by path validation or directly matching a fingerprint in this table), this table is consulted to determine the appropriate tmSecurityName to identify with the remote connection. This is done by considering each active row from this table in prioritized order according to its snmpTlstmCertToTSNID value. Each row's snmpTlstmCertToTSNFingerprint value determines whether the row is a match for the incoming connection: 1) If the row's snmpTlstmCertToTSNFingerprint value identifies the presented certificate, then consider the row as a successful match. 2) If the row's snmpTlstmCertToTSNFingerprint value identifies a locally held copy of a trusted CA certificate and that CA certificate was used to validate the path to the presented certificate, then consider the row as a successful match. Once a matching row has been found, the snmpTlstmCertToTSNMapType value can be used to determine how the tmSecurityName to associate with the session should be determined. See the snmpTlstmCertToTSNMapType column'sfor details on determining the tmSecurityName value. If it is impossible to determine a tmSecurityName from the row's data combined with the data presented in the certificate, then additional rows MUST be searched looking for another potential match. If a resulting tmSecurityName mapped from a given row is not compatible with the needed requirements of a tmSecurityName (e.g., VACM imposes a 32-octet-maximum length and the certificate derived securityName could be longer), then it must be considered an invalid match and additional rows MUST be searched looking for another potential match. If no matching and valid row can be found, the connection MUST be closed and SNMP messages MUST NOT be accepted over it. Missing values of snmpTlstmCertToTSNID are acceptable and implementations should continue to the next highest numbered row. It is recommended that administrators skip index values to leave room for the insertion of future rows (for example, use values of 10 and 20 when creating initial rows). Users are encouraged to make use of certificates with subjectAltName fields that can be used as tmSecurityNames so that a single root CA certificate can allow all child certificate's subjectAltName to map directly to a tmSecurityName via a 1:1 transformation. However, this table is flexible to allow for situations where existing deployed certificate infrastructures do not provide adequate subjectAltName values for use as tmSecurityNames. Certificates may also be mapped to tmSecurityNames using the CommonName portion of the Subject field. However, the usage of the CommonName field is deprecated and thus this usage is NOT RECOMMENDED. Direct mapping from each individual certificate fingerprint to a tmSecurityName is also possible but requires one entry in the table per tmSecurityName and requires more management operations to completely configure a device.
.1.3.6.1.2.1.198.2.2.1.3.1,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNEntry,,not-accessible,snmpTlstmCertToTSNID,current,,A row in the snmpTlstmCertToTSNTable that specifies a mapping for an incoming (D)TLS certificate to a tmSecurityName to use for a connection.
.1.3.6.1.2.1.198.2.2.1.3.1.1,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNID,Unsigned32,not-accessible,,current,,A unique, prioritized index for the given entry. Lower numbers indicate a higher priority.
.1.3.6.1.2.1.198.2.2.1.3.1.2,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNFingerprint,OCTET,read-create,,current,,A cryptographic hash of an X.509 certificate. The results of a successful matching fingerprint to either the trusted CA in the certificate validation path or to the certificate itself is dictated by the snmpTlstmCertToTSNMapType column.
.1.3.6.1.2.1.198.2.2.1.3.1.3,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNMapType,OBJECT,read-create,,current,,Specifies the mapping type for deriving a tmSecurityName from a certificate. Details for mapping of a particular type SHALL be specified in the DESCRIPTION clause of the OBJECT-IDENTITY that describes the mapping. If a mapping succeeds it will return a tmSecurityName for use by the TLSTM model and processing stops. If the resulting mapped value is not compatible with the needed requirements of a tmSecurityName (e.g., VACM imposes a 32-octet-maximum length and the certificate derived securityName could be longer), then future rows MUST be searched for additional snmpTlstmCertToTSNFingerprint matches to look for a mapping that succeeds. Suitable values for assigning to this object that are defined within the SNMP-TLS-TM-MIB can be found in the snmpTlstmCertToTSNMIdentities portion of the MIB tree.
.1.3.6.1.2.1.198.2.2.1.3.1.4,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNData,OCTET,read-create,,current,,Auxiliary data used as optional configuration information for a given mapping specified by the snmpTlstmCertToTSNMapType column. Only some mapping systems will make use of this column. The value in this column MUST be ignored for any mapping type that does not require data present in this column.
.1.3.6.1.2.1.198.2.2.1.3.1.5,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.198.2.2.1.3.1.6,SNMP-TLS-TM-MIB::snmpTlstmCertToTSNRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object may be used to create or remove rows from this table. To create a row in this table, an administrator must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTlstmParamsRowStatus column is notReady(3). In particular, a newly created row cannot be made active until the corresponding snmpTlstmCertToTSNFingerprint, snmpTlstmCertToTSNMapType, and snmpTlstmCertToTSNData columns have been set. The following objects may not be modified while the value of this object is active(1): - snmpTlstmCertToTSNFingerprint - snmpTlstmCertToTSNMapType - snmpTlstmCertToTSNData An attempt to set these objects while the value of snmpTlstmParamsRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.2.1.198.2.2.1.4,SNMP-TLS-TM-MIB::snmpTlstmParamsCount,Gauge32,read-only,,current,,A count of the number of entries in the snmpTlstmParamsTable.
.1.3.6.1.2.1.198.2.2.1.5,SNMP-TLS-TM-MIB::snmpTlstmParamsTableLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime.0 when the snmpTlstmParamsTable was last modified through any means, or 0 if it has not been modified since the command responder was started.
.1.3.6.1.2.1.198.2.2.1.6,SNMP-TLS-TM-MIB::snmpTlstmParamsTable,,not-accessible,,current,,This table is used by a (D)TLS client when a (D)TLS connection is being set up using an entry in the SNMP-TARGET-MIB. It extends the SNMP-TARGET-MIB's snmpTargetParamsTable with a fingerprint of a certificate to use when establishing such a (D)TLS connection.
.1.3.6.1.2.1.198.2.2.1.6.1,SNMP-TLS-TM-MIB::snmpTlstmParamsEntry,,not-accessible,IMPLIEDsnmpTargetParamsName,current,,A conceptual row containing a fingerprint hash of a locally held certificate for a given snmpTargetParamsEntry. The values in this row should be ignored if the connection that needs to be established, as indicated by the SNMP-TARGET-MIB infrastructure, is not a certificate and (D)TLS based connection. The connection SHOULD NOT be established if the certificate fingerprint stored in this entry does not point to a valid locally held certificate or if it points to an unusable certificate (such as might happen when the certificate's expiration date has been reached).
.1.3.6.1.2.1.198.2.2.1.6.1.1,SNMP-TLS-TM-MIB::snmpTlstmParamsClientFingerprint,OCTET,read-create,,current,,This object stores the hash of the public portion of a locally held X.509 certificate. The X.509 certificate, its public key, and the corresponding private key will be used when initiating a (D)TLS connection as a (D)TLS client.
.1.3.6.1.2.1.198.2.2.1.6.1.2,SNMP-TLS-TM-MIB::snmpTlstmParamsStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.198.2.2.1.6.1.3,SNMP-TLS-TM-MIB::snmpTlstmParamsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object may be used to create or remove rows from this table. To create a row in this table, an administrator must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTlstmParamsRowStatus column is notReady(3). In particular, a newly created row cannot be made active until the corresponding snmpTlstmParamsClientFingerprint column has been set. The snmpTlstmParamsClientFingerprint object may not be modified while the value of this object is active(1). An attempt to set these objects while the value of snmpTlstmParamsRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.2.1.198.2.2.1.7,SNMP-TLS-TM-MIB::snmpTlstmAddrCount,Gauge32,read-only,,current,,A count of the number of entries in the snmpTlstmAddrTable.
.1.3.6.1.2.1.198.2.2.1.8,SNMP-TLS-TM-MIB::snmpTlstmAddrTableLastChanged,TimeTicks,read-only,,current,,The value of sysUpTime.0 when the snmpTlstmAddrTable was last modified through any means, or 0 if it has not been modified since the command responder was started.
.1.3.6.1.2.1.198.2.2.1.9,SNMP-TLS-TM-MIB::snmpTlstmAddrTable,,not-accessible,,current,,This table is used by a (D)TLS client when a (D)TLS connection is being set up using an entry in the SNMP-TARGET-MIB. It extends the SNMP-TARGET-MIB's snmpTargetAddrTable so that the client can verify that the correct server has been reached. This verification can use either a certificate fingerprint, or an identity authenticated via certification path validation. If there is an active row in this table corresponding to the entry in the SNMP-TARGET-MIB that was used to establish the connection, and the row's snmpTlstmAddrServerFingerprint column has non-empty value, then the server's presented certificate is compared with the snmpTlstmAddrServerFingerprint value (and the snmpTlstmAddrServerIdentity column is ignored). If the fingerprint matches, the verification has succeeded. If the fingerprint does not match, then the connection MUST be closed. If the server's presented certificate has passed certification path validation [RFC5280] to a configured trust anchor, and an active row exists with a zero-length snmpTlstmAddrServerFingerprint value, then the snmpTlstmAddrServerIdentity column contains the expected host name. This expected host name is then compared against the server's certificate as follows: - Implementations MUST support matching the expected host name against a dNSName in the subjectAltName extension field and MAY support checking the name against the CommonName portion of the subject distinguished name. - The '*' (ASCII 0x2a) wildcard character is allowed in the dNSName of the subjectAltName extension (and in common name, if used to store the host name), but only as the left-most (least significant) DNS label in that value. This wildcard matches any left-most DNS label in the server name. That is, the subject *.example.com matches the server names a.example.com and b.example.com, but does not match example.com or a.b.example.com. Implementations MUST support wildcards in certificates as specified above, but MAY provide a configuration option to disable them. - If the locally configured name is an internationalized domain name, conforming implementations MUST convert it to the ASCII Compatible Encoding (ACE) format for performing comparisons, as specified in Section 7 of [RFC5280]. If the expected host name fails these conditions then the connection MUST be closed. If there is no row in this table corresponding to the entry in the SNMP-TARGET-MIB and the server can be authorized by another, implementation-dependent means, then the connection MAY still proceed.
.1.3.6.1.2.1.198.2.2.1.9.1,SNMP-TLS-TM-MIB::snmpTlstmAddrEntry,,not-accessible,IMPLIEDsnmpTargetAddrName,current,,A conceptual row containing a copy of a certificate's fingerprint for a given snmpTargetAddrEntry. The values in this row should be ignored if the connection that needs to be established, as indicated by the SNMP-TARGET-MIB infrastructure, is not a (D)TLS based connection. If an snmpTlstmAddrEntry exists for a given snmpTargetAddrEntry, then the presented server certificate MUST match or the connection MUST NOT be established. If a row in this table does not exist to match an snmpTargetAddrEntry row, then the connection SHOULD still proceed if some other certificate validation path algorithm (e.g., RFC 5280) can be used.
.1.3.6.1.2.1.198.2.2.1.9.1.1,SNMP-TLS-TM-MIB::snmpTlstmAddrServerFingerprint,OCTET,read-create,,current,,A cryptographic hash of a public X.509 certificate. This object should store the hash of the public X.509 certificate that the remote server should present during the (D)TLS connection setup. The fingerprint of the presented certificate and this hash value MUST match exactly or the connection MUST NOT be established.
.1.3.6.1.2.1.198.2.2.1.9.1.2,SNMP-TLS-TM-MIB::snmpTlstmAddrServerIdentity,OCTET,read-create,,current,,The reference identity to check against the identity presented by the remote system.
.1.3.6.1.2.1.198.2.2.1.9.1.3,SNMP-TLS-TM-MIB::snmpTlstmAddrStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.198.2.2.1.9.1.4,SNMP-TLS-TM-MIB::snmpTlstmAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. This object may be used to create or remove rows from this table. To create a row in this table, an administrator must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTlstmAddrRowStatus column is notReady(3). In particular, a newly created row cannot be made active until the corresponding snmpTlstmAddrServerFingerprint column has been set. Rows MUST NOT be active if the snmpTlstmAddrServerFingerprint column is blank and the snmpTlstmAddrServerIdentity is set to '*' since this would insecurely accept any presented certificate. The snmpTlstmAddrServerFingerprint object may not be modified while the value of this object is active(1). An attempt to set these objects while the value of snmpTlstmAddrRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.2.1.198.3,SNMP-TLS-TM-MIB::snmpTlstmConformance,,,,,,
.1.3.6.1.2.1.198.3.1,SNMP-TLS-TM-MIB::snmpTlstmCompliances,,,,,,
.1.3.6.1.2.1.198.3.1.1,SNMP-TLS-TM-MIB::snmpTlstmCompliance,,,,,,The compliance statement for SNMP engines that support the SNMP-TLS-TM-MIB
.1.3.6.1.2.1.198.3.2,SNMP-TLS-TM-MIB::snmpTlstmGroups,,,,,,
.1.3.6.1.2.1.198.3.2.1,SNMP-TLS-TM-MIB::snmpTlstmStatsGroup,,,,,,A collection of objects for maintaining statistical information of an SNMP engine that implements the SNMP TLS Transport Model.
.1.3.6.1.2.1.198.3.2.2,SNMP-TLS-TM-MIB::snmpTlstmIncomingGroup,,,,,,A collection of objects for maintaining incoming connection certificate mappings to tmSecurityNames of an SNMP engine that implements the SNMP TLS Transport Model.
.1.3.6.1.2.1.198.3.2.3,SNMP-TLS-TM-MIB::snmpTlstmOutgoingGroup,,,,,,A collection of objects for maintaining outgoing connection certificates to use when opening connections as a result of SNMP-TARGET-MIB settings.
.1.3.6.1.2.1.198.3.2.4,SNMP-TLS-TM-MIB::snmpTlstmNotificationGroup,,,,,,Notifications
.1.3.6.1.2.1.199,SNMP-VACM-AAA-MIB::vacmAaaMIB,,,,,,The management and local datastore information definitions for the AAA-Enabled View-based Access Control Model for SNMP. Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 6065; see the RFC itself for full legal notices.
.1.3.6.1.2.1.199.1,SNMP-VACM-AAA-MIB::vacmAaaMIBObjects,,,,,,
.1.3.6.1.2.1.199.1.1,SNMP-VACM-AAA-MIB::vacmAaaSecurityToGroupTable,,not-accessible,,current,,This table provides a listing of all currently active sessions for which a mapping of the combination of SnmpSecurityModel and securityName into the name of a VACM group has been provided by an AAA service. The group name (in VACM) in turn identifies an access control policy to be used for the corresponding principals.
.1.3.6.1.2.1.199.1.1.1,SNMP-VACM-AAA-MIB::vacmAaaSecurityToGroupEntry,,not-accessible,vacmAaaSecurityModel:vacmAaaSecurityName:vacmAaaSessionID,current,,An entry in this table maps the combination of a SnmpSecurityModel and securityName into the name of a VACM group defining the access control policy that is to govern a particular session. Each entry corresponds to a session. Entries do not persist across reboots. An entry is created whenever an indication occurs that a new session has been established that would not have the same index values as an existing entry. When a session is torn down, disconnected, timed out (e.g., following the RADIUS Session-Timeout Attribute), or otherwise terminated for any reason, the corresponding vacmAaaSecurityToGroupEntry is deleted.
.1.3.6.1.2.1.199.1.1.1.1,SNMP-VACM-AAA-MIB::vacmAaaSecurityModel,INTEGER,not-accessible,,current,,The security model associated with the AAA binding represented by this entry. This object cannot take the 'any' (0) value.
.1.3.6.1.2.1.199.1.1.1.2,SNMP-VACM-AAA-MIB::vacmAaaSecurityName,OCTET,not-accessible,,current,,The securityName of the principal associated with the AAA binding represented by this entry. In RADIUS environments, this corresponds to the User-Name Attribute.
.1.3.6.1.2.1.199.1.1.1.3,SNMP-VACM-AAA-MIB::vacmAaaSessionID,Unsigned32,not-accessible,,current,,An implementation-dependent identifier of the session. This value MUST be unique among all currently open sessions of all of this SNMP engine's transport models. The value has no particular significance other than to distinguish sessions. Implementations in which tmSessionID has a compatible syntax and is unique across all transport models MAY use that value.
.1.3.6.1.2.1.199.1.1.1.4,SNMP-VACM-AAA-MIB::vacmAaaGroupName,OCTET,read-only,,current,,The name of the group to which this entry is to belong. In RADIUS environments, this comes from the RADIUS Management-Policy-Id Attribute. When the appropriate conditions are met, the value of this object is applied the vacmGroupName in the corresponding vacmSecurityToGroupEntry.
.1.3.6.1.2.1.199.2,SNMP-VACM-AAA-MIB::vacmAaaMIBConformance,,,,,,
.1.3.6.1.2.1.199.2.1,SNMP-VACM-AAA-MIB::vacmAaaMIBCompliances,,,,,,
.1.3.6.1.2.1.199.2.1.1,SNMP-VACM-AAA-MIB::vacmAaaMIBBasicCompliance,,,,,,The compliance statement for SNMP engines implementing the AAA-Enabled View-based Access Control Model for SNMP.
.1.3.6.1.2.1.199.2.2,SNMP-VACM-AAA-MIB::vacmAaaMIBGroups,,,,,,
.1.3.6.1.2.1.199.2.2.1,SNMP-VACM-AAA-MIB::vacmAaaGroup,,,,,,A collection of objects for supporting the use of AAA services to provide user-to-group mappings for VACM.
.1.3.6.1.2.1.200,PW-CEP-STD-MIB::pwCepStdMIB,,,,,,This MIB module contains managed object definitions for Circuit Emulation over Packet (CEP) as in [RFC4842]: Malis, A., Prayson, P., Cohen, R., and D. Zelig. 'Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)', RFC 4842. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.200.1,PW-CEP-STD-MIB::pwCepObjects,,,,,,
.1.3.6.1.2.1.200.1.1,PW-CEP-STD-MIB::pwCepTable,,not-accessible,,current,,This table contains objects and parameters for managing and monitoring the CEP PW.
.1.3.6.1.2.1.200.1.1.1,PW-CEP-STD-MIB::pwCepEntry,,not-accessible,pwIndex,current,,Each entry represents the association of a SONET/SDH path or VT to a PW. This table is indexed by the pwIndex of the applicable PW entry in the pwTable. An entry is created in this table by the agent for every entry in the pwTable with a pwType equal to 'cep'. All read-write objects in this table MAY be changed at any time; however, change of some objects (for example pwCepCfgIndex) during PW forwarding state may cause traffic disruption. Manual entries in this table SHOULD be preserved after a reboot. The agent MUST ensure the integrity of those entries. If the set of entries of a specific row are found to be inconsistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5).
.1.3.6.1.2.1.200.1.1.1.1,PW-CEP-STD-MIB::pwCepType,INTEGER,read-write,,current,spe(1):vt(2):fracSpe(3),Specifies the sub-type of CEP PW. Currently only structured types are supported: 'spe'(1) : SONET STS-Nc signals. 'vt' (2) : SONET VT-x (x=1.5,2,3,6) signals. 'fracSpe' (3) : SONET fractional STS-1 or SDH fractional VC-3 or VC-4 carrying tributaries or asynchronous signals. Support of 'vt' mode or 'fracSpe' mode is optional.
.1.3.6.1.2.1.200.1.1.1.2,PW-CEP-STD-MIB::pwCepSonetIfIndex,Integer32,read-write,,current,,This is a unique index within the ifTable. It represents the interface index for the SONET path for SPE emulation ([RFC3592], Section 3.3), an interface index for the SONET VT ([RFC3592], Section 3.4) if the VT to be emulated is extracted from a SONET signal or locally mapped from a physical interface. A value of zero indicates an interface index that has yet to be determined. Once set, if the SONET ifIndex is (for some reason) later removed, the agent MAY delete the associated PW rows (e.g., this pwCepTableEntry). If the agent does not delete the rows, it is RECOMMENDED that the agent set this object to zero.
.1.3.6.1.2.1.200.1.1.1.3,PW-CEP-STD-MIB::pwCepSonetConfigErrorOrStatus,BITS,read-only,,current,other(0):timeslotInUse(1):timeslotMisuse(2):peerDbaIncompatible(3):peerEbmIncompatible(4):peerRtpIncompatible(5):peerAsyncIncompatible(6):peerDbaAsymmetric(7):peerEbmAsymmetric(8):peerRtpAsymmetric(9):peerAsyncAsymmetric(10),This object reports a configuration mismatch inside the local node or between the local node and the peer node. Some bits indicate an error, and some are simply status reports that do not affect the forwarding process. 'timeslotInUse'(1) is set when another CEP PW has already reserved a timeslot (or timeslots) that this CEP PW is attempting to reserve. 'timeslotMisuse'(2) is set when the stated timeslot this PW is trying to use is not legal, for example, if specifying a starting timeslot of 45 for a SONET path of an STS-12c width. The peerZZZIncompatible bits are set if the local configuration is not compatible with the peer configuration as available from the CEP option received from the peer through the signaling process and the local node cannot support such asymmetric configuration. The peerZZZAsymmetric bits are set if the local configuration is not compatible with the peer configuration as available from the CEP option received from the peer through the signaling process, but the local node can support such asymmetric configuration.
.1.3.6.1.2.1.200.1.1.1.4,PW-CEP-STD-MIB::pwCepCfgIndex,Unsigned32,read-write,,current,,Index to CEP configuration table below. Multiple CEP PWs MAY share a single pwCepCfgEntry. The value 0 indicates that no entries are available.
.1.3.6.1.2.1.200.1.1.1.5,PW-CEP-STD-MIB::pwCepTimeElapsed,Integer32,read-only,,current,,The number of seconds, including partial seconds, that have elapsed since the beginning of the current measurement period. If, for some reason such as an adjustment in the system's time-of-day clock, the current interval exceeds the maximum value, the agent will return the maximum value.
.1.3.6.1.2.1.200.1.1.1.6,PW-CEP-STD-MIB::pwCepValidIntervals,Integer32,read-only,,current,,The number (n) of previous 15-minute intervals for which data was collected. An agent with CEP capability MUST be capable of supporting at least 4 intervals. The RECOMMENDED default value for n is 32, and n MUST NOT exceed 96.
.1.3.6.1.2.1.200.1.1.1.7,PW-CEP-STD-MIB::pwCepIndications,BITS,read-write,,current,missingPkt(0):ooRngDropped(1):jtrBfrUnder(2):pktMalformed(3):lops(4):cepRdi(5):cepAis(6):badHdrStack(7):cepNeFailure(8):cepFeFailure(9),Definitions: 'missingPkt'(0) - While playing out a sequence of packets, at least one packet was determined to be missing based on a gap in the CEP sequence number. Note: If the implementation supports packet reordering, detecting gaps SHOULD take place as they are played out, not as they arrive. This provides time for misordered packets to arrive late. 'ooRngDropped'(1) - At least one packet arrived outside the range of the jitter buffer. This may be because the jitter buffer is full or the sequence number addresses a buffer outside the current jitter buffer range or an already occupied buffer within range. Whether or not packet reordering is supported by the implementation, this indication MUST be supported. 'jtrBfrUnder'(2) - The jitter buffer underflowed because not enough packets arrived as packets were being played out. 'pktMalformed'(3) - Any error related to unexpected packet format (except bad header stack) or unexpected length. 'lops'(4) - Loss of Packet Synchronization. 'cepRdi'(5) - Circuit Emulation over Packet Remote Defect Indication. Remote Defect Indication (RDI) is generated by the remote CEP de-packetizer when LOPS is detected. 'cepAis'(6) - Remote CEP packetizer has detected an Alarm Indication Signal (AIS) on its incoming SONET stream. cepAis MUST NOT (in itself) cause a CEP PW down notification. 'badHdrStack'(7) - Set when the number of CEP header extensions detected in incoming packets does not match the expected number. 'cepNeFailure'(8) - Set when CEP-NE failure is currently declared. 'cepFeFailure'(8) - Set when CEP-FE failure is currently declared. This object MUST hold the accumulated indications until the next SNMP write that clear the indication(s). Writing a non-zero value MUST fail. Currently, there is no hierarchy of CEP defects. The algorithm used to capture these indications is implementation specific.
.1.3.6.1.2.1.200.1.1.1.8,PW-CEP-STD-MIB::pwCepLastEsTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which the CEP PW entered the Errored Seconds (ES) or Severely Errored Seconds (SES) state.
.1.3.6.1.2.1.200.1.1.1.9,PW-CEP-STD-MIB::pwCepPeerCepOption,Unsigned32,read-only,,current,,The value of the CEP option parameter as received from the peer by the PW signaling protocol.
.1.3.6.1.2.1.200.1.2,PW-CEP-STD-MIB::pwCepCfgIndexNext,Unsigned32,read-only,,current,,This object contains an appropriate value to be used for pwCepCfgIndex when creating entries in the pwCepCfgTable. The value 0 indicates that no unassigned entries are available. To obtain the value of pwCepCfgIndex for a new entry in the pwCepCfgTable, the manager issues a management protocol retrieval operation to obtain the current value of pwCepCfgIndex. After each retrieval operation, the agent should modify the value to reflect the next unassigned index. After a manager retrieves a value, the agent will determine through its local policy when this index value will be made available for reuse.
.1.3.6.1.2.1.200.1.3,PW-CEP-STD-MIB::pwCepCfgTable,,not-accessible,,current,,This table contains a set of parameters that may be referenced by one or more CEP PWs by pwCepTable.
.1.3.6.1.2.1.200.1.3.1,PW-CEP-STD-MIB::pwCepCfgEntry,,not-accessible,pwCepCfgTableIndex,current,,These parameters define the characteristics of a CEP PW. They are grouped here to ease Network Management System (NMS) burden. Once an entry is created here, it may be reused by many PWs. By default, all the read-create objects MUST NOT be changed after row activation unless specifically indicated in the individual object description. If the operator wishes to change value of a read-create object, the pwCepCfgRowStatus MUST be set to notInService(2). The agent MUST NOT allow the change of the pwCepCfgRowStatus from the active(1) state for pwCepCfgEntry, which is in use by at least one active PW. Manual entries in this table SHOULD be preserved after a reboot, the agent MUST ensure the integrity of those entries. If the set of entries of a specific row are found to be inconsistent after reboot, the affected PWs' pwOperStatus MUST be declared as notPresent(5).
.1.3.6.1.2.1.200.1.3.1.1,PW-CEP-STD-MIB::pwCepCfgTableIndex,Unsigned32,not-accessible,,current,,Primary index to this table.
.1.3.6.1.2.1.200.1.3.1.2,PW-CEP-STD-MIB::pwCepSonetPayloadLength,Unsigned32,read-create,,current,,The number of SONET bytes of the Path or VT carried as payload within one packet. For example, for STS-1/VC-3 SPE circuits, a value of 783 bytes indicates that each packet carries the payload equivalent to one frame. For VT1.5/VC11 circuits, a payload length of 104 bytes indicates that each packet carries payload equivalent to one VT1.5 super-frame. The actual payload size may be different due to bandwidth reduction modes, e.g., Dynamic Bandwidth Allocation (DBA) mode or dynamically assigned fractional SPE. This length applies to inbound and outbound packets carrying user payload. Although there is no control over inbound packets, those of illegal length are discarded and accounted for (see pwCepPerf...Malformed.) The default values are determined by the pwCepType: 783 for pwCepType equal to spe(2) or fracSpe(3). For vt(3) modes, the applicable super-frame payload size is the default value.
.1.3.6.1.2.1.200.1.3.1.3,PW-CEP-STD-MIB::pwCepCfgMinPktLength,Unsigned32,read-create,,current,,This object defines the minimum CEP packet length in number of bytes (including CEP header and payload). It applies to CEP's bandwidth-savings packets. Currently, DBA is the only bandwidth-savings packet type (in the future, CEP may support compression). Minimum packet length is necessary in some systems or networks. Setting zero here indicates that there is no minimum packet restriction.
.1.3.6.1.2.1.200.1.3.1.4,PW-CEP-STD-MIB::pwCepCfgPktReorder,INTEGER,read-only,,current,true(1):false(2),This object defines if reordering is applied for incoming packets. If set 'true', as inbound packets are queued in the jitter buffer, out-of-order packets are reordered. The maximum sequence number differential (i.e., the range in which resequencing can occur) is dependant on the depth of the jitter buffer. If the local agent supports packet reordering, the default value SHOULD be set to 'true'; otherwise, this value SHOULD be set to 'false'.
.1.3.6.1.2.1.200.1.3.1.5,PW-CEP-STD-MIB::pwCepCfgEnableDBA,BITS,read-create,,current,ais(0):unequipped(1),This object defines when DBA is applied for packets sent toward the PSN. Setting 'ais' MUST cause CEP packet payload suppression when AIS is detected on the associated SONET path. Similarly, 'unequipped' MUST cause payload suppression when an unequipped condition is detected on the SONET/SDH PATH/VT. During DBA condition, CEP packets will continue to be sent, but with indicators set in the CEP header instructing the remote to play all ones (for AIS) or all zeros (for unequipped) onto its SONET/SDH path. NOTE: Some implementations may not support this feature. In these cases, this object should be read-only.
.1.3.6.1.2.1.200.1.3.1.6,PW-CEP-STD-MIB::pwCepCfgRtpHdrSuppress,INTEGER,read-create,,current,true(1):false(2),If this object is set to 'true', an RTP header is not prepended to the CEP packet.
.1.3.6.1.2.1.200.1.3.1.7,PW-CEP-STD-MIB::pwCepCfgJtrBfrDepth,Unsigned32,read-create,,current,,This object defines the number of microseconds of expected packet delay variation for this CEP PW over the PSN. The actual jitter buffer MUST be at least twice this value for proper operation. If configured to a value not supported by the implementation, the agent MUST reject the SNMP Set operation.
.1.3.6.1.2.1.200.1.3.1.8,PW-CEP-STD-MIB::pwCepCfgConsecPktsInsync,Unsigned32,read-create,,current,,Consecutive packets with sequential sequence numbers required to exit the LOPS state.
.1.3.6.1.2.1.200.1.3.1.9,PW-CEP-STD-MIB::pwCepCfgConsecMissingOutSync,Unsigned32,read-create,,current,,Consecutive missing packets required to enter the LOPS state.
.1.3.6.1.2.1.200.1.3.1.10,PW-CEP-STD-MIB::pwCepCfgPktErrorPlayOutValue,Unsigned32,read-create,,current,,This object defines the value played when inbound packets have over/underflowed the jitter buffer or are missing for any reason. This byte pattern is sent (played) on the SONET path.
.1.3.6.1.2.1.200.1.3.1.11,PW-CEP-STD-MIB::pwCepCfgMissingPktsToSes,Unsigned32,read-create,,current,,The number of missing packets detected (consecutive or not) within a 1-second window to cause a Severely Errored Second (SES) to be counted.
.1.3.6.1.2.1.200.1.3.1.12,PW-CEP-STD-MIB::pwCepCfgSesToUas,Unsigned32,read-create,,current,,The number of consecutive SESs before declaring PW in Unavailable Seconds (UAS) state (at which point pwCepPerfUASs starts counting). The SesToUas default value is 10 seconds. NOTE: Similar to [RFC3592], if the agent chooses to update the various performance statistics in real time, it MUST be prepared to retroactively reduce the ES and SES counts by this value and increase the UAS count by this value when it determines that UAS state has been entered. NOTE: See pwCepPerfSESs and pwCepPerfUASs.
.1.3.6.1.2.1.200.1.3.1.13,PW-CEP-STD-MIB::pwCepCfgSecsToExitUas,Unsigned32,read-create,,current,,The number of consecutive nonSESs before declaring PW is NOT in UAS state (at which point pwCepPerfUASs stops counting).
.1.3.6.1.2.1.200.1.3.1.14,PW-CEP-STD-MIB::pwCepCfgName,OCTET,read-create,,current,,This variable contains the name of the Configuration entry. This name may be used to help the NMS to display the purpose of the entry.
.1.3.6.1.2.1.200.1.3.1.15,PW-CEP-STD-MIB::pwCepCfgRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. None of the read-create objects' values can be changed when pwCepCfgRowStatus is in the active(1) state. Changes are allowed when the pwRowStatus is in notInService(2) or notReady(3) states only. If the operator needs to change one of the values for an active row (for example, in order to fix a mismatch in configuration between the local node and the peer), the pwCepCfgRowStatus should be first changed to notInService(2). The objects may be changed now and later changed to active(1) in order to re-initiate the signaling process with the new values in effect. Change of status from the active(1) state or deleting a row SHOULD be blocked by the local agent if the row is referenced by any pwCepEntry those pwRowStatus is in the active(1) state.
.1.3.6.1.2.1.200.1.3.1.16,PW-CEP-STD-MIB::pwCepCfgStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the storage type for this row.
.1.3.6.1.2.1.200.1.4,PW-CEP-STD-MIB::pwCepFracTable,,not-accessible,,current,,This table contains a set of parameters for CEP PWs with pwCepType FRAC type.
.1.3.6.1.2.1.200.1.4.1,PW-CEP-STD-MIB::pwCepFracEntry,,not-accessible,pwCepFracIndex,current,,There are two options for creating an entry in this table: - By the Element Management System (EMS) in advance for creating the PW. - By the agent automatically when the PW is set up. The first option is typically used when there is a native service processing (NSP) cross-connect option between the physical ports and the emulated (virtual ports), while the second MAY be used when there is a one-to-one mapping between the emulated signal and the physical signal.
.1.3.6.1.2.1.200.1.4.1.1,PW-CEP-STD-MIB::pwCepFracIndex,Integer32,not-accessible,,current,,This is the index of this table. It is a unique index within the ifTable. It represents the interface index for the SONET path ([RFC3592], Section 3.3) for fractional SPE emulation. It may represent an internal (virtual) interface if an NSP function exists between the physical interface and the emulation process.
.1.3.6.1.2.1.200.1.4.1.2,PW-CEP-STD-MIB::pwCepFracMode,INTEGER,read-create,,current,notApplicable(1):dynamic(2):static(3):staticWithEbm(4):staticAsync(5),Fractional mode for STS-1/VC-3 or VC-4 circuits: notApplicable - When this object is not applicable. dynamic - EBM carried within the CEP header. Unequipped VTs are removed from the payload on the fly. static - EBM not carried within the CEP header. Only VTs defined in the EBM are carried within the payload. staticWithEbm - EBM carried within the CEP header. Only VTs defined in the EBM are carried within the payload. staticAsync - Asynchronous E3/T3 fixed byte removal only.
.1.3.6.1.2.1.200.1.4.1.3,PW-CEP-STD-MIB::pwCepFracConfigError,BITS,read-only,,current,other(0):vtgMapEbmConflict(1):vtgMapAsyncConflict(2),vtgMapEbmConflict(1) is set when the configured static EBM does not match the configured vtgMap for fractional STS-1/VC-3 circuits or when the TUG2Map is in conflict with the static EBM for VC-4 circuits, for example, if the vtgMap specifies that VTG#1 carries VT2 VTs while the EBM indicate that four VTs are equipped within VTG#1. vtgMapAsyncConflict(2) is set when there is a conflict between the mode, the async indication, and the vtgMap fields. For example, fractional mode is set to staticAsync while the VtgMap indicates that the STS-1/VC-3 carries VTs, or both async1 and Tug2Map are set in fractional VC-4 circuits.
.1.3.6.1.2.1.200.1.4.1.4,PW-CEP-STD-MIB::pwCepFracAsync,INTEGER,read-create,,current,other(1):ds3(2):e3(3),This object defines the asynchronous payload carried within the STS-1/VC-3. This object is applicable when pwCepFracMode equals 'staticAsync' and MUST equal to 'other' otherwise.
.1.3.6.1.2.1.200.1.4.1.5,PW-CEP-STD-MIB::pwCepFracVtgMap,Unsigned32,read-create,,current,,This object defines the VT/VC types of the seven VTG/TUG-2 within the STS-1/VC-3. This variable should be set when 'dynamic', 'static', or 'staticWithEbm' fractional STS-1/VC-3 pwCepFracMode is selected.
.1.3.6.1.2.1.200.1.4.1.6,PW-CEP-STD-MIB::pwCepFracEbm,Unsigned32,read-create,,current,,This object holds the static Equipped Bit Mask (EBM) for STS-1/VC-3 channel. This variable MAY be set when 'static' or 'staticWithEbm' fractional STS-1/VC-3 pwCepFracMode is selected. It is possible that the configuration of other MIB modules will define the EBM value; in these cases, this object is read-only and reflects the actual EBM that would be used.
.1.3.6.1.2.1.200.1.4.1.7,PW-CEP-STD-MIB::pwCepFracPeerEbm,Unsigned32,read-only,,current,,This object reports the Equipped Bit Mask (EBM) for STS-1/VC-3 channel as received from the peer within the CEP extension header.
.1.3.6.1.2.1.200.1.4.1.8,PW-CEP-STD-MIB::pwCepFracSdhVc4Mode,INTEGER,read-create,,current,notApplicable(1):dynamic(2):static(3):staticWithEbm(4),Fractional mode for VC-4 circuits: notApplicable - When this is not VC-4 circuit. dynamic - EBM carried within the CEP header. Unequipped VTs are removed from the payload on the fly. static - EBM not carried within the CEP header. Only VTs defined in the EBM are carried within the payload. staticWithEbm - EBM carried within the CEP header. Only VTs defined in the EBM are carried within the payload.
.1.3.6.1.2.1.200.1.4.1.9,PW-CEP-STD-MIB::pwCepFracSdhVc4Tu3Map1,INTEGER,read-create,,current,other(1):ds3(2):e3(3),The type of asynchronous mapping carried inside STS-1, VC-3, or TUG-3 containing TU-3 circuit.
.1.3.6.1.2.1.200.1.4.1.10,PW-CEP-STD-MIB::pwCepFracSdhVc4Tu3Map2,INTEGER,read-create,,current,other(1):ds3(2):e3(3),If the second TUG-3 within the VC-4 contains a TU-3, this variable must be set.
.1.3.6.1.2.1.200.1.4.1.11,PW-CEP-STD-MIB::pwCepFracSdhVc4Tu3Map3,INTEGER,read-create,,current,other(1):ds3(2):e3(3),If the third TUG-3 within the VC-4 contains a TU-3, this variable must be set.
.1.3.6.1.2.1.200.1.4.1.12,PW-CEP-STD-MIB::pwCepFracSdhVc4Tug2Map1,Unsigned32,read-create,,current,,The VC types of the seven TUG-2s within the first TUG-3 of the VC-4.
.1.3.6.1.2.1.200.1.4.1.13,PW-CEP-STD-MIB::pwCepFracSdhVc4Tug2Map2,Unsigned32,read-create,,current,,The VC types of the seven TUG-2s within the second TUG-3 of the VC-4.
.1.3.6.1.2.1.200.1.4.1.14,PW-CEP-STD-MIB::pwCepFracSdhVc4Tug2Map3,Unsigned32,read-create,,current,,The VC types of the seven TUG-2s within the third TUG-3 of the VC-4.
.1.3.6.1.2.1.200.1.4.1.15,PW-CEP-STD-MIB::pwCepFracSdhVc4Ebm1,Unsigned32,read-create,,current,,Static Equipped Bit Mask (EBM) for the first TUG-3 within the VC-4. This variable should be set when 'static' or 'staticWithEbm' fractional VC-4 pwCepFracMode is selected. It is possible that the EBM that would be used is available based on configuration of other MIB modules. In these cases, this object is read-only and reflects the actual EBM that would be used.
.1.3.6.1.2.1.200.1.4.1.16,PW-CEP-STD-MIB::pwCepFracSdhVc4Ebm2,Unsigned32,read-create,,current,,Static Equipped Bit Mask (EBM) for the second TUG-3 within the VC-4. This variable should be set when 'static' or 'staticWithEbm' fractional VC-4 pwCepFracMode is selected. It is possible that the EBM that would be used is available based on configuration of other MIB modules. In these cases, this object is read-only and reflects the actual EBM that would be used.
.1.3.6.1.2.1.200.1.4.1.17,PW-CEP-STD-MIB::pwCepFracSdhVc4Ebm3,Unsigned32,read-create,,current,,Static Equipped Bit Mask (EBM) for the third TUG-3 within the VC-4. This variable should be set when 'Static' or 'staticWithEbm' fractional VC-4 pwCepFracMode is selected. It is possible that the EBM that would be used is available based on configuration of other MIB modules. In these cases, this object is read-only and reflects the actual EBM that would be used.
.1.3.6.1.2.1.200.1.4.1.18,PW-CEP-STD-MIB::pwCepFracSdhVc4PeerEbm1,Unsigned32,read-only,,current,,Equipped Bit Mask (EBM) for the first TUG-3 within the fractional VC-4 channel received from the peer within the CEP extension header.
.1.3.6.1.2.1.200.1.4.1.19,PW-CEP-STD-MIB::pwCepFracSdhVc4PeerEbm2,Unsigned32,read-only,,current,,Equipped Bit Mask (EBM) for the second TUG-3 within the fractional VC-4 channel received from the peer within the CEP extension header.
.1.3.6.1.2.1.200.1.4.1.20,PW-CEP-STD-MIB::pwCepFracSdhVc4PeerEbm3,Unsigned32,read-only,,current,,Equipped Bit Mask (EBM) for the third TUG-3 within the fractional VC-4 channel received from the peer within the CEP extension header.
.1.3.6.1.2.1.200.1.4.1.21,PW-CEP-STD-MIB::pwCepFracRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),For creating, modifying, and deleting this row. This object MAY be changed at any time.
.1.3.6.1.2.1.200.1.4.1.22,PW-CEP-STD-MIB::pwCepFracStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object.
.1.3.6.1.2.1.200.1.5,PW-CEP-STD-MIB::pwCepPerfCurrentTable,,not-accessible,,current,,CEP bridges the SONET and packet worlds. In the packet world, counts typically start from the time of service creation and do not stop. In the SONET world, counts are kept in 15-minute intervals. The PW CEP MIB supports both methods. The current 15-minute interval counts are in this table. The interval and total stats are in tables following this. This table provides per-CEP PW performance information. High capacity (HC) counters are required for some counts due to the high speeds expected with CEP services. A SONET path of width 48 (STS-48c) can rollover non-HC counters in a few minutes.
.1.3.6.1.2.1.200.1.5.1,PW-CEP-STD-MIB::pwCepPerfCurrentEntry,,not-accessible,pwIndex,current,,An entry in this table is created by the agent for every pwCep entry. After 15 minutes, the contents of this table entry are copied to a new entry in the pwCepPerfInterval table, and the counts in this entry are reset to zero.
.1.3.6.1.2.1.200.1.5.1.1,PW-CEP-STD-MIB::pwCepPerfCurrentDbaInPacketsHC,Counter64,read-only,,current,,Number of DBA packets received.
.1.3.6.1.2.1.200.1.5.1.2,PW-CEP-STD-MIB::pwCepPerfCurrentDbaOutPacketsHC,Counter64,read-only,,current,,Number of DBA packets sent.
.1.3.6.1.2.1.200.1.5.1.3,PW-CEP-STD-MIB::pwCepPerfCurrentInNegPtrAdjust,Gauge32,read-only,,current,,Number of negative pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
.1.3.6.1.2.1.200.1.5.1.4,PW-CEP-STD-MIB::pwCepPerfCurrentInPosPtrAdjust,Gauge32,read-only,,current,,Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
.1.3.6.1.2.1.200.1.5.1.5,PW-CEP-STD-MIB::pwCepPerfCurrentInPtrAdjustSecs,Gauge32,read-only,,current,,Number of seconds in which a positive or negative pointer adjustment was sent on the SONET path.
.1.3.6.1.2.1.200.1.5.1.6,PW-CEP-STD-MIB::pwCepPerfCurrentOutNegPtrAdjust,Gauge32,read-only,,current,,Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
.1.3.6.1.2.1.200.1.5.1.7,PW-CEP-STD-MIB::pwCepPerfCurrentOutPosPtrAdjust,Gauge32,read-only,,current,,Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
.1.3.6.1.2.1.200.1.5.1.8,PW-CEP-STD-MIB::pwCepPerfCurrentOutPtrAdjustSecs,Gauge32,read-only,,current,,Number of seconds in which a positive or negative pointer adjustment was seen on the SONET path.
.1.3.6.1.2.1.200.1.5.1.9,PW-CEP-STD-MIB::pwCepPerfCurrentAbsPtrAdjust,Integer32,read-only,,current,,Indicates the relative adjustment drift between inbound and outbound streams. It is calculated as absolute value of: (InPosPtrAdjust - InNegPtrAdjust ) - (OutPosPtrAdjust - OutNegPtrAdjust)
.1.3.6.1.2.1.200.1.5.1.10,PW-CEP-STD-MIB::pwCepPerfCurrentMissingPkts,Gauge32,read-only,,current,,Number of missing packets (as detected via CEP header sequence number gaps).
.1.3.6.1.2.1.200.1.5.1.11,PW-CEP-STD-MIB::pwCepPerfCurrentPktsOoseq,Gauge32,read-only,,current,,Number of packets detected out of sequence (via CEP header sequence numbers) but successfully reordered. Note: Some implementations may not support this feature (see pwCepCfgPktReorder).
.1.3.6.1.2.1.200.1.5.1.12,PW-CEP-STD-MIB::pwCepPerfCurrentPktsOoRngDropped,Gauge32,read-only,,current,,Number of packets detected out of range (via CEP header sequence numbers) and could not be reordered or could not fit in the jitter buffer.
.1.3.6.1.2.1.200.1.5.1.13,PW-CEP-STD-MIB::pwCepPerfCurrentJtrBfrUnderruns,Gauge32,read-only,,current,,Number of times a packet needed to be played out and the jitter buffer was empty.
.1.3.6.1.2.1.200.1.5.1.14,PW-CEP-STD-MIB::pwCepPerfCurrentPktsMalformed,Gauge32,read-only,,current,,Number of packets detected with unexpected size or bad headers stack.
.1.3.6.1.2.1.200.1.5.1.15,PW-CEP-STD-MIB::pwCepPerfCurrentSummaryErrors,Gauge32,read-only,,current,,A summary of all the packet-error types above (from missing packets to bad length packets).
.1.3.6.1.2.1.200.1.5.1.16,PW-CEP-STD-MIB::pwCepPerfCurrentESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered.
.1.3.6.1.2.1.200.1.5.1.17,PW-CEP-STD-MIB::pwCepPerfCurrentSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered.
.1.3.6.1.2.1.200.1.5.1.18,PW-CEP-STD-MIB::pwCepPerfCurrentUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered.
.1.3.6.1.2.1.200.1.5.1.19,PW-CEP-STD-MIB::pwCepPerfCurrentFC,Gauge32,read-only,,current,,CEP Failure Counts (FC-CEP). The number of CEP failure events. A failure event begins when the LOPS failure is declared and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.
.1.3.6.1.2.1.200.1.6,PW-CEP-STD-MIB::pwCepPerfIntervalTable,,not-accessible,,current,,This table provides per-CEP PW performance information, much like the pwCepPerfCurrentTable above. However, these counts represent historical 15-minute intervals. Typically, this table will have a maximum of 96 entries for a 24-hour period but is not limited to this. NOTE: Counter64 objects are used here; Counter32 is too small for OC-768 CEP PWs.
.1.3.6.1.2.1.200.1.6.1,PW-CEP-STD-MIB::pwCepPerfIntervalEntry,,not-accessible,pwIndex:pwCepPerfIntervalNumber,current,,An entry in this table is created by the agent for every pwCepPerfCurrentEntry that is 15 minutes old. The contents of the Current entry are copied to the new entry here. The Current entry then resets its counts to zero for the next current 15-minute interval. pwCepIndex is found in the pwCepCfg table.
.1.3.6.1.2.1.200.1.6.1.1,PW-CEP-STD-MIB::pwCepPerfIntervalNumber,Integer32,not-accessible,,current,,A number (between 1 and 96 to cover a 24-hour period) that identifies the interval for which the set of statistics is available. The interval identified by 1 is the most recently completed 15-minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1. The minimum range of N is 1 through 4. The default range is 1 through 32. The maximum range of N is 1 through 96.
.1.3.6.1.2.1.200.1.6.1.2,PW-CEP-STD-MIB::pwCepPerfIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.200.1.6.1.3,PW-CEP-STD-MIB::pwCepPerfIntervalReset,INTEGER,read-create,,current,reset(1):normal(2),Used in cases where the user knows that the errors within this interval should not be counted. Writing 'reset' sets all error counts to zero. The value of 0 is not used here due to issues with implementations.
.1.3.6.1.2.1.200.1.6.1.4,PW-CEP-STD-MIB::pwCepPerfIntervalTimeElapsed,Integer32,read-only,,current,,The duration of a particular interval in seconds. Adjustments in the system's time-of-day clock may cause the interval to be greater or less than the normal value. Therefore, this actual interval value is provided.
.1.3.6.1.2.1.200.1.6.1.5,PW-CEP-STD-MIB::pwCepPerfIntervalDbaInPacketsHC,Counter64,read-only,,current,,Number of DBA packets received.
.1.3.6.1.2.1.200.1.6.1.6,PW-CEP-STD-MIB::pwCepPerfIntervalDbaOutPacketsHC,Counter64,read-only,,current,,Number of DBA packets sent.
.1.3.6.1.2.1.200.1.6.1.7,PW-CEP-STD-MIB::pwCepPerfIntervalInNegPtrAdjust,Gauge32,read-only,,current,,Number of negative pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
.1.3.6.1.2.1.200.1.6.1.8,PW-CEP-STD-MIB::pwCepPerfIntervalInPosPtrAdjust,Gauge32,read-only,,current,,Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
.1.3.6.1.2.1.200.1.6.1.9,PW-CEP-STD-MIB::pwCepPerfIntervalInPtrAdjustSecs,Gauge32,read-only,,current,,Number of seconds in which a positive or negative pointer adjustment was sent on the SONET path.
.1.3.6.1.2.1.200.1.6.1.10,PW-CEP-STD-MIB::pwCepPerfIntervalOutNegPtrAdjust,Gauge32,read-only,,current,,Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
.1.3.6.1.2.1.200.1.6.1.11,PW-CEP-STD-MIB::pwCepPerfIntervalOutPosPtrAdjust,Gauge32,read-only,,current,,Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
.1.3.6.1.2.1.200.1.6.1.12,PW-CEP-STD-MIB::pwCepPerfIntervalOutPtrAdjustSecs,Gauge32,read-only,,current,,Number of seconds in which a positive or negative pointer adjustment was seen on the SONET path.
.1.3.6.1.2.1.200.1.6.1.13,PW-CEP-STD-MIB::pwCepPerfIntervalAbsPtrAdjust,Integer32,read-only,,current,,The relative adjustment drift between inbound and outbound streams. It is calculated as absolute value of: (InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)
.1.3.6.1.2.1.200.1.6.1.14,PW-CEP-STD-MIB::pwCepPerfIntervalMissingPkts,Gauge32,read-only,,current,,Number of missing packets (as detected via CEP header sequence number gaps).
.1.3.6.1.2.1.200.1.6.1.15,PW-CEP-STD-MIB::pwCepPerfIntervalPktsOoseq,Gauge32,read-only,,current,,Number of packets detected out of sequence (via CEP header sequence numbers) but successfully reordered. Note: Some implementations mat not support this feature (see pwCepCfgPktReorder).
.1.3.6.1.2.1.200.1.6.1.16,PW-CEP-STD-MIB::pwCepPerfIntervalPktsOoRngDropped,Gauge32,read-only,,current,,Number of packets detected out of range (via CEP header sequence numbers) and could not be reordered or could not fit in the jitter buffer.
.1.3.6.1.2.1.200.1.6.1.17,PW-CEP-STD-MIB::pwCepPerfIntervalJtrBfrUnderruns,Gauge32,read-only,,current,,Number of times a packet needed to be played out and the jitter buffer was empty.
.1.3.6.1.2.1.200.1.6.1.18,PW-CEP-STD-MIB::pwCepPerfIntervalPktsMalformed,Gauge32,read-only,,current,,Number of packets detected with unexpected size or bad headers stack.
.1.3.6.1.2.1.200.1.6.1.19,PW-CEP-STD-MIB::pwCepPerfIntervalSummaryErrors,Gauge32,read-only,,current,,A summary of all the packet-error types above (from missing packets to bad length packets).
.1.3.6.1.2.1.200.1.6.1.20,PW-CEP-STD-MIB::pwCepPerfIntervalESs,Gauge32,read-only,,current,,The counter associated with the number of Errored Seconds encountered.
.1.3.6.1.2.1.200.1.6.1.21,PW-CEP-STD-MIB::pwCepPerfIntervalSESs,Gauge32,read-only,,current,,The counter associated with the number of Severely Errored Seconds encountered.
.1.3.6.1.2.1.200.1.6.1.22,PW-CEP-STD-MIB::pwCepPerfIntervalUASs,Gauge32,read-only,,current,,The counter associated with the number of Unavailable Seconds encountered.
.1.3.6.1.2.1.200.1.6.1.23,PW-CEP-STD-MIB::pwCepPerfIntervalFC,Gauge32,read-only,,current,,CEP Failure Counts (FC-CEP). The number of CEP failure events. A failure event begins when the LOPS failure is declared and ends when the failure is cleared. A failure event that begins in one period and ends in another period is counted only in the period in which it begins.
.1.3.6.1.2.1.200.1.7,PW-CEP-STD-MIB::pwCepPerf1DayIntervalTable,,not-accessible,,current,,This table provides per CEP PW performance information, the current day's measurement, and the previous day's interval. In the extreme case where one of the error counters has overflowed during the one-day interval, the error counter MUST NOT wrap around and MUST return the maximum value.
.1.3.6.1.2.1.200.1.7.1,PW-CEP-STD-MIB::pwCepPerf1DayIntervalEntry,,not-accessible,pwIndex:pwCepPerf1DayIntervalNumber,current,,An entry is created in this table by the agent for every entry in the pwCepTable and for each day interval up to the number of supported historical intervals.
.1.3.6.1.2.1.200.1.7.1.1,PW-CEP-STD-MIB::pwCepPerf1DayIntervalNumber,Unsigned32,not-accessible,,current,,History Data Interval number. Interval 1 is the current day measurement period; interval 2 is the most recent previous day; and interval 30 is 31 days ago.
.1.3.6.1.2.1.200.1.7.1.2,PW-CEP-STD-MIB::pwCepPerf1DayIntervalValidData,INTEGER,read-only,,current,true(1):false(2),This variable indicates if the data for this interval is valid.
.1.3.6.1.2.1.200.1.7.1.3,PW-CEP-STD-MIB::pwCepPerf1DayIntervalMoniSecs,Integer32,read-only,,current,,The amount of time in the 1-day interval over which the performance monitoring information is actually counted. This value will be the same as the interval duration except in situations where performance monitoring data could not be collected for any reason or the agent clock was adjusted.
.1.3.6.1.2.1.200.1.7.1.4,PW-CEP-STD-MIB::pwCepPerf1DayIntervalDbaInPacketsHC,Counter64,read-only,,current,,Number of DBA packets received.
.1.3.6.1.2.1.200.1.7.1.5,PW-CEP-STD-MIB::pwCepPerf1DayIntervalDbaOutPacketsHC,Counter64,read-only,,current,,Number of DBA packets sent.
.1.3.6.1.2.1.200.1.7.1.6,PW-CEP-STD-MIB::pwCepPerf1DayIntervalInNegPtrAdjust,Counter32,read-only,,current,,Number of negative pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
.1.3.6.1.2.1.200.1.7.1.7,PW-CEP-STD-MIB::pwCepPerf1DayIntervalInPosPtrAdjust,Counter32,read-only,,current,,Number of positive pointer adjustments sent on the SONET path based on CEP pointer adjustments received.
.1.3.6.1.2.1.200.1.7.1.8,PW-CEP-STD-MIB::pwCepPerf1DayIntervalInPtrAdjustSecs,Counter32,read-only,,current,,Number of seconds in which a positive or negative pointer adjustment was sent on the SONET path.
.1.3.6.1.2.1.200.1.7.1.9,PW-CEP-STD-MIB::pwCepPerf1DayIntervalOutNegPtrAdjust,Counter32,read-only,,current,,Number of negative pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
.1.3.6.1.2.1.200.1.7.1.10,PW-CEP-STD-MIB::pwCepPerf1DayIntervalOutPosPtrAdjust,Counter32,read-only,,current,,Number of positive pointer adjustments seen on the SONET path and encoded onto sent CEP packets.
.1.3.6.1.2.1.200.1.7.1.11,PW-CEP-STD-MIB::pwCepPerf1DayIntervalOutPtrAdjustSecs,Counter32,read-only,,current,,Number of seconds in which a positive or negative pointer adjustment was seen on the SONET path.
.1.3.6.1.2.1.200.1.7.1.12,PW-CEP-STD-MIB::pwCepPerf1DayIntervalAbsPtrAdjust,Integer32,read-only,,current,,The relative adjustment of drift between inbound and outbound streams. It is calculated as absolute value of: (InPosPtrAdjust - InNegPtrAdjust) - (OutPosPtrAdjust - OutNegPtrAdjust)
.1.3.6.1.2.1.200.1.7.1.13,PW-CEP-STD-MIB::pwCepPerf1DayIntervalMissingPkts,Counter32,read-only,,current,,Number of missing packets (as detected via CEP header sequence number gaps).
.1.3.6.1.2.1.200.1.7.1.14,PW-CEP-STD-MIB::pwCepPerf1DayIntervalPktsOoseq,Counter32,read-only,,current,,Number of packets detected out of sequence (via CEP header sequence numbers) but successfully reordered. Note: Some implementations may not support this feature (see pwCepCfgPktReorder).
.1.3.6.1.2.1.200.1.7.1.15,PW-CEP-STD-MIB::pwCepPerf1DayIntervalPktsOoRngDropped,Counter32,read-only,,current,,Number of packets detected out of range (via CEP header sequence numbers) and could not be reordered or could not fit in the jitter buffer.
.1.3.6.1.2.1.200.1.7.1.16,PW-CEP-STD-MIB::pwCepPerf1DayIntervalJtrBfrUnderruns,Counter32,read-only,,current,,Number of times a packet needed to be played out, and the jitter buffer was empty.
.1.3.6.1.2.1.200.1.7.1.17,PW-CEP-STD-MIB::pwCepPerf1DayIntervalPktsMalformed,Counter32,read-only,,current,,Number of packets detected with unexpected size or bad headers stack.
.1.3.6.1.2.1.200.1.7.1.18,PW-CEP-STD-MIB::pwCepPerf1DayIntervalSummaryErrors,Counter32,read-only,,current,,A summary of all the packet-error types above (from missing packets to bad length packets).
.1.3.6.1.2.1.200.1.7.1.19,PW-CEP-STD-MIB::pwCepPerf1DayIntervalESs,Counter32,read-only,,current,,The counter associated with the number of Errored Seconds encountered.
.1.3.6.1.2.1.200.1.7.1.20,PW-CEP-STD-MIB::pwCepPerf1DayIntervalSESs,Counter32,read-only,,current,,The counter associated with the number of Severely Errored Seconds. See pwCepCfgMissingPktsToSes.
.1.3.6.1.2.1.200.1.7.1.21,PW-CEP-STD-MIB::pwCepPerf1DayIntervalUASs,Counter32,read-only,,current,,The counter associated with the number of unavailable seconds. See pwCepCfgSesToUAS. NOTE: When first entering the UAS state, the number of SesToUas is added to this object; then, as each additional UAS occurs, this object increments by one. NOTE: Similar to [RFC3592], if the agent chooses to update the various performance statistics in real time, it must be prepared to retroactively reduce the ES and SES counts (by the value of pwCepCfgSesToUas) and increase the UAS count (by that same value) when it determines that UAS state has been entered.
.1.3.6.1.2.1.200.1.7.1.22,PW-CEP-STD-MIB::pwCepPerf1DayIntervalFC,Counter32,read-only,,current,,CEP Failure Counts (FC-CEP). The number of CEP failure events. A failure event begins when the LOPS failure is declared and ends when the failure is cleared.
.1.3.6.1.2.1.200.2,PW-CEP-STD-MIB::pwCepConformance,,,,,,
.1.3.6.1.2.1.200.2.1,PW-CEP-STD-MIB::pwCepGroups,,,,,,
.1.3.6.1.2.1.200.2.1.1,PW-CEP-STD-MIB::pwCepGroup,,,,,,Collection of objects for basic CEP PW config and status.
.1.3.6.1.2.1.200.2.1.2,PW-CEP-STD-MIB::pwCepSignalingGroup,,,,,,Collection of objects required if the network element support CEP connections signaling.
.1.3.6.1.2.1.200.2.1.3,PW-CEP-STD-MIB::pwCepCfgGroup,,,,,,Collection of detailed objects needed to configure CEP PWs.
.1.3.6.1.2.1.200.2.1.4,PW-CEP-STD-MIB::pwCepPerfCurrentGroup,,,,,,Collection of statistics objects for CEP PWs.
.1.3.6.1.2.1.200.2.1.5,PW-CEP-STD-MIB::pwCepPerfIntervalGroup,,,,,,Collection of statistics objects for CEP PWs.
.1.3.6.1.2.1.200.2.1.6,PW-CEP-STD-MIB::pwCepPerf1DayIntervalGroup,,,,,,Collection of statistics objects for CEP PWs.
.1.3.6.1.2.1.200.2.1.7,PW-CEP-STD-MIB::pwCepFractionalGroup,,,,,,Collection of fractional SPE objects. These objects are optional and should be supported only if fractional SPE is supported within the network element.
.1.3.6.1.2.1.200.2.1.8,PW-CEP-STD-MIB::pwCepFractionalSts1Vc3Group,,,,,,Collection of fractional STS-1/VC3 objects. These objects are optional and should be supported only if fractional STS-1/VC3 is supported within the network element.
.1.3.6.1.2.1.200.2.1.9,PW-CEP-STD-MIB::pwCepFractionalVc4Group,,,,,,Collection of fractional VC4 objects. These objects are optional and should be supported only if fractional VC4 is supported within the network element.
.1.3.6.1.2.1.200.2.2,PW-CEP-STD-MIB::pwCepCompliances,,,,,,
.1.3.6.1.2.1.200.2.2.1,PW-CEP-STD-MIB::pwCepModuleFullCompliance,,,,,,The compliance statement for agents that support full CEP PW configuration through this MIB module.
.1.3.6.1.2.1.200.2.2.2,PW-CEP-STD-MIB::pwCepModuleReadOnlyCompliance,,,,,,The compliance statement for agents that provide read-only support for the PW CEP MIB Module. Such devices can be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.201,FLOAT-TC-MIB::floatTcMIB,,,,,,Textual conventions for the representation of floating-point numbers. Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 6340; see the RFC itself for full legal notices.
.1.3.6.1.2.1.202,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralMIB,,,,,,Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB module contains generic object definitions for MPLS Traffic Engineering Fast Reroute as defined in RFC 4090.
.1.3.6.1.2.1.202.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralObjects,,,,,,
.1.3.6.1.2.1.202.1.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralProtectionMethod,INTEGER,read-write,,current,unknown(1):oneToOneBackup(2):facilityBackup(3),Indicates which protection method is to be used for fast reroute on this device. Some devices may require a reboot if this variable is to take effect after being modified.
.1.3.6.1.2.1.202.1.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralIngressTunnelInstances,Counter32,read-only,,current,,The number of tunnel instances for either detour LSPs or bypass tunnels for which this LSR is the ingress.
.1.3.6.1.2.1.202.1.3,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsTable,,not-accessible,,current,,This table shows detour LSP or bypass tunnel setup constraints.
.1.3.6.1.2.1.202.1.3.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsEntry,,not-accessible,mplsFrrGeneralConstraintsIfIndexOrZero:mplsFrrGeneralConstraintsTunnelIndex:mplsFrrGeneralConstraintsTunnelInstance,current,,An entry in this table represents detour LSP or bypass tunnel setup constraints for an interface or link to be protected by detour LSPs or a bypass tunnel. Once the LSP or tunnel instance to be protected is identified in the mplsTunnelTable, the corresponding mplsTunnelIfIndex value of that tunnel can be used to get the ifIndex of the underlying physical interface using the ifStackTable. That ifIndex of the underlying physical interface will be used as mplsFrrGeneralConstraintsIfIndexOrZero in this table to protect the LSPs or tunnel instances determined earlier. It is recommended that ifIndex persistence be enabled across re-initializations. If persistence is not implemented, then the value of mplsFrrGeneralConstraintsIfIndexOrZero in this table cannot be guaranteed across restarts and all entries in this table MUST NOT be persistent, or the values of mplsFrrGeneralConstraintsIfIndexOrZero MUST be reconstructed on restart. SNMP engines must only allow entries in this table to be created for tunnel instances that require fast reroute as indicated by the presence of the FAST_REROUTE object in the signaling for the LSP in question. An entry in this table can be created only if a corresponding entry in mplsTunnelTable exists with the same mplsTunnelIndex as mplsFrrGeneralConstraintsTunnelIndex. Entries in this table are deleted when the corresponding entries in mplsTunnelTable are deleted. It is recommended that entries in this table be persistent across reboots. Entries indexed with mplsFrrGeneralConstraintsIfIndexOrZero and set to 0 apply to all interfaces on this device for which the FRR feature can operate. If the mplsTunnelInstance object is set to a value of 0, it indicates that the mplsTunnelEntry contains a tunnel ingress. This is typically how configuration of this feature is performed on devices where the actual protection LSP used is left up to the protecting tunnel. However, in cases where static configuration is possible, any valid tunnel instance is possible; however, it is strongly RECOMMENDED that the instance index SHOULD use the following convention to identify backup LSPs: - lower 16 bits : protected tunnel instance - higher 16 bits: must be all zeros
.1.3.6.1.2.1.202.1.3.1.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsIfIndexOrZero,Integer32,not-accessible,,current,,Uniquely identifies an interface that a fast-reroute protection tunnel is configured to potentially protect in the event of a fault. Entries with this index set to 0 indicate that the configured protection tunnel protects all interfaces on this device (i.e., node protection).
.1.3.6.1.2.1.202.1.3.1.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsTunnelIndex,Unsigned32,not-accessible,,current,,Uniquely identifies a tunnel in the mplsTunnelTable that is configured to possibly protect the interface(s) specified by mplsFrrGeneralConstraintsIfIndexOrZero in the event of a fault.
.1.3.6.1.2.1.202.1.3.1.3,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsTunnelInstance,Unsigned32,not-accessible,,current,,Uniquely identifies an existing instance of this tunnel for which fast reroute is requested. Note that a value of 0 indicates that the configuration points at a tunnel head (as specified in RFC 3812). This is typically how configuration of this feature is performed on devices where the actual protection LSP used is left up to the protecting tunnel. However, in cases where static configuration is possible, any valid tunnel instance is permissible. In these cases, it is recommended that the instance index follow the following convention so as to make identification of backup LSPs easier: - lower 16 bits : protected tunnel instance - higher 16 bits: must be all zeros
.1.3.6.1.2.1.202.1.3.1.4,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsProtectionType,INTEGER,read-create,,current,linkProtection(1):nodeProtection(2),Indicates type of the resource protection: linkProtection(1) indicates that this tunnel is set up to protect a particular link's resources. nodeProtection(2) indicates that this tunnel is set up to protect an entire node from failure.
.1.3.6.1.2.1.202.1.3.1.5,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsSetupPrio,Unsigned32,read-create,,current,,Indicates the setup priority of the detour LSP or bypass tunnel.
.1.3.6.1.2.1.202.1.3.1.6,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsHoldingPrio,Unsigned32,read-create,,current,,Indicates the holding priority for the detour LSP or bypass tunnel.
.1.3.6.1.2.1.202.1.3.1.7,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsInclAnyAffinity,Unsigned32,read-create,,current,,Indicates the include-any link constraint for the detour LSP or bypass tunnel. A link satisfies the include-any constraint if and only if the constraint is zero, or the link and the constraint have a resource class in common.
.1.3.6.1.2.1.202.1.3.1.8,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsInclAllAffinity,Unsigned32,read-create,,current,,Indicates the include-all link constraint for the detour LSP or bypass tunnel. A link satisfies the include-all constraint if and only if the link contains all of the administrative groups specified in the constraint.
.1.3.6.1.2.1.202.1.3.1.9,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsExclAnyAffinity,Unsigned32,read-create,,current,,Indicates the exclude-any link constraint for the detour LSP or bypass tunnel. A link satisfies the exclude-any constraint if and only if the link contains none of the administrative groups specified in the constraint.
.1.3.6.1.2.1.202.1.3.1.10,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsHopLimit,Unsigned32,read-create,,current,,The maximum number of hops that the detour LSP or bypass tunnel may traverse.
.1.3.6.1.2.1.202.1.3.1.11,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsBandwidth,Unsigned32,read-create,,current,,The maximum bandwidth specifically reserved for a detour LSP or bypass tunnel, in units of thousands of bits per second (kbps). Note that setting this value to 0 indicates best-effort treatment.
.1.3.6.1.2.1.202.1.3.1.12,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this configuration entry. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.
.1.3.6.1.2.1.202.1.3.1.13,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified except mplsFrrGeneralConstraintsRowStatus and mplsFrrGeneralConstraintsStorageType.
.1.3.6.1.2.1.202.1.4,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralTunnelARHopTable,,not-accessible,,current,,This table sparsely extends mplsTunnelARHopTable defined in the MPLS-TE-STD-MIB module with fast-reroute objects. These objects specify the status of local protection, including availability and active use, on a per-hop basis, of hops traversed by a protected tunnel.
.1.3.6.1.2.1.202.1.4.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralTunnelARHopEntry,,not-accessible,mplsTunnelARHopListIndex:mplsTunnelARHopIndex,current,,This entry contains fast-reroute protection status of a single protected tunnel hop.
.1.3.6.1.2.1.202.1.4.1.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralTunnelARHopSessionAttributeFlags,BITS,read-only,,current,arHopSessionAttrFlagsUnsupported(0):localProtectionDesired(1):labelRecordingDesired(2):sestyleDesired(3):bandwidthProtectionDesired(4):nodeProtectionDesired(5),This object indicates the desired values for the associated SESSION_ATTRIBUTE flags. Note that since this object is a BITS type, the bits may be set to indicate various desired combinations of the SESSION_ATTRIBUTE flags. If SESSION_ATTRIBUTE flags are not supported, then this object contains the value of arHopSessionAttrFlagsUnsupported(0).
.1.3.6.1.2.1.202.1.4.1.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralTunnelARHopRROSubObjectFlags,BITS,read-only,,current,arHopRROSubObjectFlagsUnsupported(0):localProtectionAvailable(1):localProtectionInUse(2):bandwidthProtection(3):nodeProtection(4),This object indicates the flags that are currently in use by the associated Record Route Object (RRO) sub-object. Note that since this object is a BITS type, the bits may be set to indicate various combinations of the flags. If the RRO sub-object is not supported, then this object contains the value of arHopRROSubObjectFlagsUnsupported(0).
.1.3.6.1.2.1.202.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConformance,,,,,,
.1.3.6.1.2.1.202.2.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralCompliances,,,,,,
.1.3.6.1.2.1.202.2.1.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralModuleFullCompliance,,,,,,Compliance statements for SNMP engines that support the MPLS-FRR-GENERAL-STD-MIB module.
.1.3.6.1.2.1.202.2.1.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralModuleReadOnlyCompliance,,,,,,Compliance statements for SNMP engines that support the MPLS-FRR-GENERAL-STD-MIB module.
.1.3.6.1.2.1.202.2.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralGroups,,,,,,
.1.3.6.1.2.1.202.2.2.1,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralScalarGroup,,,,,,Objects that are required to display general fast-reroute information.
.1.3.6.1.2.1.202.2.2.2,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralConstraintsGroup,,,,,,Objects that are required to configure fast-reroute constraints at the ingress LSR of the tunnel that requires fast-reroute service.
.1.3.6.1.2.1.202.2.2.3,MPLS-FRR-GENERAL-STD-MIB::mplsFrrGeneralTunnelARHopGroup,,,,,,Objects that are required to present per-hop fast-reroute protection status.
.1.3.6.1.2.1.203,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneMIB,,,,,,Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB module contains object definitions for the MPLS Traffic Engineering one-to-one backup method for Fast Reroute as defined in RFC 4090.
.1.3.6.1.2.1.203.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneObjects,,,,,,
.1.3.6.1.2.1.203.1.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrIncomingDetourLSPs,Integer32,read-only,,current,,The number of detour LSPs entering the device.
.1.3.6.1.2.1.203.1.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOutgoingDetourLSPs,Integer32,read-only,,current,,The number of detour LSPs leaving the device.
.1.3.6.1.2.1.203.1.3,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneDetourOriginating,Integer32,read-only,,current,,The number of detour LSPs originating at this PLR.
.1.3.6.1.2.1.203.1.4,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrActiveProtectedLSPs,Gauge32,read-only,,current,,Indicates the number of LSPs currently protected by the FRR feature where this device acts as the PLR for those LSPs.
.1.3.6.1.2.1.203.1.5,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrTable,,not-accessible,,current,,This table shows a list of protected TE tunnels with the corresponding protecting tunnel, as well as the PLR where the protecting tunnel that initiated the detour LSPs traverses this node.
.1.3.6.1.2.1.203.1.5.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrEntry,,not-accessible,mplsFrrOne2OnePlrTunnelIndex:mplsFrrOne2OnePlrTunnelDetourInstance:mplsFrrOne2OnePlrTunnelIngressLSRId:mplsFrrOne2OnePlrTunnelEgressLSRId:mplsFrrOne2OnePlrId,current,,An entry in this table represents a protected tunnel LSP together with its detour tunnel instance. An entry in this table is only created by an SNMP engine as instructed by an MPLS signaling protocol. The entries of this table are present in all LSRs on the path of the detour LSP. The objects mplsFrrOne2OnePlrSenderAddrType and mplsFrrOne2OnePlrSenderAddr can be modified after the row is created. The objects mplsFrrOne2OnePlrTunnelIndex, mplsFrrOne2OnePlrTunnelDetourInstance, mplsFrrOne2OnePlrTunnelIngressLSRId, and mplsFrrOne2OnePlrTunnelEgressLSRId have the same values as the objects mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, and mplsTunnelEgressLSRId of the detour tunnel instance created in the mplsTunnelTable (MPLS-TE-STD-MIB). The entries in this table will be deleted when the corresponding entries in the mplsTunnelTable are deleted.
.1.3.6.1.2.1.203.1.5.1.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrTunnelIndex,Unsigned32,not-accessible,,current,,Uniquely identifies a tunnel between a pair of LSRs from the mplsTunnelEntry.
.1.3.6.1.2.1.203.1.5.1.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrTunnelDetourInstance,Unsigned32,not-accessible,,current,,Uniquely identifies a detour instance of a tunnel from the mplsTunnelEntry. - lower 16 bits : protected tunnel instance - higher 16 bits: detour instance
.1.3.6.1.2.1.203.1.5.1.3,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrTunnelIngressLSRId,OCTET,not-accessible,,current,,The purpose of this object is to uniquely identify a tunnel within a network. When the MPLS signaling protocol is rsvp(2), this object SHOULD contain the same value as the Extended Tunnel ID field in the SESSION object. When the MPLS signaling protocol is crldp(3), this object SHOULD contain the same value as the Ingress LSR Router ID field in the LSPID TLV object. This value represents the head-end of the protected tunnel instance.
.1.3.6.1.2.1.203.1.5.1.4,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrTunnelEgressLSRId,OCTET,not-accessible,,current,,Specifies the egress LSR ID of the protected tunnel instance.
.1.3.6.1.2.1.203.1.5.1.5,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrId,OCTET,not-accessible,,current,,This value represents the PLR that has initiated a detour LSP to protect a tunnel instance. This value is signaled via the DETOUR object defined in MPLS RSVP.
.1.3.6.1.2.1.203.1.5.1.6,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrSenderAddrType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Denotes the address type of this detour instance's sender address.
.1.3.6.1.2.1.203.1.5.1.7,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrSenderAddr,OCTET,read-write,,current,,The IP address of the PLR that has initiated the detour LSP. The type of this address is determined by the value of the mplsFrrOne2OnePlrSenderAddrType object.
.1.3.6.1.2.1.203.1.5.1.8,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrAvoidNodeAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Denotes the address type of the node that this PLR tries to avoid.
.1.3.6.1.2.1.203.1.5.1.9,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrAvoidNodeAddr,OCTET,read-only,,current,,The IP address of the node that this PLR tries to avoid. The type of this address is determined by the value of the mplsFrrOne2OnePlrAvoidNodeAddrType object. This value is signaled via the DETOUR object defined in MPLS RSVP.
.1.3.6.1.2.1.203.1.6,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneDetourTable,,not-accessible,,current,,This table shows detour LSPs.
.1.3.6.1.2.1.203.1.6.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneDetourEntry,,not-accessible,mplsFrrOne2OnePlrTunnelIndex:mplsFrrOne2OnePlrTunnelDetourInstance:mplsFrrOne2OnePlrTunnelIngressLSRId:mplsFrrOne2OnePlrTunnelEgressLSRId,current,,An entry in this table represents a detour. An entry in this table is only created by an SNMP engine as instructed by an MPLS signaling protocol.
.1.3.6.1.2.1.203.1.6.1.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneDetourActive,INTEGER,read-only,,current,true(1):false(2),Indicates whether or not the main LSP has switched over to this detour LSP. If the value of this object is 'true', then it means that the main LSP has switched over to this detour LSP. Otherwise, it contains a value of 'false'. This is only relevant for detours originated by this node.
.1.3.6.1.2.1.203.1.6.1.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneDetourMergedStatus,INTEGER,read-only,,current,notMerged(1):mergedWithProtectedTunnel(2):mergedWithDetour(3),This value represents whether or not this detour is merged. This value is set to notMerged(1) if this detour is not merged. This value is set to mergedWithProtectedTunnel(2) if this detour is merged with the protected tunnel. This value is mergedWithDetour(3) if this detour is merged with another detour protecting the same tunnel.
.1.3.6.1.2.1.203.1.6.1.3,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneDetourMergedDetourInst,Unsigned32,read-only,,current,,This value represents the mplsTunnelInstance of the detour with which this detour is merged. This object is only valid when mplsFrrOne2OneDetourMergedStatus is set to mergedWithDetour(3). - lower 16 bits : protected tunnel instance - higher 16 bits: detour instance
.1.3.6.1.2.1.203.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneConformance,,,,,,
.1.3.6.1.2.1.203.2.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneCompliances,,,,,,
.1.3.6.1.2.1.203.2.1.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneModuleFullCompliance,,,,,,Compliance statements for SNMP engines that support the MPLS-FRR-ONE2ONE-STD-MIB module.
.1.3.6.1.2.1.203.2.1.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneModuleReadOnlyCompliance,,,,,,Compliance statements for SNMP engines that support the MPLS-FRR-ONE2ONE-STD-MIB module.
.1.3.6.1.2.1.203.2.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneGroups,,,,,,
.1.3.6.1.2.1.203.2.2.1,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OneScalarsGroup,,,,,,Objects that are required for general One-to-One PLR information.
.1.3.6.1.2.1.203.2.2.2,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePLRDetourGroup,,,,,,Objects that are required to present the detour LSP information at the detour ingress, transit, and egress LSRs.
.1.3.6.1.2.1.203.2.2.3,MPLS-FRR-ONE2ONE-STD-MIB::mplsFrrOne2OnePlrGroup,,,,,,Objects that are required to represent the FRR One-to-One PLR information.
.1.3.6.1.2.1.204,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityMIB,,,,,,Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB module contains object definitions for the MPLS Traffic Engineering facility backup method for Fast Reroute as defined in RFC 4090.
.1.3.6.1.2.1.204.0,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityNotifications,,,,,,
.1.3.6.1.2.1.204.0.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityInitialBackupTunnelInvoked,,,,,,This notification is generated when a tunnel running over an interface as specified in the mplsFrrConstraintsTable is initially protected by the backup tunnel also specified in the mplsFrrConstraintsTable. In some implementations, there may be a difference between when the control plane triggers this notification and when the hardware is programmed to utilize the protection path. Due to the urgency of this operation, it is acceptable for the control plane to issue this notification either before or after it programs the hardware. In cases where it is the latter approach, the notification MUST be sent immediately after the data plane has been altered. This notification should not be generated for each subsequent tunnel that is backed up by the FRR feature on this LSR, as this may result in potential scaling issues with regard to LSR performance and network load. Note also that notifications MUST be generated in accordance with the mplsFrrNotificationsMaxRate.
.1.3.6.1.2.1.204.0.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityFinalTunnelRestored,,,,,,This notification is generated when the final tunnel that is being protected by a backup tunnel as specified in the mplsFrrConstraintsTable is restored to normal operation. This notification should not be generated for each restored tunnel, as this may result in potential scaling issues with regard to LSR performance and network load. Note also that notifications MUST be generated in accordance with the mplsFrrNotificationsMaxRate.
.1.3.6.1.2.1.204.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityObjects,,,,,,
.1.3.6.1.2.1.204.1.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrConfiguredInterfaces,Integer32,read-only,,current,,Indicates the number of MPLS interfaces configured for protection.
.1.3.6.1.2.1.204.1.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrActiveInterfaces,Gauge32,read-only,,current,,Indicates the number of interfaces currently being protected. This value MUST be less than or equal to mplsFrrConfiguredInterfaces.
.1.3.6.1.2.1.204.1.3,MPLS-FRR-FACILITY-STD-MIB::mplsFrrConfiguredBypassTunnels,Gauge32,read-only,,current,,Indicates the number of bypass tunnels configured to protect TE tunnels on this LSR.
.1.3.6.1.2.1.204.1.4,MPLS-FRR-FACILITY-STD-MIB::mplsFrrActiveBypassTunnels,Gauge32,read-only,,current,,Indicates the number of bypass tunnels indicated in mplsFrrConfiguredBypassTunnels whose operStatus is up(1), indicating that they are currently protecting TE tunnels on this LSR.
.1.3.6.1.2.1.204.1.5,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),Enables or disables FRR notifications defined in this MIB module. Notifications are disabled by default. This object is needed to control the notifications emitted by this implementation.
.1.3.6.1.2.1.204.1.6,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityNotificationsMaxRate,Gauge32,read-write,,current,,This variable indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period, or may queue them until an appropriate time. In case the implementation chooses to drop the events during throttling instead of queuing them to be sent at a later time, it is assumed that there will be no indication that events are being thrown away. A value of 0 means no throttling is applied and events may be generated at the rate at which they occur.
.1.3.6.1.2.1.204.1.7,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBTable,,not-accessible,,current,,The mplsFrrFacilityDBTable provides information about the fast-reroute database. Each entry belongs to a protected interface, protecting backup tunnel, and protected tunnel. MPLS interfaces defined on this node are protected by backup tunnels and are indicated by the index mplsFrrFacilityProtectedIfIndex. If the interface index is set to 0, this indicates that the remaining indexes apply to all configured protected interfaces. Note that all objects in this table are read-only, and if new objects are added to this table, they should also be read-only. It is recommended that ifIndex persistence be enabled across re-initializations. If persistence is not implemented, then the value of mplsFrrFacilityProtectedIfIndex in this table cannot be guaranteed across restarts and all entries in this table MUST NOT be persistent, or the values of mplsFrrFacilityProtectedIfIndex MUST be reconstructed on restart. It is recommended that entries in this table be persistent across reboots. The protecting tunnel is indicated by the index mplsFrrFacilityProtectingTunnelIndex and represents a valid mplsTunnelEntry. Note that the tunnel instance index of the protecting tunnel may be set to 0, which indicates the tunnel head interface for the protecting tunnel, as per RFC 3812, but it may also be defined using the following semantics: - lower 16 bits : protected tunnel instance - higher 16 bits: must be all zeros
.1.3.6.1.2.1.204.1.7.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBEntry,,not-accessible,mplsFrrFacilityProtectedIfIndex:mplsFrrFacilityProtectingTunnelIndex:mplsFrrFacilityBackupTunnelIndex:mplsFrrFacilityBackupTunnelInstance:mplsFrrFacilityBackupTunnelIngressLSRId:mplsFrrFacilityBackupTunnelEgressLSRId,current,,An entry in the mplsFrrFacilityDBTable represents a single protected LSP, protected by a backup tunnel on a specific protected interface, or if the interface index is set to 0, on all interfaces. Note that for brevity, managers should consult the mplsTunnelTable present in the MPLS-TE-STD-MIB module for additional information about the protecting and protected tunnels, and the ifEntry in the IF-MIB module for the protected interface.
.1.3.6.1.2.1.204.1.7.1.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityProtectedIfIndex,Integer32,not-accessible,,current,,Uniquely identifies the interface configured for FRR protection. If this object is set to 0, this indicates that the remaining indexing combinations for this row apply to all interfaces on this device for which the FRR feature can operate.
.1.3.6.1.2.1.204.1.7.1.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityProtectingTunnelIndex,Unsigned32,not-accessible,,current,,Uniquely identifies the mplsTunnelEntry primary index for the tunnel head interface designated to protect the interface as specified in the mplsFrrFacilityProtectedIfIndex (and all of the tunnels using this interface). Note that the corresponding mplsTunnelInstance MUST BE 0 as per the indexing convention stipulated.
.1.3.6.1.2.1.204.1.7.1.3,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityBackupTunnelIndex,Unsigned32,not-accessible,,current,,Uniquely identifies the mplsTunnelEntry primary index for the TE tunnel LSP being protected on the interface as specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.4,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityBackupTunnelInstance,Unsigned32,not-accessible,,current,,Uniquely identifies the mplsTunnelEntry secondary index for the TE tunnel LSP being protected on the interface as specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.5,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityBackupTunnelIngressLSRId,OCTET,not-accessible,,current,,Uniquely identifies the mplsTunnelEntry third index for the TE tunnel LSP being protected on the interface as specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.6,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityBackupTunnelEgressLSRId,OCTET,not-accessible,,current,,Uniquely identifies the mplsTunnelEntry fourth index for the TE tunnel LSP being protected on the interface as specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.7,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBNumProtectingTunnelOnIf,Gauge32,read-only,,current,,The number of backup tunnels protecting the interface specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.8,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBNumProtectedLspOnIf,Gauge32,read-only,,current,,The number of LSPs currently being protected on the interface specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.9,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBNumProtectedTunnels,Gauge32,read-only,,current,,The number of tunnels protected on the interface specified by mplsFrrFacilityProtectedIfIndex.
.1.3.6.1.2.1.204.1.7.1.10,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBProtectingTunnelStatus,INTEGER,read-only,,current,active(1):ready(2):partial(3),Specifies the state of the protecting tunnel as specified by mplsFrrFacilityProtectingTunnelIndex. active - This tunnel's label has been placed in the LFIB and is ready to be applied to incoming packets. ready - This tunnel's label entry has been created but is not yet in the LFIB. partial - This tunnel's label entry has not been fully created.
.1.3.6.1.2.1.204.1.7.1.11,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBProtectingTunnelResvBw,Unsigned32,read-only,,current,,Specifies the amount of bandwidth in units of '1,000 bits per second', actually reserved by the protecting tunnel for facility backup purposes. This value is repeated here from the MPLS-TE-STD-MIB module because the tunnel entry will reveal the bandwidth reserved by the signaling protocol, which is typically 0 for backup tunnels so as to not over-book bandwidth. However, internal reservations are typically made on the PLR; thus, this value should be revealed here, as it is often different from mplsTunnelResourceMeanRate found in the MPLS-TE-STD-MIB module.
.1.3.6.1.2.1.204.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityConformance,,,,,,
.1.3.6.1.2.1.204.2.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityCompliances,,,,,,
.1.3.6.1.2.1.204.2.1.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityModuleFullCompliance,,,,,,Compliance statements for SNMP engines that support the MPLS-FRR-FACILITY-STD-MIB module.
.1.3.6.1.2.1.204.2.1.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityModuleReadOnlyCompliance,,,,,,Compliance statements for SNMP engines that support the MPLS-FRR-FACILITY-STD-MIB module.
.1.3.6.1.2.1.204.2.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityGroups,,,,,,
.1.3.6.1.2.1.204.2.2.1,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityScalarGroup,,,,,,Objects that are required to represent the FRR Facility Route Database information.
.1.3.6.1.2.1.204.2.2.2,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityDBGroup,,,,,,Objects that are required to represent the FRR Facility Route Database information.
.1.3.6.1.2.1.204.2.2.3,MPLS-FRR-FACILITY-STD-MIB::mplsFrrFacilityNotificationsGroup,,,,,,Objects that are required to represent FRR notifications.
.1.3.6.1.2.1.205,PMIPV6-TC-MIB::pmip6TCMIB,,,,,,This MIB module provides textual conventions for Proxy Mobile IPv6 Management information. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). 
.1.3.6.1.2.1.206,PMIPV6-MIB::pmip6MIB,,,,,,The MIB module for monitoring and controlling PMIPv6 entities. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). 
.1.3.6.1.2.1.206.0,PMIPV6-MIB::pmip6Notifications,,,,,,
.1.3.6.1.2.1.206.0.1,PMIPV6-MIB::pmip6MagHomeTunnelEstablished,,,,,,This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel is established between the local mobility anchor and mobile access gateway. 
.1.3.6.1.2.1.206.0.2,PMIPV6-MIB::pmip6MagHomeTunnelReleased,,,,,,This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released. 
.1.3.6.1.2.1.206.0.3,PMIPV6-MIB::pmip6LmaHomeTunnelEstablished,,,,,,This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel is established between the local mobility anchor and mobile access gateway. 
.1.3.6.1.2.1.206.0.4,PMIPV6-MIB::pmip6LmaHomeTunnelReleased,,,,,,This notification is sent by the Proxy Mobile IPv6 entities every time the tunnel between the local mobility anchor and mobile access gateway is released. 
.1.3.6.1.2.1.206.1,PMIPV6-MIB::pmip6Objects,,,,,,
.1.3.6.1.2.1.206.1.1,PMIPV6-MIB::pmip6Core,,,,,,
.1.3.6.1.2.1.206.1.1.1,PMIPV6-MIB::pmip6System,,,,,,
.1.3.6.1.2.1.206.1.1.1.1,PMIPV6-MIB::pmip6Capabilities,BITS,read-only,,current,mobilityAccessGateway(0):localMobilityAnchor(1),This object indicates the PMIPv6 functions that are supported by this managed entity. Multiple Proxy Mobile IPv6 functions may be supported by a single entity. mobilityAccessGateway(0) indicates the availability of the mobility access gateway function. localMobilityAnchor(1) indicates the availability of the local mobility anchor function. 
.1.3.6.1.2.1.206.1.1.2,PMIPV6-MIB::pmip6Bindings,,,,,,
.1.3.6.1.2.1.206.1.1.2.1,PMIPV6-MIB::pmip6BindingCacheTable,,not-accessible,,current,,This table models the Binding Cache on the local mobility anchor. Entries from the table are deleted as the lifetime of the binding expires. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.1.2.1.1,PMIPV6-MIB::pmip6BindingCacheEntry,,not-accessible,,current,,An entry containing additional information contained in the Binding Cache table of the local mobility anchor. 
.1.3.6.1.2.1.206.1.1.2.1.1.1,PMIPV6-MIB::pmip6BindingPBUFlag,INTEGER,read-only,,current,true(1):false(2),true(1) indicates that the local mobility anchor accepted the binding update with Proxy Registration Flag from a mobile access gateway. false(0) implies that the binding cache is from a mobile node. In this case, the remaining objects will not be accessible. 
.1.3.6.1.2.1.206.1.1.2.1.1.2,PMIPV6-MIB::pmip6BindingMnIndex,Unsigned32,read-only,,current,,An index to the identifier of the registered mobile node. 
.1.3.6.1.2.1.206.1.1.2.1.1.3,PMIPV6-MIB::pmip6BindingMnLLIndex,Unsigned32,read-only,,current,,The index to the link-layer identifier of the mobile node's connected interface on the access link. 
.1.3.6.1.2.1.206.1.1.2.1.1.4,PMIPV6-MIB::pmip6BindingMagLinkLocalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6BindingMagLinkLocalAddress that follows. 
.1.3.6.1.2.1.206.1.1.2.1.1.5,PMIPV6-MIB::pmip6BindingMagLinkLocalAddress,OCTET,read-only,,current,,The link-local address of the mobile access gateway on the point-to-point link shared with the mobile node. This is generated by the local mobility anchor after accepting the initial Proxy Binding Update message. This is the address that is present in the Link-local Address option of the corresponding Proxy Binding Acknowledgement message. 
.1.3.6.1.2.1.206.1.1.2.1.1.6,PMIPV6-MIB::pmip6BindingTunnelIfIdentifier,OCTET,read-only,,current,,The tunnel interface identifier (tunnel-if-id) of the bidirectional tunnel between the local mobility anchor and the mobile access gateway where the mobile node is currently anchored. This is internal to the local mobility anchor. The tunnel interface identifier is acquired during the tunnel creation. 
.1.3.6.1.2.1.206.1.1.2.1.1.7,PMIPV6-MIB::pmip6BindingMnInterfaceATT,INTEGER,read-only,,current,reserved(0):logicalNetworkInterface(1):pointToPointInterface(2):ethernet(3):wirelessLan(4):wimax(5):threeGPPGERAN(6):threeGPPUTRAN(7):threeGPPEUTRAN(8):threeGPP2eHRPD(9):threeGPP2HRPD(10):threeGPP21xRTT(11):threeGPP2UMB(12),The access technology type by which the mobile node is currently attached. This is obtained from the Access Technology Type option, present in the Proxy Binding Update message. 
.1.3.6.1.2.1.206.1.1.2.1.1.8,PMIPV6-MIB::pmip6BindingTimeRecentlyAccepted,OCTET,read-only,,current,,The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is the time of day on the local mobility anchor, when the message was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when the sequence number based scheme is in use), the value MUST be initialized with all zeroes. 
.1.3.6.1.2.1.206.1.1.3,PMIPV6-MIB::pmip6Conf,,,,,,
.1.3.6.1.2.1.206.1.1.3.1,PMIPV6-MIB::pmip6MobileNodeGeneratedTimestampInUse,INTEGER,read-write,,current,true(1):false(2),This flag indicates whether or not the MN-generated timestamp mechanism is in use in that Proxy Mobile IPv6 domain. true(1) indicates that the local mobility anchors and mobile access gateways in that Proxy Mobile IPv6 domain apply the MN-generated timestamp considerations. false(0) indicates that the MN-generated timestamp mechanism is not in use in that Proxy Mobile IPv6 domain. The default value for this flag is 'false'. 
.1.3.6.1.2.1.206.1.1.3.2,PMIPV6-MIB::pmip6FixedMagLinkLocalAddressOnAllAccessLinksType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6FixedMagLinkLocalAddressOnAllAccessLinks that follows. 
.1.3.6.1.2.1.206.1.1.3.3,PMIPV6-MIB::pmip6FixedMagLinkLocalAddressOnAllAccessLinks,OCTET,read-write,,current,,This variable indicates the link-local address value that all the mobile access gateways should use on any of the access links shared with any of the mobile nodes in that Proxy Mobile IPv6 domain. If this variable is initialized with all zeroes, it implies that the use of fixed link-local address mode is not enabled for that Proxy Mobile IPv6 domain.
.1.3.6.1.2.1.206.1.1.3.4,PMIPV6-MIB::pmip6FixedMagLinkLayerAddressOnAllAccessLinks,OCTET,read-write,,current,,This variable indicates the link-layer address value that all the mobile access gateways should use on any of the access links shared with any of the mobile nodes in that Proxy Mobile IPv6 domain. For access technologies where there is no link-layer address, this variable MUST be initialized with all zeroes. 
.1.3.6.1.2.1.206.1.1.4,PMIPV6-MIB::pmip6Stats,,,,,,
.1.3.6.1.2.1.206.1.1.4.1,PMIPV6-MIB::pmip6BindingRegCounters,,,,,,
.1.3.6.1.2.1.206.1.1.4.1.1,PMIPV6-MIB::pmip6MissingMnIdentifierOption,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing mobile node identifier option' (Code 160). Discontinuities in the value of this counter can occur at re-initialization of the mobile router, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.2,PMIPV6-MIB::pmip6MagNotAuthorizedForProxyReg,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Not authorized to send Proxy Binding Updates' (Code 154). Discontinuities in the value of this counter can occur at re-initialization of the mobile router, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.3,PMIPV6-MIB::pmip6NotLMAForThisMobileNode,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Not local mobility anchor for this mobile node' (Code 153). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.4,PMIPV6-MIB::pmip6ProxyRegNotEnabled,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Proxy Registration not enabled' (Code 152). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.5,PMIPV6-MIB::pmip6MissingHomeNetworkPrefixOption,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing home network prefix option' (Code 158). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.6,PMIPV6-MIB::pmip6MissingHandOffIndicatorOption,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing handoff indicator option' (Code 161). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.7,PMIPV6-MIB::pmip6MissingAccessTechTypeOption,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Missing access technology type option' (Code 162). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.8,PMIPV6-MIB::pmip6NotAuthorizedForHomeNetworkPrefix,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Mobile node not authorized for one or more of the requesting home network prefixes' (Code 155). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.9,PMIPV6-MIB::pmip6TimestampMismatch,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'Invalid timestamp value (the clocks are out of sync)' (Code 156). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.10,PMIPV6-MIB::pmip6TimestampLowerThanPrevAccepted,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'The timestamp value is lower than the previously accepted value' (Code 157). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.11,PMIPV6-MIB::pmip6BcePbuPrefixSetDoNotMatch,Counter32,read-only,,current,,Total number of Proxy Binding Update messages rejected by the local mobility anchor with status code in the Binding Acknowledgement message indicating 'All the home network prefixes listed in the Binding Cache entry do not match all the prefixes in the received Proxy Binding Update' (Code 159). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.12,PMIPV6-MIB::pmip6InitialBindingRegistrations,Counter32,read-only,,current,,Total number of Proxy Binding Update messages that newly creates the Binding Cache entry. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.13,PMIPV6-MIB::pmip6BindingLifeTimeExtensionNoHandOff,Counter32,read-only,,current,,Total number of Proxy Binding Update messages for extending the binding lifetime, received from the same mobile access gateway that last updated the binding. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.14,PMIPV6-MIB::pmip6BindingLifeTimeExtensionAfterHandOff,Counter32,read-only,,current,,Total number of Proxy Binding Update messages for extending the binding lifetime, received from a new mobile access gateway where the mobile node's mobility session is handed off. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.15,PMIPV6-MIB::pmip6BindingDeRegistrations,Counter32,read-only,,current,,Total number of Proxy Binding Update messages with the lifetime value of zero. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.16,PMIPV6-MIB::pmip6BindingBindingAcks,Counter32,read-only,,current,,Total number of Proxy Binding Acknowledgement messages. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of pmip6CounterDiscontinuityTime. 
.1.3.6.1.2.1.206.1.1.4.1.17,PMIPV6-MIB::pmip6CounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this PMIPv6 entity's global counters, viz., counters with OID prefix 'pmip6BindingRegCounters' suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object will have a zero value. 
.1.3.6.1.2.1.206.1.2,PMIPV6-MIB::pmip6Mag,,,,,,
.1.3.6.1.2.1.206.1.2.1,PMIPV6-MIB::pmip6MagSystem,,,,,,
.1.3.6.1.2.1.206.1.2.1.1,PMIPV6-MIB::pmip6MagStatus,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether the PMIPv6 mobile access gateway function is enabled for the managed entity. Changing the status from enabled(1) to disabled(2) will terminate the PMIPv6 mobile access gateway function. On the other hand, changing the status from disabled(2) to enabled(1) will start the PMIPv6 mobile access gateway function. The value of this object MUST remain unchanged across reboots of the managed entity. 
.1.3.6.1.2.1.206.1.2.1.2,PMIPV6-MIB::pmip6MagProxyCOATable,,not-accessible,,current,,This table models the Proxy Care-of Addresses configured on the egress interfaces of the mobile access gateway. This address is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.2.1.2.1,PMIPV6-MIB::pmip6MagProxyCOAEntry,,not-accessible,pmip6MagProxyCOAType:pmip6MagProxyCOA,current,,This entry represents a conceptual row in the Proxy-CoA table. It represents a Proxy Care-of Address on the mobile access gateway. Implementers need to be aware that if the total number of octets in pmip6MagProxyCOA exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.206.1.2.1.2.1.1,PMIPV6-MIB::pmip6MagProxyCOAType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6MagProxyCOA that follows. 
.1.3.6.1.2.1.206.1.2.1.2.1.2,PMIPV6-MIB::pmip6MagProxyCOA,OCTET,not-accessible,,current,,The Proxy-CoA configured on the egress interface of the mobile access gateway. The type of the address represented by this object is specified by the corresponding pmip6MagProxyCOAType object. 
.1.3.6.1.2.1.206.1.2.1.2.1.3,PMIPV6-MIB::pmip6MagProxyCOAState,INTEGER,read-only,,current,unknown(1):activated(2):tunneled(3),This object indicates the state of the Proxy-CoA: unknown -- The state of the Proxy-CoA cannot be determined. activated -- The Proxy-CoA is ready to establish a tunnel. This state SHOULD be indicated when the MAG is up but has no mobile node. tunneled -- Bidirectional tunnel is established using the Proxy-CoA. 
.1.3.6.1.2.1.206.1.2.2,PMIPV6-MIB::pmip6MagConf,,,,,,
.1.3.6.1.2.1.206.1.2.2.1,PMIPV6-MIB::pmip6MagEnableMagLocalRouting,INTEGER,read-write,,current,true(1):false(2),This flag indicates whether or not the mobile access gateway is allowed to enable local routing of the traffic exchanged between a visiting mobile node and a correspondent node that is locally connected to one of the interfaces of the mobile access gateway. The correspondent node can be another visiting mobile node as well, or a local fixed node. true(1) indicates that the mobile access gateway routes the traffic locally. false(0) indicates that the mobile access gateway reverse tunnels all the traffic to the mobile node's local mobility anchor. The default value for this flag is 'false'. 
.1.3.6.1.2.1.206.1.2.2.2,PMIPV6-MIB::pmip6MagMnIdentifierTable,,not-accessible,,current,,A table containing the identifiers of mobile nodes attached to the MAG. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.2.2.2.1,PMIPV6-MIB::pmip6MagMnIdentifierEntry,,not-accessible,pmip6MagBLMnIndex,current,,An entry in the mobile node identifier table. 
.1.3.6.1.2.1.206.1.2.2.2.1.1,PMIPV6-MIB::pmip6MagMnIdentifier,OCTET,read-only,,current,,The identity of a mobile node in the Proxy Mobile IPv6 domain. 
.1.3.6.1.2.1.206.1.2.2.3,PMIPV6-MIB::pmip6MagMnLLIdentifierTable,,not-accessible,,current,,A table containing the link-layer identifiers of the interfaces of the mobile nodes attached to the MAG. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.2.2.3.1,PMIPV6-MIB::pmip6MagMnLLIdentifierEntry,,not-accessible,pmip6MagBLMnIndex:pmip6MagBLMnLLIndex,current,,An entry in the mobile node link-layer identifier table. 
.1.3.6.1.2.1.206.1.2.2.3.1.1,PMIPV6-MIB::pmip6MagMnLLIdentifier,OCTET,read-only,,current,,The link-layer identifier of the mobile node's connected interface on the access link. 
.1.3.6.1.2.1.206.1.2.2.4,PMIPV6-MIB::pmip6MagHomeNetworkPrefixTable,,not-accessible,,current,,A table representing the home network prefixes assigned to the connected interfaces of mobile nodes attached to the MAG. 
.1.3.6.1.2.1.206.1.2.2.4.1,PMIPV6-MIB::pmip6MagHomeNetworkPrefixEntry,,not-accessible,pmip6MagBLMnIndex:pmip6MagBLMnLLIndex:pmip6MagHomeNetworkPrefixType:pmip6MagHomeNetworkPrefix,current,,An entry in the home network prefixes table. Implementers need to be aware that if the total number of octets in pmip6MagHomeNetworkPrefix exceeds 111, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.206.1.2.2.4.1.1,PMIPV6-MIB::pmip6MagHomeNetworkPrefixType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6MagHomeNetworkPrefix that follows. 
.1.3.6.1.2.1.206.1.2.2.4.1.2,PMIPV6-MIB::pmip6MagHomeNetworkPrefix,OCTET,not-accessible,,current,,The mobile network prefix that is delegated to the mobile node. The type of the address represented by this object is specified by the corresponding pmip6MagHomeNetworkPrefixType object. 
.1.3.6.1.2.1.206.1.2.2.4.1.3,PMIPV6-MIB::pmip6MagHomeNetworkPrefixLength,Unsigned32,read-only,,current,,The prefix length of the home network prefix. 
.1.3.6.1.2.1.206.1.2.2.4.1.4,PMIPV6-MIB::pmip6MagHomeNetworkPrefixLifeTime,Unsigned32,read-only,,current,,The lifetime parameter (in seconds) that will be advertised in Router Advertisements by the MAG for this home network prefix. 
.1.3.6.1.2.1.206.1.2.3,PMIPV6-MIB::pmip6MagRegistration,,,,,,
.1.3.6.1.2.1.206.1.2.3.1,PMIPV6-MIB::pmip6MagBLTable,,not-accessible,,current,,This table corresponds to the Binding Update List (BL) that includes PMIPv6-related information and is maintained by the mobile access gateway. Entries from the table are deleted as the lifetime of the binding expires. 
.1.3.6.1.2.1.206.1.2.3.1.1,PMIPV6-MIB::pmip6MagBLEntry,,not-accessible,,current,,An entry containing additional information from a Binding Update sent by the mobile access gateway to the local mobility anchor. 
.1.3.6.1.2.1.206.1.2.3.1.1.1,PMIPV6-MIB::pmip6MagBLFlag,INTEGER,read-only,,current,true(1):false(2),true(1) indicates that the mobile access gateway sent the Proxy Binding Update with Proxy Registration Flag that indicates to the local mobility anchor that the registration is the Proxy Binding Update and is from a mobile access gateway. false(0) implies that the mobile access gateway is behaving as a simple mobile node. 
.1.3.6.1.2.1.206.1.2.3.1.1.2,PMIPV6-MIB::pmip6MagBLMnIndex,Unsigned32,read-only,,current,,The index to the identifier of the attached mobile node in the pmip6MagMnIdentifierTable. 
.1.3.6.1.2.1.206.1.2.3.1.1.3,PMIPV6-MIB::pmip6MagBLMnLLIndex,Unsigned32,read-only,,current,,The index to the link-layer identifier of the mobile node's connected interface in the pmip6MagMnLLIdentifierTable. 
.1.3.6.1.2.1.206.1.2.3.1.1.4,PMIPV6-MIB::pmip6MagBLMagLinkLocalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6MagBLMagLinkLocalAddress that follows. 
.1.3.6.1.2.1.206.1.2.3.1.1.5,PMIPV6-MIB::pmip6MagBLMagLinkLocalAddress,OCTET,read-only,,current,,The link-local address of the mobile access gateway on the access link shared with the mobile node. This is the address that is present in the Link-local Address option of the corresponding Proxy Binding Update message. 
.1.3.6.1.2.1.206.1.2.3.1.1.6,PMIPV6-MIB::pmip6MagBLMagIfIdentifierToMn,OCTET,read-only,,current,,The interface identifier (if-id) of the point-to-point link between the mobile node and the mobile access gateway. This is internal to the mobile access gateway and is used to associate the Proxy Mobile IPv6 tunnel to the access link where the mobile node is attached. 
.1.3.6.1.2.1.206.1.2.3.1.1.7,PMIPV6-MIB::pmip6MagBLTunnelIfIdentifier,OCTET,read-only,,current,,The tunnel interface identifier (tunnel-if-id) of the bidirectional tunnel between the mobile node's local mobility anchor and the mobile access gateway. This is internal to the mobile access gateway. The tunnel interface identifier is acquired during the tunnel creation. 
.1.3.6.1.2.1.206.1.2.3.1.1.8,PMIPV6-MIB::pmip6MagBLMnInterfaceATT,INTEGER,read-only,,current,reserved(0):logicalNetworkInterface(1):pointToPointInterface(2):ethernet(3):wirelessLan(4):wimax(5):threeGPPGERAN(6):threeGPPUTRAN(7):threeGPPEUTRAN(8):threeGPP2eHRPD(9):threeGPP2HRPD(10):threeGPP21xRTT(11):threeGPP2UMB(12),The type of the access technology by which the mobile node is currently attached to the mobile access gateway. 
.1.3.6.1.2.1.206.1.2.3.1.1.9,PMIPV6-MIB::pmip6MagBLTimeRecentlyAccepted,OCTET,read-only,,current,,The 64-bit timestamp value of the most recently accepted Proxy Binding Update message sent for this mobile node. This is the time of day on the mobile access gateway, when the Proxy Binding Acknowledgement message with the Status field set to 0 was received. If the Timestamp option is not present in the Proxy Binding Update message (i.e., when the sequence-number-based scheme is in use), the value MUST be initialized with all zeroes. 
.1.3.6.1.2.1.206.1.2.3.2,PMIPV6-MIB::pmip6MagMnProfileTable,,not-accessible,,current,,This table corresponds to the mobile node's policy profile that includes the essential operational parameters that are required by the network entities for managing the mobile node's mobility service. It contains policy profiles of mobile nodes that are connected to the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.2.3.2.1,PMIPV6-MIB::pmip6MagMnProfileEntry,,not-accessible,pmip6MagProfMnIndex,current,,An entry containing information about the mobile node's policy profile. 
.1.3.6.1.2.1.206.1.2.3.2.1.1,PMIPV6-MIB::pmip6MagProfMnIndex,Unsigned32,not-accessible,,current,,The index for a mobile node in the Proxy Mobile IPv6 domain. 
.1.3.6.1.2.1.206.1.2.3.2.1.2,PMIPV6-MIB::pmip6MagProfMnIdentifier,OCTET,read-only,,current,,The identity of a mobile node in the Proxy Mobile IPv6 domain. 
.1.3.6.1.2.1.206.1.2.3.2.1.3,PMIPV6-MIB::pmip6MagProfMnLocalMobilityAnchorAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6MagMnLocalMobilityAnchorAddress that follows. 
.1.3.6.1.2.1.206.1.2.3.2.1.4,PMIPV6-MIB::pmip6MagProfMnLocalMobilityAnchorAddress,OCTET,read-only,,current,,The global address that is configured on the interface of the local mobility anchor and is the transport endpoint of the bidirectional tunnel established between the local mobility anchor and the mobile access gateway. This is the address to which the mobile access gateway sends the Proxy Binding Update messages. 
.1.3.6.1.2.1.206.1.3,PMIPV6-MIB::pmip6Lma,,,,,,
.1.3.6.1.2.1.206.1.3.1,PMIPV6-MIB::pmip6LmaSystem,,,,,,
.1.3.6.1.2.1.206.1.3.1.1,PMIPV6-MIB::pmip6LmaStatus,INTEGER,read-write,,current,enabled(1):disabled(2),This object indicates whether the PMIPv6 local mobility anchor function is enabled for the managed entity. Changing the status from enabled(1) to disabled(2) will terminate the PMIPv6 local mobility anchor function. On the other hand, changing the status from disabled(2) to enabled(1) will start the PMIPv6 local mobility anchor function. The value of this object MUST remain unchanged across reboots of the managed entity. 
.1.3.6.1.2.1.206.1.3.1.2,PMIPV6-MIB::pmip6LmaLMAATable,,not-accessible,,current,,This table models the LMA Addresses configured on the local mobility anchor. Each LMA Address acts as a transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway and is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.3.1.2.1,PMIPV6-MIB::pmip6LmaLMAAEntry,,not-accessible,pmip6LmaLMAAType:pmip6LmaLMAA,current,,This entry represents a conceptual row in the LMAA table. It represents each LMAA on the local mobility anchor. Implementers need to be aware that if the total number of octets in pmip6LmaLMAA exceeds 113, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.206.1.3.1.2.1.1,PMIPV6-MIB::pmip6LmaLMAAType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6LmaLMAA that follows. 
.1.3.6.1.2.1.206.1.3.1.2.1.2,PMIPV6-MIB::pmip6LmaLMAA,OCTET,not-accessible,,current,,The LMAA configured on the local mobility anchor. The type of the address represented by this object is specified by the corresponding pmip6LmaLMAAType object. 
.1.3.6.1.2.1.206.1.3.1.2.1.3,PMIPV6-MIB::pmip6LmaLMAAState,INTEGER,read-only,,current,unknown(1):activated(2):tunneled(3),This object indicates the state of the LMAA: unknown -- The state of the LMAA cannot be determined. activated -- The LMAA is ready to establish a tunnel. tunneled -- The LMAA is used to set up the bidirectional tunnel. 
.1.3.6.1.2.1.206.1.3.2,PMIPV6-MIB::pmip6LmaConf,,,,,,
.1.3.6.1.2.1.206.1.3.2.1,PMIPV6-MIB::pmip6LmaMinDelayBeforeBCEDelete,Integer32,read-write,,current,,This variable specifies the length of time in milliseconds the local mobility anchor MUST wait before it deletes a Binding Cache entry of a mobile node, upon receiving a Proxy Binding Update message from a mobile access gateway with a lifetime value of 0. During this wait time, if the local mobility anchor receives a Proxy Binding Update for the same mobility binding, with a lifetime value greater than 0, then it must update the Binding Cache entry with the accepted binding values. By the end of this wait time, if the local mobility anchor did not receive any valid Proxy Binding Update message for that mobility binding, it MUST delete the Binding Cache entry. This delay essentially ensures that a mobile node's Binding Cache entry is not deleted too quickly and allows some time for the new mobile access gateway to complete the signaling for the mobile node. The default value for this variable is 10000 milliseconds. 
.1.3.6.1.2.1.206.1.3.2.2,PMIPV6-MIB::pmip6LmaMaxDelayBeforeNewBCEAssign,Integer32,read-write,,current,,This variable specifies the length of time in milliseconds the local mobility anchor MUST wait for the de-registration message for an existing mobility session before it decides to create a new mobility session. The default value for this variable is 1500 milliseconds. Note that there is a dependency between this value and the values used in the retransmission algorithm for Proxy Binding Updates. The retransmissions need to happen before MaxDelayBeforeNewBCEAssign runs out, as otherwise there are situations where a de-registration from a previous mobile access gateway may be lost, and the local mobility anchor creates, needlessly, a new mobility session and new prefixes for the mobile node. However, this affects situations where there is no information from the lower layers about the type of a handoff or other parameters that can be used for identifying the mobility session. 
.1.3.6.1.2.1.206.1.3.2.3,PMIPV6-MIB::pmip6LmaTimestampValidityWindow,Integer32,read-write,,current,,This variable specifies the maximum length of time difference in milliseconds between the timestamp in the received Proxy Binding Update message and the current time of day on the local mobility anchor that is allowed by the local mobility anchor for the received message to be considered valid. The default value for this variable is 300 milliseconds. This variable must be adjusted to suit the deployments. 
.1.3.6.1.2.1.206.1.3.2.4,PMIPV6-MIB::pmip6LmaMnIdentifierTable,,not-accessible,,current,,A table containing the identifiers of mobile nodes served by the LMA. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.3.2.4.1,PMIPV6-MIB::pmip6LmaMnIdentifierEntry,,not-accessible,pmip6BindingMnIndex,current,,An entry in the mobile node identifier table. 
.1.3.6.1.2.1.206.1.3.2.4.1.1,PMIPV6-MIB::pmip6LmaMnIdentifier,OCTET,read-only,,current,,The identity of a mobile node in the Proxy Mobile IPv6 domain. 
.1.3.6.1.2.1.206.1.3.2.5,PMIPV6-MIB::pmip6LmaMnLLIdentifierTable,,not-accessible,,current,,A table containing the link-layer identifiers of the interfaces of the mobile nodes served by the LMA. Entries in this table are not required to survive a reboot of the managed entity. 
.1.3.6.1.2.1.206.1.3.2.5.1,PMIPV6-MIB::pmip6LmaMnLLIdentifierEntry,,not-accessible,pmip6BindingMnIndex:pmip6BindingMnLLIndex,current,,An entry in the mobile node link-layer identifier table. 
.1.3.6.1.2.1.206.1.3.2.5.1.1,PMIPV6-MIB::pmip6LmaMnLLIdentifier,OCTET,read-only,,current,,The link-layer identifier of the mobile node's connected interface on the access link. 
.1.3.6.1.2.1.206.1.3.2.6,PMIPV6-MIB::pmip6LmaHomeNetworkPrefixTable,,not-accessible,,current,,A table representing the home network prefixes assigned to the connected interfaces of all the mobile nodes anchored at the LMA. 
.1.3.6.1.2.1.206.1.3.2.6.1,PMIPV6-MIB::pmip6LmaHomeNetworkPrefixEntry,,not-accessible,pmip6BindingMnIndex:pmip6BindingMnLLIndex:pmip6LmaHomeNetworkPrefixType:pmip6LmaHomeNetworkPrefix,current,,An entry in the home network prefixes table. Implementers need to be aware that if the total number of octets in pmip6LmaHomeNetworkPrefix exceeds 111 then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.206.1.3.2.6.1.1,PMIPV6-MIB::pmip6LmaHomeNetworkPrefixType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the pmip6LmaHomeNetworkPrefix that follows. 
.1.3.6.1.2.1.206.1.3.2.6.1.2,PMIPV6-MIB::pmip6LmaHomeNetworkPrefix,OCTET,not-accessible,,current,,The mobile network prefix that is delegated to the mobile node. The type of the address represented by this object is specified by the corresponding pmip6LmaHomeNetworkPrefixType object. 
.1.3.6.1.2.1.206.1.3.2.6.1.3,PMIPV6-MIB::pmip6LmaHomeNetworkPrefixLength,Unsigned32,read-only,,current,,The prefix length of the home network prefix. 
.1.3.6.1.2.1.206.1.3.2.6.1.4,PMIPV6-MIB::pmip6LmaHomeNetworkPrefixLifeTime,Gauge32,read-write,,current,,The lifetime (in seconds) granted to the mobile node for this registration. 
.1.3.6.1.2.1.206.2,PMIPV6-MIB::pmip6Conformance,,,,,,
.1.3.6.1.2.1.206.2.1,PMIPV6-MIB::pmip6Groups,,,,,,
.1.3.6.1.2.1.206.2.1.1,PMIPV6-MIB::pmip6SystemGroup,,,,,, A collection of objects for basic PMIPv6 monitoring.
.1.3.6.1.2.1.206.2.1.2,PMIPV6-MIB::pmip6BindingCacheGroup,,,,,, A collection of objects for monitoring the PMIPv6 extensions of the Binding Cache.
.1.3.6.1.2.1.206.2.1.3,PMIPV6-MIB::pmip6StatsGroup,,,,,, A collection of objects for basic PMIPv6 statistics monitoring. 
.1.3.6.1.2.1.206.2.1.4,PMIPV6-MIB::pmip6MagSystemGroup,,,,,, A collection of objects for monitoring the PMIPv6-system-related objects on a mobile router.
.1.3.6.1.2.1.206.2.1.5,PMIPV6-MIB::pmip6MagConfigurationGroup,,,,,, A collection of objects for monitoring the configuration-related objects on a mobile access gateway. 
.1.3.6.1.2.1.206.2.1.6,PMIPV6-MIB::pmip6MagRegistrationGroup,,,,,, A collection of objects for monitoring the registration-related objects on a mobile access gateway. 
.1.3.6.1.2.1.206.2.1.7,PMIPV6-MIB::pmip6LmaSystemGroup,,,,,, A collection of objects for monitoring the system-related objects on an LMA.
.1.3.6.1.2.1.206.2.1.8,PMIPV6-MIB::pmip6LmaConfigurationGroup,,,,,, A collection of objects for Monitoring the configuration-related objects on an LMA.
.1.3.6.1.2.1.206.2.1.9,PMIPV6-MIB::pmip6MagNotificationGroup,,,,,,A collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router. 
.1.3.6.1.2.1.206.2.1.10,PMIPV6-MIB::pmip6LmaNotificationGroup,,,,,,A collection of notifications from a home agent or correspondent node to the Manager about the tunnel status of the mobile router. 
.1.3.6.1.2.1.206.2.2,PMIPV6-MIB::pmip6Compliances,,,,,,
.1.3.6.1.2.1.206.2.2.1,PMIPV6-MIB::pmip6CoreCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6BindingHomeAddressType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- ipv6 addresses for the pmip6BindingHomeAddress -- object. -- 
.1.3.6.1.2.1.206.2.2.2,PMIPV6-MIB::pmip6Compliance2,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB. 
.1.3.6.1.2.1.206.2.2.3,PMIPV6-MIB::pmip6CoreReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode). 
.1.3.6.1.2.1.206.2.2.4,PMIPV6-MIB::pmip6ReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode). 
.1.3.6.1.2.1.206.2.2.5,PMIPV6-MIB::pmip6MagCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- 
.1.3.6.1.2.1.206.2.2.6,PMIPV6-MIB::pmip6MagCompliance2,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB for monitoring configuration- related information, registration details, and statistics on a mobile access gateway. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- -- OBJECT pmip6MagHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- 
.1.3.6.1.2.1.206.2.2.7,PMIPV6-MIB::pmip6MagCoreReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode). There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- 
.1.3.6.1.2.1.206.2.2.8,PMIPV6-MIB::pmip6MagReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read- write (i.e., in read-only mode) and with support for monitoring configuration-related information, registration details, and statistics on a mobile access gateway. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6MagProxyCOAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOA -- object. -- -- OBJECT pmip6MagProxyCOA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6MagProxyCOAType -- object. -- -- OBJECT pmip6MagHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- -- OBJECT pmip6MagHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6MagHomeNetworkPrefix object. -- 
.1.3.6.1.2.1.206.2.2.9,PMIPV6-MIB::pmip6LmaCoreCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- 
.1.3.6.1.2.1.206.2.2.10,PMIPV6-MIB::pmip6LmaCompliance2,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB for monitoring configuration- related information, registration details, and statistics on a mobile access gateway. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. -- -- OBJECT pmip6LmaHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. -- 
.1.3.6.1.2.1.206.2.2.11,PMIPV6-MIB::pmip6LmaReadOnlyCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- 
.1.3.6.1.2.1.206.2.2.12,PMIPV6-MIB::pmip6LmaReadOnlyCompliance2,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB without support for read-write (i.e., in read-only mode) and for monitoring configuration-related information, registration details, and statistics on a mobile access gateway. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements, expressed in OBJECT clause form in this description: -- OBJECT pmip6LmaLMAAType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaLMAA -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the pmip6LmaLMAA -- object. -- -- OBJECT pmip6LmaHomeNetworkPrefixType -- SYNTAX InetAddressType { ipv6(2) } -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. -- -- OBJECT pmip6LmaHomeNetworkPrefix -- SYNTAX InetAddress (SIZE(16)) -- DESCRIPTION -- This MIB module requires support for global -- IPv6 addresses for the -- pmip6LmaHomeNetworkPrefix object. -- 
.1.3.6.1.2.1.206.2.2.13,PMIPV6-MIB::pmip6MagNotificationCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB and support notification from the mobile access gateway. 
.1.3.6.1.2.1.206.2.2.14,PMIPV6-MIB::pmip6LmaNotificationCompliance,,,,,,The compliance statement for SNMP entities that implement the PMIPV6-MIB and support notification from the LMA. 
.1.3.6.1.2.1.207,VRRPV3-MIB::vrrpv3MIB,,,,,,This MIB describes objects used for managing Virtual Router Redundancy Protocol version 3 (VRRPv3). Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of the MIB module is part of RFC 6527. Please see the RFC for full legal notices.
.1.3.6.1.2.1.207.0,VRRPV3-MIB::vrrpv3Notifications,,,,,,
.1.3.6.1.2.1.207.0.1,VRRPV3-MIB::vrrpv3NewMaster,,,,,,The newMaster notification indicates that the sending agent has transitioned to master state.
.1.3.6.1.2.1.207.0.2,VRRPV3-MIB::vrrpv3ProtoError,,,,,,The notification indicates that the sending agent has encountered the protocol error indicated by vrrpv3StatisticsProtoErrReason.
.1.3.6.1.2.1.207.1,VRRPV3-MIB::vrrpv3Objects,,,,,,
.1.3.6.1.2.1.207.1.1,VRRPV3-MIB::vrrpv3Operations,,,,,,
.1.3.6.1.2.1.207.1.1.1,VRRPV3-MIB::vrrpv3OperationsTable,,not-accessible,,current,,Unified Operations table for a VRRP router that consists of a sequence (i.e., one or more conceptual rows) of 'vrrpv3OperationsEntry' items each of which describe the operational characteristics of a virtual router.
.1.3.6.1.2.1.207.1.1.1.1,VRRPV3-MIB::vrrpv3OperationsEntry,,not-accessible,ifIndex:vrrpv3OperationsVrId:vrrpv3OperationsInetAddrType,current,,An entry in the vrrpv3OperationsTable containing the operational characteristics of a virtual router. On a VRRP router, a given virtual router is identified by a combination of ifIndex, VRID, and the IP version. ifIndex represents an interface of the router. A row must be created with vrrpv3OperationsStatus set to initialize(1) and cannot transition to backup(2) or master(3) until vrrpv3OperationsRowStatus is transitioned to active(1). The information in this table is persistent and when written the entity SHOULD save the change to non- volatile storage.
.1.3.6.1.2.1.207.1.1.1.1.1,VRRPV3-MIB::vrrpv3OperationsVrId,Integer32,not-accessible,,current,,This object contains the Virtual Router Identifier (VRID).
.1.3.6.1.2.1.207.1.1.1.1.2,VRRPV3-MIB::vrrpv3OperationsInetAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The IP address type of Vrrpv3OperationsEntry and Vrrpv3AssociatedIpAddrEntry. This value determines the type for vrrpv3OperationsMasterIpAddr, vrrpv3OperationsPrimaryIpAddr, and vrrpv3AssociatedIpAddrAddress. ipv4(1) and ipv6(2) are the only two values supported in this MIB module.
.1.3.6.1.2.1.207.1.1.1.1.3,VRRPV3-MIB::vrrpv3OperationsMasterIpAddr,OCTET,read-only,,current,,The master router's real IP address. The master router would set this address to vrrpv3OperationsPrimaryIpAddr while transitioning to master state. For backup routers, this is the IP address listed as the source in the VRRP advertisement last received by this virtual router.
.1.3.6.1.2.1.207.1.1.1.1.4,VRRPV3-MIB::vrrpv3OperationsPrimaryIpAddr,OCTET,read-create,,current,,In the case where there is more than one IP Address (associated IP addresses) for a given 'ifIndex', this object is used to specify the IP address that will become the vrrpv3OperationsMasterIpAddr', should the virtual router transition from backup state to master.
.1.3.6.1.2.1.207.1.1.1.1.5,VRRPV3-MIB::vrrpv3OperationsVirtualMacAddr,OCTET,read-only,,current,,The virtual MAC address of the virtual router. Although this object can be derived from the 'vrrpv3OperationsVrId' object, it is defined so that it is easily obtainable by a management application and can be included in VRRP-related SNMP notifications.
.1.3.6.1.2.1.207.1.1.1.1.6,VRRPV3-MIB::vrrpv3OperationsStatus,INTEGER,read-only,,current,initialize(1):backup(2):master(3),The current state of the virtual router. This object has three defined values: - 'initialize', which indicates that the virtual router is waiting for a startup event. - 'backup', which indicates that the virtual router is monitoring the availability of the master router. - 'master', which indicates that the virtual router is forwarding packets for IP addresses that are associated with this router.
.1.3.6.1.2.1.207.1.1.1.1.7,VRRPV3-MIB::vrrpv3OperationsPriority,Unsigned32,read-create,,current,,This object specifies the priority to be used for the virtual router master election process; higher values imply higher priority. A priority of '0', although not settable, is sent by the master router to indicate that this router has ceased to participate in VRRP, and a backup virtual router should transition to become a new master. A priority of 255 is used for the router that owns the associated IP address(es) for VRRP over IPv4 and hence is not settable. Setting the values of this object to 0 or 255 should be rejected by the agents implementing this MIB module. For example, an SNMP agent would return 'badValue(3)' when a user tries to set the values 0 or 255 for this object.
.1.3.6.1.2.1.207.1.1.1.1.8,VRRPV3-MIB::vrrpv3OperationsAddrCount,Integer32,read-only,,current,,The number of IP addresses that are associated with this virtual router. This number is equal to the number of rows in the vrrpv3AssociatedAddrTable that correspond to a given ifIndex/VRID/IP version.
.1.3.6.1.2.1.207.1.1.1.1.9,VRRPV3-MIB::vrrpv3OperationsAdvInterval,INTEGER,read-create,,current,,The time interval, in centiseconds, between sending advertisement messages. Only the master router sends VRRP advertisements.
.1.3.6.1.2.1.207.1.1.1.1.10,VRRPV3-MIB::vrrpv3OperationsPreemptMode,INTEGER,read-create,,current,true(1):false(2),Controls whether a higher priority virtual router will preempt a lower priority master.
.1.3.6.1.2.1.207.1.1.1.1.11,VRRPV3-MIB::vrrpv3OperationsAcceptMode,INTEGER,read-create,,current,true(1):false(2),Controls whether a virtual router in master state will accept packets addressed to the address owner's IPv6 address as its own if it is not the IPv6 address owner. Default is false(2). This object is not relevant for rows representing VRRP over IPv4 and should be set to false(2).
.1.3.6.1.2.1.207.1.1.1.1.12,VRRPV3-MIB::vrrpv3OperationsUpTime,TimeTicks,read-only,,current,,This value represents the amount of time, in TimeTicks (hundredth of a second), since this virtual router (i.e., the 'vrrpv3OperationsStatus') transitioned out of 'initialize'.
.1.3.6.1.2.1.207.1.1.1.1.13,VRRPV3-MIB::vrrpv3OperationsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the 'vrrpv3OperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpv3OperationsInetAddrType, vrrpv3OperationsVrId, and vrrpv3OperationsPrimaryIpAddr has been set, and there is at least one active row in the 'vrrpv3AssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpv3OperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpv3AssociatedIpAddrTable. 3. Populate the vrrpv3OperationsEntry. 4. Set vrrpv3OperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpv3OperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpv3AssociatedIpAddrTable to destroy(6) to delete the entry. 3. Set vrrpv3OperationsRowStatus to destroy(6) to delete the entry.
.1.3.6.1.2.1.207.1.1.2,VRRPV3-MIB::vrrpv3AssociatedIpAddrTable,,not-accessible,,current,,The table of addresses associated with each virtual router.
.1.3.6.1.2.1.207.1.1.2.1,VRRPV3-MIB::vrrpv3AssociatedIpAddrEntry,,not-accessible,ifIndex:vrrpv3OperationsVrId:vrrpv3OperationsInetAddrType:vrrpv3AssociatedIpAddrAddress,current,,An entry in the table contains an IP address that is associated with a virtual router. The number of rows for a given IP version, VrID, and ifIndex will equal the number of IP addresses associated (e.g., backed up) by the virtual router (equivalent to 'vrrpv3OperationsIpAddrCount'). Rows in the table cannot be modified unless the value of 'vrrpv3OperationsStatus' for the corresponding entry in the vrrpv3OperationsTable has transitioned to initialize(1). The information in this table is persistent and when written the entity SHOULD save the change to non- volatile storage.
.1.3.6.1.2.1.207.1.1.2.1.1,VRRPV3-MIB::vrrpv3AssociatedIpAddrAddress,OCTET,not-accessible,,current,,The assigned IP addresses that a virtual router is responsible for backing up. The IP address type is determined by the value of vrrpv3OperationsInetAddrType in the index of this row.
.1.3.6.1.2.1.207.1.1.2.1.2,VRRPV3-MIB::vrrpv3AssociatedIpAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to installation and removal conventions for conceptual rows. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Setting this object to active(1) results in the addition of an associated address for a virtual router. Setting this object to notInService(2) results in administratively bringing down the row. Destroying the entry or setting it to destroy(6) removes the associated address from the virtual router. The use of other values is implementation-dependent. Implementations should not allow deletion of the last row corresponding to an active row in vrrpv3OperationsTable. Refer to the description of vrrpv3OperationsRowStatus for typical row creation and deletion scenarios.
.1.3.6.1.2.1.207.1.2,VRRPV3-MIB::vrrpv3Statistics,,,,,,
.1.3.6.1.2.1.207.1.2.1,VRRPV3-MIB::vrrpv3RouterChecksumErrors,Counter64,read-only,,current,,The total number of VRRP packets received with an invalid VRRP checksum value. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3GlobalStatisticsDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.2,VRRPV3-MIB::vrrpv3RouterVersionErrors,Counter64,read-only,,current,,The total number of VRRP packets received with an unknown or unsupported version number. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3GlobalStatisticsDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.3,VRRPV3-MIB::vrrpv3RouterVrIdErrors,Counter64,read-only,,current,,The total number of VRRP packets received with a VRID that is not valid for any virtual router on this router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3GlobalStatisticsDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.4,VRRPV3-MIB::vrrpv3GlobalStatisticsDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one of vrrpv3RouterChecksumErrors, vrrpv3RouterVersionErrors, and vrrpv3RouterVrIdErrors suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.207.1.2.5,VRRPV3-MIB::vrrpv3StatisticsTable,,not-accessible,,current,,Table of virtual router statistics.
.1.3.6.1.2.1.207.1.2.5.1,VRRPV3-MIB::vrrpv3StatisticsEntry,,not-accessible,,current,,An entry in the table containing statistics information about a given virtual router.
.1.3.6.1.2.1.207.1.2.5.1.1,VRRPV3-MIB::vrrpv3StatisticsMasterTransitions,Counter32,read-only,,current,,The total number of times that this virtual router's state has transitioned to master state. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.2,VRRPV3-MIB::vrrpv3StatisticsNewMasterReason,INTEGER,read-only,,current,notMaster(0):priority(1):preempted(2):masterNoResponse(3),This indicates the reason for the virtual router to transition to master state. If the virtual router never transitioned to master state, the value of this object is notMaster(0). Otherwise, this indicates the reason this virtual router transitioned to master state the last time. Used by vrrpv3NewMaster notification.
.1.3.6.1.2.1.207.1.2.5.1.3,VRRPV3-MIB::vrrpv3StatisticsRcvdAdvertisements,Counter64,read-only,,current,,The total number of VRRP advertisements received by this virtual router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.4,VRRPV3-MIB::vrrpv3StatisticsAdvIntervalErrors,Counter64,read-only,,current,,The total number of VRRP advertisement packets received for which the advertisement interval is different from the vrrpv3OperationsAdvInterval configured on this virtual router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.5,VRRPV3-MIB::vrrpv3StatisticsIpTtlErrors,Counter64,read-only,,current,,The total number of VRRP packets received by the virtual router with IPv4 TTL (for VRRP over IPv4) or IPv6 Hop Limit (for VRRP over IPv6) not equal to 255. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.6,VRRPV3-MIB::vrrpv3StatisticsProtoErrReason,INTEGER,read-only,,current,noError(0):ipTtlError(1):versionError(2):checksumError(3):vrIdError(4),This indicates the reason for the last protocol error. This SHOULD be set to noError(0) when no protocol errors are encountered. Used by vrrpv3ProtoError notification.
.1.3.6.1.2.1.207.1.2.5.1.7,VRRPV3-MIB::vrrpv3StatisticsRcvdPriZeroPackets,Counter64,read-only,,current,,The total number of VRRP packets received by the virtual router with a priority of '0'. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.8,VRRPV3-MIB::vrrpv3StatisticsSentPriZeroPackets,Counter64,read-only,,current,,The total number of VRRP packets sent by the virtual router with a priority of '0'. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.9,VRRPV3-MIB::vrrpv3StatisticsRcvdInvalidTypePackets,Counter64,read-only,,current,,The number of VRRP packets received by the virtual router with an invalid value in the 'type' field. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.10,VRRPV3-MIB::vrrpv3StatisticsAddressListErrors,Counter64,read-only,,current,,The total number of packets received for which the address list does not match the locally configured list for the virtual router. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.11,VRRPV3-MIB::vrrpv3StatisticsPacketLengthErrors,Counter64,read-only,,current,,The total number of packets received with a packet length less than the length of the VRRP header. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of vrrpv3StatisticsRowDiscontinuityTime.
.1.3.6.1.2.1.207.1.2.5.1.12,VRRPV3-MIB::vrrpv3StatisticsRowDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this entry's counters suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.207.1.2.5.1.13,VRRPV3-MIB::vrrpv3StatisticsRefreshRate,Unsigned32,read-only,,current,,The minimum reasonable polling interval for this entry. This object provides an indication of the minimum amount of time required to update the counters in this entry.
.1.3.6.1.2.1.207.2,VRRPV3-MIB::vrrpv3Conformance,,,,,,
.1.3.6.1.2.1.207.2.1,VRRPV3-MIB::vrrpv3Compliances,,,,,,
.1.3.6.1.2.1.207.2.1.1,VRRPV3-MIB::vrrpv3FullCompliance,,,,,,The compliance statement
.1.3.6.1.2.1.207.2.1.2,VRRPV3-MIB::vrrpv3ReadOnlyCompliance,,,,,,When this MIB module is implemented without support for read-create (i.e., in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored, but cannot be configured with this MIB.
.1.3.6.1.2.1.207.2.2,VRRPV3-MIB::vrrpv3Groups,,,,,,
.1.3.6.1.2.1.207.2.2.1,VRRPV3-MIB::vrrpv3OperationsGroup,,,,,,Conformance group for VRRPv3 operations.
.1.3.6.1.2.1.207.2.2.2,VRRPV3-MIB::vrrpv3StatisticsGroup,,,,,,Conformance group for VRRPv3 statistics.
.1.3.6.1.2.1.207.2.2.3,VRRPV3-MIB::vrrpv3StatisticsDiscontinuityGroup,,,,,,Objects providing information about counter discontinuities.
.1.3.6.1.2.1.207.2.2.4,VRRPV3-MIB::vrrpv3InfoGroup,,,,,,Conformance group for objects contained in VRRPv3 notifications.
.1.3.6.1.2.1.207.2.2.5,VRRPV3-MIB::vrrpv3NotificationsGroup,,,,,,The VRRP MIB Notification Group.
.1.3.6.1.2.1.208,G9981-MIB::g9981MIB,,,,,,The objects in this MIB module are used to manage the multi-pair bonded xDSL interfaces using ATM inverse multiplexing, as defined in ITU-T Recommendation G.998.1 (G.Bond/ATM). This MIB module MUST be used in conjunction with the GBOND-MIB module, common to all G.Bond technologies. The following references are used throughout this MIB module: [G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005. [TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008. Naming Conventions: ATM - Asynchronous Transfer Mode BCE - Bonding Channel Entity BTU - Bonding Terminating Unit CO - Central Office CPE - Customer Premises Equipment GBS - Generic Bonding Sub-layer GBS-C - Generic Bonding Sub-layer, CO side GBS-R - Generic Bonding Sub-layer, RT (or CPE) side PM - Performance Monitoring RT - Remote Terminal SNR - Signal to Noise Ratio SES - Severely Errored Seconds UAS - Unavailable Seconds Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.208.1,G9981-MIB::g9981Objects,,,,,,
.1.3.6.1.2.1.208.1.1,G9981-MIB::g9981Port,,,,,,
.1.3.6.1.2.1.208.1.1.0,G9981-MIB::g9981PortNotifications,,,,,,
.1.3.6.1.2.1.208.1.1.0.1,G9981-MIB::g9981UpDiffDelayToleranceExceeded,,,,,,This notification indicates that the maximum upstream differential delay has exceeded the max upstream differential delay threshold, specified by g9981PortConfUpDiffDelayTolerance. This notification MAY be sent for the GBS-C ports while the port is 'up', on the crossing event in both directions: from normal (diff. delay is above the threshold) to low (diff. delay equals the threshold or is below it) and from low to normal. This notification is not applicable to the GBS-R ports. Generation of this notification is controlled by the g9981PortConfDiffDelayToleranceExceededEnable attribute. This object maps to the TR-159 notification nIMAUpDiffDelayToleranceExceeded.
.1.3.6.1.2.1.208.1.1.0.2,G9981-MIB::g9981DnDiffDelayToleranceExceeded,,,,,,This notification indicates that the maximum downstream differential delay has exceeded the max downstream differential delay threshold, specified by g9981PortConfDnDiffDelayTolerance. This notification MAY be sent for the GBS-C ports while the port is 'up', on the crossing event in both directions: from normal (diff. delay is above the threshold) to low (diff. delay equals the threshold or is below it) and from low to normal. This notification is not applicable to the GBS-R ports. Generation of this notification is controlled by the g9981PortConfDiffDelayToleranceExceededEnable attribute. This object maps to the TR-159 notification nIMADownDiffDelayToleranceExceeded.
.1.3.6.1.2.1.208.1.1.1,G9981-MIB::g9981PortConfTable,,not-accessible,,current,,Table for configuration of G.Bond/ATM ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.208.1.1.1.1,G9981-MIB::g9981PortConfEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/ATM Port Configuration table. Each entry represents a G.Bond/ATM port indexed by the ifIndex. Additional configuration parameters are available via the gBondPortConfEntry of the GBOND-MIB. Note that a G.Bond/ATM port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.208.1.1.1.1.1,G9981-MIB::g9981PortConfUpDiffDelayTolerance,Unsigned32,read-write,,current,,A maximum tolerated upstream differential delay (among the member BCEs) of a G.Bond/ATM port, expressed in ms. This object is read-write for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read or change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aIMAUpDiffDelayTolerance.
.1.3.6.1.2.1.208.1.1.1.1.2,G9981-MIB::g9981PortConfDnDiffDelayTolerance,Unsigned32,read-write,,current,,A maximum tolerated downstream differential delay (among the member BCEs) of a G.Bond/ATM port, expressed in ms. This object is read-write for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read or change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aIMADownDiffDelayTolerance.
.1.3.6.1.2.1.208.1.1.1.1.3,G9981-MIB::g9981PortConfDiffDelayToleranceExceededEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether g9981UpDiffDelayToleranceExceeded and g9981DnDiffDelayToleranceExceeded notifications should be generated for G.Bond/ATM port. A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled. This object is read-write for the GBS-C. It is irrelevant for the GBS-R ports -- an attempt to read or change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aIMADiffDelayToleranceExceededEnable.
.1.3.6.1.2.1.208.1.1.2,G9981-MIB::g9981PortStatTable,,not-accessible,,current,,This table provides overall status information of G.Bond/ATM ports, complementing the generic status information from the ifTable of the IF-MIB and the gBondFltStatus of the GBOND-MIB. Additional status information about connected BCEs is available from the relevant line MIBs. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.208.1.1.2.1,G9981-MIB::g9981PortStatEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/ATM Port Status table. Each entry represents a G.Bond/ATM port indexed by the ifIndex. Note that a GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.208.1.1.2.1.1,G9981-MIB::g9981PortStatRxLostCells,Counter32,read-only,,current,,The number of lost ATM cells detected by the G.Bond/ATM port in the receive direction (e.g., upstream direction for a GBS-C port). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159 attribute aIMARxLostCells.
.1.3.6.1.2.1.208.1.1.2.1.2,G9981-MIB::g9981PortStatTxLostCells,Counter32,read-only,,current,,The number of lost ATM cells detected by the peer G.Bond/ATM port in the receive direction, i.e., downstream direction for a GBS-C port. This object is irrelevant for the GBS-R ports -- an attempt to read it MUST be rejected (in the case of SNMP, with the error inconsistentValue). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159 attribute aIMAPeerRxLostCells.
.1.3.6.1.2.1.208.1.1.2.1.3,G9981-MIB::g9981PortStatMaxUpDiffDelay,Unsigned32,read-only,,current,,Current maximum upstream differential delay between all operational BCEs in the G.Bond/ATM bonding group, measured in units of 0.1 ms. This object is read-only for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read this object MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aIMAMaxUpDiffDelay.
.1.3.6.1.2.1.208.1.1.2.1.4,G9981-MIB::g9981PortStatMaxDnDiffDelay,Unsigned32,read-only,,current,,Current maximum downstream differential delay between all operational BCEs in the G.Bond/ATM bonding group, measured in units of 0.1 ms. This object is read-only for the GBS-C ports. It is irrelevant for the GBS-R ports -- an attempt to read this object MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aIMAMaxDownDiffDelay.
.1.3.6.1.2.1.208.1.1.3,G9981-MIB::g9981PM,,,,,,
.1.3.6.1.2.1.208.1.1.3.1,G9981-MIB::g9981PortPmCurTable,,not-accessible,,current,,This table contains current Performance Monitoring information for a G.Bond/ATM port. This table contains live data from the equipment and as such is NOT persistent.
.1.3.6.1.2.1.208.1.1.3.1.1,G9981-MIB::g9981PortPmCurEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/ATM Port PM table. Each entry represents a G.Bond/ATM port indexed by the ifIndex.
.1.3.6.1.2.1.208.1.1.3.1.1.1,G9981-MIB::g9981PortPmCur15MinValidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object partially maps to the TR-159 attribute aGroupPerf15MinValidIntervals.
.1.3.6.1.2.1.208.1.1.3.1.1.2,G9981-MIB::g9981PortPmCur15MinInvalidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object partially maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals.
.1.3.6.1.2.1.208.1.1.3.1.1.3,G9981-MIB::g9981PortPmCur15MinTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object partially maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed.
.1.3.6.1.2.1.208.1.1.3.1.1.4,G9981-MIB::g9981PortPmCur15MinRxLostCells,Counter64,read-only,,current,,A read-only count of lost ATM cells detected by a G.Bond/ATM port (e.g., the GBS-C) in the receive direction, during the current 15-minute performance history interval. Note that the total number of lost ATM cells is indicated by the g9981PortStatRxLostCells object. This object is inhibited during Severely Errored Seconds (SES) or Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.5,G9981-MIB::g9981PortPmCur15MinTxLostCells,Counter64,read-only,,current,,A read-only count of lost ATM cells detected by the peer G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the current 15-minute performance history interval. Note that the total number of lost ATM cells is indicated by the g9981PortStatTxLostCells object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.6,G9981-MIB::g9981PortPmCur15MinUpDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum upstream differential delay between all operational BCEs in the GBS-C, measured in units of 0.1 ms, during the current 15-minute performance interval. Note that the current max upstream differential delay is indicated by the g9981PortStatMaxUpDiffDelay object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.7,G9981-MIB::g9981PortPmCur15MinDnDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum downstream differential delay between all operational BCEs in the GBS-C (as perceived by the GBS-R), measured in units of 0.1 ms, during the current 15-minute performance history interval. Note that the current max downstream differential delay is indicated by the g9981PortStatMaxDnDiffDelay object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.8,G9981-MIB::g9981PortPmCur1DayValidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day intervals for which data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.
.1.3.6.1.2.1.208.1.1.3.1.1.9,G9981-MIB::g9981PortPmCur1DayInvalidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available.
.1.3.6.1.2.1.208.1.1.3.1.1.10,G9981-MIB::g9981PortPmCur1DayTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 1-day performance interval.
.1.3.6.1.2.1.208.1.1.3.1.1.11,G9981-MIB::g9981PortPmCur1DayRxLostCells,Counter64,read-only,,current,,A read-only count of lost ATM cells detected by the G.Bond/ATM port (e.g., the GBS-C) during the current 1-day performance interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.12,G9981-MIB::g9981PortPmCur1DayTxLostCells,Counter64,read-only,,current,,A read-only count of lost ATM cells detected by the peer G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the current 1-day performance history interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.13,G9981-MIB::g9981PortPmCur1DayUpDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum upstream differential delay between all operational BCEs in the GBS-C, measured in units of 0.1 ms, during the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.1.1.14,G9981-MIB::g9981PortPmCur1DayDnDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum downstream differential delay between all operational BCEs in the GBS-C, measured in units of 0.1 ms, during the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.2,G9981-MIB::g9981PortPm15MinTable,,not-accessible,,current,,This table contains historical 15-minute buckets of Performance Monitoring information for a G.Bond/ATM port (a row for each 15-minute interval, up to 96 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.208.1.1.3.2.1,G9981-MIB::g9981PortPm15MinEntry,,not-accessible,ifIndex:g9981PortPm15MinIntervalIndex,current,,An entry in the G.Bond/ATM Port historical 15-minute PM table. Each entry represents Performance Monitoring data for a G.Bond/ATM port, indexed by the ifIndex, collected during a particular 15-minute interval, indexed by the g9981PortPm15MinIntervalIndex.
.1.3.6.1.2.1.208.1.1.3.2.1.1,G9981-MIB::g9981PortPm15MinIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalNumber.
.1.3.6.1.2.1.208.1.1.3.2.1.2,G9981-MIB::g9981PortPm15MinIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.
.1.3.6.1.2.1.208.1.1.3.2.1.3,G9981-MIB::g9981PortPm15MinIntervalRxLostCells,Counter64,read-only,,current,,A read-only count of lost ATM cells detected by a G.Bond/ATM port (e.g., the GBS-C) in the receive direction, during the 15-minute performance history interval. Note that the total number of lost ATM cells is indicated by the g9981PortStatRxLostCells object. This object is inhibited during Severely Errored Seconds (SES) or Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.2.1.4,G9981-MIB::g9981PortPm15MinIntervalTxLostCells,Counter64,read-only,,current,,A read-only count of lost ATM cells detected by the peer G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the 15-minute performance history interval. Note that the total number of lost ATM cells is indicated by the g9981PortStatTxLostCells object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.2.1.5,G9981-MIB::g9981PortPm15MinIntervalUpDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum upstream differential delay between all operational BCEs in the GBS, measured in units of 0.1 ms, during the 15-minute performance history interval. Note that the current max upstream differential delay is indicated by the g9981PortStatMaxUpDiffDelay object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.2.1.6,G9981-MIB::g9981PortPm15MinIntervalDnDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum downstream differential delay between all operational BCEs in the GBS, as perceived by its peer port, measured in units of 0.1 ms, during the 15-minute performance history interval. Note that the current max downstream differential delay is indicated by the g9981PortStatMaxDnDiffDelay object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.2.1.7,G9981-MIB::g9981PortPm15MinIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalValid.
.1.3.6.1.2.1.208.1.1.3.3,G9981-MIB::g9981PortPm1DayTable,,not-accessible,,current,,This table contains historical 1-day buckets of Performance Monitoring information for a G.Bond/ATM port (a row for each 1-day interval, up to 7 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.208.1.1.3.3.1,G9981-MIB::g9981PortPm1DayEntry,,not-accessible,ifIndex:g9981PortPm1DayIntervalIndex,current,,An entry in the G.Bond/ATM Port historical 1-day PM table. Each entry represents Performance Monitoring data for such a port, indexed by the ifIndex, collected during a particular 1-day interval, indexed by the g9981PortPm1DayIntervalIndex.
.1.3.6.1.2.1.208.1.1.3.3.1.1,G9981-MIB::g9981PortPm1DayIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 7 is 24 hours ago. Intervals 2..7 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber.
.1.3.6.1.2.1.208.1.1.3.3.1.2,G9981-MIB::g9981PortPm1DayIntervalMoniTime,Integer32,read-only,,current,,A count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.208.1.1.3.3.1.3,G9981-MIB::g9981PortPm1DayIntervalRxLostCells,Counter64,read-only,,current,,A count of lost ATM cells detected by the G.Bond/ATM port (e.g., the GBS-C) during the 1-day performance history interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.3.1.4,G9981-MIB::g9981PortPm1DayIntervalTxLostCells,Counter64,read-only,,current,,A count of lost ATM cells detected by the peer G.Bond/ATM port (e.g., by the GBS-R for the GBS-C) during the 1-day performance history interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.3.1.5,G9981-MIB::g9981PortPm1DayIntervalUpDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum upstream differential delay between all operational BCEs in the GBS-C, measured in units of 0.1 ms, during the 1-day performance history interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.3.1.6,G9981-MIB::g9981PortPm1DayIntervalDnDiffDelay,Counter64,read-only,,current,,A read-only value specifying the maximum downstream differential delay between all operational BCEs in the GBS-C, measured in units of 0.1 ms, during the 1-day performance history interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.208.1.1.3.3.1.7,G9981-MIB::g9981PortPm1DayIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalValid.
.1.3.6.1.2.1.208.2,G9981-MIB::g9981Conformance,,,,,,
.1.3.6.1.2.1.208.2.1,G9981-MIB::g9981Groups,,,,,,
.1.3.6.1.2.1.208.2.1.1,G9981-MIB::g9981BasicGroup,,,,,,A collection of objects representing management information for a G.Bond/ATM port.
.1.3.6.1.2.1.208.2.1.2,G9981-MIB::g9981AlarmConfGroup,,,,,,A collection of objects required for configuration of alarm thresholds and notifications in G.Bond/ATM ports.
.1.3.6.1.2.1.208.2.1.3,G9981-MIB::g9981NotificationGroup,,,,,,This group supports notifications of significant conditions associated with G.Bond/ATM ports.
.1.3.6.1.2.1.208.2.1.4,G9981-MIB::g9981PerfCurrGroup,,,,,,A collection of objects supporting OPTIONAL current Performance Monitoring information for G.Bond/ATM ports.
.1.3.6.1.2.1.208.2.1.5,G9981-MIB::g9981Perf15MinGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/ATM ports, during previous 15-minute intervals.
.1.3.6.1.2.1.208.2.1.6,G9981-MIB::g9981Perf1DayGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/ATM ports, during previous 1-day intervals.
.1.3.6.1.2.1.208.2.2,G9981-MIB::g9981Compliances,,,,,,
.1.3.6.1.2.1.208.2.2.1,G9981-MIB::g9981Compliance,,,,,,The compliance statement for G.Bond/ATM interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 GBOND-MIB gBondCompliance
.1.3.6.1.2.1.210,G9983-MIB::g9983MIB,,,,,,The objects in this MIB module are used to manage the multi-pair bonded xDSL interfaces using time-division inverse multiplexing (TDIM), as defined in ITU-T Recommendation G.998.3 (G.Bond/TDIM). This MIB module MUST be used in conjunction with the GBOND-MIB module, common to all G.Bond technologies. The following references are used throughout this MIB module: [G.998.3] refers to: ITU-T Recommendation G.998.3: 'Multi-pair bonding using time-division inverse multiplexing', January 2005. [TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008. Naming Conventions: BCE - Bonding Channel Entity BTU - Bonding Terminating Unit BTU-C - Bonding Terminating Unit, CO side BTU-R - Bonding Terminating Unit, Remote Terminal (CPE) side CO - Central Office CPE - Customer Premises Equipment GBS - Generic Bonding Sub-layer GBS-C - Generic Bonding Sub-layer, CO side GBS-R - Generic Bonding Sub-layer, Remote Terminal (CPE) side SNR - Signal to Noise Ratio Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.210.1,G9983-MIB::g9983Objects,,,,,,
.1.3.6.1.2.1.210.1.1,G9983-MIB::g9983Port,,,,,,
.1.3.6.1.2.1.210.1.1.0,G9983-MIB::g9983PortNotifications,,,,,,
.1.3.6.1.2.1.210.1.1.0.1,G9983-MIB::g9983SvcUp,,,,,,This notification indicates that a service, indicated by the g9983OperSvcIdx (mapped to a particular interface indicated by the g9983SvcIfIdx), in a particular G.Bond/TDIM port is passing traffic. This notification is generated (unless disabled or dropped by the rate-limiting mechanism) when the g9983OperSvcState object has left the 'down' state, while the G.Bond/TDIM port state (the ifOperStatus of the IF-MIB) is 'up'. Generation of this notification is controlled by the g9983PortConfSvcUpDownEnable object. This object maps to the TR-159 notification nServiceUp.
.1.3.6.1.2.1.210.1.1.0.2,G9983-MIB::g9983SvcDown,,,,,,This notification indicates that a service indicated by the g9983OperSvcIdx (mapped to a particular interface indicated by the g9983SvcIfIdx) in a particular G.Bond/TDIM port has stopped passing traffic. This notification is generated (unless disabled or dropped by the rate-limiting mechanism), when the g9983OperSvcState object has entered the 'down' state, while the G.Bond/TDIM port state (the ifOperStatus of the IF-MIB) is 'up'. Generation of this notification is controlled by the g9983PortConfSvcUpDownEnable object. This object maps to the TR-159 notification nServiceDown.
.1.3.6.1.2.1.210.1.1.1,G9983-MIB::g9983PortConfTable,,not-accessible,,current,,Table for configuration of G.Bond/TDIM ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.1.1,G9983-MIB::g9983PortConfEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/TDIM Port Configuration table. Each entry represents a G.Bond/TDIM port indexed by the ifIndex. Additional configuration parameters are available via the gBondPortConfEntry of the GBOND-MIB. Note that a G.Bond/TDIM port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.210.1.1.1.1.1,G9983-MIB::g9983PortConfFecAdminState,INTEGER,read-write,,current,true(1):false(2),A desired state of the OPTIONAL Forward Error Correction (FEC) function of the G.Bond/TDIM port. A value of 'false' indicates that the FEC function SHALL be disabled. A value of 'true' indicates that the FEC function SHALL be enabled, if supported by the G.Bond/TDIM port, as indicated by the g9983PortCapFecSupported object. The g9983PortStatFecOperState object indicates the current operational state of the FEC function. For the GBS-R ports, the value of this object cannot be changed directly. This value may be changed as a result of a write operation on the g9983PortCapFecSupported object of a remote GBS-C. Modifications of this object MUST be performed when the link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing, or if it is a GBS-R. This object maps to the TR-159/G.998.3 attribute aFECAdminState.
.1.3.6.1.2.1.210.1.1.1.1.2,G9983-MIB::g9983PortConfFecWordSize,Unsigned32,read-write,,current,,A FEC code word size, in octets, for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of zero SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the FEC code word size MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECWordSize.
.1.3.6.1.2.1.210.1.1.1.1.3,G9983-MIB::g9983PortConfFecRedundancySize,Unsigned32,read-write,,current,,A FEC redundancy word size, in octets, for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of zero SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the FEC redundancy word size MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECRedundancySize.
.1.3.6.1.2.1.210.1.1.1.1.4,G9983-MIB::g9983PortConfFecInterleaverType,INTEGER,read-write,,current,none(0):block(1):convolution(2),An Interleaver type for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of none(0) SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the Interleaver type MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECInterleaverType.
.1.3.6.1.2.1.210.1.1.1.1.5,G9983-MIB::g9983PortConfFecInterleaverDepth,Unsigned32,read-write,,current,,An Interleaver depth for G.Bond/TDIM ports supporting the FEC function. This object is read-write for the GBS-C ports and read-only for the GBS-R. A value of zero SHALL be returned if the FEC function is disabled (via g9983PortConfFecAdminState) or not supported. Changing of the Interleaver depth MUST be performed when the FEC-enabled link is 'down'. Attempts to change this object MUST be rejected if the link is 'up' or initializing or if the FEC function is disabled/not supported. This object maps to the TR-159/G.998.3 attribute aFECInterleaverDepth.
.1.3.6.1.2.1.210.1.1.1.1.6,G9983-MIB::g9983PortConfAdminServices,OCTET,read-write,,current,,Desired list of services for a G.Bond/TDIM port. This object is a list of pointers to entries in the g9983SvcTable. The value of this object is a continuous ordered list of up to 60 indices (g9983SvcIdx) of the active services carried via the G.Bond/TDIM link. The position of a service in the list determines its relative priority in cases of bandwidth degradation -- the priority decreases towards the end of the list, which means that the last service in the list would be suspended first when the bandwidth degrades. This object is writable and readable for the GBS-C ports. It is irrelevant for the GBS-R ports -- a zero-length octet string SHALL be returned on an attempt to read this object, and an attempt to change this object MUST be rejected in this case. Note that the current operational service list is available via the g9983OperSvcTable object. This object for a GBS-C port MAY be modified independently of the link's state, i.e., in-service and out-of-service. Attempts to set this object to a list with a member value that is not the value of the index for an active entry in the corresponding g9983SvcTable table MUST be rejected.
.1.3.6.1.2.1.210.1.1.1.1.7,G9983-MIB::g9983PortConfSvcUpDownEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether g9983SvcUp and g9983SvcDown notifications should be generated for this interface. A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled. This object maps to the TR-159 attribute aServiceUpDownEnable.
.1.3.6.1.2.1.210.1.1.2,G9983-MIB::g9983PortCapTable,,not-accessible,,current,,Table for capabilities of G.Bond/TDIM ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.2.1,G9983-MIB::g9983PortCapEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/TDIM Port Capability table. Each entry represents a G.Bond/TDIM port indexed by the ifIndex. Additional capabilities are available via the gBondPortCapabilityEntry of the GBOND-MIB. Note that a G.Bond/TDIM port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.210.1.1.2.1.1,G9983-MIB::g9983PortCapFecSupported,INTEGER,read-only,,current,true(1):false(2),FEC and Interleaver capability of the G.Bond/TDIM port. This object has a value of true(1) when the port supports the FEC and Interleaver function. A value of false(2) is returned when the port does not support the FEC and Interleaver function. This object maps to the TR-159/G.998.3 attribute aFECSupported.
.1.3.6.1.2.1.210.1.1.2.1.2,G9983-MIB::g9983PortCapFecMaxWordSize,Unsigned32,read-only,,current,,A maximum supported FEC code word size, in octets, for G.Bond/TDIM ports supporting the FEC function. A value of zero SHALL be returned if the FEC function is not supported. This object maps to the TR-159 attribute aFECWordSize.
.1.3.6.1.2.1.210.1.1.2.1.3,G9983-MIB::g9983PortCapFecMaxRedundancySize,Unsigned32,read-only,,current,,A maximum supported FEC redundancy word size, in octets, for G.Bond/TDIM ports supporting the FEC function. A value of zero SHALL be returned if the FEC function is not supported. This object maps to the TR-159 attribute aFECMaxRedundancySize.
.1.3.6.1.2.1.210.1.1.2.1.4,G9983-MIB::g9983PortCapFecInterleaverTypeSupported,INTEGER,read-only,,current,none(0):block(1):convolution(2):blockConvolution(3),Supported Interleaver types for G.Bond/TDIM ports supporting the FEC function. Possible values are: none - the port does not support interleaving block - the port supports Block Interleaver convolution - the port supports Convolution Interleaver blockConvolution - the port supports both Block Interleaver and Convolution Interleaver This object maps to the TR-159 attribute aFECInterleaverTypesSupported.
.1.3.6.1.2.1.210.1.1.2.1.5,G9983-MIB::g9983PortCapFecMaxInterleaverDepth,Unsigned32,read-only,,current,,A maximum Interleaver depth for G.Bond/TDIM ports supporting the FEC function. A value of zero SHALL be returned if the Interleaver is not supported. This object maps to the TR-159 attribute aFECMaxInterleaverDepth.
.1.3.6.1.2.1.210.1.1.3,G9983-MIB::g9983PortStatTable,,not-accessible,,current,,This table provides overall status information of G.Bond TDIM ports, complementing the generic status information from the ifTable of the IF-MIB and the gBondPortStatFltStatus of the GBOND-MIB. Additional status information about connected BCEs is available from the relevant line MIBs. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.210.1.1.3.1,G9983-MIB::g9983PortStatEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/TDIM Port Status table. Each entry represents a G.Bond/TDIM port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.210.1.1.3.1.1,G9983-MIB::g9983PortStatFecOperState,INTEGER,read-only,,current,true(1):false(2),A read-only value indicating the current operational state of the OPTIONAL Forward Error Correction (FEC) function for the G.998.3 port. A value of 'false' indicates that the FEC function is disabled. A value of 'true' indicates that the FEC function is enabled (and supported). This object maps to the TR-159 attribute aFECOperState.
.1.3.6.1.2.1.210.1.1.3.1.2,G9983-MIB::g9983PortStatFltStatus,BITS,read-only,,current,serviceDown(0):wrongConfig(1),G.Bond/TDIM port fault status. This is a bitmap of possible conditions. The various bit positions are: serviceDown - at least one of the services defined for this aggregation group is down (due to low rate). wrongConfig - at least one BCE at the remote GBS-R is already connected to another GBS. This object is intended to supplement the ifOperStatus object in the IF-MIB and the gBondPortStatFltStatus object in the GBOND-MIB.
.1.3.6.1.2.1.210.1.1.3.1.3,G9983-MIB::g9983PortStatCrc4Errors,Counter32,read-only,,current,,The total number of CRC-4 errors (frame header errors) on all pairs in the G.Bond/TDIM port. Simultaneous errors on M lines SHOULD be counted M times. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159/G.998.3 attribute aCRC4Errors.
.1.3.6.1.2.1.210.1.1.3.1.4,G9983-MIB::g9983PortStatCrc6Errors,Counter32,read-only,,current,,The total number of CRC-6 errors (super-frame errors) on all pairs in the G.Bond/TDIM port. Simultaneous errors on M lines SHOULD be counted 1 time. Discontinuities in the value of this counter can occur at re-initialization of the local management subsystem, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159/G.998.3 attribute aCRC6Errors.
.1.3.6.1.2.1.210.1.1.3.1.5,G9983-MIB::g9983PortStatCrc8Errors,Counter32,read-only,,current,,The total number of CRC-8 errors (event/message errors) on all pairs in the G.Bond/TDIM port. Simultaneous errors on M lines SHOULD be counted M times. Discontinuities in the value of this counter can occur at re-initialization of the local management subsystem, and at other times as indicated by the value of ifCounterDiscontinuityTime as defined in the IF-MIB. This object maps to the TR-159/G.998.3 attribute aCRC8Errors.
.1.3.6.1.2.1.210.1.1.4,G9983-MIB::g9983OperSvcTable,,not-accessible,,current,,Table of the operational services configured on a G.Bond/TDIM port. This table reflects current actual service configuration, set by the g9983PortConfAdminServices object. The number of entries (services) in this table therefore can vary between 0, when no services are configured, and 60, for the maximum number of services. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.210.1.1.4.1,G9983-MIB::g9983OperSvcEntry,,not-accessible,ifIndex:g9983OperSvcPosition,current,,An entry in the G.Bond/TDIM Port Operational Service table, containing the index of an active service entry in the g9983SvcTable. The entry is indexed by the ifIndex, indicating a corresponding G.Bond/TDIM port, and by g9983OperSvcPosition (1..60), indicating the corresponding service position in the G.Bond/TDIM frame.
.1.3.6.1.2.1.210.1.1.4.1.1,G9983-MIB::g9983OperSvcPosition,Unsigned32,not-accessible,,current,,G.Bond/TDIM operational service position -- a unique index, indicating relative placement of the associated service pointed to by g9983OperSvcIdx, within the G.Bond/TDIM frame. There can be up to 60 services defined over a TDIM bonded facility. Services with lower indices have higher priority in cases of bandwidth degradation. The value of g9983OperSvcPosition for the first g9983OperSvcEntry is always 1, incrementing sequentially for each consecutive entry, i.e., 2 for the second entry, 3 for the third, etc. This objects maps to the TR-159/G.998.3 attribute aServiceID.
.1.3.6.1.2.1.210.1.1.4.1.2,G9983-MIB::g9983OperSvcIdx,Unsigned32,read-only,,current,,G.Bond/TDIM operational service index -- a read-only pointer to an existing entry in the g9983SvcTable (value of g9983SvcIdx) describing a particular service.
.1.3.6.1.2.1.210.1.1.4.1.3,G9983-MIB::g9983OperSvcState,INTEGER,read-only,,current,up(1):down(2),G.Bond/TDIM service operational state. Possible values are: up - Service is up and passing traffic. down - Service is down, due to a variety of reasons, e.g., G.Bond/TDIM port is down, current link bandwidth is too low to support a particular service, etc. This objects maps to the TR-159 attribute aServiceOperState.
.1.3.6.1.2.1.210.1.1.5,G9983-MIB::g9983SvcTable,,not-accessible,,current,,Table of possible services for G.Bond/TDIM ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.5.1,G9983-MIB::g9983SvcEntry,,not-accessible,ifIndex:g9983SvcIdx,current,,An entry in the G.Bond/TDIM Port Service table, containing the management information applicable to a particular service, indexed by the g9983SvcIdx, on a G.Bond/TDIM port, indexed by the ifIndex.
.1.3.6.1.2.1.210.1.1.5.1.1,G9983-MIB::g9983SvcIdx,Unsigned32,not-accessible,,current,,G.Bond/TDIM service index -- a unique index associated with a particular service entry.
.1.3.6.1.2.1.210.1.1.5.1.2,G9983-MIB::g9983SvcIfIdx,Integer32,read-create,,current,,This is a unique index within the ifTable. It represents the interface index of a service to be transmitted over the G.Bond/TDIM service instance. This objects maps to the TR-159 attribute aServiceIfIndex.
.1.3.6.1.2.1.210.1.1.5.1.3,G9983-MIB::g9983SvcType,INTEGER,read-create,,current,ds1(0):e1(1):nxds0(2):nxe0(3):ds3(4):e3(5):clock(6):ethernet(7):atm(8):gfpNoFCS(9):gfp(10),G.Bond/TDIM service type. Possible values are: ds1 - Clear Channel DS1 (synchronous) e1 - Clear Channel E1 (synchronous) nxds0 - Fractional DS1 (synchronous) nxe0 - Fractional E1 (synchronous) ds3 - DS3 (synchronous) e3 - E3 (synchronous) clock - Clock transfer (synchronous) ethernet - Ethernet (asynchronous) atm - ATM (asynchronous) gfpNoFCS - GFP encapsulated without FCS (asynchronous) gfp - GFP encapsulated with FCS (asynchronous) For the GBS-R ports, the value of this object cannot be changed directly. This value may be changed as a result of a write operation on the g9983SvcType object of a remote GBS-C. Attempts to change this object MUST be rejected for the GBS-R ports. This object maps to the TR-159/G.998.3 attribute aServiceType.
.1.3.6.1.2.1.210.1.1.5.1.4,G9983-MIB::g9983SvcSize,Unsigned32,read-create,,current,,Service size, in octets, per bonding sub-block for a specific service identified by g9983SvcIdx. For TDM (synchronous) services with variable size (e.g., fractional DS1/E1), this object represents the number of DS0/E0 channels. For asynchronous services (Ethernet, ATM, GFPnoFCS, or GFP), this object represents the maximum number of octets. For non-fractional TDM services (i.e., DS1, E1, DS3, E3, and clock), the value of this object MUST be 0. A GET operation returns the current value. A SET operation, allowed on GBS-C ports, changes the service size to the indicated value. If the service type is a fixed-rate synchronous service (g9983SvcType is nxds0, nxe0, ds1, e1, ds3, e3, or clock), the operation MUST be rejected. This object maps to the TR-159/G.998.3 attribute aServiceSize.
.1.3.6.1.2.1.210.1.1.5.1.5,G9983-MIB::g9983SvcRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls the creation, modification, or deletion of the associated entry in the g9983SvcTable per the semantics of RowStatus. If an 'active' entry is referenced via g9983OperSvcIdx or a g9983PortConfAdminServices instance, or indexes a g9983SvcPm*Entry, the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set to 'active' again.
.1.3.6.1.2.1.210.1.1.6,G9983-MIB::g9983PM,,,,,,
.1.3.6.1.2.1.210.1.1.6.1,G9983-MIB::g9983PortPmCurTable,,not-accessible,,current,,This table contains current Performance Monitoring information for a G.Bond/TDIM port. This table contains live data from the equipment and as such is NOT persistent.
.1.3.6.1.2.1.210.1.1.6.1.1,G9983-MIB::g9983PortPmCurEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/TDIM Port PM table. Each entry represents a G.Bond/TDIM port indexed by the ifIndex.
.1.3.6.1.2.1.210.1.1.6.1.1.1,G9983-MIB::g9983PortPmCur15MinValidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object partially maps to the TR-159 attribute aGroupPerf15MinValidIntervals.
.1.3.6.1.2.1.210.1.1.6.1.1.2,G9983-MIB::g9983PortPmCur15MinInvalidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object partially maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals.
.1.3.6.1.2.1.210.1.1.6.1.1.3,G9983-MIB::g9983PortPmCur15MinTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object partially maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed.
.1.3.6.1.2.1.210.1.1.6.1.1.4,G9983-MIB::g9983PortPmCur15MinCrc4s,Counter64,read-only,,current,,A read-only count of CRC-4 errors (frame header errors) on all active pairs in the G.Bond/TDIM port during the current 15-minute performance interval. Simultaneous errors on M lines SHOULD be counted M times. Note that the total number of CRC-4 errors is indicated by the g9983PortStatCrc4Errors object. This object is inhibited during Severely Errored Seconds (SES) or Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.1.1.5,G9983-MIB::g9983PortPmCur15MinCrc6s,Counter64,read-only,,current,,A read-only count of CRC-6 errors (super-frame errors) on all active pairs in the G.Bond/TDIM port during the current 15-minute performance interval. Simultaneous errors on M lines SHOULD be counted 1 time. Note that the total number of CRC-6 errors is indicated by the g9983PortStatCrc6Errors object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.1.1.6,G9983-MIB::g9983PortPmCur15MinCrc8s,Counter64,read-only,,current,,A read-only count of CRC-8 errors (event/message errors) on all active pairs in the G.Bond/TDIM port during the current 15-minute performance interval. Simultaneous errors on M lines SHOULD be counted M times. Note that the total number of CRC-8 errors is indicated by the g9983PortStatCrc8Errors object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.1.1.7,G9983-MIB::g9983PortPmCur1DayValidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day intervals for which data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.
.1.3.6.1.2.1.210.1.1.6.1.1.8,G9983-MIB::g9983PortPmCur1DayInvalidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available.
.1.3.6.1.2.1.210.1.1.6.1.1.9,G9983-MIB::g9983PortPmCur1DayTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 1-day performance interval.
.1.3.6.1.2.1.210.1.1.6.1.1.10,G9983-MIB::g9983PortPmCur1DayCrc4s,Counter64,read-only,,current,,A read-only count of CRC-4 errors on the G.Bond/TDIM port in the current 1-day performance interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.1.1.11,G9983-MIB::g9983PortPmCur1DayCrc6s,Counter64,read-only,,current,,A read-only count of CRC-6 errors on the G.Bond/TDIM port in the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.1.1.12,G9983-MIB::g9983PortPmCur1DayCrc8s,Counter64,read-only,,current,,A read-only count of CRC-8 errors on the G.Bond/TDIM port in the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.2,G9983-MIB::g9983PortPm15MinTable,,not-accessible,,current,,This table contains historical 15-minute buckets of Performance Monitoring information for a G.Bond/TDIM port (a row for each 15-minute interval, up to 96 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.6.2.1,G9983-MIB::g9983PortPm15MinEntry,,not-accessible,ifIndex:g9983PortPm15MinIntervalIndex,current,,An entry in the G.Bond/TDIM Port historical 15-minute PM table. Each entry represents Performance Monitoring data for a G.Bond TDIM port, indexed by the ifIndex, collected during a particular 15-minute interval, indexed by the g9983PortPm15MinIntervalIndex.
.1.3.6.1.2.1.210.1.1.6.2.1.1,G9983-MIB::g9983PortPm15MinIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalNumber.
.1.3.6.1.2.1.210.1.1.6.2.1.2,G9983-MIB::g9983PortPm15MinIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.
.1.3.6.1.2.1.210.1.1.6.2.1.3,G9983-MIB::g9983PortPm15MinIntervalCrc4s,Counter64,read-only,,current,,A read-only count of CRC-4 errors on the G.Bond/TDIM port during the 15-minute performance history interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.2.1.4,G9983-MIB::g9983PortPm15MinIntervalCrc6s,Counter64,read-only,,current,,A read-only count of CRC-6 errors on the G.Bond/TDIM port during the 15-minute performance history interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.2.1.5,G9983-MIB::g9983PortPm15MinIntervalCrc8s,Counter64,read-only,,current,,A read-only count of CRC-8 errors on the G.Bond/TDIM port during the current 15-minute performance interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.2.1.6,G9983-MIB::g9983PortPm15MinIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalValid.
.1.3.6.1.2.1.210.1.1.6.3,G9983-MIB::g9983PortPm1DayTable,,not-accessible,,current,,This table contains historical 1-day buckets of Performance Monitoring information for a G.Bond/TDIM port (a row for each 1-day interval, up to 7 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.6.3.1,G9983-MIB::g9983PortPm1DayEntry,,not-accessible,ifIndex:g9983PortPm1DayIntervalIndex,current,,An entry in the G.Bond/TDIM Port historical 1-day PM table. Each entry represents Performance Monitoring data for such a port, indexed by the ifIndex, collected during a particular 1-day interval, indexed by the g9983PortPm1DayIntervalIndex.
.1.3.6.1.2.1.210.1.1.6.3.1.1,G9983-MIB::g9983PortPm1DayIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber.
.1.3.6.1.2.1.210.1.1.6.3.1.2,G9983-MIB::g9983PortPm1DayIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.210.1.1.6.3.1.3,G9983-MIB::g9983PortPm1DayIntervalCrc4s,Counter64,read-only,,current,,A read-only count of CRC-4 errors on the G.Bond/TDIM port during the 1-day performance history interval. This object is inhibited during Severely Errored Seconds (SES) and Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.3.1.4,G9983-MIB::g9983PortPm1DayIntervalCrc6s,Counter64,read-only,,current,,A read-only count of CRC-6 errors on the G.Bond/TDIM port during the 1-day performance history interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.3.1.5,G9983-MIB::g9983PortPm1DayIntervalCrc8s,Counter64,read-only,,current,,A read-only count of CRC-8 errors on the G.Bond/TDIM port during the current 1-day performance interval. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.3.1.6,G9983-MIB::g9983PortPm1DayIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalValid.
.1.3.6.1.2.1.210.1.1.6.4,G9983-MIB::g9983SvcPmCurTable,,not-accessible,,current,,This table contains current Performance Monitoring information for the services of a G.Bond/TDIM port. This table contains live data from the equipment and as such is NOT persistent.
.1.3.6.1.2.1.210.1.1.6.4.1,G9983-MIB::g9983SvcPmCurEntry,,not-accessible,ifIndex:g9983SvcIdx,current,,An entry in the G.Bond/TDIM Services PM table. Each entry represents a service, indexed by the g9983SvcIdx, in a G.Bond/TDIM port, indexed by the ifIndex.
.1.3.6.1.2.1.210.1.1.6.4.1.1,G9983-MIB::g9983SvcPmCur15MinValidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object partially maps to the TR-159 attribute aGroupPerf15MinValidIntervals.
.1.3.6.1.2.1.210.1.1.6.4.1.2,G9983-MIB::g9983SvcPmCur15MinInvalidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object partially maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals.
.1.3.6.1.2.1.210.1.1.6.4.1.3,G9983-MIB::g9983SvcPmCur15MinTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object partially maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed.
.1.3.6.1.2.1.210.1.1.6.4.1.4,G9983-MIB::g9983SvcPmCur15MinDowns,Counter64,read-only,,current,,A read-only count of seconds in the current 15-minute performance interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.4.1.5,G9983-MIB::g9983SvcPmCur1DayValidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day performance history intervals for which the data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.
.1.3.6.1.2.1.210.1.1.6.4.1.6,G9983-MIB::g9983SvcPmCur1DayInvalidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day performance history intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available.
.1.3.6.1.2.1.210.1.1.6.4.1.7,G9983-MIB::g9983SvcPmCur1DayTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 1-day performance interval.
.1.3.6.1.2.1.210.1.1.6.4.1.8,G9983-MIB::g9983SvcPmCur1DayDowns,Counter64,read-only,,current,,A read-only count of seconds in the current 1-day performance interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.5,G9983-MIB::g9983SvcPm15MinTable,,not-accessible,,current,,This table contains historical 15-minute buckets of Performance Monitoring information for the services of a G.Bond/TDIM port (a multi-dimensional row for each 15-minute interval, up to 96 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.6.5.1,G9983-MIB::g9983SvcPm15MinEntry,,not-accessible,ifIndex:g9983SvcIdx:g9983SvcPm15MinIntervalIndex,current,,An entry in the G.Bond/TDIM Service historical 15-minute PM table. Each entry represents Performance Monitoring data for a particular service, indexed by the g9983SvcIdx, in a G.Bond TDIM port, indexed by the ifIndex, collected during a particular 15-minute interval, indexed by the g9983SvcPm15MinIntervalIndex.
.1.3.6.1.2.1.210.1.1.6.5.1.1,G9983-MIB::g9983SvcPm15MinIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalNumber.
.1.3.6.1.2.1.210.1.1.6.5.1.2,G9983-MIB::g9983SvcPm15MinIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.
.1.3.6.1.2.1.210.1.1.6.5.1.3,G9983-MIB::g9983SvcPm15MinIntervalDowns,Counter64,read-only,,current,,A read-only count of seconds in the 15-minute performance history interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.5.1.4,G9983-MIB::g9983SvcPm15MinIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalValid.
.1.3.6.1.2.1.210.1.1.6.6,G9983-MIB::g9983SvcPm1DayTable,,not-accessible,,current,,This table contains historical 1-day buckets of Performance Monitoring information for the services of a G.Bond/TDIM port (a multi-dimensional row for each 1-day interval, up to 7 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.210.1.1.6.6.1,G9983-MIB::g9983SvcPm1DayEntry,,not-accessible,ifIndex:g9983SvcIdx:g9983SvcPm1DayIntervalIndex,current,,An entry in the G.Bond/TDIM Service historical 1-day PM table. Each entry represents Performance Monitoring data for a particular service, indexed by the g9983SvcIdx, defined in a G.Bond/TDIM port, indexed by the ifIndex, collected during a particular 1-day interval, indexed by the g9983SvcPm1DayIntervalIndex.
.1.3.6.1.2.1.210.1.1.6.6.1.1,G9983-MIB::g9983SvcPm1DayIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber.
.1.3.6.1.2.1.210.1.1.6.6.1.2,G9983-MIB::g9983SvcPm1DayIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.210.1.1.6.6.1.3,G9983-MIB::g9983SvcPm1DayIntervalDowns,Counter64,read-only,,current,,A read-only count of seconds in the 1-day performance history interval during which a particular TDIM service was 'down', as indicated by the g9983OperSvcState object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.210.1.1.6.6.1.4,G9983-MIB::g9983SvcPm1DayIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalValid.
.1.3.6.1.2.1.210.2,G9983-MIB::g9983Conformance,,,,,,
.1.3.6.1.2.1.210.2.1,G9983-MIB::g9983Groups,,,,,,
.1.3.6.1.2.1.210.2.1.1,G9983-MIB::g9983BasicGroup,,,,,,A collection of objects representing management information for G.Bond/TDIM ports.
.1.3.6.1.2.1.210.2.1.2,G9983-MIB::g9983FecGroup,,,,,,A collection of objects supporting the OPTIONAL Forward Error Correction (FEC) and Interleaver function in G.Bond/TDIM ports.
.1.3.6.1.2.1.210.2.1.3,G9983-MIB::g9983AlarmConfGroup,,,,,,A collection of objects required for configuration of alarm thresholds and notifications in G.Bond/TDIM ports.
.1.3.6.1.2.1.210.2.1.4,G9983-MIB::g9983NotificationGroup,,,,,,This group supports notifications of significant conditions associated with G.Bond/TDIM ports.
.1.3.6.1.2.1.210.2.1.5,G9983-MIB::g9983PerfCurrGroup,,,,,,A collection of objects supporting OPTIONAL current Performance Monitoring information for G.Bond/TDIM ports.
.1.3.6.1.2.1.210.2.1.6,G9983-MIB::g9983Perf15MinGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/TDIM ports, during previous 15-minute intervals.
.1.3.6.1.2.1.210.2.1.7,G9983-MIB::g9983Perf1DayGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/TDIM ports, during previous 1-day intervals.
.1.3.6.1.2.1.210.2.2,G9983-MIB::g9983Compliances,,,,,,
.1.3.6.1.2.1.210.2.2.1,G9983-MIB::g9983Compliance,,,,,,The compliance statement for G.Bond/TDIM interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 GBOND-MIB gBondCompliance
.1.3.6.1.2.1.211,GBOND-MIB::gBondMIB,,,,,,The objects in this MIB module are used to manage the multi-pair bonded xDSL interfaces, as defined in ITU-T Recommendations G.998.1, G.998.2, and G.998.3. This MIB module MUST be used in conjunction with a bonding scheme-specific MIB module, that is, G9981-MIB, G9982-MIB, or G9983-MIB. The following references are used throughout this MIB module: [G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005. [G.998.2] refers to: ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair bonding', January 2005. [G.998.3] refers to: ITU-T Recommendation G.998.3: 'Multi-pair bonding using time-division inverse multiplexing', January 2005. [TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008. Naming Conventions: BCE - Bonding Channel Entity BTU - Bonding Terminating Unit BTU-C - Bonding Terminating Unit, CO side BTU-R - Bonding Terminating Unit, Remote Terminal (CPE) side CO - Central Office CPE - Customer Premises Equipment GBS - Generic Bonding Sub-layer PM - Performance Monitoring SNR - Signal to Noise Ratio TCA - Threshold Crossing Alert Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.211.1,GBOND-MIB::gBondObjects,,,,,,
.1.3.6.1.2.1.211.1.1,GBOND-MIB::gBondPort,,,,,,
.1.3.6.1.2.1.211.1.1.0,GBOND-MIB::gBondPortNotifications,,,,,,
.1.3.6.1.2.1.211.1.1.0.1,GBOND-MIB::gBondLowUpRateCrossing,,,,,,This notification indicates that the G.Bond port's upstream data rate has reached/dropped below or exceeded the low upstream rate threshold, specified by gBondPortConfThreshLowUpRate. This notification MAY be sent for the -O subtype ports while the port is 'up', on the crossing event in both directions: from normal (rate is above the threshold) to low (rate equals the threshold or is below it) and from low to normal. This notification is not applicable to the -R subtypes. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and notification, be implemented to prevent simultaneous LinkUp/LinkDown and gBondLowUpRateCrossing notifications from being sent. The adaptive nature of the G.Bond technology allows the port to adapt itself to the changes in the copper environment; e.g., an impulse noise, alien crosstalk, or a micro-interruption may temporarily drop one or more BCEs in the aggregation group, causing a rate degradation of the aggregated G.Bond link. The dropped BCEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide the required target SNR margin. Generation of this notification is controlled by the gBondPortConfLowRateCrossingEnable object. This object maps to the TR-159 notification nGroupLowUpRateCrossing.
.1.3.6.1.2.1.211.1.1.0.2,GBOND-MIB::gBondLowDnRateCrossing,,,,,,This notification indicates that the G.Bond port's downstream data rate has reached/dropped below or exceeded the low downstream rate threshold, specified by gBondPortConfThreshLowDnRate. This notification MAY be sent for the -O subtype ports while the port is 'up', on the crossing event in both directions: from normal (rate is above the threshold) to low (rate equals the threshold or is below it) and from low to normal. This notification is not applicable to the -R subtypes. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and notification, be implemented to prevent simultaneous LinkUp/LinkDown and gBondLowDnRateCrossing notifications from being sent. The adaptive nature of the G.Bond technology allows the port to adapt itself to the changes in the copper environment; e.g., an impulse noise, alien crosstalk, or a micro-interruption may temporarily drop one or more BCEs in the aggregation group, causing a rate degradation of the aggregated G.Bond link. The dropped BCEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide the required target SNR margin. Generation of this notification is controlled by the gBondPortConfLowRateCrossingEnable object. This object maps to the TR-159 notification nGroupLowDownRateCrossing.
.1.3.6.1.2.1.211.1.1.0.3,GBOND-MIB::gBondPmTca15MinESCrossing,,,,,,This notification indicates that the Errored Seconds threshold, specified by gBondPortPmTcaProfileThresh15MinES, has been reached or exceeded for the GBS port. Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh15MinES objects. This object maps to the TR-159 notification nGroupPerfTca15MinES.
.1.3.6.1.2.1.211.1.1.0.4,GBOND-MIB::gBondPmTca15MinSESCrossing,,,,,,This notification indicates that the Severely Errored Seconds threshold, specified by gBondPortPmTcaProfileThresh15MinSES, has been reached or exceeded for the GBS port. Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh15MinSES objects. This object maps to the TR-159 notification nGroupPerfTca15MinSES.
.1.3.6.1.2.1.211.1.1.0.5,GBOND-MIB::gBondPmTca15MinUASCrossing,,,,,,This notification indicates that the Unavailable Seconds threshold, specified by gBondPortPmTcaProfileThresh15MinUAS, has been reached or exceeded for the GBS port. Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh15MinUAS objects. This object maps to the TR-159 notification nGroupPerfTca15MinUAS.
.1.3.6.1.2.1.211.1.1.0.6,GBOND-MIB::gBondPmTca1DayESCrossing,,,,,,This notification indicates that the Errored Seconds threshold, specified by gBondPortPmTcaProfileThresh1DayES, has been reached or exceeded for the GBS port. Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh1DayES objects. This object maps to the TR-159 notification nGroupPerfTca1DayES.
.1.3.6.1.2.1.211.1.1.0.7,GBOND-MIB::gBondPmTca1DaySESCrossing,,,,,,This notification indicates that the Severely Errored Seconds threshold, specified by gBondPortPmTcaProfileThresh1DaySES, has been reached or exceeded for the GBS port. Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh1DaySES objects. This object maps to the TR-159 notification nGroupPerfTca1DaySES.
.1.3.6.1.2.1.211.1.1.0.8,GBOND-MIB::gBondPmTca1DayUASCrossing,,,,,,This notification indicates that the Unavailable Seconds threshold, specified by gBondPortPmTcaProfileThresh1DayUAS, has been reached or exceeded for the GBS port. Generation of this notification is controlled by the gBondPortConfPmTcaEnable and gBondPortPmTcaProfileThresh1DayUAS objects. This object maps to the TR-159 notification nGroupPerfTca1DayUAS.
.1.3.6.1.2.1.211.1.1.1,GBOND-MIB::gBondPortConfTable,,not-accessible,,current,,Table for configuration of G.Bond GBS ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.211.1.1.1.1,GBOND-MIB::gBondPortConfEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond Port Configuration table. Each entry represents a G.Bond port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.211.1.1.1.1.1,GBOND-MIB::gBondPortConfAdminScheme,INTEGER,read-write,,current,none(0):g9981(1):g9982(2):g9983(3),A desired bonding scheme for a G.Bond GBS port. The following values instruct the port to use the corresponding bonding scheme if supported: none(0) - instructs the port not to use bonding (only on a single-BCE G.998.2 GBS) g9981(1) - instructs the port to use G.998.1 bonding g9982(2) - instructs the port to use G.998.2 bonding g9983(3) - instructs the port to use G.998.3 bonding Changing of the gBondPortConfAdminScheme object MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. Attempts to change this object to an unsupported bonding scheme (see gBondPortCapSchemesSupported) SHALL be rejected (in the case of SNMP, with the error wrongValue). Setting this object to the value of 'none' must be rejected for GBS ports with multiple BCEs (with the error inconsistentValue). This object maps to the TR-159 attribute aGroupAdminBondScheme.
.1.3.6.1.2.1.211.1.1.1.1.2,GBOND-MIB::gBondPortConfPeerAdminScheme,INTEGER,read-write,,current,none(0):g9981(1):g9982(2):g9983(3),A desired bonding scheme for a peer (link partner) G.Bond port (GBS). The following values instruct the peer port to use the corresponding bonding scheme if supported: none(0) - instructs the port not to use bonding (only on a single-BCE G.998.2 GBS) g9981(1) - instructs the port to use G.998.1 bonding g9982(2) - instructs the port to use G.998.2 bonding g9983(3) - instructs the port to use G.998.3 bonding Changing of this object MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. Attempts to change this object to an unsupported bonding scheme (see gBondPortCapPeerSchemesSupported) SHALL be rejected (in the case of SNMP, with the error wrongValue). Setting this object to the value of 'none' must be rejected for GBS ports with multiple BCEs (with the error inconsistentValue). This object maps to the TR-159 attribute aGroupPeerAdminBondScheme.
.1.3.6.1.2.1.211.1.1.1.1.3,GBOND-MIB::gBondPortConfDiscoveryCode,OCTET,read-write,,current,,A discovery code of the G.Bond port (GBS). A unique 6-octet-long code used by the Discovery function. This object MUST be instantiated for the -O subtype GBS before write operations on the gBondBceConfRemoteDiscoveryCode (Set_if_Clear and Clear_if_Same) are performed by BCEs associated with the GBS. The initial value of this object for -R subtype ports after reset is all zeroes. For -R subtype ports, the value of this object cannot be changed directly. This value may be changed as a result of a write operation on the gBondBceConfRemoteDiscoveryCode object of a remote BCE of -O subtype, connected to one of the local BCEs associated with the GBS. Discovery MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. This object maps to the TR-159 attribute aGroupDiscoveryCode.
.1.3.6.1.2.1.211.1.1.1.1.4,GBOND-MIB::gBondPortConfTargetUpDataRate,Unsigned32,read-write,,current,,A desired G.Bond port data rate in the upstream direction, in Kbps, to be achieved during initialization, under restrictions placed upon the member BCEs by their respective configuration settings. This object represents a sum of individual BCE upstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap). Note that the target upstream data rate may not be achieved during initialization (e.g., due to unavailability of required BCEs) or the initial bandwidth could deteriorate, so that the actual upstream data rate (gBondPortStatUpDataRate) could be less than gBondPortConfTargetUpDataRate. The value is limited above by 10 Gbps, to accommodate very high speed bonded xDSL interfaces (e.g., 32 x 100 Mbps). The value between 1 and 10000000 indicates that the total upstream data rate of the G.Bond port after initialization SHALL be equal to the target data rate or less, if the target upstream data rate cannot be achieved under the restrictions configured for BCEs. In cases where the copper environment allows a higher upstream data rate to be achieved than that specified by this object, the excess capability SHALL be either converted to an additional SNR margin or reclaimed by minimizing transmit power. The value of 0 means that the target data rate is not fixed and SHALL be set to the maximum attainable rate during initialization (best effort), under specified spectral restrictions and with a desired SNR margin per BCE. This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue). Changing of the target upstream data rate MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. This object maps to the TR-159 attribute aGroupTargetUpRate.
.1.3.6.1.2.1.211.1.1.1.1.5,GBOND-MIB::gBondPortConfTargetDnDataRate,Unsigned32,read-write,,current,,A desired G.Bond port data rate in the downstream direction, in Kbps, to be achieved during initialization, under restrictions placed upon the member BCEs by their respective configuration settings. This object represents a sum of individual BCE downstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap). Note that the target downstream data rate may not be achieved during initialization (e.g., due to unavailability of required BCEs) or the initial bandwidth could deteriorate, so that the actual downstream data rate (gBondPortStatDnDataRate) could be less than gBondPortConfTargetDnDataRate. The value is limited above by 10 Gbps, to accommodate very high speed bonded xDSL interfaces (e.g., 32 x 100 Mbps). The value between 1 and 10000000 indicates that the total downstream data rate of the G.Bond port after initialization SHALL be equal to the target data rate or less, if the target downstream data rate cannot be achieved under the restrictions configured for BCEs. In cases where the copper environment allows a higher downstream data rate to be achieved than that specified by this object, the excess capability SHALL be either converted to an additional SNR margin or reclaimed by minimizing transmit power. The value of 0 means that the target data rate is not fixed and SHALL be set to the maximum attainable rate during initialization (best effort), under specified spectral restrictions and with a desired SNR margin per BCE. This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue). Changing of the target downstream data rate MUST be performed when the link is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), if the link is 'up' or initializing. This object maps to the TR-159 attribute aGroupTargetDownRate.
.1.3.6.1.2.1.211.1.1.1.1.6,GBOND-MIB::gBondPortConfThreshLowUpRate,Unsigned32,read-write,,current,,This object configures the G.Bond port low upstream rate crossing alarm threshold. When the current value of gBondPortStatUpDataRate for this port reaches/drops below or exceeds this threshold, a gBondLowUpRateCrossing notification MAY be generated if enabled by gBondPortConfLowRateCrossingEnable. This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aGroupthreshLowUpRate.
.1.3.6.1.2.1.211.1.1.1.1.7,GBOND-MIB::gBondPortConfThreshLowDnRate,Unsigned32,read-write,,current,,This object configures the G.Bond port low downstream rate crossing alarm threshold. When the current value of gBondPortStatDnDataRate for this port reaches/drops below or exceeds this threshold, a gBondLowDnRateCrossing notification MAY be generated if enabled by gBondPortConfLowRateCrossingEnable. This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aGroupThreshLowDownRate.
.1.3.6.1.2.1.211.1.1.1.1.8,GBOND-MIB::gBondPortConfLowRateCrossingEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether gBondLowUpRateCrossing and gBondLowDnRateCrossing notifications should be generated for this interface. A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled. This object is read-write for the -O subtype G.Bond ports. It is irrelevant for the -R subtypes -- attempts to read or change this object for such ports MUST be rejected (in the case of SNMP, with the error inconsistentValue). This object maps to the TR-159 attribute aGroupLowRateCrossingEnable.
.1.3.6.1.2.1.211.1.1.1.1.9,GBOND-MIB::gBondPortConfPmTcaConfProfile,OCTET,read-write,,current,,The value of this object is the index of the row in the GBS Port Alarm Configuration Profile table for Performance Monitoring Threshold Crossing Alerts -- the gBondPortAlarmConfProfileTable, which applies to this GBS port.
.1.3.6.1.2.1.211.1.1.1.1.10,GBOND-MIB::gBondPortConfPmTcaEnable,INTEGER,read-write,,current,true(1):false(2),Indicates whether the gBondPerfTca*Crossing set of notifications should be generated for this interface. A value of true(1) indicates that the notifications are enabled. A value of false(2) indicates that the notifications are disabled. This object maps to the TR-159 attribute aGroupPerfTcaEnable.
.1.3.6.1.2.1.211.1.1.2,GBOND-MIB::gBondPortCapTable,,not-accessible,,current,,Table for capabilities of G.Bond ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.211.1.1.2.1,GBOND-MIB::gBondPortCapEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond Port Capability table. Each entry represents a G.Bond port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.211.1.1.2.1.1,GBOND-MIB::gBondPortCapSchemesSupported,BITS,read-only,,current,none(0):g9981(1):g9982(2):g9983(3),Bonding capability of the G.Bond port (GBS). This is a read-only bitmap of the possible bonding schemes supported by the GBS. The various bit positions are: none(0) - GBS is capable of bonding bypass on a single-BCE G.998.2 GBS g9981(1) - GBS is capable of G.998.1 bonding g9982(2) - GBS is capable of G.998.2 bonding g9983(3) - GBS is capable of G.998.3 bonding Note that for ports supporting multiple bonding schemes, the actual administrative scheme is set via gBondPortConfAdminScheme object. The current operating bonding scheme is reflected in the gBondPortStatOperScheme object. This object maps to the TR-159 attribute aGroupBondSchemesSupported.
.1.3.6.1.2.1.211.1.1.2.1.2,GBOND-MIB::gBondPortCapPeerSchemesSupported,BITS,read-only,,current,none(0):g9981(1):g9982(2):g9983(3),Bonding capability of the peer G.Bond port (GBS). This is a read-only bitmap of the possible bonding schemes supported by the link partner GBS. The various bit positions are: none(0) - peer GBS does not support bonding, or the peer unit could not be reached, or peer GBS is capable of bonding bypass on a single-BCE G.998.2 GBS g9981(1) - peer GBS is capable of G.998.1 bonding g9982(2) - peer GBS is capable of G.998.2 bonding g9983(3) - peer GBS is capable of G.998.3 bonding Note that for ports supporting multiple bonding schemes, the actual administrative scheme is set via the gBondPortConfPeerAdminScheme object. The current operating bonding scheme is reflected in the gBondPortStatPeerOperScheme object. This object maps to the TR-159 attribute aGroupPeerBondSchemesSupported.
.1.3.6.1.2.1.211.1.1.2.1.3,GBOND-MIB::gBondPortCapCapacity,Unsigned32,read-only,,current,,Number of BCEs that can be aggregated by the local GBS. The number of BCEs currently assigned to a particular G.Bond port (gBondPortStatNumBCEs) is never greater than gBondPortCapCapacity. This object maps to the TR-159 attribute aGroupCapacity.
.1.3.6.1.2.1.211.1.1.2.1.4,GBOND-MIB::gBondPortCapPeerCapacity,Unsigned32,read-only,,current,,Number of BCEs that can be aggregated by the peer GBS port. A value of 0 is returned when peer Bonding capacity is unknown (peer cannot be reached). This object maps to the TR-159 attribute aGroupPeerCapacity.
.1.3.6.1.2.1.211.1.1.3,GBOND-MIB::gBondPortStatTable,,not-accessible,,current,,This table provides overall status information of G.Bond ports, complementing the generic status information from the ifTable of the IF-MIB. Additional status information about connected BCEs is available from the relevant line MIBs. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.211.1.1.3.1,GBOND-MIB::gBondPortStatEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond Port Status table. Each entry represents a G.Bond port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.211.1.1.3.1.1,GBOND-MIB::gBondPortStatOperScheme,INTEGER,read-only,,current,none(0):g9981(1):g9982(2):g9983(3),Current operating bonding scheme of a G.Bond port. The possible values are: none(0) - bonding bypass on a single-BCE G.998.2 GBS g9981(1) - G.998.1 bonding g9982(2) - G.998.2 bonding g9983(3) - G.998.3 bonding This object maps to the TR-159 attribute aGroupOperBondScheme.
.1.3.6.1.2.1.211.1.1.3.1.2,GBOND-MIB::gBondPortStatPeerOperScheme,INTEGER,read-only,,current,none(0):g9981(1):g9982(2):g9983(3),Current operating bonding scheme of a G.Bond port link partner. The possible values are: unknown(0) - peer cannot be reached due to the link state or bonding bypass on a single-BCE G.998.2 GBS g9981(1) - G.998.1 bonding g9982(2) - G.998.2 bonding g9983(3) - G.998.3 bonding This object maps to the TR-159 attribute aGroupPeerOperBondScheme.
.1.3.6.1.2.1.211.1.1.3.1.3,GBOND-MIB::gBondPortStatUpDataRate,Gauge32,read-only,,current,,A current G.Bond port operational data rate in the upstream direction, in bps. This object represents an estimation of the sum of individual BCE upstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap). Note that for symmetrical interfaces, gBondPortStatUpDataRate == gBondPortStatDnDataRate == ifSpeed. This object maps to the TR-159 attribute aGroupUpRate.
.1.3.6.1.2.1.211.1.1.3.1.4,GBOND-MIB::gBondPortStatDnDataRate,Gauge32,read-only,,current,,A current G.Bond port operational data rate in the downstream direction, in bps. This object represents an estimation of the sum of individual BCE downstream data rates, modified to compensate for fragmentation and encapsulation overhead (e.g., for an Ethernet service, the target data rate of 10 Mbps SHALL allow lossless transmission of full-duplex 10-Mbps Ethernet frame stream with minimal inter-frame gap). Note that for symmetrical interfaces, gBondPortStatUpDataRate == gBondPortStatDnDataRate == ifSpeed. This object maps to the TR-159 attribute aGroupDownRate.
.1.3.6.1.2.1.211.1.1.3.1.5,GBOND-MIB::gBondPortStatFltStatus,BITS,read-only,,current,noPeer(0):peerPowerLoss(1):peerBondSchemeMismatch(2):bceSubTypeMismatch(3):lowRate(4):init(5):ready(6),G.Bond (GBS) port fault status. This is a bitmap of possible conditions. The various bit positions are: noPeer - Peer GBS cannot be reached (e.g., no BCEs attached, all BCEs are 'down', etc.). peerPowerLoss - Peer GBS has indicated impending unit failure due to loss of local power ('Dying Gasp'). peerBondSchemeMismatch - Operating bonding scheme of a peer GBS is different from the local one. bceSubTypeMismatch - Local BCEs in the aggregation group are not of the same sub-type, e.g., some BCEs in the local device are -O while others are -R subtype. lowRate - gBondUpRate/gBondDnRate of the port has reached or dropped below gBondPortConfThreshLowUpRate/ gBondPortConfThreshLowDnRate. init - The link is initializing, as a result of ifAdminStatus being set to 'up' for a particular BCE or a GBS to which the BCE is connected. ready - At least one BCE in the aggregation group is detecting handshake tones. This object is intended to supplement the ifOperStatus object in the IF-MIB. This object maps to the TR-159 attribute aGroupStatus.
.1.3.6.1.2.1.211.1.1.3.1.6,GBOND-MIB::gBondPortStatSide,INTEGER,read-only,,current,subscriber(1):office(2):unknown(3),G.Bond port mode of operation (subtype). The value of 'subscriber' indicates that the port is designated as '-R' subtype (all BCEs assigned to this port are of subtype '-R'). The value of 'office' indicates that the port is designated as '-O' subtype (all BCEs assigned to this port are of subtype '-O'). The value of 'unknown' indicates that the port has no assigned BCEs yet or that the assigned BCEs are not of the same side (subTypeBCEMismatch). This object maps to the TR-159 attribute aGroupEnd.
.1.3.6.1.2.1.211.1.1.3.1.7,GBOND-MIB::gBondPortStatNumBCEs,Unsigned32,read-only,,current,,Number of BCEs that are currently aggregated by the local GBS (assigned to the G.Bond port using the ifStackTable). This number is never greater than gBondPortCapCapacity. This object SHALL be automatically incremented or decremented when a BCE is added or deleted to/from the G.Bond port using the ifStackTable. This object maps to the TR-159 attribute aGroupNumChannels.
.1.3.6.1.2.1.211.1.1.4,GBOND-MIB::gBondPortPM,,,,,,
.1.3.6.1.2.1.211.1.1.4.1,GBOND-MIB::gBondPortPmCurTable,,not-accessible,,current,,This table contains current Performance Monitoring (PM) information for a GBS port. This table contains live data from the equipment and as such is NOT persistent.
.1.3.6.1.2.1.211.1.1.4.1.1,GBOND-MIB::gBondPortPmCurEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond Port PM table. Each entry represents a G.Bond port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.211.1.1.4.1.1.1,GBOND-MIB::gBondPortPmCurES,Counter64,read-only,,current,,A count of Errored Seconds (ES) on the GBS since the BTU was last restarted. An Errored Second for a G.998.x interface is defined as a count of 1-second intervals during which one or more GBS errors are declared. The errors are specific for each bonding scheme, e.g., - lost cells for the ATM bonding - lost or discarded (due to an error or a buffer overflow) fragments for the Ethernet bonding - CRC-4, CRC-6, or CRC-8 errors for the TDIM bonding This object is inhibited during Unavailable Seconds (UAS). This object maps to the TR-159 attribute aGroupPerfES.
.1.3.6.1.2.1.211.1.1.4.1.1.2,GBOND-MIB::gBondPortPmCurSES,Counter64,read-only,,current,,A count of Severely Errored Seconds (SES) on the GBS since the BTU was last restarted. A Severely Errored Second for a G.998.x interface is defined as a count of 1-second intervals during which GBS errors cause at least 1% traffic loss of the nominal bonded link rate or at least 12 ms for the TDM traffic. The exact definition is specific for each bonding scheme, e.g., - 234 lost cells for the ATM bonding with 10-Mbps nominal link rate - 60 lost/discarded fragments for the Ethernet bonding with 10-Mbps nominal link rate and fixed 192-byte-long fragment size - 6 or more CRC-4 errors, one or more CRC-6 errors, or one or more CRC-8 errors for the TDM bonding This object is inhibited during Unavailable Seconds (UAS). This object maps to the TR-159 attribute aGroupPerfSES.
.1.3.6.1.2.1.211.1.1.4.1.1.3,GBOND-MIB::gBondPortPmCurUAS,Counter64,read-only,,current,,A count of Unavailable Seconds (UAS) on the GBS since the BTU was last restarted. An Unavailable Second for a G.998.x interface is defined as a count of 1-second intervals during which the bonded link is unavailable. The G.998.x link becomes unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in the unavailable time. Once unavailable, the G.998.x line becomes available at the onset of 10 contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from the unavailable time. This object maps to the TR-159 attribute aGroupPerfUAS.
.1.3.6.1.2.1.211.1.1.4.1.1.4,GBOND-MIB::gBondPortPmCur15MinValidIntervals,Integer32,read-only,,current,,A number of 15-minute intervals for which data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object maps to the TR-159 attribute aGroupPerf15MinValidIntervals.
.1.3.6.1.2.1.211.1.1.4.1.1.5,GBOND-MIB::gBondPortPmCur15MinInvalidIntervals,Integer32,read-only,,current,,A number of 15-minute intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals.
.1.3.6.1.2.1.211.1.1.4.1.1.6,GBOND-MIB::gBondPortPmCur15MinTimeElapsed,Integer32,read-only,,current,,A count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed.
.1.3.6.1.2.1.211.1.1.4.1.1.7,GBOND-MIB::gBondPortPmCur15MinES,Counter64,read-only,,current,,A count of Errored Seconds (ES) on the GBS in the current 15-minute performance interval. This object maps to the TR-159 attribute aGroupPerfCurr15MinES.
.1.3.6.1.2.1.211.1.1.4.1.1.8,GBOND-MIB::gBondPortPmCur15MinSES,Counter64,read-only,,current,,A count of Severely Errored Seconds (SES) on the GBS in the current 15-minute performance interval. This object maps to the TR-159 attribute aGroupPerfCurr15MinSES.
.1.3.6.1.2.1.211.1.1.4.1.1.9,GBOND-MIB::gBondPortPmCur15MinUAS,Counter64,read-only,,current,,A count of Unavailable Seconds (UAS) on the GBS in the current 15-minute performance interval. This object maps to the TR-159 attribute aGroupPerfCurr15MinUAS.
.1.3.6.1.2.1.211.1.1.4.1.1.10,GBOND-MIB::gBondPortPmCur1DayValidIntervals,Unsigned32,read-only,,current,,A number of 1-day intervals for which data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object maps to the TR-159 attribute aGroupPerf1DayValidIntervals.
.1.3.6.1.2.1.211.1.1.4.1.1.11,GBOND-MIB::gBondPortPmCur1DayInvalidIntervals,Unsigned32,read-only,,current,,A number of 1-day intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object maps to the TR-159 attribute aGroupPerf1DayInvalidIntervals.
.1.3.6.1.2.1.211.1.1.4.1.1.12,GBOND-MIB::gBondPortPmCur1DayTimeElapsed,Integer32,read-only,,current,,A count of seconds that have elapsed since the beginning of the current 1-day performance interval. This object maps to the TR-159 attribute aGroupPerfCurr1DayTimeElapsed.
.1.3.6.1.2.1.211.1.1.4.1.1.13,GBOND-MIB::gBondPortPmCur1DayES,Counter64,read-only,,current,,A count of Errored Seconds (ES) on the GBS in the current 1-day performance interval. This object maps to the TR-159 attribute aGroupPerfCurr1DayES.
.1.3.6.1.2.1.211.1.1.4.1.1.14,GBOND-MIB::gBondPortPmCur1DaySES,Counter64,read-only,,current,,A count of Severely Errored Seconds (SES) on the GBS in the current 1-day performance interval. This object maps to the TR-159 attribute aGroupPerfCurr1DaySES.
.1.3.6.1.2.1.211.1.1.4.1.1.15,GBOND-MIB::gBondPortPmCur1DayUAS,Counter64,read-only,,current,,A count of Unavailable Seconds (UAS) on the GBS in the current 1-day performance interval. This object maps to the TR-159 attribute aGroupPerfCurr1DayUAS.
.1.3.6.1.2.1.211.1.1.4.2,GBOND-MIB::gBondPortPm15MinTable,,not-accessible,,current,,This table contains historical 15-minute buckets of Performance Monitoring information for a GBS port (a row for each 15-minute interval, up to 96 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.211.1.1.4.2.1,GBOND-MIB::gBondPortPm15MinEntry,,not-accessible,ifIndex:gBondPortPm15MinIntervalIndex,current,,An entry in the G.Bond Port historical 15-minute PM table. Each entry represents Performance Monitoring data for a GBS port, indexed by the ifIndex, collected during a particular 15-minute interval, indexed by the gBondPortPm15MinIntervalIndex.
.1.3.6.1.2.1.211.1.1.4.2.1.1,GBOND-MIB::gBondPortPm15MinIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object maps to the TR-159 attribute aGroupPerf15MinIntervalNumber.
.1.3.6.1.2.1.211.1.1.4.2.1.2,GBOND-MIB::gBondPortPm15MinIntervalMoniTime,Integer32,read-only,,current,,A count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.
.1.3.6.1.2.1.211.1.1.4.2.1.3,GBOND-MIB::gBondPortPm15MinIntervalES,Counter64,read-only,,current,,A count of Errored Seconds (ES) on the GBS in the 15-minute performance history interval. This object maps to the TR-159 attribute aGroupPerf15MinIntervalES.
.1.3.6.1.2.1.211.1.1.4.2.1.4,GBOND-MIB::gBondPortPm15MinIntervalSES,Counter64,read-only,,current,,A count of Severely Errored Seconds (SES) on the GBS in the 15-minute performance history interval. This object maps to the TR-159 attribute aGroupPerf15MinIntervalSES.
.1.3.6.1.2.1.211.1.1.4.2.1.5,GBOND-MIB::gBondPortPm15MinIntervalUAS,Counter64,read-only,,current,,A count of Unavailable Seconds (UAS) on the GBS in the current 15-minute performance interval. This object maps to the TR-159 attribute aGroupPerf15MinIntervalUAS.
.1.3.6.1.2.1.211.1.1.4.2.1.6,GBOND-MIB::gBondPortPm15MinIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object maps to the TR-159 attribute aGroupPerf15MinIntervalValid.
.1.3.6.1.2.1.211.1.1.4.3,GBOND-MIB::gBondPortPm1DayTable,,not-accessible,,current,,This table contains historical 1-day buckets of Performance Monitoring information for a GBS port (a row for each 1-day interval, up to 7 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.211.1.1.4.3.1,GBOND-MIB::gBondPortPm1DayEntry,,not-accessible,ifIndex:gBondPortPm1DayIntervalIndex,current,,An entry in the G.Bond Port historical 1-day PM table. Each entry represents Performance Monitoring data for a GBS port, indexed by the ifIndex, collected during a particular 1-day interval, indexed by the gBondPortPm1DayIntervalIndex.
.1.3.6.1.2.1.211.1.1.4.3.1.1,GBOND-MIB::gBondPortPm1DayIntervalIndex,Unsigned32,not-accessible,,current,,Performance data interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL. This object maps to the TR-159 attribute aGroupPerf1DayIntervalNumber.
.1.3.6.1.2.1.211.1.1.4.3.1.2,GBOND-MIB::gBondPortPm1DayIntervalMoniTime,Integer32,read-only,,current,,A count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.211.1.1.4.3.1.3,GBOND-MIB::gBondPortPm1DayIntervalES,Counter64,read-only,,current,,A count of Errored Seconds (ES) on the GBS in the 1-day performance history interval. This object maps to the TR-159 attribute aGroupPerf1DayIntervalES.
.1.3.6.1.2.1.211.1.1.4.3.1.4,GBOND-MIB::gBondPortPm1DayIntervalSES,Counter64,read-only,,current,,A count of Severely Errored Seconds (SES) on the GBS in the 1-day performance history interval. This object maps to the TR-159 attribute aGroupPerf1DayIntervalSES.
.1.3.6.1.2.1.211.1.1.4.3.1.5,GBOND-MIB::gBondPortPm1DayIntervalUAS,Counter64,read-only,,current,,A count of Unavailable Seconds (UAS) on the GBS in the current 1-day performance interval. This object maps to the TR-159 attribute aGroupPerf1DayIntervalUAS.
.1.3.6.1.2.1.211.1.1.4.3.1.6,GBOND-MIB::gBondPortPm1DayIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU-C MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object maps to the TR-159 attribute aGroupPerf1DayIntervalValid.
.1.3.6.1.2.1.211.1.1.4.4,GBOND-MIB::gBondPortPmTcaProfileTable,,not-accessible,,current,,This table supports definitions of Performance Monitoring (PM) Threshold Crossing Alert (TCA) configuration profiles for GBS ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.211.1.1.4.4.1,GBOND-MIB::gBondPortPmTcaProfileEntry,,not-accessible,gBondPortPmTcaProfileName,current,,An entry in the GBS PM TCA Configuration table. Each entry corresponds to a single TCA configuration profile. Each profile contains a set of parameters for setting alarm thresholds for various performance attributes monitored at GBS ports. Profiles may be created/deleted using the row creation/deletion mechanism via gBondPortPmTcaProfileRowStatus. If an active entry is referenced via gBondPortConfPmTcaConfProfile, the entry MUST remain active until all references are removed. A default profile with an index of 'DEFVAL' will always exist, and its parameters will be set to vendor-specific values unless otherwise specified in this document.
.1.3.6.1.2.1.211.1.1.4.4.1.1,GBOND-MIB::gBondPortPmTcaProfileName,OCTET,not-accessible,,current,,This object is a unique index (name) associated with this GBS PM TCA profile.
.1.3.6.1.2.1.211.1.1.4.4.1.2,GBOND-MIB::gBondPortPmTcaProfileThresh15MinES,Unsigned32,read-create,,current,,A desired threshold for the number of Errored Seconds (ES) within any given 15-minute performance data collection interval. If the number of ESs in a particular 15-minute collection interval reaches or exceeds this value, a gBondPmTca15MinESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca15MinESCrossing notification. This object maps to the TR-159 attribute aGroupPerfThreshold15MinES.
.1.3.6.1.2.1.211.1.1.4.4.1.3,GBOND-MIB::gBondPortPmTcaProfileThresh15MinSES,Unsigned32,read-create,,current,,A desired threshold for the number of Severely Errored Seconds (SES) within any given 15-minute performance data collection interval. If the number of SESs in a particular 15-minute collection interval reaches or exceeds this value, a gBondPmTca15MinSESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca15MinSESCrossing notification. This object maps to the TR-159 attribute aGroupPerfThreshold15MinSES.
.1.3.6.1.2.1.211.1.1.4.4.1.4,GBOND-MIB::gBondPortPmTcaProfileThresh15MinUAS,Unsigned32,read-create,,current,,A desired threshold for the number of Unavailable Seconds (UAS) within any given 15-minute performance data collection interval. If the number of UASs in a particular 15-minute collection interval reaches or exceeds this value, a gBondPmTca15MinUASCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca15MinUASCrossing notification. This object maps to the TR-159 attribute aGroupPerfThreshold15MinUAS.
.1.3.6.1.2.1.211.1.1.4.4.1.5,GBOND-MIB::gBondPortPmTcaProfileThresh1DayES,Unsigned32,read-create,,current,,A desired threshold for the number of Errored Seconds (ES) within any given 1-day performance data collection interval. If the number of ESs in a particular 1-day collection interval reaches or exceeds this value, a gBondPmTca1DayESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca1DayESCrossing notification. This object maps to the TR-159 attribute aGroupPerfThreshold1DayES.
.1.3.6.1.2.1.211.1.1.4.4.1.6,GBOND-MIB::gBondPortPmTcaProfileThresh1DaySES,Unsigned32,read-create,,current,,A desired threshold for the number of Severely Errored Seconds (SES) within any given 1-day performance data collection interval. If the number of SESs in a particular 1-day collection interval reaches or exceeds this value, a gBondPmTca1DaySESCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca1DaySESCrossing notification. This object maps to the TR-159 attribute aGroupPerfThreshold1DaySES.
.1.3.6.1.2.1.211.1.1.4.4.1.7,GBOND-MIB::gBondPortPmTcaProfileThresh1DayUAS,Unsigned32,read-create,,current,,A desired threshold for the number of Unavailable Seconds (UAS) within any given 1-day performance data collection interval. If the number of UASs in a particular 1-day collection interval reaches or exceeds this value, a gBondPmTca1DayUASCrossing notification MAY be generated if enabled by gBondPortConfPmTcaEnable. At most one notification can be sent per interval. Setting this attribute to zero (default) effectively disables the gBondPmTca1DayUASCrossing notification. This object maps to the TR-159 attribute aGroupPerfThreshold1DayUAS.
.1.3.6.1.2.1.211.1.1.4.4.1.8,GBOND-MIB::gBondPortPmTcaProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object controls the creation, modification, or deletion of the associated entry in the gBondPortPmTcaProfileTable per the semantics of RowStatus. If an 'active' entry is referenced via gBondPortConfPmTcaConfProfile instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set to 'active' again.
.1.3.6.1.2.1.211.1.2,GBOND-MIB::gBondBce,,,,,,
.1.3.6.1.2.1.211.1.2.1,GBOND-MIB::gBondBceConfTable,,not-accessible,,current,,Table for configuration of G.Bond common aspects for the Bonding Channel Entity (BCE) ports (modems/channels). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.211.1.2.1.1,GBOND-MIB::gBondBceConfEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond BCE Configuration table. Each entry represents common aspects of a G.Bond BCE port indexed by the ifIndex. Note that a G.Bond BCE port can be stacked below a single GBS port, also indexed by the ifIndex, possibly together with other BCE ports if bonding is enabled.
.1.3.6.1.2.1.211.1.2.1.1.1,GBOND-MIB::gBondBceConfRemoteDiscoveryCode,OCTET,read-write,,current,,A remote discovery code of the BCE port at the CO. A 6-octet-long discovery code of the peer GBS connected via the BCE. Reading this object results in a Discovery Get operation. Setting this object to all zeroes results in a Discovery Clear_if_Same operation (the value of gBondPortConfDiscoveryCode at the peer GBS SHALL be the same as gBondPortConfDiscoveryCode of the local GBS associated with the BCE for the operation to succeed). Writing a non-zero value to this object results in a Discovery Set_if_Clear operation. A zero-length octet string SHALL be returned on an attempt to read this object when bonding is not enabled. This object is irrelevant in BCE-R port subtypes (CPE side): in this case, a zero-length octet string SHALL be returned on an attempt to read this object. An attempt to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue). Discovery MUST be performed when the link is 'down'. Attempts to change this object MUST be rejected (in the case of SNMP, with the error inconsistentValue), If the link is 'up' or initializing. This object maps to the TR-159 attribute aLineRemoteDiscoveryCode.
.1.3.6.1.2.1.211.2,GBOND-MIB::gBondConformance,,,,,,
.1.3.6.1.2.1.211.2.1,GBOND-MIB::gBondGroups,,,,,,
.1.3.6.1.2.1.211.2.1.1,GBOND-MIB::gBondBasicGroup,,,,,,A collection of objects representing management information common to all types of G.Bond ports.
.1.3.6.1.2.1.211.2.1.2,GBOND-MIB::gBondDiscoveryGroup,,,,,,A collection of objects supporting OPTIONAL G.Bond discovery in G.Bond ports.
.1.3.6.1.2.1.211.2.1.3,GBOND-MIB::gBondMultiSchemeGroup,,,,,,A collection of objects providing OPTIONAL management information for G.Bond ports supporting multiple bonding schemes.
.1.3.6.1.2.1.211.2.1.4,GBOND-MIB::gBondTcaConfGroup,,,,,,A collection of objects required for configuration of alarm thresholds and notifications in G.Bond ports.
.1.3.6.1.2.1.211.2.1.5,GBOND-MIB::gBondTcaNotificationGroup,,,,,,This group supports notifications of significant conditions (non-PM threshold crossing alerts) associated with G.Bond ports.
.1.3.6.1.2.1.211.2.1.6,GBOND-MIB::gBondPmCurGroup,,,,,,A collection of objects supporting OPTIONAL current Performance Monitoring information for G.Bond ports.
.1.3.6.1.2.1.211.2.1.7,GBOND-MIB::gBondPm15MinGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond ports, during previous 15-minute intervals.
.1.3.6.1.2.1.211.2.1.8,GBOND-MIB::gBondPm1DayGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond ports, during previous 1-day intervals.
.1.3.6.1.2.1.211.2.1.9,GBOND-MIB::gBondPmTcaConfGroup,,,,,,A collection of objects required for configuration of Performance Monitoring Threshold Crossing Alert notifications in G.Bond ports.
.1.3.6.1.2.1.211.2.1.10,GBOND-MIB::gBondPmTcaNotificationGroup,,,,,,This group supports notifications of Performance Monitoring Threshold Crossing Alerts associated with G.Bond ports.
.1.3.6.1.2.1.211.2.2,GBOND-MIB::gBondCompliances,,,,,,
.1.3.6.1.2.1.211.2.2.1,GBOND-MIB::gBondCompliance,,,,,,The compliance statement for G.Bond interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 Compliance with the following external compliance statements is OPTIONAL for implementations supporting bonding with flexible cross-connect between the GBS and BCE ports: MIB Module Compliance Statement ---------- -------------------- IF-INVERTED-STACK-MIB ifInvCompliance IF-CAP-STACK-MIB ifCapStackCompliance
.1.3.6.1.2.1.212,PSAMP-MIB::psampMIB,,,,,,The PSAMP MIB defines managed objects for packet sampling and filtering. These objects provide information about managed nodes supporting packet sampling, including packet sampling capabilities, configuration, and statistics. The PSAMP MIB module registers additional top-level OIDs for the parameter subtrees of its Selector functions in the IPFIX-SELECTOR-MIB Function sub-registry according to the procedures defined in RFC 6615. Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 6727; see the RFC itself for full legal notices.
.1.3.6.1.2.1.212.1,PSAMP-MIB::psampObjects,,,,,,
.1.3.6.1.2.1.212.2,PSAMP-MIB::psampConformance,,,,,,
.1.3.6.1.2.1.212.2.1,PSAMP-MIB::psampCompliances,,,,,,
.1.3.6.1.2.1.212.2.1.1,PSAMP-MIB::psampCompliance,,,,,,The implementation of all objects is optional and depends on the implementation of the corresponding functionality in the equipment.
.1.3.6.1.2.1.212.2.2,PSAMP-MIB::psampGroups,,,,,,
.1.3.6.1.2.1.212.2.2.1,PSAMP-MIB::psampGroupSampCountBased,,,,,,These objects are needed if count based sampling is implemented.
.1.3.6.1.2.1.212.2.2.2,PSAMP-MIB::psampGroupSampTimeBased,,,,,,These objects are needed if time based sampling is implemented.
.1.3.6.1.2.1.212.2.2.3,PSAMP-MIB::psampGroupSampRandOutOfN,,,,,,These objects are needed if random n-out-of-N sampling is implemented.
.1.3.6.1.2.1.212.2.2.4,PSAMP-MIB::psampGroupSampUniProb,,,,,,These objects are needed if uniform probabilistic sampling is implemented.
.1.3.6.1.2.1.212.2.2.5,PSAMP-MIB::psampGroupFiltPropMatch,,,,,,These objects are needed if property match filtering is implemented.
.1.3.6.1.2.1.212.2.2.6,PSAMP-MIB::psampGroupFiltHash,,,,,,These objects are needed if hash filtering is implemented.
.1.3.6.1.2.1.213,NHDP-MIB::nhdpMIB,,,,,,This NHDP-MIB module is applicable to routers implementing the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) defined in RFC 6130. Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.213.0,NHDP-MIB::nhdpNotifications,,,,,,
.1.3.6.1.2.1.213.0.0,NHDP-MIB::nhdpNotificationsObjects,,,,,,
.1.3.6.1.2.1.213.0.0.1,NHDP-MIB::nhdpNbrStateChange,,,,,,nhdpNbrStateChange is a notification sent when more than nhdpNbrStateChangeThreshold neighbors change their status (i.e., 'down(0)', 'asymmetric(1)', or 'symmetric(2)') within a time window of nhdpNbrStateChangeWindow.
.1.3.6.1.2.1.213.0.0.2,NHDP-MIB::nhdp2HopNbrStateChange,,,,,,nhdp2HopNbrStateChange is a notification sent when more than nhdp2HopNbrStateChangeThreshold 2-hop neighbors change their nhdp2HopNbrState within a time window of nhdp2HopNbrStateChangeWindow.
.1.3.6.1.2.1.213.0.0.3,NHDP-MIB::nhdpIfStateChange,,,,,,nhdpIfStateChange is a notification sent when nhdpIfStatus has changed on this interface.
.1.3.6.1.2.1.213.0.1,NHDP-MIB::nhdpNotificationsControl,,,,,,
.1.3.6.1.2.1.213.0.1.1,NHDP-MIB::nhdpNbrStateChangeThreshold,Integer32,read-write,,current,,A threshold value for the nhdpNbrStateChange object. If the number of occurrences exceeds this threshold within the previous nhdpNbrStateChangeWindow, then the nhdpNbrStateChange notification is to be sent. It is recommended that the value of this threshold be set to at least 10 and higher in dense topologies with frequent expected topology changes.
.1.3.6.1.2.1.213.0.1.2,NHDP-MIB::nhdpNbrStateChangeWindow,TimeTicks,read-write,,current,,A time window for the nhdpNbrStateChange object. If the number of occurrences exceeds the nhdpNbrStateChangeThreshold within the previous nhdpNbrStateChangeWindow, then the nhdpNbrStateChange notification is to be sent. It is recommended that the value for this window be set to at least 5 times the nhdpHelloInterval. This object represents the time in hundredths of a second.
.1.3.6.1.2.1.213.0.1.3,NHDP-MIB::nhdp2HopNbrStateChangeThreshold,Integer32,read-write,,current,,A threshold value for the nhdp2HopNbrStateChange object. If the number of occurrences exceeds this threshold within the previous nhdp2HopNbrStateChangeWindow, then the nhdp2HopNbrStateChange notification is to be sent. It is recommended that the value of this threshold be set to at least 10 and higher when topologies are expected to be highly dynamic.
.1.3.6.1.2.1.213.0.1.4,NHDP-MIB::nhdp2HopNbrStateChangeWindow,TimeTicks,read-write,,current,,A time window for the nhdp2HopNbrStateChange object. If the number of occurrences exceeds the nhdp2HopNbrStateChangeThreshold within the previous nhdp2HopNbrStateChangeWindow, then the nhdp2HopNbrStateChange notification is to be sent. It is recommended that the value for this window be set to at least 5 times nhdpHelloInterval. This object represents the time in hundredths of a second.
.1.3.6.1.2.1.213.0.2,NHDP-MIB::nhdpNotificationsStates,,,,,,
.1.3.6.1.2.1.213.0.2.1,NHDP-MIB::nhdpNbrState,INTEGER,read-only,,current,down(0):asymmetric(1):symmetric(2),NHDP neighbor states. In NHDP, it is not necessary to remove Protocol Tuples from Protocol Sets at the exact time indicated, only to behave as if the Protocol Tuples were removed at that time. This case is indicated here as 'down(0)', all other cases being indicated as 'asymmetric(1)' or 'symmetric(2)'. If 'down(0)', the direct neighbor is also added to the nhdpNibLostNeighborSetTable.
.1.3.6.1.2.1.213.0.2.2,NHDP-MIB::nhdp2HopNbrState,INTEGER,read-only,,current,down(0):up(1):notconsidered(2),NHDP 2-hop neighbor states. In NHDP, it is not necessary to remove Protocol Tuples from Protocol Sets at the exact time indicated, only to behave as if the Protocol Tuples were removed at that time. This case is indicated here as 'down(0)'; otherwise, it is either 'up(1)', if N2_lost for the 2-Hop Tuple is equal to false, or 'notconsidered(2)' otherwise.
.1.3.6.1.2.1.213.1,NHDP-MIB::nhdpObjects,,,,,,
.1.3.6.1.2.1.213.1.1,NHDP-MIB::nhdpConfigurationObjGrp,,,,,,
.1.3.6.1.2.1.213.1.1.1,NHDP-MIB::nhdpInterfaceTable,,not-accessible,,current,,The nhdpInterfaceTable describes the configuration of the interfaces of this router that are intended to use MANET control protocols. As such, this table 'sparse augments' the ifTable specifically when NHDP is to be configured to operate over this interface. The interface is identified by the ifIndex from the Interfaces Group defined in the Interfaces Group MIB module. A conceptual row in this table exists if and only if the row has been administratively created or there is an interface on the managed device that supports and runs NHDP. A row can be administratively created by setting rowStatus to 'createAndGo' or 'createAndWait'. During the row creation, objects having associated DEFVAL clauses are automatically defined by the agent if not explicitly administratively defined. For each entry in the nhdpInterfaceTable, there is a corresponding entry in the Interface Table where nhdpIfIndex and ifIndex are equal. If that corresponding entry in the Interface Table is deleted, then the entry in the nhdpInterfaceTable is automatically deleted, NHDP is disabled on this interface, and all configuration and state information related to this interface is to be removed from memory.
.1.3.6.1.2.1.213.1.1.1.1,NHDP-MIB::nhdpInterfaceEntry,,not-accessible,nhdpIfIndex,current,,The nhdpInterfaceEntry describes one NHDP local interface configuration as indexed by its ifIndex as defined in the Standard MIB II Interface Table (RFC 2863). The objects in this table are persistent, and when written, the device SHOULD save the change to nonvolatile storage. For further information on the storage behavior for these objects, refer to the description for the nhdpIfRowStatus object.
.1.3.6.1.2.1.213.1.1.1.1.1,NHDP-MIB::nhdpIfIndex,Integer32,not-accessible,,current,,This value MUST correspond to an ifIndex referring to a valid entry in the Interfaces Table.
.1.3.6.1.2.1.213.1.1.1.1.2,NHDP-MIB::nhdpIfName,OCTET,read-only,,current,,The textual name of the interface. The value of this object SHOULD be the name of the interface as assigned by the local device. This can be a text-name, such as 'le0' or a simple port number, such as '1', depending on the interface-naming syntax of the device. If there is no local name or this object is otherwise not applicable, then this object contains a zero-length string.
.1.3.6.1.2.1.213.1.1.1.1.3,NHDP-MIB::nhdpIfStatus,INTEGER,read-create,,current,true(1):false(2),nhdpIfStatus indicates whether this interface is currently running NHDP. A value of 'true(1)' indicates that NHDP is running on this interface. A value of 'false(2)' indicates that NHDP is not currently running on this interface. This corresponds to the I_manet parameter in the Local Interface Set of NHDP.
.1.3.6.1.2.1.213.1.1.1.1.4,NHDP-MIB::nhdpHelloInterval,Unsigned32,read-create,,current,,nhdpHelloInterval corresponds to HELLO_INTERVAL of NHDP and represents the maximum time between the transmission of two successive HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o nhdpHelloInterval > 0 o nhdpHelloInterval >= nhdpHelloMinInterval
.1.3.6.1.2.1.213.1.1.1.1.5,NHDP-MIB::nhdpHelloMinInterval,Unsigned32,read-create,,current,,nhdpHelloMinInterval corresponds to HELLO_MIN_INTERVAL of NHDP and represents the minimum interval between transmission of two successive HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o nhdpHelloMinInterval <= nhdpHelloInterval
.1.3.6.1.2.1.213.1.1.1.1.6,NHDP-MIB::nhdpRefreshInterval,Unsigned32,read-create,,current,,nhdpRefreshInterval corresponds to REFRESH_INTERVAL of NHDP and represents the maximum interval between advertisements of each 1-hop neighbor network address and its status. Each advertisement is in a HELLO message on this MANET interface. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o nhdpRefreshInterval >= nhdpHelloInterval
.1.3.6.1.2.1.213.1.1.1.1.7,NHDP-MIB::nhdpLHoldTime,Unsigned32,read-create,,current,,nhdpLHoldTime corresponds to L_HOLD_TIME of NHDP and represents the period of advertisement, on this MANET interface, of former 1-hop neighbor network addresses as lost in HELLO messages, allowing recipients of these HELLO messages to accelerate removal of this information from their Link Sets. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that it should be assigned a value significantly greater than the refresh interval held by nhdpRefreshInterval.
.1.3.6.1.2.1.213.1.1.1.1.8,NHDP-MIB::nhdpHHoldTime,Unsigned32,read-create,,current,,nhdpHHoldTime corresponds to H_HOLD_TIME of NHDP and is used as the value in the VALIDITY_TIME Message TLV included in all HELLO messages on this MANET interface. It is then used by each router receiving such a HELLO message to indicate the validity of the information taken from that HELLO message and recorded in the receiving router's Information Bases. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that it should be assigned a value significantly greater than the refresh interval held by nhdpRefreshInterval and must be representable as described in RFC 5497.
.1.3.6.1.2.1.213.1.1.1.1.9,NHDP-MIB::nhdpHystAcceptQuality,OCTET,read-create,,current,,nhdpHystAcceptQuality corresponds to HYST_ACCEPT of NHDP and represents the link quality threshold at or above which a link becomes usable, if it was not already so. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o 0 <= nhdpHystRejectQuality <= nhdpHystAcceptQuality <= 1.0 The default value for this object is 1.0. According to RFC 6340: Since these textual conventions are defined in terms of the OCTET STRING type, the SMI's mechanisms for formally setting range constraints are not available. MIB designers using these textual conventions will need to use DESCRIPTION clauses to spell out any applicable range constraints beyond those implied by the underlying IEEE types. Therefore, this object does not have a DEFVAL clause.
.1.3.6.1.2.1.213.1.1.1.1.10,NHDP-MIB::nhdpHystRejectQuality,OCTET,read-create,,current,,nhdpHystRejectQuality corresponds to HYST_REJECT of NHDP and represents the link quality threshold below which a link becomes unusable, if it was not already so. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o 0 <= nhdpHystRejectQuality <= nhdpHystAcceptQuality <= 1.0 The default value for this object is 0.0. According to RFC 6340: Since these textual conventions are defined in terms of the OCTET STRING type, the SMI's mechanisms for formally setting range constraints are not available. MIB designers using these textual conventions will need to use DESCRIPTION clauses to spell out any applicable range constraints beyond those implied by the underlying IEEE types. Therefore, this object does not have a DEFVAL clause.
.1.3.6.1.2.1.213.1.1.1.1.11,NHDP-MIB::nhdpInitialQuality,OCTET,read-create,,current,,nhdpInitialQuality corresponds to INITIAL_QUALITY of NHDP and represents the initial quality of a newly identified link. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o 0 <= nhdpInitialQuality <= 1.0 The default value for this object is 1.0. According to RFC 6340: Since these textual conventions are defined in terms of the OCTET STRING type, the SMI's mechanisms for formally setting range constraints are not available. MIB designers using these textual conventions will need to use DESCRIPTION clauses to spell out any applicable range constraints beyond those implied by the underlying IEEE types. Therefore, this object does not have a DEFVAL clause.
.1.3.6.1.2.1.213.1.1.1.1.12,NHDP-MIB::nhdpInitialPending,INTEGER,read-create,,current,true(1):false(2),nhdpInitialPending corresponds to INITIAL_PENDING of NHDP. If the value of this object is 'true(1)', then a newly identified link is considered pending and is not usable until the link quality has reached or exceeded the nhdpHystAcceptQuality threshold. Guidance for setting this object may be found in Section 5 of the NHDP specification (RFC 6130), which indicates that: o If nhdpInitialQuality >= nhdpHystAcceptQuality, then nhdpInitialPending := false(2). o If nhdpInitialQuality < nhdpHystRejectQuality, then nhdpInitialPending := true(1).
.1.3.6.1.2.1.213.1.1.1.1.13,NHDP-MIB::nhdpHpMaxJitter,Unsigned32,read-create,,current,,nhdpHpMaxJitter corresponds to HP_MAXJITTER of NHDP and represents the value of MAXJITTER used in RFC 5148 for periodically generated HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of RFC 5148, which indicates that: o nhdpHpMaxJitter <= nhdpHelloInterval / 2 o nhdpHpMaxJitter should not be greater than nhdpHelloInterval / 4 o If nhdpMinHelloInterval > 0, then nhdpHpMaxJitter <= nhdpHelloMinInterval; and nhdpHpMaxJitter should not be greater than nhdpHelloMinInterval / 2
.1.3.6.1.2.1.213.1.1.1.1.14,NHDP-MIB::nhdpHtMaxJitter,Unsigned32,read-create,,current,,nhdpHtMaxJitter corresponds to HT_MAXJITTER of NHDP and represents the value of MAXJITTER used in RFC 5148 for externally triggered HELLO messages on this MANET interface. Guidance for setting this object may be found in Section 5 of RFC 5148, which indicates that: o nhdpHtMaxJitter <= nhdpHelloInterval / 2 o nhdpHtMaxJitter should not be greater than nhdpHelloInterval / 4 o If nhdpMinHelloInterval > 0, then nhdpHtMaxJitter <= nhdpHelloMinInterval; and nhdpHtMaxJitter should not be greater than nhdpHelloMinInterval / 2
.1.3.6.1.2.1.213.1.1.1.1.15,NHDP-MIB::nhdpIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified. An entry may not exist in the 'active(1)' state unless all objects in the entry have a defined appropriate value. For objects with DEFVAL clauses, the management station does not need to specify the value of this object in order for the row to transit to the 'active(1)' state; the default value for this object is used. For objects that do not have DEFVAL clauses, the value of this object prior to this row transitioning to the 'active(1)' state MUST be administratively specified. When this object transitions to 'active(1)', all objects in this row SHOULD be written to nonvolatile (stable) storage. Read-create objects in this row MAY be modified. When an object in a row with nhdpIfRowStatus of 'active(1)' is changed, then the updated value MUST be reflected in NHDP, and this new object value MUST be written to nonvolatile storage. If the value of this object is not equal to 'active(1)', all associated entries in the nhdpLibLocalIfSetTable, nhdpInterfaceStateTable, nhdpIibLinkSetTable, and nhdpInterfacePerfTable MUST be deleted.
.1.3.6.1.2.1.213.1.1.2,NHDP-MIB::nhdpNHoldTime,Unsigned32,read-write,,current,,nhdpNHoldTime corresponds to N_HOLD_TIME of NHDP and is used as the period during which former 1-hop neighbor network addresses are advertised as lost in HELLO messages, allowing recipients of these HELLO messages to accelerate removal of this information from their 2-Hop Sets. This object is persistent, and when written, the entity SHOULD save the change to nonvolatile storage.
.1.3.6.1.2.1.213.1.1.3,NHDP-MIB::nhdpIHoldTime,Unsigned32,read-write,,current,,nhdpIHoldTime corresponds to I_HOLD_TIME of NHDP and represents the period for which a recently used local interface network address is recorded. This object is persistent, and when written, the entity SHOULD save the change to nonvolatile storage.
.1.3.6.1.2.1.213.1.1.4,NHDP-MIB::nhdpLibLocalIfSetTable,,not-accessible,,current,,A router's Local Interface Set records all network addresses that are defined as local MANET interface network addresses. As such, this table 'sparse augments' the nhdpInterfaceTable when network addresses are being defined for the interfaces existing within the nhdpInterfaceTable. The local interface is defined by the nhdpIfIndex. The Local Interface Set consists of Local Interface Address Tuples per MANET interface and their prefix lengths (in order to determine the network addresses related to the interface). A conceptual row in this table exists if and only if one has been administratively created. This can be done by setting rowStatus to 'createAndGo' or 'createAndWait'. Further guidance on the addition or removal of local addresses and network addresses is found in Section 9 of RFC 6130.
.1.3.6.1.2.1.213.1.1.4.1,NHDP-MIB::nhdpLibLocalIfSetEntry,,not-accessible,nhdpLibLocalIfSetIndex,current,,A router's Local Interface Set consists of Local Interface Tuples for each network interface. The objects in this table are persistent, and when written, the device SHOULD save the change to nonvolatile storage. For further information on the storage behavior for these objects, refer to the description for the nhdpLibLocalIfSetRowStatus object.
.1.3.6.1.2.1.213.1.1.4.1.1,NHDP-MIB::nhdpLibLocalIfSetIndex,Integer32,not-accessible,,current,,The index for this table. Necessary because multiple addresses may be associated with a given nhdpIfIndex.
.1.3.6.1.2.1.213.1.1.4.1.2,NHDP-MIB::nhdpLibLocalIfSetIfIndex,Integer32,read-only,,current,,Specifies the local nhdpIfIndex for which this IP address was added.
.1.3.6.1.2.1.213.1.1.4.1.3,NHDP-MIB::nhdpLibLocalIfSetIpAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the nhdpLibLocalIfSetIpAddr in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.213.1.1.4.1.4,NHDP-MIB::nhdpLibLocalIfSetIpAddr,OCTET,read-create,,current,,nhdpLibLocalIfSetIpAddr is an address of an interface of this router. This object is interpreted according to the setting of nhdpLibLocalIfSetIpAddrType.
.1.3.6.1.2.1.213.1.1.4.1.5,NHDP-MIB::nhdpLibLocalIfSetIpAddrPrefixLen,Unsigned32,read-create,,current,,Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpLibLocalIfSetIpAddr to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.
.1.3.6.1.2.1.213.1.1.4.1.6,NHDP-MIB::nhdpLibLocalIfSetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of the table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified. An entry may not exist in the 'active(1)' state unless all read-create objects in the entry have a defined appropriate value. As no objects in this table have DEFVAL clauses, the management station MUST specify the values of all read-create objects prior to this row transitioning to the 'active(1)' state. When this object transitions to 'active(1)', all objects in this row SHOULD be written to nonvolatile (stable) storage. Read-create objects in this row MAY be modified. When an object in a row with nhdpIfRowStatus of 'active(1)' is changed, then the updated value MUST be reflected in NHDP, and this new object value MUST be written to nonvolatile storage.
.1.3.6.1.2.1.213.1.1.5,NHDP-MIB::nhdpLibRemovedIfAddrSetTable,,not-accessible,,current,,A router's Removed Interface Address Set records network addresses that were recently used as local interface network addresses. If a router's interface network addresses are immutable, then the Removed Interface Address Set is always empty and may be omitted. It consists of Removed Interface Address Tuples, one per network address.
.1.3.6.1.2.1.213.1.1.5.1,NHDP-MIB::nhdpLibRemovedIfAddrSetEntry,,not-accessible,nhdpLibRemovedIfAddrSetIndex,current,,A router's Removed Interface Address Set consists of Removed Interface Address Tuples, one per network address: (IR_local_iface_addr, IR_time) The association between these addresses and the router's Interface is found in RFC 4293 (ipAddressTable)
.1.3.6.1.2.1.213.1.1.5.1.1,NHDP-MIB::nhdpLibRemovedIfAddrSetIndex,Integer32,not-accessible,,current,,The index for this table. Necessary because multiple addresses may be associated with a given nhdpIfIndex.
.1.3.6.1.2.1.213.1.1.5.1.2,NHDP-MIB::nhdpLibRemovedIfAddrSetIpAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the nhdpLibRemovedIfAddrSetIpAddr in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.213.1.1.5.1.3,NHDP-MIB::nhdpLibRemovedIfAddrSetIpAddr,OCTET,read-only,,current,,nhdpLibRemovedIfAddrSetIpAddr is a recently used address of an interface of this router.
.1.3.6.1.2.1.213.1.1.5.1.4,NHDP-MIB::nhdpLibRemovedIfAddrSetIpAddrPrefixLen,Unsigned32,read-only,,current,,Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpLibRemovedIfAddrSetIpAddr to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.
.1.3.6.1.2.1.213.1.1.5.1.5,NHDP-MIB::nhdpLibRemovedIfAddrSetIfIndex,Integer32,read-only,,current,,Specifies the local IfIndex from which this IP address was recently removed.
.1.3.6.1.2.1.213.1.1.5.1.6,NHDP-MIB::nhdpLibRemovedIfAddrSetIRTime,TimeTicks,read-only,,current,,nhdpLibRemovedIfAddrSetIRTime specifies the value of sysUpTime when this entry should expire and be removed from the nhdpLibRemovedIfAddrSetTable.
.1.3.6.1.2.1.213.1.2,NHDP-MIB::nhdpStateObjGrp,,,,,,
.1.3.6.1.2.1.213.1.2.1,NHDP-MIB::nhdpUpTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time the current NHDP process was initialized.
.1.3.6.1.2.1.213.1.2.2,NHDP-MIB::nhdpInterfaceStateTable,,not-accessible,,current,,nhdpInterfaceStateTable lists state information related to specific interfaces of this router. The value of nhdpIfIndex is an ifIndex from the Interfaces Group defined in the Interfaces Group MIB. The objects in this table are persistent, and when written, the entity SHOULD save the change to nonvolatile storage.
.1.3.6.1.2.1.213.1.2.2.1,NHDP-MIB::nhdpInterfaceStateEntry,,not-accessible,nhdpIfIndex,current,,nhdpInterfaceStateEntry describes one NHDP local interface state as indexed by its nhdpIfIndex.
.1.3.6.1.2.1.213.1.2.2.1.1,NHDP-MIB::nhdpIfStateUpTime,TimeTicks,read-only,,current,,The value of the sysUpTime when NHDP was last initialized on this MANET interface.
.1.3.6.1.2.1.213.1.2.3,NHDP-MIB::nhdpDiscIfSetTable,,not-accessible,,current,,A router's set of discovered interfaces on neighboring routers.
.1.3.6.1.2.1.213.1.2.3.1,NHDP-MIB::nhdpDiscIfSetEntry,,not-accessible,nhdpDiscIfSetIndex,current,,The entries include the nhdpDiscRouterIndex of the discovered router, the nhdpDiscIfIndex of the discovered interface, and the current set of addresses associated with this neighbor interface. The nhdpDiscIfIndex uniquely identifies the remote interface address sets through this table. It does not need to be unique across the MANET but MUST be locally unique within this router.
.1.3.6.1.2.1.213.1.2.3.1.1,NHDP-MIB::nhdpDiscIfSetIndex,Integer32,not-accessible,,current,,The index for this table. Necessary because multiple addresses may be associated with a given nhdpDiscIfIndex.
.1.3.6.1.2.1.213.1.2.3.1.2,NHDP-MIB::nhdpDiscIfIndex,Unsigned32,read-only,,current,,The NHDP interface index (locally created) of a neighbor's interface. Used for cross- indexing into other NHDP tables and other MIB modules.
.1.3.6.1.2.1.213.1.2.3.1.3,NHDP-MIB::nhdpDiscRouterIndex,Unsigned32,read-only,,current,,The NHDP neighbor index (locally created) of a neighboring router. Used for cross- indexing into other NHDP tables and other MIB modules.
.1.3.6.1.2.1.213.1.2.3.1.4,NHDP-MIB::nhdpDiscIfSetIpAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the nhdpDiscIfSetIpAddr in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.213.1.2.3.1.5,NHDP-MIB::nhdpDiscIfSetIpAddr,OCTET,read-only,,current,,The nhdpDiscIfSetIpAddr is a recently used address of a neighbor of this router.
.1.3.6.1.2.1.213.1.2.3.1.6,NHDP-MIB::nhdpDiscIfSetIpAddrPrefixLen,Unsigned32,read-only,,current,,Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpDiscIfSetIpAddr to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.
.1.3.6.1.2.1.213.1.2.4,NHDP-MIB::nhdpIibLinkSetTable,,not-accessible,,current,,A Link Set of an interface records all links from other routers that are, or recently were, 1-hop neighbors.
.1.3.6.1.2.1.213.1.2.4.1,NHDP-MIB::nhdpIibLinkSetEntry,,not-accessible,nhdpIfIndex:nhdpDiscIfIndex,current,,A Link Set consists of Link Tuples, each representing a single link indexed by the local and remote interface pair: (L_neighbor_iface_addr_list, L_HEARD_time, L_SYM_time, L_quality, L_pending, L_lost, L_time). The local interface is indexed via the nhdpIfIndex. The 1-hop interface is indexed via the nhdpDiscIfIndex. There SHOULD be an entry in this table for each local interface and associated 1-hop neighbor reachable on this local interface. Note that L_quality is not included in the entries below, because updates may be required too frequently.
.1.3.6.1.2.1.213.1.2.4.1.1,NHDP-MIB::nhdpIibLinkSetLHeardTime,TimeTicks,read-only,,current,,nhdpIibLinkSetLHeardTime corresponds to L_HEARD_time of NHDP and represents the time up to which the MANET interface of the 1-hop neighbor would be considered heard if not considering link quality.
.1.3.6.1.2.1.213.1.2.4.1.2,NHDP-MIB::nhdpIibLinkSetLSymTime,TimeTicks,read-only,,current,,nhdpIibLinkSetLSymTime corresponds to L_SYM_time of NHDP and represents the time up to which the link to the 1-hop neighbor would be considered symmetric if not considering link quality.
.1.3.6.1.2.1.213.1.2.4.1.3,NHDP-MIB::nhdpIibLinkSetLPending,INTEGER,read-only,,current,true(1):false(2),nhdpIibLinkSetLPending corresponds to L_pending of NHDP and is a boolean flag, describing if a link is considered pending (i.e., a candidate, but not yet established, link).
.1.3.6.1.2.1.213.1.2.4.1.4,NHDP-MIB::nhdpIibLinkSetLLost,INTEGER,read-only,,current,true(1):false(2),nhdpIibLinkSetLLost corresponds to L_lost of NHDP and is a boolean flag, describing if a link is considered lost due to low link quality.
.1.3.6.1.2.1.213.1.2.4.1.5,NHDP-MIB::nhdpIibLinkSetLTime,TimeTicks,read-only,,current,,nhdpIibLinkSetLTime specifies the value of sysUpTime when this entry should expire and be removed from the nhdpIibLinkSetTable.
.1.3.6.1.2.1.213.1.2.5,NHDP-MIB::nhdpIib2HopSetTable,,not-accessible,,current,,A 2-Hop Set of an interface records network addresses of symmetric 2-hop neighbors and the symmetric links to symmetric 1-hop neighbors through which these symmetric 2-hop neighbors can be reached. It consists of 2-Hop Tuples.
.1.3.6.1.2.1.213.1.2.5.1,NHDP-MIB::nhdpIib2HopSetEntry,,not-accessible,nhdpIfIndex:nhdpDiscIfIndex:nhdpIib2HopSetIpAddressType:nhdpIib2HopSetIpAddress,current,,nhdpIib2HopSetTable consists of 2-Hop Tuples, each representing a single network address of a symmetric 2-hop neighbor and a single MANET interface of a symmetric 1-hop neighbor. (N2_neighbor_iface_addr_list, N2_2hop_addr, N2_lost, N2_time). The entries include: - the 2-hop neighbor addresses ('N2_neighbor_iface_addr_list'), which act as the table index, - the associated symmetric 1-hop neighbor address set ('N2_2hop_addr'), designated through nhdpDiscIfIndex, - a flag indicating if the 1-hop neighbor through which this 2-hop neighbor is reachable ('N2_lost') is considered lost due to link quality, or not, - and the expiration time ('N2_time'). The nhdpIfIndex in the INDEX is the interface index of the local interface through which these 2-hop addresses are accessible. The nhdpDiscIfIndex in the INDEX represents the 1-hop neighbor interface through which these 2-hop neighbor addresses are reachable.
.1.3.6.1.2.1.213.1.2.5.1.1,NHDP-MIB::nhdpIib2HopSetIpAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the nhdpIib2HopSetIpAddress in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.213.1.2.5.1.2,NHDP-MIB::nhdpIib2HopSetIpAddress,OCTET,not-accessible,,current,,nhdpIib2HopSetIpAddr corresponds to N2_2hop_addr of NHDP and is a network address of a symmetric 2-hop neighbor that has a symmetric link (using any MANET interface) to the indicated symmetric 1-hop neighbor.
.1.3.6.1.2.1.213.1.2.5.1.3,NHDP-MIB::nhdpIib2HopSetIpAddrPrefixLen,Unsigned32,read-only,,current,,Indicates the number of leading one bits that form the mask. The mask is logically ANDed to the nhdpIib2HopSetIpAddress to determine the address prefix. A row match is true if the address used as an index falls within the network address range defined by the address prefix.
.1.3.6.1.2.1.213.1.2.5.1.4,NHDP-MIB::nhdpIib2HopSet1HopIfIndex,Unsigned32,read-only,,current,,nhdpIib2HopSet1HopIfIndex is nhdpDiscIfIndex of the 1-hop neighbor that communicated the ipAddress of the 2-hop neighbor in this row entry.
.1.3.6.1.2.1.213.1.2.5.1.5,NHDP-MIB::nhdpIib2HopSetN2Time,TimeTicks,read-only,,current,,nhdpIib2HopSetN2Time specifies the value of sysUpTime when this entry should expire and be removed from the nhdpIib2HopSetTable.
.1.3.6.1.2.1.213.1.2.5.1.6,NHDP-MIB::nhdpIib2HopSetN2Lost,INTEGER,read-only,,current,true(1):false(2),nhdpIib2HopSetN2Lost corresponds to N2_lost of NHDP and is a boolean flag, describing if for a 2-Hop Tuple, the corresponding Link Tuple currently is considered lost due to link quality.
.1.3.6.1.2.1.213.1.2.6,NHDP-MIB::nhdpNibNeighborSetTable,,not-accessible,,current,,A router's Neighbor Set records all network addresses of each 1-hop neighbor.
.1.3.6.1.2.1.213.1.2.6.1,NHDP-MIB::nhdpNibNeighborSetEntry,,not-accessible,nhdpDiscRouterIndex,current,,A router's Neighbor Set consists of Neighbor Tuples, each representing a single 1-hop neighbor: (N_neighbor_addr_list, N_symmetric)
.1.3.6.1.2.1.213.1.2.6.1.1,NHDP-MIB::nhdpNibNeighborSetNSymmetric,INTEGER,read-only,,current,true(1):false(2),nhdpNibNeighborNSymmetric corresponds to N_symmetric of NHDP and is a boolean flag, describing if this is a symmetric 1-hop neighbor.
.1.3.6.1.2.1.213.1.2.7,NHDP-MIB::nhdpNibLostNeighborSetTable,,not-accessible,,current,,A router's Lost Neighbor Set records network addresses of routers that were recently symmetric 1-hop neighbors but are now advertised as lost.
.1.3.6.1.2.1.213.1.2.7.1,NHDP-MIB::nhdpNibLostNeighborSetEntry,,not-accessible,nhdpDiscRouterIndex,current,,A router's Lost Neighbor Set consists of Lost Neighbor Tuples, each representing a single such network address: (NL_neighbor_addr, NL_time)
.1.3.6.1.2.1.213.1.2.7.1.1,NHDP-MIB::nhdpNibLostNeighborSetNLTime,TimeTicks,read-only,,current,,nhdpNibLostNeighborSetNLTime specifies the value of sysUpTime when this entry should expire and be removed from the nhdpNibLostNeighborSetTable.
.1.3.6.1.2.1.213.1.3,NHDP-MIB::nhdpPerformanceObjGrp,,,,,,
.1.3.6.1.2.1.213.1.3.1,NHDP-MIB::nhdpInterfacePerfTable,,not-accessible,,current,,This table summarizes performance objects that are measured per local NHDP interface. nhdpIfPerfCounterDiscontinuityTime indicates the most recent occasion at which any one or more of this interface's counters listed in this table suffered a discontinuity.
.1.3.6.1.2.1.213.1.3.1.1,NHDP-MIB::nhdpInterfacePerfEntry,,not-accessible,nhdpIfIndex,current,,A single entry contains performance counters for a local NHDP interface.
.1.3.6.1.2.1.213.1.3.1.1.1,NHDP-MIB::nhdpIfHelloMessageXmits,Counter32,read-only,,current,,A counter is incremented each time a HELLO message has been transmitted on that interface.
.1.3.6.1.2.1.213.1.3.1.1.2,NHDP-MIB::nhdpIfHelloMessageRecvd,Counter32,read-only,,current,,A counter is incremented each time a HELLO message has been received on that interface.
.1.3.6.1.2.1.213.1.3.1.1.3,NHDP-MIB::nhdpIfHelloMessageXmitAccumulatedSize,Counter64,read-only,,current,,A counter is incremented by the number of octets in a HELLO message each time a HELLO message has been sent.
.1.3.6.1.2.1.213.1.3.1.1.4,NHDP-MIB::nhdpIfHelloMessageRecvdAccumulatedSize,Counter64,read-only,,current,,A counter is incremented by the number of octets in a HELLO message each time a HELLO message has been received.
.1.3.6.1.2.1.213.1.3.1.1.5,NHDP-MIB::nhdpIfHelloMessageTriggeredXmits,Counter32,read-only,,current,,A counter is incremented each time a triggered HELLO message has been sent.
.1.3.6.1.2.1.213.1.3.1.1.6,NHDP-MIB::nhdpIfHelloMessagePeriodicXmits,Counter32,read-only,,current,,A counter is incremented each time a periodic HELLO message has been sent.
.1.3.6.1.2.1.213.1.3.1.1.7,NHDP-MIB::nhdpIfHelloMessageXmitAccumulatedSymmetricNeighborCount,Counter32,read-only,,current,,A counter is incremented by the number of advertised symmetric neighbors in a HELLO each time a HELLO message has been sent.
.1.3.6.1.2.1.213.1.3.1.1.8,NHDP-MIB::nhdpIfHelloMessageXmitAccumulatedHeardNeighborCount,Counter32,read-only,,current,,A counter is incremented by the number of advertised heard neighbors in a HELLO each time a HELLO message has been sent.
.1.3.6.1.2.1.213.1.3.1.1.9,NHDP-MIB::nhdpIfHelloMessageXmitAccumulatedLostNeighborCount,Counter32,read-only,,current,,A counter is incremented by the number of advertised lost neighbors in a HELLO each time a HELLO message has been sent.
.1.3.6.1.2.1.213.1.3.1.1.10,NHDP-MIB::nhdpIfPerfCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this interface's counters suffered a discontinuity. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.213.1.3.2,NHDP-MIB::nhdpDiscIfSetPerfTable,,not-accessible,,current,,A router's set of performance properties for each discovered interface of a neighbor.
.1.3.6.1.2.1.213.1.3.2.1,NHDP-MIB::nhdpDiscIfSetPerfEntry,,not-accessible,nhdpDiscIfIndex,current,,There is an entry for each discovered interface of a neighbor.
.1.3.6.1.2.1.213.1.3.2.1.1,NHDP-MIB::nhdpDiscIfRecvdPackets,Counter32,read-only,,current,,This counter increments each time this router receives a packet from that interface of the neighbor.
.1.3.6.1.2.1.213.1.3.2.1.2,NHDP-MIB::nhdpDiscIfExpectedPackets,Counter32,read-only,,current,,This counter increments by the number of missed packets from this neighbor based on the packet sequence number each time this router receives a packet from that interface of the neighbor.
.1.3.6.1.2.1.213.1.3.3,NHDP-MIB::nhdpNibNeighborSetChanges,Counter32,read-only,,current,,This counter increments each time the Neighbor Set changes. A change occurs whenever a new Neighbor Tuple has been added, a Neighbor Tuple has been removed, or any entry of a Neighbor Tuple has been modified.
.1.3.6.1.2.1.213.1.3.4,NHDP-MIB::nhdpDiscNeighborSetPerfTable,,not-accessible,,current,,A router's set of discovered neighbors and their properties.
.1.3.6.1.2.1.213.1.3.4.1,NHDP-MIB::nhdpDiscNeighborSetPerfEntry,,not-accessible,nhdpDiscRouterIndex,current,,The entries include the nhdpDiscRouterIndex of the discovered router as well as performance objects related to changes of the Neighbor Set.
.1.3.6.1.2.1.213.1.3.4.1.1,NHDP-MIB::nhdpDiscNeighborNibNeighborSetChanges,Counter32,read-only,,current,,This object returns the number of changes to the given Neighbor Tuple.
.1.3.6.1.2.1.213.1.3.4.1.2,NHDP-MIB::nhdpDiscNeighborNibNeighborSetUpTime,TimeTicks,read-only,,current,,This object returns the sysUpTime when a new nhdpNibNeighborSetEntry has been created for a particular nhdpNibNeighborSetRouterIndex.
.1.3.6.1.2.1.213.1.3.4.1.3,NHDP-MIB::nhdpDiscNeighborNibNeighborSetReachableLinkChanges,Counter32,read-only,,current,,This object counts each time the neighbor changes the interface(s) over which it is reachable. A change in the set of Link Tuples corresponding to the appropriate Neighbor Tuple is registered, i.e., a corresponding Link Tuple is added or removed from the set of all corresponding Link Tuples.
.1.3.6.1.2.1.213.1.3.5,NHDP-MIB::nhdpIib2HopSetPerfTable,,not-accessible,,current,,This table contains performance objects per discovered 2-hop neighbor.
.1.3.6.1.2.1.213.1.3.5.1,NHDP-MIB::nhdpIib2HopSetPerfEntry,,not-accessible,nhdpDiscRouterIndex,current,,The entries contain performance objects per discovered 2-hop neighbor.
.1.3.6.1.2.1.213.1.3.5.1.1,NHDP-MIB::nhdpIib2HopSetPerfChanges,Counter32,read-only,,current,,This object counts the changes of the union of all N2_neighbor_iface_addr_list of 2-Hop Tuples with an N2_2hop_addr equal to one of the given 2-hop neighbor's addresses.
.1.3.6.1.2.1.213.1.3.5.1.2,NHDP-MIB::nhdpIib2HopSetPerfUpTime,TimeTicks,read-only,,current,,This object returns the sysUpTime when the 2-Hop Tuple corresponding to the given 2-hop neighbor IP address was registered in the nhdpIib2HopSetTable.
.1.3.6.1.2.1.213.2,NHDP-MIB::nhdpConformance,,,,,,
.1.3.6.1.2.1.213.2.1,NHDP-MIB::nhdpCompliances,,,,,,
.1.3.6.1.2.1.213.2.1.1,NHDP-MIB::nhdpBasicCompliance,,,,,,The basic implementation requirements for managed network entities that implement NHDP.
.1.3.6.1.2.1.213.2.1.2,NHDP-MIB::nhdpFullCompliance,,,,,,The full implementation requirements for managed network entities that implement NHDP. For version-independence, this compliance statement is deprecated in favor of nhdpFullCompliance2.
.1.3.6.1.2.1.213.2.1.3,NHDP-MIB::nhdpFullCompliance2,,,,,,The full implementation requirements for managed network entities that implement NHDP.
.1.3.6.1.2.1.213.2.2,NHDP-MIB::nhdpMIBGroups,,,,,,
.1.3.6.1.2.1.213.2.2.2,NHDP-MIB::nhdpConfigurationGroup,,,,,,Set of NHDP configuration objects implemented in this module.
.1.3.6.1.2.1.213.2.2.3,NHDP-MIB::nhdpStateGroup,,,,,,Set of NHDP state objects implemented in this module. For version-independence, this compliance statement is deprecated in favor of nhdpStateGroup2.
.1.3.6.1.2.1.213.2.2.4,NHDP-MIB::nhdpPerformanceGroup,,,,,,Set of NHDP performance objects implemented in this module.
.1.3.6.1.2.1.213.2.2.5,NHDP-MIB::nhdpNotificationObjectGroup,,,,,,Set of NHDP notification objects implemented in this module.
.1.3.6.1.2.1.213.2.2.6,NHDP-MIB::nhdpNotificationGroup,,,,,,Set of NHDP notifications implemented in this module.
.1.3.6.1.2.1.213.2.2.7,NHDP-MIB::nhdpStateGroup2,,,,,,Set of NHDP state objects implemented in this module.
.1.3.6.1.2.1.214,RBRIDGE-MIB::rbridgeMIB,,,,,,The RBridge MIB module for managing switches that support the TRILL protocol.
.1.3.6.1.2.1.214.0,RBRIDGE-MIB::rbridgeNotifications,,,,,,
.1.3.6.1.2.1.214.0.1,RBRIDGE-MIB::rbridgeBaseNewDrb,,,,,,The rbridgeBaseNewDrb notification indicates that the sending agent has become the new Designated RBridge; the notification is sent by an RBridge soon after its election as the new DRB root, e.g., upon expiration of the Topology Change Timer, immediately subsequent to its election.
.1.3.6.1.2.1.214.0.2,RBRIDGE-MIB::rbridgeBaseTopologyChange,,,,,,The rbridgeBaseTopologyChange notification is sent by an RBridge when any of its configured ports transition to/from the VLAN-x designated forwarder. The notification is not sent if an rbridgeBaseNewDrb notification is sent for the same transition.
.1.3.6.1.2.1.214.1,RBRIDGE-MIB::rbridgeObjects,,,,,,
.1.3.6.1.2.1.214.1.1,RBRIDGE-MIB::rbridgeBase,,,,,,
.1.3.6.1.2.1.214.1.1.1,RBRIDGE-MIB::rbridgeBaseTrillVersion,Unsigned32,read-only,,current,,The maximum TRILL version number that this RBridge supports.
.1.3.6.1.2.1.214.1.1.2,RBRIDGE-MIB::rbridgeBaseNumPorts,Unsigned32,read-only,,current,,The number of ports controlled by this RBridge.
.1.3.6.1.2.1.214.1.1.3,RBRIDGE-MIB::rbridgeBaseForwardDelay,Unsigned32,read-write,,current,,Modified aging time for address entries after an appointed forwarder change. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.4,RBRIDGE-MIB::rbridgeBaseUniMultipathEnable,INTEGER,read-write,,current,true(1):false(2),The enabled status of unicast TRILL multipathing. It is enabled when true. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.5,RBRIDGE-MIB::rbridgeBaseMultiMultipathEnable,INTEGER,read-write,,current,true(1):false(2),The enabled status of multi-destination TRILL multipathing. It is enabled when true. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.6,RBRIDGE-MIB::rbridgeBaseAcceptEncapNonadj,INTEGER,read-write,,current,true(1):false(2),Accept TRILL-encapsulated frames from a neighbor with which this RBridge does not have an IS-IS adjacency, when the value of this object is 'true'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.7,RBRIDGE-MIB::rbridgeBaseNicknameNumber,Unsigned32,read-write,,current,,The number of nicknames this RBridge should acquire. These can be acquired dynamically or configured statically. This value represents the maximum number of entries in rbridgeBaseNicknameTable. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.8,RBRIDGE-MIB::rbridgeBaseNicknameTable,,not-accessible,,current,,A table that contains information about nicknames configured by an operator or learned dynamically by this RBridge.
.1.3.6.1.2.1.214.1.1.8.1,RBRIDGE-MIB::rbridgeBaseNicknameEntry,,not-accessible,rbridgeBaseNicknameName,current,,A list of information for each nickname of the RBridge.
.1.3.6.1.2.1.214.1.1.8.1.1,RBRIDGE-MIB::rbridgeBaseNicknameName,Unsigned32,not-accessible,,current,,Nicknames are 16-bit quantities that act as abbreviations for RBridge's 48-bit IS-IS System ID to achieve a more compact encoding.
.1.3.6.1.2.1.214.1.1.8.1.2,RBRIDGE-MIB::rbridgeBaseNicknamePriority,Unsigned32,read-create,,current,,This RBridge's priority to hold this nickname. When the nickname is configured, the default value of this object is 192. When the nickname is configured, the most significant bit (0x80) must be set and the bottom 7 bits have the default value of 0x40, so 0x80 + 0x40 == 0xC0, which is 192 decimal. Additionally, the bottom 7 bits could be configured to a value other than 0x40. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.8.1.3,RBRIDGE-MIB::rbridgeBaseNicknameDtrPriority,Unsigned32,read-create,,current,,The distribution tree root priority for this nickname. The default value of this object is 32768. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.8.1.4,RBRIDGE-MIB::rbridgeBaseNicknameType,INTEGER,read-only,,current,static(1):dynamic(2),This object indicates the status of the entry. The default value is static(1). static(1) - this entry has been configured and will remain after the next reset of the RBridge. dynamic(2) - this entry has been acquired by the RBridge nickname acquisition protocol.
.1.3.6.1.2.1.214.1.1.8.1.5,RBRIDGE-MIB::rbridgeBaseNicknameRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of the entry.
.1.3.6.1.2.1.214.1.1.9,RBRIDGE-MIB::rbridgeBasePortTable,,not-accessible,,current,,A table that contains generic information about every port that is associated with this RBridge.
.1.3.6.1.2.1.214.1.1.9.1,RBRIDGE-MIB::rbridgeBasePortEntry,,not-accessible,rbridgeBasePort,current,,A list of information for each port of the bridge.
.1.3.6.1.2.1.214.1.1.9.1.1,RBRIDGE-MIB::rbridgeBasePort,Unsigned32,not-accessible,,current,,The port number of the port for which this entry contains RBridge management information.
.1.3.6.1.2.1.214.1.1.9.1.2,RBRIDGE-MIB::rbridgeBasePortIfIndex,Integer32,read-only,,current,,The value of the instance of the ifIndex object, defined in the IF-MIB, for the interface corresponding to this port. The RBridge port sits on top of this interface.
.1.3.6.1.2.1.214.1.1.9.1.3,RBRIDGE-MIB::rbridgeBasePortDisable,INTEGER,read-write,,current,true(1):false(2),Disable port bit. When this bit is set (true), all frames received or to be transmitted are discarded, with the possible exception of some layer 2 control frames that may be generated and transmitted or received and processed locally. Default value is 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.4,RBRIDGE-MIB::rbridgeBasePortTrunkPort,INTEGER,read-write,,current,true(1):false(2),End-station service disable (trunk port) bit. When this bit is set (true), all native frames received on the port and all native frames that would have been sent on the port are discarded. Default value is 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.5,RBRIDGE-MIB::rbridgeBasePortAccessPort,INTEGER,read-write,,current,true(1):false(2),TRILL traffic disable (access port) bit. If this bit is set, the goal is to avoid sending any TRILL frames, except TRILL-Hello frames, on the port, since it is intended only for native end-station traffic. This ensures that the link is not on the shortest path for any destination. Default value is 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.6,RBRIDGE-MIB::rbridgeBasePortP2pHellos,INTEGER,read-write,,current,true(1):false(2),Use point-to-point (P2P) Hellos bit. If this bit is set, Hellos sent on this port are IS-IS P2P Hellos, not the default TRILL-Hellos. In addition, the IS-IS P2P three-way handshake is used on P2P RBridge links. Default value is 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.7,RBRIDGE-MIB::rbridgeBasePortState,INTEGER,read-only,,current,uninhibited(1):portInhibited(2):vlanInhibited(3):disabled(4):broken(5),The port's current state. If the entire port is inhibited, its state is portInhibited(2). If specific VLANs are inhibited, the state is vlanInhibited(3), and rbridgeVlanPortTable will tell which VLANs are inhibited. For ports that are disabled (see rbridgeBasePortDisable), this object will have a value of disabled(4). If the RBridge has detected a port that is malfunctioning, it will place that port into the broken(5) state.
.1.3.6.1.2.1.214.1.1.9.1.8,RBRIDGE-MIB::rbridgeBasePortInhibitionTime,Unsigned32,read-write,,current,,Time in seconds that this RBridge will inhibit forwarding on this port after it observes a spanning tree root bridge change on a link or receives conflicting VLAN forwarder information. The default value is 30. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.9,RBRIDGE-MIB::rbridgeBasePortDisableLearning,INTEGER,read-write,,current,true(1):false(2),Disable learning of MAC addresses seen on this port. To disable learning, the value of this object must be set to 'true'. The default is 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.10,RBRIDGE-MIB::rbridgeBasePortDesiredDesigVlan,Integer32,read-write,,current,,The VLAN that a Designated RBridge (DRB) will specify in its TRILL-Hellos as the VLAN to be used by all RBridges on the link for TRILL frames. This VLAN must be enabled on this port. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.1.9.1.11,RBRIDGE-MIB::rbridgeBasePortDesigVlan,Integer32,read-only,,current,,The VLAN being used on this link for TRILL frames.
.1.3.6.1.2.1.214.1.1.9.1.12,RBRIDGE-MIB::rbridgeBasePortStpRoot,OCTET,read-only,,current,,The bridge identifier of the root of the spanning tree, as learned from a Bridge PDU (BPDU) received on this port. For the Multiple Spanning Tree Protocol (MSTP), this is the root bridge of the Common and Internal Spanning Tree (CIST). If no BPDU has been heard, the value returned is a string of zeros.
.1.3.6.1.2.1.214.1.1.9.1.13,RBRIDGE-MIB::rbridgeBasePortStpRootChanges,Counter32,read-only,,current,,The number of times a change in the root bridge is seen from spanning tree BPDUs received on this port, indicating a change in bridged LAN topology. Each such change may cause the port to be inhibited for a period of time. This counter should be synchronized with ifCounterDiscontinuityTime. Discontinuities in the value of this counter can occur at re-initialization of the management system.
.1.3.6.1.2.1.214.1.1.9.1.14,RBRIDGE-MIB::rbridgeBasePortStpWiringCloset,OCTET,read-write,,current,,The Bridge ID to be used as the spanning tree root in BPDUs sent for the Wiring Closet topology solution described in [RFC6325]. Note that the same value of this object must be set on all RBridge ports participating in this solution. The default value is all 0s. A non-zero value configured into this object indicates that this solution is in use. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.2,RBRIDGE-MIB::rbridgeFdb,,,,,,
.1.3.6.1.2.1.214.1.2.1,RBRIDGE-MIB::rbridgeConfidenceNative,Unsigned32,read-write,,current,,The confidence level associated with MAC addresses learned from native frames. This is applicable to all RBridge ports. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.2.2,RBRIDGE-MIB::rbridgeConfidenceDecap,Unsigned32,read-write,,current,,The confidence level associated with inner MAC addresses learned after decapsulation of a TRILL data frame. This is applicable to all RBridge ports. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.2.3,RBRIDGE-MIB::rbridgeConfidenceStatic,Unsigned32,read-write,,current,,The confidence level associated with MAC addresses that are statically configured. The default value is 255. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.2.4,RBRIDGE-MIB::rbridgeUniFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the device has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.
.1.3.6.1.2.1.214.1.2.4.1,RBRIDGE-MIB::rbridgeUniFdbEntry,,not-accessible,rbridgeFdbId:rbridgeUniFdbAddr,current,,Information about a specific unicast MAC address for which the RBridge has some forwarding and/or filtering information.
.1.3.6.1.2.1.214.1.2.4.1.1,RBRIDGE-MIB::rbridgeFdbId,Unsigned32,not-accessible,,current,,The identity of this Filtering Database.
.1.3.6.1.2.1.214.1.2.4.1.2,RBRIDGE-MIB::rbridgeUniFdbAddr,OCTET,not-accessible,,current,,A unicast MAC address for which the device has forwarding information.
.1.3.6.1.2.1.214.1.2.4.1.3,RBRIDGE-MIB::rbridgeUniFdbPort,Unsigned32,read-only,,current,,Either the value '0', or the RBridge port number of the port on which a frame having a source address equal to the value of the corresponding instance of rbridgeUniFdbAddr has been seen. A value of '0' indicates that the port number has not been learned but that the device does have some information about this MAC address. Implementors are encouraged to assign the port value to this object whenever it is available, even for addresses for which the corresponding value of rbridgeUniFdbStatus is not learned(3).
.1.3.6.1.2.1.214.1.2.4.1.4,RBRIDGE-MIB::rbridgeUniFdbNickname,Unsigned32,read-only,,current,,The RBridge nickname that is placed in the egress nickname field of a TRILL frame sent to this rbridgeFdbAddress in this rbridgeFdbId.
.1.3.6.1.2.1.214.1.2.4.1.5,RBRIDGE-MIB::rbridgeUniFdbConfidence,Unsigned32,read-only,,current,,The confidence level associated with this entry.
.1.3.6.1.2.1.214.1.2.4.1.6,RBRIDGE-MIB::rbridgeUniFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5):esadi(6),The status of this entry. The meanings of the values are: other(1) - none of the following. invalid(2) - this entry is no longer valid (e.g., it was learned but has since aged out) but has not yet been flushed from the table. learned(3) - the information in this entry was learned and is being used. self(4) - the value of the corresponding instance of rbridgeFdbAddress represents one of the device's addresses. The corresponding instance of rbridgeFdbPort indicates which of the device's ports has this address. mgmt(5) - the value of the corresponding instance of rbridgeFdbAddress was configured by management. esadi(6) - the value of the corresponding instance of rbridgeFdbAddress was learned from ESADI.
.1.3.6.1.2.1.214.1.2.5,RBRIDGE-MIB::rbridgeUniFibTable,,not-accessible,,current,,A table that contains information about nicknames known by the RBridge. If Equal-Cost Multipath (ECMP) is implemented, there are as many entries for a nickname as there are ECMP paths available for it.
.1.3.6.1.2.1.214.1.2.5.1,RBRIDGE-MIB::rbridgeUniFibEntry,,not-accessible,rbridgeUniFibNickname:rbridgeUniFibPort:rbridgeUniFibNextHop,current,,A list of information about nicknames known by the RBridge. If ECMP is implemented, there are as many entries as there are ECMP paths available for a given nickname.
.1.3.6.1.2.1.214.1.2.5.1.1,RBRIDGE-MIB::rbridgeUniFibNickname,Unsigned32,not-accessible,,current,,An RBridge nickname for which this RBridge has forwarding information.
.1.3.6.1.2.1.214.1.2.5.1.2,RBRIDGE-MIB::rbridgeUniFibPort,Unsigned32,not-accessible,,current,,The RBridge port number of the port attached to the next-hop RBridge for the path towards the RBridge whose nickname is specified in this entry.
.1.3.6.1.2.1.214.1.2.5.1.3,RBRIDGE-MIB::rbridgeUniFibNextHop,Unsigned32,not-accessible,,current,,The nickname of the next-hop RBridge for the path towards the RBridge whose nickname is specified in this entry.
.1.3.6.1.2.1.214.1.2.5.1.4,RBRIDGE-MIB::rbridgeUniFibHopCount,Unsigned32,read-only,,current,,The hop count from this ingress RBridge to the egress RBridge whose nickname is specified in rbridgeUniFibNickname.
.1.3.6.1.2.1.214.1.2.6,RBRIDGE-MIB::rbridgeMultiFibTable,,not-accessible,,current,,A table that contains information about egress nicknames used for multi-destination frame forwarding by this RBridge.
.1.3.6.1.2.1.214.1.2.6.1,RBRIDGE-MIB::rbridgeMultiFibEntry,,not-accessible,rbridgeMultiFibNickname,current,,A list of information about egress nicknames used for multi-destination frame forwarding by this RBridge.
.1.3.6.1.2.1.214.1.2.6.1.1,RBRIDGE-MIB::rbridgeMultiFibNickname,Unsigned32,not-accessible,,current,,The nickname of the multicast distribution tree.
.1.3.6.1.2.1.214.1.2.6.1.2,RBRIDGE-MIB::rbridgeMultiFibPorts,OCTET,read-only,,current,,The list of ports to which a frame destined to this multicast distribution tree is flooded. This may be pruned further based on other forwarding information.
.1.3.6.1.2.1.214.1.3,RBRIDGE-MIB::rbridgeVlan,,,,,,
.1.3.6.1.2.1.214.1.3.1,RBRIDGE-MIB::rbridgeVlanTable,,not-accessible,,current,,A table that contains information about VLANs on the RBridge.
.1.3.6.1.2.1.214.1.3.1.1,RBRIDGE-MIB::rbridgeVlanEntry,,not-accessible,rbridgeVlanIndex,current,,A list of information about VLANs on the RBridge.
.1.3.6.1.2.1.214.1.3.1.1.1,RBRIDGE-MIB::rbridgeVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID referring to this VLAN.
.1.3.6.1.2.1.214.1.3.1.1.2,RBRIDGE-MIB::rbridgeVlanForwarderLosts,Counter32,read-only,,current,,The number of times this RBridge has lost appointed forwarder status for this VLAN on any of its ports. Discontinuities in the value of this counter can occur at re-initialization of the management system.
.1.3.6.1.2.1.214.1.3.1.1.3,RBRIDGE-MIB::rbridgeVlanDisableLearning,INTEGER,read-write,,current,true(1):false(2),Disable learning of MAC addresses seen in this VLAN. One application of this may be to restrict learning to ESADI. To disable learning, the value of this object should be set to 'true'. The default is 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.3.1.1.4,RBRIDGE-MIB::rbridgeVlanSnooping,INTEGER,read-only,,current,notSupported(1):ipv4(2):ipv6(3):ipv4v6(4),IP Multicast Snooping on this VLAN. For RBridges performing both IPv4 and IPv6 IP Multicast Snooping, the value returned is ipv4v6(4).
.1.3.6.1.2.1.214.1.3.2,RBRIDGE-MIB::rbridgeVlanPortTable,,not-accessible,,current,,A table that contains information about VLANs on an RBridge port.
.1.3.6.1.2.1.214.1.3.2.1,RBRIDGE-MIB::rbridgeVlanPortEntry,,not-accessible,rbridgeBasePort:rbridgeVlanIndex,current,,A list of information about VLANs on the RBridge port.
.1.3.6.1.2.1.214.1.3.2.1.1,RBRIDGE-MIB::rbridgeVlanPortInhibited,INTEGER,read-only,,current,true(1):false(2),This VLAN has been inhibited by the RBridge due to conflicting forwarder information received from another RBridge, when the value of this object is 'true'.
.1.3.6.1.2.1.214.1.3.2.1.2,RBRIDGE-MIB::rbridgeVlanPortForwarder,INTEGER,read-only,,current,true(1):false(2),This RBridge is an appointed forwarder for this VLAN on this port, when the value of this object is 'true'.
.1.3.6.1.2.1.214.1.3.2.1.3,RBRIDGE-MIB::rbridgeVlanPortAnnouncing,INTEGER,read-write,,current,true(1):false(2),TRILL-Hellos tagged with this VLAN can be sent by this RBridge on this port, when the value of this object is 'true'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.3.2.1.4,RBRIDGE-MIB::rbridgeVlanPortDetectedVlanMapping,INTEGER,read-only,,current,true(1):false(2),VLAN mapping has been detected on the link attached to this port, when the value of this object is 'true'.
.1.3.6.1.2.1.214.1.4,RBRIDGE-MIB::rbridgeEsadi,,,,,,
.1.3.6.1.2.1.214.1.4.1,RBRIDGE-MIB::rbridgeEsadiTable,,not-accessible,,current,,A table that contains information about ESADI instances on VLANs, if available.
.1.3.6.1.2.1.214.1.4.1.1,RBRIDGE-MIB::rbridgeEsadiEntry,,not-accessible,rbridgeVlanIndex,current,,Information about an ESADI instance on a VLAN.
.1.3.6.1.2.1.214.1.4.1.1.1,RBRIDGE-MIB::rbridgeEsadiEnable,INTEGER,read-create,,current,true(1):false(2),If the RBridge is participating in an ESADI instance for this VLAN, the value of this object is 'true'. To disable participation, set it to 'false'. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.4.1.1.2,RBRIDGE-MIB::rbridgeEsadiConfidence,Unsigned32,read-create,,current,,Confidence level of address entries sent by this ESADI instance. The default is 16. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.4.1.1.3,RBRIDGE-MIB::rbridgeEsadiDrbPriority,Unsigned32,read-create,,current,,The priority of this RBridge for being selected as the DRB for this ESADI instance. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.4.1.1.4,RBRIDGE-MIB::rbridgeEsadiDrb,OCTET,read-only,,current,,The DRB on this ESADI instance's virtual link.
.1.3.6.1.2.1.214.1.4.1.1.5,RBRIDGE-MIB::rbridgeEsadiDrbHoldingTime,Unsigned32,read-create,,current,,The holding time for this ESADI instance. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.4.1.1.6,RBRIDGE-MIB::rbridgeEsadiRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of the entry.
.1.3.6.1.2.1.214.1.5,RBRIDGE-MIB::rbridgeCounter,,,,,,
.1.3.6.1.2.1.214.1.5.1,RBRIDGE-MIB::rbridgePortCounterTable,,not-accessible,,current,,A table that contains per-port counters for this RBridge.
.1.3.6.1.2.1.214.1.5.1.1,RBRIDGE-MIB::rbridgePortCounterEntry,,not-accessible,rbridgeBasePort,current,,Counters for a port on this RBridge.
.1.3.6.1.2.1.214.1.5.1.1.1,RBRIDGE-MIB::rbridgePortRpfCheckFails,Counter32,read-only,,current,,The number of times a multi-destination frame was dropped on this port because the Reverse Path Forwarding (RPF) check failed. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the associated interface.
.1.3.6.1.2.1.214.1.5.1.1.2,RBRIDGE-MIB::rbridgePortHopCountExceeds,Counter32,read-only,,current,,The number of times a frame was dropped on this port because its hop count was zero. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the associated interface.
.1.3.6.1.2.1.214.1.5.1.1.3,RBRIDGE-MIB::rbridgePortOptionDrops,Counter32,read-only,,current,,The number of times a frame was dropped on this port because it contained unsupported options. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the associated interface.
.1.3.6.1.2.1.214.1.5.1.1.4,RBRIDGE-MIB::rbridgePortTrillInFrames,Counter64,read-only,,current,,The number of TRILL-encapsulated frames that have been received by this port from its attached link, including management frames. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the associated interface.
.1.3.6.1.2.1.214.1.5.1.1.5,RBRIDGE-MIB::rbridgePortTrillOutFrames,Counter64,read-only,,current,,The number of TRILL-encapsulated frames that have been transmitted by this port to its attached link, including management frames. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the associated interface.
.1.3.6.1.2.1.214.1.6,RBRIDGE-MIB::rbridgeSnooping,,,,,,
.1.3.6.1.2.1.214.1.6.1,RBRIDGE-MIB::rbridgeSnoopingPortTable,,not-accessible,,current,,For RBridges implementing IP Multicast Snooping, information about ports on which the presence of IPv4 or IPv6 multicast routers has been detected.
.1.3.6.1.2.1.214.1.6.1.1,RBRIDGE-MIB::rbridgeSnoopingPortEntry,,not-accessible,rbridgeBasePort:rbridgeVlanIndex,current,,Information about ports on which the presence of IPv4 or IPv6 multicast routers has been detected for a VLAN.
.1.3.6.1.2.1.214.1.6.1.1.1,RBRIDGE-MIB::rbridgeSnoopingPortAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2):ipv4v6(3),The IP address type of an IP multicast router detected on this port and VLAN. If only IPv4 router(s) are detected, the value returned is 'ipv4'. If only IPv6 routers are detected, the value returned is 'ipv6'. If both IPv4 and IPv6 routers are detected on this port and VLAN, the value returned is 'ipv4v6'.
.1.3.6.1.2.1.214.1.6.2,RBRIDGE-MIB::rbridgeSnoopingAddrTable,,not-accessible,,current,,For RBridges implementing IP Multicast Snooping, information about IP multicast addresses being snooped.
.1.3.6.1.2.1.214.1.6.2.1,RBRIDGE-MIB::rbridgeSnoopingAddrEntry,,not-accessible,rbridgeVlanIndex:rbridgeSnoopingAddrType:rbridgeSnoopingAddr,current,,Information about IP multicast addresses being snooped.
.1.3.6.1.2.1.214.1.6.2.1.1,RBRIDGE-MIB::rbridgeSnoopingAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The IP multicast address type for which a listener has been detected by this RBridge. This MIB requires support for only IPv4 and IPv6 address types.
.1.3.6.1.2.1.214.1.6.2.1.2,RBRIDGE-MIB::rbridgeSnoopingAddr,OCTET,not-accessible,,current,,The IP multicast address for which a listener has been detected by this RBridge. The address type of this object is specified in rbridgeSnoopingAddrType. This MIB requires support for only global IPv4 and IPv6 addresses, so the length of the object can be either 4 or 16 bytes. Hence, the index will not exceed the OID size limit.
.1.3.6.1.2.1.214.1.6.2.1.3,RBRIDGE-MIB::rbridgeSnoopingAddrPorts,OCTET,read-only,,current,,The set of ports on which a listener has been detected for this IP multicast address.
.1.3.6.1.2.1.214.1.7,RBRIDGE-MIB::rbridgeDtree,,,,,,
.1.3.6.1.2.1.214.1.7.1,RBRIDGE-MIB::rbridgeDtreePriority,Unsigned32,read-write,,current,,The distribution tree root priority for this RBridge. The default value of this object is 32768. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.7.2,RBRIDGE-MIB::rbridgeDtreeActiveTrees,Unsigned32,read-only,,current,,The total number of trees being computed by all RBridges in the campus.
.1.3.6.1.2.1.214.1.7.3,RBRIDGE-MIB::rbridgeDtreeMaxTrees,Unsigned32,read-only,,current,,The maximum number of trees this RBridge can compute.
.1.3.6.1.2.1.214.1.7.4,RBRIDGE-MIB::rbridgeDtreeDesiredUseTrees,Unsigned32,read-only,,current,,The maximum number of trees this RBridge would like to use for transmission of ingress multi-destination frames.
.1.3.6.1.2.1.214.1.7.5,RBRIDGE-MIB::rbridgeDtreeTable,,not-accessible,,current,,Information about distribution trees being computed by this RBridge.
.1.3.6.1.2.1.214.1.7.5.1,RBRIDGE-MIB::rbridgeDtreeEntry,,not-accessible,rbridgeDtreeNumber,current,,List of information about distribution trees being computed by this RBridge.
.1.3.6.1.2.1.214.1.7.5.1.1,RBRIDGE-MIB::rbridgeDtreeNumber,Unsigned32,not-accessible,,current,,The tree number of a distribution tree being computed by this RBridge.
.1.3.6.1.2.1.214.1.7.5.1.2,RBRIDGE-MIB::rbridgeDtreeNickname,Unsigned32,read-only,,current,,The nickname of the distribution tree.
.1.3.6.1.2.1.214.1.7.5.1.3,RBRIDGE-MIB::rbridgeDtreeIngress,INTEGER,read-only,,current,true(1):false(2),Indicates whether this RBridge might choose this distribution tree to ingress a multi-destination frame.
.1.3.6.1.2.1.214.1.8,RBRIDGE-MIB::rbridgeTrill,,,,,,
.1.3.6.1.2.1.214.1.8.1,RBRIDGE-MIB::rbridgeTrillMinMtuDesired,Unsigned32,read-write,,current,,The desired minimum acceptable inter-RBridge link MTU for the campus, that is, originatingLSPBufferSize. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.8.2,RBRIDGE-MIB::rbridgeTrillSz,Unsigned32,read-only,,current,,The minimum acceptable inter-RBridge link size for the campus for the proper operation of TRILL IS-IS.
.1.3.6.1.2.1.214.1.8.3,RBRIDGE-MIB::rbridgeTrillMaxMtuProbes,Unsigned32,read-write,,current,,The number of failed MTU-probes before the RBridge concludes that a particular MTU is not supported by a neighbor. The value of this object MUST be retained across re-initializations of the management system.
.1.3.6.1.2.1.214.1.8.4,RBRIDGE-MIB::rbridgeTrillNbrTable,,not-accessible,,current,,Information about this RBridge's TRILL neighbors.
.1.3.6.1.2.1.214.1.8.4.1,RBRIDGE-MIB::rbridgeTrillNbrEntry,,not-accessible,rbridgeTrillNbrMacAddr,current,,List of information about this RBridge's TRILL neighbors.
.1.3.6.1.2.1.214.1.8.4.1.1,RBRIDGE-MIB::rbridgeTrillNbrMacAddr,OCTET,not-accessible,,current,,The MAC address of a neighbor of this RBridge.
.1.3.6.1.2.1.214.1.8.4.1.2,RBRIDGE-MIB::rbridgeTrillNbrMtu,Unsigned32,read-only,,current,,MTU size for this neighbor for IS-IS communication purposes.
.1.3.6.1.2.1.214.1.8.4.1.3,RBRIDGE-MIB::rbridgeTrillNbrFailedMtuTest,INTEGER,read-only,,current,true(1):false(2),If true, indicates that the neighbor's tested MTU is less than the minimum acceptable inter-bridge link MTU for the campus (1470).
.1.3.6.1.2.1.214.2,RBRIDGE-MIB::rbridgeConformance,,,,,,
.1.3.6.1.2.1.214.2.1,RBRIDGE-MIB::rbridgeCompliances,,,,,,
.1.3.6.1.2.1.214.2.1.1,RBRIDGE-MIB::rbridgeCompliance,,,,,,The compliance statement for support of RBridge services.
.1.3.6.1.2.1.214.2.1.2,RBRIDGE-MIB::rbridgeReadOnlyCompliance,,,,,,When this MIB is implemented in read-only mode, then the implementation can claim read-only compliance. In that case, RBridge objects can be monitored but cannot be configured with this implementation.
.1.3.6.1.2.1.214.2.2,RBRIDGE-MIB::rbridgeGroup,,,,,,
.1.3.6.1.2.1.214.2.2.1,RBRIDGE-MIB::rbridgeBaseGroup,,,,,,A collection of objects providing basic control and status information for the RBridge.
.1.3.6.1.2.1.214.2.2.2,RBRIDGE-MIB::rbridgeBaseNicknameGroup,,,,,,A collection of objects providing basic control and status information for RBridge nicknames.
.1.3.6.1.2.1.214.2.2.3,RBRIDGE-MIB::rbridgeBasePortGroup,,,,,,A collection of objects providing basic control and status information for RBridge ports.
.1.3.6.1.2.1.214.2.2.4,RBRIDGE-MIB::rbridgeFdbGroup,,,,,,A collection of objects providing information about the Unicast Address Database.
.1.3.6.1.2.1.214.2.2.5,RBRIDGE-MIB::rbridgeFibGroup,,,,,,A collection of objects providing information about the Unicast and Multicast FIBs.
.1.3.6.1.2.1.214.2.2.6,RBRIDGE-MIB::rbridgeVlanGroup,,,,,,A collection of objects providing information about VLANs on the RBridge.
.1.3.6.1.2.1.214.2.2.7,RBRIDGE-MIB::rbridgePortCounterGroup,,,,,,A collection of objects providing per-port counters for the RBridge.
.1.3.6.1.2.1.214.2.2.8,RBRIDGE-MIB::rbridgeEsadiGroup,,,,,,A collection of objects providing information about ESADI instances on the RBridge.
.1.3.6.1.2.1.214.2.2.9,RBRIDGE-MIB::rbridgeSnoopingGroup,,,,,,A collection of objects providing information about IP Multicast Snooping. This MIB requires support for only global IPv4 and IPv6 address types in rbridgeSnoopingPortAddrType and rbridgeSnoopingAddrType, so the length of rbridgeSnoopingAddr can be either 4 or 16 bytes.
.1.3.6.1.2.1.214.2.2.10,RBRIDGE-MIB::rbridgeDtreeGroup,,,,,,A collection of objects providing information about distribution trees.
.1.3.6.1.2.1.214.2.2.11,RBRIDGE-MIB::rbridgeTrillGroup,,,,,,A collection of objects providing information about TRILL neighbors.
.1.3.6.1.2.1.214.2.2.12,RBRIDGE-MIB::rbridgeNotificationGroup,,,,,,A collection of objects describing notifications (traps).
.1.3.6.1.2.1.215,IANA-GBOND-TC-MIB::ianaGBondTcMIB,,,,,,This MIB module defines IANAgBondScheme and IANAgBondSchemeList TEXTUAL-CONVENTIONs, specifying enumerated values of the gBondPortConfAdminScheme, gBondPortConfPeerAdminScheme, gBondPortStatOperScheme, gBondPortStatPeerOperScheme, gBondPortCapSchemesSupported, and gBondPortCapPeerSchemesSupported objects, respectively, as defined in the GBOND-MIB. It is intended that each new bonding scheme defined by the ITU-T Q4/SG15 working group and approved for publication in a revision of the ITU-T G.998 specification will be added to this MIB module, provided that it is suitable for being managed by the base objects in the GBOND-MIB. An Expert Review, as defined in RFC 5226, is REQUIRED for such additions. The following references are used throughout this MIB module: [G.998.1] refers to: ITU-T Recommendation G.998.1: 'ATM-based multi-pair bonding', January 2005. [G.998.2] refers to: ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair bonding', January 2005. [G.998.3] refers to: ITU-T Recommendation G.998.3: 'Multi-pair bonding using time-division inverse multiplexing', January 2005. Naming Conventions: BCE - Bonding Channel Entity GBS - Generic Bonding Sub-layer These references should be updated as appropriate when a new bonding scheme is added to this MIB module. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.216,IANA-ENTITY-MIB::ianaEntityMIB,,,,,,This MIB module defines a TEXTUAL-CONVENTION that provides an indication of the general hardware type of a particular physical entity. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). The initial version of this MIB module was published in RFC 6933; for full legal notices see the RFC itself.
.1.3.6.1.2.1.217,UUID-TC-MIB::uuidTCMIB,,,,,,This MIB module defines TEXTUAL-CONVENTIONs representing Universally Unique IDentifiers (UUIDs). Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.218,RPKI-ROUTER-MIB::rpkiRtrMIB,,,,,,This MIB module contains management objects to support monitoring of the Resource Public Key Infrastructure (RPKI) protocol on routers. Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 6945; see the RFC itself for full legal notices.
.1.3.6.1.2.1.218.0,RPKI-ROUTER-MIB::rpkiRtrNotifications,,,,,,
.1.3.6.1.2.1.218.0.1,RPKI-ROUTER-MIB::rpkiRtrCacheServerConnectionStateChange,,,,,,This notification signals a change in the status of an rpkiRtrCacheServerConnection. The management agent MUST throttle the generation of consecutive rpkiRtrCacheServerConnectionStateChange notifications such that there is at least a 5 second gap between them. If more than one notification has occurred locally during that time, the most recent notification is sent at the end of the 5 second gap and the others are discarded.
.1.3.6.1.2.1.218.0.2,RPKI-ROUTER-MIB::rpkiRtrCacheServerConnectionToGoStale,,,,,,This notification signals that an RPKI cache server connection is about to go stale. It is suggested that this notification is generated when the value of the rpkiRtrCacheServerTimeToRefresh attribute goes below 60 seconds. The SNMP agent MUST throttle the generation of consecutive rpkiRtrCacheServerConnectionToGoStale notifications such that there is at least a 5 second gap between them. 
.1.3.6.1.2.1.218.1,RPKI-ROUTER-MIB::rpkiRtrObjects,,,,,,
.1.3.6.1.2.1.218.1.1,RPKI-ROUTER-MIB::rpkiRtrDiscontinuityTimer,TimeTicks,read-only,,current,,This timer represents the timestamp (value of sysUpTime) at which time any of the Counter32 objects in this MIB module encountered a discontinuity. For objects that use rpkiRtrDiscontinuityTimer to indicate discontinuity, only values received since the time indicated by rpkiRtrDiscontinuityTimer are comparable to each other. A manager should take the possibility of rollover into account when calculating difference values. In principle, that should only happen if the SNMP agent or the instrumentation for this MIB module starts or restarts.
.1.3.6.1.2.1.218.1.2,RPKI-ROUTER-MIB::rpkiRtrCacheServerTable,,not-accessible,,current,,This table lists the RPKI cache servers known to this router/system.
.1.3.6.1.2.1.218.1.2.1,RPKI-ROUTER-MIB::rpkiRtrCacheServerTableEntry,,not-accessible,rpkiRtrCacheServerRemoteAddressType:rpkiRtrCacheServerRemoteAddress:rpkiRtrCacheServerRemotePort,current,,An entry in the rpkiRtrCacheServerTable. It holds management attributes associated with one connection to a RPKI cache server. Implementers should be aware that if the rpkiRtrCacheServerRemoteAddress object exceeds 114 octets, the index values will exceed the 128 sub-identifier limit and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.218.1.2.1.1,RPKI-ROUTER-MIB::rpkiRtrCacheServerRemoteAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The network address type of the connection to this RPKI cache server. Note: Only IPv4, IPv6, and DNS support are required for read-only compliance with RFC 6945.
.1.3.6.1.2.1.218.1.2.1.2,RPKI-ROUTER-MIB::rpkiRtrCacheServerRemoteAddress,OCTET,not-accessible,,current,,The remote network address for this connection to this RPKI cache server. The format of the address is defined by the value of the corresponding instance of rpkiRtrCacheServerRemoteAddressType. This object matches the address type used within the local router configuration. If the address is of type dns (fqdn), then the router will resolve it at the time it connects to the cache server.
.1.3.6.1.2.1.218.1.2.1.3,RPKI-ROUTER-MIB::rpkiRtrCacheServerRemotePort,Unsigned32,not-accessible,,current,,The remote port number for this connection to this RPKI cache server.
.1.3.6.1.2.1.218.1.2.1.4,RPKI-ROUTER-MIB::rpkiRtrCacheServerLocalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The network address type of the connection to this RPKI cache server. Note: Only IPv4, IPv6, and DNS support are required for read-only compliance with RFC 6945.
.1.3.6.1.2.1.218.1.2.1.5,RPKI-ROUTER-MIB::rpkiRtrCacheServerLocalAddress,OCTET,read-only,,current,,The local network address for this connection to this RPKI cache server. The format of the address is defined by the value of the corresponding instance of rpkiRtrCacheServerLocalAddressType. This object matches the address type used within the local router configuration. If the address is of type dns (fqdn), then the router will resolve it at the time it connects to the cache server.
.1.3.6.1.2.1.218.1.2.1.6,RPKI-ROUTER-MIB::rpkiRtrCacheServerLocalPort,Unsigned32,read-only,,current,,The local port number for this connection to this RPKI cache server.
.1.3.6.1.2.1.218.1.2.1.7,RPKI-ROUTER-MIB::rpkiRtrCacheServerPreference,Unsigned32,read-only,,current,,The routers' preference for this RPKI cache server. A lower value means more preferred. If two entries have the same preference, then the order is arbitrary. In two cases, the maximum value for an Unsigned32 object should be returned for this object: - If no order is specified in the RPKI-Router configuration. - If a preference value is configured that is larger than the max value for an Unsigned32 object.
.1.3.6.1.2.1.218.1.2.1.8,RPKI-ROUTER-MIB::rpkiRtrCacheServerConnectionType,INTEGER,read-only,,current,ssh(1):tls(2):tcpMD5(3):tcpAO(4):tcp(5):ipsec(6):other(7),The connection type or transport security suite in use for this RPKI cache server.
.1.3.6.1.2.1.218.1.2.1.9,RPKI-ROUTER-MIB::rpkiRtrCacheServerConnectionStatus,INTEGER,read-only,,current,up(1):down(2),The connection status for this entry (connection to this RPKI cache server).
.1.3.6.1.2.1.218.1.2.1.10,RPKI-ROUTER-MIB::rpkiRtrCacheServerDescription,OCTET,read-only,,current,,Free form description/information for this connection to this RPKI cache server.
.1.3.6.1.2.1.218.1.2.1.11,RPKI-ROUTER-MIB::rpkiRtrCacheServerMsgsReceived,Counter32,read-only,,current,,Number of messages received from this RPKI cache server via this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.2.1.12,RPKI-ROUTER-MIB::rpkiRtrCacheServerMsgsSent,Counter32,read-only,,current,,Number of messages sent to this RPKI cache server via this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.2.1.13,RPKI-ROUTER-MIB::rpkiRtrCacheServerV4ActiveRecords,Gauge32,read-only,,current,,Number of active IPv4 records received from this RPKI cache server via this connection.
.1.3.6.1.2.1.218.1.2.1.14,RPKI-ROUTER-MIB::rpkiRtrCacheServerV4Announcements,Counter32,read-only,,current,,The number of IPv4 records announced by the RPKI cache server via this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.2.1.15,RPKI-ROUTER-MIB::rpkiRtrCacheServerV4Withdrawals,Counter32,read-only,,current,,The number of IPv4 records withdrawn by the RPKI cache server via this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.2.1.16,RPKI-ROUTER-MIB::rpkiRtrCacheServerV6ActiveRecords,Gauge32,read-only,,current,,Number of active IPv6 records received from this RPKI cache server via this connection.
.1.3.6.1.2.1.218.1.2.1.17,RPKI-ROUTER-MIB::rpkiRtrCacheServerV6Announcements,Counter32,read-only,,current,,The number of IPv6 records announced by the RPKI cache server via this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.2.1.18,RPKI-ROUTER-MIB::rpkiRtrCacheServerV6Withdrawals,Counter32,read-only,,current,,The number of IPv6 records withdrawn by the RPKI cache server via this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.2.1.19,RPKI-ROUTER-MIB::rpkiRtrCacheServerLatestSerial,Unsigned32,read-only,,current,,The latest serial number of data received from this RPKI server on this connection. Note: this value wraps back to zero when it reaches its maximum value.
.1.3.6.1.2.1.218.1.2.1.20,RPKI-ROUTER-MIB::rpkiRtrCacheServerSessionID,Unsigned32,read-only,,current,,The Session ID associated with the RPKI cache server at the other end of this connection.
.1.3.6.1.2.1.218.1.2.1.21,RPKI-ROUTER-MIB::rpkiRtrCacheServerRefreshTimer,Unsigned32,read-only,,current,,The number of seconds configured for the refresh timer for this connection to this RPKI cache server.
.1.3.6.1.2.1.218.1.2.1.22,RPKI-ROUTER-MIB::rpkiRtrCacheServerTimeToRefresh,Integer32,read-only,,current,,The number of seconds remaining before a new refresh is performed via a Serial Query to this cache server over this connection. A negative value means that the refresh time has passed this many seconds and the refresh has not yet been completed. It will stop decrementing at the maximum negative value. Upon a completed refresh (i.e., a successful and complete response to a Serial Query) the value of this attribute will be reinitialized with the value of the corresponding rpkiRtrCacheServerRefreshTimer attribute.
.1.3.6.1.2.1.218.1.2.1.23,RPKI-ROUTER-MIB::rpkiRtrCacheServerId,Unsigned32,read-only,,current,,The unique ID for this connection. An implementation must make sure this ID is unique within this table. It is this ID that can be used to find entries in the rpkiRtrPrefixOriginTable that were created by announcements received on this connection from this cache server.
.1.3.6.1.2.1.218.1.3,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsTable,,not-accessible,,current,,This table provides statistics on errors per RPKI peer connection. These can be used for debugging.
.1.3.6.1.2.1.218.1.3.1,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsTableEntry,,not-accessible,,current,,An entry in the rpkiCacheServerErrorTable. It holds management objects associated with errors codes that were received on the specified connection to a specific cache server.
.1.3.6.1.2.1.218.1.3.1.1,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsCorruptData,Counter32,read-only,,current,,The number of 'Corrupt Data' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.2,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsInternalError,Counter32,read-only,,current,,The number of 'Internal Error' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.3,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsNoData,Counter32,read-only,,current,,The number of 'No Data Available' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.4,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsInvalidRequest,Counter32,read-only,,current,,The number of 'Invalid Request' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.5,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsUnsupportedVersion,Counter32,read-only,,current,,The number of 'Unsupported Protocol Version' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.6,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsUnsupportedPdu,Counter32,read-only,,current,,The number of 'Unsupported PDU Type' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.7,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsWithdrawalUnknown,Counter32,read-only,,current,,The number of 'Withdrawal of Unknown Record' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.3.1.8,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsDuplicateAnnounce,Counter32,read-only,,current,,The number of 'Duplicate Announcement Received' errors received from the RPKI cache server at the other end of this connection. Discontinuities are indicated by the value of rpkiRtrDiscontinuityTimer.
.1.3.6.1.2.1.218.1.4,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginTable,,not-accessible,,current,,This table lists the prefixes that were announced by RPKI cache servers to this system. That is the prefixes and their Origin Autonomous System Number (ASN) as received by announcements via the RPKI-Router Protocol.
.1.3.6.1.2.1.218.1.4.1,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginTableEntry,,not-accessible,rpkiRtrPrefixOriginAddressType:rpkiRtrPrefixOriginAddress:rpkiRtrPrefixOriginMinLength:rpkiRtrPrefixOriginMaxLength:rpkiRtrPrefixOriginASN:rpkiRtrPrefixOriginCacheServerId,current,,An entry in the rpkiRtrPrefixOriginTable. This represents one announced prefix. If a cache server is removed from the local configuration, any table rows associated with that server (indicated by rpkiRtrPrefixOriginCacheServerId) are also removed from this table. Implementers should be aware that if the rpkiRtrPrefixOriginAddress object exceeds 111 octets, the index values will exceed the 128 sub-identifier limit and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
.1.3.6.1.2.1.218.1.4.1.1,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The network address type for this prefix. Note: Only IPv4 and IPv6 support are required for read-only compliance with RFC 6945.
.1.3.6.1.2.1.218.1.4.1.2,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginAddress,OCTET,not-accessible,,current,,The network address for this prefix. The format of the address is defined by the value of the corresponding instance of rpkiRtrPrefixOriginAddressType.
.1.3.6.1.2.1.218.1.4.1.3,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginMinLength,Unsigned32,not-accessible,,current,,The minimum prefix length allowed for this prefix.
.1.3.6.1.2.1.218.1.4.1.4,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginMaxLength,Unsigned32,not-accessible,,current,,The maximum prefix length allowed for this prefix. Note, this value must be greater or equal to the value of rpkiRtrPrefixOriginMinLength.
.1.3.6.1.2.1.218.1.4.1.5,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginASN,Unsigned32,not-accessible,,current,,The ASN that is authorized to announce the prefix or sub-prefixes covered by this entry.
.1.3.6.1.2.1.218.1.4.1.6,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginCacheServerId,Unsigned32,read-only,,current,,The unique ID of the connection to the cache server from which this announcement was received. That connection is identified/found by a matching value in attribute rpkiRtrCacheServerId.
.1.3.6.1.2.1.218.2,RPKI-ROUTER-MIB::rpkiRtrConformance,,,,,,
.1.3.6.1.2.1.218.2.1,RPKI-ROUTER-MIB::rpkiRtrCompliances,,,,,,
.1.3.6.1.2.1.218.2.1.1,RPKI-ROUTER-MIB::rpkiRtrRFC6945ReadOnlyCompliance,,,,,,The compliance statement for the rpkiRtrMIB module. There are only read-only objects in this MIB module, so the 'ReadOnly' in the name of this compliance statement is there only for clarity and truth in advertising. There are a number of INDEX objects that cannot be represented in the form of OBJECT clauses in SMIv2, but for which there are compliance requirements. Those requirements and similar requirements for related objects are expressed below, in pseudo-OBJECT clause form, in this description: -- OBJECT rpkiRtrCacheServerRemoteAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2), dns(16) } -- DESCRIPTION -- The MIB requires support for the IPv4, IPv6, and DNS -- InetAddressTypes for this object. -- OBJECT rpkiRtrCacheServerLocalAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2), dns(16) } -- DESCRIPTION -- The MIB requires support for the IPv4, IPv6, and DNS -- InetAddressTypes for this object. -- OBJECT rpkiRtrPrefixOriginAddressType -- SYNTAX InetAddressType { ipv4(1), ipv6(2) } -- DESCRIPTION -- The MIB requires support for the IPv4, and IPv6 -- InetAddressTypes for this object. 
.1.3.6.1.2.1.218.2.2,RPKI-ROUTER-MIB::rpkiRtrGroups,,,,,,
.1.3.6.1.2.1.218.2.2.1,RPKI-ROUTER-MIB::rpkiRtrCacheServerGroup,,,,,,The collection of objects to monitor the RPKI peer connections.
.1.3.6.1.2.1.218.2.2.2,RPKI-ROUTER-MIB::rpkiRtrCacheServerErrorsGroup,,,,,,The collection of objects that may help in debugging the communication between RPKI clients and cache servers.
.1.3.6.1.2.1.218.2.2.3,RPKI-ROUTER-MIB::rpkiRtrPrefixOriginGroup,,,,,,The collection of objects that represent the prefix(es) and their validated Origin ASes.
.1.3.6.1.2.1.218.2.2.4,RPKI-ROUTER-MIB::rpkiRtrNotificationsGroup,,,,,,The set of notifications to alert an NMS of change in connections to RPKI cache servers.
.1.3.6.1.2.1.219,OLSRv2-MIB::manetOlsrv2MIB,,,,,,This OLSRv2-MIB module is applicable to routers implementing the Optimized Link State Routing Protocol version 2 (OLSRv2) defined in RFC 7181. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 7184; see the RFC itself for full legal notices.
.1.3.6.1.2.1.219.0,OLSRv2-MIB::olsrv2MIBNotifications,,,,,,
.1.3.6.1.2.1.219.0.0,OLSRv2-MIB::olsrv2NotificationsObjects,,,,,,
.1.3.6.1.2.1.219.0.0.1,OLSRv2-MIB::olsrv2RouterStatusChange,,,,,,olsrv2RouterStatusChange is a notification generated when the OLSRv2 router changes it status. The router status is maintained in the olsrv2AdminStatus object.
.1.3.6.1.2.1.219.0.0.2,OLSRv2-MIB::olsrv2OrigIpAddrChange,,,,,,olsrv2OrigIpAddrChange is a notification generated when the OLSRv2 router changes it originator IP address. The notification includes the new and the previous originator IP address of the OLSRv2 router.
.1.3.6.1.2.1.219.0.0.3,OLSRv2-MIB::olsrv2RoutingSetRecalculationCountChange,,,,,,The olsrv2RoutingSetRecalculationCountChange notification is generated when a significant number of Routing Set recalculations have occurred in a short time. This notification SHOULD be generated no more than once per olsrv2RoutingSetRecalculationCountWindow. The network administrator SHOULD select appropriate values for 'significant number of Routing Set recalculations' and 'short time' through the settings of the olsrv2RoutingSetRecalculationCountThreshold and olsrv2RoutingSetRecalculationCountWindow objects.
.1.3.6.1.2.1.219.0.0.4,OLSRv2-MIB::olsrv2MPRSetRecalculationCountChange,,,,,,The olsrv2MPRSetRecalculationCountChange notification is generated when a significant number of MPR set recalculations occur in a short period of time. This notification SHOULD be generated no more than once per olsrv2MPRSetRecalculationCountWindow. The network administrator SHOULD select appropriate values for 'significant number of MPR set recalculations' and 'short period of time' through the settings of the olsrv2MPRSetRecalculationCountThreshold and olsrv2MPRSetRecalculationCountWindow objects.
.1.3.6.1.2.1.219.0.1,OLSRv2-MIB::olsrv2NotificationsControl,,,,,,
.1.3.6.1.2.1.219.0.1.1,OLSRv2-MIB::olsrv2RoutingSetRecalculationCountThreshold,Integer32,read-write,,current,,A threshold value for the olsrv2RoutingSetRecalculationCount object. If the number of occurrences exceeds this threshold within the previous olsrv2RoutingSetRecalculationCountWindow, then the olsrv2RoutingSetRecalculationCountChange notification is to be generated. It is RECOMMENDED that the value of this threshold be set to at least 20 and higher in dense topologies with frequent expected topology changes.
.1.3.6.1.2.1.219.0.1.2,OLSRv2-MIB::olsrv2RoutingSetRecalculationCountWindow,TimeTicks,read-write,,current,,This object is used to determine whether to generate an olsrv2RoutingSetRecalculationCountChange notification. This object represents an interval from the present moment, extending into the past, expressed in hundredths of a second. If the change in the value of the olsrv2RoutingSetRecalculationCount object during this interval has exceeded the value of olsrv2RoutingSetRecalculationCountThreshold, then an olsrv2RoutingSetRecalculationCountChange notification is generated. It is RECOMMENDED that the value for this window be set to at least 5 times the nhdpHelloInterval (whose default value is 2 seconds.
.1.3.6.1.2.1.219.0.1.3,OLSRv2-MIB::olsrv2MPRSetRecalculationCountThreshold,Integer32,read-write,,current,,A threshold value for the olsrv2MPRSetRecalculationCount object. If the number of occurrences exceeds this threshold within the previous olsrv2MPRSetRecalculationCountWindow, then the olsrv2MPRSetRecalculationCountChange notification is to be generated. It is RECOMMENDED that the value of this threshold be set to at least 20 and higher in dense topologies with frequent expected topology changes.
.1.3.6.1.2.1.219.0.1.4,OLSRv2-MIB::olsrv2MPRSetRecalculationCountWindow,TimeTicks,read-write,,current,,This object is used to determine whether to generate an olsrv2MPRSetRecalculationCountChange notification. This object represents an interval from the present moment, extending into the past, expressed in hundredths of a second. If the change in the value of the olsrv2MPRSetRecalculationCount object during that interval has exceeded the value of olsrv2MPRSetRecalculationCountThreshold, then the an olsrv2MPRSetRecalculationCountChange notification is generated. It is RECOMMENDED that the value for this window be set to at least 5 times the nhdpHelloInterval.
.1.3.6.1.2.1.219.0.2,OLSRv2-MIB::olsrv2NotificationsStates,,,,,,
.1.3.6.1.2.1.219.0.2.1,OLSRv2-MIB::olsrv2PreviousOrigIpAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2),The type of the olsrv2PreviousOrigIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported. This object MUST have the same persistence characteristics as olsrv2PreviousOrigIpAddr.
.1.3.6.1.2.1.219.0.2.2,OLSRv2-MIB::olsrv2PreviousOrigIpAddr,OCTET,read-only,,current,,The previous origination IP address of this OLSRv2 router. This object SHOULD be updated each time the olsrv2OrigIpAddr is modified. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1,OLSRv2-MIB::olsrv2MIBObjects,,,,,,
.1.3.6.1.2.1.219.1.1,OLSRv2-MIB::olsrv2ConfigurationGroup,,,,,,
.1.3.6.1.2.1.219.1.1.1,OLSRv2-MIB::olsrv2AdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The configured status of the OLSRv2 process on this device. 'enabled(1)' means that OLSRv2 is configured to run on this device. 'disabled(2)' mean that the OLSRv2 process is configured off. Operation of the OLSRv2 protocol requires the operation of the Neighborhood Discovery Protocol (RFC 6130). Hence, this object cannot have a status of 'enabled' unless at least one interface on the device is a MANET interface with NHDP enabled on that interface. If a network manager attempts to set this object to 'enabled' when no interfaces on this device have NHDP enabled, the device MUST fail the set with inconsistentValue. If all device interfaces running NHDP become disabled or removed, then the olsrv2AdminStatus MUST be 'disabled'. If the network manager, or other means, sets this object to 'disabled', then the associated interface specific objects, i.e., the olsrv2InterfaceAdminStatus objects MUST all be 'disabled'. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.2,OLSRv2-MIB::olsrv2InterfaceTable,,not-accessible,,current,,The olsrv2InterfaceTable describes the OLSRv2 status on the NHDP interfaces of this router. As such, this table augments the nhdpInterfaceTable defined in the NHDP-MIB (RFC 6779). NHDP interfaces are explicitly defined by network management, command line interface (CLI) or other means for interfaces on the device that are intended to run MANET protocols. The olsrv2InterfaceTable contains a single object: the olsrv2InterfaceAdminStatus object. This object is set by network management, or by other means, e.g., CLI. A conceptual row in this table exists if and only if a corresponding entry in the nhdpInterfaceTable exists. If the corresponding entry with nhdpIfIndex value is deleted from the nhdpInterfaceTable, then the entry in this table is automatically deleted and OLSRv2 is disabled on this interface, and all configuration and state information related to this interface is to be removed from memory. The olsrv2InterfaceAdminStatus can only be 'enabled' if the corresponding olsrv2AdminStatus object is also set to 'enabled'.
.1.3.6.1.2.1.219.1.1.2.1,OLSRv2-MIB::olsrv2InterfaceEntry,,not-accessible,,current,,The olsrv2InterfaceEntry describes one OLSRv2 local interface configuration as indexed by its nhdpIfIndex, as defined in the NHDP-MIB (RFC 6779). The objects in this table are persistent, and when written, the device SHOULD save the change to non-volatile storage. For further information on the storage behavior for these objects, refer to the description for the nhdpIfRowStatus object in the NHDP-MIB (RFC6779).
.1.3.6.1.2.1.219.1.1.2.1.1,OLSRv2-MIB::olsrv2InterfaceAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),The OLSRv2 interface's administrative status. The value 'enabled(1)' denotes that the interface is permitted to participate in the OLSRv2 routing process. The value 'disabled(2)' denotes that the interface is not permitted to participate in the OLSRv2 routing process. The configuration objects for the OLSRv2 routing process, other than the administrative status objects, are common to all interfaces on this device. As such, the OLSRv2 configuration objects are globally defined for the device and are not contained within the olsrv2InterfaceTable.
.1.3.6.1.2.1.219.1.1.3,OLSRv2-MIB::olsrv2OrigIpAddrType,INTEGER,read-write,,current,ipv4(1):ipv6(2),The type of the olsrv2OrigIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.1.4,OLSRv2-MIB::olsrv2OrigIpAddr,OCTET,read-write,,current,,The router's originator address. An address that is unique (within the MANET) to this router. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.5,OLSRv2-MIB::olsrv2OHoldTime,Unsigned32,read-write,,current,,olsrv2OHoldTime corresponds to O_HOLD_TIME of OLSRv2, and represents the time for which a recently used and replaced originator address is used to recognize the router's own messages. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2OHoldTime > 0 This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.6,OLSRv2-MIB::olsrv2TcInterval,Unsigned32,read-write,,current,,olsrv2TcInterval corresponds to TC_INTERVAL of OLSRv2 and represents the maximum time between the transmission of two successive TC messages by this router. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2TcInterval > 0 o olsrv2TcInterval >= olsrv2TcMinInterval This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.7,OLSRv2-MIB::olsrv2TcMinInterval,Unsigned32,read-write,,current,,olsrv2TcMinInterval corresponds to TC_MIN_INTERVAL of OLSRv2 and represents the minimum interval between transmission of two successive TC messages by this router. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2TcInterval >= olsrv2TcMinInterval The OLSRv2 protocol may choose to represent this time interval in terms of the 8-bit exponent-mantissa form defined in Section 5 of RFC 5497. When this is the case, this object value MUST be translated from the integer form represented in this MIB module into the exponent-mantissa form for the OLSRv2 protocol to use according to the algorithm defined in Section 5 of RFC 5497 for finding the next larger time value within the exponent-mantissa format. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.8,OLSRv2-MIB::olsrv2THoldTime,Unsigned32,read-write,,current,,olsrv2THoldTime corresponds to T_HOLD_TIME of OLSRv2 and is used as the minimum value in the TLV with Type = VALIDITY_TIME included in all TC messages sent by this router. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2THoldTime >= olsrv2TcInterval o If TC messages can be lost, then olsrv2THoldTime SHOULD be significantly greater than olsrv2TcInterval; a value >= 3 x olsrv2TcInterval is RECOMMENDED. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.9,OLSRv2-MIB::olsrv2AHoldTime,Unsigned32,read-write,,current,,olsrv2AHoldTime corresponds to A_HOLD_TIME of OLSRv2 and represents the period during which TC messages are sent after they no longer have any advertised information to report, but are sent in order to accelerate outdated information removal by other routers. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o If TC messages can be lost, then olsrv2AHoldTime SHOULD be significantly greater than olsrv2TcInterval; a value >= 3 x olsrv2TcInterval is RECOMMENDED. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.10,OLSRv2-MIB::olsrv2RxHoldTime,Unsigned32,read-write,,current,,olsrv2RxHoldTime corresponds to RX_HOLD_TIME of OLSRv2 and represents the period after receipt of a message by the appropriate OLSRv2 interface of this router for which that information is recorded, in order that the message is recognized as having been previously received on this OLSRv2 interface. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2RxHoldTime > 0 o This parameter SHOULD be greater than the maximum difference in time that a message may take to traverse the MANET, taking into account any message forwarding jitter as well as propagation, queuing, and processing delays. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.11,OLSRv2-MIB::olsrv2PHoldTime,Unsigned32,read-write,,current,,olsrv2PHoldTime corresponds to P_HOLD_TIME of OLSRv2 and represents the period after receipt of a message that is processed by this router for which that information is recorded, in order that the message is not processed again if received again. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2PHoldTime > 0 o This parameter SHOULD be greater than the maximum difference in time that a message may take to traverse the MANET, taking into account any message forwarding jitter as well as propagation, queuing, and processing delays. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.12,OLSRv2-MIB::olsrv2FHoldTime,Unsigned32,read-write,,current,,olsrv2FHoldTime corresponds to F_HOLD_TIME of OLSRv2 and represents the period after receipt of a message that is forwarded by this router for which that information is recorded, in order that the message is not forwarded again if received again. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o olsrv2FHoldTime > 0 o This parameter SHOULD be greater than the maximum difference in time that a message may take to traverse the MANET, taking into account any message forwarding jitter as well as propagation, queuing, and processing delays. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.13,OLSRv2-MIB::olsrv2TpMaxJitter,Unsigned32,read-write,,current,,olsrv2TpMaxJitter corresponds to TP_MAXJITTER of OLSRv2 and represents the value of MAXJITTER used in RFC 5148 for periodically generated TC messages sent by this router. For constraints on these parameters, see RFC 5148. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.14,OLSRv2-MIB::olsrv2TtMaxJitter,Unsigned32,read-write,,current,,olsrv2TtMaxJitter corresponds to TT_MAXJITTER of OLSRv2 and represents the value of MAXJITTER used in RFC 5148 for externally triggered TC messages sent by this router. For constraints on these parameters, see RFC 5148. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.15,OLSRv2-MIB::olsrv2FMaxJitter,Unsigned32,read-write,,current,,olsrv2FMaxJitter corresponds to F_MAXJITTER of OLSRv2 and represents the default value of MAXJITTER used in RFC 5148 for messages forwarded by this router. For constraints on these parameters, see RFC 5148. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.16,OLSRv2-MIB::olsrv2TcHopLimit,Unsigned32,read-write,,current,,olsrv2TcHopLimit corresponds to TC_HOP_LIMIT of OLSRv2. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o The maximum value of olsrv2TcHopLimit >= the network diameter in hops, a value of 255 is RECOMMENDED. o olsrv2TcHopLimit >= 2. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.17,OLSRv2-MIB::olsrv2WillRouting,Unsigned32,read-write,,current,,olsrv2WillRouting corresponds to WILL_ROUTING of OLSRv2. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o WILL_NEVER (0) <= olsrv2WillRouting <= WILL_ALWAYS (15) This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.18,OLSRv2-MIB::olsrv2WillFlooding,Unsigned32,read-write,,current,,olsrv2WillFlooding corresponds to WILL_FLOODING of OLSRv2. Guidance for setting this object may be found in Section 5 of the OLSRv2 specification (RFC 7181), which indicates that: o WILL_NEVER (0) <= olsrv2WillFlooding <= WILL_ALWAYS (15) This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.1.19,OLSRv2-MIB::olsrv2LinkMetricType,INTEGER,read-write,,current,unknown(0),olsrv2LinkMetricType corresponds to LINK_METRIC_TYPE of OLSRv2. If olsrv2LinkMetricType changes, then all link metric information recorded by this router is invalid. The router MUST take the actions described in Section 5.5. 'Parameter Change Constraints' and Section 17 'Information Base Changes' in RFC 7181. This object is persistent, and when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.2.1.219.1.2,OLSRv2-MIB::olsrv2StateGroup,,,,,,
.1.3.6.1.2.1.219.1.2.1,OLSRv2-MIB::olsrv2IibLinkSetTable,,not-accessible,,current,,A Link Set of an interface records all links from other routers that are, or recently were, 1-hop neighbors.
.1.3.6.1.2.1.219.1.2.1.1,OLSRv2-MIB::olsrv2IibLinkSetEntry,,not-accessible,,current,,A Link Set consists of Link Tuples, each representing a single link indexed by the local and remote interface pair. Each Link Set from NHDP is extended by OLSRv2 by the following fields: (L_in_metric (olsrv2IibLinkSetInMetricValue), L_out_metric (olsrv2IibLinkSetOutMetricValue), L_mpr_selector (olsrv2IibLinkSetMprSelector))
.1.3.6.1.2.1.219.1.2.1.1.1,OLSRv2-MIB::olsrv2IibLinkSetInMetricValue,Unsigned32,read-only,,current,,olsrv2IibLinkSetInMetricValue is the metric of the link from the OLSRv2 interface with addresses L_neighbor_iface_addr_list to this OLSRv2 interface. The L_neighbor_iface_addr_list is identified by the nhdpDiscIfIndex, which is an index to the nhdpIibLinkSetTable, which this table augments.
.1.3.6.1.2.1.219.1.2.1.1.2,OLSRv2-MIB::olsrv2IibLinkSetOutMetricValue,Unsigned32,read-write,,current,,olsrv2IibLinkSetOutMetricValue is the metric of the link to the OLSRv2 interface with addresses L_neighbor_iface_addr_list from this OLSRv2 interface. The L_neighbor_iface_addr_list is identified by the nhdpDiscIfIndex, which is an index to the nhdpIibLinkSetTable, which this table augments.
.1.3.6.1.2.1.219.1.2.1.1.3,OLSRv2-MIB::olsrv2IibLinkSetMprSelector,INTEGER,read-only,,current,true(1):false(2),olsrv2IibLinkSetMprSelector is a boolean flag, recording whether this neighbor has selected this router as a flooding MPR, i.e., is a flooding MPR selector of this router.
.1.3.6.1.2.1.219.1.2.2,OLSRv2-MIB::olsrv2Iib2HopSetTable,,not-accessible,,current,,A 2-Hop Set of an interface records network addresses of symmetric 2-hop neighbors, and the symmetric links to symmetric 1-hop neighbors through which these symmetric 2-hop neighbors can be reached. It consists of 2-Hop Tuples.
.1.3.6.1.2.1.219.1.2.2.1,OLSRv2-MIB::olsrv2Iib2HopSetEntry,,not-accessible,,current,,olsrv2Iib2HopSetTable consists of 2-Hop Tuples, each representing a single network address of a symmetric 2-hop neighbor and a single MANET interface of a symmetric 1-hop neighbor. Each 2-Hop Set from NHDP is extended by OLSRv2 by the following fields: (N2_in_metric (olsrv2Iib2HopSetInMetricValue), N2_out_metric (olsrv2Iib2HopSetOutMetricValue))
.1.3.6.1.2.1.219.1.2.2.1.1,OLSRv2-MIB::olsrv2Iib2HopSetInMetricValue,Unsigned32,read-only,,current,,olsrv2Iib2HopSetInMetricValue is the neighbor metric from the router with address N2_2hop_iface_addr to the router with OLSRv2 interface addresses N2_neighbor_iface_addr_list. The N2_2hop_iface_addr is identified by the (nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress) pair from the nhdpIibLinkSetTable, which this table augments. The N2_neighbor_iface_addr_list is defined by the nhdpDiscIfIndex, which is an index of the nhdpIibLinkSetTable, which this table augments.
.1.3.6.1.2.1.219.1.2.2.1.2,OLSRv2-MIB::olsrv2Iib2HopSetOutMetricValue,Unsigned32,read-only,,current,,olsrv2Iib2HopSetOutMetricValue is the neighbor metric to the router with address N2_2hop_iface_addr from the router with OLSRv2 interface addresses N2_neighbor_iface_addr_list. The N2_2hop_iface_addr is identified by the (nhdpIib2HopSetIpAddressType, nhdpIib2HopSetIpAddress) pair from the nhdpIibLinkSetTable, which this table augments. The N2_neighbor_iface_addr_list is defined by the nhdpDiscIfIndex, which is an index of the nhdpIibLinkSetTable, which this table augments.
.1.3.6.1.2.1.219.1.2.3,OLSRv2-MIB::olsrv2LibOrigSetTable,,not-accessible,,current,,A router's Originator Set records addresses that were recently used as originator addresses by this router.
.1.3.6.1.2.1.219.1.2.3.1,OLSRv2-MIB::olsrv2LibOrigSetEntry,,not-accessible,olsrv2LibOrigSetIpAddrType:olsrv2LibOrigSetIpAddr,current,,A router's Originator Set consists of Originator Tuples: (O_orig_addr (olsrv2LibOrigSetIpAddrType and olsrv2LibOrigSetIpAddr), O_time (olsrv2LibOrigSetExpireTime)).
.1.3.6.1.2.1.219.1.2.3.1.1,OLSRv2-MIB::olsrv2LibOrigSetIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2LibOrigSetIpAddr, as defined in the InetAddress MIB (RFC4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.3.1.2,OLSRv2-MIB::olsrv2LibOrigSetIpAddr,OCTET,not-accessible,,current,,An originator address recently employed by this router.
.1.3.6.1.2.1.219.1.2.3.1.3,OLSRv2-MIB::olsrv2LibOrigSetExpireTime,TimeTicks,read-only,,current,,olsrv2LibOrigSetExpireTime specifies the value of sysUptime when this entry SHOULD expire and be removed from the olsrv2LibOrigSetTable. This time is determined at the time the entry is added, derived from the following expression: O_time := current time + O_HOLD_TIME where O_time is olsrv2LibOrigSetExpireTime, current_time is current sysUptime, and O_HOLD_TIME is a parameter of the OLSRv2 protocol. In the event that the O_HOLD_TIME is changed, the olsrv2LibOrigSetExpireTime needs to be recomputed for each of the entries in this table.
.1.3.6.1.2.1.219.1.2.4,OLSRv2-MIB::olsrv2LibLocAttNetSetTable,,not-accessible,,current,,A router's Local Attached Network Set records its local non-OLSRv2 interfaces via which it can act as a gateway to other networks.
.1.3.6.1.2.1.219.1.2.4.1,OLSRv2-MIB::olsrv2LibLocAttNetSetEntry,,not-accessible,olsrv2LibLocAttNetSetIpAddrType:olsrv2LibLocAttNetSetIpAddr:olsrv2LibLocAttNetSetIpAddrPrefixLen,current,,The entries include the Local Attached Network Tuples: (AL_net_addr (olsrv2LibLocAttNetSetIpAddr), AL_dist (olsrv2LibLocAttNetSetDistance), AL_metric (olsrv2LibLocAttNetSetMetricValue) ) where: AL_net_addr is the network address of an attached network that can be reached via this router. The AL_net_addr is defined in this MIB module by the tuple (olsrv2LibLocAttNetSetIpAddrType, olsrv2LibLocAttNetSetIpAddr, olsrv2LibLocAttNetSetIpAddrPrefixLen). AL_dist is the number of hops to the network with address AL_net_addr from this router. The AL_dist is defined in this MIB module by the olsrv2LibLocAttNetSetDistance object. AL_metric is the metric of the link to the attached network with address AL_net_addr from this router. The AL_metric is defined in this MIB module by the olsrv2LibLocAttNetSetMetricValue object. OLSRv2 (RFC 7181) defines the rules for managing entries within this table, e.g., populating and purging entries. Specific instructions for the olsrv2LibLocAttNetSetEntry(s) are found in Sections 7.2 and 17 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.2.4.1.1,OLSRv2-MIB::olsrv2LibLocAttNetSetIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2LibLocAttNetSetIpAddr, as defined in the InetAddress MIB (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.4.1.2,OLSRv2-MIB::olsrv2LibLocAttNetSetIpAddr,OCTET,not-accessible,,current,,This is the network address of an attached network that can be reached via this router.
.1.3.6.1.2.1.219.1.2.4.1.3,OLSRv2-MIB::olsrv2LibLocAttNetSetIpAddrPrefixLen,Unsigned32,not-accessible,,current,,Indicates the number of leading one bits that form the mask to be logically ANDed with the destination address before being compared to the value in the olsrv2LibLocAttNetSetIpAddr field.
.1.3.6.1.2.1.219.1.2.4.1.4,OLSRv2-MIB::olsrv2LibLocAttNetSetDistance,Unsigned32,read-only,,current,,This object specifies the number of hops to the network with address olsrv2LibLocAttNetSetIpAddr from this router.
.1.3.6.1.2.1.219.1.2.4.1.5,OLSRv2-MIB::olsrv2LibLocAttNetSetMetricValue,Unsigned32,read-only,,current,,This object specifies the metric of the link to the attached network with address AL_net_addr from this router. The AL_net_addr is defined by the tuple (olsrv2LibLocAttNetSetIpAddrType, olsrv2LibLocAttNetSetIpAddr, olsrv2LibLocAttNetSetIpAddrPrefixLen).
.1.3.6.1.2.1.219.1.2.5,OLSRv2-MIB::olsrv2NibNeighborSetTable,,not-accessible,,current,,A router's Neighbor Set records all network addresses of each 1-hop neighbor. It consists of Neighbor Tuples, each representing a single 1-hop neighbor.
.1.3.6.1.2.1.219.1.2.5.1,OLSRv2-MIB::olsrv2NibNeighborSetEntry,,not-accessible,,current,,Each Neighbor Tuple in the Neighbor Set, defined in RFC 6130, has these additional elements: N_orig_addr (olsrv2NibNeighborSetNOrigIpAddrType, olsrv2NibNeighborSetNOrigIpAddr) N_in_metric (olsrv2NibNeighborSetNInMetricValue) N_out_metric (olsrv2NibNeighborSetNOutMetricValue) N_will_flooding (olsrv2NibNeighborSetNWillFlooding) N_will_routing (olsrv2NibNeighborSetNWillRouting) N_flooding_mpr (olsrv2NibNeighborSetNFloodingMpr) N_routing_mpr (olsrv2NibNeighborSetNRoutingMpr) N_mpr_selector (olsrv2NibNeighborSetNMprSelector) N_advertised (olsrv2NibNeighborSetNAdvertised) defined here as extensions.
.1.3.6.1.2.1.219.1.2.5.1.1,OLSRv2-MIB::olsrv2NibNeighborSetNOrigIpAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2),The type of the olsrv2NibNeighborSetNOrigIpAddr, as defined in the InetAddress MIB module (RFC4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.5.1.2,OLSRv2-MIB::olsrv2NibNeighborSetNOrigIpAddr,OCTET,read-only,,current,,This is the originator IP address of the neighbor represented by this table entry.
.1.3.6.1.2.1.219.1.2.5.1.3,OLSRv2-MIB::olsrv2NibNeighborSetNInMetricValue,Unsigned32,read-only,,current,,This object is the neighbor metric of any link from this neighbor to an OLSRv2 interface of this router, i.e., the minimum of all corresponding L_in_metric (olsrv2IibLinkSetInMetricValue) with L_status = SYMMETRIC and L_in_metric (olsrv2IibLinkSetInMetricValue) != UNKNOWN_METRIC, UNKNOWN_METRIC if there are no such Link Tuples. UNKNOWN_METRIC has a value of 0.
.1.3.6.1.2.1.219.1.2.5.1.4,OLSRv2-MIB::olsrv2NibNeighborSetNOutMetricValue,Unsigned32,read-only,,current,,This object is the neighbor metric of any link from an OLSRv2 interface of this router to this neighbor, i.e., the minimum of all corresponding L_out_metric (olsrv2IibLinkSetOutMetricValue) with L_status = SYMMETRIC and L_out_metric (olsrv2IibLinkSetOutMetricValue) != UNKNOWN_METRIC, UNKNOWN_METRIC if there are no such Link Tuples. UNKNOWN_METRIC has a value of 0.
.1.3.6.1.2.1.219.1.2.5.1.5,OLSRv2-MIB::olsrv2NibNeighborSetNWillFlooding,Unsigned32,read-only,,current,,This object is the neighbor's willingness to be selected as a flooding MPR, in the range from WILL_NEVER to WILL_ALWAYS, both inclusive, taking the value WILL_NEVER if no OLSRv2 specific information is received from this neighbor.
.1.3.6.1.2.1.219.1.2.5.1.6,OLSRv2-MIB::olsrv2NibNeighborSetNWillRouting,Unsigned32,read-only,,current,,This object is the neighbor's willingness to be selected as a routing MPR, in the range from WILL_NEVER to WILL_ALWAYS, both inclusive, taking the value WILL_NEVER if no OLSRv2 specific information is received from this neighbor.
.1.3.6.1.2.1.219.1.2.5.1.7,OLSRv2-MIB::olsrv2NibNeighborSetNFloodingMpr,INTEGER,read-only,,current,true(1):false(2),This object is a boolean flag, recording whether this neighbor is selected as a flooding MPR by this router.
.1.3.6.1.2.1.219.1.2.5.1.8,OLSRv2-MIB::olsrv2NibNeighborSetNRoutingMpr,INTEGER,read-only,,current,true(1):false(2),This object is a boolean flag, recording whether this neighbor is selected as a routing MPR by this router.
.1.3.6.1.2.1.219.1.2.5.1.9,OLSRv2-MIB::olsrv2NibNeighborSetNMprSelector,INTEGER,read-only,,current,true(1):false(2),This object is a boolean flag, recording whether this neighbor has selected this router as a routing MPR, i.e., is a routing MPR selector of this router. When set to 'true', then this router is selected as a routing MPR by the neighbor router. When set to 'false', then this router is not selected by the neighbor as a routing MPR.
.1.3.6.1.2.1.219.1.2.5.1.10,OLSRv2-MIB::olsrv2NibNeighborSetNAdvertised,INTEGER,read-only,,current,true(1):false(2),This object, N_mpr_selector (olsrv2NibNeighborSetNMprSelector), is a boolean flag, recording whether this router has elected to advertise a link to this neighbor in its TC messages.
.1.3.6.1.2.1.219.1.2.6,OLSRv2-MIB::olsrv2NibNeighborSetTableAnsn,Unsigned32,read-only,,current,,Advertised Neighbor Sequence Number (ANSN), is a variable, whose value is included in TC messages to indicate the freshness of the information transmitted.
.1.3.6.1.2.1.219.1.2.7,OLSRv2-MIB::olsrv2TibAdRemoteRouterSetTable,,not-accessible,,current,,A router's Advertising Remote Router Set records information describing each remote router in the network that transmits TC messages.
.1.3.6.1.2.1.219.1.2.7.1,OLSRv2-MIB::olsrv2TibAdRemoteRouterSetEntry,,not-accessible,olsrv2TibAdRemoteRouterSetIpAddrType:olsrv2TibAdRemoteRouterSetIpAddr,current,,A router's Advertised Neighbor Set Table entry consists of Advertising Remote Router Tuples: (AR_orig_addr (olsrv2TibAdRemoteRouterSetIpAddrType, olsrv2TibAdRemoteRouterSetIpAddr), AR_seq_number (olsrv2TibAdRemoteRouterSetMaxSeqNo), AR_time (olsrv2TibAdRemoteRouterSetExpireTime). Addresses associated with this router are found in the NHDP-MIB module's nhdpDiscIfSetTable. OLSRv2 (RFC 7181) defines the rules for managing entries within this table, e.g., populating and purging entries. Specific instructions for the olsrv2TibAdRemoteRouterSetEntry(s) are found in Section 10.1 and Section 17 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.2.7.1.1,OLSRv2-MIB::olsrv2TibAdRemoteRouterSetIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibAdRemoteRouterSetIpAddr, as defined in the InetAddress MIB module (RFC4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.7.1.2,OLSRv2-MIB::olsrv2TibAdRemoteRouterSetIpAddr,OCTET,not-accessible,,current,,This is the originator address of a received TC message.
.1.3.6.1.2.1.219.1.2.7.1.3,OLSRv2-MIB::olsrv2TibAdRemoteRouterSetMaxSeqNo,Unsigned32,read-only,,current,,This is the greatest Advertised Neighbor Sequence Number (ANSN) in any TC message received that originated from the router with originator address olsrv2TibAdRemoteRouterSetIpAddr. Sequence numbers are used in the OLSRv2 protocol for the purpose of discarding 'old' information, i.e., messages received out of order. However, with a limited number of bits for representing sequence numbers, wraparound (that the sequence number is incremented from the maximum possible value to zero) will occur. To prevent this from interfering with the operation of this protocol, OLSRv2 implementations observe the following when determining the ordering of sequence numbers. In OLSRv2, MAXVALUE designates one more than the largest possible value for a sequence number. For a 16-bit sequence number, MAXVALUE is 65536. The sequence number S1 is said to be 'greater than' the sequence number S2 if: o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR o S2 > S1 AND S2 - S1 > MAXVALUE/2 When sequence numbers S1 and S2 differ by MAXVALUE/2, their ordering cannot be determined. In this case, which should not occur, either ordering may be assumed. Thus, when comparing two messages, it is possible - even in the presence of wraparound - to determine which message contains the most recent information.
.1.3.6.1.2.1.219.1.2.7.1.4,OLSRv2-MIB::olsrv2TibAdRemoteRouterSetExpireTime,TimeTicks,read-only,,current,,olsrv2TibAdRemoteRouterSetExpireTime specifies the value of sysUptime when this entry SHOULD expire and be removed from the olsrv2TibAdRemoteRouterSetTable.
.1.3.6.1.2.1.219.1.2.8,OLSRv2-MIB::olsrv2TibRouterTopologySetTable,,not-accessible,,current,,A router's Router Topology Set records topology information about the network.
.1.3.6.1.2.1.219.1.2.8.1,OLSRv2-MIB::olsrv2TibRouterTopologySetEntry,,not-accessible,olsrv2TibRouterTopologySetFromOrigIpAddrType:olsrv2TibRouterTopologySetFromOrigIpAddr:olsrv2TibRouterTopologySetToOrigIpAddrType:olsrv2TibRouterTopologySetToOrigIpAddr,current,,It consists of Router Topology Tuples: (TR_from_orig_addr (olsrv2TibRouterTopologySetFromOrigIpAddrType, olsrv2TibRouterTopologySetFromOrigIpAddr), TR_to_orig_addr (olsrv2TibRouterTopologySetToOrigIpAddrType, olsrv2TibRouterTopologySetToOrigIpAddr), TR_seq_number (olsrv2TibRouterTopologySetSeqNo), TR_metric (olsrv2TibRouterTopologySetMetricValue), TR_time (olsrv2TibRouterTopologySetExpireTime)). OLSRv2 (RFC 7181) defines the rules for managing entries within this table, e.g., populating and purging entries. Specific instructions for the olsrv2TibRouterTopologySetEntry(s) are found in Section 10.2 and Section 17 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.2.8.1.1,OLSRv2-MIB::olsrv2TibRouterTopologySetFromOrigIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRouterTopologySetFromOrigIpAddr, as defined in the InetAddress MIB module (RFC4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.8.1.2,OLSRv2-MIB::olsrv2TibRouterTopologySetFromOrigIpAddr,OCTET,not-accessible,,current,,This is the originator address of a router that can reach the router with originator address TR_to_orig_addr in one hop.
.1.3.6.1.2.1.219.1.2.8.1.3,OLSRv2-MIB::olsrv2TibRouterTopologySetToOrigIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRouterTopologySetToOrigIpAddr, as defined in the InetAddress MIB module (RFC4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.8.1.4,OLSRv2-MIB::olsrv2TibRouterTopologySetToOrigIpAddr,OCTET,not-accessible,,current,,This is the originator address of a router that can be reached by the router with originator address TR_to_orig_addr in one hop.
.1.3.6.1.2.1.219.1.2.8.1.5,OLSRv2-MIB::olsrv2TibRouterTopologySetSeqNo,Unsigned32,read-only,,current,,This is the greatest Advertised Neighbor Sequence Number (ANSN) in any TC message received that originated from the router with originator address TR_from_orig_addr, i.e., that contributed to the information contained in this Tuple and that is defined by the objects: (olsrv2TibRouterTopologySetFromOrigIpAddrType, olsrv2TibRouterTopologySetFromOrigIpAddr). Sequence numbers are used in the OLSRv2 protocol for the purpose of discarding 'old' information, i.e., messages received out of order. However, with a limited number of bits for representing sequence numbers, wraparound (that the sequence number is incremented from the maximum possible value to zero) will occur. To prevent this from interfering with the operation of this protocol, OLSRv2 implementations observe the following when determining the ordering of sequence numbers. In OLSRv2, MAXVALUE designates one more than the largest possible value for a sequence number. For a 16-bit sequence number, MAXVALUE is 65536. The sequence number S1 is said to be 'greater than' the sequence number S2 if: o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR o S2 > S1 AND S2 - S1 > MAXVALUE/2 When sequence numbers S1 and S2 differ by MAXVALUE/2, their ordering cannot be determined. In this case, which should not occur, either ordering may be assumed. Thus, when comparing two messages, it is possible - even in the presence of wraparound - to determine which message contains the most recent information.
.1.3.6.1.2.1.219.1.2.8.1.6,OLSRv2-MIB::olsrv2TibRouterTopologySetMetricValue,Unsigned32,read-only,,current,,This is the neighbor metric from the router with originator address TR_from_orig_addr (olsrv2TibRouterTopologySetFromOrigIpAddrType, olsrv2TibRouterTopologySetFromOrigIpAddr) to the router with originator address TR_to_orig_addr (olsrv2TibRouterTopologySetToOrigIpAddrType, olsrv2TibRouterTopologySetToOrigIpAddr).
.1.3.6.1.2.1.219.1.2.8.1.7,OLSRv2-MIB::olsrv2TibRouterTopologySetExpireTime,TimeTicks,read-only,,current,,olsrv2TibRouterTopologySetExpireTime specifies the value of sysUptime when this entry SHOULD expire and be removed from the olsrv2TibRouterTopologySetTable.
.1.3.6.1.2.1.219.1.2.9,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetTable,,not-accessible,,current,,A router's Routable Address Topology Set records topology information about the routable addresses within the MANET, including via which routers they may be reached.
.1.3.6.1.2.1.219.1.2.9.1,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetEntry,,not-accessible,olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType:olsrv2TibRoutableAddressTopologySetFromOrigIpAddr:olsrv2TibRoutableAddressTopologySetDestIpAddrType:olsrv2TibRoutableAddressTopologySetDestIpAddr,current,,It consists of Router Topology Tuples: (TA_from_orig_addr (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType olsrv2TibRoutableAddressTopologySetFromOrigIpAddr), TA_dest_addr (olsrv2TibRoutableAddressTopologySetFromDestIpAddrType olsrv2TibRoutableAddressTopologySetFromDestIpAddr), TA_seq_number (olsrv2TibRoutableAddressTopologySetSeqNo) TA_metric (olsrv2TibRoutableAddressTopologySetMetricValue) TA_time (olsrv2TibRoutableAddressTopologySetExpireTime) ) OLSRv2 (RFC 7181) defines the rules for managing entries within this table, e.g., populating and purging entries. Specific instructions for the olsrv2TibRoutableAddressTopologySetEntry(s) are found in Section 10.3 and Section 17 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.2.9.1.1,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRoutableAddressTopologySetFromOrigIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.9.1.2,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetFromOrigIpAddr,OCTET,not-accessible,,current,,This is the originator address of a router that can reach the router with routable address TA_dest_addr in one hop.
.1.3.6.1.2.1.219.1.2.9.1.3,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetDestIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRouterTopologySetToOrigIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.9.1.4,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetDestIpAddr,OCTET,not-accessible,,current,,This is a routable address of a router that can be reached by the router with originator address TA_from_orig_addr in one hop. The TA_from_orig_addr is defined by the tuple (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType olsrv2TibRoutableAddressTopologySetFromOrigIpAddr).
.1.3.6.1.2.1.219.1.2.9.1.5,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetSeqNo,Unsigned32,read-only,,current,,This is the greatest Advertised Neighbor Sequence Number (ANSN) in any TC message received that originated from the router with originator address TA_from_orig_addr, i.e., that contributed to the information contained in this Tuple. The TA_from_orig_addr is defined by the tuple (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType olsrv2TibRoutableAddressTopologySetFromOrigIpAddr).
.1.3.6.1.2.1.219.1.2.9.1.6,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetMetricValue,Unsigned32,read-only,,current,,This is the neighbor metric from the router with originator address TA_from_orig_addr (defined by the tuple (olsrv2TibRoutableAddressTopologySetFromOrigIpAddrType olsrv2TibRoutableAddressTopologySetFromOrigIpAddr)) to the router with OLSRv2 interface address TA_dest_addr (defined by the tuple (olsrv2TibRoutableAddressTopologySetFromDestIpAddrType olsrv2TibRoutableAddressTopologySetFromDestIpAddr)).
.1.3.6.1.2.1.219.1.2.9.1.7,OLSRv2-MIB::olsrv2TibRoutableAddressTopologySetExpireTime,TimeTicks,read-only,,current,,olsrv2TibRoutableAddressTopologySetExpireTime specifies the value of sysUptime when this entry SHOULD expire and be removed from the olsrv2TibRoutableAddressTopologySetTable.
.1.3.6.1.2.1.219.1.2.10,OLSRv2-MIB::olsrv2TibAttNetworksSetTable,,not-accessible,,current,,A router's Attached Network Set records information about networks (which may be outside the MANET) attached to other routers and their routable addresses.
.1.3.6.1.2.1.219.1.2.10.1,OLSRv2-MIB::olsrv2TibAttNetworksSetEntry,,not-accessible,olsrv2TibAttNetworksSetOrigIpAddrType:olsrv2TibAttNetworksSetOrigIpAddr:olsrv2TibAttNetworksSetNetIpAddrType:olsrv2TibAttNetworksSetNetIpAddr:olsrv2TibAttNetworksSetNetIpAddrPrefixLen,current,,It consists of Attached Network Tuples: (AN_orig_addr (olsrv2TibAttNetworksSetOrigIpAddrType, olsrv2TibAttNetworksSetOrigIpAddr), AN_net_addr (olsrv2TibAttNetworksSetNetIpAddrType, olsrv2TibAttNetworksSetNetIpAddr, olsrv2TibAttNetworksSetNetIpAddrPrefixLen), AN_seq_number (olsrv2TibAttNetworksSetSeqNo), AN_dist (olsrv2TibAttNetworksSetDist), AN_metric (olsrv2TibAttNetworksSetMetricValue), AN_time (olsrv2TibAttNetworksSetExpireTime) ) OLSRv2 (RFC 7181) defines the rules for managing entries within this table, e.g., populating and purging entries. Specific instructions for the olsrv2TibRoutableAddressTopologySetEntry(s) are found in Section 10.4 and Section 17 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.2.10.1.1,OLSRv2-MIB::olsrv2TibAttNetworksSetOrigIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibAttNetworksSetOrigIpAddr, as defined in the InetAddress MIB module (RFC4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.10.1.2,OLSRv2-MIB::olsrv2TibAttNetworksSetOrigIpAddr,OCTET,not-accessible,,current,,This is the originator address, of type olsrv2TibAttNetworksSetOrigIpAddrType, of a router that can act as gateway to the network with address AN_net_addr. The AN_net_addr is defined by the tuple (olsrv2TibAttNetworksSetNetIpAddrType, olsrv2TibAttNetworksSetNetIpAddr, olsrv2TibAttNetworksSetNetIpAddrPrefixLen).
.1.3.6.1.2.1.219.1.2.10.1.3,OLSRv2-MIB::olsrv2TibAttNetworksSetNetIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibAttNetworksSetNetIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.10.1.4,OLSRv2-MIB::olsrv2TibAttNetworksSetNetIpAddr,OCTET,not-accessible,,current,,This is the network address, of type olsrv2TibAttNetworksSetNetIpAddrType, of an attached network, that may be reached via the router with originator address AN_orig_addr. The AN_orig_addr is defined by the tuple (olsrv2TibAttNetworksSetOrigIpAddrType, olsrv2TibAttNetworksSetOrigIpAddr).
.1.3.6.1.2.1.219.1.2.10.1.5,OLSRv2-MIB::olsrv2TibAttNetworksSetNetIpAddrPrefixLen,Unsigned32,not-accessible,,current,,Indicates the number of leading one bits that form the mask to be logically ANDed with the destination address before being compared to the value in the olsrv2TibAttNetworksSetNetIpAddr field.
.1.3.6.1.2.1.219.1.2.10.1.6,OLSRv2-MIB::olsrv2TibAttNetworksSetSeqNo,Unsigned32,read-only,,current,,This is the greatest Advertised Neighbor Sequence Number (ANSN) in any TC message received that originated from the router with originator address AN_orig_addr (i.e., that contributed to the information contained in this Tuple). The AN_orig_addr is defined by the tuple (olsrv2TibAttNetworksSetOrigIpAddrType, olsrv2TibAttNetworksSetOrigIpAddr). Sequence numbers are used in the OLSRv2 protocol for the purpose of discarding 'old' information, i.e., messages received out of order. However, with a limited number of bits for representing sequence numbers, wraparound (that the sequence number is incremented from the maximum possible value to zero) will occur. To prevent this from interfering with the operation of this protocol, the following MUST be observed when determining the ordering of sequence numbers. The term MAXVALUE designates in the following one more than the largest possible value for a sequence number. For a 16-bit sequence number (as are those defined in this specification), MAXVALUE is 65536. The sequence number S1 is said to be 'greater than' the sequence number S2 if: o S1 > S2 AND S1 - S2 < MAXVALUE/2 OR o S2 > S1 AND S2 - S1 > MAXVALUE/2 When sequence numbers S1 and S2 differ by MAXVALUE/2, their ordering cannot be determined. In this case, which should not occur, either ordering may be assumed. Thus, when comparing two messages, it is possible - even in the presence of wraparound - to determine which message contains the most recent information.
.1.3.6.1.2.1.219.1.2.10.1.7,OLSRv2-MIB::olsrv2TibAttNetworksSetDist,Unsigned32,read-only,,current,,The number of hops to the network with address AN_net_addr from the router with originator address AN_orig_addr. The AN_orig_addr is defined by the tuple (olsrv2TibAttNetworksSetOrigIpAddrType, olsrv2TibAttNetworksSetOrigIpAddr).
.1.3.6.1.2.1.219.1.2.10.1.9,OLSRv2-MIB::olsrv2TibAttNetworksSetMetricValue,Unsigned32,read-only,,current,,The metric of the link from the router with originator address AN_orig_addr to the attached network with address AN_net_addr. The AN_net_addr is defined by the tuple (olsrv2TibAttNetworksSetNetIpAddrType, olsrv2TibAttNetworksSetNetIpAddr, olsrv2TibAttNetworksSetNetIpAddrPrefixLen).
.1.3.6.1.2.1.219.1.2.10.1.10,OLSRv2-MIB::olsrv2TibAttNetworksSetExpireTime,TimeTicks,read-only,,current,,olsrv2TibAttNetworksSetExpireTime specifies the value of sysUptime when this entry SHOULD expire and be removed from the olsrv2TibAttNetworksSetTable.
.1.3.6.1.2.1.219.1.2.11,OLSRv2-MIB::olsrv2TibRoutingSetTable,,not-accessible,,current,,A router's Routing Set records the first hop along a selected path to each destination for which any such path is known.
.1.3.6.1.2.1.219.1.2.11.1,OLSRv2-MIB::olsrv2TibRoutingSetEntry,,not-accessible,olsrv2TibRoutingSetDestIpAddrType:olsrv2TibRoutingSetDestIpAddr:olsrv2TibRoutingSetDestIpAddrPrefixLen,current,,It consists of Routing Tuples: (R_dest_addr, R_next_iface_addr, R_local_iface_addr, R_dist, R_metric)
.1.3.6.1.2.1.219.1.2.11.1.1,OLSRv2-MIB::olsrv2TibRoutingSetDestIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRoutingSetDestIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.11.1.2,OLSRv2-MIB::olsrv2TibRoutingSetDestIpAddr,OCTET,not-accessible,,current,,This is the address of the destination, either the address of an interface of a destination router or the network address of an attached network.
.1.3.6.1.2.1.219.1.2.11.1.3,OLSRv2-MIB::olsrv2TibRoutingSetDestIpAddrPrefixLen,Unsigned32,not-accessible,,current,,Indicates the number of leading one bits that form the mask to be logically ANDed with the destination address before being compared to the value in the olsrv2TibRoutingSetDestIpAddr field. Note: This definition needs to be consistent with the current forwarding table MIB module description. Specifically, it SHOULD allow for longest prefix matching of network addresses.
.1.3.6.1.2.1.219.1.2.11.1.4,OLSRv2-MIB::olsrv2TibRoutingSetNextIfIpAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRoutingSetNextIfIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.11.1.5,OLSRv2-MIB::olsrv2TibRoutingSetNextIfIpAddr,OCTET,read-only,,current,,This object is the OLSRv2 interface address of the next hop on the selected path to the destination.
.1.3.6.1.2.1.219.1.2.11.1.6,OLSRv2-MIB::olsrv2TibRoutingSetLocalIfIpAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2),The type of the olsrv2TibRoutingSetLocalIfIpAddr and olsrv2TibRoutingSetNextIfIpAddr, as defined in the InetAddress MIB module (RFC 4001). Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.2.1.219.1.2.11.1.7,OLSRv2-MIB::olsrv2TibRoutingSetLocalIfIpAddr,OCTET,read-only,,current,,This object is the address of the local OLSRv2 interface over which a packet must be sent to reach the destination by the selected path.
.1.3.6.1.2.1.219.1.2.11.1.8,OLSRv2-MIB::olsrv2TibRoutingSetDist,Unsigned32,read-only,,current,,This object is the number of hops on the selected path to the destination.
.1.3.6.1.2.1.219.1.2.11.1.9,OLSRv2-MIB::olsrv2TibRoutingSetMetricValue,Unsigned32,read-only,,current,,This object is the metric of the route to the destination with address R_dest_addr. The maximum value of this object can be 256 times MAXIMUM_METRIC, as represented in Olsrv2MetricValueCompressedFormTC, i.e., 4294901760.
.1.3.6.1.2.1.219.1.3,OLSRv2-MIB::olsrv2PerformanceObjGrp,,,,,,
.1.3.6.1.2.1.219.1.3.1,OLSRv2-MIB::olsrv2InterfacePerfTable,,not-accessible,,current,,This table summarizes performance objects that are measured per each active local OLSRv2 interface. If the olsrv2InterfaceAdminStatus of the interface changes to 'disabled', then the row associated with this interface SHOULD be removed from this table.
.1.3.6.1.2.1.219.1.3.1.1,OLSRv2-MIB::olsrv2InterfacePerfEntry,,not-accessible,,current,,A single entry contains performance counters for each active local OLSRv2 interface.
.1.3.6.1.2.1.219.1.3.1.1.1,OLSRv2-MIB::olsrv2IfTcMessageXmits,Counter32,read-only,,current,,A counter is incremented each time a TC message has been transmitted on that interface.
.1.3.6.1.2.1.219.1.3.1.1.2,OLSRv2-MIB::olsrv2IfTcMessageRecvd,Counter32,read-only,,current,,A counter is incremented each time a TC message has been received on that interface. This excludes all messages that are ignored due to OLSRv2 protocol procedures, such as messages considered invalid for processing by this router, as defined in Section 16.3.1 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.3.1.1.3,OLSRv2-MIB::olsrv2IfTcMessageXmitAccumulatedSize,Counter64,read-only,,current,,A counter is incremented by the number of octets in a TC message each time a TC message has been sent.
.1.3.6.1.2.1.219.1.3.1.1.4,OLSRv2-MIB::olsrv2IfTcMessageRecvdAccumulatedSize,Counter64,read-only,,current,,A counter is incremented by the number of octets in a TC message each time a TC message has been received. This excludes all messages that are ignored due to OLSRv2 protocol procedures, such as messages considered invalid for processing by this router, as defined in Section 16.3.1 of OLSRv2 (RFC 7181).
.1.3.6.1.2.1.219.1.3.1.1.5,OLSRv2-MIB::olsrv2IfTcMessageTriggeredXmits,Counter32,read-only,,current,,A counter is incremented each time a triggered TC message has been sent.
.1.3.6.1.2.1.219.1.3.1.1.6,OLSRv2-MIB::olsrv2IfTcMessagePeriodicXmits,Counter32,read-only,,current,,A counter is incremented each time a periodic TC message has been sent.
.1.3.6.1.2.1.219.1.3.1.1.7,OLSRv2-MIB::olsrv2IfTcMessageForwardedXmits,Counter32,read-only,,current,,A counter is incremented each time a TC message has been forwarded.
.1.3.6.1.2.1.219.1.3.1.1.8,OLSRv2-MIB::olsrv2IfTcMessageXmitAccumulatedMPRSelectorCount,Counter32,read-only,,current,,A counter is incremented by the number of advertised MPR selectors in a TC each time a TC message has been sent.
.1.3.6.1.2.1.219.1.3.2,OLSRv2-MIB::olsrv2RoutingSetRecalculationCount,Counter32,read-only,,current,,This counter increments each time the Routing Set has been recalculated.
.1.3.6.1.2.1.219.1.3.3,OLSRv2-MIB::olsrv2MPRSetRecalculationCount,Counter32,read-only,,current,,This counter increments each time the MPRs of this router have been recalculated for any of its interfaces.
.1.3.6.1.2.1.219.2,OLSRv2-MIB::olsrv2MIBConformance,,,,,,
.1.3.6.1.2.1.219.2.1,OLSRv2-MIB::olsrv2Compliances,,,,,,
.1.3.6.1.2.1.219.2.1.1,OLSRv2-MIB::olsrv2BasicCompliance,,,,,,The basic implementation requirements for managed network entities that implement the OLSRv2 routing process.
.1.3.6.1.2.1.219.2.1.2,OLSRv2-MIB::olsrv2FullCompliance,,,,,,The full implementation requirements for managed network entities that implement the OLSRv2 routing process.
.1.3.6.1.2.1.219.2.2,OLSRv2-MIB::olsrv2MIBGroups,,,,,,
.1.3.6.1.2.1.219.2.2.1,OLSRv2-MIB::olsrv2ConfigObjectsGroup,,,,,,Objects to permit configuration of OLSRv2. All of these SHOULD be backed by non-volatile storage.
.1.3.6.1.2.1.219.2.2.2,OLSRv2-MIB::olsrv2StateObjectsGroup,,,,,,Objects to permit monitoring of OLSRv2 state.
.1.3.6.1.2.1.219.2.2.3,OLSRv2-MIB::olsrv2PerfObjectsGroup,,,,,,Objects to support monitoring of OLSRv2 performance.
.1.3.6.1.2.1.219.2.2.4,OLSRv2-MIB::olsrv2NotificationsObjectsGroup,,,,,,Objects to support the notification types in the olsrv2NotificationsGroup. Some of these appear in notification payloads, others serve to control notification generation.
.1.3.6.1.2.1.219.2.2.5,OLSRv2-MIB::olsrv2NotificationsGroup,,,,,,Notification types to support management of OLSRv2.
.1.3.6.1.2.1.220,LISP-MIB::lispMIB,,,,,,This MIB module contains managed objects to support monitoring devices that support the Locator/ID Separation Protocol (LISP). Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.220.1,LISP-MIB::lispObjects,,,,,,
.1.3.6.1.2.1.220.1.1,LISP-MIB::lispFeaturesTable,,not-accessible,,current,,This table represents the ON/OFF status of the various LISP features that can be enabled on LISP devices.
.1.3.6.1.2.1.220.1.1.1,LISP-MIB::lispFeaturesEntry,,not-accessible,lispFeaturesInstanceID:lispFeaturesAddressFamily,current,,An entry (conceptual row) in the lispFeaturesTable.
.1.3.6.1.2.1.220.1.1.1.1,LISP-MIB::lispFeaturesInstanceID,Unsigned32,not-accessible,,current,,This represents the Instance ID of the LISP header. An Instance ID in the LISP address encoding helps uniquely identify the AFI-based address space to which a given EID belongs. Its default value is 0.
.1.3.6.1.2.1.220.1.1.1.2,LISP-MIB::lispFeaturesAddressFamily,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The IANA Address Family Number of destination address of packets that this LISP device is enabled to process.
.1.3.6.1.2.1.220.1.1.1.3,LISP-MIB::lispFeaturesItrEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of ITR role on this device. If this object is true, then the ITR feature is enabled.
.1.3.6.1.2.1.220.1.1.1.4,LISP-MIB::lispFeaturesEtrEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of ETR role on this device. If this object is true, then the ETR feature is enabled.
.1.3.6.1.2.1.220.1.1.1.5,LISP-MIB::lispFeaturesProxyItrEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of Proxy-ITR role on this device. If this object is true, then the Proxy-ITR feature is enabled.
.1.3.6.1.2.1.220.1.1.1.6,LISP-MIB::lispFeaturesProxyEtrEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of Proxy-ETR role on this device. If this object is true, then the Proxy-ETR feature is enabled.
.1.3.6.1.2.1.220.1.1.1.7,LISP-MIB::lispFeaturesMapServerEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of Map Server role on this device. If this object is true, then the Map-Server feature is enabled.
.1.3.6.1.2.1.220.1.1.1.8,LISP-MIB::lispFeaturesMapResolverEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of Map Resolver role on this device. If this object is true, then Map-Resolver feature is enabled.
.1.3.6.1.2.1.220.1.1.1.9,LISP-MIB::lispFeaturesMapCacheSize,Unsigned32,read-only,,current,,Size of EID-to-RLOC map-cache on this device.
.1.3.6.1.2.1.220.1.1.1.10,LISP-MIB::lispFeaturesMapCacheLimit,Unsigned32,read-only,,current,,Maximum permissible entries in EID-to-RLOC map-cache on this device.
.1.3.6.1.2.1.220.1.1.1.11,LISP-MIB::lispFeaturesEtrMapCacheTtl,Unsigned32,read-only,,current,,The stored Record TTL of the EID-to-RLOC map record in the map-cache.
.1.3.6.1.2.1.220.1.1.1.12,LISP-MIB::lispFeaturesRlocProbeEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of RLOC-Probing feature on this device. If this object is true, then this feature is enabled.
.1.3.6.1.2.1.220.1.1.1.13,LISP-MIB::lispFeaturesEtrAcceptMapDataEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of accepting piggybacked mapping data received in a map-request on this device. If this object is true, then this device accepts piggybacked mapping data.
.1.3.6.1.2.1.220.1.1.1.14,LISP-MIB::lispFeaturesEtrAcceptMapDataVerifyEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates the status of verifying accepted piggybacked mapping data received in a map-request on this device. If this object is true, then this device verifies accepted piggybacked mapping data.
.1.3.6.1.2.1.220.1.1.1.15,LISP-MIB::lispFeaturesRouterTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the LISP feature was enabled on this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.2,LISP-MIB::lispIidToVrfTable,,not-accessible,,current,,This table represents the mapping of a LISP Instance ID to a VRF.
.1.3.6.1.2.1.220.1.2.1,LISP-MIB::lispIidToVrfEntry,,not-accessible,lispFeaturesInstanceID,current,,An entry (conceptual row) in the lispIidToVrfTable.
.1.3.6.1.2.1.220.1.2.1.1,LISP-MIB::lispIidToVrfName,OCTET,read-only,,current,,The identifier for each VPN that is mapped to the given LISP Instance ID.
.1.3.6.1.2.1.220.1.3,LISP-MIB::lispGlobalStatsTable,,not-accessible,,current,,This table provides global statistics for a given Instance ID per address family on a LISP device.
.1.3.6.1.2.1.220.1.3.1,LISP-MIB::lispGlobalStatsEntry,,not-accessible,lispFeaturesInstanceID:lispFeaturesAddressFamily,current,,An entry (conceptual row) in the lispGlobalStatsTable.
.1.3.6.1.2.1.220.1.3.1.1,LISP-MIB::lispGlobalStatsMapRequestsIn,Counter64,read-only,,current,,Total number of map requests received by this device for any EID-Prefix of the given address family and Instance ID. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispFeaturesRouterTimeStamp.
.1.3.6.1.2.1.220.1.3.1.2,LISP-MIB::lispGlobalStatsMapRequestsOut,Counter64,read-only,,current,,Total number of map requests sent by this device for any EID-Prefix of the given address family and Instance ID. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispFeaturesRouterTimeStamp.
.1.3.6.1.2.1.220.1.3.1.3,LISP-MIB::lispGlobalStatsMapRepliesIn,Counter64,read-only,,current,,Total number of map replies received by this device for any EID-Prefix of the given address family and Instance ID. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispFeaturesRouterTimeStamp.
.1.3.6.1.2.1.220.1.3.1.4,LISP-MIB::lispGlobalStatsMapRepliesOut,Counter64,read-only,,current,,Total number of map replies sent by this device for any EID prefix of the given address family and Instance ID. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispFeaturesRouterTimeStamp.
.1.3.6.1.2.1.220.1.3.1.5,LISP-MIB::lispGlobalStatsMapRegistersIn,Counter64,read-only,,current,,Total number of map registers received by this device for any EID-Prefix of the given address family and Instance ID. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispFeaturesRouterTimeStamp.
.1.3.6.1.2.1.220.1.3.1.6,LISP-MIB::lispGlobalStatsMapRegistersOut,Counter64,read-only,,current,,Total number of map registers sent by this device for any EID-Prefix of the given address family and Instance ID. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispFeaturesRouterTimeStamp.
.1.3.6.1.2.1.220.1.4,LISP-MIB::lispMappingDatabaseTable,,not-accessible,,current,,This table represents the EID-to-RLOC mapping database that contains the EID-Prefix to RLOC mappings configured on an ETR. This table represents all such mappings for the given LISP site to which this device belongs.
.1.3.6.1.2.1.220.1.4.1,LISP-MIB::lispMappingDatabaseEntry,,not-accessible,lispMappingDatabaseEidLength:lispMappingDatabaseEid,current,,An entry (conceptual row) in lispMappingDatabaseTable.
.1.3.6.1.2.1.220.1.4.1.1,LISP-MIB::lispMappingDatabaseEidLength,Integer32,not-accessible,,current,,This object gives the octet-length of lispMappingDatabaseEid.
.1.3.6.1.2.1.220.1.4.1.2,LISP-MIB::lispMappingDatabaseEid,OCTET,not-accessible,,current,,The EID-Prefix of the mapping database.
.1.3.6.1.2.1.220.1.4.1.3,LISP-MIB::lispMappingDatabaseLsb,Unsigned32,read-only,,current,,The locator status bits for this EID-Prefix.
.1.3.6.1.2.1.220.1.4.1.4,LISP-MIB::lispMappingDatabaseEidPartitioned,INTEGER,read-only,,current,true(1):false(2),Indicates if this device is partitioned from the site that contains this EID-Prefix. If this object is true, then it means this device is partitioned from the site.
.1.3.6.1.2.1.220.1.4.1.5,LISP-MIB::lispMappingDatabaseTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the EID Prefix information represented by this mapping database entry was configured on this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.4.1.6,LISP-MIB::lispMappingDatabaseDecapOctets,Counter64,read-only,,current,,The number of octets, after decapsulation, of LISP packets that were decapsulated by this device addressed to a host within this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispMappingDatabaseTimeStamp.
.1.3.6.1.2.1.220.1.4.1.7,LISP-MIB::lispMappingDatabaseDecapPackets,Counter64,read-only,,current,,The number of LISP packets that were decapsulated by this device addressed to a host within this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispMappingDatabaseTimeStamp.
.1.3.6.1.2.1.220.1.4.1.8,LISP-MIB::lispMappingDatabaseEncapOctets,Counter64,read-only,,current,,The number of octets, before encapsulation, of LISP packets that were encapsulated by this device, whose inner header source address matched this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispMappingDatabaseTimeStamp.
.1.3.6.1.2.1.220.1.4.1.9,LISP-MIB::lispMappingDatabaseEncapPackets,Counter64,read-only,,current,,The number of LISP packets that were encapsulated by this device whose inner header source address matched this EID prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of LISP features being removed, which can be detected by observing the value of lispMappingDatabaseTimeStamp.
.1.3.6.1.2.1.220.1.5,LISP-MIB::lispMappingDatabaseLocatorTable,,not-accessible,,current,,This table represents the set of routing locators per EID prefix contained in the EID-to-RLOC database configured on this ETR.
.1.3.6.1.2.1.220.1.5.1,LISP-MIB::lispMappingDatabaseLocatorEntry,,not-accessible,lispMappingDatabaseEidLength:lispMappingDatabaseEid:lispMappingDatabaseLocatorRlocLength:lispMappingDatabaseLocatorRloc,current,,An entry (conceptual row) in the lispMappingDatabaseLocatorTable.
.1.3.6.1.2.1.220.1.5.1.1,LISP-MIB::lispMappingDatabaseLocatorRlocLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispMappingDatabaseLocatorRloc.
.1.3.6.1.2.1.220.1.5.1.2,LISP-MIB::lispMappingDatabaseLocatorRloc,OCTET,not-accessible,,current,,This object is a locator for the given EID-Prefix in the mapping database.
.1.3.6.1.2.1.220.1.5.1.3,LISP-MIB::lispMappingDatabaseLocatorRlocPriority,Integer32,read-only,,current,,The unicast priority of the RLOC.
.1.3.6.1.2.1.220.1.5.1.4,LISP-MIB::lispMappingDatabaseLocatorRlocWeight,Integer32,read-only,,current,,The unicast weight of the RLOC.
.1.3.6.1.2.1.220.1.5.1.5,LISP-MIB::lispMappingDatabaseLocatorRlocMPriority,Integer32,read-only,,current,,The multicast priority of the RLOC.
.1.3.6.1.2.1.220.1.5.1.6,LISP-MIB::lispMappingDatabaseLocatorRlocMWeight,Integer32,read-only,,current,,The multicast weight of the RLOC.
.1.3.6.1.2.1.220.1.5.1.7,LISP-MIB::lispMappingDatabaseLocatorRlocState,INTEGER,read-only,,current,up(1):down(2):unreachable(3),The state of this RLOC as per this device. (1 = RLOC is up; 2 = RLOC is down; 3 = RLOC is unreachable).
.1.3.6.1.2.1.220.1.5.1.8,LISP-MIB::lispMappingDatabaseLocatorRlocLocal,INTEGER,read-only,,current,siteself(1):sitelocal(2),Indicates whether the RLOC is local to this device (or remote, meaning local to another device in the same LISP site). (1 = RLOC is an address on this device; 2 = RLOC is an address on another device).
.1.3.6.1.2.1.220.1.5.1.9,LISP-MIB::lispMappingDatabaseLocatorRlocTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the RLOC of the EID Prefix represented by this mapping database entry was configured on this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.5.1.10,LISP-MIB::lispMappingDatabaseLocatorRlocDecapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were addressed to this RLOC of the EID-Prefix and were decapsulated. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of database mappings getting reconfigured or RLOC status changes, which can be detected by observing the value of lispMappingDatabaseLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.5.1.11,LISP-MIB::lispMappingDatabaseLocatorRlocDecapPackets,Counter64,read-only,,current,,The number of LISP packets that were addressed to this RLOC of the EID-Prefix and were decapsulated. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of database mappings getting reconfigured or RLOC status changes, which can be detected by observing the value of lispMappingDatabaseLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.5.1.12,LISP-MIB::lispMappingDatabaseLocatorRlocEncapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were encapsulated by this device using this RLOC address as the source, and that were sourced by an address of this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of database mappings getting reconfigured or RLOC status changes, which can be detected by observing the value of lispMappingDatabaseLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.5.1.13,LISP-MIB::lispMappingDatabaseLocatorRlocEncapPackets,Counter64,read-only,,current,,The number of LISP packets that were encapsulated by this device using this RLOC address as the source and that were sourced by an address of this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of database mappings getting reconfigured or RLOC status changes, which can be detected by observing the value of lispMappingDatabaseLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.6,LISP-MIB::lispMapCacheTable,,not-accessible,,current,,This table represents the short-lived, on-demand table on an ITR that stores, tracks, and is responsible for timing-out and otherwise validating EID-to-RLOC mappings.
.1.3.6.1.2.1.220.1.6.1,LISP-MIB::lispMapCacheEntry,,not-accessible,lispMapCacheEidLength:lispMapCacheEid,current,,An entry (conceptual row) in the lispMapCacheTable.
.1.3.6.1.2.1.220.1.6.1.1,LISP-MIB::lispMapCacheEidLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispMapCacheEid.
.1.3.6.1.2.1.220.1.6.1.2,LISP-MIB::lispMapCacheEid,OCTET,not-accessible,,current,,The EID-Prefix in the mapping cache.
.1.3.6.1.2.1.220.1.6.1.3,LISP-MIB::lispMapCacheEidTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the EID Prefix information represented by this entry was learned by this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.6.1.4,LISP-MIB::lispMapCacheEidExpiryTime,TimeTicks,read-only,,current,,The time remaining before the ITR times-out this EID-Prefix.
.1.3.6.1.2.1.220.1.6.1.5,LISP-MIB::lispMapCacheEidState,INTEGER,read-only,,current,true(1):false(2),This object is used to indicate the activity of this EID prefix. If this object is true, then it means this EID prefix is seeing activity.
.1.3.6.1.2.1.220.1.6.1.6,LISP-MIB::lispMapCacheEidAuthoritative,INTEGER,read-only,,current,true(1):false(2),This object is used to indicate whether the EID-Prefix was installed by an authoritative map-reply. If this object is true, then it means this EID-Prefix was installed by an authoritative map-reply.
.1.3.6.1.2.1.220.1.6.1.7,LISP-MIB::lispMapCacheEidDecapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were decapsulated by this device and were sourced from a remote host within this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of cache being removed and replaced, which can be detected by observing the value of lispMapCacheEidTimeStamp.
.1.3.6.1.2.1.220.1.6.1.8,LISP-MIB::lispMapCacheEidDecapPackets,Counter64,read-only,,current,,The number of LISP packets that were decapsulated by this device and were sourced from a remote host within this EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of cache being removed and replaced, which can be detected by observing the value of lispMapCacheEidTimeStamp.
.1.3.6.1.2.1.220.1.6.1.9,LISP-MIB::lispMapCacheEidEncapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were encapsulated by this device using the given EID-Prefix in the map-cache. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of cache being removed and replaced, which can be detected by observing the value of lispMapCacheEidTimeStamp.
.1.3.6.1.2.1.220.1.6.1.10,LISP-MIB::lispMapCacheEidEncapPackets,Counter64,read-only,,current,,The number of LISP packets that were encapsulated by this device using the given EID-Prefix in the map-cache. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of cache being removed and replaced, which can be detected by observing the value of lispMapCacheEidTimeStamp.
.1.3.6.1.2.1.220.1.7,LISP-MIB::lispMapCacheLocatorTable,,not-accessible,,current,,This table represents the set of locators per EID-Prefix contained in the map-cache table of an ITR.
.1.3.6.1.2.1.220.1.7.1,LISP-MIB::lispMapCacheLocatorEntry,,not-accessible,lispMapCacheEidLength:lispMapCacheEid:lispMapCacheLocatorRlocLength:lispMapCacheLocatorRloc,current,,An entry (conceptual row) in the lispMapCacheLocatorTable.
.1.3.6.1.2.1.220.1.7.1.1,LISP-MIB::lispMapCacheLocatorRlocLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispMapCacheLocatorRloc.
.1.3.6.1.2.1.220.1.7.1.2,LISP-MIB::lispMapCacheLocatorRloc,OCTET,not-accessible,,current,,The locator for the EID-Prefix in the mapping cache.
.1.3.6.1.2.1.220.1.7.1.3,LISP-MIB::lispMapCacheLocatorRlocPriority,Integer32,read-only,,current,,The unicast priority of the RLOC for this EID-Prefix (0-255); lower is more preferred.
.1.3.6.1.2.1.220.1.7.1.4,LISP-MIB::lispMapCacheLocatorRlocWeight,Integer32,read-only,,current,,The unicast weight of the RLOC for this EID-Prefix (0 - 100) percentage.
.1.3.6.1.2.1.220.1.7.1.5,LISP-MIB::lispMapCacheLocatorRlocMPriority,Integer32,read-only,,current,,The multicast priority of the RLOC for this EID-Prefix (0-255); lower is more preferred.
.1.3.6.1.2.1.220.1.7.1.6,LISP-MIB::lispMapCacheLocatorRlocMWeight,Integer32,read-only,,current,,The multicast weight of the RLOC for this EID-Prefix (0 - 100) percentage.
.1.3.6.1.2.1.220.1.7.1.7,LISP-MIB::lispMapCacheLocatorRlocState,INTEGER,read-only,,current,up(1):down(2):unreachable(3),The state of this RLOC as per this device (1 = RLOC is up; 2 = RLOC is down; 3 = RLOC is unreachable).
.1.3.6.1.2.1.220.1.7.1.8,LISP-MIB::lispMapCacheLocatorRlocTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the RLOC of EID-Prefix information represented by this entry was learned by this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.7.1.9,LISP-MIB::lispMapCacheLocatorRlocLastPriorityChange,TimeTicks,read-only,,current,,Time elapsed since the last change of the unicast priority of the RLOC for this EID-Prefix. Note that this is independent of lispMapCacheLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.7.1.10,LISP-MIB::lispMapCacheLocatorRlocLastWeightChange,TimeTicks,read-only,,current,,Time elapsed since the last change of the unicast weight of the RLOC for this EID-Prefix. Note that this is independent of lispMapCacheLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.7.1.11,LISP-MIB::lispMapCacheLocatorRlocLastMPriorityChange,TimeTicks,read-only,,current,,Time since the last change of the multicast priority of the RLOC for this EID-Prefix.
.1.3.6.1.2.1.220.1.7.1.12,LISP-MIB::lispMapCacheLocatorRlocLastMWeightChange,TimeTicks,read-only,,current,,Time since the last change of the multicast weight of the RLOC for this EID-Prefix.
.1.3.6.1.2.1.220.1.7.1.13,LISP-MIB::lispMapCacheLocatorRlocLastStateChange,TimeTicks,read-only,,current,,Time since the last change of the up/down state of the RLOC for this EID-Prefix.
.1.3.6.1.2.1.220.1.7.1.14,LISP-MIB::lispMapCacheLocatorRlocRtt,TimeTicks,read-only,,current,,Round-trip time of RLOC probe and map-reply for this RLOC address for this prefix.
.1.3.6.1.2.1.220.1.7.1.15,LISP-MIB::lispMapCacheLocatorRlocDecapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were decapsulated by this device and were sourced from a remote host within this EID-Prefix and were encapsulated for this RLOC. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of RLOC of cache being removed and replaced, which can be detected by observing the value of lispMapCacheLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.7.1.16,LISP-MIB::lispMapCacheLocatorRlocDecapPackets,Counter64,read-only,,current,,The number of LISP packets that were decapsulated by this device and were sourced from a remote host within this EID-Prefix and were encapsulated for this RLOC. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of RLOC of cache being removed and replaced, which can be detected by observing the value of lispMapCacheLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.7.1.17,LISP-MIB::lispMapCacheLocatorRlocEncapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that matched this EID-Prefix and were encapsulated using this RLOC address. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of RLOC of cache being removed and replaced, which can be detected by observing the value of lispMapCacheLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.7.1.18,LISP-MIB::lispMapCacheLocatorRlocEncapPackets,Counter64,read-only,,current,,The number of LISP packets that matched this EID-Prefix and were encapsulated using this RLOC address. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of RLOC of cache being removed and replaced, which can be detected by observing the value of lispMapCacheLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.8,LISP-MIB::lispConfiguredLocatorTable,,not-accessible,,current,,This table represents the set of routing locators configured on this device. Note that the addresses configured by Proxy-ITR are treated as routing locators and therefore can be part of this table.
.1.3.6.1.2.1.220.1.8.1,LISP-MIB::lispConfiguredLocatorEntry,,not-accessible,lispConfiguredLocatorRlocLength:lispConfiguredLocatorRloc,current,,An entry (conceptual row) in the lispConfiguredLocatorTable.
.1.3.6.1.2.1.220.1.8.1.1,LISP-MIB::lispConfiguredLocatorRlocLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispConfiguredLocatorRloc.
.1.3.6.1.2.1.220.1.8.1.2,LISP-MIB::lispConfiguredLocatorRloc,OCTET,not-accessible,,current,,This object is an RLOC address configured on this device. It can be an RLOC that is local to this device or can be an RLOC that belongs to another ETR within the same site. Proxy-ITR address is treated as an RLOC.
.1.3.6.1.2.1.220.1.8.1.3,LISP-MIB::lispConfiguredLocatorRlocState,INTEGER,read-only,,current,up(1):down(2):unreachable(3),The state of this RLOC as per this device. (1 = RLOC is up; 2 = RLOC is down; 3 = RLOC is unreachable).
.1.3.6.1.2.1.220.1.8.1.4,LISP-MIB::lispConfiguredLocatorRlocLocal,INTEGER,read-only,,current,siteself(1):sitelocal(2),Indicates whether the RLOC is local to this device (or remote, meaning local to another device in the same LISP site). (1 = RLOC is an address on this device; 2 = RLOC is an address on another device).
.1.3.6.1.2.1.220.1.8.1.5,LISP-MIB::lispConfiguredLocatorRlocTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the RLOC was configured on this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.8.1.6,LISP-MIB::lispConfiguredLocatorRlocDecapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were addressed to this RLOC and were decapsulated. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of configured RLOC being removed and replaced, which can be detected by observing the value of lispConfiguredLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.8.1.7,LISP-MIB::lispConfiguredLocatorRlocDecapPackets,Counter64,read-only,,current,,The number of LISP packets that were addressed to this RLOC and were decapsulated. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of configured RLOC being removed and replaced, which can be detected by observing the value of lispConfiguredLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.8.1.8,LISP-MIB::lispConfiguredLocatorRlocEncapOctets,Counter64,read-only,,current,,The number of octets of LISP packets that were encapsulated by this device using this RLOC address as the source. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of configured RLOC being removed and replaced, which can be detected by observing the value of lispConfiguredLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.8.1.9,LISP-MIB::lispConfiguredLocatorRlocEncapPackets,Counter64,read-only,,current,,The number of LISP packets that were encapsulated by this device using this RLOC address as the source. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of configured RLOC being removed and replaced, which can be detected by observing the value of lispConfiguredLocatorRlocTimeStamp.
.1.3.6.1.2.1.220.1.9,LISP-MIB::lispEidRegistrationTable,,not-accessible,,current,,This table provides the properties of each LISP EID-Prefix that is registered with this device when configured to be a Map-Server.
.1.3.6.1.2.1.220.1.9.1,LISP-MIB::lispEidRegistrationEntry,,not-accessible,lispEidRegistrationEidLength:lispEidRegistrationEid,current,,An entry (conceptual row) in the lispEidRegistrationTable.
.1.3.6.1.2.1.220.1.9.1.1,LISP-MIB::lispEidRegistrationEidLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispEidRegistrationEid.
.1.3.6.1.2.1.220.1.9.1.2,LISP-MIB::lispEidRegistrationEid,OCTET,not-accessible,,current,,The EID-Prefix that is being registered.
.1.3.6.1.2.1.220.1.9.1.3,LISP-MIB::lispEidRegistrationSiteName,OCTET,read-only,,current,,Site name used by a Map-Server to distinguish different LISP sites that are registering with it.
.1.3.6.1.2.1.220.1.9.1.4,LISP-MIB::lispEidRegistrationSiteDescription,OCTET,read-only,,current,,Description for a site name used by a Map-Server. The EID prefix that is being registered belongs to this site.
.1.3.6.1.2.1.220.1.9.1.5,LISP-MIB::lispEidRegistrationIsRegistered,INTEGER,read-only,,current,true(1):false(2),Indicates the registration status of the given EID-Prefix. If this object is true, then it means the EID-Prefix is registered. The value false implies the EID-Prefix is not registered with the Map Server. There are multiple scenarios when this could happen like authentication failures, routing problems, misconfigs to name a few.
.1.3.6.1.2.1.220.1.9.1.6,LISP-MIB::lispEidRegistrationFirstTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the first valid register message for the EID Prefix information represented by this entry was received by this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.9.1.7,LISP-MIB::lispEidRegistrationLastTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the last valid register message for the EID Prefix information represented by this entry was received by this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.9.1.8,LISP-MIB::lispEidRegistrationLastRegisterSenderLength,Integer32,read-only,,current,,This object is used to get the octet-length of lispEidRegistrationLastRegisterSender, the next object.
.1.3.6.1.2.1.220.1.9.1.9,LISP-MIB::lispEidRegistrationLastRegisterSender,OCTET,read-only,,current,,Source address of the last valid register message for the given EID-Prefix that was received by this device.
.1.3.6.1.2.1.220.1.9.1.10,LISP-MIB::lispEidRegistrationAuthenticationErrors,Counter64,read-only,,current,,Count of total authentication errors of map-registers received for the given EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of site config changes, which can be detected by observing the value of lispEidRegistrationFirstTimeStamp.
.1.3.6.1.2.1.220.1.9.1.11,LISP-MIB::lispEidRegistrationRlocsMismatch,Counter64,read-only,,current,,Count of total map-registers received that had at least one RLOC that was not in the allowed list of RLOCs for the given EID-Prefix. Discontinuities in this monotonically increasing value occur at reinitialization of the management system. Discontinuities can also occur as a result of site config changes, which can be detected by observing the value of lispEidRegistrationFirstTimeStamp.
.1.3.6.1.2.1.220.1.10,LISP-MIB::lispEidRegistrationEtrTable,,not-accessible,,current,,This table provides the properties of ETRs that register the given EID-Prefix with this device when configured to be a Map-Server.
.1.3.6.1.2.1.220.1.10.1,LISP-MIB::lispEidRegistrationEtrEntry,,not-accessible,lispEidRegistrationEidLength:lispEidRegistrationEid:lispEidRegistrationEtrSenderLength:lispEidRegistrationEtrSender,current,,An entry (conceptual row) in the lispEidRegistrationEtrTable.
.1.3.6.1.2.1.220.1.10.1.1,LISP-MIB::lispEidRegistrationEtrSenderLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispEidRegistrationEtrSender.
.1.3.6.1.2.1.220.1.10.1.2,LISP-MIB::lispEidRegistrationEtrSender,OCTET,not-accessible,,current,,Source address of the ETR that is sending valid register messages for this EID-Prefix to this device.
.1.3.6.1.2.1.220.1.10.1.3,LISP-MIB::lispEidRegistrationEtrLastTimeStamp,TimeTicks,read-only,,current,,The value of sysUpTime at which the last valid register message from this ETR for the EID Prefix information represented by this entry was received by this device. If this information was present at the most recent reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.220.1.10.1.4,LISP-MIB::lispEidRegistrationEtrTtl,Unsigned32,read-only,,current,,The Record TTL of the registering ETR device for this EID-Prefix.
.1.3.6.1.2.1.220.1.10.1.5,LISP-MIB::lispEidRegistrationEtrProxyReply,INTEGER,read-only,,current,true(1):false(2),Indicates proxy-replying status of the registering ETR for this EID-Prefix. If this object is true, then it means the Map-Server can proxy-reply.
.1.3.6.1.2.1.220.1.10.1.6,LISP-MIB::lispEidRegistrationEtrWantsMapNotify,INTEGER,read-only,,current,true(1):false(2),Indicates whether the EID-Prefix wants Map-Notifications. If this object is true, then it means the EID-Prefix wants Map-Notifications.
.1.3.6.1.2.1.220.1.11,LISP-MIB::lispEidRegistrationLocatorTable,,not-accessible,,current,,This table provides the properties of all locators per LISP site that are served by this device when configured to be a Map-Server.
.1.3.6.1.2.1.220.1.11.1,LISP-MIB::lispEidRegistrationLocatorEntry,,not-accessible,lispEidRegistrationEidLength:lispEidRegistrationEid:lispEidRegistrationEtrSenderLength:lispEidRegistrationEtrSender:lispEidRegistrationLocatorRlocLength:lispEidRegistrationLocatorRloc,current,,An entry (conceptual row) in the lispEidRegistrationLocatorTable.
.1.3.6.1.2.1.220.1.11.1.1,LISP-MIB::lispEidRegistrationLocatorRlocLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispEidRegistrationLocatorRloc.
.1.3.6.1.2.1.220.1.11.1.2,LISP-MIB::lispEidRegistrationLocatorRloc,OCTET,not-accessible,,current,,The locator of the given EID-Prefix being registered by the given ETR with this device.
.1.3.6.1.2.1.220.1.11.1.3,LISP-MIB::lispEidRegistrationLocatorRlocState,INTEGER,read-only,,current,up(1):down(2),The cached state of this RLOC received in map-register from the ETR by the device, in the capacity of a Map-Server. Value 1 refers to up, value 2 refers to down.
.1.3.6.1.2.1.220.1.11.1.4,LISP-MIB::lispEidRegistrationLocatorIsLocal,INTEGER,read-only,,current,true(1):false(2),Indicates if the given locator is local to the registering ETR. If this object is true, it means the locator is local.
.1.3.6.1.2.1.220.1.11.1.5,LISP-MIB::lispEidRegistrationLocatorPriority,Integer32,read-only,,current,,The unicast priority of the RLOC for this EID-Prefix in the register message sent by the given ETR.
.1.3.6.1.2.1.220.1.11.1.6,LISP-MIB::lispEidRegistrationLocatorWeight,Integer32,read-only,,current,,The unicast weight of the RLOC for this EID-Prefix in the register message sent by the given ETR.
.1.3.6.1.2.1.220.1.11.1.7,LISP-MIB::lispEidRegistrationLocatorMPriority,Integer32,read-only,,current,,The multicast priority of the RLOC for this EID-Prefix in the register message sent by the given ETR.
.1.3.6.1.2.1.220.1.11.1.8,LISP-MIB::lispEidRegistrationLocatorMWeight,Integer32,read-only,,current,,The multicast weight of the RLOC for this EID-Prefix in the register message sent by the given ETR.
.1.3.6.1.2.1.220.1.12,LISP-MIB::lispUseMapServerTable,,not-accessible,,current,,This table provides the properties of the Map-Server(s) with which this device is configured to register.
.1.3.6.1.2.1.220.1.12.1,LISP-MIB::lispUseMapServerEntry,,not-accessible,lispUseMapServerAddressLength:lispUseMapServerAddress,current,,An entry (conceptual row) in the lispUseMapServerTable.
.1.3.6.1.2.1.220.1.12.1.1,LISP-MIB::lispUseMapServerAddressLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispUseMapServerAddress.
.1.3.6.1.2.1.220.1.12.1.2,LISP-MIB::lispUseMapServerAddress,OCTET,not-accessible,,current,,Address of a Map-Server configured on this device.
.1.3.6.1.2.1.220.1.12.1.3,LISP-MIB::lispUseMapServerState,INTEGER,read-only,,current,up(1):down(2):unreachable(3),State of this Map-Server configured on this device (1 = Map-Server is up; 2 = Map-Server is down).
.1.3.6.1.2.1.220.1.13,LISP-MIB::lispUseMapResolverTable,,not-accessible,,current,,This table provides the properties of the Map-Resolver(s) this device is configured to use.
.1.3.6.1.2.1.220.1.13.1,LISP-MIB::lispUseMapResolverEntry,,not-accessible,lispUseMapResolverAddressLength:lispUseMapResolverAddress,current,,An entry (conceptual row) in the lispUseMapResolverTable.
.1.3.6.1.2.1.220.1.13.1.1,LISP-MIB::lispUseMapResolverAddressLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispUseMapResolverAddress.
.1.3.6.1.2.1.220.1.13.1.2,LISP-MIB::lispUseMapResolverAddress,OCTET,not-accessible,,current,,Address of Map-Resolver configured on this device.
.1.3.6.1.2.1.220.1.13.1.3,LISP-MIB::lispUseMapResolverState,INTEGER,read-only,,current,up(1):down(2),State of this Map-Resolver configured on this device (1 = Map-Resolver is up; 2 = Map-Resolver is down).
.1.3.6.1.2.1.220.1.14,LISP-MIB::lispUseProxyEtrTable,,not-accessible,,current,,This table provides the properties of all Proxy ETRs that this device is configured to use.
.1.3.6.1.2.1.220.1.14.1,LISP-MIB::lispUseProxyEtrEntry,,not-accessible,lispUseProxyEtrAddressLength:lispUseProxyEtrAddress,current,,An entry (conceptual row) in the lispUseProxyEtrTable.
.1.3.6.1.2.1.220.1.14.1.1,LISP-MIB::lispUseProxyEtrAddressLength,Integer32,not-accessible,,current,,This object is used to get the octet-length of lispUseProxyEtrAddress.
.1.3.6.1.2.1.220.1.14.1.2,LISP-MIB::lispUseProxyEtrAddress,OCTET,not-accessible,,current,,Address of Proxy ETR configured on this device.
.1.3.6.1.2.1.220.1.14.1.3,LISP-MIB::lispUseProxyEtrPriority,Integer32,read-only,,current,,The unicast priority of the PETR locator.
.1.3.6.1.2.1.220.1.14.1.4,LISP-MIB::lispUseProxyEtrWeight,Integer32,read-only,,current,,The unicast weight of the PETR locator.
.1.3.6.1.2.1.220.1.14.1.5,LISP-MIB::lispUseProxyEtrMPriority,Integer32,read-only,,current,,The multicast priority of the PETR locator.
.1.3.6.1.2.1.220.1.14.1.6,LISP-MIB::lispUseProxyEtrMWeight,Integer32,read-only,,current,,The multicast weight of the PETR locator.
.1.3.6.1.2.1.220.1.14.1.7,LISP-MIB::lispUseProxyEtrState,INTEGER,read-only,,current,down(0):up(1),State of this Proxy ETR configured on this device (0 = Proxy ETR is down; 1 = Proxy ETR is up).
.1.3.6.1.2.1.220.2,LISP-MIB::lispConformance,,,,,,
.1.3.6.1.2.1.220.2.1,LISP-MIB::lispCompliances,,,,,,
.1.3.6.1.2.1.220.2.1.1,LISP-MIB::lispMIBComplianceEtr,,,,,,The compliance statement for LISP ETRs. It conveys whether the device supports the ETR feature, and, if so, the relevant state associated with that feature.
.1.3.6.1.2.1.220.2.1.2,LISP-MIB::lispMIBComplianceItr,,,,,,The compliance statement for LISP ITRs. It conveys whether the device supports the ITR feature, and, if so, the relevant state associated with that feature.
.1.3.6.1.2.1.220.2.1.3,LISP-MIB::lispMIBCompliancePetr,,,,,,The compliance statement for LISP Proxy-ETRs. It conveys whether the device supports the Proxy-ETR feature, and, if so, the relevant state associated with that feature.
.1.3.6.1.2.1.220.2.1.4,LISP-MIB::lispMIBCompliancePitr,,,,,,The compliance statement for LISP Proxy-ITRs. It conveys whether the device supports the Proxy-ITR feature, and, if so, the relevant state associated with that feature.
.1.3.6.1.2.1.220.2.1.5,LISP-MIB::lispMIBComplianceMapServer,,,,,,The compliance statement for LISP Map Servers. It conveys whether the device supports the Map Server feature, and, if so, the relevant state associated with that feature.
.1.3.6.1.2.1.220.2.1.6,LISP-MIB::lispMIBComplianceMapResolver,,,,,,The compliance statement for LISP Map Resolvers. It conveys whether the device supports the Map Resolver feature, and, if so, the relevant state associated with that feature.
.1.3.6.1.2.1.220.2.2,LISP-MIB::lispGroups,,,,,,
.1.3.6.1.2.1.220.2.2.1,LISP-MIB::lispMIBEtrGroup,,,,,,A collection of objects to support reporting of basic LISP ETR parameters.
.1.3.6.1.2.1.220.2.2.2,LISP-MIB::lispMIBItrGroup,,,,,,A collection of objects to support reporting of basic LISP ITR parameters.
.1.3.6.1.2.1.220.2.2.3,LISP-MIB::lispMIBPetrGroup,,,,,,A collection of objects to support reporting of basic LISP Proxy-ETR parameters.
.1.3.6.1.2.1.220.2.2.4,LISP-MIB::lispMIBPitrGroup,,,,,,A collection of objects to support reporting of basic LISP Proxy-ITR parameters.
.1.3.6.1.2.1.220.2.2.5,LISP-MIB::lispMIBMapServerGroup,,,,,,A collection of objects to support reporting of basic LISP Map Server parameters.
.1.3.6.1.2.1.220.2.2.6,LISP-MIB::lispMIBMapResolverGroup,,,,,,A collection of objects to support reporting of basic LISP Map Resolver parameters.
.1.3.6.1.2.1.220.2.2.7,LISP-MIB::lispMIBEtrExtendedGroup,,,,,,A collection of objects to support reporting of LISP features and properties on ETRs.
.1.3.6.1.2.1.220.2.2.8,LISP-MIB::lispMIBItrExtendedGroup,,,,,,A collection of objects to support reporting of LISP features and properties on ITRs.
.1.3.6.1.2.1.220.2.2.9,LISP-MIB::lispMIBMapServerExtendedGroup,,,,,,A collection of objects to support the reporting of LISP features and properties on Map Servers related to EID registrations.
.1.3.6.1.2.1.220.2.2.10,LISP-MIB::lispMIBTuningParametersGroup,,,,,,A collection of objects used to support the reporting of parameters used to control LISP behavior and to tune performance.
.1.3.6.1.2.1.220.2.2.11,LISP-MIB::lispMIBEncapStatisticsGroup,,,,,,A collection of objects used to support the reporting of LISP encapsulation statistics for the device.
.1.3.6.1.2.1.220.2.2.12,LISP-MIB::lispMIBDecapStatisticsGroup,,,,,,A collection of objects used to support the reporting of LISP decapsulation statistics for the device.
.1.3.6.1.2.1.220.2.2.13,LISP-MIB::lispMIBDiagnosticsGroup,,,,,,A collection of objects used to support the reporting of additional diagnostics related to the LISP control-plane state of a LISP device.
.1.3.6.1.2.1.220.2.2.14,LISP-MIB::lispMIBVrfGroup,,,,,,A collection of objects used to support reporting of VRF-related information on a LISP device.
.1.3.6.1.2.1.221,IANA-OLSRv2-LINK-METRIC-TYPE-MIB::ianaolsrv2LinkMetricType,,,,,,This MIB module defines the IANAolsrv2LinkMetricType Textual Convention, and thus the enumerated values of the olsrv2LinkMetricType object defined in the OLSRv2-MIB.
.1.3.6.1.2.1.222,BFD-STD-MIB::bfdMIB,,,,,,Bidirectional Forwarding Management Information Base. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.222.0,BFD-STD-MIB::bfdNotifications,,,,,,
.1.3.6.1.2.1.222.0.1,BFD-STD-MIB::bfdSessUp,,,,,,This notification is generated when the bfdSessState object for one or more contiguous entries in bfdSessTable are about to enter the up(4) state from some other state. The included values of bfdSessDiag MUST both be set equal to this new state (i.e., up(4)). The two instances of bfdSessDiag in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For the cases where a contiguous range of sessions have transitioned into the up(4) state at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single bfdSessEntry, then the instance identifier (and values) of the two bfdSessDiag objects MUST be identical.
.1.3.6.1.2.1.222.0.2,BFD-STD-MIB::bfdSessDown,,,,,,This notification is generated when the bfdSessState object for one or more contiguous entries in bfdSessTable are about to enter the down(2) or adminDown(1) states from some other state. The included values of bfdSessDiag MUST both be set equal to this new state (i.e., down(2) or adminDown(1)). The two instances of bfdSessDiag in this notification indicate the range of indexes that are affected. Note that all the indexes of the two ends of the range can be derived from the instance identifiers of these two objects. For cases where a contiguous range of sessions have transitioned into the down(2) or adminDown(1) states at roughly the same time, the device SHOULD issue a single notification for each range of contiguous indexes in an effort to minimize the emission of a large number of notifications. If a notification has to be issued for just a single bfdSessEntry, then the instance identifier (and values) of the two bfdSessDiag objects MUST be identical.
.1.3.6.1.2.1.222.1,BFD-STD-MIB::bfdObjects,,,,,,
.1.3.6.1.2.1.222.1.1,BFD-STD-MIB::bfdScalarObjects,,,,,,
.1.3.6.1.2.1.222.1.1.1,BFD-STD-MIB::bfdAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2):adminDown(3):down(4),The desired global administrative status of the BFD system in this device.
.1.3.6.1.2.1.222.1.1.2,BFD-STD-MIB::bfdOperStatus,INTEGER,read-only,,current,up(1):down(2):adminDown(3),Indicates the actual operational status of the BFD system in this device. When this value is down(2), all entries in the bfdSessTable MUST have their bfdSessOperStatus as down(2) as well. When this value is adminDown(3), all entries in the bfdSessTable MUST have their bfdSessOperStatus as adminDown(3) as well.
.1.3.6.1.2.1.222.1.1.3,BFD-STD-MIB::bfdNotificationsEnable,INTEGER,read-write,,current,true(1):false(2),If this object is set to true(1), then it enables the emission of bfdSessUp and bfdSessDown notifications; otherwise, these notifications are not emitted.
.1.3.6.1.2.1.222.1.1.4,BFD-STD-MIB::bfdSessIndexNext,Unsigned32,read-only,,current,,This object contains an unused value for bfdSessIndex that can be used when creating entries in the table. A zero indicates that no entries are available, but it MUST NOT be used as a valid index. 
.1.3.6.1.2.1.222.1.2,BFD-STD-MIB::bfdSessTable,,not-accessible,,current,,The BFD Session Table describes the BFD sessions.
.1.3.6.1.2.1.222.1.2.1,BFD-STD-MIB::bfdSessEntry,,not-accessible,bfdSessIndex,current,,The BFD Session Entry describes the BFD session.
.1.3.6.1.2.1.222.1.2.1.1,BFD-STD-MIB::bfdSessIndex,Unsigned32,not-accessible,,current,,This object contains an index used to represent a unique BFD session on this device. Managers should obtain new values for row creation in this table by reading bfdSessIndexNext.
.1.3.6.1.2.1.222.1.2.1.2,BFD-STD-MIB::bfdSessVersionNumber,Unsigned32,read-create,,current,,The version number of the BFD protocol that this session is running in. Write access is available for this object to provide the ability to set the desired version for this BFD session.
.1.3.6.1.2.1.222.1.2.1.3,BFD-STD-MIB::bfdSessType,INTEGER,read-create,,current,singleHop(1):multiHopTotallyArbitraryPaths(2):multiHopOutOfBandSignaling(3):multiHopUnidirectionalLinks(4),This object specifies the type of this BFD session.
.1.3.6.1.2.1.222.1.2.1.4,BFD-STD-MIB::bfdSessDiscriminator,Unsigned32,read-create,,current,,This object specifies the local discriminator for this BFD session, which is used to uniquely identify it.
.1.3.6.1.2.1.222.1.2.1.5,BFD-STD-MIB::bfdSessRemoteDiscr,Unsigned32,read-only,,current,,This object specifies the session discriminator chosen by the remote system for this BFD session. The value may be zero(0) if the remote discriminator is not yet known or if the session is in the down or adminDown(1) state.
.1.3.6.1.2.1.222.1.2.1.6,BFD-STD-MIB::bfdSessDestinationUdpPort,Unsigned32,read-create,,current,,This object specifies the destination UDP port number used for this BFD session's Control packets. The value may be zero(0) if the session is in adminDown(1) state.
.1.3.6.1.2.1.222.1.2.1.7,BFD-STD-MIB::bfdSessSourceUdpPort,Unsigned32,read-create,,current,,This object specifies the source UDP port number used for this BFD session's Control packets. The value may be zero(0) if the session is in adminDown(1) state. Upon creation of a new BFD session via this MIB, the value of zero(0) specified would permit the implementation to choose its own source port number.
.1.3.6.1.2.1.222.1.2.1.8,BFD-STD-MIB::bfdSessEchoSourceUdpPort,Unsigned32,read-create,,current,,This object specifies the source UDP port number used for this BFD session's Echo packets. The value may be zero(0) if the session is not running in the Echo mode, or the session is in adminDown(1) state. Upon creation of a new BFD session via this MIB, the value of zero(0) would permit the implementation to choose its own source port number.
.1.3.6.1.2.1.222.1.2.1.9,BFD-STD-MIB::bfdSessAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2):adminDown(3):down(4),Denotes the desired operational status of the BFD session. A transition to enabled(1) will start the BFD state machine for the session. The state machine will have an initial state of down(2). A transition to disabled(2) will stop the BFD state machine for the session. The state machine may first transition to adminDown(1) prior to stopping. A transition to adminDown(3) will cause the BFD state machine to transition to adminDown(1) and will cause the session to remain in this state. A transition to down(4) will cause the BFD state machine to transition to down(2) and will cause the session to remain in this state. Care should be used in providing write access to this object without adequate authentication.
.1.3.6.1.2.1.222.1.2.1.10,BFD-STD-MIB::bfdSessOperStatus,INTEGER,read-only,,current,up(1):down(2):adminDown(3),Denotes the actual operational status of the BFD session. If the value of bfdOperStatus is down(2), this value MUST eventually be down(2) as well. If the value of bfdOperStatus is adminDown(3), this value MUST eventually be adminDown(3) as well.
.1.3.6.1.2.1.222.1.2.1.11,BFD-STD-MIB::bfdSessState,INTEGER,read-only,,current,adminDown(1):down(2):init(3):up(4):failing(5),Configured BFD session state.
.1.3.6.1.2.1.222.1.2.1.12,BFD-STD-MIB::bfdSessRemoteHeardFlag,INTEGER,read-only,,current,true(1):false(2),This object specifies the status of BFD packet reception from the remote system. Specifically, it is set to true(1) if the local system is actively receiving BFD packets from the remote system and is set to false(2) if the local system has not received BFD packets recently (within the detection time) or if the local system is attempting to tear down the BFD session.
.1.3.6.1.2.1.222.1.2.1.13,BFD-STD-MIB::bfdSessDiag,INTEGER,read-only,,current,noDiagnostic(0):controlDetectionTimeExpired(1):echoFunctionFailed(2):neighborSignaledSessionDown(3):forwardingPlaneReset(4):pathDown(5):concatenatedPathDown(6):administrativelyDown(7):reverseConcatenatedPathDown(8):misConnectivityDefect(9),A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.
.1.3.6.1.2.1.222.1.2.1.14,BFD-STD-MIB::bfdSessOperMode,INTEGER,read-create,,current,asyncModeWEchoFunction(1):asynchModeWOEchoFunction(2):demandModeWEchoFunction(3):demandModeWOEchoFunction(4),This object specifies the operational mode of this BFD session.
.1.3.6.1.2.1.222.1.2.1.15,BFD-STD-MIB::bfdSessDemandModeDesiredFlag,INTEGER,read-create,,current,true(1):false(2),This object indicates the local system's desire to use Demand mode. Specifically, it is set to true(1) if the local system wishes to use Demand mode or false(2) if not.
.1.3.6.1.2.1.222.1.2.1.16,BFD-STD-MIB::bfdSessControlPlaneIndepFlag,INTEGER,read-create,,current,true(1):false(2),This object indicates the local system's ability to continue to function through a disruption of the control plane. Specifically, it is set to true(1) if the local system BFD implementation is independent of the control plane. Otherwise, the value is set to false(2).
.1.3.6.1.2.1.222.1.2.1.17,BFD-STD-MIB::bfdSessMultipointFlag,INTEGER,read-create,,current,true(1):false(2),This object indicates the Multipoint (M) bit for this session. It is set to true(1) if the Multipoint (M) bit is set to 1. Otherwise, the value is set to false(2).
.1.3.6.1.2.1.222.1.2.1.18,BFD-STD-MIB::bfdSessInterface,Integer32,read-create,,current,,This object contains an interface index used to indicate the interface that this BFD session is running on. This value can be zero if there is no interface associated with this BFD session.
.1.3.6.1.2.1.222.1.2.1.19,BFD-STD-MIB::bfdSessSrcAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the IP address type of the source IP address of this BFD session. The value of unknown(0) is allowed only when the session is singleHop(1) and the source IP address of this BFD session is derived from the outgoing interface, or when the BFD session is not associated with a specific interface. If any other unsupported values are attempted in a set operation, the agent MUST return an inconsistentValue error.
.1.3.6.1.2.1.222.1.2.1.20,BFD-STD-MIB::bfdSessSrcAddr,OCTET,read-create,,current,,This object specifies the source IP address of this BFD session. The format of this object is controlled by the bfdSessSrcAddrType object.
.1.3.6.1.2.1.222.1.2.1.21,BFD-STD-MIB::bfdSessDstAddrType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the IP address type of the neighboring IP address that is being monitored with this BFD session. The value of unknown(0) is allowed only when the session is singleHop(1) and the outgoing interface is of type point to point, or when the BFD session is not associated with a specific interface. If any other unsupported values are attempted in a set operation, the agent MUST return an inconsistentValue error.
.1.3.6.1.2.1.222.1.2.1.22,BFD-STD-MIB::bfdSessDstAddr,OCTET,read-create,,current,,This object specifies the neighboring IP address that is being monitored with this BFD session. The format of this object is controlled by the bfdSessDstAddrType object.
.1.3.6.1.2.1.222.1.2.1.23,BFD-STD-MIB::bfdSessGTSM,INTEGER,read-create,,current,true(1):false(2),Setting the value of this object to false(2) will disable GTSM protection of the BFD session. GTSM MUST be enabled on a singleHop(1) session if no authentication is in use.
.1.3.6.1.2.1.222.1.2.1.24,BFD-STD-MIB::bfdSessGTSMTTL,Unsigned32,read-create,,current,,This object is valid only when bfdSessGTSM protection is enabled on the system. This object indicates the minimum allowed Time to Live (TTL) for received BFD Control packets. For a singleHop(1) session, if GTSM protection is enabled, this object SHOULD be set to the maximum TTL value allowed for a single hop. By default, GTSM is enabled and the TTL value is 255. For a multihop session, updating of the maximum TTL value allowed is likely required.
.1.3.6.1.2.1.222.1.2.1.25,BFD-STD-MIB::bfdSessDesiredMinTxInterval,Unsigned32,read-create,,current,,This object specifies the minimum interval, in microseconds, that the local system would like to use when transmitting BFD Control packets. The value of zero(0) is reserved in this case and should not be used.
.1.3.6.1.2.1.222.1.2.1.26,BFD-STD-MIB::bfdSessReqMinRxInterval,Unsigned32,read-create,,current,,This object specifies the minimum interval, in microseconds, between received BFD Control packets the local system is capable of supporting. The value of zero(0) can be specified when the transmitting system does not want the remote system to send any periodic BFD Control packets.
.1.3.6.1.2.1.222.1.2.1.27,BFD-STD-MIB::bfdSessReqMinEchoRxInterval,Unsigned32,read-create,,current,,This object specifies the minimum interval, in microseconds, between received BFD Echo packets that this system is capable of supporting. The value must be zero(0) if this is a multihop BFD session.
.1.3.6.1.2.1.222.1.2.1.28,BFD-STD-MIB::bfdSessDetectMult,Unsigned32,read-create,,current,,This object specifies the Detect time multiplier.
.1.3.6.1.2.1.222.1.2.1.29,BFD-STD-MIB::bfdSessNegotiatedInterval,Unsigned32,read-only,,current,,This object specifies the negotiated interval, in microseconds, that the local system is transmitting BFD Control packets.
.1.3.6.1.2.1.222.1.2.1.30,BFD-STD-MIB::bfdSessNegotiatedEchoInterval,Unsigned32,read-only,,current,,This object specifies the negotiated interval, in microseconds, that the local system is transmitting BFD Echo packets. The value is expected to be zero if the sessions are not running in Echo mode.
.1.3.6.1.2.1.222.1.2.1.31,BFD-STD-MIB::bfdSessNegotiatedDetectMult,Unsigned32,read-only,,current,,This object specifies the Detect time multiplier.
.1.3.6.1.2.1.222.1.2.1.32,BFD-STD-MIB::bfdSessAuthPresFlag,INTEGER,read-create,,current,true(1):false(2),This object indicates the local system's desire to use authentication. Specifically, it is set to true(1) if the local system wishes the session to be authenticated or false(2) if not.
.1.3.6.1.2.1.222.1.2.1.33,BFD-STD-MIB::bfdSessAuthenticationType,INTEGER,read-create,,current,noAuthentication(-1):reserved(0):simplePassword(1):keyedMD5(2):meticulousKeyedMD5(3):keyedSHA1(4):meticulousKeyedSHA1(5),The authentication type used for this BFD session. This field is valid only when the Authentication Present bit is set. MAX-ACCESS to this object as well as other authentication-related objects are set to read-create in order to support management of a single key ID at a time; key rotation is not handled. Key update in practice must be done by atomic update using a set containing all affected objects in the same varBindList or otherwise risk the session dropping.
.1.3.6.1.2.1.222.1.2.1.34,BFD-STD-MIB::bfdSessAuthenticationKeyID,Integer32,read-create,,current,,The authentication key ID in use for this session. This object permits multiple keys to be active simultaneously. The value -1 indicates that no authentication key ID will be present in the optional BFD Authentication Section.
.1.3.6.1.2.1.222.1.2.1.35,BFD-STD-MIB::bfdSessAuthenticationKey,OCTET,read-create,,current,,The authentication key. When the bfdSessAuthenticationType is simplePassword(1), the value of this object is the password present in the BFD packets. When the bfdSessAuthenticationType is one of the keyed authentication types, this value is used in the computation of the key present in the BFD authentication packet.
.1.3.6.1.2.1.222.1.2.1.36,BFD-STD-MIB::bfdSessStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.2.1.222.1.2.1.37,BFD-STD-MIB::bfdSessRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This variable is used to create, modify, and/or delete a row in this table. When a row in this table has a row in the active(1) state, no objects in this row can be modified except the bfdSessRowStatus and bfdSessStorageType.
.1.3.6.1.2.1.222.1.3,BFD-STD-MIB::bfdSessPerfTable,,not-accessible,,current,,This table specifies BFD session performance counters.
.1.3.6.1.2.1.222.1.3.1,BFD-STD-MIB::bfdSessPerfEntry,,not-accessible,,current,,An entry in this table is created by a BFD-enabled node for every BFD session. bfdSessPerfDiscTime is used to indicate potential discontinuity for all counter objects in this table.
.1.3.6.1.2.1.222.1.3.1.1,BFD-STD-MIB::bfdSessPerfCtrlPktIn,Counter32,read-only,,current,,The total number of BFD control messages received for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktInHC if supported, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.2,BFD-STD-MIB::bfdSessPerfCtrlPktOut,Counter32,read-only,,current,,The total number of BFD control messages sent for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktOutHC if supported, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.3,BFD-STD-MIB::bfdSessPerfCtrlPktDrop,Counter32,read-only,,current,,The total number of BFD control messages received for this session yet dropped for being invalid. It MUST be equal to the least significant 32 bits of bfdSessPerfCtrlPktDropHC if supported, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.4,BFD-STD-MIB::bfdSessPerfCtrlPktDropLastTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which received the BFD control message for this session was dropped. If no such up event exists, this object contains a zero value.
.1.3.6.1.2.1.222.1.3.1.5,BFD-STD-MIB::bfdSessPerfEchoPktIn,Counter32,read-only,,current,,The total number of BFD Echo messages received for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktInHC if supported, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.6,BFD-STD-MIB::bfdSessPerfEchoPktOut,Counter32,read-only,,current,,The total number of BFD Echo messages sent for this BFD session. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktOutHC if supported, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.7,BFD-STD-MIB::bfdSessPerfEchoPktDrop,Counter32,read-only,,current,,The total number of BFD Echo messages received for this session yet dropped for being invalid. It MUST be equal to the least significant 32 bits of bfdSessPerfEchoPktDropHC if supported, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.8,BFD-STD-MIB::bfdSessPerfEchoPktDropLastTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which received the BFD Echo message for this session was dropped. If no such up event has been issued, this object contains a zero value.
.1.3.6.1.2.1.222.1.3.1.9,BFD-STD-MIB::bfdSessUpTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which the session came up. If no such event has been issued, this object contains a zero value.
.1.3.6.1.2.1.222.1.3.1.10,BFD-STD-MIB::bfdSessPerfLastSessDownTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which the last time communication was lost with the neighbor. If no down event has been issued, this object contains a zero value.
.1.3.6.1.2.1.222.1.3.1.11,BFD-STD-MIB::bfdSessPerfLastCommLostDiag,INTEGER,read-only,,current,noDiagnostic(0):controlDetectionTimeExpired(1):echoFunctionFailed(2):neighborSignaledSessionDown(3):forwardingPlaneReset(4):pathDown(5):concatenatedPathDown(6):administrativelyDown(7):reverseConcatenatedPathDown(8):misConnectivityDefect(9),The BFD diag code for the last time communication was lost with the neighbor. If such an event has not been issued, this object contains a zero value.
.1.3.6.1.2.1.222.1.3.1.12,BFD-STD-MIB::bfdSessPerfSessUpCount,Counter32,read-only,,current,,The number of times this session has gone into the Up state since the system last rebooted.
.1.3.6.1.2.1.222.1.3.1.13,BFD-STD-MIB::bfdSessPerfDiscTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of the session counters suffered a discontinuity. The relevant counters are the specific instances associated with this BFD session of any Counter32 object contained in the BfdSessPerfTable. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.222.1.3.1.14,BFD-STD-MIB::bfdSessPerfCtrlPktInHC,Counter64,read-only,,current,,This value represents the total number of BFD control messages received for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfCtrlPktIn, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.15,BFD-STD-MIB::bfdSessPerfCtrlPktOutHC,Counter64,read-only,,current,,This value represents the total number of BFD control messages transmitted for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfCtrlPktOut, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.16,BFD-STD-MIB::bfdSessPerfCtrlPktDropHC,Counter64,read-only,,current,,This value represents the total number of BFD control messages received for this BFD session yet dropped for being invalid. The least significant 32 bits MUST be equal to bfdSessPerfCtrlPktDrop, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.17,BFD-STD-MIB::bfdSessPerfEchoPktInHC,Counter64,read-only,,current,,This value represents the total number of BFD Echo messages received for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfEchoPktIn, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.18,BFD-STD-MIB::bfdSessPerfEchoPktOutHC,Counter64,read-only,,current,,This value represents the total number of BFD Echo messages transmitted for this BFD session. The least significant 32 bits MUST be equal to bfdSessPerfEchoPktOut, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.3.1.19,BFD-STD-MIB::bfdSessPerfEchoPktDropHC,Counter64,read-only,,current,,This value represents the total number of BFD Echo messages received for this BFD session yet dropped for being invalid. The least significant 32 bits MUST be equal to bfdSessPerfEchoPktDrop, and MUST do so with the rules spelled out in RFC 2863.
.1.3.6.1.2.1.222.1.4,BFD-STD-MIB::bfdSessDiscMapTable,,not-accessible,,current,,The BFD Session Discriminator Mapping Table maps a local discriminator value to the associated BFD session's bfdSessIndex found in the bfdSessionTable.
.1.3.6.1.2.1.222.1.4.1,BFD-STD-MIB::bfdSessDiscMapEntry,,not-accessible,bfdSessDiscriminator,current,,The BFD Session Discriminator Mapping Entry specifies a mapping between a local discriminator and a BFD session.
.1.3.6.1.2.1.222.1.4.1.1,BFD-STD-MIB::bfdSessDiscMapIndex,Unsigned32,read-only,,current,,This object specifies a mapping between a local discriminator and a BFD session in the BfdSessTable.
.1.3.6.1.2.1.222.1.5,BFD-STD-MIB::bfdSessIpMapTable,,not-accessible,,current,,The BFD Session IP Mapping Table maps given bfdSessInterface, bfdSessSrcAddrType, bfdSessSrcAddr, bfdSessDstAddrType, and bfdSessDstAddr to an associated BFD session found in the bfdSessionTable.
.1.3.6.1.2.1.222.1.5.1,BFD-STD-MIB::bfdSessIpMapEntry,,not-accessible,bfdSessInterface:bfdSessSrcAddrType:bfdSessSrcAddr:bfdSessDstAddrType:bfdSessDstAddr,current,,The BFD Session IP Map Entry contains a mapping from the IP information for a session to the session in the bfdSessionTable.
.1.3.6.1.2.1.222.1.5.1.1,BFD-STD-MIB::bfdSessIpMapIndex,Unsigned32,read-only,,current,,This object specifies the BfdSessIndexTC referred to by the indexes of this row. In essence, a mapping is provided between these indexes and the BfdSessTable.
.1.3.6.1.2.1.222.2,BFD-STD-MIB::bfdConformance,,,,,,
.1.3.6.1.2.1.222.2.1,BFD-STD-MIB::bfdGroups,,,,,,
.1.3.6.1.2.1.222.2.1.1,BFD-STD-MIB::bfdSessionGroup,,,,,,Collection of objects needed for BFD sessions.
.1.3.6.1.2.1.222.2.1.2,BFD-STD-MIB::bfdSessionReadOnlyGroup,,,,,,Collection of read-only objects needed for BFD sessions.
.1.3.6.1.2.1.222.2.1.3,BFD-STD-MIB::bfdSessionPerfGroup,,,,,,Collection of objects needed to monitor the performance of BFD sessions.
.1.3.6.1.2.1.222.2.1.4,BFD-STD-MIB::bfdSessionPerfHCGroup,,,,,,Collection of objects needed to monitor the performance of BFD sessions for which the values of bfdSessPerfPktIn and bfdSessPerfPktOut wrap around too quickly.
.1.3.6.1.2.1.222.2.1.5,BFD-STD-MIB::bfdNotificationGroup,,,,,,Set of notifications implemented in this module.
.1.3.6.1.2.1.222.2.2,BFD-STD-MIB::bfdCompliances,,,,,,
.1.3.6.1.2.1.222.2.2.1,BFD-STD-MIB::bfdModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for the BFD-MIB module. Such devices can then be monitored and also be configured using this MIB module.
.1.3.6.1.2.1.222.2.2.2,BFD-STD-MIB::bfdModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for BFD-MIB. Such devices can then be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.223,BFD-TC-STD-MIB::bfdTCStdMib,,,,,,Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.224,IANA-BFD-TC-STD-MIB::ianaBfdTCStdMib,,,,,,Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.224.1,FCIP-MGMT-MIB::fcipObjects,,,,,,
.1.3.6.1.2.1.224.1.1,FCIP-MGMT-MIB::fcipConfig,,,,,,
.1.3.6.1.2.1.224.1.1.1,FCIP-MGMT-MIB::fcipDynIpConfType,INTEGER,read-write,,current,slpv2(1):none(2),The type of discovery protocol used to discover remote FCIP entities. The value of this object is persistent across system restarts.
.1.3.6.1.2.1.224.1.1.2,FCIP-MGMT-MIB::fcipDeviceWWN,OCTET,read-only,,current,,The World Wide Name of this FCIP device.
.1.3.6.1.2.1.224.1.1.3,FCIP-MGMT-MIB::fcipEntitySACKOption,INTEGER,read-only,,current,enabled(1):disabled(2),Indication of whether the TCP Selective Acknowledgement Option is enabled at this FCIP device to let the receiver acknowledge multiple lost packets in a single ACK for faster recovery.
.1.3.6.1.2.1.224.1.1.4,FCIP-MGMT-MIB::fcipEntityInstanceTable,,not-accessible,,current,,Information about this FCIP device's existing instances of FCIP entities.
.1.3.6.1.2.1.224.1.1.4.1,FCIP-MGMT-MIB::fcipEntityInstanceEntry,,not-accessible,fcipEntityId,current,,A conceptual row of the FCIP entity table with information about a particular FCIP entity. Once a row has been created, it is non-volatile across agent restarts until it is deleted.
.1.3.6.1.2.1.224.1.1.4.1.1,FCIP-MGMT-MIB::fcipEntityId,OCTET,not-accessible,,current,,The FCIP entity identifier.
.1.3.6.1.2.1.224.1.1.4.1.2,FCIP-MGMT-MIB::fcipEntityName,OCTET,read-create,,current,,An administratively-assigned name for this FCIP entity.
.1.3.6.1.2.1.224.1.1.4.1.3,FCIP-MGMT-MIB::fcipEntityAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address by which the entity is reachable. Only address types IPv4 and IPv6 are supported.
.1.3.6.1.2.1.224.1.1.4.1.4,FCIP-MGMT-MIB::fcipEntityAddress,OCTET,read-create,,current,,The Internet address for the entity, if configured. The format of this address is determined by the value of the fcipEntityAddressType object.
.1.3.6.1.2.1.224.1.1.4.1.5,FCIP-MGMT-MIB::fcipEntityTcpConnPort,Unsigned32,read-create,,current,,A TCP port other than the FCIP Well-Known port on which the FCIP entity listens for new TCP connection requests. It contains the value zero(0) if the FCIP Entity only listens on the Well-Known port.
.1.3.6.1.2.1.224.1.1.4.1.6,FCIP-MGMT-MIB::fcipEntitySeqNumWrap,INTEGER,read-only,,current,true(1):false(2),An indication of whether the FCIP Entity supports protection against sequence number wrap.
.1.3.6.1.2.1.224.1.1.4.1.7,FCIP-MGMT-MIB::fcipEntityPHBSupport,INTEGER,read-only,,current,true(1):false(2),An indication of whether the FCIP Entity supports PHB IP quality of service (QoS).
.1.3.6.1.2.1.224.1.1.4.1.8,FCIP-MGMT-MIB::fcipEntityStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object specifies the operational status of the row. When a management station sets the status to active(1), then the values for the objects fcipEntityName, fcipEntityAddressType, and fcipEntityAddress should be supplied as part of the set request. The values of the objects fcipEntityName, fcipEntityAddressType, and fcipEntityAddress can be changed if the row status is in active state. The object fcipEntityTcpConnPort takes the default value zero(0), if no value is supplied at the time of row creation. Setting the status to destroy(6) deletes the specified FCIP entity instance row from the table. It also deletes all the rows corresponding to the specified FCIP entity from the fcipLinkTable and fcipTcpConnTable tables.
.1.3.6.1.2.1.224.1.1.5,FCIP-MGMT-MIB::fcipLinkTable,,not-accessible,,current,,Information about FCIP links that exist on this device.
.1.3.6.1.2.1.224.1.1.5.1,FCIP-MGMT-MIB::fcipLinkEntry,,not-accessible,fcipEntityId:fcipLinkIndex,current,,A conceptual row of the FCIP link table containing information about a particular FCIP link. The values of the read-create objects in this table are persistent across system restarts.
.1.3.6.1.2.1.224.1.1.5.1.1,FCIP-MGMT-MIB::fcipLinkIndex,Unsigned32,not-accessible,,current,,An arbitrary integer that uniquely identifies one FCIP link within an FCIP entity.
.1.3.6.1.2.1.224.1.1.5.1.2,FCIP-MGMT-MIB::fcipLinkIfIndex,Integer32,read-only,,current,,The ifIndex value of the virtual interface corresponding to the FCIP Link running over TCP/IP.
.1.3.6.1.2.1.224.1.1.5.1.3,FCIP-MGMT-MIB::fcipLinkCost,Unsigned32,read-create,,current,,The FSPF cost associated with this FCIP Link.
.1.3.6.1.2.1.224.1.1.5.1.4,FCIP-MGMT-MIB::fcipLinkLocalFcipEntityMode,INTEGER,read-only,,current,ePortMode(1):bPortMode(2),The mode of the local end of the FCIP link.
.1.3.6.1.2.1.224.1.1.5.1.5,FCIP-MGMT-MIB::fcipLinkLocalFcipEntityAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address contained in the corresponding instance of fcipLinkLocalFcipEntityAddress. Only address types IPv4 and IPv6 are supported.
.1.3.6.1.2.1.224.1.1.5.1.6,FCIP-MGMT-MIB::fcipLinkLocalFcipEntityAddress,OCTET,read-create,,current,,The Internet address for the local end of this FCIP Link. The format of this object is determined by the value of the fcipLinkLocalFcipEntityAddressType object.
.1.3.6.1.2.1.224.1.1.5.1.7,FCIP-MGMT-MIB::fcipLinkRemFcipEntityWWN,OCTET,read-create,,current,,The World Wide Name of the remote FC Fabric Entity.
.1.3.6.1.2.1.224.1.1.5.1.8,FCIP-MGMT-MIB::fcipLinkRemFcipEntityId,OCTET,read-create,,current,,The remote FCIP entity's identifier.
.1.3.6.1.2.1.224.1.1.5.1.9,FCIP-MGMT-MIB::fcipLinkRemFcipEntityAddressType,INTEGER,read-create,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of Internet address contained in the corresponding instance of fcipLinkRemFcipEntityAddress. Only address types IPv4 and IPv6 are supported.
.1.3.6.1.2.1.224.1.1.5.1.10,FCIP-MGMT-MIB::fcipLinkRemFcipEntityAddress,OCTET,read-create,,current,,The Internet address for the remote end of this FCIP Link. The format of this object is determined by the value of the fcipLinkRemFcipEntityAddressType object.
.1.3.6.1.2.1.224.1.1.5.1.11,FCIP-MGMT-MIB::fcipLinkStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object specifies the operational status of the row. The values of objects fcipLinkLocalFcipEntityAddressType, fcipLinkLocalFcipEntityAddress, fcipLinkRemFcipEntityWWN, fcipLinkRemFcipEntityId, fcipLinkRemFcipEntityAddressType, and fcipLinkRemFcipEntityAddress can be changed if the row is in active(1) state. The object fcipLinkCost is set to the value zero(0) if no value is supplied at the time of row creation. Setting the status to destroy(6) deletes the specified FCIP link from the table. It also deletes all rows corresponding to the specified FCIP link from the fcipTcpConnTable table.
.1.3.6.1.2.1.224.1.1.5.1.12,FCIP-MGMT-MIB::fcipLinkCreateTime,TimeTicks,read-only,,current,,The value of sysUpTime when this entry was last created.
.1.3.6.1.2.1.224.1.1.6,FCIP-MGMT-MIB::fcipTcpConnTable,,not-accessible,,current,,Information about existing TCP connections. Each FCIP link within an FCIP entity manages one or more TCP connections. The FCIP entity employs a Data Engine for each TCP connection for handling FC frame encapsulation, de-encapsulation, and transmission of FCIP frames on the connection.
.1.3.6.1.2.1.224.1.1.6.1,FCIP-MGMT-MIB::fcipTcpConnEntry,,not-accessible,fcipEntityId:fcipLinkIndex:fcipTcpConnLocalPort:fcipTcpConnRemPort,current,,A conceptual row of the FCIP TCP Connection table containing information about a particular TCP connection.
.1.3.6.1.2.1.224.1.1.6.1.1,FCIP-MGMT-MIB::fcipTcpConnLocalPort,Unsigned32,not-accessible,,current,,The local port number for this TCP connection.
.1.3.6.1.2.1.224.1.1.6.1.2,FCIP-MGMT-MIB::fcipTcpConnRemPort,Unsigned32,not-accessible,,current,,The remote port number for this TCP connection.
.1.3.6.1.2.1.224.1.1.6.1.3,FCIP-MGMT-MIB::fcipTcpConnRWSize,Unsigned32,read-only,,current,,The default maximum TCP Receiver Window size for this TCP connection.
.1.3.6.1.2.1.224.1.1.6.1.4,FCIP-MGMT-MIB::fcipTcpConnMSS,Unsigned32,read-only,,current,,The TCP Maximum Segment Size (MSS) for this TCP connection.
.1.3.6.1.2.1.224.1.1.7,FCIP-MGMT-MIB::fcipDynamicRouteTable,,not-accessible,,current,,Information about dynamically discovered routing information. The FCIP device may use the SLPv2 protocol in conjunction with other protocols (say, FSPF) for dynamically discovering other FCIP entities and may populate this table with FCIP link information for each Destination Address Identifier.
.1.3.6.1.2.1.224.1.1.7.1,FCIP-MGMT-MIB::fcipDynamicRouteEntry,,not-accessible,fcipEntityId:fcipDynamicRouteDID,current,,A conceptual row of the FCIP Dynamic Route Table containing information about a particular FCIP route.
.1.3.6.1.2.1.224.1.1.7.1.1,FCIP-MGMT-MIB::fcipDynamicRouteDID,OCTET,not-accessible,,current,,8-bit ID of a Fibre Channel Domain that is reachable from this FCIP device.
.1.3.6.1.2.1.224.1.1.7.1.2,FCIP-MGMT-MIB::fcipDynamicRouteLinkIndex,Unsigned32,read-only,,current,,The FCIP Link used to reach the domain specified by the corresponding instance of fcipDynamicRouteDID. The link identified by a value of this object is the same FCIP link as identified by the same value of fcipLinkIndex for the same FCIP entity.
.1.3.6.1.2.1.224.1.1.8,FCIP-MGMT-MIB::fcipStaticRouteTable,,not-accessible,,current,,Information about static route entries configured by the Network Admin. In the absence of dynamic discovery of remote FCIP entities, the Network Manager will figure out all remote FCIP devices that are reachable from this device and populate this table with FCIP link information for each Domain ID. At any time, both static and dynamic routing can be active, and an entry in the static route table for a given DID takes precedence over the entry in the dynamic route table for the same Domain ID.
.1.3.6.1.2.1.224.1.1.8.1,FCIP-MGMT-MIB::fcipStaticRouteEntry,,not-accessible,fcipEntityId:fcipStaticRouteDID,current,,A conceptual row of the FCIP Static Route Table containing information about a particular FCIP route. The values of the read-create objects in this table are persistent across system restarts.
.1.3.6.1.2.1.224.1.1.8.1.1,FCIP-MGMT-MIB::fcipStaticRouteDID,OCTET,not-accessible,,current,,8-bit ID of a Fibre Channel Domain that is reachable from this FCIP device.
.1.3.6.1.2.1.224.1.1.8.1.2,FCIP-MGMT-MIB::fcipStaticRouteLinkIndex,Unsigned32,read-create,,current,,The FCIP Link used to reach the domain specified by the corresponding instance of fcipStaticRouteDID. The link identified by a value of this object is the same FCIP link as identified by the same value of fcipLinkIndex for the same FCIP entity.
.1.3.6.1.2.1.224.1.1.8.1.3,FCIP-MGMT-MIB::fcipStaticRouteStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object specifies the operational status of the row. When a management station sets the status to active(1), the values for the object fcipStaticRouteLinkIndex should be supplied as part of the set request. Setting the status to destroy(6) deletes the specified FCIP static route entry from the table.
.1.3.6.1.2.1.224.1.1.9,FCIP-MGMT-MIB::fcipDiscoveryDomainTable,,not-accessible,,current,,Information about FCIP Discovery Domains. Each FCIP Discovery Domain is associated with one or more FCIP entities.
.1.3.6.1.2.1.224.1.1.9.1,FCIP-MGMT-MIB::fcipDiscoveryDomainEntry,,not-accessible,fcipEntityId:fcipDiscoveryDomainIndex,current,,A conceptual row of the FCIP Discovery Domain Table containing information about a particular FCIP Discovery Domain that is associated with one or more FCIP entities. The values of the read-write object fcipDiscoveryDomainName are persistent across system restarts.
.1.3.6.1.2.1.224.1.1.9.1.1,FCIP-MGMT-MIB::fcipDiscoveryDomainIndex,Unsigned32,not-accessible,,current,,An integer that uniquely identifies an FCIP Discovery Domain associated with this FCIP entity.
.1.3.6.1.2.1.224.1.1.9.1.2,FCIP-MGMT-MIB::fcipDiscoveryDomainName,OCTET,read-write,,current,,The name of this FCIP Discovery Domain.
.1.3.6.1.2.1.224.1.1.10,FCIP-MGMT-MIB::fcipLinkErrorsTable,,not-accessible,,current,,A list of error counters for FCIP Links. Each counter records the number of times a particular error happened that caused a TCP connection to close down.
.1.3.6.1.2.1.224.1.1.10.1,FCIP-MGMT-MIB::fcipLinkErrorsEntry,,not-accessible,fcipEntityId:fcipLinkIndex,current,,A conceptual row of the FCIP Link Errors Table containing error counters for an FCIP Link.
.1.3.6.1.2.1.224.1.1.10.1.1,FCIP-MGMT-MIB::fcipLinkFcipLossofFcSynchs,Counter32,read-only,,current,,The number of times FC synchronization was lost on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.2,FCIP-MGMT-MIB::fcipLinkFcipEncapErrors,Counter32,read-only,,current,,The number of FCIP frames received with encapsulation errors such as improper header, format, or length. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.3,FCIP-MGMT-MIB::fcipLinkFcipNotReceivedSfResps,Counter32,read-only,,current,,The number of times an FCIP Special Frame Response was expected but not received on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.4,FCIP-MGMT-MIB::fcipLinkFcipSfRespMismatches,Counter32,read-only,,current,,The number of times FCIP Special Frame Bytes mismatch happened on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.5,FCIP-MGMT-MIB::fcipLinkFcipSfInvalidNonces,Counter32,read-only,,current,,The number of times FCIP Special Frame Invalid Connection Nonce happened on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.6,FCIP-MGMT-MIB::fcipLinkFcipReceivedSfDuplicates,Counter32,read-only,,current,,The number of times duplicate FCIP Special Frames were received on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.7,FCIP-MGMT-MIB::fcipLinkFcipSfInvalidWWNs,Counter32,read-only,,current,,The number of times FCIP Special Frames with invalid destination FC Fabric Entity WWN were received on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.8,FCIP-MGMT-MIB::fcipLinkFcipBB2LkaTimeOuts,Counter32,read-only,,current,,The number of FC Keep Alive Time-outs that occurred on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.9,FCIP-MGMT-MIB::fcipLinkFcipSntpExpiredTimeStamps,Counter32,read-only,,current,,The number of frames discarded due to an expired Simple Network Time Protocol (SNTP) timestamp on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.10,FCIP-MGMT-MIB::fcipLinkTcpTooManyErrors,Counter32,read-only,,current,,The number of TCP connections that closed down on this FCIP Link due to too many errors on the connection. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.11,FCIP-MGMT-MIB::fcipLinkTcpExcessiveDroppedDatagrams,Counter32,read-only,,current,,The number of TCP connections that closed down on this FCIP Link due to an excessive number of dropped FCIP packets. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.1.1.10.1.12,FCIP-MGMT-MIB::fcipLinkTcpSaParamMismatches,Counter32,read-only,,current,,The number of times TCP connections with Security Association parameter mismatches were closed down on this FCIP Link. The last discontinuity of this counter is indicated by fcipLinkCreateTime.
.1.3.6.1.2.1.224.2,FCIP-MGMT-MIB::fcipConformance,,,,,,
.1.3.6.1.2.1.224.2.1,FCIP-MGMT-MIB::fcipCompliances,,,,,,
.1.3.6.1.2.1.224.2.1.1,FCIP-MGMT-MIB::fcipCompliance,,,,,,Compliance statement for FCIP MIB.
.1.3.6.1.2.1.224.2.2,FCIP-MGMT-MIB::fcipGroups,,,,,,
.1.3.6.1.2.1.224.2.2.1,FCIP-MGMT-MIB::fcipEntityScalarGroup,,,,,,Collection of scalar objects applicable to all FCIP instances.
.1.3.6.1.2.1.224.2.2.2,FCIP-MGMT-MIB::fcipEntityInstanceGroup,,,,,,A collection of objects providing information about FCIP instances.
.1.3.6.1.2.1.224.2.2.3,FCIP-MGMT-MIB::fcipLinkGroup,,,,,,A collection of objects providing information about FCIP Links.
.1.3.6.1.2.1.224.2.2.4,FCIP-MGMT-MIB::fcipTcpConnGroup,,,,,,A collection of objects providing information about FCIP TCP connections.
.1.3.6.1.2.1.224.2.2.5,FCIP-MGMT-MIB::fcipDiscoveryDomainGroup,,,,,,A collection of objects providing information about FCIP Discovery Domains.
.1.3.6.1.2.1.224.2.2.6,FCIP-MGMT-MIB::fcipLinkErrorsGroup,,,,,,A collection of objects providing information about FCIP link errors.
.1.3.6.1.2.1.224.2.2.7,FCIP-MGMT-MIB::fcipDynamicRouteGroup,,,,,,A collection of objects providing information about FCIP dynamic routes.
.1.3.6.1.2.1.224.2.2.8,FCIP-MGMT-MIB::fcipStaticRouteGroup,,,,,,A collection of objects providing information about FCIP static routes.
.1.3.6.1.2.1.225,IANA-SMF-MIB::ianaSmfMIB,,,,,,This MIB module defines the IANAsmfOpModeIdTC and IANAsmfRssaIdTC Textual Conventions, and thus the enumerated values of the smfCapabilitiesOpModeID and smfCapabilitiesRssaID objects defined in the SMF-MIB.
.1.3.6.1.2.1.226,LOWPAN-MIB::lowpanMIB,,,,,,The MIB module for monitoring nodes implementing the IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN) protocol. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.226.0,LOWPAN-MIB::lowpanNotifications,,,,,,
.1.3.6.1.2.1.226.1,LOWPAN-MIB::lowpanObjects,,,,,,
.1.3.6.1.2.1.226.1.1,LOWPAN-MIB::lowpanStats,,,,,,
.1.3.6.1.2.1.226.1.1.1,LOWPAN-MIB::lowpanReasmTimeout,Unsigned32,read-only,,current,,The maximum number of seconds that received fragments are held while they are awaiting reassembly at this entity.
.1.3.6.1.2.1.226.1.1.2,LOWPAN-MIB::lowpanInReceives,Counter32,read-only,,current,,The total number of 6LoWPAN datagrams received, including those received in error.
.1.3.6.1.2.1.226.1.1.3,LOWPAN-MIB::lowpanInHdrErrors,Counter32,read-only,,current,,The number of received 6LoWPAN datagrams discarded due to errors in their headers, including unknown dispatch values.
.1.3.6.1.2.1.226.1.1.4,LOWPAN-MIB::lowpanInMeshReceives,Counter32,read-only,,current,,The number of received 6LoWPAN datagrams with a MESH header.
.1.3.6.1.2.1.226.1.1.5,LOWPAN-MIB::lowpanInMeshForwds,Counter32,read-only,,current,,The number of received 6LoWPAN datagrams requiring mesh forwarding.
.1.3.6.1.2.1.226.1.1.6,LOWPAN-MIB::lowpanInMeshDelivers,Counter32,read-only,,current,,The number of received 6LoWPAN datagrams with a MESH header delivered to the local system.
.1.3.6.1.2.1.226.1.1.7,LOWPAN-MIB::lowpanInReasmReqds,Counter32,read-only,,current,,The number of received 6LoWPAN fragments that needed to be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN datagrams.
.1.3.6.1.2.1.226.1.1.8,LOWPAN-MIB::lowpanInReasmFails,Counter32,read-only,,current,,The number of failures detected by the re-assembly algorithm (e.g., timeouts). Note that this is not necessarily a count of discarded 6LoWPAN fragments since implementations can lose track of the number of fragments by combining them as received.
.1.3.6.1.2.1.226.1.1.9,LOWPAN-MIB::lowpanInReasmOKs,Counter32,read-only,,current,,The number of IPv6 packets successfully reassembled.
.1.3.6.1.2.1.226.1.1.10,LOWPAN-MIB::lowpanInCompReqds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams requiring header decompression.
.1.3.6.1.2.1.226.1.1.11,LOWPAN-MIB::lowpanInCompFails,Counter32,read-only,,current,,The number of 6LoWPAN datagrams where header decompression failed (e.g., because the necessary context information was not available).
.1.3.6.1.2.1.226.1.1.12,LOWPAN-MIB::lowpanInCompOKs,Counter32,read-only,,current,,The number of 6LoWPAN datagrams where header decompression was successful.
.1.3.6.1.2.1.226.1.1.13,LOWPAN-MIB::lowpanInDiscards,Counter32,read-only,,current,,The number of received 6LoWPAN datagrams that were discarded (e.g., for lack of buffer space) even though no problems were encountered to prevent their continued processing. Note that this counter does not include any datagrams discarded due to a reassembly failure or a compression failure.
.1.3.6.1.2.1.226.1.1.14,LOWPAN-MIB::lowpanInDelivers,Counter32,read-only,,current,,The total number of IPv6 packets successfully delivered to the IPv6 layer.
.1.3.6.1.2.1.226.1.1.15,LOWPAN-MIB::lowpanOutRequests,Counter32,read-only,,current,,The total number of IPv6 packets supplied by the IPv6 layer.
.1.3.6.1.2.1.226.1.1.16,LOWPAN-MIB::lowpanOutCompReqds,Counter32,read-only,,current,,The total number of IPv6 packets for which header compression was attempted.
.1.3.6.1.2.1.226.1.1.17,LOWPAN-MIB::lowpanOutCompFails,Counter32,read-only,,current,,The total number of IPv6 packets for which header compression failed.
.1.3.6.1.2.1.226.1.1.18,LOWPAN-MIB::lowpanOutCompOKs,Counter32,read-only,,current,,The total number of IPv6 packets for which header compression was successful.
.1.3.6.1.2.1.226.1.1.19,LOWPAN-MIB::lowpanOutFragReqds,Counter32,read-only,,current,,The number of IPv6 packets that required fragmentation in order to be transmitted.
.1.3.6.1.2.1.226.1.1.20,LOWPAN-MIB::lowpanOutFragFails,Counter32,read-only,,current,,The number of IPv6 packets that have been discarded because fragmentation failed.
.1.3.6.1.2.1.226.1.1.21,LOWPAN-MIB::lowpanOutFragOKs,Counter32,read-only,,current,,The number of IPv6 packets that have been successfully fragmented.
.1.3.6.1.2.1.226.1.1.22,LOWPAN-MIB::lowpanOutFragCreates,Counter32,read-only,,current,,The number of 6LoWPAN fragments that have been generated as a result of fragmentation. This includes both FRAG1 and FRAGN 6LoWPAN datagrams.
.1.3.6.1.2.1.226.1.1.23,LOWPAN-MIB::lowpanOutMeshHopLimitExceeds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams with a MESH header that were dropped because the hop limit was exceeded.
.1.3.6.1.2.1.226.1.1.24,LOWPAN-MIB::lowpanOutMeshNoRoutes,Counter32,read-only,,current,,The number of 6LoWPAN datagrams with a MESH header that were dropped because there was no forwarding information available.
.1.3.6.1.2.1.226.1.1.25,LOWPAN-MIB::lowpanOutMeshRequests,Counter32,read-only,,current,,The number of 6LoWPAN datagrams requiring MESH header encapsulation.
.1.3.6.1.2.1.226.1.1.26,LOWPAN-MIB::lowpanOutMeshForwds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams with a MESH header for which suitable forwarding information was available.
.1.3.6.1.2.1.226.1.1.27,LOWPAN-MIB::lowpanOutMeshTransmits,Counter32,read-only,,current,,The number of 6LoWPAN datagrams with a MESH header created.
.1.3.6.1.2.1.226.1.1.28,LOWPAN-MIB::lowpanOutDiscards,Counter32,read-only,,current,,The number of IPv6 packets that were discarded (e.g., for lack of buffer space) even though no problem was encountered to prevent their transmission to their destination.
.1.3.6.1.2.1.226.1.1.29,LOWPAN-MIB::lowpanOutTransmits,Counter32,read-only,,current,,The total number of 6LoWPAN datagram that this entity supplied to the lower layers for transmission.
.1.3.6.1.2.1.226.1.2,LOWPAN-MIB::lowpanIfStatsTable,,not-accessible,,current,,A table providing per-interface statistics.
.1.3.6.1.2.1.226.1.2.1,LOWPAN-MIB::lowpanIfStatsEntry,,not-accessible,ifIndex,current,,An entry providing statistics for a specific interface.
.1.3.6.1.2.1.226.1.2.1.1,LOWPAN-MIB::lowpanIfReasmTimeout,Unsigned32,read-only,,current,,The maximum number of seconds that received fragments are held while they are awaiting reassembly at this interface.
.1.3.6.1.2.1.226.1.2.1.2,LOWPAN-MIB::lowpanIfInReceives,Counter32,read-only,,current,,The total number of 6LoWPAN datagrams received on this interface, including those received in error.
.1.3.6.1.2.1.226.1.2.1.3,LOWPAN-MIB::lowpanIfInHdrErrors,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface that were discarded due to errors in their headers, including unknown dispatch values.
.1.3.6.1.2.1.226.1.2.1.4,LOWPAN-MIB::lowpanIfInMeshReceives,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface with a MESH header.
.1.3.6.1.2.1.226.1.2.1.5,LOWPAN-MIB::lowpanIfInMeshForwds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface requiring mesh forwarding.
.1.3.6.1.2.1.226.1.2.1.6,LOWPAN-MIB::lowpanIfInMeshDelivers,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface with a MESH header delivered to the local system.
.1.3.6.1.2.1.226.1.2.1.7,LOWPAN-MIB::lowpanIfInReasmReqds,Counter32,read-only,,current,,The number of 6LoWPAN fragments received on this interface that needed to be reassembled. This includes both FRAG1 and FRAGN 6LoWPAN datagrams.
.1.3.6.1.2.1.226.1.2.1.8,LOWPAN-MIB::lowpanIfInReasmFails,Counter32,read-only,,current,,The number of failures detected by the reassembly algorithm (e.g., timeouts) for datagrams received on this interface. Note that this is not necessarily a count of discarded 6LoWPAN fragments since implementations can lose track of the number of fragments by combining them as received.
.1.3.6.1.2.1.226.1.2.1.9,LOWPAN-MIB::lowpanIfInReasmOKs,Counter32,read-only,,current,,The number of IPv6 packets successfully reassembled from fragments received on this interface.
.1.3.6.1.2.1.226.1.2.1.10,LOWPAN-MIB::lowpanIfInCompReqds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface requiring header decompression.
.1.3.6.1.2.1.226.1.2.1.11,LOWPAN-MIB::lowpanIfInCompFails,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface where header decompression failed (e.g., because the necessary context information was not available).
.1.3.6.1.2.1.226.1.2.1.12,LOWPAN-MIB::lowpanIfInCompOKs,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface where header decompression was successful.
.1.3.6.1.2.1.226.1.2.1.13,LOWPAN-MIB::lowpanIfInDiscards,Counter32,read-only,,current,,The number of 6LoWPAN datagrams received on this interface that were discarded (e.g., for lack of buffer space) even though no problems were encountered to prevent their continued processing. Note that this counter does not include any datagrams discarded due to a reassembly failure or a compression failure.
.1.3.6.1.2.1.226.1.2.1.14,LOWPAN-MIB::lowpanIfInDelivers,Counter32,read-only,,current,,The total number of IPv6 packets received on this interface that were successfully delivered to the IPv6 layer.
.1.3.6.1.2.1.226.1.2.1.15,LOWPAN-MIB::lowpanIfOutRequests,Counter32,read-only,,current,,The total number of IPv6 packets supplied by the IPv6 layer to be sent over this interface.
.1.3.6.1.2.1.226.1.2.1.16,LOWPAN-MIB::lowpanIfOutCompReqds,Counter32,read-only,,current,,The total number of IPv6 packets to be sent over this interface for which header compression was attempted.
.1.3.6.1.2.1.226.1.2.1.17,LOWPAN-MIB::lowpanIfOutCompFails,Counter32,read-only,,current,,The total number of IPv6 packets to be sent over this interface for which header compression failed.
.1.3.6.1.2.1.226.1.2.1.18,LOWPAN-MIB::lowpanIfOutCompOKs,Counter32,read-only,,current,,The total number of IPv6 packets to be sent over this interface for which header compression was successful.
.1.3.6.1.2.1.226.1.2.1.19,LOWPAN-MIB::lowpanIfOutFragReqds,Counter32,read-only,,current,,The number of IPv6 packets to be sent over this interface that required fragmentation in order to be transmitted.
.1.3.6.1.2.1.226.1.2.1.20,LOWPAN-MIB::lowpanIfOutFragFails,Counter32,read-only,,current,,The number of IPv6 packets to be sent over this interface that have been discarded because fragmentation failed.
.1.3.6.1.2.1.226.1.2.1.21,LOWPAN-MIB::lowpanIfOutFragOKs,Counter32,read-only,,current,,The number of IPv6 packets to be sent over this interface that have been successfully fragmented.
.1.3.6.1.2.1.226.1.2.1.22,LOWPAN-MIB::lowpanIfOutFragCreates,Counter32,read-only,,current,,The number of 6LoWPAN fragments that have been generated on this interface as a result of fragmentation. This includes both FRAG1 and FRAGN 6LoWPAN datagrams.
.1.3.6.1.2.1.226.1.2.1.23,LOWPAN-MIB::lowpanIfOutMeshHopLimitExceeds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams to be sent on this interface with a MESH header that were dropped because the hop limit was exceeded.
.1.3.6.1.2.1.226.1.2.1.24,LOWPAN-MIB::lowpanIfOutMeshNoRoutes,Counter32,read-only,,current,,The number of 6LoWPAN datagrams to be sent on this interface with a MESH header that were dropped because there was no forwarding information available.
.1.3.6.1.2.1.226.1.2.1.25,LOWPAN-MIB::lowpanIfOutMeshRequests,Counter32,read-only,,current,,The number of 6LoWPAN datagrams to be sent on this interface requiring MESH header encapsulation.
.1.3.6.1.2.1.226.1.2.1.26,LOWPAN-MIB::lowpanIfOutMeshForwds,Counter32,read-only,,current,,The number of 6LoWPAN datagrams to be sent on this interface with a MESH header for which suitable forwarding information was available.
.1.3.6.1.2.1.226.1.2.1.27,LOWPAN-MIB::lowpanIfOutMeshTransmits,Counter32,read-only,,current,,The number of 6LoWPAN datagrams to be sent on this interface with a MESH header created.
.1.3.6.1.2.1.226.1.2.1.28,LOWPAN-MIB::lowpanIfOutDiscards,Counter32,read-only,,current,,The number of IPv6 packets to be sent over this interface that were discarded (e.g., for lack of buffer space) even though no problem was encountered to prevent their transmission to their destination.
.1.3.6.1.2.1.226.1.2.1.29,LOWPAN-MIB::lowpanIfOutTransmits,Counter32,read-only,,current,,The total number of 6LoWPAN datagrams to be sent on this interface that this entity supplied to the lower layers for transmission.
.1.3.6.1.2.1.226.2,LOWPAN-MIB::lowpanConformance,,,,,,
.1.3.6.1.2.1.226.2.1,LOWPAN-MIB::lowpanGroups,,,,,,
.1.3.6.1.2.1.226.2.1.1,LOWPAN-MIB::lowpanStatsGroup,,,,,,A collection of objects providing information and statistics about the processing of 6LoWPAN datagrams, excluding counters covering the processing of datagrams with a MESH header.
.1.3.6.1.2.1.226.2.1.2,LOWPAN-MIB::lowpanStatsMeshGroup,,,,,,A collection of objects providing information and statistics about the processing of 6LoWPAN datagrams with a MESH header.
.1.3.6.1.2.1.226.2.1.3,LOWPAN-MIB::lowpanIfStatsGroup,,,,,,A collection of objects providing per-interface information and statistics about the processing of 6LoWPAN datagrams, excluding counters covering the processing of datagrams with a MESH header.
.1.3.6.1.2.1.226.2.1.4,LOWPAN-MIB::lowpanIfStatsMeshGroup,,,,,,A collection of objects providing per-interface information and statistics about the processing of 6LoWPAN datagrams with a MESH header.
.1.3.6.1.2.1.226.2.2,LOWPAN-MIB::lowpanCompliances,,,,,,
.1.3.6.1.2.1.226.2.2.1,LOWPAN-MIB::lowpanCompliance,,,,,,Compliance statement for systems that implement 6LoWPAN.
.1.3.6.1.2.1.227,PCE-PCEP-MIB::pcePcepMIB,,,,,,This MIB module defines a collection of objects for managing the Path Computation Element Communication Protocol (PCEP). Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.227.0,PCE-PCEP-MIB::pcePcepNotifications,,,,,,
.1.3.6.1.2.1.227.0.1,PCE-PCEP-MIB::pcePcepSessUp,,,,,,This notification is sent when the value of pcePcepSessState enters the sessionUp state.
.1.3.6.1.2.1.227.0.2,PCE-PCEP-MIB::pcePcepSessDown,,,,,,This notification is sent when the value of pcePcepSessState leaves the sessionUp state.
.1.3.6.1.2.1.227.0.3,PCE-PCEP-MIB::pcePcepSessLocalOverload,,,,,,This notification is sent when the local PCEP entity enters overload state for a peer.
.1.3.6.1.2.1.227.0.4,PCE-PCEP-MIB::pcePcepSessLocalOverloadClear,,,,,,This notification is sent when the local PCEP entity leaves overload state for a peer.
.1.3.6.1.2.1.227.0.5,PCE-PCEP-MIB::pcePcepSessPeerOverload,,,,,,This notification is sent when a peer enters overload state.
.1.3.6.1.2.1.227.0.6,PCE-PCEP-MIB::pcePcepSessPeerOverloadClear,,,,,,This notification is sent when a peer leaves overload state.
.1.3.6.1.2.1.227.1,PCE-PCEP-MIB::pcePcepObjects,,,,,,
.1.3.6.1.2.1.227.1.1,PCE-PCEP-MIB::pcePcepEntityTable,,not-accessible,,current,,This table contains information about local PCEP entities. The entries in this table are read-only.
.1.3.6.1.2.1.227.1.1.1,PCE-PCEP-MIB::pcePcepEntityEntry,,not-accessible,pcePcepEntityIndex,current,,This entry represents a local PCEP entity.
.1.3.6.1.2.1.227.1.1.1.1,PCE-PCEP-MIB::pcePcepEntityIndex,Unsigned32,not-accessible,,current,,This index is used to uniquely identify the PCEP entity.
.1.3.6.1.2.1.227.1.1.1.2,PCE-PCEP-MIB::pcePcepEntityAdminStatus,INTEGER,read-only,,current,adminStatusUp(1):adminStatusDown(2),The administrative status of this PCEP entity. This is the desired operational status as currently set by an operator or by default in the implementation. The value of pcePcepEntityOperStatus represents the current status of an attempt to reach this desired status.
.1.3.6.1.2.1.227.1.1.1.3,PCE-PCEP-MIB::pcePcepEntityOperStatus,INTEGER,read-only,,current,operStatusUp(1):operStatusDown(2):operStatusGoingUp(3):operStatusGoingDown(4):operStatusFailed(5):operStatusFailedPerm(6),The operational status of the PCEP entity. It takes one of the following values. - operStatusUp(1): the PCEP entity is active. - operStatusDown(2): the PCEP entity is inactive. - operStatusGoingUp(3): the PCEP entity is activating. - operStatusGoingDown(4): the PCEP entity is deactivating. - operStatusFailed(5): the PCEP entity has failed and will recover when possible. - operStatusFailedPerm(6): the PCEP entity has failed and will not recover without operator intervention.
.1.3.6.1.2.1.227.1.1.1.4,PCE-PCEP-MIB::pcePcepEntityAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the PCEP entity's Internet address. This object specifies how the value of the pcePcepEntityAddr object should be interpreted. Only values unknown(0), ipv4(1), or ipv6(2) are supported.
.1.3.6.1.2.1.227.1.1.1.5,PCE-PCEP-MIB::pcePcepEntityAddr,OCTET,read-only,,current,,The local Internet address of this PCEP entity. The type is given by pcePcepEntityAddrType. If operating as a PCE server, the PCEP entity listens on this address. If operating as a PCC, the PCEP entity binds outgoing TCP connections to this address. It is possible for the PCEP entity to operate both as a PCC and a PCE server, in which case it uses this address both to listen for incoming TCP connections and to bind outgoing TCP connections.
.1.3.6.1.2.1.227.1.1.1.6,PCE-PCEP-MIB::pcePcepEntityConnectTimer,Unsigned32,read-only,,current,,The time that the PCEP entity will wait to establish a TCP connection with a peer. If a TCP connection is not established within this time, then PCEP aborts the session setup attempt.
.1.3.6.1.2.1.227.1.1.1.7,PCE-PCEP-MIB::pcePcepEntityConnectMaxRetry,Unsigned32,read-only,,current,,The maximum number of times the system tries to establish a TCP connection to a peer before the session with the peer transitions to the idle state. When the session transitions to the idle state: - pcePcepPeerSessionExists transitions to false(2). - the associated PcePcepSessEntry is deleted. - a backoff timer runs before the session is tried again.
.1.3.6.1.2.1.227.1.1.1.8,PCE-PCEP-MIB::pcePcepEntityInitBackoffTimer,Unsigned32,read-only,,current,,The initial backoff time for retrying a failed session setup attempt to a peer. The backoff time increases for each failed session setup attempt, until a maximum backoff time is reached. The maximum backoff time is pcePcepEntityMaxBackoffTimer.
.1.3.6.1.2.1.227.1.1.1.9,PCE-PCEP-MIB::pcePcepEntityMaxBackoffTimer,Unsigned32,read-only,,current,,The maximum backoff time for retrying a failed session setup attempt to a peer. The backoff time increases for each failed session setup attempt, until this maximum value is reached. Session setup attempts then repeats periodically without any further increase in backoff time.
.1.3.6.1.2.1.227.1.1.1.10,PCE-PCEP-MIB::pcePcepEntityOpenWaitTimer,Unsigned32,read-only,,current,,The time that the PCEP entity will wait to receive an Open message from a peer after the TCP connection has come up. If no Open message is received within this time, then PCEP terminates the TCP connection and deletes the associated PcePcepSessEntry.
.1.3.6.1.2.1.227.1.1.1.11,PCE-PCEP-MIB::pcePcepEntityKeepWaitTimer,Unsigned32,read-only,,current,,The time that the PCEP entity will wait to receive a Keepalive or PCErr message from a peer during session initialization after receiving an Open message. If no Keepalive or PCErr message is received within this time, then PCEP terminates the TCP connection and deletes the associated PcePcepSessEntry.
.1.3.6.1.2.1.227.1.1.1.12,PCE-PCEP-MIB::pcePcepEntityKeepAliveTimer,Unsigned32,read-only,,current,,The Keepalive transmission timer that this PCEP entity will propose in the initial OPEN message of each session it is involved in. This is the maximum time between two consecutive messages sent to a peer. Zero means that the PCEP entity prefers not to send Keepalives at all. Note that the actual Keepalive transmission intervals, in either direction of an active PCEP session, are determined by negotiation between the peers as specified by RFC 5440, and so may differ from this configured value. For the actually negotiated values (per session), see pcePcepSessKeepaliveTimer and pcePcepSessPeerKeepaliveTimer.
.1.3.6.1.2.1.227.1.1.1.13,PCE-PCEP-MIB::pcePcepEntityDeadTimer,Unsigned32,read-only,,current,,The DeadTimer that this PCEP entity will propose in the initial OPEN message of each session it is involved in. This is the time after which a peer should declare a session down if it does not receive any PCEP messages. Zero suggests that the peer does not run a DeadTimer at all.
.1.3.6.1.2.1.227.1.1.1.14,PCE-PCEP-MIB::pcePcepEntityAllowNegotiation,INTEGER,read-only,,current,true(1):false(2),Whether the PCEP entity will permit negotiation of session parameters.
.1.3.6.1.2.1.227.1.1.1.15,PCE-PCEP-MIB::pcePcepEntityMaxKeepAliveTimer,Unsigned32,read-only,,current,,In PCEP session parameter negotiation, the maximum value that this PCEP entity will accept from a peer for the interval between Keepalive transmissions. Zero means that the PCEP entity will allow no Keepalive transmission at all.
.1.3.6.1.2.1.227.1.1.1.16,PCE-PCEP-MIB::pcePcepEntityMaxDeadTimer,Unsigned32,read-only,,current,,In PCEP session parameter negotiation, the maximum value that this PCEP entity will accept from a peer for the DeadTimer. Zero means that the PCEP entity will allow not running a DeadTimer.
.1.3.6.1.2.1.227.1.1.1.17,PCE-PCEP-MIB::pcePcepEntityMinKeepAliveTimer,Unsigned32,read-only,,current,,In PCEP session parameter negotiation, the minimum value that this PCEP entity will accept for the interval between Keepalive transmissions. Zero means that the PCEP entity insists on no Keepalive transmission at all.
.1.3.6.1.2.1.227.1.1.1.18,PCE-PCEP-MIB::pcePcepEntityMinDeadTimer,Unsigned32,read-only,,current,,In PCEP session parameter negotiation, the minimum value that this PCEP entity will accept for the DeadTimer. Zero means that the PCEP entity insists on not running a DeadTimer.
.1.3.6.1.2.1.227.1.1.1.19,PCE-PCEP-MIB::pcePcepEntitySyncTimer,Unsigned32,read-only,,current,,The value of SyncTimer is used in the case of a synchronized path computation request using the SVEC object. Consider the case where a PCReq message is received by a PCE that contains the SVEC object referring to M synchronized path computation requests. If after the expiration of the SyncTimer all the M path computation requests have not been received, a protocol error is triggered and the PCE MUST cancel the whole set of path computation requests. The aim of the SyncTimer is to avoid the storage of unused synchronized requests should one of them get lost for some reason (for example, a misbehaving PCC). A value of zero is returned if and only if the entity does not use the SyncTimer.
.1.3.6.1.2.1.227.1.1.1.20,PCE-PCEP-MIB::pcePcepEntityRequestTimer,Unsigned32,read-only,,current,,The maximum time that the PCEP entity will wait for a response to a PCReq message.
.1.3.6.1.2.1.227.1.1.1.21,PCE-PCEP-MIB::pcePcepEntityMaxSessions,Unsigned32,read-only,,current,,The maximum number of sessions involving this PCEP entity that can exist at any time.
.1.3.6.1.2.1.227.1.1.1.22,PCE-PCEP-MIB::pcePcepEntityMaxUnknownReqs,Unsigned32,read-only,,current,,The maximum number of unrecognized requests and replies that any session on this PCEP entity is willing to accept per minute before terminating the session. A PCRep message contains an unrecognized reply if it contains an RP object whose request ID does not correspond to any in-progress request sent by this PCEP entity. A PCReq message contains an unrecognized request if it contains an RP object whose request ID is zero.
.1.3.6.1.2.1.227.1.1.1.23,PCE-PCEP-MIB::pcePcepEntityMaxUnknownMsgs,Unsigned32,read-only,,current,,The maximum number of unknown messages that any session on this PCEP entity is willing to accept per minute before terminating the session.
.1.3.6.1.2.1.227.1.2,PCE-PCEP-MIB::pcePcepPeerTable,,not-accessible,,current,,This table contains information about peers known by the local PCEP entity. The entries in this table are read-only. This table gives peer information that spans PCEP sessions. Information about current PCEP sessions can be found in the pcePcepSessTable table.
.1.3.6.1.2.1.227.1.2.1,PCE-PCEP-MIB::pcePcepPeerEntry,,not-accessible,pcePcepEntityIndex:pcePcepPeerAddrType:pcePcepPeerAddr,current,,Information about a single peer that spans all PCEP sessions to that peer.
.1.3.6.1.2.1.227.1.2.1.1,PCE-PCEP-MIB::pcePcepPeerAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of the peer's Internet address. This object specifies how the value of the pcePcepPeerAddr object should be interpreted. Only values unknown(0), ipv4(1), or ipv6(2) are supported.
.1.3.6.1.2.1.227.1.2.1.2,PCE-PCEP-MIB::pcePcepPeerAddr,OCTET,not-accessible,,current,,The Internet address of the peer. The type is given by pcePcepPeerAddrType.
.1.3.6.1.2.1.227.1.2.1.3,PCE-PCEP-MIB::pcePcepPeerRole,INTEGER,read-only,,current,unknown(0):pcc(1):pce(2):pccAndPce(3),The role that this peer took the last time a session was established. It takes one of the following values. - unknown(0): this peer's role is not known. - pcc(1): this peer is a Path Computation Client (PCC). - pce(2): this peer is a Path Computation Element (PCE). - pccAndPce(3): this peer is both a PCC and a PCE.
.1.3.6.1.2.1.227.1.2.1.4,PCE-PCEP-MIB::pcePcepPeerDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that the information and statistics in this row were last reset.
.1.3.6.1.2.1.227.1.2.1.5,PCE-PCEP-MIB::pcePcepPeerInitiateSession,INTEGER,read-only,,current,true(1):false(2),Indicates whether the local PCEP entity initiates sessions to this peer or waits for the peer to initiate a session.
.1.3.6.1.2.1.227.1.2.1.6,PCE-PCEP-MIB::pcePcepPeerSessionExists,INTEGER,read-only,,current,true(1):false(2),Indicates whether a session with this peer currently exists.
.1.3.6.1.2.1.227.1.2.1.7,PCE-PCEP-MIB::pcePcepPeerNumSessSetupOK,Counter32,read-only,,current,,The number of PCEP sessions successfully established with the peer, including any current session. This counter is incremented each time a session with this peer is successfully established.
.1.3.6.1.2.1.227.1.2.1.8,PCE-PCEP-MIB::pcePcepPeerNumSessSetupFail,Counter32,read-only,,current,,The number of PCEP sessions with the peer that have been attempted but failed before being fully established. This counter is incremented each time a session retry to this peer fails.
.1.3.6.1.2.1.227.1.2.1.9,PCE-PCEP-MIB::pcePcepPeerSessionUpTime,TimeTicks,read-only,,current,,The value of sysUpTime the last time a session with this peer was successfully established. If pcePcepPeerNumSessSetupOK is zero, then this object contains zero.
.1.3.6.1.2.1.227.1.2.1.10,PCE-PCEP-MIB::pcePcepPeerSessionFailTime,TimeTicks,read-only,,current,,The value of sysUpTime the last time a session with this peer failed to be established. If pcePcepPeerNumSessSetupFail is zero, then this object contains zero.
.1.3.6.1.2.1.227.1.2.1.11,PCE-PCEP-MIB::pcePcepPeerSessionFailUpTime,TimeTicks,read-only,,current,,The value of sysUpTime the last time a session with this peer failed from active. If pcePcepPeerNumSessSetupOK is zero, then this object contains zero.
.1.3.6.1.2.1.227.1.2.1.12,PCE-PCEP-MIB::pcePcepPeerAvgRspTime,Unsigned32,read-only,,current,,The average response time for this peer. If an average response time has not been calculated for this peer, then this object has the value zero. If pcePcepPeerRole is pcc, then this field is meaningless and is set to zero.
.1.3.6.1.2.1.227.1.2.1.13,PCE-PCEP-MIB::pcePcepPeerLWMRspTime,Unsigned32,read-only,,current,,The smallest (low-water mark) response time seen from this peer. If no responses have been received from this peer, then this object has the value zero. If pcePcepPeerRole is pcc, then this field is meaningless and is set to zero.
.1.3.6.1.2.1.227.1.2.1.14,PCE-PCEP-MIB::pcePcepPeerHWMRspTime,Unsigned32,read-only,,current,,The greatest (high-water mark) response time seen from this peer. If no responses have been received from this peer, then this object has the value zero. If pcePcepPeerRole is pcc, then this field is meaningless and is set to zero.
.1.3.6.1.2.1.227.1.2.1.15,PCE-PCEP-MIB::pcePcepPeerNumPCReqSent,Counter32,read-only,,current,,The number of PCReq messages sent to this peer.
.1.3.6.1.2.1.227.1.2.1.16,PCE-PCEP-MIB::pcePcepPeerNumPCReqRcvd,Counter32,read-only,,current,,The number of PCReq messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.17,PCE-PCEP-MIB::pcePcepPeerNumPCRepSent,Counter32,read-only,,current,,The number of PCRep messages sent to this peer.
.1.3.6.1.2.1.227.1.2.1.18,PCE-PCEP-MIB::pcePcepPeerNumPCRepRcvd,Counter32,read-only,,current,,The number of PCRep messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.19,PCE-PCEP-MIB::pcePcepPeerNumPCErrSent,Counter32,read-only,,current,,The number of PCErr messages sent to this peer.
.1.3.6.1.2.1.227.1.2.1.20,PCE-PCEP-MIB::pcePcepPeerNumPCErrRcvd,Counter32,read-only,,current,,The number of PCErr messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.21,PCE-PCEP-MIB::pcePcepPeerNumPCNtfSent,Counter32,read-only,,current,,The number of PCNtf messages sent to this peer.
.1.3.6.1.2.1.227.1.2.1.22,PCE-PCEP-MIB::pcePcepPeerNumPCNtfRcvd,Counter32,read-only,,current,,The number of PCNtf messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.23,PCE-PCEP-MIB::pcePcepPeerNumKeepaliveSent,Counter32,read-only,,current,,The number of Keepalive messages sent to this peer.
.1.3.6.1.2.1.227.1.2.1.24,PCE-PCEP-MIB::pcePcepPeerNumKeepaliveRcvd,Counter32,read-only,,current,,The number of Keepalive messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.25,PCE-PCEP-MIB::pcePcepPeerNumUnknownRcvd,Counter32,read-only,,current,,The number of unknown messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.26,PCE-PCEP-MIB::pcePcepPeerNumCorruptRcvd,Counter32,read-only,,current,,The number of corrupted PCEP messages received from this peer.
.1.3.6.1.2.1.227.1.2.1.27,PCE-PCEP-MIB::pcePcepPeerNumReqSent,Counter32,read-only,,current,,The number of requests sent to this peer. A request corresponds 1:1 with an RP object in a PCReq message. This might be greater than pcePcepPeerNumPCReqSent because multiple requests can be batched into a single PCReq message.
.1.3.6.1.2.1.227.1.2.1.28,PCE-PCEP-MIB::pcePcepPeerNumSvecSent,Counter32,read-only,,current,,The number of SVEC objects sent to this peer in PCReq messages. An SVEC object represents a set of synchronized requests.
.1.3.6.1.2.1.227.1.2.1.29,PCE-PCEP-MIB::pcePcepPeerNumSvecReqSent,Counter32,read-only,,current,,The number of requests sent to this peer that appeared in one or more SVEC objects.
.1.3.6.1.2.1.227.1.2.1.30,PCE-PCEP-MIB::pcePcepPeerNumReqSentPendRep,Counter32,read-only,,current,,The number of requests that have been sent to this peer for which a response is still pending.
.1.3.6.1.2.1.227.1.2.1.31,PCE-PCEP-MIB::pcePcepPeerNumReqSentEroRcvd,Counter32,read-only,,current,,The number of requests that have been sent to this peer for which a response with an ERO was received. Such responses indicate that a path was successfully computed by the peer.
.1.3.6.1.2.1.227.1.2.1.32,PCE-PCEP-MIB::pcePcepPeerNumReqSentNoPathRcvd,Counter32,read-only,,current,,The number of requests that have been sent to this peer for which a response with a NO-PATH object was received. Such responses indicate that the peer could not find a path to satisfy the request.
.1.3.6.1.2.1.227.1.2.1.33,PCE-PCEP-MIB::pcePcepPeerNumReqSentCancelRcvd,Counter32,read-only,,current,,The number of requests that were canceled by the peer with a PCNtf message. This might be different than pcePcepPeerNumPCNtfRcvd because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
.1.3.6.1.2.1.227.1.2.1.34,PCE-PCEP-MIB::pcePcepPeerNumReqSentErrorRcvd,Counter32,read-only,,current,,The number of requests that were rejected by the peer with a PCErr message. This might be different than pcePcepPeerNumPCErrRcvd because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
.1.3.6.1.2.1.227.1.2.1.35,PCE-PCEP-MIB::pcePcepPeerNumReqSentTimeout,Counter32,read-only,,current,,The number of requests that have been sent to a peer and have been abandoned because the peer has taken too long to respond to them.
.1.3.6.1.2.1.227.1.2.1.36,PCE-PCEP-MIB::pcePcepPeerNumReqSentCancelSent,Counter32,read-only,,current,,The number of requests that were sent to the peer and explicitly canceled by the local PCEP entity sending a PCNtf.
.1.3.6.1.2.1.227.1.2.1.37,PCE-PCEP-MIB::pcePcepPeerNumReqSentClosed,Counter32,read-only,,current,,The number of requests that were sent to the peer and implicitly canceled when the session they were sent over was closed.
.1.3.6.1.2.1.227.1.2.1.38,PCE-PCEP-MIB::pcePcepPeerNumReqRcvd,Counter32,read-only,,current,,The number of requests received from this peer. A request corresponds 1:1 with an RP object in a PCReq message. This might be greater than pcePcepPeerNumPCReqRcvd because multiple requests can be batched into a single PCReq message.
.1.3.6.1.2.1.227.1.2.1.39,PCE-PCEP-MIB::pcePcepPeerNumSvecRcvd,Counter32,read-only,,current,,The number of SVEC objects received from this peer in PCReq messages. An SVEC object represents a set of synchronized requests.
.1.3.6.1.2.1.227.1.2.1.40,PCE-PCEP-MIB::pcePcepPeerNumSvecReqRcvd,Counter32,read-only,,current,,The number of requests received from this peer that appeared in one or more SVEC objects.
.1.3.6.1.2.1.227.1.2.1.41,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdPendRep,Counter32,read-only,,current,,The number of requests that have been received from this peer for which a response is still pending.
.1.3.6.1.2.1.227.1.2.1.42,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdEroSent,Counter32,read-only,,current,,The number of requests that have been received from this peer for which a response with an ERO was sent. Such responses indicate that a path was successfully computed by the local PCEP entity.
.1.3.6.1.2.1.227.1.2.1.43,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdNoPathSent,Counter32,read-only,,current,,The number of requests that have been received from this peer for which a response with a NO-PATH object was sent. Such responses indicate that the local PCEP entity could not find a path to satisfy the request.
.1.3.6.1.2.1.227.1.2.1.44,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdCancelSent,Counter32,read-only,,current,,The number of requests received from this peer that were canceled by the local PCEP entity sending a PCNtf message. This might be different than pcePcepPeerNumPCNtfSent because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
.1.3.6.1.2.1.227.1.2.1.45,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdErrorSent,Counter32,read-only,,current,,The number of requests received from this peer that were rejected by the local PCEP entity sending a PCErr message. This might be different than pcePcepPeerNumPCErrSent because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
.1.3.6.1.2.1.227.1.2.1.46,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdCancelRcvd,Counter32,read-only,,current,,The number of requests that were received from the peer and explicitly canceled by the peer sending a PCNtf.
.1.3.6.1.2.1.227.1.2.1.47,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdClosed,Counter32,read-only,,current,,The number of requests that were received from the peer and implicitly canceled when the session they were received over was closed.
.1.3.6.1.2.1.227.1.2.1.48,PCE-PCEP-MIB::pcePcepPeerNumRepRcvdUnknown,Counter32,read-only,,current,,The number of responses to unknown requests received from this peer. A response to an unknown request is a response whose RP object does not contain the request ID of any request that is currently outstanding on the session.
.1.3.6.1.2.1.227.1.2.1.49,PCE-PCEP-MIB::pcePcepPeerNumReqRcvdUnknown,Counter32,read-only,,current,,The number of unknown requests that have been received from a peer. An unknown request is a request whose RP object contains a request ID of zero.
.1.3.6.1.2.1.227.1.3,PCE-PCEP-MIB::pcePcepSessTable,,not-accessible,,current,,A table of PCEP sessions that involve the local PCEP entity. Each entry in this table represents a single session. The entries in this table are read-only. An entry appears in this table when the corresponding PCEP session transitions out of idle state. If the PCEP session transitions back into an idle state, then the corresponding entry in this table is removed.
.1.3.6.1.2.1.227.1.3.1,PCE-PCEP-MIB::pcePcepSessEntry,,not-accessible,pcePcepEntityIndex:pcePcepPeerAddrType:pcePcepPeerAddr:pcePcepSessInitiator,current,,This entry represents a single PCEP session in which the local PCEP entity participates. This entry exists only if the corresponding PCEP session has been initialized by some event, such as manual user configuration, auto-discovery of a peer, or an incoming TCP connection.
.1.3.6.1.2.1.227.1.3.1.1,PCE-PCEP-MIB::pcePcepSessInitiator,INTEGER,not-accessible,,current,local(1):remote(2),The initiator of the session; that is, whether the TCP connection was initiated by the local PCEP entity or the peer. There is a window during session initialization where two sessions can exist between a pair of PCEP speakers, each initiated by one of the speakers. One of these sessions is always discarded before it leaves OpenWait state. However, before it is discarded, two sessions to the given peer appear transiently in this MIB module. The sessions are distinguished by who initiated them, and so this field is an index for pcePcepSessTable.
.1.3.6.1.2.1.227.1.3.1.2,PCE-PCEP-MIB::pcePcepSessStateLastChange,TimeTicks,read-only,,current,,The value of sysUpTime at the time this session entered its current state as denoted by the pcePcepSessState object.
.1.3.6.1.2.1.227.1.3.1.3,PCE-PCEP-MIB::pcePcepSessState,INTEGER,read-only,,current,tcpPending(1):openWait(2):keepWait(3):sessionUp(4),The current state of the session. The set of possible states excludes the idle state since entries do not exist in this table in the idle state.
.1.3.6.1.2.1.227.1.3.1.4,PCE-PCEP-MIB::pcePcepSessConnectRetry,Counter32,read-only,,current,,The number of times that the local PCEP entity has attempted to establish a TCP connection for this session without success. The PCEP entity gives up when this reaches pcePcepEntityConnectMaxRetry.
.1.3.6.1.2.1.227.1.3.1.5,PCE-PCEP-MIB::pcePcepSessLocalID,Unsigned32,read-only,,current,,The value of the PCEP session ID used by the local PCEP entity in the Open message for this session. If pcePcepSessState is tcpPending, then this is the session ID that will be used in the Open message. Otherwise, this is the session ID that was sent in the Open message.
.1.3.6.1.2.1.227.1.3.1.6,PCE-PCEP-MIB::pcePcepSessRemoteID,Unsigned32,read-only,,current,,The value of the PCEP session ID used by the peer in its Open message for this session. If pcePcepSessState is tcpPending or openWait, then this field is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.7,PCE-PCEP-MIB::pcePcepSessKeepaliveTimer,Unsigned32,read-only,,current,,The agreed maximum interval at which the local PCEP entity transmits PCEP messages on this PCEP session. Zero means that the local PCEP entity never sends Keepalives on this session. This field is used if and only if pcePcepSessState is sessionUp. Otherwise, it is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.8,PCE-PCEP-MIB::pcePcepSessPeerKeepaliveTimer,Unsigned32,read-only,,current,,The agreed maximum interval at which the peer transmits PCEP messages on this PCEP session. Zero means that the peer never sends Keepalives on this session. This field is used if and only if pcePcepSessState is sessionUp. Otherwise, it is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.9,PCE-PCEP-MIB::pcePcepSessDeadTimer,Unsigned32,read-only,,current,,The DeadTimer interval for this PCEP session.
.1.3.6.1.2.1.227.1.3.1.10,PCE-PCEP-MIB::pcePcepSessPeerDeadTimer,Unsigned32,read-only,,current,,The peer's DeadTimer interval for this PCEP session. If pcePcepSessState is tcpPending or openWait, then this field is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.11,PCE-PCEP-MIB::pcePcepSessKAHoldTimeRem,Unsigned32,read-only,,current,,The Keepalive hold time remaining for this session. If pcePcepSessState is tcpPending or openWait, then this field is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.12,PCE-PCEP-MIB::pcePcepSessOverloaded,INTEGER,read-only,,current,true(1):false(2),If the local PCEP entity has informed the peer that it is currently overloaded, then this is set to true. Otherwise, it is set to false.
.1.3.6.1.2.1.227.1.3.1.13,PCE-PCEP-MIB::pcePcepSessOverloadTime,Unsigned32,read-only,,current,,The interval of time that is remaining until the local PCEP entity will cease to be overloaded on this session. This field is only used if pcePcepSessOverloaded is set to true. Otherwise, it is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.14,PCE-PCEP-MIB::pcePcepSessPeerOverloaded,INTEGER,read-only,,current,true(1):false(2),If the peer has informed the local PCEP entity that it is currently overloaded, then this is set to true. Otherwise, it is set to false.
.1.3.6.1.2.1.227.1.3.1.15,PCE-PCEP-MIB::pcePcepSessPeerOverloadTime,Unsigned32,read-only,,current,,The interval of time that is remaining until the peer will cease to be overloaded. If it is not known how long the peer will stay in overloaded state, this field is set to zero. This field is only used if pcePcepSessPeerOverloaded is set to true. Otherwise, it is not used and MUST be set to zero.
.1.3.6.1.2.1.227.1.3.1.16,PCE-PCEP-MIB::pcePcepSessDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime at the time that the statistics in this row were last reset.
.1.3.6.1.2.1.227.1.3.1.17,PCE-PCEP-MIB::pcePcepSessAvgRspTime,Unsigned32,read-only,,current,,The average response time for this peer on this session. If an average response time has not been calculated for this peer, then this object has the value zero.
.1.3.6.1.2.1.227.1.3.1.18,PCE-PCEP-MIB::pcePcepSessLWMRspTime,Unsigned32,read-only,,current,,The smallest (low-water mark) response time seen from this peer on this session. If no responses have been received from this peer, then this object has the value zero.
.1.3.6.1.2.1.227.1.3.1.19,PCE-PCEP-MIB::pcePcepSessHWMRspTime,Unsigned32,read-only,,current,,The greatest (high-water mark) response time seen from this peer on this session. If no responses have been received from this peer, then this object has the value zero.
.1.3.6.1.2.1.227.1.3.1.20,PCE-PCEP-MIB::pcePcepSessNumPCReqSent,Counter32,read-only,,current,,The number of PCReq messages sent on this session.
.1.3.6.1.2.1.227.1.3.1.21,PCE-PCEP-MIB::pcePcepSessNumPCReqRcvd,Counter32,read-only,,current,,The number of PCReq messages received on this session.
.1.3.6.1.2.1.227.1.3.1.22,PCE-PCEP-MIB::pcePcepSessNumPCRepSent,Counter32,read-only,,current,,The number of PCRep messages sent on this session.
.1.3.6.1.2.1.227.1.3.1.23,PCE-PCEP-MIB::pcePcepSessNumPCRepRcvd,Counter32,read-only,,current,,The number of PCRep messages received on this session.
.1.3.6.1.2.1.227.1.3.1.24,PCE-PCEP-MIB::pcePcepSessNumPCErrSent,Counter32,read-only,,current,,The number of PCErr messages sent on this session.
.1.3.6.1.2.1.227.1.3.1.25,PCE-PCEP-MIB::pcePcepSessNumPCErrRcvd,Counter32,read-only,,current,,The number of PCErr messages received on this session.
.1.3.6.1.2.1.227.1.3.1.26,PCE-PCEP-MIB::pcePcepSessNumPCNtfSent,Counter32,read-only,,current,,The number of PCNtf messages sent on this session.
.1.3.6.1.2.1.227.1.3.1.27,PCE-PCEP-MIB::pcePcepSessNumPCNtfRcvd,Counter32,read-only,,current,,The number of PCNtf messages received on this session.
.1.3.6.1.2.1.227.1.3.1.28,PCE-PCEP-MIB::pcePcepSessNumKeepaliveSent,Counter32,read-only,,current,,The number of Keepalive messages sent on this session.
.1.3.6.1.2.1.227.1.3.1.29,PCE-PCEP-MIB::pcePcepSessNumKeepaliveRcvd,Counter32,read-only,,current,,The number of Keepalive messages received on this session.
.1.3.6.1.2.1.227.1.3.1.30,PCE-PCEP-MIB::pcePcepSessNumUnknownRcvd,Counter32,read-only,,current,,The number of unknown messages received on this session.
.1.3.6.1.2.1.227.1.3.1.31,PCE-PCEP-MIB::pcePcepSessNumCorruptRcvd,Counter32,read-only,,current,,The number of corrupted PCEP messages received on this session.
.1.3.6.1.2.1.227.1.3.1.32,PCE-PCEP-MIB::pcePcepSessNumReqSent,Counter32,read-only,,current,,The number of requests sent on this session. A request corresponds 1:1 with an RP object in a PCReq message. This might be greater than pcePcepSessNumPCReqSent because multiple requests can be batched into a single PCReq message.
.1.3.6.1.2.1.227.1.3.1.33,PCE-PCEP-MIB::pcePcepSessNumSvecSent,Counter32,read-only,,current,,The number of SVEC objects sent on this session in PCReq messages. An SVEC object represents a set of synchronized requests.
.1.3.6.1.2.1.227.1.3.1.34,PCE-PCEP-MIB::pcePcepSessNumSvecReqSent,Counter32,read-only,,current,,The number of requests sent on this session that appeared in one or more SVEC objects.
.1.3.6.1.2.1.227.1.3.1.35,PCE-PCEP-MIB::pcePcepSessNumReqSentPendRep,Counter32,read-only,,current,,The number of requests that have been sent on this session for which a response is still pending.
.1.3.6.1.2.1.227.1.3.1.36,PCE-PCEP-MIB::pcePcepSessNumReqSentEroRcvd,Counter32,read-only,,current,,The number of successful responses received on this session. A response corresponds 1:1 with an RP object in a PCRep message. A successful response is a response for which an ERO was successfully computed.
.1.3.6.1.2.1.227.1.3.1.37,PCE-PCEP-MIB::pcePcepSessNumReqSentNoPathRcvd,Counter32,read-only,,current,,The number of unsuccessful responses received on this session. A response corresponds 1:1 with an RP object in a PCRep message. An unsuccessful response is a response with a NO-PATH object.
.1.3.6.1.2.1.227.1.3.1.38,PCE-PCEP-MIB::pcePcepSessNumReqSentCancelRcvd,Counter32,read-only,,current,,The number of requests sent on this session that were canceled by the peer with a PCNtf message. This might be different than pcePcepSessNumPCNtfRcvd because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
.1.3.6.1.2.1.227.1.3.1.39,PCE-PCEP-MIB::pcePcepSessNumReqSentErrorRcvd,Counter32,read-only,,current,,The number of requests sent on this session that were rejected by the peer with a PCErr message. This might be different than pcePcepSessNumPCErrRcvd because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
.1.3.6.1.2.1.227.1.3.1.40,PCE-PCEP-MIB::pcePcepSessNumReqSentTimeout,Counter32,read-only,,current,,The number of requests sent on this session that have been sent to a peer and have been abandoned because the peer has taken too long to respond to them.
.1.3.6.1.2.1.227.1.3.1.41,PCE-PCEP-MIB::pcePcepSessNumReqSentCancelSent,Counter32,read-only,,current,,The number of requests sent on this session that were sent to the peer and explicitly canceled by the local PCEP entity sending a PCNtf.
.1.3.6.1.2.1.227.1.3.1.42,PCE-PCEP-MIB::pcePcepSessNumReqRcvd,Counter32,read-only,,current,,The number of requests received on this session. A request corresponds 1:1 with an RP object in a PCReq message. This might be greater than pcePcepSessNumPCReqRcvd because multiple requests can be batched into a single PCReq message.
.1.3.6.1.2.1.227.1.3.1.43,PCE-PCEP-MIB::pcePcepSessNumSvecRcvd,Counter32,read-only,,current,,The number of SVEC objects received on this session in PCReq messages. An SVEC object represents a set of synchronized requests.
.1.3.6.1.2.1.227.1.3.1.44,PCE-PCEP-MIB::pcePcepSessNumSvecReqRcvd,Counter32,read-only,,current,,The number of requests received on this session that appeared in one or more SVEC objects.
.1.3.6.1.2.1.227.1.3.1.45,PCE-PCEP-MIB::pcePcepSessNumReqRcvdPendRep,Counter32,read-only,,current,,The number of requests that have been received on this session for which a response is still pending.
.1.3.6.1.2.1.227.1.3.1.46,PCE-PCEP-MIB::pcePcepSessNumReqRcvdEroSent,Counter32,read-only,,current,,The number of successful responses sent on this session. A response corresponds 1:1 with an RP object in a PCRep message. A successful response is a response for which an ERO was successfully computed.
.1.3.6.1.2.1.227.1.3.1.47,PCE-PCEP-MIB::pcePcepSessNumReqRcvdNoPathSent,Counter32,read-only,,current,,The number of unsuccessful responses sent on this session. A response corresponds 1:1 with an RP object in a PCRep message. An unsuccessful response is a response with a NO-PATH object.
.1.3.6.1.2.1.227.1.3.1.48,PCE-PCEP-MIB::pcePcepSessNumReqRcvdCancelSent,Counter32,read-only,,current,,The number of requests received on this session that were canceled by the local PCEP entity sending a PCNtf message. This might be different than pcePcepSessNumPCNtfSent because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
.1.3.6.1.2.1.227.1.3.1.49,PCE-PCEP-MIB::pcePcepSessNumReqRcvdErrorSent,Counter32,read-only,,current,,The number of requests received on this session that were rejected by the local PCEP entity sending a PCErr message. This might be different than pcePcepSessNumPCErrSent because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
.1.3.6.1.2.1.227.1.3.1.50,PCE-PCEP-MIB::pcePcepSessNumReqRcvdCancelRcvd,Counter32,read-only,,current,,The number of requests that were received on this session and explicitly canceled by the peer sending a PCNtf.
.1.3.6.1.2.1.227.1.3.1.51,PCE-PCEP-MIB::pcePcepSessNumRepRcvdUnknown,Counter32,read-only,,current,,The number of responses to unknown requests received on this session. A response to an unknown request is a response whose RP object does not contain the request ID of any request that is currently outstanding on the session.
.1.3.6.1.2.1.227.1.3.1.52,PCE-PCEP-MIB::pcePcepSessNumReqRcvdUnknown,Counter32,read-only,,current,,The number of unknown requests that have been received on this session. An unknown request is a request whose RP object contains a request ID of zero.
.1.3.6.1.2.1.227.1.4,PCE-PCEP-MIB::pcePcepNotificationsMaxRate,Unsigned32,read-write,,current,,This variable indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period or may queue them until an appropriate time. A value of zero means no notifications are emitted and all should be discarded (that is, not queued).
.1.3.6.1.2.1.227.2,PCE-PCEP-MIB::pcePcepConformance,,,,,,
.1.3.6.1.2.1.227.2.1,PCE-PCEP-MIB::pcePcepCompliances,,,,,,
.1.3.6.1.2.1.227.2.1.1,PCE-PCEP-MIB::pcePcepModuleReadOnlyCompliance,,,,,,The module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.227.2.2,PCE-PCEP-MIB::pcePcepGroups,,,,,,
.1.3.6.1.2.1.227.2.2.1,PCE-PCEP-MIB::pcePcepGeneralGroup,,,,,,Objects that apply to all PCEP MIB module implementations.
.1.3.6.1.2.1.227.2.2.2,PCE-PCEP-MIB::pcePcepNotificationsGroup,,,,,,The notifications for a PCEP MIB module implementation.
.1.3.6.1.2.1.228,IANAPowerStateSet-MIB::ianaPowerStateSet,,,,,,Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB module defines the PowerStateSet Textual Convention, which specifies the Power State Sets and Power State Set Values an Energy Object supports. The initial version of this MIB module was published in RFC 7460; for full legal notices see the RFC itself.
.1.3.6.1.2.1.229,ENERGY-OBJECT-MIB::energyObjectMib,,,,,,Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB is used to monitor power and energy in devices. The tables eoMeterCapabilitiesTable and eoPowerTable are a sparse extension of the eoTable from the ENERGY-OBJECT-CONTEXT-MIB. As a requirement, [RFC7461] SHOULD be implemented. Module Compliance of ENTITY-MIB v4 with respect to entity4CRCompliance MUST be supported which requires implementation of 4 MIB objects: entPhysicalIndex, entPhysicalClass, entPhysicalName and entPhysicalUUID.
.1.3.6.1.2.1.229.0,ENERGY-OBJECT-MIB::energyObjectMibNotifs,,,,,,
.1.3.6.1.2.1.229.0.1,ENERGY-OBJECT-MIB::eoPowerEnableStatusNotification,INTEGER,read-write,,current,true(1):false(2),This object controls whether the system produces notifications for eoPowerStateChange. A false value will prevent these notifications from being generated.
.1.3.6.1.2.1.229.0.2,ENERGY-OBJECT-MIB::eoPowerStateChange,,,,,,The SNMP entity generates the eoPowerStateChange when the values of eoPowerAdminState or eoPowerOperState, in the context of the Power State Set, have changed for the Energy Object represented by the entPhysicalIndex.
.1.3.6.1.2.1.229.1,ENERGY-OBJECT-MIB::energyObjectMibObjects,,,,,,
.1.3.6.1.2.1.229.1.1,ENERGY-OBJECT-MIB::eoMeterCapabilitiesTable,,not-accessible,,current,,This table is useful for helping applications determine the monitoring capabilities supported by the local management agents. It is possible for applications to know which tables are usable without going through a trial-and-error process.
.1.3.6.1.2.1.229.1.1.1,ENERGY-OBJECT-MIB::eoMeterCapabilitiesEntry,,not-accessible,entPhysicalIndex,current,,An entry describes the metering capability of an Energy Object.
.1.3.6.1.2.1.229.1.1.1.1,ENERGY-OBJECT-MIB::eoMeterCapability,BITS,read-only,,current,none(0):powermetering(1):energymetering(2):powerattributes(3),An indication of the energy-monitoring capabilities supported by this agent. This object use a BITS syntax and indicates the MIB groups supported by the probe. By reading the value of this object, it is possible to determine the MIB tables supported.
.1.3.6.1.2.1.229.1.2,ENERGY-OBJECT-MIB::eoPowerTable,,not-accessible,,current,,This table lists Energy Objects.
.1.3.6.1.2.1.229.1.2.1,ENERGY-OBJECT-MIB::eoPowerEntry,,not-accessible,entPhysicalIndex,current,,An entry describes the power usage of an Energy Object.
.1.3.6.1.2.1.229.1.2.1.1,ENERGY-OBJECT-MIB::eoPower,Integer32,read-only,,current,,This object indicates the power measured for the Energy Object. For alternating current, this value is obtained as an average over fixed number of AC cycles. This value is specified in SI units of watts with the magnitude of watts (milliwatts, kilowatts, etc.) indicated separately in eoPowerUnitMultiplier. The accuracy of the measurement is specified in eoPowerAccuracy. The direction of power flow is indicated by the sign on eoPower. If the Energy Object is consuming power, the eoPower value will be positive. If the Energy Object is producing power, the eoPower value will be negative. The eoPower MUST be less than or equal to the maximum power that can be consumed at the Power State specified by eoPowerState. The eoPowerMeasurementCaliber object specifies how the usage value reported by eoPower was obtained. The eoPower value must report 0 if the eoPowerMeasurementCaliber is 'unavailable'. For devices that cannot measure or report power, this option can be used.
.1.3.6.1.2.1.229.1.2.1.2,ENERGY-OBJECT-MIB::eoPowerNameplate,Unsigned32,read-only,,current,,This object indicates the rated maximum consumption for the fully populated Energy Object. The nameplate power requirements are the maximum power numbers given in SI watts and, in almost all cases, are well above the expected operational consumption. Nameplate power is widely used for power provisioning. This value is specified in either units of watts or voltage and current. The units are therefore SI watts or equivalent Volt-Amperes with the magnitude (milliwatts, kilowatts, etc.) indicated separately in eoPowerUnitMultiplier.
.1.3.6.1.2.1.229.1.2.1.3,ENERGY-OBJECT-MIB::eoPowerUnitMultiplier,INTEGER,read-only,,current,yocto(-24):zepto(-21):atto(-18):femto(-15):pico(-12):nano(-9):micro(-6):milli(-3):units(0):kilo(3):mega(6):giga(9):tera(12):peta(15):exa(18):zetta(21):yotta(24),The magnitude of watts for the usage value in eoPower and eoPowerNameplate.
.1.3.6.1.2.1.229.1.2.1.4,ENERGY-OBJECT-MIB::eoPowerAccuracy,Integer32,read-only,,current,,This object indicates a percentage value, in hundredths of a percent, representing the assumed accuracy of the usage reported by eoPower. For example, the value 1010 means the reported usage is accurate to +/- 10.1 percent. This value is zero if the accuracy is unknown or not applicable based upon the measurement method. ANSI and IEC define the following accuracy classes for power measurement: IEC 62053-22 60044-1 class 0.1, 0.2, 0.5, 1 3. ANSI C12.20 class 0.2, 0.5
.1.3.6.1.2.1.229.1.2.1.5,ENERGY-OBJECT-MIB::eoPowerMeasurementCaliber,INTEGER,read-only,,current,unavailable(1):unknown(2):actual(3):estimated(4):static(5),This object specifies how the usage value reported by eoPower was obtained: - unavailable(1): Indicates that the usage is not available. In such a case, the eoPower value must be 0 for devices that cannot measure or report power this option can be used. - unknown(2): Indicates that the way the usage was determined is unknown. In some cases, entities report aggregate power on behalf of another device. In such cases it is not known whether the usage reported is actual, estimated, or static. - actual(3): Indicates that the reported usage was measured by the entity through some hardware or direct physical means. The usage data reported is not estimated or static but is the measured consumption rate. - estimated(4): Indicates that the usage was not determined by physical measurement. The value is a derivation based upon the device type, state, and/or current utilization using some algorithm or heuristic. It is presumed that the entity's state and current configuration were used to compute the value. - static(5): Indicates that the usage was not determined by physical measurement, algorithm, or derivation. The usage was reported based upon external tables, specifications, and/or model information. For example, a PC Model X draws 200W, while a PC Model Y draws 210W.
.1.3.6.1.2.1.229.1.2.1.6,ENERGY-OBJECT-MIB::eoPowerCurrentType,INTEGER,read-only,,current,ac(1):dc(2):unknown(3),This object indicates whether the eoPower for the Energy Object reports alternating current 'ac', direct current 'dc', or that the current type is unknown.
.1.3.6.1.2.1.229.1.2.1.7,ENERGY-OBJECT-MIB::eoPowerMeasurementLocal,INTEGER,read-only,,current,true(1):false(2),This object indicates the source of power measurement and can be useful when modeling the power usage of attached devices. The power measurement can be performed by the entity itself or the power measurement of the entity can be reported by another trusted entity using a protocol extension. A value of true indicates the measurement is performed by the entity, whereas false indicates that the measurement was performed by another entity.
.1.3.6.1.2.1.229.1.2.1.8,ENERGY-OBJECT-MIB::eoPowerAdminState,INTEGER,read-write,,current,other(0):unknown(255):ieee1621(256):ieee1621Off(257):ieee1621Sleep(258):ieee1621On(259):dmtf(512):dmtfOn(513):dmtfSleepLight(514):dmtfSleepDeep(515):dmtfOffHard(516):dmtfOffSoft(517):dmtfHibernate(518):dmtfPowerOffSoft(519):dmtfPowerOffHard(520):dmtfMasterBusReset(521):dmtfDiagnosticInterrapt(522):dmtfOffSoftGraceful(523):dmtfOffHardGraceful(524):dmtfMasterBusResetGraceful(525):dmtfPowerCycleOffSoftGraceful(526):dmtfPowerCycleHardGraceful(527):eman(1024):emanMechOff(1025):emanSoftOff(1026):emanHibernate(1027):emanSleep(1028):emanStandby(1029):emanReady(1030):emanLowMinus(1031):emanLow(1032):emanMediumMinus(1033):emanMedium(1034):emanHighMinus(1035):emanHigh(1036),This object specifies the desired Power State and the Power State Set for the Energy Object. Note that other(0) is not a Power State Set and unknown(255) is not a Power State as such, but simply an indication that the Power State of the Energy Object is unknown. Possible values of eoPowerAdminState within the Power State Set are registered at IANA. A current list of assignments can be found at <http://www.iana.org/assignments/power-state-sets>
.1.3.6.1.2.1.229.1.2.1.9,ENERGY-OBJECT-MIB::eoPowerOperState,INTEGER,read-only,,current,other(0):unknown(255):ieee1621(256):ieee1621Off(257):ieee1621Sleep(258):ieee1621On(259):dmtf(512):dmtfOn(513):dmtfSleepLight(514):dmtfSleepDeep(515):dmtfOffHard(516):dmtfOffSoft(517):dmtfHibernate(518):dmtfPowerOffSoft(519):dmtfPowerOffHard(520):dmtfMasterBusReset(521):dmtfDiagnosticInterrapt(522):dmtfOffSoftGraceful(523):dmtfOffHardGraceful(524):dmtfMasterBusResetGraceful(525):dmtfPowerCycleOffSoftGraceful(526):dmtfPowerCycleHardGraceful(527):eman(1024):emanMechOff(1025):emanSoftOff(1026):emanHibernate(1027):emanSleep(1028):emanStandby(1029):emanReady(1030):emanLowMinus(1031):emanLow(1032):emanMediumMinus(1033):emanMedium(1034):emanHighMinus(1035):emanHigh(1036),This object specifies the current operational Power State and the Power State Set for the Energy Object. other(0) is not a Power State Set and unknown(255) is not a Power State as such, but simply an indication that the Power State of the Energy Object is unknown. Possible values of eoPowerOperState within the Power State Set are registered at IANA. A current list of assignments can be found at <http://www.iana.org/assignments/power-state-sets>
.1.3.6.1.2.1.229.1.2.1.10,ENERGY-OBJECT-MIB::eoPowerStateEnterReason,OCTET,read-write,,current,,This string object describes the reason for the eoPowerAdminState transition. Alternatively, this string may contain with the entity that configured this Energy Object to this Power State.
.1.3.6.1.2.1.229.1.3,ENERGY-OBJECT-MIB::eoPowerStateTable,,not-accessible,,current,,This table enumerates the maximum power usage, in watts, for every single supported Power State of each Energy Object. This table has cross-reference with the eoPowerTable, containing rows describing each Power State for the corresponding Energy Object. For every Energy Object in the eoPowerTable, there is a corresponding entry in this table.
.1.3.6.1.2.1.229.1.3.1,ENERGY-OBJECT-MIB::eoPowerStateEntry,,not-accessible,entPhysicalIndex:eoPowerStateIndex,current,,A eoPowerStateEntry extends a corresponding eoPowerEntry. This entry displays max usage values at every single possible Power State supported by the Energy Object. For example, given the values of a Energy Object corresponding to a maximum usage of 0 W at the state emanmechoff, 8 W at state 6 (ready), 11 W at state emanmediumMinus, and 11 W at state emanhigh: State MaxUsage Units emanmechoff 0 W emansoftoff 0 W emanhibernate 0 W emansleep 0 W emanstandby 0 W emanready 8 W emanlowMinus 8 W emanlow 11 W emanmediumMinus 11 W emanmedium 11 W emanhighMinus 11 W emnanhigh 11 W Furthermore, this table also includes the total time in each Power State, along with the number of times a particular Power State was entered.
.1.3.6.1.2.1.229.1.3.1.1,ENERGY-OBJECT-MIB::eoPowerStateIndex,INTEGER,not-accessible,,current,other(0):unknown(255):ieee1621(256):ieee1621Off(257):ieee1621Sleep(258):ieee1621On(259):dmtf(512):dmtfOn(513):dmtfSleepLight(514):dmtfSleepDeep(515):dmtfOffHard(516):dmtfOffSoft(517):dmtfHibernate(518):dmtfPowerOffSoft(519):dmtfPowerOffHard(520):dmtfMasterBusReset(521):dmtfDiagnosticInterrapt(522):dmtfOffSoftGraceful(523):dmtfOffHardGraceful(524):dmtfMasterBusResetGraceful(525):dmtfPowerCycleOffSoftGraceful(526):dmtfPowerCycleHardGraceful(527):eman(1024):emanMechOff(1025):emanSoftOff(1026):emanHibernate(1027):emanSleep(1028):emanStandby(1029):emanReady(1030):emanLowMinus(1031):emanLow(1032):emanMediumMinus(1033):emanMedium(1034):emanHighMinus(1035):emanHigh(1036),This object specifies the index of the Power State of the Energy Object within a Power State Set. The semantics of the specific Power State can be obtained from the Power State Set definition.
.1.3.6.1.2.1.229.1.3.1.2,ENERGY-OBJECT-MIB::eoPowerStateMaxPower,Integer32,read-only,,current,,This object indicates the maximum power for the Energy Object at the particular Power State. This value is specified in SI units of watts with the magnitude of the units (milliwatts, kilowatts, etc.) indicated separately in eoPowerStatePowerUnitMultiplier. If the maximum power is not known for a certain Power State, then the value is encoded as 0xFFFFFFFF. For Power States not enumerated, the value of eoPowerStateMaxPower might be interpolated by using the next highest supported Power State.
.1.3.6.1.2.1.229.1.3.1.3,ENERGY-OBJECT-MIB::eoPowerStatePowerUnitMultiplier,INTEGER,read-only,,current,yocto(-24):zepto(-21):atto(-18):femto(-15):pico(-12):nano(-9):micro(-6):milli(-3):units(0):kilo(3):mega(6):giga(9):tera(12):peta(15):exa(18):zetta(21):yotta(24),The magnitude of watts for the usage value in eoPowerStateMaxPower.
.1.3.6.1.2.1.229.1.3.1.4,ENERGY-OBJECT-MIB::eoPowerStateTotalTime,TimeTicks,read-only,,current,,This object indicates the total time in hundredths of a second that the Energy Object has been in this power state since the last reset, as specified in the sysUpTime.
.1.3.6.1.2.1.229.1.3.1.5,ENERGY-OBJECT-MIB::eoPowerStateEnterCount,Counter32,read-only,,current,,This object indicates how often the Energy Object has entered this power state, since the last reset of the device as specified in the sysUpTime.
.1.3.6.1.2.1.229.1.4,ENERGY-OBJECT-MIB::eoEnergyParametersTable,,not-accessible,,current,,This table is used to configure the parameters for energy measurement collection in the table eoEnergyTable. This table allows the configuration of different measurement settings on the same Energy Object. Implementation of this table only makes sense for Energy Objects that an eoPowerMeasurementCaliber of actual.
.1.3.6.1.2.1.229.1.4.1,ENERGY-OBJECT-MIB::eoEnergyParametersEntry,,not-accessible,entPhysicalIndex:eoEnergyParametersIndex,current,,An entry controls an energy measurement in eoEnergyTable.
.1.3.6.1.2.1.229.1.4.1.2,ENERGY-OBJECT-MIB::eoEnergyParametersIndex,Integer32,not-accessible,,current,,This object specifies the index of the Energy Parameters setting for collection of energy measurements for an Energy Object. An Energy Object can have multiple eoEnergyParametersIndex, depending on the capabilities of the Energy Object
.1.3.6.1.2.1.229.1.4.1.3,ENERGY-OBJECT-MIB::eoEnergyParametersIntervalLength,INTEGER,read-create,,current,,This object indicates the length of time in hundredths of a second over which to compute the average eoEnergyConsumed measurement in the eoEnergyTable table. The computation is based on the Energy Object's internal sampling rate of power consumed or produced by the Energy Object. The sampling rate is the rate at which the Energy Object can read the power usage and may differ based on device capabilities. The average energy consumption is then computed over the length of the interval. The default value of 15 minutes is a common interval used in industry.
.1.3.6.1.2.1.229.1.4.1.4,ENERGY-OBJECT-MIB::eoEnergyParametersIntervalNumber,Unsigned32,read-create,,current,,The number of intervals maintained in the eoEnergyTable. Each interval is characterized by a specific eoEnergyCollectionStartTime, used as an index to the table eoEnergyTable. Whenever the maximum number of entries is reached, the measurement over the new interval replaces the oldest measurement. There is one exception to this rule: when the eoEnergyMaxConsumed and/or eoEnergyMaxProduced are in (one of) the two oldest measurement(s), they are left untouched and the next oldest measurement is replaced.
.1.3.6.1.2.1.229.1.4.1.5,ENERGY-OBJECT-MIB::eoEnergyParametersIntervalMode,INTEGER,read-create,,current,period(1):sliding(2):total(3),A control object to define the mode of interval calculation for the computation of the average eoEnergyConsumed or eoEnergyProvided measurement in the eoEnergyTable table. A mode of period(1) specifies non-overlapping periodic measurements. A mode of sliding(2) specifies overlapping sliding windows where the interval between the start of one interval and the next is defined in eoEnergyParametersIntervalWindow. A mode of total(3) specifies non-periodic measurement. In this mode only one interval is used as this is a continuous measurement since the last reset. The value of eoEnergyParametersIntervalNumber should be (1) one and eoEnergyParametersIntervalLength is ignored.
.1.3.6.1.2.1.229.1.4.1.6,ENERGY-OBJECT-MIB::eoEnergyParametersIntervalWindow,INTEGER,read-create,,current,,The length of the duration window between the starting time of one sliding window and the next starting time in hundredths of seconds, used to compute the average of eoEnergyConsumed, eoEnergyProvided measurements in the eoEnergyTable table. This is valid only when the eoEnergyParametersIntervalMode is sliding(2). The eoEnergyParametersIntervalWindow value should be a multiple of eoEnergyParametersSampleRate.
.1.3.6.1.2.1.229.1.4.1.7,ENERGY-OBJECT-MIB::eoEnergyParametersSampleRate,Unsigned32,read-create,,current,,The sampling rate, in milliseconds, at which the Energy Object should poll power usage in order to compute the average eoEnergyConsumed, eoEnergyProvided measurements in the table eoEnergyTable. The Energy Object should initially set this sampling rate to a reasonable value, i.e., a compromise between intervals that will provide good accuracy by not being too long, but not so short that they affect the Energy Object performance by requesting continuous polling. If the sampling rate is unknown, the value 0 is reported. The sampling rate should be selected so that eoEnergyParametersIntervalWindow is a multiple of eoEnergyParametersSampleRate. The default value is one second.
.1.3.6.1.2.1.229.1.4.1.8,ENERGY-OBJECT-MIB::eoEnergyParametersStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.229.1.4.1.9,ENERGY-OBJECT-MIB::eoEnergyParametersStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. The eoEnergyParametersStatus is used to start or stop energy usage logging. An entry status may not be active(1) unless all objects in the entry have an appropriate value. If this object is not equal to active, all associated usage-data logged into the eoEnergyTable will be deleted. The data can be destroyed by setting up the eoEnergyParametersStatus to destroy.
.1.3.6.1.2.1.229.1.5,ENERGY-OBJECT-MIB::eoEnergyTable,,not-accessible,,current,,This table lists Energy Object energy measurements. Entries in this table are only created if the corresponding value of object eoPowerMeasurementCaliber is active(3), i.e., if the power is actually metered.
.1.3.6.1.2.1.229.1.5.1,ENERGY-OBJECT-MIB::eoEnergyEntry,,not-accessible,eoEnergyParametersIndex:eoEnergyCollectionStartTime,current,,An entry describing energy measurements.
.1.3.6.1.2.1.229.1.5.1.1,ENERGY-OBJECT-MIB::eoEnergyCollectionStartTime,TimeTicks,not-accessible,,current,,The time (in hundredths of a second) since the network management portion of the system was last re-initialized, as specified in the sysUpTime RFC 3418. This object specifies the start time of the energy measurement sample.
.1.3.6.1.2.1.229.1.5.1.2,ENERGY-OBJECT-MIB::eoEnergyConsumed,Unsigned32,read-only,,current,,This object indicates the energy consumed in units of watt-hours for the Energy Object over the defined interval. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours kWh, MWh, etc.) indicated separately in eoEnergyUnitMultiplier.
.1.3.6.1.2.1.229.1.5.1.3,ENERGY-OBJECT-MIB::eoEnergyProvided,Unsigned32,read-only,,current,,This object indicates the energy produced in units of watt-hours for the Energy Object over the defined interval. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours (kWh, MWh, etc.) indicated separately in eoEnergyUnitMultiplier.
.1.3.6.1.2.1.229.1.5.1.4,ENERGY-OBJECT-MIB::eoEnergyStored,Unsigned32,read-only,,current,,This object indicates the difference of the energy consumed and energy produced for an Energy Object in units of watt-hours for the Energy Object over the defined interval. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours (kWh, MWh, etc.) indicated separately in eoEnergyUnitMultiplier.
.1.3.6.1.2.1.229.1.5.1.5,ENERGY-OBJECT-MIB::eoEnergyUnitMultiplier,INTEGER,read-only,,current,yocto(-24):zepto(-21):atto(-18):femto(-15):pico(-12):nano(-9):micro(-6):milli(-3):units(0):kilo(3):mega(6):giga(9):tera(12):peta(15):exa(18):zetta(21):yotta(24),This object is the magnitude of watt-hours for the energy field in eoEnergyConsumed, eoEnergyProvided, eoEnergyStored, eoEnergyMaxConsumed, and eoEnergyMaxProduced.
.1.3.6.1.2.1.229.1.5.1.6,ENERGY-OBJECT-MIB::eoEnergyAccuracy,Integer32,read-only,,current,,This object indicates a percentage accuracy, in hundredths of a percent, of Energy usage reporting. eoEnergyAccuracy is applicable to all Energy measurements in the eoEnergyTable. For example, 1010 means the reported usage is accurate to +/- 10.1 percent. This value is zero if the accuracy is unknown.
.1.3.6.1.2.1.229.1.5.1.7,ENERGY-OBJECT-MIB::eoEnergyMaxConsumed,Unsigned32,read-only,,current,,This object is the maximum energy observed in eoEnergyConsumed since the monitoring started or was reinitialized. This value is specified in the common billing units of watt-hours with the magnitude of watt-hours (kWh, MWh, etc.) indicated separately in eoEnergyUnitMultiplier.
.1.3.6.1.2.1.229.1.5.1.8,ENERGY-OBJECT-MIB::eoEnergyMaxProduced,Unsigned32,read-only,,current,,This object is the maximum energy ever observed in eoEnergyEnergyProduced since the monitoring started. This value is specified in the units of watt-hours with the magnitude of watt-hours (kWh, MWh, etc.) indicated separately in eoEnergyEnergyUnitMultiplier.
.1.3.6.1.2.1.229.1.5.1.9,ENERGY-OBJECT-MIB::eoEnergyDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime RFC 3418 on the most recent occasion at which any one or more of this entity's energy counters in this table suffered a discontinuity: eoEnergyConsumed, eoEnergyProvided or eoEnergyStored. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.2.1.229.2,ENERGY-OBJECT-MIB::energyObjectMibConform,,,,,,
.1.3.6.1.2.1.229.2.1,ENERGY-OBJECT-MIB::energyObjectMibCompliances,,,,,,
.1.3.6.1.2.1.229.2.1.1,ENERGY-OBJECT-MIB::energyObjectMibFullCompliance,,,,,,When this MIB is implemented with support for read-create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB. Module Compliance of RFC 6933 with respect to entity4CRCompliance MUST be supported, which requires implementation of four MIB objects: entPhysicalIndex, entPhysicalClass, entPhysicalName and entPhysicalUUID.
.1.3.6.1.2.1.229.2.1.2,ENERGY-OBJECT-MIB::energyObjectMibReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-create (i.e., in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but cannot be configured with this MIB. Module Compliance of [RFC6933] with respect to entity4CRCompliance MUST be supported which requires implementation of 4 MIB objects: entPhysicalIndex, entPhysicalClass, entPhysicalName and entPhysicalUUID.
.1.3.6.1.2.1.229.2.2,ENERGY-OBJECT-MIB::energyObjectMibGroups,,,,,,
.1.3.6.1.2.1.229.2.2.1,ENERGY-OBJECT-MIB::energyObjectMibTableGroup,,,,,,This group contains the collection of all the objects related to the Energy Object.
.1.3.6.1.2.1.229.2.2.2,ENERGY-OBJECT-MIB::energyObjectMibStateTableGroup,,,,,,This group contains the collection of all the objects related to the Power State.
.1.3.6.1.2.1.229.2.2.3,ENERGY-OBJECT-MIB::energyObjectMibEnergyParametersTableGroup,,,,,,This group contains the collection of all the objects related to the configuration of the Energy Table.
.1.3.6.1.2.1.229.2.2.4,ENERGY-OBJECT-MIB::energyObjectMibEnergyTableGroup,,,,,,This group contains the collection of all the objects related to the Energy Table.
.1.3.6.1.2.1.229.2.2.5,ENERGY-OBJECT-MIB::energyObjectMibMeterCapabilitiesTableGroup,,,,,,This group contains the object indicating the capability of the Energy Object
.1.3.6.1.2.1.229.2.2.6,ENERGY-OBJECT-MIB::eoPowerEnableStatusNotificationGroup,,,,,,The collection of objects that are used to enable notification.
.1.3.6.1.2.1.229.2.2.7,ENERGY-OBJECT-MIB::energyObjectMibNotifGroup,,,,,,This group contains the notifications for the Monitoring and Control MIB for Power and Energy.
.1.3.6.1.2.1.230,POWER-ATTRIBUTES-MIB::powerAttributesMIB,,,,,,Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB is used to report AC power attributes in devices. The table is a sparse augmentation of the eoPowerTable table from the energyObjectMib module. Both three-phase and single-phase power configurations are supported. As a requirement for this MIB module, RFC 7461 SHOULD be implemented. Module Compliance of ENTITY-MIB v4 with respect to entity4CRCompliance MUST be supported which requires implementation of four MIB objects: entPhysicalIndex, entPhysicalClass, entPhysicalName, and entPhysicalUUID.
.1.3.6.1.2.1.230.0,POWER-ATTRIBUTES-MIB::powerAttributesMIBConform,,,,,,
.1.3.6.1.2.1.230.1,POWER-ATTRIBUTES-MIB::powerAttributesMIBObjects,,,,,,
.1.3.6.1.2.1.230.1.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesTable,,not-accessible,,current,,This table contains power attributes measurements for supported entPhysicalIndex entities. It is a sparse extension of the eoPowerTable.
.1.3.6.1.2.1.230.1.1.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesEntry,,not-accessible,entPhysicalIndex,current,,This is a sparse extension of the eoPowerTable with entries for power attributes measurements or configuration. Each measured value corresponds to an attribute in IEC 61850-7-4 for non-phase measurements within the object MMXN.
.1.3.6.1.2.1.230.1.1.1.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesConfiguration,INTEGER,read-only,,current,sngl(1):del(2):wye(3),Configuration describes the physical configurations of the power supply lines: * alternating current, single phase (SNGL) * alternating current, three-phase delta (DEL) * alternating current, three-phase Y (WYE) Three-phase configurations can be either connected in a triangular delta (DEL) or star Y (WYE) system. WYE systems have a shared neutral voltage, while DEL systems do not. Each phase is offset 120 degrees to each other.
.1.3.6.1.2.1.230.1.1.1.2,POWER-ATTRIBUTES-MIB::eoACPwrAttributesAvgVoltage,Integer32,read-only,,current,,A measured value for average of the voltage measured over an integral number of AC cycles. For a three-phase system, this is the average voltage (V1+V2+V3)/3. IEC 61850-7-4 measured value attribute 'Vol'.
.1.3.6.1.2.1.230.1.1.1.3,POWER-ATTRIBUTES-MIB::eoACPwrAttributesAvgCurrent,Unsigned32,read-only,,current,,A measured value for average of the current measured over an integral number of AC cycles. For a three-phase system, this is the average current (I1+I2+I3)/3. IEC 61850-7-4 attribute 'Amp'.
.1.3.6.1.2.1.230.1.1.1.4,POWER-ATTRIBUTES-MIB::eoACPwrAttributesFrequency,Integer32,read-only,,current,,A measured value for the basic frequency of the AC circuit. IEC 61850-7-4 attribute 'Hz'.
.1.3.6.1.2.1.230.1.1.1.5,POWER-ATTRIBUTES-MIB::eoACPwrAttributesPowerUnitMultiplier,INTEGER,read-only,,current,yocto(-24):zepto(-21):atto(-18):femto(-15):pico(-12):nano(-9):micro(-6):milli(-3):units(0):kilo(3):mega(6):giga(9):tera(12):peta(15):exa(18):zetta(21):yotta(24),The magnitude of watts for the usage value in eoACPwrAttributesTotalActivePower, eoACPwrAttributesTotalReactivePower, and eoACPwrAttributesTotalApparentPower measurements. For three-phase power systems, this will also include eoACPwrAttributesWyeActivePower, eoACPwrAttributesWyeReactivePower, and eoACPwrAttributesWyeApparentPower.
.1.3.6.1.2.1.230.1.1.1.6,POWER-ATTRIBUTES-MIB::eoACPwrAttributesPowerAccuracy,Integer32,read-only,,current,,This object indicates a percentage value, in hundredths of a percent, representing the presumed accuracy of active, reactive, and apparent power usage reporting. For example, 1010 means the reported usage is accurate to +/- 10.1 percent. This value is zero if the accuracy is unknown. ANSI and IEC define the following accuracy classes for power measurement: IEC 62053-22 & 60044-1 class 0.1, 0.2, 0.5, 1, & 3. ANSI C12.20 class 0.2 & 0.5
.1.3.6.1.2.1.230.1.1.1.7,POWER-ATTRIBUTES-MIB::eoACPwrAttributesTotalActivePower,Integer32,read-only,,current,,A measured value of the actual power delivered to or consumed by the load. IEC 61850-7-4 attribute 'TotW'.
.1.3.6.1.2.1.230.1.1.1.8,POWER-ATTRIBUTES-MIB::eoACPwrAttributesTotalReactivePower,Integer32,read-only,,current,,A measured value of the reactive portion of the apparent power. IEC 61850-7-4 attribute 'TotVAr'.
.1.3.6.1.2.1.230.1.1.1.9,POWER-ATTRIBUTES-MIB::eoACPwrAttributesTotalApparentPower,Integer32,read-only,,current,,A measured value of the voltage and current that determines the apparent power. The apparent power is the vector sum of real and reactive power. Note: watts and volt-amperes are equivalent units and may be combined. IEC 61850-7-4 attribute 'TotVA'.
.1.3.6.1.2.1.230.1.1.1.10,POWER-ATTRIBUTES-MIB::eoACPwrAttributesTotalPowerFactor,Integer32,read-only,,current,,A measured value ratio of the real power flowing to the load versus the apparent power. It is dimensionless and expressed here as a percentage value in hundredths. A power factor of 100% indicates there is no inductance load and thus no reactive power. A Power Factor can be positive or negative, where the sign should be in lead/lag (IEEE) form. IEC 61850-7-4 attribute 'TotPF'.
.1.3.6.1.2.1.230.1.1.1.11,POWER-ATTRIBUTES-MIB::eoACPwrAttributesThdCurrent,Integer32,read-only,,current,,A calculated value for the current total harmonic distortion (THD). Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdAmp'.
.1.3.6.1.2.1.230.1.1.1.12,POWER-ATTRIBUTES-MIB::eoACPwrAttributesThdVoltage,Integer32,read-only,,current,,A calculated value for the voltage total harmonic distortion (THD). The method of calculation is not specified. IEC 61850-7-4 attribute 'ThdVol'.
.1.3.6.1.2.1.230.1.2,POWER-ATTRIBUTES-MIB::eoACPwrAttributesDelPhaseTable,,not-accessible,,current,,This optional table describes three-phase power attributes measurements in a DEL configuration with phase-to-phase power attributes measurements. Entities having single phase power shall not have any entities. This is a sparse extension of the eoACPwrAttributesTable. These attributes correspond to measurements related to the IEC 61850-7.4 MMXU phase and measured harmonic or interharmonics related to the MHAI phase.
.1.3.6.1.2.1.230.1.2.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesDelPhaseEntry,,not-accessible,entPhysicalIndex:eoACPwrAttributesDelPhaseIndex,current,,An entry describes power measurements of a phase in a DEL three-phase power. Three entries are required for each supported entPhysicalIndex entry. Voltage measurements are provided relative to each other. For phase-to-phase measurements, the eoACPwrAttributesDelPhaseIndex is compared against the following phase at +120 degrees. Thus, the possible values are: eoACPwrAttributesDelPhaseIndex Next Phase Angle 0 120 120 240 240 0 
.1.3.6.1.2.1.230.1.2.1.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesDelPhaseIndex,Integer32,not-accessible,,current,,A phase angle typically corresponding to 0, 120, 240.
.1.3.6.1.2.1.230.1.2.1.2,POWER-ATTRIBUTES-MIB::eoACPwrAttributesDelPhaseToNextPhaseVoltage,Integer32,read-only,,current,,A measured value of phase to next phase voltages, where the next phase is IEC 61850-7-4 attribute 'PPV'.
.1.3.6.1.2.1.230.1.2.1.3,POWER-ATTRIBUTES-MIB::eoACPwrAttributesDelThdPhaseToNextPhaseVoltage,Integer32,read-only,,current,,A calculated value for the voltage total harmonic distortion for phase to next phase. Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdPPV'.
.1.3.6.1.2.1.230.1.3,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyePhaseTable,,not-accessible,,current,,This optional table describes three-phase power attributes measurements in a WYE configuration with phase-to-neutral power attributes measurements. Entities having single phase power shall not have any entities. This is a sparse extension of the eoACPwrAttributesTable. These attributes correspond to measurements related to the IEC 61850-7.4 MMXU phase and measured harmonic or interharmonics related to the MHAI phase.
.1.3.6.1.2.1.230.1.3.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyePhaseEntry,,not-accessible,entPhysicalIndex:eoACPwrAttributesWyePhaseIndex,current,,This table describes measurements of a phase in a WYE three-phase power system. Three entries are required for each supported entPhysicalIndex entry. Voltage measurements are relative to neutral. Each entry describes power attributes of one phase of a WYE three-phase power system.
.1.3.6.1.2.1.230.1.3.1.1,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyePhaseIndex,Integer32,not-accessible,,current,,A phase angle typically corresponding to 0, 120, 240.
.1.3.6.1.2.1.230.1.3.1.2,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyePhaseToNeutralVoltage,Integer32,read-only,,current,,A measured value of phase to neutral voltage. IEC 61850-7-4 attribute 'PNV'.
.1.3.6.1.2.1.230.1.3.1.3,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyeCurrent,Integer32,read-only,,current,,A measured value of phase currents. IEC 61850-7-4 attribute 'A'.
.1.3.6.1.2.1.230.1.3.1.4,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyeActivePower,Integer32,read-only,,current,,A measured value of the actual power delivered to or consumed by the load with the magnitude indicated separately in eoPowerUnitMultiplier. IEC 61850-7-4 attribute 'W'.
.1.3.6.1.2.1.230.1.3.1.5,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyeReactivePower,Integer32,read-only,,current,,A measured value of the reactive portion of the apparent power with the magnitude of indicated separately in eoPowerUnitMultiplier. IEC 61850-7-4 attribute 'VAr'.
.1.3.6.1.2.1.230.1.3.1.6,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyeApparentPower,Integer32,read-only,,current,,A measured value of the voltage and current determines the apparent power with the indicated separately in eoPowerUnitMultiplier. Active plus reactive power equals the total apparent power. Note: Watts and volt-amperes are equivalent units and may be combined. IEC 61850-7-4 attribute 'VA'.
.1.3.6.1.2.1.230.1.3.1.7,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyePowerFactor,Integer32,read-only,,current,,A measured value ratio of the real power flowing to the load versus the apparent power for this phase. IEC 61850-7-4 attribute 'PF'. Power Factor can be positive or negative where the sign should be in lead/lag (IEEE) form.
.1.3.6.1.2.1.230.1.3.1.8,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyeThdCurrent,Integer32,read-only,,current,,A calculated value for the voltage total harmonic distortion (THD) for phase to phase. Method of calculation is not specified. IEC 61850-7-4 attribute 'ThdA'.
.1.3.6.1.2.1.230.1.3.1.9,POWER-ATTRIBUTES-MIB::eoACPwrAttributesWyeThdPhaseToNeutralVoltage,Integer32,read-only,,current,,A calculated value of the voltage total harmonic distortion (THD) for phase to neutral. IEC 61850-7-4 attribute 'ThdPhV'.
.1.3.6.1.2.1.230.2,POWER-ATTRIBUTES-MIB::powerAttributesMIBCompliances,,,,,,
.1.3.6.1.2.1.230.2.1,POWER-ATTRIBUTES-MIB::powerAttributesMIBFullCompliance,,,,,,When this MIB is implemented with support for read- create, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB. Module Compliance of RFC 6933 with respect to entity4CRCompliance MUST be supported which requires implementation of four MIB objects: entPhysicalIndex, entPhysicalClass, entPhysicalName, and entPhysicalUUID.
.1.3.6.1.2.1.230.3,POWER-ATTRIBUTES-MIB::powerAttributesMIBGroups,,,,,,
.1.3.6.1.2.1.230.3.1,POWER-ATTRIBUTES-MIB::powerACPwrAttributesMIBTableGroup,,,,,,This group contains the collection of all the power attributes objects related to the Energy Object.
.1.3.6.1.2.1.230.3.2,POWER-ATTRIBUTES-MIB::powerACPwrAttributesOptionalMIBTableGroup,,,,,,This group contains the collection of all the power attributes objects related to the Energy Object.
.1.3.6.1.2.1.230.3.3,POWER-ATTRIBUTES-MIB::powerACPwrAttributesDelPhaseMIBTableGroup,,,,,,This group contains the collection of all power attributes of a phase in a DEL three-phase power system.
.1.3.6.1.2.1.230.3.4,POWER-ATTRIBUTES-MIB::powerACPwrAttributesWyePhaseMIBTableGroup,,,,,,This group contains the collection of all power attributes of a phase in a WYE three-phase power system.
.1.3.6.1.2.1.231,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIB,,,,,,Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB is used for describing the identity and the context information of Energy Objects.
.1.3.6.1.2.1.231.0,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBNotifs,,,,,,
.1.3.6.1.2.1.231.1,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBObjects,,,,,,
.1.3.6.1.2.1.231.1.1,ENERGY-OBJECT-CONTEXT-MIB::eoTable,,not-accessible,,current,,This table lists Energy Objects.
.1.3.6.1.2.1.231.1.1.1,ENERGY-OBJECT-CONTEXT-MIB::eoEntry,,not-accessible,entPhysicalIndex,current,,An entry describes the attributes of an Energy Object. Whenever a new Energy Object is added or an existing Energy Object is deleted, a row in the eoTable is added or deleted.
.1.3.6.1.2.1.231.1.1.1.1,ENERGY-OBJECT-CONTEXT-MIB::eoEthPortIndex,Integer32,read-only,,current,,This variable uniquely identifies the power Ethernet port to which a Power over Ethernet device is connected. If the Power over Ethernet MIB in RFC 3621 is supported by the SNMP agent managing the Energy Object, then the Energy Object eoethPortIndex MUST contain the corresponding value of pethPsePortIndex. If such a power Ethernet port cannot be specified or is not known, then the object is zero.
.1.3.6.1.2.1.231.1.1.1.2,ENERGY-OBJECT-CONTEXT-MIB::eoEthPortGrpIndex,Integer32,read-only,,current,,This variable uniquely identifies the group containing the port to which a power over Ethernet device PSE is connected (RFC 3621). If the Power over Ethernet MIB (RFC 3621) is supported by the SNMP agent managing the Energy Object, then the Energy Object eoEthPortGrpIndex MUST contain the corresponding value of eoethPortGrpIndex. If such a power Ethernet port cannot be specified or is not known, then the object is zero.
.1.3.6.1.2.1.231.1.1.1.3,ENERGY-OBJECT-CONTEXT-MIB::eoLldpPortNumber,Integer32,read-only,,current,,This variable uniquely identifies the port component (contained in the local chassis with the LLDP agent) as defined by the lldpLocPortNum in the LLDP-MIB and LLDP-MED-MIB. If the LLDP-MIB is supported by the SNMP agent managing the Energy Object, then the Energy Object eoLldpPortNumber MUST contain the corresponding value of lldpLocPortNum from the LLDP-MIB. If such a port number cannot be specified or is not known, then the object is zero.
.1.3.6.1.2.1.231.1.1.1.4,ENERGY-OBJECT-CONTEXT-MIB::eoMgmtMacAddress,OCTET,read-only,,current,,This object specifies a Media Access Control (MAC) address of the Energy Object.
.1.3.6.1.2.1.231.1.1.1.5,ENERGY-OBJECT-CONTEXT-MIB::eoMgmtAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the eoMgmtAddress type, i.e., an IPv4 or IPv6 address. This object MUST be populated when eoMgmtAddress is populated.
.1.3.6.1.2.1.231.1.1.1.6,ENERGY-OBJECT-CONTEXT-MIB::eoMgmtAddress,OCTET,read-only,,current,,This object specifies the management address as an IPv4 address or IPv6 address of Energy Object. The IP address type, i.e. IPv4 or IPv6, is determined by the eoMgmtAddressType value. This object can be used as an alternate key to help link the Energy Object with other keyed information that may be stored within the EnMS(s).
.1.3.6.1.2.1.231.1.1.1.7,ENERGY-OBJECT-CONTEXT-MIB::eoMgmtDNSName,OCTET,read-only,,current,,This object specifies a DNS name of the eoMgmtAddress. This object can be used as an alternate key to help link the Energy Object with other keyed information that may be stored within the EnMS(s). A DNS Name must always be a fully qualified name. This MIB uses the same encoding as the DNS protocol.
.1.3.6.1.2.1.231.1.1.1.8,ENERGY-OBJECT-CONTEXT-MIB::eoDomainName,OCTET,read-write,,current,,This object specifies the name of an Energy Management Domain for the Energy Object. By default, this object should be an empty string. The value of eoDomainName must remain constant at least from one re-initialization of the entity local management system to the next re- initialization.
.1.3.6.1.2.1.231.1.1.1.9,ENERGY-OBJECT-CONTEXT-MIB::eoRoleDescription,OCTET,read-write,,current,,This object specifies an administratively assigned name to indicate the purpose an Energy Object serves in the network. For example, we can have a phone deployed to a lobby with eoRoleDescription as 'Lobby phone'. This object specifies that the value is the zero-length string value if no role description is configured. The value of eoRoleDescription must remain constant at least from one re-initialization of the entity local management system to the next re-initialization.
.1.3.6.1.2.1.231.1.1.1.10,ENERGY-OBJECT-CONTEXT-MIB::eoKeywords,OCTET,read-write,,current,,This object specifies a list of keywords that can be used to group Energy Objects for reporting or searching. The value is the zero-length string if no keywords have been configured. If multiple keywords are present, then this string will contain all the keywords separated by the ',' character. For example, if an Energy Object were to be tagged with the keyword values 'hospitality' and 'guest', then the keyword list will be 'hospitality,guest'. If write access is implemented and a value is written into the instance, the agent must retain the supplied value in the eoKeywords instance associated with the same physical entity for as long as that entity remains instantiated. This includes instantiations across all re-initializations/reboots of the local management agent.
.1.3.6.1.2.1.231.1.1.1.11,ENERGY-OBJECT-CONTEXT-MIB::eoImportance,Integer32,read-write,,current,,This object specifies a ranking of how important the Energy Object is (on a scale of 1 to 100) compared with other Energy Objects in the same Energy Management Domain. The ranking should provide a business or operational context for the Energy Object as compared to other similar Energy Objects. This ranking could be used as input for policy-based network management. Although network managers must establish their own ranking, the following is a broad recommendation: 90 to 100 Emergency response 80 to 89 Executive or business critical 70 to 79 General or average 60 to 69 Staff or support 40 to 59 Public or guest 1 to 39 Decorative or hospitality The value of eoImportance must remain constant at least from one re-initialization of the Energy Object local management system to the next re-initialization.
.1.3.6.1.2.1.231.1.1.1.12,ENERGY-OBJECT-CONTEXT-MIB::eoPowerCategory,INTEGER,read-only,,current,consumer(0):producer(1):meter(2):distributor(3):store(4),This object describes the Energy Object category, which indicates the expected behavior or physical property of the Energy Object, based on its design. An Energy Object can be a consumer(0), producer(1), meter(2), distributor(3), or store(4). In some cases, a meter is required to measure the power consumption. In such a case, this meter Energy Object category is meter(2). If a device is distributing electric Energy, the category of the Energy Object is distributor (3). If a device is storing electric Energy, the category of the device can be store (4).
.1.3.6.1.2.1.231.1.1.1.13,ENERGY-OBJECT-CONTEXT-MIB::eoAlternateKey,OCTET,read-write,,current,,The eoAlternateKey object specifies an alternate key string that can be used to identify the Energy Object. Since Energy Management Systems (EnMS) and Network Management Systems (NMSs) may need to correlate objects across management systems, this alternate key is provided to provide such a link. This optional value is intended as a foreign key or alternate identifier for a manufacturer or EnMS/NMS to use to correlate the unique Energy Object Id in other systems or namespaces. If an alternate key is not available or is not applicable, then the value is the zero-length string. The value of eoAlternateKey must remain constant at least from one re-initialization of the entity local management system to the next re-initialization.
.1.3.6.1.2.1.231.1.1.1.14,ENERGY-OBJECT-CONTEXT-MIB::eoPowerInterfaceType,INTEGER,read-only,,current,inlet(0):outlet(1):both(2),This object describes the Power Interface for an Energy Object. A Power Interface is an interface at which an Energy Object is connected to a power transmission medium, at which it can in turn receive power, provide power, or both. A Power Interface type can be an inlet(0), an outlet(1), or both(2), respectively.
.1.3.6.1.2.1.231.1.2,ENERGY-OBJECT-CONTEXT-MIB::eoRelationTable,,not-accessible,,current,,This table describes the relationships between Energy Objects.
.1.3.6.1.2.1.231.1.2.1,ENERGY-OBJECT-CONTEXT-MIB::eoRelationEntry,,not-accessible,entPhysicalIndex:eoRelationIndex,current,,An entry in this table specifies the Energy relationship between Energy objects. Energy relations between two Energy objects are defined in RFC 7326.
.1.3.6.1.2.1.231.1.2.1.1,ENERGY-OBJECT-CONTEXT-MIB::eoRelationIndex,Integer32,not-accessible,,current,,This object is an arbitrary index to identify the Energy Object related to another Energy Object.
.1.3.6.1.2.1.231.1.2.1.2,ENERGY-OBJECT-CONTEXT-MIB::eoRelationID,OCTET,read-create,,current,,This object specifies the Universally Unique Identifier (UUID) of the peer (other) Energy Object. The UUID must comply with the specifications of UUID in UUID-TC-MIB. If the UUID of the Energy Object is unknown or nonexistent, the eoRelationID will be set to a zero-length string instead. It is preferable that the value of entPhysicalUUID from ENTITY-MIB is used for values for this object.
.1.3.6.1.2.1.231.1.2.1.3,ENERGY-OBJECT-CONTEXT-MIB::eoRelationship,INTEGER,read-create,,current,poweredBy(1):powering(2):meteredBy(3):metering(4):aggregatedBy(5):aggregating(6),This object describes the relations between Energy Objects. For each Energy Object, the relations between the other Energy Objects are specified using the bitmap.
.1.3.6.1.2.1.231.1.2.1.4,ENERGY-OBJECT-CONTEXT-MIB::eoRelationStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status controls and reflects the creation and activation status of a row in this table to specify energy relationship between Energy Objects. An entry status may not be active(1) unless all objects in the entry have the appropriate values. No attempt to modify a row columnar object instance value in the eoRelationTable should be issued while the value of eoRelationStatus is active(1). The data can be destroyed by setting up the eoRelationStatus to destroy(2).
.1.3.6.1.2.1.231.1.2.1.5,ENERGY-OBJECT-CONTEXT-MIB::eoRelationStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This variable indicates the storage type for this row.
.1.3.6.1.2.1.231.2,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBConform,,,,,,
.1.3.6.1.2.1.231.2.1,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBCompliances,,,,,,
.1.3.6.1.2.1.231.2.1.1,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBFullCompliance,,,,,,When this MIB is implemented with support for read-write, then such an implementation can claim full compliance. Such devices can then be both monitored and configured with this MIB. Module Compliance of ENTITY-MIB with respect to entity4CRCompliance MUST be supported.
.1.3.6.1.2.1.231.2.1.2,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBReadOnlyCompliance,,,,,,When this MIB is implemented without support for read-write (i.e., in read-only mode), then such an implementation can claim read-only compliance. Such a device can then be monitored but cannot be configured with this MIB. Module Compliance of ENTITY-MIB with respect to entity4CRCompliance MUST be supported.
.1.3.6.1.2.1.231.2.2,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBGroups,,,,,,
.1.3.6.1.2.1.231.2.2.1,ENERGY-OBJECT-CONTEXT-MIB::energyObjectContextMIBTableGroup,,,,,,This group contains the collection of all the objects related to the EnergyObject.
.1.3.6.1.2.1.231.2.2.2,ENERGY-OBJECT-CONTEXT-MIB::energyObjectOptionalMIBTableGroup,,,,,,This group contains the collection of all the objects related to the Energy Object.
.1.3.6.1.2.1.231.2.2.3,ENERGY-OBJECT-CONTEXT-MIB::energyObjectRelationTableGroup,,,,,,This group contains the collection of all objects specifying the relationship between Energy Objects.
.1.3.6.1.2.1.232,IANA-ENERGY-RELATION-MIB::ianaEnergyRelationMIB,,,,,,Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This MIB module defines a TEXTUAL-CONVENTION that describes the relationships between Energy Objects. The initial version of this MIB module was published in RFC 7461; for full legal notices see the RFC itself.
.1.3.6.1.2.1.233,BATTERY-MIB::batteryMIB,,,,,,This MIB module defines a set of objects for monitoring batteries of networked devices and of their components. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 7577; see the RFC itself for full legal notices.
.1.3.6.1.2.1.233.0,BATTERY-MIB::batteryNotifications,,,,,,
.1.3.6.1.2.1.233.0.1,BATTERY-MIB::batteryChargingStateNotification,,,,,,This notification can be generated when a charging state of the battery (indicated by the value of object batteryChargingOperState) is triggered by an event other than a write action to object batteryChargingAdminState. Such an event may, for example, be triggered by a local battery controller.
.1.3.6.1.2.1.233.0.2,BATTERY-MIB::batteryLowNotification,,,,,,This notification can be generated when the current charge (batteryActualCharge) or the current voltage (batteryActualVoltage) of the battery falls below a threshold defined by object batteryAlarmLowCharge or object batteryAlarmLowVoltage, respectively. Note that, typically, this notification is generated in a state where the battery is still sufficiently charged to keep the device(s) that it powers operational for some time. If the charging state of the battery has become critical, i.e., the device(s) powered by the battery must go to a 'sleep' or 'off' state, then the batteryCriticalNotification should be used instead. If the low charge or voltage has been detected for a single cell or a set of cells of the battery and not for the entire battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. The notification should not be sent again for the same battery or cell before either (a) the current voltage or the current charge, respectively, has become higher than the corresponding threshold through charging or (b) an indication of a maintenance action has been detected, such as a battery disconnection event or a reinitialization of the battery monitoring system. This notification should not be sent when the battery is in a charging mode, i.e., the value of object batteryChargingOperState is charging(2).
.1.3.6.1.2.1.233.0.3,BATTERY-MIB::batteryCriticalNotification,,,,,,This notification can be generated when the current charge of the battery falls so low that it cannot provide a sufficient power supply function for regular operation of the powered device(s). The battery needs to be charged before it can be used for regular power supply again. The battery may still provide sufficient power for a 'sleep' mode of a powered device(s) or for a transition into an 'off' mode. If the critical state is caused by a single cell or a set of cells of the battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. The notification should not be sent again for the same battery before either the battery charge has increased through charging to a non-critical value or an indication of a maintenance action has been detected, such as a battery disconnection event or a reinitialization of the battery monitoring system. This notification should not be sent when the battery is in a charging mode, i.e., the value of object batteryChargingOperState is charging(2).
.1.3.6.1.2.1.233.0.4,BATTERY-MIB::batteryTemperatureNotification,,,,,,This notification can be generated when the measured temperature (batteryTemperature) rises above the threshold defined by object batteryAlarmHighTemperature or falls below the threshold defined by object batteryAlarmLowTemperature. If the low or high temperature has been detected for a single cell or a set of cells of the battery and not for the entire battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. It may occur that the temperature alternates between values slightly below and slightly above a threshold. For limiting the notification rate in such a case, this notification should not be sent again for the same battery or cell, respectively, within a time interval of 10 minutes. An exception to the rate limitations occurs immediately after the reinitialization of the battery monitoring system. At this point in time, if the battery temperature is above the threshold defined by object batteryAlarmHighTemperature or below the threshold defined by object batteryAlarmLowTemperature, respectively, then this notification should be sent, independent of the time at which previous notifications for the same battery or cell, respectively, had been sent.
.1.3.6.1.2.1.233.0.5,BATTERY-MIB::batteryAgingNotification,,,,,,This notification can be generated when the actual capacity (batteryActualCapacity) falls below a threshold defined by object batteryAlarmLowCapacity or when the charging cycle count of the battery (batteryChargingCycleCount) exceeds the threshold defined by object batteryAlarmHighCycleCount. If the aging has been detected for a single cell or a set of cells of the battery and not for the entire battery, then object batteryCellIdentifier should be set to a value that identifies the cell or set of cells. Otherwise, the value of object batteryCellIdentifier should be set to the empty string when this notification is generated. This notification should not be sent again for the same battery or cell, respectively, before an indication of a maintenance action has been detected, such as a battery disconnection event or a reinitialization of the battery monitoring system.
.1.3.6.1.2.1.233.0.6,BATTERY-MIB::batteryConnectedNotification,,,,,,This notification can be generated when it has been detected that a battery has been connected. The battery can be identified by the value of object batteryIdentifier as well as by the value of index entPhysicalIndex that is contained in the OID of object batteryIdentifier.
.1.3.6.1.2.1.233.0.7,BATTERY-MIB::batteryDisconnectedNotification,,,,,,This notification can be generated when it has been detected that one or more batteries have been disconnected.
.1.3.6.1.2.1.233.1,BATTERY-MIB::batteryObjects,,,,,,
.1.3.6.1.2.1.233.1.1,BATTERY-MIB::batteryTable,,not-accessible,,current,,This table provides information on batteries. It contains one conceptual row per battery in a managed entity. Batteries are indexed by the entPhysicalIndex of the entPhysicalTable defined in the ENTITY-MIB (RFC 6933). For implementations of the BATTERY-MIB, an implementation of the ENTITY-MIB complying with the entity4CRCompliance MODULE-COMPLIANCE statement of the ENTITY-MIB is required. If batteries are replaced, and the replacing battery uses the same physical connector as the replaced battery, then the replacing battery SHOULD be indexed with the same value of object entPhysicalIndex as the replaced battery.
.1.3.6.1.2.1.233.1.1.1,BATTERY-MIB::batteryEntry,,not-accessible,entPhysicalIndex,current,,An entry providing information on a battery.
.1.3.6.1.2.1.233.1.1.1.1,BATTERY-MIB::batteryIdentifier,OCTET,read-only,,current,,This object contains an identifier for the battery. Many manufacturers deliver not only simple batteries but battery packages including additional hardware and firmware. Typically, these modules include an identifier that can be retrieved by a device in which a battery has been installed. The identifier is useful when batteries are removed and reinstalled in the same or other devices. Then, the device or the network management system can trace batteries and achieve continuity of battery monitoring. If the battery is identified by more than one value, for example, by a model number and a serial number, then the value of this object is a concatenation of these values, separated by the colon symbol ':'. The values should be ordered so that a more significant value comes before a less significant one. In the example above, the (more significant) model number would be first, and the serial number would follow: '<model number>:<serial number>'. If the battery identifier cannot be represented using the ISO/IEC IS 10646-1 character set, then a hexadecimal encoding of a binary representation of the entire battery identifier must be used. The value of this object must be an empty string if there is no battery identifier or if the battery identifier is unknown.
.1.3.6.1.2.1.233.1.1.1.2,BATTERY-MIB::batteryFirmwareVersion,OCTET,read-only,,current,,This object indicates the version number of the firmware that is included in a battery module. Many manufacturers deliver not pure batteries but battery packages including additional hardware and firmware. Since the behavior of the battery may change with the firmware, it may be useful to retrieve the firmware version number. The value of this object must be an empty string if there is no firmware or if the version number of the firmware is unknown.
.1.3.6.1.2.1.233.1.1.1.3,BATTERY-MIB::batteryType,INTEGER,read-only,,current,unknown(1):other(2):primary(3):rechargeable(4):capacitor(5),This object indicates the type of battery. It distinguishes between primary (not rechargeable) batteries, rechargeable (secondary) batteries, and capacitors. Capacitors are not really batteries but are often used in the same way as a battery. The value other(2) can be used if the battery type is known but is none of the ones above. Value unknown(1) is to be used if the type of battery cannot be determined.
.1.3.6.1.2.1.233.1.1.1.4,BATTERY-MIB::batteryTechnology,Unsigned32,read-only,,current,,This object indicates the technology used by the battery. Numbers identifying battery technologies are registered at IANA. A current list of assignments can be found at <http://www.iana.org/assignments/battery-technologies>. Value unknown(1) MUST be used if the technology of the battery cannot be determined. Value other(2) can be used if the battery technology is known but is not one of the types already registered at IANA.
.1.3.6.1.2.1.233.1.1.1.5,BATTERY-MIB::batteryDesignVoltage,Unsigned32,read-only,,current,,This object provides the design (or nominal) voltage of the battery in units of millivolt (mV). Note that the design voltage is a constant value and typically different from the actual voltage of the battery. A value of 0 indicates that the design voltage is unknown.
.1.3.6.1.2.1.233.1.1.1.6,BATTERY-MIB::batteryNumberOfCells,Unsigned32,read-only,,current,,This object indicates the number of cells contained in the battery. A value of 0 indicates that the number of cells is unknown.
.1.3.6.1.2.1.233.1.1.1.7,BATTERY-MIB::batteryDesignCapacity,Unsigned32,read-only,,current,,This object provides the design (or nominal) capacity of the battery in units of milliampere hours (mAh). Note that the design capacity is a constant value and typically different from the actual capacity of the battery. Usually, this is a value provided by the manufacturer of the battery. A value of 0 indicates that the design capacity is unknown.
.1.3.6.1.2.1.233.1.1.1.8,BATTERY-MIB::batteryMaxChargingCurrent,Unsigned32,read-only,,current,,This object provides the maximum current to be used for charging the battery in units of milliampere (mA). Note that the maximum charging current may not lead to optimal charge of the battery and that some batteries can only be charged with the maximum current for a limited amount of time. A value of 0 indicates that the maximum charging current is unknown.
.1.3.6.1.2.1.233.1.1.1.9,BATTERY-MIB::batteryTrickleChargingCurrent,Unsigned32,read-only,,current,,This object provides the recommended average current to be used for trickle charging the battery in units of mA. Typically, this is a value recommended by the manufacturer of the battery or by the manufacturer of the charging circuit. A value of 0 indicates that the recommended trickle charging current is unknown.
.1.3.6.1.2.1.233.1.1.1.10,BATTERY-MIB::batteryActualCapacity,Unsigned32,read-only,,current,,This object provides the actual capacity of the battery in units of mAh. Typically, the actual capacity of a battery decreases with time and with usage of the battery. It is usually lower than the design capacity. Note that the actual capacity needs to be measured and is typically an estimate based on observed discharging and charging cycles of the battery. A value of 'ffffffff'H indicates that the actual capacity cannot be determined.
.1.3.6.1.2.1.233.1.1.1.11,BATTERY-MIB::batteryChargingCycleCount,Unsigned32,read-only,,current,,This object indicates the number of completed charging cycles that the battery underwent. In line with the Smart Battery Data Specification Revision 1.1, a charging cycle is defined as the process of discharging the battery by a total amount equal to the battery design capacity as given by object batteryDesignCapacity. A charging cycle may include several steps of charging and discharging the battery until the discharging amount given by batteryDesignCapacity has been reached. As soon as a charging cycle has been completed, the next one starts immediately, independent of the battery's current charge at the end of the cycle. For batteries of type primary(3), the value of this object is always 0. A value of 'ffffffff'H indicates that the number of charging cycles cannot be determined.
.1.3.6.1.2.1.233.1.1.1.12,BATTERY-MIB::batteryLastChargingCycleTime,OCTET,read-only,,current,,The date and time of the last charging cycle. The value '0000000000000000'H is returned if the battery has not been charged yet or if the last charging time cannot be determined. For batteries of type primary(1), the value of this object is always '0000000000000000'H.
.1.3.6.1.2.1.233.1.1.1.13,BATTERY-MIB::batteryChargingOperState,INTEGER,read-only,,current,unknown(1):charging(2):maintainingCharge(3):noCharging(4):discharging(5),This object indicates the current charging state of the battery. Value unknown(1) indicates that the charging state of the battery cannot be determined. Value charging(2) indicates that the battery is being charged in a way such that the charge of the battery increases. Value maintainingCharge(3) indicates that the battery is being charged with a low-average current that compensates self-discharging. This includes trickle charging, float charging, and other methods for maintaining the current charge of a battery. In typical implementations of charging controllers, state maintainingCharge(3) is only applied if the battery is fully charged or almost fully charged. Value noCharging(4) indicates that the battery is not being charged or discharged by electric current between the battery and electric circuits external to the battery. Note that the battery may still be subject to self-discharging. Value discharging(5) indicates that the battery is either used as the power source for electric circuits external to the battery or discharged intentionally by the charging controller, e.g., for the purpose of battery maintenance. In any case, the charge of the battery decreases.
.1.3.6.1.2.1.233.1.1.1.14,BATTERY-MIB::batteryChargingAdminState,INTEGER,read-write,,current,notSet(1):charge(2):doNotCharge(3):discharge(4),The value of this object indicates the desired charging state of the battery. The real state is indicated by object batteryChargingOperState. See the definition of object batteryChargingOperState for a description of the values. When this object is initialized by an implementation of the BATTERY-MIB module, its value is set to notSet(1). In this case, the charging controller is free to choose which operational state is suitable. When the batteryChargingAdminState object is set, then the BATTERY-MIB implementation must try to set the battery to the indicated state. The result will be indicated by object batteryChargingOperState. Setting object batteryChargingAdminState to value notSet(1) is a request to the charging controller to operate autonomously and choose the operational state that is suitable. Setting object batteryChargingAdminState to value charge(2) is a request to enter the operational state charging(2) until the battery is fully charged. When the battery is fully charged, or if the battery was already fully charged or almost fully charged at the time of the request, the operational state will change to maintainingCharge(3) if the charging controller and the battery support the functionality of maintaining the charge, or it will change to noCharging(4) otherwise. Setting object batteryChargingAdminState to value doNotCharge(3) is a request for entering operational state noCharging(4). Setting object batteryChargingAdminState to value discharge(4) is a request for entering operational state discharging(5). Discharging can be accomplished by ordinary use, applying a dedicated load, or any other means. An example for applying this state is battery maintenance. If the battery is empty or almost empty, the operational state will change to noCharging(4). The charging controller will decide which charge condition will be considered empty dependent on the battery technology used. This is done to avoid damage on the battery due to deep discharge. Due to operational conditions and limitations of the implementation of the BATTERY-MIB module, changing the battery status according to a set value of object batteryChargingAdminState may not be possible. Setting the value of object batteryChargingAdminState may result in not changing the state of the battery to this value or even in setting the charging state to another value than the requested one. For example, the charging controller might at any time decide to enter state discharging(5), if there is an operational need to use the battery for supplying power.
.1.3.6.1.2.1.233.1.1.1.15,BATTERY-MIB::batteryActualCharge,Unsigned32,read-only,,current,,This object provides the actual charge of the battery in units of mAh. Note that the actual charge needs to be measured and is typically an estimate based on observed discharging and charging cycles of the battery. A value of 'ffffffff'H indicates that the actual charge cannot be determined.
.1.3.6.1.2.1.233.1.1.1.16,BATTERY-MIB::batteryActualVoltage,Unsigned32,read-only,,current,,This object provides the actual voltage of the battery in units of mV. A value of 'ffffffff'H indicates that the actual voltage cannot be determined.
.1.3.6.1.2.1.233.1.1.1.17,BATTERY-MIB::batteryActualCurrent,Integer32,read-only,,current,,This object provides the actual charging or discharging current of the battery in units of mA. The charging current is represented by positive values, and the discharging current is represented by negative values. A value of '7fffffff'H indicates that the actual current cannot be determined.
.1.3.6.1.2.1.233.1.1.1.18,BATTERY-MIB::batteryTemperature,Integer32,read-only,,current,,The ambient temperature at or within close proximity of the battery. A value of '7fffffff'H indicates that the temperature cannot be determined.
.1.3.6.1.2.1.233.1.1.1.19,BATTERY-MIB::batteryAlarmLowCharge,Unsigned32,read-write,,current,,This object provides the lower-threshold value for object batteryActualCharge. If the value of object batteryActualCharge falls below this threshold, a low-battery alarm will be raised. The alarm procedure may include generating a batteryLowNotification. This object should be set to a value such that when the batteryLowNotification is generated, the battery is still sufficiently charged to keep the device(s) that it powers operational for a time long enough to take actions before the powered device(s) enters a 'sleep' or 'off' state. A value of 0 indicates that no alarm will be raised for any value of object batteryActualVoltage.
.1.3.6.1.2.1.233.1.1.1.20,BATTERY-MIB::batteryAlarmLowVoltage,Unsigned32,read-write,,current,,This object provides the lower-threshold value for object batteryActualVoltage. If the value of object batteryActualVoltage falls below this threshold, a low-battery alarm will be raised. The alarm procedure may include generating a batteryLowNotification. This object should be set to a value such that when the batteryLowNotification is generated, the battery is still sufficiently charged to keep the device(s) that it powers operational for a time long enough to take actions before the powered device(s) enters a 'sleep' or 'off' state. A value of 0 indicates that no alarm will be raised for any value of object batteryActualVoltage.
.1.3.6.1.2.1.233.1.1.1.21,BATTERY-MIB::batteryAlarmLowCapacity,Unsigned32,read-write,,current,,This object provides the lower-threshold value for object batteryActualCapacity. If the value of object batteryActualCapacity falls below this threshold, a battery aging alarm will be raised. The alarm procedure may include generating a batteryAgingNotification. A value of 0 indicates that no alarm will be raised for any value of object batteryActualCapacity.
.1.3.6.1.2.1.233.1.1.1.22,BATTERY-MIB::batteryAlarmHighCycleCount,Unsigned32,read-write,,current,,This object provides the upper-threshold value for object batteryChargingCycleCount. If the value of object batteryChargingCycleCount rises above this threshold, a battery aging alarm will be raised. The alarm procedure may include generating a batteryAgingNotification. A value of 0 indicates that no alarm will be raised for any value of object batteryChargingCycleCount.
.1.3.6.1.2.1.233.1.1.1.23,BATTERY-MIB::batteryAlarmHighTemperature,Integer32,read-write,,current,,This object provides the upper-threshold value for object batteryTemperature. If the value of object batteryTemperature rises above this threshold, a battery high temperature alarm will be raised. The alarm procedure may include generating a batteryTemperatureNotification. A value of '7fffffff'H indicates that no alarm will be raised for any value of object batteryTemperature.
.1.3.6.1.2.1.233.1.1.1.24,BATTERY-MIB::batteryAlarmLowTemperature,Integer32,read-write,,current,,This object provides the lower-threshold value for object batteryTemperature. If the value of object batteryTemperature falls below this threshold, a battery low temperature alarm will be raised. The alarm procedure may include generating a batteryTemperatureNotification. A value of '7fffffff'H indicates that no alarm will be raised for any value of object batteryTemperature.
.1.3.6.1.2.1.233.1.1.1.25,BATTERY-MIB::batteryCellIdentifier,OCTET,read-only,,current,,The value of this object identifies one or more cells of a battery. The format of the cell identifier may vary between different implementations. It should uniquely identify one or more cells of the indexed battery. This object can be used for batteries, such as lithium polymer batteries for which battery controllers monitor cells individually. This object is used by notifications of types batteryLowNotification, batteryTemperatureNotification, batteryCriticalNotification, and batteryAgingNotification. These notifications can use the value of this object to indicate the event that triggered the generation of the notification in more detail by specifying a single cell or a set of cells within the battery that is specifically addressed by the notification. An example use case for this object is a single cell in a battery that exceeds the temperature indicated by object batteryAlarmHighTemperature. In such a case, a batteryTemperatureNotification can be generated that not only indicates the battery for which the temperature limit has been exceeded but also the particular cell. The initial value of this object is the empty string. The value of this object is set each time a batteryLowNotification, batteryTemperatureNotification, batteryCriticalNotification, or batteryAgingNotification is generated. When a notification is generated that does not indicate a specific cell or set of cells, the value of this object is set to the empty string.
.1.3.6.1.2.1.233.2,BATTERY-MIB::batteryConformance,,,,,,
.1.3.6.1.2.1.233.2.1,BATTERY-MIB::batteryCompliances,,,,,,
.1.3.6.1.2.1.233.2.1.1,BATTERY-MIB::batteryCompliance,,,,,,The compliance statement for implementations of the BATTERY-MIB module. A compliant implementation MUST implement the objects defined in the mandatory groups batteryDescriptionGroup and batteryStatusGroup. Note that this compliance statement requires compliance with the entity4CRCompliance MODULE-COMPLIANCE statement of the ENTITY-MIB (RFC 6933).
.1.3.6.1.2.1.233.2.2,BATTERY-MIB::batteryGroups,,,,,,
.1.3.6.1.2.1.233.2.2.1,BATTERY-MIB::batteryDescriptionGroup,,,,,,A compliant implementation MUST implement the objects contained in this group.
.1.3.6.1.2.1.233.2.2.2,BATTERY-MIB::batteryStatusGroup,,,,,,A compliant implementation MUST implement the objects contained in this group.
.1.3.6.1.2.1.233.2.2.3,BATTERY-MIB::batteryAdminGroup,,,,,,A compliant implementation does not have to implement the object contained in this group.
.1.3.6.1.2.1.233.2.2.4,BATTERY-MIB::batteryAlarmThresholdsGroup,,,,,,A compliant implementation does not have to implement the objects contained in this group.
.1.3.6.1.2.1.233.2.2.5,BATTERY-MIB::batteryNotificationsGroup,,,,,,A compliant implementation does not have to implement the notifications contained in this group.
.1.3.6.1.2.1.233.2.2.6,BATTERY-MIB::batteryPerCellNotificationsGroup,,,,,,A compliant implementation does not have to implement the object contained in this group.
.1.3.6.1.2.1.234,NATV2-MIB::natv2MIB,,,,,,This MIB module defines the generic managed objects for NAT. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this MIB module is part of RFC 7659; see the RFC itself for full legal notices.
.1.3.6.1.2.1.234.0,NATV2-MIB::natv2MIBNotifications,,,,,,
.1.3.6.1.2.1.234.0.1,NATV2-MIB::natv2NotificationPoolUsageLow,,,,,,This notification is triggered when an address pool's usage becomes less than or equal to the value of the natv2PoolThresholdUsageLow object for that pool, unless the notification has been disabled by setting the value of the threshold to -1. It is reported subject to the rate limitation specified by natv2PortMapNotificationInterval. Address pool usage is calculated as the percentage of the total number of ports allocated to the address pool that are already in use, for the most-mapped protocol at the time the notification is triggered. The two returned objects are members of natv2PoolTable indexed by the NAT instance and pool indices for which the event is being reported. They give the number of port map entries using external addresses configured on the pool for the most-mapped protocol and identify that protocol at the time the notification was triggered.
.1.3.6.1.2.1.234.0.2,NATV2-MIB::natv2NotificationPoolUsageHigh,,,,,,This notification is triggered when an address pool's usage becomes greater than or equal to the value of the natv2PoolThresholdUsageHigh object for that pool, unless the notification has been disabled by setting the value of the threshold to -1. It is reported subject to the rate limitation specified by natv2PortMapNotificationInterval. Address pool usage is calculated as the percentage of the total number of ports allocated to the address pool that are already in use, for the most-mapped protocol at the time the notification is triggered. The two returned objects are members of natv2PoolTable indexed by the NAT instance and pool indices for which the event is being reported. They give the number of port map entries using external addresses configured on the pool for the most-mapped protocol and identify that protocol at the time the notification was triggered.
.1.3.6.1.2.1.234.0.3,NATV2-MIB::natv2NotificationInstanceAddressMapEntriesHigh,,,,,,This notification is triggered when the value of natv2InstanceAddressMapEntries equals or exceeds the value of the natv2InstanceThresholdAddressMapEntriesHigh object for the NAT instance, unless disabled by setting that threshold to -1. Reporting is subject to the rate limitation given by natv2InstanceNotificationInterval. natv2InstanceAddressMapEntries and natv2InstanceAddressMapCreations are members of table natv2InstanceTable indexed by the identifier of the NAT instance for which the event is being reported. The values reported are those observed at the moment the notification was triggered.
.1.3.6.1.2.1.234.0.4,NATV2-MIB::natv2NotificationInstancePortMapEntriesHigh,,,,,,This notification is triggered when the value of natv2InstancePortMapEntries becomes greater than or equal to the value of natv2InstanceThresholdPortMapEntriesHigh, unless disabled by setting that threshold to -1. Reporting is subject to the rate limitation given by natv2InstanceNotificationInterval. natv2InstancePortMapEntries and natv2InstancePortMapCreations are members of table natv2InstanceTable indexed by the identifier of the NAT instance for which the event is being reported. The values reported are those observed at the moment the notification was triggered.
.1.3.6.1.2.1.234.0.5,NATV2-MIB::natv2NotificationSubscriberPortMappingEntriesHigh,,,,,,This notification is triggered when the value of natv2SubscriberPortMapEntries for an individual subscriber becomes greater than or equal to the value of the natv2SubscriberThresholdPortMapEntriesHigh object for that subscriber, unless disabled by setting that threshold to -1. Reporting is subject to the rate limitation given by natv2SubscriberNotificationInterval. natv2SubscriberPortMapEntries and natv2SubscriberPortMapCreations are members of table natv2SubscriberTable indexed by the subscriber for which the event is being reported. The values reported are those observed at the moment the notification was triggered.
.1.3.6.1.2.1.234.1,NATV2-MIB::natv2MIBDeviceObjects,,,,,,
.1.3.6.1.2.1.234.1.1,NATV2-MIB::natv2SubscriberTable,,not-accessible,,current,,Table of subscribers. As well as the subscriber index, it provides per-subscriber state and counter objects, a last discontinuity time object for the counters, and a writable threshold value and limit on port consumption.
.1.3.6.1.2.1.234.1.1.1,NATV2-MIB::natv2SubscriberEntry,,not-accessible,natv2SubscriberIndex,current,,Each entry describes a single subscriber.
.1.3.6.1.2.1.234.1.1.1.1,NATV2-MIB::natv2SubscriberIndex,Unsigned32,not-accessible,,current,,A unique value, greater than zero, for each subscriber in the managed system. The value for each subscriber MUST remain constant at least from one update of the entity's natv2SubscriberDiscontinuityTime object until the next update of that object. If a subscriber is deleted, its assigned index value MUST NOT be assigned to another subscriber at least until reinitialization of the entity's management system.
.1.3.6.1.2.1.234.1.1.1.2,NATV2-MIB::natv2SubscriberInternalRealm,OCTET,read-only,,current,,The address realm to which this subscriber belongs. A realm defines an address space. All NATs support at least two realms. The default realm for subscribers is 'internal'. Administrators can set other values for individual subscribers when they are configured. The administrator MAY configure a new value of natv2SubscriberRealm at any time subsequent to initial configuration of the subscriber. If this happens, it MUST be treated as a point of discontinuity requiring an update of natv2SubscriberDiscontinuityTime. When the subscriber sends a packet to the NAT through a DS-Lite (RFC 6333) tunnel, this is the realm of the outer packet header source address. Other tunneled access is out of scope.
.1.3.6.1.2.1.234.1.1.1.3,NATV2-MIB::natv2SubscriberInternalPrefixType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Subscriber's internal prefix type. Any value other than ipv4(1) or ipv6(2) would be unexpected. In the case of DS-Lite access, this is the prefix type (IPv6(2)) used in the outer packet header.
.1.3.6.1.2.1.234.1.1.1.4,NATV2-MIB::natv2SubscriberInternalPrefix,OCTET,read-only,,current,,Prefix assigned to a subscriber's Customer Premises Equipment (CPE). The type of this prefix is given by natv2SubscriberInternalPrefixType. Source addresses of packets outgoing from the subscriber will be contained within this prefix. In the case of DS-Lite access, the source address taken from the prefix will be that of the outer header.
.1.3.6.1.2.1.234.1.1.1.5,NATV2-MIB::natv2SubscriberInternalPrefixLength,Unsigned32,read-only,,current,,Length of the prefix assigned to a subscriber's CPE, in bits. If a single address is assigned, this will be 32 for IPv4 and 128 for IPv6.
.1.3.6.1.2.1.234.1.1.1.6,NATV2-MIB::natv2SubscriberAddressMapEntries,Unsigned32,read-only,,current,,The current number of address map entries for the subscriber, including static mappings. An address map entry maps from a given internal address and realm to an external address in a particular external realm. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Address map entries are also tracked per instance and per address pool within the instance.
.1.3.6.1.2.1.234.1.1.1.7,NATV2-MIB::natv2SubscriberPortMapEntries,Unsigned32,read-only,,current,,The current number of port map entries in the port map table for the subscriber, including static mappings. A port map entry maps from a given external realm, address, and port for a given protocol to an internal realm, address, and port. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Port map entries are also tracked per instance and per protocol and address pool within the instance.
.1.3.6.1.2.1.234.1.1.1.8,NATV2-MIB::natv2SubscriberTranslations,Counter64,read-only,,current,,The cumulative number of translated packets received from or sent to this subscriber. This value MUST be monotone increasing in the periods between updates of the entity's natv2SubscriberDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2SubscriberDiscontinuityTime.
.1.3.6.1.2.1.234.1.1.1.9,NATV2-MIB::natv2SubscriberAddressMapCreations,Counter64,read-only,,current,,The cumulative number of address map entries created for this subscriber, including static mappings. Address map entries are also tracked per instance and per protocol and address pool within the instance. This value MUST be monotone increasing in the periods between updates of the entity's natv2SubscriberDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2SubscriberDiscontinuityTime.
.1.3.6.1.2.1.234.1.1.1.10,NATV2-MIB::natv2SubscriberPortMapCreations,Counter64,read-only,,current,,The cumulative number of port map entries created for this subscriber, including static mappings. Port map entries are also tracked per instance and per protocol and address pool within the instance. This value MUST be monotone increasing in the periods between updates of the entity's natv2SubscriberDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2SubscriberDiscontinuityTime.
.1.3.6.1.2.1.234.1.1.1.11,NATV2-MIB::natv2SubscriberAddressMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets originated by this subscriber that were dropped because the packet would have triggered the creation of a new address map entry, but no address could be allocated in the selected external realm because all addresses from the selected address pool (or the whole realm, if no address pool has been configured for that realm) have already been fully allocated. This value MUST be monotone increasing in the periods between updates of the entity's natv2SubscriberDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2SubscriberDiscontinuityTime.
.1.3.6.1.2.1.234.1.1.1.12,NATV2-MIB::natv2SubscriberPortMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets dropped because the packet would have triggered the creation of a new port mapping, but no port could be allocated for the protocol concerned. The usual case for this will be for a NAT instance that supports address pooling and the 'Paired' pooling behavior recommended by RFC 4787, where the internal endpoint has used up all of the ports allocated to it for the address it was mapped to in the selected address pool in the external realm concerned and cannot be given more ports because - policy or implementation prevents it from having a second address in the same pool, and - policy or unavailability prevents it from acquiring more ports at its originally assigned address. If the NAT instance supports address pooling but its pooling behavior is 'Arbitrary' (meaning that the NAT instance can allocate a new port mapping for the given internal endpoint on any address in the selected address pool and is not bound to what it has already mapped for that endpoint), then this counter is incremented when all ports for the protocol concerned over the whole of the selected address pool are already in use. As a third case, if no address pools have been configured for the external realm concerned, then this counter is incremented because all ports for the protocol involved over the whole set of addresses available for that external realm are already in use. Finally, this counter is incremented if the packet would have triggered the creation of a new port mapping, but the current value of natv2SubscriberPortMapEntries equals or exceeds the value of natv2SubscriberLimitPortMapEntries for this subscriber (unless that limit is disabled). This value MUST be monotone increasing in the periods between updates of the entity's natv2SubscriberDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2SubscriberDiscontinuityTime.
.1.3.6.1.2.1.234.1.1.1.14,NATV2-MIB::natv2SubscriberDiscontinuityTime,TimeTicks,read-only,,current,,Snapshot of the value of the sysUpTime object at the beginning of the latest period of continuity of the statistical counters associated with this subscriber.
.1.3.6.1.2.1.234.1.1.1.15,NATV2-MIB::natv2SubscriberLimitPortMapEntries,Unsigned32,read-write,,current,,Limit on total number of port mappings active for this subscriber (natv2SubscriberPortMapEntries). Once this limit is reached, packets that might have triggered new port mappings are dropped. The number of such packets dropped is counted in natv2InstancePortMapFailureDrops. Limit is disabled if set to zero.
.1.3.6.1.2.1.234.1.1.1.16,NATV2-MIB::natv2SubscriberThresholdPortMapEntriesHigh,Integer32,read-write,,current,,Notification threshold for total number of port mappings active for this subscriber. Whenever natv2SubscriberPortMapEntries is updated, if it equals or exceeds natv2SubscriberThresholdPortMapEntriesHigh, the notification natv2NotificationSubscriberPortMappingEntriesHigh is triggered, unless the notification is disabled by setting the threshold to -1. Reporting is subject to the minimum inter-notification interval given by natv2SubscriberNotificationInterval. If multiple notifications are triggered during one interval, the agent MUST report only the one containing the highest value of natv2SubscriberPortMapEntries and discard the others.
.1.3.6.1.2.1.234.1.1.1.17,NATV2-MIB::natv2SubscriberNotificationInterval,Unsigned32,read-write,,current,,Minimum number of seconds between successive reporting of notifications for this subscriber. Controls the reporting of natv2NotificationSubscriberPortMappingEntriesHigh.
.1.3.6.1.2.1.234.2,NATV2-MIB::natv2MIBInstanceObjects,,,,,,
.1.3.6.1.2.1.234.2.1,NATV2-MIB::natv2InstanceTable,,not-accessible,,current,,Table of NAT instances. As well as state and counter objects, it provides the instance index, instance name, and the last discontinuity time object that is applicable to the counters. It also contains writable thresholds for reporting of notifications and limits on usage of resources at the level of the NAT instance. It is assumed that NAT instances can be created and deleted dynamically, but this MIB module does not provide the means to do so. For restrictions on assignment and maintenance of the NAT index instance, see the description of natv2InstanceIndex in the table below. For the requirements on maintenance of the values of the counters in this table, see the description of natv2InstanceDiscontinuityTime in this table. Each NAT instance has its own resources and behavior. The resources include memory as reflected in space for map entries, processing power as reflected in the rate of map creation and deletion, and mappable addresses in each realm that can play the role of an external realm for at least some mappings for that instance. The NAT instance table includes limits and notification thresholds that relate to memory usage for mapping at the level of the whole instance. The limit on number of subscribers with active mappings is a limit to some extent on processor usage. The mappable 'external' addresses may or may not be organized into address pools. For a definition of address pools, see the description of natv2PoolTable. If the instance does support address pools, it also has a pooling behavior. Mapping, filtering, and pooling behavior are defined in the descriptions of the natv2InstancePortMappingBehavior, natv2InstanceFilteringBehavior, and natv2InstancePoolingBehavior objects in this table. The instance also has a fragmentation behavior, defined in the description of the natv2InstanceFragmentBehavior object.
.1.3.6.1.2.1.234.2.1.1,NATV2-MIB::natv2InstanceEntry,,not-accessible,natv2InstanceIndex,current,,Objects related to a single NAT instance.
.1.3.6.1.2.1.234.2.1.1.1,NATV2-MIB::natv2InstanceIndex,Unsigned32,not-accessible,,current,,NAT instance index. It is up to the implementation to determine which values correspond to in-service NAT instances. This object is used as an index for all tables defined below.
.1.3.6.1.2.1.234.2.1.1.2,NATV2-MIB::natv2InstanceAlias,OCTET,read-only,,current,,This object is an 'alias' name for the NAT instance as specified by a network manager and provides a non-volatile 'handle' for the instance. An example of the value that a network manager might store in this object for a NAT instance is the name/identifier of the interface that brings in internal traffic for this NAT instance or the name of the Virtual Routing and Forwarding (VRF) for internal traffic.
.1.3.6.1.2.1.234.2.1.1.3,NATV2-MIB::natv2InstancePortMappingBehavior,INTEGER,read-only,,current,endpointIndependent(0):addressDependent(1):addressAndPortDependent(2),Port mapping behavior is the policy governing the selection of external address and port in a given realm for a given five-tuple of source address and port, destination address and port, and protocol. endpointIndependent(0), the behavior REQUIRED by RFC 4787, REQ-1, maps the source address and port to the same external address and port for all destination address and port combinations reached through the same external realm and using the given protocol. addressDependent(1) maps to the same external address and port for all destination ports at the same destination address reached through the same external realm and using the given protocol. addressAndPortDependent(2) maps to a separate external address and port combination for each different destination address and port combination reached through the same external realm.
.1.3.6.1.2.1.234.2.1.1.4,NATV2-MIB::natv2InstanceFilteringBehavior,INTEGER,read-only,,current,endpointIndependent(0):addressDependent(1):addressAndPortDependent(2),Filtering behavior is the policy governing acceptance or the dropping of packets incoming from remote sources via a given external realm and destined to a specific three-tuple of external address, port, and protocol at the NAT instance that has been assigned in a port mapping. endpointIndependent(0) accepts for translation packets from all combinations of remote address and port destined to the mapped external address and port via the given external realm and using the given protocol. addressDependent(1) accepts for translation packets from all remote ports from the same remote source address destined to the mapped external address and port via the given external realm and using the given protocol. addressAndPortDependent(2) accepts for translation only those packets with the same remote source address, port, and protocol incoming from the same external realm as identified when the applicable port map entry was created. RFC 4787, REQ-8 recommends either endpointIndependent(0) or addressDependent(1) filtering behavior depending on whether application friendliness or security takes priority.
.1.3.6.1.2.1.234.2.1.1.5,NATV2-MIB::natv2InstancePoolingBehavior,INTEGER,read-only,,current,arbitrary(0):paired(1),Pooling behavior is the policy used to select the address for a new port mapping within a given address pool to which the internal address has already been mapped. arbitrary(0) pooling behavior means that the NAT instance may create the new port mapping using any address in the pool that has a free port for the protocol concerned. paired(1) pooling behavior, the behavior RECOMMENDED by RFC 4787, REQ-2, means that once a given internal address has been mapped to a particular address in a particular pool, further mappings of the same internal address to that pool will reuse the previously assigned pool member address.
.1.3.6.1.2.1.234.2.1.1.6,NATV2-MIB::natv2InstanceFragmentBehavior,INTEGER,read-only,,current,fragmentNone(0):fragmentInOrder(1):fragmentOutOfOrder(2),Fragment behavior is the NAT instance's capability to receive and translate fragments incoming from remote sources. fragmentNone(0) implies no capability to translate incoming fragments, so all received fragments are dropped. Each dropped fragment is counted in natv2InstanceFragmentDrops. fragmentInOrder(1) implies the ability to translate fragments only if they are received in order, so that in particular the header is in the first packet. If a fragment is received out of order, it is dropped and counted in natv2InstanceFragmentDrops. fragmentOutOfOrder(2), the capability REQUIRED by RFC 4787, REQ-14, implies the capability to translate fragments even when they arrive out of order, subject to a protective limit natv2InstanceLimitPendingFragments on total number of fragments awaiting the first fragment of the chain. If the implementation supports this capability, natv2InstanceFragmentDrops is incremented only when a new fragment arrives but is dropped because the limit on pending fragments has already been reached.
.1.3.6.1.2.1.234.2.1.1.7,NATV2-MIB::natv2InstanceAddressMapEntries,Unsigned32,read-only,,current,,The current number of address map entries in total over the whole NAT instance, including static mappings. An address map entry maps from a given internal address and realm to an external address in a particular external realm. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Address map entries are also tracked per subscriber and per address pool within the instance.
.1.3.6.1.2.1.234.2.1.1.8,NATV2-MIB::natv2InstancePortMapEntries,Unsigned32,read-only,,current,,The current number of entries in the port map table in total over the whole NAT instance, including static mappings. A port map entry maps from a given external realm, address, and port for a given protocol to an internal realm, address, and port. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Port map entries are also tracked per subscriber and per protocol and address pool within the instance.
.1.3.6.1.2.1.234.2.1.1.9,NATV2-MIB::natv2InstanceTranslations,Counter64,read-only,,current,,The cumulative number of translated packets passing through this NAT instance. This value MUST be monotone increasing in the periods between updates of natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.10,NATV2-MIB::natv2InstanceAddressMapCreations,Counter64,read-only,,current,,The cumulative number of address map entries created by the NAT instance, including static mappings. Address map creations are also tracked per address pool within the instance and per subscriber. This value MUST be monotone increasing in the periods between updates of natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.11,NATV2-MIB::natv2InstancePortMapCreations,Counter64,read-only,,current,,The cumulative number of port map entries created by the NAT instance, including static mappings. Port map creations are also tracked per protocol and address pool within the instance and per subscriber. This value MUST be monotone increasing in the periods between updates of natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.12,NATV2-MIB::natv2InstanceAddressMapEntryLimitDrops,Counter64,read-only,,current,,The cumulative number of packets dropped rather than translated because the packet would have triggered the creation of a new address map entry, but the limit on number of address map entries for the NAT instance given by natv2InstanceLimitAddressMapEntries has already been reached. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.13,NATV2-MIB::natv2InstancePortMapEntryLimitDrops,Counter64,read-only,,current,,The cumulative number of packets dropped rather than translated because the packet would have triggered the creation of a new port map entry, but the limit on number of port map entries for the NAT instance given by natv2InstanceLimitPortMapEntries has already been reached. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.14,NATV2-MIB::natv2InstanceSubscriberActiveLimitDrops,Counter64,read-only,,current,,The cumulative number of packets dropped rather than translated because the packet would have triggered the creation of a new mapping for a subscriber with no other active mappings, but the limit on number of active subscribers for the NAT instance given by natv2InstanceLimitSubscriberActives has already been reached. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.15,NATV2-MIB::natv2InstanceAddressMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets dropped because the packet would have triggered the creation of a new address map entry, but no address could be allocated in the selected external realm because all addresses from the selected address pool (or the whole realm, if no address pool has been configured for that realm) have already been fully allocated. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.16,NATV2-MIB::natv2InstancePortMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets dropped because the packet would have triggered the creation of a new port map entry, but no port could be allocated for the protocol concerned. The usual case for this will be for a NAT instance that supports address pooling and the 'Paired' pooling behavior recommended by RFC 4787, where the internal endpoint has used up all of the ports allocated to it for the address it was mapped to in the selected address pool in the external realm concerned and cannot be given more ports because - policy or implementation prevents it from having a second address in the same pool, and - policy or unavailability prevents it from acquiring more ports at its originally assigned address. If the NAT instance supports address pooling but its pooling behavior is 'Arbitrary' (meaning that the NAT instance can allocate a new port mapping for the given internal endpoint on any address in the selected address pool and is not bound to what it has already mapped for that endpoint), then this counter is incremented when all ports for the protocol concerned over the whole of the selected address pool are already in use. Finally, if no address pools have been configured for the external realm concerned, then this counter is incremented because all ports for the protocol involved over the whole set of addresses available for that external realm are already in use. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.17,NATV2-MIB::natv2InstanceFragmentDrops,Counter64,read-only,,current,,The cumulative number of fragments received by the NAT instance but dropped rather than translated. When the NAT instance supports the 'Receive Fragment Out of Order' capability as required by RFC 4787, this occurs because the fragment was received out of order and would be added to the queue of fragments awaiting the initial fragment of the chain, but the queue has already reached the limit set by natv2InstanceLimitsPendingFragments. Counting in other cases is specified in the description of natv2InstanceFragmentBehavior. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.18,NATV2-MIB::natv2InstanceOtherResourceFailureDrops,Counter64,read-only,,current,,The cumulative number of packets dropped because of unavailability of a resource other than an address or port that would have been required to process it. The most likely case is where the upper-layer protocol in the packet is not supported by the NAT instance. This value MUST be monotone increasing in the periods between updates of the entity's natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.1.1.19,NATV2-MIB::natv2InstanceDiscontinuityTime,TimeTicks,read-only,,current,,Snapshot of the value of the sysUpTime object at the beginning of the latest period of continuity of the statistical counters associated with this NAT instance.
.1.3.6.1.2.1.234.2.1.1.20,NATV2-MIB::natv2InstanceThresholdAddressMapEntriesHigh,Integer32,read-write,,current,,Notification threshold for total number of address map entries held by this NAT instance. Whenever natv2InstanceAddressMapEntries is updated, if it equals or exceeds natv2InstanceThresholdAddressMapEntriesHigh, then natv2NotificationInstanceAddressMapEntriesHigh may be triggered, unless the notification is disabled by setting the threshold to -1. Reporting is subject to the minimum inter-notification interval given by natv2InstanceNotificationInterval. If multiple notifications are triggered during one interval, the agent MUST report only the one containing the highest value of natv2InstanceAddressMapEntries and discard the others.
.1.3.6.1.2.1.234.2.1.1.21,NATV2-MIB::natv2InstanceThresholdPortMapEntriesHigh,Integer32,read-write,,current,,Notification threshold for total number of port map entries held by this NAT instance. Whenever natv2InstancePortMapEntries is updated, if it equals or exceeds natv2InstanceThresholdPortMapEntriesHigh, then natv2NotificationInstancePortMapEntriesHigh may be triggered, unless the notification is disabled by setting the threshold to -1. Reporting is subject to the minimum inter-notification interval given by natv2InstanceNotificationInterval. If multiple notifications are triggered during one interval, the agent MUST report only the one containing the highest value of natv2InstancePortMapEntries and discard the others.
.1.3.6.1.2.1.234.2.1.1.22,NATV2-MIB::natv2InstanceNotificationInterval,Unsigned32,read-write,,current,,Minimum number of seconds between successive notifications for this NAT instance. Controls the reporting of natv2NotificationInstanceAddressMapEntriesHigh and natv2NotificationInstancePortMapEntriesHigh.
.1.3.6.1.2.1.234.2.1.1.23,NATV2-MIB::natv2InstanceLimitAddressMapEntries,Unsigned32,read-write,,current,,Limit on total number of address map entries supported by the NAT instance. When natv2InstanceAddressMapEntries has reached this limit, subsequent packets that would normally trigger creation of a new address map entry will be dropped and counted in natv2InstanceAddressMapEntryLimitDrops. Warning of an approach to this limit can be achieved by setting natv2InstanceThresholdAddressMapEntriesHigh to a non-zero value, for example, 80% of the limit. The limit is disabled by setting its value to zero. For further information, please see the descriptions of natv2NotificationInstanceAddressMapEntriesHigh and natv2InstanceAddressMapEntries.
.1.3.6.1.2.1.234.2.1.1.24,NATV2-MIB::natv2InstanceLimitPortMapEntries,Unsigned32,read-write,,current,,Limit on total number of port map entries supported by the NAT instance. When natv2InstancePortMapEntries has reached this limit, subsequent packets that would normally trigger creation of a new port map entry will be dropped and counted in natv2InstancePortMapEntryLimitDrops. Warning of an approach to this limit can be achieved by setting natv2InstanceThresholdPortMapEntriesHigh to a non-zero value, for example, 80% of the limit. The limit is disabled by setting its value to zero. For further information, please see the descriptions of natv2NotificationInstancePortMapEntriesHigh and natv2InstancePortMapEntries.
.1.3.6.1.2.1.234.2.1.1.25,NATV2-MIB::natv2InstanceLimitPendingFragments,Unsigned32,read-write,,current,,Limit on number of out-of-order fragments received by the NAT instance from remote sources and held until head of chain appears. While the number of held fragments is at this limit, subsequent packets that contain fragments not relating to those already held will be dropped and counted in natv2InstancePendingFragmentLimitDrops. The limit is disabled by setting the value to zero. Applicable only when the NAT instance supports 'Receive Fragments Out of Order' behavior; leave at default otherwise. See the description of natv2InstanceFragmentBehavior.
.1.3.6.1.2.1.234.2.1.1.26,NATV2-MIB::natv2InstanceLimitSubscriberActives,Unsigned32,read-write,,current,,Limit on number of total number of active subscribers supported by the NAT instance. An active subscriber is defined as any subscriber with at least one map entry, including static mappings. While the number of active subscribers is at this limit, subsequent packets that would otherwise trigger first mappings for newly active subscribers will be dropped and counted in natv2InstanceSubscriberActiveLimitDrops. The limit is disabled by setting the value to zero.
.1.3.6.1.2.1.234.2.2,NATV2-MIB::natv2ProtocolTable,,not-accessible,,current,,Table of protocols with per-protocol counters. Conceptual rows of the table are indexed by the combination of the NAT instance number and the IANA-assigned upper-layer protocol number as given by the ProtocolNumber Textual Convention (TC) and contained in the packet IP header. It is up to the agent implementation to determine and operate upon only those upper-layer protocol numbers supported by the NAT instance.
.1.3.6.1.2.1.234.2.2.1,NATV2-MIB::natv2ProtocolEntry,,not-accessible,natv2ProtocolInstanceIndex:natv2ProtocolNumber,current,,Per-protocol counters.
.1.3.6.1.2.1.234.2.2.1.1,NATV2-MIB::natv2ProtocolInstanceIndex,Unsigned32,not-accessible,,current,,NAT instance index. It is up to the implementation to determine and operate upon only those values that correspond to in-service NAT instances.
.1.3.6.1.2.1.234.2.2.1.2,NATV2-MIB::natv2ProtocolNumber,Unsigned32,not-accessible,,current,,Counters in this conceptual row apply to packets indicating the upper-layer protocol identified by the value of this object. It is up to the implementation to determine and operate upon only those values that correspond to protocols supported by the NAT instance.
.1.3.6.1.2.1.234.2.2.1.3,NATV2-MIB::natv2ProtocolPortMapEntries,Unsigned32,read-only,,current,,The current number of entries in the port map table in total over the whole NAT instance for a given protocol, including static mappings. A port map entry maps from a given external realm, address, and port for a given protocol to an internal realm, address, and port. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Port map entries are also tracked per subscriber, per instance, and per address pool within the instance.
.1.3.6.1.2.1.234.2.2.1.4,NATV2-MIB::natv2ProtocolTranslations,Counter64,read-only,,current,,The cumulative number of packets translated by the NAT instance in either direction for the given protocol. This value MUST be monotone increasing in the periods between updates of the NAT instance natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.2.1.5,NATV2-MIB::natv2ProtocolPortMapCreations,Counter64,read-only,,current,,The cumulative number of port map entries created by the NAT instance for the given protocol. This value MUST be monotone increasing in the periods between updates of the NAT instance natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.2.1.6,NATV2-MIB::natv2ProtocolPortMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets dropped because the packet would have triggered the creation of a new port map entry, but no port could be allocated for the protocol concerned. The usual case for this will be for a NAT instance that supports address pooling and the 'Paired' pooling behavior recommended by RFC 4787, where the internal endpoint has used up all of the ports allocated to it for the address it was mapped to in the selected address pool in the external realm concerned and cannot be given more ports because - policy or implementation prevents it from having a second address in the same pool, and - policy or unavailability prevents it from acquiring more ports at its originally assigned address. If the NAT instance supports address pooling but its pooling behavior is 'Arbitrary' (meaning that the NAT instance can allocate a new port mapping for the given internal endpoint on any address in the selected address pool and is not bound to what it has already mapped for that endpoint), then this counter is incremented when all ports for the protocol concerned over the whole of the selected address pool are already in use. Finally, if the NAT instance has no configured address pooling, then this counter is incremented because all ports for the protocol concerned over the whole of the NAT instance for the external realm concerned are already in use. This value MUST be monotone increasing in the periods between updates of the NAT instance natv2InstanceDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2InstanceDiscontinuityTime.
.1.3.6.1.2.1.234.2.3,NATV2-MIB::natv2PoolTable,,not-accessible,,current,,Table of address pools, applicable only if these are supported by the NAT instance. An address pool is a set of addresses and ports in a particular realm, available for assignment to the 'external' portion of a mapping. Where more than one pool has been configured for the realm, policy determines which subscribers and/or services are mapped to which pool. natv2PoolTable provides basic information, state, statistics, and two notification thresholds for each pool. natv2PoolRangeTable is an expansion table for natv2PoolTable that identifies particular address ranges allocated to the pool.
.1.3.6.1.2.1.234.2.3.1,NATV2-MIB::natv2PoolEntry,,not-accessible,natv2PoolInstanceIndex:natv2PoolIndex,current,,Entry in the table of address pools.
.1.3.6.1.2.1.234.2.3.1.1,NATV2-MIB::natv2PoolInstanceIndex,Unsigned32,not-accessible,,current,,NAT instance index. It is up to the agent implementation to determine and operate upon only those values that correspond to in-service NAT instances.
.1.3.6.1.2.1.234.2.3.1.2,NATV2-MIB::natv2PoolIndex,Unsigned32,not-accessible,,current,,Index of an address pool that is unique for a given NAT instance. It is up to the agent implementation to determine and operate upon only those values that correspond to provisioned pools.
.1.3.6.1.2.1.234.2.3.1.3,NATV2-MIB::natv2PoolRealm,OCTET,read-only,,current,,Address realm to which this pool's addresses belong.
.1.3.6.1.2.1.234.2.3.1.4,NATV2-MIB::natv2PoolAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type supplied by this address pool. This will be the same for all pools in a given realm (by definition of an address realm). Values other than ipv4(1) or ipv6(2) would be unexpected.
.1.3.6.1.2.1.234.2.3.1.5,NATV2-MIB::natv2PoolMinimumPort,Unsigned32,read-only,,current,,Minimum port number of the range that can be allocated in this pool. Applies to all protocols supported by the NAT instance.
.1.3.6.1.2.1.234.2.3.1.6,NATV2-MIB::natv2PoolMaximumPort,Unsigned32,read-only,,current,,Maximum port number of the range that can be allocated in this pool. Applies to all protocols supported by the NAT instance.
.1.3.6.1.2.1.234.2.3.1.7,NATV2-MIB::natv2PoolAddressMapEntries,Unsigned32,read-only,,current,,The current number of address map entries using external addresses drawn from this pool, including static mappings. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Address map entries are also tracked per subscriber and per instance.
.1.3.6.1.2.1.234.2.3.1.8,NATV2-MIB::natv2PoolPortMapEntries,Unsigned32,read-only,,current,,The current number of entries in the port map table using external addresses and ports drawn from this pool, including static mappings. This definition includes 'hairpin' mappings, where the external realm is the same as the internal one. Port map entries are also tracked per subscriber, per instance, and per protocol within the instance.
.1.3.6.1.2.1.234.2.3.1.9,NATV2-MIB::natv2PoolAddressMapCreations,Counter64,read-only,,current,,The cumulative number of address map entries created in this pool, including static mappings. Address map entries are also tracked per instance and per subscriber. This value MUST be monotone increasing in the periods between updates of the entity's natv2PoolDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2PoolDiscontinuityTime.
.1.3.6.1.2.1.234.2.3.1.10,NATV2-MIB::natv2PoolPortMapCreations,Counter64,read-only,,current,,The cumulative number of port map entries created in this pool, including static mappings. Port map entries are also tracked per instance, per protocol, and per subscriber. This value MUST be monotone increasing in the periods between updates of the entity's natv2PoolDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2PoolDiscontinuityTime.
.1.3.6.1.2.1.234.2.3.1.11,NATV2-MIB::natv2PoolAddressMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets originated by the subscriber that were dropped because the packet would have triggered the creation of a new address map entry, but no address could be allocated from this address pool because all addresses in the pool have already been fully allocated. Counters of this event are also provided per instance, per protocol, and per subscriber. This value MUST be monotone increasing in the periods between updates of the entity's natv2PoolDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2PoolDiscontinuityTime.
.1.3.6.1.2.1.234.2.3.1.12,NATV2-MIB::natv2PoolPortMapFailureDrops,Counter64,read-only,,current,,The cumulative number of packets dropped because the packet would have triggered the creation of a new port map entry, but no port could be allocated for the protocol concerned. The usual case for this will be for a NAT instance that supports the 'Paired' pooling behavior recommended by RFC 4787, where the internal endpoint has used up all of the ports allocated to it for the address it was mapped to in this pool and cannot be given more ports because - policy or implementation prevents it from having a second address in the same pool, and - policy or unavailability prevents it from acquiring more ports at its originally assigned address. If the NAT instance pooling behavior is 'Arbitrary' (meaning that the NAT instance can allocate a new port mapping for the given internal endpoint on any address in the selected address pool and is not bound to what it has already mapped for that endpoint), then this counter is incremented when all ports for the protocol concerned over the whole of this address pool are already in use. This value MUST be monotone increasing in the periods between updates of the entity's natv2PoolDiscontinuityTime. If a manager detects a change in the latter since the last time it sampled this counter, it SHOULD NOT make use of the difference between the latest value of the counter and any value retrieved before the new value of natv2PoolDiscontinuityTime.
.1.3.6.1.2.1.234.2.3.1.13,NATV2-MIB::natv2PoolDiscontinuityTime,TimeTicks,read-only,,current,,Snapshot of the value of the sysUpTime object at the beginning of the latest period of continuity of the statistical counters associated with this address pool. This MUST be initialized when the address pool is configured and MUST be updated whenever the port or address ranges allocated to the pool change.
.1.3.6.1.2.1.234.2.3.1.14,NATV2-MIB::natv2PoolThresholdUsageLow,Integer32,read-write,,current,,Threshold for reporting low utilization of the address pool. Utilization at a given instant is calculated as the percentage of ports allocated in port map entries for the most-used protocol at that instant. If utilization is less than or equal to natv2PoolThresholdUsageLow, an instance of natv2NotificationPoolUsageLow may be triggered, unless disabled by setting it to -1. Reporting is subject to the per-pool notification interval given by natv2PoolNotificationInterval. If multiple notifications are triggered during one interval, the agent MUST report only the one with the lowest value of natv2PoolNotifiedPortMapEntries and discard the others. Implementation note: the percentage specified by this object can be converted to a number of port map entries at configuration time (after port and address ranges have been configured or reconfigured) and compared to the current value of natv2PoolNotifiedPortMapEntries.
.1.3.6.1.2.1.234.2.3.1.15,NATV2-MIB::natv2PoolThresholdUsageHigh,Integer32,read-write,,current,,Threshold for reporting high utilization of the address pool. Utilization at a given instant is calculated as the percentage of ports allocated in port map entries for the most-used protocol at that instant. If utilization is greater than or equal to natv2PoolThresholdUsageHigh, an instance of natv2NotificationPoolUsageHigh may be triggered, unless disabled by setting it to -1. Reporting is subject to the per-pool notification interval given by natv2PoolNotificationInterval. If multiple notifications are triggered during one interval, the agent MUST report only the one with the highest value of natv2PoolNotifiedPortMapEntries and discard the others. In the rare case where both upper and lower thresholds are crossed in the same interval, the agent MUST report only the upper-threshold notification. Implementation note: the percentage specified by this object can be converted to a number of port map entries at configuration time (after port and address ranges have been configured or reconfigured) and compared to the current value of natv2PoolNotifiedPortMapEntries.
.1.3.6.1.2.1.234.2.3.1.16,NATV2-MIB::natv2PoolNotifiedPortMapEntries,Unsigned32,accessible-for-notify,,current,,Number of port map entries using addresses and ports from this address pool for the most-used protocol at a given instant. One of the objects returned by natv2NotificationPoolUsageLow and natv2NotificationPoolUsageHigh.
.1.3.6.1.2.1.234.2.3.1.17,NATV2-MIB::natv2PoolNotifiedPortMapProtocol,Unsigned32,accessible-for-notify,,current,,The most-used protocol (i.e., with the largest number of port map entries) mapped into this address pool at a given instant. One of the objects returned by natv2NotificationPoolUsageLow and natv2NotificationPoolUsageHigh.
.1.3.6.1.2.1.234.2.3.1.18,NATV2-MIB::natv2PoolNotificationInterval,Unsigned32,read-write,,current,,Minimum number of seconds between successive notifications for this address pool. Controls the generation of natv2NotificationPoolUsageLow and natv2NotificationPoolUsageHigh.
.1.3.6.1.2.1.234.2.4,NATV2-MIB::natv2PoolRangeTable,,not-accessible,,current,,This table contains address ranges used by pool entries. It is an expansion of natv2PoolTable.
.1.3.6.1.2.1.234.2.4.1,NATV2-MIB::natv2PoolRangeEntry,,not-accessible,natv2PoolRangeInstanceIndex:natv2PoolRangePoolIndex:natv2PoolRangeRowIndex,current,,NAT pool address range.
.1.3.6.1.2.1.234.2.4.1.1,NATV2-MIB::natv2PoolRangeInstanceIndex,Unsigned32,not-accessible,,current,,Index of the NAT instance on which the address pool and this address range are configured. See Natv2InstanceIndex.
.1.3.6.1.2.1.234.2.4.1.2,NATV2-MIB::natv2PoolRangePoolIndex,Unsigned32,not-accessible,,current,,Index of the address pool to which this address range belongs. See Natv2PoolIndex.
.1.3.6.1.2.1.234.2.4.1.3,NATV2-MIB::natv2PoolRangeRowIndex,Unsigned32,not-accessible,,current,,Row index for successive range entries for the same address pool.
.1.3.6.1.2.1.234.2.4.1.4,NATV2-MIB::natv2PoolRangeBegin,OCTET,read-only,,current,,Lowest address included in this range. The type of address (IPv4 or IPv6) is given by natv2PoolAddressType in natv2PoolTable.
.1.3.6.1.2.1.234.2.4.1.5,NATV2-MIB::natv2PoolRangeEnd,OCTET,read-only,,current,,Highest address included in this range. The type of address (IPv4 or IPv6) is given by natv2PoolAddressType in natv2PoolTable.
.1.3.6.1.2.1.234.2.5,NATV2-MIB::natv2AddressMapTable,,not-accessible,,current,,Table of mappings from the internal to external address. By definition, this is a snapshot of NAT instance state at a given moment. Indexed by NAT instance, internal realm, and internal address in that realm. Provides the mapped external address and, depending on implementation support, identifies the address pool from which the external address and port were taken and the index of the subscriber to which the mapping has been allocated. In the case of DS-Lite (RFC 6333), the indexing realm and address are those of the IPv6 encapsulation rather than the IPv4 inner packet.
.1.3.6.1.2.1.234.2.5.1,NATV2-MIB::natv2AddressMapEntry,,not-accessible,natv2AddressMapInstanceIndex:natv2AddressMapInternalRealm:natv2AddressMapInternalAddressType:natv2AddressMapInternalAddress:natv2AddressMapRowIndex,current,,Mapping from internal to external address.
.1.3.6.1.2.1.234.2.5.1.1,NATV2-MIB::natv2AddressMapInstanceIndex,Unsigned32,not-accessible,,current,,Index of the NAT instance that generated this address map.
.1.3.6.1.2.1.234.2.5.1.2,NATV2-MIB::natv2AddressMapInternalRealm,OCTET,not-accessible,,current,,Realm to which the internal address belongs. In most cases, this is the realm defining the address space of the packet being translated. However, in the case of DS-Lite (RFC 6333), this realm defines the IPv6 outer header address space. It is the combination of that outer header and the inner IPv4 packet header that is remapped to the external address and realm. The corresponding IPv4 realm is restricted in scope to the tunnel, so there is no point in identifying it. The mapped IPv4 address will normally be the well-known value 192.0.0.2, or at least lie in the reserved 192.0.0.0/29 range. If natv2AddressMapSubscriberIndex in this table is a valid subscriber index (i.e., greater than zero), then the value of natv2AddressMapInternalRealm MUST be identical to the value of natv2SubscriberRealm associated with that index.
.1.3.6.1.2.1.234.2.5.1.3,NATV2-MIB::natv2AddressMapInternalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type in the header of packets on the interior side of this mapping. Any value other than ipv4(1) or ipv6(2) would be unexpected. In the DS-Lite case, the address type is ipv6(2).
.1.3.6.1.2.1.234.2.5.1.4,NATV2-MIB::natv2AddressMapInternalAddress,OCTET,not-accessible,,current,,Source address of packets originating from the interior of the association provided by this mapping. The address type is given by natv2AddressMapInternalAddressType. In the case of DS-Lite (RFC 6333), this is the IPv6 tunnel source address. The mapping in this case is considered to be from the combination of the IPv6 tunnel source address natv2AddressMapInternalRealmAddress and the well-known IPv4 inner source address natv2AddressMapInternalMappedAddress to the external address.
.1.3.6.1.2.1.234.2.5.1.5,NATV2-MIB::natv2AddressMapRowIndex,Unsigned32,not-accessible,,current,,Index of a conceptual row corresponding to a mapping of the given internal realm and address to a single external realm and address. Multiple rows will be present because of a promiscuous external address selection policy, policies associating the same internal address with different address pools, or because the same internal realm-address combination is communicating with multiple external address realms.
.1.3.6.1.2.1.234.2.5.1.6,NATV2-MIB::natv2AddressMapInternalMappedAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Internal address type actually translated by this mapping. Any value other than ipv4(1) or ipv6(2) would be unexpected. In the general case, this is the same as given by natv2AddressMapInternalRealmAddressType. In the tunneled case, it is the address type used in the encapsulated packet header. In particular, in the DS-Lite case, the mapped address type is ipv4(1).
.1.3.6.1.2.1.234.2.5.1.7,NATV2-MIB::natv2AddressMapInternalMappedAddress,OCTET,read-only,,current,,Internal address actually translated by this mapping. In the general case, this is the same as natv2AddressMapInternalRealmAddress. The address type is given by natv2AddressMapInternalMappedAddressType. In the case of DS-Lite (RFC 6333), this is the source address of the encapsulated IPv4 packet, normally lying in the well-known range 192.0.0.0/29. The mapping in this case is considered to be from the combination of the IPv6 tunnel source address natv2AddressMapInternalRealmAddress and the well-known IPv4 inner source address natv2AddressMapInternalMappedAddress to the external address.
.1.3.6.1.2.1.234.2.5.1.8,NATV2-MIB::natv2AddressMapExternalRealm,OCTET,read-only,,current,,External address realm to which this mapping maps the internal address. This can be the same as the internal realm in the case of a 'hairpin' connection, but otherwise will be different.
.1.3.6.1.2.1.234.2.5.1.9,NATV2-MIB::natv2AddressMapExternalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type for the external realm. Any value other than ipv4(1) or ipv6(2) would be unexpected.
.1.3.6.1.2.1.234.2.5.1.10,NATV2-MIB::natv2AddressMapExternalAddress,OCTET,read-only,,current,,External address to which the internal address is mapped. The address type is given by natv2AddressMapExternalAddressType. In the DS-Lite case, the mapping is from the combination of the internal IPv6 tunnel source address as presented in this table and the well-known IPv4 source address of the encapsulated IPv4 packet.
.1.3.6.1.2.1.234.2.5.1.11,NATV2-MIB::natv2AddressMapExternalPoolIndex,Unsigned32,read-only,,current,,Index of the address pool in the external realm from which the mapped external address given in natv2AddressMapExternalAddress was taken. Zero if the implementation does not support address pools but has chosen to support this object or if no pool was configured for the given external realm.
.1.3.6.1.2.1.234.2.5.1.12,NATV2-MIB::natv2AddressMapSubscriberIndex,Unsigned32,read-only,,current,,Index of the subscriber to which this address mapping applies, or zero if no subscribers are configured on this NAT instance.
.1.3.6.1.2.1.234.2.6,NATV2-MIB::natv2PortMapTable,,not-accessible,,current,,Table of port map entries indexed by the NAT instance, protocol, and external realm and address. A port map entry associates an internal upper-layer protocol endpoint with an endpoint for the same protocol in the given external realm. By definition, this is a snapshot of NAT instance state at a given moment. The table provides the basic mapping information. In the case of DS-Lite (RFC 6333), the table provides the internal IPv6 tunnel source address in natv2PortMapInternalRealmAddress and the IPv4 source address of the encapsulated packet that is actually translated in natv2PortMapInternalMappedAddress. In the general (non-DS- Lite) case, those two objects will have the same value.
.1.3.6.1.2.1.234.2.6.1,NATV2-MIB::natv2PortMapEntry,,not-accessible,natv2PortMapInstanceIndex:natv2PortMapProtocol:natv2PortMapExternalRealm:natv2PortMapExternalAddressType:natv2PortMapExternalAddress:natv2PortMapExternalPort,current,,A single NAT mapping.
.1.3.6.1.2.1.234.2.6.1.1,NATV2-MIB::natv2PortMapInstanceIndex,Unsigned32,not-accessible,,current,,Index of the NAT instance that created this port map entry.
.1.3.6.1.2.1.234.2.6.1.2,NATV2-MIB::natv2PortMapProtocol,Unsigned32,not-accessible,,current,,The map entry's upper-layer protocol number.
.1.3.6.1.2.1.234.2.6.1.3,NATV2-MIB::natv2PortMapExternalRealm,OCTET,not-accessible,,current,,The realm to which natv2PortMapExternalAddress belongs.
.1.3.6.1.2.1.234.2.6.1.4,NATV2-MIB::natv2PortMapExternalAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type for the external realm. A value other than ipv4(1) or ipv6(2) would be unexpected.
.1.3.6.1.2.1.234.2.6.1.5,NATV2-MIB::natv2PortMapExternalAddress,OCTET,not-accessible,,current,,The mapping's assigned external address. (This address is taken from the address pool identified by natv2PortMapExternalPoolIndex, if the implementation supports address pools and pools are configured for the given external realm.) This is the source address for translated outgoing packets. The address type is given by natv2PortMapExternalAddressType.
.1.3.6.1.2.1.234.2.6.1.6,NATV2-MIB::natv2PortMapExternalPort,Unsigned32,not-accessible,,current,,The mapping's assigned external port number. This is the source port for translated outgoing packets. If the internal port number given by natv2PortMapInternalPort is zero, this value MUST also be zero. Otherwise, this MUST be a non-zero value.
.1.3.6.1.2.1.234.2.6.1.7,NATV2-MIB::natv2PortMapInternalRealm,OCTET,read-only,,current,,The realm to which natv2PortMapInternalRealmAddress belongs. In the general case, this realm contains the address that is being translated. In the DS-Lite (RFC 6333) case, this realm defines the IPv6 address space from which the tunnel source address is taken. The realm of the encapsulated IPv4 address is restricted in scope to the tunnel, so there is no point in identifying it separately.
.1.3.6.1.2.1.234.2.6.1.8,NATV2-MIB::natv2PortMapInternalAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type for addresses in the realm identified by natv2PortMapInternalRealm.
.1.3.6.1.2.1.234.2.6.1.9,NATV2-MIB::natv2PortMapInternalAddress,OCTET,read-only,,current,,Source address for packets received under this mapping on the internal side of the NAT instance. In the general case, this address is the same as the address given in natv2PortMapInternalMappedAddress. In the DS-Lite case, natv2PortMapInternalAddress is the IPv6 tunnel source address. The address type is given by natv2PortMapInternalAddressType.
.1.3.6.1.2.1.234.2.6.1.10,NATV2-MIB::natv2PortMapInternalMappedAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Internal address type actually translated by this mapping. Any value other than ipv4(1) or ipv6(2) would be unexpected. In the general case, this is the same as given by natv2AddressMapInternalAddressType. In the DS-Lite case, the address type is ipv4(1).
.1.3.6.1.2.1.234.2.6.1.11,NATV2-MIB::natv2PortMapInternalMappedAddress,OCTET,read-only,,current,,Internal address actually translated by this mapping. In the general case, this is the same as natv2PortMapInternalRealmAddress. The address type is given by natv2PortMapInternalMappedAddressType. In the case of DS-Lite (RFC 6333), this is the source address of the encapsulated IPv4 packet, normally selected from the well-known range 192.0.0.0/29. The mapping in this case is considered to be from the external address to the combination of the IPv6 tunnel source address natv2PortMapInternalRealmAddress and the well-known IPv4 inner source address natv2PortMapInternalMappedAddress.
.1.3.6.1.2.1.234.2.6.1.12,NATV2-MIB::natv2PortMapInternalPort,Unsigned32,read-only,,current,,The mapping's internal port number. If this is zero, ports are not translated (i.e., the NAT instance is a pure NAT rather than a Network Address and Port Translator (NAPT)).
.1.3.6.1.2.1.234.2.6.1.13,NATV2-MIB::natv2PortMapExternalPoolIndex,Unsigned32,read-only,,current,,Identifies the address pool from which the external address in this port map entry was taken. Zero if the implementation does not support address pools but has chosen to support this object or if no pools are configured for the given external realm.
.1.3.6.1.2.1.234.2.6.1.14,NATV2-MIB::natv2PortMapSubscriberIndex,Unsigned32,read-only,,current,,Subscriber using this map entry. Zero if the implementation does not support subscribers but has chosen to support this object.
.1.3.6.1.2.1.234.3,NATV2-MIB::natv2MIBConformance,,,,,,
.1.3.6.1.2.1.234.3.1,NATV2-MIB::natv2MIBCompliances,,,,,,
.1.3.6.1.2.1.234.3.1.1,NATV2-MIB::natv2MIBBasicCompliance,,,,,,Describes the requirements for conformance to the basic NAT application of NATV2-MIB.
.1.3.6.1.2.1.234.3.1.2,NATV2-MIB::natv2MIBPooledNATCompliance,,,,,,Describes the requirements for conformance to the pooled NAT application of NATV2-MIB.
.1.3.6.1.2.1.234.3.1.3,NATV2-MIB::natv2MIBCGNCompliance,,,,,,Describes the requirements for conformance to the carrier-grade NAT application of NATV2-MIB.
.1.3.6.1.2.1.234.3.2,NATV2-MIB::natv2MIBGroups,,,,,,
.1.3.6.1.2.1.234.3.2.1,NATV2-MIB::natv2BasicNotificationGroup,,,,,,Notifications that MUST be supported by all NAT applications.
.1.3.6.1.2.1.234.3.2.2,NATV2-MIB::natv2BasicInstanceLevelGroup,,,,,,Per-instance objects that MUST be supported by implementations of all NAT applications.
.1.3.6.1.2.1.234.3.2.3,NATV2-MIB::natv2PooledNotificationGroup,,,,,,Notifications that MUST be supported by pooled and carrier-grade NAT applications.
.1.3.6.1.2.1.234.3.2.4,NATV2-MIB::natv2PooledInstanceLevelGroup,,,,,,Per-instance objects that MUST be supported by implementations of the pooled and carrier-grade NAT applications.
.1.3.6.1.2.1.234.3.2.5,NATV2-MIB::natv2CGNNotificationGroup,,,,,,Notification that MUST be supported by implementations of the carrier-grade NAT application.
.1.3.6.1.2.1.234.3.2.6,NATV2-MIB::natv2CGNDeviceLevelGroup,,,,,,Device-level objects that MUST be supported by the carrier-grade NAT application.
.1.3.6.1.2.1.234.3.2.7,NATV2-MIB::natv2CGNInstanceLevelGroup,,,,,,Per-instance objects that MUST be supported by the carrier-grade NAT application.
.1.3.6.1.2.1.235,SNMP-USM-HMAC-SHA2-MIB::snmpUsmHmacSha2MIB,,,,,,Definitions of Object Identities needed for the use of HMAC-SHA2 Authentication Protocols by SNMP's User-based Security Model. Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.236,VM-MIB::vmMIB,,,,,,This MIB module is for use in managing a hypervisor and virtual machines controlled by the hypervisor. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.236.0,VM-MIB::vmNotifications,,,,,,
.1.3.6.1.2.1.236.0.1,VM-MIB::vmRunning,,,,,,This notification is generated when the operational state of a virtual machine has been changed to running(4) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.2,VM-MIB::vmShuttingdown,,,,,,This notification is generated when the operational state of a virtual machine has been changed to shuttingdown(10) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.3,VM-MIB::vmShutdown,,,,,,This notification is generated when the operational state of a virtual machine has been changed to shutdown(11) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.4,VM-MIB::vmPaused,,,,,,This notification is generated when the operational state of a virtual machine has been changed to paused(8) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.5,VM-MIB::vmSuspending,,,,,,This notification is generated when the operational state of a virtual machine has been changed to suspending(5) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.6,VM-MIB::vmSuspended,,,,,,This notification is generated when the operational state of a virtual machine has been changed to suspended(6) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.7,VM-MIB::vmResuming,,,,,,This notification is generated when the operational state of a virtual machine has been changed to resuming(7) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.8,VM-MIB::vmMigrating,,,,,,This notification is generated when the operational state of a virtual machine has been changed to migrating(9) from some other state. The other state is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.9,VM-MIB::vmCrashed,,,,,,This notification is generated when a virtual machine has been crashed. The previous state of the virtual machine is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.10,VM-MIB::vmDeleted,,,,,,This notification is generated when a virtual machine has been deleted. The prior state of the virtual machine is indicated by the included value of vmOperState.
.1.3.6.1.2.1.236.0.11,VM-MIB::vmBulkRunning,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to running(4) from any prior state, except for running(4). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.12,VM-MIB::vmBulkShuttingdown,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to shuttingdown(10) from a state other than shuttingdown(10). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.13,VM-MIB::vmBulkShutdown,,,,,,This notification is generated when the operational state of one or more virtual machine has been changed to shutdown(11) from a state other than shutdown(11). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.14,VM-MIB::vmBulkPaused,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to paused(8) from a state other than paused(8). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.15,VM-MIB::vmBulkSuspending,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to suspending(5) from a state other than suspending(5). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.16,VM-MIB::vmBulkSuspended,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to suspended(6) from a state other than suspended(6). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.17,VM-MIB::vmBulkResuming,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to resuming(7) from a state other than resuming(7). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.18,VM-MIB::vmBulkMigrating,,,,,,This notification is generated when the operational state of one or more virtual machines has been changed to migrating(9) from a state other than migrating(9). Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.19,VM-MIB::vmBulkCrashed,,,,,,This notification is generated when one or more virtual machines have been crashed. Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.0.20,VM-MIB::vmBulkDeleted,,,,,,This notification is generated when one or more virtual machines have been deleted. Management stations are encouraged to subsequently poll the subset of virtual machines of interest for vmOperState.
.1.3.6.1.2.1.236.1,VM-MIB::vmObjects,,,,,,
.1.3.6.1.2.1.236.1.1,VM-MIB::vmHypervisor,,,,,,
.1.3.6.1.2.1.236.1.1.1,VM-MIB::vmHvSoftware,OCTET,read-only,,current,,A textual description of the hypervisor software. This value SHOULD NOT include its version as it SHOULD be included in 'vmHvVersion'.
.1.3.6.1.2.1.236.1.1.2,VM-MIB::vmHvVersion,OCTET,read-only,,current,,A textual description of the version of the hypervisor software.
.1.3.6.1.2.1.236.1.1.3,VM-MIB::vmHvObjectID,OBJECT,read-only,,current,,The vendor's authoritative identification of the hypervisor software contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1). Note that this is different from sysObjectID in the SNMPv2-MIB (RFC 3418) because sysObjectID is not the identification of the hypervisor software but the device, firmware, or management operating system.
.1.3.6.1.2.1.236.1.1.4,VM-MIB::vmHvUpTime,TimeTicks,read-only,,current,,The time (in centiseconds) since the hypervisor was last re-initialized. Note that this is different from sysUpTime in the SNMPv2-MIB (RFC 3418) and hrSystemUptime in the HOST-RESOURCES-MIB (RFC 2790) because sysUpTime is the uptime of the network management portion of the system, and hrSystemUptime is the uptime of the management operating system but not the hypervisor software.
.1.3.6.1.2.1.236.1.2,VM-MIB::vmNumber,Integer32,read-only,,current,,The number of virtual machines (regardless of their current state) present on this hypervisor.
.1.3.6.1.2.1.236.1.3,VM-MIB::vmTableLastChange,TimeTicks,read-only,,current,,The value of vmHvUpTime at the time of the last creation or deletion of an entry in the vmTable.
.1.3.6.1.2.1.236.1.4,VM-MIB::vmTable,,not-accessible,,current,,A list of virtual machine entries. The number of entries is given by the value of vmNumber.
.1.3.6.1.2.1.236.1.4.1,VM-MIB::vmEntry,,not-accessible,vmIndex,current,,An entry containing management information applicable to a particular virtual machine.
.1.3.6.1.2.1.236.1.4.1.1,VM-MIB::vmIndex,Integer32,not-accessible,,current,,A unique value, greater than zero, identifying the virtual machine. The value assigned to a given virtual machine may not persist across re-initialization of the hypervisor. A command generator MUST use the vmUUID to identify a given virtual machine of interest.
.1.3.6.1.2.1.236.1.4.1.2,VM-MIB::vmName,OCTET,read-only,,current,,A textual name of the virtual machine.
.1.3.6.1.2.1.236.1.4.1.3,VM-MIB::vmUUID,OCTET,read-only,,current,,The virtual machine's 128-bit Universally Unique Identifier (UUID) or the zero-length string when a UUID is not available. If set, the UUID MUST uniquely identify a virtual machine from all other virtual machines in an administrative domain. A zero-length octet string is returned if no UUID information is known.
.1.3.6.1.2.1.236.1.4.1.4,VM-MIB::vmOSType,OCTET,read-only,,current,,A textual description containing operating system information installed on the virtual machine. This value corresponds to the operating system the hypervisor assumes to be running when the virtual machine is started. This may differ from the actual operating system in case the virtual machine boots into a different operating system.
.1.3.6.1.2.1.236.1.4.1.5,VM-MIB::vmAdminState,INTEGER,read-only,,current,running(1):suspended(2):paused(3):shutdown(4),The administrative state of the virtual machine.
.1.3.6.1.2.1.236.1.4.1.6,VM-MIB::vmOperState,INTEGER,read-only,,current,unknown(1):other(2):preparing(3):running(4):suspending(5):suspended(6):resuming(7):paused(8):migrating(9):shuttingdown(10):shutdown(11):crashed(12),The operational state of the virtual machine.
.1.3.6.1.2.1.236.1.4.1.7,VM-MIB::vmAutoStart,INTEGER,read-only,,current,unknown(1):enabled(2):disabled(3),The autostart configuration of the virtual machine. If this value is enable(2), the virtual machine automatically starts at the next initialization of the hypervisor.
.1.3.6.1.2.1.236.1.4.1.8,VM-MIB::vmPersistent,INTEGER,read-only,,current,unknown(1):persistent(2):transient(3),This value indicates whether the virtual machine has a persistent configuration, which means the virtual machine will still exist after its shutdown.
.1.3.6.1.2.1.236.1.4.1.9,VM-MIB::vmCurCpuNumber,Integer32,read-only,,current,,The number of virtual CPUs currently assigned to the virtual machine.
.1.3.6.1.2.1.236.1.4.1.10,VM-MIB::vmMinCpuNumber,Integer32,read-only,,current,,The minimum number of virtual CPUs that are assigned to the virtual machine when it is in a power-on state. The value -1 indicates that there is no hard boundary for the minimum number of virtual CPUs.
.1.3.6.1.2.1.236.1.4.1.11,VM-MIB::vmMaxCpuNumber,Integer32,read-only,,current,,The maximum number of virtual CPUs that are assigned to the virtual machine when it is in a power-on state. The value -1 indicates that there is no limit.
.1.3.6.1.2.1.236.1.4.1.12,VM-MIB::vmMemUnit,Integer32,read-only,,current,,The multiplication unit in bytes for vmCurMem, vmMinMem, and vmMaxMem. For example, when this value is 1024, the memory size unit for vmCurMem, vmMinMem, and vmMaxMem is KiB.
.1.3.6.1.2.1.236.1.4.1.13,VM-MIB::vmCurMem,Integer32,read-only,,current,,The current memory size currently allocated to the virtual memory module in the unit designated by vmMemUnit.
.1.3.6.1.2.1.236.1.4.1.14,VM-MIB::vmMinMem,Integer32,read-only,,current,,The minimum memory size defined to the virtual machine in the unit designated by vmMemUnit. The value -1 indicates that there is no hard boundary for the minimum memory size.
.1.3.6.1.2.1.236.1.4.1.15,VM-MIB::vmMaxMem,Integer32,read-only,,current,,The maximum memory size defined to the virtual machine in the unit designated by vmMemUnit. The value -1 indicates that there is no limit.
.1.3.6.1.2.1.236.1.4.1.16,VM-MIB::vmUpTime,TimeTicks,read-only,,current,,The time (in centiseconds) since the administrative state of the virtual machine was last changed from shutdown(4) to running(1).
.1.3.6.1.2.1.236.1.4.1.17,VM-MIB::vmCpuTime,Counter64,read-only,,current,,The total CPU time used in microseconds. If the number of virtual CPUs is larger than 1, vmCpuTime may exceed real time. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.5,VM-MIB::vmCpuTable,,not-accessible,,current,,The table of virtual CPUs provided by the hypervisor.
.1.3.6.1.2.1.236.1.5.1,VM-MIB::vmCpuEntry,,not-accessible,vmIndex:vmCpuIndex,current,,An entry for one virtual processor assigned to a virtual machine.
.1.3.6.1.2.1.236.1.5.1.1,VM-MIB::vmCpuIndex,Integer32,not-accessible,,current,,A unique value identifying a virtual CPU assigned to the virtual machine.
.1.3.6.1.2.1.236.1.5.1.2,VM-MIB::vmCpuCoreTime,Counter64,read-only,,current,,The total CPU time used by this virtual CPU in microseconds. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.6,VM-MIB::vmCpuAffinityTable,,not-accessible,,current,,A list of CPU affinity entries of a virtual CPU.
.1.3.6.1.2.1.236.1.6.1,VM-MIB::vmCpuAffinityEntry,,not-accessible,vmIndex:vmCpuIndex:vmCpuPhysIndex,current,,An entry containing CPU affinity associated with a particular virtual machine.
.1.3.6.1.2.1.236.1.6.1.2,VM-MIB::vmCpuPhysIndex,Integer32,not-accessible,,current,,A value identifying a physical CPU on the hypervisor. On systems implementing the HOST-RESOURCES-MIB, the value MUST be the same value that is used as the index in the hrProcessorTable (hrDeviceIndex).
.1.3.6.1.2.1.236.1.6.1.3,VM-MIB::vmCpuAffinity,INTEGER,read-only,,current,unknown(0):enable(1):disable(2),The CPU affinity of this virtual CPU to the physical CPU represented by 'vmCpuPhysIndex'.
.1.3.6.1.2.1.236.1.7,VM-MIB::vmStorageTable,,not-accessible,,current,,The conceptual table of virtual storage devices attached to the virtual machine.
.1.3.6.1.2.1.236.1.7.1,VM-MIB::vmStorageEntry,,not-accessible,vmStorageVmIndex:vmStorageIndex,current,,An entry for one virtual storage device attached to the virtual machine.
.1.3.6.1.2.1.236.1.7.1.1,VM-MIB::vmStorageVmIndex,Integer32,not-accessible,,current,,This value identifies the virtual machine (guest) this storage device has been allocated to. The value zero indicates that the storage device is currently not allocated to any virtual machines.
.1.3.6.1.2.1.236.1.7.1.2,VM-MIB::vmStorageIndex,Integer32,not-accessible,,current,,A unique value identifying a virtual storage device allocated to the virtual machine.
.1.3.6.1.2.1.236.1.7.1.3,VM-MIB::vmStorageParent,Integer32,read-only,,current,,The value of hrStorageIndex, which is the parent (i.e., physical) device of this virtual device on systems implementing the HOST-RESOURCES-MIB. The value zero denotes this virtual device is not any child represented in the hrStorageTable.
.1.3.6.1.2.1.236.1.7.1.4,VM-MIB::vmStorageSourceType,INTEGER,read-only,,current,unknown(1):other(2):block(3):raw(4):sparse(5):network(6),The source type of the virtual storage device.
.1.3.6.1.2.1.236.1.7.1.5,VM-MIB::vmStorageSourceTypeString,OCTET,read-only,,current,,A (detailed) textual string of the source type of the virtual storage device. For example, this represents the specific format name of the sparse file.
.1.3.6.1.2.1.236.1.7.1.6,VM-MIB::vmStorageResourceID,OCTET,read-only,,current,,A textual string that represents the resource identifier of the virtual storage. For example, this contains the path to the disk image file that corresponds to the virtual storage.
.1.3.6.1.2.1.236.1.7.1.7,VM-MIB::vmStorageAccess,INTEGER,read-only,,current,unknown(1):readwrite(2):readonly(3),The access permission of the virtual storage device.
.1.3.6.1.2.1.236.1.7.1.8,VM-MIB::vmStorageMediaType,INTEGER,read-only,,current,other(1):unknown(2):hardDisk(3):opticalDisk(4):floppyDisk(5),The media type of the virtual storage device.
.1.3.6.1.2.1.236.1.7.1.9,VM-MIB::vmStorageMediaTypeString,OCTET,read-only,,current,,A (detailed) textual string of the virtual storage media. For example, this represents the specific driver name of the emulated media such as 'IDE' and 'SCSI'.
.1.3.6.1.2.1.236.1.7.1.10,VM-MIB::vmStorageSizeUnit,Integer32,read-only,,current,,The multiplication unit in bytes for vmStorageDefinedSize and vmStorageAllocatedSize. For example, when this value is 1048576, the storage size unit for vmStorageDefinedSize and vmStorageAllocatedSize is MiB.
.1.3.6.1.2.1.236.1.7.1.11,VM-MIB::vmStorageDefinedSize,Integer32,read-only,,current,,The defined virtual storage size defined in the unit designated by vmStorageSizeUnit. If this information is not available, this value MUST be -1.
.1.3.6.1.2.1.236.1.7.1.12,VM-MIB::vmStorageAllocatedSize,Integer32,read-only,,current,,The storage size allocated to the virtual storage from a physical storage in the unit designated by vmStorageSizeUnit. When the virtual storage is block device or raw file, this value and vmStorageDefinedSize are supposed to equal. This value MUST NOT be different from vmStorageDefinedSize when vmStorageSourceType is 'block' or 'raw'. If this information is not available, this value MUST be -1.
.1.3.6.1.2.1.236.1.7.1.13,VM-MIB::vmStorageReadIOs,Counter64,read-only,,current,,The number of read I/O requests. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.7.1.14,VM-MIB::vmStorageWriteIOs,Counter64,read-only,,current,,The number of write I/O requests. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.7.1.15,VM-MIB::vmStorageReadOctets,Counter64,read-only,,current,,The total number of bytes read from this device. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.7.1.16,VM-MIB::vmStorageWriteOctets,Counter64,read-only,,current,,The total number of bytes written to this device. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.7.1.17,VM-MIB::vmStorageReadLatency,Counter64,read-only,,current,,The total number of microseconds read requests have been queued for this device. This would typically be implemented by storing the high precision system timestamp of when the request is received from the virtual machine with the request, the difference between this initial timestamp and the time at which the requested operation has completed SHOULD be converted to microseconds and accumulated. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.7.1.18,VM-MIB::vmStorageWriteLatency,Counter64,read-only,,current,,The total number of microseconds write requests have been queued for this device. This would typically be implemented by storing the high precision system timestamp of when the request is received from the virtual machine with the request; the difference between this initial timestamp and the time at which the requested operation has completed SHOULD be converted to microseconds and accumulated. Discontinuities in the value of this counter can occur at re-initialization of the hypervisor and administrative state (vmAdminState) changes of the virtual machine.
.1.3.6.1.2.1.236.1.8,VM-MIB::vmNetworkTable,,not-accessible,,current,,The conceptual table of virtual network interfaces attached to the virtual machine.
.1.3.6.1.2.1.236.1.8.1,VM-MIB::vmNetworkEntry,,not-accessible,vmIndex:vmNetworkIndex,current,,An entry for one virtual network interface attached to the virtual machine.
.1.3.6.1.2.1.236.1.8.1.1,VM-MIB::vmNetworkIndex,Integer32,not-accessible,,current,,A unique value identifying a virtual network interface allocated to the virtual machine.
.1.3.6.1.2.1.236.1.8.1.2,VM-MIB::vmNetworkIfIndex,Integer32,read-only,,current,,The value of ifIndex, which corresponds to this virtual network interface. If this device is not represented in the ifTable, then this value MUST be zero.
.1.3.6.1.2.1.236.1.8.1.3,VM-MIB::vmNetworkParent,Integer32,read-only,,current,,The value of ifIndex, which corresponds to the parent (i.e., physical) device of this virtual device. The value zero denotes this virtual device is not any child represented in the ifTable.
.1.3.6.1.2.1.236.1.8.1.4,VM-MIB::vmNetworkModel,OCTET,read-only,,current,,A textual string containing the (emulated) model of the virtual network interface. For example, this value is 'virtio' when the emulation driver model is virtio.
.1.3.6.1.2.1.236.1.8.1.5,VM-MIB::vmNetworkPhysAddress,OCTET,read-only,,current,,The Media Access Control (MAC) address of the virtual network interface.
.1.3.6.1.2.1.236.1.9,VM-MIB::vmPerVMNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),Indicates if the notification generator will send notifications per virtual machine. Changes to this object MUST NOT persist across re-initialization of the management system, e.g., SNMP agent.
.1.3.6.1.2.1.236.1.10,VM-MIB::vmBulkNotificationsEnabled,INTEGER,read-write,,current,true(1):false(2),Indicates if the notification generator will send notifications per set of virtual machines. Changes to this object MUST NOT persist across re-initialization of the management system, e.g., SNMP agent.
.1.3.6.1.2.1.236.1.11,VM-MIB::vmAffectedVMs,OCTET,accessible-for-notify,,current,,A complete list of virtual machines whose state has changed. This object is the only object sent with bulk notifications.
.1.3.6.1.2.1.236.2,VM-MIB::vmConformance,,,,,,
.1.3.6.1.2.1.236.2.1,VM-MIB::vmCompliances,,,,,,
.1.3.6.1.2.1.236.2.1.1,VM-MIB::vmFullCompliances,,,,,,Compliance statement for implementations supporting read/write access, according to the object definitions.
.1.3.6.1.2.1.236.2.1.2,VM-MIB::vmReadOnlyCompliances,,,,,,Compliance statement for implementations supporting only read-only access.
.1.3.6.1.2.1.236.2.2,VM-MIB::vmGroups,,,,,,
.1.3.6.1.2.1.236.2.2.1,VM-MIB::vmHypervisorGroup,,,,,,A collection of objects providing insight into the hypervisor itself.
.1.3.6.1.2.1.236.2.2.2,VM-MIB::vmVirtualMachineGroup,,,,,,A collection of objects providing insight into the virtual machines controlled by a hypervisor.
.1.3.6.1.2.1.236.2.2.3,VM-MIB::vmCpuGroup,,,,,,A collection of objects providing insight into the virtual machines controlled by a hypervisor.
.1.3.6.1.2.1.236.2.2.4,VM-MIB::vmCpuAffinityGroup,,,,,,A collection of objects providing insight into the virtual machines controlled by a hypervisor.
.1.3.6.1.2.1.236.2.2.5,VM-MIB::vmStorageGroup,,,,,,A collection of objects providing insight into the virtual storage devices controlled by a hypervisor.
.1.3.6.1.2.1.236.2.2.6,VM-MIB::vmNetworkGroup,,,,,,A collection of objects providing insight into the virtual network interfaces controlled by a hypervisor.
.1.3.6.1.2.1.236.2.2.7,VM-MIB::vmPerVMNotificationOptionalGroup,,,,,,A collection of notifications for per-VM notification of changes to virtual machine state (vmOperState) as reported by a hypervisor.
.1.3.6.1.2.1.236.2.2.8,VM-MIB::vmBulkNotificationsVariablesGroup,,,,,,The variables used in vmBulkNotificationOptionalGroup virtual network interfaces controlled by a hypervisor.
.1.3.6.1.2.1.236.2.2.9,VM-MIB::vmBulkNotificationOptionalGroup,,,,,,A collection of notifications for bulk notification of changes to virtual machine state (vmOperState) as reported by a given hypervisor.
.1.3.6.1.2.1.237,IANA-STORAGE-MEDIA-TYPE-MIB::ianaStorageMediaTypeMIB,,,,,,This MIB module defines Textual Conventions representing the media type of a storage device. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.238,TRILL-OAM-MIB::trillOamMib,,,,,,This MIB module contains the management objects for the management of TRILL Services Operations, Administration and Maintenance. Initial version. Published as RFC 7784. Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). ------------------------------------------------------------- Abbreviations Used Term Definition CFM Connectivity Fault Management IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force ITU-T International Telecommunication Union - Telecommunication Standardization Bureau FCOI The Final, Cross-Connect Error, Out-of-band, and In-band flags from the TRILL OAM Application Identifier TLV. LBM Loopback Message MA Maintenance Association (equivalent to a MEG) MAC Media Access Control MD Maintenance Domain (equivalent to an OAM Domain in Metro Ethernet Forum (MEF) 17) MEG Maintenance Entity Group (equivalent to a MA) MEG Level Maintenance Entity Group Level (equivalent to MD Level) MEP Maintenance Association End Point MIB Management Information Base MIP Maintenance Domain Intermediate Point MTVM Multi-destination Tree Verification Message MTVR Multi-destination Tree Verification Reply OAM Operations, Administration, and Maintenance On-Demand OAM actions that are initiated via manual intervention for a limited time to carry out diagnostics. On-demand OAM can result in singular or periodic OAM actions during the diagnostic time interval. PTM Path Trace Message PTR Path Trace Reply RFC Request for Comments SNMP Simple Network Management Protocol TLV Type-Length-Value, a method of encoding Objects TRILL Transparent Interconnection of Lots of Links VLAN Virtual LAN
.1.3.6.1.2.1.238.0,TRILL-OAM-MIB::trillOamNotifications,,,,,,
.1.3.6.1.2.1.238.0.1,TRILL-OAM-MIB::trillOamFaultAlarm,,,,,,A MEP flow has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the flow that has detected the fault. The management entity receiving the notification can identify the system from the network source address of the notification and can identify the flow reporting the defect by the indices in the OID of the trillOamMepFlowIndex and trillOamFlowDefect variable in the notification: dot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (dot1agCfmMdTable). dot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association network table entry (dot1agCfmMaNetTable) and (with the MD table index and component ID) of the MEP's MA component table entry (dot1agCfmMaCompTable). dot1agCfmMepIdentifier - MEP Identifier and final index into the MEP table (dot1agCfmMepTable). trillOamMepFlowCfgIndex - Index identifies indicates the specific flow for the MEP
.1.3.6.1.2.1.238.1,TRILL-OAM-MIB::trillOamMibObjects,,,,,,
.1.3.6.1.2.1.238.1.1,TRILL-OAM-MIB::trillOamMep,,,,,,
.1.3.6.1.2.1.238.1.1.1,TRILL-OAM-MIB::trillOamMepTable,,not-accessible,,current,,This table is an extension of the dot1agCfmMepTable and rows are automatically added or deleted from this table based upon row creation and destruction of the dot1agCfmMepTable. This table represents the local MEP TRILL OAM configuration table. The primary purpose of this table is provide local parameters for the TRILL OAM function found in RFC 7455 and instantiated at a MEP.
.1.3.6.1.2.1.238.1.1.1.1,TRILL-OAM-MIB::trillOamMepEntry,,not-accessible,,current,,The conceptual row of trillOamMepTable.
.1.3.6.1.2.1.238.1.1.1.1.1,TRILL-OAM-MIB::trillOamMepRName,Unsigned32,read-only,,current,,This object contains the RBridge Nickname field of the TRILL RBridge as defined in RFC 6325, Section 3.7.
.1.3.6.1.2.1.238.1.1.1.1.2,TRILL-OAM-MIB::trillOamMepNextPtmTId,Counter32,read-only,,current,,Next Sequence Number / Transaction Identifier to be sent in a Multi-destination message. This Sequence Number can be zero because it wraps around. Implementation of this identifier should be should provide a unique code value in order to identify the Transaction Identifier for a MEP with multiple flows.
.1.3.6.1.2.1.238.1.1.1.1.3,TRILL-OAM-MIB::trillOamMepNextMtvmTId,Counter32,read-only,,current,,Next Sequence Number / Transaction Identifier to be sent in a Multi-destination message. This Sequence Number can be zero because it wraps around. An implementation should be unique to identify Transaction Identifier for a MEP with multiple flows.
.1.3.6.1.2.1.238.1.1.1.1.4,TRILL-OAM-MIB::trillOamMepPtrIn,Counter32,read-only,,current,,Total number of valid, in-order Path Trace Replies received.
.1.3.6.1.2.1.238.1.1.1.1.5,TRILL-OAM-MIB::trillOamMepPtrInOutofOrder,Counter32,read-only,,current,,Total number of valid, out-of-order Path Trace Replies received.
.1.3.6.1.2.1.238.1.1.1.1.6,TRILL-OAM-MIB::trillOamMepPtrOut,Counter32,read-only,,current,,Total number of valid, Path Trace Replies transmitted.
.1.3.6.1.2.1.238.1.1.1.1.7,TRILL-OAM-MIB::trillOamMepMtvrIn,Counter32,read-only,,current,,Total number of valid, in-order Multi-destination Replies received.
.1.3.6.1.2.1.238.1.1.1.1.8,TRILL-OAM-MIB::trillOamMepMtvrInOutofOrder,Counter32,read-only,,current,,Total number of valid, out-of-order Multi-destination Replies received.
.1.3.6.1.2.1.238.1.1.1.1.9,TRILL-OAM-MIB::trillOamMepMtvrOut,Counter32,read-only,,current,,Total number of valid, Multi-destination Replies transmitted.
.1.3.6.1.2.1.238.1.1.1.1.10,TRILL-OAM-MIB::trillOamMepTxLbmDestRName,Unsigned32,read-create,,current,,The Target Destination RBridge Nickname field, as defined in RFC 6325, Section 3.7, to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.11,TRILL-OAM-MIB::trillOamMepTxLbmHC,Unsigned32,read-create,,current,,The Hop Count field to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.12,TRILL-OAM-MIB::trillOamMepTxLbmReplyModeOob,INTEGER,read-create,,current,true(1):false(2),True indicates that the Reply to an LBM is out of band and the out-of-band IP Address TLV is to be transmitted. False indicates that in-band reply is transmitted.
.1.3.6.1.2.1.238.1.1.1.1.13,TRILL-OAM-MIB::trillOamMepTransmitLbmReplyIp,OCTET,read-create,,current,,The IP address for an out-of-band IP Address TLV that is to be transmitted. Maximum length for IPv6 is 16 octets and IPv4 is 4 octets.
.1.3.6.1.2.1.238.1.1.1.1.14,TRILL-OAM-MIB::trillOamMepTxLbmFlowEntropy,OCTET,read-create,,current,,96-byte Flow Entropy, as defined in RFC 7455, to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.15,TRILL-OAM-MIB::trillOamMepTxPtmDestRName,Unsigned32,read-create,,current,,The Target Destination RBridge Nickname field, as defined in RFC 6325, Section 3.7, to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.16,TRILL-OAM-MIB::trillOamMepTxPtmHC,Unsigned32,read-create,,current,,The Hop Count field to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.17,TRILL-OAM-MIB::trillOamMepTxPtmReplyModeOob,INTEGER,read-create,,current,true(1):false(2),True indicates that a Reply to a PTM will be out of band and the out-of-band IP Address TLV is to be transmitted. False indicates that an in-band reply is transmitted.
.1.3.6.1.2.1.238.1.1.1.1.18,TRILL-OAM-MIB::trillOamMepTransmitPtmReplyIp,OCTET,read-create,,current,,The IP address for an out-of-band IP Address TLV to be transmitted. The maximum length for an IPv6 address is 16 octets. The maximum length for an IPv4 address is 4 octets.
.1.3.6.1.2.1.238.1.1.1.1.19,TRILL-OAM-MIB::trillOamMepTxPtmFlowEntropy,OCTET,read-create,,current,,96-byte Flow Entropy, as defined in RFC 7455, to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.20,TRILL-OAM-MIB::trillOamMepTxPtmStatus,INTEGER,read-create,,current,true(1):false(2),A Boolean flag set to TRUE by the MEP Path Trace Initiator State Machine or a MIB manager to indicate that another PTM is being transmitted. This is reset to FALSE by the MEP Initiator State Machine. The PTM managed objects in the MEP table are used in a manner similar to that described for LBM transmission in the dot1agCfmMepTable. As per RFC 7455, Section 10, operation of the Path Trace Message is identical to the Loopback message except that it is first transmitted with a TRILL Header Hop Count field value of 1 and then retransmitted with an incrementing Hop Count until a response is received from the destination RBridge, or the Hop Count reaches a configured maximum value. The trillOamMepTxPtmStatus status is reset to FALSE by the initiator when the last PTM is transmitted.
.1.3.6.1.2.1.238.1.1.1.1.21,TRILL-OAM-MIB::trillOamMepTxPtmResultOK,INTEGER,read-create,,current,true(1):false(2),Indicates the following results of the operation: - true indicates the Path Trace Message(s) will be (or has been) sent. - false indicates the Path Trace Message(s) will not be sent.
.1.3.6.1.2.1.238.1.1.1.1.22,TRILL-OAM-MIB::trillOamMepTxPtmSeqNumber,Unsigned32,read-create,,current,,The Path Trace Transaction Identifier of the first PTM (to be) sent. The value returned is undefined if trillOamMepTxPtmResultOK is false.
.1.3.6.1.2.1.238.1.1.1.1.23,TRILL-OAM-MIB::trillOamMepTxPtmMessages,Integer32,read-create,,current,,The number of Path Trace messages to be transmitted. As per RFC 7455, Section 10, the first Path Trace Message is transmitted with a Hop Count of 1; an RBridge may continue to retransmit the request at periodic intervals with an incrementing Hop Count until a response is received from the destination RBridge or the Hop Count reaches a configured maximum value. The event of the Destination response being received or the Hop Count reaching its maximum is treated as a single Counter increment of this object.
.1.3.6.1.2.1.238.1.1.1.1.24,TRILL-OAM-MIB::trillOamMepTxMtvmTree,Unsigned32,read-create,,current,,The Multi-destination Tree identifier, as defined in RFC 6325, for an MTVM.
.1.3.6.1.2.1.238.1.1.1.1.25,TRILL-OAM-MIB::trillOamMepTxMtvmHC,Unsigned32,read-create,,current,,The Hop Count field to be transmitted. 
.1.3.6.1.2.1.238.1.1.1.1.26,TRILL-OAM-MIB::trillOamMepTxMtvmReplyModeOob,INTEGER,read-create,,current,true(1):false(2),True indicates that the reply to an MTVM is out of band and this out-of-band IP Address TLV is where the reply is to be transmitted. False indicates that an in-band reply is transmitted.
.1.3.6.1.2.1.238.1.1.1.1.27,TRILL-OAM-MIB::trillOamMepTransmitMtvmReplyIp,OCTET,read-create,,current,,IP address for an out-of-band IP Address TLV that is to be transmitted. The maximum length for IPv6 is 16 octets and IPv4 is 4 octets.
.1.3.6.1.2.1.238.1.1.1.1.28,TRILL-OAM-MIB::trillOamMepTxMtvmFlowEntropy,OCTET,read-create,,current,,96-byte Flow Entropy, as defined in RFC 7455, to be transmitted.
.1.3.6.1.2.1.238.1.1.1.1.29,TRILL-OAM-MIB::trillOamMepTxMtvmStatus,INTEGER,read-create,,current,true(1):false(2),A Boolean flag set to TRUE by the MEP Multi-destination Initiator State Machine or a MIB manager to indicate that another MTVM is being transmitted. Reset to FALSE by the MEP Initiator State Machine. The MTVM-managed objects in the MEP table are used in a manner similar to that described for LBM transmission in the dot1agCfmMepTable. As per RFC 7455, Section 11, operation of the MTVM is identical to the Loopback message except that it is first transmitted with a TRILL Header Hop Count field value of 1 and it is retransmitted incrementing the Hop Count until a response is received from the destination RBridge or the Hop Count reaches a configured maximum value. The trillOamMepTxMtvmStatus Status is reset to FALSE by the initiator when the last MTVM is transmitted.
.1.3.6.1.2.1.238.1.1.1.1.30,TRILL-OAM-MIB::trillOamMepTxMtvmResultOK,INTEGER,read-create,,current,true(1):false(2),Indicates the result of the operation in the following way: - true indicates the Multi-destination Message(s) will be (or has been) sent. - false indicates the Multi-destination Message(s) will not be sent.
.1.3.6.1.2.1.238.1.1.1.1.31,TRILL-OAM-MIB::trillOamMepTxMtvmMessages,Integer32,read-create,,current,,The number of Multi-destination messages to be transmitted. The RBridge transmit the Multi-destination message incrementing the session Identification Number at periodic interval until this count expires.
.1.3.6.1.2.1.238.1.1.1.1.32,TRILL-OAM-MIB::trillOamMepTxMtvmSeqNumber,Unsigned32,read-create,,current,,The Multi-destination Transaction Identifier of the first MTVM (to be) sent. The value returned is undefined if trillOamMepTxMtvmResultOK is false.
.1.3.6.1.2.1.238.1.1.1.1.33,TRILL-OAM-MIB::trillOamMepTxMtvmScopeList,OCTET,read-create,,current,,The Multi-destination RBridge Scope list, which requires 2 octets per RBridge.
.1.3.6.1.2.1.238.1.1.1.1.34,TRILL-OAM-MIB::trillOamMepDiscontinuityTime,TimeTicks,read-only,,current,,Snapshot of the value of the sysUpTime object at the beginning of the latest period of continuity of the statistical counters associated with this MEP.
.1.3.6.1.2.1.238.1.1.2,TRILL-OAM-MIB::trillOamMepFlowCfgTable,,not-accessible,,current,,This table includes configuration objects and operations for the TRILL OAM facilities in RFC 7455. Each row in the table represents a Flow Configuration Entry for the defined MEP. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MANET, and MEP tables. The fourth index is the specific Flow Configuration Entry on the selected MEP. Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored.
.1.3.6.1.2.1.238.1.1.2.1,TRILL-OAM-MIB::trillOamMepFlowCfgEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:trillOamMepFlowCfgIndex,current,,The conceptual row of trillOamMepFlowCfgTable.
.1.3.6.1.2.1.238.1.1.2.1.1,TRILL-OAM-MIB::trillOamMepFlowCfgIndex,Unsigned32,not-accessible,,current,,An index to the TRILL OAM MEP Flow Configuration table, which indicates the specific flow for the MEP. The index is never reused for other flow sessions on the same MEP while this session is active. The index value keeps increasing until it wraps to 0. This value can also be used in the flow-identifier TLV RFC 7455.
.1.3.6.1.2.1.238.1.1.2.1.2,TRILL-OAM-MIB::trillOamMepFlowCfgFlowEntropy,OCTET,read-create,,current,,This is 96 bytes of Flow Entropy as described in TRILL OAM, RFC 7455.
.1.3.6.1.2.1.238.1.1.2.1.3,TRILL-OAM-MIB::trillOamMepFlowCfgDestRName,Unsigned32,read-create,,current,,The Target Destination RBridge Nickname field, as defined in RFC 6325, Section 3.7, to be transmitted.
.1.3.6.1.2.1.238.1.1.2.1.4,TRILL-OAM-MIB::trillOamMepFlowCfgFlowHC,Unsigned32,read-create,,current,,The Hop Count field to be transmitted.
.1.3.6.1.2.1.238.1.1.2.1.5,TRILL-OAM-MIB::trillOamMepFlowCfgRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated.
.1.3.6.1.2.1.238.1.1.3,TRILL-OAM-MIB::trillOamPtrTable,,not-accessible,,current,,This table includes Path Trace Reply objects and operations for the TRILL OAM facilities as described in RFC 7455. Each row in the table represents a Path Trace Reply Entry for the defined MEP and Transaction. This table uses four indices. The first three indices are the indices of the Maintenance Domain, MANET, and MEP tables. The fourth index is the specific Transaction Identifier on the selected MEP. Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored.
.1.3.6.1.2.1.238.1.1.3.1,TRILL-OAM-MIB::trillOamPtrEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:trillOamMepPtrTransactionId,current,,The conceptual row of trillOamPtrTable.
.1.3.6.1.2.1.238.1.1.3.1.1,TRILL-OAM-MIB::trillOamMepPtrTransactionId,Unsigned32,not-accessible,,current,,Sequence Number / Transaction Identifier returned by a previous transmit path trace message command, indicating which PTM's response is going to be returned.
.1.3.6.1.2.1.238.1.1.3.1.2,TRILL-OAM-MIB::trillOamMepPtrHC,Unsigned32,read-only,,current,,Hop Count field value for a returned PTR.
.1.3.6.1.2.1.238.1.1.3.1.3,TRILL-OAM-MIB::trillOamMepPtrFlag,Unsigned32,read-only,,current,,FCOI (TRILL OAM Message TLV) field value for a returned PTR.
.1.3.6.1.2.1.238.1.1.3.1.4,TRILL-OAM-MIB::trillOamMepPtrErrorCode,Unsigned32,read-only,,current,,Return Code and Return Sub-code value for a returned PTR.
.1.3.6.1.2.1.238.1.1.3.1.5,TRILL-OAM-MIB::trillOamMepPtrTerminalMep,INTEGER,read-only,,current,true(1):false(2),A boolean value stating whether the forwarded PTM reached a MEP enclosing its MA, as returned in the Terminal MEP flag of the Flags field.
.1.3.6.1.2.1.238.1.1.3.1.6,TRILL-OAM-MIB::trillOamMepPtrLastEgressId,Unsigned32,read-only,,current,,An Integer field holding the Last Egress Identifier returned in the PTR Upstream RBridge Nickname TLV of the PTR. The Last Egress Identifier identifies the Upstream Nickname.
.1.3.6.1.2.1.238.1.1.3.1.7,TRILL-OAM-MIB::trillOamMepPtrIngress,INTEGER,read-only,,current,ingNoTlv(0):ingOk(1):ingDown(2):ingBlocked(3):ingVid(4),The value returned in the Ingress Action field of the PTR. The value ingNoTlv(0) indicates that no Reply Ingress TLV was returned in the PTM.
.1.3.6.1.2.1.238.1.1.3.1.8,TRILL-OAM-MIB::trillOamMepPtrIngressMac,OCTET,read-only,,current,,MAC address returned in the ingress MAC address field.
.1.3.6.1.2.1.238.1.1.3.1.9,TRILL-OAM-MIB::trillOamMepPtrIngressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Ingress Port ID. The format of this object is determined by the value of the trillOamMepPtrIngressPortIdSubtype object.
.1.3.6.1.2.1.238.1.1.3.1.10,TRILL-OAM-MIB::trillOamMepPtrIngressPortId,OCTET,read-only,,current,,Ingress Port ID. The format of this object is determined by the value of the trillOamMepPtrIngressPortId object.
.1.3.6.1.2.1.238.1.1.3.1.11,TRILL-OAM-MIB::trillOamMepPtrEgress,INTEGER,read-only,,current,egrNoTlv(0):egrOK(1):egrDown(2):egrBlocked(3):egrVid(4),The value returned in the Egress Action field of the PTR. The value ingNoTlv(0) indicates that no Reply Egress TLV was returned in the PTM.
.1.3.6.1.2.1.238.1.1.3.1.12,TRILL-OAM-MIB::trillOamMepPtrEgressMac,OCTET,read-only,,current,,MAC address returned in the egress MAC address field.
.1.3.6.1.2.1.238.1.1.3.1.13,TRILL-OAM-MIB::trillOamMepPtrEgressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Egress Port ID. The format of this object is determined by the value of the trillOamMepPtrEgressPortIdSubtype object.
.1.3.6.1.2.1.238.1.1.3.1.14,TRILL-OAM-MIB::trillOamMepPtrEgressPortId,OCTET,read-only,,current,,Egress Port ID. The format of this object is determined by the value of the trillOamMepPtrEgressPortId object.
.1.3.6.1.2.1.238.1.1.3.1.15,TRILL-OAM-MIB::trillOamMepPtrChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),This object specifies the format of the Chassis ID returned in the Sender ID TLV of the PTR, if any. This value is meaningless if the trillOamMepPtrChassisId has a length of 0.
.1.3.6.1.2.1.238.1.1.3.1.16,TRILL-OAM-MIB::trillOamMepPtrChassisId,OCTET,read-only,,current,,The Chassis ID returned in the Sender ID TLV of the PTR, if any. The format of this object is determined by the value of the trillOamMepPtrChassisIdSubtype object.
.1.3.6.1.2.1.238.1.1.3.1.17,TRILL-OAM-MIB::trillOamMepPtrOrganizationSpecificTlv,OCTET,read-only,,current,,All organization-specific TLVs returned in the PTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.
.1.3.6.1.2.1.238.1.1.3.1.18,TRILL-OAM-MIB::trillOamMepPtrNextHopNicknames,OCTET,read-only,,current,,Next hop RBridge List TLV returned in the PTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.
.1.3.6.1.2.1.238.1.1.4,TRILL-OAM-MIB::trillOamMtvrTable,,not-accessible,,current,,This table includes Multi-destination Reply objects and operations for the TRILL OAM facilities described in RFC 7455. Each row in the table represents a Multi-destination Reply Entry for the defined MEP and Transaction. This table uses five indices. The first three indices are the indices of the Maintenance Domain, MANET, and MEP tables. The fourth index is the specific Transaction Identifier on the selected MEP. The fifth index is the receive order of Multi-destination replies. Some writable objects in this table are only applicable in certain cases (as described under each object), and attempts to write values for them in other cases will be ignored.
.1.3.6.1.2.1.238.1.1.4.1,TRILL-OAM-MIB::trillOamMtvrEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:trillOamMepPtrTransactionId:trillOamMepMtvrReceiveOrder,current,,The conceptual row of trillOamMtvrTable.
.1.3.6.1.2.1.238.1.1.4.1.1,TRILL-OAM-MIB::trillOamMepMtvrTransactionId,Unsigned32,not-accessible,,current,,Sequence Number / Transaction Identifier returned by a previously transmitted Multi-destination message command indicating which MTVM's response is going to be returned.
.1.3.6.1.2.1.238.1.1.4.1.2,TRILL-OAM-MIB::trillOamMepMtvrReceiveOrder,Unsigned32,not-accessible,,current,,An index to distinguish among multiple MTVRs with same MTVR Transaction Identifier field value. trillOamMepMtvrReceiveOrder is assigned sequentially from 1, in the order that the Multi-destination Tree Initiator received the MTVRs.
.1.3.6.1.2.1.238.1.1.4.1.3,TRILL-OAM-MIB::trillOamMepMtvrFlag,Unsigned32,read-only,,current,,FCOI (TRILL OAM Message TLV) field value for a returned MTVR.
.1.3.6.1.2.1.238.1.1.4.1.4,TRILL-OAM-MIB::trillOamMepMtvrErrorCode,Unsigned32,read-only,,current,,Return Code and Return Sub-code value for a returned MTVR.
.1.3.6.1.2.1.238.1.1.4.1.5,TRILL-OAM-MIB::trillOamMepMtvrLastEgressId,Unsigned32,read-only,,current,,An Integer field holding the Last Egress Identifier returned in the MTVR Upstream RBridge Nickname TLV of the MTVR. The Last Egress Identifier identifies the Upstream Nickname.
.1.3.6.1.2.1.238.1.1.4.1.6,TRILL-OAM-MIB::trillOamMepMtvrIngress,INTEGER,read-only,,current,ingNoTlv(0):ingOk(1):ingDown(2):ingBlocked(3):ingVid(4),The value returned in the Ingress Action field of the MTVR. The value ingNoTlv(0) indicates that no Reply Ingress TLV was returned in the MTVM.
.1.3.6.1.2.1.238.1.1.4.1.7,TRILL-OAM-MIB::trillOamMepMtvrIngressMac,OCTET,read-only,,current,,MAC address returned in the ingress MAC address field.
.1.3.6.1.2.1.238.1.1.4.1.8,TRILL-OAM-MIB::trillOamMepMtvrIngressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Ingress Port ID. The format of this object is determined by the value of the trillOamMepMtvrIngressPortIdSubtype object.
.1.3.6.1.2.1.238.1.1.4.1.9,TRILL-OAM-MIB::trillOamMepMtvrIngressPortId,OCTET,read-only,,current,,Ingress Port ID. The format of this object is determined by the value of the trillOamMepMtvrIngressPortId object.
.1.3.6.1.2.1.238.1.1.4.1.10,TRILL-OAM-MIB::trillOamMepMtvrEgress,INTEGER,read-only,,current,egrNoTlv(0):egrOK(1):egrDown(2):egrBlocked(3):egrVid(4),The value returned in the Egress Action field of the MTVR. The value ingNoTlv(0) indicates that no Reply Egress TLV was returned in the MTVR.
.1.3.6.1.2.1.238.1.1.4.1.11,TRILL-OAM-MIB::trillOamMepMtvrEgressMac,OCTET,read-only,,current,,MAC address returned in the egress MAC address field.
.1.3.6.1.2.1.238.1.1.4.1.12,TRILL-OAM-MIB::trillOamMepMtvrEgressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Egress Port ID. The format of this object is determined by the value of the trillOamMepMtvrEgressPortIdSubtype object.
.1.3.6.1.2.1.238.1.1.4.1.13,TRILL-OAM-MIB::trillOamMepMtvrEgressPortId,OCTET,read-only,,current,,Egress Port ID. The format of this object is determined by the value of the trillOamMepMtvrEgressPortId object.
.1.3.6.1.2.1.238.1.1.4.1.14,TRILL-OAM-MIB::trillOamMepMtvrChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),This object specifies the format of the Chassis ID returned in the Sender ID TLV of the MTVR, if any. This value is meaningless if the trillOamMepMtvrChassisId has a length of 0.
.1.3.6.1.2.1.238.1.1.4.1.15,TRILL-OAM-MIB::trillOamMepMtvrChassisId,OCTET,read-only,,current,,The Chassis ID returned in the Sender ID TLV of the MTVR, if any. The format of this object is determined by the value of the trillOamMepMtvrChassisIdSubtype object.
.1.3.6.1.2.1.238.1.1.4.1.16,TRILL-OAM-MIB::trillOamMepMtvrOrganizationSpecificTlv,OCTET,read-only,,current,,All organization-specific TLVs returned in the MTVR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.
.1.3.6.1.2.1.238.1.1.4.1.17,TRILL-OAM-MIB::trillOamMepMtvrNextHopNicknames,OCTET,read-only,,current,,Next hop RBridge List TLV returned in the PTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.
.1.3.6.1.2.1.238.1.1.4.1.18,TRILL-OAM-MIB::trillOamMepMtvrReceiverAvailability,INTEGER,read-only,,current,true(1):false(2),A value of true indicates that the MTVR response contained Multicast receiver availability TLV.
.1.3.6.1.2.1.238.1.1.4.1.19,TRILL-OAM-MIB::trillOamMepMtvrReceiverCount,INTEGER,read-only,,current,true(1):false(2),Indicates the number of multicast receivers available on the responding RBridge on the VLAN specified by the diagnostic VLAN.
.1.3.6.1.2.1.238.1.1.5,TRILL-OAM-MIB::trillOamMepDbTable,,not-accessible,,current,,This table is an extension of the dot1agCfmMepDbTable and rows are automatically added to or deleted from this table based upon row creation and destruction of the dot1agCfmMepDbTable.
.1.3.6.1.2.1.238.1.1.5.1,TRILL-OAM-MIB::trillOamMepDbEntry,,not-accessible,,current,,The conceptual row of trillOamMepDbTable.
.1.3.6.1.2.1.238.1.1.5.1.1,TRILL-OAM-MIB::trillOamMepDbFlowIndex,Unsigned32,read-only,,current,,This object identifies the flow. If the Flow Identifier TLV is received, then the index received can also be used.
.1.3.6.1.2.1.238.1.1.5.1.2,TRILL-OAM-MIB::trillOamMepDbFlowEntropy,OCTET,read-only,,current,,96 byte Flow Entropy.
.1.3.6.1.2.1.238.1.1.5.1.3,TRILL-OAM-MIB::trillOamMepDbFlowState,INTEGER,read-only,,current,rMepIdle(1):rMepStart(2):rMepFailed(3):rMepOk(4),The operational state of the remote MEP (flow-based) IFF State machines. State Machine is running now per flow.
.1.3.6.1.2.1.238.1.1.5.1.4,TRILL-OAM-MIB::trillOamMepDbFlowFailedOkTime,TimeTicks,read-only,,current,,The Time (sysUpTime) at which the Remote MEP flow state machine last entered either the RMEP_FAILED or RMEP_OK state.
.1.3.6.1.2.1.238.1.1.5.1.5,TRILL-OAM-MIB::trillOamMepDbRBridgeName,Unsigned32,read-only,,current,,Remote MEP RBridge Nickname.
.1.3.6.1.2.1.238.1.1.5.1.6,TRILL-OAM-MIB::trillOamMepDbLastGoodSeqNum,Counter32,read-only,,current,,Last Sequence Number received.
.1.3.6.1.2.1.238.2,TRILL-OAM-MIB::trillOamMibConformance,,,,,,
.1.3.6.1.2.1.238.2.1,TRILL-OAM-MIB::trillOamMibCompliances,,,,,,
.1.3.6.1.2.1.238.2.1.1,TRILL-OAM-MIB::trillOamMibCompliance,,,,,,The compliance statement for the TRILL OAM MIB.
.1.3.6.1.2.1.238.2.1.2,TRILL-OAM-MIB::trillOamMibReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for TRILL-OAM-MIB. Such devices can be monitored but cannot be configured using this MIB module.
.1.3.6.1.2.1.238.2.2,TRILL-OAM-MIB::trillOamMibGroups,,,,,,
.1.3.6.1.2.1.238.2.2.1,TRILL-OAM-MIB::trillOamMepMandatoryGroup,,,,,,Mandatory objects for the TRILL OAM MEP group.
.1.3.6.1.2.1.238.2.2.2,TRILL-OAM-MIB::trillOamMepFlowCfgTableGroup,,,,,,TRILL OAM MEP Flow Configuration objects group.
.1.3.6.1.2.1.238.2.2.3,TRILL-OAM-MIB::trillOamPtrTableGroup,,,,,,TRILL OAM MEP PTR objects group.
.1.3.6.1.2.1.238.2.2.4,TRILL-OAM-MIB::trillOamMtvrTableGroup,,,,,,TRILL OAM MEP MTVR objects group.
.1.3.6.1.2.1.238.2.2.5,TRILL-OAM-MIB::trillOamMepDbGroup,,,,,,TRILL OAM MEP DB objects group.
.1.3.6.1.2.1.238.2.2.6,TRILL-OAM-MIB::trillOamNotificationGroup,,,,,,A collection of objects describing notifications(traps).
.1.3.6.1.2.1.239,SOFTWIRE-MESH-MIB::swmMIB,,,,,,This MIB module contains managed object definitions for the softwire mesh framework. Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.239.1,SOFTWIRE-MESH-MIB::swmObjects,,,,,,
.1.3.6.1.2.1.239.1.1,SOFTWIRE-MESH-MIB::swmSupportedTunnelTable,,not-accessible,,current,,A table of objects that show what kinds of tunnels can be supported by the AFBR.
.1.3.6.1.2.1.239.1.1.1,SOFTWIRE-MESH-MIB::swmSupportedTunnelEntry,,not-accessible,swmSupportedTunnelType,current,,A set of objects that show what kinds of tunnels can be supported in the AFBR. If the AFBR supports multiple tunnel types, the swmSupportedTunnelTable would have several entries.
.1.3.6.1.2.1.239.1.1.1.1,SOFTWIRE-MESH-MIB::swmSupportedTunnelType,INTEGER,read-only,,current,other(1):direct(2):gre(3):minimal(4):l2tp(5):pptp(6):l2f(7):udp(8):atmp(9):msdp(10):sixToFour(11):sixOverFour(12):isatap(13):teredo(14):ipHttps(15):softwireMesh(16):dsLite(17):aplusp(18),Represents the tunnel type that can be used for softwire mesh scenarios, such as L2TPv3 over IP, GRE, Transmit tunnel endpoint, IPsec in Tunnel-mode, IP in IP tunnel with IPsec Transport Mode, MPLS-in-IP tunnel with IPsec Transport Mode, and IP in IP. There is no restriction on the tunnel type the softwire mesh can use.
.1.3.6.1.2.1.239.1.2,SOFTWIRE-MESH-MIB::swmEncapsTable,,not-accessible,,current,,A table of objects that display the softwire mesh encapsulation information.
.1.3.6.1.2.1.239.1.2.1,SOFTWIRE-MESH-MIB::swmEncapsEntry,,not-accessible,ifIndex:swmEncapsEIPDstType:swmEncapsEIPDst:swmEncapsEIPPrefixLength,current,,A table of objects that manage the softwire mesh I-IP encapsulation destination based on the E-IP destination prefix.
.1.3.6.1.2.1.239.1.2.1.1,SOFTWIRE-MESH-MIB::swmEncapsEIPDstType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for swmEncapsEIPDst. It is different from the tunnelIfAddressType in the tunnelIfTable. The swmEncapsEIPDstType is IPv6 (2) if it is IPv6-over-IPv4 tunneling. The swmEncapsEIPDstType is IPv4 (1) if it is IPv4-over-IPv6 tunneling.
.1.3.6.1.2.1.239.1.2.1.2,SOFTWIRE-MESH-MIB::swmEncapsEIPDst,OCTET,not-accessible,,current,,The E-IP destination prefix, which is used for I-IP encapsulation destination looking up. The type of this address is determined by the value of swmEncapsEIPDstType
.1.3.6.1.2.1.239.1.2.1.3,SOFTWIRE-MESH-MIB::swmEncapsEIPPrefixLength,Unsigned32,not-accessible,,current,,The prefix length of the E-IP destination prefix.
.1.3.6.1.2.1.239.1.2.1.4,SOFTWIRE-MESH-MIB::swmEncapsIIPDstType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for swmEncapsIIPDst. It is the same as the tunnelIfAddressType in the tunnelIfTable.
.1.3.6.1.2.1.239.1.2.1.5,SOFTWIRE-MESH-MIB::swmEncapsIIPDst,OCTET,read-only,,current,,The I-IP destination address, which is used as the encapsulation destination for the corresponding E-IP prefix. Since the tunnelIfRemoteInetAddress in the tunnelIfTable should be 0.0.0.0 or ::, swmEncapIIPDst should be the destination address used in the outer IP header.
.1.3.6.1.2.1.239.1.3,SOFTWIRE-MESH-MIB::swmBGPNeighborTable,,not-accessible,,current,,A table of objects that display the softwire mesh BGP neighbor information.
.1.3.6.1.2.1.239.1.3.1,SOFTWIRE-MESH-MIB::swmBGPNeighborEntry,,not-accessible,ifIndex:swmBGPNeighborInetAddressType:swmBGPNeighborInetAddress,current,,A set of objects that display the softwire mesh BGP neighbor information.
.1.3.6.1.2.1.239.1.3.1.1,SOFTWIRE-MESH-MIB::swmBGPNeighborInetAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object specifies the address type used for swmBGPNeighborInetAddress.
.1.3.6.1.2.1.239.1.3.1.2,SOFTWIRE-MESH-MIB::swmBGPNeighborInetAddress,OCTET,not-accessible,,current,,The address of the AFBR's BGP neighbor. The address type is the same as the tunnelIfAddressType in the tunnelIfTable.
.1.3.6.1.2.1.239.1.3.1.3,SOFTWIRE-MESH-MIB::swmBGPNeighborTunnelType,INTEGER,read-only,,current,other(1):direct(2):gre(3):minimal(4):l2tp(5):pptp(6):l2f(7):udp(8):atmp(9):msdp(10):sixToFour(11):sixOverFour(12):isatap(13):teredo(14):ipHttps(15):softwireMesh(16):dsLite(17):aplusp(18),Represents the type of tunnel that the AFBR chooses to transmit traffic with another AFBR/BGP neighbor.
.1.3.6.1.2.1.239.2,SOFTWIRE-MESH-MIB::swmConformance,,,,,,
.1.3.6.1.2.1.239.2.1,SOFTWIRE-MESH-MIB::swmCompliances,,,,,,
.1.3.6.1.2.1.239.2.1.1,SOFTWIRE-MESH-MIB::swmCompliance,,,,,,Describes the requirements for conformance to the Softwire Mesh MIB. The following index objects cannot be added as OBJECT clauses but nevertheless have compliance requirements: 
.1.3.6.1.2.1.239.2.2,SOFTWIRE-MESH-MIB::swmGroups,,,,,,
.1.3.6.1.2.1.239.2.2.1,SOFTWIRE-MESH-MIB::swmSupportedTunnelGroup,,,,,,The collection of objects that are used to show what kind of tunnel the AFBR supports.
.1.3.6.1.2.1.239.2.2.2,SOFTWIRE-MESH-MIB::swmEncapsGroup,,,,,,The collection of objects that are used to display softwire mesh encapsulation information.
.1.3.6.1.2.1.239.2.2.3,SOFTWIRE-MESH-MIB::swmBGPNeighborGroup,,,,,,The collection of objects that are used to display softwire mesh BGP neighbor information.
.1.3.6.1.2.1.240,DSLite-MIB::dsliteMIB,,,,,,The MIB module is defined for management of objects in the DS-Lite scenario. Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.240.0,DSLite-MIB::dsliteNotifications,,,,,,
.1.3.6.1.2.1.240.0.1,DSLite-MIB::dsliteTunnelNumAlarm,,,,,,This trap is triggered when the number of current DS-Lite tunnels exceeds the value of the dsliteAFTRAlarmConnectNumber.
.1.3.6.1.2.1.240.0.2,DSLite-MIB::dsliteAFTRUserSessionNumAlarm,,,,,,This trap is triggered when user sessions reach the threshold. The threshold is specified by the dsliteAFTRAlarmSessionNumber.
.1.3.6.1.2.1.240.0.3,DSLite-MIB::dsliteAFTRPortUsageOfSpecificIpAlarm,,,,,,This trap is triggered when the used NAT ports of map address reach the threshold. The threshold is specified by the dsliteAFTRAlarmPortNumber.
.1.3.6.1.2.1.240.1,DSLite-MIB::dsliteMIBObjects,,,,,,
.1.3.6.1.2.1.240.1.1,DSLite-MIB::dsliteTunnel,,,,,,
.1.3.6.1.2.1.240.1.1.1,DSLite-MIB::dsliteTunnelTable,,not-accessible,,current,,The (conceptual) table containing information on configured tunnels. This table can be used to map a B4 address to the associated AFTR address. It can also be used for row creation.
.1.3.6.1.2.1.240.1.1.1.1,DSLite-MIB::dsliteTunnelEntry,,not-accessible,dsliteTunnelAddressType:dsliteTunnelStartAddress:dsliteTunnelEndAddress:ifIndex,current,,Each entry in this table contains the information on a particular configured tunnel.
.1.3.6.1.2.1.240.1.1.1.1.1,DSLite-MIB::dsliteTunnelAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object MUST be set to the value of ipv6(2). It describes the address type of the IPv4-in-IPv6 tunnel initiator and endpoint.
.1.3.6.1.2.1.240.1.1.1.1.2,DSLite-MIB::dsliteTunnelStartAddress,OCTET,not-accessible,,current,,The IPv6 address of the initiator of the tunnel. The address type is given by dsliteTunnelAddressType.
.1.3.6.1.2.1.240.1.1.1.1.3,DSLite-MIB::dsliteTunnelEndAddress,OCTET,not-accessible,,current,,The IPv6 address of the endpoint of the tunnel. The address type is given by dsliteTunnelAddressType.
.1.3.6.1.2.1.240.1.1.1.1.4,DSLite-MIB::dsliteTunnelStartAddPreLen,Unsigned32,read-only,,current,,The IPv6 prefix length of the IP address for the initiator of the tunnel(dsliteTunnelStartAddress).
.1.3.6.1.2.1.240.1.2,DSLite-MIB::dsliteNAT,,,,,,
.1.3.6.1.2.1.240.1.2.1,DSLite-MIB::dsliteNATBindTable,,not-accessible,,current,,This table contains information about currently active NAT binds in the NAT of the AFTR. This table adds the IPv6 address of a B4 to the natv2PortMapTable defined in NATV2-MIB (RFC 7659).
.1.3.6.1.2.1.240.1.2.1.1,DSLite-MIB::dsliteNATBindEntry,,not-accessible,dsliteNATBindMappingInstanceIndex:dsliteNATBindMappingProto:dsliteNATBindMappingExtRealm:dsliteNATBindMappingExtAddressType:dsliteNATBindMappingExtAddress:dsliteNATBindMappingExtPort:ifIndex:dsliteTunnelStartAddress,current,,The entry in this table holds the mapping relationship between tunnel information and NAT bind information. Each entry in this table not only needs to match a corresponding entry in the natv2PortMapTable, but also a corresponding entry in the dsliteTunnelTable. So, the INDEX of the entry needs to match a corresponding value in the natv2PortMapTable INDEX and a corresponding value in the dsliteTunnelTable INDEX. These entries are lost upon agent restart.
.1.3.6.1.2.1.240.1.2.1.1.1,DSLite-MIB::dsliteNATBindMappingInstanceIndex,Unsigned32,not-accessible,,current,,Index of the NAT instance that created this port map entry.
.1.3.6.1.2.1.240.1.2.1.1.2,DSLite-MIB::dsliteNATBindMappingProto,Unsigned32,not-accessible,,current,,This object specifies the mapping's transport protocol number.
.1.3.6.1.2.1.240.1.2.1.1.3,DSLite-MIB::dsliteNATBindMappingExtRealm,OCTET,not-accessible,,current,,The realm to which dsliteNATBindMappingExtAddress belongs.
.1.3.6.1.2.1.240.1.2.1.1.4,DSLite-MIB::dsliteNATBindMappingExtAddressType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type for the mapping's external address. This object MUST be set to the value of iPv4(1). The values of ipv6(2), ipv4z(3), and ipv6z(4) are not allowed.
.1.3.6.1.2.1.240.1.2.1.1.5,DSLite-MIB::dsliteNATBindMappingExtAddress,OCTET,not-accessible,,current,,The mapping's external address. This is the source address for translated outgoing packets. The address type is given by dsliteNATBindMappingExtAddressType.
.1.3.6.1.2.1.240.1.2.1.1.6,DSLite-MIB::dsliteNATBindMappingExtPort,Unsigned32,not-accessible,,current,,The mapping's assigned external port number. This is the source port for translated outgoing packets. This MUST be a non-zero value.
.1.3.6.1.2.1.240.1.2.1.1.7,DSLite-MIB::dsliteNATBindMappingIntRealm,OCTET,read-only,,current,,The realm to which natMappingIntAddress belongs. This realm defines the IPv6 address space from which the tunnel source address is taken. The realm of the encapsulated IPv4 address is restricted in scope to the tunnel, so there is no point in identifying it separately.
.1.3.6.1.2.1.240.1.2.1.1.8,DSLite-MIB::dsliteNATBindMappingIntAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),Address type of the mapping's internal address. This object MUST be set to the value of iPv4z(3). The values of ipv4(1), ipv6(2), and ipv6z(4) are not allowed.
.1.3.6.1.2.1.240.1.2.1.1.9,DSLite-MIB::dsliteNATBindMappingIntAddress,OCTET,read-only,,current,,The mapping's internal address. It is the IPv6 tunnel source address. The address type is given by dsliteNATBindMappingIntAddressType.
.1.3.6.1.2.1.240.1.2.1.1.10,DSLite-MIB::dsliteNATBindMappingIntPort,Unsigned32,read-only,,current,,The mapping's internal port number. This MUST be a non-zero value.
.1.3.6.1.2.1.240.1.2.1.1.11,DSLite-MIB::dsliteNATBindMappingPool,Unsigned32,read-only,,current,,Index of the pool that contains this mapping's external address and port. If zero, no pool is associated with this mapping.
.1.3.6.1.2.1.240.1.2.1.1.12,DSLite-MIB::dsliteNATBindMappingMapBehavior,INTEGER,read-only,,current,endpointIndependent(0):addressDependent(1):addressAndPortDependent(2),Mapping behavior as described in Section 4.1 of RFC 4787. endpointIndependent(0), the behavior REQUIRED by RFC 4787, REQ-1 maps the source address and port to the same external address and port for all destination address and port combinations reached through the same external realm and using the given protocol. addressDependent(1) maps to the same external address and port for all destination ports at the same destination address reached through the same external realm and using the given protocol. addressAndPortDependent(2) maps to a separate external address and port combination for each different destination address and port combination reached through the same external realm. For the DS-Lite scenario, it must be addressAndPortDependent(2).
.1.3.6.1.2.1.240.1.2.1.1.13,DSLite-MIB::dsliteNATBindMappingFilterBehavior,INTEGER,read-only,,current,endpointIndependent(0):addressDependent(1):addressAndPortDependent(2),Filtering behavior as described in Section 5 of RFC 4787. endpointIndependent(0) accepts for translation packets from all combinations of remote address and port destined to the mapped external address and port via the given external realm and using the given protocol. addressDependent(1) accepts for translation packets from all remote ports from the same remote source address destined to the mapped external address and port via the given external realm and using the given protocol. addressAndPortDependent(2) accepts for translation only those packets with the same remote source address, port, and protocol incoming from the same external realm as identified when the applicable port map entry was created. RFC 4787, REQ-8 recommends either endpointIndependent(0) or addressDependent(1) filtering behavior, depending on whether application friendliness or security takes priority. For the DS-Lite scenario, it must be addressAndPortDependent(2).
.1.3.6.1.2.1.240.1.2.1.1.14,DSLite-MIB::dsliteNATBindMappingAddressPooling,INTEGER,read-only,,current,arbitrary(0):paired(1),Type of address pooling behavior that was used to create this mapping. arbitrary(0) pooling behavior means that the NAT instance may create the new port mapping using any address in the pool that has a free port for the protocol concerned. paired(1) pooling behavior, the behavior RECOMMENDED by RFC 4787, REQ-2 means that once a given internal address has been mapped to a particular address in a particular pool, further mappings of the same internal address to that pool will reuse the previously assigned pool member address.
.1.3.6.1.2.1.240.1.3,DSLite-MIB::dsliteInfo,,,,,,
.1.3.6.1.2.1.240.1.3.1,DSLite-MIB::dsliteAFTRAlarmScalar,,,,,,
.1.3.6.1.2.1.240.1.3.1.1,DSLite-MIB::dsliteAFTRAlarmB4AddrType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the address type of the B4, which will send an alarm.
.1.3.6.1.2.1.240.1.3.1.2,DSLite-MIB::dsliteAFTRAlarmB4Addr,OCTET,accessible-for-notify,,current,,This object indicates the IP address of B4, which will send an alarm. The address type is given by dsliteAFTRAlarmB4AddrType.
.1.3.6.1.2.1.240.1.3.1.3,DSLite-MIB::dsliteAFTRAlarmProtocolType,INTEGER,accessible-for-notify,,current,tcp(0):udp(1):icmp(2):total(3),This object indicates the transport protocol type of alarm. tcp (0) means that the transport protocol type of alarm is tcp. udp (1) means that the transport protocol type of alarm is udp. icmp (2) means that the transport protocol type of alarm is icmp. total (3) means that the transport protocol type of alarm is total.
.1.3.6.1.2.1.240.1.3.1.4,DSLite-MIB::dsliteAFTRAlarmSpecificIPAddrType,INTEGER,accessible-for-notify,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),This object indicates the address type of the IP address whose port usage has reached the threshold.
.1.3.6.1.2.1.240.1.3.1.5,DSLite-MIB::dsliteAFTRAlarmSpecificIP,OCTET,accessible-for-notify,,current,,This object indicates the IP address whose port usage has reached the threshold. The address type is given by dsliteAFTRAlarmSpecificIPAddrType.
.1.3.6.1.2.1.240.1.3.1.6,DSLite-MIB::dsliteAFTRAlarmConnectNumber,Integer32,read-write,,current,,This object indicates the notification threshold of the DS-Lite tunnels that is active in the AFTR device.
.1.3.6.1.2.1.240.1.3.1.7,DSLite-MIB::dsliteAFTRAlarmSessionNumber,Integer32,read-write,,current,,This object indicates the notification threshold of the IPv4 session for the user.
.1.3.6.1.2.1.240.1.3.1.8,DSLite-MIB::dsliteAFTRAlarmPortNumber,Integer32,read-write,,current,,This object indicates the notification threshold of the NAT ports that have been used by the user.
.1.3.6.1.2.1.240.1.3.2,DSLite-MIB::dsliteStatisticsTable,,not-accessible,,current,,This table provides statistical information about DS-Lite.
.1.3.6.1.2.1.240.1.3.2.1,DSLite-MIB::dsliteStatisticsEntry,,not-accessible,dsliteStatisticsSubscriberIndex,current,,Each entry in this table provides statistical information about DS-Lite.
.1.3.6.1.2.1.240.1.3.2.1.1,DSLite-MIB::dsliteStatisticsSubscriberIndex,Unsigned32,not-accessible,,current,,Index of the subscriber or host. A unique value, greater than zero, for each subscriber in the managed system.
.1.3.6.1.2.1.240.1.3.2.1.2,DSLite-MIB::dsliteStatisticsDiscards,Counter64,read-only,,current,,This object indicates the number of packets discarded from this subscriber.
.1.3.6.1.2.1.240.1.3.2.1.3,DSLite-MIB::dsliteStatisticsSends,Counter64,read-only,,current,,This object indicates the number of packets that is sent to this subscriber.
.1.3.6.1.2.1.240.1.3.2.1.4,DSLite-MIB::dsliteStatisticsReceives,Counter64,read-only,,current,,This object indicates the number of packets that is received from this subscriber.
.1.3.6.1.2.1.240.1.3.2.1.5,DSLite-MIB::dsliteStatisticsIpv4Session,Counter64,read-only,,current,,This object indicates the number of the current IPv4 Sessions.
.1.3.6.1.2.1.240.1.3.2.1.6,DSLite-MIB::dsliteStatisticsIpv6Session,Counter64,read-only,,current,,This object indicates the number of the current IPv6 session. Because the AFTR is also a dual-stack device, it will also forward normal IPv6 packets for the inbound and outbound direction.
.1.3.6.1.2.1.240.2,DSLite-MIB::dsliteConformance,,,,,,
.1.3.6.1.2.1.240.2.1,DSLite-MIB::dsliteCompliances,,,,,,
.1.3.6.1.2.1.240.2.1.1,DSLite-MIB::dsliteCompliance,,,,,,Describes the minimal requirements for conformance to the DS-Lite MIB.
.1.3.6.1.2.1.240.2.2,DSLite-MIB::dsliteGroups,,,,,,
.1.3.6.1.2.1.240.2.2.1,DSLite-MIB::dsliteNATBindGroup,,,,,,A collection of objects to support basic management of NAT binds in the NAT of the AFTR.
.1.3.6.1.2.1.240.2.2.2,DSLite-MIB::dsliteTunnelGroup,,,,,,A collection of objects to support management of DS-Lite tunnels.
.1.3.6.1.2.1.240.2.2.3,DSLite-MIB::dsliteStatisticsGroup,,,,,, A collection of objects to support management of statistical information for AFTR devices.
.1.3.6.1.2.1.240.2.2.4,DSLite-MIB::dsliteNotificationsGroup,,,,,,A collection of objects to support management of trap information for AFTR devices.
.1.3.6.1.2.1.240.2.2.5,DSLite-MIB::dsliteAFTRAlarmScalarGroup,,,,,,A collection of objects to support management of the information about the AFTR alarming scalar.
.1.3.6.1.2.1.241,PTPBASE-MIB::ptpbaseMIB,,,,,,The MIB module for PTP version 2 Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). Overview of PTP version 2 (IEEE Std. 1588-2008) [IEEE-1588-2008] defines a protocol enabling precise synchronization of clocks in measurement and control systems implemented with packet-based networks, the Precision Time Protocol version 2 (PTPv2). This MIB module does not address PTPv1, the earlier version defined in IEEE Std. 1588-2002. The protocol is applicable to network elements communicating using IP. The protocol enables heterogeneous systems that include clocks of various inherent precision, resolution, and stability to synchronize to a grandmaster clock. The protocol supports system-wide synchronization accuracy in the sub-microsecond range with minimal network and local clock computing resources. [IEEE-1588-2008] uses UDP/IP or Ethernet and can be adapted to other mappings. It includes formal mechanisms for message extensions, higher sampling rates, correction for asymmetry, a clock type to reduce error accumulation in large topologies, and specifications on how to incorporate the resulting additional data into the synchronization protocol. [IEEE-1588-2008] also defines conformance and management capability. MIB description This MIB module supports the Precision Time Protocol version 2 (PTPv2, hereafter designated as PTP) features of network element system devices, when using the default PTP profile described in [IEEE-1588-2008] when running over the IP network layer. It is envisioned that this MIB module will complement other managed objects to be defined to monitor and measure the performance of the PTP devices and telecom clocks supporting specific PTP profiles. Some other PTP profiles have their own MIB modules defined as part of the profile, and this MIB module is not intended to replace those MIB modules. Technical terms used in this module are defined in [IEEE-1588-2008]. The MIB module refers to sections of [IEEE-1588-2008]. Abbreviations: E2E End-to-End EUI Extended Unique Identifier GPS Global Positioning System IANA Internet Assigned Numbers Authority IP Internet Protocol NTP Network Time Protocol (see [RFC5905]) P2P Peer-to-Peer PTP Precision Time Protocol TAI International Atomic Time UDP User Datagram Protocol UTC Coordinated Universal Time References: [IEEE-1588-2008] IEEE Standard for A Precision Clock Synchronization Protocol for Networked Measurement and Control Systems, IEEE Std. 1588-2008, July 2008. The below table specifies the object formats of the various textual conventions used. Data type mapping Textual Convention SYNTAX ------------------- --------------------- ------------------ 5.3.2 TimeInterval PtpClockTimeInterval OCTET STRING(SIZE(1..255)) 5.3.3 Timestamp PtpClockTimestamp OCTET STRING(SIZE(6)) 5.3.4 ClockIdentity PtpClockIdentity OCTET STRING(SIZE(8)) 5.3.5 PortIdentity PtpClockPortNumber INTEGER(1..65535) 5.3.7 ClockQuality PtpClockQualityClassType 
.1.3.6.1.2.1.241.0,PTPBASE-MIB::ptpbaseMIBNotifs,,,,,,
.1.3.6.1.2.1.241.1,PTPBASE-MIB::ptpbaseMIBObjects,,,,,,
.1.3.6.1.2.1.241.1.1,PTPBASE-MIB::ptpbaseMIBSystemInfo,,,,,,
.1.3.6.1.2.1.241.1.1.1,PTPBASE-MIB::ptpbaseSystemTable,,not-accessible,,current,,Table of count information about the PTP system for all domains.
.1.3.6.1.2.1.241.1.1.1.1,PTPBASE-MIB::ptpbaseSystemEntry,,not-accessible,ptpDomainIndex:ptpInstanceIndex,current,,A table entry that contains count information about a single domain. New row entries are added when the PTP clock for this domain is configured, while the unconfiguration of the PTP clock removes them.
.1.3.6.1.2.1.241.1.1.1.1.1,PTPBASE-MIB::ptpDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices. The Clock Domain is a logical group of clocks and devices that synchronize with each other using the PTP protocol. 0 Default domain 1 Alternate domain 1 2 Alternate domain 2 3 Alternate domain 3 4 - 127 User-defined domains 128 - 255 Reserved
.1.3.6.1.2.1.241.1.1.1.1.2,PTPBASE-MIB::ptpInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this domain.
.1.3.6.1.2.1.241.1.1.1.1.3,PTPBASE-MIB::ptpDomainClockPortsTotal,Gauge32,read-only,,current,,This object specifies the total number of clock ports configured within a domain in the system.
.1.3.6.1.2.1.241.1.1.2,PTPBASE-MIB::ptpbaseSystemDomainTable,,not-accessible,,current,,Table of information about the PTP system for all clock modes -- ordinary, boundary, or transparent.
.1.3.6.1.2.1.241.1.1.2.1,PTPBASE-MIB::ptpbaseSystemDomainEntry,,not-accessible,ptpbaseSystemDomainClockTypeIndex,current,,A table entry that contains information about a single clock mode for the PTP system. A row entry gets added when PTP clocks are configured on the node.
.1.3.6.1.2.1.241.1.1.2.1.1,PTPBASE-MIB::ptpbaseSystemDomainClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.1.2.1.2,PTPBASE-MIB::ptpbaseSystemDomainTotals,Unsigned32,read-only,,current,,This object specifies the total number of PTP domains for this particular clock type configured in this node.
.1.3.6.1.2.1.241.1.1.3,PTPBASE-MIB::ptpbaseSystemProfile,INTEGER,read-only,,current,default(1):telecom(2):vendorspecific(3),This object specifies the PTP profile implemented on the system.
.1.3.6.1.2.1.241.1.2,PTPBASE-MIB::ptpbaseMIBClockInfo,,,,,,
.1.3.6.1.2.1.241.1.2.1,PTPBASE-MIB::ptpbaseClockCurrentDSTable,,not-accessible,,current,,Table of information about the PTP clock currentDS for all domains.
.1.3.6.1.2.1.241.1.2.1.1,PTPBASE-MIB::ptpbaseClockCurrentDSEntry,,not-accessible,ptpbaseClockCurrentDSDomainIndex:ptpbaseClockCurrentDSClockTypeIndex:ptpbaseClockCurrentDSInstanceIndex,current,,A table entry that contains information about a single PTP clock currentDS for a domain.
.1.3.6.1.2.1.241.1.2.1.1.1,PTPBASE-MIB::ptpbaseClockCurrentDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.1.1.2,PTPBASE-MIB::ptpbaseClockCurrentDSClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.1.1.3,PTPBASE-MIB::ptpbaseClockCurrentDSInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.1.1.4,PTPBASE-MIB::ptpbaseClockCurrentDSStepsRemoved,Unsigned32,read-only,,current,,The current clock dataset stepsRemoved value. This object specifies the distance measured by the number of boundary clocks between the local clock and the foreign master as indicated in the stepsRemoved field of Announce messages.
.1.3.6.1.2.1.241.1.2.1.1.5,PTPBASE-MIB::ptpbaseClockCurrentDSOffsetFromMaster,OCTET,read-only,,current,,This object specifies the current clock dataset ClockOffset value. The value of the computation of the offset in time between a slave and a master clock.
.1.3.6.1.2.1.241.1.2.1.1.6,PTPBASE-MIB::ptpbaseClockCurrentDSMeanPathDelay,OCTET,read-only,,current,,This object specifies the current clock dataset MeanPathDelay value. The mean path delay between a pair of ports as measured by the delay request-response mechanism.
.1.3.6.1.2.1.241.1.2.2,PTPBASE-MIB::ptpbaseClockParentDSTable,,not-accessible,,current,,Table of information about the PTP clock parentDS for all domains.
.1.3.6.1.2.1.241.1.2.2.1,PTPBASE-MIB::ptpbaseClockParentDSEntry,,not-accessible,ptpbaseClockParentDSDomainIndex:ptpbaseClockParentDSClockTypeIndex:ptpbaseClockParentDSInstanceIndex,current,,A table entry that contains information about a single PTP clock parentDS for a domain.
.1.3.6.1.2.1.241.1.2.2.1.1,PTPBASE-MIB::ptpbaseClockParentDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.2.1.2,PTPBASE-MIB::ptpbaseClockParentDSClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.2.1.3,PTPBASE-MIB::ptpbaseClockParentDSInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.2.1.4,PTPBASE-MIB::ptpbaseClockParentDSParentPortIdentity,OCTET,read-only,,current,,This object specifies the value of portIdentity of the port on the master that issues the Sync messages used in synchronizing this clock.
.1.3.6.1.2.1.241.1.2.2.1.5,PTPBASE-MIB::ptpbaseClockParentDSParentStats,INTEGER,read-only,,current,true(1):false(2),This object specifies the parentDS ParentStats value. This value indicates whether the values of ParentDSOffset and ParentDSClockPhChRate have been measured and are valid. A TRUE value shall indicate valid data.
.1.3.6.1.2.1.241.1.2.2.1.6,PTPBASE-MIB::ptpbaseClockParentDSOffset,Integer32,read-only,,current,,This object specifies the parentDS ParentOffsetScaledLogVariance value. This value is the variance of the parent clock's phase as measured by the local clock.
.1.3.6.1.2.1.241.1.2.2.1.7,PTPBASE-MIB::ptpbaseClockParentDSClockPhChRate,Integer32,read-only,,current,,This object specifies the clock's parentDS ParentClockPhaseChangeRate value. This value is an estimate of the parent clock's phase change rate as measured by the slave clock.
.1.3.6.1.2.1.241.1.2.2.1.8,PTPBASE-MIB::ptpbaseClockParentDSGMClockIdentity,OCTET,read-only,,current,,This object specifies the parentDS grandmaster clock identity.
.1.3.6.1.2.1.241.1.2.2.1.9,PTPBASE-MIB::ptpbaseClockParentDSGMClockPriority1,Unsigned32,read-only,,current,,This object specifies the parentDS grandmaster clock priority1.
.1.3.6.1.2.1.241.1.2.2.1.10,PTPBASE-MIB::ptpbaseClockParentDSGMClockPriority2,Unsigned32,read-only,,current,,This object specifies the parentDS grandmaster clock priority2.
.1.3.6.1.2.1.241.1.2.2.1.11,PTPBASE-MIB::ptpbaseClockParentDSGMClockQualityClass,INTEGER,read-only,,current,clockclass6(6):clockclass7(7):clockclass13(13):clockclass14(14):clockclass52(52):clockclass58(58),This object specifies the parentDS grandmaster clock quality class.
.1.3.6.1.2.1.241.1.2.2.1.12,PTPBASE-MIB::ptpbaseClockParentDSGMClockQualityAccuracy,INTEGER,read-only,,current,nanoSecond25(32):nanoSecond100(33):nanoSecond250(34):microSec1(35):microSec2dot5(36):microSec10(37):microSec25(38):microSec100(39):microSec250(40):milliSec1(41):milliSec2dot5(42):milliSec10(43):milliSec25(44):milliSec100(45):milliSec250(46):second1(47):second10(48):secondGreater10(49):unknown(254),This object specifies the parentDS grandmaster clock quality accuracy.
.1.3.6.1.2.1.241.1.2.2.1.13,PTPBASE-MIB::ptpbaseClockParentDSGMClockQualityOffset,Unsigned32,read-only,,current,,This object specifies the parentDS grandmaster clock quality offset.
.1.3.6.1.2.1.241.1.2.3,PTPBASE-MIB::ptpbaseClockDefaultDSTable,,not-accessible,,current,,Table of information about the PTP clock defaultDS for all domains.
.1.3.6.1.2.1.241.1.2.3.1,PTPBASE-MIB::ptpbaseClockDefaultDSEntry,,not-accessible,ptpbaseClockDefaultDSDomainIndex:ptpbaseClockDefaultDSClockTypeIndex:ptpbaseClockDefaultDSInstanceIndex,current,,A table entry that contains information about a single PTP clock defaultDS for a domain.
.1.3.6.1.2.1.241.1.2.3.1.1,PTPBASE-MIB::ptpbaseClockDefaultDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.3.1.2,PTPBASE-MIB::ptpbaseClockDefaultDSClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.3.1.3,PTPBASE-MIB::ptpbaseClockDefaultDSInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.3.1.4,PTPBASE-MIB::ptpbaseClockDefaultDSTwoStepFlag,INTEGER,read-only,,current,true(1):false(2),This object specifies whether the two-step process is used.
.1.3.6.1.2.1.241.1.2.3.1.5,PTPBASE-MIB::ptpbaseClockDefaultDSClockIdentity,OCTET,read-only,,current,,This object specifies the defaultDS clockIdentity member.
.1.3.6.1.2.1.241.1.2.3.1.6,PTPBASE-MIB::ptpbaseClockDefaultDSPriority1,Unsigned32,read-only,,current,,This object specifies the defaultDS priority1 member.
.1.3.6.1.2.1.241.1.2.3.1.7,PTPBASE-MIB::ptpbaseClockDefaultDSPriority2,Unsigned32,read-only,,current,,This object specifies the defaultDS priority2 member.
.1.3.6.1.2.1.241.1.2.3.1.8,PTPBASE-MIB::ptpbaseClockDefaultDSSlaveOnly,INTEGER,read-only,,current,true(1):false(2),This object specifies whether the SlaveOnly flag is set.
.1.3.6.1.2.1.241.1.2.3.1.9,PTPBASE-MIB::ptpbaseClockDefaultDSQualityClass,INTEGER,read-only,,current,clockclass6(6):clockclass7(7):clockclass13(13):clockclass14(14):clockclass52(52):clockclass58(58),This object specifies the defaultDS Quality Class.
.1.3.6.1.2.1.241.1.2.3.1.10,PTPBASE-MIB::ptpbaseClockDefaultDSQualityAccuracy,INTEGER,read-only,,current,nanoSecond25(32):nanoSecond100(33):nanoSecond250(34):microSec1(35):microSec2dot5(36):microSec10(37):microSec25(38):microSec100(39):microSec250(40):milliSec1(41):milliSec2dot5(42):milliSec10(43):milliSec25(44):milliSec100(45):milliSec250(46):second1(47):second10(48):secondGreater10(49):unknown(254),This object specifies the defaultDS Quality Accuracy.
.1.3.6.1.2.1.241.1.2.3.1.11,PTPBASE-MIB::ptpbaseClockDefaultDSQualityOffset,Integer32,read-only,,current,,This object specifies the defaultDS Quality offset.
.1.3.6.1.2.1.241.1.2.4,PTPBASE-MIB::ptpbaseClockRunningTable,,not-accessible,,current,,Table of information about the PTP clock running datasets for all domains.
.1.3.6.1.2.1.241.1.2.4.1,PTPBASE-MIB::ptpbaseClockRunningEntry,,not-accessible,ptpbaseClockRunningDomainIndex:ptpbaseClockRunningClockTypeIndex:ptpbaseClockRunningInstanceIndex,current,,A table entry that contains information about a single PTP clock running dataset for a domain.
.1.3.6.1.2.1.241.1.2.4.1.1,PTPBASE-MIB::ptpbaseClockRunningDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.4.1.2,PTPBASE-MIB::ptpbaseClockRunningClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.4.1.3,PTPBASE-MIB::ptpbaseClockRunningInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.4.1.4,PTPBASE-MIB::ptpbaseClockRunningState,INTEGER,read-only,,current,freerun(1):holdover(2):acquiring(3):frequencyLocked(4):phaseAligned(5),This object specifies the clock state returned by a PTP engine.
.1.3.6.1.2.1.241.1.2.4.1.5,PTPBASE-MIB::ptpbaseClockRunningPacketsSent,Counter64,read-only,,current,,This object specifies the total number of all unicast and multicast packets that have been sent out for this clock in this domain for this type. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.4.1.6,PTPBASE-MIB::ptpbaseClockRunningPacketsReceived,Counter64,read-only,,current,,This object specifies the total number of all unicast and multicast packets that have been received for this clock in this domain for this type. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.5,PTPBASE-MIB::ptpbaseClockTimePropertiesDSTable,,not-accessible,,current,,Table of information about the PTP clock timePropertiesDS for all domains.
.1.3.6.1.2.1.241.1.2.5.1,PTPBASE-MIB::ptpbaseClockTimePropertiesDSEntry,,not-accessible,ptpbaseClockTimePropertiesDSDomainIndex:ptpbaseClockTimePropertiesDSClockTypeIndex:ptpbaseClockTimePropertiesDSInstanceIndex,current,,A table entry that contains information about a single PTP clock timePropertiesDS for a domain.
.1.3.6.1.2.1.241.1.2.5.1.1,PTPBASE-MIB::ptpbaseClockTimePropertiesDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.5.1.2,PTPBASE-MIB::ptpbaseClockTimePropertiesDSClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.5.1.3,PTPBASE-MIB::ptpbaseClockTimePropertiesDSInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.5.1.4,PTPBASE-MIB::ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid,INTEGER,read-only,,current,true(1):false(2),This object specifies the timePropertiesDS value of whether the current UTC offset is valid.
.1.3.6.1.2.1.241.1.2.5.1.5,PTPBASE-MIB::ptpbaseClockTimePropertiesDSCurrentUTCOffset,Integer32,read-only,,current,,This object specifies the timePropertiesDS value of the current UTC offset. In PTP systems whose epoch is the PTP epoch, the value of timePropertiesDS.currentUtcOffset is the offset between TAI and UTC; otherwise, the value has no meaning. The value shall be in units of seconds.
.1.3.6.1.2.1.241.1.2.5.1.6,PTPBASE-MIB::ptpbaseClockTimePropertiesDSLeap59,INTEGER,read-only,,current,true(1):false(2),This object specifies the Leap59 value in the clock currentDS.
.1.3.6.1.2.1.241.1.2.5.1.7,PTPBASE-MIB::ptpbaseClockTimePropertiesDSLeap61,INTEGER,read-only,,current,true(1):false(2),This object specifies the Leap61 value in the clock currentDS.
.1.3.6.1.2.1.241.1.2.5.1.8,PTPBASE-MIB::ptpbaseClockTimePropertiesDSTimeTraceable,INTEGER,read-only,,current,true(1):false(2),This object specifies the Time Traceable value in the clock currentDS.
.1.3.6.1.2.1.241.1.2.5.1.9,PTPBASE-MIB::ptpbaseClockTimePropertiesDSFreqTraceable,INTEGER,read-only,,current,true(1):false(2),This object specifies the Frequency Traceable value in the clock currentDS.
.1.3.6.1.2.1.241.1.2.5.1.10,PTPBASE-MIB::ptpbaseClockTimePropertiesDSPTPTimescale,INTEGER,read-only,,current,true(1):false(2),This object specifies the PTP Timescale value in the clock currentDS.
.1.3.6.1.2.1.241.1.2.5.1.11,PTPBASE-MIB::ptpbaseClockTimePropertiesDSSource,INTEGER,read-only,,current,atomicClock(16):gps(32):terrestrialRadio(48):ptp(64):ntp(80):handSet(96):other(144):internalOscillator(160),This object specifies the Timesource value in the clock currentDS.
.1.3.6.1.2.1.241.1.2.6,PTPBASE-MIB::ptpbaseClockTransDefaultDSTable,,not-accessible,,current,,Table of information about the PTP transparentClockDefaultDS for all domains.
.1.3.6.1.2.1.241.1.2.6.1,PTPBASE-MIB::ptpbaseClockTransDefaultDSEntry,,not-accessible,ptpbaseClockTransDefaultDSDomainIndex:ptpbaseClockTransDefaultDSInstanceIndex,current,,A table entry that contains information about a single PTP transparent clock defaultDS for a domain.
.1.3.6.1.2.1.241.1.2.6.1.1,PTPBASE-MIB::ptpbaseClockTransDefaultDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.6.1.2,PTPBASE-MIB::ptpbaseClockTransDefaultDSInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.6.1.3,PTPBASE-MIB::ptpbaseClockTransDefaultDSClockIdentity,OCTET,read-only,,current,,This object specifies the value of the clockIdentity attribute of the local clock.
.1.3.6.1.2.1.241.1.2.6.1.4,PTPBASE-MIB::ptpbaseClockTransDefaultDSNumOfPorts,Counter32,read-only,,current,,This object specifies the number of PTP ports of the device. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.6.1.5,PTPBASE-MIB::ptpbaseClockTransDefaultDSDelay,INTEGER,read-only,,current,e2e(1):p2p(2):disabled(254),This object, if the transparent clock is an end-to-end transparent clock, has the value of e2e; if the transparent clock is a peer-to-peer transparent clock, the value is p2p.
.1.3.6.1.2.1.241.1.2.6.1.6,PTPBASE-MIB::ptpbaseClockTransDefaultDSPrimaryDomain,Unsigned32,read-only,,current,,This object specifies the value of the primary syntonization domain. The initialization value is 0.
.1.3.6.1.2.1.241.1.2.7,PTPBASE-MIB::ptpbaseClockPortTable,,not-accessible,,current,,Table of information about the clock ports for a particular domain.
.1.3.6.1.2.1.241.1.2.7.1,PTPBASE-MIB::ptpbaseClockPortEntry,,not-accessible,ptpbaseClockPortDomainIndex:ptpbaseClockPortClockTypeIndex:ptpbaseClockPortClockInstanceIndex:ptpbaseClockPortTablePortNumberIndex,current,,A table entry that contains information about a single clock port.
.1.3.6.1.2.1.241.1.2.7.1.1,PTPBASE-MIB::ptpbaseClockPortDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.7.1.2,PTPBASE-MIB::ptpbaseClockPortClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.7.1.3,PTPBASE-MIB::ptpbaseClockPortClockInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.7.1.4,PTPBASE-MIB::ptpbaseClockPortTablePortNumberIndex,Unsigned32,not-accessible,,current,,This object specifies the PTP portNumber for this port.
.1.3.6.1.2.1.241.1.2.7.1.5,PTPBASE-MIB::ptpbaseClockPortName,OCTET,read-only,,current,,This object specifies the PTP clock port name configured on the node.
.1.3.6.1.2.1.241.1.2.7.1.6,PTPBASE-MIB::ptpbaseClockPortRole,INTEGER,read-only,,current,master(1):slave(2),This object describes the current role (slave/master) of the port.
.1.3.6.1.2.1.241.1.2.7.1.7,PTPBASE-MIB::ptpbaseClockPortSyncTwoStep,INTEGER,read-only,,current,true(1):false(2),This object specifies that two-step clock operation between the PTP master and slave device is enabled.
.1.3.6.1.2.1.241.1.2.7.1.8,PTPBASE-MIB::ptpbaseClockPortCurrentPeerAddressType,OBJECT,read-only,,current,,This object specifies the current peer's network address type used for PTP communication.
.1.3.6.1.2.1.241.1.2.7.1.9,PTPBASE-MIB::ptpbaseClockPortCurrentPeerAddress,OCTET,read-only,,current,,This object specifies the current peer's network address used for PTP communication.
.1.3.6.1.2.1.241.1.2.7.1.10,PTPBASE-MIB::ptpbaseClockPortNumOfAssociatedPorts,Gauge32,read-only,,current,,This object specifies the following: For a master port - the number of PTP slave sessions (peers) associated with this PTP port. For a slave port - the number of masters available to this slave port (might or might not be peered).
.1.3.6.1.2.1.241.1.2.8,PTPBASE-MIB::ptpbaseClockPortDSTable,,not-accessible,,current,,Table of information about the clock's portDS for a particular domain.
.1.3.6.1.2.1.241.1.2.8.1,PTPBASE-MIB::ptpbaseClockPortDSEntry,,not-accessible,ptpbaseClockPortDSDomainIndex:ptpbaseClockPortDSClockTypeIndex:ptpbaseClockPortDSClockInstanceIndex:ptpbaseClockPortDSPortNumberIndex,current,,A table entry that contains portDS information for a single clock port.
.1.3.6.1.2.1.241.1.2.8.1.1,PTPBASE-MIB::ptpbaseClockPortDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.8.1.2,PTPBASE-MIB::ptpbaseClockPortDSClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.8.1.3,PTPBASE-MIB::ptpbaseClockPortDSClockInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.8.1.4,PTPBASE-MIB::ptpbaseClockPortDSPortNumberIndex,Unsigned32,not-accessible,,current,,This object specifies the PTP portNumber associated with this PTP port.
.1.3.6.1.2.1.241.1.2.8.1.5,PTPBASE-MIB::ptpbaseClockPortDSName,OCTET,read-only,,current,,This object specifies the PTP clock portDS name.
.1.3.6.1.2.1.241.1.2.8.1.6,PTPBASE-MIB::ptpbaseClockPortDSPortIdentity,OCTET,read-only,,current,,This object specifies the PTP clock port Identity.
.1.3.6.1.2.1.241.1.2.8.1.7,PTPBASE-MIB::ptpbaseClockPortDSlogAnnouncementInterval,Integer32,read-only,,current,,This object specifies the Announce message transmission interval associated with this clock port.
.1.3.6.1.2.1.241.1.2.8.1.8,PTPBASE-MIB::ptpbaseClockPortDSAnnounceRctTimeout,Integer32,read-only,,current,,This object specifies the Announce receipt timeout associated with this clock port.
.1.3.6.1.2.1.241.1.2.8.1.9,PTPBASE-MIB::ptpbaseClockPortDSlogSyncInterval,Integer32,read-only,,current,,This object specifies the Sync message transmission interval.
.1.3.6.1.2.1.241.1.2.8.1.10,PTPBASE-MIB::ptpbaseClockPortDSMinDelayReqInterval,Integer32,read-only,,current,,This object specifies the Delay_Req message transmission interval.
.1.3.6.1.2.1.241.1.2.8.1.11,PTPBASE-MIB::ptpbaseClockPortDSPeerDelayReqInterval,Integer32,read-only,,current,,This object specifies the Pdelay_Req message transmission interval.
.1.3.6.1.2.1.241.1.2.8.1.12,PTPBASE-MIB::ptpbaseClockPortDSDelayMech,INTEGER,read-only,,current,e2e(1):p2p(2):disabled(254),This object specifies the delay mechanism used. If the clock is an end-to-end clock, the value is e2e; if the clock is a peer to-peer clock, the value is p2p.
.1.3.6.1.2.1.241.1.2.8.1.13,PTPBASE-MIB::ptpbaseClockPortDSPeerMeanPathDelay,OCTET,read-only,,current,,This object specifies the peer meanPathDelay.
.1.3.6.1.2.1.241.1.2.8.1.14,PTPBASE-MIB::ptpbaseClockPortDSGrantDuration,Unsigned32,read-only,,current,,This object specifies the grant duration allocated by the master.
.1.3.6.1.2.1.241.1.2.8.1.15,PTPBASE-MIB::ptpbaseClockPortDSPTPVersion,Unsigned32,read-only,,current,,This object specifies the PTP version being used.
.1.3.6.1.2.1.241.1.2.9,PTPBASE-MIB::ptpbaseClockPortRunningTable,,not-accessible,,current,,Table of information about the clock ports running datasets for a particular domain.
.1.3.6.1.2.1.241.1.2.9.1,PTPBASE-MIB::ptpbaseClockPortRunningEntry,,not-accessible,ptpbaseClockPortRunningDomainIndex:ptpbaseClockPortRunningClockTypeIndex:ptpbaseClockPortRunningClockInstanceIndex:ptpbaseClockPortRunningPortNumberIndex,current,,A table entry that contains running dataset information about a single clock port.
.1.3.6.1.2.1.241.1.2.9.1.1,PTPBASE-MIB::ptpbaseClockPortRunningDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.9.1.2,PTPBASE-MIB::ptpbaseClockPortRunningClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the clock type as defined in the textual convention description.
.1.3.6.1.2.1.241.1.2.9.1.3,PTPBASE-MIB::ptpbaseClockPortRunningClockInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.9.1.4,PTPBASE-MIB::ptpbaseClockPortRunningPortNumberIndex,Unsigned32,not-accessible,,current,,This object specifies the PTP portNumber associated with this clock port.
.1.3.6.1.2.1.241.1.2.9.1.5,PTPBASE-MIB::ptpbaseClockPortRunningName,OCTET,read-only,,current,,This object specifies the PTP clock port name.
.1.3.6.1.2.1.241.1.2.9.1.6,PTPBASE-MIB::ptpbaseClockPortRunningState,INTEGER,read-only,,current,initializing(1):faulty(2):disabled(3):listening(4):preMaster(5):master(6):passive(7):uncalibrated(8):slave(9),This object specifies the port state returned by PTP engine: initializing faulty disabled listening preMaster master passive uncalibrated slave 
.1.3.6.1.2.1.241.1.2.9.1.7,PTPBASE-MIB::ptpbaseClockPortRunningRole,INTEGER,read-only,,current,master(1):slave(2),This object specifies the Clock Role.
.1.3.6.1.2.1.241.1.2.9.1.8,PTPBASE-MIB::ptpbaseClockPortRunningInterfaceIndex,Integer32,read-only,,current,,This object specifies the interface on the node being used by the PTP clock for PTP communication.
.1.3.6.1.2.1.241.1.2.9.1.9,PTPBASE-MIB::ptpbaseClockPortRunningTransport,OBJECT,read-only,,current,,This object specifies the transport protocol being used for PTP communication (the mapping used).
.1.3.6.1.2.1.241.1.2.9.1.10,PTPBASE-MIB::ptpbaseClockPortRunningEncapsulationType,OBJECT,read-only,,current,,This object specifies the type of encapsulation if the interface is adding extra layers (e.g., VLAN or Pseudowire encapsulation) for the PTP messages.
.1.3.6.1.2.1.241.1.2.9.1.11,PTPBASE-MIB::ptpbaseClockPortRunningTxMode,INTEGER,read-only,,current,unicast(1):multicast(2):multicastmix(3),This object specifies the clock transmission mode as: unicast: Using unicast communication channel multicast: Using multicast communication channel multicast-mix: Using multicast-unicast communication channel
.1.3.6.1.2.1.241.1.2.9.1.12,PTPBASE-MIB::ptpbaseClockPortRunningRxMode,INTEGER,read-only,,current,unicast(1):multicast(2):multicastmix(3),This object specifies the clock receive mode as: unicast: Using unicast communication channel multicast: Using multicast communication channel multicast-mix: Using multicast-unicast communication channel
.1.3.6.1.2.1.241.1.2.9.1.13,PTPBASE-MIB::ptpbaseClockPortRunningPacketsReceived,Counter64,read-only,,current,,This object specifies the packets received on the clock port (cumulative). These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.9.1.14,PTPBASE-MIB::ptpbaseClockPortRunningPacketsSent,Counter64,read-only,,current,,This object specifies the packets sent on the clock port (cumulative). These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.10,PTPBASE-MIB::ptpbaseClockPortTransDSTable,,not-accessible,,current,,Table of information about the transparentClockPortDS for a particular domain.
.1.3.6.1.2.1.241.1.2.10.1,PTPBASE-MIB::ptpbaseClockPortTransDSEntry,,not-accessible,ptpbaseClockPortTransDSDomainIndex:ptpbaseClockPortTransDSInstanceIndex:ptpbaseClockPortTransDSPortNumberIndex,current,,A table entry that contains clock port transparent dataset information about a single clock port.
.1.3.6.1.2.1.241.1.2.10.1.1,PTPBASE-MIB::ptpbaseClockPortTransDSDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the domain number used to create a logical group of PTP devices.
.1.3.6.1.2.1.241.1.2.10.1.2,PTPBASE-MIB::ptpbaseClockPortTransDSInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.10.1.3,PTPBASE-MIB::ptpbaseClockPortTransDSPortNumberIndex,Unsigned32,not-accessible,,current,,This object specifies the PTP portNumber associated with this port.
.1.3.6.1.2.1.241.1.2.10.1.4,PTPBASE-MIB::ptpbaseClockPortTransDSPortIdentity,OCTET,read-only,,current,,This object specifies the value of the PortIdentity attribute of the local port.
.1.3.6.1.2.1.241.1.2.10.1.5,PTPBASE-MIB::ptpbaseClockPortTransDSlogMinPdelayReqInt,Integer32,read-only,,current,,This object specifies the value of the logarithm to the base 2 of the minPdelayReqInterval.
.1.3.6.1.2.1.241.1.2.10.1.6,PTPBASE-MIB::ptpbaseClockPortTransDSFaultyFlag,INTEGER,read-only,,current,true(1):false(2),This object specifies the value TRUE if the port is faulty and FALSE if the port is operating normally.
.1.3.6.1.2.1.241.1.2.10.1.7,PTPBASE-MIB::ptpbaseClockPortTransDSPeerMeanPathDelay,OCTET,read-only,,current,,This object specifies, if the delayMechanism used is p2p, the value of the estimate of the current one-way propagation delay, i.e., <meanPathDelay> on the link attached to this port, computed using the peer delay mechanism. If the value of the delayMechanism used is e2e, then the value will be zero.
.1.3.6.1.2.1.241.1.2.11,PTPBASE-MIB::ptpbaseClockPortAssociateTable,,not-accessible,,current,,Table of information about a given port's associated ports. For a master port: multiple slave ports that have established sessions with the current master port. For a slave port: the list of masters available for a given slave port. Session information (packets, errors) to be displayed based on availability and scenario.
.1.3.6.1.2.1.241.1.2.11.1,PTPBASE-MIB::ptpbaseClockPortAssociateEntry,,not-accessible,ptpClockPortCurrentDomainIndex:ptpClockPortCurrentClockTypeIndex:ptpClockPortCurrentClockInstanceIndex:ptpClockPortCurrentPortNumberIndex:ptpbaseClockPortAssociatePortIndex,current,,A table entry that contains information about a single associated port for the given clock port.
.1.3.6.1.2.1.241.1.2.11.1.1,PTPBASE-MIB::ptpClockPortCurrentDomainIndex,Unsigned32,not-accessible,,current,,This object specifies the given port's domain number.
.1.3.6.1.2.1.241.1.2.11.1.2,PTPBASE-MIB::ptpClockPortCurrentClockTypeIndex,INTEGER,not-accessible,,current,ordinaryClock(1):boundaryClock(2):transparentClock(3):boundaryNode(4),This object specifies the given port's clock type.
.1.3.6.1.2.1.241.1.2.11.1.3,PTPBASE-MIB::ptpClockPortCurrentClockInstanceIndex,Unsigned32,not-accessible,,current,,This object specifies the instance of the clock for this clock type in the given domain.
.1.3.6.1.2.1.241.1.2.11.1.4,PTPBASE-MIB::ptpClockPortCurrentPortNumberIndex,Unsigned32,not-accessible,,current,,This object specifies the PTP portNumber for the given port.
.1.3.6.1.2.1.241.1.2.11.1.5,PTPBASE-MIB::ptpbaseClockPortAssociatePortIndex,Unsigned32,not-accessible,,current,,This object specifies the associated port's serial number in the current port's context.
.1.3.6.1.2.1.241.1.2.11.1.6,PTPBASE-MIB::ptpbaseClockPortAssociateAddressType,OBJECT,read-only,,current,,This object specifies the peer port's network address type used for PTP communication. The OCTET STRING representation of the OID of ptpbaseWellKnownTransportTypes will be used in the values contained in the OCTET STRING.
.1.3.6.1.2.1.241.1.2.11.1.7,PTPBASE-MIB::ptpbaseClockPortAssociateAddress,OCTET,read-only,,current,,This object specifies the peer port's network address used for PTP communication.
.1.3.6.1.2.1.241.1.2.11.1.8,PTPBASE-MIB::ptpbaseClockPortAssociatePacketsSent,Counter64,read-only,,current,,The number of packets sent to this peer port from the current port. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.11.1.9,PTPBASE-MIB::ptpbaseClockPortAssociatePacketsReceived,Counter64,read-only,,current,,The number of packets received from this peer port by the current port. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.11.1.10,PTPBASE-MIB::ptpbaseClockPortAssociateInErrors,Counter64,read-only,,current,,This object specifies the input errors associated with the peer port. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.11.1.11,PTPBASE-MIB::ptpbaseClockPortAssociateOutErrors,Counter64,read-only,,current,,This object specifies the output errors associated with the peer port. These counters are discontinuous.
.1.3.6.1.2.1.241.1.2.12,PTPBASE-MIB::ptpbaseWellKnownTransportTypes,,,,,,
.1.3.6.1.2.1.241.1.2.12.1,PTPBASE-MIB::ptpbaseTransportTypeIPversion4,,,,,,IP version 4
.1.3.6.1.2.1.241.1.2.12.2,PTPBASE-MIB::ptpbaseTransportTypeIPversion6,,,,,,IP version 6
.1.3.6.1.2.1.241.1.2.12.3,PTPBASE-MIB::ptpbaseTransportTypeEthernet,,,,,,Ethernet
.1.3.6.1.2.1.241.1.2.12.4,PTPBASE-MIB::ptpbaseTransportTypeDeviceNET,,,,,,Device NET
.1.3.6.1.2.1.241.1.2.12.5,PTPBASE-MIB::ptpbaseTransportTypeControlNET,,,,,,Control NET
.1.3.6.1.2.1.241.1.2.12.6,PTPBASE-MIB::ptpbaseTransportTypeIEC61158,,,,,,IEC61158
.1.3.6.1.2.1.241.1.2.13,PTPBASE-MIB::ptpbaseWellKnownEncapsulationTypes,,,,,,
.1.3.6.1.2.1.241.1.2.13.1,PTPBASE-MIB::ptpbaseEncapsulationTypeEthernet,,,,,,Ethernet Encapsulation type.
.1.3.6.1.2.1.241.1.2.13.2,PTPBASE-MIB::ptpbaseEncapsulationTypeVLAN,,,,,,VLAN Encapsulation type.
.1.3.6.1.2.1.241.1.2.13.3,PTPBASE-MIB::ptpbaseEncapsulationTypeUDPIPLSP,,,,,,UDP/IP over MPLS Encapsulation type.
.1.3.6.1.2.1.241.1.2.13.4,PTPBASE-MIB::ptpbaseEncapsulationTypePWUDPIPLSP,,,,,,UDP/IP Pseudowire over MPLS Encapsulation type.
.1.3.6.1.2.1.241.1.2.13.5,PTPBASE-MIB::ptpbaseEncapsulationTypePWEthernetLSP,,,,,,Ethernet Pseudowire over MPLS Encapsulation type.
.1.3.6.1.2.1.241.2,PTPBASE-MIB::ptpbaseMIBConformance,,,,,,
.1.3.6.1.2.1.241.2.1,PTPBASE-MIB::ptpbaseMIBCompliances,,,,,,
.1.3.6.1.2.1.241.2.1.1,PTPBASE-MIB::ptpbaseMIBCompliancesSystemInfo,,,,,,Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide system-level information of clock devices. Such devices can only be monitored using this MIB module. The module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.241.2.1.2,PTPBASE-MIB::ptpbaseMIBCompliancesClockInfo,,,,,,Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide clock-related information. Such devices can only be monitored using this MIB module. The module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.241.2.1.3,PTPBASE-MIB::ptpbaseMIBCompliancesClockPortInfo,,,,,,Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide clock-port-related information. Such devices can only be monitored using this MIB module. The module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.241.2.1.4,PTPBASE-MIB::ptpbaseMIBCompliancesTransparentClockInfo,,,,,,Compliance statement for agents that provide read-only support for PTPBASE-MIB to provide transparent-clock-related information. Such devices can only be monitored using this MIB module. The module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.
.1.3.6.1.2.1.241.2.2,PTPBASE-MIB::ptpbaseMIBGroups,,,,,,
.1.3.6.1.2.1.241.2.2.1,PTPBASE-MIB::ptpbaseMIBSystemInfoGroup,,,,,,Group that aggregates objects describing system-wide information
.1.3.6.1.2.1.241.2.2.2,PTPBASE-MIB::ptpbaseMIBClockCurrentDSGroup,,,,,,Group that aggregates objects describing PTP currentDS information
.1.3.6.1.2.1.241.2.2.3,PTPBASE-MIB::ptpbaseMIBClockParentDSGroup,,,,,,Group that aggregates objects describing PTP parentDS information
.1.3.6.1.2.1.241.2.2.4,PTPBASE-MIB::ptpbaseMIBClockDefaultDSGroup,,,,,,Group that aggregates objects describing PTP defaultDS information
.1.3.6.1.2.1.241.2.2.5,PTPBASE-MIB::ptpbaseMIBClockRunningGroup,,,,,,Group that aggregates objects describing PTP running state information
.1.3.6.1.2.1.241.2.2.6,PTPBASE-MIB::ptpbaseMIBClockTimepropertiesGroup,,,,,,Group that aggregates objects describing PTP Time Properties information
.1.3.6.1.2.1.241.2.2.7,PTPBASE-MIB::ptpbaseMIBClockTranparentDSGroup,,,,,,Group that aggregates objects describing PTP transparentClockDefaultDS information
.1.3.6.1.2.1.241.2.2.8,PTPBASE-MIB::ptpbaseMIBClockPortGroup,,,,,,Group that aggregates objects describing information for a given PTP Port
.1.3.6.1.2.1.241.2.2.9,PTPBASE-MIB::ptpbaseMIBClockPortDSGroup,,,,,,Group that aggregates objects describing PTP portDS information
.1.3.6.1.2.1.241.2.2.10,PTPBASE-MIB::ptpbaseMIBClockPortRunningGroup,,,,,,Group that aggregates objects describing PTP running interface information
.1.3.6.1.2.1.241.2.2.11,PTPBASE-MIB::ptpbaseMIBClockPortTransDSGroup,,,,,,Group that aggregates objects describing PTP transparentClockPortDS information
.1.3.6.1.2.1.241.2.2.12,PTPBASE-MIB::ptpbaseMIBClockPortAssociateGroup,,,,,,Group that aggregates objects describing information on peer PTP ports for a given PTP clock port
.1.3.6.1.2.1.242,MAP-E-MIB::mapMIB,,,,,,This MIB module is defined for management of objects for MAP-E BRs or CEs. Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info).
.1.3.6.1.2.1.242.1,MAP-E-MIB::mapMIBObjects,,,,,,
.1.3.6.1.2.1.242.1.1,MAP-E-MIB::mapRule,,,,,,
.1.3.6.1.2.1.242.1.1.1,MAP-E-MIB::mapRuleTable,,not-accessible,,current,,The (conceptual) table containing rule information for a specific mapping rule. It can also be used for row creation.
.1.3.6.1.2.1.242.1.1.1.1,MAP-E-MIB::mapRuleEntry,,not-accessible,ifIndex:mapRuleID,current,,Each entry in this table contains the information on a particular mapping rule.
.1.3.6.1.2.1.242.1.1.1.1.1,MAP-E-MIB::mapRuleID,Unsigned32,not-accessible,,current,,A unique identifier used to distinguish mapping rules.
.1.3.6.1.2.1.242.1.1.1.1.2,MAP-E-MIB::mapRuleIPv6Prefix,OCTET,read-only,,current,,The IPv6 prefix defined in the mapping rule that will be assigned to CEs.
.1.3.6.1.2.1.242.1.1.1.1.3,MAP-E-MIB::mapRuleIPv6PrefixLen,Unsigned32,read-only,,current,,The length of the IPv6 prefix defined in the mapping rule that will be assigned to CEs.
.1.3.6.1.2.1.242.1.1.1.1.4,MAP-E-MIB::mapRuleIPv4Prefix,OCTET,read-only,,current,,The IPv4 prefix defined in the mapping rule that will be assigned to CEs.
.1.3.6.1.2.1.242.1.1.1.1.5,MAP-E-MIB::mapRuleIPv4PrefixLen,Unsigned32,read-only,,current,,The length of the IPv4 prefix defined in the mapping rule that will be assigned to CEs.
.1.3.6.1.2.1.242.1.1.1.1.6,MAP-E-MIB::mapRuleBRIPv6Address,OCTET,read-only,,current,,The IPv6 address of the BR that will be conveyed to CEs. If the BR IPv6 address is anycast, the relay must use this anycast IPv6 address as the source address in packets relayed to CEs.
.1.3.6.1.2.1.242.1.1.1.1.7,MAP-E-MIB::mapRulePSID,OCTET,read-only,,current,,The PSID value algorithmically identifies a set of ports assigned to a CE.
.1.3.6.1.2.1.242.1.1.1.1.8,MAP-E-MIB::mapRulePSIDLen,Unsigned32,read-only,,current,,The bit length value of the number of significant bits in the PSID field. When it is set to 0, the PSID field is to be ignored.
.1.3.6.1.2.1.242.1.1.1.1.9,MAP-E-MIB::mapRuleOffset,Unsigned32,read-only,,current,,The number of the mapRuleOffset is 6 by default to exclude the system ports (0-1023). It is provided via the Rule Port Mapping Parameters in the Basic Mapping Rule.
.1.3.6.1.2.1.242.1.1.1.1.10,MAP-E-MIB::mapRuleEALen,Unsigned32,read-only,,current,,The length of the Embedded Address (EA) defined in mapping rule that will be assigned to CEs.
.1.3.6.1.2.1.242.1.1.1.1.11,MAP-E-MIB::mapRuleType,INTEGER,read-only,,current,bmr(1):fmr(2):bmrAndfmr(3),Indicates the type of mapping rule. '1' represents a BMR. '2' represents an FMR. '3' represents a BMR that is also an FMR for mesh mode.
.1.3.6.1.2.1.242.1.2,MAP-E-MIB::mapSecurityCheck,,,,,,
.1.3.6.1.2.1.242.1.2.1,MAP-E-MIB::mapSecurityCheckTable,,not-accessible,,current,,The (conceptual) table containing information on MAP security checks. This table can be used for statistics on the number of invalid packets that have been identified.
.1.3.6.1.2.1.242.1.2.1.1,MAP-E-MIB::mapSecurityCheckEntry,,not-accessible,ifIndex,current,,Each entry in this table contains information on a particular MAP security check.
.1.3.6.1.2.1.242.1.2.1.1.1,MAP-E-MIB::mapSecurityCheckInvalidv4,Counter64,read-only,,current,,Indicates the number of received IPv4 packets that do not have a payload source IPv4 address or port within the range defined in the matching MAP rule. It corresponds to the second kind of invalid packet described in Section 4.1.2.
.1.3.6.1.2.1.242.1.2.1.1.2,MAP-E-MIB::mapSecurityCheckInvalidv6,Counter64,read-only,,current,,Indicates the number of received IPv6 packets that do not have a source or destination IPv6 address matching a Basic Mapping Rule. It corresponds to the first kind of invalid packet described in Section 4.1.2.
.1.3.6.1.2.1.242.2,MAP-E-MIB::mapMIBConformance,,,,,,
.1.3.6.1.2.1.242.2.1,MAP-E-MIB::mapMIBCompliances,,,,,,
.1.3.6.1.2.1.242.2.1.1,MAP-E-MIB::mapMIBCompliance,,,,,,Describes the minimal requirements for conformance to the MAP-E MIB.
.1.3.6.1.2.1.242.2.2,MAP-E-MIB::mapMIBGroups,,,,,,
.1.3.6.1.2.1.242.2.2.1,MAP-E-MIB::mapMIBRuleGroup,,,,,,The group of objects used to describe the MAP-E mapping rule.
.1.3.6.1.2.1.242.2.2.2,MAP-E-MIB::mapMIBSecurityGroup,,,,,,The group of objects used to provide information on the MAP-E security checks.
.1.3.6.1.2.1.243,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMIB,,,,,,This MIB module contains managed object definitions to configure and/or monitor Multicast communication over IP Virtual Private Networks (VPNs) supported by the Multiprotocol Label Switching/Border Gateway Protocol (MPLS/BGP) on a Provider Edge (PE) router. Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). 
.1.3.6.1.2.1.243.0,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnNotifications,,,,,,
.1.3.6.1.2.1.243.0.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMvrfActionTaken,,,,,,mvpnMvrfActionTaken notifies about a change in an MVRF on the PE. The change itself will be given by mvpnGenMvrfLastAction. 
.1.3.6.1.2.1.243.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnObjects,,,,,,
.1.3.6.1.2.1.243.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnScalars,,,,,,
.1.3.6.1.2.1.243.1.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMvrfs,Gauge32,read-only,,current,,The total number of Multicast Virtual Routing and Forwarding (MVRF) tables that are present on this Provider Edge (PE) router. This includes MVRFs for IPv4, IPv6, and Multipoint LDP (mLDP) C-multicast. 
.1.3.6.1.2.1.243.1.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnV4Mvrfs,Gauge32,read-only,,current,,The number of MVRFs for IPv4 C-multicast on this PE. 
.1.3.6.1.2.1.243.1.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnV6Mvrfs,Gauge32,read-only,,current,,The number of MVRFs for IPv6 C-multicast on this PE. 
.1.3.6.1.2.1.243.1.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMldpMvrfs,Gauge32,read-only,,current,,The number of MVRFs on this PE that use BGP for exchanging mLDP C-multicast routing information. 
.1.3.6.1.2.1.243.1.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPimV4Mvrfs,Gauge32,read-only,,current,,The number of MVRFs on this PE that use Provider Independent Multicast (PIM) for exchanging IPv4 C-multicast routing information. 
.1.3.6.1.2.1.243.1.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPimV6Mvrfs,Gauge32,read-only,,current,,The number of MVRFs on this PE that use PIM for exchanging IPv6 C-multicast routing information. 
.1.3.6.1.2.1.243.1.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpV4Mvrfs,Gauge32,read-only,,current,,The number of MVRFs on this PE that use BGP for exchanging IPv4 C-multicast routing information. 
.1.3.6.1.2.1.243.1.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpV6Mvrfs,Gauge32,read-only,,current,,The number of MVRFs on this PE that use BGP for exchanging IPv6 C-multicast routing information. 
.1.3.6.1.2.1.243.1.1.9,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSPTunnelLimit,Unsigned32,read-write,,current,,The maximum number of selective provider tunnels that are allowed for a particular MVPN on this PE. 
.1.3.6.1.2.1.243.1.1.10,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpCmcastRouteWithdrawalTimer,Unsigned32,read-write,,current,,A configurable timer to control the delay of C-multicast route withdrawal advertisements. 
.1.3.6.1.2.1.243.1.1.11,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpSrcSharedTreeJoinTimer,Unsigned32,read-write,,current,,A configurable timer to control the delay of Source/Shared Tree Join C-multicast route advertisements. 
.1.3.6.1.2.1.243.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenericTable,,not-accessible,,current,,A conceptual table containing generic information about MVPNs on this PE. 
.1.3.6.1.2.1.243.1.2.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenericEntry,,not-accessible,mplsL3VpnVrfName,current,,A conceptual row that represents an MVPN on this PE. The MVPN represented by this entry will have one or more corresponding P-Multicast Service Interfaces (PMSIs) and a corresponding VRF in MPLS-L3VPN-STD-MIB (RFC 4382). 
.1.3.6.1.2.1.243.1.2.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenMvrfLastAction,INTEGER,read-only,,current,createdMvrf(1):deletedMvrf(2):modifiedMvrfIpmsiConfig(3):modifiedMvrfSpmsiConfig(4),This object describes the last action pertaining to the MVPN represented by this entry. The enumerated action types and the corresponding descriptions are as follows: createdMvrf: MVRF was created for this MVPN on the PE. deletedMvrf: MVRF for this MVPN was deleted from the PE. A conceptual row in this table will never have mvpnGenMvrfLastAction equal to deletedMvrf, because in that case, the row itself will not exist in the table. This value for mvpnGenMvrfLastAction is defined solely for use in the mvpnMvrfActionChange notification. modifiedMvrfIpmsiConfig: An I-PMSI for this MVPN was configured, deleted, or changed. modifiedMvrfSpmsiConfig: An S-PMSI for this MVPN was configured, deleted, or changed. 
.1.3.6.1.2.1.243.1.2.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenMvrfLastActionTime,OCTET,read-only,,current,,The timestamp when the last action, given in the corresponding mvpnGenMvrfLastAction object, was carried out. 
.1.3.6.1.2.1.243.1.2.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenMvrfCreationTime,OCTET,read-only,,current,,The timestamp when the MVRF was created for the MVPN represented by this entry. 
.1.3.6.1.2.1.243.1.2.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenCmcastRouteProtocol,INTEGER,read-only,,current,pim(1):bgp(2),The protocol used to signal C-multicast routing information across the provider core for the MVPN represented by this entry. The enumerated protocols and the corresponding descriptions are as follows: pim : PIM (PIM-MVPN) bgp : BGP (BGP-MVPN) 
.1.3.6.1.2.1.243.1.2.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenIpmsiInfo,OBJECT,read-only,,current,,A pointer to a conceptual row representing the corresponding I-PMSI in mvpnPmsiTable. If there is no I-PMSI for the MVPN represented by this entry, the value of this object will be zeroDotZero. 
.1.3.6.1.2.1.243.1.2.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenInterAsPmsiInfo,OBJECT,read-only,,current,,A pointer to a conceptual row representing the corresponding segmented Inter-AS I-PMSI in mvpnPmsiTable. If there is no segmented Inter-AS I-PMSI for the MVPN, the value of this object will be zeroDotZero. 
.1.3.6.1.2.1.243.1.2.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenUmhSelection,INTEGER,read-only,,current,highestPeAddress(1):cRootGroupHashing(2):ucastUmhRoute(3),The Upstream Multicast Hop (UMH) selection method for the MVPN represented by this entry. The enumerated methods and the corresponding descriptions are as follows: highestPeAddress : PE with the highest address (see RFC 6513, Section 5.1.3) cRootGroupHashing : hashing based on (c-root, c-group) ucastUmhRoute : per-unicast route towards c-root 
.1.3.6.1.2.1.243.1.2.1.9,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenCustomerSiteType,INTEGER,read-only,,current,senderReceiver(1):receiverOnly(2):senderOnly(3),The type of the customer site, connected to the MVPN represented by this entry. The enumerated types and the corresponding descriptions are as follows: senderReceiver : Site is both sender and receiver receiverOnly : Site is receiver only senderOnly : Site is sender only 
.1.3.6.1.2.1.243.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpTable,,not-accessible,,current,,A conceptual table that supplements mvpnGenericTable with BGP-MVPN-specific information for BGP-MVPNs on this PE. 
.1.3.6.1.2.1.243.1.3.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpEntry,,not-accessible,mplsL3VpnVrfName,current,,A conceptual row corresponding to a BGP-MVPN on this PE. 
.1.3.6.1.2.1.243.1.3.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpMode,INTEGER,read-only,,current,other(0):rptSpt(1):sptOnly(2),The inter-site C-tree mode used by the BGP-MVPN represented by this entry. other : none of the following rptSpt : inter-site shared tree mode (Rendezvous Point Tree (RPT) and source-specific shortest-path tree (SPT)) sptOnly : inter-site source-only tree mode 
.1.3.6.1.2.1.243.1.3.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpVrfRouteImportExtendedCommunity,OCTET,read-only,,current,,The VRF Route Import Extended Community added by this PE to unicast VPN routes that it advertises for the BGP-MVPN corresponding to this entry. 
.1.3.6.1.2.1.243.1.3.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpSrcASExtendedCommunity,Unsigned32,read-only,,current,,The Source AS Extended Community added by this PE to the unicast VPN routes that it advertises for the BGP-MVPN represented by this entry. 
.1.3.6.1.2.1.243.1.3.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpMsgRateLimit,Unsigned32,read-write,,current,,The configurable upper bound for the rate of the BGP C-multicast routing information message exchange between this PE and other PEs in the BGP-MVPN corresponding to this entry. 
.1.3.6.1.2.1.243.1.3.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpMaxSpmsiAdRoutes,Unsigned32,read-write,,current,,The configurable upper bound for the number of S-PMSI auto-discovery (A-D) routes for the BGP-MVPN corresponding to this entry. 
.1.3.6.1.2.1.243.1.3.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpMaxSpmsiAdRouteFreq,Unsigned32,read-write,,current,,The configurable upper bound for the frequency of S-PMSI A-D route generation for the BGP-MVPN corresponding to this entry. 
.1.3.6.1.2.1.243.1.3.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpMaxSrcActiveAdRoutes,Unsigned32,read-write,,current,,The configurable upper bound for the number of Source Active A-D routes for the BGP-MVPN corresponding to this entry. 
.1.3.6.1.2.1.243.1.3.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpMaxSrcActiveAdRouteFreq,Unsigned32,read-write,,current,,The configurable upper bound for the frequency of Source Active A-D route generation for the BGP-MVPN corresponding to this entry. 
.1.3.6.1.2.1.243.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiTable,,not-accessible,,current,,A conceptual table containing information related to PMSIs on this PE. 
.1.3.6.1.2.1.243.1.4.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiEntry,,not-accessible,mvpnPmsiTunnelIfIndex,current,,A conceptual row corresponding to a PMSI on this PE. 
.1.3.6.1.2.1.243.1.4.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiTunnelIfIndex,Integer32,not-accessible,,current,,A unique value for this conceptual row. Its value will be the same as that of the ifIndex object instance for the corresponding PMSI in ifTable. 
.1.3.6.1.2.1.243.1.4.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiRD,OCTET,read-only,,current,,The Route Distinguisher for this I-PMSI. 
.1.3.6.1.2.1.243.1.4.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiTunnelType,INTEGER,read-only,,current,noTunnelInfo(0):rsvpP2mp(1):ldpP2mp(2):pimSsm(3):pimAsm(4):pimBidir(5):ingressReplication(6):ldpMp2mp(7):transportTunnel(8),The type of tunnel used to instantiate the PMSI corresponding to this entry. 
.1.3.6.1.2.1.243.1.4.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiTunnelAttribute,OBJECT,read-only,,current,,A pointer to a conceptual row representing the P-tunnel used by the PMSI in l2L3VpnMcastPmsiTunnelAttributeTable. 
.1.3.6.1.2.1.243.1.4.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiTunnelPimGroupAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnPmsiTunnelPimGroupAddr object that follows. When the PMSI corresponding to this entry does not use the PIM provider tunnel, i.e., the value of mvpnPmsiTunnelType is not one of pimSsm(3), pimAsm(4), or pimBidir(5), this object should be unknown(0). 
.1.3.6.1.2.1.243.1.4.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiTunnelPimGroupAddr,OCTET,read-only,,current,,The tunnel address that is used by the PMSI corresponding to this entry. When the PMSI corresponding to this entry does not use the PIM provider tunnel, i.e., the value of mvpnPmsiTunnelType is not one of pimSsm(3), pimAsm(4), or pimBidir(5), this object should be a zero-length octet string. 
.1.3.6.1.2.1.243.1.4.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiEncapsulationType,INTEGER,read-only,,current,greIp(1):ipIp(2):mpls(3),The encapsulation type used for sending packets through the PMSI corresponding to this entry. The enumerated encapsulation types and the corresponding descriptions are as follows: greIp : Generic Routing Encapsulation (GRE) (RFC 2784) ipIp : IP-in-IP encapsulation (RFC 2003) mpls : MPLS encapsulation (RFC 3032) 
.1.3.6.1.2.1.243.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiTable,,not-accessible,,current,,A conceptual table containing information related to S-PMSIs on this PE. This table stores only S-PMSI-specific attribute information. Generic PMSI attribute information of S-PMSIs is stored in mvpnPmsiTable. 
.1.3.6.1.2.1.243.1.5.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiEntry,,not-accessible,mplsL3VpnVrfName:mvpnSpmsiCmcastGroupAddrType:mvpnSpmsiCmcastGroupAddr:mvpnSpmsiCmcastGroupPrefixLen:mvpnSpmsiCmcastSourceAddrType:mvpnSpmsiCmcastSourceAddr:mvpnSpmsiCmcastSourcePrefixLen,current,,A conceptual row corresponding to an S-PMSI on this PE. Implementers need to be aware that if the total number of octets in mplsL3VpnVrfName, mvpnSpmsiCmcastGroupAddr, and mvpnSpmsiCmcastSourceAddr exceeds 113, the OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.243.1.5.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiCmcastGroupAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnSpmsiCmcastGroupAddr object that follows. 
.1.3.6.1.2.1.243.1.5.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiCmcastGroupAddr,OCTET,not-accessible,,current,,The group address of the C-flow assigned to the S-PMSI corresponding to this entry. 
.1.3.6.1.2.1.243.1.5.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiCmcastGroupPrefixLen,Unsigned32,not-accessible,,current,,The prefix length of the corresponding mvpnSpmsiCmcastGroupAddr object. 
.1.3.6.1.2.1.243.1.5.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiCmcastSourceAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnSpmsiCmcastSourceAddr object that follows. 
.1.3.6.1.2.1.243.1.5.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiCmcastSourceAddr,OCTET,not-accessible,,current,,The source address of the C-flow assigned to the S-PMSI corresponding to this entry. 
.1.3.6.1.2.1.243.1.5.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiCmcastSourcePrefixLen,Unsigned32,not-accessible,,current,,The prefix length of the corresponding mvpnSpmsiCmcastSourceAddr object. 
.1.3.6.1.2.1.243.1.5.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnSpmsiPmsiPointer,OBJECT,read-only,,current,,A pointer to a conceptual row representing generic information of this S-PMSI in mvpnPmsiTable. 
.1.3.6.1.2.1.243.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtStatsTable,,not-accessible,,current,,A conceptual table containing statistics pertaining to I-PMSI and S-PMSI advertisements sent/received by this PE. 
.1.3.6.1.2.1.243.1.6.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtStatsEntry,,not-accessible,mplsL3VpnVrfName:mvpnAdvtType:mvpnAdvtPeerAddrType:mvpnAdvtPeerAddr,current,,A conceptual row corresponding to statistics pertaining to advertisements sent/received for a particular MVPN on this PE. Implementers need to be aware that if the total number of octets in mplsL3VpnVrfName and mvpnAdvtPeerAddr exceeds 115, then OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.243.1.6.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtType,INTEGER,not-accessible,,current,intraAsIpmsi(0):interAsIpmsi(1):sPmsi(2),The PMSI type. The enumerated PMSI types and corresponding descriptions are as follows: intraAsIpmsi : Intra-AS Inclusive PMSI interAsIpmsi : Inter-AS Inclusive PMSI sPmsi : Selective PMSI 
.1.3.6.1.2.1.243.1.6.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtPeerAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InternetAddressType of the mvpnAdvtPeerAddr object that follows. 
.1.3.6.1.2.1.243.1.6.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtPeerAddr,OCTET,not-accessible,,current,,The address of a peer PE that exchanges advertisement with this PE. 
.1.3.6.1.2.1.243.1.6.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtSent,Counter32,read-only,,current,,The number of advertisements successfully sent to the peer PE specified by the corresponding mvpnAdvtPeerAddr. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnAdvtCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.6.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtReceived,Counter32,read-only,,current,,The number of advertisements received from the peer PE specified by the corresponding mvpnAdvtPeerAddr object. This includes advertisements that were discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnAdvtCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.6.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtReceivedError,Counter32,read-only,,current,,The total number of advertisements received from a peer PE, specified by the corresponding mvpnAdvtPeerAddr object, that were rejected due to an error(s) in the advertisement. The value of this object includes the error cases counted in the corresponding mvpnAdvtReceivedMalformedTunnelType and mvpnAdvtReceivedMalformedTunnelId objects. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnAdvtCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.6.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtReceivedMalformedTunnelType,Counter32,read-only,,current,,The total number of advertisements received from the peer PE, specified by the corresponding mvpnAdvtPeerAddr object, that were rejected due to a malformed Tunnel Type in the PMSI Tunnel attribute. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnAdvtCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.6.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtReceivedMalformedTunnelId,Counter32,read-only,,current,,The total number of advertisements received from the peer PE, specified by the corresponding mvpnAdvtPeerAddr object, that were rejected due to a malformed Tunnel Identifier in the PMSI Tunnel attribute. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnAdvtCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.6.1.9,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtLastSentTime,OCTET,read-only,,current,,The timestamp when the last advertisement was successfully sent by this PE. If no advertisement has been sent since the last re-initialization of this PE, this object will have a zero-length string. 
.1.3.6.1.2.1.243.1.6.1.10,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtLastReceivedTime,OCTET,read-only,,current,,The timestamp when the last advertisement was successfully received from the peer PE specified by the corresponding mvpnAdvtPeerAddr object and processed by this PE. If no advertisement has been received since the last re-initialization of this PE, this object will have a zero-length string. 
.1.3.6.1.2.1.243.1.6.1.11,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this application's counters, viz., counters with the OID prefix 'mvpnAdvtSent', 'mvpnAdvtReceived', 'mvpnAdvtReceivedError', 'mvpnAdvtReceivedMalformedTunnelType', or 'mvpnAdvtReceivedMalformedTunnelId', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, this object will have a zero value. 
.1.3.6.1.2.1.243.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteTable,,not-accessible,,current,,A conceptual table containing multicast routing information corresponding to the MVRFs present on the PE. 
.1.3.6.1.2.1.243.1.7.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteEntry,,not-accessible,mplsL3VpnVrfName:mvpnMrouteCmcastGroupAddrType:mvpnMrouteCmcastGroupAddr:mvpnMrouteCmcastGroupPrefixLength:mvpnMrouteCmcastSourceAddrType:mvpnMrouteCmcastSourceAddrs:mvpnMrouteCmcastSourcePrefixLength,current,,A conceptual row corresponding to a route for IP datagrams from a particular source and addressed to a particular IP multicast group address. Implementers need to be aware that if the total number of octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr, and mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.243.1.7.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCmcastGroupAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteCmcastGroupAddr object that follows. 
.1.3.6.1.2.1.243.1.7.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCmcastGroupAddr,OCTET,not-accessible,,current,,The IP multicast group address that, along with the corresponding mvpnMrouteCmcastGroupPrefixLength object, identifies destinations for which this entry contains multicast routing information. This address object is only significant up to mvpnMrouteCmcastGroupPrefixLength bits. The remaining address bits MUST be set to zero. For addresses of type 'ipv4z' or 'ipv6z', the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicates that this forwarding state applies only within the given zone. Zone index zero is not valid in this table. 
.1.3.6.1.2.1.243.1.7.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCmcastGroupPrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask that, along with the corresponding mvpnMrouteCmcastGroupAddr object, identifies destinations for which this entry contains multicast routing information. If the corresponding InetAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If the corresponding InetAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128. 
.1.3.6.1.2.1.243.1.7.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCmcastSourceAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteCmcastSourceAddrs object that follows. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of mvpnMrouteCmcastGroupAddrType. 
.1.3.6.1.2.1.243.1.7.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCmcastSourceAddrs,OCTET,not-accessible,,current,,The network address that, along with the corresponding mvpnMrouteCmcastSourcePrefixLength object, identifies the sources for which this entry contains multicast routing information. This address object is only significant up to mvpnMrouteCmcastSourcePrefixLength bits. The remaining address bits MUST be set to zero. For addresses of type 'ipv4z' or 'ipv6z', the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicates that this source address applies only within the given zone. Zone index zero is not valid in this table. 
.1.3.6.1.2.1.243.1.7.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCmcastSourcePrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask that, along with the corresponding mvpnMrouteCmcastSourceAddr object, identifies the sources for which this entry contains multicast routing information. If the corresponding InetAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If the corresponding InetAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128. If the corresponding InetAddressType is 'unknown', this object must be zero. 
.1.3.6.1.2.1.243.1.7.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteUpstreamNeighborAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteUpstreamNeighborAddr object that follows. A value of unknown(0) indicates that the upstream neighbor is unknown, for example, in Bidirectional PIM (BIDIR-PIM). 
.1.3.6.1.2.1.243.1.7.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteUpstreamNeighborAddr,OCTET,read-only,,current,,The address of the upstream neighbor (for example, the Reverse Path Forwarding (RPF) neighbor) from which IP datagrams from these sources represented by this entry to this multicast address are received. 
.1.3.6.1.2.1.243.1.7.1.9,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteInIfIndex,Integer32,read-only,,current,,The value of ifIndex for the interface on which IP datagrams sent by these sources represented by this entry to this multicast address are received. A value of zero indicates that datagrams are not subject to an incoming interface check but may be accepted on multiple interfaces (for example, in BIDIR-PIM). 
.1.3.6.1.2.1.243.1.7.1.10,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. The value zero indicates that the entry is not subject to aging. If the corresponding mvpnMrouteNextHopState object is pruned(1), this object represents the remaining time for the prune to expire after which the state will return to forwarding(2). If the corresponding mvpnMrouteNextHopState object is forwarding(2), this object indicates the time after which this entry will be removed from the table. 
.1.3.6.1.2.1.243.1.7.1.11,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The multicast routing protocol via which this multicast forwarding entry was learned. 
.1.3.6.1.2.1.243.1.7.1.12,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteRtProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):icmp(4):egp(5):ggp(6):hello(7):rip(8):isIs(9):esIs(10):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14):idpr(15):ciscoEigrp(16):dvmrp(17):rpl(18):dhcp(19):ttdp(20),The routing protocol via which the route used to find the upstream or parent interface for this multicast forwarding entry was learned. 
.1.3.6.1.2.1.243.1.7.1.13,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteRtAddrType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteRtAddr object that follows. 
.1.3.6.1.2.1.243.1.7.1.14,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteRtAddr,OCTET,read-only,,current,,The address portion of the route used to find the upstream or parent interface for this multicast forwarding entry. This address object is only significant up to mvpnMrouteRtPrefixLength bits. The remaining address bits MUST be set to zero. For addresses of type 'ipv4z' or 'ipv6z', the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicates that this forwarding state applies only within the given zone. Zone index zero is not valid in this table. 
.1.3.6.1.2.1.243.1.7.1.15,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteRtPrefixLength,Unsigned32,read-only,,current,,The length in bits of the mask associated with the route used to find the upstream or parent interface for this multicast forwarding entry. If the corresponding InetAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If the corresponding InetAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128. 
.1.3.6.1.2.1.243.1.7.1.16,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteRtType,INTEGER,read-only,,current,unicast(1):multicast(2),The reason for placing the route in the (logical) multicast Routing Information Base (RIB). The enumerated reasons and the corresponding descriptions are as follows: unicast: The route would normally be placed only in the unicast RIB, but it was placed in the multicast RIB by local configuration, such as when running PIM over RIP. multicast: The route was explicitly added to the multicast RIB by the routing protocol, such as the Distance Vector Multicast Routing Protocol (DVMRP) or Multiprotocol BGP. 
.1.3.6.1.2.1.243.1.7.1.17,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams that were received from sources represented by this entry and addressed to this multicast group address and that were forwarded by this router. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.7.1.18,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMroutePkts,Counter64,read-only,,current,,The number of packets routed using this multicast route entry. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.7.1.19,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteTtlDroppedOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams that this router has received from sources represented by this entry and addressed to this multicast group address, which were dropped due to Time To Live (TTL) issues. TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was decremented to zero or to a value less than ipMcastInterfaceTtl of the corresponding interface. The ipMcastInterfaceTtl object is defined in IPMCAST-MIB (RFC 5132) and represents the datagram TTL threshold for the interface. Any IP multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) less than this threshold will not be forwarded out of the interface. The default value of zero means all multicast packets are forwarded out of the interface. A value of 256 means that no multicast packets are forwarded out of the interface. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.7.1.20,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteTtlDroppedPackets,Counter64,read-only,,current,,The number of packets that this router has received from the sources represented by this entry and addressed to this multicast group address, which were dropped due to Time To Live (TTL) issues. TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was decremented to zero or to a value less than ipMcastInterfaceTtl of the corresponding interface. The ipMcastInterfaceTtl object is defined in IPMCAST-MIB (RFC 5132) and represents the datagram TTL threshold for the interface. Any IP multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) less than this threshold will not be forwarded out of the interface. The default value of zero means all multicast packets are forwarded out of the interface. A value of 256 means that no multicast packets are forwarded out of the interface. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.7.1.21,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteDroppedInOctets,Counter64,read-only,,current,,The number of octets contained in IP datagrams that this router has received from sources represented by this entry and addressed to this multicast group address, which were dropped due to an error(s). The value of this object includes the octets counted in the corresponding mvpnMrouteTtlDroppedOctets object. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.7.1.22,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteDroppedInPackets,Counter64,read-only,,current,,The number of packets that this router has received from sources represented by this entry and addressed to this multicast group address, which were dropped due to an error(s). The value of this object includes the number of octets counted in the corresponding mvpnMrouteTtlDroppedPackets object. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.7.1.23,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMroutePmsiPointer,OBJECT,read-only,,current,,A pointer to a conceptual row representing the corresponding I-PMSI in mvpnPmsiTable or S-PMSI in mvpnSpmsiTable that this C-multicast route is using. 
.1.3.6.1.2.1.243.1.7.1.24,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNumberOfLocalReplication,Unsigned32,read-only,,current,,Number of replications for local receivers. For example, if an ingress PE needs to send traffic out of N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication is N. 
.1.3.6.1.2.1.243.1.7.1.25,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNumberOfRemoteReplication,Unsigned32,read-only,,current,,Number of local replications for remote PEs. For example, if the number of remote PEs that need to receive traffic is N, then mvpnMrouteNumberOfRemoteReplication is N in case of Ingress Replication, but it may be less than N in case of RSVP-TE or mLDP Point-to-Multipoint (P2MP) tunnels, depending on the actual number of replications the PE needs to do. 
.1.3.6.1.2.1.243.1.7.1.26,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this application's counters, viz., counters with the OID prefix 'mvpnMrouteOctets', 'mvpnMroutePkts', 'mvpnMrouteTtlDroppedOctets', 'mvpnMrouteTtlDroppedPackets', 'mvpnMrouteDroppedInOctets', or 'mvpnMrouteDroppedInPackets', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, this object will have a zero value. 
.1.3.6.1.2.1.243.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopTable,,not-accessible,,current,,A conceptual table containing information on the next hops for routing IP multicast datagrams. Each entry is one of a list of next hops for a set of sources sending to a multicast group address. 
.1.3.6.1.2.1.243.1.8.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopEntry,,not-accessible,mplsL3VpnVrfName:mvpnMrouteNextHopGroupAddrType:mvpnMrouteNextHopGroupAddr:mvpnMrouteNextHopGroupPrefixLength:mvpnMrouteNextHopSourceAddrType:mvpnMrouteNextHopSourceAddrs:mvpnMrouteNextHopSourcePrefixLength:mvpnMrouteNextHopIfIndex:mvpnMrouteNextHopAddrType:mvpnMrouteNextHopAddr,current,,A conceptual row corresponding to a next hop to which IP multicast datagrams from a set of sources to an IP multicast group address are routed. Implementers need to be aware that if the total number of octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr, mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr exceeds 111, the OIDs of column instances in this row will have more than 128 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 
.1.3.6.1.2.1.243.1.8.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopGroupAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteNextHopGroupAddr object that follows. 
.1.3.6.1.2.1.243.1.8.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopGroupAddr,OCTET,not-accessible,,current,,The IP multicast group address that, along with the corresponding mvpnMrouteNextHopGroupPrefixLength object, identifies destinations for which this entry contains multicast forwarding information. This address object is only significant up to mvpnMrouteNextHopGroupPrefixLength bits. The remaining address bits MUST be set to zero. For addresses of type 'ipv4z' or 'ipv6z', the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicates that this forwarding state applies only within the given zone. Zone index zero is not valid in this table. 
.1.3.6.1.2.1.243.1.8.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopGroupPrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask that, along with the corresponding mvpnMrouteGroupAddr object, identifies destinations for which this entry contains multicast routing information. If the corresponding InetAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If the corresponding InetAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128. 
.1.3.6.1.2.1.243.1.8.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopSourceAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteNextHopSourceAddrs object that follows. A value of unknown(0) indicates a non-source-specific entry, corresponding to all sources in the group. Otherwise, the value MUST be the same as the value of mvpnMrouteNextHopGroupAddrType. 
.1.3.6.1.2.1.243.1.8.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopSourceAddrs,OCTET,not-accessible,,current,,The network address that, along with the corresponding mvpnMrouteNextHopSourcePrefixLength object, identifies the sources for which this entry specifies a next hop. This address object is only significant up to mvpnMrouteNextHopSourcePrefixLength bits. The remaining address bits MUST be set to zero. For addresses of type 'ipv4z' or 'ipv6z', the appended zone index is significant even though it lies beyond the prefix length. The use of these address types indicates that this source address applies only within the given zone. Zone index zero is not valid in this table. 
.1.3.6.1.2.1.243.1.8.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopSourcePrefixLength,Unsigned32,not-accessible,,current,,The length in bits of the mask that, along with the corresponding mvpnMrouteNextHopSourceAddrs object, identifies the sources for which this entry specifies a next hop. If the corresponding InetAddressType is 'ipv4' or 'ipv4z', this object must be in the range 4..32. If the corresponding InetAddressType is 'ipv6' or 'ipv6z', this object must be in the range 8..128. If the corresponding InetAddressType is 'unknown', this object must be zero. 
.1.3.6.1.2.1.243.1.8.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the outgoing interface for this next hop. 
.1.3.6.1.2.1.243.1.8.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopAddrType,INTEGER,not-accessible,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The InetAddressType of the mvpnMrouteNextHopAddr object that follows. 
.1.3.6.1.2.1.243.1.8.1.9,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopAddr,OCTET,not-accessible,,current,,The address of the next hop specific to this entry. For most interfaces, this is identical to mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access (NBMA) interfaces, however, may have multiple next-hop addresses out of a single outgoing interface. 
.1.3.6.1.2.1.243.1.8.1.10,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopState,INTEGER,read-only,,current,pruned(1):forwarding(2),An indication of whether the outgoing interface and next hop represented by this entry is currently being used to forward IP datagrams. The enumerated states and the corresponding descriptions are as follows: pruned : this entry is not currently being used. forwarding : this entry is currently being used. 
.1.3.6.1.2.1.243.1.8.1.11,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out. If mvpnMrouteNextHopState is pruned(1), this object represents the remaining time for the prune to expire after which the state will return to forwarding(2). If mvpnMrouteNextHopState is forwarding(2), this object indicates the time after which this entry will be removed from the table. The value of zero indicates that the entry is not subject to aging. 
.1.3.6.1.2.1.243.1.8.1.12,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopClosestMemberHops,Unsigned32,read-only,,current,,The minimum number of hops between this router and any member of this IP multicast group reached via this next hop on the corresponding outgoing interface. Any IP multicast datagram for the group that has a TTL (IPv4) or a Hop Count (IPv6) less than mvpnMrouteNextHopClosestMemberHops will not be forwarded through this interface. A value of zero means all multicast datagrams are forwarded out of the interface. A value of 256 means that no multicast datagrams are forwarded out of the interface. This is an optimization applied by multicast routing protocols that explicitly track hop counts to downstream listeners. Multicast protocols that are not aware of hop counts to downstream listeners set this object to zero. 
.1.3.6.1.2.1.243.1.8.1.13,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopProtocol,INTEGER,read-only,,current,other(1):local(2):netmgmt(3):dvmrp(4):mospf(5):pimSparseDense(6):cbt(7):pimSparseMode(8):pimDenseMode(9):igmpOnly(10):bgmp(11):msdp(12),The routing protocol via which this next hop was learned. 
.1.3.6.1.2.1.243.1.8.1.14,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopOctets,Counter64,read-only,,current,,The number of octets of multicast packets that have been forwarded using this route. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteNextHopCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.8.1.15,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopPkts,Counter64,read-only,,current,,The number of packets that have been forwarded using this route. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the corresponding mvpnMrouteNextHopCounterDiscontinuityTime object. 
.1.3.6.1.2.1.243.1.8.1.16,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopCounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of this application's counters, viz., counters with the OID prefix 'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets', suffered a discontinuity. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, this object will have a zero value. 
.1.3.6.1.2.1.243.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnConformance,,,,,,
.1.3.6.1.2.1.243.2.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGroups,,,,,,
.1.3.6.1.2.1.243.2.1.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnScalarGroup,,,,,,These objects are used to monitor/manage global statistics and parameters. 
.1.3.6.1.2.1.243.2.1.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpScalarGroup,,,,,,These objects are used to monitor/manage BGP-MVPN-specific global parameters. 
.1.3.6.1.2.1.243.2.1.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnGenericGroup,,,,,,These objects are used to monitor MVPNs on a PE. 
.1.3.6.1.2.1.243.2.1.4,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnBgpGroup,,,,,,These objects are used to monitor/manage MVPN-wise BGP-specific parameters. 
.1.3.6.1.2.1.243.2.1.5,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnPmsiGroup,,,,,,These objects are used to monitor I-PMSI and S-PMSI tunnels on a PE. 
.1.3.6.1.2.1.243.2.1.6,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnAdvtStatsGroup,,,,,,These objects are used to monitor the statistics pertaining to I-PMSI and S-PMSI advertisements sent/received by a PE. 
.1.3.6.1.2.1.243.2.1.7,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteGroup,,,,,,These objects are used to monitor multicast routing information corresponding to the MVRFs on a PE. 
.1.3.6.1.2.1.243.2.1.8,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnMrouteNextHopGroup,,,,,,These objects are used to monitor the information on next hops for routing datagrams to MVPNs on a PE. 
.1.3.6.1.2.1.243.2.1.9,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnNotificationGroup,,,,,,Objects required for MVPN notifications.
.1.3.6.1.2.1.243.2.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnCompliances,,,,,,
.1.3.6.1.2.1.243.2.2.1,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnModuleFullCompliance,,,,,,Compliance statement for agents that provide full support for BGP-MPLS-LAYER3-VPN-MULTICAST-MIB. 
.1.3.6.1.2.1.243.2.2.2,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnModuleReadOnlyCompliance,,,,,,Compliance requirement for implementations that only provide read-only support for BGP-MPLS-LAYER3-VPN-MULTICAST-MIB. Such devices can then be monitored but cannot be configured using this MIB module. 
.1.3.6.1.2.1.243.2.2.3,BGP-MPLS-LAYER3-VPN-MULTICAST-MIB::mvpnModuleAdvtStatsCompliance,,,,,,Compliance statement for agents that support the monitoring of the statistics pertaining to advertisements sent/received by a PE. 
.1.3.6.1.2.1.244,L2L3-VPN-MULTICAST-TC-MIB::l2L3VpnMcastTCMIB,,,,,,This MIB module specifies textual conventions for Border Gateway Protocol/Multiprotocol Label Switching Layer 2 and Layer 3 Virtual Private Networks that support multicast (L2L3VpnMCast networks). Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). 
.1.3.6.1.2.1.245,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastMIB,,,,,,This MIB module defines a table representing the attribute information of the provider tunnels (P-tunnels) on a PE router. This MIB module will be used by other MIB modules designed for monitoring and/or configuring Border Gateway Protocol/Multiprotocol Label Switching Layer 2 and Layer 3 Virtual Private Network that support multicast (L2L3VpnMCast network). Copyright (c) 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). 
.1.3.6.1.2.1.245.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastStates,,,,,,
.1.3.6.1.2.1.245.1.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelAttributeTable,,not-accessible,,current,,An entry in this table corresponds to the attribute information of a specific P-tunnel on a PE router. A part of the attributes corresponds to fields in a Provider Multicast Service Interface (PMSI) Tunnel attribute advertised and received by a PE router. The entries will be referred to by other MIB modules for monitoring and/or configuring L2L3VpnMCast networks. 
.1.3.6.1.2.1.245.1.1.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelAttributeEntry,,not-accessible,l2L3VpnMcastPmsiTunnelAttributeType:l2L3VpnMcastPmsiTunnelAttributeId,current,,A conceptual row corresponding to a specific P-tunnel on this router. 
.1.3.6.1.2.1.245.1.1.1.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelAttributeType,INTEGER,not-accessible,,current,noTunnelInfo(0):rsvpP2mp(1):ldpP2mp(2):pimSsm(3):pimAsm(4):pimBidir(5):ingressReplication(6):ldpMp2mp(7):transportTunnel(8),This object indicates the type of tunneling technology used to establish the P-tunnel corresponding to this entry. When BGP-based PMSI signaling is used, the value of this object corresponds to the Tunnel Type field in the PMSI Tunnel attribute advertised/received in a PMSI auto-discovery (A-D) route. 
.1.3.6.1.2.1.245.1.1.1.2,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelAttributeId,OCTET,not-accessible,,current,,This object represents the Tunnel Identifier field, which uniquely identifies a P-tunnel, in the PMSI Tunnel attribute of the P-tunnel corresponding to this entry. The size of the identifier depends on the address family (IPv4 or IPv6) and the value of the corresponding l2L3VpnMcastPmsiTunnelAttributeType object, i.e., the type of tunneling technology used to establish the P-tunnel. 
.1.3.6.1.2.1.245.1.1.1.3,L2L3-VPN-MULTICAST-MIB::l2L3VpnMCastPmsiTunnelLeafInfoRequired,INTEGER,read-only,,current,false(0):true(1):notAvailable(2),When the value of this object is set to 1 (true), it indicates that the PE that originated the PMSI Tunnel attribute of the P-tunnel corresponding to this entry requests receivers to originate a new Leaf A-D route. A value of zero (false) indicates that there is no such request. When the P-tunnel does not have a corresponding PMSI Tunnel attribute, the value of this object will be 2 (notAvailable). In the case of multicast in MPLS/BGP IP VPNs, this object represents the 'Leaf Information Required flag' (RFC 6514) in the Flags field in the PMSI Tunnel attribute of the P-tunnel corresponding to this entry. 
.1.3.6.1.2.1.245.1.1.1.4,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelAttributeMplsLabel,Unsigned32,read-only,,current,,This object represents the MPLS Label in the PMSI Tunnel attribute of the P-tunnel corresponding to this entry. When BGP-based PMSI signaling is used, the PMSI Tunnel attribute of the P-tunnel will be advertised/received in a PMSI A-D route. The value of this object corresponds to the MPLS Label in the attribute. When the P-tunnel does not have a PMSI tunnel attribute, the value of this object will be zero. 
.1.3.6.1.2.1.245.1.1.1.5,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelPointer,OBJECT,read-only,,current,,Details of a P-tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId may be present in some other table, e.g., mplsTunnelTable (RFC 3812). This object specifies the pointer to the row that pertains to the entry in the table. If no such entry exists, the value of this object will be zeroDotZero. 
.1.3.6.1.2.1.245.1.1.1.6,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastPmsiTunnelIf,OBJECT,read-only,,current,,If the P-tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId has a corresponding entry in ifXTable (RFC 2863), this object will point to the row in ifXTable that pertains to the entry. Otherwise, the value of this object will be zeroDotZero. 
.1.3.6.1.2.1.245.2,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastConformance,,,,,,
.1.3.6.1.2.1.245.2.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastCompliances,,,,,,
.1.3.6.1.2.1.245.2.1.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastCoreCompliance,,,,,,The core compliance statement for SNMP entities that implement the L2L3-VPN-MULTICAST-MIB module. 
.1.3.6.1.2.1.245.2.1.2,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastFullCompliance,,,,,,The full compliance statement for SNMP entities that implement the L2L3-VPN-MULTICAST-MIB module. 
.1.3.6.1.2.1.245.2.2,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastGroups,,,,,,
.1.3.6.1.2.1.245.2.2.1,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastCoreGroup,,,,,,Support of these objects is required. 
.1.3.6.1.2.1.245.2.2.2,L2L3-VPN-MULTICAST-MIB::l2L3VpnMcastOptionalGroup,,,,,,Support of these objects is optional. 
.1.3.6.1.2.1.264,G9982-MIB::g9982MIB,,,,,,The objects in this MIB module are used to manage the Ethernet-based multi-pair bonded xDSL interfaces, as defined in ITU-T Recommendation G.998.2 (G.Bond/Ethernet). This MIB module MUST be used in conjunction with the GBOND-MIB module, common to all G.Bond technologies. The following references are used throughout this MIB module: [G.998.2] refers to: ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair bonding', January 2005. [G.998.2-Amd2] refers to: ITU-T Recommendation G.998.2 Amendment 2, December 2007. [802.3] refers to: IEEE Std 802.3-2005: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications', December 2005. [TR-159] refers to: Broadband Forum Technical Report: 'Management Framework for xDSL Bonding', December 2008. Naming Conventions: BACP - Bonding Aggregation Control Protocol BCE - Bonding Channel Entity BTU - Bonding Terminating Unit BTU-C - Bonding Terminating Unit, CO side BTU-R - Bonding Terminating Unit, Remote Terminal (CPE) side CO - Central Office CPE - Customer Premises Equipment GBS - Generic Bonding Sub-layer HDLC - High-level Data Link Control PTM-TC - Packet Transfer Mode Transmission Convergence (sub-layer) SNR - Signal to Noise Ratio TC - Transmission Convergence (sub-layer) UAS - Unavailable Seconds Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.2.1.264.1,G9982-MIB::g9982Objects,,,,,,
.1.3.6.1.2.1.264.1.1,G9982-MIB::g9982Port,,,,,,
.1.3.6.1.2.1.264.1.1.1,G9982-MIB::g9982PortConfTable,,not-accessible,,current,,Table for configuration of G.Bond/Eth GBS ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.264.1.1.1.1,G9982-MIB::g9982PortConfEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/Eth Port Configuration table. Each entry represents a G.Bond Ethernet port indexed by the ifIndex. Note that a G.Bond/Eth GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.264.1.1.1.1.1,G9982-MIB::g9982PortConfTcAdminType,INTEGER,read-write,,current,tc6465(1):tcHDLC(2),Administrative (desired) PTM-TC encapsulation type of a G.Bond/Eth port (GBS). Possible values are: tc6465(1) - 64/65-octet encapsulation tcHDLC(2) - HDLC encapsulation Attempts to set a port to a non-supported PTM-TC encapsulation type (see g9982PortCapTcTypesSupported) SHALL be rejected (with the error inconsistentValue). Changing g9982PortConfTcAdminType is a traffic-disruptive operation and as such SHALL be done when the link (GBS) is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object SHALL be rejected (with the error inconsistentValue) if the link is 'up' or initializing. This object maps to the TR-159 attribute aEthTcAdminType.
.1.3.6.1.2.1.264.1.1.1.1.2,G9982-MIB::g9982PortConfAdminCp,INTEGER,read-write,,current,unknown(0):cpHS(1):cpBACP(2),Administrative (desired) bonding control protocol of a G.Bond/Eth port (GBS). Possible values are: cpHS(1) - use G.hs-based protocol (default) cpBACP(2) - use frame-based BACP Note that G.hs-based protocol support is mandatory, according to [G.998.2]. Attempts to set a port to a non-supported bonding control protocol (e.g., BACP if the value of g9982PortCapBacpSupported is false) SHALL be rejected (with the error inconsistentValue). Changing g9982PortConfAdminCp is a traffic-disruptive operation and as such SHALL be done when the link (GBS) is administratively 'down', as indicated by the ifAdminStatus object in the IF-MIB. Attempts to change this object SHALL be rejected (with the error inconsistentValue) if the link is 'up' or initializing. This object maps to the TR-159 attribute aEthAdminCP.
.1.3.6.1.2.1.264.1.1.2,G9982-MIB::g9982PortCapTable,,not-accessible,,current,,Table for capabilities of G.Bond/Eth ports. Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.264.1.1.2.1,G9982-MIB::g9982PortCapEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/Eth Port Capability table. Each entry represents a G.Bond port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.264.1.1.2.1.1,G9982-MIB::g9982PortCapTcTypesSupported,BITS,read-only,,current,tc6465(0):tcHDLC(1),PTM-TC encapsulation types supported by the G.Bond/Eth port. This is a bitmap of possible encapsulation types. The various bit positions are: tc6465 - GBS is capable of 64/65-octet encapsulation tcHDLC - GBS is capable of HDLC encapsulation A desired encapsulation is determined by g9982PortConfTcAdminType, while g9982PortStatTcOperType reflects the current operating mode. This object maps to the TR-159 attribute aEthTcTypesSupported.
.1.3.6.1.2.1.264.1.1.2.1.2,G9982-MIB::g9982PortCapBacpSupported,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Bonding Aggregation Control Protocol (BACP) -- the frame-based discovery, aggregation, and link management protocol specified in [G.998.2-Amd2]) is supported by the G.Bond/Ethernet port. A value of true(1) indicates that BACP is supported. A value of false(2) indicates that BACP is unsupported. The BACP functionality, if supported, can be enabled or disabled via g9982AdminCP, while g9982OperCP reflects the current BACP operating mode. This object maps to the TR-159 attribute aEthBACPSupported.
.1.3.6.1.2.1.264.1.1.3,G9982-MIB::g9982PortStatTable,,not-accessible,,current,,This table provides overall status information of G.Bond ports, complementing the generic status information from the ifTable of the IF-MIB. Additional status information about connected BCEs is available from the relevant line MIBs. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.264.1.1.3.1,G9982-MIB::g9982PortStatEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/Eth Port Status table. Each entry represents a G.Bond/Eth port indexed by the ifIndex. Note that a G.Bond GBS port runs on top of a single or multiple BCE port(s), which are also indexed by the ifIndex.
.1.3.6.1.2.1.264.1.1.3.1.1,G9982-MIB::g9982PortStatTcOperType,INTEGER,read-only,,current,tc6465(1):tcHDLC(2),Current operational encapsulation type of the G.Bond/Eth port. Possible values are: tc6465(1) - GBS uses 64/65-octet encapsulation tcHDLC(2) - GBS uses HDLC encapsulation The operational PTM-TC encapsulation type can be configured via g9982PortConfTcAdminType. This object maps to the TR-159 attribute aEthTcOperType.
.1.3.6.1.2.1.264.1.1.3.1.2,G9982-MIB::g9982PortStatOperCp,INTEGER,read-only,,current,unknown(0):cpHS(1):cpBACP(2),Current operational bonding discovery and aggregation control protocol of the G.Bond/Eth port. Possible values are: unknown(0) - the protocol cannot be determined, e.g., when the GBS is 'down' cpHS(1) - GBS uses G.hs-based protocol cpBACP(2) - GBS uses frame-based BACP The operational discovery and aggregation control protocol can be configured via the g9982PortConfAdminCp variable. This object maps to the TR-159 attribute aEthOperCP.
.1.3.6.1.2.1.264.1.1.3.1.3,G9982-MIB::g9982PortStatRxErrors,Counter32,read-only,,current,,A number of Ethernet frame fragments that have been received by the bonding function and discarded due to various errors. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxErrors.
.1.3.6.1.2.1.264.1.1.3.1.4,G9982-MIB::g9982PortStatRxSmallFragments,Counter32,read-only,,current,,A number of fragments smaller than minFragmentSize (64 bytes) that have been received by the bonding function and discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxSmallFragments.
.1.3.6.1.2.1.264.1.1.3.1.5,G9982-MIB::g9982PortStatRxLargeFragments,Counter32,read-only,,current,,A number of fragments larger than maxFragmentSize (512 bytes) that have been received by the bonding function and discarded. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxLargeFragments.
.1.3.6.1.2.1.264.1.1.3.1.6,G9982-MIB::g9982PortStatRxBadFragments,Counter32,read-only,,current,,A number of fragments that do not fit into the sequence expected by the frame assembly function and that have been received and discarded by the bonding function (the frame buffer is flushed to the next valid frame start). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxBadFragments.
.1.3.6.1.2.1.264.1.1.3.1.7,G9982-MIB::g9982PortStatRxLostFragments,Counter32,read-only,,current,,A number of gaps in the sequence of fragments that have been received by the bonding function (the frame buffer is flushed to the next valid frame start, when a fragment or fragments expected by the frame assembly function are not received). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxLostFragments.
.1.3.6.1.2.1.264.1.1.3.1.8,G9982-MIB::g9982PortStatRxLostStarts,Counter32,read-only,,current,,A number of missing StartOfPacket indicators expected by the frame assembly function. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxLostStarts.
.1.3.6.1.2.1.264.1.1.3.1.9,G9982-MIB::g9982PortStatRxLostEnds,Counter32,read-only,,current,,A number of missing EndOfPacket indicators expected by the frame assembly function. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxLostEnds.
.1.3.6.1.2.1.264.1.1.3.1.10,G9982-MIB::g9982PortStatRxOverflows,Counter32,read-only,,current,,A number of fragments, received and discarded by the bonding function, that would have caused the frame assembly buffer to overflow. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aEthRxOverflows.
.1.3.6.1.2.1.264.1.1.4,G9982-MIB::g9982PM,,,,,,
.1.3.6.1.2.1.264.1.1.4.1,G9982-MIB::g9982PortPmCurTable,,not-accessible,,current,,This table contains current Performance Monitoring information for a G.Bond/Eth port. This table contains live data from the equipment and as such is NOT persistent.
.1.3.6.1.2.1.264.1.1.4.1.1,G9982-MIB::g9982PortPmCurEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/Eth Port PM table. Each entry represents a G.Bond/Eth port indexed by the ifIndex.
.1.3.6.1.2.1.264.1.1.4.1.1.1,G9982-MIB::g9982PortPm15MinValidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was collected. The value of this object will be 96 or the maximum number of 15-minute history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 15-minute intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available. This object partially maps to the TR-159 attribute aGroupPerf15MinValidIntervals.
.1.3.6.1.2.1.264.1.1.4.1.1.2,G9982-MIB::g9982PortPm15MinInvalidIntervals,Integer32,read-only,,current,,A read-only number of 15-minute intervals for which the performance data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available. This object partially maps to the TR-159 attribute aGroupPerf15MinInvalidIntervals.
.1.3.6.1.2.1.264.1.1.4.1.1.3,G9982-MIB::g9982PortPmCur15MinTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 15-minute performance interval. This object partially maps to the TR-159 attribute aGroupPerfCurr15MinTimeElapsed.
.1.3.6.1.2.1.264.1.1.4.1.1.4,G9982-MIB::g9982PortPmCur15MinRxErrors,Counter64,read-only,,current,,A read-only count of errored fragments received and discarded by a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of errored fragments is indicated by the g9982PortStatRxErrors object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.5,G9982-MIB::g9982PortPmCur15MinRxSmallFragments,Counter64,read-only,,current,,A read-only count of fragments smaller than minFragmentSize (64 bytes) that have been received and discarded by a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of small fragments is indicated by the g9982PortStatRxSmallFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.6,G9982-MIB::g9982PortPmCur15MinRxLargeFragments,Counter64,read-only,,current,,A read-only count of fragments larger than maxFragmentSize (512 bytes) that have been received and discarded by a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of large fragments is indicated by the g9982PortStatRxLargeFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.7,G9982-MIB::g9982PortPmCur15MinRxBadFragments,Counter64,read-only,,current,,A read-only count of fragments that do not fit into the sequence expected by the frame assembly function and that have been received and discarded by a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of bad fragments is indicated by the g9982PortStatRxBadFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.8,G9982-MIB::g9982PortPmCur15MinRxLostFragments,Counter64,read-only,,current,,A read-only count of gaps in the sequence of fragments expected by the frame assembly function of a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of these lost fragments is indicated by the g9982PortStatRxLostFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.9,G9982-MIB::g9982PortPmCur15MinRxLostStarts,Counter64,read-only,,current,,A read-only count of missing StartOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of missing StartOfPacket indicators is indicated by the g9982PortStatRxLostStarts object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.10,G9982-MIB::g9982PortPmCur15MinRxLostEnds,Counter64,read-only,,current,,A read-only count of missing EndOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the current 15-minute performance interval. Note that the total number of missing EndOfPacket indicators is indicated by the g9982PortStatRxLostEnds object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.11,G9982-MIB::g9982PortPmCur15MinRxOverflows,Counter64,read-only,,current,,A read-only count of fragments that have been received and discarded by a G.Bond/Eth port, which would have caused the frame assembly buffer to overflow, during the current 15-minute performance interval. Note that the total number of fragments that would have caused the frame assembly buffer to overflow is indicated by the g9982PortStatRxOverflows object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.12,G9982-MIB::g9982PortPm1DayValidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day intervals for which data was collected. The value of this object will be 7 or the maximum number of 1-day history intervals collected by the implementation, unless the measurement was (re)started recently, in which case the value will be the number of complete 1-day intervals for which there are at least some data. In certain cases, it is possible that some intervals are unavailable. In this case, this object reports the maximum interval number for which data is available.
.1.3.6.1.2.1.264.1.1.4.1.1.13,G9982-MIB::g9982PortPm1DayInvalidIntervals,Unsigned32,read-only,,current,,A read-only number of 1-day intervals for which data was not always available. The value will typically be zero, except in cases where the data for some intervals are not available.
.1.3.6.1.2.1.264.1.1.4.1.1.14,G9982-MIB::g9982PortPmCur1DayTimeElapsed,Integer32,read-only,,current,,A read-only count of seconds that have elapsed since the beginning of the current 1-day performance interval.
.1.3.6.1.2.1.264.1.1.4.1.1.15,G9982-MIB::g9982PortPmCur1DayRxErrors,Counter64,read-only,,current,,A read-only count of errored fragments received and discarded by a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of errored fragments is indicated by the g9982PortStatRxErrors object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.16,G9982-MIB::g9982PortPmCur1DayRxSmallFragments,Counter64,read-only,,current,,A read-only count of fragments smaller than minFragmentSize (64 bytes) that have been received and discarded by a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of small fragments is indicated by the g9982PortStatRxSmallFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.17,G9982-MIB::g9982PortPmCur1DayRxLargeFragments,Counter64,read-only,,current,,A read-only count of fragments larger than maxFragmentSize (512 bytes) that have been received and discarded by a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of large fragments is indicated by the g9982PortStatRxLargeFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.18,G9982-MIB::g9982PortPmCur1DayRxBadFragments,Counter64,read-only,,current,,A read-only count of fragments that do not fit into the sequence expected by the frame assembly function and that have been received and discarded by a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of bad fragments is indicated by the g9982PortStatRxBadFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.19,G9982-MIB::g9982PortPmCur1DayRxLostFragments,Counter64,read-only,,current,,A read-only count of gaps in the sequence of fragments expected by the frame assembly function of a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of these lost fragments is indicated by the g9982PortStatRxLostFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.20,G9982-MIB::g9982PortPmCur1DayRxLostStarts,Counter64,read-only,,current,,A read-only count of missing StartOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of missing StartOfPacket indicators is indicated by the g9982PortStatRxLostStarts object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.21,G9982-MIB::g9982PortPmCur1DayRxLostEnds,Counter64,read-only,,current,,A read-only count of missing EndOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the current 1-day performance interval. Note that the total number of missing EndOfPacket indicators is indicated by the g9982PortStatRxLostEnds object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.1.1.22,G9982-MIB::g9982PortPmCur1DayRxOverflows,Counter64,read-only,,current,,A read-only count of fragments that have been received and discarded by a G.Bond/Eth port, which would have caused the frame assembly buffer to overflow, during the current 1-day performance interval. Note that the total number of fragments that would have caused the frame assembly buffer to overflow is indicated by the g9982PortStatRxOverflows object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2,G9982-MIB::g9982PortPm15MinTable,,not-accessible,,current,,This table contains historical 15-minute buckets of Performance Monitoring information for a G.Bond/Eth port (a row for each 15-minute interval, up to 96 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.264.1.1.4.2.1,G9982-MIB::g9982PortPm15MinEntry,,not-accessible,ifIndex:g9982PortPm15MinIntervalIndex,current,,An entry in the G.Bond/Eth Port historical 15-minute PM table. Each entry represents Performance Monitoring data for a G.Bond/Eth port, indexed by the ifIndex, collected during a particular 15-minute interval, indexed by the g9982PortPm15MinIntervalIndex.
.1.3.6.1.2.1.264.1.1.4.2.1.1,G9982-MIB::g9982PortPm15MinIntervalIndex,Unsigned32,not-accessible,,current,,Performance Data Interval number. 1 is the most recent previous interval; interval 96 is 24 hours ago. Intervals 2..96 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalNumber.
.1.3.6.1.2.1.264.1.1.4.2.1.2,G9982-MIB::g9982PortPm15MinIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (900 seconds), except in a situation where performance data could not be collected for any reason.
.1.3.6.1.2.1.264.1.1.4.2.1.3,G9982-MIB::g9982PortPm15MinIntervalRxErrors,Counter64,read-only,,current,,A read-only count of errored fragments received and discarded by a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of errored fragments is indicated by the g9982PortStatRxErrors object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.4,G9982-MIB::g9982PortPm15MinIntervalRxSmallFragments,Counter64,read-only,,current,,A read-only count of fragments smaller than minFragmentSize (64 bytes) that have been received and discarded by a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of small fragments is indicated by the g9982PortStatRxSmallFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.5,G9982-MIB::g9982PortPm15MinIntervalRxLargeFragments,Counter64,read-only,,current,,A read-only count of fragments larger than maxFragmentSize (512 bytes) that have been received and discarded by a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of large fragments is indicated by the g9982PortStatRxLargeFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.6,G9982-MIB::g9982PortPm15MinIntervalRxBadFragments,Counter64,read-only,,current,,A read-only count of fragments that do not fit into the sequence expected by the frame assembly function and that have been received and discarded by a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of bad fragments is indicated by the g9982PortStatRxBadFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.7,G9982-MIB::g9982PortPm15MinIntervalRxLostFragments,Counter64,read-only,,current,,A read-only count of gaps in the sequence of fragments expected by the frame assembly function of a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of these lost fragments is indicated by the g9982PortStatRxLostFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.8,G9982-MIB::g9982PortPm15MinIntervalRxLostStarts,Counter64,read-only,,current,,A read-only count of missing StartOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of missing StartOfPacket indicators is indicated by the g9982PortStatRxLostStarts object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.9,G9982-MIB::g9982PortPm15MinIntervalRxLostEnds,Counter64,read-only,,current,,A read-only count of missing EndOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the 15-minute performance history interval. Note that the total number of missing EndOfPacket indicators is indicated by the g9982PortStatRxLostEnds object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.10,G9982-MIB::g9982PortPm15MinIntervalRxOverflows,Counter64,read-only,,current,,A read-only count of fragments that have been received and discarded by a G.Bond/Eth port, which would have caused the frame assembly buffer to overflow, during the 15-minute performance history interval. Note that the total number of fragments that would have caused the frame assembly buffer to overflow is indicated by the g9982PortStatRxOverflows object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.2.1.11,G9982-MIB::g9982PortPm15MinIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf15MinIntervalValid.
.1.3.6.1.2.1.264.1.1.4.3,G9982-MIB::g9982PortPm1DayTable,,not-accessible,,current,,This table contains historical 1-day buckets of Performance Monitoring information for a G.Bond/Eth port (a row for each 1-day interval, up to 7 intervals). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.264.1.1.4.3.1,G9982-MIB::g9982PortPm1DayEntry,,not-accessible,ifIndex:g9982PortPm1DayIntervalIndex,current,,An entry in the G.Bond/Eth port historical 1-day PM table. Each entry represents Performance Monitoring data for such a port, indexed by the ifIndex, collected during a particular 1-day interval, indexed by the g9982PortPm1DayIntervalIndex.
.1.3.6.1.2.1.264.1.1.4.3.1.1,G9982-MIB::g9982PortPm1DayIntervalIndex,Unsigned32,not-accessible,,current,,Performance Data Interval number. 1 is the most recent previous interval; interval 7 is 7 days ago. Intervals 2..7 are OPTIONAL. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalNumber.
.1.3.6.1.2.1.264.1.1.4.3.1.2,G9982-MIB::g9982PortPm1DayIntervalMoniTime,Integer32,read-only,,current,,A read-only count of seconds over which the performance data was actually monitored. This value will be the same as the interval duration (86400 seconds), except in a situation where performance data could not be collected for any reason. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalMoniSecs.
.1.3.6.1.2.1.264.1.1.4.3.1.3,G9982-MIB::g9982PortPm1DayIntervalRxErrors,Counter64,read-only,,current,,A read-only count of errored fragments received and discarded by a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of errored fragments is indicated by the g9982PortStatRxErrors object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.4,G9982-MIB::g9982PortPm1DayIntervalRxSmallFragments,Counter64,read-only,,current,,A read-only count of fragments smaller than minFragmentSize (64 bytes) that have been received and discarded by a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of small fragments is indicated by the g9982PortStatRxSmallFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.5,G9982-MIB::g9982PortPm1DayIntervalRxLargeFragments,Counter64,read-only,,current,,A read-only count of fragments larger than maxFragmentSize (512 bytes) that have been received and discarded by a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of large fragments is indicated by the g9982PortStatRxLargeFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.6,G9982-MIB::g9982PortPm1DayIntervalRxBadFragments,Counter64,read-only,,current,,A read-only count of fragments that do not fit into the sequence expected by the frame assembly function and that have been received and discarded by a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of bad fragments is indicated by the g9982PortStatRxBadFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.7,G9982-MIB::g9982PortPm1DayIntervalRxLostFragments,Counter64,read-only,,current,,A read-only count of gaps in the sequence of fragments expected by the frame assembly function of a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of these lost fragments is indicated by the g9982PortStatRxLostFragments object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.8,G9982-MIB::g9982PortPm1DayIntervalRxLostStarts,Counter64,read-only,,current,,A read-only count of missing StartOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of missing StartOfPacket indicators is indicated by the g9982PortStatRxLostStarts object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.9,G9982-MIB::g9982PortPm1DayIntervalRxLostEnds,Counter64,read-only,,current,,A read-only count of missing EndOfPacket indicators expected by the frame assembly function of a G.Bond/Eth port during the 1-day performance history interval. Note that the total number of missing EndOfPacket indicators is indicated by the g9982PortStatRxLostEnds object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.10,G9982-MIB::g9982PortPm1DayIntervalRxOverflows,Counter64,read-only,,current,,A read-only count of fragments that have been received and discarded by a G.Bond/Eth port, which would have caused the frame assembly buffer to overflow, during the 1-day performance history interval. Note that the total number of fragments that would have caused the frame assembly buffer to overflow is indicated by the g9982PortStatRxOverflows object. This object is inhibited during Unavailable Seconds (UAS).
.1.3.6.1.2.1.264.1.1.4.3.1.11,G9982-MIB::g9982PortPm1DayIntervalValid,INTEGER,read-only,,current,true(1):false(2),A read-only object indicating whether or not this history bucket contains valid data. A valid bucket is reported as true(1) and an invalid bucket as false(2). If this history bucket is invalid, the BTU MUST NOT produce notifications based upon the value of the counters in this bucket. Note that an implementation may decide not to store invalid history buckets in its database. In such a case, this object is not required, as only valid history buckets are available while invalid history buckets are simply not in the database. This object partially maps to the TR-159 attribute aGroupPerf1DayIntervalValid.
.1.3.6.1.2.1.264.1.2,G9982-MIB::g9982Bce,,,,,,
.1.3.6.1.2.1.264.1.2.1,G9982-MIB::g9982BceConfTable,,not-accessible,,current,,Table for configuration of G.Bond/Eth-specific aspects for the Bonding Channel Entity (BCE) ports (modems/channels). Entries in this table MUST be maintained in a persistent manner.
.1.3.6.1.2.1.264.1.2.1.1,G9982-MIB::g9982BceConfEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/Eth BCE Configuration table. Each entry represents G.998.2-specific aspects of a BCE port indexed by the ifIndex. Note that a G.Bond/Eth BCE port can be stacked below a single GBS port, also indexed by the ifIndex.
.1.3.6.1.2.1.264.1.2.1.1.1,G9982-MIB::g9982BceConfEligibleGroupID,OCTET,read-write,,current,,BACP Eligible Group ID of a G.Bond/ETH BCE port. A universally unique 6-octet-long identifier, used by the OPTIONAL BACP, to determine bonding eligibility. When two BCEs have the same g9982BceConfEligibleGroupID on a system, they are eligible to be aggregated on that system. Typically, all BCEs on a BTU-R device would be assigned the same g9982BceConfEligibleGroupID, to assert that all of the BCEs should be in the same bonded group. BCEs with different g9982BceConfEligibleGroupID values MUST NOT be connected to the same GBS. BCEs with the same g9982BceConfEligibleGroupID MAY be connected to different GBS ports. This object MUST be instantiated during BACP initialization, when every BCE belongs to its own GBS. Attempts to change this object MUST be rejected (with the error inconsistentValue), if the BCE is aggregated with other BCEs, i.e., more than one BCE is connected to the same GBS, or if the BCE in question is not eligible to be bonded with other BCEs having the same value (e.g., the bonding is limited to a single line card and BCEs are located on different line cards, or BCEs are the channels of the same line). Note that bonding eligibility is reflected in the ifCapStackTable and its inverse, the ifInvCapStackTable; as such, any modification of g9982BceConfEligibleGroupID MUST be reflected in these tables. A zero-length octet string SHALL be returned on an attempt to read this object on systems not supporting BACP (the value of g9982PortCapBacpSupported for the connected GBS is false). This object maps to the TR-159 attribute aChannelEligibleGroupID.
.1.3.6.1.2.1.264.1.2.1.1.2,G9982-MIB::g9982BceConfPeerEligibleGroupID,OCTET,read-only,,current,,BACP Eligible Group ID of a peer G.Bond/ETH BCE port, most recently received by the local BCE via a Local info TLV BACPDU message from the peer BCE. A universally unique 6-octet-long identifier, used by the OPTIONAL BACP, to determine bonding eligibility. BCEs with different g9982BceConfPeerEligibleGroupID values MUST NOT be connected to the same GBS. BCEs with the same g9982BceConfPeerEligibleGroupID MAY be connected to different GBS ports. A zero-length octet string SHALL be returned on an attempt to read this object on systems not supporting BACP (the value of g9982PortCapBacpSupported for the connected GBS is false) or when no BACPDUs have been received from the peer BCE. This object maps to the G.998.2-Amd2 attribute Remote Group ID.
.1.3.6.1.2.1.264.1.2.2,G9982-MIB::g9982BceStatTable,,not-accessible,,current,,This table provides common status information of G.Bond/Eth BCE ports. This table contains live data from the equipment. As such, it is NOT persistent.
.1.3.6.1.2.1.264.1.2.2.1,G9982-MIB::g9982BceStatEntry,,not-accessible,ifIndex,current,,An entry in the G.Bond/Eth BCE Status table. Each entry represents common aspects of a G.Bond/Eth BCE port indexed by the ifIndex. Note that a BCE port can be stacked below a single GBS port, also indexed by the ifIndex, possibly together with other BCE ports.
.1.3.6.1.2.1.264.1.2.2.1.1,G9982-MIB::g9982BceStatTcInCodingErrors,Counter32,read-only,,current,,A number of PTM-TC encapsulation errors. This counter is incremented for each encapsulation error detected by the PTM-TC receive function. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aChannelPtmTcRxCodingViolations.
.1.3.6.1.2.1.264.1.2.2.1.2,G9982-MIB::g9982BceStatTcInCrcErrors,Counter32,read-only,,current,,A number of PTM-TC CRC errors. This counter is incremented for each CRC error detected by the PTM-TC receive function. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, as defined in the IF-MIB. This object maps to the TR-159 attribute aChannelPtmTcRxCrcErrors.
.1.3.6.1.2.1.264.2,G9982-MIB::g9982Conformance,,,,,,
.1.3.6.1.2.1.264.2.1,G9982-MIB::g9982Groups,,,,,,
.1.3.6.1.2.1.264.2.1.1,G9982-MIB::g9982BasicGroup,,,,,,A collection of objects representing management information for G.Bond/Eth GBS ports.
.1.3.6.1.2.1.264.2.1.2,G9982-MIB::g9982BacpGroup,,,,,,A collection of objects representing management information for the OPTIONAL frame-based Bonding Aggregation Control Protocol (BACP) used by G.Bond/Eth GBS ports instead of the mandatory G.hs-based discovery and aggregation protocol.
.1.3.6.1.2.1.264.2.1.3,G9982-MIB::g9982BceGroup,,,,,,A collection of objects representing OPTIONAL management information for G.Bond/Eth BCE ports.
.1.3.6.1.2.1.264.2.1.4,G9982-MIB::g9982PerfCurrGroup,,,,,,A collection of objects supporting OPTIONAL current Performance Monitoring information for G.Bond/Eth ports.
.1.3.6.1.2.1.264.2.1.5,G9982-MIB::g9982Perf15MinGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/Eth ports, during previous 15-minute intervals.
.1.3.6.1.2.1.264.2.1.6,G9982-MIB::g9982Perf1DayGroup,,,,,,A collection of objects supporting OPTIONAL historical Performance Monitoring information for G.Bond/Eth ports, during previous 1-day intervals.
.1.3.6.1.2.1.264.2.2,G9982-MIB::g9982Compliances,,,,,,
.1.3.6.1.2.1.264.2.2.1,G9982-MIB::g9982Compliance,,,,,,The compliance statement for G.Bond Ethernet interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 GBOND-MIB gBondCompliance
.1.3.6.1.3,SNMPv2-SMI::experimental,,,,,,
.1.3.6.1.3.1,CLNS-MIB::clns,,,,,,
.1.3.6.1.3.1.1,CLNS-MIB::clnp,,,,,,
.1.3.6.1.3.1.1.1,CLNS-MIB::clnpForwarding,INTEGER,read-write,,mandatory,is(1):es(2),The indication of whether this entity is active as an intermediate or end system. Only intermediate systems will forward PDUs onward that are not addressed to them.
.1.3.6.1.3.1.1.2,CLNS-MIB::clnpDefaultLifeTime,INTEGER,read-write,,mandatory,,The default value inserted into the Lifetime field of the CLNP PDU header of PDUs sourced by this entity.
.1.3.6.1.3.1.1.3,CLNS-MIB::clnpInReceives,Counter32,read-only,,mandatory,,The total number of input PDUs received from all connected network interfaces running CLNP, including errors.
.1.3.6.1.3.1.1.4,CLNS-MIB::clnpInHdrErrors,Counter32,read-only,,mandatory,,The number of input PDUs discarded due to errors in the CLNP header, including bad checksums, version mismatch, lifetime exceeded, errors discovered in processing options, etc.
.1.3.6.1.3.1.1.5,CLNS-MIB::clnpInAddrErrors,Counter32,read-only,,mandatory,,The number of input PDUs discarded because the NSAP address in the CLNP header's destination field was not a valid NSAP to be received at this entity. This count includes addresses not understood. For end systems, this is a count of PDUs which arrived with a destination NSAP which was not local.
.1.3.6.1.3.1.1.6,CLNS-MIB::clnpForwPDUs,Counter32,read-only,,mandatory,,The number of input PDUs for which this entity was not the final destination and which an attempt was made to forward them onward.
.1.3.6.1.3.1.1.7,CLNS-MIB::clnpInUnknownNLPs,Counter32,read-only,,mandatory,,The number of locally-addressed PDUs successfully received but discarded because the network layer protocol was unknown or unsupported (e.g., not CLNP or ES-IS).
.1.3.6.1.3.1.1.8,CLNS-MIB::clnpInUnknownULPs,Counter32,read-only,,mandatory,,The number of locally-addressed PDUs successfully received but discarded because the upper layer protocol was unknown or unsupported (e.g., not TP4).
.1.3.6.1.3.1.1.9,CLNS-MIB::clnpInDiscards,Counter32,read-only,,mandatory,,The number of input CLNP PDUs for which no problems were encountered to prevent their continued processing, but were discarded (e.g., for lack of buffer space). Note that this counter does not include any PDUs discarded while awaiting re-assembly.
.1.3.6.1.3.1.1.10,CLNS-MIB::clnpInDelivers,Counter32,read-only,,mandatory,,The total number of input PDUs successfully delivered to the CLNS transport user.
.1.3.6.1.3.1.1.11,CLNS-MIB::clnpOutRequests,Counter32,read-only,,mandatory,,The total number of CLNP PDUs which local CLNS user protocols supplied to CLNP for transmission requests. This counter does not include any PDUs counted in clnpForwPDUs.
.1.3.6.1.3.1.1.12,CLNS-MIB::clnpOutDiscards,Counter32,read-only,,mandatory,,The number of output CLNP PDUs for which no other problem was encountered to prevent their transmission but were discarded (e.g., for lack of buffer space). Note this counter includes PDUs counted in clnpForwPDUs.
.1.3.6.1.3.1.1.13,CLNS-MIB::clnpOutNoRoutes,Counter32,read-only,,mandatory,,The number of CLNP PDUs discarded because no route could be found to transmit them to their destination. This counter includes any PDUs counted in clnpForwPDUs.
.1.3.6.1.3.1.1.14,CLNS-MIB::clnpReasmTimeout,INTEGER,read-only,,mandatory,,The maximum number of seconds which received segments are held while they are awaiting reassembly at this entity.
.1.3.6.1.3.1.1.15,CLNS-MIB::clnpReasmReqds,Counter32,read-only,,mandatory,,The number of CLNP segments received which needed to be reassembled at this entity.
.1.3.6.1.3.1.1.16,CLNS-MIB::clnpReasmOKs,Counter32,read-only,,mandatory,,The number of CLNP PDUs successfully re-assembled at this entity.
.1.3.6.1.3.1.1.17,CLNS-MIB::clnpReasmFails,Counter32,read-only,,mandatory,,The number of failures detected by the CLNP reassembly algorithm (for any reason: timed out, buffer size, etc).
.1.3.6.1.3.1.1.18,CLNS-MIB::clnpSegOKs,Counter32,read-only,,mandatory,,The number of CLNP PDUs that have been successfully segmented at this entity.
.1.3.6.1.3.1.1.19,CLNS-MIB::clnpSegFails,Counter32,read-only,,mandatory,,The number of CLNP PDUs that have been discarded because they needed to be fragmented at this entity but could not.
.1.3.6.1.3.1.1.20,CLNS-MIB::clnpSegCreates,Counter32,read-only,,mandatory,,The number of CLNP PDU segments that have been generated as a result of segmentation at this entity.
.1.3.6.1.3.1.1.21,CLNS-MIB::clnpAddrTable,,not-accessible,,mandatory,,The table of addressing information relevant to this entity's CLNP addresses. 
.1.3.6.1.3.1.1.21.1,CLNS-MIB::clnpAddrEntry,,not-accessible,clnpAdEntAddr,mandatory,,The addressing information for one of this entity's CLNP addresses.
.1.3.6.1.3.1.1.21.1.1,CLNS-MIB::clnpAdEntAddr,OCTET,read-only,,mandatory,,The CLNP address to which this entry's addressing information pertains.
.1.3.6.1.3.1.1.21.1.2,CLNS-MIB::clnpAdEntIfIndex,INTEGER,read-only,,mandatory,,The index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.3.1.1.21.1.3,CLNS-MIB::clnpAdEntReasmMaxSize,INTEGER,read-only,,mandatory,,The size of the largest CLNP PDU which this entity can re-assemble from incoming CLNP segmented PDUs received on this interface.
.1.3.6.1.3.1.1.22,CLNS-MIB::clnpRoutingTable,,not-accessible,,mandatory,,This entity's CLNP routing table.
.1.3.6.1.3.1.1.22.1,CLNS-MIB::clnpRouteEntry,,not-accessible,clnpRouteDest,mandatory,,A route to a particular destination.
.1.3.6.1.3.1.1.22.1.1,CLNS-MIB::clnpRouteDest,OCTET,read-write,,mandatory,,The destination CLNP address of this route.
.1.3.6.1.3.1.1.22.1.2,CLNS-MIB::clnpRouteIfIndex,INTEGER,read-write,,mandatory,,The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same as identified by the same value of ifIndex.
.1.3.6.1.3.1.1.22.1.3,CLNS-MIB::clnpRouteMetric1,INTEGER,read-write,,mandatory,,The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's clnpRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.3.1.1.22.1.4,CLNS-MIB::clnpRouteMetric2,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's clnpRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.3.1.1.22.1.5,CLNS-MIB::clnpRouteMetric3,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's clnpRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.3.1.1.22.1.6,CLNS-MIB::clnpRouteMetric4,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's clnpRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.3.1.1.22.1.7,CLNS-MIB::clnpRouteNextHop,OCTET,read-write,,mandatory,,The CLNP address of the next hop of this route.
.1.3.6.1.3.1.1.22.1.8,CLNS-MIB::clnpRouteType,INTEGER,read-write,,mandatory,other(1):invalid(2):direct(3):remote(4),The type of route. Setting this object to the value invalid(2) has the effect of invaliding the corresponding entry in the clnpRoutingTable. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant clnpRouteType object.
.1.3.6.1.3.1.1.22.1.9,CLNS-MIB::clnpRouteProto,INTEGER,read-only,,mandatory,other(1):local(2):netmgmt(3):is-is(9):ciscoIgrp(11):bbnSpfIgp(12):ospf(13):bgp(14),The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols.
.1.3.6.1.3.1.1.22.1.10,CLNS-MIB::clnpRouteAge,INTEGER,read-write,,mandatory,,The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.
.1.3.6.1.3.1.1.22.1.11,CLNS-MIB::clnpRouteMetric5,INTEGER,read-write,,mandatory,,An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's clnpRouteProto value. If this metric is not used, its value should be set to -1.
.1.3.6.1.3.1.1.22.1.12,CLNS-MIB::clnpRouteInfo,OBJECT,read-only,,mandatory,,A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's clnpRouteProto value. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntatically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
.1.3.6.1.3.1.1.23,CLNS-MIB::clnpNetToMediaTable,,not-accessible,,mandatory,,The CLNP Address Translation table used for mapping from CLNP addresses to physical addresses.
.1.3.6.1.3.1.1.23.1,CLNS-MIB::clnpNetToMediaEntry,,not-accessible,clnpNetToMediaIfIndex:clnpNetToMediaNetAddress,mandatory,,Each entry contains one CLNP address to `physical' address equivalence.
.1.3.6.1.3.1.1.23.1.1,CLNS-MIB::clnpNetToMediaIfIndex,INTEGER,read-write,,mandatory,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.3.1.1.23.1.2,CLNS-MIB::clnpNetToMediaPhysAddress,OCTET,read-write,,mandatory,,The media-dependent `physical' address.
.1.3.6.1.3.1.1.23.1.3,CLNS-MIB::clnpNetToMediaNetAddress,OCTET,read-write,,mandatory,,The CLNP address corresponding to the media- dependent `physical' address.
.1.3.6.1.3.1.1.23.1.4,CLNS-MIB::clnpNetToMediaType,INTEGER,read-write,,mandatory,other(1):invalid(2):dynamic(3):static(4),The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the clnpNetToMediaTable. That is, it effectively dissassociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant clnpNetToMediaType object.
.1.3.6.1.3.1.1.23.1.5,CLNS-MIB::clnpNetToMediaAge,INTEGER,read-write,,mandatory,,The number of seconds since this entry was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the type of entry.
.1.3.6.1.3.1.1.23.1.6,CLNS-MIB::clnpNetToMediaHoldTime,INTEGER,read-write,,mandatory,,The time in seconds this entry will be valid. Static entries should always report this field as -1.
.1.3.6.1.3.1.1.24,CLNS-MIB::clnpMediaToNetTable,,not-accessible,,mandatory,,The CLNP Address Translation table used for mapping from physical addresses to CLNP addresses.
.1.3.6.1.3.1.1.24.1,CLNS-MIB::clnpMediaToNetEntry,,not-accessible,clnpMediaToNetIfIndex:clnpMediaToNetPhysAddress,mandatory,,Each entry contains on ClnpAddress to `physical' address equivalence.
.1.3.6.1.3.1.1.24.1.1,CLNS-MIB::clnpMediaToNetIfIndex,INTEGER,read-write,,mandatory,,The interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
.1.3.6.1.3.1.1.24.1.2,CLNS-MIB::clnpMediaToNetAddress,OCTET,read-write,,mandatory,,The ClnpAddress corresponding to the media- dependent `physical' address.
.1.3.6.1.3.1.1.24.1.3,CLNS-MIB::clnpMediaToNetPhysAddress,OCTET,read-write,,mandatory,,The media-dependent `physical' address.
.1.3.6.1.3.1.1.24.1.4,CLNS-MIB::clnpMediaToNetType,INTEGER,read-write,,mandatory,other(1):invalid(2):dynamic(3):static(4),The type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the clnpMediaToNetTable. That is, it effectively dissassociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant clnpMediaToNetType object.
.1.3.6.1.3.1.1.24.1.5,CLNS-MIB::clnpMediaToNetAge,INTEGER,read-write,,mandatory,,The number of seconds since this entry was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the type of entry.
.1.3.6.1.3.1.1.24.1.6,CLNS-MIB::clnpMediaToNetHoldTime,INTEGER,read-write,,mandatory,,The time in seconds this entry will be valid. Static entries should always report this field as -1.
.1.3.6.1.3.1.1.25,CLNS-MIB::clnpInOpts,Counter32,read-only,,mandatory,,The number of CLNP PDU segments that have been input with options at this entity.
.1.3.6.1.3.1.1.26,CLNS-MIB::clnpOutOpts,Counter32,read-only,,mandatory,,The number of CLNP PDU segments that have been generated with options by this entity.
.1.3.6.1.3.1.1.27,CLNS-MIB::clnpRoutingDiscards,Counter32,read-only,,mandatory,,The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
.1.3.6.1.3.1.2,CLNS-MIB::error,,,,,,
.1.3.6.1.3.1.2.1,CLNS-MIB::clnpInErrors,Counter32,read-only,,mandatory,,The number of CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.2,CLNS-MIB::clnpOutErrors,Counter32,read-only,,mandatory,,The number of CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.3,CLNS-MIB::clnpInErrUnspecs,Counter32,read-only,,mandatory,,The number of unspecified CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.4,CLNS-MIB::clnpInErrProcs,Counter32,read-only,,mandatory,,The number of protocol procedure CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.5,CLNS-MIB::clnpInErrCksums,Counter32,read-only,,mandatory,,The number of checksum CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.6,CLNS-MIB::clnpInErrCongests,Counter32,read-only,,mandatory,,The number of congestion drop CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.7,CLNS-MIB::clnpInErrHdrs,Counter32,read-only,,mandatory,,The number of header syntax CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.8,CLNS-MIB::clnpInErrSegs,Counter32,read-only,,mandatory,,The number of segmentation disallowed CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.9,CLNS-MIB::clnpInErrIncomps,Counter32,read-only,,mandatory,,The number of incomplete PDU CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.10,CLNS-MIB::clnpInErrDups,Counter32,read-only,,mandatory,,The number of duplicate option CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.11,CLNS-MIB::clnpInErrUnreachDsts,Counter32,read-only,,mandatory,,The number of unreachable destination CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.12,CLNS-MIB::clnpInErrUnknownDsts,Counter32,read-only,,mandatory,,The number of unknown destination CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.13,CLNS-MIB::clnpInErrSRUnspecs,Counter32,read-only,,mandatory,,The number of unspecified source route CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.14,CLNS-MIB::clnpInErrSRSyntaxes,Counter32,read-only,,mandatory,,The number of source route syntax CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.15,CLNS-MIB::clnpInErrSRUnkAddrs,Counter32,read-only,,mandatory,,The number of source route unknown address CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.16,CLNS-MIB::clnpInErrSRBadPaths,Counter32,read-only,,mandatory,,The number of source route bad path CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.17,CLNS-MIB::clnpInErrHops,Counter32,read-only,,mandatory,,The number of hop count exceeded CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.18,CLNS-MIB::clnpInErrHopReassms,Counter32,read-only,,mandatory,,The number of hop count exceeded while reassembling CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.19,CLNS-MIB::clnpInErrUnsOptions,Counter32,read-only,,mandatory,,The number of unsupported option CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.20,CLNS-MIB::clnpInErrUnsVersions,Counter32,read-only,,mandatory,,The number of version mismatch CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.21,CLNS-MIB::clnpInErrUnsSecurities,Counter32,read-only,,mandatory,,The number of unsupported security option CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.22,CLNS-MIB::clnpInErrUnsSRs,Counter32,read-only,,mandatory,,The number of unsupported source route option CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.23,CLNS-MIB::clnpInErrUnsRRs,Counter32,read-only,,mandatory,,The number of unsupported record route option CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.24,CLNS-MIB::clnpInErrInterferences,Counter32,read-only,,mandatory,,The number of reassembly interference CLNP Error PDUs received by this entity.
.1.3.6.1.3.1.2.25,CLNS-MIB::clnpOutErrUnspecs,Counter32,read-only,,mandatory,,The number of unspecified CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.26,CLNS-MIB::clnpOutErrProcs,Counter32,read-only,,mandatory,,The number of protocol procedure CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.27,CLNS-MIB::clnpOutErrCksums,Counter32,read-only,,mandatory,,The number of checksum CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.28,CLNS-MIB::clnpOutErrCongests,Counter32,read-only,,mandatory,,The number of congestion drop CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.29,CLNS-MIB::clnpOutErrHdrs,Counter32,read-only,,mandatory,,The number of header syntax CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.30,CLNS-MIB::clnpOutErrSegs,Counter32,read-only,,mandatory,,The number of segmentation disallowed CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.31,CLNS-MIB::clnpOutErrIncomps,Counter32,read-only,,mandatory,,The number of incomplete PDU CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.32,CLNS-MIB::clnpOutErrDups,Counter32,read-only,,mandatory,,The number of duplicate option CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.33,CLNS-MIB::clnpOutErrUnreachDsts,Counter32,read-only,,mandatory,,The number of unreachable destination CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.34,CLNS-MIB::clnpOutErrUnknownDsts,Counter32,read-only,,mandatory,,The number of unknown destination CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.35,CLNS-MIB::clnpOutErrSRUnspecs,Counter32,read-only,,mandatory,,The number of unspecified source route CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.36,CLNS-MIB::clnpOutErrSRSyntaxes,Counter32,read-only,,mandatory,,The number of source route syntax CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.37,CLNS-MIB::clnpOutErrSRUnkAddrs,Counter32,read-only,,mandatory,,The number of source route unknown address CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.38,CLNS-MIB::clnpOutErrSRBadPaths,Counter32,read-only,,mandatory,,The number of source route bad path CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.39,CLNS-MIB::clnpOutErrHops,Counter32,read-only,,mandatory,,The number of hop count exceeded CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.40,CLNS-MIB::clnpOutErrHopReassms,Counter32,read-only,,mandatory,,The number of hop count exceeded while reassembling CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.41,CLNS-MIB::clnpOutErrUnsOptions,Counter32,read-only,,mandatory,,The number of unsupported option CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.42,CLNS-MIB::clnpOutErrUnsVersions,Counter32,read-only,,mandatory,,The number of version mismatch CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.43,CLNS-MIB::clnpOutErrUnsSecurities,Counter32,read-only,,mandatory,,The number of unsupported security option CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.44,CLNS-MIB::clnpOutErrUnsSRs,Counter32,read-only,,mandatory,,The number of unsupported source route option CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.45,CLNS-MIB::clnpOutErrUnsRRs,Counter32,read-only,,mandatory,,The number of unsupported record route option CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.2.46,CLNS-MIB::clnpOutErrInterferences,Counter32,read-only,,mandatory,,The number of reassembly interference CLNP Error PDUs sent by this entity.
.1.3.6.1.3.1.3,CLNS-MIB::echo,,,,,,
.1.3.6.1.3.1.4,CLNS-MIB::es-is,,,,,,
.1.3.6.1.3.1.4.1,CLNS-MIB::esisESHins,Counter32,read-only,,mandatory,,The number of ESH PDUs received by this entity.
.1.3.6.1.3.1.4.2,CLNS-MIB::esisESHouts,Counter32,read-only,,mandatory,,The number of ESH PDUs sent by this entity.
.1.3.6.1.3.1.4.3,CLNS-MIB::esisISHins,Counter32,read-only,,mandatory,,The number of ISH PDUs received by this entity.
.1.3.6.1.3.1.4.4,CLNS-MIB::esisISHouts,Counter32,read-only,,mandatory,,The number of ISH PDUs sent by this entity.
.1.3.6.1.3.1.4.5,CLNS-MIB::esisRDUins,Counter32,read-only,,mandatory,,The number of RDU PDUs received by this entity.
.1.3.6.1.3.1.4.6,CLNS-MIB::esisRDUouts,Counter32,read-only,,mandatory,,The number of RDU PDUs sent by this entity.
.1.3.6.1.3.6,RFC1229-MIB::ifExtensions,,,,,,
.1.3.6.1.3.6.1,RFC1229-MIB::ifExtnsTable,,not-accessible,,mandatory,,A list of interfaces extension entries. The number of entries is given by the value of ifNumber, defined in [4,6].
.1.3.6.1.3.6.1.1,RFC1229-MIB::ifExtnsEntry,,not-accessible,ifExtnsIfIndex,mandatory,,An extension to the interfaces entry, defined in [4,6], containing additional objects at the subnetwork layer and below for a particular interface.
.1.3.6.1.3.6.1.1.1,RFC1229-MIB::ifExtnsIfIndex,INTEGER,read-only,,mandatory,,The value of this object identifies the interface for which this entry contains extended management information. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface.
.1.3.6.1.3.6.1.1.2,RFC1229-MIB::ifExtnsChipSet,OBJECT,read-only,,mandatory,,This object identifies the hardware chip set being used in the interface. The assignment of OBJECT IDENTIFIERs to various types of hardware chip sets is managed by the IANA. If the hardware chip set is unknown, the object identifier unknownChipSet OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownChipSet is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value.
.1.3.6.1.3.6.1.1.3,RFC1229-MIB::ifExtnsRevWare,OCTET,read-only,,mandatory,,An arbitrary octet string that describes the firmware version of this interface. It is intended that this should be human readable. It must only contain ASCII printable characters. Typically this will be the firmware version of the main interface software.
.1.3.6.1.3.6.1.1.4,RFC1229-MIB::ifExtnsMulticastsTransmittedOks,Counter32,read-only,,mandatory,,The count of frames successfully transmitted to a subnetwork or link-layer multicast destination address other than a broadcast address. For a MAC layer protocol, this includes both Group and Functional addresses.
.1.3.6.1.3.6.1.1.5,RFC1229-MIB::ifExtnsBroadcastsTransmittedOks,Counter32,read-only,,mandatory,,The count of frames successfully transmitted to a subnetwork or link-layer broadcast addresses. It does not include frames sent to a multicast address.
.1.3.6.1.3.6.1.1.6,RFC1229-MIB::ifExtnsMulticastsReceivedOks,Counter32,read-only,,mandatory,,The count of frames successfully received that are directed to an active subnetwork or link-layer multicast address (for a MAC layer protocol, this includes both Group and Functional addresses). This does not include frames directed to a broadcast address, nor frames received with errors.
.1.3.6.1.3.6.1.1.7,RFC1229-MIB::ifExtnsBroadcastsReceivedOks,Counter32,read-only,,mandatory,,The count of frames successfully received that are directed to a subnetwork or link-layer broadcast address. This does not include frames received with errors.
.1.3.6.1.3.6.1.1.8,RFC1229-MIB::ifExtnsPromiscuous,INTEGER,read-only,,mandatory,true(1):false(2),This object has a value of false(2) if this interface only accepts packets/frames that are addressed to this station. This object has a value of true(1) when the station accepts all packets/frames transmitted on the media. The value true(1) is only legal on certain types of media. If legal, setting this object to a value of true(1) may require the interface to be reset before becoming effective.
.1.3.6.1.3.6.2,RFC1229-MIB::ifExtnsTestTable,,not-accessible,,mandatory,,This table contains one entry per interface.
.1.3.6.1.3.6.2.1,RFC1229-MIB::ifExtnsTestEntry,,not-accessible,ifExtnsTestIfIndex,mandatory,,An entry containing objects for invoking tests on an interface.
.1.3.6.1.3.6.2.1.1,RFC1229-MIB::ifExtnsTestIfIndex,INTEGER,read-only,,mandatory,,The value of this object identifies the interface for which this entry contains information on interface tests. The value of this object for a particular interface has the same value as the ifIndex object, defined in [4,6], for the same interface.
.1.3.6.1.3.6.2.1.2,RFC1229-MIB::ifExtnsTestCommunity,OCTET,read-only,,mandatory,,This object contains the name of the SNMP authentication community [5] which was used to authenticate the SNMP Message which invoked the current or most recent test on this interface. If the authentication community is unknown or undefined, this value contains the zero-length string.
.1.3.6.1.3.6.2.1.3,RFC1229-MIB::ifExtnsTestRequestId,INTEGER,read-only,,mandatory,,This object contains the value of the request-id field in the SNMP PDU [5] which invoked the current or most recent test on this interface. If the request-id is unknown or undefined, this value contains the value zero.
.1.3.6.1.3.6.2.1.4,RFC1229-MIB::ifExtnsTestType,OBJECT,read-write,,mandatory,,A control variable used to start and stop operator-initiated interface tests. Most OBJECT IDENTIFIER values assigned to tests are defined elsewhere, in associ- ation with specific types of interface. However, this document assigns a value for a full-duplex loopback test, and defines the special meanings of the subject identifier: noTest OBJECT IDENTIFIER ::= { 0 0 } When the value noTest is written to this object, no action is taken unless a test is in progress, in which case the test is aborted. Writing any other value to this object is only valid when no test is currently in progress, in which case the indicated test is initiated. Note that noTest is a syntactically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value. When read, this object always returns the most recent value that ifExtnsTestType was set to. If it has not been set since the last initialization of the network management subsystem on the agent, a value of noTest is returned.
.1.3.6.1.3.6.2.1.5,RFC1229-MIB::ifExtnsTestResult,INTEGER,read-only,,mandatory,none(1):success(2):inProgress(3):notSupported(4):unAbleToRun(5):aborted(6):failed(7),This object contains the result of the most recently requested test, or the value none(1) if no tests have been requested since the last reset. Note that this facility provides no provision for saving the results of one test when starting another, as could be required if used by multiple managers concurrently.
.1.3.6.1.3.6.2.1.6,RFC1229-MIB::ifExtnsTestCode,OBJECT,read-only,,mandatory,,This object contains a code which contains more specific information on the test result, for example an error-code after a failed test. Error codes and other values this object may take are specific to the type of interface and/or test. However, one subject identifier: testCodeUnknown OBJECT IDENTIFIER ::= { 0 0 } for use if no additional result code is available. Note that testCodeUnknown is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value.
.1.3.6.1.3.6.3,RFC1229-MIB::ifExtnsRcvAddrTable,,not-accessible,,mandatory,,This table contains an entry for each address (broadcast, multicast, or uni-cast) for which the system will receive packets/ frames on a particular interface. When an interface is operating in promiscuous mode, entries are only required for those addresses for which the system would receive frames were it not operating in promiscuous mode.
.1.3.6.1.3.6.3.1,RFC1229-MIB::ifExtnsRcvAddrEntry,,not-accessible,ifExtnsRcvAddrIfIndex:ifExtnsRcvAddress,mandatory,,A list of objects identifying an address for which the system will accept packets/ frames on a particular interface.
.1.3.6.1.3.6.3.1.1,RFC1229-MIB::ifExtnsRcvAddrIfIndex,INTEGER,read-only,,mandatory,,The value of ifIndex, defined in [4,6], of an interface which recognizes this entry's address.
.1.3.6.1.3.6.3.1.2,RFC1229-MIB::ifExtnsRcvAddress,OCTET,read-only,,mandatory,,An address for which the system will accept packets/frames on this entry's interface.
.1.3.6.1.3.6.3.1.3,RFC1229-MIB::ifExtnsRcvAddrStatus,INTEGER,read-write,,mandatory,other(1):invalid(2):volatile(3):nonVolatile(4),This object has the value nonVolatile(4) for those entries in the table which are valid and will not be deleted by the next restart of the managed system. Entries having the value volatile(3) are valid and exist, but have not been saved, so that will not exist after the next restart of the managed system. Entries having the value other(1) are valid and exist but are not classified as to whether they will continue to exist after the next restart. Entries having the value invalid(2) are invalid and do not represent an address for which an interface accepts frames. Setting an object instance to one of the values other(1), volatile(3), or nonVolatile(4) causes the corresponding entry to exist or continue to exist, and to take on the respective status as regards the next restart of the managed system. Setting an object instance to the value invalid(2) causes the corresponding entry to become invalid or cease to exist. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ifExtnsRcvAddrStatus object instance.
.1.3.6.1.3.6.4,RFC1229-MIB::wellKnownTests,,,,,,
.1.3.6.1.3.6.4.1,RFC1229-MIB::testFullDuplexLoopBack,,,,,,
.1.3.6.1.3.61,PIM-MIB::pimMIB,,,,,,The MIB module for management of PIM routers.
.1.3.6.1.3.61.1,PIM-MIB::pimMIBObjects,,,,,,
.1.3.6.1.3.61.1.0,PIM-MIB::pimTraps,,,,,,
.1.3.6.1.3.61.1.0.1,PIM-MIB::pimNeighborLoss,,,,,,A pimNeighborLoss trap signifies the loss of an adjacency with a neighbor. This trap should be generated when the neighbor timer expires, and the router has no other neighbors on the same interface with a lower IP address than itself.
.1.3.6.1.3.61.1.1,PIM-MIB::pim,,,,,,
.1.3.6.1.3.61.1.1.1,PIM-MIB::pimJoinPruneInterval,Integer32,read-write,,current,,The default interval at which periodic PIM-SM Join/Prune messages are to be sent.
.1.3.6.1.3.61.1.1.2,PIM-MIB::pimInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the router's PIM interfaces. IGMP and PIM are enabled on all interfaces listed in this table.
.1.3.6.1.3.61.1.1.2.1,PIM-MIB::pimInterfaceEntry,,not-accessible,pimInterfaceIfIndex,current,,An entry (conceptual row) in the pimInterfaceTable.
.1.3.6.1.3.61.1.1.2.1.1,PIM-MIB::pimInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of this PIM interface.
.1.3.6.1.3.61.1.1.2.1.2,PIM-MIB::pimInterfaceAddress,IpAddress,read-only,,current,,The IP address of the PIM interface.
.1.3.6.1.3.61.1.1.2.1.3,PIM-MIB::pimInterfaceNetMask,IpAddress,read-only,,current,,The network mask for the IP address of the PIM interface.
.1.3.6.1.3.61.1.1.2.1.4,PIM-MIB::pimInterfaceMode,INTEGER,read-create,,current,dense(1):sparse(2):sparseDense(3),The configured mode of this PIM interface. A value of sparseDense is only valid for PIMv1.
.1.3.6.1.3.61.1.1.2.1.5,PIM-MIB::pimInterfaceDR,IpAddress,read-only,,current,,The Designated Router on this PIM interface. For point-to- point interfaces, this object has the value 0.0.0.0.
.1.3.6.1.3.61.1.1.2.1.6,PIM-MIB::pimInterfaceHelloInterval,Integer32,read-create,,current,,The frequency at which PIM Hello messages are transmitted on this interface.
.1.3.6.1.3.61.1.1.2.1.7,PIM-MIB::pimInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry. Creating the entry enables PIM on the interface; destroying the entry disables PIM on the interface.
.1.3.6.1.3.61.1.1.2.1.8,PIM-MIB::pimInterfaceJoinPruneInterval,Integer32,read-create,,current,,The frequency at which PIM Join/Prune messages are transmitted on this PIM interface. The default value of this object is the pimJoinPruneInterval.
.1.3.6.1.3.61.1.1.2.1.9,PIM-MIB::pimInterfaceCBSRPreference,Integer32,read-create,,current,,The preference value for the local interface as a candidate bootstrap router. The value of -1 is used to indicate that the local interface is not a candidate BSR interface.
.1.3.6.1.3.61.1.1.3,PIM-MIB::pimNeighborTable,,not-accessible,,current,,The (conceptual) table listing the router's PIM neighbors.
.1.3.6.1.3.61.1.1.3.1,PIM-MIB::pimNeighborEntry,,not-accessible,pimNeighborAddress,current,,An entry (conceptual row) in the pimNeighborTable.
.1.3.6.1.3.61.1.1.3.1.1,PIM-MIB::pimNeighborAddress,IpAddress,not-accessible,,current,,The IP address of the PIM neighbor for which this entry contains information.
.1.3.6.1.3.61.1.1.3.1.2,PIM-MIB::pimNeighborIfIndex,Integer32,read-only,,current,,The value of ifIndex for the interface used to reach this PIM neighbor.
.1.3.6.1.3.61.1.1.3.1.3,PIM-MIB::pimNeighborUpTime,TimeTicks,read-only,,current,,The time since this PIM neighbor (last) became a neighbor of the local router.
.1.3.6.1.3.61.1.1.3.1.4,PIM-MIB::pimNeighborExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before this PIM neighbor will be aged out.
.1.3.6.1.3.61.1.1.3.1.5,PIM-MIB::pimNeighborMode,INTEGER,read-only,,deprecated,dense(1):sparse(2),The active PIM mode of this neighbor. This object is deprecated for PIMv2 routers since all neighbors on the interface must be either dense or sparse as determined by the protocol running on the interface.
.1.3.6.1.3.61.1.1.4,PIM-MIB::pimIpMRouteTable,,not-accessible,,current,,The (conceptual) table listing PIM-specific information on a subset of the rows of the ipMRouteTable defined in the IP Multicast MIB.
.1.3.6.1.3.61.1.1.4.1,PIM-MIB::pimIpMRouteEntry,,not-accessible,ipMRouteGroup:ipMRouteSource:ipMRouteSourceMask,current,,An entry (conceptual row) in the pimIpMRouteTable. There is one entry per entry in the ipMRouteTable whose incoming interface is running PIM.
.1.3.6.1.3.61.1.1.4.1.1,PIM-MIB::pimIpMRouteUpstreamAssertTimer,TimeTicks,read-only,,current,,The time remaining before the router changes its upstream neighbor back to its RPF neighbor. This timer is called the Assert timer in the PIM Sparse and Dense mode specification. A value of 0 indicates that no Assert has changed the upstream neighbor away from the RPF neighbor.
.1.3.6.1.3.61.1.1.4.1.2,PIM-MIB::pimIpMRouteAssertMetric,Integer32,read-only,,current,,The metric advertised by the assert winner on the upstream interface, or 0 if no such assert is in received.
.1.3.6.1.3.61.1.1.4.1.3,PIM-MIB::pimIpMRouteAssertMetricPref,Integer32,read-only,,current,,The preference advertised by the assert winner on the upstream interface, or 0 if no such assert is in effect.
.1.3.6.1.3.61.1.1.4.1.4,PIM-MIB::pimIpMRouteAssertRPTBit,INTEGER,read-only,,current,true(1):false(2),The value of the RPT-bit advertised by the assert winner on the upstream interface, or false if no such assert is in effect.
.1.3.6.1.3.61.1.1.4.1.5,PIM-MIB::pimIpMRouteFlags,BITS,read-only,,current,rpt(0):spt(1),This object describes PIM-specific flags related to a multicast state entry. See the PIM Sparse Mode specification for the meaning of the RPT and SPT bits.
.1.3.6.1.3.61.1.1.5,PIM-MIB::pimRPTable,,not-accessible,,deprecated,,The (conceptual) table listing PIM version 1 information for the Rendezvous Points (RPs) for IP multicast groups. This table is deprecated since its function is replaced by the pimRPSetTable for PIM version 2.
.1.3.6.1.3.61.1.1.5.1,PIM-MIB::pimRPEntry,,not-accessible,pimRPGroupAddress:pimRPAddress,deprecated,,An entry (conceptual row) in the pimRPTable. There is one entry per RP address for each IP multicast group.
.1.3.6.1.3.61.1.1.5.1.1,PIM-MIB::pimRPGroupAddress,IpAddress,not-accessible,,deprecated,,The IP multicast group address for which this entry contains information about an RP.
.1.3.6.1.3.61.1.1.5.1.2,PIM-MIB::pimRPAddress,IpAddress,not-accessible,,deprecated,,The unicast address of the RP.
.1.3.6.1.3.61.1.1.5.1.3,PIM-MIB::pimRPState,INTEGER,read-only,,deprecated,up(1):down(2),The state of the RP.
.1.3.6.1.3.61.1.1.5.1.4,PIM-MIB::pimRPStateTimer,TimeTicks,read-only,,deprecated,,The minimum time remaining before the next state change. When pimRPState is up, this is the minimum time which must expire until it can be declared down. When pimRPState is down, this is the time until it will be declared up (in order to retry).
.1.3.6.1.3.61.1.1.5.1.5,PIM-MIB::pimRPLastChange,TimeTicks,read-only,,deprecated,,The value of sysUpTime at the time when the corresponding instance of pimRPState last changed its value.
.1.3.6.1.3.61.1.1.5.1.6,PIM-MIB::pimRPRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.
.1.3.6.1.3.61.1.1.6,PIM-MIB::pimRPSetTable,,not-accessible,,current,,The (conceptual) table listing PIM information for candidate Rendezvous Points (RPs) for IP multicast groups. When the local router is the BSR, this information is obtained from received Candidate-RP-Advertisements. When the local router is not the BSR, this information is obtained from received RP-Set messages.
.1.3.6.1.3.61.1.1.6.1,PIM-MIB::pimRPSetEntry,,not-accessible,pimRPSetComponent:pimRPSetGroupAddress:pimRPSetGroupMask:pimRPSetAddress,current,,An entry (conceptual row) in the pimRPSetTable.
.1.3.6.1.3.61.1.1.6.1.1,PIM-MIB::pimRPSetGroupAddress,IpAddress,not-accessible,,current,,The IP multicast group address which, when combined with pimRPSetGroupMask, gives the group prefix for which this entry contains information about the Candidate-RP.
.1.3.6.1.3.61.1.1.6.1.2,PIM-MIB::pimRPSetGroupMask,IpAddress,not-accessible,,current,,The multicast group address mask which, when combined with pimRPSetGroupAddress, gives the group prefix for which this entry contains information about the Candidate-RP.
.1.3.6.1.3.61.1.1.6.1.3,PIM-MIB::pimRPSetAddress,IpAddress,not-accessible,,current,,The IP address of the Candidate-RP.
.1.3.6.1.3.61.1.1.6.1.4,PIM-MIB::pimRPSetHoldTime,Integer32,read-only,,current,,The holdtime of a Candidate-RP. If the local router is not the BSR, this value is 0.
.1.3.6.1.3.61.1.1.6.1.5,PIM-MIB::pimRPSetExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before the Candidate-RP will be declared down. If the local router is not the BSR, this value is 0.
.1.3.6.1.3.61.1.1.6.1.6,PIM-MIB::pimRPSetComponent,Integer32,not-accessible,,current,, A number uniquely identifying the component. Each protocol instance connected to a separate domain should have a different index value.
.1.3.6.1.3.61.1.1.7,PIM-MIB::pimIpMRouteNextHopTable,,not-accessible,,current,,The (conceptual) table listing PIM-specific information on a subset of the rows of the ipMRouteNextHopTable defined in the IP Multicast MIB.
.1.3.6.1.3.61.1.1.7.1,PIM-MIB::pimIpMRouteNextHopEntry,,not-accessible,ipMRouteNextHopGroup:ipMRouteNextHopSource:ipMRouteNextHopSourceMask:ipMRouteNextHopIfIndex:ipMRouteNextHopAddress,current,,An entry (conceptual row) in the pimIpMRouteNextHopTable. There is one entry per entry in the ipMRouteNextHopTable whose interface is running PIM and whose ipMRouteNextHopState is pruned(1).
.1.3.6.1.3.61.1.1.7.1.2,PIM-MIB::pimIpMRouteNextHopPruneReason,INTEGER,read-only,,current,other(1):prune(2):assert(3),This object indicates why the downstream interface was pruned, whether in response to a PIM prune message or due to PIM Assert processing.
.1.3.6.1.3.61.1.1.11,PIM-MIB::pimCandidateRPTable,,not-accessible,,current,,The (conceptual) table listing the IP multicast groups for which the local router is to advertise itself as a Candidate-RP when the value of pimComponentCRPHoldTime is non-zero. If this table is empty, then the local router will advertise itself as a Candidate-RP for all groups (providing the value of pimComponentCRPHoldTime is non- zero).
.1.3.6.1.3.61.1.1.11.1,PIM-MIB::pimCandidateRPEntry,,not-accessible,pimCandidateRPGroupAddress:pimCandidateRPGroupMask,current,,An entry (conceptual row) in the pimCandidateRPTable.
.1.3.6.1.3.61.1.1.11.1.1,PIM-MIB::pimCandidateRPGroupAddress,IpAddress,not-accessible,,current,,The IP multicast group address which, when combined with pimCandidateRPGroupMask, identifies a group prefix for which the local router will advertise itself as a Candidate-RP.
.1.3.6.1.3.61.1.1.11.1.2,PIM-MIB::pimCandidateRPGroupMask,IpAddress,not-accessible,,current,,The multicast group address mask which, when combined with pimCandidateRPGroupMask, identifies a group prefix for which the local router will advertise itself as a Candidate-RP.
.1.3.6.1.3.61.1.1.11.1.3,PIM-MIB::pimCandidateRPAddress,IpAddress,read-create,,current,,The (unicast) address of the interface which will be advertised as a Candidate-RP.
.1.3.6.1.3.61.1.1.11.1.4,PIM-MIB::pimCandidateRPRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.
.1.3.6.1.3.61.1.1.12,PIM-MIB::pimComponentTable,,not-accessible,,current,,The (conceptual) table containing objects specific to a PIM domain. One row exists for each domain to which the router is connected. A PIM-SM domain is defined as an area of the network over which Bootstrap messages are forwarded. Typically, a PIM-SM router will be a member of exactly one domain. This table also supports, however, routers which may form a border between two PIM-SM domains and do not forward Bootstrap messages between them.
.1.3.6.1.3.61.1.1.12.1,PIM-MIB::pimComponentEntry,,not-accessible,pimComponentIndex,current,,An entry (conceptual row) in the pimComponentTable.
.1.3.6.1.3.61.1.1.12.1.1,PIM-MIB::pimComponentIndex,Integer32,not-accessible,,current,,A number uniquely identifying the component. Each protocol instance connected to a separate domain should have a different index value. Routers that only support membership in a single PIM-SM domain should use a pimComponentIndex value of 1.
.1.3.6.1.3.61.1.1.12.1.2,PIM-MIB::pimComponentBSRAddress,IpAddress,read-only,,current,,The IP address of the bootstrap router (BSR) for the local PIM region.
.1.3.6.1.3.61.1.1.12.1.3,PIM-MIB::pimComponentBSRExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before the bootstrap router in the local domain will be declared down. For candidate BSRs, this is the time until the component sends an RP-Set message. For other routers, this is the time until it may accept an RP-Set message from a lower candidate BSR.
.1.3.6.1.3.61.1.1.12.1.4,PIM-MIB::pimComponentCRPHoldTime,Integer32,read-create,,current,,The holdtime of the component when it is a candidate RP in the local domain. The value of 0 is used to indicate that the local system is not a Candidate-RP.
.1.3.6.1.3.61.1.1.12.1.5,PIM-MIB::pimComponentStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry. Creating the entry creates another protocol instance; destroying the entry disables a protocol instance.
.1.3.6.1.3.61.2,PIM-MIB::pimMIBConformance,,,,,,
.1.3.6.1.3.61.2.1,PIM-MIB::pimMIBCompliances,,,,,,
.1.3.6.1.3.61.2.1.1,PIM-MIB::pimV1MIBCompliance,,,,,,The compliance statement for routers running PIMv1 and implementing the PIM MIB.
.1.3.6.1.3.61.2.1.2,PIM-MIB::pimSparseV2MIBCompliance,,,,,,The compliance statement for routers running PIM Sparse Mode and implementing the PIM MIB.
.1.3.6.1.3.61.2.1.3,PIM-MIB::pimDenseV2MIBCompliance,,,,,,The compliance statement for routers running PIM Dense Mode and implementing the PIM MIB.
.1.3.6.1.3.61.2.2,PIM-MIB::pimMIBGroups,,,,,,
.1.3.6.1.3.61.2.2.1,PIM-MIB::pimNotificationGroup,,,,,,A collection of notifications for signaling important PIM events.
.1.3.6.1.3.61.2.2.2,PIM-MIB::pimV2MIBGroup,,,,,,A collection of objects to support management of PIM Sparse Mode (version 2) routers.
.1.3.6.1.3.61.2.2.3,PIM-MIB::pimV2CandidateRPMIBGroup,,,,,,A collection of objects to support configuration of which groups a router is to advertise itself as a Candidate-RP.
.1.3.6.1.3.61.2.2.4,PIM-MIB::pimV1MIBGroup,,,,,,A collection of objects to support management of PIM (version 1) routers.
.1.3.6.1.3.61.2.2.5,PIM-MIB::pimDenseV2MIBGroup,,,,,,A collection of objects to support management of PIM Dense Mode (version 2) routers.
.1.3.6.1.3.61.2.2.6,PIM-MIB::pimNextHopGroup,,,,,,A collection of optional objects to provide per-next hop information for diagnostic purposes. Supporting this group may add a large number of instances to a tree walk, but the information in this group can be extremely useful in tracking down multicast connectivity problems.
.1.3.6.1.3.61.2.2.7,PIM-MIB::pimAssertGroup,,,,,,A collection of optional objects to provide extra information about the assert election process. There is no protocol reason to keep such information, but some implementations may already keep this information and make it available. These objects can also be very useful in debugging connectivity or duplicate packet problems, especially if the assert winner does not support the PIM and IP Multicast MIBs.
.1.3.6.1.3.62,DVMRP-MIB::dvmrpMIB,,,,,,The MIB module for management of DVMRP routers.
.1.3.6.1.3.62.1,DVMRP-MIB::dvmrpMIBObjects,,,,,,
.1.3.6.1.3.62.1.1,DVMRP-MIB::dvmrp,,,,,,
.1.3.6.1.3.62.1.1.1,DVMRP-MIB::dvmrpVersionString,OCTET,read-only,,current,,The router's DVMRP version information.
.1.3.6.1.3.62.1.1.2,DVMRP-MIB::dvmrpGenerationId,Integer32,read-only,,current,,The generation identifier for the routing process. This is used by neighboring routers to detect whether the DVMRP routing table should be resent.
.1.3.6.1.3.62.1.1.3,DVMRP-MIB::dvmrpInterfaceTable,,not-accessible,,current,,The (conceptual) table listing the router's multicast- capable interfaces.
.1.3.6.1.3.62.1.1.3.1,DVMRP-MIB::dvmrpInterfaceEntry,,not-accessible,dvmrpInterfaceIfIndex,current,,An entry (conceptual row) in the dvmrpInterfaceTable. This row augments ipMRouteInterfaceEntry in the IP Multicast MIB, where the threshold object resides.
.1.3.6.1.3.62.1.1.3.1.1,DVMRP-MIB::dvmrpInterfaceIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for which DVMRP is enabled.
.1.3.6.1.3.62.1.1.3.1.2,DVMRP-MIB::dvmrpInterfaceType,INTEGER,read-only,,deprecated,tunnel(1):srcrt(2):querier(3):subnet(4),The type of this DVMRP interface, whether it uses a tunnel, source routing, a physical interface for which we are a querier, or a physical interface for which we are not a querier. This object is deprecated in favor of ifType.
.1.3.6.1.3.62.1.1.3.1.3,DVMRP-MIB::dvmrpInterfaceOperState,INTEGER,read-only,,deprecated,up(1):down(2),The current operational state of this DVMRP interface. This object is deprecated in favor of ifOperStatus.
.1.3.6.1.3.62.1.1.3.1.4,DVMRP-MIB::dvmrpInterfaceLocalAddress,IpAddress,read-create,,current,,The IP address this system will use as a source address on this interface. On unnumbered interfaces, it must be the same value as dvmrpInterfaceLocalAddress for some interface on the system.
.1.3.6.1.3.62.1.1.3.1.5,DVMRP-MIB::dvmrpInterfaceRemoteAddress,IpAddress,read-create,,deprecated,,The IP address of the remote end of this DVMRP virtual interface. For a tunnel (including source routed), this is the IP address of the neighboring router. For a subnet, this is the subnet address. This object is deprecated in favor of address information associated with the underlying ifEntry.
.1.3.6.1.3.62.1.1.3.1.6,DVMRP-MIB::dvmrpInterfaceRemoteSubnetMask,IpAddress,read-only,,deprecated,,The subnet mask for a directly connected subnet. For a tunnel, this should be 0.0.0.0. This object is deprecated in favor of address information associated with the underlying ifEntry.
.1.3.6.1.3.62.1.1.3.1.7,DVMRP-MIB::dvmrpInterfaceMetric,Integer32,read-create,,current,,The distance metric for this interface which is used to calculate distance vectors.
.1.3.6.1.3.62.1.1.3.1.8,DVMRP-MIB::dvmrpInterfaceRateLimit,Integer32,read-create,,deprecated,,The rate-limit, in kilobits per second, of forwarded multicast traffic on the interface. A rate-limit of 0 indicates that no rate limiting is done. This object has been moved to the IP Multicast MIB.
.1.3.6.1.3.62.1.1.3.1.9,DVMRP-MIB::dvmrpInterfaceInPkts,Counter32,read-only,,deprecated,,The number of multicast packets that have arrived on the interface. This object is deprecated in favor of ifInMulticastPkts in the Interfaces MIB [8].
.1.3.6.1.3.62.1.1.3.1.10,DVMRP-MIB::dvmrpInterfaceOutPkts,Counter32,read-only,,deprecated,,The number of multicast packets that have been sent on the interface. This object is deprecated in favor of ifOutMulticastPkts in the Interfaces MIB [8].
.1.3.6.1.3.62.1.1.3.1.11,DVMRP-MIB::dvmrpInterfaceInOctets,Counter32,read-only,,deprecated,,The number of octets in multicast packets that have arrived on the interface. This object has been moved to the IP Multicast MIB.
.1.3.6.1.3.62.1.1.3.1.12,DVMRP-MIB::dvmrpInterfaceOutOctets,Counter32,read-only,,deprecated,,The number of octets in multicast packets that have been sent on the interface. This object has been moved to the IP Multicast MIB.
.1.3.6.1.3.62.1.1.3.1.13,DVMRP-MIB::dvmrpInterfaceStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry. Creating the entry enables DVMRP on the virtual interface; destroying the entry or setting it to notInService disables DVMRP on the virtual interface.
.1.3.6.1.3.62.1.1.3.1.14,DVMRP-MIB::dvmrpInterfaceRcvBadPkts,Counter32,read-only,,current,,The number of DVMRP packets received on the interface by the DVMRP process which were subsequently discarded as invalid (e.g. invalid packet format, or a route report from an unknown neighbor).
.1.3.6.1.3.62.1.1.3.1.15,DVMRP-MIB::dvmrpInterfaceRcvBadRoutes,Counter32,read-only,,current,,The number of routes, in valid DVMRP packets, which were ignored because the entry was invalid.
.1.3.6.1.3.62.1.1.3.1.16,DVMRP-MIB::dvmrpInterfaceSentRoutes,Counter32,read-only,,current,,The number of routes, in DVMRP Report packets, which have been sent on this interface. Together with dvmrpNeighborRcvRoutes at a peer, this object is useful for detecting routes being lost.
.1.3.6.1.3.62.1.1.3.1.17,DVMRP-MIB::dvmrpInterfaceMasterKey,OCTET,read-create,,current,,The master (shared) key for authenticating neighbors on this interface. This object is intended solely for the purpose of setting the master key, and MUST be accessible only via requests using both authentication and privacy. The agent MAY report an empty string in response to get, get-next, get-bulk requests.
.1.3.6.1.3.62.1.1.3.1.18,DVMRP-MIB::dvmrpInterfaceMasterKeyVersion,Integer32,read-create,,current,,The highest version number of all known master keys used for authenticating neighbors on this interface.
.1.3.6.1.3.62.1.1.4,DVMRP-MIB::dvmrpNeighborTable,,not-accessible,,current,,The (conceptual) table listing the router's DVMRP neighbors, as discovered by receiving DVMRP messages.
.1.3.6.1.3.62.1.1.4.1,DVMRP-MIB::dvmrpNeighborEntry,,not-accessible,dvmrpNeighborIfIndex:dvmrpNeighborAddress,current,,An entry (conceptual row) in the dvmrpNeighborTable.
.1.3.6.1.3.62.1.1.4.1.1,DVMRP-MIB::dvmrpNeighborIfIndex,Integer32,not-accessible,,current,,The value of ifIndex for the virtual interface used to reach this DVMRP neighbor.
.1.3.6.1.3.62.1.1.4.1.2,DVMRP-MIB::dvmrpNeighborAddress,IpAddress,not-accessible,,current,,The IP address of the DVMRP neighbor for which this entry contains information.
.1.3.6.1.3.62.1.1.4.1.3,DVMRP-MIB::dvmrpNeighborUpTime,TimeTicks,read-only,,current,,The time since this DVMRP neighbor (last) became a neighbor of the local router.
.1.3.6.1.3.62.1.1.4.1.4,DVMRP-MIB::dvmrpNeighborExpiryTime,TimeTicks,read-only,,current,,The minimum time remaining before this DVMRP neighbor will be aged out.
.1.3.6.1.3.62.1.1.4.1.6,DVMRP-MIB::dvmrpNeighborGenerationId,Integer32,read-only,,current,,The neighboring router's generation identifier.
.1.3.6.1.3.62.1.1.4.1.7,DVMRP-MIB::dvmrpNeighborMajorVersion,Integer32,read-only,,current,,The neighboring router's major DVMRP version number.
.1.3.6.1.3.62.1.1.4.1.8,DVMRP-MIB::dvmrpNeighborMinorVersion,Integer32,read-only,,current,,The neighboring router's minor DVMRP version number.
.1.3.6.1.3.62.1.1.4.1.9,DVMRP-MIB::dvmrpNeighborCapabilities,BITS,read-only,,current,leaf(0):prune(1):generationID(2):mtrace(3),This object describes the neighboring router's capabilities. The leaf bit indicates that the neighbor has only one interface with neighbors. The prune bit indicates that the neighbor supports pruning. The generationID bit indicates that the neighbor sends its generationID in Probe messages. The mtrace bit indicates that the neighbor can handle mtrace requests.
.1.3.6.1.3.62.1.1.4.1.10,DVMRP-MIB::dvmrpNeighborRcvRoutes,Counter32,read-only,,current,,The total number of routes received in valid DVMRP packets received from this neighbor. This can be used to diagnose problems such as unicast route injection, as well as giving an indication of the level of DVMRP route exchange activity.
.1.3.6.1.3.62.1.1.4.1.11,DVMRP-MIB::dvmrpNeighborRcvBadPkts,Counter32,read-only,,current,,The number of packet received from this neighbor which were discarded as invalid.
.1.3.6.1.3.62.1.1.4.1.12,DVMRP-MIB::dvmrpNeighborRcvBadRoutes,Counter32,read-only,,current,,The number of routes, in valid DVMRP packets received from this neighbor, which were ignored because the entry was invalid.
.1.3.6.1.3.62.1.1.4.1.13,DVMRP-MIB::dvmrpNeighborState,INTEGER,read-only,,current,oneway(1):active(2):ignoring(3):down(4),State of the neighbor adjacency.
.1.3.6.1.3.62.1.1.5,DVMRP-MIB::dvmrpRouteTable,,not-accessible,,current,,The table of routes learned through DVMRP route exchange.
.1.3.6.1.3.62.1.1.5.1,DVMRP-MIB::dvmrpRouteEntry,,not-accessible,dvmrpRouteSource:dvmrpRouteSourceMask,current,,An entry (conceptual row) containing the multicast routing information used by DVMRP in place of the unicast routing information.
.1.3.6.1.3.62.1.1.5.1.1,DVMRP-MIB::dvmrpRouteSource,IpAddress,not-accessible,,current,,The network address which when combined with the corresponding value of dvmrpRouteSourceMask identifies the sources for which this entry contains multicast routing information.
.1.3.6.1.3.62.1.1.5.1.2,DVMRP-MIB::dvmrpRouteSourceMask,IpAddress,not-accessible,,current,,The network mask which when combined with the corresponding value of dvmrpRouteSource identifies the sources for which this entry contains multicast routing information.
.1.3.6.1.3.62.1.1.5.1.3,DVMRP-MIB::dvmrpRouteUpstreamNeighbor,IpAddress,read-only,,current,,The address of the upstream neighbor (e.g., RPF neighbor) from which IP datagrams from these sources are received.
.1.3.6.1.3.62.1.1.5.1.4,DVMRP-MIB::dvmrpRouteIfIndex,Integer32,read-only,,current,,The value of ifIndex for the interface on which IP datagrams sent by these sources are received.
.1.3.6.1.3.62.1.1.5.1.5,DVMRP-MIB::dvmrpRouteMetric,Integer32,read-only,,current,,The distance in hops to the source subnet.
.1.3.6.1.3.62.1.1.5.1.6,DVMRP-MIB::dvmrpRouteExpiryTime,TimeTicks,read-only,,current,,The minimum amount of time remaining before this entry will be aged out.
.1.3.6.1.3.62.1.1.5.1.7,DVMRP-MIB::dvmrpRouteUpTime,TimeTicks,read-only,,current,,The time since the route represented by this entry was learned by the router.
.1.3.6.1.3.62.1.1.6,DVMRP-MIB::dvmrpRouteNextHopTable,,not-accessible,,current,,The (conceptual) table containing information on the next hops on outgoing interfaces for routing IP multicast datagrams.
.1.3.6.1.3.62.1.1.6.1,DVMRP-MIB::dvmrpRouteNextHopEntry,,not-accessible,dvmrpRouteNextHopSource:dvmrpRouteNextHopSourceMask:dvmrpRouteNextHopIfIndex,current,,An entry (conceptual row) in the list of next hops on outgoing interfaces to which IP multicast datagrams from particular sources are routed.
.1.3.6.1.3.62.1.1.6.1.1,DVMRP-MIB::dvmrpRouteNextHopSource,IpAddress,not-accessible,,current,,The network address which when combined with the corresponding value of dvmrpRouteNextHopSourceMask identifies the sources for which this entry specifies a next hop on an outgoing interface.
.1.3.6.1.3.62.1.1.6.1.2,DVMRP-MIB::dvmrpRouteNextHopSourceMask,IpAddress,not-accessible,,current,,The network mask which when combined with the corresponding value of dvmrpRouteNextHopSource identifies the sources for which this entry specifies a next hop on an outgoing interface.
.1.3.6.1.3.62.1.1.6.1.3,DVMRP-MIB::dvmrpRouteNextHopIfIndex,Integer32,not-accessible,,current,,The ifIndex value of the interface for the outgoing interface for this next hop.
.1.3.6.1.3.62.1.1.6.1.4,DVMRP-MIB::dvmrpRouteNextHopType,INTEGER,read-only,,current,leaf(1):branch(2),Type is leaf if no downstream dependent neighbors exist on the outgoing virtual interface. Otherwise, type is branch.
.1.3.6.1.3.62.1.1.8,DVMRP-MIB::dvmrpAltNetTable,,not-accessible,,deprecated,,The (conceptual) table listing the router's alternate subnets on physical interfaces for use in constructing the routing tables.
.1.3.6.1.3.62.1.1.8.1,DVMRP-MIB::dvmrpAltNetEntry,,not-accessible,dvmrpAltNetIfIndex:dvmrpAltNetAddress:dvmrpAltNetMask,deprecated,,An entry (conceptual row) in the dvmrpAltNetTable.
.1.3.6.1.3.62.1.1.8.1.1,DVMRP-MIB::dvmrpAltNetIfIndex,Integer32,not-accessible,,deprecated,,The ifIndex value of the interface to which this alternate subnet applies.
.1.3.6.1.3.62.1.1.8.1.2,DVMRP-MIB::dvmrpAltNetAddress,IpAddress,not-accessible,,deprecated,,The subnet address of the alternate subnet.
.1.3.6.1.3.62.1.1.8.1.3,DVMRP-MIB::dvmrpAltNetMask,IpAddress,not-accessible,,deprecated,,The subnet mask of the alternate subnet.
.1.3.6.1.3.62.1.1.8.1.4,DVMRP-MIB::dvmrpAltNetStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.
.1.3.6.1.3.62.1.1.9,DVMRP-MIB::dvmrpNumRoutes,Gauge32,read-only,,current,,The number of entries in the routing table. This can be used to monitor the routing table size to detect illegal advertisements of unicast routes.
.1.3.6.1.3.62.1.1.10,DVMRP-MIB::dvmrpReachableRoutes,Gauge32,read-only,,current,,The number of entries in the routing table with non infinite metrics. This can be used to detect network partitions by observing the ratio of reachable routes to total routes.
.1.3.6.1.3.62.1.1.11,DVMRP-MIB::dvmrpTraps,,,,,,
.1.3.6.1.3.62.1.1.11.1,DVMRP-MIB::dvmrpNeighborLoss,,,,,,A dvmrpNeighborLoss trap signifies the loss of a 2-way adjacency with a neighbor. This trap should be generated when the neighbor state changes from active to one-way, ignoring, or down. The trap should be generated only if the router has no other neighbors on the same interface with a lower IP address than itself.
.1.3.6.1.3.62.1.1.11.2,DVMRP-MIB::dvmrpNeighborNotPruning,,,,,,A dvmrpNeighborNotPruning trap signifies that a non-pruning neighbor has been detected. This trap should be generated at most once per generation ID of the neighbor. For example, it may be generated at the time a neighbor is first heard from if the prune bit is not set in its capabilities. The trap should be generated only if the router has no other neighbors on the same interface with a lower IP address than itself.
.1.3.6.1.3.62.2,DVMRP-MIB::dvmrpMIBConformance,,,,,,
.1.3.6.1.3.62.2.1,DVMRP-MIB::dvmrpMIBCompliances,,,,,,
.1.3.6.1.3.62.2.1.1,DVMRP-MIB::dvmrpMIBCompliance,,,,,,The compliance statement for the DVMRP MIB.
.1.3.6.1.3.62.2.2,DVMRP-MIB::dvmrpMIBGroups,,,,,,
.1.3.6.1.3.62.2.2.1,DVMRP-MIB::dvmrpMIBGroup,,,,,,A collection of objects to support management of DVMRP routers.
.1.3.6.1.3.62.2.2.2,DVMRP-MIB::dvmrpGeneralGroup,,,,,,A collection of objects used to describe general DVMRP configuration information.
.1.3.6.1.3.62.2.2.3,DVMRP-MIB::dvmrpInterfaceGroup,,,,,,A collection of objects used to describe DVMRP interface configuration and statistics.
.1.3.6.1.3.62.2.2.4,DVMRP-MIB::dvmrpNeighborGroup,,,,,,A collection of objects used to describe DVMRP peer configuration and statistics.
.1.3.6.1.3.62.2.2.5,DVMRP-MIB::dvmrpRoutingGroup,,,,,,A collection of objects used to store the DVMRP routing table.
.1.3.6.1.3.62.2.2.6,DVMRP-MIB::dvmrpSecurityGroup,,,,,,A collection of objects used to store information related to DVMRP security.
.1.3.6.1.3.86,IPV6-TCP-MIB::ipv6TcpMIB,,,,,,The obsolete MIB module for entities implementing TCP over IPv6. Use the TCP-MIB instead. Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.3.86.2,IPV6-TCP-MIB::ipv6TcpConformance,,,,,,
.1.3.6.1.3.86.2.1,IPV6-TCP-MIB::ipv6TcpCompliances,,,,,,
.1.3.6.1.3.86.2.1.1,IPV6-TCP-MIB::ipv6TcpCompliance,,,,,,The compliance statement for SNMPv2 entities which implement TCP over IPv6. This compliance statement is obsoleted by TCP-MIB::tcpMIBCompliance2.
.1.3.6.1.3.86.2.2,IPV6-TCP-MIB::ipv6TcpGroups,,,,,,
.1.3.6.1.3.86.2.2.1,IPV6-TCP-MIB::ipv6TcpGroup,,,,,,The group of objects providing management of TCP over IPv6. This group is obsoleted by several groups in TCP-MIB.
.1.3.6.1.3.87,IPV6-UDP-MIB::ipv6UdpMIB,,,,,,The obsolete MIB module for entities implementing UDP over IPv6. Use the UDP-MIB instead. Copyright (c) 2017 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.3.87.2,IPV6-UDP-MIB::ipv6UdpConformance,,,,,,
.1.3.6.1.3.87.2.1,IPV6-UDP-MIB::ipv6UdpCompliances,,,,,,
.1.3.6.1.3.87.2.1.1,IPV6-UDP-MIB::ipv6UdpCompliance,,,,,,The compliance statement for SNMPv2 entities which implement UDP over IPv6. This object is obsoleted by UDP-MIB::udpMIBCompliance2.
.1.3.6.1.3.87.2.2,IPV6-UDP-MIB::ipv6UdpGroups,,,,,,
.1.3.6.1.3.87.2.2.1,IPV6-UDP-MIB::ipv6UdpGroup,,,,,,The group of objects providing management of UDP over IPv6. This group is obsoleted by several groups in UDP-MIB.
.1.3.6.1.3.88,SLAPM-MIB::slapmMIB,,,,,,The Service Level Agreement Performance Monitoring MIB (SLAPM-MIB) provides data collection and monitoring capabilities for Service Level Agreements (SLAs) policy definitions.
.1.3.6.1.3.88.0,SLAPM-MIB::slapmNotifications,,,,,,
.1.3.6.1.3.88.0.1,SLAPM-MIB::slapmMonitoredEventNotAchieved,,,,,,This notification is generated when an monitored event is not achieved with respect to threshold. This applies only towards monitoring a policy traffic profile as an aggregate via an associating slapmPolicyStatsEntry. The value of slapmPolicyMonitorControl can be examined to determine what is being monitored. The first slapmPolicyMonitorStatus value supplies the current monitor status while the 2nd value supplies the previous status. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.2,SLAPM-MIB::slapmMonitoredEventOkay,,,,,,This notification is generated when a monitored event has improved to an acceptable level. This applies only towards monitoring a policy traffic profile as an aggregate via an associating slapmPolicyStatsEntry. The value of slapmPolicyMonitorControl can be examined to determine what is being monitored. The first slapmPolicyMonitorStatus value supplies the current monitor status while the 2nd value supplies the previous status. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.3,SLAPM-MIB::slapmPolicyProfileDeleted,,,,,,A slapmPolicyDeleted notification is sent when a slapmPolicyStatsEntry is deleted if the value of slapmPolicyTrapEnable is enabled(1).
.1.3.6.1.3.88.0.4,SLAPM-MIB::slapmPolicyMonitorDeleted,,,,,,A slapmPolicyMonitorDeleted notification is sent when a slapmPolicyMonitorEntry is deleted if the value of slapmPolicyTrapEnable is enabled(1).
.1.3.6.1.3.88.0.5,SLAPM-MIB::slapmSubcomponentMonitoredEventNotAchieved,,,,,,This notification is generated when a monitored value does not achieved a threshold specification. This applies only towards monitoring the individual components of a policy traffic profile. The value of the corresponding slapmPolicyMonitorControl can be examined to determine what is being monitored. The first slapmSubcomponentMonitorStatus value supplies the current monitor status while the 2nd value supplies the previous status. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableSubcomponentTraps(4), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.6,SLAPM-MIB::slapmSubcomponentMonitoredEventOkay,,,,,,This notification is generated when a monitored value has reached an acceptable level. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableSubcomponentTraps(3), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.7,SLAPM-MIB::slapmPolicyRuleMonNotOkay,,,,,,This notification is generated when an monitored event is not achieved with respect to a threshold. This applies only towards monitoring a policy rule as an aggregate via an associating slapmPolicyRuleStatsEntry. The value of slapmPRMonControl can be examined to determine what is being monitored. The first slapmPRMonStatus value supplies the current monitor status while the 2nd value supplies the previous status. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.8,SLAPM-MIB::slapmPolicyRuleMonOkay,,,,,,This notification is generated when a monitored event has improved to an acceptable level. This applies only towards monitoring a policy rule as an aggregate via an associating slapmPolicyRuleStatsEntry. The value of slapmPRMonControl can be examined to determine what is being monitored. The first slapmPRMonStatus value supplies the current monitor status while the 2nd value supplies the previous status. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.9,SLAPM-MIB::slapmPolicyRuleDeleted,,,,,,A slapmPolicyRuleDeleted notification is sent when a slapmPolicyRuleStatsEntry is deleted if the value of slapmPolicyTrapEnable is enabled(1).
.1.3.6.1.3.88.0.10,SLAPM-MIB::slapmPolicyRuleMonDeleted,,,,,,A slapmPolicyRuleMonDeleted notification is sent when a slapmPRMonEntry is deleted if the value of slapmPolicyTrapEnable is enabled(1).
.1.3.6.1.3.88.0.11,SLAPM-MIB::slapmSubcMonitorNotOkay,,,,,,This notification is generated when a monitored value does not achieved a threshold specification. This applies only towards monitoring the individual components of a policy rule. The value of the corresponding slapmPRMonControl can be examined to determine what is being monitored. The first slapmSubcomponentMonitorStatus value supplies the current monitor status while the 2nd value supplies the previous status. Note: The corresponding slapmPRMonControl BITS setting, enableSubcomponentTraps(4), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.0.12,SLAPM-MIB::slapmSubcMonitorOkay,,,,,,This notification is generated when a monitored value has reached an acceptable level. Note: The corresponding slapmPRMonControl BITS setting, enableSubcomponentTraps(3), MUST be selected in order for this notification to potentially be generated.
.1.3.6.1.3.88.1,SLAPM-MIB::slapmObjects,,,,,,
.1.3.6.1.3.88.1.1,SLAPM-MIB::slapmBaseObjects,,,,,,
.1.3.6.1.3.88.1.1.1,SLAPM-MIB::slapmSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow cooperating applications to coordinate their use of the contents of this MIB. This typically occurs when an application seeks to create an new entry or alter an existing entry in slapmPRMonTable (or old slapmPolicyMonitorTable). A management implementation MAY utilize the slapmSpinLock to serialize its changes or additions. This usage is not required. However, slapmSpinLock MUST be supported by agent implementations.
.1.3.6.1.3.88.1.1.2,SLAPM-MIB::slapmPolicyCountQueries,Counter32,read-only,,current,,The total number of times that a policy lookup occurred with respect to a policy agent. This is the number of times that a reference was made to a policy definition at a system and includes the number of times that a policy repository was accessed, slapmPolicyCountAccesses. The object slapmPolicyCountAccesses should be less than slapmPolicyCountQueries when policy definitions are cached at a system.
.1.3.6.1.3.88.1.1.3,SLAPM-MIB::slapmPolicyCountAccesses,Counter32,read-only,,current,,Total number of times that a policy repository was accessed with respect to a policy agent. The value of this object should be less than slapmPolicyCountQueries, since typically policy entries are cached to minimize repository accesses.
.1.3.6.1.3.88.1.1.4,SLAPM-MIB::slapmPolicyCountSuccessAccesses,Counter32,read-only,,current,,Total number of successful policy repository accesses with respect to a policy agent.
.1.3.6.1.3.88.1.1.5,SLAPM-MIB::slapmPolicyCountNotFounds,Counter32,read-only,,current,,Total number of policy repository accesses, with respect to a policy agent, that resulted in an entry not being located.
.1.3.6.1.3.88.1.1.6,SLAPM-MIB::slapmPolicyPurgeTime,Integer32,read-write,,current,,The purpose of this object is to define the amount of time (in seconds) to wait before removing an slapmPolicyRuleStatsEntry (or old slapmPolicyStatsEntry) when a system detects that the associated policy definition has been deleted. This gives any polling management applications time to complete their last poll before an entry is removed. An slapmPolicyRuleStatsEntry (or old slapmPolicyStatsEntry) enters the deleteNeeded(3) state via slapmPolicyRuleStatsOperStatus (or old slapmPolicyStatsOperStatus) when a system first detects that the entry needs to be removed. Once slapmPolicyPurgeTime has expired for an entry in deleteNeeded(3) state it is removed a long with any dependent slapmPRMonTable (or slapmPolicyMonitorTable) entries. A value of 0 for this option disables this function and results in the automatic purging of slapmPRMonTable (or slapmPolicyTable) entries upon transition into deleteNeeded(3) state. A slapmPolicyRuleDeleted (or slapmPolicyProfileDeleted) notification is sent when an slapmPolicyRuleStatsEntry (or slapmPolicyStatsEntry) is removed. Dependent slapmPRMonTable (or slapmPolicyMonitorTable) deletion results in a slapmPolicyRuleMonDeleted (or slapmPolicyMonitorDeleted) notification being sent. These notifications are suppressed if the value of slapmPolicyTrapEnable is disabled(2).
.1.3.6.1.3.88.1.1.7,SLAPM-MIB::slapmPolicyTrapEnable,INTEGER,read-write,,current,enabled(1):disabled(2),Indicates whether slapmPolicyRuleDeleted and slapmPolicyRuleMonDeleted (or slapmPolicyProfileDeleted and slapmPolicyMonitorDeleted) notifications should be generated by this system.
.1.3.6.1.3.88.1.1.8,SLAPM-MIB::slapmPolicyTrapFilter,Integer32,read-write,,current,,The purpose of this object is to suppress unnecessary slapmSubcMonitorNotOkay (or slapmSubcomponentMonitoredEventNotAchieved), for example, notifications. Basically, a monitored event has to not meet its SLA requirement for the number of consecutive intervals indicated by the value of this object.
.1.3.6.1.3.88.1.2,SLAPM-MIB::slapmTableObjects,,,,,,
.1.3.6.1.3.88.1.2.1,SLAPM-MIB::slapmPolicyStatsTable,,not-accessible,,deprecated,,Provides statistics on all policies known at a system. This table has been deprecated and replaced with the slapmPolicyRuleStatsTable. Older implementations of this MIB are expected to continue their support of this table.
.1.3.6.1.3.88.1.2.1.1,SLAPM-MIB::slapmPolicyStatsEntry,,not-accessible,slapmPolicyStatsSystemAddress:slapmPolicyStatsPolicyName:slapmPolicyStatsTrafficProfileName,deprecated,,Defines an entry in the slapmPolicyStatsTable. This table defines a set of statistics that is kept on a per system, policy and traffic profile basis. A policy can be defined to contain multiple traffic profiles that map to a single action. Entries in this table are not created or deleted via SNMP but reflect the set of policy definitions known at a system.
.1.3.6.1.3.88.1.2.1.1.1,SLAPM-MIB::slapmPolicyStatsSystemAddress,OCTET,not-accessible,,deprecated,,Address of a system that an Policy definition relates to. A zero length octet string must be used to indicate that only a single system is being represented. Otherwise, the length of the octet string must be 4 for an ipv4 address or 16 for an ipv6 address.
.1.3.6.1.3.88.1.2.1.1.2,SLAPM-MIB::slapmPolicyStatsPolicyName,OCTET,not-accessible,,deprecated,,Policy name that this entry relates to.
.1.3.6.1.3.88.1.2.1.1.3,SLAPM-MIB::slapmPolicyStatsTrafficProfileName,OCTET,not-accessible,,deprecated,,The name of a traffic profile that is associated with a policy.
.1.3.6.1.3.88.1.2.1.1.4,SLAPM-MIB::slapmPolicyStatsOperStatus,INTEGER,read-only,,deprecated,inactive(1):active(2):deleteNeeded(3),The state of a policy entry: inactive(1) - An policy entry was either defined by local system definition or discovered via a directory search but has not been activated (not currently being used). active(2) - Policy entry is being used to affect traffic flows. deleteNeeded(3) - Either though local implementation dependent methods or by discovering that the directory entry corresponding to this table entry no longer exists and slapmPolicyPurgeTime needs to expire before attempting to remove the corresponding slapmPolicyStatsEntry and any dependent slapmPolicyMonitor table entries. Note: a policy traffic profile in a state other than active(1) is not being used to affect traffic flows.
.1.3.6.1.3.88.1.2.1.1.5,SLAPM-MIB::slapmPolicyStatsActiveConns,Gauge32,read-only,,deprecated,,The number of active TCP connections that are affected by the corresponding policy entry.
.1.3.6.1.3.88.1.2.1.1.6,SLAPM-MIB::slapmPolicyStatsTotalConns,Counter32,read-only,,deprecated,,The number of total TCP connections that are affected by the corresponding policy entry.
.1.3.6.1.3.88.1.2.1.1.7,SLAPM-MIB::slapmPolicyStatsFirstActivated,OCTET,read-only,,deprecated,,The timestamp for when the corresponding policy entry is activated. The value of this object serves as the discontinuity event indicator when polling entries in this table. The value of this object is updated on transition of slapmPolicyStatsOperStatus into the active(2) state.
.1.3.6.1.3.88.1.2.1.1.8,SLAPM-MIB::slapmPolicyStatsLastMapping,OCTET,read-only,,deprecated,,The timestamp for when the last time that the associated policy entry was used.
.1.3.6.1.3.88.1.2.1.1.9,SLAPM-MIB::slapmPolicyStatsInOctets,Counter32,read-only,,deprecated,,The number of octets that was received by IP for an entity that map to this entry.
.1.3.6.1.3.88.1.2.1.1.10,SLAPM-MIB::slapmPolicyStatsOutOctets,Counter32,read-only,,deprecated,,The number of octets that was transmitted by IP for an entity that map to this entry.
.1.3.6.1.3.88.1.2.1.1.11,SLAPM-MIB::slapmPolicyStatsConnectionLimit,Integer32,read-only,,deprecated,,The limit for the number of active TCP connections that are allowed for this policy definition. A value of zero for this object implies that a connection limit has not been specified.
.1.3.6.1.3.88.1.2.1.1.12,SLAPM-MIB::slapmPolicyStatsCountAccepts,Counter32,read-only,,deprecated,,This counter is incremented when a policy action's Permission value is set to Accept and a session (TCP connection) is accepted.
.1.3.6.1.3.88.1.2.1.1.13,SLAPM-MIB::slapmPolicyStatsCountDenies,Counter32,read-only,,deprecated,,This counter is incremented when a policy action's Permission value is set to Deny and a session is denied, or when a session (TCP connection) is rejected due to a policy's connection limit (slapmPolicyStatsConnectLimit) being reached.
.1.3.6.1.3.88.1.2.1.1.14,SLAPM-MIB::slapmPolicyStatsInDiscards,Counter32,read-only,,deprecated,,This counter counts the number of in octets discarded. This occurs when an error is detected. Examples of this are buffer overflow, checksum error, or bad packet format.
.1.3.6.1.3.88.1.2.1.1.15,SLAPM-MIB::slapmPolicyStatsOutDiscards,Counter32,read-only,,deprecated,,This counter counts the number of out octets discarded. Examples of this are buffer overflow, checksum error, or bad packet format.
.1.3.6.1.3.88.1.2.1.1.16,SLAPM-MIB::slapmPolicyStatsInPackets,Counter32,read-only,,deprecated,,This counter counts the number of in packets received that relate to this policy entry from IP.
.1.3.6.1.3.88.1.2.1.1.17,SLAPM-MIB::slapmPolicyStatsOutPackets,Counter32,read-only,,deprecated,,This counter counts the number of out packets sent by IP that relate to this policy entry.
.1.3.6.1.3.88.1.2.1.1.18,SLAPM-MIB::slapmPolicyStatsInProfileOctets,Counter32,read-only,,deprecated,,This counter counts the number of in octets that are determined to be within profile.
.1.3.6.1.3.88.1.2.1.1.19,SLAPM-MIB::slapmPolicyStatsOutProfileOctets,Counter32,read-only,,deprecated,,This counter counts the number of out octets that are determined to be within profile.
.1.3.6.1.3.88.1.2.1.1.20,SLAPM-MIB::slapmPolicyStatsMinRate,Integer32,read-only,,deprecated,,The minimum transfer rate defined for this entry.
.1.3.6.1.3.88.1.2.1.1.21,SLAPM-MIB::slapmPolicyStatsMaxRate,Integer32,read-only,,deprecated,,The maximum transfer rate defined for this entry.
.1.3.6.1.3.88.1.2.1.1.22,SLAPM-MIB::slapmPolicyStatsMaxDelay,Integer32,read-only,,deprecated,,The maximum delay defined for this entry.
.1.3.6.1.3.88.1.2.2,SLAPM-MIB::slapmPolicyMonitorTable,,not-accessible,,deprecated,,Provides a method of monitoring policies and their effect at a system. This table has been deprecated and replaced with the slapmPRMonTable. Older implementations of this MIB are expected to continue their support of this table.
.1.3.6.1.3.88.1.2.2.1,SLAPM-MIB::slapmPolicyMonitorEntry,,not-accessible,slapmPolicyMonitorOwnerIndex:slapmPolicyMonitorSystemAddress:slapmPolicyMonitorPolicyName:slapmPolicyMonitorTrafficProfileName,deprecated,,Defines an entry in the slapmPolicyMonitorTable. This table defines which policies should be monitored on a per policy traffic profile basis.
.1.3.6.1.3.88.1.2.2.1.1,SLAPM-MIB::slapmPolicyMonitorOwnerIndex,OCTET,not-accessible,,deprecated,,To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. All entries in that table belonging to a particular user will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible.
.1.3.6.1.3.88.1.2.2.1.2,SLAPM-MIB::slapmPolicyMonitorSystemAddress,OCTET,not-accessible,,deprecated,,Address of a system that an Policy definition relates to. A zero length octet string can be used to indicate that only a single system is being represented. Otherwise, the length of the octet string should be 4 for an ipv4 address and 16 for an ipv6 address.
.1.3.6.1.3.88.1.2.2.1.3,SLAPM-MIB::slapmPolicyMonitorPolicyName,OCTET,not-accessible,,deprecated,,Policy name that this entry relates to.
.1.3.6.1.3.88.1.2.2.1.4,SLAPM-MIB::slapmPolicyMonitorTrafficProfileName,OCTET,not-accessible,,deprecated,,The corresponding Traffic Profile name.
.1.3.6.1.3.88.1.2.2.1.5,SLAPM-MIB::slapmPolicyMonitorControl,BITS,read-create,,deprecated,monitorMinRate(0):monitorMaxRate(1):monitorMaxDelay(2):enableAggregateTraps(3):enableSubcomponentTraps(4):monitorSubcomponents(5),The value of this object determines the type and level of monitoring that is applied to a policy/profile. The value of this object can't be changed once the table entry that it is a part of is activated via a slapmPolicyMonitorRowStatus transition to active state. monitorMinRate(0) - Monitor minimum transfer rate. monitorMaxRate(1) - Monitor maximum transfer rate. monitorMaxDelay(2) - Monitor maximum delay. enableAggregateTraps(3) - The enableAggregateTraps(3) BITS setting enables notification generation when monitoring a policy traffic profile as an aggregate using the values in the corresponding slapmPolicyStatsEntry. By default this function is not enabled. enableSubcomponentTraps(4) - This BITS setting enables notification generation when monitoring all subcomponents that are mapped to an corresponding slapmPolicyStatsEntry. By default this function is not enabled. monitorSubcomponents(5) - This BITS setting enables monitoring of each subcomponent (typically a TCP connection or UDP listener) individually.
.1.3.6.1.3.88.1.2.2.1.6,SLAPM-MIB::slapmPolicyMonitorStatus,BITS,read-only,,deprecated,slaMinInRateNotAchieved(0):slaMaxInRateExceeded(1):slaMaxDelayExceeded(2):slaMinOutRateNotAchieved(3):slaMaxOutRateExceeded(4):monitorMinInRateNotAchieved(5):monitorMaxInRateExceeded(6):monitorMaxDelayExceeded(7):monitorMinOutRateNotAchieved(8):monitorMaxOutRateExceeded(9),The value of this object indicates when a monitored value has not meet a threshold or isn't meeting the defined service level. The SlapmStatus TEXTUAL-CONVENTION defines two levels of not meeting a threshold. The first set: slaMinInRateNotAchieved(0), slaMaxInRateExceeded(1), slaMaxDelayExceeded(2), slaMinOutRateNotAchieved(3), slaMaxOutRateExceeded(4) are used to indicate when the SLA as an aggregate is not meeting a threshold while the second set: monitorMinInRateNotAchieved(5), monitorMaxInRateExceeded(6), monitorMaxDelayExceeded(7), monitorMinOutRateNotAchieved(8), monitorMaxOutRateExceeded(9) indicate that at least one subcomponent is not meeting a threshold.
.1.3.6.1.3.88.1.2.2.1.7,SLAPM-MIB::slapmPolicyMonitorInterval,Integer32,read-create,,deprecated,,The number of seconds that defines the sample period.
.1.3.6.1.3.88.1.2.2.1.8,SLAPM-MIB::slapmPolicyMonitorIntTime,OCTET,read-only,,deprecated,,The timestamp for when the last interval ended.
.1.3.6.1.3.88.1.2.2.1.9,SLAPM-MIB::slapmPolicyMonitorCurrentInRate,Gauge32,read-only,,deprecated,,Using the value of the corresponding slapmPolicyMonitorInterval, slapmPolicyStatsInOctets is sampled and then divided by slapmPolicyMonitorInterval to determine the current in transfer rate.
.1.3.6.1.3.88.1.2.2.1.10,SLAPM-MIB::slapmPolicyMonitorCurrentOutRate,Gauge32,read-only,,deprecated,,Using the value of the corresponding slapmPolicyMonitorInterval, slapmPolicyStatsOutOctets is sampled and then divided by slapmPolicyMonitorInterval to determine the current out transfer rate.
.1.3.6.1.3.88.1.2.2.1.11,SLAPM-MIB::slapmPolicyMonitorMinRateLow,Integer32,read-create,,deprecated,,The threshold for generating a slapmMonitoredEventNotAchieved notification, signalling that a monitored minimum transfer rate has not been meet. A slapmMonitoredEventNotAchieved notification is not generated again for an slapmPolicyMonitorEntry until the minimum transfer rate exceeds slapmPolicyMonitorMinRateHigh (a slapmMonitoredEventOkay notification is then transmitted) and then fails below slapmPolicyMonitorMinRateLow. This behavior reduces the slapmMonitoredEventNotAchieved notifications that are transmitted. A value of zero for this object is returned when the slapmPolicyMonitorControl monitorMinRate(0) is not enabled. When enabled the default value for this object is the min rate value specified in the associated action definition minus 10%. If the action definition doesn't have a min rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMinRate(0) is selected. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.2.1.12,SLAPM-MIB::slapmPolicyMonitorMinRateHigh,Integer32,read-create,,deprecated,,The threshold for generating a slapmMonitoredEventOkay notification, signalling that a monitored minimum transfer rate has increased to an acceptable level. A value of zero for this object is returned when the slapmPolicyMonitorControl monitorMinRate(0) is not enabled. When enabled the default value for this object is the min rate value specified in the associated action definition plus 10%. If the action definition doesn't have a min rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMinRate(0) is selected. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.2.1.13,SLAPM-MIB::slapmPolicyMonitorMaxRateHigh,Integer32,read-create,,deprecated,,The threshold for generating a slapmMonitoredEventNotAchieved notification, signalling that a monitored maximum transfer rate has been exceeded. A slapmMonitoredEventNotAchieved notification is not generated again for an slapmPolicyMonitorEntry until the maximum transfer rate fails below slapmPolicyMonitorMaxRateLow (a slapmMonitoredEventOkay notification is then transmitted) and then raises above slapmPolicyMonitorMaxRateHigh. This behavior reduces the slapmMonitoredEventNotAchieved notifications that are transmitted. A value of zero for this object is returned when the slapmPolicyMonitorControl monitorMaxRate(1) is not enabled. When enabled the default value for this object is the max rate value specified in the associated action definition plus 10%. If the action definition doesn't have a max rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxRate(1) is selected. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.2.1.14,SLAPM-MIB::slapmPolicyMonitorMaxRateLow,Integer32,read-create,,deprecated,,The threshold for generating a slapmMonitoredEventOkay notification, signalling that a monitored maximum transfer rate has fallen to an acceptable level. A value of zero for this object is returned when the slapmPolicyMonitorControl monitorMaxRate(1) is not enabled. When enabled the default value for this object is the max rate value specified in the associated action definition minus 10%. If the action definition doesn't have a max rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxRate(1) is selected. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.2.1.15,SLAPM-MIB::slapmPolicyMonitorMaxDelayHigh,Integer32,read-create,,deprecated,,The threshold for generating a slapmMonitoredEventNotAchieved notification, signalling that a monitored maximum delay rate has been exceeded. A slapmMonitoredEventNotAchieved notification is not generated again for an slapmPolicyMonitorEntry until the maximum delay rate falls below slapmPolicyMonitorMaxDelayLow (a slapmMonitoredEventOkay notification is then transmitted) and raises above slapmPolicyMonitorMaxDelayHigh. This behavior reduces the slapmMonitoredEventNotAchieved notifications that are transmitted. A value of zero for this object is returned when the slapmPolicyMonitorControl monitorMaxDelay(4) is not enabled. When enabled the default value for this object is the max delay value specified in the associated action definition plus 10%. If the action definition doesn't have a max delay defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxDelay(4) is selected. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.2.1.16,SLAPM-MIB::slapmPolicyMonitorMaxDelayLow,Integer32,read-create,,deprecated,,The threshold for generating a slapmMonitoredEventOkay notification, signalling that a monitored maximum delay rate has fallen to an acceptable level. A value of zero for this object is returned when the slapmPolicyMonitorControl monitorMaxDelay(4) is not enabled. When enabled the default value for this object is the max delay value specified in the associated action definition minus 10%. If the action definition doesn't have a max delay defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxDelay(4) is selected. Note: The corresponding slapmPolicyMonitorControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.2.1.17,SLAPM-MIB::slapmPolicyMonitorMinInRateNotAchieves,Counter32,read-only,,deprecated,,The number of times that a minimum transfer in rate was not achieved.
.1.3.6.1.3.88.1.2.2.1.18,SLAPM-MIB::slapmPolicyMonitorMaxInRateExceeds,Counter32,read-only,,deprecated,,The number of times that a maximum transfer in rate was exceeded.
.1.3.6.1.3.88.1.2.2.1.19,SLAPM-MIB::slapmPolicyMonitorMaxDelayExceeds,Counter32,read-only,,deprecated,,The number of times that a maximum delay in rate was exceeded.
.1.3.6.1.3.88.1.2.2.1.20,SLAPM-MIB::slapmPolicyMonitorMinOutRateNotAchieves,Counter32,read-only,,deprecated,,The number of times that a minimum transfer out rate was not achieved.
.1.3.6.1.3.88.1.2.2.1.21,SLAPM-MIB::slapmPolicyMonitorMaxOutRateExceeds,Counter32,read-only,,deprecated,,The number of times that a maximum transfer out rate was exceeded.
.1.3.6.1.3.88.1.2.2.1.22,SLAPM-MIB::slapmPolicyMonitorCurrentDelayRate,Gauge32,read-only,,deprecated,,The current delay rate for this entry. This is calculated by taking the average of the TCP round trip times for all associating slapmSubcomponentTable entries within a interval.
.1.3.6.1.3.88.1.2.2.1.23,SLAPM-MIB::slapmPolicyMonitorRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the slapmPolicyMonitorTable. An entry in this table is deleted by setting this object to destroy(6). Removal of a corresponding (same policy and traffic profile names) slapmPolicyStatsEntry has the side effect of the automatic deletion an entry in this table.
.1.3.6.1.3.88.1.2.3,SLAPM-MIB::slapmSubcomponentTable,,not-accessible,,current,,Defines a table to provide information on the individually components that are mapped to a policy rule (or old traffic profile). The indexing for this table is designed to support the use of an SNMP GET-NEXT operation using only the remote address and remote port as a way for a management station to retrieve the table entries relating to a particular client.
.1.3.6.1.3.88.1.2.3.1,SLAPM-MIB::slapmSubcomponentEntry,,not-accessible,slapmSubcomponentRemAddress:slapmSubcomponentRemPort:slapmSubcomponentLocalAddress:slapmSubcomponentLocalPort,current,,Describes a particular subcomponent entry. This table does not have an OwnerIndex as part of its indexing since this table's contents is intended to span multiple users.
.1.3.6.1.3.88.1.2.3.1.1,SLAPM-MIB::slapmSubcomponentRemAddress,OCTET,not-accessible,,current,,Indicate the remote address of a subcomponent. A remote address can be either an ipv4 address in which case 4 octets are required or as an ipv6 address that requires 16 octets. The value of this subidentifier is a zero length octet string when this entry relates to a UDP listener.
.1.3.6.1.3.88.1.2.3.1.2,SLAPM-MIB::slapmSubcomponentRemPort,Integer32,not-accessible,,current,,Indicate the remote port of a subcomponent. The value of this subidentifier is 0 when this entry relates to a UDP listener.
.1.3.6.1.3.88.1.2.3.1.3,SLAPM-MIB::slapmSubcomponentLocalAddress,OCTET,not-accessible,,current,,Indicate the local address of a subcomponent. A local address can be either an ipv4 address in which case 4 octets are required or as an ipv6 address that requires 16 octets.
.1.3.6.1.3.88.1.2.3.1.4,SLAPM-MIB::slapmSubcomponentLocalPort,Integer32,not-accessible,,current,,Indicate the local port of a subcomponent.
.1.3.6.1.3.88.1.2.3.1.5,SLAPM-MIB::slapmSubcomponentProtocol,INTEGER,read-only,,current,udpListener(1):tcpConnection(2),Indicate the protocol in use that identifies the type of subcomponent.
.1.3.6.1.3.88.1.2.3.1.6,SLAPM-MIB::slapmSubcomponentSystemAddress,OCTET,read-only,,current,,Address of a system that an Policy definition relates to. A zero length octet string can be used to indicate that only a single system is being represented. Otherwise, the length of the octet string should be 4 for an ipv4 address and 16 for an ipv6 address.
.1.3.6.1.3.88.1.2.3.1.7,SLAPM-MIB::slapmSubcomponentPolicyName,OCTET,read-only,,deprecated,,Policy name that this entry relates to. This object, along with slapmSubcomponentTrafficProfileName, have been replaced with the use of an unsigned integer index that is mapped to an slapmPolicyNameEntry to actually identify policy naming.
.1.3.6.1.3.88.1.2.3.1.8,SLAPM-MIB::slapmSubcomponentTrafficProfileName,OCTET,read-only,,deprecated,,The corresponding traffic profile name. This object, along with slapmSubcomponentProfileName, have been replaced with the use of an unsigned integer index that is mapped to an slapmPolicyNameEntry to actually identify policy naming.
.1.3.6.1.3.88.1.2.3.1.9,SLAPM-MIB::slapmSubcomponentLastActivity,OCTET,read-only,,current,,The date and timestamp of when this entry was last used.
.1.3.6.1.3.88.1.2.3.1.10,SLAPM-MIB::slapmSubcomponentInOctets,Counter32,read-only,,current,,The number of octets received from IP for this connection.
.1.3.6.1.3.88.1.2.3.1.11,SLAPM-MIB::slapmSubcomponentOutOctets,Counter32,read-only,,current,,The number of octets sent to IP for this connection.
.1.3.6.1.3.88.1.2.3.1.12,SLAPM-MIB::slapmSubcomponentTcpOutBufferedOctets,Counter32,read-only,,current,,Number of outgoing octets buffered. The value of this object is zero when the entry is not for a TCP connection.
.1.3.6.1.3.88.1.2.3.1.13,SLAPM-MIB::slapmSubcomponentTcpInBufferedOctets,Counter32,read-only,,current,,Number of incoming octets buffered. The value of this object is zero when the entry is not for a TCP connection.
.1.3.6.1.3.88.1.2.3.1.14,SLAPM-MIB::slapmSubcomponentTcpReXmts,Counter32,read-only,,current,,Number of retransmissions. The value of this object is zero when the entry is not for a TCP connection.
.1.3.6.1.3.88.1.2.3.1.15,SLAPM-MIB::slapmSubcomponentTcpRoundTripTime,Integer32,read-only,,current,,The amount of time that has elapsed, measured in milliseconds, from when the last TCP segment was transmitted by the TCP Stack until the ACK was received. The value of this object is zero when the entry is not for a TCP connection.
.1.3.6.1.3.88.1.2.3.1.16,SLAPM-MIB::slapmSubcomponentTcpRoundTripVariance,Integer32,read-only,,current,,Round trip time variance. The value of this object is zero when the entry is not for a TCP connection.
.1.3.6.1.3.88.1.2.3.1.17,SLAPM-MIB::slapmSubcomponentInPdus,Counter32,read-only,,current,,The number of protocol related data units transferred inbound: slapmSubcomponentProtocol PDU Type udpListener(1) UDP datagrams tcpConnection(2) TCP segments
.1.3.6.1.3.88.1.2.3.1.18,SLAPM-MIB::slapmSubcomponentOutPdus,Counter32,read-only,,current,,The number of protocol related data units transferred outbound: slapmSubcomponentProtocol PDU Type udpListener(1) UDP datagrams tcpConnection(2) TCP segments
.1.3.6.1.3.88.1.2.3.1.19,SLAPM-MIB::slapmSubcomponentApplName,OCTET,read-only,,current,,The application name associated with this entry if known, otherwise a zero-length octet string is returned as the value of this object.
.1.3.6.1.3.88.1.2.3.1.20,SLAPM-MIB::slapmSubcomponentMonitorStatus,BITS,read-only,,current,slaMinInRateNotAchieved(0):slaMaxInRateExceeded(1):slaMaxDelayExceeded(2):slaMinOutRateNotAchieved(3):slaMaxOutRateExceeded(4):monitorMinInRateNotAchieved(5):monitorMaxInRateExceeded(6):monitorMaxDelayExceeded(7):monitorMinOutRateNotAchieved(8):monitorMaxOutRateExceeded(9),The value of this object indicates when a monitored value has exceeded a threshold or isn't meeting the defined service level. Only the following SlapmStatus BITS setting can be reported here: monitorMinInRateNotAchieved(5), monitorMaxInRateExceeded(6), monitorMaxDelayExceeded(7), monitorMinOutRateNotAchieved(8), monitorMaxOutRateExceeded(9) This object only has meaning when an corresponding slapmPolicyMonitorEntry exists with the slapmPolicyMonitorControl BITS setting monitorSubcomponents(5) enabled.
.1.3.6.1.3.88.1.2.3.1.21,SLAPM-MIB::slapmSubcomponentMonitorIntTime,OCTET,read-only,,current,,The timestamp for when the last interval ended. This object only has meaning when an corresponding slapmPRMonEntry (or old slapmPolicyMonitorEntry) exists with the slapmPRMonControl (or slapmPolicyMonitorControl) BITS setting monitorSubcomponents(5) enabled. All of the octets returned when monitoring is not in effect must be zero.
.1.3.6.1.3.88.1.2.3.1.22,SLAPM-MIB::slapmSubcomponentMonitorCurrentInRate,Gauge32,read-only,,current,,Using the value of the corresponding slapmPRMonInterval (or slapmPolicyMonitorInterval), slapmSubcomponentStatsInOctets is divided by slapmSubcomponentMonitorInterval to determine the current in transfer rate. This object only has meaning when an corresponding slapmPRMonEntry (or slapmPolicyMonitorEntry) exists with the slapmPRMonControl (or slapmPolicyMonitorControl) BITS setting monitorSubcomponents(5) enabled. The value of this object is zero when monitoring is not in effect.
.1.3.6.1.3.88.1.2.3.1.23,SLAPM-MIB::slapmSubcomponentMonitorCurrentOutRate,Gauge32,read-only,,current,,Using the value of the corresponding slapmPRMonInterval (or slapmPolicyMonitorInterva)l, slapmSubcomponentStatsOutOctets is divided by slapmPRMonInterval (or slapmPolicyMonitorInterval) to determine the current out transfer rate. This object only has meaning when an corresponding slapmPRMonEntry (or slapmPolicyMonitorEntry) exists with the slapmPRMonControl (or slapmPolicyMonitorControl) BITS setting monitorSubcomponents(5) enabled. The value of this object is zero when monitoring is not in effect.
.1.3.6.1.3.88.1.2.3.1.24,SLAPM-MIB::slapmSubcomponentPolicyRuleIndex,Unsigned32,read-only,,current,,Points to an slapmPolicyNameEntry when combined with slapmSubcomponentSystemAddress to indicate the policy naming that relates to this entry. A value of 0 for this object MUST be returned when the corresponding slapmSubcomponentEntry has no policy rule associated with it.
.1.3.6.1.3.88.1.2.4,SLAPM-MIB::slapmPolicyNameTable,,not-accessible,,current,,Provides the mapping between a policy index as a unsigned 32 bit integer and the unique name associated with a policy rule.
.1.3.6.1.3.88.1.2.4.1,SLAPM-MIB::slapmPolicyNameEntry,,not-accessible,slapmPolicyNameSystemAddress:slapmPolicyNameIndex,current,,Defines an entry in the slapmPolicyNameTable.
.1.3.6.1.3.88.1.2.4.1.1,SLAPM-MIB::slapmPolicyNameSystemAddress,OCTET,not-accessible,,current,,Address of a system that an Policy rule definition relates to. A zero length octet string must be used to indicate that only a single system is being represented. Otherwise, the length of the octet string must be 4 for an ipv4 address or 16 for an ipv6 address.
.1.3.6.1.3.88.1.2.4.1.2,SLAPM-MIB::slapmPolicyNameIndex,Unsigned32,not-accessible,,current,,A locally arbitrary, but unique identifier associated with this table entry. This value is not expected to remain constant across reIPLs.
.1.3.6.1.3.88.1.2.4.1.3,SLAPM-MIB::slapmPolicyNameOfRule,OCTET,read-only,,current,,The unique name that identifies a policy rule definition.
.1.3.6.1.3.88.1.2.5,SLAPM-MIB::slapmPolicyRuleStatsTable,,not-accessible,,current,,Provides statistics on a per system and a per policy rule basis.
.1.3.6.1.3.88.1.2.5.1,SLAPM-MIB::slapmPolicyRuleStatsEntry,,not-accessible,slapmPolicyNameSystemAddress:slapmPolicyNameIndex,current,,Defines an entry in the slapmPolicyRuleStatsTable. This table defines a set of statistics that is kept on a per system and per policy rule basis. Entries in this table are not created or deleted via SNMP but reflect the set of policy rule definitions known at a system.
.1.3.6.1.3.88.1.2.5.1.1,SLAPM-MIB::slapmPolicyRuleStatsOperStatus,INTEGER,read-only,,current,inactive(1):active(2):deleteNeeded(3),The state of a policy entry: inactive(1) - An policy entry was either defined by local system definition or discovered via a directory search but has not been activated (not currently being used). active(2) - Policy entry is being used to affect traffic flows. deleteNeeded(3) - Either though local implementation dependent methods or by discovering that the directory entry corresponding to this table entry no longer exists and slapmPolicyPurgeTime needs to expire before attempting to remove the corresponding slapmPolicyStatsEntry and any dependent slapmPolicyMonitor table entries. Note: a policy rule in a state other than active(2) is not being used to affect traffic flows.
.1.3.6.1.3.88.1.2.5.1.2,SLAPM-MIB::slapmPolicyRuleStatsActiveConns,Gauge32,read-only,,current,,The number of active TCP connections that are affected by the corresponding policy entry.
.1.3.6.1.3.88.1.2.5.1.3,SLAPM-MIB::slapmPolicyRuleStatsTotalConns,Counter32,read-only,,current,,The number of total TCP connections that are affected by the corresponding policy entry.
.1.3.6.1.3.88.1.2.5.1.4,SLAPM-MIB::slapmPolicyRuleStatsLActivated,OCTET,read-only,,current,,The timestamp for when the corresponding policy entry was last activated. The value of this object serves as the discontinuity event indicator when polling entries in this table. The value of this object is updated on transition of slapmPolicyRuleStatsOperStatus into the active(2) state.
.1.3.6.1.3.88.1.2.5.1.5,SLAPM-MIB::slapmPolicyRuleStatsLastMapping,OCTET,read-only,,current,,The timestamp for when the last time that the associated policy entry was used.
.1.3.6.1.3.88.1.2.5.1.6,SLAPM-MIB::slapmPolicyRuleStatsInOctets,Counter32,read-only,,current,,The number of octets that was received by IP for an entity that map to this entry.
.1.3.6.1.3.88.1.2.5.1.7,SLAPM-MIB::slapmPolicyRuleStatsOutOctets,Counter32,read-only,,current,,The number of octets that was transmitted by IP for an entity that map to this entry.
.1.3.6.1.3.88.1.2.5.1.8,SLAPM-MIB::slapmPolicyRuleStatsConnLimit,Unsigned32,read-only,,current,,The limit for the number of active TCP connections that are allowed for this policy definition. A value of zero for this object implies that a connection limit has not been specified.
.1.3.6.1.3.88.1.2.5.1.9,SLAPM-MIB::slapmPolicyRuleStatsCountAccepts,Counter32,read-only,,current,,This counter is incremented when a policy action's Permission value is set to Accept and a session (TCP connection) is accepted.
.1.3.6.1.3.88.1.2.5.1.10,SLAPM-MIB::slapmPolicyRuleStatsCountDenies,Counter32,read-only,,current,,This counter is incremented when a policy action's Permission value is set to Deny and a session is denied, or when a session (TCP connection) is rejected due to a policy's connection limit (slapmPolicyRuleStatsConnectLimit) being reached.
.1.3.6.1.3.88.1.2.5.1.11,SLAPM-MIB::slapmPolicyRuleStatsInDiscards,Counter32,read-only,,current,,This counter counts the number of in octets discarded. This occurs when an error is detected. Examples of this are buffer overflow, checksum error, or bad packet format.
.1.3.6.1.3.88.1.2.5.1.12,SLAPM-MIB::slapmPolicyRuleStatsOutDiscards,Counter32,read-only,,current,,This counter counts the number of out octets discarded. Examples of this are buffer overflow, checksum error, or bad packet format.
.1.3.6.1.3.88.1.2.5.1.13,SLAPM-MIB::slapmPolicyRuleStatsInPackets,Counter32,read-only,,current,,This counter counts the number of in packets received that relate to this policy entry from IP.
.1.3.6.1.3.88.1.2.5.1.14,SLAPM-MIB::slapmPolicyRuleStatsOutPackets,Counter32,read-only,,current,,This counter counts the number of out packets sent by IP that relate to this policy entry.
.1.3.6.1.3.88.1.2.5.1.15,SLAPM-MIB::slapmPolicyRuleStatsInProOctets,Counter32,read-only,,current,,This counter counts the number of in octets that are determined to be within profile.
.1.3.6.1.3.88.1.2.5.1.16,SLAPM-MIB::slapmPolicyRuleStatsOutProOctets,Counter32,read-only,,current,,This counter counts the number of out octets that are determined to be within profile.
.1.3.6.1.3.88.1.2.5.1.17,SLAPM-MIB::slapmPolicyRuleStatsMinRate,Unsigned32,read-only,,current,,The minimum transfer rate defined for this entry.
.1.3.6.1.3.88.1.2.5.1.18,SLAPM-MIB::slapmPolicyRuleStatsMaxRate,Unsigned32,read-only,,current,,The maximum transfer rate defined for this entry.
.1.3.6.1.3.88.1.2.5.1.19,SLAPM-MIB::slapmPolicyRuleStatsMaxDelay,Unsigned32,read-only,,current,,The maximum delay defined for this entry.
.1.3.6.1.3.88.1.2.5.1.20,SLAPM-MIB::slapmPolicyRuleStatsTotalRsvpFlows,Counter32,read-only,,current,,Total number of RSVP flows that have be activated.
.1.3.6.1.3.88.1.2.5.1.21,SLAPM-MIB::slapmPolicyRuleStatsActRsvpFlows,Gauge32,read-only,,current,,Current number of active RSVP flows.
.1.3.6.1.3.88.1.2.6,SLAPM-MIB::slapmPRMonTable,,not-accessible,,current,,Provides a method of monitoring policies and their effect at a system.
.1.3.6.1.3.88.1.2.6.1,SLAPM-MIB::slapmPRMonEntry,,not-accessible,slapmPRMonOwnerIndex:slapmPRMonSystemAddress:slapmPRMonIndex,current,,Defines an entry in the slapmPRMonTable. This table defines which policies should be monitored on a per policy rule basis. An attempt to set any read-create object defined within an slapmPRMonEntry while the value of slapmPRMonRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.3.88.1.2.6.1.1,SLAPM-MIB::slapmPRMonOwnerIndex,OCTET,not-accessible,,current,,To facilitate the provisioning of access control by a security administrator using the View-Based Access Control Model (RFC 2575, VACM) for tables in which multiple users may need to independently create or modify entries, the initial index is used as an 'owner index'. Such an initial index has a syntax of SnmpAdminString, and can thus be trivially mapped to a securityName or groupName as defined in VACM, in accordance with a security policy. All entries in that table belonging to a particular user will have the same value for this initial index. For a given user's entries in a particular table, the object identifiers for the information in these entries will have the same subidentifiers (except for the 'column' subidentifier) up to the end of the encoded owner index. To configure VACM to permit access to this portion of the table, one would create vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the column subidentifier. More elaborate configurations are possible.
.1.3.6.1.3.88.1.2.6.1.2,SLAPM-MIB::slapmPRMonSystemAddress,OCTET,not-accessible,,current,,Address of a system that an Policy definition relates to. A zero length octet string can be used to indicate that only a single system is being represented. Otherwise, the length of the octet string should be 4 for an ipv4 address and 16 for an ipv6 address.
.1.3.6.1.3.88.1.2.6.1.3,SLAPM-MIB::slapmPRMonIndex,Unsigned32,not-accessible,,current,,An slapmPolicyNameTable index, slapmPolicyNameIndex, that points to the unique name associated with a policy rule definition.
.1.3.6.1.3.88.1.2.6.1.4,SLAPM-MIB::slapmPRMonControl,BITS,read-create,,current,monitorMinRate(0):monitorMaxRate(1):monitorMaxDelay(2):enableAggregateTraps(3):enableSubcomponentTraps(4):monitorSubcomponents(5),The value of this object determines the type and level of monitoring that is applied to a policy rule. The value of this object can't be changed once the table entry that it is a part of is activated via a slapmPRMonRowStatus transition to active state. monitorMinRate(0) - Monitor minimum transfer rate. monitorMaxRate(1) - Monitor maximum transfer rate. monitorMaxDelay(2) - Monitor maximum delay. enableAggregateTraps(3) - The enableAggregateTraps(3) BITS setting enables notification generation when monitoring a policy rule as an aggregate using the values in the corresponding slapmPRMonStatsEntry. By default this function is not enabled. enableSubcomponentTraps(4) - This BITS setting enables notification generation when monitoring all subcomponents that are mapped to an corresponding slapmPRMonStatsEntry. By default this function is not enabled. monitorSubcomponents(5) - This BITS setting enables monitoring of each subcomponent (typically a TCP connection or UDP listener) individually.
.1.3.6.1.3.88.1.2.6.1.5,SLAPM-MIB::slapmPRMonStatus,BITS,read-only,,current,slaMinInRateNotAchieved(0):slaMaxInRateExceeded(1):slaMaxDelayExceeded(2):slaMinOutRateNotAchieved(3):slaMaxOutRateExceeded(4):monitorMinInRateNotAchieved(5):monitorMaxInRateExceeded(6):monitorMaxDelayExceeded(7):monitorMinOutRateNotAchieved(8):monitorMaxOutRateExceeded(9),The value of this object indicates when a monitored value has not meet a threshold or isn't meeting the defined service level. The SlapmStatus TEXTUAL-CONVENTION defines two levels of not meeting a threshold. The first set: slaMinInRateNotAchieved(0), slaMaxInRateExceeded(1), slaMaxDelayExceeded(2), slaMinOutRateNotAchieved(3), slaMaxOutRateExceeded(4) are used to indicate when the SLA as an aggregate is not meeting a threshold while the second set: monitorMinInRateNotAchieved(5), monitorMaxInRateExceeded(6), monitorMaxDelayExceeded(7), monitorMinOutRateNotAchieved(8), monitorMaxOutRateExceeded(9) indicate that at least one subcomponent is not meeting a threshold.
.1.3.6.1.3.88.1.2.6.1.6,SLAPM-MIB::slapmPRMonInterval,Unsigned32,read-create,,current,,The number of seconds that defines the sample period.
.1.3.6.1.3.88.1.2.6.1.7,SLAPM-MIB::slapmPRMonIntTime,OCTET,read-only,,current,,The timestamp for when the last interval ended.
.1.3.6.1.3.88.1.2.6.1.8,SLAPM-MIB::slapmPRMonCurrentInRate,Gauge32,read-only,,current,,Using the value of the corresponding slapmPRMonInterval, slapmPolicyRuleStatsInOctets is sampled and then divided by slapmPRMonInterval to determine the current in transfer rate.
.1.3.6.1.3.88.1.2.6.1.9,SLAPM-MIB::slapmPRMonCurrentOutRate,Gauge32,read-only,,current,,Using the value of the corresponding slapmPolicyMonInterval, slapmPolicyRuleStatsOutOctets is sampled and then divided by slapmPRMonInterval to determine the current out transfer rate.
.1.3.6.1.3.88.1.2.6.1.10,SLAPM-MIB::slapmPRMonMinRateLow,Unsigned32,read-create,,current,,The threshold for generating a slapmPolicyRuleMonNotOkay notification, signalling that a monitored minimum transfer rate has not been meet. A slapmPolicyRuleMonNotOkay notification is not generated again for an slapmPRMonEntry until the minimum transfer rate exceeds slapmPRMonMinRateHigh (a slapmPolicyRuleMonOkay notification is then transmitted) and then fails below slapmPRMonMinRateLow. This behavior reduces the slapmPolicyRuleMonNotOkay notifications that are transmitted. A value of zero for this object is returned when the slapmPRMonControl monitorMinRate(0) is not enabled. When enabled the default value for this object is the min rate value specified in the associated action definition minus 10%. If the action definition doesn't have a min rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMinRate(0) is selected. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.6.1.11,SLAPM-MIB::slapmPRMonMinRateHigh,Unsigned32,read-create,,current,,The threshold for generating a slapmPolicyRuleMonOkay notification, signalling that a monitored minimum transfer rate has increased to an acceptable level. A value of zero for this object is returned when the slapmPRMonControl monitorMinRate(0) is not enabled. When enabled the default value for this object is the min rate value specified in the associated action definition plus 10%. If the action definition doesn't have a min rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMinRate(0) is selected. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.6.1.12,SLAPM-MIB::slapmPRMonMaxRateHigh,Unsigned32,read-create,,current,,The threshold for generating a slapmPolicyRuleMonNotOkay notification, signalling that a monitored maximum transfer rate has been exceeded. A slapmPolicyRuleNotOkay notification is not generated again for an slapmPRMonEntry until the maximum transfer rate fails below slapmPRMonMaxRateLow (a slapmPolicyRuleMonOkay notification is then transmitted) and then raises above slapmPRMonMaxRateHigh. This behavior reduces the slapmPolicyRuleMonNotOkay notifications that are transmitted. A value of zero for this object is returned when the slapmPRMonControl monitorMaxRate(1) is not enabled. When enabled the default value for this object is the max rate value specified in the associated action definition plus 10%. If the action definition doesn't have a max rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxRate(1) is selected. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.6.1.13,SLAPM-MIB::slapmPRMonMaxRateLow,Unsigned32,read-create,,current,,The threshold for generating a slapmPolicyRuleMonOkay notification, signalling that a monitored maximum transfer rate has fallen to an acceptable level. A value of zero for this object is returned when the slapmPRMonControl monitorMaxRate(1) is not enabled. When enabled the default value for this object is the max rate value specified in the associated action definition minus 10%. If the action definition doesn't have a max rate defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxRate(1) is selected. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.6.1.14,SLAPM-MIB::slapmPRMonMaxDelayHigh,Unsigned32,read-create,,current,,The threshold for generating a slapmPolicyRuleMonNotOkay notification, signalling that a monitored maximum delay rate has been exceeded. A slapmPolicyRuleMonNotOkay notification is not generated again for an slapmPRMonEntry until the maximum delay rate falls below slapmPRMonMaxDelayLow (a slapmPolicyRuleMonOkay notification is then transmitted) and raises above slapmPRMonMaxDelayHigh. This behavior reduces the slapmPolicyRuleMonNotOkay notifications that are transmitted. A value of zero for this object is returned when the slapmPRMonControl monitorMaxDelay(4) is not enabled. When enabled the default value for this object is the max delay value specified in the associated action definition plus 10%. If the action definition doesn't have a max delay defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxDelay(4) is selected. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.6.1.15,SLAPM-MIB::slapmPRMonMaxDelayLow,Unsigned32,read-create,,current,,The threshold for generating a slapmPolicyRuleMonOkay notification, signalling that a monitored maximum delay rate has fallen to an acceptable level. A value of zero for this object is returned when the slapmPRMonControl monitorMaxDelay(4) is not enabled. When enabled the default value for this object is the max delay value specified in the associated action definition minus 10%. If the action definition doesn't have a max delay defined then there is no default for this object and a value MUST be specified prior to activating this entry when monitorMaxDelay(4) is selected. Note: The corresponding slapmPRMonControl BITS setting, enableAggregateTraps(3), MUST be selected in order for any notification relating to this entry to potentially be generated.
.1.3.6.1.3.88.1.2.6.1.16,SLAPM-MIB::slapmPRMonMinInRateNotAchieves,Counter32,read-only,,current,,The number of times that a minimum transfer in rate was not achieved.
.1.3.6.1.3.88.1.2.6.1.17,SLAPM-MIB::slapmPRMonMaxInRateExceeds,Counter32,read-only,,current,,The number of times that a maximum transfer in rate was exceeded.
.1.3.6.1.3.88.1.2.6.1.18,SLAPM-MIB::slapmPRMonMaxDelayExceeds,Counter32,read-only,,current,,The number of times that a maximum delay in rate was exceeded.
.1.3.6.1.3.88.1.2.6.1.19,SLAPM-MIB::slapmPRMonMinOutRateNotAchieves,Counter32,read-only,,current,,The number of times that a minimum transfer out rate was not achieved.
.1.3.6.1.3.88.1.2.6.1.20,SLAPM-MIB::slapmPRMonMaxOutRateExceeds,Counter32,read-only,,current,,The number of times that a maximum transfer out rate was exceeded.
.1.3.6.1.3.88.1.2.6.1.21,SLAPM-MIB::slapmPRMonCurrentDelayRate,Gauge32,read-only,,current,,The current delay rate for this entry. This is calculated by taking the average of the TCP round trip times for all associating slapmSubcomponentTable entries within a interval.
.1.3.6.1.3.88.1.2.6.1.22,SLAPM-MIB::slapmPRMonRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object allows entries to be created and deleted in the slapmPRMonTable. An entry in this table is deleted by setting this object to destroy(6). Removal of an corresponding (same policy index) slapmPolicyRuleStatsEntry has the side effect of the automatic deletion an entry in this table. Note that an attempt to set any read-create object defined within an slapmPRMonEntry while the value of slapmPRMonRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.3.88.2,SLAPM-MIB::slapmConformance,,,,,,
.1.3.6.1.3.88.2.1,SLAPM-MIB::slapmCompliances,,,,,,
.1.3.6.1.3.88.2.1.1,SLAPM-MIB::slapmCompliance,,,,,,The compliance statement for the SLAPM-MIB.
.1.3.6.1.3.88.2.2,SLAPM-MIB::slapmGroups,,,,,,
.1.3.6.1.3.88.2.2.1,SLAPM-MIB::slapmBaseGroup,,,,,,The group of objects defined by this MIB that are required for all implementations to be compliant.
.1.3.6.1.3.88.2.2.2,SLAPM-MIB::slapmOptionalGroup,,,,,,The group of objects defined by this MIB that are optional.
.1.3.6.1.3.88.2.2.3,SLAPM-MIB::slapmEndSystemGroup,,,,,,The group of objects defined by this MIB that are required for end system implementations.
.1.3.6.1.3.88.2.2.4,SLAPM-MIB::slapmNotGroup,,,,,,The group of notifications defined by this MIB that MUST be implemented.
.1.3.6.1.3.88.2.2.5,SLAPM-MIB::slapmEndSystemNotGroup,,,,,,The group of objects defined by this MIB that are required for end system implementations.
.1.3.6.1.3.88.2.2.6,SLAPM-MIB::slapmBaseGroup2,,,,,,The group of objects defined by this MIB that are required for all implementations to be compliant.
.1.3.6.1.3.88.2.2.7,SLAPM-MIB::slapmEndSystemGroup2,,,,,,The group of objects defined by this MIB that are required for end system implementations.
.1.3.6.1.3.88.2.2.8,SLAPM-MIB::slapmNotGroup2,,,,,,The group of notifications defined by this MIB that MUST be implemented.
.1.3.6.1.3.88.2.2.9,SLAPM-MIB::slapmEndSystemNotGroup2,,,,,,The group of objects defined by this MIB that are required for end system implementations.
.1.3.6.1.3.92,MSDP-MIB::msdpMIB,,,,,,An experimental MIB module for MSDP Management and Monitoring. Copyright (C) The Internet Society 2006. This version of this MIB module is part of RFC 4624; see the RFC itself for full legal notices.
.1.3.6.1.3.92.1,MSDP-MIB::msdpMIBobjects,,,,,,
.1.3.6.1.3.92.1.1,MSDP-MIB::msdp,,,,,,
.1.3.6.1.3.92.1.1.0,MSDP-MIB::msdpTraps,,,,,,
.1.3.6.1.3.92.1.1.0.1,MSDP-MIB::msdpEstablished,,,,,,The MSDP Established event is generated when the MSDP FSM enters the ESTABLISHED state.
.1.3.6.1.3.92.1.1.0.2,MSDP-MIB::msdpBackwardTransition,,,,,,The MSDPBackwardTransition Event is generated when the MSDP FSM moves from a higher-numbered state to a lower-numbered state.
.1.3.6.1.3.92.1.1.1,MSDP-MIB::msdpEnabled,INTEGER,read-write,,current,true(1):false(2),The state of MSDP on this MSDP speaker - globally enabled or disabled. Changes to this object should be stored to non-volatile memory.
.1.3.6.1.3.92.1.1.2,MSDP-MIB::msdpCacheLifetime,TimeTicks,read-write,,current,,The lifetime given to SA cache entries when created or refreshed. This is the [SG-State-Period] in the MSDP spec. A value of 0 means no SA caching is done by this MSDP speaker. Changes to this object should be stored to non-volatile memory. This object does not measure time per se; instead, it is the delta from the time at which an SA message is received at which it should be expired if not refreshed. (i.e., it is the value of msdpSACacheExpiryTime immediately after receiving an SA message applying to that row.) As such, TimeInterval would be a more appropriate SYNTAX; it remains TimeTicks for backwards compatibility.
.1.3.6.1.3.92.1.1.3,MSDP-MIB::msdpNumSACacheEntries,Gauge32,read-only,,current,,The total number of entries in the SA Cache table.
.1.3.6.1.3.92.1.1.4,MSDP-MIB::msdpRequestsTable,,not-accessible,,deprecated,,The (conceptual) table listing group ranges and MSDP peers used when deciding where to send an SA Request message, when required. If SA Requests are not enabled, this table may be empty. In order to choose a peer to whom to send an SA Request for a given group, G, the subset of entries in this table whose (msdpRequestsPeerType, msdpRequestsPeer) tuple represents a peer whose msdpPeerState is established are examined. The set is further reduced by examining only those entries for which msdpPeerRequestsGroupAddressType equals the address type of G. The entries with the highest value of msdpRequestsGroupPrefix are considered, where the group G falls within the range described by the combination of msdpRequestsGroup and msdpRequestsGroupPrefix. (This sequence is commonly known as a 'longest-match' lookup.) Finally, if multiple entries remain, the entry with the lowest value of msdpRequestsPriority is chosen. The SA Request message is sent to the peer described by this row.
.1.3.6.1.3.92.1.1.4.1,MSDP-MIB::msdpRequestsEntry,,not-accessible,msdpRequestsGroupAddress:msdpRequestsGroupMask,deprecated,,An entry (conceptual row) representing a group range used when deciding where to send an SA Request message.
.1.3.6.1.3.92.1.1.4.1.1,MSDP-MIB::msdpRequestsGroupAddress,IpAddress,not-accessible,,deprecated,,The group address that, when combined with the mask in this entry, represents the group range to which this row applies.
.1.3.6.1.3.92.1.1.4.1.2,MSDP-MIB::msdpRequestsGroupMask,IpAddress,not-accessible,,deprecated,,The mask that, when combined with the group address in this entry, represents the group range to which this row applies.
.1.3.6.1.3.92.1.1.4.1.3,MSDP-MIB::msdpRequestsPeer,IpAddress,read-create,,deprecated,,The peer to which MSDP SA Requests for groups matching this entry's group range will be sent. This object, combined with msdpRequestsPeerType, must match the INDEX of a row in the msdpPeerTable, and to be considered, this peer's msdpPeerState must be established.
.1.3.6.1.3.92.1.1.4.1.4,MSDP-MIB::msdpRequestsStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new rows may be added to the table or old rows may be deleted.
.1.3.6.1.3.92.1.1.5,MSDP-MIB::msdpPeerTable,,not-accessible,,current,,The (conceptual) table listing the MSDP speaker's peers.
.1.3.6.1.3.92.1.1.5.1,MSDP-MIB::msdpPeerEntry,,not-accessible,msdpPeerRemoteAddress,current,,An entry (conceptual row) representing an MSDP peer. If row creation is supported, dynamically added rows are added to the system's stable configuration (corresponding to a StorageType value of nonVolatile). 
.1.3.6.1.3.92.1.1.5.1.1,MSDP-MIB::msdpPeerRemoteAddress,IpAddress,not-accessible,,current,,The address of the remote MSDP peer.
.1.3.6.1.3.92.1.1.5.1.3,MSDP-MIB::msdpPeerState,INTEGER,read-only,,current,inactive(1):listen(2):connecting(3):established(4):disabled(5),The state of the MSDP TCP connection with this peer.
.1.3.6.1.3.92.1.1.5.1.4,MSDP-MIB::msdpPeerRPFFailures,Counter32,read-only,,current,,The number of SA messages received from this peer that failed the Peer-RPF check. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.5,MSDP-MIB::msdpPeerInSAs,Counter32,read-only,,current,,The number of MSDP SA messages received on this connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.6,MSDP-MIB::msdpPeerOutSAs,Counter32,read-only,,current,,The number of MSDP SA messages transmitted on this connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.7,MSDP-MIB::msdpPeerInSARequests,Counter32,read-only,,current,,The number of MSDP SA-Request messages received on this connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.8,MSDP-MIB::msdpPeerOutSARequests,Counter32,read-only,,current,,The number of MSDP SA-Request messages transmitted on this connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.9,MSDP-MIB::msdpPeerInSAResponses,Counter32,read-only,,deprecated,,The number of MSDP SA-Response messages received on this connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.10,MSDP-MIB::msdpPeerOutSAResponses,Counter32,read-only,,deprecated,,The number of MSDP SA Response messages transmitted on this TCP connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.11,MSDP-MIB::msdpPeerInControlMessages,Counter32,read-only,,current,,The total number of MSDP messages, excluding encapsulated data packets, received on this TCP connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.12,MSDP-MIB::msdpPeerOutControlMessages,Counter32,read-only,,current,,The total number of MSDP messages, excluding encapsulated data packets, transmitted on this TCP connection. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.13,MSDP-MIB::msdpPeerInDataPackets,Counter32,read-only,,current,,The total number of encapsulated data packets received from this peer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.14,MSDP-MIB::msdpPeerOutDataPackets,Counter32,read-only,,current,,The total number of encapsulated data packets sent to this peer. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of msdpPeerDiscontinuityTime.
.1.3.6.1.3.92.1.1.5.1.15,MSDP-MIB::msdpPeerFsmEstablishedTransitions,Counter32,read-only,,current,,The total number of times the MSDP FSM transitioned into the ESTABLISHED state.
.1.3.6.1.3.92.1.1.5.1.16,MSDP-MIB::msdpPeerFsmEstablishedTime,TimeTicks,read-only,,current,,This timestamp is set to the value of sysUpTime when a peer transitions into or out of the ESTABLISHED state. It is set to zero when the MSDP speaker is booted.
.1.3.6.1.3.92.1.1.5.1.17,MSDP-MIB::msdpPeerInMessageTime,TimeTicks,read-only,,current,,The sysUpTime value when the last MSDP message was received from the peer. It is set to zero when the MSDP speaker is booted.
.1.3.6.1.3.92.1.1.5.1.18,MSDP-MIB::msdpPeerLocalAddress,IpAddress,read-create,,current,,The local IP address used for this entry's MSDP TCP connection.
.1.3.6.1.3.92.1.1.5.1.20,MSDP-MIB::msdpPeerConnectRetryInterval,Integer32,read-create,,current,,Time interval, in seconds, for the [ConnectRetry-period] for this peer.
.1.3.6.1.3.92.1.1.5.1.21,MSDP-MIB::msdpPeerHoldTimeConfigured,Integer32,read-create,,current,,Time interval, in seconds, for the [HoldTime-Period] configured for this MSDP speaker with this peer. If the value of this object is zero (0), the MSDP connection is never torn down due to the absence of messages from the peer.
.1.3.6.1.3.92.1.1.5.1.22,MSDP-MIB::msdpPeerKeepAliveConfigured,Integer32,read-create,,current,,Time interval, in seconds, for the [KeepAlive-Period] configured for this MSDP speaker with this peer. If the value of this object is zero (0), no periodic KEEPALIVE messages are sent to the peer after the MSDP connection has been established.
.1.3.6.1.3.92.1.1.5.1.23,MSDP-MIB::msdpPeerDataTtl,Integer32,read-create,,current,,The minimum TTL a packet is required to have before it may be forwarded using SA encapsulation to this peer.
.1.3.6.1.3.92.1.1.5.1.24,MSDP-MIB::msdpPeerProcessRequestsFrom,INTEGER,read-create,,deprecated,true(1):false(2),This object indicates whether to process MSDP SA Request messages from this peer. If True(1), MSDP SA Request messages from this peer are processed and replied to (if appropriate) with SA Response messages. If False(2), MSDP SA Request messages from this peer are silently ignored. It defaults to False when msdpCacheLifetime is 0 and to True when msdpCacheLifetime is non-0. This object is deprecated because MSDP SA Requests were removed from the MSDP specification.
.1.3.6.1.3.92.1.1.5.1.25,MSDP-MIB::msdpPeerStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The RowStatus object by which peers can be added and deleted. A transition to 'active' will cause the MSDP 'Enable MSDP peering with P' Event to be generated. A transition out of the 'active' state will cause the MSDP 'Disable MSDP peering with P' Event to be generated. Care should be used in providing write access to this object without adequate authentication. msdpPeerRemoteAddress is the only variable that must be set to a valid value before the row can be activated. Since this is the table's INDEX, a row can be activated by simply setting the msdpPeerStatus variable. It is possible to modify other columns in the same conceptual row when the status value is active(1).
.1.3.6.1.3.92.1.1.5.1.26,MSDP-MIB::msdpPeerRemotePort,Integer32,read-only,,current,,The remote port for the TCP connection between the MSDP peers.
.1.3.6.1.3.92.1.1.5.1.27,MSDP-MIB::msdpPeerLocalPort,Integer32,read-only,,current,,The local port for the TCP connection between the MSDP peers.
.1.3.6.1.3.92.1.1.5.1.29,MSDP-MIB::msdpPeerEncapsulationType,INTEGER,read-create,,current,none(0):tcp(1),The encapsulation in use when encapsulating data in SA messages to this peer.
.1.3.6.1.3.92.1.1.5.1.30,MSDP-MIB::msdpPeerConnectionAttempts,Counter32,read-only,,current,,The number of times the state machine has transitioned from INACTIVE to CONNECTING.
.1.3.6.1.3.92.1.1.5.1.31,MSDP-MIB::msdpPeerInNotifications,Counter32,read-only,,deprecated,,The number of MSDP Notification messages received from this peer. This object is deprecated because MSDP Notifications have been removed from the spec.
.1.3.6.1.3.92.1.1.5.1.32,MSDP-MIB::msdpPeerOutNotifications,Counter32,read-only,,deprecated,,The number of MSDP Notification messages transmitted to this peer. This object is deprecated because MSDP Notifications have been removed from the spec.
.1.3.6.1.3.92.1.1.5.1.33,MSDP-MIB::msdpPeerLastError,OCTET,read-only,,deprecated,,The last error code and subcode received via Notification from this peer. If no error has occurred, this field is zero. Otherwise, the first byte of this two-byte OCTET STRING contains the O-bit and error code, and the second byte contains the subcode. This object is deprecated because MSDP Notifications have been removed from the spec.
.1.3.6.1.3.92.1.1.5.1.34,MSDP-MIB::msdpPeerDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which one or more of this entry's counters suffered a discontinuity. See the DESCRIPTION of each object to see if it is expected to have discontinuities. These discontinuities may occur at peer connection establishment. If no such discontinuities have occurred since the last reinitialization of the local management subsystem, then this object contains a zero value.
.1.3.6.1.3.92.1.1.6,MSDP-MIB::msdpSACacheTable,,not-accessible,,current,,The (conceptual) table listing the MSDP SA advertisements currently in the MSDP speaker's cache.
.1.3.6.1.3.92.1.1.6.1,MSDP-MIB::msdpSACacheEntry,,not-accessible,msdpSACacheGroupAddr:msdpSACacheSourceAddr:msdpSACacheOriginRP,current,,An entry (conceptual row) representing an MSDP SA advertisement. The INDEX to this table includes msdpSACacheOriginRP for diagnosing incorrect MSDP advertisements; normally, a Group and Source pair would be unique. Row creation is not permitted; msdpSACacheStatus may only be used to delete rows from this table.
.1.3.6.1.3.92.1.1.6.1.1,MSDP-MIB::msdpSACacheGroupAddr,IpAddress,not-accessible,,current,,The group address of the SA Cache entry.
.1.3.6.1.3.92.1.1.6.1.2,MSDP-MIB::msdpSACacheSourceAddr,IpAddress,not-accessible,,current,,The source address of the SA Cache entry.
.1.3.6.1.3.92.1.1.6.1.3,MSDP-MIB::msdpSACacheOriginRP,IpAddress,not-accessible,,current,,The RP of the SA Cache entry. This field is in the INDEX in order to catch multiple RP's advertising the same source and group.
.1.3.6.1.3.92.1.1.6.1.4,MSDP-MIB::msdpSACachePeerLearnedFrom,IpAddress,read-only,,current,,The peer from which this SA Cache entry was last accepted. This address must correspond to the msdpPeerRemoteAddress value for a row in the MSDP Peer Table. This should be 0.0.0.0 on the router that originated the entry.
.1.3.6.1.3.92.1.1.6.1.5,MSDP-MIB::msdpSACacheRPFPeer,IpAddress,read-only,,current,,The peer from which an SA message corresponding to this cache entry would be accepted (i.e., the RPF peer for msdpSACacheOriginRP). This may be different than msdpSACachePeerLearnedFrom if this entry was created by an MSDP SA-Response. This address must correspond to the msdpPeerRemoteAddress value for a row in the MSDP Peer Table, or it may be 0.0.0.0 if no RPF peer exists.
.1.3.6.1.3.92.1.1.6.1.6,MSDP-MIB::msdpSACacheInSAs,Counter32,read-only,,current,,The number of MSDP SA messages received relevant to this cache entry. This object must be initialized to zero when creating a cache entry.
.1.3.6.1.3.92.1.1.6.1.7,MSDP-MIB::msdpSACacheInDataPackets,Counter32,read-only,,current,,The number of MSDP-encapsulated data packets received relevant to this cache entry. This object must be initialized to zero when creating a cache entry.
.1.3.6.1.3.92.1.1.6.1.8,MSDP-MIB::msdpSACacheUpTime,TimeTicks,read-only,,current,,The time since this entry was first placed in the SA cache. The first epoch is the time that the entry was first placed in the SA cache, and the second epoch is the current time.
.1.3.6.1.3.92.1.1.6.1.9,MSDP-MIB::msdpSACacheExpiryTime,TimeTicks,read-only,,current,,The time remaining before this entry will expire from the SA cache. The first epoch is now, and the second epoch is the time that the entry will expire.
.1.3.6.1.3.92.1.1.6.1.10,MSDP-MIB::msdpSACacheStatus,INTEGER,read-write,,current,active(1):destroy(6),The status of this row in the table. The only allowable actions are to retrieve the status, which will be 'active', or to set the status to 'destroy' in order to remove this entry from the cache. Row creation is not permitted. No columnar objects are writable, so there are none that may be changed while the status value is active(1).
.1.3.6.1.3.92.1.1.8,MSDP-MIB::msdpMIBConformance,,,,,,
.1.3.6.1.3.92.1.1.8.1,MSDP-MIB::msdpMIBCompliances,,,,,,
.1.3.6.1.3.92.1.1.8.1.1,MSDP-MIB::msdpMIBCompliance,,,,,,The compliance statement for entities that implement a pre- RFC version of MSDP. This statement is deprecated because it includes objects used for managing/monitoring aspects of MSDP that were removed before it was published as an RFC.
.1.3.6.1.3.92.1.1.8.1.2,MSDP-MIB::msdpMIBFullCompliance,,,,,,The compliance statement for entities that implement MSDP (RFC3618).
.1.3.6.1.3.92.1.1.8.1.3,MSDP-MIB::msdpMIBReadOnlyCompliance,,,,,,The compliance statement for entities that implement MSDP (RFC3618), but do not permit configuration (or only permit partial configuration) via SNMP.
.1.3.6.1.3.92.1.1.8.2,MSDP-MIB::msdpMIBGroups,,,,,,
.1.3.6.1.3.92.1.1.8.2.1,MSDP-MIB::msdpMIBGlobalsGroup,,,,,,A collection of objects providing information on global MSDP state.
.1.3.6.1.3.92.1.1.8.2.2,MSDP-MIB::msdpMIBPeerGroup,,,,,,A collection of objects for managing MSDP peers. This group is deprecated in favor of msdpMIBPeerGroup2 because it contains objects for managing aspects of MSDP that were removed before it was published as an RFC.
.1.3.6.1.3.92.1.1.8.2.3,MSDP-MIB::msdpMIBEncapsulationGroup,,,,,,A collection of objects for managing encapsulations if the MSDP encapsulation interfaces are not given interface indices.
.1.3.6.1.3.92.1.1.8.2.4,MSDP-MIB::msdpMIBSACacheGroup,,,,,,A collection of objects for managing MSDP SA cache entries.
.1.3.6.1.3.92.1.1.8.2.5,MSDP-MIB::msdpMIBNotificationGroup,,,,,,A collection of notifications for signaling changes in MSDP peer relationships.
.1.3.6.1.3.92.1.1.8.2.6,MSDP-MIB::msdpMIBRequestsGroup,,,,,,A collection of objects for managing MSDP Request transmission. This group is deprecated because Requests were removed from MSDP before its publication as an RFC.
.1.3.6.1.3.92.1.1.8.2.7,MSDP-MIB::msdpMIBRPGroup,,,,,,A collection of objects for MSDP speakers that source MSDP messages.
.1.3.6.1.3.92.1.1.8.2.8,MSDP-MIB::msdpMIBMeshGroupGroup,,,,,,A collection of objects for MSDP speakers that can participate in MSDP mesh groups.
.1.3.6.1.3.92.1.1.8.2.9,MSDP-MIB::msdpMIBPeerGroup2,,,,,,A collection of objects for managing MSDP peers.
.1.3.6.1.3.92.1.1.11,MSDP-MIB::msdpRPAddress,IpAddress,read-write,,current,,The Rendezvous Point (RP) address used when sourcing MSDP SA messages. May be 0.0.0.0 on non-RPs. Changes to this object should be stored to non-volatile memory.
.1.3.6.1.3.92.1.1.12,MSDP-MIB::msdpMeshGroupTable,,not-accessible,,current,,The (conceptual) table listing MSDP Mesh Group configuration.
.1.3.6.1.3.92.1.1.12.1,MSDP-MIB::msdpMeshGroupEntry,,not-accessible,msdpMeshGroupName:msdpMeshGroupPeerAddress,current,,An entry (conceptual row) representing a peer in an MSDP Mesh Group. If row creation is supported, dynamically added rows are added to the system's stable configuration (corresponding to a StorageType value of nonVolatile).
.1.3.6.1.3.92.1.1.12.1.1,MSDP-MIB::msdpMeshGroupName,OCTET,not-accessible,,current,,The name of the mesh group.
.1.3.6.1.3.92.1.1.12.1.2,MSDP-MIB::msdpMeshGroupPeerAddress,IpAddress,not-accessible,,current,,A peer address that is a member of the mesh group with name msdpMeshGroupName. The msdpMeshGroupPeerAddress must match a row in the msdpPeerTable.
.1.3.6.1.3.92.1.1.12.1.3,MSDP-MIB::msdpMeshGroupStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This entry's status, by which new entries may be added to the table and old entries deleted. msdpMeshGroupName and msdpMeshGroupPeerAddress must be set to valid values before the row can be activated. Since these are the table's INDEX, a row can be activated by simply setting the msdpMeshGroupStatus variable. It is not possible to modify other columns in the same conceptual row when the status value is active(1), because the only other objects in the row are part of the INDEX. Changing one of these changes the row, so an old row must be deleted and a new one created.
.1.3.6.1.3.101,SNMP-USM-DH-OBJECTS-MIB::snmpUsmDHObjectsMIB,,,,,,The management information definitions for providing forward secrecy for key changes for the usmUserTable, and for providing a method for 'kickstarting' access to the agent via a Diffie-Helman key agreement.
.1.3.6.1.3.101.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyObjects,,,,,,
.1.3.6.1.3.101.1.1,SNMP-USM-DH-OBJECTS-MIB::usmDHPublicObjects,,,,,,
.1.3.6.1.3.101.1.1.1,SNMP-USM-DH-OBJECTS-MIB::usmDHParameters,OCTET,read-write,,current,,The public Diffie-Hellman parameters for doing a Diffie-Hellman key agreement for this device. This is encoded as an ASN.1 DHParameter per PKCS #3, section 9. E.g. DHParameter ::= SEQUENCE { prime INTEGER, -- p base INTEGER, -- g privateValueLength INTEGER OPTIONAL } Implementors are encouraged to use either the values from Oakley Group 1 or the values of from Oakley Group 2 as specified in RFC-2409, The Internet Key Exchange, Section 6.1, 6.2 as the default for this object. Other values may be used, but the security properties of those values MUST be well understood and MUST meet the requirements of PKCS #3 for the selection of Diffie-Hellman primes. In addition, any time usmDHParameters changes, all values of type DHKeyChange will change and new random numbers MUST be generated by the agent for each DHKeyChange object.
.1.3.6.1.3.101.1.1.2,SNMP-USM-DH-OBJECTS-MIB::usmDHUserKeyTable,,not-accessible,,current,,This table augments and extends the usmUserTable and provides 4 objects which exactly mirror the objects in that table with the textual convention of 'KeyChange'. This extension allows key changes to be done in a manner where the knowledge of the current secret plus knowledge of the key change data exchanges (e.g. via wiretapping) will not reveal the new key.
.1.3.6.1.3.101.1.1.2.1,SNMP-USM-DH-OBJECTS-MIB::usmDHUserKeyEntry,,not-accessible,,current,,A row of DHKeyChange objects which augment or replace the functionality of the KeyChange objects in the base table row.
.1.3.6.1.3.101.1.1.2.1.1,SNMP-USM-DH-OBJECTS-MIB::usmDHUserAuthKeyChange,OCTET,read-create,,current,,The object used to change any given user's Authentication Key using a Diffie-Hellman key exchange. The right-most n bits of the shared secret 'sk', where 'n' is the number of bits required for the protocol defined by usmUserAuthProtocol, are installed as the operational authentication key for this row after a successful SET.
.1.3.6.1.3.101.1.1.2.1.2,SNMP-USM-DH-OBJECTS-MIB::usmDHUserOwnAuthKeyChange,OCTET,read-create,,current,,The object used to change the agents own Authentication Key using a Diffie-Hellman key exchange. The right-most n bits of the shared secret 'sk', where 'n' is the number of bits required for the protocol defined by usmUserAuthProtocol, are installed as the operational authentication key for this row after a successful SET.
.1.3.6.1.3.101.1.1.2.1.3,SNMP-USM-DH-OBJECTS-MIB::usmDHUserPrivKeyChange,OCTET,read-create,,current,,The object used to change any given user's Privacy Key using a Diffie-Hellman key exchange. The right-most n bits of the shared secret 'sk', where 'n' is the number of bits required for the protocol defined by usmUserPrivProtocol, are installed as the operational privacy key for this row after a successful SET.
.1.3.6.1.3.101.1.1.2.1.4,SNMP-USM-DH-OBJECTS-MIB::usmDHUserOwnPrivKeyChange,OCTET,read-create,,current,,The object used to change the agent's own Privacy Key using a Diffie-Hellman key exchange. The right-most n bits of the shared secret 'sk', where 'n' is the number of bits required for the protocol defined by usmUserPrivProtocol, are installed as the operational privacy key for this row after a successful SET.
.1.3.6.1.3.101.1.2,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartGroup,,,,,,
.1.3.6.1.3.101.1.2.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartTable,,not-accessible,,current,,A table of mappings between zero or more Diffie-Helman key agreement values and entries in the usmUserTable. Entries in this table are created by providing the associated device with a Diffie-Helman public value and a usmUserName/usmUserSecurityName pair during initialization. How these values are provided is outside the scope of this MIB, but could be provided manually, or through a configuration file. Valid public value/name pairs result in the creation of a row in this table as well as the creation of an associated row (with keys derived as indicated) in the usmUserTable. The actual access the related usmSecurityName has is dependent on the entries in the VACM tables. In general, an implementor will specify one or more standard security names and will provide entries in the VACM tables granting various levels of access to those names. The actual content of the VACM table is beyond the scope of this MIB. Note: This table is expected to be readable without authentication using the usmUserSecurityName 'dhKickstart'. See the conformance statements for details.
.1.3.6.1.3.101.1.2.1.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartEntry,,not-accessible,usmDHKickstartIndex,current,,An entry in the usmDHKickstartTable. The agent SHOULD either delete this entry or mark it as inactive upon a successful SET of any of the KeyChange-typed objects in the usmUserEntry or upon a successful SET of any of the DHKeyChange-typed objects in the usmDhKeyChangeEntry where the related usmSecurityName (e.g. row of usmUserTable or row of ushDhKeyChangeTable) equals this entry's usmDhKickstartSecurityName. In otherwords, once you've changed one or more of the keys for a row in usmUserTable with a particular security name, the row in this table with that same security name is no longer useful or meaningful.
.1.3.6.1.3.101.1.2.1.1.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartIndex,Integer32,not-accessible,,current,,Index value for this row.
.1.3.6.1.3.101.1.2.1.1.2,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartMyPublic,OCTET,read-only,,current,,The agent's Diffie-Hellman public value for this row. At initialization, the agent generates a random number and derives its public value from that number. This public value is published here. This public value 'y' equals g^r MOD p where g is the from the set of Diffie-Hellman parameters, p is the prime from those parameters, and r is a random integer selected by the agent in the interval 2^(l-1) <= r < p-1 < 2^l. If l is unspecified, then r is a random integer selected in the interval 0 <= r < p-1 The public value is expressed as an OCTET STRING 'PV' of length 'k' which satisfies k y = SUM 2^(8(k-i)) PV'i i = 1 where PV1,...,PVk are the octets of PV from first to last, and where PV1 != 0. The following DH parameters (Oakley group #2, RFC 2409, sec 6.1, 6.2) are used for this object: g = 2 p = FFFFFFFF FFFFFFFF C90FDAA2 2168C234 C4C6628B 80DC1CD1 29024E08 8A67CC74 020BBEA6 3B139B22 514A0879 8E3404DD EF9519B3 CD3A431B 302B0A6D F25F1437 4FE1356D 6D51C245 E485B576 625E7EC6 F44C42E9 A637ED6B 0BFF5CB6 F406B7ED EE386BFB 5A899FA5 AE9F2411 7C4B1FE6 49286651 ECE65381 FFFFFFFF FFFFFFFF l=1024 
.1.3.6.1.3.101.1.2.1.1.3,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartMgrPublic,OCTET,read-only,,current,,The manager's Diffie-Hellman public value for this row. Note that this value is not set via the SNMP agent, but may be set via some out of band method, such as the device's configuration file. The manager calculates this value in the same manner and using the same parameter set as the agent does. E.g. it selects a random number 'r', calculates y = g^r mod p and provides 'y' as the public number expressed as an OCTET STRING. See usmDHKickstartMyPublic for details. When this object is set with a valid value during initialization, a row is created in the usmUserTable with the following values: usmUserEngineID localEngineID usmUserName [value of usmDHKickstartSecurityName] usmUserSecurityName [value of usmDHKickstartSecurityName] usmUserCloneFrom ZeroDotZero usmUserAuthProtocol usmHMACMD5AuthProtocol usmUserAuthKeyChange -- derived from set value usmUserOwnAuthKeyChange -- derived from set value usmUserPrivProtocol usmDESPrivProtocol usmUserPrivKeyChange -- derived from set value usmUserOwnPrivKeyChange -- derived from set value usmUserPublic '' usmUserStorageType permanent usmUserStatus active A shared secret 'sk' is calculated at the agent as sk = mgrPublic^r mod p where r is the agents random number and p is the DH prime from the common parameters. The underlying privacy key for this row is derived from sk by applying the key derivation function PBKDF2 defined in PKCS#5v2.0 with a salt of 0xd1310ba6, and iterationCount of 500, a keyLength of 16 (for usmDESPrivProtocol), and a prf (pseudo random function) of 'id-hmacWithSHA1'. The underlying authentication key for this row is derived from sk by applying the key derivation function PBKDF2 with a salt of 0x98dfb5ac , an interation count of 500, a keyLength of 16 (for usmHMAC5AuthProtocol), and a prf of 'id-hmacWithSHA1'. Note: The salts are the first two words in the ks0 [key schedule 0] of the BLOWFISH cipher from 'Applied Cryptography' by Bruce Schnier - they could be any relatively random string of bits. The manager can use its knowledge of its own random number and the agent's public value to kickstart its access to the agent in a secure manner. Note that the security of this approach is directly related to the strength of the authorization security of the out of band provisioning of the managers public value (e.g. the configuration file), but is not dependent at all on the strength of the confidentiality of the out of band provisioning data.
.1.3.6.1.3.101.1.2.1.1.4,SNMP-USM-DH-OBJECTS-MIB::usmDHKickstartSecurityName,OCTET,read-only,,current,,The usmUserName and usmUserSecurityName in the usmUserTable associated with this row. This is provided in the same manner and at the same time as the usmDHKickstartMgrPublic value - e.g. possibly manually, or via the device's configuration file.
.1.3.6.1.3.101.2,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyConformance,,,,,,
.1.3.6.1.3.101.2.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyMIBCompliances,,,,,,
.1.3.6.1.3.101.2.1.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyMIBCompliance,,,,,,The compliance statement for this module.
.1.3.6.1.3.101.2.2,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyMIBGroups,,,,,,
.1.3.6.1.3.101.2.2.1,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyMIBBasicGroup,,,,,,
.1.3.6.1.3.101.2.2.2,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyParamGroup,,,,,,The mandatory object for all MIBs which use the DHKeyChange textual convention.
.1.3.6.1.3.101.2.2.3,SNMP-USM-DH-OBJECTS-MIB::usmDHKeyKickstartGroup,,,,,,The objects used for kickstarting one or more SNMPv3 USM associations via a configuration file or other out of band, non-confidential access.
.1.3.6.1.3.123,AGGREGATE-MIB::aggrMIB,,,,,,The MIB for servicing aggregate objects. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4498; see the RFC itself for full legal notices. 
.1.3.6.1.3.123.1,AGGREGATE-MIB::aggrCtlTable,,not-accessible,,current,,A table that controls the aggregation of the MOs.
.1.3.6.1.3.123.1.1,AGGREGATE-MIB::aggrCtlEntry,,not-accessible,aggrCtlEntryID,current,,A row of the control table that defines one aggregated MO. Entries in this table are required to survive a reboot of the managed entity depending on the value of the corresponding aggrCtlEntryStorageType instance. 
.1.3.6.1.3.123.1.1.1,AGGREGATE-MIB::aggrCtlEntryID,OCTET,not-accessible,,current,,A locally unique, administratively assigned name for this aggregated MO. It is used as an index to uniquely identify this row in the table.
.1.3.6.1.3.123.1.1.2,AGGREGATE-MIB::aggrCtlMOIndex,Unsigned32,read-create,,current,,A pointer to a group of MOs identified by aggrMOEntryID in the aggrMOTable. This is the group of MOs that will be aggregated.
.1.3.6.1.3.123.1.1.3,AGGREGATE-MIB::aggrCtlMODescr,OCTET,read-create,,current,,A textual description of the object that is being aggregated.
.1.3.6.1.3.123.1.1.4,AGGREGATE-MIB::aggrCtlCompressionAlgorithm,INTEGER,read-create,,current,none(1):deflate(2),The compression algorithm that will be used by the agent to compress the value of the aggregated object. The deflate algorithm and corresponding data format specification is described in RFC 1951. It is compatible with the widely used gzip utility. 
.1.3.6.1.3.123.1.1.5,AGGREGATE-MIB::aggrCtlEntryOwner,OCTET,read-create,,current,,The entity that created this entry.
.1.3.6.1.3.123.1.1.6,AGGREGATE-MIB::aggrCtlEntryStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether the parameters defined in this row are kept in volatile storage and lost upon reboot or backed up by non-volatile (permanent) storage. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.3.123.1.1.7,AGGREGATE-MIB::aggrCtlEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to row installation and removal conventions. Objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row, a. change the row status to 'notInService', b. change the values of the row, and c. change the row status to 'active'. The aggrCtlEntryStatus may be changed to 'active' if all the MOs in the conceptual row have been assigned valid values. 
.1.3.6.1.3.123.2,AGGREGATE-MIB::aggrMOTable,,not-accessible,,current,,The table of primary(simple) MOs that will be aggregated. Each row in this table represents a MO that will be aggregated. The aggrMOEntryID index is used to identify the group of MOs that will be aggregated. The aggrMOIndex instance in the corresponding row of the aggrCtlTable will have a value equal to the value of aggrMOEntryID. The aggrMOEntryMOID index is used to identify an MO in the group. 
.1.3.6.1.3.123.2.1,AGGREGATE-MIB::aggrMOEntry,,not-accessible,aggrMOEntryID:aggrMOEntryMOID,current,,A row of the table that specifies one MO. Entries in this table are required to survive a reboot of the managed entity depending on the value of the corresponding aggrMOEntryStorageType instance. 
.1.3.6.1.3.123.2.1.1,AGGREGATE-MIB::aggrMOEntryID,Unsigned32,not-accessible,,current,,An index uniquely identifying a group of MOs that will be aggregated.
.1.3.6.1.3.123.2.1.2,AGGREGATE-MIB::aggrMOEntryMOID,Unsigned32,not-accessible,,current,,An index to uniquely identify an MO instance in the group of MO instances that will be aggregated.
.1.3.6.1.3.123.2.1.3,AGGREGATE-MIB::aggrMOInstance,OBJECT,read-create,,current,,The OID of the MO instance, the value of which will be sampled by the agent.
.1.3.6.1.3.123.2.1.4,AGGREGATE-MIB::aggrMODescr,OCTET,read-create,,current,,A textual description of the object that will be aggregated.
.1.3.6.1.3.123.2.1.5,AGGREGATE-MIB::aggrMOEntryStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether the parameters defined in this row are kept in volatile storage and lost upon reboot or backed up by non-volatile (permanent) storage. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.3.123.2.1.6,AGGREGATE-MIB::aggrMOEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to row installation and removal conventions. Objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row, a. change the row status to 'notInService', b. change the values of the row, and c. change the row status to 'active'. The aggrMOEntryStatus may be changed to 'active' iff all the MOs in the conceptual row have been assigned valid values. 
.1.3.6.1.3.123.3,AGGREGATE-MIB::aggrDataTable,,not-accessible,,current,,Each row of this table contains information about an aggregateMO indexed by aggrCtlEntryID.
.1.3.6.1.3.123.3.1,AGGREGATE-MIB::aggrDataEntry,,not-accessible,aggrCtlEntryID,current,,Entry containing information pertaining to an aggregate MO.
.1.3.6.1.3.123.3.1.1,AGGREGATE-MIB::aggrDataRecord,Opaque,read-only,,current,,The snapshot value of the aggregated MO. Note that the access privileges to this object will be governed by the access privileges of the component objects. Thus, an entity attempting to access an instance of this MO MUST have access rights to all the component instance objects and this MO instance. 
.1.3.6.1.3.123.3.1.2,AGGREGATE-MIB::aggrDataRecordCompressed,OCTET,read-only,,current,,The compressed value of the aggregated MO. The compression algorithm will depend on the aggrCtlCompressionAlgorithm given in the corresponding aggrCtlEntry. If the value of the corresponding aggrCtlCompressionAlgorithm is (1) 'none', then the value of all instances of this object will be a string of zero length. Note that the access privileges to this object will be governed by the access privileges of the component objects. Thus, an entity attempting to access an instance of this MO MUST have access rights to all the component instance objects and this MO instance. 
.1.3.6.1.3.123.3.1.3,AGGREGATE-MIB::aggrDataErrorRecord,Opaque,read-only,,current,,The error status corresponding to the MO instances aggregated in aggrDataRecord (and aggrDataRecordCompressed).
.1.3.6.1.3.123.4,AGGREGATE-MIB::aggrConformance,,,,,,
.1.3.6.1.3.123.4.1,AGGREGATE-MIB::aggrGroups,,,,,,
.1.3.6.1.3.123.4.1.1,AGGREGATE-MIB::aggrMibBasicGroup,,,,,,A collection of objects for aggregation of MOs.
.1.3.6.1.3.123.4.2,AGGREGATE-MIB::aggrCompliances,,,,,,
.1.3.6.1.3.123.4.2.1,AGGREGATE-MIB::aggrMibCompliance,,,,,,The compliance statement for SNMP entities that implement the AGGREGATE-MIB.
.1.3.6.1.3.124,TIME-AGGREGATE-MIB::tAggrMIB,,,,,,The MIB for servicing Time-Based aggregate objects. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4498; see the RFC itself for full legal notices. 
.1.3.6.1.3.124.1,TIME-AGGREGATE-MIB::tAggrCtlTable,,not-accessible,,current,,The Time-Based aggregation control table. It controls the aggregation of the samples of MO instances. There will be a row for each TAgMO. 
.1.3.6.1.3.124.1.1,TIME-AGGREGATE-MIB::tAggrCtlEntry,,not-accessible,tAggrCtlEntryID,current,,A row of the control table that defines one Time-Based aggregate MO (TAgMO).
.1.3.6.1.3.124.1.1.1,TIME-AGGREGATE-MIB::tAggrCtlEntryID,OCTET,not-accessible,,current,,A locally unique, administratively assigned name for this aggregated MO. It is used as an index to uniquely identify this row in the table.
.1.3.6.1.3.124.1.1.2,TIME-AGGREGATE-MIB::tAggrCtlMOInstance,OBJECT,read-create,,current,,The sampled values of this MO instance will be aggregated by the TAgMO. 
.1.3.6.1.3.124.1.1.3,TIME-AGGREGATE-MIB::tAggrCtlAgMODescr,OCTET,read-create,,current,,A textual description of the aggregate object.
.1.3.6.1.3.124.1.1.4,TIME-AGGREGATE-MIB::tAggrCtlInterval,Integer32,read-create,,current,,The interval, in microseconds, at which the MO instance pointed at by tAggrInstance will be sampled for Time-Based aggregation. 
.1.3.6.1.3.124.1.1.5,TIME-AGGREGATE-MIB::tAggrCtlSamples,Integer32,read-create,,current,,The number of times at which the MO instance referred to by tAggrInstance will be sampled for Time-Based aggregation.
.1.3.6.1.3.124.1.1.6,TIME-AGGREGATE-MIB::tAggrCtlCompressionAlgorithm,INTEGER,read-create,,current,none(1):deflate(2),The compression algorithm that will be used by the agent to compress the value of the TAgMO. The deflate algorithm and corresponding data format specification is described in RFC 1951. It is compatible with the widely used gzip utility. 
.1.3.6.1.3.124.1.1.7,TIME-AGGREGATE-MIB::tAggrCtlEntryOwner,OCTET,read-create,,current,,A textual description of the entity that created this entry. 
.1.3.6.1.3.124.1.1.8,TIME-AGGREGATE-MIB::tAggrCtlEntryStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object defines whether the parameters defined in this row are kept in volatile storage and lost upon reboot or backed up by non-volatile (permanent) storage. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.3.124.1.1.9,TIME-AGGREGATE-MIB::tAggrCtlEntryStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The row status variable, used according to row installation and removal conventions. Objects in a row can be modified only when the value of this object in the corresponding conceptual row is not 'active'. Thus, to modify one or more of the objects in this conceptual row, a. change the row status to 'notInService', b. change the values of the row, and c. change the row status to 'active'. The tAggrCtlEntryStatus may be changed to 'active' iff all the MOs in the conceptual row have been assigned valid values. 
.1.3.6.1.3.124.2,TIME-AGGREGATE-MIB::tAggrDataTable,,not-accessible,,current,,This is the data table. Each row of this table contains information about a TAgMO indexed by tAggrCtlEntryID. tAggrCtlEntryID is the key to the table. It is used to identify instances of the TAgMO that are present in the table. 
.1.3.6.1.3.124.2.1,TIME-AGGREGATE-MIB::tAggrDataEntry,,not-accessible,tAggrCtlEntryID,current,,Entry containing information pertaining to a TAgMO.
.1.3.6.1.3.124.2.1.1,TIME-AGGREGATE-MIB::tAggrDataRecord,Opaque,read-only,,current,,The snapshot value of the TAgMO.
.1.3.6.1.3.124.2.1.2,TIME-AGGREGATE-MIB::tAggrDataRecordCompressed,Opaque,read-only,,current,,The compressed value of the TAgMO. The compression algorithm will depend on the tAggrCtlCompressionAlgorithm given in the corresponding tAggrCtlEntry. If the value of the corresponding tAggrCtlCompressionAlgorithm is (1) 'none', then the value of all instances of this object will be a string of zero length. Note that the access privileges to this object will be governed by the access privileges of the corresponding MO instance. Thus, an entity attempting to access an instance of this MO MUST have access rights to the instance object pointed at by tAggrCtlMOInstance and this MO instance. 
.1.3.6.1.3.124.2.1.3,TIME-AGGREGATE-MIB::tAggrDataErrorRecord,Opaque,read-only,,current,,The error status corresponding to the MO instance samples aggregated in tAggrDataRecord (and tAggrDataRecordCompressed).
.1.3.6.1.3.124.3,TIME-AGGREGATE-MIB::tAggrConformance,,,,,,
.1.3.6.1.3.124.3.1,TIME-AGGREGATE-MIB::tAggrGroups,,,,,,
.1.3.6.1.3.124.3.1.1,TIME-AGGREGATE-MIB::tAggrMibBasicGroup,,,,,,A collection of objects for Time-Based aggregation of MOs.
.1.3.6.1.3.124.3.2,TIME-AGGREGATE-MIB::tAggrCompliances,,,,,,
.1.3.6.1.3.124.3.2.1,TIME-AGGREGATE-MIB::tAggrMibCompliance,,,,,,The compliance statement for SNMP entities that implement the TIME-AGGREGATE-MIB.
.1.3.6.1.3.125,RSERPOOL-MIB::rserpoolMIB,,,,,,The MIB module for managing an RSerPool implementation. Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This version of this MIB module is part of RFC 5525; see the RFC itself for full legal notices.
.1.3.6.1.3.125.1,RSERPOOL-MIB::rserpoolMIBObjects,,,,,,
.1.3.6.1.3.125.1.1,RSERPOOL-MIB::rserpoolENRPServers,,,,,,
.1.3.6.1.3.125.1.1.1,RSERPOOL-MIB::rserpoolENRPTable,,not-accessible,,current,,The table listing of ENRP servers.
.1.3.6.1.3.125.1.1.1.1,RSERPOOL-MIB::rserpoolENRPEntry,,not-accessible,rserpoolENRPIndex,current,,An ENRP server entry in the table listing of ENRP servers.
.1.3.6.1.3.125.1.1.1.1.1,RSERPOOL-MIB::rserpoolENRPIndex,Unsigned32,not-accessible,,current,,An integer to uniquely identify an ENRP server.
.1.3.6.1.3.125.1.1.1.1.2,RSERPOOL-MIB::rserpoolENRPOperationScope,OCTET,read-only,,current,,The definition of the operation scope of this ENRP server.
.1.3.6.1.3.125.1.1.1.1.3,RSERPOOL-MIB::rserpoolENRPIdentifier,Unsigned32,read-only,,current,,The ENRP server identifier of this ENRP server.
.1.3.6.1.3.125.1.1.1.1.4,RSERPOOL-MIB::rserpoolENRPDescription,OCTET,read-write,,current,,A textual description of this ENRP server, e.g., its location and a contact address of its administrator. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.1.1.1.5,RSERPOOL-MIB::rserpoolENRPUptime,TimeTicks,read-only,,current,,The ENRP service uptime of this ENRP server.
.1.3.6.1.3.125.1.1.1.1.6,RSERPOOL-MIB::rserpoolENRPPort,Unsigned32,read-only,,current,,The Stream Control Transmission Protocol (SCTP) port number of the ENRP protocol endpoint of this ENRP server.
.1.3.6.1.3.125.1.1.1.1.7,RSERPOOL-MIB::rserpoolENRPASAPAnnouncePort,Unsigned32,read-only,,current,,The destination UDP port number to which ASAP multicast announce messages are sent.
.1.3.6.1.3.125.1.1.1.1.8,RSERPOOL-MIB::rserpoolENRPASAPAnnounceAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2),The network-layer protocol over which ASAP multicast announce messages are sent.
.1.3.6.1.3.125.1.1.1.1.9,RSERPOOL-MIB::rserpoolENRPASAPAnnounceAddr,OCTET,read-only,,current,,The destination IP multicast address to which ASAP multicast announce messages are sent. The type of this address is given in rserpoolENRPASAPAnnounceAddrType.
.1.3.6.1.3.125.1.1.1.1.10,RSERPOOL-MIB::rserpoolENRPENRPAnnouncePort,Unsigned32,read-only,,current,,The destination UDP port number to which ENRP multicast announce messages are sent.
.1.3.6.1.3.125.1.1.1.1.11,RSERPOOL-MIB::rserpoolENRPENRPAnnounceAddrType,INTEGER,read-only,,current,ipv4(1):ipv6(2),The network-layer protocol over which ENRP multicast announce messages are sent.
.1.3.6.1.3.125.1.1.1.1.12,RSERPOOL-MIB::rserpoolENRPENRPAnnounceAddr,OCTET,read-only,,current,,The destination multicast IP address to which ENRP multicast announce messages are sent. The type of this address is given in rserpoolENRPENRPAnnounceAddrType.
.1.3.6.1.3.125.1.1.3,RSERPOOL-MIB::rserpoolENRPPoolTable,,not-accessible,,current,,The table listing of pools.
.1.3.6.1.3.125.1.1.3.1,RSERPOOL-MIB::rserpoolENRPPoolEntry,,not-accessible,rserpoolENRPIndex:rserpoolENRPPoolIndex,current,,The pool entry in the table listing of pools.
.1.3.6.1.3.125.1.1.3.1.1,RSERPOOL-MIB::rserpoolENRPPoolIndex,Unsigned32,not-accessible,,current,,An integer to uniquely identify a pool.
.1.3.6.1.3.125.1.1.3.1.2,RSERPOOL-MIB::rserpoolENRPPoolHandle,OCTET,read-only,,current,,The pool handle of this pool.
.1.3.6.1.3.125.1.1.4,RSERPOOL-MIB::rserpoolENRPPoolElementTable,,not-accessible,,current,,The table listing of pool elements.
.1.3.6.1.3.125.1.1.4.1,RSERPOOL-MIB::rserpoolENRPPoolElementEntry,,not-accessible,rserpoolENRPIndex:rserpoolENRPPoolIndex:rserpoolENRPPoolElementIndex,current,,A pool element in the table listing of pool elements.
.1.3.6.1.3.125.1.1.4.1.1,RSERPOOL-MIB::rserpoolENRPPoolElementIndex,Unsigned32,not-accessible,,current,,An integer to uniquely identify a pool element. Note, that uniqueness of a pool element identifier in the pool is not enforced; therefore, this index is required here!
.1.3.6.1.3.125.1.1.4.1.2,RSERPOOL-MIB::rserpoolENRPPoolElementID,Unsigned32,read-only,,current,,The pool element identifier of this pool element.
.1.3.6.1.3.125.1.1.4.1.3,RSERPOOL-MIB::rserpoolENRPASAPTransportPort,Unsigned32,read-only,,current,,The SCTP port number of the ASAP endpoint of this pool element.
.1.3.6.1.3.125.1.1.4.1.4,RSERPOOL-MIB::rserpoolENRPUserTransportProto,Unsigned32,read-only,,current,,The transport protocol number of the service endpoint of this pool element.
.1.3.6.1.3.125.1.1.4.1.5,RSERPOOL-MIB::rserpoolENRPUserTransportPort,Unsigned32,read-only,,current,,The transport protocol's port number of the service endpoint of this pool element.
.1.3.6.1.3.125.1.1.4.1.6,RSERPOOL-MIB::rserpoolENRPUserTransportUse,INTEGER,read-only,,current,dataOnly(0):dataPlusControl(1),The transport use of the service endpoint of this pool element.
.1.3.6.1.3.125.1.1.4.1.7,RSERPOOL-MIB::rserpoolENRPPolicyID,Unsigned32,read-only,,current,,The pool policy of this pool element.
.1.3.6.1.3.125.1.1.4.1.8,RSERPOOL-MIB::rserpoolENRPPolicyDescription,OCTET,read-only,,current,,The textual description of the pool policy of this pool element.
.1.3.6.1.3.125.1.1.4.1.9,RSERPOOL-MIB::rserpoolENRPPolicyWeight,Unsigned32,read-only,,current,,The pool policy's weight parameter for this pool element.
.1.3.6.1.3.125.1.1.4.1.10,RSERPOOL-MIB::rserpoolENRPPolicyLoad,Unsigned32,read-only,,current,,The pool policy's load status for this pool element.
.1.3.6.1.3.125.1.1.4.1.11,RSERPOOL-MIB::rserpoolENRPPolicyLoadDeg,Unsigned32,read-only,,current,,The pool policy's load degradation parameter for this pool element.
.1.3.6.1.3.125.1.1.4.1.12,RSERPOOL-MIB::rserpoolENRPRegistrationLife,TimeTicks,read-only,,current,,The registration life of this pool element.
.1.3.6.1.3.125.1.1.4.1.13,RSERPOOL-MIB::rserpoolENRPHomeENRPServer,Unsigned32,read-only,,current,,The ID of the Home ENRP server of this pool element.
.1.3.6.1.3.125.1.1.5,RSERPOOL-MIB::rserpoolENRPASAPAddrTable,,not-accessible,,current,,A table listing of all IP addresses of the ASAP transport endpoint.
.1.3.6.1.3.125.1.1.5.1,RSERPOOL-MIB::rserpoolENRPASAPAddrTableEntry,,not-accessible,rserpoolENRPIndex:rserpoolENRPPoolIndex:rserpoolENRPPoolElementIndex:rserpoolENRPASAPAddrTableIndex,current,,An IP address of the ASAP transport endpoint.
.1.3.6.1.3.125.1.1.5.1.1,RSERPOOL-MIB::rserpoolENRPASAPAddrTableIndex,Unsigned32,not-accessible,,current,,A unique identifier for the IP address of an ASAP transport endpoint.
.1.3.6.1.3.125.1.1.5.1.2,RSERPOOL-MIB::rserpoolENRPASAPL3Type,INTEGER,read-only,,current,ipv4(1):ipv6(2),The network-layer protocol (IPv4 or IPv6) of an IP address of an ASAP transport endpoint.
.1.3.6.1.3.125.1.1.5.1.3,RSERPOOL-MIB::rserpoolENRPASAPL3Addr,OCTET,read-only,,current,,The IP address of an ASAP transport endpoint. The type of this address is given in rserpoolENRPASAPL3Type.
.1.3.6.1.3.125.1.1.6,RSERPOOL-MIB::rserpoolENRPUserAddrTable,,not-accessible,,current,,A table listing of all IP addresses of the user transport endpoint.
.1.3.6.1.3.125.1.1.6.1,RSERPOOL-MIB::rserpoolENRPUserAddrTableEntry,,not-accessible,rserpoolENRPIndex:rserpoolENRPPoolIndex:rserpoolENRPPoolElementIndex:rserpoolENRPUserAddrTableIndex,current,,An IP address of the user transport endpoint.
.1.3.6.1.3.125.1.1.6.1.1,RSERPOOL-MIB::rserpoolENRPUserAddrTableIndex,Unsigned32,not-accessible,,current,,A unique identifier for the IP address of a user transport endpoint.
.1.3.6.1.3.125.1.1.6.1.2,RSERPOOL-MIB::rserpoolENRPUserL3Type,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2),The network-layer protocol (IPv4 or IPv6) of an IP address of a user transport endpoint. Set to unknown for an opaque address.
.1.3.6.1.3.125.1.1.6.1.3,RSERPOOL-MIB::rserpoolENRPUserL3Addr,OCTET,read-only,,current,,The IP address of a user transport endpoint. The type of this address is given in rserpoolENRPUserL3Type.
.1.3.6.1.3.125.1.1.6.1.4,RSERPOOL-MIB::rserpoolENRPUserL3Opaque,OCTET,read-only,,current,,The opaque address of a user transport endpoint.
.1.3.6.1.3.125.1.1.7,RSERPOOL-MIB::rserpoolENRPENRPAddrTable,,not-accessible,,current,,A table listing of all IP addresses of the ENRP transport endpoint.
.1.3.6.1.3.125.1.1.7.1,RSERPOOL-MIB::rserpoolENRPENRPAddrTableEntry,,not-accessible,rserpoolENRPIndex:rserpoolENRPENRPAddrTableIndex,current,,An IP address of the ENRP transport endpoint.
.1.3.6.1.3.125.1.1.7.1.1,RSERPOOL-MIB::rserpoolENRPENRPAddrTableIndex,Unsigned32,not-accessible,,current,,A unique identifier for the IP address of an ENRP transport endpoint.
.1.3.6.1.3.125.1.1.7.1.2,RSERPOOL-MIB::rserpoolENRPENRPL3Type,INTEGER,read-only,,current,ipv4(1):ipv6(2),The network-layer protocol (IPv4 or IPv6) of an IP address of an ENRP transport endpoint.
.1.3.6.1.3.125.1.1.7.1.3,RSERPOOL-MIB::rserpoolENRPENRPL3Addr,OCTET,read-only,,current,,The IP address of an ENRP transport endpoint. The type of this address is given in rserpoolENRPENRPL3Type.
.1.3.6.1.3.125.1.1.8,RSERPOOL-MIB::rserpoolENRPPeerTable,,not-accessible,,current,,The table listing of a peer table.
.1.3.6.1.3.125.1.1.8.1,RSERPOOL-MIB::rserpoolENRPPeerEntry,,not-accessible,rserpoolENRPPeerIndex,current,,A peer entry in the table listing of a peer table.
.1.3.6.1.3.125.1.1.8.1.1,RSERPOOL-MIB::rserpoolENRPPeerIndex,Unsigned32,not-accessible,,current,,A unique identifier for a peer entry in the table listing of a peer table.
.1.3.6.1.3.125.1.1.8.1.2,RSERPOOL-MIB::rserpoolENRPPeerIdentifier,Unsigned32,read-only,,current,,The ENRP identifier of this peer.
.1.3.6.1.3.125.1.1.8.1.3,RSERPOOL-MIB::rserpoolENRPPeerPort,Unsigned32,read-only,,current,,The SCTP port number of the ENRP transport endpoint of this peer.
.1.3.6.1.3.125.1.1.8.1.4,RSERPOOL-MIB::rserpoolENRPPeerLastHeard,TimeTicks,read-only,,current,,The time since the reception of the last ENRP Presence message of this peer.
.1.3.6.1.3.125.1.1.9,RSERPOOL-MIB::rserpoolENRPPeerAddrTable,,not-accessible,,current,,A table listing of the peer endpoint addresses.
.1.3.6.1.3.125.1.1.9.1,RSERPOOL-MIB::rserpoolENRPPeerAddrTableEntry,,not-accessible,rserpoolENRPPeerIndex:rserpoolENRPPeerAddrTableIndex,current,,A table listing of all IP addresses of the ENRP transport endpoint of a peer referenced by rserpoolENRPPeerIndex.
.1.3.6.1.3.125.1.1.9.1.1,RSERPOOL-MIB::rserpoolENRPPeerAddrTableIndex,Unsigned32,not-accessible,,current,,A unique identifier for the IP address of a peer ENRP transport endpoint.
.1.3.6.1.3.125.1.1.9.1.2,RSERPOOL-MIB::rserpoolENRPPeerL3Type,INTEGER,read-only,,current,ipv4(1):ipv6(2),The network-layer protocol (IPv4 or IPv6) of an IP address of a peer ENRP transport endpoint.
.1.3.6.1.3.125.1.1.9.1.3,RSERPOOL-MIB::rserpoolENRPPeerL3Addr,OCTET,read-only,,current,,The IP address of a peer ENRP transport endpoint. The type of this address is given in rserpoolENRPPeerL3Type.
.1.3.6.1.3.125.1.2,RSERPOOL-MIB::rserpoolPoolElements,,,,,,
.1.3.6.1.3.125.1.2.1,RSERPOOL-MIB::rserpoolPETable,,not-accessible,,current,,The table listing of pool elements.
.1.3.6.1.3.125.1.2.1.1,RSERPOOL-MIB::rserpoolPEEntry,,not-accessible,rserpoolPEIndex,current,,A pool element in the table listing of pool elements.
.1.3.6.1.3.125.1.2.1.1.1,RSERPOOL-MIB::rserpoolPEIndex,Unsigned32,not-accessible,,current,,An integer to uniquely identify a pool element. Note, that uniqueness of a pool element identifier in the pool is not enforced; therefore, this index is required here!
.1.3.6.1.3.125.1.2.1.1.2,RSERPOOL-MIB::rserpoolPEOperationScope,OCTET,read-only,,current,,The operation scope of this pool element.
.1.3.6.1.3.125.1.2.1.1.3,RSERPOOL-MIB::rserpoolPEPoolHandle,OCTET,read-write,,current,,The pool handle of this pool element. Changing this object will update the pool element's pool handle and result in a re-registration. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.4,RSERPOOL-MIB::rserpoolPEIdentifier,Unsigned32,read-only,,current,,The pool element identifier of this pool element.
.1.3.6.1.3.125.1.2.1.1.5,RSERPOOL-MIB::rserpoolPEDescription,OCTET,read-write,,current,,A textual description of this pool element, e.g., its location and a contact address of its administrator. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.6,RSERPOOL-MIB::rserpoolPEUptime,TimeTicks,read-only,,current,,The ENRP service uptime of this pool element.
.1.3.6.1.3.125.1.2.1.1.7,RSERPOOL-MIB::rserpoolPEASAPTransportPort,Unsigned32,read-only,,current,,The SCTP port number of the ASAP endpoint of this pool element.
.1.3.6.1.3.125.1.2.1.1.8,RSERPOOL-MIB::rserpoolPEUserTransportProto,Unsigned32,read-only,,current,,The transport protocol number of the service endpoint of this pool element.
.1.3.6.1.3.125.1.2.1.1.9,RSERPOOL-MIB::rserpoolPEUserTransportPort,Unsigned32,read-only,,current,,The transport protocol's port number of the service endpoint of this pool element.
.1.3.6.1.3.125.1.2.1.1.10,RSERPOOL-MIB::rserpoolPEUserTransportUse,INTEGER,read-only,,current,dataOnly(0):dataPlusControl(1),The transport use of the service endpoint of this pool element.
.1.3.6.1.3.125.1.2.1.1.11,RSERPOOL-MIB::rserpoolPEPolicyID,Unsigned32,read-write,,current,,The pool policy of this pool element. Changing this object will update the pool element's policy and result in a re-registration. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.12,RSERPOOL-MIB::rserpoolPEPolicyDescription,OCTET,read-write,,current,,The textual description of the pool policy of this pool element. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.13,RSERPOOL-MIB::rserpoolPEPolicyWeight,Unsigned32,read-write,,current,,The pool policy's weight parameter for this pool element. Changing this object will update the pool element's policy weight setting and result in a re-registration. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.14,RSERPOOL-MIB::rserpoolPEPolicyLoad,Unsigned32,read-only,,current,,The pool policy's load status for this pool element.
.1.3.6.1.3.125.1.2.1.1.15,RSERPOOL-MIB::rserpoolPEPolicyLoadDeg,Unsigned32,read-write,,current,,The pool policy's load degradation parameter for this pool element. Changing this object will update the pool element's load degradation setting and result in a re-registration. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.16,RSERPOOL-MIB::rserpoolPERegistrationLife,TimeTicks,read-write,,current,,The registration life of this pool element. Changing this object will update the pool element's lifetime setting and result in a re-registration. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.2.1.1.17,RSERPOOL-MIB::rserpoolPEHomeENRPServer,Unsigned32,read-only,,current,,The ID of the Home ENRP server of this pool element.
.1.3.6.1.3.125.1.2.2,RSERPOOL-MIB::rserpoolPEASAPAddrTable,,not-accessible,,current,,A table listing of all IP addresses of the ASAP transport endpoint.
.1.3.6.1.3.125.1.2.2.1,RSERPOOL-MIB::rserpoolPEASAPAddrTableEntry,,not-accessible,rserpoolPEIndex:rserpoolPEASAPAddrTableIndex,current,,An IP address of the ASAP transport endpoint.
.1.3.6.1.3.125.1.2.2.1.1,RSERPOOL-MIB::rserpoolPEASAPAddrTableIndex,Unsigned32,not-accessible,,current,,A unique identifier for the IP address of an ASAP transport endpoint.
.1.3.6.1.3.125.1.2.2.1.2,RSERPOOL-MIB::rserpoolPEASAPL3Type,INTEGER,read-only,,current,ipv4(1):ipv6(2),The network-layer protocol (IPv4 or IPv6) of an IP address of an ASAP transport endpoint.
.1.3.6.1.3.125.1.2.2.1.3,RSERPOOL-MIB::rserpoolPEASAPL3Addr,OCTET,read-only,,current,,The IP address of an ASAP transport endpoint. The type of this address is given in rserpoolPEASAPL3Type.
.1.3.6.1.3.125.1.2.6,RSERPOOL-MIB::rserpoolPEUserAddrTable,,not-accessible,,current,,A table listing of all IP addresses of the user transport endpoint.
.1.3.6.1.3.125.1.2.6.1,RSERPOOL-MIB::rserpoolPEUserAddrTableEntry,,not-accessible,rserpoolPEIndex:rserpoolPEUserAddrTableIndex,current,,An IP address of the user transport endpoint.
.1.3.6.1.3.125.1.2.6.1.1,RSERPOOL-MIB::rserpoolPEUserAddrTableIndex,Unsigned32,not-accessible,,current,,A unique identifier for the IP address of a user transport endpoint.
.1.3.6.1.3.125.1.2.6.1.2,RSERPOOL-MIB::rserpoolPEUserL3Type,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2),The network-layer protocol of an IP address of a user transport endpoint. Set to unknown for opaque address.
.1.3.6.1.3.125.1.2.6.1.3,RSERPOOL-MIB::rserpoolPEUserL3Addr,OCTET,read-only,,current,,The IP address of a user transport endpoint. The type of this address is given in rserpoolPEUserL3Addr.
.1.3.6.1.3.125.1.2.6.1.4,RSERPOOL-MIB::rserpoolPEUserL3Opaque,OCTET,read-only,,current,,The opaque address of a user transport endpoint.
.1.3.6.1.3.125.1.3,RSERPOOL-MIB::rserpoolPoolUsers,,,,,,
.1.3.6.1.3.125.1.3.1,RSERPOOL-MIB::rserpoolPUTable,,not-accessible,,current,,The table listing of pool users.
.1.3.6.1.3.125.1.3.1.1,RSERPOOL-MIB::rserpoolPUEntry,,not-accessible,rserpoolPUIndex,current,,A pool user in the table listing of pool users.
.1.3.6.1.3.125.1.3.1.1.1,RSERPOOL-MIB::rserpoolPUIndex,Unsigned32,not-accessible,,current,,An integer to uniquely identify a pool user.
.1.3.6.1.3.125.1.3.1.1.2,RSERPOOL-MIB::rserpoolPUOperationScope,OCTET,read-only,,current,,The operation scope of this pool user.
.1.3.6.1.3.125.1.3.1.1.3,RSERPOOL-MIB::rserpoolPUPoolHandle,OCTET,read-write,,current,,The pool handle of this pool user. Changing this object will update the pool user's pool handle for all future sessions. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.3.1.1.4,RSERPOOL-MIB::rserpoolPUDescription,OCTET,read-write,,current,,A textual description of this pool user, e.g., its location and a contact address of its administrator. This object SHOULD be maintained in a persistent manner.
.1.3.6.1.3.125.1.3.1.1.5,RSERPOOL-MIB::rserpoolPUUptime,TimeTicks,read-only,,current,,The ENRP service uptime of this pool user.
.1.3.6.1.3.125.2,RSERPOOL-MIB::rserpoolMIBConformance,,,,,,
.1.3.6.1.3.125.2.1,RSERPOOL-MIB::rserpoolMIBCompliances,,,,,,
.1.3.6.1.3.125.2.1.1,RSERPOOL-MIB::rserpoolMIBCompliance,,,,,,The compliance statement for SNMP entities that implement RSerPool.
.1.3.6.1.3.125.2.2,RSERPOOL-MIB::rserpoolMIBGroups,,,,,,
.1.3.6.1.3.125.2.2.1,RSERPOOL-MIB::rserpoolENRPGroup,,,,,,The group contains all ENRP server instances running on the system
.1.3.6.1.3.125.2.2.2,RSERPOOL-MIB::rserpoolPEGroup,,,,,,The group contains all pool element instances running on the system
.1.3.6.1.3.125.2.2.3,RSERPOOL-MIB::rserpoolPUGroup,,,,,,The group contains all pool user instances running on the system
.1.3.6.1.3.126,SMF-MIB::smfMIB,,,,,,This MIB module contains managed object definitions for the MANET SMF RSSA process defined in: Macker, J., Ed., Simplified Multicast Forwarding, RFC 6621, May 2012. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
.1.3.6.1.3.126.0,SMF-MIB::smfMIBNotifications,,,,,,
.1.3.6.1.3.126.0.0,SMF-MIB::smfMIBNotifObjects,,,,,,
.1.3.6.1.3.126.0.0.1,SMF-MIB::smfNotifAdminStatusChange,,,,,,smfCfgAdminStatusChange is a notification sent when the 'smfCfgAdminStatus' object changes.
.1.3.6.1.3.126.0.0.2,SMF-MIB::smfNotifConfiguredOpModeChange,,,,,,smfNotifConfiguredOpModeChange is a notification sent when the 'smfCfgOperationalMode' object changes.
.1.3.6.1.3.126.0.0.3,SMF-MIB::smfNotifIfAdminStatusChange,,,,,,smfCfgIfAdminStatusChange is a notification sent when the 'smfCfgIfAdminStatus' object changes.
.1.3.6.1.3.126.0.0.4,SMF-MIB::smfNotifDpdMemoryOverflowEvent,,,,,,smfNotifDpdMemoryOverflowEvents is sent when the number of memory overflow events exceeds the 'smfNotifDpdMemoryOverflowThreshold' within the previous number of seconds defined by the 'smfNotifDpdMemoryOverflowWindow'.
.1.3.6.1.3.126.0.1,SMF-MIB::smfMIBNotifControl,,,,,,
.1.3.6.1.3.126.0.1.1,SMF-MIB::smfNotifDpdMemoryOverflowThreshold,Integer32,read-write,,current,,A threshold value for the 'smfNotifDpdmemoryOverflowEvents' object. If the number of occurrences exceeds this threshold within the previous number of seconds 'smfNotifDpdMemoryOverflowWindow', then the 'smfNotifDpdMemoryOverflowEvent' notification is sent. The default value for this object is '1'.
.1.3.6.1.3.126.0.1.2,SMF-MIB::smfNotifDpdMemoryOverflowWindow,TimeTicks,read-write,,current,,A time window value for the 'smfNotifDpdmemoryOverflowEvents' object. If the number of occurrences exceeds the 'smfNotifDpdMemoryOverflowThreshold' within the previous number of seconds 'smfNotifDpdMemoryOverflowWindow', then the 'smfNotifDpdMemoryOverflowEvent' notification is sent. The default value for this object is '1'.
.1.3.6.1.3.126.1,SMF-MIB::smfMIBObjects,,,,,,
.1.3.6.1.3.126.1.1,SMF-MIB::smfCapabilitiesGroup,,,,,,
.1.3.6.1.3.126.1.1.1,SMF-MIB::smfCapabilitiesTable,,not-accessible,,current,,The smfCapabilitiesTable identifies the resident set of SMF Operational Modes and RSSA combinations that can run on this forwarder.
.1.3.6.1.3.126.1.1.1.1,SMF-MIB::smfCapabilitiesEntry,,not-accessible,smfCapabilitiesIndex,current,,Information about a particular operational mode and RSSA combination. 
.1.3.6.1.3.126.1.1.1.1.1,SMF-MIB::smfCapabilitiesIndex,Integer32,not-accessible,,current,,The index for this entry; a unique value, greater than zero, for each combination of a particular operational mode and RSSA available on this device. It is recommended that values are assigned contiguously starting from 1. Rows in this table are automatically populated by the entity's management system on initialization. By default, the agent should support at least the Classical Flooding 'cF' algorithm. All compliant SMF forwarders must support Classical Flooding. Hence, the first entry in this table MUST exist and MUST be defined as: smfCapabilitiesIndex i '1' smfCapabilitiesOpModeID i 'cfOnly(1)' smfCapabilitiesRssaID i 'cF(1)' The value for each combination MUST remain constant at least from one re-initialization of the entity's management system to the next re-initialization.
.1.3.6.1.3.126.1.1.1.1.2,SMF-MIB::smfCapabilitiesOpModeID,INTEGER,read-only,,current,independent(1):routing(2):crossLayer(3),This object identifies the particular operational mode for this device.
.1.3.6.1.3.126.1.1.1.1.3,SMF-MIB::smfCapabilitiesRssaID,INTEGER,read-only,,current,cF(1):sMPR(2):eCDS(3):mprCDS(4),This object identifies the particular RSSA algorithm in this MIB module. Example RSSAs are found in the appendix of RFC 6621.
.1.3.6.1.3.126.1.2,SMF-MIB::smfConfigurationGroup,,,,,,
.1.3.6.1.3.126.1.2.1,SMF-MIB::smfCfgAdminStatus,INTEGER,read-write,,current,enabled(1):disabled(2),The configured status of the SMF process on this device. 'enabled(1)' means that SMF is configured to run on this device. 'disabled(2)' means that the SMF process is configured off. Prior to SMF functions being performed over specific interfaces, this object must first be 'enabled'. If this object is 'disabled', then no SMF functions are being performed on the device and all smfCfgIfAdminStatus objects MUST also be set to 'disabled'. When this object is changed from 'enabled' to 'disabled' by the manager, then all smfCfgIfAdminStatus objects MUST also be automatically set to 'disabled' by the agent. The default value for this object SHOULD be 'enabled'. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.2,SMF-MIB::smfCfgSmfSysUpTime,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the system SMF process was last re-initialized. The SMF process is re-initialized when the value of the 'smfCfgAdminStatus' object transitions to 'enabled' from either a prior value of 'disabled' or upon initialization of this device.
.1.3.6.1.3.126.1.2.3,SMF-MIB::smfCfgRouterIDAddrType,INTEGER,read-write,,current,ipv4(1):ipv6(2),The address type of the address used for the SMF ID of this router as specified in the 'smfCfgRouterID' next. Only the values ipv4(1) and ipv6(2) are supported. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.4,SMF-MIB::smfCfgRouterID,OCTET,read-write,,current,,The IP address used as the SMF router ID. This can be set by the management station. If not explicitly set, then the device SHOULD select a routable IP address assigned to this router for use as the 'smfCfgRouterID'. The smfCfgRouterID is a logical identification that MUST be consistent across interoperable SMF neighborhoods, and it is RECOMMENDED to be chosen as the numerically largest address contained in a node's 'Neighbor Address List' as defined in NHDP. An smfCfgRouterID MUST be unique within the scope of the operating MANET network regardless of the method used for selecting it. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.5,SMF-MIB::smfCfgOperationalMode,Integer32,read-write,,current,,The SMF RSS node operational mode and RSSA combination active on this local forwarder. This object is defined to be equal to the smfCapabilitiesIndex, which identifies the specific active operational mode and RSSA. The default value for this object is '1', which corresponds to: smfCapabilitiesOpModeID i 'cfOnly(1)' smfCapabilitiesRssaID i 'cF(1)' This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.6,SMF-MIB::smfCfgRssaMember,INTEGER,read-write,,current,potential(1):always(2):never(3),The RSSA downselects a set of forwarders for multicast forwarding. Sometimes it is useful to force an agent to be included or excluded from the resulting RSS. This object is a switch to allow for this behavior. The value 'potential(1)' allows the selected RSSA to determine if this agent is included or excluded from the RSS. The value 'always(2)' forces the selected RSSA to include this agent in the RSS. The value 'never(3)' forces the selected RSSA to exclude this agent from the RSS. The default setting for this object is 'potential(1)'. Other settings could pose operational risks under certain conditions. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.7,SMF-MIB::smfCfgIpv4Dpd,INTEGER,read-write,,current,hashBased(1):identificationBased(2),The current method for IPv4 duplicate packet detection. The value 'hashBased(1)' indicates that the router's duplicate packet detection is based upon comparing a hash over the packet fields. This is the default setting for this object. The value 'identificationBased(2)' indicates that the duplicate packet detection relies upon header information in the multicast packets to identify previously received packets. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.8,SMF-MIB::smfCfgIpv6Dpd,INTEGER,read-write,,current,hashBased(1):identificationBased(2),The current method for IPv6 duplicate packet detection. The values indicate the type of method used for duplicate packet detection as described the previous description for the object 'smfCfgIpv4Dpd'. The default value for this object is 'hashBased(1)'. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.9,SMF-MIB::smfCfgMaxPktLifetime,Integer32,read-write,,current,,The estimate of the network packet traversal time. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.10,SMF-MIB::smfCfgDpdEntryMaxLifetime,Integer32,read-write,,current,,The maximum lifetime of a cached DPD record in the local device storage. If the memory is running low prior to the MaxLifetime being exceeded, the local SMF devices should purge the oldest records first. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.11,SMF-MIB::smfCfgNhdpRssaMesgTLVIncluded,INTEGER,read-write,,current,true(1):false(2),Indicates whether or not the associated NHDP messages include the RSSA Message TLV. This is an optional SMF operational setting. The value 'true(1)' indicates that this TLV is included; the value 'false(2)' indicates that it is not included. It is RECOMMENDED that the RSSA Message TLV be included in the NHDP messages. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.12,SMF-MIB::smfCfgNhdpRssaAddrBlockTLVIncluded,INTEGER,read-write,,current,true(1):false(2),Indicates whether or not the associated NHDP messages include the RSSA Address Block TLV. This is an optional SMF operational setting. The value 'true(1)' indicates that this TLV is included; the value 'false(2)' indicates that it is not included. The smfCfgNhdpRssaAddrBlockTLVIncluded is optional in all cases as it depends on the existence of an address block that may not be present. If this SMF device is configured with NHDP, then this object SHOULD be set to 'true(1)'. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.13,SMF-MIB::smfCfgAddrForwardingTable,,not-accessible,,current,,The smfCfgAddrForwardingTable is essentially a filter table (if populated) that identifies addresses/packets to be forwarded via the local SMF flooding process. The IP Multicast MIB module in RFC 5132 manages objects related to standard IP multicast, which could be running in parallel to SMF on the device. RFC 5132 manages traditional IP-based multicast (based upon multicast routing mechanisms). The SMF-MIB module provides management for a MANET subnet-based flooding mechanism that may be used for multicast transport (through SMF broadcast) depending upon the MANET dynamics and other factors regarding the MANET subnet. Further, they may coexist in certain MANET deployments using the smfCfgAddrForwardingTable to hand certain IP multicast addresses to the SMF process and other IP multicast packets to be forwarded by other multicast mechanisms that are IP route based. SMF and the associated SMF-MIB module are experimental and these are some of the experiments to be had with SMF and the SMF-MIB module. This is the (conceptual) table containing information on multicast addresses that are to be forwarded by the SMF process. This table represents an IP filters table for forwarding (or not) packets based upon their IP multicast address. The SMF process can be configured to forward only those multicast addresses found within the smfCfgAddrForwardingTable. As such, addresses that are to be forwarded by the SMF process MUST be found within the address ranges configured within this table, unless this table is empty. Each row is associated with a range of multicast addresses, and ranges for different rows must be disjoint. Different rows MAY share a common smfCfgAddrForwardingGroupName to administratively associate different rows. The objects in this table are persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.13.1,SMF-MIB::smfCfgAddrForwardingEntry,,not-accessible,smfCfgAddrForwardingIndex,current,,An entry (conceptual row) containing the information on a particular multicast scope.
.1.3.6.1.3.126.1.2.13.1.1,SMF-MIB::smfCfgAddrForwardingIndex,Integer32,not-accessible,,current,,This object identifies a unique entry for a forwarding group. The index for this entry is a unique value, greater than zero, for each row. It is recommended that values are assigned contiguously starting from 1. The value for each row index MUST remain constant from one re-initialization of the entity's management system to the next re-initialization.
.1.3.6.1.3.126.1.2.13.1.2,SMF-MIB::smfCfgAddrForwardingGroupName,OCTET,read-create,,current,,This object identifies a group name for a set of row entries in order to administratively associate a set of address ranges. If there is no group name or this object is otherwise not applicable, then this object contains a zero-length string. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.13.1.3,SMF-MIB::smfCfgAddrForwardingAddrType,INTEGER,read-create,,current,ipv4(1):ipv6(2),The type of the addresses in the multicast forwarding ranges identified by this table. Only the values ipv4(1) and ipv6(2) are supported. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.13.1.4,SMF-MIB::smfCfgAddrForwardingAddress,OCTET,read-create,,current,,The multicast group address that, when combined with smfCfgAddrForwardingAddrPrefixLength, gives the group prefix for this forwarding range. The InetAddressType is given by smfCfgAddrForwardingAddrType. This address object is only significant up to smfCfgAddrForwardingAddrPrefixLength bits. The remaining address bits are set to zero. This is especially important for this index field. Any non-zero bits would signify an entirely different entry. Legal values correspond to the subset of address families for which multicast address allocation is supported. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.13.1.5,SMF-MIB::smfCfgAddrForwardingAddrPrefixLength,Unsigned32,read-create,,current,,The length in bits of the mask that, when combined with smfCfgAddrForwardingAddress, gives the group prefix for this forwarding range. This object is persistent and, when written, the entity SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.13.1.6,SMF-MIB::smfCfgAddrForwardingStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row, by which new entries may be created, or old entries deleted from this table.
.1.3.6.1.3.126.1.2.14,SMF-MIB::smfCfgInterfaceTable,,not-accessible,,current,,The SMF Interface Table describes the SMF interfaces that are participating in the SMF packet forwarding process. The ifIndex is from the interfaces group defined in the Interfaces Group MIB module (RFC 2863). As such, this table 'sparse augments' the ifTable specifically when SMF is to be configured to operate over this interface. A conceptual row in this table exists if and only if either a manager has explicitly created the row or there is an interface on the managed device that automatically supports and runs SMF as part of the device's initialization process. The manager creates a row in this table by setting the rowStatus to 'createAndGo' or 'createAndWait'. Row objects having associated DEFVAL clauses are automatically defined by the agent with these values during row creation, unless the manager explicitly defines these object values during the row creation. As the smfCfgInterfaceTable sparsely augments the IfTable. Hence, + an entry cannot exist in smfCfgInterfaceTable without a corresponding entry in the ifTable. + if an entry in the ifTable is removed, the corresponding entry (if it exists) in the smfCfgInterfaceTable MUST be removed. + the smfCfgIfStatus can have a value of 'enabled' or 'disabled' independent of the current value of the ifAdminStatus of the corresponding entry in the ifTable. The values of the objects smfCfgAdminStatus and smfCfgIfAdminStatus reflect the up-down status of the SMF process running on the device and on the specific interfaces, respectively. Hence, + the value of the smfCfgAdminStatus can be 'enabled' or 'disabled' reflecting the current running status of the SMF process on the device. + the value of the smfCfgIfAdminStatus can be 'enabled' or 'disabled' if the value of the smfCfgAdminStatus is set to 'enabled'. + if the value of the smfCfgAdminStatus is 'disabled', then the corresponding smfCfgIfAdminStatus objects MUST be set to 'disabled' in the smfCfgInterfaceTable. + once the value of the smfCfgAdminStatus changes from 'disabled' to 'enabled', it is up to the management system to make the corresponding changes to the smfCfgIfAdminStatus values back to 'enabled'. 
.1.3.6.1.3.126.1.2.14.1,SMF-MIB::smfCfgInterfaceEntry,,not-accessible,smfCfgIfIndex,current,,The SMF interface entry describes one SMF interface as indexed by its ifIndex. The objects in this table are persistent and, when written, the device SHOULD save the change to non-volatile storage. For further information on the storage behavior for these objects, refer to the description for the smfCfgIfRowStatus object.
.1.3.6.1.3.126.1.2.14.1.1,SMF-MIB::smfCfgIfIndex,Integer32,not-accessible,,current,,The ifIndex for this SMF interface. This value MUST correspond to an ifIndex referring to a valid entry in the Interfaces Table. If the manager attempts to create a row for which the ifIndex does not exist on the local device, then the agent SHOULD issue a return value of 'inconsistentValue' and the operation SHOULD fail.
.1.3.6.1.3.126.1.2.14.1.2,SMF-MIB::smfCfgIfAdminStatus,INTEGER,read-create,,current,enabled(1):disabled(2),The SMF interface's administrative status. The value 'enabled' denotes that the interface is running the SMF forwarding process. The value 'disabled' denotes that the interface is currently external to the SMF forwarding process. When the value of the smfCfgAdminStatus is 'disabled', then the corresponding smfCfgIfAdminStatus objects MUST be set to 'disabled' in the smfCfgInterfaceTable. If this object is not equal to 'enabled', all associated entries in the 'smfPerfIpv4InterfacePerfTable' and the 'smfPerfIpv6InterfacePerfTable' MUST be deleted. The default value for this object is 'enabled(1)'. This object SHOULD be persistent and when written the device SHOULD save the change to non-volatile storage.
.1.3.6.1.3.126.1.2.14.1.3,SMF-MIB::smfCfgIfSmfUpTime,TimeTicks,read-only,,current,,The time (in hundredths of a second) since this interface SMF process was last re-initialized. The interface SMF process is re-initialized when the value of the 'smfCfgIfAdminStatus' object transitions to 'enabled' from either a prior value of 'disabled' or upon initialization of this interface or this device.
.1.3.6.1.3.126.1.2.14.1.4,SMF-MIB::smfCfgIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object permits management of this table by facilitating actions such as row creation, construction, and destruction. The value of this object has no effect on whether other objects in this conceptual row can be modified. An entry may not exist in the 'active' state unless all objects in the entry have a defined appropriate value. For objects with DEFVAL clauses, the management station does not need to specify the value of these objects in order for the row to transit to the 'active' state; the default value for these objects is used. For objects that do not have DEFVAL clauses, the network manager MUST specify the value of these objects prior to this row transitioning to the 'active' state. When this object transitions to 'active', all objects in this row SHOULD be written to non-volatile (stable) storage. Read-create objects in this row MAY be modified. When an object in a row with smfCfgIfRowStatus of 'active' is changed, then the updated value MUST be reflected in SMF and this new object value MUST be written to non-volatile storage.
.1.3.6.1.3.126.1.3,SMF-MIB::smfStateGroup,,,,,,
.1.3.6.1.3.126.1.3.1,SMF-MIB::smfStateNodeRsStatusIncluded,INTEGER,read-only,,current,true(1):false(2),The current status of the SMF node in the context of the MANETs relay set. A value of 'true(1)' indicates that the node is currently part of the MANET Relay Set. A value of 'false(2)' indicates that the node is currently not part of the MANET Relay Set.
.1.3.6.1.3.126.1.3.2,SMF-MIB::smfStateDpdMemoryOverflow,Counter32,read-only,,current,,The number of DPD records that had to be flushed to prevent memory overruns for caching of these records. The number of records to be flushed upon a buffer overflow is an implementation specific decision. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.3.3,SMF-MIB::smfStateNeighborTable,,not-accessible,,current,,The SMF StateNeighborTable describes the current one-hop neighbor nodes, their address and SMF RSSA, and the interface on which they can be reached.
.1.3.6.1.3.126.1.3.3.1,SMF-MIB::smfStateNeighborEntry,,not-accessible,smfStateNeighborIpAddrType:smfStateNeighborIpAddr:smfStateNeighborPrefixLen,current,,The SMF Neighbor Table contains the set of one-hop neighbors, the interface they are reachable on, and the SMF RSSA they are currently running.
.1.3.6.1.3.126.1.3.3.1.1,SMF-MIB::smfStateNeighborIpAddrType,INTEGER,not-accessible,,current,ipv4(1):ipv6(2),The one-hop neighbor IP address type. Only the values 'ipv4(1)' and 'ipv6(2)' are supported.
.1.3.6.1.3.126.1.3.3.1.2,SMF-MIB::smfStateNeighborIpAddr,OCTET,not-accessible,,current,,The one-hop neighbor Inet IPv4 or IPv6 address. Only IPv4 and IPv6 addresses are supported.
.1.3.6.1.3.126.1.3.3.1.3,SMF-MIB::smfStateNeighborPrefixLen,Unsigned32,not-accessible,,current,,The prefix length. This is a decimal value that indicates the number of contiguous, higher-order bits of the address that make up the network portion of the address.
.1.3.6.1.3.126.1.3.3.1.4,SMF-MIB::smfStateNeighborRSSA,INTEGER,read-only,,current,cF(1):sMPR(2):eCDS(3):mprCDS(4),The current RSSA running on the neighbor.
.1.3.6.1.3.126.1.3.3.1.6,SMF-MIB::smfStateNeighborNextHopInterface,Integer32,read-only,,current,,The interface ifIndex over which the neighbor is reachable in one-hop.
.1.3.6.1.3.126.1.4,SMF-MIB::smfPerformanceGroup,,,,,,
.1.3.6.1.3.126.1.4.1,SMF-MIB::smfPerfGobalGroup,,,,,,
.1.3.6.1.3.126.1.4.1.1,SMF-MIB::smfPerfIpv4MultiPktsRecvTotal,Counter32,read-only,,current,,A counter of the total number of multicast IPv4 packets received by the device and delivered to the SMF process. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.2,SMF-MIB::smfPerfIpv4MultiPktsForwardedTotal,Counter32,read-only,,current,,A counter of the total number of multicast IPv4 packets forwarded by the device. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.3,SMF-MIB::smfPerfIpv4DuplMultiPktsDetectedTotal,Counter32,read-only,,current,,A counter of the total number of duplicate multicast IPv4 packets detected by the device. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.4,SMF-MIB::smfPerfIpv4DroppedMultiPktsTTLExceededTotal,Counter32,read-only,,current,,A counter of the total number of dropped multicast IPv4 packets by the device due to Time to Live (TTL) exceeded. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.5,SMF-MIB::smfPerfIpv4TTLLargerThanPreviousTotal,Counter32,read-only,,current,,A counter of the total number of IPv4 packets received that have a TTL larger than that of a previously received identical packet. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.6,SMF-MIB::smfPerfIpv6MultiPktsRecvTotal,Counter32,read-only,,current,,A counter of the total number of multicast IPv6 packets received by the device and delivered to the SMF process. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.7,SMF-MIB::smfPerfIpv6MultiPktsForwardedTotal,Counter32,read-only,,current,,A counter of the total number of multicast IPv6 packets forwarded by the device. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.8,SMF-MIB::smfPerfIpv6DuplMultiPktsDetectedTotal,Counter32,read-only,,current,,A counter of the total number of duplicate multicast IPv6 packets detected by the device. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.9,SMF-MIB::smfPerfIpv6DroppedMultiPktsTTLExceededTotal,Counter32,read-only,,current,,A counter of the total number of dropped multicast IPv6 packets by the device due to TTL exceeded. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.10,SMF-MIB::smfPerfIpv6TTLLargerThanPreviousTotal,Counter32,read-only,,current,,A counter of the total number of IPv6 packets received that have a TTL larger than that of a previously received identical packet. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.11,SMF-MIB::smfPerfIpv6HAVAssistsReqdTotal,Counter32,read-only,,current,,A counter of the total number of IPv6 packets received that required the Hash Assist Value (HAV) for DPD. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.1.12,SMF-MIB::smfPerfIpv6DpdHeaderInsertionsTotal,Counter32,read-only,,current,,A counter of the total number of IPv6 packets received that the device inserted the DPD header option. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgSmfSysUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2,SMF-MIB::smfPerfInterfaceGroup,,,,,,
.1.3.6.1.3.126.1.4.2.1,SMF-MIB::smfPerfIpv4InterfacePerfTable,,not-accessible,,current,,The SMF Interface Performance Table describes the SMF counters per interface.
.1.3.6.1.3.126.1.4.2.1.1,SMF-MIB::smfPerfIpv4InterfacePerfEntry,,not-accessible,smfCfgIfIndex,current,,The SMF Interface Performance entry describes the statistics for a particular node interface.
.1.3.6.1.3.126.1.4.2.1.1.1,SMF-MIB::smfPerfIpv4MultiPktsRecvPerIf,Counter32,read-only,,current,,A counter of the number of multicast IP packets received by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.1.1.2,SMF-MIB::smfPerfIpv4MultiPktsForwardedPerIf,Counter32,read-only,,current,,A counter of the number of multicast IP packets forwarded by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.1.1.3,SMF-MIB::smfPerfIpv4DuplMultiPktsDetectedPerIf,Counter32,read-only,,current,,A counter of the number of duplicate multicast IP packets detected by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.1.1.4,SMF-MIB::smfPerfIpv4DroppedMultiPktsTTLExceededPerIf,Counter32,read-only,,current,,A counter of the total number of dropped multicast IPv4 packets by the SMF process on this device on this interface due to TTL exceeded. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.1.1.5,SMF-MIB::smfPerfIpv4TTLLargerThanPreviousPerIf,Counter32,read-only,,current,,A counter of the total number of IPv4 packets received by the SMF process on this device on this interface that have a TTL larger than that of a previously received identical packet. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2,SMF-MIB::smfPerfIpv6InterfacePerfTable,,not-accessible,,current,,The SMF Interface Performance Table describes the SMF counters per interface.
.1.3.6.1.3.126.1.4.2.2.1,SMF-MIB::smfPerfIpv6InterfacePerfEntry,,not-accessible,smfCfgIfIndex,current,,The SMF Interface Performance entry describes the counters for a particular node interface.
.1.3.6.1.3.126.1.4.2.2.1.1,SMF-MIB::smfPerfIpv6MultiPktsRecvPerIf,Counter32,read-only,,current,,A counter of the number of multicast IP packets received by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2.1.2,SMF-MIB::smfPerfIpv6MultiPktsForwardedPerIf,Counter32,read-only,,current,,A counter of the number of multicast IP packets forwarded by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2.1.3,SMF-MIB::smfPerfIpv6DuplMultiPktsDetectedPerIf,Counter32,read-only,,current,,A counter of the number of duplicate multicast IP packets detected by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2.1.4,SMF-MIB::smfPerfIpv6DroppedMultiPktsTTLExceededPerIf,Counter32,read-only,,current,,A counter of the number of dropped multicast IP packets by the SMF process on this device on this interface due to TTL exceeded. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2.1.5,SMF-MIB::smfPerfIpv6TTLLargerThanPreviousPerIf,Counter32,read-only,,current,,A counter of the total number of IPv6 packets received that have a TTL larger than that of a previously received identical packet by the SMF process on this device on this interface. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2.1.6,SMF-MIB::smfPerfIpv6HAVAssistsReqdPerIf,Counter32,read-only,,current,,A counter of the total number of IPv6 packets received by the SMF process on this device on this interface that required the HAV assist for DPD. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.1.4.2.2.1.7,SMF-MIB::smfPerfIpv6DpdHeaderInsertionsPerIf,Counter32,read-only,,current,,A counter of the total number of IPv6 packets received by the SMF process on this device on this interface that the device inserted the DPD header option. There is the potential for a counter discontinuity in this object if the system SMF process has been disabled and later enabled on this interface. In order to check for the occurrence of such a discontinuity when monitoring this counter object, it is recommended that the smfCfgIfSmfUpTime object also be monitored.
.1.3.6.1.3.126.2,SMF-MIB::smfMIBConformance,,,,,,
.1.3.6.1.3.126.2.1,SMF-MIB::smfCompliances,,,,,,
.1.3.6.1.3.126.2.1.1,SMF-MIB::smfBasicCompliance,,,,,,The basic implementation requirements for managed network entities that implement the SMF RSSA process.
.1.3.6.1.3.126.2.1.2,SMF-MIB::smfFullCompliance,,,,,,The full implementation requirements for managed network entities that implement the SMF RSSA process.
.1.3.6.1.3.126.2.2,SMF-MIB::smfMIBGroups,,,,,,
.1.3.6.1.3.126.2.2.1,SMF-MIB::smfCapabObjectsGroup,,,,,,Set of SMF configuration objects implemented in this module.
.1.3.6.1.3.126.2.2.2,SMF-MIB::smfConfigObjectsGroup,,,,,,Set of SMF configuration objects implemented in this module.
.1.3.6.1.3.126.2.2.3,SMF-MIB::smfStateObjectsGroup,,,,,,Set of SMF state objects implemented in this module.
.1.3.6.1.3.126.2.2.4,SMF-MIB::smfPerfObjectsGroup,,,,,,Set of SMF performance objects implemented in this module by total and per interface.
.1.3.6.1.3.126.2.2.5,SMF-MIB::smfNotifObjectsGroup,,,,,,Set of SMF notification control objects implemented in this module.
.1.3.6.1.3.126.2.2.6,SMF-MIB::smfNotificationsGroup,,,,,,Set of SMF notifications implemented in this module.
.1.3.6.1.4,SNMPv2-SMI::private,,,,,,
.1.3.6.1.4.1,SNMPv2-SMI::enterprises,,,,,,
.1.3.6.1.4.1.2,IBM-6611-APPN-MIB::ibm,,,,,,
.1.3.6.1.4.1.2.6,IBM-6611-APPN-MIB::ibmProd,,,,,,
.1.3.6.1.4.1.2.6.2,IBM-6611-APPN-MIB::ibm6611,,,,,,
.1.3.6.1.4.1.2.6.2.13,IBM-6611-APPN-MIB::ibmappn,,,,,,
.1.3.6.1.4.1.2.6.2.13.1,IBM-6611-APPN-MIB::ibmappnNode,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.1,IBM-6611-APPN-MIB::ibmappnGeneralInfoAndCaps,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.1.1,IBM-6611-APPN-MIB::ibmappnNodeCpName,OCTET,read-only,,mandatory,,Administratively-assigned network name for this node in the format NETID.CPNAME.
.1.3.6.1.4.1.2.6.2.13.1.1.2,IBM-6611-APPN-MIB::ibmappnNodeNetid,OCTET,read-only,,mandatory,,Administratively-assigned APPN network identification, which can be from one to eight characters. This ID is used with the control point name to create a fully-qualified control point name.
.1.3.6.1.4.1.2.6.2.13.1.1.3,IBM-6611-APPN-MIB::ibmappnNodeBlockNum,OCTET,read-only,,mandatory,,The block number is the first three digits of the node_id. These 3 hexadecimal digits identify the product and are not configurable.
.1.3.6.1.4.1.2.6.2.13.1.1.4,IBM-6611-APPN-MIB::ibmappnNodeIdNum,OCTET,read-only,,mandatory,,The ID number is the last 5 digits of the node_id. These 5 hexadecimal digits are administratively defined and combined with the 3 digit block number form the node_id. This node_id is used to identify the local node and is include in APPN alerts as well as being included in XIDs. A unique value is required for connections to SNA sub-area.
.1.3.6.1.4.1.2.6.2.13.1.1.5,IBM-6611-APPN-MIB::ibmappnNodeType,INTEGER,read-only,,mandatory,networkNode(1):endNode(2):len(4),Type of APPN node, either network, len, or end node.
.1.3.6.1.4.1.2.6.2.13.1.1.6,IBM-6611-APPN-MIB::ibmappnNodeUpTime,TimeTicks,read-only,,mandatory,,Time (in hundredths of a second) since this APPN node was initialized.
.1.3.6.1.4.1.2.6.2.13.1.1.7,IBM-6611-APPN-MIB::ibmappnNodeNegotLs,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports negotiable link stations.
.1.3.6.1.4.1.2.6.2.13.1.1.8,IBM-6611-APPN-MIB::ibmappnNodeSegReasm,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports segment reassembly. This is only supported when segment generation is also supported.
.1.3.6.1.4.1.2.6.2.13.1.1.9,IBM-6611-APPN-MIB::ibmappnNodeBindReasm,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports Bind segment reassembly. This will only be supported when Bind segment generation is also supported.
.1.3.6.1.4.1.2.6.2.13.1.1.10,IBM-6611-APPN-MIB::ibmappnNodeParallelTg,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports parallel TGs.
.1.3.6.1.4.1.2.6.2.13.1.1.11,IBM-6611-APPN-MIB::ibmappnNodeService,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node allows call-in from nodes not defined locally.
.1.3.6.1.4.1.2.6.2.13.1.1.12,IBM-6611-APPN-MIB::ibmappnNodeAdaptiveBindPacing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports adaptive bind pacing.
.1.3.6.1.4.1.2.6.2.13.1.2,IBM-6611-APPN-MIB::ibmappnNnUniqueInfoAndCaps,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.2.1,IBM-6611-APPN-MIB::ibmappnNodeNnRcvRegChar,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports receiving registered characteristics.
.1.3.6.1.4.1.2.6.2.13.1.2.2,IBM-6611-APPN-MIB::ibmappnNodeNnGateway,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this is a gateway node.
.1.3.6.1.4.1.2.6.2.13.1.2.3,IBM-6611-APPN-MIB::ibmappnNodeNnCentralDirectory,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports central directory cache.
.1.3.6.1.4.1.2.6.2.13.1.2.4,IBM-6611-APPN-MIB::ibmappnNodeNnTreeCache,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports route tree cache.
.1.3.6.1.4.1.2.6.2.13.1.2.5,IBM-6611-APPN-MIB::ibmappnNodeNnTreeUpdate,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports incremental_tree_update, which is only supported when tree caching is supported.
.1.3.6.1.4.1.2.6.2.13.1.2.6,IBM-6611-APPN-MIB::ibmappnNodeNnRouteAddResist,INTEGER,read-only,,mandatory,,Route addition resistance is a value that indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.4.1.2.6.2.13.1.2.7,IBM-6611-APPN-MIB::ibmappnNodeNnIsr,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports intermediate session routing.
.1.3.6.1.4.1.2.6.2.13.1.2.8,IBM-6611-APPN-MIB::ibmappnNodeNnFrsn,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This object is the last FRSN sent in a topology update to adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.1.3,IBM-6611-APPN-MIB::ibmappnEnUniqueCaps,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.3.1,IBM-6611-APPN-MIB::ibmappnNodeEnSegGen,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this end node supports segment generation.
.1.3.6.1.4.1.2.6.2.13.1.3.2,IBM-6611-APPN-MIB::ibmappnNodeEnModeCosMap,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this end node supports mode name to COS name mapping.
.1.3.6.1.4.1.2.6.2.13.1.3.3,IBM-6611-APPN-MIB::ibmappnNodeEnLocateCdinit,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this end node supports Locate Cdinit.
.1.3.6.1.4.1.2.6.2.13.1.3.4,IBM-6611-APPN-MIB::ibmappnNodeEnSendRegNames,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node will register its LUs with the adjacent serving network node: NO - do not register names YES - register names
.1.3.6.1.4.1.2.6.2.13.1.3.5,IBM-6611-APPN-MIB::ibmappnNodeEnSendRegChar,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node supports send register characteristics, which is only supported when send registered names is also supported.
.1.3.6.1.4.1.2.6.2.13.1.4,IBM-6611-APPN-MIB::ibmappnPortInformation,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.4.1,IBM-6611-APPN-MIB::ibmappnNodePortTable,,not-accessible,,mandatory,,The Port table describes the configuration and current status of the ports used by APPN. The type of DLC is included in this table as a pointer to the DLC port specific tables.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1,IBM-6611-APPN-MIB::ibmappnNodePortEntry,,not-accessible,ibmappnNodePortName,mandatory,,The Port Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.1,IBM-6611-APPN-MIB::ibmappnNodePortName,OCTET,read-only,,mandatory,,Administratively-assigned name for this APPN port. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.2,IBM-6611-APPN-MIB::ibmappnNodePortState,INTEGER,read-write,,mandatory,inactive(1):pendactive(2):active(3):pendinact(4),Indicates the current state of this port.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.3,IBM-6611-APPN-MIB::ibmappnNodePortDlcType,INTEGER,read-only,,mandatory,other(1):sdlc(2):dls(3):socket(4):ethernet(5):tokenRing(6),The type of DLC interface, distinguished according to the protocol immediately 'below' this layer.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.4,IBM-6611-APPN-MIB::ibmappnNodePortPortType,INTEGER,read-only,,mandatory,leased(1):switched(2):sharedAccessFacilities(3),Identifies the type of line used by this port.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.5,IBM-6611-APPN-MIB::ibmappnNodePortSIMRIM,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether Set Initialization Mode (SIM) and Receive Initialization Mode (RIM) are supported.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.6,IBM-6611-APPN-MIB::ibmappnNodePortLsRole,INTEGER,read-only,,mandatory,primary(1):secondary(2):negotiable(3):abm(4),Initial role for LSs activated through this port, where 'abm' indicates asynchronous balance mode.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.7,IBM-6611-APPN-MIB::ibmappnNodePortMaxRcvBtuSize,INTEGER,read-only,,mandatory,,Maximum Basic Transmission Size (BTU) that a link station on this port can receive.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.8,IBM-6611-APPN-MIB::ibmappnNodePortMaxIframeWindow,INTEGER,read-only,,mandatory,,Maximum number of I-frames that can be received by the XID sender before an acknowledgement is received.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.9,IBM-6611-APPN-MIB::ibmappnNodePortDefLsGoodXids,Counter32,read-only,,mandatory,,The total number of successfull XIDs that have occurred on all defined link stations on this port since the last time this port was started.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.10,IBM-6611-APPN-MIB::ibmappnNodePortDefLsBadXids,Counter32,read-only,,mandatory,,The total number of unsuccessfull XIDs that have occurred on all defined link stations on this port since the last time this port was started.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.11,IBM-6611-APPN-MIB::ibmappnNodePortDynLsGoodXids,Counter32,read-only,,mandatory,,The total number of successfull XIDs that have occurred on all dynamic link stations on this port since the last time this port was started.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.12,IBM-6611-APPN-MIB::ibmappnNodePortDynLsBadXids,Counter32,read-only,,mandatory,,The total number of unsuccessfull XIDs that have occurred on all dynamic link stations on this port since the last time this port was started.
.1.3.6.1.4.1.2.6.2.13.1.4.1.1.13,IBM-6611-APPN-MIB::ibmappnNodePortSpecific,OBJECT,read-only,,mandatory,,Identifies the port specific OBJECT IDENTIFIER that can provide additional information.
.1.3.6.1.4.1.2.6.2.13.1.4.2,IBM-6611-APPN-MIB::ibmappnNodePortIpTable,,not-accessible,,mandatory,,Port table (TCP/IP specific).
.1.3.6.1.4.1.2.6.2.13.1.4.2.1,IBM-6611-APPN-MIB::ibmappnNodePortIpEntry,,not-accessible,ibmappnNodePortIpName,mandatory,,The IP Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.4.2.1.1,IBM-6611-APPN-MIB::ibmappnNodePortIpName,OCTET,read-only,,mandatory,,Administratively-assigned name for this APPN port. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.4.2.1.2,IBM-6611-APPN-MIB::ibmappnNodePortIpPortNum,INTEGER,read-only,,mandatory,,Local TCP/IP port number.
.1.3.6.1.4.1.2.6.2.13.1.4.3,IBM-6611-APPN-MIB::ibmappnNodePortDlsTable,,not-accessible,,mandatory,,Port table (DLS specific).
.1.3.6.1.4.1.2.6.2.13.1.4.3.1,IBM-6611-APPN-MIB::ibmappnNodePortDlsEntry,,not-accessible,ibmappnNodePortDlsName,mandatory,,The DLS Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.4.3.1.1,IBM-6611-APPN-MIB::ibmappnNodePortDlsName,OCTET,read-only,,mandatory,,Administratively-assigned name for this APPN DLS port. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.4.3.1.2,IBM-6611-APPN-MIB::ibmappnNodePortDlsMac,OCTET,read-only,,mandatory,,Local DLS MAC address.
.1.3.6.1.4.1.2.6.2.13.1.4.3.1.3,IBM-6611-APPN-MIB::ibmappnNodePortDlsSap,OCTET,read-only,,mandatory,,Local DLS Sap address.
.1.3.6.1.4.1.2.6.2.13.1.4.4,IBM-6611-APPN-MIB::ibmappnNodePortTrTable,,not-accessible,,mandatory,,Port table (Token Ring specific).
.1.3.6.1.4.1.2.6.2.13.1.4.4.1,IBM-6611-APPN-MIB::ibmappnNodePortTrEntry,,not-accessible,ibmappnNodePortTrName,mandatory,,The TR Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.4.4.1.1,IBM-6611-APPN-MIB::ibmappnNodePortTrName,OCTET,read-only,,mandatory,,Administratively-assigned name for this APPN port. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.4.4.1.2,IBM-6611-APPN-MIB::ibmappnNodePortTrMac,OCTET,read-only,,mandatory,,Local Token Ring MAC address.
.1.3.6.1.4.1.2.6.2.13.1.4.4.1.3,IBM-6611-APPN-MIB::ibmappnNodePortTrSap,OCTET,read-only,,mandatory,,Local Token Ring Sap address.
.1.3.6.1.4.1.2.6.2.13.1.4.5,IBM-6611-APPN-MIB::ibmappnNodePortDlcTraceTable,,not-accessible,,mandatory,,Port table generic DLC trace table.
.1.3.6.1.4.1.2.6.2.13.1.4.5.1,IBM-6611-APPN-MIB::ibmappnNodePortDlcTraceEntry,,not-accessible,ibmappnNodePortDlcTracPortName:ibmappnNodePortDlcTracIndex,mandatory,,The Port name and a dynamic integer are the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.1,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracPortName,OCTET,read-only,,mandatory,,The Port name associated with this this trace table entry.
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.2,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracIndex,INTEGER,read-only,,mandatory,,This index value is updated every time a new trace entry is created which provides a means to retrieve only the updated entries and also provides a simple method of correlating the entries. The table will wrap when the table is full, which will result in previous entries being written over. The mangement station can over come this by retrieving the table using this index to retrieve only the new table entries.
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.3,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracDlcType,INTEGER,read-only,,mandatory,other(1):sdlc(2):dls(3):socket(4):ethernet(5):tokenRing(6),The type of DLC interface, distinguished according to the protocol immediately 'below' this layer.
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.4,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracLocalAddr,OCTET,read-only,,mandatory,,Local address in format described below: other = free form DisplayString ip = ld. ld. ld. ld / 2d tr = lx: lx: lx: lx: lx: lx . lx dlsw = lx: lx: lx: lx: lx: lx . lx ethernet = lx: lx: lx: lx: lx: lx . lx 
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.5,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracRemoteAddr,OCTET,read-only,,mandatory,,Remote Address in the format described below: other = free form DisplayString ip = ld. ld. ld. ld / 2d tr = lx: lx: lx: lx: lx: lx . lx dlsw = lx: lx: lx: lx: lx: lx . lx ethernet = lx: lx: lx: lx: lx: lx . lx 
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.6,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracMsgType,INTEGER,read-only,,mandatory,other(1):unknown(2):request(3):confirm(4):indication(5):response(6),Indicates the type of trace record entry
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.7,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracCmdType,INTEGER,read-only,,mandatory,testFrame(1):respFrame(2):curFrame(3):icrFrame(4):respAck(5):dgrmFrame(6):xidFrame(7):contFrame(8):contedFrame(9):iFrame(10):enterBusy(12):exitBusy(13):haltFrame(14):lsHalted(15):restartLs(16):lsRestarted(17):netBioSnq(18):netBioSnr(19):gnetFrame(20):netdFrame(21):oobFrame(22):alterSap(23):testRsp(24):haltLsNow(25):testReq(26):ipTestFrame(2001):ipRespFrame(2002):ipCurFrame(2003):ipIcrFrame(2004):ipRespAck(2005):ipDgrmFrame(2006):ipXidFrame(2007):ipContFrame(2008):ipContedFrame(2009):ipIFrame(2010):ipEnterBusy(2012):ipExitBusy(2013):ipHaltFrame(2014):ipLsHalted(2015):ipRestartLs(2016):ipLsRestarted(2017):ipNetBioSnq(2018):ipNetBioSnr(2019):ipGnetFrame(2020):ipNetdFrame(2021):ipOobFrame(2022):ipAlterSap(2023):ipTestRsp(2024):ipHaltLsNow(2025):ipTestReq(2026):dlsIpm(4124):trTestFrame(6001):trRespFrame(6002):trCurFrame(6003):trIcrFrame(6004):trRespAck(6005):trDgrmFrame(6006):trXidFrame(6007):trContFrame(6008):trContedFrame(6009):trIFrame(6010):trEnterBusy(6012):trExitBusy(6013):trHaltFrame(6014):trLsHalted(6015):trRestartLs(6016):trLsRestarted(6017):trNetBioSnq(6018):trNetBioSnr(6019):trGnetFrame(6020):trNetdFrame(6021):trOobFrame(6022):trAlterSap(6023):trTestRsp(6024):trHaltLsNow(6025):trTestReq(6026),Indicates the command type of the trace entry.
.1.3.6.1.4.1.2.6.2.13.1.4.5.1.8,IBM-6611-APPN-MIB::ibmappnNodePortDlcTracUseWan,INTEGER,read-only,,mandatory,other(1):notApplicable(2):useUnknown(3):useWan(4):useLan(5),Indicates the type of connection of the trace entry. For example, token ring and ethernet ports will have useLan as connection. For the dls port, it could be either useWan if connection is across Wan via dls sessions, or useLan if connection is to a local attached LAN.
.1.3.6.1.4.1.2.6.2.13.1.5,IBM-6611-APPN-MIB::ibmappnLinkStationInformation,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.5.1,IBM-6611-APPN-MIB::ibmappnNodeLsTable,,not-accessible,,mandatory,,This table contains detail information about the link station configuration and current status.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1,IBM-6611-APPN-MIB::ibmappnNodeLsEntry,,not-accessible,ibmappnNodeLsName,mandatory,,This table is indexed by the link station name.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.1,IBM-6611-APPN-MIB::ibmappnNodeLsName,OCTET,read-only,,mandatory,,Administratively-assigned name for the link station. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.2,IBM-6611-APPN-MIB::ibmappnNodeLsPortName,OCTET,read-only,,mandatory,,Administratively-assigned name for the port. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.3,IBM-6611-APPN-MIB::ibmappnNodeLsDlcType,INTEGER,read-only,,mandatory,other(1):sdlc(2):dls(3):socket(4):ethernet(5):tokenRing(6),The type of DLC interface, distinguished according to the protocol immediately 'below' this layer.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.4,IBM-6611-APPN-MIB::ibmappnNodeLsDynamic,INTEGER,read-only,,mandatory,yes(1):no(2),Identifies whether this resource is a dynamic link station. Dynamic link stations are created when adjacent nodes that have not been locally defined establish a connection with this node.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.5,IBM-6611-APPN-MIB::ibmappnNodeLsState,INTEGER,read-write,,mandatory,inactive(1):pendactive(2):active(3):pendinact(4),State of this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.6,IBM-6611-APPN-MIB::ibmappnNodeLsCpName,OCTET,read-only,,mandatory,,Fully-qualified name of the adjacent node for this link station. The name can be from three to seventeen characters. Format is netid.cpname.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.7,IBM-6611-APPN-MIB::ibmappnNodeLsTgNum,INTEGER,read-only,,mandatory,,Number associated with the TG to this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.8,IBM-6611-APPN-MIB::ibmappnNodeLsLimResource,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the link station is a limited resource. If it is, the TG is deactivated when there are no sessions.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.9,IBM-6611-APPN-MIB::ibmappnNodeLsMigration,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this link station will be used for connections to down-level or migration partners.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.10,IBM-6611-APPN-MIB::ibmappnNodeLsBlockNum,OCTET,read-only,,mandatory,,The block number is the first three digits of the node_id. These 3 hexideimal digits identify the product and are not configurable.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.11,IBM-6611-APPN-MIB::ibmappnNodeLsIdNum,OCTET,read-only,,mandatory,,The ID number is the last 5 digits of the node_id. These 5 hexadecimal digits are administratively defined and combined with the 3 digit block number form the node_id. This node_id is used to identify the local node and is include in APPN alerts as well as being included in XIDs. A unique value is required for connections to SNA sub-area.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.12,IBM-6611-APPN-MIB::ibmappnNodeLsCpCpSession,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether CP-CP sessions are supported by this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.13,IBM-6611-APPN-MIB::ibmappnNodeLsTargetPacingCount,INTEGER,read-only,,mandatory,,Numeric value between 0 and 32767 inclusive indicating the desired pacing window size for BINDs on this TG. The number is significant only when fixed bind pacing is being performed.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.14,IBM-6611-APPN-MIB::ibmappnNodeLsMaxSendBtuSize,INTEGER,read-only,,mandatory,,Numeric value between 0 and 32767 inclusive indicating the desired number of bytes in a Basic Transmission Unit (BTU) that can be sent on this TG. This is an administratively assigned value.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.15,IBM-6611-APPN-MIB::ibmappnNodeLsEffCap,INTEGER,read-only,,mandatory,,The effective capacity is an integer value that indicates the kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.16,IBM-6611-APPN-MIB::ibmappnNodeLsConnCost,INTEGER,read-only,,mandatory,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255, which indicates maximum cost. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.17,IBM-6611-APPN-MIB::ibmappnNodeLsByteCost,INTEGER,read-only,,mandatory,,Relative cost of transmitting a byte over this link. Range is from 0 (lowest cost) to 255. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.18,IBM-6611-APPN-MIB::ibmappnNodeLsSecurity,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),The security is represented as an integer with a range of 1 thru 255 with the most common values enumerated as defined above. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.19,IBM-6611-APPN-MIB::ibmappnNodeLsDelay,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with some of the more common values enumerated. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.20,IBM-6611-APPN-MIB::ibmappnNodeLsUsr1,INTEGER,read-only,,mandatory,,First user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.21,IBM-6611-APPN-MIB::ibmappnNodeLsUsr2,INTEGER,read-only,,mandatory,,Second user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.22,IBM-6611-APPN-MIB::ibmappnNodeLsUsr3,INTEGER,read-only,,mandatory,,Third user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with the TG using this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.23,IBM-6611-APPN-MIB::ibmappnNodeLsInXidBytes,Counter32,read-only,,mandatory,,Number of XID bytes received.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.24,IBM-6611-APPN-MIB::ibmappnNodeLsInMsgBytes,Counter32,read-only,,mandatory,,Number of message (I-frame) bytes received.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.25,IBM-6611-APPN-MIB::ibmappnNodeLsInXidFrames,Counter32,read-only,,mandatory,,Number of XID frames received.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.26,IBM-6611-APPN-MIB::ibmappnNodeLsInMsgFrames,Counter32,read-only,,mandatory,,Number of message (I-frame) frames received.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.27,IBM-6611-APPN-MIB::ibmappnNodeLsOutXidBytes,Counter32,read-only,,mandatory,,Number of XID bytes sent.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.28,IBM-6611-APPN-MIB::ibmappnNodeLsOutMsgBytes,Counter32,read-only,,mandatory,,Number of message (I-frame) bytes sent.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.29,IBM-6611-APPN-MIB::ibmappnNodeLsOutXidFrames,Counter32,read-only,,mandatory,,Number of XID frames sent.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.30,IBM-6611-APPN-MIB::ibmappnNodeLsOutMsgFrames,Counter32,read-only,,mandatory,,Number of message (I-frame) frames sent.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.31,IBM-6611-APPN-MIB::ibmappnNodeLsEchoRsps,Counter32,read-only,,mandatory,,Number of responses returned from adjacent link station. A response should be returned for each test frame sent by this node. Test frames are sent to adjacent nodes periodically to verify connectivity and to measure that actual round trip time, that is the time the test frame is sent until the response is received.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.32,IBM-6611-APPN-MIB::ibmappnNodeLsCurrentDelay,INTEGER,read-only,,mandatory,,The time that it took for the last test signal to be sent and returned from this link station to the adjacent links station. This time is represented in milliseconds.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.33,IBM-6611-APPN-MIB::ibmappnNodeLsMaxDelay,INTEGER,read-only,,mandatory,,The longest time it took for a test signal to be sent and returned from this link station to the adjacent links station. This time is represented in milliseconds .
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.34,IBM-6611-APPN-MIB::ibmappnNodeLsMinDelay,INTEGER,read-only,,mandatory,,The shortest time it took for a test signal to be sent and returned from this link station to the adjacent links station. This time is represented in milliseconds.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.35,IBM-6611-APPN-MIB::ibmappnNodeLsMaxDelayTime,TimeTicks,read-only,,mandatory,,The time (since system up in hundredth of seconds) when the longest delay occurred. This time can be used to identify when this high water mark occurred in relation to the last initialization of the APPN node.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.36,IBM-6611-APPN-MIB::ibmappnNodeLsGoodXids,Counter32,read-only,,mandatory,,The total number of successful XIDs that have occurred on this link station since the time it was started.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.37,IBM-6611-APPN-MIB::ibmappnNodeLsBadXids,Counter32,read-only,,mandatory,,The total number of unsuccessful XIDs that have occurred on this link station since the time it was started.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.38,IBM-6611-APPN-MIB::ibmappnNodeLsSpecific,OBJECT,read-only,,mandatory,,Identifies the DLC specific OBJECT IDENTIFIER that can provide additional information.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.39,IBM-6611-APPN-MIB::ibmappnNodeLsSubState,INTEGER,read-only,,mandatory,inactive(1):sentReqOpnstn(2):pendXidExch(3):sentActAs(4):sentSetMode(5):active(6):sentDeactAsOrd(7):sentDiscOrd(8):sentDestroyTg(9):sentCreateTg(10):sentConnReq(11):pendRcvConnInd(12):pendSendConnRsp(13):sentConnRsp(14):pendDeact(15),State of this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.40,IBM-6611-APPN-MIB::ibmappnNodeLsStartTime,TimeTicks,read-only,,mandatory,,The time (in hundredth of seconds) this link station has been active the last time since the time APPN was initialized.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.41,IBM-6611-APPN-MIB::ibmappnNodeLsActiveTime,TimeTicks,read-only,,mandatory,,The time (in hundredth of seconds) this link station has been in the active state. A zero value indicates the link station has never been active.
.1.3.6.1.4.1.2.6.2.13.1.5.1.1.42,IBM-6611-APPN-MIB::ibmappnNodeLsCurrentStateTime,TimeTicks,read-only,,mandatory,,The time (in hundredth of seconds) the link station is in the current state.
.1.3.6.1.4.1.2.6.2.13.1.5.2,IBM-6611-APPN-MIB::ibmappnNodeLsIpTable,,not-accessible,,mandatory,,Link station table (TCP/IP specific).
.1.3.6.1.4.1.2.6.2.13.1.5.2.1,IBM-6611-APPN-MIB::ibmappnNodeLsIpEntry,,not-accessible,ibmappnNodeLsIpName,mandatory,,The IP Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.5.2.1.1,IBM-6611-APPN-MIB::ibmappnNodeLsIpName,OCTET,read-only,,mandatory,,Administratively-assigned name for this link station. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.5.2.1.2,IBM-6611-APPN-MIB::ibmappnNodeLsIpState,INTEGER,read-only,,mandatory,inactive(1):pendactive(2):active(3):pendinact(4),State of this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.2.1.3,IBM-6611-APPN-MIB::ibmappnNodeLsLocalIpAddr,IpAddress,read-only,,mandatory,,Local IP address.
.1.3.6.1.4.1.2.6.2.13.1.5.2.1.4,IBM-6611-APPN-MIB::ibmappnNodeLsLocalIpPortNum,INTEGER,read-only,,mandatory,,Local TCP/IP port number. The default listening port will be administratively assigned and will dynamically change if this node initiates a session with adjacent node.
.1.3.6.1.4.1.2.6.2.13.1.5.2.1.5,IBM-6611-APPN-MIB::ibmappnNodeLsRemoteIpAddr,IpAddress,read-only,,mandatory,,Remote IP address.
.1.3.6.1.4.1.2.6.2.13.1.5.2.1.6,IBM-6611-APPN-MIB::ibmappnNodeLsRemoteIpPortNum,INTEGER,read-only,,mandatory,,Remote TCP/IP port number.
.1.3.6.1.4.1.2.6.2.13.1.5.3,IBM-6611-APPN-MIB::ibmappnNodeLsDlsTable,,not-accessible,,mandatory,,Ls Table (DLS specific).
.1.3.6.1.4.1.2.6.2.13.1.5.3.1,IBM-6611-APPN-MIB::ibmappnNodeLsDlsEntry,,not-accessible,ibmappnNodeLsDlsName,mandatory,,The DLS Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.5.3.1.1,IBM-6611-APPN-MIB::ibmappnNodeLsDlsName,OCTET,read-only,,mandatory,,Administratively-assigned name for this link station. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.5.3.1.2,IBM-6611-APPN-MIB::ibmappnNodeLsDlsState,INTEGER,read-only,,mandatory,inactive(1):pendactive(2):active(3):pendinact(4),State of this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.3.1.3,IBM-6611-APPN-MIB::ibmappnNodeLsLocalDlsMac,OCTET,read-only,,mandatory,,Local MAC address.
.1.3.6.1.4.1.2.6.2.13.1.5.3.1.4,IBM-6611-APPN-MIB::ibmappnNodeLsLocalDlsSap,OCTET,read-only,,mandatory,,Local SAP address.
.1.3.6.1.4.1.2.6.2.13.1.5.3.1.5,IBM-6611-APPN-MIB::ibmappnNodeLsRemoteDlsMac,OCTET,read-only,,mandatory,,Remote MAC address.
.1.3.6.1.4.1.2.6.2.13.1.5.3.1.6,IBM-6611-APPN-MIB::ibmappnNodeLsRemoteDlsSap,OCTET,read-only,,mandatory,,Remote SAP address.
.1.3.6.1.4.1.2.6.2.13.1.5.4,IBM-6611-APPN-MIB::ibmappnNodeLsTrTable,,not-accessible,,mandatory,,Ls Table (Token Ring specific).
.1.3.6.1.4.1.2.6.2.13.1.5.4.1,IBM-6611-APPN-MIB::ibmappnNodeLsTrEntry,,not-accessible,ibmappnNodeLsTrName,mandatory,,The TR Name is used as the index to this table.
.1.3.6.1.4.1.2.6.2.13.1.5.4.1.1,IBM-6611-APPN-MIB::ibmappnNodeLsTrName,OCTET,read-only,,mandatory,,Administratively-assigned name for this link station. The name can be from one to eight characters.
.1.3.6.1.4.1.2.6.2.13.1.5.4.1.2,IBM-6611-APPN-MIB::ibmappnNodeLsTrState,INTEGER,read-only,,mandatory,inactive(1):pendactive(2):active(3):pendinact(4),State of this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.4.1.3,IBM-6611-APPN-MIB::ibmappnNodeLsLocalTrMac,OCTET,read-only,,mandatory,,Local MAC address.
.1.3.6.1.4.1.2.6.2.13.1.5.4.1.4,IBM-6611-APPN-MIB::ibmappnNodeLsLocalTrSap,OCTET,read-only,,mandatory,,Local SAP address.
.1.3.6.1.4.1.2.6.2.13.1.5.4.1.5,IBM-6611-APPN-MIB::ibmappnNodeLsRemoteTrMac,OCTET,read-only,,mandatory,,Remote MAC address.
.1.3.6.1.4.1.2.6.2.13.1.5.4.1.6,IBM-6611-APPN-MIB::ibmappnNodeLsRemoteTrSap,OCTET,read-only,,mandatory,,Remote SAP address.
.1.3.6.1.4.1.2.6.2.13.1.5.5,IBM-6611-APPN-MIB::ibmappnNodeLsStatusTable,,not-accessible,,mandatory,,This table contains information related to exceptional and potential exceptional conditions that occur during the activation, XID exchange, and termination of the connection.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1,IBM-6611-APPN-MIB::ibmappnNodeLsStatusEntry,,not-accessible,ibmappnNodeLsStatusIndex,mandatory,,This table is indexed by the LsStatusIndex, which is an integer that is continuously updated until it eventually wraps. This provides the management station the ability to retrieve only the updates to the table by using the standard GET NEXT.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.1,IBM-6611-APPN-MIB::ibmappnNodeLsStatusIndex,INTEGER,read-only,,mandatory,,This index is continuous index this table.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.2,IBM-6611-APPN-MIB::ibmappnNodeLsStatusTime,TimeTicks,read-only,,mandatory,,Time (in hundreds of a second) since this node was last initialized.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.3,IBM-6611-APPN-MIB::ibmappnNodeLsStatusLsName,OCTET,read-only,,mandatory,,Administratively-assigned name for this link station.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.4,IBM-6611-APPN-MIB::ibmappnNodeLsStatusCpName,OCTET,read-only,,mandatory,,Administratively-assigned fully-qualified name of the adjacent node partner. This will be provided when the adjacent node has been defined at this node or when the XID sequence has proceeded far enough to to identify the adjacent node. A blank CP name will indicate the name is unknown.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.5,IBM-6611-APPN-MIB::ibmappnNodeLsStatusNodeId,OCTET,read-only,,mandatory,,Adjacent Node id
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.6,IBM-6611-APPN-MIB::ibmappnNodeLsStatusTgNum,INTEGER,read-only,,mandatory,,Number associated with the TG to this link station with a range from 0 to 256. A value of 256 indicates the tg number has not been negotiated and is unknown at this time.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.7,IBM-6611-APPN-MIB::ibmappnNodeLsStatusGeneralSense,OCTET,read-only,,mandatory,,The error sense code associated with the start sequence of activation of a link up to the beginning of the XID sequence.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.8,IBM-6611-APPN-MIB::ibmappnNodeLsStatusNofRetry,INTEGER,read-only,,mandatory,retry(1):noretry(2),Indicates whether Node Operator Facility will retry the start request to activate the link.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.9,IBM-6611-APPN-MIB::ibmappnNodeLsStatusEndSense,OCTET,read-only,,mandatory,,The sense code associated with the termination of the link connection to adjacent node. This includes all sense information included in the disconnect recieved from the lower layer DLCs and also sense information indicating the link termination originated by upper layer APPN components.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.10,IBM-6611-APPN-MIB::ibmappnNodeLsStatusXidLocalSense,OCTET,read-only,,mandatory,,The error sense code associated with the rejection of the XID.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.11,IBM-6611-APPN-MIB::ibmappnNodeLsStatusXidRemoteSense,OCTET,read-only,,mandatory,,The error sense code adjacent node returned to this node indicating the reason the XID was rejected.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.12,IBM-6611-APPN-MIB::ibmappnNodeLsStatusXidByteInError,INTEGER,read-only,,mandatory,na(1000),This identifies the actual byte in the XID that caused the error. The value of zero (0) indicates that the variable has no meaning.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.13,IBM-6611-APPN-MIB::ibmappnNodeLsStatusXidBitInError,INTEGER,read-only,,mandatory,na(8),This identifies the actual bit within the error byte of the XID. This only has meaning when the byte in error is greater than zero.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.14,IBM-6611-APPN-MIB::ibmappnNodeLsStatusDlcType,INTEGER,read-only,,mandatory,other(1):sdlc(2):dls(3):socket(4):ethernet(5):tr(6),This identifies DLC type that was being used when error occurred. This also is used to the format of the local and remote address provided. other = free form DisplayString ip = ld. ld. ld. ld / 2d tr = lx: lx: lx: lx: lx: lx . lx dlsw = lx: lx: lx: lx: lx: lx . lx ethernet = lx: lx: lx: lx: lx: lx . lx 
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.15,IBM-6611-APPN-MIB::ibmappnNodeLsStatusLocalAddr,OCTET,read-only,,mandatory,,This contains a displayable string that identifies the DLC type and appropriate address. See DlcType above for details of the format.
.1.3.6.1.4.1.2.6.2.13.1.5.5.1.16,IBM-6611-APPN-MIB::ibmappnNodeLsStatusRemoteAddr,OCTET,read-only,,mandatory,,This contains a displayable string that identifies the DLC type and appropriate address. See DlcType above for details of the format.
.1.3.6.1.4.1.2.6.2.13.1.6,IBM-6611-APPN-MIB::ibmappnSnmpInformation,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.6.1,IBM-6611-APPN-MIB::ibmappnSnmpInPkts,Counter32,read-only,,mandatory,,Total number of messages delivered to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.2,IBM-6611-APPN-MIB::ibmappnSnmpInGetRequests,Counter32,read-only,,mandatory,,Total number of GET requests delivered to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.3,IBM-6611-APPN-MIB::ibmappnSnmpInGetNexts,Counter32,read-only,,mandatory,,Total number of GETNEXT requests delivered to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.4,IBM-6611-APPN-MIB::ibmappnSnmpInSetRequests,Counter32,read-only,,mandatory,,Total number of SET requests delivered to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.5,IBM-6611-APPN-MIB::ibmappnSnmpInTotalVars,Counter32,read-only,,mandatory,,Total number of VARIABLES included in both GET and GETNEXT requests to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.6,IBM-6611-APPN-MIB::ibmappnSnmpInGetVars,Counter32,read-only,,mandatory,,Total number of VARIBLES included in all GET requests to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.7,IBM-6611-APPN-MIB::ibmappnSnmpInGetNextVars,Counter32,read-only,,mandatory,,Total number of VARIABLES included in all GETNEXT requests to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.8,IBM-6611-APPN-MIB::ibmappnSnmpInSetVars,Counter32,read-only,,mandatory,,Total number of VARIBLES included in all SET requests to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.9,IBM-6611-APPN-MIB::ibmappnSnmpOutNoSuchNames,Counter32,read-only,,mandatory,,Total number of VARIABLES that could not be found by the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.6.10,IBM-6611-APPN-MIB::ibmappnSnmpOutGenErrs,Counter32,read-only,,mandatory,,Total number of undefined errors that occurred processing SNMP request to the APPN SNMP sub-agent.
.1.3.6.1.4.1.2.6.2.13.1.7,IBM-6611-APPN-MIB::ibmappnMemoryUse,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.7.1,IBM-6611-APPN-MIB::ibmappnMemorySize,INTEGER,read-only,,mandatory,,Size of the shared storage segment, as obtained by storage management from the underlying operating system.
.1.3.6.1.4.1.2.6.2.13.1.7.2,IBM-6611-APPN-MIB::ibmappnMemoryUsed,INTEGER,read-only,,mandatory,,Number of bytes in the segment that are currently allocated to process.
.1.3.6.1.4.1.2.6.2.13.1.7.3,IBM-6611-APPN-MIB::ibmappnMemoryWarnThresh,INTEGER,read-only,,mandatory,,Allocation threshold beyond which storage management considers the storage resources to be constrained.
.1.3.6.1.4.1.2.6.2.13.1.7.4,IBM-6611-APPN-MIB::ibmappnMemoryCritThresh,INTEGER,read-only,,mandatory,,Allocation threshold beyond which storage management considers the storage resources to be critically constrained.
.1.3.6.1.4.1.2.6.2.13.1.8,IBM-6611-APPN-MIB::ibmappnXidInformation,,,,,,
.1.3.6.1.4.1.2.6.2.13.1.8.1,IBM-6611-APPN-MIB::ibmappnNodeDefLsGoodXids,Counter32,read-only,,mandatory,,The current number of successfull XIDs that have occurred on all defined link stations since the last time this node was initialized.
.1.3.6.1.4.1.2.6.2.13.1.8.2,IBM-6611-APPN-MIB::ibmappnNodeDefLsBadXids,Counter32,read-only,,mandatory,,The current number of unsuccessfull XIDs that have occurred on all defined link stations since the last time this node was initialized.
.1.3.6.1.4.1.2.6.2.13.1.8.3,IBM-6611-APPN-MIB::ibmappnNodeDynLsGoodXids,Counter32,read-only,,mandatory,,The current number of successfull XIDs that have occurred on all dynamic link stations since the last time this node was initialized.
.1.3.6.1.4.1.2.6.2.13.1.8.4,IBM-6611-APPN-MIB::ibmappnNodeDynLsBadXids,Counter32,read-only,,mandatory,,The current number of unsuccessfull XIDs that have occurred on all dynamic link stations since the last time this node was initialized.
.1.3.6.1.4.1.2.6.2.13.2,IBM-6611-APPN-MIB::ibmappnNn,,,,,,
.1.3.6.1.4.1.2.6.2.13.2.1,IBM-6611-APPN-MIB::ibmappnNnTopo,,,,,,
.1.3.6.1.4.1.2.6.2.13.2.1.1,IBM-6611-APPN-MIB::ibmappnNnTopoMaxNodes,INTEGER,read-only,,mandatory,,Maximum number of nodes allowed in the APPN topology database. This administratively assigned value must be equal to or greater than the maximum total number of end nodes and network nodes. If the number of nodes exceeds this value, APPN will issue an Alert and the node can no longer participate as a network node.
.1.3.6.1.4.1.2.6.2.13.2.1.2,IBM-6611-APPN-MIB::ibmappnNnTopoCurNumNodes,Gauge32,read-only,,mandatory,,Current number of nodes in this node's topology database. If this value exceeds the maximum number of nodes allowed (NnTopoMaxNodes), APPN alert CPDB002 is issued.
.1.3.6.1.4.1.2.6.2.13.2.1.3,IBM-6611-APPN-MIB::ibmappnNnTopoInTdus,Counter32,read-only,,mandatory,,Total number of TDUs received from all adjacent NN since last initialization.
.1.3.6.1.4.1.2.6.2.13.2.1.4,IBM-6611-APPN-MIB::ibmappnNnTopoOutTdus,Counter32,read-only,,mandatory,,Total number of TDUs built by this node to be sent to all adjacent NN since last initialization.
.1.3.6.1.4.1.2.6.2.13.2.1.5,IBM-6611-APPN-MIB::ibmappnNnTopoNodeLowRsns,Counter32,read-only,,mandatory,,Total number of topology node updates received by this node with a RSN less than the current RSN. Both even and odd RSN are included in this count. These TDUs are not errors, but result when TDUs are broadcast to all adjacent network nodes. No update to this node's topology database occurs, but this node will send a TDU with it's higher RSN to the adjacent node that sent this low RSN.
.1.3.6.1.4.1.2.6.2.13.2.1.6,IBM-6611-APPN-MIB::ibmappnNnTopoNodeEqualRsns,Counter32,read-only,,mandatory,,Total number of topology node updates received by this node with a RSN equal to the current RSN. Both even and odd RSN are included in this count. These TDUs are not errors, but result when TDUs are broadcast to all adjacent network nodes. No update to this node's topology database occurs.
.1.3.6.1.4.1.2.6.2.13.2.1.7,IBM-6611-APPN-MIB::ibmappnNnTopoNodeGoodHighRsns,Counter32,read-only,,mandatory,,Total number of topology node updates received by this node with a RSN greater than the current RSN. This results in updating this nodes topology and broadcasting a TDU to all adjacent network nodes. It is not required to send a TDU to the sender of this update because that node already has the update.
.1.3.6.1.4.1.2.6.2.13.2.1.8,IBM-6611-APPN-MIB::ibmappnNnTopoNodeBadHighRsns,Counter32,read-only,,mandatory,,Total number of topology node updates received by this node with an odd RSN greater than the current RSN. These updates represent a topology inconsistency detected by one of the APPN network nodes. This results in updating this nodes topology and broadcasting a TDU to all adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.2.1.9,IBM-6611-APPN-MIB::ibmappnNnTopoNodeStateUpdates,Counter32,read-only,,mandatory,,Total number of topology Node records built as a result of internally detected node state changes that affect APPN topology and routing. Updates are sent via TDUs to all adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.2.1.10,IBM-6611-APPN-MIB::ibmappnNnTopoNodeErrors,Counter32,read-only,,mandatory,,Total number of topology node records inconsistencies detected by this node. This occurs when this node attempts to update its topology database and detects a data inconsistency. This node will create a TDU with the current RSN incremented to the next odd number and broadcast it to all adjacent NNs.
.1.3.6.1.4.1.2.6.2.13.2.1.11,IBM-6611-APPN-MIB::ibmappnNnTopoNodeTimerUpdates,Counter32,read-only,,mandatory,,Total number of topology node records built for this node's resource due to timer updates. Updates are sent via TDUs to all adjacent network nodes. These updates insure other network nodes do not delete this node's resources from their topology database.
.1.3.6.1.4.1.2.6.2.13.2.1.12,IBM-6611-APPN-MIB::ibmappnNnTopoNodePurges,Counter32,read-only,,mandatory,,Total number of topology node records purged from this node's topology database. This occurs when a node has not been updated in a specified amount of time. The owning node is responsible for broadcasting updates for its resource that it wants kept in the network topology.
.1.3.6.1.4.1.2.6.2.13.2.1.13,IBM-6611-APPN-MIB::ibmappnNnTopoTgLowRsns,Counter32,read-only,,mandatory,,Total number of topology TG updates received by this node with a RSN less than the current RSN. Both even and odd RSN are included in this count. These TDUs are not errors, but result when TDUs are broadcast to all adjacent network nodes. No update to this node's topology database occurs, but this node will send a TDU with it's higher RSN to the sender of the low RSN.
.1.3.6.1.4.1.2.6.2.13.2.1.14,IBM-6611-APPN-MIB::ibmappnNnTopoTgEqualRsns,Counter32,read-only,,mandatory,,Total number of topology TG updates received by this node with a RSN equal to the current RSN. Both even and odd RSN are included in this count. These TDUs are not errors, but result when TDUs are broadcast to all adjacent network nodes. No update to this node's topology database occurs.
.1.3.6.1.4.1.2.6.2.13.2.1.15,IBM-6611-APPN-MIB::ibmappnNnTopoTgGoodHighRsns,Counter32,read-only,,mandatory,,Total number of topology TG updates received by this node with a RSN greater than the current RSN. This results in updating this nodes topology and broadcasting the update to all adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.2.1.16,IBM-6611-APPN-MIB::ibmappnNnTopoTgBadHighRsns,Counter32,read-only,,mandatory,,Total number of topology TG updates received by this node with an odd RSN greater than the current RSN. These updates represent a topology inconsistency detected by one of the APPN network nodes. This results in updating this nodes topology and broadcasting a TDU to all adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.2.1.17,IBM-6611-APPN-MIB::ibmappnNnTopoTgStateUpdates,Counter32,read-only,,mandatory,,Total number of topology TG records built as a result of internally detected node state changes that affect APPN topology and routing. Updates are sent via TDUs to all adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.2.1.18,IBM-6611-APPN-MIB::ibmappnNnTopoTgErrors,Counter32,read-only,,mandatory,,Total number of topology TG records inconsistencies detected by this node. This occurs when this node attempts to update its topology database and detects a data inconsistency. This node will create a TDU with the current RSN incremented to the next odd number and broadcast it to all adjacent NNs.
.1.3.6.1.4.1.2.6.2.13.2.1.19,IBM-6611-APPN-MIB::ibmappnNnTopoTgTimerUpdates,Counter32,read-only,,mandatory,,Total number of topology TG records built for this node's resource due to timer updates. Updates are sent via TDUs to all adjacent network nodes. These updates insure other network nodes do not delete this node's resources from their topology database.
.1.3.6.1.4.1.2.6.2.13.2.1.20,IBM-6611-APPN-MIB::ibmappnNnTopoTgPurges,Counter32,read-only,,mandatory,,Total number of topology TG records purged from this node's topology database. This occurs when a TG has not been updated in a specified amount of time. The owning node is responsible for broadcasting updates for its resource that it wants to keep in the network topology.
.1.3.6.1.4.1.2.6.2.13.2.1.21,IBM-6611-APPN-MIB::ibmappnNnTopoTotalRouteCalcs,Counter32,read-only,,mandatory,,Number of routes calculated for all class of services since the last initialization.
.1.3.6.1.4.1.2.6.2.13.2.1.22,IBM-6611-APPN-MIB::ibmappnNnTopoTotalRouteRejs,Counter32,read-only,,mandatory,,Number of route requests for all class of services that could not be calculated since last initialization.
.1.3.6.1.4.1.2.6.2.13.2.1.23,IBM-6611-APPN-MIB::ibmappnNnTopoRouteTable,,not-accessible,,mandatory,,Table containing an entry for every Class of Service that it has calculated a route for.
.1.3.6.1.4.1.2.6.2.13.2.1.23.1,IBM-6611-APPN-MIB::ibmappnNnTopoRouteEntry,,not-accessible,ibmappnNnTopoRouteCos,mandatory,,The Class of Service name is the index for this table.
.1.3.6.1.4.1.2.6.2.13.2.1.23.1.1,IBM-6611-APPN-MIB::ibmappnNnTopoRouteCos,OCTET,read-only,,mandatory,,The Class of Service for the route.
.1.3.6.1.4.1.2.6.2.13.2.1.23.1.2,IBM-6611-APPN-MIB::ibmappnNnTopoRouteTrees,Counter32,read-only,,mandatory,,Number of routes tree caches built for this Class of Service since the last initialization.
.1.3.6.1.4.1.2.6.2.13.2.1.23.1.3,IBM-6611-APPN-MIB::ibmappnNnTopoRouteCalcs,Counter32,read-only,,mandatory,,Number of routes calculated since last initialization.
.1.3.6.1.4.1.2.6.2.13.2.1.23.1.4,IBM-6611-APPN-MIB::ibmappnNnTopoRouteRejs,Counter32,read-only,,mandatory,,Number of route requests that could not be calculated since last initialization.
.1.3.6.1.4.1.2.6.2.13.2.2,IBM-6611-APPN-MIB::ibmappnNnAdjNodeTable,,not-accessible,,mandatory,,Table containing an entry for every node. The information kept in this table is the last FRSN sent and received, the status of the CP-CP sessions, and a gauge that indicates the number of outstanding TDUs.
.1.3.6.1.4.1.2.6.2.13.2.2.1,IBM-6611-APPN-MIB::ibmappnNnAdjNodeEntry,,not-accessible,ibmappnNnAdjNodeAdjName,mandatory,,The adjacent node name is the index for this table.
.1.3.6.1.4.1.2.6.2.13.2.2.1.1,IBM-6611-APPN-MIB::ibmappnNnAdjNodeAdjName,OCTET,read-only,,mandatory,,An administratively-assigned fully-qualified name of this node's adjacent network node.
.1.3.6.1.4.1.2.6.2.13.2.2.1.2,IBM-6611-APPN-MIB::ibmappnNnAdjNodeCpCpSessStatus,INTEGER,read-only,,mandatory,active(1):conLoserActive(2):conWinnerActive(3):inactive(4),Indicates the state of CP-CP sessions between this node and adjacent network and end nodes. Incative indicates no CP-CP sessions exists between this node and the adjacent node. Active indicates CP-CP sessons are active using both the ConWinner and ConLoser sessions. The session initiated by this node is refered to as the ConWinner session and is used by this node to send to the adjacent node. The ConLoserr session is initiated by the adjacent node and is used by this node to receive from the adjacent node.
.1.3.6.1.4.1.2.6.2.13.2.2.1.3,IBM-6611-APPN-MIB::ibmappnNnAdjNodeOutOfSeqTdus,Gauge32,read-only,,mandatory,,Number of out of sequence Topology Database Updates (TDUs). In a quiesced state, this value is zero. In normal operation, the value varies depending on the network environment.
.1.3.6.1.4.1.2.6.2.13.2.2.1.4,IBM-6611-APPN-MIB::ibmappnNnAdjNodeLastFrsnSent,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last TDU sent to this adjacent node.
.1.3.6.1.4.1.2.6.2.13.2.2.1.5,IBM-6611-APPN-MIB::ibmappnNnAdjNodeLastFrsnRcvd,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last TDU received from this adjacent node.
.1.3.6.1.4.1.2.6.2.13.2.3,IBM-6611-APPN-MIB::ibmappnNnTopology,,,,,,
.1.3.6.1.4.1.2.6.2.13.2.3.1,IBM-6611-APPN-MIB::ibmappnNnTopologyTable,,not-accessible,,mandatory,,Portion of the APPN routing table that describes all of the APPN network nodes and virtual nodes known to this node.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1,IBM-6611-APPN-MIB::ibmappnNnTopologyEntry,,not-accessible,ibmappnNnNodeName,mandatory,,The fully-qualified node name is used to index this table.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.1,IBM-6611-APPN-MIB::ibmappnNnNodeName,OCTET,read-only,,mandatory,,Administratively-assigned network name that is locally defined at each network node in the format NETID.CPNAME.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.2,IBM-6611-APPN-MIB::ibmappnNnNodeFrsn,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.3,IBM-6611-APPN-MIB::ibmappnNnNodeEntryTimeLeft,INTEGER,read-only,,mandatory,,Number of days before deletion of this network node entry. Range is 0-31.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.4,IBM-6611-APPN-MIB::ibmappnNnNodeType,INTEGER,read-only,,mandatory,networknode(1):virtualnode(3),Type of APPN node.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.5,IBM-6611-APPN-MIB::ibmappnNnNodeRsn,INTEGER,read-only,,mandatory,,Resource sequence number that is assigned and controlled by the network node that owns this resource. This is always an even 32-bit number unless an error has occurred.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.6,IBM-6611-APPN-MIB::ibmappnNnNodeRouteAddResist,INTEGER,read-only,,mandatory,,Route addition resistance indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.7,IBM-6611-APPN-MIB::ibmappnNnNodeCongested,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node is congested. This node is not be included in route selection by other nodes when this congestion exists.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.8,IBM-6611-APPN-MIB::ibmappnNnNodeIsrDepleted,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether intermediate session routing resources are depleted. This node is not included in intermediate route selection by other nodes when resources are depleted.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.9,IBM-6611-APPN-MIB::ibmappnNnNodeEndptDepleted,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether session endpoint resources are depleted.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.10,IBM-6611-APPN-MIB::ibmappnNnNodeQuiescing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is quiescing. This node is not included in route selection by other nodes when the node is quiescing.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.11,IBM-6611-APPN-MIB::ibmappnNnNodeGateway,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node provide gateway functions.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.12,IBM-6611-APPN-MIB::ibmappnNnNodeCentralDirectory,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is central directory.
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.13,IBM-6611-APPN-MIB::ibmappnNnNodeIsr,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports intermediate session routing (ISR).
.1.3.6.1.4.1.2.6.2.13.2.3.1.1.14,IBM-6611-APPN-MIB::ibmappnNnNodeChainSupport,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports chaining.
.1.3.6.1.4.1.2.6.2.13.2.3.2,IBM-6611-APPN-MIB::ibmappnNnTgTopologyTable,,not-accessible,,mandatory,,Portion of the APPN topology database that describes all of the APPN transmissions groups used by the APPN network nodes.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1,IBM-6611-APPN-MIB::ibmappnNnTgTopologyEntry,,not-accessible,ibmappnNnTgOwner:ibmappnNnTgDest:ibmappnNnTgNum,mandatory,,This table requires three indexes to provide a unique index. The indexes are the owning or originating CPname, the destination CPname, and the TG number.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.1,IBM-6611-APPN-MIB::ibmappnNnTgOwner,OCTET,read-only,,mandatory,,Administratively-assigned name for the originating node for this TG. The format is NETID.CPNAME and is the same name specified in the node table.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.2,IBM-6611-APPN-MIB::ibmappnNnTgDest,OCTET,read-only,,mandatory,,Administratively-assigned fully-qualified network name for the destination node for this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.3,IBM-6611-APPN-MIB::ibmappnNnTgNum,INTEGER,read-only,,mandatory,,Number associated with this transmission group. Range is 0-255.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.4,IBM-6611-APPN-MIB::ibmappnNnTgFrsn,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.5,IBM-6611-APPN-MIB::ibmappnNnTgEntryTimeLeft,INTEGER,read-only,,mandatory,,Number of days before deletion of this network node TG entry. Range is 0-31.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.6,IBM-6611-APPN-MIB::ibmappnNnTgDestVirtual,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the destination node is a virtual node.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.7,IBM-6611-APPN-MIB::ibmappnNnTgDlcData,OCTET,read-only,,mandatory,,DLC specific data related to the link connection network. Token-Ring - MAC/SAP X.25 Switched - dial digits X.21 Switched - dial digits Circuit Swtch - dial digits
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.8,IBM-6611-APPN-MIB::ibmappnNnTgRsn,INTEGER,read-only,,mandatory,,Current owning node's resource sequence number for this resource.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.9,IBM-6611-APPN-MIB::ibmappnNnTgOperational,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the transmission group is operational.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.10,IBM-6611-APPN-MIB::ibmappnNnTgQuiescing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the transmission group is quiescing.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.11,IBM-6611-APPN-MIB::ibmappnNnTgCpCpSession,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether CP-CP sessions are supported on this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.12,IBM-6611-APPN-MIB::ibmappnNnTgEffCap,INTEGER,read-only,,mandatory,,The effective capacity is an integer value that indicates the kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.13,IBM-6611-APPN-MIB::ibmappnNnTgConnCost,INTEGER,read-only,,mandatory,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255, which indicates maximum cost. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.14,IBM-6611-APPN-MIB::ibmappnNnTgByteCost,INTEGER,read-only,,mandatory,,Relative cost of transmitting a byte over this link. Range is from 0 (lowest cost) to 255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.15,IBM-6611-APPN-MIB::ibmappnNnTgSecurity,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),The security is represented as an integer with a range of 1 thru 255 with the most common values enumerated as defined above. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.16,IBM-6611-APPN-MIB::ibmappnNnTgDelay,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with some of the more common values enumerated. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.17,IBM-6611-APPN-MIB::ibmappnNnTgModemClass,INTEGER,read-only,,mandatory,,This is used to have multiple images for a connection network. For a connection network it is the same as in the TG vector; for a non-connection network it is X'00'.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.18,IBM-6611-APPN-MIB::ibmappnNnTgUsr1,INTEGER,read-only,,mandatory,,First user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.19,IBM-6611-APPN-MIB::ibmappnNnTgUsr2,INTEGER,read-only,,mandatory,,Second user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.2.1.20,IBM-6611-APPN-MIB::ibmappnNnTgUsr3,INTEGER,read-only,,mandatory,,Third user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.3,IBM-6611-APPN-MIB::ibmappnNnTopologyFRTable,,not-accessible,,mandatory,,Portion of the APPN routing table that describes all of the APPN network nodes and virtual nodes known to this node.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1,IBM-6611-APPN-MIB::ibmappnNnTopologyFREntry,,not-accessible,ibmappnNnNodeFRFrsn:ibmappnNnNodeFRName,mandatory,,This table is indexed by two columns: FRSN, followed by fully-qualified node name.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.1,IBM-6611-APPN-MIB::ibmappnNnNodeFRName,OCTET,read-only,,mandatory,,Administratively-assigned network name that is locally defined at each network node in the format NETID.CPNAME.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.2,IBM-6611-APPN-MIB::ibmappnNnNodeFRFrsn,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.3,IBM-6611-APPN-MIB::ibmappnNnNodeFREntryTimeLeft,INTEGER,read-only,,mandatory,,Number of days before deletion of this network node entry. Range is 0-31.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.4,IBM-6611-APPN-MIB::ibmappnNnNodeFRType,INTEGER,read-only,,mandatory,networknode(1):virtualnode(3),Type of APPN node.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.5,IBM-6611-APPN-MIB::ibmappnNnNodeFRRsn,INTEGER,read-only,,mandatory,,Resource sequence number that is assigned and controlled by the network node that owns this resource. This is always an even 32-bit number unless an error has occurred.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.6,IBM-6611-APPN-MIB::ibmappnNnNodeFRRouteAddResist,INTEGER,read-only,,mandatory,,Route addition resistance indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.7,IBM-6611-APPN-MIB::ibmappnNnNodeFRCongested,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node is congested. This node is not be included in route selection by other nodes when this congestion exists.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.8,IBM-6611-APPN-MIB::ibmappnNnNodeFRIsrDepleted,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether intermediate session routing resources are depleted. This node is not included in intermediate route selection by other nodes when resources are depleted.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.9,IBM-6611-APPN-MIB::ibmappnNnNodeFREndptDepleted,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether session endpoint resources are depleted.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.10,IBM-6611-APPN-MIB::ibmappnNnNodeFRQuiescing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is quiescing. This node is not included in route selection by other nodes when the node is quiescing.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.11,IBM-6611-APPN-MIB::ibmappnNnNodeFRGateway,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node provide gateway functions.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.12,IBM-6611-APPN-MIB::ibmappnNnNodeFRCentralDirectory,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is central directory.
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.13,IBM-6611-APPN-MIB::ibmappnNnNodeFRIsr,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports intermediate session routing (ISR).
.1.3.6.1.4.1.2.6.2.13.2.3.3.1.14,IBM-6611-APPN-MIB::ibmappnNnNodeFRChainSupport,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports chaining.
.1.3.6.1.4.1.2.6.2.13.2.3.4,IBM-6611-APPN-MIB::ibmappnNnTgTopologyFRTable,,not-accessible,,mandatory,,Portion of the APPN topology database that describes all of the APPN transmissions groups used by the APPN network nodes.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1,IBM-6611-APPN-MIB::ibmappnNnTgTopologyFREntry,,not-accessible,ibmappnNnTgFRFrsn:ibmappnNnTgFROwner:ibmappnNnTgFRDest:ibmappnNnTgFRNum,mandatory,,This table is indexed by four columns: FRSN, TG owner fully-qualified node name, TG destination fully-qualified node name, and TG number.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.1,IBM-6611-APPN-MIB::ibmappnNnTgFROwner,OCTET,read-only,,mandatory,,Administratively-assigned name for the originating node for this TG. The format is NETID.CPNAME and is the same name specified in the node table.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.2,IBM-6611-APPN-MIB::ibmappnNnTgFRDest,OCTET,read-only,,mandatory,,Administratively-assigned fully-qualified network name for the destination node for this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.3,IBM-6611-APPN-MIB::ibmappnNnTgFRNum,INTEGER,read-only,,mandatory,,Number associated with this transmission group. Range is 0-255.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.4,IBM-6611-APPN-MIB::ibmappnNnTgFRFrsn,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This FRSN indicates the last time this resource was updated at this node.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.5,IBM-6611-APPN-MIB::ibmappnNnTgFREntryTimeLeft,INTEGER,read-only,,mandatory,,Number of days before deletion of this network node TG entry. Range is 0-31.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.6,IBM-6611-APPN-MIB::ibmappnNnTgFRDestVirtual,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the destination node is a virtual node.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.7,IBM-6611-APPN-MIB::ibmappnNnTgFRDlcData,OCTET,read-only,,mandatory,,DLC specific data related to the link connection network. Token-Ring - MAC/SAP X.25 Switched - dial digits X.21 Switched - dial digits Circuit Swtch - dial digits
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.8,IBM-6611-APPN-MIB::ibmappnNnTgFRRsn,INTEGER,read-only,,mandatory,,Current owning node's resource sequence number for this resource.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.9,IBM-6611-APPN-MIB::ibmappnNnTgFROperational,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the transmission group is operational.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.10,IBM-6611-APPN-MIB::ibmappnNnTgFRQuiescing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the transmission group is quiescing.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.11,IBM-6611-APPN-MIB::ibmappnNnTgFRCpCpSession,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether CP-CP sessions are supported on this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.12,IBM-6611-APPN-MIB::ibmappnNnTgFREffCap,INTEGER,read-only,,mandatory,,The effective capacity is an integer value that indicates the kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.13,IBM-6611-APPN-MIB::ibmappnNnTgFRConnCost,INTEGER,read-only,,mandatory,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255, which indicates maximum cost. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.14,IBM-6611-APPN-MIB::ibmappnNnTgFRByteCost,INTEGER,read-only,,mandatory,,Relative cost of transmitting a byte over this link. Range is from 0 (lowest cost) to 255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.15,IBM-6611-APPN-MIB::ibmappnNnTgFRSecurity,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),The security is represented as an integer with a range of 1 thru 255 with the most common values enumerated as defined above. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.16,IBM-6611-APPN-MIB::ibmappnNnTgFRDelay,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with some of the more common values enumerated. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.17,IBM-6611-APPN-MIB::ibmappnNnTgFRModemClass,INTEGER,read-only,,mandatory,,This is used to have multiple images for a connection network. For a connection network it is the same as in the TG vector; for a non-connection network it is X'00'.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.18,IBM-6611-APPN-MIB::ibmappnNnTgFRUsr1,INTEGER,read-only,,mandatory,,First user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.19,IBM-6611-APPN-MIB::ibmappnNnTgFRUsr2,INTEGER,read-only,,mandatory,,Second user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.2.3.4.1.20,IBM-6611-APPN-MIB::ibmappnNnTgFRUsr3,INTEGER,read-only,,mandatory,,Third user-defined TG characteristic for this TG with a range of 0-255. This is an administratively assigned value associated with this TG.
.1.3.6.1.4.1.2.6.2.13.3,IBM-6611-APPN-MIB::ibmappnLocalTopology,,,,,,
.1.3.6.1.4.1.2.6.2.13.3.1,IBM-6611-APPN-MIB::ibmappnLocalThisNode,,,,,,
.1.3.6.1.4.1.2.6.2.13.3.1.1,IBM-6611-APPN-MIB::ibmappnLocalGeneral,,,,,,
.1.3.6.1.4.1.2.6.2.13.3.1.1.1,IBM-6611-APPN-MIB::ibmappnLocalNodeName,OCTET,read-only,,mandatory,,Administratively-assigned fully-qualified name for this node. Format is NETID.CPNAME.
.1.3.6.1.4.1.2.6.2.13.3.1.1.2,IBM-6611-APPN-MIB::ibmappnLocalNodeType,INTEGER,read-only,,mandatory,networknode(1):endnode(2):len(4),Type of APPN node.
.1.3.6.1.4.1.2.6.2.13.3.1.2,IBM-6611-APPN-MIB::ibmappnLocalNnSpecific,,,,,,
.1.3.6.1.4.1.2.6.2.13.3.1.2.1,IBM-6611-APPN-MIB::ibmappnLocalNnRsn,INTEGER,read-only,,mandatory,,Resource sequence number is assigned and controlled by the network node that owns this resource. This is always an even unsigned number unless an error has occurred.
.1.3.6.1.4.1.2.6.2.13.3.1.2.2,IBM-6611-APPN-MIB::ibmappnLocalNnRouteAddResist,INTEGER,read-only,,mandatory,,Route addition resistance indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.4.1.2.6.2.13.3.1.2.3,IBM-6611-APPN-MIB::ibmappnLocalNnCongested,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether this node is congested. Other network nodes stop routing traffic to this node while this flag is on.
.1.3.6.1.4.1.2.6.2.13.3.1.2.4,IBM-6611-APPN-MIB::ibmappnLocalNnIsrDepleted,INTEGER,read-only,,mandatory,yes(1):no(2),Indicate whether intermediated session routing resources are depleted. Other network nodes stop routing traffic through this node while this flag is on.
.1.3.6.1.4.1.2.6.2.13.3.1.2.5,IBM-6611-APPN-MIB::ibmappnLocalNnEndptDepleted,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether session endpoint resources are depleted.
.1.3.6.1.4.1.2.6.2.13.3.1.2.6,IBM-6611-APPN-MIB::ibmappnLocalNnQuiescing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is quiescing.
.1.3.6.1.4.1.2.6.2.13.3.1.2.7,IBM-6611-APPN-MIB::ibmappnLocalNnGateway,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is a gateway.
.1.3.6.1.4.1.2.6.2.13.3.1.2.8,IBM-6611-APPN-MIB::ibmappnLocalNnCentralDirectory,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node is a central directory.
.1.3.6.1.4.1.2.6.2.13.3.1.2.9,IBM-6611-APPN-MIB::ibmappnLocalNnIsr,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports intermediate session routing.
.1.3.6.1.4.1.2.6.2.13.3.1.2.10,IBM-6611-APPN-MIB::ibmappnLocalNnChainSupport,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the node supports chaining.
.1.3.6.1.4.1.2.6.2.13.3.1.2.11,IBM-6611-APPN-MIB::ibmappnLocalNnFrsn,INTEGER,read-only,,mandatory,,Flow reduction sequence numbers (FRSNs) are associated with Topology Database Updates (TDUs) and are unique only within each APPN network node. A TDU can be associated with multiple APPN resources. This object is the last FRSN sent in a topology update to adjacent network nodes.
.1.3.6.1.4.1.2.6.2.13.3.1.3,IBM-6611-APPN-MIB::ibmappnLocalTg,,,,,,
.1.3.6.1.4.1.2.6.2.13.3.1.3.1,IBM-6611-APPN-MIB::ibmappnLocalTgTable,,not-accessible,,mandatory,,TG Table describes all of the TGs owned by this node. The TG destination can be a virtual node, network node, len, or end node.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1,IBM-6611-APPN-MIB::ibmappnLocalTgEntry,,not-accessible,ibmappnLocalTgDest:ibmappnLocalTgNum,mandatory,,This table is indexed by the destination CPname and the TG number.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.1,IBM-6611-APPN-MIB::ibmappnLocalTgDest,OCTET,read-only,,mandatory,,Administratively-assigned name for the destination node for this TG. This is the fully-qualified network node name.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.2,IBM-6611-APPN-MIB::ibmappnLocalTgNum,INTEGER,read-only,,mandatory,,Number associated with this transmission group.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.3,IBM-6611-APPN-MIB::ibmappnLocalTgDestVirtual,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the destination node is a Virtual node.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.4,IBM-6611-APPN-MIB::ibmappnLocalTgDlcData,OCTET,read-only,,mandatory,,DLC specific data related to the link connection network. Token-Ring - MAC/SAP X.25 Switched - dial digits X.21 Switched - dial digits Circuit Swtch - dial digits
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.5,IBM-6611-APPN-MIB::ibmappnLocalTgRsn,INTEGER,read-only,,mandatory,,The resource sequence number is assigned and controlled by the network node that owns this resource. This is always an even unsigned number unless an error has occurred.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.6,IBM-6611-APPN-MIB::ibmappnLocalTgQuiescing,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the Transmission Group is quiescing.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.7,IBM-6611-APPN-MIB::ibmappnLocalTgOperational,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the Transmission Group is operational.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.8,IBM-6611-APPN-MIB::ibmappnLocalTgCpCpSession,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the CP-CP Sessions are supported on this TG.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.9,IBM-6611-APPN-MIB::ibmappnLocalTgEffCap,INTEGER,read-only,,mandatory,,The effective capacity is an integer value that indicates the actual kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.10,IBM-6611-APPN-MIB::ibmappnLocalTgConnCost,INTEGER,read-only,,mandatory,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.11,IBM-6611-APPN-MIB::ibmappnLocalTgByteCost,INTEGER,read-only,,mandatory,,Relative cost of transmitting a byte over this link. Range is from 0 (lowest cost) to 255.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.12,IBM-6611-APPN-MIB::ibmappnLocalTgSecurity,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Security level for this TG.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.13,IBM-6611-APPN-MIB::ibmappnLocalTgDelay,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with some of the more common values enumerated.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.14,IBM-6611-APPN-MIB::ibmappnLocalTgModemClass,INTEGER,read-only,,mandatory,,This is used to have multiple images for a connection network. For a connection network it is the same as in the TG vector and for a non-connection network it is zero.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.15,IBM-6611-APPN-MIB::ibmappnLocalTgUsr1,INTEGER,read-only,,mandatory,,Value of the first user-defined TG characteristic for this TG. Range is 0-255.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.16,IBM-6611-APPN-MIB::ibmappnLocalTgUsr2,INTEGER,read-only,,mandatory,,Value of the second user-defined TG characteristic for this TG. Range is 0-255.
.1.3.6.1.4.1.2.6.2.13.3.1.3.1.1.17,IBM-6611-APPN-MIB::ibmappnLocalTgUsr3,INTEGER,read-only,,mandatory,,Value of the third user-defined TG characteristic for this TG. Range is 0-255.
.1.3.6.1.4.1.2.6.2.13.3.2,IBM-6611-APPN-MIB::ibmappnLocalEnTopology,,,,,,
.1.3.6.1.4.1.2.6.2.13.3.2.1,IBM-6611-APPN-MIB::ibmappnLocalEnTable,,not-accessible,,mandatory,,Portion of the APPN topology database that describes the end nodes known to this node.
.1.3.6.1.4.1.2.6.2.13.3.2.1.1,IBM-6611-APPN-MIB::ibmappnLocalEnEntry,,not-accessible,ibmappnLocalEnName,mandatory,,This table is indexed by the end node CPname.
.1.3.6.1.4.1.2.6.2.13.3.2.1.1.1,IBM-6611-APPN-MIB::ibmappnLocalEnName,OCTET,read-only,,mandatory,,Administratively-assigned fully-qualified name of end node in the format NETID.CPNAME.
.1.3.6.1.4.1.2.6.2.13.3.2.1.1.2,IBM-6611-APPN-MIB::ibmappnLocalEnEntryTimeLeft,INTEGER,read-only,,mandatory,,Number of days before deletion of this end node entry. Range is 0-31.
.1.3.6.1.4.1.2.6.2.13.3.2.1.1.3,IBM-6611-APPN-MIB::ibmappnLocalEnType,INTEGER,read-only,,mandatory,endnode(2):len(4),Type of APPN node (must always be a len or end node).
.1.3.6.1.4.1.2.6.2.13.3.2.2,IBM-6611-APPN-MIB::ibmappnLocalEnTgTable,,not-accessible,,mandatory,,Table describing all of the TGs owned by the end nodes known to this node. The TG destination can be a virtual node, network node, or end node.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1,IBM-6611-APPN-MIB::ibmappnLocalEnTgEntry,,not-accessible,ibmappnLocalEnTgOrigin:ibmappnLocalEnTgDest:ibmappnLocalEnTgNum,mandatory,,This table requires multiple indexes to uniquely identify each TG. They are originating CPname, destination CPname, and the TG number.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.1,IBM-6611-APPN-MIB::ibmappnLocalEnTgOrigin,OCTET,read-only,,mandatory,,Administratively-assigned name for the origination node for this TG. This is the fully-qualified network name.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.2,IBM-6611-APPN-MIB::ibmappnLocalEnTgDest,OCTET,read-only,,mandatory,,Administratively-assigned name for the destination node for this TG. This is the fully-qualified network name.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.3,IBM-6611-APPN-MIB::ibmappnLocalEnTgNum,INTEGER,read-only,,mandatory,,Number associated with this transmission group.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.4,IBM-6611-APPN-MIB::ibmappnLocalEnTgEntryTimeLeft,INTEGER,read-only,,mandatory,,Number of days before deletion of this end node TG entry. Range is 0-31.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.5,IBM-6611-APPN-MIB::ibmappnLocalEnTgDestVirtual,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the destination node is a virtual node.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.6,IBM-6611-APPN-MIB::ibmappnLocalEnTgDlcData,OCTET,read-only,,mandatory,,DLC specific data related to the link connection network. Token-Ring - MAC/SAP X.25 Switched - dial digits X.21 Switched - dial digits Circuit Swtch - dial digits
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.7,IBM-6611-APPN-MIB::ibmappnLocalEnTgOperational,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether the Transmission Group is operational.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.8,IBM-6611-APPN-MIB::ibmappnLocalEnTgCpCpSession,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether CP-CP sessions are supported on this TG.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.9,IBM-6611-APPN-MIB::ibmappnLocalEnTgEffCap,INTEGER,read-only,,mandatory,,The effective capacity is an integer value that indicates the actual kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.10,IBM-6611-APPN-MIB::ibmappnLocalEnTgConnCost,INTEGER,read-only,,mandatory,,Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.11,IBM-6611-APPN-MIB::ibmappnLocalEnTgByteCost,INTEGER,read-only,,mandatory,,Relative cost of transmitting a byte over this link. Range is from 0, which means no cost, to 255.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.12,IBM-6611-APPN-MIB::ibmappnLocalEnTgSecurity,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Security level for this TG.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.13,IBM-6611-APPN-MIB::ibmappnLocalEnTgDelay,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with some of the more common values enumerated.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.14,IBM-6611-APPN-MIB::ibmappnLocalEnTgModemClass,INTEGER,read-only,,mandatory,,This is used to have multiple images for a connection network. For a connection network it is the same as in the TG vector and for a non connection network it is zero.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.15,IBM-6611-APPN-MIB::ibmappnLocalEnTgUsr1,INTEGER,read-only,,mandatory,,First user-defined TG characteristic for this TG. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.16,IBM-6611-APPN-MIB::ibmappnLocalEnTgUsr2,INTEGER,read-only,,mandatory,,Second user-defined TG characteristic for this TG. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.3.2.2.1.17,IBM-6611-APPN-MIB::ibmappnLocalEnTgUsr3,INTEGER,read-only,,mandatory,,Third user-defined TG characteristic for this TG. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.5,IBM-6611-APPN-MIB::ibmappnDir,,,,,,
.1.3.6.1.4.1.2.6.2.13.5.1,IBM-6611-APPN-MIB::ibmappnDirPerf,,,,,,
.1.3.6.1.4.1.2.6.2.13.5.1.1,IBM-6611-APPN-MIB::ibmappnDirMaxCaches,INTEGER,read-only,,mandatory,,Maximum number of cache entries allowed. This is an administratively assigned value.
.1.3.6.1.4.1.2.6.2.13.5.1.2,IBM-6611-APPN-MIB::ibmappnDirCurCaches,Gauge32,read-only,,mandatory,,Current number of cache entries.
.1.3.6.1.4.1.2.6.2.13.5.1.3,IBM-6611-APPN-MIB::ibmappnDirCurHomeEntries,Gauge32,read-only,,mandatory,,Current number of home entries.
.1.3.6.1.4.1.2.6.2.13.5.1.4,IBM-6611-APPN-MIB::ibmappnDirRegEntries,Gauge32,read-only,,mandatory,,Current number of registered entries.
.1.3.6.1.4.1.2.6.2.13.5.1.5,IBM-6611-APPN-MIB::ibmappnDirInLocates,Counter32,read-only,,mandatory,,Number of directed locates received.
.1.3.6.1.4.1.2.6.2.13.5.1.6,IBM-6611-APPN-MIB::ibmappnDirInBcastLocates,Counter32,read-only,,mandatory,,Number of broadcast locates received.
.1.3.6.1.4.1.2.6.2.13.5.1.7,IBM-6611-APPN-MIB::ibmappnDirOutLocates,Counter32,read-only,,mandatory,,Number of directed locates sent.
.1.3.6.1.4.1.2.6.2.13.5.1.8,IBM-6611-APPN-MIB::ibmappnDirOutBcastLocates,Counter32,read-only,,mandatory,,Number of broadcast locates sent.
.1.3.6.1.4.1.2.6.2.13.5.1.9,IBM-6611-APPN-MIB::ibmappnDirNotFoundLocates,Counter32,read-only,,mandatory,,Number of directed locates returned with a 'not found'.
.1.3.6.1.4.1.2.6.2.13.5.1.10,IBM-6611-APPN-MIB::ibmappnDirNotFoundBcastLocates,Counter32,read-only,,mandatory,,Number of broadcast locates returned with a not found.
.1.3.6.1.4.1.2.6.2.13.5.1.11,IBM-6611-APPN-MIB::ibmappnDirLocateOutstands,Gauge32,read-only,,mandatory,,Current number of outstanding locates, both directed and broadcast. This value varies. A value of zero indicates that no locates are unanswered.
.1.3.6.1.4.1.2.6.2.13.5.2,IBM-6611-APPN-MIB::ibmappnDirTable,,not-accessible,,mandatory,,Table containing information about all known LUs and TPs.
.1.3.6.1.4.1.2.6.2.13.5.2.1,IBM-6611-APPN-MIB::ibmappnDirEntry,,not-accessible,ibmappnDirLuName,mandatory,,This table is indexed by the LU name.
.1.3.6.1.4.1.2.6.2.13.5.2.1.1,IBM-6611-APPN-MIB::ibmappnDirLuName,OCTET,read-only,,mandatory,,Fully-qualified network LU name in the domain of the serving network node.
.1.3.6.1.4.1.2.6.2.13.5.2.1.2,IBM-6611-APPN-MIB::ibmappnDirServerName,OCTET,read-only,,mandatory,,Fully-qualified control point (CP) name of the network node server. For unassociated end node entries, the end node fully-qualified name is returned.
.1.3.6.1.4.1.2.6.2.13.5.2.1.3,IBM-6611-APPN-MIB::ibmappnDirLuOwnerName,OCTET,read-only,,mandatory,,Fully-qualified CP name of the node at which the LU is located. This name is the same as the serving NN name when the LU is located at a network node or an unassociated end node. It is also the same as the fully-qualified LU name when this is the control point LU for this node.
.1.3.6.1.4.1.2.6.2.13.5.2.1.4,IBM-6611-APPN-MIB::ibmappnDirLuLocation,INTEGER,read-only,,mandatory,local(1):domain(2):xdomain(3),Specifies the location of the LU.
.1.3.6.1.4.1.2.6.2.13.5.2.1.5,IBM-6611-APPN-MIB::ibmappnDirType,INTEGER,read-only,,mandatory,home(1):cache(2):registered(3),Directory types are: 1 - Home The LU is in the domain of the local network node and the LU information has been configured at the local node. 2 - Cache The LU has previously been located by a broadcast search and the location information has been saved. 3 - Register The LU is at an end node that is in the domain of the local network node. Registered entries are registered by the served end node.
.1.3.6.1.4.1.2.6.2.13.5.2.1.6,IBM-6611-APPN-MIB::ibmappnDirWildCard,INTEGER,read-only,,mandatory,other(1):explicit-entry(2):partial-wildcard(3):full-wildcard(4),1 - Other means unknown type of LU entry. 2 - Expliced-entry means the full LUNAME will be used for locating this LU. 3 - Partial-wildcard means only the non-blank portions of the LUNAME will be used for locating this LU. 4 - Full-wildcard means all LUNAMES will be directed to this LU.
.1.3.6.1.4.1.2.6.2.13.6,IBM-6611-APPN-MIB::ibmappnCos,,,,,,
.1.3.6.1.4.1.2.6.2.13.6.1,IBM-6611-APPN-MIB::ibmappnCosModeTable,,not-accessible,,mandatory,,Table representing all of the defined mode names for this node. The table contains the matching COS name.
.1.3.6.1.4.1.2.6.2.13.6.1.1,IBM-6611-APPN-MIB::ibmappnCosModeEntry,,not-accessible,ibmappnCosModeName,mandatory,,This table is indexed by the Mode Name.
.1.3.6.1.4.1.2.6.2.13.6.1.1.1,IBM-6611-APPN-MIB::ibmappnCosModeName,OCTET,read-only,,mandatory,,Administratively-assigned name for this mode entry.
.1.3.6.1.4.1.2.6.2.13.6.1.1.2,IBM-6611-APPN-MIB::ibmappnCosModeCosName,OCTET,read-only,,mandatory,,An administratively assigned name for this Class of Service.
.1.3.6.1.4.1.2.6.2.13.6.2,IBM-6611-APPN-MIB::ibmappnCosNameTable,,not-accessible,,mandatory,,Table representing all of the defined class-of-service names for this node. The COS node and TG tables are accessed using the same index, which is the COS name.
.1.3.6.1.4.1.2.6.2.13.6.2.1,IBM-6611-APPN-MIB::ibmappnCosNameEntry,,not-accessible,ibmappnCosName,mandatory,,The COS name is the index to this table.
.1.3.6.1.4.1.2.6.2.13.6.2.1.1,IBM-6611-APPN-MIB::ibmappnCosName,OCTET,read-only,,mandatory,,Administratively-assigned name for this class of service.
.1.3.6.1.4.1.2.6.2.13.6.2.1.2,IBM-6611-APPN-MIB::ibmappnCosTransPriority,INTEGER,read-only,,mandatory,low(1):medium(2):high(3):network(4),Transmission priority for this class of service. Values are: Low Medium High Network 
.1.3.6.1.4.1.2.6.2.13.6.3,IBM-6611-APPN-MIB::ibmappnCosNodeRowTable,,not-accessible,,mandatory,,This table contains all node-row information for all class of service in this node.
.1.3.6.1.4.1.2.6.2.13.6.3.1,IBM-6611-APPN-MIB::ibmappnCosNodeRowEntry,,not-accessible,ibmappnCosNodeRowName:ibmappnCosNodeRowIndex,mandatory,,The COS name is the first index and a integer is the second index to insure a unique index.
.1.3.6.1.4.1.2.6.2.13.6.3.1.1,IBM-6611-APPN-MIB::ibmappnCosNodeRowName,OCTET,read-only,,mandatory,,Administratively-assigned name for this class of service.
.1.3.6.1.4.1.2.6.2.13.6.3.1.2,IBM-6611-APPN-MIB::ibmappnCosNodeRowIndex,INTEGER,read-only,,mandatory,,Index of COS name. This same value is used to access the node and TG COS tables. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.6.3.1.3,IBM-6611-APPN-MIB::ibmappnCosNodeRowWgt,OCTET,read-only,,mandatory,,Weight to be associated with the nodes that fit the criteria specified by this node row.
.1.3.6.1.4.1.2.6.2.13.6.3.1.4,IBM-6611-APPN-MIB::ibmappnCosNodeRowResistMin,INTEGER,read-only,,mandatory,,Minimum route addition resistance value for this node. Range of values is 0-255. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.4.1.2.6.2.13.6.3.1.5,IBM-6611-APPN-MIB::ibmappnCosNodeRowResistMax,INTEGER,read-only,,mandatory,,Maximum route addition resistance value for this node. Range of values is 0-255. The lower the value, the more desirable the node is for intermediate routing.
.1.3.6.1.4.1.2.6.2.13.6.3.1.6,IBM-6611-APPN-MIB::ibmappnCosNodeRowMinCongestAllow,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether low congestion will be tolerated. The minimum and maximum parameters will allow specifying either low-congested, high-congested, or either to be used.
.1.3.6.1.4.1.2.6.2.13.6.3.1.7,IBM-6611-APPN-MIB::ibmappnCosNodeRowMaxCongestAllow,INTEGER,read-only,,mandatory,yes(1):no(2),Indicates whether high congestion will be tolerated. The minimum and maximum parameters will allow specifying either low-congested, high-congested, or either to be used.
.1.3.6.1.4.1.2.6.2.13.6.4,IBM-6611-APPN-MIB::ibmappnCosTgRowTable,,not-accessible,,mandatory,,Table containing all the Tg-row information for all class of service defined in this node.
.1.3.6.1.4.1.2.6.2.13.6.4.1,IBM-6611-APPN-MIB::ibmappnCosTgRowEntry,,not-accessible,ibmappnCosTgRowName:ibmappnCosTgRowIndex,mandatory,,The TgRowName and the TgRowIndex are the index for this table.
.1.3.6.1.4.1.2.6.2.13.6.4.1.1,IBM-6611-APPN-MIB::ibmappnCosTgRowName,OCTET,read-only,,mandatory,,Administratively-assigned name for this class of service.
.1.3.6.1.4.1.2.6.2.13.6.4.1.2,IBM-6611-APPN-MIB::ibmappnCosTgRowIndex,INTEGER,read-only,,mandatory,,Index of COS name. This same value is used to access the node and TG COS tables.
.1.3.6.1.4.1.2.6.2.13.6.4.1.3,IBM-6611-APPN-MIB::ibmappnCosTgRowWgt,OCTET,read-only,,mandatory,,Weight to be associated with the nodes that fit the criteria specified by this tg-row.
.1.3.6.1.4.1.2.6.2.13.6.4.1.4,IBM-6611-APPN-MIB::ibmappnCosTgRowEffCapMin,INTEGER,read-only,,mandatory,,Minimum acceptable speed for this Class of Service. The effective capacity is an integer value that indicates the actual kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776.
.1.3.6.1.4.1.2.6.2.13.6.4.1.5,IBM-6611-APPN-MIB::ibmappnCosTgRowEffCapMax,INTEGER,read-only,,mandatory,,Maximum acceptable speed for this Class of Service. The effective capacity is an integer value that indicates the actual kilo bits per second. It is derived from the link bandwidth and maximum load factor with the range of 0 thru 603,979,776.
.1.3.6.1.4.1.2.6.2.13.6.4.1.6,IBM-6611-APPN-MIB::ibmappnCosTgRowConnCostMin,INTEGER,read-only,,mandatory,,Minimum acceptable cost per connect time for this Class of Service. Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.4.1.2.6.2.13.6.4.1.7,IBM-6611-APPN-MIB::ibmappnCosTgRowConnCostMax,INTEGER,read-only,,mandatory,,Maximum acceptable cost per connect time for this Class of Service. Cost per connect time: a value representing the relative cost per unit of time to use the TG. Range is from 0, which means no cost, to 255.
.1.3.6.1.4.1.2.6.2.13.6.4.1.8,IBM-6611-APPN-MIB::ibmappnCosTgRowByteCostMin,INTEGER,read-only,,mandatory,,Minimum acceptable cost per byte for this Class of Service.
.1.3.6.1.4.1.2.6.2.13.6.4.1.9,IBM-6611-APPN-MIB::ibmappnCosTgRowByteCostMax,INTEGER,read-only,,mandatory,,Maximum acceptable cost per byte for this Class of Service.
.1.3.6.1.4.1.2.6.2.13.6.4.1.10,IBM-6611-APPN-MIB::ibmappnCosTgRowSecurityMin,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Minimum acceptable security for this Class of Service.
.1.3.6.1.4.1.2.6.2.13.6.4.1.11,IBM-6611-APPN-MIB::ibmappnCosTgRowSecurityMax,INTEGER,read-only,,mandatory,nonsecure(1):publicSwitchedNetwork(32):undergroundCable(64):secureConduit(96):guardedConduit(128):encrypted(160):guardedRadiation(192),Maximum acceptable security for this Class of Service.
.1.3.6.1.4.1.2.6.2.13.6.4.1.12,IBM-6611-APPN-MIB::ibmappnCosTgRowDelayMin,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Minimum acceptable propagation delay for this class of service. Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with the more values enumerated.
.1.3.6.1.4.1.2.6.2.13.6.4.1.13,IBM-6611-APPN-MIB::ibmappnCosTgRowDelayMax,INTEGER,read-only,,mandatory,minimum(0):negligible(384):terrestrial(9216):packet(147456):long(294912):maximum(2013265920),Maximum acceptable propagation delay for this class of service. Relative amount of time that it takes for a signal to travel the length of the logical link. This time is represented in micro seconds, with the more values enumerated.
.1.3.6.1.4.1.2.6.2.13.6.4.1.14,IBM-6611-APPN-MIB::ibmappnCosTgRowUsr1Min,INTEGER,read-only,,mandatory,,Minimum acceptable value for this user defined characteristic. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.6.4.1.15,IBM-6611-APPN-MIB::ibmappnCosTgRowUsr1Max,INTEGER,read-only,,mandatory,,Maximum acceptable value for this user defined characteristic. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.6.4.1.16,IBM-6611-APPN-MIB::ibmappnCosTgRowUsr2Min,INTEGER,read-only,,mandatory,,Minimum acceptable value for this user defined characteristic. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.6.4.1.17,IBM-6611-APPN-MIB::ibmappnCosTgRowUsr2Max,INTEGER,read-only,,mandatory,,A Maximum acceptable value for this user defined characteristic.
.1.3.6.1.4.1.2.6.2.13.6.4.1.18,IBM-6611-APPN-MIB::ibmappnCosTgRowUsr3Min,INTEGER,read-only,,mandatory,,Minimum acceptable value for this user defined characteristic. Range of values is 0-255.
.1.3.6.1.4.1.2.6.2.13.6.4.1.19,IBM-6611-APPN-MIB::ibmappnCosTgRowUsr3Max,INTEGER,read-only,,mandatory,,Maximum acceptable value for this user defined characteristic. Range of values is 0-255.
.1.3.6.1.4.1.4,SMUX-MIB::unix,,,,,,
.1.3.6.1.4.1.4.4,SMUX-MIB::smux,,,,,,
.1.3.6.1.4.1.4.4.1,SMUX-MIB::smuxPeerTable,,not-accessible,,mandatory,,The SMUX peer table.
.1.3.6.1.4.1.4.4.1.1,SMUX-MIB::smuxPeerEntry,,not-accessible,smuxPindex,mandatory,,An entry in the SMUX peer table.
.1.3.6.1.4.1.4.4.1.1.1,SMUX-MIB::smuxPindex,INTEGER,read-only,,mandatory,,An index which uniquely identifies a SMUX peer.
.1.3.6.1.4.1.4.4.1.1.2,SMUX-MIB::smuxPidentity,OBJECT,read-only,,mandatory,,The authoritative designation for a SMUX peer.
.1.3.6.1.4.1.4.4.1.1.3,SMUX-MIB::smuxPdescription,OCTET,read-only,,mandatory,,A human-readable description of a SMUX peer.
.1.3.6.1.4.1.4.4.1.1.4,SMUX-MIB::smuxPstatus,INTEGER,read-write,,mandatory,valid(1):invalid(2):connecting(3),The type of SMUX peer. Setting this object to the value invalid(2) has the effect of invaliding the corresponding entry in the smuxPeerTable. It is an implementation- specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that correspond to entries not currently in use. Proper interpretation of such entries requires examination of the relative smuxPstatus object.
.1.3.6.1.4.1.4.4.2,SMUX-MIB::smuxTreeTable,,not-accessible,,mandatory,,The SMUX tree table.
.1.3.6.1.4.1.4.4.2.1,SMUX-MIB::smuxTreeEntry,,not-accessible,smuxTsubtree:smuxTpriority,mandatory,,An entry in the SMUX tree table.
.1.3.6.1.4.1.4.4.2.1.1,SMUX-MIB::smuxTsubtree,OBJECT,read-only,,mandatory,,The MIB subtree being exported by a SMUX peer.
.1.3.6.1.4.1.4.4.2.1.2,SMUX-MIB::smuxTpriority,INTEGER,read-only,,mandatory,,The SMUX peer's priority when exporting the MIB subtree.
.1.3.6.1.4.1.4.4.2.1.3,SMUX-MIB::smuxTindex,INTEGER,read-only,,mandatory,,The SMUX peer's identity.
.1.3.6.1.4.1.4.4.2.1.4,SMUX-MIB::smuxTstatus,INTEGER,read-write,,mandatory,valid(1):invalid(2),The type of SMUX tree. Setting this object to the value invalid(2) has the effect of invaliding the corresponding entry in the smuxTreeTable. It is an implementation- specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that correspond to entries not currently in use. Proper interpretation of such entries requires examination of the relative smuxTstatus object.
.1.3.6.1.4.1.23,IPX::novell,,,,,,
.1.3.6.1.4.1.23.2,IPX::mibDoc,,,,,,
.1.3.6.1.4.1.23.2.5,IPX::ipx,,,,,,
.1.3.6.1.4.1.23.2.5.1,IPX::ipxSystem,,,,,,
.1.3.6.1.4.1.23.2.5.1.1,IPX::ipxBasicSysTable,,not-accessible,,mandatory,,The IPX System table - basic information.
.1.3.6.1.4.1.23.2.5.1.1.1,IPX::ipxBasicSysEntry,,not-accessible,ipxBasicSysInstance,mandatory,,Each entry corresponds to one instance of IPX running on the system.
.1.3.6.1.4.1.23.2.5.1.1.1.1,IPX::ipxBasicSysInstance,INTEGER,read-write,,mandatory,,The unique identifier of the instance of IPX to which this row corresponds. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.1.1.1.2,IPX::ipxBasicSysExistState,INTEGER,read-write,,mandatory,off(1):on(2),The validity of this entry in the IPX system table. Setting this field to off indicates that this entry may be deleted from the system table at the IPX implementation's discretion.
.1.3.6.1.4.1.23.2.5.1.1.1.3,IPX::ipxBasicSysNetNumber,OCTET,read-write,,mandatory,,The network number portion of the IPX address of this system.
.1.3.6.1.4.1.23.2.5.1.1.1.4,IPX::ipxBasicSysNode,OCTET,read-write,,mandatory,,The node number portion of the IPX address of this system.
.1.3.6.1.4.1.23.2.5.1.1.1.5,IPX::ipxBasicSysName,OCTET,read-write,,mandatory,,The readable name for this system.
.1.3.6.1.4.1.23.2.5.1.1.1.6,IPX::ipxBasicSysInReceives,Counter32,read-only,,mandatory,,The total number of IPX packets received, including those received in error.
.1.3.6.1.4.1.23.2.5.1.1.1.7,IPX::ipxBasicSysInHdrErrors,Counter32,read-only,,mandatory,,The number of IPX packets discarded due to errors in their headers, including any IPX packet with a size less than the minimum of 30 bytes.
.1.3.6.1.4.1.23.2.5.1.1.1.8,IPX::ipxBasicSysInUnknownSockets,Counter32,read-only,,mandatory,,The number of IPX packets discarded because the destination socket was not open.
.1.3.6.1.4.1.23.2.5.1.1.1.9,IPX::ipxBasicSysInDiscards,Counter32,read-only,,mandatory,,The number of IPX packets received but discarded due to reasons other than those accounted for by ipxBasicSysInHdrErrors, ipxBasicSysInUnknownSockets, ipxAdvSysInDiscards, and ipxAdvSysInCompressDiscards.
.1.3.6.1.4.1.23.2.5.1.1.1.10,IPX::ipxBasicSysInBadChecksums,Counter32,read-only,,mandatory,,The number of IPX packets received with incorrect checksums.
.1.3.6.1.4.1.23.2.5.1.1.1.11,IPX::ipxBasicSysInDelivers,Counter32,read-only,,mandatory,,The total number of IPX packets delivered locally, including packets from local applications.
.1.3.6.1.4.1.23.2.5.1.1.1.12,IPX::ipxBasicSysNoRoutes,Counter32,read-only,,mandatory,,The number of times no route to a destination was found.
.1.3.6.1.4.1.23.2.5.1.1.1.13,IPX::ipxBasicSysOutRequests,Counter32,read-only,,mandatory,,The number of IPX packets supplied locally for transmission, not including any packets counted in ipxAdvForwPackets.
.1.3.6.1.4.1.23.2.5.1.1.1.14,IPX::ipxBasicSysOutMalformedRequests,Counter32,read-only,,mandatory,,The number of IPX packets supplied locally that contained errors in their structure.
.1.3.6.1.4.1.23.2.5.1.1.1.15,IPX::ipxBasicSysOutDiscards,Counter32,read-only,,mandatory,,The number of outgoing IPX packets discarded due to reasons other than those accounted for in ipxBasicSysOutMalformedRequests, ipxAdvSysOutFiltered, and ipxAdvSysOutCompressDiscards.
.1.3.6.1.4.1.23.2.5.1.1.1.16,IPX::ipxBasicSysOutPackets,Counter32,read-only,,mandatory,,The total number of IPX packets transmitted.
.1.3.6.1.4.1.23.2.5.1.1.1.17,IPX::ipxBasicSysConfigSockets,INTEGER,read-only,,mandatory,,The configured maximum number of IPX sockets that may be open at one time.
.1.3.6.1.4.1.23.2.5.1.1.1.18,IPX::ipxBasicSysOpenSocketFails,Counter32,read-only,,mandatory,,The number of IPX socket open calls which failed.
.1.3.6.1.4.1.23.2.5.1.2,IPX::ipxAdvSysTable,,not-accessible,,mandatory,,The IPX System table - advanced information.
.1.3.6.1.4.1.23.2.5.1.2.1,IPX::ipxAdvSysEntry,,not-accessible,ipxAdvSysInstance,mandatory,,Each entry corresponds to one instance of IPX running on the system.
.1.3.6.1.4.1.23.2.5.1.2.1.1,IPX::ipxAdvSysInstance,INTEGER,read-write,,mandatory,,The unique identifier of the instance of IPX to which this row corresponds. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.1.2.1.2,IPX::ipxAdvSysMaxPathSplits,INTEGER,read-write,,mandatory,,The maximum number of paths with equal routing metric value which this instance of the IPX may split between when forwarding packets.
.1.3.6.1.4.1.23.2.5.1.2.1.3,IPX::ipxAdvSysMaxHops,INTEGER,read-write,,mandatory,,The maximum number of hops a packet may take.
.1.3.6.1.4.1.23.2.5.1.2.1.4,IPX::ipxAdvSysInTooManyHops,Counter32,read-only,,mandatory,,The number of IPX packets discarded due to exceeding the maximum hop count.
.1.3.6.1.4.1.23.2.5.1.2.1.5,IPX::ipxAdvSysInFiltered,Counter32,read-only,,mandatory,,The number of incoming IPX packets discarded due to filtering.
.1.3.6.1.4.1.23.2.5.1.2.1.6,IPX::ipxAdvSysInCompressDiscards,Counter32,read-only,,mandatory,,The number of incoming IPX packets discarded due to decompression errors.
.1.3.6.1.4.1.23.2.5.1.2.1.7,IPX::ipxAdvSysNETBIOSPackets,Counter32,read-only,,mandatory,,The number of NETBIOS packets received.
.1.3.6.1.4.1.23.2.5.1.2.1.8,IPX::ipxAdvSysForwPackets,Counter32,read-only,,mandatory,,The number of IPX packets forwarded.
.1.3.6.1.4.1.23.2.5.1.2.1.9,IPX::ipxAdvSysOutFiltered,Counter32,read-only,,mandatory,,The number of outgoing IPX packets discarded due to filtering.
.1.3.6.1.4.1.23.2.5.1.2.1.10,IPX::ipxAdvSysOutCompressDiscards,Counter32,read-only,,mandatory,,The number of outgoing IPX packets discarded due to compression errors.
.1.3.6.1.4.1.23.2.5.1.2.1.11,IPX::ipxAdvSysCircCount,INTEGER,read-only,,mandatory,,The number of circuits known to this instance of IPX.
.1.3.6.1.4.1.23.2.5.1.2.1.12,IPX::ipxAdvSysDestCount,INTEGER,read-only,,mandatory,,The number of currently reachable destinations known to this instance of IPX.
.1.3.6.1.4.1.23.2.5.1.2.1.13,IPX::ipxAdvSysServCount,INTEGER,read-only,,mandatory,,The number of services known to this instance of IPX.
.1.3.6.1.4.1.23.2.5.2,IPX::ipxCircuit,,,,,,
.1.3.6.1.4.1.23.2.5.2.1,IPX::ipxCircTable,,not-accessible,,mandatory,,The Circuit table.
.1.3.6.1.4.1.23.2.5.2.1.1,IPX::ipxCircEntry,,not-accessible,ipxCircSysInstance:ipxCircIndex,mandatory,,Each entry corresponds to one circuit known to the system.
.1.3.6.1.4.1.23.2.5.2.1.1.1,IPX::ipxCircSysInstance,INTEGER,read-write,,mandatory,,The unique identifier of the instance of IPX to which this entry corresponds. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.2,IPX::ipxCircIndex,INTEGER,read-write,,mandatory,,The identifier of this circuit, unique within the instance of IPX. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.3,IPX::ipxCircExistState,INTEGER,read-write,,mandatory,off(1):on(2),The validity of this circuit entry. A circuit with this value set to off may be deleted from the table at the IPX implementation's discretion.
.1.3.6.1.4.1.23.2.5.2.1.1.4,IPX::ipxCircOperState,INTEGER,read-write,,mandatory,down(1):up(2):sleeping(3):suspended(4),The operational state of the circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.5,IPX::ipxCircIfIndex,INTEGER,read-write,,mandatory,,The value of ifIndex for the interface used by this circuit. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.6,IPX::ipxCircName,OCTET,read-write,,mandatory,,The readable name for the circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.7,IPX::ipxCircType,INTEGER,read-write,,mandatory,other(1):broadcast(2):ptToPt(3):wanRIP(4):unnumberedRIP(5):dynamic(6):wanWS(7),The type of the circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.8,IPX::ipxCircDialName,OCTET,read-write,,mandatory,,The symbolic name used to refernce the dialing information used to create this circuit. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.9,IPX::ipxCircLocalMaxPacketSize,INTEGER,read-write,,mandatory,,The maximum size (including header), in bytes, that the system supports locally on this circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.10,IPX::ipxCircCompressState,INTEGER,read-write,,mandatory,off(1):on(2),The compression state on this circuit. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.11,IPX::ipxCircCompressSlots,INTEGER,read-write,,mandatory,,The number of compression slots available on this circuit. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.12,IPX::ipxCircStaticStatus,INTEGER,read-write,,mandatory,unknown(1):changed(3):read(4):reading(5):write(6):writing(7),Indicates whether the information about static routes and services reached via this circuit matches that saved in permanent storage (current). Setting the value to write when it had the value changed will write the currently in use information to permanent storage, if supported. Setting the value to read when it had the value changed will replace any routes and services currently defined for the circuit with those read from permanent storage, if supported.
.1.3.6.1.4.1.23.2.5.2.1.1.13,IPX::ipxCircCompressedSent,Counter32,read-only,,mandatory,,The number of compressed packets sent.
.1.3.6.1.4.1.23.2.5.2.1.1.14,IPX::ipxCircCompressedInitSent,Counter32,read-only,,mandatory,,The number of compression initialization packets sent.
.1.3.6.1.4.1.23.2.5.2.1.1.15,IPX::ipxCircCompressedRejectsSent,Counter32,read-only,,mandatory,,The number of compressed packet rejected packets sent.
.1.3.6.1.4.1.23.2.5.2.1.1.16,IPX::ipxCircUncompressedSent,Counter32,read-only,,mandatory,,The number of packets sent without being compressed even though compression was turned on for this circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.17,IPX::ipxCircCompressedReceived,Counter32,read-only,,mandatory,,The number of compressed packets received.
.1.3.6.1.4.1.23.2.5.2.1.1.18,IPX::ipxCircCompressedInitReceived,Counter32,read-only,,mandatory,,The number of compression initialization packets received.
.1.3.6.1.4.1.23.2.5.2.1.1.19,IPX::ipxCircCompressedRejectsReceived,Counter32,read-only,,mandatory,,The number of compressed packet rejected packets received.
.1.3.6.1.4.1.23.2.5.2.1.1.20,IPX::ipxCircUncompressedReceived,Counter32,read-only,,mandatory,,The number of packets received without having been compressed even though compression was turned on for this circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.21,IPX::ipxCircMediaType,OCTET,read-only,,mandatory,,The media type used on this circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.22,IPX::ipxCircNetNumber,OCTET,read-write,,mandatory,,The IPX network number of this circuit. This value may be written only when creating a new entry in the table.
.1.3.6.1.4.1.23.2.5.2.1.1.23,IPX::ipxCircStateChanges,Counter32,read-only,,mandatory,,The number of times the circuit has changed state.
.1.3.6.1.4.1.23.2.5.2.1.1.24,IPX::ipxCircInitFails,Counter32,read-only,,mandatory,,The number of times that initialization of this circuit has failed.
.1.3.6.1.4.1.23.2.5.2.1.1.25,IPX::ipxCircDelay,INTEGER,read-only,,mandatory,,The period of time, in milliseconds, that it takes to transmit one byte of data, excluding protocol headers, to a destination on the other end of the circuit, if the circuit is free of other traffic.
.1.3.6.1.4.1.23.2.5.2.1.1.26,IPX::ipxCircThroughput,INTEGER,read-only,,mandatory,,The amount of data, in bits per second, that may flow through the circuit if there is no other traffic.
.1.3.6.1.4.1.23.2.5.2.1.1.27,IPX::ipxCircNeighRouterName,OCTET,read-only,,mandatory,,The name of the neighboring router on a WAN circuit.
.1.3.6.1.4.1.23.2.5.2.1.1.28,IPX::ipxCircNeighInternalNetNum,OCTET,read-only,,mandatory,,The internal network number of the neighboring router on a WAN circuit.
.1.3.6.1.4.1.23.2.5.3,IPX::ipxForwarding,,,,,,
.1.3.6.1.4.1.23.2.5.3.1,IPX::ipxDestTable,,not-accessible,,mandatory,,The Destination table contains information about all known destinations.
.1.3.6.1.4.1.23.2.5.3.1.1,IPX::ipxDestEntry,,not-accessible,ipxDestSysInstance:ipxDestNetNum,mandatory,,Each entry corresponds to one destination.
.1.3.6.1.4.1.23.2.5.3.1.1.1,IPX::ipxDestSysInstance,INTEGER,read-only,,mandatory,,The unique identifier of the instance of IPX to which this row corresponds.
.1.3.6.1.4.1.23.2.5.3.1.1.2,IPX::ipxDestNetNum,OCTET,read-only,,mandatory,,The IPX network number of the destination.
.1.3.6.1.4.1.23.2.5.3.1.1.3,IPX::ipxDestProtocol,INTEGER,read-only,,mandatory,other(1):local(2):rip(3):nlsp(4):static(5),The routing protocol from which knowledge of this destination was obtained.
.1.3.6.1.4.1.23.2.5.3.1.1.4,IPX::ipxDestTicks,INTEGER,read-only,,mandatory,,The delay in ticks to reach this destination.
.1.3.6.1.4.1.23.2.5.3.1.1.5,IPX::ipxDestHopCount,INTEGER,read-only,,mandatory,,The number of hops necessary to reach the destination.
.1.3.6.1.4.1.23.2.5.3.1.1.6,IPX::ipxDestNextHopCircIndex,INTEGER,read-only,,mandatory,,The unique identifier of the circuit used to reach the next hop.
.1.3.6.1.4.1.23.2.5.3.1.1.7,IPX::ipxDestNextHopNICAddress,OCTET,read-only,,mandatory,,The NIC address of the next hop.
.1.3.6.1.4.1.23.2.5.3.1.1.8,IPX::ipxDestNextHopNetNum,OCTET,read-only,,mandatory,,The IPX network number of the next hop.
.1.3.6.1.4.1.23.2.5.3.2,IPX::ipxStaticRouteTable,,not-accessible,,mandatory,,The Static Routes table contains information about all destinations reached via statically configured routes.
.1.3.6.1.4.1.23.2.5.3.2.1,IPX::ipxStaticRouteEntry,,not-accessible,ipxStaticRouteSysInstance:ipxStaticRouteCircIndex:ipxStaticRouteNetNum,mandatory,,Each entry corresponds to one static route.
.1.3.6.1.4.1.23.2.5.3.2.1.1,IPX::ipxStaticRouteSysInstance,INTEGER,read-write,,mandatory,,The unique identifier of the instance of IPX to which this row corresponds.
.1.3.6.1.4.1.23.2.5.3.2.1.2,IPX::ipxStaticRouteCircIndex,INTEGER,read-write,,mandatory,,The unique identifier of the circuit used to reach the first hop in the static route.
.1.3.6.1.4.1.23.2.5.3.2.1.3,IPX::ipxStaticRouteNetNum,OCTET,read-write,,mandatory,,The IPX network number of the route's destination.
.1.3.6.1.4.1.23.2.5.3.2.1.4,IPX::ipxStaticRouteExistState,INTEGER,read-write,,mandatory,off(1):on(2),The validity of this static route. Entries with the value set to off may be deleted from the table at the implementation's discretion.
.1.3.6.1.4.1.23.2.5.3.2.1.5,IPX::ipxStaticRouteTicks,INTEGER,read-write,,mandatory,,The delay, in ticks, to reach the route's destination.
.1.3.6.1.4.1.23.2.5.3.2.1.6,IPX::ipxStaticRouteHopCount,INTEGER,read-write,,mandatory,,The number of hops necessary to reach the destination.
.1.3.6.1.4.1.23.2.5.4,IPX::ipxServices,,,,,,
.1.3.6.1.4.1.23.2.5.4.1,IPX::ipxServTable,,not-accessible,,mandatory,,The table of services, indexed by name and type.
.1.3.6.1.4.1.23.2.5.4.1.1,IPX::ipxServEntry,,not-accessible,ipxServSysInstance:ipxServType:ipxServName,mandatory,,Each entry corresponds to one service.
.1.3.6.1.4.1.23.2.5.4.1.1.1,IPX::ipxServSysInstance,INTEGER,read-only,,mandatory,,The unique identifier of the instance of IPX to which this entry corresponds.
.1.3.6.1.4.1.23.2.5.4.1.1.2,IPX::ipxServType,OCTET,read-only,,mandatory,,The service type.
.1.3.6.1.4.1.23.2.5.4.1.1.3,IPX::ipxServName,OCTET,read-only,,mandatory,,The service name.
.1.3.6.1.4.1.23.2.5.4.1.1.4,IPX::ipxServProtocol,INTEGER,read-only,,mandatory,other(1):local(2):nlsp(4):static(5):sap(6),The protocol from which knowledge of this service was obtained.
.1.3.6.1.4.1.23.2.5.4.1.1.5,IPX::ipxServNetNum,OCTET,read-only,,mandatory,,The IPX network number portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.1.1.6,IPX::ipxServNode,OCTET,read-only,,mandatory,,The node portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.1.1.7,IPX::ipxServSocket,OCTET,read-only,,mandatory,,The socket portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.1.1.8,IPX::ipxServHopCount,INTEGER,read-only,,mandatory,,The number of hops to the service.
.1.3.6.1.4.1.23.2.5.4.2,IPX::ipxDestServTable,,not-accessible,,mandatory,,The table of services, indexed by address, name, and type.
.1.3.6.1.4.1.23.2.5.4.2.1,IPX::ipxDestServEntry,,not-accessible,ipxDestServSysInstance:ipxDestServNetNum:ipxDestServNode:ipxDestServSocket:ipxDestServName:ipxDestServType,mandatory,,Each entry corresponds to one service.
.1.3.6.1.4.1.23.2.5.4.2.1.1,IPX::ipxDestServSysInstance,INTEGER,read-only,,mandatory,,The unique identifier of the instance of IPX to which this entry corresponds.
.1.3.6.1.4.1.23.2.5.4.2.1.2,IPX::ipxDestServNetNum,OCTET,read-only,,mandatory,,The IPX network number portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.2.1.3,IPX::ipxDestServNode,OCTET,read-only,,mandatory,,The node portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.2.1.4,IPX::ipxDestServSocket,OCTET,read-only,,mandatory,,The socket portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.2.1.5,IPX::ipxDestServName,OCTET,read-only,,mandatory,,The service name.
.1.3.6.1.4.1.23.2.5.4.2.1.6,IPX::ipxDestServType,OCTET,read-only,,mandatory,,The service type.
.1.3.6.1.4.1.23.2.5.4.2.1.7,IPX::ipxDestServProtocol,INTEGER,read-only,,mandatory,other(1):local(2):nlsp(4):static(5):sap(6),The protocol from which knowledge of this service was obtained.
.1.3.6.1.4.1.23.2.5.4.2.1.8,IPX::ipxDestServHopCount,INTEGER,read-only,,mandatory,,The number of hops to the service.
.1.3.6.1.4.1.23.2.5.4.3,IPX::ipxStaticServTable,,not-accessible,,mandatory,,The Static Services table contains information about all services reached via statically configured routes.
.1.3.6.1.4.1.23.2.5.4.3.1,IPX::ipxStaticServEntry,,not-accessible,ipxStaticServSysInstance:ipxStaticServCircIndex:ipxStaticServName:ipxStaticServType,mandatory,,Each entry corresponds to one service.
.1.3.6.1.4.1.23.2.5.4.3.1.1,IPX::ipxStaticServSysInstance,INTEGER,read-write,,mandatory,,The unique identifier of the instance of IPX to which this entry corresponds.
.1.3.6.1.4.1.23.2.5.4.3.1.2,IPX::ipxStaticServCircIndex,INTEGER,read-write,,mandatory,,The circuit used to reach this service.
.1.3.6.1.4.1.23.2.5.4.3.1.3,IPX::ipxStaticServName,OCTET,read-write,,mandatory,,The service name.
.1.3.6.1.4.1.23.2.5.4.3.1.4,IPX::ipxStaticServType,OCTET,read-write,,mandatory,,The service type.
.1.3.6.1.4.1.23.2.5.4.3.1.5,IPX::ipxStaticServExistState,INTEGER,read-write,,mandatory,off(1):on(2),The validity of this static service. Entries with the value set to off may be deleted from the table at the implementation's discretion.
.1.3.6.1.4.1.23.2.5.4.3.1.6,IPX::ipxStaticServNetNum,OCTET,read-write,,mandatory,,The IPX network number portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.3.1.7,IPX::ipxStaticServNode,OCTET,read-write,,mandatory,,The node portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.3.1.8,IPX::ipxStaticServSocket,OCTET,read-write,,mandatory,,The socket portion of the IPX address of the service.
.1.3.6.1.4.1.23.2.5.4.3.1.9,IPX::ipxStaticServHopCount,INTEGER,read-write,,mandatory,,The number of hops to the service.
.1.3.6.1.4.1.23.2.5.5,IPX::ipxTraps,,,,,,
.1.3.6.1.4.1.23.2.5.5.0,IPX::ipxTraps#,,,,,,
.1.3.6.1.4.1.23.2.5.5.0.1,IPX::ipxTrapCircuitDown,,,,,,This trap signifies that the specified circuit has gone down.
.1.3.6.1.4.1.23.2.5.5.0.2,IPX::ipxTrapCircuitUp,,,,,,This trap signifies that the specified circuit has come up.
.1.3.6.1.4.1.23.2.29,TCPIPX-MIB::tcpx,,,,,,
.1.3.6.1.4.1.23.2.29.1,TCPIPX-MIB::tcpxTcp,,,,,,
.1.3.6.1.4.1.23.2.29.1.1,TCPIPX-MIB::tcpIpxConnTable,,not-accessible,,mandatory,,A table containing information specific on TCP connection over IPX network layer.
.1.3.6.1.4.1.23.2.29.1.1.1,TCPIPX-MIB::tcpIpxConnEntry,,not-accessible,tcpIpxConnLocalAddress:tcpIpxConnLocalPort:tcpIpxConnRemAddress:tcpIpxConnRemPort,mandatory,,Information about a particular current TCP connection over IPX An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
.1.3.6.1.4.1.23.2.29.1.1.1.1,TCPIPX-MIB::tcpIpxConnState,INTEGER,read-write,,mandatory,closed(1):listen(2):synSent(3):synReceived(4):established(5):finWait1(6):finWait2(7):closeWait(8):lastAck(9):closing(10):timeWait(11):deleteTCB(12),The state of this TCP connection. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
.1.3.6.1.4.1.23.2.29.1.1.1.2,TCPIPX-MIB::tcpIpxConnLocalAddress,OCTET,read-only,,mandatory,,The local IPX address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any interface, the value 00000000:000000000000 is used. See tcpUnspecConnTable for connections in the listen state which is willing to accept connects for any IP interface associated with the node.
.1.3.6.1.4.1.23.2.29.1.1.1.3,TCPIPX-MIB::tcpIpxConnLocalPort,INTEGER,read-only,,mandatory,,The local port number for this TCP connection.
.1.3.6.1.4.1.23.2.29.1.1.1.4,TCPIPX-MIB::tcpIpxConnRemAddress,OCTET,read-only,,mandatory,,The remote IPX address for this TCP connection.
.1.3.6.1.4.1.23.2.29.1.1.1.5,TCPIPX-MIB::tcpIpxConnRemPort,INTEGER,read-only,,mandatory,,The remote port number for this TCP connection.
.1.3.6.1.4.1.23.2.29.1.2,TCPIPX-MIB::tcpUnspecConnTable,,not-accessible,,mandatory,,A table containing information specific on TCP connection over unspecified network layer.
.1.3.6.1.4.1.23.2.29.1.2.1,TCPIPX-MIB::tcpUnspecConnEntry,,not-accessible,tcpUnspecConnLocalPort,mandatory,,Information about a particular current TCP connection over unspecified network layer. An object of this type is transient, in that it ceases to exist when the connection makes transition beyond LISTEN state, or when (or soon after) the connection makes transition to the CLOSED state,
.1.3.6.1.4.1.23.2.29.1.2.1.1,TCPIPX-MIB::tcpUnspecConnState,INTEGER,read-write,,mandatory,closed(1):listen(2):deleteTCB(12),The state of this TCP connection. Since the TCP connection can belong to this table only when its state is less than SYN_SENT, only closed and listen state apply. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
.1.3.6.1.4.1.23.2.29.1.2.1.2,TCPIPX-MIB::tcpUnspecConnLocalPort,INTEGER,read-only,,mandatory,,The local port number for this TCP connection.
.1.3.6.1.4.1.23.2.29.2,TCPIPX-MIB::tcpxUdp,,,,,,
.1.3.6.1.4.1.23.2.29.2.1,TCPIPX-MIB::udpIpxTable,,not-accessible,,mandatory,,A table containing UDP listener information.
.1.3.6.1.4.1.23.2.29.2.1.1,TCPIPX-MIB::udpIpxEntry,,not-accessible,udpIpxLocalAddress:udpIpxLocalPort,mandatory,,Information about a particular current UDP listener.
.1.3.6.1.4.1.23.2.29.2.1.1.1,TCPIPX-MIB::udpIpxLocalAddress,OCTET,read-only,,mandatory,,The local IPX address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any interface, the value 00000000:000000000000 is used. See udpUnspecTable for UDP listener which is willing to accept datagrams from any network layer.
.1.3.6.1.4.1.23.2.29.2.1.1.2,TCPIPX-MIB::udpIpxLocalPort,INTEGER,read-only,,mandatory,,The local port number for this UDP listener.
.1.3.6.1.4.1.23.2.29.2.2,TCPIPX-MIB::udpUnspecTable,,not-accessible,,mandatory,,A table containing UDP listener information.
.1.3.6.1.4.1.23.2.29.2.2.1,TCPIPX-MIB::udpUnspecEntry,,not-accessible,udpUnspecLocalPort,mandatory,,Information about a particular current UDP listener.
.1.3.6.1.4.1.23.2.29.2.2.1.1,TCPIPX-MIB::udpUnspecLocalPort,INTEGER,read-only,,mandatory,,The local port number for this UDP listener.
.1.3.6.1.4.1.2699,Job-Monitoring-MIB::pwg,,,,,,
.1.3.6.1.4.1.2699.1,Job-Monitoring-MIB::mibs,,,,,,
.1.3.6.1.4.1.2699.1.1,Job-Monitoring-MIB::jobmonMIB,,,,,,The MIB module for monitoring job in servers, printers, and other devices. Version: 1.0
.1.3.6.1.4.1.2699.1.1.1,Job-Monitoring-MIB::jobmonMIBObjects,,,,,,
.1.3.6.1.4.1.2699.1.1.1.1,Job-Monitoring-MIB::jmGeneral,,,,,,
.1.3.6.1.4.1.2699.1.1.1.1.1,Job-Monitoring-MIB::jmGeneralTable,,not-accessible,,current,,The jmGeneralTable consists of information of a general nature that are per-job-set, but are not per-job. See Section 2 entitled 'Terminology and Job Model' for the definition of a job set. The MANDATORY-GROUP macro specifies that this group is MANDATORY.
.1.3.6.1.4.1.2699.1.1.1.1.1.1,Job-Monitoring-MIB::jmGeneralEntry,,not-accessible,jmGeneralJobSetIndex,current,,Information about a job set (queue). An entry SHALL exist in this table for each job set.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.1,Job-Monitoring-MIB::jmGeneralJobSetIndex,Integer32,not-accessible,,current,,A unique value for each job set in this MIB. The jmJobTable and jmAttributeTable tables have this same index as their primary index. The value(s) of the jmGeneralJobSetIndex SHALL be persistent across power cycles, so that clients that have retained jmGeneralJobSetIndex values will access the same job sets upon subsequent power-up. An implementation that has only one job set, such as a printer with a single queue, SHALL hard code this object with the value 1. See Section 2 entitled 'Terminology and Job Model' for the definition of a job set. Corresponds to the first index in jmJobTable and jmAttributeTable.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.2,Job-Monitoring-MIB::jmGeneralNumberOfActiveJobs,Integer32,read-only,,current,,The current number of 'active' jobs in the jmJobIDTable, jmJobTable, and jmAttributeTable, i.e., the total number of jobs that are in the pending, processing, or processingStopped states. See the JmJobStateTC textual-convention for the exact specification of the semantics of the job states.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.3,Job-Monitoring-MIB::jmGeneralOldestActiveJobIndex,Integer32,read-only,,current,,The jmJobIndex of the oldest job that is still in one of the 'active' states (pending, processing, or processingStopped). In other words, the index of the 'active' job that has been in the job tables the longest. If there are no active jobs, the agent SHALL set the value of this object to 0. See Section 3.2 entitled 'The Job Tables and the Oldest Active and Newest Active Indexes' for a description of the usage of this object.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.4,Job-Monitoring-MIB::jmGeneralNewestActiveJobIndex,Integer32,read-only,,current,,The jmJobIndex of the newest job that is in one of the 'active' states (pending, processing, or processingStopped). In other words, the index of the 'active' job that has been most recently added to the job tables. When all jobs become 'inactive', i.e., enter the pendingHeld, completed, canceled, or aborted states, the agent SHALL set the value of this object to 0. See Section 3.2 entitled 'The Job Tables and the Oldest Active and Newest Active Indexes' for a description of the usage of this object.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.5,Job-Monitoring-MIB::jmGeneralJobPersistence,Integer32,read-only,,current,,The minimum time in seconds for this instance of the Job Set that an entry SHALL remain in the jmJobIDTable and jmJobTable after processing has completed, i.e., the minimum time in seconds starting when the job enters the completed, canceled, or aborted state. Configuring this object is implementation-dependent. This value SHALL be equal to or greater than the value of jmGeneralAttributePersistence. This value SHOULD be at least 60 which gives a monitoring or accounting application one minute in which to poll for job data.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.6,Job-Monitoring-MIB::jmGeneralAttributePersistence,Integer32,read-only,,current,,The minimum time in seconds for this instance of the Job Set that an entry SHALL remain in the jmAttributeTable after processing has completed , i.e., the time in seconds starting when the job enters the completed, canceled, or aborted state. Configuring this object is implementation-dependent. This value SHOULD be at least 60 which gives a monitoring or accounting application one minute in which to poll for job data.
.1.3.6.1.4.1.2699.1.1.1.1.1.1.7,Job-Monitoring-MIB::jmGeneralJobSetName,OCTET,read-only,,current,,The human readable name of this job set assigned by the system administrator (by means outside of this MIB). Typically, this name SHOULD be the name of the job queue. If a server or device has only a single job set, this object can be the administratively assigned name of the server or device itself. This name does not need to be unique, though each job set in a single Job Monitoring MIB SHOULD have distinct names. NOTE - If the job set corresponds to a single printer and the Printer MIB is implemented, this value SHOULD be the same as the prtGeneralPrinterName object in the draft Printer MIB [print-mib-draft]. If the job set corresponds to an IPP Printer, this value SHOULD be the same as the IPP 'printer- name' Printer attribute. NOTE - The purpose of this object is to help the user of the job monitoring application distinguish between several job sets in implementations that support more than one job set. See the OBJECT compliance macro for the minimum maximum length required for conformance.
.1.3.6.1.4.1.2699.1.1.1.2,Job-Monitoring-MIB::jmJobID,,,,,,
.1.3.6.1.4.1.2699.1.1.1.2.1,Job-Monitoring-MIB::jmJobIDTable,,not-accessible,,current,,The jmJobIDTable provides a correspondence map (1) between the job submission ID that a client uses to refer to a job and (2) the jmGeneralJobSetIndex and jmJobIndex that the Job Monitoring MIB agent assigned to the job and that are used to access the job in all of the other tables in the MIB. If a monitoring application already knows the jmGeneralJobSetIndex and the jmJobIndex of the job it is querying, that application NEED NOT use the jmJobIDTable. The MANDATORY-GROUP macro specifies that this group is MANDATORY.
.1.3.6.1.4.1.2699.1.1.1.2.1.1,Job-Monitoring-MIB::jmJobIDEntry,,not-accessible,jmJobSubmissionID,current,,The map from (1) the jmJobSubmissionID to (2) the jmGeneralJobSetIndex and jmJobIndex. An entry SHALL exist in this table for each job currently known to the agent for all job sets and job states. There MAY be more than one jmJobIDEntry that maps to a single job. This many to one mapping can occur when more than one network entity along the job submission path supplies a job submission ID. See Section 3.5. However, each job SHALL appear once and in one and only one job set.
.1.3.6.1.4.1.2699.1.1.1.2.1.1.1,Job-Monitoring-MIB::jmJobSubmissionID,OCTET,not-accessible,,current,,A quasi-unique 48-octet fixed-length string ID which identifies the job within a particular client-server environment. There are multiple formats for the jmJobSubmissionID. Each format SHALL be uniquely identified. See the JmJobSubmissionIDTypeTC textual convention. Each format SHALL be registered using the procedures of a type 2 enum. See section 3.7.3 entitled: 'PWG Registration of Job Submission Id Formats'. If the requester (client or server) does not supply a job submission ID in the job submission protocol, then the recipient (server or device) SHALL assign a job submission ID using any of the standard formats that have been reserved for agents and adding the final 8 octets to distinguish the ID from others submitted from the same requester. The monitoring application, whether in the client or running separately, MAY use the job submission ID to help identify which jmJobIndex was assigned by the agent, i.e., in which row the job information is in the other tables. NOTE - fixed-length is used so that a management application can use a shortened GetNext varbind (in SNMPv1 and SNMPv2) in order to get the next submission ID, disregarding the remainder of the ID in order to access jobs independent of the trailing identifier part, e.g., to get all jobs submitted by a particular jmJobOwner or submitted from a particular MAC address. See the JmJobSubmissionIDTypeTC textual convention. See APPENDIX B - Support of Job Submission Protocols.
.1.3.6.1.4.1.2699.1.1.1.2.1.1.2,Job-Monitoring-MIB::jmJobIDJobSetIndex,Integer32,read-only,,current,,This object contains the value of the jmGeneralJobSetIndex for the job with the jmJobSubmissionID value, i.e., the job set index of the job set in which the job was placed when that server or device accepted the job. This 16-bit value in combination with the jmJobIDJobIndex value permits the management application to access the other tables to obtain the job-specific objects for this job. See jmGeneralJobSetIndex in the jmGeneralTable.
.1.3.6.1.4.1.2699.1.1.1.2.1.1.3,Job-Monitoring-MIB::jmJobIDJobIndex,Integer32,read-only,,current,,This object contains the value of the jmJobIndex for the job with the jmJobSubmissionID value, i.e., the job index for the job when the server or device accepted the job. This value, in combination with the jmJobIDJobSetIndex value, permits the management application to access the other tables to obtain the job-specific objects for this job. See jmJobIndex in the jmJobTable.
.1.3.6.1.4.1.2699.1.1.1.3,Job-Monitoring-MIB::jmJob,,,,,,
.1.3.6.1.4.1.2699.1.1.1.3.1,Job-Monitoring-MIB::jmJobTable,,not-accessible,,current,,The jmJobTable consists of basic job state and status information for each job in a job set that (1) monitoring applications need to be able to access in a single SNMP Get operation, (2) that have a single value per job, and (3) that SHALL always be implemented. The MANDATORY-GROUP macro specifies that this group is MANDATORY.
.1.3.6.1.4.1.2699.1.1.1.3.1.1,Job-Monitoring-MIB::jmJobEntry,,not-accessible,jmGeneralJobSetIndex:jmJobIndex,current,,Basic per-job state and status information. An entry SHALL exist in this table for each job, no matter what the state of the job is. Each job SHALL appear in one and only one job set. See Section 3.2 entitled 'The Job Tables'.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.1,Job-Monitoring-MIB::jmJobIndex,Integer32,not-accessible,,current,,The sequential, monatonically increasing identifier index for the job generated by the server or device when that server or device accepted the job. This index value permits the management application to access the other tables to obtain the job-specific row entries. See Section 3.2 entitled 'The Job Tables and the Oldest Active and Newest Active Indexes'. See Section 3.5 entitled 'Job Identification'. See also jmGeneralNewestActiveJobIndex for the largest value of jmJobIndex. See JmJobSubmissionIDTypeTC for a limit on the size of this index if the agent represents it as an 8-digit decimal number.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.2,Job-Monitoring-MIB::jmJobState,INTEGER,read-only,,current,unknown(2):pending(3):pendingHeld(4):processing(5):processingStopped(6):canceled(7):aborted(8):completed(9),The current state of the job (pending, processing, completed, etc.). Agents SHALL implement only those states which are appropriate for the particular implementation. However, management applications SHALL be prepared to receive all the standard job states. The final value for this object SHALL be one of: completed, canceled, or aborted. The minimum length of time that the agent SHALL maintain MIB data for a job in the completed, canceled, or aborted state before removing the job data from the jmJobIDTable and jmJobTable is specified by the value of the jmGeneralJobPersistence object.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.3,Job-Monitoring-MIB::jmJobStateReasons1,INTEGER,read-only,,current,,Additional information about the job's current state, i.e., information that augments the value of the job's jmJobState object. Implementation of any reason values is OPTIONAL, but an agent SHOULD return any reason information available. These values MAY be used with any job state or states for which the reason makes sense. Since the Job State Reasons will be more dynamic than the Job State, it is recommended that a job monitoring application read this object every time jmJobState is read. When the agent cannot provide a reason for the current state of the job, the value of the jmJobStateReasons1 object and jobStateReasonsN attributes SHALL be 0. The jobStateReasonsN (N=2..4) attributes provide further additional information about the job's current state.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.4,Job-Monitoring-MIB::jmNumberOfInterveningJobs,Integer32,read-only,,current,,The number of jobs that are expected to complete processing before this job has completed processing according to the implementation's queuing algorithm, if no other jobs were to be submitted. In other words, this value is the job's queue position. The agent SHALL return a value of 0 for this attribute when the job is the next job to complete processing (or has completed processing).
.1.3.6.1.4.1.2699.1.1.1.3.1.1.5,Job-Monitoring-MIB::jmJobKOctetsPerCopyRequested,Integer32,read-only,,current,,The total size in K (1024) octets of the document(s) being requested to be processed in the job. The agent SHALL round the actual number of octets up to the next highest K. Thus 0 octets is represented as '0', 1-1024 octets is represented as '1', 1025-2048 is represented as '2', etc. In computing this value, the server/device SHALL NOT include the multiplicative factors contributed by (1) the number of document copies, and (2) the number of job copies, independent of whether the device can process multiple copies of the job or document without making multiple passes over the job or document data and independent of whether the output is collated or not. Thus the server/device computation is independent of the implementation and indicates the size of the document(s) measured in K octets independent of the number of copies.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.6,Job-Monitoring-MIB::jmJobKOctetsProcessed,Integer32,read-only,,current,,The total number of octets processed by the server or device measured in units of K (1024) octets so far. The agent SHALL round the actual number of octets processed up to the next higher K. Thus 0 octets is represented as '0', 1-1024 octets is represented as '1', 1025-2048 octets is '2', etc. For printing devices, this value is the number interpreted by the page description language interpreter rather than what has been marked on media. For implementations where multiple copies are produced by the interpreter with only a single pass over the data, the final value SHALL be equal to the value of the jmJobKOctetsPerCopyRequested object. For implementations where multiple copies are produced by the interpreter by processing the data for each copy, the final value SHALL be a multiple of the value of the jmJobKOctetsPerCopyRequested object. NOTE - See the impressionsCompletedCurrentCopy and pagesCompletedCurrentCopy attributes for attributes that are reset on each document copy. NOTE - The jmJobKOctetsProcessed object can be used with the jmJobKOctetsPerCopyRequested object to provide an indication of the relative progress of the job, provided that the multiplicative factor is taken into account for some implementations of multiple copies.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.7,Job-Monitoring-MIB::jmJobImpressionsPerCopyRequested,Integer32,read-only,,current,,The total size in number of impressions of the document(s) submitted. In computing this value, the server/device SHALL NOT include the multiplicative factors contributed by (1) the number of document copies, and (2) the number of job copies, independent of whether the device can process multiple copies of the job or document without making multiple passes over the job or document data and independent of whether the output is collated or not. Thus the server/device computation is independent of the implementation and reflects the size of the document(s) measured in impressions independent of the number of copies. See the definition of the term 'impression' in Section 2.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.8,Job-Monitoring-MIB::jmJobImpressionsCompleted,Integer32,read-only,,current,,The total number of impressions completed for this job so far. For printing devices, the impressions completed includes interpreting, marking, and stacking the output. For other types of job services, the number of impressions completed includes the number of impressions processed. NOTE - See the impressionsCompletedCurrentCopy and pagesCompletedCurrentCopy attributes for attributes that are reset on each document copy. NOTE - The jmJobImpressionsCompleted object can be used with the jmJobImpressionsPerCopyRequested object to provide an indication of the relative progress of the job, provided that the multiplicative factor is taken into account for some implementations of multiple copies. See the definition of the term 'impression' in Section 2 and the counting example in Section 3.4 entitled 'Monitoring Job Progress'.
.1.3.6.1.4.1.2699.1.1.1.3.1.1.9,Job-Monitoring-MIB::jmJobOwner,OCTET,read-only,,current,,The coded character set name of the user that submitted the job. The method of assigning this user name will be system and/or site specific but the method MUST ensure that the name is unique to the network that is visible to the client and target device. This value SHOULD be the most authenticated name of the user submitting the job. See the OBJECT compliance macro for the minimum maximum length required for conformance.
.1.3.6.1.4.1.2699.1.1.1.4,Job-Monitoring-MIB::jmAttribute,,,,,,
.1.3.6.1.4.1.2699.1.1.1.4.1,Job-Monitoring-MIB::jmAttributeTable,,not-accessible,,current,,The jmAttributeTable SHALL contain attributes of the job and document(s) for each job in a job set. Instead of allocating distinct objects for each attribute, each attribute is represented as a separate row in the jmAttributeTable. The MANDATORY-GROUP macro specifies that this group is MANDATORY. An agent SHALL implement any attribute if (1) the server or device supports the functionality represented by the attribute and (2) the information is available to the agent. 
.1.3.6.1.4.1.2699.1.1.1.4.1.1,Job-Monitoring-MIB::jmAttributeEntry,,not-accessible,jmGeneralJobSetIndex:jmJobIndex:jmAttributeTypeIndex:jmAttributeInstanceIndex,current,,Attributes representing information about the job and document(s) or resources required and/or consumed. Each entry in the jmAttributeTable is a per-job entry with an extra index for each type of attribute (jmAttributeTypeIndex) that a job can have and an additional index (jmAttributeInstanceIndex) for those attributes that can have multiple instances per job. The jmAttributeTypeIndex object SHALL contain an enum type that indicates the type of attribute (see the JmAttributeTypeTC textual-convention). The value of the attribute SHALL be represented in either the jmAttributeValueAsInteger or jmAttributeValueAsOctets objects, and/or both, as specified in the JmAttributeTypeTC textual- convention. The agent SHALL create rows in the jmAttributeTable as the server or device is able to discover the attributes either from the job submission protocol itself or from the document PDL. As the documents are interpreted, the interpreter MAY discover additional attributes and so the agent adds additional rows to this table. As the attributes that represent resources are actually consumed, the usage counter contained in the jmAttributeValueAsInteger object is incremented according to the units indicated in the description of the JmAttributeTypeTC enum. The agent SHALL maintain each row in the jmAttributeTable for at least the minimum time after a job completes as specified by the jmGeneralAttributePersistence object. Zero or more entries SHALL exist in this table for each job in a job set. See Section 3.3 entitled 'The Attribute Mechanism' for a description of the jmAttributeTable.
.1.3.6.1.4.1.2699.1.1.1.4.1.1.1,Job-Monitoring-MIB::jmAttributeTypeIndex,INTEGER,not-accessible,,current,other(1):jobStateReasons2(3):jobStateReasons3(4):jobStateReasons4(5):processingMessage(6):processingMessageNaturalLangTag(7):jobCodedCharSet(8):jobNaturalLanguageTag(9):jobURI(20):jobAccountName(21):serverAssignedJobName(22):jobName(23):jobServiceTypes(24):jobSourceChannelIndex(25):jobSourcePlatformType(26):submittingServerName(27):submittingApplicationName(28):jobOriginatingHost(29):deviceNameRequested(30):queueNameRequested(31):physicalDevice(32):numberOfDocuments(33):fileName(34):documentName(35):jobComment(36):documentFormatIndex(37):documentFormat(38):jobPriority(50):jobProcessAfterDateAndTime(51):jobHold(52):jobHoldUntil(53):outputBin(54):sides(55):finishing(56):printQualityRequested(70):printQualityUsed(71):printerResolutionRequested(72):printerResolutionUsed(73):tonerEcomonyRequested(74):tonerEcomonyUsed(75):tonerDensityRequested(76):tonerDensityUsed(77):jobCopiesRequested(90):jobCopiesCompleted(91):documentCopiesRequested(92):documentCopiesCompleted(93):jobKOctetsTransferred(94):sheetCompletedCopyNumber(95):sheetCompletedDocumentNumber(96):jobCollationType(97):impressionsSpooled(110):impressionsSentToDevice(111):impressionsInterpreted(112):impressionsCompletedCurrentCopy(113):fullColorImpressionsCompleted(114):highlightColorImpressionsCompleted(115):pagesRequested(130):pagesCompleted(131):pagesCompletedCurrentCopy(132):sheetsRequested(150):sheetsCompleted(151):sheetsCompletedCurrentCopy(152):mediumRequested(170):mediumConsumed(171):colorantRequested(172):colorantConsumed(173):mediumTypeConsumed(174):mediumSizeConsumed(175):jobSubmissionToServerTime(190):jobSubmissionTime(191):jobStartedBeingHeldTime(192):jobStartedProcessingTime(193):jobCompletionTime(194):jobProcessingCPUTime(195),The type of attribute that this row entry represents. The type MAY identify information about the job or document(s) or MAY identify a resource required to process the job before the job start processing and/or consumed by the job as the job is processed. Examples of job attributes (i.e., apply to the job as a whole) that have only one instance per job include: jobCopiesRequested(90), documentCopiesRequested(92), jobCopiesCompleted(91), documentCopiesCompleted(93), while examples of job attributes that may have more than one instance per job include: documentFormatIndex(37), and documentFormat(38). Examples of document attributes (one instance per document) include: fileName(34), and documentName(35). Examples of required and consumed resource attributes include: pagesRequested(130), mediumRequested(170), pagesCompleted(131), and mediumConsumed(171), respectively.
.1.3.6.1.4.1.2699.1.1.1.4.1.1.2,Job-Monitoring-MIB::jmAttributeInstanceIndex,Integer32,not-accessible,,current,,A running 16-bit index of the attributes of the same type for each job. For those attributes with only a single instance per job, this index value SHALL be 1. For those attributes that are a single value per document, the index value SHALL be the document number, starting with 1 for the first document in the job. Jobs with only a single document SHALL use the index value of 1. For those attributes that can have multiple values per job or per document, such as documentFormatIndex(37) or documentFormat(38), the index SHALL be a running index for the job as a whole, starting at 1.
.1.3.6.1.4.1.2699.1.1.1.4.1.1.3,Job-Monitoring-MIB::jmAttributeValueAsInteger,Integer32,read-only,,current,,The integer value of the attribute. The value of the attribute SHALL be represented as an integer if the enum description in the JmAttributeTypeTC textual-convention definition has the tag: 'INTEGER:'. Depending on the enum definition, this object value MAY be an integer, a counter, an index, or an enum, depending on the jmAttributeTypeIndex value. The units of this value are specified in the enum description. For those attributes that are accumulating job consumption as the job is processed as specified in the JmAttributeTypeTC textual-convention, SHALL contain the final value after the job completes processing, i.e., this value SHALL indicate the total usage of this resource made by the job. A monitoring application is able to copy this value to a suitable longer term storage for later processing as part of an accounting system. Since the agent MAY add attributes representing resources to this table while the job is waiting to be processed or being processed, which can be a long time before any of the resources are actually used, the agent SHALL set the value of the jmAttributeValueAsInteger object to 0 for resources that the job has not yet consumed. Attributes for which the concept of an integer value is meaningless, such as fileName(34), jobName, and processingMessage, do not have the 'INTEGER:' tag in the JmAttributeTypeTC definition and so an agent SHALL always return a value of '-1' to indicate 'other' for the value of the jmAttributeValueAsInteger object for these attributes. For attributes which do have the 'INTEGER:' tag in the JmAttributeTypeTC definition, if the integer value is not (yet) known, the agent either (1) SHALL not materialize the row in the jmAttributeTable until the value is known or (2) SHALL return a '-2' to represent an 'unknown' counting integer value, a '0' to represent an 'unknown' index value, and a '2' to represent an 'unknown(2)' enum value.
.1.3.6.1.4.1.2699.1.1.1.4.1.1.4,Job-Monitoring-MIB::jmAttributeValueAsOctets,OCTET,read-only,,current,,The octet string value of the attribute. The value of the attribute SHALL be represented as an OCTET STRING if the enum description in the JmAttributeTypeTC textual-convention definition has the tag: 'OCTETS:'. Depending on the enum definition, this object value MAY be a coded character set string (text), such as 'JmUTF8StringTC', or a binary octet string, such as 'DateAndTime'. Attributes for which the concept of an octet string value is meaningless, such as pagesCompleted, do not have the tag 'OCTETS:' in the JmAttributeTypeTC definition and so the agent SHALL always return a zero length string for the value of the jmAttributeValueAsOctets object. For attributes which do have the 'OCTETS:' tag in the JmAttributeTypeTC definition, if the OCTET STRING value is not (yet) known, the agent either SHALL NOT materialize the row in the jmAttributeTable until the value is known or SHALL return a zero-length string.
.1.3.6.1.4.1.2699.1.1.2,Job-Monitoring-MIB::jobmonMIBNotifications,,,,,,
.1.3.6.1.4.1.2699.1.1.3,Job-Monitoring-MIB::jmMIBConformance,,,,,,
.1.3.6.1.4.1.2699.1.1.3.1,Job-Monitoring-MIB::jmMIBCompliance,,,,,,The compliance statement for agents that implement the job monitoring MIB.
.1.3.6.1.4.1.2699.1.1.3.2,Job-Monitoring-MIB::jmMIBGroups,,,,,,
.1.3.6.1.4.1.2699.1.1.3.2.1,Job-Monitoring-MIB::jmGeneralGroup,,,,,,The general group.
.1.3.6.1.4.1.2699.1.1.3.2.2,Job-Monitoring-MIB::jmJobIDGroup,,,,,,The job ID group.
.1.3.6.1.4.1.2699.1.1.3.2.3,Job-Monitoring-MIB::jmJobGroup,,,,,,The job group.
.1.3.6.1.4.1.2699.1.1.3.2.4,Job-Monitoring-MIB::jmAttributeGroup,,,,,,The attribute group.
.1.3.6.1.4.1.4300,SFLOW-MIB::anonymous#0,,,,,,
.1.3.6.1.4.1.4300.1,SFLOW-MIB::sFlowMIB,,,,,,The MIB module for managing the generation and transportation of sFlow data records.
.1.3.6.1.4.1.4300.1.1,SFLOW-MIB::sFlowAgent,,,,,,
.1.3.6.1.4.1.4300.1.1.1,SFLOW-MIB::sFlowVersion,OCTET,read-only,,current,,Uniquely identifies the version and implementation of this MIB. The version string must have the following structure: <MIB Version>;<Organization>;<Software Revision> where: <MIB Version> must be '1.2', the version of this MIB. <Organization> the name of the organization responsible for the agent implementation. <Revision> the specific software build of this agent. As an example, the string '1.2;InMon Corp.;2.1.1' indicates that this agent implements version '1.2' of the SFLOW MIB, that it was developed by 'InMon Corp.' and that the software build is '2.1.1'. The MIB Version will change with each revision of the SFLOW MIB. Management entities must check the MIB Version and not attempt to manage agents with MIB Versions greater than that for which they were designed. Note: The sFlow Datagram Format has an independent version number which may change independently from <MIB Version>. <MIB Version> applies to the structure and semantics of the SFLOW MIB only.
.1.3.6.1.4.1.4300.1.1.2,SFLOW-MIB::sFlowAgentAddressType,INTEGER,read-only,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The address type of the address associated with this agent. Only ipv4 and ipv6 types are supported.
.1.3.6.1.4.1.4300.1.1.3,SFLOW-MIB::sFlowAgentAddress,OCTET,read-only,,current,,The IP address associated with this agent. In the case of a multi-homed agent, this should be the loopback address of the agent. The sFlowAgent address must provide SNMP connectivity to the agent. The address should be an invariant that does not change as interfaces are reconfigured, enabled, disabled, added or removed. A manager should be able to use the sFlowAgentAddress as a unique key that will identify this agent over extended periods of time so that a history can be maintained.
.1.3.6.1.4.1.4300.1.1.4,SFLOW-MIB::sFlowTable,,not-accessible,,current,,A table of the sFlow samplers within a device.
.1.3.6.1.4.1.4300.1.1.4.1,SFLOW-MIB::sFlowEntry,,not-accessible,sFlowDataSource,current,,Attributes of an sFlow sampler.
.1.3.6.1.4.1.4300.1.1.4.1.1,SFLOW-MIB::sFlowDataSource,OBJECT,read-only,,current,,Identifies the source of the data for the sFlow sampler. The following data source types are currently defined: - ifIndex.<I> DataSources of this traditional form are called 'port-based'. Ideally the sampling entity will perform sampling on all flows originating from or destined to the specified interface. However, if the switch architecture only permits input or output sampling then the sampling agent is permitted to only sample input flows input or output flows. Each packet must only be considered once for sampling, irrespective of the number of ports it will be forwarded to. Note: Port 0 is used to indicate that all ports on the device are represented by a single data source. - sFlowPacketSamplingRate applies to all ports on the device capable of packet sampling. - sFlowCounterSamplingInterval applies to all ports. - smonVlanDataSource.<V> A dataSource of this form refers to a 'Packet-based VLAN' and is called a 'VLAN-based' dataSource. <V> is the VLAN ID as defined by the IEEE 802.1Q standard. The value is between 1 and 4094 inclusive, and it represents an 802.1Q VLAN-ID with global scope within a given bridged domain. Sampling is performed on all packets received that are part of the specified VLAN (no matter which port they arrived on). Each packet will only be considered once for sampling, irrespective of the number of ports it will be forwarded to. - entPhysicalEntry.<N> A dataSource of this form refers to a physical entity within the agent (e.g., entPhysicalClass = backplane(4)) and is called an 'entity-based' dataSource. Sampling is performed on all packets entering the resource (e.g. If the backplane is being sampled, all packets transmitted onto the backplane will be considered as single candidates for sampling irrespective of the number of ports they ultimately reach). Note: Since each DataSource operates independently, a packet that crosses multiple DataSources may generate multiple flow records.
.1.3.6.1.4.1.4300.1.1.4.1.2,SFLOW-MIB::sFlowOwner,OCTET,read-write,,current,,The entity making use of this sFlow sampler. The empty string indicates that the sFlow sampler is currently unclaimed. An entity wishing to claim an sFlow sampler must make sure that the sampler is unclaimed before trying to claim it. The sampler is claimed by setting the owner string to identify the entity claiming the sampler. The sampler must be claimed before any changes can be made to other sampler objects. In order to avoid a race condition, the entity taking control of the sampler must set both the owner and a value for sFlowTimeout in the same SNMP set request. When a management entity is finished using the sampler, it should set its value back to unclaimed. The agent must restore all other entities this row to their default values when the owner is set to unclaimed. This mechanism provides no enforcement and relies on the cooperation of management entities in order to ensure that competition for a sampler is fairly resolved.
.1.3.6.1.4.1.4300.1.1.4.1.3,SFLOW-MIB::sFlowTimeout,Integer32,read-write,,current,,The time (in seconds) remaining before the sampler is released and stops sampling. When set, the owner establishes control for the specified period. When read, the remaining time in the interval is returned. A management entity wanting to maintain control of the sampler is responsible for setting a new value before the old one expires. When the interval expires, the agent is responsible for restoring all other entities in this row to their default values.
.1.3.6.1.4.1.4300.1.1.4.1.4,SFLOW-MIB::sFlowPacketSamplingRate,Integer32,read-write,,current,,The statistical sampling rate for packet sampling from this source. Set to N to sample 1/Nth of the packets in the monitored flows. An agent should choose its own algorithm introduce variance into the sampling so that exactly every Nth packet is not counted. A sampling rate of 1 counts all packets. A sampling rate of 0 disables sampling. The agent is permitted to have minimum and maximum allowable values for the sampling rate. A minimum rate lets the agent designer set an upper bound on the overhead associated with sampling, and a maximum rate may be the result of hardware restrictions (such as counter size). In addition not all values between the maximum and minimum may be realizable as the sampling rate (again because of implementation considerations). When the sampling rate is set the agent is free to adjust the value so that it lies between the maximum and minimum values and has the closest achievable value. When read, the agent must return the actual sampling rate it will be using (after the adjustments previously described). The sampling algorithm must converge so that over time the number of packets sampled approaches 1/Nth of the total number of packets in the monitored flows.
.1.3.6.1.4.1.4300.1.1.4.1.5,SFLOW-MIB::sFlowCounterSamplingInterval,Integer32,read-write,,current,,The maximum number of seconds between successive samples of the counters associated with this data source. A sampling interval of 0 disables counter sampling.
.1.3.6.1.4.1.4300.1.1.4.1.6,SFLOW-MIB::sFlowMaximumHeaderSize,Integer32,read-write,,current,,The maximum number of bytes that should be copied from a sampled packet. The agent may have an internal maximum and minimum permissible sizes. If an attempt is made to set this value outside the permissible range then the agent should adjust the value to the closest permissible value.
.1.3.6.1.4.1.4300.1.1.4.1.7,SFLOW-MIB::sFlowMaximumDatagramSize,Integer32,read-write,,current,,The maximum number of data bytes that can be sent in a single sample datagram. The manager should set this value to avoid fragmentation of the sFlow datagrams.
.1.3.6.1.4.1.4300.1.1.4.1.8,SFLOW-MIB::sFlowCollectorAddressType,INTEGER,read-write,,current,unknown(0):ipv4(1):ipv6(2):ipv4z(3):ipv6z(4):dns(16),The type of sFlowCollectorAddress.
.1.3.6.1.4.1.4300.1.1.4.1.9,SFLOW-MIB::sFlowCollectorAddress,OCTET,read-write,,current,,The IP address of the sFlow collector. If set to 0.0.0.0 all sampling is disabled.
.1.3.6.1.4.1.4300.1.1.4.1.10,SFLOW-MIB::sFlowCollectorPort,Integer32,read-write,,current,,The destination port for sFlow datagrams.
.1.3.6.1.4.1.4300.1.1.4.1.11,SFLOW-MIB::sFlowDatagramVersion,Integer32,read-write,,current,,The version of sFlow datagrams that should be sent. When set to a value not support by the agent, the agent should adjust the value to the highest supported value less than the requested value, or return an error if no such values exist.
.1.3.6.1.4.1.4300.1.2,SFLOW-MIB::sFlowMIBConformance,,,,,,
.1.3.6.1.4.1.4300.1.2.1,SFLOW-MIB::sFlowMIBGroups,,,,,,
.1.3.6.1.4.1.4300.1.2.1.1,SFLOW-MIB::sFlowAgentGroup,,,,,,A collection of objects for managing the generation and transportation of sFlow data records.
.1.3.6.1.4.1.4300.1.2.2,SFLOW-MIB::sFlowMIBCompliances,,,,,,
.1.3.6.1.4.1.4300.1.2.2.1,SFLOW-MIB::sFlowCompliance,,,,,,Compliance statements for the sFlow Agent.
.1.3.6.1.4.1.12325,FOKUS-MIB::fokus,,,,,,The root of the Fokus enterprises tree.
.1.3.6.1.4.1.12325.1,BEGEMOT-MIB::begemot,,,,,,The root of the Begemot subtree of the fokus tree.
.1.3.6.1.4.1.12325.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpd,,,,,,The MIB module for the Begemot SNMP daemon.
.1.3.6.1.4.1.12325.1.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdObjects,,,,,,
.1.3.6.1.4.1.12325.1.1.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdConfig,,,,,,
.1.3.6.1.4.1.12325.1.1.1.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdTransmitBuffer,INTEGER,read-write,,current,,The size of the receive buffer in bytes. Larger messages
.1.3.6.1.4.1.12325.1.1.1.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdReceiveBuffer,INTEGER,read-write,,current,,The size of the transmit buffer in bytes. Larger messages
.1.3.6.1.4.1.12325.1.1.1.1.3,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityDisable,INTEGER,read-write,,current,true(1):false(2),Disables all access to the CommunityTable from SNMP. Once
.1.3.6.1.4.1.12325.1.1.1.1.4,BEGEMOT-SNMPD-MIB::begemotSnmpdTrap1Addr,IpAddress,read-write,,current,,The trap sink for v1 traps.
.1.3.6.1.4.1.12325.1.1.1.1.5,BEGEMOT-SNMPD-MIB::begemotSnmpdVersionEnable,Unsigned32,read-only,,current,,The SNMP versions that the agent processes. The following
.1.3.6.1.4.1.12325.1.1.1.2,BEGEMOT-SNMPD-MIB::begemotTrapSinkTable,,not-accessible,begemotTrapSinkAddr:begemotTrapSinkPort,current,,A table with destinations for standard traps.
.1.3.6.1.4.1.12325.1.1.1.2.1,BEGEMOT-SNMPD-MIB::begemotTrapSinkEntry,,not-accessible,begemotTrapSinkAddr:begemotTrapSinkPort,current,,Entry describes one trap destination.
.1.3.6.1.4.1.12325.1.1.1.2.1.1,BEGEMOT-SNMPD-MIB::begemotTrapSinkAddr,IpAddress,not-accessible,,current,,Destination IP address of the manager station where to send
.1.3.6.1.4.1.12325.1.1.1.2.1.2,BEGEMOT-SNMPD-MIB::begemotTrapSinkPort,INTEGER,not-accessible,,current,,Destination UDP port of the manager station where to send
.1.3.6.1.4.1.12325.1.1.1.2.1.3,BEGEMOT-SNMPD-MIB::begemotTrapSinkStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create/activate/destroy the entry.
.1.3.6.1.4.1.12325.1.1.1.4,BEGEMOT-SNMPD-MIB::begemotSnmpdPortTable,,not-accessible,,current,,A table with descriptions of UDP ports to listen on
.1.3.6.1.4.1.12325.1.1.1.4.1,BEGEMOT-SNMPD-MIB::begemotSnmpdPortEntry,,not-accessible,begemotSnmpdPortAddress:begemotSnmpdPortPort,current,,An entry in the table with descriptions of UDP ports to
.1.3.6.1.4.1.12325.1.1.1.4.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdPortAddress,IpAddress,not-accessible,,current,,The IP address to bind to.
.1.3.6.1.4.1.12325.1.1.1.4.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdPortPort,INTEGER,not-accessible,,current,,The UDP port to listen on for SNMP messages.
.1.3.6.1.4.1.12325.1.1.1.4.1.3,BEGEMOT-SNMPD-MIB::begemotSnmpdPortStatus,INTEGER,read-create,,current,valid(1):invalid(2),Set status to 1 to create entry, set it to 2 to delete it.
.1.3.6.1.4.1.12325.1.1.1.5,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityTable,,not-accessible,,current,,A table with the community strings for access control.
.1.3.6.1.4.1.12325.1.1.1.5.1,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityEntry,,not-accessible,begemotSnmpdCommunityModule:begemotSnmpdCommunityIndex,current,,A table with the community strings for access control.
.1.3.6.1.4.1.12325.1.1.1.5.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityModule,OCTET,not-accessible,,current,,Index of the module that has registered this community.
.1.3.6.1.4.1.12325.1.1.1.5.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityIndex,Unsigned32,not-accessible,,current,,The numerical index of the community (private to the module).
.1.3.6.1.4.1.12325.1.1.1.5.1.3,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityString,OCTET,read-write,,current,,The string for access to SNMPd.
.1.3.6.1.4.1.12325.1.1.1.5.1.4,BEGEMOT-SNMPD-MIB::begemotSnmpdCommunityDescr,OCTET,read-only,,current,,A description what this community is good for.
.1.3.6.1.4.1.12325.1.1.1.6,BEGEMOT-SNMPD-MIB::begemotSnmpdModuleTable,,not-accessible,,current,,A table describing all the currently loaded dynamic modules.
.1.3.6.1.4.1.12325.1.1.1.6.1,BEGEMOT-SNMPD-MIB::begemotSnmpdModuleEntry,,not-accessible,begemotSnmpdModuleSection,current,,A table entry describing a loadable module.
.1.3.6.1.4.1.12325.1.1.1.6.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdModuleSection,OCTET,not-accessible,,current,,The string used for matching configuration file sections
.1.3.6.1.4.1.12325.1.1.1.6.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdModulePath,OCTET,read-create,,current,,The path name of the module. Set to empty string
.1.3.6.1.4.1.12325.1.1.1.6.1.3,BEGEMOT-SNMPD-MIB::begemotSnmpdModuleComment,OCTET,read-only,,current,,A comment describing this module.
.1.3.6.1.4.1.12325.1.1.1.7,BEGEMOT-SNMPD-MIB::begemotSnmpdStats,,,,,,
.1.3.6.1.4.1.12325.1.1.1.7.1,BEGEMOT-SNMPD-MIB::begemotSnmpdStatsNoRxBufs,Counter32,read-only,,current,,Number of times a receive buffer could not be allocated
.1.3.6.1.4.1.12325.1.1.1.7.2,BEGEMOT-SNMPD-MIB::begemotSnmpdStatsNoTxBufs,Counter32,read-only,,current,,Number of times a transmit buffer could not be allocated
.1.3.6.1.4.1.12325.1.1.1.7.3,BEGEMOT-SNMPD-MIB::begemotSnmpdStatsInTooLongPkts,Counter32,read-only,,current,,Number of packets received that were longer than the
.1.3.6.1.4.1.12325.1.1.1.7.4,BEGEMOT-SNMPD-MIB::begemotSnmpdStatsInBadPduTypes,Counter32,read-only,,current,,Number of packets received with a bad type field.
.1.3.6.1.4.1.12325.1.1.1.8,BEGEMOT-SNMPD-MIB::begemotSnmpdDebug,,,,,,
.1.3.6.1.4.1.12325.1.1.1.8.1,BEGEMOT-SNMPD-MIB::begemotSnmpdDebugDumpPdus,INTEGER,read-write,,current,true(1):false(2),Dump PDUs to log file if true.
.1.3.6.1.4.1.12325.1.1.1.8.2,BEGEMOT-SNMPD-MIB::begemotSnmpdDebugSnmpTrace,Unsigned32,read-write,,current,,Tracing flags for the SNMP library. These flags have the
.1.3.6.1.4.1.12325.1.1.1.8.3,BEGEMOT-SNMPD-MIB::begemotSnmpdDebugSyslogPri,INTEGER,read-write,,current,,Events with this or higher priority should not be logged.
.1.3.6.1.4.1.12325.1.1.1.9,BEGEMOT-SNMPD-MIB::begemotSnmpdLocalPortTable,,not-accessible,,current,,A table with descriptions of local (unix domain) ports to listen
.1.3.6.1.4.1.12325.1.1.1.9.1,BEGEMOT-SNMPD-MIB::begemotSnmpdLocalPortEntry,,not-accessible,begemotSnmpdLocalPortPath,current,,An entry in the table with descriptions of local ports to
.1.3.6.1.4.1.12325.1.1.1.9.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdLocalPortPath,OCTET,not-accessible,,current,,The path name to create and listen on.
.1.3.6.1.4.1.12325.1.1.1.9.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdLocalPortStatus,INTEGER,read-create,,current,valid(1):invalid(2),Set status to 1 to create entry, set it to 2 to delete it.
.1.3.6.1.4.1.12325.1.1.1.9.1.3,BEGEMOT-SNMPD-MIB::begemotSnmpdLocalPortType,INTEGER,read-create,,current,dgram-unpriv(1):dgram-priv(2):stream-unpriv(3):stream-priv(4),Type of the port. If the type is unpriv SET operations
.1.3.6.1.4.1.12325.1.1.1.10,BEGEMOT-SNMPD-MIB::begemotSnmpdTransportMappings,,,,,,
.1.3.6.1.4.1.12325.1.1.1.10.1,BEGEMOT-SNMPD-MIB::begemotSnmpdTransportTable,,not-accessible,,current,,A table containing all the currently loaded transport mappings.
.1.3.6.1.4.1.12325.1.1.1.10.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdTransportEntry,,not-accessible,begemotSnmpdTransportName,current,,An entry in the table with the transport mappings.
.1.3.6.1.4.1.12325.1.1.1.10.1.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdTransportName,OCTET,not-accessible,,current,,The name of the mapping.
.1.3.6.1.4.1.12325.1.1.1.10.1.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdTransportStatus,INTEGER,read-only,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create/activate/destroy the entry.
.1.3.6.1.4.1.12325.1.1.1.10.1.1.3,BEGEMOT-SNMPD-MIB::begemotSnmpdTransportOid,OBJECT,read-only,,current,,A pointer to the group with the transport-dependend stuff.
.1.3.6.1.4.1.12325.1.1.1.10.2,BEGEMOT-SNMPD-MIB::begemotSnmpdTransUdp,,,,,,
.1.3.6.1.4.1.12325.1.1.1.10.3,BEGEMOT-SNMPD-MIB::begemotSnmpdTransLsock,,,,,,
.1.3.6.1.4.1.12325.1.1.2,BEGEMOT-SNMPD-MIB::begemotSnmpdDefs,,,,,,
.1.3.6.1.4.1.12325.1.1.2.1,BEGEMOT-SNMPD-MIB::begemotSnmpdAgent,,,,,,
.1.3.6.1.4.1.12325.1.1.2.1.1,BEGEMOT-SNMPD-MIB::begemotSnmpdAgentFreeBSD,,,,,,Identifies the agent as running on FreeBSD.
.1.3.6.1.4.1.12325.1.2,BEGEMOT-NETGRAPH-MIB::begemotNg,,,,,,The MIB for the NetGraph access module for SNMP.
.1.3.6.1.4.1.12325.1.2.1,BEGEMOT-NETGRAPH-MIB::begemotNgObjects,,,,,,
.1.3.6.1.4.1.12325.1.2.1.1,BEGEMOT-NETGRAPH-MIB::begemotNgConfig,,,,,,
.1.3.6.1.4.1.12325.1.2.1.1.1,BEGEMOT-NETGRAPH-MIB::begemotNgControlNodeName,OCTET,read-only,,current,,The name of the netgraph node of this daemon. The name is
.1.3.6.1.4.1.12325.1.2.1.1.2,BEGEMOT-NETGRAPH-MIB::begemotNgResBufSiz,INTEGER,read-write,,current,,The size of the receive buffers for netgraph messages.
.1.3.6.1.4.1.12325.1.2.1.1.3,BEGEMOT-NETGRAPH-MIB::begemotNgTimeout,INTEGER,read-write,,current,,The maximum time to wait for a response to a netgraph message.
.1.3.6.1.4.1.12325.1.2.1.1.4,BEGEMOT-NETGRAPH-MIB::begemotNgDebugLevel,Unsigned32,read-write,,current,,The netgraph library debug level. This should be set only
.1.3.6.1.4.1.12325.1.2.1.2,BEGEMOT-NETGRAPH-MIB::begemotNgStats,,,,,,
.1.3.6.1.4.1.12325.1.2.1.2.1,BEGEMOT-NETGRAPH-MIB::begemotNgNoMems,Counter32,read-only,,current,,Number of times a memory allocation has failed for buffers
.1.3.6.1.4.1.12325.1.2.1.2.2,BEGEMOT-NETGRAPH-MIB::begemotNgMsgReadErrs,Counter32,read-only,,current,,Number of times reading a netgraph message has failed.
.1.3.6.1.4.1.12325.1.2.1.2.3,BEGEMOT-NETGRAPH-MIB::begemotNgTooLargeMsgs,Counter32,read-only,,current,,Number of times a netgraph message was too large for
.1.3.6.1.4.1.12325.1.2.1.2.4,BEGEMOT-NETGRAPH-MIB::begemotNgDataReadErrs,Counter32,read-only,,current,,Number of times reading a netgraph data message has failed.
.1.3.6.1.4.1.12325.1.2.1.2.5,BEGEMOT-NETGRAPH-MIB::begemotNgTooLargeDatas,Counter32,read-only,,current,,Number of times a netgraph data message was too large.
.1.3.6.1.4.1.12325.1.2.1.3,BEGEMOT-NETGRAPH-MIB::begemotNgTypeTable,,not-accessible,,current,,A table containing information about all netgraph node types.
.1.3.6.1.4.1.12325.1.2.1.3.1,BEGEMOT-NETGRAPH-MIB::begemotNgTypeEntry,,not-accessible,begemotNgTypeName,current,,Table entry that describes one netgraph node.
.1.3.6.1.4.1.12325.1.2.1.3.1.1,BEGEMOT-NETGRAPH-MIB::begemotNgTypeName,OCTET,not-accessible,,current,,The name of the type. Used as index.
.1.3.6.1.4.1.12325.1.2.1.3.1.2,BEGEMOT-NETGRAPH-MIB::begemotNgTypeStatus,INTEGER,read-create,,current,loaded(1):unloaded(2),If loaded then the node type is available. A type can be load
.1.3.6.1.4.1.12325.1.2.1.4,BEGEMOT-NETGRAPH-MIB::begemotNgNodeTable,,not-accessible,,current,,A table containing information about all netgraph nodes.
.1.3.6.1.4.1.12325.1.2.1.4.1,BEGEMOT-NETGRAPH-MIB::begemotNgNodeEntry,,not-accessible,begemotNgNodeId,current,,Table entry that describes one netgraph node.
.1.3.6.1.4.1.12325.1.2.1.4.1.1,BEGEMOT-NETGRAPH-MIB::begemotNgNodeId,Unsigned32,not-accessible,,current,,The 32bit node id of this node. 0 is an illegal value.
.1.3.6.1.4.1.12325.1.2.1.4.1.2,BEGEMOT-NETGRAPH-MIB::begemotNgNodeStatus,INTEGER,read-only,,current,valid(1):invalid(2),Indicates whether the node exists or not.
.1.3.6.1.4.1.12325.1.2.1.4.1.3,BEGEMOT-NETGRAPH-MIB::begemotNgNodeName,OCTET,read-only,,current,,Name of the node (if any).
.1.3.6.1.4.1.12325.1.2.1.4.1.4,BEGEMOT-NETGRAPH-MIB::begemotNgNodeType,OCTET,read-only,,current,,Type name of the node.
.1.3.6.1.4.1.12325.1.2.1.4.1.5,BEGEMOT-NETGRAPH-MIB::begemotNgNodeHooks,Unsigned32,read-only,,current,,Number of hooks on this node.
.1.3.6.1.4.1.12325.1.2.1.5,BEGEMOT-NETGRAPH-MIB::begemotNgHookTable,,not-accessible,,current,,A table containing information about all netgraph hooks.
.1.3.6.1.4.1.12325.1.2.1.5.1,BEGEMOT-NETGRAPH-MIB::begemotNgHookEntry,,not-accessible,begemotNgHookNodeId:begemotNgHookHook,current,,Table entry that describes one netgraph node.
.1.3.6.1.4.1.12325.1.2.1.5.1.1,BEGEMOT-NETGRAPH-MIB::begemotNgHookNodeId,Unsigned32,not-accessible,,current,,The 32bit node id of this node.
.1.3.6.1.4.1.12325.1.2.1.5.1.2,BEGEMOT-NETGRAPH-MIB::begemotNgHookHook,OCTET,read-only,,current,,Name of the hook.
.1.3.6.1.4.1.12325.1.2.1.5.1.3,BEGEMOT-NETGRAPH-MIB::begemotNgHookStatus,INTEGER,read-only,,current,valid(1):invalid(2),Indicates whether the hook exists or not.
.1.3.6.1.4.1.12325.1.2.1.5.1.4,BEGEMOT-NETGRAPH-MIB::begemotNgHookPeerNodeId,Unsigned32,read-only,,current,,The 32bit node id of the peer node of this hook.
.1.3.6.1.4.1.12325.1.2.1.5.1.5,BEGEMOT-NETGRAPH-MIB::begemotNgHookPeerHook,OCTET,read-only,,current,,Name of the peer hook.
.1.3.6.1.4.1.12325.1.2.1.5.1.6,BEGEMOT-NETGRAPH-MIB::begemotNgHookPeerType,OCTET,read-only,,current,,Name of the peer type.
.1.3.6.1.4.1.12325.1.3,BEGEMOT-IP-MIB::begemotIp,,,,,,The MIB for IP stuff that is not in the official IP MIBs.
.1.3.6.1.4.1.12325.1.3.1,BEGEMOT-IP-MIB::begemotIpObjects,,,,,,
.1.3.6.1.4.1.12325.1.3.1.1,BEGEMOT-MIB2-MIB::begemotIfMaxspeed,Counter64,read-only,,current,,The speed of the fastest interface in ifTable in bps.
.1.3.6.1.4.1.12325.1.3.1.2,BEGEMOT-MIB2-MIB::begemotIfPoll,TimeTicks,read-only,,current,,The current polling rate for the HC 64-bit counters.
.1.3.6.1.4.1.12325.1.3.1.3,BEGEMOT-MIB2-MIB::begemotIfForcePoll,TimeTicks,read-write,,current,,The polling rate to be enforced for the HC 64-bit counters.
.1.3.6.1.4.1.12325.1.200,BEGEMOT-PF-MIB::begemotPf,,,,,,The Begemot MIB for the pf packet filter.
.1.3.6.1.4.1.12325.1.200.1,BEGEMOT-PF-MIB::begemotPfObjects,,,,,,
.1.3.6.1.4.1.12325.1.200.1.1,BEGEMOT-PF-MIB::pfStatus,,,,,,
.1.3.6.1.4.1.12325.1.200.1.1.1,BEGEMOT-PF-MIB::pfStatusRunning,INTEGER,read-only,,current,true(1):false(2),True if pf is currently enabled.
.1.3.6.1.4.1.12325.1.200.1.1.2,BEGEMOT-PF-MIB::pfStatusRuntime,TimeTicks,read-only,,current,,Indicates how long pf has been enabled. If pf is not currently
.1.3.6.1.4.1.12325.1.200.1.1.3,BEGEMOT-PF-MIB::pfStatusDebug,INTEGER,read-only,,current,none(0):urgent(1):misc(2):loud(3),Indicates the debug level at which pf is running.
.1.3.6.1.4.1.12325.1.200.1.1.4,BEGEMOT-PF-MIB::pfStatusHostId,OCTET,read-only,,current,,The (unique) host identifier of the machine running pf.
.1.3.6.1.4.1.12325.1.200.1.2,BEGEMOT-PF-MIB::pfCounter,,,,,,
.1.3.6.1.4.1.12325.1.200.1.2.1,BEGEMOT-PF-MIB::pfCounterMatch,Counter64,read-only,,current,,Number of packets that matched a filter rule.
.1.3.6.1.4.1.12325.1.200.1.2.2,BEGEMOT-PF-MIB::pfCounterBadOffset,Counter64,read-only,,current,,Number of packets with bad offset.
.1.3.6.1.4.1.12325.1.200.1.2.3,BEGEMOT-PF-MIB::pfCounterFragment,Counter64,read-only,,current,,Number of fragmented packets.
.1.3.6.1.4.1.12325.1.200.1.2.4,BEGEMOT-PF-MIB::pfCounterShort,Counter64,read-only,,current,,Number of short packets.
.1.3.6.1.4.1.12325.1.200.1.2.5,BEGEMOT-PF-MIB::pfCounterNormalize,Counter64,read-only,,current,,Number of normalized packets.
.1.3.6.1.4.1.12325.1.200.1.2.6,BEGEMOT-PF-MIB::pfCounterMemDrop,Counter64,read-only,,current,,Number of packets dropped due to memory limitations.
.1.3.6.1.4.1.12325.1.200.1.3,BEGEMOT-PF-MIB::pfStateTable,,,,,,
.1.3.6.1.4.1.12325.1.200.1.3.1,BEGEMOT-PF-MIB::pfStateTableCount,Unsigned32,read-only,,current,,Number of entries in the state table.
.1.3.6.1.4.1.12325.1.200.1.3.2,BEGEMOT-PF-MIB::pfStateTableSearches,Counter64,read-only,,current,,Number of searches against the state table.
.1.3.6.1.4.1.12325.1.200.1.3.3,BEGEMOT-PF-MIB::pfStateTableInserts,Counter64,read-only,,current,,Number of entries inserted into the state table.
.1.3.6.1.4.1.12325.1.200.1.3.4,BEGEMOT-PF-MIB::pfStateTableRemovals,Counter64,read-only,,current,,Number of entries removed from the state table.
.1.3.6.1.4.1.12325.1.200.1.4,BEGEMOT-PF-MIB::pfSrcNodes,,,,,,
.1.3.6.1.4.1.12325.1.200.1.4.1,BEGEMOT-PF-MIB::pfSrcNodesCount,Unsigned32,read-only,,current,,Number of entries in the source tracking table.
.1.3.6.1.4.1.12325.1.200.1.4.2,BEGEMOT-PF-MIB::pfSrcNodesSearches,Counter64,read-only,,current,,Number of searches against the source tracking table.
.1.3.6.1.4.1.12325.1.200.1.4.3,BEGEMOT-PF-MIB::pfSrcNodesInserts,Counter64,read-only,,current,,Number of entries inserted into the source tracking table.
.1.3.6.1.4.1.12325.1.200.1.4.4,BEGEMOT-PF-MIB::pfSrcNodesRemovals,Counter64,read-only,,current,,Number of entries removed from the source tracking table.
.1.3.6.1.4.1.12325.1.200.1.5,BEGEMOT-PF-MIB::pfLimits,,,,,,
.1.3.6.1.4.1.12325.1.200.1.5.1,BEGEMOT-PF-MIB::pfLimitsStates,Unsigned32,read-only,,current,,Maximum number of 'keep state' rules in the ruleset.
.1.3.6.1.4.1.12325.1.200.1.5.2,BEGEMOT-PF-MIB::pfLimitsSrcNodes,Unsigned32,read-only,,current,,Maximum number of 'sticky-address' or 'source-track' rules
.1.3.6.1.4.1.12325.1.200.1.5.3,BEGEMOT-PF-MIB::pfLimitsFrags,Unsigned32,read-only,,current,,Maximum number of 'scrub' rules in the ruleset.
.1.3.6.1.4.1.12325.1.200.1.6,BEGEMOT-PF-MIB::pfTimeouts,,,,,,
.1.3.6.1.4.1.12325.1.200.1.6.1,BEGEMOT-PF-MIB::pfTimeoutsTcpFirst,Integer32,read-only,,current,,State after the first packet in a connection.
.1.3.6.1.4.1.12325.1.200.1.6.2,BEGEMOT-PF-MIB::pfTimeoutsTcpOpening,Integer32,read-only,,current,,State before the destination host ever sends a packet.
.1.3.6.1.4.1.12325.1.200.1.6.3,BEGEMOT-PF-MIB::pfTimeoutsTcpEstablished,Integer32,read-only,,current,,The fully established state.
.1.3.6.1.4.1.12325.1.200.1.6.4,BEGEMOT-PF-MIB::pfTimeoutsTcpClosing,Integer32,read-only,,current,,State after the first FIN has been sent.
.1.3.6.1.4.1.12325.1.200.1.6.5,BEGEMOT-PF-MIB::pfTimeoutsTcpFinWait,Integer32,read-only,,current,,State after both FINs have been exchanged and the
.1.3.6.1.4.1.12325.1.200.1.6.6,BEGEMOT-PF-MIB::pfTimeoutsTcpClosed,Integer32,read-only,,current,,State after one endpoint sends an RST.
.1.3.6.1.4.1.12325.1.200.1.6.7,BEGEMOT-PF-MIB::pfTimeoutsUdpFirst,Integer32,read-only,,current,,State after the first packet.
.1.3.6.1.4.1.12325.1.200.1.6.8,BEGEMOT-PF-MIB::pfTimeoutsUdpSingle,Integer32,read-only,,current,,State if the source host sends more than one packet but
.1.3.6.1.4.1.12325.1.200.1.6.9,BEGEMOT-PF-MIB::pfTimeoutsUdpMultiple,Integer32,read-only,,current,,State if both hosts have sent packets.
.1.3.6.1.4.1.12325.1.200.1.6.10,BEGEMOT-PF-MIB::pfTimeoutsIcmpFirst,Integer32,read-only,,current,,State after the first packet.
.1.3.6.1.4.1.12325.1.200.1.6.11,BEGEMOT-PF-MIB::pfTimeoutsIcmpError,Integer32,read-only,,current,,State after an ICMP error came back in response to an
.1.3.6.1.4.1.12325.1.200.1.6.12,BEGEMOT-PF-MIB::pfTimeoutsOtherFirst,Integer32,read-only,,current,,State after the first packet.
.1.3.6.1.4.1.12325.1.200.1.6.13,BEGEMOT-PF-MIB::pfTimeoutsOtherSingle,Integer32,read-only,,current,,State if the source host sends more than one packet but
.1.3.6.1.4.1.12325.1.200.1.6.14,BEGEMOT-PF-MIB::pfTimeoutsOtherMultiple,Integer32,read-only,,current,,State if both hosts have sent packets.
.1.3.6.1.4.1.12325.1.200.1.6.15,BEGEMOT-PF-MIB::pfTimeoutsFragment,Integer32,read-only,,current,,Seconds before an unassembled fragment is expired.
.1.3.6.1.4.1.12325.1.200.1.6.16,BEGEMOT-PF-MIB::pfTimeoutsInterval,Integer32,read-only,,current,,Interval between purging expired states and fragments.
.1.3.6.1.4.1.12325.1.200.1.6.17,BEGEMOT-PF-MIB::pfTimeoutsAdaptiveStart,Integer32,read-only,,current,,When the number of state entries exceeds this value,
.1.3.6.1.4.1.12325.1.200.1.6.18,BEGEMOT-PF-MIB::pfTimeoutsAdaptiveEnd,Integer32,read-only,,current,,When reaching this number of state entries, all timeout
.1.3.6.1.4.1.12325.1.200.1.6.19,BEGEMOT-PF-MIB::pfTimeoutsSrcNode,Integer32,read-only,,current,,Length of time to retain a source tracking entry after
.1.3.6.1.4.1.12325.1.200.1.7,BEGEMOT-PF-MIB::pfLogInterface,,,,,,
.1.3.6.1.4.1.12325.1.200.1.7.1,BEGEMOT-PF-MIB::pfLogInterfaceName,OCTET,read-only,,current,,The name of the interface configured with 'set loginterface'.
.1.3.6.1.4.1.12325.1.200.1.7.2,BEGEMOT-PF-MIB::pfLogInterfaceIp4BytesIn,Counter64,read-only,,current,,Number of IPv4 bytes passed in on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.3,BEGEMOT-PF-MIB::pfLogInterfaceIp4BytesOut,Counter64,read-only,,current,,Number of IPv4 bytes passed out on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.4,BEGEMOT-PF-MIB::pfLogInterfaceIp4PktsInPass,Counter64,read-only,,current,,Number of IPv4 packets passed in on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.5,BEGEMOT-PF-MIB::pfLogInterfaceIp4PktsInDrop,Counter64,read-only,,current,,Number of IPv4 packets dropped coming in on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.6,BEGEMOT-PF-MIB::pfLogInterfaceIp4PktsOutPass,Counter64,read-only,,current,,Number of IPv4 packets passed out on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.7,BEGEMOT-PF-MIB::pfLogInterfaceIp4PktsOutDrop,Counter64,read-only,,current,,Number of IPv4 packets dropped going out on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.8,BEGEMOT-PF-MIB::pfLogInterfaceIp6BytesIn,Counter64,read-only,,current,,Number of IPv6 bytes passed in on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.9,BEGEMOT-PF-MIB::pfLogInterfaceIp6BytesOut,Counter64,read-only,,current,,Number of IPv6 bytes passed out on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.10,BEGEMOT-PF-MIB::pfLogInterfaceIp6PktsInPass,Counter64,read-only,,current,,Number of IPv6 packets passed in on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.11,BEGEMOT-PF-MIB::pfLogInterfaceIp6PktsInDrop,Counter64,read-only,,current,,Number of IPv6 packets dropped coming in on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.12,BEGEMOT-PF-MIB::pfLogInterfaceIp6PktsOutPass,Counter64,read-only,,current,,Number of IPv6 packets passed out on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.7.13,BEGEMOT-PF-MIB::pfLogInterfaceIp6PktsOutDrop,Counter64,read-only,,current,,Number of IPv6 packets dropped going out on the loginterface.
.1.3.6.1.4.1.12325.1.200.1.8,BEGEMOT-PF-MIB::pfInterfaces,,,,,,
.1.3.6.1.4.1.12325.1.200.1.8.1,BEGEMOT-PF-MIB::pfInterfacesIfNumber,Integer32,read-only,,current,,The number of network interfaces on this system.
.1.3.6.1.4.1.12325.1.200.1.8.2,BEGEMOT-PF-MIB::pfInterfacesIfTable,,not-accessible,,current,,Table of network interfaces, indexed on pfInterfacesIfNumber.
.1.3.6.1.4.1.12325.1.200.1.8.2.1,BEGEMOT-PF-MIB::pfInterfacesIfEntry,,not-accessible,pfInterfacesIfIndex,current,,An entry in the pfInterfacesIfTable containing information
.1.3.6.1.4.1.12325.1.200.1.8.2.1.1,BEGEMOT-PF-MIB::pfInterfacesIfIndex,Integer32,not-accessible,,current,,A unique value, greater than zero, for each interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.2,BEGEMOT-PF-MIB::pfInterfacesIfDescr,OCTET,read-only,,current,,The name of the interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.3,BEGEMOT-PF-MIB::pfInterfacesIfType,INTEGER,read-only,,current,group(0):instance(1):detached(2),Indicates whether the interface is a group inteface, an
.1.3.6.1.4.1.12325.1.200.1.8.2.1.4,BEGEMOT-PF-MIB::pfInterfacesIfTZero,TimeTicks,read-only,,current,,Time since statistics were last reset or since the
.1.3.6.1.4.1.12325.1.200.1.8.2.1.5,BEGEMOT-PF-MIB::pfInterfacesIfRefsState,Unsigned32,read-only,,current,,The number of state and/or source track entries referencing
.1.3.6.1.4.1.12325.1.200.1.8.2.1.6,BEGEMOT-PF-MIB::pfInterfacesIfRefsRule,Unsigned32,read-only,,current,,The number of rules referencing this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.7,BEGEMOT-PF-MIB::pfInterfacesIf4BytesInPass,Counter64,read-only,,current,,The number of IPv4 bytes passed coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.8,BEGEMOT-PF-MIB::pfInterfacesIf4BytesInBlock,Counter64,read-only,,current,,The number of IPv4 bytes blocked coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.9,BEGEMOT-PF-MIB::pfInterfacesIf4BytesOutPass,Counter64,read-only,,current,,The number of IPv4 bytes passed going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.10,BEGEMOT-PF-MIB::pfInterfacesIf4BytesOutBlock,Counter64,read-only,,current,,The number of IPv4 bytes blocked going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.11,BEGEMOT-PF-MIB::pfInterfacesIf4PktsInPass,Counter64,read-only,,current,,The number of IPv4 packets passed coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.12,BEGEMOT-PF-MIB::pfInterfacesIf4PktsInBlock,Counter64,read-only,,current,,The number of IPv4 packets blocked coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.13,BEGEMOT-PF-MIB::pfInterfacesIf4PktsOutPass,Counter64,read-only,,current,,The number of IPv4 packets passed going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.14,BEGEMOT-PF-MIB::pfInterfacesIf4PktsOutBlock,Counter64,read-only,,current,,The number of IPv4 packets blocked going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.15,BEGEMOT-PF-MIB::pfInterfacesIf6BytesInPass,Counter64,read-only,,current,,The number of IPv6 bytes passed coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.16,BEGEMOT-PF-MIB::pfInterfacesIf6BytesInBlock,Counter64,read-only,,current,,The number of IPv6 bytes blocked coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.17,BEGEMOT-PF-MIB::pfInterfacesIf6BytesOutPass,Counter64,read-only,,current,,The number of IPv6 bytes passed going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.18,BEGEMOT-PF-MIB::pfInterfacesIf6BytesOutBlock,Counter64,read-only,,current,,The number of IPv6 bytes blocked going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.19,BEGEMOT-PF-MIB::pfInterfacesIf6PktsInPass,Counter64,read-only,,current,,The number of IPv6 packets passed coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.20,BEGEMOT-PF-MIB::pfInterfacesIf6PktsInBlock,Counter64,read-only,,current,,The number of IPv6 packets blocked coming in on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.21,BEGEMOT-PF-MIB::pfInterfacesIf6PktsOutPass,Counter64,read-only,,current,,The number of IPv6 packets passed going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.8.2.1.22,BEGEMOT-PF-MIB::pfInterfacesIf6PktsOutBlock,Counter64,read-only,,current,,The number of IPv6 packets blocked going out on this interface.
.1.3.6.1.4.1.12325.1.200.1.9,BEGEMOT-PF-MIB::pfTables,,,,,,
.1.3.6.1.4.1.12325.1.200.1.9.1,BEGEMOT-PF-MIB::pfTablesTblNumber,Integer32,read-only,,current,,The number of tables on this system.
.1.3.6.1.4.1.12325.1.200.1.9.2,BEGEMOT-PF-MIB::pfTablesTblTable,,not-accessible,,current,,Table of tables, index on pfTablesTblIndex.
.1.3.6.1.4.1.12325.1.200.1.9.2.1,BEGEMOT-PF-MIB::pfTablesTblEntry,,not-accessible,pfTablesTblIndex,current,,Any entry in the pfTablesTblTable containing information
.1.3.6.1.4.1.12325.1.200.1.9.2.1.1,BEGEMOT-PF-MIB::pfTablesTblIndex,Integer32,not-accessible,,current,,A unique value, greater than zero, for each table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.2,BEGEMOT-PF-MIB::pfTablesTblDescr,OCTET,read-only,,current,,The name of the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.3,BEGEMOT-PF-MIB::pfTablesTblCount,Integer32,read-only,,current,,The number of addresses in the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.4,BEGEMOT-PF-MIB::pfTablesTblTZero,TimeTicks,read-only,,current,,The time passed since the statistics of this table were last cleared or the time since this table was loaded, whichever is sooner.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.5,BEGEMOT-PF-MIB::pfTablesTblRefsAnchor,Integer32,read-only,,current,,The number of anchors referencing this table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.6,BEGEMOT-PF-MIB::pfTablesTblRefsRule,Integer32,read-only,,current,,The number of rules referencing this table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.7,BEGEMOT-PF-MIB::pfTablesTblEvalMatch,Counter64,read-only,,current,,The number of evaluations returning a match.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.8,BEGEMOT-PF-MIB::pfTablesTblEvalNoMatch,Counter64,read-only,,current,,The number of evaluations not returning a match.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.9,BEGEMOT-PF-MIB::pfTablesTblBytesInPass,Counter64,read-only,,current,,The number of bytes passed in matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.10,BEGEMOT-PF-MIB::pfTablesTblBytesInBlock,Counter64,read-only,,current,,The number of bytes blocked coming in matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.11,BEGEMOT-PF-MIB::pfTablesTblBytesInXPass,Counter64,read-only,,current,,The number of bytes statefully passed in where the state entry refers to the table, but the table no longer contains
.1.3.6.1.4.1.12325.1.200.1.9.2.1.12,BEGEMOT-PF-MIB::pfTablesTblBytesOutPass,Counter64,read-only,,current,,The number of bytes passed out matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.13,BEGEMOT-PF-MIB::pfTablesTblBytesOutBlock,Counter64,read-only,,current,,The number of bytes blocked going out matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.14,BEGEMOT-PF-MIB::pfTablesTblBytesOutXPass,Counter64,read-only,,current,,The number of bytes statefully passed out where the state entry refers to the table, but the table no longer contains
.1.3.6.1.4.1.12325.1.200.1.9.2.1.15,BEGEMOT-PF-MIB::pfTablesTblPktsInPass,Counter64,read-only,,current,,The number of packets passed in matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.16,BEGEMOT-PF-MIB::pfTablesTblPktsInBlock,Counter64,read-only,,current,,The number of packets blocked coming in matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.17,BEGEMOT-PF-MIB::pfTablesTblPktsInXPass,Counter64,read-only,,current,,The number of packets statefully passed in where the state entry refers to the table, but the table no longer contains
.1.3.6.1.4.1.12325.1.200.1.9.2.1.18,BEGEMOT-PF-MIB::pfTablesTblPktsOutPass,Counter64,read-only,,current,,The number of packets passed out matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.19,BEGEMOT-PF-MIB::pfTablesTblPktsOutBlock,Counter64,read-only,,current,,The number of packets blocked going out matching the table.
.1.3.6.1.4.1.12325.1.200.1.9.2.1.20,BEGEMOT-PF-MIB::pfTablesTblPktsOutXPass,Counter64,read-only,,current,,The number of packets statefully passed out where the state entry refers to the table, but the table no longer contains
.1.3.6.1.4.1.12325.1.200.1.9.3,BEGEMOT-PF-MIB::pfTablesAddrTable,,not-accessible,,current,,Table of addresses from every table on the system.
.1.3.6.1.4.1.12325.1.200.1.9.3.1,BEGEMOT-PF-MIB::pfTablesAddrEntry,,not-accessible,pfTablesAddrIndex,current,,An entry in the pfTablesAddrTable containing information about a particular entry in a table.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.1,BEGEMOT-PF-MIB::pfTablesAddrIndex,Integer32,not-accessible,,current,,A unique value, greater than zero, for each address.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.2,BEGEMOT-PF-MIB::pfTablesAddrNet,IpAddress,read-only,,current,,The IP address of this particular table entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.3,BEGEMOT-PF-MIB::pfTablesAddrMask,Integer32,read-only,,current,,The CIDR netmask of this particular table entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.4,BEGEMOT-PF-MIB::pfTablesAddrTZero,TimeTicks,read-only,,current,,The time passed since this entry's statistics were last
.1.3.6.1.4.1.12325.1.200.1.9.3.1.5,BEGEMOT-PF-MIB::pfTablesAddrBytesInPass,Counter64,read-only,,current,,The number of inbound bytes passed as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.6,BEGEMOT-PF-MIB::pfTablesAddrBytesInBlock,Counter64,read-only,,current,,The number of inbound bytes blocked as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.7,BEGEMOT-PF-MIB::pfTablesAddrBytesOutPass,Counter64,read-only,,current,,The number of outbound bytes passed as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.8,BEGEMOT-PF-MIB::pfTablesAddrBytesOutBlock,Counter64,read-only,,current,,The number of outbound bytes blocked as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.9,BEGEMOT-PF-MIB::pfTablesAddrPktsInPass,Counter64,read-only,,current,,The number of inbound packets passed as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.10,BEGEMOT-PF-MIB::pfTablesAddrPktsInBlock,Counter64,read-only,,current,,The number of inbound packets blocked as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.11,BEGEMOT-PF-MIB::pfTablesAddrPktsOutPass,Counter64,read-only,,current,,The number of outbound packets passed as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.9.3.1.12,BEGEMOT-PF-MIB::pfTablesAddrPktsOutBlock,Counter64,read-only,,current,,The number of outbound packets blocked as a result of this entry.
.1.3.6.1.4.1.12325.1.200.1.10,BEGEMOT-PF-MIB::pfAltq,,,,,,
.1.3.6.1.4.1.12325.1.200.1.10.1,BEGEMOT-PF-MIB::pfAltqQueueNumber,Unsigned32,read-only,,current,,The number of queues in the active set.
.1.3.6.1.4.1.12325.1.200.1.10.2,BEGEMOT-PF-MIB::pfAltqQueueTable,,not-accessible,,current,,Table containing the rules that are active on this system.
.1.3.6.1.4.1.12325.1.200.1.10.2.1,BEGEMOT-PF-MIB::pfAltqQueueEntry,,not-accessible,pfAltqQueueIndex,current,,An entry in the pfAltqQueueTable table.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.1,BEGEMOT-PF-MIB::pfAltqQueueIndex,Integer32,not-accessible,,current,,A unique value, greater than zero, for each queue.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.2,BEGEMOT-PF-MIB::pfAltqQueueDescr,OCTET,read-only,,current,,The name of the queue.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.3,BEGEMOT-PF-MIB::pfAltqQueueParent,OCTET,read-only,,current,,Name of the queue's parent if it has one.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.4,BEGEMOT-PF-MIB::pfAltqQueueScheduler,INTEGER,read-only,,current,cbq(1):hfsc(8):priq(11),Scheduler algorithm implemented by this queue.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.5,BEGEMOT-PF-MIB::pfAltqQueueBandwidth,Unsigned32,read-only,,current,,Bandwitch assigned to this queue.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.6,BEGEMOT-PF-MIB::pfAltqQueuePriority,Integer32,read-only,,current,,Priority level of the queue.
.1.3.6.1.4.1.12325.1.200.1.10.2.1.7,BEGEMOT-PF-MIB::pfAltqQueueLimit,Integer32,read-only,,current,,Maximum number of packets in the queue.
.1.3.6.1.4.1.12325.1.202,BEGEMOT-HOSTRES-MIB::begemotHostres,,,,,,The MIB for additional HOST-RESOURCES data.
.1.3.6.1.4.1.12325.1.202.1,BEGEMOT-HOSTRES-MIB::begemotHostresObjects,,,,,,
.1.3.6.1.4.1.12325.1.202.1.1,BEGEMOT-HOSTRES-MIB::begemotHrStorageUpdate,TimeTicks,read-write,,current,,The maximum number of ticks the storage table is cached.
.1.3.6.1.4.1.12325.1.202.1.2,BEGEMOT-HOSTRES-MIB::begemotHrFSUpdate,TimeTicks,read-write,,current,,The maximum number of ticks the FS table is cached.
.1.3.6.1.4.1.12325.1.202.1.3,BEGEMOT-HOSTRES-MIB::begemotHrDiskStorageUpdate,TimeTicks,read-write,,current,,The maximum number of ticks the disk storage table is cached.
.1.3.6.1.4.1.12325.1.202.1.4,BEGEMOT-HOSTRES-MIB::begemotHrNetworkUpdate,TimeTicks,read-write,,current,,The maximum number of ticks the network table is cached.
.1.3.6.1.4.1.12325.1.202.1.5,BEGEMOT-HOSTRES-MIB::begemotHrSWInstalledUpdate,TimeTicks,read-write,,current,,The maximum number of ticks the hrSWInstalledTable is cached.
.1.3.6.1.4.1.12325.1.202.1.6,BEGEMOT-HOSTRES-MIB::begemotHrSWRunUpdate,TimeTicks,read-write,,current,,The maximum number of ticks the hrSWRunTable and
.1.3.6.1.4.1.12325.1.202.1.7,BEGEMOT-HOSTRES-MIB::begemotHrPkgDir,OCTET,read-write,,current,,The path to the package DB directory.
.1.3.6.1.4.1.12325.1.205,BEGEMOT-BRIDGE-MIB::begemotBridge,,,,,,The Begemot MIB for managing bridge interfaces.
.1.3.6.1.4.1.12325.1.205.0,BEGEMOT-BRIDGE-MIB::begemotBridgeNotifications,,,,,,
.1.3.6.1.4.1.12325.1.205.0.1,BEGEMOT-BRIDGE-MIB::begemotBridgeNewRoot,,,,,,The begemotBridgeNewRoot trap indicates that one of the
.1.3.6.1.4.1.12325.1.205.0.2,BEGEMOT-BRIDGE-MIB::begemotBridgeTopologyChange,,,,,,A begemotBridgeTopologyChange trap is send when a member
.1.3.6.1.4.1.12325.1.205.1,BEGEMOT-BRIDGE-MIB::begemotBridgeBase,,,,,,
.1.3.6.1.4.1.12325.1.205.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseTable,,not-accessible,,current,,A table that contains generic information for each
.1.3.6.1.4.1.12325.1.205.1.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseEntry,,not-accessible,begemotBridgeBaseName,current,,A list of information for the bridge interfaces on
.1.3.6.1.4.1.12325.1.205.1.1.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName,OCTET,read-only,,current,,The name of the bridge interface for which this
.1.3.6.1.4.1.12325.1.205.1.1.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress,OCTET,read-only,,current,,The MAC address of the bridge interface.
.1.3.6.1.4.1.12325.1.205.1.1.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts,Integer32,read-only,,current,,The number of ports, members of this bridge.
.1.3.6.1.4.1.12325.1.205.1.1.1.4,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseType,INTEGER,read-only,,current,unknown(1):transparent-only(2):sourceroute-only(3):srt(4),Indicates what type of bridging this bridge can
.1.3.6.1.4.1.12325.1.205.1.1.1.5,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to create/destroy bridge interfaces on the
.1.3.6.1.4.1.12325.1.205.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortTable,,not-accessible,,current,,A table containing generic information about ports,
.1.3.6.1.4.1.12325.1.205.1.2.1,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortEntry,,not-accessible,begemotBridgeBaseName:begemotBridgeBasePortIfIndex,current,,A list of information about a specific port, member of
.1.3.6.1.4.1.12325.1.205.1.2.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePort,Integer32,read-only,,current,,The system interface index of the interface corresponding
.1.3.6.1.4.1.12325.1.205.1.2.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortIfIndex,Integer32,read-only,,current,,The value of the instance of the ifIndex object,
.1.3.6.1.4.1.12325.1.205.1.2.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeBaseSpanEnabled,INTEGER,read-write,,current,enabled(1):disabled(2),The value of this objects reflects whether the port
.1.3.6.1.4.1.12325.1.205.1.2.1.4,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortDelayExceededDiscards,Counter32,read-only,,current,,The number of frames discarded by this port due
.1.3.6.1.4.1.12325.1.205.1.2.1.5,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortMtuExceededDiscards,Counter32,read-only,,current,,The number of frames discarded by this port due
.1.3.6.1.4.1.12325.1.205.1.2.1.6,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Used to control addition of member ports to or
.1.3.6.1.4.1.12325.1.205.1.2.1.7,BEGEMOT-BRIDGE-MIB::begemotBridgeBasePortPrivate,INTEGER,read-write,,current,true(1):false(2),The value of this objects reflects whether the port
.1.3.6.1.4.1.12325.1.205.2,BEGEMOT-BRIDGE-MIB::begemotBridgeStp,,,,,,
.1.3.6.1.4.1.12325.1.205.2.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpTable,,not-accessible,,current,,A table that contains Spanning Tree Protocol information
.1.3.6.1.4.1.12325.1.205.2.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpEntry,,not-accessible,,current,,A list of information about the Spanning Tree Protocol
.1.3.6.1.4.1.12325.1.205.2.1.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpProtocolSpecification,INTEGER,read-only,,current,unknown(1):decLb100(2):ieee8021d(3),The Spanning Tree Protocol version being run on the
.1.3.6.1.4.1.12325.1.205.2.1.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPriority,Integer32,read-write,,current,,The priority value of the bridge interface forming the
.1.3.6.1.4.1.12325.1.205.2.1.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange,TimeTicks,read-only,,current,,The time (in hundreds of a second) since a topology change
.1.3.6.1.4.1.12325.1.205.2.1.1.4,BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges,Counter32,read-only,,current,,The number of times a topology change was detected by the
.1.3.6.1.4.1.12325.1.205.2.1.1.5,BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot,OCTET,read-only,,current,,The bridge identifier of the root of the spanning tree as
.1.3.6.1.4.1.12325.1.205.2.1.1.6,BEGEMOT-BRIDGE-MIB::begemotBridgeStpRootCost,Integer32,read-only,,current,,The cost of the path from this bridge to the root bridge.
.1.3.6.1.4.1.12325.1.205.2.1.1.7,BEGEMOT-BRIDGE-MIB::begemotBridgeStpRootPort,Integer32,read-only,,current,,The port number of the port that offers the lowest
.1.3.6.1.4.1.12325.1.205.2.1.1.8,BEGEMOT-BRIDGE-MIB::begemotBridgeStpMaxAge,Integer32,read-only,,current,,The maximum age of Spanning Tree Protocol information
.1.3.6.1.4.1.12325.1.205.2.1.1.9,BEGEMOT-BRIDGE-MIB::begemotBridgeStpHelloTime,Integer32,read-only,,current,,The amount of time between transmission of
.1.3.6.1.4.1.12325.1.205.2.1.1.10,BEGEMOT-BRIDGE-MIB::begemotBridgeStpHoldTime,Integer32,read-only,,current,,This time value determines the interval length
.1.3.6.1.4.1.12325.1.205.2.1.1.11,BEGEMOT-BRIDGE-MIB::begemotBridgeStpForwardDelay,Integer32,read-only,,current,,This value, measured in units of hundredths of a second
.1.3.6.1.4.1.12325.1.205.2.1.1.12,BEGEMOT-BRIDGE-MIB::begemotBridgeStpBridgeMaxAge,Integer32,read-write,,current,,The value that all bridges participating in the
.1.3.6.1.4.1.12325.1.205.2.1.1.13,BEGEMOT-BRIDGE-MIB::begemotBridgeStpBridgeHelloTime,Integer32,read-write,,current,,The value that all bridges participating in the
.1.3.6.1.4.1.12325.1.205.2.1.1.14,BEGEMOT-BRIDGE-MIB::begemotBridgeStpBridgeForwardDelay,Integer32,read-write,,current,,The value that all bridges participating in the
.1.3.6.1.4.1.12325.1.205.2.1.1.15,BEGEMOT-BRIDGE-MIB::begemotBridgeStpVersion,INTEGER,read-write,,current,stpCompatible(0):rstp(2),The version of Spanning Tree Protocol the bridge is
.1.3.6.1.4.1.12325.1.205.2.1.1.16,BEGEMOT-BRIDGE-MIB::begemotBridgeStpTxHoldCount,Integer32,read-write,,current,,The value used by the Port Transmit state machine to limit
.1.3.6.1.4.1.12325.1.205.2.2,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortTable,,not-accessible,,current,,A table containing Spanning Tree Protocol information
.1.3.6.1.4.1.12325.1.205.2.2.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortEntry,,not-accessible,begemotBridgeBaseName:begemotBridgeBasePortIfIndex,current,,A list of Spanning Tree Protocol information about
.1.3.6.1.4.1.12325.1.205.2.2.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPort,Integer32,read-only,,current,,The system interface index of the interface corresponding
.1.3.6.1.4.1.12325.1.205.2.2.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortPriority,Integer32,read-write,,current,,The STP priority of this port that is contained in the first
.1.3.6.1.4.1.12325.1.205.2.2.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortState,INTEGER,read-only,,current,disabled(1):blocking(2):listening(3):learning(4):forwarding(5):broken(6),The current state of the port as defined by the operation
.1.3.6.1.4.1.12325.1.205.2.2.1.4,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortEnable,INTEGER,read-write,,current,enabled(1):disabled(2),The administrative Spanning Tree Protocol state of the
.1.3.6.1.4.1.12325.1.205.2.2.1.5,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortPathCost,Integer32,read-write,,current,,The contribution of the path through this port, when the port
.1.3.6.1.4.1.12325.1.205.2.2.1.6,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortDesignatedRoot,OCTET,read-only,,current,,The unique Bridge Identifier of the bridge recorded as the
.1.3.6.1.4.1.12325.1.205.2.2.1.7,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortDesignatedCost,Integer32,read-only,,current,,For a Designated port, the path cost (equal to the Root
.1.3.6.1.4.1.12325.1.205.2.2.1.8,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortDesignatedBridge,OCTET,read-only,,current,,The unique Bridge Identifier of the bridge to which the
.1.3.6.1.4.1.12325.1.205.2.2.1.9,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortDesignatedPort,OCTET,read-only,,current,,The Port Identifier of the Bridge port, on the Designated
.1.3.6.1.4.1.12325.1.205.2.2.1.10,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortForwardTransitions,Counter32,read-only,,current,,The number of times this port has transitioned
.1.3.6.1.4.1.12325.1.205.2.3,BEGEMOT-BRIDGE-MIB::begemotBridgeStpExtPortTable,,not-accessible,,current,,A table that contains port-specific Rapid Spanning Tree
.1.3.6.1.4.1.12325.1.205.2.3.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpExtPortEntry,,not-accessible,,current,,A list of Rapid Spanning Tree information maintained by
.1.3.6.1.4.1.12325.1.205.2.3.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortProtocolMigration,INTEGER,read-write,,current,true(1):false(2),When operating in RSTP (version 2) mode, writing true(1)
.1.3.6.1.4.1.12325.1.205.2.3.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortAdminEdgePort,INTEGER,read-write,,current,true(1):false(2),The administrative value of the Edge Port parameter. A
.1.3.6.1.4.1.12325.1.205.2.3.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortOperEdgePort,INTEGER,read-only,,current,true(1):false(2),The operational value of the Edge Port parameter. The
.1.3.6.1.4.1.12325.1.205.2.3.1.4,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortAdminPointToPoint,INTEGER,read-write,,current,forceTrue(0):forceFalse(1):auto(2),The administrative point-to-point status of the LAN segment
.1.3.6.1.4.1.12325.1.205.2.3.1.5,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortOperPointToPoint,INTEGER,read-only,,current,true(1):false(2),The operational point-to-point status of the LAN segment
.1.3.6.1.4.1.12325.1.205.2.3.1.6,BEGEMOT-BRIDGE-MIB::begemotBridgeStpPortAdminPathCost,Integer32,read-write,,current,,The administratively assigned value for the contribution
.1.3.6.1.4.1.12325.1.205.3,BEGEMOT-BRIDGE-MIB::begemotBridgeTp,,,,,,
.1.3.6.1.4.1.12325.1.205.3.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpTable,,not-accessible,,current,,A table that contains information regarding transparent
.1.3.6.1.4.1.12325.1.205.3.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpEntry,,not-accessible,,current,,A list of information regarding transparent bridging
.1.3.6.1.4.1.12325.1.205.3.1.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpLearnedEntryDiscards,Counter32,read-only,,current,,The total number of Forwarding Database entries that would
.1.3.6.1.4.1.12325.1.205.3.1.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeTpAgingTime,Integer32,read-write,,current,,The timeout period in seconds before aging out dynamically learnt forwarding entries.
.1.3.6.1.4.1.12325.1.205.3.1.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeTpMaxAddresses,Integer32,read-write,,current,,The maximum number of entires that this bridge can
.1.3.6.1.4.1.12325.1.205.3.2,BEGEMOT-BRIDGE-MIB::begemotBridgeTpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries
.1.3.6.1.4.1.12325.1.205.3.2.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpFdbEntry,,not-accessible,begemotBridgeBaseName:begemotBridgeTpFdbAddress,current,,Information about a specific unicast MAC address
.1.3.6.1.4.1.12325.1.205.3.2.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpFdbAddress,OCTET,read-only,,current,,A unicast MAC address for which the bridge has which the
.1.3.6.1.4.1.12325.1.205.3.2.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeTpFdbPort,Integer32,read-only,,current,,The port number of the bridge port on which a frame having
.1.3.6.1.4.1.12325.1.205.3.2.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeTpFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5),The status of this entry. The meanings of the
.1.3.6.1.4.1.12325.1.205.3.3,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPortTable,,not-accessible,,current,,A table that contains information about every bridge port,
.1.3.6.1.4.1.12325.1.205.3.3.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPortEntry,,not-accessible,begemotBridgeBaseName:begemotBridgeBasePortIfIndex,current,,A list of information about every bridge port, member of a
.1.3.6.1.4.1.12325.1.205.3.3.1.1,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPort,Integer32,read-only,,current,,The system interface index of the port for which this entry
.1.3.6.1.4.1.12325.1.205.3.3.1.2,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPortMaxInfo,Integer32,read-only,,current,,The maximum size of the INFO (non-MAC) field that this port
.1.3.6.1.4.1.12325.1.205.3.3.1.3,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPortInFrames,Counter32,read-only,,current,,The number of frames that have been received by this
.1.3.6.1.4.1.12325.1.205.3.3.1.4,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPortOutFrames,Counter32,read-only,,current,,The number of frames that have been transmitted by this
.1.3.6.1.4.1.12325.1.205.3.3.1.5,BEGEMOT-BRIDGE-MIB::begemotBridgeTpPortInDiscards,Counter32,read-only,,current,,Count of received valid frames that were discarded
.1.3.6.1.4.1.12325.1.205.4,BEGEMOT-BRIDGE-MIB::begemotBridgePf,,,,,,
.1.3.6.1.4.1.12325.1.205.4.1,BEGEMOT-BRIDGE-MIB::begemotBridgePfilStatus,INTEGER,read-write,,current,true(1):false(2),Indicates whether packet filtering by some firewall
.1.3.6.1.4.1.12325.1.205.4.2,BEGEMOT-BRIDGE-MIB::begemotBridgePfilMembers,INTEGER,read-write,,current,true(1):false(2),A value of true(1) indicates that packet filtering is
.1.3.6.1.4.1.12325.1.205.4.3,BEGEMOT-BRIDGE-MIB::begemotBridgePfilIpOnly,INTEGER,read-write,,current,true(1):false(2),This value controls the handling of non-IP packets which
.1.3.6.1.4.1.12325.1.205.4.4,BEGEMOT-BRIDGE-MIB::begemotBridgeLayer2PfStatus,INTEGER,read-write,,current,enabled(1):disabled(2),This value indicates whether layer2 filtering by a
.1.3.6.1.4.1.12325.1.205.5,BEGEMOT-BRIDGE-MIB::begemotBridgeConfigObjects,,,,,,
.1.3.6.1.4.1.12325.1.205.5.1,BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf,OCTET,read-write,,current,,The name of the bridge interface that will be managed
.1.3.6.1.4.1.12325.1.205.5.2,BEGEMOT-BRIDGE-MIB::begemotBridgeDataUpdate,Integer32,read-write,,current,,The maximum age in seconds of the cached data.
.1.3.6.1.4.1.12325.1.205.5.3,BEGEMOT-BRIDGE-MIB::begemotBridgeDataPoll,Integer32,read-write,,current,,The polling rate of data when the module is idle.
.1.3.6.1.5,SNMPv2-SMI::security,,,,,,
.1.3.6.1.6,SNMPv2-SMI::snmpV2,,,,,,
.1.3.6.1.6.1,SNMPv2-SMI::snmpDomains,,,,,,
.1.3.6.1.6.1.1,SNMPv2-TM::snmpUDPDomain,,,,,,The SNMP over UDP over IPv4 transport domain. The corresponding transport address is of type SnmpUDPAddress.
.1.3.6.1.6.1.2,SNMPv2-TM::snmpCLNSDomain,,,,,,The SNMP over CLNS transport domain. The corresponding transport address is of type SnmpOSIAddress.
.1.3.6.1.6.1.3,SNMPv2-TM::snmpCONSDomain,,,,,,The SNMP over CONS transport domain. The corresponding transport address is of type SnmpOSIAddress.
.1.3.6.1.6.1.4,SNMPv2-TM::snmpDDPDomain,,,,,,The SNMP over DDP transport domain. The corresponding transport address is of type SnmpNBPAddress.
.1.3.6.1.6.1.5,SNMPv2-TM::snmpIPXDomain,,,,,,The SNMP over IPX transport domain. The corresponding transport address is of type SnmpIPXAddress.
.1.3.6.1.6.1.6,SNMP-IEEE802-TM-MIB::snmpIeee802Domain,,,,,,The SNMP over IEEE 802 networks transport domain. The corresponding transport address is of type MacAddress as defined in the SNMPv2-TC module (RFC 2579).
.1.3.6.1.6.1.8,SNMP-TLS-TM-MIB::snmpTLSTCPDomain,,,,,,The SNMP over TLS via TCP transport domain. The corresponding transport address is of type SnmpTLSAddress. The securityName prefix to be associated with the snmpTLSTCPDomain is 'tls'. This prefix may be used by security models or other components to identify which secure transport infrastructure authenticated a securityName.
.1.3.6.1.6.1.9,SNMP-TLS-TM-MIB::snmpDTLSUDPDomain,,,,,,The SNMP over DTLS via UDP transport domain. The corresponding transport address is of type SnmpTLSAddress. The securityName prefix to be associated with the snmpDTLSUDPDomain is 'dtls'. This prefix may be used by security models or other components to identify which secure transport infrastructure authenticated a securityName.
.1.3.6.1.6.2,SNMPv2-SMI::snmpProxys,,,,,,
.1.3.6.1.6.2.1,SNMPv2-TM::rfc1157Proxy,,,,,,
.1.3.6.1.6.2.1.1,SNMPv2-TM::rfc1157Domain,,,,,,The transport domain for SNMPv1 over UDP over IPv4. The corresponding transport address is of type SnmpUDPAddress.
.1.3.6.1.6.3,SNMPv2-SMI::snmpModules,,,,,,
.1.3.6.1.6.3.1,SNMPv2-MIB::snmpMIB,,,,,,The MIB module for SNMP entities. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3418; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.1.1,SNMPv2-MIB::snmpMIBObjects,,,,,,
.1.3.6.1.6.3.1.1.4,SNMPv2-MIB::snmpTrap,,,,,,
.1.3.6.1.6.3.1.1.4.1,SNMPv2-MIB::snmpTrapOID,OBJECT,accessible-for-notify,,current,,The authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2-Trap-PDU and InformRequest-PDU.
.1.3.6.1.6.3.1.1.4.3,SNMPv2-MIB::snmpTrapEnterprise,OBJECT,accessible-for-notify,,current,,The authoritative identification of the enterprise associated with the trap currently being sent. When an SNMP proxy agent is mapping an RFC1157 Trap-PDU into a SNMPv2-Trap-PDU, this variable occurs as the last varbind.
.1.3.6.1.6.3.1.1.5,SNMPv2-MIB::snmpTraps,,,,,,
.1.3.6.1.6.3.1.1.5.1,SNMPv2-MIB::coldStart,,,,,,A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered.
.1.3.6.1.6.3.1.1.5.2,SNMPv2-MIB::warmStart,,,,,,A warmStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself such that its configuration is unaltered.
.1.3.6.1.6.3.1.1.5.3,IF-MIB::linkDown,,,,,,A linkDown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of ifOperStatus.
.1.3.6.1.6.3.1.1.5.4,IF-MIB::linkUp,,,,,,A linkUp trap signifies that the SNMP entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links left the down state and transitioned into some other state (but not into the notPresent state). This other state is indicated by the included value of ifOperStatus.
.1.3.6.1.6.3.1.1.5.5,SNMPv2-MIB::authenticationFailure,,,,,,An authenticationFailure trap signifies that the SNMP entity has received a protocol message that is not properly authenticated. While all implementations of SNMP entities MAY be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated.
.1.3.6.1.6.3.1.1.6,SNMPv2-MIB::snmpSet,,,,,,
.1.3.6.1.6.3.1.1.6.1,SNMPv2-MIB::snmpSetSerialNo,INTEGER,read-write,,current,,An advisory lock used to allow several cooperating command generator applications to coordinate their use of the SNMP set operation. This object is used for coarse-grain coordination. To achieve fine-grain coordination, one or more similar objects might be defined within each MIB group, as appropriate.
.1.3.6.1.6.3.1.2,SNMPv2-MIB::snmpMIBConformance,,,,,,
.1.3.6.1.6.3.1.2.1,SNMPv2-MIB::snmpMIBCompliances,,,,,,
.1.3.6.1.6.3.1.2.1.2,SNMPv2-MIB::snmpBasicCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the SNMPv2 MIB. This compliance statement is replaced by snmpBasicComplianceRev2.
.1.3.6.1.6.3.1.2.1.3,SNMPv2-MIB::snmpBasicComplianceRev2,,,,,,The compliance statement for SNMP entities which implement this MIB module.
.1.3.6.1.6.3.1.2.2,SNMPv2-MIB::snmpMIBGroups,,,,,,
.1.3.6.1.6.3.1.2.2.5,SNMPv2-MIB::snmpSetGroup,,,,,,A collection of objects which allow several cooperating command generator applications to coordinate their use of the set operation.
.1.3.6.1.6.3.1.2.2.6,SNMPv2-MIB::systemGroup,,,,,,The system group defines objects which are common to all managed systems.
.1.3.6.1.6.3.1.2.2.7,SNMPv2-MIB::snmpBasicNotificationsGroup,,,,,,The basic notifications implemented by an SNMP entity supporting command responder applications.
.1.3.6.1.6.3.1.2.2.8,SNMPv2-MIB::snmpGroup,,,,,,A collection of objects providing basic instrumentation and control of an SNMP entity.
.1.3.6.1.6.3.1.2.2.9,SNMPv2-MIB::snmpCommunityGroup,,,,,,A collection of objects providing basic instrumentation of a SNMP entity which supports community-based authentication.
.1.3.6.1.6.3.1.2.2.10,SNMPv2-MIB::snmpObsoleteGroup,,,,,,A collection of objects from RFC 1213 made obsolete by this MIB module.
.1.3.6.1.6.3.1.2.2.11,SNMPv2-MIB::snmpWarmStartNotificationGroup,,,,,,An additional notification for an SNMP entity supporting command responder applications, if it is able to reinitialize itself such that its configuration is unaltered.
.1.3.6.1.6.3.1.2.2.12,SNMPv2-MIB::snmpNotificationGroup,,,,,,These objects are required for entities which support notification originator applications.
.1.3.6.1.6.3.2,SNMPv2-M2M-MIB::snmpM2M,,,,,,The Manager-to-Manager MIB module.
.1.3.6.1.6.3.2.1,SNMPv2-M2M-MIB::snmpM2MObjects,,,,,,
.1.3.6.1.6.3.2.1.1,SNMPv2-M2M-MIB::snmpAlarm,,,,,,
.1.3.6.1.6.3.2.1.1.1,SNMPv2-M2M-MIB::snmpAlarmNextIndex,INTEGER,read-only,,current,,The index number of the next appropriate unassigned entry in the snmpAlarmTable. The value 0 indicates that no unassigned entries are available. A management station should create new entries in the snmpAlarmTable using this algorithm: first, issue a management protocol retrieval operation to determine the value of snmpAlarmNextIndex; and, second, issue a management protocol set operation to create an instance of the snmpAlarmStatus object setting its value to `createAndGo' or `createAndWait' (as specified in the description of the RowStatus textual convention).
.1.3.6.1.6.3.2.1.1.2,SNMPv2-M2M-MIB::snmpAlarmTable,,not-accessible,,current,,A list of snmpAlarm entries.
.1.3.6.1.6.3.2.1.1.2.1,SNMPv2-M2M-MIB::snmpAlarmEntry,,not-accessible,contextIdentity:snmpAlarmIndex,current,,A list of parameters that set up a periodic sampling query to check for alarm conditions. The contextIdentity included in the INDEX clause is the context to which the sampling queries are directed.
.1.3.6.1.6.3.2.1.1.2.1.1,SNMPv2-M2M-MIB::snmpAlarmIndex,INTEGER,not-accessible,,current,,An index that uniquely identifies an entry in the snmpAlarm table for a particular sampling context. Each such entry defines a diagnostic sample at a particular interval for a variable in the particular context's object resources.
.1.3.6.1.6.3.2.1.1.2.1.2,SNMPv2-M2M-MIB::snmpAlarmVariable,OBJECT,read-create,,current,,The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (Integer32, Counter32, Gauge32, TimeTicks, Counter64, or UInteger32) may be sampled. If it is detected by an error response of authorizationError, noSuchObject, or noSuchInstance that the variable name of an established snmpAlarmEntry is no longer available in the sampling context, a single snmpObjectUnavailableAlarm event is generated and the status of this snmpAlarmEntry is set to `destroy'. Likewise, if the syntax of the variable retrieved by the query is not Integer32, Counter32, Gauge32, TimeTicks, Counter64, or UInteger32, the same actions will be taken. If the SNMPv2 entity acting in a dual role detects that the sampled value can not be obtained due to lack of response to management queries, it should either: 1) Set the status of this snmpAlarmEntry to `destroy', if it is determined that further communication is not possible; or, 2) Delete the associated snmpAlarmValue instance (but not the entire conceptual row), and continue to attempt to sample the variable and recreate the associated snmpAlarmValue instance should communication be reestablished. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.3,SNMPv2-M2M-MIB::snmpAlarmInterval,Integer32,read-create,,current,,The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this object and the sampling type is `deltaValue', care should be taken to ensure that the change during this interval of the variable being sampled will not exceed the (-2^31...2^31-1) range of the snmpAlarmValue. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.4,SNMPv2-M2M-MIB::snmpAlarmSampleType,INTEGER,read-create,,current,absoluteValue(1):deltaValue(2),The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is `absoluteValue', the value of the selected variable at the end of the sampling interval will be compared directly with both the snmpAlarmRisingThreshold and the snmpAlarmFallingThreshold values. If the value of this object is `deltaValue', the value of the selected variable at the end of the sampling interval will be subtracted from its value at the end of the previous sampling interval, and the difference compared with both the snmpAlarmRisingThreshold and the snmpAlarmFallingThreshold values. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.5,SNMPv2-M2M-MIB::snmpAlarmValue,Integer32,read-only,,current,,The value of the statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed. If the value of the statistic does not fit in the signed 32 bit representation of this object, it should be truncated in an implementation specific manner. Note that if the associated snmpAlarmSampleType is set to `deltaValue', the value of this object is the difference in the sampled variable since the last sample. This object will be created by the SNMPv2 entity acting in a dual role when this entry is set to `active', and the first sampling period has completed. It may be created and deleted at other times by the SNMPv2 entity acting in a dual role when the sampled value can not be obtained, as specified in the snmpAlarmVariable object.
.1.3.6.1.6.3.2.1.1.2.1.6,SNMPv2-M2M-MIB::snmpAlarmStartupAlarm,INTEGER,read-create,,current,risingAlarm(1):fallingAlarm(2):risingOrFallingAlarm(3),The alarm that may be sent when this entry is first set to `active'. If the first sample after this entry becomes active is greater than or equal to the risingThreshold and snmpAlarmStartupAlarm is equal to `risingAlarm' or `risingOrFallingAlarm', then a single rising alarm will be generated. If the first sample after this entry becomes active is less than or equal to the fallingThreshold and snmpAlarmStartupAlarm is equal to `fallingAlarm' or `risingOrFallingAlarm', then a single falling alarm will be generated. Note that a snmpObjectUnavailableAlarm is sent upon startup whenever it is applicable, independent of the setting of snmpAlarmStartupAlarm. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.7,SNMPv2-M2M-MIB::snmpAlarmRisingThreshold,Integer32,read-create,,current,,A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes active is greater than or equal to this threshold and the associated snmpAlarmStartupAlarm is equal to `risingAlarm' or `risingOrFallingAlarm'. After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the snmpAlarmFallingThreshold. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.8,SNMPv2-M2M-MIB::snmpAlarmFallingThreshold,Integer32,read-create,,current,,A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes active is less than or equal to this threshold and the associated snmpAlarmStartupAlarm is equal to `fallingAlarm' or `risingOrFallingAlarm'. After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the snmpAlarmRisingThreshold. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.9,SNMPv2-M2M-MIB::snmpAlarmRisingEventIndex,INTEGER,read-create,,current,,The index of the snmpEventEntry that is used when a rising threshold is crossed. The snmpEventEntry identified by a particular value of this index is the same as identified by the same value of the snmpEventIndex object. If there is no corresponding entry in the snmpEventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid snmpEventIndex. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.10,SNMPv2-M2M-MIB::snmpAlarmFallingEventIndex,INTEGER,read-create,,current,,The index of the snmpEventEntry that is used when a falling threshold is crossed. The snmpEventEntry identified by a particular value of this index is the same as identified by the same value of the snmpEventIndex object. If there is no corresponding entry in the snmpEventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid snmpEventIndex. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.11,SNMPv2-M2M-MIB::snmpAlarmUnavailableEventIndex,INTEGER,read-create,,current,,The index of the snmpEventEntry that is used when a variable becomes unavailable. The snmpEventEntry identified by a particular value of this index is the same as identified by the same value of the snmpEventIndex object. If there is no corresponding entry in the snmpEventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid snmpEventIndex. An attempt to modify this object will fail with an `inconsistentValue' error if the associated snmpAlarmStatus object would be equal to `active' both before and after the modification attempt.
.1.3.6.1.6.3.2.1.1.2.1.12,SNMPv2-M2M-MIB::snmpAlarmStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this snmpAlarm entry. This object may not be set to `active' unless the following columnar objects exist in this row: snmpAlarmVariable, snmpAlarmInterval, snmpAlarmSampleType, snmpAlarmStartupAlarm, snmpAlarmRisingThreshold, snmpAlarmFallingThreshold, snmpAlarmRisingEventIndex, snmpAlarmFallingEventIndex, and snmpAlarmUnavailableEventIndex.
.1.3.6.1.6.3.2.1.1.3,SNMPv2-M2M-MIB::snmpAlarmNotifications,,,,,,
.1.3.6.1.6.3.2.1.1.3.1,SNMPv2-M2M-MIB::snmpRisingAlarm,,,,,,An event that is generated when an alarm entry crosses its rising threshold. The instances of those objects contained within the varbind list are those of the alarm entry which generated this event.
.1.3.6.1.6.3.2.1.1.3.2,SNMPv2-M2M-MIB::snmpFallingAlarm,,,,,,An event that is generated when an alarm entry crosses its falling threshold. The instances of those objects contained within the varbind list are those of the alarm entry which generated this event.
.1.3.6.1.6.3.2.1.1.3.3,SNMPv2-M2M-MIB::snmpObjectUnavailableAlarm,,,,,,An event that is generated when a variable monitored by an alarm entry becomes unavailable. The instance of snmpAlarmVariable contained within the varbind list is the one associated with the alarm entry which generated this event.
.1.3.6.1.6.3.2.1.2,SNMPv2-M2M-MIB::snmpEvent,,,,,,
.1.3.6.1.6.3.2.1.2.1,SNMPv2-M2M-MIB::snmpEventNextIndex,INTEGER,read-only,,current,,The index number of the next appropriate unassigned entry in the snmpEventTable. The value 0 indicates that no unassigned entries are available. A management station should create new entries in the snmpEventTable using this algorithm: first, issue a management protocol retrieval operation to determine the value of snmpEventNextIndex; and, second, issue a management protocol set operation to create an instance of the snmpEventStatus object setting its value to `createAndWait' or 'createAndGo'.
.1.3.6.1.6.3.2.1.2.2,SNMPv2-M2M-MIB::snmpEventTable,,not-accessible,,current,,A list of events.
.1.3.6.1.6.3.2.1.2.2.1,SNMPv2-M2M-MIB::snmpEventEntry,,not-accessible,snmpEventIndex,current,,A set of parameters that describe an event that is generated when certain conditions are met.
.1.3.6.1.6.3.2.1.2.2.1.1,SNMPv2-M2M-MIB::snmpEventIndex,INTEGER,not-accessible,,current,,An index that uniquely identifies an entry in the snmpEvent table. Each such entry defines an event generated when the appropriate conditions occur.
.1.3.6.1.6.3.2.1.2.2.1.2,SNMPv2-M2M-MIB::snmpEventID,OBJECT,read-create,,current,,The authoritative identification of the event type generated by this entry. This variable occurs as the second varbind of an InformRequest- PDU. If this OBJECT IDENTIFIER maps to a NOTIFICATION-TYPE the sender will place the objects listed in the NOTIFICATION-TYPE in the varbind list.
.1.3.6.1.6.3.2.1.2.2.1.3,SNMPv2-M2M-MIB::snmpEventDescription,OCTET,read-create,,current,,A comment describing this snmpEvent entry.
.1.3.6.1.6.3.2.1.2.2.1.4,SNMPv2-M2M-MIB::snmpEventEvents,Counter32,read-only,,current,,The number of events caused by event generators associated with this snmpEvent entry.
.1.3.6.1.6.3.2.1.2.2.1.5,SNMPv2-M2M-MIB::snmpEventLastTimeSent,TimeTicks,read-only,,current,,The value of sysUpTime at the time this snmpEvent entry last generated an event. If this entry has not generated any events, this value will be zero.
.1.3.6.1.6.3.2.1.2.2.1.6,SNMPv2-M2M-MIB::snmpEventStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this snmpEvent entry. This object may not be set to `active' unless the following columnar objects exist in this row: snmpEventID, snmpEventDescription, snmpEventEvents, and snmpEventLastTimeSent. Setting an instance of this object to the value 'destroy' has the effect of invalidating any/all entries in the snmpEventTable, and the snmpEventNotifyTable which reference the corresponding snmpEventEntry.
.1.3.6.1.6.3.2.1.2.3,SNMPv2-M2M-MIB::snmpEventNotifyMinInterval,Integer32,read-only,,current,,The minimum interval that the SNMPv2 entity acting in a dual role will wait before retransmitting an InformRequest-PDU. This object specifies the minimal value supported by the SNMPv2 entity acting in a dual role, based on resource or implementation constraints. For a particular entry in the snmpEventNotifyTable, if the associated snmpEventNotifyIntervalRequested variable is greater than this object, the snmpEventNotifyIntervalRequested value shall be used as the minimum interval for retransmissions of InformRequest-PDUs sent on behalf of that entry.
.1.3.6.1.6.3.2.1.2.4,SNMPv2-M2M-MIB::snmpEventNotifyMaxRetransmissions,Integer32,read-only,,current,,The maximum number of time that the SNMPv2 entity acting in a dual role will retransmit an InformRequest-PDU. This object specifies the maximal value supported by the SNMPv2 entity acting in a dual role, based on resource or implementation constraints. For a particular entry in the snmpEventNotifyTable, if the associated snmpEventNotifyRetransmissionsRequested variable is less than this object, the snmpEventNotifyRetransmissionsRequested value shall be used as the retransmission count for InformRequest-PDUs sent on behalf of that entry.
.1.3.6.1.6.3.2.1.2.5,SNMPv2-M2M-MIB::snmpEventNotifyTable,,not-accessible,,current,,A list of protocol configuration entries for event notifications from this entity.
.1.3.6.1.6.3.2.1.2.5.1,SNMPv2-M2M-MIB::snmpEventNotifyEntry,,not-accessible,snmpEventIndex:contextIdentity,current,,A set of parameters that describe the type and destination of InformRequest-PDUs sent for a particular event. The snmpEventIndex in this entry's INDEX clause identifies the snmpEventEntry which, when triggered, will generate a notification as configured in this entry. The contextIdentity in this entry's INDEX clause identifies the context to which a notification will be sent.
.1.3.6.1.6.3.2.1.2.5.1.1,SNMPv2-M2M-MIB::snmpEventNotifyIntervalRequested,Integer32,read-create,,current,,The requested interval for retransmission of Inform PDUs generated on the behalf of this entry. This variable will be the actual interval used unless the snmpEventNotifyMinInterval is greater than this object, in which case the interval shall be equal to snmpEventNotifyMinInterval.
.1.3.6.1.6.3.2.1.2.5.1.2,SNMPv2-M2M-MIB::snmpEventNotifyRetransmissionsRequested,Integer32,read-create,,current,,The requested number of retransmissions of an InformRequest-PDU generated on behalf of this entry. This variable will be the actual number of retransmissions used unless the snmpEventNotifyMaxRetransmissions is less than this object, in which case the retransmission count shall be equal to snmpEventNotifyMaxRetransmissions.
.1.3.6.1.6.3.2.1.2.5.1.3,SNMPv2-M2M-MIB::snmpEventNotifyLifetime,Integer32,read-create,,current,,The number of seconds this entry shall live until the corresponding instance of snmpEventNotifyStatus is set to 'destroy'. This value shall count down to zero, at which time the corresponding instance of snmpEventNotifyStatus will be set to 'destroy'. Any management station that is using this entry must periodically refresh this value to ensure the continued delivery of events.
.1.3.6.1.6.3.2.1.2.5.1.4,SNMPv2-M2M-MIB::snmpEventNotifyStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The state of this snmpEventNotifyEntry. This object may not be set to `active' unless the following columnar objects exist in this row: snmpEventNotifyIntervalRequested, snmpEventNotifyRetransmissionsRequested, and snmpEventNotifyLifetime.
.1.3.6.1.6.3.2.2,SNMPv2-M2M-MIB::snmpM2MConformance,,,,,,
.1.3.6.1.6.3.2.2.1,SNMPv2-M2M-MIB::snmpM2MCompliances,,,,,,
.1.3.6.1.6.3.2.2.1.1,SNMPv2-M2M-MIB::snmpM2MCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the Manager-to-Manager MIB.
.1.3.6.1.6.3.2.2.2,SNMPv2-M2M-MIB::snmpM2MGroups,,,,,,
.1.3.6.1.6.3.2.2.2.1,SNMPv2-M2M-MIB::snmpAlarmGroup,,,,,,A collection of objects allowing the description and configuration of threshold alarms from a SNMPv2 entity acting in a dual role.
.1.3.6.1.6.3.2.2.2.2,SNMPv2-M2M-MIB::snmpEventGroup,,,,,,A collection of objects allowing the description and configuration of events from a SNMPv2 entity acting in a dual role.
.1.3.6.1.6.3.3,SNMPv2-PARTY-MIB::partyMIB,,,,,,The MIB module describing SNMPv2 parties.
.1.3.6.1.6.3.3.1,SNMPv2-PARTY-MIB::partyAdmin,,,,,,
.1.3.6.1.6.3.3.1.1,SNMPv2-PARTY-MIB::partyProtocols,,,,,,
.1.3.6.1.6.3.3.1.1.1,SNMPv2-PARTY-MIB::noAuth,,,,,,
.1.3.6.1.6.3.3.1.1.2,SNMPv2-PARTY-MIB::noPriv,,,,,,
.1.3.6.1.6.3.3.1.1.3,SNMPv2-PARTY-MIB::desPrivProtocol,,,,,,
.1.3.6.1.6.3.3.1.1.4,SNMPv2-PARTY-MIB::v2md5AuthProtocol,,,,,,
.1.3.6.1.6.3.3.1.2,SNMPv2-PARTY-MIB::temporalDomains,,,,,,
.1.3.6.1.6.3.3.1.2.1,SNMPv2-PARTY-MIB::currentTime,,,,,,
.1.3.6.1.6.3.3.1.2.2,SNMPv2-PARTY-MIB::restartTime,,,,,,
.1.3.6.1.6.3.3.1.2.3,SNMPv2-PARTY-MIB::cacheTime,,,,,,
.1.3.6.1.6.3.3.1.3,SNMPv2-PARTY-MIB::initialPartyId,,,,,,
.1.3.6.1.6.3.3.1.4,SNMPv2-PARTY-MIB::initialContextId,,,,,,
.1.3.6.1.6.3.3.2,SNMPv2-PARTY-MIB::partyMIBObjects,,,,,,
.1.3.6.1.6.3.3.2.1,SNMPv2-PARTY-MIB::snmpParties,,,,,,
.1.3.6.1.6.3.3.2.1.1,SNMPv2-PARTY-MIB::partyTable,,not-accessible,,current,,The SNMPv2 Party database.
.1.3.6.1.6.3.3.2.1.1.1,SNMPv2-PARTY-MIB::partyEntry,,not-accessible,IMPLIEDpartyIdentity,current,,Locally held information about a particular SNMPv2 party.
.1.3.6.1.6.3.3.2.1.1.1.1,SNMPv2-PARTY-MIB::partyIdentity,OBJECT,not-accessible,,current,,A party identifier uniquely identifying a particular SNMPv2 party.
.1.3.6.1.6.3.3.2.1.1.1.2,SNMPv2-PARTY-MIB::partyIndex,INTEGER,read-only,,current,,A unique value for each SNMPv2 party. The value for each SNMPv2 party must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
.1.3.6.1.6.3.3.2.1.1.1.3,SNMPv2-PARTY-MIB::partyTDomain,OBJECT,read-create,,current,,Indicates the kind of transport service by which the party receives network management traffic.
.1.3.6.1.6.3.3.2.1.1.1.4,SNMPv2-PARTY-MIB::partyTAddress,OCTET,read-create,,current,,The transport service address by which the party receives network management traffic, formatted according to the corresponding value of partyTDomain. For snmpUDPDomain, partyTAddress is formatted as a 4-octet IP Address concatenated with a 2-octet UDP port number.
.1.3.6.1.6.3.3.2.1.1.1.5,SNMPv2-PARTY-MIB::partyMaxMessageSize,INTEGER,read-create,,current,,The maximum length in octets of a SNMPv2 message which this party will accept. For parties which execute at an agent, the agent initializes this object to the maximum length supported by the agent, and does not let the object be set to any larger value. For parties which do not execute at the agent, the agent must allow the manager to set this object to any legal value, even if it is larger than the agent can generate.
.1.3.6.1.6.3.3.2.1.1.1.6,SNMPv2-PARTY-MIB::partyLocal,INTEGER,read-create,,current,true(1):false(2),An indication of whether this party executes at this SNMPv2 entity. If this object has a value of true(1), then the SNMPv2 entity will listen for SNMPv2 messages on the partyTAddress associated with this party. If this object has the value false(2), then the SNMPv2 entity will not listen for SNMPv2 messages on the partyTAddress associated with this party.
.1.3.6.1.6.3.3.2.1.1.1.7,SNMPv2-PARTY-MIB::partyAuthProtocol,OBJECT,read-create,,current,,The authentication protocol by which all messages generated by the party are authenticated as to origin and integrity. The value noAuth signifies that messages generated by the party are not authenticated. Once an instance of this object is created, its value can not be changed.
.1.3.6.1.6.3.3.2.1.1.1.8,SNMPv2-PARTY-MIB::partyAuthClock,UInteger32,read-create,,current,,The authentication clock which represents the local notion of the current time specific to the party. This value must not be decremented unless the party's private authentication key is changed simultaneously.
.1.3.6.1.6.3.3.2.1.1.1.9,SNMPv2-PARTY-MIB::partyAuthPrivate,OCTET,read-create,,current,,An encoding of the party's private authentication key which may be needed to support the authentication protocol. Although the value of this variable may be altered by a management operation (e.g., a SNMPv2 Set-Request), its value can never be retrieved by a management operation: when read, the value of this variable is the zero length OCTET STRING. The private authentication key is NOT directly represented by the value of this variable, but rather it is represented according to an encoding. This encoding is the bitwise exclusive-OR of the old key with the new key, i.e., of the old private authentication key (prior to the alteration) with the new private authentication key (after the alteration). Thus, when processing a received protocol Set operation, the new private authentication key is obtained from the value of this variable as the result of a bitwise exclusive-OR of the variable's value and the old private authentication key. In calculating the exclusive-OR, if the old key is shorter than the new key, zero-valued padding is appended to the old key. If no value for the old key exists, a zero-length OCTET STRING is used in the calculation.
.1.3.6.1.6.3.3.2.1.1.1.10,SNMPv2-PARTY-MIB::partyAuthPublic,OCTET,read-create,,current,,A publically-readable value for the party. Depending on the party's authentication protocol, this value may be needed to support the party's authentication protocol. Alternatively, it may be used by a manager during the procedure for altering secret information about a party. (For example, by altering the value of an instance of this object in the same SNMPv2 Set-Request used to update an instance of partyAuthPrivate, a subsequent Get-Request can determine if the Set- Request was successful in the event that no response to the Set-Request is received, see [4].) The length of the value is dependent on the party's authentication protocol. If not used by the authentication protocol, it is recommended that agents support values of any length up to and including the length of the corresponding partyAuthPrivate object.
.1.3.6.1.6.3.3.2.1.1.1.11,SNMPv2-PARTY-MIB::partyAuthLifetime,INTEGER,read-create,,current,,The lifetime (in units of seconds) which represents an administrative upper bound on acceptable delivery delay for protocol messages generated by the party. Once an instance of this object is created, its value can not be changed.
.1.3.6.1.6.3.3.2.1.1.1.12,SNMPv2-PARTY-MIB::partyPrivProtocol,OBJECT,read-create,,current,,The privacy protocol by which all protocol messages received by the party are protected from disclosure. The value noPriv signifies that messages received by the party are not protected. Once an instance of this object is created, its value can not be changed.
.1.3.6.1.6.3.3.2.1.1.1.13,SNMPv2-PARTY-MIB::partyPrivPrivate,OCTET,read-create,,current,,An encoding of the party's private encryption key which may be needed to support the privacy protocol. Although the value of this variable may be altered by a management operation (e.g., a SNMPv2 Set-Request), its value can never be retrieved by a management operation: when read, the value of this variable is the zero length OCTET STRING. The private encryption key is NOT directly represented by the value of this variable, but rather it is represented according to an encoding. This encoding is the bitwise exclusive-OR of the old key with the new key, i.e., of the old private encryption key (prior to the alteration) with the new private encryption key (after the alteration). Thus, when processing a received protocol Set operation, the new private encryption key is obtained from the value of this variable as the result of a bitwise exclusive-OR of the variable's value and the old private encryption key. In calculating the exclusive-OR, if the old key is shorter than the new key, zero-valued padding is appended to the old key. If no value for the old key exists, a zero-length OCTET STRING is used in the calculation.
.1.3.6.1.6.3.3.2.1.1.1.14,SNMPv2-PARTY-MIB::partyPrivPublic,OCTET,read-create,,current,,A publically-readable value for the party. Depending on the party's privacy protocol, this value may be needed to support the party's privacy protocol. Alternatively, it may be used by a manager as a part of its procedure for altering secret information about a party. (For example, by altering the value of an instance of this object in the same SNMPv2 Set-Request used to update an instance of partyPrivPrivate, a subsequent Get-Request can determine if the Set- Request was successful in the event that no response to the Set-Request is received, see [4].) The length of the value is dependent on the party's privacy protocol. If not used by the privacy protocol, it is recommended that agents support values of any length up to and including the length of the corresponding partyPrivPrivate object.
.1.3.6.1.6.3.3.2.1.1.1.15,SNMPv2-PARTY-MIB::partyCloneFrom,OBJECT,read-create,,current,,The identity of a party to clone authentication and privacy parameters from. When read, the value { 0 0 } is returned. This value must be written exactly once, when the associated instance of partyStatus either does not exist or has the value `notReady'. When written, the value identifies a party, the cloning party, whose status column has the value `active'. The cloning party is used in two ways. One, if instances of the following objects do not exist for the party being created, then they are created with values identical to those of the corresponding objects for the cloning party: partyAuthProtocol partyAuthPublic partyAuthLifetime partyPrivProtocol partyPrivPublic Two, instances of the following objects are updated using the corresponding values of the cloning party: partyAuthPrivate partyPrivPrivate (e.g., the value of the cloning party's instance of the partyAuthPrivate object is XOR'd with the value of the partyAuthPrivate instances of the party being created.)
.1.3.6.1.6.3.3.2.1.1.1.16,SNMPv2-PARTY-MIB::partyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4),The storage type for this conceptual row in the partyTable.
.1.3.6.1.6.3.3.2.1.1.1.17,SNMPv2-PARTY-MIB::partyStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row in the partyTable. A party is not qualified for activation until instances of all columns of its partyEntry row have an appropriate value. In particular: A value must be written to the Party's partyCloneFrom object. If the Party's partyAuthProtocol object has the value md5AuthProtocol, then the corresponding instance of partyAuthPrivate must contain a secret of the appropriate length. Further, at least one management protocol set operation updating the value of the party's partyAuthPrivate object must be successfully processed, before the partyAuthPrivate column is considered appropriately configured. If the Party's partyPrivProtocol object has the value desPrivProtocol, then the corresponding instance of partyPrivPrivate must contain a secret of the appropriate length. Further, at least one management protocol set operation updating the value of the party's partyPrivPrivate object must be successfully processed, before the partyPrivPrivate column is considered appropriately configured. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the partyStatus column is `notReady'.
.1.3.6.1.6.3.3.2.2,SNMPv2-PARTY-MIB::snmpContexts,,,,,,
.1.3.6.1.6.3.3.2.2.1,SNMPv2-PARTY-MIB::contextTable,,not-accessible,,current,,The SNMPv2 Context database.
.1.3.6.1.6.3.3.2.2.1.1,SNMPv2-PARTY-MIB::contextEntry,,not-accessible,IMPLIEDcontextIdentity,current,,Locally held information about a particular SNMPv2 context.
.1.3.6.1.6.3.3.2.2.1.1.1,SNMPv2-PARTY-MIB::contextIdentity,OBJECT,not-accessible,,current,,A context identifier uniquely identifying a particular SNMPv2 context.
.1.3.6.1.6.3.3.2.2.1.1.2,SNMPv2-PARTY-MIB::contextIndex,INTEGER,read-only,,current,,A unique value for each SNMPv2 context. The value for each SNMPv2 context must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.6.3.3.2.2.1.1.3,SNMPv2-PARTY-MIB::contextLocal,INTEGER,read-create,,current,true(1):false(2),An indication of whether this context is realized by this SNMPv2 entity.
.1.3.6.1.6.3.3.2.2.1.1.4,SNMPv2-PARTY-MIB::contextViewIndex,INTEGER,read-create,,current,,If the value of an instance of this object is zero, then this corresponding conceptual row in the contextTable refers to a SNMPv2 context which identifies a proxy relationship; the values of the corresponding instances of the contextProxyDstParty, contextProxySrcParty, and contextProxyContext objects provide further information on the proxy relationship. Otherwise, if the value of an instance of this object is greater than zero, then this corresponding conceptual row in the contextTable refers to a SNMPv2 context which identifies a MIB view of a locally accessible entity; the value of the instance identifies the particular MIB view which has the same value of viewIndex; and the value of the corresponding instances of the contextLocalEntity and contextLocalTime objects provide further information on the local entity and its temporal domain.
.1.3.6.1.6.3.3.2.2.1.1.5,SNMPv2-PARTY-MIB::contextLocalEntity,OCTET,read-create,,current,,If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object identifies the local entity whose management information is in the SNMPv2 context's MIB view. The empty string indicates that the MIB view contains the SNMPv2 entity's own local management information; otherwise, a non-empty string indicates that the MIB view contains management information of some other local entity, e.g., 'Repeater1'.
.1.3.6.1.6.3.3.2.2.1.1.6,SNMPv2-PARTY-MIB::contextLocalTime,OBJECT,read-create,,current,,If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object identifies the temporal context of the management information in the MIB view.
.1.3.6.1.6.3.3.2.2.1.1.7,SNMPv2-PARTY-MIB::contextProxyDstParty,OBJECT,read-create,,current,,If the value of the corresponding instance of the contextViewIndex is equal to zero, then the value of an instance of this object identifies a SNMPv2 party which is the proxy destination of a proxy relationship. If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object is { 0 0 }.
.1.3.6.1.6.3.3.2.2.1.1.8,SNMPv2-PARTY-MIB::contextProxySrcParty,OBJECT,read-create,,current,,If the value of the corresponding instance of the contextViewIndex is equal to zero, then the value of an instance of this object identifies a SNMPv2 party which is the proxy source of a proxy relationship. Interpretation of an instance of this object depends upon the value of the transport domain associated with the SNMPv2 party used as the proxy destination in this proxy relationship. If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object is { 0 0 }.
.1.3.6.1.6.3.3.2.2.1.1.9,SNMPv2-PARTY-MIB::contextProxyContext,OBJECT,read-create,,current,,If the value of the corresponding instance of the contextViewIndex is equal to zero, then the value of an instance of this object identifies the context of a proxy relationship. Interpretation of an instance of this object depends upon the value of the transport domain associated with the SNMPv2 party used as the proxy destination in this proxy relationship. If the value of the corresponding instance of the contextViewIndex is greater than zero, then the value of an instance of this object is { 0 0 }.
.1.3.6.1.6.3.3.2.2.1.1.10,SNMPv2-PARTY-MIB::contextStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4),The storage type for this conceptual row in the contextTable.
.1.3.6.1.6.3.3.2.2.1.1.11,SNMPv2-PARTY-MIB::contextStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row in the contextTable. A context is not qualified for activation until instances of all corresponding columns have the appropriate value. In particular, if the context's contextViewIndex is greater than zero, then the viewStatus column of the associated conceptual row(s) in the viewTable must have the value `active'. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the contextStatus column is `notReady'.
.1.3.6.1.6.3.3.2.3,SNMPv2-PARTY-MIB::snmpAccess,,,,,,
.1.3.6.1.6.3.3.2.3.1,SNMPv2-PARTY-MIB::aclTable,,not-accessible,,current,,The access privileges database.
.1.3.6.1.6.3.3.2.3.1.1,SNMPv2-PARTY-MIB::aclEntry,,not-accessible,aclTarget:aclSubject:aclResources,current,,The access privileges for a particular subject SNMPv2 party when asking a particular target SNMPv2 party to access a particular SNMPv2 context.
.1.3.6.1.6.3.3.2.3.1.1.1,SNMPv2-PARTY-MIB::aclTarget,INTEGER,not-accessible,,current,,The value of an instance of this object identifies a SNMPv2 party which is the target of an access control policy, and has the same value as the instance of the partyIndex object for that party.
.1.3.6.1.6.3.3.2.3.1.1.2,SNMPv2-PARTY-MIB::aclSubject,INTEGER,not-accessible,,current,,The value of an instance of this object identifies a SNMPv2 party which is the subject of an access control policy, and has the same value as the instance of the partyIndex object for that SNMPv2 party.
.1.3.6.1.6.3.3.2.3.1.1.3,SNMPv2-PARTY-MIB::aclResources,INTEGER,not-accessible,,current,,The value of an instance of this object identifies a SNMPv2 context in an access control policy, and has the same value as the instance of the contextIndex object for that SNMPv2 context.
.1.3.6.1.6.3.3.2.3.1.1.4,SNMPv2-PARTY-MIB::aclPrivileges,INTEGER,read-create,,current,,The access privileges which govern what management operations a particular target party may perform with respect to a particular SNMPv2 context when requested by a particular subject party. These privileges are specified as a sum of values, where each value specifies a SNMPv2 PDU type by which the subject party may request a permitted operation. The value for a particular PDU type is computed as 2 raised to the value of the ASN.1 context-specific tag for the appropriate SNMPv2 PDU type. The values (for the tags defined in [5]) are defined in [3] as: Get : 1 GetNext : 2 Response : 4 Set : 8 unused : 16 GetBulk : 32 Inform : 64 SNMPv2-Trap : 128 The null set is represented by the value zero.
.1.3.6.1.6.3.3.2.3.1.1.5,SNMPv2-PARTY-MIB::aclStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4),The storage type for this conceptual row in the aclTable.
.1.3.6.1.6.3.3.2.3.1.1.6,SNMPv2-PARTY-MIB::aclStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row in the aclTable.
.1.3.6.1.6.3.3.2.4,SNMPv2-PARTY-MIB::snmpViews,,,,,,
.1.3.6.1.6.3.3.2.4.1,SNMPv2-PARTY-MIB::viewTable,,not-accessible,,current,,Locally held information about the MIB views known to this SNMPv2 entity. Each SNMPv2 context which is locally accessible has a single MIB view which is defined by two collections of view subtrees: the included view subtrees, and the excluded view subtrees. Every such subtree, both included and excluded, is defined in this table. To determine if a particular object instance is in a particular MIB view, compare the object instance's OBJECT IDENTIFIER with each of the MIB view's entries in this table. If none match, then the object instance is not in the MIB view. If one or more match, then the object instance is included in, or excluded from, the MIB view according to the value of viewType in the entry whose value of viewSubtree has the most sub- identifiers. If multiple entries match and have the same number of sub-identifiers, then the lexicographically greatest instance of viewType determines the inclusion or exclusion. An object instance's OBJECT IDENTIFIER X matches an entry in this table when the number of sub- identifiers in X is at least as many as in the value of viewSubtree for the entry, and each sub- identifier in the value of viewSubtree matches its corresponding sub-identifier in X. Two sub- identifiers match either if the corresponding bit of viewMask is zero (the 'wild card' value), or if they are equal. Due to this 'wild card' capability, we introduce the term, a 'family' of view subtrees, to refer to the set of subtrees defined by a particular combination of values of viewSubtree and viewMask. In the case where no 'wild card' is defined in viewMask, the family of view subtrees reduces to a single view subtree.
.1.3.6.1.6.3.3.2.4.1.1,SNMPv2-PARTY-MIB::viewEntry,,not-accessible,viewIndex:IMPLIEDviewSubtree,current,,Information on a particular family of view subtrees included in or excluded from a particular SNMPv2 context's MIB view. Implementations must not restrict the number of families of view subtrees for a given MIB view, except as dictated by resource constraints on the overall number of entries in the viewTable.
.1.3.6.1.6.3.3.2.4.1.1.1,SNMPv2-PARTY-MIB::viewIndex,INTEGER,not-accessible,,current,,A unique value for each MIB view. The value for each MIB view must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
.1.3.6.1.6.3.3.2.4.1.1.2,SNMPv2-PARTY-MIB::viewSubtree,OBJECT,not-accessible,,current,,A MIB subtree.
.1.3.6.1.6.3.3.2.4.1.1.3,SNMPv2-PARTY-MIB::viewMask,OCTET,read-create,,current,,The bit mask which, in combination with the corresponding instance of viewSubtree, defines a family of view subtrees. Each bit of this bit mask corresponds to a sub- identifier of viewSubtree, with the most significant bit of the i-th octet of this octet string value (extended if necessary, see below) corresponding to the (8*i - 7)-th sub-identifier, and the least significant bit of the i-th octet of this octet string corresponding to the (8*i)-th sub-identifier, where i is in the range 1 through 16. Each bit of this bit mask specifies whether or not the corresponding sub-identifiers must match when determining if an OBJECT IDENTIFIER is in this family of view subtrees; a '1' indicates that an exact match must occur; a '0' indicates 'wild card', i.e., any sub-identifier value matches. Thus, the OBJECT IDENTIFIER X of an object instance is contained in a family of view subtrees if the following criteria are met: for each sub-identifier of the value of viewSubtree, either: the i-th bit of viewMask is 0, or the i-th sub-identifier of X is equal to the i-th sub-identifier of the value of viewSubtree. If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of viewSubtree, then the bit mask is extended with 1's to be the required length. Note that when the value of this object is the zero-length string, this extension rule results in a mask of all-1's being used (i.e., no 'wild card'), and the family of view subtrees is the one view subtree uniquely identified by the corresponding instance of viewSubtree.
.1.3.6.1.6.3.3.2.4.1.1.4,SNMPv2-PARTY-MIB::viewType,INTEGER,read-create,,current,included(1):excluded(2),The status of a particular family of view subtrees within the particular SNMPv2 context's MIB view. The value 'included(1)' indicates that the corresponding instances of viewSubtree and viewMask define a family of view subtrees included in the MIB view. The value 'excluded(2)' indicates that the corresponding instances of viewSubtree and viewMask define a family of view subtrees excluded from the MIB view.
.1.3.6.1.6.3.3.2.4.1.1.5,SNMPv2-PARTY-MIB::viewStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4),The storage type for this conceptual row in the viewTable.
.1.3.6.1.6.3.3.2.4.1.1.6,SNMPv2-PARTY-MIB::viewStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row in the viewTable.
.1.3.6.1.6.3.3.3,SNMPv2-PARTY-MIB::partyMIBConformance,,,,,,
.1.3.6.1.6.3.3.3.1,SNMPv2-PARTY-MIB::partyMIBCompliances,,,,,,
.1.3.6.1.6.3.3.3.1.1,SNMPv2-PARTY-MIB::unSecurableCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the Party MIB, but do not support any authentication or privacy protocols (i.e., only the noAuth and noPriv protocols are supported).
.1.3.6.1.6.3.3.3.1.2,SNMPv2-PARTY-MIB::partyNoPrivacyCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the Party MIB, and support an authentication protocol, but do not support any privacy protocols (i.e., only the noAuth, v2md5AuthProtocol, and noPriv protocols are supported).
.1.3.6.1.6.3.3.3.1.3,SNMPv2-PARTY-MIB::partyPrivacyCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the Party MIB, support an authentication protocol, and support a privacy protocol ONLY for the purpose of accessing security parameters. For all aclTable entries authorizing a subject and/or target SNMPv2 party whose privacy protocol is desPrivProtocol, to be used in accessing a SNMPv2 context, the MIB view for that SNMPv2 context shall include only those objects subordinate to partyMIBObjects, or a subset thereof, e.g., viewSubtree = { partyMIBObjects } viewMask = ''H viewType = { included } Any attempt to configure an entry in the partyTable, the contextTable, the aclTable or the viewTable such that a party using the desPrivProtocol would be authorized for use in accessing objects outside of the partyMIBObjects subtree shall result in the appropriate error response (e.g., wrongValue or inconsistentValue).
.1.3.6.1.6.3.3.3.1.4,SNMPv2-PARTY-MIB::fullPrivacyCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the Party MIB, support an authentication protocol, and support a privacy protocol without restrictions on its use.
.1.3.6.1.6.3.3.3.2,SNMPv2-PARTY-MIB::partyMIBGroups,,,,,,
.1.3.6.1.6.3.3.3.2.1,SNMPv2-PARTY-MIB::partyMIBGroup,,,,,,The collection of objects allowing the description and configuration of SNMPv2 parties. Note that objects which support proxy relationships are not included in this conformance group.
.1.3.6.1.6.3.6,SNMPv2-USEC-MIB::usecMIB,,,,,,The MIB module for SNMPv2 entities implementing the user- based security model.
.1.3.6.1.6.3.6.1,SNMPv2-USEC-MIB::usecMIBObjects,,,,,,
.1.3.6.1.6.3.6.1.1,SNMPv2-USEC-MIB::usecAgent,,,,,,
.1.3.6.1.6.3.6.1.1.1,SNMPv2-USEC-MIB::agentID,OCTET,read-only,,current,,The agent's administratively-unique identifier.
.1.3.6.1.6.3.6.1.1.2,SNMPv2-USEC-MIB::agentBoots,Unsigned32,read-only,,current,,The number of times that the agent has re-initialized itself since its initial configuration.
.1.3.6.1.6.3.6.1.1.3,SNMPv2-USEC-MIB::agentTime,Unsigned32,read-only,,current,,The number of seconds since the agent last incremented the agentBoots object.
.1.3.6.1.6.3.6.1.1.4,SNMPv2-USEC-MIB::agentSize,INTEGER,read-only,,current,,The maximum length in octets of an SNMPv2 message which this agent will accept using any transport mapping.
.1.3.6.1.6.3.6.1.2,SNMPv2-USEC-MIB::usecStats,,,,,,
.1.3.6.1.6.3.6.1.2.1,SNMPv2-USEC-MIB::usecStatsUnsupportedQoS,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because they requested a quality-of- service that was unknown to the agent or otherwise unavailable.
.1.3.6.1.6.3.6.1.2.2,SNMPv2-USEC-MIB::usecStatsNotInWindows,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because they appeared outside of the agent's window.
.1.3.6.1.6.3.6.1.2.3,SNMPv2-USEC-MIB::usecStatsUnknownUserNames,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because they referenced a user that was not known to the agent.
.1.3.6.1.6.3.6.1.2.4,SNMPv2-USEC-MIB::usecStatsWrongDigestValues,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because they didn't contain the expected digest value.
.1.3.6.1.6.3.6.1.2.5,SNMPv2-USEC-MIB::usecStatsUnknownContexts,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because they referenced a context that was not known to the agent.
.1.3.6.1.6.3.6.1.2.6,SNMPv2-USEC-MIB::usecStatsBadParameters,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because the <parameters> field was improperly encoded or had invalid syntax.
.1.3.6.1.6.3.6.1.2.7,SNMPv2-USEC-MIB::usecStatsUnauthorizedOperations,Counter32,read-only,,current,,The total number of packets received by the SNMPv2 entity which were dropped because the PDU type referred to an operation that is invalid or not authorized.
.1.3.6.1.6.3.6.2,SNMPv2-USEC-MIB::usecMIBConformance,,,,,,
.1.3.6.1.6.3.6.2.1,SNMPv2-USEC-MIB::usecMIBCompliances,,,,,,
.1.3.6.1.6.3.6.2.1.1,SNMPv2-USEC-MIB::usecMIBCompliance,,,,,,The compliance statement for SNMPv2 entities which implement the SNMPv2 USEC model.
.1.3.6.1.6.3.6.2.2,SNMPv2-USEC-MIB::usecMIBGroups,,,,,,
.1.3.6.1.6.3.6.2.2.1,SNMPv2-USEC-MIB::usecBasicGroup,,,,,,A collection of objects providing identification, clocks, and capabilities of an SNMPv2 entity which implements the SNMPv2 USEC model.
.1.3.6.1.6.3.6.2.2.2,SNMPv2-USEC-MIB::usecStatsGroup,,,,,,A collection of objects providing basic error statistics of an SNMPv2 entity which implements the SNMPv2 USEC model.
.1.3.6.1.6.3.10,SNMP-FRAMEWORK-MIB::snmpFrameworkMIB,,,,,,The SNMP Management Architecture MIB Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3411; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.10.1,SNMP-FRAMEWORK-MIB::snmpFrameworkAdmin,,,,,,
.1.3.6.1.6.3.10.1.1,SNMP-FRAMEWORK-MIB::snmpAuthProtocols,,,,,,Registration point for standards-track authentication protocols used in SNMP Management Frameworks. 
.1.3.6.1.6.3.10.1.1.1,SNMP-USER-BASED-SM-MIB::usmNoAuthProtocol,,,,,,No Authentication Protocol.
.1.3.6.1.6.3.10.1.1.2,SNMP-USER-BASED-SM-MIB::usmHMACMD5AuthProtocol,,,,,,The HMAC-MD5-96 Digest Authentication Protocol.
.1.3.6.1.6.3.10.1.1.3,SNMP-USER-BASED-SM-MIB::usmHMACSHAAuthProtocol,,,,,,The HMAC-SHA-96 Digest Authentication Protocol.
.1.3.6.1.6.3.10.1.1.4,SNMP-USM-HMAC-SHA2-MIB::usmHMAC128SHA224AuthProtocol,,,,,,The Authentication Protocol usmHMAC128SHA224AuthProtocol uses HMAC-SHA-224 and truncates output to 128 bits.
.1.3.6.1.6.3.10.1.1.5,SNMP-USM-HMAC-SHA2-MIB::usmHMAC192SHA256AuthProtocol,,,,,,The Authentication Protocol usmHMAC192SHA256AuthProtocol uses HMAC-SHA-256 and truncates output to 192 bits.
.1.3.6.1.6.3.10.1.1.6,SNMP-USM-HMAC-SHA2-MIB::usmHMAC256SHA384AuthProtocol,,,,,,The Authentication Protocol usmHMAC256SHA384AuthProtocol uses HMAC-SHA-384 and truncates output to 256 bits.
.1.3.6.1.6.3.10.1.1.7,SNMP-USM-HMAC-SHA2-MIB::usmHMAC384SHA512AuthProtocol,,,,,,The Authentication Protocol usmHMAC384SHA512AuthProtocol uses HMAC-SHA-512 and truncates output to 384 bits.
.1.3.6.1.6.3.10.1.2,SNMP-FRAMEWORK-MIB::snmpPrivProtocols,,,,,,Registration point for standards-track privacy protocols used in SNMP Management Frameworks. 
.1.3.6.1.6.3.10.1.2.1,SNMP-USER-BASED-SM-MIB::usmNoPrivProtocol,,,,,,No Privacy Protocol.
.1.3.6.1.6.3.10.1.2.2,SNMP-USER-BASED-SM-MIB::usmDESPrivProtocol,,,,,,The CBC-DES Symmetric Encryption Protocol.
.1.3.6.1.6.3.10.1.2.4,SNMP-USM-AES-MIB::usmAesCfb128Protocol,,,,,,The CFB128-AES-128 Privacy Protocol.
.1.3.6.1.6.3.10.2,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBObjects,,,,,,
.1.3.6.1.6.3.10.2.1,SNMP-FRAMEWORK-MIB::snmpEngine,,,,,,
.1.3.6.1.6.3.10.2.1.1,SNMP-FRAMEWORK-MIB::snmpEngineID,OCTET,read-only,,current,,An SNMP engine's administratively-unique identifier. This information SHOULD be stored in non-volatile storage so that it remains constant across re-initializations of the SNMP engine. 
.1.3.6.1.6.3.10.2.1.2,SNMP-FRAMEWORK-MIB::snmpEngineBoots,INTEGER,read-only,,current,,The number of times that the SNMP engine has (re-)initialized itself since snmpEngineID was last configured. 
.1.3.6.1.6.3.10.2.1.3,SNMP-FRAMEWORK-MIB::snmpEngineTime,INTEGER,read-only,,current,,The number of seconds since the value of the snmpEngineBoots object last changed. When incrementing this object's value would cause it to exceed its maximum, snmpEngineBoots is incremented as if a re-initialization had occurred, and this object's value consequently reverts to zero. 
.1.3.6.1.6.3.10.2.1.4,SNMP-FRAMEWORK-MIB::snmpEngineMaxMessageSize,INTEGER,read-only,,current,,The maximum length in octets of an SNMP message which this SNMP engine can send or receive and process, determined as the minimum of the maximum message size values supported among all of the transports available to and supported by the engine. 
.1.3.6.1.6.3.10.3,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBConformance,,,,,,
.1.3.6.1.6.3.10.3.1,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliances,,,,,,
.1.3.6.1.6.3.10.3.1.1,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance,,,,,,The compliance statement for SNMP engines which implement the SNMP Management Framework MIB. 
.1.3.6.1.6.3.10.3.2,SNMP-FRAMEWORK-MIB::snmpFrameworkMIBGroups,,,,,,
.1.3.6.1.6.3.10.3.2.1,SNMP-FRAMEWORK-MIB::snmpEngineGroup,,,,,,A collection of objects for identifying and determining the configuration and current timeliness values of an SNMP engine. 
.1.3.6.1.6.3.11,SNMP-MPD-MIB::snmpMPDMIB,,,,,,The MIB for Message Processing and Dispatching Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3412; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.11.1,SNMP-MPD-MIB::snmpMPDAdmin,,,,,,
.1.3.6.1.6.3.11.2,SNMP-MPD-MIB::snmpMPDMIBObjects,,,,,,
.1.3.6.1.6.3.11.2.1,SNMP-MPD-MIB::snmpMPDStats,,,,,,
.1.3.6.1.6.3.11.2.1.1,SNMP-MPD-MIB::snmpUnknownSecurityModels,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they referenced a securityModel that was not known to or supported by the SNMP engine. 
.1.3.6.1.6.3.11.2.1.2,SNMP-MPD-MIB::snmpInvalidMsgs,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because there were invalid or inconsistent components in the SNMP message. 
.1.3.6.1.6.3.11.2.1.3,SNMP-MPD-MIB::snmpUnknownPDUHandlers,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because the PDU contained in the packet could not be passed to an application responsible for handling the pduType, e.g. no SNMP application had registered for the proper combination of the contextEngineID and the pduType. 
.1.3.6.1.6.3.11.3,SNMP-MPD-MIB::snmpMPDMIBConformance,,,,,,
.1.3.6.1.6.3.11.3.1,SNMP-MPD-MIB::snmpMPDMIBCompliances,,,,,,
.1.3.6.1.6.3.11.3.1.1,SNMP-MPD-MIB::snmpMPDCompliance,,,,,,The compliance statement for SNMP entities which implement the SNMP-MPD-MIB. 
.1.3.6.1.6.3.11.3.2,SNMP-MPD-MIB::snmpMPDMIBGroups,,,,,,
.1.3.6.1.6.3.11.3.2.1,SNMP-MPD-MIB::snmpMPDGroup,,,,,,A collection of objects providing for remote monitoring of the SNMP Message Processing and Dispatching process. 
.1.3.6.1.6.3.12,SNMP-TARGET-MIB::snmpTargetMIB,,,,,,This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of SNMP messages. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3413; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.12.1,SNMP-TARGET-MIB::snmpTargetObjects,,,,,,
.1.3.6.1.6.3.12.1.1,SNMP-TARGET-MIB::snmpTargetSpinLock,INTEGER,read-write,,current,,This object is used to facilitate modification of table entries in the SNMP-TARGET-MIB module by multiple managers. In particular, it is useful when modifying the value of the snmpTargetAddrTagList object. The procedure for modifying the snmpTargetAddrTagList object is as follows: 1. Retrieve the value of snmpTargetSpinLock and of snmpTargetAddrTagList. 2. Generate a new value for snmpTargetAddrTagList. 3. Set the value of snmpTargetSpinLock to the retrieved value, and the value of snmpTargetAddrTagList to the new value. If the set fails for the snmpTargetSpinLock object, go back to step 1.
.1.3.6.1.6.3.12.1.2,SNMP-TARGET-MIB::snmpTargetAddrTable,,not-accessible,,current,,A table of transport addresses to be used in the generation of SNMP messages.
.1.3.6.1.6.3.12.1.2.1,SNMP-TARGET-MIB::snmpTargetAddrEntry,,not-accessible,IMPLIEDsnmpTargetAddrName,current,,A transport address to be used in the generation of SNMP operations. Entries in the snmpTargetAddrTable are created and deleted using the snmpTargetAddrRowStatus object.
.1.3.6.1.6.3.12.1.2.1.1,SNMP-TARGET-MIB::snmpTargetAddrName,OCTET,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this snmpTargetAddrEntry.
.1.3.6.1.6.3.12.1.2.1.2,SNMP-TARGET-MIB::snmpTargetAddrTDomain,OBJECT,read-create,,current,,This object indicates the transport type of the address contained in the snmpTargetAddrTAddress object.
.1.3.6.1.6.3.12.1.2.1.3,SNMP-TARGET-MIB::snmpTargetAddrTAddress,OCTET,read-create,,current,,This object contains a transport address. The format of this address depends on the value of the snmpTargetAddrTDomain object.
.1.3.6.1.6.3.12.1.2.1.4,SNMP-TARGET-MIB::snmpTargetAddrTimeout,INTEGER,read-create,,current,,This object should reflect the expected maximum round trip time for communicating with the transport address defined by this row. When a message is sent to this address, and a response (if one is expected) is not received within this time period, an implementation may assume that the response will not be delivered. Note that the time interval that an application waits for a response may actually be derived from the value of this object. The method for deriving the actual time interval is implementation dependent. One such method is to derive the expected round trip time based on a particular retransmission algorithm and on the number of timeouts which have occurred. The type of message may also be considered when deriving expected round trip times for retransmissions. For example, if a message is being sent with a securityLevel that indicates both authentication and privacy, the derived value may be increased to compensate for extra processing time spent during authentication and encryption processing.
.1.3.6.1.6.3.12.1.2.1.5,SNMP-TARGET-MIB::snmpTargetAddrRetryCount,Integer32,read-create,,current,,This object specifies a default number of retries to be attempted when a response is not received for a generated message. An application may provide its own retry count, in which case the value of this object is ignored.
.1.3.6.1.6.3.12.1.2.1.6,SNMP-TARGET-MIB::snmpTargetAddrTagList,OCTET,read-create,,current,,This object contains a list of tag values which are used to select target addresses for a particular operation.
.1.3.6.1.6.3.12.1.2.1.7,SNMP-TARGET-MIB::snmpTargetAddrParams,OCTET,read-create,,current,,The value of this object identifies an entry in the snmpTargetParamsTable. The identified entry contains SNMP parameters to be used when generating messages to be sent to this transport address.
.1.3.6.1.6.3.12.1.2.1.8,SNMP-TARGET-MIB::snmpTargetAddrStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.6.3.12.1.2.1.9,SNMP-TARGET-MIB::snmpTargetAddrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTargetAddrRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding instances of snmpTargetAddrTDomain, snmpTargetAddrTAddress, and snmpTargetAddrParams have all been set. The following objects may not be modified while the value of this object is active(1): - snmpTargetAddrTDomain - snmpTargetAddrTAddress An attempt to set these objects while the value of snmpTargetAddrRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.6.3.12.1.3,SNMP-TARGET-MIB::snmpTargetParamsTable,,not-accessible,,current,,A table of SNMP target information to be used in the generation of SNMP messages.
.1.3.6.1.6.3.12.1.3.1,SNMP-TARGET-MIB::snmpTargetParamsEntry,,not-accessible,IMPLIEDsnmpTargetParamsName,current,,A set of SNMP target information. Entries in the snmpTargetParamsTable are created and deleted using the snmpTargetParamsRowStatus object.
.1.3.6.1.6.3.12.1.3.1.1,SNMP-TARGET-MIB::snmpTargetParamsName,OCTET,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this snmpTargetParamsEntry.
.1.3.6.1.6.3.12.1.3.1.2,SNMP-TARGET-MIB::snmpTargetParamsMPModel,INTEGER,read-create,,current,,The Message Processing Model to be used when generating SNMP messages using this entry.
.1.3.6.1.6.3.12.1.3.1.3,SNMP-TARGET-MIB::snmpTargetParamsSecurityModel,INTEGER,read-create,,current,,The Security Model to be used when generating SNMP messages using this entry. An implementation may choose to return an inconsistentValue error if an attempt is made to set this variable to a value for a security model which the implementation does not support.
.1.3.6.1.6.3.12.1.3.1.4,SNMP-TARGET-MIB::snmpTargetParamsSecurityName,OCTET,read-create,,current,,The securityName which identifies the Principal on whose behalf SNMP messages will be generated using this entry.
.1.3.6.1.6.3.12.1.3.1.5,SNMP-TARGET-MIB::snmpTargetParamsSecurityLevel,INTEGER,read-create,,current,noAuthNoPriv(1):authNoPriv(2):authPriv(3),The Level of Security to be used when generating SNMP messages using this entry.
.1.3.6.1.6.3.12.1.3.1.6,SNMP-TARGET-MIB::snmpTargetParamsStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.6.3.12.1.3.1.7,SNMP-TARGET-MIB::snmpTargetParamsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpTargetParamsRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding snmpTargetParamsMPModel, snmpTargetParamsSecurityModel, snmpTargetParamsSecurityName, and snmpTargetParamsSecurityLevel have all been set. The following objects may not be modified while the value of this object is active(1): - snmpTargetParamsMPModel - snmpTargetParamsSecurityModel - snmpTargetParamsSecurityName - snmpTargetParamsSecurityLevel An attempt to set these objects while the value of snmpTargetParamsRowStatus is active(1) will result in an inconsistentValue error.
.1.3.6.1.6.3.12.1.4,SNMP-TARGET-MIB::snmpUnavailableContexts,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unavailable.
.1.3.6.1.6.3.12.1.5,SNMP-TARGET-MIB::snmpUnknownContexts,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because the context contained in the message was unknown.
.1.3.6.1.6.3.12.3,SNMP-TARGET-MIB::snmpTargetConformance,,,,,,
.1.3.6.1.6.3.12.3.1,SNMP-TARGET-MIB::snmpTargetCompliances,,,,,,
.1.3.6.1.6.3.12.3.1.1,SNMP-TARGET-MIB::snmpTargetCommandResponderCompliance,,,,,,The compliance statement for SNMP entities which include a command responder application.
.1.3.6.1.6.3.12.3.2,SNMP-TARGET-MIB::snmpTargetGroups,,,,,,
.1.3.6.1.6.3.12.3.2.1,SNMP-TARGET-MIB::snmpTargetBasicGroup,,,,,,A collection of objects providing basic remote configuration of management targets.
.1.3.6.1.6.3.12.3.2.2,SNMP-TARGET-MIB::snmpTargetResponseGroup,,,,,,A collection of objects providing remote configuration of management targets for applications which generate SNMP messages for which a response message would be expected.
.1.3.6.1.6.3.12.3.2.3,SNMP-TARGET-MIB::snmpTargetCommandResponderGroup,,,,,,A collection of objects required for command responder applications, used for counting error conditions.
.1.3.6.1.6.3.13,SNMP-NOTIFICATION-MIB::snmpNotificationMIB,,,,,,This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of notifications. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3413; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.13.1,SNMP-NOTIFICATION-MIB::snmpNotifyObjects,,,,,,
.1.3.6.1.6.3.13.1.1,SNMP-NOTIFICATION-MIB::snmpNotifyTable,,not-accessible,,current,,This table is used to select management targets which should receive notifications, as well as the type of notification which should be sent to each selected management target.
.1.3.6.1.6.3.13.1.1.1,SNMP-NOTIFICATION-MIB::snmpNotifyEntry,,not-accessible,IMPLIEDsnmpNotifyName,current,,An entry in this table selects a set of management targets which should receive notifications, as well as the type of notification which should be sent to each selected management target. Entries in the snmpNotifyTable are created and deleted using the snmpNotifyRowStatus object.
.1.3.6.1.6.3.13.1.1.1.1,SNMP-NOTIFICATION-MIB::snmpNotifyName,OCTET,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this snmpNotifyEntry.
.1.3.6.1.6.3.13.1.1.1.2,SNMP-NOTIFICATION-MIB::snmpNotifyTag,OCTET,read-create,,current,,This object contains a single tag value which is used to select entries in the snmpTargetAddrTable. Any entry in the snmpTargetAddrTable which contains a tag value which is equal to the value of an instance of this object is selected. If this object contains a value of zero length, no entries are selected.
.1.3.6.1.6.3.13.1.1.1.3,SNMP-NOTIFICATION-MIB::snmpNotifyType,INTEGER,read-create,,current,trap(1):inform(2),This object determines the type of notification to be generated for entries in the snmpTargetAddrTable selected by the corresponding instance of snmpNotifyTag. This value is only used when generating notifications, and is ignored when using the snmpTargetAddrTable for other purposes. If the value of this object is trap(1), then any messages generated for selected rows will contain Unconfirmed-Class PDUs. If the value of this object is inform(2), then any messages generated for selected rows will contain Confirmed-Class PDUs. Note that if an SNMP entity only supports generation of Unconfirmed-Class PDUs (and not Confirmed-Class PDUs), then this object may be read-only.
.1.3.6.1.6.3.13.1.1.1.4,SNMP-NOTIFICATION-MIB::snmpNotifyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.6.3.13.1.1.1.5,SNMP-NOTIFICATION-MIB::snmpNotifyRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5).
.1.3.6.1.6.3.13.1.2,SNMP-NOTIFICATION-MIB::snmpNotifyFilterProfileTable,,not-accessible,,current,,This table is used to associate a notification filter profile with a particular set of target parameters.
.1.3.6.1.6.3.13.1.2.1,SNMP-NOTIFICATION-MIB::snmpNotifyFilterProfileEntry,,not-accessible,IMPLIEDsnmpTargetParamsName,current,,An entry in this table indicates the name of the filter profile to be used when generating notifications using the corresponding entry in the snmpTargetParamsTable. Entries in the snmpNotifyFilterProfileTable are created and deleted using the snmpNotifyFilterProfileRowStatus object.
.1.3.6.1.6.3.13.1.2.1.1,SNMP-NOTIFICATION-MIB::snmpNotifyFilterProfileName,OCTET,read-create,,current,,The name of the filter profile to be used when generating notifications using the corresponding entry in the snmpTargetAddrTable.
.1.3.6.1.6.3.13.1.2.1.2,SNMP-NOTIFICATION-MIB::snmpNotifyFilterProfileStorType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.6.3.13.1.2.1.3,SNMP-NOTIFICATION-MIB::snmpNotifyFilterProfileRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpNotifyFilterProfileRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding instance of snmpNotifyFilterProfileName has been set.
.1.3.6.1.6.3.13.1.3,SNMP-NOTIFICATION-MIB::snmpNotifyFilterTable,,not-accessible,,current,,The table of filter profiles. Filter profiles are used to determine whether particular management targets should receive particular notifications. When a notification is generated, it must be compared with the filters associated with each management target which is configured to receive notifications, in order to determine whether it may be sent to each such management target. A more complete discussion of notification filtering can be found in section 6. of [SNMP-APPL].
.1.3.6.1.6.3.13.1.3.1,SNMP-NOTIFICATION-MIB::snmpNotifyFilterEntry,,not-accessible,snmpNotifyFilterProfileName:IMPLIEDsnmpNotifyFilterSubtree,current,,An element of a filter profile. Entries in the snmpNotifyFilterTable are created and deleted using the snmpNotifyFilterRowStatus object.
.1.3.6.1.6.3.13.1.3.1.1,SNMP-NOTIFICATION-MIB::snmpNotifyFilterSubtree,OBJECT,not-accessible,,current,,The MIB subtree which, when combined with the corresponding instance of snmpNotifyFilterMask, defines a family of subtrees which are included in or excluded from the filter profile.
.1.3.6.1.6.3.13.1.3.1.2,SNMP-NOTIFICATION-MIB::snmpNotifyFilterMask,OCTET,read-create,,current,,The bit mask which, in combination with the corresponding instance of snmpNotifyFilterSubtree, defines a family of subtrees which are included in or excluded from the filter profile. Each bit of this bit mask corresponds to a sub-identifier of snmpNotifyFilterSubtree, with the most significant bit of the i-th octet of this octet string value (extended if necessary, see below) corresponding to the (8*i - 7)-th sub-identifier, and the least significant bit of the i-th octet of this octet string corresponding to the (8*i)-th sub-identifier, where i is in the range 1 through 16. Each bit of this bit mask specifies whether or not the corresponding sub-identifiers must match when determining if an OBJECT IDENTIFIER matches this family of filter subtrees; a '1' indicates that an exact match must occur; a '0' indicates 'wild card', i.e., any sub-identifier value matches. Thus, the OBJECT IDENTIFIER X of an object instance is contained in a family of filter subtrees if, for each sub-identifier of the value of snmpNotifyFilterSubtree, either: the i-th bit of snmpNotifyFilterMask is 0, or the i-th sub-identifier of X is equal to the i-th sub-identifier of the value of snmpNotifyFilterSubtree. If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of snmpNotifyFilterSubtree, then the bit mask is extended with 1's to be the required length. Note that when the value of this object is the zero-length string, this extension rule results in a mask of all-1's being used (i.e., no 'wild card'), and the family of filter subtrees is the one subtree uniquely identified by the corresponding instance of snmpNotifyFilterSubtree.
.1.3.6.1.6.3.13.1.3.1.3,SNMP-NOTIFICATION-MIB::snmpNotifyFilterType,INTEGER,read-create,,current,included(1):excluded(2),This object indicates whether the family of filter subtrees defined by this entry are included in or excluded from a filter. A more detailed discussion of the use of this object can be found in section 6. of [SNMP-APPL].
.1.3.6.1.6.3.13.1.3.1.4,SNMP-NOTIFICATION-MIB::snmpNotifyFilterStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.6.3.13.1.3.1.5,SNMP-NOTIFICATION-MIB::snmpNotifyFilterRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5).
.1.3.6.1.6.3.13.3,SNMP-NOTIFICATION-MIB::snmpNotifyConformance,,,,,,
.1.3.6.1.6.3.13.3.1,SNMP-NOTIFICATION-MIB::snmpNotifyCompliances,,,,,,
.1.3.6.1.6.3.13.3.1.1,SNMP-NOTIFICATION-MIB::snmpNotifyBasicCompliance,,,,,,The compliance statement for minimal SNMP entities which implement only SNMP Unconfirmed-Class notifications and read-create operations on only the snmpTargetAddrTable.
.1.3.6.1.6.3.13.3.1.2,SNMP-NOTIFICATION-MIB::snmpNotifyBasicFiltersCompliance,,,,,,The compliance statement for SNMP entities which implement SNMP Unconfirmed-Class notifications with filtering, and read-create operations on all related tables.
.1.3.6.1.6.3.13.3.1.3,SNMP-NOTIFICATION-MIB::snmpNotifyFullCompliance,,,,,,The compliance statement for SNMP entities which either implement only SNMP Confirmed-Class notifications, or both SNMP Unconfirmed-Class and Confirmed-Class notifications, plus filtering and read-create operations on all related tables.
.1.3.6.1.6.3.13.3.2,SNMP-NOTIFICATION-MIB::snmpNotifyGroups,,,,,,
.1.3.6.1.6.3.13.3.2.1,SNMP-NOTIFICATION-MIB::snmpNotifyGroup,,,,,,A collection of objects for selecting which management targets are used for generating notifications, and the type of notification to be generated for each selected management target.
.1.3.6.1.6.3.13.3.2.2,SNMP-NOTIFICATION-MIB::snmpNotifyFilterGroup,,,,,,A collection of objects providing remote configuration of notification filters.
.1.3.6.1.6.3.14,SNMP-PROXY-MIB::snmpProxyMIB,,,,,,This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by a proxy forwarding application. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3413; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.14.1,SNMP-PROXY-MIB::snmpProxyObjects,,,,,,
.1.3.6.1.6.3.14.1.2,SNMP-PROXY-MIB::snmpProxyTable,,not-accessible,,current,,The table of translation parameters used by proxy forwarder applications for forwarding SNMP messages.
.1.3.6.1.6.3.14.1.2.1,SNMP-PROXY-MIB::snmpProxyEntry,,not-accessible,IMPLIEDsnmpProxyName,current,,A set of translation parameters used by a proxy forwarder application for forwarding SNMP messages. Entries in the snmpProxyTable are created and deleted using the snmpProxyRowStatus object.
.1.3.6.1.6.3.14.1.2.1.1,SNMP-PROXY-MIB::snmpProxyName,OCTET,not-accessible,,current,,The locally arbitrary, but unique identifier associated with this snmpProxyEntry.
.1.3.6.1.6.3.14.1.2.1.2,SNMP-PROXY-MIB::snmpProxyType,INTEGER,read-create,,current,read(1):write(2):trap(3):inform(4),The type of message that may be forwarded using the translation parameters defined by this entry.
.1.3.6.1.6.3.14.1.2.1.3,SNMP-PROXY-MIB::snmpProxyContextEngineID,OCTET,read-create,,current,,The contextEngineID contained in messages that may be forwarded using the translation parameters defined by this entry.
.1.3.6.1.6.3.14.1.2.1.4,SNMP-PROXY-MIB::snmpProxyContextName,OCTET,read-create,,current,,The contextName contained in messages that may be forwarded using the translation parameters defined by this entry. This object is optional, and if not supported, the contextName contained in a message is ignored when selecting an entry in the snmpProxyTable.
.1.3.6.1.6.3.14.1.2.1.5,SNMP-PROXY-MIB::snmpProxyTargetParamsIn,OCTET,read-create,,current,,This object selects an entry in the snmpTargetParamsTable. The selected entry is used to determine which row of the snmpProxyTable to use for forwarding received messages.
.1.3.6.1.6.3.14.1.2.1.6,SNMP-PROXY-MIB::snmpProxySingleTargetOut,OCTET,read-create,,current,,This object selects a management target defined in the snmpTargetAddrTable (in the SNMP-TARGET-MIB). The selected target is defined by an entry in the snmpTargetAddrTable whose index value (snmpTargetAddrName) is equal to this object. This object is only used when selection of a single target is required (i.e. when forwarding an incoming read or write request).
.1.3.6.1.6.3.14.1.2.1.7,SNMP-PROXY-MIB::snmpProxyMultipleTargetOut,OCTET,read-create,,current,,This object selects a set of management targets defined in the snmpTargetAddrTable (in the SNMP-TARGET-MIB). This object is only used when selection of multiple targets is required (i.e. when forwarding an incoming notification).
.1.3.6.1.6.3.14.1.2.1.8,SNMP-PROXY-MIB::snmpProxyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type of this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
.1.3.6.1.6.3.14.1.2.1.9,SNMP-PROXY-MIB::snmpProxyRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). The following objects may not be modified while the value of this object is active(1): - snmpProxyType - snmpProxyContextEngineID - snmpProxyContextName - snmpProxyTargetParamsIn - snmpProxySingleTargetOut - snmpProxyMultipleTargetOut
.1.3.6.1.6.3.14.3,SNMP-PROXY-MIB::snmpProxyConformance,,,,,,
.1.3.6.1.6.3.14.3.1,SNMP-PROXY-MIB::snmpProxyCompliances,,,,,,
.1.3.6.1.6.3.14.3.1.1,SNMP-PROXY-MIB::snmpProxyCompliance,,,,,,The compliance statement for SNMP entities which include a proxy forwarding application.
.1.3.6.1.6.3.14.3.2,SNMP-PROXY-MIB::snmpProxyGroups,,,,,,
.1.3.6.1.6.3.14.3.2.3,SNMP-PROXY-MIB::snmpProxyGroup,,,,,,A collection of objects providing remote configuration of management target translation parameters for use by proxy forwarder applications.
.1.3.6.1.6.3.15,SNMP-USER-BASED-SM-MIB::snmpUsmMIB,,,,,,The management information definitions for the SNMP User-based Security Model. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3414; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.15.1,SNMP-USER-BASED-SM-MIB::usmMIBObjects,,,,,,
.1.3.6.1.6.3.15.1.1,SNMP-USER-BASED-SM-MIB::usmStats,,,,,,
.1.3.6.1.6.3.15.1.1.1,SNMP-USER-BASED-SM-MIB::usmStatsUnsupportedSecLevels,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they requested a securityLevel that was unknown to the SNMP engine or otherwise unavailable. 
.1.3.6.1.6.3.15.1.1.2,SNMP-USER-BASED-SM-MIB::usmStatsNotInTimeWindows,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they appeared outside of the authoritative SNMP engine's window. 
.1.3.6.1.6.3.15.1.1.3,SNMP-USER-BASED-SM-MIB::usmStatsUnknownUserNames,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they referenced a user that was not known to the SNMP engine. 
.1.3.6.1.6.3.15.1.1.4,SNMP-USER-BASED-SM-MIB::usmStatsUnknownEngineIDs,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they referenced an snmpEngineID that was not known to the SNMP engine. 
.1.3.6.1.6.3.15.1.1.5,SNMP-USER-BASED-SM-MIB::usmStatsWrongDigests,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they didn't contain the expected digest value. 
.1.3.6.1.6.3.15.1.1.6,SNMP-USER-BASED-SM-MIB::usmStatsDecryptionErrors,Counter32,read-only,,current,,The total number of packets received by the SNMP engine which were dropped because they could not be decrypted. 
.1.3.6.1.6.3.15.1.2,SNMP-USER-BASED-SM-MIB::usmUser,,,,,,
.1.3.6.1.6.3.15.1.2.1,SNMP-USER-BASED-SM-MIB::usmUserSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow several cooperating Command Generator Applications to coordinate their use of facilities to alter secrets in the usmUserTable. 
.1.3.6.1.6.3.15.1.2.2,SNMP-USER-BASED-SM-MIB::usmUserTable,,not-accessible,,current,,The table of users configured in the SNMP engine's Local Configuration Datastore (LCD). To create a new user (i.e., to instantiate a new conceptual row in this table), it is recommended to follow this procedure: 1) GET(usmUserSpinLock.0) and save in sValue. 2) SET(usmUserSpinLock.0=sValue, usmUserCloneFrom=templateUser, usmUserStatus=createAndWait) You should use a template user to clone from which has the proper auth/priv protocol defined. If the new user is to use privacy: 3) generate the keyChange value based on the secret privKey of the clone-from user and the secret key to be used for the new user. Let us call this pkcValue. 4) GET(usmUserSpinLock.0) and save in sValue. 5) SET(usmUserSpinLock.0=sValue, usmUserPrivKeyChange=pkcValue usmUserPublic=randomValue1) 6) GET(usmUserPulic) and check it has randomValue1. If not, repeat steps 4-6. If the new user will never use privacy: 7) SET(usmUserPrivProtocol=usmNoPrivProtocol) If the new user is to use authentication: 8) generate the keyChange value based on the secret authKey of the clone-from user and the secret key to be used for the new user. Let us call this akcValue. 9) GET(usmUserSpinLock.0) and save in sValue. 10) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=akcValue usmUserPublic=randomValue2) 11) GET(usmUserPulic) and check it has randomValue2. If not, repeat steps 9-11. If the new user will never use authentication: 12) SET(usmUserAuthProtocol=usmNoAuthProtocol) Finally, activate the new user: 13) SET(usmUserStatus=active) The new user should now be available and ready to be used for SNMPv3 communication. Note however that access to MIB data must be provided via configuration of the SNMP-VIEW-BASED-ACM-MIB. The use of usmUserSpinlock is to avoid conflicts with another SNMP command generator application which may also be acting on the usmUserTable. 
.1.3.6.1.6.3.15.1.2.2.1,SNMP-USER-BASED-SM-MIB::usmUserEntry,,not-accessible,usmUserEngineID:usmUserName,current,,A user configured in the SNMP engine's Local Configuration Datastore (LCD) for the User-based Security Model. 
.1.3.6.1.6.3.15.1.2.2.1.1,SNMP-USER-BASED-SM-MIB::usmUserEngineID,OCTET,not-accessible,,current,,An SNMP engine's administratively-unique identifier. In a simple agent, this value is always that agent's own snmpEngineID value. The value can also take the value of the snmpEngineID of a remote SNMP engine with which this user can communicate. 
.1.3.6.1.6.3.15.1.2.2.1.2,SNMP-USER-BASED-SM-MIB::usmUserName,OCTET,not-accessible,,current,,A human readable string representing the name of the user. This is the (User-based Security) Model dependent security ID. 
.1.3.6.1.6.3.15.1.2.2.1.3,SNMP-USER-BASED-SM-MIB::usmUserSecurityName,OCTET,read-only,,current,,A human readable string representing the user in Security Model independent format. The default transformation of the User-based Security Model dependent security ID to the securityName and vice versa is the identity function so that the securityName is the same as the userName. 
.1.3.6.1.6.3.15.1.2.2.1.4,SNMP-USER-BASED-SM-MIB::usmUserCloneFrom,OBJECT,read-create,,current,,A pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user. When a new user is created (i.e., a new conceptual row is instantiated in this table), the privacy and authentication parameters of the new user must be cloned from its clone-from user. These parameters are: - authentication protocol (usmUserAuthProtocol) - privacy protocol (usmUserPrivProtocol) They will be copied regardless of what the current value is. Cloning also causes the initial values of the secret authentication key (authKey) and the secret encryption key (privKey) of the new user to be set to the same values as the corresponding secrets of the clone-from user to allow the KeyChange process to occur as required during user creation. The first time an instance of this object is set by a management operation (either at or after its instantiation), the cloning process is invoked. Subsequent writes are successful but invoke no action to be taken by the receiver. The cloning process fails with an 'inconsistentName' error if the conceptual row representing the clone-from user does not exist or is not in an active state when the cloning process is invoked. When this object is read, the ZeroDotZero OID is returned. 
.1.3.6.1.6.3.15.1.2.2.1.5,SNMP-USER-BASED-SM-MIB::usmUserAuthProtocol,OBJECT,read-create,,current,,An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be authenticated, and if so, the type of authentication protocol which is used. An instance of this object is created concurrently with the creation of any other object instance for the same user (i.e., as part of the processing of the set operation which creates the first object instance in the same conceptual row). If an initial set operation (i.e. at row creation time) tries to set a value for an unknown or unsupported protocol, then a 'wrongValue' error must be returned. The value will be overwritten/set when a set operation is performed on the corresponding instance of usmUserCloneFrom. Once instantiated, the value of such an instance of this object can only be changed via a set operation to the value of the usmNoAuthProtocol. If a set operation tries to change the value of an existing instance of this object to any value other than usmNoAuthProtocol, then an 'inconsistentValue' error must be returned. If a set operation tries to set the value to the usmNoAuthProtocol while the usmUserPrivProtocol value in the same row is not equal to usmNoPrivProtocol, then an 'inconsistentValue' error must be returned. That means that an SNMP command generator application must first ensure that the usmUserPrivProtocol is set to the usmNoPrivProtocol value before it can set the usmUserAuthProtocol value to usmNoAuthProtocol. 
.1.3.6.1.6.3.15.1.2.2.1.6,SNMP-USER-BASED-SM-MIB::usmUserAuthKeyChange,OCTET,read-create,,current,,An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. The associated protocol is the usmUserAuthProtocol. The associated secret key is the user's secret authentication key (authKey). The associated hash algorithm is the algorithm used by the user's usmUserAuthProtocol. When creating a new user, it is an 'inconsistentName' error for a set operation to refer to this object unless it is previously or concurrently initialized through a set operation on the corresponding instance of usmUserCloneFrom. When the value of the corresponding usmUserAuthProtocol is usmNoAuthProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. The recommended way to do a key change is as follows: 1) GET(usmUserSpinLock.0) and save in sValue. 2) generate the keyChange value based on the old (existing) secret key and the new secret key, let us call this kcValue. If you do the key change on behalf of another user: 3) SET(usmUserSpinLock.0=sValue, usmUserAuthKeyChange=kcValue usmUserPublic=randomValue) If you do the key change for yourself: 4) SET(usmUserSpinLock.0=sValue, usmUserOwnAuthKeyChange=kcValue usmUserPublic=randomValue) If you get a response with error-status of noError, then the SET succeeded and the new key is active. If you do not get a response, then you can issue a GET(usmUserPublic) and check if the value is equal to the randomValue you did send in the SET. If so, then the key change succeeded and the new key is active (probably the response got lost). If not, then the SET request probably never reached the target and so you can start over with the procedure above. 
.1.3.6.1.6.3.15.1.2.2.1.7,SNMP-USER-BASED-SM-MIB::usmUserOwnAuthKeyChange,OCTET,read-create,,current,,Behaves exactly as usmUserAuthKeyChange, with one notable difference: in order for the set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. In addition, the USM security model must be used for this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret authentication key (authKey). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned. 
.1.3.6.1.6.3.15.1.2.2.1.8,SNMP-USER-BASED-SM-MIB::usmUserPrivProtocol,OBJECT,read-create,,current,,An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be protected from disclosure, and if so, the type of privacy protocol which is used. An instance of this object is created concurrently with the creation of any other object instance for the same user (i.e., as part of the processing of the set operation which creates the first object instance in the same conceptual row). If an initial set operation (i.e. at row creation time) tries to set a value for an unknown or unsupported protocol, then a 'wrongValue' error must be returned. The value will be overwritten/set when a set operation is performed on the corresponding instance of usmUserCloneFrom. Once instantiated, the value of such an instance of this object can only be changed via a set operation to the value of the usmNoPrivProtocol. If a set operation tries to change the value of an existing instance of this object to any value other than usmNoPrivProtocol, then an 'inconsistentValue' error must be returned. Note that if any privacy protocol is used, then you must also use an authentication protocol. In other words, if usmUserPrivProtocol is set to anything else than usmNoPrivProtocol, then the corresponding instance of usmUserAuthProtocol cannot have a value of usmNoAuthProtocol. If it does, then an 'inconsistentValue' error must be returned. 
.1.3.6.1.6.3.15.1.2.2.1.9,SNMP-USER-BASED-SM-MIB::usmUserPrivKeyChange,OCTET,read-create,,current,,An object, which when modified, causes the secret encryption key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. The associated protocol is the usmUserPrivProtocol. The associated secret key is the user's secret privacy key (privKey). The associated hash algorithm is the algorithm used by the user's usmUserAuthProtocol. When creating a new user, it is an 'inconsistentName' error for a set operation to refer to this object unless it is previously or concurrently initialized through a set operation on the corresponding instance of usmUserCloneFrom. When the value of the corresponding usmUserPrivProtocol is usmNoPrivProtocol, then a set is successful, but effectively is a no-op. When this object is read, the zero-length (empty) string is returned. See the description clause of usmUserAuthKeyChange for a recommended procedure to do a key change. 
.1.3.6.1.6.3.15.1.2.2.1.10,SNMP-USER-BASED-SM-MIB::usmUserOwnPrivKeyChange,OCTET,read-create,,current,,Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. In addition, the USM security model must be used for this operation. The idea here is that access to this column can be public, since it will only allow a user to change his own secret privacy key (privKey). Note that this can only be done once the row is active. When a set is received and the usmUserName of the requester is not the same as the umsUserName that indexes the row which is targeted by this operation, then a 'noAccess' error must be returned. When a set is received and the security model in use is not USM, then a 'noAccess' error must be returned. 
.1.3.6.1.6.3.15.1.2.2.1.11,SNMP-USER-BASED-SM-MIB::usmUserPublic,OCTET,read-create,,current,,A publicly-readable value which can be written as part of the procedure for changing a user's secret authentication and/or privacy key, and later read to determine whether the change of the secret was effected. 
.1.3.6.1.6.3.15.1.2.2.1.12,SNMP-USER-BASED-SM-MIB::usmUserStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' must allow write-access at a minimum to: - usmUserAuthKeyChange, usmUserOwnAuthKeyChange and usmUserPublic for a user who employs authentication, and - usmUserPrivKeyChange, usmUserOwnPrivKeyChange and usmUserPublic for a user who employs privacy. Note that any user who employs authentication or privacy must allow its secret(s) to be updated and thus cannot be 'readOnly'. If an initial set operation tries to set the value to 'readOnly' for a user who employs authentication or privacy, then an 'inconsistentValue' error must be returned. Note that if the value has been previously set (implicit or explicit) to any value, then the rules as defined in the StorageType Textual Convention apply. It is an implementation issue to decide if a SET for a readOnly or permanent row is accepted at all. In some contexts this may make sense, in others it may not. If a SET for a readOnly or permanent row is not accepted at all, then a 'wrongValue' error must be returned. 
.1.3.6.1.6.3.15.1.2.2.1.13,SNMP-USER-BASED-SM-MIB::usmUserStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the usmUserStatus column is 'notReady'. In particular, a newly created row for a user who employs authentication, cannot be made active until the corresponding usmUserCloneFrom and usmUserAuthKeyChange have been set. Further, a newly created row for a user who also employs privacy, cannot be made active until the usmUserPrivKeyChange has been set. The RowStatus TC [RFC2579] requires that thisclause states under which circumstances other objects in this row can be modified: The value of this object has no effect on whether other objects in this conceptual row can be modified, except for usmUserOwnAuthKeyChange and usmUserOwnPrivKeyChange. For these 2 objects, the value of usmUserStatus MUST be active. 
.1.3.6.1.6.3.15.2,SNMP-USER-BASED-SM-MIB::usmMIBConformance,,,,,,
.1.3.6.1.6.3.15.2.1,SNMP-USER-BASED-SM-MIB::usmMIBCompliances,,,,,,
.1.3.6.1.6.3.15.2.1.1,SNMP-USER-BASED-SM-MIB::usmMIBCompliance,,,,,,The compliance statement for SNMP engines which implement the SNMP-USER-BASED-SM-MIB. 
.1.3.6.1.6.3.15.2.2,SNMP-USER-BASED-SM-MIB::usmMIBGroups,,,,,,
.1.3.6.1.6.3.15.2.2.1,SNMP-USER-BASED-SM-MIB::usmMIBBasicGroup,,,,,,A collection of objects providing for configuration of an SNMP engine which implements the SNMP User-based Security Model. 
.1.3.6.1.6.3.16,SNMP-VIEW-BASED-ACM-MIB::snmpVacmMIB,,,,,,The management information definitions for the View-based Access Control Model for SNMP. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3415; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.16.1,SNMP-VIEW-BASED-ACM-MIB::vacmMIBObjects,,,,,,
.1.3.6.1.6.3.16.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmContextTable,,not-accessible,,current,,The table of locally available contexts. This table provides information to SNMP Command Generator applications so that they can properly configure the vacmAccessTable to control access to all contexts at the SNMP entity. This table may change dynamically if the SNMP entity allows that contexts are added/deleted dynamically (for instance when its configuration changes). Such changes would happen only if the management instrumentation at that SNMP entity recognizes more (or fewer) contexts. The presence of entries in this table and of entries in the vacmAccessTable are independent. That is, a context identified by an entry in this table is not necessarily referenced by any entries in the vacmAccessTable; and the context(s) referenced by an entry in the vacmAccessTable does not necessarily currently exist and thus need not be identified by an entry in this table. This table must be made accessible via the default context so that Command Responder applications have a standard way of retrieving the information. This table is read-only. It cannot be configured via SNMP. 
.1.3.6.1.6.3.16.1.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmContextEntry,,not-accessible,vacmContextName,current,,Information about a particular context.
.1.3.6.1.6.3.16.1.1.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmContextName,OCTET,read-only,,current,,A human readable name identifying a particular context at a particular SNMP entity. The empty contextName (zero length) represents the default context. 
.1.3.6.1.6.3.16.1.2,SNMP-VIEW-BASED-ACM-MIB::vacmSecurityToGroupTable,,not-accessible,,current,,This table maps a combination of securityModel and securityName into a groupName which is used to define an access control policy for a group of principals. 
.1.3.6.1.6.3.16.1.2.1,SNMP-VIEW-BASED-ACM-MIB::vacmSecurityToGroupEntry,,not-accessible,vacmSecurityModel:vacmSecurityName,current,,An entry in this table maps the combination of a securityModel and securityName into a groupName. 
.1.3.6.1.6.3.16.1.2.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmSecurityModel,INTEGER,not-accessible,,current,,The Security Model, by which the vacmSecurityName referenced by this entry is provided. Note, this object may not take the 'any' (0) value. 
.1.3.6.1.6.3.16.1.2.1.2,SNMP-VIEW-BASED-ACM-MIB::vacmSecurityName,OCTET,not-accessible,,current,,The securityName for the principal, represented in a Security Model independent format, which is mapped by this entry to a groupName. 
.1.3.6.1.6.3.16.1.2.1.3,SNMP-VIEW-BASED-ACM-MIB::vacmGroupName,OCTET,read-create,,current,,The name of the group to which this entry (e.g., the combination of securityModel and securityName) belongs. This groupName is used as index into the vacmAccessTable to select an access control policy. However, a value in this table does not imply that an instance with the value exists in table vacmAccesTable. 
.1.3.6.1.6.3.16.1.2.1.4,SNMP-VIEW-BASED-ACM-MIB::vacmSecurityToGroupStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.6.3.16.1.2.1.5,SNMP-VIEW-BASED-ACM-MIB::vacmSecurityToGroupStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the vacmSecurityToGroupStatus column is 'notReady'. In particular, a newly created row cannot be made active until a value has been set for vacmGroupName. The RowStatus TC [RFC2579] requires that thisclause states under which circumstances other objects in this row can be modified: The value of this object has no effect on whether other objects in this conceptual row can be modified. 
.1.3.6.1.6.3.16.1.4,SNMP-VIEW-BASED-ACM-MIB::vacmAccessTable,,not-accessible,,current,,The table of access rights for groups. Each entry is indexed by a groupName, a contextPrefix, a securityModel and a securityLevel. To determine whether access is allowed, one entry from this table needs to be selected and the proper viewName from that entry must be used for access control checking. To select the proper entry, follow these steps: 1) the set of possible matches is formed by the intersection of the following sets of entries: the set of entries with identical vacmGroupName the union of these two sets: - the set with identical vacmAccessContextPrefix - the set of entries with vacmAccessContextMatch value of 'prefix' and matching vacmAccessContextPrefix intersected with the union of these two sets: - the set of entries with identical vacmSecurityModel - the set of entries with vacmSecurityModel value of 'any' intersected with the set of entries with vacmAccessSecurityLevel value less than or equal to the requested securityLevel 2) if this set has only one member, we're done otherwise, it comes down to deciding how to weight the preferences between ContextPrefixes, SecurityModels, and SecurityLevels as follows: a) if the subset of entries with securityModel matching the securityModel in the message is not empty, then discard the rest. b) if the subset of entries with vacmAccessContextPrefix matching the contextName in the message is not empty, then discard the rest c) discard all entries with ContextPrefixes shorter than the longest one remaining in the set d) select the entry with the highest securityLevel Please note that for securityLevel noAuthNoPriv, all groups are really equivalent since the assumption that the securityName has been authenticated does not hold. 
.1.3.6.1.6.3.16.1.4.1,SNMP-VIEW-BASED-ACM-MIB::vacmAccessEntry,,not-accessible,vacmGroupName:vacmAccessContextPrefix:vacmAccessSecurityModel:vacmAccessSecurityLevel,current,,An access right configured in the Local Configuration Datastore (LCD) authorizing access to an SNMP context. Entries in this table can use an instance value for object vacmGroupName even if no entry in table vacmAccessSecurityToGroupTable has a corresponding value for object vacmGroupName. 
.1.3.6.1.6.3.16.1.4.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmAccessContextPrefix,OCTET,not-accessible,,current,,In order to gain the access rights allowed by this conceptual row, a contextName must match exactly (if the value of vacmAccessContextMatch is 'exact') or partially (if the value of vacmAccessContextMatch is 'prefix') to the value of the instance of this object. 
.1.3.6.1.6.3.16.1.4.1.2,SNMP-VIEW-BASED-ACM-MIB::vacmAccessSecurityModel,INTEGER,not-accessible,,current,,In order to gain the access rights allowed by this conceptual row, this securityModel must be in use. 
.1.3.6.1.6.3.16.1.4.1.3,SNMP-VIEW-BASED-ACM-MIB::vacmAccessSecurityLevel,INTEGER,not-accessible,,current,noAuthNoPriv(1):authNoPriv(2):authPriv(3),The minimum level of security required in order to gain the access rights allowed by this conceptual row. A securityLevel of noAuthNoPriv is less than authNoPriv which in turn is less than authPriv. If multiple entries are equally indexed except for this vacmAccessSecurityLevel index, then the entry which has the highest value for vacmAccessSecurityLevel is selected. 
.1.3.6.1.6.3.16.1.4.1.4,SNMP-VIEW-BASED-ACM-MIB::vacmAccessContextMatch,INTEGER,read-create,,current,exact(1):prefix(2),If the value of this object is exact(1), then all rows where the contextName exactly matches vacmAccessContextPrefix are selected. If the value of this object is prefix(2), then all rows where the contextName whose starting octets exactly match vacmAccessContextPrefix are selected. This allows for a simple form of wildcarding. 
.1.3.6.1.6.3.16.1.4.1.5,SNMP-VIEW-BASED-ACM-MIB::vacmAccessReadViewName,OCTET,read-create,,current,,The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes read access. The identified MIB view is that one for which the vacmViewTreeFamilyViewName has the same value as the instance of this object; if the value is the empty string or if there is no active MIB view having this value of vacmViewTreeFamilyViewName, then no access is granted. 
.1.3.6.1.6.3.16.1.4.1.6,SNMP-VIEW-BASED-ACM-MIB::vacmAccessWriteViewName,OCTET,read-create,,current,,The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes write access. The identified MIB view is that one for which the vacmViewTreeFamilyViewName has the same value as the instance of this object; if the value is the empty string or if there is no active MIB view having this value of vacmViewTreeFamilyViewName, then no access is granted. 
.1.3.6.1.6.3.16.1.4.1.7,SNMP-VIEW-BASED-ACM-MIB::vacmAccessNotifyViewName,OCTET,read-create,,current,,The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes access for notifications. The identified MIB view is that one for which the vacmViewTreeFamilyViewName has the same value as the instance of this object; if the value is the empty string or if there is no active MIB view having this value of vacmViewTreeFamilyViewName, then no access is granted. 
.1.3.6.1.6.3.16.1.4.1.8,SNMP-VIEW-BASED-ACM-MIB::vacmAccessStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.6.3.16.1.4.1.9,SNMP-VIEW-BASED-ACM-MIB::vacmAccessStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The RowStatus TC [RFC2579] requires that thisclause states under which circumstances other objects in this row can be modified: The value of this object has no effect on whether other objects in this conceptual row can be modified. 
.1.3.6.1.6.3.16.1.5,SNMP-VIEW-BASED-ACM-MIB::vacmMIBViews,,,,,,
.1.3.6.1.6.3.16.1.5.1,SNMP-VIEW-BASED-ACM-MIB::vacmViewSpinLock,INTEGER,read-write,,current,,An advisory lock used to allow cooperating SNMP Command Generator applications to coordinate their use of the Set operation in creating or modifying views. When creating a new view or altering an existing view, it is important to understand the potential interactions with other uses of the view. The vacmViewSpinLock should be retrieved. The name of the view to be created should be determined to be unique by the SNMP Command Generator application by consulting the vacmViewTreeFamilyTable. Finally, the named view may be created (Set), including the advisory lock. If another SNMP Command Generator application has altered the views in the meantime, then the spin lock's value will have changed, and so this creation will fail because it will specify the wrong value for the spin lock. Since this is an advisory lock, the use of this lock is not enforced. 
.1.3.6.1.6.3.16.1.5.2,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyTable,,not-accessible,,current,,Locally held information about families of subtrees within MIB views. Each MIB view is defined by two sets of view subtrees: - the included view subtrees, and - the excluded view subtrees. Every such view subtree, both the included and the excluded ones, is defined in this table. To determine if a particular object instance is in a particular MIB view, compare the object instance's OBJECT IDENTIFIER with each of the MIB view's active entries in this table. If none match, then the object instance is not in the MIB view. If one or more match, then the object instance is included in, or excluded from, the MIB view according to the value of vacmViewTreeFamilyType in the entry whose value of vacmViewTreeFamilySubtree has the most sub-identifiers. If multiple entries match and have the same number of sub-identifiers (when wildcarding is specified with the value of vacmViewTreeFamilyMask), then the lexicographically greatest instance of vacmViewTreeFamilyType determines the inclusion or exclusion. An object instance's OBJECT IDENTIFIER X matches an active entry in this table when the number of sub-identifiers in X is at least as many as in the value of vacmViewTreeFamilySubtree for the entry, and each sub-identifier in the value of vacmViewTreeFamilySubtree matches its corresponding sub-identifier in X. Two sub-identifiers match either if the corresponding bit of the value of vacmViewTreeFamilyMask for the entry is zero (the 'wild card' value), or if they are equal. A 'family' of subtrees is the set of subtrees defined by a particular combination of values of vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask. In the case where no 'wild card' is defined in the vacmViewTreeFamilyMask, the family of subtrees reduces to a single subtree. When creating or changing MIB views, an SNMP Command Generator application should utilize the vacmViewSpinLock to try to avoid collisions. Seeclause of vacmViewSpinLock. When creating MIB views, it is strongly advised that first the 'excluded' vacmViewTreeFamilyEntries are created and then the 'included' entries. When deleting MIB views, it is strongly advised that first the 'included' vacmViewTreeFamilyEntries are deleted and then the 'excluded' entries. If a create for an entry for instance-level access control is received and the implementation does not support instance-level granularity, then an inconsistentName error must be returned. 
.1.3.6.1.6.3.16.1.5.2.1,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyEntry,,not-accessible,vacmViewTreeFamilyViewName:vacmViewTreeFamilySubtree,current,,Information on a particular family of view subtrees included in or excluded from a particular SNMP context's MIB view. Implementations must not restrict the number of families of view subtrees for a given MIB view, except as dictated by resource constraints on the overall number of entries in the vacmViewTreeFamilyTable. If no conceptual rows exist in this table for a given MIB view (viewName), that view may be thought of as consisting of the empty set of view subtrees. 
.1.3.6.1.6.3.16.1.5.2.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyViewName,OCTET,not-accessible,,current,,The human readable name for a family of view subtrees. 
.1.3.6.1.6.3.16.1.5.2.1.2,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilySubtree,OBJECT,not-accessible,,current,,The MIB subtree which when combined with the corresponding instance of vacmViewTreeFamilyMask defines a family of view subtrees. 
.1.3.6.1.6.3.16.1.5.2.1.3,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyMask,OCTET,read-create,,current,,The bit mask which, in combination with the corresponding instance of vacmViewTreeFamilySubtree, defines a family of view subtrees. Each bit of this bit mask corresponds to a sub-identifier of vacmViewTreeFamilySubtree, with the most significant bit of the i-th octet of this octet string value (extended if necessary, see below) corresponding to the (8*i - 7)-th sub-identifier, and the least significant bit of the i-th octet of this octet string corresponding to the (8*i)-th sub-identifier, where i is in the range 1 through 16. Each bit of this bit mask specifies whether or not the corresponding sub-identifiers must match when determining if an OBJECT IDENTIFIER is in this family of view subtrees; a '1' indicates that an exact match must occur; a '0' indicates 'wild card', i.e., any sub-identifier value matches. Thus, the OBJECT IDENTIFIER X of an object instance is contained in a family of view subtrees if, for each sub-identifier of the value of vacmViewTreeFamilySubtree, either: the i-th bit of vacmViewTreeFamilyMask is 0, or the i-th sub-identifier of X is equal to the i-th sub-identifier of the value of vacmViewTreeFamilySubtree. If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of vacmViewTreeFamilySubtree, then the bit mask is extended with 1's to be the required length. Note that when the value of this object is the zero-length string, this extension rule results in a mask of all-1's being used (i.e., no 'wild card'), and the family of view subtrees is the one view subtree uniquely identified by the corresponding instance of vacmViewTreeFamilySubtree. Note that masks of length greater than zero length do not need to be supported. In this case this object is made read-only. 
.1.3.6.1.6.3.16.1.5.2.1.4,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyType,INTEGER,read-create,,current,included(1):excluded(2),Indicates whether the corresponding instances of vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask define a family of view subtrees which is included in or excluded from the MIB view. 
.1.3.6.1.6.3.16.1.5.2.1.5,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. 
.1.3.6.1.6.3.16.1.5.2.1.6,SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row. The RowStatus TC [RFC2579] requires that thisclause states under which circumstances other objects in this row can be modified: The value of this object has no effect on whether other objects in this conceptual row can be modified. 
.1.3.6.1.6.3.16.2,SNMP-VIEW-BASED-ACM-MIB::vacmMIBConformance,,,,,,
.1.3.6.1.6.3.16.2.1,SNMP-VIEW-BASED-ACM-MIB::vacmMIBCompliances,,,,,,
.1.3.6.1.6.3.16.2.1.1,SNMP-VIEW-BASED-ACM-MIB::vacmMIBCompliance,,,,,,The compliance statement for SNMP engines which implement the SNMP View-based Access Control Model configuration MIB. 
.1.3.6.1.6.3.16.2.2,SNMP-VIEW-BASED-ACM-MIB::vacmMIBGroups,,,,,,
.1.3.6.1.6.3.16.2.2.1,SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup,,,,,,A collection of objects providing for remote configuration of an SNMP engine which implements the SNMP View-based Access Control Model. 
.1.3.6.1.6.3.18,SNMP-COMMUNITY-MIB::snmpCommunityMIB,,,,,,This MIB module defines objects to help support coexistence between SNMPv1, SNMPv2c, and SNMPv3. Copyright (C) The Internet Society (2003) This version of this MIB module is part of RFC 3584; see the RFC itself for full legal notices.
.1.3.6.1.6.3.18.1,SNMP-COMMUNITY-MIB::snmpCommunityMIBObjects,,,,,,
.1.3.6.1.6.3.18.1.1,SNMP-COMMUNITY-MIB::snmpCommunityTable,,not-accessible,,current,,The table of community strings configured in the SNMP engine's Local Configuration Datastore (LCD).
.1.3.6.1.6.3.18.1.1.1,SNMP-COMMUNITY-MIB::snmpCommunityEntry,,not-accessible,IMPLIEDsnmpCommunityIndex,current,,Information about a particular community string.
.1.3.6.1.6.3.18.1.1.1.1,SNMP-COMMUNITY-MIB::snmpCommunityIndex,OCTET,not-accessible,,current,,The unique index value of a row in this table.
.1.3.6.1.6.3.18.1.1.1.2,SNMP-COMMUNITY-MIB::snmpCommunityName,OCTET,read-create,,current,,The community string for which a row in this table represents a configuration. There is no SIZE constraint specified for this object because RFC 1157 does not impose any explicit limitation on the length of community strings (their size is constrained indirectly by the SNMP message size).
.1.3.6.1.6.3.18.1.1.1.3,SNMP-COMMUNITY-MIB::snmpCommunitySecurityName,OCTET,read-create,,current,,A human readable string representing the corresponding value of snmpCommunityName in a Security Model independent format.
.1.3.6.1.6.3.18.1.1.1.4,SNMP-COMMUNITY-MIB::snmpCommunityContextEngineID,OCTET,read-create,,current,,The contextEngineID indicating the location of the context in which management information is accessed when using the community string specified by the corresponding instance of snmpCommunityName. The default value is the snmpEngineID of the entity in which this object is instantiated.
.1.3.6.1.6.3.18.1.1.1.5,SNMP-COMMUNITY-MIB::snmpCommunityContextName,OCTET,read-create,,current,,The context in which management information is accessed when using the community string specified by the corresponding instance of snmpCommunityName.
.1.3.6.1.6.3.18.1.1.1.6,SNMP-COMMUNITY-MIB::snmpCommunityTransportTag,OCTET,read-create,,current,,This object specifies a set of transport endpoints which are used in two ways: - to specify the transport endpoints from which an SNMP entity will accept management requests, and - to specify the transport endpoints to which a notification may be sent using the community string matching the corresponding instance of snmpCommunityName. In either case, if the value of this object has zero-length, transport endpoints are not checked when either authenticating messages containing this community string, nor when generating notifications. The transports identified by this object are specified in the snmpTargetAddrTable. Entries in that table whose snmpTargetAddrTagList contains this tag value are identified. If a management request containing a community string that matches the corresponding instance of snmpCommunityName is received on a transport endpoint other than the transport endpoints identified by this object the request is deemed unauthentic. When a notification is to be sent using an entry in this table, if the destination transport endpoint of the notification does not match one of the transport endpoints selected by this object, the notification is not sent.
.1.3.6.1.6.3.18.1.1.1.7,SNMP-COMMUNITY-MIB::snmpCommunityStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row in the snmpCommunityTable. Conceptual rows having the value 'permanent' need not allow write-access to any columnar object in the row.
.1.3.6.1.6.3.18.1.1.1.8,SNMP-COMMUNITY-MIB::snmpCommunityStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this conceptual row in the snmpCommunityTable. An entry in this table is not qualified for activation until instances of all corresponding columns have been initialized, either through default values, or through Set operations. The snmpCommunityName and snmpCommunitySecurityName objects must be explicitly set. There is no restriction on setting columns in this table when the value of snmpCommunityStatus is active(1).
.1.3.6.1.6.3.18.1.2,SNMP-COMMUNITY-MIB::snmpTargetAddrExtTable,,not-accessible,,current,,The table of mask and maximum message size (mms) values associated with the snmpTargetAddrTable. The snmpTargetAddrExtTable augments the snmpTargetAddrTable with a transport address mask value and a maximum message size value. The transport address mask allows entries in the snmpTargetAddrTable to define a set of addresses instead of just a single address. The maximum message size value allows the maximum message size of another SNMP entity to be configured for use in SNMPv1 (and SNMPv2c) transactions, where the message format does not specify a maximum message size.
.1.3.6.1.6.3.18.1.2.1,SNMP-COMMUNITY-MIB::snmpTargetAddrExtEntry,,not-accessible,,current,,Information about a particular mask and mms value.
.1.3.6.1.6.3.18.1.2.1.1,SNMP-COMMUNITY-MIB::snmpTargetAddrTMask,OCTET,read-create,,current,,The mask value associated with an entry in the snmpTargetAddrTable. The value of this object must have the same length as the corresponding instance of snmpTargetAddrTAddress, or must have length 0. An attempt to set it to any other value will result in an inconsistentValue error. The value of this object allows an entry in the snmpTargetAddrTable to specify multiple addresses. The mask value is used to select which bits of a transport address must match bits of the corresponding instance of snmpTargetAddrTAddress, in order for the transport address to match a particular entry in the snmpTargetAddrTable. Bits which are 1 in the mask value indicate bits in the transport address which must match bits in the snmpTargetAddrTAddress value. Bits which are 0 in the mask indicate bits in the transport address which need not match. If the length of the mask is 0, the mask should be treated as if all its bits were 1 and its length were equal to the length of the corresponding value of snmpTargetAddrTable. This object may not be modified while the value of the corresponding instance of snmpTargetAddrRowStatus is active(1). An attempt to set this object in this case will result in an inconsistentValue error.
.1.3.6.1.6.3.18.1.2.1.2,SNMP-COMMUNITY-MIB::snmpTargetAddrMMS,Integer32,read-create,,current,,The maximum message size value associated with an entry in the snmpTargetAddrTable. Note that a value of 0 means that the maximum message size is unknown.
.1.3.6.1.6.3.18.1.3,SNMP-COMMUNITY-MIB::snmpTrapAddress,IpAddress,accessible-for-notify,,current,,The value of the agent-addr field of a Trap PDU which is forwarded by a proxy forwarder application using an SNMP version other than SNMPv1. The value of this object SHOULD contain the value of the agent-addr field from the original Trap PDU as generated by an SNMPv1 agent.
.1.3.6.1.6.3.18.1.4,SNMP-COMMUNITY-MIB::snmpTrapCommunity,OCTET,accessible-for-notify,,current,,The value of the community string field of an SNMPv1 message containing a Trap PDU which is forwarded by a a proxy forwarder application using an SNMP version other than SNMPv1. The value of this object SHOULD contain the value of the community string field from the original SNMPv1 message containing a Trap PDU as generated by an SNMPv1 agent. There is no SIZE constraint specified for this object because RFC 1157 does not impose any explicit limitation on the length of community strings (their size is constrained indirectly by the SNMP message size).
.1.3.6.1.6.3.18.2,SNMP-COMMUNITY-MIB::snmpCommunityMIBConformance,,,,,,
.1.3.6.1.6.3.18.2.1,SNMP-COMMUNITY-MIB::snmpCommunityMIBCompliances,,,,,,
.1.3.6.1.6.3.18.2.1.1,SNMP-COMMUNITY-MIB::snmpCommunityMIBCompliance,,,,,,The compliance statement for SNMP engines which implement the SNMP-COMMUNITY-MIB.
.1.3.6.1.6.3.18.2.1.2,SNMP-COMMUNITY-MIB::snmpProxyTrapForwardCompliance,,,,,,The compliance statement for SNMP engines which contain a proxy forwarding application which is capable of forwarding SNMPv1 traps using SNMPv2c or SNMPv3.
.1.3.6.1.6.3.18.2.1.3,SNMP-COMMUNITY-MIB::snmpCommunityMIBFullCompliance,,,,,,The compliance statement for SNMP engines which implement the SNMP-COMMUNITY-MIB with full read-create access.
.1.3.6.1.6.3.18.2.2,SNMP-COMMUNITY-MIB::snmpCommunityMIBGroups,,,,,,
.1.3.6.1.6.3.18.2.2.1,SNMP-COMMUNITY-MIB::snmpCommunityTableGroup,,,,,,A collection of objects providing for configuration of community strings for SNMPv1 (and SNMPv2c) usage.
.1.3.6.1.6.3.18.2.2.3,SNMP-COMMUNITY-MIB::snmpProxyTrapForwardGroup,,,,,,Objects which are used by proxy forwarding applications when translating traps between SNMP versions. These are used to preserve SNMPv1-specific information when translating to SNMPv2c or SNMPv3.
.1.3.6.1.6.3.19,SNMPv2-TM::snmpv2tm,,,,,,The MIB module for SNMP transport mappings. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3417; see the RFC itself for full legal notices. 
.1.3.6.1.6.3.20,SNMP-USM-AES-MIB::snmpUsmAesMIB,,,,,,Definitions of Object Identities needed for the use of AES by SNMP's User-based Security Model. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3826; see the RFC itself for full legal notices. Supplementary information may be available on http://www.ietf.org/copyrights/ianamib.html.
.1.3.6.1.6.3.21,SNMP-IEEE802-TM-MIB::snmpIeee802TmMib,,,,,,This MIB module defines the SNMP over IEEE 802 transport mapping. Copyright (C) The IETF Trust (2006). This version of this MIB module is part of RFC 4789; see the RFC itself for full legal notices.
.1.3.111,IEEE8021-TC-MIB::ieee,,,,,,
.1.3.111.2,IEEE8021-TC-MIB::standards-association-numbers-series-standards,,,,,,
.1.3.111.2.802,IEEE8021-TC-MIB::lan-man-stds,,,,,,
.1.3.111.2.802.1,IEEE8021-TC-MIB::ieee802dot1,,,,,,
.1.3.111.2.802.1.1,IEEE8021-TC-MIB::ieee802dot1mibs,,,,,,
.1.3.111.2.802.1.1.1,IEEE8021-TC-MIB::ieee8021TcMib,,,,,,Textual conventions used throughout the various IEEE 802.1 MIB modules. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2014). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeMib,,,,,,The Bridge MIB module for managing devices that support IEEE Std 802.1Q. This MIB module is derived from the IETF BRIDGE-MIB, RFC 4188. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2014). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.2.0,IEEE8021-BRIDGE-MIB::ieee8021BridgeNotifications,,,,,,
.1.3.111.2.802.1.1.2.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeObjects,,,,,,
.1.3.111.2.802.1.1.2.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBase,,,,,,
.1.3.111.2.802.1.1.2.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseTable,,not-accessible,,current,,A table that contains generic information about every Bridge component. All writable objects in this table MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseEntry,,not-accessible,ieee8021BridgeBaseComponentId,current,,A list of objects containing information for each Bridge component.
.1.3.111.2.802.1.1.2.1.1.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.2.1.1.1.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseBridgeAddress,OCTET,read-create,,current,,The MAC address used by this Bridge when it is referred to in a unique fashion. It is recommended that this be the numerically smallest MAC address of all ports that belong to this Bridge. However, it is only required to be unique. When concatenated with ieee8021SpanningTreePriority, a unique BridgeIdentifier is formed, which is used in the Spanning Tree Protocol. This object may not be modified while the corresponding instance of ieee8021BridgeBaseRowStatus is active(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.1.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseNumPorts,Integer32,read-only,,current,,The number of ports controlled by this bridging entity.
.1.3.111.2.802.1.1.2.1.1.1.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseComponentType,INTEGER,read-create,,current,iComponent(1):bComponent(2):cVlanComponent(3):sVlanComponent(4):dBridgeComponent(5):erComponent(6):tComponent(7),Indicates the component type(s) of this Bridge. The following component types are possible: iComponent(1) - An S-VLAN component of a Backbone Edge Bridge which performs encapsulation of customer frames. bComponent(2) - An S-VLAN component of a Backbone Edge Bridge which bundles backbone service instances into B-VLANs. cVlanComponent(3) - A C-VLAN component of an enterprise VLAN Bridge or of a Provider Bridge used to process C-tagged frames. sVlanComponent(4) - An S-VLAN component of a Provider Bridge. dBridgeComponent(5) - A VLAN unaware component of an IEEE 802.1Q Bridge.  erComponent (6) - An Edge Relay component of an EVB Station. tComponent (7) - A TPMR component in a Backbone Edge Bridge. This object may not be modified while the corresponding instance of ieee8021BridgeBaseRowStatus is active(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.1.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseDeviceCapabilities,BITS,read-create,,current,dot1dExtendedFilteringServices(0):dot1dTrafficClasses(1):dot1qStaticEntryIndividualPort(2):dot1qIVLCapable(3):dot1qSVLCapable(4):dot1qHybridCapable(5):dot1qConfigurablePvidTagging(6):dot1dLocalVlanCapable(7),Indicates the optional parts of IEEE Std 802.1Q that are implemented by this device and are manageable through this MIB. Capabilities that are allowed on a per-port basis are indicated in ieee8021BridgeBasePortCapabilities. dot1dExtendedFilteringServices(0), -- can perform filtering of -- individual multicast addresses -- controlled by MMRP. dot1dTrafficClasses(1), -- can map priority to -- multiple traffic classes. dot1qStaticEntryIndividualPort(2), -- dot1qStaticUnicastReceivePort & -- dot1qStaticMulticastReceivePort -- can represent non-zero entries. dot1qIVLCapable(3), -- Independent VLAN Learning (IVL). dot1qSVLCapable(4), -- Shared VLAN Learning (SVL). dot1qHybridCapable(5), -- both IVL & SVL simultaneously. dot1qConfigurablePvidTagging(6), -- whether the implementation -- supports the ability to -- override the default PVID -- setting and its egress status -- (VLAN-Tagged or Untagged) on -- each port. dot1dLocalVlanCapable(7) -- can support multiple local -- Bridges, outside of the scope -- of IEEE 802.1Q defined VLANs. This object may not be modified while the corresponding instance of ieee8021BridgeBaseRowStatus is active(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.1.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseTrafficClassesEnabled,INTEGER,read-create,,current,true(1):false(2),The value true(1) indicates that Traffic Classes are enabled on this Bridge. When false(2), the Bridge operates with a single priority level for all traffic. This object may be modified while the corresponding instance of ieee8021BridgeBaseRowStatus is active(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.1.1.7,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseMmrpEnabledStatus,INTEGER,read-create,,current,true(1):false(2),The administrative status requested by management for MMRP. The value true(1) indicates that MMRP should be enabled on this device, in all VLANs, on all ports for which it has not been specifically disabled. When false(2), MMRP is disabled, in all VLANs and on all ports, and all MMRP packets will be forwarded transparently. This object affects both Applicant and Registrar state machines. A transition from false(2) to true(1) will cause a reset of all MMRP state machines on all ports. This object may be modified while the corresponding instance of ieee8021BridgeBaseRowStatus is active(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.1.1.8,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object indicates the status of an entry, and is used to create/delete entries. The following objects MUST be set prior to making a new entry active: ieee8021BridgeBaseBridgeAddress ieee8021BridgeBaseComponentType ieee8021BridgeBaseDeviceCapabilities It is recommended that these three objects not be allowed to be modified while the corresponding instance of ieee8021BridgeBaseRowStatus object is active(1). The following objects are not required to be set before making a new entry active (they will take their defaults), and they also may be modified while the corresponding instance of this object is active(1): ieee8021BridgeBaseTrafficClassesEnabled ieee8021BridgeBaseMmrpEnabledStatus The value of this object and all corresponding instances of other objects in this table MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortTable,,not-accessible,,current,,A table that contains generic information about every port that is associated with this Bridge. Transparent, and source-route ports are included.
.1.3.111.2.802.1.1.2.1.1.4.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,A list of objects containing information for each port of the Bridge.
.1.3.111.2.802.1.1.2.1.1.4.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.2.1.1.4.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePort,Unsigned32,not-accessible,,current,,The port number of the port for which this entry contains Bridge management information.
.1.3.111.2.802.1.1.2.1.1.4.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortIfIndex,Integer32,read-write,,current,,The value of the instance of the IfIndex object, defined in the IF-MIB, for the interface corresponding to this port, or the value 0 if the port has not been bound to an underlying frame source and sink. It is an implementation specific decision as to whether this object may be modified if it has been created or if 0 is a legal value. The underlying IfEntry indexed by this column MUST be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.4.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortDelayExceededDiscards,Counter64,read-only,,current,,The number of frames discarded by this port due to excessive transit delay through the Bridge. It is incremented by both transparent and source route Bridges. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.2.1.1.4.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortMtuExceededDiscards,Counter64,read-only,,current,,The number of frames discarded by this port due to an excessive size. It is incremented by both transparent and source route Bridges. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.2.1.1.4.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortCapabilities,BITS,read-only,,current,dot1qDot1qTagging(0):dot1qConfigurableAcceptableFrameTypes(1):dot1qIngressFiltering(2),Indicates the parts of IEEE 802.1Q that are optional on a per-port basis, that are implemented by this device, and that are manageable through this MIB. dot1qDot1qTagging(0), -- supports IEEE 802.1Q VLAN tagging of -- frames and MVRP. dot1qConfigurableAcceptableFrameTypes(1), -- allows modified values of -- dot1qPortAcceptableFrameTypes. dot1qIngressFiltering(2) -- supports the discarding of any -- frame received on a Port whose -- VLAN classification does not -- include that Port in its Member -- set.
.1.3.111.2.802.1.1.2.1.1.4.1.7,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortTypeCapabilities,BITS,read-only,,current,customerVlanPort(0):providerNetworkPort(1):customerNetworkPort(2):customerEdgePort(3):customerBackbonePort(4):virtualInstancePort(5):dBridgePort(6):remoteCustomerAccessPort(7):stationFacingBridgePort(8):uplinkAccessPort(9):uplinkRelayPort(10),Indicates the capabilities of this port. The corresponding instance of ieee8021BridgeBasePortType can potentially take any of the values for which the corresponding bit in this object is 1. The possible port types are as follows: customerVlanPort(0) - Indicates the port can be a C-TAG- aware port of an enterprise VLAN-aware Bridge. providerNetworkPort(1) - Indicates the port can be an S-TAG-aware port of a Provider Bridge or Backbone Edge Bridge used for connections within a PBN or PBBN. customerNetworkPort(2) - Indicates the port can be an S-TAG-aware port of a Provider Bridge or Backbone Edge Bridge used for connections to the exterior of a PBN or PBBN. customerEdgePort(3) - Indicates the port can be a C-TAG- aware port of a Provider Bridge used for connections to the exterior of a PBN or PBBN. customerBackbonePort(4) - Indicates the port can be a I-TAG-aware port of a Backbone Edge Bridge's B-component. virtualInstancePort(5) - Indicates the port can be a virtual S-TAG-aware port within a Backbone Edge Bridge's I-component which is responsible for handling S-tagged traffic for a specific backbone service instance. dBridgePort(6) - Indicates the port can be a VLAN-unaware member of an IEEE 802.1Q Bridge. remoteCustomerAccessPort(7) - Indicates the port can be an S-TAG-aware port of a Provider Bridge capable of providing Remote Customer Service Interfaces.  stationFacingBridgePort(8) - Indicates the station-facing Bridge Port in a EVB Bridge.  uplinkAccessPort(9) - Indicates the uplink access port in an EVB Bridge or EVB station.  uplinkRelayPort (10) - Indicates the uplink relay port in an EVB station.
.1.3.111.2.802.1.1.2.1.1.4.1.8,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortType,INTEGER,read-only,,current,none(1):customerVlanPort(2):providerNetworkPort(3):customerNetworkPort(4):customerEdgePort(5):customerBackbonePort(6):virtualInstancePort(7):dBridgePort(8):remoteCustomerAccessPort(9):stationFacingBridgePort(10):uplinkAccessPort(11):uplinkRelayPort(12),The port type. This value MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.1.4.1.9,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortExternal,INTEGER,read-only,,current,true(1):false(2),A boolean indicating whether the port is external. A value of true(1) means the port is external. A value of false(2) means the port is internal.
.1.3.111.2.802.1.1.2.1.1.4.1.10,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortAdminPointToPoint,INTEGER,read-write,,current,forceTrue(1):forceFalse(2):auto(3),For a port running spanning tree, this object represents the  administrative point-to-point status of the LAN segment attached to this port, using the enumeration values of IEEE Std 802.1AC. A value of forceTrue(1) indicates that this port should always be treated as if it is connected to a point-to-point link. A value of forceFalse(2) indicates that this port should be treated as having a shared media connection. A value of auto(3) indicates that this port is considered to have a point-to-point link if it is an Aggregator and all of its members are aggregatable, or if the MAC entity is configured for full duplex operation, either through auto-negotiation or by management means. Manipulating this object changes the underlying adminPointToPointMAC. For a VIP, the adminPointToPointMAC parameter controls the mechanism by which the Default Backbone Destination parameter for the VIP is determined. For a backbone service instance that includes only 2 VIPs, the value may be set to forceTrue(1) which permits dynamic learning of the Default Backbone Destination parameter. For a backbone service instance that includes more than 2 VIPs, the value MUST be set to ForceFalse(2) or auto(3). When this object is set to forceTrue(1) for a VIP, the Default Backbone Destination parameter is modified by the subsequent M_UNITDATA.indications as specified in 6.10.1 (and described in 26.4.1). Whenever the parameter is set to forceFalse(2) or auto(3), the value for the Default Backbone Destination parameter is set to the Backbone Service Instance Group Address for the VIP-ISID.  The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.1.4.1.11,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortOperPointToPoint,INTEGER,read-only,,current,true(1):false(2),For a port running spanning tree, this object represents the operational point-to-point status of the LAN segment attached to this port. It indicates whether a port is considered to have a point-to-point connection. If adminPointToPointMAC is set to auto(2), then the value of operPointToPointMAC is determined in accordance with the specific procedures defined for the MAC entity concerned, as defined in IEEE Std 802.1AC. The value is determined dynamically; that is, it is re-evaluated whenever the value of adminPointToPointMAC changes, and whenever the specific procedures defined for the MAC entity evaluate a change in its point-to-point status. For a VIP, this object simply reflects the value of the corresponding instance of ieee8021BridgeBasePortAdminPointToPoint. The value will be true(1) if that object is forceTrue(1), and the value will be false(2) if the value of that object is either forceFalse(2) or auto(3).
.1.3.111.2.802.1.1.2.1.1.4.1.12,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortName,OCTET,read-only,,current,,A text string of up to 32 characters, of locally determined significance.
.1.3.111.2.802.1.1.2.1.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseIfToPortTable,,not-accessible,,current,,A table that contains generic information about every ifIndex that is associated with this Bridge.
.1.3.111.2.802.1.1.2.1.1.5.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseIfToPortEntry,,not-accessible,ifIndex,current,,A list of objects containing information for each ifIndex of the Bridge.
.1.3.111.2.802.1.1.2.1.1.5.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseIfIndexComponentId,Unsigned32,read-only,,current,,The component ID for this ifIndex.
.1.3.111.2.802.1.1.2.1.1.5.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseIfIndexPort,Unsigned32,read-only,,current,,The port for this ifIndex.
.1.3.111.2.802.1.1.2.1.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPortTable,,not-accessible,,current,,A table that contains ISS port number to Bridge  componentID and port number mapping.
.1.3.111.2.802.1.1.2.1.1.6.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPortEntry,,not-accessible,ieee8021BridgePhyPort,current,,A list of objects containing mapping for ISS port numbers to Bridge componentID and port numbers 
.1.3.111.2.802.1.1.2.1.1.6.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPort,Unsigned32,not-accessible,,current,,The ISS port.
.1.3.111.2.802.1.1.2.1.1.6.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPortIfIndex,Integer32,read-only,,current,,The value of the instance of the IfIndex object, defined in the IF-MIB, for the interface corresponding to this port, or the value 0 if the port has not been bound to an underlying frame source and sink. The underlying IfEntry indexed by this column MUST  be persistent across reinitializations of the  management system.
.1.3.111.2.802.1.1.2.1.1.6.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyMacAddress,OCTET,read-only,,current,,The MAC address
.1.3.111.2.802.1.1.2.1.1.6.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPortToComponentId,Unsigned32,read-only,,current,,The component ID that this ISS port belongs to.
.1.3.111.2.802.1.1.2.1.1.6.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPortToInternalPort,Unsigned32,read-only,,current,,The port number to which this ISS port maps to.
.1.3.111.2.802.1.1.2.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeTp,,,,,,
.1.3.111.2.802.1.1.2.1.2.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortTable,,not-accessible,,current,,A table that contains information about every port that is associated with this transparent Bridge.
.1.3.111.2.802.1.1.2.1.2.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortEntry,,not-accessible,ieee8021BridgeTpPortComponentId:ieee8021BridgeTpPort,current,,A list of objects containing information for each port of a transparent Bridge.
.1.3.111.2.802.1.1.2.1.2.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.2.1.2.1.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPort,Unsigned32,not-accessible,,current,,The port number of the port for which this entry contains Transparent bridging management information.
.1.3.111.2.802.1.1.2.1.2.1.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortMaxInfo,Integer32,read-only,,current,,The maximum size of the INFO (non-MAC) field that this port will receive or transmit.
.1.3.111.2.802.1.1.2.1.2.1.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortInFrames,Counter64,read-only,,current,,The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including Bridge management frames. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.2.1.2.1.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortOutFrames,Counter64,read-only,,current,,The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including Bridge management frames. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.2.1.2.1.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortInDiscards,Counter64,read-only,,current,,Count of received valid frames that were discarded (i.e., filtered) by the Forwarding Process. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.2.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePriority,,,,,,
.1.3.111.2.802.1.1.2.1.3.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortPriorityTable,,not-accessible,,current,,A table that contains information about every port that is associated with this transparent Bridge.
.1.3.111.2.802.1.1.2.1.3.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortPriorityEntry,,not-accessible,,current,,A list of Default User Priorities for each port of a transparent Bridge. This is indexed by ieee8021BridgeBasePortComponentId and ieee8021BridgeBasePort.
.1.3.111.2.802.1.1.2.1.3.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDefaultUserPriority,Unsigned32,read-write,,current,,The default ingress priority for this port. This only has effect on media, such as Ethernet, that do not support native priority. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.3.1.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePortNumTrafficClasses,Integer32,read-write,,current,,The number of egress traffic classes supported on this port. This object may optionally be read-only. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.3.1.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePortPriorityCodePointSelection,INTEGER,read-write,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4), This object identifies the rows in the PCP encoding and decoding tables that are used to remark frames on this  port if this remarking is enabled.
.1.3.111.2.802.1.1.2.1.3.1.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgePortUseDEI,INTEGER,read-write,,current,true(1):false(2),If the Use_DEI is set to true(1) for the Port then the  drop_eligible parameter is encoded in the DEI of transmitted frames, and the drop_eligible parameter shall be true(1) for a received frame if the DEI is set in the VLAN tag or the Priority Code Point Decoding Table indicates drop_eligible True for the received PCP value. If the Use_DEI parameter is false(2), the DEI shall be transmitted as zero and ignored on receipt. The default value of the Use_DEI parameter is false(2).
.1.3.111.2.802.1.1.2.1.3.1.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgePortRequireDropEncoding,INTEGER,read-write,,current,true(1):false(2),If a Bridge supports encoding or decoding of drop_eligible from the PCP field of a VLAN tag (6.7.3) on any of its Ports, then it shall implement a Boolean parameter Require Drop Encoding on each of its Ports with default value false(2). If Require Drop Encoding is True and the Bridge Port cannot encode particular priorities with drop_eligible, then frames queued with those priorities and drop_eligible true(1) shall be discarded and not transmitted.
.1.3.111.2.802.1.1.2.1.3.1.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgePortServiceAccessPrioritySelection,INTEGER,read-write,,current,true(1):false(2),Indication of whether the Service Access Priority Selection function is supported on the Customer Bridge Port to request priority handling of the frame from a Port-based service interface.
.1.3.111.2.802.1.1.2.1.3.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeUserPriorityRegenTable,,not-accessible,,current,,A list of Regenerated User Priorities for each received priority on each port of a Bridge. The regenerated priority value may be used to index the Traffic Class Table for each input port. This only has effect on media that support native priority. The default values for Regenerated User Priorities are the same as the User Priorities.
.1.3.111.2.802.1.1.2.1.3.2.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeUserPriorityRegenEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021BridgeUserPriority,current,,A mapping of incoming priority to a regenerated priority.
.1.3.111.2.802.1.1.2.1.3.2.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeUserPriority,Unsigned32,not-accessible,,current,,The priority for a frame received on this port.
.1.3.111.2.802.1.1.2.1.3.2.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeRegenUserPriority,Unsigned32,read-write,,current,,The regenerated priority that the incoming User Priority is mapped to for this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.3.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeTrafficClassTable,,not-accessible,,current,,A table mapping evaluated priority to Traffic Class, for forwarding by the Bridge. Traffic class is a number in the range (0..(ieee8021BridgePortNumTrafficClasses-1)).
.1.3.111.2.802.1.1.2.1.3.3.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeTrafficClassEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021BridgeTrafficClassPriority,current,,Priority to Traffic Class mapping.
.1.3.111.2.802.1.1.2.1.3.3.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeTrafficClassPriority,Unsigned32,not-accessible,,current,,The Priority value determined for the received frame. This value is equivalent to the priority indicated in the tagged frame received, or one of the evaluated priorities, determined according to the media-type. For untagged frames received from Ethernet media, this value is equal to the ieee8021BridgePortDefaultUserPriority value for the ingress port. For untagged frames received from non-Ethernet media, this value is equal to the ieee8021BridgeRegenUserPriority value for the ingress port and media-specific priority.
.1.3.111.2.802.1.1.2.1.3.3.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeTrafficClass,Integer32,read-write,,current,,The Traffic Class the received frame is mapped to. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.3.4,IEEE8021-BRIDGE-MIB::ieee8021BridgePortOutboundAccessPriorityTable,,not-accessible,,current,,A table mapping regenerated priority to Outbound Access Priority. This is a fixed mapping for all port types, with three options for IEEE 802.17 RPR.
.1.3.111.2.802.1.1.2.1.3.4.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortOutboundAccessPriorityEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021BridgeRegenUserPriority,current,,Regenerated priority to Outbound Access Priority mapping.
.1.3.111.2.802.1.1.2.1.3.4.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortOutboundAccessPriority,Unsigned32,read-only,,current,,The Outbound Access Priority the received frame is mapped to.
.1.3.111.2.802.1.1.2.1.3.5,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingTable,,not-accessible,,current,,A table that contains information about Priority Code Point Decoding Table for a Port of a provider Bridge. Alternative values for each table are specified as rows in Table 6-3 (6.9.3), with each alternative labeled by the number of distinct priorities that can be communicated, and the number of these for which drop precedence can be communicated. All writable objects in this table MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.3.5.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingEntry,,not-accessible,ieee8021BridgePortDecodingComponentId:ieee8021BridgePortDecodingPortNum:ieee8021BridgePortDecodingPriorityCodePointRow:ieee8021BridgePortDecodingPriorityCodePoint,current,,A list of objects containing Priority Code Point Decoding information for a port of a provider Bridge.
.1.3.111.2.802.1.1.2.1.3.5.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.2.1.3.5.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingPortNum,Unsigned32,not-accessible,,current,,A unique identifier of a port controlled by this VLAN bridging entity.
.1.3.111.2.802.1.1.2.1.3.5.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingPriorityCodePointRow,INTEGER,not-accessible,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4),The specific row in Table 6-2 (6.9.3) indicating the PCP.
.1.3.111.2.802.1.1.2.1.3.5.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingPriorityCodePoint,Integer32,not-accessible,,current,,The specific PCP value in Table 6-2 (6.9.3).
.1.3.111.2.802.1.1.2.1.3.5.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingPriority,Unsigned32,read-write,,current,,The specific priority value in Table 6-2 (6.9.3).
.1.3.111.2.802.1.1.2.1.3.5.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingDropEligible,INTEGER,read-write,,current,true(1):false(2),The drop eligibility value in Table 6-3 (6.7.3).
.1.3.111.2.802.1.1.2.1.3.6,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingTable,,not-accessible,,current,,A table that contains information about Priority Code Point Decoding Table for a Port of a provider Bridge. Alternative values for each table are specified as rows in Table 6-2 (6.9.3), with each alternative labeled by the number of distinct priorities that can be communicated, and the number of these for which drop precedence can be communicated. All writable objects in this table MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.3.6.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingEntry,,not-accessible,ieee8021BridgePortEncodingComponentId:ieee8021BridgePortEncodingPortNum:ieee8021BridgePortEncodingPriorityCodePointRow:ieee8021BridgePortEncodingPriorityCodePoint:ieee8021BridgePortEncodingDropEligible,current,,A list of objects containing Priority Code Point Encoding information for a port of a provider Bridge.
.1.3.111.2.802.1.1.2.1.3.6.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.2.1.3.6.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingPortNum,Unsigned32,not-accessible,,current,,A unique identifier of a port controlled by this VLAN bridging entity.
.1.3.111.2.802.1.1.2.1.3.6.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingPriorityCodePointRow,INTEGER,not-accessible,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4),The specific row in Table 6-2 (6.9.3) indicating the PCP row. (i.e., 8P0D, 7P1D, 6P2D, 5P3D)
.1.3.111.2.802.1.1.2.1.3.6.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingPriorityCodePoint,Integer32,not-accessible,,current,,The specific row in Table 6-2 (6.9.3) indicating the PCP. (i.e., 0,1,2,3,4,5,6,7).
.1.3.111.2.802.1.1.2.1.3.6.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingDropEligible,INTEGER,not-accessible,,current,true(1):false(2),The specific row in Table 6-2 (6.9.3) indicating the drop eligibility. A value of true(1) means eligible for drop.
.1.3.111.2.802.1.1.2.1.3.6.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingPriority,Unsigned32,read-write,,current,,The encoding priority in Table 6-2 (6.9.3).
.1.3.111.2.802.1.1.2.1.3.7,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityTable,,not-accessible,,current,,A table that contains information about the Service Access Priority Selection function for a provider Bridge. The use of this table enables a mechanism for a Customer Bridge attached to a Provider Bridged Network to request priority handling of frames. All writable objects in this table MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.3.7.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityEntry,,not-accessible,ieee8021BridgeServiceAccessPriorityComponentId:ieee8021BridgeServiceAccessPriorityPortNum:ieee8021BridgeServiceAccessPriorityReceived,current,,A list of objects containing information about the Service Access Priority Selection function for a provider Bridge.
.1.3.111.2.802.1.1.2.1.3.7.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.2.1.3.7.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityPortNum,Unsigned32,not-accessible,,current,,A unique identifier of a port controlled by this VLAN bridging entity.
.1.3.111.2.802.1.1.2.1.3.7.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityReceived,Unsigned32,not-accessible,,current,,The default received priority value in Table 6-4. (i.e., 0,1,2,3,4,5,6,7)
.1.3.111.2.802.1.1.2.1.3.7.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityValue,Unsigned32,read-write,,current,,The regenerated priority value in Table 6-4. (i.e., 0,1,2,3,4,5,6,7)
.1.3.111.2.802.1.1.2.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeMrp,,,,,,
.1.3.111.2.802.1.1.2.1.4.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMrpTable,,not-accessible,,current,,A table of MRP control information about every Bridge port. This is indexed by ieee8021BridgeBasePortComponentId and ieee8021BridgeBasePort.
.1.3.111.2.802.1.1.2.1.4.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMrpEntry,,not-accessible,,current,,MRP control information for a Bridge Port.
.1.3.111.2.802.1.1.2.1.4.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMrpJoinTime,INTEGER,read-write,,current,,The MRP Join time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.4.1.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMrpLeaveTime,INTEGER,read-write,,current,,The MRP Leave time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.4.1.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMrpLeaveAllTime,INTEGER,read-write,,current,,The MRP LeaveAll time, in centiseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.5,IEEE8021-BRIDGE-MIB::ieee8021BridgeMmrp,,,,,,
.1.3.111.2.802.1.1.2.1.5.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMmrpTable,,not-accessible,,current,,A table of MMRP control and status information about every Bridge Port. Augments the ieee8021BridgeBasePortTable.
.1.3.111.2.802.1.1.2.1.5.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMmrpEntry,,not-accessible,,current,,MMRP control and status information for a Bridge Port.
.1.3.111.2.802.1.1.2.1.5.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMmrpEnabledStatus,INTEGER,read-write,,current,true(1):false(2),The administrative state of MMRP operation on this port. The value true(1) indicates that MMRP is enabled on this port in all VLANs as long as ieee8021BridgeMmrpEnabledStatus is also true(1). A value of false(2) indicates that MMRP is disabled on this port in all VLANs: any MMRP packets received will be silently discarded, and no MMRP registrations will be propagated from other ports. Setting this to a value of true(1) will be stored by the agent but will only take effect on the MMRP protocol operation if ieee8021BridgeMmrpEnabledStatus also indicates the value true(1). This object affects all MMRP Applicant and Registrar state machines on this port. A transition from false(2) to true(1) will cause a reset of all MMRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.5.1.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMmrpFailedRegistrations,Counter64,read-only,,current,,The total number of failed MMRP registrations, for any reason, in all VLANs, on this port.
.1.3.111.2.802.1.1.2.1.5.1.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMmrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last MMRP message received on this port.
.1.3.111.2.802.1.1.2.1.5.1.1.4,IEEE8021-BRIDGE-MIB::ieee8021BridgePortRestrictedGroupRegistration,INTEGER,read-write,,current,true(1):false(2),The state of Restricted Group Registration on this port. If the value of this control is true(1), then creation of a new dynamic entry is permitted only if there is a Static Filtering Entry for the VLAN concerned, in which the Registrar Administrative Control value is Normal Registration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.2.1.6,IEEE8021-BRIDGE-MIB::ieee8021BridgeInternalLan,,,,,,
.1.3.111.2.802.1.1.2.1.6.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeILanIfTable,,not-accessible,,current,,This table is a sparse augmentation of ifTable and controls the creation of the I-LAN Interface. An I-LAN Interface is used to create internal connections between Bridge Ports in a 802.1 device. An I-LAN Interfaces can be directly associated with a set of Bridge Ports. An I-LAN Interfaces can also be used as a stacking interface to relate other interfaces before association to Bridge Ports. For example, an I-LAN interface can be created to link traffic between a PIP and a CBP. In this case a CBP is created on the B-Component and the CBP's related IfEntry is stacked upon the IfEntry of the I-LAN. The PIP is stacked upon the I-LAN using the IfStackTable. Finally, a VIP is created on the I-Component and is associated with the PIP, thus completing the path from the I-Component's MAC relay to the CBP on the B-Component. Entries in this table MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.6.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeILanIfEntry,,not-accessible,ifIndex,current,,Each entry consists of a Row Status to control creation.
.1.3.111.2.802.1.1.2.1.6.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeILanIfRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete entries in this table and the Interface table.
.1.3.111.2.802.1.1.2.1.7,IEEE8021-BRIDGE-MIB::ieee8021BridgeDot1d,,,,,,
.1.3.111.2.802.1.1.2.1.7.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeDot1dPortTable,,not-accessible,,current,,This table provides the capability to dynamically create and delete MAC Bridge Ports. Each entry in this table MUST have a corresponding entry in the ieee8021BridgeBasePortTable. Entries in this table MUST be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.2.1.7.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeDot1dPortEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,Each entry consists of a Row Status to control creation.
.1.3.111.2.802.1.1.2.1.7.1.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeDot1dPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used to create and delete entries in this table and the ieee8021BridgeBasePortTable.
.1.3.111.2.802.1.1.2.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeConformance,,,,,,
.1.3.111.2.802.1.1.2.2.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeCompliances,,,,,,
.1.3.111.2.802.1.1.2.2.1.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeCompliance,,,,,,The compliance statement for devices supporting VLAN-unaware bridging services as defined in  IEEE Std 802.1Q. Such devices support path cost values of 32-bits, and Bridge and port priority values are more restricted than in IEEE Std 802.1D-1995. Full support for the IEEE 802.1Q management objects requires implementation of the objects listed in the systemGroup from the SNMPv2-MIB [RFC3418], as well as the objects listed in the ifGeneralInformationGroup from the IF-MIB [RFC2863].
.1.3.111.2.802.1.1.2.2.1.2,IEEE8021-BRIDGE-MIB::ieee8021BridgePriorityAndMulticastFilteringCompliance,,,,,,The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
.1.3.111.2.802.1.1.2.2.1.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeCompliance1,,,,,,The compliance statement for devices supporting VLAN-unaware bridging services as defined in  IEEE Std 802.1Q. Such devices support path cost values of 32-bits, and Bridge and port priority values are more restricted than in IEEE Std 802.1D-1995. Full support for the IEEE 802.1Q management objects requires implementation of the objects listed in the systemGroup from the SNMPv2-MIB [RFC3418], as well as the objects listed in the ifGeneralInformationGroup from the IF-MIB [RFC2863].
.1.3.111.2.802.1.1.2.2.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeGroups,,,,,,
.1.3.111.2.802.1.1.2.2.2.1,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseBridgeGroup,,,,,,Bridge level information for this device.
.1.3.111.2.802.1.1.2.2.2.2,IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortGroup,,,,,,Information for each port on this device.
.1.3.111.2.802.1.1.2.2.2.3,IEEE8021-BRIDGE-MIB::ieee8021BridgeCapGroup,,,,,,A collection of objects indicating the optional capabilities of the device.
.1.3.111.2.802.1.1.2.2.2.4,IEEE8021-BRIDGE-MIB::ieee8021BridgeDeviceMmrpGroup,,,,,,A collection of objects providing device-level control for the Multicast Filtering extended Bridge services.
.1.3.111.2.802.1.1.2.2.2.6,IEEE8021-BRIDGE-MIB::ieee8021BridgeTpPortGroup,,,,,,Dynamic Filtering Database information for each port of the Bridge.
.1.3.111.2.802.1.1.2.2.2.7,IEEE8021-BRIDGE-MIB::ieee8021BridgeDevicePriorityGroup,,,,,,A collection of objects providing device-level control for the Priority services.
.1.3.111.2.802.1.1.2.2.2.8,IEEE8021-BRIDGE-MIB::ieee8021BridgeDefaultPriorityGroup,,,,,,A collection of objects defining the priority applicable to each port for media that do not support native priority.
.1.3.111.2.802.1.1.2.2.2.9,IEEE8021-BRIDGE-MIB::ieee8021BridgeRegenPriorityGroup,,,,,,A collection of objects defining the User Priorities applicable to each port for media that support native priority.
.1.3.111.2.802.1.1.2.2.2.10,IEEE8021-BRIDGE-MIB::ieee8021BridgePriorityGroup,,,,,,A collection of objects defining the traffic classes within a Bridge for each evaluated priority.
.1.3.111.2.802.1.1.2.2.2.11,IEEE8021-BRIDGE-MIB::ieee8021BridgeAccessPriorityGroup,,,,,,A collection of objects defining the media-dependent outbound access level for each priority.
.1.3.111.2.802.1.1.2.2.2.12,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMrpGroup,,,,,,A collection of objects providing port level control and status information for MRP operation.
.1.3.111.2.802.1.1.2.2.2.13,IEEE8021-BRIDGE-MIB::ieee8021BridgePortMmrpGroup,,,,,,A collection of objects providing port level control and status information for MMRP operation.
.1.3.111.2.802.1.1.2.2.2.14,IEEE8021-BRIDGE-MIB::ieee8021BridgePortDecodingGroup,,,,,,A collection of objects providing statistics counters for decoding priority and drop eligibility for Bridge Ports.
.1.3.111.2.802.1.1.2.2.2.15,IEEE8021-BRIDGE-MIB::ieee8021BridgePortEncodingGroup,,,,,,A collection of objects providing statistics counters for encoding priority and drop eligibility for Bridge Ports.
.1.3.111.2.802.1.1.2.2.2.16,IEEE8021-BRIDGE-MIB::ieee8021BridgeServiceAccessPriorityGroup,,,,,,A collection of objects providing statistics counters for service access priority.
.1.3.111.2.802.1.1.2.2.2.17,IEEE8021-BRIDGE-MIB::ieee8021BridgeInternalLANGroup,,,,,,A collection of objects providing control of internal LAN configuration.
.1.3.111.2.802.1.1.2.2.2.18,IEEE8021-BRIDGE-MIB::ieee8021BridgeCreatableBaseBridgeGroup,,,,,,Controls the managment system directed creation of Bridge Components.
.1.3.111.2.802.1.1.2.2.2.19,IEEE8021-BRIDGE-MIB::ieee8021BridgeDot1dDynamicPortCreationGroup,,,,,,A collection of objects providing dynamic creation and deletion of MAC Bridge Ports.
.1.3.111.2.802.1.1.2.2.2.20,IEEE8021-BRIDGE-MIB::ieee8021BridgeBaseIfToPortGroup,,,,,,A collection of objects providing a map between interface index and component ID and Bridge Ports.
.1.3.111.2.802.1.1.2.2.2.21,IEEE8021-BRIDGE-MIB::ieee8021BridgePhyPortGroup,,,,,,The collection of objects used to represent a ISS port management objects.
.1.3.111.2.802.1.1.3,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeMib,,,,,,The Spanning-Tree MIB module for managing devices that support IEEE 802.1Q. This MIB module is derived from the IETF BRIDGE-MIB, RFC 4188. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2014). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.3.0,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeNotifications,,,,,,
.1.3.111.2.802.1.1.3.0.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeNewRoot,,,,,,The ieee8021SpanningTreeNewRoot notification indicates that the sending agent has become the new root of the Spanning Tree; the notification is sent by a Bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer, immediately subsequent to its election.
.1.3.111.2.802.1.1.3.0.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeTopologyChange,,,,,,A ieee8021SpanningTreeTopologyChange notification is sent by a Bridge when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The notification is not sent if a ieee8021SpanningTreeNewRoot notification is sent for the same transition.
.1.3.111.2.802.1.1.3.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeObjects,,,,,,
.1.3.111.2.802.1.1.3.1.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeTable,,not-accessible,,current,,A table that contains information related to STP about every Bridge.
.1.3.111.2.802.1.1.3.1.1.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeEntry,,not-accessible,ieee8021SpanningTreeComponentId,current,,A list of objects containing information for each Bridge about the Spanning Tree Protocol for that Bridge.
.1.3.111.2.802.1.1.3.1.1.1.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.3.1.1.1.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeProtocolSpecification,INTEGER,read-only,,current,unknown(1):decLb100(2):ieee8021d(3):ieee8021q(4),An indication of what version of the Spanning Tree Protocol is being run. The value 'decLb100(2)' indicates the DEC LANbridge 100 Spanning Tree protocol. IEEE 802.1D implementations will return 'ieee8021d(3)'. New enumerated values may be added in the future to the definition of this object to reflect future versions of the IEEE Spanning Tree protocol.
.1.3.111.2.802.1.1.3.1.1.1.3,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePriority,Integer32,read-write,,current,,The value of the write-able portion of the Bridge ID (i.e., the first two octets of the (8 octet long) Bridge ID). The other (last) 6 octets of the Bridge ID are given by the value of ieee8021BridgeBaseBridgeAddress. On Bridges supporting IEEE 802.1t or IEEE 802.1w, permissible values are 0-61440, in steps of 4096. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.1.1.4,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeTimeSinceTopologyChange,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last time a topology change was detected by the Bridge entity. For RSTP, this reports the time since the tcWhile timer for any port on this Bridge was nonzero.
.1.3.111.2.802.1.1.3.1.1.1.5,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeTopChanges,Counter64,read-only,,current,,The total number of topology changes detected by this Bridge since the management entity was last reset or initialized. Discontinuities in the value of the counter can occur at re-initialization of the management system.
.1.3.111.2.802.1.1.3.1.1.1.6,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeDesignatedRoot,OCTET,read-only,,current,,The Bridge identifier of the root of the spanning tree, as determined by the Spanning Tree Protocol, as executed by this node. This value is used as the Root Identifier parameter in all Configuration Bridge PDUs originated by this node.
.1.3.111.2.802.1.1.3.1.1.1.7,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRootCost,Integer32,read-only,,current,,The cost of the path to the root as seen from this Bridge.
.1.3.111.2.802.1.1.3.1.1.1.8,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRootPort,Unsigned32,read-only,,current,,The port number of the port that offers the lowest cost path from this Bridge to the root Bridge.
.1.3.111.2.802.1.1.3.1.1.1.9,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeMaxAge,Integer32,read-only,,current,,The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this Bridge is currently using.
.1.3.111.2.802.1.1.3.1.1.1.10,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeHelloTime,Integer32,read-only,,current,,The amount of time between the transmission of Configuration Bridge PDUs by this node on any port when it is the root of the spanning tree, or trying to become so, in units of hundredths of a second. This is the actual value that this Bridge is currently using.
.1.3.111.2.802.1.1.3.1.1.1.11,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeHoldTime,Integer32,read-only,,current,,This time value determines the interval length during which no more than two Configuration Bridge PDUs shall be transmitted by this node, in units of hundredths of a second.
.1.3.111.2.802.1.1.3.1.1.1.12,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeForwardDelay,Integer32,read-only,,current,,This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the Listening and Learning states, which precede the Forwarding state. This value is also used when a topology change has been detected and is underway, to age all dynamic entries in the Filtering Database. [Note that this value is the one that this Bridge is currently using, in contrast to ieee8021SpanningTreeBridgeForwardDelay, which is the value that this Bridge and all others would start using if/when this Bridge were to become the root.]
.1.3.111.2.802.1.1.3.1.1.1.13,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeBridgeMaxAge,Integer32,read-write,,current,,The value that all Bridges use for MaxAge when this Bridge is acting as the root. Note that IEEE Std 802.1D-1998 specifies that the range for this parameter is related to the value of ieee8021SpanningTreeBridgeHelloTime. The granularity of this timer is specified by IEEE Std 802.1D-1998  to be 1 second. An agent may return an SNMP badValue error (or its equivalent if another protocol is used) if a set is attempted to a value that is not a whole number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.1.1.14,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeBridgeHelloTime,Integer32,read-write,,current,,The value that all Bridges use for HelloTime when this Bridge is acting as the root. The granularity of this timer is specified by IEEE Std 802.1D-1998 to be 1 second.  An agent may return an SNMP badValue error (or its equivalent if another protocol is used) if a set is attempted to a value that is not a whole number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.1.1.15,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeBridgeForwardDelay,Integer32,read-write,,current,,The value that all Bridges use for ForwardDelay when this Bridge is acting as the root. Note that IEEE Std  802.1D-1998 specifies that the range for this parameter is related to the value of ieee8021SpanningTreeBridgeMaxAge. The granularity of this timer is specified by IEEE Std 802.1D-1998 to be 1 second. An agent may return an SNMP badValue error (or its equivalent if another protocol is used) if a set is attempted to a value that is not a whole number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.1.1.16,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeVersion,INTEGER,read-write,,current,stp(0):rstp(2):mstp(3),The version of Spanning Tree Protocol the Bridge is currently running. The values are directly from the IEEE standard. New values may be defined as future versions of the protocol become available. The value 'stp(0)' indicates the Bridge is running the Spanning Tree Protocol specified in IEEE Std 802.1D-1998. The value 'rstp(2)' indicates the Bridge is running RSTP specified in IEEE 802.1Q. The value 'mstp(3)' indicates the Bridge is running MSTP specified in Clause 13 of IEEE Std 802.1Q. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.1.1.17,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpTxHoldCount,Integer32,read-write,,current,,The value used by the Port Transmit state machine to limit the maximum transmission rate. This is used by Bridges that are running RSTP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortTable,,not-accessible,,current,,A table that contains port-specific information for the Spanning Tree Protocol.
.1.3.111.2.802.1.1.3.1.2.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortEntry,,not-accessible,ieee8021SpanningTreePortComponentId:ieee8021SpanningTreePort,current,,A list of objects containing information maintained by every port about the Spanning Tree Protocol state for that port.
.1.3.111.2.802.1.1.3.1.2.1.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.3.1.2.1.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePort,Unsigned32,not-accessible,,current,,The port number of the port for which this entry contains Spanning Tree Protocol management information.
.1.3.111.2.802.1.1.3.1.2.1.3,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortPriority,Integer32,read-write,,current,,The value of the priority field that is contained in the first (in network byte order) octet of the (2 octet long) Port ID. The other octet of the Port ID is given by the value of ieee8021SpanningTreePort. On Bridges supporting IEEE 802.1t or IEEE 802.1w, permissible values are 0-240, in steps of 16. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.2.1.4,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortState,INTEGER,read-only,,current,disabled(1):blocking(2):listening(3):learning(4):forwarding(5):broken(6),The port's current state, as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the Bridge has detected a port that is malfunctioning, it will place that port into the broken(6) state. For ports that are disabled (see ieee8021SpanningTreePortEnabled), this object will have a value of disabled(1). The values disabled, blocking,  listening, and broken correspond to the Clause 12 port  state of 'Discarding'. The value learning corresponds to  the Clause 12 port state of 'Learning'. The value forwarding corresponds to the Clause 12 port state of 'Forwarding'.
.1.3.111.2.802.1.1.3.1.2.1.5,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortEnabled,INTEGER,read-write,,current,true(1):false(2),The enabled/disabled status of the port. A value of true(1) means the spanning-tree protocol is enabled for this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.2.1.6,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortPathCost,Integer32,read-write,,current,,The contribution of this port to the path cost of paths towards the spanning tree root which include this port. Table 13-4 recommends defaults and ranges for Port Path Cost values, in inverse proportion to the speed of the attached LAN. If this object is used to set the Path Cost it is possible to restore the  default setting using the  ieee8021SpanningTreeRstpPortAdminPathCost object. Table 13-4 recommends defaults and ranges for Port  Path Cost values, in inverse proportion to the speed of the  attached LAN. If this object is used to set the Path  Cost it is possible to restore the default setting using the ieee8021MstpPortAdminPathCost object. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.2.1.7,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortDesignatedRoot,OCTET,read-only,,current,,The unique Bridge Identifier of the Bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached.
.1.3.111.2.802.1.1.3.1.2.1.8,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortDesignatedCost,Integer32,read-only,,current,,The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received Bridge PDUs.
.1.3.111.2.802.1.1.3.1.2.1.9,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortDesignatedBridge,OCTET,read-only,,current,,The Bridge Identifier of the Bridge that this port considers to be the Designated Bridge for this port's segment.
.1.3.111.2.802.1.1.3.1.2.1.10,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortDesignatedPort,OCTET,read-only,,current,,The Port Identifier of the port on the Designated Bridge for this port's segment.
.1.3.111.2.802.1.1.3.1.2.1.11,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortForwardTransitions,Counter64,read-only,,current,,The number of times this port has transitioned from the Learning state to the Forwarding state. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.3.1.2.1.12,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortProtocolMigration,INTEGER,read-write,,current,true(1):false(2),When operating in RSTP (version 2) mode, writing true(1) to this object forces this port to transmit RSTP BPDUs. Any other operation on this object has no effect and it always returns false(2) when read.
.1.3.111.2.802.1.1.3.1.2.1.13,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortAdminEdgePort,INTEGER,read-write,,current,true(1):false(2),The administrative value of the Edge Port parameter. A value of true(1) indicates that this port should be assumed as an edge-port, and a value of false(2) indicates that this port should be assumed as a non-edge-port. Setting this object will also cause the corresponding instance of ieee8021SpanningTreeRstpPortOperEdgePort to change to the same value. Note that even when this object's value is true(1), the value of the corresponding instance of ieee8021SpanningTreeRstpPortOperEdgePort can be false(2) if a BPDU has been received. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.2.1.14,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortOperEdgePort,INTEGER,read-only,,current,true(1):false(2),The operational value of the Edge Port parameter. The object is initialized to the value of the corresponding instance of ieee8021SpanningTreeRstpPortAdminEdgePort. When the corresponding instance of ieee8021SpanningTreeRstpPortAdminEdgePort is set, this object will be changed as well. This object will also be changed to false(2) on reception of a BPDU.
.1.3.111.2.802.1.1.3.1.2.1.15,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortAdminPathCost,Integer32,read-write,,current,,The administratively assigned value for the contribution of this port to the path cost of paths toward the spanning tree root. Writing a value of '0' assigns the automatically calculated default Path Cost value to the port. If the default Path Cost is being used, this object returns '0' when read. This complements the object ieee8021SpanningTreePortPathCost, which returns the operational value of the path cost. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.3,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortExtensionTable,,not-accessible,,current,,A table that contains port-specific information for the Spanning Tree Protocol.
.1.3.111.2.802.1.1.3.1.3.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortExtensionEntry,,not-accessible,,current,,A list of additional objects containing information  maintained by every port about the Spanning Tree  Protocol state for that port.
.1.3.111.2.802.1.1.3.1.3.1.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortAutoEdgePort,INTEGER,read-write,,current,true(1):false(2),The administrative value of the Auto Edge Port parameter. A value of true(1) indicates if the Bridge detection state  machine (BDM, 13.31) is to detect other Bridges attached to the LAN, and set  ieee8021SpanningTreeRstpPortOperEdgePort automatically. The default value is true(1) This is optional and provided only by implementations  that support the automatic identification of edge ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.3.1.3.1.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortAutoIsolatePort,INTEGER,read-only,,current,true(1):false(2),The operational value of the Isolate Port parameter.  A value of true(1) indicates a Designated Port will  transition to discarding if both  ieee8021SpanningTreeRstpPortAdminEdgePort and  ieee8021SpanningTreeRstpPortAutoEdgePort are FALSE and  the other Bridge presumed to be attached to the same  point-to-point LAN does not transmit periodic BPDUs. This is optional and provided only by implementations  that support the automatic identification of edge ports.
.1.3.111.2.802.1.1.3.1.3.1.3,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortIsolatePort,INTEGER,read-only,,current,true(1):false(2),The operational value of the Isolate Port parameter.  A value of true(1), Set by the Bridge detection state  machine (BDM, 13.31), indicates when the Spanning Tree  Protocol Entity of a neighboring Bridge has apparently failed .
.1.3.111.2.802.1.1.3.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeConformance,,,,,,
.1.3.111.2.802.1.1.3.2.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeCompliances,,,,,,
.1.3.111.2.802.1.1.3.2.1.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeCompliance,,,,,,The compliance statement for devices supporting the Spanning Tree Protocol.
.1.3.111.2.802.1.1.3.2.1.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpCompliance,,,,,,The compliance statement for devices supporting RSTP.
.1.3.111.2.802.1.1.3.2.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeGroups,,,,,,
.1.3.111.2.802.1.1.3.2.2.1,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeGroup,,,,,,Bridge level Spanning Tree data for this device.
.1.3.111.2.802.1.1.3.2.2.2,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpGroup,,,,,,Bridge level Rstp data for this device.
.1.3.111.2.802.1.1.3.2.2.3,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreePortGroup,,,,,,Spanning Tree data for each port on this device.
.1.3.111.2.802.1.1.3.2.2.4,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpPortGroup,,,,,,Rstp data for each port on this device.
.1.3.111.2.802.1.1.3.2.2.5,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeNotificationGroup,,,,,,Group of notifications.
.1.3.111.2.802.1.1.3.2.2.6,IEEE8021-SPANNING-TREE-MIB::ieee8021SpanningTreeRstpFragileGroup,,,,,,Rstp fragile Bridge data for each port on this device.
.1.3.111.2.802.1.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeMib,,,,,,The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE Std 802.1Q. This MIB module is derived from the IETF Q-BRIDGE-MIB from RFC 4363. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.4.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeMibObjects,,,,,,
.1.3.111.2.802.1.1.4.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeBase,,,,,,
.1.3.111.2.802.1.1.4.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTable,,not-accessible,,current,,A table that contains generic information about every VLAN Bridge.
.1.3.111.2.802.1.1.4.1.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEntry,,not-accessible,ieee8021QBridgeComponentId,current,,A list of objects containing information for each VLAN Bridge.
.1.3.111.2.802.1.1.4.1.1.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.1.1.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanVersionNumber,INTEGER,read-only,,current,version1(1):version2(2),The version number of IEEE 802.1Q that this device supports. Reported as 1 by VLAN Bridges that support only SST operation, and reported as 2 by VLAN Bridges that support MST operation.
.1.3.111.2.802.1.1.4.1.1.1.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeMaxVlanId,Integer32,read-only,,current,,The maximum IEEE 802.1Q VLAN-ID that this device supports.
.1.3.111.2.802.1.1.4.1.1.1.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeMaxSupportedVlans,Unsigned32,read-only,,current,,The maximum number of IEEE 802.1Q VLANs that this device supports.
.1.3.111.2.802.1.1.4.1.1.1.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeNumVlans,Gauge32,read-only,,current,,The current number of IEEE 802.1Q VLANs that are configured in this device.
.1.3.111.2.802.1.1.4.1.1.1.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeMvrpEnabledStatus,INTEGER,read-write,,current,true(1):false(2),The administrative status requested by management for MVRP. The value true(1) indicates that MVRP should be enabled on this device, on all ports for which it has not been specifically disabled. When false(2), MVRP is disabled on all ports, and all MVRP packets will be forwarded transparently. This object affects all MVRP Applicant and Registrar state machines. A transition from false(2) to true(1) will cause a reset of all MVRP state machines on all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCVlanPortTable,,not-accessible,,current,,This table provides the capability to create and delete customer VLAN ports. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.4.1.1.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCVlanPortEntry,,not-accessible,ieee8021QBridgeCVlanPortComponentId:ieee8021QBridgeCVlanPortNumber,current,,A list of objects containing information for each VLAN Bridge.
.1.3.111.2.802.1.1.4.1.1.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCVlanPortComponentId,Unsigned32,not-accessible,,current,,The componentcontaining the customer VLAN port represented by this row.
.1.3.111.2.802.1.1.4.1.1.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCVlanPortNumber,Unsigned32,not-accessible,,current,,The customer VLAN port number represented by this row.
.1.3.111.2.802.1.1.4.1.1.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCVlanPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of the entry, and is used to create and delete entries in this table. Each entry in this table that is valid will have a corresponding entry in the ieee8021BridgeBasePortTable whose value for ieee8021BridgeBasePortType is customerVlanPort(2). The corresponding value of ieee8021BridgeBasePortIfIndex must be set at the time the value of this object transitions to valid(1). Entries in this table must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTp,,,,,,
.1.3.111.2.802.1.1.4.1.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbTable,,not-accessible,,current,,A table that contains configuration and control information for each Filtering Database currently operating on this device. Entries in this table appear automatically when VLANs are assigned FDB IDs in the ieee8021QBridgeVlanCurrentTable.
.1.3.111.2.802.1.1.4.1.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbEntry,,not-accessible,ieee8021QBridgeFdbComponentId:ieee8021QBridgeFdbId,current,,Information about a specific Filtering Database.
.1.3.111.2.802.1.1.4.1.2.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.2.1.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbId,Unsigned32,not-accessible,,current,,The identity of this Filtering Database.
.1.3.111.2.802.1.1.4.1.2.1.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbDynamicCount,Gauge32,read-only,,current,,The current number of dynamic entries in this Filtering Database.
.1.3.111.2.802.1.1.4.1.2.1.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbLearnedEntryDiscards,Counter64,read-only,,current,,The total number of Filtering Database entries that have been or would have been learned, but have been discarded due to a lack of storage space in the Filtering Database. If this counter is increasing, it indicates that the Filtering Database is regularly becoming full (a condition that has unpleasant performance effects on the subnetwork). If this counter has a significant value but is not presently increasing, it indicates that the problem has been occurring but is not persistent. Discontinuities in the value of the counter can occur at re-initialization of the management system.
.1.3.111.2.802.1.1.4.1.2.1.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbAgingTime,Integer32,read-write,,current,,The timeout period in seconds for aging out dynamically-learned forwarding information. IEEE Std 802.1D-1998 recommends a default of 300 seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.2.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the device has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.
.1.3.111.2.802.1.1.4.1.2.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpFdbEntry,,not-accessible,ieee8021QBridgeFdbComponentId:ieee8021QBridgeFdbId:ieee8021QBridgeTpFdbAddress,current,,Information about a specific unicast MAC address for which the device has some forwarding and/or filtering information.
.1.3.111.2.802.1.1.4.1.2.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpFdbAddress,OCTET,not-accessible,,current,,A unicast MAC address for which the device has forwarding and/or filtering information.
.1.3.111.2.802.1.1.4.1.2.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpFdbPort,Unsigned32,read-only,,current,,Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of ieee8021QBridgeTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned but that the device does have some forwarding/filtering information about this address (e.g., in the ieee8021QBridgeStaticUnicastTable). Implementors are encouraged to assign the port value to this object whenever it is learned, even for addresses for which the corresponding value of ieee8021QBridgeTpFdbStatus is not learned(3).
.1.3.111.2.802.1.1.4.1.2.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpFdbStatus,INTEGER,read-only,,current,other(1):invalid(2):learned(3):self(4):mgmt(5),The status of this entry. The meanings of the values are: other(1) - none of the following. This may include the case where some other MIB object (not the corresponding instance of ieee8021QBridgeTpFdbPort, nor an entry in the ieee8021QBridgeStaticUnicastTable) is being used to determine if and how frames addressed to the value of the corresponding instance of ieee8021QBridgeTpFdbAddress are being forwarded. invalid(2) - this entry is no longer valid (e.g., it was learned but has since aged out), but has not yet been flushed from the table. learned(3) - the value of the corresponding instance of ieee8021QBridgeTpFdbPort was learned and is being used. self(4) - the value of the corresponding instance of ieee8021QBridgeTpFdbAddress represents one of the device's addresses. The corresponding instance of ieee8021QBridgeTpFdbPort indicates which of the device's ports has this address. mgmt(5) - the value of the corresponding instance of ieee8021QBridgeTpFdbAddress is also the value of an existing instance of ieee8021QBridgeStaticUnicastAddress.
.1.3.111.2.802.1.1.4.1.2.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpGroupTable,,not-accessible,,current,,A table containing filtering information for VLANs configured into the Bridge by (local or network) management, or learned dynamically, specifying the set of ports to which frames received on a VLAN for this FDB and containing a specific Group destination address are allowed to be forwarded.
.1.3.111.2.802.1.1.4.1.2.3.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpGroupEntry,,not-accessible,ieee8021QBridgeVlanCurrentComponentId:ieee8021QBridgeVlanIndex:ieee8021QBridgeTpGroupAddress,current,,Filtering information configured into the Bridge by management, or learned dynamically, specifying the set of ports to which frames received on a VLAN and containing a specific Group destination address are allowed to be forwarded. The subset of these ports learned dynamically is also provided.
.1.3.111.2.802.1.1.4.1.2.3.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpGroupAddress,OCTET,not-accessible,,current,,The destination Group MAC address in a frame to which this entry's filtering information applies.
.1.3.111.2.802.1.1.4.1.2.3.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpGroupEgressPorts,OCTET,read-only,,current,,The complete set of ports, in this VLAN, to which frames destined for this Group MAC address are currently being explicitly forwarded. This does not include ports for which this address is only implicitly forwarded, in the ieee8021QBridgeForwardAllPorts list.
.1.3.111.2.802.1.1.4.1.2.3.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpGroupLearnt,OCTET,read-only,,current,,The subset of ports in ieee8021QBridgeTpGroupEgressPorts that were learned by MMRP or some other dynamic mechanism, in this Filtering database.
.1.3.111.2.802.1.1.4.1.2.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardAllTable,,not-accessible,,current,,A table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of all multicasts applies, configured statically by management or dynamically by MMRP. An entry appears in this table for all VLANs that are currently instantiated.
.1.3.111.2.802.1.1.4.1.2.4.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardAllEntry,,not-accessible,ieee8021QBridgeVlanCurrentComponentId:ieee8021QBridgeForwardAllVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which all multicasts should be forwarded, configured statically by management or dynamically by MMRP.
.1.3.111.2.802.1.1.4.1.2.4.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardAllVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier referring to this VLAN.
.1.3.111.2.802.1.1.4.1.2.4.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardAllPorts,OCTET,read-only,,current,,The complete set of ports in this VLAN to which all multicast group-addressed frames are to be forwarded. This includes ports for which this need has been determined dynamically by MMRP, or configured statically by management.
.1.3.111.2.802.1.1.4.1.2.4.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardAllStaticPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN to which all multicast group-addressed frames are to be forwarded. Ports entered in this list will also appear in the complete set shown by ieee8021QBridgeForwardAllPorts. This value will be restored after the device is reset. This only applies to ports that are members of the VLAN, defined by ieee8021QBridgeVlanCurrentEgressPorts. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeForwardAllForbiddenPorts. The default value is a string of ones of appropriate length, to indicate the standard behavior of using basic filtering services, i.e., forward all multicasts to all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.2.4.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardAllForbiddenPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward All Multicast Groups may not be dynamically registered by MMRP. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeForwardAllStaticPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.2.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardUnregisteredTable,,not-accessible,,current,,A table containing forwarding information for each VLAN, specifying the set of ports to which forwarding of multicast group-addressed frames for which no more specific forwarding information applies. This is configured statically by management and determined dynamically by MMRP. An entry appears in this table for all VLANs that are currently instantiated.
.1.3.111.2.802.1.1.4.1.2.5.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardUnregisteredEntry,,not-accessible,ieee8021QBridgeVlanCurrentComponentId:ieee8021QBridgeForwardUnregisteredVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which all multicasts for which there is no more specific forwarding information shall be forwarded. This is configured statically by management or dynamically by MMRP.
.1.3.111.2.802.1.1.4.1.2.5.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardUnregisteredVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier referring to this VLAN.
.1.3.111.2.802.1.1.4.1.2.5.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardUnregisteredPorts,OCTET,read-only,,current,,The complete set of ports in this VLAN to which multicast group-addressed frames for which there is no more specific forwarding information will be forwarded. This includes ports for which this need has been determined dynamically by MMRP, or configured statically by management.
.1.3.111.2.802.1.1.4.1.2.5.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardUnregisteredStaticPorts,OCTET,read-write,,current,,The set of ports configured by management, in this VLAN, to which multicast group-addressed frames for which there is no more specific forwarding information are to be forwarded. Ports entered in this list will also appear in the complete set shown by ieee8021QBridgeForwardUnregisteredPorts. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeForwardUnregisteredForbiddenPorts. The default value is a string of zeros of appropriate length, although this has no effect with the default value of ieee8021QBridgeForwardAllStaticPorts. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.2.5.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeForwardUnregisteredForbiddenPorts,OCTET,read-write,,current,,The set of ports configured by management in this VLAN for which the Service Requirement attribute Forward Unregistered Multicast Groups may not be dynamically registered by MMRP. This value will be restored after the device is reset. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeForwardUnregisteredStaticPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStatic,,,,,,
.1.3.111.2.802.1.1.4.1.3.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastTable,,not-accessible,,current,,A table containing filtering information for Unicast MAC addresses for each Filtering Database, configured into the device by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific unicast destination addresses are allowed to be forwarded.  Entries are valid for unicast addresses only. Two modes of operation are supported by this table. When the receive port index is non-zero, this table is supporting an IEEE 802.1D filtering database as specified in 14.7.6.1 of IEEE Std 802.1D. If the receive port is zero, the table is operating as specified in IEEE Std 802.1Q  8.8.1 and 12.7.7. An agent must at least  support the IEEE Std 802.1Q mode of operation.
.1.3.111.2.802.1.1.4.1.3.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastEntry,,not-accessible,ieee8021QBridgeStaticUnicastComponentId:ieee8021QBridgeStaticUnicastVlanIndex:ieee8021QBridgeStaticUnicastAddress:ieee8021QBridgeStaticUnicastReceivePort,current,,Filtering information configured into the device by (local or network) management specifying the set of ports to which frames received from a specific port and containing a specific unicast destination address are allowed to be forwarded.
.1.3.111.2.802.1.1.4.1.3.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.3.1.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastVlanIndex,Unsigned32,not-accessible,,current,,The Vlan to which this entry applies.
.1.3.111.2.802.1.1.4.1.3.1.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastAddress,OCTET,not-accessible,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object must take the value of a unicast address.
.1.3.111.2.802.1.1.4.1.3.1.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastReceivePort,Unsigned32,not-accessible,,current,,Either the value '0' or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which there is no other applicable entry. An implementation is required to support the '0' value and may optionally support non-zero values for this column.
.1.3.111.2.802.1.1.4.1.3.1.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastStaticEgressPorts,OCTET,read-create,,current,,The set of ports to which frames received from a specific port and destined for a specific unicast address must be forwarded, regardless of any dynamic information, e.g., from MMRP. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeStaticUnicastForbiddenEgressPorts. The default value of this object is a string of ones of appropriate length.
.1.3.111.2.802.1.1.4.1.3.1.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastForbiddenEgressPorts,OCTET,read-create,,current,,The set of ports to which frames received from a specific port and destined for a specific unicast MAC address must not be forwarded, regardless of any dynamic information, e.g., from MMRP. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeStaticUnicastStaticEgressPorts. The default value of this object is a string of zeros of appropriate length.
.1.3.111.2.802.1.1.4.1.3.1.1.7,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. If this object has a value of permanent(4), then no other objects are required to be able to be modified.
.1.3.111.2.802.1.1.4.1.3.1.1.8,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticUnicastRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry, and is used to create/delete entries in the table. An entry of this table may be set to active without setting any other columns of the table. Also, other columns of this table may be set while the value of this object is active(1).
.1.3.111.2.802.1.1.4.1.3.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastTable,,not-accessible,,current,,A table containing filtering information for Multicast and Broadcast MAC addresses for each VLAN, configured into the device by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific Multicast and Broadcast destination addresses are allowed to be forwarded. A value of zero in this table (as the port number from which frames with a specific destination address are received) is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for Multicast and Broadcast addresses only.
.1.3.111.2.802.1.1.4.1.3.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastEntry,,not-accessible,ieee8021QBridgeVlanCurrentComponentId:ieee8021QBridgeVlanIndex:ieee8021QBridgeStaticMulticastAddress:ieee8021QBridgeStaticMulticastReceivePort,current,,Filtering information configured into the device by (local or network) management specifying the set of ports to which frames received from this specific port for this VLAN and containing this Multicast or Broadcast destination address are allowed to be forwarded.
.1.3.111.2.802.1.1.4.1.3.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastAddress,OCTET,not-accessible,,current,,The destination MAC address in a frame to which this entry's filtering information applies. This object must take the value of a Multicast or Broadcast address.
.1.3.111.2.802.1.1.4.1.3.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastReceivePort,Unsigned32,not-accessible,,current,,Either the value '0' or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the device for which there is no other applicable entry. An implementation is required to support the '0' value and may optionally support non-zero values for this column.
.1.3.111.2.802.1.1.4.1.3.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastStaticEgressPorts,OCTET,read-create,,current,,The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC address must be forwarded, regardless of any dynamic information, e.g., from MMRP. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeStaticMulticastForbiddenEgressPorts. The default value of this object is a string of ones of appropriate length.
.1.3.111.2.802.1.1.4.1.3.2.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastForbiddenEgressPorts,OCTET,read-create,,current,,The set of ports to which frames received from a specific port and destined for a specific Multicast or Broadcast MAC address must not be forwarded, regardless of any dynamic information, e.g., from MMRP. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeStaticMulticastStaticEgressPorts. The default value of this object is a string of zeros of appropriate length.
.1.3.111.2.802.1.1.4.1.3.2.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this conceptual row. If this object has a value of permanent(4), then no other objects are required to be able to be modified.
.1.3.111.2.802.1.1.4.1.3.2.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeStaticMulticastRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry, and is used to create/delete entries in the table. An entry of this table may be set to active without setting any other columns of the table. Also, other columns of this table may be set while the value of this object is active(1).
.1.3.111.2.802.1.1.4.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlan,,,,,,
.1.3.111.2.802.1.1.4.1.4.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanNumDeletes,Counter64,read-only,,current,,The number of times a VLAN entry has been deleted from the ieee8021QBridgeVlanCurrentTable (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. Discontinuities in this value can only occur at a reboot.
.1.3.111.2.802.1.1.4.1.4.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanCurrentTable,,not-accessible,,current,,A table containing current configuration information for each VLAN currently configured into the device by (local or network) management, or dynamically created as a result of MVRP requests received.
.1.3.111.2.802.1.1.4.1.4.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanCurrentEntry,,not-accessible,ieee8021QBridgeVlanTimeMark:ieee8021QBridgeVlanCurrentComponentId:ieee8021QBridgeVlanIndex,current,,Information for a VLAN configured into the device by (local or network) management, or dynamically created as a result of MVRP requests received.
.1.3.111.2.802.1.1.4.1.4.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention to see how this works.
.1.3.111.2.802.1.1.4.1.4.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanCurrentComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.4.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier referring to this VLAN.
.1.3.111.2.802.1.1.4.1.4.2.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanFdbId,Unsigned32,read-only,,current,,The Filtering Database used by this VLAN. This is one of the ieee8021QBridgeFdbId values in the ieee8021QBridgeFdbTable. This value is allocated automatically by the device whenever the VLAN is created: either dynamically by MVRP, or by management, in ieee8021QBridgeVlanStaticTable. Allocation of this value follows the learning constraints defined for this VLAN in ieee8021QBridgeLearningConstraintsTable.
.1.3.111.2.802.1.1.4.1.4.2.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanCurrentEgressPorts,OCTET,read-only,,current,,The set of ports that are transmitting traffic for this VLAN as either tagged or untagged frames.
.1.3.111.2.802.1.1.4.1.4.2.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanCurrentUntaggedPorts,OCTET,read-only,,current,,The set of ports that are transmitting traffic for this VLAN as untagged frames.
.1.3.111.2.802.1.1.4.1.4.2.1.7,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStatus,INTEGER,read-only,,current,other(1):permanent(2):dynamicMvrp(3),This object indicates the status of this entry. other(1) - this entry is currently in use, but the conditions under which it will remain so differ from the following values. permanent(2) - this entry, corresponding to an entry in ieee8021QBridgeVlanStaticTable, is currently in use and will remain so after the next reset of the device. The port lists for this entry include ports from the equivalent ieee8021QBridgeVlanStaticTable entry and ports learned dynamically. dynamicMvrp(3) - this entry is currently in use and will remain so until removed by MVRP. There is no static entry for this VLAN, and it will be removed when the last port leaves the VLAN.
.1.3.111.2.802.1.1.4.1.4.2.1.8,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanCreationTime,TimeTicks,read-only,,current,,The value of sysUpTime when this VLAN was created.
.1.3.111.2.802.1.1.4.1.4.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticTable,,not-accessible,,current,,A table containing static configuration information for each VLAN configured into the device by (local or network) management. All entries are persistent and will be restored after the device is reset.
.1.3.111.2.802.1.1.4.1.4.3.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticEntry,,not-accessible,ieee8021QBridgeVlanStaticComponentId:ieee8021QBridgeVlanStaticVlanIndex,current,,Static information for a VLAN configured into the device by (local or network) management.
.1.3.111.2.802.1.1.4.1.4.3.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.4.3.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier referring to this VLAN.
.1.3.111.2.802.1.1.4.1.4.3.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticName,OCTET,read-create,,current,,An administratively assigned string, which may be used to identify the VLAN.
.1.3.111.2.802.1.1.4.1.4.3.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticEgressPorts,OCTET,read-create,,current,,The set of ports that are permanently assigned to the egress list for this VLAN by management. Changes to a bit in this object affect the per-port, per-VLAN Registrar control for Registration Fixed for the relevant MVRP state machine on each port. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeVlanForbiddenEgressPorts. The default value of this object is a string of zeros of appropriate length, indicating not fixed.
.1.3.111.2.802.1.1.4.1.4.3.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanForbiddenEgressPorts,OCTET,read-create,,current,,The set of ports that are prohibited by management from being included in the egress list for this VLAN. Changes to this object that cause a port to be included or excluded affect the per-port, per-VLAN Registrar control for Registration Forbidden for the relevant MVRP state machine on each port. A port may not be added in this set if it is already a member of the set of ports in ieee8021QBridgeVlanStaticEgressPorts. The default value of this object is a string of zeros of appropriate length, excluding all ports from the forbidden set.
.1.3.111.2.802.1.1.4.1.4.3.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticUntaggedPorts,OCTET,read-create,,current,,The set of ports that should transmit egress packets for this VLAN as untagged. The default value of this object for the default VLAN (ieee8021QBridgeVlanIndex = 1) is a string of appropriate length including all ports. There is no specified default for other VLANs. If a device agent cannot support the set of ports being set, then it will reject the set operation with an error. For example, a manager might attempt to set more than one VLAN to be untagged on egress where the device does not support this IEEE 802.1Q option.
.1.3.111.2.802.1.1.4.1.4.3.1.7,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry, and is used to create/delete entries. Any object in an entry of this table may be modified while the value of the corresponding instance of this object is active(1).
.1.3.111.2.802.1.1.4.1.4.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeNextFreeLocalVlanTable,,not-accessible,,current,,A table that contains information about the next free VLAN value for a statically configured VLAN Bridge.
.1.3.111.2.802.1.1.4.1.4.4.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeNextFreeLocalVlanEntry,,not-accessible,ieee8021QBridgeNextFreeLocalVlanComponentId,current,,The next free VLAN value for a statically configured VLAN Bridge
.1.3.111.2.802.1.1.4.1.4.4.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeNextFreeLocalVlanComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.4.4.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeNextFreeLocalVlanIndex,Unsigned32,read-only,,current,,The next available value for ieee8021QBridgeVlanIndex of a local VLAN entry in ieee8021QBridgeVlanStaticTable. This will report values >=4096 if a new Local VLAN may be created or else the value 0 if this is not possible. A row creation operation in this table for an entry with a local VlanIndex value may fail if the current value of this object is not used as the index. Even if the value read is used, there is no guarantee that it will still be the valid index when the create operation is attempted; another manager may have already got in during the intervening time interval. In this case, ieee8021QBridgeNextFreeLocalVlanIndex should be re-read and the creation re-tried with the new value. This value will automatically change when the current value is used to create a new row.
.1.3.111.2.802.1.1.4.1.4.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortVlanTable,,not-accessible,,current,,A table containing per-port control and status information for VLAN configuration in the device.
.1.3.111.2.802.1.1.4.1.4.5.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortVlanEntry,,not-accessible,,current,,Information controlling VLAN configuration for a port on the device. This is indexed by ieee8021BridgeBasePort.
.1.3.111.2.802.1.1.4.1.4.5.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePvid,Unsigned32,read-write,,current,,The PVID, the VLAN-ID assigned to untagged frames or Priority-tagged frames received on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.4.5.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortAcceptableFrameTypes,INTEGER,read-write,,current,admitAll(1):admitUntaggedAndPriority(2):admitTagged(3),When this is admitTagged(3), the device will discard untagged frames or Priority-tagged frames received on this port. When admitAll(1), untagged frames or Priority-tagged frames received on this port will be accepted and assigned to a VID based on the PVID and VID Set for this port. This control does not affect VLAN-independent Bridge Protocol Data Unit (BPDU) frames, such as MVRP and Spanning Tree Protocol (STP). It does affect VLAN- dependent BPDU frames, such as MMRP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.4.5.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortIngressFiltering,INTEGER,read-write,,current,true(1):false(2),When this is true(1), the device will discard incoming frames for VLANs that do not include this Port in its Member set. When false(2), the port will accept all incoming frames. This control does not affect VLAN-independent BPDU frames, such as MVRP and STP. It does affect VLAN- dependent BPDU frames, such as MMRP. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.4.5.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortMvrpEnabledStatus,INTEGER,read-write,,current,true(1):false(2),The state of MVRP operation on this port. The value true(1) indicates that MVRP is enabled on this port, as long as ieee8021QBridgeMvrpEnabledStatus is also enabled for this device. When false(2) but ieee8021QBridgeMvrpEnabledStatus is still enabled for the device, MVRP is disabled on this port: any MVRP packets received will be silently discarded, and no MVRP registrations will be propagated from other ports. This object affects all MVRP Applicant and Registrar state machines on this port. A transition from false(2) to true(1) will cause a reset of all MVRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.4.5.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortMvrpFailedRegistrations,Counter64,read-only,,current,,The total number of failed MVRP registrations, for any reason, on this port. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.4.1.4.5.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortMvrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last MVRP message received on this port.
.1.3.111.2.802.1.1.4.1.4.5.1.7,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortRestrictedVlanRegistration,INTEGER,read-write,,current,true(1):false(2),The state of Restricted VLAN Registration on this port. If the value of this control is true(1), then creation of a new dynamic VLAN entry is permitted only if there is a Static VLAN Registration Entry for the VLAN concerned, in which the Registrar Administrative Control value for this port is Normal Registration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.4.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortVlanStatisticsTable,,not-accessible,,current,,A table containing per-port, per-VLAN statistics for traffic received.
.1.3.111.2.802.1.1.4.1.4.6.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortVlanStatisticsEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021QBridgeVlanIndex,current,,Traffic statistics for a VLAN on an interface.
.1.3.111.2.802.1.1.4.1.4.6.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpVlanPortInFrames,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN. Note that a frame received on this port is counted by this object if and only if it is for a protocol being processed by the local forwarding process for this VLAN. This object includes received Bridge management frames classified as belonging to this VLAN (e.g., MMRP, but not MVRP or STP. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.4.1.4.6.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpVlanPortOutFrames,Counter64,read-only,,current,,The number of valid frames transmitted by this port to its segment from the local forwarding process for this VLAN. This includes Bridge management frames originated by this device that are classified as belonging to this VLAN (e.g., MMRP, but not MVRP or STP). Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.4.1.4.6.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeTpVlanPortInDiscards,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN and that were discarded due to VLAN-related reasons. Specifically, the IEEE 802.1Q counters for Discard Inbound and Discard on Ingress Filtering. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.4.1.4.8,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsTable,,not-accessible,,deprecated,,A table containing learning constraints for sets of Shared and Independent VLANs. Entries in this table are persistent and are preserved across reboots.
.1.3.111.2.802.1.1.4.1.4.8.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsEntry,,not-accessible,ieee8021QBridgeLearningConstraintsComponentId:ieee8021QBridgeLearningConstraintsVlan:ieee8021QBridgeLearningConstraintsSet,deprecated,,A learning constraint defined for a VLAN.
.1.3.111.2.802.1.1.4.1.4.8.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsComponentId,Unsigned32,not-accessible,,deprecated,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.4.8.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsVlan,Unsigned32,not-accessible,,deprecated,,The index of the row in ieee8021QBridgeVlanCurrentTable for the VLAN constrained by this entry.
.1.3.111.2.802.1.1.4.1.4.8.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsSet,Integer32,not-accessible,,deprecated,,The identity of the constraint set to which ieee8021QBridgeLearningConstraintsVlan belongs. These values may be chosen by the management station.
.1.3.111.2.802.1.1.4.1.4.8.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsType,INTEGER,read-create,,deprecated,independent(1):shared(2),The type of constraint this entry defines. independent(1) - the VLAN, ieee8021QBridgeLearningConstraintsVlan, uses a filtering database independent from all other VLANs in the same set, defined by ieee8021QBridgeLearningConstraintsSet. shared(2) - the VLAN, ieee8021QBridgeLearningConstraintsVlan, shares the same filtering database as all other VLANs in the same set, defined by ieee8021QBridgeLearningConstraintsSet.
.1.3.111.2.802.1.1.4.1.4.8.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this entry. Any object in an entry of this table may be modified while the value of the corresponding instance of this object is active(1).
.1.3.111.2.802.1.1.4.1.4.9,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintDefaultsTable,,not-accessible,,deprecated,,A table containing learning constraints for sets of Shared and Independent VLANs.
.1.3.111.2.802.1.1.4.1.4.9.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintDefaultsEntry,,not-accessible,ieee8021QBridgeLearningConstraintDefaultsComponentId,deprecated,,A learning constraint defined for a VLAN.
.1.3.111.2.802.1.1.4.1.4.9.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintDefaultsComponentId,Unsigned32,not-accessible,,deprecated,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.4.9.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintDefaultsSet,Integer32,read-write,,deprecated,,The identity of the constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in ieee8021QBridgeLearningConstraintsTable. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.4.9.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintDefaultsType,INTEGER,read-write,,deprecated,independent(1):shared(2),The type of constraint set to which a VLAN belongs, if there is not an explicit entry for that VLAN in ieee8021QBridgeLearningConstraintsTable. The types are as defined for ieee8021QBridgeLearningConstraintsType. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.4.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocol,,,,,,
.1.3.111.2.802.1.1.4.1.5.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolGroupTable,,not-accessible,,current,,A table that contains mappings from Protocol Templates to Protocol Group Identifiers used for Port-and-Protocol-based VLAN Classification. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.4.1.5.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolGroupEntry,,not-accessible,ieee8021QBridgeProtocolGroupComponentId:ieee8021QBridgeProtocolTemplateFrameType:ieee8021QBridgeProtocolTemplateProtocolValue,current,,A mapping from a Protocol Template to a Protocol Group Identifier.
.1.3.111.2.802.1.1.4.1.5.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolGroupComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.4.1.5.1.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolTemplateFrameType,INTEGER,not-accessible,,current,ethernet(1):rfc1042(2):snap8021H(3):snapOther(4):llcOther(5),The data-link encapsulation format or the 'detagged_frame_type' in a Protocol Template.
.1.3.111.2.802.1.1.4.1.5.1.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolTemplateProtocolValue,OCTET,not-accessible,,current,,The identification of the protocol above the data-link layer in a Protocol Template. Depending on the frame type, the octet string will have one of the following values: For 'ethernet', 'rfc1042' and 'snap8021H', this is the 16-bit (2-octet) IEEE 802.3 Type Field. For 'snapOther', this is the 40-bit (5-octet) PID. For 'llcOther', this is the 2-octet IEEE 802.2 Link Service Access Point (LSAP) pair: first octet for Destination Service Access Point (DSAP) and second octet for Source Service Access Point (SSAP).
.1.3.111.2.802.1.1.4.1.5.1.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolGroupId,Integer32,read-create,,current,,Represents a group of protocols that are associated together when assigning a VID to a frame.
.1.3.111.2.802.1.1.4.1.5.1.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolGroupRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.111.2.802.1.1.4.1.5.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolPortTable,,not-accessible,,current,,A table that contains VID sets used for Port-and-Protocol-based VLAN Classification.
.1.3.111.2.802.1.1.4.1.5.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolPortEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021QBridgeProtocolPortGroupId,current,,A VID set for a port.
.1.3.111.2.802.1.1.4.1.5.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolPortGroupId,Integer32,not-accessible,,current,,Designates a group of protocols in the Protocol Group Database.
.1.3.111.2.802.1.1.4.1.5.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolPortGroupVid,Integer32,read-create,,current,,The VID associated with a group of protocols for each port.
.1.3.111.2.802.1.1.4.1.5.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeProtocolPortRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of this entry.
.1.3.111.2.802.1.1.4.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDX,,,,,,
.1.3.111.2.802.1.1.4.1.6.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDXTable,,not-accessible,,current,,This table is used to configure the VID Translation Table defined in 12.10.1.8 and 6.9. The Bridge VID Translation Table is used to implement a mapping between a local VID, and a relay VID, used by the filtering and forwarding process. Each row in this table is indexed by component, port, and local VID value and a value to be used for the specified VID as specified in (6.9). Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.4.1.6.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDXEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021QBridgeVIDXLocalVid,current,,An entry for the S-VID translation table which includes  both the Local and Relay S-VIDs.
.1.3.111.2.802.1.1.4.1.6.1.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDXLocalVid,Integer32,not-accessible,,current,,The Local VID after translation received at the ISS or EISS.
.1.3.111.2.802.1.1.4.1.6.1.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDXRelayVid,Integer32,read-create,,current,,The Relay VID received before translation received at ISS or EISS.
.1.3.111.2.802.1.1.4.1.6.1.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDXRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. It is an  implementation specific decision as to whether  any column in this table may be set while the  corresponding instance of this object is valid(1).
.1.3.111.2.802.1.1.4.1.6.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXTable,,not-accessible,,deprecated,,This table is used to configure the VID Translation Table defined in 12.10.1.9 and 6.9. The Bridge VID Egress Translation Table is used to implement a mapping between a relay VID, and a local VID, used by the filtering and forwarding process. Each row in this table is indexed by component, port, and relay VID value and a value to be used for the specified local VID as specified in (6.9). Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.4.1.6.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021QBridgeEgressVidXRelayVid,deprecated,,An entry for the Egress VID translation table which includes  both the relay and local IDs between which the PNP or CNP translates.
.1.3.111.2.802.1.1.4.1.6.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXRelayVid,Integer32,not-accessible,,deprecated,,The Relay VID after translation transmitted to the  ISS or EISS.
.1.3.111.2.802.1.1.4.1.6.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXLocalVid,Integer32,read-create,,deprecated,,The Local VID before translation transmitted to the  ISS or EISS.
.1.3.111.2.802.1.1.4.1.6.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. It is an  implementation specific decision as to whether  any column in this table may be set while the  corresponding instance of this object is valid(1).
.1.3.111.2.802.1.1.4.1.6.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXV2Table,,not-accessible,,current,,This table is used to configure the VID Translation Table defined in 12.10.1.9 and 6.9. The Bridge VID Egress Translation Table is used to implement a mapping between a relay VID, and a local VID, used by the filtering and forwarding process. Each row in this table is indexed by component, port, and relay VID value and a value to be used for the specified local VID as specified in (6.9). Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.4.1.6.3.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXV2Entry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021QBridgeEgressVidXV2RelayVid,current,,An entry for the Egress VID translation table which includes  both the relay and local IDs between which the PNP or CNP translates.
.1.3.111.2.802.1.1.4.1.6.3.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXV2RelayVid,Integer32,not-accessible,,current,,The Relay VID after translation transmitted to the  ISS or EISS.
.1.3.111.2.802.1.1.4.1.6.3.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXV2LocalVid,Integer32,read-create,,current,,The Local VID before translation transmitted to the  ISS or EISS.
.1.3.111.2.802.1.1.4.1.6.3.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVidXV2RowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. It is an  implementation specific decision as to whether  any column in this table may be set while the  corresponding instance of this object is valid(1).
.1.3.111.2.802.1.1.4.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeConformance,,,,,,
.1.3.111.2.802.1.1.4.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeGroups,,,,,,
.1.3.111.2.802.1.1.4.2.1.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeBaseGroup,,,,,,A collection of objects providing device-level control and status information for the VLAN Bridge services.
.1.3.111.2.802.1.1.4.2.1.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbUnicastGroup,,,,,,A collection of objects providing information about all unicast addresses, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.111.2.802.1.1.4.2.1.3,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbMulticastGroup,,,,,,A collection of objects providing information about all multicast addresses, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.111.2.802.1.1.4.2.1.4,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeServiceRequirementsGroup,,,,,,A collection of objects providing information about service requirements, learned dynamically or statically configured by management, in each Filtering Database.
.1.3.111.2.802.1.1.4.2.1.5,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeFdbStaticGroup,,,,,,A collection of objects providing information about unicast and multicast addresses statically configured by management, in each Filtering Database or VLAN.
.1.3.111.2.802.1.1.4.2.1.6,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanGroup,,,,,,A collection of objects providing information about all VLANs currently configured on this device.
.1.3.111.2.802.1.1.4.2.1.7,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStaticGroup,,,,,,A collection of objects providing information about VLANs statically configured by management.
.1.3.111.2.802.1.1.4.2.1.8,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVlanStatisticsGroup,,,,,,A collection of objects providing per-port packet statistics for all VLANs currently configured on this device.
.1.3.111.2.802.1.1.4.2.1.9,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintsGroup,,,,,,A collection of objects defining the Filtering Database constraints all VLANs have with each other.
.1.3.111.2.802.1.1.4.2.1.10,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeLearningConstraintDefaultGroup,,,,,,A collection of objects defining the default Filtering Database constraints for VLANs that have no specific constraints defined.
.1.3.111.2.802.1.1.4.2.1.11,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeClassificationDeviceGroup,,,,,,VLAN classification information for the Bridge.
.1.3.111.2.802.1.1.4.2.1.12,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeClassificationPortGroup,,,,,,VLAN classification information for individual ports.
.1.3.111.2.802.1.1.4.2.1.13,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgePortGroup2,,,,,,A collection of objects providing port-level VLAN control and status information for all ports.
.1.3.111.2.802.1.1.4.2.1.14,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCVlanPortGroup,,,,,,Objects used to create/delete customer VLAN ports.
.1.3.111.2.802.1.1.4.2.1.15,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeVIDXGroup,,,,,,Ingress or Ingress/Egress VID translation for  individual ports.
.1.3.111.2.802.1.1.4.2.1.16,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVIDXGroup,,,,,,Egress VID translation for individual ports.
.1.3.111.2.802.1.1.4.2.1.17,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeEgressVIDXV2Group,,,,,,Egress VID translation for individual ports.
.1.3.111.2.802.1.1.4.2.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCompliances,,,,,,
.1.3.111.2.802.1.1.4.2.2.1,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeCompliance,,,,,,The compliance statement for device support of Virtual LAN Bridge services.
.1.3.111.2.802.1.1.4.2.2.2,IEEE8021-Q-BRIDGE-MIB::ieee8021QBridgeComplianceV2,,,,,,The compliance statement for device support of Virtual LAN Bridge services.
.1.3.111.2.802.1.1.5,IEEE8021-PB-MIB::ieee8021PbMib,,,,,,Provider Bridge MIB module. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.5.0,IEEE8021-PB-MIB::ieee8021PbNotifications,,,,,,
.1.3.111.2.802.1.1.5.1,IEEE8021-PB-MIB::ieee8021PbObjects,,,,,,
.1.3.111.2.802.1.1.5.1.1,IEEE8021-PB-MIB::ieee8021PbVidTranslationTable,,not-accessible,,deprecated,,This table is used to configure the VID Translation Table defined in 12.10.1.8. The VID Translation Table is used to implement a bidirectional mapping between a local S-VID, used in data and protocol frames transmitted and received through a CNP or PNP, and a relay S-VID, used by the filtering and forwarding process. Each row in this table is indexed by component, port, and local S-VID value and indicates the relay S-VID value to be used for the specified S-VID. If no entry for a component, port, and local-svid is present in this table is present then the relay S-VID used for a frame received on that port with the local S-VID value will be the S-VID that has the same numeric value as the local S-VID of the received frame. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.5.1.1.1,IEEE8021-PB-MIB::ieee8021PbVidTranslationEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021PbVidTranslationLocalVid,deprecated,,An entry for the S-VID translation table which includes  both the Local and Relay S-VIDs between which the PNP or CNP translates. Note that the component ID of entries in this table must refer to the S-VLAN Component of a Provider Bridge.
.1.3.111.2.802.1.1.5.1.1.1.1,IEEE8021-PB-MIB::ieee8021PbVidTranslationLocalVid,Integer32,not-accessible,,deprecated,,The S-VID on received(transmitted) at the ISS of a CNP or PNP.
.1.3.111.2.802.1.1.5.1.1.1.2,IEEE8021-PB-MIB::ieee8021PbVidTranslationRelayVid,Integer32,read-create,,deprecated,,The translated S-VID delivered(received) over the EISS from a CNP or PNP. The default value of this object on creation will be the value of the corresponding instance of ieee8021PbVidTranslationLocalVid.
.1.3.111.2.802.1.1.5.1.1.1.3,IEEE8021-PB-MIB::ieee8021PbVidTranslationRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. It is an implementation specific decision as to whether any column in this table may be set while the corresponding instance of this object is valid(1).
.1.3.111.2.802.1.1.5.1.2,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationTable,,not-accessible,,current,,A table used in a CEP to create the mapping between a C-VID and a service represented by an S-VID. Note that the component ID of entries in this table must refer to the S-VLAN component of a Provider Edge Bridge and the Port Number must refer to the port number of the Customer Edge Port associated with that Provider Edge Bridge. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.5.1.2.1,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021PbCVidRegistrationCVid,current,,An element of the C-VID registration table accessed by PB C-VLAN component, Customer Edge Port Bridge Port number, and C-VID. Each element contains the mapping between a C-VID and the S-VID which carries the service and booleans for handling untagged frames at the PEP and CEP.
.1.3.111.2.802.1.1.5.1.2.1.1,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationCVid,Integer32,not-accessible,,current,,C-VID of this C-VID registration entry.
.1.3.111.2.802.1.1.5.1.2.1.2,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationSVid,Integer32,read-create,,current,,S-VID for this C-VID registration entry.
.1.3.111.2.802.1.1.5.1.2.1.3,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationUntaggedPep,INTEGER,read-create,,current,true(1):false(2),A flag indicating if this C-VID should be carried untagged at the PEP. A value of true(1) means untagged.
.1.3.111.2.802.1.1.5.1.2.1.4,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationUntaggedCep,INTEGER,read-create,,current,true(1):false(2),A flag indicating if this C-VID should be carried untagged at the CEP. A value of true(1) means untagged.
.1.3.111.2.802.1.1.5.1.2.1.5,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. The value of ieee8021PbCVidRegistrationSVid must be set before an entry in this table can be made valid. It is an implementation specific decision as to whether any column in this table may be set while the corresponding instance of this object is valid(1).
.1.3.111.2.802.1.1.5.1.3,IEEE8021-PB-MIB::ieee8021PbEdgePortTable,,not-accessible,,current,,A Provider Edge Port (PEP) table which indicate the subset of parameters needed for each PEP.
.1.3.111.2.802.1.1.5.1.3.1,IEEE8021-PB-MIB::ieee8021PbEdgePortEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021PbEdgePortSVid,current,,An entry in the PEP table indexed by ComponentID and S-VID and containing parameters used to configure ingress filtering on the PEP, thus affecting traffic transiting from the provider network to the customer edge port. The columns allow the default C-VID value and default priority to be specified and PEP's ingress filtering operation to be controlled. Note that the component ID of entries in this table must refer to an S-VLAN component of a provider edge Bridge and the Bridge Port number must refer to the port number of a Customer Edge Port associated with that Provider Edge Bridge.
.1.3.111.2.802.1.1.5.1.3.1.1,IEEE8021-PB-MIB::ieee8021PbEdgePortSVid,Integer32,not-accessible,,current,,The 12 bit S-VID associated with the PEP.
.1.3.111.2.802.1.1.5.1.3.1.2,IEEE8021-PB-MIB::ieee8021PbEdgePortPVID,Integer32,read-write,,current,,A 12-bit C-VID to be used for untagged frames received at the Provider Edge Port.
.1.3.111.2.802.1.1.5.1.3.1.3,IEEE8021-PB-MIB::ieee8021PbEdgePortDefaultUserPriority,Unsigned32,read-write,,current,,An integer range 0-7 to be used for untagged frames received at the Provider Edge Port.
.1.3.111.2.802.1.1.5.1.3.1.4,IEEE8021-PB-MIB::ieee8021PbEdgePortAcceptableFrameTypes,INTEGER,read-write,,current,admitAll(1):admitUntaggedAndPriority(2):admitTagged(3),the Acceptable Frame Types for frames received at the PEP. The permissible values for the parameter are: 1) Admit all frames; 2) Admit only untagged and Priority-tagged frames; 3) Admit only VLAN-tagged frames.
.1.3.111.2.802.1.1.5.1.3.1.5,IEEE8021-PB-MIB::ieee8021PbEdgePortEnableIngressFiltering,INTEGER,read-write,,current,true(1):false(2),Filtering parameter for frames received at the PEP. The permissible values for the parameter are: true(1) Enabled; false(2) Disabled.
.1.3.111.2.802.1.1.5.1.4,IEEE8021-PB-MIB::ieee8021PbServicePriorityRegenerationTable,,not-accessible,,current,,The priority regeneration table for this PEP.
.1.3.111.2.802.1.1.5.1.4.1,IEEE8021-PB-MIB::ieee8021PbServicePriorityRegenerationEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021PbServicePriorityRegenerationSVid:ieee8021PbServicePriorityRegenerationReceivedPriority,current,,An element of the PEP priority regeneration table indexed by Component ID, Bridge Port number, S-VID, and received priority. Each element contains the regenerated priority. Note that the component ID of entries in this table must refer to the S-VLAN component of a Provider Edge Bridge and the Port Number must refer to the port number of the Customer Edge Port associated with that S-VLAN component.
.1.3.111.2.802.1.1.5.1.4.1.1,IEEE8021-PB-MIB::ieee8021PbServicePriorityRegenerationSVid,Integer32,not-accessible,,current,,S-VID for this regeneration table entry.
.1.3.111.2.802.1.1.5.1.4.1.2,IEEE8021-PB-MIB::ieee8021PbServicePriorityRegenerationReceivedPriority,Unsigned32,not-accessible,,current,,Received priority for this regeneration table entry.
.1.3.111.2.802.1.1.5.1.4.1.3,IEEE8021-PB-MIB::ieee8021PbServicePriorityRegenerationRegeneratedPriority,Unsigned32,read-write,,current,,The regenerated priority contained in this regeneration table entry.
.1.3.111.2.802.1.1.5.1.5,IEEE8021-PB-MIB::ieee8021PbCnpTable,,not-accessible,,current,,This table is used for dynamic creation and deletion of Customer Network Ports on S-VLAN components or I-components. Creation of an entry in this table will implicitly also create a corresponding entry in the ieee8021BridgeBasePortTable. Entries in this table must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.5.1.5.1,IEEE8021-PB-MIB::ieee8021PbCnpEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,Represents a dynamically created Customer Network Port.
.1.3.111.2.802.1.1.5.1.5.1.1,IEEE8021-PB-MIB::ieee8021PbCnpCComponentId,Unsigned32,read-create,,current,,The component ID of the C-Vlan component if this is an internal customer network port. The value must be 0 for an external customer network port. This value must be consistent with the value of the corresponding instance of ieee8021PbCnpSVid. Both must be non-zero, or both must be zero.
.1.3.111.2.802.1.1.5.1.5.1.2,IEEE8021-PB-MIB::ieee8021PbCnpSVid,Integer32,read-create,,current,,The S-VID for service for an internal customer network port. For an external port, this value must be 0. This value must be consistent with the value of the corresponding instance of ieee8021PbCnpCComponentId. Both must be non-zero, or both must be zero.
.1.3.111.2.802.1.1.5.1.5.1.3,IEEE8021-PB-MIB::ieee8021PbCnpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used for creation/deletion of entries in this table. All columns in this table must have valid values before this object can be set to active(1). While the value of this object is active(1), the values of other columns in the same entry may not be modified.
.1.3.111.2.802.1.1.5.1.6,IEEE8021-PB-MIB::ieee8021PbPnpTable,,not-accessible,,current,,This table is used for dynamic creation and deletion of Provider Network Ports on S-VLAN components or B-components. Creation of an entry in this table will implicitly also create a corresponding entry in the ieee8021BridgeBasePortTable. Entries in this table must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.5.1.6.1,IEEE8021-PB-MIB::ieee8021PbPnpEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,Represents a dynamically created Provider Network Port.
.1.3.111.2.802.1.1.5.1.6.1.1,IEEE8021-PB-MIB::ieee8021PbPnpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used for creation/deletion of entries in this table.
.1.3.111.2.802.1.1.5.1.7,IEEE8021-PB-MIB::ieee8021PbCepTable,,not-accessible,,current,,This table is used to create Customer Edge Ports, CEPs, on a provider edge Bridge. It is indexed by the ComponentId of the PEB's S-VLAN component and by the port number for the CEP. Note that the CEP's port number belongs to the set of port numbers associated with the PEB's S-VLAN component. Entries in this table must be persistent across reinitializations of the management system. However, note that some column values, as noted below, may change across system reinitializations.
.1.3.111.2.802.1.1.5.1.7.1,IEEE8021-PB-MIB::ieee8021PbCepEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,The entry of the ieee8021PbCepTable. Note that the component index must refer to the S-VLAN component of a PEB, and that the port number for the CEP is allocated from the port number space of that S-VLAN component.
.1.3.111.2.802.1.1.5.1.7.1.1,IEEE8021-PB-MIB::ieee8021PbCepCComponentId,Unsigned32,read-only,,current,,This column is an implementation specific column that may be used to map the C component associated with this CEP to other tables within the system, such as the Entity MIB. This column may not be created or modified by management station action. A value of 0 is always legal, and non-zero values will be interpreted in an implementation specific manner. The value of this column may or may not persist across system restarts.
.1.3.111.2.802.1.1.5.1.7.1.2,IEEE8021-PB-MIB::ieee8021PbCepCepPortNumber,Unsigned32,read-only,,current,,This column is an implementation specific column that may be used to map the CEP to other tables within the system, for example the Entity MIB. This column may not be created or modified by management station action. A value of 0 is always legal, and non-zero values will be interpreted in an implementation specific manner. The value of this column may or may not persist across system restarts.
.1.3.111.2.802.1.1.5.1.7.1.3,IEEE8021-PB-MIB::ieee8021PbCepRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of the entry, and is used to create and delete entries in this table.
.1.3.111.2.802.1.1.5.1.8,IEEE8021-PB-MIB::ieee8021PbRcapTable,,not-accessible,,current,,This table is used to create Remote Customer Access Ports, on a provider edge Bridge. It is indexed by the ComponentId of the PEB's S-VLAN component and by the port number for the RCAP. Note that the index port number belongs to the set of port numbers associated with the PEB's primary S-VLAN component. Entries in this table must be persistent across reinitializations of the management agent. However, note that some column values, as noted below, may change across system reinitializations.
.1.3.111.2.802.1.1.5.1.8.1,IEEE8021-PB-MIB::ieee8021PbRcapEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,The entry of the ieee8021PbRcapTable. Note that the component index must refer to the primary S-VLAN component of a PEB, and that the port number index for the RCAP is allocated from the port number space of that S-VLAN component.
.1.3.111.2.802.1.1.5.1.8.1.1,IEEE8021-PB-MIB::ieee8021PbRcapSComponentId,Unsigned32,read-only,,current,,This column is an implmentation specific column that may be used to map the Port-mapping S-VLAN component associated with this RCAP to other tables within the system, such as the Entity MIB. This column may not be created or modified by management station action. A value of 0 is always legal, and non-zero values will be interpreted in an implementation specific manner. The value of this column may or may not persist across system restarts.
.1.3.111.2.802.1.1.5.1.8.1.2,IEEE8021-PB-MIB::ieee8021PbRcapRcapPortNumber,Unsigned32,read-only,,current,,This column is an implementation specific column that may be used to map the RCAP to other tables within the system, for example the Entity MIB. This column may not be created or modified by management station action. A value of 0 is always legal, and non-zero values will be interpreted in an implementation specific manner. The value of this column may or may not persist across system restarts.
.1.3.111.2.802.1.1.5.1.8.1.3,IEEE8021-PB-MIB::ieee8021PbRcapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of the entry, and is used to create and delete entries in this table.
.1.3.111.2.802.1.1.5.1.9,IEEE8021-PB-MIB::ieee8021PbInternalInterfaceTable,,not-accessible,,current,,A table used in a Port-mapping S-VLAN component associated with a Remote Customer Access Port to manage the mapping between external S-VIDs and internal interfaces/S-VIDs. Note that the component ID of entries in this table must refer to the primary S-VLAN component of a Provider Edge Bridge and the Port Number must refer to the port number of a Remote Customer Access Port associated with that S-VLAN component. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.5.1.9.1,IEEE8021-PB-MIB::ieee8021PbIiEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021PbIiExternalSVid,current,,An element of the internal interface table accessed by PB S-VLAN component ID, Remnote Customer Access Port Bridge Port number, and external S-VID. Each element contains the mapping between an external S-VID and the internal port it selects and, except in the case of a C-tagged service interface the internal S-VID which carries the service .
.1.3.111.2.802.1.1.5.1.9.1.1,IEEE8021-PB-MIB::ieee8021PbIiExternalSVid,Integer32,not-accessible,,current,,External S-VID for this internal interface table entry.
.1.3.111.2.802.1.1.5.1.9.1.2,IEEE8021-PB-MIB::ieee8021PbIiInternalPortNumber,Unsigned32,read-only,,current,,The port number for the internal port on the primary S-VLAN component. This port number is used in FDB entries that reference an RCSI. The port number of the Remote Customer Access Port can be used to identify a PNP on the primary S-VLAN component connected to a PNP on the Port-mapping S-VLAN component.
.1.3.111.2.802.1.1.5.1.9.1.3,IEEE8021-PB-MIB::ieee8021PbIiInternalPortType,INTEGER,read-create,,current,none(1):customerVlanPort(2):providerNetworkPort(3):customerNetworkPort(4):customerEdgePort(5):customerBackbonePort(6):virtualInstancePort(7):dBridgePort(8):remoteCustomerAccessPort(9):stationFacingBridgePort(10):uplinkAccessPort(11):uplinkRelayPort(12),The port type of the internal port on the primary S-VLAN component. This indicates the type of RCSI as follows:  providerNetworkPort(3) - Indicates a PNP (not an RCSI) customerNetworkPort(4) - Indicates a Port-based RCSI customerEdgePort(5) - Indicates a C-tagged RCSI Other port type values are not valid for this field.
.1.3.111.2.802.1.1.5.1.9.1.4,IEEE8021-PB-MIB::ieee8021PbIiInternalSVid,Integer32,read-create,,current,,Internal S-VID for this external S-VID entry.
.1.3.111.2.802.1.1.5.1.9.1.5,IEEE8021-PB-MIB::ieee8021PbIiRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. The value of ieee8021PbIiExternalSVid must be set before an entry in this table can be made valid.deprecated It is an implementation specific decision as to whether any column in this table may be set while the corresponding instance of this object is valid(1).
.1.3.111.2.802.1.1.5.2,IEEE8021-PB-MIB::ieee8021PbConformance,,,,,,
.1.3.111.2.802.1.1.5.2.1,IEEE8021-PB-MIB::ieee8021PbGroups,,,,,,
.1.3.111.2.802.1.1.5.2.1.1,IEEE8021-PB-MIB::ieee8021PbVidTranslationGroup,,,,,,The collection of objects used to represent a PB C-VID/S-VID translation.
.1.3.111.2.802.1.1.5.2.1.2,IEEE8021-PB-MIB::ieee8021PbCVidRegistrationGroup,,,,,,The collection of objects used to represent a CEP translation.
.1.3.111.2.802.1.1.5.2.1.3,IEEE8021-PB-MIB::ieee8021PbEdgePortGroup,,,,,,The collection of objects user to represent a PEP.
.1.3.111.2.802.1.1.5.2.1.4,IEEE8021-PB-MIB::ieee8021PbServicePriorityRegenerationGroup,,,,,,A regenerated priority value for a PEP.
.1.3.111.2.802.1.1.5.2.1.5,IEEE8021-PB-MIB::ieee8021PbDynamicCnpGroup,,,,,,A set of objects used for dynamic creation and deletion of customer network ports.
.1.3.111.2.802.1.1.5.2.1.6,IEEE8021-PB-MIB::ieee8021PbDynamicPnpGroup,,,,,,A set of objects used for dynamic creation and deletion of provider network ports.
.1.3.111.2.802.1.1.5.2.1.7,IEEE8021-PB-MIB::ieee8021PbDynamicCepGroup,,,,,,A set of objects used for dynamic creation and deletion of customer edge ports.
.1.3.111.2.802.1.1.5.2.1.8,IEEE8021-PB-MIB::ieee8021PbDynamicRcapGroup,,,,,,A set of objects used for dynamic creation and deletion of remote customer access ports.
.1.3.111.2.802.1.1.5.2.1.9,IEEE8021-PB-MIB::ieee8021PbInternalInterfaceGroup,,,,,,A set of objects used for dynamic creation and deletion of internal interfaces on a Port-mapping S-VLAN component.
.1.3.111.2.802.1.1.5.2.1.10,IEEE8021-PB-MIB::ieee8021PbDynamicRcapV2Group,,,,,,A set of objects used for dynamic creation and deletion of remote customer access ports.
.1.3.111.2.802.1.1.5.2.2,IEEE8021-PB-MIB::ieee8021PbCompliances,,,,,,
.1.3.111.2.802.1.1.5.2.2.1,IEEE8021-PB-MIB::ieee8021PbCompliance,,,,,,The compliance statement for device support of Provider Bridge services.
.1.3.111.2.802.1.1.5.2.2.2,IEEE8021-PB-MIB::ieee8021PbComplianceV2,,,,,,The compliance statement for device support of Provider Bridge services.
.1.3.111.2.802.1.1.6,IEEE8021-MSTP-MIB::ieee8021MstpMib,,,,,,The Bridge MIB modules for managing devices that support IEEE Std 802.1Q multiple spanning tree groups. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.6.0,IEEE8021-MSTP-MIB::ieee8021MstpNotifications,,,,,,
.1.3.111.2.802.1.1.6.1,IEEE8021-MSTP-MIB::ieee8021MstpObjects,,,,,,
.1.3.111.2.802.1.1.6.1.1,IEEE8021-MSTP-MIB::ieee8021MstpCistTable,,not-accessible,,current,,The Common and Internal Spanning Tree (CIST) Table. Each row in the table represents information regarding a Bridge's Bridge Protocol Entity for the CIST. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3). This table contains objects corresponding to the following items from 12.8.1.1 and 12.8.1.3. Some of those items are provided  in the IEEE8021-SPANNING-TREE-MIB as noted below. From 12.8.1.1: Items a), c), o), p), and q) are defined in this table The remaining items are covered in the IEEE8021-SPANNING-TREE-MIB: b) ieee8021SpanningTreeTimeSinceTopologyChange c) ieee8021SpanningTreeTopChanges e) ieee8021SpanningTreeDesignatedRoot f) ieee8021SpanningTreeRootCost g) ieee8021SpanningTreeRootPort h) ieee8021SpanningTreeMaxAge i) ieee8021SpanningTreeForwardDelay j) ieee8021SpanningTreeBridgeMaxAge k) ieee8021SpanningTreeBridgeHelloTime l) ieee8021SpanningTreeBridgeForwardDelay m) ieee8021SpanningTreeHoldTime n) ieee8021SpanningTreeVersion From 12.8.1.3: Item g) is defined in this table The remaining items are covered in the IEEE8021-SPANNING-TREE-MIB: a) ieee8021SpanningTreeBridgeMaxAge b) ieee8021SpanningTreeBridgeHelloTime c) ieee8021SpanningTreeBridgeForwardDelay d) ieee8021SpanningTreePriority e) ieee8021SpanningTreeVersion f) ieee8021RstpStpExtTxHoldCount
.1.3.111.2.802.1.1.6.1.1.1,IEEE8021-MSTP-MIB::ieee8021MstpCistEntry,,not-accessible,ieee8021MstpCistComponentId,current,,A CIST Table entry.
.1.3.111.2.802.1.1.6.1.1.1.1,IEEE8021-MSTP-MIB::ieee8021MstpCistComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.1.1.2,IEEE8021-MSTP-MIB::ieee8021MstpCistBridgeIdentifier,OCTET,read-only,,current,,The Bridge Identifier for the CIST.
.1.3.111.2.802.1.1.6.1.1.1.3,IEEE8021-MSTP-MIB::ieee8021MstpCistTopologyChange,INTEGER,read-only,,current,true(1):false(2),In an STP Bridge, the value of the Topology Change parameter (14.8.1.1.3, item d of IEEE Std 802.1D, 2004 Edition), or in an RSTP or MSTP Bridge, asserted if the tcWhile timer for any Port for the CIST is non-zero.
.1.3.111.2.802.1.1.6.1.1.1.4,IEEE8021-MSTP-MIB::ieee8021MstpCistRegionalRootIdentifier,OCTET,read-only,,current,,In an MSTP Bridge, the CIST Regional Root Identifier parameter, i.e., the Bridge Identifier of the current CIST Regional Root.
.1.3.111.2.802.1.1.6.1.1.1.5,IEEE8021-MSTP-MIB::ieee8021MstpCistPathCost,Unsigned32,read-only,,current,,In an MSTP Bridge, the CIST Path Cost parameter, i.e., the CIST path cost from the transmitting Bridge to the CIST Regional Root. The sum (about 20 possible out of the given range) of multiple port path costs. Also, if the 'transmitting Bridge' is the 'CIST Regional Root', then this value could be zero.
.1.3.111.2.802.1.1.6.1.1.1.6,IEEE8021-MSTP-MIB::ieee8021MstpCistMaxHops,Integer32,read-write,,current,,In an MSTP Bridge, the MaxHops parameter. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.6.1.2,IEEE8021-MSTP-MIB::ieee8021MstpTable,,not-accessible,,current,,In an MSTP Bridge, the MSTP Table. Each row in the Table represents information regarding a Bridge's Bridge Protocol Entity for the specified Spanning Tree instance. Entries in this table MUST be retained across reinitializations of the management system. Note that entries can be created in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.2.1,IEEE8021-MSTP-MIB::ieee8021MstpEntry,,not-accessible,ieee8021MstpComponentId:ieee8021MstpId,current,,A MSTP Table entry.
.1.3.111.2.802.1.1.6.1.2.1.1,IEEE8021-MSTP-MIB::ieee8021MstpComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.2.1.2,IEEE8021-MSTP-MIB::ieee8021MstpId,Unsigned32,not-accessible,,current,,In an MSTP Bridge, this parameter is the MSTID, i.e., the identifier of a Spanning Tree (or MST) Instance.
.1.3.111.2.802.1.1.6.1.2.1.3,IEEE8021-MSTP-MIB::ieee8021MstpBridgeId,OCTET,read-only,,current,,In an MSTP Bridge, the Bridge Identifier for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.4,IEEE8021-MSTP-MIB::ieee8021MstpTimeSinceTopologyChange,TimeTicks,read-only,,current,,In an MSTP Bridge, count in seconds of the time elapsed since tcWhile was last non-zero for any Port for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.5,IEEE8021-MSTP-MIB::ieee8021MstpTopologyChanges,Counter64,read-only,,current,,In an MSTP Bridge, count of the times tcWhile has been non-zero for any Port for the MSTI since the Bridge was powered on or initialized.
.1.3.111.2.802.1.1.6.1.2.1.6,IEEE8021-MSTP-MIB::ieee8021MstpTopologyChange,INTEGER,read-only,,current,true(1):false(2),In an MSTP Bridge, the Topology Change parameter value: true(1) if tcWhile is non-zero for any Port for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.7,IEEE8021-MSTP-MIB::ieee8021MstpDesignatedRoot,OCTET,read-only,,current,,In an MSTP Bridge, the Designated Root parameter value, i.e., the Bridge Identifier of the Root Bridge for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.8,IEEE8021-MSTP-MIB::ieee8021MstpRootPathCost,Integer32,read-only,,current,,In an MSTP Bridge, the Root Path Cost parameter value, i.e., the path cost from the transmitting Bridge to the Root Bridge for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.9,IEEE8021-MSTP-MIB::ieee8021MstpRootPort,Unsigned32,read-only,,current,,In an MSTP Bridge, the Root Port parameter value, i.e., the Root Port for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.10,IEEE8021-MSTP-MIB::ieee8021MstpBridgePriority,Integer32,read-create,,current,,In an MSTP Bridge, the Bridge Priority parameter value for the MSTI, i.e., the most significant 4 bits of the Bridge Identifier for the MSTI.
.1.3.111.2.802.1.1.6.1.2.1.11,IEEE8021-MSTP-MIB::ieee8021MstpVids0,OCTET,read-only,,current,,This object contains the first 1024 bits of the 4096 bit vector indicating which VIDs are assigned to this MSTID. The high order bit of the first octet corresponds to the first bit of the vector, while the low order bit of the last octet corresponds to the last bit of this portion of the vector. A bit that is on (equal to 1) indicates that the corresponding VID is assigned to this MSTID.
.1.3.111.2.802.1.1.6.1.2.1.12,IEEE8021-MSTP-MIB::ieee8021MstpVids1,OCTET,read-only,,current,,This object contains the second 1024 bits of the 4096 bit vector indicating which VIDs are assigned to this MSTID. The high order bit of the first octet corresponds to the first bit of this portion of the vector, while the low order bit of the last octet corresponds to the last bit of this portion of the vector. A bit that is on (equal to 1) indicates that the corresponding VID is assigned to this MSTID.
.1.3.111.2.802.1.1.6.1.2.1.13,IEEE8021-MSTP-MIB::ieee8021MstpVids2,OCTET,read-only,,current,,This object contains the third 1024 bits of the 4096 bit vector indicating which VIDs are assigned to this MSTID. The high order bit of the first octet corresponds to the first bit of this portion of the vector, while the low order bit of the last octet corresponds to the last bit of this portion of the vector. A bit that is on (equal to 1) indicates that the corresponding VID is assigned to this MSTID.
.1.3.111.2.802.1.1.6.1.2.1.14,IEEE8021-MSTP-MIB::ieee8021MstpVids3,OCTET,read-only,,current,,This object contains the fourth 1024 bits of the 4096 bit vector indicating which VIDs are assigned to this MSTID. The high order bit of the first octet corresponds to the first bit of this portion of the vector, while the low order bit of the last octet corresponds to the last bit of this portion of the vector. A bit that is on (equal to 1) indicates that the corresponding VID is assigned to this MSTID.
.1.3.111.2.802.1.1.6.1.2.1.15,IEEE8021-MSTP-MIB::ieee8021MstpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. Read SNMPv2-TC (RFC2579) for an explanation of the possible values this object can take. The writable columns in a row cannot be changed if the row is active. All columns must have a valid value before a row can be activated.
.1.3.111.2.802.1.1.6.1.3,IEEE8021-MSTP-MIB::ieee8021MstpCistPortTable,,not-accessible,,current,,The CIST Port Table. Each row in the Table represents information regarding a specific Port within the Bridge's Bridge Protocol Entity, for the CIST. The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3). This table contains objects corresponding to the following items from 12.8.2.1, 12.8.2.3, and 12.8.2.5. Some of those items are  provided in the IEEE8021-SPANNING-TREE-MIB as noted below. From 12.8.2.1: Items a), d), e), and i) through w) are defined in this table The remaining items are covered in the IEEE8021-SPANNING-TREE-MIB: b) ieee8021SpanningTreePortState c) ieee8021SpanningTreePortPriority d) ieee8021SpanningTreePortPathCost f) ieee8021SpanningTreePortDesignatedCost g) ieee8021SpanningTreePortDesignatedBridge h) ieee8021SpanningTreePortDesignatedPort From 12.8.2.3: Items a), b), and d) through h) are defined in this table (item a is the index) The remaining items are covered in the IEEE8021-SPANNING-TREE-MIB: b) ieee8021SpanningTreePortPathCost, c) ieee8021SpanningTreePortPriority From 12.8.2.5: All items are defined in this table Also from 12.8.2.1: Items u), v), w), and x) are defined in this table Also from 12.8.2.3: Items i), j), k), and l) are defined in this table
.1.3.111.2.802.1.1.6.1.3.1,IEEE8021-MSTP-MIB::ieee8021MstpCistPortEntry,,not-accessible,ieee8021MstpCistPortComponentId:ieee8021MstpCistPortNum,current,,A CIST Port Table entry.
.1.3.111.2.802.1.1.6.1.3.1.1,IEEE8021-MSTP-MIB::ieee8021MstpCistPortComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.3.1.2,IEEE8021-MSTP-MIB::ieee8021MstpCistPortNum,Unsigned32,not-accessible,,current,,The Port's Port Number parameter value for the CIST, i.e., the number of the Bridge Port for the CIST.
.1.3.111.2.802.1.1.6.1.3.1.3,IEEE8021-MSTP-MIB::ieee8021MstpCistPortUptime,TimeTicks,read-only,,current,,The Port's Uptime parameter value for the CIST, i.e., the count in seconds of the time elapsed since the Port was last reset or initialized (BEGIN, Annex E).
.1.3.111.2.802.1.1.6.1.3.1.4,IEEE8021-MSTP-MIB::ieee8021MstpCistPortAdminPathCost,Integer32,read-write,,current,,The administratively assigned value for the contribution of this port to the path cost of paths toward the spanning tree root. Writing a value of '0' assigns the automatically calculated default Path Cost value to the port. If the default Path Cost is being used, this object returns '0' when read. This complements the object ieee8021MstpCistPortCistPathCost, which returns the operational value of the port path cost. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.6.1.3.1.5,IEEE8021-MSTP-MIB::ieee8021MstpCistPortDesignatedRoot,OCTET,read-only,,current,,The CIST Regional Root Identifier component of the Port's port priority vector, as defined in 13.10, for the CIST.
.1.3.111.2.802.1.1.6.1.3.1.6,IEEE8021-MSTP-MIB::ieee8021MstpCistPortTopologyChangeAck,INTEGER,read-only,,current,true(1):false(2),The Port's Topology Change Acknowledge parameter value. True(1) if a Configuration Message with a topology change acknowledge flag set is to be transmitted. 
.1.3.111.2.802.1.1.6.1.3.1.7,IEEE8021-MSTP-MIB::ieee8021MstpCistPortHelloTime,Integer32,read-only,,current,,The Port's Hello Time timer parameter value, for the CIST. In centi-seconds
.1.3.111.2.802.1.1.6.1.3.1.8,IEEE8021-MSTP-MIB::ieee8021MstpCistPortAdminEdgePort,INTEGER,read-write,,current,true(1):false(2),In a Bridge that supports the identification of edge ports, the Port's Admin Edge Port parameter value, for the CIST.
.1.3.111.2.802.1.1.6.1.3.1.9,IEEE8021-MSTP-MIB::ieee8021MstpCistPortOperEdgePort,INTEGER,read-only,,current,true(1):false(2),In a Bridge that supports the identification of edge ports, the Port's operational Edge Port parameter value, for the CIST. True(1) if it is an Oper Edge Port.
.1.3.111.2.802.1.1.6.1.3.1.10,IEEE8021-MSTP-MIB::ieee8021MstpCistPortMacEnabled,INTEGER,read-write,,current,true(1):false(2),In a Bridge that supports the MAC Enabled parameter, the current state of the MAC Enabled parameter. True(1) indicates that adminstratively the MAC is set as if it  was connected to a point-to-point LAN.
.1.3.111.2.802.1.1.6.1.3.1.11,IEEE8021-MSTP-MIB::ieee8021MstpCistPortMacOperational,INTEGER,read-only,,current,true(1):false(2),In a Bridge that supports the MAC Operational parameter, the current state of the MAC Operational parameter. True(1) indicates the MAC is operational.
.1.3.111.2.802.1.1.6.1.3.1.12,IEEE8021-MSTP-MIB::ieee8021MstpCistPortRestrictedRole,INTEGER,read-write,,current,true(1):false(2),The current state of the restrictedRole parameter for the Port. True(1) causes the Port not to be selected as Root Port for the  CIST or any MSTI. 
.1.3.111.2.802.1.1.6.1.3.1.13,IEEE8021-MSTP-MIB::ieee8021MstpCistPortRestrictedTcn,INTEGER,read-write,,current,true(1):false(2),The current state of the restrictedTcn parameter for the Port. True(1) causes the Port not to propagate topology changes to  other Ports.
.1.3.111.2.802.1.1.6.1.3.1.14,IEEE8021-MSTP-MIB::ieee8021MstpCistPortRole,INTEGER,read-only,,current,root(1):alternate(2):designated(3):backup(4),The current Port Role for the Port (i.e., Root, Alternate, Designated, or Backup), for the CIST.
.1.3.111.2.802.1.1.6.1.3.1.15,IEEE8021-MSTP-MIB::ieee8021MstpCistPortDisputed,INTEGER,read-only,,current,true(1):false(2),The current value of the disputed variable for the CIST for the Port. A value of true(1) indicates that the disputed variable is set. A value of false(2) indicates that the agreed variable is cleared.
.1.3.111.2.802.1.1.6.1.3.1.16,IEEE8021-MSTP-MIB::ieee8021MstpCistPortCistRegionalRootId,OCTET,read-only,,current,,In an MSTP Bridge, the CIST Regional Root Identifier, i.e., the Bridge Identifier of the current CIST Regional Root, for the CIST.
.1.3.111.2.802.1.1.6.1.3.1.17,IEEE8021-MSTP-MIB::ieee8021MstpCistPortCistPathCost,Unsigned32,read-only,,current,,In an MSTP Bridge, the Port's Port Path Cost parameter value for the CIST.
.1.3.111.2.802.1.1.6.1.3.1.18,IEEE8021-MSTP-MIB::ieee8021MstpCistPortProtocolMigration,INTEGER,read-write,,current,true(1):false(2),In an MSTP Bridge, the current value of the mcheck variable for the Port. A value of true(1) forces the state machine to perform functions as per 13.27.38.
.1.3.111.2.802.1.1.6.1.3.1.19,IEEE8021-MSTP-MIB::ieee8021MstpCistPortEnableBPDURx,INTEGER,read-write,,current,true(1):false(2),In an MSTP Bridge, the enableBPDUrx parameter value. A value of false(2) indicates that BPDUs are ignored.
.1.3.111.2.802.1.1.6.1.3.1.20,IEEE8021-MSTP-MIB::ieee8021MstpCistPortEnableBPDUTx,INTEGER,read-write,,current,true(1):false(2),In an MSTP Bridge, the enableBPDUtx parameter value. A value of false(2) indicates that BPDUs are not transmitted.
.1.3.111.2.802.1.1.6.1.3.1.21,IEEE8021-MSTP-MIB::ieee8021MstpCistPortPseudoRootId,OCTET,read-write,,current,,In an MSTP Bridge, the pseudoRootId parameter value.
.1.3.111.2.802.1.1.6.1.3.1.22,IEEE8021-MSTP-MIB::ieee8021MstpCistPortIsL2Gp,INTEGER,read-write,,current,true(1):false(2),In an MSTP Bridge, the isL2gp parameter value. A value of true(1) indicates this is an L2GP port.
.1.3.111.2.802.1.1.6.1.4,IEEE8021-MSTP-MIB::ieee8021MstpPortTable,,not-accessible,,current,,The MSTP Port Table. Each row in the Table represents information regarding a specific Port within the Bridge's Bridge Protocol Entity, for a given MSTI. The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.4.1,IEEE8021-MSTP-MIB::ieee8021MstpPortEntry,,not-accessible,ieee8021MstpPortComponentId:ieee8021MstpPortMstId:ieee8021MstpPortNum,current,,A MSTP Port Table entry.
.1.3.111.2.802.1.1.6.1.4.1.1,IEEE8021-MSTP-MIB::ieee8021MstpPortComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.4.1.2,IEEE8021-MSTP-MIB::ieee8021MstpPortMstId,Unsigned32,not-accessible,,current,,In an MSTP Bridge, this parameter is the MSTID, i.e., the identifier of a Spanning Tree (or MST) Instance.
.1.3.111.2.802.1.1.6.1.4.1.3,IEEE8021-MSTP-MIB::ieee8021MstpPortNum,Unsigned32,not-accessible,,current,,In an MSTP Bridge, the Port's Port Number parameter value for the MSTI, i.e., the number of the Bridge Port for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.4,IEEE8021-MSTP-MIB::ieee8021MstpPortUptime,TimeTicks,read-only,,current,,In an MSTP Bridge, the Port's Uptime parameter value for the MSTI, i.e., the count in seconds of the time elapsed since the Port was last reset or initialized (BEGIN, Annex E).
.1.3.111.2.802.1.1.6.1.4.1.5,IEEE8021-MSTP-MIB::ieee8021MstpPortState,INTEGER,read-only,,current,disabled(1):listening(2):learning(3):forwarding(4):blocking(5),In an MSTP Bridge, the current state of the Port (i.e., Disabled, Listening, Learning, Forwarding, or Blocking), for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.6,IEEE8021-MSTP-MIB::ieee8021MstpPortPriority,Integer32,read-write,,current,,In an MSTP Bridge, the Port's Port Priority parameter value for the MSTI, i.e., the priority field for the Port Identifier for the Port for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.7,IEEE8021-MSTP-MIB::ieee8021MstpPortPathCost,Integer32,read-write,,current,,In an MSTP Bridge, the Port's Port Path Cost parameter value for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.8,IEEE8021-MSTP-MIB::ieee8021MstpPortDesignatedRoot,OCTET,read-only,,current,,In an MSTP Bridge, the Regional Root Identifier component of the Port's MSTI port priority vector, as defined in 13.11, for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.9,IEEE8021-MSTP-MIB::ieee8021MstpPortDesignatedCost,Integer32,read-only,,current,,In an MSTP Bridge, the Internal Root Path Cost component of the Port's MSTI port priority vector, as defined in 13.11, for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.10,IEEE8021-MSTP-MIB::ieee8021MstpPortDesignatedBridge,OCTET,read-only,,current,,In an MSTP Bridge, the Designated Bridge Identifier component of the Port's MSTI port priority vector, as defined in 13.11, for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.11,IEEE8021-MSTP-MIB::ieee8021MstpPortDesignatedPort,Unsigned32,read-only,,current,,In an MSTP Bridge, the Designated Port Identifier component of the Port's MSTI port priority vector, as defined in 13.11, for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.12,IEEE8021-MSTP-MIB::ieee8021MstpPortRole,INTEGER,read-only,,current,root(1):alternate(2):designated(3):backup(4),In an MSTP Bridge, the current Port Role for the Port (i.e., Root, Alternate, Designated, or Backup), for the MSTI.
.1.3.111.2.802.1.1.6.1.4.1.13,IEEE8021-MSTP-MIB::ieee8021MstpPortDisputed,INTEGER,read-only,,current,true(1):false(2),In an MSTP Bridge, the current value of the disputed variable for the MSTI for the Port.
.1.3.111.2.802.1.1.6.1.4.1.14,IEEE8021-MSTP-MIB::ieee8021MstpPortAdminPathCost,Integer32,read-write,,current,,In an MSTP Bridge, the administrative value of the Port's Port Path Cost parameter value for the MSTI. Writing a value of '0' assigns the automatically calculated default Path Cost value to the Port. If the default Path Cost is being used, this object returns '0' when read. This complements the object ieee8021MstpPortPathCost, which returns the operational value of the path cost. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.6.1.5,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiTable,,not-accessible,,deprecated,,In an MSTP Bridge, the fixed-length FID to MSTID Allocation Table entry. Each entry in the Table corresponds to a FID, and the value of the entry specifies the MSTID of the spanning tree to which the set of VLANs supported by that FID are assigned. A value of zero in an entry specifies that the set of VLANs supported by that FID are assigned to the CST. The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.5.1,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiEntry,,not-accessible,ieee8021MstpFidToMstiComponentId:ieee8021MstpFidToMstiFid,deprecated,,In an MSTP Bridge, a FID to MSTID Allocation Table entry.
.1.3.111.2.802.1.1.6.1.5.1.1,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiComponentId,Unsigned32,not-accessible,,deprecated,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.5.1.2,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiFid,Unsigned32,not-accessible,,deprecated,,In an MSTP Bridge, the FID of the entry in the FID to MSTID Allocation Table.
.1.3.111.2.802.1.1.6.1.5.1.3,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiMstId,Unsigned32,read-write,,deprecated,,In an MSTP Bridge, the MSTID to which the FID (of the entry in the FID to MSTID Allocation Table) is to be allocated.
.1.3.111.2.802.1.1.6.1.6,IEEE8021-MSTP-MIB::ieee8021MstpVlanTable,,not-accessible,,deprecated,,In an MSTP Bridge, the fixed-length (4094 elements), read-only, MST Configuration Table. Its elements are derived from other configuration information held by the Bridge; specifically, the current state of the VID to FID Allocation Table (8.8.8, 12.10.1),and the FID to MSTID Allocation Table (8.9.3, 12.12.2). Hence, changes made to either of these Tables can in turn affect the contents of the MST Configuration Table, and also affect the value of the digest element of the MST Configuration Identifier. The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.6.1,IEEE8021-MSTP-MIB::ieee8021MstpVlanEntry,,not-accessible,ieee8021MstpVlanComponentId:ieee8021MstpVlanId,deprecated,,In an MSTP Bridge, a MST Configuration Table entry.
.1.3.111.2.802.1.1.6.1.6.1.1,IEEE8021-MSTP-MIB::ieee8021MstpVlanComponentId,Unsigned32,not-accessible,,deprecated,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.6.1.2,IEEE8021-MSTP-MIB::ieee8021MstpVlanId,Unsigned32,not-accessible,,deprecated,,In an MSTP Bridge, the VID of the entry in the MST Configuration Table.
.1.3.111.2.802.1.1.6.1.6.1.3,IEEE8021-MSTP-MIB::ieee8021MstpVlanMstId,Unsigned32,read-only,,deprecated,,In an MSTP Bridge, the MSTID value corresponding to the VID of the entry in the MST Configuration Table.
.1.3.111.2.802.1.1.6.1.7,IEEE8021-MSTP-MIB::ieee8021MstpConfigIdTable,,not-accessible,,current,,A table containing the MST Configuration Identifier for each virtual Bridge. In simple situations where there is only a single component, there will only be a single entry in this table (i.e., only a single MST Configuration Identifier). The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.7.1,IEEE8021-MSTP-MIB::ieee8021MstpConfigIdEntry,,not-accessible,ieee8021MstpConfigIdComponentId,current,,An entry contining the MST Configuration Identifier of a Bridge.
.1.3.111.2.802.1.1.6.1.7.1.1,IEEE8021-MSTP-MIB::ieee8021MstpConfigIdComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.7.1.2,IEEE8021-MSTP-MIB::ieee8021MstpConfigIdFormatSelector,Integer32,read-write,,current,,In an MSTP Bridge, the Configuration Identifier Format Selector in use by the Bridge, in the MST Configuration Identifier. This has a value of 0 to indicate the format specified in IEEE Std 802.1Q.
.1.3.111.2.802.1.1.6.1.7.1.3,IEEE8021-MSTP-MIB::ieee8021MstpConfigurationName,OCTET,read-write,,current,,In an MSTP Bridge, the Configuration Name in the MST Configuration Identifier.
.1.3.111.2.802.1.1.6.1.7.1.4,IEEE8021-MSTP-MIB::ieee8021MstpRevisionLevel,Unsigned32,read-write,,current,,In an MSTP Bridge, the Revision Level in the MST Configuration Identifier.
.1.3.111.2.802.1.1.6.1.7.1.5,IEEE8021-MSTP-MIB::ieee8021MstpConfigurationDigest,OCTET,read-only,,current,,In an MSTP Bridge, the Configuration Digest in the MST Configuration Identifier.
.1.3.111.2.802.1.1.6.1.8,IEEE8021-MSTP-MIB::ieee8021MstpCistPortExtensionTable,,not-accessible,,current,,The CIST Port Extensions Table. Each row in the Table represents information regarding a specific Port within the Bridge's Bridge Protocol Entity, for the CIST.
.1.3.111.2.802.1.1.6.1.8.1,IEEE8021-MSTP-MIB::ieee8021MstpCistPortExtensionEntry,,not-accessible,,current,,A list of additional objects containing information  maintained by every port about the CIST  state for that port.
.1.3.111.2.802.1.1.6.1.8.1.1,IEEE8021-MSTP-MIB::ieee8021MstpCistPortAutoEdgePort,INTEGER,read-write,,current,true(1):false(2),The administrative value of the Auto Edge Port parameter. A value of true(1) indicates if the Bridge detection state  machine (BDM, 13.31) is to detect other Bridges attached to the LAN, and set  ieee8021SpanningTreeRstpPortOperEdgePort automatically. The default value is true(1) This is optional and provided only by implementations  that support the automatic identification of edge ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.6.1.8.1.2,IEEE8021-MSTP-MIB::ieee8021MstpCistPortAutoIsolatePort,INTEGER,read-only,,current,true(1):false(2),The operational value of the Isolate Port parameter.  A value of true(1) indicates a Designated Port will  transition to discarding if both  ieee8021SpanningTreeRstpPortAdminEdgePort and  ieee8021SpanningTreeRstpPortAutoEdgePort are FALSE and  the other Bridge presumed to be attached to the same  point-to-point LAN does not transmit periodic BPDUs. This is optional and provided only by implementations  that support the automatic identification of fragile Bridges.
.1.3.111.2.802.1.1.6.1.9,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiV2Table,,not-accessible,,current,,In an MSTP Bridge, the fixed-length FID to MSTID Allocation Table entry. Each entry in the Table corresponds to a FID, and the value of the entry specifies the MSTID of the spanning tree to which the set of VLANs supported by that FID are assigned. A value of zero in an entry specifies that the set of VLANs supported by that FID are assigned to the CST. The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.9.1,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiV2Entry,,not-accessible,ieee8021MstpFidToMstiV2ComponentId:ieee8021MstpFidToMstiV2Fid,current,,In an MSTP Bridge, a FID to MSTID Allocation Table entry.
.1.3.111.2.802.1.1.6.1.9.1.1,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiV2ComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.9.1.2,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiV2Fid,Unsigned32,not-accessible,,current,,In an MSTP Bridge, the FID of the entry in the FID to MSTID Allocation Table.
.1.3.111.2.802.1.1.6.1.9.1.3,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiV2MstId,Unsigned32,read-write,,current,,In an MSTP Bridge, the MSTID to which the FID (of the entry in the FID to MSTID Allocation Table) is to be allocated. In an SPT Bridge, the value 4095 is used to indicate unused (non-filtering) FIDs.
.1.3.111.2.802.1.1.6.1.10,IEEE8021-MSTP-MIB::ieee8021MstpVlanV2Table,,not-accessible,,current,,In an MSTP Bridge, the fixed-length (4094 elements), read-only, MST Configuration Table. Its elements are derived from other configuration information held by the Bridge; specifically, the current state of the VID to FID Allocation Table (8.8.8, 12.10.1),and the FID to MSTID Allocation Table (8.9.3, 12.12.2). Hence, changes made to either of these Tables can in turn affect the contents of the MST Configuration Table, and also affect the value of the digest element of the MST Configuration Identifier. The values of all writable objects in this table MUST be retained across reinitializations of the management system. Note that entries will exist in this table only for Bridge components for which the corresponding instance of ieee8021SpanningTreeVersion (from the IEEE8021-SPANNING-TREE-MIB) has a value of mstp(3).
.1.3.111.2.802.1.1.6.1.10.1,IEEE8021-MSTP-MIB::ieee8021MstpVlanV2Entry,,not-accessible,ieee8021MstpVlanV2ComponentId:ieee8021MstpVlanV2Id,current,,In an MSTP Bridge, a MST Configuration Table entry.
.1.3.111.2.802.1.1.6.1.10.1.1,IEEE8021-MSTP-MIB::ieee8021MstpVlanV2ComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual Bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.6.1.10.1.2,IEEE8021-MSTP-MIB::ieee8021MstpVlanV2Id,Unsigned32,not-accessible,,current,,In an MSTP Bridge, the VID of the entry in the MST Configuration Table.
.1.3.111.2.802.1.1.6.1.10.1.3,IEEE8021-MSTP-MIB::ieee8021MstpVlanV2MstId,Unsigned32,read-only,,current,,In an MSTP Bridge, the MSTID value corresponding to the VID of the entry in the MST Configuration Table.  In an SPT Bridge, a value of 4095 is used to indicate  SPVIDs.
.1.3.111.2.802.1.1.6.2,IEEE8021-MSTP-MIB::ieee8021MstpConformance,,,,,,
.1.3.111.2.802.1.1.6.2.1,IEEE8021-MSTP-MIB::ieee8021MstpGroups,,,,,,
.1.3.111.2.802.1.1.6.2.1.1,IEEE8021-MSTP-MIB::ieee8021MstpCistGroup,,,,,,Objects for the CIST group
.1.3.111.2.802.1.1.6.2.1.2,IEEE8021-MSTP-MIB::ieee8021MstpGroup,,,,,,Objects for the MST group
.1.3.111.2.802.1.1.6.2.1.3,IEEE8021-MSTP-MIB::ieee8021MstpCistPortGroup,,,,,,Objects for the CIST Port group
.1.3.111.2.802.1.1.6.2.1.4,IEEE8021-MSTP-MIB::ieee8021MstpPortGroup,,,,,,Objects for the MST Port group
.1.3.111.2.802.1.1.6.2.1.5,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiGroup,,,,,,Objects for the MST FID to MSTID Allocation Table group
.1.3.111.2.802.1.1.6.2.1.6,IEEE8021-MSTP-MIB::ieee8021MstpVlanGroup,,,,,,Objects for the MST Configuration Table group
.1.3.111.2.802.1.1.6.2.1.7,IEEE8021-MSTP-MIB::ieee8021MstpConfigIdGroup,,,,,,Objects for the MST Configuration Identifier group
.1.3.111.2.802.1.1.6.2.1.8,IEEE8021-MSTP-MIB::ieee8021MstpCistPortExtensionGroup,,,,,,Objects for the CIST Port Extension group  for fragile Bridges
.1.3.111.2.802.1.1.6.2.1.9,IEEE8021-MSTP-MIB::ieee8021MstpFidToMstiV2Group,,,,,,Objects for the MST FID to MSTID Allocation Table group  for SPB
.1.3.111.2.802.1.1.6.2.1.10,IEEE8021-MSTP-MIB::ieee8021MstpVlanV2Group,,,,,,Objects for the MST Configuration Table group for SPB
.1.3.111.2.802.1.1.6.2.2,IEEE8021-MSTP-MIB::ieee8021MstpCompliances,,,,,,
.1.3.111.2.802.1.1.6.2.2.1,IEEE8021-MSTP-MIB::ieee8021MstpCompliance,,,,,,The compliance statement for devices supporting Multiple Spanning Tree as defined in 13 of IEEE Std 802.1Q.
.1.3.111.2.802.1.1.6.2.2.2,IEEE8021-MSTP-MIB::ieee8021MstpComplianceV2,,,,,,The compliance statement for devices supporting Multiple Spanning Tree as defined in 13 of IEEE Std 802.1Q.
.1.3.111.2.802.1.1.7,IEEE8021-CFM-V2-MIB::ieee8021CfmV2Mib,,,,,,Connectivity Fault Management V2 module. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.8,IEEE8021-CFM-MIB::ieee8021CfmMib,,,,,,Connectivity Fault Management module. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Syd 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.8.0,IEEE8021-CFM-MIB::dot1agNotifications,,,,,,
.1.3.111.2.802.1.1.8.0.1,IEEE8021-CFM-MIB::dot1agCfmFaultAlarm,,,,,,A MEP has a persistent defect condition. A notification (fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP has a persistent defect, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm. If a defect with a higher priority is raised after a Fault Alarm has been issued, another Fault Alarm is issued. The management entity receiving the notification can identify the system from the network source address of the notification, and can identify the MEP reporting the defect by the indices in the OID of the dot1agCfmMepHighestPrDefect variable in the notification: dot1agCfmMdIndex - Also the index of the MEP's Maintenance Domain table entry (dot1agCfmMdTable). dot1agCfmMaIndex - Also an index (with the MD table index) of the MEP's Maintenance Association network table entry (dot1agCfmMaNetTable), and (with the MD table index and component ID) of the MEP's MA component table entry (dot1agCfmMaCompTable). dot1agCfmMepIdentifier - MEP Identifier and final index into the MEP table (dot1agCfmMepTable). 
.1.3.111.2.802.1.1.8.1,IEEE8021-CFM-MIB::dot1agMIBObjects,,,,,,
.1.3.111.2.802.1.1.8.1.1,IEEE8021-CFM-MIB::dot1agCfmStack,,,,,,
.1.3.111.2.802.1.1.8.1.1.1,IEEE8021-CFM-MIB::dot1agCfmStackTable,,not-accessible,,deprecated,,There is one CFM Stack table per Bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.1.1,IEEE8021-CFM-MIB::dot1agCfmStackEntry,,not-accessible,dot1agCfmStackifIndex:dot1agCfmStackVlanIdOrNone:dot1agCfmStackMdLevel:dot1agCfmStackDirection,deprecated,,The Stack table entry **NOTE: this object is deprecated due to re-indexing of the  table.
.1.3.111.2.802.1.1.8.1.1.1.1.1,IEEE8021-CFM-MIB::dot1agCfmStackifIndex,Integer32,not-accessible,,deprecated,,This object represents the Bridge Port or aggregated port on which MEPs or MHFs might be configured. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable, and rearrange the dot1agCfmStackTable, so that it indexes the entry in the interface table with the same value of ifAlias that it indexed before the system restart. If no such entry exists, then the system SHALL delete all entries in the dot1agCfmStackTable with the interface index. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.1.1.2,IEEE8021-CFM-MIB::dot1agCfmStackVlanIdOrNone,Integer32,not-accessible,,deprecated,,VLAN ID to which the MP is attached, or 0, if none. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.1.1.3,IEEE8021-CFM-MIB::dot1agCfmStackMdLevel,Integer32,not-accessible,,deprecated,,MD Level of the Maintenance Point. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.1.1.4,IEEE8021-CFM-MIB::dot1agCfmStackDirection,INTEGER,not-accessible,,deprecated,down(1):up(2),Direction in which the MP faces on the Bridge Port **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.1.1.5,IEEE8021-CFM-MIB::dot1agCfmStackMdIndex,Unsigned32,read-only,,deprecated,,The index of the Maintenance Domain in the dot1agCfmMdTable to which the MP is associated, or 0, if none. 
.1.3.111.2.802.1.1.8.1.1.1.1.6,IEEE8021-CFM-MIB::dot1agCfmStackMaIndex,Unsigned32,read-only,,deprecated,,The index of the MA in the dot1agCfmMaNetTable and dot1agCfmMaCompTable to which the MP is associated, or 0, if none. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.1.1.7,IEEE8021-CFM-MIB::dot1agCfmStackMepId,Unsigned32,read-only,,deprecated,,If an MEP is configured, the MEPID, else 0
.1.3.111.2.802.1.1.8.1.1.1.1.8,IEEE8021-CFM-MIB::dot1agCfmStackMacAddress,OCTET,read-only,,deprecated,,MAC address of the MP. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.1.2,IEEE8021-CFM-V2-MIB::ieee8021CfmStackTable,,not-accessible,,current,,There is one CFM Stack table per Bridge. It permits the retrieval of information about the Maintenance Points configured on any given interface. 
.1.3.111.2.802.1.1.8.1.1.2.1,IEEE8021-CFM-V2-MIB::ieee8021CfmStackEntry,,not-accessible,ieee8021CfmStackifIndex:ieee8021CfmStackServiceSelectorType:ieee8021CfmStackServiceSelectorOrNone:ieee8021CfmStackMdLevel:ieee8021CfmStackDirection,current,,The Stack table entry
.1.3.111.2.802.1.1.8.1.1.2.1.1,IEEE8021-CFM-V2-MIB::ieee8021CfmStackifIndex,Integer32,not-accessible,,current,,This object represents the Bridge Port or aggregated port on which MEPs or MHFs might be configured. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable, and rearrange the ieee8021CfmStackTable, so that it indexes the entry in the interface table with the same value of ifAlias that it indexed before the system restart. If no such entry exists, then the system SHALL delete all entries in the ieee8021CfmStackTable with the interface index. 
.1.3.111.2.802.1.1.8.1.1.2.1.2,IEEE8021-CFM-V2-MIB::ieee8021CfmStackServiceSelectorType,INTEGER,not-accessible,,current,vlanId(1):isid(2):tesid(3):segid(4):path-tesid(5):group-isid(6):ieeeReserved(7),Type of the Service Selector identifier indicated by ieee8021CfmStackServiceSelectorOrNone. See textual convention IEEE8021ServiceSelectorType for details. 
.1.3.111.2.802.1.1.8.1.1.2.1.3,IEEE8021-CFM-V2-MIB::ieee8021CfmStackServiceSelectorOrNone,Unsigned32,not-accessible,,current,,Service Selector identifier to which the MP is attached, or 0, if none. See textual convention IEEE8021ServiceSelectorValue for details. 
.1.3.111.2.802.1.1.8.1.1.2.1.4,IEEE8021-CFM-V2-MIB::ieee8021CfmStackMdLevel,Integer32,not-accessible,,current,,MD Level of the Maintenance Point.
.1.3.111.2.802.1.1.8.1.1.2.1.5,IEEE8021-CFM-V2-MIB::ieee8021CfmStackDirection,INTEGER,not-accessible,,current,down(1):up(2),Direction in which the MP faces on the Bridge Port
.1.3.111.2.802.1.1.8.1.1.2.1.6,IEEE8021-CFM-V2-MIB::ieee8021CfmStackMdIndex,Unsigned32,read-only,,current,,The index of the Maintenance Domain in the ieee8021CfmMdTable to which the MP is associated, or 0, if none.
.1.3.111.2.802.1.1.8.1.1.2.1.7,IEEE8021-CFM-V2-MIB::ieee8021CfmStackMaIndex,Unsigned32,read-only,,current,,The index of the MA in the dot1agCfmMaNetTable and ieee8021CfmMaCompTable to which the MP is associated, or 0, if none.
.1.3.111.2.802.1.1.8.1.1.2.1.8,IEEE8021-CFM-V2-MIB::ieee8021CfmStackMepId,Unsigned32,read-only,,current,,If an MEP is configured, the MEPID, else 0
.1.3.111.2.802.1.1.8.1.1.2.1.9,IEEE8021-CFM-V2-MIB::ieee8021CfmStackMacAddress,OCTET,read-only,,current,,MAC address of the MP.
.1.3.111.2.802.1.1.8.1.2,IEEE8021-CFM-MIB::dot1agCfmDefaultMd,,,,,,
.1.3.111.2.802.1.1.8.1.2.1,IEEE8021-CFM-MIB::dot1agCfmDefaultMdDefLevel,Integer32,read-write,,current,,A value indicating the MD Level at which MHFs are to be created, and Sender ID TLV transmission by those MHFs is to be controlled, for each dot1agCfmDefaultMdEntry whose dot1agCfmDefaultMdLevel object contains the value -1. After this initialization, this object needs to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.2.2,IEEE8021-CFM-MIB::dot1agCfmDefaultMdDefMhfCreation,INTEGER,read-write,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3),A value indicating if the Management entity can create MHFs (MIP Half Function) for the VID, for each dot1agCfmDefaultMdEntry whose dot1agCfmDefaultMdMhfCreation object contains the value defMHFdefer. Since, in this variable, there is no encompassing Maintenance Domain, the value defMHFdefer is not allowed. After this initialization, this object needs to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.2.3,IEEE8021-CFM-MIB::dot1agCfmDefaultMdDefIdPermission,INTEGER,read-write,,current,sendIdNone(1):sendIdChassis(2):sendIdManage(3):sendIdChassisManage(4),Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MHFs created by the Default Maintenance Domain, for each dot1agCfmDefaultMdEntry whose dot1agCfmDefaultMdIdPermission object contains the value sendIdDefer. Since, in this variable, there is no encompassing Maintenance Domain, the value sendIdDefer is not allowed. After this initialization, this object needs to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.2.4,IEEE8021-CFM-MIB::dot1agCfmDefaultMdTable,,not-accessible,,deprecated,,For each Bridge component, the Default MD Level Managed Object controls MHF creation for VIDs that are not attached to a specific Maintenance Association Managed Object, and Sender ID TLV transmission by those MHFs. For each Bridge Port, and for each VLAN ID whose data can pass through that Bridge Port, an entry in this table is used by the algorithm in 22.2.3 only if there is no entry in the Maintenance Association table defining an MA for the same VLAN ID and MD Level as this table's entry, and on which MA an Up MEP is defined. If there exists such an MA, that MA's objects are used by the algorithm in 22.2.3 in place of this table entry's objects. The agent maintains the value of dot1agCfmDefaultMdStatus to indicate whether this entry is overridden by an MA. When first initialized, the agent creates this table automatically with entries for all VLAN IDs, with the default values specified for each object. After this initialization, the writable objects in this table need to be persistent upon reboot or restart of a device. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1,IEEE8021-CFM-MIB::dot1agCfmDefaultMdEntry,,not-accessible,dot1agCfmDefaultMdComponentId:dot1agCfmDefaultMdPrimaryVid,deprecated,,The Default MD Level table entry. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1.1,IEEE8021-CFM-MIB::dot1agCfmDefaultMdComponentId,Unsigned32,not-accessible,,deprecated,,The Bridge component within the system to which the information in this dot1agCfmDefaultMdEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1.2,IEEE8021-CFM-MIB::dot1agCfmDefaultMdPrimaryVid,Integer32,not-accessible,,deprecated,,The Primary VID of the VLAN to which this entry's objects apply. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1.3,IEEE8021-CFM-MIB::dot1agCfmDefaultMdStatus,INTEGER,read-only,,deprecated,true(1):false(2),State of this Default MD Level table entry. True if there is no entry in the Maintenance Association table defining an MA for the same VLAN ID and MD Level as this table's entry, and on which MA an Up MEP is defined, else false. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1.4,IEEE8021-CFM-MIB::dot1agCfmDefaultMdLevel,Integer32,read-write,,deprecated,,A value indicating the MD Level at which MHFs are to be created, and Sender ID TLV transmission by those MHFs is to be controlled, for the VLAN to which this entry's objects apply. If this object has the value -1, the MD Level for MHF creation for this VLAN is controlled by dot1agCfmDefaultMdDefLevel. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1.5,IEEE8021-CFM-MIB::dot1agCfmDefaultMdMhfCreation,INTEGER,read-write,,deprecated,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3):defMHFdefer(4),A value indicating if the Management entity can create MHFs (MIP Half Function) for this VID at this MD Level. If this object has the value defMHFdefer, MHF creation for this VLAN is controlled by dot1agCfmDefaultMdDefMhfCreation. The value of this variable is meaningless if the values of dot1agCfmDefaultMdStatus is false. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.4.1.6,IEEE8021-CFM-MIB::dot1agCfmDefaultMdIdPermission,INTEGER,read-write,,deprecated,sendIdNone(1):sendIdChassis(2):sendIdManage(3):sendIdChassisManage(4):sendIdDefer(5),Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MHFs created by the Default Maintenance Domain. If this object has the value sendIdDefer, Sender ID TLV transmission for this VLAN is controlled by dot1agCfmDefaultMdDefIdPermission. The value of this variable is meaningless if the values of dot1agCfmDefaultMdStatus is false. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.2.5,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdTable,,not-accessible,,current,,For each Bridge component, the Default MD Level Managed Object controls MHF creation for VIDs that are not attached to a specific Maintenance Association Managed Object, and Sender ID TLV transmission by those MHFs. For each Bridge Port, and for each VLAN ID whose data can pass through that Bridge Port, an entry in this table is used by the algorithm in 22.2.3 only if there is no entry in the Maintenance Association table defining an MA for the same VLAN ID and MD Level as this table's entry, and on which MA an Up MEP is defined. If there exists such an MA, that MA's objects are used by the algorithm in 22.2.3 in place of this table entry's objects. The agent maintains the value of ieee8021CfmDefaultMdStatus to indicate whether this entry is overridden by an MA. When first initialized, the agent creates this table automatically with entries for all VLAN IDs, with the default values specified for each object. After this initialization, the writable objects in this table need to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.2.5.1,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdEntry,,not-accessible,ieee8021CfmDefaultMdComponentId:ieee8021CfmDefaultMdPrimarySelectorType:ieee8021CfmDefaultMdPrimarySelector,current,,The Default MD Level table entry.
.1.3.111.2.802.1.1.8.1.2.5.1.1,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CfmDefaultMdEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.8.1.2.5.1.2,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdPrimarySelectorType,INTEGER,not-accessible,,current,vlanId(1):isid(2):tesid(3):segid(4):path-tesid(5):group-isid(6):ieeeReserved(7),Type of the Primary Service Selector identifier indicated by  ieee8021CfmDefaultMdPrimarySelector. See textual convention IEEE8021ServiceSelectorType for details. 
.1.3.111.2.802.1.1.8.1.2.5.1.3,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdPrimarySelector,Unsigned32,not-accessible,,current,,Primary Service Selector identifier of a Service Instance with  no MA configured. See IEEE8021ServiceSelectorValue for details. 
.1.3.111.2.802.1.1.8.1.2.5.1.4,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdStatus,INTEGER,read-only,,current,true(1):false(2),State of this Default MD Level table entry. True if there is no entry in the Maintenance Association table defining an MA for the same VLAN ID and MD Level as this table's entry, and on which MA an Up MEP is defined, else false. 
.1.3.111.2.802.1.1.8.1.2.5.1.5,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdLevel,Integer32,read-write,,current,,A value indicating the MD Level at which MHFs are to be created, and Sender ID TLV transmission by those MHFs is to be controlled, for the VLAN to which this entry's objects apply. 
.1.3.111.2.802.1.1.8.1.2.5.1.6,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdMhfCreation,INTEGER,read-write,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3):defMHFdefer(4),A value indicating if the Management entity can create MHFs (MIP Half Function) for this VID at this MD Level. If this object has the value defMHFdefer, MHF creation for this VLAN is controlled by ieee8021CfmDefaultMdDefMhfCreation. The value of this variable is meaningless if the values of ieee8021CfmDefaultMdStatus is false. 
.1.3.111.2.802.1.1.8.1.2.5.1.7,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdIdPermission,INTEGER,read-write,,current,sendIdNone(1):sendIdChassis(2):sendIdManage(3):sendIdChassisManage(4):sendIdDefer(5),Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MHFs created by the Default Maintenance Domain. If this object has the value sendIdDefer, Sender ID TLV transmission for this VLAN is controlled by ieee8021CfmDefaultMdDefIdPermission. The value of this variable is meaningless if the values of ieee8021CfmDefaultMdStatus is false. 
.1.3.111.2.802.1.1.8.1.3,IEEE8021-CFM-MIB::dot1agCfmVlan,,,,,,
.1.3.111.2.802.1.1.8.1.3.1,IEEE8021-CFM-MIB::dot1agCfmVlanTable,,not-accessible,,deprecated,,This table defines the association of VIDs into VLANs. There is an entry in this table, for each component of the Bridge, for each VID that is: a) a VID belonging to a VLAN associated with more than one VID; and b) not the Primary VLAN of that VID. The entry in this table contains the Primary VID of the VLAN. By default, this table is empty, meaning that every VID is the Primary VID of a single-VID VLAN. VLANs that are associated with only one VID SHOULD NOT have an entry in this table. The writable objects in this table need to be persistent upon reboot or restart of a device. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.3.1.1,IEEE8021-CFM-MIB::dot1agCfmVlanEntry,,not-accessible,dot1agCfmVlanComponentId:dot1agCfmVlanVid,deprecated,,The VLAN table entry. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.3.1.1.1,IEEE8021-CFM-MIB::dot1agCfmVlanComponentId,Unsigned32,not-accessible,,deprecated,,The Bridge component within the system to which the information in this dot1agCfmVlanEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.3.1.1.2,IEEE8021-CFM-MIB::dot1agCfmVlanVid,Integer32,not-accessible,,deprecated,,This is a VLAN ID belonging to a VLAN that is associated with more than one VLAN ID, and this is not the Primary VID of the VLAN. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.3.1.1.3,IEEE8021-CFM-MIB::dot1agCfmVlanPrimaryVid,Integer32,read-create,,deprecated,,This is the Primary VLAN ID of the VLAN with which this entry's dot1agCfmVlanVid is associated. This value MUST not equal the value of dot1agCfmVlanVid. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.3.1.1.4,IEEE8021-CFM-MIB::dot1agCfmVlanRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.3.2,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanTable,,not-accessible,,current,,This table defines the association of VIDs into VLANs. There is an entry in this table, for each component of the Bridge, for each VID that is: a) a VID belonging to a VLAN associated with more than one VID; and b) not the Primary VID of that VLAN. The entry in this table contains the Primary VID of the VLAN. By default, this table is empty, meaning that every VID is the Primary VID of a single-VID VLAN. VLANs that are associated with only one VID SHOULD NOT have an entry in this table. The writable objects in this table need to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.3.2.1,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanEntry,,not-accessible,ieee8021CfmVlanComponentId:ieee8021CfmVlanSelector,current,,The VLAN table entry.
.1.3.111.2.802.1.1.8.1.3.2.1.1,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CfmVlanEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.8.1.3.2.1.3,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanSelector,Unsigned32,not-accessible,,current,,This is a service ID belonging to a service that is associated with more than one Service Selector identifiers, and this is not the Primary  Service ID of the service. The type of this Service Selector is the same as the primary Service Selector's type defined by ieee8021CfmMaCompPrimarySelectorType  in the ieee8021CfmMaCompTable. 
.1.3.111.2.802.1.1.8.1.3.2.1.5,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanPrimarySelector,Unsigned32,read-create,,current,,This is the Primary Service selector for a Service that is associated with more than one Service Selector identifiers. This value MUST not equal the value of ieee8021CfmVlanSelector. The type of this Service Selector is the same as the primary Service Selector's type defined by ieee8021CfmMaCompPrimarySelectorType  in the ieee8021CfmMaCompTable. 
.1.3.111.2.802.1.1.8.1.3.2.1.6,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.8.1.4,IEEE8021-CFM-MIB::dot1agCfmConfigErrorList,,,,,,
.1.3.111.2.802.1.1.8.1.4.1,IEEE8021-CFM-MIB::dot1agCfmConfigErrorListTable,,not-accessible,,deprecated,,The CFM Configuration Error List table provides a list of Interfaces and VIDs that are incorrectly configured. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.4.1.1,IEEE8021-CFM-MIB::dot1agCfmConfigErrorListEntry,,not-accessible,dot1agCfmConfigErrorListVid:dot1agCfmConfigErrorListIfIndex,deprecated,,The Config Error List Table entry **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.4.1.1.1,IEEE8021-CFM-MIB::dot1agCfmConfigErrorListVid,Integer32,not-accessible,,deprecated,,The VLAN ID of the VLAN with interfaces in error. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.4.1.1.2,IEEE8021-CFM-MIB::dot1agCfmConfigErrorListIfIndex,Integer32,not-accessible,,deprecated,,This object is the IfIndex of the interface. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable so that it indexes the entry in the interface table with the same value of ifAlias that it indexed before the system restart. If no such entry exists, then the system SHALL delete any entries in dot1agCfmConfigErrorListTable indexed by that InterfaceIndex value. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.4.1.1.3,IEEE8021-CFM-MIB::dot1agCfmConfigErrorListErrorType,BITS,read-only,,deprecated,cfmLeak(0):conflictingVids(1):excessiveLevels(2):overlappedLevels(3),A vector of Boolean error conditions from 22.2.4, any of which may be true: 0) CFMleak; 1) ConflictingVids; 2) ExcessiveLevels; 3) OverlappedLevels. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.4.2,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListTable,,not-accessible,,current,,The CFM Configuration Error List table provides a list of Interfaces and VIDs that are incorrectly configured. 
.1.3.111.2.802.1.1.8.1.4.2.1,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListEntry,,not-accessible,ieee8021CfmConfigErrorListSelectorType:ieee8021CfmConfigErrorListSelector:ieee8021CfmConfigErrorListIfIndex,current,,The Config Error List Table entry
.1.3.111.2.802.1.1.8.1.4.2.1.1,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListSelectorType,INTEGER,not-accessible,,current,vlanId(1):isid(2):tesid(3):segid(4):path-tesid(5):group-isid(6):ieeeReserved(7),Type of the Service Selector identifier indicated by ieee8021CfmConfigErrorListSelector. See textual  convention IEEE8021ServiceSelectorType for details. 
.1.3.111.2.802.1.1.8.1.4.2.1.2,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListSelector,Unsigned32,not-accessible,,current,,The Service Selector Identifier of the Service with interfaces in error. See IEEE8021ServiceSelectorValue for details. 
.1.3.111.2.802.1.1.8.1.4.2.1.3,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListIfIndex,Integer32,not-accessible,,current,,This object is the IfIndex of the interface. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable so that it indexes the entry in the interface table with the same value of ifAlias that it indexed before the system restart. If no such entry exists, then the system SHALL delete any entries in ieee8021CfmConfigErrorListTable indexed by that InterfaceIndex value. 
.1.3.111.2.802.1.1.8.1.4.2.1.4,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListErrorType,BITS,read-only,,current,cfmLeak(0):conflictingVids(1):excessiveLevels(2):overlappedLevels(3),A vector of Boolean error conditions from 22.2.4, any of which may be true: 0) CFMleak; 1) ConflictingVids; 2) ExcessiveLevels; 3) OverlappedLevels. 
.1.3.111.2.802.1.1.8.1.5,IEEE8021-CFM-MIB::dot1agCfmMd,,,,,,
.1.3.111.2.802.1.1.8.1.5.1,IEEE8021-CFM-MIB::dot1agCfmMdTableNextIndex,Unsigned32,read-only,,current,,This object contains an unused value for dot1agCfmMdIndex in the dot1agCfmMdTable, or a zero to indicate that none exist. 
.1.3.111.2.802.1.1.8.1.5.2,IEEE8021-CFM-MIB::dot1agCfmMdTable,,not-accessible,,current,,The Maintenance Domain table. Each row in the table represents a different Maintenance Domain. A Maintenance Domain is described 3.135 as the network or the part of the network for which faults in connectivity are to be managed. The boundary of a Maintenance Domain is defined by a set of DSAPs, each of which can become a point of connectivity to a service instance. 
.1.3.111.2.802.1.1.8.1.5.2.1,IEEE8021-CFM-MIB::dot1agCfmMdEntry,,not-accessible,dot1agCfmMdIndex,current,,The Maintenance Domain table entry. This entry is not lost upon reboot. It is backed up by stable storage. 
.1.3.111.2.802.1.1.8.1.5.2.1.1,IEEE8021-CFM-MIB::dot1agCfmMdIndex,Unsigned32,not-accessible,,current,,The index to the Maintenance Domain table. dot1agCfmMdTableNextIndex needs to be inspected to find an available index for row-creation. Referential integrity is required, i.e., the index needs to be persistent upon a reboot or restart of a device. The index can never be reused for other Maintenance Domain. The index value SHOULD keep increasing up to the time that they wrap around. This is to facilitate access control based on OID. 
.1.3.111.2.802.1.1.8.1.5.2.1.2,IEEE8021-CFM-MIB::dot1agCfmMdFormat,INTEGER,read-create,,current,none(1):dnsLikeName(2):macAddressAndUint(3):charString(4),The type (and thereby format) of the Maintenance Domain Name.
.1.3.111.2.802.1.1.8.1.5.2.1.3,IEEE8021-CFM-MIB::dot1agCfmMdName,OCTET,read-create,,current,,The Maintenance Domain name. The type/format of this object is determined by the value of the dot1agCfmMdNameType object.  Each Maintenance Domain has unique name among all those used or available to a service provider or operator. It facilitates easy identification of administrative responsibility for each Maintenance Domain. 3.140 defines a Maintenance Domain name as the identifier, unique over the domain for which CFM is to protect against accidental concatenation of Service Instances, of a particular Maintenance Domain. 
.1.3.111.2.802.1.1.8.1.5.2.1.4,IEEE8021-CFM-MIB::dot1agCfmMdMdLevel,Integer32,read-create,,current,,The Maintenance Domain Level.
.1.3.111.2.802.1.1.8.1.5.2.1.5,IEEE8021-CFM-MIB::dot1agCfmMdMhfCreation,INTEGER,read-create,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3),Enumerated value indicating whether the management entity can create MHFs (MIP Half Function) for this Maintenance Domain. Since, in this variable, there is no encompassing Maintenance Domain, the value defMHFdefer is not allowed. 
.1.3.111.2.802.1.1.8.1.5.2.1.6,IEEE8021-CFM-MIB::dot1agCfmMdMhfIdPermission,INTEGER,read-create,,current,sendIdNone(1):sendIdChassis(2):sendIdManage(3):sendIdChassisManage(4),Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MPs configured in this Maintenance Domain. Since, in this variable, there is no encompassing Maintenance Domain, the value sendIdDefer is not allowed. 
.1.3.111.2.802.1.1.8.1.5.2.1.7,IEEE8021-CFM-MIB::dot1agCfmMdMaNextIndex,Unsigned32,read-only,,current,,Value to be used as the index of the MA table entries, both the dot1agCfmMaNetTable and the dot1agCfmMaCompTable, for this Maintenance Domain when the management entity wants to create a new row in those tables. 
.1.3.111.2.802.1.1.8.1.5.2.1.8,IEEE8021-CFM-MIB::dot1agCfmMdRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.8.1.6,IEEE8021-CFM-MIB::dot1agCfmMa,,,,,,
.1.3.111.2.802.1.1.8.1.6.1,IEEE8021-CFM-MIB::dot1agCfmMaNetTable,,not-accessible,,current,,The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. This is the part of the complete MA table that is constant across all Bridges in a Maintenance Domain, and across all components of a single Bridge. That part of the MA table that can vary from Bridge component to Bridge component is contained in the dot1agCfmMaCompTable. Creation of a Service Instance establishes a connectionless association among the selected DSAPs. Configuring a Maintenance association Endpoint (MEP) at each of the DSAPs creates a Maintenance Association (MA) to monitor that connectionless connectivity. The MA is identified by a Short MA Name that is unique within the Maintenance Domain and chosen to facilitate easy identification of the Service Instance. Together, the Maintenance Domain Name and the Short MA Name form the Maintenance Association Identifier (MAID) that is carried in CFM Messages to identify incorrect connectivity among Service Instances. A small integer, the Maintenance association Endpoint Identifier (MEPID), identifies each MEP among those configured on a single MA (3.132, 18.2). This table uses two indices, first index is the index of the Maintenance Domain table. The second index is the same as the index of the dot1agCfmMaCompEntry for the same MA. The writable objects in this table need to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.6.1.1,IEEE8021-CFM-MIB::dot1agCfmMaNetEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex,current,,The MA table entry.
.1.3.111.2.802.1.1.8.1.6.1.1.1,IEEE8021-CFM-MIB::dot1agCfmMaIndex,Unsigned32,not-accessible,,current,,Index of the MA table dot1agCfmMdMaNextIndex needs to be inspected to find an available index for row-creation. 
.1.3.111.2.802.1.1.8.1.6.1.1.2,IEEE8021-CFM-MIB::dot1agCfmMaNetFormat,INTEGER,read-create,,current,primaryVid(1):charString(2):unsignedInt16(3):rfc2865VpnId(4):iccFormat(32),The type (and thereby format) of the Maintenance Association Name. 
.1.3.111.2.802.1.1.8.1.6.1.1.3,IEEE8021-CFM-MIB::dot1agCfmMaNetName,OCTET,read-create,,current,,The Short Maintenance Association name. The type/format of this object is determined by the value of the dot1agCfmMaNetNameType object. This name MUST be unique within a maintenance domain. 
.1.3.111.2.802.1.1.8.1.6.1.1.4,IEEE8021-CFM-MIB::dot1agCfmMaNetCcmInterval,INTEGER,read-create,,current,intervalInvalid(0):interval300Hz(1):interval10ms(2):interval100ms(3):interval1s(4):interval10s(5):interval1min(6):interval10min(7),Interval between CCM transmissions to be used by all MEPs in the MA. 
.1.3.111.2.802.1.1.8.1.6.1.1.5,IEEE8021-CFM-MIB::dot1agCfmMaNetRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.8.1.6.2,IEEE8021-CFM-MIB::dot1agCfmMaCompTable,,not-accessible,,deprecated,,The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. This is the part of the complete MA table that is variable across the Bridges in a Maintenance Domain, or across the components of a single Bridge. That part of the MA table that is constant across the Bridges and their components in a Maintenance Domain is contained in the dot1agCfmMaNetTable. This table uses three indices, first index is the Dot1agCfmPbbComponentIdentifier that identifies the component within the Bridge for which the information in the dot1agCfmMaCompEntry applies. The second is the index of the Maintenance Domain table. The third index is the same as the index of the dot1agCfmMaNetEntry for the same MA. The writable objects in this table need to be persistent upon reboot or restart of a device. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1,IEEE8021-CFM-MIB::dot1agCfmMaCompEntry,,not-accessible,dot1agCfmMaComponentId:dot1agCfmMdIndex:dot1agCfmMaIndex,deprecated,,The MA table entry. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1.1,IEEE8021-CFM-MIB::dot1agCfmMaComponentId,Unsigned32,not-accessible,,deprecated,,The Bridge component within the system to which the information in this dot1agCfmMaCompEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1.2,IEEE8021-CFM-MIB::dot1agCfmMaCompPrimaryVlanId,Integer32,read-create,,deprecated,,The Primary VLAN ID with which the Maintenance Association is associated, or 0 if the MA is not attached to any VID. If the MA is associated with more than one VID, the dot1agCfmVlanTable lists them. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1.3,IEEE8021-CFM-MIB::dot1agCfmMaCompMhfCreation,INTEGER,read-create,,deprecated,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3):defMHFdefer(4),Indicates if the Management entity can create MHFs (MIP Half Function) for this MA. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1.4,IEEE8021-CFM-MIB::dot1agCfmMaCompIdPermission,INTEGER,read-create,,deprecated,sendIdNone(1):sendIdChassis(2):sendIdManage(3):sendIdChassisManage(4):sendIdDefer(5),Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MPs configured in this MA. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1.5,IEEE8021-CFM-MIB::dot1agCfmMaCompNumberOfVids,Unsigned32,read-create,,deprecated,,The number of VIDs associated with the MA. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.2.1.6,IEEE8021-CFM-MIB::dot1agCfmMaCompRowStatus,INTEGER,read-create,,deprecated,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. **NOTE: this object is deprecated due to re-indexing of the  table. 
.1.3.111.2.802.1.1.8.1.6.3,IEEE8021-CFM-MIB::dot1agCfmMaMepListTable,,not-accessible,,current,,List of MEPIDs that belong to this MA. 12.14.6.1.3 specifies that a list of MEPIDs in all Bridges in that MA, but since SNMP SMI does not allow to state in a MIB that an object in a table is an array, the  information has to be stored in another table with two indices, being the first index, the index of the table that  contains the list or array. For all Bridges in which the same MAID {dot1agCfmMdFormat, dot1agCfmMdName, dot1agCfmMaNetFormat, and dot1agCfmMaNetName} is configured, the same set of dot1agCfmMaMepListIdentifiers MUST be configured in the Bridges' dot1agCfmMaMepListTables. This allows each MEP to determine whether or not it is receiving CCMs from all of the other MEPs in the MA. For example, if one were creating a new MA whose MAID were {charString, 'Dom1', charString, 'MA1'}, that had 2 MEPs, whose MEPIDs were 1 and 3, one could, in Bridge A: 1. Get a new MD index d from dot1agCfmMdTableNextIndex. 2. Create the Maintenance Domain {charString, 'Dom1'}. 3. Get a new MA index a from dot1agCfmMdMaNextIndex [d]. 4. Create the Maintenance Association {charString, 'MA1'}. 5. Create a new dot1agCfmMaMepListEntry for each of the MEPs in the MA: [d, a, 1] and [d, a, 3]. 6. Create one of the new MEPs, say [d, a, 1]. Then, in Bridge B: 7. Do all of these steps 1-6, except for using the other MEPID for the new MEP in Step 6, in this example, MEPID 3. Note that, when creating the MA, MEP List Table, and MEP entries in the second Bridge, the indices 'd' and 'a' identifying the MAID {charString, 'Dom1', charString, 'MA1'} may have different values than those in the first Bridge. 
.1.3.111.2.802.1.1.8.1.6.3.1,IEEE8021-CFM-MIB::dot1agCfmMaMepListEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMaMepListIdentifier,current,,The known MEPS table entry.
.1.3.111.2.802.1.1.8.1.6.3.1.1,IEEE8021-CFM-MIB::dot1agCfmMaMepListIdentifier,Unsigned32,not-accessible,,current,,MEPID
.1.3.111.2.802.1.1.8.1.6.3.1.2,IEEE8021-CFM-MIB::dot1agCfmMaMepListRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. Read SNMPv2-TC (RFC1903) for an explanation of the possible values this object can take. 
.1.3.111.2.802.1.1.8.1.6.4,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompTable,,not-accessible,,current,,The Maintenance Association table. Each row in the table represents an MA. An MA is a set of MEPs, each configured with a single service instance. This is the part of the complete MA table that is variable across the Bridges in a Maintenance Domain, or across the components of a single Bridge. That part of the MA table that is constant across the Bridges and their components in a Maintenance Domain is contained in the dot1agCfmMaNetTable. This table uses three indices, first index is the IEEE8021PbbComponentIdentifier that identifies the component within the Bridge for which the information in the ieee8021CfmMaCompEntry applies. The second is the index of the Maintenance Domain table. The third index is the same as the index of the ieee8021CfmMaNetEntry for the same MA. The writable objects in this table need to be persistent upon reboot or restart of a device. 
.1.3.111.2.802.1.1.8.1.6.4.1,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompEntry,,not-accessible,ieee8021CfmMaComponentId:dot1agCfmMdIndex:dot1agCfmMaIndex,current,,The MA table entry.
.1.3.111.2.802.1.1.8.1.6.4.1.1,IEEE8021-CFM-V2-MIB::ieee8021CfmMaComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CfmMaCompEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.8.1.6.4.1.2,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompPrimarySelectorType,INTEGER,read-create,,current,vlanId(1):isid(2):tesid(3):segid(4):path-tesid(5):group-isid(6):ieeeReserved(7),Type of the Service Selector identifiers indicated by  ieee8021CfmMaCompPrimarySelectorOrNone. If the service  instance is defined by more than one Service Selector, this  parameter also indicates the type of the  ieee8021CfmVlanPrimarySelector and ieee8021CfmVlanSelector in the ieee8021CfmVlanTable.  In Services instances made of multiple Service Selector identifiers, ensures that the type of the Service selector identifiers is the same. See textual convention  IEEE8021ServiceSelectorType for details. 
.1.3.111.2.802.1.1.8.1.6.4.1.3,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompPrimarySelectorOrNone,Unsigned32,read-create,,current,,Service Selector identifier to which the MP is attached, or 0, if none. If the MA is associated with more than one Service Selectors Identifiers, the ieee8021CfmVlanTable lists them. 
.1.3.111.2.802.1.1.8.1.6.4.1.4,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompMhfCreation,INTEGER,read-create,,current,defMHFnone(1):defMHFdefault(2):defMHFexplicit(3):defMHFdefer(4),Indicates if the Management entity can create MHFs (MIP Half Function) for this MA. 
.1.3.111.2.802.1.1.8.1.6.4.1.5,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompIdPermission,INTEGER,read-create,,current,sendIdNone(1):sendIdChassis(2):sendIdManage(3):sendIdChassisManage(4):sendIdDefer(5),Enumerated value indicating what, if anything, is to be included in the Sender ID TLV (21.5.3) transmitted by MPs configured in this MA. 
.1.3.111.2.802.1.1.8.1.6.4.1.6,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompNumberOfVids,Unsigned32,read-create,,current,,The number of VIDs associated with the MA. 
.1.3.111.2.802.1.1.8.1.6.4.1.7,IEEE8021-CFM-V2-MIB::ieee8021CfmMaCompRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.8.1.7,IEEE8021-CFM-MIB::dot1agCfmMep,,,,,,
.1.3.111.2.802.1.1.8.1.7.1,IEEE8021-CFM-MIB::dot1agCfmMepTable,,not-accessible,,current,,The Maintenance Association Endpoint (MEP) table. Each row in the table represents a different MEP. A MEP is an actively managed CFM entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM PDUs and track any responses. It is an endpoint of a single Maintenance Association, and is an endpoint of a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association (3.132). This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a MEP is always related to an MA and Maintenance Domain. The MEP table also stores all the managed objects for sending LBM and LTM. *LBM Managed objects LBM Managed objects in the MEP table enables the management entity to initiate transmission of Loopback messages. It will signal the MEP that it SHOULD transmit some number of Loopback messages and detect the detection (or lack thereof) of the corresponding Loopback messages. Steps to use entries in this table: 1) Wait for dot1agCfmMepTransmitLbmStatus value to be false. To do this do this sequence: a. an SNMP GET for both SnmpSetSerialNo and dot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU). b. Check if value for dot1agCfmMepTransmitLbmStatus is false. - if not, wait x seconds, go to step a above. - if yes, save the value of SnmpSetSerialNo and go to step 2) below 2) Change dot1agCfmMepTransmitLbmStatus value from false to true to ensure no other management entity will use the service. In order to not disturb a possible other NMS do this by sending an SNMP SET for both SnmpSetSerialNo and dot1agCfmMepTransmitLbmStatus objects (in same SNMP PDU, and make sure SNmpSetSerialNo is the first varBind). For the SnmpSetSerialNo varBind, use the value that you obtained in step 1)a.. This ensures that two cooperating NMSes will not step on each others toes. Setting this MIB object does not set the corresponding LBIactive state machine variable. 3) Setup the different data to be sent (number of messages, optional TLVs,...), except do not set dot1agCfmMepTransmitLbmMessages. 4) Record the current values of dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu. 6) Set dot1agCfmMepTransmitLbmMessages to a non-zero value to initiate transmission of Loopback messages. The dot1agCfmMepTransmitLbmMessages indicates the number of LBMs to be sent and is not decremented as loopbacks are actually sent. dot1agCfmMepTransmitLbmMessages is not equivalent to the LBMsToSend state machine variable. 7) Check the value of dot1agCfmMepTransmitLbmResultOK to find out if the operation was successfully initiated or not. 8) Monitor the value of dot1agCfmMepTransmitLbmStatus. When it is reset to false, the last LBM has been transmitted. Wait an additional 5 seconds to ensure that all LBRs have been returned. 9) Compare dot1agCfmMepLbrIn, dot1agCfmMepLbrInOutOfOrder, and dot1agCfmMepLbrBadMsdu to their old values from step 4, above, to get the results of the test. *LTM Managed objects The LTM Managed objects in the MEP table are used in a manner similar to that described for LBM transmission, above. A SET operation to the variable dot1agCfmMepTransmitLtmFlags triggers the transmission of an LTM. Then, the variables dot1agCfmMepTransmitLtmSeqNumber and dot1agCfmMepTransmitLtmEgressIdentifier return the information required to recover the resu
.1.3.111.2.802.1.1.8.1.7.1.1,IEEE8021-CFM-MIB::dot1agCfmMepEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier,current,,The MEP table entry
.1.3.111.2.802.1.1.8.1.7.1.1.1,IEEE8021-CFM-MIB::dot1agCfmMepIdentifier,Unsigned32,not-accessible,,current,,Integer that is unique among all the MEPs in the same MA. Other definition is: a small integer, unique over a given Maintenance Association, identifying a specific Maintenance association Endpoint (3.132). MEP Identifier is also known as the MEPID. 
.1.3.111.2.802.1.1.8.1.7.1.1.2,IEEE8021-CFM-MIB::dot1agCfmMepIfIndex,Integer32,read-create,,current,,This object is the interface index of the interface either a Bridge Port, or an aggregated IEEE 802.1 link within a Bridge port, to which the MEP is attached. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable so that it indexes the entry in the interface table with the same value of ifAlias that it indexed before the system restart. If no such entry exists, then the system SHALL set this variable to 0. 
.1.3.111.2.802.1.1.8.1.7.1.1.3,IEEE8021-CFM-MIB::dot1agCfmMepDirection,INTEGER,read-create,,current,down(1):up(2),The direction in which the MEP faces on the Bridge port.
.1.3.111.2.802.1.1.8.1.7.1.1.4,IEEE8021-CFM-MIB::dot1agCfmMepPrimaryVid,Unsigned32,read-create,,current,,An integer indicating the Primary VID of the MEP, always one of the VIDs assigned to the MEP's MA. The value 0 indicates that either the Primary VID is that of the MEP's MA, or that the MEP's MA is associated with no VID.
.1.3.111.2.802.1.1.8.1.7.1.1.5,IEEE8021-CFM-MIB::dot1agCfmMepActive,INTEGER,read-create,,current,true(1):false(2),Administrative state of the MEP A Boolean indicating the administrative state of the MEP. True indicates that the MEP is to function normally, and false that it is to cease functioning.
.1.3.111.2.802.1.1.8.1.7.1.1.6,IEEE8021-CFM-MIB::dot1agCfmMepFngState,INTEGER,read-only,,current,fngReset(1):fngDefect(2):fngReportDefect(3):fngDefectReported(4):fngDefectClearing(5),Current state of the MEP Fault Notification Generator State Machine. 
.1.3.111.2.802.1.1.8.1.7.1.1.7,IEEE8021-CFM-MIB::dot1agCfmMepCciEnabled,INTEGER,read-create,,current,true(1):false(2),If set to true, the MEP will generate CCM messages.
.1.3.111.2.802.1.1.8.1.7.1.1.8,IEEE8021-CFM-MIB::dot1agCfmMepCcmLtmPriority,Unsigned32,read-create,,current,,The priority value for CCMs and LTMs transmitted by the MEP. Default Value is the highest priority value allowed to pass through the Bridge Port for any of this MEPs VIDs. The management entity can obtain the default value for this  variable from the priority regeneration table by extracting the  highest priority value in this table on this MEPs Bridge Port. (1 is lowest, then 2, then 0, then 3-7). 
.1.3.111.2.802.1.1.8.1.7.1.1.9,IEEE8021-CFM-MIB::dot1agCfmMepMacAddress,OCTET,read-only,,current,,MAC address of the MEP.
.1.3.111.2.802.1.1.8.1.7.1.1.10,IEEE8021-CFM-MIB::dot1agCfmMepLowPrDef,INTEGER,read-create,,current,allDef(1):macRemErrXcon(2):remErrXcon(3):errXcon(4):xcon(5):noXcon(6),An integer value specifying the lowest priority defect  that is allowed to generate fault alarm. 
.1.3.111.2.802.1.1.8.1.7.1.1.11,IEEE8021-CFM-MIB::dot1agCfmMepFngAlarmTime,INTEGER,read-create,,current,,The time that defects MUST be present before a Fault Alarm is issued (fngAlarmTime, 20.3.3) (default 2.5s). 
.1.3.111.2.802.1.1.8.1.7.1.1.12,IEEE8021-CFM-MIB::dot1agCfmMepFngResetTime,INTEGER,read-create,,current,,The time that defects MUST be absent before resetting a Fault Alarm (fngResetTime, 20.35.4) (default 10s). 
.1.3.111.2.802.1.1.8.1.7.1.1.13,IEEE8021-CFM-MIB::dot1agCfmMepHighestPrDefect,INTEGER,read-only,,current,none(0):defRDICCM(1):defMACstatus(2):defRemoteCCM(3):defErrorCCM(4):defXconCCM(5),The highest priority defect that has been present since the MEPs Fault Notification Generator State Machine was last in the FNG_RESET state. 
.1.3.111.2.802.1.1.8.1.7.1.1.14,IEEE8021-CFM-MIB::dot1agCfmMepDefects,BITS,read-only,,current,bDefRDICCM(0):bDefMACstatus(1):bDefRemoteCCM(2):bDefErrorCCM(3):bDefXconCCM(4),A vector of Boolean error conditions from Table 20-1, any of which may be true: DefRDICCM(0) DefMACstatus(1) DefRemoteCCM(2) DefErrorCCM(3) DefXconCCM(4) 
.1.3.111.2.802.1.1.8.1.7.1.1.15,IEEE8021-CFM-MIB::dot1agCfmMepErrorCcmLastFailure,OCTET,read-only,,current,,The last-received CCM that triggered an DefErrorCCM fault.
.1.3.111.2.802.1.1.8.1.7.1.1.16,IEEE8021-CFM-MIB::dot1agCfmMepXconCcmLastFailure,OCTET,read-only,,current,,The last-received CCM that triggered a DefXconCCM fault.
.1.3.111.2.802.1.1.8.1.7.1.1.17,IEEE8021-CFM-MIB::dot1agCfmMepCcmSequenceErrors,Counter32,read-only,,current,,The total number of out-of-sequence CCMs received from all remote MEPs. 
.1.3.111.2.802.1.1.8.1.7.1.1.18,IEEE8021-CFM-MIB::dot1agCfmMepCciSentCcms,Counter32,read-only,,current,,Total number of Continuity Check messages transmitted.
.1.3.111.2.802.1.1.8.1.7.1.1.19,IEEE8021-CFM-MIB::dot1agCfmMepNextLbmTransId,Unsigned32,read-only,,current,,Next sequence number/transaction identifier to be sent in a Loopback message. This sequence number can be zero because it wraps around. 
.1.3.111.2.802.1.1.8.1.7.1.1.20,IEEE8021-CFM-MIB::dot1agCfmMepLbrIn,Counter32,read-only,,current,,Total number of valid, in-order Loopback Replies received.
.1.3.111.2.802.1.1.8.1.7.1.1.21,IEEE8021-CFM-MIB::dot1agCfmMepLbrInOutOfOrder,Counter32,read-only,,current,,The total number of valid, out-of-order Loopback Replies received. 
.1.3.111.2.802.1.1.8.1.7.1.1.22,IEEE8021-CFM-MIB::dot1agCfmMepLbrBadMsdu,Counter32,read-only,,current,,The total number of LBRs received whose mac_service_data_unit did not match (except for the OpCode) that of the corresponding LBM (20.2.3). 
.1.3.111.2.802.1.1.8.1.7.1.1.23,IEEE8021-CFM-MIB::dot1agCfmMepLtmNextSeqNumber,Unsigned32,read-only,,current,,Next transaction identifier/sequence number to be sent in a Linktrace message. This sequence number can be zero because it wraps around. 
.1.3.111.2.802.1.1.8.1.7.1.1.24,IEEE8021-CFM-MIB::dot1agCfmMepUnexpLtrIn,Counter32,read-only,,current,,The total number of unexpected LTRs received (20.39.1). 
.1.3.111.2.802.1.1.8.1.7.1.1.25,IEEE8021-CFM-MIB::dot1agCfmMepLbrOut,Counter32,read-only,,current,,Total number of Loopback Replies transmitted.
.1.3.111.2.802.1.1.8.1.7.1.1.26,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmStatus,INTEGER,read-create,,current,true(1):false(2),A Boolean flag set to true by the MEP Loopback Initiator State Machine or an MIB manager to indicate that another LBM is being transmitted. Reset to false by the MEP Loopback Initiator State Machine.
.1.3.111.2.802.1.1.8.1.7.1.1.27,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmDestMacAddress,OCTET,read-create,,current,,The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is 'false'. 
.1.3.111.2.802.1.1.8.1.7.1.1.28,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmDestMepId,Unsigned32,read-create,,current,,The Maintenance association Endpoint Identifier of another MEP in the same Maintenance Association to which the LBM is to be sent. This address will be used if the value of the column dot1agCfmMepTransmitLbmDestIsMepId is 'true'. 
.1.3.111.2.802.1.1.8.1.7.1.1.29,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmDestIsMepId,INTEGER,read-create,,current,true(1):false(2),True indicates that MEPID of the target MEP is used for Loopback transmission. False indicates that unicast destination MAC address of the target MEP is used for Loopback transmission. 
.1.3.111.2.802.1.1.8.1.7.1.1.30,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmMessages,Integer32,read-create,,current,,The number of Loopback messages to be transmitted.
.1.3.111.2.802.1.1.8.1.7.1.1.31,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmDataTlv,OCTET,read-create,,current,,An arbitrary amount of data to be included in the Data TLV, if the Data TLV is selected to be sent. The intent is to be able to fill the frame carrying the CFM PDU to its maximum length. This may lead to fragmentation in some cases. 
.1.3.111.2.802.1.1.8.1.7.1.1.32,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmVlanPriority,Integer32,read-create,,current,,Priority. 3 bit value to be used in the VLAN tag, if present in the transmitted frame. The default value is CCM priority. 
.1.3.111.2.802.1.1.8.1.7.1.1.33,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmVlanDropEnable,INTEGER,read-create,,current,true(1):false(2),Drop Enable bit value to be used in the VLAN tag, if present in the transmitted frame. For more information about VLAN Drop Enable, check IEEE Std 802.1ad. 
.1.3.111.2.802.1.1.8.1.7.1.1.34,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmResultOK,INTEGER,read-only,,current,true(1):false(2),Indicates the result of the operation: - true The Loopback Message(s) will be (or has been) sent. - false The Loopback Message(s) will not be sent. 
.1.3.111.2.802.1.1.8.1.7.1.1.35,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLbmSeqNumber,Unsigned32,read-only,,current,,The Loopback Transaction Identifier (dot1agCfmMepNextLbmTransId) of the first LBM (to be) sent. The value returned is undefined if dot1agCfmMepTransmitLbmResultOK is false. 
.1.3.111.2.802.1.1.8.1.7.1.1.36,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmStatus,INTEGER,read-create,,current,true(1):false(2),A Boolean flag set to true by the Bridge Port to indicate that another LTM may be transmitted.  Reset to false by the MEP Linktrace Initiator State Machine.
.1.3.111.2.802.1.1.8.1.7.1.1.37,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmFlags,BITS,read-create,,current,useFDBonly(0),The flags field for LTMs transmitted by the MEP.
.1.3.111.2.802.1.1.8.1.7.1.1.38,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmTargetMacAddress,OCTET,read-create,,current,,The Target MAC Address Field to be transmitted: A unicast destination MAC address. This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is 'false'. 
.1.3.111.2.802.1.1.8.1.7.1.1.39,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmTargetMepId,Unsigned32,read-create,,current,,An indication of the Target MAC Address Field to be transmitted: The Maintenance association Endpoint Identifier of another MEP in the same Maintenance Association This address will be used if the value of the column dot1agCfmMepTransmitLtmTargetIsMepId is 'true'. 
.1.3.111.2.802.1.1.8.1.7.1.1.40,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmTargetIsMepId,INTEGER,read-create,,current,true(1):false(2),True indicates that MEPID of the target MEP is used for Linktrace transmission. False indicates that unicast destination MAC address of the target MEP is used for Loopback transmission. 
.1.3.111.2.802.1.1.8.1.7.1.1.41,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmTtl,Unsigned32,read-create,,current,,The LTM TTL field. Default value, if not specified, is 64. The TTL field indicates the number of hops remaining to the LTM. Decremented by 1 by each Linktrace Responder that handles the LTM. The value returned in the LTR is one less than that received in the LTM. If the LTM TTL is 0 or 1, the LTM is not forwarded to the next hop, and if 0, no LTR is generated. 
.1.3.111.2.802.1.1.8.1.7.1.1.42,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmResult,INTEGER,read-only,,current,true(1):false(2),Indicates the result of the operation: - true The Linktrace Message will be (or has been) sent. - false The Linktrace Message will not be sent
.1.3.111.2.802.1.1.8.1.7.1.1.43,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmSeqNumber,Unsigned32,read-only,,current,,The LTM Transaction Identifier (dot1agCfmMepLtmNextSeqNumber) of the LTM sent. The value returned is undefined if dot1agCfmMepTransmitLtmResult is false. 
.1.3.111.2.802.1.1.8.1.7.1.1.44,IEEE8021-CFM-MIB::dot1agCfmMepTransmitLtmEgressIdentifier,OCTET,read-create,,current,,Identifies the MEP Linktrace Initiator that is originating, or the Linktrace Responder that is forwarding, this LTM. The low-order six octets contain a 48-bit IEEE MAC address unique to the system in which the MEP Linktrace Initiator or Linktrace Responder resides. The high-order two octets contain a value sufficient to uniquely identify the MEP Linktrace Initiator or Linktrace Responder within that system. For most Bridges, the address of any MAC attached to the Bridge will suffice for the low-order six octets, and 0 for the high-order octets. In some situations, e.g., if multiple virtual Bridges utilizing emulated LANs are implemented in a single physical system, the high-order two octets can be used to differentiate among the transmitting entities. The value returned is undefined if dot1agCfmMepTransmitLtmResult is false. 
.1.3.111.2.802.1.1.8.1.7.1.1.45,IEEE8021-CFM-MIB::dot1agCfmMepRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.8.1.7.1.1.46,IEEE8021-CFM-MIB::dot1agCfmMepPbbTeCanReportPbbTePresence,INTEGER,read-create,,current,true(1):false(2),A Boolean valued parameter that is set to true if the system has the capability to report the presence of traffic and that the capability is enabled. Traffic presence reporting is an optional PBB-TE feature.
.1.3.111.2.802.1.1.8.1.7.1.1.47,IEEE8021-CFM-MIB::dot1agCfmMepPbbTeTrafficMismatchDefect,INTEGER,read-only,,current,true(1):false(2),A Boolean valued parameter that is set to true if the system has detected a traffic field mismatch defect. Mismatch detection is an optional PBB-TE feature.
.1.3.111.2.802.1.1.8.1.7.1.1.48,IEEE8021-CFM-MIB::dot1agCfmMepPbbTransmitLbmLtmReverseVid,Unsigned32,read-create,,current,,This column specifies the value to use in the Reverse VID value field of PBB-TE MIP TLVs contained within TransmitLTM pdus.
.1.3.111.2.802.1.1.8.1.7.1.1.49,IEEE8021-CFM-MIB::dot1agCfmMepPbbTeMismatchAlarm,INTEGER,read-create,,current,true(1):false(2),A Boolean valued parameter that is set to true if the system is to allow a mismatch defect to generate a fault alarm.
.1.3.111.2.802.1.1.8.1.7.1.1.50,IEEE8021-CFM-MIB::dot1agCfmMepPbbTeLocalMismatchDefect,INTEGER,read-only,,current,true(1):false(2),A Boolean valued parameter that is set to true if the system has detected a local mismatch defect. Mismatch detection is an optional PBB-TE feature.
.1.3.111.2.802.1.1.8.1.7.1.1.51,IEEE8021-CFM-MIB::dot1agCfmMepPbbTeMismatchSinceReset,INTEGER,read-only,,current,true(1):false(2),A Boolean valued parameter indicating if the mismatch defect has been present since the MEP Mismatch Fault Notification Generator was last in the MFNG_RESET state.
.1.3.111.2.802.1.1.8.1.7.2,IEEE8021-CFM-MIB::dot1agCfmLtrTable,,not-accessible,,current,,This table extends the MEP table and contains a list of Linktrace replies received by a specific MEP in response to a linktrace message. SNMP SMI does not allow to state in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices. 
.1.3.111.2.802.1.1.8.1.7.2.1,IEEE8021-CFM-MIB::dot1agCfmLtrEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:dot1agCfmLtrSeqNumber:dot1agCfmLtrReceiveOrder,current,,The Linktrace Reply table entry.
.1.3.111.2.802.1.1.8.1.7.2.1.1,IEEE8021-CFM-MIB::dot1agCfmLtrSeqNumber,Unsigned32,not-accessible,,current,,Transaction identifier/Sequence number returned by a previous transmit linktrace message command, indicating which LTM's response is going to be returned. 
.1.3.111.2.802.1.1.8.1.7.2.1.2,IEEE8021-CFM-MIB::dot1agCfmLtrReceiveOrder,Unsigned32,not-accessible,,current,,An index to distinguish among multiple LTRs with the same LTR Transaction Identifier field value. dot1agCfmLtrReceiveOrder are assigned sequentially from 1, in the order that the Linktrace Initiator received the LTRs. 
.1.3.111.2.802.1.1.8.1.7.2.1.3,IEEE8021-CFM-MIB::dot1agCfmLtrTtl,Unsigned32,read-only,,current,,TTL field value for a returned LTR.
.1.3.111.2.802.1.1.8.1.7.2.1.4,IEEE8021-CFM-MIB::dot1agCfmLtrForwarded,INTEGER,read-only,,current,true(1):false(2),Indicates if a LTM was forwarded by the responding MP, as returned in the 'FwdYes' flag of the flags field. 
.1.3.111.2.802.1.1.8.1.7.2.1.5,IEEE8021-CFM-MIB::dot1agCfmLtrTerminalMep,INTEGER,read-only,,current,true(1):false(2),A Boolean value stating whether the forwarded LTM reached a MEP enclosing its MA, as returned in the Terminal MEP flag of the Flags field. 
.1.3.111.2.802.1.1.8.1.7.2.1.6,IEEE8021-CFM-MIB::dot1agCfmLtrLastEgressIdentifier,OCTET,read-only,,current,,An octet field holding the Last Egress Identifier returned in the LTR Egress Identifier TLV of the LTR. The Last Egress Identifier identifies the MEP Linktrace  Initiator that originated, or the Linktrace Responder that  forwarded, the LTM to which this LTR is the response. This is the same value as the Egress Identifier TLV of that LTM. 
.1.3.111.2.802.1.1.8.1.7.2.1.7,IEEE8021-CFM-MIB::dot1agCfmLtrNextEgressIdentifier,OCTET,read-only,,current,,An octet field holding the Next Egress Identifier returned in the LTR Egress Identifier TLV of the LTR. The Next Egress Identifier Identifies the Linktrace Responder that transmitted this LTR, and can forward the LTM to the next hop. This is the same value as the Egress Identifier TLV of the forwarded LTM, if any. If the FwdYes bit of the Flags field is false, the contents of this field are undefined, i.e., any value can be transmitted, and the field is ignored by the receiver. 
.1.3.111.2.802.1.1.8.1.7.2.1.8,IEEE8021-CFM-MIB::dot1agCfmLtrRelay,INTEGER,read-only,,current,rlyHit(1):rlyFdb(2):rlyMpdb(3),Value returned in the Relay Action field.
.1.3.111.2.802.1.1.8.1.7.2.1.9,IEEE8021-CFM-MIB::dot1agCfmLtrChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),This object specifies the format of the Chassis ID returned in the Sender ID TLV of the LTR, if any. This value is meaningless if the dot1agCfmLtrChassisId has a length of 0.
.1.3.111.2.802.1.1.8.1.7.2.1.10,IEEE8021-CFM-MIB::dot1agCfmLtrChassisId,OCTET,read-only,,current,,The Chassis ID returned in the Sender ID TLV of the LTR, if any. The format of this object is determined by the value of the dot1agCfmLtrChassisIdSubtype object. 
.1.3.111.2.802.1.1.8.1.7.2.1.11,IEEE8021-CFM-MIB::dot1agCfmLtrManAddressDomain,OBJECT,read-only,,current,,The TDomain that identifies the type and format of the related dot1agCfmMepDbManAddress object, used to access the SNMP agent of the system transmitting the LTR. Received in the LTR Sender ID TLV from that system. Typical values will be one of (not all inclusive) list: snmpUDPDomain (from SNMPv2-TM, RFC3417) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB, RFC4789) The value 'zeroDotZero' (from RFC2578) indicates 'no management address was present in the LTR', in which case the related object dot1agCfmMepDbManAddress MUST have a zero-length OCTET STRING as a value. 
.1.3.111.2.802.1.1.8.1.7.2.1.12,IEEE8021-CFM-MIB::dot1agCfmLtrManAddress,OCTET,read-only,,current,,The TAddress that can be used to access the SNMP agent of the system transmitting the CCM, received in the CCM Sender ID TLV from that system. If the related object dot1agCfmLtrManAddressDomain contains the value 'zeroDotZero', this object dot1agCfmLtrManAddress MUST have a zero-length OCTET STRING as a value. 
.1.3.111.2.802.1.1.8.1.7.2.1.13,IEEE8021-CFM-MIB::dot1agCfmLtrIngress,INTEGER,read-only,,current,ingNoTlv(0):ingOk(1):ingDown(2):ingBlocked(3):ingVid(4),The value returned in the Ingress Action Field of the LTM. The value ingNoTlv(0) indicates that no Reply Ingress TLV was returned in the LTM.
.1.3.111.2.802.1.1.8.1.7.2.1.14,IEEE8021-CFM-MIB::dot1agCfmLtrIngressMac,OCTET,read-only,,current,,MAC address returned in the ingress MAC address field. If the dot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless.
.1.3.111.2.802.1.1.8.1.7.2.1.15,IEEE8021-CFM-MIB::dot1agCfmLtrIngressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Format of the Ingress Port ID. If the dot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless.
.1.3.111.2.802.1.1.8.1.7.2.1.16,IEEE8021-CFM-MIB::dot1agCfmLtrIngressPortId,OCTET,read-only,,current,,Ingress Port ID. The format of this object is determined by the value of the dot1agCfmLtrIngressPortIdSubtype object. If the dot1agCfmLtrIngress object contains the value ingNoTlv(0), then the contents of this object are meaningless.
.1.3.111.2.802.1.1.8.1.7.2.1.17,IEEE8021-CFM-MIB::dot1agCfmLtrEgress,INTEGER,read-only,,current,egrNoTlv(0):egrOK(1):egrDown(2):egrBlocked(3):egrVid(4),The value returned in the Egress Action Field of the LTM. The value egrNoTlv(0) indicates that no Reply Egress TLV was returned in the LTM.
.1.3.111.2.802.1.1.8.1.7.2.1.18,IEEE8021-CFM-MIB::dot1agCfmLtrEgressMac,OCTET,read-only,,current,,MAC address returned in the egress MAC address field. If the dot1agCfmLtrEgress object contains the value egrNoTlv(0), then the contents of this object are meaningless.
.1.3.111.2.802.1.1.8.1.7.2.1.19,IEEE8021-CFM-MIB::dot1agCfmLtrEgressPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),Format of the egress Port ID. If the dot1agCfmLtrEgress object contains the value egrNoTlv(0), then the contents of this object are meaningless.
.1.3.111.2.802.1.1.8.1.7.2.1.20,IEEE8021-CFM-MIB::dot1agCfmLtrEgressPortId,OCTET,read-only,,current,,Egress Port ID. The format of this object is determined by the value of the dot1agCfmLtrEgressPortIdSubtype object. If the dot1agCfmLtrEgress object contains the value egrNoTlv(0), then the contents of this object are meaningless.
.1.3.111.2.802.1.1.8.1.7.2.1.21,IEEE8021-CFM-MIB::dot1agCfmLtrOrganizationSpecificTlv,OCTET,read-only,,current,,All Organization specific TLVs returned in the LTR, if any. Includes all octets including and following the TLV Length field of each TLV, concatenated together.
.1.3.111.2.802.1.1.8.1.7.3,IEEE8021-CFM-MIB::dot1agCfmMepDbTable,,not-accessible,,current,,The MEP Database. A database, maintained by every MEP, that maintains received information about other MEPs in the Maintenance Domain. The SMI does not allow to state in a MIB that an object in a table is an array. The solution is to take the index (or indices) of the first table and add one or more indices. 
.1.3.111.2.802.1.1.8.1.7.3.1,IEEE8021-CFM-MIB::dot1agCfmMepDbEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepIdentifier:dot1agCfmMepDbRMepIdentifier,current,,The MEP Database table entry.
.1.3.111.2.802.1.1.8.1.7.3.1.1,IEEE8021-CFM-MIB::dot1agCfmMepDbRMepIdentifier,Unsigned32,not-accessible,,current,,Maintenance association Endpoint Identifier of a remote MEP whose information from the MEP Database is to be returned. 
.1.3.111.2.802.1.1.8.1.7.3.1.2,IEEE8021-CFM-MIB::dot1agCfmMepDbRMepState,INTEGER,read-only,,current,rMepIdle(1):rMepStart(2):rMepFailed(3):rMepOk(4),The operational state of the remote MEP IFF State machines.
.1.3.111.2.802.1.1.8.1.7.3.1.3,IEEE8021-CFM-MIB::dot1agCfmMepDbRMepFailedOkTime,TimeTicks,read-only,,current,,The time (SysUpTime) at which the IFF Remote MEP state machine last entered either the RMEP_FAILED or RMEP_OK state. 
.1.3.111.2.802.1.1.8.1.7.3.1.4,IEEE8021-CFM-MIB::dot1agCfmMepDbMacAddress,OCTET,read-only,,current,,The MAC address of the remote MEP.
.1.3.111.2.802.1.1.8.1.7.3.1.5,IEEE8021-CFM-MIB::dot1agCfmMepDbRdi,INTEGER,read-only,,current,true(1):false(2),State of the RDI bit in the last received CCM (true for RDI=1), or false if none has been received. 
.1.3.111.2.802.1.1.8.1.7.3.1.6,IEEE8021-CFM-MIB::dot1agCfmMepDbPortStatusTlv,INTEGER,read-only,,current,psNoPortStateTLV(0):psBlocked(1):psUp(2),An enumerated value of the Port status TLV received in the last CCM from the remote MEP or the default value psNoPortStateTLV indicating either no CCM has been received, or that nor port status TLV was received in the last CCM. 
.1.3.111.2.802.1.1.8.1.7.3.1.7,IEEE8021-CFM-MIB::dot1agCfmMepDbInterfaceStatusTlv,INTEGER,read-only,,current,isNoInterfaceStatusTLV(0):isUp(1):isDown(2):isTesting(3):isUnknown(4):isDormant(5):isNotPresent(6):isLowerLayerDown(7),An enumerated value of the Interface status TLV received in the last CCM from the remote MEP or the default value isNoInterfaceStatus TLV indicating either no CCM has been received, or that no interface status TLV was received in the last CCM. 
.1.3.111.2.802.1.1.8.1.7.3.1.8,IEEE8021-CFM-MIB::dot1agCfmMepDbChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),This object specifies the format of the Chassis ID received in the last CCM.
.1.3.111.2.802.1.1.8.1.7.3.1.9,IEEE8021-CFM-MIB::dot1agCfmMepDbChassisId,OCTET,read-only,,current,,The Chassis ID. The format of this object is determined by the value of the dot1agCfmLtrChassisIdSubtype object. 
.1.3.111.2.802.1.1.8.1.7.3.1.10,IEEE8021-CFM-MIB::dot1agCfmMepDbManAddressDomain,OBJECT,read-only,,current,,The TDomain that identifies the type and format of the related dot1agCfmMepDbManAddress object, used to access the SNMP agent of the system transmitting the CCM. Received in the CCM Sender ID TLV from that system. Typical values will be one of (not all inclusive) list: snmpUDPDomain (from SNMPv2-TM, RFC3417) snmpIeee802Domain (from SNMP-IEEE802-TM-MIB, RFC4789) The value 'zeroDotZero' (from RFC2578) indicates 'no management address was present in the LTR', in which case the related object dot1agCfmMepDbManAddress MUST have a zero-length OCTET STRING as a value. 
.1.3.111.2.802.1.1.8.1.7.3.1.11,IEEE8021-CFM-MIB::dot1agCfmMepDbManAddress,OCTET,read-only,,current,,The TAddress that can be used to access the SNMP agent of the system transmitting the CCM, received in the CCM Sender ID TLV from that system. If the related object dot1agCfmMepDbManAddressDomain contains the value 'zeroDotZero', this object dot1agCfmMepDbManAddress MUST have a zero-length OCTET STRING as a value. 
.1.3.111.2.802.1.1.8.1.7.3.1.12,IEEE8021-CFM-MIB::dot1agCfmMepDbRMepIsActive,INTEGER,read-write,,current,true(1):false(2),A Boolean value stating if the remote MEP is active.
.1.3.111.2.802.1.1.8.2,IEEE8021-CFM-MIB::dot1agCfmConformance,,,,,,
.1.3.111.2.802.1.1.8.2.1,IEEE8021-CFM-MIB::dot1agCfmCompliances,,,,,,
.1.3.111.2.802.1.1.8.2.1.1,IEEE8021-CFM-MIB::dot1agCfmCompliance,,,,,,The compliance statement for support of the CFM MIB module.
.1.3.111.2.802.1.1.8.2.1.2,IEEE8021-CFM-V2-MIB::ieee8021CfmComplianceV2,,,,,,The compliance statement for support of the CFM MIB module.
.1.3.111.2.802.1.1.8.2.1.3,IEEE8021-CFM-V2-MIB::dot1agCfmWithPbbTeCompliance,,,,,,The compliance statement for support of the CFM MIB for systems that support PBB-TE.
.1.3.111.2.802.1.1.8.2.2,IEEE8021-CFM-MIB::dot1agCfmGroups,,,,,,
.1.3.111.2.802.1.1.8.2.2.1,IEEE8021-CFM-MIB::dot1agCfmStackGroup,,,,,,Objects for the Stack group.
.1.3.111.2.802.1.1.8.2.2.2,IEEE8021-CFM-MIB::dot1agCfmDefaultMdGroup,,,,,,Objects for the Default MD Level group.
.1.3.111.2.802.1.1.8.2.2.3,IEEE8021-CFM-MIB::dot1agCfmVlanIdGroup,,,,,,Objects for the VLAN ID group.
.1.3.111.2.802.1.1.8.2.2.4,IEEE8021-CFM-MIB::dot1agCfmConfigErrorListGroup,,,,,,Objects for the CFM Configuration Error List Group.
.1.3.111.2.802.1.1.8.2.2.5,IEEE8021-CFM-MIB::dot1agCfmMdGroup,,,,,,Objects for the Maintenance Domain Group.
.1.3.111.2.802.1.1.8.2.2.6,IEEE8021-CFM-MIB::dot1agCfmMaGroup,,,,,,Objects for the MA group.
.1.3.111.2.802.1.1.8.2.2.7,IEEE8021-CFM-MIB::dot1agCfmMepGroup,,,,,,Objects for the MEP group.
.1.3.111.2.802.1.1.8.2.2.8,IEEE8021-CFM-MIB::dot1agCfmMepDbGroup,,,,,,Objects for the MEP group.
.1.3.111.2.802.1.1.8.2.2.9,IEEE8021-CFM-MIB::dot1agCfmNotificationsGroup,,,,,,Objects for the Notifications group.
.1.3.111.2.802.1.1.8.2.2.10,IEEE8021-CFM-MIB::ieee8021CfmMaNetGroup,,,,,,Objects for the MA Net group.
.1.3.111.2.802.1.1.8.2.2.11,IEEE8021-CFM-MIB::ieee8021CfmDefaultMdDefGroup,,,,,,Objects for the Default MD default Level group.
.1.3.111.2.802.1.1.8.2.2.12,IEEE8021-CFM-MIB::ieee8021CfmPbbTeExtensionGroup,,,,,,Objects needed for systems that support PBB-TE CFM functionality.
.1.3.111.2.802.1.1.8.2.2.13,IEEE8021-CFM-MIB::ieee8021CfmPbbTeTrafficBitGroup,,,,,,Objects needed for PBB-TE supporting systems that support the optional traffic bit.
.1.3.111.2.802.1.1.8.2.2.14,IEEE8021-CFM-V2-MIB::ieee8021CfmDefaultMdGroup,,,,,,Objects for the Default MD Level group.
.1.3.111.2.802.1.1.8.2.2.15,IEEE8021-CFM-V2-MIB::ieee8021CfmVlanIdGroup,,,,,,Objects for the VLAN ID group.
.1.3.111.2.802.1.1.8.2.2.16,IEEE8021-CFM-V2-MIB::ieee8021CfmConfigErrorListGroup,,,,,,Objects for the CFM Configuration Error List Group.
.1.3.111.2.802.1.1.9,IEEE8021-PBB-MIB::ieee8021PbbMib,,,,,,The Provider Backbone Bridge (PBB) MIB module for managing devices that support PBB. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.9.0,IEEE8021-PBB-MIB::ieee8021PbbNotifications,,,,,,
.1.3.111.2.802.1.1.9.1,IEEE8021-PBB-MIB::ieee8021PbbObjects,,,,,,
.1.3.111.2.802.1.1.9.1.1,IEEE8021-PBB-MIB::ieee8021PbbProviderBackboneBridge,,,,,,
.1.3.111.2.802.1.1.9.1.1.1,IEEE8021-PBB-MIB::ieee8021PbbBackboneEdgeBridgeObjects,,,,,,
.1.3.111.2.802.1.1.9.1.1.1.1,IEEE8021-PBB-MIB::ieee8021PbbBackboneEdgeBridgeAddress,OCTET,read-only,,current,,The MAC Address used by the BEB when it must be refered to in a unique fashion.
.1.3.111.2.802.1.1.9.1.1.1.2,IEEE8021-PBB-MIB::ieee8021PbbBackboneEdgeBridgeName,OCTET,read-write,,current,,A text string of locally determined significance. This value must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.1.3,IEEE8021-PBB-MIB::ieee8021PbbNumberOfIComponents,Unsigned32,read-only,,current,,The number of I-components in this BEB.
.1.3.111.2.802.1.1.9.1.1.1.4,IEEE8021-PBB-MIB::ieee8021PbbNumberOfBComponents,Unsigned32,read-only,,current,,The number of B-components in this BEB.
.1.3.111.2.802.1.1.9.1.1.1.5,IEEE8021-PBB-MIB::ieee8021PbbNumberOfBebPorts,Unsigned32,read-only,,current,,The number of CNPs, PIPs, CBPs, and PNPs in this BEB.
.1.3.111.2.802.1.1.9.1.1.1.6,IEEE8021-PBB-MIB::ieee8021PbbNextAvailablePipIfIndex,Integer32,read-only,,current,,This object provides an available ifIndex value that can be used for creation of a PIP.
.1.3.111.2.802.1.1.9.1.1.1.7,IEEE8021-MIRP-MIB::ieee8021PbbMirpEnableStatus,INTEGER,read-write,,current,true(1):false(2),The administrative status requested by management for MIRP. The value true(1) indicates that MIRP should be enabled on this component, on all ports for which it has not been specifically disabled. When false(2), MIRP is disabled on all ports. This object affects all MIRP Applicant and Registrar state machines. A transition from false(2) to true(1) will cause a reset of all MIRP state machines on all ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.1.8,IEEE8021-MIRP-MIB::ieee8021PbbMirpBvid,Integer32,read-write,,current,,The B-VID to which received MIRPDUs are to be assigned, or 0, if they are to be sent on the CBP PVID.
.1.3.111.2.802.1.1.9.1.1.1.9,IEEE8021-MIRP-MIB::ieee8021PbbMirpDestSelector,INTEGER,read-write,,current,cbpMirpGroup(1):cbpMirpVlan(2):cbpMirpTable(3),An enumerated value specifying what destination_address and vlan_identifier are to be used when the MIRP Participant transmits an MIRPDU towards the MAC relay entity: cbpMirpGroup (1) Use the Nearest Customer Bridge group address from Table 8-1 with the MIRP B-VID. cbpMirpVlan (2) Use the Nearest Customer Bridge group address from Table 8-1 with the Backbone VLAN Identifier field from the Backbone Service Instance table. cbpMirpTable (3) Use the Default Backbone Destination and Backbone VLAN Identifier fields from the Backbone Service Instance table. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.1.10,IEEE8021-MIRP-MIB::ieee8021PbbMirpPnpEnable,INTEGER,read-write,,current,true(1):false(2),A Boolean value specifying the administrative status requested by management for attaching a MIRP Participant to a PNP if and only if this system is a Backbone Edge Bridge (BEB): true(1) The BEB is to attach a MIRP Participant to exactly one Port, either a management Port with no LAN connection external to the BEB, or a PNP. false(2) No MIRP Participant is to be present on any PNP (or on the MAC Relay-facing side of a CBP). The value of this object MUST be retained across reinitializations of the management system. 
.1.3.111.2.802.1.1.9.1.1.1.11,IEEE8021-MIRP-MIB::ieee8021PbbMirpPnpPortNumber,Unsigned32,read-only,,current,,The Bridge Port Number of the Provider Network Port (PNP) that has an associated MIRP Participant, or 0, if no Bridge Port has an associated MIRP Participant. This object indexes an entry in the Bridge Port Table. The system SHALL ensure that either ieee8021PbbMirpPnpPortNumber contains 0, or that the indexed ieee8021BridgeBasePortType object contains the value providerNetworkPort(3).
.1.3.111.2.802.1.1.9.1.1.2,IEEE8021-PBB-MIB::ieee8021PbbVipTable,,not-accessible,,current,,This table lists the additional PBB parameters for each VIP. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.2.1,IEEE8021-PBB-MIB::ieee8021PbbVipEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,Each entry consists of the name string, I-SID, Default Destination MAC, Service Type, and possible B-MAC.
.1.3.111.2.802.1.1.9.1.1.2.1.1,IEEE8021-PBB-MIB::ieee8021PbbVipPipIfIndex,Integer32,read-only,,current,,Identifies the PIP associated with this VIP within the BEB. A value of zero indicates the VIP is not currently associated with any PIP. The value of this object must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.2.1.2,IEEE8021-PBB-MIB::ieee8021PbbVipISid,Unsigned32,read-create,,current,,The I-SID for this VIP. Within an I-Component, an VIP can only be serviced by one I-SID. And the ISID is a configurable parameter of the VIP. The value of this object must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.2.1.3,IEEE8021-PBB-MIB::ieee8021PbbVipDefaultDstBMAC,OCTET,read-only,,current,,The Default Destination B-MAC for this VIP.
.1.3.111.2.802.1.1.9.1.1.2.1.4,IEEE8021-PBB-MIB::ieee8021PbbVipType,BITS,read-create,,deprecated,ingress(0):egress(1),This feature is used to support asymmetic VLANs. The value of this object must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.2.1.5,IEEE8021-PBB-MIB::ieee8021PbbVipRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This indicates the status of an entry in this table, and is used to create/delete entries. It is an implementation specific decision as to whether any column in this table may be set while the corresponding instance of this object is valid(1). The value of this object must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.2.1.6,IEEE8021-PBB-MIB::ieee8021PbbVipEnableConnectionId,INTEGER,read-write,,current,true(1):false(2),This indicates if the connection_identifier parameter is allowed to learn associations between a backbone MAC address and a customer MAC address. The default value is true, indicating that such learning is allowed. This parameter should be configured to false at the root node of a Point-to-multipoint TE service instance.
.1.3.111.2.802.1.1.9.1.1.3,IEEE8021-PBB-MIB::ieee8021PbbISidToVipTable,,not-accessible,,current,,This table contains a cross-reference of I-SID values to the VIPs with which they are associated. This allows VIPs to be located easily by their associated I-SID.
.1.3.111.2.802.1.1.9.1.1.3.1,IEEE8021-PBB-MIB::ieee8021PbbISidToVipEntry,,not-accessible,ieee8021PbbISidToVipISid,current,,A mapping from an I-SID to the VIP whith which it is associated. An entry will exist for each entry in the ieee8021PbbVipTable.
.1.3.111.2.802.1.1.9.1.1.3.1.1,IEEE8021-PBB-MIB::ieee8021PbbISidToVipISid,Unsigned32,not-accessible,,current,,The I-SID of a VIP.
.1.3.111.2.802.1.1.9.1.1.3.1.2,IEEE8021-PBB-MIB::ieee8021PbbISidToVipComponentId,Unsigned32,read-only,,current,,The component identifier of the VIP to which this I-SID is associated.
.1.3.111.2.802.1.1.9.1.1.3.1.3,IEEE8021-PBB-MIB::ieee8021PbbISidToVipPort,Unsigned32,read-only,,current,,The port number of the VIP to which this I-SID is associated.
.1.3.111.2.802.1.1.9.1.1.4,IEEE8021-PBB-MIB::ieee8021PbbPipTable,,not-accessible,,current,,This table contains the parameters for each PIP, and can be used to configure the PIP port names. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.4.1,IEEE8021-PBB-MIB::ieee8021PbbPipEntry,,not-accessible,ieee8021PbbPipIfIndex,current,,The parameters for a PIP. 
.1.3.111.2.802.1.1.9.1.1.4.1.1,IEEE8021-PBB-MIB::ieee8021PbbPipIfIndex,Integer32,not-accessible,,current,,The number identifying the PIP.
.1.3.111.2.802.1.1.9.1.1.4.1.2,IEEE8021-PBB-MIB::ieee8021PbbPipBMACAddress,OCTET,read-create,,current,,The B-MAC used by this PIP for the B-SA.
.1.3.111.2.802.1.1.9.1.1.4.1.3,IEEE8021-PBB-MIB::ieee8021PbbPipName,OCTET,read-create,,current,,A text string of local significance which identifies the PIP within a BEB.
.1.3.111.2.802.1.1.9.1.1.4.1.4,IEEE8021-PBB-MIB::ieee8021PbbPipIComponentId,Unsigned32,read-only,,current,,Identifies the I-component associated with this PIP.
.1.3.111.2.802.1.1.9.1.1.4.1.5,IEEE8021-PBB-MIB::ieee8021PbbPipVipMap,OCTET,read-create,,current,,This object contains a bitmap indicating all the VIPs in the range 1 through 4094 that are associated with this PIP. The bits correspond to Bridge Port numbers in the range 1 through 4094. The high-order bit of the first octet corresponds to port number 1, and subsequent bits of the octet string correspond to subsequent port numbers. The following formula can be used to find the bit corresponding to a particular port number B: octet[(B-1)/8] & (1 >> ((B-1)%8)) If the bit for a particular port number is 1, that VIP is associated with this PIP. The value of this object may be truncated to remove trailing octets of all zeros.
.1.3.111.2.802.1.1.9.1.1.4.1.6,IEEE8021-PBB-MIB::ieee8021PbbPipVipMap1,OCTET,read-create,,current,,This object contains a bitmap indicating all the VIPs in the range 4095 through 20478 that are associated with this PIP. The bits correspond to Bridge Port numbers in the range 4095 through 20478. The high-order bit of the first octet corresponds to port number 1, and subsequent bits of the octet string correspond to subsequent port numbers. The following formula can be used to find the bit corresponding to a particular port number B: octet[(B-4095)/8] & (1 >> ((B-4095)%8)) If the bit for a particular port number is 1, that VIP is associated with this PIP. Note that ports numbers greater than 4094 cannot be used with xSTP. The value of this object may be truncated to remove trailing octets of all zeros.
.1.3.111.2.802.1.1.9.1.1.4.1.7,IEEE8021-PBB-MIB::ieee8021PbbPipVipMap2,OCTET,read-create,,current,,This object contains a bitmap indicating all the VIPs in the range 20479 through 36861 that are associated with this PIP. The bits correspond to Bridge Port numbers in the range 20479 through 36861. The high-order bit of the first octet corresponds to port number 1, and subsequent bits of the octet string correspond to subsequent port numbers. The following formula can be used to find the bit corresponding to a particular port number B: octet[(B-20479)/8] & (1 >> ((B-20479)%8)) If the bit for a particular port number is 1, that VIP is associated with this PIP. Note that ports numbers greater than 4094 cannot be used with xSTP. The value of this object may be truncated to remove trailing octets of all zeros.
.1.3.111.2.802.1.1.9.1.1.4.1.8,IEEE8021-PBB-MIB::ieee8021PbbPipVipMap3,OCTET,read-create,,current,,This object contains a bitmap indicating all the VIPs in the range 36862 through 53245 that are associated with this PIP. The bits correspond to Bridge Port numbers in the range 36862 through 53245. The high-order bit of the first octet corresponds to port number 1, and subsequent bits of the octet string correspond to subsequent port numbers. The following formula can be used to find the bit corresponding to a particular port number B: octet[(B-36862)/8] & (1 >> ((B-36862)%8)) If the bit for a particular port number is 1, that VIP is associated with this PIP. Note that ports numbers greater than 4094 cannot be used with xSTP. The value of this object may be truncated to remove trailing octets of all zeros.
.1.3.111.2.802.1.1.9.1.1.4.1.9,IEEE8021-PBB-MIB::ieee8021PbbPipVipMap4,OCTET,read-create,,current,,This object contains a bitmap indicating all the VIPs in the range 53246 through 65535 that are associated with this PIP. The bits correspond to Bridge Port numbers in the range 53246 through 65535. The high-order bit of the first octet corresponds to port number 1, and subsequent bits of the octet string correspond to subsequent port numbers. The following formula can be used to find the bit corresponding to a particular port number B: octet[(B-53246)/8] & (1 >> ((B-53246)%8)) If the bit for a particular port number is 1, that VIP is associated with this PIP. Note that ports numbers greater than 4094 cannot be used with xSTP. The value of this object may be truncated to remove trailing octets of all zeros.
.1.3.111.2.802.1.1.9.1.1.4.1.10,IEEE8021-PBB-MIB::ieee8021PbbPipRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Indicates the status of an entry in this table, and is used to create/delete entries. The object ieee8021PbbPipBMACAddress must be set before this object can be made active(1). The value of ieee8021PbbPipBMACAddress cannot be modified while this object is active(1).
.1.3.111.2.802.1.1.9.1.1.5,IEEE8021-PBB-MIB::ieee8021PbbPipPriorityTable,,not-accessible,,current,,A table that contains information about every PIP that is associated with this PBB.
.1.3.111.2.802.1.1.9.1.1.5.1,IEEE8021-PBB-MIB::ieee8021PbbPipPriorityEntry,,not-accessible,,current,,A list of Default User Priorities for each PIP of a PBB. This is indexed by ieee8021PbbPipIfIndex.
.1.3.111.2.802.1.1.9.1.1.5.1.1,IEEE8021-PBB-MIB::ieee8021PbbPipPriorityCodePointSelection,INTEGER,read-write,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4), This object identifies the rows in the PCP encoding and decoding tables that are used to remark frames on this PIP if this remarking is enabled.
.1.3.111.2.802.1.1.9.1.1.5.1.2,IEEE8021-PBB-MIB::ieee8021PbbPipUseDEI,INTEGER,read-write,,current,true(1):false(2),If the Use_DEI is set to true(1) for the PIP then the drop_eligible parameter is encoded in the DEI of transmitted frames, and the drop_eligible parameter shall be true(1) for a received frame if the DEI is set in the VLAN tag or the Priority Code Point Decoding Table indicates drop_eligible True for the received PCP value. If the Use_DEI parameter is false(2), the DEI shall be transmitted as zero and ignored on receipt. The default value of the Use_DEI parameter is false(2).
.1.3.111.2.802.1.1.9.1.1.5.1.3,IEEE8021-PBB-MIB::ieee8021PbbPipRequireDropEncoding,INTEGER,read-write,,current,true(1):false(2),If a Bridge supports encoding or decoding of drop_eligible from the PCP field of a VLAN tag (6.7.3) on any of its PIPs, then it shall implement a Boolean parameter Require Drop Encoding on each of its PIPs with default value false(2). If Require Drop Encoding is True and the PIP cannot encode particular priorities with drop_eligible, then frames queued with those priorities and drop_eligible true(1) shall be discarded and not transmitted.
.1.3.111.2.802.1.1.9.1.1.6,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingTable,,not-accessible,,current,,A table that contains information about Priority Code Point Decoding Table for a PIP of a provider Bridge. Alternative values for each table are specified as rows in Table 6-3 (6.9.3), with each alternative labeled by the number of distinct priorities that can be communicated, and the number of these for which drop precedence can be communicated. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.6.1,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingEntry,,not-accessible,ieee8021PbbPipIfIndex:ieee8021PbbPipDecodingPriorityCodePointRow:ieee8021PbbPipDecodingPriorityCodePoint,current,,A list of objects containing Priority Code Point Decoding information for a PIP of a provider Bridge.
.1.3.111.2.802.1.1.9.1.1.6.1.1,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingPriorityCodePointRow,INTEGER,not-accessible,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4),The specific row in Table 6-3 (6.9.3) indicating the PCP.
.1.3.111.2.802.1.1.9.1.1.6.1.2,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingPriorityCodePoint,Integer32,not-accessible,,current,,The specific PCP value in Table 6-3 (6.9.3).
.1.3.111.2.802.1.1.9.1.1.6.1.3,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingPriority,Unsigned32,read-write,,current,,The specific priority value in Table 6-3 (6.9.3).
.1.3.111.2.802.1.1.9.1.1.6.1.4,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingDropEligible,INTEGER,read-write,,current,true(1):false(2),The drop eligibility value in 12.6.2.8.
.1.3.111.2.802.1.1.9.1.1.7,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingTable,,not-accessible,,current,,A table that contains information about Priority Code Point Decoding Table for a PIP of a provider Bridge. Alternative values for each table are specified as rows in Table 6-3 (6.9.3), with each alternative labeled by the number of distinct priorities that can be communicated, and the number of these for which drop precedence can be communicated. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.7.1,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingEntry,,not-accessible,ieee8021PbbPipIfIndex:ieee8021PbbPipEncodingPriorityCodePointRow:ieee8021PbbPipEncodingPriorityCodePoint:ieee8021PbbPipEncodingDropEligible,current,,A list of objects containing Priority Code Point Encoding information for a PIP of a provider Bridge.
.1.3.111.2.802.1.1.9.1.1.7.1.1,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingPriorityCodePointRow,INTEGER,not-accessible,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4),The specific row in Table 6-3 (6.9.3)indicating the PCP row. (i.e., 8P0D, 7P1D, 6P2D, 5P3D)
.1.3.111.2.802.1.1.9.1.1.7.1.2,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingPriorityCodePoint,Integer32,not-accessible,,current,,The specific row in Table 6-3 (6.9.3) indicating the PCP. (i.e., 0,1,2,3,4,5,6,7).
.1.3.111.2.802.1.1.9.1.1.7.1.3,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingDropEligible,INTEGER,not-accessible,,current,true(1):false(2),The specific row in Table 6-3 (6.9.3) indicating the drop eligibility. A value of true(1) means eligible for drop.
.1.3.111.2.802.1.1.9.1.1.7.1.4,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingPriority,Unsigned32,read-write,,current,,The encoding priority in Table 6-3 (6.9.3).
.1.3.111.2.802.1.1.9.1.1.8,IEEE8021-PBB-MIB::ieee8021PbbVipToPipMappingTable,,not-accessible,,current,,This table lists VIPs and the PIP to which each is associated, and allows the PIP associated with each VIP to be configured. Entries in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.8.1,IEEE8021-PBB-MIB::ieee8021PbbVipToPipMappingEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,, The PIP is identified by the value of the ieee8021PbbVipToPipNumber. This value may be used to index the ieee8021PbbPipTable to set or retrieve the  PIP's configuration information
.1.3.111.2.802.1.1.9.1.1.8.1.1,IEEE8021-PBB-MIB::ieee8021PbbVipToPipMappingPipIfIndex,Integer32,read-create,,current,,The PIP's interface number.
.1.3.111.2.802.1.1.9.1.1.8.1.2,IEEE8021-PBB-MIB::ieee8021PbbVipToPipMappingStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),Indicates the storage type of this entry. An entry whose storage type is permanent(4) need not allow write access to other columns in that entry.
.1.3.111.2.802.1.1.9.1.1.8.1.3,IEEE8021-PBB-MIB::ieee8021PbbVipToPipMappingRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Indicates the status of an entry in this table, and is used to create/delete entries. The corresponding instance of ieee8021PbbVipToPipMappingPipIfIndex must be set before this object can be made active(1). The corresponding instance of ieee8021PbbVipToPipMappingPipIfIndex may not be changed while this object is active(1).
.1.3.111.2.802.1.1.9.1.1.9,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingTable,,not-accessible,,current,,The CBP table of I-SID values (6.11). The contents of this table are not persistent over power up restart/reboot.
.1.3.111.2.802.1.1.9.1.1.9.1,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021PbbCBPServiceMappingBackboneSid,current,,Each entry includes the B-VID to carry and optionally an I-SID for mapping I-SIDs normally used at a Peer E-NNI (6.11, 26.6.2). The table is indexed by the component ID  of the relevant B-Component of the PBB, the Bridge port number of the CBP on that Bcomponent, and the I-SID for  the service. 
.1.3.111.2.802.1.1.9.1.1.9.1.1,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingBackboneSid,Unsigned32,not-accessible,,current,,The I-SID which will be transmitted over the PBBN.
.1.3.111.2.802.1.1.9.1.1.9.1.2,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingBVid,Integer32,read-create,,current,,The B-VID which will carry this service instance.
.1.3.111.2.802.1.1.9.1.1.9.1.3,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingDefaultBackboneDest,OCTET,read-create,,current,,A default destination B-MAC for the CBP to use.
.1.3.111.2.802.1.1.9.1.1.9.1.4,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingType,BITS,read-create,,deprecated,ingress(0):egress(1),Used for Pt-MPt service where ingress or egress limiting is desired.
.1.3.111.2.802.1.1.9.1.1.9.1.5,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingLocalSid,Unsigned32,read-create,,current,,The I-SID value used in frames transmitted and received through this CustomerBackbonePort.
.1.3.111.2.802.1.1.9.1.1.9.1.6,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Indicates the status of an entry in this table, and is used to create/delete entries. The corresponding instances of the following objects must be set before this object can be made active(1): ieee8021PbbCBPServiceMappingBVid ieee8021PbbCBPServiceMappingDefaultBackboneDest ieee8021PbbCBPServiceMappingType The corresponding instances of the following objects may not be changed while this object is active(1): ieee8021PbbCBPServiceMappingBVid ieee8021PbbCBPServiceMappingDefaultBackboneDest ieee8021PbbCBPServiceMappingType ieee8021PbbCBPServiceMappingLocalSid
.1.3.111.2.802.1.1.9.1.1.10,IEEE8021-PBB-MIB::ieee8021PbbCbpTable,,not-accessible,,current,,This table is used to dynamically create/delete Customer Backbone Ports in a PBB. Entries in this table must be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.9.1.1.10.1,IEEE8021-PBB-MIB::ieee8021PbbCbpEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort,current,,An entry representing a dynamically created CBP in a PBB.
.1.3.111.2.802.1.1.9.1.1.10.1.1,IEEE8021-PBB-MIB::ieee8021PbbCbpRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object is used for creation/deletion of entries in this table.
.1.3.111.2.802.1.1.9.2,IEEE8021-PBB-MIB::ieee8021PbbConformance,,,,,,
.1.3.111.2.802.1.1.9.2.1,IEEE8021-PBB-MIB::ieee8021PbbGroups,,,,,,
.1.3.111.2.802.1.1.9.2.1.1,IEEE8021-PBB-MIB::ieee8021PbbBackboneEdgeBridgeGroup,,,,,,The collection of objects used to represent a Backbone Edge Bridge.
.1.3.111.2.802.1.1.9.2.1.2,IEEE8021-PBB-MIB::ieee8021PbbVipGroup,,,,,,The collection of objects used to represent a Virtual Instance Port (VIP).
.1.3.111.2.802.1.1.9.2.1.3,IEEE8021-PBB-MIB::ieee8021PbbPipGroup,,,,,,The collection of objects used to represent a Provider Instance Port (PIP).
.1.3.111.2.802.1.1.9.2.1.4,IEEE8021-PBB-MIB::ieee8021PbbDefaultPriorityGroup,,,,,,A collection of objects defining the priority applicable to each port for media that do not support native priority.
.1.3.111.2.802.1.1.9.2.1.5,IEEE8021-PBB-MIB::ieee8021PbbPipDecodingGroup,,,,,,A collection of objects providing statistics counters for decoding priority and drop eligibility for Bridge Ports.
.1.3.111.2.802.1.1.9.2.1.6,IEEE8021-PBB-MIB::ieee8021PbbPipEncodingGroup,,,,,,A collection of objects providing statistics counters for encoding priority and drop eligibility for Bridge Ports.
.1.3.111.2.802.1.1.9.2.1.7,IEEE8021-PBB-MIB::ieee8021PbbVipToPipMappingGroup,,,,,,The collection of objects used to represent the mapping of a VIP to a PIP.
.1.3.111.2.802.1.1.9.2.1.8,IEEE8021-PBB-MIB::ieee8021PbbCBPServiceMappingGroup,,,,,,The collection of objects used to represent a service instance.
.1.3.111.2.802.1.1.9.2.1.9,IEEE8021-PBB-MIB::ieee8021PbbDynamicCbpGroup,,,,,,The collection of objects used to dynamically create/delete CBPs in a PBB.
.1.3.111.2.802.1.1.9.2.1.10,IEEE8021-PBB-MIB::ieee8021PbbVipPbbTeGroup,,,,,,The collection of objects specific to PBB Bridges operating in a PBB-TE-aware manner.
.1.3.111.2.802.1.1.9.2.2,IEEE8021-PBB-MIB::ieee8021PbbCompliances,,,,,,
.1.3.111.2.802.1.1.9.2.2.1,IEEE8021-PBB-MIB::ieee8021PbbCompliance,,,,,,The compliance statement for devices supporting Provider Backbone Bridging as defined in IEEE Std 802.1ah.
.1.3.111.2.802.1.1.9.2.2.2,IEEE8021-PBB-MIB::ieee8021PbbWithPbbTeCompliance,,,,,,The compliance statement for devices supporting Provider Backbone Bridging with traffic engineering as defined in IEEE Std 802.1ah and IEEE Std 802.1Qay.
.1.3.111.2.802.1.1.10,IEEE8021-PBBTE-MIB::ieee8021PbbTeMib,,,,,,Copyright (C) IEEE (2018). All Rights Reserved This version of this MIB module is part of IEEE 802.1Q; See the standard itself for full legal notices. Unless otherwise indicated, the references in this MIB  module are to IEEE Std 802.1Q.
.1.3.111.2.802.1.1.10.0,IEEE8021-PBBTE-MIB::ieee8021PbbTeNotifications,,,,,,
.1.3.111.2.802.1.1.10.0.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupAdminFailure,,,,,,A protection group generates this notification whenever an adminisistrative command cannot be executed by the protection state machine. For example, a requested manual switch cannot be performed because of a signal failure condition. The management entity receiving the notification can identify the system from the network source address of the notification and can identify the protection group by the indices of the OID of the ieee8021PbbTeProtectionGroupConfigState variable in the notification:  ieee8021BridgeBaseComponentId - Identifies the component on the Bridge where the protection group is configured. ieee8021PbbTeProtectionGroupListGroupId - The id of the protection group. 
.1.3.111.2.802.1.1.10.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeObjects,,,,,,
.1.3.111.2.802.1.1.10.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListTable,,not-accessible,,current,,The PBB-TE Protection group list table. Each entry in this table corresponds to a configured PBB-TE Protection Group configured on the B-Component of an IB-BEB.
.1.3.111.2.802.1.1.10.1.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021PbbTeProtectionGroupListGroupId,current,,The PBB-TE protection group list table entry. Note that the component ID must refer to an B component
.1.3.111.2.802.1.1.10.1.1.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListGroupId,Unsigned32,not-accessible,,current,,The unique identifier for the protection group.
.1.3.111.2.802.1.1.10.1.1.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListMD,Unsigned32,read-create,,current,,This refers to the Maintenance Domain that qualifies the WorkingMA and ProtectionMA columns of this table. The MD index in this column must hold a value that matches the in the dot1agCfmStackMdIndex in the dot1agCfmStackTable for the corresponding WorkingMA and ProtectionMA columns of this table. This correspondence must hold for the RowStatus of this row to be set to Active. Furthermore, this column may not be modified while the RowStatus for this row is Active
.1.3.111.2.802.1.1.10.1.1.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListWorkingMA,Unsigned32,read-create,,current,,This refers to the Maintenance Association that refers to the PBB-TE MA that corresponds to the group's working entity. The MA index in this column must hold a value that is the value of dot1agCfmStackMaIndex column for some entry in the dot1agCfmStackTable before the RowStatus for this row can be set to Active. Furthermore, this column may not be modified when the RowStatus for this row is Active.
.1.3.111.2.802.1.1.10.1.1.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListProtectionMA,Unsigned32,read-create,,current,,This refers to the Maintenance Association that refers to the PBB-TE MA that corresponds to the group's protection entity. The MA index in this column must hold a value that is the value of dot1agCfmStackMaIndex column for some entry in the dot1agCfmStackTable before the RowStatus for this row can be set to Active. Furthermore, this column may not be modified when the RowStatus for this row is Active.
.1.3.111.2.802.1.1.10.1.1.1.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable if this column is set to permanent.
.1.3.111.2.802.1.1.10.1.1.1.6,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupListRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. The writable columns in a row cannot be changed if the row is active. The PbbTeProtectionGroupListWorkingMA, and PbbTeProtectionGroupListProtectionMA columns must be specified before the row can be activated.
.1.3.111.2.802.1.1.10.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeMASharedGroupTable,,not-accessible,,current,,This table contains references to all protection groups that share a working or protection entity with a given protection group.
.1.3.111.2.802.1.1.10.1.2.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeMASharedGroupEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021PbbTeProtectionGroupListGroupId:ieee8021PbbTeMASharedGroupSubIndex,current,,The ieee801PbbTeMASharedGroupEntry table. The table is indexed by protection group and by a simple integer. The table lists all protection groups that load share with that group.
.1.3.111.2.802.1.1.10.1.2.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeMASharedGroupSubIndex,Unsigned32,not-accessible,,current,,A simple integer to distinguish the members of the set of MAs that comprise the set of load sharing MAs for the specified protection group.
.1.3.111.2.802.1.1.10.1.2.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeMASharedGroupId,Unsigned32,read-only,,current,,This column holds the group id of a protection group that shares a working or protection group with the group whose index is the first index of this row.
.1.3.111.2.802.1.1.10.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiTable,,not-accessible,,current,,The PBB-TE TESI table contains information for each TE Service Instance known to a system.
.1.3.111.2.802.1.1.10.1.3.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiEntry,,not-accessible,ieee8021PbbTeTesiId,current,,The PBB-TE TESI entry. Each entry maps a TESI to  a component and CBP.
.1.3.111.2.802.1.1.10.1.3.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiId,Unsigned32,not-accessible,,current,,This is the unique identifier for a PBB-TE TE-SID.
.1.3.111.2.802.1.1.10.1.3.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiComponent,Unsigned32,read-create,,current,,This is the component upon which the Bridge Port of the TESI is located.
.1.3.111.2.802.1.1.10.1.3.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiBridgePort,Unsigned32,read-create,,current,,This is the Bridge Port of the TESI.
.1.3.111.2.802.1.1.10.1.3.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-crate columns must be writable for rows whose StorageType is permanaent.
.1.3.111.2.802.1.1.10.1.3.1.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated.
.1.3.111.2.802.1.1.10.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeTeSiEspTable,,not-accessible,,current,,The PBB-TE TE-SID table contains information for each TE service instance known to a system.
.1.3.111.2.802.1.1.10.1.4.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeTeSiEspEntry,,not-accessible,ieee8021PbbTeTesiId:ieee8021PbbTeTeSiEspEspIndex,current,,The PBB-TE TE-SID entry. Each entry refers to a TE Service Instance by identifier and contains information about one of the ESPs that comprise this TE Service Instance.
.1.3.111.2.802.1.1.10.1.4.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeTeSiEspEspIndex,Unsigned32,not-accessible,,current,,This is an identifier, of local signifigance to a particular PBB-TE TE-SID which is used to index all of the ESPs associated with the TE-SID.
.1.3.111.2.802.1.1.10.1.4.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeTeSiEspEsp,OCTET,read-create,,current,,This column holds the ESP identifier for one of the Ethernet Switched Paths that define the TE service instance.
.1.3.111.2.802.1.1.10.1.4.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeTeSiEspStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable for permanent rows.
.1.3.111.2.802.1.1.10.1.4.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeTeSiEspRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated.
.1.3.111.2.802.1.1.10.1.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigTable,,not-accessible,,current,,The PBB-TE Protection group config table contains configuration and status information for each configuration group configured in the system. Entries in this table are created implicitly by the creation of entries in the ieee8021PbbTeProtectionGroupListTable table.
.1.3.111.2.802.1.1.10.1.5.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021PbbTeProtectionGroupListGroupId,current,,The protection group confguration table entry. Rows are created in this table implicitly when a row is added to the ieee8021PbbTeProtectionGroupListTable.
.1.3.111.2.802.1.1.10.1.5.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigState,INTEGER,read-only,,current,workingPath(1):protectionPat(2):waitToRestore(3):protAdmin(4),This column indicates the current state of the protection switching state machine for a protection group.
.1.3.111.2.802.1.1.10.1.5.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigCommandStatus,INTEGER,read-only,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column indicates the status of administrative commands within the protection group. It reflects the current operational administrative command being acted upon by the protection group.
.1.3.111.2.802.1.1.10.1.5.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigCommandLast,INTEGER,read-only,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column indicates the last attempted administrative command applied to the protection group. It is changed whenever a write is made to the CommandAdmin column of this table and is a record of the last attempted administrative operation.
.1.3.111.2.802.1.1.10.1.5.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigCommandAdmin,INTEGER,read-create,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column is used by the operator to request that the protection group state machine perform some administrative operation. The operator requests a command by writing the command value to this column. The state machine indicates the command that it is performing by setting the value of the CommandStatus column of this table. This column always reads back as clear(1).
.1.3.111.2.802.1.1.10.1.5.1.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigActiveRequests,INTEGER,read-only,,current,noRequest(1):loP(2):fs(3):pSFH(4):wSFH(5):manualSwitchToProtection(6):manualSwitchToWorking(7),This column shows the status of active requests within the TE protection group.
.1.3.111.2.802.1.1.10.1.5.1.6,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigWTR,Unsigned32,read-create,,current,,This column is used to configure the wait-to-restore timer for the protection group operation. The timer may be configured in steps of 1 minute between 5 and 12 minutes, the default being 5. Additionally, the value 0 is used to indicate that the protection group is to operate non-revertively.
.1.3.111.2.802.1.1.10.1.5.1.7,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigHoldOff,Unsigned32,read-create,,current,,This column is used to configure the hold off timer. The purpose is to allow a service layer protection mechanism to have a chance to fix athe problem before switching at the client layer, or to allow an upstream protected domain to switch before a downsream domain. The hold off timer has a period of from 0 to 10 seconds, the default being 0, with a 100ms granularity.
.1.3.111.2.802.1.1.10.1.5.1.8,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigNotifyEnable,INTEGER,read-create,,current,true(1):false(2),This column is used to enable or disable transmission of ieee8021PbbTeProtectionGroupAdminFailure notifications. These notifications are generated whenever an administrative command cannot be performed  by the protection group.
.1.3.111.2.802.1.1.10.1.5.1.9,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. For permanent objects the  ieee8021PbbTeProtectionGroupConfigCommandAdmin column must be writable.
.1.3.111.2.802.1.1.10.1.6,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidTable,,not-accessible,,current,,This table contains entries for each I-SID that is transported over TE-SIDs that belong to protection groups. Each I-SID maps to a single protection group.
.1.3.111.2.802.1.1.10.1.6.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidEntry,,not-accessible,ieee8021PbbTeProtectionGroupISidIndex,current,,The ieee8021PbbTeProtectionGroupISidTable entry.
.1.3.111.2.802.1.1.10.1.6.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidIndex,Unsigned32,not-accessible,,current,,This is the I-Sid that is to be mapped to a protection group.
.1.3.111.2.802.1.1.10.1.6.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidComponentId,Unsigned32,read-create,,current,,This column qualifies the GroupId column to a particular component.
.1.3.111.2.802.1.1.10.1.6.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidGroupId,Unsigned32,read-create,,current,,This column contains the Id of the protection group used to transport the data belonging to the service identified by the I-SID value specified in the ISidIndex column of this table.
.1.3.111.2.802.1.1.10.1.6.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry.
.1.3.111.2.802.1.1.10.1.6.1.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column contains the status for this row. Once active none of the columns in the row may be modified. All columns must be specified when creating the row.
.1.3.111.2.802.1.1.10.1.7,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastTable,,not-accessible,,current,,A table containing forwarding information for each vlan specifying the set of ports to which forwarding of unicast addressed frames for which no more specific forwarding information applies. This is configured statically by management.
.1.3.111.2.802.1.1.10.1.7.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastEntry,,not-accessible,ieee8021QBridgeVlanCurrentComponentId:ieee8021PbbTeBridgeStaticForwardAnyUnicastVlanIndex,current,,Forwarding information for a VLAN, specifying the set of ports to which forwarding of unicast addressed frames for which no more specific forwarding information applies. The EgressPorts and ForbiddenPorts PortList objects, together, implement the PortMap control element listed in IEEE Std 802.1Q 8.8.1.c.
.1.3.111.2.802.1.1.10.1.7.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastVlanIndex,Unsigned32,not-accessible,,current,,The VLAN-ID or other identifier refering to the VLAN to which this static filtering entry applies.
.1.3.111.2.802.1.1.10.1.7.1.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastEgressPorts,OCTET,read-create,,current,,The complete set of ports to which a unicast addressed frame is to be forwarded. This value is persistent and will be restored upon system reboot. A port may not be added to this set if it is already a member of ieee8021PbbTeBridgeStaticForwardAnyUnicastForbiddenPorts. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitialization of the management system.
.1.3.111.2.802.1.1.10.1.7.1.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastForbiddenPorts,OCTET,read-create,,current,,The complete set of ports to which a unicast addressed frame is to be filtered. This value is persistent and will be restored upon system reboot. A port may not be added to this set if it is already a member of ieee8021PbbTeBridgeStaticForwardAnyUnicastEgress. The default value is a string of zeros of appropriate length. The value of this object MUST be retained across reinitialization of the management system.
.1.3.111.2.802.1.1.10.1.7.1.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. All read-create columns must be writable for permanent entries.
.1.3.111.2.802.1.1.10.1.7.1.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeBridgeStaticForwardAnyUnicastRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column contains the status for this row.
.1.3.111.2.802.1.1.10.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeConformance,,,,,,
.1.3.111.2.802.1.1.10.2.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeCompliances,,,,,,
.1.3.111.2.802.1.1.10.2.1.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeCompliance,,,,,,The compliance statement for support of the PBB-TE MIB module.
.1.3.111.2.802.1.1.10.2.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeGroups,,,,,,
.1.3.111.2.802.1.1.10.2.2.1,IEEE8021-PBBTE-MIB::ieee8021PbbTeGroupListGroup,,,,,,Objects for the GroupList group.
.1.3.111.2.802.1.1.10.2.2.2,IEEE8021-PBBTE-MIB::ieee8021PbbTeMASharedGroup,,,,,,Objects for the MA Load Sharing Table Group.
.1.3.111.2.802.1.1.10.2.2.3,IEEE8021-PBBTE-MIB::ieee8021PbbTeTesiGroup,,,,,,Objects for the TE SI group 
.1.3.111.2.802.1.1.10.2.2.4,IEEE8021-PBBTE-MIB::ieee8021PbbTeSiEspGroup,,,,,,Objects for the TESI ESP group.
.1.3.111.2.802.1.1.10.2.2.5,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionConfigManGroup,,,,,,Objects for the PbbTeConfiguration group.
.1.3.111.2.802.1.1.10.2.2.6,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionConfigOptGroup,,,,,,Objects for the PbbTeConfiguration group.
.1.3.111.2.802.1.1.10.2.2.7,IEEE8021-PBBTE-MIB::ieee8021PbbTeProtectionGroupISidGroup,,,,,,Objects for the ieee8021PbbTeProtectionGroupISidGroup group.
.1.3.111.2.802.1.1.10.2.2.8,IEEE8021-PBBTE-MIB::ieee8021PbbTeFdbGroup,,,,,,Fdb extension objects group
.1.3.111.2.802.1.1.10.2.2.9,IEEE8021-PBBTE-MIB::ieee8021PbbTeNotificationsGroup,,,,,,Objects for the notifications group.
.1.3.111.2.802.1.1.11,IEEE8021-DDCFM-MIB::ieee8021DdcfmMIB,,,,,,module for managing Data Dependent and Data Driven Connectivity Fault Management.  Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.11.1,IEEE8021-DDCFM-MIB::ieee8021MIBObjects,,,,,,
.1.3.111.2.802.1.1.11.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmStack,,,,,,
.1.3.111.2.802.1.1.11.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackTable,,not-accessible,,current,,The DDCFM Stack MIB object table. This table is for operator to  retrieve all the DDCFM entities defined on a specified interface.  This table is created by default.
.1.3.111.2.802.1.1.11.1.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackEntry,,not-accessible,ieee8021DdcfmStackIfIndex,current,,The DDCFM Stack Table. 
.1.3.111.2.802.1.1.11.1.1.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackIfIndex,Integer32,not-accessible,,current,,This object is the interface index of the interface either a Bridge Port, or an aggregated port within a Bridge Port. When the ifIndex value corresponds to the ifIndex of a Bridge Port, the value in this column must match the value in the ieee8021BridgeBasePortIfIndex column for the Bridge Port.
.1.3.111.2.802.1.1.11.1.1.1.1.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackRrMdLevel,Integer32,read-only,,current,,MD level of the Reflection Responder managed object.
.1.3.111.2.802.1.1.11.1.1.1.1.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackRrDirection,INTEGER,read-only,,current,down(1):up(2),The direction in which the RR faces.
.1.3.111.2.802.1.1.11.1.1.1.1.4,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackRFMreceiverMdLevel,Integer32,read-only,,current,,MD level of the RFM Receiver MO configured on the interface.
.1.3.111.2.802.1.1.11.1.1.1.1.5,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackDrMdLevel,Integer32,read-only,,current,,MD level of the Deflection Responder managed object.
.1.3.111.2.802.1.1.11.1.1.1.1.6,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackDrVlanIdOrNone,Integer32,read-only,,current,,The MA of the DR configured on the interface.
.1.3.111.2.802.1.1.11.1.1.1.1.7,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackSFMOriginatorMdLevel,Integer32,read-only,,current,,MD level of the SFM Originator MO configured on the interface.
.1.3.111.2.802.1.1.11.1.1.1.1.8,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackSFMOriginatorVlanIdOrNone,Integer32,read-only,,current,,The MA of the SFM Originator configured on the interface.
.1.3.111.2.802.1.1.11.1.1.1.1.9,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackSFMOriginatorDirection,INTEGER,read-only,,current,down(1):up(2),The direction of which the SFM Originator is facing.
.1.3.111.2.802.1.1.11.1.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmRr,,,,,,
.1.3.111.2.802.1.1.11.1.2.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrTable,,not-accessible,,current,,The Reflection Responder MIB object table. Each row in the table represents a different Reflection Responder.  All rows in this table persist across a system restart,  however after such a restart, the value of the  ActivationStatus column will be false.
.1.3.111.2.802.1.1.11.1.2.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrEntry,,not-accessible,ieee8021DdcfmRrIfIndex:ieee8021DdcfmRrMdIndex:ieee8021DdcfmRrDirection,current,,The Reflection Responder. Each entry associated with a Reflection Responder.
.1.3.111.2.802.1.1.11.1.2.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrIfIndex,Integer32,not-accessible,,current,,This object is the interface index of the interface either a Bridge Port, or an aggregated port within a Bridge Port, on which Reflection Responder is defined.  When the ifIndex value corresponds to the ifIndex of a Bridge Port, the value in this column must match the value in the ieee8021BridgeBasePortIfIndex column for the Bridge Port.
.1.3.111.2.802.1.1.11.1.2.1.1.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrMdIndex,Integer32,not-accessible,,current,,MD level of the Reflection Responder managed object.
.1.3.111.2.802.1.1.11.1.2.1.1.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrDirection,INTEGER,not-accessible,,current,down(1):up(2),The direction in which the RR faces.
.1.3.111.2.802.1.1.11.1.2.1.1.4,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrPrimaryVlanIdOrNone,Integer32,read-create,,current,,The VID to be used on RFM frames.
.1.3.111.2.802.1.1.11.1.2.1.1.5,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrFilter,OCTET,read-create,,current,,A pattern string specifies what data frames are selected to be reflected. Below are the primary Reflection Filters all Implementers should support. Multiple primary filters can be combined together by && (and), || (or), or !(negation). 1) All; 2) VID= vid; 3) I-SID = x; 4) DA = xx.xx.xx.xx.xx.xx; 5) SA = xx.xx.xx.xx.xx.xx; 6) EtherType =xx. For the reason that this management object allows a max size of 1500, messages carrying this object may be fragmented on some segments.
.1.3.111.2.802.1.1.11.1.2.1.1.6,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrSamplingInterval,Unsigned32,read-create,,current,,Indicates a time interval in which only the first frame matching the filter conditions is refected.
.1.3.111.2.802.1.1.11.1.2.1.1.7,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrTargetAddress,OCTET,read-create,,current,,The Reflection Target Address, which is a MAC address to which the reflected frames are targeted. Only individual address is allowed for the Reflection Target Address.  If not specified, the source_address of the selected data frame is used for Reflection Target Address.
.1.3.111.2.802.1.1.11.1.2.1.1.8,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrContinueFlag,INTEGER,read-create,,current,true(1):false(2),True indicates that the selected data frames are to be continued towards the DA specified in the frame header. False indicates that the selected data frames are terminated.
.1.3.111.2.802.1.1.11.1.2.1.1.9,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrDuration,Unsigned32,read-create,,current,,Duration of time in the unit of seconds or the number of frames to be reflected, for Reflection Responder to remain active after activation; Minimum 2 octets (65536 seconds) are needed for the duration of time;
.1.3.111.2.802.1.1.11.1.2.1.1.10,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrDurationInTimeFlag,INTEGER,read-create,,current,true(1):false(2),True indicates that duration is in seconds; False indicates that duration is by the total number of frames reflected.
.1.3.111.2.802.1.1.11.1.2.1.1.11,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrVlanPriority,Integer32,read-create,,current,,Priority, 3 bit value to be used in the VLAN tag, to be used in the transmitted encapsulated frames. The default value is the highest  priority.
.1.3.111.2.802.1.1.11.1.2.1.1.12,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrVlanDropEligible,INTEGER,read-create,,current,true(1):false(2),It indicates that drop_eligible bit value to be used in  the VLAN tag which to be used in the transmitted encapsulated frames is set as True or False accordingly.
.1.3.111.2.802.1.1.11.1.2.1.1.13,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrFloodingFlag,INTEGER,read-create,,current,true(1):false(2),True indicates that flooding is allowed if Egress port cannot be identified for RFM by the Filtering Database, False otherwise.
.1.3.111.2.802.1.1.11.1.2.1.1.14,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrTruncationFlag,INTEGER,read-create,,current,true(1):false(2),True indicates that the received data frame will be truncated to keep the contructed RFM size not exceeding the egress port's  Maximum Service Data Unit Size, False otherwise.
.1.3.111.2.802.1.1.11.1.2.1.1.15,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrActivationStatus,INTEGER,read-only,,current,true(1):false(2),True When receiving a request to activate a Reflection Responder, False When receiving a request to stop Reflection Responder or its timer expires.
.1.3.111.2.802.1.1.11.1.2.1.1.16,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrRemainDuration,Unsigned32,read-only,,current,,The value indicates the time, in the unit of seconds, or count left for Reflection Responder to be active.
.1.3.111.2.802.1.1.11.1.2.1.1.17,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrNextRfmTransID,Unsigned32,read-only,,current,,It indicates the value of RFM Transaction Identifier field of the next RFM transmitted. It is incremented by 1 with each transmission of RFM.
.1.3.111.2.802.1.1.11.1.2.1.1.18,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active.
.1.3.111.2.802.1.1.11.1.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmRFMReceiver,,,,,,
.1.3.111.2.802.1.1.11.1.3.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmRFMReceiverTable,,not-accessible,,current,,The RFM Receiver MIB object table. Each row in the table represents a different RFM Receiver. All rows associated with this table persist across system restart.
.1.3.111.2.802.1.1.11.1.3.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmRFMReceiverEntry,,not-accessible,ieee8021DdcfmRfmReceiverIfIndex:ieee8021DdcfmRfmReceiverMdIndex,current,,The DDCFM RFM Receiver. Each entry associated with a DDCFM RFM Receiver that reference to a MP.
.1.3.111.2.802.1.1.11.1.3.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmRfmReceiverIfIndex,Integer32,not-accessible,,current,,The interface index of the interface either a Bridge Port, or an aggregated port within a Bridge Port, on which the RFM Receiver is created. When the ifIndex value corresponds to the ifIndex of a Bridge Port, the value in this column must match the value in the ieee8021BridgeBasePortIfIndex column for the Bridge Port.
.1.3.111.2.802.1.1.11.1.3.1.1.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmRfmReceiverMdIndex,Integer32,not-accessible,,current,,MD level of the RFM Receiver managed object.
.1.3.111.2.802.1.1.11.1.3.1.1.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmRFMRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active.
.1.3.111.2.802.1.1.11.1.4,IEEE8021-DDCFM-MIB::ieee8021DdcfmDr,,,,,,
.1.3.111.2.802.1.1.11.1.4.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrTable,,not-accessible,,current,,The DDCFM Decapsulator Responder MIB object table. Each row in the table represents a different DDCFM Decapsulator Responder. All rows  in this table persist across a system restart; however after such a restart, the value of the ActivationStatus column will be false.
.1.3.111.2.802.1.1.11.1.4.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrEntry,,not-accessible,ieee8021DdcfmDrIfIndex:ieee8021DdcfmDrMdIndex:ieee8021DdcfmDrVlanIdOrNone,current,,The DDCFM Decapsulator Responder. Each entry associated with a DDCFM RFM Receiver which reference to a MP.
.1.3.111.2.802.1.1.11.1.4.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrIfIndex,Integer32,not-accessible,,current,,The interface index of the interface either a Bridge Port, or an aggregated port within a Bridge Port, on which the Decapsulator Responder is created. When the ifIndex value corresponds to the ifIndex of a Bridge Port, the value in this column must match the value in the ieee8021BridgeBasePortIfIndex column for the Bridge Port.
.1.3.111.2.802.1.1.11.1.4.1.1.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrMdIndex,Integer32,not-accessible,,current,,MD level of the Decapsulator Responder managed object.
.1.3.111.2.802.1.1.11.1.4.1.1.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrVlanIdOrNone,Integer32,not-accessible,,current,,An integer indicating the VID expected from the Send Frame Message frames.
.1.3.111.2.802.1.1.11.1.4.1.1.4,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrSfmOriginator,OCTET,read-create,,current,,MAC address reference to the corresponding Send Frame Message Originator.
.1.3.111.2.802.1.1.11.1.4.1.1.5,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrSourceAddressStayFlag,INTEGER,read-create,,current,true(1):false(2),True indicates that Decapsulator Responder does not replace the  source_address field of the decapsulated frame with the Decapsulator Responder's own MAC address, False otherwise.
.1.3.111.2.802.1.1.11.1.4.1.1.6,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrFloodingFlag,INTEGER,read-create,,current,true(1):false(2),True indicates that broadcast is allowed if Egress port cannot be identified by the Filtering Database, False otherwise.
.1.3.111.2.802.1.1.11.1.4.1.1.7,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrDuration,Unsigned32,read-create,,current,,The time that the Decapsulator Responder can stay active after its activation in the unit of seconds.
.1.3.111.2.802.1.1.11.1.4.1.1.8,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrActivationStatus,INTEGER,read-only,,current,true(1):false(2),True When receiving a request to activate a Decapsulator Responder, false When receiving a request to stop the Decapsulator Responder or its timer expires.
.1.3.111.2.802.1.1.11.1.4.1.1.9,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrRemainDuration,Unsigned32,read-only,,current,,The value indicates the time left for Decapsulator Responder keep active. Its granularity is in seconds.
.1.3.111.2.802.1.1.11.1.4.1.1.10,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrSFMsequenceErrors,Unsigned32,read-only,,current,,The value indicates the total number of out-of-sequence SFMs.
.1.3.111.2.802.1.1.11.1.4.1.1.11,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active.
.1.3.111.2.802.1.1.11.1.5,IEEE8021-DDCFM-MIB::ieee8021DdcfmSFMOriginator,,,,,,
.1.3.111.2.802.1.1.11.1.5.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoTable,,not-accessible,,current,,The DDCFM Send Frame Message Originator MIB object table. Each row in the table represents a different DDCFM Send Frame Message Originator. All rows in this table persist across a system restart; however after such a restart, the value of the ActivationStatus column will be false.
.1.3.111.2.802.1.1.11.1.5.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoEntry,,not-accessible,ieee8021DdcfmSfmIfIndex:ieee8021DdcfmSoMdIndex:ieee8021DdcfmSoVlanIdOrNone:ieee8021DdcfmSoDirection,current,,Each entry associated with a Send Frame Message Originator.
.1.3.111.2.802.1.1.11.1.5.1.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmSfmIfIndex,Integer32,not-accessible,,current,,The interface index of the interface either a Bridge port, or an aggregated port within a Bridge port, on which Send Frame Message Originator is created. When the ifIndex value corresponds to the ifIndex of a Bridge Port, the value in this column must match the value in the ieee8021BridgeBasePortIfIndex column for the Bridge Port.
.1.3.111.2.802.1.1.11.1.5.1.1.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoMdIndex,Integer32,not-accessible,,current,,MD level of the Send Frame Message Originator managed object.
.1.3.111.2.802.1.1.11.1.5.1.1.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoVlanIdOrNone,Integer32,not-accessible,,current,,An integer indicating the VID to be used on Send Frame Message frames.
.1.3.111.2.802.1.1.11.1.5.1.1.4,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoDirection,INTEGER,not-accessible,,current,down(1):up(2),The direction in which the SFM Originator faces.
.1.3.111.2.802.1.1.11.1.5.1.1.5,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoDrMacAddress,OCTET,read-create,,current,,MAC Address of the corresponding Decapsulator Responder.
.1.3.111.2.802.1.1.11.1.5.1.1.6,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoDuration,Unsigned32,read-create,,current,,Duration, in the unit of seconds, of Send Frame Message Originator  staying active once activated.
.1.3.111.2.802.1.1.11.1.5.1.1.7,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoActivationStatus,INTEGER,read-only,,current,true(1):false(2),True When receiving a request to activate a Send Frame Message Originator, false When receiving a request to stop the Send Frame Message Originator or its timer expires.
.1.3.111.2.802.1.1.11.1.5.1.1.8,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoRemainDuration,Unsigned32,read-only,,current,,The value indicates the time left for Send Frame Message Originator keep active. Its granularity is in seconds.
.1.3.111.2.802.1.1.11.1.5.1.1.9,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active.
.1.3.111.2.802.1.1.11.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmConformance,,,,,,
.1.3.111.2.802.1.1.11.2.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmCompliances,,,,,,
.1.3.111.2.802.1.1.11.2.1.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmCompliance,,,,,,The compliance statement for support of the DDCFM MIB module.
.1.3.111.2.802.1.1.11.2.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmGroups,,,,,,
.1.3.111.2.802.1.1.11.2.2.1,IEEE8021-DDCFM-MIB::ieee8021DdcfmStackGroup,,,,,,Objects for the DDCFM Stack group.
.1.3.111.2.802.1.1.11.2.2.2,IEEE8021-DDCFM-MIB::ieee8021DdcfmRrGroup,,,,,,Objects for the Reflection Responder group.
.1.3.111.2.802.1.1.11.2.2.3,IEEE8021-DDCFM-MIB::ieee8021DdcfmRFMReceiverGroup,,,,,,Objects for the RFM Receiver group.
.1.3.111.2.802.1.1.11.2.2.4,IEEE8021-DDCFM-MIB::ieee8021DdcfmDrGroup,,,,,,Objects for the Decapsulator Responder group.
.1.3.111.2.802.1.1.11.2.2.5,IEEE8021-DDCFM-MIB::ieee8021DdcfmSoGroup,,,,,,Objects for the Send Frame Message Originator group.
.1.3.111.2.802.1.1.12,LLDP-V2-TC-MIB::lldpV2TcMIB,,,,,,Textual conventions used throughout the IEEE Std 802.1AB version 2 and later MIB modules. Unless otherwise indicated, the references in this MIB module are to IEEE 802.1AB-2016. The TCs in this MIB are taken from the original LLDP-MIB, LLDP-EXT-DOT1-MIB, and LLDP-EXT-DOT3-MIB published in IEEE Std 802-1D-2004, with the addition of TCs to support the management address table. They have been made available as a separate TC MIB module to facilitate referencing from other MIB modules. Copyright (C) IEEE (2016). This version of this MIB module is published as 11.5.1 of IEEE Std 802.1AB-2016; see the standard itself for full legal notices.
.1.3.111.2.802.1.1.13,LLDP-V2-MIB::lldpV2MIB,,,,,,Management Information Base module for LLDP configuration, statistics, local system data and remote systems data components. This MIB module supports the architecture described in Clause 6, where multiple LLDP agents can be associated with a single Port, each supporting transmission by means of a different MAC address. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1AB-2016. Copyright (C) IEEE (2016). This version of this MIB module is published as 11.5.2 of IEEE Std 802.1AB-2016; see the standard itself for full legal notices.
.1.3.111.2.802.1.1.13.0,LLDP-V2-MIB::lldpV2Notifications,,,,,,
.1.3.111.2.802.1.1.13.0.0,LLDP-V2-MIB::lldpV2NotificationPrefix,,,,,,
.1.3.111.2.802.1.1.13.0.0.1,LLDP-V2-MIB::lldpV2RemTablesChange,,,,,,A lldpV2RemTablesChange notification is sent when the value of lldpV2StatsRemTablesLastChangeTime changes. It can be utilized by an NMS to trigger LLDP remote systems table maintenance polls. Note that transmission of lldpV2RemTablesChange notifications are throttled by the agent, as specified by the 'lldpV2NotificationInterval' object.
.1.3.111.2.802.1.1.13.1,LLDP-V2-MIB::lldpV2Objects,,,,,,
.1.3.111.2.802.1.1.13.1.1,LLDP-V2-MIB::lldpV2Configuration,,,,,,
.1.3.111.2.802.1.1.13.1.1.1,LLDP-V2-MIB::lldpV2MessageTxInterval,Unsigned32,read-write,,current,,The interval at which LLDP frames are transmitted on behalf of this LLDP agent. The default value for lldpV2MessageTxInterval object is 30 seconds. The value of this object is used as the initial value of the lldpV2PortMessageTxInterval object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.2,LLDP-V2-MIB::lldpV2MessageTxHoldMultiplier,Unsigned32,read-write,,current,,The time to live value expressed as a multiple of the lldpV2MessageTxInterval object. The actual time to live value used in LLDP frames, transmitted on behalf of this LLDP agent, can be expressed by the following formula: TTL = min(65535, (lldpV2MessageTxInterval*lldpV2MessageTxHoldMultiplier)+1) For example, if the value of lldpV2MessageTxInterval is '30', and the value of lldpV2MessageTxHoldMultiplier is '4', then the value '121' is encoded in the TTL field in the LLDP header. The default value for lldpV2MessageTxHoldMultiplier object is 4. The value of this object is used as the initial value of the lldpV2PortMessageTxHoldMultiplier object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.3,LLDP-V2-MIB::lldpV2ReinitDelay,Unsigned32,read-write,,current,,The lldpV2ReinitDelay indicates the delay (in units of seconds) from when lldpPortConfigAdminStatus object of a particular port becomes 'disabled' until re-initialization is attempted. The default value for lldpV2ReinitDelay is 2 s. The value of this object is used as the initial value of the lldpV2PortReinitDelay object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.4,LLDP-V2-MIB::lldpV2NotificationInterval,Unsigned32,read-write,,current,,This object controls the interval between transmission of LLDP notifications during normal transmission periods. The value of this object is used as the initial value of the lldpV2PortNotificationInterval object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.5,LLDP-V2-MIB::lldpV2TxCreditMax,Unsigned32,read-write,,current,,The maximum number of consecutive LLDPDUs that can be transmitted at any time. The default value for lldpV2TxCreditMax object is 5 PDUs. The value of this object is used as the initial value of the lldpV2PortTxCreditMax object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.6,LLDP-V2-MIB::lldpV2MessageFastTx,Unsigned32,read-write,,current,,The interval at which LLDP frames are transmitted on behalf of this LLDP agent during fast transmission period (e.g., when a new neighbor is detected). The default value for lldpV2MessageFastTx object is 1 second. The value of this object is used as the initial value of the lldpV2PortMessageFastTx object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.7,LLDP-V2-MIB::lldpV2TxFastInit,Unsigned32,read-write,,current,,The initial value used to initialize the txFast variable which determines the number of transmissions that are made in fast transmission mode. The default value for lldpV2TxFastInit object is 4. The value of this object is used as the initial value of the lldpV2PortTxFastInit object on row creation in the lldpV2PortConfigTableV2. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.8,LLDP-V2-MIB::lldpV2PortConfigTable,,not-accessible,,deprecated,,The table that controls LLDP frame transmission on individual ports that uses particular destination MAC addresses.
.1.3.111.2.802.1.1.13.1.1.8.1,LLDP-V2-MIB::lldpV2PortConfigEntry,,not-accessible,lldpV2PortConfigIfIndex:lldpV2PortConfigDestAddressIndex,deprecated,,LLDP configuration information for a particular port and destination MAC address. This configuration parameter controls the transmission and the reception of LLDP frames on those interface/address  combinations whose rows are created in this table. Rows in this table can only be created for MAC addresses that can validly be used in association with the type of  interface concerned, as defined by Table 7-2. The contents of this table is persistent across re-initializations or re-boots.
.1.3.111.2.802.1.1.13.1.1.8.1.1,LLDP-V2-MIB::lldpV2PortConfigIfIndex,Integer32,not-accessible,,deprecated,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB. The value of this object is used as an index to the lldpV2PortConfigTable.
.1.3.111.2.802.1.1.13.1.1.8.1.2,LLDP-V2-MIB::lldpV2PortConfigDestAddressIndex,Unsigned32,not-accessible,,deprecated,,The index value used to identify the destination MAC address associated with this entry. Its value identifies the row in the lldpV2DestAddressTable where the MAC address can be found. The value of this object is used as an index to the lldpV2PortConfigTable.
.1.3.111.2.802.1.1.13.1.1.8.1.3,LLDP-V2-MIB::lldpV2PortConfigAdminStatus,INTEGER,read-write,,deprecated,txOnly(1):rxOnly(2):txAndRx(3):disabled(4),The administratively desired status of the local LLDP agent. If the associated lldpV2PortConfigAdminStatus object is set to a value of 'txOnly(1)', then LLDP agent transmits LLDPframes on this port and it does not store any information about the remote systems connected.  If the associated lldpV2PortConfigAdminStatus object is  set to a value of 'rxOnly(2)', then the LLDP agent receives, but it does not transmit LLDP frames on this port. If the associated lldpV2PortConfigAdminStatus object is set to a value of 'txAndRx(3)', then the LLDP agent transmits and receives LLDP frames on this port. If the associated lldpV2PortConfigAdminStatus object is set to a value of 'disabled(4)', then LLDP agent does not transmit or receive LLDP frames on this port. If there is remote systems information that is received on this port and stored in other tables, before the port's lldpV2PortConfigAdminStatus becomes disabled, then that information is deleted.
.1.3.111.2.802.1.1.13.1.1.8.1.4,LLDP-V2-MIB::lldpV2PortConfigNotificationEnable,INTEGER,read-write,,deprecated,true(1):false(2),The lldpV2PortConfigNotificationEnable controls, on a per agent basis, whether or not notifications from the agent are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
.1.3.111.2.802.1.1.13.1.1.8.1.5,LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnable,BITS,read-write,,deprecated,portDesc(0):sysName(1):sysDesc(2):sysCap(3),The lldpV2PortConfigTLVsTxEnable, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. It should be noted that the organizationally-specific TLVs are excluded from the lldpV2PortConfigTLVsTxEnable bitmap.  LLDP Organization Specific Information Extension MIBs should have similar configuration objects to control transmission of their organizationally defined TLVs. The bit 'portDesc(0)' indicates that LLDP agent should transmit 'Port Description TLV'. The bit 'sysName(1)' indicates that LLDP agent should transmit 'System Name TLV'. The bit 'sysDesc(2)' indicates that LLDP agent should transmit 'System Description TLV'. The bit 'sysCap(3)' indicates that LLDP agent should transmit 'System Capabilities TLV'. There is no bit reserved for the management address TLV type since transmission of management address TLVs are controlled by another object, lldpV2ConfigManAddrTable. The default value for lldpV2PortConfigTLVsTxEnable object is empty set, which means no enumerated values are set. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.9,LLDP-V2-MIB::lldpV2DestAddressTable,,not-accessible,,current,,The table that contains the set of MAC addresses used by LLDP for transmission and reception of LLDPDUs.
.1.3.111.2.802.1.1.13.1.1.9.1,LLDP-V2-MIB::lldpV2DestAddressTableEntry,,not-accessible,lldpV2AddressTableIndex,current,,Destination MAC address information for LLDP. This configuration parameter identifies a MAC address corresponding to a LldpV2DestAddressTableIndex value. Rows in this table are created as necessary, to support MAC addresses needed by other tables in the MIB that are indexed by MAC address. A given row in this table cannot be deleted if the MAC address table index value is in use in any other table in the MIB. The contents of this table are persistent across re-initializations or re-boots.
.1.3.111.2.802.1.1.13.1.1.9.1.1,LLDP-V2-MIB::lldpV2AddressTableIndex,Unsigned32,not-accessible,,current,,The index value used to identify the destination MAC address associated with this entry. The value of this object is used as an index to the lldpV2DestAddressTable.
.1.3.111.2.802.1.1.13.1.1.9.1.2,LLDP-V2-MIB::lldpV2DestMacAddress,OCTET,read-only,,current,,The MAC address associated with this entry. The octet string identifies an individual or a group MAC address that is in use by LLDP as a destination MAC address. The MAC address is encoded in the octet string in canonical format (see IEEE Std 802).
.1.3.111.2.802.1.1.13.1.1.10,LLDP-V2-MIB::lldpV2ManAddrConfigTxPortsTable,,not-accessible,,current,,The table that controls selection of LLDP management address TLV instances to be transmitted on individual port/ destination address pairs.
.1.3.111.2.802.1.1.13.1.1.10.1,LLDP-V2-MIB::lldpV2ManAddrConfigTxPortsEntry,,not-accessible,lldpV2ManAddrConfigIfIndex:lldpV2ManAddrConfigDestAddressIndex:lldpV2ManAddrConfigLocManAddrSubtype:lldpV2ManAddrConfigLocManAddr,current,,LLDP configuration information that specifies the set of port/destination address pairs on which the local system management address instance is transmitted. Each active lldpManAddrConfigTxPortsTableV2Entry is  restored from non-volatile storage and re-created  after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.10.1.1,LLDP-V2-MIB::lldpV2ManAddrConfigIfIndex,Integer32,not-accessible,,current,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB. The value of this object is used as an index to the lldpV2PortConfigTable. The value in this column of the table MUST match the IfIndex value specified in the BridgePort table.
.1.3.111.2.802.1.1.13.1.1.10.1.2,LLDP-V2-MIB::lldpV2ManAddrConfigDestAddressIndex,Unsigned32,not-accessible,,current,,The index value used to identify the destination MAC address associated with this entry. Its value identifies the row in the lldpV2DestAddressTable where the MAC address can be found. The value of this object is used as an index to the lldpV2PortConfigTable.
.1.3.111.2.802.1.1.13.1.1.10.1.3,LLDP-V2-MIB::lldpV2ManAddrConfigLocManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpLocManagmentAddr' object. It should be noted that only a subset of the possible address encodings enumerated in AddressFamilyNumbers are appropriate for use as a LLDP management address, either because some are just not applicable or  because the maximum size of a LldpV2ManAddress octet string would prevent the use of some address identifier encodings.
.1.3.111.2.802.1.1.13.1.1.10.1.4,LLDP-V2-MIB::lldpV2ManAddrConfigLocManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the local system. The purpose of this address is to contact the management entity.
.1.3.111.2.802.1.1.13.1.1.10.1.5,LLDP-V2-MIB::lldpV2ManAddrConfigTxEnable,INTEGER,read-create,,current,true(1):false(2),A Boolean controlling the transmission of system management address instance for the specified port, destination, subtype, and MAN address used to index this table. If set to the default value of false, no transmission occurs. If set to true, the appropriate information is transmitted out of the port specified in the row's index.
.1.3.111.2.802.1.1.13.1.1.10.1.6,LLDP-V2-MIB::lldpV2ManAddrConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Indicates the status of an entry in this table, and is used to create/delete entries. The corresponding instances of the following objects must be set before this object can be made active(1): lldpV2ManAddrConfigDestAddressIndex lldpV2ManAddrConfigLocManAddrSubtype lldpV2ManAddrConfigLocManAddr  lldpV2ManAddrConfigTxEnable The corresponding instances of the following objects may not be changed while this object is active(1): lldpV2ManAddrConfigDestAddressIndex lldpV2ManAddrConfigLocManAddrSubtype lldpV2ManAddrConfigLocManAddr 
.1.3.111.2.802.1.1.13.1.1.11,LLDP-V2-MIB::lldpV2PortConfigTableV2,,not-accessible,,current,,The table that controls LLDP frame transmission on individual ports and using particular destination MAC addresses.
.1.3.111.2.802.1.1.13.1.1.11.1,LLDP-V2-MIB::lldpV2PortConfigEntryV2,,not-accessible,lldpV2PortConfigIfIndexV2:lldpV2PortConfigDestAddressIndexV2,current,,LLDP configuration information for a particular port and destination MAC address. This configuration parameter controls the transmission and the reception of LLDP frames on those interface/address  combinations whose rows are created in this table. Rows in this table can only be created for MAC addresses that can validly be used in association with the type of  interface concerned, as defined by Table 7-2. The contents of this table is persistent across re-initializations or re-boots.
.1.3.111.2.802.1.1.13.1.1.11.1.1,LLDP-V2-MIB::lldpV2PortConfigIfIndexV2,Integer32,not-accessible,,current,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB. The value of this object is used as an index to the lldpV2PortConfigTable.
.1.3.111.2.802.1.1.13.1.1.11.1.2,LLDP-V2-MIB::lldpV2PortConfigDestAddressIndexV2,Unsigned32,not-accessible,,current,,The index value used to identify the destination MAC address associated with this entry. Its value identifies the row in the lldpV2DestAddressTable where the MAC address can be found. The value of this object is used as an index to the lldpV2PortConfigTable.
.1.3.111.2.802.1.1.13.1.1.11.1.3,LLDP-V2-MIB::lldpV2PortConfigAdminStatusV2,INTEGER,read-write,,current,txOnly(1):rxOnly(2):txAndRx(3):disabled(4),The administratively desired status of the local LLDP agent. If the associated lldpV2PortConfigAdminStatus object is set to a value of 'txOnly(1)', then LLDP agent transmits LLDPframes on this port and it does not store any information about the remote systems connected.  If the associated lldpV2PortConfigAdminStatus object is  set to a value of 'rxOnly(2)', then the LLDP agent receives, but it does not transmit, LLDP frames on this port. If the associated lldpV2PortConfigAdminStatus object is set to a value of 'txAndRx(3)', then the LLDP agent transmits and receives LLDP frames on this port. If the associated lldpV2PortConfigAdminStatus object is set to a value of 'disabled(4)', then LLDP agent does not transmit or receive LLDP frames on this port. If there is remote systems information that is received on this port and stored in other tables, before the port's lldpV2PortConfigAdminStatus becomes disabled, then that information is deleted.
.1.3.111.2.802.1.1.13.1.1.11.1.4,LLDP-V2-MIB::lldpV2PortMessageTxInterval,Unsigned32,read-write,,current,,The interval at which LLDP frames are transmitted on behalf of this LLDP agent. This object takes its initial value from the lldpV2MessageTxInterval object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.5,LLDP-V2-MIB::lldpV2PortMessageTxHoldMultiplier,Unsigned32,read-write,,current,,The time to live value expressed as a multiple of the lldpV2MessageTxInterval object. The actual time to live value used in LLDP frames, transmitted on behalf of this LLDP agent, can be expressed by the following formula: TTL = min(65535, (lldpV2MessageTxInterval*lldpV2MessageTxHoldMultiplier)+1) For example, if the value of lldpV2MessageTxInterval is '30', and the value of lldpV2MessageTxHoldMultiplier is '4', then the value '121' is encoded in the TTL field in the LLDP header. This object takes its initial value from the lldpV2PortMessageTxHoldMultiplier object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.6,LLDP-V2-MIB::lldpV2PortReinitDelay,Unsigned32,read-write,,current,,The lldpV2ReinitDelay indicates the delay (in units of seconds) from when lldpPortConfigAdminStatus object of a particular port becomes 'disabled' until re-initialization is attempted. This object takes its initial value from the lldpV2PortReinitDelay object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.7,LLDP-V2-MIB::lldpV2PortNotificationInterval,Unsigned32,read-write,,current,,This object controls the interval between transmission of LLDP notifications during normal transmission periods. This object takes its initial value from the lldpV2PortNotificationInterval object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.8,LLDP-V2-MIB::lldpV2PortTxCreditMax,Unsigned32,read-write,,current,,The maximum number of consecutive LLDPDUs that can be transmitted at any time. This object takes its initial value from the lldpV2PortTxCreditMax object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.9,LLDP-V2-MIB::lldpV2PortMessageFastTx,Unsigned32,read-write,,current,,The interval at which LLDP frames are transmitted on behalf of this LLDP agent during fast transmission period (e.g., when a new neighbor is detected). This object takes its initial value from the lldpV2PortMessageFastTx object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.10,LLDP-V2-MIB::lldpV2PortTxFastInit,Unsigned32,read-write,,current,,The initial value used to initialize the txFast variable which determines the number of transmissions that are made in fast transmission mode. This object takes its initial value from the lldpV2PortTxFastInit object on table row creation. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.1.11.1.11,LLDP-V2-MIB::lldpV2PortConfigNotificationEnableV2,INTEGER,read-write,,current,true(1):false(2),The lldpV2PortConfigNotificationEnableV2 controls, on a per agent basis, whether or not notifications from the agent are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
.1.3.111.2.802.1.1.13.1.1.11.1.12,LLDP-V2-MIB::lldpV2PortConfigTLVsTxEnableV2,BITS,read-write,,current,portDesc(0):sysName(1):sysDesc(2):sysCap(3),The lldpV2PortConfigTLVsTxEnableV2, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. It should be noted that the organizationally-specific TLVs are excluded from the lldpV2PortConfigTLVsTxEnable bitmap.  LLDP Organization Specific Information Extension MIBs should have similar configuration objects to control transmission of their organizationally defined TLVs. The bit 'portDesc(0)' indicates that LLDP agent should transmit 'Port Description TLV'. The bit 'sysName(1)' indicates that LLDP agent should transmit 'System Name TLV'. The bit 'sysDesc(2)' indicates that LLDP agent should transmit 'System Description TLV'. The bit 'sysCap(3)' indicates that LLDP agent should transmit 'System Capabilities TLV'. There is no bit reserved for the management address TLV type since transmission of management address TLVs are controlled by another object, lldpV2ConfigManAddrTable. The default value for lldpV2PortConfigTLVsTxEnable object is empty set, which means no enumerated values are set. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.2,LLDP-V2-MIB::lldpV2Statistics,,,,,,
.1.3.111.2.802.1.1.13.1.2.1,LLDP-V2-MIB::lldpV2StatsRemTablesLastChangeTime,TimeTicks,read-only,,current,,The value of sysUpTime object (defined in IETF RFC 3418) at the time an entry is created, modified, or deleted in the in tables associated with the lldpV2RemoteSystemsData objects and all LLDP extension objects associated with remote systems. An NMS can use this object to reduce polling of the lldpV2RemoteSystemsData objects.
.1.3.111.2.802.1.1.13.1.2.2,LLDP-V2-MIB::lldpV2StatsRemTablesInserts,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpV2RemoteSystemsData and lldpV2Extensions objects. The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed. This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set that result in deletion of previously inserted information should not trigger any changes in lldpV2StatsRemTablesInserts since the insert is not completed yet or in lldpStatsRemTablesDeletes since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
.1.3.111.2.802.1.1.13.1.2.3,LLDP-V2-MIB::lldpV2StatsRemTablesDeletes,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpV2RemoteSystemsData and lldpV2Extensions objects. This counter should be incremented only once when the complete set of information is completely deleted from all related tables. Partial deletions, such as deletion of rows associated with a particular MSAP from some tables, but not from all tables are not allowed, thus should not change the value of this counter.
.1.3.111.2.802.1.1.13.1.2.4,LLDP-V2-MIB::lldpV2StatsRemTablesDrops,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP could not be entered into tables contained in lldpV2RemoteSystemsData and lldpV2Extensions objects because of insufficient resources.
.1.3.111.2.802.1.1.13.1.2.5,LLDP-V2-MIB::lldpV2StatsRemTablesAgeouts,Gauge32,read-only,,current,,The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpV2RemoteSystemsData and lldpV2Extensions objects because the information timeliness interval has expired. This counter should be incremented only once when the complete set of information is completely invalidated (aged out) from all related tables. Partial ageing, similar to deletion case, is not allowed, and thus, should not change the value of this counter.
.1.3.111.2.802.1.1.13.1.2.6,LLDP-V2-MIB::lldpV2StatsTxPortTable,,not-accessible,,current,,A table containing LLDP transmission statistics for individual port/destination address combinations.  Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
.1.3.111.2.802.1.1.13.1.2.6.1,LLDP-V2-MIB::lldpV2StatsTxPortEntry,,not-accessible,lldpV2StatsTxIfIndex:lldpV2StatsTxDestMACAddress,current,,LLDP frame transmission statistics for a particular port and destination MAC address.  The port is contained in the same chassis as the LLDP agent.  All counter values in a particular entry shall be maintained on a continuing basis and shall not be deleted upon expiration of rxInfoTTL timing counters in the LLDP remote systems MIB of the receipt of a shutdown frame from a remote LLDP agent. All statistical counters associated with a particular port on the local LLDP agent become frozen whenever the adminStatus is disabled for the same port. Rows in this table can only be created for MAC addresses that can validly be used in association with the type of  interface concerned, as defined by Table 7-2.
.1.3.111.2.802.1.1.13.1.2.6.1.1,LLDP-V2-MIB::lldpV2StatsTxIfIndex,Integer32,not-accessible,,current,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB. The value of this object is used as an index to the lldpV2StatsTxPortTable.
.1.3.111.2.802.1.1.13.1.2.6.1.2,LLDP-V2-MIB::lldpV2StatsTxDestMACAddress,Unsigned32,not-accessible,,current,,The index value used to identify the destination MAC address associated with this entry. Its value identifies the row in the lldpV2DestAddressTable where the MAC address can be found. The value of this object is used as an index to the lldpV2StatsTxPortTable.
.1.3.111.2.802.1.1.13.1.2.6.1.3,LLDP-V2-MIB::lldpV2StatsTxPortFramesTotal,Counter32,read-only,,current,,The number of LLDP frames transmitted by this LLDP agent on the indicated port to the destination MAC address associated with this row of the table.
.1.3.111.2.802.1.1.13.1.2.6.1.4,LLDP-V2-MIB::lldpV2StatsTxLLDPDULengthErrors,Counter32,read-only,,current,,The number of LLDPDU Length Errors recorded for the Port.
.1.3.111.2.802.1.1.13.1.2.7,LLDP-V2-MIB::lldpV2StatsRxPortTable,,not-accessible,,current,,A table containing LLDP reception statistics for individual ports and destination MAC addresses.  Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
.1.3.111.2.802.1.1.13.1.2.7.1,LLDP-V2-MIB::lldpV2StatsRxPortEntry,,not-accessible,lldpV2StatsRxDestIfIndex:lldpV2StatsRxDestMACAddress,current,,LLDP frame reception statistics for a particular port. The port is contained in the same chassis as the LLDP agent.  All counter values in a particular entry shall be maintained on a continuing basis and shall not be deleted upon expiration of rxInfoTTL timing counters in the LLDP remote systems MIB of the receipt of a shutdown frame from a remote LLDP agent. All statistical counters associated with a particular port on the local LLDP agent become frozen whenever the adminStatus is disabled for the same port. Rows in this table can only be created for MAC addresses that can validly be used in association with the type of  interface concerned, as defined by Table 7-2. The contents of this table is persistent across re-initializations or re-boots.
.1.3.111.2.802.1.1.13.1.2.7.1.1,LLDP-V2-MIB::lldpV2StatsRxDestIfIndex,Integer32,not-accessible,,current,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB. The value of this object is used as an index to the lldpStatsRxPortV2Table.
.1.3.111.2.802.1.1.13.1.2.7.1.2,LLDP-V2-MIB::lldpV2StatsRxDestMACAddress,Unsigned32,not-accessible,,current,,The index value used to identify the destination MAC address associated with this entry. Its value identifies the row in the lldpV2DestAddressTable where the MAC address can be found. The value of this object is used as an index to the lldpStatsRxPortV2Table.
.1.3.111.2.802.1.1.13.1.2.7.1.3,LLDP-V2-MIB::lldpV2StatsRxPortFramesDiscardedTotal,Counter32,read-only,,current,,The number of LLDP frames received by this LLDP agent on the indicated port, and then discarded for any reason. This counter can provide an indication that LLDP header formatting problems may exist with the local LLDP agent in the sending system or that LLDPDU validation problems may exist with the local LLDP agent in the receiving system.
.1.3.111.2.802.1.1.13.1.2.7.1.4,LLDP-V2-MIB::lldpV2StatsRxPortFramesErrors,Counter32,read-only,,current,,The number of invalid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled.
.1.3.111.2.802.1.1.13.1.2.7.1.5,LLDP-V2-MIB::lldpV2StatsRxPortFramesTotal,Counter32,read-only,,current,,The number of valid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled.
.1.3.111.2.802.1.1.13.1.2.7.1.6,LLDP-V2-MIB::lldpV2StatsRxPortTLVsDiscardedTotal,Counter32,read-only,,current,,The number of LLDP TLVs discarded for any reason by this LLDP agent on the indicated port.
.1.3.111.2.802.1.1.13.1.2.7.1.7,LLDP-V2-MIB::lldpV2StatsRxPortTLVsUnrecognizedTotal,Counter32,read-only,,current,,The number of LLDP TLVs received on the given port that are not recognized by this LLDP agent on the indicated port.  An unrecognized TLV is referred to as the TLV whose type value is in the range of reserved TLV types (000 1001 - 111 1110) in Table 8-1 of IEEE Std 802.1AB-2015. An unrecognized TLV may be a basic management TLV from a later LLDP version.
.1.3.111.2.802.1.1.13.1.2.7.1.8,LLDP-V2-MIB::lldpV2StatsRxPortAgeoutsTotal,Gauge32,read-only,,current,,The counter that represents the number of age-outs that occurred on a given port. An age-out is the number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpV2RemoteSystemsData and lldpV2Extensions objects because the information timeliness interval has expired. This counter is similar to lldpV2StatsRemTablesAgeouts, except that the counter is on a per port basis. This enables NMS to poll tables associated with the lldpV2RemoteSystemsData objects and all LLDP extension objects associated with remote systems on the indicated port only. This counter is set to zero during agent initialization and its value should not be saved in non-volatile storage. This counter is incremented only once when the complete set of information is invalidated (aged out) from all related tables on a particular port. Partial ageing is not allowed.
.1.3.111.2.802.1.1.13.1.3,LLDP-V2-MIB::lldpV2LocalSystemData,,,,,,
.1.3.111.2.802.1.1.13.1.3.1,LLDP-V2-MIB::lldpV2LocChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),The type of encoding used to identify the chassis associated with the local system.
.1.3.111.2.802.1.1.13.1.3.2,LLDP-V2-MIB::lldpV2LocChassisId,OCTET,read-only,,current,,The string value used to identify the chassis component associated with the local system.
.1.3.111.2.802.1.1.13.1.3.3,LLDP-V2-MIB::lldpV2LocSysName,OCTET,read-only,,current,,The string value used to identify the system name of the local system. If the local agent supports IETF RFC 3418, lldpLocSysName object should have the same value as sysName object.
.1.3.111.2.802.1.1.13.1.3.4,LLDP-V2-MIB::lldpV2LocSysDesc,OCTET,read-only,,current,,The string value used to identify the system description of the local system. If the local agent supports IETF RFC 3418, lldpLocSysDesc object should have the same value as sysDesc object.
.1.3.111.2.802.1.1.13.1.3.5,LLDP-V2-MIB::lldpV2LocSysCapSupported,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7):cVLANComponent(8):sVLANComponent(9):twoPortMACRelay(10),The bitmap value used to identify which system capabilities are supported on the local system.
.1.3.111.2.802.1.1.13.1.3.6,LLDP-V2-MIB::lldpV2LocSysCapEnabled,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7):cVLANComponent(8):sVLANComponent(9):twoPortMACRelay(10),The bitmap value used to identify which system capabilities are enabled on the local system.
.1.3.111.2.802.1.1.13.1.3.7,LLDP-V2-MIB::lldpV2LocPortTable,,not-accessible,,current,,This table contains one row per port of information associated with the local system known to this agent.
.1.3.111.2.802.1.1.13.1.3.7.1,LLDP-V2-MIB::lldpV2LocPortEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about a particular port component. Entries may be created and deleted in this table by the agent. Rows in this table can only be created for MAC addresses that can validly be used in association with the type of  interface concerned, as defined by Table 7-2. The contents of this table is persistent across re-initializations or re-boots.
.1.3.111.2.802.1.1.13.1.3.7.1.1,LLDP-V2-MIB::lldpV2LocPortIfIndex,Integer32,not-accessible,,current,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB. The value of this object is used as an index to the lldpV2LocPortTable.
.1.3.111.2.802.1.1.13.1.3.7.1.2,LLDP-V2-MIB::lldpV2LocPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),The type of port identifier encoding used in the associated 'lldpLocPortId' object.
.1.3.111.2.802.1.1.13.1.3.7.1.3,LLDP-V2-MIB::lldpV2LocPortId,OCTET,read-only,,current,,The string value used to identify the port component associated with a given port in the local system.
.1.3.111.2.802.1.1.13.1.3.7.1.4,LLDP-V2-MIB::lldpV2LocPortDesc,OCTET,read-only,,current,,The string value used to identify the IEEE 802 LAN station's port description associated with the local system. If the local agent supports IETF RFC 2863, lldpLocPortDesc object should have the same value of ifDescr object.
.1.3.111.2.802.1.1.13.1.3.8,LLDP-V2-MIB::lldpV2LocManAddrTable,,not-accessible,,current,,This table contains management address information on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.3.8.1,LLDP-V2-MIB::lldpV2LocManAddrEntry,,not-accessible,lldpV2LocManAddrSubtype:lldpV2LocManAddr,current,,Management address information about a particular chassis component. There may be multiple management addresses configured on the system identified by a particular lldpLocChassisId. Each management address should have distinct 'management address type' (lldpV2LocManAddrSubtype) and 'management address' (lldpLocManAddr.) Entries may be created and deleted in this table by the agent. Since a variable length octetstring is used as an index in a table, the address length is encoded as part of the OID (as per IETF RFC 2578).
.1.3.111.2.802.1.1.13.1.3.8.1.1,LLDP-V2-MIB::lldpV2LocManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpLocManagmentAddr' object. It should be noted that only a subset of the possible address encodings enumerated in AddressFamilyNumbers are appropriate for use as a LLDP management address, either because some are just not applicable or  because the maximum size of a LldpV2ManAddress octet string would prevent the use of some address identifier encodings.
.1.3.111.2.802.1.1.13.1.3.8.1.2,LLDP-V2-MIB::lldpV2LocManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the local system. The purpose of this address is to contact the management entity.
.1.3.111.2.802.1.1.13.1.3.8.1.3,LLDP-V2-MIB::lldpV2LocManAddrLen,Unsigned32,read-only,,current,,The total length of the management address subtype and the management address fields in LLDPDUs transmitted by the local LLDP agent. The management address length field is needed so that the receiving systems that do not implement SNMP are not required to implement an Internet Assigned Numbers  Authority (IANA) family numbers/address length equivalency table in order to decode the management address.
.1.3.111.2.802.1.1.13.1.3.8.1.4,LLDP-V2-MIB::lldpV2LocManAddrIfSubtype,INTEGER,read-only,,current,unknown(1):ifIndex(2):systemPortNumber(3),The enumeration value that identifies the interface numbering method used for defining the interface number (lldpV2LocManAddrIfId), associated with the local system.
.1.3.111.2.802.1.1.13.1.3.8.1.5,LLDP-V2-MIB::lldpV2LocManAddrIfId,Unsigned32,read-only,,current,,The integer value used to identify the interface number regarding the management address component associated with the local system.
.1.3.111.2.802.1.1.13.1.3.8.1.6,LLDP-V2-MIB::lldpV2LocManAddrOID,OBJECT,read-only,,current,,The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the local system agent.
.1.3.111.2.802.1.1.13.1.4,LLDP-V2-MIB::lldpV2RemoteSystemsData,,,,,,
.1.3.111.2.802.1.1.13.1.4.1,LLDP-V2-MIB::lldpV2RemTable,,not-accessible,,current,,This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port and destination MAC address, or it may choose to maintain multiple lldpRemEntries for the same local port and destination MAC address. The following procedure may be used to retrieve remote systems information updates from an LLDP agent: 1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpV2StatsRemTablesInserts b. lldpV2StatsRemTablesDeletes c. lldpV2StatsRemTablesDrops d. lldpV2StatsRemTablesAgeouts e. lldpV2StatsRxPortAgeoutsTotal for all ports. 2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations. 3. NMS receives the notifications and compares the new values of objects listed in step 1.  Periodically, NMS should poll the object lldpV2StatsRemTablesLastChangeTime to find out if anything has changed since the last poll. If something has changed, NMS polls the objects listed in step 1 to figure out what kind of changes occurred in the tables. If value of lldpV2StatsRemTablesInserts has changed, then NMS walks all tables by employing TimeFilter with the last-polled time value. This request returns new objects or objects whose values have been updated since the last poll. If value of lldpV2StatsRemTablesAgeouts has changed, then NMS walks the lldpStatsRxPortAgeoutsTotal and compares the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS can retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter). lldpV2StatsRemTablesDeletes and lldpV2StatsRemTablesDrops objects are provided for informational purposes.
.1.3.111.2.802.1.1.13.1.4.1.1,LLDP-V2-MIB::lldpV2RemEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Information about a particular physical network connection. Entries may be created and deleted in this table by the agent, if a physical topology discovery process is active. Rows in this table can only be created for MAC addresses that can validly be used in association with the type of  interface concerned, as defined by Table 7-2. The contents of this table is persistent across re-initializations or re-boots.
.1.3.111.2.802.1.1.13.1.4.1.1.1,LLDP-V2-MIB::lldpV2RemTimeMark,TimeTicks,not-accessible,,current,,A TimeFilter for this entry. See the TimeFilter textual convention in IETF RFC 4502 and  http://www.ietf.org/IESG/Implementations/RFC2021-Implementation.txt to see how TimeFilter works.
.1.3.111.2.802.1.1.13.1.4.1.1.2,LLDP-V2-MIB::lldpV2RemLocalIfIndex,Integer32,not-accessible,,current,,The interface index value used to identify the port associated with this entry. Its value is an index into the interfaces MIB The value of this object is used as an index to the lldpV2RemTable.
.1.3.111.2.802.1.1.13.1.4.1.1.3,LLDP-V2-MIB::lldpV2RemLocalDestMACAddress,Unsigned32,not-accessible,,current,,The index value used to identify the destination MAC address associated with this entry. Its value identifies the row in the lldpV2DestAddressTable where the MAC address can be found. The value of this object is used as an index to the lldpV2RemTable.
.1.3.111.2.802.1.1.13.1.4.1.1.4,LLDP-V2-MIB::lldpV2RemIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemIndex can wrap between reboots.
.1.3.111.2.802.1.1.13.1.4.1.1.5,LLDP-V2-MIB::lldpV2RemChassisIdSubtype,INTEGER,read-only,,current,chassisComponent(1):interfaceAlias(2):portComponent(3):macAddress(4):networkAddress(5):interfaceName(6):local(7),The type of encoding used to identify the chassis associated with the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.6,LLDP-V2-MIB::lldpV2RemChassisId,OCTET,read-only,,current,,The string value used to identify the chassis component associated with the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.7,LLDP-V2-MIB::lldpV2RemPortIdSubtype,INTEGER,read-only,,current,interfaceAlias(1):portComponent(2):macAddress(3):networkAddress(4):interfaceName(5):agentCircuitId(6):local(7),The type of port identifier encoding used in the associated 'lldpRemPortId' object.
.1.3.111.2.802.1.1.13.1.4.1.1.8,LLDP-V2-MIB::lldpV2RemPortId,OCTET,read-only,,current,,The string value used to identify the port component associated with the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.9,LLDP-V2-MIB::lldpV2RemPortDesc,OCTET,read-only,,current,,The string value used to identify the description of the given port associated with the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.10,LLDP-V2-MIB::lldpV2RemSysName,OCTET,read-only,,current,,The string value used to identify the system name of the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.11,LLDP-V2-MIB::lldpV2RemSysDesc,OCTET,read-only,,current,,The string value used to identify the system description of the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.12,LLDP-V2-MIB::lldpV2RemSysCapSupported,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7):cVLANComponent(8):sVLANComponent(9):twoPortMACRelay(10),The bitmap value used to identify which system capabilities are supported on the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.13,LLDP-V2-MIB::lldpV2RemSysCapEnabled,BITS,read-only,,current,other(0):repeater(1):bridge(2):wlanAccessPoint(3):router(4):telephone(5):docsisCableDevice(6):stationOnly(7):cVLANComponent(8):sVLANComponent(9):twoPortMACRelay(10),The bitmap value used to identify which system capabilities are enabled on the remote system.
.1.3.111.2.802.1.1.13.1.4.1.1.14,LLDP-V2-MIB::lldpV2RemRemoteChanges,INTEGER,read-only,,current,true(1):false(2),Indicates that there are changes in the remote systems MIB, as determined by the variable remoteChanges.
.1.3.111.2.802.1.1.13.1.4.1.1.15,LLDP-V2-MIB::lldpV2RemTooManyNeighbors,INTEGER,read-only,,current,true(1):false(2),Indicates that there are too many neighbors as determined by the variable tooManyNeighbors.
.1.3.111.2.802.1.1.13.1.4.2,LLDP-V2-MIB::lldpV2RemManAddrTable,,not-accessible,,current,,This table contains one or more rows per management address information on the remote system learned on a particular port contained in the local chassis known to this agent.
.1.3.111.2.802.1.1.13.1.4.2.1,LLDP-V2-MIB::lldpV2RemManAddrEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpV2RemManAddrSubtype:lldpV2RemManAddr,current,,Management address information about a particular chassis component. There may be multiple management addresses configured on the remote system identified by a particular lldpRemIndex whose information is received on an interface of the local system and a given destination MAC address. Each management address should have distinct 'management address type' (lldpRemManAddrSubtype) and 'management address' (lldpRemManAddr). Entries may be created and deleted in this table by the agent. Since a variable length octetstring is used as an index in a table, theaddress length is encoded as part of the OID (as per IETF RFC 2578).
.1.3.111.2.802.1.1.13.1.4.2.1.1,LLDP-V2-MIB::lldpV2RemManAddrSubtype,INTEGER,not-accessible,,current,other(0):ipV4(1):ipV6(2):nsap(3):hdlc(4):bbn1822(5):all802(6):e163(7):e164(8):f69(9):x121(10):ipx(11):appleTalk(12):decnetIV(13):banyanVines(14):e164withNsap(15):dns(16):distinguishedName(17):asNumber(18):xtpOverIpv4(19):xtpOverIpv6(20):xtpNativeModeXTP(21):fibreChannelWWPN(22):fibreChannelWWNN(23):gwid(24):afi(25):mplsTpSectionEndpointIdentifier(26):mplsTpLspEndpointIdentifier(27):mplsTpPseudowireEndpointIdentifier(28):eigrpCommonServiceFamily(16384):eigrpIpv4ServiceFamily(16385):eigrpIpv6ServiceFamily(16386):lispCanonicalAddressFormat(16387):bgpLs(16388):fortyeightBitMac(16389):sixtyfourBitMac(16390):oui(16391):mac24(16392):mac40(16393):ipv664(16394):rBridgePortID(16395):trillNickname(16396):reserved(65535),The type of management address identifier encoding used in the associated 'lldpRemManagmentAddr' object. It should be noted that only a subset of the possible address encodings enumerated in AddressFamilyNumbers are appropriate for use as a LLDP management address, either because some are just not apliccable or  because the maximum size of a LldpV2ManAddress octet string would prevent the use of some address identifier encodings.
.1.3.111.2.802.1.1.13.1.4.2.1.2,LLDP-V2-MIB::lldpV2RemManAddr,OCTET,not-accessible,,current,,The string value used to identify the management address component associated with the remote system. The purpose of this address is to contact the management entity.
.1.3.111.2.802.1.1.13.1.4.2.1.3,LLDP-V2-MIB::lldpV2RemManAddrIfSubtype,INTEGER,read-only,,current,unknown(1):ifIndex(2):systemPortNumber(3),The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the remote system.
.1.3.111.2.802.1.1.13.1.4.2.1.4,LLDP-V2-MIB::lldpV2RemManAddrIfId,Unsigned32,read-only,,current,,The integer value used to identify the interface number regarding the management address component associated with the remote system. The value depends upon the value of the lldpV2RemManAddrIfSubtype for the table row.
.1.3.111.2.802.1.1.13.1.4.2.1.5,LLDP-V2-MIB::lldpV2RemManAddrOID,OBJECT,read-only,,current,,The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the remote system agent.
.1.3.111.2.802.1.1.13.1.4.3,LLDP-V2-MIB::lldpV2RemUnknownTLVTable,,not-accessible,,current,,This table contains information about an incoming TLV that is not recognized by the receiving LLDP agent. The TLV may be from a later version of the basic management set. This table should only contain TLVs that are found in a single LLDP frame. Entries in this table, associated with an MAC service access point (MSAP, the access point for MAC services provided to the LCC sublayer, defined in IEEE Standards Dictionary Online, which is also identified with a particular lldpRemLocalPortNum, lldpRemIndex pair) are overwritten with most recently received unrecognized TLV from the same MSAP, or they naturally age out when the rxInfoTTL timer (associated with the MSAP) expires.
.1.3.111.2.802.1.1.13.1.4.3.1,LLDP-V2-MIB::lldpV2RemUnknownTLVEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpV2RemUnknownTLVType,current,,Information about an unrecognized TLV received from a physical network connection. Entries may be created and deleted in this table by the agent, if a physical topology discovery process is active.
.1.3.111.2.802.1.1.13.1.4.3.1.1,LLDP-V2-MIB::lldpV2RemUnknownTLVType,Unsigned32,not-accessible,,current,,This object represents the value extracted from the type field of the TLV.
.1.3.111.2.802.1.1.13.1.4.3.1.2,LLDP-V2-MIB::lldpV2RemUnknownTLVInfo,OCTET,read-only,,current,,This object represents the value extracted from the value field of the TLV.
.1.3.111.2.802.1.1.13.1.4.4,LLDP-V2-MIB::lldpV2RemOrgDefInfoTable,,not-accessible,,current,,This table contains one or more rows per physical network connection which advertises the organizationally defined information. Note that this table contains one or more rows of organizationally defined information that is not recognized by the local agent. If the local system is capable of recognizing any organizationally defined information, appropriate extension MIBs from the organization should be used for information retrieval.
.1.3.111.2.802.1.1.13.1.4.4.1,LLDP-V2-MIB::lldpV2RemOrgDefInfoEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpV2RemOrgDefInfoOUI:lldpV2RemOrgDefInfoSubtype:lldpV2RemOrgDefInfoIndex,current,,Information about the unrecognized organizationally defined information advertised by the remote system. The lldpRemTimeMark, lldpRemLocalPortNum, lldpRemIndex, lldpRemOrgDefInfoOUI, lldpRemOrgDefInfoSubtype, and lldpRemOrgDefInfoIndex are indexes to this table. If there is an lldpRemOrgDefInfoEntry associated with a particular remote system identified by the lldpRemLocalPortNum and lldpRemIndex, then there is an lldpRemEntry associated with the same instance (i.e., using same indexes.) When the lldpRemEntry for the same index is removed from the lldpRemTable, the associated lldpRemOrgDefInfoEntry is removed from the lldpRemOrgDefInfoTable. Entries may be created and deleted in this table by the agent.
.1.3.111.2.802.1.1.13.1.4.4.1.1,LLDP-V2-MIB::lldpV2RemOrgDefInfoOUI,OCTET,not-accessible,,current,,The Organizationally Unique Identifier (OUI), as defined in IEEE Std 802, is a 24 bit (three octets) globally unique assigned number referenced by various standards, of the information received from the remote system.
.1.3.111.2.802.1.1.13.1.4.4.1.2,LLDP-V2-MIB::lldpV2RemOrgDefInfoSubtype,Unsigned32,not-accessible,,current,,The integer value used to identify the subtype of the organizationally defined information received from the remote system. The subtype value is required to identify different instances of organizationally defined information that could not be retrieved without a unique identifier that indicates the particular type of information contained in the information string.
.1.3.111.2.802.1.1.13.1.4.4.1.3,LLDP-V2-MIB::lldpV2RemOrgDefInfoIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular unrecognized organizationally defined information instance, unique only for the lldpRemOrgDefInfoOUI and lldpRemOrgDefInfoSubtype from the same remote system. An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemOrgDefInfoIndex can wrap between reboots.
.1.3.111.2.802.1.1.13.1.4.4.1.4,LLDP-V2-MIB::lldpV2RemOrgDefInfo,OCTET,read-only,,current,,The string value used to identify the organizationally defined information of the remote system. The encoding for this object should be as defined for SnmpAdminString TC.
.1.3.111.2.802.1.1.13.1.5,LLDP-V2-MIB::lldpV2Extensions,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3MIB,,,,,,The LLDP Management Information Base extension module for IEEE 802.3 organizationally defined discovery information. In order to assure the uniqueness of the LLDP-MIB, lldpV2Xdot3MIB is branched from lldpV2Extensions using OUI value as the node. An OUI/'company_id' is a 24 bit globally unique assigned number referenced by various standards. Unless otherwise indicated, the references in this MIB module are to IEEE 802.1AB-2009. Copyright (C) IEEE (2009). This version of this MIB module is published as Annex F.6.5 of IEEE Std 802.1AB-2009; see the standard itself for full legal notices.
.1.3.111.2.802.1.1.13.1.5.4623.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3Objects,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3Config,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.1.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3PortConfigTable,,not-accessible,,current,,A table that controls selection of LLDP TLVs to be transmitted  on individual ports.
.1.3.111.2.802.1.1.13.1.5.4623.1.1.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3PortConfigEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.3 organizationally defined TLVs on LLDP transmission capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpV2Xdot3PortConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.4623.1.1.1.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3PortConfigTLVsTxEnable,BITS,read-write,,current,macPhyConfigStatus(0):powerViaMDI(1):unused(2):maxFrameSize(3),The lldpV2Xdot3PortConfigTLVsTxEnable, defined as a bitmap, includes the IEEE 802.3 organizationally defined set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to an IEEE 802.3 subtype associated with a specific IEEE 802.3 optional TLV. The bit 0 is not used since there is no corresponding subtype. The bit 'macPhyConfigStatus(0)' indicates that LLDP agent should transmit 'MAC/PHY configuration/status TLV'. The bit 'powerViaMDI(1)' indicates that LLDP agent should transmit 'Power via MDI TLV'. The bit 'unused(2)' is no longer used; this was used for the 'Link Aggregation TLV' in the previous version. The bit 'maxFrameSize(3)' indicates that LLDP agent should transmit 'Maximum-frame-size TLV'. The default value for lldpV2Xdot3PortConfigTLVsTxEnable object is an empty set, which means no enumerated values are set. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocalData,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.1.2.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPortTable,,not-accessible,,current,,This table contains one row per port of Ethernet port information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPortEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about a particular port component.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.1.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPortAutoNegSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with the local system) supports Auto-negotiation.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.1.1.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPortAutoNegEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether port Auto-negotiation is enabled on the given port associated with the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.1.1.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPortAutoNegAdvertisedCap,OCTET,read-only,,current,,This object contains the value (bitmap) of the ifMauAutoNegCapAdvertisedBits object (defined in IETF RFC 3636) which is associated with the given port on the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.1.1.4,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPortOperMauType,Unsigned32,read-only,,current,,An integer value that indicates the operational MAU type of the given port on the local system. This object contains the integer value derived from the list position of the corresponding dot3MauType as listed  in IETF RFC 4836 (or subsequent revisions) and is equal to the last number in the respective dot3MauType OID.  For example, if the ifMauType object is dot3MauType1000BaseTHD which corresponds to {dot3MauType 29}, the numerical value of this field is 29. For MAU types not listed in RFC 4836 (or subsequent revisions), the value of this field shall be set to zero.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerTable,,not-accessible,,current,,This table contains one row per port of power ethernet  information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about a particular port component.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerPortClass,INTEGER,read-only,,current,pClassPSE(1):pClassPD(2),The value that identifies the port Class of the given port associated with the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerMDISupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is supported on the given port associated with the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerMDIEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to identify whether MDI power is enabled on the given port associated with the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.4,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerPairControlable,INTEGER,read-only,,current,true(1):false(2),The truth value is derived from the value of pethPsePortPowerPairsControlAbility object (defined in IETF RFC 3621) and is used to indicate whether the pair selection can be controlled on the given port associated with the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.5,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerPairs,Unsigned32,read-only,,current,,This object contains the value of the pethPsePortPowerPairs object (defined in IETF RFC 3621) which is associated with the given port on the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.6,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocPowerClass,Unsigned32,read-only,,current,,This object contains the value of the pethPsePortPowerClassifications object (defined in IETF RFC 3621) which is associated with the given port on the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocMaxFrameSizeTable,,not-accessible,,current,,This table contains one row per port of maximum frame  size information (as a part of the LLDP 802.3 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.3.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocMaxFrameSizeEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Maximum Frame Size information about a particular port component.
.1.3.111.2.802.1.1.13.1.5.4623.1.2.3.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocMaxFrameSize,Unsigned32,read-only,,current,,An integer value indicating the maximum supported frame  size in octets on the given port of the local system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemoteData,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.1.3.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPortTable,,not-accessible,,current,,This table contains Ethernet port information (as a part of the LLDP 802.3 organizational extension) of the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPortEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Information about a particular physical network connection.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.1.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPortAutoNegSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with remote system) supports Auto-negotiation.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.1.1.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPortAutoNegEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether port Auto-negotiation is enabled on the given port associated with the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.1.1.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPortAutoNegAdvertisedCap,OCTET,read-only,,current,,This object contains the value (bitmap) of the ifMauAutoNegCapAdvertisedBits object (defined in IETF RFC 3636) which is associated with the given port on the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.1.1.4,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPortOperMauType,Unsigned32,read-only,,current,,An integer value that indicates the operational MAU type of the sending device. This object contains the integer value derived from the list position of the corresponding dot3MauType as listed in in IETF RFC 4836 (or subsequent revisions) and is equal to the last number in the respective dot3MauType OID.  For example, if the ifMauType object is dot3MauType1000BaseTHD which corresponds to {dot3MauType 29}, the numerical value of this field is 29. For MAU types not listed in RFC 4836 (or subsequent revisions), the value of this field shall be set to zero.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerTable,,not-accessible,,current,,This table contains Ethernet power information (as a part of the LLDP 802.3 organizational extension) of the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Information about a particular physical network connection.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerPortClass,INTEGER,read-only,,current,pClassPSE(1):pClassPD(2),The value that identifies the port Class of the given port associated with the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerMDISupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the MDI power is supported on the given port associated with the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerMDIEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to identify whether MDI power is enabled on the given port associated with the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.4,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerPairControlable,INTEGER,read-only,,current,true(1):false(2),The truth value is derived from the value of pethPsePortPowerPairsControlAbility object (defined in IETF RFC 3621) and is used to indicate whether the pair selection can be controlled on the given port associated with the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.5,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerPairs,Unsigned32,read-only,,current,,This object contains the value of the pethPsePortPowerPairs object (defined in IETF RFC 3621) which is associated with the given port on the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.6,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemPowerClass,Unsigned32,read-only,,current,,This object contains the value of the pethPsePortPowerClassifications object (defined in IETF RFC 3621) which is associated with the given port on the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemMaxFrameSizeTable,,not-accessible,,current,,This table contains one row per port/destination address pair of maximum frame  size information (as a part of the LLDP IEEE 802.3  organizational extension) of the remote system.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.3.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemMaxFrameSizeEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Maximum Frame Size information about a particular port component.
.1.3.111.2.802.1.1.13.1.5.4623.1.3.3.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemMaxFrameSize,Unsigned32,read-only,,current,,An integer value indicating the maximum supported frame  size in octets on the port component associated with the  remote system.
.1.3.111.2.802.1.1.13.1.5.4623.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3Conformance,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.2.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3Compliances,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.2.1.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3TxRxCompliance,,,,,,A compliance statement for SNMP entities that implement the LLDP 802.3 organizational extension MIB. This group is mandatory for all agents that implement the  LLDP 802.3 organizational extension in TX and/or RX mode. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.4623.2.1.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3TxCompliance,,,,,,The compliance statement for SNMP entities which implement the LLDP 802.3 organizational extension MIB. This group is mandatory for agents which implement the  LLDP 802.3 organizational extension in the TX mode. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.4623.2.1.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RxCompliance,,,,,,The compliance statement for SNMP entities which implement the LLDP 802.3 organizational extension MIB. This group is mandatory for agents which implement the  LLDP 802.3 organizational extension in the RX mode. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.4623.2.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3Groups,,,,,,
.1.3.111.2.802.1.1.13.1.5.4623.2.2.1,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3ConfigGroup,,,,,,The collection of objects which are used to configure the LLDP 802.3 organizational extension implementation behavior. 
.1.3.111.2.802.1.1.13.1.5.4623.2.2.2,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3LocSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.3 organizational extension Local Device Information. 
.1.3.111.2.802.1.1.13.1.5.4623.2.2.3,LLDP-EXT-DOT3-V2-MIB::lldpV2Xdot3RemSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.3 organizational extension Local Device Information. 
.1.3.111.2.802.1.1.13.1.5.32962,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1MIB,,,,,,The LLDP Management Information Base extension module for IEEE 802.1 organizationally defined discovery information. In order to ensure the uniqueness of the LLDP-V2-MIB, lldpV2Xdot1MIB is branched from lldpV2Extensions using an  Organizationally Unique Identifier (OUI) value as the node. An OUI is a 24 bit globally unique number assigned by the  IEEE Registration Authority - see:  http://standards.ieee.org/develop/regauth/oui/index.html Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is published as D.5.5 of IEEE Std 802.1Q; see the standard itself for full legal notices.
.1.3.111.2.802.1.1.13.1.5.32962.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1Objects,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1Config,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigPortVlanTable,,not-accessible,,current,,A table that controls selection of LLDP Port VLAN-ID TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigPortVlanEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined Port VLAN-ID TLV on LLDP transmission-capable ports. This configuration object augments the  lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the  associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding  lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigPortVlanTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpV2Xdot1ConfigPortVlanTxEnable, which is defined  as a truth value and configured by the network management, determines whether the IEEE 802.1 organizationally defined port VLAN TLV transmission is allowed on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigVlanNameTable,,not-accessible,,current,,The table that controls selection of LLDP VLAN name TLV instances to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigVlanNameEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the Local System VLAN name instance is transmitted. This configuration object augments the lldpV2LocVlanEntry, therefore it is only present along with the VLAN Name  instance contained in the associated lldpV2LocVlanNameEntry entry. Each active lldpV2Xdot1ConfigVlanNameEntry is restored from non-volatile storage (along with the corresponding lldpV2Xdot1LocVlanNameEntry) after a re-initialization of  the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigVlanNameTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding Local System VLAN name instance is transmitted on the port defined by the given lldpV2Xdot1LocVlanNameEntry. The value of this object is restored from non-volatile storage after a re-initialization of the management  system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigProtoVlanTable,,not-accessible,,current,,The table that controls selection of LLDP Port And  Protocol VLAN ID TLV instances to be transmitted on  individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigProtoVlanEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the Local System Protocol VLAN instance is transmitted. This configuration object augments the  lldpV2Xdot1LocVlanEntry, therefore it is only present along  with the Port and Protocol VLAN ID instance contained in  the associated lldpV2Xdot1LocVlanEntry entry. Each active lldpV2Xdot1ConfigProtoVlanEntry is restored from non-volatile storage (along with the corresponding lldpV2Xdot1LocProtoVlanEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigProtoVlanTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding Local System Port and Protocol VLAN instance is transmitted on the port defined by the given lldpV2Xdot1LocProtoVlanEntry. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.4,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigProtocolTable,,not-accessible,,current,,The table that controls selection of LLDP Protocol  TLV instances to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.4.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigProtocolEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of ports (represented as a PortList) on which the Local System Protocol instance is transmitted. This configuration object augments the  lldpV2Xdot1LocProtoEntry, therefore it is only present  along with the Protocol instance contained in the  associated lldpV2Xdot1LocProtoEntry entry. Each active lldpV2Xdot1ConfigProtocolEntry is restored from non-volatile storage (along with the corresponding lldpV2Xdot1LocProtocolEntry) after a re-initialization of  the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigProtocolTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding Local System Protocol Identity instance is transmitted on the port defined by the given  lldpV2Xdot1LocProtocolEntry. The value of this object is restored from non-volatile storage after a re-initialization of the management  system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.5,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigVidUsageDigestTable,,not-accessible,,current,,A table that controls selection of LLDP VID Usage Digest TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.5.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigVidUsageDigestEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of  ports (represented as a PortList) on which the local  system VID Usage Digest instance will be transmitted. This configuration object augments the  lldpLocVidUsageDigestEntry, therefore it is only present along with the VID Usage Digest instance  contained in the associated lldpV2Xdot1LocVidUsageDigestEntry entry. Each active lldpConfigVidUsageDigestEntry must be  restored from non-volatile storage and re-created (along with the corresponding lldpV2Xdot1LocVidUsageDigestEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigVidUsageDigestTxEnable,INTEGER,read-write,,current,true(1):false(2),The boolean value that indicates whether the corresponding  Local System VID Usage Digest instance will be transmitted  on the port defined by the given  lldpV2Xdot1LocVidUsageDigestEntry. The value of this object  must be restored from non-volatile storage after a  reinitialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.6,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigManVidTable,,not-accessible,,current,,A table that controls selection of LLDP Management VID  TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.6.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigManVidEntry,,not-accessible,,current,,LLDP configuration information that specifies the set of port/destination address pairs on which the Local System Management VID will be transmitted. This configuration object augments the  lldpV2Xdot1LocManVidEntry, therefore it is only present along with the Management VID contained in the associated lldpV2Xdot1LocManVidEntry entry.  Each active lldpV2Xdot1ConfigManVidEntry must be restored from non-volatile storage (along with the corresponding lldpV2Xdot1LocManVidEntry) after a  re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.1.6.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigManVidTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpV2Xdot1ConfigManVidTxEnable, which is defined as a  truth value and configured by the network management,  determines whether the IEEE 802.1 organizationally  defined Management VID TLV transmission is allowed on a given LLDP transmission-capable port.  The value of this object must be restored from non-volatile storage after a re-initialization of the  management system.
.1.3.111.2.802.1.1.13.1.5.32962.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocalData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocTable,,not-accessible,,current,,This table contains one row per port for IEEE 802.1 organizationally defined LLDP extension on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about IEEE 802.1 organizationally defined LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocPortVlanId,Unsigned32,read-only,,current,,The integer value used to identify the port's VLAN  identifier associated with the local system. A value  of zero shall be used if the system either does not know the PVID or does not support Port-based VLAN operation.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtoVlanTable,,not-accessible,,current,,This table contains one or more rows per Port and Protocol VLAN information about the local system.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtoVlanEntry,,not-accessible,lldpV2LocPortIfIndex:lldpV2Xdot1LocProtoVlanId,current,,Port and protocol VLAN ID Information about a particular port component. There may be multiple port and protocol VLANs, identified by a particular  lldpV2Xdot1LocProtoVlanId, configured on the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtoVlanId,Unsigned32,not-accessible,,current,,The integer value used to identify the port and protocol VLANs associated with the given port associated with the local system. A value of zero shall be used if the system either does not know the protocol VLAN ID (PPVID) or does not support port and protocol VLAN operation.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtoVlanSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with the local system) supports port and  protocol VLANs.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.2.1.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtoVlanEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the port and protocol VLANs are enabled on the given port associated with the local system.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVlanNameTable,,not-accessible,,current,,This table contains one or more rows per IEEE 802.1Q VLAN name information on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.3.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVlanNameEntry,,not-accessible,lldpV2LocPortIfIndex:lldpV2Xdot1LocVlanId,current,,VLAN name Information about a particular port component. There may be multiple VLANs, identified by a particular lldpV2Xdot1LocVlanId, configured on the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVlanId,Integer32,not-accessible,,current,,The integer value used to identify the IEEE 802.1Q  VLAN IDs with which the given port is compatible.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVlanName,OCTET,read-only,,current,,The string value used to identify VLAN name identified by the Vlan Id associated with the given port on the  local system. This object should contain the value of the  dot1QVLANStaticName object (defined in IETF RFC 4363)  identified with the given lldpV2Xdot1LocVlanId.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.4,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtocolTable,,not-accessible,,current,,This table contains one or more rows per protocol identity information on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.4.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtocolEntry,,not-accessible,lldpV2LocPortIfIndex:lldpV2Xdot1LocProtocolIndex,current,,Information about particular protocols that are accessible through the given port component. There may be multiple protocols, identified by particular lldpV2Xdot1ProtocolIndex, lldpV2LocPortIfIndex
.1.3.111.2.802.1.1.13.1.5.32962.1.2.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtocolIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary local integer value  used by this agent to identify a particular protocol  identity.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocProtocolId,OCTET,read-only,,current,,The octet string value used to identify the protocols associated with the given port of the local system.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.5,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVidUsageDigestTable,,not-accessible,,current,,This table contains one row per ifIndex/ destination MAC address pair for usage digest information on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.5.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVidUsageDigestEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Usage digest information to be transmitted through the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocVidUsageDigest,Unsigned32,read-only,,current,,The integer value obtained by applying the CRC32 function  to the 128-octet VID Usage Table. A bit of the VID Usage  Table contains the value PBB-TE-USAGE (binary 1) if the  corresponding element of the MST Configuration Table  (IEEE Std 802.1Q 8.9.1) contains the value PBB-TE MSTID  (hex FFE) and otherwise contains the value NON-PBB-TE-USAGE  (binary 0).
.1.3.111.2.802.1.1.13.1.5.32962.1.2.6,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocManVidTable,,not-accessible,,current,,This table contains one row per ifIndex/ destination MAC address pair for usage digest information on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.6.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocManVidEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Usage digest information to be transmitted through the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.6.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocManVid,Unsigned32,read-only,,current,,The integer value configured on the Local system for  the Management VID, or the value 0 if a Management VID has not been provisioned.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.7,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocLinkAggTable,,not-accessible,,current,,This table contains one row per port of link aggregation  information (as a part of the LLDP 802.1 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.7.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocLinkAggEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Link Aggregation information about a particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.7.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocLinkAggStatus,BITS,read-only,,current,aggCapable(0):aggEnabled(1):portTypeLS(2):portTypeMS(3),The bitmap value contains the link aggregation  capabilities and the current aggregation status of the link.
.1.3.111.2.802.1.1.13.1.5.32962.1.2.7.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocLinkAggPortId,Unsigned32,read-only,,current,,This object contains the IEEE 802.1 aggregated port identifier, aAggPortID (IEEE Std 802.1AX, 6.3.2.1.1), derived from the ifNumber of the ifIndex for the port component in link aggregation. If the port is not in link aggregation state and/or it does not support link aggregation, this value should be set to zero.
.1.3.111.2.802.1.1.13.1.5.32962.1.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemoteData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemTable,,not-accessible,,current,,This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpV2Xdot1RemEntry is present for each local port, or it may choose to maintain multiple lldpV2Xdot1RemEntries for the same local port.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Information about a particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemPortVlanId,Unsigned32,read-only,,current,,The integer value used to identify the port's VLAN  identifier associated with the remote system. if the  remote system either does not know the PVID or does not  support Port-based VLAN operation, the value of  lldpV2Xdot1RemPortVlanId should be zero.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtoVlanTable,,not-accessible,,current,,This table contains one or more rows per Port and Protocol VLAN information about the remote system, received on the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtoVlanEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpV2Xdot1RemProtoVlanId,current,,Port and protocol VLAN name Information about a particular port component. There may be multiple protocol VLANs, identified by a particular lldpV2Xdot1RemProtoVlanId,  configured on the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtoVlanId,Unsigned32,not-accessible,,current,,The integer value used to identify the port and protocol VLANs associated with the given port associated with the remote system. If port and protocol VLANs are not supported on the given port associated with the remote system, or if the port is not enabled with any port and protocol VLAN, the value of lldpV2Xdot1RemProtoVlanId should be zero.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtoVlanSupported,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the given port (associated with the remote system) is capable of  supporting port and protocol VLANs.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.2.1.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtoVlanEnabled,INTEGER,read-only,,current,true(1):false(2),The truth value used to indicate whether the port and protocol VLANs are enabled on the given port associated  with the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVlanNameTable,,not-accessible,,current,,This table contains one or more rows per IEEE 802.1Q VLAN name information about the remote system, received on the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.3.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVlanNameEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpV2Xdot1RemVlanId,current,,VLAN name Information about a particular port component. There may be multiple VLANs, identified by a particular lldpV2Xdot1RemVlanId, received on the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVlanId,Integer32,not-accessible,,current,,The integer value used to identify the IEEE 802.1Q  VLAN IDs with which the given port of the remote system is compatible.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVlanName,OCTET,read-only,,current,,The string value used to identify VLAN name identified by the VLAN Id associated with the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.4,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtocolTable,,not-accessible,,current,,This table contains one or more rows per protocol  information about the remote system, received on  the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.4.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtocolEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpV2Xdot1RemProtocolIndex,current,,Protocol information about a particular port component. There may be multiple protocols, identified by a particular lldpV2Xdot1ProtocolIndex, received on the given port.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtocolIndex,Unsigned32,not-accessible,,current,,This object represents an arbitrary local integer value used by this agent to identify a particular protocol  identity.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemProtocolId,OCTET,read-only,,current,,The octet string value used to identify the protocols associated with the given port of remote system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.5,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVidUsageDigestTable,,not-accessible,,deprecated,,This table contains one row per ifIndex/ destination MAC address pair for usage digest information received by the local system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.5.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVidUsageDigestEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress,deprecated,,Usage digest information received on the given port/destination address pair.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVidUsageDigest,Unsigned32,read-only,,deprecated,,The integer value obtained by applying the CRC32 function  to the 128-octet VID Usage Table. A bit of the VID Usage  Table contains the value PBB-TE-USAGE (binary 1) if the  corresponding element of the MST Configuration Table  (IEEE Std 802.1Q 8.9.1) contains the value PBB-TE MSTID (hex FFE)and otherwise contains the value NON-PBB-TE-USAGE (binary 0).
.1.3.111.2.802.1.1.13.1.5.32962.1.3.6,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemManVidTable,,not-accessible,,deprecated,,This table contains one row per ifIndex/ destination MAC address pair for management VID information received from remote systems.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.6.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemManVidEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress,deprecated,,Management VID information received through the given port/destination address pair.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.6.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemManVid,Unsigned32,read-only,,deprecated,,The integer value configured on a system for  the Management VID, or the value 0 if a Management VID has not been provisioned.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.7,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemLinkAggTable,,not-accessible,,current,,This table contains port link aggregation information (as a part of the LLDP IEEE 802.1 organizational extension) of the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.7.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemLinkAggEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Link Aggregation information about remote system's port component.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.7.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemLinkAggStatus,BITS,read-only,,current,aggCapable(0):aggEnabled(1):portTypeLS(2):portTypeMS(3),The bitmap value contains the link aggregation capabilities and the current aggregation status of the link.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.7.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemLinkAggPortId,Unsigned32,read-only,,current,,This object contains the IEEE 802.1 aggregated port identifier, aAggPortID (IEEE Std 802.1AX, 6.3.2.1.1), derived from the ifNumber of the ifIndex for the port component associated with the remote system. If the remote port is not in link aggregation state and/or it does not support link aggregation, this value should be zero.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.8,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVidUsageDigestV2Table,,not-accessible,,current,,This table contains one row per ifIndex/ destination MAC address pair for usage digest information received by the local system.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.8.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVidUsageDigestV2Entry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Usage digest information received on the given port/destination address pair.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.8.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemVidUsageDigestV2,Unsigned32,read-only,,current,,The integer value obtained by applying the CRC32 function  to the 128-octet VID Usage Table. A bit of the VID Usage  Table contains the value PBB-TE-USAGE (binary 1) if the  corresponding element of the MST Configuration Table  (IEEE Std 802.1Q 8.9.1) contains the value PBB-TE MSTID (hex FFE)and otherwise contains the value NON-PBB-TE-USAGE (binary 0).
.1.3.111.2.802.1.1.13.1.5.32962.1.3.9,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemManVidV2Table,,not-accessible,,current,,This table contains one row per ifIndex/ destination MAC address pair for management VID information received from remote systems.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.9.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemManVidV2Entry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Management VID information received through the given port/destination address pair.
.1.3.111.2.802.1.1.13.1.5.32962.1.3.9.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemManVidV2,Unsigned32,read-only,,current,,The integer value configured on a system for  the Management VID, or the value 0 if a Management VID has not been provisioned.
.1.3.111.2.802.1.1.13.1.5.32962.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1Conformance,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1Compliances,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1TxRxCompliance,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined LLDP extension MIB. This group is mandatory for all agents that implement the  LLDP 802.1 organizational extension in TX and/or RX mode for the basicSet TLV set. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.32962.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1TxCompliance,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined LLDP extension MIB. This group is mandatory for agents that implement the  LLDP 802.1 organizational extension in the RX mode for the basicSet TLV set. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.32962.2.1.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RxCompliance,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined LLDP extension MIB. This group is mandatory for agents that implement the  LLDP 802.1 organizational extension in the RX mode for the basicSet TLV set. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.32962.2.1.4,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RxComplianceV2,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined LLDP extension MIB. This group is mandatory for agents that implement the  LLDP 802.1 organizational extension in the RX mode for the basicSet TLV set. This version defines compliance requirements for V2 of the LLDP MIB.
.1.3.111.2.802.1.1.13.1.5.32962.2.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1Groups,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.2.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1ConfigGroup,,,,,,The collection of objects which are used to configure the IEEE 802.1 organizationally defined LLDP extension implementation behavior for the basicSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.2.2.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocSysGroup,,,,,,The collection of objects which are used to represent  IEEE 802.1 organizationally defined LLDP extension  associated with the Local Device Information for the  basicSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.2.2.3,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemSysGroup,,,,,,The collection of objects which are used to represent LLDP 802.1 organizational extension Remote Device Information for the basicSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.2.2.4,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemSysV2Group,,,,,,The collection of objects which are used to represent LLDP 802.1 organizational extension Remote Device Information for the basicSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnMIB,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnObjects,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnConfig,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnConfigCnTable,,not-accessible,,current,,A table that controls selection of Congestion Notification TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnConfigCnEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  Congestion Notification TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnConfigCnTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1CnConfigCnTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally defined Congestion Notification TLV transmission is allowed  on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnLocalData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.3.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocCnTable,,not-accessible,,current,,This table contains one row per port of Congestion Notification information (as a part of the LLDP  802.1 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocCnEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Congestion Notification information about a  particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.2.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocCNPVIndicators,BITS,read-only,,current,pri0status(0):pri1status(1):pri2status(2):pri3status(3):pri4status(4):pri5status(5):pri6status(6):pri7status(7),This object contains the CNPV indicators for the Port.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.2.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1LocReadyIndicators,BITS,read-only,,current,pri0status(0):pri1status(1):pri2status(2):pri3status(3):pri4status(4):pri5status(5):pri6status(6):pri7status(7),This object contains the Ready indicators for the Port.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnRemoteData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.3.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemCnTable,,not-accessible,,current,,This table contains Congestion Notification information (as a part of the LLDP IEEE 802.1 organizational extension) of the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemCnEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Port Extension information about remote systems port component.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemCNPVIndicators,BITS,read-only,,current,pri0status(0):pri1status(1):pri2status(2):pri3status(3):pri4status(4):pri5status(5):pri6status(6):pri7status(7),This object contains the CNPV indicators for the Port.
.1.3.111.2.802.1.1.13.1.5.32962.3.1.3.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpV2Xdot1RemReadyIndicators,BITS,read-only,,current,pri0status(0):pri1status(1):pri2status(2):pri3status(3):pri4status(4):pri5status(5):pri6status(6):pri7status(7),This object contains the Ready indicators for the Port.
.1.3.111.2.802.1.1.13.1.5.32962.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnConformance,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnCompliances,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnCompliance,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined Congestion Notification LLDP extension MIB. This group is mandatory for agents that implement the  Congestion Notification cnSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.4.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnGroups,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.4.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1CnGroup,,,,,,The collection of objects that support the Congestion Notification cnSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.5,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxMIB,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxObjects,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfig,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigETSConfigurationTable,,not-accessible,,current,,A table that controls selection of ETS Configuration TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigETSConfigurationEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  ETS Configuration TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigETSConfigurationTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1dcbxConfigETSConfigurationTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally defined ETS Configuration TLV transmission is allowed on a  given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigETSRecommendationTable,,not-accessible,,current,,A table that controls selection of ETS Recommendation TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigETSRecommendationEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  ETS Recommendation TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigETSRecommendationTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1dcbxConfigETSRecommendationTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally  defined ETS Recommendation TLV transmission is allowed on a  given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigPFCTable,,not-accessible,,current,,A table that controls selection of Priority-based Flow Control Configuration TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigPFCEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  Priority-based Flow Control Configuration TLV on LLDP  transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigPFCTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1dcbxConfigPFCTxEnable, which is defined as a truth value and configured by the network management, determines whether the IEEE 802.1 organizationally defined Priority-based Flow Control Configuration TLV transmission is allowed on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigApplicationPriorityTable,,not-accessible,,current,,A table that controls selection of Priority-based Flow Control Configuration TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigApplicationPriorityEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  Application Priority TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigApplicationPriorityTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1dcbxConfigApplicationPriorityTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally defined Application Priority TLV transmission is allowed on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.5,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigApplicationVlanTable,,not-accessible,,current,,A table that controls selection of Application VLAN TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.5.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigApplicationVlanEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  Application VLAN TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.1.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConfigApplicationVlanTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1dcbxConfigApplicationVlanTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally defined Application VLAN TLV transmission is allowed on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocalData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConfiguration,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSBasicConfigurationTable,,not-accessible,,current,,This table contains one row per port for the IEEE 802.1 organizationally defined LLDP ETS Configuration TLV on the local system known to this agent
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSBasicConfigurationEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about the IEEE 802.1 organizational defined ETS Configuration TLV LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConCreditBasedShaperSupport,INTEGER,read-only,,current,true(1):false(2),Indicates if the credit-based shaper Traffic Selection Algorithm is supported on the local system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficClassesSupported,Unsigned32,read-only,,current,,Indicates the number of traffic classes supported.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConWilling,INTEGER,read-only,,current,true(1):false(2),Indicates if the local system is willing to accept the ETS configuration recommended by the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConPriorityAssignmentTable,,not-accessible,,current,,This table contains one row per priority. The entry in each row indicates the traffic class to which the priority is  assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConPriorityAssignmentEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocETSConPriority,current,,Indicates a priority to traffic class assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConPriority,Unsigned32,not-accessible,,current,,Indicates the priority that is assigned to a traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConPriTrafficClass,Unsigned32,read-only,,current,,Indicates the traffic class to which this priority is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficClassBandwidthTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic class to  which the bandwidth is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficClassBandwidthEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocETSConTrafficClass,current,,Indicates a traffic class to Bandwidth assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficClassBandwidth,Unsigned32,read-only,,current,,Indicates the bandwidth assigned to this traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficSelectionAlgorithmTable,,not-accessible,,current,,This table contains one row per traffic class. The entry in each row indicates the traffic selction algorithm to be used by the traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficSelectionAlgorithmEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocETSConTSATrafficClass,current,,Indicates a traffic class to traffic selection algorithm assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTSATrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class that is assigned to a traffic  selection algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.1.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSConTrafficSelectionAlgorithm,INTEGER,read-only,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Indicates the Traffic Selection Algorithm to which this traffic class is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSReco,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficClassBandwidthTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic class to  which the bandwidth is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficClassBandwidthEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocETSRecoTrafficClass,current,,Indicates a traffic class to Bandwidth assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficClassBandwidth,Unsigned32,read-only,,current,,Indicates the bandwidth assigned to this traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficSelectionAlgorithmTable,,not-accessible,,current,,This table contains one row per priority. The entry in each row indicates the traffic selction algorithm to be used by the traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficSelectionAlgorithmEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocETSRecoTSATrafficClass,current,,Indicates a priority to traffic selection algorithm assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTSATrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class that is assigned to a traffic  selection algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.2.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocETSRecoTrafficSelectionAlgorithm,INTEGER,read-only,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Indicates the Traffic Selection Algorithm to which this traffic class is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFC,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCBasicTable,,not-accessible,,current,,This table contains one row per port for the IEEE 802.1 organizationally defined LLDP PFC TLV on the local system known to this agent
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCBasicEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about the IEEE 802.1 organizational defined PFC TLV LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCWilling,INTEGER,read-only,,current,true(1):false(2),Indicates if the local system is willing to accept the  PFC configuration of the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCMBC,INTEGER,read-only,,current,true(1):false(2),Indicates if the local system is capable of bypassing MACsec processing when MACsec is disabled.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCCap,Unsigned32,read-only,,current,,Indicates the number of traffic classes on the local device that may simultaneously have PFC enabled.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCEnableTable,,not-accessible,,current,,This table contains eight entries, one entry per priority, indicating if PFC is enabled on the corresponding priority.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCEnableEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocPFCEnablePriority,current,,Each entry indicates if PFC is enabled on the  correponding priority
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCEnablePriority,Unsigned32,not-accessible,,current,,Prioity for which PFC is enabled / disabled
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.3.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocPFCEnableEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates if PFC is enabled on the corresponding priority
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationPriorityAppTable,,not-accessible,,current,,Table containing entries indicating the priorty to be used for a given application
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationPriorityAppEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocApplicationPriorityAESelector:lldpXdot1dcbxLocApplicationPriorityAEProtocol,current,,Entry that indicates the priority to be used for a given application.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationPriorityAESelector,INTEGER,not-accessible,,current,asEthertype(1):asTCPPortNumber(2):asUDPPortNumber(3):asTCPUDPPortNumber(4):asDSCPValue(5),Indicates the contents of the protocol object (lldpXdot1dcbxLocApplicationPriorityAEProtocol) 1: Ethertype 2: Well Known Port number over TCP, or SCTP 3: Well Known Port number over UDP, or DCCP 4: Well Known Port number over TCP, SCTP, UDP, and DCCP 5: Differentiated Services Code Point (DSCP) value. The 6 bit DSCP value is stored in the low order 6 bits of the  protocol object. The higher order bits are set to zero. (See IETF RFC 2474 for the definition of the DSCP value.)
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationPriorityAEProtocol,Unsigned32,not-accessible,,current,,The protocol indicator of the type indicated by lldpXdot1dcbxLocApplicationPriorityAESelector.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.4.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationPriorityAEPriority,Unsigned32,read-only,,current,,The priority code point that should be used in frames transporting the protocol indicated by lldpXdot1dcbxLocApplicationPriorityAESelector and lldpXdot1dcbxLocApplicationPriorityAEProtocol
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.5,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationVlanAppTable,,not-accessible,,current,,Table containing entries indicating the VLAN to be used for a given application
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.5.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationVlanAppEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxLocApplicationVlanAESelector:lldpXdot1dcbxLocApplicationVlanAEProtocol,current,,Entry that indicates the VLAN to be used for a given application.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationVlanAESelector,INTEGER,not-accessible,,current,asEthertype(1):asTCPPortNumber(2):asUDPPortNumber(3):asTCPUDPPortNumber(4):asDSCPValue(5),Indicates the contents of the protocol object (lldpXdot1dcbxLocApplicationVlanAEProtocol) 1: Ethertype 2: Well Known Port number over TCP, or SCTP 3: Well Known Port number over UDP, or DCCP 4: Well Known Port number over TCP, SCTP, UDP, and DCCP 5: Differentiated Services Code Point (DSCP) value. The 6 bit DSCP value is stored in the low order 6 bits of the  protocol object. The higher order bits are set to zero. (See IETF RFC 2474 for the definition of the DSCP value.)
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.5.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationVlanAEProtocol,Unsigned32,not-accessible,,current,,The protocol indicator of the type indicated by lldpXdot1dcbxLocApplicationVlanAESelector.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.2.5.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxLocApplicationVlanAEVlanId,Integer32,read-only,,current,,The VLAN Identifier that should be used in frames transporting the protocol indicated by lldpXdot1dcbxLocApplicationVlanAESelector and lldpXdot1dcbxLocApplicationVlanAEProtocol
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemoteData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConfiguration,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSBasicConfigurationTable,,not-accessible,,current,,This table contains one row per port for the IEEE 802.1 organizationally defined LLDP ETS Configuration TLV on the local system known to this agent
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSBasicConfigurationEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Information about the IEEE 802.1 organizational defined ETS Configuration TLV LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConCreditBasedShaperSupport,INTEGER,read-only,,current,true(1):false(2),Indicates if the credit-based shaper Traffic Selection algorithm is supported on the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficClassesSupported,Unsigned32,read-only,,current,,Indicates the number of traffic classes supported.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConWilling,INTEGER,read-only,,current,true(1):false(2),Indicates if the remote system is willing to accept the ETS configuration recommended by the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConPriorityAssignmentTable,,not-accessible,,current,,This table contains one row per priority. The entry in  each row indicates the traffic class to which the  priority is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConPriorityAssignmentEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemETSConPriority,current,,Indicates a priority to traffic class assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConPriority,Unsigned32,not-accessible,,current,,Indicates the priority that is assigned to a traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConPriTrafficClass,Unsigned32,read-only,,current,,Indicates the traffic class to which this priority is  to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficClassBandwidthTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic class to  which the bandwidth is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficClassBandwidthEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemETSConTrafficClass,current,,Indicates a traffic class to Bandwidth assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficClassBandwidth,Unsigned32,read-only,,current,,Indicates the bandwidth assigned to this traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficSelectionAlgorithmTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic selction algorithm to be used by the traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficSelectionAlgorithmEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemETSConTSATrafficClass,current,,Indicates a traffic class to traffic selection algorithm assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTSATrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class that is assigned to a traffic  selection algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.1.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSConTrafficSelectionAlgorithm,INTEGER,read-only,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Indicates the Traffic Selection Algorithm to which this traffic class is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSReco,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficClassBandwidthTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic class to  which the bandwidth is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficClassBandwidthEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemETSRecoTrafficClass,current,,Indicates a traffic class to Bandwidth assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficClassBandwidth,Unsigned32,read-only,,current,,Indicates the bandwidth assigned to this traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficSelectionAlgorithmTable,,not-accessible,,current,,This table contains one row per traffic class. The entry in each row indicates the traffic selction  algorithm to be used by the priority.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficSelectionAlgorithmEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemETSRecoTSATrafficClass,current,,Indicates a priority to traffic selection algorithm assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTSATrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class that is assigned to a traffic  selection algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.2.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemETSRecoTrafficSelectionAlgorithm,INTEGER,read-only,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Indicates the Traffic Selection Algorithm to which this traffic class is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFC,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCBasicTable,,not-accessible,,current,,This table contains one row per port for the IEEE 802.1 organizationally defined LLDP PFC TLV on the local system known to this agent
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCBasicEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Information about the IEEE 802.1 organizational defined PFC TLV LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCWilling,INTEGER,read-only,,current,true(1):false(2),Indicates if the remote system is willing to accept the  PFC configuration of the local system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCMBC,INTEGER,read-only,,current,true(1):false(2),Indicates if the remote system is capable of bypassing MACsec processing when MACsec is disabled.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCCap,Unsigned32,read-only,,current,,Indicates the number of traffic classes on the remote device that may simultaneously have PFC enabled.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCEnableTable,,not-accessible,,current,,This table contains eight entries, one entry per priority, indicating if PFC is enabled on the corresponding priority.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCEnableEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemPFCEnablePriority,current,,Each entry indicates if PFC is enabled on the  correponding priority
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCEnablePriority,Unsigned32,not-accessible,,current,,Prioity for which PFC is enabled / disabled
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.3.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemPFCEnableEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates if PFC is enabled on the corresponding priority
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationPriorityAppTable,,not-accessible,,current,,Table containing entries indicating the priorty to be used for a given application
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationPriorityAppEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemApplicationPriorityAESelector:lldpXdot1dcbxRemApplicationPriorityAEProtocol,current,,Entry that indicates the priority to be used for a given application.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationPriorityAESelector,INTEGER,not-accessible,,current,asEthertype(1):asTCPPortNumber(2):asUDPPortNumber(3):asTCPUDPPortNumber(4):asDSCPValue(5),Indicates the contents of the protocol object (lldpXdot1dcbxRemApplicationPriorityAEProtocol) 1: Ethertype 2: Well Known Port number over TCP, or SCTP 3: Well Known Port number over UDP, or DCCP 4: Well Known Port number over TCP, SCTP, UDP, and DCCP 5: Differentiated Services Code Point (DSCP) value. The 6 bit DSCP value is stored in the low order 6 bits of the  protocol object. The higher order bits are set to zero. (See IETF RFC 2474 for the definition of the DSCP value.)
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationPriorityAEProtocol,Unsigned32,not-accessible,,current,,The protocol indicator of the type indicated by lldpXdot1dcbxRemApplicationPriorityAESelector.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.4.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationPriorityAEPriority,Unsigned32,read-only,,current,,The priority code point that should be used in frames transporting the protocol indicated by lldpXdot1dcbxRemApplicationPriorityAESelector and lldpXdot1dcbxRemApplicationPriorityAEProtocol
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.5,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationVlanAppTable,,not-accessible,,current,,Table containing entries indicating the VLAN to be used for a given application
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.5.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationVlanAppEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex:lldpXdot1dcbxRemApplicationVlanAESelector:lldpXdot1dcbxRemApplicationVlanAEProtocol,current,,Entry that indicates the VLAN to be used for a given application.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationVlanAESelector,INTEGER,not-accessible,,current,asEthertype(1):asTCPPortNumber(2):asUDPPortNumber(3):asTCPUDPPortNumber(4):asDSCPValue(5),Indicates the contents of the protocol object (lldpXdot1dcbxRemApplicationVlanAEProtocol) 1: Ethertype 2: Well Known Port number over TCP, or SCTP 3: Well Known Port number over UDP, or DCCP 4: Well Known Port number over TCP, SCTP, UDP, and DCCP 5: Differentiated Services Code Point (DSCP) value. The 6 bit DSCP value is stored in the low order 6 bits of the  protocol object. The higher order bits are set to zero. (See IETF RFC 2474 for the definition of the DSCP value.)
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.5.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationVlanAEProtocol,Unsigned32,not-accessible,,current,,The protocol indicator of the type indicated by lldpXdot1dcbxRemApplicationVlanAESelector.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.3.5.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxRemApplicationVlanAEVlanId,Integer32,read-only,,current,,The VLAN Identifier that should be used in frames transporting the protocol indicated by lldpXdot1dcbxRemApplicationVlanAESelector and lldpXdot1dcbxRemApplicationVlanAEProtocol
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConfiguration,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSBasicConfigurationTable,,not-accessible,,current,,This table contains one row per port for the IEEE 802.1 organizationally defined LLDP ETS Configuration TLV on the local system known to this agent
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSBasicConfigurationEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about the IEEE 802.1 organizational defined ETS Configuration TLV LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConCreditBasedShaperSupport,INTEGER,read-only,,current,true(1):false(2),Indicates support for the credit-based shaper Traffic Selection Algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficClassesSupported,Unsigned32,read-only,,current,,Indicates the number of traffic classes supported.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConWilling,INTEGER,read-write,,current,true(1):false(2),Indicates if the local system is willing to accept the ETS configuration recommended by the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConPriorityAssignmentTable,,not-accessible,,current,,This table contains one row per priority. The entry in each row indicates the traffic class to which the priority is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConPriorityAssignmentEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminETSConPriority,current,,Indicates a priority to traffic class assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConPriority,Unsigned32,not-accessible,,current,,Indicates the priority that is assigned to a traffic  class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConPriTrafficClass,Unsigned32,read-write,,current,,Indicates the traffic class to which this priority is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficClassBandwidthTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic class to  which the bandwidth is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficClassBandwidthEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminETSConTrafficClass,current,,Indicates a traffic class to Bandwidth assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.3.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficClassBandwidth,Unsigned32,read-write,,current,,Indicates the bandwidth assigned to this traffic class. The sum of the bandwidths assigned to a given port is required at all times to eqaul 100. An operation that attempts to change this table such that the bandwidth entires do not total 100 shall be rejected. An implication of this is that modification of this table requires that multiple set operations be included in a single SNMP PDU, commonly referred to as an MSET operation, to perform simultaneous set operations to keep the sum at 100. Any attempt to change a single entry in this table will result in the operation being rejected since entries in the  table referring to the given port will no longer  sum to 100.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficSelectionAlgorithmTable,,not-accessible,,current,,This table contains one row per traffic class. The entry in each row indicates the traffic selction algorithm to be used by the priority.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficSelectionAlgorithmEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminETSConTSATrafficClass,current,,Indicates a traffic class to traffic selection algorithm assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTSATrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class that is assigned to a traffic selection algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.1.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSConTrafficSelectionAlgorithm,INTEGER,read-write,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Indicates the Traffic Selection Algorithm to which this traffic class is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSReco,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficClassBandwidthTable,,not-accessible,,current,,This table contains one row per traffic class. The  entry in each row indicates the traffic class to  which the bandwidth is assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficClassBandwidthEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminETSRecoTrafficClass,current,,Indicates a traffic class to Bandwidth assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficClassBandwidth,Unsigned32,read-write,,current,,Indicates the bandwidth assigned to this traffic class. The sum of the bandwidths assigned to a given port is required at all times to eqaul 100. An operation that attempts to change this table such that the bandwidth entires do not total 100 shall be rejected. An implication of this is that modification of this table requires that multiple set operations be included in a single SNMP PDU, commonly referred to as an MSET operation, to perform simultaneous set operations to keep the sum at 100. Any attempt to change a single entry in this table will result in the operation being rejected since entries in the  table referring to the given port will no longer  sum to 100.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficSelectionAlgorithmTable,,not-accessible,,current,,This table contains one row per traffic class. The entry in each row indicates the traffic selction algorithm to  be used by the traffic class.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficSelectionAlgorithmEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminETSRecoTSATrafficClass,current,,Indicates a traffic class to traffic selection algorithm assignment.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTSATrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class that is assigned to a traffic  selection algorithm.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.2.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminETSRecoTrafficSelectionAlgorithm,INTEGER,read-write,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Indicates the Traffic Selection Algorithm to which this traffic class is to be assigned.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFC,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCBasicTable,,not-accessible,,current,,This table contains one row per port for the IEEE 802.1 organizationally defined LLDP PFC TLV on the local system known to this agent
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCBasicEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Information about the IEEE 802.1 organizational defined PFC TLV LLDP extension.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.1.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCWilling,INTEGER,read-write,,current,true(1):false(2),Indicates if the local system is willing to accept the  PFC configuration of the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.1.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCMBC,INTEGER,read-only,,current,true(1):false(2),Indicates if the local system is capable of bypassing MACsec processing when MACsec is disabled.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.1.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCCap,Unsigned32,read-only,,current,,Indicates the number of traffic classes on the local device that may simultaneously have PFC enabled.  Note that this typically indicates a physical limitation of the device. However, some devices may allow this parameter to be administratively configured, in which case the MAX-ACCESS should be changed to read-write with and an appropriate DEFVAL added.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCEnableTable,,not-accessible,,current,,This table contains eight entries, one entry per priority, indicating if PFC is enabled on the corresponding priority.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCEnableEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminPFCEnablePriority,current,,Each entry indicates if PFC is enabled on the  correponding priority
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.2.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCEnablePriority,Unsigned32,not-accessible,,current,,Prioity for which PFC is enabled / disabled
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.3.2.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminPFCEnableEnabled,INTEGER,read-write,,current,true(1):false(2),Indicates if PFC is enabled on the corresponding priority
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationPriorityAppTable,,not-accessible,,current,,Table containing entries indicating the priorty to be used for a given application
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.4.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationPriorityAppEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminApplicationPriorityAESelector:lldpXdot1dcbxAdminApplicationPriorityAEProtocol,current,,Entry that indicates the priority to be used for a given application.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.4.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationPriorityAESelector,INTEGER,not-accessible,,current,asEthertype(1):asTCPPortNumber(2):asUDPPortNumber(3):asTCPUDPPortNumber(4):asDSCPValue(5),Indicates the contents of the protocol object (lldpXdot1dcbxAdminApplicationPriorityAEProtocol) 1: Ethertype 2: Well Known Port number over TCP, or SCTP 3: Well Known Port number over UDP, or DCCP 4: Well Known Port number over TCP, SCTP, UDP, and DCCP 5: Differentiated Services Code Point (DSCP) value. The 6 bit DSCP value is stored in the low order 6 bits of the  protocol object. The higher order bits are set to zero. (See IETF RFC 2474 for the definition of the DSCP value.)
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.4.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationPriorityAEProtocol,Unsigned32,not-accessible,,current,,The protocol indicator of the type indicated by lldpXdot1dcbxAdminApplicationPriorityAESelector.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.4.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationPriorityAEPriority,Unsigned32,read-create,,current,,The priority code point that should be used in frames transporting the protocol indicated by lldpXdot1dcbxAdminApplicationPriorityAESelector and lldpXdot1dcbxAdminApplicationPriorityAEProtocol
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.5,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationVlanAppTable,,not-accessible,,current,,Table containing entries indicating the VLAN to be used for a given application
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.5.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationVlanAppEntry,,not-accessible,lldpV2LocPortIfIndex:lldpXdot1dcbxAdminApplicationVlanAESelector:lldpXdot1dcbxAdminApplicationVlanAEProtocol,current,,Entry that indicates the VLAN to be used for a given application.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.5.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationVlanAESelector,INTEGER,not-accessible,,current,asEthertype(1):asTCPPortNumber(2):asUDPPortNumber(3):asTCPUDPPortNumber(4):asDSCPValue(5),Indicates the contents of the protocol object (lldpXdot1dcbxAdminApplicationVlanAEProtocol) 1: Ethertype 2: Well Known Port number over TCP, or SCTP 3: Well Known Port number over UDP, or DCCP 4: Well Known Port number over TCP, SCTP, UDP, and DCCP 5: Differentiated Services Code Point (DSCP) value. The 6 bit DSCP value is stored in the low order 6 bits of the  protocol object. The higher order bits are set to zero. (See IETF RFC 2474 for the definition of the DSCP value.)
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.5.1.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationVlanAEProtocol,Unsigned32,not-accessible,,current,,The protocol indicator of the type indicated by lldpXdot1dcbxAdminApplicationVlanAESelector.
.1.3.111.2.802.1.1.13.1.5.32962.5.1.4.5.1.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxAdminApplicationVlanAEVlanId,Integer32,read-create,,current,,The VLAN Identifier that should be used in frames transporting the protocol indicated by lldpXdot1dcbxAdminApplicationVlanAESelector and lldpXdot1dcbxAdminApplicationVlanAEProtocol
.1.3.111.2.802.1.1.13.1.5.32962.6,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxConformance,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.6.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxCompliances,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.6.1.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxCompliance,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined DCBX LLDP  extension MIB. This group is mandatory for agents which implement Enhanced Transmission Selection.
.1.3.111.2.802.1.1.13.1.5.32962.6.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxGroups,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.6.2.1,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxETSGroup,,,,,,The collection of objects used for Enhanced Transmission Selection.
.1.3.111.2.802.1.1.13.1.5.32962.6.2.2,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxPFCGroup,,,,,,The collection of objects used for Priority- base Flow Control.
.1.3.111.2.802.1.1.13.1.5.32962.6.2.3,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxApplicationPriorityGroup,,,,,,The collection of objects used for Application priority.
.1.3.111.2.802.1.1.13.1.5.32962.6.2.4,LLDP-EXT-DOT1-V2-MIB::lldpXdot1dcbxApplicationVlanGroup,,,,,,The collection of objects used for Application VLAN.
.1.3.111.2.802.1.1.13.1.5.32962.7,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1StandAloneExtensions,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXDot1EvbExtensions,,,,,,The LLDP Management Information Base extension module for IEEE 802.1 organizationally defined discovery information for the EVB extension objects. This MIB module is rooted under the lldpXdot1StandAloneExtensions OID arc, in order to allow it to be defined independently of other 802.1 LLDP extension MIBs. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is published as D.5.6 of IEEE Std 802.1Q; see the standard itself for full legal notices.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbMIB,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbObjects,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfig,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfigEvbTable,,not-accessible,,current,,A table that controls selection of EVB TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfigEvbEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  EVB TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfigEvbTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1EvbConfigEvbTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally defined EVB TLV transmission is allowed  on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1.2,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfigCdcpTable,,not-accessible,,current,,A table that controls selection of EVB TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1.2.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfigCdcpEntry,,not-accessible,,current,,LLDP configuration information that controls the transmission of IEEE 802.1 organizationally defined  CDCP TLV on LLDP transmission-capable ports. This configuration object augments the lldpV2PortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpV2PortConfigEntry entry. Each active lldpConfigEntry is restored from non-volatile storage (along with the corresponding lldpV2PortConfigEntry) after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.1.2.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConfigCdcpTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1EvbConfigCdcpTxEnable, which is defined as a truth value and configured by the network  management, determines whether the IEEE 802.1 organizationally defined CDCP TLV transmission is allowed  on a given LLDP transmission-capable port. The value of this object is restored from non-volatile storage after a re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbLocalData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1LocEvbTlvTable,,not-accessible,,current,,This table contains one row per port of EVB TLV information (as a part of the LLDP  802.1 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1LocEvbTlvEntry,,not-accessible,lldpV2LocPortIfIndex,current,,EVB TLV information about a  particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1LocEvbTlvString,OCTET,read-only,,current,,This object contains the EVB TLV information string  for the Port, as defined in D.2.13. As the elements within the string are not individually manipulated via SNMP (they are of concern only to the state machines), the sub-structure of the string is not visible as separate objects within the local database.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2.2,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1LocCdcpTlvTable,,not-accessible,,current,,This table contains one row per port of CDCP TLV information (as a part of the LLDP  802.1 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2.2.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1LocCdcpTlvEntry,,not-accessible,lldpV2LocPortIfIndex,current,,CDCP TLV information about a  particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.2.2.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1LocCdcpTlvString,OCTET,read-only,,current,,This object contains the CDCP TLV information string  for the Port, as defined in D.2.14. As the elements within the string are not individually manipulated via SNMP (they are of concern only to the state machines), the sub-structure of the string is not visible as separate objects within the local database.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbRemoteData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1RemEvbTlvTable,,not-accessible,,current,,This table contains one row per port of EVB TLV information (as a part of the LLDP  802.1 organizational extension) on the remote system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1RemEvbTlvEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,EVB TLV information about a  particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3.1.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1RemEvbTlvString,OCTET,read-only,,current,,This object contains the EVB TLV information string  for the Port, as defined in D.2.13. As the elements within the string are not individually manipulated via SNMP (they are of concern only to the state machines), the sub-structure of the string is not visible as separate objects within the local database.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3.2,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1RemCdcpTlvTable,,not-accessible,,current,,This table contains one row per port of CDCP TLV information (as a part of the LLDP  802.1 organizational extension) on the remote system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3.2.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1RemCdcpTlvEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,CDCP TLV information about a  particular port component.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.1.1.3.2.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpV2Xdot1RemCdcpTlvString,OCTET,read-only,,current,,This object contains the CDCP TLV information string  for the Port, as defined in D.2.14. As the elements within the string are not individually manipulated via SNMP (they are of concern only to the state machines), the sub-structure of the string is not visible as separate objects within the local database.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.2,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbConformance,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.2.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbCompliances,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.2.1.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbCompliance,,,,,,A compliance statement for SNMP entities that implement the IEEE 802.1 organizationally defined Congestion Notification LLDP extension MIB. This group is mandatory for agents that implement the  EVB evbSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.7.1.2.2,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbGroups,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.1.2.2.1,LLDP-EXT-DOT1-EVB-EXTENSIONS-MIB::lldpXdot1EvbGroup,,,,,,The collection of objects that support the EVB evbSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.7.2,LLDP-EXT-DOT1-PE-MIB::lldpXDot1PEExtensions,,,,,,The LLDP Management Information Base extension module for IEEE 802.1 organizationally defined discovery information  to support Port Extension. This MIB module is rooted under the  lldpXdot1StandAloneExtensions OID arc, in order to allow  it to be defined independently of other 802.1 LLDP  extension MIBs. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1BR-2012. Copyright (C) IEEE. This version of this MIB module is published as Annex B.5 of IEEE Std 802.1BR-2012; see the standard itself for full legal notices.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeMIB,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeObjects,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeConfig,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeConfigPortExtensionTable,,not-accessible,,current,,A table that controls selection of LLDP Port Extension  TLVs to be transmitted on individual ports.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.1.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeConfigPortExtensionEntry,,not-accessible,,current,,LLDP configuration information that specifies Port Exension configuration. This configuration object augments the  lldpV2Xdot1LocPortExtensionEntry, therefore it is only present along with the associated  lldpV2Xdot1LocPortExtensionEntry entry.  Each active lldpV2Xdot1ConfigPortExensionEntry must be restored from non-volatile storage (along with the corresponding lldpV2Xdot1LocPortExtensionEntry) after a  re-initialization of the management system.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.1.1.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeConfigPortExtensionTxEnable,INTEGER,read-write,,current,true(1):false(2),The lldpXdot1PeConfigPortExtensionTxEnable, which is defined as a truth value and configured by the network management, determines whether the IEEE 802.1  organizationally defined Port Extension TLV transmission is allowed on a given LLDP transmission capable port.  The value of this object must be restored from non-volatile storage after a re-initialization of the  management system.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.2,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeLocalData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.2.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeLocPortExtensionTable,,not-accessible,,current,,This table contains one row per port of Port Extension information (as a part of the LLDP 802.1 organizational extension) on the local system known to this agent.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.2.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeLocPortExtensionEntry,,not-accessible,lldpV2LocPortIfIndex,current,,Port Extension information about a particular  Port Extender Port.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.2.1.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeLocPECascadePortPriority,Unsigned32,read-write,,current,,Contains the cascade port priority.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.2.1.1.2,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeLocPEAddress,OCTET,read-only,,current,,This object contains the MAC address that uniquely identifies the Port Extender.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.2.1.1.3,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeLocPECSPAddress,OCTET,read-only,,current,,This object contains the MAC address to be used for the Port Extension control and status protocol.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.3,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeRemoteData,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.3.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeRemPortExtensionTable,,not-accessible,,current,,This table contains Port Extension information (as a part of the LLDP IEEE 802.1 organizational extension) of the remote system.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.3.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeRemPortExtensionEntry,,not-accessible,lldpV2RemTimeMark:lldpV2RemLocalIfIndex:lldpV2RemLocalDestMACAddress:lldpV2RemIndex,current,,Port Extension information about remote systems port component.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.3.1.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeRemPECascadePortPriority,Unsigned32,read-only,,current,,The cascade port priority.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.3.1.1.2,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeRemPEAddress,OCTET,read-only,,current,,This object contains the MAC address that uniquely identifies the Port Extender.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.1.1.3.1.1.3,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeRemPECSPAddress,OCTET,read-only,,current,,This object contains the MAC address to be used for the Port Extension Control and Status Protocol.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.2,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeConformance,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.2.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeCompliances,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.2.1.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeCompliance,,,,,,A compliance statement for entities that implement the IEEE 802.1 organizationally defined Port Extension LLDP extension MIB. This group is mandatory for agents that implement the  Port Extension peSet TLV set.
.1.3.111.2.802.1.1.13.1.5.32962.7.2.2.2,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeGroups,,,,,,
.1.3.111.2.802.1.1.13.1.5.32962.7.2.2.2.1,LLDP-EXT-DOT1-PE-MIB::lldpXdot1PeGroup,,,,,,The collection of objects that support the Port Extension peSet TLV set.
.1.3.111.2.802.1.1.13.2,LLDP-V2-MIB::lldpV2Conformance,,,,,,
.1.3.111.2.802.1.1.13.2.1,LLDP-V2-MIB::lldpV2Compliances,,,,,,
.1.3.111.2.802.1.1.13.2.1.1,LLDP-V2-MIB::lldpV2TxRxCompliance,,,,,,A compliance statement for all SNMP entities that  implement the LLDP MIB as either a transmitter or  a receiver of LLDPDUs. This version defines compliance requirements for V2 of the LLDP MIB module.
.1.3.111.2.802.1.1.13.2.1.2,LLDP-V2-MIB::lldpV2TxCompliance,,,,,,A compliance statement for SNMP entities that implement the LLDP MIB and have the capability of transmitting LLDP frames. This version defines compliance requirements for V2 of the LLDP MIB module.
.1.3.111.2.802.1.1.13.2.1.3,LLDP-V2-MIB::lldpV2RxCompliance,,,,,,The compliance statement for SNMP entities that implement the LLDP MIB and have the capability of receiving LLDP frames. This version defines compliance requirements for V2 of the LLDP MIB module.
.1.3.111.2.802.1.1.13.2.2,LLDP-V2-MIB::lldpV2Groups,,,,,,
.1.3.111.2.802.1.1.13.2.2.1,LLDP-V2-MIB::lldpV2ConfigGroup,,,,,,The collection of objects that are used to configure the LLDP implementation behavior.
.1.3.111.2.802.1.1.13.2.2.2,LLDP-V2-MIB::lldpV2ConfigRxGroup,,,,,,The collection of objects that are used to configure the LLDP reception implementation behavior.
.1.3.111.2.802.1.1.13.2.2.3,LLDP-V2-MIB::lldpV2ConfigTxGroup,,,,,,The collection of objects that are used to configure the LLDP transmission implementation behavior.
.1.3.111.2.802.1.1.13.2.2.4,LLDP-V2-MIB::lldpV2StatsRxGroup,,,,,,The collection of objects that are used to represent LLDP reception statistics.
.1.3.111.2.802.1.1.13.2.2.5,LLDP-V2-MIB::lldpV2StatsTxGroup,,,,,,The collection of objects that are used to represent LLDP transmission statistics.
.1.3.111.2.802.1.1.13.2.2.6,LLDP-V2-MIB::lldpV2LocSysGroup,,,,,,The collection of objects that are used to represent LLDP Local System Information.
.1.3.111.2.802.1.1.13.2.2.7,LLDP-V2-MIB::lldpV2RemSysGroup,,,,,,The collection of objects that are used to represent LLDP Remote Systems Information. The objects represent the information associated with the basic TLV set. Please note that even if the agent does not implement some of the optional TLVs, it shall recognize all the optional TLV information that the remote system may advertise.
.1.3.111.2.802.1.1.13.2.2.8,LLDP-V2-MIB::lldpV2NotificationsGroup,,,,,,The collection of notifications used to indicate LLDP MIB data consistency and general status information.
.1.3.111.2.802.1.1.14,IEEE8021-TPMR-MIB::ieee8021TpmrMib,,,,,,Two-Port MAC Relay (TPMR) MIB module.  Unless otherwise indicated, the references in this MIB  module are to IEEE Std 802.1Q. Copyright(c) IEEE (2018) This MIB module is part of IEEE Std 802.1Q;  refer to the document itself for full legal notices.
.1.3.111.2.802.1.1.14.0,IEEE8021-TPMR-MIB::ieee8021TpmrNotifications,,,,,,
.1.3.111.2.802.1.1.14.1,IEEE8021-TPMR-MIB::ieee8021TpmrObjects,,,,,,
.1.3.111.2.802.1.1.14.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortTable,,not-accessible,,current,,The TPMR port table. Each row in the table represents a TPMR port. By definition there are two ports per TPMR. Note that the indices of this table are equivalent to those of the ieee8021BridgeBasePortTable in the IEEE8021-BRIDGE-MIB, with ieee8021TpmrPortNumber having a more limited value range than ieee8021BridgeBasePort.
.1.3.111.2.802.1.1.14.1.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021TpmrPortNumber,current,,A TPMR port table entry.
.1.3.111.2.802.1.1.14.1.1.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortNumber,Unsigned32,not-accessible,,current,,The number of this TPMR port.
.1.3.111.2.802.1.1.14.1.1.1.2,IEEE8021-TPMR-MIB::ieee8021TpmrPortMgmtAddr,INTEGER,read-only,,current,true(1):false(2),Is 'true' if the TPMR port MAC address is the management address of the TPMR, otheriwse 'false'.
.1.3.111.2.802.1.1.14.1.1.1.3,IEEE8021-TPMR-MIB::ieee8021TpmrPortMgmtAddrForwarding,INTEGER,read-only,,current,true(1):false(2),Is 'true' if forwarding is enabled for frames destined to the management address of the TPMR, otherwise 'false'.
.1.3.111.2.802.1.1.14.1.2,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsTable,,not-accessible,,current,,The TPMR port statistics table. Each row in the table represents a TPMR port. By definition there are two ports per TPMR. Discontinuities in the value of counters in this table can occur at re-initialization of the management system, and at other times as indicated by the value of IF-MIB ifCounterDiscontinuityTime.
.1.3.111.2.802.1.1.14.1.2.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsEntry,,not-accessible,,current,,A TPMR port counters table entry.
.1.3.111.2.802.1.1.14.1.2.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsRxFrames,Counter64,read-only,,current,,Count of all valid frames received on this port (including BPDUs, frames addressed to the TPMR as an end station, and frames that were submitted to the Forwarding Process).
.1.3.111.2.802.1.1.14.1.2.1.2,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsRxOctets,Counter64,read-only,,current,,Count of the total number of octets in all valid frames received on this port (including BPDUs, frames addressed to the TPMR as an end station, and frames that were submitted to the Forwarding Process).
.1.3.111.2.802.1.1.14.1.2.1.3,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsFramesForwarded,Counter64,read-only,,current,,Count of all frames that were received on this port and were forwarded to the transmission port.
.1.3.111.2.802.1.1.14.1.2.1.4,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsFramesDiscarded,Counter64,read-only,,current,,Count of all frames that were received on this port but were discarded by the Forwarding Process for any reason.
.1.3.111.2.802.1.1.14.1.2.1.5,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsFramesDiscardedQueueFull,Counter64,read-only,,current,,Count of all frames received on this port that were to be transmitted through the transmission port but were discarded due to lack of available queue space.
.1.3.111.2.802.1.1.14.1.2.1.6,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsFramesDiscardedLifetime,Counter64,read-only,,current,,Count of all frames received on this port that were to be transmitted through the transmission port but were discarded due to their frame lifetime having been exceeded.
.1.3.111.2.802.1.1.14.1.2.1.7,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsFramesDiscardedError,Counter64,read-only,,current,,Count of all frames received on this port that were to be transmitted through the transmission port but could not be transmitted (e.g., frame too large).
.1.3.111.2.802.1.1.14.1.3,IEEE8021-TPMR-MIB::ieee8021TpmrPortDiscardDetailsTable,,not-accessible,,current,,The TPMR frames discard details table. Each row in the table represents a discarded frame on a TPMR port. By definition there are two ports per TPMR. This table is maintained as a FIFO. A new entry is inserted in the first row, and existing entries are shuffled down, with the last entry being discarded. Because of the FIFO behavior, the relationship between the index and contents will change when an entry is added to the table. This may result in apparent duplication of row content during a table traversal.
.1.3.111.2.802.1.1.14.1.3.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortDiscardDetailsEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021TpmrPortNumber:ieee8021TpmrPortDiscardDetailsIndex,current,,A TPMR frames discarded error details table entry.
.1.3.111.2.802.1.1.14.1.3.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortDiscardDetailsIndex,Unsigned32,not-accessible,,current,,The second index of a TPMR frames discard details table entry.
.1.3.111.2.802.1.1.14.1.3.1.2,IEEE8021-TPMR-MIB::ieee8021TpmrPortDiscardDetailsSource,OCTET,read-only,,current,,The source MAC address of the discarded frame.
.1.3.111.2.802.1.1.14.1.3.1.3,IEEE8021-TPMR-MIB::ieee8021TpmrPortDiscardDetailsReason,INTEGER,read-only,,current,txSduSizeExceeded(1),The reason why the frame was discarded.
.1.3.111.2.802.1.1.14.1.4,IEEE8021-TPMR-MIB::ieee8021TpmrMspTable,,not-accessible,,current,,The TPMR MAC status propagation performance table. Each row in the table represents a TPMR port. By definition there are two ports per TPMR. The persistence of writable objects in a conceptual row of this table is determined by the value of the ieee8021TpmrMspStorageType object.
.1.3.111.2.802.1.1.14.1.4.1,IEEE8021-TPMR-MIB::ieee8021TpmrMspEntry,,not-accessible,,current,,A TPMR MAC status propagation performance table entry.
.1.3.111.2.802.1.1.14.1.4.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrMspLinkNotify,INTEGER,read-write,,current,true(1):false(2),The value of LinkNotify used by the MSP state machines.
.1.3.111.2.802.1.1.14.1.4.1.2,IEEE8021-TPMR-MIB::ieee8021TpmrMspLinkNotifyWait,INTEGER,read-write,,current,,The value of LinkNotifyWait used by the MSP state machines.
.1.3.111.2.802.1.1.14.1.4.1.3,IEEE8021-TPMR-MIB::ieee8021TpmrMspLinkNotifyRetry,INTEGER,read-write,,current,,The value of LinkNotifyRetry used by the MSP state machines.
.1.3.111.2.802.1.1.14.1.4.1.4,IEEE8021-TPMR-MIB::ieee8021TpmrMspMacNotify,INTEGER,read-write,,current,true(1):false(2),The value of MacNotify used by the MSP state machines.
.1.3.111.2.802.1.1.14.1.4.1.5,IEEE8021-TPMR-MIB::ieee8021TpmrMspMacNotifyTime,INTEGER,read-write,,current,,The value of MacNotifyTime used by the MSP state machines.
.1.3.111.2.802.1.1.14.1.4.1.6,IEEE8021-TPMR-MIB::ieee8021TpmrMspMacRecoverTime,INTEGER,read-write,,current,,The value of MacRecoverTime used by the MSP state machines.
.1.3.111.2.802.1.1.14.1.4.1.7,IEEE8021-TPMR-MIB::ieee8021TpmrMspStorageType,INTEGER,read-write,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for all read-write objects within this row. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row. If this object has the value 'volatile', modifications to read-write objects in this row are not persistent across reboots or restarts. If this object has the value 'nonVolatile', modifications to objects in this row are persistent.
.1.3.111.2.802.1.1.14.1.5,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsTable,,not-accessible,,current,,The TPMR MAC status propagation statistics table. Each row in the table represents a TPMR port. By definition there are two ports per TPMR. Discontinuities in the value of counters in this table can occur at re-initialization of the management system, and at other times as indicated by the value of IF-MIB ifCounterDiscontinuityTime.
.1.3.111.2.802.1.1.14.1.5.1,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsEntry,,not-accessible,,current,,A TPMR MAC status propagation statistics table entry.
.1.3.111.2.802.1.1.14.1.5.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsTxAcks,Counter32,read-only,,current,,The number of acks transmitted by the port's Transmit Process as a consequence of txAck being set.
.1.3.111.2.802.1.1.14.1.5.1.2,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsTxAddNotifications,Counter32,read-only,,current,,The number of adds transmitted by the port's Transmit Process as a consequence of txAdd being set.
.1.3.111.2.802.1.1.14.1.5.1.3,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsTxAddConfirmations,Counter32,read-only,,current,,The number of add confirms transmitted by the port's Transmit Process as a consequence of txAddConfirm being set.
.1.3.111.2.802.1.1.14.1.5.1.4,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsTxLossNotifications,Counter32,read-only,,current,,The number of losses transmitted by the port's Transmit Process as a consequence of txLoss being set.
.1.3.111.2.802.1.1.14.1.5.1.5,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsTxLossConfirmations,Counter32,read-only,,current,,The number of loss confirms transmitted by the port's Transmit Process as a consequence of txLossConfirm being set.
.1.3.111.2.802.1.1.14.1.5.1.6,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsRxAcks,Counter32,read-only,,current,,The number of acks received by the port's Receive Process.
.1.3.111.2.802.1.1.14.1.5.1.7,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsRxAddNotifications,Counter32,read-only,,current,,The number of adds received by the port's Receive Process.
.1.3.111.2.802.1.1.14.1.5.1.8,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsRxAddConfirmations,Counter32,read-only,,current,,The number of add confirms received by the port's Receive Process.
.1.3.111.2.802.1.1.14.1.5.1.9,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsRxLossNotifications,Counter32,read-only,,current,,The number of losses received by the port's Receive Process.
.1.3.111.2.802.1.1.14.1.5.1.10,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsRxLossConfirmations,Counter32,read-only,,current,,The number of loss confirms received by the port's Receive Process.
.1.3.111.2.802.1.1.14.1.5.1.11,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsAddEvents,Counter32,read-only,,current,,The number of transitions to STM:ADD directly from STM:DOWN or STM:LOSS.
.1.3.111.2.802.1.1.14.1.5.1.12,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsLossEvents,Counter32,read-only,,current,,The number of transitions to STM:LOSS directly from STM:UP or STM:ADD.
.1.3.111.2.802.1.1.14.1.5.1.13,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsMacStatusNotifications,Counter32,read-only,,current,,The number of transitions to SNM:MAC_NOTIFICATION.
.1.3.111.2.802.1.1.14.2,IEEE8021-TPMR-MIB::ieee8021TpmrConformance,,,,,,
.1.3.111.2.802.1.1.14.2.1,IEEE8021-TPMR-MIB::ieee8021TpmrCompliances,,,,,,
.1.3.111.2.802.1.1.14.2.1.1,IEEE8021-TPMR-MIB::ieee8021TpmrCompliance,,,,,,The compliance statement for device support of TPMR.
.1.3.111.2.802.1.1.14.2.2,IEEE8021-TPMR-MIB::ieee8021TpmrGroups,,,,,,
.1.3.111.2.802.1.1.14.2.2.1,IEEE8021-TPMR-MIB::ieee8021TpmrPortGroup,,,,,,TPMR port objects.
.1.3.111.2.802.1.1.14.2.2.2,IEEE8021-TPMR-MIB::ieee8021TpmrPortStatsGroup,,,,,,TPMR port statistics objects.
.1.3.111.2.802.1.1.14.2.2.3,IEEE8021-TPMR-MIB::ieee8021TpmrPortDiscardDetailsGroup,,,,,,TPMR port discard details objects.
.1.3.111.2.802.1.1.14.2.2.4,IEEE8021-TPMR-MIB::ieee8021TpmrMspGroup,,,,,,TPMR port MSP objects.
.1.3.111.2.802.1.1.14.2.2.5,IEEE8021-TPMR-MIB::ieee8021TpmrMspStatsGroup,,,,,,TPMR port MSP statistics objects.
.1.3.111.2.802.1.1.15,IEEE8021X-PAE-MIB::ieee8021XPaeMIB,,,,,,The MIB module for managing the Port Access Entity (PAE) functions of IEEE 802.1X (Revision of 802.1X-2004). The PAE functions managed are summarized in Figure 12-3 of IEEE 802.1X and include EAPOL PACP support for authentication (EAP Supplicant and/or Authenticator), MACsec Key Agreement (MKA), EAPOL, and transmission and reception of network announcements. The following acronyms and definitions are used in this MIB. AN : Association Number, a number that is concatenated with a MACsec Secure Channel Identifier to identify a Secure Association (SA). Announcer : EAPOL-Announcement transmission functionality. Authenticator : An entity that facilitates authentication of other entities attached to the same LAN. CA : secure Connectivity Association: A security relationship, established and maintained by key agreement protocols, that comprises a fully connected subset of the service access points in stations attached to a single LAN that are to be supported by MACsec. CAK : secure Connectivity Association Key, a secret key possessed by members of a given CA. CKN : secure Connectivity Association Key Name (CKN), a text that identifies a CAK. Common Port : An instance of the MAC Internal Sublayer Service used by the SecY or PAC to provide transmission and reception of frames for both the Controlled and Uncontrolled Ports. Controlled Port : The access point used to provide the secure MAC Service to a client of a PAC or SecY. CP state machine : Controlled Port state machine is capable of controlling a SecY or a PAC. The CP supports interoperability with unauthenticated systems that are not port-based network access control capable, or that lack  MKA. When the access controlled port is supported by a SecY, the CP is capable of controlling the SecY so as to provide unsecured connectivity to systems that implement a PAC. EAP : Extensible Authentication Protocol, RFC3748. EAPOL : EAP over LANs. KaY : Key Agreement Entity, a PAE entity responsible for MKA. Key Server : Elected by MKA, to transport a succession of SAKs, for use by MACsec, to the other member(s) of a CA. KMD : Key Management Domain, a string identifying systems that share cached CAKs. Listener : The role is to receive the network announcement parameters in the authentication process. Logon Process : The Logon Process is responsible for the managing the use of authentication credentials, for initiating use of the PAE's Supplicant and or Authenticator functionality, for deriving CAK, CKN tuples from PAE results, for maintaining PSKs (Pre-Sharing Keys), and for managing MKA instances. In the absence of successful authentication, key agreement, or support for MAC Security, the Logon Process determines whether the CP state machine should provide unauthenticated connectivity or authenticated but unsecured connectivity. MKA : MACsec Key Agreement protocol allows PAEs, each associated with a port that is an authenticated member of a secure connectivity association (CA) or a potential CA, to discover other PAEs attached to the same LAN, to confirm mutual possession of a CAK and hence to prove a past mutual authentication, to agree the secret keys (SAKs) used by MACsec for symmetric shared key cryptography, and to ensure that the data protected by MACsec has not been delayed. MKPDU : MACsec Key Agreement Protocol Data Unit. MPDU : MAC Protocol Data Unit. NID : Network Identity, a UTF-
.1.3.111.2.802.1.1.15.0,IEEE8021X-PAE-MIB::ieee8021XPaeMIBNotifications,,,,,,
.1.3.111.2.802.1.1.15.1,IEEE8021X-PAE-MIB::ieee8021XPaeMIBObjects,,,,,,
.1.3.111.2.802.1.1.15.1.1,IEEE8021X-PAE-MIB::ieee8021XPaeSystem,,,,,,
.1.3.111.2.802.1.1.15.1.1.1,IEEE8021X-PAE-MIB::ieee8021XPaeSysAccessControl,INTEGER,read-write,,current,true(1):false(2),This object enables or disables port-based network access control for all the system's ports. Setting this control object to 'false' causes the following actions : . Deletes any virtual ports previously instantiated. . Terminates authentication exchanges and MKA instances' operation. . Each real port PAE behaves as if no virtual ports created. . All the PAEs' Supplicant, Authenticator, and KaY are disabled. . Logon Process(es) behave as if the object ieee8021XNidUnauthAllowed was 'immediate'. . Announcements can be transmitted, both periodically and in response to announcement requests (conveyed by EAPOL-Starts or EAPOL-Announcement-Reqs) but are sent with a single NULL NID. . Objects announcementAccessStatus and announceAccessStatus have the 'noAccess' value, announcementAccessRequested is 'false', object announcementUnauthAccess has the 'openAccess' value. The control variable settings for each real port PAE in the ieee8021XPaePortTable are unaffected, and will be used once the object is set to 'true'. This configured value for this object shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.1.2,IEEE8021X-PAE-MIB::ieee8021XPaeSysAnnouncements,INTEGER,read-write,,current,true(1):false(2),Setting this control object to 'false' causes each PAE in this system to behave as if the PAE's Announcement functionality is  disabled. The independent controls for each PAE apply if this object is 'true'. This configured value for this object shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.1.3,IEEE8021X-PAE-MIB::ieee8021XPaeSysEapolVersion,Unsigned32,read-only,,current,,The EAPOL protocol version for this system.
.1.3.111.2.802.1.1.15.1.1.4,IEEE8021X-PAE-MIB::ieee8021XPaeSysMkaVersion,Unsigned32,read-only,,current,,The MKA protocol version for this system.
.1.3.111.2.802.1.1.15.1.1.5,IEEE8021X-PAE-MIB::ieee8021XPaePortTable,,not-accessible,,current,,A table of system level information for each port supported by the Port Access Entity. An entry appears in this table for each port of this system. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.1.5.1,IEEE8021X-PAE-MIB::ieee8021XPaePortEntry,,not-accessible,ieee8021XPaePortNumber,current,,The Port number, protocol version, and initialization control for a Port. If the PAE has been dynamically instantiated to support an existing or potential virtual port, the Uncontrolled Port interface and Controlled Port interface are allocated by the real port's PAE.
.1.3.111.2.802.1.1.15.1.1.5.1.1,IEEE8021X-PAE-MIB::ieee8021XPaePortNumber,Integer32,not-accessible,,current,,An interface index indicates the port number associated with this port. Each PAE is uniquely identified by a port number. The port number used is unique amongst all port numbers for the system, and directly or indirectly identifies the Uncontrolled Port that supports the PAE. If the PAE indicates a real port, ieee8021XPaePortType object in the same row is 'realPort', the port number shall be the same as the ieee8021XPaeCommonPortNumber object in the same row for the associated PAC or SecY. If the PAE indicates a virtual port, ieee8021XPaePortType object in the same row is 'virtualPort', this port number should be the same as the uncontrolledPortNumber object in the same row for the associated PAC or SecY.
.1.3.111.2.802.1.1.15.1.1.5.1.2,IEEE8021X-PAE-MIB::ieee8021XPaePortType,INTEGER,read-only,,current,realPort(1):virtualPort(2),The port type of the PAE. realPort(1) : indicates the PAE is for a real port. virtualPort(2) : indicates the PAE is for a virtual port.
.1.3.111.2.802.1.1.15.1.1.5.1.3,IEEE8021X-PAE-MIB::ieee8021XPaeControlledPortNumber,Integer32,read-only,,current,,An interface index indicates the port number associated with PAC or SecY's Controlled Port.
.1.3.111.2.802.1.1.15.1.1.5.1.4,IEEE8021X-PAE-MIB::ieee8021XPaeUncontrolledPortNumber,Integer32,read-only,,current,,An interface index indicates the port number associated with PAC or SecY's Uncontrolled Port. If the PAE supports a real port, this port number can be the same as the ieee8021XPaeCommonPortNumber object in the same row, otherwise it shall not be the same.
.1.3.111.2.802.1.1.15.1.1.5.1.5,IEEE8021X-PAE-MIB::ieee8021XPaeCommonPortNumber,Integer32,read-only,,current,,An interface index indicates the port number associated with PAC or SecY's 'Common Port'. All the virtual ports created for a given real port share the same 'Common Port' and ieee8021XPaeCommonPortNumber in the same row.
.1.3.111.2.802.1.1.15.1.1.5.1.6,IEEE8021X-PAE-MIB::ieee8021XPaePortInitialize,INTEGER,read-write,,current,true(1):false(2),The initialization control for this Port. Setting this object 'true' causes the Port to be reinitialized, terminating (and potentially restarting) authentication exchanges and MKA operation. If the port is a real port, any virtual ports previously instantiated are deleted. Virtual ports can be reinstantiated through normal protocol operation. The object value reverts to 'false' once initialization has completed.
.1.3.111.2.802.1.1.15.1.1.5.1.7,IEEE8021X-PAE-MIB::ieee8021XPaePortCapabilities,BITS,read-only,,current,suppImplemented(0):authImplemented(1):mkaImplemented(2):macsecImplemented(3):announcementsImplemented(4):listenerImplemented(5):virtualPortsImplemented(6),The capabilities of this PAE port. 'suppImplemented' : A PACP EAP supplicant functions are implemented in this PAE if this bit is on. 'authImplemented' : A PACP EAP authenticator functions are implemented in this PAE if this bit is on. 'mkaImplemented' : The KaY MKA functions are implemented in this PAE if this bit is on. 'macsecImplemented' : The MACsec functions in the Controlled Port are implemented in this PAE if this bit is on. 'announcementsImplemented' : The EAPOL announcement can be sent in this PAE if this bit is on. 'listenerImplemented' : This PAE can receive EAPOL announcement if this bit is on. 'virtualPortsImplemented' : Virtual Port functions are implemented in this PAE if this bit is on.
.1.3.111.2.802.1.1.15.1.1.5.1.8,IEEE8021X-PAE-MIB::ieee8021XPaePortVirtualPortsEnable,INTEGER,read-write,,current,true(1):false(2),Enable or disable to Virtual Ports function for this Real Port PAE, the object ieee8021XPaePortType in the same row has the value 'realPort'. If this PAE is not a Real Port, this object should be read only and returns 'false'. This object will be read only and returns 'false' if the value of the object ieee8021XPaePortCapabilities in the same row has the bit 'virtualPortsImplemented' off.
.1.3.111.2.802.1.1.15.1.1.5.1.9,IEEE8021X-PAE-MIB::ieee8021XPaePortMaxVirtualPorts,Unsigned32,read-only,,current,,The maximum number of virtual ports can be supported in this port.
.1.3.111.2.802.1.1.15.1.1.5.1.10,IEEE8021X-PAE-MIB::ieee8021XPaePortCurrentVirtualPorts,Gauge32,read-only,,current,,The current number of virtual ports is running in this port.
.1.3.111.2.802.1.1.15.1.1.5.1.11,IEEE8021X-PAE-MIB::ieee8021XPaePortVirtualPortStart,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if the virtual port is created by receipt of an EAPOL-Start packet.
.1.3.111.2.802.1.1.15.1.1.5.1.12,IEEE8021X-PAE-MIB::ieee8021XPaePortVirtualPortPeerMAC,OCTET,read-only,,current,,The source MAC address of the received EAPOL-Start if ieee8021XPaePortVirtualPortStart is set 'true'. If ieee8021XPaePortVirtualPortStart is not 'true' in the same row, the value of this object should be 00-00-00-00-00-00.
.1.3.111.2.802.1.1.15.1.1.5.1.13,IEEE8021X-PAE-MIB::ieee8021XPaePortLogonEnable,INTEGER,read-write,,current,true(1):false(2),Enable or disable to transmit network announcement information.
.1.3.111.2.802.1.1.15.1.1.5.1.14,IEEE8021X-PAE-MIB::ieee8021XPaePortAuthenticatorEnable,INTEGER,read-only,,current,true(1):false(2),Enable or disable to the Authenticator function in this PAE. This object will be read only and returns 'false' if the value of the object ieee8021XPaePortCapabilities in the same row has the bit 'authImplemented' Off.
.1.3.111.2.802.1.1.15.1.1.5.1.15,IEEE8021X-PAE-MIB::ieee8021XPaePortSupplicantEnable,INTEGER,read-only,,current,true(1):false(2),Enable or disable to the Supplicant function in this PAE. This object will be read only and returns 'false' if the value of the object ieee8021XPaePortCapabilities in the same row has the bit 'suppImplemented' off.
.1.3.111.2.802.1.1.15.1.1.5.1.16,IEEE8021X-PAE-MIB::ieee8021XPaePortKayMkaEnable,INTEGER,read-write,,current,true(1):false(2),Enable or disable the MKA protocol function in this PAE. This object will be read only and returns 'false' if the value of the object ieee8021XPaePortCapabilities in the same row has the bit 'mkaImplemented' off.
.1.3.111.2.802.1.1.15.1.1.5.1.17,IEEE8021X-PAE-MIB::ieee8021XPaePortAnnouncerEnable,INTEGER,read-write,,current,true(1):false(2),Enable or disable the network Announcer function in this PAE. This object will be read only and returns 'false' if the value of the object ieee8021XPaePortCapabilities in the same row has the bit 'announcementsImplemented' off.
.1.3.111.2.802.1.1.15.1.1.5.1.18,IEEE8021X-PAE-MIB::ieee8021XPaePortListenerEnable,INTEGER,read-write,,current,true(1):false(2),Enable or disable the network Listener function in this PAE. This object will be read only and returns 'false' if the value of the object ieee8021XPaePortCapabilities in the same row has the bit 'listenerImplemented' off.
.1.3.111.2.802.1.1.15.1.1.6,IEEE8021X-PAE-MIB::ieee8021XPacPortTable,,not-accessible,,current,,A table of system level information for each interface supported by PAC. This table will be instantiated if the value of the object ieee8021XPaePortCapabilities in the corresponding entry of the ieee8021XPaePortTable has the bit 'macsecImplemented' off. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.1.6.1,IEEE8021X-PAE-MIB::ieee8021XPacPortEntry,,not-accessible,ieee8021XPacPortControlledPortNumber,current,,An entry containing PAC management information applicable to a particular interface.
.1.3.111.2.802.1.1.15.1.1.6.1.1,IEEE8021X-PAE-MIB::ieee8021XPacPortControlledPortNumber,Integer32,not-accessible,,current,,The index to identify the 'Controlled Port' interface for a PAC.
.1.3.111.2.802.1.1.15.1.1.6.1.2,IEEE8021X-PAE-MIB::ieee8021XPacPortAdminPt2PtMAC,INTEGER,read-write,,current,forceTrue(1):forceFalse(2):auto(3),An object to control the service connectivity to at most one other system. The ieee8021XPacPortOperPt2PtMAC indicates operational status of the service connectivity for this PAC. 'forceTrue' : allows only one service connection to the other system. 'forceFalse' : no restriction on the number of service connections to the other systems. 'auto' : means the service connectivity is determined by the service providing entity.
.1.3.111.2.802.1.1.15.1.1.6.1.3,IEEE8021X-PAE-MIB::ieee8021XPacPortOperPt2PtMAC,INTEGER,read-only,,current,true(1):false(2),An object to reflect the current service connectivity status. 'true' : means the service connectivity of this PAC Controlled Port provides at most one other system. 'false' : means the service connectivity of this PAC could provide more than one other system.
.1.3.111.2.802.1.1.15.1.2,IEEE8021X-PAE-MIB::ieee8021XPaeLogon,,,,,,
.1.3.111.2.802.1.1.15.1.2.1,IEEE8021X-PAE-MIB::ieee8021XPaePortLogonTable,,not-accessible,,current,,A table of system level information for each port to support the Logon Process(es) status information. This table will be instantiated if the object ieee8021XPaePortLogonEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'.
.1.3.111.2.802.1.1.15.1.2.1.1,IEEE8021X-PAE-MIB::ieee8021XPaePortLogonEntry,,not-accessible,ieee8021XPaePortNumber,current,,An entry contains Logon Process status information for the PAE.
.1.3.111.2.802.1.1.15.1.2.1.1.1,IEEE8021X-PAE-MIB::ieee8021XPaePortLogonConnectStatus,INTEGER,read-only,,current,pending(1):unauthenticated(2):authenticated(3):secure(4),The Logon Process sets this variable to one of the following values, to indicate to the CP state machine if, and how, connectivity is to be provided through the Controlled Port : 'pending' : Prevent connectivity by disabling the Controlled Port of this PAE. 'unauthenticated' : Provide unsecured connectivity, enabling the Controlled Port of this PAE. 'authenticated' : Provide unsecured connectivity but with authentication, enabling Controlled Port of this PAE. 'secure' : Provide secure connectivity, using SAKs provided by the KaY (when available) and enabling Controlled Port when those keys are installed and in use.
.1.3.111.2.802.1.1.15.1.2.1.1.2,IEEE8021X-PAE-MIB::ieee8021XPaePortPortValid,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' if Controlled Port communication is secured as specified by the MACsec.
.1.3.111.2.802.1.1.15.1.2.2,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionTable,,not-accessible,,current,,A table of system level information for each port to support Logon Process(es) session information. This table maintains session statistics for its associated Controlled Port, suitable for communication to a RADIUS or other AAA server at the end of a session for accounting purpose. This table will be instantiated if the object ieee8021XPaePortLogonEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'.
.1.3.111.2.802.1.1.15.1.2.2.1,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionEntry,,not-accessible,ieee8021XPaeSessionControlledPortNumber,current,,An entry contains Logon Process session information for the PAE. A session, an entry, begins when the operation of Controlled Port becomes 'true' and ends when it becomes 'false'. The counts of frames and octets can be derived from those maintained to support from Interface MIB counters for the SecY's or the PAC's Controlled Port, but differs in that the counts are zeroed when the session begins.
.1.3.111.2.802.1.1.15.1.2.2.1.1,IEEE8021X-PAE-MIB::ieee8021XPaeSessionControlledPortNumber,Integer32,not-accessible,,current,,The index to identify the 'Controlled Port' interface's session information for a PAE.
.1.3.111.2.802.1.1.15.1.2.2.1.2,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionOctetsRx,Counter64,read-only,,current,,The number of octets received in this session of this PAE. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ieee8021XPaePortSessionStartTime.
.1.3.111.2.802.1.1.15.1.2.2.1.3,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionOctetsTx,Counter64,read-only,,current,,The number of octets transmitted in this session of this PAE. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ieee8021XPaePortSessionStartTime.
.1.3.111.2.802.1.1.15.1.2.2.1.4,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionPktsRx,Counter64,read-only,,current,,The number of packets received in this session of this PAE. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ieee8021XPaePortSessionStartTime.
.1.3.111.2.802.1.1.15.1.2.2.1.5,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionPktsTx,Counter64,read-only,,current,,The number of packets transmitted in this session of this PAE. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ieee8021XPaePortSessionStartTime.
.1.3.111.2.802.1.1.15.1.2.2.1.6,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionId,OCTET,read-only,,current,,The session identifier for this session of the PAE. A UTF-8 string, uniquely identifying the session within the context of the PAE's system.
.1.3.111.2.802.1.1.15.1.2.2.1.7,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionStartTime,TimeTicks,read-only,,current,,The starting time of this session.
.1.3.111.2.802.1.1.15.1.2.2.1.8,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionIntervalTime,INTEGER,read-only,,current,,The duration time of the session has been last.
.1.3.111.2.802.1.1.15.1.2.2.1.9,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionTerminate,INTEGER,read-only,,current,macOperFailed(1):sysAccessDisableOrPortInit(2):receiveEapolLogOff(3):eapReauthFailure(4):mkaFailure(5):newSessionBegin(6):notTerminateYet(7),The reason for the session termination, one of the following : 'macOperFailed' : 'Common Port' for this PAE is not operational. 'sysAccessDisableOrPortInit' : The ieee8021XPaeSysAccessControl object is set to 'false' or initialization process of this PAE is invoked. 'receiveEapolLogOff' : The PAE has received EAPOL-Logoff frame. 'eapReauthFailure' : EAP reauthentication has failed. 'mkaFailure' : MKA failure or other MKA termination. 'newSessionBegin' : New session beginning. 'notTerminateYet' : Not Terminated Yet.
.1.3.111.2.802.1.1.15.1.2.2.1.10,IEEE8021X-PAE-MIB::ieee8021XPaePortSessionUserName,OCTET,read-only,,current,,The session user name for this session in the PAE. A UTF-8 string, representing the identity of the peer Supplicant. If no such information, zero length string will return.
.1.3.111.2.802.1.1.15.1.2.3,IEEE8021X-PAE-MIB::ieee8021XLogonNIDTable,,not-accessible,,current,,The Logon Process may use Network Identities (NIDs) to manage its use of authentication credentials, cached CAKs, and announcements. This table provides the NID information for Logon Process. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.2.3.1,IEEE8021X-PAE-MIB::ieee8021XLogonNIDEntry,,not-accessible,ieee8021XPaePortNumber,current,,An entry provides the NID information for a Logon Process.
.1.3.111.2.802.1.1.15.1.2.3.1.1,IEEE8021X-PAE-MIB::ieee8021XLogonNIDConnectedNID,OCTET,read-only,,current,,The NID associated with the current connectivity (possibly unauthenticated) provided by the operation of the CP state machine. This object can differ from both the ieee8021XLogonNIDSelectedNID and the ieee8021XLogonNIDRequestedNID objects in the same row if authenticated connectivity (either secure or unsecured) has already been established, and EAP authentication and MKA operation for both of the latter have not met the necessary conditions (as specified by the control variables unauthAllowed and unsecureAllowed).
.1.3.111.2.802.1.1.15.1.2.3.1.2,IEEE8021X-PAE-MIB::ieee8021XLogonNIDRequestedNID,OCTET,read-only,,current,,The NID marked as access requested in announcements, as determined from EAPOL-Start frames. The default of this object is as the configured value of object ieee8021XLogonNIDSelectedNID. This object information provides context for the PAE's EAP Authenticator. If no EAPOL-Start frame has been received since the PAE's 'Common Port' became operational, or the last EAPOL-Start frame received for the port did not contain a requested NID, the object will take on the value of the object ieee8021XLogonNIDSelectedNID in the same row.
.1.3.111.2.802.1.1.15.1.2.3.1.3,IEEE8021X-PAE-MIB::ieee8021XLogonNIDSelectedNID,OCTET,read-write,,current,,The NID currently configured for use by an access 'Controlled Port' when transmitting EAPOL-Start frames. The default of this object is empty string. This object may be either explicitly configured by management or determined by the PAE using NID selection algorithms. If no authentication is in progress, and the current connectivity is terminated and then starts again, ieee8021XLogonNIDConnectedNID will take on the value of ieee8021XLogonNIDRequestedNID (though a PAE NID's election algorithm, if used, can subsequently select another NID).
.1.3.111.2.802.1.1.15.1.3,IEEE8021X-PAE-MIB::ieee8021XPaeAuthenticator,,,,,,
.1.3.111.2.802.1.1.15.1.3.1,IEEE8021X-PAE-MIB::ieee8021XAuthenticatorTable,,not-accessible,,current,,A table that contains the configuration objects for the Authenticator PAE associated with each port. This table will be instantiated if the object ieee8021XPaePortAuthenticatorEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.3.1.1,IEEE8021X-PAE-MIB::ieee8021XAuthenticatorEntry,,not-accessible,ieee8021XPaePortNumber,current,,An entry that contains the Authenticator configuration objects for the PAE.
.1.3.111.2.802.1.1.15.1.3.1.1.1,IEEE8021X-PAE-MIB::ieee8021XAuthPaeAuthenticate,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' by the PAE authenticator to request authentication, and if this object is 'true', reauthentication is allowed. This object will be 'false' while the PAE authenticator revokes authentication.
.1.3.111.2.802.1.1.15.1.3.1.1.2,IEEE8021X-PAE-MIB::ieee8021XAuthPaeAuthenticated,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' by PACP if the PAE authenticator currently authenticated, and 'false' if the authentication fails or is revoked.
.1.3.111.2.802.1.1.15.1.3.1.1.3,IEEE8021X-PAE-MIB::ieee8021XAuthPaeFailed,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' by PACP if the authentication has failed or has been terminated. The cause could be a failure returned by EAP, either immediately or following a reauthentication, an excessive number of attempts to authenticate (either immediately or upon reauthentication), or the authenticator deasserting authenticate, the object authPaeAuthenticate in the same row is 'false'. The PACP will set the object authPaeAuthenticated false as well as setting the object 'true'.
.1.3.111.2.802.1.1.15.1.3.1.1.4,IEEE8021X-PAE-MIB::ieee8021XAuthPaeReAuthEnabled,INTEGER,read-write,,current,true(1):false(2),This object is set 'true' if PACP should initiate reauthentication periodically, 'false' otherwise . Reading this object always returns 'false'.
.1.3.111.2.802.1.1.15.1.3.1.1.5,IEEE8021X-PAE-MIB::ieee8021XAuthPaeQuietPeriod,Unsigned32,read-write,,current,,This object indicates a waiting period after a failed authentication attempt, before another attempt is permitted.
.1.3.111.2.802.1.1.15.1.3.1.1.6,IEEE8021X-PAE-MIB::ieee8021XAuthPaeReauthPeriod,Unsigned32,read-write,,current,,This object indicates the time period of the reauthentication to the supplicant.
.1.3.111.2.802.1.1.15.1.3.1.1.7,IEEE8021X-PAE-MIB::ieee8021XAuthPaeRetryMax,Unsigned32,read-write,,current,,The maximum number of authentication attempts before failure is reported to the Logon Process, and the authPaeQuietPeriod  timer imposed before further attempts are permitted.
.1.3.111.2.802.1.1.15.1.3.1.1.8,IEEE8021X-PAE-MIB::ieee8021XAuthPaeRetryCount,Gauge32,read-only,,current,,The count of the number of authentication attempts.
.1.3.111.2.802.1.1.15.1.4,IEEE8021X-PAE-MIB::ieee8021XPaeSupplicant,,,,,,
.1.3.111.2.802.1.1.15.1.4.1,IEEE8021X-PAE-MIB::ieee8021XSupplicantTable,,not-accessible,,current,,A table that contains the configuration objects for the Supplicant PAE associated with each port. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.4.1.1,IEEE8021X-PAE-MIB::ieee8021XSupplicantEntry,,not-accessible,ieee8021XPaePortNumber,current,,The configuration information for an Supplicant PAE.
.1.3.111.2.802.1.1.15.1.4.1.1.1,IEEE8021X-PAE-MIB::ieee8021XSuppPaeAuthenticate,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' by the PAE supplicant to request authentication, and if this object is 'true', reauthentication is allowed. This object will be 'false' while the PAE supplicant revokes authentication.
.1.3.111.2.802.1.1.15.1.4.1.1.2,IEEE8021X-PAE-MIB::ieee8021XSuppPaeAuthenticated,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' by PACP if the PAE supplicant currently authenticated, and 'false' if the authentication fails or is revoked.
.1.3.111.2.802.1.1.15.1.4.1.1.3,IEEE8021X-PAE-MIB::ieee8021XSuppPaeFailed,INTEGER,read-only,,current,true(1):false(2),This object will be set 'true' by PACP if the authentication has failed or has been terminated. The cause could be a failure returned by EAP, either immediately or following a reauthentication, an excessive number of attempts to authenticate (either immediately or upon reauthentication), or the supplicant deasserting authenticate, the object ieee8021XSuppPaeAuthenticate in the same row is 'false'. The PACP will set the object ieee8021XSuppPaeAuthenticated false as well as setting the object 'true'.
.1.3.111.2.802.1.1.15.1.4.1.1.4,IEEE8021X-PAE-MIB::ieee8021XSuppPaeHelloPeriod,Unsigned32,read-write,,current,,This object indicated a waiting time period after a failed authentication attempt, before another attempt is permitted.
.1.3.111.2.802.1.1.15.1.4.1.1.5,IEEE8021X-PAE-MIB::ieee8021XSuppPaeRetryMax,Unsigned32,read-write,,current,,The maximum number of authentication attempts before failure is reported to the Logon Process, and the ieee8021XSuppPaeHelloPeriod timer imposed before further attempts are permitted.
.1.3.111.2.802.1.1.15.1.4.1.1.6,IEEE8021X-PAE-MIB::ieee8021XSuppPaeRetryCount,Gauge32,read-only,,current,,The count of the number of authentication attempts.
.1.3.111.2.802.1.1.15.1.5,IEEE8021X-PAE-MIB::ieee8021XPaeEapol,,,,,,
.1.3.111.2.802.1.1.15.1.5.1,IEEE8021X-PAE-MIB::ieee8021XEapolStatsTable,,not-accessible,,current,,A table in system level contains the EAPOL statistics and diagnostics information supported by PAE.
.1.3.111.2.802.1.1.15.1.5.1.1,IEEE8021X-PAE-MIB::ieee8021XEapolStatsEntry,,not-accessible,ieee8021XPaePortNumber,current,,An entry contains the EAPOL statistics and diagnostics information for a PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.1,IEEE8021X-PAE-MIB::ieee8021XEapolInvalidFramesRx,Counter32,read-only,,current,,The number of invalid EAPOL frames of any type that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.2,IEEE8021X-PAE-MIB::ieee8021XEapolEapLengthErrorFramesRx,Counter32,read-only,,current,,The number of EAPOL frames that the Packet Body Length does not match a Packet Body that is contained within the octets of the received EAPOL MPDU in this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.3,IEEE8021X-PAE-MIB::ieee8021XEapolAnnouncementFramesRx,Counter32,read-only,,current,,The number of EAPOL-Announcement frames that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.4,IEEE8021X-PAE-MIB::ieee8021XEapolAnnouncementReqFramesRx,Counter32,read-only,,current,,The number of EAPOL-Announcement-Req frames that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.5,IEEE8021X-PAE-MIB::ieee8021XEapolPortUnavailableFramesRx,Counter32,read-only,,current,,The number of EAPOL frames that are discarded because their processing would require the creation of a virtual port, for which there are inadequate or constrained resources, or an existing virtual port and no such port currently exists. If virtual port is not supported, this object should be always 0.
.1.3.111.2.802.1.1.15.1.5.1.1.6,IEEE8021X-PAE-MIB::ieee8021XEapolStartFramesRx,Counter32,read-only,,current,,The number of EAPOL-Start frames that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.7,IEEE8021X-PAE-MIB::ieee8021XEapolEapFramesRx,Counter32,read-only,,current,,The number of EAPOL-EAP frames that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.8,IEEE8021X-PAE-MIB::ieee8021XEapolLogoffFramesRx,Counter32,read-only,,current,,The number of EAPOL-Logoff frames that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.9,IEEE8021X-PAE-MIB::ieee8021XEapolMkNoCknFramesRx,Counter32,read-only,,current,,The number of MKPDUs received with MKA not enabled or CKN not recognized in this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.10,IEEE8021X-PAE-MIB::ieee8021XEapolMkInvalidFramesRx,Counter32,read-only,,current,,The number of MKPDUs failing in message authentication on receipt process in this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.11,IEEE8021X-PAE-MIB::ieee8021XEapolLastRxFrameVersion,Unsigned32,read-only,,current,,The version of last received EAPOL frame by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.12,IEEE8021X-PAE-MIB::ieee8021XEapolLastRxFrameSource,OCTET,read-only,,current,,The source MAC address of last received EAPOL frame by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.13,IEEE8021X-PAE-MIB::ieee8021XEapolSuppEapFramesTx,Counter32,read-only,,current,,The number of EAPOL-EAP frames that have been transmitted by the supplicant of this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.14,IEEE8021X-PAE-MIB::ieee8021XEapolLogoffFramesTx,Counter32,read-only,,current,,The number of EAPOL-Logoff frames that have been transmitted by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.15,IEEE8021X-PAE-MIB::ieee8021XEapolAnnouncementFramesTx,Counter32,read-only,,current,,The number of EAPOL-Announcement frames that have been transmitted by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.16,IEEE8021X-PAE-MIB::ieee8021XEapolAnnouncementReqFramesTx,Counter32,read-only,,current,,The number of EAPOL-Announcement-Req frames that have been transmitted by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.17,IEEE8021X-PAE-MIB::ieee8021XEapolStartFramesTx,Counter32,read-only,,current,,The number of EAPOL-Start frames that have been received by this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.18,IEEE8021X-PAE-MIB::ieee8021XEapolAuthEapFramesTx,Counter32,read-only,,current,,The number of EAPOL-EAP frames that have been transmitted by the authenticator of this PAE.
.1.3.111.2.802.1.1.15.1.5.1.1.19,IEEE8021X-PAE-MIB::ieee8021XEapolMkaFramesTx,Counter32,read-only,,current,,The number of EAPOL-MKA frames with no CKN information that have been transmitted by this PAE.
.1.3.111.2.802.1.1.15.1.6,IEEE8021X-PAE-MIB::ieee8021XPaeKaY,,,,,,
.1.3.111.2.802.1.1.15.1.6.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaTable,,not-accessible,,current,,A table of system level information for each interface supported by the KaY (Key Agreement Entity). This table will be instantiated if the object ieee8021XPaePortKayMkaEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'. The following terms are used to identify roles within the MKA protocol or protocol scenarios and the MIB description : participant : An instance of MKA, transmitting and receiving frames protected by keys derived from a single CAK, and operating with positive intent, obeying the protocol. member: A participant that possesses the CAK that can be used to prove liveness and to obtain membership in the CA under discussion. actor: The participant under discussion, usually in the KaY being described. partners: Participants or members attached to the same LAN as the actor, excluding the actor. principal actor: The actor controlling the PAC or SecY associated with the KaY. Each participant selects the live participant advertising the highest priority as its key server provided that participant has not selected another as its key server or is unwilling to act as the key server. If a key server cannot be selected SAKs are not distributed. In the event of a tie for highest priority key server, the member with the highest priority SCI is chosen. For consistency with other uses of the SCI's MAC Address component as a priority, numerically lower values of the key server priority and SCI are accorded the highest priority. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.6.1.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaEntry,,not-accessible,ieee8021XPaePortNumber,current,,An entry containing KaY MKA management information applicable to a particular interface.
.1.3.111.2.802.1.1.15.1.6.1.1.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaActive,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if there is at least one MKA active actor, transmitting MKPDUs
.1.3.111.2.802.1.1.15.1.6.1.1.2,IEEE8021X-PAE-MIB::ieee8021XKayMkaAuthenticated,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if the principal actor, i.e. the actor controlling the PAC or SecY associated with the KaY, has determined that Controlled Port communication communication should proceed without MACsec.
.1.3.111.2.802.1.1.15.1.6.1.1.3,IEEE8021X-PAE-MIB::ieee8021XKayMkaSecured,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if the principal actor has determined that communication should use MACsec.
.1.3.111.2.802.1.1.15.1.6.1.1.4,IEEE8021X-PAE-MIB::ieee8021XKayMkaFailed,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if the object ieee8021XKayMkaSecured in the same row is 'false' and MKA Life Time has elapsed since an MKA participant was last created.
.1.3.111.2.802.1.1.15.1.6.1.1.5,IEEE8021X-PAE-MIB::ieee8021XKayMkaActorSCI,OCTET,read-only,,current,,The SCI assigned by the system to the port, applies to all the port's MKA actors.
.1.3.111.2.802.1.1.15.1.6.1.1.6,IEEE8021X-PAE-MIB::ieee8021XKayMkaActorsPriority,OCTET,read-write,,current,,The Key Server priority for all the port's MKA actors. Each participant encodes a key server priority, an 8-bit integer, in each MKPDU.
.1.3.111.2.802.1.1.15.1.6.1.1.7,IEEE8021X-PAE-MIB::ieee8021XKayMkaKeyServerPriority,OCTET,read-only,,current,,The priority of the elected Key Server through MKA in the CA.
.1.3.111.2.802.1.1.15.1.6.1.1.8,IEEE8021X-PAE-MIB::ieee8021XKayMkaKeyServerSCI,OCTET,read-only,,current,,The SCI for key server for the MKA principal actor. The length of this object is 0 if there is no principal actor, or that actor has no live peers. This object matches the ieee8021XKayMkaActorSCI object in the same row if the actor is the key server.
.1.3.111.2.802.1.1.15.1.6.1.1.9,IEEE8021X-PAE-MIB::ieee8021XKayAllowedJoinGroup,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if the KaY will accept Group CAKs distributed by MKA protocol.
.1.3.111.2.802.1.1.15.1.6.1.1.10,IEEE8021X-PAE-MIB::ieee8021XKayAllowedFormGroup,INTEGER,read-only,,current,true(1):false(2),This object will be 'true' if the KaY will attempt to use point-to-point CAKs to distribute a group CAK, if it is the Key Server for the MKA instances for all the point-to-point CAKs.
.1.3.111.2.802.1.1.15.1.6.1.1.11,IEEE8021X-PAE-MIB::ieee8021XKayCreateNewGroup,INTEGER,read-write,,current,true(1):false(2),This object is set 'true' if a new Group CAK is to be distributed if the KaY is the Key Server for the MKA instances for all the point-to-point CAKs. This object will be set 'false' by the KaY when distribution is complete.
.1.3.111.2.802.1.1.15.1.6.1.1.12,IEEE8021X-PAE-MIB::ieee8021XKayMacSecCapability,INTEGER,read-only,,current,noMACsec(0):macSecCapability1(1):macSecCapability2(2):macSecCapability3(3),This object indicates whether MACsec is implemented, and if so whether the implementation provides integrity protection only, integrity and integrity with confidentiality, or integrity and integrity with confidentiality with a selectable confidentiality offset of 0, 30, or 50 octets (see IEEE Std 802.1AE). 'noMACsec' : the MACsec is not implemented. 'macSecCapability1' : capable in 'integrity protection without confidentiality'. 'macSecCapability2' : capable in 'integrity protection without confidentiality' and integrity protection and confidentiali with a confidentiality offset 0',. 'macSecCapability3' : capable in 'integrity protection without confidentiality' and integrity protection and confidentiali with a confidentiality offset 0, 30 or 50'.
.1.3.111.2.802.1.1.15.1.6.1.1.13,IEEE8021X-PAE-MIB::ieee8021XKayMacSecDesired,INTEGER,read-write,,current,true(1):false(2),This object will be set 'true' if the MKA participants desire the use of MACsec to protect frames with this KaY.
.1.3.111.2.802.1.1.15.1.6.1.1.14,IEEE8021X-PAE-MIB::ieee8021XKayMacSecProtect,INTEGER,read-only,,current,true(1):false(2),The status of the MACsec protection function for this KaY. 'true' : then the status of the MACsec protection function will be as object secyIfProtectFramesEnable object configured in the IEEE8021-SECY-MIB. 'false' : then the MACsec protection function is disabled by this KaY.
.1.3.111.2.802.1.1.15.1.6.1.1.15,IEEE8021X-PAE-MIB::ieee8021XKayMacSecReplayProtect,INTEGER,read-only,,current,true(1):false(2),The status of the MACsec replay protection function for this KaY. 'true' : then the status of the MACsec replay protection function will be as secyIfReplayProtectEnable object configured in the IEEE8021-SECY-MIB. 'false' : then the MACsec replay protection function is disabled by this KaY.
.1.3.111.2.802.1.1.15.1.6.1.1.16,IEEE8021X-PAE-MIB::ieee8021XKayMacSecValidate,INTEGER,read-only,,current,true(1):false(2),The status of the MACsec validation function for this KaY. 'true' : then the status of the MACsec validation function will be as secyIfValidateFrames object configured in the IEEE8021-SECY-MIB. 'false' : then the MACsec validation function is enabled but only for checking without filtering out invalid frames by the SecY.
.1.3.111.2.802.1.1.15.1.6.1.1.17,IEEE8021X-PAE-MIB::ieee8021XKayMacSecConfidentialityOffset,Integer32,read-write,,current,,The confidentiality protection offset options for the selected cipher suite in the MACsec. If the cipher suite does not have this capability, the configured value of the object will not apply to the cipher suite.
.1.3.111.2.802.1.1.15.1.6.1.1.18,IEEE8021X-PAE-MIB::ieee8021XKayMkaTxKN,Unsigned32,read-only,,current,,The key number assigned by the key server to the SAK currently being used for transmission. This object will be 0 if MACsec is not being used or the key number is not available yet.
.1.3.111.2.802.1.1.15.1.6.1.1.19,IEEE8021X-PAE-MIB::ieee8021XKayMkaTxAN,OBJECT,read-only,,current,,The AN assigned by the key server for use with the key number for transmission. This row pointer will point to an entry in the secyTxSATable which the secyTxSCEncodingSA object also points to in the IEEE8021-SECY-MIB. If MACsec is not in use or the AN is not identified yet, the value of this object shall be set to the OBJECT IDENTIFIER { 0 0 }.
.1.3.111.2.802.1.1.15.1.6.1.1.20,IEEE8021X-PAE-MIB::ieee8021XKayMkaRxKN,Unsigned32,read-only,,current,,The key number assigned by the key server to the oldest SAK currently being used for reception. It is the same as the key number for transmission if a single SAK is currently in use. This object will be 0 if MACsec is not being used or the key number is not available yet.
.1.3.111.2.802.1.1.15.1.6.1.1.21,IEEE8021X-PAE-MIB::ieee8021XKayMkaRxAN,OBJECT,read-only,,current,,The AN assigned by the key server for use with the key number for reception. It is the same as AN for transmission if a single SAK is currently in use. This row pointer will point to an entry in the secyRxSATable which the secyRxSCCurrentSA object also points to in the IEEE8021-SECY-MIB. If MACsec is not in use or the AN is not identified yet, the value of this object shall be set to the OBJECT IDENTIFIER { 0 0 }.
.1.3.111.2.802.1.1.15.1.6.1.1.22,IEEE8021X-PAE-MIB::ieee8021XKayMkaSuspendFor,INTEGER,read-write,,current,,Set by management to a non-zero number of seconds between 1 and MKA Suspension Limit to initiate a suspension (9.18) of that duration (if the KaY's principal actor is the Key Server) or to request a suspension (otherwise)
.1.3.111.2.802.1.1.15.1.6.1.1.23,IEEE8021X-PAE-MIB::ieee8021XKayMkaSuspendOnRequest,INTEGER,read-write,,current,true(1):false(2),The status of the suspendOnRequest function for this KaY. 'true' : then the KaY's principal actor will initiate a suspension if it is the Key Server and another participant has requested a suspension by transmitting a non-zero value of its suspendFor parameter 'false' : then the KaY will not initiate a suspension on request from another participant.
.1.3.111.2.802.1.1.15.1.6.1.1.24,IEEE8021X-PAE-MIB::ieee8021XKayMkaSuspendedWhile,INTEGER,read-write,,current,,Read by management to determine if a suspension is in progress and to discover the remaining duration of that suspension. May be set directly to coordinate in-service upgrades.
.1.3.111.2.802.1.1.15.1.6.2,IEEE8021X-PAE-MIB::ieee8021XKayMkaParticipantTable,,not-accessible,,current,,A table for each MKA participant supported by the KaY MKA entity. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.6.2.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaParticipantEntry,,not-accessible,ieee8021XPaePortNumber:ieee8021XKayMkaPartCKN,current,,An entry containing KaY MKA management information applicable to a MKA participant.
.1.3.111.2.802.1.1.15.1.6.2.1.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartCKN,OCTET,not-accessible,,current,,The CKN information for this MKA participant.
.1.3.111.2.802.1.1.15.1.6.2.1.2,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartKMD,OCTET,read-create,,current,,The KMD information for this MKA participant.
.1.3.111.2.802.1.1.15.1.6.2.1.3,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartNID,OCTET,read-create,,current,,The NID information for this MKA participant.
.1.3.111.2.802.1.1.15.1.6.2.1.4,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartCached,INTEGER,read-create,,current,true(1):false(2),This object is set 'true' by the KaY if the participant's parameters are cached. If this object is 'true', this object can be set 'false' cleared by management to remove the participant's parameters from the cache.
.1.3.111.2.802.1.1.15.1.6.2.1.5,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartActive,INTEGER,read-only,,current,true(1):false(2),This object is set 'true' if the participant is active, i.e. is currently transmitting periodic MKPDUs.
.1.3.111.2.802.1.1.15.1.6.2.1.6,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartRetain,INTEGER,read-create,,current,true(1):false(2),This object is set 'true' to retain the participant in the cache, even if the KaY would normally remove it (due to lack of use for example)
.1.3.111.2.802.1.1.15.1.6.2.1.7,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartActivateControl,INTEGER,read-create,,current,default(1):disabled(2):onOperUp(3):always(4),This object is for controlling the participant's behavior when the participant is activated.  'default' : the participant is from cached entries created by the KaY as part of normal operation, without explicit management, and is activated according to the implementation dependent policies of the KaY. 'disabled' : the participant allows the cache information to be retained, but disabled for indefinite period. 'onOperUp' : causing the participant to be activated when the PAE's 'Uncontrolled Port' becomes operational and when the PAE resumes following suspension. 'always' : causing the participant to remain active all the time, even in the continued absence of partners. If the object changed to disabled(1) or onOperUp(3), the participant ceases operation immediately and receipt of MKPDUs with a matching CKN during a subsequent period of twice MKA lifetime will not cause the participant to become active once more.
.1.3.111.2.802.1.1.15.1.6.2.1.8,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartPrincipal,INTEGER,read-only,,current,true(1):false(2),This object is set 'true' if the participant is currently the principal actor.
.1.3.111.2.802.1.1.15.1.6.2.1.9,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartDistCKN,OCTET,read-only,,current,,The CKN for the last CAK distributed either by the actor or one of its partners. Empty string for this object will be provided if this participant has not been used to distribute a CAK or the participant is not active, i.e. the object ieee8021XKayMkaPartActive in the same row is 'false'.
.1.3.111.2.802.1.1.15.1.6.2.1.10,IEEE8021X-PAE-MIB::ieee8021XKayMkaPartRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object to create the parameters for the supported participant information in the system. If the participant information is from downloaded policies, this object is 'active'.
.1.3.111.2.802.1.1.15.1.6.3,IEEE8021X-PAE-MIB::ieee8021XKayMkaPeerListTable,,not-accessible,,current,,A table containing the lists of Live Peers and Potential Peers, for all MKA instances for which the KaY is active.
.1.3.111.2.802.1.1.15.1.6.3.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaPeerListEntry,,not-accessible,ieee8021XPaePortNumber:ieee8021XKayMkaPartCKN:ieee8021XKayMkaPeerListMI,current,,A table entry for one of the peers for one of the MKA instances for which this KaY is an active participant.
.1.3.111.2.802.1.1.15.1.6.3.1.1,IEEE8021X-PAE-MIB::ieee8021XKayMkaPeerListMI,OCTET,not-accessible,,current,,The peer entry's MI information in the peer list of this active participant in MKA protocol.
.1.3.111.2.802.1.1.15.1.6.3.1.2,IEEE8021X-PAE-MIB::ieee8021XKayMkaPeerListMN,Unsigned32,read-only,,current,,The peer entry's latest MN information in the peer list of this active participant in MKA protocol.
.1.3.111.2.802.1.1.15.1.6.3.1.3,IEEE8021X-PAE-MIB::ieee8021XKayMkaPeerListType,INTEGER,read-only,,current,livePeerList(1):potentialPeerList(2),The peer entry's type in the peer list of this active participant in MKA protocol. 'livePeerList' : the peer entry is in the Live Peer List. 'potentialPeerList' : the peer entry is in the Potential Peer List.
.1.3.111.2.802.1.1.15.1.6.3.1.4,IEEE8021X-PAE-MIB::ieee8021XKayMkaPeerListSCI,OCTET,read-only,,current,,The SCI information of the peer entry in the peer list of this active participant in MKA protocol.
.1.3.111.2.802.1.1.15.1.7,IEEE8021X-PAE-MIB::ieee8021XPaeNetworkIdentifier,,,,,,
.1.3.111.2.802.1.1.15.1.7.1,IEEE8021X-PAE-MIB::ieee8021XNidConfigTable,,not-accessible,,current,,A table that contains the configuration objects for the network announcement information for the Logon Process. The detail operation of the Logon Process can vary depending on the port-based network access control applications, and on the capabilities supported by that implementation including, for example, network discovery and roaming. This table specifies control variables that facilitate behaviors that are potentially useful in a range of applications. Implementations may use and augment the variables specified, or may use variables specific to the implementation. For the writeable objects in this table, the configured value shall be stored in persistent memory and remain unchanged across a re-initialization of the management system of the entity.
.1.3.111.2.802.1.1.15.1.7.1.1,IEEE8021X-PAE-MIB::ieee8021XNidConfigEntry,,not-accessible,IMPLIEDieee8021XNidNID,current,,An entry contains network announcement parameters for a NID.
.1.3.111.2.802.1.1.15.1.7.1.1.1,IEEE8021X-PAE-MIB::ieee8021XNidNID,OCTET,not-accessible,,current,,The network identifier to identify NID configuration in the PAE.
.1.3.111.2.802.1.1.15.1.7.1.1.2,IEEE8021X-PAE-MIB::ieee8021XNidUseEap,INTEGER,read-create,,current,never(1):immediate(2):mkaFail(3),Determines when the Logon Process will initiate EAP, if the Supplicant and or Authenticator are enabled, and takes one of the following values: 'never' : Never. 'immediate' : Immediately, concurrently with the use of MKA with any cached CAK(s). 'mkaFail' : Not until MKA has failed, if a prior CAK has been cached.
.1.3.111.2.802.1.1.15.1.7.1.1.3,IEEE8021X-PAE-MIB::ieee8021XNidUnauthAllowed,INTEGER,read-create,,current,never(1):immediate(2):authFail(3),Determines when the Logon Process will tell the CP state machine to provide unauthenticated connectivity, and takes one of the following values: 'never' : Never. 'immediate' : Immediately, independently of any current or future attempts to authenticate using the PAE or MKA. 'authFail' : Not until an attempt has been made to authenticate using EAP, unless neither the Supplicant nor the Authenticator is enabled, and MKA has attempted to use any cached CAK (unless the KaY is not enabled).
.1.3.111.2.802.1.1.15.1.7.1.1.4,IEEE8021X-PAE-MIB::ieee8021XNidUnsecuredAllowed,INTEGER,read-create,,current,never(1):immediate(2):mkaFail(3):mkaServer(4),Determines when the Logon Process will tell the CP state machine to provide authenticated but unsecured connectivity, takes one of the following values: 'never' : Never. 'immediate' : Immediately, to provide connectivity concurrently with the use of MKA with any CAK acquired through EAP. 'mkaFail' : Not until MKA has failed, or is not enabled. 'mkaServer' : Only if directed by the MKA server.
.1.3.111.2.802.1.1.15.1.7.1.1.5,IEEE8021X-PAE-MIB::ieee8021XNidUnauthenticatedAccess,INTEGER,read-create,,current,noAccess(0):fallbackAccess(1):limitedAccess(2):openAccess(3),The configured access capability of the port's clients without authentication in this NID.
.1.3.111.2.802.1.1.15.1.7.1.1.6,IEEE8021X-PAE-MIB::ieee8021XNidAccessCapabilities,BITS,read-create,,current,eap(0):eapMka(1):eapMkaMacSec(2):mka(3):mkaMacSec(4):higherLayer(5):higherLayerFallback(6):vendorSpecific(7),The authentication and protection capabilities supported for the NID.
.1.3.111.2.802.1.1.15.1.7.1.1.7,IEEE8021X-PAE-MIB::ieee8021XNidKMD,OCTET,read-create,,current,,The configured KMD information for this NID.
.1.3.111.2.802.1.1.15.1.7.1.1.8,IEEE8021X-PAE-MIB::ieee8021XNidRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object to create the parameters for the supported Network Announcement information in the system. If the Network Announcement information of the entry is from downloaded policies, this object is 'active'.
.1.3.111.2.802.1.1.15.1.7.2,IEEE8021X-PAE-MIB::ieee8021XAnnounceTable,,not-accessible,,current,,A table contains the status information that the Announcers announce in the network announcement of the PAE system. This table will be instantiated if the object ieee8021XPaePortAnnouncerEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'.
.1.3.111.2.802.1.1.15.1.7.2.1,IEEE8021X-PAE-MIB::ieee8021XAnnounceEntry,,not-accessible,ieee8021XPaePortNumber:IMPLIEDieee8021XAnnounceNID,current,,An entry contains an Announcer's status information.
.1.3.111.2.802.1.1.15.1.7.2.1.1,IEEE8021X-PAE-MIB::ieee8021XAnnounceNID,OCTET,not-accessible,,current,,The NID information to identify a transmitting network announcement for the PAE.
.1.3.111.2.802.1.1.15.1.7.2.1.2,IEEE8021X-PAE-MIB::ieee8021XAnnounceAccessStatus,INTEGER,read-only,,current,noAccess(0):remedialAccess(1):restrictedAccess(2):expectedAccess(3),The object information reflects connectivity as a result of authentication attempts of this NID for this Announcer.
.1.3.111.2.802.1.1.15.1.7.3,IEEE8021X-PAE-MIB::ieee8021XAnnouncementTable,,not-accessible,,current,,A table contains the status information that the Listeners receive in the network announcement of the PAE system. This table will be instantiated if the object ieee8021XPaePortListenerEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'.
.1.3.111.2.802.1.1.15.1.7.3.1,IEEE8021X-PAE-MIB::ieee8021XAnnouncementEntry,,not-accessible,ieee8021XPaePortNumber:IMPLIEDieee8021XAnnouncementNID,current,,An entry contains a Listener's status information.
.1.3.111.2.802.1.1.15.1.7.3.1.1,IEEE8021X-PAE-MIB::ieee8021XAnnouncementNID,OCTET,not-accessible,,current,,The NID information to identify a received network announcement for the PAE.
.1.3.111.2.802.1.1.15.1.7.3.1.2,IEEE8021X-PAE-MIB::ieee8021XAnnouncementKMD,OCTET,read-only,,current,,The KMD information for this received network announcement of the PAE.
.1.3.111.2.802.1.1.15.1.7.3.1.3,IEEE8021X-PAE-MIB::ieee8021XAnnouncementSpecific,INTEGER,read-only,,current,true(1):false(2),This object indicates the received announcement information was specific to the receiving PAE, not generic for all systems attached to the LAN.
.1.3.111.2.802.1.1.15.1.7.3.1.4,IEEE8021X-PAE-MIB::ieee8021XAnnouncementAccessStatus,INTEGER,read-only,,current,noAccess(0):remedialAccess(1):restrictedAccess(2):expectedAccess(3),The object information reflects connectivity as a result of authentication attempts for this received network announcement of the PAE.
.1.3.111.2.802.1.1.15.1.7.3.1.5,IEEE8021X-PAE-MIB::ieee8021XAnnouncementAccessRequested,INTEGER,read-only,,current,true(1):false(2),The authenticated access has been requested for this particular NID or not.
.1.3.111.2.802.1.1.15.1.7.3.1.6,IEEE8021X-PAE-MIB::ieee8021XAnnouncementUnauthAccess,INTEGER,read-only,,current,noAccess(0):fallbackAccess(1):limitedAccess(2):openAccess(3),The access capability of the port's clients without authentication in this received network announcement of the PAE. 'openAccess', 'limitedAccess' should not be returned if the object ieee8021XNidUnauthAllowed is 'immediate'.
.1.3.111.2.802.1.1.15.1.7.3.1.7,IEEE8021X-PAE-MIB::ieee8021XAnnouncementCapabilities,BITS,read-only,,current,eap(0):eapMka(1):eapMkaMacSec(2):mka(3):mkaMacSec(4):higherLayer(5):higherLayerFallback(6):vendorSpecific(7),The announcement capabilities of this received network announcement for this PAE.
.1.3.111.2.802.1.1.15.1.7.4,IEEE8021X-PAE-MIB::ieee8021XAnnouncementCipherSuitesTable,,not-accessible,,current,,A table contains the Cipher Suites information that the Listeners receive in the network announcement of the PAE system. This table will be instantiated if the object ieee8021XPaePortListenerEnable in the corresponding entry of the ieee8021XPaePortTable is 'true'.
.1.3.111.2.802.1.1.15.1.7.4.1,IEEE8021X-PAE-MIB::ieee8021XAnnouncementCipherSuitesEntry,,not-accessible,ieee8021XPaePortNumber:ieee8021XAnnouncementNID:ieee8021XAnnouncementCipherSuite,current,,An entry contains the Cipher Suite information which a Listener has reveived from network announcement.
.1.3.111.2.802.1.1.15.1.7.4.1.1,IEEE8021X-PAE-MIB::ieee8021XAnnouncementCipherSuite,OCTET,not-accessible,,current,,The identifier for the announced cipher suite. This is a global unique 64-bit (EUI-64) identifier to identify a cipher suite.
.1.3.111.2.802.1.1.15.1.7.4.1.2,IEEE8021X-PAE-MIB::ieee8021XAnnouncementCipherCapability,Unsigned32,read-only,,current,,The capability of a Cipher Suite received from the network announcement by the Listener. A 2 octets Cipher Suite dependent implementation capability field precedes each Cipher Suite reference number. If the Cipher Suite, ieee8021XAnnouncementCipherSuite, identifies the Default Cipher Suite (specified in IEEE Std 802.1AE), the two least significant bits of the implementation capability field encode the MACsec Capability parameter specified in Table 11-7 and the fourteen more significant bits are as 0 and ignored on receipt.
.1.3.111.2.802.1.1.15.2,IEEE8021X-PAE-MIB::ieee8021XPaeMIBConformance,,,,,,
.1.3.111.2.802.1.1.15.2.1,IEEE8021X-PAE-MIB::ieee8021XPaeCompliances,,,,,,
.1.3.111.2.802.1.1.15.2.1.1,IEEE8021X-PAE-MIB::ieee8021XPaeCompliance,,,,,,The compliance statement for device support of Port Access Control.
.1.3.111.2.802.1.1.15.2.1.2,IEEE8021X-PAE-MIB::ieee8021XPaeV2Compliance,,,,,,The compliance statement for device support of Port Access Control as specified in 802.1X-2010 amended by 802.1Xbx.
.1.3.111.2.802.1.1.15.2.2,IEEE8021X-PAE-MIB::ieee8021XPaeGroups,,,,,,
.1.3.111.2.802.1.1.15.2.2.1,IEEE8021X-PAE-MIB::ieee8021XPaeSystemGroup,,,,,,A collection of objects providing system information for a PAE system and a PAE port status and control information.
.1.3.111.2.802.1.1.15.2.2.2,IEEE8021X-PAE-MIB::ieee8021XPacGroup,,,,,,A collection of objects providing information of a PAC in the system.
.1.3.111.2.802.1.1.15.2.2.3,IEEE8021X-PAE-MIB::ieee8021XPaeLogonGroup,,,,,,A collection of objects providing information of a Logon Process in the system.
.1.3.111.2.802.1.1.15.2.2.4,IEEE8021X-PAE-MIB::ieee8021XPaeAuthConfigGroup,,,,,,A collection of objects providing configuration information of an Authenticator in the system.
.1.3.111.2.802.1.1.15.2.2.5,IEEE8021X-PAE-MIB::ieee8021XPaeSuppConfigGroup,,,,,,A collection of objects providing configuration information of a Supplicant in the system.
.1.3.111.2.802.1.1.15.2.2.6,IEEE8021X-PAE-MIB::ieee8021XPaeEapolStatsGroup,,,,,,A collection of objects providing counters and diagnostic information for the EAPOL in the system.
.1.3.111.2.802.1.1.15.2.2.7,IEEE8021X-PAE-MIB::ieee8021XPaeKaYMkaGroup,,,,,,A collection of objects providing monitoring and controlling information of a KaY MKA in the system.
.1.3.111.2.802.1.1.15.2.2.8,IEEE8021X-PAE-MIB::ieee8021XPaeNetworkIdentifierGroup,,,,,,A collection of objects providing monitoring and controlling information of an NID in the system.
.1.3.111.2.802.1.1.15.2.2.9,IEEE8021X-PAE-MIB::ieee8021XPaeAnnouncerGroup,,,,,,A collection of objects providing status information for an Announcer in the system.
.1.3.111.2.802.1.1.15.2.2.10,IEEE8021X-PAE-MIB::ieee8021XPaeListenerGroup,,,,,,A collection of objects providing status information for a Listener in the system.
.1.3.111.2.802.1.1.15.2.2.11,IEEE8021X-PAE-MIB::ieee8021XPaeKaYIsupgradeGroup,,,,,,A collection of objects providing monitoring and control for MKA support of in-service upgrades.
.1.3.111.2.802.1.1.16,IEEE8021-FQTSS-MIB::ieee8021FqtssMib,,,,,,The Bridge MIB module for managing devices that support the Forwarding and Queuing Enhancements for Time Sensitive Streams. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.16.0,IEEE8021-FQTSS-MIB::ieee8021FqtssNotifications,,,,,,
.1.3.111.2.802.1.1.16.1,IEEE8021-FQTSS-MIB::ieee8021FqtssObjects,,,,,,
.1.3.111.2.802.1.1.16.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBap,,,,,,
.1.3.111.2.802.1.1.16.1.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBapTable,,not-accessible,,current,,A table containing a set of bandwidth availability parameters for each traffic class that supports the credit-based shaper algorithm. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.16.1.1.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBapEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021FqtssBAPTrafficClass,current,,A list of objects containing bandwidth allocation information for each traffic class that supports the credit-based shaper algorithm. Rows in the table are automatically created and deleted as a result of the operation of the algorithm described in 34.5. 
.1.3.111.2.802.1.1.16.1.1.1.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBAPTrafficClass,Unsigned32,not-accessible,,current,,The traffic class number associated with the row of the table. A row in this table is created for each traffic class that supports the credit-based shaper algorithm. The recommended mappings of priorities to traffic classes for support of the credit-based shaper algorithm are described in 34.5.
.1.3.111.2.802.1.1.16.1.1.1.1.2,IEEE8021-FQTSS-MIB::ieee8021FqtssDeltaBandwidth,Unsigned32,read-write,,current,,The value of the deltaBandwidth parameter for the traffic class. This value is represented as a fixed point number scaled by a factor of 1,000,000; i.e., 100,000,000 (the maximum value) represents 100%. The default value of the deltaBandwidth parameter for the highest numbered traffic class that supports the credit-based shaper algorithm is 75%; for all lower numbered traffic classes that support the credit-based shaper algorithm the default value is 0%. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.1.1.1.3,IEEE8021-FQTSS-MIB::ieee8021FqtssOperIdleSlopeMs,Unsigned32,read-only,,current,,The most significant 32 bits of the bandwidth, in bits per second, that is currently allocated to the traffic class (idleSlope(N)). This object MUST be read at the same time as ieee8021FqtssOperIdleSlopeLs, which represents the LS 32 bits of the value, in order for the read operation to succeed. If SRP is supported and in operation, then the reserved bandwidth is determined by the operation of SRP; otherwise, the value of ieee8021FqtssOperIdleSlopeMs is equal to the value of ieee8021FqtssAdminIdleSlopeMs. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.1.1.1.4,IEEE8021-FQTSS-MIB::ieee8021FqtssOperIdleSlopeLs,Unsigned32,read-only,,current,,The least significant 32 bits of the bandwidth, in bits per second, that is currently allocated to the traffic class (idleSlope(N)). This object MUST be read at the same time as ieee8021FqtssOperIdleSlopeMs, which represents the LS 32 bits of the value, in order for the read operation to succeed. If SRP is supported and in operation, then the reserved bandwidth is determined by the operation of SRP; otherwise, the value of ieee8021FqtssOperIdleSlopeLs is equal to the value of ieee8021FqtssAdminIdleSlopeMs. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.1.1.1.5,IEEE8021-FQTSS-MIB::ieee8021FqtssAdminIdleSlopeMs,Unsigned32,read-write,,current,,The most significant 32 bits of the bandwidth, in bits per second, that the manager desires to allocate to the traffic class as idleSlope(N). This object MUST be read or written at the same time as ieee8021FqtssAdminIdleSlopeLs, which represents the LS 32 bits of the value, in order for the read or write operation to succeed. If SRP is supported and in operation, then the reserved bandwidth is determined by the operation of SRP, and any changes to the value of this object have no effect on the operational value of idleSlope(N). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.1.1.1.6,IEEE8021-FQTSS-MIB::ieee8021FqtssAdminIdleSlopeLs,Unsigned32,read-write,,current,,The least significant 32 bits of the bandwidth, in bits per second, that the manager desires to allocate to the traffic class as idleSlope(N). This object MUST be read or written at the same time as ieee8021FqtssAdminIdleSlopeMs, which represents the LS 32 bits of the value, in order for the read or write operation to succeed. If SRP is supported and in operation, then the reserved bandwidth is determined by the operation of SRP, and any changes to the value of this object have no effect on the operational value of idleSlope(N). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.1.1.1.7,IEEE8021-FQTSS-MIB::ieee8021FqtssBapRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Indicates the status of an entry (row) in this table, and is used to create/delete entries. The corresponding instances of the following objects must be set before this object can be made active(1): ieee8021FqtssBAPTrafficClass ieee8021FqtssDeltaBandwidth ieee8021FqtssOperIdleSlopeMs ieee8021FqtssOperIdleSlopeLs ieee8021FqtssAdminIdleSlopeMs ieee8021FqtssAdminIdleSlopeLs The corresponding instances of the following objects may not be changed while this object is active(1): ieee8021FqtssBAPTrafficClass
.1.3.111.2.802.1.1.16.1.2,IEEE8021-FQTSS-MIB::ieee8021FqtssMappings,,,,,,
.1.3.111.2.802.1.1.16.1.2.1,IEEE8021-FQTSS-MIB::ieee8021FqtssTxSelectionAlgorithmTable,,not-accessible,,current,,A table containing the assignment of transmission selection algorithms to traffic classes for the Port. This table provides management of the Transmission Selection Algorithm Table defined in 8.6.8. For a given Port, a row in the table exists for each traffic class that is supported by the Port. The default assignments of transmission selection algorithms to traffic classes in the table are made on instantiation of the table, in accordance with the defaults defined in 8.6.8 and 34.5. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.16.1.2.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssTxSelectionAlgorithmEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021FqtssTrafficClass,current,,A list of objects that contain the mapping of a traffic class value to a transmission selection algorithm value.
.1.3.111.2.802.1.1.16.1.2.1.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssTrafficClass,Unsigned32,not-accessible,,current,,The traffic class to which the transmission selection algorithm is assigned. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.2.1.1.2,IEEE8021-FQTSS-MIB::ieee8021FqtssTxSelectionAlgorithmID,Unsigned32,read-write,,current,,The identifier of the transmission selection algorithm assigned to the traffic class. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.2.2,IEEE8021-FQTSS-MIB::ieee8021FqtssSrpRegenOverrideTable,,not-accessible,,current,,A table containing the set of priority regeneration table override values for the Port. The recommended default values of priorities associated with SR classes, and the corresponding override values, are defined in 6.9.4. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.16.1.2.2.1,IEEE8021-FQTSS-MIB::ieee8021FqtssSrpRegenOverrideEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021FqtssSrClassPriority,current,,A list of objects that contain the mapping of a priority value to a priority regeneration override value, and a boundary port indication. Rows in the table exist for all priorities that are associated with SR classes.
.1.3.111.2.802.1.1.16.1.2.2.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssSrClassPriority,Unsigned32,not-accessible,,current,,The priority value that is overridden at the SRP domain boundary. 
.1.3.111.2.802.1.1.16.1.2.2.1.2,IEEE8021-FQTSS-MIB::ieee8021FqtssPriorityRegenOverride,Unsigned32,read-write,,current,,The priority value that is used to override the priority regeneration table entry at the SRP domain boundary. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.2.2.1.3,IEEE8021-FQTSS-MIB::ieee8021FqtssSrpBoundaryPort,INTEGER,read-only,,current,true(1):false(2),The value of the SRPdomainBoundaryPort parameter (35.1.4) for the priority. 
.1.3.111.2.802.1.1.16.1.2.3,IEEE8021-FQTSS-MIB::ieee8021FqtssSRClassToPriorityTable,,not-accessible,,current,,A table containing the mapping of the SR Class to the associated priority. The default values for the entries of this table are specified in 34.5
.1.3.111.2.802.1.1.16.1.2.3.1,IEEE8021-FQTSS-MIB::ieee8021FqtssSRClassToPriorityEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021FqtssSrClassPriority,current,,This attribute holds the Data Frame Priority (35.2.2.8.5(a)) value that will be used for streams that belong to the associated SR class.
.1.3.111.2.802.1.1.16.1.2.3.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssSRClassToPrioritySrClassID,Unsigned32,read-create,,current,,The srClassId attribute provides the SR class ID from Table 35-7 of 35.2.2.9.2, so that management software can associate the traffic class to the corresponding SR class A or B used by protocols such as SRP. The default values for this attribute use the default values specified in 34.5 (i.e. Priority 3 for SRclassID 6 and Priority 2 for SRclassID 5). If this managed object is not supported, the default values specified in 34.5 are used as the fixed configuration.
.1.3.111.2.802.1.1.16.1.2.3.1.2,IEEE8021-FQTSS-MIB::ieee8021FqtssSRClassToPriorityRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),Indicates the status of an entry (row) in this table, and is used to create/delete entries.
.1.3.111.2.802.1.1.16.1.3,IEEE8021-FQTSS-MIB::ieee8021FqtssBapX,,,,,,
.1.3.111.2.802.1.1.16.1.3.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBapXTable,,not-accessible,,current,,A table containing a set of bandwidth availability parameters for each traffic class configured for use with time-sensitive streams. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.16.1.3.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBapXEntry,,not-accessible,,current,,A list of objects containing bandwidth allocation information for each traffic class configured for use with time-sensitive streams. Rows in the table are automatically created and deleted as a result of the operation of the algorithm described in 34.5.
.1.3.111.2.802.1.1.16.1.3.1.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBAPClassMeasurementInterval,Unsigned32,read-create,,current,,The value of the ClassMeasurementInterval parameter for the traffic class. This attribute uses units of nanoseconds, converted to/from units of seconds for use in 34.3. If management of classMeasurementInterval is not supported, the default values (34.5) are used as the fixed Port configuration. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.16.1.3.1.1.2,IEEE8021-FQTSS-MIB::ieee8021FqtssBAPLockClassBandwidth,INTEGER,read-create,,current,true(1):false(2),This attribute determines the interpretation of deltaBandwidth. For the value false(2), deltaBandwidth is specified in 34.3.1. For true(1), deltaBandwidth is specified in 34.3.2
.1.3.111.2.802.1.1.16.2,IEEE8021-FQTSS-MIB::ieee8021FqtssConformance,,,,,,
.1.3.111.2.802.1.1.16.2.1,IEEE8021-FQTSS-MIB::ieee8021FqtssCompliances,,,,,,
.1.3.111.2.802.1.1.16.2.1.1,IEEE8021-FQTSS-MIB::ieee8021FqtssCompliance,,,,,,The compliance statement for devices supporting forwarding and queuing for time sensitive streams. Support of the objects defined in the IEEE8021-FQTSS MIB also requires support of the IEEE8021-BRIDGE-MIB; the provisions of 17.3.2 apply to implementations claiming support of the IEEE8021-FQTSS MIB. 
.1.3.111.2.802.1.1.16.2.2,IEEE8021-FQTSS-MIB::ieee8021FqtssGroups,,,,,,
.1.3.111.2.802.1.1.16.2.2.1,IEEE8021-FQTSS-MIB::ieee8021FqtssBapGroup,,,,,,Objects that define bandwidth allocation for FQTSS.
.1.3.111.2.802.1.1.16.2.2.2,IEEE8021-FQTSS-MIB::ieee8021FqtssTxSelectionAlgorithmGroup,,,,,,Objects that define transmission selection mappings for FQTSS.
.1.3.111.2.802.1.1.16.2.2.3,IEEE8021-FQTSS-MIB::ieee8021FqtssBoundaryPortGroup,,,,,,Objects that define boundary port priority override mappings for FQTSS.
.1.3.111.2.802.1.1.16.2.2.4,IEEE8021-FQTSS-MIB::ieee8021FqtssBapMeasurementGroup,,,,,,Objects that define the SRP TSpec measurement interval and deltaBandwidth interpretation for FQTSS.
.1.3.111.2.802.1.1.16.2.2.5,IEEE8021-FQTSS-MIB::ieee8021FqtssSRClassPriorityGroup,,,,,,Objects that define mappings of the SR class ID to the associated priority for FQTSS.
.1.3.111.2.802.1.1.17,IEEE8021-DEVID-MIB::ieee8021DevIDMIB,,,,,,The MIB module for managing an IEEE 802.1AR DevID (Secure Device
.1.3.111.2.802.1.1.17.0,IEEE8021-DEVID-MIB::devIDMIBNotifications,,,,,,
.1.3.111.2.802.1.1.17.1,IEEE8021-DEVID-MIB::devIDMIBObjects,,,,,,
.1.3.111.2.802.1.1.17.1.1,IEEE8021-DEVID-MIB::devIDGlobalMIBObjects,,,,,,
.1.3.111.2.802.1.1.17.1.2,IEEE8021-DEVID-MIB::devIDMgmtMIBObjects,,,,,,
.1.3.111.2.802.1.1.17.1.2.1,IEEE8021-DEVID-MIB::devIDPublicKeyCount,Unsigned32,read-only,,obsolete,,The total number of DevID public keys installed in the module. Obsolete: the number of currently installed keys is the number of  DevIDCertEntry's with the module's entPhysicalIndex and distinct  devIDCertPublicKeyInfoFprint values, the maximum number can be an implementation dependent function of the keys' signature suites and  the storage occupied by certificates and certificate chains.
.1.3.111.2.802.1.1.17.1.2.2,IEEE8021-DEVID-MIB::devIDPublicKeyTable,,not-accessible,,obsolete,,A table containing the public key, the keys keyIndex, a value
.1.3.111.2.802.1.1.17.1.2.2.1,IEEE8021-DEVID-MIB::devIDPublicKeyEntry,,not-accessible,entPhysicalIndex,obsolete,,An entry containing DevID public key, the keys keyIndex, a value
.1.3.111.2.802.1.1.17.1.2.2.1.1,IEEE8021-DEVID-MIB::devIDPublicKeyIndex,Unsigned32,not-accessible,,obsolete,,All keys are indexed internally with this object. The  value of this object is within 0..devIDPublicKeyCount. This is the
.1.3.111.2.802.1.1.17.1.2.2.1.2,IEEE8021-DEVID-MIB::devIDPublicKeyEnabled,INTEGER,read-write,,obsolete,true(1):false(2),The enable/disable state of this public key. This  setting persists across restarts. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.2.1.3,IEEE8021-DEVID-MIB::devIDPublicKeyAlgorithm,INTEGER,read-only,,obsolete,rsaEncryption(1):idecPublicKey(2),The DevID PublicKey Algorithm field shall indicate the public key
.1.3.111.2.802.1.1.17.1.2.2.1.4,IEEE8021-DEVID-MIB::devIDPublicKeyPubkeySHA1Hash,OCTET,read-only,,obsolete,,The SHA1 Hash of this DevID public key. Obsolete with table. DevIDFingerprint used in new table objects to provided allow hash flexibility without MIB update.
.1.3.111.2.802.1.1.17.1.2.2.1.5,IEEE8021-DEVID-MIB::devIDPublicKeyErrStatus,INTEGER,read-only,,obsolete,none(1):internalError(2),Displays the status of an operation on the public key.  The default value is none which means no error, indicating a  successful operation. Obsolete: DevID module service interface  operations are not visible in this MIB so this object provides no clue as to what has failed and does not specify whether it is  cleared by subsequent successful operations. If keys or certs are unusable they should not be visible to SNMP or appear not enabled. In  both cases this read-only MIB cannot diagnose or repair. SNMP  operations already have their own error codes.
.1.3.111.2.802.1.1.17.1.2.3,IEEE8021-DEVID-MIB::devIDCredentialCount,Unsigned32,read-only,,obsolete,,This gives the total number of DevID credentials  installed in the DevID module. Obsolete: Object is not indexed by entPhysicalIndex so is not a per module count if the agent is  managing multiple devices. Changes as component devices are added or removed are not meaningful without other information. Per module counts can be obtained by interrogating the devIDCertTable.
.1.3.111.2.802.1.1.17.1.2.4,IEEE8021-DEVID-MIB::devIDCredentialTable,,not-accessible,,obsolete,,A table of current DevID credentials, where for each  certificate the following are indicated: sha1 hash of the  certificate, section7 defined fields of cert serial number, issuer, subject, HardwareModuleName, and public key. Obsolete: the ASN.1 encoding of a certificate is already defined  elsewhere, there is no need to require a device to decode the certificate into a different ASN.1 structure, and picking particular  field might omit problematic extensions in particular certificates.
.1.3.111.2.802.1.1.17.1.2.4.1,IEEE8021-DEVID-MIB::devIDCredentialEntry,,not-accessible,devIDCredentialIndex,obsolete,,An entry containing DevID Credential information. Obsolete: Table entries are not indexed by entPhysicalIndex.
.1.3.111.2.802.1.1.17.1.2.4.1.1,IEEE8021-DEVID-MIB::devIDCredentialIndex,Unsigned32,not-accessible,,obsolete,,All credentials are indexed internally with this  object. The value of this object is in [0..devIDCredentialCount]. Operations on credentials will use the credentialIndex to address a  specific credential. The IDevID credential shall only be at index 0.  Additional operations on credentials use the credentialIndex to  address a specific credential. Obsolete: The SNP agent does not control or monitor individual  DevID service operations, an SNMP agent can manage a system that comprises multiple devices identified by the ENTITY-MIB and more  than one of those devices can have a DevID module with an IDevID. 
.1.3.111.2.802.1.1.17.1.2.4.1.2,IEEE8021-DEVID-MIB::devIDCredentialEnabled,INTEGER,read-write,,obsolete,true(1):false(2),The enable/disable state of this credential. This  setting persists across restarts. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.3,IEEE8021-DEVID-MIB::devIDCredentialSHA1Hash,OCTET,read-only,,obsolete,,The SHA1 Hash of this DevID credential. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.4,IEEE8021-DEVID-MIB::devIDCredentialSerialNumber,OCTET,read-only,,obsolete,,The serial number of the credential. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.5,IEEE8021-DEVID-MIB::devIDCredentialIssuer,OCTET,read-only,,obsolete,,The issuer field of the credential. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.6,IEEE8021-DEVID-MIB::devIDCredentialSubject,OCTET,read-only,,obsolete,,The subject field of the credential. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.7,IEEE8021-DEVID-MIB::devIDCredentialSubjectAltName,OCTET,read-only,,obsolete,,The subjectaltname field of the credential. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.8,IEEE8021-DEVID-MIB::devIDCredentialEntityIndex,Integer32,read-only,,obsolete,,This refers to the entPhysicalIndex in entPhysicalTable  to identify the associated physical entity. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.9,IEEE8021-DEVID-MIB::devIDCredentialPubkeyIndex,Unsigned32,read-only,,obsolete,,Has the appropriate devIDPublicKeyIndex value from  devIDPublicKeyTable to identify the public key information. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.4.1.10,IEEE8021-DEVID-MIB::devIDCredentialErrStatus,INTEGER,read-only,,obsolete,none(1):internalError(2),The displays the status of an operation on the credential. The default value is none which means no error,  indicating a successful operation. Obsolete with table.
.1.3.111.2.802.1.1.17.1.2.5,IEEE8021-DEVID-MIB::devIDStatisticsTable,,not-accessible,,current,,Counts of selected operations for each DevID module.
.1.3.111.2.802.1.1.17.1.2.5.1,IEEE8021-DEVID-MIB::devIDStatisticsEntry,,not-accessible,entPhysicalIndex,current,,Counts of selected operations for a DevID module.
.1.3.111.2.802.1.1.17.1.2.5.1.1,IEEE8021-DEVID-MIB::devIDStatisticKeyGenerationCount,Counter32,read-only,,current,,The number of LDevID key pairs generated by the  module. Discontinuities at system restart and counter rollover.
.1.3.111.2.802.1.1.17.1.2.5.1.2,IEEE8021-DEVID-MIB::devIDStatisticKeyInsertionCount,Counter32,read-only,,current,,The number of LDevID key pairs inserted into the module.  Discontinuities occur at system restart and counter rollover.
.1.3.111.2.802.1.1.17.1.2.5.1.3,IEEE8021-DEVID-MIB::devIDStatisticKeyDeletionCount,Counter32,read-only,,current,,The number of LDevID key pairs deleted by the module. 
.1.3.111.2.802.1.1.17.1.2.5.1.4,IEEE8021-DEVID-MIB::devIDStatisticCSRGenerationCount,Counter32,read-only,,deprecated,,The number of Certificate Signing Requests (CSR, RFC2986) generated by the module. Discontinuities occur at system  restart and counter rollover. Deprecated: the module does not necessarily have all the information to generate a meaningful CSR, and key and certificate insertion is not tied to prior CSR  generation. If required the signing operation can generate a CSR  though this is not required for LDevID insertion.
.1.3.111.2.802.1.1.17.1.2.5.1.5,IEEE8021-DEVID-MIB::devIDStatisticCredentialInsertionCount,Counter32,read-only,,obsolete,,The number of LDevID credential insertions. 
.1.3.111.2.802.1.1.17.1.2.5.1.6,IEEE8021-DEVID-MIB::devIDStatisticCredentialDeletionCount,Counter32,read-only,,obsolete,,The number of LDevID credential deletions. 
.1.3.111.2.802.1.1.17.1.2.5.1.7,IEEE8021-DEVID-MIB::devIDStatisticCertInsertionCount,Counter32,read-only,,current,,The number of LDevID certificate insertions. 
.1.3.111.2.802.1.1.17.1.2.5.1.8,IEEE8021-DEVID-MIB::devIDStatisticCertDeletionCount,Counter32,read-only,,current,,This number of LDevID certificate deletions. 
.1.3.111.2.802.1.1.17.1.2.6,IEEE8021-DEVID-MIB::devIDModuleTable,,not-accessible,,current,,A table of DevID module capabilities, which can differ for devices
.1.3.111.2.802.1.1.17.1.2.6.1,IEEE8021-DEVID-MIB::devIDModuleEntry,,not-accessible,entPhysicalIndex,current,,DevID module capabilities, indexed by the ENTITY MIB's
.1.3.111.2.802.1.1.17.1.2.6.1.1,IEEE8021-DEVID-MIB::devIDModuleSupportsLDevIDs,INTEGER,read-only,,current,true(1):false(2),True if the module supports the mandatory operations for LDevIDs.
.1.3.111.2.802.1.1.17.1.2.6.1.2,IEEE8021-DEVID-MIB::devIDModuleGeneratesLDevIDKeys,INTEGER,read-only,,current,true(1):false(2),True if the module supports LDevID key generation.
.1.3.111.2.802.1.1.17.1.2.6.1.3,IEEE8021-DEVID-MIB::devIDModuleInsertsLDevIDKeys,INTEGER,read-only,,current,true(1):false(2),True if the module supports LDevID key insertion.
.1.3.111.2.802.1.1.17.1.2.7,IEEE8021-DEVID-MIB::devIDCertTable,,not-accessible,,current,,A table of DevID certificates, indexed by
.1.3.111.2.802.1.1.17.1.2.7.1,IEEE8021-DEVID-MIB::devIDCertEntry,,not-accessible,entPhysicalIndex:devIDCertFingerprint,current,,DevID certificate objects, indexed by entPhysicalIndex 
.1.3.111.2.802.1.1.17.1.2.7.1.1,IEEE8021-DEVID-MIB::devIDCertFingerprint,OCTET,not-accessible,,current,,A fingerprint of the DevID certificate, identifying the  fingerprinting hash.
.1.3.111.2.802.1.1.17.1.2.7.1.2,IEEE8021-DEVID-MIB::devIDCertPublicKeyInfoFprint,OCTET,read-only,,current,,A fingerprint of the DevID certificate's  subjectPublicKeyInfo field, identifying the fingerprinting hash.
.1.3.111.2.802.1.1.17.1.2.7.1.3,IEEE8021-DEVID-MIB::devIDCertIDevID,INTEGER,read-only,,current,true(1):false(2),True if this is an IDevID Certificate.
.1.3.111.2.802.1.1.17.1.2.7.1.4,IEEE8021-DEVID-MIB::devIDCertKeyEnabled,INTEGER,read-only,,current,true(1):false(2),True if use of the DevID Secret for this certificate is enabled, allowing its use.
.1.3.111.2.802.1.1.17.1.2.7.1.5,IEEE8021-DEVID-MIB::devIDCertEnabled,INTEGER,read-only,,current,true(1):false(2),True if the certificate can be used.
.1.3.111.2.802.1.1.17.1.2.7.1.6,IEEE8021-DEVID-MIB::devIDCert,OCTET,read-only,,current,,The X.509 DevID certificate.
.1.3.111.2.802.1.1.17.1.2.8,IEEE8021-DEVID-MIB::devIDChainTable,,not-accessible,,current,,A table of DevID intermediate certificates, indexed by 
.1.3.111.2.802.1.1.17.1.2.8.1,IEEE8021-DEVID-MIB::devIDChainEntry,,not-accessible,entPhysicalIndex:devIDCertFingerprint:devIDChainCertIndex,current,,DevID intermediate certificate objects, indexed by 
.1.3.111.2.802.1.1.17.1.2.8.1.1,IEEE8021-DEVID-MIB::devIDChainCertIndex,Unsigned32,not-accessible,,current,,The position of this intermediate certificate in the certificate chain.
.1.3.111.2.802.1.1.17.1.2.8.1.2,IEEE8021-DEVID-MIB::devIDChainCertFingerprint,OCTET,read-only,,current,,A fingerprint of the intermediate certificate, identifying the  fingerprinting hash.
.1.3.111.2.802.1.1.17.1.2.8.1.3,IEEE8021-DEVID-MIB::devIDChainCert,OCTET,read-only,,current,,The X.509 intermediate certificate in a certificate chain.
.1.3.111.2.802.1.1.17.1.3,IEEE8021-DEVID-MIB::devIDStatsMIBObjects,,,,,,
.1.3.111.2.802.1.1.17.2,IEEE8021-DEVID-MIB::devIDMIBConformance,,,,,,
.1.3.111.2.802.1.1.17.2.1,IEEE8021-DEVID-MIB::devIDMIBCompliances,,,,,,
.1.3.111.2.802.1.1.17.2.1.1,IEEE8021-DEVID-MIB::devIDMIBModuleCompliance,,,,,,Module Compliance for DevID MIB-2009.
.1.3.111.2.802.1.1.17.2.1.2,IEEE8021-DEVID-MIB::devIDMIBModuleCompliance2,,,,,,Module Compliance for DevID MIB-2018.
.1.3.111.2.802.1.1.17.2.2,IEEE8021-DEVID-MIB::devIDMIBGroups,,,,,,
.1.3.111.2.802.1.1.17.2.2.1,IEEE8021-DEVID-MIB::devIDMIBObjectGroup,,,,,,A collection of objects providing public key  manageability, credential manageability and stats.
.1.3.111.2.802.1.1.17.2.2.2,IEEE8021-DEVID-MIB::devIDMIBModuleGroup,,,,,,DevID MIB objects describing module capabilities.
.1.3.111.2.802.1.1.17.2.2.3,IEEE8021-DEVID-MIB::devIDMIBCertificateGroup,,,,,,DevID MIB objects for DevID public key, certificate, and certificate chain inventory operations.
.1.3.111.2.802.1.1.17.2.2.4,IEEE8021-DEVID-MIB::devIDMIBAuditGroup,,,,,,DevID MIB objects supporting DevID operation auditing.
.1.3.111.2.802.1.1.18,IEEE8021-CN-MIB::ieee8021CnMib,,,,,,Congestion notification module. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.18.1,IEEE8021-CN-MIB::ieee8021CnMIBObjects,,,,,,
.1.3.111.2.802.1.1.18.1.1,IEEE8021-CN-MIB::ieee8021CnGlobalTable,,not-accessible,,current,,A table containing the global variables for each component of a Bridge or for an end station. A value of 1 is used in a Bridge or end station that does not have multiple components. The contents of this table SHALL be maintained across a restart of the system. 
.1.3.111.2.802.1.1.18.1.1.1,IEEE8021-CN-MIB::ieee8021CnGlobalEntry,,not-accessible,ieee8021CnGlobalComponentId,current,,A list of objects pertaining to a whole Bridge component or end station. 
.1.3.111.2.802.1.1.18.1.1.1.1,IEEE8021-CN-MIB::ieee8021CnGlobalComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnGlobalEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.1.1.2,IEEE8021-CN-MIB::ieee8021CnGlobalMasterEnable,INTEGER,read-write,,current,true(1):false(2),The state of the congestion notification feature on this Bridge component or system. If true, Congestion notification is enabled, and if false, congestion notification is disabled. 
.1.3.111.2.802.1.1.18.1.1.1.3,IEEE8021-CN-MIB::ieee8021CnGlobalCnmTransmitPriority,Unsigned32,read-write,,current,,The priority to use for all Congestion Notification Messages transmitted by this Bridge component or end station. 
.1.3.111.2.802.1.1.18.1.1.1.4,IEEE8021-CN-MIB::ieee8021CnGlobalDiscardedFrames,Counter64,read-only,,current,,The number of frames discarded from full CP queues, in spite of the efforts of congestion notification to avoid discards. This object is incremented whenever any of the ieee8021CnCpDiscardedFrames objects on any Port or priority in this same component are incremented. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any). 
.1.3.111.2.802.1.1.18.1.2,IEEE8021-CN-MIB::ieee8021CnErroredPortTable,,not-accessible,,current,,There is one Errored Port Table per Bridge component or end station. It permits the retrieval of information about which interfaces have congestion notification configuration errors, namely, those specifying an alternate priority that is a CNPV. 
.1.3.111.2.802.1.1.18.1.2.1,IEEE8021-CN-MIB::ieee8021CnErroredPortEntry,,not-accessible,ieee8021CnEpComponentId:ieee8021CnEpPriority:ieee8021CnEpIfIndex,current,,A list of interfaces whose ieee8021CnComPriAlternatePriority and/or ieee8021CnPortPriAlternatePriority specify a priority value that is a Congestion Notification Priority Value. 
.1.3.111.2.802.1.1.18.1.2.1.1,IEEE8021-CN-MIB::ieee8021CnEpComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnErroredPortEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.2.1.2,IEEE8021-CN-MIB::ieee8021CnEpPriority,Unsigned32,not-accessible,,current,,The priority value whose alternate priority is misconfigured. 
.1.3.111.2.802.1.1.18.1.2.1.3,IEEE8021-CN-MIB::ieee8021CnEpIfIndex,Integer32,read-only,,current,,This object represents the Bridge Port or aggregated port on which the congestion notification alternate priority is misconfigured. Upon a restart of the system, the system SHALL, if necessary, change the value of this variable so that it references the row in the ifXTable with the same value of ifAlias that it referenced before the system restart. If no such row exists, then the system SHALL delete this row in the ieee8021CnErroredPortTable. 
.1.3.111.2.802.1.1.18.1.3,IEEE8021-CN-MIB::ieee8021CnCompntPriTable,,not-accessible,,current,,Each row in this table supplies default values for one Congestion Notification Priority Value for a whole Bridge  component or end station. Creating a row in this table makes the priority value of ieee8021CnComPriPriority a Congestion Notification Priority Value. Deleting a row in this table makes the value in the deleted ieee8021CnComPriPriority no longer a Congestion Notification Priority Value. A system SHALL NOT allow eight rows in this table to be created with the same value of ieee8021CnComPriComponentId; see the description of ieee8021CnComPriRowStatus. The contents of this table SHALL be maintained across a restart of the system. 
.1.3.111.2.802.1.1.18.1.3.1,IEEE8021-CN-MIB::ieee8021CnCompntPriEntry,,not-accessible,ieee8021CnComPriComponentId:ieee8021CnComPriPriority,current,,One entry per Congestion Notification Priority Value per Bridge component or end station. 
.1.3.111.2.802.1.1.18.1.3.1.1,IEEE8021-CN-MIB::ieee8021CnComPriComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnCompntPriEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.3.1.2,IEEE8021-CN-MIB::ieee8021CnComPriPriority,Unsigned32,not-accessible,,current,,The Congestion Notification Priority Value for which this row supplies default values. 
.1.3.111.2.802.1.1.18.1.3.1.3,IEEE8021-CN-MIB::ieee8021CnComPriDefModeChoice,INTEGER,read-create,,current,cpcAdmin(1):cpcAuto(2),Specifies how the default CND defense mode and alternate priority for this Congestion Notification Priority Value on all ports on this Bridge component or end station are to be chosen, either: cpcAdmin(1) Default CND defense mode is chosen by ieee8021CnComPriAdminDefenseMode, and alternate priority by ieee8021CnComPriAlternatePriority. cpcAuto(2) Default CND defense mode is chosen by ieee8021CnPortPriAutoDefenseMode, and alternate priority by ieee8021CnComPriAutoAltPri. This variable can be overridden by ieee8021CnPortPriDefModeChoice. 
.1.3.111.2.802.1.1.18.1.3.1.4,IEEE8021-CN-MIB::ieee8021CnComPriAlternatePriority,Unsigned32,read-create,,current,,The Congestion Notification Priority Value to which an incoming frame is to be mapped, in spite of what the Priority Regereration Table says, if 1) Congestion Notification is enabled and 2) the CND defense mode of the port is cptEdge. Deleting a row in this table does not alter the value of any other row's ieee8021CnComPriAlternatePriority. 
.1.3.111.2.802.1.1.18.1.3.1.5,IEEE8021-CN-MIB::ieee8021CnComPriAutoAltPri,Unsigned32,read-only,,current,,The Congestion Notification Priority Value to which an incoming frame can be mapped, in spite of what the Priority Regereration Table says, if 1) Congestion Notification is enabled, 2) the CND defense mode of the port is cptEdge, and 3) ieee8021CnComPriDefModeChoice contains the value cpcAuto (2). The value of this object is the next lower priority value than this row's ieee8021CnComPriPriority that is not a CNPV, or the next higher non-CNPV, if all lower values are CNPVs. The value of this object, and any consequent priority regeneration, is automatically updated by the managed system whenever a row in the ieee8021CnCompntPriTable is created or deleted. The value of this object is not dependent upon whether congestion notification is enabled or disabled for any priority or for the whole Bridge component or end station; it depends only upon whether the ieee8021CnCompntPriTable row exists. 
.1.3.111.2.802.1.1.18.1.3.1.6,IEEE8021-CN-MIB::ieee8021CnComPriAdminDefenseMode,INTEGER,read-create,,current,cptDisabled(1):cptInterior(2):cptInteriorReady(3):cptEdge(4),The default CND defense mode for this Congestion Notification Priority Value on all ports on this Bridge component or end station. This variable can be overridden by ieee8021CnPortPriAdminDefenseMode. 
.1.3.111.2.802.1.1.18.1.3.1.7,IEEE8021-CN-MIB::ieee8021CnComPriCreation,INTEGER,read-create,,current,cncpAutoEnable(1):cncpAutoDisable(2),The default value for ieee8021CnComPriDefModeChoice for newly-created entries in the ieee8021CnPortPriTable: cncpAutoEnable (1) Newly-created ieee8021CnPortPriDefModeChoice objects take the value cpcComp (3). cncpAutoDisable(2) Newly-created ieee8021CnPortPriDefModeChoice objects take the value cpcAdmin (1). 
.1.3.111.2.802.1.1.18.1.3.1.8,IEEE8021-CN-MIB::ieee8021CnComPriLldpInstanceChoice,INTEGER,read-create,,current,cnlNone(1):cnlAdmin(2),Specifies whether or not the default value for all Ports is to send and receive the Congestion Notification TLV in LLDPDUs, either: cnlNone(1) Do not send Congestion Notification TLVs, and ignore them on receipt. cnlAdmin(2) Use the LLDP instance selected by ieee8021CnComPriLldpInstanceSelector to send and receive the Congestion Notification TLV. This object can be overridden by ieee8021CnPortPriLldpInstanceChoice. 
.1.3.111.2.802.1.1.18.1.3.1.9,IEEE8021-CN-MIB::ieee8021CnComPriLldpInstanceSelector,Unsigned32,read-create,,current,,Specifies a default value for which LLDP instance is to be used to provide the information for automatic configuration of ports' CND defense modes (ieee8021CnPortPriAutoDefenseMode). This object is ignored by the managed system if ieee8021CnComPriLldpInstanceChoice contains the value cnlNone (1). This object can be overridden by  ieee8021CnPortPriLldpInstanceChoice and ieee8021CnPortPriLldpInstanceChoice. 
.1.3.111.2.802.1.1.18.1.3.1.10,IEEE8021-CN-MIB::ieee8021CnComPriRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of an entry, and is used to create/delete entries. A system SHALL NOT permit eight ieee8021CnComPriRowStatus objects, all with the same value of ieee8021CnComPriComponentId, to have the value active(1). An attempt to create or activate a row when there are already seven active rows SHALL result in that eighth row's ieee8021CnComPriRowStatus having the value notReady(3), and the return of an inconsistentValue error. 
.1.3.111.2.802.1.1.18.1.4,IEEE8021-CN-MIB::ieee8021CnPortPriTable,,not-accessible,,current,,Each row in this table supplies values for one port's Congestion Notification Priority Value (CNPV). Creating an entry in ieee8021CnCompntPriTable creates this entry, with the default values, on all ports in the Bridge component or end station. Deleting an entry in ieee8021CnCompntPriTable deletes this ieee8021CnCompntPriEntry on all ports in the Bridge component or end station. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnPortPriIfIndex. 
.1.3.111.2.802.1.1.18.1.4.1,IEEE8021-CN-MIB::ieee8021CnPortPriEntry,,not-accessible,ieee8021CnPortPriComponentId:ieee8021CnPortPriority:ieee8021CnPortPriIfIndex,current,,One entry per port per Congestion Notification Priority Value per Bridge component or end station. 
.1.3.111.2.802.1.1.18.1.4.1.1,IEEE8021-CN-MIB::ieee8021CnPortPriComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnPortPriEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.4.1.2,IEEE8021-CN-MIB::ieee8021CnPortPriority,Unsigned32,not-accessible,,current,,The Congestion Notification Priority Value for which this row supplies default values. 
.1.3.111.2.802.1.1.18.1.4.1.3,IEEE8021-CN-MIB::ieee8021CnPortPriIfIndex,Integer32,not-accessible,,current,,This object represents the port or aggregated port to which the entry applies. Upon a restart of the system, the system SHALL, if necessary, change the value of this object, and rearrange the order of the ieee8021CnPortPriTable, so that the value in ieee8021CnPortPriIfIndex references the row in the ifXTable with the same value for ifAlias that it referenced before the system restart. If no such entry exists in the ifXTable, then the system SHALL delete the row in the ieee8021CnPortPriTable. 
.1.3.111.2.802.1.1.18.1.4.1.4,IEEE8021-CN-MIB::ieee8021CnPortPriDefModeChoice,INTEGER,read-write,,current,cpcAdmin(1):cpcAuto(2):cpcComp(3),This object determines how the CND defense mode and alternate priority value of this port for this CNPV is to be selected, either: cpcAdmin(1) CND defense mode is controlled by ieee8021CnPortPriAdminDefenseMode, and alternate priority by ieee8021CnPortPriAlternatePriority. cpcAuto(2) CND defense mode is controlled by ieee8021CnPortPriAutoDefenseMode and alternate priority by ieee8021CnComPriAlternatePriority. cpcComp(3) CND defense mode and alternate priority are controlled by ieee8021CnComPriDefModeChoice. This variable can override ieee8021CnComPriDefModeChoice. 
.1.3.111.2.802.1.1.18.1.4.1.5,IEEE8021-CN-MIB::ieee8021CnPortPriAdminDefenseMode,INTEGER,read-write,,current,cptDisabled(1):cptInterior(2):cptInteriorReady(3):cptEdge(4),This object indicates the operator's choice for the CND defense mode in which this port is to operate for this CNPV whenever ieee8021CnPortPriDefModeChoice has the value cpcAdmin(1). This variable can override ieee8021CnComPriDefModeChoice. 
.1.3.111.2.802.1.1.18.1.4.1.6,IEEE8021-CN-MIB::ieee8021CnPortPriAutoDefenseMode,INTEGER,read-only,,current,cptInterior(2):cptInteriorReady(3):cptEdge(4),This object indicates in which the CND defense mode this port would operate for this CNPV as determined by the LLDP Congestion Notification TLV. 
.1.3.111.2.802.1.1.18.1.4.1.7,IEEE8021-CN-MIB::ieee8021CnPortPriLldpInstanceChoice,INTEGER,read-write,,current,cnlNone(1):cnlAdmin(2):cnlComponent(3),Specifies how to determine the LLDP instance to be used for the Congestion Notification TLV, either: cnlNone(1) No LLDP Congestion Notification TLV is to carry Per-priority CNPV indicators or Per-priority Ready indicators on this Port for this priority. cnlAdmin(2) ieee8021CnPortPriLldpInstanceSelector governs which LLDP instance is to carry Per-priority CNPV indicators and Per-priority Ready indicators for this priority in its Congestion Notification TLV on this Port cnlComponent(3) ieee8021CnComPriLldpInstanceChoice governs LLDP instance selection for this Port and priority. This object can override ieee8021CnComPriLldpInstanceChoice. 
.1.3.111.2.802.1.1.18.1.4.1.8,IEEE8021-CN-MIB::ieee8021CnPortPriLldpInstanceSelector,Unsigned32,read-write,,current,,This object determines which LLDP instance selector, if any, is used for automatic determination of the CND defense mode for this port and CNPV. This object can override ieee8021CnComPriLldpInstanceSelector. 
.1.3.111.2.802.1.1.18.1.4.1.9,IEEE8021-CN-MIB::ieee8021CnPortPriAlternatePriority,Unsigned32,read-write,,current,,The Congestion Notification Priority Value to which an incoming frame is to be mapped, in spite of what the Priority Regereration Table says, if 1) Congestion Notification is enabled and 2) the port is acting in the cptEdge (4) CND defense mode. This object is ignored unless ieee8021CnPortPriDefModeChoice contains the value cpcAdmin (1). 
.1.3.111.2.802.1.1.18.1.5,IEEE8021-CN-MIB::ieee8021CnCpTable,,not-accessible,,current,,Each row in this table supplies values for one Congestion Point (CP). This table is indexed by component, port (interface), and an arbitrary CP index. This arbitrary CP index is not necessarily the Congestion Point Identifier (CPID) carried in Congestion Notification Messages (CNMs). Creating an entry in ieee8021CnCompntPriTable can create an entry in this table, with the default values, on all ports in the Bridge component or end station. Because more than one Congestion Notification Priority Value (CNPV) can flow through a single CP, the creation of an entry in ieee8021CnCompntPriTable does not necessarily create a new entry in this table. An end station can have more than one CP for the same CNPV, so creating an entry in ieee8021CnCompntPriTable can create multiple entries in this table. Because each port in a Bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. Deleting the last entry in ieee8021CnCompntPriTable for a CNPV passing through the CP controlled by this entry deletes the entry on some or all of the ports in the Bridge component or end station. Because each port in a Bridge component or end station can have a different relationship between CNPVs and CPs, the entries created or deleted on each port can be different. The relationship between ieee8021CnCpIndex values and CPs is an implementation dependent matter. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnCpIfIndex. 
.1.3.111.2.802.1.1.18.1.5.1,IEEE8021-CN-MIB::ieee8021CnCpEntry,,not-accessible,ieee8021CnCpComponentId:ieee8021CnCpIfIndex:ieee8021CnCpIndex,current,,An entry in the Congestion Point table controls a single Congestion Point on a port in a Bridge component or end station. 
.1.3.111.2.802.1.1.18.1.5.1.1,IEEE8021-CN-MIB::ieee8021CnCpComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnCpEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.5.1.2,IEEE8021-CN-MIB::ieee8021CnCpIfIndex,Integer32,not-accessible,,current,,This object represents the port or aggregated port to which the entry applies. Upon a restart of the system, the system SHALL, if necessary, change the value of this object, and rearrange the order of the ieee8021CnCpTable, so that the value in ieee8021CnCpIfIndex references the row in the ifXTable with the same value for ifAlias that it referenced before the system restart. If no such entry exists in the ifXTable, then the system SHALL delete the row in the ieee8021CnCpTable. 
.1.3.111.2.802.1.1.18.1.5.1.3,IEEE8021-CN-MIB::ieee8021CnCpIndex,Unsigned32,not-accessible,,current,,This object is an arbitrary integer indexing the entries in this table among the entries for the same component and interface. In a system that supports no more than one Congestion Point per priority per interface, ieee8021CnCpIndex SHALL be equal to the lowest numerical Congestion Notification Priority Value served by this Congestion Point. Otherwise, it SHOULD be a small integer value. 
.1.3.111.2.802.1.1.18.1.5.1.4,IEEE8021-CN-MIB::ieee8021CnCpPriority,Unsigned32,read-only,,current,,This object indicates the lowest numerical Congestion Notification Priority Value that this entry's Congestion Point serves. 
.1.3.111.2.802.1.1.18.1.5.1.5,IEEE8021-CN-MIB::ieee8021CnCpMacAddress,OCTET,read-only,,current,,This object indicates the MAC address used as the source address in Congestion Notification Message transmitted by this Congestion Point. 
.1.3.111.2.802.1.1.18.1.5.1.6,IEEE8021-CN-MIB::ieee8021CnCpIdentifier,OCTET,read-only,,current,,This object indicates the Congestion Point Identifier (CPID) transmitted in Congestion Notification Message by this Congestion Point. It is not specified whether the CPID reported in a CNM by a CP that serves multiple CNPVs does or does not have the same value for its different CNPVs. 
.1.3.111.2.802.1.1.18.1.5.1.7,IEEE8021-CN-MIB::ieee8021CnCpQueueSizeSetPoint,Unsigned32,read-write,,current,,This object is the set point for the queue managed by this Congestion Point (CP). Congestion Notification Messages are transmitted to the sources of frames queued in this CP's queue in order to keep the total number of octets stored in the queue at this set point. 
.1.3.111.2.802.1.1.18.1.5.1.8,IEEE8021-CN-MIB::ieee8021CnCpFeedbackWeight,Integer32,read-write,,current,,This object controls the weight (cpW) change in queue length in the calculation of cpFb when the Congestion Point is generating a Congestion Notification Message. The weight cpW is equal to two to the power of this object. Thus, if this object contains a -1, cpW = 1/2. 
.1.3.111.2.802.1.1.18.1.5.1.9,IEEE8021-CN-MIB::ieee8021CnCpMinSampleBase,Unsigned32,read-write,,current,,This object determines the minimum number of octets to enqueue in the Congestion Point's queue between transmissions of Congestion Notification Messages. 
.1.3.111.2.802.1.1.18.1.5.1.10,IEEE8021-CN-MIB::ieee8021CnCpDiscardedFrames,Counter64,read-only,,current,,The number of data frames discarded by the queue controlled by this Congestion Point due to queue congestion. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any). 
.1.3.111.2.802.1.1.18.1.5.1.11,IEEE8021-CN-MIB::ieee8021CnCpTransmittedFrames,Counter64,read-only,,current,,The number of data frames passed on to the queue controlled by this Congestion Point that were not discarded due to queue congestion. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any). 
.1.3.111.2.802.1.1.18.1.5.1.12,IEEE8021-CN-MIB::ieee8021CnCpTransmittedCnms,Counter64,read-only,,current,,The number of Congestion Notification Message transmitted by this Congestion Point. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any). 
.1.3.111.2.802.1.1.18.1.5.1.13,IEEE8021-CN-MIB::ieee8021CnCpMinHeaderOctets,Unsigned32,read-write,,current,,Specifies the minimum number of octets to be returned in a Congestion Notification Message from the mac_service_data_unit of the data frame that triggered transmission of the CNM. If the mac_service_data_unit has fewer octets than the value of this object, then all of the mac_service_data_unit is returned in the CNM. 
.1.3.111.2.802.1.1.18.1.6,IEEE8021-CN-MIB::ieee8021CnCpidToInterfaceTable,,not-accessible,,current,,This table allows the network manager to obtain the interface index and CP index needed to access an entry in the ieee8021CnCpTable, given a Congestion Point Identifier (CPID) received a Congestion Notification Messages (CNMs). Upon a restart of the system, the system SHALL, if necessary, update this table to be consistent with the ieee8021CnCpTable. 
.1.3.111.2.802.1.1.18.1.6.1,IEEE8021-CN-MIB::ieee8021CnCpidToInterfaceEntry,,not-accessible,ieee8021CnCpidToIfCpid,current,,An entry in the ieee8021CnCpidToInterfaceTable. Translates a Congestion Point Identifier to a component identifier, interface index, and CP index 
.1.3.111.2.802.1.1.18.1.6.1.1,IEEE8021-CN-MIB::ieee8021CnCpidToIfCpid,OCTET,not-accessible,,current,,This object is the Congestion Point Identifier (CPID) transmitted in Congestion Notification Message by a Congestion Point residing in this Bridge component or end station. 
.1.3.111.2.802.1.1.18.1.6.1.2,IEEE8021-CN-MIB::ieee8021CnCpidToIfComponentId,Unsigned32,read-only,,current,,The Bridge component within the system to which the information in this ieee8021CnCpidToInterfaceEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.6.1.3,IEEE8021-CN-MIB::ieee8021CnCpidToIfIfIndex,Integer32,read-only,,current,,This object indicates the interface on which the selected Congestion Point resides. This value can be used, along with ieee8021CnCpidToIfCpIndex, to find the Congestion Point in the ieee8021CnCpTable. 
.1.3.111.2.802.1.1.18.1.6.1.4,IEEE8021-CN-MIB::ieee8021CnCpidToIfCpIndex,Unsigned32,read-only,,current,,This object indicates the Congestion Point's index on the interface on which the selected Congestion Point resides. This value can be used, along with ieee8021CnCpidToIfIfIndex, to find the Congestion Point in the ieee8021CnCpTable. 
.1.3.111.2.802.1.1.18.1.7,IEEE8021-CN-MIB::ieee8021CnRpPortPriTable,,not-accessible,,current,,Each row in this table supplies values for all of the Reaction Points (RPs) on one Port and one priority of an end station or Bridge component. This table is indexed by component, port (interface), and priority. Creating an entry in ieee8021CnCompntPriTable can create an entry in this table, with the default values, on all ports in the end station. Deleting the an entry in ieee8021CnCompntPriTable for a CNPV passing through the RP controlled by this entry deletes entries on some or all of the ports in the end station. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnRpPortPriIfIndex. 
.1.3.111.2.802.1.1.18.1.7.1,IEEE8021-CN-MIB::ieee8021CnRpPortPriEntry,,not-accessible,ieee8021CnRpPortPriComponentId:ieee8021CnRpPortPriPriority:ieee8021CnRpPortPriIfIndex,current,,An entry in the Reaction Point table controls all of the Reaction Points on a port in an end station that share the same priority value. 
.1.3.111.2.802.1.1.18.1.7.1.1,IEEE8021-CN-MIB::ieee8021CnRpPortPriComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnRpGroupEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.7.1.2,IEEE8021-CN-MIB::ieee8021CnRpPortPriPriority,Unsigned32,not-accessible,,current,,This object indicates the lowest numerical Congestion Notification Priority Value that this entry's Reaction Point serves. 
.1.3.111.2.802.1.1.18.1.7.1.3,IEEE8021-CN-MIB::ieee8021CnRpPortPriIfIndex,Integer32,not-accessible,,current,,This object indicates the interface on which the selected Reaction Points reside. Upon a restart of the system, the system SHALL, if necessary, change the value of this object, and rearrange the order of the ieee8021CnRpPortPriTable, so that the value in ieee8021CnRpPortPriIfIndex references the row in the ifXTable with the same value for ifAlias that it referenced before the system restart. If no such entry exists in the ifXTable, then the system SHALL delete the row in the ieee8021CnRpPortPriTable. 
.1.3.111.2.802.1.1.18.1.7.1.4,IEEE8021-CN-MIB::ieee8021CnRpPortPriMaxRps,Unsigned32,read-write,,current,,An integer controlling the maximum number of Reaction Points allowed for this CNPV on this Port. An end station SHALL not create more than this many Reaction Point on this Port, but it MAY create fewer. 
.1.3.111.2.802.1.1.18.1.7.1.5,IEEE8021-CN-MIB::ieee8021CnRpPortPriCreatedRps,Counter32,read-only,,current,,This object returns the number of times any of the Reaction Points (RPs) controlled by this entry has had its rpEnabled variable set TRUE by the reception of a Congestion Notification Message. Dividing the change in ieee8021CnRpPortPriCentiseconds by the change in this object over a time interval yields the average lifetime of an active RP during that interval. 
.1.3.111.2.802.1.1.18.1.7.1.6,IEEE8021-CN-MIB::ieee8021CnRpPortPriCentiseconds,Counter64,read-only,,current,,This object returns the total number of centi-seconds that any of the Reaction Points (RPs) controlled by this entry has had its rpEnabled variable in the TRUE state. That is, once each centi-second, this counter is incremented by the number of RPs this entry controls that are actively rate limiting output frames. Dividing the change in this object over a time interval by the length of the interval yields the average number of RPs active over that interval. Dividing the change in this object by the change in ieee8021CnRpPortPriCreatedRps over that same time interval yields the average lifetime of an active RP during that interval. 
.1.3.111.2.802.1.1.18.1.8,IEEE8021-CN-MIB::ieee8021CnRpGroupTable,,not-accessible,,current,,Each row in this table supplies values for one or more Reaction Points (RPs). This table is indexed by component, port (interface), and an arbitrary RP index. Creating an entry in ieee8021CnCompntPriTable can create an entry in this table, with the default values, on all ports in the end station. An end station can have more than one RP for the same Congestion Notification Priority Value (CNPV), so creating an entry in ieee8021CnCompntPriTable can create multiple entries in this table. Because each port in a Bridge component or end station can have a different relationship between CNPVs and RPs, the entries created or deleted on each port can be different. Deleting the an entry in ieee8021CnCompntPriTable for a CNPV passing through the RP controlled by this entry deletes entries on some or all of the ports in the end station. Because each port in an end station can have a different relationship between CNPVs and RPs, the entries created or deleted on each port can be different. The relationship between ieee8021CnRpgIdentifier values and RPs is an implementation dependent matter. The contents of this table SHALL be maintained across a restart of the system, except as noted in the description of ieee8021CnRpgIfIndex. 
.1.3.111.2.802.1.1.18.1.8.1,IEEE8021-CN-MIB::ieee8021CnRpGroupEntry,,not-accessible,ieee8021CnRpgComponentId:ieee8021CnRpgPriority:ieee8021CnRpgIfIndex:ieee8021CnRpgIdentifier,current,,An entry in the Reaction Point table controls a group of Reaction Points, on a port in an end station. All of the Reaction Point controlled by this entry serve the same Congestion Notification Priority Value. 
.1.3.111.2.802.1.1.18.1.8.1.1,IEEE8021-CN-MIB::ieee8021CnRpgComponentId,Unsigned32,not-accessible,,current,,The Bridge component within the system to which the information in this ieee8021CnRpGroupEntry applies. If the system is not a Bridge, or if only one component is present in the Bridge, then this variable (index) MUST be equal to 1. 
.1.3.111.2.802.1.1.18.1.8.1.2,IEEE8021-CN-MIB::ieee8021CnRpgPriority,Unsigned32,not-accessible,,current,,This object indicates the lowest numerical Congestion Notification Priority Value that this entry's Reaction Point serves. 
.1.3.111.2.802.1.1.18.1.8.1.3,IEEE8021-CN-MIB::ieee8021CnRpgIfIndex,Integer32,not-accessible,,current,,This object indicates the interface on which the group of Reaction Points reside. Upon a restart of the system, the system SHALL, if necessary, change the value of this object, and rearrange the order of the ieee8021CnRpGroupTable, so that the value in ieee8021CnRpgIfIndex references the row in the ifXTable with the same value for ifAlias that it referenced before the system restart. If no such entry exists in the ifXTable, then the system SHALL delete the row in the ieee8021CnRpGroupTable. 
.1.3.111.2.802.1.1.18.1.8.1.4,IEEE8021-CN-MIB::ieee8021CnRpgIdentifier,Unsigned32,not-accessible,,current,,This object is an arbitrary integer indexing the entries in this table among the entries for the same interface. This index SHOULD, where possible, be equal to the Congestion Notification Priority Value served by this Reaction Point. 
.1.3.111.2.802.1.1.18.1.8.1.5,IEEE8021-CN-MIB::ieee8021CnRpgEnable,INTEGER,read-write,,current,true(1):false(2),Controls the rpEnabled variable of the Reaction Point state machines of the Reaction Points (RPs) controlled by this entry as follows: true(1) The rpEnabled variable for the RPs controlled by this object are not held in the FALSE state, thus enabling them to pay attention to received CNMs. false(2) The rpEnabled variable for the RPs controlled by this object are held in the FALSE state, thus disabling them from paying attention to received CNMs. 
.1.3.111.2.802.1.1.18.1.8.1.6,IEEE8021-CN-MIB::ieee8021CnRpgTimeReset,INTEGER,read-write,,current,,This object controls the value for all of the state machine variables, rpgTimeReset, used to reset the timers RpWhile. 
.1.3.111.2.802.1.1.18.1.8.1.7,IEEE8021-CN-MIB::ieee8021CnRpgByteReset,Unsigned32,read-write,,current,,This object controls the value for all of the state machine variables, rpgByteReset, used to reset the counters rpByteCount. 
.1.3.111.2.802.1.1.18.1.8.1.8,IEEE8021-CN-MIB::ieee8021CnRpgThreshold,Unsigned32,read-write,,current,,This object controls the number of times rpByteStage or rpTimeStage can count before the RP rate control state machine advances states. 
.1.3.111.2.802.1.1.18.1.8.1.9,IEEE8021-CN-MIB::ieee8021CnRpgMaxRate,Unsigned32,read-write,,current,,This object controls the maximum rate, in multiples of 1 Mb/s, at which an RP can transmit. Default value is the speed of the port. A system SHALL support a minimim value for this object that is no larger than 5 Mbits/s (object value 5). This rate includes all bits consequent to transmitting the frame on the LAN, including preamble, inter-frame gap, etc. 
.1.3.111.2.802.1.1.18.1.8.1.10,IEEE8021-CN-MIB::ieee8021CnRpgAiRate,Unsigned32,read-write,,current,,This object controls the transmission rate increment in the RPR_ACTIVE_INCREASE state (rpgAiRate) in multiples of 1 Mb/s. This rate includes all bits consequent to transmitting the frame on the LAN, including preamble, inter-frame gap, etc. 
.1.3.111.2.802.1.1.18.1.8.1.11,IEEE8021-CN-MIB::ieee8021CnRpgHaiRate,Unsigned32,read-write,,current,,This object controls the transmission rate increment in the RPR_HYPER_INCREASE state (rpgHaiRate) in multiples of 1 Mb/s. This rate includes all bits consequent to transmitting the frame on the LAN, including preamble, inter-frame gap, etc. 
.1.3.111.2.802.1.1.18.1.8.1.12,IEEE8021-CN-MIB::ieee8021CnRpgGd,Integer32,read-write,,current,,This object controls the number of bits that the value of the Quantized Feedback field received in a CNM PDU is shifted to the right to decrease rpTargetRate. rpgGd is thus 2 to the negative power of this object, e.g., 7 means rpgGd = 1/128. 
.1.3.111.2.802.1.1.18.1.8.1.13,IEEE8021-CN-MIB::ieee8021CnRpgMinDecFac,Unsigned32,read-write,,current,,This object controls the minimum factor by which the current RP transmit rate rpCurrentRate can be changed by reception of a Congestion Notification Message. Its integer value represents a percentage, from 1% to 100%. 
.1.3.111.2.802.1.1.18.1.8.1.14,IEEE8021-CN-MIB::ieee8021CnRpgMinRate,Unsigned32,read-write,,current,,This object controls the minimum transmission rate (rpgMinRate) in multiples of 1 Mb/s. A system SHALL support a value for this object that is no larger than 5 Mb/s per second. This rate includes all bits consequent to transmitting the frame on the LAN, including preamble, inter-frame gap, etc. 
.1.3.111.2.802.1.1.18.2,IEEE8021-CN-MIB::ieee8021CnConformance,,,,,,
.1.3.111.2.802.1.1.18.2.1,IEEE8021-CN-MIB::ieee8021CnCompliances,,,,,,
.1.3.111.2.802.1.1.18.2.1.1,IEEE8021-CN-MIB::ieee8021CnBridgeCompliance,,,,,,The compliance statement for support by a Bridge of the IEEE8021-MIRP-MIB module.
.1.3.111.2.802.1.1.18.2.1.2,IEEE8021-CN-MIB::ieee8021CnStationCompliance,,,,,,The compliance statement for support by an end station of the IEEE8021-MIRP-MIB module.
.1.3.111.2.802.1.1.18.2.2,IEEE8021-CN-MIB::ieee8021CnGroups,,,,,,
.1.3.111.2.802.1.1.18.2.2.1,IEEE8021-CN-MIB::ieee8021CnGlobalReqdGroup,,,,,,Objects in the global required group.
.1.3.111.2.802.1.1.18.2.2.2,IEEE8021-CN-MIB::ieee8021CnCpGlobalGroup,,,,,,Objects in the Congestion Point global group.
.1.3.111.2.802.1.1.18.2.2.3,IEEE8021-CN-MIB::ieee8021CnCpidTranslateGroup,,,,,,Objects in the CPID translate group.
.1.3.111.2.802.1.1.18.2.2.4,IEEE8021-CN-MIB::ieee8021CnEplGroup,,,,,,Objects for the Errored Ports Table group.
.1.3.111.2.802.1.1.18.2.2.5,IEEE8021-CN-MIB::ieee8021CnComPriGroup,,,,,,Objects for the global per-priority group.
.1.3.111.2.802.1.1.18.2.2.6,IEEE8021-CN-MIB::ieee8021CnCpPriGroup,,,,,,Objects for the Congestion Point per-priority group.
.1.3.111.2.802.1.1.18.2.2.7,IEEE8021-CN-MIB::ieee8021CnGlobalPriPortGroup,,,,,,Objects for the global per-priority per-port group.
.1.3.111.2.802.1.1.18.2.2.8,IEEE8021-CN-MIB::ieee8021CnCpPriPortGroup,,,,,,Objects for the Congestion Point per-priority per-port group. 
.1.3.111.2.802.1.1.18.2.2.9,IEEE8021-CN-MIB::ieee8021CnCpGroup,,,,,,Objects for the Congestion Point group.
.1.3.111.2.802.1.1.18.2.2.10,IEEE8021-CN-MIB::ieee8021CnRpppGroup,,,,,,Objects for the Reaction Point per-Port per-priority group.
.1.3.111.2.802.1.1.18.2.2.11,IEEE8021-CN-MIB::ieee8021CnRpGroup,,,,,,Objects for the Reaction Point group.
.1.3.111.2.802.1.1.19,IEEE8021-SRP-MIB::ieee8021SrpMib,,,,,,The Bridge MIB module for managing devices that support the IEEE Std 802.1Q Stream Reservation Protocol. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.19.0,IEEE8021-SRP-MIB::ieee8021SrpNotifications,,,,,,
.1.3.111.2.802.1.1.19.1,IEEE8021-SRP-MIB::ieee8021SrpObjects,,,,,,
.1.3.111.2.802.1.1.19.1.1,IEEE8021-SRP-MIB::ieee8021SrpConfiguration,,,,,,
.1.3.111.2.802.1.1.19.1.1.1,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseTable,,not-accessible,,current,,A table for SRP main control and status information. All writeable objects in this table must be persistent over power up restart/reboot. These objects augment the ieee8021BridgeBasePortTable.
.1.3.111.2.802.1.1.19.1.1.1.1,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseEntry,,not-accessible,,current,,SRP control and status information for a Bridge.
.1.3.111.2.802.1.1.19.1.1.1.1.1,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseMsrpEnabledStatus,INTEGER,read-create,,current,true(1):false(2),The administrative status requested by management for MSRP. The value true(1) indicates that MSRP should be enabled on this device, in all VLANs, on all ports for which it has not been specifically disabled. When false(2), MSRP is disabled, in all VLANs and on all ports, and all MSRP frames will be forwarded transparently. This objects affects both Applicant and Registrar state machines. A transition from false(2) to true(1) will cause a reset of all MSRP state machines on all ports. This object may be modified while the corresponding instance of ieee8021BridgeBaseRowStatus is active(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.19.1.1.1.1.2,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseMsrpTalkerPruning,INTEGER,read-create,,current,true(1):false(2),The value of the talkerPruning parameter which controls the propagation of Talker declarations. The value true(1) indicates that Talker attributes are only declared on ports that have the Stream destination_address registered in the MMRP MAC Address Registration Entries. When false(2), Talker attribute are declared on all egress ports in the active topology. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.19.1.1.1.1.3,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseMsrpMaxFanInPorts,Unsigned32,read-create,,current,,The value of the msrpMaxFanInPorts parameter which limits the total number of ports on a Bridge that are allowed to establish reservations for inbound Streams. A value of zero (0) indicates no fan-in limit is being specified and calculations involving fan-in will only be limited by the number of MSRP enabled ports. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.19.1.1.1.1.4,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseMsrpLatencyMaxFrameSize,Unsigned32,read-create,,current,,The value of msrpLatencyMaxFrameSize parameter which is used in the calculation of the maximum latency through a Bridge. The maximum size is defined to be 2000 octets by default, but may be set to a smaller or larger value dependent on the particular Bridge configuration. This parameter does not imply any type of policing of frame size, it is only used in the latency calculations. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.19.1.1.1.1.5,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseMsrpTalkerVlanPruning,INTEGER,read-create,,current,true(1):false(2),This parameter allows to limit the Talker declaration to ports, that have the Stream's VLAN identifier registered as a member in the VLAN Registration Entries. The value true(1) indicates that Talker declarations are only sent out on ports, that have the Stream's VLAN identifier registered as a member in the VLAN Registration Entries. When false(2), Talker declarations are propagated according to the VLAN spanning tree.
.1.3.111.2.802.1.1.19.1.1.1.1.6,IEEE8021-SRP-MIB::ieee8021SrpBridgeBaseMsrpMaxSRClasses,Unsigned32,read-only,,current,,This attribute provides the maximum number of SR classes supported by the Bridge.
.1.3.111.2.802.1.1.19.1.1.2,IEEE8021-SRP-MIB::ieee8021SrpBridgePortTable,,not-accessible,,current,,A table for SRP control and status information about every Bridge Port. Augments the ieee8021BridgeBasePortTable.
.1.3.111.2.802.1.1.19.1.1.2.1,IEEE8021-SRP-MIB::ieee8021SrpBridgePortEntry,,not-accessible,,current,,SRP control and status information for a Bridge Port.
.1.3.111.2.802.1.1.19.1.1.2.1.1,IEEE8021-SRP-MIB::ieee8021SrpBridgePortMsrpEnabledStatus,INTEGER,read-create,,current,true(1):false(2),The administrative state of MSRP operation on this port. The value true(1) indicates that MSRP is enabled on this port in all VLANs as long as ieee8021BridgeMsrpEnabledStatus is also true(1). A value of false(2) indicates that MSRP is disabled on this port in all VLANs: any MSRP frames received will be silently discarded, and no MSRP registrations will be propagated from other ports. Setting this to a value of true(1) will be stored by the agent but will only take effect on the MSRP protocol operation if ieee8021BridgeMsrpEnabledStatus also indicates the value true(1). This object affects all MSRP Applicant and Registrar state machines on this port. A transition from false(2) to true(1) will cause a reset of all MSRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.19.1.1.2.1.2,IEEE8021-SRP-MIB::ieee8021SrpBridgePortMsrpFailedRegistrations,Counter64,read-only,,current,,The total number of failed MSRP registrations, for any reason, in all VLANs, on this port. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.19.1.1.2.1.3,IEEE8021-SRP-MIB::ieee8021SrpBridgePortMsrpLastPduOrigin,OCTET,read-only,,current,,The Source MAC Address of the last MSRP message received on this port.
.1.3.111.2.802.1.1.19.1.1.2.1.4,IEEE8021-SRP-MIB::ieee8021SrpBridgePortSrPvid,Unsigned32,read-create,,current,,The default VLAN ID that Streams are assigned to. Talkers learn this VID from the SRP Domain attribute and tag Streams accordingly. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.19.1.1.2.1.5,IEEE8021-SRP-MIB::ieee8021SrpBridgePortMsrpTalkerPrunningPerPort,INTEGER,read-create,,current,true(1):false(2),This parameter controls the forwarding behavior for Talker declarations on the port when the TalkerPruning parameter is disabled for the bridge. The value true(1) indicates, that Talker declarations are only forwarded on that port, if the destination_address of the Stream is found in the MAC Address Registration Entries for the port. When false(2), Talker declarations are forwarded on that port regardless of the destination address.
.1.3.111.2.802.1.1.19.1.2,IEEE8021-SRP-MIB::ieee8021SrpLatency,,,,,,
.1.3.111.2.802.1.1.19.1.2.1,IEEE8021-SRP-MIB::ieee8021SrpLatencyTable,,not-accessible,,current,,A table containing a set of latency measurement parameters for each traffic class.
.1.3.111.2.802.1.1.19.1.2.1.1,IEEE8021-SRP-MIB::ieee8021SrpLatencyEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021SrpTrafficClass,current,,A list of objects containing latency information for each traffic class. Rows in the table are automatically created for ports that are not an SRP domain boundary port (i.e. SRPdomainBoundaryPort is FALSE). See 35.1.4, 8.8.2, 12.22.3.
.1.3.111.2.802.1.1.19.1.2.1.1.1,IEEE8021-SRP-MIB::ieee8021SrpTrafficClass,Unsigned32,not-accessible,,current,,The traffic class number associated with the row of the table. Rows in the table are automatically created for ports that are not an SRP domain boundary port (i.e. SRPdomainBoundaryPort is FALSE).
.1.3.111.2.802.1.1.19.1.2.1.1.2,IEEE8021-SRP-MIB::ieee8021SrpPortTcLatency,Unsigned32,read-only,,current,,The value of the portTcMaxLatency parameter for the traffic class. This value is expressed in nano-seconds.
.1.3.111.2.802.1.1.19.1.3,IEEE8021-SRP-MIB::ieee8021SrpStreams,,,,,,
.1.3.111.2.802.1.1.19.1.3.1,IEEE8021-SRP-MIB::ieee8021SrpStreamTable,,not-accessible,,current,,A table containing a set of characteristics for each registered Stream.
.1.3.111.2.802.1.1.19.1.3.1.1,IEEE8021-SRP-MIB::ieee8021SrpStreamEntry,,not-accessible,ieee8021SrpStreamId,current,,A list of objects containing characteristics for each registered Stream. Rows in the table are automatically created for Streams registered on any port of a Bridge.
.1.3.111.2.802.1.1.19.1.3.1.1.1,IEEE8021-SRP-MIB::ieee8021SrpStreamId,OCTET,not-accessible,,current,,The Stream ID associated with the row of the table. Rows in the table are automatically created when Streams are registered via MSRP.
.1.3.111.2.802.1.1.19.1.3.1.1.2,IEEE8021-SRP-MIB::ieee8021SrpStreamDestinationAddress,OCTET,read-only,,current,,The MAC destination address for the Stream described by this reservation.
.1.3.111.2.802.1.1.19.1.3.1.1.3,IEEE8021-SRP-MIB::ieee8021SrpStreamVlanId,Unsigned32,read-only,,current,,The VLAN ID associated with the MSRP registration for this Stream.
.1.3.111.2.802.1.1.19.1.3.1.1.4,IEEE8021-SRP-MIB::ieee8021SrpStreamTspecMaxFrameSize,Unsigned32,read-only,,current,,The maximum size frame that will be sent by a Talker for this Stream. This value is part of the Traffic Specification for the Stream.
.1.3.111.2.802.1.1.19.1.3.1.1.5,IEEE8021-SRP-MIB::ieee8021SrpStreamTspecMaxIntervalFrames,Unsigned32,read-only,,current,,The maximum number of frame that will be sent during a class measurement interval (L.2). This value is part of the Traffic Specification for the Stream.
.1.3.111.2.802.1.1.19.1.3.1.1.6,IEEE8021-SRP-MIB::ieee8021SrpStreamDataFramePriority,INTEGER,read-only,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4),The Priority Code Point (PCP) value that the referenced Stream will be tagged with. This value is used to distinguish Class A and Class B traffic.
.1.3.111.2.802.1.1.19.1.3.1.1.7,IEEE8021-SRP-MIB::ieee8021SrpStreamRank,INTEGER,read-only,,current,emergency(0):nonEmergency(1),SRP supports emergency and non-emergency. Emergency traffic will interrupt non-emergency traffic if there is insufficient bandwidth or resources available for the emergency traffic.
.1.3.111.2.802.1.1.19.1.3.2,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadTable,,not-accessible,,current,,A table containing a set of parameters for each StreamID that is preloaded on the Bridge as it initializes.
.1.3.111.2.802.1.1.19.1.3.2.1,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadEntry,,not-accessible,ieee8021SrpStreamPreloadId,current,,A list of objects containing characteristics for each registered Stream. Rows in the table are automatically created for Streams registered on any port of a Bridge.
.1.3.111.2.802.1.1.19.1.3.2.1.1,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadId,OCTET,not-accessible,,current,,The 64-bit StreamID is used to match Talker registrations with their corresponding Listener registrations(35.2.4).
.1.3.111.2.802.1.1.19.1.3.2.1.2,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadDestinationAddress,OCTET,read-write,,current,,The MAC destination address for the Stream described by this reservation.
.1.3.111.2.802.1.1.19.1.3.2.1.3,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadVlanId,Unsigned32,read-write,,current,,The VLAN ID associated with the MSRP registration for this Stream.
.1.3.111.2.802.1.1.19.1.3.2.1.4,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadTspecMaxFrameSize,Unsigned32,read-write,,current,,The maximum size frame that will be sent by a Talker for this Stream. This value is part of the Traffic Specification for the Stream.
.1.3.111.2.802.1.1.19.1.3.2.1.5,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadTspecMaxIntervalFrames,Unsigned32,read-write,,current,,The maximum number of frames that the Talker may transmit in one classMeasurementInterval (34.3). This value is part of the Traffic Specification for the Stream.
.1.3.111.2.802.1.1.19.1.3.2.1.6,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadDataFramePriority,INTEGER,read-write,,current,codePoint8p0d(1):codePoint7p1d(2):codePoint6p2d(3):codePoint5p3d(4),The Priority Code Point (PCP) value that the referenced Stream will be tagged with. This value is used to distinguish Class A and Class B traffic.
.1.3.111.2.802.1.1.19.1.3.2.1.7,IEEE8021-SRP-MIB::ieee8021SrpStreamPreloadRank,INTEGER,read-write,,current,emergency(0):nonEmergency(1),SRP supports emergency and non-emergency. Emergency traffic will interrupt non-emergency traffic if there is insufficient bandwidth or resources available for the emergency traffic.
.1.3.111.2.802.1.1.19.1.4,IEEE8021-SRP-MIB::ieee8021SrpReservations,,,,,,
.1.3.111.2.802.1.1.19.1.4.1,IEEE8021-SRP-MIB::ieee8021SrpReservationsTable,,not-accessible,,current,,A table containing Stream attribute registrations per port.
.1.3.111.2.802.1.1.19.1.4.1.1,IEEE8021-SRP-MIB::ieee8021SrpReservationsEntry,,not-accessible,ieee8021SrpReservationStreamId:ieee8021SrpReservationDirection:ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort,current,,A list of objects containing Stream attribute registrations per port. Rows in the table are automatically created for Streams registered on any port of a Bridge.
.1.3.111.2.802.1.1.19.1.4.1.1.1,IEEE8021-SRP-MIB::ieee8021SrpReservationStreamId,OCTET,not-accessible,,current,,The Stream ID associated with the row of the table. Rows in the table are automatically created when Streams are registered via MSRP.
.1.3.111.2.802.1.1.19.1.4.1.1.2,IEEE8021-SRP-MIB::ieee8021SrpReservationDirection,INTEGER,not-accessible,,current,talkerRegistrations(0):listenerRegistrations(1),The source of this Stream registration, either Talker or Listener.
.1.3.111.2.802.1.1.19.1.4.1.1.3,IEEE8021-SRP-MIB::ieee8021SrpReservationDeclarationType,INTEGER,read-only,,current,talkerAdvertise(0):talkerFailed(1):listenerAskingFailed(2):listenerReady(3):listenerReadyFailed(4),The type of Talker or Listener registration.
.1.3.111.2.802.1.1.19.1.4.1.1.4,IEEE8021-SRP-MIB::ieee8021SrpReservationAccumulatedLatency,Unsigned32,read-only,,current,,The Accumulated Latency associated with the current registration. For Talker registrations this represents the accumulated latency from the Talker to the ingress port of this Bridge. For Listener registrations this represents the accumulated latency to the ingress port of the neighbor Bridge or end stations. This include the latency of the media attached to this egress port.
.1.3.111.2.802.1.1.19.1.4.1.1.5,IEEE8021-SRP-MIB::ieee8021SrpReservationFailureSystemId,OCTET,read-only,,current,,The first system that changes a Talker Advertise to a Talker Failed registration will report its System Identification in this field. That single System Identification is then propagated from system to system.
.1.3.111.2.802.1.1.19.1.4.1.1.6,IEEE8021-SRP-MIB::ieee8021SrpReservationFailureCode,INTEGER,read-only,,current,noFailure(0):insufficientBandwidth(1):insufficientResources(2):insufficientTrafficClassBandwidth(3):streamIDInUse(4):streamDestinationAddressInUse(5):streamPreemptedByHigherRank(6):latencyHasChanged(7):egressPortNotAVBCapable(8):useDifferentDestinationAddress(9):outOfMSRPResources(10):outOfMMRPResources(11):cannotStoreDestinationAddress(12):priorityIsNoAnSRCLass(13):maxFrameSizeTooLarge(14):maxFanInPortsLimitReached(15):firstValueChangedForStreamID(16):vlanBlockedOnEgress(17):vlanTaggingDisabledOnEgress(18):srClassPriorityMismatch(19),The first Bridge that changes a Talker Advertise to a Talker Failed registration will report the Failure Code in this field. That single Failure Code is then propagated from Bridge to Bridge.
.1.3.111.2.802.1.1.19.1.4.1.1.7,IEEE8021-SRP-MIB::ieee8021SrpReservationDroppedStreamFrames,Counter64,read-only,,current,,A count of the number of data stream frames that have been dropped for whatever reason. These are not MSRP frames, but the stream data frames that are carried by the MSRP Reservation. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.19.1.4.1.1.8,IEEE8021-SRP-MIB::ieee8021SrpReservationStreamAge,Unsigned32,read-only,,current,,The number of seconds since the reservation was established on this port.
.1.3.111.2.802.1.1.19.1.4.2,IEEE8021-SRP-MIB::ieee8021SrpReservationsPreloadTable,,not-accessible,,current,,A table containing Stream attribute registrations per port.
.1.3.111.2.802.1.1.19.1.4.2.1,IEEE8021-SRP-MIB::ieee8021SrpReservationsPreloadEntry,,not-accessible,ieee8021SrpReservationsPreloadStreamId:ieee8021SrpReservationPreloadDirection:ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort,current,,A list of objects containing Stream attribute registrations per port. Rows in the table are automatically created for Streams registered on any port of a Bridge.
.1.3.111.2.802.1.1.19.1.4.2.1.1,IEEE8021-SRP-MIB::ieee8021SrpReservationsPreloadStreamId,OCTET,not-accessible,,current,,The 64-bit StreamID is used to match Talker registrations with their corresponding Listener registrations(35.2.4).
.1.3.111.2.802.1.1.19.1.4.2.1.2,IEEE8021-SRP-MIB::ieee8021SrpReservationPreloadDirection,INTEGER,read-write,,current,talkerRegistrations(0):listenerRegistrations(1),The source of this Stream registration, either Talker or Listener
.1.3.111.2.802.1.1.19.1.4.2.1.3,IEEE8021-SRP-MIB::ieee8021SrpReservationPreloadAccumulatedLatency,Unsigned32,read-write,,current,,The Accumulated Latency associated with the current registration. For Talker registrations this represents the accumulated latency from the Talker to the ingress port of this Bridge. For Listener registrations this represents the accumulated latency to the ingress port of the neighbor Bridge or end stations. This include the latency of the media attached to this egress port.
.1.3.111.2.802.1.1.19.2,IEEE8021-SRP-MIB::ieee8021SrpConformance,,,,,,
.1.3.111.2.802.1.1.19.2.1,IEEE8021-SRP-MIB::ieee8021SrpCompliances,,,,,,
.1.3.111.2.802.1.1.19.2.1.1,IEEE8021-SRP-MIB::ieee8021SrpCompliance,,,,,,The compliance statement for devices supporting Stream Reservation Protocol. Support of the objects defined in the IEEE8021-SRP MIB also requires support of the IEEE8021-BRIDGE-MIB; the provisions of 17.3.2 apply to implementations claiming support of the IEEE8021-SRP MIB.
.1.3.111.2.802.1.1.19.2.2,IEEE8021-SRP-MIB::ieee8021SrpGroups,,,,,,
.1.3.111.2.802.1.1.19.2.2.1,IEEE8021-SRP-MIB::ieee8021SrpConfigurationGroup,,,,,,Objects that define configuration of SRP.
.1.3.111.2.802.1.1.19.2.2.2,IEEE8021-SRP-MIB::ieee8021SrpLatencyGroup,,,,,,Objects that define latency for SRP.
.1.3.111.2.802.1.1.19.2.2.3,IEEE8021-SRP-MIB::ieee8021SrpStreamsGroup,,,,,,Objects that define Streams for SRP.
.1.3.111.2.802.1.1.19.2.2.4,IEEE8021-SRP-MIB::ieee8021SrpReservationsGroup,,,,,,Objects that define Stream Reservations for SRP.
.1.3.111.2.802.1.1.19.2.2.5,IEEE8021-SRP-MIB::ieee8021SrpConfigurationPruningGroup,,,,,,Objects that allow configuration of pruning behavior for SRP.
.1.3.111.2.802.1.1.19.2.2.6,IEEE8021-SRP-MIB::ieee8021SrpMonitoringSRclassesGroup,,,,,,Objects that provides information on the maximum number of SR classes supported on the Bridge.
.1.3.111.2.802.1.1.19.2.2.7,IEEE8021-SRP-MIB::ieee8021SrpStreamsPreloadGroup,,,,,,Objects that allow to preload parameters for each StreamId on Bridge Ports as the Bridge initializes.
.1.3.111.2.802.1.1.19.2.2.8,IEEE8021-SRP-MIB::ieee8021SrpReservationsPreloadGroup,,,,,,Objects that allow to initialize Streams within each Bridge as it powers up, to preload the Stream registrations that will later be provided by operation of SRP.
.1.3.111.2.802.1.1.20,IEEE8021-AS-MIB::ieee8021AsTimeSyncMib,,,,,,The Management Information Base module for  IEEE 802.1AS time synchronization protocol.
.1.3.111.2.802.1.1.20.1,IEEE8021-AS-MIB::ieee8021AsMIBObjects,,,,,,
.1.3.111.2.802.1.1.20.1.1,IEEE8021-AS-MIB::ieee8021AsDefaultDS,,,,,,
.1.3.111.2.802.1.1.20.1.1.1,IEEE8021-AS-MIB::ieee8021AsDefaultDSClockIdentity,OCTET,read-only,,current,,Globally unique manufacturer-assigned clock identifier for the local clock. The identifier is based on an  EUI-64.
.1.3.111.2.802.1.1.20.1.1.2,IEEE8021-AS-MIB::ieee8021AsDefaultDSNumberPorts,Unsigned32,read-only,,current,,The number of PTP ports on the device.  For an end station the value is 1.
.1.3.111.2.802.1.1.20.1.1.3,IEEE8021-AS-MIB::ieee8021AsDefaultDSClockClass,INTEGER,read-only,,current,primarySync(6):primarySyncLost(7):applicationSpecificSync(13):applicationSpecficSyncLost(14):primarySyncAlternativeA(52):applicationSpecificAlternativeA(58):primarySyncAlternativeB(187):applicationSpecficAlternativeB(193):defaultClock(248):slaveOnlyClock(255),Denotes the traceability of the time or frequency of the local clock. The value shall be selected as follows: a) If the Default Parameter Data Set member gmCapable is  TRUE, then clockClass is set to the value that reflects the combination of the LocalClock and ClockSource entities; else if the value that reflects the LocalClock and ClockSource entities is not  specified or not known,clockClass is set to 248; b) If the Default Parameter Data Set member gmCapable is  FALSE (see 8.6.2.1), clockClass is set to 255. 
.1.3.111.2.802.1.1.20.1.1.4,IEEE8021-AS-MIB::ieee8021AsDefaultDSClockAccuracy,INTEGER,read-only,,current,timeAccurateTo25ns(32):timeAccurateTo100ns(33):timeAccurateTo250ns(34):timeAccurateTo1us(35):timeAccurateTo2dot5us(36):timeAccurateTo10us(37):timeAccurateTo25us(38):timeAccurateTo100us(39):timeAccurateTo250us(40):timeAccurateTo1ms(41):timeAccurateTo2dot5ms(42):timeAccurateTo10ms(43):timeAccurateTo25ms(44):timeAccurateTo100ms(45):timeAccurateTo250ms(46):timeAccurateTo1s(47):timeAccurateTo10s(48):timeAccurateToGT10s(49):timeAccurateToUnknown(254),Characterizes local clock for the purpose of the best  master clock algorithm. The value shall be selected as  follows: a) clockAccuracy is set to the value that reflects the  combination of the LocalClock and ClockSource  entities if specified or known;  b) if the value that reflects the LocalClock and  ClockSource entities is not specified or unknown,  clockAccuracy is set to 254. 
.1.3.111.2.802.1.1.20.1.1.5,IEEE8021-AS-MIB::ieee8021AsDefaultDSOffsetScaledLogVariance,Unsigned32,read-only,,current,,The offsetScaledLogVariance is scaled, offset  representation of an estimate of the PTP variance. The PTP variance characterizes the precision and frequency stability of the ClockMaster. The PTP variance is the square of PTPDEV (see B.1.3.2). The value shall be selected as follows: a) offsetScaledLogVariance is set to the value that reflects the combination of the LocalClock and ClockSource entities; else b) if the value that reflects these entities is not specified or not known, offsetScaledLogVariance is set to 16640 (0x4100). This value corresponds to the  value of PTPDEV for observation interval equal to the  default Sync message transmission interval (i.e., observation interval of 0.125 s, see 11.5.2.3 and B.1.3.2). A value of 65535 (0xFFFF) indicates value is too  large to be represented or has not been computed. 
.1.3.111.2.802.1.1.20.1.1.6,IEEE8021-AS-MIB::ieee8021AsDefaultDSPriority1,Unsigned32,read-write,,current,,Most-significant priority declaration in the execution of  the best master clock algorithm. Lower values take precedence. The value of priority1 shall be 255 for a time-aware system that is not grandmaster-capable.  The value of priority1 shall be less than 255 for a  time-aware system that is grandmaster-capable. The value 0 shall be reserved for future management use, i.e., the  valueof priority1 shall be set to 0 only via management action, and shall not be specified as a default value by  a user of this standard. In the absence of a default value set by a user of this standard, the default value  shall be set as below:  a) system type of network infrastructure time-aware  system to value 246; b) portable time-aware system, 250;  c) other time-aware systems, 248.
.1.3.111.2.802.1.1.20.1.1.7,IEEE8021-AS-MIB::ieee8021AsDefaultDSPriority2,Unsigned32,read-write,,current,,Least-significant priority declaration in the execution of the best master clock algorithm. Lower values take precedence. The default value is 248
.1.3.111.2.802.1.1.20.1.1.8,IEEE8021-AS-MIB::ieee8021AsDefaultDSGmCapable,INTEGER,read-only,,current,true(1):false(2),True (1) if master clock capable; false (2) otherwise.
.1.3.111.2.802.1.1.20.1.1.9,IEEE8021-AS-MIB::ieee8021AsDefaultDSCurrentUTCOffset,Integer32,read-only,,current,,The value is the offset between TAI and UTC, relative to  the ClockMaster entity of this time-aware system. It is  equal to the global variable sysCurrentUtcOffset (see  10.3.8.16). The value is in units of seconds. The initialization default value is selected as  follows: a) the value is the value obtained from a primary  reference if the value is known at the at the time of  initialization,  b) else the value is the current number ofleap seconds,  see 8.2.3, when the time-aware system is designed.
.1.3.111.2.802.1.1.20.1.1.10,IEEE8021-AS-MIB::ieee8021AsDefaultDSCurrentUTCOffsetValid,INTEGER,read-only,,current,true(1):false(2),True (1) if ieee8021AsDefaultDSCurrentUTCOffset is known  to be correct; false (2) otherwise.
.1.3.111.2.802.1.1.20.1.1.11,IEEE8021-AS-MIB::ieee8021AsDefaultDSLeap59,INTEGER,read-only,,current,true(1):false(2),A true (1) value indicates that the last minute of the  current UTC day, relative to the ClockMaster entity of  this time-aware system, will contain 59 seconds. It is  equal to the global variable sysLeap59 (see 10.3.8.12).  The initialization value is selected as follows:  a) Set to true (1) if the value is obtained from a  primary reference if known at the at the time of  initialization, else b) The value is set to false (2).
.1.3.111.2.802.1.1.20.1.1.12,IEEE8021-AS-MIB::ieee8021AsDefaultDSLeap61,INTEGER,read-only,,current,true(1):false(2),A true (1) value indicates that the last minute of the  current UTC day, relative to the ClockMaster entity of  this time-aware system, will contain 59 seconds. It is  equal to the global variable sysLeap61 (see 10.3.8.11).  The initialization value is selected as follows:  a) Set to true (1) if the value is obtained from a  primary reference if known at the at the time of  initialization, else b) The value is set to false (2).
.1.3.111.2.802.1.1.20.1.1.13,IEEE8021-AS-MIB::ieee8021AsDefaultDSTimeTraceable,INTEGER,read-only,,current,true(1):false(2),The value is set to true (1) if the timescale and the value of Ieee8021AsCurrentUtcOffset, relative to the  ClockMaster entity of this time-aware system, are  traceable to a primary reference standard; otherwise  the value is set to false (2). It is equal to the global  variable sysTimeTraceable (see 10.3.8.14). The initialization value is selected as follows: a) If the time and the value of currentUtcOffset are  traceable to a primary reference standard at the  time of initialization, the value is set to true  (1), else b) The value is set to false (2).
.1.3.111.2.802.1.1.20.1.1.14,IEEE8021-AS-MIB::ieee8021AsDefaultDSFrequencyTraceable,INTEGER,read-only,,current,true(1):false(2),The value is set to true (1) if the frequency determining  the timescale of the ClockMaster Entity of this time- aware system is traceable to a primary reference  standard; otherwise the value is set to false (2). It is  equal to the global variable sysFrequencyTraceable (see  10.3.8.15). The initialization value is selected as follows: a) If the frequency is traceable to a primary reference  standard at the time of initialization, the value is  set to true (1), else b) The value is set to false (2)..
.1.3.111.2.802.1.1.20.1.1.15,IEEE8021-AS-MIB::ieee8021AsDefaultDSTimeSource,INTEGER,read-only,,current,atomicClock(16):gps(32):terrestrialRadio(48):ptp(64):ntp(80):handSet(96):other(144):internalOscillator(160),The timeSource is an information-only attribute  indicating the type of source of time used by a  ClockMaster. The value is not used in the selection of  the grandmaster. The values shall be as specified in  Table 8-3. These represent categories. For example, the  GPS entry would include not only the GPS system of the  U.S. Department of Defense but the European Galileo  system and other present and future satellite-based  timing systems. All unused values in Table 8-3 are  reserved. The initialization value is selected as follows: a) If the timeSource (8.6.2.7 and Table 8-3), is known at the time of initialization, the value is derived from the table, else b) The value is set to INTERNAL_OSCILLATOR (160).
.1.3.111.2.802.1.1.20.1.2,IEEE8021-AS-MIB::ieee8021AsCurrentDS,,,,,,
.1.3.111.2.802.1.1.20.1.2.1,IEEE8021-AS-MIB::ieee8021AsCurrentDSStepsRemoved,Integer32,read-only,,current,,The number of communication paths traversed between the local clock and the grandmaster clock (see Table 10.3.3).  For example, stepsRemoved for a slave clock on the same PTP communication path as the grandmaster clock will have  a value of 1, indicating that a single path was traversed.
.1.3.111.2.802.1.1.20.1.2.2,IEEE8021-AS-MIB::ieee8021AsCurrentDSOffsetFromMasterHs,Integer32,read-only,,current,,The most significant 32 bits of the offset, signed  96 bit number in 2**-16 ns, an implementation-specific  computation of the current value of the time difference  between a master and a slave as computed by the slave.  This object MUST be read at the same time as  ieee8021AsCurrentDSOffsetFromMasterMs, and  ieee8021AsCurrentDSOffsetFromMasterLs, which  represents middle and least significant 32 bits of  values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.3,IEEE8021-AS-MIB::ieee8021AsCurrentDSOffsetFromMasterMs,Integer32,read-only,,current,,The middle significant 32 bits of the offset, signed  96 bit number in 2**-16 ns, an implementation-specific  computation of the current value of the time difference  between a master and a slave as computed by the slave.  This object MUST be read at the same time as  ieee8021AsCurrentDSOffsetFromMasterHs, and  ieee8021AsCurrentDSOffsetFromMasterLs, which  represents most (highest) and least significant 32 bits  of values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.4,IEEE8021-AS-MIB::ieee8021AsCurrentDSOffsetFromMasterLs,Integer32,read-only,,current,,The least significant 32 bits of the offset, signed  96 bit number in 2**-16 ns, an implementation-specific  computation of the current value of the time difference  between a master and a slave as computed by the slave.  This object MUST be read at the same time as  ieee8021AsCurrentDSOffsetFromMasterHs, and  ieee8021AsCurrentDSOffsetFromMasterMs, which  represents most (highest) and middle significant 32 bits of values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.5,IEEE8021-AS-MIB::ieee8021AsCurrentDSLastGmPhaseChangeHs,Integer32,read-only,,current,,The value (see 10.2.3.16) is the phase change that occurred on the most recent change in either  grandmaster or gmTimeBaseIndicator (see 9.2.2.2). This object MUST be read at the same time as  ieee8021AsCurrentDSLastGmPhaseChangeMs, and  ieee8021AsCurrentDSLastGmPhaseChangeLs, which  represents middle and least significant 32 bits of  values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.6,IEEE8021-AS-MIB::ieee8021AsCurrentDSLastGmPhaseChangeMs,Unsigned32,read-only,,current,,The value (see 10.2.3.16) is the phase change that occurred on the most recent change in either  grandmaster or gmTimeBaseIndicator (see 9.2.2.2). This object MUST be read at the same time as  ieee8021AsCurrentDSLastGmPhaseChangeHs, and  ieee8021AsCurrentDSLastGmPhaseChangeLs, which  represents most and least significant 32 bits of  values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.7,IEEE8021-AS-MIB::ieee8021AsCurrentDSLastGmPhaseChangeLs,Unsigned32,read-only,,current,,The value (see 10.2.3.16) is the phase change that occurred on the most recent change in either  grandmaster or gmTimeBaseIndicator (see 9.2.2.2). This object MUST be read at the same time as  ieee8021AsCurrentDSLastGmPhaseChangeMs, and  ieee8021AsCurrentDSLastGmPhaseChangeLs, which  represents middle and least significant 32 bits of  values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.8,IEEE8021-AS-MIB::ieee8021AsCurrentDSLastGmFreqChangeMs,Integer32,read-only,,current,,The value (see 10.2.3.17) is the frequency change that  occurred on the most recent change in either grandmaster  or gmTimeBaseIndicator (see 9.2.2.2). This object MUST be read at the same time as  ieee8021AsCurrentDSLastGmFreqChangeLs, which  represents least significant 32 bits of the value in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.9,IEEE8021-AS-MIB::ieee8021AsCurrentDSLastGmFreqChangeLs,Unsigned32,read-only,,current,,The value (see 10.2.3.17) is the frequency change that  occurred on the most recent change in either grandmaster  or gmTimeBaseIndicator (see 9.2.2.2). This object MUST be read at the same time as  ieee8021AsCurrentDSLastGmFreqChangeMs, which  represents most significant 32 bits of the value in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.2.10,IEEE8021-AS-MIB::ieee8021AsCurrentDSGmTimebaseIndicator,Unsigned32,read-only,,current,,This reports the grandmaster's time base change value  conveyed in the Sync message. The value is the value of  timeBaseIndicator of the current grandmaster (see 9.2.2.2  and 9.6.2.2) 
.1.3.111.2.802.1.1.20.1.2.11,IEEE8021-AS-MIB::ieee8021AsCurrentDSGmChangeCount,Counter32,read-only,,current,,This statistics counter tracks the number of times the  grandmaster has changed in a gPTP domain. This counter  increments when the PortAnnounceInformation state  machine enters the SUPERIOR_MASTER_PORT state or the  INFERIOR_MASTER_OR_OTHER_PORT state (see 10.3.11 and  Figure 10-13).  
.1.3.111.2.802.1.1.20.1.2.12,IEEE8021-AS-MIB::ieee8021AsCurrentDSTimeOfLastGmChangeEvent,TimeTicks,read-only,,current,,This timestamp denotes the system time when the most  recent grandmaster change occurred in a gPTP domain.  This timestamp is updated when the  PortAnnounceInformation state machine enters the  SUPERIOR_MASTER_PORT state or the  INFERIOR_MASTER_OR_OTHER_PORT state (see 10.3.11 and  Figure 10-13). 
.1.3.111.2.802.1.1.20.1.2.13,IEEE8021-AS-MIB::ieee8021AsCurrentDSTimeOfLastGmFreqChangeEvent,TimeTicks,read-only,,current,,This timestamp denotes the system time when the most  recent change in grandmaster phase occured, due to a  change of either the grandmaster or the grandmaster  time base. This timestamp is updated when the  PortAnnounceInformation state machine enters the  SUPERIOR_MASTER_PORT state or the  INFERIOR_MASTER_OR_OTHER_PORT state (see 10.3.11 and  Figure 10-13), and when the  ieee802AsCurrentDSGmTimebaseIndicator managed object (see 14.3.5) changes. 
.1.3.111.2.802.1.1.20.1.2.14,IEEE8021-AS-MIB::ieee8021AsCurrentDSTimeOfLastGmPhaseChangeEvent,TimeTicks,read-only,,current,,This timestamp denotes the system time when the most  recent change in grandmaster frequency occured, due to  a change of either the grandmaster or the grandmaster  time base. This timestamp is updated when the  PortAnnounceInformation state machine enters the  SUPERIOR_MASTER_PORT state or the  INFERIOR_MASTER_OR_OTHER_PORT state (see 10.3.11 and  Figure 10-13), and when the  ieee802AsCurrentDSGmTimebaseIndicator managed object (see 14.3.5) changes. 
.1.3.111.2.802.1.1.20.1.3,IEEE8021-AS-MIB::ieee8021AsParentDS,,,,,,
.1.3.111.2.802.1.1.20.1.3.1,IEEE8021-AS-MIB::ieee8021AsParentDSParentClockIdentity,OCTET,read-only,,current,,Clock identifier (clockIdentity) of the local clock's  parent clock. The default value is set to  ieee8021AsDefaultDSClockIdentity. If this time-aware system is the grandmaster, the value  is the clockIdentity of this time-aware system.  If this time-aware system is not the grandmaster, the  value is the clockIdentity of the MasterPort (see  Table 10-1) of the gPTP communication path attached to  the single slave port of this time-aware system. 
.1.3.111.2.802.1.1.20.1.3.2,IEEE8021-AS-MIB::ieee8021AsParentDSParentPortNumber,Unsigned32,read-only,,current,,Port number (portNumber) of the local clock's parent gPTP  port number. If this time-aware system is the grandmaster, the value  is the gPTP portNumber of this time-aware system.  If this time-aware system is not the grandmaster, the  value is the portNumber of the MasterPort (see  Table 10-1) of the gPTP communication path attached to  the single gPTP slave port of this time-aware system. 
.1.3.111.2.802.1.1.20.1.3.3,IEEE8021-AS-MIB::ieee8021AsParentDSCumlativeRateRatio,Integer32,read-only,,current,,The value is an estimate of the ratio of the frequency  of the grandmaster to the frequency of the LocalClock  entity of this time-aware system. Cumulative rate ratio is expressed as the fractional  frequency offset multiplied by 2**41, i.e., the  quantity (rateRatio - 1.0)(2**41), where rateRatio is  computed by the PortSyncSyncReceive state machine (see  10.2.7.1.4).
.1.3.111.2.802.1.1.20.1.3.4,IEEE8021-AS-MIB::ieee8021AsParentDSGrandmasterIdentity,OCTET,read-only,,current,,Clock identifier (clockIdentity) of the grandmaster. The default value is set to  ieee8021AsDefaultDSClockIdentity.
.1.3.111.2.802.1.1.20.1.3.5,IEEE8021-AS-MIB::ieee8021AsParentDSGrandmasterClockClass,INTEGER,read-only,,current,primarySync(6):primarySyncLost(7):applicationSpecificSync(13):applicationSpecficSyncLost(14):primarySyncAlternativeA(52):applicationSpecificAlternativeA(58):primarySyncAlternativeB(187):applicationSpecficAlternativeB(193):defaultClock(248):slaveOnlyClock(255),Denotes the traceability of the time or frequency of the grandmaster. The default value is set to  ieee8021AsDefaultDSClockClass.
.1.3.111.2.802.1.1.20.1.3.6,IEEE8021-AS-MIB::ieee8021AsParentDSGrandmasterClockAccuracy,INTEGER,read-only,,current,timeAccurateTo25ns(32):timeAccurateTo100ns(33):timeAccurateTo250ns(34):timeAccurateTo1us(35):timeAccurateTo2dot5us(36):timeAccurateTo10us(37):timeAccurateTo25us(38):timeAccurateTo100us(39):timeAccurateTo250us(40):timeAccurateTo1ms(41):timeAccurateTo2dot5ms(42):timeAccurateTo10ms(43):timeAccurateTo25ms(44):timeAccurateTo100ms(45):timeAccurateTo250ms(46):timeAccurateTo1s(47):timeAccurateTo10s(48):timeAccurateToGT10s(49):timeAccurateToUnknown(254),Characterizes the grandmaster clock for the purpose of  the best master clock algorithm. The default value is  set to ieee8021AsDefaultDSClockAccuracy.
.1.3.111.2.802.1.1.20.1.3.7,IEEE8021-AS-MIB::ieee8021AsParentDSGrandmasterOffsetScaledLogVariance,Unsigned32,read-only,,current,,Clock Allan variance of the local clock expressed as a  base-2 logarithm multiplied by a scale factor of 256. Hysteresis is applied requiring the underlying computed variance to move by at least 128 before a change is reported. A value of 65535 (0xFFFF) indicates value  is too large to be represented or has not been computed.  The default value is set to  ieee8021AsDefaultDSOffsetScaledLogVariance.
.1.3.111.2.802.1.1.20.1.3.8,IEEE8021-AS-MIB::ieee8021AsParentDSGrandmasterPriority1,Unsigned32,read-write,,current,,Grandmaster's most-significant priority declaration in  the execution of the best master clock algorithm.  Lower values take precedence.   The default value is set to ieee8021AsDefaultDSPriority1.
.1.3.111.2.802.1.1.20.1.3.9,IEEE8021-AS-MIB::ieee8021AsParentDSGrandmasterPriority2,Unsigned32,read-write,,current,,Grandmaster's least-significant priority declaration in  the execution of the best master clock algorithm.  Lower values take precedence.   The default value is set to ieee8021AsDefaultDSDSPriority2.
.1.3.111.2.802.1.1.20.1.4,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDS,,,,,,
.1.3.111.2.802.1.1.20.1.4.1,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSCurrentUtcOffset,Integer32,read-only,,current,,The value is currentUtcOffset for the current grandmaster  (see Table 14.2.9). It is equal to the value of the global variable currentUtcOffset (see 10.3.8.9). The value is in  units of seconds. The default value is set to  ieee8021AsDefaultDSCurrentUTCOffset.
.1.3.111.2.802.1.1.20.1.4.2,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSCurrentUtcOffsetValid,INTEGER,read-only,,current,true(1):false(2),True (1) if ieee8021AsTimePropertiesDSCurrentUTCOffset  is known to be correct; false (2) otherwise. The default  value is set to ieee8021AsDefaultDSCurrentUTCOffsetValid. 
.1.3.111.2.802.1.1.20.1.4.3,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSLeap59,INTEGER,read-only,,current,true(1):false(2),The value is leap59 for the current grandmaster (see  14.2.11). It is equal to the global variable leap59  (see 10.3.8.5).  A true (1) value indicates that the last minute of the  current UTC day, relative to the ClockMaster entity of  this time-aware system, will contain 59 seconds. The default value is set to ieee8021AsDefaultDSLeap59.
.1.3.111.2.802.1.1.20.1.4.4,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSLeap61,INTEGER,read-only,,current,true(1):false(2),The value is leap61 for the current grandmaster (see  14.2.12). It is equal to the global variable leap59  (see 10.3.8.4).  A true (1) value indicates that the last minute of the  current UTC day, relative to the ClockMaster entity of  this time-aware system, will contain 61 seconds.The default value is set to  ieee8021AsDefaultDSLeap61.
.1.3.111.2.802.1.1.20.1.4.5,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSTimeTraceable,INTEGER,read-only,,current,true(1):false(2),The value is timeTraceable for the current grandmaster  (see 14.2.13). It is equal to the global variable  timeTraceable (see 10.3.8.7).  True (1) if the timescale and the value of  timePropertiesDSCurrentUTCOffset are traceable to a primary reference; false (2) otherwise. The default  value is set to ieee8021AsDefaultDSTimeTraceable.
.1.3.111.2.802.1.1.20.1.4.6,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSFrequencyTraceable,INTEGER,read-only,,current,true(1):false(2),The value is frequencyTraceable for the current  grandmaster (see 14.2.14). It is equal to the global  variable frequencyTraceable (see 10.3.8.8).  True (1) if the frequency determining the timescale is traceable to a primary reference; false (2) otherwise.  The default value is set to  ieee8021AsDefaultDSFrequencyTraceable.
.1.3.111.2.802.1.1.20.1.4.7,IEEE8021-AS-MIB::ieee8021AsTimePropertiesDSTimeSource,INTEGER,read-only,,current,atomicClock(16):gps(32):terrestrialRadio(48):ptp(64):ntp(80):handSet(96):other(144):internalOscillator(160),The value is timeSource for the current grandmaster  (see 14.2.15). It is equal to the global variable  timeTraceable (see 10.3.8.10).  Indicates the source of time used by the grandmaster clock. The default value is set to  ieee8021AsDefaultDSTimeSource.
.1.3.111.2.802.1.1.20.1.5,IEEE8021-AS-MIB::ieee8021AsPortDSIfTable,,not-accessible,,current,,A table of gPTP port related variables in a time-aware  Bridge or for a time-aware end station. A value of 1 is used in  a bridge or an end station that does not have multiple  components.  For a given media port of a Bridge or an end station, there may  be one or more gPTP port, and depends whether a media port  supports point to point link (e.g. IEEE 802.3 Ethernet) or point  to multi-point (e.g. CSN, IEEE 802.3 EPON, etc) links on the  media port. 
.1.3.111.2.802.1.1.20.1.5.1,IEEE8021-AS-MIB::ieee8021AsPortDSIfEntry,,not-accessible,ieee8021AsBridgeBasePort:ieee8021AsPortDSAsIfIndex,current,,A list of objects pertaining to a gPTP port of a time-aware  bridge component or a time-aware end station. 
.1.3.111.2.802.1.1.20.1.5.1.1,IEEE8021-AS-MIB::ieee8021AsBridgeBasePort,Unsigned32,not-accessible,,current,,This object identifies the bridge port number of  the port for which this entry contains bridge management  information. For end stations, this port number shall  be (1).
.1.3.111.2.802.1.1.20.1.5.1.2,IEEE8021-AS-MIB::ieee8021AsPortDSAsIfIndex,Integer32,not-accessible,,current,,This object identifies the gPTP interface group within  the system for which this entry contains information. It is the value of the instance of the IfIndex object, defined in the IF-MIB, for the gPTP interface group corresponding to this port, or the value 0 if the port has not been bound to an underlying frame source and sink. For a given media port of a Bridge or an end station,  there may be one or more gPTP port, and depends whether  a media port supports point to point link (e.g. IEEE  802.3 Ethernet) or point to multi-point (e.g. CSN, IEEE  802.3 EPON, etc) links on the media port.
.1.3.111.2.802.1.1.20.1.5.1.3,IEEE8021-AS-MIB::ieee8021AsPortDSClockIdentity,OCTET,read-only,,current,,The clockIdentity is an 8 octet array formed by  mapping an IEEE EUI-48 assigned to the time-aware system  to IEEE EUI-64 format (i.e., to an array of 8 octets).  The EUI-48 shall be an Ethernet MAC address owned by the  organization creating the instance of a clockIdentity  under the terms of this subclause. The organization  owning the MAC address shall ensure that the  MAC address is used in generating only a single instance  of a clockIdentity, for example by requiring that the  MAC address be a MAC address embedded in the device  identified by the clockIdentity. The mapping rules for  constructing the EUI-64 from the EUI-48 shall be those  specified by the IEEE [B2]. The 8 octets of the created  IEEE EUI-64 shall be assigned in order to the 8 octet  array clockIdentity with most significant octet of the  IEEE EUI-64 assigned to the clockIdentity octet array  member with index 0.(see 8.5.2.2).
.1.3.111.2.802.1.1.20.1.5.1.4,IEEE8021-AS-MIB::ieee8021AsPortDSPortNumber,Unsigned32,read-only,,current,,The portNumber value for a port on a time-aware end  station (i.e., a time-aware system supporting a single  gPTP port) shall be 1. The portNumber values for the  gPTP ports on a time-aware bridgeBridge supporting N  ports shall be 1, 2, ?, N, respectively (see 8.5.2.3) .
.1.3.111.2.802.1.1.20.1.5.1.5,IEEE8021-AS-MIB::ieee8021AsPortDSPortRole,INTEGER,read-only,,current,disabledPort(3):masterPort(6):passivePort(7):slavePort(9),The value is the value of the port role of this port  (see Table 10-1), and is taken from the enumeration in Table 14-5. All other values reserved. The enumeration values are consistent with IEEE Std 1588TM-2008,  Table 8. The default value is 3 (DisabledPort).
.1.3.111.2.802.1.1.20.1.5.1.6,IEEE8021-AS-MIB::ieee8021AsPortDSPttPortEnabled,INTEGER,read-write,,current,true(1):false(2),802.1AS function enable for a given port. True (1) if  the time-synchronization and best master selection functions of the port are enabled; False (2) otherwise (see 10.2.4.12). The contents of this table SHALL be maintained across a  restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.7,IEEE8021-AS-MIB::ieee8021AsPortDSIsMeasuringDelay,INTEGER,read-only,,current,true(1):false(2),True (1) if the port is measuring link propagation delay; The value is equal to the value of the Boolean  isMeasuringPdDelay (see 11.2.12.5 and E.4.3.2) False (2) otherwise.
.1.3.111.2.802.1.1.20.1.5.1.8,IEEE8021-AS-MIB::ieee8021AsPortDSAsCapable,INTEGER,read-only,,current,true(1):false(2),True (1) if and only if it is determined that this  time-aware system and the time-aware system at the  other ends of the link attached to this port can interoperate with each other via the IEEE 802.1AS  protocol; False (2) otherwise.
.1.3.111.2.802.1.1.20.1.5.1.9,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborPropDelayHs,Unsigned32,read-only,,current,,The most (highest) significant 32 bits, unsigned  96 bit number in 2**-16 ns, the value is equal to the  value of the per-port global variable neighborPropDelay (see 10.2.4.6). It is an estimate of the current one-way propagation time on the link attached to this port, measured as specified for the respective medium (see 11.2.15, 12.5, and E.4). The value is zero for ports attached to IEEE 802.3 EPON links and for the master port of an IEEE 802.11 link, because one-way propagation delay is not measured on the latter and not directly measured on the former. It is recommended that the data type be scaled in ns. The initialization value is zero. This object MUST be read at the same time as  ieee8021AsPortDSNeighborPropDelayMs, and  ieee8021AsPortDSNeighborPropDelayLs, which  represents middle and least significant 32 bits of values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.5.1.10,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborPropDelayMs,Unsigned32,read-only,,current,,The second most (middle) significant 32 bits, unsigned  96 bit number in 2**-16 ns, the value is equal to the  value of the per-port global variable neighborPropDelay (see 10.2.4.6). It is an estimate of the current one-way propagation time on the link attached to this port, measured as specified for the respective medium (see 11.2.15, 12.5, and E.4). The value is zero for ports attached to IEEE 802.3 EPON links and for the master port of an IEEE 802.11 link, because one-way propagation delay is not measured on the latter and not directly measured on the former. It is recommended that the data type be scaled in ns. The initialization value is zero. This object MUST be read at the same time as  ieee8021AsPortDSNeighborPropDelayHs, and  ieee8021AsPortDSNeighborPropDelayLs, which  represents most (highest) and least significant 32 bits of values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.5.1.11,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborPropDelayLs,Unsigned32,read-only,,current,,The least significant 32 bits, unsigned  96 bit number in 2**-16 ns, the value is equal to the  value of the per-port global variable neighborPropDelay (see 10.2.4.6). It is an estimate of the current one-way propagation time on the link attached to this port, measured as specified for the respective medium (see 11.2.15, 12.5, and E.4). The value is zero for ports attached to IEEE 802.3 EPON links and for the master port of an IEEE 802.11 link, because one-way propagation delay is not measured on the latter and not directly measured on the former. It is recommended that the data type be scaled in ns. The initialization value is zero. This object MUST be read at the same time as  ieee8021AsPortDSNeighborPropDelayHs, and  ieee8021AsPortDSNeighborPropDelayMs, which  represents most (highest) and middle significant 32 bits of values, respectively, in order for the read operation to succeed. 
.1.3.111.2.802.1.1.20.1.5.1.12,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborPropDelayThreshHs,Unsigned32,read-write,,current,,The most (highest) significant 32 bits, unsigned  96 bit number in 2**-16 ns, the value is equal to the  value of the per-port global variable  neighborPropDelayThresh (see 11.2.12.5). It  is the propagation time threshold, above which a port is not considered capable of participating in the 802.1AS protocol This object MUST be read or written at the same time as  ieee8021AsPortDSNeighborPropDelayThreshMs, and  ieee8021AsPortDSNeighborPropDelayThreshLs, which  represents middle and least significant 32 bits of values, respectively, in order for the read or write  operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.13,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborPropDelayThreshMs,Unsigned32,read-write,,current,,The middle significant 32 bits, unsigned  96 bit number in 2**-16 ns, the value is equal to the  value of the per-port global variable  neighborPropDelayThresh (see 11.2.12.5). It  is the propagation time threshold, above which a port is not considered capable of participating in the 802.1AS protocol This object MUST be read or written at the same time as  ieee8021AsPortDSNeighborPropDelayThreshHs, and  ieee8021AsPortDSNeighborPropDelayThreshLs, which  represents most (highest) and least significant 32 bits of values, respectively, in order for the read or write  operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.14,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborPropDelayThreshLs,Unsigned32,read-write,,current,,The least significant 32 bits, unsigned  96 bit number in 2**-16 ns, the value is equal to the  value of the per-port global variable  neighborPropDelayThresh (see 11.2.12.5). It  is the propagation time threshold, above which a port is not considered capable of participating in the 802.1AS protocol This object MUST be read at the same time as  ieee8021AsPortDSNeighborPropDelayThreshHs, and  ieee8021AsPortDSNeighborPropDelayThreshMs, which  represents most (highest) and middle significant 32 bits of values, respectively, in order for the read or write  operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.15,IEEE8021-AS-MIB::ieee8021AsPortDSDelayAsymmetryHs,Integer32,read-write,,current,,The most (highest) significant 32 bits, signed  96 bit number in 2**-16 ns.  The value is the asymmetry in the propagation delay on  the link attached to this port relative to the  grandmaster time base, as defined in 8.3. If  propagation delay asymmetry is not modeled, then  delayAsymmetry is 0.  This object MUST be read or written at the same time as  ieee8021AsPortDSDelayAsymmetryMs, and  ieee8021AsPortDSDelayAsymmetryLs, which  represents middle and least significant 32 bits of values, respectively, in order for the read or write  operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.16,IEEE8021-AS-MIB::ieee8021AsPortDSDelayAsymmetryMs,Unsigned32,read-write,,current,,The middle significant 32 bits, signed  96 bit number in 2**-16 ns.  The value is the asymmetry in the propagation delay on  the link attached to this port relative to the  grandmaster time base, as defined in 8.3. If  propagation delay asymmetry is not modeled, then  delayAsymmetry is 0.  This object MUST be read or written at the same time as  ieee8021AsPortDSDelayAsymmetryHs, and  ieee8021AsPortDSDelayAsymmetryLs, which  represents middle and least significant 32 bits of values, respectively, in order for the read or write  operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.17,IEEE8021-AS-MIB::ieee8021AsPortDSDelayAsymmetryLs,Unsigned32,read-write,,current,,The least significant 32 bits, signed  96 bit number in 2**-16 ns.  The value is the asymmetry in the propagation delay on  the link attached to this port relative to the  grandmaster time base, as defined in 8.3. If  propagation delay asymmetry is not modeled, then  delayAsymmetry is 0.  This object MUST be read or written at the same time as  ieee8021AsPortDSDelayAsymmetryHs, and  ieee8021AsPortDSDelayAsymmetryLs, which  represents most (highest) and least significant 32 bits of values, respectively, in order for the read or write  operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.18,IEEE8021-AS-MIB::ieee8021AsPortDSNeighborRateRatio,Integer32,read-only,,current,,The value is an estimate of the ratio of the frequency of  the LocalClock entity of the time-aware system at the  other end of the link attached to this port, to the  frequency of the LocalClock entity of this time-aware  system (see 10.2.4.6). Neighbor rate ratio is expressed  as the fractional frequency offset multiplied by 2**41,  i.e., the quantity (neighborRateRatio - 1.0)(2**41).
.1.3.111.2.802.1.1.20.1.5.1.19,IEEE8021-AS-MIB::ieee8021AsPortDSInitialLogAnnounceInterval,Integer32,read-write,,current,,The value is the logarithm to the base 2 of the of the announce interval used when  (a) the port is initialized, or (b) a message interval request TLV is received with  announceInterval field set to 126 (see 10.6.2.2 and  and the AnnounceIntervalSetting state machine  10.3.14) The default value is 0. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.20,IEEE8021-AS-MIB::ieee8021AsPortDSCurrentLogAnnounceInterval,Integer32,read-only,,current,,The value is the logarithm to the base 2 of the of the current announce transmission interval. The currentLogAnnounceInterval specifies the current  value of the announce interval. Every port supports the value 127; the port does not  send Announce messages when currentLogAnnounceInterval  has this value (see 10.3.14). A port may support other  values, except for the reserved values -128 through - 125, inclusive, and 124 through 126, inclusive. A port  ignores requests (see 10.3.14) for unsupported values.  
.1.3.111.2.802.1.1.20.1.5.1.21,IEEE8021-AS-MIB::ieee8021AsPortDSAnnounceReceiptTimeout,Unsigned32,read-write,,current,,The value is the number of Announce message  transmission intervals that a slave port waits without receiving an Announce message, before assuming that the master is no longer transmitting Announce  messages, and that the BMC algorithm needs to be run, if appropriate. The condition of the slave port not receiving an Announce message for  announceReceiptTimeout announce intervals is referred to as 'announce receipt timeout'. The default value is 3 (see 10.6.3.2). The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.22,IEEE8021-AS-MIB::ieee8021AsPortDSInitialLogSyncInterval,Integer32,read-write,,current,,The value is the logarithm to the base 2 of the sync interval used when,  (a) the port is initialized, or (b) a message interval request TLV is received with the timeSyncInterval field set to 126 (see 10.6.2.3, 11.5.2.3, 12.6.2, 13.9.2, and the  LinkDelaySyncIntervalSetting state machine, 11.2.17). The initialization value is -3 (see 10.6.2.3). The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.23,IEEE8021-AS-MIB::ieee8021AsPortDSCurrentLogSyncInterval,Integer32,read-only,,current,,The value is the logarithm to the base 2 of the current time-synchronization transmission interval, see 10.6.2.3.  The initialization value is -3. 
.1.3.111.2.802.1.1.20.1.5.1.24,IEEE8021-AS-MIB::ieee8021AsPortDSSyncReceiptTimeout,Unsigned32,read-write,,current,,The value of this attribute tells a slave port the number of sync intervals to wait without receiving synchronization information, before assuming that the master is no longer transmitting synchronization information, and that the BMC algorithm needs to be run, if appropriate. The condition of the slave port not receiving synchronization information for syncReceiptTimeout sync intervals is referred to as 'sync receipt timeout'. The initialization value is 3 (see 10.6.3.1). The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.25,IEEE8021-AS-MIB::ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalHs,Unsigned32,read-only,,current,,The most (highest) significant 32 bits, of unsigned  96 bit number in 2**-16 ns.  The value is equal to the value of the per port global variable syncReceiptTimeoutTimeInterval (see 10.2.4.2). It is the time interval after which sync receipt timeout occurs if time-synchronization information has not been received during the interval. This object MUST be read at the same time as  ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalMs, and  ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalLs, which  represents middle and least significant 32 bits of values, respectively, in order for the read  operation to succeed. Default value is calculated per 10.2.4.2, or  '0000 0000 0000 165A 0BC0 0000'h.  The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.26,IEEE8021-AS-MIB::ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalMs,Unsigned32,read-only,,current,,The middle significant 32 bits, unsigned  96 bit number in 2**-16 ns.  The value is equal to the value of the per port global variable syncReceiptTimeoutTimeInterval (see 10.2.4.2). It is the time interval after which sync receipt timeout occurs if time-synchronization information has not been received during the interval. This object MUST be read at the same time as  ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalHs, and  ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalLs, which  represents most (highest) and least significant 32 bits of values, respectively, in order for the read  operation to succeed. Default value is calculated per 10.2.4.2, or  '0000 0000 0000 165A 0BC0 0000'h.  The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.27,IEEE8021-AS-MIB::ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalLs,Unsigned32,read-only,,current,,The least significant 32 bits, unsigned  96 bit number in 2**-16 ns.  The value is equal to the value of the per port global variable syncReceiptTimeoutTimeInterval (see 10.2.4.2). It is the time interval after which sync receipt timeout occurs if time-synchronization information has not been received during the interval. This object MUST be read at the same time as  ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalHs, and  ieee8021AsPortDSSyncReceiptTimeoutTimeIntervalMs, which  represents most (highest) and middle significant 32 bits of values, respectively, in order for the read  operation to succeed. Default value is calculated per 10.2.4.2, or  '0000 0000 0000 165A 0BC0 0000'h.  The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.28,IEEE8021-AS-MIB::ieee8021AsPortDSInitialLogPdelayReqInterval,Integer32,read-write,,current,,For full-duplex, IEEE 802.3 media and CSN media that use the peer delay mechanism to measure path delay (see E.4.3.1), the value is the logarithm to the base 2 of the Pdelay_Req message transmission interval used when, (a) the port is initialized, or (b) a message interval request TLV is received with the  linkDelayInterval field set to 126 (see 11.5.2.2 and the LinkDelaySyncIntervalSetting state machine,  11.2.17). For these media, the initialization value is 0.  For all other media, the value is 127. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.29,IEEE8021-AS-MIB::ieee8021AsPortDSCurrentLogPdelayReqInterval,Integer32,read-only,,current,,For full-duplex, IEEE 802.3 media and CSN media that use the peer delay mechanism to measure path delay (see E.4.3.1), the value is the logarithm to the base 2 of the current Pdelay_Req message transmission interval, see 11.5.2.2. For all other media, the value is 127. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.30,IEEE8021-AS-MIB::ieee8021AsPortDSAllowedLostResponses,Unsigned32,read-write,,current,,The value is equal to the value of the per-port global variable allowedLostResponses (see 11.2.12.4). It is the number of Pdelay_Req messages for which a valid response is not received, above which a port is considered to not be exchanging peer delay messages with its neighbor. 
.1.3.111.2.802.1.1.20.1.5.1.31,IEEE8021-AS-MIB::ieee8021AsPortDSVersionNumber,Unsigned32,read-only,,current,,Indicates the PTP version in use on the port. The version number for this standard is set to  the value 2 (see 10.5.2.2.3). The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.32,IEEE8021-AS-MIB::ieee8021AsPortDSNupMs,Unsigned32,read-write,,current,,The most significant 32 bits, of unsigned  64 bit fixed point number between 0 and less than 2.  For an OLT port of an IEEE 802.3 EPON link, the value is the effective index of refraction for the EPON upstream wavelength light of the optical path (see 13.1.4 and 13.8.1.2). The default value is  1.46770 for 1 Gb/s upstream links, and 1.46773 for 10 Gb/s upstream links. For all other ports, the value is 0. This object MUST be read or written at the same time as  ieee8021AsPortDSNupLs, which represents least significant 32 bits of the value in order for the read  or write operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.33,IEEE8021-AS-MIB::ieee8021AsPortDSNupLs,Unsigned32,read-write,,current,,The least significant 32 bits, of unsigned  64 bit fixed point number between 0 and less than 2.  For an OLT port of an IEEE 802.3 EPON link, the value is the effective index of refraction for the EPON upstream wavelength light of the optical path (see 13.1.4 and 13.8.1.2). The default value is 1.46770 for 1 Gb/s upstream links, and 1.46773 for 10 Gb/s upstream links. For all other ports, the value is 0. This object MUST be read or written at the same time as  ieee8021AsPortDSNupMs, which represents the most significant 32 bits of the value in order for the read  or write operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.34,IEEE8021-AS-MIB::ieee8021AsPortDSNdownMs,Unsigned32,read-write,,current,,The least significant 32 bits, of unsigned  64 bit fixed point number between 0 and less than 2.  For an OLT port of an IEEE 802.3 EPON link, the value is the effective index of refraction for the EPON downstream wavelength light of the optical path (see 13.1.4 and 13.8.1.2.2). The default value is 1.46805 for 1 Gb/s downstream links, and 1.46851 for 10 Gb/s downstream links. For all other ports, the value is 0. This object MUST be read or written at the same time as  ieee8021AsPortDSNdownLs, which represents the least significant 32 bits of the value in order for the read  or write operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.35,IEEE8021-AS-MIB::ieee8021AsPortDSNdownLs,Unsigned32,read-write,,current,,The least significant 32 bits, of unsigned  64 bit fixed point number between 0 and less than 2.  For an OLT port of an IEEE 802.3 EPON link, the value is the effective index of refraction for the EPON downstream wavelength light of the optical path (see 13.1.4 and 13.8.1.2.1). The default value is  1.46805 for 1 Gb/s downstream links, and 1.46851 for 10 Gb/s downstream links. For all other ports, the value is 0. This object MUST be read or written at the same time as  ieee8021AsPortDSNdownMs, which represents the most significant 32 bits of the value in order for the read  or write operation to succeed. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.5.1.36,IEEE8021-AS-MIB::ieee8021AsPortDSAcceptableMasterTableEnabled,INTEGER,read-write,,current,true(1):false(2),True (1) if acceptableMasterTableEnabled (see 13.1.3.1)  and 13.1.3.5) is true and an ONU port attached to an  IEEE 802.3 EPON link in a time-aware system. False (2), otherwise. The default value is FALSE. The contents of this variable SHALL be maintained  across a restart of the system. 
.1.3.111.2.802.1.1.20.1.6,IEEE8021-AS-MIB::ieee8021AsPortStatIfTable,,not-accessible,,current,,A table of time-aware port related counters in a gPTP domain. A value of 1 is used in a bridge or an end station that does not  have multiple components. 
.1.3.111.2.802.1.1.20.1.6.1,IEEE8021-AS-MIB::ieee8021AsPortStatIfEntry,,not-accessible,ieee8021AsBridgeBasePort:ieee8021AsPortDSAsIfIndex,current,,A list of statistics pertaining to a port of a gPTP domain.  This statistics table uses ieee8021AsPortDSAsIfIndex, and  corresponds to ieee8021ASPortDSTable entries. 
.1.3.111.2.802.1.1.20.1.6.1.1,IEEE8021-AS-MIB::ieee8021AsPortStatRxSyncCount,Counter32,read-only,,current,,A counter that increments every time synchronization  information is received, denoted by a transition to  TRUE from FALSE of the rcvdSync variable of the  MDSyncReceiveSM state machine (see 11.2.13.1.2 and  Figure 11-6), when in the DISCARD or WAITING_FOR_SYNC  states; or rcvdIndication transitions to TRUE (see Figure 12-3). 
.1.3.111.2.802.1.1.20.1.6.1.2,IEEE8021-AS-MIB::ieee8021AsPortStatRxFollowUpCount,Counter32,read-only,,current,,A counter that increments every time a Follow_Up message  is received, denoted by a transition to TRUE from FALSE  of the rcvdFollowUp variable of the MDSyncReceiveSM  state machine (see 11.2.13.1.3 and Figure 11-6) when in  the WAITING_FOR_FOLLOW_UP state.  
.1.3.111.2.802.1.1.20.1.6.1.3,IEEE8021-AS-MIB::ieee8021AsPortStatRxPdelayRequest,Counter32,read-only,,current,,A counter that increments every time a Pdelay_Req message  is received, denoted by a transition to TRUE from FALSE  of the rcvdPdelayReq variable of the MDPdelayResp state  machine (see 11.2.16.1.1 and Figure 11-9) when in the  WAITING_FOR_PDELAY_REQ or INITIAL_WAITING_FOR_PDELAY_REQ  states. 
.1.3.111.2.802.1.1.20.1.6.1.4,IEEE8021-AS-MIB::ieee8021AsPortStatRxPdelayResponse,Counter32,read-only,,current,,A counter that increments every time a Pdelay_Resp  message is received, denoted by a transition to TRUE  from FALSE of the rcvdPdelayResp variable of the  MDPdelayReq state machine (see 11.2.15.1.2 and Figure  11-8) when in the WAITING_FOR_PDELAY_RESP state. 
.1.3.111.2.802.1.1.20.1.6.1.5,IEEE8021-AS-MIB::ieee8021AsPortStatRxPdelayResponseFollowUp,Counter32,read-only,,current,,A counter that increments every time a  Pdelay_Resp_Follow_Up message is received, denoted by a  transition to TRUE from FALSE of the  rcvdPdelayRespFollowUp variable of the MDPdelayReq  state machine (see 11.2.15.1.4 and Figure 11-8) when in  the WAITING_FOR_PDELAY_RESP_FOLLOW_UP state. 
.1.3.111.2.802.1.1.20.1.6.1.6,IEEE8021-AS-MIB::ieee8021AsPortStatRxAnnounce,Counter32,read-only,,current,,A counter that increments every time an Announce message  is received, denoted by a transition to TRUE from FALSE  of the rcvdAnnounce variable of the PortAnnounceReceive  state machine (see 10.3.10 and Figure 10-12) when in the  DISCARD or RECEIVE states. 
.1.3.111.2.802.1.1.20.1.6.1.7,IEEE8021-AS-MIB::ieee8021AsPortStatRxPTPPacketDiscard,Counter32,read-only,,current,,A counter that increments every time a PTP message is discarded, caused by the occurrence of any of the following conditions: a) A received Announce message is not qualified, denoted by the function qualifyAnnounce (see  10.3.10.2.1 and 13.1.3.4) of the PortAnnounceReceive  state machine (see 10.3.10 and Figure 10-12) returning FALSE; b) A Follow_Up message corresponding to a received Sync  message is not received, denoted by a transition of  the condition (currentTime greater or equal to followUpReceiptTimeoutTime) to TRUE from FALSE when  in the WAITING_FOR_FOLLOW_UP state of the  MDSyncReceiveSM state machine (see 11.2.13 and  Figure 11-6); c) A Pdelay_Resp message corresponding to a  transmitted Pdelay_Req message is not received,  denoted by a transition from the  WAITING_FOR_PDELAY_RESP state to the RESET state of  the MDPdelayReq state machine (see 11.2.15 and  Figure 11-8); d) A Pdelay_Resp_Follow_Up message corresponding to a  transmitted Pdelay_Req message is not received,  denoted by a transition from the  WAITING_FOR_PDELAY_RESP_FOLLOW_UP state to the  RESET state of the MDPdelayReq state machine (see  11.2.15 and Figure 11-8). 
.1.3.111.2.802.1.1.20.1.6.1.8,IEEE8021-AS-MIB::ieee8021AsPortStatRxSyncReceiptTimeouts,Counter32,read-only,,current,,A counter that increments every time sync receipt timeout  occurs, denoted by entering the AGED state of the  PortAnnounceInformation state machine (see 10.3.11 and  Figure 10-13), with the condition (currentTime greater or  equual to announceReceiptTimeoutTime) TRUE 
.1.3.111.2.802.1.1.20.1.6.1.9,IEEE8021-AS-MIB::ieee8021AsPortStatAnnounceReceiptTimeouts,Counter32,read-only,,current,,A counter that increments every time announce receipt  timeout occurs, denoted by entering the AGED state of  the PortAnnounceInformation state machine (see 10.3.11  and Figure 10-13), with the condition ((currentTime  greater than or equal to syncReceiptTimeoutTime) AND gmPresent)) TRUE. 
.1.3.111.2.802.1.1.20.1.6.1.10,IEEE8021-AS-MIB::ieee8021AsPortStatPdelayAllowedLostResponsesExceeded,Counter32,read-only,,current,,A counter that increments everytime the value of the  variable lostResponses (see, 11.2.15.1.10) exceeds the  value of the variable allowedLostResponses (see  11.2.12.4), in the RESET state of the MDPdelayReq state  machine (see 11.2.15 and Figure 11-8) 
.1.3.111.2.802.1.1.20.1.6.1.11,IEEE8021-AS-MIB::ieee8021AsPortStatTxSyncCount,Counter32,read-only,,current,,A counter that increments every time synchronization information is transmitted, denoted by a transition to TRUE from FALSE of the rcvdMDSync variable of the MDSyncSendSM state machine (see 11.2.14.1.1 and Figure 11-7), when in the INITIALIZING or SEND_FOLLOW_UP states; or the INITIATE_REQUEST_WAIT_CONFIRM state is entered in Figure 12-3. 
.1.3.111.2.802.1.1.20.1.6.1.12,IEEE8021-AS-MIB::ieee8021AsPortStatTxFollowUpCount,Counter32,read-only,,current,,A counter that increments every time a Follow_Up message  is transmitted, denoted by a transition to TRUE from  FALSE of the rcvdMDTimestampReceive variable of the  MDSyncSendSM state machine (see 11.2.14.1.3 and Figure  11-7), when in the SEND_SYNC state increments every time  a Follow_Up packet is transmitted. 
.1.3.111.2.802.1.1.20.1.6.1.13,IEEE8021-AS-MIB::ieee8021AsPortStatTxPdelayRequest,Counter32,read-only,,current,,A counter that increments every time a Pdelay_Req message  is transmitted, denoted by entering the  INITIAL_SEND_PDELAY_REQ or SEND_PDELAY_REQ states of the  MDPdelayReq state machine (see 11.2.15 and Figure 11-8). 
.1.3.111.2.802.1.1.20.1.6.1.14,IEEE8021-AS-MIB::ieee8021AsPortStatTxPdelayResponse,Counter32,read-only,,current,,A counter that increments every time a Pdelay_Resp  message is transmitted, denoted by a transition to TRUE  from FALSE of the rcvdPdelayReq variable of the  MDPdelayResp state machine (see 11.2.16.1.1 and  Figure 11-9) when in the WAITING_FOR_PDELAY_REQ or  INITIAL_WAITING_FOR_PDELAY_REQ states, and resulting  entry to the SENT_PDELAY_RESP_WAITING_FOR_TIMESTAMP  state. 
.1.3.111.2.802.1.1.20.1.6.1.15,IEEE8021-AS-MIB::ieee8021AsPortStatTxPdelayResponseFollowUp,Counter32,read-only,,current,,A counter that increments every time a  Pdelay_Resp_Follow_Up message is transmitted, denoted  by a transition to TRUE from FALSE of the  rcvdMDTimestampReceive variable of the MDPdelayResp  state machine (see 11.2.16.1.2 and Figure 11-9) when in  the SENT_PDELAY_RESP_WAITING_FOR_TIMESTAMP state, and  resulting entry to the WAITING_FOR_PDELAY_REQ state. 
.1.3.111.2.802.1.1.20.1.6.1.16,IEEE8021-AS-MIB::ieee8021AsPortStatTxAnnounce,Counter32,read-only,,current,,A counter that increments every time an Announce message  is transmitted, denoted by entering the  TRANSMIT_ANNOUNCE state of the PortAnnounceReceive state  machine (see 10.3.13 and Figure 10-15). 
.1.3.111.2.802.1.1.20.1.7,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDS,,,,,,
.1.3.111.2.802.1.1.20.1.7.1,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSBase,,,,,,
.1.3.111.2.802.1.1.20.1.7.1.1,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSMaxTableSize,Unsigned32,read-only,,current,,The value is the maximum size of the AcceptableMasterTable. It is equal to the maxTableSize member of the AcceptableMasterTable structure (see 13.1.3.2)
.1.3.111.2.802.1.1.20.1.7.1.2,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSActualTableSize,Unsigned32,read-write,,current,,The value is the actual size of the AcceptableMasterTable. It is equal to the actualTableSize member of the AcceptableMasterTable structure (see 13.1.3.2 and 13.1.3.5),  i.e., the current number of  elements in the acceptable master array. The actual table size is less than or equal to the max table size. This value SHOULD be reflect the number of entries in  the ieee8021AsAcceptableMasterTableDSMasterTable. For a time-aware system that contains an ONU attached to an IEEE 802.3 EPON link, the initialization value is 1. For a time-aware system that does not contain an ONU attached to an IEEE 802.3 EPON link, the initialization value is 0.
.1.3.111.2.802.1.1.20.1.7.2,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSMaster,,,,,,
.1.3.111.2.802.1.1.20.1.7.2.1,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSMasterTable,,not-accessible,,current,,A table of time-aware port related variables in a time-aware  bridge or for a time-aware end station. A value of 1 is used in  a bridge or an end station that does not have multiple  components. The contents of this table SHALL be maintained across a restart of the system. 
.1.3.111.2.802.1.1.20.1.7.2.1.1,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSMasterEntry,,not-accessible,ieee8021AsAcceptableMasterTableDSMasterId,current,,A list of objects pertaining to a port of a time-aware bridge  component or a time-aware end station. 
.1.3.111.2.802.1.1.20.1.7.2.1.1.1,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableDSMasterId,Unsigned32,not-accessible,,current,,Acceptable Master row entry index in this  ieee8021AsAcceptableMasterTabdDSMaster Entry applies.  If the does not contain Media type of EPON, this variable (index) MUST be equal to 0.
.1.3.111.2.802.1.1.20.1.7.2.1.1.2,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterClockIdentity,OCTET,read-create,,current,,Globally unique manufacturer-assigned clock identifier for the local clock port. The identifier is based on an EUI-64.
.1.3.111.2.802.1.1.20.1.7.2.1.1.3,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterPortNumber,Unsigned32,read-create,,current,,This object represents a Port or aggregated port on a bridge component or end-station.  This object and ieee8021AsAcceptableMasterClockIdentity together forms AcceptableMasterDS Port Identity.
.1.3.111.2.802.1.1.20.1.7.2.1.1.4,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterAlternatePriority1,Unsigned32,read-create,,current,,If the alternatePriority1 member of the AcceptableMaster  array element that corresponds to the sourcePortIdentity  of a received Announce message is greater than 0, the  value of the grandmasterPriority1 field of the Announce  message is replaced by the value of alternatePriority1  of this AcceptableMaster array element for use in the  invocation of BMCA
.1.3.111.2.802.1.1.20.1.7.2.1.1.5,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This object indicates the status of an entry, and is used to create/delete entries. 
.1.3.111.2.802.1.1.20.2,IEEE8021-AS-MIB::ieee8021AsConformance,,,,,,
.1.3.111.2.802.1.1.20.2.1,IEEE8021-AS-MIB::ieee8021AsCompliances,,,,,,
.1.3.111.2.802.1.1.20.2.1.1,IEEE8021-AS-MIB::ieee8021AsCompliance,,,,,,The compliance statement for support of the IEEE8021-AS-MIB module.
.1.3.111.2.802.1.1.20.2.1.2,IEEE8021-AS-MIB::ieee8021AsComplianceCor1,,,,,,The compliance statement for support of the IEEE8021-AS-MIB module.
.1.3.111.2.802.1.1.20.2.2,IEEE8021-AS-MIB::ieee8021AsGroups,,,,,,
.1.3.111.2.802.1.1.20.2.2.1,IEEE8021-AS-MIB::ieee8021ASSystemDefaultReqdGroup,,,,,,Objects in the System Default required global group.
.1.3.111.2.802.1.1.20.2.2.2,IEEE8021-AS-MIB::ieee8021ASSystemCurrentGroup,,,,,,Objects in the System Current global group.
.1.3.111.2.802.1.1.20.2.2.3,IEEE8021-AS-MIB::ieee8021AsSystemClockParentGroup,,,,,,Objects in the Clock Parent global group.
.1.3.111.2.802.1.1.20.2.2.4,IEEE8021-AS-MIB::ieee8021AsSystemTimePropertiesGroup,,,,,,Objects for the Time Properties Global group.
.1.3.111.2.802.1.1.20.2.2.5,IEEE8021-AS-MIB::ieee8021AsPortDataSetGlobalGroup,,,,,,Objects for the port dataset global group.
.1.3.111.2.802.1.1.20.2.2.6,IEEE8021-AS-MIB::ieee8021ASPortStatisticsGlobalGroup,,,,,,Objects in the Port statistics global group.
.1.3.111.2.802.1.1.20.2.2.7,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterBaseGroup,,,,,,Objects for the Acceptable Master group.
.1.3.111.2.802.1.1.20.2.2.8,IEEE8021-AS-MIB::ieee8021AsAcceptableMasterTableGroup,,,,,,Objects for the Acceptable Master group.
.1.3.111.2.802.1.1.20.2.3,IEEE8021-AS-MIB::ieee8021AsCompliancesCor1,,,,,,
.1.3.111.2.802.1.1.21,IEEE8021-PFC-MIB::ieee8021PFCMib,,,,,,Priority-based Flow Control module for IEEE Std 802.1Q. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices. 
.1.3.111.2.802.1.1.21.1,IEEE8021-PFC-MIB::ieee8021PfcMIBObjects,,,,,,
.1.3.111.2.802.1.1.21.1.1,IEEE8021-PFC-MIB::ieee8021PfcIfTable,,not-accessible,,current,,A table of PFC information for all interfaces of a system.
.1.3.111.2.802.1.1.21.1.1.1,IEEE8021-PFC-MIB::ieee8021PfcIfEntry,,not-accessible,,current,,Each entry contains information about the PFC function on a single interface.
.1.3.111.2.802.1.1.21.1.1.1.1,IEEE8021-PFC-MIB::ieee8021PfcLinkDelayAllowance,Unsigned32,read-write,,current,,The allowance made for round-trip propagation delay  of the link in bits. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.21.1.1.1.2,IEEE8021-PFC-MIB::ieee8021PfcRequests,Counter32,read-only,,current,,A count of the invoked PFC M_CONTROL.request primitives. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.111.2.802.1.1.21.1.1.1.3,IEEE8021-PFC-MIB::ieee8021PfcIndications,Counter32,read-only,,current,,A count of the received PFC M_CONTROL.indication primitives. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
.1.3.111.2.802.1.1.21.2,IEEE8021-PFC-MIB::ieee8021PfcConformance,,,,,,
.1.3.111.2.802.1.1.21.2.1,IEEE8021-PFC-MIB::ieee8021PfcCompliances,,,,,,
.1.3.111.2.802.1.1.21.2.1.1,IEEE8021-PFC-MIB::ieee8021PfcCompliance,,,,,,The compliance statement for support by a system of the IEEE8021-PFC-MIB module.
.1.3.111.2.802.1.1.21.2.2,IEEE8021-PFC-MIB::ieee8021PfcGroups,,,,,,
.1.3.111.2.802.1.1.21.2.2.1,IEEE8021-PFC-MIB::ieee8021PfcGlobalReqdGroup,,,,,,Objects in the global required group.
.1.3.111.2.802.1.1.22,IEEE8021-MVRPX-MIB::ieee8021MvrpxMib,,,,,,Multiple VLAN Registration Protocol extension module for managing MVRP extensions defined in IEEE Std 802.1Q Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices. 
.1.3.111.2.802.1.1.22.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxMIBObjects,,,,,,
.1.3.111.2.802.1.1.22.1.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxPortTable,,not-accessible,,current,,A table that contains controls for the Multiple VLAN Registration Protocol (MVRP) state machines for all of the Ports of a Bridge.
.1.3.111.2.802.1.1.22.1.1.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxPortEntry,,not-accessible,,current,,Each entry contains the MVRP Registrar controls for one Port.
.1.3.111.2.802.1.1.22.1.1.1.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxPortNewOnly,INTEGER,read-create,,current,true(1):false(2),The mode of operation of the MVRP state machines on this port, if enabled. The value of this object and the value of the individual Port+Attribute type enable object ieee8021QBridgePortMvrpEnabledStatus combine to control the state machines as follows: ieee8021MvrpxPortNewOnly ieee8021QBridgePortMvrpEnabledStatus MVRP state machines not implemented true(1) Full participant false(2) true(1) Full participant true(1) true(1) New-only participant not implemented false(2) MVRP disabled false(2) false(2) MVRP disabled true(1) false(2) MVRP disabled This object affects all MVRP Applicant and Registrar state machines on this port. A change to the value of this object will cause a reset of all MVRP state machines for this attribute type on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.22.1.1.1.2,IEEE8021-MVRPX-MIB::ieee8021MvrpxPortMvrpNewPropagated,INTEGER,read-create,,current,true(1):false(2),The mode of operation of the MVRP on this port, if enabled. If this object contains the value true(1), then all Static VLAN Registration Entries that are Registration Fixed are treated as Registration Fixed (New propagated), and if false(2), as Registration Fixed (New ignored) This object affects only the MVRP Applicant and Registrar state machines on this port. A change to the value of this object will cause a reset of all MVRP state machines on this port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.22.1.1.1.3,IEEE8021-MVRPX-MIB::ieee8021MvrpxPortXmitZero,INTEGER,read-create,,current,true(1):false(2),Selects whether MVRP is enabled to transmit 0 as the attribute value for the one VLAN ID for which this Port is in the untagged set, true(1) to enable transmit 0, and false(2) to transmit the VLAN ID. The value 0 is not transmitted unless ieee8021MvrpxPortNewOnly is true(1). This feature is optional. If not supported, the system SHALL NOT allow this object to be set to the value true(1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.22.2,IEEE8021-MVRPX-MIB::ieee8021MvrpxConformance,,,,,,
.1.3.111.2.802.1.1.22.2.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxCompliances,,,,,,
.1.3.111.2.802.1.1.22.2.1.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxCompliance,,,,,,The compliance statement for support by a Bridge of the IEEE8021-MVRPX-MIB module.
.1.3.111.2.802.1.1.22.2.2,IEEE8021-MVRPX-MIB::ieee8021MvrpxGroups,,,,,,
.1.3.111.2.802.1.1.22.2.2.1,IEEE8021-MVRPX-MIB::ieee8021MvrpxReqdGroup,,,,,,Objects in the MVRP extension augmentation table required group.
.1.3.111.2.802.1.1.23,IEEE8021-MIRP-MIB::ieee8021MirpMib,,,,,,Multiple I-SID Registration Protocol module for managing IEEE 802.1Qbe Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices. 
.1.3.111.2.802.1.1.23.1,IEEE8021-MIRP-MIB::ieee8021MirpV2MIBObjects,,,,,,
.1.3.111.2.802.1.1.23.1.1,IEEE8021-MIRP-MIB::ieee8021MirpV2PortTable,,not-accessible,,current,,A table that contains controls for the Multiple I-SID Registration Protocol (MIRP) state machines for all of the Ports of a Bridge.
.1.3.111.2.802.1.1.23.1.1.1,IEEE8021-MIRP-MIB::ieee8021MirpV2PortEntry,,not-accessible,,current,,Each entry contains the MIRP Participant controls for one Port.
.1.3.111.2.802.1.1.23.1.1.1.1,IEEE8021-MIRP-MIB::ieee8021MirpV2PortEnabledStatus,INTEGER,read-create,,current,true(1):false(2),The state of MIRP operation on this port. The value true(1) indicates that MIRP is enabled on this port, as long as ieee8021PbbMirpEnableStatus is also enabled for this component. When false(2) but ieee8021PbbMirpEnableStatus is still enabled for the device, MIRP is disabled on this port. If MIRP is enabled on a VIP, then the MIRP Participant is enabled on that VIP's PIP. If MIRP is enabled on none of the VIPs on a PIP, then the MIRP Participant on the PIP is diabled; any MIRP packets received will be silently discarded, and no MIRP registrations will be propagated from the PIP. A transition from all VIPs on a PIP false(2) to at least one VIP on the PIP true(1) will cause a reset of all MIRP state machines on this PIP. If MIRP is enabled on any port not a VIP, then the MIRP Participant is enabled on that port. If MIRP is disabled on a non-VIP port, then MIRP packets received will be silently discarded, and no MIRP registrations will be propagated from the port. A transition from false(2) to true(1) will cause a reset of all MIRP state machines on a non-VIP port. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.23.2,IEEE8021-MIRP-MIB::ieee8021MirpV2Conformance,,,,,,
.1.3.111.2.802.1.1.23.2.1,IEEE8021-MIRP-MIB::ieee8021MirpV2Compliances,,,,,,
.1.3.111.2.802.1.1.23.2.1.1,IEEE8021-MIRP-MIB::ieee8021MirpV2BridgeCompliance,,,,,,The compliance statement for support by a Bridge of the IEEE8021-MIRP-MIB module.
.1.3.111.2.802.1.1.23.2.2,IEEE8021-MIRP-MIB::ieee8021MirpV2Groups,,,,,,
.1.3.111.2.802.1.1.23.2.2.1,IEEE8021-MIRP-MIB::ieee8021MirpV2ReqdGroup,,,,,,Objects in the MIRP augmentation required group.
.1.3.111.2.802.1.1.24,IEEE8021-EVB-MIB::ieee8021BridgeEvbMib,,,,,,The EVB MIB module for managing devices that support Edge Virtual Bridging. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.24.0,IEEE8021-EVB-MIB::ieee8021BridgeEvbNotifications,,,,,,
.1.3.111.2.802.1.1.24.0.1,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgAdminFailure,,,,,,An IPG generates this notification whenever an adminisistrative command cannot be executed by the IPS state machine. For example, when a requested manual switch cannot be performed because of a signal failure condition. The management entity receiving the notification can identify the system from the network source address of the notification and can identify the IPG by the indices of  the OID of the ieee8021TeipsIpgConfigState variable in the notification:  ieee8021BridgeBaseComponentId - Identifies the component on the bridge where the protection group is configured. ieee8021TeipsIpgid - The ID of the protection group. 
.1.3.111.2.802.1.1.24.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbObjects,,,,,,
.1.3.111.2.802.1.1.24.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbSys,,,,,,
.1.3.111.2.802.1.1.24.1.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysType,INTEGER,read-only,,current,evbBridge(1):evbStation(2),The evbSysType determines if this is an EVB Bridge  or EVB station.
.1.3.111.2.802.1.1.24.1.1.1.1,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgid,Unsigned32,not-accessible,,current,,Uniquely identifies an IPG within the PBB.
.1.3.111.2.802.1.1.24.1.1.1.2,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgWorkingMA,Unsigned32,read-create,,current,,Identifies the Segment MA that corresponds to the IPG's working entity. The MA index in this column must hold a value that is the value of dot1agCfmStackMaIndex column for some entry in the dot1agCfmStackTable before the RowStatus for this row can be set to Active. Furthermore, this column may not be modified when the RowStatus for this row is Active.
.1.3.111.2.802.1.1.24.1.1.1.3,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgProtectionMA,Unsigned32,read-create,,current,,Identifies the Segment MA that corresponds to the IPG's protection entity. The MA index in this column must hold a value that is the value of dot1agCfmStackMaIndex column for some entry in the dot1agCfmStackTable before the RowStatus for this row can be set to Active. Furthermore, this column may not be modified when the RowStatus for this row is Active.
.1.3.111.2.802.1.1.24.1.1.1.4,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgWorkingPortNumber,Unsigned32,read-only,,current,,Identifies the local Port associated with the IPG Working Segment.
.1.3.111.2.802.1.1.24.1.1.1.5,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgProtectionPortNumber,Unsigned32,read-only,,current,,Identifies the local Port associated with the IPG Protection Segment.
.1.3.111.2.802.1.1.24.1.1.1.6,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable if this column is set to permanent.
.1.3.111.2.802.1.1.24.1.1.1.7,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. The writable columns in a row cannot be changed if the row is active. The TeipsIpgWorkingMA and TeipsIpgProtectionMA columns must be specified before the row can be activated.
.1.3.111.2.802.1.1.24.1.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysNumExternalPorts,Unsigned32,read-only,,current,,The evbSysNumExternalPorts parameter indicates how  many externally accessible port are available.
.1.3.111.2.802.1.1.24.1.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysEvbLldpTxEnable,INTEGER,read-write,,current,true(1):false(2),This object is used to initialize the LLDP EVB  objects for new SBPs and URPS. When set to 'true' a new SBP or URP will place the local EVB objects in the LLDP nearest Customer database; when set to 'false' a new SBP or URP will not place the local EVB objects in the LLDP database.
.1.3.111.2.802.1.1.24.1.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysEvbLldpManual,INTEGER,read-write,,current,true(1):false(2),This object is used to initialize the LLDP EVB  objects for new SBPs and URPS. When set to 'false' the operating configuration will be determined by the comparison between  the local and remote LLDP EVB objects  (automatic), regardless of the setting of  ieee8021BridgeEvbSysLldpTxEnable.  When ieee8021BridgeEvbSysLldpManual is 'true' the configuration will be determined by the setting of the local EVB objects only (manual).
.1.3.111.2.802.1.1.24.1.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysEvbLldpGidCapable,INTEGER,read-write,,current,true(1):false(2),The value of this object is used as the default  value of the BGID or SGID bit of the EVB LLDP TLV string.
.1.3.111.2.802.1.1.24.1.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysEcpAckTimer,Integer32,read-write,,deprecated,,A value indicating the Bridge Proposed ECP ackTimer.
.1.3.111.2.802.1.1.24.1.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysEcpMaxRetries,Integer32,read-write,,current,,A value indicating the Bridge ECP maxRetries.
.1.3.111.2.802.1.1.24.1.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysVdpDfltRsrcWaitDelay,Integer32,read-write,,deprecated,,A value indicating the Bridge Resource VDP Timeout.
.1.3.111.2.802.1.1.24.1.1.9,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysVdpDfltReinitKeepAlive,Integer32,read-write,,deprecated,,A value indicating the Bridge Proposed VDP Keep Alive Timeout.
.1.3.111.2.802.1.1.24.1.1.10,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpTable,,not-accessible,,current,,A table that contains Station-facing Bridge Port (SBP)  details.
.1.3.111.2.802.1.1.24.1.1.10.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpEntry,,not-accessible,ieee8021BridgeEvbSbpComponentID:ieee8021BridgeEvbSbpPortNumber,current,,A list of objects describing SBP.
.1.3.111.2.802.1.1.24.1.1.10.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpComponentID,Unsigned32,not-accessible,,current,,The SBP component ID
.1.3.111.2.802.1.1.24.1.1.10.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpPortNumber,Unsigned32,not-accessible,,current,,The SBP port number.
.1.3.111.2.802.1.1.24.1.1.10.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpLldpManual,INTEGER,read-write,,current,true(1):false(2),The evbSbpLldpManual parameter switches EVB TLVs to manual mode.  In manual mode the running parameters are determined solely from the local LLDP database values.
.1.3.111.2.802.1.1.24.1.1.10.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpVdpOperRsrcWaitDelay,Unsigned32,read-only,,deprecated,,The value used to initialize the waitWhile timer  (41.5.5.7) by the station VDP state machine when the state machine is waiting for a response.
.1.3.111.2.802.1.1.24.1.1.10.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpVdpOperReinitKeepAlive,Unsigned32,read-only,,deprecated,,The value used to initialize the waitWhile timer  (41.5.5.5) by the station VDP state machine in  order to determine when to transmit a keep alive message.
.1.3.111.2.802.1.1.24.1.1.10.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpVdpOperToutKeepAlive,Unsigned32,read-only,,current,,The value used to initialize the waitWhile timer (41.5.5.13) by the EVBCB VDP state machine in order to determine when to transmit a keep alive message.
.1.3.111.2.802.1.1.24.1.1.10.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpVdpOperRsrcWaitDelayExp,Unsigned32,read-only,,current,,The exponent of 2 used to calculate the value to initialize the waitWhile timer  (41.5.5.7) by the station VDP state machine when the state machine is waiting for a response.
.1.3.111.2.802.1.1.24.1.1.10.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpVdpOperReinitKeepAliveExp,Unsigned32,read-only,,current,,The exponent of 2 used to calculate the value to initialize the waitWhile timer  (41.5.5.5) by the station VDP state machine in  order to determine when to transmit a keep alive message.
.1.3.111.2.802.1.1.24.1.1.11,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysEcpDfltAckTimerExp,Integer32,read-write,,current,,The exponent of 2 indicating the Bridge Proposed ECP ackTimer in tens of microseconds.
.1.3.111.2.802.1.1.24.1.1.12,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysVdpDfltRsrcWaitDelayExp,Integer32,read-write,,current,,The exponent of 2 indicating the Bridge Resource VDP  Timeout in tens of microseconds.
.1.3.111.2.802.1.1.24.1.1.13,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysVdpDfltReinitKeepAliveExp,Integer32,read-write,,current,,The exponent of 2 indicating the Bridge Proposed VDP Keep Alive Timeout in tens of microseconds.
.1.3.111.2.802.1.1.24.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBObjects,,,,,,
.1.3.111.2.802.1.1.24.1.2.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBTable,,not-accessible,,current,,A table that contains database of the active Virtual Station  Interfaces.
.1.3.111.2.802.1.1.24.1.2.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBEntry,,not-accessible,ieee8021BridgeEvbVSIComponentID:ieee8021BridgeEvbVSIPortNumber:ieee8021BridgeEvbVSIIDType:ieee8021BridgeEvbVSIID,current,,A list of objects containing database of the active Virtual Station Interfaces.
.1.3.111.2.802.1.1.24.1.2.1.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIComponentID,Unsigned32,not-accessible,,current,,The evbVSIComponentID is the ComponentID for the  C-VLAN component of the EVB Bridge or for the edge relay of the EVB station.
.1.3.111.2.802.1.1.24.1.2.1.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIPortNumber,Unsigned32,not-accessible,,current,,The evbVSIPortNumber is the Port Number for the SBP or URP where the VSI is accessed.
.1.3.111.2.802.1.1.24.1.2.1.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIIDType,INTEGER,not-accessible,,current,vsiidIpv4(1):vsiidIpv6(2):vsiidMAC(3):vsiidLocal(4):vsiidUUID(5),This object specifies the VSIID Type for the VSIID in the DCN 
.1.3.111.2.802.1.1.24.1.2.1.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIID,OCTET,not-accessible,,current,,This object specifies the VSIID that uniquely identifies the VSI  in the DCN 
.1.3.111.2.802.1.1.24.1.2.1.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSITimeSinceCreate,Unsigned32,read-only,,current,,This object specifies the time since creation 
.1.3.111.2.802.1.1.24.1.2.1.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbVsiVdpOperCmd,INTEGER,read-only,,current,preAssociate(1):preAssociateWithRsrcReservation(2):associate(3):deAssociate(4),This object identifies the type of TLV.
.1.3.111.2.802.1.1.24.1.2.1.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbVsiOperRevert,INTEGER,read-only,,current,true(1):false(2),The evbOperRevert status indicator shows the most  recent value of the KEEP indicator from the VDP protocol exchange.
.1.3.111.2.802.1.1.24.1.2.1.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbVsiOperHard,INTEGER,read-only,,current,true(1):false(2),The evbVsiHard status indicator shows the most recent value of the HARD indicator from the VDP protocol exchange.
.1.3.111.2.802.1.1.24.1.2.1.1.9,IEEE8021-EVB-MIB::ieee8021BridgeEvbVsiOperReason,BITS,read-only,,current,success(0):invalidFormat(1):insufficientResources(2):otherfailure(3),This object indicates the outcome of a request.
.1.3.111.2.802.1.1.24.1.2.1.1.10,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIMgrID,OCTET,read-only,,deprecated,,This object identifies the VSI Manager with a database that holds the detailed VSI type and or instance definitions.
.1.3.111.2.802.1.1.24.1.2.1.1.11,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIType,Integer32,read-only,,current,, The VTID is an integer value used to identify a pre-configured set of controls and attributes that are associated with a set of VSIs.
.1.3.111.2.802.1.1.24.1.2.1.1.12,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSITypeVersion,OCTET,read-only,,current,,The VSI Type Version is an integer identifier designating the
.1.3.111.2.802.1.1.24.1.2.1.1.13,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIMvFormat,INTEGER,read-only,,deprecated,basic(1):partial(2):vlanOnly(3),This object specifies the MAC/VLAN format. basic - Basic MAC/VLAN format partial - Partial MAC/VLAN format vlanOnly - Vlan-only MAC/VLAN format
.1.3.111.2.802.1.1.24.1.2.1.1.14,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSINumMACs,Integer32,read-only,,current,,This object specifies the the number of MAC address/VLAN ID pairs
.1.3.111.2.802.1.1.24.1.2.1.1.15,IEEE8021-EVB-MIB::ieee8021BridgeEvbVDPMachineState,INTEGER,read-only,,current,preAssociate(1):preAssociateWithRsrcReservation(2):associate(3):deAssociate(4),This object specifies the VDP state machine. 
.1.3.111.2.802.1.1.24.1.2.1.1.16,IEEE8021-EVB-MIB::ieee8021BridgeEvbVDPCommandsSucceeded,Counter32,read-only,,current,,This object specifies the VDP number of successful commands since creation.
.1.3.111.2.802.1.1.24.1.2.1.1.17,IEEE8021-EVB-MIB::ieee8021BridgeEvbVDPCommandsFailed,Counter32,read-only,,current,,This object specifies the VDP number of failed commands since 
.1.3.111.2.802.1.1.24.1.2.1.1.18,IEEE8021-EVB-MIB::ieee8021BridgeEvbVDPCommandReverts,Counter32,read-only,,current,,This object specifies the VDP command reverts since creation 
.1.3.111.2.802.1.1.24.1.2.1.1.19,IEEE8021-EVB-MIB::ieee8021BridgeEvbVDPCounterDiscontinuity,TimeTicks,read-only,,current,,The time (in hundredths of a second) since the last counter discontinuity for any of the counters in the row.
.1.3.111.2.802.1.1.24.1.2.1.1.20,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIMgrID16,OCTET,read-only,,current,,This object identifies the VSI Manager with a database that holds the detailed VSI type and or instance definitions.
.1.3.111.2.802.1.1.24.1.2.1.1.21,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIFilterFormat,INTEGER,read-only,,current,vid(1):macVid(2):groupidVid(3):groupidMacVid(4),This object specifies the MAC/VLAN format: vid (see 41.2.9.1) macVid (see 41.2.9.2) groupidVid (see 41.2.9.3) groupidMacVid (see 41.2.9.4)
.1.3.111.2.802.1.1.24.1.2.1.2,IEEE8021-TEIPS-MIB::ieee8021TeipsTesiId,Unsigned32,read-create,,current,,This column holds the TESI identifier corresponding to a TE service instance associated with an IPG.
.1.3.111.2.802.1.1.24.1.2.1.3,IEEE8021-TEIPS-MIB::ieee8021TeipsTesiStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable for permanent rows.
.1.3.111.2.802.1.1.24.1.2.1.4,IEEE8021-TEIPS-MIB::ieee8021TeipsTesiRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated.
.1.3.111.2.802.1.1.24.1.2.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBMacTable,,not-accessible,,current,,A table that contains database of the active Virtual Station  Interfaces.
.1.3.111.2.802.1.1.24.1.2.2.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBMacEntry,,not-accessible,ieee8021BridgeEvbVSIComponentID:ieee8021BridgeEvbVSIPortNumber:ieee8021BridgeEvbVSIIDType:ieee8021BridgeEvbVSIID:ieee8021BridgeEvbGroupID:ieee8021BridgeEvbVSIMac:ieee8021BridgeEvbVSIVlanId,current,,A list of objects containing database of the MAC/VLANs  associated with Virtual Station Interfaces.
.1.3.111.2.802.1.1.24.1.2.2.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbGroupID,Unsigned32,not-accessible,,current,,Group ID
.1.3.111.2.802.1.1.24.1.2.2.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIMac,OCTET,not-accessible,,current,,The mac-address part of the MAC/VLANs for a VSI.
.1.3.111.2.802.1.1.24.1.2.2.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIVlanId,Unsigned32,read-only,,current,,The Vlan ID part of the MAC/VLANs for a VSI.
.1.3.111.2.802.1.1.24.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbSChannelObjects,,,,,,
.1.3.111.2.802.1.1.24.1.3.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPConfigTable,,not-accessible,,current,,A table that contains configuration parameters for UAP.
.1.3.111.2.802.1.1.24.1.3.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPConfigEntry,,not-accessible,ieee8021BridgePhyPort,current,,A list of objects containing information to configure the  attributes for UAP.
.1.3.111.2.802.1.1.24.1.3.1.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPComponentId,Unsigned32,read-only,,current,,The ComponentID of the port for the UAP.
.1.3.111.2.802.1.1.24.1.3.1.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPPort,Unsigned32,read-only,,current,,The port number of the port for the UAP.
.1.3.111.2.802.1.1.24.1.3.1.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbUapConfigIfIndex,Integer32,read-only,,current,,The value of the instance of the IfIndex object, defined in the IF-MIB, for the interface corresponding to this port, or the value 0 if the port has not been bound to an underlying frame source and sink.
.1.3.111.2.802.1.1.24.1.3.1.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchCdcpAdminEnable,INTEGER,read-create,,current,enable(1):disable(2),Administrative staus of CDCP.
.1.3.111.2.802.1.1.24.1.3.1.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchAdminCDCPRole,INTEGER,read-create,,current,cdcpRoleB(1):cdcpRoleS(2),The administratively configured value for the local 
.1.3.111.2.802.1.1.24.1.3.1.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchAdminCDCPChanCap,Integer32,read-create,,current,,The administratively configured value for the  Number of Channels supported parameter. This  value is included as the ChanCap parameter in  the S-channel TLV.
.1.3.111.2.802.1.1.24.1.3.1.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchOperCDCPChanCap,Integer32,read-only,,current,,The operational value for the Number of Channels  supported parameter. This value is included  as the ChnCap parameter in the S-channel TLV.
.1.3.111.2.802.1.1.24.1.3.1.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchAdminCDCPSVIDPoolLow,Unsigned32,read-create,,current,,Determines the lowest S-VIDs available for  assignment by CDCP.
.1.3.111.2.802.1.1.24.1.3.1.1.9,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchAdminCDCPSVIDPoolHigh,Unsigned32,read-create,,current,,Determines the highest S-VIDs available for assignment by CDCP.
.1.3.111.2.802.1.1.24.1.3.1.1.10,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPSchOperState,INTEGER,read-only,,current,running(1):notRunning(2),The current runnning state of CDCP.
.1.3.111.2.802.1.1.24.1.3.1.1.11,IEEE8021-EVB-MIB::ieee8021BridgeEvbSchCdcpRemoteEnabled,INTEGER,read-only,,current,enable(1):disable(2),CDCP state for the remote S-channel.
.1.3.111.2.802.1.1.24.1.3.1.1.12,IEEE8021-EVB-MIB::ieee8021BridgeEvbSchCdcpRemoteRole,INTEGER,read-only,,current,cdcpRoleB(1):cdcpRoleS(2),The value for the remote port's role parameter.
.1.3.111.2.802.1.1.24.1.3.1.1.13,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),The storage type for this row. Rows in this table that were created through an external process may have a storage type of readOnly or permanent. For a storage type of permanent, none of the columns have to be writable.
.1.3.111.2.802.1.1.24.1.3.1.1.14,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPConfigRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),RowStatus for creating a UAP table entry.
.1.3.111.2.802.1.1.24.1.3.1.2,IEEE8021-TEIPS-MIB::ieee8021TeipsCandidatePsMA,Unsigned32,read-create,,current,,This column holds the candidate Protection Segment MA corresponding to a candidate Protection Segment associated with an IPG.
.1.3.111.2.802.1.1.24.1.3.1.3,IEEE8021-TEIPS-MIB::ieee8021TeipsCandidatePsPort,Unsigned32,read-only,,current,,This column holds the Port Number corresponding to the candidate Protection Segment associated with an IPG.
.1.3.111.2.802.1.1.24.1.3.1.4,IEEE8021-TEIPS-MIB::ieee8021TeipsCandidatePsOper,INTEGER,read-only,,current,true(1):false(2),This column indicates whether or not the candidate Protection Segment is operational.
.1.3.111.2.802.1.1.24.1.3.1.5,IEEE8021-TEIPS-MIB::ieee8021TeipsCandidatePsStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable for permanent rows.
.1.3.111.2.802.1.1.24.1.3.1.6,IEEE8021-TEIPS-MIB::ieee8021TeipsCandidatePsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated.
.1.3.111.2.802.1.1.24.1.3.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPConfigTable,,not-accessible,,current,,A table that contains configuration information for 
.1.3.111.2.802.1.1.24.1.3.2.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPConfigEntry,,not-accessible,ieee8021BridgePhyPort:ieee8021BridgeEvbSchID,current,,A list of objects containing information for the S-Channel  Access Ports (CAP)
.1.3.111.2.802.1.1.24.1.3.2.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbSchID,Unsigned32,not-accessible,,current,,This object represents the SVID for a ieee8021BridgeEvbSysType  of evbBridge and a SCID(S-Channel ID) for a  ieee8021BridgeEvbSysType of evbStation.
.1.3.111.2.802.1.1.24.1.3.2.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPComponentId,Unsigned32,read-only,,current,,Component ID for S-channel Access Port.
.1.3.111.2.802.1.1.24.1.3.2.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbCapConfigIfIndex,Integer32,read-only,,current,,The value of the instance of the IfIndex object, defined in the IF-MIB, for the interface corresponding to this port, or the value 0 if the port has not been bound to an underlying frame source and sink. The underlying IfEntry indexed by this column MUST be persistent across reinitializations of the management system.
.1.3.111.2.802.1.1.24.1.3.2.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPPort,Unsigned32,read-only,,current,,Port number for the S-Channel Access Port.
.1.3.111.2.802.1.1.24.1.3.2.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPSChannelID,Unsigned32,read-only,,current,,S-Channel ID (SCID) for this CAP.
.1.3.111.2.802.1.1.24.1.3.2.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPAssociateSBPOrURPCompID,Unsigned32,read-write,,current,,Component ID of the Server Edge Port to be  associated with the CAP.
.1.3.111.2.802.1.1.24.1.3.2.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPAssociateSBPOrURPPort,Unsigned32,read-write,,current,,Port number of the Server Edge Port to be 
.1.3.111.2.802.1.1.24.1.3.2.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),RowStatus to create/destroy this table.
.1.3.111.2.802.1.1.24.1.3.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPTable,,not-accessible,,current,,A table that contains configuration information for 
.1.3.111.2.802.1.1.24.1.3.3.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPEntry,,not-accessible,ieee8021BridgeEvbURPComponentId:ieee8021BridgeEvbURPPort,current,,A list of objects containing information for the Uplink  Relay Ports(URP).
.1.3.111.2.802.1.1.24.1.3.3.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPComponentId,Unsigned32,not-accessible,,current,,Component ID that the URP belongs to.
.1.3.111.2.802.1.1.24.1.3.3.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPPort,Unsigned32,not-accessible,,current,,port number of the urp.
.1.3.111.2.802.1.1.24.1.3.3.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPIfIndex,Integer32,read-write,,current,,The value of the instance of the IfIndex object, defined in the IF-MIB, for the interface corresponding to this port, or the value 0 if the port has not been bound to an underlying frame source and sink. It is an implementation specific decision as to whether this object may be modified if it has been created or if 0 is a legal value. The underlying IfEntry indexed by this column MUST be  persistent across reinitializations of the management system. 
.1.3.111.2.802.1.1.24.1.3.3.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPBindToISSPort,Unsigned32,read-write,,current,,The evbURPBindToISSPort is the ISS Port Number where  the URP is attached.  This binding is optional and only required in some  systems.
.1.3.111.2.802.1.1.24.1.3.3.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPLldpManual,INTEGER,read-write,,current,true(1):false(2),The evbUrpLldpManual parameter control how the EVB TLV determines the operating values for parameters. When set TRUE only the local EVB TLV will be used to  determine the parameters.
.1.3.111.2.802.1.1.24.1.3.3.1.9,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPVdpOperRsrcWaitDelay,Unsigned32,read-only,,deprecated,,The parameter evbURPVdpOperRsrcWaitDelay is the  exponent of 2 used to set the VDP resourceWaitDelay timer at the EVB Bridge.
.1.3.111.2.802.1.1.24.1.3.3.1.10,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPVdpOperRespWaitDelay,Unsigned32,read-write,,current,,The evbUrpVdpOperRespWaitDelay is how long a  EVb station VDP will wait for a response from  the EVB Bridge VDP.
.1.3.111.2.802.1.1.24.1.3.3.1.11,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPVdpOperReinitKeepAlive,Unsigned32,read-write,,deprecated,,The evbURPVdpOperReinitKeepAlive is the exponent  of 2 used to determine the time interval of Keep  Alives transmitted by the EVB station.
.1.3.111.2.802.1.1.24.1.3.3.1.12,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPVdpOperRsrcWaitDelayExp,Unsigned32,read-only,,current,,The parameter evbURPVdpOperRsrcWaitDelay is the  exponent of 2 used to set the VDP resourceWaitDelay timer at the EVB Bridge.
.1.3.111.2.802.1.1.24.1.3.3.1.13,IEEE8021-EVB-MIB::ieee8021BridgeEvbURPVdpOperReinitKeepAliveExp,Unsigned32,read-write,,current,,The evbURPVdpOperReinitKeepAlive is the exponent  of 2 used to determine the time interval of Keep  Alives transmitted by the EVB station.
.1.3.111.2.802.1.1.24.1.3.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpTable,,not-accessible,,current,,A table that contains configuration information for  the Edge Control Protocol (ECP).
.1.3.111.2.802.1.1.24.1.3.4.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpEntry,,not-accessible,ieee8021BridgeEvbEcpComponentId:ieee8021BridgeEvbEcpPort,current,,A list of objects containing information for theEdge Control Protocol (ECP).
.1.3.111.2.802.1.1.24.1.3.4.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpComponentId,Unsigned32,not-accessible,,current,,Component ID .
.1.3.111.2.802.1.1.24.1.3.4.1.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpPort,Unsigned32,not-accessible,,current,,Port number.
.1.3.111.2.802.1.1.24.1.3.4.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpOperAckTimerInit,Unsigned32,read-only,,deprecated,,The initial value used to initialize ackTimer  (43.3.6.1).
.1.3.111.2.802.1.1.24.1.3.4.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpOperMaxRetries,Unsigned32,read-only,,current,,This integer variable defines the maximum number of times that the ECP transmit state machine will retry a transmission if no ACK is received.
.1.3.111.2.802.1.1.24.1.3.4.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpTxFrameCount,Counter32,read-only,,current,,The evbECPTxFrameCount is the number of ECP frame transmitted since ECP was instanciated.
.1.3.111.2.802.1.1.24.1.3.4.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpTxRetryCount,Counter32,read-only,,current,,The evbECPTxRetryCount is the number of times  ECP re-tried transmission since ECP was  instanciated.
.1.3.111.2.802.1.1.24.1.3.4.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpTxFailures,Counter32,read-only,,current,,The evbECPTxFailures is the number of times ECP  failed to successfully deliver a frame since ECP was instanciated.
.1.3.111.2.802.1.1.24.1.3.4.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpRxFrameCount,Counter32,read-only,,current,,The evbECPRxFrameCount is the number of frames received since ECP was instanciated.
.1.3.111.2.802.1.1.24.1.3.4.1.9,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpOperAckTimerInitExp,Unsigned32,read-only,,current,,The initial value used to initialize ackTimer.  Expressed as exp where 10*2exp microseconds is the duration of the ack timer(43.3.6.1).
.1.3.111.2.802.1.1.24.1.4,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigTable,,not-accessible,,current,,The PBB-TE IPS IPG config table contains configuration and status information for each IPG configured in the system. Entries in this table are created implicitly by the creation of entries in the ieee8021TeipsIpgTable.
.1.3.111.2.802.1.1.24.1.4.1,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021TeipsIpgid,current,,The IPG confguration table entry. Rows are created in this table implicitly when a row is added to the ieee8021TeipsIpgTable.
.1.3.111.2.802.1.1.24.1.4.1.1,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigState,INTEGER,read-only,,current,workingSegment(1):protectionSegment(2):waitToRestore(3):protAdmin(4),This column indicates the current state of the protection switching state machine for an IPG.  The value can be one of the following: workingSegment(1) The protection switching state machine is in the WORKING_PATH state. protectionSegment(2) The protection switching state machine is in the PROTECTION_PATH state. waitToRestore(3) The protection switching state machine is in the WTR state. protAdmin(4) The protection switching state machine is in the PROT_ADMIN state.
.1.3.111.2.802.1.1.24.1.4.1.2,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigCommandStatus,INTEGER,read-only,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column indicates the status of administrative commands within the protection group. It reflects the current operational administrative command being acted upon by the IPG.
.1.3.111.2.802.1.1.24.1.4.1.3,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigCommandLast,INTEGER,read-only,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column indicates the last attempted administrative command applied to the IPG. It is changed whenever a write is made to the CommandAdmin column of this table and is essentially record of the last attempted administrative operation.
.1.3.111.2.802.1.1.24.1.4.1.4,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigCommandAdmin,INTEGER,read-create,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column is used by the operator to request that the IPG state machine perform some administrative operation. The operator requests a command by writing the command value to this column. The state machine indicates the command that it is performing by setting the value of the CommandStatus column of this table. This column always reads back as clear(1).
.1.3.111.2.802.1.1.24.1.4.1.5,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigActiveRequests,INTEGER,read-only,,current,noRequest(1):loP(2):fs(3):pSFH(4):wSFH(5):manualSwitchToProtection(6):manualSwitchToWorking(7),This column shows the status of active requests associated with the IPG.
.1.3.111.2.802.1.1.24.1.4.1.6,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigWTR,Unsigned32,read-create,,current,,This column is used to configure the wait-to-restore timer for the IPG operation. The timer may be configured in steps of 1 minute between 5 and 12 minutes, the default being 5. Additionally, the value 0 is used to indicate that the IPG is to operate non-revertively. The value 0 is not permitted if the IPG is configured for M:1 IPS operation.
.1.3.111.2.802.1.1.24.1.4.1.7,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigHoldOff,Unsigned32,read-create,,current,,This column is used to configure the hold off timer. The purpose is to allow IPS to fix the problem before a higher-layer mechanism, such as PBB-TE TESI protection, is invoked or to allow an inner IPG to fix  the problem before IPS is invoked by the outer IPG when  IPGs are nested. The hold off timer has a period of from 0 to 10 seconds, the default being 0, with a 100ms granularity.
.1.3.111.2.802.1.1.24.1.4.1.8,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgM1ConfigState,INTEGER,read-only,,current,psAssigned(1):segmentOk(2):segmentFailed(3):assignNewPs(4):revertToBetterPs(5),This column indicates the current state of the M:1 protection switching state machine for an IPG if M:1 IPS is supported. The value can be one of the following: psAssigned(1) The protection switching state machine is in the PS_ASSIGNED state. segmentOk(2) The protection switching state machine is in the SEGMENT_OK state. segmentFailed(3) The protection switching state machine is in the SEGMENT_FAILED state. assignNewPs(4) The protection switching state machine is in the ASSIGN_NEW_PS state.  revertToBetterPs(5) The protection switching state machine is in the REVERT_T0_BETTER_PS state.
.1.3.111.2.802.1.1.24.1.4.1.9,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigMWTR,Unsigned32,read-create,,current,,This column is used to configure the M:1 wait-to-restore timer for the IPG operation if M:1 protection is supported. The timer may be configured in steps of 1 minute between 5 and 12 minutes, the default being 5. Additionally, the value 0 is used to indicate that the IPG is to operate non-revertively.
.1.3.111.2.802.1.1.24.1.4.1.10,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigNotifyEnable,INTEGER,read-create,,current,true(1):false(2),This column is used to enable or disable transmission of ieee8021TeipsIpgAdminFailure notifications. These notifications are generated whenever an administrative command cannot be performed by the IPG.
.1.3.111.2.802.1.1.24.1.4.1.11,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. For permanent objects the ieee8021TeipsIpgConfigCommandAdmin column must be writable.
.1.3.111.2.802.1.1.24.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbConformance,,,,,,
.1.3.111.2.802.1.1.24.2.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbGroups,,,,,,
.1.3.111.2.802.1.1.24.2.1.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysGroup,,,,,,The collection of objects used to represent a EVB  management objects.
.1.3.111.2.802.1.1.24.2.1.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpGroup,,,,,,The collection of objects used to represent a SBP  management objects.
.1.3.111.2.802.1.1.24.2.1.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBGroup,,,,,,The collection of objects used to represent a EVB VSI DB table.
.1.3.111.2.802.1.1.24.2.1.5,IEEE8021-EVB-MIB::ieee8021BridgeEvbUAPGroup,,,,,,The collection of objects used to represent a EVB UAP  table.
.1.3.111.2.802.1.1.24.2.1.6,IEEE8021-EVB-MIB::ieee8021BridgeEvbCAPConfigGroup,,,,,,The collection of objects used to represent a EVB  CAP management objects.
.1.3.111.2.802.1.1.24.2.1.7,IEEE8021-EVB-MIB::ieee8021BridgeEvbsURPGroup,,,,,,The collection of objects used to represent a EVBS URP  management objects.
.1.3.111.2.802.1.1.24.2.1.8,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpGroup,,,,,,The collection of objects used to represent a EVB CAP  management objects.
.1.3.111.2.802.1.1.24.2.1.9,IEEE8021-EVB-MIB::ieee8021BridgeEvbSysV2Group,,,,,,The collection of objects used to represent a EVB  management objects.
.1.3.111.2.802.1.1.24.2.1.10,IEEE8021-EVB-MIB::ieee8021BridgeEvbSbpV2Group,,,,,,The collection of objects used to represent a SBP  management objects.
.1.3.111.2.802.1.1.24.2.1.11,IEEE8021-EVB-MIB::ieee8021BridgeEvbVSIDBV2Group,,,,,,The collection of objects used to represent a EVB VSI DB table.
.1.3.111.2.802.1.1.24.2.1.12,IEEE8021-EVB-MIB::ieee8021BridgeEvbsURPV2Group,,,,,,The collection of objects used to represent a EVBS URP  management objects.
.1.3.111.2.802.1.1.24.2.1.13,IEEE8021-EVB-MIB::ieee8021BridgeEvbEcpV2Group,,,,,,The collection of objects used to represent a EVB CAP  management objects.
.1.3.111.2.802.1.1.24.2.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbCompliances,,,,,,
.1.3.111.2.802.1.1.24.2.2.1,IEEE8021-EVB-MIB::ieee8021BridgeEvbbCompliance,,,,,,The compliance statement for devices supporting EVB as defined in IEEE 802.1Q.
.1.3.111.2.802.1.1.24.2.2.2,IEEE8021-EVB-MIB::ieee8021BridgeEvbsCompliance,,,,,,The compliance statement for devices supporting EVBS as defined in IEEE 802.1Q.
.1.3.111.2.802.1.1.24.2.2.3,IEEE8021-EVB-MIB::ieee8021BridgeEvbbComplianceV2,,,,,,The compliance statement for devices supporting EVB as defined in IEEE 802.1Q.
.1.3.111.2.802.1.1.24.2.2.4,IEEE8021-EVB-MIB::ieee8021BridgeEvbsComplianceV2,,,,,,The compliance statement for devices supporting EVBS as defined in IEEE 802.1Q.
.1.3.111.2.802.1.1.24.2.2.5,IEEE8021-TEIPS-MIB::ieee8021TeipsIpgConfigOptGroup,,,,,,Optional 0bjects for the TeipsConfiguration group.
.1.3.111.2.802.1.1.24.2.2.6,IEEE8021-TEIPS-MIB::ieee8021TeipsNotificationsGroup,,,,,,Objects for the notifications group.
.1.3.111.2.802.1.1.25,IEEE8021-PE-MIB::ieee8021BridgePEMib,,,,,,The PE MIB module for managing devices that support Bridge Port Extension. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1BR-2012. Copyright (C) IEEE. This version of this MIB module is part of  IEEE 802.1BR-2012; see the specification itself for full legal notices.
.1.3.111.2.802.1.1.25.1,IEEE8021-PE-MIB::ieee8021BridgePENotifications,,,,,,
.1.3.111.2.802.1.1.25.2,IEEE8021-PE-MIB::ieee8021BridgePEObjects,,,,,,
.1.3.111.2.802.1.1.25.2.1,IEEE8021-PE-MIB::ieee8021BridgePEPortTable,,not-accessible,,current,,A table that contains per port information related to Port Extension. A row is created in this table for any port on a Controlling Bridge that is extended using Port Extension, including those ports that provide communication to the Port Extenders themselves.
.1.3.111.2.802.1.1.25.2.1.1,IEEE8021-PE-MIB::ieee8021BridgePEPortEntry,,not-accessible,ieee8021BridgePEPortComponentId:ieee8021BridgePEPort:ieee8021BridgePEPortType,current,,A list of per port Port Extension objects.
.1.3.111.2.802.1.1.25.2.1.1.1,IEEE8021-PE-MIB::ieee8021BridgePEPortComponentId,Unsigned32,not-accessible,,current,,The component identifier is used to distinguish between the multiple virtual bridge instances within a PBB. In simple situations where there is only a single component the default value is 1.
.1.3.111.2.802.1.1.25.2.1.1.2,IEEE8021-PE-MIB::ieee8021BridgePEPort,Unsigned32,not-accessible,,current,,The port number of the port for which this entry contains bridge management information.
.1.3.111.2.802.1.1.25.2.1.1.3,IEEE8021-PE-MIB::ieee8021BridgePEPortType,INTEGER,not-accessible,,current,pepCascade(1):pepUpstream(2):pepExtended(3),The operational mode of a port participating in Port Exension. The enumerated values are: pepCascade - the port is operating as a Cascade port pepUpstream - the port is operating as an Upstream port pepExtended - the port is operating as an Extended port
.1.3.111.2.802.1.1.25.2.1.1.4,IEEE8021-PE-MIB::ieee8021BridgePEPortUpstreamCSPAddress,OCTET,read-only,,current,,The MAC address used for communication of the PE CSP protocol of the device connected to the upstream port of the Port Extender (which may be the Controlling  Bridge or an upstream Port Extender). This provides the hierarchal relationship in a cascade of Port Extenders
.1.3.111.2.802.1.1.25.2.1.1.5,IEEE8021-PE-MIB::ieee8021BridgePEPortEcid,Unsigned32,read-only,,current,,The default ECID assigend to this port and the port on the Port Extender to which this port corresponds.
.1.3.111.2.802.1.1.25.2.1.1.6,IEEE8021-PE-MIB::ieee8021BridgePEPortNumber,Unsigned32,read-only,,current,,The Port number on the of the Port on the Port Extender, or zero for the Upstream Port.
.1.3.111.2.802.1.1.25.2.1.1.7,IEEE8021-PE-MIB::ieee8021BridgePECounterDiscontinuityTime,TimeTicks,read-only,,current,,The value of sysUpTime on the most recent occasion at which any one or more of the counters in this conceptaul row suffered a discontinuity. The relevant counters are the specific instances associated with this conceptual row of  any Counter32 or Counter64 object. If no such discontinuities have occurred since the last re-initialization of the local  management subsystem, then this object contains a zero value.
.1.3.111.2.802.1.1.25.2.1.1.8,IEEE8021-PE-MIB::ieee8021BridgePEPortRxrqErrorsBridge,Counter64,read-only,,current,,The number of PE CSP flow control overflow errors that have occured for requests on the Bridge.
.1.3.111.2.802.1.1.25.2.1.1.9,IEEE8021-PE-MIB::ieee8021BridgePEPortRxrspErrorsBridge,Counter64,read-only,,current,,The number of PE CSP flow control overflow errors that have occured for responses on the Bridge.
.1.3.111.2.802.1.1.25.2.1.1.10,IEEE8021-PE-MIB::ieee8021BridgePEPortRxrqErrorsPE,Counter64,read-only,,current,,The number of PE CSP flow control overflow errors that have occured for requests on the Port Extender.
.1.3.111.2.802.1.1.25.2.1.1.11,IEEE8021-PE-MIB::ieee8021BridgePEPortRxrspErrorsPE,Counter64,read-only,,current,,The number of PE CSP flow control overflow errors that have occured for responses on the Port Extender.
.1.3.111.2.802.1.1.25.2.1.1.12,IEEE8021-PE-MIB::ieee8021BridgePEPCP,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Port Exender supports modification of the priority code point table (true) or not (false).
.1.3.111.2.802.1.1.25.2.1.1.13,IEEE8021-PE-MIB::ieee8021BridgePEROW,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Port Extender supports rows in the PCP table in addition to the 8P0D row (true)or not (false).
.1.3.111.2.802.1.1.25.2.1.1.14,IEEE8021-PE-MIB::ieee8021BridgePEDEI,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Port Extender supports encoding of the Drop Eligible Indicatior (true) or not (false).
.1.3.111.2.802.1.1.25.2.1.1.15,IEEE8021-PE-MIB::ieee8021BridgePECN,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Port Extender supports Congestion Notification (true) or not (false).
.1.3.111.2.802.1.1.25.2.1.1.16,IEEE8021-PE-MIB::ieee8021BridgePEPFC,INTEGER,read-only,,current,true(1):false(2),Indicates whether the Port Extender supports Priority-based flow control(true) or not (false).
.1.3.111.2.802.1.1.25.2.1.1.17,IEEE8021-PE-MIB::ieee8021BridgePEExtPortEChannelsSupported,Unsigned32,read-only,,current,,Indicates the number of Extended Port E-channels supported by the Port Extender.
.1.3.111.2.802.1.1.25.2.1.1.18,IEEE8021-PE-MIB::ieee8021BridgePERemoteRepEChannelsSupported,Unsigned32,read-only,,current,,Indicates the number of Remote Replication E-channels supported by the Port Extender.
.1.3.111.2.802.1.1.25.2.1.1.19,IEEE8021-PE-MIB::ieee8021BridgePETCsSupported,Unsigned32,read-only,,current,,Indicates the number of traffic clasees supported by the Port Extender.
.1.3.111.2.802.1.1.25.2.1.1.20,IEEE8021-PE-MIB::ieee8021BridgePEUtVLANsSupported,Unsigned32,read-only,,current,,Indicates the number of untagged VLANs supported by the Port Extender.
.1.3.111.2.802.1.1.25.2.2,IEEE8021-PE-MIB::ieee8021BridgePERemoteReplicationTable,,not-accessible,,current,,A table that contains one row for each Remote Replication entry in the filtering database.
.1.3.111.2.802.1.1.25.2.2.1,IEEE8021-PE-MIB::ieee8021BridgePERemoteReplicationEntry,,not-accessible,ieee8021BridgePEPortComponentId:ieee8021BridgePERREcid,current,,A list of Remote Replication objects.
.1.3.111.2.802.1.1.25.2.2.1.1,IEEE8021-PE-MIB::ieee8021BridgePERREcid,Unsigned32,not-accessible,,current,,The ECID assigend to this Remote Replication filtering entry.
.1.3.111.2.802.1.1.25.2.2.1.2,IEEE8021-PE-MIB::ieee8021BridgePERRPortMap,OCTET,read-only,,current,,The list of ports to which a frame is to be replicated.
.1.3.111.2.802.1.1.25.2.3,IEEE8021-PE-MIB::ieee8021BridgePEETSTable,,not-accessible,,current,,A table that contains per port information related to Enhanced Transmission Selection. A row is created in this table for any port on a Controlling Bridge that corresponds to a Cascade Port. These objects refer to the ETS configuration  of the attached Upstream Port
.1.3.111.2.802.1.1.25.2.3.1,IEEE8021-PE-MIB::ieee8021BridgePEETSEntry,,not-accessible,ieee8021BridgePEPortComponentId:ieee8021BridgePEPort:ieee8021BridgePEETSTrafficClass,current,,A list of per Cascade Port ETS objects.
.1.3.111.2.802.1.1.25.2.3.1.1,IEEE8021-PE-MIB::ieee8021BridgePEETSTrafficClass,Unsigned32,not-accessible,,current,,Indicates the traffic class to which this bandwidth applies
.1.3.111.2.802.1.1.25.2.3.1.2,IEEE8021-PE-MIB::ieee8021BridgePEETSTrafficSelectionAlgorthm,INTEGER,read-write,,current,tsaStrictPriority(0):tsaCreditBasedShaper(1):tsaEnhancedTransmission(2):tsaVendorSpecific(255),Inticates the Traffic Selection Algorthm  assigned to this traffic class
.1.3.111.2.802.1.1.25.2.3.1.3,IEEE8021-PE-MIB::ieee8021BridgePEETSBandwidth,Unsigned32,read-write,,current,,Indicates the bandwidth assigned to this traffic class.
.1.3.111.2.802.1.1.25.3,IEEE8021-PE-MIB::ieee8021BridgePEConformance,,,,,,
.1.3.111.2.802.1.1.25.3.1,IEEE8021-PE-MIB::ieee8021BridgePEGroups,,,,,,
.1.3.111.2.802.1.1.25.3.1.1,IEEE8021-PE-MIB::ieee8021BridgePEGroup,,,,,,The collection of objects used to represent Port Extension management objects.
.1.3.111.2.802.1.1.25.3.2,IEEE8021-PE-MIB::ieee8021BridgePECompliances,,,,,,
.1.3.111.2.802.1.1.25.3.2.1,IEEE8021-PE-MIB::ieee8021BridgePECompliance,,,,,,The compliance statement for devices supporting PE as defined in IEEE 802.1BR.
.1.3.111.2.802.1.1.26,IEEE8021-SPB-MIB::ieee8021SpbMib,,,,,,802.1 SPB MIB
.1.3.111.2.802.1.1.26.1,IEEE8021-SPB-MIB::ieee8021SpbObjects,,,,,,
.1.3.111.2.802.1.1.26.1.1,IEEE8021-SPB-MIB::ieee8021SpbSys,,,,,,
.1.3.111.2.802.1.1.26.1.1.1,IEEE8021-SPB-MIB::ieee8021SpbSysAreaAddress,OCTET,read-write,,current,,The three byte IS-IS Area Address to join. Normally
.1.3.111.2.802.1.1.26.1.1.2,IEEE8021-SPB-MIB::ieee8021SpbSysId,OCTET,read-write,,current,,SYS ID used for all SPB instances on this bridge.
.1.3.111.2.802.1.1.26.1.1.3,IEEE8021-SPB-MIB::ieee8021SpbSysControlAddr,OCTET,read-write,,current,,Group MAC that the ISIS control plane will use. SPB can
.1.3.111.2.802.1.1.26.1.1.4,IEEE8021-SPB-MIB::ieee8021SpbSysName,OCTET,read-only,,current,,Name to be used to refer to this SPB bridge. This is advertised 
.1.3.111.2.802.1.1.26.1.1.5,IEEE8021-SPB-MIB::ieee8021SpbSysBridgePriority,OCTET,read-only,,current,,This is a 16 bit quantity which ranks this SPB Bridge
.1.3.111.2.802.1.1.26.1.1.6,IEEE8021-SPB-MIB::ieee8021SpbmSysSPSourceId,OCTET,read-write,,current,,The Shortest Path Source Identifier.
.1.3.111.2.802.1.1.26.1.1.7,IEEE8021-SPB-MIB::ieee8021SpbvSysMode,INTEGER,read-write,,current,auto(1):manual(2),Indication of supporting SPBV mode
.1.3.111.2.802.1.1.26.1.1.8,IEEE8021-SPB-MIB::ieee8021SpbmSysMode,INTEGER,read-write,,current,auto(1):manual(2),Indication of supporting SPBM mode
.1.3.111.2.802.1.1.26.1.1.9,IEEE8021-SPB-MIB::ieee8021SpbSysDigestConvention,INTEGER,read-write,,current,off(1):loopFreeBoth(2):loopFreeMcastOnly(3),The Agreement Digest convention setting 
.1.3.111.2.802.1.1.26.1.2,IEEE8021-SPB-MIB::ieee8021SpbMtidStaticTable,,not-accessible,,current,,A Table of multiple logical topologies - MT.
.1.3.111.2.802.1.1.26.1.2.1,IEEE8021-SPB-MIB::ieee8021SpbMtidStaticTableEntry,,not-accessible,ieee8021SpbMtidStaticEntryMtid:ieee8021SpbTopIx,current,,This table configures a MTID to a topology index. A 
.1.3.111.2.802.1.1.26.1.2.1.1,IEEE8021-SPB-MIB::ieee8021SpbMtidStaticEntryMtid,Unsigned32,not-accessible,,current,,ISIS Multi Topology Identifier MTID
.1.3.111.2.802.1.1.26.1.2.1.2,IEEE8021-SPB-MIB::ieee8021SpbMTidStaticEntryMtidOverload,INTEGER,read-create,,current,true(1):false(2),When set for this logical topology this bridge can only
.1.3.111.2.802.1.1.26.1.2.1.3,IEEE8021-SPB-MIB::ieee8021SpbMtidStaticEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object indicates the status of an entry, and is used
.1.3.111.2.802.1.1.26.1.2.1.4,IEEE8021-SPB-MIB::ieee8021SpbTopIx,Unsigned32,not-accessible,,current,,Unique identifier of this SPB topology
.1.3.111.2.802.1.1.26.1.3,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicTable,,not-accessible,,current,,This table is for SPB dynamic information. The dynamic 
.1.3.111.2.802.1.1.26.1.3.1,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicTableEntry,,not-accessible,ieee8021SpbTopIxDynamicEntryTopIx,current,,This table displays the digest information computed for this bridge. 
.1.3.111.2.802.1.1.26.1.3.1.1,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicEntryTopIx,Unsigned32,not-accessible,,current,,ISIS-SPB Topology Index identifier
.1.3.111.2.802.1.1.26.1.3.1.2,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicEntryAgreeDigest,OCTET,read-only,,current,,The topology agreement digest value. Digest of all
.1.3.111.2.802.1.1.26.1.3.1.3,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicEntryMCID,OCTET,read-only,,current,,The MST Identifier MCID. The MCID is a digest of the 
.1.3.111.2.802.1.1.26.1.3.1.4,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicEntryAuxMCID,OCTET,read-only,,current,,The aux MST Identifier for migration.
.1.3.111.2.802.1.1.26.1.4,IEEE8021-SPB-MIB::ieee8021SpbEctStaticTable,,not-accessible,,current,,The Equal Cost Tree (ECT) static configuration table.
.1.3.111.2.802.1.1.26.1.4.1,IEEE8021-SPB-MIB::ieee8021SpbEctStaticTableEntry,,not-accessible,ieee8021SpbEctStaticEntryTopIx:ieee8021SpbEctStaticEntryBaseVid,current,,The Equal Cost Tree static configuration Table defines the
.1.3.111.2.802.1.1.26.1.4.1.1,IEEE8021-SPB-MIB::ieee8021SpbEctStaticEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.4.1.2,IEEE8021-SPB-MIB::ieee8021SpbEctStaticEntryBaseVid,Integer32,not-accessible,,current,,Base VID to use for this ECT-ALGORITHM.
.1.3.111.2.802.1.1.26.1.4.1.3,IEEE8021-SPB-MIB::ieee8021SpbEctStaticEntryEctAlgorithm,OCTET,read-create,,current,,This identifies the method and the algorithm used
.1.3.111.2.802.1.1.26.1.4.1.4,IEEE8021-SPB-MIB::ieee8021SpbvEctStaticEntrySpvid,Integer32,read-create,,current,,If SPBV mode this is the VID originating from this bridge.
.1.3.111.2.802.1.1.26.1.4.1.5,IEEE8021-SPB-MIB::ieee8021SpbEctStaticEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object indicates the status of an entry, and is used
.1.3.111.2.802.1.1.26.1.5,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicTable,,not-accessible,,current,,A table containing Data about the ECT behavior on this bridge
.1.3.111.2.802.1.1.26.1.5.1,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicTableEntry,,not-accessible,ieee8021SpbEctDynamicEntryTopIx:ieee8021SpbEctDynamicEntryBaseVid,current,,This table can be used to check that neighbor bridges are 
.1.3.111.2.802.1.1.26.1.5.1.1,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.5.1.2,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicEntryBaseVid,Integer32,not-accessible,,current,,The Base VID being queried. Base VID 
.1.3.111.2.802.1.1.26.1.5.1.3,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicEntryMode,INTEGER,read-only,,current,disabled(1):spbm(2):spbv(3),The Operating mode of this Base VID. 
.1.3.111.2.802.1.1.26.1.5.1.4,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicEntryLocalUse,INTEGER,read-only,,current,true(1):false(2),This value indicates the ECT is in use locally 
.1.3.111.2.802.1.1.26.1.5.1.5,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicEntryRemoteUse,INTEGER,read-only,,current,true(1):false(2),This value indicates the remote ECT is in use 
.1.3.111.2.802.1.1.26.1.5.1.6,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicEntryIngressCheckDiscards,Unsigned32,read-only,,current,,The number of ingress check failures on this ECT VID.
.1.3.111.2.802.1.1.26.1.6,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticTable,,not-accessible,,current,,A table containing the SPB configuration data for a neighbor
.1.3.111.2.802.1.1.26.1.6.1,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticTableEntry,,not-accessible,ieee8021SpbAdjStaticEntryTopIx:ieee8021SpbAdjStaticEntryIfIndex,current,,This table can be used to display the interfaces and metrics 
.1.3.111.2.802.1.1.26.1.6.1.1,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.6.1.2,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticEntryIfIndex,Integer32,not-accessible,,current,,The System interface/index which defines this 
.1.3.111.2.802.1.1.26.1.6.1.3,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticEntryMetric,Integer32,read-create,,current,,The ieee8021Spb metric (incremental cost) to this peer. 
.1.3.111.2.802.1.1.26.1.6.1.4,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticEntryIfAdminState,INTEGER,read-create,,current,up(1):down(2):testing(3),The administrative state of this interface/port.
.1.3.111.2.802.1.1.26.1.6.1.5,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object indicates the status of an entry, and is used
.1.3.111.2.802.1.1.26.1.7,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicTable,,not-accessible,,current,,The SPB neighbor dynamic information table.
.1.3.111.2.802.1.1.26.1.7.1,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicTableEntry,,not-accessible,ieee8021SpbAdjDynamicEntryTopIx:ieee8021SpbAdjDynamicEntryIfIndex:ieee8021SpbAdjDynamicEntryPeerSysId,current,,This table is used to determine operational values of digests
.1.3.111.2.802.1.1.26.1.7.1.1,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.7.1.2,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryIfIndex,Integer32,not-accessible,,current,,System interface/index which defines this adjacency
.1.3.111.2.802.1.1.26.1.7.1.3,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerSysId,OCTET,not-accessible,,current,,The SPB System Identifier of this peer. This is used to 
.1.3.111.2.802.1.1.26.1.7.1.4,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPort,Unsigned32,read-only,,current,,The port number to reach this adjacency.
.1.3.111.2.802.1.1.26.1.7.1.5,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryIfOperState,INTEGER,read-only,,current,up(1):down(2):testing(3),The operational state of this port.
.1.3.111.2.802.1.1.26.1.7.1.6,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerSysName,OCTET,read-only,,current,,IS-IS system name of peer.
.1.3.111.2.802.1.1.26.1.7.1.7,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerAgreeDigest,OCTET,read-only,,current,,The peer topology agreement digest value
.1.3.111.2.802.1.1.26.1.7.1.8,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerMCID,OCTET,read-only,,current,,The peer MST Identifier MCID. The MCID is a digest of the 
.1.3.111.2.802.1.1.26.1.7.1.9,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerAuxMCID,OCTET,read-only,,current,,The peer auxiliary MST Identifier. This MCID is 
.1.3.111.2.802.1.1.26.1.7.1.10,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryLocalCircuitID,Unsigned32,read-only,,current,,The value used by IS-IS to identify this adjacency locally.
.1.3.111.2.802.1.1.26.1.7.1.11,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerLocalCircuitID,Unsigned32,read-only,,current,,The value used by peer IS-IS to identify this adjacency remotely.
.1.3.111.2.802.1.1.26.1.7.1.12,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPortIdentifier,Unsigned32,read-only,,current,,The value for this bridge which has been selected by 
.1.3.111.2.802.1.1.26.1.7.1.13,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryPeerPortIdentifier,Unsigned32,read-only,,current,,The value for peer port Identifier selected by IS-IS 
.1.3.111.2.802.1.1.26.1.7.1.14,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicEntryIsisCircIndex,Unsigned32,read-only,,current,,The isisCircTable reference. This allows cross referencing
.1.3.111.2.802.1.1.26.1.8,IEEE8021-SPB-MIB::ieee8021SpbTopNodeTable,,not-accessible,,current,,Table of network specific bridge information.
.1.3.111.2.802.1.1.26.1.8.1,IEEE8021-SPB-MIB::ieee8021SpbTopNodeTableEntry,,not-accessible,ieee8021SpbTopNodeEntryTopIx:ieee8021SpbTopNodeEntrySysId,current,,This table is used to display system level information about 
.1.3.111.2.802.1.1.26.1.8.1.1,IEEE8021-SPB-MIB::ieee8021SpbTopNodeEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.8.1.2,IEEE8021-SPB-MIB::ieee8021SpbTopNodeEntrySysId,OCTET,not-accessible,,current,,The IS-IS System ID of a bridge in the SPB 
.1.3.111.2.802.1.1.26.1.8.1.3,IEEE8021-SPB-MIB::ieee8021SpbTopNodeEntryBridgePriority,OCTET,read-only,,current,,The Bridge Priority of the bridge in the LSP database. 
.1.3.111.2.802.1.1.26.1.8.1.4,IEEE8021-SPB-MIB::ieee8021SpbmTopNodeEntrySPsourceID,OCTET,read-only,,current,,The Shortest Path Source Identifier.
.1.3.111.2.802.1.1.26.1.8.1.5,IEEE8021-SPB-MIB::ieee8021SpbTopNodeEntrySysName,OCTET,read-only,,current,,The System Name. A Human readable name of this bridge
.1.3.111.2.802.1.1.26.1.9,IEEE8021-SPB-MIB::ieee8021SpbTopEctTable,,not-accessible,,current,,Table of all ECT use in the network
.1.3.111.2.802.1.1.26.1.9.1,IEEE8021-SPB-MIB::ieee8021SpbTopEctTableEntry,,not-accessible,ieee8021SpbTopEctEntryTopIx:ieee8021SpbTopEctEntrySysId:ieee8021SpbTopEctEntryBaseVid,current,,This table lists bridges and the ECT Algorithms configured and in use. 
.1.3.111.2.802.1.1.26.1.9.1.1,IEEE8021-SPB-MIB::ieee8021SpbTopEctEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.9.1.2,IEEE8021-SPB-MIB::ieee8021SpbTopEctEntrySysId,OCTET,not-accessible,,current,,The system ID which is using a particular ECT.
.1.3.111.2.802.1.1.26.1.9.1.3,IEEE8021-SPB-MIB::ieee8021SpbTopEctEntryBaseVid,Integer32,not-accessible,,current,,Base VID related to this algorithm.
.1.3.111.2.802.1.1.26.1.9.1.4,IEEE8021-SPB-MIB::ieee8021SpbTopEctEntryEctAlgorithm,OCTET,read-only,,current,,The ECT-ALGORITHM in use. 
.1.3.111.2.802.1.1.26.1.9.1.5,IEEE8021-SPB-MIB::ieee8021SpbTopEctEntryMode,INTEGER,read-only,,current,disabled(1):spbm(2):spbv(3),Operating mode : SPBM (=2) or SPBV (=3)
.1.3.111.2.802.1.1.26.1.9.1.6,IEEE8021-SPB-MIB::ieee8021SpbvTopEctSysMode,INTEGER,read-only,,current,auto(1):manual(2),Indication of supporting SPBV mode
.1.3.111.2.802.1.1.26.1.9.1.7,IEEE8021-SPB-MIB::ieee8021SpbvTopEctEntrySpvid,Integer32,read-only,,current,,SPVID in V mode
.1.3.111.2.802.1.1.26.1.9.1.8,IEEE8021-SPB-MIB::ieee8021SpbTopEctEntryLocalUse,INTEGER,read-only,,current,true(1):false(2),Is this ECT-ALGORITHM in use locally by advertising 
.1.3.111.2.802.1.1.26.1.10,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeTable,,not-accessible,,current,,A Table of edges in network (not duplicated),
.1.3.111.2.802.1.1.26.1.10.1,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeTableEntry,,not-accessible,ieee8021SpbTopEdgeEntryTopIx:ieee8021SpbTopEdgeEntrySysIdNear:ieee8021SpbTopEdgeEntrySysIdFar,current,,The table lists information about bridge edges (links).
.1.3.111.2.802.1.1.26.1.10.1.1,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.10.1.2,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeEntrySysIdNear,OCTET,not-accessible,,current,,The System ID of near bridge (the bridge 
.1.3.111.2.802.1.1.26.1.10.1.3,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeEntrySysIdFar,OCTET,not-accessible,,current,,The System ID of far bridge (the neighbor 
.1.3.111.2.802.1.1.26.1.10.1.4,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeEntryMetricNear2Far,Integer32,read-only,,current,,The metric used on this edge advertised by near end
.1.3.111.2.802.1.1.26.1.10.1.5,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeEntryMetricFar2Near,Integer32,read-only,,current,,The metric used on this edge advertised by far end
.1.3.111.2.802.1.1.26.1.11,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvTable,,not-accessible,,current,,All SPBM PBB encapsulated services in this network.
.1.3.111.2.802.1.1.26.1.11.1,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvTableEntry,,not-accessible,ieee8021SpbmTopSrvEntryTopIx:ieee8021SpbmTopSrvEntrySysId:ieee8021SpbmTopSrvEntryIsid:ieee8021SpbmTopSrvEntryBaseVid:ieee8021SpbmTopSrvEntryMac,current,,This table displays information about PBB services received
.1.3.111.2.802.1.1.26.1.11.1.1,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvEntryTopIx,Unsigned32,not-accessible,,current,,Entry of one The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.11.1.2,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvEntrySysId,OCTET,not-accessible,,current,,The System identifier this service originates/terminates on.
.1.3.111.2.802.1.1.26.1.11.1.3,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvEntryIsid,Unsigned32,not-accessible,,current,,An ISID (service) originating/terminating on this bridge.
.1.3.111.2.802.1.1.26.1.11.1.4,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvEntryBaseVid,Integer32,not-accessible,,current,,The Base VID associated with this service. The Base VID determines
.1.3.111.2.802.1.1.26.1.11.1.5,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvEntryMac,OCTET,not-accessible,,current,,The MAC address associated with a service.
.1.3.111.2.802.1.1.26.1.11.1.6,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvEntryIsidFlags,BITS,read-only,,current,ingress(0):egress(1),A pair of flags defining the attributes of this
.1.3.111.2.802.1.1.26.1.12,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvTable,,not-accessible,,current,,The SPBV group services in this network
.1.3.111.2.802.1.1.26.1.12.1,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvTableEntry,,not-accessible,ieee8021SpbvTopSrvEntryTopIx:ieee8021SpbvTopSrvEntrySysId:ieee8021SpbvTopSrvEntryMMac,current,,This table displays information about SPBV group address. 
.1.3.111.2.802.1.1.26.1.12.1.1,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvEntryTopIx,Unsigned32,not-accessible,,current,,The ISIS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.1.12.1.2,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvEntrySysId,OCTET,not-accessible,,current,,The System identifier advertising this group address.
.1.3.111.2.802.1.1.26.1.12.1.3,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvEntryMMac,OCTET,not-accessible,,current,,This Group MAC address entry.
.1.3.111.2.802.1.1.26.1.12.1.4,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvEntryBaseVid,Integer32,read-only,,current,,The Base VID associated with this service. The Base VID determines
.1.3.111.2.802.1.1.26.1.12.1.5,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvEntryMMacFlags,BITS,read-only,,current,ingress(0):egress(1),A pair of {ingress, egress} flags for this 
.1.3.111.2.802.1.1.26.1.13,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticTable,,not-accessible,,current,,Table of BSIs configured on this system and assigned to an SPBM VID. The table is indexed by - ieee8021SpbTopIx from ieee8021SpbMtidStaticTable indicating the ISIS-SPB topology instance into which the BSI will be advertised,  - ieee8021BridgeBasePort from ieee8021PbbCbpTable identifying the CPB on which the BSI is configured, - an I-SID value identifying the BSI, and - a VID value identifying a B-VID for which forwarding state is to be installed for the BSI
.1.3.111.2.802.1.1.26.1.13.1,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntry,,not-accessible,ieee8021SpbTopIx:ieee8021BridgeBasePort:ieee8021SpbmBsiStaticEntryIsid:ieee8021SpbmBsiStaticEntryBaseVid,current,,This table contains information about backbone services configured on this system to be advertised by ISIS-SPB.
.1.3.111.2.802.1.1.26.1.13.1.1,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryIsid,Unsigned32,not-accessible,,current,,An I-SID registered on the CBP identified by ieee8021BridgeBasePort.
.1.3.111.2.802.1.1.26.1.13.1.2,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryBaseVid,Integer32,not-accessible,,current,,An B-VID registered on the CBP identified by ieee8021BridgeBasePort.
.1.3.111.2.802.1.1.26.1.13.1.3,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryTBit,INTEGER,read-create,,current,true(1):false(2),If true(1), indicates the BSI transmits multicast frames from this CBP. This object is persistent.
.1.3.111.2.802.1.1.26.1.13.1.4,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryRBit,INTEGER,read-create,,current,true(1):false(2),If true(1), indicates the BSI wishes to receive multicast frames at this CBP. This object is persistent.
.1.3.111.2.802.1.1.26.1.13.1.5,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryTsBit,INTEGER,read-create,,current,true(1):false(2),If true(1), indicates the BSI transmits multicast frames on a shared tree from this CBP. This object is persistent.
.1.3.111.2.802.1.1.26.1.13.1.6,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryTieBreakMask,Integer32,read-create,,current,,The value used to create the Tie-Break Mask for calculating multicast trees. This object is persistent.
.1.3.111.2.802.1.1.26.1.13.1.7,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table can be modified. This object is persistent.
.1.3.111.2.802.1.1.26.1.14,IEEE8021-SPB-MIB::dot1agCfmMepSpbmTable,,not-accessible,,current,,The additional objects configurable in SPBM MEPs
.1.3.111.2.802.1.1.26.1.14.1,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEntry,,not-accessible,,current,,The SPBM MEP table additions.
.1.3.111.2.802.1.1.26.1.14.1.1,IEEE8021-SPB-MIB::dot1agCfmMepTransmitLbmSpbmDA,OCTET,read-create,,current,,The MAC Address to be used as the LBM destination address in an SPBM MA: A unicast or multicast address.
.1.3.111.2.802.1.1.26.1.14.1.2,IEEE8021-SPB-MIB::dot1agCfmMepTransmitLtmSpbmDA,OCTET,read-create,,current,,The MAC Address to be used as the LTM destination address in an SPBM MA: A unicast or multicast address.
.1.3.111.2.802.1.1.26.1.15,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEspTable,,not-accessible,,current,,The SPBM ESP table contains path-tesid information for each SPBM path MA known to a system. This table uses three indices. The first two indices are the indices of the Maintenance Domain and MA tables, the reason being that a path-tesid is always related to an MA and Maintenance Domain.
.1.3.111.2.802.1.1.26.1.15.1,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEspEntry,,not-accessible,dot1agCfmMdIndex:dot1agCfmMaIndex:dot1agCfmMepSpbmEspIndex,current,,The SPBM path MA ESP entry. Each entry refers to an ESP by identifier and contains information about one of the ESPs that comprise an SPBM path MA. The 
.1.3.111.2.802.1.1.26.1.15.1.1,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEspIndex,Unsigned32,not-accessible,,current,,This is an identifier, of local signifigance to a particular SPBM path MA which is used to index the ESPs associated with that MA.
.1.3.111.2.802.1.1.26.1.15.1.2,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEspEsp,OCTET,read-create,,current,,This column holds the ESP identifier for one of the Ethernet Switched Paths that define the SPBM path MA. This object is persistent.
.1.3.111.2.802.1.1.26.1.15.1.3,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEspRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table can be modified. This object is persistent.
.1.3.111.2.802.1.1.26.2,IEEE8021-SPB-MIB::ieee8021SpbConformance,,,,,,
.1.3.111.2.802.1.1.26.2.1,IEEE8021-SPB-MIB::ieee8021SpbGroups,,,,,,
.1.3.111.2.802.1.1.26.2.1.1,IEEE8021-SPB-MIB::ieee8021SpbSysGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbSys
.1.3.111.2.802.1.1.26.2.1.2,IEEE8021-SPB-MIB::ieee8021SpbMtidStaticTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbMtidStaticTable
.1.3.111.2.802.1.1.26.2.1.3,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbTopIxDynamicTable
.1.3.111.2.802.1.1.26.2.1.4,IEEE8021-SPB-MIB::ieee8021SpbEctStaticTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbEctStaticTable
.1.3.111.2.802.1.1.26.2.1.5,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbEctDynamicTable
.1.3.111.2.802.1.1.26.2.1.6,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbAdjStaticTable
.1.3.111.2.802.1.1.26.2.1.7,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbAdjDynamicTable
.1.3.111.2.802.1.1.26.2.1.8,IEEE8021-SPB-MIB::ieee8021SpbTopNodeTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbTopNodeTable
.1.3.111.2.802.1.1.26.2.1.9,IEEE8021-SPB-MIB::ieee8021SpbTopEctTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbTopEctTable
.1.3.111.2.802.1.1.26.2.1.10,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbTopEdgeTable
.1.3.111.2.802.1.1.26.2.1.11,IEEE8021-SPB-MIB::ieee8021SpbmTopSrvTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbmTopSrvTable
.1.3.111.2.802.1.1.26.2.1.12,IEEE8021-SPB-MIB::ieee8021SpbSysGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbSys
.1.3.111.2.802.1.1.26.2.1.13,IEEE8021-SPB-MIB::ieee8021SpbMtidStaticTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbMtidStaticTable
.1.3.111.2.802.1.1.26.2.1.14,IEEE8021-SPB-MIB::ieee8021SpbTopIxDynamicTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbTopIxDynamicTable
.1.3.111.2.802.1.1.26.2.1.15,IEEE8021-SPB-MIB::ieee8021SpbEctStaticTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbEctStaticTable
.1.3.111.2.802.1.1.26.2.1.16,IEEE8021-SPB-MIB::ieee8021SpbEctDynamicTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbEctDynamicTable
.1.3.111.2.802.1.1.26.2.1.17,IEEE8021-SPB-MIB::ieee8021SpbAdjStaticTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbAdjStaticTable
.1.3.111.2.802.1.1.26.2.1.18,IEEE8021-SPB-MIB::ieee8021SpbAdjDynamicTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbAdjDynamicTable
.1.3.111.2.802.1.1.26.2.1.19,IEEE8021-SPB-MIB::ieee8021SpbTopNodeTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbTopNodeTable
.1.3.111.2.802.1.1.26.2.1.20,IEEE8021-SPB-MIB::ieee8021SpbTopEctTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbTopEctTable
.1.3.111.2.802.1.1.26.2.1.21,IEEE8021-SPB-MIB::ieee8021SpbTopEdgeTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbTopEdgeTable
.1.3.111.2.802.1.1.26.2.1.22,IEEE8021-SPB-MIB::ieee8021SpbvTopSrvTableGroupSPBV,,,,,,The collection of objects used to represent ieee8021SpbvTopSrvTable
.1.3.111.2.802.1.1.26.2.1.23,IEEE8021-SPB-MIB::ieee8021SpbmBsiStaticTableGroupSPBM,,,,,,The collection of objects used to represent ieee8021SpbmBsiStaticTable
.1.3.111.2.802.1.1.26.2.1.24,IEEE8021-SPB-MIB::dot1agCfmMepSpbmTableGroupSPBM,,,,,,The collection of objects used to represent dot1agCfmMepSpbmTable
.1.3.111.2.802.1.1.26.2.1.25,IEEE8021-SPB-MIB::dot1agCfmMepSpbmEspTableGroupSPBM,,,,,,The collection of objects used to represent dot1agCfmMepSpbmEspTable
.1.3.111.2.802.1.1.26.2.2,IEEE8021-SPB-MIB::ieee8021SpbCompliances,,,,,,
.1.3.111.2.802.1.1.26.2.2.1,IEEE8021-SPB-MIB::ieee8021SpbComplianceSPBM,,,,,,Compliance to IEEE 802.1 SPBM mode
.1.3.111.2.802.1.1.26.2.2.2,IEEE8021-SPB-MIB::ieee8021SpbComplianceSPBV,,,,,,Compliance to IEEE 802.1 SPBV mode
.1.3.111.2.802.1.1.26.3,IEEE8021-SPB-MIB::ieee8021PcrObjects,,,,,,
.1.3.111.2.802.1.1.26.3.1,IEEE8021-SPB-MIB::ieee8021PcrEctStaticTable,,not-accessible,,current,,The Path Control and Reservation (PCR)
.1.3.111.2.802.1.1.26.3.1.1,IEEE8021-SPB-MIB::ieee8021PcrEctStaticTableEntry,,not-accessible,ieee8021PcrEctStaticEntryTopIx:ieee8021PcrEctStaticEntryBaseVid,current,,The PCR static configuration Table defines the
.1.3.111.2.802.1.1.26.3.1.1.1,IEEE8021-SPB-MIB::ieee8021PcrEctStaticEntryTopIx,Unsigned32,not-accessible,,current,,The IS-IS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.3.1.1.2,IEEE8021-SPB-MIB::ieee8021PcrEctStaticEntryBaseVid,Integer32,not-accessible,,current,,Base VID to use for the MRT ECT-Algorithm or for the
.1.3.111.2.802.1.1.26.3.1.1.3,IEEE8021-SPB-MIB::ieee8021PcrEctStaticEntryMrtBlueVid,Integer32,read-write,,current,,MRT-Blue VID.
.1.3.111.2.802.1.1.26.3.1.1.4,IEEE8021-SPB-MIB::ieee8021PcrEctStaticEntryMrtRedVid,Integer32,read-write,,current,,MRT-Red VID.
.1.3.111.2.802.1.1.26.3.1.1.5,IEEE8021-SPB-MIB::ieee8021PcrEctStaticEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The object indicates the status of an entry and is used
.1.3.111.2.802.1.1.26.3.2,IEEE8021-SPB-MIB::ieee8021PcrTopEctTable,,not-accessible,,current,,Table of MRT use in the network.
.1.3.111.2.802.1.1.26.3.2.1,IEEE8021-SPB-MIB::ieee8021PcrTopEctTableEntry,,not-accessible,ieee8021PcrTopEctEntryTopIx:ieee8021PcrTopEctEntrySysId:ieee8021PcrTopEctEntryBaseVid,current,,This table lists bridges configured to use MRT.
.1.3.111.2.802.1.1.26.3.2.1.1,IEEE8021-SPB-MIB::ieee8021PcrTopEctEntryTopIx,Unsigned32,not-accessible,,current,,The IS-IS Topology Index identifier to which this 
.1.3.111.2.802.1.1.26.3.2.1.2,IEEE8021-SPB-MIB::ieee8021PcrTopEctEntrySysId,OCTET,not-accessible,,current,,The System ID that is using MRT.
.1.3.111.2.802.1.1.26.3.2.1.3,IEEE8021-SPB-MIB::ieee8021PcrTopEctEntryBaseVid,Integer32,not-accessible,,current,,Base VID related to this algorithm.
.1.3.111.2.802.1.1.26.3.2.1.4,IEEE8021-SPB-MIB::ieee8021PcrTopEctEntryMode,INTEGER,read-only,,current,disabled(1):spbm(2):spbv(3),Operating mode : non-learning (=2) or learning (=3)
.1.3.111.2.802.1.1.26.3.2.1.5,IEEE8021-SPB-MIB::ieee8021PcrTopEctEntryMrtBlueVid,Integer32,read-only,,current,,MRT-Blue VID.
.1.3.111.2.802.1.1.26.3.2.1.6,IEEE8021-SPB-MIB::ieee8021PcrTopEctEntryMrtRedVid,Integer32,read-only,,current,,MRT-Red VID.
.1.3.111.2.802.1.1.26.4,IEEE8021-SPB-MIB::ieee8021PcrConformance,,,,,,
.1.3.111.2.802.1.1.26.4.1,IEEE8021-SPB-MIB::ieee8021PcrGroups,,,,,,
.1.3.111.2.802.1.1.26.4.1.1,IEEE8021-SPB-MIB::ieee8021PcrSysGroup,,,,,,The collection of objects used to represent ieee8021SpbSys for PCR.
.1.3.111.2.802.1.1.26.4.1.2,IEEE8021-SPB-MIB::ieee8021PcrMtidStaticTableGroup,,,,,,The collection of objects used to represent ieee8021SpbMtidStaticTable for PCR.
.1.3.111.2.802.1.1.26.4.1.3,IEEE8021-SPB-MIB::ieee8021PcrTopIxDynamicTableGroup,,,,,,The collection of objects used to represent ieee8021SpbTopIxDynamicTable for PCR.
.1.3.111.2.802.1.1.26.4.1.4,IEEE8021-SPB-MIB::ieee8021PcrEctStaticTableGroupMAC,,,,,,The collection of objects used to represent ieee8021SpbEctStaticTable for PCR,
.1.3.111.2.802.1.1.26.4.1.5,IEEE8021-SPB-MIB::ieee8021PcrEctStaticTableGroupVID,,,,,,The collection of objects used to represent ieee8021SpbEctStaticTable for PCR,
.1.3.111.2.802.1.1.26.4.1.6,IEEE8021-SPB-MIB::ieee8021PcrEctStaticTableGroupMrt,,,,,,The collection of objects used to represent ieee8021PcrEctStaticTable,
.1.3.111.2.802.1.1.26.4.1.7,IEEE8021-SPB-MIB::ieee8021PcrEctDynamicTableGroup,,,,,,The collection of objects used to represent ieee8021SpbEctDynamicTable for PCR.
.1.3.111.2.802.1.1.26.4.1.8,IEEE8021-SPB-MIB::ieee8021PcrAdjStaticTableGroup,,,,,,The collection of objects used to represent ieee8021SpbAdjStaticTable for PCR.
.1.3.111.2.802.1.1.26.4.1.9,IEEE8021-SPB-MIB::ieee8021PcrAdjDynamicTableGroup,,,,,,The collection of objects used to represent ieee8021SpbAdjDynamicTable for PCR.
.1.3.111.2.802.1.1.26.4.1.10,IEEE8021-SPB-MIB::ieee8021PcrTopNodeTableGroup,,,,,,The collection of objects used to represent ieee8021SpbTopNodeTable for PCR.
.1.3.111.2.802.1.1.26.4.1.11,IEEE8021-SPB-MIB::ieee8021PcrTopEctTableGroup,,,,,,The collection of objects used to represent ieee8021PcrTopEctTable.
.1.3.111.2.802.1.1.26.4.1.12,IEEE8021-SPB-MIB::ieee8021PcrTopEdgeTableGroup,,,,,,The collection of objects used to represent ieee8021SpbTopEdgeTable for PCR.
.1.3.111.2.802.1.1.26.4.1.13,IEEE8021-SPB-MIB::ieee8021PcrTopSrvTableGroupVid,,,,,,The collection of objects used to represent ieee8021SpbvTopSrvTable for PCR,
.1.3.111.2.802.1.1.26.4.2,IEEE8021-SPB-MIB::ieee8021PcrCompliances,,,,,,
.1.3.111.2.802.1.1.26.4.2.1,IEEE8021-SPB-MIB::ieee8021PcrCompliance,,,,,,Compliance to IEEE 802.1 PCR
.1.3.111.2.802.1.1.27,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Mib,,,,,,MIB Module for managing systems that provide Provider Backbone Bridge Traffic Engineering (PBB-TE) Infrastructure Segment Protection. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). All Rights Reserved  This MIB module is part of IEEE 802.1Q; See the IEEE 802.1Q standard for full legal notices. 
.1.3.111.2.802.1.1.27.0,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Notifications,,,,,,
.1.3.111.2.802.1.1.27.0.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgAdminFailure,,,,,,An IPG generates this notification whenever an adminisistrative command cannot be executed by the IPS state machine. For example, when a requested manual switch cannot be performed because of a signal failure condition. The management entity receiving the notification can identify the system from the network source address of the notification and can identify the IPG by the indices of  the OID of the ieee8021TeipsV2IpgConfigState variable in the notification:  ieee8021BridgeBaseComponentId - Identifies the component on the Bridge where the protection group is configured. ieee8021TeipsV2Ipgid - The ID of the protection group. 
.1.3.111.2.802.1.1.27.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Objects,,,,,,
.1.3.111.2.802.1.1.27.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgTable,,not-accessible,,current,,The IPG table. Each entry in this table corresponds to an Infrastructure Protection Group (IPG) associated with a PBB supporting Infrastructure Protection Switching (IPS).
.1.3.111.2.802.1.1.27.1.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021TeipsV2Ipgid,current,,The IPG table entry.
.1.3.111.2.802.1.1.27.1.1.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Ipgid,Unsigned32,not-accessible,,current,,Uniquely identifies an IPG within the PBB.
.1.3.111.2.802.1.1.27.1.1.1.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgWorkingMA,Unsigned32,read-create,,current,,Identifies the Segment MA that corresponds to the IPG's working entity. The MA index in this column must hold a value that is the value of dot1agCfmStackMaIndex column for some entry in the dot1agCfmStackTable before the RowStatus for this row can be set to Active. Furthermore, this column may not be modified when the RowStatus for this row is Active.
.1.3.111.2.802.1.1.27.1.1.1.3,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgProtectionMA,Unsigned32,read-create,,current,,Identifies the Segment MA that corresponds to the IPG's protection entity. The MA index in this column must hold a value that is the value of dot1agCfmStackMaIndex column for some entry in the dot1agCfmStackTable before the RowStatus for this row can be set to Active. Furthermore, this column may not be modified when the RowStatus for this row is Active.
.1.3.111.2.802.1.1.27.1.1.1.4,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgWorkingPortNumber,Unsigned32,read-only,,current,,Identifies the local Port associated with the IPG Working Segment.
.1.3.111.2.802.1.1.27.1.1.1.5,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgProtectionPortNumber,Unsigned32,read-only,,current,,Identifies the local Port associated with the IPG Protection Segment.
.1.3.111.2.802.1.1.27.1.1.1.6,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable if this column is set to permanent.
.1.3.111.2.802.1.1.27.1.1.1.7,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of this row. The writable columns in a row cannot be changed if the row is active. The TeipsIpgWorkingMA and TeipsIpgProtectionMA columns must be specified before the row can be activated.
.1.3.111.2.802.1.1.27.1.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2TesiTable,,not-accessible,,current,,The IPG TE-SID table contains identifies the TE service instances associated with an IPG.
.1.3.111.2.802.1.1.27.1.2.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2TesiEntry,,not-accessible,ieee8021TeipsV2Ipgid:ieee8021TeipsV2TesiIndex,current,,The TE-IPS TESI entry. Each entry identifies a TESI associated with an IPG.
.1.3.111.2.802.1.1.27.1.2.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2TesiIndex,Unsigned32,not-accessible,,current,,This is an identifier, of local signifigance to a particular PBB-TE TE-SID associated with an IPG.
.1.3.111.2.802.1.1.27.1.2.1.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2TesiId,Unsigned32,read-create,,current,,This column holds the TESI identifier corresponding to a TE service instance associated with an IPG.
.1.3.111.2.802.1.1.27.1.2.1.3,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2TesiStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable for permanent rows.
.1.3.111.2.802.1.1.27.1.2.1.4,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2TesiRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated.
.1.3.111.2.802.1.1.27.1.3,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsTable,,not-accessible,,current,,The Candidate PS table lists, in priority order, from highest priority to lowest priority, the Maintenance Associations corresponding to candidate Protection Segments associated with an IPG.
.1.3.111.2.802.1.1.27.1.3.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsEntry,,not-accessible,ieee8021TeipsV2Ipgid:ieee8021TeipsV2CandidatePsIndex,current,,A Candidate PS entry. Each entry identifies a candidate Protection Segment associated with an IPG.
.1.3.111.2.802.1.1.27.1.3.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsIndex,Unsigned32,not-accessible,,current,,This is an identifier, of local signifigance to a particular candidate Protection Segment associated with an IPG.
.1.3.111.2.802.1.1.27.1.3.1.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsMA,Unsigned32,read-create,,current,,This column holds the candidate Protection Segment MA corresponding to a candidate Protection Segment associated with an IPG.
.1.3.111.2.802.1.1.27.1.3.1.3,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsPort,Unsigned32,read-only,,current,,This column holds the Port Number corresponding to the candidate Protection Segment associated with an IPG.
.1.3.111.2.802.1.1.27.1.3.1.4,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsOper,INTEGER,read-only,,current,true(1):false(2),This column indicates whether or not the candidate Protection Segment is operational.
.1.3.111.2.802.1.1.27.1.3.1.5,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. All read-create columns must be writable for permanent rows.
.1.3.111.2.802.1.1.27.1.3.1.6,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated.
.1.3.111.2.802.1.1.27.1.4,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigTable,,not-accessible,,current,,The PBB-TE IPS IPG config table contains configuration and status information for each IPG configured in the system. Entries in this table are created implicitly by the creation of entries in the ieee8021TeipsV2IpgTable.
.1.3.111.2.802.1.1.27.1.4.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021TeipsV2Ipgid,current,,The IPG confguration table entry. Rows are created in this table implicitly when a row is added to the ieee8021TeipsV2IpgTable.
.1.3.111.2.802.1.1.27.1.4.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigState,INTEGER,read-only,,current,workingSegment(1):protectionSegment(2):waitToRestore(3):protAdmin(4),This column indicates the current state of the protection switching state machine for an IPG.  The value can be one of the following: workingSegment(1) The protection switching state machine is in the WORKING_PATH state. protectionSegment(2) The protection switching state machine is in the PROTECTION_PATH state. waitToRestore(3) The protection switching state machine is in the WTR state. protAdmin(4) The protection switching state machine is in the PROT_ADMIN state.
.1.3.111.2.802.1.1.27.1.4.1.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigCommandStatus,INTEGER,read-only,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column indicates the status of administrative commands within the protection group. It reflects the current operational administrative command being acted upon by the IPG.
.1.3.111.2.802.1.1.27.1.4.1.3,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigCommandLast,INTEGER,read-only,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column indicates the last attempted administrative command applied to the IPG. It is changed whenever a write is made to the CommandAdmin column of this table and is essentially record of the last attempted administrative operation.
.1.3.111.2.802.1.1.27.1.4.1.4,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigCommandAdmin,INTEGER,read-create,,current,clear(1):lockOutProtection(2):forceSwitch(3):manualSwitchToProtection(4):manualSwitchToWorking(5),This column is used by the operator to request that the IPG state machine perform some administrative operation. The operator requests a command by writing the command value to this column. The state machine indicates the command that it is performing by setting the value of the CommandStatus column of this table. This column always reads back as clear(1).
.1.3.111.2.802.1.1.27.1.4.1.5,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigActiveRequests,INTEGER,read-only,,current,noRequest(1):loP(2):fs(3):pSFH(4):wSFH(5):manualSwitchToProtection(6):manualSwitchToWorking(7),This column shows the status of active requests associated with the IPG.
.1.3.111.2.802.1.1.27.1.4.1.6,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigWTR,Unsigned32,read-create,,current,,This column is used to configure the wait-to-restore timer for the IPG operation. The timer may be configured in steps of 1 minute between 5 and 12 minutes, the default being 5. Additionally, the value 0 is used to indicate that the IPG is to operate non-revertively. The value 0 is not permitted if the IPG is configured for M:1 IPS operation.
.1.3.111.2.802.1.1.27.1.4.1.7,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigHoldOff,Unsigned32,read-create,,current,,This column is used to configure the hold off timer. The purpose is to allow IPS to fix the problem before a higher-layer mechanism, such as PBB-TE TESI protection, is invoked or to allow an inner IPG to fix  the problem before IPS is invoked by the outer IPG when  IPGs are nested. The hold off timer has a period of from 0 to 10 seconds, the default being 0, with a 100ms granularity.
.1.3.111.2.802.1.1.27.1.4.1.8,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgM1ConfigState,INTEGER,read-only,,current,psAssigned(1):segmentOk(2):segmentFailed(3):assignNewPs(4):revertToBetterPs(5),This column indicates the current state of the M:1 protection switching state machine for an IPG if M:1 IPS is supported. The value can be one of the following: psAssigned(1) The protection switching state machine is in the PS_ASSIGNED state. segmentOk(2) The protection switching state machine is in the SEGMENT_OK state. segmentFailed(3) The protection switching state machine is in the SEGMENT_FAILED state. assignNewPs(4) The protection switching state machine is in the ASSIGN_NEW_PS state.  revertToBetterPs(5) The protection switching state machine is in the REVERT_T0_BETTER_PS state.
.1.3.111.2.802.1.1.27.1.4.1.9,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigMWTR,Unsigned32,read-create,,current,,This column is used to configure the M:1 wait-to-restore timer for the IPG operation if M:1 protection is supported. The timer may be configured in steps of 1 minute between 5 and 12 minutes, the default being 5. Additionally, the value 0 is used to indicate that the IPG is to operate non-revertively.
.1.3.111.2.802.1.1.27.1.4.1.10,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigNotifyEnable,INTEGER,read-create,,current,true(1):false(2),This column is used to enable or disable transmission of ieee8021TeipsV2IpgAdminFailure notifications. These notifications are generated whenever an administrative command cannot be performed by the IPG.
.1.3.111.2.802.1.1.27.1.4.1.11,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigStorageType,INTEGER,read-create,,current,other(1):volatile(2):nonVolatile(3):permanent(4):readOnly(5),This object indicates the persistence of this entry. For permanent objects the ieee8021TeipsV2IpgConfigCommandAdmin column must be writable.
.1.3.111.2.802.1.1.27.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Conformance,,,,,,
.1.3.111.2.802.1.1.27.2.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Compliances,,,,,,
.1.3.111.2.802.1.1.27.2.1.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Compliance,,,,,,The compliance statement for support of the TEIPS MIB module.
.1.3.111.2.802.1.1.27.2.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2Groups,,,,,,
.1.3.111.2.802.1.1.27.2.2.1,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgGroup,,,,,,Objects for the IPG group.
.1.3.111.2.802.1.1.27.2.2.2,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2CandidatePsGroup,,,,,,Objects for the Candidate PS group.
.1.3.111.2.802.1.1.27.2.2.3,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgTesiGroup,,,,,,Objects for the IPG Tuple group.
.1.3.111.2.802.1.1.27.2.2.4,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigManGroup,,,,,,Mandatory objects for the TeipsConfiguration group.
.1.3.111.2.802.1.1.27.2.2.5,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2IpgConfigOptGroup,,,,,,Optional 0bjects for the TeipsConfiguration group.
.1.3.111.2.802.1.1.27.2.2.6,IEEE8021-TEIPS-V2-MIB::ieee8021TeipsV2NotificationsGroup,,,,,,Objects for the notifications group.
.1.3.111.2.802.1.1.28,IEEE8021-ECMP-MIB::ieee8021EcmpMib,,,,,,MIB Module for managing systems that provide 802.1Q Equal Cost Multiple Paths. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.28.0,IEEE8021-ECMP-MIB::ieee8021EcmpNotifications,,,,,,
.1.3.111.2.802.1.1.28.1,IEEE8021-ECMP-MIB::ieee8021EcmpObjects,,,,,,
.1.3.111.2.802.1.1.28.1.1,IEEE8021-ECMP-MIB::ieee8021QBridgeEcmpFdbTable,,not-accessible,,current,,A table that contains information about unicast entries for which the device has forwarding and/or filtering information. This information is used by the ECMP next hop selection function in determining how to propagate a received frame.
.1.3.111.2.802.1.1.28.1.1.1,IEEE8021-ECMP-MIB::ieee8021QBridgeEcmpFdbEntry,,not-accessible,,current,,Information about a specific unicast MAC address for which the device has some forwarding and/or filtering information.
.1.3.111.2.802.1.1.28.1.1.1.1,IEEE8021-ECMP-MIB::ieee8021QBridgeEcmpFdbPortList,OCTET,read-only,,current,,The complete set of ports, in this FID, to which frames destined for this individual MAC address may be forwarded.
.1.3.111.2.802.1.1.28.1.2,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlTable,,not-accessible,,current,,A table flow filtering control informmation for ports in a Bridge supporting F-Tag processing.
.1.3.111.2.802.1.1.28.1.2.1,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlEntry,,not-accessible,ieee8021BridgeBasePortComponentId:ieee8021BridgeBasePort:ieee8021EcmpFlowFilterCtlVid,current,,An entry in the Flow Filtering Control Table for a port (CPB or PNP).
.1.3.111.2.802.1.1.28.1.2.1.1,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlVid,Integer32,not-accessible,,current,,A B-vID registered on the port.
.1.3.111.2.802.1.1.28.1.2.1.2,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlEnabled,INTEGER,read-only,,current,true(1):false(2),Indicates whether or not flow filtering behavior is enabled on the port for the VID (true(1) is enabled, false(2) is disabled).
.1.3.111.2.802.1.1.28.1.2.1.3,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlHashGen,INTEGER,read-only,,current,true(1):false(2),indicates whether or not flow hash generation is enabled on the port for the VID (true(1) is enabled, false(2) is disabled).
.1.3.111.2.802.1.1.28.1.2.1.4,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlTtl,Integer32,read-write,,current,,the initial TTL value for frames entering the flow filtering SPT Domain. Valid values are 1..63, zero indicates the value has not been set. This object is persistent.
.1.3.111.2.802.1.1.28.1.3,IEEE8021-ECMP-MIB::ieee8021EcmpEctStaticTable,,not-accessible,,current,,Table containing alternate Bridge priorities for tie-breaker masks used in selecting shared tree root bridges. The table is indexed by - ieee8021SpbTopIx from ieee8021SpbMtidStaticTable indicating the ISIS-SPB topology instance into which the bridge priority will be advertised, and - ieee8021EcmpEctStaticEntryTieBreakMask the associated tie-break mask value.
.1.3.111.2.802.1.1.28.1.3.1,IEEE8021-ECMP-MIB::ieee8021EcmpEctStaticEntry,,not-accessible,ieee8021SpbTopIx:ieee8021EcmpEctStaticEntryTieBreakMask,current,,This entry contains information about backbone services configured on this system to be advertised by ISIS-SPB.
.1.3.111.2.802.1.1.28.1.3.1.1,IEEE8021-ECMP-MIB::ieee8021EcmpEctStaticEntryTieBreakMask,Integer32,not-accessible,,current,,The value used to create the Tie-Break Mask for selecting a shared tree root bridge.
.1.3.111.2.802.1.1.28.1.3.1.2,IEEE8021-ECMP-MIB::ieee8021EcmpEctStaticEntryBridgePriority,OCTET,read-create,,current,,A Bridge Priority value to be used for selecting a shared tree root bridge, i.e., the most significant 4 bits of the Bridge Identifier. This object is persistent.
.1.3.111.2.802.1.1.28.1.3.1.3,IEEE8021-ECMP-MIB::ieee8021EcmpEctStaticEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),This column holds the status for this row. When the status is active, no columns of this table may be modified. All columns must have a valid value before the row can be activated. This object is persistent.
.1.3.111.2.802.1.1.28.1.4,IEEE8021-ECMP-MIB::ieee8021EcmpTopSrvTable,,not-accessible,,current,,Added info for SPBM PBB encapsulated services in this network.
.1.3.111.2.802.1.1.28.1.4.1,IEEE8021-ECMP-MIB::ieee8021EcmpTopSrvEntry,,not-accessible,,current,,This table contains additional information about backbone services configured on this system to be advertised by ISIS-SPB.
.1.3.111.2.802.1.1.28.1.4.1.1,IEEE8021-ECMP-MIB::ieee8021EcmpTopSrvEntryTsBit,INTEGER,read-only,,current,true(1):false(2),If true(1), indicates the BSI transmits multicast frames on a shared tree from this CBP.
.1.3.111.2.802.1.1.28.1.4.1.2,IEEE8021-ECMP-MIB::ieee8021EcmpTopSrvEntryTieBreakMask,Integer32,read-only,,current,,The value used to create the Tie-Break Mask for calculating multicast trees.
.1.3.111.2.802.1.1.28.1.5,IEEE8021-ECMP-MIB::ieee8021QBridgePortVlanTtlStatisticsTable,,not-accessible,,current,,A table containing per-port, per-VID TTL discard statistics.
.1.3.111.2.802.1.1.28.1.5.1,IEEE8021-ECMP-MIB::ieee8021QBridgePortVlanTtlStatisticsEntry,,not-accessible,,current,,TTL discard statistics for a VID on an interface.
.1.3.111.2.802.1.1.28.1.5.1.1,IEEE8021-ECMP-MIB::ieee8021QBridgeTpVlanPortTtlDiscards,Counter64,read-only,,current,,The number of valid frames received by this port from its segment that were classified as belonging to this VLAN and that were discarded due to TTL expiry. Discontinuities in the value of the counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime object of the associated interface (if any).
.1.3.111.2.802.1.1.28.2,IEEE8021-ECMP-MIB::ieee8021EcmpConformance,,,,,,
.1.3.111.2.802.1.1.28.2.1,IEEE8021-ECMP-MIB::ieee8021EcmpGroups,,,,,,
.1.3.111.2.802.1.1.28.2.1.1,IEEE8021-ECMP-MIB::ieee8021QBridgeEcmpFdbGroup,,,,,,FDB Port Map for ECMP Individual address
.1.3.111.2.802.1.1.28.2.1.2,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilterCtlGroup,,,,,,Flow filtering control parameters on a CBP or PNP
.1.3.111.2.802.1.1.28.2.1.3,IEEE8021-ECMP-MIB::ieee8021EcmpEctStaticGroup,,,,,,Optional Bridge Priority for selecting shared tree root
.1.3.111.2.802.1.1.28.2.1.4,IEEE8021-ECMP-MIB::ieee8021EcmpTopSrvGroup,,,,,,Advertised I-SID parameters controlling multicast routing
.1.3.111.2.802.1.1.28.2.1.5,IEEE8021-ECMP-MIB::ieee8021QBridgePortVlanTtlStatisticsGroup,,,,,,TTL discard statistics
.1.3.111.2.802.1.1.28.2.2,IEEE8021-ECMP-MIB::ieee8021EcmpCompliances,,,,,,
.1.3.111.2.802.1.1.28.2.2.1,IEEE8021-ECMP-MIB::ieee8021EcmpCompliance,,,,,,Compliance to IEEE 802.1 SPBM ECMP
.1.3.111.2.802.1.1.28.2.2.2,IEEE8021-ECMP-MIB::ieee8021EcmpFlowFilteringCompliance,,,,,,Compliance to IEEE 802.1 SPBM ECMP with flow filtering
.1.3.111.2.802.1.1.29,IEEE8021-Preemption-MIB::ieee8021PreemptionMib,,,,,,The Bridge MIB module for managing devices that support the frame preemption enhancements for IEEE 802.1Q Bridges. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.29.0,IEEE8021-Preemption-MIB::ieee8021PreemptionNotifications,,,,,,
.1.3.111.2.802.1.1.29.1,IEEE8021-Preemption-MIB::ieee8021PreemptionObjects,,,,,,
.1.3.111.2.802.1.1.29.1.1,IEEE8021-Preemption-MIB::ieee8021PreemptionParameters,,,,,,
.1.3.111.2.802.1.1.29.1.1.1,IEEE8021-Preemption-MIB::ieee8021PreemptionParameterTable,,not-accessible,,current,,A table containing a set of frame preemption  parameters, one for each priority value. All writeable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.29.1.1.1.1,IEEE8021-Preemption-MIB::ieee8021PreemptionParameterEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021PreemptionPriority,current,,A list of objects containing preemption parameters  for each priority value.
.1.3.111.2.802.1.1.29.1.1.1.1.1,IEEE8021-Preemption-MIB::ieee8021PreemptionPriority,Unsigned32,not-accessible,,current,,The priority number associated with the row of the table. A row in this table is created for each priority value.
.1.3.111.2.802.1.1.29.1.1.1.1.2,IEEE8021-Preemption-MIB::ieee8021FramePreemptionAdminStatus,INTEGER,read-write,,current,express(1):preemptible(2),The value of the framePreemptionAdminStatus parameter for the traffic class. The default value of the framePreemptionAdminStatus parameter  is express (1). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.29.1.1.2,IEEE8021-Preemption-MIB::ieee8021PreemptionConfigTable,,not-accessible,,current,,A table containing a set of frame preemption  parameters, one for each Port. All writeable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.29.1.1.2.1,IEEE8021-Preemption-MIB::ieee8021PreemptionConfigEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort,current,,A list of objects containing preemption parameters  for each Port.
.1.3.111.2.802.1.1.29.1.1.2.1.1,IEEE8021-Preemption-MIB::ieee8021FramePreemptionHoldAdvance,Unsigned32,read-only,,current,,The value of the holdAdvance parameter for the Port in nanoseconds. There is no default value; the holdAdvance is  a property of the underlying MAC.
.1.3.111.2.802.1.1.29.1.1.2.1.2,IEEE8021-Preemption-MIB::ieee8021FramePreemptionReleaseAdvance,Unsigned32,read-only,,current,,The value of the releaseAdvance parameter for the Port in nanoseconds. There is no default value; the releaseAdvance is  a property of the underlying MAC.
.1.3.111.2.802.1.1.29.1.1.2.1.3,IEEE8021-Preemption-MIB::ieee8021FramePreemptionActive,INTEGER,read-only,,current,idle(1):active(2),The value is active (2) when preemption is operationally active for the Port, and idle (1) otherwise.
.1.3.111.2.802.1.1.29.1.1.2.1.4,IEEE8021-Preemption-MIB::ieee8021FramePreemptionHoldRequest,INTEGER,read-only,,current,hold(1):release(2),The value is hold (1) when the sequence of gate operations for the Port has executed a Set-And-Hold-MAC operation, and release (2) when the sequence of gate operations has  executed a Set-And-Release-MAC operation. The  value of this object is release (2) on system initialization.
.1.3.111.2.802.1.1.29.2,IEEE8021-Preemption-MIB::ieee8021PreemptionConformance,,,,,,
.1.3.111.2.802.1.1.29.2.1,IEEE8021-Preemption-MIB::ieee8021PreemptionCompliances,,,,,,
.1.3.111.2.802.1.1.29.2.1.1,IEEE8021-Preemption-MIB::ieee8021PreemptionCompliance,,,,,,The compliance statement for devices supporting  frame preemption.  Support of the objects defined in this MIB module also requires support of the IEEE8021-BRIDGE-MIB; the provisions of 17.3.2 apply to implementations claiming support of this MIB. 
.1.3.111.2.802.1.1.29.2.2,IEEE8021-Preemption-MIB::ieee8021PreemptionGroups,,,,,,
.1.3.111.2.802.1.1.29.2.2.1,IEEE8021-Preemption-MIB::ieee8021PreemptionGroup,,,,,,Objects that allow management of frame preemption.
.1.3.111.2.802.1.1.30,IEEE8021-ST-MIB::ieee8021STMib,,,,,,The Bridge MIB module for managing devices that support the Scheduled Traffic Enhancements for IEEE 802.1Q Bridges. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.30.0,IEEE8021-ST-MIB::ieee8021STNotifications,,,,,,
.1.3.111.2.802.1.1.30.1,IEEE8021-ST-MIB::ieee8021STObjects,,,,,,
.1.3.111.2.802.1.1.30.1.1,IEEE8021-ST-MIB::ieee8021STMaxSDUSubtree,,,,,,
.1.3.111.2.802.1.1.30.1.1.1,IEEE8021-ST-MIB::ieee8021STMaxSDUTable,,not-accessible,,current,,A table containing a set of max SDU  parameters, one for each traffic class. All writeable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.30.1.1.1.1,IEEE8021-ST-MIB::ieee8021STMaxSDUEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021STTrafficClass,current,,A list of objects containing Max SDU size  for each traffic class supported by the Port.
.1.3.111.2.802.1.1.30.1.1.1.1.1,IEEE8021-ST-MIB::ieee8021STTrafficClass,Unsigned32,not-accessible,,current,,The traffic class number associated with the row of the table. A row in this table is created for each traffic class that is supported by the Port
.1.3.111.2.802.1.1.30.1.1.1.1.2,IEEE8021-ST-MIB::ieee8021STMaxSDU,Unsigned32,read-write,,current,,The value of the MaxSDU parameter for the traffic class. This value is represented as an unsigned integer. A value of 0 is interpreted as the max SDU size supported by the underlying MAC. The default value of the MaxSDU parameter is 0. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.1.1.1.3,IEEE8021-ST-MIB::ieee8021TransmissionOverrun,Counter64,read-only,,current,,A counter of transmission overrun events, where a PDU is still being transmitted by a MAC at the time when the transmission gate for the queue closed.
.1.3.111.2.802.1.1.30.1.2,IEEE8021-ST-MIB::ieee8021STParameters,,,,,,
.1.3.111.2.802.1.1.30.1.2.1,IEEE8021-ST-MIB::ieee8021STParametersTable,,not-accessible,,current,,A table that contains the per-port manageable parameters for  traffic scheduling. For a given Port, a row in the table exists. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.30.1.2.1.1,IEEE8021-ST-MIB::ieee8021STParametersEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort,current,,A list of objects that contains the manageable parameters for  traffic scheduling for a port.
.1.3.111.2.802.1.1.30.1.2.1.1.1,IEEE8021-ST-MIB::ieee8021STGateEnabled,INTEGER,read-write,,current,true(1):false(2),The GateEnabled parameter determines whether traffic scheduling is active (true) or inactive (false). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.2,IEEE8021-ST-MIB::ieee8021STAdminGateStates,OCTET,read-write,,current,,The administrative value of the GateStates parameter for the Port. The bits of the octet represent the gate states for the  corresponding traffic classes; the MS bit corresponds to traffic class 7, the LS bit to traffic class 0. A bit value of 0 indicates closed; a  bit value of 1 indicates open. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.3,IEEE8021-ST-MIB::ieee8021STOperGateStates,OCTET,read-only,,current,,The operational value of the GateStates parameter for the Port. The bits of the octet represent the gate states for the  corresponding traffic classes; the MS bit corresponds to traffic class 7, the LS bit to traffic class 0. A bit value of 0 indicates closed; a  bit value of 1 indicates open.
.1.3.111.2.802.1.1.30.1.2.1.1.4,IEEE8021-ST-MIB::ieee8021STAdminControlListLength,Unsigned32,read-write,,current,,The administrative value of the ListMax parameter for the Port. The integer value indicates the number of entries (TLVs) in the AdminControlList. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.5,IEEE8021-ST-MIB::ieee8021STOperControlListLength,Unsigned32,read-only,,current,,The operational value of the ListMax parameter for the Port. The integer value indicates the number of entries (TLVs) in the OperControlList.
.1.3.111.2.802.1.1.30.1.2.1.1.6,IEEE8021-ST-MIB::ieee8021STAdminControlList,OCTET,read-write,,current,,The administrative value of the ControlList parameter for the Port. The octet string value represents the contents of the control list as an ordered list of entries, each encoded as a TLV, as follows. The first octet of each TLV is interpreted as an unsigned integer representing a gate operation name: 0: SetGateStates 1: Set-And-Hold-MAC 2: Set-And-Release-MAC 3-255: Reserved for future gate operations  The second octet of the TLV is the length field,  interpreted as an unsigned integer, indicating the number of octets of the value that follows the length. A length of zero indicates that there is no value  (i.e., the gate operation has no parameters).  The third through (3 + length -1)th octets encode the  parameters of the gate operation, in the order that they  appear in the definition of the operation in Table 8-6. Two parameter types are currently defined:  - GateState: A GateState parameter is encoded in a single octet. The bits of the octet represent the gate states for the  corresponding traffic classes; the MS bit corresponds to traffic class 7, the LS bit to traffic class 0. A bit value of 0 indicates closed; a bit value of 1 indicates open.  - TimeInterval:  A TimeInterval is encoded in 4 octets as a 32-bit  unsigned integer, representing a number of nanoseconds. The first octet encodes the most significant 8 bits of the  integer, and the fourth octet encodes the least  significant 8 bits.  The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.7,IEEE8021-ST-MIB::ieee8021STOperControlList,OCTET,read-only,,current,,The operational value of the ListMax parameter for the Port. The octet string value represents the contents of the control list as an ordered list of TLVs, as follows. The first octet of each TLV is interpreted as a gate operation name: 0: SetGateStates 1: Set-And-Hold-MAC 2: Set-And-Release-MAC 3-255: Reserved for future gate operations  The second octet of the TLV is the length field,  interpreted as an unsigned integer, indicating the number of octets of the value that follows the length. A length of zero indicates that there is no value  (i.e., the gate operation has no parameters).  The third through (3 + length -1)th octets encode the  parameters of the gate operation, in the order that they  appear in the definition of the operation in Table 8-6. Two parameter types are currently defined:  - GateState: A GateState parameter is encoded in a single octet. The bits of the octet represent the gate states for the  corresponding traffic classes; the MS bit corresponds to traffic class 7, the LS bit to traffic class 0.  A bit value of 0 indicates closed; a  bit value of 1 indicates open.  - TimeInterval:  A TimeInterval is encoded in 4 octets as a 32-bit  unsigned integer, representing a number of nanoseconds. The first octet encodes the most significant 8 bits of the integer, and the fourth octet encodes the least significant 8 bits.
.1.3.111.2.802.1.1.30.1.2.1.1.8,IEEE8021-ST-MIB::ieee8021STAdminCycleTimeNumerator,Unsigned32,read-write,,current,,The administrative value of the numerator of the CycleTime parameter for the Port. The numerator and denominator together represent the cycle time as a rational number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.9,IEEE8021-ST-MIB::ieee8021STAdminCycleTimeDenominator,Unsigned32,read-write,,current,,The administrative value of the denominator of the  CycleTime parameter for the Port. The numerator and denominator together represent the cycle time as a rational number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.10,IEEE8021-ST-MIB::ieee8021STOperCycleTimeNumerator,Unsigned32,read-only,,current,,The operational value of the numerator of the  CycleTime parameter for the Port. The numerator and denominator together represent the cycle time as a rational number of seconds.
.1.3.111.2.802.1.1.30.1.2.1.1.11,IEEE8021-ST-MIB::ieee8021STOperCycleTimeDenominator,Unsigned32,read-only,,current,,The operational value of the denominator of the  CycleTime parameter for the Port. The numerator and denominator together represent the  cycle time as a rational number of seconds.
.1.3.111.2.802.1.1.30.1.2.1.1.12,IEEE8021-ST-MIB::ieee8021STAdminCycleTimeExtension,Unsigned32,read-write,,current,,The administrative value of the CycleTimeExtension  parameter for the Port.  The value is an unsigned integer number of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.13,IEEE8021-ST-MIB::ieee8021STOperCycleTimeExtension,Unsigned32,read-only,,current,,The operational value of the CycleTimeExtension parameter for the Port. The value is an unsigned integer number of nanoseconds.
.1.3.111.2.802.1.1.30.1.2.1.1.14,IEEE8021-ST-MIB::ieee8021STAdminBaseTime,OCTET,read-write,,current,,The administrative value of the BaseTime parameter for the Port. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.15,IEEE8021-ST-MIB::ieee8021STOperBaseTime,OCTET,read-only,,current,,The operationsl value of the BaseTime parameter for the Port. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds.
.1.3.111.2.802.1.1.30.1.2.1.1.16,IEEE8021-ST-MIB::ieee8021STConfigChange,INTEGER,read-write,,current,true(1):false(2),The ConfigChange parameter signals the start of a  configuration change when it is set to TRUE. This should only be done when the various administrative parameters are all set to appropriate values.
.1.3.111.2.802.1.1.30.1.2.1.1.17,IEEE8021-ST-MIB::ieee8021STConfigChangeTime,OCTET,read-only,,current,,The PTPtime at which the next config change is scheduled to occur. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.18,IEEE8021-ST-MIB::ieee8021STTickGranularity,Unsigned32,read-only,,current,,The granularity of the cycle time clock, represented as an unsigned number of tenths of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.30.1.2.1.1.19,IEEE8021-ST-MIB::ieee8021STCurrentTime,OCTET,read-only,,current,,The current time, in PTPtime, as maintained by the local system. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds.
.1.3.111.2.802.1.1.30.1.2.1.1.20,IEEE8021-ST-MIB::ieee8021STConfigPending,INTEGER,read-only,,current,true(1):false(2),The value of the ConfigPending state machine variable. The value is TRUE if a configuration change is in progress but has not yet completed.
.1.3.111.2.802.1.1.30.1.2.1.1.21,IEEE8021-ST-MIB::ieee8021STConfigChangeError,Counter64,read-only,,current,,A counter of the number of times that a re-configuration of the traffic schedule has been requested with the old schedule still running and the requested base time was in the past.
.1.3.111.2.802.1.1.30.1.2.1.1.22,IEEE8021-ST-MIB::ieee8021STSupportedListMax,Unsigned32,read-only,,current,,The maximum value supported by this Port of the  AdminControlListLength and OperControlListLength parameters.
.1.3.111.2.802.1.1.30.2,IEEE8021-ST-MIB::ieee8021STConformance,,,,,,
.1.3.111.2.802.1.1.30.2.1,IEEE8021-ST-MIB::ieee8021STCompliances,,,,,,
.1.3.111.2.802.1.1.30.2.1.1,IEEE8021-ST-MIB::ieee8021STCompliance,,,,,,The compliance statement for devices supporting  scheduled traffic.  Support of the objects defined in this MIB module also requires support of the IEEE8021-BRIDGE-MIB; the provisions of 17.3.2 apply to implementations claiming support of this MIB. 
.1.3.111.2.802.1.1.30.2.2,IEEE8021-ST-MIB::ieee8021STGroups,,,,,,
.1.3.111.2.802.1.1.30.2.2.1,IEEE8021-ST-MIB::ieee8021STObjectsGroup,,,,,,Objects that allow management of scheduled traffic.
.1.3.111.2.802.1.1.31,IEEE8021-PSFP-MIB::ieee8021PSFPMib,,,,,,The Bridge MIB module for managing devices that support the Per-Stream Filtering and Policing enhancements for IEEE 802.1Q Bridges. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE Std 802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.31.0,IEEE8021-PSFP-MIB::ieee8021PSFPNotifications,,,,,,
.1.3.111.2.802.1.1.31.1,IEEE8021-PSFP-MIB::ieee8021PSFPObjects,,,,,,
.1.3.111.2.802.1.1.31.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamFilterParameters,,,,,,
.1.3.111.2.802.1.1.31.1.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamFilterTable,,not-accessible,,current,,A table that contains the per-filter instance manageable parameters for stream filters. A row in the table exists for each stream filter instance. associated with a Bridge component. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.31.1.1.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamFilterEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021PSFPStreamFilterInstance,current,,A list of objects that contains the manageable parameters for  stream filters for a Bridge component.
.1.3.111.2.802.1.1.31.1.1.1.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamFilterInstance,Unsigned32,not-accessible,,current,,The StreamFilterInstance parameter is an index into the  StreamFilterTable. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.2,IEEE8021-PSFP-MIB::ieee8021PSFPStreamHandleSpec,Integer32,read-create,,current,,The StreamHandleSpec parameter contains a stream identifier  specification value. A value of -1 denotes the wild card value; all positive values denote stream identifier values. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.3,IEEE8021-PSFP-MIB::ieee8021PSFPPrioritySpec,Integer32,read-create,,current,,The PrioritySpec parameter contains a priority  specification value. A value of -1 denotes the wild card value; zero or positive values denote priority values. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.4,IEEE8021-PSFP-MIB::ieee8021PSFPStreamGateInstanceID,Unsigned32,read-create,,current,,The StreamGateInstance parameter contains the index of an  entry in the Stream Gate Table. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.5,IEEE8021-PSFP-MIB::ieee8021PSFPFilterSpecificationList,OCTET,read-create,,current,,The FilterSpecificationList parameter contains a list of  filter specifications associated with this stream filter. The octet string value represents the contents of the list as an ordered list of entries, each encoded as a TLV, as follows. The first octet of each TLV is interpreted as an unsigned integer representing a filter specification type: 0: Maximum SDU Size. 1: Flow meter instance identifier. 2-255: Reserved for future gate operations  The second and third octets of the TLV are the length field,  interpreted as an unsigned integer, indicating the number of octets of the value that follows the length. A length of zero indicates that there is no value  (i.e., the filter specification has no parameters).  The fourth through (4 + length -1)th octets encode the  parameters of the filter specification, as defined for each filter specification type.  - Maximum SDU Size: A single SDU size parameter is encoded in four octets, and is interpreted as an unsigned integer value.  - Flow meter instance identifier: A single flow meter instance identifier is encoded in four octets, and is interpreted as an unsigned integer value.  The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.6,IEEE8021-PSFP-MIB::ieee8021PSFPMatchingFramesCount,Counter64,read-only,,current,,The MatchingFramesCount counter counts received frames that match this stream filter. 
.1.3.111.2.802.1.1.31.1.1.1.1.7,IEEE8021-PSFP-MIB::ieee8021PSFPPassingFramesCount,Counter64,read-only,,current,,The PassingFramesCount counter counts received frames that pass the gate associated with this stream filter. 
.1.3.111.2.802.1.1.31.1.1.1.1.8,IEEE8021-PSFP-MIB::ieee8021PSFPNotPassingFramesCount,Counter64,read-only,,current,,The NotPassingFramesCount counter counts received frames that do not pass the gate associated with this stream filter. 
.1.3.111.2.802.1.1.31.1.1.1.1.9,IEEE8021-PSFP-MIB::ieee8021PSFPPassingSDUCount,Counter64,read-only,,current,,The PassingSDUCount counter counts received frames that pass the SDU size filter specification associated with this stream filter. 
.1.3.111.2.802.1.1.31.1.1.1.1.10,IEEE8021-PSFP-MIB::ieee8021PSFPNotPassingSDUCount,Counter64,read-only,,current,,The NotPassingSDUCount counter counts received frames that do not pass the SDU size filter specification associated with this stream filter. 
.1.3.111.2.802.1.1.31.1.1.1.1.11,IEEE8021-PSFP-MIB::ieee8021PSFPREDFramesCount,Counter64,read-only,,current,,The REDFramesCount counter counts received frames that were discarded as a result of the operation of the flow meter. 
.1.3.111.2.802.1.1.31.1.1.1.1.12,IEEE8021-PSFP-MIB::ieee8021PSFPStreamBlockedDueToOversizeFrameEnable,INTEGER,read-create,,current,true(1):false(2),The ieee8021PSFPStreamBlockedDueToOversizeFrameEnable object  contains a Boolean value that indicates whether the  ieee8021PSFPStreamBlockedDueToOversizeFrame function is enabled (TRUE) or disabled (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.13,IEEE8021-PSFP-MIB::ieee8021PSFPStreamBlockedDueToOversizeFrame,INTEGER,read-create,,current,true(1):false(2),The ieee8021PSFPStreamBlockedDueToOversizeFrame object  contains a Boolean value that indicates whether, if the ieee8021PSFPStreamBlockedDueToOversizeFrame function is  enabled, all frames are to be discarded (TRUE)  or not (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.1.1.1.14,IEEE8021-PSFP-MIB::ieee8021PSFPStreamFilterEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.31.1.2,IEEE8021-PSFP-MIB::ieee8021PSFPStreamGateParameters,,,,,,
.1.3.111.2.802.1.1.31.1.2.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamGateTable,,not-accessible,,current,,A table that contains the per-gate instance manageable parameters for stream gate scheduling. For a given Bridge component, a row in the table exists for each stream gate instance. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.31.1.2.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamGateEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021PSFPStreamGateInstance,current,,A list of objects that contains the manageable parameters for  stream gate scheduling for a Bridge component.
.1.3.111.2.802.1.1.31.1.2.1.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamGateInstance,Unsigned32,not-accessible,,current,,The StreamGateInstance parameter is an index into the  StreamGateTable. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.2,IEEE8021-PSFP-MIB::ieee8021PSFPGateEnabled,INTEGER,read-create,,current,true(1):false(2),The GateEnabled parameter determines whether the stream gate is active (true) or inactive (false). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.3,IEEE8021-PSFP-MIB::ieee8021PSFPAdminGateStates,INTEGER,read-create,,current,open(1):closed(2),The administrative value of the GateStates parameter for the stream gate. The open value indicates that the gate is open,  the closed value indicates that the gate is closed. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.4,IEEE8021-PSFP-MIB::ieee8021PSFPOperGateStates,INTEGER,read-only,,current,open(1):closed(2),The operational value of the GateStates parameter for the stream gate. The open value indicates that the gate is open,  the closed value indicates that the gate is closed.
.1.3.111.2.802.1.1.31.1.2.1.1.5,IEEE8021-PSFP-MIB::ieee8021PSFPAdminControlListLength,Unsigned32,read-create,,current,,The administrative value of the ListMax parameter for the gate. The integer value indicates the number of entries (TLVs) in the AdminControlList. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.6,IEEE8021-PSFP-MIB::ieee8021PSFPOperControlListLength,Unsigned32,read-only,,current,,The operational value of the ListMax parameter for the gate. The integer value indicates the number of entries (TLVs) in the OperControlList.
.1.3.111.2.802.1.1.31.1.2.1.1.7,IEEE8021-PSFP-MIB::ieee8021PSFPAdminControlList,OCTET,read-create,,current,,The administrative value of the ControlList parameter for the gate. The octet string value represents the contents of the control list as an ordered list of entries, each encoded as a TLV, as follows. The first octet of each TLV is interpreted as an unsigned integer representing a gate operation name: 0: SetGateAndIPV 1-255: Reserved for future gate operations  The second octet of the TLV is the length field,  interpreted as an unsigned integer, indicating the number of octets of the value that follows the length. A length of zero indicates that there is no value  (i.e., the gate operation has no parameters).  The third through (3 + length -1)th octets encode the  parameters of the gate operation, in the order that they  appear in the definition of the operation in Table 8-4. Three parameter types are defined:  - StreamGateState: A GateState parameter is encoded in a single octet, and is interpreted as an integer value. The value 1 indicates open; the value 2 indicates closed.  - IPV: An IPV is encoded in four octets as a 32-bit  signed integer. A negative denotes the null value; zero or positive values denote internal priority values.  - TimeInterval:  A TimeInterval is encoded in 4 octets as a 32-bit  unsigned integer, representing a number of nanoseconds. The first octet encodes the most significant 8 bits of the  integer, and the fourth octet encodes the least  significant 8 bits. - IntervalOctetMax: An integer representing the maximum number of MSDU octets  that are permitted to pas the gate during the specified TimeInterval. If this parameter is omitted, there is no maximum.  The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.8,IEEE8021-PSFP-MIB::ieee8021PSFPOperControlList,OCTET,read-only,,current,,The operational value of the ControlList parameter for the gate. The octet string value represents the contents of the control list as an ordered list of entries, each encoded as a TLV, as follows. The first octet of each TLV is interpreted as an unsigned integer representing a gate operation name: 0: SetGateAndIPV 1-255: Reserved for future gate operations  The second octet of the TLV is the length field,  interpreted as an unsigned integer, indicating the number of octets of the value that follows the length. A length of zero indicates that there is no value  (i.e., the gate operation has no parameters).  The third through (3 + length -1)th octets encode the  parameters of the gate operation, in the order that they  appear in the definition of the operation in Table 8-4. Three parameter types are defined:  - StreamGateState: A GateState parameter is encoded in a single octet, and is interpreted as an integer value. The value 1 indicates open; the value 2 indicates closed.  - IPV: An IPV is encoded in four octets as a 32-bit  signed integer. A negative value denotes the null value; zero and positive values denote internal priority values.  - TimeInterval:  A TimeInterval is encoded in 4 octets as a 32-bit  unsigned integer, representing a number of nanoseconds. The first octet encodes the most significant 8 bits of the integer, and the fourth octet encodes the least significant 8 bits. - IntervalOctetMax: An integer representing the maximum number of MSDU octets  that are permitted to pas the gate during the specified TimeInterval. If this parameter is omitted, there is no maximum. 
.1.3.111.2.802.1.1.31.1.2.1.1.9,IEEE8021-PSFP-MIB::ieee8021PSFPAdminCycleTimeNumerator,Unsigned32,read-create,,current,,The administrative value of the numerator of the CycleTime parameter for the gate. The numerator and denominator together represent the cycle time as a rational number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.10,IEEE8021-PSFP-MIB::ieee8021PSFPAdminCycleTimeDenominator,Unsigned32,read-create,,current,,The administrative value of the denominator of the  CycleTime parameter for the gate. The numerator and denominator together represent the cycle time as a rational number of seconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.11,IEEE8021-PSFP-MIB::ieee8021PSFPOperCycleTimeNumerator,Unsigned32,read-only,,current,,The operational value of the numerator of the  CycleTime parameter for the gate. The numerator and denominator together represent the cycle time as a rational number of seconds.
.1.3.111.2.802.1.1.31.1.2.1.1.12,IEEE8021-PSFP-MIB::ieee8021PSFPOperCycleTimeDenominator,Unsigned32,read-only,,current,,The operational value of the denominator of the  CycleTime parameter for the gate. The numerator and denominator together represent the  cycle time as a rational number of seconds.
.1.3.111.2.802.1.1.31.1.2.1.1.13,IEEE8021-PSFP-MIB::ieee8021PSFPAdminCycleTimeExtension,Unsigned32,read-create,,current,,The administrative value of the CycleTimeExtension  parameter for the gate.  The value is an unsigned integer number of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.14,IEEE8021-PSFP-MIB::ieee8021PSFPOperCycleTimeExtension,Unsigned32,read-only,,current,,The operational value of the CycleTimeExtension parameter for the gate. The value is an unsigned integer number of nanoseconds.
.1.3.111.2.802.1.1.31.1.2.1.1.15,IEEE8021-PSFP-MIB::ieee8021PSFPAdminBaseTime,OCTET,read-create,,current,,The administrative value of the BaseTime parameter for the gate. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.16,IEEE8021-PSFP-MIB::ieee8021PSFPOperBaseTime,OCTET,read-only,,current,,The operationsl value of the BaseTime parameter for the gate. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds.
.1.3.111.2.802.1.1.31.1.2.1.1.17,IEEE8021-PSFP-MIB::ieee8021PSFPConfigChange,INTEGER,read-create,,current,true(1):false(2),The ConfigChange parameter signals the start of a  configuration change for the gate when it is set to TRUE. This should only be done when the various administrative parameters are all set to appropriate values.
.1.3.111.2.802.1.1.31.1.2.1.1.18,IEEE8021-PSFP-MIB::ieee8021PSFPConfigChangeTime,OCTET,read-only,,current,,The PTPtime at which the next config change is scheduled to occur. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.19,IEEE8021-PSFP-MIB::ieee8021PSFPTickGranularity,Unsigned32,read-only,,current,,The granularity of the cycle time clock, represented as an unsigned number of tenths of nanoseconds. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.20,IEEE8021-PSFP-MIB::ieee8021PSFPCurrentTime,OCTET,read-only,,current,,The current time, in PTPtime, as maintained by the local system. The value is a representation of a PTPtime value,  consisting of a 48-bit integer number of seconds and a 32-bit integer number of nanoseconds.
.1.3.111.2.802.1.1.31.1.2.1.1.21,IEEE8021-PSFP-MIB::ieee8021PSFPConfigPending,INTEGER,read-only,,current,true(1):false(2),The value of the ConfigPending state machine variable. The value is TRUE if a configuration change is in progress but has not yet completed.
.1.3.111.2.802.1.1.31.1.2.1.1.23,IEEE8021-PSFP-MIB::ieee8021PSFPConfigChangeError,Counter64,read-only,,current,,A counter of the number of times that a re-configuration of the traffic schedule has been requested with the old schedule still running and the requested base time was in the past.
.1.3.111.2.802.1.1.31.1.2.1.1.24,IEEE8021-PSFP-MIB::ieee8021PSFPAdminIPV,Integer32,read-create,,current,,The administrative value of the IPV parameter for the gate. A value of -1 denotes the null value. 
.1.3.111.2.802.1.1.31.1.2.1.1.25,IEEE8021-PSFP-MIB::ieee8021PSFPOperIPV,Integer32,read-create,,current,,The operational value of the IPV parameter for the gate. A value of -1 denotes the null value. 
.1.3.111.2.802.1.1.31.1.2.1.1.26,IEEE8021-PSFP-MIB::ieee8021PSFPGateClosedDueToInvalidRxEnable,INTEGER,read-create,,current,true(1):false(2),The PSFPGateClosedDueToInvalidRxEnable object contains a Boolean value that indicates whether the  PSFPGateClosedDueToInvalidRx function is enabled (TRUE) or disabled (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.27,IEEE8021-PSFP-MIB::ieee8021PSFPGateClosedDueToInvalidRx,INTEGER,read-create,,current,true(1):false(2),The PSFPGateClosedDueToInvalidRx object contains a Boolean value that indicates whether, if the PSFPGateClosedDueToInvalidRx function is enabled,  all frames are to be discarded (TRUE) or not (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.28,IEEE8021-PSFP-MIB::ieee8021PSFPGateClosedDueToOctetsExceededEnable,INTEGER,read-create,,current,true(1):false(2),The PSFPGateClosedDueToOctetsExceededEnable object contains a Boolean value that indicates whether the PSFPGateClosedDueToOctetsExceeded function is enabled (TRUE) or disabled (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.29,IEEE8021-PSFP-MIB::ieee8021PSFPGateClosedDueToOctetsExceeded,INTEGER,read-create,,current,true(1):false(2),The PSFPGateClosedDueToOctetsExceeded parameter contains a Boolean value that indicates whether, if the  PSFPGateClosedDueToOctetsExceeded function is enabled, all  frames are to be discarded (TRUE) or not (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.2.1.1.30,IEEE8021-PSFP-MIB::ieee8021PSFPStreamGateEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.31.1.3,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterParameters,,,,,,
.1.3.111.2.802.1.1.31.1.3.1,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterTable,,not-accessible,,current,,A table that contains the per-meter instance manageable parameters for flow meters. For a given Bridge component, a row in the table exists for each flow meter instance. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.31.1.3.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021PSFPFlowMeterInstance,current,,A list of objects that contains the manageable parameters for  flow meters for a Bridge component.
.1.3.111.2.802.1.1.31.1.3.1.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterInstance,Unsigned32,not-accessible,,current,,The FlowMeterInstance parameter is an index into the  FlowMeterTable. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.2,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterCIR,Unsigned32,read-create,,current,,The FlowMeterCIR parameter contains an integer value that represents the CIR value for the flow meter, in bit/second. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.3,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterCBS,Unsigned32,read-create,,current,,The FlowMeterCBS parameter contains an integer value that represents the CBS value for the flow meter, in octets. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.4,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterEIR,Unsigned32,read-create,,current,,The FlowMeterEIR parameter contains an integer value that represents the EIR value for the flow meter, in bit/second. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.5,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterEBS,Unsigned32,read-create,,current,,The FlowMeterEBS parameter contains an integer value that represents the EBS value for the flow meter, in octets. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.6,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterCF,Integer32,read-create,,current,,The FlowMeterCF parameter contains an integer value that represents the CF value for the flow meter, as an integer value 0 or 1. The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.7,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterCM,INTEGER,read-create,,current,colorBlind(1):colorAware(2),The FlowMeterCM parameter contains an integer value that represents the CM value for the flow meter, as an enumerated value indicating colorBlind(1) or colorAware(2). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.8,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterDropOnYellow,INTEGER,read-create,,current,true(1):false(2),The FlowMeterDropOnYellow parameter contains a Boolean value that indicates whether yellow frames are dropped (TRUE) or have drop_eligible set to TRUE (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.9,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterMarkAllFramesRedEnable,INTEGER,read-create,,current,true(1):false(2),The FlowMeterMarkAllFramesRedEnable parameter contains a Boolean value that indicates whether the MarkAllFramesRed function is enabled (TRUE) or disabled (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.10,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterMarkAllFramesRed,INTEGER,read-create,,current,true(1):false(2),The FlowMeterMarkAllFramesRed parameter contains a Boolean value that indicates whether, if the  MarkAllFramesRed function is enabled, all frames are to be discarded (TRUE) or not (FALSE). The value of this object MUST be retained across reinitializations of the management system.
.1.3.111.2.802.1.1.31.1.3.1.1.11,IEEE8021-PSFP-MIB::ieee8021PSFPFlowMeterEntryRowStatus,INTEGER,read-create,,current,active(1):notInService(2):notReady(3):createAndGo(4):createAndWait(5):destroy(6),The status of the row. The writable columns in a row cannot be changed if the row is active. All columns MUST have a valid value before a row can be activated. 
.1.3.111.2.802.1.1.31.1.4,IEEE8021-PSFP-MIB::ieee8021PSFPStreamParameters,,,,,,
.1.3.111.2.802.1.1.31.1.4.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamParameterTable,,not-accessible,,current,,A table that contains per-Bridge component manageable parameters for PSFP. A row in the table exists for each Bridge component. All writable objects in this table must be persistent over power up restart/reboot.
.1.3.111.2.802.1.1.31.1.4.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPStreamParameterEntry,,not-accessible,ieee8021BridgeBaseComponentId,current,,A list of objects that contains the manageable parameters for  flow meters for a Bridge component.
.1.3.111.2.802.1.1.31.1.4.1.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPMaxStreamFilterInstances,Unsigned32,read-only,,current,,The MaxStreamFilterInstances parameter defines the  maximum number of stream filter instances that are supported by this Bridge component.
.1.3.111.2.802.1.1.31.1.4.1.1.2,IEEE8021-PSFP-MIB::ieee8021PSFPMaxStreamGateInstances,Unsigned32,read-only,,current,,The MaxStreamGateInstances parameter defines the  maximum number of stream gate instances that are supported by this Bridge component.
.1.3.111.2.802.1.1.31.1.4.1.1.3,IEEE8021-PSFP-MIB::ieee8021PSFPMaxFlowMeterInstances,Unsigned32,read-only,,current,,The MaxFlowMeterInstances parameter defines the  maximum number of flow meter instances that are supported by this Bridge component.
.1.3.111.2.802.1.1.31.1.4.1.1.4,IEEE8021-PSFP-MIB::ieee8021PSFPSupportedListMax,Unsigned32,read-only,,current,,The SupportedListMax parameter defines the  The maximum value supported by this Bridge component of the AdminControlListLength and OperControlListLength parameters.
.1.3.111.2.802.1.1.31.2,IEEE8021-PSFP-MIB::ieee8021PSFPConformance,,,,,,
.1.3.111.2.802.1.1.31.2.1,IEEE8021-PSFP-MIB::ieee8021PSFPCompliances,,,,,,
.1.3.111.2.802.1.1.31.2.1.1,IEEE8021-PSFP-MIB::ieee8021PSFPCompliance,,,,,,The compliance statement for devices supporting  PSFP.  Support of the objects defined in this MIB module also requires support of the IEEE8021-BRIDGE-MIB; the provisions of 17.3.2 apply to implementations claiming support of this MIB. 
.1.3.111.2.802.1.1.31.2.2,IEEE8021-PSFP-MIB::ieee8021PSFPGroups,,,,,,
.1.3.111.2.802.1.1.31.2.2.1,IEEE8021-PSFP-MIB::ieee8021PSFPObjectsGroup,,,,,,Objects that allow management of PSFP.
.1.3.111.2.802.1.1.32,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMib,,,,,,The Bridge MIB module for managing devices that support the IEEE Std 802.1Q Stream Reservation Protocol Enhancements and Performance Improvements. Unless otherwise indicated, the references in this MIB module are to IEEE Std 802.1Q. Copyright (C) IEEE (2018). This version of this MIB module is part of IEEE802.1Q; see the draft itself for full legal notices.
.1.3.111.2.802.1.1.32.0,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtNotifications,,,,,,
.1.3.111.2.802.1.1.32.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtObjects,,,,,,
.1.3.111.2.802.1.1.32.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtBridgeDelay,,,,,,
.1.3.111.2.802.1.1.32.1.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtBridgeDelayTable,,not-accessible,,current,,A table containing a set of parameters necessary to determine the delay of frames as they pass through the Bridge's relay. There is one Bridge Delay managed object per Port pair of a Bridge component. The Port pair consists of three indices, an ingress Port followed by an egress Port and a traffic class associated with the Port pair.
.1.3.111.2.802.1.1.32.1.1.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtBridgeDelayEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeTrafficClass:ieee8021TsnRemoteMgmtBridgeIngressPort:ieee8021TsnRemoteMgmtBridgeEgressPort,current,,A list of objects containing information necessary to determine the delay of frames as they pass through the Bridge's relay.
.1.3.111.2.802.1.1.32.1.1.1.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtBridgeIngressPort,Unsigned32,not-accessible,,current,,...
.1.3.111.2.802.1.1.32.1.1.1.1.2,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtBridgeEgressPort,Unsigned32,not-accessible,,current,,...
.1.3.111.2.802.1.1.32.1.1.1.1.3,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtIndependentDelayMin,Unsigned32,read-only,,current,,This attribute provides the minimum delay independent from frame length for a frame to forward from ingress port to egress port. The delay begins when the message timestamp point of the ingress frame passes the reference plane marking the boundary between the network media and PHY. The delay ends when the message timestamp point of the egress frame passes the reference plane marking the boundary between the network media and PHY. The message timestamp point is specified by IEEE Std 802.1AS for various media, near the start of the frame. Note: This delay includes all aspects of length-independent delay for a frame that is forwarded, including handling of error conditions.
.1.3.111.2.802.1.1.32.1.1.1.1.4,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtIndependentDelayMax,Unsigned32,read-only,,current,,This attribute provides the maximum delay independent from frame length for a frame to forward from ingress port to egress port. The delay begins when the message timestamp point of the ingress frame passes the reference plane marking the boundary between the network media and PHY. The delay ends when the message timestamp point of the egress frame passes the reference plane marking the boundary between the network media and PHY. The message timestamp point is specified by IEEE Std 802.1AS for various media, near the start of the frame.
.1.3.111.2.802.1.1.32.1.1.1.1.5,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtDependentDelayMin,Unsigned32,read-only,,current,,This attribute provides the minimum length-dependent delay from ingress port to egress port. It provides the portion of delay that is dependent on frame length, where frame length is the number of octets that transfer across the MAC Service interfaces. Each length-dependent delay attribute specifies the time for a single octet of the frame to transfer from ingress to egress.
.1.3.111.2.802.1.1.32.1.1.1.1.6,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtDependentDelayMax,Unsigned32,read-only,,current,,This attribute provides the maximum length-dependent delay from ingress port to egress port. It provides the portion of delay that is dependent on frame length, where frame length is the number of octets that transfer across the MAC Service interfaces. Each length-dependent delay attribute specifies the time for a single octet of the frame to transfer from ingress to egress.
.1.3.111.2.802.1.1.32.1.2,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtPropagationDelay,,,,,,
.1.3.111.2.802.1.1.32.1.2.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtPropagationDelayTable,,not-accessible,,current,,A table containing a set of parameters necessary to determine the delay along the network media (e.g. cable) for a frame transmitted from the specifed Port of this Bridge to the neighboring Port on a different Bridge. There is one Propagation Delay managed object per egress Port of a Bridge.
.1.3.111.2.802.1.1.32.1.2.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtPropagationDelayEntry,,not-accessible,ieee8021BridgeBasePort,current,,A list of objects containing information necessary to determine the delay along the network media (e.g. cable) for a frame transmitted from the specifed Port of this Bridge to the neighboring Port on a different Bridge.
.1.3.111.2.802.1.1.32.1.2.1.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtTxPropagationDelay,Unsigned32,read-only,,current,,This attribute provides the transmission propagation delay. The propagation delay begins when the message timestamp point of an egress frame passes the reference plane marking the boundary between the network media and PHY. It ends when the message timestamp point of an ingress frame on the neighboring Bridge's Port passes the reference plane marking the boundary between the network media and PHY. The message timestamp point is specified by IEEE Std 802.1AS for various media.
.1.3.111.2.802.1.1.32.1.3,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtStaticTrees,,,,,,
.1.3.111.2.802.1.1.32.1.3.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtStaticTreesSupported,INTEGER,read-only,,current,true(1):false(2),This attribute is used by the TSN CNC to determine that TE-MSTID is supported by the Bridge.
.1.3.111.2.802.1.1.32.1.4,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpExternalControl,,,,,,
.1.3.111.2.802.1.1.32.1.4.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMsrpMrpExternalControlTable,,not-accessible,,current,,A table containing a set of parameters necessary for a network manager to 1) disable MRP attribute propagation (MAP) for the MRP Participant of a bridge port, 2) read MRP attribute registrations that the MRP Participant receives, and 3) write MRP attribute values for the MRP Participant to declare.
.1.3.111.2.802.1.1.32.1.4.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMsrpMrpExternalControlEntry,,not-accessible,ieee8021BridgeBaseComponentId:ieee8021BridgeBasePort:ieee8021QBridgeVlanIndex,current,,A list of objects necessary for a network manager to 1) disable MRP attribute propagation (MAP) for the MRP Participant of a bridge port, 2) read MRP attribute registrations that the MRP Participant receives, and 3) write MRP attribute values for the MRP Participant to declare.
.1.3.111.2.802.1.1.32.1.4.1.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMsrpMrpExternalControl,INTEGER,read-write,,current,true(1):false(2),This attribute is used to indicate, whether MRP attributes are propagated on the MRP Participant, according to the specifications for MRP Attribute Propagation (MAP) and specifications of the MRP Application. When true(1), the MRP Participant is removed from the MRP Application's MAP Context. The MRP Participant performs all other aspects of MRP, including MRP operation, MRP specifications, and MRPDU encodings. The application component stores MAD indications for registration received on the Port, and invokes MAD requests for declarations on the Port. When false(2), MRP attributes propagate on the MRP Participant according to the specifications for MRP Attribute Propagation (MAP) and specifications of the MRP Application. Ports with the externalControl attribute false(2) are considered as candidates for the MRP Application's MAP Context. The remaining attributes of this subtree are ignored by Ports with the externalControl attribute false(2). This managed object applies to the MSRP application. A table is provided for each MAP Context (VLAN ID).
.1.3.111.2.802.1.1.32.1.4.1.1.2,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpIndicationList,OCTET,read-only,,current,,This attribute is used to store the list of all joined MRP attributes for the MRP Participant when the ieee8021TsnRemoteMgmtMrpExternalControl attribute is true(1). When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is false(2), this attribute is ignored by the MRP Participant, and returns the empty octet string.
.1.3.111.2.802.1.1.32.1.4.1.1.3,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpIndicationListLength,Unsigned32,read-only,,current,,This attribute is used to provide the number of octets in the ieee8021TsnRemoteMgmtMrpIndicationListLength attribute. When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is false(2), this attribute returns zero.
.1.3.111.2.802.1.1.32.1.4.1.1.4,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpIndicationChangeCounter,Counter64,read-only,,current,,This attribute is used to provide the number of changes done to the ieee8021TsnRemoteMgmtMrpIndicationList. When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is false(2), this attribute returns zero.
.1.3.111.2.802.1.1.32.1.4.1.1.5,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpAdminRequestList,OCTET,read-only,,current,,This attribute is used to provide the administrative value of the current list of MAD requests for the MRP Participant (operRequestList). Each entry in this attribute is encoded as the attribute_type parameter as a single octet, followed by the length of the attribute_value parameter as a single octet, followed by a sequence of octets for the attribute_value parameter. When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is true(1), this attribute is copied to the ieee8021TsnRemoteMgmtMrpOperRequestList attribute as soon as possible according to the implementation. When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is false(2), this attribute is ignored by the MRP Participant, but it retains its value.
.1.3.111.2.802.1.1.32.1.4.1.1.6,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpAdminRequestListLength,Unsigned32,read-only,,current,,This attribute is used to provide the administrative value for the number of octets in the ieee8021TsnRemoteMgmtMrpAdminRequestList attribute. When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is true(1), this attribute is copied to the ieee8021TsnRemoteMgmtMrpOperRequestListLength attribute at the same time that the ieee8021TsnRemoteMgmtMrpAdminRequestList attribute is copied to the ieee8021TsnRemoteMgmtMrpOperRequestList attribute. When the ieee8021TsnRemoteMgmtMrpExternalControl attribute is false(2), this attribute is ignored by the MRP Participant, but it retains its value.
.1.3.111.2.802.1.1.32.1.4.1.1.7,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpOperRequestList,OCTET,read-only,,current,,This attribute is used to proivde the operational value of the current list of MAD requests for the MRP Participant.
.1.3.111.2.802.1.1.32.1.4.1.1.8,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpOperRequestListLength,Unsigned32,read-only,,current,,This attribute is used to provide the operational value of the ieee8021TsnRemoteMgmtMrpAdminRequestListLength attribute, and it is copied at the same time that ieee8021TsnRemoteMgmtMrpAdminRequestList attribute is copied to ieee8021TsnRemoteMgmtMrpOperRequestList.
.1.3.111.2.802.1.1.32.2,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtConformance,,,,,,
.1.3.111.2.802.1.1.32.2.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtCompliances,,,,,,
.1.3.111.2.802.1.1.32.2.1.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtCompliance,,,,,,The compliance statement for devices supporting TSN Remote management. Support of the objects defined in the IEEE8021-TSN REMOTE MANAGEMENT MIB also requires support of the IEEE8021-BRIDGE-MIB; the provisions of 17.3.2 apply to implementations claiming support of the IEEE8021-TSN REMOTE MANAGEMENT MIB.
.1.3.111.2.802.1.1.32.2.2,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtGroups,,,,,,
.1.3.111.2.802.1.1.32.2.2.1,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtBridgeDelayGroup,,,,,,Objects that define the delay of frames as they pass through the Bridge's relay.
.1.3.111.2.802.1.1.32.2.2.2,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtPropagationDelayGroup,,,,,,Objects that define delay of frames along the network media (e.g. cable).
.1.3.111.2.802.1.1.32.2.2.3,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtStaticTreesGroup,,,,,,Objects that define static tree support.
.1.3.111.2.802.1.1.32.2.2.4,IEEE8021-TSN-REMOTE-MANAGEMENT-MIB::ieee8021TsnRemoteMgmtMrpExternalControlGroup,,,,,,Objects that define configuration of MRP External control.
